Huawei OMC IManager M2000 System Description

System Description of Huawei OMC iManager M2000

Huawei Technologies Co., Ltd.

Huawei OMC iManager M2000 System Description

Vietnam VMS BSS GSM Project Commercial In Confidence Page 1 of 34

Table of Contents

Chapter 1 System Introduction ....................................................................................................... 4 1.1 Overview of M2000............................................................................................................... 4

1.1.1 M2000 Management Function ................................................................................... 4 1.1.2 Network Product......................................................................................................... 4

1.2 Position of M2000 in Network ............................................................................................... 5

Chapter 2 System Characteristics .................................................................................................. 6 2.1 Overview of M2000 System Characteristics......................................................................... 6 2.2 Multi-platform Component-based Architecture ..................................................................... 6 2.3 Itf-N Network Management Interfaces.................................................................................. 6 2.4 Software Management.......................................................................................................... 6 2.5 Time Synchronization ........................................................................................................... 6 2.6 Log Management.................................................................................................................. 7 2.7 IP Device Management ........................................................................................................ 7 2.8 Custom Reports in the WEB Mode....................................................................................... 7

Chapter 3 System Architecture....................................................................................................... 8 3.1 Overview of M2000 System Architecture ............................................................................. 8 3.2 Physical Architecture ............................................................................................................ 8

3.2.1 Overview of Physical Architecture.............................................................................. 8 3.2.2 Physical Architecture of Single-Server Configuration ................................................ 8 3.2.3 Physical Architecture of HA Configuration ................................................................. 9 3.2.4 Typical Configuration of M2000 Server...................................................................... 9 3.2.5 Typical Configuration of M2000 Client ..................................................................... 11

3.3 Software Architecture ......................................................................................................... 11 3.3.1 Overview of Software Architecture........................................................................... 11 3.3.2 M2000 Server Software ........................................................................................... 12 3.3.3 M2000 Client Software............................................................................................. 12 3.3.4 Interfaces.................................................................................................................. 13

Chapter 4 Services and Functions ............................................................................................... 14 4.1 Overview of M2000 Services and Functions ...................................................................... 14 4.2 Centralized Topology Management.................................................................................... 14

4.2.1 Overview of Topology Management ........................................................................ 14 4.2.2 Topological Objects Management............................................................................ 14 4.2.3 Topological Navigation Tree .................................................................................... 15 4.2.4 Topological Map....................................................................................................... 15

4.3 Centralized Configuration Management ............................................................................. 15 4.3.1 Overview of Centralized Configuration Management .............................................. 15



4.3.2 NE Configuration...................................................................................................... 16 4.3.3 Configuration Data Query ........................................................................................ 16 4.3.4 Report on NEs and Links ......................................................................................... 16 4.3.5 Configuration Data Export........................................................................................ 16 4.3.6 Configuration Data Synchronization ........................................................................ 16

4.4 Centralized Fault Management........................................................................................... 16 4.4.1 Overview of Centralized Fault Management............................................................ 16 4.4.2 Real-Time Alarm Browse ......................................................................................... 17 4.4.3 Alarm Statistic and Query ........................................................................................ 17 4.4.4 Alarm Correlation Analysis....................................................................................... 17 4.4.5 Alarm Acknowledgement and Un-acknowledgement .............................................. 17 4.4.6 Alarm Database Auto Displacement ........................................................................ 17 4.4.7 Redefinition of Alarm Severity Levels ...................................................................... 17 4.4.8 Alarm Handling Experience Management ............................................................... 18 4.4.9 Alarm Synchronization ............................................................................................. 18 4.4.10 Alarm Filter ............................................................................................................. 18 4.4.11 Alarm Customization .............................................................................................. 18 4.4.12 Remote Notification of Alarms................................................................................ 18

4.5 Centralized Performance Management.............................................................................. 18 4.5.1 Overview of Centralized Performance Management ............................................... 18 4.5.2 Performance Data Collection ................................................................................... 19 4.5.3 Realtime Measurement ............................................................................................ 19 4.5.4 Performance Data Management .............................................................................. 19 4.5.5 Performance Alarm .................................................................................................. 20 4.5.6 Customized Counters............................................................................................... 20

4.6 Centralized Software Management .................................................................................... 21 4.6.1 Overview of Software Management......................................................................... 21 4.6.2 NE Software Version and License Management ..................................................... 21 4.6.3 NE Data Backup....................................................................................................... 21 4.6.4 File Transmission ..................................................................................................... 21

4.7 Centralized Security Management...................................................................................... 21 4.7.1 Overview of Security Management .......................................................................... 21 4.7.2 User Account and Group Management ................................................................... 21 4.7.3 User Authority Management .................................................................................... 22 4.7.4 Terminal Management ............................................................................................. 22 4.7.5 Log Management ..................................................................................................... 22

4.8 System Management.......................................................................................................... 23 4.8.1 Overview of System Management ........................................................................... 23 4.8.2 Remote Maintenance ............................................................................................... 23 4.8.3 Online Help............................................................................................................... 23 4.8.4 System State Monitor............................................................................................... 23 4.8.5 System Data Backup and Restoration ..................................................................... 23



4.8.6 System Un-installation ............................................................................................. 24 4.9 Itf-N Network Management Interface.................................................................................. 24 4.10 NTP................................................................................................................................... 24 4.11 Intelligent Report............................................................................................................... 24

Chapter 5 System Reliability ......................................................................................................... 25 5.1 Overview of M2000 System Reliability ............................................................................... 25 5.2 System Reliability................................................................................................................ 25

5.2.1 Data Security............................................................................................................ 25 5.2.2 Operation Security ................................................................................................... 25

5.3 Hardware Reliability............................................................................................................ 26 5.4 Software Reliability ............................................................................................................. 26

Chapter 6 System Specifications.................................................................................................. 27 6.1 Overview of M2000 System Specifications ........................................................................ 27 6.2 Performance Specifications ................................................................................................ 27

6.2.1 Overview of Performance Specifications ................................................................. 27 6.2.2 System Capacity ...................................................................................................... 27 6.2.3 Performance Data Storage Capacity ....................................................................... 28 6.2.4 Alarm Data Storage Capacity................................................................................... 29 6.2.5 Alarm Response....................................................................................................... 29

6.3 Environment Parameters .................................................................................................... 29 6.4 Reliability Specifications ..................................................................................................... 30

Appendix Acronyms and Abbreviations..................................................................................... 32



Chapter 1 System Introduction

1.1 Overview of M2000

iManager M2000 Mobile Element Management System (M2000 for short) serves to manage and maintain Huawei mobile network products. With this platform, you can manage the Huawei mobile equipment, including UMTS equipment, GSM equipment, CDMA equipment and IP equipment in a mobile network.

1.1.1 M2000 Management Function

The managements include the following aspects:

z Centralized fault management z Centralized performance management z Centralized configuration management z Centralized software management z Centralized topology management z Centralized security management z System management

1.1.2 Network Product

Table 1-1 shows Huawei mobile network products that M2000 can access to.

Table 1-1 The network products that M2000 can access to

NE Type Description Model

NodeB Radio network base station BTS3812/ BTS3806A/ BTS3806/ BTS3802C

RNC Radio Network Controller BSC6800

SGSN Serving GPRS support node SGSN9810

GGSN Gateway GPRS support node GGSN9811

MSC Server Mobile switching center server MSOFTX3000

MGW Media gateway UMG8900

HLR Home location register HLR9820/HLR36

CG Charging Gateway CG9812



NE Type Description Model

PCU Packet Control Unit /

BSC Base Station Controller BSC32

BTS Base Transceiver Station BTS312/BTS3002C/BTS3012A

1.2 Position of M2000 in Network

M2000 is located at the element management (EM) layer in the telecommunication management network (TMN) model. It provides interfaces in compliance with 3GPP network management standards to network management system (NMS). Figure 1-1 shows a M2000 networking application.

Figure 1-1 M2000 networking application



Chapter 2 System Characteristics

2.1 Overview of M2000 System Characteristics

M2000 has the following characteristics:

z Multi-platform component-based architecture z Itf-N network management interfaces z Software management z Custom reports in the WEB mode z Time synchronization z Log management z IP device management

2.2 Multi-platform Component-based Architecture

M2000 supports several kinds of hardware platforms, including UNIX server and PC server, and Sybase database. Adopting the common object request broker architecture (CORBA) technology enables M2000 to expand capacity smoothly to meet network management requirements.

2.3 Itf-N Network Management Interfaces

M2000 supports the following Itf-N network management interfaces:

z Itf-N interface of CORBA interface format, in compliance with 3GPP R99/R4 z File interface, through which M2000 sends files containing information of alarm,

performance and configuration to the NMS z Database interface, through which the NMS visits the M2000 performance

database z Alarm transfer, through which M2000 sends processed NE alarms to the NMS

2.4 Software Management

M2000 can upload or download NE-related software, patch, license, data and other files from or to managed network elements (NE). It also manages software versions, including querying, activating and falling back the software.

2.5 Time Synchronization

M2000 provides network time protocol (NTP) services to ensure that NEs and M2000 can synchronize in time.



2.6 Log Management

There are three types of logs: operation logs, system logs and debugging logs. Operation logs record all user operations on both the M2000 and on NEs.

Log management includes log query, log statistics analysis and log displacement.

2.7 IP Device Management

IP device of mobile network can be as a specific NE managed by M2000. You can query configuration data and alarms of IP device.

M2000 only supports to manage Huawei IP device now.

2.8 Custom Reports in the WEB Mode

M2000 provides report system. You can customize templates and contents of performance reports, print, query and perform statistics to reports generated.

The report system provides WEB style user interface.



Chapter 3 System Architecture

3.1 Overview of M2000 System Architecture

The working mode of the M2000 system is Client/Server. The M2000 software is divided into Client software and Server software, which are independent of each other. The Client software runs on Clients and the Server software runs on the Server.

The hardware of an M2000 Client is a PC. An M2000 can have multiple Clients.

This chapter introduces the physical architecture and software architecture of the M2000 system.

3.2 Physical Architecture

3.2.1 Overview of Physical Architecture

A typical M2000 system includes Server(s), Client(s), Alarm Box(es), and networking equipment. You can perform remote operation and maintenance through public switched telephone network (PSTN) using a dial-up Server.

3.2.2 Physical Architecture of Single-Server Configuration

Figure 3-1 illustrates the M2000 system in single-server configuration.

Alarm box Client 1 Dial-up server

Server

PSTN

Client 2

Figure 3-1 M2000 system in single-server configuration



3.2.3 Physical Architecture of HA Configuration

Figure 3-2 illustrates the physical architecture of the M2000 system in HA configuration.

Active server

TC

Standby server

Diskarray

Alarm boxClient 1

Dial-up server

PSTN

Client 2

Clusterconsole

Figure 3-2 M2000 system in HA configuration

The following introduces the server-side equipment illustrated in Figure 3-2:

z Active and standby servers: work as the Server of the M2000 system. The M2000 server software runs on them. The monitor and switchover between the active and standby servers are realized through SUN Cluster scheme.

z Disk array: Provides active-standby protection for the data in the active and standby servers, and maintains data synchronization between the two servers.

z Cluster console: Provides single point management for the cluster system and the databases, and handles cluster related faults.

z TC(Terminal Connector): Connects the cluster console with active and standby servers.

3.2.4 Typical Configuration of M2000 Server

According to the total number of NEs managed by M2000, many types of equipment can serve as M2000 Server. The typical equipment is Sun Netra 240, Sun Fire V880 or Sun Fire E4900. For HA configuration, the system requires a Sun Blade150 as the cluster console.

I. Typical Single-Server Configuration

Table 3-1 lists the typical single-server configuration of the M2000 Server.

Table 3-1 Typical single-server configuration

Sun Netra 240 Sun Fire V880 Sun Fire 4800

CPU 2 CPU/1.28 GHz 4 CPU/1.2 GHz or 8 CPU/1.2 GHz 4 CPU/1.2 GHz 8 CPU/1.2 GHz

Memory 4 GB 8 GB 16 GB 32 GB



Sun Netra 240 Sun Fire V880 Sun Fire 4800

Hard disk 2 x 73 GB 6 x 73 GB 2 x 73 GB

Disk array None 3310 (73 GB x 8) x 1 6120 (73 GB x 9) x 2

Accessories

DVD/Network Adapter/Tape drive DATA72/English Documentation

DVD/Network Adapter/Tape drive DDS4/English Documentation

DVD/Network Adapter/Tape drive DATA72/English Documentation

Operating system

Solaris 8/English Documentation Solaris 8/English Documentation Solaris 8/English Documentation

Database Sybase 12.0/English Documentation

Sybase 12.0/English Documentation Sybase 12.0/English Documentation

Application software

M2000 Server application software M2000 Server application software M2000 Server application software

II. Typical HA Configuration

Table 3-2 lists the configurations of different types of servers for HA configuration.

Table 3-2 M2000 server configuration for HA configuration

Sun Netra 240 Sun Fire V880 Sun Fire E4900

CPU 2CPU/1.28 GHz 4CPU/1.2 GHz 8CPU/1.2 GHz 4CPU/1.2 GHz 8CPU/1.2 GHz

Memory 4 GB 8 GB 16 GB 32 GB

Hard disk 73 GB x 2 73GB x 6 73 GB x 2

Disk array 3310 (73 G hard disk x 5) x 2 3310 (73 G hard disk x 8) x 2 6120 (73 G hard disk x 9) x 2

Accessories

DVD/Ethernet adapter/DATA72 tape drive/user manuals

DVD/Ethernet adapter/TC/DDS4 tape drive/user manual

DVD/Ethernet adapter/TC/DATA72 tape drive/user manual

Operating system

Solaris 8/user manual Solaris 8/user manual Solaris 8/user manual

Database Sybase 12.0/user manual Sybase 12.0/user manual Sybase 12.0/user manual

Application M2000 Server applications M2000 Server applications M2000 Server applications

Table 3-3 lists the configuration of Sun Blade 150.



Table 3-3 Configuration Blade 150

Item Recommendation

CPU 650MHz

Memory 512MB

Hard disk 80 GB

Accessory CDROM/Ethernet adapter/Sound card/17 display

Operating system Solaris 8

3.2.5 Typical Configuration of M2000 Client

The M2000 Client runs on Windows 2000. Table 3-4lists the recommended PC environment.

Table 3-4 PC environment recommended for M2000

Item Recommendation

CPU P4/2.8 GHz

Memory 512 MB

Hard disk 80 GB

Accessories CDROM/Floppy Drive/Ethernet Adapter/Sound Card/17 LCD Display

Operating system Windows 2000 professional SP2 (or later)

Application software M2000 Client application software

3.3 Software Architecture

3.3.1 Overview of Software Architecture

M2000 software comprises two sub-systems: M2000 Server software and M2000 Client software. M2000 Client and Server software communicate with each other through a CORBA software bus. In addition, M2000 provides a report tool. You can use it to customize reports. Figure 3-3 shows the software modules of M2000.



Topologymanagement

Server

Configurationmanagement

Itf-NInterface

Performancemanagement

Securitymanagement GUI

ReportSystem

Client

NMS

CORBA Software Bus

Optional

Softwaremanagement Mediation

NE

Faultmanagement

MML interface/SNMP/Bin

Itf-N

Figure 3-3 Software modules of M2000

3.3.2 M2000 Server Software

M2000 Server software consists of eight software modules which are:

z Topology management module z Configuration management module z Performance management module z Security management module z Fault management module z Software management module z Itf-N interface module z Mediation module

3.3.3 M2000 Client Software

The M2000 Client software provides graphic user interface (GUI) for users. You can use the M2000 Client to manage and maintain all the NEs in the following aspects:

z Observing operation status z Retrieving alarm information in real time z Querying performance data z Configuring data z Managing software



3.3.4 Interfaces

M2000 resides between the NMS and NE and provides interfaces to both sides.

M2000 provides various Itf-N interfaces for communication with different NMS systems. For details, refer to 4.9 Itf-N Network Management Interface.

M2000 manages mobile network elements (NEs) through man machine language (MML) interfaces or binary interface, and manages IP devices through Simple Network Management Protocol (SNMP).



Chapter 4 Services and Functions

4.1 Overview of M2000 Services and Functions

M2000 provides the following functions:

z Centralized topology management z Centralized configuration management z Centralized fault management z Centralized performance management z Centralized software management z Centralized security management z System management z Itf-N network management interface z Time synchronization

4.2 Centralized Topology Management

4.2.1 Overview of Topology Management

M2000 provides topology management for all NEs in the entire network, including the following aspects:

z Topological objects z Topological navigation tree z Topological map

4.2.2 Topological Objects Management

Topological object management includes the following aspects:

z Topological object creation, modification and deletion z NE status view z Search for specified NE z Bulk operations on NEs z NE display filtering

I. Topological Object Creation, Modification and Deletion

You can create topological objects, which can be NEs, virtual NEs and links, directly on a topology map, modify configured data of topological objects, drag or delete topological objects. You can create NEs in batches.



II. NE Status View

On the topology map, you can view status of all NEs managed by M2000, including normal status and faulty status (four severity levels) as well as communication status between NE and M2000, such as synchronization and disconnection.

III. Search for Specified NE

You can search a specified NE on the topological map by NE name, software version, equipment supplier or IP address. Both precise search and fuzzy search are supported.

IV. Bulk Operations on NEs

M2000 provides bulk operations on NEs, with which you can create, delete and synchronize multiple NEs at one time.

V. NE Display Filtering

The system displays or shields certain types of NEs as required.

4.2.3 Topological Navigation Tree

When the system is very large, there will be many topological objects. You can easily find these NEs through the topological navigation tree.

4.2.4 Topological Map

You can change background map and choose suitable locations for NEs as needed. The background map can be a vector map, which can locate NEs accurately.

You can display NEs on the map hierarchically using subnets.

You can activate NE LMTs from the NEs on the topology map.

4.3 Centralized Configuration Management

4.3.1 Overview of Centralized Configuration Management

M2000 provides centralized configuration management for all NEs in the entire network, including the following aspects:

z NE configuration z Configuration data query z Report on NEs and links z Configuration data backup and restoration z Data synchronization configuration



4.3.2 NE Configuration

Through the MML interfaces of M2000, you can send one or more MML commands to NEs to configure them.

You can edit a MML command script file and execute the script file through MML interface of M2000. You can also create a task to execute the MML commands periodically.

4.3.3 Configuration Data Query

You can query NE configuration data as required. M2000 displays the query result in a report.

4.3.4 Report on NEs and Links

M2000 provides reports on the configuration data of NEs and links.

4.3.5 Configuration Data Export

M2000 supports configuration data export. The storage media can be hard disks or tapes. You can manually export the configuration data of an NE to .xml or .cvs files and save them in the specified directory in the server.

4.3.6 Configuration Data Synchronization

The M2000 system can synchronize the configuration data either automatically or manually. Auto configuration data synchronization means that the configuration change of an NE is automatically reported to M2000 upon update. Manual configuration data synchronization means that the user manually synchronizes the configuration data on an M2000 Client.

4.4 Centralized Fault Management

4.4.1 Overview of Centralized Fault Management

M2000 provides centralized fault management for all NEs in the entire network, including the following aspects:

z Real-time alarm browse z Alarm and statistic query z Alarm correlation analysis z Alarm acknowledgement z Alarm database auto displacement z Redefinition of alarm severity levels z Alarm handling experience management



z Alarm synchronization z Alarm filter z Alarm customization z Remote notification of alarms

4.4.2 Real-Time Alarm Browse

You can browse real-time alarms of all NEs and M2000 to find out severities and types.

M2000 highlights fault alarms unprocessed for a long time.

M2000 provides audible and visual alarms through the alarm window on M2000 Client or its alarm box.

4.4.3 Alarm Statistic and Query

You can query current alarms, event alarms and history alarms according to specified conditions. You can get statistic results.

4.4.4 Alarm Correlation Analysis

M2000 stores key information in the database and drops redundant information after performing correlation analysis on all received alarms. In this way, M2000 assists operators to locate faults quickly.

4.4.5 Alarm Acknowledgement and Un-acknowledgement

You may acknowledge alarms to identify themselves as taking corrective action. You can also un-acknowledge the alarms that you have acknowledged, meaning that the alarm has not been processed yet.

4.4.6 Alarm Database Auto Displacement

It includes two types of displacement: periodical displacement and displacement when the alarm database capacity exceeds the upper limit. The former includes setting of displacement cycle, displacement content and displacement format, while the latter includes setting of upper limit of the database capacity, displacement content and displacement format. The format of a displaced file can be TXT, XML or HTML.

4.4.7 Redefinition of Alarm Severity Levels

You can redefine alarm severity levels as needed.



4.4.8 Alarm Handling Experience Management

You can put the alarm handling experiences, such as fault location and handling suggestions, to the alarm knowledge database. You can also query the database for information you need according to the alarm Identity (ID) and knowledge content. This function is very helpful for troubleshooting.

4.4.9 Alarm Synchronization

The M2000 system supports auto and manual alarm synchronizations. Auto alarm synchronization means that the alarm change of an NE is automatically reported to M2000 upon update. Manual alarm synchronization means that the user manually synchronizes alarm information on an M2000 Client.

4.4.10 Alarm Filter

M2000 can filter specified alarms. When you screen an alarm from NEs, M2000 saves this alarm but does not display it to you.

You can define the filter conditions by alarm level, alarm ID, alarm type and time segment.

4.4.11 Alarm Customization

You can define an alarm with a specified ID and reported through a specified port of the NE as an alarm with a specified ID on M2000.

4.4.12 Remote Notification of Alarms

As per the preset conditions, M2000 can forward alarm information by pager, E-mail or SMS. You can configure the conditions through M2000 Client.

4.5 Centralized Performance Management

4.5.1 Overview of Centralized Performance Management

Centralized performance management is to authenticate the network performance specifications to provide references for network planning and maintenance.

Centralized performance management includes the following aspects:

z Performance data collection z Performance data management z Realtime measurement z Performance alarm z Customized counters z Template management



4.5.2 Performance Data Collection

I. Overview of Performance Data Collection

This function includes performance object management and performance counter management.

II. Performance Object Management

Through the M2000 Client, you can view and specify objects from which the performance data is collected.

III. Performance Counter Management

The performance counters of an NE include Key Performance Indices (KPI) and extension counters. The data collection of KPIs is mandatory to the M2000 system. The data collection of extension counters is optional. You can specify the extension counters to be used to collect performance data through the M2000 Client.

4.5.3 Realtime Measurement

The M2000 system supports realtime measurement. This function enables you to view a measurement result shortly after it is collected. You can use this function to carry out timely fault location and test for the equipment or network. The period of a realtime measurement is 5 minutes or 15 minutes.

You can specify objects and counters, and query and export the measurement results through the M2000 Client.

4.5.4 Performance Data Management

Performance data management includes the following aspects:

z Performance data report z Performance data storage z Performance data query z Data query template measurement z Time of performance data missing query z Flexible report z Performance data subscription

I. Performance data Report

M2000 reports performance data to multiple NMSs. It supports both active report and passive query.



II. Performance data Storage

M2000 can export performance data to files in a specified format. The format can be HTML or CSV.

III. Performance data Query

You can query, sort, display and print performance data.

IV. Data query template management

The M2000 system provides performance data query templates. Each template contains information such as objects, counters and query time. You can customize, delete or modify these templates.

You can create directories to classify the templates.

The M2000 system provides default template groups and templates for easier management.

V. Performance data missing time segment query

This function enables you to query the time segment when the specified performance data is lost.

VI. Flexible Report

With the report system, M2000 provides some commonly used or standard report templates. You can also create report templates.

VII. Performance data Subscription

You can subscribe the desired performance data. After subscription, you can browse performance data according to the measurement cycle.

4.5.5 Performance Alarm

You can set alarm thresholds. M2000 generates the corresponding alarm when a result exceeds the relative threshold.

4.5.6 Customized Counters

You can combine existing performance counters to define new measurement counters. You can also share your customized counters with other users.



4.6 Centralized Software Management

4.6.1 Overview of Software Management

M2000 provides centralized management on software versions and data of all NEs in the entire network. Software management includes the following aspects:

z NE software version and license management z NE data backup z File transmission

4.6.2 NE Software Version and License Management

M2000 stores different software version, license information and files of managed NEs. You can load and activate a version to single or multiple NEs through M2000.

4.6.3 NE Data Backup

M2000 backs up data of managed NEs, including configuration, performance, alarm and log data.

4.6.4 File Transmission

M2000 provides fast and convenient file transmission between M2000 Client and M2000 Server and between M2000 Server and NE. You can transmit a batch of files from M2000 to multiple NEs or from multiple NEs to M2000 through one operation.

4.7 Centralized Security Management

4.7.1 Overview of Security Management

Security management includes the following aspects:

User account and group management User authority management Terminal management Log management

Unless clarified, all functions are applicable to all NEs.

4.7.2 User Account and Group Management

To log in to and use M2000, you must have a user account. M2000 user account information consists of four main components:

z User name: the user name that a user uses to log in to the M2000 system.



z Password: A secret combination of characters that a user must enter with a user name to gain access to M2000.

z Login time: A time segment when a user can log in to M2000. z User group: Each user account belongs to one or more user groups to have

specified operation and maintenance rights on NEs, or to have administration rights on M2000.

M2000 automatically creates the user account admin and the user group Administrators during installation of the system. The user admin belongs to Administrators and has all the administration, operation and maintenance rights.

4.7.3 User Authority Management

This function enables you to manage user operation authorities, user login time, user login Client addresses, user operation and maintenance status management and user MML authorities on NEs.

You can be authorized with MML operation authority on a specified NE to execute the corresponding MML commands on that NE from an M2000 Client or the NEs LMT. GSM NEs, CDMA NEs and IP equipment does not support this function.

4.7.4 Terminal Management

To avoid illegal login, the system will lock a terminal that has been idle for a certain period. The user also can lock the terminal manually.

To conduct operations, the user should log in to the system again.

4.7.5 Log Management

There are three types of logs: operation log, system log, debugging log and NE operation log.

z Operation logs record all user operation events in M2000. z System logs record all system important events, such as network failures and

attacks against the system, to facilitate troubleshooting and analysis of system status.

z Debugging logs help locate system problems. z An NE operation log records user operations on this NE. M2000 can collect the

operation logs from NEs. You can query these logs through the M2000 Client.

Log management includes the following three aspects to operation logs:

z Log query: You can set query conditions to view logs, print or save the query results as files.



z Log statistics analysis: You can quickly find out system operation status using this function, for example, which period contains most of operations and what are the most commonly performed operations.

z Log displacement: M2000 performs automatic log displacement when the capacity exceeds the limit. You can also manually displace logs.

4.8 System Management

4.8.1 Overview of System Management

System management includes the following aspects:

z Remote maintenance z Online Help z System state monitoring z System data backup and restoration z System un-installation

4.8.2 Remote Maintenance

M2000 supports TCP/IP. By means of dial-up server, M2000 supports dial-up access through PSTN.

4.8.3 Online Help

M2000 provides detailed and convenient help information of MML commands, alarms and performance counters of all the managed NEs and instructions on system operations and maintenance.

To invoke the online help, you can:

z Select [Help/Topics] in the window titled with iManager M2000 Mobile Element Management System, or

z Press when any M2000 window or dialog box is active, or z Select [Start/Program/ iManager M2000/ M2000 Client Help].

4.8.4 System State Monitor

You can query the states of the processes and resources in the server and all software installed in the M2000 Server in real time.

4.8.5 System Data Backup and Restoration

The system data, including security data, log date, NE alarm data and performance data, can be backed up periodically or manually, and the backup data should be restored manually.



4.8.6 System Un-installation

After being uninstalled, the system will be restored to the status before installation.

4.9 Itf-N Network Management Interface

M2000 supports the following Itf-N network management interfaces:

z Itf-N interface of CORBA interface format, in compliance with 3GPP R99/R4 z File interface, through which M2000 sends files containing information of alarm,

performance and configuration to the NMS z Database interface, through which the NMS visits the M2000 performance

database z Alarm transfer, through which M2000 sends processed NE alarms to the NMS

4.10 NTP

M2000 provides NTP services to synchronize time between NEs and M2000. With this function, you can ensure the consistency between network management data. This improves your network status analysis.

The time source can either be provided by the NMS Server or other sources. You can define the calibration time.

4.11 Intelligent Report

The M2000 system provides Web intelligent reports. You can select the format and contents of a report.



Chapter 5 System Reliability

5.1 Overview of M2000 System Reliability

M2000 system reliability is based on reliability design. The reliability design of M2000 comprises:

z System reliability z Hardware reliability z Software reliability

5.2 System Reliability

System reliability design includes the following aspects:

z Data security z Operation security

5.2.1 Data Security

All the M2000 system data, including performance data, alarm data, configuration data, security data and log data, is collectively saved at the database of M2000 Server. High security of the database and backup and restoration function for the system data ensure the reliability of system data.

I. Backup Mechanism

M2000 provides automatic and manual backup function.

It automatically backs up system data every day, every week or every month. With manual backup function, you can perform the backup command anytime.

The backup data can be output to external media.

II. Restoration Mechanism

In case there is data damaged due to system failure or upgrade failure, you can execute the restoration command to restore the system data.

5.2.2 Operation Security

I. Limit to Login

M2000 limits the number of login attempts (the number is configurable). If the number of login attempts of a user exceeds the maximum, M2000 will lock the user, records the



failure information in the system log and generates an internal alarm at the same time. After a period time (normally 30 minutes), M2000 will unlock the user.

II. User Monitor

M2000 monitors operations of all users, and generates maintenance reports. The user admin has the right to kick out any user.

III. Operation Confirmation

M2000 provides confirmation function for important or global operations.

5.3 Hardware Reliability

M2000 hardware supports dual-system mode. Two servers constitute a symmetrical high availability (HA) system through dual-system software and work in active/standby mode. M2000 features high reliability and running without interruption. It also supports single-system mode for the purposes of installation convenience and cost saving. In this mode, it adopts disk mirror.

5.4 Software Reliability

M2000 provides self-protection mechanism and checks the states of all M2000 services periodically. For any fault detected, M2000 records the failure information in the system log, resumes the service automatically or generates an alarm to get manual assistance.



Chapter 6 System Specifications

6.1 Overview of M2000 System Specifications

This chapter introduces system specifications, including

z Performance specifications z Environment parameters z Reliability specifications

6.2 Performance Specifications

6.2.1 Overview of Performance Specifications

The system performance depends on following aspects:

z System capacity z Performance data storage capacity z Alarm data storage capacity z Alarm response

6.2.2 System Capacity

Table 6-1 describes the system capacity.

Table 6-1 M2000 system capacity

Mode 1 Mode 2 Mode 3 Mode 4 Mode 5

Network scale (number of equivalent NEs)

< 15 < 30 < 55 < 60 < 120

Hardware configuration

Sun Netra 240 Server

4CPU Sun Fire V880 Server

4CPU Sun Fire E4900

8CPU Sun Fire V880

8CPU Sun Fire E4900 Server

The number of equivalent NEs depends on the complexity of NEs used. Table 6-2 lists the number of equivalent NEs of UMTS NEs. Table 6-3 lists the number of equivalent NEs of GSM NEs. Table 6-4 lists the number of equivalent NEs of CDMA NEs. IP equipment does not have any equivalent NE.

Table 6-2 Number of equivalent NEs of UMTS NEs

NE Number of equivalent NEs

RNC + NodeB 50 cells = 1 equivalent NE




MSC Server 4

SGSN 2

MGW 0.2

GGSN 0.1

HLR 0.1

CG 0.04

SIWF 0.04

Table 6-3 Number of equivalent NEs of GSM NEs


BSC+ BTS 60 cells = 1 equivalent NE

MSC 1

PCU 1

HLR 0.1

Table 6-4 Number of equivalent NEs of CDMA NEs


BSC+ BTS 60 cells = 1 equivalent NE

MSC Server 4

MSC 1

PDSN 1

MGW 0.2

HLR 0.1

RAC+RAU 50 cells = 1 equivalent NE

6.2.3 Performance Data Storage Capacity

The M2000 system stores performance data of all NEs for at least three months. The number of NEs under management and the specific performance data to be stored depend on the type of the server.

The following is the details:



z Sun Netra240 stores three-months performance data of at least one million counters.

z Sun Fire V880 stores three-months performance data of at least three million counters.

z Sun Fire E4900 stores three-months performance data of at least six million counters.

6.2.4 Alarm Data Storage Capacity

The M2000 system classifies alarms into the following types:

z Current fault alarm: Generated when faults occurs to the system. When the faults are cleared and the system recovers, the corresponding fault alarm is labeled as Cleared".

z Event alarm: Instant status report during system operation. z History fault alarm: Current fault alarm known and acknowledged by the system

maintenance personnel and labeled as cleared. z Screened alarm: Alarm not displayed to the user as requested.

The number of NEs under management and the storage capacity depend on the type of the server. The following is the details:

z Sun Netra240: one million entries for each type of alarm z Sun Fire V880: 7.5 million entries for each type of alarm z Sun Fire E4900: 12.5 million entries for each type of alarm

6.2.5 Alarm Response

Generally, when an alarm occurs on NE, it will be displayed on M2000 Client in 5 to 6 seconds.

Hardware configuration of M2000 server determines alarm-handling capacity. For Sun Netra 240, it is up to 60 alarms per second for 40 minutes, for Sun Fire V880, it is up to 100 alarms per second for 40 minutes, for Sun Fire 4800, it is up to 160 alarms per second for 40 minutes.

6.3 Environment Parameters

Table 6-5 lists parameters of system operational environment.



Table 6-5 System operational environment parameters

Equipment Item

M2000 Client M2000 Server

Hardware platform P4 CPU/256M memory/40G Hard Disk (HD) or above Sun Netra 240, Sun Fire V880 or Sun Fire 4800

Software platform Windows 2000 professional operating system Operating system: Sun Solaris 8; Database: Sybase 12.0

Power consumption 250 W

Sun Netra 240: Single Server 600 W, Dual Server 1700 W Sun Fire V880: Single Server 1975 W, Dual Server 3490 W Sun Fire E4900: Single Server 5180 W, Dual Server 9360 W

Normal working range:15C - 35C Temperature

Safe working range: 0 C - 45 C Normal working range: 30% - 65%

Humidity Safe working range: 10% - 90%

6.4 Reliability Specifications

The reliability of an M2000 system depends on its server type and server configuration mode. Table 6-6 lists the reliability indices of single-server configuration. Table 6-7 lists the reliability indices of HA configuration.

Table 6-6 Reliability indices of single-server configuration

Server Type Sun Netra 240 Sun Fire V880 Sun Fire E4900

MTBF 42566 hours 10420 hours 47313 hours

Total system failure duration every year

0.522211 hours 2.485872 hours 0.112182 hours

System availability 99.994039% 99.971622% 99.998719%

MTTR 1.3095 hours 1.6320 hours 0.4483 hours



Table 6-7 Reliability indices of HA configuration

Server Type Sun Netra 240 Sun Fire V880 Sun Fire E4900

MTBF 5858.0 hours 4969.0 hours 23476.0 hours Total system failure duration every year

3.715982 hours 6.127225 hours 0.897662 hours

System availability 99.957801% 99.930055% 99.989753% MTTR 0.5212 hours 1.5121 hours 0.4419 hours



Appendix Acronyms and Abbreviations

Numeric

3GPP 3rd Generation Partnership Project

C

CDMA Code Division Multiple Access

CG Charging Gateway

CORBA Common Object Request Broker Architecture

CPU Center Processing Unit

CSV Comma Separation Value

E

EM Element Management

EMS Element Management System

G

GB Gigabyte

GGSN Gateway GPRS Support Node

GHz Gigahertz

GLMS Group and List Management Server

GSM Global System for Mobile communications

GUI Graphic User Interface

H

HA High Availability

HD Hard Disk

HLR Home Location Register

HTML Hyper Text Markup Language

I

ID Identity

IRP Integration Reference Point

K

KPI Key Performance Index

L

LAN Local Area Network



LMT Local Maintenance Terminal

M

MSC Mobile Service Switching Center

MSC Server Mobile Service Switching Center Server

MTBF Mean Time Between Failures

MTTR Mean Time To Repair

MGW Media Gate-Way

MML Man Machine Language

N

NE Network Element

NMS Network Management System

NodeB WCDMA base station

NTP Network Time Protocol

P

PC Personal Computer

PCU Packet Control Unit

PDSN Packet Data Serving Node

PoC Push-To-Talk over Cellular

PSTN Public Switched Telephone Network

PTT Push to Talk

R

RAC Radio Access Controller

RAU Radio Access Unit

RNC Radio Network Controller

S

SGSN Serving GPRS Support Node

SNMP Simple Network Management Protocol

SMS Short Message Service

T

TMN Telecommunications Management Network

TSC Trunking Switching Center

W

WCDMA Wideband Code Division Multiple Access



X

XML Extensible Markup Language

Documents

Huawei OMC IManager M2000 System Description