BNG THEO DI S THAY I CA TI LIU

VIETTEL TANZANIA LIMITEDCode:

GUIDELINES FOR MONITORING HUAWEI RNC, NODEBEffective date: .../..../...

Once issued: 01

Page: 3/16

TRACKING SHEET MODIFICATION

No.HomeAmendmentsEffective date

CompilationCheckApproval

Signature

Table of Contents

31.Purpose

32.Scope of Application

32.1.The system applies

32.2.The application

32.3.Subjects of application

33.Reference

34.Abbreviations

35.Monitoring system alarms on Huawei RNC

35.1.Login to U2000 client

45.2.U2000client GUI (application style)

45.2.1.Fault Management

45.2.2.Topology Management

45.2.3.Configuration Management

55.2.4.Performance Management

55.2.5.Software Management

55.2.6.System Management

65.2.7.OSS User Management

65.2.8.Trace and Maintenance

65.2.9.SON

65.2.10.CME

65.2.11.Performance Report Management

65.2.12.IMS&NGN Service Management

65.2.13.Core Network Pool Management

65.2.14.Core Network Dual Homing Management

65.2.15.Signaling Network Service Management

75.3.Basic knowledge of monitoring alarms

75.3.1.Alarm management

85.3.2.Alarm severity

85.3.3.Alarm status

95.4.Alarm Panel

95.5.Browsing Current Alarms

115.6.Setting Display of the Filter Dialog Box for Alarms

115.7.Synchronizing NE Alarms Manually

115.8.Setting Maintenance Regions

125.9.Monitoring Alarms by Using the NE Monitoring List

125.10.Setting Columns to Be Displayed in an Alarm/EventWindow

135.11.Alarm types

145.12.Alarm reporting procedure

155.13.Recording Alarm or Event Handling Experience

166.Profile

1. Purpose

This document guides all staff of NOC at the time of implementation to see the overall status of the current system and directed to promptly remedy the error (if any).

2. Scope of Application

2.1. The system applies

This guide applies to the RNC, NodeB of Huaweis equipment at Viettel Tanzania Ltd.

2.2. The application

Done in shifts.2.3. Subjects of application

The staffs are directly at NOC department.3. Reference

Library of Huawei HedexLite software.4. Abbreviations

NOC: Network Operations CenterRNC: Radio Network Controller

NE: Network Equipment

PRS: Performance Report System

CME: Configuration Management Express

SON: Self Organizing Network

NGN: Next-generation Network

IMS: IP Multimedia Subsystem5. Monitoring system alarms on Huawei RNC5.1. Login to U2000 clientTo be able to monitor U20000 must be logged into the system. Login by using the given username and password:USER NAME

PASSWORD

5.2. U2000client GUI (application style)The figure below shows the GUI displayed when you log in to the U2000 client.

Figure 1: Graphic User Interface of U2000To monitor the system section Right-click an application to browse all functions of the application listed on the shortcut menu. Choose a function to open the main window of the function: 5.2.1. Fault Management

Provide guidance to fault monitoring, fault localization, and troubleshooting for the entire network.

5.2.2. Topology Management

Provide the topology and real-time running status of the network and the shortcut menus for important functions.

5.2.3. Configuration Management

Allow users to synchronize and query NE configuration data, and provide configuration reports.

5.2.4. Performance Management

Provides functions such as set NE performance measurement and query performance result.

5.2.5. Software Management

Provides functions such as query, transfer, and back up NE files, and provide NE upgrade and NE license management.

5.2.6. System Management

Provides functions such as monitor and manageU2000system resources. These applications help ensure proper running of theU2000and improve work efficiency. The system management applications are classified into the following types:

System resource monitoring

You can monitor theU2000server to obtain information about the services, processes, hard disks, database, resource status, and components of theU2000server.

Information settings

You can set log forwarding servers to ensure normal communication between theU2000and third-party servers. You can also set management capacity alarms to ensure normal communication between theU2000and NEs.

Management of scheduled tasks

In the ITM, you can browse information, such as task status and progress, about system and user scheduled tasks, and change task status by performing such operations as running, suspending, and running tasks. If you haveTask Managementrights, you can create, modify, and delete user scheduled tasks.

U2000licensemanagement

By managing theU2000license, you can checklicensefile information on theU2000server and replacelicensefiles that are to expire. The management preventslicenseexpiration from affecting services.

Script-based secondary development platform

Using theiSStar-based secondary development platform, you can write high-level script language (HSL) scripts for repetitive and complicated routine maintenance operations, and use the application management platform to manage these scripts. In this way, theiSStarimplements automatic maintenance, therefore reducing repetitive work and improving work efficiency.

5.2.7. OSS User Management

Provides functions such as browse and configure data related to the security and logs of the OSS and NEs.

5.2.8. Trace and Maintenance

Provide signaling trace FARS, CCE client login, and common NE maintenance functions such as device panel, inventory data, MML command, NE health check and System Management Tool.

5.2.9. SON

Provide auto deployment, self-planning, self-optimization, and BTS power saving.

5.2.10. CME

Provide quick RAN data configuration. CME applications can be viewed only after you install the CME application software.

5.2.11. Performance Report Management

Provide visualize the performance and resources of the MBB network and help to operate and maintain the MBB network. PRS applications can be viewed only after you install the PRS application software.

5.2.12. IMS&NGN Service Management

Provides functions such as IMS subscriber information query, NGN service configuration and provisioning, NGN line testing, NGN bearer network QoS testing, and NGN media gateway port testing.

5.2.13. Core Network Pool Management

Provides functions such as Pool data check, real-time monitoring, subscriber migration, and subscriber search.

5.2.14. Core Network Dual Homing Management

Provides functions such as synchronization, consistency check, and batch configuration of data on dual-homing NEs.

5.2.15. Signaling Network Service Management

Provides functions such as signaling network topology management, resource status statistics collection, port check, and backup data management.5.3. Basic knowledge of monitoring alarms To monitor alarms you need to be familiar with certain knowledge, such as alarm management, alarm severity, alarm status, and alarm report procedure. This helps you to better monitor the alarms generated on the network.5.3.1. Alarm managementAlarm management involves alarm display and statistics, visual alarm notification, alarm acknowledgement and synchronization.

Alarm display status The Monitoring system receives the NEs (Network elements) alarms in real time. It provides various methods of alarm display and statistics.

Alarm display

Alarm display involves alarm board output and alarm query a. Alarm board collect statistics of the alarm on the managed object by alarm severities and states with templates. Working as the monitoring panel, it provides the fault status of the entire system.

b. Alarm Query is to query a current alarm `fault, history fault alarms, event alarms, filtered fault alarms, and filtered event alarms. The Monitoring system can display fault alarms and event alarms in a window by different alarm status. Alarm statistics

The Monitoring system can collect statistics on fault alarms and event alarms according to the preset statistical conditions. The statistical conditions include alarm name, alarm severity, alarm type, alarm raised time, and alarm status, and can be combinations of these items. Alarm NotificationMonitoring systems provides means of alarm notification through alarm Box and optional on the Audio speaker.

Alarm acknowledgementMonitoring systems provide manual and automatic acknowledgement of alarms. Alarm synchronization

The monitoring system supports synchronization of network |elements; this can be done manually through the system.5.3.2. Alarm severityThe Monitoring system defines the alarm to be four severities (Critical, Major, minor and warning) according to the severity of the alarm. You can adopt corresponding processing strategy for different alarm severities and redefine the alarm severities. The alarm severities is described as follows (Refer figure 3); Critical - the device may be no longer available. The fault must be removed immediately.

Major - The quality of service (QoS) of the device or resource decreases greatly. Proper measures must be taken to recover the service.

Minor - The QoS of the device or resource decreases slightly. Proper measures must be taken or further observation need to be done to avoid more severe faults.

Warning - The QoS of the device or resource may be affected. Proper measures must be taken.

5.3.3. Alarm statusThe monitoring system divides the alarm into different states according to whether the alarm is confirmed or cleared. You can adopt corresponding processing measures for alarms of different states.

Alarm status

The status of an event alarm involves: unacknowledged and acknowledged.

The status of a fault alarm involves: unacknowledged and uncleared, acknowledged and uncleared, unacknowledged and cleared, and acknowledged and cleared.

Condition of changing alarm statusThe certain condition triggered the change of the alarm status.

Clear an alarm: when the condition that causes a fault alarm is removed, the device recovers to its normal state; the device reports a cleared alarm to the Monitoring system. The source alarms are cleared. You can also clear an alarm manually though not advised to do so.

Acknowledged alarm: if an alarm is acknowledged, it is processed. You can unacknowledged an acknowledged alarm.

Alarm status conversionThe figure below shows the model of the fault alarm status conversion.

Figure 2: Model of alarm status conversionNote: The acknowledged and cleared alarms are history alarms. The fault alarms in other status are current alarms. That is, the unacknowledged and uncleared, acknowledged and uncleared, unacknowledged and cleared fault alarms are current alarms.

5.4. Alarm Panel

This panel is under the Fault management part of the GUI in the U2000. ChooseMonitor>Display Alarm Panel(traditional style); alternatively, double-clickFault Managementin Application Centerand chooseBrowse Alarm>Display Alarm Panel(application style), or clickon theU2000client to open the alarm panel. Click the alarm panel next toOption.

Figure 3: Alarm panel5.5. Browsing Current Alarms

Before you browse alarms reported by NEs to theU2000, theU2000fault processifms_agentis enabled. You can chooseMonitor>System Monitor>Browser(traditional style); alternatively, double-clickSystem Managementin Application Centerand chooseSystem>System Monitor>Browser(application style)on the integrated client to view the running status of the fault process on theProcess Monitortab of theSystem Monitor Browserwindow.

Figure 4: Browse current alarms windowTable 1: Components of the Browse Current Alarms windowNo.NameDescription

1Alarm listBased on configured filter criteria, this area lists alarms that you need to handle. You can select one or more alarms, right-click them, and choose an operation item from the shortcut menu. For example, you can acknowledge, clear, or mask the alarms.

2Expanded alarm areaThis area displays commonly used alarm information, which includes alarm details, troubleshooting suggestions, root alarm information, correlative alarm information, associated alarms, and alarm logs. By default, only theDetailstab is displayed in this area. You can open theRoot Alarms,Correlative Alarms,Associated Alarms, andAlarm Logstabs by right-clicking selected alarms and choosingDisplay>Tab namefrom the shortcut menu.

3Configuration areaThis area enables you to the alarm display and provides the buttonsTemplate,Filter,Refresh,Acknowledge, andClear.

4Statistics areaThis area displays alarm statistics.

5.6. Setting Display of the Filter Dialog Box for Alarms

You can specify whether the Filter dialog box is displayed to facilitate alarm and event browsing or querying.

Procedure:1. ChooseSystem>Preferences orFile>Preferences(application style).

2. In thePreferencesdialog box, expand theAlarm Local Terminal Settingsnode in the navigation tree and chooseAlarm/Event Filtering.

3. In theAlarm/Event Filteringarea, specify whether to automatically display theFilterdialog box.

4. ClickOK.5.7. Synchronizing NE Alarms Manually

Due to problems such as network interruptions, the alarm data on theU2000may be inconsistent with that on NEs. To obtain the latest alarm status of the NEs, you can manually synchronize the alarm data of selected NEs to theU2000to keep data consistency.

Procedure:1. ChooseMonitor>Synchronize NE Alarms(traditional style); alternatively, double-clickFault ManagementinApplication Centerand chooseBrowse Alarm>Synchronize NE Alarms(application style).

2. In theSynchronize NE Alarmsdialog box, set the NEs whose alarms you want to synchronize and clickOK.

3. In theConfirmdialog box, clickYes.5.8. Setting Maintenance Regions

By setting maintenance regions, you can divide NEs based on maintenance regions. Values ofDetailsfor alarms contain information about maintenance regions where the NEs that report the alarms are located. Maintenance region information includes NE maintenance information, for example, NE locations or personnel who maintain the NEs.Context

Each NE belongs to only one maintenance region.

Maintenance regions cannot be nested.

The user can add only visible NEs to maintenance regions.

Procedure:ChooseMaintenance>Maintenance Region Management(traditional style) ordouble-clickTopology ViewinApplication Centerand chooseFile>Maintenance Region Management(application style).5.9. Monitoring Alarms by Using the NE Monitoring List

By monitoring the NE status, you can learn about the names, types, severities, and connection status of the NEs managed by theU2000. This information helps you learn the running status of the NEs, and identify and rectify faults in a timely manner.Procedure:1. ChooseSystem>NE Monitor(traditional style) ordouble-clickConfigurationinApplication Centerand chooseBrowser>NE Monitor(application style).

NOTE: In theNE Monitorwindow, the details about the NEs managed by theU2000are displayed.

2. Right-click an NE and chooseLocate in Topologyfrom the shortcut menu to locate the NE in the topology view.5.10. Setting Columns to Be Displayed in an Alarm/EventWindow

In the Monitoring systems Alarms are classified as fault and events according to the effect of the alarm to the system. The difference between fault and events alarms is shown on the table below.Table 2: Difference between fault and events alarmsAlarm CategoryDefinitionRelated ConceptImpactHandlingRecommend-ation

Fault alarmA notification that the system provides when it detects a fault.A fault is a physical or logical factor that causes the system to fail.

For example, Central Processing Unit (CPU) busy, hard disk failure, or network cable disconnection.The system probably cannot work properly.Can be cleared.Clear the alarm to restore the system to normal.

Event alarmA notification that the system provides when it detects an event.An event is a situation of the managed object.

For example, succeeded in periodic export of operation logs.Events occur all the time. They have no negative impacts on the system.Cannot be cleared, but can be acknowledged and unacknowledged.You do not have to handle the event.

In the alarmor eventquery window, you can display the information only about the preset fields of alarmsor eventsby setting the columns to be displayed.

Procedure:1. ChooseMonitor>Browse Current Alarms(traditional style); alternatively, double-clickFault ManagementinApplication Centerand chooseBrowse Alarm>Browse Current Alarms(application style), or click theon the toolbar.

2. In theFilterdialog box, set filter criteria, and clickOK.

3. In theBrowse Current Alarmswindow, right-click the table header or right click in a blank space at the bottom of the table, and chooseConfigure Columnsfrom the shortcut menu.

4. In theConfigure Columnsdialog box, set the fields to be displayed and select theTake effect for the current window and the current alarm windows to be openedorTake effect for the current windowonlycheck box as required.

5. ClickOK.

5.11. Alarm typesBased on the different alarm resources alarms can be classified into 11 types such as power system alarm and environment system alarm.

Table 3: Types of alarmsAlarm typeDescription

Power system alarmA power system alarm is raised by the power supply.

Environment system alarmAn environment system alarm is an alarm about the environment of the equipment room, such as the temperature, humidity, or gate.

Signaling system alarmA signaling system alarm is an alarm about the signaling system, such as No. 7 signaling.

Trunk system alarmA trunk system alarm is an alarm about the trunk system, such as E1, STM-1 optical or electrical relay.

Hardware system alarmA hardware system alarm is an alarm about a board device, such as clock or CPU.

Software alarmA software system alarm is an alarm about the software.

Running system alarmA running system alarm is an alarm about the Monitoring system running.

Communication system alarmA communication system alarm is an alarm about the communication system.

QoS alarmA QoS alarm is an alarm about the QoS.

Processing error alarmProcessing error alarms are alarms about other exceptions that are not described here.

Internal alarmAn internal alarm is raised by the Monitoring system. Except such alarms, other types of alarms are all external alarms reported by the devices.

5.12. Alarm reporting procedureIt describes the process from generating the fault to receiving the alarm notification by the user.

Figure 5: Flow diagram of alarm reporting procedureThe following is the description of the flow of the figure above.

1. Reporting an alarm

When a device raises an alarm, it sends the alarm to the monitoring system by the Man-Machine Language (MML) protocol or Simple Network Management Protocol (SNMP).

2. Masking alarms

The Monitoring system masks alarms based on the mask condition set by users. The alarms that match the condition are masked.

3. Redefining the alarm severity

The Monitoring systems redefine the alarm severities based on the redefinition conditions set by users.

4. Analyzing alarm correlation

The Monitoring system analyzes the alarm correlation based on the correlation rule and shield the repetitive or non-root alarms.

5. Saving alarms

After processing, the Monitoring system writes the alarms into the alarm database.

6. Notifying the user of alarms

The Monitoring sends the alarm notifications to users based on the alarm notification rules set by users.5.13. Recording Alarm or Event Handling Experience

You can record alarm or event handling experience to the experience library. When a similar alarm or event occurs, you can refer to the experience library to handle the alarm or event.Procedure:1. ChooseMonitor>Alarm Settings>Experience(traditional style); alternatively, double-clickFault ManagementinApplication Centerand chooseAlarm Settings>Experience(application style).

2. In theExperiencewindow, clickRange. In theSearch Rangedialog box, specify a search range and click OK.

3. Enter an alarm or event name, default alarm or event group name, or handling experience in theFilter by nametext box.

In theAlarm/Event Namenavigation tree, alarm or event names with the specified keyword are listed.

4. In theAlarm/Event Namenavigation tree, select an alarm or event name, and then clickModify.

NOTE:1. You can select an alarm or event or double-click in a blank area in theExperiencearea to open theExperiencedialog box.

2. Clickto collapse all objects.

3. Click one or more of the icons,, , andto classify alarms or events and improve the speed of locating alarm or event names in the navigation tree.

5. In theExperiencedialog box, enter alarm or event handling experience. ClickOK.

6. Profile

No.Name ProfileResponsibilities saveTime savedCancel

1Guidelines monitoring Huawei RNC, NodeBNOC Department1 Year