SJ-20110823134613-002-NetNumen U31 R18 (V12.10.040) Product Description

NetNumen U31 R18
Unified Element Management System
Product Description
Version: 12.10.040
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 2011 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 Date
Revision Reason
R1.1
2011-1216
Updates Section 4.1.1, Server Hardware Configuration
Updates Section 6.2, Fault Alarm Management
Updates Section 6.3, Performance Management
R1.0
2011-0916
Serial Number: SJ-20110823134613-002

Publishing Date: 2011-12-16(R1.1)
First Edition
Contents
About This Manual ......................................................................................... I
Chapter 1 System Overview ...................................................................... 1-1
1.1 Overview ........................................................................................................... 1-1
1.2 Functions........................................................................................................... 1-2
1.3 Standards Followed............................................................................................ 1-2
Chapter 2 System Features ....................................................................... 2-1

2.1 Conformity to Standards ..................................................................................... 2-1
2.2 Integrated Network Management......................................................................... 2-1
2.3 System Expansion.............................................................................................. 2-1
2.4 System Openness .............................................................................................. 2-1
2.5 System Reliability............................................................................................... 2-2
2.6 System Operation Security ................................................................................. 2-2
2.7 Ease of Use ....................................................................................................... 2-2
Chapter 3 System Structure ...................................................................... 3-1

3.1 Hardware Structure ............................................................................................ 3-1
3.2 Software Structure.............................................................................................. 3-3
Chapter 4 Configuration Requirements ................................................... 4-1

4.1 Server Configuration Requirements ..................................................................... 4-1
4.1.1 Server Hardware Configuration ................................................................. 4-1
4.1.2 Server Software Configuration .................................................................. 4-2
4.2 Client Configuration Requirements ...................................................................... 4-3
4.2.1 Client Hardware Configuration .................................................................. 4-3
4.2.2 Client Software Configuration.................................................................... 4-3
Chapter 5 System Principles ..................................................................... 5-1

5.1 Working Principle ............................................................................................... 5-1
5.2 Remote Client Principle ...................................................................................... 5-2
5.3 NMS Hierarchy Model......................................................................................... 5-2
Chapter 6 Product Functions .................................................................... 6-1

6.1 Topology Management ....................................................................................... 6-1
6.2 Fault Alarm Management.................................................................................... 6-3
6.3 Performance Management.................................................................................. 6-7
6.4 Security Management......................................................................................... 6-8
6.5 Log Management ............................................................................................... 6-9

6.6 System Backup ................................................................................................ 6-10
6.7 System Monitoring............................................................................................ 6-10
6.8 Task Management .............................................................................................6-11
6.9 Command Line Terminal ................................................................................... 6-12
6.10 Radio Configuration Application....................................................................... 6-12
6.11 Northbound Interface ...................................................................................... 6-13
Chapter 7 Interfaces and Protocols .......................................................... 7-1

7.1 Internal Interfaces .............................................................................................. 7-1
7.2 Southbound Interfaces........................................................................................ 7-1
7.3 Northbound Interfaces ........................................................................................ 7-1
7.3.1 CORBA Northbound Interfaces ................................................................. 7-2
7.3.2 FTP Northbound Interface......................................................................... 7-4
7.3.3 SNMP Northbound Interface ..................................................................... 7-5
7.3.4 SOCKET Northbound Interface ................................................................. 7-7
Chapter 8 Networking Modes .................................................................... 8-1

8.1 Local Networking Mode ...................................................................................... 8-1
8.2 Remote Networking Mode................................................................................... 8-2
8.3 Remote Client Networking Mode ......................................................................... 8-3
Chapter 9 Environment Requirements ..................................................... 9-1

9.1 Grounding Requirements .................................................................................... 9-1
9.2 Temperature and Humidity Requirements ............................................................ 9-2
9.3 Cleanness Requirements.................................................................................... 9-3
9.4 Air Conditioning and Ventilation Requirements ..................................................... 9-3
9.5 Anti-EMI Requirements....................................................................................... 9-3
9.6 Lightning Protection Requirements ...................................................................... 9-4
9.7 Anti-Static Requirements .................................................................................... 9-5
9.8 Quakeproof Requirements .................................................................................. 9-5
9.9 Illumination ........................................................................................................ 9-5
9.10 Fire Prevention Requirements ........................................................................... 9-6
9.11 Atmospheric Pressure Requirement................................................................... 9-6
9.12 Air Pollution Limitation ...................................................................................... 9-6
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
II
About This Manual

The NetNumenTM U31 R18 Unified Element Management System (NetNumen U31 or
EMS) is a special network element management system that manages network elements
in radio access systems. By using NetNumen U31, users can configure and maintain
individual network elements, and manage radio access networks in a unified manner.
NetNumen U31 provides the following management functions:
l
l
l
l
l
Configuration management
Fault management
Performance management
Topology management
Security management
As an object-oriented system designed on the J2EE platform, NetNumen U31 provides

unified standard interfaces to external devices.
Purpose
This manual describes the functions, features, working principles, and networking of the
NetNumen U31 Unified Element Management System.
Intended Audience
l
l
Maintenance engineers
Debugging engineers
What Is in This Manual

Section
Summary
Chapter 1, System Overview
Describes the background, functions, and standards followed in the

NetNumen U31 system.
Chapter 2, System Features
Describes the features of the NetNumen U31 system.
Chapter 3, System Structure
Describes the hardware and software structure of the NetNumen

U31 system.
Chapter 4, Configuration
Describes the configuration requirements for the server and client
Requirements
of NetNumen U31.
Chapter 5, System Principles
Describes the working principle, remote client principal, and

hierarchical model of the NetNumen U31 system.
Chapter 6, Product Functions
Describes the functions of each module in the NetNumen U31

system, including topology management, fault management, and
performance management.
Section
Summary
Chapter 7, Interfaces and
Describes the internal interfaces and external interfaces provided by
Protocols
the NetNumen U31 system and related protocols.
Chapter 8, Networking
Describes the networking modes of the NetNumen U31 system,
Modes
including local networking, remote networking, and remote client

networking.
Chapter 9, Environment
Describes the working environment requirements of the NetNumen
Requirements
U31 system.
II
Chapter 1
System Overview
Table of Contents
Overview ....................................................................................................................1-1
Functions ...................................................................................................................1-2
Standards Followed....................................................................................................1-2
1.1 Overview
According to the network management definition specified in Telecommunications
Management Network (TMN), NetNumen U31 is located in the network element
management layer, as shown in Figure 1-1.
Figure 1-1 Network Management Model
The NetNumen U31 network element management system is located between the network
element layer and the network management layer. It belongs to the network element
management layer.
The NetNumen U31 system manages and controls various connected radio network
systems, implementing centralized management of the radio network systems, including:
l
l
Centralized topology management

Centralized log management
1-1
SJ-20110823134613-002|2011-12-16(R1.1)
ZTE Proprietary and Confidential
NetNumen U31 R18 Product Description
l
l
l
l
Centralized
Centralized
Centralized
Centralized
fault management
performance management
command line tool
maintenance tool
The NetNumen U31 system provides interfaces for the network management layer,
reporting information of the managed elements, including the alarm data, performance
data, and configuration data.
The NetNumen U31 system improves centralized management of the telecommunication
enterprises.
1.2 Functions
The NetNumen U31 system is a centralized management system of the mobile radio
products of ZTE Corporation. Through NetNumen U31, users can manage all the radio
devices over the entire network in a centralized manner. It also provides the standard
northbound interfaces to the upper-layer Network Management System (NMS).
The NetNumen U31 system manages the lower-level network element systems in a
centralized manner, and provides unified interfaces to the upper-layer applications.
The managed elements report the topology data, alarm data, and performance data
through their interfaces. The NetNumen U31 system implements centralized information
displaying and management through centralized modeling and conversion.
The NetNumen U31 system provides the following network management functions:
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
Configuration management
Topology management
Fault management
Performance management
Security management
System management
Task management
Command line tool
Graphical User Interface (GUI)
Maintenance tool
Role-based and domain-based management
Backup and restoration
Three-layered networking
Northbound interface
Network Time Protocol (NTP) function
1.3 Standards Followed

NetNumen U31 complies with the following standards.
1-2
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 1 System Overview
ITU-T
l
l
l
l
l
l
l
l
l
l
l
l
l
l
ITU-T M.3000, Overview of TMN recommendations

ITU-T M.3010, Principles for a Telecommunications management network
ITU-T M.3016, TMN security overview
ITU-T M.3020, TMN Interface Specification Methodology
ITU-T M.3100, Generic Network Information Model
ITU-T M.3101, Managed Object Conformance Statements for the Generic Network
Information Model
ITU-T M.3200, TMN management services and telecommunications managed areas:
overview
ITU-T M.3300, TMN F interface requirements
ITU-T M.3400, TMN Management Function
ITU-T Temporary Document 69 (IP Experts): Revised draft document on IP access
network architecture
ITU-T X.701-X.709, Systems Management framework and architecture
ITU-T X.710-X.719, Management Communication Service and Protocol
ITU-T X.720-X.729, Structure of Management Information
ITU-T X.730-X.799, Management functions
RFC
l
l
l
l
l
l
l
l
l
l
l
l
l
RFC1157, Simple Network Management Protocol

RFC1213, Management Information Base for Network Management of TCP/IP based
internets: MIB-II
RFC1901, Introduction to Community-based SNMPv2
RFC1902, Structure of Management Information for Version 2 of the Simple Network
Management Protocol (SNMPv2)
RFC1903, Textual Conventions for Version 2 of the Simple Network Management
Protocol (SNMPv2)
RFC1905, Protocol Operations for Version 2 of the Simple Network Management
Protocol (SNMPv2)
RFC2037, Entity MIB using SMIv2
RFC2233, The Interface Group MIB using SMIv2
RFC1558, A String Representation of LDAP Search Filters
RFC1777, Lightweight Directory Access Protocol
RFC1778, The String Representation of Standard Attribute Syntaxes
RFC1959, An LDAP URL Format
RFC2251, Lightweight Directory Access Protocol (v3)
TMF
l
l
l
l
GB901, A Service management Business Process Model

GB921, Enhanced Telecom Operations Map
GB909, Generic Requirements for Telecommunications Management Building Blocks
GB908, Network Management Detailed Operations Map
1-3
SJ-20110823134613-002|2011-12-16(R1.1)
l
l
l
l
l
l
l
GB914, System Integration Map

GB917, SLA Management Handbook V1.5
NMF038, Bandwidth Management Ensemble V1.0
TMF508, Connection and Service Management Information Model Business
Agreement
TMF801, Plug and Play Service Fulfillment Phase 2 Validation Specification V1.0
TMF605, Connection and Service Management Information Model
NMF037, Sub-System Alarm Surveillance Ensemble V1.0
OMG
l
Interworking Between CORBA and TMN System Specification V1.0
Ministry of Information Industry and China Telecom

l
l
YD/T 852-1996 Telecom Management Network (TMN) General Design Principle

YD/T 871-1996 Telecom Management Network (TMN) Universal Information Model
1-4
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 2
System Features
Table of Contents
Conformity to Standards.............................................................................................2-1
Integrated Network Management................................................................................2-1
System Expansion......................................................................................................2-1
System Openness ......................................................................................................2-1
System Reliability .......................................................................................................2-2
System Operation Security .........................................................................................2-2
Ease of Use ...............................................................................................................2-2
2.1 Conformity to Standards

NetNumen U31 strictly complies with the TMN series proposals established by ITU-T and
the series NM protocols of RFC.
2.2 Integrated Network Management

The NetNumen U31 system manages the radio network element devices in the following
systems:
l
l
l
l
l
l
l
ZTE UMTS
GSM
TD-SCDMA
CDMA
LTE (including LTE-FDD and LTE-TDD)
WiMAX
Microwave
2.3 System Expansion

NetNumen U31 is designed with a modularized structure, which ensures a strong capability
of expansion of system devices and service management functions.
2.4 System Openness

The following technologies ensures the openness of NetNumen U31:
2-1
SJ-20110823134613-002|2011-12-16(R1.1)
NetNumen U31 supports standard CORBA, SNMP, and FTP/SFTP northbound

interfaces. The relationship between NetNumen U31 and the service system is both
data sharing and service sharing.
NetNumen U31 is implemented through JAVA. Thus it can run on Windows and UNIX
platforms, meeting users' demands for managing networks of different scales.
2.5 System Reliability

The reliability of NetNumen U31 is embodied in the following aspects:
l
l
l
l
The NetNumen U31 server has redundant network ports, dual power supplies, and
hard disks that can be mirrored, which improves hardware reliability.
Local High Availability (HA) and remote disaster recovery capability ensure that the
services can be switched to the standby server when the active server is down.
NetNumen U31 provides a complete system management capability, which helps
monitor the system running condition.
Disk mirroring and data backup ensure the data saving security.
Disk mirroring: In one host, all data modifications on the active disk are
synchronously backed up to the standby disk.
Data backup: Through the network management system, users can back up or
dump the specified data to the specified peripheral storage devices, such as disks
and magnetic tapes. Users can restore the system with the data in the peripheral
storage devices as required. It provides various choices for data saving and
backup.
NetNumen U31 supports in-band management and out-of-band management. In the

out-of-band management mode, the network management data and the service data
are transmitted in different channels. In the in-band management mode, the two data
are transmitted in the same channel. For applications with high reliability requirement,
it is recommended to use the out-of-band management mode.
2.6 System Operation Security

The operation security of the NetNumen U31 system is ensured by the following two
aspects:
l
Complete access rights control

The system provides a complete access rights control function. Users can access
the controlled network elements, in other words, the system supports operations on
limited NEs in limited granularity.
Complete log records
2.7 Ease of Use

NetNumen U31 provides a friendly man-machine GUI.
2-2
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 3
System Structure
Table of Contents
Hardware Structure ....................................................................................................3-1
Software Structure......................................................................................................3-3
3.1 Hardware Structure

The hardware of NetNumen U31 consists of two parts: server cluster and client cluster.
According to server functions, the server cluster is divided into application servers and
database servers. These servers can share one workstation or use different workstations,
and the default setting is the former case.
According to the actual requirement, there are three types of server configuration:
single-server configuration, local HA configuration, and remote disaster recovery
configuration. By default, the single-server configuration is used.
Single-Server System
Figure 3-1 shows the hardware structure of a single-server NetNumen U31 system.
Figure 3-1 Single-Server System Hardware Structure
Local HA System
The two servers are located in the same LAN and share the disk array.
3-1
SJ-20110823134613-002|2011-12-16(R1.1)
The two servers are managed through the HA software. One server is in the service
running status, saving the real-time data to the disk array. The other server is in the standby
status, not providing services to external devices. The two servers are connected by the
heartbeat cable. When the active server is down, the applications are switched to the
standby server, as shown in Figure 3-2
Figure 3-2 Hardware Structure of Local HA System
Remote Disaster Recovery System

The two servers are located in different LANs and each uses an independent disk array.
The two servers are managed through software. One server is in the service running
status, saving the real-time data to the disk array. The other server is in the standby
status, not providing services to external devices. A dedicated network is used between
the active server and the standby server to implement data synchronization in real time.
The active server data is synchronized to the standby server through software. When the
active server is down, the applications are switched to the standby server, as shown in
Figure 3-3.
3-2
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 3 System Structure
Figure 3-3 Hardware Structure of Remote Disaster Recovery System
3.2 Software Structure

The NetNumen U31 system software includes:
l
l
server software
client software
NetNumen U31 uses the client/server architecture, and TCP/IP is used in communication
between different parts.
The NetNumen U31 software system consists of the following software modules:
l
l
l
l
l
l
l
l
l
l
l
l
Topology management module

Fault management module
Performance management module
Command line terminal module
Task management module
System backup module
System monitoring module
NE management module
Security management module
Log management module
Radio configuration application
Northbound interface module
3-3
SJ-20110823134613-002|2011-12-16(R1.1)
This page intentionally left blank.
3-4
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 4
Configuration Requirements
Table of Contents
Server Configuration Requirements............................................................................4-1
Client Configuration Requirements .............................................................................4-3
4.1 Server Configuration Requirements

4.1.1 Server Hardware Configuration
The NetNumen U31 server can use the SUN server platform or the IBM server platform.
Table 4-1 and Table 4-2 list the recommended hardware configuration.
Table 4-1 Server Hardware Configuration (SUN)
Configuration Item
Model1
Model2
Server
SUN M4000
SUN M4000
(CPU: 2*4 core
(CPU: 4*4 core
Memory: 32G
Memory: 64G
HD: 2*146G SAS
HD: 2*146G SAS
Dual port HBA card)
Dual port HBA card)
ST6180(8*300G FC 15K)
ST6180(16*300G FC 15K)
or
or
EMC CX4-120C(8*300G FC
EMC CX4-120C(15*300G FC
15K)
15K)
SUN T5220
SUN T5220
(CPU: 1*8 core
(CPU: 1*8 core
Memory: 16G
Memory: 16G
HD: 2*146G
HD: 2*146G
Dual port HBA card)
Dual port HBA card)
SL 24 (12*400G)
SL 24 (12*400G)
DiskArray
Backup server
TAPE
4-1
SJ-20110823134613-002|2011-12-16(R1.1)
Table 4-2 Server Hardware Configuration (IBM)

Configuration Item
Model1
Model2
Server
IBM P740
IBM P740
(CPU: 2*2 core
(CPU: 4*2 core
Memory: 32G
Memory: 64G
HD: 2*146G SAS
HD: 2*146G SAS
Dual port HBA card)
Dual port HBA card)
DiskArray
NAS N6210(8*300G FC 15K)
NAS N6210(14*300G FC 15K)
Backup server
IBM P520
IBM P520
TAPE
(CPU: 2*2 core
(CPU: 2*2 core
Memory: 16G
Memory: 16G
HD: 2*146G
HD: 2*146G
Dual port HBA card)
Dual port HBA card)
TS3310 (12*400G)
TS3310 (12*400G)
4.1.2 Server Software Configuration

The NetNumen U31 server can use the SUN server platform or the IBM server platform.
Table 4-3 and Table 4-4 list the recommended software configuration.
Table 4-3 Server Software Configuration (SUN)
Software Type
Software Name and Version
Network management software
EMS server version NetNumen U31 R18 (V12.11.40)
Operating system
Solaris 10 U9 sparc
Database
Oracle 11.2.0.2 EE 64bit for solaris sparc
HA software
VCS, VVR 5.1
Table 4-4 Server Software Configuration (IBM)

Software
Software Name and Version
Network management software
EMS server version NetNumen U31 R18 (V12.11.40)
Operating system
AIX 6103
Database
Oracle 11.2.0.2 EE 64bit for aix
HA software
PowerHA+SnapMirror 6105
4-2
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 4 Configuration Requirements
4.2 Client Configuration Requirements

4.2.1 Client Hardware Configuration
The NetNumen U31 client uses the PC work station. Table 4-5 lists the recommended
configuration.
Table 4-5 Client Hardware Configuration
Managed Object
Configuration
CPU
PentiumIV 3.0 GHz or higher
Memory
2 GB
Built-in hard disk
500 GB
Disk array
None
4.2.2 Client Software Configuration

Table 4-6 lists the software configuration on the client.
Table 4-6 Client Software Configuration
Managed Object
Configuration
Operating system
Windows XP
Windows 7
Browser
Internet Explorer 7.0
Document viewer
Microsoft Office 2003/2007
Antivirus software
McafeeVirusScan 8.5, Norton, or Trend
4-3
SJ-20110823134613-002|2011-12-16(R1.1)
4-4
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 5
System Principles
Table of Contents
Working Principle .......................................................................................................5-1
Remote Client Principle ..............................................................................................5-2
NMS Hierarchy Model ................................................................................................5-2
5.1 Working Principle

The relation between NetNumen U31 and the systems at different levels is shown in Figure
5-1.
Figure 5-1 Working Principle of NetNumen U31
The relation between NetNumen U31 and the upper-layer NMS and the lower-layer OMMs
are described as follows:
l
l
NetNumen U31 provides the basic data of the devices and the device management
services for the upper-layer OSS or integrated NMS.
Operation analysis
NetNumen U31 provides the original statistic analysis data for the operation analysis
system.
Resource management
NetNumen U31 provides centralized device configuration information for the resource
management system.
Electronic operation and maintenance

NetNumen U31 provides the network fault and alarm information for the operation and
maintenance system.
5-1
SJ-20110823134613-002|2011-12-16(R1.1)
NetNumen U31 implements centralized monitoring, management, and maintenance

for the devices of the entire network through the local OMM.
Through the interface between NetNumen U31 and the managed NEs, the OMMs of the
managed NEs report topology, fault, performance and report data to NetNumen U31.
Through centralized modeling and conversion, NetNumen U31 presents and manages
the data in a centralized manner.
5.2 Remote Client Principle

Remote client, also called Embedded Remote Terminal (ERT), is a remote client
established in areas outside the place where the NetNumen U31 server is located. It
displays the data of the NetNumen U31 system in a distant place, as shown in Figure 5-2.
Figure 5-2 Remote Client Position
The following describes the remote client principle:

l
l
l
l
The NetNumen U31 server collects the NE data through each NE and process the
data.
The NetNumen U31 client displays the data that is collected and handled by the
NetNumen U31 server through GUI.
Through the TCP/IP protocol, the remote NetNumen U31 client selectively presents
collected network management information to different areas.
To ensure the network security, user rights can be customized for different areas
through the security management functions of NetNumen U31.
5.3 NMS Hierarchy Model

Figure 5-3 shows the hierarchy of the NetNumen U31 system.
5-2
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 5 System Principles
Figure 5-3 NetNumen U31 System Hierarchy
The NetNumen U31 system has the following three layers:

l
NMS layer:
It manages all NEs within the controlled area, and coordinates the actions of all NEs.
EMS layer:
It implements operations on or manages one or multiple NEs, providing the
coordination function for the communication between NMS and NEs. The NetNumen
U31 system is located in this layer.
NE layer:
It includes the local OMM and NEs. The NetNumen U31 system connects an NE
through a local OMM. The local OMM shields the difference between various NEs,
collects the NE data and reports it to NetNumen U31, and converts the requests issued
by NetNumen U31 to instructions that can be processed by NEs.
Here, the northbound interface is the interface between NetNumen U31 and NMS, and the
southbound interface is the interface between NetNumen U31 and a managed NE.
5-3
SJ-20110823134613-002|2011-12-16(R1.1)
5-4
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 6
Product Functions
Table of Contents
Topology Management ...............................................................................................6-1
Fault Alarm Management ...........................................................................................6-3
Performance Management .........................................................................................6-7
Security Management ................................................................................................6-8
Log Management .......................................................................................................6-9
System Backup ........................................................................................................6-10
System Monitoring....................................................................................................6-10
Task Management ....................................................................................................6-11
Command Line Terminal...........................................................................................6-12
Radio Configuration Application ...............................................................................6-12
Northbound Interface................................................................................................6-13
6.1 Topology Management

Through topology management, users can learn the distribution and organization of
all network devices. The NetNumen U31 system manages a large number of devices
of different types. To manage these devices, it is necessary to perform centralized
management and grouping management.
The topology management view includes topology tree and topology view. The topology
tree and topology view synchronize with each other, and the topology tree provides the
navigation function for the topology view. The topology view displays the network structure
of the managed devices, and reflects the relationship of devices in a hierarchical manner.
In the topology view, the lines between the devices show the connection relationship
between the devices. The topology tree displays all the topology nodes in the network,
and the topology view displays all the topology nodes of the current layer. To the right
of the topology view, the lengend and bird's eye view map are embedded. The toolbar
contains a filter and buttons that help customize the displayed contents. Through the
filter, users can set the filtering conditions so that only the required contents are displayed
in the view.
The topology management provides the following functions:
l
l
Viewing and editing the location, network structure, link connection, and service
distribution of the network resources in each service system.
Displaying the topology relationship between service subnets, and supporting access
management.
6-1
SJ-20110823134613-002|2011-12-16(R1.1)
The following describes the functions of topology display, topology operations and topology
monitoring.
Topology Display
This function requires that the network resources are presented through a combination of
the resource tree and network topology view. According to different resource management
requirements, it provides different management views.
Topology Operations
NetNumen U31 supports the following topology operations:
l
l
l
l
l
l
l
l
l
l
Switching between different views

Selecting a single object, multiple objects, a batch of objects, or all objects
Zooming in, zooming out, moving, and restoring a view
Providing a panoramic view
Displaying the view in full screen
Automatically laying out the view
Displaying the filtered view
Searching for objects
Querying basic information
Linking to other functions
Topology Monitoring
The network topology view can dynamically display the running status of the managed
network in real time, implementing configuration monitoring, alarm monitoring, and
performance monitoring.
l
Configuration Monitoring
Through periodic synchronization, the topology view can dynamically show the
change of the network device configuration, including addition/deletion of NEs and
NE configuration change. In this way, users can obtain relevant prompts from the
topology view.
Users can set the information update period.
Alarm monitoring
The topology view can display the alarms generated in each lower-layer network
management system in the entire network, and remind users of the alarms in a
visible and audible manner.
The object icons corresponding to the faulty NEs are colored differently according to
the alarm levels. Acknowledged, unacknowledged, handled and cleared alarms are
also displayed differently.
On the lower part of the topology view on the client, all alarms of the current NE are
displayed in a list.
Performance Monitoring
6-2
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 6 Product Functions
In the topology view, users can monitor the performance tables or performance prompt
messages of specified NEs.
In the topology view, after setting the counters and NEs to be monitored, users can
click a NE in the topology tree to view the counter values of it. The performance prompt
message monitoring enables users to learn the latest information of the customized
key performance indices.
On the lower part of the topology view on the client, the performance data related to
the current NE is displayed in a list.
6.2 Fault Alarm Management

The fault management helps maintenance personnel find network faults and accurately
locate them immediately, and collect real-time alarm data and monitor the alarm data in a
centralized manner. It helps maintenance personnel to rapidly detect and locate network
faults.
The NetNumen U31 server and client cooperates with each other to implement the
centralized fault management functions.
l
Server
The server processes the alarms normalized by the NetNumen U31 system, and
stores the processed alarms in the alarm database. At the same time, it sends the
processed alarm data to the client for display.
Client
The client filters the alarms received from the server, and performs the user security
check. Then, it displays the alarms required by the user on the alarm list and topology
view.
The centralized fault management functions include:

l
l
l
l
l
l
l
l
l
l
l
l
l
Alarm data collection

Alarm information synchronization
Centralized alarm monitoring
Alarm query and statistics
Alarm forwarding
Alarm acknowledgement and clearing
Alarm redefinition
Alarm handling suggestions
Alarm filtering
Alarm rule management
Alarm backup and deletion
Alarm box management
Alarm filtering
6-3
SJ-20110823134613-002|2011-12-16(R1.1)
Alarm Data Collection

l
NetNumen U31 collects alarm data in real time.

The collected alarm data includes alarm information of the managed devices,
performance threshold-crossing alarm information, and alarm information of the
NetNumen U31 itself.
l
l
NetNumen U31 can control the alarm and notification reporting condition and
implement alarm masking.
NetNumen U31 ensures correctness of the data obtained from the lower-layer OMMs.
Alarm Information Synchronization

The lower-layer and upper-layer systems present inconsistent data in the following
cases: network fault, NetNumen U31 server failure, and lower-layer system fault. In such
case, users can perform automatic synchronization of current alarms to ensure the data
consistency.
The following two synchronization methods are provided to synchronize the current alarm
status displayed in NetNumen U31 and the current alarm status of the managed OMM:
l
l
Manual synchronization: In this mode, the alarm synchronization is initiated by a user.

Automatic synchronization: In this mode, the alarm synchronization is initiated by the
system.
After the synchronization starts, the system will prompt the initiation and result of the
synchronization in the down-left message bar.
Centralized Alarm Monitoring

In alarm monitoring, the real-time alarms are displayed in the form of charts or tables. The
following functions are supported:
l
l
l
l
Customizing the display of alarm information to show the needed information of the
alarms
Setting filter conditions to display qualified alarms only
Querying historical alarms by customized conditions
Customizing the colors and sounds of alarms based on alarm severity level.
Alarm Query and Statistics

This function involves two aspects: operations and results:
l
Alarm query and statistics operations

Users can query and measure the current and historical alarm information according
to the combination of the following conditions: alarm occurrence system, network
element location, alarm severity level, alarm status, alarm type, alarm occurrence
time, and alarm code.
Alarm query and statistics results:

6-4
SJ-20110823134613-002|2011-12-16(R1.1)
The query and statistics result can be displayed in many forms, such as report and
chart. The result can be saved and printed. Users can set the output condition, output
destination and output mode (such as printer or file).
Alarm statistics includes basic historical alarm statistics and busy-hour historical alarm
statistics.
l
Basic historical alarm statistics

It counts the alarm frequency and effective alarm time according to conditions like the
alarm occurrence system type, NE position, NE type, alarm severity level, alarm code,
and alarm type.
Busy-hour historical alarm statistics

It takes each hour of a day as the query condition, which facilitates users to query the
alarm frequency and effective alarm time during a time segment of the day.
Alarm Forwarding
NetNumen U31 can automatically forward alarm information to network management
users or maintenance personnel for timely processing. Users can customize the alarm
forwarding condition, forwarding recipients and forwarding mode.
NetNumen U31 uses the following alarm forwarding methods:
l
l
l
E-mail
Mobile phone short messages
Alarm box
Alarm Acknowledgement and Clearing

The network management personnel can acknowledge, unacknowledge, or clear alarms,
and save the alarm handling suggestions in the system.
After NetNumen U31 receives the alarm acknowledgement message or alarm clearing
message from the managed OMMs, it automatically acknowledges or clears the
corresponding alarms.
Alarm Redefinition
This function is to redefine severity level of an alarm according to the alarm code, alarm
source, and NE type.
Alarm Handling Suggestions

NetNumen U31 provides the function of managing alarm handling suggestions and
providing users with suggestions of alarm handling. Users can easily view the suggestions
when they handle alarms.
There are two types of alarm handling suggestions: default suggestions and customized
suggestions. Users can modify the customized suggestions on the interface or by
importing suggestions from files.
6-5
SJ-20110823134613-002|2011-12-16(R1.1)
Alarm Filtering
User can filter out certain unimportant alarms according to a combination of alarm type,
alarm code and alarm cause. Alarm filtering effectively reduces the number of alarms.
Alarm filtering can be performed respectively on the server and the client:
l
Alarm filtering on the server

Alarms are directly filtered out on the NetNumen U31 server, and not saved in the
NetNumen U31 database. After the alarm rules are set, users on the client cannot
see the alarms that are filtered out. After the alarm rules are deleted, users on the
client cannot see such alarms either.
Alarm filtering on the client
Alarm filtering for all users: In this case, alarm filtering is performed during alarm
preprocessing, and the selected alarms will not be sent to the client.
Alarm filtering for a filter creator: In this case, the selected alarms will not be sent
to the client to which the filter creator logs in.
Alarm Backup and Deletion

Users can manually back up and delete an alarm according to alarm occurrence time.
Alarm Task Setting

Alarm task setting includes alarm statistics task setting and alarm report task setting.
l
Alarm statistics task setting

It sets the scheduled tasks to periodically execute the alarm statistics template, such
as basic/busy-hour historical alarm statistics template, and saves the statistics result
as a file in the server directory.
Alarm report task setting

It sets the scheduled tasks to query the current/historical alarms that meet the
customized query conditions (without using a template), and saves the query result
as a file in the server directory.
Alarm Rule Setting

The alarm management function uses many customized rules, which are the basis of alarm
processing. Alarm rule setting enables users to add, delete, modify, refresh, activate, and
suspend such alarm rules.
The rules include the alarm counting rule, alarm delay rule, alarm clearing rule, alarm
merging rule, alarm timing rule, alarm association rule, and notification filtering rule.
6-6
SJ-20110823134613-002|2011-12-16(R1.1)
Alarm Box Management

NetNumen U31 supports the use of alarm box to indicate alarms. Users can create, modify,
view, delete, disable, and enable an alarm box in the system. The system connects an
alarm box according to the preset rule and sends alarm information to the alarm box.
6.3 Performance Management

Performance management is responsible for network performance monitoring and
analysis. Through this function, the system collects various performance data from NEs
and detects the network running status, providing detailed information for the operation
and maintenance personnel. The performance management helps to guide the network
project planning and adjustment, and improves the network running quality.
NetNumen U31 collects the data of the entire network for lateral comparison and analysis,
which helps to find the operating problems of devices in different areas, and improve the
upper-level management.
Performance management provides the following functions:
Performance Data Query

Displays the performance data, which is collected by the measurement task and saved in
the database, in various mode according to the query conditions set by users.
Measurement Task Management

The measurement task defines the data collection method, which specifies the NE type,
measurement object type, performance object, NE position, measurement object, and
collection time. After a measurement task is created, the system collects the performance
data according to the task scheduling rule and measurement granularity defined in the
task.
Counter and Index Management

Provides the viewing function for the counter, and the creating, deleting, modifying,
viewing, importing, and exporting functions for the indexes.
Threshold Task Management

The threshold task monitors the measured data during a preset period and calculates the
data of a specific performance object. If the calculation result of a performance object
exceeds the corresponding preset threshold, the system raises an alarm and reports it to
the fault management module for display.
Template Management
Two template types are defined: common template and query template.
6-7
SJ-20110823134613-002|2011-12-16(R1.1)
Common template: a common template defines the NE type, measured object type,
and performance object. The NE position and the measured object position often
change in actual queries, so they are not defined in the common template. Users can
specify such positions in an actual query.
Query template: a query template is often used in a performance data query. Users
can save the query conditions in it. By using an appropriate query template, users can
quickly query performance data at any time without setting the same query conditions
repeatedly.
The query template parameters include the queried index, queried object, and queried
time.
Template Task Management

The query template or common template can be used to create a performance data query
task (namely, a template task) and set the task schedule. Then, the system can periodically
implement performance data query according to the task template and task schedule.
Performance Data Monitoring

Monitors and displays the latest data of specified indices or counters of specific NEs.
The performance data real-time monitoring module displays the latest value of the specified
monitoring index or counter that is in the specified monitoring location.
Performance Data Integrity Check

NetNumen U31 provides the function of checking the integrity of collected performance
data. By using this function, users can check the integrity of performance data of each
performance object in the database and find the period(s) during which the performance
data is absent.
6.4 Security Management

Security management is implemented on the client and the server. The client provides
the user login window, handles and displays the data of user security management,
including role management, role set management, user management, and department
management. The server implements logical processing for login authentication and
operation authentication.
Security management ensures legal use of the system by users. It implements role
management and user management. Through appropriate organization of the relationship
between users and roles, security management provides security control on the security
management operations. Through login authentication, it prevents illegal users from
accessing the system. Through operation authentication, it provides security control on
the user operations.
6-8
SJ-20110823134613-002|2011-12-16(R1.1)
Role Management
The role management involves two aspects: role set management and role management.
l
Role Set Management

A role set is a set of role rights. After a user is assigned with a role set, the user has
all the role rights in the set.
Users can create, modify, duplicate and delete a role set with a user account
authorized with the operations on the role sets.
Role Management
A role defines the user rights, including operation rights and resource rights.
Users can create, modify, duplicate and delete a role within the scope of authority
assigned by the system.
User Management
User management is the most important part of security management of the NetNumen
U31 system.
Through user management, the system administrator can perform the following operations:
l
l
l
l
l
l
l
Creating a user
Querying a user
Modifying a user
Assigning operation rights to a user
Setting the working period for a user
Deleting a user
Prohibiting a user
A newly created user can log in to the NetNumen U31 system with its user name and
password, and performs network management operations within the scope of rights
assigned to it.
A department is used to manage the executive affiliation of users. In practical applications,
for the convenience of user management, departments can be established corresponding
to the real network management departments.
6.5 Log Management

According to the log type, the logs can be categorized into three types: operation log,
security log, and system log.
Log management provides an effective tool for the system administrator to trace system
running status, locate system faults, and trace the situation of users. A common user, that
is, a user other than the administrator, can also know the working status of the system
through log management by reviewing previous operations.
Log management provides the following functions:
l
Querying logs according to log type

6-9
SJ-20110823134613-002|2011-12-16(R1.1)
Querying logs according to customized conditions

Users can customize the query conditions.
Exporting logs
Users can export the logs in the form of a file to a remote log server, either manually
or by customizing a exporting task.
The logs are divided into the following three types:

l
l
l
Operation log, recording user operation information.

Security log, recording user login information.
System log, recording the completion status of system tasks on the server.
6.6 System Backup

The default maintenance policy is provided for all the databases of NetNumen U31.
The backup and recovery functions of the NetNumen U31 system include backup tasks
and restoration tasks. The main objects include database, file, log data, alarm data, and
performance data.
l
Backup Tasks
Whole database structure backup
Basic data backup
File backup
Log data backup and deletion
Alarm data backup and deletion
Performance data backup and deletion
Restoration Tasks
Log data restoration
Alarm data restoration
Performance data restoration
6.7 System Monitoring

NetNumen U31 provides a unified maintenance and management platform for monitoring
the system itself. System monitoring includes application server monitoring and database
monitoring.
l
Application Server Monitoring
Monitoring the application server performance

To monitor the application server of the system, users should set the thresholds
of the CPU, memory and hard disk utilization of the server. After the monitoring
is started, the system collects the real-time performance data during each
6-10
SJ-20110823134613-002|2011-12-16(R1.1)
monitoring period, compares them with the preset thresholds, and decides
whether to report alarms in the monitoring view.
Viewing the application server performance

Users can monitor the application server performance in real time, including
setting the periods for monitoring the utilization of CPU, memory and hard disk
of the server and checking the current utilization of them.
Viewing basic information of the application server

The system also displays basic information of the application server, including the
device name, device type, Java Name and Directory Interface (JNDI) port, host
IP address, host name, and NMS version number.
Database Monitoring
Monitoring the database resource

The system can monitor the hard disk space of the database according to the
preset monitoring period. It can also monitor specific table space as required.
When the size of the used disk space exceeds the preset threshold, the system
gives an alarm.
Viewing the database resource

Users can view and refresh information of the table space, data tables, and
processes of the database.
Viewing basic information of the database server

The system also displays basic information of the database server, including the
device name, device type, database type, database port, database version, and
host IP address.
6.8 Task Management

In NetNumen U31, task management is used to manage all periodic tasks.
l
Historical data archiving task

This task periodically backs up and deletes the data in the database, including
log data, performance data, and alarm data. It avoids that the data amount of the
database becomes too large, which might influence the system performance.
Configuration data backup task

This task backs up all the basic configuration data of the network management system,
that is, all data except for the table structure data and historical data.
Version and database backup task

This task backs up the whole database structure and the file system. For the whole
database structure backup, all database structures used in the NMS are backed up.
For the file system backup, the version files, configuration files, and running files are
backed up.
6-11
SJ-20110823134613-002|2011-12-16(R1.1)
File cleaning task

This task periodically clean the query files generated by the cleaning task according to
the directory setting and cleaning setting. It effectively manages the hard disk space.
Alarm back-end task

This task automatically acknowledges the historical alarms before the preset number
of days. It avoids manually acknowledging alarms, and improves the maintenance
efficiency.
MML timing task

This task executes MML commands according to preset time to implement the
customized functions.
6.9 Command Line Terminal

The command line terminal is a command line tool that NetNumen U31 provides for
the engineering technical personnel. Users can enter a single command or a batch of
commands to manage the network management objects.
Users can execute the commands in the GUI on the client, or telnet to the server to use
the command line tool.
The command line terminal provides the following functions:
l
Executing a single command

A single command can perform only one operation on the managed object at a time,
for example, creating a managed object, deleting a managed object, and refreshing a
view. With the online help provided by the system, users can conveniently obtain the
command format. Then, users can modify or add command parameters according to
the operation requirement. After the command syntax check is passed, the command
can be executed.
Executing a batch of commands

If multiple maintenance tasks are to be implemented continuously, users can execute
the commands in batch.
Providing help, including the MML command help.
6.10 Radio Configuration Application

NetNumen U31 provides a radio configuration application module that supports centralized
configuration and maintenance of multiple NEs at the same time.
The local Operation Maintenance Module (OMM) of each NE can only complete
configuration operations on the NE itself. However, the radio configuration application
module can implement centralized configuration that involves multiple NEs.
It provides the following functions:
6-12
SJ-20110823134613-002|2011-12-16(R1.1)
l
l
l
l
l
l
l
l
l
l
l
l
Interconnection parameter management

NE association relation management
NE stability management
Operation and maintenance status query and setting
VIP site priority query and setting
Inventory management
Site migration
Inter-NE import and export of configuration data
Neighbor cell relation check
Neighbor users ID consistency check
Cell broadcasting management
Configuration data collection
6.11 Northbound Interface

The NetNumen U31 system provides the northbound access capability.
6-13
SJ-20110823134613-002|2011-12-16(R1.1)
6-14
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 7
Interfaces and Protocols

Table of Contents
Internal Interfaces ......................................................................................................7-1
Southbound Interfaces ...............................................................................................7-1
Northbound Interfaces ................................................................................................7-1
7.1 Internal Interfaces

The internal interfaces of NetNumen U31 are interfaces between the NetNumen U31
server and clients. The bottom layer of the interface uses the TCP/IP protocol. The
communication bandwidth is not smaller than 256 kbps.
The NetNumen U31 server and clients communicate with each other through an LAN or a
WAN.
7.2 Southbound Interfaces

Through the southbound interfaces, NetNumen U31 communicates with the OMM.
Southbound interfaces implement the communication between NetNumen U31 and the
local OMMs of managed NEs.
The protocols that the southbound interfaces comply with include MML, FTP, and
SOCKET.
The southbound interfaces supports the adaptation of data of different formats in data
transmission.
7.3 Northbound Interfaces

The interfaces between NetNumen U31 and a Network Management System (NMS) are
called northbound interfaces.
The northbound interfaces comply with special interface standards that specify the
information model, technical modes and functions for the connection between the EMS of
the manufacture and the NMS of the operator. The use of northbound interfaces provides
the basis for centralized network management and maintenance required by operators.
Figure 7-1 shows the position of the northbound interfaces in the radio network.
7-1
SJ-20110823134613-002|2011-12-16(R1.1)
Figure 7-1 Northbound Interface Position
NetNumen U31 provides abundant northbound interfaces, including:

l
l
l
l
l
l
l
l
l
CORBA northbound alarm interface

CORBA northbound configuration interface
CORBA northbound performance interface
CORBA northbound inventory interface
SNMP northbound alarm interface
Socket northbound alarm interface
FTP northbound interface
FTP northbound performance interface
FTP northbound inventory interface
7.3.1 CORBA Northbound Interfaces

CORBA Overview
Common Object Request Broker Architecture (CORBA) is an open, client/server-based
and object-oriented industrial standard. CORBA defines a protocol for communication
between objects. The objects that comply with the protocol can interact with each other,
without being affected by languages, hosts, and OSs. Any application systems that provide
CORBA interfaces can interconnect with each other easily.
Through the CORBA interface, the configuration, performance, and alarm functions are
implemented. The CORBA architecture consists of the following parts:
l Object Request Broker (ORB)
ORB is the basis for constructing distributed object applications, and the basis for
inter-operability of applications in heterogeneous or homogeneous environment.
ORBs receive and transmit requests and responses transparently in the distributed
environment.
l
Object service
The object service provides a set of basic objects with the aim of implementing and
using objects. The object service is independent of the application area.
Public facilities
7-2
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 7 Interfaces and Protocols
The public facilities provides the user with a group of interfaces for shared services,
such as system management, compound document and E-mail.
l
Application interface
The application interface is the interface that expand the application, which is similar
to the application presentation layer.
Domain interface
The domain interface is the interface that is provided for the application domain
service.
CORBA Northbound Interface Capability of NetNumen U31

The CORBA northbound interfaces of NetNumen U31 include:
l
l
l
l
CORBA
CORBA
CORBA
CORBA
northbound
northbound
northbound
northbound
interface
configuration interface
performance interface
inventory interface
7.3.1.1 CORBA Northbound Alarm Interface

The CORBA northbound alarm interface provided by NetNumen U31 supports the
following functions:
l
l
l
l
l
l
l
l
l
l
Reporting alarms
Synchronizing alarms
Acknowledging alarms
Unacknowledging alarms
Acquiring the number of alarms
Adding the description of alarms
Clearing alarms
Notifying the change of alarm acknowledgement status
Reporting the addition of alarm description
Reporting the reestablishment of alarm information list
7.3.1.2 CORBA Northbound Configuration Interface

The CORBA northbound configuration interface provided by NetNumen U31 supports the
l
Basic configuration functions

Creating, deleting, querying and modifying configuration information
Notifying the change of configuration information

When configuration information of an NE changes, NetNumen U31 notifies the NMS
of the configuration information change, including object creation, object deletion, or
the change of attribute values.
Synchronizing configuration information

7-3
SJ-20110823134613-002|2011-12-16(R1.1)
When network configuration information changes, a synchronization process can be

initiated to synchronize the latest configuration information from NetNumen U31 to the
NMS.
7.3.1.3 CORBA Northbound Performance Interface

The CORBA northbound performance interface provided by NetNumen U31 supports the
1. Performance collection management function set
l Creating collection activities
l Stopping collection activities
l Suspending collection activities
l Restoring collection activities
l Querying collection activity parameters
l Recollecting performance data
l Reporting performance data
l Reporting the status change of collection activities
2. Performance threshold management function set
l Creating performance thresholds
l Deleting performance thresholds
l Suspending performance thresholds
l Restoring performance thresholds
l Querying performance threshold parameters
l Reporting performance threshold-crossing alarms
l Reporting the status change of performance thresholds
7.3.1.4 CORBA Northbound Inventory Interface

NetNumen U31 provides a detailed inventory of software and hardware resources in
the managed network. Users can query hardware information in Radio Configuration
Application, and query software information in software version management.
Inventory information stored in the NetNumen U31 system includes the physical location
of devices (building, floor, room, rack, shelf, slot, port, and serial number), electronic serial
numbers of devices, firewall level, and software level.
NetNumen U31 transfers inventory information to the NMS in the format of XML or CSV file
through the CORBA northbound inventory interface or FTP northbound inventory interface
7.3.2 FTP Northbound Interface

The FTP northbound interface of NetNumen U31 is used to get file information from
NetNumen U31 for an NMS.
In NetNumen U31, users can transfer the selected data to a specified file and periodically
report this file to the NMS via the FTP northbound interface, or store the selected data in
a file in a specified path for periodic acquisition by the NMS.
7-4
SJ-20110823134613-002|2011-12-16(R1.1)
In NetNumen U31, configuration data, performance data, and inventory data are
transferred to the NMS in the format of XML file or CSV file via the FTP northbound
interface.
NetNumen U31 also supports the SSH-based SFTP protocol, which ensures safer
northbound file transmission services.
7.3.3 SNMP Northbound Interface

SNMP is an application-layer protocol used for management information exchange
between network devices. It is a part of TCP/IP stack. SNMP has been widely used in
the telecommunications field due to its simple and practical characteristics. It becomes
the most widely used management frame of TCP/IP networks.
SNMP protocol is based on User Datagram Protocol (UDP), which specifies the
encapsulation format of data units.
SNMP protocol has three versions: SNMPv1, SNMPv2c and SNMPv3.
SNMP Network Management Model

The network management model of SNMP consists of four parts:
l
Management Node
The management node runs the SNMP agent program. It maintains a local database,
describes the status and history of the node, and influences the running of the node.
Management Station
The management station runs a special network management program (manager) to
implement communication with the SNMP agent on the managed node, and maintains
the management information base.
Management Information Base

Each management station use one or more variables to describe its status. These
variables are objects that form the Management Information Base (MIB).
Management Protocol
The management protocol is used by the management station to query and modify
the status of the managed node. The management node can use the management
protocol to send Trap messages to the management station.
SNMP Message Types

There are five types of SNMP messages:
l
l
Get_Request
Get_Next_Request
SNMP Manager uses a Get_Request message to search for information in a network
device with SNMP Agent. Get_Request and Get_Next_Request messages can be
used together to get an object in a table, where Get_Request is used for getting a
7-5
SJ-20110823134613-002|2011-12-16(R1.1)
specific object in the table and Get_Next_Request is used for getting the next object
in the same table.
l
Get_Response
SNMP Agent responds to the Get_Request message with a Get_Response message.
It exchanges much information with SNMP Manager, such as system name, how
long the system runs properly after starting automatically, and the number of network
interfaces in the system.
Set_Request
SNMP Agent can use the Set_Request message to remotely configure the parameters
of a device.
Trap
Trap is a non-request message sent by SNMP Agent to the management station. It is
used to notify the server of a certain event.
Application of SNMP in the NMS

The SNMP protocol provides the functions of SNMP Manager and SNMP Agent in the
network management system, as shown in Figure 7-2.
Figure 7-2 Application of SNMP in NMS
The functions of SNMP Manager are used when the lower-level network element systems
are managed by the SNMP protocol. In this case, all NEs are managed by NetNumen U31
as SNMP agents.
7-6
SJ-20110823134613-002|2011-12-16(R1.1)
The functions of SNMP Agent are used when the upper-layer NMS manages NetNumen
U31 by the SNMP protocol. In this case, the upper-layer NMS manages NetNumen U31
as an SNMP manager.
SNMP Manager functions and SNMP Agent functions have no coupling relation.
NetNumen U31 provides SNMP Manager and SNMP Agent functions according to the
actual requirements.
Functions of SNMP Northbound Interface of NetNumen U31

The SNMP northbound alarm interface of NetNumen U31 complies with the IETF
specification, and provides the following alarm functions for the upper-layer NMS:
l
l
l
l
l
l
l
l
Adding an alarm reported

Clearing alarms reported
Getting the alarm list
Getting the number of alarms
Querying and acknowledging alarm status
Clearing alarms
Querying and modifying alarm comments
Filtering and controlling the alarms reported
7.3.4 SOCKET Northbound Interface

NetNumen U31 provides a SOCKET northbound alarm interface with excellent real-time
performance, short delay and high flexibility to transfer alarm information to the NMS via
TCP/IP.
The SOCKET northbound alarm interface provides the following functions:
l
l
l
l
l
Reporting heartbeat messages

Reporting alarm events
Clearing alarm event reporting
Synchronizing alarms
Filtering and controlling the alarms reported
7-7
SJ-20110823134613-002|2011-12-16(R1.1)
7-8
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 8
Networking Modes
Table of Contents
Local Networking Mode ..............................................................................................8-1
Remote Networking Mode ..........................................................................................8-2
Remote Client Networking Mode ................................................................................8-3
8.1 Local Networking Mode

The local networking mode is the simplest and the most common networking mode used
by centralized network management systems. In this networking mode, the server and
clients are located in the same Local Area Network (LAN) and are connected with each
other through Ethernet, and the server connects the managed Network Elements (NEs)
through various transmission networks.
1. Topology
Figure 8-1 shows the topology of the local networking mode.
8-1
SJ-20110823134613-002|2011-12-16(R1.1)
Figure 8-1 Local Networking Topology
2. Device requirement
Few network devices are needed for the local networking mode. According to the
quantity of hosts (namely, the number of servers and clients), select proper 10/100
Mbps adaptive HUBs with enough ports and prepare necessary twisted pairs (namely,
Ethernet cables) to construct the network.
8.2 Remote Networking Mode

In remote networking mode, the NMS clients are located remotely from the NMS server.
There are many remote networking types, which have similar basic network topology and
the same principle. In this networking mode, a special transmission device is used for WAN
access, and the interface between the transmission device and the router is a standard
interface. The router, switch, server, and clients form a LAN.
8-2
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 8 Networking Modes
According to transmission mode, the remote networking mode supports transmission over
the Digital Data Network (DDN) dedicated line, E1 line, or High-data-rate Digital Subscriber
Line (HDSL).
Figure 8-2 shows an example of remote networking. The NMS server and NEs are located
in the same LAN. The remote client connects the local NMS server through DCN and
performs maintenance management operations.
Figure 8-2 Remote Networking Example
8.3 Remote Client Networking Mode

In remote client networking mode, the client and managed NEs are in a LAN while the
server is located in a remote site. The client connects the remote server through DCN and
manages the local NEs through the server.
Figure 8-3 shows a remote client networking example.
8-3
SJ-20110823134613-002|2011-12-16(R1.1)
Figure 8-3 Remote Client Networking Example
8-4
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 9
Environment Requirements
Table of Contents
Grounding Requirements ...........................................................................................9-1
Temperature and Humidity Requirements...................................................................9-2
Cleanness Requirements ...........................................................................................9-3
Air Conditioning and Ventilation Requirements ...........................................................9-3
Anti-EMI Requirements ..............................................................................................9-3
Lightning Protection Requirements.............................................................................9-4
Anti-Static Requirements............................................................................................9-5
Quakeproof Requirements .........................................................................................9-5
Illumination.................................................................................................................9-5
Fire Prevention Requirements ....................................................................................9-6
Atmospheric Pressure Requirement ...........................................................................9-6
Air Pollution Limitation ................................................................................................9-6
9.1 Grounding Requirements

Grounding plays an important role in keeping a good electromagnetic environment for the
primary device and auxiliary devices and in keeping the anti-interference capability of the
devices. Therefore, much attention should be paid to grounding.
The following rules must be followed:
l
Adopt the joint grounding mode: The working groundings, protective groundings and
the lightning protection grounding of the building share one grounding body.
The soil type has a significant effect on the grounding resistance.

In the area where the grounding of soil is poor, add chemical additives (such
as acrylamide resistance-reducing agent) around the grounding pole to reduce
the resistance of the soil and the contact resistance between the soil and the
grounding pole.
The temperature and humidity may also affect the grounding resistance.
If the temperature is lower than 0 or the humidity is too low, the grounding
resistance may change largely. In this case, bury the grounding pole deeply or
add chemical additives to meet the requirement on the grounding resistance.
The requirements on the grounding pole and the connection cable between the
grounding pole and the grounding bolt of the main device are as follows:
The angle iron that is used by the grounding pole should be shorter than 2 m. If
conditions permit, adopt the grounding net.
9-1
SJ-20110823134613-002|2011-12-16(R1.1)
The connection cable between the grounding pole and the grounding bolt of the
main device should adopt the copper core. The sectional area of the copper
cable should be equal to or larger than 50 mm2, and the length of the copper
cable should be as short as possible. If the length is longer than 50 m, use a
copper cable with a larger sectional area. Tin coat or flow promoter solder the
two ends of the connection cable. Remove the coating, varnish, oil paint, and
oxid coating from the fastening point to ensure good contact between the mental
surfaces.
Take corrosion-proof measures to protect all grounding junction pieces, and

fasten the grounding bolts with the mechanical method to ensure low-resistance
connection.
To ensure a grounding resistance smaller than 1 , users need to consider the factors
that affect the grounding resistance. The factors include soil status, resistance of the
grounding body, grounding cable, and so on.
Before device commissioning, measure the accurate grounding resistance.
If the grounding resistance does not meet the requirement, usually you need to stop
the office deployment temporarily. If the user want to continue the office deployment,
the user needs to make a written commitment in which the user promises to be
responsible for any problem caused by grounding. The office deployment cannot
continue before the written commitment is allowed by the corresponding department
of ZTE Corporation.
After the device is put to use, the maintenance personnel must measure the grounding
resistance periodically and record the resistance. If the grounding resistance grows
larger, take proper measures to reduce it so that it meet the grounding resistance
requirement of the device.
9.2 Temperature and Humidity Requirements

Too high or too low temperature and humidity may affect the device running and device
life cycle adversely.
For example, if the temperature is 10 higher than the normal temperature, the life cycle
of the device is shortened to one half of its normal life cycle. If the temperature is too low,
the performance of the optical components and crystal components cannot be ensured.
If the relative humidity is constantly too high, the insulation of certain insulation material
may deteriorate or even cause electric leakage, and the metal components of the device
may get corroded. If the relative humidity is constantly too low, the insulation pad may
shrink and then loosen the fastening bolt, and strong static discharge is liable to occur,
endangering the CMOS circuit on the device.
Table 9-1 shows the requirements on the temperature and humidity in the equipment room.
9-2
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 9 Environment Requirements
Table 9-1 Temperature and Humidity Requirements

Temperature
Relative Humidity
Long-Term Operating
Short-Term Operating
Long-Term Operating
Short-Term Operating
Conditions
Conditions
Conditions
Conditions
10 ~ 30
0 ~ 45
30% ~ 85%
20% ~ 90%
Measure the temperature of the operating environment inside the equipment room at the spot that is
1.5 m above the floor and 0.4 m before the rack when there is no protective plate in front or back of
the equipment rack.
Short-term operating conditions mean that the successive operating time is not more than 48 hours
and the accumulated operating time per year is not more than 15 days.
9.3 Cleanness Requirements

The cleanness of the equipment room must meet the following requirements:
l
l
l
l
The percentage of fresh air in the equipment room should be at least 5%, ensuring
the freshness of the air.
In addition to percentage of dust and the size of the dust particle, there are also strict
requirements on the concentration of salt, acid and sulfide in the air, because they
cause the erosion of metal and aging of certain parts.
Harmful gases, such as SO2 and H2S, should be kept out of the equipment room to
protect the health of the maintenance personnel.
The concentration of the dust particles with a diameter of larger than 5 um should be
equal to or smaller than 3104 particles/m3.
9.4 Air Conditioning and Ventilation Requirements

The air conditioners in the equipment room run normally, and the temperature and humidity
in the equipment room are within the normal ranges.
9.5 Anti-EMI Requirements

The equipment room should be far away from the strong-power radio station, radar
transmitting station, or high-frequency and high-current device. The radiant energy that
the equipment room suffers should be under 300 mV/m. The magnetic intensity around
the equipment room should be smaller than 11 GS.
Usually, you can take the following anti-Electro Magnetic Interference (anti-EMI) measures.
l
l
Shield the equipment room or shield the specific EMI source.

Install a shielding wall between the main devices and the transmitter that has
high-frequency radiation, and the devices and the transmitter use different power
supply cables.
Ground all the cables and conductors properly, and ground the shielded layers of all
the cables properly.
9-3
SJ-20110823134613-002|2011-12-16(R1.1)
l
l
l
Twist the signal line and the return line to counteract the induced voltage caused by
the EMI on the lines.
Separate the power cable and signal cable and do not lay them in parallel.
The grounding cable of the AC power supply and that of the DC power supply must
be separated strictly.
9.6 Lightning Protection Requirements

Lightning protection is an important measure that ensures the security of the device. The
equipment room should meet the following requirements in design:
l
If the height of the main building or affiliated facilities such as chimney, antenna and
water tower is higher than 15 m, adopt effective lightning protection measures based
on the lightning protection requirements on class-2 civil buildings and structures.
Take measures to prevent direct lightning strokes and lightning current invasion. If a
high-rise building acts as the equipment room, take measures to prevent side thunder
strokes. In the areas where thunders are frequent, side thunder strokes are common.
In design, adopt measures to prevent side thunder strokes. For example, connect the
metal windows to the lightning protection down lead, and attach horizontal lightning
protection bars to the external wall surface with a specified distance.
The following lightning protection measures should be taken for the main building of the
equipment room.
l
l
Install a lightning protection grid or lightning protection bar in the locations where
lightning attacks are liable to occur.
On the top of the objects that are higher than the building roof, such as chimney,
antenna, and water tower, install the lightning protection wire or lightning arrester on
them.
The sectional area of the down lead of the lightning protection device should be at
least 200 mm2, and distance between the down leads should be equal to or smaller
than 30 m. In the case of joint grounding, the grounding resistance should be equal to
or smaller than 1 ; in the case of independent grounding, the grounding resistance
should be equal to or smaller than 10 .
In the past, the lightning protection grounding of the building and that of the power
supply system are separated. It is required that a certain distance be reserved
between the grounding bodies. However, the building space is limited, the distance
requirement is usually not met.
In fact, the grounding bodies cannot be separated in many cases, so a joint grounding
system is recommended, that is, the working grounding, protection grounding, and
the lightning protection grounding of the building share one grounding system. In this
case, the grounding resistance is high.
l
l
Before entering a building, the cables and metal pipes should be grounded.
The metal part (such as the reinforcing steel bar within the building or column) is
recommended as the down lead of the lightning protection grounding. The down leads
should be electrically interconnected for equalizing potential within the building.
9-4
SJ-20110823134613-002|2011-12-16(R1.1)
Chapter 9 Environment Requirements
The grounding resistance is far smaller than 10 according to the telecom

requirement, and the grounding requirements of different telecom devices may be
different, so users need to determine the grounding resistance according to the
smallest grounding resistance.
On the line that leads from the mains to the equipment room, install the proper power
supply lightning protection device.
9.7 Anti-Static Requirements

The damage of static electricity to electron devices is not a one-time damage; instead, the
damage may accumulate and cause episodic fault or performance deterioration during the
device running. The static electricity may also cause software faults, cause malfunction or
even misoperation of the electronic switch and control circuit. Therefore, much attention
must be paid to the anti-static requirement.
Electrostatic induction mainly comes from the following aspects:
l
l
l
External electric field such as high-voltage transmission line and thunder and lightning.
External system such as in-door environment, floor material, and integrated
equipment structure.
Human contact of the maintenance personnel with the device which may leak the
static electricity of the human body to the device
To eliminate the damage that is caused by static electricity, take the following measures:
l
l
l
Ground the devices properly.

Install the anti-static floor and ground the floor properly.
The maintenance personnel should wear an anti-static wrist strap during operations,
and the anti-static wrist strap should be connected to the static discharge hole of the
rack.
9.8 Quakeproof Requirements

The quakeproof level of the equipment room building should be one level higher than the
quakeproof level of the common local buildings. For the equipment room building that
does not meet the quakeproof level requirement, strengthen it for earthquake resistance.
Before the reinforcement, ask the building design department for earthquake-resistance
reinforcement design. The devices should resist the earthquake with magnitude of 7.
9.9 Illumination
The illumination in the equipment room should meet the following requirements:
l
Install incandescent lamps or emergency lightning equipment in proper locations

between racks, which may be used during equipment installation and maintenance.
Direct sunshine should be avoided to prevent the circuit boards and other components
from aging and deforming.
9-5
SJ-20110823134613-002|2011-12-16(R1.1)
l
l
Colored glass is recommended as the window glass, and dark and non-transparent
curtains are recommended.
Fluorescent lamps that are embedded in the ceiling of the equipment room are used
for illumination, and the recommended average illumination is 150 lx ~ 200 lx.
9.10 Fire Prevention Requirements

The main building of the equipment room must meet the requirements of Building Design
Fireproof Specification. Equip the building with the required fire-fighting equipment and
reserve sufficient fire-fighting accesses according to the fire regulation of the related local
department. Mark the equipment room with the key fire-fighting unit label.
Dangerous substances such as inflammable and explosive substances are prohibited in
the equipment room and auxiliary equipment room. Post the "No smoking" or "No fire"
notice in a proper locations in the equipment rooms; equip the equipment rooms with
proper fire-fighting equipment and put the equipment in the proper position; equip the
equipment rooms with the water supply facilities for fire fighting.
The storage capacity of the fire-fighting water must ensure a fire fighting of at least two
hours. The water supply pipe (as well as drain pipe and rainwater pipe) should not cross
the equipment room, and the fire hydrant should not be located inside the equipment room.
9.11 Atmospheric Pressure Requirement

The atmospheric pressure requirement for the NetNumen U31 system is between 70 kPa
and 106 kPa.
9.12 Air Pollution Limitation

Erosive gases, smog and smoking are prohibited in the equipment room.
9-6
SJ-20110823134613-002|2011-12-16(R1.1)
Figures
Figure 1-1 Network Management Model ................................................................... 1-1
Figure 3-1 Single-Server System Hardware Structure ............................................... 3-1
Figure 3-2 Hardware Structure of Local HA System .................................................. 3-2
Figure 3-3 Hardware Structure of Remote Disaster Recovery System ...................... 3-3
Figure 5-1 Working Principle of NetNumen U31 ........................................................ 5-1
Figure 5-2 Remote Client Position ............................................................................ 5-2
Figure 5-3 NetNumen U31 System Hierarchy ........................................................... 5-3
Figure 7-1 Northbound Interface Position.................................................................. 7-2
Figure 7-2 Application of SNMP in NMS.................................................................... 7-6
Figure 8-1 Local Networking Topology ...................................................................... 8-2
Figure 8-2 Remote Networking Example................................................................... 8-3
Figure 8-3 Remote Client Networking Example......................................................... 8-4
Figures
Tables
Table 4-1 Server Hardware Configuration (SUN)....................................................... 4-1
Table 4-2 Server Hardware Configuration (IBM)........................................................ 4-2
Table 4-3 Server Software Configuration (SUN) ........................................................ 4-2
Table 4-4 Server Software Configuration (IBM) ......................................................... 4-2
Table 4-5 Client Hardware Configuration................................................................... 4-3
Table 4-6 Client Software Configuration .................................................................... 4-3
Table 9-1 Temperature and Humidity Requirements.................................................. 9-3
III
Tables
Glossary
CDMA
- Code Division Multiple Access
CMOS
- Complementary Metal-Oxide-Semiconductor
CORBA
- Common Object Request Broker Architecture
DCN
- Data Communications Network
DDN
- Digital Data Network
EMS
- Network Element Management System
ERT
- Embedded Remote Terminal
FDD
- Frequency Division Duplex
FTP
- File Transfer Protocol
GSM
- Global System for Mobile Communication
GUI
- Graphical User Interface
HA
- High Availability
HDSL
- High-data-rate Digital Subscriber Line
IETF
- Internet Engineering Task Force
IP
- Internet Protocol
ITU-T
- International Telecommunication Union - Telecommunication Standardization
Sector
J2EE
- JAVA 2 platform Enterprise Edition
V
LAN
- Local Area Network
LDAP
- Lightweight Directory Access Protocol
LTE
- Long Term Evolution
MIB
- Management Information Base
MML
- Man Machine Language
NE
- Network Element
NM
- Network Management
NMF
- Network Management Function
NMS
- Network Management System
NTP
- Network Time Protocol
OMM
- Operation & Maintenance Module
OSS
- Operation Support System
PC
- Personal Computer
RFC
- Request For Comments
SFTP
- Secure File Transfer Protocol
SLA
- Service Level Agreement
SMI
- Structure of Management Information
SNMP
- Simple Network Management Protocol
SSH
- Secure Shell
VI
Glossary
TCP
- Transfer Control Protocol
TD-SCDMA
- Time Division-Synchronization Code Division Multiple Access
TDD
- Time Division Duplex
TMF
- Telecommunication Management Forum
TMN
- Telecommunications Management Network
UDP
- User Datagram Protocol
UMTS
- Universal Mobile Telecommunication System
WAN
- Wide Area Network
WiMAX
- Worldwide Interoperability for Microwave Access
VII

SJ-20110823134613-002-NetNumen U31 R18 (V12.10.040) Product Description

Uploaded by

Document Information

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

SJ-20110823134613-002-NetNumen U31 R18 (V12.10.040) Product Description

Uploaded by

Copyright:

Available Formats

NetNumen U31 R18

Unified Element Management System

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

Updates Section 4.1.1, Server Hardware Configuration

Updates Section 6.2, Fault Alarm Management

Updates Section 6.3, Performance Management

Serial Number: SJ-20110823134613-002

Chapter 2 System Features ....................................................................... 2-1

Chapter 3 System Structure ...................................................................... 3-1

Chapter 4 Configuration Requirements ................................................... 4-1

Chapter 5 System Principles ..................................................................... 5-1

Chapter 6 Product Functions .................................................................... 6-1

6.5 Log Management ............................................................................................... 6-9

Chapter 7 Interfaces and Protocols .......................................................... 7-1

Chapter 8 Networking Modes .................................................................... 8-1

Chapter 9 Environment Requirements ..................................................... 9-1

About This Manual

As an object-oriented system designed on the J2EE platform, NetNumen U31 provides

What Is in This Manual

Chapter 1, System Overview

Describes the background, functions, and standards followed in the

Chapter 2, System Features

Describes the features of the NetNumen U31 system.

Chapter 3, System Structure

Describes the hardware and software structure of the NetNumen

Describes the configuration requirements for the server and client

Chapter 5, System Principles

Describes the working principle, remote client principal, and

Chapter 6, Product Functions

Describes the functions of each module in the NetNumen U31

Chapter 7, Interfaces and

Describes the internal interfaces and external interfaces provided by

the NetNumen U31 system and related protocols.

Describes the networking modes of the NetNumen U31 system,

including local networking, remote networking, and remote client

Describes the working environment requirements of the NetNumen

Centralized topology management

ZTE Proprietary and Confidential

NetNumen U31 R18 Product Description

1.3 Standards Followed

ZTE Proprietary and Confidential

Chapter 1 System Overview

ITU-T M.3000, Overview of TMN recommendations

RFC1157, Simple Network Management Protocol

GB901, A Service management Business Process Model

ZTE Proprietary and Confidential

NetNumen U31 R18 Product Description

GB914, System Integration Map

Interworking Between CORBA and TMN System Specification V1.0

Ministry of Information Industry and China Telecom

YD/T 852-1996 Telecom Management Network (TMN) General Design Principle

ZTE Proprietary and Confidential

2.1 Conformity to Standards

2.2 Integrated Network Management

2.3 System Expansion

2.4 System Openness

ZTE Proprietary and Confidential

NetNumen U31 R18 Product Description

NetNumen U31 supports standard CORBA, SNMP, and FTP/SFTP northbound

2.5 System Reliability

NetNumen U31 supports in-band management and out-of-band management. In the

2.6 System Operation Security

Complete access rights control