mw_ss31_e1_0 netnumen u31 system description

NetNumen U31System Description

ZTE UNIVERSITYZTE University, DameishaYanTian District, Shenzhen,P. R. China518083Tel: (86) 755 26778800Fax: (86) 755 26778999URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright © 2010 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-RATION 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 CORPORATIONor of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter 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.

Publishing Date (MONTH/DATE/YEAR) : 03/07/2011

Content

NetNumen U31 System Description.............................. 1

1 System Overview....................................................... 21.1 System Background ............................................................... 2

1.2 System Function.................................................................... 3

1.3 Physical Architecture.............................................................. 4

1.4 System Features ................................................................... 5

1.4.1 Standard Compliance..................................................... 5

1.4.2 Comprehensive Network Management Capability ............... 5

1.4.3 Remote Management Capability ...................................... 6

1.4.4 Modularized Design ....................................................... 6

1.4.5 System Openness.......................................................... 6

1.4.6 System Reliability.......................................................... 6

1.4.7 Operation Security ........................................................ 7

1.4.8 Ease of Use .................................................................. 7

1.4.9 Data Security................................................................ 7

1.5 Compliant Standards.............................................................. 8

2 System Architecture ................................................ 112.1 Hardware Architecture...........................................................11

2.2 Software Architecture............................................................12

3 Configuration Requirements.................................... 153.1 Requirements for the Server Configuration...............................15

3.1.1 Configuration Solutions .................................................15

3.1.2 Hardware Configuration of the Server .............................16

3.1.3 Software Configuration of the Server ..............................17

3.2 Requirements for the Client Configuration ................................18

3.2.1 Hardware Configuration of the Client...............................18

3.2.2 Software Configuration of the Client................................18

4 System Principles .................................................... 194.1 Layered Software Model ........................................................19

4.2 Remote Client ......................................................................20

5 Management Functions ........................................... 23

5.1 Topology Management...........................................................23

5.2 Fault Management ................................................................25

5.3 Performance Management .....................................................27

5.4 Security Management ...........................................................28

5.5 Configuration Management ....................................................30

5.6 Software Management ..........................................................31

5.7 Log Management..................................................................32

5.8 Report Management..............................................................32

5.9 Database Management..........................................................32

5.10 Inventory Management........................................................33

5.11 License Management...........................................................33

6 Technical Specifications .......................................... 356.1 Performance Specifications ....................................................35

6.2 Interface Specifications .........................................................35

7 Interfaces and Protocols ......................................... 377.1 Interfaces............................................................................37

7.1.1 Logical Interfaces .........................................................37

7.1.2 Physical Interfaces .......................................................37

7.2 Protocols .............................................................................38

7.2.1 CORBA........................................................................38

7.2.2 IIOP Protocol Stack ......................................................38

7.2.3 FTP Protocol Stack........................................................39

7.2.4 TELNET Protocol Stack ..................................................39

7.2.5 SNMP Protocol .............................................................40

8 Networking Modes................................................... 438.1 Non-Cascade Networking Modes .............................................43

8.1.1 Non-Cascade Local Networking.......................................43

8.1.2 Non-Cascade Remote Networking ...................................44

8.1.3 Non-Cascade Integrated Networking ...............................48

8.2 Cascade Networking Modes....................................................48

8.2.1 Local Cascade Networking .............................................48

8.2.2 Remote Cascade Networking..........................................49

8.3 Distributed System ...............................................................50

Glossary ..................................................................... 55

NetNumen U31System DescriptionAfter you have completed this course, you

will be able to:

>> Know the structure and principle ofNetNumen U31

>> Know the system features and functionmoudles of NetNumen U31

Confidential and Proprietary Information of ZTE CORPORATION 1

NetNumen U31 System Description

Chapter1 System Overview

After you have completed this chapter, you will know:

>> System Background>> System Function>> Physical Architecture>> System Features>> Compliant Standards

1.1 System BackgroundSince 1985, ITU-T has defined a suite of recommendations forTelecommunications Management Network (TMN). As a specialnetwork independent of telecommunications networks, TMNsupports the management requirements of operators to operate,manage, and maintain telecommunications networks and servicesin a standard, simple, and automatic way.

TMN provides an organized network architecture based on a uni-fied framework with standard interfaces, in which different operat-ing systems can be connected to telecommunications equipmentto provide various management functions for telecommunicationsnetworks. The scale of a TMN depends on the scale of the telecom-munications network to be managed. TMN supports the inter-op-eration of different operating systems. It can receive the infor-mation from managed telecommunication networks via differentinterfaces, and control the operation of these telecommunicationsnetworks.

TMN, as specified in ITU-T recommendations, is logically dividedinto four layers, as illustrated in Figure 1.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 System Overview

FIGURE 1 LOGICALLY LAYERED ARCHITECTURE OF TMN

� Element Management Layer (EML)

The EML provides the operation and management functionsacting upon individual network elements (NEs) for operatorsand maintenance personnel of telecommunications equipment.

� Network Management Layer (NML)

The NML provides the functions acting on various NEs in thewhole network for organizers and managers of telecommuni-cations networks.

� Service Management Layer (SML)

The SML provides the management functions acting upon cus-tomer data or service-level data for service providers, for ex-ample, service provisioning, service control and monitoring,and service billing.

� Business Management Layer (BML)

The BML provides the management functions acting upon cor-poration-wide data for decision-makers of telecommunicationscorporations. In addition, TMN provides a series of modular-ized management functions in the management functional ar-eas, including performance management, configuration man-agement, accounting management, fault management, andsecurity management.

The NetNumen U31 system is an Element Management System(EMS) designed in compliance with TMN recommendations.

1.2 System FunctionThe NetNumen U31 system provides the management functionssupporting routine operation and maintenance of microwavenetwork elements, for example, topology management functions,performance management functions, and fault managementfunctions. It supports the centralized and unified management



of ZTE's microwave transmission equipment and authorizedmicrowave equipment provided by other vendors. In addition,the NetNumen U31 system can connect to upper-layer applica-tions, such as a Network Management System (NMS), via unifiedinterfaces.

1.3 Physical ArchitectureThe NetNumen U31 system is designed in compliance with therecommendations for Telecommunications Management Network(TMN) specified by ITU-T. It is a fault tolerant system that can beflexibly expanded and conveniently transplanted.

Figure 2 illustrates the client/server architecture of a distributedNetNumen U31 system.

FIGURE 2 DISTRIBUTED NETNUMEN U31 SYSTEM

As shown in Figure 2, the NetNumen U31 server connects to themanaged network elements directly. It can also connect to net-work elements via TCP/IP, X.25, or DDN. The server gets accessto the database and read/write information from/to the databasevia internal interfaces.

The NetNumen U31 system connects to network elements viasouthbound interfaces, for example, MML, FTP, Socket, CORBA,and SNMP interfaces. It can also connect to an upper-layerNetwork Management System (NMS) via northbound interfaces,for example, CORBA, database, SNMP, and File interfaces.

Figure 3 illustrates the positions of southbound and northboundinterfaces in a network management system.



FIGURE 3 SOUTHBOUND INTERFACES AND NORTHBOUND INTERFACES

1.4 System Features

1.4.1 Standard Compliance

The NetNumen U31 system strictly complies with TMN series rec-ommendations specified by ITU-T and RFC standards related tonetwork management.

For the list of compliant recommendations and standards, refer tothe later section “Compliant Standards” in Chapter 1.

1.4.2 Comprehensive NetworkManagement Capability

The NetNumen U31 system has a comprehensive network man-agement capability. It can manage various microwave transmis-sion equipment, including microwave equipment provided by ZTEand authorized microwave equipment provided by other vendors.In addition, the NetNumen U31 system covers both the networkelement management layer and the network management layer.It provides comprehensive network management functions.



1.4.3 Remote Management Capability

The NetNumen U31 system adopts a reliable security controlmechanism. By connecting a remote client to the system, youcan monitor and manage the network at any place.

1.4.4 Modularized Design

The NetNumen U31 system can easily meet the requirements formanaging new devices and services due to its modularized archi-tecture. The system software consists of several modules, whichcan be distributed on different computers. The distributed deploy-ment of software modules provides the processing capability of thesystem.

1.4.5 System Openness

The NetNumen U31 system adopts the following technologies tosupport its openness.

� Standard CORBA and XML Interfaces

The use of CORBA and XML interfaces enables the system toshare both data and services with other service systems.

� JAVA

The use of JAVA enables the system to run on either UNIXor Linux operating system for managing networks of differentscales.

� Various External Interfaces

The use of various external interfaces, such as IBM Netcoolinterface, enables the system to receive alarm data.

1.4.6 System Reliability

The NetNumen U31 system has a high reliability due to the follow-ing features:

� Outband and Inband Management Modes

� In the case of outband management, network managementdata and service data is transferred over different chan-nels. In addition, the outband management supports dualbackup of the channels. You can choose the outband man-agement mode if the actual environment requires a higherreliability.

� In the case of inband management, network managementdata and service data is transferred over the same channel.

� Perfect System Monitoring Capability



By monitoring the running status of the system conveniently,you can troubleshoot potential problems of the system to en-sure its reliability.

1.4.7 Operation Security

The NetNumen U31 system uses the access right control and logrecords to ensure the security of operations on it.

� Access Right Control

You can constrain the operation right of a user based on theview of a controlled network, that is, the operations performedby the user are limited to certain network elements with a cer-tain granularity.

� Complete Log Records

By observing the log records, you can find unauthorized op-erations in time to ensure the security of the system and themanaged network.

1.4.8 Ease of Use

By using the topology navigation function on the NetNumen U31system, you can perform network management operations easilyin an intuitive way, for example, monitor the running status of themanaged network on the topological graph of the network.

The topological graph has different levels, for example, globaltopology and local topology. The alarm information in the wholenetwork can be displayed on the topological graph or rack mapin real time. The system provides different audible and visualalarm indications according to the severity of alarms. In addition,the system supports the centralized management of performancedata in the whole network for convenient query, statistics, andreport.

1.4.9 Data Security

The NetNumen U31 system adopts database backup and disk mir-roring to ensure the security of data in the system.

� Database Backup

The system provides diversified backup modes by supportingthe storage of data on another peripheral memory, such asdisk, tape, compact disk, or database. You can restore thedata backup on the peripheral memory to the system whennecessary.

� Disk Mirroring

When data mirroring is used, all data on the active disk is repli-cated to the standby disk in real time for backup.



1.5 Compliant StandardsNetNumen U31 complies with the following recommendations andstandards.

� ITU-T Recommendations

� ITU-T M.3000, Overview of TMN recommendations

� ITU-T M.3010, Principles for a Telecommunications man-agement 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 Statementsfor the Generic Network Information Model

� ITU-T M.3200, TMN management services and telecommu-nications 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 draftdocument on IP access network architecture

� ITU-T X.701-X.709, Systems Management framework andarchitecture

� ITU-T X.710-X.719, Management Communication Serviceand Protocol

� ITU-T X.720-X.729, Structure of Management Information

� ITU-T X.730-X.799, Management functions

� RFC Standards

� RFC1157, Simple Network Management Protocol

� RFC1213, Management Information Base for Network Man-agement of TCP/IP based internets: MIB-II

� RFC1901, Introduction to Community-based SNMPv2

� RFC1902, Structure of Management Information for Ver-sion 2 of the Simple Network Management Protocol (SN-MPv2)

� RFC1903, Textual Conventions for Version 2 of the SimpleNetwork Management Protocol (SNMPv2)

� RFC1905, Protocol Operations for Version 2 of the SimpleNetwork 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 AttributeSyntaxes

� RFC1959, An LDAP URL Format



� RFC2251, Lightweight Directory Access Protocol (v3)

� TMF Standards

� GB901, A Service management Business Process Model

� GB921, Enhanced Telecom Operations Map

� GB909, Generic Requirements for TelecommunicationsManagement Building Blocks

� GB908, Network Management Detailed Operations Map

� GB914, System Integration Map

� GB917, SLA Management Handbook V1.5

� NMF038, Bandwidth Management Ensemble V1.0

� TMF508, Connection and Service Management InformationModel Business Agreement

� TMF801, Plug and Play Service Fulfillment Phase 2 Valida-tion Specification V1.0

� TMF605, Connection and Service Management InformationModel

� NMF037, Sub-System Alarm Surveillance Ensemble V1.0

� OMG Standards

� Interworking Between CORBA and TMN System Specifica-tion V1.0

� Specifications by Ministry of Information Industry andChina Telecom

� YD/T 852-1996 General Principles for the Design ofTelecommunications Management Network (TMN)

� YD/T 871-1996 Generic Information Model of Telecommu-nications Management Network (TMN)



This page is intentionally blank.


Chapter2 System Architecture


>> Hardware Architecture>> Software Architecture

2.1 Hardware ArchitectureThe NetNumen U31 system adopts a client/server architecture.The client in the system communicates with the server via TCP/IP.

The hardware configuration of the system depends on the scale ofthe network to be managed and the system load. Generally, a highconfiguration Sun-series workstation is used as the NetNumen U31server because the server runs all core functional modules of thesystem, stores and maintains massive network management data.The configuration of the NetNumen U31 client is relatively lowerbecause the task of the client is connecting the server and display-ing the operation results. A personal computer (PC) can be usedas the client of the system.

In terms of logical structure, two types of devices are deployed atthe server: host and storage device.

� The host is the physical foundation of the NetNumen U31 sys-tem. It processes data in the system. The system performancegreatly depends on the processor speed of the host.

� Storage devices are used to save the data in the system. Forstoring large amounts of important data in the system, exter-nal data storage devices with high capacity and reliability arerequired besides the built-in disks in the host.

In terms of function, a server cluster, including application server,database server, and File Transfer Protocol (FTP) server, can bedeployed at the server. These servers can be configured togetheron the same host, or independently on different hosts.

To ensure high availability and security, dual servers can be usedin the NetNumen U31 system, as shown in Figure 4.



FIGURE 4 DUAL-SERVER NETNUMEN U31 SYSTEM

As shown in Figure 4, the dual-server NetNumen U31 systemadopts the Veritas Cluster solution to monitor the active andstandby servers and implement the switching between them. Thedisk array keeps the consistency of the data between two serversvia two routes.

When the active server fails, the Veritas Cluster System, whichmonitors the heartbeat between dual servers, detects the failure.Then the Veritas Cluster System switches the NetNumen U31 sys-tem to the standby server for providing continuous network man-agement services. The standby server can be deployed in a cityfar away from the active server to ensure the data security in thecase of natural or artificial disasters.

2.2 Software ArchitectureObject-oriented technologies are adopted to design the NetNumenU31 software based on JAVA 2 platform Enterprise Edition (J2EE).The software modules can be deployed in an integrated or distrib-ute way to manage microwave network elements (NEs).

In addition, the NetNumen U31 software provides CORBA, SNMP,DB and File interfaces for connecting the NetNumen U31 systemto a Network Management System (NMS) or Operation SupportSystem (OSS).


Chapter 2 System Architecture

By using the NetNumen U31 software, you can configure and main-tain individual microwave network elements, and implement theintegrated monitoring and maintenance of all network elementsfrom the network management point of view.

The NetNumen U31 system provides two software: server soft-ware and client software.

� Server Software

The server software can be divided into several modules, eachof them implementing certain functions. Table 1 lists thesemodules and describes their functions.

TABLE 1 SERVER SOFTWARE MODULES

Module Function

Networkmanagementinterface module

Provides northbound access function (NAF)to support the connection to a networkmanagement system (NMS) via northboundinterface.

Topologymanagement module

Provides topology management functions,that is, the management of topologyobjects.

Fault managementmodule

Provides fault management functions, suchas alarm collection, alarm query, and alarmprocessing.

Performancemanagement module

Provides performance managementfunctions, such as the collection of NEperformance data, real-time performancemonitoring, and the report of thresholdcrossing alarms.

Securitymanagement module

Provides security functions, such as themanagement of user rights and usergroups.

Configurationmanagement module

Provides configuration managementfunctions, such as the configuration of NEs,and the query of configuration data.

Softwaremanagement module

Provides software management functions,such as the query of software version,software upgrade, activation anddeactivation of the software.

Log managementmodule

Provides report management functions,such as the management of systemreports, user logs, and NE logs.

Report managementmodule

Provides a report tool that can be used tocustomize specific reports.

Databasemanagement module

Supports the management of Oracledatabase, including database backup,restoration, and monitoring.



Module Function

Inventorymanagement module

Supports the addition, deletion,modification, query, synchronization,import and export of NE inventory data.

NE adaptationmodule

Acts as an adapter for connecting variousNEs to the software.

� Client Software

The client software provides a graphic user interface (GUI).After connecting to the NetNumen U31 server,

the client can display the results of management operations inthe system. On the GUI, you can operate and maintain theNEs managed by the system.


Chapter3 ConfigurationRequirements


>> Requirements for the Server Configuration>> Requirements for the Client Configuration

3.1 Requirements for the ServerConfiguration

3.1.1 Configuration Solutions

The NetNumen U31 system has a client/server architecture. ASun-series workstation is generally used as the NetNumen U31server. As the core of the system, the server provides the followingtwo types of services.

� Database Services

The server uses a commercial database software, Oracle Data-base 10g, to provide database access and storage services.

� Application Services

The application services provided by the server include perfor-mance management, fault management, configuration man-agement, security management, topology management, andsystem management services. The server implements basicnetwork management functions, and accomplishes the man-agement and analysis of the NetNumen U31 system itself.

Two solutions are available to configure the server in the NetNu-men U31 system: integrated configuration, and dual-server con-figuration for hot backup.

� Integrated Configuration

The integrated configuration solution is a simple solution thatintegrates the database services and the application serviceson the same server. It is low-cost but less reliable. However, aRedundant Array of Independent Disks (RAID) scheme (RAID1or RAID5) can be used to improve the server reliability.

� Dual-Server Configuration for Hot Backup

In the dual-server configuration solution, two servers providingthe same services are used. One acts as the primary server,and the other acts as the standby one. The primary server,also called active server, provides application services whenthe system runs properly. The standby server monitors the



working status of the primary one. And at the same time, theprimary server checks whether the standby server is workingproperly. If the primary server fails to provide the applications,the standby server takes over the primary one to provide keyapplication services and ensure the continuous running of thesystem.

To achieve a high reliability of the system, the dual-server con-figuration solution also supports the hot backup of data. Thedata in the database is stored in an RAID storage device. Whenthe primary server fails, the standby server takes over the pri-mary server and accesses the data in the RAID.

Figure 5 illustrates a dual-server NetNumen U31 system forexample.

FIGURE 5 DUAL-SERVER CONFIGURATION SOLUTION FOR HOT BACKUP

3.1.2 Hardware Configuration of theServer

In actual applications, the hardware configuration of the NetNu-men U31 server depends on the scale of the network to be man-aged by it. To be specific, the hardware configuration depends onthe quantity of microwave network elements (NEs) to be managed.

Table 2 lists the typical hardware configuration of the server in asingle-server NetNumen U31 system.


Chapter 3 Configuration Requirements

TABLE 2 HARDWARE CONFIGURATION OF THE SERVER (SINGLE-SERVERSYSTEM)

NetworkScale

ServerModel

Quantity Configuration

512 NEs Sun T5220 1 � CPU: 4 Core 1.2 GHz� Memory: 16 GB (8*2 GB)� Internal disk drives: 2*146

GB (SAS 10K 2.5")


GB (SAS 10K 2.5")� External disk drives:

2*146 GB (SESX3C11Z)



4*146 GB (SESX3C11Z)



6*146 G (SESX3C11Z)

Table 3 lists the typical hardware configuration of the server in adual-server NetNumen U31 system.

TABLE 3 HARDWARE CONFIGURATION OF THE SERVER (DUAL-SERVERSYSTEM)

NetworkScale

ServerModel

Quantity Configuration


GB (SAS 10K 2.5")


GB (SAS 10K 2.5")

3.1.3 Software Configuration of theServer

Table 4 lists the software that is required on the NetNumen U31server.



TABLE 4 SOFTWARE CONFIGURATION OF THE SERVER

Software Configuration

Operating system Solaris 10

Database Oracle Database 10g for SunSolaris

Disaster recovery software Veritas

3.2 Requirements for the ClientConfiguration

3.2.1 Hardware Configuration of theClient

A Personal Computer (PC) can be used as the NetNumen U31client. Table 5 lists the minimal hardware configuration of the clientcomputer.

TABLE 5 HARDWARE CONFIGURATION OF THE CLIENT

Hardware Configuration

CPU PentiumIV 2.6 GB

Memory 1 GB

Internal hard disk 80 GB

Disk array None

3.2.2 Software Configuration of theClient

Table 6 lists the software that is required on the client computer.

TABLE 6 SOFTWARE CONFIGURATION OF THE CLIENT

Software Configuration

Operating system Microsoft Windows 2000 Professional, orWindowsXP

Browser Netscape, or Internet Explorer 6.0 or later

Document viewer Microsoft Office 2000 or later

Antivirus software Mcafee VirusScan8.5, Norton, or Trend


Chapter4 System Principles


>> Layered Software Model>> Remote Client

4.1 Layered Software ModelThe layered model of the NetNumen U31 system software is illus-trated in Figure 6.

FIGURE 6 LAYERED SOFTWARE MODEL OF NETNUMEN U31

The NetNumen U31 system software can be divided into threelayers: Platform Support Layer (PSL), Platform Framework Layer(PFL), and Platform Application Layer (PAL).

� Platform Support Layer (PSL)



The platform support layer provides all necessary underlyingfunctions for supporting a large-scale distributed system.These functions can be used not only in the network manage-ment system, but also all kinds of distributed managementsystems in theory. The platform support layer provides thefollowing applications and functions:

� J2EE application server

� Extended functions of J2EE application server

� TMN standard protocol stack

� Common development kits

� Platform Framework Layer (PFL)

Some common software frameworks are specially extracted forthe application of the network management system. All thesesoftware frameworks form the platform framework layer. Allmanagement applications are developed on the basis of all orpart frameworks on this layer.

� Platform Application Layer (PAL)

The platform application layer provides specific managementapplications based on the platform framework layer. Theseapplications are demountable. The needed management ap-plications can be loaded to the network management platformas required.

Due to this distributed and scalable system architecture, the net-work management system can provides a diversity of functionalmodules according to the actual management requirements.

4.2 Remote ClientRemote client, also called remote terminal or embedded remoteterminal (ERT), is a client deployed in an area far away from theNetNumen U31 server. It is used to display the data in the NetNu-men U31 system at a distant place, as shown in Figure 7.


Chapter 4 System Principles

FIGURE 7 LOCATIONS OF REMOTE CLIENTS

The following explains the working principle illustrated in Figure 7.

� The NetNumen U31 server collects data from the managed NEsand processes the collected data.

� The local NetNumen U31 clients show the collected and pro-cessed data on a graphic user interface.

� The NetNumen U31 remote clients select and display specificnetwork management information collected via TCP/IP.

To ensure the network security, a remote client only supports theoperations on the resource data in the area where it is located.


Chapter5 Management Functions


>> Topology Management>> Fault Management>> Performance Management>> Security Management>> Configuration Management>> Software Management>> Log Management>> Report Management>> Database Management>> Inventory Management>> License Management

5.1 Topology ManagementThe NetNumen U31 system is required to support the centralizedmanagement and group management of all the managed devicesdue to the large quantity and diversity of managed devices. Thetopology management module of the NetNumen U31 system pro-vides various topology management functions to display the dis-tribution and organization of devices on topology views.

A topology view is divided into two parts: the navigation pane onthe left part, and the topology map on the right part. The nav-igation pane provides an network element tree that lists all themanaged network elements (NEs) in the system. The topologymap shows the managed NEs on a map according to their loca-tions and relations in the network. In addition, some alarm andconfiguration information of NEs is also available on the topologyview.

The following lists the topology management functions that youcan use in the NetNumen U31 system.

� Navigation

The NEs added in the system are listed on an NE tree in thenavigation pane, corresponding to the NE icons displayed onthe topology map. When you add or delete an NE via short-cut menu on the NE tree, corresponding NE icon appears ordisappears on the topology map at the same time. You canlocate corresponding NE icon on the topology map by clickingthe NE on the NE tree. Besides some topology managementfunctions, the NE tree also provides the access to some othermanagement functions via shortcut menu, including configura-



tion management, fault management, and performance man-agement functions.

� Graphic Display

The topology map shows all NEs managed by the system aswell as their relations in the network. You can search for spe-cific NEs on the topology map, lock some NEs to prevent themfrom being deleted by other users, and view the statistical in-formation of the NEs in the system, including NE quantity, linkquantity, group quantity, and alarm information.

� Display of NEs and Links

NEs and links between NEs that have connection relations aredisplayed on the topology map. You can set the attributes ofan NE to determine whether to show its peripheral device.

� Topology Map Control

On the topology map, you can do the following operations.

� Drag, zoom in, and zoom out the topology map.

� Go to, back to, and forward to a specific NE or topologylayer.

� Search for specific NEs.

� Change the background of the topology map.

� Synchronize the configuration information of NEs on thetopology map from the server and refresh the display onthe client without changing the positions and connectionrelations of those NEs.

� Select the layout mode of NE icons on the topology map,including hierarchical layout, tree layout, radial tree layout,spring embedded layout, and uniform length edges layout.

� Filtered Display

On the topology map, you can set filtering conditions to filterthe NEs or links that you do not concern from the topologymap. The filter conditions can be NE name, group name, IPaddress, link name, NE type, link type, and/or group type.

� Authorization-Based Data Display

To ensure the system security, the system only provides topol-ogy management functions to authorized users.

� Alarm Display

On the topology map, an NE or link is highlighted in differentcolors when some fault(s) occur in it according to the faultseverity and the acknowledgement status of correspondingalarm(s).

� Group-Based View

To manage NEs more effectively, you can group NEs based oncertain rules. Then the topology map can arrange the NEs bygroup.


Chapter 5 Management Functions

5.2 Fault ManagementThe fault management module of the NetNumen U31 system pro-vides fault management functions for monitoring and processingthe fault information in the managed network. It monitors the run-ning status of equipment in the network and collects alarm datain real time. Once a fault occurs, the system notifies operationand maintenance personnel of the fault in the format of alarm ornotification, who can quickly locate the fault and take measures toremove the fault by analyzing the alarm or notification message.

The following lists the fault management functions that you canuse in the NetNumen U31 system.

� Alarm Data Collection and Storage

The system collects alarm information sent by the managedNEs in real time, converts the format of the alarm informationas required, and then store all the alarm information in thedatabase. In addition, the fault management module can au-tomatically save the alarm information into files according topreset parameters.

� Graphic Display and Localization of Alarms

The system monitors the managed NEs in real time and dis-plays the received alarm information on the client screen. Onthe topology map, you can open the rack diagram of a faultyNE to locate the module where an alarm is generated.

� Alarm Acknowledging and Unacknowledging

When an alarm is reported and displayed on the client screen,you can acknowledge the alarm. The system saves the recordof your acknowledging operation. You can also cancel theacknowledgement of an alarm, that is, unacknowledge thealarm. All acknowledging and unacknowledging operations arerecorded, including the information of the users performingthe operations as well as the operation time.

By observing the acknowledgement status of alarms, you canknow the running status of the network, find the latest alarminformation quickly, and process the alarms respectively ac-cording to their acknowledgement status.

� Real-Time Alarm Monitoring

The system shows real-time alarms in the form of list on theclient screen. In the alarm list, you can filter alarms by occur-rence time or severity level. When the system receives newalarms from managed NEs, it refreshes the alarm list auto-matically.

� Alarm Clearing

The system automatically clears an alarm from the activealarm list after the fault causing this alarm is removed. Thecleared alarm becomes a history alarm and the acknowledge-ment status turns into “Acknowledged” no matter whether itis acknowledged before being cleared. You can also clear analarm forcibly from the active alarm list even if correspondingfault is not removed.

� Alarm Synchronization



Alarm synchronization includes the synchronization of alarminformation between the NetNumen U31 server and the man-aged NEs (that is, the alarm sources), and the synchronizationof alarm information between the NetNumen U31 client andthe server.

NetNumen U31 supports two alarm synchronization modes:manual synchronization and automatic synchronization.

� In the manual synchronization mode, the alarm synchro-nization is initiated by a user.

� In the automatic synchronization mode, the alarm synchro-nization is initiated by the system.

The system initiates an alarm synchronization process in thefollowing situations.

� The broken connection between the client and the serverrecovers.

� The broken connection between the server and a managedNE in the network recovers.

� The server is restarted.

� A scheduled alarm synchronization task is defined and thepreset start time is up.

� Output of Alarm Data

All alarm information can be output to *.txt, *.xls, *.pdf,*.html, or *.csv files.

� Alarm Rule Management

The system supports the customization of various alarm rulesfor managing and processing received alarms, such as alarmstorage, alarm filtering, alarm reclassification, and alarm cor-relation.

For example, by creating an alarm filtering rule, you can filterless important alarms and therefore reduce the count of alarmsdisplayed on the client screen. In this way, you can easily findcritical alarms and handle them first.

A fault in an NE may cause several correlated alarms. Bysetting a correlation rule, you can collapse a series of corre-lated alarms caused by the same fault and therefore reducethe count of alarms displayed on the client screen.

� Modification of Alarm Settings

This function allows you to define the alarm managementmode, reset the indication colors of alarms, and set the thresh-olds of environment parameters, for example, temperature,humidity, and smog existence.

� Alarm Query and Statistic

The alarm query and statistic function enables you to queryalarms stored in the database and get a statistic report of thesealarms. By analyzing the alarm report, you can find problemsin the network and improve the network performance by re-moving those problems. For example, you can query historyalarms, active alarms and notifications.

In addition, the system can count alarms according to theirtypes and severity levels, and indicate the distribution of dif-



ferent alarms by displaying the statistic information in variouschart forms.

� Event (Notification) Management

A notification is sent to the system when a transient fault orevent occurs in a managed NE. By using the event manage-ment function, you can analyze the cause of notifications andfind potential problems in the network.

5.3 Performance ManagementThe purpose of performance management is to improve the net-work performance and efficiency and provide a basis as well assuggestions for proper planning of network resources. The per-formance management module of the NetNumen U31 system cancollect the performance data of network elements in the network.By observing and analyzing the collected performance data, youcan know the running status of equipment in the network, evalu-ate the efficiency of equipment and the network, and monitor thequality of service in the network.

The following lists the performance management functions thatyou can use in the NetNumen U31 system.

� Performance Data Query

You can query raw performance data stored in the databaseafter setting the query conditions, for example, NE type, timeperiod and performance object. The query result is displayedin a list. You can print the query result or save it as a file.

� Performance Data Synchronization

The system can automatically synchronize performance datafrom the managed NEs to the server, and synchronize perfor-mance data from the server to the client. You can also initiatethe synchronization of performance data via a client.

� Performance Report

The system can generate a performance data statistic reportto show current KPIs, which can also be output as *.xls, *.pdf,*.html, and *.txt files. A predefined template or user-definedtemplate can be used to generate the report you want.

In addition, you can create a report task by specifying the re-port type, template, object, time, and file name. When thepreset is up, the system generates the customized report ac-cording to the task. The customized task is stored in the data-base, which can be queried, modified and deleted. After thereport is generated by the system, you can view the report andsave it as an *.xls file.

The system can send the periodically-generated report to auser in the specified format via E-mail as required.



5.4 Security ManagementThe security management module of the NetNumen U31 systemprovides security management functions to ensure that only au-thorized users can access and manage network resources.

For better understanding of security management, the followingexplains some basic concepts related to security management, in-cluding role, role set, department, and user.

� Role

A role specifies the management permission for a user group,including the operation permission and manageable resources.

� The operation permission allows the user group to use spe-cific functional modules of the network management sys-tem. For example, if a role has the operation permission ofthe log management module, the users acting as the rolecan perform log management operations, such as queryinglogs and maintaining logs.

� The manageable resources refer to subnetworks and/ornetwork elements that can be managed by the role.

� Role Set

A role set is a set of roles. The management permission of arole set involves the management permissions of all roles inthe role set.

� Department

Departments are specified in the network management sys-tem to simulate the actual administrative departments. In thisway, the system administrator can conveniently organize andmanage users in the system. A newly-created user must be-long to a department.

� User

A user is an operator who is authorized to log in to the systemand perform operations in the system. While creating a user,the system administrator assigns the management permissionto the user by specifying a role or role set and allocates theuser to a department according to the actual situation.

Figure 8 illustrates the model of relations among user, role, roleset, department, operation permission, and manageable resourcesinvolved in the security management.



FIGURE 8 RELATION MODEL OF SECURITY MANAGEMENT

The following explains the relation model of security management.

� A user is administered by a department.

� The management permission of a user depends on the role setassigned to the user.

� A role set includes one role or a set of roles. Correspondingly,the management permission of a role set is the collection ofmanagement permissions of all roles in the role set.

� The management permission of a role depends on the oper-ation permission and manageable resources specified for therole.

The NetNumen U31 system provides the following security man-agement functions.

� Security Event Recording

The system can record security events, for example, authenti-cation failure, locking a user, and disabling a user. The systemadministrator can know the situation of user accounts in thesystem by observing the security event log.

� Reporting of Security-Related Alarms



The system can report alarms to the administrator when someimportant security events occur, for example, a user accountis locked.

� Setting of Login Time Period

By using the security management module, you can set a limitof the time period for a user. The user is allowed to log in tothe system only in this period.

� User Account Management

A user can query and change its password, policy, locking rule,and validity period. For example, you can specify a rule likethis: if a user enters the wrong password three times, the useraccount will be locked for the purpose of preventing unautho-rized login.

� Login User Management

� Forcible Removal of Users

The super administrator of the system can remove a userfrom the system forcibly to avoid unauthorized operationsperformed by this user and therefore ensure the systemsecurity.

� IP Address Setting of Super Administrator

You can set the IP address of the super administrator to ensurethe security of the super administrator account. After you setthe IP address, the super administrator can only log in to thesystem on the client with the same IP address as the presetone.

� User Password Modification

The super administrator of the system can change the pass-words of all the other users.

� User Status Check

If you log in to the system as a super administrator, you cancheck the locking status of other users, enable the automaticunlocking function of other users, and set the unlocking time.

� Locking of Clients

If no operation is performed for on a client a long time, thesystem will lock the client and force the login user on the clientto log out of the system. The user is required to log in to thesystem again before performing any operation in the system.

5.5 Configuration ManagementThe configuration management module of the NetNumen U31 sys-tem allows you to configure managed NEs in the system. It pro-vides the following configuration management functions.

� Data Configuration

On the client of the system, which provides a Graphic User In-terface (GUI), you can configure NEs to be managed by the sys-



tem, including the addition, deletion, modification, and queryof configuration data.

� Data Synchronization

The system supports both automatic and manual synchroniza-tion of configuration data. For example, the system can au-tomatically synchronize the configuration data from managedNEs to the server according to preset schedules. In addition,you can initiate a process to synchronize the configuration datafrom the server to the client you are using. All information re-lated to synchronization operations are recorded.

� Data Export

The configuration data can be exported and saved as *.xml,*.csv, or *.txt files.

� Data Import

You can import predefined configuration data from a file in spe-cific format into the system. The system will automaticallycheck the integrity and consistency of the imported data andcomplete the configuration of related NEs according to the im-ported data.

� Consistency Check

The system can check the consistency of configuration databetween the system and the managed NEs, and report thecheck result.

5.6 Software ManagementThe software management module of the NetNumen U31 systemallows you to manage the software packages and versions of mi-crowave equipment. It provides the following software manage-ment functions.

� Software Loading

In the system, you can conveniently load the software packageof new version to the managed microwave equipment.

� Version Management

The system can manage microwave equipment with differentsoftware versions. You can conveniently switch the version toanother for a equipment when necessary.

� Remote Installation and Upgrade

You can install a software package to the managed microwaveequipment or upgrade existing software remotely via the clientof the system. The remote operation improves the system reli-ability. If the upgrade fails, the system enables the equipmentto roll its software back to the previous one.



5.7 Log ManagementThe NetNumen U31 system provides three types of logs: operationlog, security log, and system log.

� Operation Log records operation information, including log ID,operation level, user name, operation name, host address,command function, operation details, operation result, causeof operation failure, connection mode, operation object, starttime, end time and related log.

� Security Log records login information, including log ID, username, host address, log name, operation time, access modeand details of the log.

� System Log records the completion state of time tasks on theserver, including log ID, level, source, log name, details, hostaddress, start time, end time, and related log.

The log management module of the NetNumen U31 system pro-vides the following log management functions.

� Log Query

You can set filtering conditions to query specific logs in thesystem, and save or print the query result.

� Log Backup

The system can back up the logs in the system as files accord-ing to the specified number of days or storage capacity.

� Log Deletion

You can delete unnecessary logs or logs that has been backedup.

5.8 Report ManagementThe NetNumen U31 system provides a special report tool, by whichyou can customize the report format according to the actual re-quirements.

The reports generated by the system can be displayed in tables,bar charts, charts, pie charts, and composite charts.

5.9 Database ManagementThe NetNumen U31 system provides powerful database manage-ment functions to ensure the security of the system database, in-cluding the backup, restoration, and monitoring of database.

The database management functions include:

� Database Monitoring

� Database Backup

� Offline Data Restoration



� Scheduled Backup

� Manual Backup

5.10 Inventory ManagementThe inventory management module of the NetNumen U31 systemprovides the following functions:

� Manual and Automatic Inventory Synchronization

The system supports both manual and automatic synchroniza-tion of inventory data from managed NEs to the server, includ-ing inventory ID, name, type, version, and date.

� Synchronization, Query and Deletion of Inventory

You can synchronize the inventory information from the serverto the client, query the inventory information via the client,and delete unnecessary inventory information.

� Prompt of Inventory Update

When some inventory information changes, corresponding NEprompts the update of the inventory information. After receiv-ing the prompt, the system updates the inventory informationstored in the database.

� Import and Export of Inventory

You can export the inventory information in the system into*.xml or *.pdf files, as well as import predefined inventoryinformation from an *.xml or *.pdf file to the system.

5.11 License ManagementThe purpose of license management is to control the managementauthorities of the NetNumen U31 system and NEs.

� System License Management

The license of the NetNumen U31 system limits the quantity ofnetwork elements that can be managed by the system. In thesystem, you can view the valid system license or update thecurrent license by importing a new license file.

� NE License Management

The NE license management module is separated from the con-figuration management module. It is used to enable or disablethe running of NEs via license. The NE license managementmodule supports the following functions.

� Importing NE license file

� Activating NE license

� Querying license information from the system or corre-sponding NE



� Configuring the capacity and ACM authority of each trans-mission unit in NEs according to license information

� Removing the NE license from the system

� Removing the NE license from corresponding NE


Chapter6 Technical Specifications


>> Performance Specifications>> Interface Specifications

6.1 Performance SpecificationsThe performance specifications of the NetNumen U31 system arelisted in Table 7

TABLE 7 PERFORMANCE SPECIFICATIONS

Item Specification

Maximum number of NEsthat can be managed by asingle server

10000

Maximum number ofconcurrent clients that canbe connected to a singleserver

100ManagementCapacity

Maximum number ofconcurrent users that log into the same server

40

Alarm processing capability

Average value: 100alarms per second

Peak value: 500 alarmsper second

Response time for alarmdisplay

≤ 2 seconds (from thetime when an alarm isreported to the systemto the time when thisalarm is displayed on theNetNumen U31 client)

ProcessingCapability

Response time forperformance processing

About 10 secondsfor storing 1000performance recordsto the database

6.2 Interface SpecificationsNetNumen U31 provides a diversity of interfaces, including:

� Communication interfaces between the NetNumen U31 systemand managed NEs, adopting TCP/IP.



� File transfer interfaces between the NetNumen U31 system andmanaged NEs, adopting FTP.

� Physical Interfaces

� 10M/100M adaptive Ethernet interfaces

� GE interface for connecting to Gigabit Ethernet

� X.25 interface for connecting to Packet Switched (PS) net-work


Chapter7 Interfaces and Protocols


>> Interfaces>> Protocols

7.1 Interfaces

7.1.1 Logical Interfaces

7.1.1.1 Internal Interfaces

The internal interfaces of the NetNumen U31 system refers to thecommunication interfaces between the server and the client. Theyadopt TCP/IP for communication. In the NetNumen U31 system,the server and the client communicate with each other via a LocalArea Network (LAN) or a Wide Area Network (WAN). The commu-nication bandwidth is equal to or greater than 2Mbps.

7.1.1.2 Southbound Interfaces

The southbound interfaces of the NetNumen U31 system refers tothe communication interfaces and file transfer interfaces betweenthe NetNumen U31 server and the managed NEs. These inter-faces adopts various communication protocols and specifications,including: TCP/IP, FTP, MML (EMB), Socket, CORBA, and SNMP. Inaddition, the southbound interfaces have the adaptation capabilityfor the conversion and transfer of data in different formats.

7.1.1.3 Northbound Interfaces

The northbound interfaces of the NetNumen U31 system are usedto connect the system to an upper-layer network managementsystem (NMS) of ZTE or another vendor. For detailed informationof NetNumen U31’s northbound interfaces, please refer to Appen-dix A, Northbound Interfaces in this manual.

7.1.2 Physical Interfaces

The physical interfaces provided by the NetNumen U31 system areintroduced in Table 8.



TABLE 8 PHYSICAL INTERFACES

Interface Type Description

10M/100M adaptiveEthernet interface Used to connect 10M/100M Ethernet

GE interface Used to connect a Gigabit Ethernet

X.25 interface Used to connect a packet switchednetwork

7.2 Protocols

7.2.1 CORBA

Common Object Request Broker Architecture (CORBA) specifies aset of communication protocols between objects, which enablesthe interaction between the objects that comply with the protocolsindependent of language, device, and operating system.

The communication medium of CORBA is Object Request Broker(ORB), which is responsible for message transfer between objects.ORB provides a mechanism that enables user applications to callremote objects. Different companies can develop different ORBs.However, seamless communication between the applicationsbased on these different ORBs is possible because the samecommunication protocols are adopted.

CORBA adopts the following protocols:

� Internet Inter-ORB Protocol (IIOP) for Communication

� File Transfer Protocol (FTP)

� TELNET Protocol for Remote Operation and Maintenance

7.2.2 IIOP Protocol Stack

Internet Inter-ORB Protocol (IIOP), as an IP-based protocol, isspecified for CORBA applications over the Internet.

Figure 9 illustrates the IIOP protocol stack.


Chapter 7 Interfaces and Protocols

FIGURE 9 PROTOCOL STACK ADOPTED FOR CORBA INTERFACE

7.2.3 FTP Protocol Stack

CORBA adopts File Transfer Protocol (FTP) for transferring files.Figure 10 illustrates the FTP protocol stack.

FIGURE 10 FTP PROTOCOL STACK

7.2.4 TELNET Protocol Stack

CORBA adopts Telecommunication Network Protocol (TELNET)protocol to support remote operation and maintenance functions.Figure 11 illustrates the TELNET protocol stack.



FIGURE 11 TELNET PROTOCOL STACK

7.2.5 SNMP Protocol

Simple Network Management Protocol (SNMP) is an application-layer protocol used for management information exchange be-tween network devices. It is a part of TCP/IP stack. SNMP hasbeen widely used in the telecommunications field due to its sim-ple and practical characteristics. It becomes the most widely usedmanagement frame of TCP/IP networks. SNMP protocol is basedon User Datagram Protocol (UDP), which specifies the encapsula-tion format of data units. SNMP protocol has three versions SN-MPv1, SNMPv2c and SNMPv3.

SNMP NetworkManagement

Model

The network management model of SNMP consists of four parts:

� Management Node: The management node runs the SNMPagent program. It maintains a local database, describes thestatus and history of the node, and influence the running ofthe node.

� Management Station: The management station runs aspecial network management program (manager) to supportthe communication between the management protocol andthe SNMP Agent on the management node. It maintains themanagement information base.

� Management Information Base (MIB): Each managementstation use one or more variables to describe its status. Thesevariables are objects forming the management informationbase.

� Management Protocol: The management protocol is usedby the management station to query and modify the status ofmanagement node. The management node can use the man-agement protocol to send Trap messages to the managementstation.

SNMP MessageTypes

SNMP messages are classified into five types:

� Get_Request:

SNMP Manager uses a Get_Request message to search for in-formation in a network device with SNMP Agent.

� Get_Next_Request

Get_Request and Get_Next_Request messages can be used to-gether to get an object in a table, where Get_Request is usedfor getting a specific object in the table and Get_Next_Requestis used for getting the next object in the same table.


Chapter 7 Interfaces and Protocols

� Get_Response

SNMP Agent responds to the Get_Request message with aGet_Response message. It exchanges much information withSNMP Manager, such as system name, how long the systemruns properly after autorun, and the number of networkinterfaces in the system.

� Set_Request

SNMP Agent can use the Set_Request message to remotelyconfigure the parameters of a device.

� Trap

Trap is a non-request message sent by SNMP Agent to the man-agement station. It is used to notify the server of a certainevent.

Application ofSNMP in NMS

SNMP protocol provides SNMP Manager and Agent functions in thenetwork management system, as depicted in Figure 12.

FIGURE 12 APPLICATION OF SNMP IN THE NMS

The functions of SNMP Manager are used when the network ele-ment system can only be managed by SNMP protocol. In this case,all NEs are managed by the network element management system(EMS) as SNMP agents.

The functions of SNMP Agent are used when the upper-layer net-work management system (NMS) requires to manage the EMS by



SNMP protocol. In this case, the NMS manages the network ele-ment system as an SNMP manager.

SNMP Manager functions and SNMP Agent functions have nocoupling relation. The network management system providesSNMP Manager and Agent functions according to the actualrequirements.


Chapter8 Networking Modes


>> Non-Cascade Networking Modes>> Cascade Networking Modes>> Distributed System

8.1 Non-Cascade NetworkingModesThe NetNumen U31 system generally adopts a non-cascade net-working mode, in which a single server is used to manage thewhole network. The management capability of the system is mea-sured based on this networking mode.

The following three non-cascade networking modes are available:

� Non-Cascade Local Networking

� Non-Cascade Remote Networking

� Non-Cascade Integrated Networking

8.1.1 Non-Cascade Local Networking

Non-cascade local networking is the most common networkingmode used by centralized network management systems. It is asimple networking mode, in which the server, clients and NEs areall located in the same Local Area Network (LAN) and connectedwith each other via Ethernet. In this networking mode, the serverconnects to the managed NEs via LAN.

The following describes the topology of this networking mode andthe required devices for the local networking.

� Topology

The topology of the non-cascade local networking of the net-work element management system is shown in Figure 13.



FIGURE 13 NON-CASCADE LOCAL NETWORKING

� Required Devices

Few network devices are needed in the local networking mode.Select proper 10M/100M adaptive HUBs with enough ports ac-cording to the quantity of hosts (that is, the sum of server num-ber and client number) and prepare necessary twisted pairs(network cables) correspondingly, as described inTable 9.

TABLE 9 DEVICES NEEDED FOR NON-CASCADE LOCAL NETWORKING

Device Model Quantity Remark

16-port HUB ZXR10 1816 n “n” depends on theactual situation

Twisted pair Category–3 orCategory-5

x

The length of twistedpair “x” (unit: m)depends on theactual situation

8.1.2 Non-Cascade Remote Networking

The NetNumen U31 system supports various non-cascade remotenetworking modes, in which the clients are located remotely fromthe server. Different remote networking modes have the samenetwork topology and follow the same networking principle. Spe-cific transmission equipment is used to connect the system to aWide Area Network (WAN). The server and the client are locatedin different LANs with corresponding routers and HUBs.


Chapter 8 Networking Modes

The non-cascade remote networking supports the transmissionover leased line of Digital Data Network (DDN), E1 line, or High-data-rate Digital Subscriber Line (HDSL).

The following introduces the remote networking based on DDNleased line transmission mode and E1 transmission mode, whichare commonly used in the actual telecommunication networks dueto their quality and cost advantages.

� Remote Networking Based on DDN Leased Line

The stable and reliable DDN provides a high transmission ratefrom 64kbps to 2Mbps. In this remote networking mode,routers and baseband MODEMs are used. At the server, anHUB is connected to a router and the router is connectedto the leased line of the DDN via a baseband MODEM. Theremote client is connected to the leased line in the same wayvia its Ethernet interface.

Figure 14 illustrates the remote networking of the NetNumenU31 system based on DDN leased line.

FIGURE 14 NON-CASCADE REMOTE NETWORKING OVER DDN

The devices and their quantity needed for the non-cascade re-mote networking over DDN are described in Table 10.

TABLE 10 DEVICES NEEDED FOR NON-CASCADE REMOTE NETWORKINGOVER DDN


Router ZXR10GAR2604 1+n -

Switch ZXR10 1816 m

ZXR10 1816 isa 16-port switchused to connect thedevices in an LAN.




Twisted pair Category–3,or Category-5

x Unit: m

Daughtercard of router RA-4HS 1+n

It is used to connectthe router to a localbaseband MODEM.

Cable forconnectingrouter

V.35C1 1+nIt is used to connecta router to abaseband MODEM.

BasebandMODEM ASM-40 1+n

It is used to connectthe system tothe DDN when abroad bandwidthis required. Thehighest rate of thebaseband MODEMis 2048 kbps.

– “n” depends on the number of LANs required by the remote clients inthe system.

– Determine the switch number “m” and the length of twisted pair “x”according to the actual situation.

� Remote Networking Based on E1 Transmission

In the non–cascade remote networking over E1 transmission,E1 (2Mbit/s) lines are used to transmit IP packets. At both endsof an E1 line, timeslot extractors are needed. The maximumtransmission rate of each timeslot is 64kbps. By the channel-ization technology, N timeslots can be used together to get arate of N×64kbps, which meets the requirements for differenttransmission rates. A router and a channelized E1 module canbe used together as a stable and reliable timeslot extractor.

Figure 15 illustrates the remote networking of the NetNumenU31 system based on E1 transmission.



FIGURE 15 NON-CASCADE REMOTE NETWORKING BASED ON E1TRANSMISSION NETWORK

The devices and their quantity needed for the non-cascade re-mote networking over E1 transmission network are describedin Table 11.

TABLE 11 DEVICES NEEDED FOR NON-CASCADE REMOTE NETWORKINGBASED ON E1 TRANSMISSION


Router ZXR10GAR2604 1+n -

Switch ZXR10 1816 m

ZXR10 1816 isa 16-port switchused to connectthe devices in anLAN.

Twisted pair Category–3,or Category–5

x Unit: m

Daughtercard of router RA-4CE175 1+n

It acts as the E1interface board,providing coaxialinterfaces.

E1 cable DT75/3- 1+n

It is used toconnect therouters to theE1 transmissionnetwork.

– “n” depends on the number of LANs required by the remote clients inthe system.

– Determine the switch number “m” and the length of twisted pair “x”according to the actual situation.



8.1.3 Non-Cascade IntegratedNetworking

The integrated networking is a combination of local networkingand remote networking. Local NEs/clients and remote NEs/clientscoexist in this networking mode. Figure 16 illustrates the topologyof the integrated networking over DDN.

FIGURE 16 NON-CASCADE INTEGRATED NETWORKING OVER DDN

8.2 Cascade Networking ModesMultiple NetNumen U31 servers can be cascaded to manage alarge-scale network. The lower-level servers manage part of thenetwork, responding to the requests and processing the data com-ing from this part. The upper-lever server connects to multiplelower-level servers, processing the information from the lower-level servers and responding to the requests from the upper-levelclients. It manages the whole network via lower-level servers.

The cascade networking can be classified into local cascade net-working and remote cascade networking according to the physicalrelations between the upper-level server and lower-level servers.

8.2.1 Local Cascade Networking

When the scale of a network is so large that a single NetNumen U31system can not manage the whole network, the cascade network-ing mode can be used to increase the management capacity. Inthis networking mode, the lower-level servers manage the devices



in corresponding areas. They are integrated and connected to theupper-level server via LAN. Therefore, the upper-level server canimplement the centralized management of the whole network.

In the local cascade networking mode, the upper-level server andlower-level servers are located in the same LAN. Any of the non-cascade networking modes described earlier can be used for eachserver and the clients corresponding to it.

For example, Figure 17 illustrates the networking of a NetNumenU31 system, where the local cascade networking mode is usedfor the upper-level server and two lower-level servers, and thenon-cascade local networking mode is used for each server andcorresponding clients.

FIGURE 17 LOCAL CASCADE NETWORKING

As shown in Figure 17, the upper-level server and the lower-levelservers are integrated in the same LAN, and each server has cor-responding clients.

Note:

Figure 17 illustrates the logical model of upper-level client andlower-level clients. Physically, the management processes of thelower-level clients can be deployed on the upper-level client.

8.2.2 Remote Cascade Networking

In the remote cascade networking mode, the upper-level serverand the lower-level servers are connected via DDN or E1 trans-mission network. All non-cascade networking modes describedearlier can be used for each server and corresponding client.

Figure 18 illustrates the topology of a remote cascade networkingmode.



FIGURE 18 REMOTE CASCADE NETWORKING

As shown in Figure 18, the upper-level server and lower-levelservers are integrated via E1 transmission network instead of aLAN.

8.3 Distributed SystemThe commercial application capability meeting the requirement ofhigh capacity and load is a key point for a centralized network man-agement system, which has a bottleneck of load processing dueto huge amount of performance and alarm data. The distributeddeployment of the centralized network management system canimprove the overall processing capability of the system, eliminat-ing the bottleneck of load processing.

The NetNumen U31 system supports the flexible deployment ofits functional modules on different servers in a distributed way.The distributed deployment not only improves the system stabil-ity, but also provides convenience for troubleshooting and moduleupgrade.

The distributed system is designed on the application layer, whichfollows the same basic principle as other application systems.There is no uniform requirement for the topology of the distributedsystem. Figure 19 illustrates a typical topology of a distributednetwork management system, in which the database server,application server and access server are deployed in a distributedway.



FIGURE 19 TYPICAL DISTRIBUTED DEPLOYMENT OF THE SYSTEM

The following distributed deployment modes are available for acentralized network management system:

� Distributed Deployment of Database

In this mode, the database is independently deployed on aserver.

� Distributed Deployment of Access Servers

The access services can be distributed on common servers toreduce the cost. For example, three access servers can bearranged to access nine radio network subsystems to the cen-tralized network management system. Each server supportsthe access of three radio network subsystems. The functionsof an access server include transferring information betweenupper-level and lower-level interfaces, collecting the data andstoring the data in the database.

� Distributed Deployment of Application Servers

In this mode, fault management server, performance manage-ment server and other management servers are deployed in-dependently according to the actual needs.


Figures

Figure 1 Logically Layered Architecture of TMN ....................... 3

Figure 2 Distributed NetNumen U31 System........................... 4

Figure 3 Southbound Interfaces and Northbound Interfaces ..... 5

Figure 4 Dual-Server NetNumen U31 System ........................12

Figure 5 Dual-Server Configuration Solution for Hot Backup ....16

Figure 6 Layered Software Model of NetNumen U31 ...............19

Figure 7 Locations of Remote Clients ....................................21

Figure 8 Relation Model of Security Management ...................29

Figure 9 Protocol Stack Adopted for CORBA Interface .............39

Figure 10 FTP Protocol Stack...............................................39

Figure 11 TELNET Protocol Stack .........................................40

Figure 12 Application of SNMP in the NMS.............................41

Figure 13 Non-Cascade Local Networking..............................44

Figure 14 Non-Cascade Remote Networking over DDN............45

Figure 15 Non-Cascade Remote Networking Based on E1

Transmission Network ........................................47

Figure 16 Non-Cascade Integrated Networking over DDN........48

Figure 17 Local Cascade Networking ....................................49

Figure 18 Remote Cascade Networking.................................50

Figure 19 Typical Distributed Deployment of the System .........51


Glossary

ACMAdaptive Coding and Modulation

BMLBusiness Management Layer

CORBACommon Object Request Broker Architecture

DBDataBase

DDNDigital Data Network

EMLElement Management Layer

EMSNetwork Element Management System

ERTEmbedded Remote Terminal

FTPFile Transfer Protocol

GUIGraphical User Interface

HDSLHigh-data-rate Digital Subscriber Line

IIOPInternet Inter-ORB Protocol

IPInternet Protocol

ITU-TInternational Telecommunication Union - Telecommunication Stan-dardization Sector

J2EEJAVA 2 platform Enterprise Edition

KPIKey Performance Indicator

LANLocal Area Network

MIBManagement Information Base

MMLMan Machine Language

MODEMModulator-Demodulator

NAFNorthbound Adapter Function



NENetwork Element

NMLNetwork Management Layer

NMSNetwork Management System

ORBObject Request Broker

OSSOperation Support System

PCPersonal Computer

PSPacket Switched

RAIDRedundant Array of Independent Disks

RFCRequest For Comments

SMLService Management Layer

SNMPSimple Network Management Protocol

TCPTransfer Control Protocol

TELNETTelecommunication Network Protocol

TMNTelecommunications Management Network

UDPUser Datagram Protocol

WANWide Area Network

XMLeXtensible Markup Language


mw_ss31_e1_0 netnumen u31 system description

Documents

system architecture

system overview

system background

system function

system features

system openness

system reliability

zte corporationor