imanager M2000 V200R012 Basic Feature Description(eWBB2.1) HUAWEI TECHNOLOGIES CO., LTD. Issue 02 Date

Transcription

1 (ewbb2.1) Issue 02 Date HUAWEI TECHNOLOGIES CO., LTD.

2 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 commercial contract made between Huawei and the customer. All or partial products, services and features described in this document may not be within the purchased scope or the usage scope. Unless otherwise agreed by the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied. Huawei Technologies Co., Ltd. Address: Website: Huawei Industrial Base Bantian, Longgang Shenzhen People's Republic of China support@huawei.com

3 Contents 1 Overview Basic Features (WOFD ) Platform Fault Management Configuration Management Performance Management Security Management Topology Management NE License Management Hardware and Software Management Network Monitoring and Analysis FARS Base Station Commissioning Management Acronyms and Abbreviations

4 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 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 2

5 2 Basic Features (WOFD ) 2.1 Platform WOFD Basic M2000 Service Summary Benefits This feature was introduced in M2000 V200R003. 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. 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's working efficiency, reduce operation and maintenance (O&M) costs, and therefore minimize telecom operators' investments. This feature provides the following functions: Hardware and software platforms For details about the hardware and software platforms, see imanager M2000 V200R012 Product. 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. 3

6 Online help imanager M2000 V200R012 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: of M2000 functions such as fault, configuration, performance, security, and topology management, and how to implement these functions 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, performance counters, 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. 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. When a fault occurs on the hardware, the M2000 generates an alarm. 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 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 the M2000 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 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 4

7 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 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. 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 The following functions are added to M2000 V200R009: 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 The following functions are added to M2000 V200R008: 5

8 Collecting M2000 performance statistics Installing and automatically upgrading M2000 clients on a web browser Loading M2000 mediation versions online WOFD File Transfer Management Summary Benefits Enhancement This feature was introduced in M2000 V200R003. imanager M2000 V200R012 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 Encrypted Transmission. 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. 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 transfer 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. The function of customizing FTP and FTPS service ports is added to M2000 V200R012C00. 6

9 Dependency None. WOFD Application Management Platform Summary Benefits This feature was introduced in M2000 V200R008. 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. 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. 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. 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 7

10 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, resume a task, delete tasks in batches, and check task execution results. WOFD Local Maintenance Agent This feature was introduced in M2000 V200R002. 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 Supporting Network Time Synchronization Summary This feature was introduced in M2000 V200R002. 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. If the NTP server provided by a customer 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 customer 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 8

11 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. Customer 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 synchronizes time with the time of the upper-layer NTP server in encrypted authentication mode. After NEs send a time synchronization request to the M2000, the M2000 allows NEs to synchronize time with the M2000 server time in encrypted authentication mode. This feature requires customer to provide a top-level clock source server. If customer requires 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 Network Time Synchronization Solution. Enhancement The following functions are added to M2000 V200R011C00: The M2000 generates an alarm after detecting any exceptions in the NTP service or a synchronization 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 Daylight Saving Time and Management of Multiple Time Zones This feature was introduced in M2000 V200R003. 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 browsing window. If the area where an NE is located is using DST, the M2000 displays DST in MML messages. WOFD Centralized Task Manager This feature was introduced in M2000 V200R005. 9

12 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 Dependency None 10

13 WOFD Script Trigger Enhancement This feature was introduced in M2000 V200R006. 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 The following function is added to M2000 V200R008: This feature can be used for triggering the HSL script. WOFD Auto IP Address Allocation Service for BTS This feature was introduced in M2000 V200R008. 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 BSs 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). 11

14 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 The following function is added to M2000 V200R011C01: Allowing users to filter IP address assignment records by fields such as BTS ID, BTS name, and ESN WOFD User Profile Management This feature was introduced in M2000 V200R008. 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 Disk Redundant Backup This feature was introduced in M2000 V200R002. The local disks of the M2000 support the RAID 1 backup mode (1+1 disk mirroring). WOFD M2000 Data Backup and Restore This feature was introduced in M2000 V200R

15 Summary The M2000 provides the backup and restore solutions for M2000 application data including M2000 application and service data. Benefits This feature brings about the following benefits: The M2000 provides cost-efficient backup and restore solutions for the O&M network. This feature provides the following functions: 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. 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 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 the database and applications, users need to run the restore script. WOFD NE Data Backup and Restore Summary This feature was introduced in M2000 V200R002. 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. 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 by using the feature WOFD Centralized Task Manager. The M2000 backs up the data based on the preset period and time. 13

16 Data must be restored manually because it may lead to NE restart. After users start restoring 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 Automatic File Upload Summary This feature was introduced in M2000 V200R008. 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 Encrypted Transmission. Benefits The M2000 sets up and manages the transmission connection. This feature provides the following functions: 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-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 (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 files. Alternatively, the M2000 can create a directory for saving the files. The directory structure is 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 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. 14

17 imanager M2000 V200R012 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 system because the FTP service of a third-party system is not 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 cannot work independently: WOFD NE License Management 2.2 Fault Management WOFD Centralized Storage of Alarm Information This feature was introduced in M2000 V200R002. 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. 15

18 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 Alarm Viewer Summary Benefits This feature was introduced in M2000 V200R002. 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 browsing window. Users can also set the uncleared alarms to be highlighted. This feature brings about the following 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. 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 display alarm logs, event logs, and alarm lists. Users can set filter criteria in each browsing 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 types, NEs, MOs, MBTSs, object groups and topology maintenance areas, 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. 16

19 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 imanager M2000 V200R012 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 browsing 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 browsing 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 browsing window as TXT, HTML, PDF, XLS, and CSV files or print the information. Users can save or print part of or all alarms. 17

20 Customizing alarm/event display styles imanager M2000 V200R012 The M2000 allows users to customize the following elements in the alarm browsing 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 browsing window, users can sort alarms/events according to one or more alarm/event attributes. Alarms and events of different severities are identified with different colors. Users can modify 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 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 following functions are added to M2000 V200R009: 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 Real-Time Alarm Notification Summary Benefits This feature was introduced in M2000 V200R002. 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. 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. 18

21 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 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 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 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 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 Alarm Viewer. WOFD Automatic Alarm Retrieval This feature was introduced in M2000 V200R002. 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. 19

22 WOFD Alarm Synchronization This feature was introduced in M2000 V200R002. 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. 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 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 Alarm Pre-Processing on M2000 Summary Benefits This feature was introduced in M2000 V200R002. 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. 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. This feature provides the following functions: Masking alarms and events After receiving alarms or events, the M2000 checks and discards the alarms or events that meet 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, 20

23 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 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. 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. 21

24 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. 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 following functions are added to M2000 V200R011C01: 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 following functions are added to M2000 V200R011C00: The M2000 generates a toggling alarm in analyzing alarm or event occurrence frequency. The following functions are added to M2000 V200R010: The M2000 supports redefinition of alarm severities based on time segments. The following functions are added to M2000 V200R009: 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 Alarm Severity Redefinition on NE This feature was introduced in M2000 V200R

25 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 Alarm Masking on NE This feature was introduced in M2000 V200R002. 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. The M2000 masks alarms and events according to alarm/event names and severities. When setting 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. 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 Environment Alarm Setting Summary Benefits This feature was introduced in M2000 V200R002. To monitor NE environments, the M2000 supports the settings of environment alarms. 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. 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. 23