NetNumen U31 R22 (V12.16.10) Unified Network Management System Product Description - V1.0

NetNumen™ U31 R22
Unified Network Management System

Product Description
Version: V12.16.10
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: 800@zte.com.cn
LEGAL INFORMATION
Copyright © 2016 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R6.0 2015-12-30 NetNumen™ U31 R22 (V12.16.10) Issued.
Updated the "Manageable NEs", "New Features", "Important

Changes", and "System Interfaces".
R5.1 2015-06-30 NetNumen™ U31 R22 (V12.15.10P02) Issued.
Updated the "Manageable NEs", "New Features", "Important

Changes", and "System Interfaces".
l Updated the "Manageable NEs", "New Features", and

"Computer Ports Occupied by the System".
l Updated some configuration interfaces and menu items.
l Updated the "New Features".

l Updated the "Manageable NEs" and "New Features".

SJ-20151230113133-001|2015-12-30 (R6.0) ZTE Proprietary and Confidential

Revision No. Revision Date Revision Reason
l Updated the "Location of the Product in a Bearer Network",

"New Features", and "System Functions" .
l Updated the "Location of the Product on a Bearer Network",

"New Features", and "Configuration Management" sections,
and the "Product Interfaces" and "Technical Specification"
chapters.
l Updated the "System Overview", "New Features", "Product

Interfaces", Product Functions", "Technical Specifications",
"Compliant Standards" chapter.
l Added the "Environmental Requirement" "chapter.
Updated the "Manageable NEs", "New Features" section.
l Added the "Computer Ports Occupied by the System", "New

Features" chapter.
l Updated the "Network Architecture Requirement", "Cascade
Networking Modes" section.
Serial Number: SJ-20151230113133-001
Publishing Date: 2015-12-30 (R6.0)

Contents
About This Manual ......................................................................................... I
Chapter 1 System Overview ...................................................................... 1-1
1.1 Location of the Product in a Bearer Network ........................................................ 1-1
1.2 Product Features................................................................................................ 1-2
1.3 Manageable NEs................................................................................................ 1-5
Chapter 2 New Features............................................................................. 2-1

2.1 New Functions ................................................................................................... 2-1
2.2 Important Changes............................................................................................. 2-9
Chapter 3 System Architecture ................................................................. 3-1

3.1 Hardware Architecture ........................................................................................ 3-1
3.2 Software Architecture ......................................................................................... 3-2
Chapter 4 System Functions ..................................................................... 4-1

4.1 Topology Management ....................................................................................... 4-1
4.2 Alarm Management ............................................................................................ 4-2
4.3 Performance Management.................................................................................. 4-3
4.4 Security Management......................................................................................... 4-4
4.5 Configuration Management ................................................................................. 4-6
4.6 Software Management........................................................................................ 4-8
4.7 Log Management ............................................................................................... 4-8
4.8 Report Management........................................................................................... 4-9
4.9 Database Management ...................................................................................... 4-9
4.10 License Management ....................................................................................... 4-9
Chapter 5 Network Designs and Applications......................................... 5-1

5.1 Deployment Schema .......................................................................................... 5-1
5.1.1 Stand-Alone System Deployment ............................................................. 5-1
5.1.2 Dual-Computer Cluster System Deployment .............................................. 5-2
5.2 Network Models ................................................................................................. 5-4
5.2.1 Non-Cascade Local Networking ................................................................ 5-4
5.2.2 Non-Cascade Remote Networking............................................................. 5-4
5.2.3 Non-Cascade Integrated Networking ......................................................... 5-6
5.3 Network Architecture Requirements..................................................................... 5-7
Chapter 6 System Interfaces ..................................................................... 6-1

Chapter 7 Technical Specifications .......................................................... 7-1
7.1 Performance Specifications................................................................................. 7-1
7.2 Reliability Specifications ..................................................................................... 7-2
Chapter 8 Environmental Requirements .................................................. 8-1

8.1 Power Specifications .......................................................................................... 8-1
8.2 Environmental Specifications .............................................................................. 8-1
Chapter 9 Compliant Standards................................................................ 9-1

Glossary .......................................................................................................... I
II

About This Manual
Purpose
This manual describes the network position, functional features, network applications,
and system architecture of the U31 R22 system and provides the reliability solutions and
technical specifications to help users understand the features of the U31 R22 system.
Intended Audience
This manual is intended for:
l Planning engineers
l Monitoring personnel
l Maintenance engineers
What Is in This Manual

This manual contains the following chapters.
Chapter 1, System Overview Describes the system overview, position, features, managed
NEs, management functions, interfaces, technical specifications,
and compliant standards of the U31 R22.
Chapter 2, New Features Describes the new functions and important changes of the U31
R22.
Chapter 3, System Architecture Describes the hardware architecture and software architecture
of the U31 R22.
Chapter 4, System Functions Describes the functions of the U31 R22.
Chapter 5, Network Designs and Describes the U31 R22 deployment plans, network designs, and
Applications requirements for network bandwidths.
Chapter 6, System Interfaces Describes the system interfaces of the U31 R22.
Chapter 7, Technical Describes the performance specifications and interface

Specifications specifications of the U31 R22.
Chapter 8, Environmental Describes the power specifications and environmental

Requirements specifications of the U31 R22.
Chapter 9, Compliant Standards Describes the standards that the U31 R22 complies with.
Conventions
This manual uses the following conventions.
Italics Variables in commands. It may also refer to other related manuals and documents.

Menus, menu options, function names, input fields, option button names, check boxes,
Bold
drop-down lists, dialog box names, window names, parameters, and commands.
Constant
Text that you type, program codes, filenames, directory names, and function names.
width
[] Optional parameters.
{} Mandatory parameters.
| Separates individual parameters in a series of parameters.
Danger: indicates an imminently hazardous situation. Failure to comply can result in

death or serious injury, equipment damage, or site breakdown.
Warning: indicates a potentially hazardous situation. Failure to comply can result in

serious injury, equipment damage, or interruption of major services.
Caution: indicates a potentially hazardous situation. Failure to comply can result in

moderate injury, equipment damage, or interruption of minor services.
Note: provides additional information about a topic.
II

Chapter 1
System Overview
Table of Contents
Location of the Product in a Bearer Network...............................................................1-1
Product Features........................................................................................................1-2
Manageable NEs........................................................................................................1-5
1.1 Location of the Product in a Bearer Network

The U31 R22 is a network management system that is located at the network element
management layer/subnetwork management layer and performs EMS/NMS management.
The U31 R22 allows unified management over a series of telecommunications equipment,
including CTN, SDH, WDM/OTN, BRAS, Router, Switch serials equipment, and supports
the LCT function. The U31 R22 can communicate with BSS/OSS through the NBI
interfaces.
For the location of the U31 R22 in a bearer network, see Figure 1-1.
1-1

NetNumen™ U31 R22 Product Description
Figure 1-1 Location of the U31 R22 in the Bearer Network
1.2 Product Features

Unified Network Management
The U31 R22 allows unified management over a series of telecommunications equipment,
including CTN, SDH, WDM/OTN equipment, routers, BRASs, and switches.
Advanced Architecture and Scalability

l Strong equipment management capacity
The U31 R22 uses a distributed architecture. The client, server, and database can
operate on one computer or on multiple computers.
l Flexible plug-in design
The U31 R22 kernel uses a plug-in design. The functional modules can be customized
by adding the plug-ins.
Multiple Network Management Scales Supported

During the U31 R22 installation, there are multiple installation scales available. For details
of scales, refer to the NetNumenTM U31 R22 Unified Network Management System Single
Server Installation Guide.
1-2

Chapter 1 System Overview
Multiple Standard Northbound Interfaces Supported

l SNMP interfaces in compliance with SNMPv1, SNMPv2c, and SNMPv3
l CORBA interfaces in compliance with Recommendation TMF 814
l FTP interfaces
l TL1 interfaces in compliance with Recommendation Bellcore GR-831
l XML interfaces in compliance with MTOSI V2.0
Service Deployment Features

l User-friendly interface.
l Supports single point and end-to-end service provisioning
l Supports cross-domain service management between CTN and IP, CTN and MSTP,
CTN/MSTP and WDM/OTN.
l Supports one-touch CTN service setup
l Supports convenient CTN/SDH service capacity expansion and reduction
l Supports CTN/SDH service cutover
l Supports port CTN port service migration
l Supports FE->GE, GE->10GE, FE->10GE Ethernet link capacity upgrade function.
l Supports offline and online configuration
l Supports multiple service deployment policy
Value-Added Function Features

Advantages of universal value-added functions:
l Supports remote online upgrade
The U31 R22 supports downloading board software remotely via FTP and supports
upgrading board software online.
l Supports intelligent troubleshooting
The U31 R22 has an alarm correlation analysis system, which can analyze and locate
the root alarms and derived alarms based on the network resources and relations.
Various relations and navigation between network alarms and service data can be
performed to fast assess network operation.
l Provides resource views
The resources views can display statistics on the ports, tunnels, and PWs bandwidth
utilization and display the physical link bandwidth utilization in topology.
l Provides statistics, analysis and report management function
The report template function supports designing a report as required.
l Supports multiple time zones and daylight saving time function
This function is used when the clients, servers, and equipment are located at different
time zones or in a region using daylight saving time.
The U31 R22 supports three types of time zones: only daylight time, UTC, and
multiple-time-zone daylight-saving time.
1-3

CTN equipment value-added functions

l Provides unique channel view
The channel views can display the ports in the boards, as well as tunnels, PWs, and
services carried by the ports.
l Provides performance analysis system
This system performs trend analysis and pre-alarms based on historical operation data
to detect network defects. You can perform timed cancellation of some operations to
the equipment.
l Provides inspection tool
The U31 R22 supports remote and centralized equipment patrol and inspection,
generates inspection reports.
WDM/OTN equipment value-added functions
l Provides OTN signal flow
The OTN equipment signal flows can be viewed on the U31 R22. The connections
among the ports and the board alarms can be obtained on the U31 R22.
l Supports OTN APO subsystem
The APO subsystem supports the manual power optimization and automatic power
optimization of OTN equipment.
l Supports OTN APC subsystem
If the optical power in the OTN main optical path is lost, the APC subsystem (auto
protection control) will lower or shuts off the optical output power at the transmit end
to ensure that the optical power in the optical fiber is safe and avoid any personnel
injury.
The U31 R22 system allows the centralized management over APR-APSD protection
groups, which can automatically detect the actuator and monitor port information to
facilitate the configuration.
l Provides channel view
The unique channel view displays the ports in boards, services and alarms on the
ports.
l Provides performance analysis system
This system can perform the trend analysis, generate alarms based on the equipment
operation history data. The U31 R22 supports disabling some maintenance
operations that may affect the equipment normal operation at a scheduled time.
IP equipment value-added functions
l Provides inspection tool
The U31 R22 supports remote and centralized equipment patrol and inspection,
generates inspection reports and simplifies the inspection procedure. The inspection
1-4

reports can provide detailed information and defects about each equipment and
scores them.
l Provides network performance analysis through WEB
Together with external tools, the U31 R22 provides the network analysis and report
function through WEB.
Security
l Supports backup routes
When ECCs are broken, the U31 R22 information can be sent through the backup
DCN, so that the U31 R22 management will not be affected.
l International standards-compliant security mechanism
The U31 R22 supports three-level security mechanisms. They are located at the
clients, servers, and adapters. The client interfaces and server interfaces support
SSL, and TLS. The AAA, Radius authentication, PAP, CHAP, and LDAP are
supported.
l Supports data consistence protection
The U31 R22 uses database backup and database synchronization mechanism.
1.3 Manageable NEs

For the manageable NEs of the U31 R22 V12.16.10 and the hardware versions, refer to
Table 1-1.
Table 1-1 Manageable NEs
NE Type NE and Hardware Version
CTN ZXCTN 6100 (V1.10)

ZXCTN 6110 (V1.10/V2.00)
ZXCTN 6120 (V2.00)
ZXCTN 6120R (V2.00)
ZXCTN 6120S (V3.00.00/V3.00.10)
ZXCTN 6130 (V2.08.33/V2.10)
ZXCTN 6130XG-S (V2.10/V3.00)
ZXCTN 6150 (V2.00/V3.00.00/V3.00.10)
ZXCTN 6150R (V2.00)
ZXCTN 6180 (V3.00.00/V3.00.10)
ZXCTN 6200 (V1.10/V2.00/V2.10)
ZXCTN 6220 (V2.00/V2.10)
ZXCTN 6300 (V1.10/V2.00/V2.10)
ZXCTN 6500-8 (V1.0/V2.00/V1.00.10/V2.00.10)
ZXCTN 6500-16L (V1.0/V2.00/V1.00.10/V2.00.10)
ZXCTN 6500-32 (V1.0/V2.00/V1.00.10/V2.00.10)
ZXCTN 9002 (V2.08.32/V2.08.33/V2.08.33R1)
1-5

ZXCTN 9004 (V2.08.32/V2.08.33/V2.08.33R1)

ZXCTN 9008 (V2.08.32/V2.08.33/V2.08.33R1)
ZXCTN 605 (V1.00/V3.40)
ZXCTN 9000-3E/5E/8E/18E/2E4/2E10 (V3.00.10)
SDH ZXMP S100 (V1.00)

ZXMP S150 (V1.00)
ZXMP S200 (V1.00/V2.00/V2.10/V2.20/V3.00)
ZXMP S320 (V1.00/V1.10/V2.00/V2.30)
ZXMP S325 (V1.00/V1.10/V2.00/V2.10/V2.20)
ZXMP S330 (V1.10/V1.20/V1.30/V1.40/V1.41/V1.43)
ZXMP S335 (V1.00/V2.00)
ZXMP S335E (V1.00)
ZXMP S390/S380 (V2.00/V2.01/V2.02/V2.10/V2.11/V2.12/V2.13/V2
.15/V2.16)
ZXMP S360 (V1.00)
ZXMP S385 (V1.05/V1.10/V2.00/V2.10/V2.20/V2.30/V2.40/V2.50/V-
2.60/V3.00/V3.10/V3.20/V3.30)
ZXONE 5800 (V1.00/V1.10/V1.20)
ZXONE 5800-E (V1.0/V1.x)
WDM/OTN ZXWM-32 (V1.00/V1.10)

ZXMP M600 (V1.00/V2.05/V2.20/V2.20P01)
ZXMP M800 (2M) /M800 (100M) (V1.00/V2.00/V2.10/V2.20/V2.30)
ZXWM M900 (2M) /M900 (100M)
(V1.00/V2.00/V2.10/V2.20/V4.00/V4.10)
ZXMP M720 (V1.00/V1.10/V1.10P01/V1.10P02)
ZXMP M721 (V1.00/V1.10C03/V1.10/V1.11)
ZXMP M820 (V2.4/V2.50/V2.51/V2.52)
ZXWM M920 (V4.10/4.20/V4.20P01/V4.30/V5.00/V5.10)
ZXONE 8300 (V1.00/V1.1/V8.0)
ZXONE 8500 (V1.00/V1.10/V8.0)
ZXONE 8700 (V1.00/V1.10//V1.20/V1.30/V3.00/V4.3/V4.30P01/V6.0/
V6.1/V8.0/ V4.00)
ZXONE 9700 (V3.00/V3.10/V3.20)
ZXUCP A200 ( V1.20/V2.00/V2.10)
UAS product ZXUAS 10800E (V2.8.01/V2.8.22)

ZXUAS 10600 (V2.8.01)
ZXUAS 2500S (V2.1.0)
1-6

Router ZXR10 T1200/T600 (V2.6.02/V2.6.03/V2.08.20/V2.08.21.B/V2.8.22/

V2.08.30/V2.8.32)
ZXR10 T128/T64E (V2.2/V2.6.02–V2.6.03/V2.08.21.B)
ZXR10 GER (V2.2/V2.6.02–V2.8.01)
ZXR10 ZSR (V2.6.03–V2.8.01/V2.8.01B/V2.08.11.B/V3.00.11)
ZXR10 GAR (V2.2/V2.6.02–V2.8.01)
ZXR10 T8000 (V1.00.10/V2.00.20)
ZXR10 M6000-3S (V3.00.10)
ZXR10 M6000-5S (V3.00.10)
ZXR10 M6000-8S (V3.00.10)
ZXR10 M6000-18S (V3.00.10)
ZXR10 M6000-2S10 (V1.00)
ZXR10 6800 (V1.00.10/V1.00.20/V2.00.21/V2.00.20)
ZXR10 1800/2800/3800 (V2.00.10)
Switch ZXR10 G series (V2.6.02D/V2.8.01C/V2.8.02B/V2.8.01.C)

ZXR10 8900 (V2.8.01C/V2.8.02A/V2.8.02B/V2.8.02C/V2.8.02.C.3/V-
2.8.02.C.4/V2.8.03.C.4/V3.00.01/V3.00.02)
ZXR10 8900E (V3.00.01/V3.00.02/V3.03.10/V3.01.01/V3.02.01)
ZXR10 6900 (V2.8.01C/V2.8.02A/V2.8.02B/V2.8.02C/V2.8.02.C.3/V-
2.8.02.C.4/V2.8.03.C.4)
ZXR10 5960 (V3.00.20/V3.02.20)
ZXR10 5950 (V2.8.23.A.19)
ZXR10 5900E (V3.00.10/V3.00.11)
ZXR10 5900A/5200A (V2.8.23.A.11)
ZXR10 5900 (V2.8.02)
ZXR10 5900 STACK (V3.00.11)
ZXR10 5960 STACK (V3.00.20)
ZXR10 5900 /5200 (V2.6.02–V2.6.03/V2.8.02A/V2.8.23.A/V2.8.23.A-
.11)
ZXR10 5250-24T (V1.2.12.R)
ZXR10 5250-52TM (V2.8.23.A.19)
ZXR10 5250 (V2.05.10/V2.05.11/V2.05.12)
ZXR10 5100 (V1.2.11.b–V1.2.11.k)
ZXR10 5009 (V1.0–V1.1.11.j)
ZXR10 3950 (V2.8.23.B2.06)
ZXR10 3900E (V2.8.23.B/V2.8.23.B2/V2.8.23C/V2.09.10)
ZXR10 3900A/3200A (V2.8.02.B/V2.8.23.A/V2.8.23.A.11)
ZXR10 3900/3200 (V2.6.02/V2.8.02.B/V2.8.23.A/V2.8.23.A.11)
ZXR10 2950 (V2.03.11.02/V2.05.10)
ZXR10 2900S (V2.1.12.k)
ZXR10 2900E (V2.03.10/V2.03.11/V2.05.10/V2.05.11)
ZXR10 2900A (V2.2.10.A/V2.2.10.D)
ZXR10 2900 (V2.0.10.h or above/V2.0.12.J/V2.0.11.q)
1-7

ZXR10 2850 (V1.1.12.U)

ZXR10 2800S-LE (V1.0–V1.1.11.o/V1.1.12.L)
ZXR10 2800S (V1.0–V1.1.11.y/V1.1.12.L/V1.1.12.U)
ZXR10 2800SEI (V1.1.20.a–1.1.20.f)
ZXR10 2800E (V1.0–V1.1.11.j)
ZXR10 2800A/2600A (V1.1–V1.1.11.s)
ZXR10 9904//9908/9912/9916 (V1.00.01/V1.00.02/V1.01.10)
PCM equipment ZXMP P210

ZXMP P230
1-8

Chapter 2
New Features
Table of Contents
New Functions ...........................................................................................................2-1
Important Changes.....................................................................................................2-9
2.1 New Functions

New Functions Provided by the U31 R22 V12.16.10 (Compared With V12.15.10P02)
For the new functions provided by the U31 R22 V12.16.10 (compared with V12.15.10P02),
refer to Table 2-1.
Table 2-1 New Functions Provided by the U31 R22 V12.16.10 (Compared With
V12.15.10P02)
Function Description
Common Management scale Displays the NMS management scale, including NE names,
number of licenses, number of the current NEs, and the total
number of the current equivalent NEs.
PTN Unloaded tunnel The system detects and manages (queries or deletes)
unloaded non-terminating tunnels.
Migration into or out l You can check whether the service tunnel of the
of the shared ring protection sub-net at the section layer is bound to the
shared ring.
l You can check whether the service tunnel is bound to the
tunnel of the shared ring.
Resource Usage Displays the resource usages of the TMS and static tunnels,
including the CAC function, convergence ratio mode,
automatic adjustment or not, and bandwidth usage.
Batch adjustment of By adjusting the service bandwidth, the service CAC function
the service bandwidth can be enabled and the service bandwidth can also be
adjusted.
Recovery of The system automatically recovers non-terminating tunnels.

non-terminating
tunnels
Service transition In some networks with special architectures, a lot of services

require scheme transition and network model adjustment.
The scenarios include:
2-1

l Changing dual-homing Ethernet bridging point to

dual-homing DNI (PTN): This scenario is applicable to
changing general dual homing of Ethernet services to
dual-homing DNI in mobile LTE network. In this scenario,
only general dual-homing services on the Ethernet
bridging point can be changed to the dual-homing DNI
service. Other services (for example, unprotected
Ethernet services and openly protected Ethernet services
unassociated with L3VPN services) are not supported.
l Changing unprotected TDM to dual-homing DNI (PTN):
This scenario is applicable to 2G/3G networks to change
single-homing Ethernet services to dual-homing Ethernet
services, or the IPRAN scenario to change single-homing
TDM services to dual-homing services.
l Changing closed TDM protection to dual-homing DNI
(IPRAN): This scenario is applicable to the IPRAN
scenario.
PTN service recovery With this function, damaged tunnels and pseudo wire
services can be automatically recovered.
Automatic link This function is implemented manually or periodically.

detection
WDM/OTN ONT status The system can check the OTN protection status in the
maintenance and network and perform switchover.
management
Independent resources: various configuration data for

uncreated end-to-end paths, including access service
configuration, service mapping configuration, optical cross
configuration, and wavelength tuning.
The system supports independent resource detection and
manages (queries or deletes) these resources.
Intelligent wave Supports adjusting the optical power threshold and gain after
spread tool wave spread, including the following:
l Automatically calculating the recommended optical
power threshold and delivering the threshold to
equipment after manual confirmation.
l Automatically calculating the recommended value for
automatically adjusting the VMUX attenuation or OA
gain and delivering the value to equipment after manual
confirmation.
2-2

Chapter 2 New Features
Tool for planning the The system can replan the protection relationship group ID
protection relationship and deliver this ID to equipment after manual confirmation.
group ID.
Service maintenance You can check optical spectrum analysis information.
Service configuration Supports modifying service configurations by one key based

modification on paths, or modifying the 10 GE LAN to 10 GE WAN or vise
versa.
New Functions Provided by the U31 R22 V12.15.10P02 (Compared With V12.15.10)
For the new functions provided by the U31 R22 V12.15.10P02 (compared with V12.15.10),
refer to Table 2-2.
Table 2-2 New Functions Provided by the U31 R22 V12.15.10P02 (Compared With
V12.15.10)
PTN Traffic statistics Adjusts traffic for PWs and tunnels in batches.
Concentration ratio Adjusts the convergence ratios of tunnel bearer interfaces

in batches.
Damaged service Supports the automatic recovery of damaged services.
Protection type Supports the rectangle dual-node protection service

model.
SRLG Supports the creation, modification, deletion, and query

functions of Shared Risk Link Groups (SRLG).
Service template Supports service node parameter templates.
Fault diagnosis Supports L2L3 fault diagnosis.
Traffic analysis The U31 R22 provides a performance collection interface

to the ZXDNA system.
Supports the traffic analysis function in IPRAN scenarios.
SQA Supports the SQA-based end-to-end service quality

detection.
OSPF view Supports the OSPF configuration view.
2-3

WDM and OTN Resource Discovers and manages isolated resources.

management Isolated resources refer to various configuration data that
has not formed end-to-end paths, including the access
service configuration, service mapping configuration,
electrical cross-connection configuration, optical
cross-connection configuration, and wavelength tuning.
NE neighbor Queries the neighbor information of OTN NEs.

information
Protection Supports electrical-layer 1+1+1 protection and WASON

management gold electrical-layer services.
Power equalization After power equalization is configured, you can select

the manual or automatic adjustment operation based on
the alarm information of the monitoring unit to realize the
power equalization of each channel.
APO link Supports the real-time APO function.

This function only needs to be configured on the EMS.
APO power is adjusted by the device.
IP Resource view Supports the resource view function.
OSPF view Supports the OSPF protocol configuration view.
SQA Supports the SQA-based end-to-end service detection

management for IP devices.
Intelligent l Supports the configuration template for IPRAN

configuration tool services.
l Supports advanced configuration templates.
l Supports the configuration rollback function.
l Supports the import and export of configuration
templates.
Backup and l Supports the cross-scale backup and recovery of

recovery the dbtool.
l Supports the cross-version backup and recovery of
the dbtool.
refer to Table 2-3.
V12.14.10P02)
Installation mode The U31 R22 client supports installation through Web.
2-4

IT EMS The U31 R22 has the ITMP module and the U31 R22 can monitor and
manage server hardware, the operating system, and third-party software.
Resource search and The U31 R22 supports searching resources by an NE, board, port, or
location CTP. After your double-click the resource, the corresponding interface
is displayed.
Resource permission The U31 R22 supports management authority partition based on boards
management and ports.
POTN capacity expansion The ZXCTN 6500 (V2.0) supports capacity expansion and reduction of
and reduction the POTN.
Port convergence ratio The ZXCTN 6000 series and ZXCTN 9000 series support the
convergence ratio. The port convergence ratio can be set on the EMS.
Optical fiber cutover After optical fiber cutover, you can query optical power of the optical
management fibers, and compare the optical power after cutover with that before
the cutover.
Service correction A damaged WDM service can be corrected.
Automatic generation of After optical fibers among WDM NEs are connected, the EMS
OTS and OMS paths automatically generates OTS and OMS paths.
Service interruption alarm The U31 R22 supports statistical analysis on service interruption alarms.
statistical analysis
PTN service cutover l Pre-configured services and normal services are involved in
function supporting CAC bandwidth sharing, release, and reuse.
l The TMS and tunnel resource usage interface shows the bandwidth
usages with pre-configured services and without pre-configured
services.
l The U31 R22 supports creating a redundancy protection scenario.
Tunnel migration function The tunnel NNI side can be migrated across NEs to meet the
requirements in the scenarios where nodes of a tunnel are added or
reduced, boards and nodes are migrated in an NE, and link capacity
is upgraded.
Same-route tunnel To release bandwidth and save the physical link bandwidth resources,
bandwidth compression the U31 R22 can set a tunnel sharing relationship for the tunnels that
tool share the same TMS.
refer to Table 2-4.
2-5

V12.14.10)
Connection Admission The resource reservation switch is used to designate whether bandwidth
Control (CAC) parameters participate in the CAC calculation at the control layer.
Protocol template During protocol instance configuration, the preset protocol template
must be used.
Parameter template You can preset a parameter template based on the actual requirements,
and then directly import this parameter template during service
configuration. There is no need to set the parameters one by one.
Ethernet service Modification scenarios can be divided into incremental modification and
modification decremental modification, which are used to add or delete sites and
add or delete protection.
In these two scenarios, data is only sent to the affected sites.
QoS template During service parameter configuration, you can select the preset QoS
template.
Section layer OAM and You can query, set, and modify the section-layer OAM parameters of
SD CTN links.
Maintenance operations include Ping, LCK, LB, LM, and DM.
Fault information The CTN fault information collection tool can be used for remote fault
collection location and information collection (including computer configuration
information, EMS configuration files, and EMS log files).
Event compression The system discards the events that are repeatedly reported.
If the time interval between the next event and the previous event that
have the same source and the same alarm code is within a specified
range, this event is considered to be a repeatedly reported event.
refer to Table 2-5.
V12.13.10P02)
NE-level resource The U31 R22 can implement region-based authentication and
authentication management in the network. The user with the resource management
authority in a region can only manage the NEs in this region rather than
query or operate the NEs in other regions.
CTN service automatic Cooperates with third-party companies to realize the CTN service
activation system automatic activation system.
2-6

TMS fault response If a TMS fault occurs in the network and this fault affects its carried
services (such as TMS LOC), the tunnels, PWs, client-layer services
carried over the TMS report the service fault.
Service group navigation Supports creating, deleting, and modifies service groups and filtering
services by using service groups as filtering conditions.
OTN path management l Supports discovering OSC paths automatically and managing them.
l Supports the graphical routing display of OSC paths.
l Supports filtering OSC paths in the entire network and forming an
OSC path view.
Path management based Supports PID-based path management, including path discovery, path
on PID creation, path display, and path maintenance.
L3 VPN aggregation Supports the L3 VPN aggregation function of CTN equipment.
Batch migration Supports batch non-protection tunnel migration of CTN shared ring.
Service template Adds a damaged service template and an alarm service template to the
template list in the service view.
WDM and OTN service Supports creating ODU Flex services.
Ping and Trace l Supports the Ping and Trace functions of dynamic tunnels in the
IP private network.
l Supports the Ping and Trace functions of PWs.
TDM service Adds dual-DNI scenarios for TDM services.
Tunnel Tunnels support the cross-ring scenarios of shared rings.
Automatic discovery Supports the automatic TMS discovery of CTN pass-through WDM
and OTN and the automatic TMS discovery of aggregation microwave
interfaces.
Static tunnel CTN equipment support free-configuration of static tunnels.
Common routing analysis Supports the common routing analysis of CTN services.
New Functions Provided by the U31 R22 V12.13.10P02 (Compared With V12.13.10P01)
For the new functions provided by the U31 R22 V12.13.10P02 (compared with
V12.13.10P01), refer to Table 2-6.
V12.13.10P01)
IP conflict detection If the IP of a created NE conflicts with that of an existing NE, or the IP
of a port of a created NE conflicts with that of a port of an existing NE,
an alarm is reported.
Connectivity detection Supports tests for dynamic tunnel connectivity.
2-7

Capacity extension Supports extension and reduction of the shared ring, and service
and reduction, service migration.
migration
Optical power Supports power comparison.

management
Fault diagnosis Supports static and dynamic fault diagnosis.
OAM management Supports Ethernet OAM management (WDM and CTN).
Batch migration Supports batch tunnel migration of CTN shared ring.
Ping and trace l Supports the Ping function of MS-PW, L2 services and L3 VPN.
l Supports the Trace function of MS-PW.
Static tunnel management Supports IP static tunnel management.
refer to Table 2-7.
V12.13.10)
Detection function Supports MSTP backup channel detection.
Services query Queries Ethernet services by VLAN.
Software installation. Adds the self-check function during installation.
Backup and restoration Supports cross-scale data backup and restoration.
Log query Queries Telnet operation logs of NEs.
Copy and paste Copies and pastes IP addresses and subnet mask controls.
Ping Supports the VRF ping function of L3 VPN.
Associated services Supports the associated services of IP equipment.
New Functions Provided by V12.13.10 (Compared With the U31 R22 V12.12.20P01)
refer to Table 2-8.
Table 2-8 New Functions Provided by V12.13.10 (Compared With the U31 R22
V12.12.20P01)
Real-time traffic Supports monitoring real-time MSTP traffic.

monitoring
View management Supports DCN view.
2-8

NE management Supports virtual NEs, virtual links.
Report management Supports resource analysis function.
Protocol management Supports IPV6 protocol management channel; supports browsing the
IPV6 protocol.
DOT1X management Supports configuring the 802.1X on middle-end switches.
Channel template Supports configuring the QoS on middle-end switches.

management
Resource view Resource views support abnormal traffic monitoring and packet
performance reports
Link management Supports creating links in batches.
Northbound interface Supports northbound interface in XML.
PW Supports transparent PW.
SNCP Supports multiple-section SNCP.
New Functions Provided by V12.12.20P01 (Compared With the U31 R22 V12.12.20)
refer to Table 2-9.
Table 2-9 New Functions of the U31 R22 V12.12.20P01
Service configuration The SDH equipment supports VC3 concatenation.
Backup and restoration Supports cross-version and cross-scale data restoration.
IP RAN management Supports the IP RAN function.
Resource view The resource view supports topology monitoring over CPU and memory.
2.2 Important Changes

Changed Items in the U31 R22 V12.16.10 (Compared With V12.15.10P02)
For changed items in the U31 R22 V12.16.10 (compared with V12.15.10P02), refer to
Table 2-10.
2-9

Table 2-10 Changed Items in the U31 R22 V12.16.10 (Compared With V12.15.10P02)
Common Installation disk l The icons in the installation window are updated.
l Installation steps are simplified.
Customized view Supports customizing the OTN rate. The topology is

elements presented depending on the rate level of the NE at the
originating end of the link.
Alarm Management Current/historical alarms (including both visible and invisible

alarms) reported by the northbound interface are the same
as those on the NMS.
Performance l Supports performance items for which thresholds can be

management configured, and these thresholds can be displayed.
l Supports arranging the sequence by service, time, and
physical routes of services. Service performances of
the same service at the same time are arranged in the
sequence of the physical routes of services (including
the service layer). For services in two directions, arrange
the performances as two unidirectional services.
l "Granularity" is not displayed in the service performance
column by default.
PTN Layer-3 port l The configuration window is modified.

configuration l The filter function is added.
End-to-end service The end-to-end service configuration table is optimized.

configuration table
WDM/OTN Service view l Working routes and protective routes are displayed in
texts w and p on the link and are not hidden by default.
However, you can customize the routes as hidden or not.
l The texts are displayed on the link and are distinguished
in different colors (for example, p is displayed yellow and
w is displayed blue).
Service route When service creation fails due to a route computing failure,
computing failure the system provides the function of analyzing the route
analyzing tool computing failure causes.
Service route Supports navigation to error codes by right-clicking the NEs

navigation chart and boards in the service route chart.
Changed Items in the U31 R22 V12.15.10P02 (Compared With V12.15.10)

For changed items in the U31 R22 V12.15.10P02 (compared with V12.15.10), refer to
Table 2-11.
2-10

Table 2-11 Changed Items in the U31 R22 V12.15.10P02 (Compared With V12.15.10)
Common Network Supports up to 60000 equivalent NEs (25000 physical

management NEs).
capability
Protection view In the protection view, protection subnet information is

displayed in tabular form.
EMS framework l Integrates the NE creation function with the

framework.
l Integrates the operation permission tree.
Alarm management Optimizes the functions in the alarm right-click shortcut

menu.
Performance Optimizes the service performance list and performance

management statistics function.
PTN Analysis for the NEs Based on the selected service, analyzes the actual
with the same routes operating status of the service and NEs with the same
routes.
WDM/OTN Protection view Supports electrical-layer protection.
Straight-through l Supports performance query templates.

performance query l Queries performance by selecting the corresponding
item from the right-click shortcut menu in the board
view.
IP TOPN function Improves the TOPN function of performance statistics.

of performance
statistics

For changed items in the U31 R22 V12.15.10 (compared with V12.14.10P02), refer to
Table 2-12.
EMS frame The function accesses and names on the EMS interfaces are integrated
and optimized.
Alarm right-button function The suppression filtering rules can be configured with the time of taking
effect.
Clock/time view The node or link that does not lock the clock or time properly is strikingly
displayed.
Optical power With the optical power management function, you can export the
management network-wide main optical power status table by clicking one button.
2-11

Optical power attenuation The optical fiber attenuation trend of an optical fiber over a period of
trend time is displayed graphically.
Ping The scenarios that are applicable to GNEs and the ZXMP M721 are
added.
Attenuation spectrum The default page for showing the attenuation spectrum is changed.
management
Optical per performance If optical power performance exceeds the performance threshold but it
belongs to the performance detection range, the detailed performance
value is displayed.
Service cutover The service cutover function supports automatically binding shared rings.

For changed items in the U31 R22 V12.14.10P02 (compared with V12.14.10), refer to
Table 2-13.
Alarm management l If an alarms is reported, the associated service information is also

reported.
l Adds how to handle visible and invisible alarms.
Alarm log Optimizes the contents of alarm logs.
Configuration tool l Adds BN northbound TMF CORBA interface configuration in the

U31 EMS configuration center.
l Adds the TMF CORBA process-related configuration items in the
NBI configuration center.
l By default, the CAC switch is disabled.
Service query Modifies the fields of service query and optimizes query efficiency.
Software installation l Not support the installation of Scale 4 any longer.

l After software installation, configuration files of the unified FTP
historical performance interface are automatically deployed to the
designated directory rather than copied manually.
NE management Supports the ZXR10 9904//9908/9912/9916 (V1.00.01)/ZXONE 9700

(V3.00).
2-12

Easy-of-use management This version improves the following functions.

l Service configuration
l Service template
l Associated service
l Automatic discovery
l Service cutover
l Capacity expansion and reduction
l Shared ring
l Resource view

For changed items in the U31 R22 V12.13.10P02 (compared with V12.13.10P02), refer to
Table 2-14.
Network management Supports managing up to 4000 equivalent NEs in the ultra-large-scale

capability network.
Ethernet service Supports the mix of NNI and UNI.

configuration
DBtool database tool Supports the database upgrade of data communication devices.
Software/hardware l Supports CGSL V4.02.20.P2.

configuration l Supports using the CGSL/Windows 8 system as the NMS client.
l Supports the local dual-computer scheme of the Windows operating
system and the remote dual-computer scheme of the CGSL system.
Time view/optical power Supports the unified management for CTN devices.
view This function can be configured even though the IPTN is not deployed.
Product operating -
efficiency optimization
NE management Supports the ZXCTN 6120 (R)/6150 (R) (V2.00), the

ZXCTN 6130XG-S/6200/6220/6300 (V2.10), the ZXCTN
6500-8/6500-16L/6500-32 (V1.00.10R2), and the ZXMP M721/ZXONE
8700 (V1.10).
2-13


l Service view
l Protection subnet
l Optical power management
l Data check tool
l Board software upgrade
l WASON function
l Needed board update
Changed Items in the U31 R22 V12.13.10P02 (Compared With V12.13.10P01)

For changed items in the U31 R22 V12.13.10P02 (compared with V12.13.10P01), refer to
Table 2-15.
Table 2-15 Changed Items in the U31 R22 V12.13.10P02 (Compared With V12.13.10P01)
Software installation l Modifies the installation interface.

l Deploys end-to-end auto discovery process independently.
Product operating -
Service configuration Supports WDM/OTN service auto optical power adjustment.
Software/hardware Supports Windows 8 and CGSL (V4.02.20) OS.

configuration
NE management Supports the ZXCTN 6120 (V2.00P01), the ZXCTN 6500

(V1.0R1P01/V1.0R1P02), and the ZXCTN 9002/9004/9008 (V2.08.33
R1)

l SNCP protection for SDH services.
l L3 VPN service management.
l Ethernet service configuration
l Service deletion
l Service rollback
l Service report
l Alarm function
l Resource view
l Time view
l Optical power view

For the changed items of the U31 R22 V12.13.10P01 (compared with V12.13.10), refer to
Table 2-16.
2-14

Network management A single server can manage 32000 equivalent NEs.

capability
Software installation Improves installation configuration of northbound interfaces.
Port migration Adds license control for port migration.
NE management l Supports the ZXMP S385 (V3.30).

l Supports the ZXMP S320 (V2.30).

l Shared ring configuration
l dynamic tunnel management
l Channel view
l optical power view
l Performance management
l Explicit route management
l TNP configuration window
l deletion function
l ASON call management window
Changed Items in the V12.13.10 (Compared With the U31 R22 V12.12.20P01)
For the changed items of the U31 R22 V12.13.10 (compared with V12.12.20P01), refer to
Table 2-17.
Table 2-17 Changes of U31 R22 V12.13.10 (Compared With V12.12.20P01)
Protection function The MSTP EPS protection can be configured in the end-to-end mode.
Real-time traffic monitoring Supports real-time MSTP monitoring.
IP RAN function Updates the IP RAN function.
Software installation Updates the installation scale.
Product operating efficiency -

optimization
Network management Supports up to 30000 equivalent NEs.
File management l Improves file management backup strategy.

l Decreases backup time and disk occupation.
ACL management Supports the ACL management for 8900 serials equipment.
Route monitoring Private network route monitoring.
2-15

NE management l Supports the ZXR10 5900E (V2.09.10).

l Supports the ZXR10 5960 (V2.09.10).
l Supports ZXR10 M6000 (V2.00.20) (topology management,
alarm, performance, rack diagram).
l Supports ZXR10 T8000 (V 2.00.20) (topology management,
l Supports ZXR10 M6000-nS (V2.00.20) (topology management,
l Supports PCM equipment.
Easy-of-use management This version improves the following function.

l WDM protection subnet management
l Service cutover
l Resource view
l Channel view
Changed Items in the V12.12.20P01 (Compared With the U31 R22 V12.12.20)
For the changed items of the U31 R22 V12.12.20P01 (compared with V12.12.20), refer to
Table 2-18.
Table 2-18 New Functions of the U31 R22 V12.12.20P01
Software/hardware Changes the SUN server model.

configuration
Software installation Simplifies the software installation disk and changes the installation
procedure.
Product operating -
Link management Changes the fiber connection function.
Service cutover Optimizes the service cutover function.
Northbound interface TL1 and FTP northbound supports the 5900E series equipment.
Statistics management Supports the BRAS user statistics management.
NE management l Supports the ZXCTN 6130 and ZXR10 6800 series equipment.
l Supports daughter cards on the 2900E series equipment.
2-16

Chapter 3
System Architecture
Table of Contents
Hardware Architecture................................................................................................3-1
Software Architecture .................................................................................................3-2
3.1 Hardware Architecture

The U31 R22 system uses the client-server model. One U31 R22 system contains a set
of servers and multiple clients, see Figure 3-1.
Figure 3-1 U31 R22 Hardware Architecture Diagram
The U31 R22 hardware contains servers, clients, alarm boxes, network devices, and
optional devices, such as printers, sound boxes, and backup devices.
l Servers
The servers are the core devices of the U31 R22 system. The servers communicate
with NEs via southbound interfaces. After the data is processed on the servers, they
are sent to the corresponding clients. The servers communicate with the upper-level
network management systems via northbound interfaces.
The servers can be divided into application servers and database servers based
on their functions. In general, the application server and the database server are
configured in one computer. While, they can also be configured in different computers
for sharing the load.
You can configure one U31 R22 server or two servers (master/slave), which can create
an HA system, as required.
3-1

The U31 R22 uses Windows/Solaris/Linux operation system.

l Clients
The clients operate on Windows and they provide GUIs for the users.
The U31 R22 supports multiple clients. Users can manage NEs through the clients,
monitor and manage the U31 R22 system itself.
The clients are divided into three types based on physical positions of the clients, the
connected servers and the managed NEs.
à Local client: The client and server belong to one LAN.
à Remote client: The managed NEs and the server belong to one LAN. The client
and the server do not belong to one LAN.
à Return client: The managed NEs and the clients belong to one LAN, but the
server does not belong to the LAN.
l Alarm boxes
Alarm boxes are used to transfer information. They can collect alarms, alarm recovery,
pre-alarm information and logs, and send these information to the alarm center, where
these information is processed and then sent to the corresponding personnel.
l Network devices
Network devices are used to connect U31 R22 and NEs or connect U31 R22 and the
upper-level network systems. The network devices contain switches and routers.
l Optional devices
Optional devices contain printers and sound boxes.
3.2 Software Architecture

The U31 R22 software contains four parts: clients, servers, adapters and the databases,
see Figure 3-2.
3-2

Chapter 3 System Architecture
Figure 3-2 U31 R22 Software Architecture
3-3

This page intentionally left blank.
3-4

Chapter 4
System Functions
Table of Contents
Topology Management ...............................................................................................4-1
Alarm Management ....................................................................................................4-2
Performance Management .........................................................................................4-3
Security Management ................................................................................................4-4
Configuration Management ........................................................................................4-6
Software Management ...............................................................................................4-8
Log Management .......................................................................................................4-8
Report Management...................................................................................................4-9
Database Management ..............................................................................................4-9
License Management .................................................................................................4-9
4.1 Topology Management

The topology management module of the U31 R22 system provides NE topology views.
The following lists the topology management functions that you can use in the U31 R22
system.
l Navigation
The navigation tree and topology view are consistent. The navigation tree provides
corresponding NE operations, including NE modification or alarm querying.
l Graphic Display
The topology map shows all NEs managed by the system as well as their relations in
the network. You can view NE statistics, such as NE quantity, link quantity or alarms.
l NEs and Links

You can create NEs of various attributes and view relations among NEs through link
identifiers.
l Topology Map Control

On the topology map, you can do the following operations.
à Drag, zoom in, and zoom out the topology map.
à Go to, back to, and forward to a specific NE or topology layer.

à Search for specific NEs.
à Change the background of the topology map.
4-1

à Synchronize the configuration information of NEs on the topology map from the
server and refresh the display on the client without changing the positions and
connection relations of those NEs.
à Select the layout mode of NE icons on the topology map, including hierarchical
layout, tree layout, radial tree layout, spring embedded layout, and uniform length
edges layout.
l Filtered Display
On the topology map, you can set filtering conditions to filter the NEs or links that
you do not concern from the topology map. The filter conditions can be NE name, IP
address, link name, NE type, link type, and/or group type.
l Authorization-Based Data Display
The system only provides topology management functions to authorized users.
l Alarm Display
On the topology map, an NE or link is highlighted in different colors when some
fault(s) occur in it according to the fault severity and the acknowledgement status of
corresponding alarm(s).
l Group-Based View
To manage NEs more effectively, you can group NEs based on NE types or NE
locations.
4.2 Alarm Management

The fault management module monitors the operating status of the equipment in real time.
The fault management includes the following functions:
l Alarm Data Collection and Storage
The system collects alarm information sent by the managed NEs in real time,
converts the format of the alarm information as required, and then stores all the alarm
information in the database.
l Graphic Display and Localization of Alarms
The system monitors the managed NEs in real time and displays the received alarm
information on the client screen.
l Alarm Acknowledging and Unacknowledging
By observing the acknowledgement status of alarms, you can know the running
status of the network, find the latest alarm information quickly, and process the
alarms respectively according to their acknowledgement status.
l Real-Time Alarm Monitoring
The system shows real-time alarms in the form of list on the client screen.
l Alarm Clearing
4-2

Chapter 4 System Functions
The system automatically clears an alarm from the active alarm list after the fault
causing this alarm is removed.
l Alarm Synchronization
Alarm synchronization includes the synchronization of alarm information between
the U31 R22 server and the managed NEs (that is, the alarm sources), and the
synchronization of alarm information between the U31 R22 client and the server.
The system initiates an alarm synchronization process in the following situations:
à The broken connection between the client and the server recovers.
à The broken connection between the server and a managed NE in the network
recovers.
à The server is restarted.
l Output of Alarm Data
All alarm information can be output to *.txt, *.xls, *.pdf, *.html, or *.csv files.
l Alarm Rule Management
A fault in an NE may cause several correlated alarms. By setting a correlation rule,
you can collapse a series of correlated alarms caused by the same fault and reduce
the count of alarms displayed on the client screen.
l Alarm Query and Statistic
The alarm query and statistic include history alarms, active alarms, notifications, and
alarm number.
In addition, the system can indicate the distribution of different alarms by displaying
the statistic information in various chart forms, such as PDF, HTML, or CSV.
4.3 Performance Management

The purpose of performance management is to collect the performance data of NEs in the
network, evaluate the efficiency of equipment and the network, and monitor the quality of
service and network.
The following lists the performance management functions that you can use in the U31
R22 system.
l Data Query
You can query raw performance data stored in the database.
l Data Synchronization
The system can automatically synchronize performance data from the managed NEs
to the server, and synchronize performance data from the server to the client. You
can also initiate the synchronization of performance data through a client.
l Data Report
4-3

The system can generate a performance data statistic report to show current KPIs,
which can also be output as *.xls, *.pdf, *.html, and *.txt files.
A predefined template or user-defined template can be used to generate the report
you want.
The system can send the periodically-generated report to a user in the specified format
through E-mail as required.
4.4 Security Management

For better understanding of security management, the following explains some basic
concepts related to security management, including role, role set, department, and user.
Only authorized users can access and manage network resources.
l Role
A role specifies the management permission for a user group, including the operation
permission and manageable resources.
à The operation permission allows the user group to use specific functional modules
of the network management system. For example, if a role has the operation
permission of the log management module, the users acting as the role can
perform log management operations, such as querying logs and maintaining logs.
à The manageable resources refer to subnetworks and/or network elements that
can be managed by the role.
l Role Set
A role set is a set of roles. The management permission of a role set involves the
management permissions of all roles in the role set.
l Department
Departments are specified in the network management system to simulate the actual
administrative departments. In this way, the system administrator can conveniently
organize and manage users in the system.
l User
A user is an operator who is authorized to log in to the system and perform

operations in the system. While creating a user, the system administrator assigns
the management permission to the user by specifying a role or role set and allocates
the user to a department according to the actual situation.
For the model of relations among user, role, role set, department, operation permission,
and manageable resources involved in the security management, see Figure 4-1.
4-4

Figure 4-1 Relation Model of Security Management
The U31 R22 system provides the following security management functions.
l Security Event Recording
The system can record security events, for example, authentication failure, locking a
user, and disabling a user. The system administrator can know the situation of user
accounts in the system by observing the security event log.
l Reporting of Security-Related Alarms
The system can report alarms to the administrator when some important security
events occur, for example, a user account is locked.
l Setting of Login Time Period
By using the security management module, you can set a limit of the time period for
a user. The user is allowed to log in to the system only in this period.
l User Account Management
A user can query and change its password, policy, locking rule, and validity period.
For example, you can specify a rule like this: if a user enters the wrong password three
times, the user account will be locked for the purpose of preventing unauthorized login.
The super administrator of the system can remove a user from the system forcibly to
avoid unauthorized operations performed by this user and ensure the system security.
4-5

l IP Address Setting of Super Administrator

After you set the IP address, the super administrator can only log in to the system on
the client with the same IP address as the preset one.
l User Password Modification
The super administrator of the system can change the passwords of all the other
users.
l User Status Check
If you log in to the system as a super administrator, you can check the locking status
of other users, enable the automatic unlocking function of other users, and set the
unlocking time.
l Locking of Clients
If no operation is performed for on a client a long time, the system will lock the client
and force the login user on the client to log out of the system. The user is required to
log in to the system again before performing any operation in the system.
4.5 Configuration Management

The configuration management module of the U31 R22 system allows you to configure the
managed NEs in the system. Different NEs support different configuration management
functions.
CTN NEs support the following configurations:
l NE basic configuration
l Clock time configuration
l Interface configuration
l Protocol configuration
l Configuration for single NE service and end-to-end service
l OAM configuration
l Qos configuration
l Configuration for equipment-layer protection
l Configuration for network-layer protection
l Configuration for network expansion and shrink
l Alarm configuration
l Performance configuration
l Overhead configuration
l Port migration
l Channel view
l Resource view
l Real-time traffic monitoring
SDH NEs support the following configurations:
l Gateway NE configuration
l Clock configuration
4-6

NE time configuration
Service telephone configuration
NE and board configuration
Configuration for equipment-layer protection
l Configuration for network-layer protection
Configuration for single NE service and end-to-end service
l Ethernet service configuration
l Configuration for CTN and SDH mixed networking service
l Clock view
l Network maintenance
l Data synchronization
OTN NEs support the following configurations:
NE clock synchronization configuration
NE basic configuration
Protection configuration
Configuration for single NE service and end-to-end service
l APR-AOSD configuration
l Optical power configuration.
l Spectrum configuration
l Overhead configuration
l Service telephone configuration
The following hybrid networks are supported:
l Configuration for CTN and SDH mixed networking service
l Hybrid network composed of SDH and WDM/OTN NEs
l Hybrid network composed of CTN and router/switch NEs
IP NEs support the following configurations:
l Basic NE configuration
l Interface configuration
l L2 configuration
l L3 configuration
l Configuration for single NE service and end-to-end service
l Security configuration
l UAS configuration
l OAM configuration
l QoS configuration
4-7

l Performance configuration
PCM NEs support the following configurations:
l Basic NE configuration
l NMS channel management
l Route management
4.6 Software Management

The U31 R22 system allows you to upgrade the board software in a batches, load the
equipment software, and manage the software versions.
l In the system, you can conveniently load the software package of new version to
the managed bearer equipment. The system can manage bearer equipment with
different software versions. You can conveniently switch the version to another for
the equipment when necessary.
l The E300, T31, and U31 R22 can be upgraded to the current version.
l If the upgrade fails, the system enables the equipment to roll its software back to the
previous one.
l The client software can be automatically downloaded from the server.
4.7 Log Management

The U31 R22 system provides three types of logs: operation log, security log, and system
log.
l Operation Log records operation information, including user name, operation level,
operations, command function, operation object, object group, object address, start
time, operation result, cause of operation failure, operation end time, host address,
and access mode.
l Security Log records login information, including user name, host address, log name,
operation time, access mode and details of the log.
l System Log records the completion state of time tasks on the server, including source,
level, log name, details, host address, start time, end time, and related log.
The log management module of the U31 R22 system provides the following log
management functions.
l Log Query
You can set filtering conditions to query specific logs in the system, and save or print
the query result.
l Log Backup
The system can back up the logs in the system as files according to the specified
number of days or storage capacity.
4-8

4.8 Report Management

The U31 R22 system provides a rich report resource for users to query information
including configuration report, information report, status report, and statistics report.
Users can check, export or print reports upon actual requirements.
4.9 Database Management

The database management functions include:
l Database Monitoring
If the database capacity reaches the preset threshold, the U31 R22 will generate an
alarm.
l Database Backup
l Offline Data Restoration
l Scheduled Backup
l Manual Backup
4.10 License Management

The purpose of license management is to control the management authorities of the U31
R22 system and NEs.
l NE license management: controls the types and quantity of manageable NEs.
l NMS license management: controls the NMS functions, such as exceptional service
management, service cutover management, and northbound interface.
4-9

4-10

Chapter 5
Network Designs and
Applications
Table of Contents
Deployment Schema ..................................................................................................5-1
Network Models .........................................................................................................5-4
Network Architecture Requirements ...........................................................................5-7
5.1 Deployment Schema

The U31 R22 provides two deployment modes: stand-alone server deployment and
dual-computer cluster system deployment. For the detailed deployment models, refer to
Table 5-1.
Table 5-1 U31 R22 Deployment Model
Deployment Model Operating System Disaster Tolerance Network Design

Complexity
Stand-alone server l Windows Low Simple

deployment l Solaris
l Linux
Dual-computer cluster l Windows High Complex

system deployment l Solaris
5.1.1 Stand-Alone System Deployment

In the stand-alone system deployment, only one U31 R22 server exists. All the processes
operate on the server and multiple clients can access and operate the server at the same
time.
The stand-alone system can be used on Windows, Solaris, and Linux. It uses the network
design that contains multiple clients and one server. The clients and the server are
connected via a LAN or WAN. For the network design, see Figure 5-1.
5-1

Figure 5-1 Stand-Alone System Deployment
5.1.2 Dual-Computer Cluster System Deployment

The U31 R22 dual-computer cluster system contains a master server and a slave server.
Multiple clients can access and operate on the servers. The hardware configuration of the
master server and the slave server must be the same. The master and slave servers can
be deployed at one location (local) or at different cities (remote) .
The master and slave servers can be deployed at one location (local) or at different cities
(remote).
l When the master and slave server are deployed at one location, the master server
and slave server use one hard disk array. The database data is stored in individual
hard disk arrays. When the master server fails, the slave server can access the data
in the hard disk array and process the services of the master server.
For the local hot standby redundancy, see Figure 5-2.
5-2

Chapter 5 Network Designs and Applications
Figure 5-2 Local Hot Standby Redundancy
l When the master and slave servers are deployed at different locations, they use two
computers. The data of the two servers is synchronized automatically. When the
master server fails, the services processed by the master server will be switched to
the slave server.
For the remote hot standby redundancy, see Figure 5-3.
Figure 5-3 Remote Hot Standby Redundancy
1. Ethernet interface for 3. Ethernet interface

remote dual-computer between the U31 R22
heartbeat server and a client
2. Ethernet interface for 4. Ethernet interface
the data replication between the U31 R22
network server and an NE
5-3

5.2 Network Models

The U31 R22 network uses the Client/Server (C/S) structure, in which the clients and
servers are connected via LANs or WANs. The U31 R22 servers communicate with the
managed NEs by using the inband network design or out-of-band network design.
Three types of the U31 R22 network design are optional: local network, remote network
and integrated network.
5.2.1 Non-Cascade Local Networking

Non-cascade local networking is the networking mode, in which the server, clients and
NEs are all located in the same Local Area Network (LAN).
For the topology of the non-cascade local networking of U31 R22, see Figure 5-4.
Figure 5-4 Non-Cascade Local Networking
5.2.2 Non-Cascade Remote Networking

The non-cascade remote networking refers to the network, in which the clients are located
remotely from the server and connected through Wide Area Network (WAN).
The non-cascade remote networking supports the transmission over leased line of Digital
Data Network (DDN), E1 line, or High-data-rate Digital Subscriber Line (HDSL).
The following introduces the remote networking based on DDN leased line
transmission mode and E1 transmission mode, which are commonly used in the actual
telecommunication networks due to their quality and cost advantages.
5-4

l Remote Networking Based on DDN Leased Line

For DDN leased line, routers and baseband MODEMs are used. At the server and
client, a hub is connected to a router and the router is connected to the leased line of
the DDN through a baseband MODEM.
For the remote networking of the U31 R22 system based on DDN leased line, see
Figure 5-5.
Figure 5-5 Non-Cascade Remote Networking over DDN
l Remote Networking Based on E1 Transmission

In the non–cascade remote networking over E1 transmission, E1 (2Mbit/s) lines are
used to transmit IP packets. At both ends of an E1 line, timeslot extractors are needed.
The maximum transmission rate of each timeslot is 64kbps. By the channelization
technology, N timeslots can be used together to get a rate of N×64kbps, which meets
the requirements for different transmission rates. A router and a channelized E1
module can be used together as a stable and reliable timeslot extractor.
For the remote networking of the U31 R22 system based on E1 transmission, see
Figure 5-6.
5-5

Figure 5-6 Non-Cascade Remote Networking Based on E1 Transmission Network
5.2.3 Non-Cascade Integrated Networking

The integrated networking is a combination of local networking and remote networking.
For the topology of the integrated networking over DDN, see Figure 5-7.
5-6

Figure 5-7 Non-Cascade Integrated Networking over DDN
5.3 Network Architecture Requirements

For the bandwidth requirement for the U31 R22 network architecture, refer to Table 5-2.
Table 5-2 Bandwidth Requirement for the U31 R22 Network Architecture
Item Bandwidth
Bandwidth between the client and the server At least 2 Mbit/s is recommended.
Bandwidth between the primary server and the At least 10 Mbit/s is recommended.
standby server
5-7

5-8

Chapter 6
System Interfaces
The U31 R22 system interfaces include internal interfaces, southbound interfaces, and
northbound interfaces.
Internal Interfaces
The internal interfaces of the U31 R22 system refers to the communication interfaces
between the server and the client. They adopt TCP/IP for communication. In the U31
R22 system, the server and the client communicate with each other through a Local Area
Network (LAN) or a Wide Area Network (WAN). The communication bandwidth is equal to
or greater than 2Mbps.
Southbound Interfaces
Southbound interfaces refer to the communication interfaces between U31 R22 and the
managed NEs.
The U31 R22 supports the SNMP, Syslog, Telnet/SSH, FTP/TFTP, and private interfaces.
Northbound Interfaces
The U31 R22 northbound interfaces locate between U31 R22 and the upper integrated
NMS/OSS (Operation Support System). The upper integrated NMS/OSS can manage the
northbound interfaces through U31 R22.
U31 R22 provides the following northbound interfaces of three types:
l BN-xTN northbound interface
à BN-xTN northbound CORBA interface
à BN-xTN northbound TMF CORBA (CTCC) interface
à BN-xTN northbound TMF CORBA (CTCC) dual-interface
à BN-xTN northbound SNMP interface
à BN-xTN northbound FTP (CSV) asset interface
à BN-xTN northbound FTP (CSV) performance interface
l Unified northbound interface
à Wireline northbound CORBA interface
à Wireline northbound XML(MTOS) interface
à Unified northbound SNMP interface
à Unified northbound MML interface
6-1

à Unified northbound FTP alarm/asset/performance interface

à Unified northbound DB interface
l Customized interface
à xTN FTP (CSV) asset interface (applicable to TM)
à xTN FTP (XML) asset interface (applicable to DiGi)
6-2

Chapter 7
Technical Specifications
Table of Contents
Performance Specifications ........................................................................................7-1
Reliability Specifications .............................................................................................7-2
7.1 Performance Specifications

For the performance specifications of the U31 R22 system, refer to Table 7-1.
Table 7-1 U31 R22 Performance Specifications
Item Specification
System response time l When the equipment operates properly, the response time for user
operations is less than 3 s.
l When the equipment operates abnormally (frequent alarms occur),
the response time for user operations is less than 30 s.
Mean response time for alarm display, which refers to the duration from
the time when NE generates an alarm to that when EMS displays the
alarm, is less than 10 s.
Mean system response time, which refers to the duration from the time
when an alarm is reported to that when the client displays the alarm, is
less than 3 s.
Master/slave network When the hot standby redundancy is used for the network management,
management system the time for switching the master and slave network management system
performance is less than 10 min.
Data storage capacity Alarm data storage time: It can be configured by users. The default value
is 6 months.
Performance data storage time: It can be configured by users. The

15–min performance history data generated in at least 3 months and
the 24–hour performance history data generated in at least 6 months
can be stored.
System log storage time: It can be configured by users. The default value
is 6 months.
Security and operation log storage time: It can be configured by users.

The default value is 6 months.
7-1

Note:
When the system operates with full load, the system response time should not be larger
than 150% of the above specifications.
7.2 Reliability Specifications

For the U31 R22 reliability specifications, refer to Table 7-2.
Table 7-2 U31 R22 Reliability Specifications
Item Specification
Mean Time Between Failures (MTBF) MTBF>=1200h

Mean time between severe failures is larger than
180 days
Mean Time To Recovery (MTTR) MTTR <=0.5h
Note:
l Ordinary failures refer to the failures that only affect partial functions of the system.
When an ordinary failure occurs, the system can operate properly.
l Severe failures refer to the failures that affect the entire system. When a severe failure
occurs, the system cannot operate properly.
7-2

Chapter 8
Environmental Requirements
Table of Contents
Power Specifications ..................................................................................................8-1
Environmental Specifications......................................................................................8-1
8.1 Power Specifications

The equipment room must be equipped with Uninterruptible Power Supplies (UPSs) or
inverters, and power generating equipment.
The power sockets in the equipment room should be clearly labelled.
The requirements for the AC power supply are as follows:

l Three-phase power supply: 380 V±10%, 50 Hz±5%, waveform distortion <5%
l Single-phase power supply: 220 V±10%, 50 Hz±5%, waveform distortion <5%
l Voltage waveform distortion of the backup generator <10%
8.2 Environmental Specifications

For the requirements for the environmental specifications of the equipment room where
the U31 R22 operates, refer to Table 8-1.
Table 8-1 U31 R22 Environmental Specifications
Item Operating Condition
Temperature +5 ºC to +35 ºC
Humidity 15% RH to 93% RH
8-1

8-2

Chapter 9
Compliant Standards
ITU-T Recommendations for TMN Concepts and Features
l ITU-T M.3000 overview of TMN Recommendations
l ITU-T M.3010 principles for a telecommunications management network
l ITU-T M.3013 considerations for a Telecommunications Management Network
l ITU-T M.3020 TMN interface specification methodology
l ITU-T M.3200 TMN management services overview
l ITU-T M.3300 F interface Requirements
l ITU-T M.3400 TMN management functions
ITU-T Recommendations for Communication Protocol Stacks

l ITU-T Q.811 low layer protocol profiles for the Q3 interface
l ITU-T Q.812 upper layer protocol profiles for the Q3 interface
l ITU-T X.200 Reference Model for OSI .
l ITU-T X.700 Management Framework for OSI
l ITU-T X.702 Application Context for Systems Management with OSI Transaction
Processing
l ITU-T X.703 Open Distributed Management Architecture
l ITU-T X.710 common management information service
l ITU-T X.711 common management information protocol
ITU-T Recommendations for Information Model Grammar Descriptions and

Definitions
l ITU-T X.208 Specification of Abstract Syntax Notation One (ASN.1)
l ITU-T X.209 Specification of BER for ASN.1
l ITU-T X.720 Information technology - Open System Interconnection - Structure of
management information: Management information model
l ITU-T X.721 Information technology - Open System Interconnection - Structure of
management information: Definition of management information
l ITU-T X.722 Information Technology - Open System Interconnection - Structure of
management information: Guidelines for the definition of managed objects
ITU-T Recommendations for Universal Information Model Definitions and System

Management Functions
l ITU-T M.3100 generic network information model
l ITU-T Q.811 low layer protocol profiles for the Q3 interface
l ITU-T Q.812 upper layer protocol profiles for the Q3 interface
9-1

l ITU-T Q.821 Stage 2 and Stage 3 Description for the Q3 Interface - Alarm surveillance
l ITU-T Q.822 Stage 1, Stage 2 and Stage 3 Description for the Q3 Interface -
Performance Management
l ITU-T X.730 object management function
l ITU-T X.731 state management function
l ITU-T X.733 alarm reporting function
l ITU-T X.734 event report management function
l ITU-T X.735 log control function
ITU-T Recommendations for SDH Information Model Definitions

l ITU-T G.774 SDH management information model for the network element view
l ITU-T G.774.01 SDH performance monitoring for the network element view
l ITU-T G.774.02 SDH configuration of the payload structure for the network element
view
l ITU-T G.774.03 SDH management of multiplex-section protection for the network
element view
l ITU-T G.774.04 SDH management of the subnetwork connection protection for the
network element view
l ITU-T G.774.05 SDH management of connection supervision functionality (HCS/LCS)
for the network element view
l ITU-T G.774.06 SDH unidirectional performance monitoring for the network element
view
l ITU-T G.774.07 SDH management of lower order path trace and interface labeling for
the network element view
l ITU-T G.784 Management of SDH
l DN 037-1997 Synchronous digital hierarchy (SDH) - management functions, ECC and
Q3 interfaces - Specifications for protocol stacks (temporary regulations)
ITU-T Recommendations for the ASON Network Management System

l ITU-T G.7712 Architecture and specification of data communication network
l ITU-T G.7714 Generalized automatic discovery techniques (port adjacent discovery,
layer adjacent: optical interface, OMS, RS)
l ITU-T G.7714.1 Protocol for automatic discovery in SDH and OTN networks
l ITU-T G.fame Framework for ASON management
ITU-T Recommendations for CTN Information Model Definitions

l ITU-T G.7710/Y.1701 Common equipment management function requirements
l ITU-T G.7712/Y.1703 Architecture and specification of data communication network
l RFC 4377 Operations and Management (OAM)
l ITU-T G.8601/Y.1391 Architecture of service management in multi-bearer,
multi-carrier environment
l ITU-T G.8114 Operation and maintenance mechanism for T-MPLS layer networks
l ITU-T G.8131 Linear protection switching for transport MPLS (T-MPLS) networks
9-2

Chapter 9 Compliant Standards
l ITU-T G.8132 T-MPLS Shared Protection Ring

l RFC 5654: MPLS-TP Requirements
l ITU-T Recommendation M.20, "Maintenance philosophy for telecommunication
networks", October 1992
l draft-ietf-mpls-tp-nm-req: MPLS TP Network Management Requirements
l draft-ietf-mpls-tp-nm-framework: MPLS-TP Networks Management Framework
ITU-T Recommendations for OTN Information Model Definitions

l ITU-T G.709 Interfaces for the Optical Transport Network (OTN)
l ITU-T G.798 Characteristics of optical transport network hierarchy equipment
functional blocks
l OTN alarm protocols supported by ITU-T X.721, M.3100,G.798 network management
systems
l OTN performance protocols supported by ITU-T M.3100, G.8201, G.798
ITU-T Recommendations for TMF Service Management Interfaces

l TMF 513 Multi-Technology Network Management Business Agreement (NML-EML
Interface)
l TMF 608 Multi-Technology Network Management Information Agreement
l TMF 814 Multi-Technology Network Management Solution Set Document
l TMF 508 Connection and Service Management Business Agreement
l TMF 605 Connection and Service Management Information
l TMF 807 Connection and Service Management Solution Set Document
CORBA Standards for OMG

l OMG, The Common Object Request Broker: Architecture and Specification, version
2.3.1, October 1999
l OMG, CORBA services: Common Object Services Specification, December 1998
l OMG, Interworking Between CORBA and TMN System Specification V1.0.
9-3

9-4

Glossary
AAA
- Authentication, Authorization and Accounting
APC
- Automatic Power Control
APO
- Automatic Power Optimization
ASON
- Automatically Switched Optical Network
BRAS
- Broadband Remote Access Server
BSS
- Business Support System
CAC
- Connection Admission Control
CGSL
- Carrier Grade Server Linux
CHAP
- Challenge Handshake Authentication Protocol
CORBA
- Common Object Request Broker Architecture
CTN
- Converged Transport Network
DCN
- Data Communications Network
DDN
- Digital Data Network
ECC
- Embedded Control Channel
EML
- Element Management Layer
EMS
- Element Management System
FE
- Fast Ethernet

FTP
- File Transfer Protocol
GE
- Gigabit Ethernet
HA
- High Availability
HCS
- Hierarchical Cell Structures
HDSL
- High-data-rate Digital Subscriber Line
IP
- Internet Protocol
ITU-T
- International Telecommunication Union - Telecommunication Standardization
Sector
KPI
- Key Performance Indicator
LAN
- Local Area Network
LCS
- LoCation Services
LCT
- Local Craft Terminal
LDAP
- Lightweight Directory Access Protocol
MODEM
- Modulator-Demodulator
MPLS
- Multiprotocol Label Switching
MPLS-TP
- Multi-Protocol Label Switching Transport Profile
MTBF
- Mean Time Between Failures
NBI
- Northbound Interface
NML
- Network Management Layer
NMS
- Network Management System
II

Glossary
OAM
- Operation, Administration and Maintenance
OMG
- Open Mobile Gateway
OMS
- Optical Multiplex Section
OSI
- Open System Interconnection
OSPF
- Open Shortest Path First
OSS
- Operation Support System
OTN
- Optical Transport Network
PAP
- Password Authentication Protocol
QoS
- Quality of Service
RS
- Regenerator Section
SD
- Signal Degrade
SDH
- Synchronous Digital Hierarchy
SNMP
- Simple Network Management Protocol
SQA
- Service Quality Analyzer
SRLG
- Shared Risk Link Group
SSL
- Secure Sockets Layer
T-MPLS
- Transport Multi-Protocol Label Switching
TCP
- Transmission Control Protocol
TLS
- Transport Layer Security
III

TMN
- Telecommunications Management Network
TP
- Transport Protocol
UPS
- Uninterruptible Power Supply
UTC
- Universal Time Coordinated
WAN
- Wide Area Network
WDM
- Wavelength Division Multiplexing
WEB
- Web
XML
- Extensible Markup Language
IV

NetNumen U31 R22 (V12.16.10) Unified Network Management System Product Description - V1.0

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

NetNumen U31 R22 (V12.16.10) Unified Network Management System Product Description - V1.0

Caricato da

Copyright:

NetNumen™ U31 R22

Unified Network Management System

Revision No. Revision Date Revision Reason

R6.0 2015-12-30 NetNumen™ U31 R22 (V12.16.10) Issued.

Updated the "Manageable NEs", "New Features", "Important

R5.1 2015-06-30 NetNumen™ U31 R22 (V12.15.10P02) Issued.

Updated the "Manageable NEs", "New Features", "Important

R5.0 2014-12-30 NetNumen™ U31 R22 (V12.15.10) Issued.

l Updated the "Manageable NEs", "New Features", and

R4.1 2014-06-30 NetNumen™ U31 R22 (V12.14.10P02) Issued.

l Updated the "New Features".

R4.0 2013-12-20 NetNumen™ U31 R22 (V12.14.10) Issued.

l Updated the "Manageable NEs" and "New Features".

SJ-20151230113133-001|2015-12-30 (R6.0) ZTE Proprietary and Confidential

R3.2 2013-07-30 NetNumen™ U31 R22 (V12.13.10P02) Issued.

l Updated the "Location of the Product in a Bearer Network",

R3.1 2013-03-25 NetNumen™ U31 R22 (V12.13.10P01) Issued.

l Updated the "Location of the Product on a Bearer Network",

R3.0 2012-12-30 NetNumen™ U31 R22 (V12.13.10) Issued.

l Updated the "System Overview", "New Features", "Product

R2.1 2012-11-19 NetNumen™ U31 R22 (V12.12.20P01) Issued.

Updated the "Manageable NEs", "New Features" section.

R2.0 2012-07-30 NetNumen™ U31 R22 (V12.12.20) Issued.

l Added the "Computer Ports Occupied by the System", "New

Serial Number: SJ-20151230113133-001

Publishing Date: 2015-12-30 (R6.0)

Chapter 2 New Features............................................................................. 2-1

Chapter 3 System Architecture ................................................................. 3-1

Chapter 4 System Functions ..................................................................... 4-1

Chapter 5 Network Designs and Applications......................................... 5-1

Chapter 6 System Interfaces ..................................................................... 6-1

SJ-20151230113133-001|2015-12-30 (R6.0) ZTE Proprietary and Confidential

Chapter 8 Environmental Requirements .................................................. 8-1

Chapter 9 Compliant Standards................................................................ 9-1

SJ-20151230113133-001|2015-12-30 (R6.0) ZTE Proprietary and Confidential

What Is in This Manual

Chapter 4, System Functions Describes the functions of the U31 R22.

Chapter 7, Technical Describes the performance specifications and interface

Chapter 8, Environmental Describes the power specifications and environmental

SJ-20151230113133-001|2015-12-30 (R6.0) ZTE Proprietary and Confidential

| Separates individual parameters in a series of parameters.

Danger: indicates an imminently hazardous situation. Failure to comply can result in

Warning: indicates a potentially hazardous situation. Failure to comply can result in

Caution: indicates a potentially hazardous situation. Failure to comply can result in

Note: provides additional information about a topic.

SJ-20151230113133-001|2015-12-30 (R6.0) ZTE Proprietary and Confidential

1.1 Location of the Product in a Bearer Network

SJ-20151230113133-001|2015-12-30 (R6.0) ZTE Proprietary and Confidential

Figure 1-1 Location of the U31 R22 in the Bearer Network

1.2 Product Features

Advanced Architecture and Scalability

Multiple Network Management Scales Supported

SJ-20151230113133-001|2015-12-30 (R6.0) ZTE Proprietary and Confidential

Multiple Standard Northbound Interfaces Supported

Service Deployment Features

Value-Added Function Features

SJ-20151230113133-001|2015-12-30 (R6.0) ZTE Proprietary and Confidential

CTN equipment value-added functions

SJ-20151230113133-001|2015-12-30 (R6.0) ZTE Proprietary and Confidential

1.3 Manageable NEs

NE Type NE and Hardware Version

CTN ZXCTN 6100 (V1.10)

SJ-20151230113133-001|2015-12-30 (R6.0) ZTE Proprietary and Confidential

NE Type NE and Hardware Version

ZXCTN 9004 (V2.08.32/V2.08.33/V2.08.33R1)

SDH ZXMP S100 (V1.00)