ran routine maintenance guide(ran11.0_01)

7/27/2019 RAN Routine Maintenance Guide(RAN11.0_01)

http://slidepdf.com/reader/full/ran-routine-maintenance-guideran11001 1/70

RAN

11.0

Routine Maintenance Guide

Issue 01

Date 2009-02-10

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.



Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For anyassistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd. Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

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

No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but the statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

http://www.huawei.com/



Contents

About This Docum ent.....................................................................................................................1

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

2 Introduction to R AN Routine Maintenance.........................................................................2-12.1 Range of RAN Routine Maintenance..............................................................................................................2-22.2 Tools and Uti lities of RAN Routine Maintenance..........................................................................................2-2

2.3 Items List and Period of RAN Routine Maintenance.....................................................................................2-2

3 RAN Daily Main tenance Guidelines.....................................................................................3-13.1 Monitorin g RAN Alarms on the M2000 ........................................................................................................3-3

3.1.1 Mon itoring RAN Current Fault Alarms on the M2000..........................................................................3-3

3.1.2 Mon itoring RAN Event Alarms on the M2000......................................................................................3-4

3.2 Collecting Statistics About RNC and NodeB Alarms.....................................................................................3-4

3.3 Querying and Saving RAN Performance Measurement Results.....................................................................3-5

3.3.1 Quer ying the Results of Major Performance Measurement Counters...................................................3-5

3.3.2 Saving t he Results of Major Performance Measurement Counters.......................................................3-7

3.4 Querying and Saving RNC Operation Logs....................................................................................................3-8

3.5 Querying and Saving Other RNC Logs...........................................................................................................3-8

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

3.7 Saving NodeB other logs.................................................................................................................................3-9

3.8 Checking the Automatic Backup of NEs on the M2000...............................................................................3-10

3.9 Checking Cell State and Resources...............................................................................................................3-11

3.9 .1 Checking the States of All Cells..........................................................................................................3-12

3.9.2 Chec king the States of Faulty Cells.....................................................................................................3-123.9.3 Chec king Cell Resources.....................................................................................................................3-13

3.10 Checking the State of Interfaces on the RNC (over ATM).........................................................................3-14

3.1 0.1 Checking the State of an Interface on the Physical Layer (over ATM).............................................3-15

3.10.2 Checking the State of an SAAL Link.................................................................................................3-17

3.10.3 Checking the State of an MTP3.........................................................................................................3-18

3.1 0.4 Checking the State of an SCCP..........................................................................................................3-19

3.10.5 Checking the State of an AAL2 Path.................................................................................................3-19

3.10.6 Checking the State of an NCP or CCP (over ATM)..........................................................................3-20

3.11 Checking the State of Interfaces on the RNC (over IP)..............................................................................3-20

3.11.1 Checking the State of an Interface on the Physical Layer (over IP)..................................................3-21

RANRoutine Maintenance Guide Contents

Issue 01 (2009-02-10) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i



3.11.2 Checking the State of an SCTP Link.................................................................................................3-22

3.11.3 Checking the State of an M3UA........................................................................................................3-23

3.11.4 Checking the State of an IP Path........................................................................................................3-24

3.11.5 Checking the State of an NCP or CCP (over IP)................................................................................3-25

4 RAN Weekly Maintenance Guidelines.................................................................................4-14.1 Checking the State of a BAM on the M2000..................................................................................................4-2

4.2 Checking the State of a BAM Module on the M2000.....................................................................................4-3

4.3 Checking the State of an RNC Board on the M2000......................................................................................4-3

4.4 Checking the State of a NodeB Board on the M2000.....................................................................................4-4

4.5 Checking the State of the RNC Clock on the M2000.....................................................................................4-4

4.6 Checking the State of the NodeB Clock on the M2000..................................................................................4-5

4.7 Backing Up RNC System Data.......................................................................................................................4-6

4.7.1 Automatically Backing Up RNC System Data......................................................................................4-6

4.7.2 Manually Backing Up RNC System Data on the LMT.........................................................................4-7

4.7.3 Backing Up RNC System Data Manually(Using BamBackup Tool)....................................................4-8

4.8 Backing Up NodeB Configuration Data.......................................................................................................4-10

4.8.1 Automatically Backing Up NodeB Configuration Data......................................................................4-10

4.8.2 Man ually Backing Up NodeB Configuration Data on the M2000.......................................................4-11

4.8.3 Man ually Backing Up NodeB Configuration Data on the LMT..........................................................4-12

5 RAN Mo nthly Maintenance Guidelines...............................................................................5-15.1 Analyzing Customers Complaints...................................................................................................................5-2

5.2 Making a Performance Report........................................................................................................................5-2

5.3 Checking the Data Consistency Between the RNC FAM and BAM Servers.................................................5-2

5.4 Checking Disk Space of Terminal System......................................................................................................5-3

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

6 RAN Routine Maintenance Record........................................................................................6-16.1 RAN Daily Maintenance Record....................................................................................................................6-2

6.2 RAN Weekly Maintenance Record.................................................................................................................6-4

6.3 RAN Monthly Maintenance Record...............................................................................................................6-5

ContentsRAN


ii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2009-02-10)



Figures

Figure 4-1 omu_backup_restore_tool interface....................................................................................................4-9

Figure 4-2 Backup progress prompt...................................................................................................................4-10

Figure 4-3 DataConfig File Transfer dialog box.............................................................................................4-13

Figure 4-4 FTP Setting dialog box...................................................................................................................4-13

RANRoutine Maintenance Guide Figures


iii



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 Performance counters....................................................................................................... ....................3-6

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

Table 3-3 Criteria for physical layer interface status in ATM transport mode..................................................3-15

Table 3-4 Criteria for MTP3 state......................................................................................................................3-18

Table 3-5 Criteria for physical layer interface status in IP transport mode........................................................3-21

Table 3-6 Criteria for M3UA state.....................................................................................................................3-23

Table 4-1 Criteria for checking the operational state of the BAMs.....................................................................4-2

Table 4-2 Criteria for the state of BAM modules.................................................................................................4-3

Table 4-3 Fields in the FTP Setting dialog box................................................................................................4-14

Table 6-1 RAN daily maintenance record............................................................................................................6-2

Table 6-2 RAN weekly maintenance record........................................................................................................6-4Table 6-3 RA N monthly maintenance record.......................................................................................................6-5

RANRoutine Maintenance Guide Tables


v



About This Document

PurposeThe RAN Routine Maintenance Guide provides suggestions on how to maintain HuaweiWCDMA RAN system and serves as a reference for operators to perform routine maintenance.

This document provides guidelines for daily, weekly, and monthly RAN maintenance and givestables for recording routine maintenance.

Product VersionThe following table lists the product versions related to this document.

Product Name Product Version

RNC V100R011

V200R011 NodeB V100R011

V200R011

M2000 V200R008

Intended AudienceThis document is intended for:

l Shift operators

l System engineers

Organization

1 Changes in RAN Routine Maintenance Guide

This provides the changes in the RAN Routine Maintenance Guide.

2 Introduction to RAN Routine Maintenance

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

state of the RNC and the NodeB. Routine maintenance reduces the risk of system failure byidentifying and tackling problems in time.

RANRoutine Maintenance Guide About This Document


1



3 RAN Daily Maintenance Guidelines

This part describes daily maintenance tasks and corresponding operations.

4 RAN Weekly Maintenance Guidelines

This part describes weekly maintenance tasks and corresponding operations.

5 RAN Monthly Maintenance Guidelines

This part describes monthly maintenance tasks and corresponding operations.

6 RAN Routine Maintenance Record

The RAN Routine Maintenance Record is used to record the information about the equipment performance state during the maintenance.

ConventionsSymbol 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 notavoided,will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if notavoided,could result in equipment damage, data loss,

performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or savetime.

Provides additional information to emphasize or supplementimportant points of the main text.

General ConventionsThe 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 inboldface . For example, log in as user root .

Italic Book titles are in italics .

Courier New Examples of information displayed on the screen are inCourier New.

About This DocumentRAN


2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2009-02-10)



Command Conventions

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

Convention DescriptionBoldface 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 byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... } * Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ] * Optional items are grouped in brackets and separated byvertical 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.

Convention DescriptionBoldface 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.

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 meansthe two keys should be pressed in turn.

Mouse Operations

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

RANRoutine Maintenance Guide About This Document


3



Action Description

Click Select and release the primary mouse button without movingthe pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

Drag Press and hold the primary mouse button and move the pointer to a certain position.

About This DocumentRAN


4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2009-02-10)



1 Changes in RAN Routine MaintenanceGuide

This provides t he changes in the RAN Routine Mainte nance Guide.

01(2009-02-10)This is the field trial release of RAN11.0.

Compared with issue 02(2008-08-05)of RAN10.0, the following parts are deleted:l Backing up the RNC logs

l Making a report on fault alarms

Compared with iss ue 02(2008-08-05)of RAN10.0, the following parts are added :l 3.5 Queryin g and Saving Other RNC Logs

l 3.8 Checking the Automatic Backup of NEs on the M2000

l 5.1 Analyzing Customers Complaints

l 4.7.1 Automatically Backing Up RNC System Data

l 4.7.2 Manually Backing Up RNC System Data on the LMT

l 4.7.3 Backing Up RNC System Data Manually(Using BamBackup Tool)

Compared with issue 02(2008-08-05)of RAN10.0, the following parts are modified:

Content Modified Item3.11.2 Checking the State of an SCTPLink , 3.10.2 Checking the State of anSAAL Link

Description of checking the status of theSCTP link and the SAAL link on the M2000client is modified.

RANRoutine Maintenance Guide 1 Changes in RAN Routine Maintenance Guide


1-1



2 Introduction to RAN Routine Maintenance

About This Chapter

The purpose of routine maintenance is to ensure reliability, stability, and optimum operationstate of the RNC and the NodeB. Routine maintenance reduces the risk of system failure byidentifying and tackling problems in time.

2.1 Range of RAN Routine MaintenanceRoutine maintenance is conducted at the network management center to ensure reliable operationof the NodeB and the RNC.

2.2 Tools and Utilities of RAN Routine MaintenanceTools and utilities of RAN routine maintenance involve the M2000 client and the NE LMTs.They are com plementary to each other for RAN routine maintenance.

2.3 Items Lis t and Period of RAN Routine MaintenanceAccording to the maintenance frequency, routine maintenance can be classified into: dailymaintenance, weekly maintenance, and monthly maintenance.

RANRoutine Maintenance Guide 2 Introduction to RAN Routine Maintenance


2-1



2.1 Range of RAN Routine MaintenanceRoutine maintenance is conducted at the network management center to ensure reliable operationof the NodeB and the RNC.

Routine maintenance of the RAN refers to device performance monitoring and maintenance of the RNC and the NodeB. The maintenance is generally performed on the M2000.

RAN routine maintenan ce does not inclu de the rou tine maintenance of the M2000 or the on-sitemaintenance.

l To perform routine maintenance for the M2000, refer to the M2000 Operator Guide .

l To perform on-site maintenance, refer to the RNC Site Maintenance Guide and the NodeBSite Maintenance Guide .

l To modify the RAN configuration, refer to the RAN Reconfiguration Guide .

2.2 Tools and Utilities of RAN Routine MaintenanceTools and utilities of RAN routine maintenance involve the M2000 client and the NE LMTs.They are complementary to each other for RAN routine maintenance.

M2000 Client

The M2000 client is used to monitor multiple NEs simultaneously.

NOTE

When the RAN Sharing feature is enabled, the OSS of an operator gains access to the RAN through thenorthbound interface. It does not have the authority to check the configurations, status, alarms, and

performance of the cells of other operators. Instead, it is authorized to check the configurations, status,alarms, and performance of public resources. The OSS of the operator, however, is not authorized to modifythe attributes of public resources. It can check and modify the configurations, status, alarms, and

performance of its own cells.

NE LMT

An NE LMT is used to perform routine maintenance for a single NE.

When the M2000 client detects a fault of an NE, you can log in to that NE through the LMT tolocate, analyze, and clear that fault.

2.3 Items List and Period of RAN Routine MaintenanceAccording to the maintenance frequency, routine maintenance can be classified into: dailymaintenance, weekly maintenance, and monthly maintenance.

Table 2-1 , Table 2-2 , and Table 2-3 list the contents and operation references of the dailymaintenance, weekly maintenance, and monthly maintenance respectively.

You can add or delete maintenance tasks according to the field requirements.

2 Introduction to RAN Routine MaintenanceRAN


2-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2009-02-10)



Table 2-1 Daily maintenance tasks

SN Item Reference

1 Querying current fault alarms 3.1.1 Monitoring RAN Current Fault

Alarms on the M2000

2 Querying event alarms 3.1.2 Monitoring RAN Event Alarmson the M2000

3 Collecting statistics about RNC and NodeB alarms

3.2 Collecting Statistics About RNCand NodeB Alarms

4 Checking the states of all cells 3.9.1 Checking the States of All Cells

5 Checking the states of faulty cells 3.9.2 Checking the States of FaultyCells

6 Checking cell resources 3.9.3 Checking Cell Resources

7 Checking the state of a physical link 3.10.1 Checking the State of anInterface on the Physical Layer (overATM)

3.11.1 Checking the State of anInterface on the Physical Layer (overIP)

8 Checking the state of an SAAL link 3.10.2 Checking the State of an SAALLink

9 Checking the state of an MTP3-B 3.10.3 Checking the State of an MTP3

10 Checking the state of an SCCP 3.10.4 Checking the State of an SCCP

11 Checking the state of an AAL2 path 3.10.5 Checking the State of an AAL2Path

12 Checking the state of an NCP or CCP

3.10.6 Checking the State of an NCP orCCP (over ATM)

3.11.5 Checking the State of an NCP orCCP (over IP)

13 Checking the state of an M3UA 3.11.3 Checking the State of an M3UA

14 Checking the state of an IP path 3.11.4 Checking the State of an IP Path

15 Checking the State of an SCTP link 3.11.2 Checking the State of an SCTPLink

16 Querying the results of major performance measurement counters

3.3.1 Querying the Results of MajorPerformance Measurement Counters

17 Saving the results of major performance measurement counters

3.3.2 Saving the Results of MajorPerformance Measurement Counters

18 Querying and Saving RNCOperation Logs

3.4 Querying and Saving RNCOperation Logs



2-3



SN Item Reference

19 Querying and Saving RNC Other Logs

3.5 Querying and Saving Other RNCLogs

20 Querying and Saving NodeBOperation Logs

3.6 Querying and Saving NodeBOperation Logs

21 Saving NodeB other logs 3.7 Saving NodeB other logs

22 Checking the automatic backup of NEs on the M2000

3.8 Checking the Automatic Backup of NEs on the M2000

Table 2-2 Weekly maintenance tasks

SN Item Reference Step

1 Checking the state of a BAM 4.1 Checking the State of a BAM onthe M2000

2 Checking the state of a BAM module 4.2 Checking the State of a BAMModule on the M2000

3 Checking the state of an RNC board 4.3 Checking the State of an RNCBoard on the M2000

4 Checking the state of an NodeB board 4.4 Checking the State of a NodeBBoard on the M2000

5 Checking the state of the RNC clock 4.5 Checking the State of the RNC

Clock on the M2000

6 Checking the state of the NodeB clock 4.6 Checking the State of the NodeBClock on the M2000

7 Backing up the RNC system data 4.7 Backing Up RNC System Data

8 Backing up the NodeB configurationdata

4.8 Backing Up NodeBConfiguration Data

Table 2-3 Monthly maintenance tasks

SN Item Reference Step1 Analyzing customers' complaints 5.1 Analyzing Customers

Complaints

2 Making a performance report 5.2 Making a Performance Report

3 Checking the data consistency between the RNC FAM and BAMs

5.3 Checking the Data ConsistencyBetween the RNC FAM and BAMServers

4 Checking disk space of terminalsystem

5.4 Checking Disk Space of TerminalSystem

2 Introduction to RAN Routine MaintenanceRAN



Issue 01 (2009-02-10)



SN Item Reference Step

5 Checking the terminal system for viruses

5.5 Checking the Terminal Systemfor Viruses



2-5



3 RAN Daily Maintenance Guidelines

About This Chapter

This part describes daily maintenance tasks and corresponding operations.

3.1 Monitorin g RAN Alarms on the M2000This task mo nitors RAN alarms on the M2000 client. Th e alarms are of two types: fault alarmsand event ala rms.

3.2 Collectin g Statistics About RNC and NodeB AlarmsThis task sort s out alarms generated on the RNC and the Nod eB according to NE types, alarmseverities, or alarm types. This task also saves the result.

3.3 Querying and Saving RAN Performance Measurement ResultsThis task is p erformed on the M2000 client to query and save RAN performance measurementresults.

3.4 Querying and Saving RNC Operation LogsThe operatio n information is recorded on the M2000 client. You can q uery the information ona visualized i nterface and save the results in category.

3.5 Querying and Saving Other RNC LogsThis describe s how to query and save other RNC logs on the M2000 client. Other logs refer tohost logs, BAM logs, database logs, and system event logs.

3.6 Querying and Saving NodeB Operation LogsThe operation information is recorded on the M2000 client. You can query the information ona visualized interface and save the results in category.

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

3.8 Checking the Automatic Backup of NEs on the M2000This describes how to check the automatic backup of network elements (NEs) on the M2000.

3.9 Checking Cell State and ResourcesThis task checks the cell state and cell resources on the M2000.

3.10 Checking the State of Interfaces on the RNC (over ATM)

RANRoutine Maintenance Guide 3 RAN Daily Maintenance Guidelines


3-1



This task checks the states of RNC interfaces and links on the M2000 client in ATM transportmode.

3.11 Checking the State of Interfaces on the RNC (over IP)This task checks the states of RNC interfaces and links on the M2000 client in IP transport mode.

3 RAN Daily Maintenance GuidelinesRAN



Issue 01 (2009-02-10)



3.1 Monitoring RAN Alarms on the M2000This task monitors RAN alarms on the M2000 client. The alarms are of two types: fault alarmsand event alarms.

3.1.1 Monitoring RAN Current Fault Alarms on the M2000This task queries all the current fault alarms of the RNC and the NodeB.

3.1.2 Monitoring RAN Event Alarms on the M2000This task queries all the event alarms of the RNC and the NodeB.

3.1.1 Monitoring RAN Current Fault Alarms on the M2000This task queries all the cur rent faul t alarm s of the RNC and the NodeB.

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

l You have the permission to query alarms.

Procedure

Step 1 Choose Monitor > Current Fault Alarms on the M2000 client. The Filter dialog box isdisplayed.

Step 2 Select the conditions in the Filter dialog box.

Step 3 Click OK . Then the current fault alarms are displayed in the Current Fault Alarms tab.

Step 4 To view details of an alarm, double-click the alarm. The Detail Information dialog box isdisplayed.

NOTE

When select an alarm you can find some information:

l In Alarm Detail Information tab you can find the details of an alarm

l In Process Advice tab you can click the link to check the process advice of an alarm.

Step 5 Contact corresponding personnel to handle and acknowledge uncleared alarms and to analyzeand acknowledge those automatically cleared alarms.

Records of the acknowledged and cleared alarms are removed from the window.

Step 6 In the Detail Information dialog box, double-click the Alarm Experience tab. Then you mayrecord the symptom, cause and handling method of the alarm in Modify Experience dialog box.

Step 7 Repeat Step 4 through Step 6 to handle the alarms one by one until no fault alarms are generated.

NOTE

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

1. Specif y query conditions and click Template .

2. Click Save As .

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

----End



3-3



3.1.2 Monitoring RAN Event Alarms on the M2000This task queries all the event alarms of the RNC and the NodeB.


l You have the permission to query alarms.

Procedure

Step 1 Choose Monitor > Event Alarms on the M2000 client. The Filter dialog box is displayed.

Step 2 Select the conditions in the Filter dialog box.

Step 3 Click OK . Then the event alarms are displayed in the Event Alarms tab.

Step 4 Double-click the alarm. The Detail Information dialog box is displayed.

NOTE

When select an alarm you can find some information:

l In Alarm Detail Information tab you can find the details of an alarm

l In Process Advice tab you can click the link to check the process advice of an alarm.

Step 5 Contact corresponding personnel to analyze and acknowledge the event alarms.

Records of those acknowledged alarms are deleted from the window.

Step 6 In the Detail Information dialog box, double-click the Alarm Experience tab. Then you mayrecord the symptom, cause a nd handl ing me thod of the alarm in Modify Experience dialog box.

Step 7 Repeat Step 4 through Step 6 to handle other alarms one by one until no event alarms aregenerated.

NOTE

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

1. Specify query conditions and click Template .

2. Click Save As .


----End

3.2 Collecting Statistics About RNC and NodeB AlarmsThis task sorts out alarms generated on the RNC and the NodeB according to NE types, alarmseverities, or alarm types. This task also saves the result.


l You have the permission to operate on the corresponding NEs.

l You have the permission to sort out alarms.




Issue 01 (2009-02-10)



Procedure

Step 1 Choose Monitor > Fault Alarm Statistics or Monitor > Event Alarm Statistics on the M2000client. The Statistic Filter dialog box is displayed.

Step 2 Select the conditions in the Statistic Filter dialog box.

Step 3 Click OK . Then the Fault Alarm Statistics or Event Alarm Statistics tab displays the result.

The query results are displayed in the Table and Pie tab pages.l The Table tab page displays the statistics in a table.

l The Pie tab page displays different pies, depending on different measurement items.

Step 4 Click Save As . Then specify the file type and path and save the statistics.l Click the Table tab in the result pane, and then save the file in .txt, .csv, or .html format.

l Click the Pie tab in the result pane, and then save the file in .jpg format.

Step 5 Record the statistics in the daily maintenance record.

NOTE

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

1. Specif y statistic conditions and click Template .

2. Click Save As .


----End

3.3 Querying and Saving RAN Performance MeasurementResults

This task is performed on the M2000 client to query and save RAN performance measurementresults.

3.3.1 Querying the Results of Major Performance Measurement CountersThis task queries the results of performance measurement counters reported on the M2000 at aninterval of 0.5, 1, or 24 hours so that you can check whether the RNC is functional.

3.3.2 Saving the Results of Major Performance Measurement CountersThis task saves results of the performance measurement in a file through the M2000 client.

3.3.1 Querying the Results of Major Performance MeasurementCounters

This task queries the results of performance measurement counters reported on the M2000 at aninterval of 0.5, 1, or 24 hours so that you can check whether the RNC is functional.


l There are objects to be measured.



3-5



l You have the permission to query the results of the RNC performance measurementcounters.

ContextTable 3-1 lists the performance counters.

Table 3-1 Performance counters

Category 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

Inter-RAT handover success rate Outgoing voice servicehandover

Outgoing PS servicehandover

Availability Paging congestion rate All services

DL transmission resource usage All servicesUL transmission resource usage All services

ProcedureChoose Performance > Query Result on the M2000 client. The Query Result window isdisplayed.




Issue 01 (2009-02-10)



If... Then...

You use a template for the query Right-click a template in the navigation tree onthe left and choose Query Result from theshortcut menu. Choose a query time from thesubmenu of Query Result .

You need to specify new queryconditions

1. In the Query Result window, click NewQuery . The Query dialog box is displayed.

2. Select the measurement item corresponding tothe RNC in the navigation tree on the left.

3. In the Object Settings , Counter Settings , andOther Settings tabs of the right pane, specifythe object, counter, and period for

measurement.4. Click Query .

The system displays the query results.

NOTE

l If the measurement result contains a Reliability field, the measurement result is reliable only when thevalue of this field is Reliable .

l Compare the values of these items with those required by the site. If you find any inconsistency, reportit to engineers for troubleshooting.

l

For descriptions of the listed performance counters, refer to the RAN Performance Management Guidelines .

----End

3.3.2 Saving the Results of Major Performance MeasurementCounters

This task saves results of the performance measurement in a file through the M2000 client.

Prerequisitel Connection between the M2000 client and the M2000 server is operational.l Performance measurement results are queried.

Procedure

In the Query Result window, save the information through the shortcut menu.l When the results are displayed in a table, right-click in 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 should be displayed in a line chart or a bar chart, right-click Save , and then save

the file in .jpg format.

----End



3-7



3.4 Querying and Saving RNC Operation LogsThe operation information is recorded on the M2000 client. You can query the information ona visualized interface and save the results in category.

Prerequisitel Connection between the M2000 client and the M2000 server is operational.l The M2000 user logs and the RNC operation logs are synchronized. For details about how

to synchronize 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 RNC.

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.5 Querying and Saving Other RNC LogsThis describes how to query and save other RNC logs on the M2000 client. Other logs refer tohost logs, BAM 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 RNC.

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

is displayed.

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

NOTE

If this function is used for the first time, a dialog box will be displayed, prompting you to download theMML command configuration file of the current version of the NE when the NE is selected. Click Yes todownload 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 asfollows:




Issue 01 (2009-02-10)



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 starttime of the current maintenance.

Save the result in the zip format in the BAM active workspace installation directory \FTPdirectory.

NOTE

l The information collected in this operation involves RNC running logs, RNC operation logs, and thecorresponding alarms.

l The log files that are not compressed in the BZ2 format in the BAM active workspace installationdirectory \common\fam\famlog and the BAM active workspace installation directory \common\fam\famlogfmt directories will not be saved.

l For the directory structure of BAM workspace, seeInstallation Directory of the BAM Application.

----End

3.6 Querying and Saving NodeB Operation LogsThe operation information is recorded on the M2000 client. You can query the information ona visualized interface and save the results in category.


l The M2000 user logs and the NodeB operation logs are synchronized. For details abouthow 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 Saving NodeB other logsOther NodeB logs consist of the main board log, operation log, board log, and RTWP routinetest log.



3-9




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.

Procedurel In GUI mode

1. Choose Software > Browser on the M2000 client. The Software Browser windowis displayed.

2. Click the NE tab in the navigation pane on the left, and then select the NodeB to be backed up.

3. Click the Other tab in the right pane. The NodeB log files are displayed.

4. Select the file to be saved and click Transfer > Upload from Client to NM to savethe file on the server.

l In MML mode

1. Choose Maintenance > MML Command on the M2000 client. The MMLCommand window is displayed.

2. Select the NodeB in the navigation tree on the left. The navigation tree of NodeBMML commands is displayed.

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

parameters as follows:– Enter a name in Destination File .

– 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 .

– Specify FTP Server IP .

– 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 of NEs on the M2000This describes how to check the automatic backup of network elements (NEs) on the M2000.

Prerequisitel The M2000 client is properly connected to the server.

l You have the right to operate the M2000 system tool.




Issue 01 (2009-02-10)



Procedure

Step 1 On the M2000 client, choose Maintain > Task Management . The Task Management windowis displayed.

Step 2 Expand the Backup node and click NE Backup in the left navigation pane. Check whether thetask for automatic backup of NEs exists on the task list on the right.

If... Then...

An NE automatic backup task exists, The automatic backup function of the NE isnormal.

An NE automatic backup task does not exist, Perform Step 3 through Step 7 .

Step 3 Click New ,NOTE

or double-click NE Backup under the Backup node. The New Task dialog box is displayed.

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

l Enter a name in Task Name .

l Select NE Backup for Task Type .

l Select Period for Run Type .

Step 5 Click Next , and set Time Setting and Period Setting .

Step 6 Click Next , and set NE Type to RNC and all the NodeB models.

NOTE

Only the configuration data on the RNC can be automatically backed up.

Step 7 Click Finish . Now the new task is displayed on the task list.

----End

3.9 Checking Cell State and ResourcesThis task checks the cell state and cell resources on the M2000.

3.9.1 Checking the States of All CellsThis task checks the state of all cells and saves the results.

3.9.2 Checking the States of Faulty CellsThis task queries the cells whose administrative state is Not blocked and operational state isUnavailable on the M2000 client.

3.9.3 Checking Cell ResourcesThis task checks the cell resources including the number of subscribers in the cell and the total

Receiving Total Wideband Power (RTWP) of the cell. The check result reflects the current performance of the cell.



3-11



3.9.1 Checking the States of All CellsThis task checks the state of all cells and saves the results.


l You have the permission to run RNC query commands.

Procedure

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

Step 2 Select an RNC to be checked from the navigation tree on the left. The navigation tree of theRNC MML commands is displayed.

Step 3 Run DSP CELL to check the state of all the 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, refer to the HelpInformation on the interface.

NOTE

Validation: The operational states of the cells should be Available .

Step 4 Right-click the Common Maintenance tab. Choose Save As , specify the file name and path,

and then click Save . The result is saved in the specified file.----End

3.9.2 Checking the States of Faulty CellsThis task queries the cells whose administrative state is Not blocked and operational state isUnavailable on the M2000 client.



Procedure


Step 2 Select an RNC to be checked from the navigation tree on the left. The navigation tree of theRNC MML commands is displayed.

Step 3 Run DSP CELL to query the faulty cells. Here, set the parameters as follows:l Set Query type to BYCELLSTATE .

l Set Cell operate state to UNAVAILABLE .




Issue 01 (2009-02-10)



l Set Cell administrate state to UNBLOCK .

l Leave other parameters empty.

The execution result is displayed. For the meaning of the result, refer to the HelpInformation on the interface.

Step 4 Right-click the Common Maintenance tab. Choose Save As , specify the file name and path,and then click Save . The result is saved in the specified file.

Step 5 Record the cell ID. For more information, run DSP CELLCHK . Here, set Check Scope toCELLID and specify the previously recorded Cell ID . Further locate the cause of the fault onthe cell and contact corresponding personnel to handle it.

Step 6 For the faulty cells that are found through Step 3 , repeat Step 5 for each cell until all the faultyare cleared.

----End

3.9.3 Checking Cell ResourcesThis task checks the cell resources including the number of subscribers in the cell and the totalReceiving Total Wideband Power (RTWP) of the cell. The check result reflects the current

performance of the cell.


l You have the permission to query the results of the RNC performance measurementcounters.

Context

Table 3-2 lists the cell resources to be checked.

Table 3-2 Measurement counters of cell resources

Performance Item

MeasurementCounter

Description Criteria for Reference

Number of subscribersin the cell

VS.CellDCHUEs

VS.CellFACHU

Es

Measurement object: Cell

Location of the counters:

Measurement related toRadio Resource Control >RRC connection setupmeasurement per cell

These two countersmeasure the number of subscribers on thededicated and thecommon channelsrespectively.

If both are 0, it is anindication that there areno subscribers carried onthe cell. A fault mayoccur in the cell.



3-13



Performance Item

MeasurementCounter

Description Criteria for Reference

Measurement of the cellRTWP

VS.MeanRTWP

VS.MaxRTWPVS.MinRTWP

Measurement object: Cell

Location of the counters:Measurements related toMeasurement Report >Cell TX and RX PowerMeasurement per cell

These items measure theuplink load of a cell.

Larger value meansheavier load.

Procedure

Choose Performance > Query Result on the M2000 client. The Query Result window isdisplayed.

If... Then...

You use a template for the query Right-click a template in the navigation tree onthe left and choose Query Result from theshortcut menu. Then, select a query time from thesubmenu of Query Result .

You need to specify new queryconditions

1. In the Query Result window, click NewQuery . The Query dialog box is displayed.

2. Select the measurement item corresponding tothe RNC in the navigation tree on the left.

3. In the Object Settings , Counter Settings , andOther Settings tabs of the right pane, specifythe object, counter, and period for measurement.

4. Click Query .

The system displays the query results.

NOTE

l If the measurement result contains a Reliability field, the measurement result is reliable only when thevalue of this field is Reliable .

l Compare the values of these items with the reference standards in Table 3-2 . If you find anyinconsistency, report it to corresponding personnel for troubleshooting.

----End

3.10 Checking the State of Interfaces on the RNC (overATM)

This task checks the states of RNC interfaces and links on the M2000 client in ATM transport

mode.




Issue 01 (2009-02-10)



3.10.1 Checking the State of an Interface on the Physical Layer (over ATM)This task checks the state of an interface on the RNC physical layer in ATM transport mode.The task checks the state of the optical port, E1/T1 link, UNI link, IMA link, IMA group,fractional IMA/ATM link, and timeslot cross-connects.

3.10.2 Checking the State of an SAAL Link This task checks the state of an SAAL link.

3.10.3 Checking the State of an MTP3This task checks the state of an MTP3.

3.10.4 Checking the State of an SCCPThis task checks the state of the SCCP.

3.10.5 Checking the State of an AAL2 PathThis task checks the state of the AAL2 path.

3.10.6 Checking the State of an NCP or CCP (over ATM)

This task checks the state of the NCP and CCPs between the RNC and the NodeB in ATMtransport mode.

3.10.1 Checking the State of an Interface on the Physical Layer (overATM)

This task checks the state of an interface on the RNC physical layer in ATM transport mode.The task checks the state of the optical port, E1/T1 link, UNI link, IMA link, IMA group,fractional IMA/ATM link, and timeslot cross-connects.



ContextNOTE

The links described in this task cover all types of links that the RNC may use in ATM transport mode. Inroutine maintenance, link management is based on the RNC configuration.

Table 3-3 describes the criteria for physical layer interface status in ATM transport mode.

Table 3-3 Cr iteria for physical layer interface status in ATM transport mode

Check Item Criteria for Reference

Optical port status and performance statistics

Optical port state : Normal

State of E1/T1 links Link running state : Link available

State of IMA groups l Near end state : Group operational

l Far end state : Group operational



3-15




State of IMA links l Near end Tx state : Active

l Near end Rx state : Active

l Far end Tx state : Active

l Far end Rx state : Active

l Near end Rx failure state : Not failed

l Far end Rx failure state : Not failed

State of UNI links Link state : Normal

State of fractional ATM links Link state : Normal

State of fractional IMA links l Near end Tx state : Active

l Near end Rx state : Active

l Far end Tx state : Active

l Far end Rx state : Active

l Near end Rx failure state : Not failed

l Far end Rx failure state : Not failed

Timeslot cross state output enable flag : Switch normal

Procedure


Step 2 Select the RNC in the navigation tree on the left. The navigation tree of RNC MML commandsis displayed.

Step 3 Run DSP OPT to check the optical port status and performance measurement results. Here, setthe parameters as follows:l Specify Subrack No. and Slot No. .

l Select board type based on actual configuration.

NOTE

When board type is set to AOU , you need to set Perfomace type. to LINK and then enter the PortNo. .

Step 4 Run DSP E1T1 to check the state of all the E1/T1 links on the board. Here, set the parametersas follows:l Specify Subrack No. and Slot No. .

l Select Board type based on actual configuration.

l Leave Link No. empty.

Step 5 Run DSP IMAGRP to check the state of all the IMA groups on the board. Here, set the parameters as follows:

l Specify Subrack No. and Slot No. .




Issue 01 (2009-02-10)



l Leave IMA group No. empty.

Step 6 Run DSP IMALNK to check the state of all the IMA links on this board. Here, set the parametersas follows:l

Specify Subrack No. and Slot No. .l Leave IMA link No. empty.

Step 7 Run DSP UNILNK to check the state of all the UNI links on this board. Here, set the parametersas follows:l Specify Subrack No. and Slot No. .

l Leave UNI link No. empty.

Step 8 Run DSP FRALNK to check the state of all the fractional IMA links and fractional ATM links.Here, set the parameters as follows:l Specify Subrack No. and Slot No. .

l Set Link type to ALL .

l Leave Fractional link No. empty.

Step 9 Run DSP TSCROSS to check all timeslot cross state. Here, set the parameters as follows:l Specify Subrack No. and Slot No. .

l Leave Time slot cross index empty.

NOTE

Perform Step 3 through Step 9 to query the state of the links that are actually configured on the RNC. For the links whose state is abnormal, note them down and contact corresponding personnel for troubleshooting.

----End

3.10.2 Checking the State of an SAAL LinkThis task checks the state of an SAAL link.



Procedure



Step 3 Run DSP SAALLNK to check the state of all the SAAL links in a specified SPU subsystem.Here, set the parameters as follows:l Specify Subrack No. , Slot No. .

l Leave SAAL link No. empty.



3-17



NOTE

If any SAAL link is found unavailable, contact corresponding personnel for troubleshooting until the stateof all the SAAL links is Available .

----End

3.10.3 Checking the State of an MTP3This task checks the state of an MTP3.



Context

Table 3-4 describes the criteria for MTP3 state.

Table 3-4 Criteria for MTP3 state


State of the OSP l SCCP OSP state : Available

l SCCP state : Available

l SCCP OSP congested state : Not congested

l MTP3 OSP state : Available

l MTP3 OSP congested state : Not congested

State of the DSPs l SCCP DSP state : Accessible

l Peer SCCP state: : Available

l SCCP DSP congested state : Not congested

l MTP3 DSP state : Available

l MTP3 DSP congested state : Not congested

State of MTP3 signalinglink sets

l Operation state : Available

State of MTP3 signalinglink

l Administrative state : Local management uninhibited

l Operational state : Available

l Activated state : Activated

l Congested state : Not congested

State of MTP3 signalingroutes






Issue 01 (2009-02-10)



Procedure



Step 3 Run DSP OPC to check the state of the OSP.

Step 4 Run DSP N7DPC to check the state of all the DSPs. Here, leave DSP index empty.

Step 5 Run DSP MTP3LKS to check the state of all the MTP3 signaling link sets. Here, leaveSignalling linkset index empty.

Step 6 Run DSP MTP3LNK to check the state of all the MTP3 signaling links. Here, set Querytype to BYLKS (QUERY BY LINKSET) .

Step 7 Run DSP MTP3RT to check the state of all the signaling routes. Here, leave all parametersempty.

NOTE

If there is any link found not in compliance with the criteria listed in Table 3-4 , contact corresponding personnel for troubleshooting.

----End

3.10.4 Checking the State of an SCCPThis task checks the state of the SCCP.



Procedure

Step 1 Choose Maintenance > MML Command on the M2000 client. The MML C ommand windowis displayed.


Step 3 Run DSP SSN to check the state of all the SCCP SSNs. Here, leave the parameters empty.

NOTE

If SCCP SSN state is Prohibited , contact corresponding personnel to handle it until the state is Allowed .

----End

3.10.5 Checking the State of an AAL2 PathThis task checks the state of the AAL2 path.



3-19





Procedure



Step 3 Run DSP AAL2PATH to check the state of all the AAL2 paths. Here, set the parameters asfollows:l Enter Adjacent node ID .

l Leave AAL2 path ID empty.NOTE

If the operation state of the AAL2 path is Unavailable , you can infer that the path is abnormal. Contactcorresponding personnel for troubleshooting until it is Available .

----End

3.10.6 Checking the State of an NCP or CCP (over ATM)This task checks the state of the NCP and CCPs between the RNC and the NodeB in ATMtransport mode.



Procedure



Step 3 Run DSP IUBCP to check the operational state of the NCP and CCPs on the Iub interface. Here,specify the NodeB name and set Port type to ALL_TYPE .

NOTE

If the operational state of the NCP or CCPs is Unavailable , contact corresponding personnel for troubleshooting until it is Available .

----End

3.11 Checking the State of Interfaces on the RNC (over IP)This task checks the states of RNC interfaces and links on the M2000 client in IP transport mode.




Issue 01 (2009-02-10)



3.11.1 Checking the State of an Interface on the Physical Layer (over IP)This task checks the state of an interface on the RNC physical layer in IP transport mode. Thetask checks the state of the E1/T1 link, UNI link, IMA link, IMA group, fractional IMA/ATMlink, and FE port.

3.11.2 Checking the State of an SCTP Link This task checks the state of the SCTP link.

3.11.3 Checking the State of an M3UAThis task checks the state of an M3UA.

3.11.4 Checking the State of an IP PathThis task checks the state of the IP path.

3.11.5 Checking the State of an NCP or CCP (over IP)This task checks the state of the NCP and CCPs between the RNC and the NodeB in IP transportmode.

3.11.1 Checking the State of an Interface on the Physical Layer (overIP)

This task checks the state of an interface on the RNC physical layer in IP transport mode. Thetask checks t he state of the E1/T1 link, UNI link, IMA link, IMA group, fractional IMA/ATMlink, and FE port.



ContextNOTE

The links described in this task cover all types of links that the RNC may use in IP transport mode. Inroutine maintenance, link management is based on the RNC configuration.

Table 3-5 describes the criteria for physical layer interface status in IP transport mode.

Table 3-5 Criteria for physical layer interface status in IP transport mode


State of E1/T1 links Link running state : Link available

State of PPP links Link state : UP

State of MLPPP links Link state : UP

State of MLPPP groups Link state : Normal

Timeslot cross state output enable flag : Switch normal

State of FE port Link Availability state : Available



3-21



Procedure



Step 3 Run DSP E1T1 to check the state of all the E1/T1 links on the board. Here, set the parametersas follows:l Specify Subrack No. and Slot No. .

l Select Board type based on actual configuration.

l Leave Link No. empty.

Step 4 Run DSP PPPLNK to check the state of all the PPP links in the specified slots. Here, set the parameters as follows:

l Specify Subrack No. and Slot No. .l Leave PPP link No. empty.

Step 5 Run DSP MPLNK to check the state of the specified MLPPP links. Here, set the parameters asfollows:l Specify Subrack No. and Slot No. .

l Leave MLPPP link No. empty.

Step 6 Run DSP MPGRP to check the state of the specified MLPPP group. Here, set the parametersas follows:l Specify Subrack No. and Slot No. .

l Enter MLPPP group No. .

Step 7 Run DSP TSCROSS to check all timeslot cross state. Here, set the parameters as follows:l Specify Subrack No. and Slot No. .

l Leave Time slot cross index empty.

Step 8 Run DSP ETHPORT to check the state of all the FE ports . Here, set the parameters as follows:l Specify Subrack No. and Slot No. .

l Leave Port No. empty.

NOTE

Perform Step 3 through Step 8 to query the state of the links that are actually configured on the RNC. For the links whose state is abnormal, note them down and contact corresponding personnel for troubleshooting.

----End

3.11.2 Checking the State of an SCTP LinkThis task checks the state of the SCTP link.






Issue 01 (2009-02-10)



Procedure



Step 3 Run DSP SCTPLNK to check the state of all the SCTP links. Here, set the parameters as follows:

l Specify Subrack No. , Slot No. .

l Leave other parameters empty.

NOTE

If the operational state of the SCTP link is Unavailable , contact corresponding personnel for troubleshooting until it is normal .

----End

3.11.3 Checking the State of an M3UAThis task checks the state of an M3UA.



Context

Table 3-6 describes the criteria for M3UA state.

Table 3-6 Criteria for M3UA state


State of the OSP l SCCP OSP state : Available

l SCCP state : Available

l SCCP OSP congested state : Not congested

l MTP3 OSP state : Available

l MTP3 OSP congested state : Not congested

State of the DSPs l SCCP DSP state : Accessible

l Peer SCCP state: : Available

l SCCP DSP congested state : Not congested

l M3UA DSP state : Available

l M3UA DSP congested state : Not congested

State of the local entities l Operational state : Available



3-23




State of the destinationentities



State of M3UA signalinglink sets


l Activated state : Activated

State of M3UA signalinglink

l Operation state : Activated state

l Administrative state : M3UA uninhibited

l Manual activate flag : Manual activated


State of M3UA signalingroutes


Procedure



Step 3 Run DSP OPC to check the state of the OSP.

Step 4 Run DSP N7DPC to check the state of all the DSPs. Here, leave DSP index empty.

Step 5 Run DSP M3LE to check the state of all the local entities. Here, leave all parameters empty.

Step 6 Run DSP M3DE to check the state of all the destination entities. Here, leave all parametersempty.

Step 7 Run DSP M3LKS to check the state of all the M3UA signaling link sets. Here, leave M3UASignalling linkset index empty.

Step 8 Run DSP M3LNK to check the state of the M3UA signaling links. Here, set the parameters asrequired.

NOTE

Run LST M3LNK to check the configuration data of all the M3UA links. Here, leave all parameters empty.

Step 9 Run DSP M3RT to check the state of the M3UA signaling routes. Here, set the parameters asrequired. The M3UA signaling route information describes the signaling routes from the localentities to the destination entities.

NOTE

If there is any link found not in compliance with the criteria listed in Table 3-6 , contact corresponding personnel for troubleshooting.

----End

3.11.4 Checking the State of an IP PathThis task checks the state of the IP path.




Issue 01 (2009-02-10)





Procedure



Step 3 Run DSP IPPATH to check the state of all the IP paths under the specified adjacent node. Here,specify Adjacent node ID and leave IP path ID empty.

NOTE

If the operational state of the IP path is Unavailable , contact corresponding personnel for troubleshootinguntil it is Available .

----End

3.11.5 Checking the State of an NCP or CCP (over IP)This task checks the state of the NCP and CCPs between the RNC and the NodeB in IP transportmode.



Procedure



Step 3 Run DSP IUBCP to check the operational state of the NCP and CCPs on the Iub interface. Here,specify the NodeB name and set Port type to ALL_TYPE .

NOTE

If the operational state of the NCP or CCPs is Unavailable , contact corresponding personnel for troubleshooting until it is Available .

----End



3-25



4 RAN Weekly Maintenance Guidelines

About This Chap ter

This part des cribes weekly maintenance tasks an d corresponding operations.

4.1 Checking the State of a BAM on the M2000This task checks the state of BAMs. The state information includes the CPU usage, memoryusage, hard d isk space, operational state, IP addresses, and state of the links between the twoBAMs.

4.2 Checking the State of a BAM Module on the M2000This task che cks startup types and operational state of BAM modules.

4.3 Checking the State of an RNC Board on the M2000This task che cks the working state of the RNC boards.

4.4 Checking the State of a NodeB Board on the M2000This task che cks the state of a NodeB board on the M2000 client.

4.5 Checking the State of the RNC Clock on the M2000This task che cks the clock state of the clock sub-boards in the RSS.

4.6 Checking the State of the NodeB Clock on the M2000This task, on the M2000 client, checks the current state of the clock in the basic NodeB cabinet.

4.7 Backing Up RNC System DataThis task describes how to back up the RNC system data on the M2000 client, on the LM, or byusing BamBackup, a BAM backup tool. The RNC system data consists of the RNC configurationdata, performance data, and alarm data.

4.8 Backing Up NodeB Configuration DataThis task describes how to manually back up the NodeB configuration data on the M2000 clientor on the LMT.

RANRoutine Maintenance Guide 4 RAN Weekly Maintenance Guidelines


4-1



4.1 Checking the State of a BAM on the M2000

This task checks the state of BAMs. The state information includes the CPU usage, memoryusage, hard disk space, operational state, IP addresses, and state of the links between the twoBAMs.



Context

Table 4-1 describes the criteria for checking the state of the BAMs.

Table 4-1 Criteria for checking the operational state of the BAMs


State of the BAM In the query result, MEM(%) cannot be higher than 85% and Freespace(%) cannot be smaller than 20%.

Operational stateand datasynchronization

state of the activeand standby BAMs

l Computer name , Internal network fixed IP , External network fixed IP , Internal network virtual IP , and External network virtual IP in the execution results are all consistent with the plan.

l Operational state , Internal network virtual IP state , Externalnetwork virtual IP state , Internal network link state , Externalnetwork link state , and Backup channel state are all Normal .

l Data-sync stat is Data synchronization normal .

Procedure



Step 3 Run DSP BA MSRV to check the operational state of the BAM.

Step 4 Run DSP BAM to check the operational state and data synchronization state of each BAM.

NOTE

l In dual-BAM mode, you may also run CHK PEERCFG to query the configuration information aboutthe active and standby BAMs.

l Table 4-1 describes the criteria for the query results. If any fault occurs, contact corresponding personnel for troubleshooting.

----End

4 RAN Weekly Maintenance GuidelinesRAN



Issue 01 (2009-02-10)



4.2 Checking the State of a BAM Module on the M2000

This task checks startup types and operational state of BAM modules.



Context

Table 4-2 describes the criteria for the state of BAM modules.

Table 4-2 Criteria for the state of BAM modules


Active BAM l State : Started

l Startup Type : Automatic

Standby BAM For SNTP Client, FTP Server, DynMonitor, and FTP Client:l State : Started

l Startup Type : Automatic

For other modules:l State : Stopped

l Startup Type : Disabled

Procedure



Step 3 Run DSP BAMMODULE to check the state of BAM modules.

NOTE

Table 4-2 describes the criteria for the query results. If any fault occurs, contact corresponding personnelfor trouble shooting.

----End

4.3 Checking the State of an RNC Board on the M2000

This task checks the working state of the RNC boards.



4-3





Procedure



Step 3 Run DSP BRD to check the state of all the boards in the RBS and RSS. Here, specify Subrack No. and leave Slot No. empty.

NOTE

If faults occur to the CPU, contact corresponding personnel to clear the faults until the board CPU state isnormal .

----End

4.4 Checking the State of a NodeB Board on the M2000This task checks the state of a NodeB board on the M2000 client.



Procedure


Step 2 Select the NodeB in the navigation tree on the left. You may select multiple NodeBs of the sameversion 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 alarmhandling procedures in Macro NodeB Alarm Reference and Distributed NodeB Alarm Reference .

----End

4.5 Checking the State of the RNC Clock on the M2000This task checks the clock state of the clock sub-boards in the RSS.





Issue 01 (2009-02-10)




ContextNOTE

l It is recommended to query only the state of the GCUa board and not to query the working state of all the board clocks. For the GCUa, the active clock source state used by the system and the handover mode of the active state of phase lock loop can be queried.

l The GCUa boards are permanently configured in slot 12 and slot 13 in the RSS subrack.

Procedure



Step 3 Run DSP CLK to check the state of the RSS clock board. Here, set Subrack No. to 0 and specifySlot No. .

NOTE

If one level state of the clock source is Unavailable or clock working state is Unknown , it is an indicationthat the clock source is lost. Contact corresponding personnel for troubleshooting until the state becomesAvailable or Fast Tracking respectively.

----End

4.6 Checking the State of the NodeB Clock on the M2000This task, on the M2000 client, checks the current state of the clock in the basic NodeB cabinet.



ProcedureStep 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. You may select multiple NodeBs of the sameversion 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 byrunning DSP CLKSTAT .

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



4-5



If... Then...

The OCXO clock source is unavailable, orCurrent work mode is inconsistent with theset 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 isexceptional.

Current working oscillator is of the TCXOtype

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 sta tus : LOCKED .

l Current oscillator : OCXO .

----End

4.7 Backing Up R NC System DataThis task des cribes how to back up the RNC system data on the M 2000 client, on the LM, or by

using BamBackup, a BAM backup tool. The RNC system data consists of the RNC configurationdata, performance data, and alarm data.

4.7.1 Automatically Backing Up RNC System DataThis describes how to set automatic backup task of the RNC system data on the LMT. The systemdata consists of the RNC configuration data, performance data, and alarm data.

4.7.2 Manually Backing Up RNC System Data on the LMTThis task describes how to manually back up the RNC system data on the LMT. The systemdata consists of the RNC configuration data, performance data, and alarm data.

4.7.3 Backing Up RNC System Data Manually(Using BamBackup Tool)

This describes how to manually back up the configuration data, performance data, and alarmdata. You can perform this task in MML mode or by using the backup and restore tool.

4.7.1 Automatically Backing Up RNC System DataThis describes how to set automatic backup task of the RNC system data on the LMT. The systemdata consists of the RNC configuration data, performance data, and alarm data.

Prerequisitel You have logged in to the RNC LMT.

l You have the right to configure data on the RNC.




Issue 01 (2009-02-10)



Procedure

Step 1 On the MML client, run the ADD SCHTSK command, and then set Task ID and Task Name to add a scheduled task.

Step 2 On the MML client, run the ADD SUBTSK command, and then set parameters as follows toadd a scheduled subtask for backing up the RNC system data:

1. Set Task ID or Task Name .

NOTE

Task ID or Task Name cannot be specified at the same time.

2. Set Subtask ID .

3. Set Subtask Status to ENABLED(available) .

4. Set Command String to BKP DB .

For rules of setting the command string parameter, see the Help Information of the ADDSUBTSK command on the LMT.

5. Set Time Mode .

Step 3 To check whether the subtask is successfully created, run the LST SUBTSK command. Tomodify the backup time or period, run the MOD SUBTSK command.

----End

ResultAfter the backup tasks are performed, you can obtain the latest backup files from the specified

path on the BAM. For the descriptions of Path of Backup File and Backup File Name , see theHelp Information of the BKP DB command.

NOTE

The automatically named backup files will not overwrite the earlier backup files. If there are already seven backup files saved in the path, the system automatically deletes the file backed up at the earliest time byrunning the BKP DB command before saving a new one.

Example

To set a scheduled task for backing up the RNC system data and set its start time to 2007-04-1212:00:00, run the following command:

ADD SUBTSK: ID=1, SUBID=8, SCMD="BKP DB:", FREQ=ONTIME, SD=2007&04&12,TM=12&00;

4.7.2 Manually Backing Up RNC System Data on the LMTThis task describes how to manually back up the RNC system data on the LMT. The systemdata consists of the RNC configuration data, performance data, and alarm data.

Prerequisite

You are logged in to the RNC LMT.



4-7



Context

CAUTIONl If the RNC is configured with two OMUa boards, that is, in dual-BAM mode, you must

back up data on the active BAM.l You must manually back up the BAM database before capacity expansion or upgrade.

ProcedureOn the MML client, run BKP DB , and then set Path of Backup File and Backup File Nameto save the backup data to the specified path.

NOTE

l All configuration data is backed up. Part of performance data and alarm data are backed up. Inemergency, using backup alarm data and performance data to restore the system data leads to the lossof some history data and real-time data.

l The specified backup path is the file path on the BAM. The path is automatically created if it does notexist. If the file name is not specified, the backup file is automatically named BKPDB * .bak (* is the

backup time.)

----End

ResultYou can get the backup files in the specified directory on the FTP client or through remote login

to the BAM.

4.7.3 Backing Up RNC System Data Manually(Using BamBackupTool)

This describes how to manually back up the configuration data, performance data, and alarmdata. You can perform this task in MML mode or by using the backup and restore tool.

Prerequisitel For performing backup using the MML commands: You have logged in to the LMT. The

communication between the LMT and the BAM is normal.l For performing backup using the omu_backup_restore_tool:

– You have logged in to the BAM in remote mode. For details, see Remotely Logging Into the BAM.

– The omu_backup_restore_tool is started. For details, see Start theomu_backup_restore_tool.




Issue 01 (2009-02-10)



Context

CAUTIONl In dual-BAM mode, you must back up data on the active BAM.

l You must manually back up the BAM database before capacity expansion, upgrade, or load.

Procedurel Using the MML command

1. On the MML client, run the BKP DB command, and then set Path of Backup Fileand Backup File Name to back up the data in the specified directory.

You can obtain the backup files from the specified directory through the FTP clientor by directly logging in to the BAM.

l Using the backup tool

1. Enter backup and then press Enter in the window, as shown in Figure 4-1 .

Figure 4-1 omu_backup_restore_tool interface

2. Enter the save path and name of the backup file, and then press Enter.

3. The data starts to be restored. The system displays the result, as shown in Figure4-2 .



4-9



Figure 4-2 Backup progress prompt

4. Pre ss any key to exit.

----End

4.8 Backing Up NodeB Configuration DataThis task describes how to manually back up the NodeB configuration data on the M2000 clientor on the LMT.

4.8.1 Automatically Backing Up NodeB Configuration DataThis task describes how to automatically back up the NodeB configuration data on the M2000client.

4.8.2 Manually Backing Up NodeB Configuration Data on the M2000This task describes how to manually back up the NodeB configuration data on the M2000 client.

4.8.3 Manually Backing Up NodeB Configuration Data on the LMTThis task describes how to manually back up NodeB configuration data, namely, how to upload

NodeB data configuration file from the NodeB to the FTP server. By performing this task, youcan save or query the data configuration file later.

4.8.1 Automatically Backing Up NodeB Configuration DataThis task describes how to automatically back up the NodeB configuration data on the M2000client.





Issue 01 (2009-02-10)



l The M2000 server properly communicates with the NodeB.

Procedure

Step 1 On the M2000 client, choose Maintenance > Task Management .Step 2 Double-click NE Backup under the Backup node or click New in the lower part of the window.

Step 3 Enter a task name in the Task Name box and then select NE Backup for Task Type andPeriod for Run Type .

Step 4 Click Next and set Time Setting and Period Setting as required.

Step 5 Click Next and set NE Type to all the NodeB models.

File Path , specified by the M2000, is the main path for storing backup files. Based on NE types, backup files are stored to different paths under this main path.

Step 6 Click Finish .

----End

ResultThe NodeB configuration data files are backed up in the directory M2000 server /export/home/sysm/ftproot/NodeB/Data/ NE FDN at the scheduled time. The name of the backup file isAUTOBAKDATA * (* is the backup time.)

NOTE

The NE model is identified only by the NE FDN. For example, .3221229568.3221233664.3221287025 isan NE FDN.

Postrequisite

Through this task, data of a class of NEs is backed up. If you want to view the data of a specified NE, you need to know the FDN of this NE.

On the M2000 client, choose Configuration > MIT Browser . The MIT Browser window isdisplayed, showing the NE MIT tree in the navigation pane on the left. Right-click the NE andchoose Export to export the NE data to the specified path. You can query the NE FDN in theexported files.

4.8.2 Manually Backing Up NodeB Configuration Data on theM2000

This task describes how to manually back up the NodeB configuration data on the M2000 client.


l The M2000 server properly communicates with the NodeB.

Procedure

Step 1 On the M2000 client, choose Maintenance > System Backup . The Backup Managementwindow is displayed.



4-11



Step 2 Click the NE Backup List tab.

Step 3 Expand the navigation tree and select the NodeB whose data needs backing up.

NOTE

You can select multiple NodeBs by holding down Ctrl and clicking the NodeBs.

Step 4 Click Backup .

----End

Result

The NodeB configuration data files are immediately backed up in the directory M2000 Server /export/home/sysm/ftproot/NodeB/Data/ NE FDN . The name of the backup file isBAKDATA * (* is the backup time).

NOTE

The NE model is identified only by the NE FDN. For example, .3221229568.3221233664.3221287025 isan NE FDN.

Postrequisite

Through this task, data of a class of NEs is backed up. If you want to view the data of a specified NE, you need to know the FDN of this NE.

On the M2000 client, choose Configuration > MIT Browser . The MIT Browser window isdisplayed, showing the NE MIT tree in the navigation pane on the left. Right-click the NE andchoose Export to export the NE data to the specified path. You can query the NE FDN in theexported files.

4.8.3 Manually Backing Up NodeB Configuration Data on the LMTThis task describes how to manually back up NodeB configuration data, namely, how to upload

NodeB data configuration file from the NodeB to the FTP server. By performing this task, youcan save or query the data configuration file later.

Procedurel In GUI mode

1. In the navigation pane, click the Maintenance tab.

2. Double-click Software Management > Data Config File Transfer . The DataConfiguration File Transfer dialog box is displayed, as shown in Figure 4-3 .




Issue 01 (2009-02-10)



Figure 4-3 DataConfig File Transfer dialog box

3. Select the Upload (from NodeB to FTP server).

4. Click Modify in the dialog box. The FTP Setting dialog box is displayed, as shownin Figure 4-4 .

Figure 4-4 FTP Setting dialog box



4-13



Table 4-3 describes the fields in the FTP Setting dialog box.

Table 4-3 Fields in the FTP Setting dialog box

Field Description

Use Built-in FTP Server This enables you to decide whether to use a built-in or a specified FTP server. The built-in FTPserver is started by default.

Use Specified FTPServer

IPaddress

The FTP server can be started either from thelocal computer installed with the LMTapplication or from another computer. Here itrefers to the IP address of the FTP server.

User Name

This enables you to specify the user name for logging in to the FTP server.

Passwor d

This enables you to specify the password for logging in to the FTP server.

5. Set the FTP server.

6. Click OK . The FTP Setting dialog box is closed and the DataConfig FileTransfer dialog box is displayed.

7. Set the other parameters in the dialog box.

8. Click Start .l In MML mode

Run the command ULD CFGFILE .

----End




Issue 01 (2009-02-10)



5 RAN Monthly Maintenance Guidelines

About This Chapter

This part describes monthly maintenance tasks and corresponding operations.

5.1 Analyzing Customers ComplaintsThis describes how to identify the causes and analyze the tendency of faults. This task helps tohandle proble ms at points where faults frequently occur.

5.2 Making a Performance ReportThis task makes a RAN performance report based on the fault tendency.

5.3 Checking the Data Consistency Between the RNC FAM and BAM ServersThis task checks configuration consistency between the FAM and the BAM server of the RNC.

5.4 Checking Disk Space of Terminal SystemThe disk space available on the RAN terminal system should meet the specified requirements.

5.5 Checking the Terminal System for VirusesThis task checks viruses on the terminal system. The terminal system consists of the M2000client, RNC LMT, and NodeB LMT.

RANRoutine Maintenance Guide 5 RAN Monthly Maintenance Guidelines


5-1



5.1 Analyzing Customers ComplaintsThis describes how to identify the causes and analyze the tendency of faults. This task helps tohandle problems at points where faults frequently occur.

ContextFor details on how to identify and rectify the common faults, see the RAN Troubleshooting Guide and RAN Emergency Maintenance Guide .

Procedure

Step 1 Collect the fault information of the month and determine the fault coverage and type.

Step 2 Identify the fault causes by using certain methods to compare and analyze possible causes andeliminate impossible ones until the immediate causes are finally determined.

Step 3 Collect statistics on the faults of this month and analyze the fault tendency.

Step 4 Analyze the points where faults frequently occur and identify and handle the problems.

Step 5 Summarize the troubleshooting experience and provide suggestions.

----End

5.2 Making a Performance ReportThis task makes a RAN performance report based on the fault tendency.

Procedure

Step 1 Analyze and locate the faults in this month. For details, refer to 5.1 Analyzing CustomersComplaints .

Step 2 Collect data of monthly performance, such as performance statistics, performance history data,and system monitoring data. This enables you to find the change tendency in performance dataof this month.

Step 3 Collect daily and weekly monitoring reports on routine network performance, and then find outthe change tendency of RAN performance.

Step 4 Make a monthly report on RAN performance by referring to statistics collected in Step 2 andin Step 3 . For details, refer to the RAN Performance Management Guidelines .

----End

5.3 Checking the Data Consistency Between the RNC FAMand BAM Servers

This task checks configuration consistency between the FAM and the BAM server of the RNC.

5 RAN Monthly Maintenance GuidelinesRAN



Issue 01 (2009-02-10)





Contextl FAM: the front administration module or the host, consisting of the switching subsystem

and the service processing subsystem.l BAM: back administration module, that is, the OMUa board in the RNC.

Procedure



Step 3 Run ACT CRC to check data consistency. Here, leave all parameters empty.

The data table that reports the inconsistency of the data between the FAM and the BAM isobtained.

Step 4 If you find any inconsistency in the table, run CMP TBLDATA to compare the records inspecific data and to find differences in the FAM and BAM data tables. Here, set the parametersas follows:l Specify Board type . Other parameter to be set depends on the actual board type.

– For the SPU board, specify Subrack No. , Slot No. , and Subsystem No. .– For the SCU board, specify only Subrack No. .

l Set Data table , that is, the data table that reports the inconsistency of the data between theFAM and the BAM. The data table is obtained after the comparison in Step 3 .

Step 5 Run CMP BRDVER . Here, leave all the parameters empty. The system compares the versionused by the host with that saved on the BAM server.

NOTE

If there is inconsistency in Step 4 and Step 5 , contact corresponding personnel for troubleshooting. Ensurethat the data and the version of the FAM are consistent with those of the BAM.

----End

5.4 Checking Disk Space of Terminal SystemThe disk space available on the RAN terminal system should meet the specified requirements.

Contextl For the M2000 client, NodeB LMT, and RNC LMT, the spare space of the hard disk should

be at least 50% of the total capacity.l

For drives C, D and E on the BAMs, the free space on each disk should be no less than20% of its capacity. The total free space on the disks should be no less than 1.5 GB.

RANRoutine Maintenance Guide 5 RAN Monthly Maintenance Guidelines


5-3



Procedure

Step 1 Check whether there are temporary files. If there are temporary files, delete them.

Step 2 Check whether there are unnecessary programs. If there are unnecessary programs, delete them.

Step 3 Check whether there are unnecessary backup files. If there are unnecessary backup files, deletethem or move them to another magnetic medium.

----End

5.5 Checking the Terminal System for VirusesThis task checks viruses on the terminal system. The terminal system consists of the M2000client, RNC LMT, and NodeB LMT.

ProcedureUse antivirus software to clear viruses on the computer.

----End

5 RAN Monthly Maintenance GuidelinesRAN



Issue 01 (2009-02-10)



6 RAN Routine Maintenance Record

About This Chapter

The RAN Routine Maintenance Record is used to record the information about the equipment performance state during the maintenance.

6.1 RAN Daily Maintenance RecordThis part provides the RAN daily maintenance record for recording daily routine maintenanceon the site.

6.2 RAN We ekly Maintenance RecordThis part pro vides the RAN weekly maintenance record for recording weekly routinemaintenance.

6.3 RAN Mo nthly Maintenance RecordThis part pro vides the RAN monthly maintenance record for recording monthly routinemaintenance.

RANRoutine Maintenance Guide 6 RAN Routine Maintenance Record


6-1



6.1 RAN Daily Maintenance RecordThis part provides the RAN daily maintenance record for recording daily routine maintenanceon the site.

After the daily routine maintenance tasks are performed, record the checking result in Table6-1 .

Table 6-1 RAN daily maintenance record

BasicInformation

Operator

Time

S

N

Item Criteria for Reference Current Result Description

1 Queryingcurrent faultalarms

There is no fault alarm of theRNC and NodeB.

2 Queryingcurrent eventalarms

There is no event alarm of theRNC and NodeB.

3 Collectingstatisticsabout RNC

and NodeBalarms

–

4 Checking thestates of allcells

The operational states of thecells are Available .

5 Checking thestates of faulty cells

–

6 Checking cellresources

–

7 Checking thestate of a

physical link

Refer to Criteria for physicallayer interface status in ATMtransport mode and Criteriafor physical layer interfacestatus in IP transport mode .

8 Checking thestate of anSAAL link

The operational state of theSAAL link is Available .

6 RAN Routine Maintenance RecordRAN



Issue 01 (2009-02-10)



BasicInformation

Operator

Time

SN


9 Checking thestate of anMTP3-B

Refer to Criteria for MTP3state .

10

Checking thestate of anSCCP

The state of the SCCP SSN isAllowed .

11

Checking thestate of anAAL2 path

The operational state of the theAAL2 path is Available .

12

Checking thestate of an

NCP or CCP

The operational states of the NCP and the CCP areAvailable .

13

Checking thestate of anM3UA

Refer to Criteria for M3UAstate .

14

Checking thestate of an IP

path

The operational state of the theIP path is Available .

15

Checking theState of anSCTP link

The operational state of theSCTP link is Normal .

16

Querying andsaving theresults of major RAN

performancemeasurementcounters

The performance measurementcounters meet the siterequirements.

17

Querying andsaving RNCoperationlogs

–

18

Querying andsaving

NodeBoperationlogs

–



6-3



BasicInformation

Operator

Time

SN


19

Querying andsaving RNCother logs

–

20

Saving NodeB other logs

–

21

Checking theautomatic

backup of NEs on theM2000

The automatic backup functionof the NE is operational.

6.2 RAN Weekly Maintenanc e Re cordThis part provides the RAN weekly maintena nce record for recordin g weekly routinemaintenance.

After the weekly routine maintenance tasks are performed, record the checking result in Table6-2 .

Table 6-2 RAN weekly maintenance record

BasicInformation

Operator

Time

SN Item Criteria for Reference Current Result Description

1 Checkingthe state of a BAM

Refer to Criteria for checkingthe operational state of theBAMs .

2 Checkingthe state of a BAMmodule

Refer to Criteria for the state of BAM modules .

3 Checkingthe state of an RNC

board

The state of each board CPU isNormal .

4 Checkingthe state of an NodeB

board

The state of each board is normal.




Issue 01 (2009-02-10)



BasicInformation

Operator

Time

SN Item Criteria for Reference Current Result Description

5 Checkingthe state of the RNCclock

The state of the clock source isnormal.

6 Checkingthe state of the NodeBclock

The state of the clock source isnormal.

7 Backing upthe RNCsystem data

–

8 Backing upthe NodeBconfiguration data

–

6.3 RAN Monthly Maintenance RecordThis part provides the RAN monthly maintenance record for recording monthly routine

maintenance.After the monthly routine maintenance tasks are performed, record the checking result in Table6-3 .

Table 6-3 RAN monthly maintenance record

Basic Information Operator

Time

SN Item Criteria for Reference Current ResultDescription

1 Analyzingcustomers'complaints

–

2 Making a performancereport

–



6-5



Basic Information Operator

Time

SN Item Criteria for Reference Current ResultDescription

3 Checking thedataconsistency

between theRNC FAMand BAMs

The data and the version of the FAM are consistent withthose of the BAM.

4 Checkingdisk space of terminal

system

The disk space of the terminalsystem meets therequirements.

5 Checking theterminalsystem for viruses

The terminal system is notinfected by viruses.



ran routine maintenance guide(ran11.0_01)

Documents