iManager M2000 V200R011 Product IMS V2.1(20110630)

iManager M2000 V200R011 Product Description

Issue

V2.1

Date

2011-06-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. 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. implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]


Contents 1 Introduction............................. Introduction.................................................... .............................................. .............................................. ............................................. .................................. ............ 5 1.1 Positioning ....................................................................................................................................................... 5 1.2 Managed NEs ..................................................... ................................................................. ............................. 5 1.2.1 CBSS NEs ............................................................ .............................................................. ..................... 5 1.2.2 CN NEs ..................................................... ................................................................. ............................. 5 1.2.3 STP NEs ............................................................... ................................................................. .................. 6 1.2.4 IMS NEs ................................................................................................................................................. 6 1.2.5 Transmission and Other Devices.......................................................... ................................................... 7 1.3 Benefits ............................................................................................................................................................ 7

2 Architecture ............................................. ................................................................... ............................................ ............................................. ........................................... ....................9 2.1 Overview ............................................................ ................................................................. ............................. 9 2.2 Hardware Structure .......................................................................................................................................... 9 2.3 Software Structure ......................................................... .............................................................. ..................... 9 2.4 External Interfaces ......................................................................................................................................... 10

3 Products and Application Scenarios ......................................................... ................................................................................ .............................. ....... 12 3.1 Overview ............................................................ ................................................................. ........................... 12 3.2 OM Solutions ................................................................................................................................................. 12 3.3 Network Deployment .................................................................................................................. ................... 18 3.4 Network Monitoring ................................................................ ............................................................... ........ 19 3.5 Network Adjustment ................................................................................................ ...................................... 22 3.6 Service Management ................................................................................................................... ................... 22

4 Configuration.............................................. .................................................................... ............................................ ............................................. ..................................... .............. 23 5 Operation and Maintenance ............................................................ ................................................................................... ......................................... .................. 25 5.1 Overview ............................................................ ................................................................. ........................... 25 5.2 OM Features ....................................................... ................................................................. ........................... 25

6 Technical Specifications ........................................................ .............................................................................. ............................................. .............................. ....... 28 6.1 Overview ............................................................ ................................................................. ........................... 28 6.2 Management Capability ................................................................................................................................. 28 6.3 Reliability Specifications ............................................................................................................................... 29 6.4 Compliant Safety Standards ........................................................................................................ ................... 31 6.5 EMC Specifications ....................................................................................................................................... 31 6.6 Environmental Requirements ................................................................................................................. ........ 31 Huawei Proprietary and Confidential IssueV2.1 (2011-06-30)

Page 3 of 39 Copyright © Huawei Technologies Co., Ltd.


6.6.1 Storage Environment ................................................................. ............................................................ 31 6.6.2 Transportation Environment ................................................................................................................. 34 6.6.3 Operating Environment ............................................................. ............................................................ 36

A Acronyms and Abbreviations.................................................................................................. 39

Huawei Proprietary and Confidential IssueV2.1 (2011-06-30)



1

Introduction

1.1 Positioning This manual is used only for the iManager M2000 Mobile Element Management System V200R011. The iManager M2000 Mobile Element Management System (hereinafter referred to as the M2000) manages the network devices provided by Huawei in a centralized manner. These devices include NEs in the CBSS system, CN network, STP network, and IMS network. In addition, the M2000 manages the transmission devices and other devices used in the mobile network. The M2000 provides basic network management functions such as configuration management, performance management, fault management, security management, log management, topology management, software management, and system management. In addition, the M2000 provides rich optional functions. The M2000 provides the centralized operation and maintenance (OM) functions for the Huawei mobile element management solution. The M2000 system adopts a modular design. The modules communicate with each other through the CORBA bus. The M2000 provides the mediation for adaptation of various types of NEs. In addition, the M2000 provides external interfaces, which allow for interoperability with other systems.

1.2 Managed NEs This section introduces the NEs managed by the M2000.

1.2.1 CBSS NEs The M2000 manages the following NEs in the CBSS: 

Base Transceiver Station (CBTS)



Base Station Controller (CBSC)



Radio Access Unit (RAU)



Radio Access Controller (RAC)

1.2.2 CN NEs CN refers to the core network (CN) equipment of Huawei. M2000 can manage both fixed and mobile CN devices: Huawei Proprietary and Confidential IssueV2.1 (2011-06-30)





Mobile Switching Center (CMSC)



Mobile Service Switching Center Server (MSCe)



Media Gateway (MGW)



Fixed-Mobile Convergence Media Gateway (FMC MGW)



Home Location Register (CHLR9820)



Home Location Register-(Data Node) (CHLR-DC)



Home Location Register-(Service Node) (CHLR-SC)



Signaling Gateway (SG7000)



Packet Data Serving Node (PDSN)



Home Agent (HA)



Authentication, Authorization and Accounting (AAA)



Trunking Switching Center (TSC)



Group and List Management Server (GLMS)



Push-To-Talk over Cellular Server (POC Server)

1.2.3 STP NEs The M2000 manages the following STP NEs: 

CAS Service Processing System (CAS9910)



SPS Signaling Service Processing System (SPS)



Signaling Gateway (SG7000)

1.2.4 IMS NEs The M2000 manages the following IMS NEs: 

Media gateway (MGW)



Session Border Controller (SBC) (SE2300, SE2600)



Home Subscriber Server (HSS) (HSS9820)



Calling Session Control Function (CSCF) (CSC3300)



Unified policy and charging controller(UPCC)



Charging Collection Function (CCF) (iCG9815)



Advanced Telephony Server (ATS) (ATS9900)



Multimedia Exchange Server (MediaX) (MediaX3600)



IP Centrex (IPCTRX) (ETAS9960)



Multimedia Resource Function Processor (MRFP) (MRP6600)



SingleSDBDatabase (USCDB)



Attachment Information Management System (AIM) (AIM6300)



Service Provisioning Gateway (SPG) (SPG2800)



Unified Gateway Controller (UGC) (UGC3200)



E.164 Number (ENUM)



CAS Service Processing System (CAS9910)



Mediation Huawei Proprietary and Confidential

IssueV2.1 (2011-06-30)





Presence server, Group server, Messaging s erver (PGM)



ENS-FE



Multipoint Control Unit (MCU)



Open Service Gateway (OSG)



Access Gateway Control Function (AGCF) (UAC3000)

1.2.5 Transmission and Other Devices The M2000 manages the following transmission devices and other devices: 

Wireless Bearer Network Supported Devices (Metro1000V3, OSN3500, RTN, and BITS)



Routers of NE08 series, Routers of AR46-series (AR4640)



LAN switches of S series



Firewalls of Eudemon series



Domain Name Server (DNS)



Dynamic Host Configuration Protocol Server (DHCP Server)



NE Bearing Server (the server that bears the SG7000, MSCe)



Wi-Fi device: Skyway Excel XL5810 from the third-party

1.3 Benefits Open Structure Allows for Smooth Evolution The M2000 is a future proof solution for management of mobile networks. It provides a centralized network management platform to support telecom operators in their long-term evolution. The M2000 provides a complete support for all mobile network operators, regardless of what combination of network technologies they are deploying. The M2000 is a centralized radio network management platform. The M2000 server software consists of main version software and mediation software. The main version software implements system functions, and the mediation software is for adaptation of different NE interfaces. The M2000 can manage new NEs after the corresponding mediation software is installed. The M2000 is the core system that manages the CDMA/LTE radio networks, core networks, STP, and IMS. The great flexibility of the M2000 makes it possible to provide optimal network management in each phase of its evolution. The M2000 provides standard CORBA, SNMP, file, and alarm streaming interfaces. In addition, the M2000 allows for interoperability with other s ystems provided by HP, Aircom, IBM, Inspur, Remedy, Vallent, Mycom, and Bright Oceans.

Powerful Network Management Centralized management of large-sized networks requires high system performance. In addition, today's market demand focuses on hardware reuse and smooth expansion. To meet the demand, the M2000 provides the multi-server load-sharing (SLS) system based on the Sun platform and the cluster solution based on the ATAE platform. This implements the smooth expansion of networks. During network expansion, users can enhance the Huawei Proprietary and Confidential IssueV2.1 (2011-06-30)



management capability of the M2000 by adding one or multiple servers in the SLS system or adding service blades in the ATAE cluster system. This protects telecom operator's hardware investments and reduces network deployment costs.

Intelligent Platforms Reduce OPEX The iSStar secondary development platform enables OM engineers to customize a s ervice process by editing programs. Thus, the M2000 can automatically handle OM tasks in batches. In addition to common functions, the M2000 provides a series of specific functions such as network health check, remote NE upgrade and batch upgrade of NEs, device panel, and maintenance-mode alarm setting. These functions significantly improve the work efficiency of OM engineers and lower operation costs.




2

Architecture

2.1 Overview The M2000 system works in client/server (C/S) mode. The M2000 software consists of the client software, server software, and NE mediation software. The client software runs on the M2000 client, and the server software and mediation software run on the M2000 server. This chapter describes the hardware and software structures of the M2000 s ystem.

2.2 Hardware Structure A typical M2000 system consists of M2000 servers, M2000 clients, alarm boxes, and some networking devices. Figure 2-1 shows the hardware structure of the M2000 single-server system. The M2000 provides multiple solutions to meet the specific scenario requirements of telecom operators. For details about these solutions, see section 3.2 "OM Solutions". Figure 2-1 Hardware structure of the M2000 single-server system

2.3 Software Structure As shown in Figure 2-2, the M2000 software is classified into the following t ypes: 

M2000 server software



M2000 client software Huawei Proprietary and Confidential

IssueV2.1 (2011-06-30)





NE mediation software

NE mediation software varies according to the NE version. Through the adaptation of the NE mediation software, the M2000 connects to the NE of the corresponding version. Figure 2-2 Software structure of the M2000 system

2.4 External Interfaces To adapt to non-Huawei systems and software, the M2000 provides the following interfaces: 

CORBA interface The CORBA interface is based on CORBA interface specifications and is in compliance with 3GPP R6 specifications. Through the CORBA interface, the NMS manages M2000 alarms, sets performance measurement tasks, and queries M2000 configuration data.



CORBA security interface Through the CORBA security interface, the NMS manages M2000 users and user rights, such as creating users and maintaining user information.



File interface The M2000 saves alarm data, performance data, configuration data, and inventory data as files. Through the file interface, the NMS obtains and processes these files.



Alarm streaming interface The M2000 forwards NE alarms to the NMS in the form of character stream in real time. The NMS can actively obtain the list of active alarms from the M2000.



SNMP interface




Through the SNMP alarm interface, the M2000 forwards alarms to the NMS in real time. The NMS can handle the alarm. The SNMP interface supports SNMPv1, SNMPv2, and SNMPv3 protocols. 

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 related NEs by running MML commands.



Syslog interface The M2000 forwards operating system logs, M2000 logs, and NE logs using the Syslog protocol.




3

Products and Application Scenarios

3.1 Overview The M2000 provides various OM solutions for telecom operators to meet the requirements of network deployment, network monitoring, network adjustment, and service management. Telecom operators can select proper M2000 systems as required.

3.2 OM Solutions The M2000 provides various OM solutions based on M2000 system solutions and platforms: 

SLS, remote HA, and emergency systems are developed based on the Sun platform.



The local HA system is supported by Sun, HP, and ATAE platforms.

Sun-Based SLS System Developed on the Sun platform, the SLS system allows the deployment of multiple servers to implement the centralized management of large-sized networks. In the M2000 SLS system, multiple servers are deployed to form an EMS, and services are loaded and processed on different servers in a distributed manner. The SLS system manages multiple M2000 servers in a centralized manner and supports the smooth expansion of the M2000. Thus, the costs for operating and maintaining multiple M2000 systems are reduced. Figure 3-1 shows the physical structure of an M2000 SLS system. Figure 3-1 Physical structure of an M2000 SLS system




Table 3-1 describes the devices on the server side in the SLS system. Table 3-1 Devices on the server side in the SLS system

Device

Description

Master server

The master server runs the M2000 server software and balances load with slave servers.

Slave server

Slave servers run the M2000 server software and balance load with the master server.

Standby server

The standby server functions as a backup for the master or slave server. If the master server or the slave server becomes unavailable, the services carried by the master or slave server are switched over to the standby server through the cluster software.

Disk array

The disk array provides reliable storage for the master and slave servers. When an exception occurs on the master server or on a slave server, the cluster software mounts the disk array to the standby server.

ATAE Cluster Solution Developed on the ATAE platform, the ATAE cluster system allows the deployment of multiple blades to provide powerful management capability. Consisting of multiple server blades, switching blades, OSS self management unit (OSMU), and disk arrays, the ATAE cluster system has the following features: 

High integration



high performance



N:1 redundancy



hardware redundancy



blade plug-and-play



OSMU intelligent management

With the increasing demand of enhanced management capability, users can implement capacity expansion by adding blades. In addition, multiple OSS products, such as the M2000 and the PRS, can be deployed on the ATAE cluster system in a centralized manner. This enables telecom operators to use multiple OSS products at the same time. Figure 3-2 shows the physical structure of the ATAE cluster system.




Figure 3-2 Physical structure of the ATAE cluster system

Table 3-2 describes the devices on the server side in the ATAE cluster system. Table 3-2 Devices on the server side in the ATAE cluster system

Device

Description

ATAE subrack

An ATAE subrack can be configured with 14 blades. The typical configuration in the scenario where the M2000 is deployed in an ATAE subrack is as follows:

Disk array



The OSMU monitors and manages the entire ATAE cluster system and can be accessed through a Web browser.



Two switching blades provide the functions of a switch.



One master service blade, one slave service blade, one standby blade, and one database blade form the M2000 system.



One standby database blade provides the hot backup service for the database blades of the M2000 and the PRS.



Three reserved blades are used for capacity expansion.



Three reserved blades are used for the PRS when deploying with the M2000.

Other server blades except the OSMU use the disk array as a storage device.

Local Disaster Recovery Huawei provides an M2000 high availability (HA) system where services are automatically switched over from the active server to the standby server when an exception occurs in the active server. In this way, the reliability of the M2000 system is improved. The active and standby servers are placed together to constitute an HA system through the cluster software. The active and standby servers communicate with each other on a local area network (LAN) and gain access to the same disk array. Figure 3-3 shows the physical structure of an M2000 HA system.




Figure 3-3 Physical structure of the M2000 HA system

Table 3-3 describes the devices on the server side in the HA system. Table 3-3 Devices on the server side in the M2000 HA system

Device

Description

Active server

The active server functions as the M2000 system active server. It runs the M2000 server software. The active server, together with the standby server, performs resource monitoring and service switchover through the cluster software.

Standby server

The standby server functions as a backup for the active server. When the active server becomes unavailable, the resources carried by the active server are switched over to the standby server through the cluster software.

Disk array

Two disk arrays, one of which is the mirror of the other, provide reliable storage space. When an exception occurs on the active server, the cluster software mounts the disk array to the standby server.

Sun-Based Remote Disaster Recovery Huawei remote HA system provides software and hardware redundancy. It also effectively reduces the losses caused by power failures, earthquakes, fires, wars, tsunamis, and mudflows. Thus, remote protection is implemented on both the M2000 servers and the disaster recovery capability of the M2000 is improved. The active and standby servers in different locations constitute a remote HA system through the cluster software. The active and standby servers communicate with each other through the OM network and gain access to different disk arrays. Figure 3-4 shows the physical structure of a remote HA system.




Figure 3-4 Physical structure of a remote HA system

Table 3-4 describes the devices on the server side in the remote HA system. Table 3-4 Devices on the server side in the remote HA system

Device

Description

Server

The server functions as the M2000 system server. It runs the M2000 server software. The servers in equipment rooms I and II perform resource monitoring and service switchover through the cluster software.

Disk array

The disk array provides the server with reliable storage.

Sun-Based Emergency System The emergency system has lower hardware requirements than typical local and remote HA systems. The emergency system is applicable to the M2000 single-server and SLS systems that are based on the Sun platform. The emergency system functions as a backup for the M2000 primary system. It provides basic network management services when the primary system fails to provide services properly. The emergency system and the primary system can be deployed on the same LAN. They can also be deployed on different LANs and in this case they communicate with each other through an IP network. An emergency system can back up N (no more than four) M2000 single-server systems or N (no more than two) M2000 SLS systems. The system to be backed up is referred to as a primary system. When the emergency system takes over the services of a primary system, it cannot take over the services of any other primary system. Figure 3-5 shows the physical structure of the emergency system that backs up N M2000 single-server systems. Figure 3-6 shows the physical structure of the emergency system that backs up an M2000 SLS system.




Figure 3-5 Physical structure of the M2000 emergency system when it backs up N (N ≤ 4)M2000 single-server systems

Figure 3-6 Physical structure of the M2000 emergency system when it backs up N (N ≤ 2) M2000 SLS systems

Table 3-5 describes the devices on the server side. Table 3-5 Devices on the server side of the emergency system

Device

Description

Server

The server of the emergency system functions as a backup for the server of the primary system. When the server of the primary system becomes unavailable, the carried services are manually switched over to the server of the emergency system.

Disk array

The disk array provides the server with reliable storage.

Web-Based Client Access The M2000 provides the Citrix access solution, which enables users to log in to the M2000 client and perform routine OM operations through a Web browser on a PC with low configurations.




In the Citrix access solution, one or more servers are added to the existing M2000 system. The Citrix access solution has the following advantages: 

Solving the problem that the number of connected clients is restricted by the hardware capacity of the M2000 server



Reducing the costs of upgrading and maintaining the M2000 client



Reducing the hardware configuration costs of the PC where the M2000 client is running



Lowering the requirements for the operating system environment of the PC where the M2000 client is running

Network Time Synchronization Solution The M2000 supports the Network Time Protocol (NTP)/Simple Network Time Protocol (SNTP) so that the time of NEs on the entire network is synchronized. 

The clock source and NTP server are provided by a telecom operator, and the M2000 server functions as the NTP client or intermediate NTP server. When functioning as an intermediate NTP server, the M2000 can synchronize time with the upper-layer NTP server and provide a clock source for managed NEs to synchronize.



A dedicated clock server is provided. In addition, two NTP service channels working in active/standby mode are provided. The clock source server can be deployed as the top NTP clock server, or as a medium NTP clock server.

Veritas System Backup and Restore Solution The M2000 adopts the Veritas system backup and restore solution. This solution enables users to back up and restore the key data on the entire network, for example, applications, key files, data stored in the database, and key NE data.

3.3 Network Deployment Flexibly Managing and Mediating NEs The mediation software can be installed to convert data between NEs and the M2000 so that the M2000 can manage NEs. The M2000 can dynamically install NE mediations, or upgrade NE mediation patches without disrupting M2000 services on a web-based GUI or command line interface. When managing various types of NEs, the M2000 can install mediations in batches without disrupting M2000 services. This reduces the costs of manual operations and interventions.

Remote and Centralized Initial Configuration The M2000 provides the remote and centralized initial configuration function during initial network configuration. 

Through a GUI The M2000 provides the graphical configuration function for users to configure the CBSS NEs, which enables users to view and configure the configuration data of the NEs and of the managed objects (MOs) on the CDMA access network. The M2000 provides a basic configuration function for all NEs in the CS domain on the CN. Users can prepare Huawei Proprietary and Confidential

IssueV2.1 (2011-06-30)



configuration data in batches and remotely configure basic device data in a centralized manner through a GUI. NEs can provide basic services after being configured initially. 

Through a command-line interface The M2000 provides a command-line interface, which enables users to issue MML commands to multiple NEs of the same type on the M2000 client. Users can save MML commands in a script and then schedule and deliver the script to NEs through the M2000. Users can issue MML commands in debugging mode or task mode. When issuing commands in debugging mode, users can check script execution information and execution result of each command in real time. When issuing commands in task mode, users only need to select a required script and then create a task by using the centralized task management function.

Radio Transmission Device Search The M2000 can manage a large number of transmission devices such as microwaves in mobile networks in a centralized manner. The radio transmission device search function enables users to search for all the transmission devices that meet specified search conditions. Then, users can select the required devices from the search result and create the related NEs in a topology view. In this way, these devices are connected to the M2000 quickly.

Remote and Centralized NE Upgrade NE device upgrade is a common OM operation for service evolution. The M2000 can remotely upgrade NE devices in batches in a centralized manner. Users can implement dynamic mediation simply by upgrading NE software versions through the M2000. This minimizes the impact of NE upgrade on the OM of the entire network.

NE Health Check The NE health check function is used to check NE status and identify and locate potential network problems before and after an NE upgrade, during routine network maintenance, or when an exception occurs in the network. This facilitates troubleshooting.

3.4 Network Monitoring Topology Monitoring The M2000 provides an integrated topology window, through which users can create and manage the topology view of the entire network. The topology view displays the networking status, geographical locations of devices, alarms generated during device operation, link status between devices, and connection status between devices and the M2000. This helps users to learn about and monitor the running status of the entire network.

Performance Monitoring Using the performance monitoring function, the M2000 collects KPIs in real time, provides associated data analysis, threshold alarm settings, and threshold warnings, and displays the network operating status in a graph correctly. This facilitates routine network maintenance and fault locating. In addition, the M2000 provides performance monitoring functions based Huawei Proprietary and Confidential IssueV2.1 (2011-06-30)



on scenarios such as network deployment, routine maintenance, and operations during holidays, meeting various user requirements.

Alarm and Event Monitoring In scenarios such as NE deployment, upgrade, commissioning, and capacity expansion, NEs report a large number of unnecessary alarms to the M2000. These alarms severely affect the monitoring of alarms on devices that are not in maintenance mode. To solve this problem, the M2000 provides the maintenance mode alarm function. After users set maintenance modes for an NE, alarms generated in the NE maintenance modes are regarded as maintenance mode alarms. By default, the M2000 does not display maintenance mode alarms, generate an audio or visual alarm message, send an alarm notification, or forward these alarms to an external system. In the alarm monitoring window, users can browse, query, and collect statistics on maintenance mode alarms by maintenance mode to meet user requirements in specified scenarios. In common OM scenarios, the M2000 enables users to view the alarm and event information about all NEs on the network in real time. The M2000 provides various functions based on the requirements for monitoring system performance and handling alarms. 

To ensure that alarm data is accurate and intact, the M2000 provides the functions of automatically and manually synchronizing alarm data in case of NE or network disconnection.



To ensure that information can be effectively transmitted to users in real time, the M2000 provides audio and visual alarm notification through topology tips, alarm boxes, and alarm boards. The M2000 can also send alarm information through short message services (SMSs) and emails to ensure that the information can be transmitted in time even when the site is unmanned.



To help users to quickly locate the required information in a large amount of alarm or event information, the M2000 provides the filtering function based on various conditions. For example, users can filter alarm/event information by alarm/event source, alarm/event occurrence time, alarm/event severity, and alarm/event name.



To ensure that users can identify the required key alarms and events during routine operation and maintenance, the M2000 provides the functions of redefining alarm severities, converting events to Auto Detected Manual Cleared (ADMC) alarms, shielding alarms on the M2000, shielding alarms on NEs, filtering maintenance mode alarms, summarized parallel alarms, and alarm frequency analysis.



To help users to handle alarms in time, the M2000 provides the functions of locating alarms in a topology view, automatically clearing alarms, manually clearing alarms, and displaying and analyzing alarms based on alarm correlations. In addition, the information about how to handle alarms can be recorded on the M2000 for sharing purposes.

Security Monitoring The M2000 provides security monitoring functions, which enable users to obtain the information about unauthorized activities or audit user operations in time. You can perform the following operations through the M2000: 

Querying and exporting users' NE operation logs



Monitoring online NE users and related user operations and forcing a user to exit

Configuration Data Query Users can query the configuration information about the devices on the entire network through the M2000. When an exception occurs on the network or when the network needs to Huawei Proprietary and Confidential IssueV2.1 (2011-06-30)



be adjusted, users can easily obtain the configuration information and then perform troubleshooting or adjust the configurations. 

To ensure that the configuration data is accurate and valid, the M2000 provides the functions of synchronizing configuration data automatically, manually, and on a scheduled basis in cases of configuration modification and network disconnection.



The M2000 enables users to query network configuration information in real time. The information serves as a basis for troubleshooting and configuration adjustment. In addition, the M2000 provides NE reports, CN resource reports, NE statistical reports, and RAN configuration reports.

Inventory Information Query The inventory management function enables users to manage the physical and logical asset information on the network in a centralized manner. Users can view, query, maintain, synchronize, import, or export the inventory information.

Troubleshooting The M2000 provides subscriber tracing function through GUIs and supports the centralized tracing management over the entire network. The FARS helps OM engineers to locate call-related faults and network faults, optimize the network coverage, and solve interconnection problems. This reduces the OM costs for telecom operators.

iSStar The M2000 provides a powerful script enhancement maintenance platform, HFC library function, and an easy-to-use High level Script Language (HSL).Users can create an HSL script for the repeated and effort-consuming routine maintenance and then use the iSStar to edit, debug, and run the HSL script. This automates routine maintenance, reduces the workload, and improves the work efficiency.

Bearer Network Management The M2000 provides the Ethernet OAM function, which improves the maintenance of the MAC layer on the Ethernet. According to the ETH OAM protocol defined by IEEE 802.1ag and IEEE 802.3ah, the M2000 provides the Ethernet OAM solution.

Signaling Link Management The functions of the STP signaling link management consist of automatically creating the signaling link topology and displaying signaling resource and status statistics. You can view the STP signaling network architecture, device status, device alarms, and link alarms in the signaling link topology. You can also filter and view the statistics about the signaling resources and status. Signaling link management enables OM personnel to monitor the STP nodes, destination signaling points, and signaling links in the signaling network in a centralized manner.




3.5 Network Adjustment Configuration Adjustment The M2000 provides the remote and centralized configuration adjustment function for network troubleshooting and network optimization. 

Through a GUI The M2000 provides the graphic configuration of CBSS function for users to adjust the configuration of the CBSS NEs. The M2000 provides the basic configuration function for all the CS NEs on the CN. Users can adjust configuration data on a GUI.



Through a command-line interface The M2000 provides a command-line interface, which enables users to issue MML commands to multiple NEs of the same type to adjust configuration data.

NE Data Backup and Restoration The M2000 provides the NE data backup and restoration function to ensure that NE data can be restored by using backup data when faults occur in NE devices.

3.6 Service Management CDMA Pool/SingleSDB/CSCF Pool Through the M2000, users can group CN NEs such as MSCes, HSSs/USCDBs, and CSCFs into resource pools for resource sharing and service balancing. This improves hardware resource usage. In addition, users can configure, monitor, and maintain the resource pools through the M2000 client.

Dual-Homing The dual-homing function provides a disaster recovery mechanism for the CN. It prevents network services from being interrupted when softswitches break down or an exception occurs. In this way, this function ensures uninterrupted communications. In addition, the M2000 provides a dual-homing topology view and the functions of synchronizing dual-homing configuration data and automatically checking data consistency. The purposes are to facilitate routine dual-homing maintenance.




4

Configuration

The M2000 system can be installed on different types of servers. Telecom operators can select appropriate servers according to the number of managed NEs. Table 4-1 describes the typical server configuration. The M2000 server supports the Solaris and SUSE Linux operating systems. It uses the Sybase or Oracle database. The M2000 client can be installed on a PC or connected to the M2000 system through the Citrix solution by using a web browser. Table 4-1 M2000 typical server configuration

Platform

Networking

Server Type

Operating System and Database

Sun

Single-server system

Sun Sparc Enterprise M4000 Server, or Sun Sparc Enterprise M5000 Server

Solaris and Sybase

ATAE blades

SUSE Linux and Oracle

HA system SLS system Remote HA system Emergency system ATAE

Cluster system

The Sun Netra240, Sun Fire V890, Sun Fire E4900, Sun T5220, HP RX2660, HP RX7640 servers are no longer delivered for installing M2000V200R011. If the customer is using these servers whose configurations include the items described in Table 4-2, M2000V200R011 can still be installed on these servers and can run properly. Table 4-3 lists the minimum configuration items of the M2000 client. Table 4-2 M2000 server minimum hardware requirements

Server Model

CPU

Memory

Hard Disk

Sun Netra240

2 x 1.5 GHz

8 GB

Local:2 x 146 GB

Sun Fire V890

2 x 1.8 GHz

8 GB

Local:6 x 146 GB, Diskarray:16 x 146 GB




Sun Fire E4900

4 x 1.8GHz

8 GB


Sun T5220

1 x 1.2 GHz/4 Core

8 GB

Local:4 x 146 GB

Sun M4000

2 x 2.4 GHz/8 Core

16 GB


Sun M5000

4 x 2.4 GHz/16 Core

32 GB


HP RX2660

2 x 1.4 GHZ/4 Core

8 GB

Local:4 x 146 GB

HP RX7640

2 x 1.6 GHZ/4 Core

16 GB


Table 4-3 M2000 client minimum requirements

Item

Configuration

CPU

E5300 or above

Memory

2 GB

Hard disk

160 GB

Accessories

DVDRW-Integrated Ethernet adapter-Integrated audio adapter-Built-in sound box-19'' LCD

Operating system

Windows XP professional (or a later version)

Application software

M2000 client application software

If the M2000 client is installed with the Windows 7 Professional operating system, Internet Explorer 8 32-bit must be used, if necessary.




5

Operation and Maintenance

5.1 Overview The M2000 provides a comprehensive system security solution, powerful data backup and restoration, and efficient OM functions, significantly improving OM efficiency.

5.2 OM Features Comprehensive System Security Solution 

The M2000 provides comprehensive security hardening solutions for operating systems and databases. These solutions meet the security requirements for operating systems and databases.



The M2000 provides an OSS antivirus solution to protect the M2000 system against attacks of viruses, worms, and spyware and to ensure the security of network OM data. By deploying the OfficeScan, this solution protects Windows-based M2000 clients, Citrix clients, and Citrix servers against viruses. By providing ServerProtect for Linux 3.0 and Control Manager, this solution protects SUSE Linux-based M2000 servers against viruses.



The M2000 provides rights management, access control, and user monitoring functions to ensure user security. The M2000 provides centralized OSS user management and single sign-on (SSO) to meet the requirements of centralized authentication for multiple OSS applications. The M2000 provides an LDAP-based centralized user management interface for telecom operators to manage user information on their own user account management platforms. The M2000 also provides an LDAP/RADIUS-based user authentication interface to enhance the security of M2000 user management.



The M2000 provides transmission encryption to enhance the security of data transmission between the M2000 client and server, between the M2000 server and NEs, and between theM2000 and the NMS.

Powerful Data Backup and Restore The M2000 allows users to set flexible backup policies, based on which users can back up M2000 applications and real-time data using periodical backup tasks. When the M2000 application real-time data is damaged or missing, users can restore the system quickly by using the corresponding backup package. In addition, the M2000 provides dedicated backup and restore tools, with which users can back up and restore the data of the entire operating system. Huawei Proprietary and Confidential IssueV2.1 (2011-06-30)



Comprehensive System Monitoring Users can monitor the status of all the M2000 services and the usage of the system resources on each server in real time. Users can set thresholds for system status. When the service is interrupted or the usage of system resources reaches a threshold, the system generates an alarm and quickly notifies users of the fault.

ATAE Cluster System Intelligent Management All the boards except for the OSMU involved in the Advanced Telecommunications Application Environment (ATAE) cluster system solution are not configured with any hard disk. The boards without hard disks use the SAN Boot technology and boot the operating system from the disk array. If a fault occurs on a board, the SAN Boot technology maps the boot volume of the faulty board onto the substitute board to quickly resume the services. OSMU intelligent hardware management includes: 

Running on a separate board, the OSMU provides centralized maintenance by enabling users to change IP addresses, time, routes, and user passwords in batches, and power on and power off the boards in batches. This improves the maintenance efficiency.



The OSMU provides a device panel, which enables users to view the device status in r eal time. The information about the board status displayed on the device panel in real time provides references for board maintenance operations. Error information is included in alarms and the alarms are automatically sent to the M2000 for uniform hardware alarm monitoring.



The OSMU provides the function of centralized task management, which enables users to query the system tasks in real time. By querying the system tasks before performing a major operation, users can learn the tasks being performed by the OSMU in advance to make a preliminary decision on the major operation.



The OSMU provides a built-in function of centralized backup. With this function, data on each service board is backed up to the backup media through the OSMU in a centralized manner. The backup media for centralized backup through the OSMU is disk array. In comparison with traditional backup mode, the centralized backup is faster, more efficient, and more cost-effective.



The OSMU provides the automatic deployment of the operating system and database software during the commissioning process.

Graphical System Maintenance In addition to command-based routine commissioning and maintenance, the M2000 provides the following web-based functions to reduce costs and improve OM efficiency: 

Querying basic server information



Upgrading M2000 server software



Installing mediations



Starting and stopping relevant components by radio access technology



Clearing data



Inspection



Collecting fault locating information



Managing northbound interfaces




Centralized Task Management Based on the centralized task management function, the M2000 performs routine maintenance tasks related to the system. System-scheduled tasks include database capacity management tasks, data export tasks, synchronization tasks, and M2000 backup tasks. User-scheduled tasks include NE license backup, network-wide NE backup, health check, MML script execution, iSStar script execution, software download, remote service upgrade verification, configuration report generation.




6

Technical Specifications

6.1 Overview This chapter describes the following system specifications: 

Management Capability



Reliability Specifications



Compliant Safety Standards



EMC Specifications



Environmental Requirements

6.2 Management Capability The management capability of the M2000 is calculated according to equivalent NEs, and the NMS server is configured according to the number of equivalent NEs. If the M2000 server hardware configurations are the same, the capability of managing NEs varies according to the versions of the operating system and database on the M2000 server. Table 6-1 describes the capability of the M2000. Sun servers are installed with the Solaris10 operating system and the Sybase15 database. If the PRS and the M2000 are deployed on one server, the NE management capability decreases by 30%. Table 6-1 NE management capability of the M2000 (except SLS system)

Hardware Platform

Management Capability (Number of Equivalent NEs)

2 CPU Sun M4000

≤ 100

4 CPU Sun M4000

≤ 190

4 CPU Sun M5000

≤ 190

6 CPU Sun M5000

≤ 270

8 CPU Sun M5000

≤ 340




The management capability of an SLS s ystem depends on the number of servers. Assume that the management capability of one single server is 1, the total management capability is the result of multiplying 1 by a coefficient if another server is added. This coefficient varies according to the number of added servers. Table 6-2 shows an example of the management capability of the full configuration M5000 server. Table 6-2 Estimation of the management capability on NEs in the Sun SLS system(M5000)

Number of Servers

Total Management Capability Coefficient

Single

1

2:1

1.6

3:1

2.3

4:1

3.6

5:1

4.8

6:1

6

The management capability of the ATAE cluster system depends on the number of blades in use. With the typical configuration, the ATAE cluster system can manage 400 equivalent NEs. The number of equivalent NEs is determined by the following factors: 

NE type



Performance measurement period



Performance measurement object



Performance measurement counter

The number of equivalent NEs for the same type of NEs varies according to performance measurement requirements of users. For details, see the table of calculating equivalent NEs in the iManager M2000 V200R011 Configuration Principles. Users can ask Huawei engineers to analyze and calculate the number of equivalent NEs for the measurement unavailable in the table.

6.3 Reliability Specifications The reliability of the M2000 system varies according to the server model and the hardware configuration. Table 6-3, Table 6-4 and Table 6-5 describe the specifications for configuring the Sun-based single-server system, HA system and SLS system. Table 6-6 describes the specifications for configuring the ATAE cluster server.




Table 6-3 Hardware reliability specifications (Sun-based single-server system)

Server Model

MTBF (Hour)

MTTR (Hour)

Annual Mean Failure Time (Hour)

Availability

2 CPU M4000

64776

3.4376545

0.464867472

0.999946933

4 CPU M4000

57110

3.372342

0.51724692

0.999940954

4 CPU M5000

49238

3.3053582

0.588021329

0.999932874

6 CPU M5000

40980

3.3493621

0.715910545

0.999918275

8 CPU M5000

31629

3.3989344

0.941271176

0.999892549

Table 6-4 Hardware reliability specifications (Sun-based HA system)

Server Model

MTBF (Hour)

MTTR (Hour)


Availability

2 CPU M4000

64776

0.61666667

0.083394291

0.99999048

4 CPU M4000

57110

0.68333333

0.104814015

0.999988035

4 CPU M5000

49238

0.71666667

0.127501292

0.999985445

6 CPU M5000

40980

0.81666667

0.174569484

0.999980072

8 CPU M5000

31629

0.96666667

0.267720801

0.999969438

Table 6-5 Hardware reliability specifications (Sun-based SLS system)

Server Model

MTBF (Hour)

MTTR (Hour)


Availability

2 CPU M4000

50993.76207

0.616666667

0.10593324

0.999987907

4 CPU M4000

38385.24089

0.683333333

0.15594258

0.999982198

4 CPU M5000

32572.64978

0.716666667

0.19273415

0.999977998

6 CPU M5000

26077.96584

0.816666667

0.27432262

0.999968685

8 CPU M5000

20382.88129

0.966666667

0.41542696

0.999952577

Table 6-6 Hardware reliability specifications (ATAE cluster system with typical M2000 configuration)

MTBF (Year)

MTBF (Hour)

MTTR (Hour)

Annual Mean Failure Time (Minute)

Availability

62.72

549482

3

2.87

0.9999945




6.4 Compliant Safety Standards The M2000 complies with the following safety standards: 

IEC 60950-1



IEC/EN41003



EN 60950-1



UL 60950-1



CSA C22.2 No 60950-1



AS/NZS 60950-1



BS EN 60950-1



IS 13252



GB4943

6.5 EMC Specifications The M2000 complies with the following Electromagnetic Compatibility (EMC) standards: 

CISPR22 Class A



EN55022 Class A



EN50024



ETSI EN 300 386 Serial Class A



ETSI EN 301 489 Class A



ICES 003 Class A



AS/NZS CISPR22 Class A



GB9254 Class A



VCCI Class A



CNS 13438 Class A

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

6.6.1 Storage Environment This section describes the climatic, waterproof, biological, air purity, and mechanical stress requirements for storing the equipment. Huawei Proprietary and Confidential IssueV2.1 (2011-06-30)



Climatic Requirements Table 6-7 lists the climatic requirements for equipment storage. Table 6-7 Climatic requirements for equipment storage

Item

Range

Temperature

-20°C (-4 ºF) to +60°C (140 ºF)

Relative humidity

8% to 93%

Altitude

 5,000 m (16,404 ft.)

Air pressure

70 kPa to 106 kPa

Solar radiation

 1,120 W/s²

Heat radiation

 600 W/s²

Wind speed

 30 m (98.42 ft.)/s

Waterproof Requirements The equipment must be stored in a room where: 

Water does not accumulate on the ground or fall on the package. Water sources such as a hydrant and air-conditioner are placed at a distance.

If the equipment is placed outdoors, ensure that: 

The package is intact.



Waterproof measures are taken to prevent water penetration.



Water does not accumulate on the ground or flow into the package.



The package is not exposed directly to sunlight.

Biological Requirements Ensure that the place for equipment storage is free of: 

Fungus or mildew



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-8.




Table 6-8 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

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-9. Table 6-9 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-10 lists the mechanical stress that the equipment can endure during storage. Table 6-10 Storage requirements regarding mechanical stress

Item

Subitem

Range

Sinusoidal vibration

Offset

 7.0 mm (0.28

None

in.) Accelerated speed

None

 20.0 m (65.62

ft.)/s²




Item

Unsteady impact

Subitem

Range

Frequency range

2 Hz to 9 Hz

Impact response spectrum II

 250 m (820.20 ft.)/s²

Static payload

 5 kPa

9 Hz to 200 Hz

NOTE

Impact response spectrum: refers to the maximum acceleration response curve generated by the equipment under specified excitation. Impact response spectrum II means that the duration of semi-sine impact response spectrum is 6 microseconds. 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.6.2 Transportation Environment This section describes the climatic, waterproof, biological, air purity, and mechanical stress requirements for transporting the equipment.

Climatic Requirements Table 6-11 lists the climatic requirements for transporting the equipment. Table 6-11 Climatic requirements for transporting the equipment

Item

Range

Altitude

 5,000 m (16,404 ft.)

Air pressure

70 kPa to 106 kPa

Temperature

-20 °C (-4 ºF) to 60 °C (140 ºF)

Humidity

8% to 93%

Solar radiation

 1,120 W/s²

Heat radiation

 600 W/s²

Wind speed

 30 m (98.42 ft.)/s

Waterproof Requirements Before transporting the equipment, ensure that: 

The package is intact.



Waterproof measures are taken to prevent water penetration.



There is no water in the vehicle.




Biological Requirements Ensure that the vehicle is free of: 

Fungus or mildew



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-12. Table 6-12 Requirements for physically active materials in the transportation environment


Unit

Density

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

The density of chemically active materials must comply with the requirements listed in Table 6-13. Table 6-13 Requirements for physically active materials in the transportation environment


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-14 lists the mechanical stress that the equipment can endure during transportation. Table 6-14 Transportation requirements regarding mechanical stress

Item

Subitem

Range


Offset

 7.5 mm (0.30

Unsteady impact

--

 20.0 m (65.62

 40.0 m (131.23

ft.)/s²

ft.)/s²

in.) Accelerated speed

Random vibration

N/A

N/A

Frequency range

2 Hz to 9 Hz

9 Hz to 200 Hz

200 Hz to 500 Hz

Spectrum density of accelerated speed

10 m²/s³

3 m²/s³

1 m²/s³

Frequency range

2 Hz to 9 Hz

9 Hz to 200 Hz

200 Hz to 500 Hz


 300 m (984.24 ft.)/s²

Static payload

 10 kPa

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 microseconds. 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.6.3 Operating Environment This section describes the climatic, waterproof, biological, air purity, and mechanical stress requirements for operating the equipment.

Climatic Requirements Table 6-15 and Table 6-16 list the climatic requirements for operating the equipment. Table 6-15 Temperature and humidity requirements for operating the M2000

Temperature

Relative Humidity

5°C (41 ºF) to 35°C (95 ºF)

20% to 80%

NOTE

The values are measured 1.5 meters above the floor and 0.4 meters 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 operation of not more than 15 days accumulated in a year.




Table 6-16 Other climatic requirements for the operation of the M2000

Item

Range

Altitude

 4,000 m (13,123.20 ft.)

Air pressure

70 kPa to 106 kPa

Solar radiation

 700 W/m²

Heat radiation

 600 W/m²

Wind speed

 1 m (3.28 ft.)/s

Biological Requirements Ensure that the place for storing the equipment is free of: 

Fungus or mildew



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-17. Table 6-17 Operation requirements for physically active materials


Unit

Density

Dust particles

Particles/m³

 3 x 10

4

(Ensure that the dust accumulated for three days on the desktop is not visible.) NOTE

Dust particles: diameter  5 m

The density of chemically active materials must comply with the requirements listed in Table 6-18. Table 6-18 Operation requirements for chemically active materials


Unit

Density

SO2

mg/m³

 0.20

H2S

mg/m³

 0.006

NH3

mg/m³

 0.05





Unit

Density

Cl2

mg/m³

 0.01

Mechanical Stress Requirements Table 6-19 lists the mechanical stress that the equipment can endure during its operation. Table 6-19 Operation requirements regarding mechanical stress

Item

Subitem

Range


Offset

 3.5 mm (0.14 in.)

N/A

Accelerated speed

N/A

 10.0 m (32.81

ft.)/s²

Unsteady impact

Frequency range

2 Hz to 9 Hz


 100 m (328.08 ft.)/s²

Static payload

0

9 Hz to 200 Hz

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.



iManager M2000 V200R011 Product IMS V2.1(20110630)

Recommend Documents