IManager M2000 V200R012 Basic Feature Description

iManager M2000 V200R012

Basic Feature Description

Issue 03

Date 2012-07-30

HUAWEI TECHNOLOGIES CO., LTD.

Issue 03 (2012-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

i

Copyright Huawei Technologies Co., Ltd. 2012. 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 contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in 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 a 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: [email protected]

iManager M2000 V200R012 Basic Feature Description


ii

Contents

1 Overview ......................................................................................................................................... 1

2 Basic Features (WOFD-100000) ................................................................................................... 5

2.1 Platform ............................................................................................................................................................ 5 2.2 Fault Management .......................................................................................................................................... 23 2.3 Configuration Management ............................................................................................................................ 39 2.4 CME ............................................................................................................................................................... 51 2.5 Performance Management .............................................................................................................................. 83 2.6 Security Management ..................................................................................................................................... 90 2.7 Topology Management ................................................................................................................................. 104 2.8 NE License Management ............................................................................................................................. 107 2.9 Hardware and Software Management .......................................................................................................... 111 2.10 Network Monitoring and Analysis ............................................................................................................. 116 2.11 FARS .......................................................................................................................................................... 127 2.12 Base Station Commissioning Management ................................................................................................ 141 2.13 SingleRAN Management ........................................................................................................................... 149 2.14 Network Planning and Optimization .......................................................................................................... 157 2.15 Wireless Auxiliary Networking Devices .................................................................................................... 161

3 Acronyms and Abbreviations ................................................................................................. 163



1

1 Overview This document describes the basic features provided by Huawei M2000 V200R012. This document helps users understand the M2000 features.

The network elements (NEs) in this document refer to the network devices managed by the M2000. The M2000 manages Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications (GSM), SingleRAN, Long Term Evolution (LTE), information management system (IMS), and UMTS Broadband (uBro) NEs, transmission devices, IP devices, and other devices such as domain name servers (DNSs) and Dynamic Host Configuration Protocol (DHCP) servers. Unless otherwise specified, all the devices described in this document are Huawei products.

By default, SingleRAN is managed by one M2000 system.

The solutions used with M2000 V200R012 include GBSS14.0, RAN14.0, eRAN3.0, SingleRAN7.0, CS9.2, PS9.1, SingleSDB3.3, IMS9.0, NGN10.6, and signaling transfer point (STP). The new and enhanced features in M2000 V200R012 are available only when M2000 V200R012 works with a corresponding solution.

The M2000 manages the following WRAN NEs:

Base station: NodeBV1, including the base station types of BTS3812, BTS3806, BTS3806A, BTS3812E, BTS3812AE, BTS3812A, and DBS3800

Base station: NodeBV2, including the base station types of DBS3900 WCDMA, BTS3900 WCDMA, BTS3900A WCDMA, BTS3900L WCDMA, and BTS3900AL WCDMA

Micro base station: BTS3902E WCDMA Radio network controller: BSC6800 Multimode base station controller: BSC6900 UMTS Clock server: IP Clock Server

The M2000 manages the following GBSS NEs:

Base station controller: BSC6000 (GSM-R) Multimode base station controller: BSC6900 GSM Base station: GBTS (GSM BTSs except BTS3900B and BTS3900E) Pico BTS: BTS3900B Compact BTS: BTS3900E Clock server: IP Clock Server



2

The M2000 manages the following core network (CN) NEs: Serving GPRS support node: SGSN Gateway GPRS support node: GGSN Report server: SUR Mobile switching center server: MSC Server Home location register: HLR9820 Home location register (service node): HLR-FE Media gateway: MGW Fixed-mobile convergence media gateway: FMC MGW Charging gateway: CG Signaling gateway: SG7000 Interworking function: IWF Enhanced name server: ENS Unified number portability: UNP Unified identity management: UIM Unified equipment identity register: UEIR Unified Subscriber Center Database: USCDB Visual IP Security immunity gateway: SIG Embedded Edge Router: EER SigProbe SigProbeTDM

The M2000 manages the following SingleRAN NEs:

Multimode base station controller (GU mode): BSC6900 GU Multimode base station: MBTS(GU), MBTS(GL), MBTS(UL), MBTS(GUL), and

MBTS(WL) The M2000 manages the following uBro NEs:

Access point: AP (The AP Manager forwards AP alarm and performance data to the M2000.)

Operations support system (OSS) of AP: AP Manager AP wireless gateway: AG AP home register: AHR Authentication, Authorization and Accounting: AAA Clock server: IP Clock Server Security gateway: IPSec GW, including Eudemon1000E, and Eudemon8000E

(Eudemon8080E) The M2000 manages the following eRAN NEs:

Base station: eNodeB, including DBS3900 LTE, BTS3900 LTE, BTS3900A LTE, BTS3900L LTE, and BTS3900AL LTE

Micro base station: BTS3202E Universal switching unit: USU



3

Wireless backhaul system: eRelay, including eRelay BS and eRelay Remote Node (RRN) Clock server: IP Clock Server

The M2000 manages the following evolved packet core (EPC) NEs: Home subscriber server: SAE-HSS Unified service node: USN Unified gateway: UGW Charging gateway: CG Unified policy and charging controller: UPCC Signaling service processing system: SPSV3

The M2000 manages the following IMS NEs:

Media gateway: MGW Session border controller: SBC (SE2300, SE2600) Home subscriber server: HSS (HSS9820) Call 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) Multimedia resource function processor: MRFP (MRP6600) Unified Subscriber Center Database: USCDB Attachment information management system: AIM (AIM6300) Service provisioning gateway: SPG (SPG2800) Unified gateway controller: UGC (UGC3200) E.164 number: ENUM Convergent Application Server: CAS9910 Presence server, Group server, Messaging server: PGM Enhanced name server: ENS Multipoint control unit: ViewPoint Open service gateway: OSG Access gateway control function: AGCF (UAC3000) Rich Communication Suite: RCS (RCS9100) Terminal management system: TMS9950 Network recording&playback server: MediaX3600NRS (NRS2000) The M2000 manages the following signaling transfer point (STP) NEs: Convergent Application Server: CAS9910 Signaling service processing system: SPS Signaling gateway: SG7000 The M2000 manages the following next generation network (NGN) NEs: Softswitch system: SoftX3000 Media gateway: MGW



4

Signaling gateway: SG7000 Signaling service processing system: SPS Media switch server: MediaX3600 Session border controller: SE2300/SE2600 Media resource server: MRS6100 iGateWay Bill: iGWB Signaling transfer point: STP Smart home location register: SHLR (SHLR9200) Convergent Application Server: CAS9910

The M2000 manages the following wireless transmission devices:

Optical transmission devices: Metro1000V3 and OSN3500 Microwave transmission devices: RTN620, RTN605, RTN910, RTN950, and RTN980 Building integrated timing supply system: BITS

The M2000 manages the following IP devices:

S series switches: S9300: S9303, S9306, and S9312 S8500: S8505, S8512 S5624P: S5624P and S5624 S5000: S5000 S3900: S3928P-EI S3500: S3526C-24[12FS], S3526C-24[12FM], S3526C, S3552G, S3552P, S3528G, S3528P, S3538G, and S3528P-EA S5300: S5328TP-EI-24S, S5328TP-EI/SI, S5328C-EI-24S, S5328C-EI, S5352C-EI, S5352TP-EI-48S S3300: S3328TP-EI, S3328TP-SI, S3328TP-EI-24S, S3352P-SI, S3352P-EI-24S, S3352P-EI-48S

NE08 series routers NE08: NE08 and NE08E NE16: NE16 and NE16E NE20: NE20E NE40: NE40-2, NE40-4, NE40-8, and NE40-E NE80: NE80

AR46 series routers AR4640

Eudemon series firewalls Eudemon200, Eudemon300, Eudemon500, Eudemon1000, and Eudemon8000

Other devices that can be managed by the M2000 are as follows:

DNS (including third-party DNSs) DHCP server (including third-party DHCP servers) NE bearing server: servers that bear the SG7000, MSC Server, and iGWB Wi-Fi device: Skyway Excel XL5810, which is from a third-party system



5

2 Basic Features (WOFD-100000) 2.1 Platform

WOFD-000100 Basic M2000 Service

Availability

This feature was introduced in M2000 V200R003.

Summary

This feature provides hardware and software platforms and basic functions required for the proper operation of the M2000. Basic functions include system operating-status monitoring, online help, and remote maintenance.

Benefits

The M2000 centrally manages WCDMA, GSM, LTE, and SingleRAN networks. Based on common software and hardware platforms, the M2000 provides various network management application services such as alarm, performance, security, and configuration management. These functions improve the M2000's working efficiency, reduce operation and maintenance (O&M) costs, and therefore minimize telecom operators' investments.

Description

This feature provides the following functions:

Hardware and software platforms For details about the hardware and software platforms, see iManager M2000 V200R012 Product Description.

M2000 software integrity check This function ensures the accuracy and integrity of the M2000 software when it is being installed on the live network. When releasing an M2000 software version, the M2000 uses a digital certificate to sign the software version. Before installing or upgrading the M2000 software, the M2000 verifies the digital certificate of the software. If the digital certificate passes the verification, the M2000 proceeds with the installation or upgrade. Otherwise, the M2000 provides information about the verification failure.



6

Online help The M2000 provides online help information that supports functions such as hotspot help, full-text search, and offline browse. Online help includes the following items: Description of M2000 functions such as fault, configuration, performance, security,

and topology management, and how to implement these functions Description of valid value ranges for MML command parameters Details about configuration parameters, alarms, and performance counters Users can switch to Help information about the MML commands, alarms, performance counters, and configuration objects and parameters from the command-line interface (CLI), alarm, performance, and configuration management windows. Users can create, edit, and delete, and manage remarks on any Help page. Remarks management functions include querying, importing, and exporting.

M2000 status monitoring This function monitors the M2000, database, and hardware status, and performance counters in real time. System status information that can be monitored includes the server, service and

process status, database and disk partition space, and component information. The M2000 allows users to set thresholds for system status. If a counter value exceeds the user-specified threshold, the M2000 generates an alarm. If the counter value returns to the valid range, the M2000 clears the alarm.

The parts of the system that can be monitored include disks, CPUs, memory, disk arrays, power supplies, fans, network ports, and environments. When a fault occurs on the hardware, the system generates an alarm. This function does not apply to the ATAE cluster solution.

After being started, the M2000 automatically collects its own performance statistics, including the average and peak usage of the server processor, server memory, server partitions, and database space. The M2000 allows users to query the M2000 performance statistics based on time ranges.

M2000 license management The M2000 license defines the M2000's management capability on the network. The M2000 provides specific network resource management capacity and optional features under license control. The M2000 license control items consist of function control items and resource control items. Users can view the function authorization information, update the license file, and export license information to a CSV or XLS file. Function control items: authorized optional M2000 features controlled on the basis of

functions. Resource control items: authorized M2000 features that are controlled by the number

of resources, manageable resource capacities, and number of used resources of these features. The M2000 generates an alarm if the number of network resources managed by a resource control item exceeds the number specified by the license. Users can manually clear this alarm.

Invalidating a license The M2000 allows users to invalidate a license on the client and generates an invalid code. According to the invalid code, Huawei technical support personnel apply for a new license. This significantly improves the efficiency of updating licenses in cases such as expansion, incremental sales, electronic serial number (ESN) replacement, and version upgrade.

Concurrent M2000 clients



7

The M2000 supports multiple concurrent clients. The number of concurrent clients that the M2000 can manage depends on the hardware configuration of the M2000 server. An M2000 single-server system supports up to 100 concurrent clients, and a multi-server load-sharing (SLS) system supports up to 120 concurrent clients.

Remote maintenance Users can connect the M2000 client to the M2000 server for remote maintenance through dial-up or a virtual private network (VPN). Remote maintenance through dial-up requires a dial-up server. Remote maintenance through a VPN requires a VPN gateway.

Web-based installation and automatic upgrade of the M2000 client Users can install the M2000 client locally or remotely through a web browser. In the case of remote web-based installation, users can log in to the M2000 server through a web browser and install the M2000 client. The M2000 supports automatic upgrades of the M2000 client. If the version of the M2000 client is inconsistent with the server version when users log in, the M2000 automatically updates the client software to the matching version according to the user confirmation. This improves the efficiency in changing client versions and reduces maintenance costs.

Dynamic adaption of new NE version The M2000 provides the mediation solution to match multiple NE versions. Therefore, to manage a new NE version, users only need to install the mediation of the NE without upgrading the M2000. During the mediation installation, the M2000 can provide network management services properly. The installation of mediation does not affect the online users who do not require the mediation version. Users who require the new mediation need log in to the client again to use the latest mediation version. In scenarios such as initial site deployment and network upgrade, multiple mediations need to be loaded at a time. The M2000 can load NE mediations in batches, reducing the loading time and improving efficiency.

Online user monitoring The M2000 monitors the session status and operations performed by all M2000 users. The user-session monitoring can display information such as user name, maintenance terminal IP address, user type, session start time, and user group. The user-operation monitoring can display information such as user name, maintenance terminal IP address, security operation, operation object, risk level, and execution result. With this function, administrators can force a specified user to log out.

Workbench management The M2000 provides a workbench for function and application shortcuts. Users can create function and application shortcuts on the workbench, which simplifies operations and improves operation efficiency. Users can also customize the names, description, and icons of workbench shortcuts. The M2000 provides default workbench shortcuts to certain functions such as centralized MML CLI, centralized task management, system monitoring, and topology management.

Southbound and northbound subnet separation To enhance network security, the M2000 now separates southbound and northbound interfaces by configuring IP addresses belonging to different subnets. This ensures that these interfaces are deployed in different subnets. The southbound subnet connects NEs and the M2000 and the northbound subnet connects the M2000 client and a third-party system.



8

Enhancement

The following function is added to M2000 V200R012C00:

Southbound and northbound subnet separation: This solution is supported by Sun-platform-based single-server, local HA, remote HA, SLS, and emergency systems.

The following functions are added to M2000 V200R011C00:

Monitoring M2000 hardware based on HP platform Dynamically loading NE mediations in batches Running M2000 clients on the Windows 7 operating system Verifying M2000 software integrity

The following functions are added to M2000 V200R010:

Associating alarm, performance, and configuration management and centralized command configuration functions with related Help information: Only the NodeB, BSC6900 GU, BSC6900 GSM, and BSC6900 UMTS support the function of associating performance counters with related Help information.

Creating and managing remarks in a Help window Invalidating licenses Monitoring the operating status of the Sybase database


Verifying M2000 services after the M2000 is upgraded Supporting Windows Vista and XP operating systems Managing functions and applications using a workspace Updating M2000 license files on the client


Collecting M2000 performance statistics Installing and automatically upgrading M2000 clients on a web browser Loading M2000 mediation versions online Supporting HP and ATAE platforms

WOFD-000200 File Transfer Management

Availability


Summary

The M2000 supports file transfer between the M2000 server and the M2000 client, between the M2000 and NEs, and between the M2000 and a third-party system by using File Transfer Protocol (FTP). To ensure data transmission security, the M2000 supports FTPS- and SFTP-based file transfer. For details, see the optional feature WOFD-210100 Encrypted Transmission.



9

Benefits

This feature ensures the effective transfer of files between the M2000 server and the M2000 client, between the M2000 and NEs, and between the M2000 and a third-party system.

Description

FTP is a standard protocol, which specifies that file transfer between network nodes can be implemented by setting up control channels and data transfer channels. Complying with the RFC 959 FTP standard protocol, the M2000 supports file transfer and management. It transfers files between the M2000 server and the M2000 client, between the M2000 and NEs, and between the M2000 and a third-party system. The data to be transferred is as follows:

Performance data, log, and configuration data files collected from NEs or sent to a third-party system by the M2000

NE version, configuration data, and patch files downloaded from the M2000 by NEs License and NE version files transferred between the M2000 client and server

According to the application scenarios, the M2000 can function as an FTP server or client. For example, when transferring files to a third-party system, the M2000 can be either an FTP server or client based on user requirements. When upgrading NEs, users need to upload the software version from the M2000 client to the M2000 server. In such a case, the M2000 server functions as an FTP server, while the M2000 client functions as an FTP client.

The M2000 manages parameters related to file transfer. For example, it allows users to set file transfer between NEs and the M2000 server and between the M2000 client and server, disable plaintext transfer, and set a relay server and a third-party FTP server.

Generally, FTP and File Transfer Protocol over SSL (FTPS) use default service ports, which may cause security risks. To improve system security, the M2000 allows users to customize FTP and FTPS service ports.

Enhancement

The function of customizing FTP and FTPS service ports is added to M2000 V200R012C00.

Dependency

None

WOFD-000300 Application Management Platform

Availability


Summary

The application management platform supports centralized management of iSStar script applications and other applications. The iSStar is an enhanced script development platform provided by the M2000. With the application management platform, the M2000 manages application shortcuts by category and manages iSStar script applications.



10

The iSStar script applications are classified into local script applications and remote script applications. Local script application files are stored and executed on the M2000 client. Remote script application files are stored and executed on the M2000 server.

Benefits

This feature brings about the following benefits:

Using this feature, users do not need to pay attention to the implementation of the iSStar script. After the script is released, users can run it and obtain the execution results through the shortcut on the application management platform.

The application management platform can also manage other applications to implement the uniform management of scripts and other applications.

Description

The application management platform is used to manage the iSStar and other applications. This feature allows users to categorize application shortcuts and manage the remote iSStar applications, including management for workspaces, application shortcuts, remote applications, and iSStar tasks.

Workspace management A workspace is a management platform for categorizing application shortcuts. The applications of the same category can be managed by one workspace. Users can categorize applications based on their preferences and manage these applications on different workspaces. Users can create or delete workspaces and change the workspace names.

Remote application management The application management platform allows users to manage remote iSStar script applications, such as viewing, issuing, downloading, and deleting the applications.

Management of application shortcuts Users can create, delete, and copy shortcuts. They can also modify the attributes of the shortcuts. In addition, users can create shortcuts to both local and remote iSStar script applications. When using the shortcuts of iSStar script applications, users can select multiple NEs at a time to create script tasks in batches.

Task management The M2000 provides a GUI for managing local and remote iSStar script tasks, including tasks started through application shortcuts or through the iSStar development platform. Users can check task information such as script file path and name, NE, progress, start time, end time, status, task creator, and IP address of the client where a local task is executed. Users can also create, copy, start, suspend, or resume a task, delete tasks in batches, and check task execution results.

WOFD-000700 ATAE Cluster Solution

Availability


Summary

The advanced telecommunications application environment (ATAE) cluster solution is an integrated OSS solution developed on the Huawei ATAE platform.



11

The characteristics of the ATAE cluster solution are as follows:

Highly professional Highly integrated Carrier-class reliability High performance Enables smooth expansion through board insertion

In addition, the ATAE cluster solution centrally implements the following functions:

Managing large-scale networks Monitoring and maintaining hardware Holding multiple OSS products such as the M2000 (including the Trace Server), PRS, and

Nastar (including the eSAU, which is short for evolved service aware unit) These features of the ATAE cluster solution help telecom operators minimize energy consumption, save equipment room space, reduce overall deployment costs, and improve competitiveness.

The Trace Server is a dedicated server provided by the M2000 for LTE tracing services. This server stores LTE UE and cell tracing data. The eSAU is a server provided by the Nastar for preprocessing data reported from NEs, such as measurement reports (MRs).

Benefits


An ATAE subrack contains 14 boards, where 12 boards function as servers and 2 boards function as switching boards. Compared with traditional servers that provide equivalent management capability, the ATAE cluster solution reduces energy consumption by over 60%, saves equipment room space by 50%, and reduces the number of cables for connecting servers.

The ATAE cluster solution helps improve O&M efficiency and minimize O&M costs because it can centrally manage large-scale networks. For example, a single ATAE cabinet can hold an M2000 system, the PRS, and the Nastar at the same time.

The ATAE cluster solution provides carrier-class reliability and ensures that services run smoothly all the time. In an ATAE cabinet, the key function modules such as subrack power supply units, fans, subrack management units, and switching units adopt the redundancy design, which provides carrier-class high reliability for telecom operators. The ATAE cluster solution adopts the N:1 redundancy solution, which improves hardware usage.

ATAE cluster solution supports board plug-and-play by using the SAN boot technology to re-load software automatically. Therefore, services can be quickly restored when a fault occurs.

The ATAE cluster solution provides the OSS self-maintenance unit (OSMU), which helps telecom operators improve O&M efficiency.

Description

This feature is described as follows:

Hardware configuration



12

An ATAE cabinet consists of 1 or 2 subracks, which can hold the M2000, PRS, and Nastar concurrently. The ATAE cluster solution provides flexible integrated deployment solutions for different network scales and scenarios. For example, integrated deployment of the M2000 and Trace Server for the LTE network and integrated deployment of the M2000, PRS, and Nastar for GSM and UMTS networks.

Carrier-class reliability Software redundancy: The boards in the ATAE cluster solution are classified into

server, switching, and DB boards. Server and DB boards support N:1 redundancy. The server boards implement different functions by loading corresponding software. One OSS product can be deployed on multiple server boards, and the boards are grouped into a cluster that adopts N:1 redundancy. DB boards implement data storage by loading corresponding database software. The DB board architectures for all OSS products are similar. Therefore, these DB boards share only one standby board.

Hardware redundancy: The key function modules in an ATAE subrack adopt the redundancy design. When the active module is faulty, services are immediately switched over to the standby module. a. The power supply units, subrack management units, switching units, and fans of

the ATAE subrack adopt the redundancy design. b. The service bus of the ATAE subrack adopts dual-star redundancy. c. The service plane and the management plane are deployed on different boards. In

this manner, the impact on services is minimized. d. The main storage system adopts the RAID 1+0 and backup storage system adopts

RAID 5 to protect data. e. The controllers and power supply units in the storage system adopt the redundancy

design. Smooth expansion

In the ATAE cluster solution, services are classified into different types and are deployed on corresponding boards. Therefore, users can smoothly expand the system capacity by inserting boards.

The ATAE cluster solution adopts the storage area network (SAN) architecture, which allows for the smooth expansion of storage devices. For example, users can expand storage capacity by adding disk arrays or a storage cabinet.

Board plug-and-play In the ATAE cluster solution, only the OSMU is configured with hard disks, and other boards adopt the SAN Boot technology. With the SAN Boot technology, users can start the operating system from the disk arrays. When a board is faulty, the boot volume is mapped on a new board that replaces the faulty one. Therefore, the SAN Boot technology helps quickly rectify faults.

OSMU The OSMU is the O&M unit of the ATAE cluster solution. It provides centralized maintenance and management for the ATAE cluster system. The OSMU is deployed on an independent board, supporting functions such as device, software, and service management, OSMU maintenance, and data backup. The device management function supports one-click installation and configuration of

the operating system, database, and Veritas Cluster Server (VCS). This function allows users to monitor and maintain hardware devices such as cabinets, subracks, boards, and disk arrays. It also allows users to view device information and status in real time, and perform operations on boards such as powering on and off the boards, resetting the boards, and changing their IP addresses.



13

The OSMU provides a device panel, which displays hardware configuration and status in graphics and provides command portals for querying hardware status and maintaining boards. On the device panel, users can query basic information about subracks, power entry modules (PEMs), self management modules (SMMs), and boards, health events, and sensor information. They can also maintain boards with functions such as powering on and off, resetting, and switching over the boards.

The software management function allows users to centrally manage various software packages, including the VCS, operating system, database, and application packages. It also allows users to install antivirus software and applications of the M2000, PRS, and Nastar, upgrade M2000 applications, and manage the VCS software license.

The service management function allows users to start and stop board and system services, and query cluster resource status and OSS product versions. It also provides product-specific functions for OSSs, such as northbound interface commissioning, mediation installation, and fault information collection for the M2000, and a management tool for the PRS.

System maintenance includes time and route management, operating system and database password management, and device preventive maintenance.

The OSMU centrally backs up the operating system, database, OSMU, and OSS applications from server boards to disk arrays, and restores the system using backup data. Each OSS product backs up its service data in the database and dumps the data to the OSMU. The data is restored on the OSMU.

OSMU maintenance supports self-management functions, such as monitoring hardware, signing and verifying software, and managing logs. The hardware components that can be monitored are boards, subracks, power supplies, and fans. After detecting a hardware fault, the OSMU automatically generates an alarm and reports it to the M2000 for centralized monitoring. When the OSMU fails to communicate with the M2000, the M2000 detects that the fault occurred on the OSMU and generates an alarm.

The OSMU centrally manages system tasks created by management modules. Users can perform or delete the tasks and view task information in real time, such as the execution type, status, progress, and start and end time.

Enhancement


Installing antivirus software and updating virus definitions for all boards through the OSMU

Querying hardware status on the device panel Deploying the eSAU (a module of the Nastar) with the M2000 Detecting OSMU faults


Centrally deploying the M2000 (including the Trace Server), PRS, and Nastar in a cabinet configured with two subracks

Performing OS hardening for the OSMU and OSSs Enhancing OSMU maintenance, including monitoring hardware, signing and verifying

software, and recording and managing logs Acting as an intermediate NTP server to obtain reference time from the upper-level clock

source and providing clock synchronization signals for the M2000 and the PRS Upgrading the PRS software through the OSMU



14

Dependency

The ATAE cluster solution of the current version does not support or does not involve the following features:

WOFD-000600 Database Hardening WOFD-130100 Local HA System WOFD-530200 Remote HA System WOFD-530100 Server Load Sharing WOFD-210700 Emergency System for Single-Server and Local HA System WOFD-210800 Emergency System for SLS System WOFD-500100 Veritas System Backup and Restore Solution WOFD-040900 Single Sign On

WOFD-070100 Local Maintenance Agent

Availability


Description

The M2000 provides communication agents for local maintenance terminals (LMTs) to maintain NEs. When an NE and its LMT are located on different network segments, the LMT can connect to the NE through the agent provided by the M2000 to maintain the NE.

Along with the development and spread of the web LMT, M2000 can also be a communication proxy for the web LMT.

LMTs can still set up connections to NEs through SSL or HTTPs to ensure transmission security when using the M2000 as an agent.

WOFD-070800 Supporting Network Time Synchronization

Availability


Summary

The M2000 supports the NTP/SNTP network time synchronization protocols so that it can synchronize time with the time server of a third-party system and provide synchronization time sources for NEs. This ensures that the time between the M2000 and the NEs is synchronized.

In addition, according to the security policy of the telecom operator, the M2000 uses MD5 encrypted algorithm defined in the NTP V3 in time synchronization.

Benefits

This feature ensures that the time of NEs on the entire network is synchronized. In addition, it supports adopting the encrypted authentication to enhance the security of network time synchronization.



15

Description

If the NTP server provided by a telecom operator network cannot communicate with the mobile communication devices managed by the M2000, the M2000 server can function as an intermediate NTP server. The M2000 server obtains the reference time from the NTP server provided by the telecom operator and sends time synchronization signals to NEs to ensure the consistency between the time of all NEs and the time of the time source. The M2000 monitors the operating status of the NTP service in real time and generates an alarm after detecting any exceptions in the NTP service or a synchronization failure with the upper-level time source.

The NTP protocol supports two authentication modes: unauthenticated and encrypted authentication. Telecom operators can determine the authentication mode according to security requirements. If the upper-layer NTP server provided by the telecom operator uses the encrypted authentication mode, the M2000 server can function as the NTP client to synchronize time with the upper-layer NTP server.

This feature requires telecom operators to provide a top-level clock source server. If telecom operators require a top-level clock source server from Huawei, they need to purchase Huawei entire-network time synchronization solution. For details about the solution, see the feature WOFD-540100 Network Time Synchronization Solution.

Enhancement


The M2000 generates an alarm after detecting any exceptions in the NTP service or a synchronization failure with the upper-level time source.

The M2000 functions as an intermediate NTP server in an SLS system, Sun-based local and remote HA systems, HP-based single-server and local HA systems, and ATAE-based single-server and local HA systems.

The following function is added to M2000 V200R009:

The M2000 supports encrypted authentication of the NTP.

Dependency

None

WOFD-070900 Daylight Saving Time and Management of Multiple Time Zones

Availability


Description

For some countries that use the daylight saving time (DST), there are two time switchovers every year. Some countries cross multiple time zones. Therefore, the time of NEs in different time zones must be different.

This feature ensures that the M2000 adapts to DST shifts on NEs and allows users to set time zone information. For example, users can choose whether to display server time or local NE time in the alarm browse window. If the area where an NE is located is using DST, the M2000 displays DST in MML messages.



16

WOFD-071200 Centralized Task Manager

Availability


Description

Centralized task manager is a task management mechanism of the M2000. It manages and controls all the scheduled tasks in the M2000 system through a centralized task management window.

The tasks managed centrally are classified into system-scheduled tasks and user-scheduled tasks. There are two types of tasks: one-time tasks and periodic tasks. Users can create user-scheduled tasks and select one-time tasks or periodic tasks as required. All system-scheduled tasks are periodic tasks and cannot be created by users.

Users can view information about all tasks on the task list provided by the M2000. The task information includes task name, execution period, type, creator, status, execution progress, execution result, and last execution time. Users can also perform specific operations on the tasks, such as start, delete, suspend, copy, or resume the tasks. In addition, users can modify task parameters.

System-scheduled tasks are as follows:

Database capacity management Data export Synchronization M2000 data backup

The limitations on the operations of system tasks are as follows:

Only users in the administrator group can manage and view system-scheduled tasks. System-scheduled tasks cannot be copied or deleted, and only some parameters can be

modified. Data capacity tasks in system-scheduled tasks cannot be suspended or resumed. Data

export tasks, synchronization tasks, and backup tasks can be suspended and resumed. Users can set the time to suspend and resume tasks.

User-scheduled tasks are as follows:

NE license backup NE backup BSC and RNC license activation Distribution of NodeB licenses MML script execution iSStar script execution Software download Verification after upgrade Generation of configuration reports Single antenna interference cancellation (SAIC) terminal capability sharing Configuration data synchronization on the CME



17

Data consistency check on the CME Export of data from the current data area on the CME

Enhancement

SAIC terminal capability sharing for GSM is added to M2000 V200R012C00.

Dependency

None

WOFD-071300 Script Trigger

Availability


Description

This feature supports two triggering modes, customizing menus to trigger scripts and automatic triggering.

Customizing menus to trigger scripts: This function allows users to customize the menus for script triggering. Users can add, delete, modify, or query user-defined menus. When adding a user-defined menu, users can select the script and set script execution parameters. The user-defined menus are used to trigger scripts stored on the M2000 client.

Automatic triggering: The M2000 allows users to set script triggering conditions and specify the scripts. Triggering conditions include validity time range, script type, execution period, and alarm ID. The M2000 automatically checks whether script triggering conditions are met. If the conditions are met, the corresponding script is automatically triggered.

The automatically triggered scripts are scripts stored on the M2000 server. Currently, HSL scripts and the following Shell scripts can be automatically triggered:

Bourne Again shell Bourne shell C shell Z shell Korn shell TC shell

Enhancement

The following function is added to M2000 V200R008:

This feature can be used for triggering the HSL script.

WOFD-071400 Auto IP Address Allocation Service for BTS

Availability




18

Description

The M2000 automatically assigns IP addresses to BTSs through the DHCP protocol. The M2000 extends the DHCP protocol based on the standard protocol to support the required functions, and automatically assigns IP addresses to Huawei base stations on IP networks based on the extended DHCP protocol. The DHCP Server service provides the following functions:

The M2000 extends protocols based on the DHCP protocol and assigns IP addresses based on specific configuration information such as the BTS name, BTS ID, IP address, and electronic serial number (ESN).

The M2000 allows users to add, delete, or modify the binding relationships between specific NE configuration information and IP addresses on the M2000 client. It also allows users to import the information about the binding relationships into a file.

The M2000 allows users to view the assignment information about IP addresses. To facilitate information browse, it also allows users to filter IP address assignment records by fields such as BTS ID, BTS name, and ESN.

Enhancement


Allowing users to filter IP address assignment records by fields such as BTS ID, BTS name, and ESN

WOFD-071500 User Profile Management

Availability


Description

The user profile setting provides the user-defined settings based on M2000 users. Therefore, multiple maintenance terminals can share the user-defined user settings. The M2000 provides default settings for all M2000 users. The supported profile setting options are as follows:

Display styles of parameter settings on the M2000 client, such as area setting, metrology setting, LMT prompt setting, agent server setting, MML client setting, file transfer parameter setting, alarm sound and colors, time mode, system lock time, data display modes, system login modes, display of alarm states in the topology view, and display of the performance module interface.

Environment setting of function interfaces, such as the topology view, activated subnets and filter criteria in the topology view, filter criteria for querying alarms, and alarm query templates.

WOFD-080100 Disk Redundant Backup

Availability




19

Description

The local disks of the M2000 support the RAID 1 backup mode (1+1 disk mirroring). The supported redundancy solutions vary according to disk array types. Sun 6140, Sun 3320, OceanStor S3100, and OceanStor S3200 disk arrays support the RAID 5+Hotspare mode. Sun 6180, OceanStor S2600, and OceanStor S3900 disk arrays support the RAID 10+Hotspare mode.

WOFD-080200 Dual Plane Communication

Availability


Description

The M2000 supports the dual-plane networking of operation and maintenance, in which two independent communication links form an O&M network. The M2000 automatically monitors the communication status of both channels. The routine communication is performed on the active plane. If the active plane is faulty, the M2000 automatically switches the communication to the standby plane to ensure the reliability of the O&M network.

WOFD-080300 M2000 Data Backup and Restore

Availability


Summary

The M2000 provides the backup and restore solutions for M2000 data. According to the characteristics of backup data, the backup and restore is classified into backup and restore of application data including M2000 application and service data, backup and restore of database applications, and backup and restore of operating systems. The M2000 provides different backup and restore solutions based on the levels.

Benefits


The M2000 provides cost-efficient backup and restore solutions for the O&M network. With the characteristics of simple configuration and flexible deployment, the backup and

restore solutions require only tape drives and related tapes. Therefore, the solutions are easy to use.

The M2000 provides backup and restore solutions at multiple levels, meeting the requirements of primary O&M application scenarios.

Description


Backing up and restoring application data



20

Application data consists of the data in the M2000 application and the service data in the M2000 database. The M2000 provides a user-friendly GUI for backup operations and management. Users can set backup tasks on the M2000 client to back up the application data of the M2000 in full or incremental backup mode. The M2000 using the Sybase database supports both full and incremental backups. The M2000 using the Oracle database supports only the full backup. The system provides automatic and manual backups. A manual backup is started immediately after users activate the backup. Manual backups can be implemented in incremental or full backup mode. The M2000 manages automatic backup tasks based on the feature WOFD-071200 Centralized Task Manager. In each backup period, the M2000 using Sybase database performs a full backup on the first day. Users can set the M2000 to perform no backup or an incremental backup on each of the other days. Users can also specify the backup execution time and period. The M2000 using Oracle database performs a full backup each day. Users can also specify the backup execution time. The backup data is stored on the disk array of the M2000 server or external tape drives. The M2000 based on ATAE platform stores the backup data on the disk array. To restore the application data in specified full and incremental backup files to the database and applications, users need to run the restore script.

Backing up and restoring the database application and operating systems Database applications consist of database server application and database device files. Operating system data involves all the files related to the operating system. Users perform the backup or recovery of the database application and operating system by running the scripts. Database applications and operating systems are backed up to the local hard disk and disk array of the M2000 server or external tape drives. The M2000 based on ATAE platform stores the backup data on the disk array.

Enhancement


The M2000 system using M4000 or M5000 servers allows users to back up the operating system to the local hard disk of the M2000 server.


Users can back up database applications to local hard disk of the M2000 server.

WOFD-080400 NE Data Backup and Restore

Availability


Summary

The M2000 supports the backup and restore of key NE data. If NE data is missing due to a fault, users can use the backup data to restore the NE data on the M2000.



21

Description

Generally, key NE data (such as NE configuration data and logs) is stored on NEs. The M2000 backs up NE data by obtaining the data from NEs and saving it on the disk array of the M2000 server or downloading the data to the M2000 client.

Key NE data is backed up and restored on the M2000. The data can be backed up manually or automatically on a scheduled basis. The M2000 centrally manages and schedules backup tasks by using the feature WOFD-071200 Centralized Task Manager. The M2000 backs up NE data based on the preset period and time.

Data must be restored manually because it may lead to NE restart. After users restore NE data, the M2000 downloads backup NE data to the NE and runs data restoration commands for the data to take effect. Users must upload the NE data that was downloaded and stored on the M2000 client to the M2000 server before restoring the data.

NE logs cannot be modified or replaced, and the restore of NE logs may result in invalid modification of the NE logs. Therefore, the M2000 does not provide the function of restoring NE logs.

WOFD-210200 Automatic File Upload

Availability


Summary

The M2000 supports the function of automatically uploading the northbound configuration files, performance files, inventory files and alarm files to the specified FTP server by using FTP.

To ensure data transmission security, the M2000 supports SFTP-based file transfer with the third-party system. For details, see the optional feature WOFD-210100 Encrypted Transmission.

Benefits

This feature reduces the workload and costs for developing a third-party system.

The M2000 sets up and manages the transmission connection. In the HA, remote HA, or SLS system, the switchover between the active node and the

standby node does not affect the uploading of files to the third-party system.

Description


Configuring the uploaded information about the server On the client, users can choose to upload the exported files of configuration data, alarms, performance data, inventory data, and license data and set the IP address, directory, user name, password, and file compression mode of the server. The M2000 creates a directory on the server according to the settings. Users can configure specific file servers for different types of data. The M2000 can upload data files to a maximum of 10 file servers.

Supporting the file transfer in single- or multi-connection mode



22

The types of northbound exported files comprise the configuration files, performance files, alarm files, and inventory files. The M2000 can upload the files of each type to one server (single-connection) or multiple servers (multi-connection). By default, the single-connection mode is used. Users can set the uploading mode.

Creating a directory on the uploading server Users can create a directory on the server for the M2000 to save uploaded northbound files.

Alternatively, the M2000 can create a directory for saving the files. The directory structure is the same as that of the M2000 northbound export file directory.

Managing file transfer On the M2000 client, users can browse files to be transferred and files failing to be transferred. In addition, users can delete the files to be transferred. Users can automatically re-transfer the files that failed to be transferred according to the configuration parameters. The valid duration for re-transferring the files is 1 hour. The system cancels the transfer

of the files that exceed the valid duration. The system transfers the files again three times. The system records the files that are

re-transferred more than three times, to the logs. The interval for re-transferring files is 15 minutes.

Managing faults If a file fails to be uploaded to a third-party system because the FTP service of the third-party system is not enabled or the network is disconnected, the M2000 generates an alarm and forwards this alarm to the third-party system through the northbound alarm interface.

Enhancement

In M2000 V200R010, the M2000 generates an alarm if a file fails to be uploaded to a third-party system.

Dependency

This feature is used with the following features to implement automatic file upload and cannot work independently:

WOFD-100210 Alarm File Interface WOFD-100220 Performance File Interface WOFD-100230 Configuration File Interface WOFD-100240 Inventory File Interface WOFD-261000 Interface for Exporting Configuration Data Files GBSS WOFD-184500 Interface for Exporting Configuration Data Files WRAN WOFD-188011 Interface for Exporting Configuration Data Files LTE WOFD-070400 NE License Management



23

2.2 Fault Management

WOFD-010100 Centralized Storage of Alarm Information

Availability


Description

The M2000 centrally collects the alarm information about all the entities (including the M2000 itself) of managed networks and stores the alarm information in the database. The fault management module of the M2000 can manage alarms and events. Alarms are classified into ADAC alarms and ADMC alarms. Unless otherwise stated, alarms mentioned in this document do not include events.

Event: An event is a notification that is generated and needs to be sent to users when the system is running properly. For example, the notification can be the deletion, modification, or status change of an object. Fault: A fault occurs when the system is running improperly. The fault may affect the operation capability or backup capability.

Alarm: An alarm is a notification that is generated when the system detects a fault.

Based on the detection capability, alarms are categorized as ADAC alarms and ADMC alarms.

ADAC (Auto Detected Auto Cleared) alarm: An ADAC alarm is generated and cleared when specified conditions are met. When a fault occurs, an alarm occurrence notification is generated. After the fault is cleared, an alarm clearance notification is generated.

ADMC alarm: An ADMC alarm is generated when specified conditions are met, but it cannot be cleared automatically. When a fault occurs, an alarm occurrence notification is generated. An alarm clearance notification, however, is not sent. O&M personnel need to check that the fault is cleared and manually clear the ADMC alarm.

After receiving the alarm and event reported by an NE, the M2000 preprocesses the alarm and event and stores them in the centralized mode. The information serves as the reference for future browse, collection of statistics, and query.

The M2000 records each alarm or event as one log. The database stores alarm or event logs for a maximum of 90 days. Users can change the period. If the M2000 alarm database does not meet the standard configuration or the network size exceeds the management capacity of the server, users may not be able to store the logs for 90 days. When the M2000 reaches the end of the storage period or disk capacity limit, the M2000 automatically dumps event logs and logs for acknowledged and cleared alarms to files.

WOFD-010300 Alarm Viewer

Availability




24

Summary

This feature allows users to view the alarms and events of NEs and the M2000 in real time. Based on the browse results, users can also perform operations such as saving and printing alarm information, viewing detailed alarm information, and locating alarms in the topology view. Users can set conditions for filtering alarms or save the filter criteria as a template for future use.

In addition, users can customize the colors and properties of alarms and events displayed in the browse window. Users can also set the uncleared alarms to be highlighted.

Benefits


The M2000 allows users to browse alarms on the entire network in real time. It also allows users to set various filter criteria to focus on key network faults.

The function of customizing display styles helps users to personalize working interfaces.

Description


Alarm/Event browse The M2000 displays the alarms that meet the preset filter criteria in the alarm/event browse window. Multiple browse windows can be opened concurrently to display alarm logs, event logs, and alarm lists. Users can set filter criteria in each browse window. The alarm list displays important alarms that users must focus on or handle. If an alarm has duplicate alarm records, only one record is displayed in the alarm list. During routine maintenance, O&M personnel need to monitor only the alarm list. By default, acknowledged and cleared alarms are not stored in the alarm list. Users can store these alarms after setting a storage period. Users can set the following filter criteria: alarm source (including NE type, NE, MO, MBTS, object group, and topology maintenance area), severity, type, and name. Events do not need to be cleared or acknowledged. Therefore, log browse does not support status-related filter criteria such as clearance status and acknowledgment status. The M2000 supports the following alarm types: Power system alarm Environment system alarm Signaling system alarm Trunk system alarm Hardware system alarm Software system alarm Running system alarm Communication system alarm QoS alarm Processing error alarm Internal alarm Integrity violation alarm Operational violation alarm



25

Physical violation alarm Security violation alarm Time domain violation alarm In addition, the M2000 supports the browse of alarms based on alarm categories. Users can browse alarms according to alarm severities or alarm statuses in the same window. Alarms statuses are unacknowledged and uncleared, unacknowledged and cleared, acknowledged and uncleared, and acknowledged and clear. In the event browse window, users can query event details, locate an event on the corresponding NE in the topology view, mask the event, or send a remote event notification. In the alarm browse windows, users can perform more operations, such as acknowledging, unacknowledging, and clearing alarms.

Template Users can save common filter criteria as a template so that they can use the template to set filter criteria when browsing alarms or events. The M2000 filters the browse results according to the conditions set in the template. Alarm templates are saved by user. The owner of a template is the user who creates the template. Such users can share their templates with other users. Administrators can manage and use all templates. Common users can manage and use their templates and shared templates. The M2000 provides a centralized template management window. Users can manage their templates, for example, viewing, creating, deleting, modifying, and renaming templates.

Alarm/Event groups and object groups The M2000 allows users to view, query, and collect the statistics on alarms and events based on alarm/event groups and object groups. An alarm or event group is a set of alarms or events. An object group is a set of objects where alarms or events are generated, for example, NEs, boards, cells, and links. Users can define alarm/event groups and object groups according to the actual requirements.

Saving and printing alarm/event information Users can save the alarm or event information in the browse window as TXT, HTML, PDF, XLS, and CSV files or print the information. Users can save or print part of or all alarms.

Customizing alarm/event display styles The M2000 allows users to customize the following elements in the alarm browse window: Colors in which alarms/events are displayed Attributes of the alarms/events to be displayed Orders for sorting alarm/event attribute columns Conditions for sorting alarm/event attributes The settings take effect only on the current client. Alarm properties include alarm names, severities, types, location information, IDs, clearance status, and acknowledgment status. Events do not need to be cleared or acknowledged. Therefore, log browse does not support status-related filter criteria such as clearance status and acknowledgment status. In the alarm browse window, users can sort alarms/events according to one or more alarm/event attributes.



26

Alarms and events of different severities are identified with different colors. Users can modify the default settings. The settings take effect in the alarm browse window, alarm boards, and alarm icons in the topology view. The M2000 checks alarms and highlights the alarms that are in the unacknowledged and uncleared state, unacknowledged and cleared state, and acknowledged and uncleared state for a long time. Users can set thresholds for alarms of different severities. When the status or state duration reaches the preset thresholds, the M2000 highlights the corresponding alarms.

Enhancement


The M2000 allows users to open the device panel of the NE that generates the selected alarm when users locate the device panel in the alarm viewer.

The M2000 supports alarm/event groups and object groups. Users can perform operations such as viewing, querying, and collecting the statistics on alarms and events based on alarm/event groups and object groups.

WOFD-014200 Real-Time Alarm Notification

Availability


Summary

The M2000 supports the real-time notification of alarms in the forms of sound, light, blinking, and display of statistical results. Alarms are notified through alarm boxes, alarm boards, tool tips, and real-time statistics.

Benefits

The M2000 supports the real-time alarm notification in multiple modes. This ensures that users can learn about the generation and clearance of alarms in real time to take corresponding troubleshooting measures, reducing the impacts on network services.

Description


Alarm box The M2000 notifies users of audible and visual alarms through an alarm box. The alarm box is connected to the M2000 client through a serial port. The M2000 client sends the alarms that meet the preset conditions to the alarm box in real time. Then, the alarm box generates sound and the corresponding alarm indicators blink according to the alarm severities. Users can filter alarms based on alarm severities or by using a query template. The filter criteria set in a query template are the same as the filter criteria in the feature WOFD-010300 Alarm Viewer.

Alarm notification by sound and light M2000 provides alarm boards to display the total number of current alarms, number of alarms of each severity, and number of alarms of each severity in each status in real time



27

and to notify users of new alarms by emitting sound and through blinking icons. Users can customize notification sound. Users can set a template to control the range for collecting the statistics of alarms. The conditions in the template are the same as the conditions described in the feature WOFD-010300 Alarm Viewer.

Tool tip After users set the alarm indication in the topology view, the NE icon is identified in the color of the alarm of the highest severity when alarms in the same status exist on an NE. The alarm states that can be selected are unacknowledged and uncleared. In addition, users can set whether to display the current number of alarms of the highest severity on NEs.

Real-time collection of alarm statistics When creating statistical charts, users need to select alarm templates. According to filter criteria in the alarm list templates, the M2000 filters alarms and collects the statistics of alarms based on alarm severities and types. The statistical results are displayed in a bar chart and are updated in real time according to the generation or clearance of alarms. Users can select multiple alarm list templates to create multiple statistical charts.

Users can obtain the details about alarm sources in masking conditions by referring to the feature WOFD-010300 Alarm Viewer.

WOFD-011400 Automatic Alarm Retrieval

Availability


Description

After the connection between the M2000 and NEs is restored, the M2000 automatically synchronizes the data between the M2000 and NEs to obtain the alarm data generated during the disconnection. This feature ensures that the alarm data on the M2000 and NEs is consistent.

When NEs report alarms to the M2000, the M2000 automatically checks whether the alarm data on the M2000 is consistent with that on NEs. If the data is inconsistent, the M2000 synchronizes the alarm data on the M2000 with that on NEs.

WOFD-011500 Alarm Synchronization

Availability


Description

Generally, after an alarm is generated on an NE or the M2000, the alarm is automatically reported to the M2000 in real time. The M2000 supports manual and scheduled alarm synchronization modes. Therefore, alarms can be synchronized in the following scenarios:

The connection between an NE and the M2000 is restored after it is disrupted. The status of an alarm is updated after the alarm is handled.

The M2000 supports manual alarm synchronization and scheduled alarm synchronization.



28

In manual synchronization mode, users manually synchronize the alarm data on the M2000 with that on NEs through the M2000 client.

Scheduled synchronization tasks are managed and scheduled by using the feature WOFD-071200 Centralized Task Manager. In scheduled synchronization mode, the M2000 synchronizes the alarm data on the M2000 with that on NEs according to the preset period and time. Users can change the synchronization period and time. The unit of the synchronization period is day. The default synchronization period is one day.

WOFD-014000 Alarm Pre-Processing on M2000

Availability


Summary

Alarm pre-processing on the M2000 refers to processing the new alarms and events received by the M2000 before they are saved to the database. Alarm pre-processing involves alarm masking, alarm severity redefinition, and alarm correlation analysis.

Benefits

The M2000 provides flexible functions of masking alarms and customizing the rules for analyzing alarm correlations. This helps in sharing the maintenance experience of O&M personnel, reducing the number of alarms, and improving work efficiency.

Description


Masking alarms and events After receiving alarms or events, the M2000 checks and discards the alarms or events that meet the preset masking conditions. The supported conditions for masking alarms and events include alarm/event sources, alarm/event severities, alarm/event names, alarm location information, alarm duration, and alarm/event types. Users can also set the time segment for alarm masking conditions to take effect. Delayed alarm/event processing: If the duration of an alarm/event is shorter than the threshold set in the alarm/event masking criteria, the M2000 discards the alarm/event after analyzing toggling alarms. When the duration of an alarm/event reaches or exceeds the preset threshold, the M2000 delays processing the alarm/event. The delay time equals the preset threshold of alarm/event duration.

Users can obtain the details about alarm sources in masking conditions by referring to the feature WOFD-010300 Alarm Viewer.

Redefining alarm and event severities Users can modify the properties of alarms and events on the M2000. For example, users can change the severities, names, and types of alarms and events. After the alarm and event properties are redefined, the M2000 displays the alarms and events based on the new properties. The redefinition takes effect only on the M2000. On NEs, the properties of alarms and events remain unchanged.



29

Alarm severities can be redefined on the basis of time segments, such as during a busy hour and a non-busy hour.

Analyzing correlations Correlation rules are classified into default and user-defined rules. Default rules are provided by the system and can be instantiated by users. These rules are used for analyzing alarm or event occurrence frequency, intermittent alarms, repeated events, and duration of acknowledged and uncleared alarms. Associated concepts are described as follows: Alarm or event occurrence frequency: If the number of repeated alarms or events exceeds a preset threshold within a specified period, the M2000 considers that these alarms or events are correlated and performs one of the following operations, which have different threshold ranges: Changing the alarm or event severity Generating an avalanche alarm Generating an avalanche alarm and masking alarms or events Generating a toggling alarm Intermittent alarm: The M2000 generates an intermittent alarm if the interval for reporting the clearance alarm of an alarm is within a specified period. The M2000 displays only the first intermittent alarm and discards other ones. If the number of intermittent alarms exceeds a preset threshold within a specified period, the M2000 generates a high-frequency intermittent alarm. When intermittent alarms are generated at a lower frequency than the threshold, the high-frequency intermittent alarm is automatically cleared. Repeated event: The M2000 generates a repeated event if the interval for reporting an event is within a specified period. The M2000 displays only the first repeated event and discards other ones. If the number of repeated events exceeds a preset threshold within a specified period, the M2000 generates a high-frequency repeated event. With the correlation analysis function, users can create rule instances for analyzing alarms/events frequency, intermittent alarms, and repeated events. If alarms/events meet the preset conditions, the M2000 deals with the information about redundant alarms/events according to the preset policy. This prevents the M2000 from generating or clearing the same alarms, enhancing system reliability. The purpose of analyzing the duration of acknowledged and uncleared alarms is to prompt users to clear these alarms in time. If certain alarms are already acknowledged but are not cleared for a long time, the M2000 sets the severity of these alarms to a higher level. The M2000 allows users to define alarm correlation rules by setting root alarms, correlated alarms, handling methods, handling conditions, analysis periods, and priorities through the creation wizard. Users can delete or modify alarm correlation rules. After users apply advanced correlation rules, the M2000 discards the alarms/events that meet the correlation rules. It can also redefine the severities of these alarms or set them to correlative alarms. Therefore, the number of unnecessary alarms/events is reduced and non-root alarms/events are not considered. Therefore, users can handle key alarms/events to quickly locate and rectify related faults. Advanced correlation rules support the following functions: Setting correlations within a single NE and among multiple NEs. The main property values in the alarm locating information can serve as correlation

conditions. Users can set the interval for analyzing correlations.



30

Converting events to ADMC alarms The M2000 allows users to convert an event to an ADMC alarm. Then, the ADMC alarm is displayed in the alarm list. After the conversion setting is canceled, newly reported records of this event are no longer displayed in the alarm list.

Enhancement


The M2000 generates a summarized parallel alarm when the number of alarms meeting the requirements exceeds Set Threshold.

The M2000 clears the summarized parallel alarm when the number of alarms is smaller than Clear Threshold.

Users can add or delete summarized parallel alarm rule.


The M2000 generates a toggling alarm in analyzing alarm or event occurrence frequency.


The M2000 supports redefinition of alarm severities based on time segments.


A wizard for creating advanced correlation rules is added, which improves the usability of this feature.

The names and types of alarms/events can be redefined.

WOFD-012200 Alarm Severity Redefinition on NE

Availability


Description

Alarm severity redefinition on NEs allows users to change the severities of alarms and events on NEs. After severities of alarms and events are redefined, NEs report alarms and events according to the new severities, and the M2000 displays the alarms and events according to the new severities.

WOFD-012400 Alarm Masking on NE

Availability


Description

Alarm masking on NEs allows users to set masking conditions on the M2000 and send the conditions to NEs so that NEs do not report the alarms and events that meet the masking conditions. Therefore, the masking for alarms and events is implemented on NEs.



31

The M2000 masks alarms and events according to alarm/event names and severities. When setting masking conditions, users can sort NE objects according to NE types and sort alarms and events according to alarm/event types and severities. This facilitates alarm/event selection.

Some NEs such as the BSC6900 GSM and BSC6900 GU can mask alarms and events according to objects. The supported objects are cells and GBTSs. Users can modify, delete, or query preset alarm masking conditions.

In addition, the M2000 allows users to import the masking conditions of alarms and events from a file to the M2000. Users can export the preset masking conditions as a template, set masking conditions in the template, and import the template to the M2000. Then, the M2000 generates masking conditions based on the records in the file.

WOFD-013400 Environment Alarm Setting

Availability


Summary

To monitor NE environments, the M2000 supports the settings of environment alarms.

Benefits

Users can customize environment alarms to learn about the faults in the equipment room environment and remotely monitor the environment centrally. This helps ensure the normal equipment operation.

Description

Based on the actual situations, users can set environment alarms of NEs through the M2000 client, and bind the alarms with an NE port. In addition, users can mount an environment monitoring device on the port so that NEs can generate alarms and report the alarms to the M2000 in real time when the environment monitoring device detects environment faults.

This feature requires alarm definition and binding information.

The alarm information to be defined includes alarm names, severities, and IDs.

Alarm binding information indicates the mapping between environment monitoring devices and defined alarms (including alarm generation conditions). After the binding, NEs can generate alarms based on the binding conditions and report the alarms to the M2000.

The M2000 also allows users to import and export environment alarms as XLS files. Users export a template from the M2000, fill in required information, and import the template into the M2000. The M2000 can then generate environment alarms based on the information in the template.

Enhancement

The functions of importing and exporting environment alarms are added to M2000 V200R012C00.



32

WOFD-014100 Alarm Post-Processing on M2000

Availability


Summary

In alarm post-processing on the M2000, the M2000 allows users to perform a series of operations on the alarms stored in the database, such as acknowledging alarms, unacknowledging alarms, and collecting the statistics of alarms.

Benefits According to the requirements of the 3GPP specifications, alarm acknowledgment, alarm

unacknowledgment, and status switch are supported to meet the requirements of network O&M scenarios.

The M2000 collects the statistics on alarms based on different dimensions and displays the statistical results on the GUI so that users can directly learn about the alarm distribution on the network.

Description


Acknowledging and unacknowledging alarms After users successfully acknowledge an alarm, its status automatically changes to "Acknowledged." The M2000 supports manual acknowledgment and automatic acknowledgment. In manual acknowledgment mode, users can select and acknowledge alarms in the alarm browse window. In automatic acknowledgment mode, alarms can be automatically acknowledged according to the preset conditions.

Users can learn about the details of alarm sources in the automatic alarm acknowledgment conditions by referring to the feature WOFD-010300 Alarm Viewer.

Users can unacknowledge the alarms that are acknowledged but not cleared. After an alarm is successfully unacknowledged, its status automatically changes to "Unacknowledged." The M2000 records the information about the time and the user who performs the related operations.

Collecting alarm and event statistics Users can collect the statistics of alarms and events based on multiple dimensions. The statistical results can be displayed in a table or pie chart. Supported statistical conditions are NE types, NEs, alarm/event names, severities, types, and status. Users can collect alarm statistics based on a maximum of three conditions. Users can save the statistical results as TXT, HTML, CSV, XLS, or PDF files, or print the results. In addition, users can filter alarms before collecting statistics. The supported filter criteria are the same as the conditions described in the feature WOFD-010300 Alarm Viewer.



33

WOFD-012000 Automatic Alarm Clearing

Availability


Description

When the fault on an NE or on the M2000 is rectified, the NE reports a clear alarm and the M2000 sets the status of the corresponding fault alarm to "Cleared."

WOFD-011900 Manual Alarm Clearing

Availability


Description

On the M2000 client, users can manually clear specified alarms. After an alarm is cleared, the M2000 changes the status of this alarm to "Cleared" and instructs the related NE to change the alarm status to "Cleared." This feature is used to clear the alarms that cannot be automatically cleared or the alarms that do not exist according to user confirmation.

WOFD-013300 Alarm Checking

Availability


Descr

Documents

IManager M2000 V200R012 Basic Feature Description