NetNumen™U31R10 - EDGE · PDF fileTo follow the future network development trends, ZTE...

NetNumen™ U31 R10Unified Element Management System

Product Description

Version: V12.14.30

ZTE CORPORATIONNo. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://support.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright © 2014 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or

distribution of this document or any portion of this document, in any form by any means, without the prior written

consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by

contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE

CORPORATION or of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions

are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,

title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the

use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications

covering the subject matter of this document. Except as expressly provided in any written license between ZTE

CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter

herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 2014-09-16 First edition

Serial Number: SJ-20140901094922-001

Publishing Date: 2014-09-16 (R1.0)

SJ-20140901094922-001|2014-09-16 (R1.0) ZTE Proprietary and Confidential

ContentsAbout This Manual ......................................................................................... I

Chapter 1 Product Positioning and Characteristics ............................... 1-11.1 Product Positioning ............................................................................................ 1-1

1.2 Characteristics ................................................................................................... 1-2

Chapter 2 Product Architecture ................................................................ 2-12.1 System Hardware Architecture ............................................................................ 2-1

2.2 System Software Architecture ............................................................................. 2-2

Chapter 3 Product Functions .................................................................... 3-13.1 Topology Management ....................................................................................... 3-1

3.2 Fault Management ............................................................................................. 3-1

3.3 Performance Management.................................................................................. 3-1

3.4 System Management.......................................................................................... 3-2

3.5 Task Management .............................................................................................. 3-2

3.6 Security Management......................................................................................... 3-3

3.7 Log Management ............................................................................................... 3-4

3.8 Report Management........................................................................................... 3-5

Chapter 4 Networking Applications.......................................................... 4-14.1 Networking Mode ............................................................................................... 4-1

4.1.1 Local Networking...................................................................................... 4-1

4.1.2 Remote Networking.................................................................................. 4-1

4.1.3 Mixed Networking..................................................................................... 4-1

4.2 Server Deployment............................................................................................. 4-2

4.2.1 Centralized Deployment............................................................................ 4-2

4.2.2 Distributed Deployment ............................................................................ 4-3

4.2.3 Layered Networking ................................................................................. 4-4

4.3 Client Deployment .............................................................................................. 4-5

4.3.1 Single-client Deployment .......................................................................... 4-5

4.3.2 Multi-client Deployment ............................................................................ 4-6

4.4 Typical O&M Solution ......................................................................................... 4-7

4.4.1 Integrated Management for Fixed and Mobile Networks.............................. 4-7

4.4.2 Integrated ICT Management ..................................................................... 4-8

4.4.3 End-to End Service Assurance Solution..................................................... 4-9

Chapter 5 Interfaces and Protocols .......................................................... 5-1

I


5.1 System Interface ................................................................................................ 5-1

5.2 Protocol Interface Description ............................................................................. 5-2

5.2.1 SNMP Interface........................................................................................ 5-2

5.2.2 FTP Interface ........................................................................................... 5-2

5.2.3 CORBA Interface ..................................................................................... 5-2

5.2.4 TL1 Interface ........................................................................................... 5-3

5.2.5 XML Interface .......................................................................................... 5-3

5.2.6 DB Interface............................................................................................. 5-3

Chapter 6 Technical Specifications .......................................................... 6-16.1 Physical Indexes ................................................................................................ 6-1

6.2 Performance Indexes ......................................................................................... 6-2

6.3 Power Consumption Specifications.................................................................... 6-10

Chapter 7 Environmental Requirements .................................................. 7-17.1 Requirements for Power Supply .......................................................................... 7-1

7.2 Grounding Requirements .................................................................................... 7-1

7.3 Temperature and Humidity Requirements ............................................................ 7-2

7.4 Anti-EMI Requirements....................................................................................... 7-3

7.5 Anti-Lightning Requirements ............................................................................... 7-4

7.6 Anti-Static Requirements .................................................................................... 7-5

7.7 Illumination ....................................................................................................... 7-5

7.8 Fire Control ....................................................................................................... 7-5

Chapter 8 Complied Standards................................................................. 8-1

Figures............................................................................................................. I

Tables ............................................................................................................ III

Glossary .........................................................................................................V

II


About This ManualPurposeThis manual describes the characteristics, architecture, function, technical data ofNetNumen U31 system and related protocols and interfaces.

Intended AudienceThis manual is intended for:

l Planning engineersl Debugging engineers

What Is in This ManualThis document uses the following typographical conventions.

Chapter Summary

1, Product Positioning and

Characteristics

Describes the location and characteristics of the product on the

network.

2, Product Architecture Describes the hardware, software architectures and the configuration

requirements of the product.

3, Product Functions Describes the service functions of the product, such as topology,

alarm and performance.

4, Networking Applications Describes the typical network solution mode of the product.

5, Interfaces and Protocols Describes the internal and external interfaces of the product and

related protocols.

6, Technical Specifications Describes the technical specifications of the product, including power

consumption and reliability.

7, Environmental

Requirements

Describes the requirements of the product for operation environment.

8, Standards Describes the standards that the product follows.

I


This page intentionally left blank.

II


Chapter 1Product Positioning andCharacteristicsTable of Contents

Product Positioning ....................................................................................................1-1Characteristics ...........................................................................................................1-2

1.1 Product PositioningWith the development of the all IP technology and the tremendous transformation in thetelecom industry, broadband, mobility, and convergence have become the mainstreamtrends in telecom networks. An all IP network architecture requires a flat Operation,Administration and Maintenance (OAM) to reduce the OPEX and improve efficiency.

To follow the future network development trends, ZTE launched the unified networkmanagement system NetNumen U31. It can manage all the NEs of ZTE wired network,including various devices in the service layer, control layer, bearer layer, access layer,and terminal layer.

The location of the NetNumen U31 in the network is shown in Figure 1-1.

1-1


NetNumen™ U31 R10 Product Description

Figure 1-1 NetNumen U31's Location in an Network

l Based on the TMN hierarchical division, NetNumen U31 is located at the elementmanagement layer.

l The NetNumen U31 provides upper level NMS/BBS with northbound interfaces.l The NetNumen U31 provides lower level NEs with southbound interfaces.

1.2 CharacteristicsThe NetNumen U31 has the following characteristics:

Unified management, simplified operation and maintenance, reduced OPEXl Multiple networks can be managed in a unified way. The network management

functions of fixed networks, bearer networks, terminals, services, and microwavenetworks are integrated into the NetNumen U31, which means that multiple scenarioscan be managed in a unified way.

l Unified IT/IP software and hardware management: IT devices, IP devices, andsoftware systems, for example, routers, Ethernet switches, firewalls, servers,operating systems, databases, storage devices, clusters, and middleware aremanaged in a unified way.

Flexible system architecture, smooth evolutionl The NetNumen U31 provides a redundancy solution of high availability by using a

cluster consisting of a local server and a remote server.

1-2


Chapter 1 Product Positioning and Characteristics

l The NetNumen U31 supports multiple platforms and databases. The system isdeveloped based on the JAVA language, so it supports UNIX, Windows, and Linuxoperating systems, and MSSQL Server and Oracle databases.

l The NetNumen U31 is modularized, so that it is easy to expand and upgrade. Clientsand servers are in platform + EMS mode. All EMSs and management functionmodules are imbedded in the system platform as components. When you installthe NetNumen U31, you can select the devices to be managed to customize yourinstallation. In addition, the NetNumen U31 supports EMS systems of new products,and is compatible with early and later versions. Because it is extendable, compatible,and upgradable, it can meet specific network development needs.

l The NetNumen U31 provides open interfaces that can be used to integrate with a thirdparty EMS system. It supports SNMP and provides CORBA, TL1, FTP, DB, and ASCIIinterfaces. In addition, it can be integrated with third party EMS systems, for example,IBM Tivoli Netcool/OMNIbus and HP TeMIP. Therefore, carriers can construct an OSSapplication system for the global network easily.

l The NetNumen U31 supports multiple access methods and networking modes.Networks can be managed at any time and place. Depending on different applicationscenarios, it can provide three access methods: GUI, CLI, and Web. It can beaccessed by either a local client or a remote client, and it can be maintained in aunified manner or locally. You can select a client based on the application scenario,habit, networking requirements, and bandwidth.

Convenient and efficient system managementl The NetNumen U31 can detect NEs fast automatically, and thus the management

efficiency is improved and the operation & maintenance costs are reduced. Devicescan be detected and added to the NetNumen U31 system in batches based on theuser-defined IP range and device types.

l The NetNumen U31 provides statistics collection. The resource and performancestatistics of all managed devices can be collected. This function can be used toguarantee network QoS.

Secure and reliable managementl The NetNumen U31 provides sophisticated security management. Multiple security

levels can be set based on management area, management range, and managementfunction to meet different management requirements. In addition, the NetNumen U31provides security logs, operation logs, and system logs.

l TheNetNumenU31 supports single sign-on, which contributes to unifiedmanagementand maintenance. Data can be saved and managed in a unified manner.

1-3




1-4


Chapter 2Product ArchitectureTable of Contents

System Hardware Architecture ...................................................................................2-1System Software Architecture ....................................................................................2-2

2.1 System Hardware ArchitectureThe NetNumen U31 system uses client/server mode, which means that a server isconnected with multiple clients in the NetNumen U31 system.

The NetNumen U31 system hardware consists of a server, clients, a disk array, networkdevices, and an alarm box. For the architecture of the NetNumen U31 hardware, seeFigure 2-1.

Figure 2-1 System Hardware Architecture

l Server

The NetNumen U31 server can operate on a Windows, Linux or UNIX platform. Itprocesses and saves NE data. In addition, the server communicates with upper levelNMS systems through the northbound interface. Based on functions, the NetNumenU31 server can operate as either an application server or a database server. The

2-1



hardware of these two servers can either co-located or installed independently. Bydefault, the hardware is co-located. The NetNumen U31 system can be installed onone server or two servers. If it is installed on two servers, these two servers are inactive and standby mode.

l Client

NetNumen U31 clients operate on aWindows platform. They provide a graphical userinterface. Operators can operate and maintain NEs through the clients.

l Disk array

The disk array is used to store data reported by lower-layer network elements, suchas alarms and performance data.

l Network device

Network devices are used to connect the NetNumen U31 server with NEs or BOSS/NMS, for example, the switch or the router.

l Alarm box

The NetNumen U31 system uses an alarm box to monitor current alarms. Alarms ofdifferent levels are indicated by different lights and sounds.

2.2 System Software ArchitectureTheNetNumenU31 system uses a client/server operationmode. Both the client and serversoftware are independent of each other. The server software is installed on a server andthe client software is installed on a PC client. They can also be installed on the samecomputer if necessary.

For the architecture of the NetNumen U31 software, see Figure 2-2.

2-2


Chapter 2 Product Architecture

Figure 2-2 NetNumen U31 Software Architecture

l The NetNumen U31 system is based on a J2EE platform. It can operate on a UNIX,Windows, or Linux OS. It uses a SQL Server or Oracle database.

l The NetNumen U31 server software is composed of multiple modules. Each mod-ule provides certain functions, for example, configuration management, fault man-agement, security management, topology management, performance management,report management, policy management, and log management. The NetNumen U31server software provides northbound interfaces for BOSS/NMS, and southbound in-terfaces for NEs.

l The NetNumen U31 client software provides graphical user interfaces to operate andmaintain NEs.

l The NetNumen U31 system is designed with the load balance and disaster recoveryfunctions. Data is saved in a distributed manner to ensure system reliability.

2-3




2-4


Chapter 3Product FunctionsTable of Contents

Topology Management ...............................................................................................3-1Fault Management .....................................................................................................3-1Performance Management .........................................................................................3-1System Management .................................................................................................3-2Task Management ......................................................................................................3-2Security Management ................................................................................................3-3Log Management .......................................................................................................3-4Report Management...................................................................................................3-5

3.1 Topology ManagementThe NetNumen U31 manages a large number of devices, which are managed in differentgroups. By using topology management, the system can display the topology of the entirenetwork by function or device type. On the topology, NEs, NE connections, and alarmsare displayed directly in different colors. You can know the operation status of the entirenetwork easily.

3.2 Fault ManagementWith the fault management function, all types of device alarms and other network eventsreported on the entire network are displayed to maintenance personnel directly, and thusthe maintenance personnel can know the operation status of the network. If any faultis detected, it is easy for maintenance personnel to locate the fault and the cause, andtroubleshoot the fault to ensure normal system operation.

3.3 Performance ManagementThe performance management module is responsible for performance monitoring andanalysis of data network and equipment. By collecting various performance data fromnetwork elements and generating performance reports after processing, this moduleprovides information for system maintenance and management, network planning andadjustment, and network optimization.

The NetNumen U31 provides sophisticated performance management. It monitorsperformance of the entire network through performance task customization, performancereport output, and performance threshold management.

3-1



3.4 System ManagementThe system management function is used to monitor and maintain the application serverand the database server. In addition, it provides the frequently used functions for managingthe database.

For the frequently used functions provided by system management, refer to Table 3-1.

Table 3-1 System management function Descriptions

Function Description

Server performance

management

Checks server performance parameters (for example, CPU, memory, hard

disk, and server process), and set system threshold parameters and

server performance alarms.

Database management Provides the following local database management functions: database

login, database resource view, database backup, database restoration,

data table backup, data table restoration, data table clearance, database

maintenance task, regular database maintenance task, and database

logout.

System data backup

and restoration

Provides backup and restoration functions for logs, alarms and

performance data.

Provides the backup function for database and files.

Provides a unique “Favorite” function, which is similar to IE's “Favorite”

function, to offer fast link for frequently used functions.

Other management

Views the system time, prints settings, sets system styles, sets screen

lock, controls access rights, and sets window size.

License control Uses the license to control server-side MAC address, validity period,

number of user interface terminals, function package module, northbound

function package, device types under management and specific function

authorization.

3.5 Task ManagementIt is also called policy management. A task is a predefined procedure in the EMS. Theprocedure specifies operations in the EMS under special conditions. With the predefinedtask, the EMS system can automatically execute related operations in accordancewith the current operation status for automatic dispatching and protection, and systemself-management for high efficiency.

For a description of the task management functions, refer to Table 3-2.

3-2


Chapter 3 Product Functions

Table 3-2 Task Management Function Descriptions


History data archive Executes periodically backup and deletion tasks for logs,

performance data, and alarms to prevent the database from being

overloaded.

Basic data backup Executes basic data backup tasks periodically. Back up all the basic

data of the network management system. Back up only data records

excluding the history data, such as table structure and history

alarms, notifications, logs, performance raw data (history data has

the dedicated backup function).

Version and database backup Executes NM version file and database backup tasks periodically.

File clearance Monitors data catalogs of different types, and executes periodically

clearance tasks when the index exceeds the threshold.

Automatic confirmation of

history alarm

Confirms history alarms before the set days automatically, so as to

improve the maintainability.

IP NE resource collection Executes IP NE resource collection tasks periodically. The operation

can be performed based on hour/day/week/month and one-time.

The start and end time can be set.

3.6 Security ManagementSecurity management is used to ensure users’ legal use of the NetNumen U31 system.With the security management function, users, user groups, and roles can be managed,and the operators are controlled when performing operations in the NetNumen U31system. Users must log in to the system, and then can perform operations in the system.

For the security management functions, refer to Table 3-3.

Table 3-3 Security Management Function Descriptions


Role management The user can create, modify, copy and delete a role set as well as assign a

role to a role set based on the operation rights.

The user can create, modify, copy and delete a role as well as assign

operation rights to a role based on the operation rights.

The user can set role rights for resources and an operation set, which means

that users of different roles manage different areas.

3-3




User management A user has multiple attributes, including ID, password, user validity period,

password validity period, and department. The management functions

supported include: add/delete a user, associate a user with a role or a role

set, configure a user profile and modify a user password.

Check user lock status.

Views the information of the current logged-in user, and log out a logged-in

user if necessary.

Blacklist management: the users added to a blacklist cannot log in to the

system.

Sets a validity period for a user account.

Sets the validity period for a password.

Sets the working time, holiday, login IP range, and login MAC binding for a

user.

Sets concurrent login number for one user.

Sets the maximal and minimal length of a password.

Sets account lock upon login failure.

Sets automatic lock function.

Department

management

Department is a simulation of an administrative department for the

convenience of user organization and management. The user can create a

department as required. By default, there is a root department in the system.

This department is the supreme department and all other newly created

departments are its sub-departments.

3.7 Log ManagementA log refers to the recorded information of various events and operations in the system. Byviewing logs, a user can know whether the system is operating properly, locate the causeof a fault, and trace and audit important events. Log management is an effective tool forthe system administrator to check the system operating status, locate a system fault, andtrace user operations.

For the log management functions, refer to Table 3-4.

Table 3-4 Log Management Function Descriptions


Operation log Saves user's access information, including the accessed function module,

operation process, operation time, and operation result.

Security log Saves user's login and logout information.

System log Saves the operation information of the system or a module, for example,

when the system is started and turned off, the operation status of all

modules, system interruption, and module interruption.

3-4


Chapter 3 Product Functions


Log query Queries a system log.

Log output Outputs a log in the form of text or SYSLOG.

Log deletion Deletes logs periodically.

3.8 Report ManagementA user can be informaed of the system operation status and performance through reports.The report management system generates reports periodically. The user can make correctanalysis and decision based on the reports.

For the report management functions, refer to Table 3-5.

Table 3-5 Report Management Function Descriptions


Unified Report View The system provides a unified report view, including performance report

and alarm report.

Report Task

Management

Report task management generates reports periodically. The time and

report type can be set.

Report File

Management

Reports can be previewed, printed, and saved as Excel, Html, PDF, or

CSV files.

3-5




3-6


Chapter 4Networking ApplicationsTable of Contents

Networking Mode .......................................................................................................4-1Server Deployment.....................................................................................................4-2Client Deployment ......................................................................................................4-5Typical O&M Solution .................................................................................................4-7

4.1 Networking ModeThe networkingmode includes local networking, remote networking, andmixed networkingbased on the location between the NetNumen U31 and an NE.

4.1.1 Local NetworkingLAN networking is the simplest and the most commonly used networking in the networkmanagement system. For this networking, the NetNumen U31 server, clients, and NEsare in one LAN and are interconnected through Ethernet. The NetNumen U31 and its NEsare at one physical location. LCT is in charge of local operation and maintenance of theNE, and the NetNumen U31 manages the devices in the entire network.

4.1.2 Remote NetworkingRemote networking is used when clients and the NetNumen U31 server are not in thesame LAN. For remote networking, basic topologies of the network and their principlesare the same. They use specific transmission devices to transmit data on WAN. A routeris used for the access from the WAN to an LAN. TCP/IP is used for the communicationamong NEs, NetNumen U31 server, and clients.

Because the communication methods between remote network management systems aredifferent, the NetNumen U31 provides different remote access solutions: 2 MB dedicatedline, DDN dedicated line, ISDN, PSTN, and Ethernet.

4.1.3 Mixed NetworkingThe actual networking sometimes uses the mixed networking that consists of localnetworking and remote networking.

Clients include local clients and remote clients. They provide a GUI for operating andmonitoring NEs. Clients are connected to the server through the LAN or an MAN. Thesetwo types of clients have the same operation capability.

4-1



For the architecture of a mixed networking solution, see Figure 4-1.

Figure 4-1 NetNumen U31 Typical Networking

4.2 Server DeploymentServers can be deployed in centralized, distributed, and layered modes.

4.2.1 Centralized DeploymentIn centralized deployment, all servers operate on one host. The centralized networkmanagement is suitable for small-scale networks to meeting the network managementrequirements with the minimized cost.

For the architecture of the solution, see Figure 4-2.

4-2


Chapter 4 Networking Applications

Figure 4-2 NetNumen U31 Centralized Deployment

4.2.2 Distributed DeploymentThe NetNumen U31 supports distributed deployment that allows carriers to deploymanagement modules on different servers. The NetNumen U31 system can consistof one active server and multiple standby servers. The active server provides thefundamental network management functions.

Deployment of the standby servers is based on the network scale and the deploymentcondition. Therefore, servers are loaded in a balanced manner, more NEs and systemscan be managed, and the operation efficiency is improved.


4-3



Figure 4-3 Distributed Deployment Solution (Fixed Access Network)

The servers of the NetNumen U31 are operating on different machines. They operatewith each other to manage the devices on the entire network. Distributed deployment issuitable for a large-scale network. Moreover, it is suitable for networks that will grow bothin scale and complexity.

4.2.3 Layered NetworkingThe NetNumen U31 supports a special layered networking deployment solution.. Each ofthe management domains has its own EMS server. At the upper layer, there is a superiorEMS to implement centralized management.


4-4



Figure 4-4 Layered Networking (Bearer Network)

Server-1 manages devices in domain 1 and server-2 manages devices in domain2. Thesuperior server-3 manages the two domains simultaneously.

4.3 Client DeploymentClient deployment includes single-client deployment and multi-client deployment.

4.3.1 Single-client DeploymentIt is the most basic and common application mode. The client, server and database mayoperate either on the same computer or independently on different computers dependingon the amount of managed devices and the processing capability of the computer.

For the architecture of the deployment, see Figure 4-5.

4-5



Figure 4-5 Single-Client and Single-Server Networking Mode

4.3.2 Multi-client DeploymentOne server can be logged on by multiple clients. The server assures that all the clientsare synchronized.

This networking mode is usually applied in the case that multiple operation terminals(clients) or display terminals are required by users, and the clients might be distributed invarious areas, so some of the clients need to log on the server remotely. In this way, themanagement of the upper layer NM can also be accessed, with a northbound interfacemodule needed.

For the architecture of the deployment, see Figure 4-6.

Figure 4-6 Multi-Client and Single-Server Networking Mode

4-6



4.4 Typical O&M Solution

4.4.1 Integrated Management for Fixed and Mobile NetworksThe NetNumen U31 provides the integrated management for fixed and mobile networks.For the typical networking architecture, see Figure 4-7.

Figure 4-7 Integrated Management for Fixed and Mobile Networks

Note:

The products with their names in red are not managed by U31 (Wireline).

l Integrated management, supporting all services operations

à The integrated management can manage the access network, transport network,core network, and intelligent VAS products, which provides the uniform O&M forall domains of a telecom network.

à End-to-end service configuration and management for bearer network products;end-to-end service configuration and management across the transport anddatacom networks; simple, quick commissioning and deployment are bothachieved, and O&M difficulty is reduced.

à Network-wide intelligent fault analysis and diagnosis: Based on networkresources and service relationships, the system can automatically locate andanalyze the root/derivative alarms, shortening the time spent on handling alarms.

l Fine-grained customization to lower costs significantly

4-7



à The NetNumen U31 uses the unique PPU component technology that allowscarriers to determine the functions integrated into the EMS. This feature enablesZTE to customize an EMS to meet the individual business needs of a carrier.Furthermore, a variety of deployment schemes are available, and carriers canfind the very one for their current O&M mode. ZTE aims to help carriers drive uptheir ROI.

à Three access methods are available: GUI, Web, and CLI to support the local andremote access requirements. O&M personnel can get access to U31 anytimeanywhere.

l Flexible system architecture for smooth evolution

à Modular design for easy rollout of new services: The modular architecturebrings good scalability to U31, which allows only small adjustments for growth inservices or changes in NE management. Investment is protected, and customerrequirements in the future can be met.

à Distributed deployment and flexible investment: Distributed deployment allowsa minimum investment when carriers are to build a network. The networkmanagement capacity can be expanded flexibly if the network scale is growing.

à Open interfaces for fast integration with third-party systems: A variety ofnorthbound interfaces are provided, which allows the integration of the NetNumenU31 with third-party NMS/BOSS systems, such as IBM Tivoli Netcool/OMNIbus,HP TeMIP, and Aircom Optima.

4.4.2 Integrated ICT ManagementWith multiple management layers combined together, the NetNumen U31 integrated theICT management solution to satisfy the IT management demand that devices of differenttypes and at different network layers can be managed in a uniform manner. It is a simple,convenient, economic, and highly efficient solution.

For the typical architecture, see Figure 4-8.

4-8



Figure 4-8 Integrated IT Device Management

l Support multiple vendors’ IT devices and quick scalability to bring high customersatisfaction

l Integrate with the U31 system to share resources and reduce investment costsl Provides a uniform GUI and combined management capability to ensure high

management efficiency and service QoS.l Provides carrier-class reliability, usability, and securityl Deployed independently or operated with the NetNumen U31 to meet the needs of

networks of different scales.

4.4.3 End-to End Service Assurance SolutionAn end-to-end service assurance solution is implemented based on three layers:

l The bottom layer is for the NE devices.l The middle layer is the management layer, including the U31 system and the

EasyOptical diagnosis system. The EasyOptical is responsible for the followingfunctions: end-to-end fault diagnosis, real-time monitor, performance alarm, statisticsanalysis, and evaluation optimization. With these functions, the service assuranceof the FTTx network is upgrade from onsite manual assurance to remote intelligentassurance.

l The top layer is for the BOSS system. The middle layer is connected with the BOSSsystem through the northbound interface of the EasyOptical. After the three layersare interconnected, service faults can be handled automatically.

4-9



Figure 4-9 End-to-End Service Assurance Solution

4-10


Chapter 5Interfaces and ProtocolsTable of Contents

System Interface ........................................................................................................5-1Protocol Interface Description.....................................................................................5-2

5.1 System InterfaceThe NetNumen U31 provides both southbound and northbound interfaces.

l Southbound interface: The NetNumen U31 manages accessed devices throughthe southbound interface. On the NetNumen U31, the following operations canbe performed: alarm management, performance management, configurationmanagement, topology management, and security management. The southboundinterface supports the following protocols: SNMP, TR069, MML, ASN.1 Qx, Syslog,Telnet/SSH, and FTP/SFTP.

l Northbound interface: The NetNumen U31 provides the open northbound interface tointerconnect with the upper level NMS/BOSS/BSS system. The northbound interfacesupports the following protocols: FTP, SNMP, CORBA, MTOSI, TL1, and DB.

5-1



Figure 5-1 System Interfaces

5.2 Protocol Interface DescriptionThe following sections describe the frequently used interface protocols.

5.2.1 SNMP InterfaceSNMP is a set of standards defined by IETF for network management. It is acceptedin the industry because it is simple and easy to understand. SNMP is implementedbased on the Manager/Agent model where the manager interacts with agents throughManagement Information Base (MIB) and command sets. SNMP provides the activereporting mechanism that allows agents to send the trap messages to the manager.

5.2.2 FTP InterfaceFTP is used by U31 to transfer data files of large sizes, such as PM data files and resourcestopology data files.

5.2.3 CORBA InterfaceCORBA is a standard for distributed objects being developed by the Object ManagementGroup (OMG). It consists of ORB, object services, common facilities, domain-independentinterfaces, and application interfaces. ORB provides the method of implementingtransparent communications between clients and objects.

5-2


Chapter 5 Interfaces and Protocols

5.2.4 TL1 InterfaceTransaction Language-1 (TL1) is an ASCII-based man-machine language defined byTelcordia. It is a standard management protocol in telecommunications. It brings severalbenefits: simple integration, convenient commissioning, good scalability, and goodnetwork adaptability.

5.2.5 XML InterfaceXML, also named as MTOSI, provides a simple and lightweight mechanism for exchangingstructured and typed information using XML through Web. It is a standard interfaceintroduced by TMF. XML messages serve as the interface for OSS. XML defines theinterfaces at the OSS layer, including the high-layer interface (service) and fine-grainedinterfaces (that each OSS service provides to the running environment).

5.2.6 DB InterfaceDB views are a transformation of database data, allowing users to retrieve database tabledata in another way. Through this interface, NMS can query the data view in EMS by usingthe uniform username and password, implementing integration between NMS and EMS.

5-3




5-4


Chapter 6Technical SpecificationsTable of Contents

Physical Indexes ........................................................................................................6-1Performance Indexes .................................................................................................6-2Power Consumption Specifications ..........................................................................6-10

6.1 Physical IndexesThe NetNumen U31 server and disk array are server devices installed in a standard19-inch B6080-22 cabinet. The clients are PCs or workstations that comply with industrialstandards.

For technical parameters of the B6080-22 cabinet, refer to Table 6-1.

Table 6-1 Technical Parameters of the B6080-22 Cabinet

Item Index Description

Standard Design

standard

Complies with the IEC 60297-2 standard, and uses modular

design that facilitates capacity extension and maintenance.

Dimension Height × Width × Depth: 2200 mm× 600 mm × 800 mm.

Capability Standard shelves or devices whose widths are 19 inches provided

by ZTE or a third party can be installed in the cabinet.

Capacity The available internal height is 47U (1U = 44.45 mm).

Weight The empty cabinet is about 124 kg.

Color Navy blue.

Protection Electromagnetic compatibility is considered when the cabinet is

designed. All interfaces provide high electromagnetic shielding

performance.

Dust screens are installed behind the ventilation holes on the front

door, back door, and baseplate of the cabinet.

Physical

parameters

Heat

dissipation

There are ventilation holes on the front door, back door, and

baseplate of the cabinet. The percentage of opening is 56%, so

the cabinet provides high heat dissipation performance.

6-1




Wiring design There are wiring holes at the top and bottom of the cabinet. The

cabinet supports top routing and bottom routing.

Process

specifications

Installation

mode

In a room without antistatic floor, the cabinet can be installed on

the cement floor directly. In a room with antistatic floor, the cabinet

can be installed on the cement floor through the adjustable base.

The NetNumen U31 server can be a SUN-series server or ATCA blade server (with anE4140 shelf). For the technical parameters of the E4140 shelf, refer to Table 6-2.

Table 6-2 Technical Parameters of the E4140 Shelf


Standard Design

standard

19-inch standard 14U shelf, complies with PICMG 3.0 R2.0.

Dimension Height× Width × Depth: 619.5 mm× 482.6 mm × 415 mm.

Number of

board slots

14.

Empty-cabinet

weight

35 kg.

Physical

parameters

Full-

configuration

weight

77 kg.

6.2 Performance IndexesFor the performance indexes of the NetNumen U31, refer to Table 6-3.

Table 6-3 Performance Indexes

Item Index Value Description

Time used for starting a

client for the first time

≤ 7 seconds. Period from the time when a client is

started for the first time to the time when

the dialog box for login is displayed.

Time used for logging in to

a client for the first time


logged in to for the first time to the time

when the main page is displayed (not

including the time used for obtaining data

in the topology view).

Time used for starting a

client


started not for the first time to the time

when the dialog box for login is displayed.

Start

speed

6-2


Chapter 6 Technical Specifications


For a Citrix scenario, every startup is

considered as the first startup.

Time used for logging in to

a client


logged in to not for the first time to the

time when the rack diagram is displayed

(not including the time used for displaying

the topology view). For a Citrix scenario,

every login is considered as the first

login.

Time used for displaying a

view (topology view, alarm

view, performance view,

security view, log view, or

configuration view) on a

client

≤ 2 seconds. -

Time used for switching

views or windows on a

client

≤ 1 second. Time used for switching views, module

windows, and NE windows that have be

opened on a client.

Time used for starting the

command terminal

≤ 2 seconds. Time used for opening a subview on

the command terminal through EMS

commands, not OMM commands (OMM

commands are loaded on the back end,

and the time varies with the size of the

OMM version file).

Time used for starting the

server

≤ 5 minutes. If there are multiple processes on the

server, this index refers to the time

used for starting these processes on the

server.

Operation interaction

between users and the

EMS

When a user performs an

operation in the system, for

example, starting the client, the

system responds within one

second. If the response time

is more than one second, the

system provides a response

indication, for example, the

arrow of mouse becomes a

funnel. If the response time is

more than five seconds, the

system provides a progress

bar.

The system responds to an operation

within 1 second. For an asynchronous

operation, the system sends an

asynchronous command successfully

within 1 second. The time used for

executing the command is not included in

the response time (for an asynchronous

command, the execution time is long).

Opera-

tion re-

sponse

6-3




Time used for querying

logs

≤ 2 seconds. When a user queries 50,000 historical

logs among 1,000,000 historical logs,

the query results on the first page

are displayed within 2 seconds, and

all results can be retrieved within 30

seconds.


active alarms

≤ 2 seconds. Period from the time when the query

parameters are set to the time when

query results are displayed on the first

page (the alarm report speed is 50

alarms per second, and active alarms

are queried on less than 10 clients

simultaneously). If the active alarm

threshold is 20,000, the time is less than

or equal to 2 seconds. If the active alarm

threshold is 100,000, the time is less than

or equal to 5 seconds.


historical alarms

≤ 5 seconds. When a user queries 50,000 historical

alarms among 5,000,000 historical

alarms, the query results on the first

page are displayed within 5 seconds,

and all results can be retrieved within

30 seconds. If this index cannot be met

in some situations, the system sends a

prompt message through a dialog box or

progress bar.


performance information

≤ 5 seconds. When a user queries 100,000 records

among 5,000,000 records, the query

results on the first page are displayed

within 5 seconds, and all results

can be retrieved within 60 seconds.

Performance query operations mean all

operations related to performance data

query, including performance information

browsing. If this index cannot be met

in some situations, the system sends a

prompt message through a dialog box or

progress bar.

Time used for displaying

the rack diagram

≤ 2 seconds. Time used for displaying basic

information about the rack and boards in

the diagram. The time used for retrieving

6-4




alarms from the rack diagram is not

included.

Alarm response time ≤ 5 seconds. Time used for displaying alarm

information in the EMS, making a sound,

and changing color after an NE generates

an alarm in a normal situation (meaning

that the EMS receives 50 or less alarms

per second).

In an alarm storm (meaning that 200

alarms are received per second), the

alarm response time is less than or equal

to 15 seconds (the period from the time

when the EMS southbound interface

receives alarms to the time when the

alarms are displayed on a client is less

than or equal to 8 seconds).

MML command response

time

≤ 2 seconds. Period from the time when a MML

command is sent to the time when the

result is returned. Operation response

processing complies with the Operationinteraction between users and theEMS index.

Time used for

synchronizing alarms

on a single NE

≤ 5 seconds. The time that the EMS uses to

successfully send a single-NE

alarm synchronization command (an

asynchronous operation) is less than or

equal to 1 second.

Time used for

synchronizing alarms

in the entire network

≤ 60 seconds. The time that the EMS uses to

successfully send an entire-network

alarm synchronization command (an

asynchronous operation) is less than or

equal to 3 seconds.

Dialog box and button

response time

≤ 1 second. Time used for responding to an operation

performed through a menu or button

Menu (including shortcut

menu and drop-down list)

and shortcut key response

time

≤ 1 second. Time used for displaying a shortcut menu

or drop-down list.

Time used for exporting

10,000 performance data

entries to a file

≤ 10 seconds. -

6-5





10,000 logs to a file

≤ 10 seconds. -


10,000 historical alarms to

a file

≤ 10 seconds. -

Time used for getting

online help (in Topology,

Fault, Security,

Configuration, and Tools

modules)

≤ 2 seconds. Period from the time when a user presses

F1 in a module to the time when help

information is displayed (if the user uses

help for the first time, the period is 3

seconds. If the size of the help file is

large, for example, the file contains a lot

of figures, the period may be more than

3 seconds).

Time used for getting MML

command online help

≤ 2 seconds. Period from the time when a user click

the help tab on an MML page to the time

when help information is displayed.

Time used for turning

pages turning to browse

information (including

alarm information,

tracing information, MML

returning information, and

performance information),

selecting a node in a tree,

and switching windows

≤ 1 second. When a user browse data by pressing

the PgUn (or PgDn) button or dragging

the scroll bar, the windows do not flicker

or fail to respond, and the scroll bar is

smooth.

Alarm report delay ≤ 2 seconds. Period from the time when alarms

are uploaded through the northbound

interface to the time when the alarms

are received in the upper-layer network

management system.

CPU usage of a client ≤ 65%. CPU usage of a client

does not exceed 65% for a long

period.

The period when CPU usage exceeds

90% due to instantaneous peak traffic

must not be more than 10 seconds.

If CPU usage is increased due to an

operation, the CPU usage should be

reduced to a normal value after the

operation processing is completed.

Re-

source

usage

CPU usage of the server ≤ 70％. CPU usage of the server in lightly loaded

conditions or normal conditions (for

example, at least ten NEs download

software version file simultaneously, or

6-6




the maximum number of active clients

perform concurrent operations).

The period when CPU usage exceeds

90% due to instantaneous peak traffic

must not be more than 10 seconds.

If CPU usage is increased due to an

operation, the CPU usage should be

reduced to a normal value after the

operation processing is completed.

Access

capabil-

ity

Number of concurrent-

access clients

≥ 50. The number of concurrent operations

is smaller than the number of

concurrent-access clients. For

small-scale services, the number of

concurrent-access clients can be smaller

than 50.

In specified conditions, the number of

supported terminals must be equal to

greater than 128. For fixed networks

and bearer networks, the number of

concurrent-access clients must be equal

to greater than 200.

Maximum number of NEs

managed by the system

50, 000 equivalent NEs (bearer

network).

100,000 equivalent NEs (fixed

network).

For conversion between NE types and

equivalent NEs, contact ZTE technical

supports.

Maximum number of NEs

managed by a single

server

8,000 physical NEs (bearer

network).

40, 000 equivalent NEs (fixed

network).

Information about the NetNumen U31

operation on a single server. The

configuration of the server is equal to or

higher than the hardware configuration

for network scale 6.

Alarm processing capacity Active alarm processing

capacity: ≤ 100,000 alarms per

second.

Historical alarm processing

capacity: ≤ 10,000,000 alarms

per second.

During normal system

operation, the alarm processing

capacity is equal to or more

than 150 alarms per second.

The peak alarm processing

capacity is equal to or more

Total number of alarm generation

messages and alarm clearance

messages processed per second.

Man-

agement

capabil-

ity

6-7




than 250 alarms per second,

lasting for 15 minutes at least.

Performance processing

capacity

Database storage efficiency: ≥

300 per second.

The system operates properly and stably.

CPU usage and memory usage of the

server is normal.

Operation log capacity ≤ 5,000,000. -

Maximum number of

alarms that can be stored

in a single server

20,000,000 Total number of active alarms, historical

alarms, and notifications.

Maximum number of

performance records that

can be stored in a single

server

1,400,000,000 -

Period when report data is

retained

Alarm data: 120 days.

Original performance data: 90

days (granularity: 15 minutes).

Report data: 13 months.

The original performance data table is

retained for 30 days, hourly tables are

retained for 90 days, and daily tables are

retained for 180 days. The maximum

size of report data is 1.5 GB.

The period when report data is retained

can be modified based on the server

configuration.

Minimum bandwidth

between the server and

OMM

256 kbps. -

Minimum bandwidth for

the northbound interface

256 kbps. -

Network

band-

width

Minimum bandwidth

between a client and the

server

32 kbps – 256 kbps. l If the Citrix solution is used, the

minimum bandwidth is 128 kbps.

l If the Coolbit solution is used, the

minimum bandwidth between a

Coolbit browser and Coolbit server

is 32 kbps.

l If the Citrix solution or Coolbit

solution is not used, the minimum

bandwidth is 256 kbps.

l If the PSTN solution is used and

the client uses the Web mode, the

minimum bandwidth is 64 kbps.

6-8




MTBF 6480 hours. Mean time between failures (class A

failures).

MTTR 0.5 hour. Mean time to recovery when the

hardware, operating system, JRE, and

database system are normal. When the

database fails, the MTTR is less than or

equal to 15 minutes.

Availability 0.99992. -

Down time ≤ 30 minutes/year. -

Time used for recovering

configuration data

≤ 10 minutes. In bearer networks, the time used for

backing up configuration data is less than

5 minutes, and the performance archive

efficiency is greater than 6000 pieces per

second.


all data

≤ 40 minutes. Time used for recovering data through

dual-server cluster software when a

server fails.


the database and network

management software

≤ 1.5 hours. Time used for recovering data and

operating the network management

system through dual-server cluster

software when a server fails.

RTO ≤ 4 hours. Recovery time objective when the

operating system is reinstalled.

RPO ≤ 24 hours. Recovery point objective. The data to

be recovered includes basic data and

historical data.

Time used for switching

the active and standby

servers

≤ 7 minutes. Time used for switching the active

and standby servers automatically or

manually (The stop processes is stoppedwith a 1-minute delay, the server is

started within 5 minutes, and the VCS

uses 1 minute for switching).

Stability

Backup and restoration The complete backup data is

retained for two weeks, and

the incremental backup data is

retained for one week.

Complete backup is performed

once a week, and incremental

backup is performed 6 times a

week.

All servers in the system can be backed

up, including the standby server. The

SAN backup mode is supported.

6-9



6.3 Power Consumption SpecificationsThe power consumption of NetNumen U31 depends on the real configuration. For theATCA blade server, Table 6-4 describes the power consumption of shelves and boards.

Table 6-4 Power Consumption Specifications of the ATCA Blade Server

Name Description Full Load Power

E4140 shelf 14 U shelf 260 W

OPBB1 board Universal processing blade, dual-way four-core and

64-bit Jasper processor.

145 W

OPI1 board Rear plate of the universal processing blade. 15 W

SWBB1 board The switching blade with the clock function. 60 W

SWI2 board Rear plate of the switching blade. 15 W

Unified PDU - 10 W

6-10


Chapter 7Environmental RequirementsTable of Contents

Requirements for Power Supply .................................................................................7-1Grounding Requirements ...........................................................................................7-1Temperature and Humidity Requirements...................................................................7-2Anti-EMI Requirements ..............................................................................................7-3Anti-Lightning Requirements ......................................................................................7-4Anti-Static Requirements............................................................................................7-5Illumination ................................................................................................................7-5Fire Control ...............................................................................................................7-5

7.1 Requirements for Power SupplyTable 7-1 describes the specifications of the DC power supply.

Table 7-1 Specifications of a DC Power Supply

Parameter Specifications

Working power -48 V

Voltage range -57 V to -40 V

Voltage output ripple < 200 mV

Table 7-2 describes the specifications of the AC power supply.

Table 7-2 Specifications of an AC Power Supply

Parameter Specifications

Working power 220 V/50 Hz

Voltage range 176 V-264 V

Frequency range 45 Hz-65 Hz

7.2 Grounding RequirementsGrounding intents to guarantee proper operations on equipments and provides a capabilityto resist external electromagnetic disturbance for equipments. The grounding rules are asfollows.

7-1



l Central grounding mode: The working ground, protection ground and buildinglightning ground for various communication equipments share a group of groundingbody.

à The grounding resistance largely depends on soil types.

For areas with poor soil conditions, it is allowable to add some additive chemicalsaround the grounding markers to reduce soil resistivity and contact resistance.

à Variations of temperature and humidity also make the grounding resistancechange.

If the temperature is below 0℃ and humidity is much lower, grounding resistancealso varies greatly. In this case, bury ground markers deep into the soil and addadditive chemicals to satisfy requirements of grounding resistance.

à Grounding markers should use angle irons with a length smaller than 2 m. Ifconditions permit, it is recommended to use grounding nets.

Copper-coin connection cables must be used to connect grounding markers togrounding bolts attaching to main equipments. The sectional area cannot be lessthan 50 mm2. The cable length should be as short as possible, and sectional areaof copper cables should be extended if the cable length exceeds 50 m. Both endsof connection cables should be coated with tins or soaked with hot tins. Moreover,remove coating materials, varnishes, paints and oxidation layers away from fixingpoints. This is to ensure good contact between metallic surfaces.

à For all grounding junction pieces, corrosion protection is necessary. Use amechanical way to secure grounding bolts so that lower resistance connectioncan be guaranteed.

l Ensure that the grounding resistance is less than 1 ohm. Additionally, several factorsshould be considered, such as soil conditions, grounding body resistance, groundingcables, and so forth.

l Prior to commissioning equipments, grounding resistance should be measuredprecisely.

If the grounding resistance does not meet requirements, commissioning should bedelayed. Customers that still insist commissioning should present a written instructionand make promises to bear responsibility for any problems caused by grounding.Then, commissioning can be proceeded if ZTE Cooperation approves.

l For operating equipments, maintenance personnel should measure groundingresistance periodically and keep records. If grounding resistance becomes larger,appropriate measures should be taken to reduce resistance to a satisfied level.

7.3 Temperature and Humidity RequirementsMuch higher or lower temperature or humidity in the equipment room will shorten theequipment lifespan.

7-2


Chapter 7 Environmental Requirements

l If the temperature exceeds the normal temperature by 10℃, the equipment lifespanis approximately shortened by fifty percent.

l In the case of much lower temperature, the performance of optical components andcrystal components cannot be guaranteed.

l Much higher humidity in a long term will result in degraded insulation performance ofinsulating materials and even leakage; and then all kinds of metallic components forthe equipments are corroded.

l Much lower humidity in a long term will result in drying shrinkage of insulationgaskets; and then connections of fastening bolts become loose. This will easilylead to discharge of strong static electricity and damages to CMOS circuits withinequipments.

Temperature and humidity in the equipment room should satisfy following requirements aslisted in Table 7-3.

Table 7-3 Temperature/Humidity Requirements

Temperature Relative Humidity

Long-Term Working

Conditions

Short-Term Working

Conditions

Long-Term Working

Conditions

Short-Term Working

Conditions

5 ℃ to 40 ℃ –5 ℃ to 50 ℃ 5% to 85% 5% to 90%

• Short-term operating conditions refer to that the successive operating time is not more than 96 hoursand the accumulated operating time per year is not more than 15 days.

7.4 Anti-EMI RequirementsThe equipment room must be far away from high-power radio transmitting stations, radiotransmitting stations and high-frequency, large-current equipments. The actual radiationto the equipment room should be controlled below 300 mV/m, and the magnetic intensityaround the equipment room should be less than 11 GS.

The following measures are taken to remove radiated interferences.

l Shield the equipment room or specific electromagnetic interference sources.l Install shielding walls between primary equipments and transmitters with

high-frequency radiation, and use different power lines.l Properly ground all cables and conductors inside pipes. Ground shielding layers of

all cables.l Twist signal cables and return cables to cancel induced voltage caused by radiation

interferences from lines.l Try to separately lay power cables and signal cables. Parallel layout should be

avoided.l Strictly separate grounding cables of DC and AC in the equipment room.

7-3



7.5 Anti-Lightning RequirementsLightning protection is an important measure to ensure the safe operating of equipments.The following measures must be followed during designing.

l When the height of main building itself or its auxiliary facilities (such as chimney,antenna, and water tower) is over 15 meters, effective lightning protection measuresare necessary in accordance with the lightning protection requirements for Class IIcivil buildings and constructions.

l In addition, measures should be taken to protect the equipment from the directlightning strike and incursion of lightning current. When a tall building is used as theequipment room, take adequate measures to protect against slide lightning that arefrequently encountered in lightning-intensive areas.

l Protective measures against sidestroke are taken in line with specific conditions. Forexample, connect the metal window shelf of a building to the lightning protection leadwire, or install horizontal lightning-protection metal straps on the external surface ofwall at particular place along the height of the building.

The following anti-lightning measures must be taken for main building of the equipmentroom.

l Anti-lightning grids or belts must be installed in parts vulnerable to lightning strokes.l Overhead lightning protection wire or lightning arrestor must be installed on top of

objects extruding out of a building such as chimney and antenna.l The sectional area of down lead of anti-lightning equipment cannot be less than 200

mm2, and the space cannot be greater than 30 m. For lightning grounding equipmentsin buildings, grounding resistance cannot be greater than 1 ohm if the joint groundingmode is applied, and cannot be greater than 10 ohm if the independent groundingmode is applied.

In the past, the buildings' lightning grounding and telecommunication/power system'sgrounding are independent, and larger spaces are reserved between each groundingbody. However, due to the limited sites for buildings, most of the spacing requirementsare not satisfied.

Actually, the buildings' lightning grounding and telecommunication/power system'sgrounding cannot be separated. The joint ground system should be appliedto the buildings' lightning grounding. That is, connect the telecommunicationsystem's working ground and protective ground, buildings' lightning ground andindustrial-frequency AC power system's ground together. In this case, groundingresistance requirements are higher.

l Outdoor cables and metal pipes must be grounded before entering building.l Actually, it is better to use metal components (such as reinforcing steels inside walls

and posts) of buildings as down leads for lightning grounding. These down leadsshould be electrically interconnected to ensure electric potential equalization.

l The telecommunication system-required grounding resistance is far lower than 10ohm, and grounding requirements for different telecommunication equipments are

7-4


Chapter 7 Environmental Requirements

various. It is necessary to determine the specific grounding resistance in accordancewith the minimum resistance requirements for each grounding equipment.

l Install proper lightning prevention equipments for the power supply along the lines ofmains input to the equipment room.

7.6 Anti-Static RequirementsFrequently, static electricity causes accumulative damages to components rather thanone-time damages, resulting in intermittent failures or degraded performance whenequipments operate. Moreover, static electricity will lead to software failures, electronicswitch and control circuits failures, and even malfunctions. Much attention should be paidto anti-static requirements of the system.

The following may cause the static induction.

l External electric field caused by outdoor high-voltage power transmission lines,thunder strike.

l Internal systems such as indoor environment, floor material, and structure of the entireequipment.

l Static discharge from the operation and maintenance personnel to the equipment.

The following measures should be taken to prevent static discharge from damaging theequipment.

l Equipment should be properly grounded.l Layer anti-static floor and ground it well.l Operation and maintenance personnel should wear anti-static wrist strap, connected

to the static electricity discharge hole in the rack.

7.7 IlluminationIllumination in the equipment room should satisfy the following requirements.

l Install incandescent lamps or configure emergent lightning equipment in properplaces between racks to facilitate equipment installation and maintenance. However,long-term, direct sunshine or light should be avoided to prevent the circuit boardsand other components from aging and deforming.

l It is recommended that use color glasses and non-transparent curtains for windows.l Use the daylight lamps installed into the ceiling for the main body of the equipment

room. The average illumination between 150 lx~250 lX is recommended.

7.8 Fire ControlThemain building of the equipment roommust meet the requirements of related fire controlstandards. Based on the local fire control regulations, the corresponding fire equipmentshould be equipped and sufficient fire passages should be reserved. Notice boards bearing"Key Fire Control Site" should be put at proper locations.

7-5



Neither the main equipment room nor the accessory equipment room should haveflammable and explosive materials placed inside. Warning boards bearing “No Smoking”or “Smoking prohibited” shall be located in notable places. Prepare for effectivefire-protection appliances and put them within the reach. Install effective fire protectionwater equipments in proper locations.

The water in store should suffice continuous fire-fighting for two hours. But the supplyingpipes (drainage pipes and rain pipes) should not traverse the equipment room; neithershall the fire hydrant be placed in the equipment room.

7-6


Chapter 8Complied StandardsThe NetNumen U31 system complies with the following standards.

ITU-T Proposalsl ITU-T M.3000, Overview of TMN recommendationsl ITU-T M.3010, Principles for a Telecommunications management networkl ITU-T M.3016, TMN security overviewl ITU-T M.3020, TMN Interface Specification Methodologyl ITU-T M.3100, Generic Network Information Modell ITU-T M.3101, Managed Object Conformance Statements for the Generic Network

Information Modell ITU-T M.3200, TMN management services and telecommunications managed areas:

overviewl ITU-T M.3300, TMN F interface requirementsl ITU-T M.3400, TMN Management Functionl ITU-T Temporary Document 69（IP Experts）: Revised draft document on IP access

network architecturel ITU-T X.701-X.709, Systems Management framework and architecturel ITU-T X.710-X.719, Management Communication Service and Protocoll ITU-T X.720-X.729, Structure of Management Informationl ITU-T X.730-X.799, Management functions

RFC Proposalsl RFC1157, Simple Network Management Protocoll RFC1213, Management Information Base for Network Management of TCP/IP based

internets: MIB-IIl RFC1901, Introduction to Community-based SNMPv2l RFC1902, Structure of Management Information for Version 2 of the Simple Network

Management Protocol （SNMPv2）l RFC1903, Textual Conventions for Version 2 of the Simple Network Management

Protocol （SNMPv2）l RFC1905, Protocol Operations for Version 2 of the Simple Network Management

Protocol （SNMPv2）l RFC2037, Entity MIB using SMIv2l RFC2233, The Interface Group MIB using SMIv2l RFC1558, A String Representation of LDAP Search Filtersl RFC1777, Lightweight Directory Access Protocoll RFC1778, The String Representation of Standard Attribute Syntaxes

8-1



l RFC1959, An LDAP URL Formatl RFC2251, Lightweight Directory Access Protocol （v3）

TMF Proposalsl GB901, A Service management Business Process Modell GB921，Enhanced Telecom Operations Mapl GB909，Generic Requirements for Telecommunications Management Building

Blocksl GB908，Network Management Detailed Operations Mapl GB914，System Integration Mapl GB917, SLA Management Handbook V1.5l NMF038, Bandwidth Management Ensemble V1.0l TMF508, Connection and Service Management Information Model Business

Agreementl TMF801, Plug and Play Service Fulfillment Phase 2 Validation Specification V1.0l TMF605, Connection and Service Management Information Modell NMF037, Sub-System Alarm Surveillance Ensemble V1.0

OMG Standardl Interworking Between CORBA and TMN System Specification V1.0

8-2


FiguresFigure 1-1 NetNumen U31's Location in an Network ................................................. 1-2

Figure 2-1 System Hardware Architecture................................................................. 2-1

Figure 2-2 NetNumen U31 Software Architecture...................................................... 2-3

Figure 4-1 NetNumen U31 Typical Networking.......................................................... 4-2

Figure 4-2 NetNumen U31 Centralized Deployment.................................................. 4-3

Figure 4-3 Distributed Deployment Solution (Fixed Access Network) ........................ 4-4

Figure 4-4 Layered Networking (Bearer Network) ..................................................... 4-5

Figure 4-5 Single-Client and Single-Server Networking Mode ................................... 4-6

Figure 4-6 Multi-Client and Single-Server Networking Mode ..................................... 4-6

Figure 4-7 Integrated Management for Fixed and Mobile Networks........................... 4-7

Figure 4-8 Integrated IT Device Management ........................................................... 4-9

Figure 4-9 End-to-End Service Assurance Solution................................................. 4-10

Figure 5-1 System Interfaces .................................................................................... 5-2

I


Figures


II


TablesTable 3-1 System management function Descriptions .............................................. 3-2

Table 3-2 Task Management Function Descriptions .................................................. 3-3

Table 3-3 Security Management Function Descriptions ............................................. 3-3

Table 3-4 Log Management Function Descriptions.................................................... 3-4

Table 3-5 Report Management Function Descriptions ............................................... 3-5

Table 6-1 Technical Parameters of the B6080-22 Cabinet ......................................... 6-1

Table 6-2 Technical Parameters of the E4140 Shelf .................................................. 6-2

Table 6-3 Performance Indexes ................................................................................ 6-2

Table 6-4 Power Consumption Specifications of the ATCA Blade Server................. 6-10

Table 7-1 Specifications of a DC Power Supply......................................................... 7-1

Table 7-2 Specifications of an AC Power Supply....................................................... 7-1

Table 7-3 Temperature/Humidity Requirements......................................................... 7-3

III


Tables


IV


GlossaryASCI- Advanced Speech Call Items

ATCA- Advanced Telecommunications Computing Architecture

BBS- Backplane of Baseband Subsystem

BOSS- Business and Operation Support System

CLI- Command Line Interface

CMOS- Complementary Metal-Oxide-Semiconductor

CORBA- Common Object Request Broker Architecture

CPU- Central Processing Unit

DB- Database

DDN- Digital Data Network

EMS- Element Management System

FTP- File Transfer Protocol

GUI- Graphical User Interface

IE- Internet Explorer

IETF- Internet Engineering Task Force

IP- Internet Protocol

ISDN- Integrated Services Digital Network

V



ITU-T- International Telecommunication Union - Telecommunication StandardizationSector

J2EE- JAVA 2 platform Enterprise Edition

JRE- Java Runtime Environment

LAN- Local Area Network

LCT- Local Craft Terminal

MAC- Media Access Control

MAN- Metropolitan Area Network

MIB- Management Information Base

MML- Man Machine Language

MTBF- Mean Time Between Failures

MTOSI- Multi-Technology Operations System Interface

MTTR- Mean Time To Recovery

NE- Network Element

NMS- Network Management System

OAM- Operation, Administration and Maintenance

OMG- Open Mobile Gateway

OMM- Operation and Maintenance Management

OPEX- Operating Expenditure

ORB- Object Request Broker

VI


Glossary

OSS- Operation Support System

PDU- Power Distribution Unit

PM- Performance Management

PPU- Protocol Process Unit

PSTN- Public Switched Telephone Network

QoS- Quality of Service

RPO- Recovery Point Objective

RTO- Recovery Time Objective

SAN- Storage Area Network

SFTP- Secure File Transfer Protocol

SNMP- Simple Network Management Protocol

SSH- Secure Shell

TL1- Transaction Language 1

TMF- Telecommunication Management Forum

TMN- Telecommunications Management Network

VCS- Virtual Cluster System

VII


NetNumen™U31R10 - EDGE · PDF fileTo follow the future network development trends, ZTE...

Documents

Transcript of NetNumen™U31R10 - EDGE · PDF fileTo follow the future network development trends, ZTE...