IManager M2000 V200R013 Basic Feature Description(ELTE2.1)

8/20/2019 IManager M2000 V200R013 Basic Feature Description(ELTE2.1)

1/80

iManager M2000 V200R013Basic Feature Description(eLTE2.1)

Issue 02

Date 2012-04-12

HUAWEI TECHNOLOGIES CO., LTD.


2/80

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 trademarksand 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, andrecommendations 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]

http://www.huawei.com/mailto:[email protected]:[email protected]://www.huawei.com/


3/80

iManager M2000 V200R012

Basic Feature Description

Issue 02 (2012-04-12) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

1

Contents

1 Overview ................................................................................................................................... 2

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

2.1 Platform .................................................................................................................................................... 3

2.2 Fault Management ....................................................................................................................................15

2.3 Configuration Management.......................................................................................................................27

2.4 Performance Management ........................................................................................................................34

2.5 Security Management ...............................................................................................................................40

2.6 Topology Management .............................................................................................................................52

2.7 NE License Management ..........................................................................................................................54

2.8 Hardware and Software Management ........................................................................................................56

2.9 Network Monitoring and Analysis .............................................................................................................59

2.10 FARS .....................................................................................................................................................67

2.11 Base Station Commissioning Management ..............................................................................................73

3 Acronyms and Abbreviations ............................................................................................... 76


4/80





2

1 OverviewThis document describes the basic features provided by Huawei M2000 V200R012. Thisdocument helps users understand the M2000 features.

The network elements (NEs) in this document refer to the network devices managed by theM2000. The M2000 manages eWBB based on Long Term Evolution (LTE), .

The M2000 manages the following eRAN NEs:

Base station: eNodeB, including DBS3900 LTE

Clock server: IP Clock Server

The M2000 manages the following evolved packet core (EPC) NEs:

Enterprise core network system: eCNS


5/80





3

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 LTE network. 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'sworking efficiency, reduce operation and maintenance (O&M) costs, and therefore minimizetelecom 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 beinginstalled on the live network. When releasing an M2000 software version, the M2000 usesa digital certificate to sign the software version. Before installing or upgrading the M2000software, 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/80





4

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 and valid value ranges of MML command parameters

− Details about configuration parameters, alarms, and performance counters

Users can switch to Help information about the MML commands, alarms, performancecounters, and configuration objects and parameters from the command-line interface(CLI), alarm, performance, and configuration management windows.

Users can create, edit, delete, and manage remarks on any Help pages. Remarksmanagement 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. When afault occurs on the hardware, the M2000 generates an alarm.

M2000 license management

The M2000 license defines the M2000's management capability on the network. TheM2000 provides specific network resource management capacity and optional featuresunder license control.

The M2000 license control items consist of function control items and resource controlitems. Users can view the function authorization information, update the license file, andexport license information to a CSV or XLS file.

− Function control items: authorized optional M2000 features controlled on the basis offunctions.

− Resource control items: authorized M2000 features that are controlled by the numberof resources, manageable resource capacities, and number of used resources of thesefeatures. 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 canmanually clear the 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

The M2000 supports multiple concurrent clients. The number of concurrent clients that theM2000 can manage depends on the hardware configuration of the M2000 server.

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 a remote web-based installation, users can log in to the M2000 serverthrough 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


7/80





5

updates the client software to the matching version according to the user confirmation.This improves the efficiency of 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 withoutupgrading 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 requirethe mediation version. Users who require the new mediation need log in to the client againto use the latest mediation version.

In scenarios such as initial site deployment and network upgrade, multiple mediationsneed to be loaded at a time. The M2000 can load NE mediations in batches, reducing theloading 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, M2000 client IPaddress, user type, session start time, and user group. The user-operation monitoring candisplay information such as user name, M2000 Client IP address, security operation,operation object, risk level and execution result. With this function, administrators canforce a specified user to log out.

Workbench management

The M2000 provides a workbench for function and application shortcuts. Users can createfunction and application shortcuts on the workbench, which simplifies operations andimproves operation efficiency. Users can also customize the names, description, and iconsof workbench shortcuts. The M2000 provides default workbench shortcuts to certainfunctions such as centralized MML CLI, centralized task management, system monitoring,and topology management.

Enhancement

The following functions are added to M2000 V200R011C00:

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:

Creating and managing remarks in a Help window

Invalidating licenses


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



8/80





6

Collecting M2000 performance statistics

Installing and automatically upgrading M2000 clients on a web browser

Loading M2000 mediation versions online

WOFD-000200 File Transfer Management

Availability


Summary

The M2000 supports file transfer between the M2000 server and the M2000 client, between theM2000 and NEs, and between the M2000 and a third-party system by using File TransferProtocol (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.

Benefits

This feature ensures effective file transfers 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 beimplemented 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 transfersfiles 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 athird-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. Forexample, when transferring files to a third-party system, the M2000 can be either an FTP serveror 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 functionsas 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 filetransfer between NEs and the M2000 server and between the M2000 client and server, disable plaintext transfer, and set a transfer server and a third-party FTP server.

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

Enhancement

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


9/80





7

Dependency

None.

WOFD-000300 Application Management Platform

Availability


Summary

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

The iSStar script applications are classified into local script applications and remote scriptapplications. Local script application files are stored and executed on the M2000 client. Remotescript 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 iSStarscript. After the script is released, users can run it and obtain the execution results throughthe shortcut on the application management platform.

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

Description

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

Workspace management

A workspace is a management platform for categorizing application shortcuts. Theapplications of the same category can be managed by one workspace. Users can categorize

applications based on their preferences and manage these applications on differentworkspaces. Users can create or delete workspaces and change the workspace names.

Remote application management

The application management platform allows users to manage remote iSStar scriptapplications, 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 theshortcuts. In addition, users can create shortcuts to both local and remote iSStar scriptapplications. When using the shortcuts of iSStar script applications, users can selectmultiple NEs at a time to create script tasks in batches.

Task management


10/80





8

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

and check task execution results.

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 LMTcan 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 transmissionsecurity 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 cansynchronize time with the time server of a third-party system and provide synchronization timesources 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 MD5encrypted algorithm defined in the NTP V3 in time synchronization.

BenefitsThis feature ensures that the time of NEs on the entire network is synchronized. In addition, itsupports adopting the encrypted authentication to enhance the security of network timesynchronization.

Description

If the NTP server provided by a customer network cannot communicate with the mobilecommunication devices managed by the M2000, the M2000 server can function as anintermediate NTP server. The M2000 server obtains the reference time from the NTP server provided by the customer and sends time synchronization signals to NEs to ensure theconsistency between the time of all NEs and the time of the time source. The M2000 monitors


11/80





9

the operating status of the NTP service in real time and generates an alarm after detecting anyexceptions in the NTP service or a synchronization failure with the upper-level time source.

The NTP protocol supports two authentication modes: unauthenticated and encryptedauthentication. Customer can determine the authentication mode according to security

requirements. If the upper-layer NTP server provided by the telecom operator uses theencrypted authentication mode, the M2000 server synchronizes time with the time of theupper-layer NTP server in encrypted authentication mode. After NEs send a timesynchronization request to the M2000, the M2000 allows NEs to synchronize time with theM2000 server time in encrypted authentication mode.

This feature requires customer to provide a top-level clock source server. If customer requires atop-level clock source server from Huawei, they need to purchase Huawei entire-network timesynchronization 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 asynchronization failure with the upper-level time source.

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 switchoversevery year. Some countries cross multiple time zones. Therefore, the time of NEs in differenttime zones must be different.

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

WOFD-071200 Centralized Task Manager

Availability



12/80





10

Description

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

The tasks managed centrally are classified into system-scheduled tasks and user-scheduledtasks. There are two types of tasks: one-time tasks and periodic tasks. Users can createuser-scheduled tasks and select one-time tasks or periodic tasks as required. Allsystem-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 taskinformation includes task name, execution period, type, creator, status, execution progress,execution result, and last execution time. Users can also perform specific operations on thetasks, such as start, delete, suspend, copy, or resume the tasks. In addition, users can modifytask 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 bemodified.

Data capacity tasks in system-scheduled tasks cannot be suspended or resumed. Dataexport 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

Dependency

None


13/80





11

WOFD-071300 Script Trigger

Availability


Description

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

Customizing menus to trigger scripts: This function allows users to customize the menus forscript triggering. Users can add, delete, modify, or query user-defined menus. When adding auser-defined menu, users can select the script and set script execution parameters. Theuser-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, andalarm ID. The M2000 automatically checks whether script triggering conditions are met. If theconditions are met, the corresponding script is automatically triggered.

The automatically triggered scripts are scripts stored on the M2000 server. Currently, HSLscripts 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


Description

The M2000 automatically assigns IP addresses to BTSs through the DHCP protocol. TheM2000 extends the DHCP protocol based on the standard protocol to support the requiredfunctions, and automatically assigns IP addresses to Huawei BSs on IP networks based on theextended DHCP protocol. The DHCP Server service provides the following functions:

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


14/80





12

The M2000 allows users to add, delete, or modify the binding relationships betweenspecific NE configuration information and IP addresses on the M2000 client. It also allowsusers 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

The following function is added to M2000 V200R011C01:

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

WOFD-071500 User Profile Management

AvailabilityThis feature was introduced in M2000 V200R008.

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 providesdefault 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, metrologysetting, 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 ofthe performance module interface.

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

WOFD-080100 Disk Redundant Backup

Availability


Description

The local disks of the M2000 support the RAID 1 backup mode (1+1 disk mirroring).

WOFD-080300 M2000 Data Backup and Restore

Availability



15/80





13

Summary

The M2000 provides the backup and restore solutions for M2000 application data includingM2000 application and service data.

Benefits


The M2000 provides cost-efficient backup and restore solutions for the O&M network.

Description


Backing up and restoring application data

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. Userscan set backup tasks on the M2000 client to back up the application data of the M2000 infull or incremental backup mode. The M2000 using the Sybase database supports both fulland incremental backups. The M2000 using the Oracle database supports only the full backup.

The system provides automatic and manual backups. A manual backup is startedimmediately after users activate the backup. Manual backups can be implemented inincremental or full backup mode. The M2000 manages automatic backup tasks based onthe feature WOFD-071200 Centralized Task Manager. The M2000 using Oracle database performs a full backup each day. Users can also specify the backup execution time.

To restore the application data in specified full and incremental backup files to thedatabase and applications, users need to run the restore script.

Dependency

This feature is supported when implement using Sybase database.

WOFD-080400 NE Data Backup and Restore

Availability


Summary

The M2000 supports 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.

Description

Generally, key NE data (such as NE configuration data and logs) is stored on NEs.

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


16/80





14

by using the feature WOFD-071200 Centralized Task Manager. The M2000 backs up the data based on the preset period and time.

Data must be restored manually because it may lead to NE restart. After users start restoring NEdata, 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 theM2000 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 ofthe 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 thethird-party system. For details, see the optional feature WOFD-210100 EncryptedTransmission.

Benefits The M2000 sets up and manages the transmission connection.

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, username, password, and file compression mode of the server. The M2000 creates a directoryon the server according to the settings. Users can configure specific file servers fordifferent types of data. The M2000 can upload data files to a maximum of 10 file servers.

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

The types of 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 (singleconnection) or multiple servers (multi-connection). By default, the single-connectionmode 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 files.Alternatively, the M2000 can create a directory for saving the files. The directory structureis the same as that of the M2000 export file directory.

Managing file transfer

On the M2000 client, users can browse files to be transferred and files failing to betransferred. In addition, users can delete the files to be transferred.


17/80





15

Users can automatically re-transfer the files that failed to be transferred according to theconfiguration parameters.

− The valid duration for re-transferring the files is 1 hour. The system cancels the transferof the files that exceed the valid duration.

− The system transfers the files again three times. The system records the files that arere-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 system because the FTP service of a third-party system isnot enabled or the network is disconnected, the M2000 generates an alarm.

Dependency

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

WOFD-070400 NE License Management

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 M2000itself) of managed networks and stores the alarm information in the database. The faultmanagement module of the M2000 can manage alarms and events. Alarms are classified intoADAC alarms and ADMC alarms. Unless otherwise stated, alarms mentioned in this documentdo not include events.

Event: An event is a notification that is generated and needs to be sent to users when the systemis running properly. For example, the notification can be the deletion, modification, or statuschange of an object.

Fault: A fault occurs when the system is running improperly. The fault may affect the operationcapability 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 whenspecified 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 thefault is cleared and manually clear the ADMC alarm.


18/80





16

After receiving the alarm and event reported by an NE, the M2000 preprocesses the alarm andevent and stores them in the centralized mode. The information serves as the reference forfuture 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 notmeet the standard configuration or the network size exceeds the management capacity of theserver, users may not be able to store the logs for 90 days. When the M2000 reaches the end ofthe storage period or disk capacity limit, the M2000 automatically dumps event logs and logsfor acknowledged and cleared alarms to files.

WOFD-010300 Alarm Viewer

Availability


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 printingalarm information, viewing detailed alarm information, and locating alarms in the topologyview. Users can set conditions for filtering alarms or save the filter criteria as a template forfuture use.

In addition, users can customize the colors and properties of alarms and events displayed in the browsing 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 allowsusers to set various filter criteria to focus on key network faults.

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

Description

This feature is described as follows:

Alarm/Event browse

The M2000 displays the alarms that meet the preset filter criteria in the alarm/event browsing window. Multiple browsing windows can be opened concurrently to displayalarm logs, event logs, and alarm lists. Users can set filter criteria in each browsingwindow.

The alarm list displays important alarms that users must focus on or handle. If an alarm hasduplicate alarm records, only one record is displayed in the alarm list. During routinemaintenance, 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 thesealarms after setting a storage period.

Users can set the following filter criteria: alarm source including NE types, NEs, MOs,MBTSs, object groups and topology maintenance areas, severity, type, and name. Eventsdo not need to be cleared or acknowledged. Therefore, log browse does not support

status-related filter criteria such as clearance status and acknowledgment status.


19/80





17

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

− Physical violation alarm

− Security violation alarm

− Time domain violation alarm

In addition, the M2000 supports the browse of alarms based on alarm categories. Userscan 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 browsing window, users can query event details, locate an event on thecorresponding NE in the topology view, mask the event, or send a remote event

notification. In the alarm browsing windows, users can perform more operations, such asacknowledging, unacknowledging, and clearing alarms.

Template

Users can save common filter criteria as a template so that they can use the template to setfilter criteria when browsing alarms or events. The M2000 filters the browse resultsaccording 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 theirtemplates with other users. Administrators can manage and use all templates. Commonusers can manage and use their templates and shared templates.

The M2000 provides a centralized template management window. Users can manage theirtemplates, for example, viewing, creating, deleting, modifying, and renaming templates.

Alarm/Event groups and object groupsThe 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 actualrequirements.

Saving and printing alarm/event information

Users can save the alarm or event information in the browsing window as TXT, HTML,

PDF, XLS, and CSV files or print the information. Users can save or print part of or allalarms.


20/80





18

Customizing alarm/event display styles

The M2000 allows users to customize the following elements in the alarm browsingwindow:

− 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 oracknowledged. Therefore, log browse does not support status-related filter criteria such asclearance status and acknowledgment status.

In the alarm browsing window, users can sort alarms/events according to one or morealarm/event attributes.

Alarms and events of different severities are identified with different colors. Users canmodify the default settings. The settings take effect in the alarm browsing window, alarm boards, and alarm icons in the topology view.

The M2000 checks alarms and highlights the alarms that are in the unacknowledged anduncleared state, unacknowledged and cleared state, and acknowledged and uncleared statefor a long time. Users can set thresholds for alarms of different severities. When the statusor state duration reaches the preset thresholds, the M2000 highlights the correspondingalarms.

Enhancement


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

The M2000 supports alarm/event groups and object groups. Users can perform operationssuch as viewing, querying, and collecting the statistics on alarms and events based onalarm/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, tooltips, and real-time statistics.

Benefits

The M2000 supports the real-time alarm notification in multiple modes. This ensures that userscan learn about the generation and clearance of alarms in real time to take corresponding

troubleshooting measures, reducing the impacts on network services.


21/80





19

Description

This feature is described as follows:

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 thealarms that meet the preset conditions to the alarm box in real time. Then, the alarm boxgenerates sound and the corresponding alarm indicators blink according to the alarmseverities. 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 featureWOFD-010300 Alarm Viewer.

Alarm notification by sound and light

M2000 provides alarm boards to display the total number of current alarms, number ofalarms of each severity, and number of alarms of each severity in each status in real timeand to notify users of new alarms by emitting sound and through blinking icons. Users cancustomize notification sound.

Users can set a template to control the range for collecting the statistics of alarms. Theconditions in the template are the same as the conditions described in the featureWOFD-010300 Alarm Viewer.

Tool tip

After users set the alarm indication in the topology view, the NE icon is identified in thecolor 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, userscan 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 ofalarms based on alarm severities and types. The statistical results are displayed in a barchart 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 featureWOFD-010300 Alarm Viewer.

WOFD-011400 Automatic Alarm Retrieval

Availability


Description

After the connection between the M2000 and NEs is restored, the M2000 automaticallysynchronizes the data between the M2000 and NEs to obtain the alarm data generated duringthe 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 dataon the M2000 is consistent with that on NEs. If the data is inconsistent, the M2000synchronizes the alarm data on the M2000 with that on NEs.


22/80





20

WOFD-011500 Alarm Synchronization

Availability


Description

Generally, after an alarm is generated on an NE or the M2000, the alarm is automaticallyreported to the M2000 in real time. The M2000 supports manual and scheduled alarmsynchronization 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.

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

Scheduled synchronization tasks are managed and scheduled by using the featureWOFD-071200 Centralized Task Manager. In scheduled synchronization mode, the M2000synchronizes the alarm data on the M2000 with that on NEs according to the preset period andtime. Users can change the synchronization period and time. The unit of t he 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 bythe 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 thatmeet the preset conditions.

The supported conditions for masking alarms and events include alarm/event sources,alarm/event severities, alarm/event names, alarm location information, alarm duration,


23/80





21

and alarm/event types. Users can also set the time segment for alarm masking conditionsto take effect.

Delayed alarm/event processing: If the duration of an alarm/event is shorter than thethreshold 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 featureWOFD-010300 Alarm Viewer.

Redefining alarm and event severities

Users can modify the properties of alarms and events on the M2000. For example, userscan change the severities, names, and types of alarms and events. After the alarm andevent 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 ofalarms and events remain unchanged.

Alarm severities can be redefined on the basis of time segments, such as during a busyhour 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 areused for analyzing alarm or event occurrence frequency, intermittent alarms, repeatedevents, 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 exceedsa 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 differentthreshold 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 reportingthe clearance alarm of an alarm is within a specified period. The M2000 displays only thefirst intermittent alarm and discards other ones. If the number of intermittent alarmsexceeds a preset threshold within a specified period, the M2000 generates ahigh-frequency intermittent alarm. When intermittent alarms are generated at a lower

frequency than the threshold, the high-frequency intermittent alarm is automaticallycleared.

Repeated event: The M2000 generates a repeated event if the interval for reporting anevent is within a specified period. The M2000 displays only the first repeated event anddiscards other ones. If the number of repeated events exceeds a preset threshold within aspecified period, the M2000 generates a high-frequency repeated event.

With the correlation analysis function, users can create rule instances for analyzingalarms/events frequency, intermittent alarms, and repeated events. If alarms/events meetthe preset conditions, the M2000 deals with the information about redundantalarms/events according to the preset policy. This prevents the M2000 from generating orclearing the same alarms, enhancing system reliability.


24/80





22

The purpose of analyzing the duration of acknowledged and uncleared alarms is to promptusers to clear these alarms in time. If certain alarms are already acknowledged but are notcleared 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 throughthe creation wizard.

Users can delete or modify alarm correlation rules.

After users apply advanced correlation rules, the M2000 discards the alarms/events thatmeet the correlation rules. It can also redefine the severities of these alarms or set them tocorrelative alarms. Therefore, the number of unnecessary alarms/events is reduced andnon-root alarms/events are not considered. Therefore, users can handle key alarms/eventsto 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.

Converting events to ADMC alarms

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

Enhancement


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

The M2000 clears the summarized parallel alarm when the number of alarms is smallerthan 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 ofthis feature.

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

WOFD-012200 Alarm Severity Redefinition on NE

Availability



25/80





23

Description

Alarm severity redefinition on NEs allows users to change the severities of alarms and eventson NEs. After severities of alarms and events are redefined, NEs report alarms and eventsaccording 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 maskingconditions. Therefore, the masking for alarms and events is implemented on NEs.

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

Users can modify, delete, or query preset alarm masking conditions.

In addition, the M2000 allows users to import the masking conditions of alarms and eventsfrom a file to the M2000. Users can export the preset masking conditions as a template, setmasking 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 roomenvironment and remotely monitor the environment centrally. This helps ensure the normalequipment operation.

Description

Based on the actual situations, users can set environment alarms of NEs through the M2000client, and bind the alarms with an NE port. In addition, users can mount an environmentmonitoring 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.


26/80





24

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 cangenerate 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. Usersexport a template from the M2000, fill in required information, and import the template into theM2000. The M2000 can then generate environment alarms based on the information in thetemplate.

Enhancement

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

WOFD-014100 Alarm Post-Processing on M2000

Availability


Summary

In alarm post-processing on the M2000, the M2000 allows users to perform a series ofoperations 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 networkO&M scenarios.

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

Description


Acknowledging and unacknowledging alarms

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

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

Users can unacknowledge the alarms that are acknowledged but not cleared. After analarm is successfully unacknowledged, its status automatically changes to"Unacknowledged."


27/80





25

The M2000 records the information about the time and the user who performs the relatedoperations.

Collecting alarm and event statistics

Users can collect the statistics of alarms and events based on multiple conditions. 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 theresults.

In addition, users can filter alarms before collecting statistics. The supported filter criteriaare the same as the conditions described in the feature WOFD-010300 Alarm Viewer.

WOFD-012000 Automatic Alarm Clearing

AvailabilityThis feature was introduced in M2000 V200R002.

Description

When the fault on an NE or on the M2000 is rectified, the NE reports a cleared alarm and theM2000 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, theM2000 changes the status of this alarm to "Cleared" and instructs the related NE to change thealarm status to "Cleared." This feature is used to clear the alarms that cannot be automaticallycleared or the alarms that do not exist according to user confirmation.

WOFD-013300 Alarm Checking

Availability


Description

This feature allows users on the M2000 client to check whether the status of a specified alarm isconsistent on the M2000 and on NEs. If the status is inconsistent, the M2000 updates the alarmstatus.


28/80





26

WOFD-013900 Alarm Correlation View

Availability


Summary

This feature is used for classifying NE alarms into root alarms and correlative alarms,depending on alarm generation causes. This feature allows O&M personnel to focus on rootalarms in the case of excessive alarms. Generally, multiple correlative alarms may result from aroot alarm. If a root alarm is cleared, most of its correlative alarms are cleared automatically.

Benefits

Device O&M personnel can clear root alarms first so that most of the correlative alarms can be

cleared automatically. Therefore, manual operations are reduced and maintenance efficiency isimproved.

Description


Analyzing alarm correlations

When alarms are generated, NEs and the M2000 analyze the correlated alarms, identifyroot alarms and correlative alarms, and report analysis results to the M2000.

Displaying alarm correlations

The M2000 displays the correlations between root alarms and correlative alarms in thealarm browsing window. This helps users to quickly locate faults.

The M2000 displays correlations between root and correlative alarms in the alarm browsing window. Users can quickly and efficiently locate faults by checking alarmcorrelations. Users can disable this function if they do not require the correlated alarmsreported by NEs. After this function is disabled, the M2000 does not display thecorrelations between root and correlative alarms reported from NEs.

Enhancement


Controlling the switch of alarm correlation display

Dependency

This feature applies to eRAN1.0 and later versions.

WOFD-012900 Alarm Information Base

Availability



29/80





27

Description

This feature allows users to record the explanations of alarms or events and the troubleshootingexperience in the alarm information base through the M2000 client. The M2000 keeps therecords in terms of the alarm/event ID. To facilitate maintenance experience sharing, the

M2000 allows users to export the alarm information base as an XML, CSV, TXT, XLS, HTML,or PDF file. It also allows users to import an external alarm information base as an XML file toappend to or replace the original alarm information base on the M2000.

The M2000 supports fuzzy search of maintenance experience information based on the namesof alarms and events or keywords of maintenance experience information in the alarmknowledge library. The search criteria can be the names of alarms and events, keywords ofmaintenance experience information, or the combination of the names and keywords. This improves the efficiency of querying maintenance experience information.

Users can also add comments to alarms and events to record the operations performed on thealarms and events. The change history (including the user, change time, and contents), isautomatically saved in the comments.

Enhancement

In M2000 V200R009, the M2000 supports fuzzy search of maintenance experience information based on the names of alarms and events or keywords of maintenance experience information.

2.3 Configuration Management

WOFD-020100 Auto-Synchronization for Configuration Alteration

Availability


Description

If the configuration of an NE is modified, the NE reports a modification notification to theM2000. Then, the M2000 updates the NE configuration data in the database according to thenotification. This implements the automatic synchronization of configuration data and ensuresthe consistency of the configuration data between NEs and the M2000.

Users can view the information about the latest automatic configuration data synchronization ofeach NE. The information contains the start time and end time of the synchronization,synchronization types, synchronization results, and result details.

Enhancement

The function of browsing the information about automatic data configuration synchronizationis added to M2000 V200R008.


30/80





28

WOFD-020200 Configuration Data Synchronization

Availability


Summary

To ensure that the configuration data between the M2000 and NEs is consistent, the M2000supports manual and scheduled synchronization of configuration data. Users can view theinformation about synchronization tasks.

Benefits The M2000 provides manual and scheduled configuration data synchronization. The two

synchronization modes enable users to control the synchronization progress and ensurethat the configuration data between NEs and the M2000 is consistent.

The M2000 displays the detailed information about NE configuration datasynchronization on the GUI, facilitating tracing and review of the configuration data.

Description


Synchronizing configuration data

The M2000 supports synchronizing configuration data manually or on a scheduled basis.

In manual synchronization mode, users manually start a synchronization task on theM2000 client. The M2000 updates and stores the data in the M2000 database based on the

current data obtained from NEs.

The M2000 synchronizes configuration based on the period and time set by users and therange of NEs. If users do not set the period or time, the M2000 performs scheduledsynchronization tasks according to the default settings. Users can set synchronizationintervals by day. The intervals must be a multiple of one day. Scheduled synchronizationtasks are managed and scheduled by using the feature WOFD-071200 Centralized TaskManager.

Browsing configuration task information

The M2000 displays, in a list, the current manual and scheduled data synchronizationinformation about all NEs managed by the M2000. The information listed includes thestart time, type, progress, and description of the synchronization. Users can save the

information to a local PC as a file.After the synchronization is started, the M2000 automatically records the synchronization.After the synchronization is complete, the M2000 automatically deletes the record.

In addition, users can view the information about the latest manual or scheduledconfiguration data synchronization. The M2000 displays, in a list, the executioninformation about the latest configuration data synchronization of all the NEs managed bythe M2000. The list displays the information about the start and end time of the historyconfiguration data synchronization tasks, synchronization types, synchronization results,and result details.


31/80





29

Enhancement

The function of browsing the information about manual and scheduled configurationsynchronization tasks is added to M2000 V200R008.

Dependency

None

WOFD-020400 Configuration Data Query

Availability


Summary

The M2000 provides a window for viewing configuration data. It supports the functions ofsearching for and exporting NE configuration data.

Benefits

The M2000 displays NE configuration data in a navigation tree and a table so that users caneasily view the logical relationships between configuration objects and detailed configurationinformation.

Description

The M2000 displays NE configuration data in an interface that contains a navigation tree in theleft pane and a table in the right pane. The navigation tree displays NE configuration objectsand their logical relationships. The table displays the details about selected configurationobjects. The M2000 allows users to search for NE configuration data based on the keywordscontained in configuration object names. It also allows users to locate the search results on thecorresponding nodes in the navigation tree.

In the window for viewing configuration data, users can select an NE to export its configurationdata. The exported data can be saved as CSV and XML files.

In addition, the M2000 displays the common configuration data of some objects as labels in thetopology view. The common configuration data includes NE names, NE types, IP addresses,current version information, link names, link types, and names of the NE nodes at both ends of

a link.

WOFD-020800 Object Management Status Monitor

Availability


Description

The M2000 displays the information about and status of hardware and software resources on

the GUI, which allows users to learn about the network status in real time. Users can set the


32/80





30

range of the objects whose status is to be monitored. They can also add, delete, suspend, andresume monitoring tasks. The M2000 supports sorting the monitoring results by the statusesand names of NEs and objects.

Table 2-1 describes the resources and resource statuses that can be monitored by using this

feature.

Table 2-1 Object management status

NE Type Object Type Management Status

eNodeB Cell Administration status: unlocked, locked, shuttingdown

Operating status: enable, disable

eNodeB License status: Default, Demo, Normal,Protected, Emergency

Operating status: Starting, Software ready,Software not ready

Board Administration status: unlocked, locked, shuttingdown

Operating status: enable, disable

Availability status: normal, fault, uninstalled,un-configured, inconsistent, power-off

Usage status: idle, active, busy

Standby status: active, standby

WOFD-021000 Local Device Panel

Availability


Description

The device panel provided by the LMT of an NE displays the subracks, boards, configuration,and alarms of NEs on the GUI. On the boards, users can perform common operations such as

querying board statuses and resetting boards.

After starting the LMT of a specified NE in the M2000 topology view and starting the device panel, users can check the hardware status in the topology view or perform routine maintenanceof devices through shortcut menus.

To ensure security of data transmission between LMTs and NEs, LMTs based on the iView platform support SSL-encrypted transmission, and web LMTs support HTTPS-encryptedtransmission.


33/80





31

Dependency

This feature is implemented on the LMT. If the NE LMT is based on the iView platform, usersmust install the NE LMT on the M2000 client before using this feature. If the NE supports aWeb LMT, users do not need to install the NE LMT.

WOFD-022300 Centralized Device Panel

Availability


Summary

The M2000 provides the centralized device panel function and graphically displays subracks, boards, and the status and alarm information about subracks and boards. On the device panel,

users can perform common operations such as querying board states and restarting boards.

Benefits

The graphical display of devices allows users to maintain NEs easily and improves the usabilityof the M2000. By using this feature, users can directly view the hardware status of devices and perform common operations on the device panel.

Description

The M2000 implements centralized device panel management, which allows users to switchdevice panels of different NEs on the same GUI.

The device panel graphically displays the physical locations and states of racks, subracks, and boards. In addition, the states can be updated in real time. The M2000 displays the following board states: null, unknown, uninstalled, unconfigured, inconsistent, starting up, power off, blocked normal, blocked faulty, faulty, active normal, standby normal, and abnormalactive/standby. The states are identified in different colors on the device panel. In addition, onthe device panel, users can learn about the running status of boards according to the indicatorsof board states, fault bar, and the indicators of active alarms.

Users can right-click a board and perform common O&M operations through shortcut menus,such as querying board status, alarms, CPU usage, inventory information, and resetting or blocking the board. Board status varies according to the board type, and shortcut menussupported by boards are slightly different.

The device panel provides shortcut menus for common maintenance, such as querying boardstatus, alarms, CPU usage, and inventory data, and resetting or blocking boards. The shortcutmenus vary according to board states.

If a BTS is configured with RRUs, the M2000 displays the physical topology relationships between RRUs and between RRU and BBU ports by displaying the RRU device panel, RRUchains, and CPRI connections. The physical network topology can be updated in real time,showing the connection status and the device status on the topology.

Enhancement



34/80





32

Querying the inventory data on boards through the device panel

Displaying the topology of CPRIs


Displaying the device panel of the RRU

Dependency

This feature applies to eRAN1.0 and later versions.

WOFD-022000 Configuration Report

Availability


Summary

The M2000 provides the NE report, core network resource report, NE statistics report, linkreport, and RAN configuration report. Users can view the basic NE information, port resourceinformation, NE version information, link information, base station configuration information,and cell configuration information presented by these reports through GUI. Users can also savethe reports to a local PC or print the reports.

In addition, the M2000 can periodically generate the configuration reports through centralizedtask management.

BenefitsThe M2000 provides various configuration reports according to configuration data types andO&M scenarios. Therefore, users can easily learn about the NE information, port resourceinformation, link information, base station configuration information, and cell configurationinformation. This improves O&M efficiency.

Description

The M2000 provides reports such as the RAN configuration report. Users can view thesereports through the GUI. In addition, users can save the reports as XLS, CSV, TXT, PDF, orHTML files. They can also print the reports.

The configuration reports can be generated periodically through centralized task management.Users can set the report generation period in the unit of day.

The data in each report is as follows:

NE report

An NE report contains basic NE information, such as NE names, types, versions, IPaddresses, physical locations, vendors, districts, maintenance areas, status of theconnection with the M2000, and capacity. The report also provides the total number of NEs and the number of disconnected NEs by NE type.

NE statistics report


35/80





33

An NE statistics report allows users to query the version information about multiple NEs.The version information includes the NE type, NE versions involved in each type of NE,and number of NEs corresponding to each version.

Core network resource report

A core network resource report allows users to query the resource information about the ports and CPUs information.

All the NEs support the NE report and NE statistics report.

Enhancement

The following function is added to M2000 V200R012C00:

Information about NE maintenance areas and connection status with the M2000 are added toan NE report.


NE report, core network resource report, NE statistics report. Various configuration reports can be automatically generated by using centralized task

management.

WOFD-070200 Centralized MML for Configuration

Availability


Summary

This feature allows users to concurrently send MML commands and MML scripts to multiple NEs on the M2000 client.

Description

The centralized command line feature allows users to send MML commands to multiple NEs ofthe same type on the M2000 client. The CLI provides a command navigation tree organized byfunction, supports the predictive input technique and help information, and records executedcommands. It also allows users to filter, search for, and sort NEs. Before executing a commandthat may have severe negative effects, the M2000 displays a message, informing users of the possible execution results. The M2000 executes the command only after users confirm the

operation.

The M2000 displays the execution results of MML commands on a GUI in real time. It also provides a result redirection function so that users can directly save the command executionresults in a file.

MML commands can be processed in batches. To implement this, users edit the MMLcommands to be executed in MML scripts, import the scripts to the M2000, and create acentralized task to deliver the scripts to NEs. After a script is executed, the M2000 providesstatistics about the execution, including the number of successfully executed MML commands,number of unsuccessfully executed MML commands, and list of unsuccessfully executed MMLcommands.


36/80





34

The M2000 centrally manages and schedules script tasks by using the feature WOFD-071200Centralized Task Manager. When creating a task, users need to specify a script and set theexecution mode (immediate execution or scheduled execution), running mode, redirection ofthe script result and NEs. According to the preset time, the M2000 sends the MML commandsin sequence in the script to the selected NE or multiple NEs of the same type. If required, user

can cancel the task during its execution.

Enhancement

Documents

IManager M2000 V200R013 Basic Feature Description(ELTE2.1)