BSS Routine Maintenance Guide (V900R008C12 - 03)

HUAWEI BSC6000 Base Station Controller
V900R008C12
BSS Routine Maintenance Guide

Issue
03
Date
2009-07-20
HUAWEI TECHNOLOGIES CO., LTD.
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 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 the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 03 (2009-07-20)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

About This Document
About This Document
Purpose
Routine maintenance is conducted at the network management center to ensure the performance
of the BTS and the BSC. This document gives an overview of the BSS routine maintenance. It
consists of daily maintenance, weekly maintenance, and monthly maintenance.
Product Version
The following table lists the product versions related to this document.
Product Name
Product Model
Product Version
BSC
BSC6000
V900R008C12
BTS
BTS3012
V300R008
BTS3012AE
V300R008
BTS3006C
V300R008
BTS3002E
V300R005
DBS3036
V300R008
BTS3036
V300R008
BTS3036A
V300R008
DBS3900 GSM
V300R008
BTS3900 GSM
V300R008
BTS3900A GSM
V300R008
BTS3900B GSM
V300R008
BTS3900E GSM
V300R008
M2000
V200R006
M2000
Intended Audience
This document is intended for:
Issue 03 (2009-07-20)

iii

About This Document

l
Shift operators
System engineers
Organization
1 Changes in BSS Routine Maintenance Guide
This provides the changes of the BSS Routine Maintenance Guide.
2 Introduction to BSS Routine Maintenance
This introduces BSS routine maintenance. Routine maintenance is an active maintenance mode.
It refers to the maintenance performed periodically when equipment is in normal state. Routine
maintenance is performed daily, weekly, and monthly.
3 BSS Daily Maintenance Guide
This describes daily maintenance tasks and procedures.
4 BSS Weekly Maintenance Guide
This describes weekly maintenance tasks and procedures.
5 BSS Monthly Maintenance Guide
This describes monthly maintenance tasks and procedures.
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.
iv

Issue 03 (2009-07-20)

About This Document
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.
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.
Convention
Description
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.
Convention
Description
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.
Issue 03 (2009-07-20)


About This Document
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.
vi
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.

Issue 03 (2009-07-20)

Contents
Contents
About This Document...................................................................................................................iii
1 Changes in BSS Routine Maintenance Guide......................................................................1-1
2 Introduction to BSS Routine Maintenance...........................................................................2-1
2.1 Scope of BSS Routine Maintenance...............................................................................................................2-2
2.2 BSS Routine Maintenance Tools....................................................................................................................2-2
2.3 Items and Intervals of BSS Routine Maintenance..........................................................................................2-2
3 BSS Daily Maintenance Guide................................................................................................3-1

3.1 Monitoring BSS Alarms (M2000)...................................................................................................................3-3
3.1.1 Monitoring BSS Current Fault Alarms (M2000)...................................................................................3-3
3.1.2 Monitoring BSS Current Event Alarms (M2000)..................................................................................3-4
3.1.3 Collecting BSS Alarms in Real Time (M2000).....................................................................................3-4
3.2 Querying and Saving BSS Performance Measurement Results (M2000).......................................................3-5
3.2.1 Querying the Measurement Results of BSS Key Performance Indicators (M2000)..............................3-6
3.2.2 Saving the Measurement Results of BSS Key Performance Indicators (M2000)................................3-10
3.3 Querying and Saving BSS Operation Logs (M2000)....................................................................................3-11
3.4 Querying BSC Operation Logs (BSC LMT).................................................................................................3-12
3.5 Checking the Automatic Backup Function of the NE (M2000)....................................................................3-13
3.6 Checking Cell Status and Cell Resources.....................................................................................................3-13
3.6.1 Checking Cell Status............................................................................................................................3-14
3.6.2 Checking Cell Resources.....................................................................................................................3-14
3.7 Checking A Interface Status (TDM).............................................................................................................3-15
3.8 Checking A Interface Status (IP)..................................................................................................................3-16
3.9 Checking Ater Interface Status.....................................................................................................................3-16
3.10 Checking Abis Interface Status (TDM)......................................................................................................3-17
3.11 Checking Abis Interface Status (HDLC)....................................................................................................3-17
3.12 Checking Abis Interface Status (IP)............................................................................................................3-18
3.13 Checking Pb Interface Status......................................................................................................................3-18
3.14 Checking Gb Interface Status (FR).............................................................................................................3-19
3.15 Checking Gb Interface Status (IP)..............................................................................................................3-19
3.16 Querying the Operating Status of the BTS (BSC LMT).............................................................................3-20
3.17 Querying the Operating Status of the External PCU (PCU Maintenance Terminal)..................................3-23
3.17.1 Querying the PCIC Status on the Pb Interface (PCU Command Terminal)......................................3-24
Issue 03 (2009-07-20)

vii
Contents

3.17.2 Querying the GPRS Status of Cells (PCU Command Terminal).......................................................3-26
4 BSS Weekly Maintenance Guide............................................................................................4-1

4.1 Checking the Operating Status of the GBAM.................................................................................................4-3
4.1.1 Backing Up the Server Files to the LMT PC.........................................................................................4-3
4.1.2 Checking the Hard Disk Partitioning.....................................................................................................4-6
4.1.3 Checking the Memory............................................................................................................................4-6
4.1.4 Checking the Communication Status of the GBAM..............................................................................4-7
4.2 Checking the Operating Status of the GOMU................................................................................................4-7
4.2.1 Checking and Cleaning Up the Server Hard Disk Space Regularly......................................................4-8
4.2.2 Backing Up the Server Files to the LMT PC.........................................................................................4-8
4.2.3 Checking the Hard Disk Partitioning of the GOMU Board.................................................................4-11
4.2.4 Checking the Memory Capacity of the GOMU Board........................................................................4-11
4.3 Checking the Status of the BSC Boards (BSC LMT)...................................................................................4-12
4.3.1 Querying the CPU/DSP Status.............................................................................................................4-12
4.3.2 Querying the Clock Status of a Board..................................................................................................4-14
4.4 Checking the BSC Clock (BSC LMT)..........................................................................................................4-16
4.4.1 Querying the Clock Status of a Board..................................................................................................4-17
4.4.2 Maintaining the BSC Clock Reference Status.....................................................................................4-18
4.5 Analyzing Performance Measurement Results (M2000)..............................................................................4-20
4.6 Collecting History Alarm Statistics (M2000)...............................................................................................4-24
4.7 Checking the Communication Between NEs and the M2000 (M2000)........................................................4-26
4.8 Monitoring the BTS Software Version (BSC LMT).....................................................................................4-27
4.9 Backing Up the BSS Configuration Data......................................................................................................4-29
4.9.1 Basic Knowledge of BSS Data Backup...............................................................................................4-30
4.9.2 Automatically Backing Up the BSC Configuration Data (M2000).....................................................4-31
4.9.3 Manually Backing Up the BSC Configuration Data (M2000).............................................................4-31
4.9.4 Manually Backing Up the PCU System Data (M2000).......................................................................4-32
5 BSS Monthly Maintenance Guide..........................................................................................5-1

5.1 Analyzing Customer Complaints....................................................................................................................5-2
5.2 Making the Network Performance Report......................................................................................................5-3
5.3 Checking the Disk Space of the BSS Maintenance Terminal.........................................................................5-4
5.4 Checking the BSS Maintenance Terminal for Viruses...................................................................................5-4
5.5 Backing Up the BSC/BTS Program Files.......................................................................................................5-5
5.5.1 Backing Up the BSC/BTS Program Files (Samba)................................................................................5-5
5.5.2 Backing Up the BSC/BTS Program Files (M2000)...............................................................................5-6
viii

Issue 03 (2009-07-20)

Figures
Figures
Figure 3-1 Querying KPI measurement per cell.................................................................................................3-15
Figure 3-2 Query BTS Running Status dialog box............................................................................................3-21
Figure 3-3 Querying BTS operating status.........................................................................................................3-22
Figure 3-4 Maintain Pb Interface Circuit dialog box.........................................................................................3-25
Figure 4-1 Querying samba status........................................................................................................................4-5
Figure 4-2 Checking the hard disk partitioning....................................................................................................4-6
Figure 4-3 Checking the memory.........................................................................................................................4-6
Figure 4-4 Querying samba status......................................................................................................................4-10
Figure 4-5 Checking the hard disk partitioning..................................................................................................4-11
Figure 4-6 Checking the memory.......................................................................................................................4-12
Figure 4-7 Querying the CPU state....................................................................................................................4-14
Figure 4-8 Query result of the board clock status..............................................................................................4-16
Figure 4-9 Query result of the board clock status..............................................................................................4-18
Figure 4-10 Querying the clock reference status................................................................................................4-19
Figure 4-11 Collecting the statistics of fault alarms...........................................................................................4-25
Figure 4-12 M2000 network topology...............................................................................................................4-27
Figure 4-13 Query Board Running Software Version window (1)....................................................................4-28
Figure 4-14 Query Board Running Software Version window (2)....................................................................4-29
Figure 5-1 Select General Parameters dialog box (from NE to NM)...................................................................5-7
Figure 5-2 Select General Parameters dialog box (from NM to Client).............................................................. 5-8
Issue 03 (2009-07-20)

ix

Tables
Tables
Table 2-1 BSS routine maintenance tools............................................................................................................ 2-2
Table 2-2 Items and reference standards of daily maintenance............................................................................2-2
Table 2-3 Items and reference standards of weekly maintenance........................................................................2-3
Table 2-4 Items and reference standards of monthly maintenance...................................................................... 2-4
Table 3-1 Recommended standards for BSS performance indicators..................................................................3-6
Table 3-2 Reference standards for GPRS performance indicators.......................................................................3-7
Table 3-3 Solutions to some abnormal indicators................................................................................................3-8
Table 3-4 Site status information........................................................................................................................3-22
Table 3-5 Checking the availability status of cells.............................................................................................3-27
Table 4-1 Board status........................................................................................................................................4-13
Table 4-2 Boards and their corresponding clocks..............................................................................................4-15
Table 4-3 Boards and their corresponding clocks..............................................................................................4-17
Table 4-4 Key BSS performance counters in weekly maintenance...................................................................4-20
Table 4-5 Key GPRS performance counters in weekly maintenance.................................................................4-21
Table 4-6 Solutions to some abnormal counters................................................................................................4-22
Table 5-1 Analysis of customer complaints.........................................................................................................5-2
Issue 03 (2009-07-20)

xi

Changes in BSS Routine Maintenance Guide

This provides the changes of the BSS Routine Maintenance Guide.
03(2009-07-20) of V900R008C12
This is the third commercial release.
Compared with issue 02(2009-05-30) of V900R008C12, no information is added, modified, or
removed in this document.
02(2009-05-30) of V900R008C12
This is the second commercial release.
Compared with issue 01(2009-02-16) of V900R008C12, no information is added, modified, or
removed in this document.
01(2009-02-16) of V900R008C12
This is the initial commercial release.
Compared with issue 02(2008-06-30) of V900R008C01, no information is added.
Compared with issue 02(2008-06-30) of V900R008C01, the following information is modified:
Issue 03 (2009-07-20)
Item
Change Description
3.1.1 Monitoring BSS Current Fault

Alarms (M2000)
the steps of saving the fault alarms are added.
3.1.2 Monitoring BSS Current Event

Alarms (M2000)
the steps of saving the event alarms are added.
the Backing Up the BSS Data is added.
the Backing Up the BSC/BTS Program Files

are added .

1-1

Compared with issue 02(2008-06-30) of V900R008C01, no information is removed.
1-2

Issue 03 (2009-07-20)

Introduction to BSS Routine Maintenance
About This Chapter

This introduces BSS routine maintenance. Routine maintenance is an active maintenance mode.
It refers to the maintenance performed periodically when equipment is in normal state. Routine
maintenance is performed daily, weekly, and monthly.
BSS routine maintenance ensures the reliability, stability, and optimum operating status of the
BTS, BSC, and PCU. In addition, routine maintenance reduces the risk of system failure by
identifying and tackling problems in time.
The basic tasks of routine maintenance are as follows:
l
Eliminating all kinds of risks to maintain the normal running of the system
Checking the electrical performance, mechanical performance, and quality of service of

the equipment
Cooperating with other entities to ensure the quality of the entire network
Checking the operating status of new equipment and expansion equipment and ensuring
their network access quality
2.1 Scope of BSS Routine Maintenance

This describes the scope of BSS routine maintenance. BSS routine maintenance involves the
maintenance of the BSC, BTS, and external PCU.
2.2 BSS Routine Maintenance Tools
This describes the BSS routine maintenance tools. These tools are the M2000 client, BSC LMT,
PCU OMC Shell, and BTS local maintenance tool. These four complementary entities work
together to perform the routine maintenance of the BSS.
2.3 Items and Intervals of BSS Routine Maintenance
This describes the items and intervals of BSS routine maintenance. BSS routine maintenance
can be performed daily, weekly, and monthly. Based on the maintenance frequency, routine
maintenance can be categorized into the following types: daily maintenance, weekly
maintenance, and monthly maintenance.
Issue 03 (2009-07-20)

2-1

2.1 Scope of BSS Routine Maintenance

This describes the scope of BSS routine maintenance. BSS routine maintenance involves the
maintenance of the BSC, BTS, and external PCU.
BSS routine maintenance refers to the monitoring and maintenance of BSS performance. Routine
maintenance is always performed on the M2000 client, BSC LMT, or PCU Command Terminal.
The BSS routine maintenance does not include the routine maintenance of the M2000 or the
maintenance performed in the equipment room.
2.2 BSS Routine Maintenance Tools

This describes the BSS routine maintenance tools. These tools are the M2000 client, BSC LMT,
PCU OMC Shell, and BTS local maintenance tool. These four complementary entities work
together to perform the routine maintenance of the BSS.
Table 2-1 lists the tools used in BSS routine maintenance.
Table 2-1 BSS routine maintenance tools
Tool
Function
M2000 client
Monitoring multiple network elements simultaneously.
BSC LMT
Maintaining and troubleshooting the BSC and BTS
PCU Command Terminal
Maintaining and troubleshooting the external PCU
BTS local maintenance

tool
Maintaining and troubleshooting the BTS
2.3 Items and Intervals of BSS Routine Maintenance

This describes the items and intervals of BSS routine maintenance. BSS routine maintenance
can be performed daily, weekly, and monthly. Based on the maintenance frequency, routine
maintenance can be categorized into the following types: daily maintenance, weekly
maintenance, and monthly maintenance.
Daily Maintenance
Table 2-2 lists the items of BSS daily maintenance.
Table 2-2 Items and reference standards of daily maintenance
2-2
SN
Item
Reference Standard
Monitoring BSS alarms on the M2000
All the fault alarms are cleared.

Issue 03 (2009-07-20)

SN
Item
Reference Standard
Querying and Saving BSS Performance

Measurement Results (M2000)
The measurement results meet the

requirements.
Querying and Saving BSS Operation Logs

(M2000)
None.
Querying BSC Operation Logs (BSC

LMT)
The operation logs do not contain the

information about unknown data
configuration operations or reset
operations.
Checking the Automatic Backup Function

of the NE (M2000)
The automatic backup function of

the NE is normal.
Checking Cell Status and Cell Resources
None.
Checking A Interface Status (None-IP)
The A interface is normal.
Checking A Interface Status (IP)
The A interface is normal.
Checking Ater Interface Status
The Ater interface is normal.
10
Checking Abis Interface Status (TDM)
The Abis interface is normal.
11
Checking Abis Interface Status (HDLC)
The Abis interface is normal.
12
Checking Pb Interface Status
The Pb interface is normal.
13
Checking Gb Interface Status (FR)
The Gb interface is normal.
14
Checking Gb Interface Status (IP)
The Gb interface is normal.
15
Querying the Operating Status of the BTS

(BSC LMT)
All the BTSs are functional. The

BTSs do not incur unexpected faults.
16
Querying the Operating Status of the

External PCU (PCU Maintenance
Terminal)
The external PCU is functional.
Weekly Maintenance
Table 2-3 lists the items of BSS weekly maintenance.
Table 2-3 Items and reference standards of weekly maintenance
Issue 03 (2009-07-20)
SN
Item
Reference Standard
Checking the Operating Status of the GBAM
The GBAM is running

normally.
Checking the Operating Status of the GOMU
The GOMU board is running

normally.

2-3

SN
Item
Reference Standard
Checking the Status of the BSC Boards (BSC

LMT)
The BSC boards are

functional.
Checking the BSC Clock (BSC LMT)
The clock is normal.
Analyzing Performance Measurement Results

(M2000)
The measurement results

meet the requirements.
Collecting History Alarm Statistics (M2000)
None.
Checking the Communication Between NEs and

the M2000 (M2000)
The communication is
normal.
Monitoring the BTS Software Version (BSC

LMT)
All the software versions are

correct.
Backing Up BSS System Data
None.
Monthly Maintenance
Table 2-4 lists the items of BSS monthly maintenance.
Table 2-4 Items and reference standards of monthly maintenance
2-4
SN
Item
Reference Standard
Analyzing Customer Complaints
None.
Making the Network Performance Report
None.
Checking the Disk Space of the BSS

Maintenance Terminal
The remaining disk space is

sufficient for system running.
Checking the BSS Maintenance Terminal

for Viruses
No viruses are detected.

Issue 03 (2009-07-20)

BSS Daily Maintenance Guide
About This Chapter

This describes daily maintenance tasks and procedures.
3.1 Monitoring BSS Alarms (M2000)
This describes how to monitor BSS alarms on the M2000 client. The BSS alarms are fault alarms
and event alarms.
3.2 Querying and Saving BSS Performance Measurement Results (M2000)
This describes how to query and save BSS performance measurement results on the M2000
client.
3.3 Querying and Saving BSS Operation Logs (M2000)
This describes how to query and save BSS operation logs on the M2000. The operation logs
contain the information about the operations performed by maintenance personnel on the
equipment. The operation logs are used to locate faults. By querying and saving the operation
logs every day, you can review all the operations performed on the equipment on that day and
check whether there are maloperations.
3.4 Querying BSC Operation Logs (BSC LMT)
This describes how to query BSC operation logs on the LMT. The BSC operation logs contain
the information about the operations performed by maintenance personnel on the equipment.
The BSC operation logs are used to locate faults. By querying and saving the operation logs
every day, you can review all the operations performed on the equipment on that day and check
whether there are maloperations.
3.5 Checking the Automatic Backup Function of the NE (M2000)
This describes how to check the automatic backup function of the NE on the M2000 client.
3.6 Checking Cell Status and Cell Resources
This describes how to check cell status and cell resources to monitor cells so that faults can be
rectified in time.
3.7 Checking A Interface Status (TDM)
This describes how to check the A interface status in TDM transmission mode.
3.8 Checking A Interface Status (IP)
This describes how to check the A interface status in IP transmission mode.
Issue 03 (2009-07-20)

3-1

3.9 Checking Ater Interface Status

This describes how to check the status of the Ater interface.
3.10 Checking Abis Interface Status (TDM)
This describes how to check the Abis interface status in TDM transmission mode.
3.11 Checking Abis Interface Status (HDLC)
This describes how to check the Abis interface status in HDLC transmission mode.
3.12 Checking Abis Interface Status (IP)
This describes how to check the Abis interface status in IP transmission mode.
3.13 Checking Pb Interface Status
This describes how to check the status of the Pb interface.
3.14 Checking Gb Interface Status (FR)
This describes how to check the Gb interface status in FR transmission mode.
3.15 Checking Gb Interface Status (IP)
This describes how to check the Gb interface status in IP transmission mode.
3.16 Querying the Operating Status of the BTS (BSC LMT)
This describes how to query the operating status of all the BTSs controlled by a BSC on the
LMT.
3.17 Querying the Operating Status of the External PCU (PCU Maintenance Terminal)
This task describes how to query the LAPD and PCIC status on the Pb interface, and the FR,
NS, and BSSGP status on the Gb interface. The task also describes how to monitor the GPRS
cell status and cell channel status in the PCU.
3-2

Issue 03 (2009-07-20)

3.1 Monitoring BSS Alarms (M2000)

This describes how to monitor BSS alarms on the M2000 client. The BSS alarms are fault alarms
and event alarms.
3.1.1 Monitoring BSS Current Fault Alarms (M2000)
This describes how to monitor the current fault alarms, such as BSC alarms, BTS alarms, and
PCU alarms of the BSS system.
3.1.2 Monitoring BSS Current Event Alarms (M2000)
This describes how to monitor the event alarms, such as BSC alarms, BTS alarms, and PCU
alarms of the BSS system.
3.1.3 Collecting BSS Alarms in Real Time (M2000)
This describes how to collect BSS fault alarms and BSS event alarms in real time. The NEs
involved in this operation are the BSC, BTS, and external PCU. BSS alarms are collected for
future query.
3.1.1 Monitoring BSS Current Fault Alarms (M2000)

This describes how to monitor the current fault alarms, such as BSC alarms, BTS alarms, and
PCU alarms of the BSS system.
Prerequisite
l
You have logged in to the M2000 client.
The communication between the M2000 client and the server is normal.
You have the right to query alarms.
Procedure
Step 1 On the M2000 client, choose Monitor > Current Fault Alarms.
Step 2 In the displayed Filter dialog box, set Base Setting and Alarm Source.
NOTE
Click Advanced to set Maintenance Region, Browse Setting, and Default.
Step 3 Click OK. The query result is displayed in the Current Fault Alarms window.
Step 4 Click Save As to save the query result.
NOTE
Optionally, select an alarm, right-click it, and then choose Save Selected Records from the shortcut menu
to save the alarm.
The query result can be saved as a .txt, .html, or .csv file. By default, the query result is saved as a .csv file.
Step 5 Optional: Right-click the alarm to be monitored, and then choose Detail Information from the
shortcut menu. Optionally, double-click the alarm. The Detail Information dialog box is
displayed.
View the alarm name, alarm location information, and alarm severity in the displayed dialog
box.
----End
Issue 03 (2009-07-20)

3-3

3.1.2 Monitoring BSS Current Event Alarms (M2000)

This describes how to monitor the event alarms, such as BSC alarms, BTS alarms, and PCU
alarms of the BSS system.
Prerequisite
l
You have the authority to query alarms.
Procedure
Step 1 On the M2000 client, choose Monitor > Event Alarms.
Step 2 In the Filter dialog box, set the conditions for querying the alarms.
Step 3 Click OK. The query result is displayed in the Event Alarms window.
Step 4 Optional: Click Save As to save the query result.
NOTE
The query result can be saved as a .txt, .html, or .csv file. By default, the query result is saved as a .csv file.
Step 5 Optional: Right-click the alarm to be monitored, and then choose Detail Information from the
shortcut menu. Optionally, double-click the alarm. The Detail Information dialog box is
displayed.
View the alarm name, alarm location information, and alarm severity in the displayed dialog
box.
----End
3.1.3 Collecting BSS Alarms in Real Time (M2000)

This describes how to collect BSS fault alarms and BSS event alarms in real time. The NEs
involved in this operation are the BSC, BTS, and external PCU. BSS alarms are collected for
future query.
Prerequisite
l
You have the right to operate the related network element.
You have the right to collect alarm statistics.
Context
You can collect a maximum of 400,000 BSS alarms on the M2000. The total number of BSS
alarms is the summation the total number of statistic items. The alarms whose statistics are zero,
however, are not displayed on the M2000 client. Therefore, the total number of alarms displayed
on the M2000 client is smaller than the actual number of BSS alarms.
3-4

Issue 03 (2009-07-20)

Procedure
l
Collecting the statistics of fault alarms

1.
On the M2000 client, choose Monitor > Fault Alarm Statistics.
2.
In the Statistic Item dialog box, set the conditions for collecting fault alarms, and
then click OK. The statistics of fault alarms are displayed.
3.
On the Alarm Source tab, you can select the alarm source according to the following
categories: By Object, By Type, and By Topo.
4.
Click Save As to save the fault alarm statistics.
5.
l
If you click the Table tab, the fault alarm statistics can be saved as a .txt, .html,
or .csv file. By default, the statistics are saved as a .csv file. If there are more than
256 columns in the .csv file, you cannot open the file with Excel. You may open
it with UltraEdit or Notepad.
On the Pie tab, the statistics can be saved as a .jpg file.
Click the Table tab, and then click Print to print the statistics of fault alarms.
Collecting the statistics of event alarms

1.
On the M2000 client, choose Monitor > Event Alarm Statistics.
2.
In the Statistic Item dialog box, set the conditions for collecting event alarms, and
then click OK. The statistics of event alarms are displayed.
3.
On the Alarm Source tab, you can select the alarm source according to the following
categories: By Object, By Type, and By Topo.
4.
Click Save As to save the event alarm statistics.
5.
If you click the Table tab, the event alarm statistics can be saved as a .txt, .html,
or .csv file. By default, the statistics are saved as a .csv file. If there are more than
256 columns in the .csv file, you cannot open the file with Excel. You may open
it with UltraEdit or Notepad.
On the Pie tab, the statistics can be saved as a .jpg file.
Click the Table tab, and then click Print to print the statistics of event alarms.
----End
3.2 Querying and Saving BSS Performance Measurement

Results (M2000)
This describes how to query and save BSS performance measurement results on the M2000
client.
3.2.1 Querying the Measurement Results of BSS Key Performance Indicators (M2000)
This describes how to query the measurement results of the performance indicators that have a
granularity period of 5 minutes, 15 minutes, 30 minutes, 60 minutes, or 24 hours. The task
monitors whether the key performance data in the BSS system is normal.
3.2.2 Saving the Measurement Results of BSS Key Performance Indicators (M2000)
This describes how to save performance measurement results as a .txt, .html, .csv, or .xls file.
You can back up performance measurement results to prevent data loss.
Issue 03 (2009-07-20)

3-5

3.2.1 Querying the Measurement Results of BSS Key Performance

Indicators (M2000)
This describes how to query the measurement results of the performance indicators that have a
granularity period of 5 minutes, 15 minutes, 30 minutes, 60 minutes, or 24 hours. The task
monitors whether the key performance data in the BSS system is normal.
Prerequisite
l
The measurement objects exist.
You have the authority to query the results of BSC performance measurement.
Context
The key performance indicators in the BSS routine maintenance are the BSS performance
indicators and the GPRS performance indicators.
Table 3-1 lists the recommended standards for the BSS performance indicators. Table 3-2 lists
the recommended standards for the GPRS performance indicators.
Table 3-1 Recommended standards for BSS performance indicators
3-6
Indicator
Reference
Standard
Success rate of immediate assignment
>92%
Success rate of TCH assignment
>94%
Success Rate of Call Establishment per Cell
>92%
TCH Call Drop Rate (Including Handover)
<2%
TCH Call Drop Rate (Excluding Handover)
<2%
Call drop rate on SDCCH
<2%
Congestion Rate on TCH (All Channels Busy)
<5%
Congestion Rate on SDCCH (All Channels Busy)
<5%
Intra-BSC Handover Success Rate
>92%
Success Rate of Incoming External Inter-Cell Handover
>86%
Inter-BSC Outgoing Cell Handover Success Rate
>86%
Traffic volume on TCH per Cell
Subject to network
conditions
Traffic call drop rate
Subject to network
conditions

Issue 03 (2009-07-20)

Indicator
Reference
Standard
SDCCH availability
>98%
TCH availability
>98%
Table 3-2 Reference standards for GPRS performance indicators

Indicator
Reference Standard
Uplink Assignment Success Ratio
>90%
Downlink Assignment Success Ratio
>80%
Uplink TBF congestion rate (%)
<5%
Downlink TBF congestion rate (%)
<5%
PDCH usage
Subject to network conditions
Uplink GPRS TBF Call Drop Rate
<3%
Downlink GPRS TBF Call Drop Rate
<5%
NOTE
The indicator values provided in Table 3-1 and Table 3-2 are for reference only. You can set your own
standards for routine maintenance based on your network conditions and assessment standards.
Procedure
Step 1 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 operations:
1.
Select the target NE in the navigation tree on the left.
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 in any of the following formats: table, line chart, and bar chart. You can specify
the format in the View Type area.
Step 4 Compare the values of these indicators with those required by the office. If you find any
inconsistency, report it to the engineers concerned with troubleshooting.
----End
Issue 03 (2009-07-20)

3-7

Postrequisite
Table 3-3 lists the solutions to some abnormal indicators.
Table 3-3 Solutions to some abnormal indicators
Fault
Description
Possible Cause
Solution
High CPU
usage
Subject to actual
conditions
Contact Huawei Technical Support.
Low success
rate of
handovers
The handover
threshold is too low.
The neighboring cells

are congested. There
are no idle channels.
Some neighboring
cells are missing.
The settings of
handover hysteresis
and handover priority
are improper.
The settings of best

cell measurement
time N and P are
improper.
High call
drop rate on
TCHs and
SDCCHs
High TCH
congestion
rate
3-8
Rectify the faults based on the causes.
T3103 timeout
The timing length of T3103 is too short. Set the

timing length to a proper value.
Radio link failure due to

interference, coverage,
parameter, or equipment
problems
Interference: Perform drive tests to check

equipment. Check the area where interference
occurs and find the interference frequencies.
Use a spectrum analyzer to further locate the
interference source. If functions such as
frequency hopping, DTX, and power control
are enabled, the internal interference will be
greatly reduced.
Coverage: Regulate network parameters. Add

more BTSs.
Improper parameter settings: Regulate

parameters to proper values.
Equipment problems: Rectify equipment

problems.
The configurations of
trunk circuits on the A
interface are incorrect.
Modify data configurations.

Issue 03 (2009-07-20)

Fault
Description
High
SDCCH
congestion
rate
Issue 03 (2009-07-20)
Possible Cause
Solution
The TSC and the BCC of

a frequency hopping cell
are inconsistent.
The TCH assignment

fails because of the same
frequency and BSIC.
Board fault or unreliable

board performance
leads to a high
congestion rate.
Find the faulty board and replace it.
BTS hardware (antenna

and feeder) is
improperly installed.
This leads to unbalance
between the uplink level
and the downlink level
and TCH congestion
occurs.
Correctly install BTS hardware.
The cell is installed with

a repeater. The cell
capacity is expanded but
the repeater capacity is
not.
Expand the capacity of the repeater.
In the same cell, the

transmit power of the
TRX carrying the
BCCH is greater than
that of the TRX carrying
the TCH.
Modify antenna attributes or network parameters

to optimize the coverage of the BCCH and the
TCH.
Interference
Analyze the results of performance measurement

and eliminate interference.
TCH assignment fails

because of the isolated
site or complex terrain.
Therefore, the
congestion rate rises.
Optimize the network based on the coverage

problems.
Excessive subscribers
Expand the system capacity by adding TRXs or

by other methods.
SDCCH location
updating occurs
frequently because the
cell is on the edge of the
location area.
Modify the settings of location area selection, Cell

Reselection Hysteresis (CRH), and periodic
location updating, as well as modify the dual-band
network planning to prevent frequent handovers.

3-9

Fault
Description
Possible Cause
Solution
Frequent short messages

and weather forecasting
Configure more SDCCHs or do not send too many

short messages at a time.
Insufficient system
capacity: There are not
enough SDCCHs
configured.
Expand the capacity.
Improper settings of
system parameters
Improve the RACH access threshold to reduce

interference. Reduce the maximum number of
retransmissions and increase the Tx-integer.
SDCCH congestion due

to board (TRX) fault or
transmission fault
Rectify the fault.
Improper planning of
the location area
Replan the location area.
3.2.2 Saving the Measurement Results of BSS Key Performance

Indicators (M2000)
This describes how to save performance measurement results as a .txt, .html, .csv, or .xls file.
You can back up performance measurement results to prevent data loss.
Prerequisite
l
You have logged in to the M2000 client. The communication between the M2000 client
and the server is normal.
You have the right to save the results of BSC performance measurement.
Procedure
Step 1 Query performance measurement results by referring to 3.2.1 Querying the Measurement
Results of BSS Key Performance Indicators (M2000).
Step 2
3-10
Right-click in the Query Result window, and choose Export All from the shortcut menu.
Right-click in the Query Result window, and choose Save from the shortcut menu to save
the measurement results.

Issue 03 (2009-07-20)

NOTE
Save the measurement results of the indicators based on the network assessment. You are advised to
save these indicators as a template. The performance indicators can be automatically saved as a file.
For details, refer to the M2000 Operator Guide.
To save the table-formatted measurement results, choose Export Selected Rows or Export All from
the shortcut menu.
The table-formatted measurement results can be saved as a .xls, .csv, .html, or .txt file.
To save the line chart-formatted or bar chart-formatted measurement results, choose Save from the
shortcut menu.
The line chart-formatted or bar chart-formatted measurement results can be saved as a .jpg file.
----End
3.3 Querying and Saving BSS Operation Logs (M2000)

This describes how to query and save BSS operation logs on the M2000. The operation logs
contain the information about the operations performed by maintenance personnel on the
equipment. The operation logs are used to locate faults. By querying and saving the operation
logs every day, you can review all the operations performed on the equipment on that day and
check whether there are maloperations.
Prerequisite
l
On the M2000 Client, choose Topology > Main Topology. In the Main Topology window,
right-click the NE whose log is to be synchronized, and then choose Synchronize NE
Operation & Security Logs to synchronize the user log with the operation log.
If you do not set the querying condition, all the operation logs are queried. If the query
results need to be printed, install a printer.
If you have no authority for querying the operation logs, you can query the operation logs
of your own only.
The query results are based on the data in the database.
If there is no data in the database, no operation log is displayed.
Context
Procedure
Step 1 On the M2000 client, choose System > Log Management > Query Operation Logs.
Step 2 In the Filter Condition dialog box, set the filtering conditions, and then click OK. The query
results are displayed in the Query Operation Logs window.
NOTE
If you do not query the operation logs of all NEs, select the Operation Object in the Filter Condition
dialog box.
Step 3 You can also perform the following operations in the Query Operation Logs window:
Issue 03 (2009-07-20)

3-11


l
Right-click an operation log, and then choose Details. The Log Details dialog box is
displayed. View all the information about the operation log. You can click Previous or
Next to query the detailed information about the previous or the next operation log.
Click Save As to save the query results to the local PC.
Click Refresh to refresh the query results.
Click Print to print the query results.
----End
3.4 Querying BSC Operation Logs (BSC LMT)

This describes how to query BSC operation logs on the LMT. The BSC operation logs contain
the information about the operations performed by maintenance personnel on the equipment.
The BSC operation logs are used to locate faults. By querying and saving the operation logs
every day, you can review all the operations performed on the equipment on that day and check
whether there are maloperations.
Prerequisite
You have the authority to query the BSC operation logs.
Context
Criterion for the operation: There is no record about unknown data configuration operations or
reset operations in the operation logs.
Procedure
l
Through GUI
1.
On the BSC6000 Local Maintenance Terminal, choose BSC Maintenance >

Maintain Logs > Query Operation Logs Online.
2.
Set parameters in the Query Condition area, and then click Query. The query results
are displayed.
Through MML
1.
On the Local Maintenance Terminal, run the LST OPTLOG command to query
the BSC operation logs.
----End
Postrequisite
If you find records about data configuration operations in the operation logs, check whether the
operations are proper and who performed these operations.
If there are records about board reset, board switchover, link blocking, SS7 prohibition or
deactivation, SCCP DSP and subsystem prohibition, and port loopback, check the cause of these
operations.
3-12

Issue 03 (2009-07-20)

3.5 Checking the Automatic Backup Function of the NE

(M2000)
This describes how to check the automatic backup function of the NE on the M2000 client.
Prerequisite
Context
The NE backup task refers to saving the NE data as the backup file to the specified directory on
the server. This task is performed to prevent data loss and to restore NEs when they are faulty.
l
The NE backup task is a scheduled task.
The task can be performed periodically or only once. The units of Period can be set to days,
weeks, and months.
The M2000 supports a maximum of 50 NE backup tasks.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Click New. The New Task dialog box is displayed.
Step 3 Set the basic information of the task.
1.
Enter a name in the Task Name text box.
2.
Set Task Type to NE Backup.
3.
Set Run Type to Period.
Step 4 Click Next. Set Start Time.

Step 5 Click Next to select backup type. The following backup types are available: Backup ALL
NE, By NE Type, and By NE.
Step 6 Click Finish.
----End
3.6 Checking Cell Status and Cell Resources

This describes how to check cell status and cell resources to monitor cells so that faults can be
rectified in time.
3.6.1 Checking Cell Status
This describes how to check the service status and operating status of cells on the Local
Maintenance Terminal.
3.6.2 Checking Cell Resources
This describes how to check the traffic volume on the TCH and SDCCH of the cell on the M2000
Client to determine the performance of the cell.
Issue 03 (2009-07-20)

3-13

3.6.1 Checking Cell Status

This describes how to check the service status and operating status of cells on the Local
Maintenance Terminal.
Procedure
Step 1 Enter the DSP CELLSRVSTAT command on the Local Maintenance Terminal to query the
service status of cells.
1.
Enter the Cell Index.

NOTE
If you query the service status of all cells, you do not need to enter the Cell Index.
2.
Run the command. The Cell service state varies with the Cell Index. There are two types
of cell service states: Cell is inservice or Cell is outservice.
Step 2 Enter the DSP CELLSTAT command on the Local Maintenance Terminal to query the
operating status of cells.
1.
Specify the Index type, enter the Cell Index or Cell Name, and then specify the Cell
attribute.
NOTE
2.
If you need to query the operating status of all cells, you do not need to select the Index type.
If you query the operating status of the cell in any state, you do not need to specify the Cell
attribute.
Execute the command. The cell operating status varies with the Cell Index. There are three
types of operating states: Cell Initialized, Blocked Automatically, or Channel Fault.
----End
3.6.2 Checking Cell Resources

This describes how to check the traffic volume on the TCH and SDCCH of the cell on the M2000
Client to determine the performance of the cell.
Procedure
Step 1 Choose Performance > Query Result. The Query Result window is displayed.
Step 2 Click New Query. The Query Result dialog box is displayed.
Step 3 On the left pane of the dialog box, choose BSC6000 > Call Measurement > KPI Measurement
per Cell. Select one or more than one Available Objects and add it to the Selected Objects
area, as shown in Figure 3-1.
3-14

Issue 03 (2009-07-20)

Figure 3-1 Querying KPI measurement per cell
Step 4 Click the Counter Settings tab, select the Traffic Volume on SDCCH and Traffic Volume
on Tch from the Available Counters, and then add the two counters to the Selected
Counters.
Step 5 Click the Other Settings tab, and set the time and date for the query.
Step 6 Click Query. The traffic volumes on the TCH and SDCCH of the queried cell are displayed.
----End
3.7 Checking A Interface Status (TDM)

This describes how to check the A interface status in TDM transmission mode.
Context
To check the A interface status, you must perform the following operations:
l
Check the status of the physical layer interface
Check the status of the SS7 signaling link
Checking the status of the A interface circuit
Issue 03 (2009-07-20)

3-15

Procedure
Step 1 Check the status of the physical layer interface. For details, refer to Verifying the Physical Links
on the A Interface.
Step 2 Check the status of the SS7 signaling link. For details, refer to Verifying the Control Plane on
the A Interface.
Step 3 Check the status of the A interface circuit. For details, refer to Verifying the User Plane on the
A Interface.
----End
3.8 Checking A Interface Status (IP)

This describes how to check the A interface status in IP transmission mode.
Context
To check the A interface status, you must perform the following operations:
l
Checking the status of the A interface link
Procedure
on the A Interface (A over IP).
Step 2 Check the status of the A interface link. For details, refer to Verifying the Control Plane on the
A Interface (A over IP).
----End
3.9 Checking Ater Interface Status

This describes how to check the status of the Ater interface.
Context
To check the Ater interface status, you must perform the following operations:
l
Check the status of the operation and maintenance link
Check the status of the service channel

NOTE
Checking the status of the physical layer interface and checking the status of the service channel in the
local configuration of the Ater interface are similar to those in the remote configuration of the Ater interface.
This following takes the remote configuration as an example.
3-16

Issue 03 (2009-07-20)

Procedure
Step 1 For details on checking the status of the physical layer interface, refer to Verifying the Physical
Links on the Ater Interface (Configuration on the MSC Side).
Step 2 For details on checking the status of the operation and maintenance link, refer to Verifying the
Management Plane on the Ater Interface (Configuration on the MSC Side).
Step 3 For details on checking the status of the service channel, refer to Verifying the User Plane on
the Ater Interface (Configuration on the MSC Side).
----End
3.10 Checking Abis Interface Status (TDM)

This describes how to check the Abis interface status in TDM transmission mode.
Context
To check the Abis interface status, you must perform the following operations:
l
Check the status of the LAPD link
Check the status of the Abis interface timeslot
Procedure
on the Abis Interface.
Step 2 Check the status of the LAPD link by querying the OML status and RSL status. For how to query
the OML status, refer to Verifying the Management Plane on the Abis Interface; for how to
query the RSL status, refer to Verifying the Control Plane on the Abis Interface.
Step 3 Checking the status of the Abis interface timeslot. For details, refer to Verifying the User Plane
on the Abis Interface.
----End
3.11 Checking Abis Interface Status (HDLC)

This describes how to check the Abis interface status in HDLC transmission mode.
Context
l
Issue 03 (2009-07-20)

3-17

Procedure
on the Abis Interface (Abis over HDLC).
Step 2 Check the status of the LAPD link. For details, refer to Verifying the Control Plane on the Abis
Interface (Abis over HDLC).
----End
3.12 Checking Abis Interface Status (IP)

This describes how to check the Abis interface status in IP transmission mode.
Context
l
Procedure
on the Abis Interface (Abis over IP).
Step 2 Check the status of the LAPD link. For details, refer to Verifying the Control Plane on the Abis
Interface (Abis over IP).
----End
3.13 Checking Pb Interface Status

This describes how to check the status of the Pb interface.
Context
To check the Pb interface status, you must perform the following operations:
l
Check the status of the PBSL
Check the status of the Pb interface circuit
Procedure
on the Pb Interface.
Step 2 Check the status of the PBSL. For details, refer to Verifying the Control Plane on the Pb Interface.
Step 3 Check the status of the Pb interface circuit. For details, refer to Verifying the User Plane on the
Pb Interface.
----End
3-18

Issue 03 (2009-07-20)

3.14 Checking Gb Interface Status (FR)

This describes how to check the Gb interface status in FR transmission mode.
Context
To check the Gb interface status, you must perform the following operations:
l
Verify the BC status
Verify the NSVC status
Verify the SIGBVC status
Verify the PTPBVC status
Procedure
on the Gb interface.
Step 2 Verify the BC status. For details, refer to Verifying the BC.
Step 3 Verify the NSVC status. For details, refer to Verifying the NSVC.
Step 4 Verify the SIGBVC status. For details, refer to Verifying the SIGBVC.
Step 5 Verify the PTPBVC status. For details, refer to Verifying the PTPBVC.
----End
3.15 Checking Gb Interface Status (IP)

This describes how to check the Gb interface status in IP transmission mode.
Context
To check the Gb interface status, you must perform the following operations:
l
Verify the BC status
Verify the IP route on the Gb interface
Verify the SIGBVC status
Verify the PTPBVC status
Procedure
on the Gb interface.
Step 2 Verify the BC status. For details, refer to Verifying the NSVL.
Issue 03 (2009-07-20)

3-19

Step 3 Verify the IP route on the Gb interface. For details, refer to Verifying the IP Routes on the Gb
Interface.
Step 4 Verify the SIGBVC status. For details, refer to Verifying the SIGBVC.
Step 5 Verify the PTPBVC status. For details, refer to Verifying the PTPBVC.
----End
3.16 Querying the Operating Status of the BTS (BSC LMT)

This describes how to query the operating status of all the BTSs controlled by a BSC on the
LMT.
Prerequisite
l
The LMT is running normally.
The communication between the BTS and the BSC is normal.
Context
Criterion for the operation: All the BTSs are normal.
You can query the operating status of multiple BTSs. Through this operation, the LMT displays
all the faulty BTSs or BTS boards, which makes the maintenance easy and effective. It helps to
obtain the operating status of BTSs and replace the faulty board in time.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, choose BTS Maintenance > Query BTS
Running Status.
The Query BTS Running Status dialog box is displayed, as shown in Figure 3-2.
3-20

Issue 03 (2009-07-20)

Figure 3-2 Query BTS Running Status dialog box
Step 2 Set Object Type and Site Type. The sites to be queried are displayed in the Candidate sites
list box.
Step 3 Select the sites to be queried and move them from Candidate sites to Selected sites, select
parameters in the Query Status list box, and click OK.
The operating status of the selected sites is displayed, as shown in Figure 3-3.
Issue 03 (2009-07-20)

3-21

Figure 3-3 Querying BTS operating status
Step 4 Click Save to save the query result or click Query to query other sites.
----End
Postrequisite
Table 3-4 lists the query results and handling suggestions.
Table 3-4 Site status information
3-22
Status
Parameter
Normal
Value
Description
Site Name
None
None
Normal OML
Link
Yes
Yes indicates that the OML is normal. No indicates that the

OML is broken.
BTS Initialized
Yes
Yes indicates that the site is initialized normally. No indicates

that the site is not normally initialized. You need other
information to determine the fault.
Cell Initialized
Yes
Yes indicates that the cell is initialized normally. No

indicates that the cell is not normally initialized. You need
other information to determine the fault.
Block
Automatically
NO
If a BTS is blocked automatically, you can infer that the BTS

incurs a fault. If the value is Yes, check whether the BTS
reports alarms and whether all the services are normal.

Issue 03 (2009-07-20)

Status
Parameter
Normal
Value
Channel Fault
NO
Yes indicates a channel is faulty. Check which channel incurs

a fault and rectify the fault. No indicates that no channel is
faulty.
NO
Yes indicates that the TRX carrying the main BCCH incurs
a fault. You need to identify the fault and replace a board if
necessary. No indicates that the TRX carrying the main
BCCH is functional.
BT Hop Mutual
Aid
NO
Yes indicates that the TRXs participating in baseband

frequency hopping are faulty. The baseband frequency
hopping function of the related cell is disabled automatically.
Huawei recommends that you check the board status and
rectify the fault.
Channel Type
Dynamically
Changed
Yes
Management
Authority in the
Near End
NO
Board Fault
NO
Yes indicates that the faulty board needs to be replaced.
Board not
Configured
NO
Yes indicates that the board is not configured. Check whether

a board is installed in the slot. Modify the data configuration
or insert the board according to actual conditions. No
indicates that the board is configured normally.
Alarm
NO
If the value is Yes, handle the alarm.
Block Manually
NO
If the value is Yes, find the reason why the site is blocked
manually. If the reason is maloperation, unblock the site.
Alarm Shielded
NO
If the value is Yes, some alarms are shielded. Check whether

the shielded alarms are caused by the operation recorded.
Frequency
Scanning
NO
BCCH Mutual
Aid
Description
Ignore it.
Ignore it.
Ignore it.
3.17 Querying the Operating Status of the External PCU

(PCU Maintenance Terminal)
This task describes how to query the LAPD and PCIC status on the Pb interface, and the FR,
NS, and BSSGP status on the Gb interface. The task also describes how to monitor the GPRS
cell status and cell channel status in the PCU.
3.17.1 Querying the PCIC Status on the Pb Interface (PCU Command Terminal)
Issue 03 (2009-07-20)

3-23

This describes how to query the status of the Pb interface circuits on the PCU Command
Terminal. The Pb interface circuits carry the GPRS services. If a Pb interface circuit is faulty,
it cannot carry services.
3.17.2 Querying the GPRS Status of Cells (PCU Command Terminal)
This describes how to check the GPRS status of cells on the PCU Command Terminal.
3.17.1 Querying the PCIC Status on the Pb Interface (PCU

Command Terminal)
This describes how to query the status of the Pb interface circuits on the PCU Command
Terminal. The Pb interface circuits carry the GPRS services. If a Pb interface circuit is faulty,
it cannot carry services.
Prerequisite
l
The LMT is started in online mode.
You have the authority to log in to the PCU through Telnet.
Context
Criterion for the operation: The BSC and the PCU do not return any unavailable Pb interface
circuits, that is, the returned result is null.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, choose BSC Maintenance > Maintain User
Resource > Maintain Pb Interface Circuit.
The Maintain Pb Interface Circuit dialog box is displayed, as shown in Figure 3-4.
3-24

Issue 03 (2009-07-20)

Figure 3-4 Maintain Pb Interface Circuit dialog box
Step 2 In the Maintain Pb Interface Circuit dialog box, select a Subrack No. and a PCU No., and
then set the state to Failure or Blocked to query the circuits.
Step 3 Log in to the PCU through Telnet.
Step 4 Run the command mt pcic show unavailable all to query all the unavailable Pb interface circuits
under the BSC.
Step 5 Collect statistics on the unavailable Pb interface circuits under the BSC and under the PCU.
----End
Postrequisite
The maintenance of Pb interface circuits is similar to that of circuits. If a Pb interface circuit
incurs a fault or is blocked, you can reset or unblock it.
l
Issue 03 (2009-07-20)
Failure: The Pb interface circuit is faulty. You can reset the circuit by selecting it and
clicking Reset on the LMT.
3-25


l
Blocked: Check whether the Pb interface circuit is blocked manually. Unblock or reset the
circuit by selecting it and clicking Unblock or Reset on the LMT.
If the fault persists, contact Huawei for technical support.
3.17.2 Querying the GPRS Status of Cells (PCU Command

Terminal)
This describes how to check the GPRS status of cells on the PCU Command Terminal.
Prerequisite
l
You have the authority to log in to the PCU through Telnet.
You have the proper operation authority.
Context
Criterion for the operation: No unavailable cell is found after the operation, that is, the returned
result is null.
NOTE
For parameter settings of the corresponding PCU commands, see List of PCU Commands and Parameters.
Procedure
Step 1 Log in to the PCU through Telnet.
Step 2 Run the command mt gcell show unavailable to query all the unavailable cells under the BSC.
Step 3 The statistics of the unavailable cells is displayed.
----End
Postrequisite
If the returned result shows that there are unavailable cells, troubleshoot and rectify the faults.
To rectify the faults, you have to check the availability of cells, the BSC management status of
cells, the Gb interface management status of cells, and the data configuration of cells under the
PCU.
Checking the Availability Status of Cells
To offer GPRS services, a cell must be normal. You can run the command mt gcell show
state to check the status of a cell on the PCU Command Terminal. Table 3-5 lists various
availability status, causes of faults, and troubleshooting methods.
3-26

Issue 03 (2009-07-20)

Table 3-5 Checking the availability status of cells

Cell
Availability
Cause
Troubleshooting
Internal fault
The data of the cell is

configured on the PCU, but
it is not configured on the
BSC. The BSC sends the
cell blocked message to the
PCU. The cause value is
that the cell does not exist.
The PCU sets the status to
the internal fault. After the
cell is initialized, the BSC
performs dynamic data
configuration. This fault
occurs when the cell is
deleted.
Check the BSC data configurations (BSC

Cell Table), including the data
configurations on the BSC OMC and on the
host. Check whether the corresponding cell
exists. If no corresponding cell exists, add a
cell.
Dependency
All the LAPDs connected to

the BSC where the faulty
cell is located are
unavailable. When the cell
has no available PBCCHs,
the cell is in the dependency
state.
Troubleshooting LAPD Link Faults

(External PCU).
Device has not

been initialized
The initialization of the cell

is not performed or
completed. When the PCU
cannot obtain the cell
configuration from the
BSC, the PCU repeatedly
performs initialization of
the cell.
Check the status of the BSC and the BTS. If

they are faulty, initialize cells. Check
whether the line connection on the Pb
interface is correct, whether the BSC data
and the PCU data are correct, and whether
the PCICs are sufficient.
The cell does

not support
GPRS.
The cell is not configured

with the GPRS function.
Check the data configurations (BSC Cell

Table) of the BSC. Set the cell to support
GPRS.
The cell does not exist in the

BSC configuration data.
Compare the data configurations in the

ATTR table of the PCU and in the cell table
of the BSC. Check whether the CGIs of the
cell are consistent. If they are inconsistent,
modify the CGI.
The cell does

not exist.
Issue 03 (2009-07-20)

3-27

Cell
Availability
Cause
Troubleshooting
(1) On the PCU Command Terminal, run the
command pcu check cellconfig to check the
data configurations of the PCU. Modify the
data configurations according to the error
indications.
Cell database
configuration
error
The data configuration of

cells in the PCU is
incomplete.
(2) Check the configuration data (Cell

Channel Description Table) of the BSC.
Check whether the corresponding cells are
configured with the PBCCH but the PCU
license does not permit this function.
Purchase the license permitting the PBCCH
function from Huawei or delete the PBCCH
configuration from the BSC according to
your requirement.
(3) Check whether the cell is configured with
the PDCH in the BSC data configuration. If
no PDCH is configured, configure it.
(4) Check whether the cell is configured with
multiple PBCCHs in the BSC data
configuration. If you have purchased the
corresponding license, you can configure the
PBCCHs. Each cell can be configured with
only one PBCCH. Delete the redundant
PBCCHs.
Cell is deactive
The cell does not exist in the

BSC configuration data.
Compare the configuration data in the ATTR

table of the PCU with that in the cell table of
the BSC. Check whether the cell is activated.
Checking the BSC Management Status of Cells

If the BSC management status is Blocked, the cells under the BSC are faulty. You have to handle
them.
1.
On the LMT, check the status of BTSs and cells and ensure that all the cells are normal. If
some cells are faulty, contact Huawei for technical support.
2.
Unblock cells on the LMT.
3.
On the PCU Command Terminal (or LMT), open the PB interface information trace
window and trace the Pb interface information of the faulty cell. On the PCU command
terminal, run the command mt gcell reset to reset the cell. Save the interface information
and contact Huawei for technical support.
Checking the Gb Interface Management Status of Cells

If the Gb interface management status of cells is Blocked, do as follows:
1.
3-28
Run the command mt fr bc show statinfo. If the bc state is Q933 invalid, run the command
mt nsvc show state. If the NS-VC state is Dead-blocked, you can infer that the FR data
on the PCU is inconsistent with that on the SGSN or the physical line between the PCU
Issue 03 (2009-07-20)

and the SGSN is abnormal. You have to confirm that the FR data on the PCU and that on
the SGSN are correct and consistent. Then configure a test BC in DCE mode on an idle
port on the PCU and use an E1 to connect the service port and the test port to perform the
loopback test. If a fault occurs, contact maintenance engineers to handle it.
2.
Run the command mt fr bc show statinfo. If the FR BC state is normal, run the command
mt nsvc show state. If the NS-VC state is Alive-blocked, you can infer that the NSVC is
blocked manually on the PCU or on the SGSN. You have to unblock the NSVC.
3.
Run the command mt nsvc show state. If the NS-VC state is normal, run the command
mt bvc signal show state. If the SIG BVC state is abnormal, you can infer that the NSE
data on the PCU is inconsistent with that on the SGSN. You have to modify the NSE data
on the PCU or on the SGSN to ensure that they are consistent. Then run the command mt
bvc signal reset on the PCU command terminal to reset the NSE.
4.
Run the command mt bvc signal show state, if the SIG BVC state is normal, run the
command mt bvc ptp show state. If the PTP BVC state is BLOCKED, you can infer that
the PTP BVC data on the PCU is inconsistent with that on the SGSN. You have to modify
the PTP BVC data on the PCU or on the SGSN to ensure that they are consistent. Then run
the command mt bvc ptp reset on the PCU command terminal to reset the PTP BVC.
Checking the Data Configurations of PCU Cells

Run the command mt bvc signal show state. If the SIG BVC state is normal, run the command
mt bvc ptp show state. If the PTP BVC state is normal, you can infer that the data configurations
of cells in the PCU are incorrect. Run the command pcu show attr and cell show to check and
modify the data configurations of cells.
If the fault persists, contact Huawei Customer Service Center.
Issue 03 (2009-07-20)

3-29

BSS Weekly Maintenance Guide
About This Chapter

This describes weekly maintenance tasks and procedures.
4.1 Checking the Operating Status of the GBAM
This describes how to check the operating status of the GBAM. For the BSC configured with
the GBAM, you can check the hard disk partitioning, memory, and communication status of the
GBAM to ensure that the GBAM can normally report data.
4.2 Checking the Operating Status of the GOMU
This describes how to check the operating status of the GOMU. For the BSC configured with
the GOMU, you can check the hard disk partitioning, memory, and communication status of the
GOMU to ensure that the GOMU can normally report data.
4.3 Checking the Status of the BSC Boards (BSC LMT)
This describes how to check the status of BSC boards on the LMT. Checking the status of BSC
boards consists of querying the status of the CPU/DSP and querying the clock status of BSC
boards.
4.4 Checking the BSC Clock (BSC LMT)
Checking the BSC clock on the BSC LMT consists of checking the BSC clock reference state
and checking the BSC board clock state.
4.5 Analyzing Performance Measurement Results (M2000)
This describes how to analyze performance measurement results on the M2000. Collect a week
of performance measurement results on the M2000 client. If the results fluctuate, you need to
analyze them based on network conditions.
4.6 Collecting History Alarm Statistics (M2000)
This describes how to collect the M2000 history alarm statistics, including the fault alarms and
event alarms. The statistics are based on the factors such as the equipment type, alarm severity,
and alarm type. This also describes how to obtain the statistical tables and analytic diagrams and
save the statistical results.
4.7 Checking the Communication Between NEs and the M2000 (M2000)
This describes how to check the communication between NEs and the M2000 in the M2000
network topology.
4.8 Monitoring the BTS Software Version (BSC LMT)
Issue 03 (2009-07-20)

4-1

This describes how to monitor the BTS software versions. The task helps to avoid the mismatch
of software versions because of BTS capacity expansion or software upgrading.
4.9 Backing Up the BSS Configuration Data
This describes how to back up BSS system data on the M2000 client or on the LMT. The BSS
system data is backed up to prevent data loss due to equipment failure.
4-2

Issue 03 (2009-07-20)

4.1 Checking the Operating Status of the GBAM

This describes how to check the operating status of the GBAM. For the BSC configured with
the GBAM, you can check the hard disk partitioning, memory, and communication status of the
GBAM to ensure that the GBAM can normally report data.
4.1.1 Backing Up the Server Files to the LMT PC
This describes how to save the server files to an LMT PC.
4.1.2 Checking the Hard Disk Partitioning
This describes how to check the hard disk partitioning of the GBAM server.
4.1.3 Checking the Memory
This describes how to check the memory of the GBAM server space and their usage.
4.1.4 Checking the Communication Status of the GBAM
This describes how to check the communication status of the GBAM server to ensure its normal
communication.

Prerequisite
l
The server works and communicates with the LMT and M2000 normally.
The Samba service of the server is started.
This operation should be performed when the traffic volume is the lowest.
The sda8 partition of the server saves the traffic statistics and logs. Thus, the disk space is
totally occupied within a short time.
When you back up the BSC data, the following directory must be included:
Context
/BSC6000/data/datafile
/BSC6000/data/mtndata/alm
/BSC6000/data/mtndata/log
/BSC6000/data/mtndata/inventory
/BSC6000/data/mtndata/pfm
/BSC6000/data/mtndata/btsswm
/BSC6000/data/mtndata/transxml
Procedure
l
Synchronize the data on the server to the M2000.

1.
Issue 03 (2009-07-20)
Log in to the M2000. On the iManager M2000 Mobile Element Management

System window, choose Performance > Measure Management > Status
Browser .
4-3

2.
The Measure Management tab page is displayed. Right-click the tab page and click
Synchronize Result.
3.
The Synchronization Result dialog box is displayed. In the Measurement Period

area, select a measurement period. In the Time area, select the Start Time and End
Time. In the NE area box, select NE Type (BSC6000) and network elements on the
left and select All on the right. Click OK.
4.
The Information dialog box is displayed, indicating that the synchronization

command is successfully delivered. Click OK.
Back up the configuration data of the server to the LMT PC through the BSC6000 Local
Maintenance Terminal. Take the GOMU as example (the same as the operation of the
GBAM):
1.
Choose Configuration > Back Up > Back Up Server Data from the menu. The Back
Up GOMU Data dialog box is displayed.
2.
In the File Information on GOMU area, select the file to be backed up. In the Please
input the file name (*.dat) area box, enter the file name. In the Please select the
operation area box, select Back up to local.
NOTE
By default, the file to be backed up is saved to the directory R:\HW LMT\BSC6000

\BSC6000V900R008Cxx\BackupCfgData. (R indicates the destination where the BSC6000
Local Maintenance Terminal is installed;xx indicates the number of Version C of the
BSC6000.)
4-4
3.
Click Execute. The Information dialog box is displayed.
4.
In the Information dialog box, the message Uploading succeeded. is

displayed. Click OK.
5.
In the Back Up GOMU Data dialog box, click Exit. The configuration data of the
GOMU is backed up.
Back Up the Server Files to the LMT PC

1.
Choose Start > Run on the local PC. Enter the IP address of the server, and then click
OK to log in to the server.
2.
Start the Telnet client on the LMT PC (for example, PuTTY) and enter the IP address
of the server. After logging in to the server as user bsc6000, input the command su and press Enter to switch to user root.
3.
Run the chmod 777 /BSC6000 -R command to correct all folders and the folders
attributes in the BSC6000 directory.
4.
Access data\mtndata\log\dbg in the BSC6000 directory. Save all the files and folders
in the directory to the LMT PC.
5.
Access data\mtndata\pfm\rslt, and save all the files and folders in the directory to
the LMT PC.
6.
Keep folders in the two directories, and delete all the files in .zip format.
7.
After saving the files and folders to the LMT PC is complete, quit the remote login.
Back up the board software of the server, BSC operation data and software license to the
LMT PC.
1.
2.
Run the rcsmb status command to view the current status of samba. The normal status
of samba is shown in Figure 4-1.
Issue 03 (2009-07-20)

Figure 4-1 Querying samba status
NOTE
If samba is malfunctioning, run the rcsmb restart command to restart samba. If the problem
is still not solved, Contact Huawei Customer Service Center.
3.
Choose Start > Run on the LMT PC. Enter the IP address of the server, and then click
4.
5.
Run the chmod 777 /BSC6000 -R command on the Telnet client to modify the
attributes of all folders and files in the BSC6000 directory.
6.
Run the cp /BSC6000/bscswm /BSC6000/bscswmxxx -R command on the Telnet

client to back up the software of the BSC6000 boards on the server, where, xxx
indicates the version number of the current operating version. Enter the version
number as required.
7.
Run the cp /BSC6000/btsswm /BSC6000/btsswmxxx -R command on the Telnet

client to back up the BTS software on the server, where, xxx indicates the version
number of the current operating version. Enter the version number as required.
8.
Double-click the BSC6000 shared folder on the LMT PC, and enter the user name and
password. The default user name is bsc6000, and the password is 11111111.
9.
Copy the bscswmbxxx and btsswmxxx folders from the BSC6000 directory shared
by the server, save the files to the LMT PC.
10. Run the following commands to delete the bscswmxxx and btsswmxxx folders in the
bsc60000 folder.
rm -R /BSC6000/bscswmxxx/
rm -R /BSC6000/btsswmxxx/
11. Copy the data folder under the BSC6000 directory shared by the server, and then save
them to the LMT PC.
NOTE
The backup data is marked by the backup date on the LMT PC. If the saved folder is databxxxyyyy-mm-dd, xxx indicates the version number of current operating version. When you restore
the data by the backup file, rename the file data.
12. Copy the \bsc6000\bscswm\area1\license folder, and save to the folder in the
Common\SWM\License\bxxx directory.
----End
Postrequisite
When you restore the server data or roll back the software,
l
Issue 03 (2009-07-20)
Rename bscswmxxx and btsswmxxx folders as bscswm and btsswm respectively, and
then copy them to the BSC6000 directory. Overwrite the existing folders.
4-5


l
Copy the data folder to the BSC6000 directory, and overwrite the existing folder.
(optional) Copy the License folder to the BSC6000\bscswm\area1 directory, and

overwrite the existing folder.
4.1.2 Checking the Hard Disk Partitioning

This describes how to check the hard disk partitioning of the GBAM server.
Prerequisite
The GBAM server starts normally.
Procedure
Step 1 Start Telnet client on the LMT computer(If the KVM is not configured, log in through
PuTTY),enter the IP address of the GBAM and log in as user bsc6000.
Step 2 Enter the df -h command to check the hard disk partitioning, as shown in Figure 4-2.
NOTE
The /bsc6000 of the Mounted on indicates the software partition of the GBAM. Ensure that the partition is
at least 3 GB in size.
The /bsc6000/data of the Mounted on indicates the data partition of the GBAM server. Ensure that the
partition is at least 20 GB in size.
Figure 4-2 Checking the hard disk partitioning

linux:~ # df -h
Filesystem
/dev/sda6
tmpfs
/dev/sda7
/dev/sda8
/dev/sda1
Size
9.9G
1013M
20G
103G
251M
Used Avail Use% Mounted on

6.0G 3.5G 64% /
12K 1013M
1% /dev/shm
288M
19G
2% /BSC6000
89M
98G
1% /BSC6000/data
15M 224M
7% /boot
----End
4.1.3 Checking the Memory

This describes how to check the memory of the GBAM server space and their usage.
Prerequisite
The GBAM server starts normally.
Procedure
Step 2 Enter the free -m command to check the size of the GBAM memory,as shown in Figure 4-3.
Figure 4-3 Checking the memory
4-6

Issue 03 (2009-07-20)

NOTE
Before installing the OMU Software,ensure that the free size of the memory is at least 512 MB,
----End
4.1.4 Checking the Communication Status of the GBAM

This describes how to check the communication status of the GBAM server to ensure its normal
communication.
Prerequisite
l
The GBAM server is running normally.
The OMU software is installed on the GBAM server.
Procedure
Step 2 Enter the ifconfig command to check the network settings of the GBAM server.
Step 3 If the network settings are incorrect, enter the omuctrl status command to check the operating
status of the OMU software.
l
If the OMU software is running normally, go to Step 4.
If the message No omu process is running. is displayed, go to Step 5.

NOTE
For normal network settings, refer to Checking the Ethernet Adapter Teaming on the GBAM.
Step 4 Run the omuctrl status command to stop the OMU software.
Step 5 Run the omuctrl cfg command to reconfigure the network parameters of the GBAM server.
Step 6 Run the omuctrl start command to restart the OMU software.
----End
4.2 Checking the Operating Status of the GOMU

This describes how to check the operating status of the GOMU. For the BSC configured with
the GOMU, you can check the hard disk partitioning, memory, and communication status of the
GOMU to ensure that the GOMU can normally report data.
4.2.1 Checking and Cleaning Up the Server Hard Disk Space Regularly
This describes how to check and clean up the hard disk space of the server regularly to ensure
that the available space of each directory is not less than 20% of the total space.
4.2.3 Checking the Hard Disk Partitioning of the GOMU Board
This describes how to check the hard disk partitioning of the GOMU.
Issue 03 (2009-07-20)

4-7

4.2.4 Checking the Memory Capacity of the GOMU Board

This describes how to check the size and usage of the GOMU memory.
4.2.1 Checking and Cleaning Up the Server Hard Disk Space

Regularly
This describes how to check and clean up the hard disk space of the server regularly to ensure
that the available space of each directory is not less than 20% of the total space.
Prerequisite
The server works normally.
Procedure
Step 1 Start the Telnet client on the LMT PC (for example, PuTTY) and enter the IP address of the
server. After logging in to the server as user bsc6000, input the command su - and press
Enter to switch to user root.
Step 2 Run the df -h command to check the partition and usage of the server hard disk.
1.
If the directory space is less than 20% of the total hard disk space, save the files of this
directory to a storage medium by referring to 4.2.2 Backing Up the Server Files to the
LMT PC.
2.
If there is no such a directory, go to Step 3.
Step 3 Exit PuTTY.

----End

Prerequisite
l
The server works and communicates with the LMT and M2000 normally.
The Samba service of the server is started.
This operation should be performed when the traffic volume is the lowest.
The sda8 partition of the server saves the traffic statistics and logs. Thus, the disk space is
totally occupied within a short time.
When you back up the BSC data, the following directory must be included:
Context
4-8
/BSC6000/data/datafile
/BSC6000/data/mtndata/alm
/BSC6000/data/mtndata/log
/BSC6000/data/mtndata/inventory
/BSC6000/data/mtndata/pfm
/BSC6000/data/mtndata/btsswm
Issue 03 (2009-07-20)

/BSC6000/data/mtndata/transxml
Procedure
l
Synchronize the data on the server to the M2000.

1.
Log in to the M2000. On the iManager M2000 Mobile Element Management

System window, choose Performance > Measure Management > Status
Browser .
2.
The Measure Management tab page is displayed. Right-click the tab page and click
Synchronize Result.
3.
The Synchronization Result dialog box is displayed. In the Measurement Period

area, select a measurement period. In the Time area, select the Start Time and End
Time. In the NE area box, select NE Type (BSC6000) and network elements on the
left and select All on the right. Click OK.
4.
The Information dialog box is displayed, indicating that the synchronization

command is successfully delivered. Click OK.
Back up the configuration data of the server to the LMT PC through the BSC6000 Local
Maintenance Terminal. Take the GOMU as example (the same as the operation of the
GBAM):
1.
Choose Configuration > Back Up > Back Up Server Data from the menu. The Back
Up GOMU Data dialog box is displayed.
2.
In the File Information on GOMU area, select the file to be backed up. In the Please
input the file name (*.dat) area box, enter the file name. In the Please select the
operation area box, select Back up to local.
NOTE
By default, the file to be backed up is saved to the directory R:\HW LMT\BSC6000

\BSC6000V900R008Cxx\BackupCfgData. (R indicates the destination where the BSC6000
Local Maintenance Terminal is installed;xx indicates the number of Version C of the
BSC6000.)
Issue 03 (2009-07-20)
3.
Click Execute. The Information dialog box is displayed.
4.
In the Information dialog box, the message Uploading succeeded. is

displayed. Click OK.
5.
In the Back Up GOMU Data dialog box, click Exit. The configuration data of the
GOMU is backed up.
Back Up the Server Files to the LMT PC

1.
Choose Start > Run on the local PC. Enter the IP address of the server, and then click
2.
3.
Run the chmod 777 /BSC6000 -R command to correct all folders and the folders
attributes in the BSC6000 directory.
4.
Access data\mtndata\log\dbg in the BSC6000 directory. Save all the files and folders
in the directory to the LMT PC.
5.
Access data\mtndata\pfm\rslt, and save all the files and folders in the directory to
the LMT PC.
6.
Keep folders in the two directories, and delete all the files in .zip format.
4-9

7.
l
After saving the files and folders to the LMT PC is complete, quit the remote login.
Back up the board software of the server, BSC operation data and software license to the
LMT PC.
1.
2.
Run the rcsmb status command to view the current status of samba. The normal status
of samba is shown in Figure 4-4.
Figure 4-4 Querying samba status
NOTE
If samba is malfunctioning, run the rcsmb restart command to restart samba. If the problem
is still not solved, Contact Huawei Customer Service Center.
3.
Choose Start > Run on the LMT PC. Enter the IP address of the server, and then click
4.
5.
Run the chmod 777 /BSC6000 -R command on the Telnet client to modify the
attributes of all folders and files in the BSC6000 directory.
6.
Run the cp /BSC6000/bscswm /BSC6000/bscswmxxx -R command on the Telnet

client to back up the software of the BSC6000 boards on the server, where, xxx
indicates the version number of the current operating version. Enter the version
number as required.
7.
Run the cp /BSC6000/btsswm /BSC6000/btsswmxxx -R command on the Telnet

client to back up the BTS software on the server, where, xxx indicates the version
number of the current operating version. Enter the version number as required.
8.
Double-click the BSC6000 shared folder on the LMT PC, and enter the user name and
password. The default user name is bsc6000, and the password is 11111111.
9.
Copy the bscswmbxxx and btsswmxxx folders from the BSC6000 directory shared
by the server, save the files to the LMT PC.
10. Run the following commands to delete the bscswmxxx and btsswmxxx folders in the
bsc60000 folder.
rm -R /BSC6000/bscswmxxx/
rm -R /BSC6000/btsswmxxx/
11. Copy the data folder under the BSC6000 directory shared by the server, and then save
them to the LMT PC.
NOTE
The backup data is marked by the backup date on the LMT PC. If the saved folder is databxxxyyyy-mm-dd, xxx indicates the version number of current operating version. When you restore
the data by the backup file, rename the file data.
4-10

Issue 03 (2009-07-20)

12. Copy the \bsc6000\bscswm\area1\license folder, and save to the folder in the
Common\SWM\License\bxxx directory.
----End
Postrequisite
When you restore the server data or roll back the software,
l
Rename bscswmxxx and btsswmxxx folders as bscswm and btsswm respectively, and
then copy them to the BSC6000 directory. Overwrite the existing folders.
Copy the data folder to the BSC6000 directory, and overwrite the existing folder.
(optional) Copy the License folder to the BSC6000\bscswm\area1 directory, and

overwrite the existing folder.
4.2.3 Checking the Hard Disk Partitioning of the GOMU Board

This describes how to check the hard disk partitioning of the GOMU.
Prerequisite
The GOMU board starts normally.
Procedure
Step 1 Start Telnet client, such as PuTTY on the LMT computer, enter the IP address of the GOMU
and log in as user bsc6000.
Step 2 Enter the df -h command to check the hard disk partitioning, as shown in Figure 4-5.
NOTE
The /bsc6000 of the Mounted on indicates the software partition of the GOMU. Ensure that the partition
is at least 3 GB.
The /bsc6000/dataof the Mounted on indicates the data partition of the GOMU. Ensure that the partition
is at least 40 GB.
Figure 4-5 Checking the hard disk partitioning

inux:~ # df -h
Filesystem
/dev/sda6
tmpfs
/dev/sda7
/dev/sda8
/dev/sda1
Size
9.9G
1013M
5.0G
51G
130M
Used Avail Use% Mounted on

1.8G 7.6G 20% /
4.0K 1013M
1% /dev/shm
904M 3.8G 19% /BSC6000
1.4G
47G
3% /BSC6000/data
11M 113M
9% /boot
----End
4.2.4 Checking the Memory Capacity of the GOMU Board

This describes how to check the size and usage of the GOMU memory.
Prerequisite
The GOMU board starts normally.
Issue 03 (2009-07-20)

4-11

Procedure
Step 1 Start Telnet client, such as PuTTY on the LMT computer, enter the IP address of the GOMU
and log in as user bsc6000.
Step 2 Enter the free -m command to check the size and the usage of the memory,as shown in Figure
4-6.
Figure 4-6 Checking the memory
NOTE
Before installing the OMU Software,ensure that the free size of the memory is at least 512 MB,
----End
4.3 Checking the Status of the BSC Boards (BSC LMT)

This describes how to check the status of BSC boards on the LMT. Checking the status of BSC
boards consists of querying the status of the CPU/DSP and querying the clock status of BSC
boards.
4.3.1 Querying the CPU/DSP Status
This describes how to query the status of the CPUs and how to query the status of the DSP unit
in the GDPUC/GDPUX/GDPUP.
4.3.2 Querying the Clock Status of a Board
This describes how to query the status of the input clock of a board.
4.3.1 Querying the CPU/DSP Status

This describes how to query the status of the CPUs and how to query the status of the DSP unit
in the GDPUC/GDPUX/GDPUP.
Prerequisite
l
The LMT runs normally.
The communication between the LMT and the BSC is normal.
All the boards are functional.
Context
Table 4-1 describes the CPU/DSP states that can be queried on the LMT.
4-12

Issue 03 (2009-07-20)

Table 4-1 Board status

Parameter
Meaning
Value Range
Admin state
Indicating whether the

current board can provide
services or not
Lock: The current board cannot provide

services.
Unlock: The current board can provide

services, but whether it actually
provides services depends on other
states, such as operation state and
standby state.
Shutdown: New services cannot access

the current board, but the existing
services on the board continue.
NOTE
After all the services on the board exit, the
board enters Shutdown automatically.
Operation state
Standby state
Available state

current board can be
operated or not
Enable: The current board can be

operated.
Disable: The current board cannot be

operated.

current board works in
active mode or standby
mode
Active: The current board works in

active mode.
Standby: The current board works in

standby mode.
Unassigned: The current board is not in

active/standby mode.
Invalid: The current board is not ready.
Normal: The current board is running

properly.
Fault: The current board is faulty.
Uninstalled: The current board is not in

position.
Inconsistent: The status information

about the current board is inconsistent
with the configuration information
about the slot.
Power off: The current board is

powered off.
indicating more
information about the board
usage state
The method of querying CPU state is the same as that of querying DSP state. This topic takes
querying the CPU state as an example.
Procedure
l
Issue 03 (2009-07-20)
Through GUI
4-13

1.
On the LMT, choose BSC Maintenance > Maintain Device > Query CPU/DSP
State.
2.
Select CPU in the Query Type area, set parameters in the Location area, and then
click Query. The results are displayed, as shown in Figure 4-7.
Figure 4-7 Querying the CPU state
Through MML
1.
You can run the following commands on the Local Maintenance Terminal to query
the CPU/DSP status.
Run the DSP CPUSTAT to query the CPU status.
Run the DSP DSPSTAT to query the DSP status.
----End

Prerequisite
l
Context
Table 4-2 lists the clock types for different boards.
4-14

Issue 03 (2009-07-20)

Table 4-2 Boards and their corresponding clocks

Board
Clock
GDPUC/GDPUX/GDPUP
TDM 32.768 MHz clock
GTNU
GSCU in the GMPS
Status of the 8 kHz reference clock from the active GGCU

Status of the 8 kHz reference clock from the standby
GGCU
GSCU in the GEPS
Status of the 8 kHz reference clock from the GGCU
GSCU in the GTCS
0-line back slot 8 kHz reference clock status

GEIUA/GEIUT/GEIUB/
GEIUP
GOIUA/GOIUT/GOIUB/
GOIUP
GFGUA/GFGUB/GFGUG
Low subboard 2 MHz clock
GOGUA/GOGUB
Top subboard 0 2 MHz clock
GEHUB/GEPUG

Backplane SDH 8 kHz clock
Backplane SDH 19 MHz clock
Backplane TDM 8 kHz clock
Backplane TDM 32 MHz clock
Backplane 0 8 kHz clock
On the LMT, the clock status of the GXPUM, the GXPUT, and the server cannot be queried.
This topic takes querying the clock status of the GTNU as an example. The method for querying
the clock status of other boards is the same.
Procedure
l
Issue 03 (2009-07-20)
Through GUI
1.
On the LMT, choose BSC Maintenance > Maintain Device > Query BSC Board
Clock State.
2.
Set parameters in the Location area, and then click Query. The query result is
displayed, as shown in Figure 4-8.

4-15

Figure 4-8 Query result of the board clock status
Through MML
1.
Run the DSP BRDCLK command on the Local Maintenance Terminal to query the
board clock state.
----End
4.4 Checking the BSC Clock (BSC LMT)

Checking the BSC clock on the BSC LMT consists of checking the BSC clock reference state
and checking the BSC board clock state.
4.4.2 Maintaining the BSC Clock Reference Status
This describes how to query the status of the BSC clock reference for the GGCU. Check whether
the PLL status of the BSC clock reference source is trace locked, check from which line clock
the clock is obtained, and check the time when the PLL locks the clock.
4-16

Issue 03 (2009-07-20)


Prerequisite
l
Context
Table 4-3 lists the clock types for different boards.
Table 4-3 Boards and their corresponding clocks
Board
Clock
GDPUC/GDPUX/GDPUP
GTNU
GSCU in the GMPS
Status of the 8 kHz reference clock from the active GGCU

Status of the 8 kHz reference clock from the standby
GGCU
GSCU in the GEPS
Status of the 8 kHz reference clock from the GGCU
GSCU in the GTCS

GEIUA/GEIUT/GEIUB/
GEIUP
GOIUA/GOIUT/GOIUB/
GOIUP
GFGUA/GFGUB/GFGUG
Low subboard 2 MHz clock
GOGUA/GOGUB
GEHUB/GEPUG

Backplane SDH 8 kHz clock
Backplane SDH 19 MHz clock
Backplane TDM 8 kHz clock
Backplane TDM 32 MHz clock
On the LMT, the clock status of the GXPUM, the GXPUT, and the server cannot be queried.
This topic takes querying the clock status of the GTNU as an example. The method for querying
the clock status of other boards is the same.
Issue 03 (2009-07-20)

4-17

Procedure
l
Through GUI
1.
On the LMT, choose BSC Maintenance > Maintain Device > Query BSC Board
Clock State.
2.
Set parameters in the Location area, and then click Query. The query result is
displayed, as shown in Figure 4-9.
Figure 4-9 Query result of the board clock status
Through MML
1.
Run the DSP BRDCLK command on the Local Maintenance Terminal to query the
board clock state.
----End
4.4.2 Maintaining the BSC Clock Reference Status

This describes how to query the status of the BSC clock reference for the GGCU. Check whether
the PLL status of the BSC clock reference source is trace locked, check from which line clock
the clock is obtained, and check the time when the PLL locks the clock.
4-18

Issue 03 (2009-07-20)

Prerequisite
l
The GGCU is running properly.
Context
The GGCU is the clock board for the BSC system. After the clock reference signals are
transmitted to the GGCU, a line of clock is selected in Manual or Automatic mode and
converted to clock signals for the entire system after the phase-locked tracing. The clock signals
are then transmitted to the GSCU in each subrack through the backplane or the panel.
Procedure
l
Through GUI
1.
On the LMT, choose BSC Maintenance > Maintain Device > Query BSC Clock
Reference State.
2.
Set parameters in the Select GGCU Slot No. area, and then click Refresh. The query
results are displayed, as shown in Figure 4-10.
Figure 4-10 Querying the clock reference status
Issue 03 (2009-07-20)

4-19

3.
l
Click Cancel to end the query.
Through MML
1.
Run the DSP CLKSTAT command on the Local Maintenance Terminal to query the
BSC clock reference status.
----End
Postrequisite
Without the clock reference, the BSC can still run for a period of time by using the free-run
clock, but finally the BSC stops working.
4.5 Analyzing Performance Measurement Results (M2000)

This describes how to analyze performance measurement results on the M2000. Collect a week
of performance measurement results on the M2000 client. If the results fluctuate, you need to
analyze them based on network conditions.
Prerequisite
l
You have the authority to query the results of BSC performance measurement.
Context
The key performance counters in the routine maintenance are the BSS performance counters
and the GPRS performance counters.
Table 4-4 lists the recommended standards for the BSS performance counters. Table 4-5 lists
the recommended standards for the GPRS performance counters.
Table 4-4 Key BSS performance counters in weekly maintenance
4-20
Counter
Recommended Standard
Success Rate of Call Setup (Immediate Assignment)
>92%
Success Rate of TCH Assignment
>94%
TCH Call Drop Rate (Including Handover)
<2%
TCH Call Drop Rate (Excluding Handover)
<2%
Call Drop Rate on SDCCH
<2%
Congestion Ratio on TCH (All Channels Busy)
<5%
Congestion Ratio on SDCCH per CELL (due to Busy)
<5%
Internal Handover Success Ratio per Cell
>92%

Issue 03 (2009-07-20)

Counter
Success Rate of Incoming External Inter-Cell Handovers
>86%
Success Rate of Outgoing External Inter-Cell Handover
>86%
Traffic Volume on TCH
Subject to network
conditions
Traffic Call Drop Ratio per cell
Subject to network
conditions
Table 4-5 Key GPRS performance counters in weekly maintenance

Counter
Uplink Assignment Success Ratio
>90%
Downlink Assignment Success Ratio
>80%
Uplink TBF congestion rate
<5%
Downlink TBF congestion rate
<5%
PDCH usage
Subject to network conditions
Uplink GPRS TBF Call Drop Rate
<3%
Downlink GPRS TBF Call Drop Rate
<5%
Procedure
Step 1 Choose Performance > Query Result.
Step 2 In the Query Result window, click New Query.
Step 3 Perform the following operations:
1.
Select the object type or the function subset.
2.
In the three tabs of the right pane, specify the object, item, and period for measurement.
3.
Click Query. The query result is displayed.

NOTE
The query result can be displayed in three forms: table, line chart, and bar chart.
Step 4 Compare the values of these items with those required by the site. If you find any inconsistency,
report it to engineers for troubleshooting.
----End
Issue 03 (2009-07-20)

4-21

Postrequisite
Table 4-6 lists the solutions to some abnormal counters.
Table 4-6 Solutions to some abnormal counters
Fault
Description
Possible Cause
Solution
High CPU
usage
The high CPU usage

may be caused by
different factors.
If the CPU usage of a BSC board is too high, the

BSC may start flow control and the services will
be affected. Therefore, handle this fault in time if
the CPU usage exceeds the threshold. The high
CPU usage may be caused by different factors.
Contact Huawei for technical support.
Low success
rate of
handovers
The handover
threshold is too low.
The neighbor cells

are congested. There
are no idle channels.
The neighbor relation

is not configured.
The settings of
handover hysteresis
and handover priority
are improper.
The settings of best

cell measurement
time N and P are
improper.
In the hybrid
networking with the
external cells (from
other manufacturers),
the parameters such
as LAC, CI, and
BCCH of the external
cells are incorrect.
High call
drop rate on
TCHs and
SDCCHs
4-22
T3103 timeout
Rectify the faults based on the causes.
If the timing length of T3103 is too short, the

number of call drops may increase. The handover
failure and call re-establishment failure lead to call
drops, If the timing length of T3103 is too short,
the channel retaining time is too short for the
channel in the source cell to reconnect the MS after
a handover failed. Therefore, the call drop rate
rises. You need to set the timing length of T3103
to a proper value.

Issue 03 (2009-07-20)

Fault
Description
High TCH
congestion
rate
Issue 03 (2009-07-20)
Possible Cause
Solution
Radio link failure
Interference: Perform drive tests to check

equipment. Check the area where interference
occurs and find the interference frequencies.
Use a spectrum analyzer to further locate the
interference source. If functions such as
frequency hopping, DTX, and power control
are enabled, the internal interference will be
greatly reduced.
Coverage: Regulate network parameters. Add

more BTSs.
Improper parameter settings: Regulate

parameters to proper values.
Equipment problems: Rectify equipment

problems.
The configurations of
trunk circuits on the A
interface are incorrect.
The TSC and the BCC of

a frequency hopping cell
are inconsistent.
The TCH assignment

fails because of the same
frequency and BSIC.
Board fault or unreliable

board performance
leads to a high
congestion rate.
Find the faulty board and replace it.
BTS hardware (antenna

and feeder) is
improperly installed.
This leads to unbalance
between the uplink level
and the downlink level
and TCH congestion
occurs.
Correctly install BTS hardware.
The cell connects with a

repeater. The cell
capacity is expanded but
the repeater capacity is
not.
Expand the capacity of the repeater.

4-23

Fault
Description
High
SDCCH
congestion
rate
Possible Cause
Solution
In the same cell, the

transmit power of the
TRX carrying the
primary BCCH is
greater than that of the
TRX carrying the TCH.
Modify antenna attributes or network parameters

to optimize the coverage of the primary BCCH
and the TCH.
Interference
Analyze the results of performance measurement

and eliminate interference. For details, refer to the
troubleshooting guide.
TCH assignment fails

because of the isolated
site or complex terrain.
Therefore, the
congestion rate rises.
Optimize the network based on the coverage

problems.
SDCCH location
updating occurs
frequently because the
cell is on the edge of the
location area.
Modify the settings of location area selection, Cell

Reselection Hysteresis (CRH), and periodic
location updating, and modify the dual-band
network planning to avoid frequent handovers.
Frequent short messages

and weather forecasting
Do not send too many short messages at a time.

Configure more SDCCHs.
Insufficient system
capacity: There are not
enough SDCCHs
configured.
Expand the capacity.
System parameter
configuration error,
improper RACH access
threshold
Improve the RACH access threshold to reduce

interference. Reduce the maximum number of
retransmissions and increase the Tx-integer.
Board (TRX) fault or

transmission fault
Rectify the fault.
4.6 Collecting History Alarm Statistics (M2000)

This describes how to collect the M2000 history alarm statistics, including the fault alarms and
event alarms. The statistics are based on the factors such as the equipment type, alarm severity,
and alarm type. This also describes how to obtain the statistical tables and analytic diagrams and
save the statistical results.
Prerequisite
l
4-24
Issue 03 (2009-07-20)

You have the authority to operate the related network element.
You have the authority to collect alarm statistics.

NOTE
The procedures of collecting the statistics of event alarms and fault alarms are the same. The following
part describes how to collect the statistics of fault alarms as an example.
Procedure
l
Collect the alarm statistics using the Statistic Filter.

1.

The Statistic Filter dialog box is displayed. as shown in Figure 4-11.
Figure 4-11 Collecting the statistics of fault alarms
2.
Issue 03 (2009-07-20)
In the Statistic Filter dialog box, set the fault alarm statistical conditions, and then
click OK.

4-25


NOTE
The statistical results are displayed on the Table and Pie tabs.
3.
On the Table tab page, the results are displayed in a table.
On the Pie tab page, the results are displayed in pie charts. Click the tab of an item name to view
the corresponding pie chart.
In the statistical result window, click Save As to save the result in a file.
NOTE
If you click Table tab, the file can be saved in the *.txt, *.html, or *.csv format.
NOTE
When a CSV file contains more than 256 lines, it cannot be opened by Excel. Use a text editing
tool such as UltraEdit or notepad to open the file.
l
4.
l
If you click the Pie tab, the file can be saved in *.jpg format.
In the statistical result window, click the Table tab. Click Print to print the statistical
result.
Collect the alarm statistics using the template.

1.
2.
In the Statistic Filter dialog box, click Cancel.
3.
In the Fault Alarm Statistics tab page, click Template, and then select New.
4.
In the Enter The Template Name dialog box, enter the template name. Select Set
Default Template or Set auto load template as required. Click OK
NOTE
After you log in to the M2000 client, it opens all auto-loaded templates and displays
corresponding alarms of these templates.
When alarm statistics is collected, the M2000 automatically opens the default template.
5.
In the Statistic Filter dialog box, set the alarm statistical conditions, and then click
OK.
6.
In the Confirmation dialog box, click Yes.
----End
4.7 Checking the Communication Between NEs and the

M2000 (M2000)
This describes how to check the communication between NEs and the M2000 in the M2000
network topology.
Prerequisite
l
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-12.
4-26

Issue 03 (2009-07-20)

Figure 4-12 M2000 network topology
Procedure
Step 1 Log in to the M2000 and 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.
4.8 Monitoring the BTS Software Version (BSC LMT)

This describes how to monitor the BTS software versions. The task helps to avoid the mismatch
of software versions because of BTS capacity expansion or software upgrading.
Prerequisite
l
The LMT is running normally.
The LMT is in normal communication with the BSC.
The communication between the BSC and the BTS is normal.
Issue 03 (2009-07-20)

4-27

Context
Criterion for the operation: The board software versions of all the BTSs are correct.
Procedure
Step 1 Choose BTS Maintenance > Query Board Running Software Version.
The Query Board Running Software Version window is displayed, as shown in Figure
4-13.
Figure 4-13 Query Board Running Software Version window (1)
Step 2 Set Site Type and select sites from the Candidate Sites box and add them to the Selected
Sites box.
Step 3 Set Board Type and click Start. The query result is displayed in the Result area, as shown in
Figure 4-14.
4-28

Issue 03 (2009-07-20)

Figure 4-14 Query Board Running Software Version window (2)
----End
Postrequisite
Upgrade the software at a suitable time.
4.9 Backing Up the BSS Configuration Data

This describes how to back up BSS system data on the M2000 client or on the LMT. The BSS
system data is backed up to prevent data loss due to equipment failure.
4.9.1 Basic Knowledge of BSS Data Backup
This describes the basic knowledge of data management that you must know before performing
data management operations.
4.9.2 Automatically Backing Up the BSC Configuration Data (M2000)
This describes how to set the automatic backup of the BSS configuration data on the M2000.
Through the NE backup task, you can set the automatic backup of the BSC, BTS, and external
PCU.
4.9.3 Manually Backing Up the BSC Configuration Data (M2000)
This describes how to manually back up the BSC configuration data on the M2000.
4.9.4 Manually Backing Up the PCU System Data (M2000)
This describes how to manually back up the PCU system data on the M2000.
Issue 03 (2009-07-20)

4-29

4.9.1 Basic Knowledge of BSS Data Backup

This describes the basic knowledge of data management that you must know before performing
data management operations.
NE Data Backup on the M2000

The M2000 provides the function of backing up the NE data. Through this function, all NE
configuration files and the dynamic data that changes when NE is running can be backed up.
The NE data can be backed up either periodically or manually. A backup file, however, is
generated on the M2000 server every time a backup task is performed regardless of the backup
mode.
The M2000 supports a maximum of 50 NE backup tasks.
The number of backup files that can be saved on the M2000 server is determined by the M2000
configuration file. Currently, the M2000 supports a maximum of seven backup files of an NE.
When the number of backup files of an NE is greater than seven, the file backed up at the earliest
time is automatically deleted and the NE backup list is updated.
The backup file is saved to the M2000 server/export/home/sysm/ftproot/NE type/data type/
NE FDN directory.
l
The naming convention for the manually backed up file is BAKDATA+current time.
The units of Period can be set to days, weeks, and months.
Periodic backup can be classified into full backup and incremental backup.
Every time a full backup task is performed, the system deletes the earlier full backup
files and incremental backup files on the server. Only the latest full backup compressed
file is stored. The full backup file must be named in the format of all-current time, for
example, all-20060106103055.tar.gz.
Every time an incremental backup task is performed, a new backup file is generated.
The incremental backup task is performed on the basis of the earlier backup. The earlier
backup can be a full backup or an incremental backup. The incremental backup file must
be named in the format of inc-current time.
BSS System Data Backup

The BSS system data backup consists of the configuration data backup and data backup before
major events.
l
Routine data backup

Routine data backup is performed to save the data that is generated during the daily
operation of the system. In the case of exceptions, you can use the backup data to restore
the data and to prevent huge loss.
4-30
BSC or BTS configuration data backup
Huawei recommends that you back up the BSC or BTS configuration data once a
day.
The device that stores the backup data should be kept properly and labeled with
detailed descriptions.
PCU configuration data backup

Issue 03 (2009-07-20)

Huawei recommends that you back up the PCU configuration data once a month.
The device that stores the backup data should be kept properly and labeled with
detailed descriptions.
Data backup before major events

Data backup before major events refers to the data backup performed before major events
such as upgrade and capacity expansion occur. In the case of exceptions such as system
crash and upgrade failure, you can use the latest backup data to restore the system.
4.9.2 Automatically Backing Up the BSC Configuration Data

(M2000)
This describes how to set the automatic backup of the BSS configuration data on the M2000.
Through the NE backup task, you can set the automatic backup of the BSC, BTS, and external
PCU.
Prerequisite
Context
The NE backup task refers to saving the NE data as the backup file to the specified directory on
the M2000 server. This task is performed to prevent data loss and to restore NEs when they are
faulty.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Click New. The New Task dialog box is displayed.
Step 3 Set the basic information of 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 4 Click Next. Set Start Time.

Step 5 Click Next to select backup type. The following backup types are available: Backup ALL
NE, By NE Type, and By NE.
Step 6 Click Finish.
----End
4.9.3 Manually Backing Up the BSC Configuration Data (M2000)

This describes how to manually back up the BSC configuration data on the M2000.
Prerequisite
l
Issue 03 (2009-07-20)
The communication between the BSC/BTS and the M2000 is normal.

4-31


l
The FTP server is set up on the M2000.
You have the right to perform operations.
Context
The naming convention of manually backed up file is BAKDATA+current time. The M2000
server is used as the FTP server to connect the client and the NE.
Procedure
Step 1 Choose Maintenance > Backup Management. The Backup Management window is
displayed.
Step 2 Click the NE Backup List tab.
Step 3 Select a BSC/BTS.
l
You can press Ctrl to select multiple NEs. To select all the NEs, click the root node.
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. You can select sub NEs under this NE
for backup.
Step 4 Click Backup. The Confirm dialog box is displayed. Click Yes.
In the Backup Management window, the real-time progress and detailed information of the
backup task are displayed in the Backup Task List.
----End
4.9.4 Manually Backing Up the PCU System Data (M2000)

This describes how to manually back up the PCU system data on the M2000.
Prerequisite
l
The communication between the PCU and the M2000 is normal.
The FTP server is set up on the M2000.
Context
Naming convention of the backup file: BAKDATA+current time. For daylight saving time, DST
should be added after the current time. The M2000 server is used as the FTP server to connect
the client and the NE.
Procedure
Step 1 Choose Maintenance > Backup Management. The Backup Management window is
displayed.
Step 2 Click the NE Backup List tab.
4-32

Issue 03 (2009-07-20)

Step 3 Select a PCU.

l
You can press Ctrl to select multiple NEs. To select all the NEs, click the root node.
If the selected NE contains sub NEs, a dialog box is displayed, asking you whether to back
up the data of all the sub NEs under the selected NE. You can select sub NEs under this NE
for backup.
Step 4 Click Backup. The Confirm dialog box is displayed. Click Yes.
In the Backup Management window, the real-time progress and detailed information of the
backup task are displayed in the Immediate Task List.
----End
Issue 03 (2009-07-20)

4-33

BSS Monthly Maintenance Guide
About This Chapter

This describes monthly maintenance tasks and procedures.
5.1 Analyzing Customer Complaints
This describes how to find the causes and tendency of faults. The task helps to handle problems
at points of frequent faults.
5.2 Making the Network Performance Report
This describes how to make a BSS performance report based on the fault tendency.
5.3 Checking the Disk Space of the BSS Maintenance Terminal
This describes how to check the disk space of the BSS maintenance terminal. You need to check
the disk space of the BSS maintenance terminal periodically to avoid insufficient disk space.
5.4 Checking the BSS Maintenance Terminal for Viruses
This describes how to check the BSS maintenance terminal for viruses.
5.5 Backing Up the BSC/BTS Program Files
This describes how to back up the BSC/BTS program files through the Samba services or through
the M2000.
Issue 03 (2009-07-20)

5-1

5.1 Analyzing Customer Complaints

This 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. For details, refer to
the BSS Troubleshooting Guide.
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
Postrequisite
Based on the customer complaints, you can determine whether the equipment incurs faults. If
customers complain about bad speech quality, you need to consider the insufficient coverage
and interference problems. Table 5-1 lists the analysis of customer complaints.
Table 5-1 Analysis of customer complaints
Complaint
Possible Cause
Locating Method
Weak signals
and
bad
speech quality
Bad network coverage
Analyze
the
results
of
performance measurement and
perform driving tests.
Interference
Analyze
the
results
of
BSS equipment incurs faults
Check the running status of the

equipment.
Interference or weak signals
Analyze
the
results
of
Handset problems
Check the models of handsets.
Data configuration problems
Check the data configurations.
Noise, echoes,
one-way
audio, or other
problems
occur
in
speech.
5-2

Issue 03 (2009-07-20)

Complaint
Calls cannot
be made.
Network
access failed
using
the
GPRS
services
Slow GPRS
services
Possible Cause
Locating Method
BSS equipment or transmission incurs

faults.

equipment.
Handset problems, such as hardware

failure, defaulting, and SIM card
problems.
Rectify the problems.
Network congestion
Analyze
the
results
of
expand network capacity.
Bad network coverage
Analyze
the
results
of
Equipment failure, such as the failure of

the MSC, BSC, and BTS

equipment.
Data Configuration Problem
Check the data configurations of

each NE.
Handset problems, such as hardware

limitation, handset setting error,
defaulting, and SIM card problems.
Rectify the problems.
The GPRS services are unavailable in

the cells where the handsets are located.
PDCH congestion
Analyze
the
results
performance measurement.
The GPRS status of cells is abnormal.
Check the data configurations

and the running status of the
equipment.

the SGSN, BSC, PCU, and BTS.

equipment.
Handset problems
Check the models and network

configurations of handsets.
Busy PDCH
Analyze
the
results
performance measurement.
Incorrect data configurations of the

SGSN, PCU, and BTS

the SGSN, BSC, PCU, and BTS.

equipment.
of
of
5.2 Making the Network Performance Report

This describes how to make a BSS performance report based on the fault tendency.
Issue 03 (2009-07-20)

5-3

Procedure
Step 1 Identify and analyze the faults that have occurred in this month. For details, refer to 5.1
Analyzing Customer Complaints.
Step 2 Collect the monthly performance data, such as performance statistics, history performance data,
and system monitoring data. Find out the change tendency in the monthly performance data.
Step 3 Collect the daily and weekly monitoring reports on routine network performance, and then find
out the change tendency of BSS performance. The monitoring items are the same as those of
monthly maintenance. You have to make a tendency chart based on the performance.
Step 4 Make a monthly report on BSS performance based on the collected statistics.
----End
5.3 Checking the Disk Space of the BSS Maintenance

Terminal
This describes how to check the disk space of the BSS maintenance terminal. You need to check
the disk space of the BSS maintenance terminal periodically to avoid insufficient disk space.
Prerequisite
Context
Criterion for the operation: For the M2000 client, BSC LMT, PCU, and BTS, the free space of
the hard disk should be at least 50% of the total capacity.
Procedure
Step 1 Check whether there are temporary files, such as the message tracing file, alarm file, and
performance file. If there are temporary files, delete them.
Step 2 Check whether there are software programs that are not required by operation and maintenance.
If there are such software programs, delete them.
Step 3 Check whether there are backup files not required. If there are backup files not required, delete
them or move them to other magnetic media.
----End
5.4 Checking the BSS Maintenance Terminal for Viruses

This describes how to check the BSS maintenance terminal for viruses.
Prerequisite
5-4
You have upgraded the antivirus software.

Issue 03 (2009-07-20)

Context
Criterion for the operation: No terminal system is infected by viruses.
Procedure
Step 1 Use the upgraded antivirus software to scan the entire system, including the M2000, LMT, and
PCU maintenance system.
----End
Postrequisite
If a virus is detected, clear it according to the information provided by the antivirus software. If
an exception occurs after the virus is killed, for example, the BSS software is damaged and
cannot work normally, contact Huawei for technical support.
5.5 Backing Up the BSC/BTS Program Files

This describes how to back up the BSC/BTS program files through the Samba services or through
the M2000.
5.5.1 Backing Up the BSC/BTS Program Files (Samba)
This describes how to back up the BSC/BTS program files through the Samba shared services.
5.5.2 Backing Up the BSC/BTS Program Files (M2000)
This describes how to back up the BSC/BTS program files on the M2000. The backup of the
BSC/BTS program files on the M2000 consists of two procedures: transferring files from the
NE to the NM and transferring files from the NM to the M2000 client.
5.5.1 Backing Up the BSC/BTS Program Files (Samba)

This describes how to back up the BSC/BTS program files through the Samba shared services.
Prerequisite
The Samba service of the GBAM/GOMU is started.
Context
l
Backing up BSC files

Back up BSC files from the BSC to the LMT PC. The BSC files consist of configuration
data files, board program files, board patch files, level 2 BIOS files, and license file.
Backing up BTS files

Back up BTS files from the BSC to the LMT PC.
Procedure
Step 1 On the LMT PC, choose Start > Run, and then enter the IP address of the GBAM/GOMU. The
login window is displayed.
Step 2 Enter the correct user name and password to display the GBAM/GOMU sharing file directory.
Issue 03 (2009-07-20)

5-5

Step 3 Double-click the bsc6000 folder to expand it.

Step 4 Right-click the bscswm folder and choose Copy from the shortcut menu.
NOTE
To back up BTS files, select the btsswm folder and back up it.
Step 5 On the LMT PC, select a directory to save backup files. In the selected directory, right-click and
choose Paste from the shortcut menu.
Step 6 The Copying progress dialog box is displayed. When the copying is complete, the dialog box
will be closed.
----End
5.5.2 Backing Up the BSC/BTS Program Files (M2000)

This describes how to back up the BSC/BTS program files on the M2000. The backup of the
BSC/BTS program files on the M2000 consists of two procedures: transferring files from the
NE to the NM and transferring files from the NM to the M2000 client.
Prerequisite
l
Transferring files from the NE to the NM: There are corresponding files on the NE.
Transferring files from the NM to the client: There are corresponding files on the NM.
Backing up BSC program files
Context
Back up the BSC configuration data files from the BSC to the M2000 client.
l
Backing up BTS program files

Back up the BTS program files from the BTS to the M2000 client.
Procedure
l
5-6
Transferring files from the NE to the NM

1.
Choose Software > File Transfer Wizard. The Select General Parameters dialog
box is displayed.
2.
Set Direction to From NE To NM.
3.
In the NE Path area, select BSC6000, Data, and DataPackageFile, as shown in

Figure 5-1.

Issue 03 (2009-07-20)

Figure 5-1 Select General Parameters dialog box (from NE to NM)
NOTE
To back up BTS files, select a BTS under a BTS model.
4.
Click Finish.
In the Software Browser window, the backup progress information is displayed in
the Immediate Task list box.
Issue 03 (2009-07-20)
Transferring files from the NM to the client

1.
Choose Software > File Transfer Wizard. The Select General Parameters dialog
box is displayed.
2.
Set Direction to From NM To Client.
3.
In the Server Path area, select the data file of a backup item (Data, License, Path,
Version) under BSC6000, as shown in Figure 5-2.

5-7

Figure 5-2 Select General Parameters dialog box (from NM to Client)
NOTE
To back up BTS files, select a BTS under a BTS model.
4.
Click Next. The Select Client Directory dialog box is displayed.
5.
Click
6.
Click Finish.
. The Select dialog box is displayed. Select a save path.
In the Software Browser window, the backup progress information is displayed in

the FTP Task list box.
----End
5-8

Issue 03 (2009-07-20)

BSS Routine Maintenance Guide (V900R008C12 - 03)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSS Routine Maintenance Guide (V900R008C12 - 03)

Uploaded by

Copyright:

Available Formats

HUAWEI BSC6000 Base Station Controller