M2000 Product Description (CDMA)

M2000 V200R008
Product Description
Issue V2.0
Date 2009-02-28
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks
and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the commercial contract made between
Huawei and the customer. All or partial products, services and features described in this document may not
be within the purchased scope or the usage scope. Unless otherwise agreed by the contract, all
statements, information, and recommendations in this document are provided “AS IS” without warranties,
guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Huawei Proprietary and Confidential

Issue V2.0 (2009-02-28) Page 2 of 77
Copyright © Huawei Technologies Co., Ltd.
M2000
Product Description
Contents
1 Introduction to the M2000 ..............................................................................................7

1.1 About the M2000 .............................................................................................................................. 7
1.2 Position of the M2000 in the Network .............................................................................................. 7
1.3 Interfaces of the M2000 ................................................................................................................. 13
2 Key Benefits ..................................................................................................................15

2.1 Challenges and Trends .................................................................................................................. 15
2.2 Advanced Componentized Architecture ......................................................................................... 15
2.3 Flexible Networking Mode.............................................................................................................. 16
2.4 Various Interfaces........................................................................................................................... 16
2.5 Powerful Operation and Maintenance Function............................................................................. 17
2.6 Comprehensive Operation and Maintenance Solution .................................................................. 17
3 System Architecture .....................................................................................................18

3.1 About This Chapter......................................................................................................................... 18
3.2 Physical Structure .......................................................................................................................... 18
3.2.1 Overview................................................................................................................................ 18
3.2.2 Physical Structure of the Single-Server System.................................................................... 18
3.2.3 Physical Structure of the HA System..................................................................................... 19
3.2.4 Typical M2000 Server Configuration ..................................................................................... 20
3.2.5 Typical M2000 Client Configuration....................................................................................... 25
3.3 M2000 Operating Environment ...................................................................................................... 26
3.3.1 Operating Environment for the M2000 Single-Server System .............................................. 26
3.3.2 Operating Environment for the M2000 HA System ............................................................... 26
3.4 Software Architecture ..................................................................................................................... 27
3.4.1 Overview................................................................................................................................ 27
3.4.2 M2000 Server Software......................................................................................................... 28
3.4.3 M2000 Client Software .......................................................................................................... 30
3.4.4 NE Mediation Software.......................................................................................................... 30
3.5 Interfaces........................................................................................................................................ 30
3.5.1 Northbound Interfaces ........................................................................................................... 30
3.5.2 Southbound Interfaces .......................................................................................................... 31
3.5.3 Internal Interfaces.................................................................................................................. 31
4 Services and Functions................................................................................................32

Issue V2.0 (2009-02-28) Page 3 of 77
M2000
Product Description

4.2 Topology Management ................................................................................................................... 32
4.2.1 Function Type ........................................................................................................................ 32
4.2.2 Topology Object Management............................................................................................... 32
4.2.3 Topology Object Viewing ....................................................................................................... 32
4.2.4 Topology Map Management .................................................................................................. 33
4.2.5 NE Management by District................................................................................................... 33
4.2.6 Shortcut Operation Access.................................................................................................... 33
4.3 Configuration Management............................................................................................................ 33
4.3.1 Function Type ........................................................................................................................ 33
4.3.2 Configuration Data Synchronization...................................................................................... 33
4.3.3 Configuration Data Query...................................................................................................... 34
4.3.4 Configuration Data Export ..................................................................................................... 34
4.4 Centralized Fault Management ...................................................................................................... 34
4.4.1 Function Type ........................................................................................................................ 34
4.4.2 Real-Time Alarm Monitoring .................................................................................................. 34
4.4.3 Alarm Data Management....................................................................................................... 35
4.4.4 Alarm Query and Statistics .................................................................................................... 35
4.4.5 Alarm Assisting Handling ....................................................................................................... 35
4.5 Centralized Performance Management ......................................................................................... 36
4.5.1 Function Type ........................................................................................................................ 36
4.5.2 NE Performance Measurement Setting................................................................................. 36
4.5.3 Real-Time Monitoring of Performance Results ..................................................................... 37
4.5.4 Performance Result Query.................................................................................................... 37
4.5.5 Performance Data Management ........................................................................................... 37
4.5.6 Performance Alarm................................................................................................................ 38
4.5.7 Custom Counters................................................................................................................... 38
4.5.8 Performance Report .............................................................................................................. 38
4.6 Centralized Security Management ................................................................................................. 38
4.6.1 Function Type ........................................................................................................................ 38
4.6.2 User and User Group Management ...................................................................................... 38
4.6.3 User Authority Management.................................................................................................. 39
4.6.4 User Monitoring ..................................................................................................................... 39
4.6.5 Terminal Locking.................................................................................................................... 39
4.6.6 Security Policy Setting........................................................................................................... 40
4.6.7 Log Management................................................................................................................... 40
4.7 System Management ..................................................................................................................... 41
4.7.1 Function Type ........................................................................................................................ 41
4.7.2 License Management ............................................................................................................ 42
4.7.3 Online Help............................................................................................................................ 42
4.7.4 System Status Monitoring...................................................................................................... 42
4.7.5 Centralized Scheduled Task Monitoring ................................................................................ 42

Issue V2.0 (2009-02-28) Page 4 of 77
M2000
Product Description
4.7.6 Individual Setting ................................................................................................................... 43

4.7.7 System Data Backup and Restore ........................................................................................ 43
4.7.8 System Installation and Uninstalling...................................................................................... 44
4.7.9 Client Remote Access ........................................................................................................... 44
4.7.10 Citrix-Based Client Access .................................................................................................. 44
4.8 Time Management for the Entire Network ..................................................................................... 44
4.8.1 Function Type ........................................................................................................................ 44
4.8.2 Time Zone Management ....................................................................................................... 45
4.8.3 DST Supported...................................................................................................................... 45
4.8.4 Time Synchronization for the Entire Network ........................................................................ 45
4.9 CBSS Specified Functions ............................................................................................................. 45
4.9.1 Custom NE Alarms ................................................................................................................ 45
4.9.2 Inventory Management.......................................................................................................... 46
4.9.3 Basic CBSS Navigation Configuration .................................................................................. 46
4.10 CN Specified Functions................................................................................................................ 47
4.10.1 Customized NE Alarms........................................................................................................ 47
4.10.2 Centralized User Management............................................................................................ 47
4.10.3 NE Configuration ................................................................................................................. 47
4.10.4 Inventory Management........................................................................................................ 48
4.10.5 NE Resource Monitoring ..................................................................................................... 48
4.10.6 Signaling Tracing ................................................................................................................. 48
4.10.7 Dual-Homing Management ................................................................................................. 49
4.10.8 CDMA Pool Management.................................................................................................... 49
5 Reliability.......................................................................................................................50
5.2 System Reliability ........................................................................................................................... 50
5.2.1 Data Security ......................................................................................................................... 50
5.2.2 Operation Security................................................................................................................. 51
5.3 Hardware Reliability ....................................................................................................................... 51
5.4 Software Reliability......................................................................................................................... 52
6 Technical Specifications ..............................................................................................53

6.2 Performance Specifications............................................................................................................ 53
6.2.1 System Capacity.................................................................................................................... 53
6.2.2 Bandwidth .............................................................................................................................. 55
6.2.3 Data Processing Capability of the M2000 Server.................................................................. 57
6.2.4 Peak Alarm Processing Capacity .......................................................................................... 57
6.2.5 Alarm Data Storage Capacity ................................................................................................ 58
6.2.6 Number of Clients Simultaneously Started on the Server ..................................................... 59
6.3 Physical and Electrical Specifications ............................................................................................ 60
6.4 Reliability Specifications................................................................................................................. 63

Issue V2.0 (2009-02-28) Page 5 of 77
M2000
Product Description
6.5 Compliant Safety Standards........................................................................................................... 65

6.6 EMC Specifications ........................................................................................................................ 66
6.7 Environmental Requirements ......................................................................................................... 66
6.7.1 Storage Environment............................................................................................................. 66
6.7.2 Transportation Environment .................................................................................................. 69
6.7.3 Operation Environment ......................................................................................................... 71
7 Acronyms and Abbreviations ......................................................................................74

Issue V2.0 (2009-02-28) Page 6 of 77
M2000
Product Description
1 Introduction to the M2000
1.1 About the M2000

This manual is used only for the iManager M2000 Mobile Element Management
System V200R008.
The iManager M2000 Mobile Element Management System (hereafter referred to as
the M2000) is a centralized mobile network management platform developed by
Huawei Technologies Co., Ltd. (hereafter referred to as Huawei). The M2000 can
perform centralized management on mobile NEs provided by Huawei. These NEs
include NEs in the CBSS system, NEs in the RASYS network, and NEs in the CN
network. In addition, the M2000 manages the IP networking devices used in the
mobile network.
1.2 Position of the M2000 in the Network

Figure 1-1 shows the position of the M2000 in a CDMA network.

Issue V2.0 (2009-02-28) Page 7 of 77
M2000
Product Description
Figure 1-1 Networking of Huawei CDMA 1X/1xEV-DO/digital trunking system
M2000
BNH
PDSN/FA
AAA
HA
PS Domain
BTS
MSC/VLR/
HLR/AC
SSP/IP
BSC
MGW
MSCe Internet
BTS
CS Domain
AN AAA
GMSC PSTN/PLMN/ISDN
Access Network
TSC
GLMS
Enterprise user
iGWB VPN
Trunking Domain
Core Network
Figure 1-2 shows the position of the M2000 in a WLL network.

Issue V2.0 (2009-02-28) Page 8 of 77
M2000
Product Description
Figure 1-2 Networking of Huawei RASYS system
M2000
PDSN/FA
AAA Internet
RAU
HA
RAC
RAU
LE
Table 1-1 lists the functions of the elements in the CDMA network.
Table 1-1 Functions of the elements in the CDMA network

Element Function
Provides the following functions:

z Transmitting and receiving radio signals
Base Transceiver
Station (BTS)
z Realizing the communications between the mobile network
and the MS
Huawei provides a series of BTS products.
z Controlling and managing the BTS's
z Setting up and releasing call connections
Base Station z Distributing digital trunking service streams
Controller (BSC) z Forwarding digital trunking signaling messages
z Implementing power control
z Managing radio resources
z Providing reliable radio connections by different handoffs

Issue V2.0 (2009-02-28) Page 9 of 77
M2000
Product Description
Element Function

z Call setup
z Route selection
z Radio resource allocation
Mobile Switching z Mobility management
Center (MSC) z Location registration
z Channel switching within switching area
z Bill generation
z Service coordination with the PSTN
z SS7 interface and network interface
A dynamic database. It stores the temporary information of the
Visitor Location
subscribers roaming in a local MSC area. The VLR is integrated
Register (VLR)
with the MSC physically.
z Detecting intelligent service requests
z Communicating with the SCP
Service Switching z Responding to the service request from the SCP
Point (SSP)
z Using the service logics in the SCP to process the calls
An SSP provides call control and service switching.
The SSP is integrated with the MSC or VLR physically.
Core component of the intelligent network. It provides the
following functions:
z Storing the subscriber data and service logics
Service Control z Receiving the query requests from the SSP and querying
Point (SCP) the database to carry out decoding
Initiating service logics according to the call event reported by
the SSP and setting up intelligent calls by sending call control
instructions to the SSP according to service logics
The IP is integrated with the MSC physically as a network
Intelligent functional unit. Through the internal interface, the IP provides
Peripheral (IP) dedicated resource for the SSP to implement intelligent
services.
The soft switching center in a CDMA network. It incorporates the VLR

database for the following functions:
z Call control
z Access control of MGW
Mobile Switching z Resource allocation
Center emulation z Signaling processing
(MSCe) z Routing
z Authorization
z Charging
z Basic services, mobility management, and multimedia
services for subscribers

Issue V2.0 (2009-02-28) Page 10 of 77
M2000
Product Description
Element Function
Deals with the format conversion and signaling conversion of media

Media Gateway streams. It connects the base station controller (BSC), home location
(MGW) register (HLR), message center (MC), service control point (SCP), TMSC,
GMSC, and other network elements.
A database for mobile subscriber management. It is integrated

Home Location with the HLR physically. It provides the following functions:
Register z Storing the subscription information, subscriber states, MS
(HLR)/Authenticat location information, MDN, and IMSI (MIN)
ion Center (AC) z Managing the information necessary for subscriber
authentication
Short Message
Center (SMC)
z Storing and forwarding short messages
z Providing services supplementary to short messages
Gateway Mobile Provides the following functions:
Switching Center z Requesting the routing information of a called subscriber
(GMSC) z Providing interconnection and settling between networks
Packet Data z A gateway for connecting the mobile network and the IP
Serving Node backbone network
(PDSN) z Providing the access of packet data service for mobile
subscribers.
z Providing the interface between the mobile network and the
Internet
Home Agent (HA)
z An auxiliary node for mobile subscribers to access the
Internet
z Supporting downlink data forwarding in the mobile IP tunnel
mode
z Supporting uplink data forwarding through reverse tunnel
A high-performance remote verification server for dial-in
subscribers. It provides the following functions:
Authentication,
Authorization and
z Providing authentication, authorization, accounting, and
Accounting (AAA) data value-added services
z Supporting multiple types of databases, powerful agent, and
flexible operations
Trunk Switching z Processing trunk call signaling
Center (TSC) z Distributing trunk call media.
A TSC can be connected with multiple PCF's.

Issue V2.0 (2009-02-28) Page 11 of 77
M2000
Product Description
Element Function
Manages the information about:

z Trunk group
Group and List
Management
z Trunk service subscribers
server (GLMS) z Subscriber trunk services
z Dispatcher
z Virtual Private Network (VPN)
z Collecting bills
iGateway Bill z Storing bills
(iGWB) z Filtering bills
z Sorting bills
z Send bills
z Call setup and voice conversion between the Dispatcher
(DPT) and the MSE
Dispatcher server
(DPS)
z Call transfer and connection between the DPT and the
PSTN or PLMN
z Transfer of session control command transfer for the DPT
z Transfer of trunk session state information
The DPT is connected with the MSE through the DPS. It
provides a user interface for the dispatcher to carry out
dispatching operations.
The dispatcher provides the following functions:
z Group calls
Dispatcher (DPT) z Broadcast calls
z Private calls
z Short message transmission
z Forced insertion
z Forced release
z Display of the status of subscribers and groups in real time
Service
The enterprise user enables the VPN manager and the VPN
Maintenance
operator to operate on and manage the data, such as the data
Terminal
about subscribers, groups, and location areas.
(enterprise user)
Radio Access
Controls the radio access to the RASYS.
Controller (RAC)
Radio Access
Implements the radio access to the RASYS.
Unit (RAU)

Issue V2.0 (2009-02-28) Page 12 of 77
M2000
Product Description
Element Function
The centralized management platform for Huawei mobile

network products.
The M2000 provides the following functions:
z Centralized fault management
iManager M2000
(M2000)
z Centralized performance management
z Centralized configuration management
z Centralized topology management
z Centralized security management
z System management
1.3 Interfaces of the M2000

In the Telecommunication Management Network (TMN), the M2000 is at the Element
Management-layer (EM-layer). It provides network management interface for the
Network Management System (NMS). Figure 1-3 shows the standard interfaces
provided by the M2000.
Figure 1-3 Interfaces provided by the M2000
Table 1-2 lists the interfaces provided by the M2000 and the properties.
Table 1-2 Interfaces provided by the M2000 and thee properties

Peer Protocol Transmission
Common Object Request Broker

Architecture (COBRA) protocol, file TCP/IP protocol based
NMS interface, SNMP interface, alarm Ethernet network or supported
streaming interface or MML transparent transmission network
transmission interface

Issue V2.0 (2009-02-28) Page 13 of 77
M2000
Product Description
Peer Protocol Transmission

z For devices in Huawei CDMA mobile
networks: the internal Human Machine
Language (MML) protocol or binary TCP/IP protocol based Ethernet
NE protocol network or supported transmission
z For IP networking devices: Simple network
Network Management Protocol
(SNMP)

Issue V2.0 (2009-02-28) Page 14 of 77
M2000
Product Description
2 Key Benefits
2.1 Challenges and Trends

The O&M system in the current telecommunication network faces the following
challenges:
z With the network expansion and increasingly involved subscribers, how to
manage the network in an effective manner?
z With the rapid development of telecommunication technology, how can the
element management system (EMS) evolve itself?
z How to speed up network construction to meet the demands of quick
deployment?
The O&M system also shows the following trends in its development:
z Integrated network monitoring and maintenance
z Open interface and flexible networking to facilitate the network expansion and
evolution
z Service-oriented, active maintenance, and performance management taking
place of device-oriented, passive maintenance, and alarm management
z Network quality evaluation and persistent improvement on service quality
Providing powerful and rich functions, the Huawei M2000 system meets the latest
development trends and helps network operators handle the challenges with ease.
2.2 Advanced Componentized Architecture

With the Common Object Request Broker Architecture (CORBA) design, each service
function in the M2000 can be developed and deployed through componentized
module, which enables the M2000 to meet the maintenance demands in a quick
manner and realize smooth upgrade.
Having several hardware, software platforms, and different databases, the M2000
also provides typical configurations for these resources to be applied to different
networks. The M2000 realizes smooth network expansion based on the increasingly
network dimensioning.

Issue V2.0 (2009-02-28) Page 15 of 77
M2000
Product Description
2.3 Flexible Networking Mode

The M2000 manages the following network elements (NE) or devices provided by
Huawei:
z NEs in the CDMA Base Station Subsystem (CBSS)
z NEs in the Radio Access System (RASYS)
z NEs in the Core Network (CN)
The IP networking devices complying with the SNMP protocol and the third-party
servers (BAM server used by the MSCe) are also supported in the M2000.
The M2000 can either execute integrated management on CN and CBSS, or manage
the CN or CBSS individually.
Communicating with NEs based on TCP/IP, the M2000 supports the following types of
networks:
z Local area network (LAN)
z E1/T1 network
z DDN/X.25 network
z Virtual private network (VPN)
2.4 Various Interfaces

The M2000 provides various kinds of interfaces to cater for a wide range of users and
situations.
The M2000 provides the NMS with the following northbound interfaces that comply
with the protocol standards:
z CORBA interface
z File interface
z SNMP interface
z Alarm streaming interface
z MML transparent transmission interface
The M2000 manages standard IP networking devices through SNMP interface and
manages devices provided by Huawei through the following southbound interfaces:
z MML interface
z Binary interface
In addition, the M2000 provides a platform for script development. The script
development includes:
z Editing, debugging, and running scripts
z Executing tasks on a scheduled basis
You can use the script development platform to edit or run High-level Script Language
(HSL) to realize automatic routine maintenance.

Issue V2.0 (2009-02-28) Page 16 of 77
M2000
Product Description
2.5 Powerful Operation and Maintenance Function

The M2000 provides the following powerful O&M functions:
z Fault management (FM)
z Performance management (PM)
z Configuration management (CM)
z Security management (SM)
z Topology management
z Device panel simulation
z Basic CBSS navigation configuration
z Subscriber signaling tracing
z Performance report
Based on new features of services after the introduction of soft switch in the CN, the
M2000 provides the following functions:
z Dual-homing management
z CDMA Pool management
2.6 Comprehensive Operation and Maintenance Solution

The M2000 provides a comprehensive O&M solution.
The solution provides:
z Intelligent reports to meet the requirements of performance KPI.
z Citrix client access solution to enable the remote access of clients.
z Time management to synchronize the time in the entire network.
z System backup restore solution to ensure the data security in the network

Issue V2.0 (2009-02-28) Page 17 of 77
M2000
Product Description
3 System Architecture
3.1 About This Chapter

The M2000 system works in client/server mode.
The M2000 software consists of the client software, server software, and NE
mediation software. The software is mutually independent. The client software runs on
the client, and the server software and mediation software run on the server.
The M2000 client uses a PC. If required, multiple M2000 clients can be configured at
the same time. As required, you can configure the M2000 system with one server, that
is, a single server, or you can configure the M2000 system with two servers, which
work in active/standby mode to form a high availability (HA) system.
Besides the server and the client, the M2000 system may also include the following
networking devices based on requirements:
z Router
z Switch
z Timeslot cross-multiplexer
This chapter describes the physical and software architecture of the M2000 system.
3.2 Physical Structure

3.2.1 Overview
A typical M2000 system includes:
z Server(s)
z Client(s)
z Alarm box(es)
z Other networking devices
3.2.2 Physical Structure of the Single-Server System

Figure 3-1 shows the physical structure of the M2000 single-server system.

Issue V2.0 (2009-02-28) Page 18 of 77
M2000
Product Description
Figure 3-1 M2000 single-server system
3.2.3 Physical Structure of the HA System

Using the Cluster application, the M2000 makes active and standby servers in the
same local network constitute an HA system. The active and standby servers
communicate with each other through LAN and get access to disk arrays of the same
group.
Figure 3-2 shows the physical structure of the M2000 HA system with the Cluster
application.
Figure 3-2 Physical structure of the M2000 (HA system)
Table 3-1 describes the devices at the server side.
Table 3-1 Devices at the server side (HA system)

Equipment Description
Active server The active server works as the M2000 system server. It runs the
M2000 server software. In conjunction with the standby server,
the active server monitors and switches server resources
through the Cluster software.

Issue V2.0 (2009-02-28) Page 19 of 77
M2000
Product Description
Standby server The standby server provides redundancy for the master server. If
the resources on the master server work improperly, you can use
the Cluster software to switch the resources over to the standby
server.
Disk array The disk array provides highly available storage space for the
master server. If the master server works improperly, the Cluster
software mounts the disk array on the standby server.
3.2.4 Typical M2000 Server Configuration

The M2000 server may be:
z Sun Sparc Enterprise T5220 Server
z Sun Sparc Enterprise M4000 Server
z Sun Sparc Enterprise M5000 Server
z HP rx2660
z HP rx7640
z ATAE
The selection of the computer for an M2000 server depends on the number of NEs in
the network.
Typical Server Configuration for the Single-Server System

Table 3-2 lists the typical Sun server configuration of an M2000 single-server system.
Table 3-3 lists the typical HP server configuration of an M2000 single-server system.
Table 3-4 lists the typical ATAE server configuration of an M2000 single-server
system.

Issue V2.0 (2009-02-28) Page 20 of 77
M2000
Product Description
Table 3-2 Typical configuration of M2000 server (single-server system, Sun)

T5220 M4000 M5000
Number of CPUs 1(4 Core) 2 4 4 6 8
Main frequency of the 1.2 2.4 2.4 2.4 2.4 2.4

CPU (GHz)
Memory (GB) 8 16 32 32 48 64
Hard disk (GB) 4 x 146 2 x 146 2 x 146
Disk array (GB) None 1 x 3320 1 x 3320

(A 3320 disk array (A 3320 disk array
consists of sixteen consists of sixteen
146 GB hard disks) 146 GB hard disks) or
or 1 x 6140 1 x 6140
(A 6140 disk array (A 6140 disk array
consists of sixteen consists of sixteen
146 GB hard disks) 146 GB hard disks)
Accessories DVD/Ethernet adapter/DATA72 tape drive/English
documentation
Operating system Solaris 10/English documentation
Database Sybase 15.0.2
Application software M2000 server application software
Table 3-3 Typical configuration of M2000 server (single-server system, HP)

rx2660 rx7640
Number of 2 X 2 Core 2 X 2 Core 4 X 2 Core 6 X 2 Core 8 X 2 Core

CPUs
Main 4 X 1.4 4 X 1.6 8 X 1.6 12 X 1.6 16 X 1.6

frequency of
the CPU
(GHz)
Memory (GB) 8 16 32 48 64
Hard disk 4 X 146 2 X 146

(GB)
Disk array - 1 x S3200

(GB) (A S3200 disk array consists of sixteen 146 GB hard
disks)
Accessories DVD/Ethernet adapter/English documentation

Issue V2.0 (2009-02-28) Page 21 of 77
M2000
Product Description
Operating SUSE Linux Enterprise Server 10/English documentation

system
Database Oracle Database Enterprise/Standard Edition 10g
Application M2000 server application software

software
Table 3-4 Typical configuration of M2000 server (ATAE)

Item ATAE
Number of CPUs 2
Main frequency of the 2.13

CPU (GHz)
Memory (GB) 8
Hard disk (GB) 2 X 146
Accessories DVD/DATA72 tape drive/English documentation
Operating system SUSE Linux Enterprise Server 10/English

documentation
Database Oracle Database Standard Edition 11g
Application software M2000 server application software
When selecting the ATAE as the M2000 server, you also need to configure a USM
server to be the console of installing software on the ATAE server. For details about
the configuration of the USM server, refer to Table 3-5.

Issue V2.0 (2009-02-28) Page 22 of 77
M2000
Product Description
Table 3-5 Typical configuration of USM server

Item PC Server
Number of CPUs 2
Main frequency of the CPU 1.6

(GHz)
Memory (GB) 8
Hard disk(GB) 2 X 146
Accessories DVD/Ethernet adapter/English documentation
Operating system SUSE Linux Enterprise Server 9 SP02/English

documentation
Application software USM server application software
Typical Server Configuration for the HA System

The configurations of the two servers in the HA system are the same. Table 3-6 and
Table 3-7 list the usable server types and the standard configuration of each server.

Issue V2.0 (2009-02-28) Page 23 of 77
M2000
Product Description
Table 3-6 Typical configuration of M2000 server (HA system, Sun)

T5220 M4000 M5000
Number of 1 2 4 4 6 8
CPUs
Main 1.2 2.4 2.4 2.4 2.4 2.4

Frequency
of the CPU
(GHz)
Memory 8 16 32 32 48 64
(GB)
Hard disk 4 x 146 GB 2 x 146 GB 2 x 146 GB
Disk array 2 x S3100 2 x 3320 2 x 3320

(GB) (A S3100 (A 3320 disk array (A 3320 disk array consists
disk array consists of sixteen 146 of sixteen 146 GB hard
consists of GB hard disks) or 2 x disks) or 2 x 6140
sixteen 146 6140
GB hard (A 6140 disk array consists
disks) (A 6140 disk array of sixteen 146 GB hard
consists of sixteen 146 disks)
GB hard disks)
Accessories DVD/Ethernet adapter/DATA72 tape drive/User manual
Operating Solaris 10/English documentation

system
Database Sybase 15.0.2
Table 3-7 Typical configuration of M2000 server (HA system, HP)

rx7640
Number of 2 X 2 Core 4 X 2 Core 6 X 2 Core 8 X 2 Core

CPUs
Main 4 X 1.6 8 X 1.6 12 X 1.6 16 X 1.6

Frequency
of the CPU
(GHz)
Memory 16 32 48 64
(GB)

Issue V2.0 (2009-02-28) Page 24 of 77
M2000
Product Description
rx7640
Disk array 2 x S3200 (A 2 x S3200 (A 2 x 3320 2 x 3320

(GB) S3200 disk S3200 disk (A 3320 disk (A 3320 disk array
array array array consists consists of sixteen
consists of consists of of sixteen 146 146 GB hard
sixteen 146 sixteen 146 GB hard disks)
GB hard GB hard disks)
disks) disks)
Accessories DVD/Ethernet adapter/ User manual
Operating SUSE Linux Enterprise Server 10/English documentation

system
Database Oracle Database Enterprise Edition 10g
Common Networking Devices

Table 3-8 lists the common networking devices used in the M2000 system.
Table 3-8 Common networking devices

Item Configuration
Router M2000 side: Quidway AR46-20

NE side: Quidway AR28-11 and Quidway AR28-10
Switch Quidway S5624P, Quidway S3928-EI
Timeslot cross Mercury3600
multiplexer
3.2.5 Typical M2000 Client Configuration

Table 3-9 lists the recommended PC configuration.
Table 3-9 Recommended PC configuration for the M2000 client

Item Configuration
CPU E2140 (1.6 GHz or faster)

Memory 1 GB
Hard disk 80 GB
Accessories DVDRW /Floppy drive/Ethernet adapter/Sound card/Sound
box/17" LCD display

Issue V2.0 (2009-02-28) Page 25 of 77
M2000
Product Description
Item Configuration
Operating system Windows XP professional SP02 (or a later version), or

Windows Vista Business with Service Pack 1
Application M2000 client application software
software
3.3 M2000 Operating Environment

3.3.1 Operating Environment for the M2000 Single-Server
System
Figure 3-3 shows the operating environment for the M2000 single-server system.
Figure 3-3 M2000 operating environment (single-server system)
The Veritas Volume Manager (VxVM) is installed when the server is equipped
with a disk array.
3.3.2 Operating Environment for the M2000 HA System

Figure 3-4 shows the operating environment for the M2000 high availability (HA)
system.

Issue V2.0 (2009-02-28) Page 26 of 77
M2000
Product Description
Figure 3-4 M2000 operating environment (HA system)
As shown in Figure 3-4, the active server and the standby server are in the same local
area network. The M2000 clients are connected to the active server. The Cluster
software on the serer monitors the operation of each application in a real-time manner.
When exceptions occur, the active server is switched to standby server.
3.4 Software Architecture

3.4.1 Overview
The M2000 software consists of three sub-systems:
z M2000 Server software
z M2000 Client software
z NE mediation software
The NE mediation software varies according to the version of the NE. The NE
mediation software accesses the NE of the corresponding version and adapts it for the
network.
In addition, the M2000 provides a report tool for customizing reports.
Figure 3-5 shows the M2000 software architecture.
Figure 3-5 M2000 software architecture

Issue V2.0 (2009-02-28) Page 27 of 77
M2000
Product Description
3.4.2 M2000 Server Software

Figure 3-6 shows the composition of the M2000 server software.
Figure 3-6 Component modules of the M2000 server software

Client software
CORBA software bus
NE mediation software
Mediation
SWM
NMS
SEM
SYM
NBI
CM
NM
RM
PM
FM
TM
DP
LM
ST
Server software
Data center/Database system
The M2000 server software consists of 12 modules. Through the CORBA software
bus, these modules communicate with each other and with the corresponding
modules of the M2000 client software.
The M2000 server provides the interface for the NMS through the NM interface
module. It provides interfaces for the mediation software of various NEs through the
mediation common module. Some modules access the M2000 server database
through the database interface.
Table 3-10 describes these modules and their functions.

Issue V2.0 (2009-02-28) Page 28 of 77
M2000
Product Description
Table 3-10 Modules of the M2000 server software and their functions
Module Function
NMS interface module Provides the northbound interface for the NMS
(NBI)
Fault management module Manages alarms. The fault management involves:
(FM) z Collecting alarms
z Querying alarms
z Processing alarms
Security management Manages the system security. The system security
module (SEM) involves:
z Managing user authorities
z Managing user groups
Topology management Manages the topology. The topology management
module (TM) involves:
z Managing topology objects
z Managing the topology view
System management Manages the system. The system management
module (SYM) involves:
z Managing the system license
z Initializing the system
z Installing and uninstalling the software
z Managing scheduled system tasks
Configuration management Manages the configuration. The configuration
module (CM) management involves:
z Querying the configuration data
z Configuring NEs
z Displaying NE and link reports
Performance management Manages the performance. The performance
module (PM) management involves:
z Collecting the performance data
z Monitoring the performance in real time
z Generating the threshold alarm
Log management module Manages logs. These logs can be as follows:
(LM) z System logs
z Operation logs
z Security logs

Issue V2.0 (2009-02-28) Page 29 of 77
M2000
Product Description
Module Function
Provides a graphic interface for integrated

monitoring.
Displays the following items for the specified objects
Network monitoring (NM) in real time:
z Alarm status
z Configuration status
z KPI
Signaling trace module (ST) Traces signaling at various interfaces of the NE.
Device panel module (DP) Provides the device panel for:
z Querying the status of NE devices
z Operating on the devices
Mediation module Provides interfaces for the mediation software of
various NEs.
3.4.3 M2000 Client Software

The M2000 client software provides the graphic user interface (GUI) for operating and
maintaining the managed NEs.
Each module of the M2000 server software, except the mediation common module
and the NMS interface module, corresponds to a module on the GUI.
You can start the report tool client and the NE LMT directly from the M2000 client.
3.4.4 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 the NE needs
to access the M2000 system.
3.5 Interfaces
3.5.1 Northbound Interfaces
The M2000 supports the following Itf-N network management interfaces:
z CORBA interface
The Itf-N interface is based on CORBA interface protocols and is in compliance
with 3GPP R6 protocols.
It supports the management of northbound users. The alarm data can be filtered
by operator.
z File interface

Issue V2.0 (2009-02-28) Page 30 of 77
M2000
Product Description
The NMS retrieves from the M2000 the alarm, performance, and configuration
data saved to TXT files. The performance file interface can be connected to
several NMSs and has the function of northbound user management. The
performance files can be filtered by operator.
z Alarm streaming interface
The M2000 sends the processed NE alarms in the form of character stream to
the NMS.
z SNMP interface
The M2000 sends the processed alarms in the form of text to the NMS through
the SNMP alarm interface. The SNMP interface supports the SNMPv1, SNMPv2,
and SNMPv3 protocols.
z MML transparent transmission interface
The MML transparent transmission interface serves as a proxy for transferring
MML commands between the NMS and NEs. Through this interface, the NMS
can operate and maintain the associated NEs using MML commands.
3.5.2 Southbound Interfaces

The M2000 manages mobile NEs through the Human Machine Language (MML)
interfaces or binary interfaces, and manages the IP devices using the Simple Network
Management Protocol (SNMP).
In addition, the files such as performance result files are transported using the FTP
protocol between the M2000 and managed NEs.
3.5.3 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 WEB mode.

Issue V2.0 (2009-02-28) Page 31 of 77
M2000
Product Description
4 Services and Functions

The M2000 provides the functions of the following two types:
z Common functions: refer to the functions supported by all NEs.
z Specified functions: refer to the functions supported by some NEs.
4.2 Topology Management

4.2.1 Function Type
Topology management is a common function supported by all the NEs on the M2000.
4.2.2 Topology Object Management

Topology object refers to the NE, subnet, or link on a topology map.
Topology object management provides the following functions:
z Creating and deleting topology objects
Bulk creation and deletion are also supported.
z Modifying the attributes of a topology object
You can modify the basic attributes or position of a topology object on the map.
z Finding the specified NE
You can search by NE name, software version, vendor, or IP address. The M2000
supports both precise search and fuzzy search.
z Customizing the topology map
z You can conduct the settings to display or hide NEs or links of some type.
4.2.3 Topology Object Viewing

On a topology map, you can view the following information:
z Detailed information of an NE
z Connection status of an NE

Issue V2.0 (2009-02-28) Page 32 of 77
M2000
Product Description
In case an NE is disconnected, the M2000 automatically originates the

reconnection attempts.
z Links between NEs
z Alarms of NEs and links
z KPI of NEs and links
4.2.4 Topology Map Management

The topology map can display NEs and links as hierarchical subnets. Each subnet
can use different topology map.
Two types of topology maps are available:
z Vector map
Flags the accurate location of an NE
z Electronic map
Displays the district, longitude, and latitude of an NE
4.2.5 NE Management by District

With the electronic map, the M2000 can obtain the district information of each NE, that
is, the province in which the NE is located. Based on the KPI values and alarm
statistics by district, the M2000 monitors all NEs in the districts.
4.2.6 Shortcut Operation Access

The M2000 offers shortcut operation accesses on the topology map, which facilitate
querying the following information:
z Configuration information of NEs and links
z Alarm information
z Performance measurement results
After the client is installed with the corresponding LMT software version, you can start
the LMT on the topology map.
4.3 Configuration Management

4.3.1 Function Type
Configuration management is a common function of the M2000. All NEs except IP
networking devices support this function.
4.3.2 Configuration Data Synchronization

The M2000 saves the configuration data of all NEs and synchronizes the data in real
time. You can view the progress of and details about the synchronization of
configuration data, as well as the record of the latest synchronization.
The configuration data can be synchronized in the following three modes:
z Automatic synchronization

Issue V2.0 (2009-02-28) Page 33 of 77
M2000
Product Description
Changes in the NE configuration are automatically reported to the M2000. Then

the system updates the existing configuration data on the M2000.
z Manual synchronization
You can synchronize the configuration data on the M2000 client manually. Then
the system acquires the latest configuration data from NEs and updates the
existing data on the M2000.
z Periodic synchronization
The M2000 system synchronizes the configuration data periodically. Then the
system acquires the latest configuration data from NEs and updates the existing
data on the M2000.
4.3.3 Configuration Data Query

Through this function, the M2000 client allows you to:
z Query NE configuration data on the client and view the queried results in reports.
z Refresh the configuration data and search for configuration objects.
For a large number of configuration data, the system segments the data and displays
them in different tabs on the client.
4.3.4 Configuration Data Export

The M2000 provides the export of the following two types:
z Manual export
z Scheduled export
You can export NE configuration data to .xml files or .csv files to the specified directory
of the server.
Scheduled export supports only XML format. Manual export supports both XML and
CSV formats.
4.4 Centralized Fault Management

4.4.1 Function Type
Centralized fault management is a common function of the M2000. All NEs support
this function.
4.4.2 Real-Time Alarm Monitoring

On the M2000, you can monitor alarms of all NEs in the network. Thus you can know
the alarm severity, alarm type, and causes, and handle fault alarms in time.
The M2000 provides the following alarm notification modes:
z Displaying alarms of different severities and statuses in custom colors on the
interface, such as topology view and alarm browse window.
The M2000 also highlights the fault alarms that have not been handled for a long
time.

Issue V2.0 (2009-02-28) Page 34 of 77
M2000
Product Description
z Displaying the total of alarms of each severity on the alarm board, and alerting
you by sounds and blinking icons.
z Providing remote alarm notification by E-mail or SMS.
You can set the conditions of alarm forwarding.
z Displaying the current alarm status using the custom sound when a sound box is
connected to the client.
z Providing audible and visual alarms when an alarm box is connected to the client.
z Printing the alarm information when a printer is connected to the client.
After alarms are handled, the M2000 automatically changes the corresponding
statuses to be cleared. For the alarm which is handled while the status is not changed,
you can manually change the status to be cleared.
On the M2000 client, you can check whether the statuses of the specified alarm are
consistent on the NE and the M2000. If the statuses are different, the M2000 updates
the alarm status to keep the consistency with the NE.
4.4.3 Alarm Data Management

The M2000 database stores all NE alarms in the network. You can export the alarm
data as files when required.
To ensure the correctness of the data in the database, the M2000 synchronize alarms.
The M2000 supports automatic, manual, and scheduled alarm synchronization. The
three types of synchronization are described as follows:
z Automatic alarm synchronization
NEs automatically report the changed alarms to the M2000. Then the M2000
updates the alarm database.
z Manual alarm synchronization
You can synchronize alarms manually on the M2000 client. Then the M2000
updates the alarm database.
z Scheduled alarm synchronization
The M2000 synchronizes alarms at the scheduled time every day. Then the
M2000 updates the alarm database.
4.4.4 Alarm Query and Statistics

For this function, the M2000 enables you to:
z Query the generated fault alarms and event alarms of all NEs, and know the
handling situation. Save common query conditions to query templates.
z Set conditions to collect the statistics of alarm situations, alarm severities, and
NE type.
z Print the result of alarm query and statistics.
4.4.5 Alarm Assisting Handling

The M2000 offers alarm acknowledgement mechanism, which allows you to indicate
whether the current alarm is noticed and handled. You can acknowledge or
unacknowledge alarms manually, or set acknowledge alarms automatically.

Issue V2.0 (2009-02-28) Page 35 of 77
M2000
Product Description
You can add comments for each alarm. For the convenience of subsequent
operations, the alarm remark can tell history operations, operator, operating time, and
additional information. You can record your alarm handling experiences, such as fault
location and handling suggestions, in the alarm knowledge library. This facilitates
troubleshooting and sharing maintenance experiences.
You can set conditions for the M2000 to analyze correlation, redefine alarm severity,
and shield alarms of specified NEs. In this case, you can focus on key alarms, locate
alarms promptly and correctly, and maintain the network in various scenarios.
4.5 Centralized Performance Management

4.5.1 Function Type
Centralized performance management is a common function of the M2000. All NEs
except IP networking devices support this function. The M2000 can manage its own
performance data.
4.5.2 NE Performance Measurement Setting

You can set the method for measuring NE performance based on requirements.
The settings for NE performance measurement include:
z Counters
z Objects
z Intervals
Performance counters of an NE fall into two categories: common counters and
extended counters. The M2000 collects common data about the common counters
automatically. Based on the common counters, you can view and set the extended
counters for collection on the M2000 client.
You can set the new performance measurement objects to new object auto measure.
Performance objects of NEs fall into the following three categories:
z Class 1 performance objects
The M2000 collects counter information for these objects automatically.
You must specify the objects through the M2000 client to collect counter
information.
You must specify the objects and enter required parameters for the M2000 to
collect counter information.
Performance measurement intervals can be 5 minutes, 15 minutes, 30 minutes, 60
minutes, and 24 hours. Some measurement counters do not support the intervals of 5
minutes and 15 minutes.

Issue V2.0 (2009-02-28) Page 36 of 77
M2000
Product Description
4.5.3 Real-Time Monitoring of Performance Results

You can specify an object or a counter for real-time monitoring. In addition, you can
monitor an object on multiple clients.
The M2000 allows you to use a custom real-time monitoring template to start a
monitoring task. You can also modify or delete a real-time monitoring template. The
M2000 displays real-time monitoring result through tables or graphics. You can filter
results and define display effect by setting conditions.
4.5.4 Performance Result Query

In one measurement interval, the value of a measurement counter is a measurement
result of an object.
This function enables you to:
z Set object, counter, and time to query the performance result.
z Query performance results through default or custom performance result query
templates.
z Customize, delete, or modify custom performance result query templates.
z Query the performance results of history objects.
The M2000 displays the queried performance result in tables, linear chart or bar chart.
You can also print the queried results. For the result table, you can specify the
conditions to sort the results. For the linear chart, you can specify to the display the
result of multiple counters for one object, or the result of one counter for multiple
objects.
You can check whether the performance results are reliable, and whether missing
performance data exists. If there is missing performance data, trigger the performance
data synchronization.
You can subscribe performance results. In this case, you can browse the performance
results in real time.
4.5.5 Performance Data Management

The M2000 database stores the performance data of all NEs. You can export the
performance data .xml files or .csv files and save them on the server.
The M2000 provides two types of data export:
z Export of latest data
Exports the performance data collected in the recent period to files. This can help
the analysis for other systems and users.
z Export of oldest data
Exports the performance data that exceeds the validity period to files. The
records in the database are deleted. This protects the database.
The M2000 exports data through automatic and manual synchronization, so that the
performance data stored on the EMS and the NEs are consistent. When performance
results are synchronized, you can view the details about the synchronization task.

Issue V2.0 (2009-02-28) Page 37 of 77
M2000
Product Description
4.5.6 Performance Alarm

You can set the threshold, that is, the range, for the specified performance
measurement counter value. When the counter value exceeds the range, the M2000
triggers fault alarms of different severities based on the preset conditions.
The M2000 allows you to set threshold alarms for object groups. The counters in the
object group are summarized to set the threshold. When the value of the counter
exceeds the preset threshold, the M2000 triggers a threshold alarm.
The M2000 allows you to query by threshold. It also allows you to set threshold alarms
by tasks. You can set the time for activating and suspending of threshold tasks.
Alternatively, you can manually activate and suspend threshold tasks.
4.5.7 Custom Counters

Custom counter is a new measurement counter which is the result of adding,
subtracting, multiplying, and dividing multiple performance counters of the NE. When
receiving performance results from the NE, the M2000 calculates the value of the
custom counter according to the user-defined formula. Then you can query and
process the results in future.
For custom counters, the M2000 allows you to:
z Customize, modify, and delete the custom counter.
z Export or import custom counters to share and back up them.
4.5.8 Performance Report

The M2000 allows you to retrieve the KPI data of the network and summarizing the
data on the time and object basis. You can query and browse the summary data.
Compared with the original performance data, the summary data enjoys the longer
storage period.
The performance report has the following features:
z Policy on discovering multiple busy hours
z Custom measurement counters
z Predefined reports to provide basis analysis methods
z Custom reports
z Long-term storage for special and crucial data
z Comparison report to compare the data at two time points
4.6 Centralized Security Management

4.6.1 Function Type
Centralized security management is a common function. All NEs except IP devices
support this function.
4.6.2 User and User Group Management

The M2000 user information consists of the following items:

Issue V2.0 (2009-02-28) Page 38 of 77
M2000
Product Description
z User account: the user name for a user to log in to the M200.
z Password: the password used by the user to access the M2000.
z Login time: a valid time period for a user to log in to the M2000.
z Allowable terminals: defines through which IP addresses can users log in to the
M2000.
z User group: refers to those groups that each user belongs to which they have the
related operation and maintenance (O&M) authority.
You can create, modify, and delete a user group or user. The M2000 automatically
creates the user account admin and the user group Administrators after the
installation of the system. The user admin belongs to Administrators and has all the
administration, operation, and maintenance authorities.
4.6.3 User Authority Management

The M2000 assigns different operation authorities for different O&M tasks. Only the
users having the O&M authorities can perform the related operations.
The M2000 divides all operations into two types based on the association with NEs.
z For the operations not associated with NEs, the M2000 assigns OMC authorities.
z For the operations associated with NEs, the M2000 assigns NE authorities.
You can preset NE authorities. In other words, you can set the authorities for a type of
NE. Once a new NE of this type is created on the M2000, you are automatically
granted the preset authorities.
The M2000 can assign operation authorities to user groups, thus all users in the group
have these authorities.
The M2000 can also directly assign operation authorities to a user.
The authorities of a user consist of two parts:
z Public authority: refers to the authority that is inherited from the user group.
z Private authority: refers to the authority that is directly allocated to the user.
4.6.4 User Monitoring

On the M2000 client, you can monitor online users in real time. Through the
monitoring interface, the M2000 displays the information such as user name,
operation, executing time, result, and terminal.
In addition, you can force the specified user to exit to protect the system against illegal
operations.
The system also automatically monitors user logins. If the time of consecutive failed
login attempts exceeds the limit, the user is locked automatically.
4.6.5 Terminal Locking

The system locks a terminal that has been idle for a certain period. You must log in
again to prevent illegal users. You can also lock the terminal manually to avoid illegal
operations.
After the administrator or current user enters the password the terminal is unlocked.

Issue V2.0 (2009-02-28) Page 39 of 77
M2000
Product Description
4.6.6 Security Policy Setting

The M2000 provides a flexible security policy setting function to meet the
requirements of different users.
The policies that can be set include:
z Minimum length of user password
z Minimum number of special characters contained in a password
z Minimum number of numeric letters contained in a password
z Minimum number of letters contained in a password
z Validity period for a password (in days)
z Maximum interval for modifying a password
z Number of non-duplicate historical passwords
z Maximum number of login attempts
z Legal prescription after the login of a valid user
z Duration for locking the user account after maximum of login attempts (in
minutes)
4.6.7 Log Management

The M2000 system logs consist of operation logs, system logs, and security logs.
Table 4-1 lists the details of these logs.
Table 4-1 Log description

Categories Description
Record the operation conducted by users.

The following information is recorded in operation logs:
z User name
Operation z Operation terminal
logs z Operation time
z Operation objects
z Operation name
z Operation results
Record significant events occurred in the system to facilitate the
smooth operation of system and removal of faults.
These significant events include but not limited to:
System logs z Exceptional system running
z Network faults
z System's being attacked

Issue V2.0 (2009-02-28) Page 40 of 77
M2000
Product Description
Categories Description
Record significant events that have great influence on system

security.
These significant events include but not limited to:
z Account management events
Security logs
z Account login events
z System security events
z Resources access events (including attempts to access objects
without permission)
Log management involves the following operations:

z Querying logs
z Collecting statistics of logs
z Exporting logs
Table 4-2 describes log management.
Table 4-2 Log management

Log Management Description
You can set query conditions in a flexible manner. In this way,

Querying logs you can query contents of logs, print and save log query
results in files.
Through collecting log statistics, you can quickly familiarize
yourself with information on log operations.
Collecting These information is about:
statistics of logs
z Period when most of operations take place
z Routine operations executed by users
The log export function can export log data that exceeding the
date from database to files on a scheduled basis. In the
Exporting logs
meantime, the exceeded data is deleted from the database,
which protects the database.
The M2000 provides a template for querying logs and collecting log statistics.
4.7 System Management

4.7.1 Function Type
The system management is a general function that does not require support from
NEs.

Issue V2.0 (2009-02-28) Page 41 of 77
M2000
Product Description
4.7.2 License Management

The M2000 supports functions that are licensed while shielding those functions that
are not licensed.
The M2000 allows you to control the NE license resources.
You can query and update license information.
4.7.3 Online Help

The M2000 provides rich, detailed, and flexible online help. Besides the online help on
the M2000 GUI, the online help also includes the help on the following items of the
monitored NEs:
z MML command
z Performance indicators
z Alarm handling
The M2000 GUI is a context-sensitive help. That is, you can invoke the following
information from the online help:
z Specific pages for operation guidance
z Introductory pages for MML commands
z Pages for alarm handling
4.7.4 System Status Monitoring

The system status monitoring enables you to check the following items:
z Status of each service session
z Occupancy of resources (including CPU, memory, hard disk, and database)
z Applications installed on the M2000 server
4.7.5 Centralized Scheduled Task Monitoring

Using a unified interface, the task management manages and schedules all the
scheduled tasks in an integrated manner.
You can execute the following operations on the scheduled tasks:
z Creating
z Deleting
z Modifying
z Suspending
z Resuming
Task-related parameters can also be configured.
You can view the following information on tasks on the task management interface:
z Status
z Results
z Progress

Issue V2.0 (2009-02-28) Page 42 of 77
M2000
Product Description
The system scheduled tasks are of the following categories:

z Database management
z Data synchronization
z Data export
z Backup
z Script
z Scheduled software download
The scheduled tasks can be categorized as follows:
z One-time tasks
Refer to a task that is executed only once at some time.
z Periodic tasks
Refer to a task that is executed on a periodic basis.
4.7.6 Individual Setting

The M2000 allows you to set the interface based on personal preference. The
individual settings can be shared among different clients.
The following settings are available:
z Common setting: defines the style in which the client is displayed.
z Context setting: switches to the setting of the last time when certain function is
enabled.
4.7.7 System Data Backup and Restore

The system data includes:
z Security data
z Log data
z NE alarm data
z Performance data
The system data can be backed up automatically or manually. The data that is backed
up can be recovered manually only.
In addition, the system supports the Veritas-based system back up solution from the
third party. The solution can back up the whole system.
The backup of the whole system involves the backup of:
z Operating system
z Database
z M2000 applications
z Related data
You can execute backup and restore operations through the Veritas interface.
Automatic and manual backup are supported on the M2000.

Issue V2.0 (2009-02-28) Page 43 of 77
M2000
Product Description
4.7.8 System Installation and Uninstalling

You can download the M2000 client software to a local computer and then install the
software. You can also install the software by visiting the installation server through
the web. The web installation mode supports the increment installation of the M2000
components.
When the M2000 is uninstalled, the system recovers to the status before installation.
4.7.9 Client Remote Access

The M2000 clients communicate with the M2000 server or servers using TCP/IP. Thus,
the clients can remotely access the M2000 server in many ways.
The common access mode is to use Internet or VPN. The client is connected to server
directly in case the IP address of the server can be accessed. In such a situation, you
need to set firewalls to safeguard the network.
4.7.10 Citrix-Based Client Access

In the Citrix solution, the Citrix server and Citrix clients are included. All applications
run on the Citrix server or on Citrix server groups, while the Citrix client provides only
an interface for operating on these applications or displaying the operation results.
The Citrix clients communicate with Citrix server or server groups using Independent
Computing Architecture (ICA). When applications are running, only the following
information is transferred between Citrix server (server groups) and Citrix clients:
z Screen refreshment
z Keyboard pressing
z Mouse movement
In the M2000 Citrix solution, the Citrix server or Citrix server group is deployed in the
network where the M2000 server is located. You can execute operations on the
M2000 client applications that are running on Citrix server or Citrix server group
through the Citrix clients. In this way, you conduct maintenance on the network under
consideration.
When using Citrix solution, you only need to install Citrix client applications; thus
lowering the requirements for user access. In addition, the requirement for bandwidth
between Citrix server and clients is relatively low, which enables you to select access
devices and network flexibly.
The Citrix solution significantly improves the security control for terminal access.
4.8 Time Management for the Entire Network

4.8.1 Function Type
Time management for entire network is a common function supported by all the NEs
except IP networking devices.

Issue V2.0 (2009-02-28) Page 44 of 77
M2000
Product Description
4.8.2 Time Zone Management

The M2000 can deal with time transient caused by the fact that the M2000 system is
located in a time zone different from where managed NEs are located.
According to the demands, you can set to display on the M2000 client:
z Time in the time zone where the specified NE is located
z Time in the time zone where the M2000 server is located
4.8.3 DST Supported

The M2000 system supports the daylight saving time (DST) and handles the time
transient brought about by DST. Not only the operation time but the DST-related
information is displayed on the M2000 client.
4.8.4 Time Synchronization for the Entire Network

According to the NTP, the M2000 guarantees the consistency in time for all the NEs in
the network. The reference source for the NTP can be external time server.
4.9 CBSS Specified Functions

4.9.1 Custom NE Alarms
You can set alarm severity of NEs on the M2000. The NE reports alarms based on the
modified alarm severity. In addition, you can shield some specified alarms of NEs. The
NE does not report the shielded alarms.
Some interfaces for external alarms are provided for the BSC. Based on actual on-site
requirements, you can define alarms for BSC peripherals on the M2000 to monitor the
performance of the site where the BSC is located.
These peripherals include:
z Power equipment
z Lightning protection equipment
z Air conditioner
z Environment monitoring equipment
The site performance refers to:
z Operating status of the BSC
z Operating status of the peripherals of the BSC
z Environment status of the site where the BSC is located
You can define the following attributes of alarms on the M2000 GUI:
z ID
z Name
z Severity

Issue V2.0 (2009-02-28) Page 45 of 77
M2000
Product Description
4.9.2 Inventory Management

The M2000 implements the centralized management on the information about
physical and logical assets of NEs.
The M2000 allows you to perform the following functions on the inventory data:
z Browsing
z Querying
z Maintaining
z Synchronizing
z Importing
z Exporting
4.9.3 Basic CBSS Navigation Configuration

The CBSS network is categorized into the following types:
z CDMA access network comprising CBSCs and CBTSs
z Radio access subsystem comprising RACs and RAUs
The basic CBSS navigation configuration enables you to configure CBSS network
parameters on an M2000 client.
The M2000 provides the CBSS management object (MO) tree for displaying the
mappings between the MOs and the NEs in the CBSS network. The M2000 topology
view shows the CBSS MO tree in the left part and tabulates the attribute parameters
of each MO in the right part. MOs such as boards and cells are the basic units of the
CBSS network configuration.
The basic CBSS navigation configuration allows you to perform the following
operations:
z Browsing the configuration data of the entire CBSS network
You can browse the configuration data of each NE and each MO in the CBSS
network. Before browsing data, you are allowed to sequence configuration data.
z Configuring NE data
You can configure NE configuration data on the GUI. For example, you can add
and remove the MO of an NE and modify the attribute parameters of an MO. You
can also configure NE data in batch mode.
z Viewing the CBSS configuration record
During the process for adjusting the CBSS network parameters on the M2000,
the system saves the operation record in the current window. By viewing the
operation record, you can learn the information about the related operations.

Issue V2.0 (2009-02-28) Page 46 of 77
M2000
Product Description
4.10 CN Specified Functions

4.10.1 Customized NE Alarms
You can set or modify alarm severity of NEs on the M2000. The NE reports alarms
based on the modified alarm severity. In addition, some specified alarms of NEs can
be shielded. After the shield, the NE does not report this alarm.
4.10.2 Centralized User Management

The M2000 manages the O&M users in an integrated manner to CN NEs. That is, you
can create users on the M2000 and set for the established users the operating
authorities (including the authority on the M2000 and NEs). After the setting, you can
log in to the M2000 or to the associated LMT as the established user and execute
operations.
When a user logs in to the M2000 client or to the LMT, the M2000 verifies the access
authority of the user. The M2000 allows only valid users to log in and use the
operation and maintenance system (including the M2000 and the associated LMT of
NEs).
When a user executes operations on the M2000 client or on the LMT, the M2000 also
verifies their operating authority to prevent any authority abuse.
To manage users in an integrated manner, you also need to define for established
users the operating authority on specified MML groups of specified NEs. To achieve
this, you can set for users operating authorities on:
z Some command groups of the specified NE
z MML command groups of an NE of a category
In the latter method, the established user has the operating authority on MML
command groups of all the NEs of this category.
The M2000 monitors the users' operations on the LMT in real time. On the monitoring
interface, the following information is displayed:
z User name
z Operation
z Time
z Result
z Operation terminal
During the monitoring, the M2000 can force users to exit from the LMT, which
prevents dangerous operation and safeguards the system.
The M2000 collects the NE operation logs and security logs. You can query or collect
statistics of these logs on the M2000 GUI.
4.10.3 NE Configuration
You can deliver either one or several MML commands to the specified NEs through
the MML interface on the M2000. In this way, you configure data for NEs. You can first
write the MML commands to be executed into a file, and then execute these MML
commands through the MML interface.

Issue V2.0 (2009-02-28) Page 47 of 77
M2000
Product Description
The scheduled tasks based on MML commands can also be set.
4.10.4 Inventory Management

The M2000 implements the centralized management on the information about
physical and logical assets of NEs.
The M2000 allows you to perform the following functions on the inventory data:
z Browsing
z Querying
z Maintaining
z Synchronizing
z Importing
z Exporting
4.10.5 NE Resource Monitoring

The M2000 can view and monitor the status of critical NE resources in real time.
The critical resources include:
z CPU
z Board
z Link
z Port
z Cell information
In addition, the M2000 can stimulate device panels of each NE.
Through graphic simulation panels, you can:
z Check hardware configurations of NE devices (including subracks, frames,
boards, ports)
z Check hardware-related alarms of NE devices
z Maintenance the devices (such as resetting boards)
The M2000 also uses reports to offer detailed information on the following specified
items:
z NE
z Link
z Resources
4.10.6 Signaling Tracing

Signaling tracing is a key approach to locating faults. The M2000 traces user signaling
messages of NEs.
Create message tracing tasks on the M2000 client, and you can specify an NE user to
trace its signaling messages in real time. In addition, you can save these signaling
messages into files for later query.

Issue V2.0 (2009-02-28) Page 48 of 77
M2000
Product Description
4.10.7 Dual-Homing Management

When the dual-homing networking mode is employed between the MSCe and the
MGW, you can browse the information and status of dual-homing on the M2000
topology view.
In dual-homing networking mode, you can deliver configurations of related parameters
to several associated NEs through M2000 GUI.
4.10.8 CDMA Pool Management

When using CDMA Pool management, the MSCes in the pool are evenly distributed to
perform load balancing. If an MSCe in the pool incurs a fault, the other MSCes take
over the users of the faulty MSCe. Thus, network disaster tolerance is implemented.
The M2000 provides the following management functions of the CDMA pool:
z Managing the parameters related to pool features
The M2000 centralizes the configuration and management of the parameters
related to the features of the CDMA pool.
z Monitoring the load of the MSCe in real time during the shortest period, that is,
30s
On the MSCe, the M2000 monitors the number of idle users, the number of
power-off users, the number of total users, and CPU occupancy. The M2000 also
monitors the number of contexts on the MGW. The shortest period for refreshing
statistics is 30s.
z Collecting the global performance statistics of the CDMA pool
The M2000 summarizes common KPI counters at the level of the CDMA pool and
provides the global KPI counters of the CDMA pool.
z Checking data consistency and synchronizing data
The M2000 checks on schedule or periodically whether the configuration data of
each NE in the pool is consistent. In case of inconsistency, the M2000 generates
a synchronization script to enable data consistency.
z Transferring of users in the pool
The M2000 can create transfer tasks and monitor transfer status.

Issue V2.0 (2009-02-28) Page 49 of 77
M2000
Product Description
5 Reliability

The M2000 reliability includes:
z System Reliability
z Hardware Reliability
z Software Reliability
5.2 System Reliability

The system reliability includes:
z Data Security
z Operation Security
5.2.1 Data Security

All the M2000 system data, such as the performance data, alarm data, configuration
data, security data, and log data, is saved in the database of the M2000 server. The
high security of the database, and the backup and restore mechanism ensure the
reliability of system data.
Backup Mechanism
The M2000 backs up the system data in scheduled or manual modes.
For the scheduled backup, you can set the backup period. For the manual backup,
you can back up the data at any time.
You can export the backup data into an external media.
Restore Mechanism
If the system data is damaged because of system or upgrade failures, you can restore
the system data to the latest data backup using the M2000 restore mechanism.

Issue V2.0 (2009-02-28) Page 50 of 77
M2000
Product Description
Veritas System Backup and Restoration Solution

The third-party Veritas solution applies to backing up the whole system, including the
server and disk array.
The Veritas solution backs up the following data:
z Operating system
z Database
z Server application
z Other relevant data
You can back up the data described previously to a tape or tape drive.
After you back up the system through the Veritas solution, you can use the backup
data to restore the system to the latest backup even when the operating system is
damaged.
5.2.2 Operation Security

Login Control
The M2000 specifies the maximum number of login attempts.
If the number of login attempts of a user exceeds the maximum number, the M2000
locks this user, records the failure information in the system log, and generates an
internal alarm.
The M2000 unlocks the user after the locking period is up. You can define the locking
period. You can define the locking period, which is normally set to 30 minutes.
User Monitoring
The M2000 monitors operations of all users, and generates maintenance reports. The
user admin has the privilege to force any user to exit.
Operation Confirmation
The M2000 provides the function of confirming important or global operations.
5.3 Hardware Reliability

The M2000 hardware uses the dual-server mode. The two servers constitute a
symmetrical HA system through the dual-server software, and work in active/standby
mode. This backup mode features high reliability and uninterrupted running.
The M2000 also supports the single-server mode for installation convenience and cost
saving. In this mode, the hardware reliability is based on disk mirroring.
The M2000 uses the networking of dual O&M planes. Two independent
communication links form the O&M network. The M2000 detects the communication
status of these two links, and switches communications to the standby plane
automatically when detecting faults on the active plane. The dual O&M planes
guarantees reliability of the O&M network.

Issue V2.0 (2009-02-28) Page 51 of 77
M2000
Product Description
5.4 Software Reliability

The M2000 uses the self-protection mechanism and checks the status of all M2000
services periodically. For any faults that are detected, the M2000 records the fault
information in the system log, and then clears the fault or generates an alarm to
request for manual treatment.

Issue V2.0 (2009-02-28) Page 52 of 77
M2000
Product Description
6 Technical Specifications

This chapter lists system specifications, including
z Performance Specifications
z Physical and Electrical Specifications
z Reliability Specifications
z Compliant Safety Standards
z EMC Specifications
z Environmental Requirements
6.2 Performance Specifications

6.2.1 System Capacity
The M2000 calculates the system capacity by use of equivalent NEs. In addition, you
need to configure the server based on the number of equivalent NEs.
Depending on the versions of the operating system and database on the M2000
servers, the NE management capabilities of the M2000 servers are different even
when the same hardware is installed on the M2000 servers. Table 6-1 describes the
system capacity of the single-server system and HA system.
Sun servers are installed with the Solaris10 operating system and the Sybase15
database.
HP servers are installed with the SuSE10 Linux operating system and the Oracle10g
database.
ATAE is installed with the SuSE10 Linux operating system and the Oracle11g
database.
Table 6-1 M2000 system capacity (single system and HA system)

Server Hardware Management Capacity
Sun Sparc Enterprise ≤ 30 equivalent NEs

T5220 Server (1 CPU)

Issue V2.0 (2009-02-28) Page 53 of 77
M2000
Product Description
Server Hardware Management Capacity

M4000 Server (2 CPUs)
2 CPU HP rx2660 ≤ 45 equivalent NEs
2CPU ATAE ≤ 18 equivalent NEs
The number of equivalent NEs is associated with the following factors:

z NE type
z Performance measurement period
z Performance measurement object
z Performance measurement counter
For NEs of the same type, the number of equivalent NEs varies with different
measurement requirements proposed by customers.
Table 6-2 lists the number of equivalent NEs for common measurement and maximum
measurement when the measurement period is 60 minutes. To get the number of
equivalent NEs for the measurements unavailable in the list, contact Huawei
engineers for analysis and calculation. The number of equivalent NEs for the IP
networking devices is 0.
In the Table 6-2, the symbol "-" indicates that the measurement requirements for the NE have
no impact on the number of equivalent NEs.

Issue V2.0 (2009-02-28) Page 54 of 77
M2000
Product Description
Table 6-2 Number of equivalent NEs for CDMA NEs

NE Type Physical NE Equivalent NEs Common Equivalent NEs Maximum
for Common Measurement for Maximum Measurement
Measurement Measurement
CBSC+BTS 50 1 Measure only 2.5 Measure all

Sector-carrier common counters and
counters objects
cMSCV9 1 2 Measure 6 Measure all
(gateway common counters and
office) objects and objects
common
counters
cMSCV9 1 6 Measure 18 Measure all
common counters and
objects and objects
common
counters
cMSCV6 1 1 - - -
PDSN 1 1 - - -
MGW 1 0.7 Measure 1.4 Measure all
common counters and
objects and objects
common
counters
cHLR 1 0.1 - - -
TSC 1 0.1 - - -
GLMS 1 0.1 - - -
HA 1 0.1 - - -
AAA 1 0.1 - - -
SG7000 1 0.5 - - -
RAC + RAU 50 1 Measure only 2.5 Measure all
Sector-carrier common counters and
counters objects
6.2.2 Bandwidth
The bandwidth required between the M2000 client and the M2000 server is 512 kbit/s.
The bandwidth required between the NMS and the M2000 server is 256 kbit/s.
The bandwidth between the M2000 and the managed NEs varies according to the NE
type, the bandwidth required between the IP devices and the M2000 server is 16
kbit/s. The requirement for bandwidth of the NEs in the CBSS varies according to the

Issue V2.0 (2009-02-28) Page 55 of 77
M2000
Product Description
number of managed BTSs. Table 6-3 lists the bandwidth requirements for managing
CN and RASYS NEs.
If the Citrix networking solution is used, the required bandwidth between each
operation terminal and the Citrix server is 64 kbit/s.
Table 6-3 Bandwidth requirements for managing the CN and RASYS NEs
CN and RASYS NE Bandwidth Requirement (kbit/s)
cMSCV9 512
cMSCV6 256
PDSN 64
MGW 64
cHLR 64
TSC 64
GLMS 64
HA 64
AAA 64
SG7000 64
SIWF 64
POC Server 64
Table 6-4 lists the bandwidth requirements for managing CBSS NEs.
Table 6-4 Bandwidth requirements for managing CBSS NEs (Each BTS covers three
cells.)
Number of BTSs on Bandwidth requirement of one BSC and its
one BSC BTSs (kbit/s)
100 320
200 448
400 576
600 704
800 896
1000 1024

Issue V2.0 (2009-02-28) Page 56 of 77
M2000
Product Description
6.2.3 Data Processing Capability of the M2000 Server

Real-Time Alarm Processing Speed
Generally, an alarm is generated and then displayed on the M2000 client within six
seconds. The time spent for correlation analysis is not included.
Data Traffic on the M2000 Server with Normal Load

Table 6-5 lists the traffic of alarm data and performance data processed by the M2000
server with normal load.
Table 6-5 Data traffic on the M2000 server with normal load
Server Model Alarm Data Traffic Performance Data Traffic
(Pieces per Second) (Pieces per Second)
1-CPU Sun Sparc 2 90
Enterprise T5220 Server
Enterprise M4000 Server
8-CPU Sun Sparc 15 1,200
2 CPU HP rx2660 2 90
2 CPU HP rx7640 4 260
4 CPU HP rx7640 7 510
6 CPU HP rx7640 12 940
8 CPU HP rx7640 15 1200
6.2.4 Peak Alarm Processing Capacity

Table 6-6 lists the peak alarm data processing capabilities of the M2000 configured
with different server models when alarms are reported continuously for five minutes.

Issue V2.0 (2009-02-28) Page 57 of 77
M2000
Product Description
Table 6-6 M2000 alarm processing capability of various servers

Server Peak Alarm Processing Capacity (Record/Second)
Sun Sparc Enterprise 20

T5220 Server (1 CPU)
2 CPU HP rx2660 20
2 CPU HP rx7640 30
4 CPU HP rx7640 55
6 CPU HP rx7640 100
8 CPU HP rx7640 125
6.2.5 Alarm Data Storage Capacity

The M2000 system classifies alarms into the following categories:
z Current fault alarms
Current fault alarms are generated when faults occur in the system. When the
faults are cleared and the system recovers, the corresponding fault alarms are
labeled as cleared.
z Event alarms
Event alarms report the current status of the system during the system operation.
z History fault alarms
History fault alarms refer to the current fault alarms known and acknowledged,
and labeled as cleared.
z Shielded alarms
You can shield alarms as required. The shielded alarms are not displayed on the
client.
The alarm data in the M2000 can be stored in two modes: database and files. Only the
latest data is saved in the database. Files are used for saving data exported from the
database.
You can set the save days for the data in the database. The M2000 exports the data
that exceeds the save days into specified files. Then, the exported data is removed
from the database.

Issue V2.0 (2009-02-28) Page 58 of 77
M2000
Product Description
The alarm data that is stored in the database varies according to different server
model and the number of NEs managed by the M2000.
Table 6-7 lists the storage capacity of the alarm database on different servers.
Table 6-7 Storage capacity of the alarm database on different servers

Server Event History Current Shielded Keep Time
Hardware Alarm Fault Alarm Fault Alarm Alarm of the
Alarms
Sun Sparc 800,000 800,000 100,000 100,000 < 3 months

Enterprise
T5220
Server
Sun Sparc 5,000,000 5,000,000 600,000 600,000
Enterprise
M4000
Server
Sun Sparc 7,000,000 7,000,000 800,000 800,000
Enterprise
M5000
Server
HP rx2660 800 000 800 000 100 000 100 000
HP rx7640 7 000 000 7 000 000 800 000 800 000
The number of files containing exported data depends on the remaining disk space of
the server.
6.2.6 Number of Clients Simultaneously Started on the Server

The number of clients that can be started simultaneously on the server varies based
on the server model.
Table 6-8 lists the maximum number of M2000 clients simultaneously started on the
server.
Table 6-8 Maximum number of M2000 clients simultaneously started on the server
Server Model Maximum Number of Clients Connected
Simultaneously (Controlled by the M2000
License)
Sun Sparc Enterprise T5220 25

Server (1 CPU)
Sun Sparc Enterprise M4000 40
Server (2 CPUs)

Issue V2.0 (2009-02-28) Page 59 of 77
M2000
Product Description

Server (4 CPUs)
Server (4 CPUs)
Server (6 CPUs)
Server (8 CPUs)
2 CPU HP rx2660 25
2 CPU HP rx7640 30
4 CPU HP rx7640 50
6 CPU HP rx7640 80
8 CPU HP rx7640 80
If the Citrix networking scheme is adopted, the number of clients that can be
connected to the M2000 server is the same as the number in this table.
6.3 Physical and Electrical Specifications

Table 6-9 lists specifications of different models of M2000 servers.
Table 6-9 Specifications of different models of M2000 server and cabinet (Sun)
Item Specifications
Server model Sun Sparc Sun Sparc Sun Sparc

Enterprise Enterprise Enterprise M5000
T5220 Server M4000 Server Server
Server dimensions (W x 425 mm x 714 444 mm x 810 444 mm x 810 mm
D x H) mm x 88 mm mm x 263 mm x 440 mm
Server weight (kg) 23.58 84 125
Cabinet N610E-22 N610E-22 N610E-22
Cabinet dimensions (W x 600 mm x 600 mm x 1,000 600 mm x 1,000
D x H) 1,000 mm x mm x 2,200 mm mm x 2,200 mm
2,200 mm
Cabinet Power input (V) 220 V AC 220 V AC 220 V AC

Issue V2.0 (2009-02-28) Page 60 of 77
M2000
Product Description
Table 6-10 Specifications of different models of M2000 server and cabinet (HP)
Item Specifications
Server model HP rx2660 HP rx7640

Server dimensions (W x D x 482 mm x 672 mm x 86 482 mm x 762 mm x 445
H) mm mm
Server weight (kg) 28 101.6
Cabinet N610E-22 N610E-22
Cabinet dimensions (W x D 600 mm x 1000 mm x 600 mm x 1000 mm x
x H) 2,200 mm 2200 mm
Cabinet Power input (V) 220 V AC 220 V AC
Table 6-11 Specifications of different models of M2000 server and cabinet (ATAE)
Item Specifications
Subrack model AT8223

Subrack dimensions (W x D 436 mm x 619.5 mm x 450 mm
x H)
Subrack weight (kg) 127(full configuration)
Subrack Power 4000(full configuration)
consumption (W)
Cabinet N68E-22
Cabinet dimensions (W x D 600 mm x 800 mm x 2,200 mm
x H)
Cabinet Power input (V) DC: -48
AC: 220
Table 6-12 lists specifications of different models of single server system.
Table 6-12 Specifications of different models of single server system

Server Model Cabinet Number Quality in Power
Type of full consumption in
Cabinets configuration full configuration
(kg) (W)
Sun Sparc N610E-22 1 190 5,900

Enterprise
T5220 Server

Issue V2.0 (2009-02-28) Page 61 of 77
M2000
Product Description
Sun Sparc N610E-22 1 215 5,385

Enterprise
M4000 Server
Sun Sparc N610E-22 1 255 7,625
Enterprise
M5000 Server
HP rx2660 N610E-22 1 167.25 968
HP rx7640 N610E-22 1 280.6 3256
ATAE N68E-22 1 240 4800
Table 6-13 lists specifications of different models of HA system.
Table 6-13 Specifications of different models of HA system

Server Model Cabinet Number Quality in Power
Type of full consumption in
Cabinets configuration full configuration
(kg) (W)
Sun Sparc N610E-22 1 210 4,695

Enterprise
T5220 Server
Sun Sparc N610E-22 2 2 x 215 2 x 5,385
Enterprise
M4000 Server
Sun Sparc N610E-22 2 2 x 255 2 x 7,625
Enterprise
M5000 Server
HP rx7640 N610E-22 2 2×279.35 2×3246
Table 6-14 lists the power consumption of all the equipment in the M2000 system.
Table 6-14 Power consumption of all the equipment in the M2000 system
Equipment Power Consumption (W)
Sun Sparc Enterprise T5220 Server 795

Sun Sparc Enterprise M4000 Server 2350
Sun Sparc Enterprise M5000 Server 4590
HP rx2660 798
HP rx7640 2640

Issue V2.0 (2009-02-28) Page 62 of 77
M2000
Product Description
Citrix PC Server or USM Server (HP 1000

DL380G5)
Disk array(S3100/S3200) 446
Disk array(6140) 800
ATAE front board 170
ATAE back board 14.2
Front board of ATAE switch board 80
Back board of ATAE switch board 15
Quidway AR46-20 86
Quidway R28-10/AR28-11 60
LAN Switch S3928 40
LAN Switch S5624 170
KVM AC 120 V: 25
AC 230 V: 54.6
DC: 75
Mercury3600 20
6.4 Reliability Specifications

The reliability of the M2000 system relies on the server model and the hardware
configured.
Table 6-15 lists the reliability specifications for the M2000 system of the single-server
configuration.
Table 6-15 Reliability specifications for the M2000 system of the single-server
configuration
Server Model MTBF MTTR Annual Mean Availability
(Hour) (Hour) Failure Time
(Hour)
Sun Sparc 95082 4.011394 0.369558206 0.999957813

Enterprise 5
T5220 Server (1
CPU)
Sun Sparc 64776 3.437654 0.464867472 0.999946933
Enterprise 5
M4000 Server
(2 CPUs)

Issue V2.0 (2009-02-28) Page 63 of 77
M2000
Product Description
Sun Sparc 57110 3.372342 0.51724692 0.999940954

Enterprise
M4000 Server
(4 CPUs)
Sun Sparc 49238 3.305358 0.588021329 0.999932874
Enterprise 2
M5000 Server
(4 CPUs)
Sun Sparc 40980 3.349362 0.715910545 0.999918275
Enterprise 1
M5000 Server
(6 CPUs)
Sun Sparc 31629 3.398934 0.941271176 0.999892549
Enterprise 4
M5000 Server
(8 CPUs)
3.97387
HP rx2660 96192 0.361877241 0.99995869
37
rx7640 (2 3.21472
86259 0.326458203 0.999962733
CPUs) 69
rx7640 (4 3.34812
80324 0.365126106 0.999958319
CPUs) 92
rx7640 (6 3.45837
61567 0.492044185 0.999943831
CPUs) 74
rx7640 (8 3.49212
55298 0.553168112 0.999936853
CPUs) 58
ATAE 244 140 0.178679 0.0064 0.9999992681
623
Table 6-16 lists the reliability specifications for the M2000 system of the HA
configuration.
Table 6-16 Reliability specifications for the M2000 system of the HA configuration
Server Model MTBF MTTR Annual Mean Availability
(Hour) (Hour) Failure Time
(Hour)
Sun Sparc 95082 0.58333

Enterprise
333 0.053742755 0.999993865
T5220 Server (1
CPU)

Issue V2.0 (2009-02-28) Page 64 of 77
M2000
Product Description
Sun Sparc 64776 0.61666

Enterprise
667 0.083394291 0.99999048
M4000 Server
(2 CPUs)
Sun Sparc 57110 0.68333
Enterprise
333 0.104814015 0.999988035
M4000 Server
(4 CPUs)
Sun Sparc 49238 0.71666
Enterprise
667 0.127501292 0.999985445
M5000 Server
(4 CPUs)
Sun Sparc 40980 0.81666
Enterprise
667 0.174569484 0.999980072
M5000 Server
(6 CPUs)
Sun Sparc 31629 0.96666
Enterprise
667 0.267720801 0.999969438
M5000 Server
(8 CPUs)
rx7640 (2 86259 0.63333
CPUs) 0.064317454 0.999992658
333
rx7640 (4 80324 0.76666
CPUs) 0.083610576 0.999990455
667
rx7640 (6 61567 0.86666
CPUs) 0.123311078 0.999985923
667
rx7640 (8 55298 0.98333
CPUs) 0.155771399 0.999982218
333
6.5 Compliant Safety Standards

The M2000 complies with the following safety standards:
z IEC 60950-1
z IEC/EN41003
z EN 60950-1
z UL 60950-1
z CSA C22.2 No 60950-1
z AS/NZS 60950-1
z BS EN 60950-1
z IS 13252

Issue V2.0 (2009-02-28) Page 65 of 77
M2000
Product Description
z GB4943
6.6 EMC Specifications

The M2000 complies with the following Electromagnetic Compatibility (EMC)
standards:
z CISPR22 Class A
z EN55022 Class A
z EN50024
z ETSI EN 300 386 Serial Class A
z ETSI EN 301 489 Class A
z ICES 003 Class A
z AS/NZS CISPR22 Class A
z GB9254 Class A
z VCCI Class A
z CNS 13438 Class A
6.7 Environmental Requirements

Environmental requirements include the requirements for the storage, transportation,
and operation of the equipment.
The environmental requirements comply with the following two standards:
z ETS 300019 "Equipment Engineering (EE); Environmental conditions and
environmental tests for telecom equipment"
z IEC 60721 "Classification of environmental conditions"
6.7.1 Storage Environment

This section describes the climatic, waterproof, biological, air purity, and mechanical
stress requirements for equipment storage.
Climatic Requirements
Table 6-17 lists the climatic requirements for equipment storage.
Table 6-17 Climatic requirements for the equipment storage

Item Range
Altitude ≤ 5,000 m
Air pressure 70 kPa to 106 kPa
Temperature 0°C to +40°C
Temperature change
≤ 1oC/min
rate

Issue V2.0 (2009-02-28) Page 66 of 77
M2000
Product Description
Item Range
Relative humidity 10% to 100%

Solar radiation ≤ 1,120 W/s²
Heat radiation ≤ 600 W/s²
Wind speed ≤ 30 m/s
Waterproof Requirements
The equipment must be stored in a room where:
z No water accumulates on the ground or falls on the package.
z The equipment is kept away from water sources such as a hydrant and
air-conditioner.
If the equipment is placed outdoors, ensure that:
z The package is intact.
z Waterproof measures are applied to prevent water penetration.
z No water accumulates on the ground or flows into the package.
z The package is not exposed directly to sunlight.
Biological Requirements
Ensure that the place for equipment storage is free of:
z Fungus or mildew
z Rodents, such as rats
Air Purity Requirements

The air must be free of explosive, conductive, magnetic conductive or corrosive dust.
The density of physically active materials must comply with the requirements listed in
Table 6-18.
Table 6-18 Storage requirements for physically active materials

Physically Active Material Unit Density
Suspended dust mg/m³ ≤ 5.00

Falling dust mg/m²·h ≤ 20.0
Sand mg/m³ ≤ 300

Issue V2.0 (2009-02-28) Page 67 of 77
M2000
Product Description
Note:
Suspended dust: Diameter ≤ 75 μm
Falling dust: 75 μm ≤ Diameter ≤ 150 μm
Sand: 150 μm ≤ Diameter ≤ 1 000 μm
The density of chemically active materials must comply with the requirements listed in
Table 6-19.
Table 6-19 Storage requirements for chemically active materials

Chemically Active Material Unit Density
SO2 mg/m³ ≤ 0.30

H2S mg/m³ ≤ 0.10
NO2 mg/m³ ≤ 0.50
NH3 mg/m³ ≤ 1.00
Cl2 mg/m³ ≤ 0.10
HCl mg/m³ ≤ 0.10
HF mg/m³ ≤ 0.01
O3 mg/m³ ≤ 0.05
Mechanical Stress Requirements

Table 6-20 lists the mechanical stress that the equipment can endure during storage.
Table 6-20 Storage requirements regarding mechanical stress

Item Sub-Item Range
Offset ≤ 7.0 mm None

Sinusoidal
vibration
Accelerated speed None ≤ 20.0 m/s²
Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz
Impact response
≤ 250 m/s²
Unsteady impact spectrum II
Static payload ≤ 5 kPa

Issue V2.0 (2009-02-28) Page 68 of 77
M2000
Product Description
Item Sub-Item Range
Note:
Impact response spectrum: refers to the maximum acceleration response curve generated by
the equipment under specified impact excitation. Impact response spectrum II means that the
duration of semi-sine impact response spectrum is 6 ms.
Static payload: refers to the capability of the equipment to bear the pressure from the top when it
is packed in the normal pile-up method.
6.7.2 Transportation Environment

stress requirements for equipment transportation.
Table 6-21 lists the climatic requirements for the transportation of the equipment.
Table 6-21 Climatic requirements for transporting the equipment

Item Range
Temperature 0 °C to +40 °C
Temperature change rate ≤ 3°C/min
Humidity 5% to 100%
Solar radiation ≤ 1, 120 W/s²
Heat radiation ≤ 600 W/s²
Waterproof Requirements
Before transporting the equipment, ensure that:
z The package is intact.
z Waterproof measures are applied to prevent water penetration.
z There is no water in the vehicle.
Ensure that the vehicle is free of:
z Fungus or mildew
z Rodents such as rats

Issue V2.0 (2009-02-28) Page 69 of 77
M2000
Product Description

The air must be free of explosive, conductive, magnetic conductive or corrosive dust.
Table 6-22.
Table 6-22 Requirements on physically active materials in the transportation environment

Suspended dust mg/m³ No requirement

Falling dust mg/m²·h ≤ 3.0
Sand mg/m³ ≤ 100
Note:
Suspended dust: diameter ≤ 75 μm
Falling dust: 75 μm ≤ diameter ≤ 150 μm
Sand: 150 μm ≤ diameter ≤ 1,000 μm
Table 6-23.
Table 6-23 Transportation requirements of physically active materials

Chemically Active
Unit Density
Material
SO2 mg/m³ ≤ 0.30

H2S mg/m³ ≤ 0.10
NO2 mg/m³ ≤ 0.50
NH3 mg/m³ ≤ 1.00
Cl2 mg/m³ ≤ 0.10
HCl mg/m³ ≤ 0.10
HF mg/m³ ≤ 0.01
O3 mg/m³ ≤ 0.05

Table 6-24 lists the mechanical stress that the equipment can endure during
transportation.

Issue V2.0 (2009-02-28) Page 70 of 77
M2000
Product Description
Table 6-24 Transportation requirements regarding mechanical stress

Item Sub-Item Range
Offset ≤ 7.5 mm -- --
Sinusoida Accelerated speed -- ≤ 20.0 m/s² ≤ 40.0 m/s²
l vibration
9 Hz to 200 Hz to
Frequency range 2 Hz to 9Hz
200 Hz 500 Hz
Spectrum density of
10 m²/s³ 3 m²/s³ 1 m²/s³
Random accelerated speed
vibration 9 Hz to 200 Hz to
Frequency range 2 Hz to 9Hz
200 Hz 500 Hz
Impact response
Unsteady ≤ 300 m/s²
spectrum II
impact
Static payload ≤ 10 kPa
Note:
Static payload: refers to the capability of the equipment in package to bear the pressure from
the top in normal pile-up method.
6.7.3 Operation Environment

stress requirements for equipment operation.
Table 6-25 and Table 6-26 list the climatic requirements for the operation of the
equipment.
Table 6-25 Temperature and humidity requirements for the operation of the M2000
Temperature Relative Humidity
Normal Safe Normal Safe

15°C to 30°C 0°C to 40°C 20% to 80% 20% to 90%
Note:
The values are measured 1.5 m above the floor and 0.4 m in front of the equipment,
without protective panels in front of or behind the cabinet.
Safe operation refers to continuous operation for not more than 48 hours or accumulated
operation of not more than 15 days in a year.

Issue V2.0 (2009-02-28) Page 71 of 77
M2000
Product Description
Table 6-26 Other climatic requirements for the operation of the M2000
Item Range
Temperature change rate ≤ 3 °C/min
Solar radiation ≤ 700 W/m²
Heat radiation ≤ 600 W/m²
Ensure that the place for storing the equipment is free of:
z Fungus or mildew
z Rodents such as rats

The air must be free of explosive, conductive, magnetic, conductive, or corrosive dust.
Table 6-27.
Table 6-27 Operation requirements for physically active materials

Physically Active
Unit Density
Material
≤ 3 x 104
Dust particles Particles/m³ (Visible dust must not accumulate on the
desktop within three days.)
Note:
Dust particles: diameter ≥ 5 μm
Table 6-28.
Table 6-28 Operation requirements for chemically active materials

Chemically active material Unit Density
SO2 mg/m³ ≤ 0.20

H2S mg/m³ ≤ 0.006

Issue V2.0 (2009-02-28) Page 72 of 77
M2000
Product Description
Chemically active material Unit Density
NH3 mg/m³ ≤ 0.05

Cl2 mg/m³ ≤ 0.01

Table 6-29 lists the mechanical stress that the equipment can endure during its
operation.
Table 6-29 Operation requirements regarding mechanical stress

Item Sub-item Range
Offset ≤ 3.5 mm --
Sinusoidal
vibration
Accelerated speed -- ≤ 10.0 m/s²
Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz
Impact response spectrum
≤ 100 m/s²
Unsteady impact II
Static payload 0
Note:
Static payload: refers to the capability of the equipment to bear the pressure from the top
when it is packed in the normal pile-up method.

Issue V2.0 (2009-02-28) Page 73 of 77
M2000
Product Description
7 Acronyms and Abbreviations
Numerics
3GPP 3rd Generation Partnership Project
A
AAA Authentication，Authorization and Accounting
AC Alternating Current
AC Authentication Center
B
BSC Base Station Controller
BTS Base Transceiver Station
C
CDMA Code Division Multiple Access
CN Core Network
CORBA Common Object Request Broker Architecture

CPU Center Processing Unit
CSV Comma Separation Value
D
DC Direct Current
DDN Digital Data Network
DPS Dispatcher Server
DPT Dispatcher

Issue V2.0 (2009-02-28) Page 74 of 77
M2000
Product Description
DST Daylight Saving Time
E
EM Element Management
EMC Electromagnetic Compatibility
EMS Element Management System
ETS European Telecommunication Standards
ETSI European Telecommunications Standards Institute
F
FTP File Transfer Protocol
G
GByte Gigabyte
GHz Gigahertz
GLMS Group and List Management Server
GMSC Gateway Mobile Switching Center
GUI Graphic User Interface
H
HA High Availability
HA Home Agent
HLR Home Location Register
HTML Hyper Text Markup Language
I
ID Identity
IEC International Electrotechnical Commission
iGWB iGateway Bill
IP Intelligent Peripheral
IRP Integration Reference Point
Itf-N Northbound Interface

Issue V2.0 (2009-02-28) Page 75 of 77
M2000
Product Description
K
KPI Key Performance Index
L
LAN Local Area Network
LMT Local Maintenance Terminal
M
MSC Mobile Service Switching Center
MSCe Mobile Switching Center emulation
MTBF Mean Time Between Failures
MTTR Mean Time To Repair
MGW Media Gate-Way
MML Man Machine Language
N
NMS Network Management System
NTP Network Time Protocol
P
PC Personal Computer
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
S
SCP Service Control Point
SG Singling Gateway

Issue V2.0 (2009-02-28) Page 76 of 77
M2000
Product Description
SMC Short Message Center

SNMP Simple Network Management Protocol
SNTP Simple Network Time Protocol
SSP Service Switching Point
T
TCP Transfer Control Protocol
TMN Telecommunication Management Network
TSC Trunking Switching Center
V
VLR Visitor Location Register
VPN Virtual Private Network
X
XML Extensible Markup Language

Issue V2.0 (2009-02-28) Page 77 of 77

M2000 Product Description (CDMA)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

M2000 Product Description (CDMA)

Загружено:

Авторское право:

Доступные форматы

M2000 V200R008

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential

1 Introduction to the M2000 ..............................................................................................7

2 Key Benefits ..................................................................................................................15

3 System Architecture .....................................................................................................18

4 Services and Functions................................................................................................32

Huawei Proprietary and Confidential

4.1 About This Chapter......................................................................................................................... 32

Huawei Proprietary and Confidential

4.7.6 Individual Setting ................................................................................................................... 43

6 Technical Specifications ..............................................................................................53

Huawei Proprietary and Confidential

6.5 Compliant Safety Standards........................................................................................................... 65

7 Acronyms and Abbreviations ......................................................................................74

Huawei Proprietary and Confidential

1 Introduction to the M2000

1.1 About the M2000

1.2 Position of the M2000 in the Network

Huawei Proprietary and Confidential

Figure 1-1 Networking of Huawei CDMA 1X/1xEV-DO/digital trunking system

Figure 1-2 shows the position of the M2000 in a WLL network.

Huawei Proprietary and Confidential

Figure 1-2 Networking of Huawei RASYS system

Table 1-1 Functions of the elements in the CDMA network

Provides the following functions:

Huawei Proprietary and Confidential

Provides the following functions:

The soft switching center in a CDMA network. It incorporates the VLR

Huawei Proprietary and Confidential

Deals with the format conversion and signaling conversion of media

A database for mobile subscriber management. It is integrated

Huawei Proprietary and Confidential

Manages the information about:

Huawei Proprietary and Confidential

The centralized management platform for Huawei mobile

1.3 Interfaces of the M2000

Figure 1-3 Interfaces provided by the M2000

Table 1-2 Interfaces provided by the M2000 and thee properties

Common Object Request Broker

Huawei Proprietary and Confidential

Peer Protocol Transmission

Huawei Proprietary and Confidential

2.1 Challenges and Trends

2.2 Advanced Componentized Architecture

Huawei Proprietary and Confidential

2.3 Flexible Networking Mode

2.4 Various Interfaces

Huawei Proprietary and Confidential

2.5 Powerful Operation and Maintenance Function

2.6 Comprehensive Operation and Maintenance Solution

Huawei Proprietary and Confidential

3.1 About This Chapter

3.2 Physical Structure

3.2.2 Physical Structure of the Single-Server System

Huawei Proprietary and Confidential

Figure 3-1 M2000 single-server system

3.2.3 Physical Structure of the HA System

Figure 3-2 Physical structure of the M2000 (HA system)

Table 3-1 describes the devices at the server side.

Table 3-1 Devices at the server side (HA system)