OWL000100 iManager M2000 V2 System Overview ISSUE2.1

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved

www.huawei.com

Internal

OWL000100 iManager M2000 V2

System Overview

ISSUE 2.1

HUAWEI TECHNOLOGIES CO., LTD. Page 2All rights reserved

The iManager M2000 Mobile Element M

anagement System is a centralized mob

ile network management platform of Hu

awei. Using this platform, you can mana

ge the UMTS/GSM/CDMA/IP network el

ements (NEs), manufactured by Huawei.

This presentation covers the iManager

M2000V2 architecture, design ideas, fun

ctions and reliability.


Chapter 1 Product IntroductionChapter 1 Product Introduction

Chapter 2 M2000 ArchitectureChapter 2 M2000 Architecture

Chapter 3 Function IntroductionChapter 3 Function Introduction

Chapter 4 Configuration ListChapter 4 Configuration List


M2000Other EMS Other EMS

NE

NE NE

NetworkManagementLayer

ElementManagementLayer

NE

NMS

Network Position of iManager M2000

In Telecommunication

Management Network

(TMN), the M2000 is

located in the

Element

Management-layer

(EM-layer).


Network Deployment

M2000 Server

OMC Center

OMC Client2

NE1 NE2

OMC Client

Area 1

Alarm box

Alarm box

OMC Client1

NE1 NE2 NE3

Area 1 Area 2

Firewall

OMC Client(Administrator)

Alarm box

Area 2

Firewall

Alarm boxLMT LMT

E1/ATM/IP Backbone

NMS

SQL FtpASCII Stream


CN Standard Network Deployment

M2000 Server

OMC Center

CS OMC Client2

24-hour Alarm Monitoring Room

MGW MSC Server

PS OMC Client

Area 1

Alarmbox

Alarmbox

CS OMC Client1

SGSN GGSN CG

PS Equipment Room CS Equipment Room

Firewall

OMC Client(Administrator)

Alarmbox

Area 2

Firewall

AlarmboxLMT LMT

E1/ATM/IP Backbone


iManager M2000V2 Ability

M2000V2 managed NEs can be UMTS/GSM/CDMA equipments a

nd IP devices. The M2000 cannot manage the CDMA NE with the

UMTS or GSM NE at the same time.

UMTS

NodeB

RNC

SGSN

GGSN

MSC Server

MGW

HLR

CG

SIWF

GSM

MSC

BSC

BTS

PCU

HLR

CDMA

MSC

MSC Server

MGW

PDSN

HLR

BSC

BTS

RAC

RAU

TSC

IP

Router

Switch

Firewall







Brief Introduction of System Architecture

The M2000 system works in client/server mode.

The M2000 software consists of the client software, server

software, and NE mediation software, which is mutually

independent. The client software runs on the client, and the

server software and mediation software run on the server.

The hardware of an M2000 client refers to a PC. An M2000

system can have multiple clients, and can have either one

server or two servers. The two servers constitute a High

Availability (HA) system.


M2000 Physical Structure Overview

A typical M2000 system consists of:

Servers

Clients

Alarm box

Other networking devices

Using a dial-up server, you can operate and maintain

the M2000 system through the Public Switched

Telephone Network (PSTN).


M2000 Physical Structure of Single Server System

Alarm box Client 1 Dial-up server

Server

PSTN

Client 2


M2000 Physical Structure of HA System

Active server

Standby server

Diskarray

Alarm boxClient 1

Dial-up server

Client 2

Cluster console

PSTN


M2000 Software Architecture Overview

The M2000 software consists of the following sub-systems:

Server Software

Client Software

NE mediation software

Using a dial-up server, you can operate and maintain the

M2000 system through the Public Switched Telephone

Network (PSTN).

Each NE version corresponds to an NE mediation software.


M2000 Software Architecture


M2000 Server Software Architecture

The M2000 server software consists of 13 modules.


M2000 Client Software


M2000 NE Mediation Software

The M2000 mediation module software consists of a series

of mediation software. Each piece of mediation software

corresponds to one or more NE versions.

The mediation software provides the interface files and

mediation files that the NE needs to access the M2000

system.


Questions

In one network, there are two CSOFTX3000, two UMG8900 and

one HLR9820 need to be connected to the M2000V2 server,

equipments versions are: CSOFTX3000 V100R001,

CSOFTX3000 V100R002, UMG8900 V100R002, UMG8900

V100R002, HLR9820 V100R002.

How many NE mediation software we need to install in M2000V2

server?


Interfaces (I)

External Interfaces

The M2000 provides interfaces for the NMS a

nd the managed NEs, Itf-N interfaces for vario

us NMS systems and Human Machine Langu

age (MML) interfaces or binary interfaces for

NEs, and manages the IP devices through the

Simple Network Management Protocol (SNM

P).

In addition, the files such as NE log files and

performance result files are transported throu

gh the FTP protocol between the M2000 and

managed NEs.

NE NENE

Inner interface

CORBAFILE SNMPASCII

Stream

iManager M2000

NMS


Interfaces (II)

Internal Interfaces

The server software, client

software and mediation

software in the M2000 system

communicate with each other

through the CORBA interface.

When the report tool is

installed, the report tool client

and the M2000 server

communicate in the WEB

mode.

SNMPMML FILE Other

iManager M2000

NE







M2000 Functions List

Centralized Topology Management

Centralized Configuration Management

Centralized Fault Management

Centralized Performance Management

Centralized Software Management

Centralized Security Management

Signaling Tracing

Equipment Panel

System Management

Itf-N Network Management Interface

Entire Network Time Management

Customizable Report


CConfigurationonfiguration Management ManagementFFaultault Management Management

SSecurityecurity Management Management

Securitystrategy

protect

detectrespond

DOS

Black list

authentication

encryptaccesscontrolinsulate

Alarm

Strategychange

firewall

Log

PPerformanceerformance Management Management

TTopologyopology Management Management

Basic Features


Centralized Topology Management

Topology Object

Management

Topology Navigation

Tree Management

Topology Map

Management

Management by

District


Centralized Configuration Management

NE Configuration

NE Configuration Query

Soft Switch Resource

Management

Resource Status Query

and Monitoring

NE and Link Report

NE Configuration

Export

NE Configuration

Synchronization


Centralized Fault Management

Real-Time Alarm Brows

Alarm Statistic and Query

Alarm Correlation Analysis

Alarm Acknowledgement

Alarm Database Displacement

Redefinition of Alarm Severity

Alarm Knowledge Base

Management

Alarm Synchronization

Alarm Shielding

Alarm Customization

Remote Alarm Notification


Centralized Performance Management

Performance Counter and

Performance Object

Management

Real-Time Measurement

Real-Time Monitoring

Performance Data

Management

Performance Alarm

Customized Counters



NE Software Version

Management

NE License Management

NE Data Backup

The software management applies only to the UMTS NEs.


OM Software Upgrade:

Automatic upgrading Clients

from server

NE Software Deployment / Upgrade:

Remote upgrading procedures

Multiple NE’ software upgrading

simultaneously in two steps

Minimum impact on live servicesStep1: Upgrade Server

Step2: Clients in different areas will be upgraded automatically

Area1 Area2 Area3

iManager M2000 Server

M2000 Client

iManager M2000 Server

Step1: Bulk DownloadStep2: Bulk Activate




M2000 security management provides:

User Account and Group Management

User Privilege Management

User Monitor

Terminal Management

Log Management User

System

Network



Login Authorization

IP address

Password

Valid User account

Date & time

Why can not be operated？

Not in correct time

Configuration

Management

MaintenanceRead

NEs

Rights

Joe Mike

Group 1

Ann Harry

Group 2

Before Login After Login

User group can combine with operation right on demand

System screen unauthorized command, and user can only find authorized NEs in GUI

Authentication & Authorization


Signaling Tracing

The signaling tracing is a key method used for locating the f

aults. The M2000 system traces user signaling messages of

the NEs.

You can create message tracing tasks on the M2000 client,

and specify an NE user to trace its signaling messages in re

al time. In addition, you can save these signaling messages i

nto files for later query.


Equipment Panel

Using the GUI on the M2000 client, you can carry out the

following operations:

View the hardware configuration of the NE devices, such as

the rack, frames, board and port.

View alarms occurring to the hardware of the NE devices.

Carry out device maintenance operations such as resetting

the boards.


System Management

The M2000 system management provides the following functions:

License Management

Remote Maintenance

Citrix Based Client Integration

Online Help

System Status Monitoring

System Data Backup and Restoration

System Uninstall


Entire Network Time Management

Time Zone Management

The M2000 system can manage the processes and faults occurr

ing within itself and NEs located in different time zones. It autom

atically processes the time change because of different time zon

es.

DST

The M2000 system supports the DST system and automatically

processes the time change.

Time Synchronization

The M2000 system provides NTP services to synchronize the N

Es with the M2000 system. With this function, you can ensure th

e consistency between network management data, thereby impr

oving the network status analysis.


The M2000 system

supports customizable

reports. You can

specify the format and

content of a report.

Design template freely

Choose data freely

Statistic periodically

+Template design

Basic data

Get what you wantGet what you wantGet what you wantGet what you want

Customizable Report

Alarm

Configuration

Performance







Typical Single-Server Configuration for M2000 Server

Sun Netra 240 Sun Fire V890 Sun Fire E4900

Number ofCPUs

2 2 4 8 4 8

Main Frequencyof the CPU

(GHz)

1.5 1.35 1.35 1.35 1.5 1.5

Memory (GB) 4 8 16 32 16 32

Hard disk (GB) 2 x 146 4 x 146 2 x 73

Disk array (GB) None 1 x 3320(A 3320 disk array consists of

eight 73 GB hard disks.)

1 x 6140(A 6140 disk array consists of

fourteen 73 GB hard disks)

Accessories DVD/Ethernetadapter/DATA72 tape

drive/Englishdocumentation

DVD/Ethernetadapter/DATA72 tape

drive/English documentation

DVD/Ethernet adapter/DATA72tape drive/English

documentation

Operatingsystem

Solaris 10/Englishdocumentation



Database Sybase 15.0/Englishdocumentation

Sybase 15.0/Englishdocumentation


Applicationsoftware

M2000 serverapplication software

M2000 server applicationsoftware



Typical HA Configuration for M2000 Server

Sun Netra 240 Sun Fire V890 Sun Fire E4900

Number of CPUs 2 2 4 8 4 8

Main Frequency ofthe CPU (GHz)

1.5 1.35 1.5

Memory (GB) 4 8 16 32 16 32

Hard disk (GB) 2 x 146 4 x 146 2 x 73

Disk array (GB) 2 x 3320(A 3320 disk array

consists of five 73 GBhard disks.)

2 x 3320(A 3320 disk array

consists of eight 73GB hard disks.)

1 x 6140(A 6140 disk array consists of fourteen 73GB hard disks.)

Accessories DVD/Ethernetadapter/DATA72 tape

drive/User manual


drive/User manual


drive/User manual

Operating system Solaris 10/Englishdocumentation



Database Sybase 15.0/Englishdocumentation



Application M2000 serverapplication software


M2000 serverapplication software


Typical Configuration for the Cluster Console (Sun Netra 240)

Item Configuration

CPU (GHz) 1.5

Memory (GB) 1

Hard disk (GB) 2 x 146

Accessories DVD/Display card/Ethernet adapter/KVM/User manual

Operating system Solaris 10


Common Networking Equipment

Item Configuration

RouterM2000 side: Quidway AR46-20NE side: Quidway AR28-13 and Quidway AR28-10

Switch and Hub Quidway S2016HI, Quidway S3928EI and 16-port Hub

Timeslot cross multiplexer

Mecury3600


Typical M2000 Client Configuration

Item Configuration

CPU P4/2.8 GHz

Memory 512 MB

Hard disk 80 GB

AccessoriesCDROM/Floppy Drive/Ethernet Adapter/Sound Card/17” LCD Display

Operating system Windows 2000 professional SP2 (or a later version)

Application software M2000 client application software


System Capacity

Configuration

Management capacity Server hardware

1 15 equivalent NEs Sun Netra 240 (2 CPUs)

2 25 equivalent NEs Sun Fire V890 (2 CPUs)


4 55 equivalent NEs Sun Fire E4900 (4 CPUs)


6 120 equivalent NEs Sun Fire E4900 (8 CPUs) According to the complexity of NEs:

For RAN, every 50 cells = 1 equivalent NE For MSC Server, each MSC Server = 4 equivalent NE ……


Performance Data Processing Capacity

Server model Performance data processing (message/hour)

Sun Netra 240 (2 CPUs) 1.2 million

Sun Fire V890 (2 CPUs) 1.8 million


Sun Fire E4900 (4 CPUs) 4.5 million


Sun Fire E4900 (8 CPUs) 9 million


Alarm Data Storage Capacity

Server hardware

Event alarm

History fault alarm

Current fault alarm

Shielded alarm

Sun Netra240 800 000 800 000 100 000 100 000

Sun Fire V890 5 000 000 5 000 000 600 000 600 000

Sun Fire E4900 7 000 000 7 000 000 800 000 800 000


Alarm Processing Capacity

Server Peak alarm processing capacity (record/second)

Sun Netra 240 (2 CPUs)

20

Sun Fire V890 (2 CPUs)

30


50

Sun Fire E4900 (4 CPUs)

55


90


100


Reliability Specifications

Server model MTBF (hour) MTTR (hour) Annual mean failure time (hour)

Availability (%)

Sun Netra 240 (2 CPUs)

42 566 1.3095 0.522211 99.994039%


17 732 0.6557 1.522984 99.982614%


16 138 0.5541 1.241355 99.985829%


47 313 0.4483 0.112182 99.998719%


15 889 0.4664 1.226084 99.986003%


47 313 0.4483 0.112182 99.998719%

www.huawei.com

Thank You

Documents

OWL000100 iManager M2000 V2 System Overview ISSUE2.1