ran routine maintenance guide(v900r011c00_04)

7/27/2019 RAN Routine Maintenance Guide(V900R011C00_04)

http://slidepdf.com/reader/full/ran-routine-maintenance-guidev900r011c0004 1/60

RAN

V900R011C00

Routine Maintenance Guide

Issue 04

Date 2010-05-31

HUAWEI TECHNOLOGIES CO., LTD.



Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written

consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the

customer. All or part of the products, services and features described in this document may not be within the

purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representations

of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute the 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]

Issue 04 (2010-05-31) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com/



About This Document

Purpose

The RAN Routine Maintenance Guide provides suggestions for telecom operators to perform

routine maintenance.

This document provides guidelines for daily, weekly, and monthly maintenance of the RAN and

provides tables for recording the maintenance results.

Product Version

The following table lists the product versions related to this document.

Product Name Product Version

BSC6900 V900R011C00

NodeB V100R011

NodeB V200R011

Intended Audience

This document is intended for:

l Shift operators

l System engineers

Organization

1 Changes in RAN Routine Maintenance Guide

This chapter provides the changes in the RAN Routine Maintenance Guide.

2 Introduction to RAN Routine Maintenance

RAN

Routine Maintenance Guide About This Document



iii



The purpose of RAN routine maintenance is to ensure the reliability, stability, and optimum

operating status of the BSC6900 and NodeB. In addition, routine maintenance can prevent

potential accidents, identify and solve problems in time, and improve equipment reliability.

3 Daily RAN Maintenance Guidelines

This chapter provides guidelines for performing the daily maintenance tasks.

4 Weekly RAN Maintenance Guidelines

This chapter provides guidelines for performing the weekly maintenance tasks.

5 Monthly RAN Maintenance Guidelines

This chapter provides guidelines for performing the monthly maintenance tasks.

6 RAN Routine Maintenance Record

The Routine Maintenance Record is used to record the information about the equipment

performance during the maintenance.

Conventions

Symbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk, which if not

avoided,will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if not

avoided,could result in equipment damage, data loss,

performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or save

time.

Provides additional information to emphasize or supplement

important points of the main text.

General Conventions

The general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.

About This Document

RAN


iv Huawei Proprietary and Confidential


Issue 04 (2010-05-31)




Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in

Courier New.

Command Conventions

The command conventions that may be found in this document are defined as follows.


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all

items can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.

GUI Conventions

The GUI conventions that may be found in this document are defined as follows.


Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK .

> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.

Keyboard Operations

The keyboard operations that may be found in this document are defined as follows.

RAN

Routine Maintenance Guide About This Document



v



Format Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt

+A means the three keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.

Mouse Operations

The mouse operations that may be found in this document are defined as follows.

Action Description

Click Select and release the primary mouse button without moving

the pointer.

Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.

Drag Press and hold the primary mouse button and move the

pointer to a certain position.

About This Document

RAN


vi Huawei Proprietary and Confidential


Issue 04 (2010-05-31)



Contents

About This Document...................................................................................................................iii

1 Changes in RAN Routine Maintenance Guide....................................................................1-1

2 Introduction to RAN Routine Maintenance.........................................................................2-1

2.1 Scope...............................................................................................................................................................2-2

2.2 Tools................................................................................................................................................................2-2

2.3 Tasks and Intervals of RAN Routine Maintenance.........................................................................................2-2

2.3.1 Daily Maintenance Tasks.......................................................................................................................2-3

2.3.2 Weekly Maintenance Tasks...................................................................................................................2-3

2.3.3 Monthly Maintenance Tasks..................................................................................................................2-4

3 Daily RAN Maintenance Guidelines.....................................................................................3-1

3.1 Monitoring R AN Alarms................................................................................................................................3-2

3.1.1 Monitor ing RAN Fault Alarms..............................................................................................................3-2

3.1.2 Monitoring RAN Event Alarms.............................................................................................................3-3

3.1.3 Collecting RAN Alarm Statistics...........................................................................................................3-4

3.2 Monitoring the RAN Performance..................................................................................................................3-4

3.2.1 Monitor ing the Key Performance Counters...........................................................................................3-5

3.2.2 Saving the Performance Measurement Results......................................................................................3-6

3.3 Monitoring the Cell Status and Cell Resources..............................................................................................3-7

3.3.1 Monitor ing the Cell Status.....................................................................................................................3-7

3.3.2 Monitor ing the Cell Resources...............................................................................................................3-8

3.4 Querying and Saving the BSC6900 Operation Logs on the M2000...............................................................3-9

3.5 Querying and Saving other Logs of the BSC6900........................................................................................3-11

3.6 Querying and Saving NodeB Operation Logs...............................................................................................3-12

3.7 Querying and Saving NodeB other logs........................................................................................................3-12

3.8 Checking the Automatic Backup Function of NEs.......................................................................................3-13

4 Weekly RAN Maintenance Guidelines.................................................................................4-1

4.1 Checking the Running Status of OMU...........................................................................................................4-3

4.2 Checking the BSC6900 Board Status..............................................................................................................4-4

4.3 Checking the NodeB Board Status..................................................................................................................4-5

4.4 Checking the BSC6900 Clock.........................................................................................................................4-6

4.5 Checking the State of the NodeB Clock..........................................................................................................4-7

4.6 Backing Up and Restoring the RAN System Data..........................................................................................4-8

RAN

Routine Maintenance Guide Contents



vii



4.6.1 Automatically Backing Up the System Data..........................................................................................4-8

4.6.2 Manually Backing Up the System Data.................................................................................................4-9

4.6.3 Manually Restoring the System Data (M2000)....................................................................................4-10

4.6.4 Manually Backing Up and Restoring the System Data on the LMT...................................................4-11

4.7 Analyzing the Performance Measurement Results.......................................................................................4-12

4.8 Collecting History Alarm Statistics...............................................................................................................4-13

4.9 Checking the Communication Between NEs and the M2000 ......................................................................4-14

5 Monthly RAN Maintenance Guidelines...............................................................................5-1

5.1 Analyzing Customer Complaints....................................................................................................................5-2

5.2 Preparing the NE Performance Report............................................................................................................5-2

5.3 Preparing a Performance Report.....................................................................................................................5-4

5.4 Checking the Disk Space on the Terminal System.........................................................................................5-4

5.5 Checking the Maintenance Terminal System for Viruses...............................................................................5-4

6 RAN Routine Maintenance Record........................................................................................6-1

6.1 Daily Maintenance Record..............................................................................................................................6-2

6.2 Weekly Maintenance Record..........................................................................................................................6-3

6.3 Monthly Maintenance Record.........................................................................................................................6-3

Contents

RAN


viii Huawei Proprietary and Confidential


Issue 04 (2010-05-31)



Figures

Figure 3-1 Query NE Operation Logs................................................................................................................3-10

Figure 4-1 NE Backup List.................................................................................................................................. 4-9

Figure 4-2 NE Backup List................................................................................................................................4-11

Figure 4-3 M2000 network topology.................................................................................................................4-14

RAN

Routine Maintenance Guide Figures



ix



Tables

Table 2-1 Daily maintenance tasks.......................................................................................................................2-3

Table 2-2 Weekly maintenance tasks...................................................................................................................2-4

Table 2-3 Monthly maintenance tasks..................................................................................................................2-4

Table 3-1 Expected results of the measurement counters.................................................................................... 3-5

Table 3-2 Measurement counters of cell resources.............................................................................................. 3-8

Table 4-1 Expected result of checking the operating status of the OMU.............................................................4-3

Table 4-2 Expected result of checking the operating status of the service modules of the OMU boards............4-3

Table 5-1 Alarm statistical modes........................................................................................................................5-2

Table 6-1 Daily Maintenance Record...................................................................................................................6-2

Table 6-2 Weekly Maintenance Record...............................................................................................................6-3

Table 6-3 Monthly Maintenance Record..............................................................................................................6-4

RAN

Routine Maintenance Guide Tables



xi



1 Changes in RAN Routine Maintenance

Guide

This chapter provides the changes in the RAN Routine Maintenance Guide.

04 (2010-05-31)

This is the forth commercial release.

Compared with issue 03 (2009-12-05) of V900R011C00, this issue does not include any new

topic.

Compared with issue 03 (2009-12-05) of V900R011C00, this issue incorporates the following

changes:

l The template of change history is updated.

Compared with issue 03 (2009-12-05) of V900R011C00, this issue does not exclude any topic.

03 (2009-12-05)

This is the third commercial release.

Compared with issue 02 (2009-10-30) of V900R011C00, this issue includes the following new

topics:

l 3.8 Checking the Automatic Backup Function of NEs

l 4.6.3 Manually Restoring the System Data (M2000)

l 4.6.4 Manually Backing Up and Restoring the System Data on the LMT



changes:

Topic Change Description

5.4 Checking the Disk Space on the

Terminal System

Add the operation of how to regularly check

and clean up the OMU hard disk.

RAN

Routine Maintenance Guide 1 Changes in RAN Routine Maintenance Guide



1-1



02 (2009-10-30)

This is the second commercial release.

Compared with issue 01 (2009-07-30) of V900R011C00, this issue includes the following new

topics:

l 4.5 Checking the State of the NodeB Clock

l 4.3 Checking the NodeB Board Status

l 4.9 Checking the Communication Between NEs and the M2000

l 5.1 Analyzing Customer Complaints



changes:

Topic Change Description

3.4 Querying and Saving the BSC6900

Operation Logs on the M2000

Add the GUI operation mode.

4.2 Checking the BSC6900 Board Status Add the GUI operation mode.

4.4 Checking the BSC6900 Clock Add the GUI operation mode.

4.4 Checking the BSC6900 Clock Add the GUI operation mode.

01 (2009-07-30)

This is the first commercial release.

1 Changes in RAN Routine Maintenance Guide

RAN


1-2 Huawei Proprietary and Confidential


Issue 04 (2010-05-31)




About This Chapter

The purpose of RAN routine maintenance is to ensure the reliability, stability, and optimum

operating status of the BSC6900 and NodeB. In addition, routine maintenance can prevent

potential accidents, identify and solve problems in time, and improve equipment reliability.

2.1 Scope

RAN routine maintenance is performed at the network management center to ensure the reliable

operation of the BSC6900 and NodeB.

2.2 Tools

The tools for RAN routine maintenance consist of the M2000 client and LMT.

2.3 Tasks and Intervals of RAN Routine Maintenance

Based on the maintenance frequency, routine maintenance is classified into daily, weekly, and

monthly maintenance.

RAN

Routine Maintenance Guide 2 Introduction to RAN Routine Maintenance



2-1



2.1 Scope

RAN routine maintenance is performed at the network management center to ensure the reliable

operation of the BSC6900 and NodeB.

RAN routine maintenance is a process in which the BSC6900 and NodeB are monitored and

maintained. Generally, routine maintenance is performed through the M2000.

RAN routine maintenance does not include the routine maintenance of the M2000 or the site

maintenance.

To perform r outine maintenance on the M2000, see the M2000 Operator Guide.

2.2 Tools

The tools for RAN routine maintenance consist of the M2000 client and LMT.

M2000 Client

The M2000 client is used to monitor multiple NEs simultaneously.

NOTE

When the BSC6900 UMTS Sharing function is applied, the operating support systems (OSSs) of the

telecom operators are connected to the M2000 through the northbound interface. Accordingly, your

permissions are as follows:

l You have no permission to view the configurations, status, alarms, and performance of the cells of

other telecom operators.l You have the permissions to view the configurations, status, alarms, and performance of the common

resources but have no permission to modify them.

l You have the permissions not only to view the configurations, status, alarms, and performance of your

own cells but also to modify them.

LMT

The LMT is used to perform routine maintenance on a single NE.

When the M2000 client detects a fault in an NE, you can log in to the NE through the LMT to

locate, analyze, and rectify the fault.

2.3 Tasks and Intervals of RAN Routine Maintenance

Based on the maintenance frequency, routine maintenance is classified into daily, weekly, and

monthly maintenance.

2.3.1 Daily Maintenance Tasks

This section describes the daily maintenance tasks and provides reference for each task.

2.3.2 Weekly Maintenance Tasks

This section describes the weekly maintenance tasks and provides reference for each task.

2.3.3 Monthly Maintenance Tasks


RAN




Issue 04 (2010-05-31)



This section describes the monthly maintenance tasks and provides reference for each task.

2.3.1 Daily Maintenance Tasks

This section describes the daily maintenance tasks and provides reference for each task.

Table 2-1 lists the daily maintenance tasks and provides reference for each task.

You can add or delete maintenance tasks as required.

Table 2-1 Daily maintenance tasks

SN Task Reference

1 Querying the current fault alarms 3.1.1 Monitoring RAN Fault Alarms

2 Querying the event alarms 3.1.2 Monitoring RAN Event Alarms

3 Collecting the alarm statistics 3.1.3 Collecting RAN Alarm Statistics

4 Querying the performance

measurement results

3.2.1 Monitoring the Key Performance

Counters

5 Saving the performance

measurement results

3.2.2 Saving the Performance

Measurement Results

6 Checking the cell status 3.3.1 Monitoring the Cell Status

7 Checking the cell resources 3.3.2 Monitoring the Cell Resources

8 Querying and Saving the BSC6900

operation logs

3.4 Querying and Saving the BSC6900

Operation Logs on the M2000

9 Querying and Saving other Logs of

the BSC6900

3.5 Querying and Saving other Logs of

the BSC6900

10 Querying and Saving NodeB

Operation Logs

3.6 Querying and Saving NodeB

Operation Logs

11 Querying and Saving NodeB other

logs

3.7 Querying and Saving NodeB other

logs

12 Checking the automatic backup

function of NEs

3.8 Checking the Automatic Backup

Function of NEs

2.3.2 Weekly Maintenance Tasks

This section describes the weekly maintenance tasks and provides reference for each task.

Table 2-2 lists the weekly maintenance tasks and provides reference for each task.


RAN

Routine Maintenance Guide 2 Introduction to RAN Routine Maintenance



2-3



Table 2-2 Weekly maintenance tasks

SN Task Reference

1 Checking the running status of OMU 4.1 Checking the Running Status of

OMU

2 Checking the BSC6900 board status 4.2 Checking the BSC6900 Board

Status

3 Checking the NodeB Board Status 4.3 Checking the NodeB Board

Status

4 Checking the BSC6900 clock 4.4 Checking the BSC6900 Clock

5 Checking the State of the NodeB

Clock

4.5 Checking the State of the NodeB

Clock

6 Backing up and restoring the system

data 4.6 Backing Up and Restoring theRAN System Data

7 Analyzing the performance

measurement results

4.7 Analyzing the Performance

Measurement Results

8 Analyzing the alarm statistics results 4.8 Collecting History Alarm

Statistics

9 Checking the Communication

Between NEs and the M2000

4.9 Checking the Communication

Between NEs and the M2000

2.3.3 Monthly Maintenance Tasks

This section describes the monthly maintenance tasks and provides reference for each task.

Table 2-3 lists the monthly maintenance tasks and provides reference for each task.


Table 2-3 Monthly maintenance tasks

SN Task Reference

1 Analyzing Customer Complaints 5.1 Analyzing Customer Complaints

2 Preparing an equipment operation

report

5.2 Preparing the NE Performance

Report

3 Preparing a performance report 5.3 Preparing a Performance Report

4 Checking the disk space on the

terminal system

5.4 Checking the Disk Space on the

Terminal System

5 Checking the terminal system for

viruses

5.5 Checking the Maintenance

Terminal System for Viruses


RAN




Issue 04 (2010-05-31)



3Daily RAN Maintenance Guidelines

About This Chapter

This chapter provides guidelines for performing the daily maintenance tasks.

3.1 Monitoring RAN Alarms

This section describes how to monitor the current alarms of the BSC6900 and NodeB on the

M2000 client. The alarms consist of fault alarms and event alarms.

3.2 Monitoring the RAN Performance

This section describes how to monitor the performance and save the performance measurement

results of the BSC6900 and NodeB on the M2000 client.

3.3 Monitoring the Cell Status and Cell Resources

This section describes how to monitor the cell status and cell resources on the M2000 client.

3.4 Querying and Saving the BSC6900 Operation Logs on the M2000

The operation logs record the operations that the operation and maintenance personnel perform

on the BSC6900. The operation logs are used to identify faults. It is recommended that you

browse and save the operation logs on the M2000 client every day so that you can check whether

any unauthor ized operations are performed on the equipment.

3.5 Querying and Saving other Logs of the BSC6900

This section describes how to query and save other BSC6900 logs on the M2000 client. Other

logs refer to host logs, OMU logs, database logs, and system event logs.

3.6 Querying and Saving NodeB Operation Logs

The operation information is recorded on the M2000 client. You can query the information on

a visualized interface and save the results in category.

3.7 Querying and Saving NodeB other logs

Other NodeB logs consist of the main board log, operation log, board log, and RTWP routine

test log.

3.8 Checking the Automatic Backup Function of NEs

This section describes how to check the automatic backup function of NEs on the M2000 client.

RAN

Routine Maintenance Guide 3 Daily RAN Maintenance Guidelines



3-1



3.1 Monitoring RAN Alarms

This section describes how to monitor the current alarms of the BSC6900 and NodeB on the

M2000 client. The alarms consist of fault alarms and event alarms.

3.1.1 Monitoring RAN Fault Alarms

This section describes how to monitor the current fault alarms of the BSC6900 and NodeB on

the M2000 client.

3.1.2 Monitoring RAN Event Alarms

This section describes how to monitor the event alarms of the BSC6900 and NodeB on the

M2000 client.

3.1.3 Collecting RAN Alarm Statistics

This section describes how to collect statistics on the alarms of the BSC6900 and NodeB on the

M2000 client based on the alarm severity and alarm type. It also describes how to save the alarmstatistics for easy querying.

3.1.1 Monitoring RAN Fault Alarms

This section describes how to monitor the current fault alarms of the BSC6900 and NodeB on

the M2000 client.

Prerequisite

l You have logged in to the M2000 client and the M2000 client communicates with the related

NEs normally.

l You have the permission to query alarms.

Procedure

Step 1 On the M2000 client, choose Monitor > Query Alarm Logs. The Filter dialog box is displayed.

Step 2 In the Filter dialog box, set the conditions for querying the alarms.

Step 3 Click OK . The current alarms are displayed on the Query Alarm Logs tab page.

NOTE

It is recommended that you set the daily used query conditions as a template as follows:

1. Click Template in the lower left area.

2. Choose Save As... from the shortcut menu.

3. In the displayed dialog box, enter the template name and click OK .

Step 4 Double-click an alarm to view the details in the displayed Details dialog box.

NOTE

When you click an alarm, you can:

l View the details in the Details area.

l Obtain the handling suggestions about the alarm by clicking the link in the Handling Suggestion area.

Step 5 Contact the r elated personnel to acknowledge and handle the alarms not cleared, and analyzeand acknowledge the automatically cleared alarms.


RAN




Issue 04 (2010-05-31)



NOTE

Records of the acknowledged and cleared alarms are not displayed in the window.

Step 6 In the Details dialog box, click Modify to record the fault symptoms, causes, and handling

procedures of the alarm in the Experience area.

Step 7 Repeat Step 4 through Step 6 to handle the alarms in succession until there is no fault alarm on

the current fault alarms tab page.

----End

3.1.2 Monitoring RAN Event Alarms

This section describes how to monitor the event alarms of the BSC6900 and NodeB on the

M2000 client.

Prerequisitel You have logged in to the M2000 client and the M2000 client communicates with the related

NEs normally.

l You have the permission to query alarms.

Procedure

Step 1 On the M2000 client, choose Monitor > Query Event Logs. The Filter dialog box is displayed.

Step 2 In the Filter dialog box, set the conditions for querying the alarms.

Step 3 Click OK . The current alarms are displayed on the Query Event Logs tab page.

NOTE





Step 4 Double-click an alarm to view the details in the displayed Details dialog box.

NOTE

When you click an alarm, you can:

l View the details in the Details area.

l Obtain the handling suggestions about the alarm by clicking the link in the Handling Suggestion area.

Step 5 Contact the related personnel to handle and acknowledge the event alarms.

Step 6 In the Details dialog box, click Modify... to record the fault symptoms, causes, and handling

procedures of the alarm in the Experience area.

Step 7 Repeat Step 4 through Step 6 to handle and acknowledge the alarms in succession.

----End

RAN




3-3



3.1.3 Collecting RAN Alarm Statistics

This section describes how to collect statistics on the alarms of the BSC6900 and NodeB on the

M2000 client based on the alarm severity and alarm type. It also describes how to save the alarm

statistics for easy querying.

Prerequisite


NEs normally.

l You have the permission to collect alarm statistics.

Procedure

Step 1 Log in to the M2000 client. Then, choose Monitor > Alarm Logs Statistics or Monitor >

Event Logs Statistics on the menu bar. The Statistic Filter dialog box is displayed.

Step 2 In the Statistic Filter dialog box, set the conditions for querying the alarms.

Step 3 Click OK . The current alarms are displayed on the Alarm Logs Statistics or Event Logs

Statistics tab page.

NOTE





The statistical results are displayed on the Table and Pie tab pages.

l On the Table tab page, the results are displayed in a table.

l On the Pie tab page, the results are displayed in pie charts.

Step 4 Click Save As... in the lower right area and then select the file type and save path to save the

results of alarm statistics as a file.

l On the Table tab page, the results can be saved as a .txt, .html, .csv, .xls or .pdf file.

l On the Pie tab page, the results can be saved as a .jpg file.

NOTE

It is recommended that you set the daily used collection conditions as a template as follows:

1. Click Template.



Step 5 Record the alarm statistics information in the Daily Maintenance Table.

----End

3.2 Monitoring the RAN Performance

This section describes how to monitor the performance and save the performance measurement

results of the BSC6900 and NodeB on the M2000 client.


RAN




Issue 04 (2010-05-31)



3.2.1 Monitoring the Key Performance Counters

This section describes how to query the measurement results of the performance counters

reported on the M2000 client at an interval of 0.5, 1, or 24 hours so that you can check whether

the BSC6900 and NodeB are functional.

3.2.2 Saving the Performance Measurement ResultsThis section describes how to save the performance measurement results on the M2000 client

in case of data loss.

3.2.1 Monitoring the Key Performance Counters

This section describes how to query the measurement results of the performance counters

reported on the M2000 client at an interval of 0.5, 1, or 24 hours so that you can check whether

the BSC6900 and NodeB are functional.

Prerequisite


NEs normally.

l The measurement objects exist.

l You have the permission to query the measurement results of the performance counters.

Context

Table 3-1 lists the measurement counters.

Table 3-1 Expected results of the measurement counters

Category Measurement Counter Service

Coverage Uplink interference cell ratio All services

Soft handover overhead All services

Accessibility RRC setup success rate All services

RAB setup success rate Voice

VP

PS

PS (HSDPA)

Retainability CS call drop rate Voice

VP

PS call drop rate PS

PS (HSDPA)

Mobility Cell update success rate All services

Soft handover success rate CS and PS

RAN




3-5



Category Measurement Counter Service

Inter-RAT handover success rate Outgoing voice service

handover

Outgoing PS servicehandover

Availability Paging congestion rate All services

DL transmission resource usage All services

UL transmission resource usage All services

NOTE

The performance counter values provided in Table 3-1 are for reference only.

For the definitions of the listed performance counters, see the BSC6900 Performance Counter Reference.

You can specify the daily maintenance standards based on the network status and assessment standards.

Procedure

Step 1 On the M2000 client, choose Performance > Query Result. The Query Result window is

displayed.

Step 2 Click New Query. The Query Result dialog box is displayed.

Step 3 Perform the following steps:

1. Select the object type or the function subset in the left navigation tree.

2. Set parameters on the Object Settings, Counter Settings, and Other Settings tab pages.

3. Click Query. The query result is displayed.

NOTE

The query result can be displayed in three forms: table, line chart, and bar chart. You can specify the form

in the View Type area.

Step 4 Compare the performance counter values with those required for the office. If the values are

inconsistent, contact the corresponding personnel for troubleshooting.

NOTE

If the measurement result contains a Reliability field, the measurement result is valid only when the valueof this field is Reliable.

----End

3.2.2 Saving the Performance Measurement Results

This section describes how to save the performance measurement results on the M2000 client

in case of data loss.

Prerequisite

l

You have logged in to the M2000 client and the M2000 client communicates with the related NEs normally.


RAN




Issue 04 (2010-05-31)



l You have queried the performance measurement results.

l You have the permission to save the performance measurement results.

Procedure

Step 1 Query the performance measurement results by referring to 3.2.1 Monitoring the Key

Performance Counters.

Step 2 In the Query Result window, save the information by clicking Save... in the lower right area or

through the shortcut menu.

l If the results are displayed in a table, right-click the table, choose Export Selected Rows...

or Export All..., and then save the file in .txt, .csv, .html, or .xls format.

l If the results are displayed in a line chart or a bar chart, right-click Save..., and then save the

file in .jpg format.

----End

3.3 Monitoring the Cell Status and Cell ResourcesThis section describes how to monitor the cell status and cell resources on the M2000 client.

3.3.1 Monitoring the Cell Status

This section describes how to monitor the cell status and save the result.

3.3.2 Monitoring the Cell Resources

This section describes how to monitor the cell resources on the M2000 client so that you can

determine the current performance status of the cell.

3.3.1 Monitoring the Cell Status

This section describes how to monitor the cell status and save the result.

Prerequisite


NEs nor mally.

l You have the permission to run MML commands.

Procedure

Step 1 On the M2000 client, choose Maintenance> MML Command. The MML Command window

is displayed.

Step 2 Select the BSC6900 in the left navigation tree. The navigation tree of BSC6900 MML commands

is displayed.

Step 3 Run the MML command DSP UCELL to query the running status of all cells. Here, set the

parameters as follows:

l Set Query type to BYCELL(Query by cell).

l Leave Cell ID empty.

The execution result is displayed. For the meaning of the result, see the Help Information inthe upper right area on the interface.

RAN




3-7



NOTE

Expected result: The operating status of the cells should be Available. If the result is inconsistent, contact

the corresponding personnel for troubleshooting.

Step 4 On the Common Maintenance tab page, right-click and then choose Save As... from the shortcut

menu. Specify the file name and path, and then click Save. The result is saved in the specified

file.

----End

3.3.2 Monitoring the Cell Resources

This section describes how to monitor the cell resources on the M2000 client so that you can

determine the current performance status of the cell.

Prerequisite


NEs normally.


Context

The measurement counters listed in Table 3-2 should be checked to determine the current

performance status of the cell.

Table 3-2 Measurement counters of cell resources

Performance Item

MeasurementCounter

Description Expected Result

Number of

subscribers

in the cell

VS.CellDCHUEs

VS.CellFACHU

Es

Measurement object:

UCELL

Location of the counters:

Measurement related to

Radio Resource Control >

RRC connection setup

measurement per cell

The two counters

measure the number of

subscribers on the

dedicated channels and

on the common channels

respectively.

If the values of both

counters are 0, you can

infer that there are nosubscribers in the cell. A

fault may occur in the

cell.

Measuremen

t of the cell

RTWP

VS.MeanRTWP

VS.MaxRTWP

VS.MinRTWP

Measurement object:

UCELL

Location of the counters:

Measurements related to

Measurement Report >

Cell TX and RX Power

Measurement per cell

These counters measure

the uplink load of a cell.

The measurement value

has a positive correlation

with the cell load.


RAN




Issue 04 (2010-05-31)



Procedure


displayed.

Step 2 Click New Query... in the lower area. The Query Result dialog box is displayed.


1. Select the Object Type or the Function Subset in the left navigation tree.

2. Set parameters on the Object Settings, Counter Settings, and Other Settings tab pages.


NOTE

The query result can be displayed in three forms: Table, Line chart, and Bar chart. You can specify the

form in the View Type area.



NOTE

If the measurement result contains a Reliability field, the measurement result is reliable only when the

value of this field is Reliable.

----End

3.4 Querying and Saving the BSC6900 Operation Logs onthe M2000

The operation logs record the operations that the operation and maintenance personnel performon the BSC6900. The operation logs are used to identify faults. It is recommended that you

browse and save the operation logs on the M2000 client every day so that you can check whether

any unauthorized operations are performed on the equipment.

Prerequisite

l You have logged in to the M2000 client and the M2000 client communicates with the

BSC6900 normally.

l The BSC6900 operation logs are synchronized to the M2000 server. For the method of

synchronizing the operation logs, see the M2000 Operator Guide.

Procedure

l Operation Mode 1

1. On the M2000 client, choose System > Log Management > Query NE Operation

Logs, as shown in Figure 3-1.

RAN




3-9



Figure 3-1 Query NE Operation Logs

2. In the Filter Condition dialog box, set the query conditions for the NE operation logs.

– Based on the operation results, select Succeeded or Failed in the Result area.

– Set the Time Range.

– Click Choose to select the target NE. Then, the NE is displayed in the NE

Name area.

3. Click OK . The Query NE Operation Logs window displays the query results.

4. Click Save As. Then, enter the name of the log file and specify the format of the file

that saves the information about the operation logs.


RAN




Issue 04 (2010-05-31)



The information about the operation logs is saved in the specified folder for easy

querying.

l Operation Mode 2

1. On the M2000 client, choose Maintenance > MML Command. The MML

Command window is displayed.

2. Run the MML command BKP LOGDB to query the running status of the BTSs.

----End

3.5 Querying and Saving other Logs of the BSC6900

This section describes how to query and save other BSC6900 logs on the M2000 client. Other

logs refer to host logs, OMU logs, database logs, and system event logs.

Prerequisitel The M2000 client is properly connected to the server.

l You have the right to run the query type MML commands of the BSC6900.

Procedure


is displayed.

Step 2 Select the BSC6900 in the left navigation pane. The MML command navigation tree of the

BSC6900 is displayed.NOTE

If this function is used for the first time, a dialog box will be displayed, prompting you to download the

MML command configuration file of the current version of the NE when the NE is selected. Click Yes to

download the configuration file. After the downloading is complete, click OK .

Step 3 Run the COL LOG command to query all BAM logs and host logs. Set the parameters as

follows:

l Set Type to ALL.

l Set the Start Time to the start time of the last maintenance, and set the End Time to the start

time of the current maintenance.

Save the result in the zip format in the OMU active workspace installation directory\FTP

directory.

NOTE

l The information collected in this operation involves BSC6900 running logs, BSC6900 operation logs,

and the corresponding alarms.

l The log files that are not compressed in the BZ2 format in the OMU active workspace installation

directory\common\fam\famlog and the OMU active workspace installation directory\common\fam

\famlogfmt directories will not be saved.

l For the directory structure of OMU workspace, seeChecking the Installation Directory of the OMU

Applications.

----End

RAN




3-11



3.6 Querying and Saving NodeB Operation LogsThe operation information is recorded on the M2000 client. You can query the information on

a visualized interface and save the results in category.

Prerequisite

l Connection between the M2000 client and the M2000 server is operational.

l The M2000 user logs and the NodeB operation logs are synchronized. For details about

how to set synchronization of the logs, refer to the M2000 Operator Guide.

Procedure

Step 1 Choose System > Log Management > Query NE Operation logs on the M2000 client.

Step 2 Select the conditions in the Filter Condition dialog box:

l Choose Succeeded in the Result.

l Set Time Range to be from the previous day to the present day.

l Set NE Name to all the NodeB type.

Step 3 Click OK . You can view the corresponding log information.

Step 4 Click Save As to save the RNC operation logs.

The log records are saved in the specified folder for query.

----End

3.7 Querying and Saving NodeB other logsOther NodeB logs consist of the main board log, operation log, board log, and RTWP routine

test log.

Prerequisite


l The FTP server setting is complete.

l The FTP server communicates with the NodeB properly in the same intranet.

l No firewall is installed between the FTP server and the NodeB.

l You have the permission to run NodeB query commands.

Procedure

Step 1 Choose Maintenance > MML Command on the M2000 client. The MML Command window

is displayed.

Step 2 Select the NodeB in the navigation tree on the left. The navigation tree of NodeB MML

commands is displayed.

Step 3 Upload NodeB logs to a specified path by running ULD FILE . Here, set the parameters asfollows:


RAN




Issue 04 (2010-05-31)



l Enter a name in Destination File.

l Set File Flag based on the type of the backup file.

– To back up the main board log, select MAINBRDLOG.

–

To back up the operation log, select OPLOG.– To back up the board log, select BRDLOG.

– To back up the RTWP routine test log, select RTWPTEST.

l Specify FTP Server IP.

l Specify User Name and Password.

NodeB logs are backed up and saved under a specified path on the FTP server.

----End

3.8 Checking the Automatic Backup Function of NEsThis section describes how to check the automatic backup function of NEs on the M2000 client.

Prerequisite

You have logged in to the M2000 client and the M2000 client communicates with the related

NEs normally.

Context

The scheduled NE backup is a process in which the NE data is saved to the specified directory

on the server as a backup file. By performing this operation, you can prevent data loss and restorethe NEs in case they are not normal.

l The scheduled NE backup is a regular task.

l The task can be performed periodically or only once. The unit of Period can be set to days,

weeks, or months.

l The M2000 supports a maximum of 50 scheduled NE backup tasks.

Procedure

Step 1 On the M2000 client, choose Maintenance > Task Management. The Task Management

window is displayed.

Step 2 Click NE Backup under the Backup node in the left pane, and then check whether there are

scheduled NE backup tasks in the right pane.

If... Then...

There are scheduled NE backup tasks, The automatic backup function of the NE is

normal.

There is no scheduled NE backup task, Perform Step 3 through Step 7.

Step 3 Click New... in the lower area. The New Task dialog box is displayed.

RAN




3-13



Step 4 Set the basic information about the task as follows:

1. Enter a name in the Task Name text box.

2. Set Task Type to NE Backup.

3. Set Run Type to Period.Step 5 Click Next. Set Start Time, Period, and Run Times.

Step 6 Click Next. Select the backup type of By NE. The By NE dialog box is displayed. Select the

NE to be back up.

Step 7 Click Finish.

----End


RAN




Issue 04 (2010-05-31)



4Weekly RAN Maintenance Guidelines

About This Chapter

This chapter provides guidelines for performing the weekly maintenance tasks.

4.1 Checking the Running Status of OMU

This section describes how to check the running status of OMU on the M2000 client. The check

items are the CPU usage, memory usage, hard disk space, operating status, IP addresses, state

of the links between the two OMU, operating status of the service modules, and startup type.

4.2 Checking the BSC6900 Board Status

This section describes how to check the running status of the BSC6900 boards on the M2000

client or LMT. In the case of DPUb and DPUe boards, you should also check the running statusof the DSPs.

4.3 Checking the NodeB Board Status

This task checks the status of a NodeB board on the M2000 client.

4.4 Checking the BSC6900 Clock

This section describes how to check the clock status of the GCGa/GCUa board on the M2000

client or LMT.

4.5 Checking the State of the NodeB Clock

This task, on the M2000 client, checks the current state of the clock in the basic NodeB cabinet.

4.6 Backing Up and Restoring the RAN System Data

This section describes how to back up the system data on the M2000 client. The system data

consists of the configuration data, performance data, and alarm data.

4.7 Analyzing the Performance Measurement Results

This section describes how to analyze the performance measurement results on the M2000 client.

It is recommended that you collect the performance measurement results of a week on the M2000

client. If fluctuations are observed in the measurement result, you need to analyze them based

on the network conditions.

4.8 Collecting History Alarm Statistics

This section describes how to collect history alarm statistics on the M2000 client. The statistics

are based on the factors such as the equipment type, alarm severity, and alarm type. It also

describes how to obtain the statistical tables and analytic diagrams and how to save the statisticalresults.

RAN

Routine Maintenance Guide 4 Weekly RAN Maintenance Guidelines



4-1



4.9 Checking the Communication Between NEs and the M2000

This section describes how to check the communication between NEs and the M2000 in the

M2000 network topology.


RAN




Issue 04 (2010-05-31)



4.1 Checking the Running Status of OMU

This section describes how to check the running status of OMU on the M2000 client. The check

items are the CPU usage, memory usage, hard disk space, operating status, IP addresses, state

of the links between the two OMU, operating status of the service modules, and startup type.

Prerequisite

l You have logged in to the M2000 client and the M2000 client communicates with the

BSC6900 normally.


Context

Table 4-1 describes the expected result of checking the operating status of the OMU.

Table 4-1 Expected result of checking the operating status of the OMU

Check Item Expected Result

Operating status of

the OMU

In the query result, Free space(%) is greater than or equal to 20%.

Operating status

and data

synchronization

status of the active

and standby OMU

subsystems

l Computer name, Internal network fixed IP, External network

fixed IP, Internal network virtual IP, and External network

virtual IP in the query result comply with the planning.

l

Operational state, Internal network virtual IP state, Externalnetwork virtual IP state, Internal network link state, External

network link state, and Backup network link state are Normal.

l Data-sync state is Data synchronization is successful.

Table 4-2 describes the expected result of checking the operating status of the service modules

of the OMU.

Table 4-2 Expected result of checking the operating status of the service modules of the OMU

boards


State of the active

OMU

l State: Started

l Startup Type: Automatic

RAN




4-3




State of the standby

OMU

For sntp, ftp_server, omu_manager, and software:

l State: Started

l Startup Type: Automatic

For other services rather than sntp, ftp_server, omu_manager, and

software:

l State: Stopped

l Startup Type: Disabled

Configuration of

active and standby

OMU servers

For configuration of active and standby OMU servers: Consistent.

Procedure


is displayed.

Step 2 Select the BSC6900 in the left navigation tree. The navigation tree of BSC6900 MML commands

is displayed.

Step 3 Run the MML command DSP OMUSRV to query the operating status of the OMU.

Step 4 Run the MML command DSP OMU to query the operating status and data synchronization

status of the active and standby OMU subsystems.

Step 5 Run the MML command DSP OMUMODULE to query the operating status and startup type

of the modules of the active and standby OMU subsystems.

NOTE

l In the case of active/standby OMU, you can also run the MML command CHK PEERCFG to query

the configuration information about the active and standby OMU.

l For the reference of the query result, see Table 4-1. If any fault occurs, contact the corresponding

personnel for troubleshooting.

----End

4.2 Checking the BSC6900 Board Status

This section describes how to check the running status of the BSC6900 boards on the M2000

client or LMT. In the case of DPUb and DPUe boards, you should also check the running status

of the DSPs.

Prerequisite

l You have logged in to the M2000 client or LMT, and the M2000 client communicates with

the BSC6900 normally.



RAN




Issue 04 (2010-05-31)



Procedure

l Checking the Board Status Through MML Commands on the M2000



2. Select the BSC6900 in the left navigation tree. The navigation tree of BSC6900 MML


3. Run the MML command DSP BRD to query the status of all the boards in the specified

subrack. Here, specify Subrack No. and leave Slot No. empty.

4. Run the MML command DSP DSP to query the DSP state of the DPUb and DPUe

boards in the specified subrack. Here, specify Subrack No. and leave Slot No. empty.

l Checking the Board Status Through GUI on the LMT

1. On the LMT, click Device Maintenance. The Device Maintenance tab page is

displayed.

2. On the BSC Maintenance tab page, choose BSC Maintenance > MaintainDevice, and then double click Query BSC Board Information. The Query BSC

Board Information dialog box is displayed.

3. Set the parameters on the Query BSC Board Information tab page, and then click

Query.

NOTE

You can also query the board status in the following way: right-click a board on the BSC device

panel and then choose Query BSC Board Information from the shortcut menu.

4. On the BSC Maintenance tab page, choose BSC Maintenance > Maintain User

Resources, and then double-click Query DSP Resources. The Query DSP

Resources dialog box is displayed.5. Set the parameters on the DSP Resource Info tab page, and then click Query.

6. The result is displayed in the Query DSP Resources tab page.

----End

Postrequisite

l If any fault occurs on the boards, contact the corresponding personnel to rectify the fault.

Ensure that the CPUs of all the boards are normal.

l If any fault occurs on the DSPs of the DPUb and DPUe boards, contact the corresponding

personnel to rectify the fault. If the DSPs cannot be restored to normal and the services areadversely affected, replace the board.

4.3 Checking the NodeB Board Status

This task checks the status of a NodeB board on the M2000 client.

Prerequisite



RAN




4-5



Procedure


is displayed.

Step 2 Select the NodeB in the navigation tree on the left. You may select multiple NodeBs of the same

version and model at a time. The navigation tree of the NodeB MML commands is displayed.

Step 3 Query the state of all the NodeB boards by running DSP BRD. Do not set the parameters.

NOTE

If faults occur to the boards, contact corresponding personnel to clear the faults. Refer to board alarm

handling procedures in NodeB Alarm Reference.

----End

4.4 Checking the BSC6900 ClockThis section describes how to check the clock status of the GCGa/GCUa board on the M2000

client or LMT.

Prerequisite

l You have logged in to the M2000 client or LMT, and the M2000 client communicates with

the BSC6900 normally.


ContextNOTE

l It is recommended that you query the clock status of only the GCUa/GCGa board. For the GCUa/

GCGa board, you can query the status of the clock source used by the current system and the clock

source switching mode of the current clock phase-locked loop.

l The GCUa/GCGa boards are fixedly configured in slots 12 and 13 in the MPS.

Procedure

l Checking the Clock Status Through MML Commands on the M2000



2. Select the BSC6900 in the left navigation tree. The navigation tree of BSC6900 MML


3. Run the MML command DSP CLK to query the status of the clock boards in the MPS.

Here, set Subrack No. to 0 and specify Slot No..

l Checking the Clock Status Through GUI on the LMT

1. On the LMT, click Device Maintenance. The Device Maintenance tab page is

displayed.

2. On the BSC Maintenance tab page, choose BSC Maintenance > Maintain

Device, and then double-click Query BSC Board Clock Status. The Query BSCBoard Clock Status dialog box is displayed.


RAN




Issue 04 (2010-05-31)



3. Set the parameters on the Query BSC Board Clock Status tab page, and then click

Query.

4. The result is displayed in the Query BSC Board Clock Status tab page.

NOTE

If the clock source state of any level is Unavailable or the Phase-locked loop state of current

clock is Unknown, you can infer that the clock source is lost. Contact the corresponding personnel

for troubleshooting. Ensure that the status of the clock source stratum and the clock working state

are Available and Fast Tracking respectively.

----End

4.5 Checking the State of the NodeB Clock

This task, on the M2000 client, checks the current state of the clock in the basic NodeB cabinet.

Prerequisite



Procedure


is displayed.

Step 2 Select the NodeB in the navigation tree on the left. You may select multiple NodeBs of the same

version at a time. The navigation tree of the NodeB MML commands is displayed.

Step 3 Check the clock state of the active and standby NMPTs/BBUs in the basic NodeB cabinet by

running DSP CLKSTAT .

Step 4 Contact corresponding personnel for troubleshooting when the following situations occur:

If... Then...

The OCXO clock source is unavailable, or

Current work mode is inconsistent with the

set working mode.

It is an indication that the clock source is lost.

Clock source status is JITTER, LOST,

OUTSCOPE, or UNKNOWN

It is an indication that the clock source is

exceptional.

Current working oscillator is of the TCXO

type

It is an indication that the oscillator OCXO of

the NMPT/BBU is faulty.

Clear the problems and ensure that the NodeB clock state is as follows:

l Clock source status: NORMAL.

l Clock status: LOCKED.

RAN




4-7



l Current oscillator: OCXO.

----End

4.6 Backing Up and Restoring the RAN System DataThis section describes how to back up the system data on the M2000 client. The system data

consists of the configuration data, performance data, and alarm data.

4.6.1 Automatically Backing Up the System Data

You can enable the automatic backup of the BSC6900 and NodeB by creating the corresponding

backup tasks on the M2000 client.

4.6.2 Manually Backing Up the System Data

The M2000 client supports not only the periodical backup of NE data but also the manual backup

of NE data as required.

4.6.3 Manually Restoring the System Data (M2000)

The M2000 client supports not only the periodical backup of NE data but also the manual backup

of NE data as required.

4.6.4 Manually Backing Up and Restoring the System Data on the LMT

This describes how to manually back up the BSC6900 system data on the LMT. The system data

consists of the BSC6900 configuration data, performance data, and alarm data.

4.6.1 Automatically Backing Up the System Data

You can enable the automatic backup of the BSC6900 and NodeB by creating the corresponding

backup tasks on the M2000 client.

Prerequisite


NEs normally.

l You have the permission to back up data.

Context

The NE backup task is a process in which the NE data is saved to the specified directory on the

M2000 server as a backup file. Through this task, you can prevent data loss and restore the NEsin case they are not normal.

Procedure

Step 1 On the M2000 client, choose Maintenance > Task Management. The Task Management

window is displayed.

Step 2 Click New... in the lower area. The New Task dialog box is displayed.

Step 3 Set the basic information about the task as follows:

1. Enter a name in the Task Name text box.

2. Set Task Type to NE Backup.


RAN




Issue 04 (2010-05-31)



Step 3 Expand the navigation tree and select an NE.

l You can press Ctrl to select multiple NEs at a time. To select all the NEs, click the root node.

l If the selected NE contains sub NEs, a dialog box is displayed, prompting whether to back up the data of all the sub NEs under the selected NE. Under this NE, you can also select only

the sub NEs whose data needs to be backed up.

Step 4 Click Backup. The Confirm dialog box is displayed. Click Yes.

When the backup task is started, the real-time progress and detailed information about the backup

task are displayed in the Immediate Task in the Backup Management window.

----End

4.6.3 Manually Restoring the System Data (M2000)

The M2000 client supports not only the periodical backup of NE data but also the manual backupof NE data as required.

Prerequisite


NEs normally.

l The FTP server is set up on the M2000.

l You have the permission to restore data.

l The NE data has been on the server.

Context

The M2000 server is used as the FTP server to connect the client and the NE.

Procedure

Step 1 On the M2000 client, choose Maintenance > Backup Management. The Backup

Management window is displayed.

Step 2 Click the NE Backup List tab, as shown in Figure 4-2.


RAN




Issue 04 (2010-05-31)



Figure 4-2 NE Backup List

Step 3 Expand the navigation tree and select an NE.

l You can press Ctrl to select multiple NEs at a time. To select all the NEs, click the root node.

l If the selected NE contains sub NEs, a dialog box is displayed, prompting whether to back

up the data of all the sub NEs under the selected NE. Under this NE, you can also select only

the sub NEs whose data needs to be backed up.

Step 4 Select a backup file in the list.

Step 5 Click Restore in the dialog box, and click Yes in the displayed Confirm dialog box.

CAUTION

The NE restarts after you perform the restore operations.

----End

4.6.4 Manually Backing Up and Restoring the System Data on theLMT

This describes how to manually back up the BSC6900 system data on the LMT. The system data

consists of the BSC6900 configuration data, performance data, and alarm data.

Prerequisite

You have logged in to the BSC6900 LMT.

RAN




4-11



Context

CAUTION

l When the BSC6900 is configured with two OMUa boards, that is, in dual-OMU mode, you

must back up data on the primary OMU.

l You must manually back up the OMU database before capacity expansion or upgrade.

Procedure

Step 1 Manually back up and restore the BSC6900 system data by referring to Backing Up the System

Data and Restoring the System Data.

----End

4.7 Analyzing the Performance Measurement Results

This section describes how to analyze the performance measurement results on the M2000 client.

It is recommended that you collect the performance measurement results of a week on the M2000

client. If fluctuations are observed in the measurement result, you need to analyze them based

on the network conditions.

Prerequisite

l

You have logged in to the M2000 client and the M2000 client communicates with the related NEs normally.

l The measurement objects exist.


Context

For details of the performance counters, see the BSC6900 Performance Counter Reference. You

can specify the daily maintenance standards based on the network status and assessment

standards.

Procedure


displayed.

Step 2 In the Query Result window, click New Query... in the lower area. The Query Result dialog

box is displayed.


1. Select the Object Type or the Function Subset in the left navigation tree.

2. In the three tab pages (Object Settings, Counter Settings, and Other Settings) on the

right pane, specify the object, counter, and period for measurement.



RAN




Issue 04 (2010-05-31)



NOTE

The query result can be displayed in three forms: Table, Line chart, and Column chart.



----End

4.8 Collecting History Alarm Statistics

This section describes how to collect history alarm statistics on the M2000 client. The statistics

are based on the factors such as the equipment type, alarm severity, and alarm type. It also

describes how to obtain the statistical tables and analytic diagrams and how to save the statistical

results.

Prerequisitel You have logged in to the M2000 client and the M2000 client communicates with the related

NEs normally.

l You have the permission to collect alarm statistics.

NOTE

The procedures for collecting the statistics about event alarms and fault alarms are the same. For illustrative

purposes, the following part describes how to collect the statistics about fault alarms.

Procedure

l Collect alarm statistics according to the statistical conditions.

1. On the M2000 client, choose Monitor > Alarm Logs Statistics.

The Statistic Filter dialog box is displayed.

2. In the Statistic Filter dialog box, set the fault alarm statistical conditions, and then

click OK .

NOTE

The statistical results are displayed on the Table and Pie tabs.

l On the Table tab page, the results are displayed in a table.

l On the Pie tab page, the results are displayed in pie charts.

3. Click Save As... in the lower right area to save the results as a file.

NOTE

l On the Table tab page, the results can be saved as .txt, .html, .csv, .xls or .pdf file. By

default, the results are saved as a .pdf file. If there are more than 256 columns in the .csv

file, the Excel tool may not be able to open the file. In such cases, use UltraEdit or Notepad.

l On the Pie tab page, the results can be saved as a .jpg file.

4. On the Table tab page, click Print to print the statistical results.

l Collect alarm statistics according to the template.

1. On the M2000 client, choose Monitor > Alarm Logs Statistics.

2. In the displayed Statistic Filter dialog box, click Cancel.

3. In the Alarm Logs Statistics window, click Template. The following part takes howto create a template as an example. On the shortcut menu, click New....

RAN




4-13



4. In the Add Template dialog box, enter the Template name and set Share to Yes or

No as required. Then, click Next.

5. In the Filter dialog box, set the alarm statistical conditions, and then click OK .

6. In the Confirm dialog box, click Yes.

----End

4.9 Checking the Communication Between NEs and theM2000

This section describes how to check the communication between NEs and the M2000 in the

M2000 network topology.

Prerequisite

l You have logged in to the M2000 client. The communication between the M2000 client

and the server is normal.

l You have the proper operation authority.

Context

Criterion for the operation: All the NEs communicate with the M2000 normally. If the

communication between a NE and the M2000 is disrupted, there is a red cross on the upper left

of the NE, as shown in Figure 4-3.

Figure 4-3 M2000 network topology


RAN




Issue 04 (2010-05-31)



Procedure

Step 1 Log in to the M2000, and than choose Topology > Main Topology. The Main Topology tab

page is displayed. Check the status of each NE in the network topology. Check whether the

connections of NEs are normal.

----End

Postrequisite

In routine maintenance, most communication problems are caused by network failure. Rectify

the connection problems of the network and the communication problems will disappear.

RAN




4-15



5Monthly RAN Maintenance Guidelines

About This Chapter

This chapter provides guidelines for performing the monthly maintenance tasks.

5.1 Analyzing Customer Complaints

This section describes how to find the causes and tendency of faults. The task helps to handle

problems at points of frequent faults.

5.2 Preparing the NE Performance Report

Collecting statistics about the fault alarms on a monthly basis helps to analyze the occurrences

of the fault alarms generated on the BSC6900 and NodeB and to prepare the NE performance

report.

5.3 Preparing a Performance Report

According to the fault occurrence tendency, analyze the performance of the BSC6900 and

NodeB and prepare a performance report.

5.4 Checking the Disk Space on the Terminal System

The disk space available on the terminal system should meet the specified requirements.

5.5 Checking the Maintenance Terminal System for Viruses

This section describes how to check the maintenance terminal system for viruses so that the

system is free of any virus. The maintenance terminal system consists of the M2000 client and

LMT.

RAN

Routine Maintenance Guide 5 Monthly RAN Maintenance Guidelines



5-1



5.1 Analyzing Customer Complaints

This section describes how to find the causes and tendency of faults. The task helps to handle problems at points of frequent faults.

Prerequisite

The records of customer complaints are obtained.

Procedure

Step 1 Based on customer complaints, collect information of monthly faults and identify the scope and

category of the faults.

Step 2 Determine the causes of faults by analyzing and comparing possible causes.

Step 3 Collect statistics on the monthly faults and analyze the fault tendency.

Step 4 Analyze the points of frequent faults, locate problems, and handle the problems.

Step 5 Summarize the troubleshooting experience and offer suggestions.

----End

5.2 Preparing the NE Performance Report

Collecting statistics about the fault alarms on a monthly basis helps to analyze the occurrences

of the fault alarms generated on the BSC6900 and NodeB and to prepare the NE performance

report.

Context

Table 5-1 lists the alarm statistical modes. It is recommended that you select the alarm statistical

mode according to the actual requirements and the number of alarms generated in the month.

Table 5-1 Alarm statistical modes

Alarm Statistical Mode Description

By alarm severity The alarm statistics are collected according to the

alarm severity.

There are four alarm severities: critical, major,

minor, and warning.

By alarm ID The alarm statistics are collected according to the

alarm ID.

By alarm type The alarm statistics are collected according to the

alarm type.


RAN




Issue 04 (2010-05-31)



Alarm Statistical Mode Description

By top N base stations with the

maximum number of alarms

The alarm statistics about the current monitoring

group are collected according to the number of

alarms generated by the base stations in this group.

The system collects statistics on the N base stations

that have the maximum number of alarms and the

alarms generated by the base stations.

By top N cells with the maximum

number of alarms



alarms generated in the cells in this group.

The system collects statistics on the N cells that

have the maximum number of alarms and the alarms

generated in the cells.

By top N signaling links with themaximum number of alarms

The alarm statistics about the current monitoringgroup are collected according to the number of

alarms generated on the signaling links in this

group.

The system collects statistics on the N signaling

links that have the maximum number of alarms and

the alarms generated on the signaling links.

By top N E1/T1 links with the

maximum number of alarms



alarms generated on the E1/T1 links in this group.

The system collects statistics on the N E1/T1 links

that have the maximum number of alarms and thealarms generated on the E1/T1 links.

Procedure

Step 1 On the M2000 client, choose Monitor > Network Integration Monitoring. The Network

Integration Monitoring window is displayed.

Step 2 On the Network Monitor tab page, double-click an NE monitoring group panel. Alternatively,

you can right-click an NE monitoring group panel and then choose Alarm from the shortcutmenu. You can also select the global monitoring group panel.

Step 3 Click the Alarm Stat. tab in the lower part of the Network Integration Monitoring window.

Step 4 Click Stat. Options.... The Stat. Options dialog box is displayed.

Step 5 In the Stat. Type area, specify the NE Type.

Step 6 Specify the Start Time and End Time. The statistical period should be a whole month.

Step 7 Configure the related parameters in the Stat. Type area. See Table 5-1.

Step 8 Click Stat.. The corresponding alarm statistics are collected.

RAN




5-3



Step 9 Right-click in the Alarm Browse tab page, and then click Save or Print to form an alarm report.

----End

5.3 Preparing a Performance ReportAccording to the fault occurrence tendency, analyze the performance of the BSC6900 and

NodeB and prepare a performance report.

Procedure

Step 1 Identify and analyze the faults occurred in this month. For details, see 5.2 Preparing the NE

Performance Report.

Step 2 Collect the monthly performance data, such as performance statistics, history performance data,

and system monitoring data. Find the change tendency in the monthly performance data.

Step 3 Collect daily and weekly monitoring reports on routine network performance, and then find the

performance change tendency.

Step 4 Prepare a monthly performance report according to the collected statistics.

----End

5.4 Checking the Disk Space on the Terminal System

The disk space available on the terminal system should meet the specified requirements.

Prerequisite

l For the M2000 client, the available space on the hard disk should be at least 50% of the

total capacity.

l Minimum configuration requirement for the independent partitioning of the OMU: The

available space should be at least 10% of the capacity of each partition.

Procedure

Step 1 Check the available space on the hard disk of the M2000 client. If the available space is lower

than 50% of the total capacity, delete the temporary files, unnecessary software programs andunnecessary backup files.

Step 2 Check and clean up the OMU Hard Disk by referring to Regularly Checking and Cleaning Up

the OMU Hard Disk. Delete the temporary files and unnecessary backup files.

----End

5.5 Checking the Maintenance Terminal System for Viruses

This section describes how to check the maintenance terminal system for viruses so that the

system is free of any virus. The maintenance terminal system consists of the M2000 client andLMT.


RAN




Issue 04 (2010-05-31)



Procedure

Step 1 Clear viruses on the computer by using copyrighted antivirus software.

----End

RAN




5-5




About This Chapter

The Routine Maintenance Record is used to record the information about the equipment

performance during the maintenance.

6.1 Daily Maintenance Record

This section provides the daily maintenance record for recording daily routine maintenance on

site.

6.2 Weekly Maintenance Record

This section provides the weekly maintenance record for recording weekly routine maintenance.

6.3 Monthly Maintenance Record

This section provides the monthly maintenance record for recording monthly routine

maintenance.

RAN

Routine Maintenance Guide 6 RAN Routine Maintenance Record



6-1



6.1 Daily Maintenance Record

This section provides the daily maintenance record for recording daily routine maintenance on

site.

After performing daily routine maintenance, record the result in the Table 6-1.

Table 6-1 Daily Maintenance Record

SN Item Expected Result OperationRecord

1 Check RAN fault alarms.

No BSC6900 or NodeB fault

alarms exist.

2 Check RAN eventalarms. No BSC6900 or NodeB eventalarms exist.

3

Collect RAN alarm

statistics. —

4

Check the status of

important cells.

The cell operating status is

Available.

5

Check resources of

important cells. —

6

Check the status of each

interface.

7 Check the key counters.

The value of the counters meets

the requirements.

8

Save the results of key

performance counters. —

9

Query and save the

BSC6900 operation logs. —

10

Query and save other

BSC6900 logs. —

11Query and save NodeBoperation logs. —

12

Query and save other

NodeB logs. —

13

Check the automatic NE

backup function.

The automatic NE backup

function is normal.

You can download the table: Daily Maintenance Record


RAN




Issue 04 (2010-05-31)



6.2 Weekly Maintenance Record

This section provides the weekly maintenance record for recording weekly routine maintenance.

After performing weekly routine maintenance, record the result in the Table 6-2.

Table 6-2 Weekly Maintenance Record


1

Check the running status

of the OMU.

See Table 1 and Table 2 in the

Context part of Chapter

"Checking the Running Status of

OMU".

2

Check the BSC6900

board status.

The CPU status of each board is

normal.

3

Check the NodeB board

status.

The status of each board is

normal.

4

Check the BSC6900

clock.

The clock source status is

normal.

5 Check the NodeB clock.

The clock source status is

normal.

6 Back up the system data. -

7

Analyze performance

measurement results. -

8

Analyze alarm statistics

results. -

9

Check the

communication between

NEs and the M2000.

All NEs communicate with the

M2000 normally.

You can download the table: Weekly Maintenance Record

6.3 Monthly Maintenance Record

This section provides the monthly maintenance record for recording monthly routine

maintenance.

After performing monthly routine maintenance, record the result in the Table 6-3.

RAN

Routine Maintenance Guide 6 RAN Routine Maintenance Record



6-3



Table 6-3 Monthly Maintenance Record


1 Analyze customer complaints.—

2

Prepare the equipment running

report. —

3

Preparing the performance

report. —

4

Check the disk space on the

terminal system.

The disk space on the

terminal system meets the

requirements.

5

Check the maintenance

terminal system for viruses.

The system is free of any

virus.

You can download the table: Monthly Maintenance Record


RAN


ran routine maintenance guide(v900r011c00_04)

Documents