ZTE NetNumen U31 (BN) Product Description

NetNumen
U31
Product Description
(BN)
NetNumen U31 (BN) Product Description

Version
Date
Author
Fan Qiaoyun,
V1.00
2011-03-31
Zhou Yan,
Zheng Wenwen
Fan Qiaoyun,
V1.1
2011-8-29
Zhou Yan,
Wang Lei
V1.2
2012-01-04
Fan Qiaoyun,
Ren Xiang,
Wang Lei
Fan Qiaoyun,
V1.3
2012-06-30
Ren Xiang,
Zheng Wenwen
Reviewer
Notes
Chen Jie, Jiang

Yong, Zhao Yalu,
Jia Kui, Ye
Not open to the Third Party
Dezhong
Chen Jie, Jiang
Yong, Zhao Yalu,
Update based on NetNumen U31
Jia Kui, Ye
R22 V12.11.20P01
Dezhong
Chen Jie, Jiang

Yong, Zhao Yalu,
Jia Kui, Ye
Dezhong
Update based on NetNumen

U31 R22 V12.11.40
Chen Jie, Jiang

Yong, Zhao Yalu,
Update based on NetNumen U31
Jia Kui, Ye
R22 V12.12.20
Dezhong
2012 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential Proprietary
TABLE OF CONTENTS
1
1.1
1.2
1.3
1.4
Overview ............................................................................................................ 9
Network Operation & Maintenance Trend ............................................................ 9
Brief Introduction .................................................................................................. 9
Product Positioning .............................................................................................. 9
Manageable NE Type ........................................................................................ 10
2
2.1
2.2
2.2.1
2.2.2
2.3
2.3.1
2.3.2
2.4
2.5
2.5.1
2.5.2
2.5.3
2.6
2.6.1
2.6.2
2.6.3
2.6.4
2.7
2.7.1
2.7.2
2.7.3
System Characteristics ................................................................................... 14

Unified Network Management ............................................................................ 14
Advanced architecture and high scalability ........................................................ 14
Powerful device management capability ............................................................ 14
Flexible Plug-in design ....................................................................................... 14
Networking advantages...................................................................................... 15
Flexible networking function ............................................................................... 15
Powerful management scale .............................................................................. 15
Standard northbound interface ........................................................................... 15
Service deployment advantages ........................................................................ 16
Public Service Deployment Advantages ............................................................. 16
Advantages of CTN device service deployment ................................................. 16
Advantages of IP device service deployment ..................................................... 19
Value-added function advantages ...................................................................... 20
Advantages of public value-added functions ...................................................... 20
Advantages of CTN device value-added functions ............................................. 21
Advantages of OTN device value-added functions ............................................. 22
Advantages of IP device value-added functions ................................................. 24
Security advantage ............................................................................................ 24
High available back-up routine ........................................................................... 24
Triple-level security mechanism ......................................................................... 25
Perfect data consistency protection ................................................................... 25
3
3.1
3.2
3.2.1
3.2.2
3.2.3
3.3
3.3.1
3.3.2
3.3.3
System Architecture........................................................................................ 26
System Hardware Structure ............................................................................... 26
System Software Structure ................................................................................ 28
Client ................................................................................................................. 28
Server ................................................................................................................ 29
Database ........................................................................................................... 29
System Interfaces .............................................................................................. 29
Internal Interfaces .............................................................................................. 29
Southbound Interfaces ....................................................................................... 29
Northbound Interfaces ....................................................................................... 29
3.4
System Running Platform .................................................................................. 30
4
4.1
4.2
4.3
4.3.1
4.3.2
4.3.3
4.4
4.4.1
4.4.2
4.4.3
4.5
4.6
4.7
4.8
4.9
System Basic Features ................................................................................... 31

Topology Management ...................................................................................... 31
View Management ............................................................................................. 33
Fault Management ............................................................................................. 34
Network Fault Monitoring ................................................................................... 35
Alarm Message Processing ............................................................................... 35
Failure Diagnosis and Elimination ...................................................................... 39
Performance Management ................................................................................. 39
Performance Task Management ........................................................................ 40
Performance Report Output ............................................................................... 41
Performance Threshold Management ................................................................ 42
Security Management ........................................................................................ 42
Log Management ............................................................................................... 43
System management ......................................................................................... 45
Task management ............................................................................................. 46
Report management .......................................................................................... 47
5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
PTN Management ............................................................................................ 49

PTN Public Management ................................................................................... 49
PTN Interface Management ............................................................................... 52
PTN Protocol Management ................................................................................ 54
PTN Service Management ................................................................................. 57
PTN Clock Management .................................................................................... 58
PTN OAM Management ..................................................................................... 59
PTN QoS Management ...................................................................................... 60
PTN Protection Management ............................................................................. 61
PTN Maintenance and Security Management .................................................... 63
6
6.1
6.2
6.3
SDH/MSTP Management ................................................................................. 67

SDH/MSTP Single NE Management .................................................................. 67
ASON Management ........................................................................................... 71
MSTP Protection Subnet Function ..................................................................... 72
7
7.1
7.2
7.3
7.4
7.5
7.6
WDM/OTN Management .................................................................................. 74

WDM/OTN Network Element Management ........................................................ 74
WDM/OTN Equipment Public Configuration ....................................................... 77
WDM/OTN Equipment Overhead Configuration ................................................. 78
WDM/OTN Equipment Service Configuration ..................................................... 79
WDM/OTN Equipment APR-AOSD Management .............................................. 80
WDM/OTN Equipment Power Management ....................................................... 81
7.7
7.8
7.9
7.10
7.11
7.12
7.13
WDM/OTN Equipment Spectrum Management .................................................. 83

WDM/OTN Equipment Wavelength Management .............................................. 83
WDM/OTN Equipment Protection Configuration................................................. 84
WDM/OTN Equipment Other Interface & Module Configuration ......................... 86
WDM/OTN L2 Ethernet Configuration ................................................................ 87
WDM/OTN Equipment Maintenance .................................................................. 89
WASON Configuration ....................................................................................... 90
8
8.1
8.2
8.3
8.4
8.5
8.6
8.7
8.8
8.9
8.10
8.10.1
8.10.2
8.11
IP NE Management .......................................................................................... 98
IP Resource Configuration Management ........................................................... 98
IP Rack Management ...................................................................................... 100
IP Performance Data Types ............................................................................. 100
IP File management ......................................................................................... 102
IP OAM Management ...................................................................................... 103
IP Network TE Management ............................................................................ 106
IP Network MPLS VPN Management ............................................................... 107
IP Network VLAN Management ....................................................................... 109
IP Network ZESR/ZESS Service Management ................................................ 109
IP Network IPTV Service Management ............................................................ 110
IPTV Controllable Multicast Management Based on User Service ................... 110
IPTV Broadcast Control Management Based on Multicast Source ................... 112
IP Network Cluster Service Management ......................................................... 113
9
9.1
9.2
9.3
9.4
9.5
9.6
9.7
9.8
9.9
9.10
End to End Service Management ................................................................. 115

Customer management.................................................................................... 115
PTN E2E Management .................................................................................... 115
MSTP E2E Management ................................................................................. 120
MSTP Ethernet E2E Management ................................................................... 124
WDM/OTN E2E Management .......................................................................... 128
IP E2E service management ............................................................................ 132
PTN and IP cross-domain E2E service management ....................................... 134
PTN and MSTP cross-domain E2E service management ................................ 135
MSTP and WDM/OTN cross-domain E2E service management ...................... 136
Cross-domain E2E Service Managemetn of CTN and WDM/OTN ................... 136
10
10.1
10.2
10.3
10.4
10.4.1
10.4.2
System Security ............................................................................................ 138

Physical Security.............................................................................................. 138
Network Security .............................................................................................. 138
System Security ............................................................................................... 138
Application Security ......................................................................................... 139
Security model ................................................................................................. 139
Access control and authorization ..................................................................... 140
10.4.3
10.4.4
10.4.5
System authentication ...................................................................................... 140

System audit .................................................................................................... 141
Security management policy ............................................................................ 141
11
11.1
11.2
11.3
System Reliability.......................................................................................... 142

NE data protection ........................................................................................... 142
NetNumen U31 single-host data protection .................................................. 142
Active/standby server data protection .............................................................. 143
12
12.1
12.1.1
12.1.2
12.1.3
12.2
12.2.1
12.2.2
12.3
12.3.1
12.4
12.5
System Networking ....................................................................................... 147

Networking Mode ............................................................................................. 147
Local networking .............................................................................................. 147
Remote networking .......................................................................................... 147
Mixed networking ............................................................................................. 148
Client ............................................................................................................... 148
Single-client ..................................................................................................... 148
Multi-client........................................................................................................ 149
Server .............................................................................................................. 150
Centralized deployment ................................................................................... 150
Network Element Networking and Monitoring Management ............................. 150
Network Bandwidth Demand ............................................................................ 151
13
13.1
13.2
13.3
13.3.1
13.3.2
13.4
13.4.1
13.4.2
13.4.3
13.5
13.6
13.7
Technical Specifications ............................................................................... 154

Overview of equivalent NE calculation ............................................................. 154
Rapid calculation table for equipment equivalent NE ....................................... 155
Network Management Capability ..................................................................... 159
Management Capacity and Configuration ........................................................ 159
Number of Clients ............................................................................................ 161
Software Performance ..................................................................................... 161
System response time ..................................................................................... 161
Active/standby NM performance ...................................................................... 162
Data Storage Capacity ..................................................................................... 162
Power supply Index.......................................................................................... 162
Environmental Index ........................................................................................ 163
Reliability Index ................................................................................................ 163
14
LCT management .......................................................................................... 166
FIGURES
Figure 1-1 ZTE NetNumen U31(BN) .................................................................................10
Figure 3-1 NetNumen U31 hardware Structure .................................................................26
Figure 3-2 NetNumen U31 Software Structure ..................................................................28
Figure 4-1 Performance threshold schematic diagram..........................................................42
Figure 7-1 WDM/OTN Equipment Overhead Configuration ..................................................78
Figure 7-2 WDM/OTN Equipment Service Configuration ......................................................79
Figure 10-1 Role-based authority and domain fine-grain security model ............................139
Figure 11-1 Local dual-system backup Solution .................................................................144
Figure 11-2 Remote dual-system backup Solution .............................................................145
Figure 12-1 NetNumen U31 typical networking ...............................................................148
Figure 12-2 The single-Client and single-Server networking mode .....................................149
Figure 12-3 The multi-Client and single-Server networking mode .......................................149
Figure 12-4 NetNumen U31 centralized deployment .......................................................150
TABLES
Table 1-1 Manageable NE Type ...........................................................................................10
Table 3-1 NetNumen U31 Internal Interfaces ....................................................................29
Table 3-2 NetNumen U31 Northbound Interfaces .............................................................30
Table 4-1 Topology Management .........................................................................................31
Table 4-2 View Management ................................................................................................33
Table 4-3 Network Fault Monitoring ......................................................................................35
Table 4-4 Alarm message processing ..................................................................................36
Table 4-5 Failure diagnosis and elimination..........................................................................39
Table 4-6 Performance Task Management...........................................................................40
Table 4-7 Performance Report Output ..................................................................................41
Table 4-8 Security management function .............................................................................43

Table 4-9 Log management..................................................................................................44
Table 4-10 System management function ............................................................................45
Table 4-11 Task management function ................................................................................46
Table 4-12 Report management function..............................................................................47
Table 5-1 PTN Public Management ......................................................................................49
Table 5-2 PTN Interface Management ..................................................................................52
Table 5-3 PTN Protocol Management ..................................................................................54
Table 5-4 PTN Service Management....................................................................................57
Table 5-5 PTN Clock Management.......................................................................................58
Table 5-6 PTN OAM Management .......................................................................................59
Table 5-7 PTN QoS Management ........................................................................................60
Table 5-8 PTN Protection Management ...............................................................................61
Table 5-9 PTN Maintenance and Security Management.......................................................63
Table 6-1 MSTP single NE management function ................................................................67
Table 6-2 ASON Management Function ...............................................................................71
Table 6-3 MSTP Protection Subnet Function........................................................................73
Table 7-1 WDM/OTN Equipment Public Configuration .........................................................77
Table 7-2 WDM/OTN Equipment APR-AOSD Management .................................................80
Table 7-3 WDM/OTN Equipment Power Management .........................................................81
Table 7-4 WDM/OTN Equipment Spectrum Management ....................................................83
Table 7-5 WDM/OTN Equipment Wavelength Management .................................................83
Table 7-6 WDM/OTN Equipment Protection Configuration ...................................................84
Table 7-7 WDM/OTN Equipment Other Interface & Module Configuration............................86
Table 7-8 WDM/OTN Equipment Maintenance .....................................................................89
Table 7-9 WASON Configuration ..........................................................................................90
Table 8-1 Resource Configuration ........................................................................................98
Table 8-2 Rack monitoring function ....................................................................................100
Table 8-3 Performance data monitoring function ................................................................100
Table 8-4 File management function ..................................................................................102
Table 8-5 IP Network TE Management ............................................................................106

Table 8-6 IP Network MPLS VPN Management ...............................................................107
Table 8-7 IP Network VLAN Management ..........................................................................109
Table 8-8 IP Network ZESR/ZESS Service Management ...................................................110
Table 8-9 IP Network Cluster Service Management ...........................................................114
Table 9-1 E2E Service Customer Management ..................................................................115
Table 9-2 PTN Service Management Functions .................................................................115
Table 9-3 MSTP Service Management Functions...............................................................120
Table 9-4 MSTP Ethernet Service Management Functions ................................................124
Table 9-5 WDM/OTN E2E Service Management Functions................................................128
Table 9-6 IP E2E management function...........................................................................132
Table 9-7 PTN and IP cross-domain E2E service management .......................................135
Table 9-8 PTN and MSTP cross-domain E2E service management ................................135
Table 9-9 MSTP and OTN/WDM cross-domain E2E service management ......................136
Table 9-10 Cross-domain E2E service management of CTN andOTN/WDM ...................137
Table 12-1 Bandwidth requirements ...................................................................................151
Table 13-1 Rapid table of equivalent NE ............................................................................155
Table 13-2 NetNumen U31 Scale and Configuration.......................................................160
Table 13-3 NetNumen U31 Scale and Configuration.......................................................160
Table 13-4 Temperature and humidity index ......................................................................163
Overview
1.1
Network Operation & Maintenance Trend

With the development of ALL IP technology and the tremendous transformation in
telecom industry, broadband, mobility and convergence become the mainstream trends
in telecom network. ALL IP network structure requires that OAM (Operation,
Administration and Maintenance) tends to be flat to reduce OPEX and raise efficiency.
To follow the future network development trend, ZTE launched the unified network
management system NetNumen U31. NetNumen U31(BN) manages the bearer
network equipment. U31 can manage multi-domain equipment, integrate NE-layer and
network-layer management, and break hierarchical management mode to meet the
requirements of flat management.
1.2
Brief Introduction
NetNumen U31 adopts the distributed, multi-process and modular design. It can
manage all ZTEs optical transport products. It has such management function as
configuration management, fault management, performance management, maintenance
management, path management, security management, system management and report
management. While assuring transport equipment functions, it can manage and control
NE and regional networks.
The system adopts multiple network management technologies, follow ITU-T TMN ideas
in design and R&D and collect industry-leading NM software development experiences to
provide powerful management and flexible networking.
1.3
Product Positioning
NetNumen U31 (BN), the management platform of ZTEs BN products, can manage
SDH, MSTP, PTN, WDM/OTN and IP equipments (router and switch). U31 is the new
generation network management system at NE management layer/subnet management

layer and has powerful NE-layer and network-layer management functions.
In the TMN hierarchy, the U31 is located between the element management layer and
network management layer, and supports all functions of the NE and network layers. The
network position of the U31 is showed as follow.
Figure 1-1 ZTE NetNumen U31(BN)
NMS/OSS
OSS
NBI
NBI
EMS
NetNumen U31
NetNumen U31
Element Layer
IP Network
PTN
1.4
Router
BAS
WDM/OTN
SDH/MSTP
Swtich
Manageable NE Type
NetNumen U31(BN) manages ZTEs BN MSTP, CTN, WDM/OTN and IP products.
Table 1-1 Manageable NE Type

NE
NE name
product
Router
10
ZXR10 T8000-16
NE
NE name
product
product
ZXR10 M6000-8/ M6000-16

ZXR10 M6000-3S/ M6000-5S/M6000-8S
ZXR10 T1200/T1200 BMSG/ ZXR10 T600/ T600 BMSG
ZXR10 T1212/ T1216
ZXR10 T128/ T64E
ZXR10 GER/GER04/GER02
ZXR10 1809/1822/1822E/1842/1842R
ZXR10 2822/2822R/2842/2842R/2882/2882R/2884
ZXR10 3822/3842/3844/3882/3884
ZXR10 T16S/T16C/T32C/T64C/T160
ZXR10 GAR2604/2608/3608/7208
High/med
ZXR10 8905/8908/8912 /8905E/8908E/8912E
ium-end
ZXR10 8902 /8902E
switch
ZXR10 6905/6908
ZXR10 6902
ZXR10 T40G/T64G/T160G/T240G
ZXR10 5116E/5128E/5128E-FI/5152/5224/5228/5228-FI/
5252/5916E/5928/5928-FI/5928-PS/5928E/5928E-FI/5952/59
52E
ZXR10 5250-52TM
ZXR10
5950-24T/5950-28PM/5950-28SM/5950-28TM/5950-48T/5950
-52TM
ZXR10 5228A/5252A
ZXR10
3928A/3928A-FI/3928A-PS/3952A/3228A/3228A-EI/3228A-FI/
3252A/ZXR10
3950-28PM/3950-28SM/3950-28TM/3950-52TS
ZXR10 3206/
3226/3228/3226-FI/3252/3906/3928/3928E/3928E-FI/3952/39
52E
ZXR10 59S STACK
11
NE
NE name
product
Low-end
ZXR10 5109/5116/5116-FI/5116-SI/5124/5124-FI/5124-SI
switch
ZXR10 5250-24T
ZXR10 5009
ZXR10 2920-SI/2928-SI/2952-SI/2936-FI
ZXR10 2909-SI/2909-FU/2918-SI/2926-SI
ZXR10 2609-LE/2818S-LE/2826S-LE/2852S-LE
ZXR10 2609A/2618A/2626A/2826A/2826A-PS
ZXR10 2609/2609-FU
ZXR10 2809/2809-FU/2818S/ 2826S/2852S
ZXR10
2850-9TS/2850-9TT/2850-18TM/2850-26TM/2850-52TC
ZXR10 2826E/2618/2626
ZXR10 2609-EI/2818S-EI/2826S-EI
ZXR10 2910E-PS/2918E/2918E-PS/2928E/2928E-PS/2952E
ZXR10
2950-10PC/2950-18PC/2950-18TC/2950-28TC/2950-52TS
ZXR10 29S STACK
UAS
ZXUAS 10800E
product
ZXUAS 10800
ZXUAS 10400/10600/2500S
MSTP
ZXMP S100
product
ZXMP S150
ZXMP S200
ZXMP S320
ZXMP S325
ZXMP S330
ZXMP S380/S390
ZXMP S360
ZXMP S385
ZXONE 5800/ZXONE 5800-E
PTN
12
ZXCTN 6100
NE
NE name
product
product
ZXCTN 6110
ZXCTN 6120
ZXCTN 6130
ZXCTN 6200
ZXCTN 6220
ZXCTN 6300
ZXCTN 6320
ZXCTN 9002
ZXCTN 9004
ZXCTN 9008
ZXWM 32(V1.1)
ZXMP M600
ZXMP M800
ZXWM M900
WDM/OT
N product
ZXMP M820
ZXWM M920
ZXMP M720
ZXMP M721
ZXONE 8000
13
System Characteristics
2.1
Unified Network Management

NetNumen U31 uses the software system to enhance convergence management,
improve scalability and feasibility, and build the client-centered, future-oriented new
generation management system. U31 can manage SDH, MSTP, CTN, WDM/OTN and IP
equipment (router and switch), and support unified service, alarm and performance
monitoring and management.
2.2
Advanced architecture and high scalability
2.2.1
Powerful device management capability

NetNumen U31 adopts the distributed architecture and has powerful flexibility and
scalability. Client, server and database may run in one computer or in different ones.
Servers support process distribution and computer distribution according to network
characteristics and scale to get the best network management status. Distributed design
greatly extends network management capability by configuring hardware resources to
extend the manageable networks.
2.2.2
Flexible Plug-in design

NetNumen U31 core supports the plug-in design and arbitrary distribution of functional
components. The plug-in design has strong scalability. With the plug-in design, U31
provide the distributed management of server modules to improve management and
facilitate operation.
NetNumen U31 kernel adopts plug-in design, enabling plug-in loading. The functional
components can be distributed arbitrarily via loading plug-ins. Plug-in design features
robust scalability and supports customization.
14
2.3
Networking advantages
2.3.1
Flexible networking function

NetNumen U31 is based on client/server/Adapter structure. The components are
deployed separately and connected remotely to provide flexible networking.
2.3.2
Powerful management scale

NetNumen U31 can manage up to 20000 equivalent NEs, and support at most 200
clients. It assures large-scale network management and reduce carrier CAPEX in the
expansion.
2.4
Standard northbound interface

Support SNMP interface in compliance with SNMPv1, SNMPv2 and SNMPv3.
Support CORBA interface in compliance with TMF 814.
Support FTP interface.
Support TL1 interface in compliance with Bellcore GR-831.
Support XML interface which based on MTOSI V2.0.
It has completed the integration with the third-party systems from IBM Tivoli
Netcool/OMNIbus, HP TeMIP, Accenture NOVA, Infovista, Bright Oceans Corporation,
Guoxin Lucent, Datang Telecom, Beijing Metarnet and Shenyang Langchao to facilitate
OSS application of carriers.
15
2.5
Service deployment advantages
2.5.1
Public Service Deployment Advantages
2.5.1.1
Fast End-To-End (E2E) service deployment

NetNumen U31 supports perfect service E2E management and fast service
dispatching & monitoring.
It supports circuit management, e.g., service configuration and maintenance
management, service adjustment and service performance alarm management. It
provides the users with fast, convenient and safe E2E service management.
2.5.1.2
Unified service management

NetNumen U31 provides unified management for various services including tunnel,
GRE tunnel, PW, MS PW, TDM, Ethernet, ATM, L2VPN (VPWS/VPLS), L3 VPN, WDM
and OAC services in the service view, so that the operators need not change operation
interfaces frequently upon service management and maintenance. This function can
keep the maintenance habits for different services unified and reduce maintenance cost
and difficulty.
2.5.1.3
Powerful cross-domain service management capability

NetNumen U31 network management system provides CTN and IP cross-domain
service management, CTN and MSTP cross-domain service management, as well as
CTN/MSTP and WDM/OTN cross-domain service management, providing perfect
solution for E2E management of hybrid networking.
2.5.2
16
Advantages of CTN device service deployment
2.5.2.1
Convenient service navigation

NetNumen U31 provides convenient service navigation function. The users can be
easily navigated to the related service management interface from typology, alarm and
performance views, which make fault location, service query and maintenance
convenient and fast.
It provides service navigation at different levels such as NE, board, port, tunnel, PW and
client layer in the physical typology view; it provides alarm and performance-related
service query function in alarm and performance views; it provides fast navigation for
client lease service in user management interface.
2.5.2.2
One-button service creation tool

The one-button service creation tool facilitates service provisioning. The user only
needs to click E2E service creation without tunnel and PW configuration in advance, the
tunnel and PW will be created automatically upon service creation, which highly
simplifies the workload of service provisioning.
2.5.2.3
Convenient and safe capacity expansion/shrinking, function

NetNumen U31 offers intelligent, safe capacity expansion/shrinking function, can be
more convenient in the current implementation of network capacity expansion
contraction.
The wizard mode can modify the configuration automatically. This function makes the
operation more intelligent and simple without interrupting the service.
The function supports linear, ring and dual homing protection etc, and supports all
current versions of PTN equipment. In addition to automatic generate a variety of data,
U31 supports customize the data after being modified. Such as: new interface VLAN and
IP customization, the new MEG name, the name of the protection group customization.
17
2.5.2.4
Smart and reliable service cut-over function

NetNumen U31 offers smart, convenient, safe and reliable service cut-over function.
Friendly and personalized service cut-over interface can greatly reduce the network
operation and maintenance complexity.
A variety of cutover strategies such as rollback cut-over, cut-over as much as possible,
stop when encounter error ensure the process smooth.
The check function before cut-over and rollback ensures the effectiveness and accuracy.
After cut-over, data synchronization allows the consistency of data to be guaranteed. If
the cut-over fails, the data and configuration will be automatically recovered, ensuring
network security and reliability.
2.5.2.5
Flexible port migration function

NetNumen U31 Supports flexible port service migration function. Service on a specific
port can be migrated to the alternate port, in order to quickly restore service.
After the service opened, due to port damage, service restructuring and other reasons,
the board cannot be replaced (such as multi-port on a single-board, other ports in the
normal use, and there are free ports, the user may save cost, not ready to replace the
board, etc.) it cannot be replaced, in such cases, users can migrate the service to the
alternate port, to quickly resume service.
2.5.2.6
Convenient link capacities upgrade capability

NetNumen U31 supports convenient link capacity upgrade capability. After the service
opened, due to enhance the network service capacity, need to upgrade the existing
network link capacity. For PTN, the physical link using the Ethernet interface, physical
link capacity upgrades to support the following Ethernet link capacity upgrade: FE->GE
GE->10GEFE->10GE.
18
2.5.3
Advantages of IP device service deployment
2.5.3.1
Human Deployment Interface

Human interface design is implemented for hardware configuration, L2 configuration, L3
configuration, and service deployment. The deployment of different service functions is
displayed in the way similar to webpage browser tab. Each tab lists details of services,
shows service topology in graphs, and shows the change history of the service.
Fast service relation navigation is provided for each service configuration. For example,
VPN service can be quickly navigated to the correlated interface, VLAN, tunnel, AC, and
PW configuration. Its easy for user to take switching, which improves deployment
efficiency.
2.5.3.2
Offline pre-configuration improves network reliability

It provides two flexible configurations: offline configuration and online configuration. It
provides resource synchronization view before the configuration to effectively avoid
man-made conflict and mistake. It takes checking and auditing after configuration to
guarantee reliable operation of the network element. Once any device in the network is
detached, the original configuration information of the device can be checked offline to
realize quick positioning of device failure so as to improve the maintainability. At the
same time offline configuration can be implemented firstly during the process of initial
construction and expansion. Distribution of configuration data after multi-directional can
improve security and reliability.
2.5.3.3
Complete service deployment strategy

It provides continuous service configuration. It supports batch service distribution,
improves deployment efficiency and provides incremental deployment. Deployment of
some non-key configuration will not influence the current services, which guarantees
non-stop online services. It provides flexible deployment time strategy, supports regular
deployment, scheduled deployment and one-time deployment, which can avoid the
influence of service peak on the network to the best.
19
2.6
Value-added function advantages
2.6.1
Advantages of public value-added functions
2.6.1.1
Flexible offline configuration

NetNumen U31 supports flexible equipment configuration, online or offline. When
network equipment is disconnected with U31, U31 checks the original configuration
information in the offline way to locate quickly equipment fault and improve
maintainability. In the initial and expansion stage, it is suggested to configure the
equipment in the offline way, then make all-round check and finally send out
configuration data, which will improve security and reliability.
2.6.1.2
Remote, online software upgrade

NetNumen U31 can remotely download and upgrade NCP software/card software in
the FTP way. This way affects no services, facilitates system maintenance and upgrade,
and ensures upgrade reliability.
2.6.1.3
Intelligent fault analysis and diagnosis

NetNumen U31 has the industry-leading alarm correlation analysis system which can
automatically analyze and locate root alarm and derived alarm according to network
resources and service relations to shorten the troubleshooting time. The diverse
association and navigation between network alarms and service data help the user to
know and evaluate network conditions quickly. Meanwhile, VIP services can b configured
with independent fault prompting and processing to offer differentiated service for
different users.
2.6.1.4
Powerful resource view

NetNumen U31 Supports powerful resource view. This view presents the MPLS
related resource view, display configuration and actual views, can present ports, tunnels
and pseudo-line bandwidth usage statistics. According topology map showing the
20
physical link bandwidth usage information, you can view several links or network
elements at the same time.
Customized bandwidth utilization threshold setting function, can be idle, low, medium,
high, full utilization levels. And distinguish various grades by colors; allow the user to the
utilization of the bandwidth at a glance. The statistical analysis can be output by the
report mode.
2.6.1.5
A Variety of Statistics, Analysis and Report Management Functions

NetNumen U31 supports plentiful report management: Report functions includes
report template, report schedule management. User can define his own output templates
according to demand and make timing schedule to generate output report.
As IP equipment supports WEB report, performance monitoring reported can be viewed
remotely at once without client. And there are a variety of flexible report views.
2.6.1.6
Flexible time zones, daylight saving time display function

NetNumen U31 supports multiple time zones and daylight savings time, the client and
server and device time can be unified display. Client, server and equipment can be
divided in different time zones, and the situation in some areas use Daylight Saving Time
use, ease of equipment maintenance.
NetNumen U31 supports three time zones: only daylight saving time, the UTC time
zones, and daylight saving time. Three times way can be set according to the needs of
users, requires prior planning, can be set when software installation.
2.6.2
Advantages of CTN device value-added functions
2.6.2.1
Plug and Play zero-touch deployment

In the initial network installation and deployment stage, the equipment can obtain
initialization information automatically to achieve remote management and maintenance
without manual operation. The easy zero-touch deployment function effectively improves
maintenance efficiency and reduces maintenance cost.
21
2.6.2.2
Distinctive channel view

The distinctive channel view design can completely display the status of board ports,
tunnels, PWs and services. The users can be clear about all the resources in the board
and the maintenance on ports, tunnels, PWs and services is convenient and fast.
2.6.2.3
Advanced preventive maintenance design

NetNumen U31 can set reference value, optimal threshold and maximum working
threshold for such major performances as optical power, so as to get real time equipment
run status.
NetNumen U31 has intelligent performance analysis system. It can automatically
analyze history performance data to find out dormant troubles in advance. It can also
provide timing cancellation function for loopback and ALS affecting normal operation to
reduce human errors.
2.6.2.4
Intelligent inspection tool

NetNumen U31 supports remote and centralized equipment inspection with inspection
reports. This service simplifies inspection process and saves human resource greatly.
2.6.3
Advantages of OTN device value-added functions
2.6.3.1
Clear OTN signal flow chart

With signal flow chart, users can easily check OTN signal flow of the cards on the
network element, obtain the connection information of the ports on the cards, and
accurately catch the card alarm.
2.6.3.2
Powerful OTN APO Sub-system

For OTN equipment, APO subsystem provides manual power optimization and automatic
power optimization, to implement network power optimization triggered by command and
automatic power management triggered by timing. The subsystem guarantees gain
attenuation and optimization of the multiplexing section and channel optical
22
signal-noise-ratio optimization for the receiver of channel layer power management

through advanced algorithms.
2.6.3.3
Intelligent OTN APC Sub-system

For OTN equipment, APC (automatic protection control) subsystem is used when optical
power is lost in an optical transmission segment in OTN main optical channel. The
system automatically reduces or turns off the output optical power of the sender to make
sure its safe for the maintenance staffs eyes, so that the fiber optical power meets the
security level requirements.
NetNumen U31 system provides centralized management capabilities of APR-APSD
protection group, which can automatically detect the actuator and monitor port
information. its easy and quick to configure.
2.6.3.4
Distinctive channel view

The distinctive channel view design can completely display the status of board ports and
services. The users can be clear about all the resources in the board and the
maintenance on ports and services is convenient and fast.
2.6.3.5
Advanced preventive maintenance design

NetNumen U31 can set reference value, optimal threshold and maximum working
threshold for such major performances as optical power, so as to get real time equipment
run status.
NetNumen U31 has intelligent performance analysis system. It can automatically
analyze history performance data to find out dormant troubles in advance. It can also
provide timing cancellation function for loopback and ALS affecting normal operation to
reduce human errors.
23
2.6.4
Advantages of IP device value-added functions
2.6.4.1
Plug and Play zero-touch deployment

In the initial network installation and deployment stage, the equipment can obtain
initialization information automatically to achieve remote management and maintenance
without manual operation. The easy zero-touch deployment function effectively improves
maintenance efficiency and reduces maintenance cost.
2.6.4.2
Intelligent inspection tool

NetNumen U31 supports remote and centralized equipment inspection with inspection
reports, which provide the detailed information and problems for each device in an
intelligent way, as well as scores for the health. This service simplifies inspection process
and saves human resource greatly.
2.6.4.3
Flexible and various WEB network performance analysis

Working with external tool, NetNumen U31 supports WEB network performance
analysis and report for IP device. It can provide network administrator with efficient and
clear network performance and quality analysis and monitoring tool with direct Web
interface, compact combination of view, instrument panel chart, flexible data model,
end-to-end measurement management, accurate quantitative data, and rich preset
report templates. It can collect, aggregate, process, store the resource performance data
in IP network to realize the transfer from data to knowledge and to wisdom.
2.7
Security advantage
2.7.1
High available back-up routine

NM access to several gateway NEs, which makes NM has back-up routine. As far as the
chain mode system is concerned, NM information can communicate through back-up
DCN network, when ECC channel is cut off., so that there will be no influence on the
management of NM to NEs, which can improve the reliability of NMS.
24
2.7.2
Triple-level security mechanism

NetNumen U31 has 3-level safety mechanism. It has the corresponding safety
measures for client, server and Adapter. It has strong safety (client and server interfaces
support SSL and TLS protocols). It supports AAA certification and Radius safety
certification (Radius certification: support PAP and CHAP password certification protocol
and LDAP directory access protocol).
2.7.3
Perfect data consistency protection

Employing the database backup and synchronization mechanism, NetNumen U31
features the excellent security and ensures the data consistency.
For multi-Client /multi-Manager-DB, the locking mechanism and the data

synchronization mechanism assure the synchronization and data consistency
among multiple Clients and among multiple Managers.
Provide active/standby NM to keep the data consistent among several server

components.
Support EMS synchronization in LCT data modification.
It also supports the database uploading and downloading.
The data synchronization, subject to Agent data or U31 data.
25
System Architecture
3.1
System Hardware Structure

NetNumen U31 adopts client/server mode. One NetNumen U31 has one server and
several clients connected to the server. NetNumen U31 server runs on Windows or
Solaris to process and store NE data. NetNumen U31 client run on Windows to provide
the user with GUI. The user operates and maintains NE via the client.
Figure 3-1 NetNumen U31 hardware Structure
As shown above, NetNumen U31 hardware includes server, disk array, client, alarm
box, switch, router, etc. The printer, speaker box and backup device are optional for the
user.
1.
26
Server
Server is the core of NetNumen U31. NetNumen U31 server exchanges the
information with NE, fulfills relative functions and sends back the results to client.
NetNumen U31 server exchanges the information with upper-layer NM via
northbound interface. NetNumen U31 server is divided into application server and
database server according to functions. The servers share the load together or
independently; they share together by default. NetNumen U31 is configured with
one server or two servers (in active/standby mode) to form HA (High Availability)
system.
Server can adopt Windows server or SUN Solaris server.
2.
Client
NetNumen U31 client provides front-end device for different users. NetNumen
U31 supports multi-client, and operates and manages its NE. The user manages its
NE via client, and supervises and manages NetNumen U31. According to
physical location of the connected server and managed NE, It can be divided into:
i.
Local client: Client and server are in one LAN.
ii.
Remote client: NE and server are in one LAN, but client and server are in
different LANs, that is, in remote LAN.
iii.
Return client: Another form of remote client. NE and server are in one LAN, but
server is in remote LAN.
3.
Network equipment
It is used for network connection between NetNumen U31 and NE equipment or
upper-layer NM. It includes switch, router, etc.
4.
Outsourced device
It includes printer, speaker box, etc.
27
3.2
System Software Structure

NetNumen U31 adopts advanced software structure, including: client, server, adopter,
and database. See in following figure.
Figure 3-2 NetNumen U31 Software Structure
NE
Management
Inventory
Management
E2E
Management
Perfo
rman
ce
Alar
m
Network
Management
Report
Management
NBI Module
Ser
ver
Protection
View
Data Subne
base twork
Mana
ger
Client
Alar
m
Adapter
IP Network
3.2.1
Datab
ase
...
Perfo
rman
ce
Data
base
Subne Ad
twork apt
Mana er
ger
Adapter
MSTP
Network
WDM
Network
PTN
Network
Client
Client GUI shows the processing results of software system in graphics to users.
NetNumen U31 adopts the thin client design and supports large-scale network
management and good platform portability. It has the following functions:
1.
Provides a graphic interface for the user.
2.
Provides
various
management
interfaces
for
operator,
i.e.,
configuration
management, fault management, performance management, security management,

maintenance management, system management and help system.
28
3.
3.2.2
User security control.
Server
Server OSF component is the body fulfilling network-level NM function and adding values
to service function.
3.2.3
Database
The database is the main body to storage data, and query data.
3.3
System Interfaces
3.3.1
Internal Interfaces
Internal interfaces are used for data communication between U31 internal components.
For details, refer to Table 3-1.
Table 3-1 NetNumen U31 Internal Interfaces
Interface name
F interface
Interface description
The interfaces between client components and server
components and between server components are
private interfaces. F interface adopts Ethernet (emulate
in the same PC) and uses TCP/IP for Ethernet.
3.3.2
Southbound Interfaces
Southbound interfaces are used for data communication between U31 and equipment.
The system supports such southbound interfaces as SNMP, Syslog, Telnet/SSH,
FTP/TFTP and private interface.
3.3.3
Northbound Interfaces
Northbound interfaces are used for data communication between U31 and external
system. U31 offers a variety of alarm, performance and resource information for OSS via
29
open-standard northbound interfaces. Via northbound interfaces they are integrated into
different OSS to meet different OSS demands.
Northbound interfaces are shown in Table 3-2:
Table 3-2 NetNumen U31 Northbound Interfaces

Interface
Interface description
name
CORBA
Provide OSS with such functions as resource/inventory,
interface
fault, performance and service management for

MSTP/CTN/OTN, and fault management for IP.
SNMP interface
Provide OSS with such functions as fault management.
FTP interface
Provide OSS with such functions as resource/inventory

and performance.
TL1 interface
Provide OSS with such functions as IP equipment

configuration management and resource management.
Provide OSS with such functions as transport equipment
XML interface
resource management, alarm management and

performance management.
3.4
System Running Platform

NetNumen U31 supports Windows + MS SQL Server or Solaris + Oracle.
30
System Basic Features
4.1
Topology Management
Topology Management provides the topology view of the whole network. It enables users
to scan network key data and information on a complete and clear interface. The
topology view shows NEs, their links and their alarms. It displays all these information in
a direct way and bright colors, which makes the users get a general picture of the
network with a quick glance.
NetNumen U31 network management system supports hierarchical topology structure
to show the whole network. Its specific functions are as follows:
Table 4-1 Topology Management

Functions
Description
Layout of topology
Topology management view interface is composed of four parts
management
of views: topology tree (navigation tree), topology diagram, hide
interface
legend/bird view, and alarm/performance table.

1. It supports hierarchical topology management. Users can get
linked to lower layer topology view from high layer topology
view. The contents displayed by the topology logic view are: NE
objects indicated by icons, logic relationship between NEs
indicated by lines, NE and link state indicated by tags, bubbles,
or small state icons.
Logic view of
2. Topology view filtering: it implements filtering according to
topology
filtering tree based on different conditions such as name and

address.
3. Expansion and contraction of topology view and its nodes
4. Topology area provides table display
5. Links displayed on the topology view
6. Multiple management views based on different equipment
type, positions, and IP.
31
Functions
Description
1. Select/move NE, zoom in/out view, undo/restore view, show
all topology, zoom in for area, lock NE position, network layout
setting (grid/ring/hub-spoke), save NE position, NE searching,
full screen, turn to/backward/forward, show in list, filter, legend,
contents setting, bird view, configuration map, and customize
interface elements.
Operation based on
2. Export of topology data
logic view of topology
3. SNMP V3 parameter configuration

4. Setting of poll parameter and automatic discovery parameter
5. Refreshing of topology data
6. Import and export of interface style
7. Statistics of topology information
8. Import and export of topology data
1. Alarm message is shown on the topology view, which is
Alarm message
correlated to NE and link.

2. The list below the view shows alarm message.
Performance
message
The list below the view shows performance KPI.

1. Create groups based on types and regions.
2. Create groups in batches or one by one.
Operation for groups
3. Set group creating rules (based on IP/position/type)

4. Set group members
5. Group information statistics
6. Duplicate and paste groups
NE operation
Create, modify, delete and move NEs.

Create NEs in batches.
Link operation
Create, modify and delete links
Automatic discovery
Automatic discovery of NE and links

Support adding the current typology diagram to Favorites,
helping the user to locate it fast.
Typology diagrams include: the current layer, scaling, view
Favorites
range of typology diagram, legend display switch and

figure/table display mode. Click the Favorites menu, the current
typology window will be displayed in the style as you collect.
Support arranging Favorites, such as creating a folder, deleting
a Favorite item and modifying the name.
32
4.2
View Management
NetNumen U31 provides all-sided view management to provide graphic information for
operators. Following view management functions are available on NetNumen U31:
Table 4-2 View Management

Functions
Description
Physical View: view, create, delete, modify the physical equipments
in the entire network, and perform relevant configurations for
physical equipments. Implement display filtering for topology
display, create customized physical view.
In protection view, the protection can be viewed, created, deleted
and modified according to protection subnet. Various protections
can be configured with PTN tunnel, PW, MSP, TMS, protection
switching, APS start/end and SD threshold.
Service View: view, create, delete and modify all services
Clock source view: View current configuration and real-time status
of clock source of all-network NEs.
Time view: View 1588 clock and the time of all-network NEs.
View
Management
Clock SSM: Configure clock source, current clock source query,

SSM, clock synchronous network boundary compatibility, clock
source switching, protection blocking, WTR clearance, protection
switching/restoration time, external clock export, current export
clock source query, external clock SA byte, and S1 byte transport.
Support background color and diagram modification, province or city
map invocation, specific map adding by the user, topology diagram
saving & locking, screen protection, topology diagram zoom out/in
and recovery, and provide micro-diagram locating, NE or service
status and alarm display in topology diagram, NE discovery and
locating.
Status information query, adding up alarm, event, maintenance
status information of NetNumen U31 NM. When configurations
and data mentioned above change, it can offer dynamic prompt and
query navigating functions via unified status bar interface, enabling
users to supervise the sensitive data with ease.
33
Functions
Description
Resource veiw:
The resource view subsystem is used in three scenarios:
transmission device, transmission device + IP device, and only data
device. Resource view related to MPLS is displayed.
The resource view can be divided into three parts: topology control,
resource view and resource statistics.
Topology monitoring
Include physical topology, tunnel topology and the topology of
pseudo-wire. Link, tunnels and pseudo-line configuration bandwidth
consumption and the actual bandwidth occupied can be checked by
the topology on the monitor; according to user-defined threshold,
rendering the color of the corresponding topological elements.
Resource View
According specific resources for the particle size show the resource
usage. Specific port bandwidth usage, bandwidth usage of tunnels,
network elements, and physical resource utilization can be checked
on this view. The user can view the results saved as an Excel file,
you can save the query.
Resource statistics
Different from view resources, resource statistics is in high
granularity of the statistics, in line with the amount of resources in
certain conditions. Such as the statistical distribution of the network
element type, the distribution of the board type, the number of port
which bandwidth occupied 50%. Users can save the statistical
results as an Excel, you can save the statistical conditions.
4.3
Fault Management
Fault management mainly receives various realtime equipment alarm and network event
reports reported by all network elements in the whole network. It notifies the maintenance
staff in a realtime, audible, visual and direct way to let the users know about the
abnormal operation state of the network and equipment. It helps the staff to locate the
failure cause and position so that the users can discover as soon as possible, deal with
the failure and solve it as soon as possible to guarantee normal operation of the system.
Alarm management unit receives and processes the alarm reported by the equipment
and display it to the users via the interface. It can also forward it to the designated
34
objective by email or short message. The maintenance staff processes it when they
confirm. All the alarm reports collected are saved in the base for various alarm statistics
and query.
4.3.1
Network Fault Monitoring

NetNumen U31 network management system provides perfect network monitoring,
permitting the network provider to learn whether the network works as expected. It traces
the current state and makes the state visual to users.
Table 4-3 Network Fault Monitoring

Function
Description
Alarm type conforms to ITU-T X.733 standard including
Alarm type
communication alarm, equipment alarm, quality of service

alarm, processing error alarm, environmental alarm, and
network management system alarm.
Alarm message is automatically reported in SNMP TRAP
message. Network management system can automatically
receive various real-time alarms reported by all network
elements with the alarm parameters including confirmed alarm
state, level, network element position, location position in
Alarm parameter
network element, alarm code, occurring time, network element

type, alarm type, alarm reason, additional text, product, alarm
sign, service information, service location, alarm modification
time, additional content, acknowledge/unacknowledged user,
acknowledge/unacknowledged system, and
acknowledge/unacknowledged time.
Network management system can monitor itself; generate
NM system alarm
system alarms such as performance alarm and system

management alarm based on thresholds of some preset
operation parameters.
4.3.2
Alarm Message Processing

NetNumen U31 network management system can collect and maintain the generated
alarms, and make alarm and network state visual to users.
35
Table 4-4 Alarm message processing

Function
Description
Users observe realtime alarm on the network topology. There
are obvious alarm signs on the network element topology for
users to enter the next level, and down to rack state figure.
These alarm signs will automatically disappear when alarm
recovers.
Alarm display
When there are multiple alarms occur at one network node, the
icon color should be the same with the current highest level
alarm. When the alarm with the higher level is cleared, the next
higher level alarm is displayed in turn.
Alarm levels can be distinguished based on different colors.
They can be divided into critical alarm, major alarm, minor
alarm and warning alarm.
Display all detailed alarm information reported by each network
element in the alarm list and update it regularly.
Alarm list contains confirm state, alarm level, network element,
location inside network element, alarm code, occurring time,
network element type, alarm type, alarm cause, additional text,
Alarm monitoring list
product, alarm sign, service information, service position, alarm

modification time, additional content, confirm/reconfirm user,
confirm/reconfirm system, confirm/reconfirm time, alarm notes,
note user, note system, note time, alarm No., network element
IP, link, network element group, network element agent,
equipment type, and path name. The list can be customized.
Display all detailed notification information reported by each
network element in the notification list and update it regularly.
Notification list contains network element, location inside
Notification
network element, notification code, occurring time, network
monitoring list
element type, product additional text, service information,

service position, additional content, network element IP,
network element group, network element agent, and equipment
type.
Export display column, export all columns, print, alarm
List operation
sound/mute setting, full screen, refresh, display column

customization, filter based on level or confirmed state, statistics
based on level
Alarm annotation
36
Support alarm annotation, namely, editing the remark

information of alarms
Function
Description
Confirmed alarm is paid attention to and may be processed by
Alarm confirm and
certain measures. But it doesnt mean the alarm is solved or
reconfirm
cleared.
Reconfirm the alarm to recover it to the state of unattended.
Alarm clearing
After manual clearing, the alarm is in cleared state; the user

can no longer care about this alarm.
After shielding configuration, the alarm will not be reported to
Alarm shielding
NM. Support setting the shielding state by resource and alarm

cause to shield the specified alarms.
Alarm forwarding
Support dispatching to corresponding maintenance staff by

short message or Email.
Alarm confirming rule, alarm clearing rule, alarm filtering rule,
alarm delay rule, alarm merging rule, alarm timing rule, alarm
Alarm rule
counting rule, alarm associating rule (based on network

element), alarm associating rule (based on network element
type), alarm forwarding rule, alarm blocking rule, and alarm
filtering rule.
Based on different alarms, set expert base of processing
Suggested setting for
suggestions involving specific cause, diagnosis, and
processing
processing.
Support import and export of processing suggestions.
Redefining of alarm
Modify levels for different types of alarms. Support four levels of
severity
critical, major, minor and warning.
Setting of alarm box
Set alarm box state, IP address, port, and level.

Fast query of all current alarms.
Fast query of unconfirmed current alarms.
Customized query: query conditions include position
Current alarm query
(equipment, rack, frame, slot, power supply, fan and port),

alarm code, alarm occurring time, alarm recovery time, alarm
confirm/reconfirm time, duration, alarm type, alarm type before
clearing, confirm state, confirm/reconfirm user name, additional
text and visibility.
37
Function
Description
Fast query of history alarm recovered during one day.
Fast query of history alarm recovered during three days.
History alarm query
(equipment, rack, frame, slot, power supply, fan, port), alarm

code, alarm occurring time, alarm recovery time, alarm
confirm/reconfirm time, duration, alarm type, alarm type before
clearing, confirm state, recovery, confirm/reconfirm user name,
clearing user, and additional text.
Fast query of history notification during one day.
Fast query of history notification during three days.
Notification query

(equipment, rack, frame, slot, power supply, fan and port),
notification code, occurring time (in section such as the latest T
week/day/hour/min), and additional text.
Statistics based on network element and network element type.
Take statistics based on alarm frequency or average duration.
Take statistics based on the objects.
Alarm statistics
Alarm statistics in busy hours.

Timing statistics task management
Timing output task management
Alarm forwarding
Customize alarm forwarding short message template and email
template
template.
Alarm
synchronization
Alarm sound and
light setting
Actively synchronize equipment alarm
Customize sound and color for different levels

Set alarm archiving when the alarms exceed the threshold. The
Alarm compression
and dumping
cycle and threshold of alarm archiving can be set. When the

alarms exceed the cycle or threshold, they can be deleted from
the database and compressed as external files automatically
for saving.
Alarm print/export
38
Support alarm print and export. The export formats supported

include XLS, TXT, HTML, pdf, csv and xml.
4.3.3
Failure Diagnosis and Elimination

NetNumen U31 network management system provides various failure diagnosis
measures and elimination processing suggestions to help the staff quickly location and
eliminate the failures.
Table 4-5 Failure diagnosis and elimination

Function
Description
One failure usually causes a series of alarms. For example,
plugging out of a cable will cause interruption of routing protocol
thus lead to interruption of user service. Failure root analysis of
Analysis on failure
relativity
NetNumen U31 can analyze the relativity between alarms in

an intelligent way, display root alarm and restrained alarms,
and display affected customer and service, make relativity
through each layer, and finally locate the root failure which
causes a series of alarms. Then it provides processing
suggestions for users to make diagnosis and elimination.
Based on long-term network operation, users can summarize
some processing experience from frequently occurred
problems for reference of similar problems in future. This
summary is expert base suggestions. NetNumenU31 network
Expert base
suggestions
management system provides users with functions of

importing, exporting, checking, and modifying alarm processing
suggestions to make the processing of alarms easier.
Meanwhile, NetNumen U31 network management provides
detailed reason, diagnosis and processing method for each
alarm. It helps users to take in-depth diagnosis of the network
to quickly eliminate the failure.
4.4
Performance Management
Performance management module is responsible for performance monitoring and
analysis of data network and equipment. By collecting various performance data from
network elements and generating performance reports after processing, this module
provides information for maintenance department and management department to guide
network engineering, planning and network adjustment and improve network operation
quality.
39
NetNumen U31 provides performance management with complete functions. It

monitors performance of the whole network by functions like performance task
customization, performance report output and performance threshold management.
4.4.1
Performance Task Management

The users can order different performance monitoring tasks according to the
performance variables they pay attention to. NetNumen U31 provides flexible task
customization modes:
Table 4-6 Performance Task Management

Function
Description
Performance Task
Take performance data collection by creating performance
Management
measurement task. It supports management of performance

measurement task.
Create measurement task.
Supports selection of measurement object and measurement
position.
Supports setting of starting time of performance task with the
fomat of yyyy-mm-dd hh:mm:ss.
Supports collection granularity of 5mins/15mins.
Supports setting of valid data (week and month) and valid
period (time) within the range of starting time of the
measurement task with the format of hh:mm:ss.
Counter and index management. Users can check performance
counter defined by the system. They can customize new index
based on certain calculation formula according to the existing
measurement index.
Query template management. It can customize condition and
regular task query. It can load the template when it queries
performance history data.
Performance data integrity query. It can query performance
data collection of each network element in each period.
40
4.4.2
Performance Report Output

NetNumen U31 collects performance data automatically according to the ordered
performance tasks, stores history data in the database and generates different
performance reports by analysis.
Table 4-7 Performance Report Output

Function
Description
All collected data can be displayed by graph or table
Performance historty data query granularities include 15 mins,
30 mins, 1 hour, 1 day, and 1 week.
Performance histroy data query periods include 1 day, 1 week,
and 1 month, holiday query, and customizing starting time and
ending time based on the format of yyyy-mm-dd hh:mm:ss.
It supports selection based on week and month for valid query
of performance history data. It supports customized period
based on the format of hh:mm:ss.
It supports saving of history performance data report in files so
that we can check at any time. The file formats of *.xml, *.prn,
*.txt, *.htm, *.pdf, *.xls, *.xlsx, and *.csv are supported.
Performance report
output
It supports printing of history performance data report we get.

Categorize and put the collected original performance data into
storage. It supports backup and deletion of the performance
data.
History performance data is automatically filed. It supports
automatic or manual filing of history performance data. It
supports setting of automatic filing period and threshold.
It supports TOP N packet query. In performance data query
filtering, it provides performance TOPN query.
It supports check of realtime performance. It supports two
collection granularities of 10 seconds and 1 minute. Realtime
performance data is saved in files with the format of *.txt and
*.csv.
41
4.4.3
Performance Threshold Management

The user can set high and low thresholds for the performance variable they are
concerned about by performance threshold management. When the collected
performance data exceeds the set threshold, the network management system will
generate threshold alarms automatically.
Besides, four levels of thresholds can be set, corresponding to four types of alarms;
threshold delta value can be set at the same time. For example, when the highest
threshold for critical alarm is set to 100 and the delta value is set to 2, the alarm is
generated only when the performance data is larger than 102, and the alarm is recovered
when the data is lower than 98.
Figure 4-1 Performance threshold schematic diagram
4.5
Security Management
Security management is used to ensure users legal use of system. Security
management realizes management on user, user group and role. It provides security
control for the operator to perform secure management operation by properly organizing
the relationship between user, user group and role; it prevents illegal user from entering
the system by login authentication; it provide security control for the operator to operate
by operation authentication.
42
Table 4-8 Security management function

Function
Description
The user can create, modify, copy and delete a role set as well
as assigning roles to a role set according to his rights.
Role management
The user can create, modify, copy and delete a role as well as
assigning operation rights to a role according to his rights.
The user can set role rights according to resource and
operation set. This is decentralized multi-domain management.
The user has attributes including ID, password, user validity
period, password validity period, and department. The
management functions supported include: add/delete user,
associate user and role or role set, configure user Profile and
modify user password.
Check user lock status.
View the information of the current login user, and tick the login
user off the system if necessary.
Blacklist management: the users entering the blacklist cannot
User management
log in the system.

Set validity period of user account
Set validity period of password
Set user working time and holiday, login IP range, and login
MAC binding
Set concurrent login number of the same user
Set maximal and minimal length of password
Set account lock upon login failure
Set automatic lock function
Department is a simulation of administrative department for the
convenience of user organization and management. The user
Department
can create department in department management as required.
management
By default there is a root department in the system; this

department is the supreme department and all other newly
created departments are its inferior sub-departments.
4.6
Log Management
Log Management:
43
Log management is used to manage various logs of the system. Log is recorded
information of various events and operations of the system. By viewing logs, the
user can know whether the system is running properly, locate the cause of problem,
trace and audit important events. Log management is an effective tool of the system
administrator to trace system running status, locate system fault and trace user
operations.
Table 4-9 Log management

Function
Description
Operation log record user access to the system, including
Operation log
access function module, operation process, operation time,

operation result, etc.
Security log
User login and logout information.

System and module run record, including system start, system
System log
exit, module run process, system interruption, module

interruption, etc.
Log query
System administrator can browse and query the record in

system log.
Log output
Output the log in the form of text or SYSLOG.
Log deletion
The system regularly deletes system logs.
Syslog log management can manage the operation log reported from the equipment.
Syslog message is a necessary means to ensure normal operation of the system
and is applied to the debugging and security check. Syslog management module of
NM software can fulfill the following function: Syslog filtering, receiving, resolution,
storage, query, statistics, customization deletion policy, file storage and printing,
and user receiving Syslog log from several equipments or operation systems.
Syslog message displays in GUI so that the user can easily check the logs of
different equipments or operation systems and deal with them.
44
4.7
System management
System management is used to manage NetNumen U31 NM system functions. With
system management, the user maintains NM system better. System management offers
a unified maintenance and management platform for NMs to monitor and maintain
application server and database server and manage database.
System management can monitor performance indexes of application server, e.g., server
CPU utilization rate, memory utilization rate and hard disk space, and set performance
parameter threshold. When performance index reaches the threshold, the alarm is sent.
System management can also monitor resource indexes of database server. For
example, when total database space exceeds the threshold, major alarm is sent; when
the spaces of monitored objects in the database exceed their threshold, the alarms at
different levels are sent; when these indexes are lower than the threshold again, alarm
information will return to normal.
System management can create database maintenance task, and regularly execute
such operations as data export, data import, and data clearance in the data table of the
database.
System management has the following common functions:
Table 4-10 System management function

Function
Server performance
management
Description
View server performance parameter (CPU, memory, hard disk,
server process, etc.), and set system threshold parameter and
server performance alarm.
The user has the following local database management
Database
management
function: database login, database resource view, database

backup, database restoration, data table backup, data table
restoration, data table clearance, database maintenance task,
regular database maintenance task, and database logout.
System data backup

and restoration
Provide backup and restoration of such data as log, alarm and

performance.
Provide database and file backup.
45
Function
Description
U31 has unique Favorite function, which is similar to IE
Favorite function, to offer fast link for frequently used
Other management
functions.
View the system time, print settings, system style settings,
screen lock settings, access control, window resizing, etc.
Use license to control server-side MAC address, authorized
License control
use period, number of user interface terminals, function

package module, northbound function package, device types
under management and specific function authorization.
4.8
Task management
It is also called policy management. A task is a predefined procedure in NM system and
specifies NM system actions under special conditions. With the predefined task, NM
system can automatically execute relative operation according to current run status for
automatic dispatching and protection, and system self-management for high efficiency
and facilitation.
Table 4-11 Task management function

Function
Description
Regularly execute backup and deletion task of log,
History data archive
performance and alarm data to prevent large volume of data in

database influencing the system.
Regularly execute basic data backup task. Backup all the basic
data of the network management system. Just backup data
Basic data backup
records excluding the history data such as table structure and

history alarms, notifications, logs, performance raw data
(history data the has individual backup function).
version and database

backup
File clearance
46
Regularly execute NM version file and database backup task.

Monitor data catalogs of different types, and regularly execute
clearance task when the index exceeds the threshold.
Function
Automatic
confirmation of
history alarm
Description
It is used to automatically confirm history alarm before the set
days to avoid manual way, so as to improve the maintainability.
Regularly execute IP NE resource collection task. It supports It
IP NE resource
supports regular implementation based on
collection
hour/day/week/month and one-time implementation. It supports

setting of starting time of the tasks.
4.9
Report management
Report Management is mainly used for output of data concerned by users in the mode of
reports, and provides view and print functions.
Table 4-12 Report management function

Function
Description
SDH: provide service data report, service statistics report,
optical link utilization rate report and isolated cross-connect
report.
Service report
PTN: provide service data report and service statistics report.

OTN: provide service data report, service statistics report, and
whole-network power adjustable margin report.
SDH: support resource statistics reports on NE configuration,
board configuration, boards, connection, port status, device
types, protection group information, service cross-connect
configuration and optical module information.
PTN: support resource statistics reports on NE configuration,
board configuration, boards, connection, port status, device
Resource report
types, protection group information, service cross-connect

configuration and optical module information.
OTN: support resource statistics reports on NE configuration,
boards, connection, port status, device types, protection group
information, service cross-connect configuration and
management module information as well as board component
information report, subrack information report and board
configuration report.
47
Alarm report
Performance report
48
Provide basic history alarm statistics report and busy hour

history alarm statistics report.
Provide performance data report
PTN Management
This chapter introduces the management function set of PTN NE layer, including NE
attributes, service, OAM, QOS, protection and clock functions.
5.1
PTN Public Management

Table 5-1 PTN Public Management
Function
Description
Support creating network elements of all PTN equipment managed
by U31. The following equipment types are supported:
ZXCTN 6100;
ZXCTN 6110;
ZXCTN 6120;
ZXCTN 6130
ZXCTN 6200;
NE creation
ZXCTN 6220;
ZXCTN 6300;
ZXCTN 6320;
ZXCTN 9002;
ZXCTN 9004;
ZXCTN 9008;
when creating NE, you can select equipment type and set NE label,
gateway, IP, rack and subrack.
NE Attribute
Support checking NE attribute information and modifying NE
Checking &
attributes. The NE attributes that can be modified include the NE
Setting
tag, IP, and geographical location information.
Deleting NE
Support deleting the NE. The NE as well as all configuration

information on NE can be deleted by force.
Copying NE
Support copying NE in batch; support setting the number and IP

addresses of NEs to be copied in batch.
49
Function
Description
Data
Support NE data uploading, downloading and uploading
Synchronizatio
comparison. You can set whether the NE is synchronized
automatically; the default setting is "No".

Data synchronization is the synchronization processing mechanism
between the data in NMS database and the data on the main
controlling board of NE.
NE
configuration
saving and
Save NE configuration; clear configuration data on NE
clearing
NE Time
Support NE time query and correction; set NTP server of NE and
Management
the time synchronization mode of different NEs (non-automatic

synchronization, NMS automatic synchronization, NTP
synchronization); query the NE time and correct the time in batch.
The network management server and client support daylight saving
time and multiple time zones.
Static Route
Support creating, modifying and deleting the static route of NE.
Gateway NE
Set the gateway NE attributes; set master/slave gateway NE; view

the current gateway of NE; print configuration information of the
current gateway.
NE Automatic
Provide the NE topology automatic discovery which helps obtain the
Discovery
complete network configuration information. The function may

involve discovery protocols such as LLDP, and NM supports the
setting of protocol parameters.
NE upgrade
Bulk upgrade
of board
software
PTN fault
diagnosis
Support version file management; NE version upgrade rollback

management
Remotely upgrade board software of CTN devices and output
upgrade information in the form of tables.
Analyze the designated objects (e.g., NE/tunnel/service), including
configuration, alarm, performance and equipment status, and give
failure causes and solution recommendations.
NE
configuration
NE configuration file backup
file
50
Function
Equipment
data saving
NE User
Description
The system provides the function of saving NE configuration data,
that is, writing the data to the configuration file of equipment so that
the configuration data is still valid after NE restarts after power-off.
Support the management of all users who telnet on NE
Management
Board
Display the slot diagram of the current NE; support inserting, pulling
management
and automatic discovery of boards on all subracks; support the

board-related configuration, alarm, performance and maintenance
operations; the board view displays the alarm status of the current
NE.
Board Running
Support querying the running statuses on the board.
Status
Fan
Support configuring the related attributes of fan, including the
Management
rotational speed and control mode.
Cable
Create, delete and view the NE connection in graphic or text mode;
Connection
set the connection attribute information, including the connection
Management
tag, optical module type, fiber type, line attenuation, jump station
&
information and J0 byte.
Configuration
Link Automatic
Provide the link automatic discovery to automatically discover the
Discovery
optic fiber link through LLDP.
Equipment
Various functions for NE and boards can be implemented by the
Manager
equipment manager. The equipment manager provides the entry for

the functions.
Convenient
Configure parameters of accessed equipment via network
DCN
management interface so as to access equipment in network
provisioning
equipment installation and deployment stage

As NM signaling and user data are multiplexed on the data link for
transmission, to separate NM signaling and user data, separate
VLAN ID need be configured for NM data. To avoid the problem of
NM signaling
NM signaling channel disconnection caused by incorrect
channel
modification of VLAN ID on NM, the VLAN ID of NM signaling

channel can only be modified on the local accessed terminal of NE
instead of on NM. NM only provides the function of setting NM
signaling channel bandwidth of each port.
51
Function
Description
1. Support NE user management. Set user rights in the login modes
of LCT, DCN and QX. Create, modify and delete users; set
writing/reading rights, access restriction, login number limit and right
NE security
levels.
2. Support querying users logging in the NE, and user lock and
unlock functions.
3. Query all NE log information.
Display the information and status of all channels of service boards,
Channel view
including port occupancy status, alarm status and maintenance

status; support navigation to corresponding function windows.
5.2
PTN Interface Management

Table 5-2 PTN Interface Management
Function
Description
User Network
Support creating, modifying and deleting UNI (user network
Interface (UNI)
interface). This port includes two types: UNI-ETH and UNI-VCG.
Management
EI Port
Support setting the related attributes of frames on E1 port.
Management
IMA Interface
Support creating, modifying and deleting the IMA interface.
Management
ATM Interface
Support creating, modifying and deleting the ATM interface.
Management
Link
Support creating, modifying and deleting the link congregation port.
Congregation
Port
Management
52
Basic data free
It is configured to target whether the added link aggregate port
from
supports the attribute basic data free from configuration. The
configuration
designated port is free from configuration with basic data. The
of link
device can automatically generate the data or does not need the
aggregate port
data before deploying services.
Function
Link capacity
upgrade
management
Description
It supports the following Ethernet link capacity upgrade: FE->GE,
GE->10GE, and FE->10GE.
VLAN
Support creating, modifying and deleting the VLAN (Virtual Local
Interface
Area Network) interface.
Management
IP Interface
Support creating, modifying and deleting the 3-layer interface (IP
Management
interface). Support setting the related VLAN interface, IP address

and subnet mask.
VCG Port
Support creating, modifying and deleting the VCG port. Support
Management
setting the members of VCG port.
Ethernet Port
Support configuring the Ethernet port mode, including the access
Management
mode, trunk mode and mixed mode.
Basic data free
It is configured to target whether the added Ethernet port supports
from
the attribute basic data free from configuration. The designated
configuration
port is free from configuration with basic data. The device can
of Ethernet
automatically generate the data or does not need the data before
port
deploying services.
SDH Optic
Support setting the enabling status of SDH optic port.
Port
Management
MLPPP
Support creating the MLPPP Interface group based on the E1 port
Interface
or the channel E1. Support bundling one or several E1 ports and

channel E1 ports to the MLPPP interface.
L2 or L3 virtual
Create virtual L2 or L3 Ethernet interfaces; create virtual bridging group;
port, L2VPN to
one group correlates one virtual L2 Ethernet interface and one virtual L3
L3VPN bridging
Ethernet interface
L2 MAC
Support the configuration of L2 MAC addresses
Address
Configuration
53
5.3
PTN Protocol Management

Table 5-3 PTN Protocol Management
Function
Description
Spanning Tree
Support the spanning tree protocol configuration. Support the
Protocol
parameter configuration on the NE & port level for SSTP/RSTP

protocol, and support the parameter configuration for multiple
spanning tree protocols, including the configurations of MST
domain, MST instance and instance port.
Syslog basic
configuration
IGMP
Snooping
Syslog protocol is a standard protocol, mainly used for event

notification information. It provides functions like setting Syslog type
and configuring syslog server host.
IGMP Snooping is a feature of L2 function, which can limit
forwarding of IP multicast traffic. The product supports configuration
of NE-level and service-level parameters of IGMP Snooping.
Dynamic label distribution protocol of MPLS, such as NE LDP global
LDP
attribute management, L3 LDP attribute management and LDP

non-associated neighbor management.
Display the LLDP global information of port information of the
equipment. NM can trigger LLDP action; the equipment reports link
discovery result to NM. The system can perform automatic link
LLDP
discovery for a particular NE or for all equipment. The result

displayed includes current equipment information and link discovery
result, and will include corresponding detailed information for the
port in connected status.
Basic attribute management of RSVP-TE, including setting basic
RSVP-TE
parameters of RSVP, message retransmission parameters and GR

parameters
TE FRR
54
For specified TE tunnel, configure whether FRR (Fast Rerouting)

protection is allowed and specify its parameters
Function
Description
Manage BGP protocol, including BGP process instance attribute
table, address family attribute table, corresponding neighbor
attribute, route import policy and route aggregation policy
management. The major management functions of this module:
primary table BGP process attribute; address family attribute table
supports route mode address family, multicast address family,
BGP-4
VPNV4 address family and IPV4 VRF address family attribute

management; IPV4 VRF address can be created and the attributes
of the other three address families can be modified; neighbors can
be created under route mode address family and IPV4 VRF address
family; under other addresses, neighbors can be activated or
deactivated but cannot be created; support address family group
management; support configuring route import policy and route
aggregation policy under each address family
ISIS instance attribute management, ISIS L3 interface attribute
ISIS
management, route notification policy management and

aggregation route policy management
Process instance attribute management, area management,
OSPF
neighbor management; L3 interface supports OSPF attribute

management and link status database browsing
Support VRRP (virtual router redundancy protocol) group creation,
VRRP/VGMP
and specify identifier, L3 interface and virtual IP. Support VGMP

group and correlate with VRRP. Support configuring whether VRRP
and VGMP sends notification messages using local time interval
DHCP Relay
Support configuring whether to enable DHCP function, which

interfaces are enabled and whether roaming is allowed
DHCP Relay
Support configuring whether to enable DHCP Relay Snooping
Snooping
function and port trust

Give IPv6 L3 address to an interface of the equipment; add or delete
IPV6
IPv6 static route; set and execute Ping6 detection task; display the
actual path of trace6 to a destination
Configure L3 interface based on VLAN port/SuperVLAN, including
L3 interface
IP address and mask of this L3 interface; or configure this L3
creation
interface as unnumbered interface, and specify from which L3

interface to borrow IP address
55
Function
Description
Vlan transformation (VLAN translation) is also called vlan mapping.
It allows repeated configuration of vlan id of different Ethernet
VLAN
transformation
switches for edge access; by vlan translation function of Ethernet

switches, the repeated vlan id can be modified to different vlan id
and sent from the uplink port, so as to realize user isolation in L2
core switches. In this way, it simplifies the setting of edge access
switches. This function is to realize configuration of vlan translation.
Static route
Statically specify the next-hop IP address and forwarding interface

of the destination network segment
Multicast route management can realize configuration of multicast
IPv4 multicast
route
management
route attributes of an NE, and support querying total number of

multicast routes and multicast forwarding table. The management
functions supported include: query multicast route attribute,
configure enable status of multicast route and query multicast
forwarding table information
Manage global attribute and neighbor attribute configuration of
MSDP (Multicast Source Discovery Protocol). RPs can forward SA
MSDP
messages to each other in the domain by creating MSDP peer

relations between RPs in each PIM-SM domain to share multicast
source information. The functions include: NE MSDP global attribute
management and NE MSDP neighbor attribute management
Configure whether to enable PIM-DM protocol globally and whether
PIM-DM
to enable PIM-DM for each L3 interface; browse interface neighbor

status information and route table information of PIM-DM protocol
PIM-SM/SSM
MLD Snooping
Support PIM-SM (Protocol Independent Multicast Sparse Mode)

and SSM (Source-Specific Multicast)
Configure MLD Snooping in global mode and VLAN mode and set
multicast attribute in VLAN mode
Load sharing is a policy to perform load balance on multiple links.
Support setting number of BGP, OSPF, IS-IS and RIP for load
Load sharing
sharing; support load sharing configuration of static routes with the

same destination and different next hop addresses; support
configuration information query.
56
5.4
PTN Service Management

Table 5-4 PTN Service Management
Function
Description
TMS
Configure, modify and delete TMS, and configure IP address of the
management
next-hop IP interface.
Dynamic
tunnel
Support creating TE dynamic tunnel
configuration
Create/delete MS-PW. MS-PW: is composed of multiple SS-PWs
MS-PW
jointed end to end; the jointed points are called switching PE (S-PE)
configuration
points, on which switching of PW label levels between board PWs is

performed.
Tunnel
Support creating the static 2-way tunnel, realizing the route by the
Configuration
label exchange mechanism, and restricting the ratio of the tunnel.
Pseudowire
Support creating the pseudo wire of Ethernet and Ethernet VLAN
Configuration
types, bundling the related tunnels and restricting the ratio of

pseudo wire.
Complete GRE tunnel configuration, so as to invoke this GRE tunnel
GRE tunnel
created here in tunnel configuration to implement the function of

transporting MPLS tunnel crossing IP network.
ATM local
switching
service
Support port-level emulation setting, N:1 mapping mode and

classified service flow setting
ATM emulation service is to emulate ATM connection via PW. In
ATM
emulation
service
ATM->PW direction, bind an ATM-CES port to a PW and send it to

another port via this PW. In PW->ATM direction, according to the
binding relation of PW and ATM-CES port, put the ATM service
obtained by PW decapsulation on the specified ATM-CES interface
and send it out.
TDM local
switching
service
TDM local switching service means to directly switch the accessed

PDH signals to another access port.
57
Complete creation of E1 emulation service. TDM circuit emulation

service is to directly adapt the accessed PDH signals to PW, or
TDM
emulation
service
adapt to ATM AAL1 cell and then to PW, send it the destination
point via PW, decapsulate PW, or decapsulate PW first and then
ATM, and finally extract the PDH signals. The tunnel mechanism in
PW and physical bearing link in the tunnel are determined by the
system and irrelevant to circuit emulation part. The current TDM
circuit emulation service only supports E1 and T1 circuit emulation.
Ethernet
Support the 6 types of Ethernet service configurations:
Service
EPL/EVPL/EPLAN/EVPLAN/EPTREE/EVPTREE.
Configuration
L3 VPN
fulfilled by BGP.
Static MAC
Configure static MAC address learning, forwarding, filtering and
address
display.
NE MPLS
attribute
5.5
It mainly involves BGP MPLS VPN, that is, VPN route release is
Complete the global configuration of MPLS attribute parameters,

including OAM type, PW control word, label uniqueness, and one or
more static label range.
PTN Clock Management

Table 5-5 PTN Clock Management
Function
Description
Clock Source
Support the clock source configuration, querying the current
Configuration
synchronization scheduling source, configuring the mode of SSM

byte, configuring the external clock exporting, configuring the clock
source changeover type, configuring the clock source changeover
recovery mode and quitting the WTR status by force, configuring the
Sa position for external clock, configuring to sending the S1 byte by
forced, querying the exported clock source, configuring the optic
connection on the border of synchronization network, setting the
tunnel clock and E1 port clock, setting the GPS parameters, setting
the tunnel clock and E1 port clock.
TDM service
clock
Setting related to clock restoration for TDM services
restoration
58
Function
Time
transportation
function
GPS
Description
Configure 1588 time synchronization function of Ethernet port,
including: query 1588 status, set 1588 time domain, set 1588 time
node, set 1588 time source port, configuration needed for frequency
restoration from 1588V2 or 1pps
GPS-related setting, including whether to enable each absolute time
port, protocol type, and communication rate.
Display the configuration status information and actual working
status information of time synchronization source. The view displays
Time view
clock node type information configured on the NE, such as ordinary

clock, boundary clock, W2E transparent clock, P2P transparent
clock, ordinary clock+E2E transparent clock and ordinary
clock+P2P transparent clock
Display the configuration status information and actual working
Clock view
status information of clock source; provide clock source

configuration and query functions by menu or right click mode.
5.6
PTN OAM Management

Table 5-6 PTN OAM Management
Function
TMPLS OAM
Description
This is the OAM detection mechanism for the transmission path on
each TMPLS layer (TMP, TMC and TMS). Support configuring MEG
(maintenance entity group), MEP (maintenance end point) and MIP
(maintenance intermediate point). Support configuring the CV
package parameter, CC (connectivity check), pre-activate LM, LM
by requirement, AIS, DM, APS inserting/extracting, CSF
inserting/extracting, LB (loopback), locking and LT (link tracing
status) setting and querying.
CFM OAM
Ethernet CFM (Connectivity Fault Management) is the protocol

based on OAM (operation, management and maintenance).
Support the path discovery, fault detection, fault confirmation and
separation, fault notification, fault recovery and link detection
function. Support the configuration of CFM startup, MD
(maintenance domain), MA (maintenance association), MIP
(maintenance intermediate point), RMEP (remote EMP).
59
Function
Description
OAM upgrade
Include PW control word application, whole network PW control
parameters
word verification, protection switching application, OAM sending

direction status application and OAM receiving direction status
application
OAM Mapping
Notify the faults at UNI side to the peer side by OAM messages at
management
NNI side
Define Ping detection parameter template; create, modify and
delete detection group; periodical Ping detection and display
PING
detection result; the detection tasks supported include:

MPLS-LDP-Ping, MPLS-PW-Ping, MPLS-TE-LSP-Ping, IP,
Mac-OutIf-Ping, Mac-PW-Ping, IP-ICMP-Ping, IP-MNG-Ping and
IP-VRF-Ping
Set trace detection tasks in various modes; Trace modes include:
trace
ldp, PW, rsvp-te, IP (identified by port address), out-of-interface Mac

Trace, trace of specified PW
BFD
ICCP
5.7
BFD (Bidirectional Forwarding Detection) provides failure detection

between two systems
Support ICCP functions, including: configure LDP enable, create
redundancy group RG and specify RG attribute
PTN QoS Management

Table 5-7 PTN QoS Management
Function
Description
ACL (Access
Support ACL configuration, ACL rule group, ACL flow parameter
Control List)
configuration and port ACL template configuration.
Configuration
Complicated
flow
Add, modify and delete flow classification principle of virtual
classification
Ethernet services (LAN, TREE)
(template)
60
Port traffic
The priority queue at each input/output port controls the data traffic
control
to make it comply with the specify parameter requirement.
Function
Description
Port Ratio
Set the port ratio restriction. The parameters of output flow include
Restriction
CIR, CBS, PIR and PBS.

Complete configuration of PHB template; support setting PHB
PHB template,
DS domain
PHB
configuration
information and T-MPLS EXP field in this domain, or default

mapping relation between 802.1p priority of BVID of PBT and C-Bit
of BVID, that is, using which value of priority field to represent which
PHB.
DS domain PHB configuration: the system provides PHB
configuration function in DS domain
Dispatching
Support setting the dispatching policy of UNI/NNI port, including the
Policy
DRR dispatch, SP and DFQ dispatching.
Discarding
The user can only set the discarding policy of UNI/NNI port. The
Policy
discarding policy includes WRED and end discarding. By default, its

value is WRED.
Hierarchical QoS technology packages dispatching policies to
hierarchical tree structure, including setting and displaying HQOS
H-QOS
flow classification information, flow classification principles, HQOS

policy group attribute, policy group-related flow classification
attribute, policy correlation attribute, policy nest attribute, and
binding relation between port and HQOS policy.
5.8
PTN Protection Management

Table 5-8 PTN Protection Management
Function
Description
MSP
Support configuring the MSP (multiplex segment protection)
Protection
protection group. Support configuring the protection relationship,

protection group parameter (protection group name, WTR time,
return mode) and protection protocol APS.
TMS
Support configuring the TMS (segment layer) protection group, used
Protection
to complete the loop protection configuration. Support configuring

the protection parameter, protection group parameter (protection
group name, WTR time and return mode) and protection protocol
APS.
61
Function
Description
Port protection
Multicast streams are sent to two access ports concurrently; the two
ports protect each other; block one of the ports at a time; when the
working port has any problem, switch to the standby port quickly to
reduce packet loss.
Dual-ring
Dual-ring dual-node protection is formed by the protection of two
dual-node
intersected ring networks; the protection is basically fulfilled by
protection
combination of ring network protection and tunnel protection.
Tunnel
Support configuring the linear protection group of the tunnel.
Protection
Support configuring the protection relationship, protection group

parameter (protection group name, WTR time and return mode) and
protection protocol APS.
Main
Support setting the master/salve changeover of main controlling
Controlling
board, and querying the protection status.
Board
Protection
Board
Support the E1 board protection configuration.
Protection
Pseudowire
Support configuring the pseudowire dual-homing protection group.
Dual-homing
The pseudowire protection corresponds to the pseudowire
Configuration
dual-homing protection in EMS.

Dual Homing is a network topology wherein the equipment is
connected to the network via the independent access point
(appended point). One access point is the main connection while
the other access point is the standby connection, which is activated
if the main connection fails. Support configuring the protection
relationship, protection group parameter (protection group name,
WTR time and return mode) and protection protocol APS.
Support Hot standby protection configuration and switching. TE
Hot standby
dynamic tunnel protection mainly includes path protection which is
protection
achieved by Hot-standby. Hot standby is to protect the whole E2E,

using one LSP to protect another LSP.
62
Function
Description
Support VLAN 1+1 protection configuration and switching. VLAN
1+1 protection function is implemented on the basis of multicast
VLAN copying to improve the reliability of multicast services, Use
VLAN 1+1
working VLAN and protection VLAN to achieve 1+1 backup of
protection
multicast streams. Upon configuration, configure the active and

standby VLAN, set protection mode return/non-return, automatic
switching delay time, perform manual switching/forced
switching/lock/clearing, and query protection switching status.
Protection
Support querying the protection changeover status and
Changeover
maintenance status of all protection groups. Support the manual
Status
changeover of protection group, including forced changeover,

blocking/unblocking, manual changeover and clearing changeover.
L3 VPN FRR
Support enabling/disabling FRR function for a VRF in a BGP system
management
VLAN 1+1
To improve the reliability of multicast service, the system realizes
protection
VLAN1+1 protection function based on multicast VLAN copy; it

realizes 1+1 backup of multicast streams via working LVAN and
protection VLAN. Upon configuration, configure active and standby
VLAN, set protection mode return/not return, automatic switch of
delay time, perform manual switch/forced switch/lock/clear, and
query protection switching status
SD attribute
setting,
SD parameter configuration not based on protection group. Support
threshold
setting whether to enable SD alarm proliferation for the specified
setting,
port; support setting whether to allow FEI insertion; support setting
insertion
SD threshold of tunnel, section and PW
parameter
Provide protection view search, protection sub-network search,
Protection
protection sub-network creation, deletion & modification and
view
protection view display. The protection type supported is TMS ring

network protection.
5.9
PTN Maintenance and Security Management

Table 5-9 PTN Maintenance and Security Management
Function
Description
63
Function
Port Mirroring
Description
Support the configuration of port mirroring. Provide the mirror switch
setting. The mirror port can be used to monitor packets, perform
daily maintenance and online debugging.
Stream
Support port stream mirroring configuration; for stream mirroring
mirroring
configuration, first determine a stream via ACL rule and then mirror
to another port
Loopback
Support the loopback setting on the terminal end and line end.
Board
Support the board resetting function, including the hard resetting
Resetting
and soft resetting.
Laser Setting
Support setting the related parameter of ASL, manually

starting/stopping laser and laser status query. ALS is the automatic
laser judgment, which can automatically shuts down the sending of
laser when the laser is receiving LOS.
Inserting
Support manually inserting alarms, used in remote testing and
Alarm
maintenance.
Inserting Error
Support inserting error codes by force, used in remote testing and
Code
maintenance.
Overhead
Support the overhead configuration.
Management
Overhead
query
The system provides overhead setting function

Implement setting of alarm parameters, including alarm generation
confirmation time and alarm disappearance confirmation time. The
former one indicates how long after the alarm is generated it will be
Alarm
confirmed as alarm generation; the latter one how long after the
parameter
alarm disappears it will be confirmed as alarm disappearance. The

purpose of delaying confirmation of alarm generation and
disappearance is to avoid jittering caused by alarm generation and
disappearance.
Setting Visible
Support setting the visible and audible alarms.
& Audible
Alarms
Alarm
Support the alarm shielding setting and status query.
Shielding
64
Function
Description
Invert is mainly used for physical port setting. For the physical port
that is configured with invert, the alarm status will be inverted, that
is, when there is no alarm, the board will consider there are alarms,
and when there are alarms, the board will consider there is no
alarm; the generation and disappearance of alarms are reported as
what the board considers. If there is no alarm, the board will report
alarm generation after receiving the invert command; If there are
alarms, the board will report alarm disappearance after receiving the
invert command.
Automatic report restoration is used for physical port setting of
Alarm
tributary board/optical board. The loss of signal alarm will not be
pre-investment
generated when the service is not loaded. When the service is

loaded, the system enters normal status and automatically cancels
the invert status. Therefore, for the physical port that is configured
with invert, no alarm is reported. Meanwhile, the system decides
whether there is service according to whether there is LOS. When
LOS disappears, it indicates there is service; the system will
automatically cancel the pre-investment status and report cancel
alarm pre-investment status actively.
If there is no LOS alarm when receiving set alarm pre-investment,
the system should respond successfully first and then report cancel
alarm pre-investment status.
External Alarm
Support customizing external alarms
Setting
Alarm cascade
Set external alarm cascade
Zero-performa
Set if NE reports the cleared performance. When the setting is
nce
successful, the device does not report the cleared performance.
Suppression
Clearing
Clear the selected performance record of the selected resource.
Performance
Counter
Able to set real-time performance monitoring for port/LSP/PW and
Real-time
E2E port/LSP/PW; performance monitoring granularity can be set to
traffic
2s-900s.
monitoring
Support real-time statistics on traffic of current object in list and

graphic mode.
65
Function
Description
Radius
RADIUS is a standard AAA (Authentication, Authorization, and
management
Accounting)protocol, which authenticates users that access the

route switch to prevent illegal users to enter and improve equipment
security, including configuration of RADIUS accounting group and
authentication group
Anti-attack
Prevent various attacks on equipment and users to better guarantee

network security, including URPF configuration on L3 interface and
SYN FLOOD configuration.
66
SDH/MSTP Management
6.1
SDH/MSTP Single NE Management

This chapter introduces the management function set of MSTP NE layer, including NE
attributes, service, protection, clock and maintenance configuration functions.
MSTP NE management functions that can be provided include:
Table 6-1 MSTP single NE management function

Function
Description
NE creation. When creating NE, you can select MSTP equipment
type, set NE label, gateway, IP, rack and subrack. The NE label and
equipment ID can be repeated, but NE IP cannot be repeated.
NE attributes view and modification. Modify NE attributes including
label and ip after NE creation
Deleting NE. Support deleting the NE. The NE as well as all
configuration information on NE can be deleted by force.
Copying NE. Support copying NE in batch; support setting the
number and IP addresses of NEs to be copied in batch.
Basic
configuration
of NE
Ping and CLI function: ping NE in the right-click menu of NE or

telnet to N in CLI mode
NE Time Management
Board view: display the slot diagram of current NE, perform board
insertion and pulling operation, and perform board-related
configuration, alarm, performance and maintenance operations. The
board view displays the alarm status of current NE. Delete the
board.
Cable connection management and configuration: create, delete
and view NE connection in graphic or text mode; set connection
attribute information, including connection label, optical module
type, fiber type, line attenuation, jumper station information and J0
byte
67
Function
Description
Auto discovery: support auto discovery of NE and board; able to
create object directly in the typology view after discovery
Gateway NE configuration function: support gateway NE attribute
setting
Static route configuration
Multiplex section (MS) protection management: query MS protection
group and APS ID; support setting of protection attributes such as
protection level and switching restoration time; support setting
multiplex sections for one physical optical interface
Subnet connection protection: support setting subnet connection
protection, query SNCP protection group attribute and status
Board protection management: support setting various board-level
protections, including main control board 1+1 protection,
cross-connect board 1+1 protection and tributary board 1:N
protection
Orderwire (OW) management: set and query NE OW number and
OW protection information, including, OW number, group calling
password and forced insertion password
Trunk configuration: allow the user to create, query and deleted
corresponding trunk pair at the granularity of boar according to
SDH
requirements
configuration
Time slot configuration: configure aggregate-to-aggregate,
tributary-to-aggregate, aggregate-to-tributary and
tributary-to-tributary service configuration; support bidirectional and
unidirectional setting; support time slot query and configuration in
text and graphic mode; support TD resource query of online NE;
support resource statistics
Clock source configuration: support clock source setting, query,
switching and restoration; support standard SSM byte management
and ZTEs proprietary clock protection protocol management
Overhead configuration: support SDH overhead byte configuration,
query and deletion
Overhead cross-connect configuration: support SDH overhead
cross-connect configuration, query and deletion
PDH framing configuration: support framing configuration at E1 port,
framing format and multi-frame format
68
Function
Description
DCC/ECC utilization mode configuration: support configuration of
utilization mode of DCC/ECC in receiving and transmitting direction
MSTP protocol configuration; STP protocol configuration
Ethernet Port Attributes. Support Ethernet board port enabling, rate
configuration, MAC address learning, loopback test and query &
configuration of cross-connection, etc., data board attribute
management, Ethernet port basic attribute management, Ethernet
port VLAN tag management, Ethernet port TRUNK group
configuration, and Ethernet port egress QoS algorithm
configuration.
Ethernet Bandwidth Restriction. Port bandwidth restriction, including
egress/ingress bandwidth restriction mode.
L2 Switching Configuration. Support MAC address list configuration
and multicast setting.
Ethernet Port Mirror Management. Support the port mirror setting.
LCAS management: set LCAS attribute of port
VLAN tag: VLAN mode setting of port
MSTP
configuration
Service
configuration
VCG channel binding: VCG channel binding configuration

MSTP VCG status: dynamically monitor current status of VCG;
query VCG status; query history VCG status; set VCG status
threshold; shield VCG status threshold
VLAN security: set MAC address filtering according to VLAN
Ethernet Qos algorithm setting
UNINNI interface maintenance
User Ethernet interface management
Ethernet service management: set Ethernet services (E-LINE,
E-LAN, E-TREE service); query, create, delete and modify MFDFr;
configure board service attribute; related operation;
activate/deactivate MFDFr
Ethernet service classified management: Ethernet CoS template
management, CAR template management and Ethernet service
classified management
RPR node attribute: configure attributes of RPR node, including site
name, fair algorithm and protection parameters
69
Function
Description
RPR service classified management: RPR CoS template
management, RPR CAR template management, RPR service
classified management
MST area management: create MST area and MST instance
Trunk group: creation, modification and deletion of Trunk group and
setting of LACP attributes
L2 control frame processing mode: configure frame processing
mode of board/port
Loopback. Support setting of NE loopback and automatic
cancellation of loopback.
Inserting Alarm
Inserting Error Code
Channel Detection
ASCII Code Stream Test. Support the query and test of ASCII code
stream on board.
Setting of Board Register
Card Communication Test
Card Resetting
Laser Switch & ALS Setting
Maintenance
Management
Mechanical & Electrical Management

Port Attribute Setting
Cross-connection Board Loopback
TCM
Querying board production information and Optical Module
Information
IP Port Overhead Setting
Overhead Configuration
Overhead Cross-connection
64K Cross-connection
64K Attribute Setting/Mapping Setting. Support the setting of
transceiving clock at port of S200 V35B board, and setting of data
validity. Support the initial time slot mapping at PDH 2M detection
point.
70
Function
Description
Synchronize Module Hardware Information
Entire Network Maintenance. Support the query of NE or entire
network loopback, cross-connection board loopback, channel
detection, alarm insertion, error code insertion, laser shutdown,
DCC port shielding, alarm shielding, performance shielding and
alarm pre-input, etc. All maintenance mentioned above can either
be saved or printed.
Select one record, the setting can be deleted.
PING Function of Data Board. Support the PING function of data
board, used to test the connectivity of current board and other
boards.
Querying Board Running Status. Support querying the running
status of data board.
RPR Maintenance. Support the RPR port status querying and
changeover.
6.2
ASON Management
This chapter describes the intelligent network management features of U31 together with
traditional SDH network for ASON (Automatically Switched Optical Network). ASON
management functions that can be provided include:
Table 6-2 ASON Management Function

Function
Description
ASON Node Attribute. Support the node identification attribute.
Initiate and stop the ASON control plane setting and node signaling
parameter.
ASON
NNI Management. Support the management of transport interface
Management
NNI.
Control Interface. Support the configuration, querying and
modification of inband control interface and outband control
interface.
71
Function
Description
Outband Control Interface Neighbor. Support the configuration,
query and modification of outband control interface neighbor.
TE Link. Check the TE link and modify TE link attribute.
Transport Plane Topology. Generate the topology based on the
transport interface configuration. Support the automatic update and
alarm state.
TE Link in Whole Network. Display the TE link topology of the whole
network based on ASON node.
Control Plane Operation Topology. Display the control interface
topology of the whole network based on ASON node.
Control Plane Loopback. Setting of control plane loopback.
Call Management. Create, check, modify and delete the ASON call.
Setting Dynamic Recovery Lock of ASON Service
Setting Manual Response of ASON Service
Modifying Initial Connection of ASON Service
Setting Optimized Rerouting of ASON Connection
Querying Cross-connection of Single-point Control Plane
Unified Display of ASON Service & Traditional Service in Service
View
Creating Low-level Traditional Service Based on ASON Tunnel
Service
Deleting Remained Connection
1:N Protection Group Management
Alarm Management of Control Plane
6.3
MSTP Protection Subnet Function

TM
This chapter describes NetNumen
U31 protection subnet function, managing all
protection subnets in view mode. Protection subnet is a wide concept, not only including
network structures that have complete self-protection function, such as multiplex section
ring and channel protection ring, but also including network structures that do not have
self-protection function such as non-protection ring and non-protection chain. This mode
72
is more efficient and convenient compared with single-NE protection group configuration
mode. Protection subnet management functions that can be provided include:
Table 6-3 MSTP Protection Subnet Function

Function
Description
Protection subnetwork creation.
The following protection types are supported: SDH dual-fiber
two-way multiplex segment sharing protection loop (without extra
services), SDH dual-fiber two-way multiplex segment sharing
protection loop (with extra services), SDH 4-fiber one-way 1+1
multiplex segment protection (MSP1+1), SDH 4-fiber one-way 1:1
multiplex segment protection (without extra services), SDH 4-fiber
one-way 1:1 multiplex segment protection (with extra services),
SDH 4-fiber two-way multiplex segment sharing protection loop
(without extra services), SDH 4-fiber two-way multiplex segment
sharing protection loop (with extra services), SDH 4-fiber link 1+1
multiplex segment protection (MSP1+1), SDH 4-fiber link 1:1
multiplex segment protection (without extra services), SDH 4-fiber
link 1:1 multiplex segment protection (with extra services), SDH
multi-fiber one-way 1:N multiplex segment protection (without extra
Protection
services), SDH multi-fiber one-way 1:N multiplex segment
View
protection (with extra services), SDH multi-fiber link 1:N multiplex

segment protection (without extra services), SDH multi-fiber link 1:N
multiplex segment protection (with extra services).
Protection subnet verification: support verification of protection
subnet
Form complete protection subnet by searching according to NE
information and cable information on NM
Protection subnet manager
Support graphic display of protection and working routes; query
detailed information including name, type, switching status, and
maintenance status of each protection subnet in the form of list;
Support modification of protection subnet information;
Support setting manual protection switching
Support querying switching events
Delete protection subnet
73
WDM/OTN Management
7.1
WDM/OTN Network Element Management

Table 7-1
Table 7-2 WDM/OTN Network element management
Function item
Description
WDM/OTN
Network element creation: it supports creation of all OTN device
device network
network element that managed by U3. It supports the following
element
device types:
management
ZXWM 32(V1.1);
ZXMP M600;
ZXMP M800;
ZXWM M900;
ZXMP M720;
ZXMP M721;
ZXMP M820;
ZXWM M920;
ZXONE 8300.
ZXONE 8500.
ZXONE 8700 X32;
When we create the network element, we can select device type,
set network element label, gateway, IP, rack and subrack.
Network element categorizing: it supports network element
categorizing based on type, area, and universal categorizing.
(based on IP address, location and device type).
Network element attribute check and setting: It supports network
element attribute information check and network element attribute
modification. It supports modification of network element attributes
including network elemetn label, IP, geographic location
information, and manufacturer information.
Network element deletion: it supports network element deletion. It
can delete network element. It needs a second confirmation to
delete the network element. If we confirm at the second time, we
can forcibly delete network element as well as timeslot and
protection configured for the netowrk element.
74
Network element duplication: it supports batch duplication of

network element. It supports setting of number and IP address for
batch duplicatoin of network element. It supports setting of whether
to duplicate card, timeslot, clock information in duplication, and
network element number and IP address for network element that
duplicated.
Gateway network element: It supports setting of gateway network
element attributes, and master-standby gateway network element. It
supports view of current gateway of the network elements, and
printing of the configuration information of the current gateway.
Data synchronization: It supports network element data upload,
download and upload comparison. We can set automatical
synchronization or not for network element and its asynchronous by
default.
Data synchronization: the synchronization processing mechanism
on network management database and network element main
control card.
Network element time management: it supports network element
time query, network element time calibration, and setting of time
synchronization (non-automatic synchronization, network
management automatic synchronization, and NTP synchronization)
for NTP server and each network element. It can take batch query
and calibration of network element time.
Static route: it supports creation, modification and deletion of static
route of the network element.
Automatic topology discovery: it supports automatic network
element nad network topology connection discovery. It can obtain
the complete configuration and connection information by automatic
discovery.
Network element connection test, ping connection test, and telnet
connection test.
Network
Management of network element administrator: it supports setting of
element
LCT access authority. It supports setting of reading and writing
security
authority of the administrator.
management
Local access prompt: when LCT or EMS takes local access to NE,
NE reports local access event to the network management (the
network management software that login the network element), and
display is in the alarm.
75
The current logged in administrator on the network element: query

the information of the administrator that currently logs in the network
element.
Network element log management: it provides network element log
query, and user management. it can be configured with user name,
password and authority for the user that logs in.
Network
Card management: It displays the current network element slot
element card
diagram and card plugging-in, plugging-out operation, as well as
management
card related configuration, alarm, performance, and maintenance

operations. The card view displays the alarm status of the current
network element. Delete the card. Install the card: In card view, right
click in the blank slot, we can choose card to plug in. Or in the card
type page to the right of the card view, we can select the card to
plug in the card in the specified slot. Delete the card: in the card
view, right click the plugged-in card to plug-out it. When we plug out
the card, we need to make a second confirmation. If confirmed, the
card can be plugged out forcibly.
It supports card attribute configuration, including: basic card
attributes configuration, additional card attributes configuration, card
description information, card IP address configuration, module
information, and basic port attributes.
WDM/OTN signal flow diagram displays the flow information of
service signal in the card on the network elemetn in graphs. It
supports connection alarm display inside network element.
Card version information query: it supports detailed version
information of the card including software, FPGA, and PCB version.
Synchronous card hardware information: it supports synchronous
card hardware information. When card hardware information is put
into the base, the card version information can be exported by card
report.
Card software upgrade: It provides software upgrade management
functions. It supports single card software upgrade and batch
network element/card software upgrade.
Automatic card discovery: it supports automatic card discovery.
Display the newly discovered automatic card creation, newly
plugged-in card, card conflict, and existing card in different colors
and icons.
76
Network
Cable connection managemetn and configuration: Create, delete
element fiber
and check network element connection in graphs or text. We can
connection
set the connection attribute information including connection label,
management
optical unit type, fiber type, line attenuation, jump station

information, and J0 byte.
Batch connection management: it supports batch configuration and
check of fiber connection.
Cable connection report: it can export cable connection information
as report file.
WDM/OTN signal flow chart: It shows the flow information of service
signal in the card on the network element in graphs.
Fiber topology management: we can check wavelength occupation,
link optical power loss, and link related services. We can query and
modify the link and check link related alarms.
7.2
WDM/OTN Equipment Public Configuration

Table 7-1 WDM/OTN Equipment Public Configuration
Function
Description
Equipment manager: The equipment manager can help to
accomplish various functions of NE and boards. The equipment
manager provides the portal of the functions.
Resource naming principle management: support customizing the
default naming principles for network management system, link, NE,
board, port and service.
WDM/OTN
Equipment
Public
Configuration
Fan Management: Configure the fan speed adjustment mode and

fan speed level.
The clock source configuration: set the master/secondary relation of
network element clock source, and we can adjust the network clock
synchronization direction of the whole network. We can define the
priority level of the single-card clock source by setting the clock
source quality level. We can query clock synchronization status
through network management, get and monitor the synchronization
status of the network element clock.
77
Function
Description
Network element time management: We can configure network
element current time, network element synchronization (network
element and network management synchronization), and NTP
server management. Network element and network management
time is synchronized automatically, so the network management
records the correct alarm time and log time. If the network has been
equipped with NTP (Network Time Protocol) server, we can set the
time synchronization of network element and NTP server.
Time configuration management: configure 1588 time
synchronization functions, including: the time domain, time node,
the parameter configuration of the time port, external time 1PPS +
the TOD port configuration, and the time node status query.
Channel Management: we can query the logic resources form of
each physical port on the card in the form of topology, including the
layer rate, the port user label, service status, service direction,
service labels, connected ports, and alarm status.
7.3
WDM/OTN Equipment Overhead Configuration

Figure 7-1 WDM/OTN Equipment Overhead Configuration
Function
Description
J0 Overhead Configuration :By repeatedly sending the segment
access point ID, the J0 byte can make the segment receiver confirm
whether it and the pre-defined sending end are in the continuous
connection status. To guarantee the interconnection of
WDM/OTN
uplink/downlink services on the wave-division channel, the sent
Equipment
value and the received value should be consistent.
Overhead
OTN Overhead Configuration :In OTN network, the system checks
Configuration
whether the expected values of the tracing ID over OTUk and ODUk
layer are consistent with the received values, to monitor the related
channels. The OTN overhead configuration can be used to
configure the OTN TCM overhead, PM overhead, SM overhead, PT
overhead, ODU-layer port locking and MSI overhead.
78
Function
Description
GCC Byte Usage Configuration: The GCC byte of OTN can be used
to transmit the monitoring information or dedicated communication
information, or both. By configuring the usage mode of GCC byte,
the enabling of monitoring channel and dedicated communication
channel can be realized.
7.4
WDM/OTN Equipment Service Configuration

Figure 7-2 WDM/OTN Equipment Service Configuration
Function
Description
FEC Mode Configuration: FEC is a technology that performs the
error correction verification by using the redundancy information
transmitted together with the information. The system can configure
the FEC working mode of NE board.
Data Board Trunk Enabling Configuration: Perform the enabling
control upon the trunk ports on the board. The user side can provide
several tributary channels at the same time, and each channel can
separately access several client services such as GE, FC, ESCON,
FICON and DVB, to realize the access and congregation of different
services.
Ethernet Port Property Configuration: Configure the self-negotiation
WDM/OTN
mode of GbE port on GE-type boards, for the negotiation of working
Equipment
status of GbE port on the opposite equipment. That is, the GbE port
Service
on both equipment taking part in the communication must have the
Configuration
same working capacity.

FC Long haul Enabling Configuration: When the board access
service type is FC, it supports the configuration of FE pull enabling.
Board Physical-layer Transparent Transmission Configuration: The
user can configure the port transparent transmission enabling and
port status on related boards.
Service Type Configuration: Configure the access service type for
the boards with different service access capabilities.
Congregation Service Context Configuration: Set the tributary port
status (loopback/direct connection, context) on the congregation
service board.
79
Function
Description
Data Service Configuration: Set the service type, encapsulation
protocol, VC capacity, context/direct connection, stream control of
each tributary board on the data board.
Service Mapping Configuration: Configure the mapping relationship
between the service side and the line side of the board access
client.
Cross-connection Configuration: Provide the ODUk electric
cross-connection configuration for the concentrated or distributed
cross-connection matrix of OTN equipment. It supports the graphic
and text modes.
It supports working crossed connection and protection crossed
connection configuration.
ROADM System Wavelength Assignment: Support assigning any
wavelength to any port in ROADM system. Meanwhile, set the
attenuation amount for each wavelength to realize the spectrum
balancing, so that the transmitted spectrum satisfies the
requirement.
7.5
WDM/OTN Equipment APR-AOSD Management

Table 7-2 WDM/OTN Equipment APR-AOSD Management
Function
Description
APS Communication Status Configuration: When a large number of
boards are configured in the system, if all the related service boards
report APS alarms at the same time due to line fault, it will cause
WDM/OTN
Equipment
APR-AOSD
Management
unnecessary pressures upon the efficiency and reliability of APS

bus. To reduce the communication pressure, we need to control the
initial reporting of APS alarms on service board, so that we can
choose to report the APS alarms of service board according to the
system APS function. At this time, for the board, the controlled
alarms mainly include the LOF/LOS/SD alarms. It controls whether
the board reports alarms to the APS port, but does not affect the
alarms reported to the upper-layer EMS.
80
Function
Description
Board APC Configuration: The function of APC (Automatic Power
Control) is that in case of line fault (optic fiber is disconnected), the
OA board automatically disconnects or reduces the light power
sending to the direction of disconnection, so as to protect the line
maintenance personnel from the damage of strong light, and
resume the line to normal working status after it is repaired.
APS Condition Enabling Configuration: Considering the difference
of AOSD conditions for different users, when the user chooses to
enable the board, he needs to enable it in the board enabling
function. For future expansion, the user needs to set the AOSD
condition for each port on the board.
Protection Mode Configuration:Configure the APC protection mode.
Port AOSD Enabling Configuration: Configure the AOSD enabling of
the tributary port on the board.
DEG Condition Enabling Configuration: Set the reference
attenuation amount of the filter on the specified board on the
specified NE.
7.6
WDM/OTN Equipment Power Management

Table 7-3 WDM/OTN Equipment Power Management
Function
Description
Fixed Attenuator: Set the fixed attenuator on EMS, to record down
the location of the line attenuator.
WDM/OTN
Board Power Adjustment: Adjust the line output optic power
Equipment
difference on the AO board of WDM or the gains of optic power
Power
amplification board, to guarantee the balance of channel power.
Management
Laser Setting: Provide the query and setting of laser switch status
for OUT boards and OA boards in NE, so that the system can shut
down laser in case of abnormality or query the current laser status.
81
Function
Description
Optic Changeover Board Switch Setting: In the debugging of optic
circuit, the optic signal needs to be manually switched to the
working/protection channel via OPCS/OPMS. Currently this
operation can only be realized by APS controlling board, so it is not
convenient during the debugging process. Based on this
consideration, on EMS, there adds the command of setting/querying
the optic changeover boards.
RPOA Subsystem: RPOA is the abbreviation for remote pump optic
amplifier, which embeds a segment of optic fibers when laying out
the transmission optic fiber and provides the pump optic at the
remote point, so as to amplify the transmission optic signal. The
RPOA subsystem includes two parts: the gains module RGU
between the lines, and the pump module RPU at the remote site.
The RPOA subsystem provides the two-way configuration between
two OTM sites. As the RPOA subsystem cannot detect the signal
optic powers that the RGU entry, it cannot realize the gains locking,
and needs to realize the gains adjustment via EMS. Different output
gains correspond to different output powers of different pump
wavelengths on RPU. EMS calculates the output power of each
pump wavelength according to the configuration information of
RPOA system such as: wavelength in RPU appended information,
cross-segment type, optic fiber type, number of pumps,
transmission distance, attenuation amount. By adjusting the input
power of pump and distributing it to the board, realize different
output gains. Also support the reverse calculation (calculate the
RPU output gains according to the different powers queried out).
Optic Power Management: Query the board port, line optic power
and attenuation, wherein the optic power data include both the
history data and current data, while the attenuation data are the
current data. Provide the path power diagram, and support the
history performance statistics based on path. Provide optical power
statistics based on multiple services and points of time.
Querying Main Optic Power: The user can produce the main optic
power and optic fiber attenuation change of the whole network,
including the reference value, nominal value and current value of
output/input optic power on each optic fiber port. The user can
generate the adjustable remaining amount table of the whole
network.
82
Function
Description
Optic Power Management Subsystem: Provide the power
management domain configuration, including the multiplex layer
/channel layer detector and executor. Provide the manual power
optimization and automatic power optimization configurations. View
all-network primary optical power and fiber attenuation variation.
7.7
WDM/OTN Equipment Spectrum Management

Table 7-4 WDM/OTN Equipment Spectrum Management
Function
Description
OPM Setting: The OPM setting function is used to query/modify the
OPM channel, and real-time monitor the optic channel performance.
The user can configure whether to detect each optic channel
according to the actual system configuration. The port attenuation
on OPM board refers to the difference between the optic power
reported on the detection port of OPM board and the actually
measured optic power. By the command of setting OPM
attenuation, complete the function of querying and setting the
WDM/OTN
Spectrum
Management
attenuation on each port of OPM

DRA Pump Wavelength Power Adjustment: Set the pump
wavelength power assignment table of the specified board.
Attenuation Spectrum Adjustment: The system allows the user to
set a target spectrum, and set the attenuation spectrum of the
related board by combining OPM/EOPM board, VMUX board and
DGE board, so as to adjust the input spectrum.
Attenuation Spectrum Adjustment Enabling Configuration :Query
and set the attenuation spectrum enabling of DGE and VMUX
boards.
7.8
WDM/OTN Equipment Wavelength Management

Table 7-5 WDM/OTN Equipment Wavelength Management
Function
Description
83
Function
Description
Wavelength Automatic Adjustment Period Configuration: When the
wavelength detection is enabled, VCF will continuous scan the
wavelength. This operation should be avoided because of the lifespan of
VCF. A new round of scanning is not allowed one week after EOWM
scanning. The scanning interval can be set, and it is 24 hours by default.
One week after the scanning, the board software resets the timer and
counts again. When the timer is due, it starts a new round of scanning.
EMS provides the configuration of wavelength automatic adjustment
period.
DLI Status Configuration: Support the command of setting and querying
DLI status.
WDM/OTN
Equipment
Sub-wavelength Home Configuration: It is used to modify the deviation

of channel central frequency of the CTDC module.
Wavelength
Wavelength Adjustment Tuning: When the standby optic source is used,
Management
according to the specific situations of wavelengths in the system, the

wavelength tuning is used to adjust the output wavelength of the
adjustable spectrum laser from one standard wavelength to another
standard wavelength. This method can be used to improve the
wavelength usage ratio. If the laser has worked in a bad working
environment (high temperature) for a long time, or the laser is aged, the
frequency will have certain deviation. When the deviation is
accumulated to a certain amount, the channel service will be damaged
or even interrupted. The wavelength adjustment function provides the
method of adjusting the wavelength deviation, to make the laser of the
service board work at the central frequency. When adjusting the
wavelength, detect the power by using the OWM board or
multi-wavelength meter.
7.9
WDM/OTN Equipment Protection Configuration

Table 7-6 WDM/OTN Equipment Protection Configuration
Function
84
Description
Function
Description
It provides protection group creation of OTN device.
Including:
Protection attributes: set protection group ID, select protection group
type, relay protection, and user label. The protection types include:
Ethernet 1+1 protection
Ethernet 1:1 protection
WDM chain multiplexing section 1+1
WDM chain channel layer 1+1
WDM electrial layer sub-wavelength 1+1 protection
WDM electrical layer sub-wavelength 1:N protection
WDM electrical layer wavelength 1:N protection
WDM ODUk SCNP protection
WDM 2-fiber bi-directional OCH sharing protection
WDM 2-fiber bi-directional OMS sharing protection
WDM electrical layer sub-wavelength 2-fiber bi-directional OCH sharing
WDM electrical layer wavelength 2-fiber bi-directional OCH sharing
WDM/OTN
Equipment
Protection
Management
WDM optical layer sub-wavelength 2-fiber bi-directional OCH sharing

Protection parameters, linear protection includes the return type,
additional service, Wait To Restore time, whether to take the signal
degradation protection, switching type, APS signaling channel, the
actuator; ring protection to increase False-Connection-Proof, whether to
initiate Holdoff mechanism, and Holdoff time;
APS setting includes APS ID, APS protocol, APS controller, and
protection subnet topology.
Protection relation:Confirm the work to protect the port relations.
Supports the protection group editing, operation, and view operations
when it is created.
Querying Related Information of Protection Group: Provide the service
query on the NE port of protection group, and the PSE event query.
Protection Changeover Command: Provide the external command
configuration for protection group, to test the changeover of protection
groups. The following external commands can be distributed: clearing,
ring working channel lock, all cross-segment protection locking, ring
forced changeover, ring manual changeover, ring practice
Protection protocol reset: Make protocol reset of protection APS
controller.
85
Function
Description
Board IP Configuration: For the 100M monitoring channel system, the
electric port and optic port of OSCF board of all NEs should have the
corresponding IP address, and other service boards need one IP
address, to guarantee that the OSPF route protocol can realize the
unicast route.
Multicast Route Configuration: For the 100M monitoring channel
system, to improve the one-to-many point communication efficiency,
multicast is introduced. Compared to the unicast, the multicast can
reduce the network traffic and avoid sending the repeated data packets.
When one NE needs to send the same packet to other N NEs, it needs
to send N data packets if using unicast, but only needs to send one data
packet if using multicast. Configure the multicast route in U31 EMS,
which can calculate the multicast group and multicast route, set and
query the multicast route.
7.10
WDM/OTN
It provides creation, search, and protection switching query and setting
protection
of various types of protection sub-networks. It protects the display of
sub-network
subnet topology. It creates/deletes/modifies the protection group.
WDM/OTN Equipment Other Interface & Module

Configuration
Table 7-7 WDM/OTN Equipment Other Interface & Module Configuration
Function
Description
Port Enabling Setting: Control the enabling of monitoring ports according
to the actual networking. If one monitoring port is forbidden to be used,
the related performance and alarms of this monitoring port cannot be
WDM/OTN
reported, and it cannot affect other monitoring channels, tributary
Equipment
services and performance.
Other Interface
Disperse Compensation Setting: Configure the adjustment mode, step
& Module
and target dispersion for the related parameters of dynamic dispersion
Configuration
compensation.
AIS Enabling Setting: By setting the AIS enabling status, decide whether
to automatically generate the AIS signal when the protection channel
has no light.
86
Function
Description
Backplane Setting: Query and set the backplane channel changeover
mode, and the current backplane working channel.
Board Master/Slave Binding Configuration: When many boards in WDM
need to configure the master/slave status, to guarantee the data
consistency, we need to configure the binding relationship of related
boards on EMS, and save only one copy of the data for the related two
boards. In this way, the data consistency is easier to be processed.
7.11
WDM/OTN L2 Ethernet Configuration

Table 7-3
L2 Ethernet configuration
Functional
Description
items
Aggregated port configuration: The system provides the creation of the

link aggregated ports. Link aggregated port is one port aggregated from
multiple Ethernet ports with different rates. It is used to carry services
with large bandwidth requirements. The rates of aggregated port in one
link aggregation group must be consistent. Different ports in an
WDM/OTN L2
Ethernet
configuration
aggregated port implement LCAP protection.

Ethernet service configuration: it supports single-point creation of six
Ethernet services: EPL/EVPL/EPLAN/EVPLAN/EPTREE/EVPTREE. It
provides service flow point information query.
Port Ethernet OAM configuration.
It supports CFM configuration: CFM, MD, MA, MEP, MIP, RMEP, and
CFM global configuration.
87
Functional
Description
items
QOS configuration: supports ACL configuration including ACL Rule

Configuration, ACL flow control configuration, the port ACL
Configuration, ACL local priority configuration, ACL traffic statistics
configuration, ACL mirroring configuration, ACL reorientation
configuration, and ACL flow SWAP configuration.
Support QoS scheduling solution configuration including port
configuration, VLAN queue configuration, flow queue configuration, DS
domain configuration, WRED drop policy template configuration, the
service instance configuration, and card MAC address queries.
Support PHB mapping configurations including PHB mapping table
configuration, and PHB mapping table object configuration.
Support the flow control configuration including port flow control
configuration, port shaping configuration, queue shaping configuration,
and VLAN queue shaping configuration.
Support VLAN queue configuration.
MAC address configuration: provides static MAC address configuration,
VLAN ID, and MAC aging configuration
Port configuration: Configure the port attributes of the card that supports
the feature, including attributes of the physical ports and service ports.
Set the loopback and take maintenance operations such as clearing the
MAC address.
Test-Probe Configuration: configure the card Ethernet test data.
Protocol transparent configuration: Configure the following transparent
protocol packets: STP, LACP, GARP, Mac-control, 802.1d, 802.1x,
802.3ah, and 802.1ag.
ESR configuration: configure the VLAN the ESR information.
MIRROR configuration: configure mirroring to support all ports at the
customer side of the card and the line side. Support Mirror addition,
deletion and modification.
VLAN mapping configuration: Set the VLAN mapping information.
Spanning Tree Configuration features include the spanning tree
enabling configuration, the spanning tree global parameter
configuration, the Spanning Tree domain configuration, spanning tree
priority configuration, spanning tree card parameter query, and the
spanning tree port parameters configuration.
88
Functional
Description
items
IGMP Snooping Configuration: IGMP Snooping is a feature of L2

function. It can restrict the forwarding of IP multicast traffic. It supports
the IGMP Snooping network element level parameters configuration,
and IGMP Snooping servcie level paramters.configuration.
The features supported include IGMP enabling configuration, IGMP
attribute configuration, IGMP static multicast configuration, IGMP
multicast queries, and IGMP router port query.
7.12
WDM/OTN Equipment Maintenance

Table 7-8 WDM/OTN Equipment Maintenance
Function
Description
Board Software Management & Upgrading: From the board view, query
the hardware version and software version of one board, as well as the
PCB version, FPGA version and software version currently running on
the board. The board software management is used to pre-configure the
related board software for each board type in U31. Perform the remote
upgrading of the board software upon the managed NE, to upgrade the
board software into the specified software version, download and
activate the board software. Batch upgrade the board software, by
performing the remote upgrading of the board software upon the
managed NE into the specified software version. Display the current
WDM/OTN
Equipment
Maintenance
upgrading plan of the board software, and customized the board

software upgrading plan.
Loopback: Perform the testing of adjacent end and remote end of the
trunk and tributary respectively.
Board Communication Setting: To improve the system maintenance
capability, provide the communication testing capability to test whether
the system is abnormal. Note that the system must realize the different
testing types upon different modules. Currently all boards can support
the function of testing the communication port.
Inserting Alarm: Support inserting alarms manually, to be used in remote
testing and maintenance.
Inserting Error Code: Support inserting error codes by force, to be used
in remote testing and maintenance.
89
Function
Description
Board Important Data Setting: The system allows the user to read and
modify the important maintenance data on board, to increase the
operation flexibility.
Board Register Setting: The system allows the user to read and modify
the content of board register, to enhance the maintenance function.
Board Resetting: The board resetting includes the hard resetting and
soft resetting.
Soft resetting: After the board receives the request of soft resetting, it
interrupts the program running, and points the program pointer to the
initial address, to initialize and re-start the operation.
Hard resetting: After the board receives the request of hard resetting, it
should generate the hardware resetting signal, which not only resets the
board software, but also initializes the board register.
Judging Electric-level Adjustment Mode: By judging the electric-level
adjustment mode, automatically or manually adjust the judgment
electric-level of DWDM according to the error code, to increase the
system reliability and reduce the error code ratio, so as to reduce or
eliminate the wrong frames.
Master/Slave Changeover: Set the board master/slave status.
Backup & Recovery of Single NE: recovery in database level
NCP Backup & Recovery: Provide the data backup and recovery
functions of NCP board.
7.13
WASON Configuration
Table 7-9 WASON Configuration
Function
90
Description
Single-node
The control plane enabling: configure whether WASON of network
management
element is enabled.
of WDM/OTN
Node configuration: WASON node identifier is the parameter to
WASON
exclusively identify a node on the control plane. Configuring

WASON node identifier for the enabled network element on the
control plane, we can make the network element become a WASON
node network element, which is the premise of other WASON
configuration operations. The network element can be normally
managed when it is configured with WASON node identifier.
I-NNI transport interface configuration: supports batch increase of
the I-NNI transport interface wavelength information, and automatic
discovery parameter at the transmission interface,
Transmission interface status configuration.
Support I-NNI out-band control interface configuration.
Support I-NNI out-band neighbor configuration.
TE link attribute configuration: the system is configured with I-NNI
transport interface information. The control plane automatically
generates TE link based on the resources allocated to it. Support
query of TE link with the source of the transmission interface of a
node, and the query of TE link topology operation in the whole
network.
Control plane wavelength group information configuration: support
query and modify of the control plane wavelength group information.
In the device with ROADM + TMUX application, if the wavelength in
the transmission link takes service scheduling in the node by TMUX,
since TMUX physical design is not full-crossing model, the
wavelength switching between the transmission links can not
implement switching of any wavelengths in the node. Wavelength
conversion has certain constraint features. It is configured with the
control plane wavelength group data.
In the process of WASON operation, if network management is
normal, the control plane related data will be initiatively reported to
the network management, which takes data synchronization.
However, if the network management and device are detached, the
network management hasnt updated the information that the device
calculates based on the protocol, it may lead to conflict between
network management resources and device, which may cause
service problems. So it is necessary to provide data synchronization
to support conflict coordination and processing between control
plane and management plane.
91
Management plane controls plane data in a synchronous way. The

network management shows the control plane running topology with
WASON node as its nodes to control the control channel (including
inband and outband) between the interfaces. Since there may be
redundant control channel between two network elements, the
network management needs to take mapping of multiple control
channels to one line of the topology. We can check the detailed
parameters of the multiple control channels that represented by
topology line.
The control plane runs topology query: for the purpose of user
management and maintenance, the management plane needs to
set automatic discovery mode of the control plane, including the
control interface, the control channel, transmission interface, the
layer adjacency, and the transmission capacity control such as start
or stop automatic discovery of the entire control plane. And
management plane can control in which layer of the network the
automatic discovery is.
Link bundle: we bundle multiple (or all) paralleling links with the
same features between two adjacent ASON nodes into one logical
link, which can be released as one line in link maintenance and
broadcast so that we can avoid the waste of resources. The bundled
logical link is called link bundle.
Wrong fiber connection detection: at the final step in the process of
automatic discovery, if the original adjacency relationship changes
(such as changes in fiber connection), the control plane will report
wrong fiber connection/line alarm to the management plane.
Wrong line indicates the remote information for receiving and
transmitting fiber is inconsistent. Wrong connection indicates the
bi-directional data link of automatic discovery is consistent with the
remote information provided by the management plane.
92
Optical damage parameter configuration: including line card optical

damage parameter configuration, the amplifier optical damage
parameter configuration, and the link optical damage parameters.
The relevant optical damage parameters are as follows:
OSNR: amplifier output power, the amplifier gain, amplifier noise
index;
Dispersion: the dispersion coefficient, fiber length, dispersion
compensation distance;
PMD: the number of components, the PMD values of the
components;
Optical damage parameters of the components:
Line-side optical fiber: dispersion coefficient, length, PMD value;
OA: gain, output power, noise index;
WSU, OMU, ODU: PMD value;
DCM (Dispersion Compensation Module): The compensation
distance.
Control plane parameters configuration: including the signaling
protocol parameter configuration, routing protocol parameters
configuration, and LMP protocol parameters configuration.
Connection backtracking Strategies: For the SPC connection with
no backtracking parameters configured, or not easy to be configure
with the SC connection of the relevant parameters, we can set
policy parameters for the network nodes. If the connection or the
service layer connection is blocked when no specific connection
backtracking parameters are configured, we implement these
backtracking strategies. In order to avoid rerouting confusion
caused by inconsistent operations in practice, the strategy
configuration choice at all nodes in a network is the same.
Fiber connection data comparison: the management plane can
query the control plane fiber connection configuration information,
compare it with fiber connection configuration information of the
management plane, and generate comparison results. If there is
difference in the comparison results, the fiber connection
information of the management plane can be re-distributed to the
control plane, and cover the fiber connection configuration
information of the control plane.
93
WASON
WASON Service Management: 1. It supports WASON SPC service
connection
overview, creating, deletion, modification, SPC service query and
management
maintenance.
2. It supports the searching of SPC service with fuzzy search. It
searches SPC service conditions including user label, A endpoint, Z
endpoint, creation time, and service status.
3. Select an SPC service, show the basic attributes, routing
strategies, routing constraints, and the established connections of
the service, among which the established connection should be
displayed in topology. It supports recovery routing of WASON
pre-calculation service. It also supports preset re-routing strategies
to support the distinction to protect the preset connection.
4. Select an SPC service. It needs to support call modification, call
deletion, manual reply, recovery initiation activation, recovery
initiation deactivation, putting into operation, not putting into
operation, routing information refreshing, command clearing,
protection locking, forced switching to the active, forced switching to
the protection, manual switching to the active, and manual switching
to the protection.
Configure basic service information, protection settings, recovery
reply, multicast strategy, whether to work as a link, routing
strategies; specify the connection information list, the route that
active connection must go through, the route that
protection
connection must go through, and the eliminated connection route.

Initiatively report WASON service information:
report the service status information directly to the management
plane owing to service connection information changes (connection
increase or decrease) due to the management plane request
operations or internal automatic operations.
Delete WASON service: Delete SPC service.
Modify WASON service: SPC service modification.
Deletion of remained SPC connections: in the process of control
plane node operation, the label is the SNP point distributed by the
control plane. In the process of service establishment and deletion,
there may occur remained labels or transferred labels, both of which
are caused by asynchronous information of the nodes that the
service involves. The Network management can delete this type of
connections.
SPC service status modification: SPC service status modification.
94
SPC service recovery initiation activation modification: SPC service

recovery initiation activation supports batch modification of SPC
service recovery initiation activation.
Manual reply of SPC service: manual reply setting for SPC service.
SPC service synchronization: synchronize SPC service to make the
SPC service information of the network management system is
consistent with the SPC service information of the control plane.
SPC service connection optimizes re-routing: When the LSP service
path is interrupted, the first node calculates the best path for service
recovery, then establishes a new LSP service path by signaling to
transport the service by the new service path. Delete the original
LSP service path when the new LSP service path is established.
Crossed internal path query: when the service is established, the
path that the service goes through when it is reported contains only
the transmission interface, without the resources used on the
interfaces on the components it goes through inside the node. To
manage the complete path that the service goes through in a better
way, including the path between nodes and within the nodes, the
management plane needs to query the internal path of each node.
SPC service recovery preset rerouting: the path constraint that
rerouting goes through can be manually specified when the service
establishment is completed, including the resources it goes through,
eliminated resources and recovery strategies.
Mandatory delete WASON service: It forcibly deletes the specified
WASON service, especially the service that can not be deleted by
normal means.
Service path display: the service traffic is currently operated on
which connection, and the path that the connection goes through
can be displayed.
95
The establishment and management of multi-layer network

services: it can view the routing information of the customer layer
service including the path of active, protection, the active recovery,
protection recovery, active optimization, and protection optimization.
It can view which links provided by service layer service are used in
the customer layer service link. When a customer layer service path
is selected, if the path contains lower layer path, it can be expanded
to the lower layer path, and displays the routing information of the
lower layer service. When the lower layer path is contracted, the
customer layer path before expansion is displayed before the start
of the customer layer path.
SPC service protection parameter modification: SPC service
protection parameter modification indicates that we can modify the
related attributes of the channel 1 +1 protection service established
for the control plane: protection switching recovery waiting time,
protection switching lag time and the protection switching recovery
method.
PC to SPC Service transfer: the traditional service (PC service) can
be upgraded to intelligent service (SPC service) in the process of
network upgrades, expansion and transformation, that is to say, we
can upgrade permanent connection with PC originally controlled by
the control plane to soft permanent connection with SPC controlled
by the control plane. The purpose is to achieve the smooth evolution
of the intelligent optical network. During the process of PC to SPC
service transfer, it is requested that services must not be damaged
during the conversion process from PC service to SPC service.
SPC to the PC service transfer: transfer the soft permanent
connection that originally controlled by the control plane to
management plane. For example, the method should be used at the
initial phase of ASON application to reduce the possible risk of
instability in engineering applications.
Set 1 +1 service protection switching: take switching control of 1 +1
protection & recovery (permanent 1 +1 service does not support
external commands) and 1 +1 protection service. At present
supported switching operation types include clear, lock, manual
switching and compulsory switching.
96
PCE node
PCE subrack configuration: It implements display and operations
management
with individual PCE subrack. PCE sub-frame configuration:
of WDM/OTN
separate PCE sub-frame display and manipulation.
WASON
Card View: card view needs to support PCE card plug-in and
plug-out. It supports automatic card discovery. The card view needs
to support basic attributes of PCE card and port.
It supports right click menu list for PCE slot before plug-in: card
plug-in, and automatic card discovery.
It supports PCE card right-click menu lists including device
manager, card plug-out, card reset, the currently running version,
and attributes.
Create PCE equipment: When we successfully create PCE
equipment, the configuration menu in equipment view or WASON
view will show other function menu of PCE management so that we
can take further management of PCE equipment.
Delete PCE equipment: Delete PCE equipment.
PCE node configuration: Configure PCE node identifier, configure
PCE node identifier and the equipment can be normally managed in
the network management system.
PCE interface management: It supports physical outband control
interface configuration, and control interface neighbor configuration.
PCE automatic discover attribute configuration: PCE automatic
discovery is used for PCC to automatically obtain PCE existence
and capability, service range information to use PCE calculation
capability. It supports discovery attribute configuration.
PCE master/secondary management: It supports PCE
master/secondary management configuration.
PCE version management: It supports PCE version management
Global Resource Optimization: After multiple service creation,
deletion, and adjusting, there may be resource fragments, resulting
in abundant total resources in connection creation which cannot be
distributed. Global resource optimization is used to defrag the
existing connections to put the resource fragments into block so as
to carry more services.
Data
Data Synchronization: It provides real-time synchronization of
synchronization intelligent network element data items, which is the same with data
synchronization of non-intelligent network elements.
Data Upload: It provides upload feature of intelligent network
element data.
Create WASON service: It provides data download of intelligent
network elements.
97
IP NE Management
8.1
IP Resource Configuration Management

Resource configuration management integrates two major functions of resource
management and configuration management. Resource management unit occupies a
more and more important position in network management. It can not only provide
statistics management of all used and available resource in the network, but also works
on network planning. At the same time it gives directions in future network maintenance.
With resource configuration management, users can get a general picture of network
operation. Thus resource configuration management is a basic system in operators
service process that cannot be neglected. Its also an important premise of automatic key
service process for service launching and service guarantee. Resources have certain
common places so that resource configuration can be implemented together for easy
management and statistics.
Table 8-1 Resource Configuration

Functions
Description
1. NetNumen U31 network management system can provide
graphic interface to make configuration for all managed
equipment and implement remote configuration management
Resource
configuration
management based
on GUI
with the least steps. NM engineers dont need to learn all those
complicated command formats so that OAM efficiency is greatly
improved.
2. NetNumen U31 network management system provides
configuration template function, with which users can
customize configuration template, make configuration of NEs of
the same type in batches, simplify configuration steps, and
realize automatic management.
98
Functions
Description
1. All managed equipment in NetNumen U31 network
Resource
management system supports human-machine command so
configuration
that in-built Telnet/SSH can be adopted to support remote
management based
configuration management of the equipment.
on man-machine
2. NetNumen U31 network management system provides
command
script file editing function, with which users can directly edit
script file, finish it, and distribute it to the NEs.
Take integrated management such as check, modification,
NE information
management
deletion, importing/exporting of NE basic information (name,

type, memory, and software version), IP address information,
rack physical information, interface information, slot
information, card information, link information and clock time.
NE statistics
L2 resource
configuration
management
Take statistics of utilization and state of the NEs in the whole

network.
It provides management of all resource in the network and that
related to L2 network. The manageable resource includes MAC
address, L2 VLAN, LLDP, link aggregation, EPON, STP and
IGMP Snooping.
It provides management of all resource in the network and that
related to L3 network. The manageable resource includes IP
L3 resource
address, IPV4/IPV6 information, L3 multicast management,
configuration
dynamic and static route and its topology display,
management
OSPF/BGP/ISIS/RIP route management, specific route

monitoring, ARP management, VRRP management and
Radius information view.
Service
configuration
management
Provide IP equipment with MPLS basic configuration

management, static tunnel management, dynamic tunnel
management, and L2VPN & L3VPN management.
NE configuration
Configuration of router, switch and UAS products.
Configuration
It supports script customization template, and distribute the
template
configuration template to NE as tasks.
NE security
NE time segment management, ACL management, NE user
management
and account management.
Add strategy
Customize timing strategy to complete the corresponding
configuration task
configuration.
99
8.2
IP Rack Management
Rack diagram management displays equipment configuration in graphics and rack run
status. The user can view the following information in the diagram:
Table 8-2 Rack monitoring function

Function
Description
Display rack information, version information, board
Rack diagram display
CPU/memory/temperature/hardware information, power supply

information, fan information and port information in graphics.
Display the corresponding color according to the rack status
Status display
including link break, on-line, non-management, and master,

secondary and so on.
Alarm display
Display alarm severity with different colors. The alarm levels

are: critical, major, minor and warning.
Associate alarm in rack diagram and view alarm details.
Fast navigation
Associate performance in rack diagram and implement query of

real-time performance and history performance data based on
network element CPU/memory or port traffic.
Rack operation
8.3
It supports card reset, and port opening/closing.
IP Performance Data Types

NetNumen U31 can monitor different performance variables of the whole network,
including:
Table 8-3 Performance data monitoring function

Item
Description
NE system
information
Monitor performance indexes such as NE, including CPU
performance
utilization , CPU peak utilization, memory utilization.
monitoring
100
Item
Optical module
information
monitoring
Interface
performance
monitoring
Link performance
monitoring
PW traffic monitoring
L2VPN service
performance
monitoring
L3VPN service
performance
monitoring
Description
Monitor performance indexes of optical module such as optical
power interface status, optical wavelength (nm), received
power (dBm), launched power (dBm), voltage (mV), bias
current (mA) and temperature ().
Monitor performance indexes such as port receiving/sending
bytes, port receiving/sending packets, error rate statistics,
packet loss statistics, transceiving rate and egress/ingress
bandwidth utilization .
Monitor performance indexes such as incoming/outgoing traffic
statistics, delay/jitter/packet loss statistics and bandwidth
utilization statistics
Count PW egress/ingress byte number, egress/ingress packet
number, egress/ingress rate, CIR and PIR.
Count L2VPN egress/ingress byte number, egress/ingress
packet number, egress/ingress rate, CIR and PIR.
Count L3VPN egress/ingress byte number, egress/ingress

packet number, and egress/ingress rate.
Count total route number, straight route number, static route
VRF route statistics
number, RIP route number, OSPF route number, ISIS route

number and BGP route number.
AC access point
Count egress/ingress byte number, egress/ingress packet
traffic monitoring
number and egress/ingress rate of AC access point.
Snmp information
statistics
Take statistics of received and transmitted

Get/Get-Next/Get-Response/Set/Trap type packets, and
number of packets with error label.
101
Item
Description
Availability (the ratio of normal operation time of NE in a day)
Connectivity (the ratio between NE link failure times and polling
times)
Cumulative time to failure (the cumulative time to NE failure
from the creation of performance task)
NE availability
statistics
Cumulative time to normal (the cumulative time to NE normal

from the creation of performance task)
Cumulative availability (the cumulative availability of NE from
the creation of performance task)
MTTR (the time from failure to recovery)
MTBF (the average time from normal to failure)
8.4
IP File management
As network scale and services rise, network equipment type and number will increase
sharply. Therefore, network administrator urgently needs an excellent management tool
to manage the files of different NEs. NetNumen U31 offers the policy-based file base
management tool, namely, all files are arranged into different bases according to NE type,
and are backed up and restored according to the policy.
Table 8-4 File management function

Function
Description
Manage NE configuration file, create configuration file base for
each IP NE in NM system, and organize configuration file base
according to NE type. The user can create a task backing up
and restoring configuration file for each IP NE, and set task
Configuration file
attribute to timely or periodical run, to avoid executing file
management
management when the services are busy. The system supports

mass task run. The user can edit the file in the base or select
any two configuration files or the run configuration of the same
equipment to compare. The system can periodically audit
configuration file.
102
Manage NE version according to NE type and create version

file base for NE of one type. NM system can list current and
available software version in the system. The user decides
whether to upgrade and backup the version according to
Version file
current information. The user can also create version upgrade
management
and backup task, set task attribute to timely or periodical run, to

avoid executing file management when the services are busy.
The system can execute mass version upgrade and backup for
NE of one type. It supports Grace Restart without affecting
services.
8.5
IP OAM Management
NetNumen U31 network management system provides active failure detection function
for the staff to actively monitor the network operation state regularly, forecast and
discover the possible failures.
Switch port loopback check: Check port loopback and close the port if the loopback
is available. It is a switch proection mechanism.
Switch VCT.
E2E PING check
MAC PING: Check the IEEE802.3-defined Ethernet link-layer information.
ICMP PING: Check IP-layer performance and errors.
LSP PING: Check MPLS LSP data plane failure.
RSVP PING: Check MPLS TE tunnel.
VRF PING: Check MPLS L3 VPN errors.
VPLS PING: Check VPLS service errors.
Customize periodic check, generate result reports and display them in

graphics and matrix lists.
Check results include packet loss rate, maximum/minimum/average delay,

and maximum/minimum/average jitter. Support threshold alarm.
NetNumen U31 supports EFM management in IEEE 802.3ah (Operations,

Administration,
and
Maintenance-OAM).
Mainly
directed
to
link-level
103
management, it can perform monitoring and fault management for point-to-point (or
virtual point-to-point) Ethernet links. It plays an important role in the connection
management of network users in the last kilometer, where faults occur frequently.
EFM counts and monitor PTP physical link operation status, including frame
transport failure rate, link transceiving rate comparison, and packet loss statistics.
The major functions include:
Set global EFM and loopback timeout.
Set EFM check link and port parameters.
Verify link connectivity: Check the status of the monitored link.
Check remote loopback: The local sends to the remote the packets except
OAMPDU. After receiving them, the loops back them to the local and counts
the packet loss rate.
View link event: View wrong frames and symbols of the checked link in the
form of tables.
View link remote discovery information.
NetNumen U31 realizes the management functions defined in IEEE 802.1ag

(Connectivity Fault Management). It is mainly directed to service-level
management, providing convenient and fast fault discovery, detection and
management function for the network. The major functions include:
Global CFM enabling management
Domain
resource
configuration,
including
MD/MA/MEP/RMEP/MIP
configuration.
ETH-LB (Ethernet loop back) management
ETH-LT (Ethernet link tracing) management
SQA(Service Quality Analyzer)

By sending test packets, SQA analyzes network service performance and quality,
such as delay variation, TCP delay, FTP delay and file transport rate. It is primarily
applied to ZXR10 M6000/T8000/89E.
104
NetNumen U31 sends different kinds of test packets from one end to the other
and counts remote response and round-trip time so that the user judges protocol
availability and network performance according to the statistics. It supports such
tests as ICMP-echo/UDP/TCP/FTP and outputs performance check report. The
functions include:
ICMP ECHO: Check network performance between source node and

destination node through enhanced PING packet. Network performance in a
specific VRF can be checked. Check result includes packet loss,
maximum/minimum/average delay(ms) and maximum/minimum/average
jitter(ms).
UDP: Check network performance between source node and destination

node through UDP packet. Network performance in a specific VRF can be
checked. Check result includes packet loss, maximum/minimum/average
delay(ms) and maximum/minimum/average jitter(ms).
TCP: Check network performance between source node and destination

node through TCP packet. Network performance in a specific VRF can be
checked. Check result includes packet loss and maximum/minimum/average
delay(ms).
FTP: Check network performance between source node (client) and

destination node (server) through FTP. Network performance in a specific
VRF can be checked. Check result displays and obtain delay and reading
bytes of a certain file.
MPLS OAM TRACE
In MPLS L2 VPN network, detection is initiated at PE side to check the

connectivity of MAC layer for the L2VPN. In regular network, detection is
initiated at CE side to check the connectivity of MAC. Each hop information
of the network can be displayed in the detection results.
In MPLS network the error reporting mechanism for MPLS LDP / RSVP
detection can be used to discover and locate network failures. The detection
results cover the connectivity, loopback interval, and hops.
105
8.6
IP Network TE Management
MPLS TE management module is located on NetNumen U31 network
management platform, capable of integrating with other modules of platform to
implement comprehensive management of the service layer. Via the access
interface, it arranges data exchange between the network management system and
equipment to finish MPLS TE management. This module contains the following
services:
Table 8-5
IP Network TE Management
Functions
Description
Service plan stage is mainly responsible for implementing basic
network TE resource management before service implementation.
The basic management of network TE resource is the primary
condition of managing MPLS TE tunnel service. MPLS TE
management module provides the simplest graphic page and
Service Plan
unified resource configuration management in plan, so that theres

less unreliable man-made factor in the plan, which accordingly
makes the service definition more reliable and stable. All the
modules with TE feature support off-line configuration and in-batch
online deployment. In this way, the network administrator can
prepare for configuring MPLS TE tunnel efficiently.
End-to-end MPLS TE tunnel guide definition: It provides a
convenient and flexible end-to-end tunnel deployment. With graphic,
click method and automatic distribution strategy of default
Service
parameters, it can conceal the configuration details and make the
Implementatio
service launching easier and faster. It supports automatic
calculation to generate path as well as manual addition of the path.

It can show path topology in graphs. Automatic tunnel parameters
distribution can avoid complicated planning. It can be adjusted as
needed with flexible customization.
106
Definition of explict path: It uses network management to implement

graphic configuration of explict path. Its easier to use the mouse to
drag and create. Pay attention to real-time color applying of view
path at the same time of configuration. Users can use view path
attribute default option to improve planning efficiency. Attribute
modification of explict path is also supported. Strict and loose path
setting are both supported.
MPLS TE status topology display: different colors are used to
display different states such as strict and loose explict path,
connection status of tunnel, and alarm level display. It provides
easier management.
MPLS TE tunnel service strategy deployment: it supports instant
deployment, timing deployment, and regular deployment.
Automatic discovery and configuration auditing: it supports
automatic discovery of tunnel service in the network, configuration
auditing between network and database, and comaprison of
auditing results.
Flexible service monitoring capability. Service monitoring is an
important job in daily network maintenance. As for MPLS TE
service, the alarm management provided by MPLS TE can carry out
accurate fault location and service topology display.
Service
OAM functions it provides can implement PING and TRACE
Guarantee
detection of MPLS TE service tunnel.

Powerful protection management mechanism. MPLS TE service
supports two kinds of tunnel protection mechanism, i.e.
Fast-reroute (FRR) and hot-standby tunnel LSP.
8.7
IP Network MPLS VPN Management

NetNumen U31 provides a user-oriented, carrier-class, and cross-platform VPN
service integrated management module. It provides the operator with a scalable and
high-performance service management to satisfy the increasingly developing
demands. The module is featured with the following functions:
Table 8-6
IP Network MPLS VPN Management
Functions
Description
107
Functions
Description
Service plan stage is mainly responsible for implementing basic
network VPN resource management before service implementation.
The basic management of network VPN resource is the primary
condition of managing MPLS VPN. MPLS VPN management
module provides the simplest graphic page and unified resource
configuration management in plan, so that theres less unreliable
Service Plan
man-made factor in the plan, which accordingly makes the service

definition more reliable and stable. Including:
Basic Network Configuration, consists of the configuration of PE
equipment interface, link, basic network protocol, etc.
Equipments Resource Management: consists of all the physical
resources and logical resources.
Service Definition: VPN Service definition wizard (AC, PW, VPLS,
VPWS, L3VPN); VPN service view.
Service Deployment:
To keep the normal and convenient service operation and
management in peak hour, service deployment not only can be
carried out in user-drive immediate initiation manner but also
supports reserved customization manner. User only has to set
Service
specific implementation time in execution policy, and then the
Implementatio
system will initiate deployment right on the required time. It also
supports periodically deployment.

The service deployment will generates related reports to record the
execution of every command, so that users can check them as per
their demands.
Service Audit compares configuration record in the management
system and the real deployment to check their coherence.
Service Discovery: It supports dicovering VPN network from
equipments.
Service alarm monitoring.
Service performance statistics: supports VPN traffic, packets, and
rates.
Service
Network connectivity auditing: Connectivity audit verifies the status
assurance
of service deployment. It can accomplish the connectivity test of

PE-PE, PE-CE, and CE-CE. The audit report will be generated
accordingly.
MPLS OAM
108
8.8
IP Network VLAN Management

With the enlargement of the network scale, there are more and more VLAN applications.
NetNumen U31 provides user-friendly and cross-platform VLAN management system
to realize unified management of many VLANs of different levels in different domains. In
this way, it satisfies the increasing service development. The services involved are:
Table 8-7 IP Network VLAN Management

Function
Description
IP Network VLAN
L2/L3 VLAN plan and configuration
Management
Deployment and deletion of L2/L3 VPN

Automatic discovery and configuration audit
Information management of VLAN related port
Export of VLAN information
8.9
IP Network ZESR/ZESS Service Management

ZESR (ZTE Ethernet Smart Ring) is actually a protocol used in the Ethernet ring link
layer. It features fast convergence, high performance, and high reliability. By providing
highly reliable performance based upon less than 50ms fast convergence, ZESR is
capable of implementing multiple services. Together with advantages of Ethernet like
cost effectiveness, flexibility, high bandwidth and extensibility, ZESR is an integrated
solution for Ethernet ring technology. The extension of ZESR technology gives support to
ZESS (ZTE Ethernet Smart Switching) technology, which realizes the fast switchover
and load balance between L2 Ethernet links. Besides, the switchover from the active link
to the standby one is less than 50ms.
NetNumen U31 focusing on ZESR and ZESS services provides corresponding
management solutions, which gives conveniences to user to manage ZESR/ZESS
service in graph. The specific features include:
109
Table 8-8 IP Network ZESR/ZESS Service Management

Function
Description
ZESR/ZESS Service
End-to-end topology display
Topology Display
Display of the roles of different nodes

Display of the blocked port and link
ZESR/ZESS Service
End-to-end equipment graphic configuration simplifies
Deployment
configuration procedure
Support pre-deployment and consistency verification, which
ensure stable network operation
ZESR/ZESS
Automatically discover the services running in the existing
Automatic Discovery
network
Get the configuration data automatically
Implement real-time synchronization
8.10
IP Network IPTV Service Management

IPTV stands for interactive protocol TV. Taking telecom broadband network as transfer
tunnel and TV as terminal, IPTV a brand-new technology integrates multiple technologies
including interactive Internet, multimedia and communication to provide family users with
many interactive services such as TV.
For
IPTV
service,
NetNumen
U31
network
management
system
provides
corresponding management solutions to enable user to carry out graphic IPTV service
management to satisfy users multiple demands. It implements management in two
scenarios:
8.10.1
IPTV Controllable Multicast Management Based on User Service

It is used for IPTV channel control on switch. It implements a whole set of IPTV service
management by network management with the following specific functions:
110
Template Management
According to real service initiation, NetNumen U31 provides template-based

IPTV management. The template management consists of the following five
classifications:
Preview policy: The preview parameters (including maximum preview time,

maximum lasting time and minimum interval) configured for one channel with
preview authority is called one piece of preview policy.
Channel resource: All channels for implementing IPTV service; one channel is
defined by channel name, channel VLANID, and multicast address.
Channel template: The collection of all the channels deployed on a device is

called a channel template.
Package resource: Several channels stick together in preview or watch mode

to compose package resource.
Package template: the collection of all the channels and packages deployed
on one device is called a package template. The package in one package
template must be built on the basis of the same channel template.
First of all, information that will be configured on a device should be considered. If

package service is going to be implemented, the preview policies related to the
channels included in the package should be configured first. Then configure a
channel template, and a package template will be configured at last; otherwise, only
the configuration of preview policy and channel template will do. The channel
collection configured on the equipment is a channel template, and the configured
package collection is a package template.
Configuration Management
Configuration management includes the configuration of NE multicast and user
multicast. The configuration of the NE multicast is the primary condition of user
multicast configuration.
The configuration of NE multicast is used to deploy channel, package, preview

policy, global IPTV configuration, global CDR configuration and global preview
111
policy configuration on one NE. It is responsible for the delivering of

corresponding commands.
User multicast configuration is used to deploy channels and packages related

to one user, the CAC attributes (maximum bandwidth and maximum ports) of
the user and the package subscription time restriction on the NE.
CDR Record Management

CDR (Call Detail Record) is used to record users specific applications of IPTV. It is
the original source of the accounting. The network management system as the
middle system on one hand receives CDR record from the equipment regularly; on
the other hand it reports CDR record to the superior service management system.
At the same time, it provides simple query service for the network management
client.
Northbound interface
Provide TL1 northbound interface to interconnect with upper-level BSS system, to
meet the service provisioning requirements of operators.
8.10.2
IPTV Broadcast Control Management Based on Multicast Source

This function is mainly used on service gateway router to take broadcast control
management based on the validity of multicast source with the following specific
functions:
IPTV channel management

Implement management of IPTV channel on service gateway router. Each channel
contains the following information: channel name, source address, multicast
address, and notes. It supports creation, modification, and import/export of the
channel.
IPTV monitoring platform management
Implement management of IPTV monitoring platform in the network

management system. Each monitoring platform contains the following
information: platform name, service gateway router, related user, monitoring
112
interface, downlink interface, and the managed channel list.
It supports the decentralization and domains of the monitoring staff by

creating different role users associated with different monitoring platforms.
Each monitoring person can only monitor the platform related to himself.
They are not allowed to manage the other monitoring platforms.
It supports creation, modification, deletion, and configuration deployment

and uninstallation of the monitoring platform.
IPTV channel make-break management

Each monitoring person can manage the channel list of their own monitoring
platform. Unique broadcast control function can enable the monitoring person to
take the realtime check of the live channel. When he discovers security/illegal
problems in the live channel source contents on the television wall, he can take
direct control through the graphic interface of the network management system by a
click to cut off/resume live channel contents so as to realize the legality and security
monitoring of the live channel contents.
8.11
IP Network Cluster Service Management

The access layer network normally consists of a large number of mid-range/entry-level
Ethernet switch spreading in different access areas, for example, L2 access switch in
corridors in the residential community network. These devices take up public network
address to arrange management, which wastes lots of IP addresses. At the same time,
as all these devices with similar configurations are dispersive, traditional management
leads to low efficiency. To implement dispersive management of switch network and
save IP address resource, cluster management technology comes out. By using one
public network address, it manages a collection of Ethernet switch (support 255 member
devices maximally).
The major advantages of the cluster management mode provided by NetNumen U31
are:
113
Table 8-9 IP Network Cluster Service Management

Function
GUI Configuration
Description
For the switches allocated in all corridors, they only have the
private network addresses. When it is working as a member of
one cluster, it can be managed.
All member switches can carry out graphic page configuration,
including port configuration (initiate port and priority, etc.), loop
detection configuration, VLAN configuration, port mirroring
image configuration, L3 port configuration, the storage of the
existing configuration, LACP configuration and QoS
configuration.
Cluster Topology
Display the tree-mode topology view of the existing cluster and
Display
the information of all switches; after a while, the system

automatically updates the cluster topology. The default time
interval is 10 minutes. User can carry out configuration as per
specific situation.
Cluster Configuration
The role of the switch can be changed on the cluster topology

freely; Provide graphic configuration of cluster parameter,
topology collection and neighbor discovery.
114
Rack view
check the switch port status according to the port color
Alarm statistics
Alarm statistics in cluster
Traffic statistics
CPU utilization, memory utilization, port ingress traffic, etc
End to End Service Management
9.1
Customer management
The customer management module provides specific management functions for leasing
customers of bearing services so that the operators can perform unified management
and maintenance for customer information.
Table 9-1 E2E Service Customer Management

Function
Description
1. Support creating, querying, modifying and deleting a customer.
Support setting customer attributes upon creation, including
customer name, position, address, E-mail and contact information.
Support querying a customer. The query conditions include
Customer
customer name, customer level, credit level, contact name, contact
management
address and creation time.

2. Support setting the services leased by the customer.
3. Support setting customers equipment management range.
Distribute an existing device to a customer for management or input
a non-existing device to a specified customer for management.
9.2
PTN E2E Management

NetNumen U31 has the following PTN E2E service management function:
Table 9-2 PTN Service Management Functions

Functions
Description
115
Functions
Description
TMP Tunnel Configuration.
Support creating link tunnel and loop tunnel. During the creating
process, he can set the batch number, user label, source end,
client, tunnel mode, configuration status, route constraint and QoS.
The batch creation is supported.
Calculating Route: The user can automatically or manually calculate
the route.
Dynamic TE Tunnel configuration.
For dynamic tunnel, it is up to control plane to complete label
consultations, for a static tunnel, it is up to NMS to compute and
specify the labels.
GRE tunnel.
Create end to end GRE tunnel, and generate single point GRE
tunnel configuration information at source and sink point.
PW configuration.
The user can create and modify the end-to-end pseudowire. During
the creating process, he can set the batch number, user label,
E2E Service
source end, client, tunnel, forward/backward label, controlling
Management
character, pseudowire type, QoS parameter. The forward/backward

label can be manually input or automatically generated.
CES service Configuration.
The user can create and modify the end-to-end E1 service. He can
set the service source end, structuralization, local idle code, client,
route and encapsulation type, wherein the service route can be
created by the pseudowire or tunnel.
ATM service Configuration.
The user can create and modify the end-to-end ATM service,
including the source end, port-level simulation mode and mapping
mode, wherein the service route can be created by the pseudowire
or tunnel. Different mapping modes can set different vp and vc
exchange tables.
Ethernet Service Configuration.
The user can create the end-to-end Ethernet services, including:
EPL/EVPL, EPLAN/EVPLAN and ETREE/EVTREE. He can set the
source end, choose the route, choose the pseudowire or tunnel or
configure the node parameter.
116
Functions
Description
L3 VPN service configuration.
Create end to end L3VPN, support dynamic / static hybrid
configuration, RD configuration, RT configuration, LSP binding
configuration, in all PE nodes generate a single network element of
L3VPN service instance
Discovering Services Automatically.
Discovering All Services Automatically: The user can discover all
services in the whole network.
Discovering Incremental Services Automatically: The user can
discover the services incrementally in the whole network. He can
only re-discover the TS cross-over or label that has not formed
services, or the services not in consistent status.
Copying service. Copy the tunnel, pseudowire, the parameter
template of Ethernet services.
Service navigating. Support navigating by Domain and navigating
by NE Resources.
Filtering Services. The user can filter the services according to the
various conditions, including the user label, rate, direction,
configuration status, service status, alarm level, endpoint, passing
NE, client, consistency status, service quality and Ethernet service
type. The services satisfying the filtering conditions will be displayed
on the service topology. Note that the filtering results are the
common results by both the navigation mode and the filtering
condition.
Managing Service Domains. The user can create, modify, view and
delete the service domains. The service domain is the service set
within the specific areas. The user can input the user label of the
service domain, or choose the NEs included in the service domain.
Once the NE is chosen, the services included in it are also
determined.
Service topology management. Support customizing service
topology display, customizing alarm bubble display, customizing the
display of consistency status locking/unlocking service topology,
synchronizing coordinates of topology view, exporting service
topology ,configuring service topology map and etc. Synchronize
the layouts in topology view and view pre-merger service.
117
Functions
Description
Service manager: It offers a comprehensive page to view service
details. The topology shows actual route information, working
protection and alarm status of the selected service. Service view
supports NE memberships in several packets, the stop function set
in service creation and the E2E impact of U31 basic data free from
configuration.
Service status detection. Support manually checking consistency
and service status automatic update. The service consistency status
includes: consistent, extended, damaged or abnormal. The
operation status includes: in maintenance, in operation and out of
operation.
Service querying.
Support querying service alarm, performance, associated card,
client service and etc.
Service management. Support setting on/out services,
activating/deactivating services, deleting/removing Services
On service: Services are in normal running, and cant maintain.
Out of service: Services can be maintained.
Activating Services: The user can activate one or several services,
during which the service-related route information will be distributed
to the equipment.
Deactivating Services: The user can deactivate one or several
services, during which the route information of the service will be
deleted from the equipment, but it is still saved on EMS. The route
information can be set to the equipment again by re-activation.
Deleting Services: The user can delete one or several services,
during which the service-related route information is deleted from
EMS and the equipment. The deleted services can be recovered
only by re-creation.
Removing Services: The user can remove one or several services,
during which only the service information is deleted from the EMS.
But the route information of these services on EMS is not affected,
nor the services on the equipment.
Manually Checking Consistency: The user can manually check the
consistency of one or several services, and the detailed checking
results are displayed after the checking is finished, such as
consistency status, inconsistency cause.
118
Functions
Description
TNP (Trail Network Protection) Management. Support automatically
Discovering, creating, querying and deleting TNP group. Support
displaying route, querying actual route and modifying protection
parameter, switching protection group. Support Multi-segment PW
protection, dual-loop dual-node protection and etc.
Abnormal service complete filtering. According to the filtering
condition, it filters the abnormal operations within the entire network,
the results are listed in tabular form in the top right of operating
interface, bottom right is a route map for each filtering results, the
tables and graphics areas have linkage relationships, which is
similar with the service Manager's display.
PTN service cutover management. Support creating, modifying and
deleting cutover plan/group. Support adding service before cutover
and after cutover. Support verification, execution and rollback of
cutover plan.
Service maintenance management: Create and delete MEG group,
configure PTN OAM function, support alarm & bit error insertion, set
the loopback, etc.
Alarm correlate path analysis. In alarm list, choose one alarm, and
support correlate path querying.
Performance correlated path analysis. In performance list, choose
one item, and support correlate path querying.
Report management: Output and print all-network service report,
service statistics report and optical connection utilization rate report.
Navigation: Navigate the user to channel view, L2VPN service
connectivity check and wavelength service overhead setting.
Help: Navigate the user to the Help.
Show path: Create, delete and modify a show path.
Set protection policy: Set the protection policy in tunnel creation,
including best-effort protection and complete protection. Complete
protection means that working tunnel and protection tunnel go
different TMSs, and ring tunnel goes the same TMS.
Automatic rollback after failed tunnel creation: If tunnel creation
fails, automatic rollback is selected, namely, delete the failed
service and related configuration in NM to ensure that NM and
devices do not create damaged data.
119
Functions
Description
Adjust protective linear tunnel route without disconnecting service
endpoints: Modify tunnel route without disconnecting services.
Procedure: Manually switch services to protection tunnel, adjust the
route of working tunnel and manually switch the services back to
working tunnel.
Wizard-style TDM service creation: Enter the menu and
continuously create tunnels and TDM services. It is unnecessary to
create tunnels in advance.
Service topology saving in Ethernet service creation: Filter some
services in Ethernet service creation, namely, display the services of
a specific layer rate in service topology. The TOPO filtering
condition is automatically saved and can be used in the next
creation.
Hybrid Ethernet services: Automatically discover, create, delete and
modify hybrid Ethernet services.
Wizard-style Ethernet service creation: Enter the menu and
continuously create tunnels and Ethernet services. It is unnecessary
to create tunnels in advance. Support wizard-style L3 VPN service
creation.
Support cross-rack protection.
Support dual-transmitting-dual-receiving protection.
9.3
MSTP E2E Management

NetNumen U31 has the following PTN E2E service management function:
Table 9-3 MSTP Service Management Functions

Functions
Description
SDH Service Configuration.
The user can create and modify the end-to-end SDH service. The
E2E Service
Management
service level includes VC11, VC12, VC3, VC4, VC4 service layer
path and VC4-nC. The user can set the service direction, service
ratio, service label, batch-creating number, service quality template,
user label, source node, customer, configuration status, route
constraint and protection information.
120
Functions
Description
Querying Maximum Batch-creating Number (When Creating Normal
Services). The user can set the maximum number of source ports
when maximum number of source ends when creating the service,
and he can make the batch-creation.
Route Constraint.
The user can manually set the route constraint conditions, the
NE/link/service that the working route or protection path passes or is
forbidden to pass, and the tunnel as well.
Calculating Route.
The user can automatically or manually calculate the route. By the
automatic calculation, once the constraint condition is changed,
EMS will automatically calculate the route and display the
calculation result. After the calculation is completed, one way is to
display the detailed routes on the table, including the route table,
source node and tunnel No., and the other way is to display the
route on the service topology in the graphic mode. The routes on the
table and those on the graphic service topology are related.
Service Quality Template Maintenance. Support creating, querying
and deleting service quality template.
Service copy: Copy services in batches.
by NE Resources.
configuration status, service status, client, consistency status,
service quality and Ethernet service type. The services satisfying
the filtering conditions will be displayed on the service topology.
Note that the filtering results are the common results by both the
navigation mode and the filtering condition.
121
Functions
Description
determined.
topology ,configuring service topology map and etc.
protection and alarm status of the selected service.
operation.
Service querying.
Support querying service alarm, performance, associated Ethernet
link, resource usage and etc.
122
Functions
Description
to the equipment.
But the route information of these services on EMS are not affected,
SNCP Configuration.
The user can add and delete the SNCP route into the existing
services.
Abnormal service complete filtering. According to the filtering
condition, it filters the abnormal operations within the entire network,
the results are listed in tabular form in the top right of operating
interface, bottom right is a route map for each filtering results, the
tables and graphics areas have linkage relationships, which is
similar with the service Manager's display.
Querying isolated crossover.
Query the NEs of the whole network, or query the isolated crossover
of designated NEs
123
Functions
Description
Service cutover management. Support creating, modifying and
cutover plan.
Adjusting Services. Support adjusting service end point, route and
SNCP protection.
Repairing Damaged Service.
The user can modify one or a batch of damaged services, and repair
the lost services on the TS cross-connection.
Service Maintenance. Support setting service Loopback, inserting
service Alarm, inserting service error code and protection
changeover of SNCP service.
9.4
MSTP Ethernet E2E Management

NetNumen U31 has the following MSTP Ethernet E2E service management function:
Table 9-4 MSTP Ethernet Service Management Functions

Functions
Description
Creating Ethernet Link.
The user can create the end-to-end Ethernet link. During the
creating process, he can set the service label, source end, capacity,
service quality template, client, configuration status, route constraint
E2E MSTP
and protection information. After creating successfully, 1 Ethernet
Ethernet
link and VC-x bundled by N Ethernet links (N is the set the capacity)
Management
will be formed.
Setting Capacity (When Creating Ethernet Link).
When creating the Ethernet link, the user can set the number of
tunnels and rate bundled on the link, as well as the tunnel capacity
of the Ethernet link.
124
Functions
Description
Route Constraint.
The user can manually set the route constraint conditions, the
NE/link/service that the working route or protection path passes or is
forbidden to pass, and the tunnel as well.
Setting Protection Information.
The user can set the protection information of SNCP service,
including the changeover waiting time, recovery mode and the
recovery waiting time.
Calculating Route.
The user can automatically or manually calculate the route. By the
automatic calculation, once the constraint condition is changed,
EMS will automatically calculate the route and display the
calculation result. After the calculation is completed, one way is to
display the detailed routes on the table, including the route table,
source node and tunnel No., and the other way is to display the
route on the service topology in the graphic mode. The routes on the
table and those on the graphic service topology are related.
Creating EPL/EVPL.
The user can create the end-to-end EPL and EVPL. During the
creating process, he can set the source end, VLAN mapping (when
creating EVPL), the client renting the service, the service
configuration status and service status, the route, the route VLAN
mapping (when creating EVPL), VLAN ID (when creating EVPL),
S-VLAN attribute (when creating EVPL), VLAN ID holding, VLAN
COS holding.
Creating ETREE/EVTREE.
The user can create the end-to-end ETREE and EVTREE services.
During the creating process, he can set the root node, sub-node,
node VLAN mapping, the client renting services, the service
configuration status and service status, the route, VLAN ID (when
creating EVTREE), VLAN ID holding (when creating EVTREE), and
S-VLAN attribute (when creating EVTREE).
125
Functions
Description
Creating EPLAN/EVPLAN.
The user can create the end-to-end ETREE and EVTREE services.
During the creating process, he can set the root node, sub-node,
node VLAN mapping, the client renting services, the service
configuration status and service status, the route, VLAN ID (when
creating EVTREE), VLAN ID holding (when creating EVTREE), and
S-VLAN attribute (when creating EVTREE).
Service Quality Template Maintenance. Support creating, querying
and deleting service quality template.
Service copy: Copy services in batches.
by NE Resources.
configuration status, service status, client, consistency status,
service quality and Ethernet service type. The services satisfying
the filtering conditions will be displayed on the service topology.
Note that the filtering results are the common results by both the
navigation mode and the filtering condition.
determined.
topology ,configuring service topology map and etc.
126
Functions
Description
protection and alarm status of the selected service.
operation.
Service querying.
Support querying service alarm, performance, associated Ethernet
link, resource usage and etc.
to the equipment.
But the route information of these services on EMS are not affected,
SNCP Configuration.
The user can add and delete the SNCP route into the existing
services.
127
Functions
Description
Abnormal service complete filtering.
According to the filtering condition, it filters the abnormal operations
within the entire network, the results are listed in tabular form in the
top right of operating interface, bottom right is a route map for each
filtering results, the tables and graphics areas have linkage
relationships, which is similar with the service Manager's display.
Querying isolated crossover.
Query the NEs of the whole network, or query the isolated crossover
of designated NEs
Service cutover management. Support creating, modifying and
cutover plan.
Adjusting Services. Support adjusting service end point, route and
SNCP protection.
Adjusting Ethernet Link Bandwidth. The user can add/delete the
Ethernet link bandwidth capacity.
Repairing Damaged Service.
The user can modify one or a batch of damaged services, and repair
the lost services on the TS cross-connection.
Service Maintenance. Support setting service Loopback, inserting
service Alarm, inserting service error code and protection
changeover of SNCP service.
9.5
WDM/OTN E2E Management

NetNumen U31 has the following WDM/OTN E2E service management function:
Table 9-5 WDM/OTN E2E Service Management Functions

Functions
128
Description
WDM/OTN
(1) Create OCH service
E2E service
(2) Create ODU service including ODU0, ODU1 into ODU2, ODU3
management
ODU1 into-2C, ODU0-7C, ODU1f, ODU2e, ODU2f, ODU3e1,

ODU3e2, and ODU4;
(3) Create OAC Ethernet services of FE, GE, 10GE, FE100
(1062.5M), FE200 (2125M), FE400 (4G), FE1000 (10G), WDM
DVB-ASI (270M), ESCON, FCON, 10GE, the WAN 40GbE,
100GbE, and HD-SDI;
(4) Create ordinary OAC services of STM1, STM4, STM16, and
STM256;
(5) Create sub-wavelength services STM-16 (M800/M900 CC)
It supports end-to-end optical channel service creation. Users can
configure service direction (specified one-way / two-way service),
user label (user customized rules), A, Z endpoint (selectable port,
low-level time slot, and high level time slot), the customer,
associated protection configuration, and routing constraints.
Create WDM service (automatically create the service layer):
(1) Create OCH service;
(2) Create ODU service including ODU0, ODU1 into ODU2, ODU3
ODU1 into-2C, ODU0-7C, ODU1f, ODU2e, ODU2f, ODU3e1,
ODU3e2, and ODU4;
(3) Create OAC Ethernet service of FE, GE, 10GE, FE100
(1062.5M), FE200 (2125M), FE400 (4G), FE1000 (10G), WDM
DVB-ASI (270M), ESCON, FCON, 10GE-the WAN , 40GbE,
100GbE, and HD-SDI;
(4) Create ordinary OAC service STM1, STM4, STM16, and
STM256;
(5) Create sub-wavelength service of STM-16
It supports end-to-end optical channel service creation. Users can
configure service direction (specified one-way / two-way service)
user label (user customized rules), A, Z endpoint (selectable port,
low-level time slot, high level time slot), the customer, associated
protection configuration, and routing constraints.
Set service user label: It supports manual input of service label. We
can also select the associated default naming rules.
Associated customers: we can set customers of leased service in
the process of service creation.
129
Routing constraints: It supports setting of must-go-through routes

for active and protection, as well as prohibited route constraints.
It supports manual setting of the routing constraint conditions, the
network element, card, port WDM node CC, and specified CTP (with
specified wavelength) that the route goes through. It also supports
setting of network elements that the route is prohibited to go
through.
It supports route clearance, including the clearance of the endpoint
and constraints.
Calculate routes: It supports automatic calculation and manual
calculation of route. Automatic calculation: the network
management will automatically calculate the route and show the
calculation results as long as routing constraint condition is slightly
altered. When calculation is completed, route can be listed in the
form of a table, including routing label, source/destination endpoints,
and channel number. It can also be displayed in graphs of service
topology. The routes in the table are associated with the graphs in
the topologies.
Set the activation status of the service: It supports setting of the
service configuration activation status during the process of service
creation.
Optical layer 1 +1 protection path creation: It supports creation of
optical layer 1 +1 protection path. Protection group can be
automatically configured when service is created.
ODUk 1 +1 protection path creation: It supports ODUk 1 +1
protection path creation. Protection group can be automatically
configured when service is created.
Enhance support for 1 +1 protection based on the creation of ODU
service function. Generate corresponding protection information at
the Concurrently transmitting and preferred receiving node.
It supports bi-directional path protection creation, as well as SNCP
additions and deletions;
WDM creates parameter template: based on WDM layer rate, the
user can create service group template for the specified service.
130
E2E Ethernet service creation: It supports E2E creation of Ethernet

service. During the process of service creation we need to set
service type, select the parameters template, user labels,
customers, select the endpoint, add the existing service layer link,
and node parameters configuration. There will be one Ethernet
service when we successfully create it.
Ethernet services cover EPL, EVPL, EPLAN, EVPLAN EPTREE
and EVPTREE services.
Virtual network element end-to-end service configuration: It
supports searching of end-to-end path.
It supports configuration of various virtual network element border
services. It also supports the use of the virtual network element as
routing site that the service passes by.
It provides display of service route in service view and service
manager.
View wavelength information based on service: In service manager,
we can see the route wavelength information of OCH path.
View alarm information based on service: we can query the current
alarms (including service layer) based on service, history alarms,
and history alarms (including the service layer).
It supports correlation of one alarm with multiple services.
View performance information based on service: we can query the
current performance (including the service layer) based on the
service, history performance, and history performance (including the
service layer).
Service status: the service status is decided based on the alarm of
service make-break. There are three levels of status: in service,
degradation, and interruption, which are corresponding to service
double-pass, single failure and double failure.
Cancel service and delete service: cancel service: delete service
only from the network management. We don't distribute it to the
equipment. The service still possibly works.
Delete service: delete service in the network management. We also
distribute the related configuration to the equipment. The service is
interrupted when it is successfully deleted. Fixed service cannot be
deleted.
131
Consistency status operation: It supports management of abnormal

path.
Damaged SNC: It supports functions of SNC deletion / repair.
Abnormal SNC: It supports features of deletion / adjusting A / Z
endpoint.
Activation / deactivation: It supports path activation / deactivation
status modification
Enter / quit service: It supports enter /quit service status
modification.
Adjust the route: it supports service route adjusting.
Adjust the endpoint: it supports service endpoint adjusting.
Add / delete broadcast path branches: It supports addition of OCH
layer braodcast branch in an end-to-end way. Firstly we need to
select the the OCH service needs a new branch, and then we select
the branch Z endpoints, branch points, and routing constraints.
It supports broadcast branch deletion.
Activation / deactivation of broadcasting service branch: It supports
activation and deactivation of broadcasting branch in an end-to-end
way. The activation / deactivation operation of a branch does not
affect the other branches
Ethernet Service group maintenance: Add or delete EVC service in
EVC service group. Add or delete leave nodes in RMP EVP-Tree
service group. Add or delete UNI in E-LAN
9.6
service.
IP E2E service management

This section gives details of NetNumen U31 network-layer management function. U31
has strong E2E service management (path management) which is more efficient than
single-NE service configuration. It can configure and maintain all services through E2E
management. IP E2E management function includes:
Table 9-6
IP E2E management function
Functional
item
132
Description
Functional
Description
item
Tunnel configuration (static and dynamic)

1. Create the tunnels of different networking modes. The networking
is static or dynamic. Select networking type, protection type,
termination attribute and networking scenario to create dynamic
tunnel, static tunnel, ordinary tunnel, tunnel without termination at
one or two ends, and tunnel protection group.
Automatically calculate and create non-protection tunnel in
FullMesh, H-VPLS and Tree networks.
2. Import existing tunnel templates in tunnel creation. If a user
configures a tunnel template in advance, the system automatically
brings up the parameters of the default template to create a service.
The user can select different templates to create services.
3. Manually constraint tunnel route. The constraint conditions
include allowed/forbidden NE or TMS, and even a designated label.
4. Automatically and manually calculate route. Automatic
calculation: If restrain conditions change a bit, NM automatically
calculates a route and shows a result. After calculation, a table lists
IP E2E service
the routes, including route label and source/destination endpoints,
management
or service topology diagram shows the routes. (Only static tunnel is

supported now.)
5. Bidirectionally set tunnel QOS parameters in tunnel creation.
6. If the protection is needed, TNP should be configured to protect
the attributes.
7. Modify tunnel attributes such as tunnel route point and QOS (The
attributes of IP static tunnel and non-termination tunnel cannot be
modified).
Ethernet service configuration (including L2 VPN service):
1. Create E2E Ethernet service. Ethernet services include
EPL/EVPL, EPLAN/EVPLAN, and ETREE/EVTREE. The creation is
based on existing PW/MSPW or tunnel. PW, MSPW and PW
protection group are created automatically. E(V)PLAN is applied to
manual application/FULL MESH/H-VPLS, and E(V)PTREE to
manual application /tree.
2. Modify Ethernet service attributes such as Ethernet service
endpoint and route. PW/MSPW and PW protection group
information can be modified at the same time.
133
Functional
Description
item
L3 VPN service configuration:

1. Create E2E L3VPN, RD configuration, RT configuration, and LSP
binding configuration, and generate single-NE L3VPN service
instance at all PE nodes.
2. Modify E2E L3VPN information such as L3 port access, RD, RT,
and LSP binding.
TNP management:
1. Automatically discover all-network path protection subnet
according to protection group and service information.
2. Query configuration details of the all-network path protection
subnet.
3. Create a path protection subnet and support tunnel and PW
protection.
4. Delete TNP protection subnet and select whether to delete
protection service, single-point protection group information and
OAM together.
5. Show working and protection routes in graphics in one topology.
6. Query an actual route and highlight it on GUI.
7. Support manual protection switching.
8. Modify protection subnet parameters such as protection group
name, WRT and return mode.
9. Verify protection group data loss and check the consistency
between TNP data and protection group data.
10. Verify the consistency between protection subnet and protection
group. Check the consistency between TNP data and protection
group data according to single-point data or TNP data.
9.7
PTN and IP cross-domain E2E service management

NetNumen U31 provides the unified E2E service management platform to support
cross-domain E2E service management in a PTN and IP hybrid network. The function
includes:
134
Table 9-7
PTN and IP cross-domain E2E service management
Functional
Description
item
Tunnel
configuration
Create dynamic tunnel in a hybrid network.
Ethernet
service
Create and modify E2E Ethernet services, including EPL/EVPL,
(L2VPN
EPLAN/EVPLAN and ETREE/EVTREE.
service)
configuration
9.8
L3VPN service
Create and modify E2E L3VPN service, including RD configuration,
configuration
RT configuration, and LSP binding configuration.
PTN
and
MSTP
cross-domain
E2E
service
management
cross-domain E2E service management in a PTN and MSTP hybrid network. The
function includes:
Table 9-8
PTN and MSTP cross-domain E2E service management
Functional
item
Description
Automatically
discover
MSTP and
PTN
cross-domain
Automatically discover services across MSTP and PTN networks,

including E1/EPL(including single/dual-node
interconnection)/EVPL(including single/dual-node interconnection).
service
Create
cross-domain
E1 service
Create cross-domain E1 service, PW and PW protection group in

MSTP and PTN hybrid network.
135
Functional
Description
item
Functions
supported by
cross-domain
service
9.9
MSTP and PTN cross-domain service supports the same functions

as single-domain service: delete, release, modify, activate,
deactivate, insert loopback, etc.
MSTP and WDM/OTN cross-domain E2E service

management
cross-domain E2E service management in a MSTP and WDM/OTN hybrid network. The
function includes:
Table 9-9
MSTP and OTN/WDM cross-domain E2E service management
Functional
Description
item
Automatically
discover
Automatically discover services across MSTP and WDM networks.
MSTP and
The hybrid networking scenario is usually MSTP network A - WDM
WDM
network B - MSTP network C. Automatically discover services
cross-domain
between A and B, between B and C, and between A and C.
service
MSTP service
configuration
Create an E2E A B C service in the above scenario. Its service
in MSTP/WDM
type is the same as that supported by SDH/MSTP.
hybrid network
9.10
Cross-domain E2E Service Managemetn of CTN

and WDM/OTN
NetNumen U31 network management system provides integrated E2E service
management platform to implement cross-domain E2E service management in the
136
scenario with hybrid networking of CTN and WDM/OTN. The specific functions are as
follows:
Table 9-10
Cross-domain E2E service management of CTN andOTN/WDM
Function item
Fiber
configuration
and service
creation
Description
It can implement E2E service management of CTN network
element. Create optical connection between CTN and OTN. It can
be integratedly displayed in the physical topology.
137
10
System Security
10.1
Physical Security
NetNumen U31 hard disk uses RAID technology for data security.
NetNumen U31 also adopts the remote DR (Disaster Recovery) backup to recover the
system destroyed in the disaster. The server is configured with redundant power supply
and employs UPS to prevent power fault. The local high-availability solution can avoid
the accidental breakdown caused by manual operations.
10.2
Network Security
NetNumen U31 isolates itself from NE network and external network with multiple IP
network sections and network firewall, so as to protect network management system and
NE network. Furthermore, NE NetNumen U31 supports IPSec, SSH, SNMP v3, SFTP,
SSL(V3.0)/TLS, IPv6, Syslog, RADIUS, SSH-2, AES-128, aes128-ctr, aes192-ctr,
aes256-ctr, Blowfish, 3DES, etc.
10.3
System Security
NetNumen
U31
adopts
Windows
XP/Windows7
as
client
and
Window2003/Windows2008/Solaris as server OS (Operating System), and enhances

their security in terms of system hardening policy, system virus base and system firewall.
NetNumen U31 formulates the system hardening policy and supplies relative script
and checklist for the user to execute. The policy is: close insecure ports, terminate the
unused service, close the unused shared directory, adopt powerful password, patch
system in time, etc.
NetNumen U31 employs Microsoft SQL Server 2005/2008/Oracle with high security.
138
10.4
Application Security
In order to protect NM operations, NetNumen U31 security management module
designs role-based authority security model, and uses authorization, authentication,
audit and security management policy to assure operation security.
10.4.1
Security model
NetNumen U31 offers the role-based authority and domain fine-grain security model to
facilitate network operation and maintenance, as shown below:
Figure 10-1 Role-based authority and domain fine-grain security model
User
Role
Role set
Department
......
Role 1
Role N
Log
management
System
management
Log
management
System
management
......
......
Operating
right 1
Management
resource 1
Operating
right N
Management
resource N
NetNumen U31 divides operations into several levels such as addition, deletion,
modification and query, and can authorize atomic operation and thick-grain operation in
operation item authorization. For example, atomic operation items include alarm
confirmation, alarm clearance, alarm query, software activation, NE creation, NE deletion,
139
etc; thick-grain operation items include configuration management, performance

management, fault management, etc. Resource item refers to the region and NE object
in the network. It divides the above objects into several levels based on geographical
domain or service domain. Role authority consists of operation and resource authorities.
Role set consists of multiple roles, and a user belongs to one or several roles, or one or
several role sets. User group consists of multiple users.
10.4.2
Access control and authorization

NetNumen U31 adopts the role-based authority and domain authorization mechanism
and sets the authority of management object and management operation through role
object. It can separately authorize each management operation of management object.
The system makes the access control according to the role of a user, and sets access
control.
1.
Set login duration, account, password expiration date, and failed login times to
manage user authority expiration.
2.
Set user login IP address, login date and time.
3.
Lock a user. When failed login times exceed the limit, the user will be locked and a
security event will be triggered to report. The locked user is unlocked by the system
administrator or when the preset time limit reaches.
4.
10.4.3
Modify the password on GUI and check weak user password.
System authentication
NetNumen U31 offers the centralized authentication for the managed NEs. All user
names, passwords and roles can be stored into the system.
1.
Support client access restriction based on login IP address, login date and time.
2.
Support password-based authentication. Passwords are stored and transported in

the encryption mode.
3.
In terms of northbound interface, TL1 interface supports the encrypted

authentication to stop illegal upper-layer NM access system
140
10.4.4
System audit
NetNumen U31 supports log management and collects such information as system log,
security log and operation log. With these logs, the system can record all operation
details of all users, including user ID, login time, logout time, all operation contents,
operation time and operation results. Log management provides the friendly query
interface for users.
10.4.5
Security management policy

NetNumen U31 provides many security management means and mechanisms to
maintain system security.
1.
Customize security policies, e.g., screen locking time, security event report and
password policy.
2.
Support system administrator role.

i.
System administrator can monitor all online users and view their operations.
ii.
System administrator can force the logout of any other users.
iii.
System administrator can view user locking and unlock the locked user.
iv.
System administrator can add, delete, modify and query the authority of any
user.
141
11
System Reliability
11.1
NE data protection
NE NCP saves all of the configuration data of NE itself, including time, cross, card
attribute, protection, and alarm property setting etc., all of the data save in the flash
memory of NCP card, flash memory can support data saving when out of power.
NetNumen U31 saves NE configuration data also, supports upload, download,
comparison of consistency and clear to NCP database, and offers strict mechanism to
guarantee the consistency between U31 data and NCP configuration data.
Additionally, U31 offers NE database backup restoration functions. In case of lost of NE
database, the backup NE database can be restored on NE. It should be noted that only
the latest backup database can be restored.
11.2
NetNumen U31 single-host data protection

1.
NetNumen U31 supports the export and import of service configuration data with
script mode. Back-up of U31 database. Database back-up means that back-up user
tables, system tables even all of the database to hard-disk files, tape machine or
magnetism/compact disc periodically. Once the database system is destroyed, it
can resume from the back-up data. U31 system management supports database
back-up management and automatically back-up periodically.
2.
Disk mirror data back-up. All of the operations on active disk are synchronous with
standby disk. Once the active disk fails, NM system will adopt the standby disk.
3.
Disk array Data backup provides protection in raid level, such as: Raid1, Raid5 and
Raid10. It realized data protection from hardware aspect.
4.
Data migration. NetNumen U31 supports the migration of log files in database
(such as history alarm, history performance and operation log etc.) manually or
142
periodically. On the one hand, back-up the log files; on the other hand, it can
prevent the log file capability getting larger, which will influence the performance of
NM system.
11.3
Active/standby server data protection

NetNumen U31 server supports the dual-system backup configuration.
The dual-system backup employs two servers to execute one service. One is active
server and the other standby server. When the system runs normally, active server
serves application system and standby server monitors the operation of active server
(active server also checks whether standby server runs normally). When active server
goes wrong and cannot support the operation of application system, standby server will
take over the work of active server to support key application service and ensure
continuous system operation.
NetNumen U31 key module adopts the load control design, software design adopts the
fault tolerance design and data adopts the distributed storage to assure reliable system
operation.
As a core application system that monitors and manages the network, the NMS must run
stably on a long-term basis. Stable system running is subjected to various factors,
including:
Hardware platform stability
Software system stability: Such as system software (operating systems, database

systems and virtual machines) and NM applications
Network status and stability.
System running environment (temperature, humidity, power supply, and natural

disasters)
Therefore, to enable the system to run stably, the NetNumen U31 provides hot
redundancy backup and supports 1:1 backup.
143
1.
Local dual-system backup

The local dual-system backup solution is generally implemented on a LAN with dual
computers + HA cluster fault tolerance software + disk array. The networking
diagram is shown in Figure below.
Proprietary Confidential
Figure 11-1 Local dual-system backup Solution

Reliability
Solutions-Local Dual Host Backup
NM Server(Main)
NM Server(standby)
NM Client
LAN
NM Client
Disk Array
The
Themanaged
managednetwork
network
Local backup solution for system
Local dual host backup solution implements by dual host + HA dual host error tolerance software
+ disk array. Main and standby host share the database system locates on disk array to ensure
the consistence of data on main and standby. Disk array is configured in RAID (0+1) to guarantee
In this hot backup solution, the active server and the standby server are in the same
data reliability.
LAN, and connected to the same disk array, where the database generally resides.
Normally, the active system is managed oriented to the network, while the standby
system is in hot backup. The active server and the standby server monitor each
others status through the heartbeat line. When the standby server discovers that
the active server has a fault (such as system breakdown), the NM applications
(including the database system) are handed over to the standby server through the
HA dual computer fault tolerance software.
When the standby server detects that the active server has returned to normal, they
share the database system in the disk array to ensure the data on the two servers
are consistent. The disk array is configured as RAID1/RAID5/RAID10.
2.
144
Remote dual-system backup
The remote dual-system hot backup solution is generally implemented with the
active NM server system + HA cluster fault tolerance software + standby NM server
system. The networking diagram is shown as below.
Proprietary Confidential
Figure 11-2 Remote dual-system backup Solution

Reliability
Solutions-Remote Dual Host Backup
NM Server(Main)
NM server(standby)
Private IP
network
NM client
The
Themanaged
managed
network
network
NM client
Remote dual host backup solution for system

Remote dual host backup solution is implemented by main network management server system
+ HA dual host error tolerance software + backup network management server system, Usually, a
The network
active and
standby
NM
server
systems
havenetwork
the same
configuration,
and both
subordinate
center
can be
used
to backup
upper
central
server offsite.
use RAID1 mirroring for redundancy backup of data and system.

Normally, the active system is managed oriented to the network, while the standby
system is in hot backup. The active system and standby system monitor each
others status through the IP network. To ensure reliability and stability, the
dedicated IP network is usually used for communication between the two systems.
When the standby server detects that the active server has a fault (such as system
breakdown), the NM applications (including the database system) are handed over
the standby server through the HA dual computer fault tolerance software.
The active system and standby system exchange data with each other through the
dedicated IP network. When the active system is working, it backs up the data
changes of the NMS to the remote standby system to ensure data consistency
between them. When the NM application is handed over to the standby system, the
services of the NMS undergo a seamless changeover since the standby system has
the same data as the active system. At the same time, the standby NMS backs up
145
the related data to the active NMS through the dedicated IP network. Thus,
wherever the NM application runs, the active NMS and standby NMS always have
the same data.
146
12
System Networking
12.1
Networking Mode
The networking is divided into local networking, remote networking and mixed networking
according to the location between NetNumen U31 and NE.
12.1.1
Local networking
LAN networking is the simplest and the most commonly used networking in the network
management system. In this networking, NetNumen U31 server, client and NE are in
one LAN and are interconnected via Ethernet. NetNumen U31 and its NE are in one
physical location. LCT is in charge of local operation and maintenance of the NE, and
NetNumen U31 manages the devices in the entire network.
12.1.2
Remote networking
Remote networking can be adopted when client and NetNumen U31 server are not in
one LAN. For remote networking, basic topologies of the network and their principles are
the same. They use specific transport equipment to transmits data on WAN, router for
the access from WAN to LAN, and TCP/IP for the communication among NE, server and
client, so the remote communication supported by transport equipment and router can
adopt NetNumen U31 remote networking. Client can be located at remote equipment
room and can divide management domain to manage local equipment. Remote terminal
is not directly oriented to the managed equipment.
As per different communications ways between remote network management systems,
NetNumen U31 provides different remote access solutions to support 2M private line,
DDN private line, ISDN, PSTN and Ethernet modes.
147
12.1.3
Mixed networking
The actual networking sometimes uses the mixed networking which includes local
networking and remote networking.
Client is divided into local client and remote client. It operates and monitors NE on GUI
and is connected to server via LAN or metro network. Two types of clients have the same
operation capability.
Figure 12-1 NetNumen U31 typical networking
12.2
Client
12.2.1
Single-client
It is the most basically and most common application mode. The Client, Server and
Database may run either on the same computer or separately on different computers
depending on the amount of managed equipment and the process capability of the
computer.
148
Figure 12-2 The single-Client and single-Server networking mode
12.2.2
Multi-client
One Server allows logon of multiple Clients. It assures the clients of data
synchronization.
This structure is usually applied in the case that multiple operation terminals (Clients) or
display terminals are required by users, and the Clients might be distributed in various
areas, so some of the Clients need to log on the Server remotely. In this way,
management of upper layer NM can also be accessed, with a northbound interface
module needed.
Figure 12-3 The multi-Client and single-Server networking mode
149
12.3
Server
The server sub-systems can apply centralized deployment, distributed deployment,
depending on different engineering environments.
12.3.1
Centralized deployment
As shown below, in centralized deployment, the servers running on a single host.
Centralized network management is suitable for small-scale network to meeting the
network management requirements with minimized cost.
Figure 12-4 NetNumen U31 centralized deployment
12.4
Network Element Networking and Monitoring

Management
The physical channel of ECC networking between ZTEs SDH/MSTP equipment adopts
DCC. Different devices can support DCCr, DCCm and DCCr+DCCm mode respectively.
And protocol of network layer adopts standard IP protocol, route protocol is OSPF, offer
150
perfect OSPF route protocol function, such as IP sub-network division, route circle
avoiding, route auto-protection, fast route rebuilding when fiber is cut off and so on.
PTN equipment manages network equipment via service channel. The inband mode
adopts MCC packet to transfer data between NM and equipment or employs
network-layer OSPF protocol.
In PTN network, there should be less than 512 network elements in single NM subnet.
OTN equipment manages network equipment via GCC bytes or OSC. The routing
protocol is dynamic OSPF protocol.
IP device can build special DCN management network in outband channel mode. It does
not need to take up service tunnel. Or service port can be used for connection in inband
channel mode. Build network channel via dynamic routing protocol like OSPF.
12.5
Network Bandwidth Demand

In order to ensure good data communication, the bandwidth for EMS and equipment
management has the following requirements:
Table 12-1 Bandwidth requirements

Item
Bandwidth between client
Requirements
At least 2M
and server
SDH/MSTP Network
At least 2M
and gateway NE of
PTN Network(less than 128
At least 4M
transmission
NEs)
PTN Network(more than
At least 10M
128 NEs and less than 512

NEs)
WDM/OTN Network
C = NPB/G
and IP NE
(See the following notes)
Bandwidth for data
At least 10M
At least 10M
151
Item
Requirements
synchronization between
active and standby nodes
Bandwidth for EMS and up
At least 2M
layer system
Notes:
The bandwidth demand between the NetNumen U31 and IP NEs mainly includes:
Link polling: This traffic is small with only several bytes. It depends on the polling
cycle and the number of managed NEs.
Configuration operation: This traffic is not large, generally with a dozen or more
bytes. The operation frequency is random.
Performance data: This traffic is large. The operation frequency depends on the
statistics cycle.
Alarm data: This is burst traffic. It depends on the running status of and the number
of managed NEs.
Based on the above traffic data for single NEs, we can use the following empirical
formula to calculate the bandwidth required by a NM channel:
C = N P B/G
Where,
C: Traffic convergence value. This is the bandwidth necessary for ensuring service
quality and avoiding congestion in normal operation.
N: Number of NEs;
P: Concentration ratio (percentage of concurrent operation NEs);
B: Single NE NM bandwidth;
G: Gain factor, which represents the actual consumption ratio of user bandwidth. It can be
interpreted as an empirical factor. Generally speaking, a narrowband with its slow rate
152
has more time periods of traffic created when operating with NEs, and its gain factor is
usually smaller than that of a broadband. In traditional computation, we set the gain factor
for a narrow band between 4 and 7. In the broadband network, the gain factor is larger.
Based on the above empirical formula (C=NPB/G), we can calculate the bandwidth
required by the NM channel for 200 NEs:
C = 200 10% 200/8 = 500kbps
Where,
N: The number of NEs is 200.
P: The probability of concurrent operation NEs is 10%.
B: The maximum value of 200kbps is set for the bandwidth occupied by NE operation.
G: The gain factor is set to 8 (For a narrowband, it is generally 4 ~ 7. Since the
NetNumen U31 is used for the broadband network, here it is set to 8.).
153
13
Technical Specifications
13.1
Overview of equivalent NE calculation

At present, ITU-T or other standard organizations have not given uniform definition to
equivalent NE, and meanwhile the concept of equivalent NE is introduced instead to
describe physical NE, network size and NM management capability in unification.
Therefore, equivalent NE quantities of various vendors are of certain difference. In this
technical instruction, unless a special remark is given, NE quantity managed by NMS is
the equivalent NE quantity defined in that case. Some definitions are given for
convenience before describing the calculation of equivalent NE:
Physical NE: equipments (may contain multiple sub racks) an equipment main control
software system (including active/standby systems) can manage.
NE capacity: perspective to NM management, it is the quantization index of information
quantity, complexity for internal management of a physical NE.
Equivalent NE: refers to NE whose NE capacity is normalized.
NM management capability: NE quantity managed by NM, which is calculated in the
unit of equivalent NE.
Criterion of management capability: in the worst case, the subnet quantity and
equivalent NE quantity that it can manage within the operation and response time
tolerable by the user. The worst case refers to the condition that there are large amount
of alarms and performance data to report, leading to busyness of communication and
CPU process.
154
13.2
Rapid calculation table for equipment equivalent

NE
In typical configuration, rapid comparison table of equivalent NE is provided for easy
calculation.
Table 13-1 Rapid table of equivalent NE

Type
PTN
MSTP
Module
Equivalent NE
ZXCTN 6100
ZXCTN 6110
ZXCTN 6120
1.5
ZXCTN 6130
1.5
ZXCTN 6200
ZXCTN 6220
2.5
ZXCTN 6300
ZXCTN 6320
ZXCTN 9002
ZXCTN 9004
ZXCTN 9008
ZXMP S385
4.5(without ASON
6(with ASON)
ZXMP S390
ZXMP S380
3.5
ZXMP S330
2.5
ZXMP S325
ZXMP S200
ZXMP S360
2.5
ZXMP S320
ZXMP S100
0.8
ZXONE 5800
6(without ASON)
8(with ASON)
ZXONE 5800E
2.5
155
Type
Module
Equivalent NE
WDM/OT
ZXWM M900/
OTM / OADM 80*10G
ZXMP M800
4.5
OTM / OADM 40*10G
OADM
4.5
ROADM
0.5
OLA
OTM 8*2.5G
0.5
OLA
ZXWM M920/
Nt * 2
Nt indicates transport subrack
ZXMP M820/
+ Nx
number
ZXMP M720
*2
Nx stands for CX subrack
ZXMP M600
number
OTM/OADM/ROADM, (dont
configure WASON)
1.5*(
Nt * 2
number
+ Nx
*2)
number
OTM/OADM/ROADM,(Configur
e WASON)
ZXONE 8000
0.5
OLA (Configure WASON)
OLA(Dont configure WASON)
Nt * 2
+ Nx
number
*2+
Nx_1
number
*3 +
Nx_1 stands for one single
Nx_2
layer switch subrack
*6+
Nx_3
*9
Nx_2 stands for dual-layer

switch subrack
Nx_3 stands for triple-layer
switch subrack
OTM/OADM/ROADM, (Dont
configure WASON)
156
Type
Module
Equivalent NE
1.5*(
Nt * 2
number
+ Nx
*2+
number
Nx_1
Nx_1 stands for one single
*3 +
layer switch subrack
Nx_2
*6+
Nx_3
*9)
Nx_2 stands for dual-layer

switch subrack
Nx_3 stands for triple-layer
switch subrack
OTM/OADM/ROADM,
(Configure WASON)
ZXMP M721
0.5
OLA (Dont configure WASON)
OLA (Configure WASON)
N*1
N stands for AC/DC subrack

number
Router
ZXR10 T8000-8/ T8000-16

ZXR10 M6000-8/ M6000-16
/ M6000-8S
10
6
ZXR10 M6000-3S/ M6000-5S
ZXR10 T1200/T1200 BMSG/
ZXR10 T600/ T600 BMSG

ZXR10 T1212/ T1216
ZXR10 T128/ T64E
ZXR10 GER/GER04/GER02
ZXR10
1809/1822/1822E/1842/1842R
ZXR10
2822/2822R/2842/2842R/2882/
2882R/2884
ZXR10
3822/3842/3844/3882/3884
ZXR10
T16S/T16C/T32C/T64C/T160
157
Type
Module
ZXR10
GAR2604/2608/3608/7208
Medium &
ZXR10
high-end
8905/8908/8912/8905E/8908E/
Switch
8912E
Equivalent NE
4
6
ZXR10 8902/8902E
ZXR10 6905/6908
ZXR10 6902
ZXR10
T40G/T64G/T160G/T240G
ZXR10
5116E/5128E/5128E-FI/5152/
5224/5228/5228-FI/
5252/5916E/5928/5928-FI/5928
-PS/5928E/5928E-FI/5952/5952
E
ZXR10 5950/5250
ZXR10 5228A/5252A
ZXR10
3928A/3928A-FI/3928A-PS/395
2A/3228A/3228A-EI/3228A-FI/3
252A
ZXR10 3950
ZXR10 3206/
3226/3228/3226-FI/3252/3906/3
928/3928E/3928E-FI/3952/3952
E
ZXR10 59S STACK
Calculated according to the number of

stacks
Low end
ZXR10
Switch
5109/5116/5116-FI/5116-SI/512
4/5124-FI/5124-SI
ZXR10 5009
ZXR10
2920-SI/2928-SI/2952-SI/2936FI
158
Type
Module
ZXR10
Equivalent NE
2
2909-SI/2909-FU/2918-SI/2926SI
ZXR10
2609-LE/2818S-LE/2826S-LE/2
852S-LE
ZXR10
2609A/2618A/2626A/2826A/28
26A-PS
ZXR10 2609/2609-FU
ZXR10 2809/2809-FU/2818S/
2826S/2852S
ZXR10 2850
ZXR10 2826E/2618/2626
ZXR10
2609-EI/2818S-EI/2826S-EI
ZXR10
2910E-PS/2918E/2918E-PS/29
28E/2928E-PS/2952E
ZXR10 2950
ZXR10 29S STACK
Calculated according to the number of

stacks
UAS
ZXUAS10800E
ZXUAS 10800
ZXUAS10400/10600/2500S
13.3
Network Management Capability
13.3.1
Management Capacity and Configuration

Due to unified calculating method, the number of the equivalent network element can be
calculated no matter the device type in the network. The network scale can be defined by
the equivalent network element quantity in the managed network. Different scales of
networks can be managed by the network management system in the same scale. Or it
159
can use flexible networking mode like hierarchical management to make the network
management system more extensible.
NetNumen U31 totally defines five scales of network management system. The
definition standard is as follows.
Table 13-2 NetNumen U31 Scale and Configuration

Scale
Equivalent
Hardware
OS
Database
Windows Server
MS SQL Server
2003/2008
2005/2008
NE number
Small
300
CPU: Dual Core

RAM: 8G
Small-Me
1000
dium
Standard
CPU: 2 * Dual
Windows Server
MS SQL Server
Core or Quad
2003/2008
2005/2008
Core
Enterprise
RAM: 8G
Medium
Large
Extra
3000
8000
20000
Large
CPU: 2* Quad
Windows Server
MS SQL Server
Core
2003/2008
2005/2008
RAM: 16G
Enterprise
CPU: 4* Quad
Windows Server
MS SQL Server
Core
2003/2008
2005/2008
RAM: 24G
Enterprise
CPU: 4* Six Core

RAM: 48G
Windows Server
MS SQL Server
2003/2008
2005/2008
Enterprise
Table 13-3 NetNumen U31 Scale and Configuration

Scale
Equivalent
Hardware
OS
Database
NE number
Small
300
CPU: 2* Quad
Core
Solaris 10
Oracle 10
Solaris 10
Oracle 10
RAM: 16G
Small-Me
dium
1000
CPU: 2* Quad
Core
RAM: 16G
160
Scale
Equivalent
Hardware
OS
Database
NE number
Medium
3000
CPU: 2* Quad
Core
Solaris 10
Oracle 10
Solaris 10
Oracle 10
Solaris 10
Oracle 10
RAM: 32G
Large
8000
CPU: 4* Quad
Core
RAM:64G
Extra
20000
Large
CPU: 8* Quad
Core
RAM: 128G
NetNumen U31 is proposed to use hardware platform integrating client and server
together to reduce costs.
13.3.2
Number of Clients
The maximum number of clients connected by a NM server is 200.
13.4
Software Performance
13.4.1
System response time
NetNumen U31 response time to user operation is less than 3 seconds in normal
operation and less than 30 seconds in abnormal operation (frequent system alarms,
etc.).
Average alarm response time (from NE alarm appearance to EMS alarm display)
does not exceed 10 seconds.
Average response time (from alarm report to alarm display at the client end) does
not exceed 3s.
Note: When the system is fully loaded, alarm response time should not be more than 150%
of the above indexes.
161
Timing precision of NE collecting alarm/performance data is 1s and the floating

number in the program has 3 digits.
13.4.2
Active/standby NM performance
In the hot backup, automatic switching time between active and standby NM is less than
10 minutes.
13.4.3
Data Storage Capacity

The data storage capacity on EMS:
Alarm data storage time: Users can configure this parameter, which is defaulted to 6
months.
Performance data storage time: Users can configure this parameter, which is
defaulted to 6 months.
System log storage time: Users can configure this parameter, which is defaulted to
6 months.
Security and operation log storage time: Users can configure this parameter, which
is defaulted to 6 months.
13.5
Power supply Index

The equipment room must be equipped with UPS or inverter and power generator.
Different sockets should have clear signs.
The indexes for AC power are as below:
Three-phase power: 380 V10%, 50 Hz5%, wave shape distortion <5%
Single-phase power: 220 V10%, 50 Hz5%, wave shape distortion <5%
The voltage wave shape distortion of backup power generator is <10%.
162
13.6
Environmental Index
The environmental requirements for equipment room are as follows:
Table 13-4 Temperature and humidity index

name
13.7
Working condition
Temperature
+5 ~+35
Humidity
15% RH~93% RH
Reliability Index
Definition of fault: The common fault means that the fault just affects a part of functions in
a system, but the system can still operate normally. The severe fault means that the fault
affects the whole system and disables the system to operate normally.
Software:
The calculation formula of MTTF is:
Of which: K is the empiric value, which is about 200; E is the total of failures in program
before test; E1 is the total of failures corrected during the test; and I is total of program
commands.
According to the formula and empiric value:
The NM continuous MTTF>=1200 hours; and the continuous mean time without severe
fault should be more than 180 days.
163
The maintainability demand: MTTR <= 0.5 hour.

MTTF=1200hrs, MTTR=0.5h. The time R of the delay in the preparation of maintenance
is 4 hours.
Availability: A = MTTF/(MTTF+MTTR+R) = 1200/(1200+0.5+4) = 0.99626;
Unavailability: A1 = 1 - A =0.00374;
Since active/standby sites can backup each other, the unavailability is minimized.
Considering others fault caused by the active/standby mode, the fault coefficient is
B=1.01.
Unavailability time
@A1 = A1A1B =0.00867*0.00867*1.01=0.000014127476
Availability time
@A2 =1-@A1 = 0.99999
Thus, annual mean time to failure should be 365*24*@A1= 0.12375hr. = 7.425minute.
Hardware:
It is ensured by the reliability of PC. The MTBF of PC >= 30000 hrs. If the time to
maintenance is estimated, the annual mean time to failure calculated on the basis is
about 0.5 hr.
Thus, the conclusion is:
Weekly serviceable time W = 167.9832 hrs./week.
Annual total of fault should be less than X = 6 times (including recoverable fault).
Every fault time should not exceed Y = 0.5 hr.
164
Supposed that The time R on the way and in the preparation of maintenance personnel is
10 hours.
Annual accumulated fault time should not exceed Z = 50 minutes.
165
14
LCT management
LCT (Local Craft Terminal) is used for equipment maintenance. It is directly connected to
NE via network interface to monitor the working status of NE and provide the
configuration and maintenance function of a single NE. NetNumen U31 LCT is the
local control terminal in U3 network management series and has the management
functions of a single NE.
Overview to LCT NM functions:
Use the free database as the database supporting system.
LCT NM is accessed with the authority of central NM. When active NM authorizes,
NM just allows LCT with default manager identity to log in and manage, which
allows only one valid LCT to exist.
LCT does not make the active/standby NM switching.
NetNumen U31 LCT is local maintenance terminal managing SDH/MSTP, PRN and
WDM/OTN devices. It has the following services:
SDH and PTN device configuration management functions of NETNUMEN U31

LCT include:
Network element communications management includes communications

between subracks, communications between NEs, and management of static
route between NE.
Automatic module discovery. It discovers and manages modules which are

running on the device without being configured on NM.
Clock source configuration. Support query of the configuration of entire

network clocks.
Clock management. Support clock source setting, query, switchover and

recovery, etc. Support standard SSM byte management and clock protection
protocol management with ZTE self-owned intellectual property.
166
Interface configuration. Support the configuration of attributes of SDH optical

interface, Ethernet port, VCG port, ATM port, link aggregation port, VLAN
interface, IP interface and MLPPP interface.
Protocol configuration. Support the configuration of protocols related to SDH

and PTN devices. Support the configuration of spanning tree protocol, IGMP
Snooping, OSPF, ARP, LDP and BGP protocols.
Protection configuration. Support module protection, multiplexing segment

protection, SNCP protection RPR ring protection, PTN line protection , ring
protection, dual-homing protection, etc. Support manual switchover setting and
protection status query.
SDH service configuration. Support timeslot cross-connected configuration.

Enable cluster to cluster, branch to cluster, cluster to branch and branch to
branch service configuration. Support unidirectional and bidirectional service
setting, support text-based query and timeslot configuration.
Data service management. Support the configuration of Ethernet data module

like EPL, EVPL, EPLAN and EVPLAN, as well as the attributes of Ethernet
port. Support ATM service management and RPR protection management.
PTN service configuration. Support the creation, modification and deletion of

LSP, PW, CES service, ATN service, L2 VPN service and L3 VPN service.
Consumption and consumption cross connection. Support the configuration,

query and deletion of SDH consumption byte cross connection.
QOS configuration. Support the configuration of QoS, HQoS, including the

configuration of ACL, traffic speed restriction and discarding policy, etc.
OAM configuration. Support the configuration of OAM feature, including

MPLS-TP OAM EFM OAM and CFM OAM.
SDH and PTN device maintenance management functions of NETNUMEN U31

LCT include:
Support NE alarm query and filtration.
167
Support NE performance query and filtration
Alarm shield
Performance shield and threshold setting.
Set port loopback. Query all loopback ports.
Insert alarm and error code.
1:N branch protection switchover, cross-connected 1+1 protection and clock

board 1+1 protection management.
Module soft reset, module hard reset, NCP reset.
Branch retiming.
ALS setting (automatic laser breakdown)
Query NCP time
Segment consumption, channel consumption query and setting
Automatic failure location.
Packet mirroring management.
Support CC test, LT test, LB test, LM test, DM test and AIS test, etc.
WDM/OTN device configuration management functions of NETNUMEN U31 LCT

include:
168
Clock source configuration
NE time management
Channel management
Fan management
J0 consumption configuration
OTN consumption configuration
GCC byte adoption method configuration
FEC mode configuration
Data module cluster activation configuration
Ethernet port attribute configuration
FC remote activation configuration
Module physical layer transparent transmission configuration
Service type configuration
Aggregation service uplink and downlink configuration
Data service configuration
Service mapping configuration
Cross connection configuration
ROADM system wavelength configuration
Configure APS communications status
Configure module APC
APC condition activation configuration
Protection mode configuration
Port AOSD activation
DEG condition activation
Fixed attenuator
Module power consumption adjustment
169
170
Laser setting
Optical switching board switch configuration
RPOA subsystem
Optical power consumption management
OPM setting
DGE basic attenuation value adjustment
DRA pump wavelength power consumption adjustment
Attenuation adjustment
Attenuation adjustment activation setting
Configure period for automatic wavelength adjustment
DLI status configuration setting
Subwavelength segment homing configuration
Wavelength adjustment tuning
Protection group configuration
Protection group information query
Protection switchover command
Configure module IP address
Configure multicast route
Configure port initiation
Set color compensation
AIS activation configuration
Backplane setting
Active/standby mainboard binding
WASON node configuration
NNI transmission interface configuration
TE link attribute configuration
Configure information of control plane wavelength group
Management plane synchronizes control plane data
Control plane running topology query
Fiber connection number comparison
PCE node configuration
PCE control interface
PCE automatic discovery attribute configuration
WDM/OTN device maintenance management functions of NETNUMEN U31 LCT

include:
Module software management and update
Loopback
Module communications setting
Insert alarm
Insert error code
Set key module data
Set module register
Reset module
171
172
Determine level modulating mode
Active and standby switchover
NCP backup recovery
AppA Standard and Protocol Compliance
ITU-T recommendations on TMN concepts and function descriptions:

ITU-T M.3000 Overview of TMN Recommendations
ITU-T M.3010 Principles for a telecommunications management network .
ITU-T M.3013 Considerations for a Telecommunications Management Network
ITU-T M.3020 TMN interface specification methodology .
ITU-T M.3200 TMN management services overview .
ITU-T M.3300 F Interface Requirements
ITU-T M.3400 TMN management functions .
ITU-T recommendations on communications protocol stack:

ITU-T Q.811 Low layer protocol profiles for the Q3 interface .
ITU-T Q.812 Upper layer protocol profiles for the Q3 interface .
ITU-T X.200 Reference Model for OSI .
ITU-T X.700 Management Framework for OSI
ITU-T X.702 Application Context for Systems Management with OSI Transaction
Processing
ITU-T X.703 Open Distributed Management Architecture
ITU-T X.710 Common management information service .
ITU-T X.711 Common management information protocol .
ITU-T recommendations on syntax description and definition of information model:

ITU-T X.208 Specification of Abstract Syntax Notation One (ASN.1) .
173
ITU-T X.209 Specification of BER for ASN.1

ITU-T X.720 Information technology - Open System Interconnection - Structure of
management information: Management information model.
ITU-T X.721 Information technology - Open System Interconnection - Structure of
management information: Definition of management information.
ITU-T X.722 Information Technology - Open System Interconnection - Structure of
management information: Guidelines for the definition of managed objects.
ITU-T recommendations on general information model definition and system

management function description:
ITU-T M.3100 Generic network information model.
ITU-T Q.811 Low layer protocol profiles for the Q3 interface
ITU-T Q.812 Upper layer protocol profiles for the Q3 interface
ITU-T Q.821 Stage 2 and Stage 3 Description for the Q3 Interface - Alarm
surveillance .
ITU-T Q.822 Stage 1,Stage 2 and Stage 3 Description for the Q3 Interface Performance Management.
ITU-T X.730 Object management function .
ITU-T X.731 State management function .
ITU-T X.733 Alarm reporting function .
ITU-T X.734 Event report management function .
ITU-T X.735 Log control function .
ITU-T recommendations on SDH information model definition:

ITU-T G.774 SDH management information model for the network element view.
ITU-T G.774.01 SDH performance monitoring for the network element view.
174
ITU-T G.774.02 SDH Configuration of the payload structure for the network element
view.
ITU-T G.774.03 SDH management of multiplex-section protection for the network
element view.
ITU-T G.774.04 SDH management of the subnetwork connection protection for the
network element view.
ITU-T G.774.05 SDH management of connection supervision functionality
(HCS/LCS) for the network element view.
ITU-T G.774.06 SDH unidirectional performance monitoring for the network
element view.
ITU-T G.774.07 SDH management of lower order path trace and interface labeling
for the network element view.
ITU-T G.784 Management of SDH
DN 037-1997 SDH management network management functions, ECC and Q3
interface protocol stack (temporary)
ITU-T recommendations on ASON NM:

ITU-T G.7712 Architecture and specification of data communication network
ITU-T G.7714 Generalized automatic discovery techniques (port adjacent discovery,
layer adjacency: optical interface, MS, RS)
ITU-T G.7714.1 Automatic discovery in SDH and OTN networks
ITU-T G.7718/Y.1709 Framework for ASON management
ITU-T recommendations on PTN information model definition:

ITU-T G.7710/Y.1701 Requirements of public equipment management functions
ITU-T G.7712/Y.1703 Architecture and specification of data communication network
175
RFC 4377 Operations and Management (OAM)ITU-T G.8011 AMD 1 Ethernet over
Transport Ethernet services framework Amendment 1
ITU-T G.8601/Y.1391 Service management structure in multi-bearing, multi-carrier
environment
ITU-T G.8114 T-MPLS network OAM mechanism
ITU-T G.8131 T-MPLS linear protection switching
ITU-T G.8132 T-MPLS shared protection ring ITU-T G.8151 Management Aspects
of the T-MPLS NE
RFC 5654: MPLS-TP Requirements
ITU-T Recommendation M.20, "Maintenance philosophy for
telecommunication networks", October 1992.
draft-ietf-mpls-tp-nm-req: MPLS TP Network Management Requirements
draft-ietf-mpls-tp-nm-framework: MPLS-TP Networks Management Framework
ITU-T recommendations on OTN information model definition:

ITU-T G.709 Interfaces for the Optical Transport Network (OTN)
ITU-T G.798 Characteristics of optical transport network hierarchy equipment
functional blocks
ITU-T X.721, M.3100,G.798
ITU-T M.3100,G.8201,G.798
TMF Service Management Service Agreement

TMF 513 Multi-Technology Network Management Service Agreement (NML-EML
Interface)
TMF 608 Multi-Technology Network Management Information Agreement
176
TMF 814 Multi-Technology Network Management Solution Set Document

TMF 508 Connection and Service Management Service Agreement
TMF 605 Connection and Service Management Information
TMF 807 Connection and Service Management Solution Set Document
Standards of the Ministry of Information Industry of China, and China Telecom

YD/T 852-1996 General Design Principles for Telecom Management Network
(TMN)
YD/T 871-1996 General Information Model for Telecom Management Network
YD/T XXXX-2001 General Technical Requirements for Broadband Metropolitan
Area Network
YD/T XXXX-2001 IP Network Technical Requirements Network Performance
Indexes and Usability
YD/T XXXX-2000 IP Network Technical Requirements Overall Network
YDN 075-1998 Network Management Specifications for China Public Multimedia
Communication Network
CORBA specifications of OMG

OMG, The Common Object Request Broker: Architecture and Specification ,version
2.3.1, October 1999;
OMG, CORBA services: Common Object Services Specification, December 1998.
OMG, Interworking Between CORBA and TMN System Specification V1.0
177
AppB Glossary
Abbreviations
178
Full name
AAA
Authorization, Authentication and Accounting
ACL
Access control list
ARP
Address Resolution Protocol
ASON
Automatically Switched Optical Network
ATM
Asynchronous Transfer Mode
BFD
Bidirectional Forwarding Detection
BGP
Border Gateway Protocol
bps
Bits Per Second
CC
Continuity Check
CDR
Call Detail Record
CFM
Connectivity Fault Management
CIR
Committed Information Rate
CLI
Command Line Interpreter
CORBA
Common Object Request Broker Architecture
CRC
Cyclic Redundancy Check
DCN
Data Communication Network
DDN
Digital Data Network
DHCP
Dynamic Host Configuration Protocol
DNI
Dual Node Interconnection
DPI
Deep Packet Inspection
ECC
Embedded Control Channel
EFM OAM
Ethernet in the First Mile OAM
EML
Element management Layer
EMS
Element Management System
EPL
Ethernet Private Line
Abbreviations
Full name
EPLAN
Ethernet Private LAN
EPON
Ethernet Passive Optical Network
ETH-CC
Ethernet Continuity Check
ETH-LB
Ethernet Loopback
ETH-LT
Ethernet Link Trace
EVPL
Ethernet Virtual Private Line
EVPLAN
Ethernet Virtual Private LAN
FCAPS
Fault Management, Configuration Management, Accounting

Management, Performance Management, Security Management
FCS
Flow Collection System
FMS
Flow Management System
FRR
Fast Re-Route
GCC
General communication channel
GNE
Gate Network Element
GUI
Graphical User Interface
HA
High Availability
HTML
Hyper Text Markup Language
HTTP
Hyper-Text Transmission Protocol
ICMP
Internet Control Message Protocol
IEEE
Institute of Electrical and Electronics Engineers
IGMP
Internet Group Management Protocol
IMA
Inverse Multiplexing for ATM
IPTV
Internet Protocol Television
ITU-T
International Telecommunication Union- Telecommunication

Standardization Sector
J2EE
Java 2 Platform, Enterprise Edition
JDBC
Java Data Base Connectivity
JSP
Java Server Pages
JVM
Java Virtual Machine
LACP
Lightweight Directory Access Protocol
179
Abbreviations
180
Full name
LB
Loopback
LCT
Local Craft Terminal
LLDP
Link Layer Discovery Protocol
LSP
Label Switch Path
LT
Link trace
MA
Maintenance Association
MAC
Media Access Control
MCC
Management communication channel
MD
Maintenance Domain
MEP
Maintenance association End Point
MIB
Management Information Base
MIP
Maintenance association Intermediate Point
MO
Management Object
MPLS
Multi Protocol Label Switching
MSP
Multiplex Section Protection
MSTP
Multi-Service Transmission Platform
MTBF
Mean Time Between Failures
MTTF
mean time to failure
NBI
Northbound Interface
NE
Network Element
NEL
Network Element Level
NML
Network Management Layer
NMS
Network Management System
NTP
Network Time Protocol
OAM
Operation, Administration and Maintenance
OCH
Optical Channel
OID
Object Identifiers
OMS
Optical Multiplexing Section
OSI
Open Systems Interconnection
OSPF
Open Shortest Path First
Abbreviations
Full name
OSS
Operations Support System
PIR
Peak Information Rate
PPS
Packet Per Second
PW
Pseudo Wire
QoS
Quality of Service
RAID
Redundant Array of Independent Disks
RMI
Remote Method Invocation
RODAM
Reconfiguration Optical Add/drop Multiplexer
RPR
Resilient Packet Ring
RSVP
Resource Reservation Protocol
SDH
Synchronous Digital Hierarchy
SLA
Service Level Agreement
SML
Service Management Layer
SNCP
Sub-Network Connection Protection
SNML
Sub-Network Management Layer
SNMP
Simple Network Management Protocol
SSH
Secure Shell Client
STP
Spanning Tree Protocol
TCP
Transmission Control Protocol
TDR
Time Domain Reflectometers
TE
Traffic Engineering
TL1
Transaction Language 1
TMC
T-MPLS Channel
TMF
Tele Management Forum
TMN
Telecommunication Management Network
TMP
T-MPLS Path
TMS
T-NPLS Section
tpmC
Transactions per Minute

(C refers to the TPC benchmark procedures)
UDP
User Datagram Protocol
UML
Unified Modeling Language
181
Abbreviations
182
Full name
VCT
Virtual Cable Test
VLAN
Virtual Local Area Network
VPLS
Virtual Private LAN Service
VPN
Virtual Private Network
VPWS
Virtual Private Wire Service
VRRP
Virtual Router Redundancy Protocol
WDM
Wavelength Division Multiplexing
WTR
Wait-to-Restore

ZTE NetNumen U31 (BN) Product Description

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ZTE NetNumen U31 (BN) Product Description

Загружено:

Авторское право:

Доступные форматы

NetNumen

NetNumen U31 (BN) Product Description

NetNumen U31 (BN) Product Description

Chen Jie, Jiang

Not open to the Third Party

Update based on NetNumen U31

Chen Jie, Jiang

Update based on NetNumen

Chen Jie, Jiang

Update based on NetNumen U31

2012 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

NetNumen U31 (BN) Product Description

System Characteristics ................................................................................... 14

ZTE Confidential Proprietary

NetNumen U31 (BN) Product Description

System Running Platform .................................................................................. 30

System Basic Features ................................................................................... 31

PTN Management ............................................................................................ 49

SDH/MSTP Management ................................................................................. 67

WDM/OTN Management .................................................................................. 74

ZTE Confidential Proprietary

NetNumen U31 (BN) Product Description

WDM/OTN Equipment Spectrum Management .................................................. 83

End to End Service Management ................................................................. 115

System Security ............................................................................................ 138

ZTE Confidential Proprietary

NetNumen U31 (BN) Product Description

System authentication ...................................................................................... 140

System Reliability.......................................................................................... 142

System Networking ....................................................................................... 147

Technical Specifications ............................................................................... 154

LCT management .......................................................................................... 166

ZTE Confidential Proprietary

NetNumen U31 (BN) Product Description

ZTE Confidential Proprietary

NetNumen U31 (BN) Product Description

Table 4-8 Security management function .............................................................................43

ZTE Confidential Proprietary

NetNumen U31 (BN) Product Description

Table 8-5 IP Network TE Management ............................................................................106

ZTE Confidential Proprietary

NetNumen U31 (BN) Product Description

Network Operation & Maintenance Trend

ZTE Confidential Proprietary

NetNumen U31 (BN) Product Description

generation network management system at NE management layer/subnet management

Table 1-1 Manageable NE Type

ZTE Confidential Proprietary

NetNumen U31 (BN) Product Description

ZXR10 M6000-8/ M6000-16

ZXR10 8905/8908/8912 /8905E/8908E/8912E

ZXR10 8902 /8902E

ZTE Confidential Proprietary

NetNumen U31 (BN) Product Description

ZTE Confidential Proprietary

NetNumen U31 (BN) Product Description

ZTE Confidential Proprietary

NetNumen U31 (BN) Product Description

Unified Network Management

Advanced architecture and high scalability

Powerful device management capability

Flexible Plug-in design