12 NetNumen U31 R22 (V12.13.10) Product Description

NetNumen™ U31 R22
Unified Network Management System

Product Description
Product Version: V12.13.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://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2013 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 ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Data Revision Reason
R3.0 2012-12-30 NetNumen™ U31 R22 (V12.13.10) Issued.
l Updated the "System Overview", "New Features", "Product

Interfaces", Product Functions", "Technical Specifications",
"Compliant Standards" chapter.
l Added the "Environmental Requirement" chapter.
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

Features" chapter.
l Updated the "Network Architecture Requirement", "Cascade
Networking Modes" section.
Serial Number: SJ-20121127091048-001
Publishing Date: 2012-12-30 (R3.0)
SJ-20121127091048-001|2012-12-30 (R3.0) ZTE Proprietary and Confidential

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 applies to the following engineers:
l Planning engineers
l Monitoring personnel
l Maintenance engineers
What Is in This Manual

This manual contains the following contents:
Chapter Content
1, System Overview Describes the system overview, position, features, managed

NEs, management functions, interfaces, technical specifications,
and compliant standards of the U31 R22.
2, New Features Describes the new functions and important changes of the U31
R22.
3, Product Architecture Describes the hardware architecture and software architecture

of the U31 R22.
4, Product Functions Describes the functions of the U31 R22.
5, Network Designs and Describes the U31 R22 deployment plans, network designs, and
Applications requirements for network bandwidths.
6, Product Interfaces Describes the logical interfaces and physical interfaces of U31
R22.
7, Technical Specifications Describes the performance specifications and interface

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

specifications of the U31 R22.
9, Compliant Standards Describes the standards that the U31 R22 complies with.
Conventions
This manual uses the following typographical conventions:

Typeface Meaning
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 certain topic.
II

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

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

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

4.1 Topology Management ....................................................................................... 4-1
4.2 Alarm Management ............................................................................................ 4-3
4.3 Performance Management.................................................................................. 4-4
4.4 Security Management......................................................................................... 4-5
4.5 Configuration Management ................................................................................. 4-8
4.6 Software Management........................................................................................ 4-9
4.7 Log Management ............................................................................................. 4-10
4.8 Report Management......................................................................................... 4-10
4.9 Database Management .................................................................................... 4-10
4.10 License Management ......................................................................................4-11
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-5
5.2.3 Non-Cascade Integrated Networking ......................................................... 5-7
5.3 Network Architecture Requirements..................................................................... 5-8
Chapter 6 Product Interfaces .................................................................... 6-1

6.1 Logical Interfaces ............................................................................................... 6-1
6.2 Physical Interfaces ............................................................................................. 6-2
Chapter 7 Technical Specifications .......................................................... 7-1

7.1 Performance Specifications................................................................................. 7-1
7.2 Reliability Specifications ..................................................................................... 7-2
7.3 Computer Ports Occupied by the System ............................................................ 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

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

U31 R22 is a unified management platform that manages all types of equipment of ZTE
bearer networks, including CTN, SDH, WDM/OTN equipment, routers, BRASs, and
switches.
U31 R22 is a network management system that is located at the network element
management layer/subnetwork management layer and performs the network element
layer and network layer management.
For the position of the U31 R22 in a bearer network, see Figure 1-1.
1-1

NetNumen™ U31 R22 Product Description
Figure 1-1 Position of U31 R22 in the Bearer Network
• BSS: Business Support • NBI: North Bound Interface • WDM: Wavelength Division
System • IP: Internet Protocol Multiplexing
• OSS: Operation Support • LCT: Local Craft Terminal • OTN: Optical Transport
System • CTN: Converged Packet Network
• EMS: Network Element Transport Network • SDH: Synchronous Digital
Management System • BRAS: Broadband Remote Hierarchy
• NMS: Network Access Server
Management System
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, so that all
services, alarms and performances are monitored and managed on a unified platform.
Advanced Architecture and Scalability

l Strong equipment management capacity
The U31 R22 uses a distributed architecture and features high flexibility and scalability.
The client module, server module, and database module can operate on one computer
or on multiple computers.
l Flexible plug-in design
1-2

Chapter 1 System Overview
The U31 R22 kernel uses a plug-in design. The functional modules can be customized
by adding the plug-ins. The plug-in design has a strong scalability.
Networking Advantages
l Flexible network design
The U31 R22 has a three-layer architecture based on the client module, server
module, and adapter module. These modules can be deployed separately and
connected remotely.
l Large management scale
The U31 R22 can manage up to 30000 equivalent network elements. Up to 200 clients
can be connected at the same time. The U31 R22 software can guarantee large-scale
network management and lower the CAPEX of operators for capacity expansion in the
future.
Standard Northbound Interface

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 Advantages

Universal service deployment advantages
l Quick end-to-end service provisioning
The U31 R22 supports comprehensive end-to-end service management and supports
quick service scheduling and monitoring.
The U31 R22 supports the circuit management, such as service configuration
and maintenance management. The U31 R22 supports service adjustment and
service performance alarm maintenance management. The U31 R22 allows a quick,
convenient and secure end-to-end service management to users.
l Centralized service management
In the service view interface the U31 R22 manages the services including tunnels,
GRE tunnels, pseudo-wire (PW), multi-segment pseudo-wire (MS-PW), TDM,
Ethernet, ATM, L2 VPN(VPWS/VPLS), L3 VPN, WDM, OCH/OAC services. You
do not need to switch among operation interfaces for service management and
maintenance. This lowers the operation & maintenance costs and difficulties.
l Cross-domain service management
The U31 R22 allows cross-domain service management between CTN and IP, CTN
and MSTP, CTN/MSTP and WDM/OTN. The U31 R22 allows sound end-to-end
management solution for a hybrid network.
1-3

Advantages of CTN equipment service deployment

l Quick service navigation
The U31 R22 supports a convenient navigation of services. You can navigate to the
related service management pages from the topology, alarm or performance views,
which facilitates the fault location, service query, and maintenance.
l One-touch service setup
The “one-touch service setup” tool helps with the service creation. After you perform
the end-to-end service creation, the service will be set up with tunnels and PWs, which
greatly simplifies the service creation steps.
l Convenient and secure service capacity expansion and reduction
The U31 R22 supports the intelligent and secure service expansion and reduction
function.
l Intelligent and reliable service cutover
The U31 R22 supports intelligent, convenient and reliable CTN network cutover. The
user-friendly service cutover interface can greatly lower the operation complexity. The
verification before the cutover guarantees the cutover effect and accuracy. The data
synchronization after the cutover ensures data consistency. If the cutover fails, the
original data and configuration can be restored to ensure the network security and
reliability.
l Port service migration function
The U31 R22 supports flexible migration of CTN port services. The services on a
specific port can be migrated to other ports for the service recovery.
l Link capacity upgrade function
The U31 R22 supports the CTN link capacity upgrade function. After the services are
provided, the network link capacities need to be upgraded due to the expansion of
network service capacity. Because the physical links in the current CTN networks use
Ethernet interfaces, the capacities of the following Ethernet links can be upgraded:
FE->GE, GE->10GE, FE->10GE.
IP equipment service deployment advantages:
l User-friendly deployment interface
A user-friendly interface design is used in the hardware configuration, layer 2
configuration, layer 3 configuration, and service deployment configuration. The
services are displayed in tabs (similar to those in web browsers). The service details
are listed in the tabs, the service topologies are displayed graphically, and the service
change histories are displayed as well.
A quick service-related navigation is provided for each service. For example, the
VPN service can be navigated to the related interfaces, such as VLAN, tunnel, AC,
PW configuration, which facilitates the switching among interfaces and improves the
deployment efficiency.
1-4

l Offline pre-configuration capability

The U31 R22 supports offline configuration and online configuration. Before the
configuration, the resource synchronization can be viewed to avoid artificial conflicts
and errors. After configuration, verification should be performed to ensure the
normal operation of the NEs. If any equipment cannot be managed by the network
management system, you can check the original configuration by setting the
equipment to be offline to locate the fault. Before setting up a network or expanding
the network capacity, you can configure the equipment offline, check the configuration
data, and then apply the configuration data.
l Perfect service deployment policy
The U31 R22 supports continuous service configuration and sending services in
batches. The U31 R22 supports incremental deployment. When some non-critical
deployment is performed, the current services will not be affected, and the online
services are not broken. The U31 R22 provides flexible time policies. The periodic
deployment, timed deployment and one-time deployment are available for option,
which can minimize the impacts of service peak on the networks.
Value-Added Function Advantages

Advantages of universal value-added functions:
l Flexible equipment offline configurations
The U31 R22 supports offline configuration and online configuration. If any equipment
cannot be managed by the network management system, you can check the original
configuration by setting the equipment to be offline to locate the fault. Before setting
up a network or expanding the network capacity, you can configure the equipment
offline, check the configuration data, and then send the configuration data.
l Remote online upgrade
The U31 R22 supports downloading NCP software/board software remotely via FTP
and supports upgrading NCP software/board software online.
l 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
to reduce the fault handling time when any emergency alarm occurs. The network
alarms and service data can be related and navigated in multiple ways. Specific
alarm prompts and handling methods can be set for services of important users so
that operators can provide customized services.
l Resource views
The U31 R22 provides the MPLS-related resources views, including the configuration
view and actual view. The resources views can display statistics on the ports, tunnels,
and PWs bandwidth utilization and display the physical link bandwidth utilization in
topology. More than one NE can be selected to be viewed at the same time.
1-5

The bandwidth utilization can be set to Full, High, Middle, Low, and Empty. They are
highlighted in various colors. The statistics analysis results are generated in reports.
l Statistics, analysis and report management function
The U31 R22 supports a powerful report function, including report templates and
report task management. The report template function supports designing a report
as required. The report management function supports generating reports based on
the preset task triggering rules and template parameters.
l Multiple time zones and daylight saving time function
The U31 R22 supports multiple time zones and daylight saving time. 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. They should be planned in advance and can
be selected when the U31 R22 is installed.
Advantages of CTN equipment value-added function
l Plug and play function
In the initial network installation and deployment, the equipment can obtain the
initialization information automatically, so that NEs can be managed and maintained
remotely without manual operations.
l 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 Preventive maintenance design
The U31 R22 can set the reference value, optimal threshold, and maximum threshold
for the analog variables, such as optical power.
l The U31 R22 provides an intelligent performance analysis system, which 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, such as loop and laser shutdown at a scheduled time.
l Inspection tool
The U31 R22 supports remote and centralized equipment patrol and inspection,
generates inspection reports and simplifies the inspection procedure.
Advantages of WDM/OTN equipment value-added functions
l Clear 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 OTN APO subsystem
1-6

The APO subsystem supports the manual power optimization and automatic power
optimization of OTN equipment. The manual power optimization refers to triggering
the network power optimization in command. The automatic power optimization
refers to triggering the network power optimization at a scheduled time. The APO
subsystem can guarantee the gain attenuation and optimization of OMS signals and
the optimization of OSNR of the OCH signals at receiving ends.
l OTN APC subsystem
If the optical power in the OTN main optical path is lost, the APC subsystem 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 Unique channel view
The unique channel view displays the ports in boards, services and alarms on the
ports so that the ports and services can be maintained with convenience.
l Preventive maintenance design

The U31 R22 can set the reference value, optimal threshold, and maximum threshold
for the analog variables, such as optical power. You can know the equipment operation
by viewing the current performance in real time.
The U31 R22 provides the performance analysis system, which 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, such as loop and laser shutdown at a scheduled time.
Advantages of IP equipment value-added functions

l Plug and play function
In the initial network installation and deployment, the equipment can obtain the
initialization information automatically, so that NEs can be managed and maintained
remotely without manual operations.
l Inspection tool
The U31 R22 supports remote and centralized equipment patrol and inspection,
generates inspection reports and simplifies the inspection procedure. The inspection
reports can provide detailed information and defects about each equipment and
scores them.
l Network performance analysis through WEB
Together with external tools, the U31 R22 provides the network analysis and report
function through WEB. The U31 R22 provides the network performance and quality
monitoring tool by using the Web interfaces, combined views, diagrams, data
templates, end-to-end measurement management, quantized data, and preset report
1-7

templates. The resource performance data in the IP network can be collected,

converged, processed and stored.
Security Advantages
l Reliable backup routes
The U31 R22 can provide backup routes by connecting multiple gateway NEs. 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 Data consistence protection
The U31 R22 uses database backup and database synchronization mechanism to
ensure the consistency of the data.
à When multiple clients and servers exist in one network, the synchronization
mechanism can guarantee the data consistency of these servers and clients.
à The master/slave network management systems can ensure the data consistency
of multiple servers.
à When LCT modifies data, the data on EMS is synchronized.
à The U31 R22 supports data upload and download.
à The U31 R22 supports two types of data synchronization mechanisms, that is,
the based on equipment data and based on network management system.
1.3 Manageable NEs

l SDH NEs
ZXMP S100, ZXMP S150, ZXMP S200, ZXMP S320, ZXMP S325, ZXMP S330,
ZXMP S335, ZXMP S360, ZXMP S380, ZXMP S385, ZXMP S390, ZXONE 5800,
ZXONE 5800-E.
l WDM/OTN NEs
ZXWM-32, ZXMP M600, ZXMP M720, ZXMP M721, ZXMP M800, ZXWM M900,
ZXMP M820, ZXMP M920, ZXONE 8000, ZXONE 8300, ZXONE 8500, ZXONE 8700
X32.
l CTN NEs
ZXCTN 6100, ZXCTN 6110, ZXCTN 6120, ZXCTN 6130, ZXCTN 6150, ZXCTN
6200, ZXCTN 6220, ZXCTN 6300, ZXCTN 6320, ZXCTN 6500-8, ZXCTN 6500-16L,
ZXCTN 6500-32, ZXCTN 9002, ZXCTN 9004, ZXCTN 9008.
1-8

l UAS Products
ZXUAS 10600, ZXE10 UAS2500S, ZXUAS 10800E, ZXUAS 10400, ZXUAS 10800.
l Router
ZXR10 T8000-16, ZXR10 M6000-8, ZXR10 M6000-16, ZXR10 M6000-8s, ZXR10
M6000-5s, ZXR10 M6000-3s, ZXR10 T1200, ZXR10 T1200 BMSG, ZXR10 T600,
ZXR10 T600 BMSG, ZXR10 T128, ZXR10 T64E, ZXR10 GER, ZXR10 GER04,
ZXR10 GER02, ZXR10 1822, ZXR10 1842, ZXR10 2842, ZXR10 2882, ZXR10
3842, ZXR10 3884, ZXR10 1809, ZXR10 2822R, ZXR10 1842R, ZXR10 2842R,
ZXR10 2882R, ZXR10 2822, ZXR10 2884, ZXR10 ZSR 3822, ZXR10 3844, ZXR10
3882, ZXR10 1822E, ZXR10 GAR 2604, ZXR10 GAR2608, ZXR10 GAR3608,
ZXR10 GAR7208, ZXR10 T16S, ZXR10 T16C, ZXR10 T32C, ZXR10 T64C, ZXR10
T160, ZXR10 T1216, ZXR10 T1212, ZXR10 6802, ZXR10 6804, ZXR10 6812, and
ZXR10 6800.
l Switch
ZXR10 8902, ZXR10 8905, ZXR10 8908, ZXR10 8912, ZXR10 8902E, ZXR10
8905E, ZXR10 8908E, ZXR10 8912E, ZXR10 6902, ZXR10 6905, ZXR10 6908,
ZXR10 T40G, ZXR10 T64G, ZXR10 T160G, ZXR10 T240G, ZXR10 5224, ZXR10
5228, ZXR10 5228-FI, ZXR10 5252, ZXR10 5928, ZXR10 5928-FI, ZXR10 5928-PS,
ZXR10 5928E, ZXR10 5928E-FI, ZXR10 5952, ZXR10 5952E, ZXR10 5916E,
ZXR10 5128E, ZXR10 5116E, ZXR10 5128E-FI, ZXR10 5228A, ZXR10 5252A,
ZXR10 3928A, ZXR10 3928A-FI, ZXR10 3952A, ZXR10 3228A, ZXR10 3228A-EI,
ZXR10 3228A-FI, ZXR10 3252A, ZXR10 3206, ZXR10 3226, ZXR10 3228, ZXR10
3226-FI, ZXR10 3252, ZXR10 3906, ZXR10 3928, ZXR10 3928E, ZXR10 3928E-FI,
ZXR10 3952, ZXR10 3952E, ZXR10 59S STACK.
ZXR10 5109, ZXR10 5116, ZXR10 5116-FI, ZXR10 5116-SI, ZXR10 5124, ZXR10
5124-FI, ZXR10 5124-SI, ZXR10 2920-SI, ZXR10 2928-SI, ZXR10 2952-SI, ZXR10
2936-FI, ZXR10 2909-SI, ZXR10 2909-FU, ZXR10 2918-SI, ZXR10 2926-SI, ZXR10
2910E-PS, ZXR10 2918E, ZXR10 2918E-PS, ZXR10 2928E, ZXR10 2952E, ZXR10
2609-LE, ZXR10 2818S-LE, ZXR10 2826S-LE, ZXR10 2852S-LE, ZXR10 2609A,
ZXR10 2618A, ZXR10 2626A, ZXR10 2826A, ZXR10 2826A-PS, ZXR10 2609,
ZXR10 2609-FU, ZXR10 2809, ZXR10 2809-FU, ZXR10 2818S, ZXR10 2826S,
ZXR10 2852S, ZXR10 2826E, ZXR10 2618, ZXR10 2626, ZXR10 2609-EI, ZXR10
2818S-EI, ZXR10 2826S-EI, ZXR10 3904F, ZXR10 3904, ZXR10 3206S, ZXR10
2826, ZXR10 1816, ZXR10 29S STACK, ZXR10 5009.
ZXR10 5250-28TC, ZXR10 5250-52TC ZXR10 5250-28SM, ZXR10 5250-28PM,
ZXR10 5250-52PM, ZXR10 2928E-PS, and ZXR10 2950-28PC.
l Government and Enterprise Network Products

ZXR10 5950-28TM, ZXR10 5950-28SM, ZXR10 5950-52TM, ZXR10 5950-28PM,
ZXR10 5950-24T, ZXR10 5950-48T, ZXR10 5250-24T, ZXR10 5250-52TM, ZXR10
3950-28TM, ZXR10 3950-28SM, ZXR10 3950-28PM, ZXR10 3950-52TS, ZXR10
2950-52TS, ZXR10 2950-28TC, ZXR10 2950-18TC, ZXR10 2950-18PC, ZXR10
1-9

2950-10PC, ZXR10 2850-18TM, ZXR10 2850-26TM, ZXR10 2850-52TC, ZXR10

2850-9TT, ZXR10 2850-9TS.
1-10

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

New Functions Provided by V12.13.10 (Compared With the U31 R22 V12.12.20P01)
Compared with the U31 R22 V12.12.20P01, the V12.13.10 provides the following new
functions, refer to Table 2-1.
Table 2-1 New Functions Provided by V12.13.10 (Compared With the U31 R22
V12.12.20P01)
No. Function Description
1 Supports the ZXCTN 6500 Refer to “Manageable NEs ” in the NetNumen™ U31 R22
V1.00R1 Unified Network Management System Product Description.
2 ZXCTN 9000 (V2.08.33R1) Refer to “Manageable NEs ” in the NetNumen™ U31 R22
Unified Network Management System Product Description.
3 Monitors real-time MSTP Refer to “Basic Maintenance Operations” in the NetNumen™

traffic U31 R22 Unified Network Management System Operation
Guide (SDH NE Management).
4 DCN view Refer to “DCN Management” in the NetNumen™ U31 R22

Unified Network Management System Operation Guide (CTN
NE Management).
5 Virtual NEs, virtual links Refer to “Topology Management” in the NetNumen™ U31
R22 Unified Network Management System Operation Guide
(Common Operations).
6 Resource analysis function Refer to “Report Management” in the NetNumen™ U31

(Common Operations).
7 Supports the ZXR10 5900E Refer to “Manageable Products” in the NetNumen™ U31 R22
(V2.09.10) Unified Network Management System Operation Guide (Data
Product NE Management).
2-1

8 Supports the ZXR10 5960 Refer to “Manageable Products” in the NetNumen™ U31 R22
(V2.09.10) Unified Network Management System Operation Guide (Data
Product NE Management)
9 Supports ZXR10 M6000 Refer to “Manageable Products” in the NetNumen™ U31 R22
(V2.00.20) (topology Unified Network Management System Operation Guide (Data
management, alarm, Product NE Management)
performance, rack diagram)
10 Supports ZXR10 T8000 Refer to “Manageable Products” in the NetNumen™ U31 R22
(V 2.00.20) (topology Unified Network Management System Operation Guide (Data
11 Supports ZXR10 M6000-nS Refer to “Manageable Products” in the NetNumen™ U31 R22
(V2.00.20) (topology Unified Network Management System Operation Guide (Data
12 Supports IPV6 protocol Refer to “IPV6 Management” in the NetNumen™ U31 R22
management channel; Unified Network Management System Operation Guide (Data
supports browsing the IPV6 Product NE Management).
protocol
13 Supports configuring the Refer to “DOT1X Management” in the NetNumen™ U31 R22
802.1X on middle-end Unified Network Management System Operation Guide (Data
switches Product NE Management).
14 Supports configuring the QoS Refer to “Configuring Common Template” in the NetNumen™
on middle-end switches U31 R22 Unified Network Management System Operation
Guide (Data Product NE Management).
15 Resource views support Refer to “BN NE Resource View Management” in the

abnormal traffic monitoring NetNumen™ U31 R22 Unified Network Management System
and packet performance Operation Guide (Data Product NE Management).
reports
16 Creating links in batches Refer to “Creating a Link” in the NetNumen™ U31 R22 Unified
Network Management System Operation Guide (Data Product
NE Management).
17 Supports northbound interface Refer to the NetNumen™ U31 R22 Unified Network
in XML Management System Northbound Interface User Guide (Data
Products).
18 Transparent PW -
19 Service parameter templates -
2-2

Chapter 2 New Features
20 Supports multiple-section Refer to “Configuring SDH Services with SNCP” in the

SNCP NetNumen™ U31 R22 Unified Network Management System
Operation Guide (SDH End-to-End Management).
New Functions Provided by V12.12.20P01 (Compared With the U31 R22 V12.12.20)
Compared with the U31 R22 V12.12.20, the V12.12.20P01 provides the following new
functions, refer to Table 2-2.
Table 2-2 New Functions of the U31 R22 V12.12.20P01
1 Supports the ZXCTN 6130 Refer to “Manageable NEs” in the NetNumen™ U31 R22
Unified Network Management System Product Description.
2 The SDH equipment Refer to “Creating SDH Services” in the NetNumen™ U31
supports VC3 R22Unified Network Management System Operation Guide
concatenation (SDH NE Management).
3 Supports cross-version Refer to “Data Backup and Restoration” in the NetNumen™

and cross-scale data U31 R22 Unified Network Management System Operation
restoration Guide (Common Operations).
4 Supports PCM equipment Refer to “Installing the U31 R22” in the NetNumen™ U31 R22
Unified Network Management System Installation Guide.
5 Supports the IP RAN Refer to the NetNumen™ U31 R22 Unified Network
function Management System Operation Guide (IP RAN Management).
6 Supports the ZXR10 6800 Refer to the NetNumen™ U31 R22 Unified Network
series equipment Management System Operation Guide (Data Product NE
Management).
7 The resource view supports Refer to the NetNumen™ U31 R22 Unified Network
topology monitoring over Management System Operation Guide (Data Product NE
CPU and memory Management).
2.2 Important Changes

Changed Items in the V12.13.10 (Compared With the U31 R22 V12.12.20P01)
Compared with the U31 R22 V12.12.20P01, the following items in the V12.13.10 are
changed, refer to Table 2-3.
2-3

Table 2-3 Changes of U31 R22 V12.13.10 (Compared With V12.12.20P01)
1 The MSTP EPS protection Refer to “Configuring Equipment-Level Protection” in the

can be configured in the NetNumen™ U31 R22 Unified Network Management System
end-to-end mode. Operation Guide (SDH NE Management)
2 Real-time MSTP Refer to “Basic Maintenance Operations” in the NetNumen™

monitoring U31 R22 Unified Network Management System Operation
Guide (SDH NE Management).
3 Changes the resource view Refer to “Maintenance Skills” in the NetNumen™ U31 R22
NE Management).
4 Changes the channel view Refer to “Maintenance Skills” in the NetNumen™ U31 R22
NE Management).
5 Changes the optical power Refer to “Maintenance Skills” in the NetNumen™ U31 R22
view Unified Network Management System Operation Guide (CTN
NE Management).
6 Updates the U31 R22 Refer to the NetNumen™ U31 NMS R22 Unified Network
product function Management System User Guide.
7 Updates the IP RAN Refer to the NetNumen™ U31 R22 Unified Network
function Management System Operation Guide (IP RAN Management).
8 Updates the installation Refer to “Installing the U31 R22” in the NetNumen™ U31 R22
scale Unified Network Management System Software Installation
Guide.
9 Updates the U31 R22 LCT Refer to the NetNumen™ U31 R22 Unified Network
product function Management System Local Craft Terminal (User Guide)
10 Service cutover Refer to “Service Leasing” in the NetNumen™ U31 R22

End-to-End Management)
11 Improves the product -

operation
12 Improves the WDM Refer to “Protection Management” in the NetNumen™ U31

protection subnetwork R22 Unified Network Management System Operation Guide
management (WDM/OTN NE Management)
13 Supports up to 30000 -
equivalent NEs
2-4

Chapter 2 New Features
14 Improves the file -

management backup
policy: the backup time
and space occupation are
reduced
15 Supports the ACL Refer to “ACL Management” in the NetNumen™ U31 R22
management for 8900 Unified Network Management System Operation Guide (Data
serials equipment Product NE Management).
16 Private network route Refer to “Configuring a Route Viewer” in the NetNumen™ U31
monitoring R22 Unified Network Management System Operation Guide
(Data Product NE Management).
Changed Items in the V12.12.20P01 (Compared With the U31 R22 V12.12.20)
Compared with the U31 R22 V12.12.20, the following items are changed in V12.12.20P01,
refer to Table 2-4.
Table 2-4 New Functions of the U31 R22 V12.12.20P01
1 Changes the SUN Refer to the “Installing the U31 R22 on Solaris” section of the
server model NetNumen™ U31 R22 Unified Network Management System
Installation Guide.
2 Simplifies the software Refer to the “Installing the U31 R22” section of the NetNumen™
installation disk and U31 R22 Unified Network Management System Installation Guide.
changes the installation
procedure
3 Optimizes the product -

operation
4 Changes the fiber Refer to the following manuals:

connection function The “Fiber Connection” section of the NetNumen™ U31 R22
Unified Network Management System Operation Guide (SDH NE
Management).
The “Fiber Connection” section of the NetNumen™ U31 R22
Unified Network Management System Operation Guide (CTN NE
Management).
The “Fiber Connection” section of the NetNumen™ U31
(WDM/OTN NE Management).
5 Optimizes the service Refer to the “Managing Service Cutover” section of the
cutover function NetNumen™ U31 R22 Unified Network Management System
Operation Guide (SDH/OTN NE End-to-End Management).
2-5

6 TL1 and FTP Refer to the NetNumen™ U31 R22 Unified Network Management
northbound supports the System Northbound Interface User Guide (Data Product).
5900E series equipment
7 Supports daughter Refer to the NetNumen™ U31 R22 Unified Network Management
cards on the 2900E System Operation Guide (Data Product NE Management).
series equipment
8 Supports the BRAS user Refer to the NetNumen™ U31 R22 Unified Network Management
statistics management System Operation Guide (Data Product NE Management).
2-6

Chapter 3
Product 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.
3-1

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.
U31 R22 use Windows/Solaris/Linux servers.
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 modules: clients, servers, adapters and the
databases, see Figure 3-2.
3-2

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

This page intentionally left blank.
3-4

Chapter 4
Product Functions
Table of Contents
Topology Management ...............................................................................................4-1
Alarm Management ....................................................................................................4-3
Performance Management .........................................................................................4-4
Security Management ................................................................................................4-5
Configuration Management ........................................................................................4-8
Software Management ...............................................................................................4-9
Log Management .....................................................................................................4-10
Report Management.................................................................................................4-10
Database Management ............................................................................................4-10
License Management ...............................................................................................4-11
4.1 Topology Management

The U31 R22 system is required to support the centralized management and group
management of all the managed devices due to the large quantity and diversity of
managed devices. The topology management module of the U31 R22 system provides
various topology management functions to display the distribution and organization of
devices on topology views.
A topology view is divided into two parts: the navigation pane on the left part, and the
topology map on the right part. The navigation pane provides a network element tree that
lists all the managed network elements (NEs) in the system. The topology map shows
the managed NEs on a map according to their locations and relations in the network. In
addition, some alarm and configuration information of NEs is also available on the topology
view.
The following lists the topology management functions that you can use in the U31 R22
system.
l Navigation
The NEs added in the system are listed on an NE tree in the navigation pane,
corresponding to the NE icons displayed on the topology map. When you add or
delete an NE through shortcut menu on the NE tree, corresponding NE icon appears
or disappears on the topology map at the same time. You can locate corresponding
NE icon on the topology map by clicking the NE on the NE tree. Besides some
topology management functions, the NE tree also provides the access to some other
management functions through shortcut menu, including configuration management,
fault management, and performance management functions.
4-1

l Graphic Display
The topology map shows all NEs managed by the system as well as their relations in
the network. You can search for specific NEs on the topology map, lock some NE icons
to prevent them from being moved by other users, and view the statistical information
of the NEs in the system, including NE quantity, link quantity, group quantity, and alarm
information.
l Display of NEs and Links
NEs and links between NEs that have connection relations are displayed on the
topology map. You can set the attributes of an NE to determine whether to show its
peripheral device.
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.
à 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
To ensure the system security, 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 certain rules. Then
the topology map can arrange the NEs by group.
4-2

Chapter 4 Product Functions
4.2 Alarm Management

The fault management module monitors the operating status of the equipment in real time.
The alarm status is displayed by colors. 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. In addition, the fault management module can
automatically save the alarm information into files according to preset parameters.
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. On the topology map, you can open the board
management view of a faulty NE to locate the board where an alarm is generated.
l Alarm Acknowledging and Unacknowledging
When an alarm is reported and displayed on the client screen, you can acknowledge
the alarm. The system saves the record of your acknowledging operation. You can
also cancel the acknowledgement of an alarm, that is, unacknowledging the alarm.
All acknowledging and unacknowledging operations are recorded, including the
information of the users performing the operations as well as the operation time.
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. In the
alarm list, you can filter alarms by occurrence time or severity level. When the system
receives new alarms from managed NEs, it refreshes the alarm list automatically.
l Alarm Clearing
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.
U31 R22 supports two alarm synchronization modes: manual synchronization and
automatic synchronization.
à In the manual synchronization mode, the alarm synchronization is initiated by a
user.
à In the automatic synchronization mode, the alarm synchronization is initiated by
the system.
4-3

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
The system supports the customization of various alarm rules for managing
and processing received alarms, such as alarm storage, alarm filtering, alarm
reclassification, and alarm correlation.
For example, by creating an alarm filtering rule, you can filter less important alarms
and reduce the count of alarms displayed on the client screen. In this way, you can
easily find critical alarms and handle them first.
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 Modification of Alarm Settings
This function allows you to define the alarm management mode, reset the indication
colors of alarms, and set the thresholds of environment parameters, for example,
temperature, humidity, and smog existence.
l Alarm Query and Statistic
The alarm query and statistic function enables you to query alarms stored in the
database and get a statistic report of these alarms. By analyzing the alarm report,
you can find problems in the network and improve the network performance by
removing those problems. For example, you can query history alarms, active alarms
and notifications.
In addition, the system can count alarms according to their types and severity levels,
and indicate the distribution of different alarms by displaying the statistic information
in various chart forms.
4.3 Performance Management

The purpose of performance management is to improve the network performance and
efficiency and provide a basis as well as suggestions for proper planning of network
resources. The performance management module of the U31 R22 system can collect
the performance data of network elements in the network. By observing and analyzing
the collected performance data, you can know the running status of equipment in the
network, evaluate the efficiency of equipment and the network, and monitor the quality of
service in the network.
4-4

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 after setting the query
conditions, for example, NE type, time period and performance object. The query
result is displayed in a list. You can print the query result or save it as a file.
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
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.
In addition, you can create a report task by specifying the report type, template, object,
time, and file name. When the preset is up, the system generates the customized
report according to the task. The customized task is stored in the database, which
can be queried, modified and deleted. After the report is generated by the system,
you can view the report and save it as an *.xls file.
The system can send the periodically-generated report to a user in the specified format
through E-mail as required.
4.4 Security Management

The security management module of the U31 R22 system provides security management
functions to ensure that only authorized users can access and manage network resources.
For better understanding of security management, the following explains some basic
concepts related to security management, including role, role set, department, and user.
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.
4-5

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. A newly-created user must belong to a
department.
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.
Figure 4-1 Relation Model of Security Management
The following explains the relation model of security management.
l A user is administered by a department.

l The management permission of a user depends on the role set assigned to the user.
4-6

l A role set includes one role or a set of roles. Correspondingly, the management
permission of a role set is the collection of management permissions of all roles in
the role set.
l The management permission of a role depends on the operation permission and
manageable resources specified for the role.
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.
l Login User Management
l Forcible Removal of Users
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.
l IP Address Setting of Super Administrator
You can set the IP address of the super administrator to ensure the security of the
super administrator account. 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
4-7

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.
The CTN NE supports the following configuration:
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 Optical power view
l Real-time traffic monitoring
The SDH NE supports the following configuration:
l Gateway NE configuration
l Clock configuration
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 Optical power view
4-8

l Data synchronization
The OTN NE supports the following configuration:
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
The IP NE supports the following configuration:
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
l Alarm configuration
l Performance configuration
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.
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. If the upgrade fails, the system enables the equipment to roll its software
back to the previous one.
The E300, T31, and U31 R22 can be upgraded to the current version. The client software
can be automatically downloaded from the server.
4-9

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 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 U31 R22 system provides powerful database management functions to ensure the
security of the system database, including the backup, restoration, and monitoring of
database.
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

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

4-12

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

You can select the network management deployment model based on the network scale
and deployment requirements. For the deployment models supported by the U31 R22,
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 deployment is simple and cost effective.
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

In the dual-computer cluster system deployment, the master and slave servers compose
a system with high availability. The data of the master and slave servers is synchronized
in real time. When the master server is faulty, the data can be switched to the slave one
automatically, which can monitor the network and ensure a proper operation of the system.
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) .
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.
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.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. The
faults of the U31 R22 will not affect the networks composed of the managed NEs and the
carried services.
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 most common networking mode used by centralized
network management systems. It is a simple networking mode, in which the server, clients
and NEs are all located in the same Local Area Network (LAN) and connected with each
other through Ethernet. In this networking mode, the server connects to the managed NEs
through LAN.
5-4

The following describes the topology of this networking mode and the required devices for
the local networking.
l Topology
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 U31 R22 system supports various non-cascade remote networking modes, in which
the clients are located remotely from the server. Different remote networking modes
have the same network topology and follow the same networking principle. Specific
transmission equipment is used to connect the system to a Wide Area Network (WAN).
The server and the client are located in different LANs with corresponding routers and
hubs.
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.
l Remote Networking Based on DDN Leased Line
The stable and reliable DDN provides a high transmission rate from 64kbps to 2Mbps.
In this remote networking mode, routers and baseband MODEMs are used. At the
server, a hub is connected to a router and the router is connected to the leased line of
5-5

the DDN through a baseband MODEM. The remote client is connected to the leased
line in the same way through its Ethernet interface.
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-6

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.
Local NEs/clients and remote NEs/clients coexist in this networking mode. For the topology
of the integrated networking over DDN, see Figure 5-7.
5-7

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

Chapter 6
Product Interfaces
Table of Contents
Logical Interfaces .......................................................................................................6-1
Physical Interfaces .....................................................................................................6-2
6.1 Logical 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.
The northbound interfaces have comply with special interface standards that specify the
information model, interface technical modes, and interface functions for the connection
between the EMS/NMS and the upper integrated NMS/OSS. The northbound interfaces
are the basis for centralized network management and integrated management and
maintenance.
For the position of northbound interfaces in the network, refer to the section of U31 R22
Position.
U31 R22 provides the following northbound interfaces:
l CORBA northbound interface
CORBA is a standard for the distributed computer environment and the computer
network interconnection. U31 R22 can interact with the upper integrated NMS/OSS
through the CORBA interface that complies with the TMF standards and protocols.
6-1

The CORBA interface of U31 R22 supports the functions such as configuration
management, alarm management, performance management, and property
management.
l SNMP northbound alarm interface
U31 R22 provides the SNMP northbound alarm interface, which sends the alarm
message to the upper integrated NMS/OSS.
l FILE/FTP northbound interface
The FILE/FTP northbound interface obtains the information of all the NEs in the
network, the network topology, history alarms, and history performances. Then, it
composes files based on the above information and sends the files to the FTP server.
The upper integrated NMS/OSS can get these files from the FTP server.
l XML northbound interface
Through the U31 R22 XML northbound interface, the upper integrated NMS/OSS can
perform uniform management of all the ZTE transmission equipment.
l TL1 northbound
The upper-layer network management systems/OSS can perform the configuration
management and resource management for IP equipment via the U31 R22 TL1
northbound interfaces.
6.2 Physical Interfaces

For the physical interfaces provided by the U31 R22 system, refer to Table 6-1.
Table 6-1 Physical Interfaces
Interface Type Description
10M/100M adaptive Ethernet interface Used to connect 10M/100M Ethernet
GE interface Used to connect a Gigabit Ethernet
X.25 interface Used to connect a packet switched network
6-2

Chapter 7
Technical Specifications
Table of Contents
Performance Specifications ........................................................................................7-1
Reliability Specifications .............................................................................................7-2
Computer Ports Occupied by the System ..................................................................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.3 Computer Ports Occupied by the System

Server and Client
For the computer ports occupied by the U31 R22 server and client, refer to Table 7-3.
Table 7-3 Computer Ports Occupied by the U31 R22 Server and Client
Nu- Source Destination Direction Protocol Description

m- Port Port
ber
1 Random 20800-20999 Client -> TCP File Transfer Protocol (FTP) data
Server transmission port
2 Random 21100 Client -> TCP Java naming service port for the main
Server process
7-2

Chapter 7 Technical Specifications

m- Port Port
ber
3 Random 21101 Client -> TCP Naming service port for the Cluster
Server process, for Java Message Service
(JMS)
4 Random 21102 Client -> TCP Remote Method Invocation (RMI)

Server communication server port for the
Cluster message server
5 Random 21103 Client -> TCP Remote invocation adaptation port for
Server the Java naming service for the main
process
6 Random 21104 Client -> TCP Java naming service invocation port
Server for the main process
7 Random 21105 Client -> TCP Enterprise Message Bus (EMB) port
9 Random 21109 Client -> TCP Heartbeat detection port for the F
Server interface
10 Random 21110 Client -> TCP Java naming service transaction

Server management for the main process
11 Random 21111 Client -> TCP FTP server control port

Server
12 Random 21112 Client -> TCP Remote invocation port for Java
Server components of the main process
Server for the Cluster process
14 Random 21114 Client -> TCP JMS port for the cluster process
Server
15 Random 21118 Client -> TCP Bandwidth detection port for the client
Server server
16 Random 21128 Client -> TCP Secure File Transfer Protocol (SFTP)
Server server port
17 Random 21133 Client -> TCP Port used by the upgrading tool for
Server automatic client upgrade
18 Random 21140 Client -> TCP Secure Shell (SSH) forwarding port
Server
7-3


m- Port Port
ber
19 Random 21199 Client -> TCP SSH forwarding port for Man Machine
Server Language (MML) commands
20 Random 21 Client -> TCP Port for the FTP service of the NMS
Server server
21 Random 21160 Client -> TCP ZXTIM400 polling tool port

Server
22 Random 21162 Client -> TCP EMB port

Server

Server

Server

Server

Server

Server

Server

Server
30 Random 21138 Client -> TCP EMB port of the TOPO process
Server
31 Random 21188 Client -> TCP RMI port used by the Telnet tool
Server
32 Random 69 Client -> TCP Port used by the TFTP protocol

Server
33 Random 20201 – Client -> TCP Port used for IP management process
20220 Server debugging
34 Random 20141 – Client -> TCP Port used for wireline management
20160 Server process debugging
35 Random 20001 – Client -> TCP Port used for UEP management
20020 Server process debugging
7-4

Server and OSS

For the computer ports occupied by the U31 R22 server and Operation Support System
(OSS), refer to Table 7-4.
Table 7-4 Computer Ports Occupied by the U31 R22 Server and OSS

m- Port Port
ber
1 Random 20800-20999 OSS -> TCP FTP data transmission port

Server
2 Random 21111 OSS -> TCP FTP server port

Server
3 Random 21115 OSS -> TCP Common Object Request Broker

Server Architecture (CORBA) naming service
port
5 Random 21126 OSS -> TCP CORBA notification service port

Server
6 Random 21128 OSS -> TCP SFTP server port

Server
7 Random 21161 OSS -> UDP Non-trap message port for Simple
Server Network Management Protocol
(SNMP) v2C
8 Random 21164 OSS -> UDP Non-trap message port for SNMP v3
Server
9 Random 21165 OSS -> UDP Non-trap message port for SNMP v1
Server
10 Random 161 OSS -> UDP Port used for receiving requests when
Server the U31 R22 operates as the SNMP
agent.
11 Random 21175 OSS -> TCP The port used by the U31 R22 for
Server communicating with OSS when the
fixed CORBA service port is used
12 Random 21176 OSS -> TCP North Bound Interface (NBI) naming
Server service port
13 Random 21177 OSS -> TCP NBI notification service port

Server
14 Random 21178 OSS -> UDP NBI SNMP agent port

Server
15 Random 162 OSS -> UDP Default port for the SNMP Trap
Server message
7-5

Server and Equipment

For the computer ports occupied by the U31 R22 server and the equipment, refer to Table
7-5.
Table 7-5 Computer Ports Occupied by the U31 R22 Server and Equipment

m- Port Port
ber
1 Random 20 Server -> TCP FTP data transmission port

NE
2 Random 21 Server -> TCP FTP server control port

NE
3 Random 9023 Server -> TCP Telnet port used by the OTN
NE equipment
4 Random 1025-1030 Server -> TCP Qx communication port

NE
5 Random 9998 Server -> TCP Qx communication i port

NE
6 Random 9999 Server -> TCP Qx communication port

NE
7 Random 12288-13311 Server -> TCP Enables the communication port of

NE the gateway NE
8 Random 16384-17407 Server -> TCP Enables the FTP control port of the
NE gateway NE
9 Random 20480-21503 Server -> TCP Enables the Telnet port of the gateway
NE NE
10 57344- Random NE -> TCP Enables the FTP data transmission

57407 Server port of the gateway NE
11 Random 20800-20999 NE -> TCP FTP data transmission port

Server
12 Random 21111 NE -> TCP FTP server control port

Server
13 Random 23 Server -> TELNET TELNET port for the CTN equipment
NE
14 Random 22 Server -> TCP SSH protocol port

NE
15 Random 161 Server -> TCP Port occupied for the NMS to acquire
NE SNMP messages
7-6


m- Port Port
ber
16 23742 – 23740 NE -> TCP Port opened in the distributed

23753 Server performance collection mode.
17 Random 9890 NE -> TCP Port used for the NMS to enable
Server the monitoring device to send zero
deployment service TCP messages.
18 Random 9835 – 9840 NE -> TCP TL1 northbound port

Server
19 Random 514 NE -> TCP SYSLOG receiving port

Server
7-7

7-8

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 ℃~+35 ℃
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
AC
- Access Circuit
APC
- Automatic Power Control
APO
- Automatic Power Optimization
ASON
- Automatically Switched Optical Network
ATM
- Asynchronous Transfer Mode
BRAS
- Broadband Remote Access Server
CAPEX
- Capital Expenditure
CHAP
- Challenge Handshake Authentication Protocol
CORBA
- Common Object Request Broker Architecture
CTN
- Converged packet Transport Network
DCN
- Data Communications Network
DDN
- Digital Data Network
ECC
- Embedded Control Channel
EMB
- Enterprise Message Bus
EML
- Element Management Layer
EMS
- Element Management System

FE
- Fast Ethernet
FTP
- File Transfer Protocol
GE
- Gigabit Ethernet
GRE
- General Routing Encapsulation
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
JMS
- Java Message Service
KPI
- Key Performance Indicator
L2
- Layer 2
L3
- Layer 3
LAN
- Local Area Network
LCS
- LoCation Services
LCT
- Local Craft Terminal
LDAP
- Lightweight Directory Access Protocol
MML
- Man Machine Language
MODEM
- Modulator-Demodulator
II

Glossary
MPLS
- Multiprotocol Label Switching
MPLS-TP
- Multi-Protocol Label Switching Transport Profile
MTBF
- Mean Time Between Failures
NBI
- NorthBound Interface
NCP
- Network element Control Processing board
NE
- Network Element
NML
- Network Management Layer
NMS
- Network Management System
OAC
- Optical Access
OAM
- Operation, Administration and Maintenance
OCH
- Optical Channel
OMG
- Open Mobile Gateway
OMS
- Optical Multiplex Section
OSI
- Open System Interconnection
OSS
- Operation Support System
OTN
- Optical Transport Network
PAP
- Password Authentication Protocol
PW
- Pseudo Wire
RMI
- Remote Method Invocation
III

RS
- Regenerator Section
SDH
- Synchronous Digital Hierarchy
SFTP
- Secure File Transfer Protocol
SNMP
- Simple Network Management Protocol
SSH
- Secure Shell
SSL
- Secure Sockets Layer
T-MPLS
- Transport Multi-Protocol Label Switching
TCP
- Transmission Control Protocol
TDM
- Time Division Multiplexing
TLS
- TransportLayer Security
TMN
- Telecommunications Management Network
TP
- Transport Protocol
UDP
- User Datagram Protocol
UPS
- Uninterruptible Power Supply
UTC
- Universal Time Coordinated
VLAN
- Virtual Local Area Network
VPLS
- Virtual Private LAN Service
VPN
- Virtual Private Network
VPWS
- Virtual Private Wire Service
IV

Glossary
WAN
- Wide Area Network
WDM
- Wavelength Division Multiplexing
WEB
- Web
XML
- eXtensible Markup Language

12 NetNumen U31 R22 (V12.13.10) Product Description

Uploaded by

Copyright:

Available Formats

You might also like

12 NetNumen U31 R22 (V12.13.10) Product Description

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

12 NetNumen U31 R22 (V12.13.10) Product Description

Uploaded by

Copyright:

Available Formats

NetNumen™ U31 R22

Unified Network Management System

Product Version: V12.13.10

Revision No. Revision Data Revision Reason

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-20121127091048-001

Publishing Date: 2012-12-30 (R3.0)

SJ-20121127091048-001|2012-12-30 (R3.0) ZTE Proprietary and Confidential

What Is in This Manual

1, System Overview Describes the system overview, position, features, managed

3, Product Architecture Describes the hardware architecture and software architecture

4, Product Functions Describes the functions of the U31 R22.

7, Technical Specifications Describes the performance specifications and interface

8, Environmental Requirements Describes the power specifications and environmental

SJ-20121127091048-001|2012-12-30 (R3.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 certain topic.

SJ-20121127091048-001|2012-12-30 (R3.0) ZTE Proprietary and Confidential

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

Chapter 3 Product Architecture ................................................................ 3-1

Chapter 4 Product Functions .................................................................... 4-1

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

Chapter 6 Product Interfaces .................................................................... 6-1

SJ-20121127091048-001|2012-12-30 (R3.0) ZTE Proprietary and Confidential

Chapter 7 Technical Specifications .......................................................... 7-1

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

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

SJ-20121127091048-001|2012-12-30 (R3.0) ZTE Proprietary and Confidential

1.1 Location of the Product on a Bearer Network

SJ-20121127091048-001|2012-12-30 (R3.0) ZTE Proprietary and Confidential

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

1.2 Product Features

Advanced Architecture and Scalability

SJ-20121127091048-001|2012-12-30 (R3.0) ZTE Proprietary and Confidential

Standard Northbound Interface

Service Deployment Advantages

SJ-20121127091048-001|2012-12-30 (R3.0) ZTE Proprietary and Confidential

Advantages of CTN equipment service deployment

SJ-20121127091048-001|2012-12-30 (R3.0) ZTE Proprietary and Confidential

l Offline pre-configuration capability

Value-Added Function Advantages

SJ-20121127091048-001|2012-12-30 (R3.0) ZTE Proprietary and Confidential

l Clear OTN signal flow

l OTN APO subsystem

SJ-20121127091048-001|2012-12-30 (R3.0) ZTE Proprietary and Confidential

l Preventive maintenance design

Advantages of IP equipment value-added functions

SJ-20121127091048-001|2012-12-30 (R3.0) ZTE Proprietary and Confidential

templates. The resource performance data in the IP network can be collected,