BSS Troubleshooting Guide (V900R008C01 - 01)

HUAWEI BSC6000 Base Station Subsystem
V900R008
BSS Troubleshooting Guide
Issue 01
Date 2008-06-10
INTERNAL
Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
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
Copyright © Huawei Technologies Co., Ltd. 2008. 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 the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in 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 Proprietary and Confidential

BSS Troubleshooting Guide Contents
Contents
About This Document.....................................................................................................................1

1 Introduction to BSS Troubleshooting....................................................................................1-1
1.1 Troubleshooting Process.................................................................................................................................1-2
1.2 Common Troubleshooting Methods................................................................................................................1-4
1.3 Huawei Technical Support..............................................................................................................................1-6
1.3.1 Obtaining Technical Support.................................................................................................................1-7
1.3.2 Information Collected for Troubleshooting...........................................................................................1-7
1.3.3 Fault Location Record Form..................................................................................................................1-8
2 Collecting Information for Locating BSS Faults..................................................................2-1

2.1 Collecting the Local Information....................................................................................................................2-3
2.2 Collecting BSC Configuration Data................................................................................................................2-4
2.3 Collecting M2000 Performance Measurement Information...........................................................................2-5
2.4 Collecting BSC Performance Measurement Information...............................................................................2-7
2.5 Collecting BSS Alarm Information.................................................................................................................2-7
2.5.1 Collecting BSS Alarm Log Files............................................................................................................2-7
2.5.2 Collecting BSS Alarm Information......................................................................................................2-10
2.6 Collecting BSS Log Information...................................................................................................................2-10
2.6.1 Collecting BSC Log Files....................................................................................................................2-10
2.6.2 Collecting BTS Log Files.....................................................................................................................2-12
2.6.3 Collecting LMT Log Files....................................................................................................................2-14
2.7 Collecting GBAM/GOMU Information........................................................................................................2-14
2.7.1 Collecting Information About the GBAM Model................................................................................2-14
2.7.2 Collecting Running Information About the GBAM/GOMU Local Processes....................................2-14
2.7.3 Collecting Running Information About the GBAM/GOMU Core Processes......................................2-15
2.7.4 Collecting Other Information About the GBAM/GOMU....................................................................2-16
2.8 Collecting Messages Traced on the BSC......................................................................................................2-17
2.9 Collecting TRACE Files of the M2000.........................................................................................................2-17
2.10 Collecting Channel Status Information.......................................................................................................2-18
2.11 Collecting Board Bar Code Information.....................................................................................................2-19
2.12 Collecting Voice Tuning Information.........................................................................................................2-20
2.13 Collecting External PCU Information.........................................................................................................2-21
2.13.1 Collecting PCUINFO Information.....................................................................................................2-21
Issue 01 (2008-06-10) Huawei Proprietary and Confidential i

Contents BSS Troubleshooting Guide
2.13.2 Collecting Messages Traced on the External PCU............................................................................2-24
3 Common Faults...........................................................................................................................3-1
3.1 Troubleshooting One-Way Audio or No Audio..............................................................................................3-2
3.2 Troubleshooting Noises...................................................................................................................................3-3
3.3 Troubleshooting Cross Connection Faults......................................................................................................3-5
4 Link Faults...................................................................................................................................4-1
4.1 Link Fault Symptoms......................................................................................................................................4-2
4.1.1 Impacts of Link Faults on Services........................................................................................................4-2
4.1.2 Alarms Related to Link Faults...............................................................................................................4-3
4.1.3 Counters Related to Link Faults.............................................................................................................4-9
4.2 Link Troubleshooting Methods.....................................................................................................................4-11
4.2.1 Troubleshooting OML Faults...............................................................................................................4-13
4.2.2 Troubleshooting EML Faults...............................................................................................................4-14
4.2.3 Troubleshooting RSL Faults................................................................................................................4-16
4.2.4 Troubleshooting ESL Faults.................................................................................................................4-17
4.2.5 Troubleshooting PBSL Faults..............................................................................................................4-18
4.2.6 Troubleshooting SS7 Signaling Link Faults........................................................................................4-23
4.2.7 Troubleshooting Ater Signaling Link Faults........................................................................................4-26
4.2.8 Troubleshooting Ater OML Faults.......................................................................................................4-27
4.2.9 Troubleshooting E1/T1 Transmission Faults.......................................................................................4-27
4.2.10 Troubleshooting Optical Transmission Faults...................................................................................4-28
4.2.11 Troubleshooting M3UA Link Faults..................................................................................................4-29
4.2.12 Troubleshooting M3UA Route Unavailability Faults........................................................................4-32
4.2.13 Troubleshooting M3UA Destination Entity Inaccessibility Faults....................................................4-33
4.2.14 Troubleshooting Abis Interface IP Link Faults..................................................................................4-36
4.3 Typical Cases of Troubleshooting Link Faults.............................................................................................4-37
4.3.1 Case: BTS TRX Faults.........................................................................................................................4-38
4.3.2 Case: BTS Faults..................................................................................................................................4-38
4.3.3 Case: BTS Loading Failure..................................................................................................................4-39
4.3.4 Case: Abis Transmission Faults...........................................................................................................4-39
4.3.5 Case: M3UA Link Faults.....................................................................................................................4-40
5 Clock Faults.................................................................................................................................5-1
5.1 Clock Fault Symptoms....................................................................................................................................5-2
5.1.1 Impacts of Clock Faults on Services......................................................................................................5-2
5.1.2 Alarms Related to Clock Faults.............................................................................................................5-2
5.1.3 Counters Related to Clock Faults...........................................................................................................5-5
5.2 Clock Troubleshooting Methods.....................................................................................................................5-5
5.2.1 Troubleshooting Clock Source Faults....................................................................................................5-5
5.2.2 Troubleshooting Board Clock Faults.....................................................................................................5-7
5.3 Typical Cases of Troubleshooting Clock Faults.............................................................................................5-7
5.3.1 Case: All BTS Clock Reference Sources Unavailable...........................................................................5-8
ii Huawei Proprietary and Confidential Issue 01 (2008-06-10)

BSS Troubleshooting Guide Contents
5.3.2 Case: Slip Frame Alarm.........................................................................................................................5-8

5.3.3 Case: Phase-Locked Loop in Non-Locked State....................................................................................5-9
5.3.4 Case: Handover Call Drop Due to Large Frequency Offset of BTS Clock.........................................5-11
6 Handover Faults.........................................................................................................................6-1
6.1 Handover Fault Symptoms..............................................................................................................................6-2
6.1.1 Impacts of Handover Faults on Services................................................................................................6-2
6.1.2 Alarms Related to Handover Faults.......................................................................................................6-2
6.1.3 Counters Related to Handover Faults.....................................................................................................6-2
6.2 Handover Troubleshooting Methods...............................................................................................................6-5
6.2.1 Troubleshooting No or Too Many Handovers Originated by the MS...................................................6-5
6.2.2 Troubleshooting Destination Cell Congestion Faults............................................................................6-6
6.2.3 Troubleshooting Hardware Faults..........................................................................................................6-6
6.2.4 Troubleshooting Inter-BSC or Inter-MSC Handover Failures...............................................................6-7
6.2.5 Troubleshooting Other Handover Faults................................................................................................6-8
7 Congestion Faults.......................................................................................................................7-1
7.1 Congestion Fault Symptoms...........................................................................................................................7-2
7.1.1 Impacts of Congestion Faults on Services.............................................................................................7-2
7.1.2 Alarms Related to Congestion Faults.....................................................................................................7-2
7.1.3 Counters Related to Congestion Faults..................................................................................................7-3
7.2 Congestion Troubleshooting Methods............................................................................................................7-4
7.2.1 Troubleshooting High Traffic................................................................................................................7-5
7.2.2 Troubleshooting Burst Traffic................................................................................................................7-6
7.2.3 Troubleshooting TRX Faults..................................................................................................................7-6
7.2.4 Troubleshooting Interference Problems.................................................................................................7-8
7.2.5 Troubleshooting Insufficient Terrestrial Resources...............................................................................7-9
7.2.6 Troubleshooting Insufficient Abis Resources........................................................................................7-9
7.3 Typical Cases of Troubleshooting Congestion Faults...................................................................................7-11
7.3.1 Case: TCH Congestion Due to TRX Faults.........................................................................................7-11
7.3.2 Case: SDCCH Congestion Due to LAC Configuration Faults............................................................7-11
8 Access Faults...............................................................................................................................8-1
8.1 Access Fault Symptoms..................................................................................................................................8-2
8.1.1 Impacts of Access Faults on Services....................................................................................................8-2
8.1.2 Alarms Related to Access Faults............................................................................................................8-2
8.1.3 Counters Related to Access Faults.........................................................................................................8-3
8.2 Access Troubleshooting Methods...................................................................................................................8-4
8.2.1 Troubleshooting Um Interface Quality Problems..................................................................................8-4
8.2.2 Troubleshooting Data Configuration Faults...........................................................................................8-7
8.3 Typical Cases of Troubleshooting Access Faults.........................................................................................8-11
8.3.1 Case: MS Access Failure Due to Weak Signals...................................................................................8-11
8.3.2 Case: MS Cell Reselection Failure Due to Weak Signals of Neighboring Cells.................................8-12
8.3.3 Case: MS Network Disconnection Due to Location Update Period Set Too Small............................8-12
Issue 01 (2008-06-10) Huawei Proprietary and Confidential iii

Contents BSS Troubleshooting Guide
8.3.4 Case: MS Network Disconnection Due to Incorrect CGI Configuration.............................................8-13

8.3.5 Case: MS Access Failure Due to Incorrect CBQ/CBA Setting...........................................................8-13
8.3.6 Case: MS Access Failure Due to Incorrect Setting of Minimum RACH Access Level......................8-14
9 PS Service Faults........................................................................................................................9-1
9.1 PS Service Fault Symptoms............................................................................................................................9-2
9.1.1 Impacts of PS Service Faults on Services..............................................................................................9-2
9.1.2 Alarms Related to PS Service Faults......................................................................................................9-2
9.1.3 Counters Related to PS Service Faults...................................................................................................9-4
9.2 PS Service Troubleshooting Methods...........................................................................................................9-12
9.2.1 Troubleshooting a Cell Not Supporting GPRS....................................................................................9-13
9.2.2 Troubleshooting Cell Faults (External PCU).......................................................................................9-14
9.2.3 Troubleshooting Cell Kickoff Failures (External PCU)......................................................................9-17
9.2.4 Troubleshooting PDCH Faults (External PCU)...................................................................................9-20
9.2.5 Troubleshooting LAPD Link Faults (External PCU)...........................................................................9-21
9.2.6 Troubleshooting Cell Activity State Faults (Built-in PCU).................................................................9-23
9.2.7 Troubleshooting Cell Service Disruption Faults (Built-in PCU).........................................................9-27
9.2.8 Troubleshooting Global Service Disruption Faults (Built-in PCU).....................................................9-28
9.2.9 Commands Executed on the PCU Maintenance Terminal...................................................................9-30
9.3 Typical Cases of Troubleshooting PS Service Faults...................................................................................9-31
9.3.1 Case: Intermittent LAPD Links............................................................................................................9-32
9.3.2 Case: Broken Links on the Gb Interface..............................................................................................9-32
9.3.3 Case: MS GPRS Failure.......................................................................................................................9-33
9.3.4 Case: Unstable GPRS Download Rate.................................................................................................9-33
10 Cell Broadcast Faults.............................................................................................................10-1

10.1 Cell Broadcast Fault Symptoms..................................................................................................................10-2
10.1.1 Impacts of Cell Broadcast Faults on Services....................................................................................10-2
10.1.2 Alarms Related to Cell Broadcast Service Faults..............................................................................10-2
10.1.3 Counters Related to Cell Broadcast Service Faults............................................................................10-2
10.2 Cell Broadcast Troubleshooting Methods...................................................................................................10-4
10.2.1 Troubleshooting Disconnection Between the BSC and the CBC......................................................10-5
10.2.2 Troubleshooting CBS Startup Failures..............................................................................................10-6
10.2.3 Troubleshooting a Failure to Submit Cell Broadcast Messages to the BSC......................................10-7
10.2.4 Troubleshooting Incorrect Cell Broadcast Parameter Settings..........................................................10-9
10.2.5 Troubleshooting Message Reception Failures Caused by the MS...................................................10-11
10.2.6 Troubleshooting Incorrect Parameter Setting of the Simple Cell Broadcast...................................10-12
10.3 Typical Cases of Troubleshooting Cell Broadcast Service Faults............................................................10-12
10.3.1 Case: CBT/OMT/MMT Login Failure.............................................................................................10-12
iv Huawei Proprietary and Confidential Issue 01 (2008-06-10)

BSS Troubleshooting Guide Figures
Figures
Figure 1-1 Troubleshooting process.....................................................................................................................1-2

Figure 2-1 Collecting BSC local information......................................................................................................2-4
Figure 2-2 Backing up server data.......................................................................................................................2-5
Figure 2-3 Query Result dialog box.....................................................................................................................2-6
Figure 2-4 New Query interface...........................................................................................................................2-6
Figure 2-5 Manage Alarm Log File window........................................................................................................2-8
Figure 2-6 Create Alarm Log File dialog box......................................................................................................2-9
Figure 2-7 Manage Alarm Log File window........................................................................................................2-9
Figure 2-8 Upload BSC Log Files window........................................................................................................2-11
Figure 2-9 Upload BSC Log Files window........................................................................................................2-11
Figure 2-10 BTS Work Log dialog box.............................................................................................................2-12
Figure 2-11 Get BTS Compressed Log dialog box............................................................................................2-13
Figure 2-12 Monitor Channel Status window....................................................................................................2-19
Figure 2-13 Query BSC Board Information dialog box.....................................................................................2-20
Figure 2-14 PCUINFO window.........................................................................................................................2-22
Figure 2-15 Information items that can be connected through the PCUInfo....................................................2-23
Figure 2-16 Obtaining the PCU information......................................................................................................2-23
Figure 2-17 Directory of the PCU Info..............................................................................................................2-24
Figure 2-18 Um interface tracing Setting dialog box.........................................................................................2-25
Figure 2-19 Pb interface tracing Setting dialog box...........................................................................................2-25
Figure 2-20 BSSGP cell information tracing Setting dialog box.......................................................................2-26
Figure 2-21 BSSGP signaling message tracing Setting dialog box...................................................................2-26
Figure 3-1 Cross connection.................................................................................................................................3-5
Figure 3-2 Both TX and RX ports being cross-connected...................................................................................3-7
Figure 3-3 Cross connection detection.................................................................................................................3-7
Figure 4-1 Cell attributes....................................................................................................................................4-17
Figure 4-2 Configure Board Attributes dialog box............................................................................................4-20
Figure 4-3 Checking the frame format...............................................................................................................4-20
Figure 4-4 BSC attributes...................................................................................................................................4-21
Figure 4-5 Checking the PCU............................................................................................................................4-22
Figure 4-6 Checking the OSP of the SS7 signaling link....................................................................................4-24
Figure 4-7 Checking the SS7 signaling link.......................................................................................................4-25
Figure 4-8 Modify M3UA Link dialog box.......................................................................................................4-31
Issue 01 (2008-06-10) Huawei Proprietary and Confidential v

Figures BSS Troubleshooting Guide
Figure 4-9 Modify M3UA Link dialog box (2)..................................................................................................4-32

Figure 4-10 Configure M3UA Entity dialog box...............................................................................................4-34
Figure 4-11 Configure M3UA Linkset dialog box.............................................................................................4-35
Figure 4-12 Configure M3UA Route dialog box...............................................................................................4-36
Figure 4-13 Router configuration.......................................................................................................................4-41
Figure 5-1 Query BSC Clock Reference State dialog box.................................................................................5-10
Figure 7-1 Site device panel.................................................................................................................................7-7
Figure 7-2 Setting Call Control Parameter dialog box.......................................................................................7-10
Figure 8-1 Check the kickoff status of the cell.....................................................................................................8-5
Figure 8-2 Configure TRX Attributes dialog box................................................................................................8-6
Figure 8-3 Configure Frequency Scan dialog box............................................................................................... 8-7
Figure 8-4 Set Cell Attributes dialog box............................................................................................................ 8-9
Figure 8-5 Parameters related to the cells in idle mode.....................................................................................8-10
Figure 8-6 Parameters related to the cell timer..................................................................................................8-10
Figure 8-7 Call Control dialog box....................................................................................................................8-15
Figure 9-1 Cell attributes....................................................................................................................................9-14
Figure 9-2 Site device panel...............................................................................................................................9-16
Figure 9-3 Channel attributes.............................................................................................................................9-17
Figure 9-4 GPRS cell kickoff procedure............................................................................................................9-18
Figure 9-5 Set Cell Attributes dialog box..........................................................................................................9-25
Figure 9-6 NS and BSSGP tab page...................................................................................................................9-34
Figure 10-1 Configuring BSC attributes............................................................................................................10-8
Figure 10-2 Selecting a message........................................................................................................................10-9
Figure 10-3 Broadcast scope............................................................................................................................10-10
Figure 10-4 Editing the message......................................................................................................................10-11
vi Huawei Proprietary and Confidential Issue 01 (2008-06-10)

BSS Troubleshooting Guide Tables
Tables
Table 1-1 BSS fault location information form....................................................................................................1-8

Table 3-1 Alarm analysis and processing.............................................................................................................3-3
Table 3-2 Alarm analysis and processing.............................................................................................................3-4
Table 3-3 Noise analysis and processing..............................................................................................................3-4
Table 3-4 Noise feature analysis and fault location..............................................................................................3-5
Table 4-1 Alarms related to the BTS interface link faults....................................................................................4-3
Table 4-2 Alarms related to the BSC interface link faults....................................................................................4-5
Table 4-3 Alarms related to the external PCU interface link faults.....................................................................4-7
Table 4-4 Counters related to link faults..............................................................................................................4-9
Table 4-5 Link troubleshooting methods............................................................................................................4-11
Table 5-1 Alarms related to BSC clock faults......................................................................................................5-2
Table 5-2 Alarms related to BTS clock faults......................................................................................................5-4
Table 5-3 Clock troubleshooting methods............................................................................................................5-5
Table 6-1 Counters related to handover faults......................................................................................................6-3
Table 6-2 Handover troubleshooting methods.....................................................................................................6-5
Table 7-1 Alarms related to BTS congestion faults.............................................................................................7-2
Table 7-2 Alarms related to BSC congestion faults.............................................................................................7-3
Table 7-3 Counters related to congestion faults...................................................................................................7-3
Table 7-4 Congestion troubleshooting methods...................................................................................................7-5
Table 8-1 Alarms related to access faults.............................................................................................................8-2
Table 8-2 Counters related to access faults..........................................................................................................8-3
Table 8-3 Access troubleshooting methods..........................................................................................................8-4
Table 9-1 Alarms related to PS service faults (external PCU).............................................................................9-2
Table 9-2 Alarms related to PS service faults (built-in PCU)..............................................................................9-3
Table 9-3 Counters related to PS service faults (external PCU)..........................................................................9-4
Table 9-4 Counters related to PS service faults (built-in PCU)...........................................................................9-6
Table 9-5 PS service troubleshooting methods..................................................................................................9-12
Table 9-6 Cell kickoff troubleshooting methods................................................................................................9-20
Table 9-7 Commands executed on the PCU maintenance terminal...................................................................9-30
Table 10-1 Alarms related to cell broadcast service faults.................................................................................10-2
Table 10-2 Counters related to cell broadcast service faults..............................................................................10-3
Table 10-3 Cell broadcast troubleshooting methods..........................................................................................10-4
Issue 01 (2008-06-10) Huawei Proprietary and Confidential vii

BSS Troubleshooting Guide About This Document
About This Document
Purpose
This document describes the methods of troubleshooting faults when the GBSS equipment is in
service. With this document, the maintenance personnel can solve the following problems:
l Complaints from subscribers
l Faults detected in regular maintenance
l Burst equipment faults
Product Version
The following table lists the product versions related to this document.
Product Name Model Product Version
BSC BSC6000 V900R008C01
BTS BTS3012 V300R004&V300R005&V300R006
BTS3012AE V300R005&V300R006
BTS3006C V300R005&V300R006
BTS3002E V300R005
BTS3036/BTS3900 V300R008
GSM
BTS3036A/BTS3900A V300R008
GSM
DBS3036/DBS3900 V300R008
GSM
Intended Audience
This document is intended for:
l System engineers
l Technical support engineers
l Maintenance engineers
Issue 01 (2008-06-10) Huawei Proprietary and Confidential 1

About This Document BSS Troubleshooting Guide
Change History
For changes in the document, refer to Changes in BSS Troubleshooting Guide.
Organization
1 Introduction to BSS Troubleshooting
This introduces the troubleshooting process and common means of fault location. If a fault cannot
be rectified, you can contact Huawei for technical support.
2 Collecting Information for Locating BSS Faults
When a fault occurs to the BSS, you need to collect the fault information as a reference for
troubleshooting. In addition, when you contact Huawei Customer Service Center, provide the
fault information for more efficient troubleshooting.
3 Common Faults
This describes the methods of troubleshooting common faults. Through these methods, you can
determine the class, subclass, or specific location of a fault.
4 Link Faults
This describes link faults in terms of the symptoms, troubleshooting methods, and typical cases.
5 Clock Faults
This describes clock faults in terms of the symptoms, troubleshooting methods, and typical cases.
6 Handover Faults
This describes handover faults in terms of the symptoms, troubleshooting methods, and typical
cases.
7 Congestion Faults
This describes congestion faults in terms of the symptoms, troubleshooting methods, and typical
cases.
8 Access Faults
This describes access faults in terms of the symptoms, troubleshooting methods, and typical
cases.
9 PS Service Faults
This describes PS service faults in terms of the symptoms, troubleshooting methods, and typical
cases.
10 Cell Broadcast Faults
This describes cell broadcast faults in terms of the symptoms, troubleshooting methods, and
typical cases.
Conventions
1. Symbol Conventions
The following symbols may be found in this document. They are defined as follows
2 Huawei Proprietary and Confidential Issue 01 (2008-06-10)

BSS Troubleshooting Guide About This Document
Symbol Description
Indicates a hazard with a high level of risk that, if not avoided,

will result in death or serious injury.
DANGER
Indicates a hazard with a medium or low level of risk which, if

not avoided, could result in minor or moderate injury.
WARNING
Indicates a potentially hazardous situation that, if not avoided,

could cause equipment damage, data loss, and performance
CAUTION degradation, or unexpected results.
TIP Indicates a tip that may help you solve a problem or save your
time.
NOTE Provides additional information to emphasize or supplement

important points of the main text.
2. General Conventions
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 Terminal display is in Courier New.
3. Command Conventions
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italic.
[] Items (keywords or arguments) in square brackets [ ] are optional.
{x | y | ...} Alternative items are grouped in braces and separated by vertical

bars.One is selected.
[ x | y | ... ] Optional alternative items are grouped in square brackets and

separated by vertical bars.One or none is selected.
{ x | y | ... } * Alternative items are grouped in braces and separated by vertical

bars.A minimum of one or a maximum of all can be selected.
Issue 01 (2008-06-10) Huawei Proprietary and Confidential 3

About This Document BSS Troubleshooting Guide
[ x | y | ... ] * Alternative items are grouped in braces and separated by vertical

bars.A minimum of zero or a maximum of all can be selected.
4. GUI Conventions
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 .
5. Keyboard Operation
Key Press the key.For example,press Enter and press Tab.
Key1+Key2 Press the keys concurrently.For example,pressing Ctrl+Alt+A

means the three keys should be pressed concurrently.
Key1,Key2 Press the keys in turn.For example,pressing Alt,A means the two
keys should be pressed in turn.
6. Mouse Operation
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.
4 Huawei Proprietary and Confidential Issue 01 (2008-06-10)

BSS Troubleshooting Guide 1 Introduction to BSS Troubleshooting
1 Introduction to BSS Troubleshooting
About This Chapter
This introduces the troubleshooting process and common means of fault location. If a fault cannot
be rectified, you can contact Huawei for technical support.
1.1 Troubleshooting Process

This introduces the troubleshooting process.
1.2 Common Troubleshooting Methods
Common troubleshooting methods include raw data analysis, alarm information analysis, LED
status analysis, dialing test, measurement, performance statistics, interface tracing, common test/
loopback test, comparison/interchange, and switchover/reset.
1.3 Huawei Technical Support
You can obtain Huawei technical support by contacting Huawei technical services center,
collecting information associated with a specific fault, or filling in the feedback form for
troubleshooting.
Issue 01 (2008-06-10) Huawei Proprietary and Confidential 1-1

1 Introduction to BSS Troubleshooting BSS Troubleshooting Guide
1.1 Troubleshooting Process

This introduces the troubleshooting process.
Figure 1-1 shows the troubleshooting process.
Figure 1-1 Troubleshooting process
Start
Collect fault
information
Determine the scope

and type of the fault
Find the causes

of the fault
Rectify the fault
Equipment
No Obtain Huawei
and services are Technical Support
restored?
Yes
End
Collecting Fault Information

Before troubleshooting, you need to collect the following information:
l Fault symptoms
l Fault occurrence time, site, and frequency
l Fault scope and impact
l Operational status of the equipment before the fault occurs
l Operations performed on the equipment before the fault occurs, and the consequence
l Alarms and associated alarms when the fault occurs
1-2 Huawei Proprietary and Confidential Issue 01 (2008-06-10)

l Status of the LEDs on involved boards

l Measures taken to deal with the fault, and the consequence
You can collect fault information in the following ways:

l Consult the person who reports the fault about the symptom, time, location, and frequency
of the fault.
l Ask the operator of the equipment about the daily running status, failure symptom,
operations performed before the fault occurs, and measures taken after the fault occurs and
the consequence.
l Observe board LEDs and the alarm management system on the LMT to obtain information
about the running status of software and hardware.
l Test the service, measure the performance data, or trace interfaces or signaling messages
to learn the scope of the fault and the impact of the fault on the system.
Determining the Scope and Type of the Fault

After collecting fault information, you need to analyze the fault symptom to determine the scope
and type of the fault.
The types of BSS faults are as follows:
l 3 Common Faults
l 4 Link Faults
l 5 Clock Faults
l 6 Handover Faults
l 7 Congestion Faults
l 8 Access Faults
l 9 PS Service Faults
l 10 Cell Broadcast Faults
NOTE
l Fault symptoms mentioned in this document are categorized into several classes. For each class, this
document provides a series of fault location methods, through which subclasses may be determined.
For each subclass, this document provides a series of operations, through which the specific fault causes
can be found.
l In addition, this document describes how to analyze and locate common faults, such as one-way audio,
no audio, and noise.
Finding the Causes of the Fault

By analyzing and comparing possible causes, find the specific causes of the fault.
Fault location is categorized into two types:
l Location of service-related faults
– For a one-way audio, no audio, noise, or PS service fault, check the Abis interface and
Um interface to determine whether the BSS system is faulty. If the BSS system is faulty,
continue to locate the fault.
– For a handover fault or an access fault, start signaling tracing and compare the signaling
flows with the protocols to locate the fault.

NOTE
For service-related faults, you can refer to 1.2 Common Troubleshooting Methods to locate the
fault.
l Location of faults related to the subsystems
There are many types of clock faults and link faults. The fault scope, however, is relatively
narrow. Such faults have simple causes. Fault-related information is presented through
board LEDs, alarms, and error prompts. Based on such information, you can rectify the
fault in most cases.
Rectifying the Fault

After locating the fault, you can start to rectify the fault and restore the system by taking proper
measures, such as checking the cables, replacing the faulty boards, modifying configuration data,
switching over a pair of active and standby parts, and resetting the boards.
When rectifying the fault, ensure that:
l Use different procedures for different faults.
l Check the system again after the troubleshooting to ensure that the fault is completely
rectified.
l To avoid the occurrence of similar faults, record the causes of the fault and take preventive
or corrective measures.
Checking the Equipment and Services

After rectifying the fault, check whether the system works properly by checking the status of
board LEDs and alarm LEDs, and perform dialing tests to ensure that the services are normal.
Contacting the Huawei Customer Service Center

Collect required fault information and contact the Huawei Customer Service Center. For details,
refer to 1.3.2 Information Collected for Troubleshooting.
1.2 Common Troubleshooting Methods

Common troubleshooting methods include raw data analysis, alarm information analysis, LED
status analysis, dialing test, measurement, performance statistics, interface tracing, common test/
loopback test, comparison/interchange, and switchover/reset.
Raw Data Analysis

Raw data refers to the information reported by the users and other offices, found during the
maintenance, and collected by the maintenance engineers in the initial period.
Raw data is used to locate and analyze a fault, especially to determine the impact scope and the
category of the fault. Raw data can help to narrow the fault scope and locate the fault in the
initial stage of troubleshooting. An experienced maintenance engineer can even locate the fault
simply based on raw data.
Raw data can help service troubleshooting and other types of troubleshooting, especially trunk
troubleshooting. The reason is that trunk troubleshooting requires the connection to the
transmission system and the cooperation with the signaling.

Alarm Information Analysis

Alarm information is provided by the BSS alarm system in the form of sound, light, LED, or
screen display. As a result, alarm information is of great help to analyze and locate a fault.
Alarm information includes the description of the fault or exception, fault causes, and handling
suggestions. Alarm information relates to many parts of the BSS, including hardware, link, trunk,
and CPU load. It is an important key to fault analysis and location.
Alarm information is used to locate the fault and finding out the causes. The BSS alarm system
provides a huge amount of alarm information, which can be used to locate faults directly or
together with other means.
LED Status Analysis

An LED reflects the working status of a board, a circuit, a link, an optical path, or a node. The
LED is an important key to fault analysis and location.
The LED status is used to quickly locate the fault and the causes of the fault. Because of limited
information, the LED status is often used together with alarm information.
Dialing Test
A dialing test is used to check the call processing function of the BSS and the relevant equipment.
It is a simple and quick way of troubleshooting.
Voice services take up a great part of all the services provided by the BSS. As a result, most
faults related to the BSS have great impacts on calls.
Dialing tests are often used in daily maintenance to determine whether the MS, BTS, BSC, and
trunk system work properly. Dialing tests are also used together with continuous and dynamic
tracing to test the BSS functions, such as call processing and calling number display.
Measurement
Measurement is a common technical means of BSS troubleshooting. It is widely used in power
supply testing, signaling analysis, waveform analysis, and bit error rate (BER) check. Through
instruments and meters, you can directly obtain fault-related data.
Performance Statistics
Performance statistics are a means of analyzing the call drop rate.
The call drop rate is an important counter of the BSS. It is affected by many factors and therefore
difficult to predict. Performance statistics can help to find call drop causes in time and prevent
call drops effectively
Interface Tracing
Interface tracing is used to analyze the causes of a failure in calling connection or signaling
cooperation between offices. Based on tracing results, you can directly locate the causes in most
cases.

Common Test and Loopback Test

A common test is used to obtain the technical parameters of transmit power, transport channels,
or trunk equipment that may be exceptional. Test tools include instruments, meters, and software
test tools. Based on test results, you can learn whether a device is faulty or about to be faulty.
A loopback test refers to such a test in which a transmitted signal is returned to the sending
device. Loopback is used to observe the functioning of a device or channel, the provisioning of
services, and the status of signaling flows. With the information, you can determine whether
hardware and software parameters are properly set. Loopback is commonly used to locate
transmission faults and trunk parameter errors. During the process of setting up a new site and
expanding the capacity of trunks, loopback of a BSS trunk can help to determine whether the
trunk and signaling link parameters are properly set.
Common tests and loopback tests are usually used together to locate transmission faults.
Comparison and Interchange

You can compare the symptoms of a faulty part with those of a good one to find out the causes.
Comparison is applicable when the fault occurs in a narrow scope.
You can replace the faulty part with a good one to compare the running status of the two parts
to determine the scope or location of the fault. Interchange is applicable when the fault occurs
in a wide scope.
Switchover and Reset

Switchover refers to switching all the services from the active device to the standby device. By
comparing the running status before and after the switchover, you can determine whether the
active device works properly or whether the active and standby devices cooperate properly.
Reset refers to manually resetting some or all of the devices. Reset is mainly used to rectify
software running faults.
Switchover and reset should be used only in emergency. The reasons are as follows:
l Compared with other methods, switchover and reset are auxiliary methods.
l After switchover or reset, the fault symptom seldom appears again within a short period.
As a result, the faults cannot be found, which brings potential security and stability risks
to the equipment.
l Usually, the reset operation disrupts the ongoing services and even brings the system down.
To avoid data loss, you need to back up the system data before switchover of main control boards.
For details, refer to BSS Backup and Recovery Guide.
1.3 Huawei Technical Support

You can obtain Huawei technical support by contacting Huawei technical services center,
collecting information associated with a specific fault, or filling in the feedback form for
troubleshooting.
1. Collect the information necessary for troubleshooting by referring to 1.3.2 Information

Collected for Troubleshooting.

2. Provide the feedback information to Huawei technical services center according to 1.3.3
Fault Location Record Form. For details, refer to 1.3.1 Obtaining Technical Support.
NOTE
If encountered a critical fault, you can first contact Huawei technical services center prior to collecting and
providing the information necessary for troubleshooting.
1.3.1 Obtaining Technical Support

This describes how to contact Huawei for technical support.
1.3.2 Information Collected for Troubleshooting
The information associated with the occurred fault should be collected before you contact
Huawei technical services center in order to facilitate the future troubleshooting.
1.3.3 Fault Location Record Form
After collecting the location information of the faults, you need to fill in the fault location
information form to help the technical services center locate and rectify the faults.
1.3.1 Obtaining Technical Support

This describes how to contact Huawei for technical support.
Procedure
l Dial the customer service number of Huawei: 4008302118 or (+86-755) 2856 0000.
l Fax a properly written feedback form to Huawei (0755-28560111) or the local office.
– For an emergent fault, fill in the BSS Emergency Maintenance Notice to provide
the feedback information.
– For a non-emergent fault, fill in the 1.3.3 Fault Location Record Form to provide
the feedback information.
l Send an E-mail to support@huawei.com.
l Visit the website http://support.huawei.com for help.
NOTE
For details on how to contact the local office, visit the support website.
----End
1.3.2 Information Collected for Troubleshooting

The information associated with the occurred fault should be collected before you contact
Huawei technical services center in order to facilitate the future troubleshooting.
Collecting General Fault Information

The general fault information to be collected is as follows:
l Full name of the office

l Name and phone number of the contact person
l Time when the fault occurs
l Detailed description of the fault symptoms
l Host software version of the equipment

l Measures taken after the fault occurs and the result

l Severity level of the fault and the time required for rectifying the fault
Collecting Fault Location Information

The fault location information to be collected is as follows:
l BSC configuration data
l M2000 performance measurement information
l BSC performance measurement information
l BSS alarm information
l BSS log information
l GBAM/GOMU information
l Messages traced on the BSC
l M2000 TRACE files
l Channel status information
l Board bar code information
l Voice tuning information
l External PCU information
For details on the collection of fault location information, refer to 2 Collecting Information for
Locating BSS Faults.
1.3.3 Fault Location Record Form

After collecting the location information of the faults, you need to fill in the fault location
information form to help the technical services center locate and rectify the faults.
Table 1-1 describes the fault location information form.
Table 1-1 BSS fault location information form
Please fill in the following blanks in detail:
Office Name Response Time Device Type
Complainer Telephone Host Software

Version
Complaint Warranty □Yes
Time Expired? □No
Fault location information collected:
Information gatherer: Date:
The following contents should be completed by the personnel from Huawei technical
services center.
Instructional Methods □Telephone-Based Instruction □Remote Maintenance □

Onsite Instruction

Handling result (attachment allowed):
Operator: Date:
Outstanding issue:

BSS Troubleshooting Guide 2 Collecting Information for Locating BSS Faults
2 Collecting Information for Locating BSS

Faults
About This Chapter
When a fault occurs to the BSS, you need to collect the fault information as a reference for
troubleshooting. In addition, when you contact Huawei Customer Service Center, provide the
fault information for more efficient troubleshooting.
2.1 Collecting the Local Information

This describes how to collect the information on the BSC side and BTS side on the BSC6000
Local Maintenance Terminal, including mirror of the realtime running of the server, performance
statistics, logs, and alarm logs, so that test personnel can analyze and locate faults.
2.2 Collecting BSC Configuration Data
This describes how to collect BSC configuration data for troubleshooting.
2.3 Collecting M2000 Performance Measurement Information
This describes how to collect M2000 performance measurement information for
troubleshooting.
2.4 Collecting BSC Performance Measurement Information
This describes how to collect BSC performance measurement information for troubleshooting.
2.5 Collecting BSS Alarm Information
This describes how to collect BSS alarm log files and relevant information for troubleshooting.
2.6 Collecting BSS Log Information
This describes how to collect the log information associated with the BSC, BTS, LMT for
troubleshooting. The information consists of the Operation Log, Debug Log, Running Log,
LastWord Log, CHR Log, BTS Log, and Frequency Scan Log.
2.7 Collecting GBAM/GOMU Information
This describes how to collect GBAM/GOMU information for troubleshooting.
2.8 Collecting Messages Traced on the BSC
This describes how to collect signaling messages and user message on the BSC for
troubleshooting.
2.9 Collecting TRACE Files of the M2000

2 Collecting Information for Locating BSS Faults BSS Troubleshooting Guide
This describes how to collect the TRACE files of the M2000 server and M2000 client for
troubleshooting.
2.10 Collecting Channel Status Information
This describes how to collect the channel status information for troubleshooting.
2.11 Collecting Board Bar Code Information
This describes how to collect bar code information of a BSC board for troubleshooting.
2.12 Collecting Voice Tuning Information
This describes how to collect voice tuning information based on the voice symptoms. The voice
problems involve noise, one-way audio (including no audio and voice discontinuity), and echo.
2.13 Collecting External PCU Information
When a fault occurs to the external PCU, you need to collect the fault information as a reference
for troubleshooting. In addition, when you contact Huawei Customer Service Center, provide
the fault information for more efficient troubleshooting.

2.1 Collecting the Local Information

This describes how to collect the information on the BSC side and BTS side on the BSC6000
Local Maintenance Terminal, including mirror of the realtime running of the server, performance
statistics, logs, and alarm logs, so that test personnel can analyze and locate faults.
Prerequisite
l The LMT runs normally.
l The communication between the LMT and the BSC is normal.
Context
If the local information is successfully collected, the local information is automatically saved to
the path: LMT installation path\BSC6000\BSC6000V900R008C01\BscObj\BSC Name
\LocaleInfo.
The local information is categorized into the following four types:
l Core Dump: mirror file of the realtime running of the server
l Pfm: performance statistics file
l Log: oprlog (operation log), dbglog (debugging log), runlog (running log), lstlog (lastword
log), chrlog (CHR log), btslog (BTS log), and frqlog (frequency scan log).
l Alarm: alarm log file
Procedure
Step 1 Choose BSC Maintenance > Maintain User Resource > Collect BSC Local Information.
Step 2 Click the Collect BSC Information tab. On the tab page, select Collect BSC local
information and set the BSC local information.
NOTE
You must select the Collect BSC local information so that you can collect and save the BSC local
information.
l Click the Collect BTS information tab. On the tab page, select the BTSs of which the
information needs to be collected.
l Click the Collect File tab. On the tab page, select the files of which the information needs
to be collected.
Step 3 Click Execute. The BSC local information is collected, as shown in Figure 2-1.

Figure 2-1 Collecting BSC local information
Step 4 Click Cancel. Collecting the BSC local information is complete.
----End
2.2 Collecting BSC Configuration Data

This describes how to collect BSC configuration data for troubleshooting.
Prerequisite
l The LMT runs properly.
l The BSC is functional.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, choose Configuration > Back Up > Back
Up Server Data on the menu. A dialog box is displayed, as shown in Figure 2-2.

Figure 2-2 Backing up server data
Step 2 Click Back up to local. Then, click the button in the File Path on Local area to specify the path
for saving the data.
Step 3 Click Execute. After the operation is complete, the message Uploading succeeded is displayed.
You can obtain the BSC configuration data file specified in Step 2.
----End
2.3 Collecting M2000 Performance Measurement

Information
This describes how to collect M2000 performance measurement information for
troubleshooting.
Prerequisite
l The M2000 runs properly.
l The communication between the M2000 and the BSC is proper.
Procedure
Step 1 On the M2000 Client, choose Performance > Query Result on the menu. A dialog box is
displayed, as shown in Figure 2-3.

Figure 2-3 Query Result dialog box
Step 2 Click New Query. A dialog box is displayed, as shown in Figure 2-4.
Figure 2-4 New Query interface
Step 3 In the left pane of the interface, click Object Type or Function Subset in the Organization
Style area, in the right pane of the interface, specify the object to be queried, the counters, and

period on the Object Settings, Counter Settings, and Other Settings tab pages separately.
Then, click Query.
Step 4 Click Save Template. The performance measurement result is saved in the form of .XLS.
----End
2.4 Collecting BSC Performance Measurement Information

This describes how to collect BSC performance measurement information for troubleshooting.
Prerequisite
l The communication between the LMT and the GBAM or the GOMU is proper.
l The communication between the Telnet client and the GBAM or the GOMU is proper.
Procedure
Step 1 Start the Telnet client, such as PuTTY Software, on the PC. Then, enter the IP address of the
GBAM and GOMU, and log in to the GBAM or GOMU as user root.
Step 2 Double-click the Internet Explorer icon and run the IP address (in the format of \
\XXX.XXX.XXX.XXX) of the GBAM to connect the GBAM server or the GOMU.
NOTE
If the Samba service is not started, run the rcsmb start command to start the service.
Step 3 Double-click the BSC6000 folder. Type User Name and Password, and then click Yes.
Step 4 Copy all the files under the BSC6000\data\mtndata\pfm directory to the local hard disk.
NOTE
If you are prompted to obtain specific rights in coping the files, run the chmod 777 /BSC6000 -R command
to change the read-and-write authority. After the files are copied, run the chmod 755 /BSC6000 -R
command to recover the read-and-write authority.
----End
2.5 Collecting BSS Alarm Information

This describes how to collect BSS alarm log files and relevant information for troubleshooting.
2.5.1 Collecting BSS Alarm Log Files

This describes how to collect BSS alarm log files and upload the log files to the LMT.
2.5.2 Collecting BSS Alarm Information
This describes how to collect BSS alarm information for troubleshooting.
2.5.1 Collecting BSS Alarm Log Files

This describes how to collect BSS alarm log files and upload the log files to the LMT.

Prerequisite
l The communication between the LMT and the alarm box is normal.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, choose Alarm Maintenance > Manage
Alarm Log File on the menu. A window is displayed, as shown in Figure 2-5.
Figure 2-5 Manage Alarm Log File window
Step 2 Click Create. A dialog box is displayed, as shown in Figure 2-6. Specify the period during
which the fault occurs, and then generate the log file.

Figure 2-6 Create Alarm Log File dialog box
Step 3 After the log file generation succeeds, if you click Query in Figure 2-5, all the alarm log files
that are generated and saved in the server are displayed, as shown in Figure 2-7.
Figure 2-7 Manage Alarm Log File window
Step 4 Select the alarm log file that you want to upload it to the LMT PC, and then click Upload. The
alarm log file is uploaded to the path BscObj\Office Name\Alm in the LMT installation
directory.
----End

2.5.2 Collecting BSS Alarm Information

This describes how to collect BSS alarm information for troubleshooting.
Prerequisite
l The communication between the LMT and the GBAM or the GOMU is proper.
l The communication between the Telnet client and the GBAM or the GOMU is proper.
Procedure
Step 1 Start the Telnet client, such as PuTTY Software, on the PC. Then, enter the IP address of the
GBAM and GOMU, and log in to the GBAM or GOMU as user root.
Step 2 Double-click the Internet Explorer icon and run the IP address (in the format of \
\XXX.XXX.XXX.XXX) of the GBAM to connect the GBAM server or the GOMU.
NOTE
If the Samba service is not started, run the rcsmb start command to start the service.
Step 3 Double-click the BSC6000 folder. Type User Name and Password, and then click Yes.
Step 4 Copy all the files under the BSC6000\data\datafile directory to the local hard disk.
NOTE
If you are prompted to obtain specific rights in coping the files, run the chmod 777 /BSC6000 -R command
to change the read-and-write authority. After the files are copied, run the chmod 755 /BSC6000 -R
command to recover the read-and-write authority.
----End
2.6 Collecting BSS Log Information

This describes how to collect the log information associated with the BSC, BTS, LMT for
troubleshooting. The information consists of the Operation Log, Debug Log, Running Log,
LastWord Log, CHR Log, BTS Log, and Frequency Scan Log.
2.6.1 Collecting BSC Log Files

This describes how to collect BSC log files for troubleshooting.
2.6.2 Collecting BTS Log Files
This describes how to collect BTS log files for troubleshooting.
2.6.3 Collecting LMT Log Files
This describes how to collect LMT log files for troubleshooting.
2.6.1 Collecting BSC Log Files

This describes how to collect BSC log files for troubleshooting.
Prerequisite

Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, choose BSC Maintenance > Maintain
Logs > Upload BSC Log Files on the menu. A window is displayed, as shown in Figure 2-8.
Figure 2-8 Upload BSC Log Files window
Step 2 Specify the Log Type and then click Query. The query result is shown in Figure 2-9.
Figure 2-9 Upload BSC Log Files window

Step 3 In the query result, select the log file to be uploaded and specify its upload path. Then, click
Upload to upload the log file to the path BscObj\Office Name\BscLog in the LMT installation
directory.
----End
2.6.2 Collecting BTS Log Files

This describes how to collect BTS log files for troubleshooting.
Prerequisite
l The communication between the BSC and the BTS is normal.
NOTE
The following steps are taken as examples for logging in to the server.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, choose BTS Maintenance > Maintain Site
> BTS Work Log. A dialog box is displayed, as shown in Figure 2-10.
Figure 2-10 BTS Work Log dialog box
The three options available in Figure 2-10 are described as follows:

l Get BTS logs to GBAM.
If this option is selected, the BTS log is saved in the directory IP address of the GBAM
\bsc6000\data\mtndata\log\dbg\btslog.
After the log is saved to the server, the log saved to the BTS is deleted automatically. You
can retrieve the BTS log files saved to the GBAM through the LMT. For the detailed
operations, refer to 2.6.1 Collecting BSC Log Files.
l Get BTS Compressed Log.
If this option is selected, the BTS log is compressed before it is saved to the path BscObj
\Office Name\CompressLog in the LMT installation directory.

l Browse BTS Log.

If this option is selected, the parameters such as site, board type, board No., start time, and
end time should be specified in order to have the specific log information displayed.
CAUTION
The BSC extracts BTS logs and saves them on the server. You can obtain these logs on the
server, and then these logs saved in the BTS are deleted. When other two methods are used to
obtain logs, the logs saved in the BTS still exist.
Step 2 Click Get BTS Compressed Log, and then click OK. A dialog box is displayed, as shown in
Figure 2-11.
Figure 2-11 Get BTS Compressed Log dialog box
Step 3 In Figure 2-11, specify the parameters such as Site Name, Start Time, and End Time. Then,
click Start. If the progress bars in the Progress area show that the operation is complete, a
message is displayed, prompting you that the log extraction succeeds. The default directory on
the LMT for saving the compressed BTS log, BscObj\Office Name\CompressLog, is
displayed.
NOTE
You can use a log interpretation tool to view the log file.
----End

2.6.3 Collecting LMT Log Files

This describes how to collect LMT log files for troubleshooting.
Prerequisite
Procedure
You can get the LMT log files from the LMT installation directory \BscObj\Office Name
\LmtLog.
----End
2.7 Collecting GBAM/GOMU Information

This describes how to collect GBAM/GOMU information for troubleshooting.
2.7.1 Collecting Information About the GBAM Model

This describes how to collect the information about the GBAM model from its label.
2.7.2 Collecting Running Information About the GBAM/GOMU Local Processes
This describes how to collect the running information about the GBAM/GOMU local processes
for troubleshooting.
2.7.3 Collecting Running Information About the GBAM/GOMU Core Processes
This describes how to collect the running information about the GBAM/GOMU core processes
2.7.4 Collecting Other Information About the GBAM/GOMU
This describes how to collect other information about the GBAM/GOMU for troubleshooting.
2.7.1 Collecting Information About the GBAM Model

This describes how to collect the information about the GBAM model from its label.
Procedure
Search for the white label attached to the GBAM shell. The literature following HUAWEI, such
as C5201 SERVER, is the GBAM model.
----End
2.7.2 Collecting Running Information About the GBAM/GOMU

Local Processes
This describes how to collect the running information about the GBAM/GOMU local processes

Context
CAUTION
If the operations described below are performed, the local processes of the GBAM/GOMU will
be restarted. Thus, you are not advised to perform these operations except that the local processes
of the GBAM/GOMU are faulty and need to be restarted.
Procedure
Step 1 Start the Telnet client, such as PuTTY Software, on the PC. Enter the IP address of the GBAM/
GOMU, and then log in to the GBAM/GOMU as the root user.
Step 2 Run the cd /BSC6000/coredump command to visit the directory that saves the error information
associated with the GBAM/GOMU.
Step 3 Run the pkill -8 pomu_local.bin command to generate the omulocal.0000.core.1.gz file.
Here, 0000 indicates the subrack number and slot number of the GOMU, and 1 indicates the
count of the recorded abnormal information. This file is large is size (it may be 2 GB); thus, its
generation might take several minutes. You can run the ll command to query the file size. If the
file size becomes stable, you can infer that the file is successfully generated. Perform the
operations in Step 4 to compress the file.
Step 4 Run the gzip omulocal.0000.core.1.gz command to generate the compressed file, say, omulocal.
0000.local.1.gz.
This file is generally several decades of MB in size. You can copy the file from the path IP
address of the GBAM/GOMU\bsc6000\coredump.
----End
2.7.3 Collecting Running Information About the GBAM/GOMU

Core Processes
This describes how to collect the running information about the GBAM/GOMU core processes
Context
CAUTION
If the operations described below are performed, the core processes of the GBAM/GOMU will
be restarted. Thus, you are not advised to perform these operations except that the core processes
of the GBAM/GOMU are faulty and need to be restarted.

Procedure
Step 1 Start the Telnet client, such as PuTTY Software, on the PC. Enter the IP address of the GBAM/
GOMU, and then log in to the GBAM/GOMU as the root user.
Step 2 Run the cd /BSC6000/coredump command to visit the directory that saves the error information
associated with the GBAM/GOMU.
Step 3 Run the pkill -8 pomu_core.bin command to generate the omucore.0000.core.1.gz file.
Here, 0000 indicates the subrack number and slot number of the GOMU, and 1 indicates the
count of the recorded abnormal information. This file is large is size (it may be 2 GB); thus, its
generation might take several minutes. You can run the ll command to query the file size. If the
file size becomes stable, you can infer that the file is successfully generated. Perform the
operations in Step 4 to compress the file.
Step 4 Run the gzip omucore.0000.core.1.gz command to generate the compressed file, say, omucore.
0000.core.1.gz.
This file is generally several decades of MB in size. You can copy the file from the path IP
address of the GBAM/GOMU\bsc6000\coredump.
----End
2.7.4 Collecting Other Information About the GBAM/GOMU

This describes how to collect other information about the GBAM/GOMU for troubleshooting.
Context
NOTE
You can get other information about the GBAM/GOMU from the shared directory of the GBAM/GOMU.
Procedure
l To get the history operation information about the user, do as follows:
1. Start the Telnet client, such as PuTTY Software, on the PC. Enter the IP address of
the GBAM/GOMU, and then log in to the GBAM/GOMU as the root user.
2. Run the cp .bash_history /BSC6000/install command to copy the .bash_history file
to the shared directory of the GBAM/GOMU.
3. Visit the .bash_history file in the directory IP address of the GBAM/GOMU/users/
bsc6000/install to get the history operation information about the user.
l To get the information about the abnormal restart of the GBAM/GOMU, do as follows:
2. Visit the core.********* file in the directory IP address of the GBAM/GOMU/
bsc6000/bscswm/omuroot to get the information about the abnormal restart of the
GBAM/GOMU.
NOTE
This file is generated automatically by the system when the OMU process is restarted
abnormally.
l To get the login information about the shared directory of the GBAM/GOMU, do as
follows:

2. Run the cd /var/log/samba command to enter the /var/log/samba directory.
3. Run the cp log.smbd /BSC6000 command to copy the log.smbd file to the shared
directory of the GBAM/GOMU.
4. Visit the log.smbd file in the directory IP address of the GBAM/GOMU/users/
bsc6000 to get the login information about the shared directory of the GBAM/GOMU.
l To get the information about the Ethernet cards of the GBAM/GOMU, do as follows:
2. Run the lspci | grep Ethernet command. After the result is displayed, capture it using
a relevant application, and save it for future use.
----End
2.8 Collecting Messages Traced on the BSC

This describes how to collect signaling messages and user message on the BSC for
troubleshooting.
Prerequisite
l The communication between the BSC and the MSC is normal.
Context
Two types of messages are available for tracing: signaling messages and user messages.
l Signaling messages
– The interface-related signaling messages involve those traced on the A interface, Abis
interface, Um interface, BSC_CBC interface, Pb interface for the external PCU, and Gb
interface for the built-in PCU.
– The link-related messages involve those traced on the BSSAP, SCCP, MTP2, MTP3,
SCTP, M3UA, RSL, OML, ESL, EML, and LAPD.
l User messages
The user messages are concerned with the continuity procedures and status of the user.
Procedure
For the detailed operations, refer to Configuring Message Tracing.
----End
2.9 Collecting TRACE Files of the M2000

This describes how to collect the TRACE files of the M2000 server and M2000 client for
troubleshooting.

Procedure
l Collect the TRACE file of the M2000 server.
1. Visit the directory IP address of the M2000 server/export/home/omc/var/logs
through FTP.
2. Find the TRACE file of the M2000, iMAP.XXXX.trace, in the previous directory.
The history TRACE files are saved in the tracebak folder of the same directory. Here,
XXXX indicates the name of an M2000 process.
NOTE
A history trace file is named as follows: iMAP.XXXX.trace.20061123155759.tar.gz. Here,

20061123155759 indicates the time when the file is generated.
CAUTION
To obtain an interpretable TRACE file through FTP, set the FTP download mode to
binary.
l Collect the TRACE file of the M2000 client.
You can get the TRACE file of the M2000 client from the installation directory of the
M2000 client, \client\tracefile.
NOTE
A TRACE file of the M2000 client is named as follows: DebugTrace_2007-06-12_14-24-44.txt.

Here, 14-24-44 indicates the time when the file is generated.
----End
2.10 Collecting Channel Status Information

This describes how to collect the channel status information for troubleshooting.
Prerequisite
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, choose BTS Maintenance > Monitor
Channel Status on the menu.
Step 2 In the displayed window, specify the Site, Cell, and TRX in the Operation Object. Then, click
Start. The channel status information is displayed, as shown in Figure 2-12.

Figure 2-12 Monitor Channel Status window
Step 3 Use a relevant application to capture the result, and save it for future use.
----End
2.11 Collecting Board Bar Code Information

This describes how to collect bar code information of a BSC board for troubleshooting.
Prerequisite
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, choose BSC Maintenance > Maintain
Device > Query BSC Board Information on the menu. A dialog box is displayed, as shown
in Figure 2-13.

Figure 2-13 Query BSC Board Information dialog box
Step 2 In the Board Location area, specify the Subrack No., Board Type, and Slot No. of a board.
Then, on the Board Information tab page, click Query to get the bar code information about
the board.
Step 3 Use a relevant application to capture the result, and save it for future use.
----End
2.12 Collecting Voice Tuning Information

This describes how to collect voice tuning information based on the voice symptoms. The voice
problems involve noise, one-way audio (including no audio and voice discontinuity), and echo.
Procedure
l During the tuning phase, collect the information associated with noise and one-way audio
(including no audio and voice continuity) problems as follows:
– Check the number of noise occurrences during a call and the characteristics of the noise,
such as the clicking sound and the metal sound.
– Check whether the noise occurs regularly, say, every x seconds or every x minutes. If
the noise does not occur regularly, check whether the noise persists during the call.

– Check whether the amplitude of the noise is even, such as the volume fluctuation.
– Approximate the ratio of the noise amplitude to the normal voice strength.
– Check whether the noise is sharp than the voice.
– Check whether the symptom such as one-way audio, no audio, or voice discontinuity
occurs during the conversation. One-way audio means that only one party can hear the
voice from the other end of the line. No audio means both parties fail to hear the voice
from the peer. Voice discontinuity means that the voice is interrupted irregularly during
the conversation.
– The occurrences of the one-way audio are of the following types:
The one-way audio symptom occurs after the call is put through and persists during the
conversation (excluding the long call put-through failure). The one-way audio symptom
occurs after a period of normal conversation, and persists until the call is hanged up.
The one-way audio symptom also occurs after a period of normal conversation, and
then disappears.
l During the tuning phase, collect the information associated with the echo problem as
follows:
– Test place and BTS type
– Models and MSISDNs of the MSs that hear the echoes from the peer end
– Local echo volume (compared with the peer voice volume)
– Space condition of the peer MS (whether the MS is in a spacious place, near a wall, or
in a narrow room)
– Ambient environment of the peer MS (noisy or quiet)
– Peer volume fluctuation and the fluctuation of the echo heard by the local party
– Fluctuation of the echo heard by the local party once the speaker at the peer is blocked
– Fluctuation of the echo heard by the local party once the peer party is under an inter-
BTS handover
– Fluctuation of the echo heard by the local party once the peer party is under an inter-
BSC handover
– Whether the echo persists even through the peer party walks out of the room or its
ambient voice volume changes
----End
2.13 Collecting External PCU Information

When a fault occurs to the external PCU, you need to collect the fault information as a reference
for troubleshooting. In addition, when you contact Huawei Customer Service Center, provide
the fault information for more efficient troubleshooting.
2.13.1 Collecting PCUINFO Information

This describes how to collect PCU system information and PCU resource information.
2.13.2 Collecting Messages Traced on the External PCU
This describes how to collect the signaling messages on the Um, Pb, and Gb interfaces.
2.13.1 Collecting PCUINFO Information

This describes how to collect PCU system information and PCU resource information.

Prerequisite
l The PCUInfo application is running.
l The Telnet terminal is started.
l The FTP terminal is started.
Procedure
Step 1 Double-click PCUInfo.exe.
Step 2 On the PCUInfo, choose Capture > Capture on the menu. Figure 2-14 shows the PCUINFO
window.
Figure 2-14 PCUINFO window
Step 3 Set the parameters on the PCUInfo.

1. Enter the IP address of the PCU in the POMU IP ADDR text box.
2. In the PCU System Info and PCU Res Info areas, click the check boxes of the items to be
collected.

Figure 2-15 Information items that can be connected through the PCUInfo
3. In the Alarm and DbgAlm text boxes, set the start date and end date, as shown in Figure
2-15.
NOTE
l The information in the PCU System Info and PCU Res Info areas is obtained through Telnet.
l The information in the FTP Files Setting area is obtained from the PCU hard disk through FTP.
Step 4 Click Start to obtain information.

l If the PCUInfo is connected to the PCU, a dialog box is displayed, as shown in Figure
2-16. This indicates that the PCUInfo can obtain the required information.
l If the PCUInfo fails to be connected to the PCU. Check whether the network connection is
proper and whether the IP address of the PCU is correct.
Figure 2-16 Obtaining the PCU information
Step 5 After obtaining the PCU information, click OK to save the PCU information to the sub-folder
in the PCU Info folder. The PCU information is named in the Info+the current date format, as
shown in Figure 2-17.

Figure 2-17 Directory of the PCU Info
Step 6 Click Exit.
----End
2.13.2 Collecting Messages Traced on the External PCU

This describes how to collect the signaling messages on the Um, Pb, and Gb interfaces.
Prerequisite
l The PCU LocalWS is started.
l The communication between the PCU LocalWS and the PCU is proper.
l The communication between the Telnet terminal and the PCU is proper.
Context
The signaling tracing of the PCU is performed on the PCU LocalWS. The interfaces consist of
the Um interface, Pb interface, and Gb interface.
Procedure
l Trace messages on the Um interface.
1. Start the PCU LocalWS. In the Maintenance window, choose Tracing > Um
Interface Tracing on the menu. A dialog box is displayed, as shown in Figure
2-18.

CAUTION
When tracing messages on the Um interface, you must clear the option Filter data
block.
Figure 2-18 Um interface tracing Setting dialog box
2. Set the parameters. Create a task to trace the Um interface messages of the test cell.
NOTE
You can query the Cell No. and TRX No. by running the command mt pdch show attr
LCNo all in the Telnet terminal.
l Trace messages on the Pb interface.
1. Start the PCU LocalWS. In the Maintenance window, choose Tracing > Pb
Interface Tracing on the menu. A dialog box is displayed, as shown in Figure
2-19.
CAUTION
When tracing the messages on the Pb interface, click all the check boxes.
Figure 2-19 Pb interface tracing Setting dialog box
2. Set the parameters. Create a task to trace the Pb interface messages of the test cell.

NOTE
The Cell No. must be the same as that specified in the Um interface tracing.
l Trace the Gb interface (BSSGP CELL) signaling messages.
1. Start the PCU LocalWS. In the Maintenance window, choose Tracing > BSSGP
Cell Message Tracing on the menu. A dialog box is displayed, as shown in Figure
2-20.
Figure 2-20 BSSGP cell information tracing Setting dialog box
2. Specify the Cell ID. Create a task to trace on the Gb interface the BSSGP cell
information messages of the test cell.
NOTE
You can query the Cell ID by running the command pcu show lcc LCNo in the Telnet terminal.
l Trace the Gb interface (BSSGP SIG) messages.
1. Start the PCU LocalWS. In the Maintenance window, choose Tracing > BSSGP
Signaling Message Tracing on the menu. A dialog box is displayed, as shown in
Figure 2-21.
Figure 2-21 BSSGP signaling message tracing Setting dialog box
2. Specify the NSEI. Create a task to trace on the Gb interface the BSSGP messages of
the test cell.
NOTE
You can query the NSEI by running the command Cell show CellID in the Telnet terminal.
l Save signaling messages.
1. After creating the tracing tasks on the Um, Pb, and Gb interfaces, save the messages
traced on the interfaces.
2. You should trace the signaling on the three interfaces simultaneously. After the test,
save the signaling tracing messages as a .gmt file. If the .gmt file is too large, you
should compress it into a .rar file.
----End

BSS Troubleshooting Guide 3 Common Faults
3 Common Faults
About This Chapter
This describes the methods of troubleshooting common faults. Through these methods, you can
determine the class, subclass, or specific location of a fault.
3.1 Troubleshooting One-Way Audio or No Audio

This describes how to troubleshoot one-way audio or no audio. One-way audio means that only
one party in a call can hear the voice. No audio means that no party in a call can hear the voice.
Generally, one-way audio or no audio occurs when a speech channel segment is faulty. The fault
can be rectified on the BSC6000 Local Maintenance Terminal.
3.2 Troubleshooting Noises
This describes how to troubleshoot noises, such as the bubble sound, clicking sound, and metal
sound, that appear during a call. In some cases, noises are so serious that the voices cannot be
heard clearly. Noises are usually caused by error bits.
3.3 Troubleshooting Cross Connection Faults
This describes how to troubleshoot the faults in cross connection. The fault symptoms show that
the E1/T1 wires at one end are mismatched with the TX/RX ports, thus disconnecting the upper-
level links.

3 Common Faults BSS Troubleshooting Guide
3.1 Troubleshooting One-Way Audio or No Audio

This describes how to troubleshoot one-way audio or no audio. One-way audio means that only
one party in a call can hear the voice. No audio means that no party in a call can hear the voice.
Generally, one-way audio or no audio occurs when a speech channel segment is faulty. The fault
can be rectified on the BSC6000 Local Maintenance Terminal.
Possible Causes
The possible causes of one-way audio or no audio are as follows:
l Engineering connection problem

– E1/T1 lines carried by the GEIUT are connected improperly. For example, they are
cross connected.
– E1/T1 lines on the A interface are connected improperly. For example, they are cross
connected.
l Data configuration problem
– Circuit configuration on the BSC side is inconsistent with that on the MSC side.
– On the BSC side, timeslots for carrying signaling are configured as ones for carrying
services.
l Hardware fault
A board, backplane, transmission line, or connector through which voice signals pass is
faulty.
l Radio link interference
Radio link interference is mainly caused by the radio environment. For example,
unbalanced UL and DL levels may lead to poor quality in one way or interference in the
uplink and the downlink.
l Clock fault
A clock fault usually occurs in a clock source.
l MS fault
An MS fault usually lies in the MS itself.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, perform a remote loopback on the speech
channel during a call. Here, set MSISDN to the called number and Loop Location to GE(O)
IUA. For detailed operations, refer to Looping Back Remote Speech Channel.
l If the Loop Direction is To BTS, you can infer that the speech channel on the BSC side is
operational if you (the calling party) can hear your own voice through the MS.
l If the Loop Direction is To MSC, you can infer that the speech channel on the MSC side
is operational if you (the calling party) can hear your own voice through the MS.
l If the fault occurs on the BSC side, go to Step 2; otherwise, go to Step 3 and Step 4.
Step 2 During a call, test the internal speech channel on the BSC6000 Local Maintenance
Terminal to check whether the TDM switching on the GTNU is normal. For detailed operations,
refer to Testing the Internal Speech Channel.

l If normal, go to Step 3.
l If abnormal, contact the Huawei Customer Service Center by referring to 1.3.1 Obtaining
Technical Support.
Step 3 During a call, check the speech channel resources on the BSC6000 Local Maintenance
Terminal by referring to Querying the Resources of An MS. The resources include the boards,
ports, and timeslots that carry the Abis, Ater, TC, and ACIC resources.
Step 4 Based on the ACIC information obtained in Step 3, check whether the configuration of the ACIC
port on the BSC side is consistent with that on the MSC side and whether the physical connection
is consistent with the configuration.
Step 5 Based on the Ater resource information obtained in Step 3, check whether there are cross
connections on the Ater interface and whether the physical connection is consistent with the
configuration.
Step 6 Based on the Ater resource information obtained in Step 3, check whether the Ater timeslots for
the speech channel are used for other purposes.
Step 7 Check whether an alarm about the speech channel is reported. If such an alarm is reported,
perform the corresponding processing by referring to Table 3-1.
Table 3-1 Alarm analysis and processing
System Alarm Type Analysis Processing
Link alarm Possibly caused by a link 4 Link Faults

fault
Interference alarm Possibly caused by radio 7.2.4 Troubleshooting

link interference, which Interference Problems
increases the bit error rate
on the radio link
Clock alarm Caused by frame slipping or 5 Clock Faults

frame loss
Step 8 If the fault persists, contact the Huawei Customer Service Center by referring to 1.3.1 Obtaining
Technical Support.
----End
3.2 Troubleshooting Noises

This describes how to troubleshoot noises, such as the bubble sound, clicking sound, and metal
sound, that appear during a call. In some cases, noises are so serious that the voices cannot be
heard clearly. Noises are usually caused by error bits.
Possible Causes
The possible causes of bit errors that lead to noises are as follows:
l Fault in a board, connector, or line through which voice signals pass

l Grounding fault
l Radio link interference
l Clock fault
l Mismatching between the settings of DIP switch on the DTMU of the BTS and the actual
type (75 ohms or 120 ohms) of the transmission cable
Procedure
Step 1 If an alarm is reported, perform the corresponding analysis and processing by referring to Table
3-2.
Table 3-2 Alarm analysis and processing

System Alarm Type Analysis Fault Rectification
Link alarm Possibly caused by radio link l 4 Link Faults

interference, which increases l 7.2.4 Troubleshooting
the bit error rate on the radio Interference Problems
link
Clock alarm Caused by frame slipping or 5 Clock Faults

frame loss
If no such an alarm is reported, go to Step 2.

Step 2 Perform the corresponding noise analysis and processing by referring to Table 3-3.
Table 3-3 Noise analysis and processing

Noise Location Analysis Fault Rectification
Only within the coverage of a Make test calls by using the l For a frequency problem,
BTS MS to determine the specific check the status of the
location, such as a timeslot, a TRX.
frequency, or the entire l For a BTS problem,
coverage of the BTS. check the transmission
lines within the BTS.
Within the coverage of the - Check the transmission

BSC lines within the BSC.
Within the coverage of the - Check the transmission

MSC lines within the MSC.
Step 3 If the alarm persists, perform the corresponding analysis and locate the fault by referring to
Table 3-4.

Table 3-4 Noise feature analysis and fault location

Noise Feature Analysis Location
Noises and voices are Error bits on the Error bits exist on the MSC
transmitted at the same time transmission lines affect the side.
in superimposition-like sample values of PCM.
format. Between them, noises
are not fluctuated greatly.
Some words cannot be heard Compressed voice signals Error bits exist within the
clearly. There are some must be decompressed BSC. Rectify the fault based
abnormal sounds such as the before being sent to the on the specific symptom and
bubble sound, clicking sound, receiver. The the corresponding rectification
and metal sound. decompression leads to method.
greatly fluctuated noises.
Noises occur at regular Frame slipping or frame 5 Clock Faults

intervals during a call. loss due to a clock fault
occurs at regular intervals,
such as every several
seconds.
Step 4 Check whether the settings of the DIP switch on the DTMU of the BTS are consistent with the
type (75 ohms or 120 ohms) of the transmission cable.
Technical Support.
----End
3.3 Troubleshooting Cross Connection Faults

This describes how to troubleshoot the faults in cross connection. The fault symptoms show that
the E1/T1 wires at one end are mismatched with the TX/RX ports, thus disconnecting the upper-
level links.
Fault Symptoms
In cross connection, the E1/T1 port can receive signals from the physical layer and no alarm is
generated, but the signals are sent by a wrong E1/T1 port at the peer end. Therefore, the upper-
level links are broken. Figure 3-1 shows the cross connection.
Figure 3-1 Cross connection

RX Port TX Port RX Port TX Port
E1/T1 A E1/T1 A E1/T1 A E1/T1 A
TX Port RX Port TX Port RX Port
TX Port RX Port TX Port RX Port

E1/T1 B E1/T1 B E1/T1 B E1/T1 B
RX Port TX Port RX Port TX Port
Correct connection
Cross connection

Detection Methods
There are two methods to detect cross connection faults, namely, loopback detection and alarm-
based detection.
l Loopback detection
Perform loopback on the remote E1/T1 port, and then check the data consistency between
the TX port and the RX port that are connected by the E1/T1 cables.
– If the data is consistent between the TX port and the RX port, the E1/T1 cables are
connected correctly.
– If the data is inconsistent between the TX port and the RX port, the E1/T1 cables are
cross-connected.
The loopback detection is of two types, remote loopback and physical loopback.
– Remote loopback applies when the GMPS/GEPS is directly connected to the GTCS
through the E1/T1 cables. In this scenario, you can run MML commands to perform
remote loopback on the remote E1/T1 ports.
– Physical loopback applies when the devices are connected through the DDF. In this
scenario, you can short-circuit the RX/TX ports on the DDF for the E1/T1 cables by
using conversion connectors to form a self-loop.
CAUTION
Physical loopback detection is applied to only the ports that carry the Ater OM links.
The loopback detection is performed during site deployment or upgrade. The advantage of
loopback detection is that ports can be detected in batches and faults in cross connections
can be located effectively. The disadvantage of loopback detection is that physical or remote
loopback must be performed on the DDF or remote E1/T1 port.
l Alarm-based detection
Disable the transmit function of the local E1/T1 port to enable the remote port to generate
the alarm 20081 Loss of E1/T1 Signals (LOS), and then add the Remote Alarm Indication
(RAI) to the alarm.
– If the E1/T1 cables are connected correctly, the local E1/T1 port can receive the RAI.
– If the E1/T1 cables are connected incorrectly, the local E1/T1 port does not generate
any alarm.
The alarm-based detection is used to locate the fault when one-way audio occurs during
site maintenance, or when loopback cannot be performed during site deployment. The
advantage of alarm-based detection is that loopback is not performed on the remote E1/T1
ports. The disadvantage of alarm-based detection is that you can only check whether the
E1/T1 cables are connected correctly but cannot acquire port information or detect the ports
in batches.
Restrictions
The restrictions of cross connection are as follows:
l Only the E1/T1 ports on the EIUa can be detected, but the optical ports on the OIUa cannot
be detected.

l Only whether cross connection exists can be detected, but the fact that both TX and RX
ports are cross-connected, as shown in Figure 3-2, cannot be detected.
Figure 3-2 Both TX and RX ports being cross-connected

RX Port TX Port
E1/T1 A E1/T1 A
TX Port RX Port
RX Port TX Port
E1/T1 B E1/T1 B
TX Port RX Port
l If the E1/T1 cables are wrongly connected and the RX and TX ports on the DDF form a
self-loop, the loopback detection cannot find out whether cross connection exists.
l If the boards are in active/standby mode, the cross connection detection can be performed
only on the active board instead of the standby board.
l When the E1/T1 interface board works in active/standby mode, the alarm-based detection
requires the Y-shaped E1/T1 cables.
l The local E1/T1 ports to be detected have no alarms generated.
l No loopback is performed on the local E1/T1 ports to be detected.
l If the loopback detection is used, it must be performed on the remote E1/T1 port.
l If the alarm-based detection is used, you must ensure that no loopback is performed on the
remote E1/T1 port.
l The loopback detection supports the single-port test and board test, whereas the alarm-
based detection supports only the single-port test. Neither detection can be used to
simultaneously test multiple ports on a board or simultaneously test multiple boards.
Procedure
For details of how to perform loopback detection and alarm-based detection, refer to Check E1/
T1 Cross Connection(CHK E1T1CRS). Figure 3-3 shows the interface.
Figure 3-3 Cross connection detection

CAUTION
l Cross connection detection may disrupt the service temporarily. It is recommended that you
test cross connection during site deployment or upgrade.
l You cannot run the commands for testing cross connection repeatedly. Instead, you must run
another command after the previous test is completed.
----End

BSS Troubleshooting Guide 4 Link Faults
4 Link Faults
About This Chapter
This describes link faults in terms of the symptoms, troubleshooting methods, and typical cases.
4.1 Link Fault Symptoms

This describes the impacts of link faults on services, possible alarms, and involved performance
counters.
4.2 Link Troubleshooting Methods
This describes how to troubleshoot different types of link faults. Basically, when a link is faulty,
first deal with the reported alarm, then determine the subclass of the fault, and finally rectify the
fault.
4.3 Typical Cases of Troubleshooting Link Faults
This describes the typical cases of troubleshooting link faults.

4 Link Faults BSS Troubleshooting Guide
4.1 Link Fault Symptoms

This describes the impacts of link faults on services, possible alarms, and involved performance
counters.
4.1.1 Impacts of Link Faults on Services

This describes the impacts of different link faults on services.
4.1.2 Alarms Related to Link Faults
This describes the BSS alarms caused by link faults. The alarms help locate and rectify the faults.
4.1.3 Counters Related to Link Faults
This describes the counters related to link faults. The counters can help locate and rectify the
faults.
4.1.1 Impacts of Link Faults on Services

This describes the impacts of different link faults on services.
OML/EML Faults
When the operation and maintenance link (OML) or extended maintenance link (EML) is faulty,
neither voice services nor data services can be provided for the MSs in the coverage of the BTS.
RSL/ESL Faults
When the radio signaling link (RSL) or extended signaling link (ESL) is faulty, the impacts are
as follows:
l If the BCCH TRX is faulty and the TRX aid function is not configured, neither voice
services nor data services can be provided for the MSs in the cell.
l If a non-BCCH TRX is faulty, neither voice services nor data services can be provided for
the MSs occupying the TRX channel.
PBSL Faults
When the PCU is configured outside the BSC, the impacts of PCU-BSC signaling links (PBSLs)
are as follows:
l When all the PBSLs are faulty, data services cannot be provided for the MSs controlled by
the BSC.
l When some PBSLs are faulty, the capacity of data services of the BSC decreases.
SS7 Signaling Link Faults

SS7 signaling link faults affect signaling transmission directly and voice services indirectly. The
specific impacts are as follows:
l When all the SS7 signaling links break down, all the MSs drop calls.
l When some SS7 signaling links break down, the loads on other SS7 signaling links increase
but not all the MSs drop calls.

Ater Signaling Link Faults

Ater signaling link faults directly affect voice services. The specific impacts are as follows:
l When all the Ater signaling links break down, all the MSs drop calls.
l When some Ater signaling links break down, the loads on other links increase but not all
the MSs drop calls.
Ater OML Faults

When the Ater OML is faulty in BM/TC separated mode, no operation or maintenance for the
remote GTCS can succeed.
SIGTRAN Link Faults

Signaling transport (SIGTRAN) link faults affect IP signaling transmission on the A interface
directly and voice services indirectly. The specific impacts are as follows:
l When all the SIGTRAN links break down, all the MSs drop calls.
l When some SIGTRAN links break down, the loads on other SIGTRAN links increase but
not all the MSs drop calls.
Abis Interface IP Link Faults

When the IP link on the Abis interface is faulty, neither voice services nor data services can be
provided for all the MSs in the coverage of the BTS.
4.1.2 Alarms Related to Link Faults

This describes the BSS alarms caused by link faults. The alarms help locate and rectify the faults.
Alarms Related to BTS Interface Link Faults

Table 4-1 lists the alarms related to the BTS interface link faults.
Table 4-1 Alarms related to the BTS interface link faults
Fault Cause Site Type Alarm Name
Line fault or BTS3X 2114 LAPD Alarm

transmission module
fault 2214 E1 Local Alarm
2216 E1 Remote Alarm
2218 AIS Alarm
2452 E1 Outboard Alarm
2454 E1 Inboard Alarm
BTS3001C 3052 LAPD alarm
3152 E1 Local alarm

Fault Cause Site Type Alarm Name
3154 E1 Remote alarm
3190 Optical Receive Channel alarm
3192 Optical Transmit Channel alarm
3194 ASU E1 Port alarm
BTS3002C 3572 LAPD alarm
3672 E1 Local alarm
3674 E1 Remote alarm
3794 Optical Receive Channel Alarm
3796 Optical Transmit Channel Alarm
3798 IASU E1 Port Alarm
3800 IASU Cock Source Lost alarm
Double- 4102 LAPD Alarm

transceiver BTS
4714 E1 Local Alarm
4716 E1 Remote Alarm
4718 AIS Alarm
4836 E1 Port Illegal Alarm
7400 IASU E1 Port Alarm
7402 IASU Cock Source Lost Alarm
7404 IASU Crystal Oscillator Alarm
7512 E1 Outboard Alarm
7514 E1 Inboard Alarm
Alarms Related to BSC Interface Link Faults

Table 4-2 lists the alarms related to the BSC interface link faults.

Table 4-2 Alarms related to the BSC interface link faults
Fault Cause Alarm Name
E1/T1 fault or optical port fault 21205 Board Fault
20081 Loss of E1/T1 Signals (LOS)
20082 Loss of E1/T1 Frames (LOF)
20083 Remote E1/T1 Alarm (RAI)
20084 E1/T1 Alarm Indication Signal (AIS)
20085 Loss of E1/T1 Multiframes (LOM)
20086 E1/T1 Link Loopback
20087 High BER over the E1/T1 Link
20089 Excessive Loss of E1/T1 Signals in an

Hour
20090 Excessive E1/T1 Synchronization

Failures in an Hour
20091 E1/T1 Excessive Peer End Alarms Per

Hour
20092 E1/T1 Excessive Bit Error Rate Per

Hour
20093 E1/T1 Excessive Slip Frames Per Hour
20222 Loss of Signals on the Optical Port

(RLOS)
20223 Loss of Received Signal Frames on the

Optical Port (RLOF)
20224 Out-of-Synchronization of Received

Signal Frames on the Optical Port (ROOF)
20225 Mismatch of Trace Byte of the

Regenerator Section on the Optical Port
(RTIM)
20226 Regenerator Section Signal Failure

(RSF)
20227 Regenerator Section Signal

Deteriorated (RSD)
20228 Multiplex Section Alarm Indication

Signal (MAIS)
20229 Multiplex Section Remote Defect

Indication (MRDI)
20230 Loopback on the Optical Port

20231 Administration Unit Alarm Indication

Signal (AUAIS)
20232 Loss of Administration Unit Pointer

(AULOP)
20239 Loss of Tributary Unit Multi-frames

(TULOM)
20240 Tributary Unit Alarm Indication

Signal (TUAIS)
20241 Loss of Tributary Unit Pointer

(TULOP)
20248 Loss of Tributary Signals (LOS)
20249 Tributary Alarm Indication Signal

(AIS)
20250 Loss of Tributary Frames (LOF)
20251 Remote Alarm Indication over the

Tributary (RAI)
20252 Loss of Tributary Multi-Frames

(LOM)
20253 Slip Frame over the Tributary
20254 Tributary Loopback Alarm
20255 Optical Module Fault
Transmission fault 21001 LAPD Link Congestion
21002 Broken LAPD Link
21501 MTP3 DSP Unreachable
21502 MTP3 Layer 3 Congestion
21503 MTP3 Link Unavailable
21504 MTP3 Signaling Link2 Congestion
21512 MTP3 Link Test Failure
21513 MTP2 Link Location Failure
21514 MTP2 Link Service Disrupted
21516 Route Transmission on the MTP3

Prohibited
20081 Loss of E1/T1 Signals (LOS)
21525 SCCP DSP Unreachable

21526 SCCP Subsystem Prohibited
21528 Remote SCCP Fault
21531 Lack of SCCP Connection Resources
21551 Ater OML Broken Alarm
102 Disrupted Connection with the CBC
103 All SS7 Links Faulty
104 All PBSLs in the PCU Are Faulty
129 MSC Resetting
1000 LAPD OML Fault
21551 Ater OML Broken Alarm
701 M3UA Link Fault
702 M3UA Link Congestion
703 M3UA Route Unvailable
704 M3UA Destination Entity Unvailably
705 FG2/GOU Route Status Unavailable
Alarms Related to External PCU Interface Link Faults

Table 4-3 lists the alarms related to the external PCU interface link faults.
Table 4-3 Alarms related to the external PCU interface link faults
Fault Type Alarm Name
E1/T1 fault or optical port fault 20081 Loss of E1/T1 Signals (LOS)
20082 Loss of E1/T1 Frames (LOF)
20083 Remote E1/T1 Alarm (RAI)
20084 E1/T1 Alarm Indication Signal (AIS)
20085 Loss of E1/T1 Multiframes (LOM)
20086 E1/T1 Link Loopback
20087 High BER over the E1/T1 Link
20089 Excessive Loss of E1/T1 Signals in an

Hour


Failures in an Hour
20091 E1/T1 Excessive Peer End Alarms Per

Hour
20092 E1/T1 Excessive Bit Error Rate Per

Hour
20093 E1/T1 Excessive Slip Frames Per Hour
20222 Loss of Signals on the Optical Port

(RLOS)
20223 Loss of Received Signal Frames on the

Optical Port (RLOF)
20224 Out-of-Synchronization of Received

Signal Frames on the Optical Port (ROOF)
20225 Mismatch of Trace Byte of the

Regenerator Section on the Optical Port
(RTIM)
20226 Regenerator Section Signal Failure

(RSF)
20227 Regenerator Section Signal

Deteriorated (RSD)
20228 Multiplex Section Alarm Indication

Signal (MAIS)
20229 Multiplex Section Remote Defect

Indication (MRDI)
20230 Loopback on the Optical Port
20231 Administration Unit Alarm Indication

Signal (AUAIS)
20232 Loss of Administration Unit Pointer

(AULOP)
20239 Loss of Tributary Unit Multi-frames

(TULOM)
20240 Tributary Unit Alarm Indication

Signal (TUAIS)
20241 Loss of Tributary Unit Pointer

(TULOP)
20248 Loss of Tributary Signals (LOS)

20249 Tributary Alarm Indication Signal

(AIS)
20250 Loss of Tributary Frames (LOF)
20251 Remote Alarm Indication over the

Tributary (RAI)
20252 Loss of Tributary Multi-Frames

(LOM)
20253 Slip Frame over the Tributary
20254 Tributary Loopback Alarm
20255 Optical Module Fault
Transmission fault 21001 LAPD Link Congestion
105 ONE PBSL Link SINGLE PASS
106 PCIC CHECK IS INCONSISTENT
128 No Circuit Configured in the PCU
4.1.3 Counters Related to Link Faults

This describes the counters related to link faults. The counters can help locate and rectify the
faults.
Table 4-4 lists the counters related to link faults.
Table 4-4 Counters related to link faults

Counter Description
L5012 I Frames Discarded by LAPD Link
L5007 I Frames Resent on LAPD Link
L0486 Disruptions of the BSC-CBC Connection
L0056A Number of MSC Resets
L6002 Out-of-Service Duration of MTP3 Link
L6003 Duration of MTP3 Link Fault
L6004 Duration of MTP3 Link Local Inhibition
L6005 Duration of MTP3 Link Remote Inhibition

Counter Description
L6006 Duration of MTP3 Link Remote Processor Fault
L6007 Duration of MTP3 Link Congestion
L6008 MTP3 Link Failures for All Reasons
L6009 MTP3 Link Local Inhibitions
L6010 MTP3 Link Remote Inhibitions
L6011 MTP3 Link Remote Processor Failures
L6012 MTP3 Link Local Switchovers
L6015 MTP3 Link Congestions
RL7009 Ratio of CREF by Peer SCCP
RL7010 Ratio of CREF by Peer SCCP
AL1251 Mean Number of Faulty Circuits on the Ater

Interface
AL0051 Mean Number of Faulty Circuits on the A Interface
AL0053 Mean Number of Blocked Circuits on the A

Interface
AL8351 Mean Number of Faulty Circuits on the Pb

Interface
AL8353 Mean Number of Blocked Circuits on the Pb

Interface
L0031 SCTP Link Retransmission Thunks
L0032 SCTP Link Received Error Packets
L0033 SCTP Link Sent Thunks
L0034 SCTP Link Received Thunks
L0035 SCTP Link Sent Packets
L0036 SCTP Link Received Packets
L0021 M3UA Link Failure Times
L0022 M3UA Link Failure Duration
L0023 M3UA Link Congestion Duration
L0024 M3UA Link Sent Packets
L0025 M3UA Link Received Packets
L01001 Received Bytes
L01002 Received Packets

Counter Description
L01003 Sent Bytes
L01004 Sent Packets
L01005 Error Sent Packets
SC010A CS Packets Sent over FE Port of the PTU
SC000A CS Packets Received over FE Port of the PTU
SC011A PS Packets Sent over FE Port of the PTU
SC001A PS Packets Received over FE Port of the PTU
SC012A Control-Plane Packets Sent over FE Port of the PTU
SC003A Error CRC Packets Received over FE Port of the

PTU
4.2 Link Troubleshooting Methods

This describes how to troubleshoot different types of link faults. Basically, when a link is faulty,
fault.
Procedure
Step 1 Deal with the reported alarm according to the alarm help.
Step 2 If the alarm persists, determine the subclass of the fault and take the corresponding measure, as
listed in Table 4-5.
Table 4-5 Link troubleshooting methods

Fault Location Fault Rectification
On the BSC6000 Local Maintenance 4.2.1 Troubleshooting OML Faults

Terminal, check the status of LAPD links.
The result shows that the State of an OML
is Failure.
On the BSC6000 Local Maintenance 4.2.2 Troubleshooting EML Faults

The result shows that the State of an EML
is Failure.

On the BSC6000 Local Maintenance 4.2.3 Troubleshooting RSL Faults

The result shows that the State of an RSL
is Failure. In addition, the Subrack area on
the BTS Device Panel shows that the TRX
board is faulty.
On the BSC6000 Local Maintenance 4.2.4 Troubleshooting ESL Faults

The result shows that the State of an ESL
is Failure.
On the BSC6000 Local Maintenance 4.2.5 Troubleshooting PBSL Faults

The result shows that the State of a PBSL
is Failure.
On the BSC6000 Local Maintenance 4.2.6 Troubleshooting SS7 Signaling Link

Terminal, check the status of SCCP Faults
connections. The result shows that the
Destination signaling point state of an
SCCP connection is Prohibit.
On the BSC6000 Local Maintenance

Terminal, check the status of MTP3 links.
The result shows that the Service
Transmit of an MTP3 link is Not using.
On the BSC6000 Local Maintenance

Terminal, check the status of MTP2 links.
The result shows that the Link State of an
MTP2 link is Start Locating.
On the Local Maintenance Terminal, 4.2.7 Troubleshooting Ater Signaling Link

check the status of Ater signaling links. Faults
The result shows that an Ater signaling
link is faulty.
On the BSC6000 Local Maintenance 4.2.8 Troubleshooting Ater OML Faults

Terminal, check the status of Ater OMLs.
The result shows that the Available
Status of some or all HDLC links is Not
available.
On the Local Maintenance Terminal, 4.2.11 Troubleshooting M3UA Link Faults

check the status of M3UA links. The result
shows that the Link State of an M3UA
link is the non-activated or invalid state.
On the Local Maintenance Terminal, 4.2.12 Troubleshooting M3UA Route

check the status of M3UA routes. The Unavailability Faults
result shows that the Access Flag of an
M3UA route is Unavailable.

On the Local Maintenance Terminal, 4.2.13 Troubleshooting M3UA Destination

check the status of M3UA destination Entity Inaccessibility Faults
entities. The result shows that the Access
Flag of an M3UA destination entity is
Inaccessible.
On the BSC6000 Local Maintenance 4.2.14 Troubleshooting Abis Interface IP

Terminal, check the status of LAPD links. Link Faults
The result shows that the State of an OML,
EML, RSL, or ESL is Failure.
Technical Support.
----End
4.2.1 Troubleshooting OML Faults

This describes how to troubleshoot OML faults. When an OML is faulty, neither voice services
nor data services can be provided for the MSs in the coverage of the BTS.
Fault Symptoms
The State of an OML is Failure, which you can check on the BSC6000 Local Maintenance
Terminal by referring to Maintaining LAPD Links. An alarm 1000 LAPD OML Fault is
reported. Multiple cells are out of service. Neither voice services nor data services can be
provided for the MSs in the coverage of the BTS.
Possible Causes
The possible causes of OML faults are as follows:
l The GEIUB/GOIUB is faulty.

l The GXPUT is faulty.
l The GXPUM is faulty.
l The configured BTS type is inconsistent with the actual one.
l The port configured for the BTS is inconsistent with the actual one.
l The BTS main control board is faulty.
l The BTS is not powered.
l The BTS has a transmission failure.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, view the alarm information.
l Check whether a power-off alarm exists. If existent, rectify the fault by referring to 4.1.2
Alarms Related to Link Faults.

l Check whether an E1/T1 transmission alarm exists. If existent, rectify the fault by referring
to 4.2.9 Troubleshooting E1/T1 Transmission Faults.
l If no such an alarm exists, go to Step 2.
Step 2 By referring to Querying BTS Board Information, check whether the BTS main control board
is faulty.
l If faulty, rectify the fault by referring to 4.1.2 Alarms Related to Link Faults.
l If not faulty, go to Step 3.
Step 3 By referring to Querying the Status of an Interface Board Port, check whether the E1/T1 port
in connection with the BTS is faulty.
Step 4 By referring to Querying BSC Board Information, check whether the GEIUB/GOIUB,
GXPUT, and GXPUM are faulty.
Step 5 Check the configured BTS type.
1. On the BSC6000 Local Maintenance Terminal, click the corresponding TRX on the
Management Tree tab page.
2. In the Site Description area on the Site Device Panel tab page, check whether the
configured Site Type is consistent with the actual one.
l If inconsistent, remove this BTS and then reconfigure it by referring to Configuring
the BTS.
l If consistent, go to Step 6.
Step 6 Check the number of the E1/T1 port in connection with the BTS.
2. In the Site Description area on the Site Device Panel tab page, check whether the GEIUB
Subrack No., GEIUB Slot No., and GEIUB Port No. are consistent with the actual ones.
l If the settings are incorrect, move the BTS by referring to . Alternatively, connect the
corresponding port on the DDF and the configured port.
l If the settings are correct but the fault persists, contact the Huawei Customer Service
Center by referring to 1.3.1 Obtaining Technical Support.
----End
4.2.2 Troubleshooting EML Faults

This describes how to troubleshoot EML faults. When the EMLs are faulty, neither voice services
nor data services can be provided for the MSs in the coverage of the BTS.
Fault Symptoms
On the BSC6000 Local Maintenance Terminal, the query result shows that the State of an
EML is Failure. For details, refer to Maintaining LAPD Links. The alarms 1000 LAPD OML
Fault and 11270 LAPD Alarm are reported. Multiple cells are out of service. Neither voice
services nor data services can be provided for the MSs in the coverage of the BTS.

Possible Causes
The possible causes of the EML fault are as follows:
l The GEHUB board is faulty.
l The GXPUT is faulty.
l The configured BTS type is inconsistent with the actual BTS type.
l The port configured for the BTS is inconsistent with the actual one.
l The BTS main control board is faulty.
l The BTS is not powered.
l The BTS has a transmission failure.
Procedure
l Check whether a power-off alarm exists. If existent, rectify the fault by referring to 4.1.2
Alarms Related to Link Faults.
l Check whether an E1/T1 transmission alarm exists. If existent, rectify the fault by referring
to 4.2.9 Troubleshooting E1/T1 Transmission Faults.
l If not existent, go to Step 2.
Step 2 Check whether the BTS board is faulty by referring to Querying BTS Board Information.
in connection with the BTS is faulty.
Step 4 Check whether the GEHUB, GXPUT, and GXPUM are faulty by referring to Querying BSC
Board Information.
Step 5 Check the configured BTS type.
2. In the Site Description area on the Site Device Panel tab page, check whether the
configured Site Type is consistent with the actual one.
l If inconsistent, remove this BTS and then reconfigure it by referring to Configuring
the BTS.
Step 6 Check the number of the E1/T1 port in connection with the BTS.

2. In the Site Description area on the Site Device Panel tab page, check whether the GEHUB
Subrack No., GEHUB Slot No., and GEHUB Port No. are consistent with the actual
ones.
l If inconsistent, move the BTS by referring to . Alternatively, connect the DDF cable to
the data configuration port.
Step 7 On the BSC6000 Local Maintenance Terminal, browse the HDLC path data in the BTS data,
and check whether 31 timeslots are configured for the HDLC path. For details, refer to Browsing
Configuration Data.
l If the number of configured timeslots is not 31, reconfigure this BTS. For details of
configuring timeslots, refer to Timeslots on the Abis Interface.
l If the number of configured timeslots is 31 but the fault persists, contact the Huawei
Customer Service Center by referring to 1.3.1 Obtaining Technical Support.
----End
4.2.3 Troubleshooting RSL Faults

This describes how to troubleshoot RSL faults. When an RSL is faulty, neither voice services
nor data services can be provided for the MSs in the cell.
Fault Symptoms
The RSL fault symptoms are as follows:
l The State of an RSL is Failure, which you can check on the BSC6000 Local Maintenance
Terminal by referring to Maintaining LAPD Links.
l On the BSC6000 Local Maintenance Terminal, the Cabinet area of the Site Device
Panel shows that the TRX board is faulty.
l On the BSC6000 Local Maintenance Terminal, an alarm 2204 TRX Communication
Alarm or 405 Cell Out of Service is reported. Neither voice services nor data services can
be provided for the MSs in the cell.
NOTE
When the BCCH TRX is faulty, the TRX aid function works. TRX aid can take effect only when it is
configured for the cell. For detailed operations, refer to Configuring TRX Cooperation.
Possible Causes
The possible causes of RSL faults are as follows:
l The corresponding OML is not operational.

l The DTRU is faulty.
Procedure
l If a TRX fault alarm such as 2204 TRX Communication Alarm is reported, rectify the
fault by referring to 4.1.2 Alarms Related to Link Faults.
l If no such an alarm is reported, go to Step 2.

Step 2 Check the status of the involved links by referring to Maintaining LAPD Links.
l If the OML is faulty, rectify the fault by referring to 4.2.1 Troubleshooting OML
Faults.
l If the RSL is faulty, go to Step 3.
Step 3 Check the TRX configuration.

1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, click
the cell. A dialog box is displayed, as shown in Figure 4-1.
Figure 4-1 Cell attributes
2. Check the frequency.
Select the TRX from the Assigned TRXs area, and then check whether the corresponding
frequency in the Frequencies area is consistent with that supported by the TRX.
l If the setting is incorrect, replace the TRX board or modify the frequency. For details
about how to modify frequencies, refer to Configuring the Multiband Network.
l If the setting is correct but the fault persists, contact the Huawei Customer Service
----End
4.2.4 Troubleshooting ESL Faults

This describes how to troubleshoot ESL faults. When the ESLs are faulty, neither voice services
nor data services can be provided for the MSs in the cell.

Fault Symptoms
On the BSC6000 Local Maintenance Terminal, query the status of the LAPD link. The result
shows that the State of the ESL is Failure. For details, refer to Maintaining LAPD Links. An
alarm 2114 LAPD Alarm is reported. Multiple cells are out of service and neither voice services
nor data services can be provided for all the MSs in the coverage of the BTS.
Possible Causes
The possible causes of the ESL faults are as follows:
l The GEHUB board is faulty.

l The DPTU board is incorrectly installed or cabled.
Procedure
l Check whether the TRX fault-related alarms such as 2204 TRX Communication Alarm
exist. If existent, rectify the fault by referring to 4.1.2 Alarms Related to Link Faults.
l If not existent, go to Step 2.
Step 2 Check whether the GEHUB/GFGUB board is faulty by referring to Querying BSC Board
Information.
Step 3 Check whether the cable is correctly connected to the E1 port on the DPTU board. The correct
way is to connect the E1 cable at the top of the cabinet to the E1 port on the DPTU board.
l If the cable is connected incorrectly, reconnect the cable in the correct way as mentioned
previously.
l If the cable is connected correctly, go to Step 4.
Step 4 Check whether the DPTU board is inserted in a correct slot. The correct location is slot 3 or 4
of subrack 0.
l If the board is inserted in a wrong slot, reinsert the board in the correct location as mentioned
previously.
l If the board is inserted correctly but the fault persists, contact the Huawei Customer Service
----End
4.2.5 Troubleshooting PBSL Faults

This describes how to troubleshoot PBSL faults. When a PBSL is faulty, PS services cannot be
provided for the MSs or the capacity of PS services decreases.
Fault Symptoms
The State of a PBSL is Failure, which you can check on the BSC6000 Local Maintenance
Terminal by referring to Maintaining LAPD Links.

Possible Causes
The possible causes of PBSL faults are as follows:
l The GEIUB/GOIUB is faulty.
l A transmission fault occurs.
l The E1 frame format on the external PCU side is inconsistent with that on the BSC side.
l The timeslot configured on the BSC side is inconsistent with that configured on the external
PCU side.
Procedure
Step 1 By referring to Querying BSC Board Information, check whether the GEIUB/GOIUB and
GXPUM in connections with the BTS are faulty.
Step 2 By referring to Querying the Status of an Interface Board Port, check whether E1/T1 port of
the PBSL is faulty.
Step 3 Check the Port Attributes in the Configure Board Attributes dialog box of the GEIUP/
GOIUP. Set the Frame Format to DOUBLE_FRAME.
NOTE
The frame format on the PCU side is set to DOUBLE_FRAME.

1. Right-click the GEIUP/GOIUP on the BSC Device Panel, and then select Configure
Board Attributes from the shortcut menu. A dialog box is displayed, as shown in Figure
4-2.

Figure 4-2 Configure Board Attributes dialog box
2. Click Next. A dialog box is displayed, as shown in Figure 4-3.
Figure 4-3 Checking the frame format
3. Set the Frame Format shown in Figure 4-3 to DOUBLE_FRAME.

Step 4 Check whether the Timeslot No. of the PBSL on the BSC side is consistent with the Signaling
Link Timeslot No. of the PBSL on the external PCU side.
l Check the timeslot number of the signaling link on the external PCU side.

On the PCU LocalWS, check the Signaling Link Timeslot No. on the PCU side by running
the pcu show e1slot command.
l Check the Timeslot No. of the PBSL on the BSC side.
1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal,
right-click the root node BSC6000, and then click the BSC Attributes tab. The tab page
is displayed, as shown in Figure 4-4.
Figure 4-4 BSC attributes
2. Click PCU in the Other Data area. In the displayed dialog box, click the Pb Signaling
Link tab, as shown in Figure 4-5.

Figure 4-5 Checking the PCU
3. Click Refresh to check the Timeslot No. of the PBSL.
Based on the query result, do as follows:
l If the configured timeslot number is inconsistent with the actual one, change the Timeslot
No. of the PBSL on the BSC6000 Local Maintenance Terminal or PCU LocalWS.
Step 5 On the PCU LocalWS, check the status of the PBSL link and perform the corresponding
operations.
1. Run the command mt lapd show state {<BoardNo> all}|<LapdNo>|<LapdName> to
check the status of the PBSL.
l If the administrative status of the PBSL is Blocked, run the command mt lapd unblock
{<BoardNo> all}|<LapdNo>|<LapdName> to unblock the PBSL. The PBSL should
be restored to the Enabled state. If not restored, go to Step 5.2.
l If the administrative status of the PBSL is Unblocked, end the troubleshooting.
2. Run the command Mt lapd port show state <BoardNo> <HLPU/L2PUNo> to check the
status of the port on the L2PU/HLPU that carries the PBSL.
l If the LoopMode of the port carrying the PBSL is local loopback or remote loopback,
run the command mt lapd port loop set <BoardNo> <PortNo> <LoopMode> to set
LoopMode to NoLoop. The status of the PBSL should be restored to ENABLED. If
not restored, go to Step 5.3.

l If the LoopMode of the port carrying the PBSL is NoLoop, end the troubleshooting.
3. Rectify the PBSL fault by referring to 9.2.5 Troubleshooting LAPD Link Faults
(External PCU).
----End
4.2.6 Troubleshooting SS7 Signaling Link Faults

This describes how to troubleshoot SS7 signaling link faults. When all the SS7 signaling links
configured for the BSC break down, all the MSs drop calls. When some links break down, the
loads on other links increase but not all the MSs drop calls.
Fault Symptoms
The fault symptoms of SS7 signaling links are as follows:
l The Destination signaling point state of an SCCP link is Prohibit, which you can check
on the BSC6000 Local Maintenance Terminal by referring to Maintaining the SCCP.
l The Service Transmit of an MTP3 link is Not using, which you can check on the BSC6000
Local Maintenance Terminal by referring to Maintaining MTP3 Links.
l The Link State of an MTP2 link is Start Locating, which you can check on the BSC6000
Local Maintenance Terminal by referring to Querying Status of MTP2 Links.
l An alarm 21525 SCCP DSP Unreachable or 21501 MTP3 DSP Unreachable is reported,
which you can check on the BSC6000 Local Maintenance Terminal. The ongoing
services are disrupted.
l The alarm 21514 MTP2 Link Service Disrupted is cleared immediately after it is
generated. Intermittence may lead to call drops.
Possible Causes
The possible causes of SS7 signaling link faults are as follows:
l The SS7 signaling link is not operational.

l The SS7 signaling link breaks down.
l The SS7 signaling link is disconnected intermittently.
NOTE
Assume that the peer MSC runs properly.
Procedure
l If the SS7 signaling link is not operational, do as follows:
1. By referring to Querying BSC Board Information, check whether the GXPUM,
GEIUT/GOIUT, and GEIUA/GOIUA that carry the SS7 signaling link are faulty.
– If faulty, rectify the fault by referring to 4.1.2 Alarms Related to Link Faults.
– If not faulty, go to Step 2.
2. On the BSC6000 Local Maintenance Terminal, click the BSC Attributes tab. In
the Other Data area, click SS7 Signaling Point. A dialog box is displayed, as shown
in Figure 4-6.

Figure 4-6 Checking the OSP of the SS7 signaling link
3. Check whether the settings of OPC, Encoding Scheme, Network Indicator, and
DPC are consistent with those on the MSC side.
– If inconsistent, delete the settings and then reconfigure the parameters by referring
to Configuring the SS7 Signaling Points.
– If consistent, go to Step 4.
4. On the BSC6000 Local Maintenance Terminal, click the BSC Attributes tab. In
the Other Data area, click SS7 Signaling Link. A dialog box is displayed, as shown
in Figure 4-7.

Figure 4-7 Checking the SS7 signaling link
5. Check whether the settings of A Timeslot Mask, SLC, and SLC Send are consistent
with those on the MSC side.
– If inconsistent, delete the settings and then reconfigure the parameters by referring
to Adding an SS7 Signaling Link.
– If consistent, go to Step 6.
6. By referring to Querying the Status of an Interface Board Port, check whether the
E1/T1 port that resides on the A interface and carries the SS7 signaling link is faulty.
E1/T1 port that resides on the Ater interface and carries the SS7 signaling link is faulty.
If faulty, rectify the fault by referring to 4.1.2 Alarms Related to Link Faults.
l If the SS7 signaling link breaks down, do as follows:
1. By referring to Querying BSC Board Information, check whether the GXPUM,
GEIUT(GOIUT), and GEIUA(GOIUA) that carry the SS7 signaling link are faulty.
E1/T1 port that resides on the A interface and carries the SS7 signaling link is faulty.

E1/T1 port that resides on the Ater interface and carries the SS7 signaling link is faulty.
If faulty, rectify the fault by referring to 4.1.2 Alarms Related to Link Faults.
l If the SS7 signaling link is disconnected intermittently, do as follows:
1. On the BSC6000 Local Maintenance Terminal, check whether there is an alarm
21514 MTP2 Link Service Disrupted that is cleared immediately after it is generated.
– If there is, rectify the fault by referring to 4.1.2 Alarms Related to Link Faults.
– If the fault persists, go to Step 2.
2. If the fault persists, contact the Huawei Customer Service Center by referring to 1.3.1
Obtaining Technical Support.
----End
4.2.7 Troubleshooting Ater Signaling Link Faults

This describes how to troubleshoot the faults in the Ater signaling links. The fault symptoms
show that if all the Ater signaling links are broken, all the MSs incur call drops; if a few Ater
signaling links are broken, the link load increases and no MSs incur call drops; if the Ater
signaling links are overloaded, the call loss increases.
Fault Symptoms
Check the status of the Ater signaling links on the Local Maintenance Terminal. For details,
refer to List LAPD Link(LST LAPDLNK) and List Ater Signaling Link(LST ATERSL).
On the BSC6000 Local Maintenance Terminal, by querying the alarm information you can
find that the 21002 Broken LAPD Link alarm is reported.
Possible Causes
The possible causes of the faults in Ater signaling links are as follows:
l In BM/TC separated mode, the GEIUT/GOIUT in the GMPS or remote GTCS is faulty.
l A transmission fault occurs on the Ater interface.
Procedure
Step 1 Check whether the GEIUT/GOIUT that carries the Ater signaling links is faulty. For details,
refer to Querying BSC Board Information.
Step 2 Check whether the E1/T1 port that carries the Ater OM links is faulty. For details, refer to
Querying the Status of an Interface Board Port. If faulty, rectify the fault by referring to
4.1.2 Alarms Related to Link Faults.
----End

4.2.8 Troubleshooting Ater OML Faults

This describes how to troubleshoot Ater OML faults. When all Ater OMLs break down, no
operation or maintenance for the remote subracks can be performed.
Fault Symptoms
The Available Status of some or all HDLC links is Not available, which you can check on the
BSC6000 Local Maintenance Terminal by referring to Querying the Status of the Ater
OML. In addition, an alarm 21551 Ater OML Broken Alarm is reported. If all the Ater OMLs
break down, no operation or maintenance for the remote subracks can be performed.
Possible Causes
The possible causes of Ater OML link faults are as follows:
l In BM/TC separated mode, the GEIUT/GOIUT in the GMPS or remote GTCS is faulty.
l A transmission fault occurs on the Ater interface.
Procedure
Step 1 By referring to Querying BSC Board Information, check whether the GEIUT/GOIUT carrying
the Ater OML is faulty.
of the Ater OML is faulty. If faulty, rectify the fault by referring to 4.1.2 Alarms Related to
Link Faults.
----End
4.2.9 Troubleshooting E1/T1 Transmission Faults

This describes how to troubleshoot the faults in E1/T1 links and upper-level E1/T1 links.
Fault Symptoms
On the BSC6000 Local Maintenance Terminal, the query result shows that Port Status of the
E1/T1 port is Fault. For details of how to browse the alarm information, refer to Querying the
Status of an Interface Board Port. The following alarms are reported:
l 20081 Loss of E1/T1 Signals (LOS)
l 20082 Loss of E1/T1 Frames (LOF)
l 20083 Remote E1/T1 Alarm (RAI)
l 20084 E1/T1 Alarm Indication Signal (AIS)
l 20085 Loss of E1/T1 Multiframes (LOM)
l 20086 E1/T1 Link Loopback
l 20087 High BER over the E1/T1 Link
l 20089 Excessive Loss of E1/T1 Signals in an Hour

l 20090 Excessive E1/T1 Synchronization Failures in an Hour

l 20091 E1/T1 Excessive Peer End Alarms Per Hour
l 20092 E1/T1 Excessive Bit Error Rate Per Hour
l 20093 E1/T1 Excessive Slip Frames Per Hour
Possible Causes
The possible causes of the E1/T1 transmission faults are as follows:
l The DB44 connector of the E1/T1 cable is not securely connected to the panel of the
interface board.
l The transmission cable is wrongly connected.
l The E1/T1 port on the local device cannot receive signals normally.
l The E1/T1 port on the peer device cannot transmit signals normally.
l The line codes are inconsistent between lines.
l The subrack is not properly grounded.
l The shielding layer of the cable between the BSC and the transmission equipment is
damaged.
l The transmission line is faulty.
Procedure
Rectify the faults according to the alarm-handling suggestions. If the faults persist, contact the
Huawei Customer Service Center by referring to 1.3.1 Obtaining Technical Support.
----End
4.2.10 Troubleshooting Optical Transmission Faults

This describes how to troubleshoot the optical transmission faults. The optical transmission is
interrupted and the upper links, such as OML, RSL, SS7 signaling link, PBSL, Ater signaling
link, and Ater OML are faulty at the same time.
Fault Symptoms
On the BSC6000 Local Maintenance Terminal, the query result shows that Port Status of the
E1/T1 port is Fault. For details, refer to Querying the Status of an Interface Board Port. The
following alarms are reported:
l 20222 Loss of Signals on the Optical Port (RLOS)
l 20223 Loss of Received Signal Frames on the Optical Port (RLOF)
l 20224 Out-of-Synchronization of Received Signal Frames on the Optical Port (ROOF)
l 20225 Mismatch of Trace Byte of the Regenerator Section on the Optical Port (RTIM)
l 20228 Multiplex Section Alarm Indication Signal (MAIS)
l 20227 Regenerator Section Signal Deteriorated (RSD)
l 20228 Multiplex Section Alarm Indication Signal (MAIS)
l 20229 Multiplex Section Remote Defect Indication (MRDI)

l 20230 Loopback on the Optical Port

l 20231 Administration Unit Alarm Indication Signal (AUAIS)
l 20232 Loss of Administration Unit Pointer (AULOP)
l 20239 Loss of Tributary Unit Multi-frames (TULOM)
l 20240 Tributary Unit Alarm Indication Signal (TUAIS)
l 20241 Loss of Tributary Unit Pointer (TULOP)
l 20248 Loss of Tributary Signals (LOS)
l 20249 Tributary Alarm Indication Signal (AIS)
l 20250 Loss of Tributary Frames (LOF)
l 20251 Remote Alarm Indication over the Tributary (RAI)
l 20252 Loss of Tributary Multi-Frames (LOM)
l 20253 Slip Frame over the Tributary
l 20254 Tributary Loopback Alarm
l 20255 Optical Module Fault
Possible Causes
The possible causes of optical transmission faults are as follows:
l The optical cable is not connected properly.

l The transmission cable is wrongly connected.
l The optical port on the peer board is faulty.
l The optical port on the local board is faulty.
l The optical module is faulty.
l The transmission line is faulty.
Procedure
Rectify the faults according to the alarm-handling suggestions. If the faults persist, contact the
Huawei Customer Service Center by referring to 1.3.1 Obtaining Technical Support.
----End
4.2.11 Troubleshooting M3UA Link Faults

This describes how to troubleshoot M3UA link faults. When all the M3UA links configured for
the BSC break down, all the MSs drop calls. When some of the M3UA links break down, the
loads on others increase but the MSs do not drop calls.
Fault Symptoms
The M3UA link fault symptoms are as follows:
l On the BSC6000 Local Maintenance Terminal, check the status of SCCP connections.
The result shows that the Destination signaling point state of an SCCP connection is
Prohibited. For details, refer to Maintaining the SCCP.

l On the Local Maintenance Terminal, check the status of M3UA links. The result shows
that the Link State of an M3UA link is the non-activated or invalid state. For details, refer
to Display M3UA Link Status(DSP M3LNK).
l On the BSC6000 Local Maintenance Terminal, an alarm 701 M3UA Link Fault or
possibly 21525 SCCP DSP Unreachable and 704 M3UA Destination Entity
Unvailably are reported. The ongoing services are disrupted.
Possible Causes
The possible causes of M3UA link faults are as follows:
l The links are manually disconnected or deactivated.
l The SCTP link configuration is inconsistent between the BSC and the MSC.
l The router to the BSC is wrongly configured.
Procedure
Step 1 Check whether the GXPUM, GXPUT, and GFGUA that carry the M3UA links are faulty by
referring to Querying BSC Board Information.
l If faulty, check whether the board type is consistent with the data configuration and whether
the board is securely connected.
Step 2 Check whether the parameter configuration related to M3UA links is consistent between the
BSC and the MSC.
1. On the BSC6000 Local Maintenance Terminal, right-click the GFGUA board on the
BSC Device Panel tab page, and then choose Configure M3UA Link > Modify M3UA
Link.
2. A dialog box is displayed. Click Modify.
3. Select the M3UA tab, as shown in Figure 4-8.

Figure 4-8 Modify M3UA Link dialog box
Check whether the parameters such as Local Port No., Local Address 1, Local Address 2,
Peer Port No., Peer Address 1, and Peer Address 2 on the BSC side are consistent with those
on the MSC side.
l If inconsistent, delete the original parameter settings and reconfigure the parameters.
Step 3 Verify whether the SCTP check and algorithm on the BSC side are consistent with those on the
MSC side.
Refer to Step 2. On the interface shown in Figure 4-8, select the SCTP tab page, as shown in
Figure 4-9.

Figure 4-9 Modify M3UA Link dialog box (2)
Check whether the parameters such as Receive Check Sum Validation Flag, Send Check Sum
Validation Flag, and Check Sum Type on the BSC side are consistent with those on the MSC
side.
l If inconsistent, reconfigure the parameters to keep them consistent with those on the MSC
side.
Step 4 On the Local Maintenance Terminal, run the PING IP command to ping the IP address of the
remote MSC. Check whether the IP address can be pinged by referring to Ping Peer IP Address
(PING IP).
l If the IP address cannot be pinged, check whether the route from the BSC to the MSC is
normal. If the route is faulty, contact the Huawei Customer Service Center by referring to
1.3.1 Obtaining Technical Support.
l If the IP address can be pinged, on the peer MSC side ping the device IP address of the local
BSC. If the device IP address cannot be pinged, go to Step 5.
Step 5 Check the route configuration on the router connected to the BSC. Verify whether there is a
route to the GFGUA and ensure no redundant route configuration exists.
l If there is no route to the GFGUA, add a valid route by referring to step 5 described in
Configuring the GFGUA/GOGUA.
l If there is a route to the GFGUA and no redundant route configuration but the fault persists,
contact the Huawei Customer Service Center by referring to 1.3.1 Obtaining Technical
Support.
----End
4.2.12 Troubleshooting M3UA Route Unavailability Faults

This describes how to troubleshoot the faults caused by M3UA route unavailability. The fault
symptom shows that the MSs incur call drops if all the M3UA routes from the BSC to the MSC

are unavailable, or only the load on the available routes increases and the MSs incur no call
drops if some of the M3UA routes are unavailable.
Fault Symptoms
The fault symptoms of M3UA route unavailability are as follows:
l On the Local Maintenance Terminal, check the status of M3UA routes. The result shows
that the Access Flag of an M3UA route is Unaccessible. For details, refer to Display M3UA
Route Status(DSP M3RT).
l On the BSC6000 Local Maintenance Terminal, an alarm 703 M3UA Route
Unvailable or possibly 21525 SCCP DSP Unreachable and 704 M3UA Destination
Entity Unvailably are reported. The ongoing services are disrupted.
Possible Causes
The possible causes of M3UA route unavailability are as follows:
l The M3UA link is faulty.

l If the BSC is connected to the MSC through the STP, the BSC may receive the signaling
network management message DUNA from the STP.
Procedure
Step 1 Check whether the M3UA link is faulty.
l If faulty, rectify the fault by referring to 4.2.11 Troubleshooting M3UA Link Faults.
Step 2 Check whether the BSC is connected to the MSC through an STP entity.
l If the BSC is connected to the MSC through an STP entity, check whether the link and the
route between STP and MSC is available.
l If the BSC is directly connected to the MSC with the link activated but the fault persists,
contact the Huawei Customer Service Center by referring to 1.3.1 Obtaining Technical
Support.
----End
4.2.13 Troubleshooting M3UA Destination Entity Inaccessibility

Faults
This describes how to troubleshoot the faults in the M3UA destination entity that is unavailable.
The fault symptom shows that all the MSs incur call drops.
Fault Symptoms
The fault symptoms of M3UA destination entity inaccessibility are as follows:

l On the Local Maintenance Terminal, check the status of M3UA destination entities. The
result shows that the Access Flag of an M3UA destination entity is Unaccessible. For
details, refer to Display M3UA Destination Entity Status(DSP M3DE).
l On the BSC6000 Local Maintenance Terminal, view the alarm information. The alarms
704 M3UA Destination Entity Unvailably, 21525 SCCP DSP Unreachable, and 701
M3UA Link Fault are reported.
Possible Causes
The possible causes of M3UA destination entity inaccessibility are as follows:
l The M3UA link is faulty.
l The M3UA destination entity does not exist.
Procedure
Step 1 Check whether the M3UA link is faulty.
l If faulty, rectify the fault by referring to 4.2.11 Troubleshooting M3UA Link Faults.
Step 2 Check whether the configuration data of the M3UA destination entity is correct.
1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-
click BSC6000 and choose Configure M3UA Data > Configure M3UA Entity.
2. Select the M3UA DE tab, as shown in Figure 4-10.
Figure 4-10 Configure M3UA Entity dialog box

Check whether the DPC(Hex) on the BSC side is consistent with the DCP on the MSC side.
l If the DPC is inconsistent, delete the M3UA destination entity on the BSC side and then
reconfigure the parameter.
l If the DPC(Hex) is consistent, go to Step 3.
Step 3 Check whether the M3UA linkset is configured correctly.

On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click
BSC6000 and choose Configure M3UA Linkset. A dialog box is displayed, as shown in Figure
4-11.
Figure 4-11 Configure M3UA Linkset dialog box
Check whether the Adjacent DE Name on the BSC side is consistent with that on the MSC
side.
l If the corresponding MSC does not exists, add a linkset to the destination entity that is
adjacent to the MSC.
l If the corresponding MSC exists, go to Step 4.
Step 4 Check whether the M3UA route is configured correctly.

On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click
BSC6000 and choose Configure M3UA Data > Configure M3UA Route. A dialog box is

Figure 4-12 Configure M3UA Route dialog box
Check whether the DE Name on the BSC side correspond to the destination entity on the MSC
side.
l If not existent, add a destination entity that corresponds to that on the MSC side.
l If existent, check whether the M3UA link is faulty. For details, see 4.2.11 Troubleshooting
M3UA Link Faults.
----End
4.2.14 Troubleshooting Abis Interface IP Link Faults

This describes how to troubleshoot the faults in the Abis interface IP link. When an Abis interface
IP link is faulty, neither voice services nor data services can be provided for the MSs in the
coverage of the BTS.
Fault Symptoms
On the BSC6000 Local Maintenance Terminal, query the status of the LAPD link. The query
result shows that the State of the OML/EML/RSL/ESL is Failure. For details, refer to
Maintaining LAPD Links. An alarm 2114 LAPD Alarm is reported. Multiple cells are out of
service and neither voice services nor data services can be provided for the MSs in the coverage
of the BTS.
NOTE
After the Abis interface uses the IP link, the BTS communicates with the BSC through the IP network.
Therefore, if the IP link is functional, the IP bearer layer works normally.
Possible Causes
The possible causes of Abis interface IP link faults are as follows:

l The data configuration is inconsistent.

l The hardware is wrongly installed or cabled.
l The BSC route configuration is incorrect.
Procedure
Step 1 On the Local Maintenance Terminal, ping the IP address of the BTS port. For details, refer to
Pinging the Peer-End IP Address.
l If you ping the IP address successfully, you can infer that the BTS has obtained the IP
address; but if the OML is inaccessible, you can infer that the BTS fails to set up the link
correctly. Then, go to Step 2.
l If you cannot ping the IP address, the BTS may have not obtained the IP address through
the DHCP. Check whether the ports interconnecting the BTS and the BSC are configured
consistently with the data configuration and whether the electronic labels of the BTS are
consistent with the data configuration. If inconsistent, reconfigure the ports or the electronic
labels. For details, refer to Configuring Abis over IP. If consistent, go to Step 3.
Step 2 Check whether the TRAN wiring terminal is plugged out from the interface board.
l If the TRAN wiring terminal is still connected to the interface board, plug it out to reduce
its interference to the IP communication.
l If the TRAN wiring terminal is plugged out, go to Step 3.
Step 3 Check whether the DPTU board is inserted in a correct slot. The correct location is slot 3 or 4
of subrack 0.
l If the board is inserted in a wrong slot, reinsert the board in the correct location as mentioned
previously.
l If the board is inserted in a correct slot, go to Step 4.
Step 4 Check whether the route from the BSC to the BTS is configured incorrectly.
l If the route configuration is incorrect, reconfigure the route as follows:
– For layer 2 networking, the destination IP address is the logical IP address of the BTS,
and the gateway IP address is the port IP address of the BTS.
– For layer 3 networking, configure the following two routes:
– One destination IP address is the logical IP address of the BTS, and the gateway IP
address is the IP address of the port connecting the router and the GFGUB.
– One destination IP address is the DHCP Relay IP address of the BSC, and the
gateway IP address is the IP address of the port connecting the router and the
GFGUB.
For details, refer to Configuring Abis over IP.
l If the route configuration is correct but the fault persists, contact the Huawei Customer
Service Center by referring to 1.3.1 Obtaining Technical Support.
----End
4.3 Typical Cases of Troubleshooting Link Faults

This describes the typical cases of troubleshooting link faults.

4.3.1 Case: BTS TRX Faults

This describes a case of troubleshooting BTS TRX faults. Due to the TRX faults, the TRX board
cannot upload data normally, and therefore the configured TRX should be kept consistent with
the actual TRX type.
4.3.2 Case: BTS Faults
This describes a typical case of troubleshooting BTS faults. Due to the BTS faults, all the boards
of the BTS cannot upload data normally, and therefore the configured BTS type should be kept
consistent with the actual BTS type.
4.3.3 Case: BTS Loading Failure
This describes a typical case of troubleshooting the BTS loading failure. The symptom is that
when the 120-ohm trunk cable is used to connect the BTS and the BSC, they cannot communicate
normally. The DIP switches of the BSC6000 interface board and the BTS DTMU must be
adjusted.
4.3.4 Case: Abis Transmission Faults
This describes a typical case of troubleshooting Abis transmission faults. If the Abis transmission
is faulty, the LIUx LEDs of the BTS blink irregularly. You should prevent both ends of the E1
cable from being grounded.
4.3.5 Case: M3UA Link Faults
This describes a typical case of troubleshooting M3UA link faults. The link connection between
BSC and MSC is also associated with the configuration of routers. You need not configure
redundant route data for the routers if unnecessary.
4.3.1 Case: BTS TRX Faults

This describes a case of troubleshooting BTS TRX faults. Due to the TRX faults, the TRX board
cannot upload data normally, and therefore the configured TRX should be kept consistent with
the actual TRX type.
Fault Symptoms
The inconsistency between configured TRX and actually used TRX results in the failure of the
TRX board to upload data. Thus, a fault occurs in the RSL.
Fault Location and Rectification

Delete the TRX and reconfigure the TRX data. For details, refer to Modifying TRX
Assignment.
4.3.2 Case: BTS Faults

This describes a typical case of troubleshooting BTS faults. Due to the BTS faults, all the boards
of the BTS cannot upload data normally, and therefore the configured BTS type should be kept
consistent with the actual BTS type.
Fault Symptoms
The inconsistency between configured BTS type and actual BTS type results in the failure of
the BTS boards to upload data. Thus, a fault occurs in the OML.


Delete the BTS and reconfigure the BTS data. For details, refer to Configuring the BTS.
4.3.3 Case: BTS Loading Failure

This describes a typical case of troubleshooting the BTS loading failure. The symptom is that
when the 120-ohm trunk cable is used to connect the BTS and the BSC, they cannot communicate
normally. The DIP switches of the BSC6000 interface board and the BTS DTMU must be
adjusted.
Fault Symptoms
If the DIP switches of the BSC6000 interface board and the BTS DTMU are not correctly set
when the 120-ohm trunk cable is used for transmission, both ends of the cable may be grounded
and thus form a loop. This follows a burst of bit errors, which disables the communication
between the BTS and the BSC. As a result, the BTS cannot be initialized.

l Set the DIP switches S1, S3, S4, S5, and S6 of the BSC GEIUB to OFF.
l Set the SW6 and SW7 of the BTS DCSU to OFF. For details, refer to DIP Switches on
the DCSU.
l Set the S4, S5, S6, and S7 of the BTS DTMU to OFF. For details, refer to DIP Switches
on the DTMU.
4.3.4 Case: Abis Transmission Faults

This describes a typical case of troubleshooting Abis transmission faults. If the Abis transmission
is faulty, the LIUx LEDs of the BTS blink irregularly. You should prevent both ends of the E1
cable from being grounded.
Fault Symptoms
The 120-ohm twisted pair cable is used for the Abis transmission of a BTS and the signals are
transmitted through the DDF. After a loopback is performed on the DDF, the LIUx LEDs of the
BTS are off. The analysis shows that the Abis transmission is normal but bit errors may occur
on the Abis interface. The causes of bit errors are as follows:
l The connectors of the 120-ohm twisted pair cable are in poor contact.
l The connectors of the 120-ohm twisted pair cable are polluted.
l The 120-ohm twisted pair cable has wires exposed, which leads to strong signal
interference.
l Both ends of the shielding layer of the E1 cable between the BTS DTMU, DDF, and
BSC6000 GEIUB are grounded.
The previous analysis shows that both ends of the shielding layer of the E1 cable between the
BTS DTMU and the DDF are grounded and a loop is formed, which leads to bit errors. The
causes of bit errors are as follows:
l The signals are transmitted between the GEIUB, GEIUP, and GEIUT of the BSC through
the 120-ohm twisted pair cable in balanced mode. If the DIP switch for the transmitting

end is set to OFF, the cable is not grounded automatically. If the DDF is grounded only,
then no loop is formed, and thus the signal quality at the BSC transmitting end is good.
l The DIP switch on the BTS3012 DTMU is used to control the grounding of the E1 cable
jacket at the transmitting end, and the DIP switch on the DCSU is used for controlling
different transmission cables instead of grounding only the E1 cable jacket at the
transmitting end. The DIP switches S4, S5, S6, and S7 on the DTMU are set to ON before
delivery. Such settings form a loop between DTMU and DDF and lead to bit errors.

1. On the BSC6000 Local Maintenance Terminal, check the status of the E1 port. The Abis
interconnection, however, introduces the following problems:
l The LIUx LEDs of the BTS blink irregularly.
l On the BSC6000 Local Maintenance Terminal, trace the Abis OML messages. The
BTS reports UI frames occasionally. For details, refer to Tracing OML Messages on
the Abis Interface.
l The BTS local and remote alarms are reported on the site maintenance terminal, and
the related alarms are cleared.
l On the BSC6000 Local Maintenance Terminal, view the alarm information, and you
can find that the 1000 LAPD OML Fault alarm is reported and the LAPD link is broken.
l Use the DDF connector probe to check the transmit and receive signal strength. The
result shows that the BSC transmit signal is strong and the BTS transmit signal is weak.
2. Check the E1 cable connection and prevent both ends of the E1 cable from being grounded.
4.3.5 Case: M3UA Link Faults

This describes a typical case of troubleshooting M3UA link faults. The link connection between
BSC and MSC is also associated with the configuration of routers. You need not configure
redundant route data for the routers if unnecessary.
Fault Symptoms
The reset of the BSC GFGUA causes the SCTP link to break down. After the Ethernet cable is
reconnected, the SCTP link works normally.

1. Verify the check and algorithm configuration of the SCTP link of the BSC and MSC. The
CRC32 check is not enabled. For details of the BSC side, refer to Step 3 described in 4.2.11
Troubleshooting M3UA Link Faults.
The SCTP link check and algorithm are correctly configured because the SCTP link works
normally after the Ethernet cable is reconnected. Therefore, the data configuration between
BSC and MSC is considered to be consistent.
2. Check the IP address of the SCTP and the port number on both BSC and MSC sides and
ensure that there is no data inconsistency between them. For details of the data configuration
on the BSC side, refer to Configuring the GFGUA/GOGUA.
After the Ethernet cable is reconnected, the SCTP link recovers. You can infer that the data
configuration between the two sides is consistent. Therefore, the problem is not caused by
data inconsistency.

3. According to the previous analysis, you can decide that the fault is related to the router
configuration. Perform the following operations for further analysis:
(1) Trace the SCTP of the A interface on the BSC side. You can find that only the uplink
message to the MSC instead of the MSC downlink message to the BSC is traced. For
details, refer to Tracing SCTP Messages on the A Interface.
(2) Trace the SCTP of the A interface on the MSC side. The MSC can receive the SCTP
message from the BSC and the MSC responds to the message.
(3) The port of the MSC connected to the router catches IP packets. The port can catch
the messages sent from or received by the MSC.
Based on the analysis, you can determine that the messages are discarded in the router and
you need to check the router configuration.
4. Check the router configuration. Figure 4-13 shows the routes between the BSC and the
MSC.
Figure 4-13 Router configuration
G 1
F
BSC G Router MSC
U
A 5
Two routes are configured from the MSC to the BSC: one is to port 1 of the GFGUA, and
the other is to port 5 of the GFGUA. When port 1 is enabled and port 5 is disabled, the
physical connection between the routers still exists. That is, two MSC-to-BSC routes exist
on the router. One is available and the other is unavailable.
Because the router determines the availability of a route according to physical connections,
the router identifies the route to port 5 as available. When the IP packets from the MSC to
the BSC are transferred at the router, the router may forward the IP packets to an unavailable
port 5.
To sum up, the messages sent by the BSC can reach the MSC, but the messages returned
by the MSC cannot reach the BSC.
5. Delete the redundant routes in the router, that is, physically disconnect the router from port
5.

BSS Troubleshooting Guide 5 Clock Faults
5 Clock Faults
About This Chapter
This describes clock faults in terms of the symptoms, troubleshooting methods, and typical cases.
5.1 Clock Fault Symptoms

This describes the impacts of clock faults on services, possible alarms, and involved performance
counters.
5.2 Clock Troubleshooting Methods
This describes how to troubleshoot clock faults. Basically, when a clock fault occurs, first deal
with the reported alarm, then determine the subclass of the fault, and finally rectify the fault.
5.3 Typical Cases of Troubleshooting Clock Faults
This describes the typical cases of troubleshooting clock faults.

5 Clock Faults BSS Troubleshooting Guide
5.1 Clock Fault Symptoms

This describes the impacts of clock faults on services, possible alarms, and involved performance
counters.
5.1.1 Impacts of Clock Faults on Services

This describes the impacts of clock faults on services.
5.1.2 Alarms Related to Clock Faults
This describes the BSS alarms related to clock faults. The alarms help locate and rectify the
faults.
5.1.3 Counters Related to Clock Faults
Currently there are no counters related to clock faults.
5.1.1 Impacts of Clock Faults on Services

This describes the impacts of clock faults on services.
The impacts of clock faults on services are as follows:
l The MS drops the call.

l The signaling link is disconnected intermittently.
5.1.2 Alarms Related to Clock Faults

This describes the BSS alarms related to clock faults. The alarms help locate and rectify the
faults.
Alarms related to BSC clock faults

Table 5-1 lists the alarms related to BSC clock faults.
Table 5-1 Alarms related to BSC clock faults
BSC clock faults 20003 Board Fault - Faulty Inner Clock
20005 Faulty Clock Source 0 from the Front

Interface Board to the Backplane of the
GSCU
20006 Faulty Clock Source 1 from the Front

GSCU
20007 Faulty Clock Source 0 from the Rear

GSCU

20008 Faulty Clock Source 1 from the Rear

GSCU
20009 Faulty 8 kHz Clock Source from the

Active GGCU to the Backplane of the GSCU
20010 Faulty 8 kHz Clock Source from the

Standby GGCU to the Backplane of the
GSCU
20013 Faulty GGCU 8 kHz Clock Source for

the Front Panel of the GSCU
20016 Faulty 32 MHz Clock from the

Backplane
20026 Faulty Phase-Locked Loop of the

Board Clock
20039 Faulty Output Clock Signals
20044 Unavailable Clock Source
20221 Loss of Clock on the Optical Port

(RLOC)
20321 Unavailable Clock Reference for

GGCU
20322 Unavailable Current Clock Reference

for GGCU
20323 GGCU Failure-Abnormal Frequency

Doubler
20324 GGCU Failure-Abnormal Local

Oscillation Signal
20325 Clock Reference Failure of GGCU over

24 Hours
20329 Unavailable Input Clock Source for

GGCU
Alarms related to BTS clock faults

Table 5-2 lists the alarms related to BTS clock faults.

Table 5-2 Alarms related to BTS clock faults

BTS3X clock fault 2166 TRX Main Clock Alarm
2168 TRX Slave Clock Alarm
2196 TRX Clock Critical Alarm
2208 Clock Reference abnormal Alarm
2232 Master TMU Clock Failure Alarm
2234 Master TMU Clock Alarm
2236 Extended TMU Clock Alarm
2260 13M Clock Maintenance Alarm
2574 PBU Main Clock Alarm
2576 PBU Slave Clock Alarm
2578 PBU Clock Critical Alarm
BTS3001C clock fault 3134 MFU Clock Critical alarm
3146 Clock Reference Abnormal alarm
3172 MMU Clock alarm
3438 Clock alarm
BTS3002C clock fault 3654 DRU Clock Critical alarm
3666 Clock Reference Abnormal alarm
3692 IOMU Clock Alarm
3718 13M Clock Maintenance Alarm
3800 IASU Cock Source Lost alarm
3802 IASU Crystal Oscillator Alarm
Double-transceiver BTS clock fault 4120 DBUS Clock alarm
4154 TRX main clock alarm
4156 TRX slave clock alarm
4184 TRX clock critical alarm
4708 Clock Reference Abnormal Alarm
4732 TMU clock critical alarm
4734 Master TMU clock alarm
4736 Extended TMU clock alarm

4760 13M Maintenance Alarm
4772 Master Clock Alarm
4804 Slave DTMU TDMA CLK Alarm
5320 DUP Unit Clock Abnormal
9682 PBU Main Clock Alarm
9684 PBU Slave Clock Alarm
9686 PBU Clock Critical Alarm
5.1.3 Counters Related to Clock Faults

Currently there are no counters related to clock faults.
5.2 Clock Troubleshooting Methods

This describes how to troubleshoot clock faults. Basically, when a clock fault occurs, first deal
with the reported alarm, then determine the subclass of the fault, and finally rectify the fault.
Procedure
Table 5-3 Clock troubleshooting methods

On the BSC6000 Local Maintenance 5.2.1 Troubleshooting Clock Source Faults

Terminal, find that the PLL state is not
Locked.
On the BSC6000 Local Maintenance 5.2.2 Troubleshooting Board Clock Faults

Terminal, find that a clock source
provided by a board is in an abnormal state.
Technical Support.
----End
5.2.1 Troubleshooting Clock Source Faults

This describes how to troubleshoot clock source faults.

Fault Symptoms
The PLL state is not Locked, which you can check on the BSC6000 Local Maintenance
Terminal by referring to Maintaining the BSC Clock Reference Status. An alarm 20010
Faulty 8 kHz Clock Source from the Standby GGCU to the Backplane of the GSCU or
20009 Faulty 8 kHz Clock Source from the Active GGCU to the Backplane of the GSCU
is reported.
Possible Causes
The possible causes of clock source faults are as follows:
l The active GGCU fails to lock the upper-layer clock source and provide the timing signals
to the GSCU.
l The active GGCU is faulty.
l The standby GSCU is faulty.
l The backplane is faulty.
Procedure
Step 1 By referring to Maintaining the BSC Clock Reference Status, check whether the standby
GGCU locks the upper-layer clock source.
l If the standby GGCU locks the upper-layer clock source, go to Step 2.
l If the standby GGCU fails to lock the upper-layer clock source, go to Step 3.
Step 2 Check whether the alarm is cleared.

l If the alarm is cleared, end the troubleshooting.
l If the alarm is not cleared, go to Step 3.
Step 3 Check whether both the active and the standby GSCUs report this alarm.
l If both the active and the standby GSCUs report this alarm, go to Step 4.
l If only one GSCU reports this alarm, go to Step 6.
Step 4 Secure the standby GGCU and then check whether the alarm is cleared.
Step 5 Replace the standby GGCU and then check whether the alarm is cleared after the board is
successfully restarted.
Step 6 Secure the GSCU and then check whether the alarm is cleared.
Step 7 Check whether the board reporting the alarm is active.

l If the board is active, go to Step 8.
l If the board is standby, go to Step 9.

Step 8 Switch over the active and standby boards, and then check whether the alarm is cleared after the
originally standby board is successfully restarted.
Step 9 Replace the standby GSCU and then check whether the alarm is cleared after the board is
l If the alarm is not cleared, contact the Huawei Customer Service Center by referring to
----End
5.2.2 Troubleshooting Board Clock Faults

This describes how to troubleshoot board clock faults.
Fault Symptoms
A clock source provided by a board is in an abnormal state, which you can check on the BSC6000
Local Maintenance Terminal by referring to Maintaining the BSC Clock Reference
Status. An alarm 20003 Board Fault - Faulty Inner Clock is reported.
Possible Causes
The possible cause of a board clock fault is that the board hardware is faulty.
Procedure
Replace the faulty board and then check whether the alarm is cleared after the board is
l If the alarm is not cleared, contact the Huawei Customer Service Center by referring to
----End
5.3 Typical Cases of Troubleshooting Clock Faults

This describes the typical cases of troubleshooting clock faults.
5.3.1 Case: All BTS Clock Reference Sources Unavailable

This describes a typical case of troubleshooting the faults occuring when all BTS clock reference
sources of the BSC are unavailable. If the BSC clock reference source is not BITS Clock, all
BTS clock reference sources are unavailable.
5.3.2 Case: Slip Frame Alarm
This describes a typical case of handling the slip frame alarm. If the BSC clock is configured
incorrectly or the transmission equipment/cable is faulty, the slip frame alarm is generated. You
must check the BSC clock configuration and the transmission equipment/cable.
5.3.3 Case: Phase-Locked Loop in Non-Locked State

This describes a typical case of troubleshooting the faults in the phrase-lock loop that is in non-
locked state. when the faults occur, you can infer that the clock reference source of the GGCU
is faulty.
5.3.4 Case: Handover Call Drop Due to Large Frequency Offset of BTS Clock
This describes how to troubleshoot the handover call drop fault caused by the unstable BTS
clock. You need to keep the BTS clock stable.
5.3.1 Case: All BTS Clock Reference Sources Unavailable

This describes a typical case of troubleshooting the faults occuring when all BTS clock reference
sources of the BSC are unavailable. If the BSC clock reference source is not BITS Clock, all
BTS clock reference sources are unavailable.
Fault Symptoms
When the networking mode is BTS - BSC (BM) - trunk transmission - BSC (TC) - MSC, all
BTSs of the BSC report the alarm warning that the clock reference source is faulty. Other network
performances are listed as follows:
l The BSC traces the line clock, and the BSC reports no related alarms.
l The transmission on the Ater interface is normal.
l Other BSCs under the same MSC report no related alarms.
The MSC and BSC report no clock reference source alarms, and you can infer that the clock
frequency offset is within a normal range.
The BTS clock frequency offset ranges from -0.15 ppm to +0.15 ppm (a millionth), and the BSC
clock frequency offset ranges from -4.6 ppm to +4.6 ppm. If the MSC clock frequency offset is
larger than ±0.15 ppm and smaller than ±4.6 ppm (in theory), the BTS reports the clock reference
source abnormal alarm and the BSC reports no related alarms.

Modify the clock configuration on the BSC6000 Local Maintenance Terminal. Set the Source
Type to BITS0. For details, refer to Configuring the System Clock.
5.3.2 Case: Slip Frame Alarm

This describes a typical case of handling the slip frame alarm. If the BSC clock is configured
incorrectly or the transmission equipment/cable is faulty, the slip frame alarm is generated. You
must check the BSC clock configuration and the transmission equipment/cable.
Fault Symptoms
Currently, the BSC slip frame alarm is of two types:
l 20093 E1/T1 Excessive Slip Frames Per Hour

l 20253 Slip Frame over the Tributary
If the BSC clock is asynchronous with the MSC clock and the difference between them reaches
a frame, one frame signal is discarded or repeated. Therefore, when the slip frame alarm is
reported, you must check the configuration and state of the clock on both BSC and MSC sides.


1. Check whether the BSC clock is configured incorrectly, if the alarm 20253 Slip Frame
over the Tributary is reported.
l If the BSC clock is configured incorrectly, go to 2.
l If the BSC clock is configured correctly, go to 3.
2. Based on the configurations of system clock, GMPS line clock, and GTCS line clock,
configure the BSC clock correctly. For details, refer to Configuring the System Clock,
Configuring the Line Clock for the GMPS, and Configuring the Line Clock for the
GTCS.
l If the alarms are cleared, end the task.
l If the alarms are still reported, go to 3.
3. Contact the transmission engineer to check whether the transmission equipment or cable
is normal.
l If the transmission cable is normal, contact the Huawei Customer Service Center by
referring to 1.3.1 Obtaining Technical Support.
l If the transmission cable is faulty, contact the transmission engineer to solve the problem
until the alarms are cleared.
5.3.3 Case: Phase-Locked Loop in Non-Locked State

This describes a typical case of troubleshooting the faults in the phrase-lock loop that is in non-
locked state. when the faults occur, you can infer that the clock reference source of the GGCU
is faulty.
Fault Symptoms
On the BSC6000 Local Maintenance Terminal, query the status of the BSC clock reference
source. The PLL state is Free running, and the Work mode is Automatic. For details, refer to
Maintaining the BSC Clock Reference Status. Figure 5-1 shows the dialog box.

Figure 5-1 Query BSC Clock Reference State dialog box

The non-locked state of the phrase-locked loop of the GGCU is categorized into Free running,
Fast tracking, and Hold over. Normally, the phrase-locked loop of the GGCU is in locked state.
If the phrase-locked loop of the GGCU is in non-locked state, the clock reference source of the
GGCU is faulty.
l When the phrase-locked loop of the GGCU is in Free running state, you can infer that the
clock reference source is unavailable. You must check the configuration of the clock
reference source of the GGCU.
– If the clock reference source type is line 0 or line 1, view the alarm information on the
BSC6000 Local Maintenance Terminal, and check whether the GEIUA/GOIUA
where the line clock is located reports alarms. If alarms are reported, handle the alarms
by referring to BSS Alarm Reference.
– If the clock reference source type is BITS0, view the alarm information on the BSC6000
Local Maintenance Terminal, and check whether there are alarms related to the clock
reference source. If alarms are reported, handle the alarms by referring to BSS Help
System.


l When the phrase-locked loop of the GGCU is in Fast tracking state, this state is temporary
but will not last long.
l When the phrase-locked loop of the GGCU is in Hold over state, you can infer that the
current clock reference source is unavailable. On the BSC6000 Local Maintenance
Terminal, view the alarm information and check whether the alarms related to the clock
reference source are reported. If alarms are reported, handle the alarms by referring to BSS
Alarm Reference.
5.3.4 Case: Handover Call Drop Due to Large Frequency Offset of

BTS Clock
This describes how to troubleshoot the handover call drop fault caused by the unstable BTS
clock. You need to keep the BTS clock stable.
Fault Symptoms
Call drops occasionally occur when the handover is performed at the DCS1800M frequency
band. However, the signal level is normal without interference.

1. The BTS frequency offset remain large. The 13 MHz output frequency offset of some BTSs
reaches 2.5 Hz. This exceeds the national standard, 0.65 Hz.
2. The system reports many BTS 8 kHz clock alarms, and the MSC reports 3598 Phase-Lock
Loop alarm frequently. You can infer that the MSC clock is unstable and that the call drop
is mainly caused by the unstable BTS clock.
3. The MSC clock reference source is adjusted on the MSC side. The BTS clock becomes
stable and the BTS 8 kHz clock alarms are cleared. The handover call drop disappears.

BSS Troubleshooting Guide 6 Handover Faults
6 Handover Faults
About This Chapter
This describes handover faults in terms of the symptoms, troubleshooting methods, and typical
cases.
6.1 Handover Fault Symptoms

This describes the impacts of handover faults on services, possible alarms, and involved
performance counters.
6.2 Handover Troubleshooting Methods
This describes how to troubleshoot handover problems. Basically, when a handover problem
occurs, first deal with the reported alarm, then determine the subclass of the fault, and finally
rectify the fault.

6 Handover Faults BSS Troubleshooting Guide
6.1 Handover Fault Symptoms

This describes the impacts of handover faults on services, possible alarms, and involved
6.1.1 Impacts of Handover Faults on Services

This describes the impacts of handover faults on services. When a handover fault occurs, the
voice quality deteriorates or the handover success rate decreases obviously.
6.1.2 Alarms Related to Handover Faults
This describes the alarms related to handover faults. The alarms help locate and rectify the faults.
6.1.3 Counters Related to Handover Faults
This describes the counters related to handover faults. The counters help locate and rectify the
faults.
6.1.1 Impacts of Handover Faults on Services

This describes the impacts of handover faults on services. When a handover fault occurs, the
voice quality deteriorates or the handover success rate decreases obviously.
The types of handovers originated by the MS are as follows:
l Edge handover
l Bad quality handover
l Rapid level drop handover
l Power budget (PBGT) handover
l Interference handover
If the handover fails, the voice quality is deteriorated or the call is dropped. Moreover, the
handover success rate decreases obviously.
6.1.2 Alarms Related to Handover Faults

This describes the alarms related to handover faults. The alarms help locate and rectify the faults.
The BSC clock alarm, BTS clock alarm, TRX fault alarm, CDU fault alarm, and antenna fault
alarm are related to handover.
When the clock alarm is generated, the BTS service still provides services but greatly affects
the handover. For clock alarms, refer to 5.1.2 Alarms Related to Clock Faults.
6.1.3 Counters Related to Handover Faults

This describes the counters related to handover faults. The counters help locate and rectify the
faults.
Table 6-1 lists the counters related to handover faults.

Table 6-1 Counters related to handover faults

Counter Description
ZK3180 Handover Success Ratio per BSC
ZK3181 Intra-BSC Handover Success Rate
ZK3176 Inter-BSC Outgoing Cell Handover Success Rate
CH302A Failed Internal Intra-Cell Handovers (Channel

Unavailable)
CH302C Failed Internal Intra-Cell Handovers (Timer

Expired)
CH302D Failed Internal Intra-Cell Handovers

(Reconnection to Old Channels)
H3022A Failed Internal Intra-Cell Handovers (Underlay

to Overlay)
H3021A Failed Internal Intra-Cell Handovers (Overlay to

Underlay)
H3022M Failed Internal Intra-Cell Handovers (Other

Causes) (Overlay to Underlay)
H3021M Failed Internal Intra-Cell Handovers (Other

Causes) (Overlay to Underlay)
H322B Failed Incoming Internal Inter-Cell Handovers

(Terrestrial Resource Request Failed)
H322D Failed Incoming Internal Inter-Cell Handovers

H322G Failed Incoming Internal Inter-Cell Handovers

(A Interface Failure)
H3220A Failed Internal Intra-Cell Handovers (No

Channel Available) (SDCCH)]
H3229A Failed Internal Intra-Cell Handovers (No

Channel Available) (TCH)]
CH322C Failed Internal Intra-Cell Handovers (Timer

Expiry)

Counter Description
H312A Failed Outgoing Internal Inter-Cell Handovers

(No Channel Available)
H312B Failed Outgoing Internal Inter-Cell Handovers

H312G Failed Outgoing Internal Inter-Cell Handovers

(A Interface Failure)
CH312C Failed Outgoing Internal Intra-Cell Handovers

(Timer Expiry)
CH312D Failed Outgoing Internal Inter-Cell Handovers

H342I Failed Incoming External Inter-Cell Handovers

(Invalid Message)
H3420A Failed External Intra-Cell Handovers (No

Channel Available) (SDCCH)]
H3429A Failed External Intra-Cell Handovers (No

Channel Available) (TCH)]
H342E Failed Incoming External Inter-Cell Handovers

(CIC Unavailable)
H342F Failed Incoming External Inter-Cell Handovers

(CIC Allocated)
H342B Failed Incoming External Inter-Cell Handovers

H342H Failed Incoming External Inter-Cell Handovers

(Clear Commands Sent By MSC)
CH342C Failed Incoming External Inter-Cell Handovers

(Timer Expired)
CH332K Failed Outgoing External Inter-Cell Handovers

(Handover Request Rejected)
CH332D Failed Outgoing External Inter-Cell Handovers

CH332H Failed Outgoing External Inter-Cell Handovers

(Clear Commands Sent By MSC)
CH332L Failed Outgoing External Inter-Cell Handovers

(T7 Expired)
CH332C Failed Outgoing External Inter-Cell Handovers

(T8 Expired)

6.2 Handover Troubleshooting Methods

This describes how to troubleshoot handover problems. Basically, when a handover problem
rectify the fault.
Procedure
Table 6-2 Handover troubleshooting methods
The MS does not originate a handover 6.2.1 Troubleshooting No or Too Many

when it should do or originates handovers Handovers Originated by the MS
frequently.
A handover fails because the target cell is 6.2.2 Troubleshooting Destination Cell
congested. Congestion Faults
A cell to which no handover can be 6.2.3 Troubleshooting Hardware Faults

performed reports a BTS fault alarm.
No handover between BSCs or MSCs can 6.2.4 Troubleshooting Inter-BSC or Inter-

succeed. MSC Handover Failures
A handover of any other type fails. 6.2.5 Troubleshooting Other Handover

Faults
Technical Support.
----End
6.2.1 Troubleshooting No or Too Many Handovers Originated by

the MS
This describes how to troubleshoot a problem of no handover originated or too many handovers
originated by the MS.
Possible Causes
The possible causes of no handover originated or too many handovers originated are as follows:
l If the handover threshold is too high, few handovers can be originated. If it is too low, too
many handovers are originated frequently.
l If a neighboring cell is not configured, the MS cannot originate a handover to this cell.

l If the handover hysteresis is too large, few handovers can be originated. If it is too small,
too many handovers are originated frequently.
l If the N or P value is too large, few handovers can be originated. If it is too small, the
handover target cell may not be the best one.
Procedure
Step 1 If the handover threshold is improper, adjust it.
Step 2 If a neighboring cell is not configured, add it.
Step 3 If the handover hysteresis is improper, adjust it.
Step 4 If the N or P values is improper, adjust it.

NOTE
For detailed operations, refer to Configuring the Handover.
----End
6.2.2 Troubleshooting Destination Cell Congestion Faults

This describes how to troubleshoot destination cell congestion faults. When the destination cell
is congested, the MS cannot obtain the channel resource after requesting a handover.
Possible Causes
The possible causes of destination cell congestion are as follows:
l The number of MSs suddenly increases, exceeding the designed number.

l Improper parameter settings during network optimization lead to admission of too many
MSs to the cell.
l Improper handover parameter settings lead to admission of too many MSs to the cell.
Procedure
Step 1 If a TRX or channel fault occurs, rectify such a fault first.
Step 2 If the cell does not allow the conversion from full-rate channels to half-rate channels, set TCH
Rate Adjust Allow of each TRX of this cell to Yes on the BSC6000 Local Maintenance
Terminal by referring to Modifying Channel Attributes (Full Rate and Half Rate).
Alternatively, expand the capacity of the cell.
----End
6.2.3 Troubleshooting Hardware Faults

This describes how to troubleshoot hardware faults. When a hardware fault occurs, an alarm is
reported.
Possible Causes
The possible causes of hardware faults are as follows:

l The BTS transmission management unit (TMU) is faulty.

l The BTS TRX is faulty.
l The BTS CDU is faulty.
l The BTS feeder is faulty.
Procedure
Step 1 If the configuration data of the failed cell and its neighboring cells is not modified recently, you
can infer that the BTS hardware is faulty.
l If the handover problem occurs in only one cell under this BTS, you can infer that a TRX
of the cell is faulty, which leads to a failure in handover to this TRX.
l If the handover problem occurs also in the neighboring cells on the same site, you can infer
that the hardware, such as the TMU, shared by the cells is faulty.
For the above problems, you can check them by blocking some TRXs. If the handover success
rate is within the allowed range after blocking a TRX, check whether this TRX is faulty or
whether the related CDU or feeder is faulty.
NOTE
If UL signals and DL signals on a TRX are very unbalanced, then handover problems, such as frequent
handovers or decreases in the handover success rate, may often occur.
Step 2 Trace the Abis interface to check whether the signaling related to this cell is normal, including
whether the UL and DL RX qualities are good. For detailed operations, refer to Tracing the
Messages on the Abis Interface.
If the measurement report shows that the TCHH Receive Level Measurement or TCHF
Receive Level Measurement is poor, you can infer that the hardware of this cell is faulty or
there is severe interference to this cell. Thus, signaling messages cannot be exchanged properly
and the handover cannot be performed successfully. For detailed operations, refer to 7.2.4
Troubleshooting Interference Problems.
----End
6.2.4 Troubleshooting Inter-BSC or Inter-MSC Handover Failures

This describes how to troubleshoot Inter-BSC or inter-MSC handover failures.
Possible Causes
The possible causes of inter-BSC and inter-MSC handover failures are as follows:
l The data configuration of the cells involved in inter-MSC handover is incorrect.
l The configuration data of the target cell for inter-BSC handover is incorrect.
l The MSC and the BSC process signaling messages on the A interface in different ways,
and therefore they fail to cooperate with each other.
l Clocks of the two BSCs are out of synchronization.
Procedure
Step 1 On the MSC side, check whether the configuration data, such as the CGI and owner, of the
involved cells is correct.

l If incorrect, modify it.

l If correct, go to Step 2.
Step 2 Check whether the neighboring cells are configured properly on the source BSC side and the
target BSC side.
l If incorrect, modify it by referring to Configuring the Handover.
l If correct, go to Step 3.
Step 3 Trace the signaling on the A interface by referring to Tracing the Messages on the A
Interface.
Check whether the signaling procedure between the source BSC and the MSC works well with
that between the MSC and the target BSC. For example, check whether there is an abnormal
handover release procedure performed by the MSC.
l If there is such a procedure, find out the specific cause and then rectify the fault. If the fault
is rectified, end the troubleshooting; otherwise, go to Step 4.
l If there is no such a procedure, go to Step 4.
Step 4 If the source or target BSC fails to lock the MSC clock, find out the cause and rectify the fault.
For detailed operations, refer to 5.2.1 Troubleshooting Clock Source Faults.
l If the fault is rectified, end the troubleshooting.
l If the fault persists, contact the Huawei Customer Service Center by referring to 1.3.1
----End
6.2.5 Troubleshooting Other Handover Faults

This describes how to troubleshoot other handover faults by analyzing traffic statistics in depth
and mastering the features of the handovers with high failure rates.
Possible Causes
The possible causes of other handover faults are cell congestion, poor quality of transmission
on the Um interface, and signaling problem on the A interface.
NOTE
The following procedure helps analyze configuration data in depth for troubleshooting.
Procedure
Step 1 Determine the type of handovers with high failure rates by referring to 6.1.3 Counters Related
to Handover Faults. The handover may be intra-cell handover, handover from a cell in the same
BSC, handover to a cell in the same BSC, handover from a cell in another BSC, handover to a
cell in another BSC, handover from a cell in another system, or handover to a cell in another
system.
Step 2 Based on the specific counter and signaling tracing result, find the cause of the handover fault.
Step 3 If the cause of the handover fault is still unclear, contact the Huawei Customer Service Center
by referring to 1.3.1 Obtaining Technical Support.
----End

BSS Troubleshooting Guide 7 Congestion Faults
7 Congestion Faults
About This Chapter
This describes congestion faults in terms of the symptoms, troubleshooting methods, and typical
cases.
7.1 Congestion Fault Symptoms

This describes the impacts of congestion faults on services, possible alarms, and involved
7.2 Congestion Troubleshooting Methods
This describes how to troubleshoot congestion faults. Basically, when a congestion fault occurs,
fault.
7.3 Typical Cases of Troubleshooting Congestion Faults

7 Congestion Faults BSS Troubleshooting Guide
7.1 Congestion Fault Symptoms

This describes the impacts of congestion faults on services, possible alarms, and involved
7.1.1 Impacts of Congestion Faults on Services

This describes the impacts of congestion faults on calls, SMSs, and BTS maintenance.
7.1.2 Alarms Related to Congestion Faults
This describes the alarms related to congestion faults. The alarms help locate and rectify the
faults.
7.1.3 Counters Related to Congestion Faults
This describes the counters related to congestion faults. The counters help locate and rectify the
faults.
7.1.1 Impacts of Congestion Faults on Services

This describes the impacts of congestion faults on calls, SMSs, and BTS maintenance.
When a congestion fault occurs, pages of the calling parties and the called parties cannot be
processed, SMSs cannot be sent or received, or the BTS cannot be maintained. Congestion
mainly occurs on the radio channels, Abis interface, and A interface.
7.1.2 Alarms Related to Congestion Faults

This describes the alarms related to congestion faults. The alarms help locate and rectify the
faults.
Alarms Related to BTS Congestion Faults

Table 7-1 lists the alarms related to BTS congestion faults.
Table 7-1 Alarms related to BTS congestion faults
The E1 transmission is faulty, or the congestion 21001 LAPD Link Congestion

start threshold and congestion end threshold of
LAPD links are set incorrectly.
The TRX incurs faults, which leads to the 2116 TRX Configuration Alarm
congestion of Um interface resources in peak
hours. 2148 TRX Hardware Alarm
2180 TRX Band Mismatch ARFCN
2196 TRX Clock Critical Alarm
2204 TRX Communication Alarm

Alarms Related to BSC Congestion Faults

Table 7-2 lists the alarms related to BSC congestion faults.
Table 7-2 Alarms related to BSC congestion faults
The E1 transmission on the A interface is faulty, 20082 Loss of E1/T1 Frames (LOF)
or the bit error rate is high (higher than 10-6), or
the number of configured signaling links is too 20089 Excessive Loss of E1/T1 Signals
small, which leads to the congestion or in an Hour
unavailability of MTP2 and MTP3 links. 20090 Excessive E1/T1
Synchronization Failures in an Hour
20093 E1/T1 Excessive Slip Frames Per

Hour
21502 MTP3 Layer 3 Congestion
21504 MTP3 Signaling Link2

Congestion
21503 MTP3 Link Unavailable
21513 MTP2 Link Location Failure
21514 MTP2 Link Service Disrupted
7.1.3 Counters Related to Congestion Faults

This describes the counters related to congestion faults. The counters help locate and rectify the
faults.
Table 7-3 lists the counters related to congestion faults.
Table 7-3 Counters related to congestion faults
Counter Description
H382A Failed Cell Incoming Handovers (Congestion)
A3050 Rejects to Service Requests (Congestion)
L6007 Duration of MTP3 Link Congestion
L6015 MTP3 Link Congestions
L6016 Discarded MSUs during Link Congestion
L3188G LOAD IND Messages Sent on the A Interface
R3202B TCH Assignment Requests (Underlaid Subcell

Preferred)

Counter Description
R3203B TCH Assignment Requests (Overlaid Subcell

Preferred)
R3202D Channel Assignment Requests in Incoming Internal

Inter-Cell Handover Procedure (TCH)(Underlaid
Subcell Preferred)
R3203D Channel Assignment Requests in Incoming Internal

Inter-Cell Handover Procedure (TCH) (Overlaid
Subcell Preferred)
R3202E Channel Assignment Requests in Incoming External

Inter-Cell Handover Procedure (TCH) (Underlaid
Subcell Preferred)
R3203E Channel Assignment Requests in Incoming External

Inter-Cell Handover Procedure (TCH) (Overlaid
Subcell Preferred)
R3225K Failed Handovers from Overlaid Subcell to

Underlaid Subcell due to Busy Channels in Underlaid
Subcell
R3162B Number of Failures to Allocate Abis Resources

(TCHF)

(TCHF)

(TCHF)
7.2 Congestion Troubleshooting Methods

This describes how to troubleshoot congestion faults. Basically, when a congestion fault occurs,
fault.
Procedure

Table 7-4 Congestion troubleshooting methods
On the M2000 Client, check the traffic on 7.2.1 Troubleshooting High Traffic
the SDCCH and TCH. The result shows
that the traffic exceeds the designed.
On the M2000 Client, check the traffic on 7.2.2 Troubleshooting Burst Traffic
the TCH. The result shows that the traffic
increases suddenly during a short period.
On the BSC6000 Local Maintenance 7.2.3 Troubleshooting TRX Faults

Terminal, check the running state of the
BTS. The result shows that a TRX is
faulty.
On the BSC6000 Local Maintenance 7.2.4 Troubleshooting Interference Problems

Terminal, check the channel interference
band. The result shows that interference is
existent.
On the BSC6000 Local Maintenance 7.2.5 Troubleshooting Insufficient

Terminal, check the circuit resource on Terrestrial Resources
the A interface. The result shows that the
configured circuits are insufficient or
some circuits are blocked or faulty.
On the BSC6000 Local Maintenance 7.2.6 Troubleshooting Insufficient Abis

Terminal, check the circuit resource on Resources
the Abis interface. The result shows that
the configured Abis timeslots are
insufficient or some Abis timeslots are
blocked or faulty.
Technical Support.
----End
7.2.1 Troubleshooting High Traffic

This describes how to troubleshoot high traffic. When a high traffic fault occurs, the query result
on the M2000 Client shows that the traffic on the TCH is obviously higher than the average.
Fault Symptoms
The symptoms of high traffic are as follows:
l The traffic in each of recent days is higher than the designed. On the M2000 Client, you
can obtain the Traffic Volume on TCH.
l More than 90% of the channel resource and circuit resource are occupied at traffic hours.
On the BSC6000 Local Maintenance Terminal, you can obtain the TCH status at peak

hours by referring to Monitoring Channel Status and the circuit resource usage on the A
interface by referring to Maintaining the Circuits on the A Interface.
Possible Causes
High traffic is possibly caused by too many subscribers.
Procedure
Expand the system capacity by referring to BSS Capacity Expansion Guide. Alternatively,
take traffic-sharing measures to relieve congestion.
----End
7.2.2 Troubleshooting Burst Traffic

This describes how to troubleshoot a sudden increase in traffic within a short period.
Fault Symptoms
The symptoms of burst traffic are as follows:
l More than 90% of the channel resource and circuit resource are occupied at traffic hours.
On the BSC6000 Local Maintenance Terminal, you can obtain the TCH status at peak
hours by referring to Monitoring Channel Status and the circuit resource usage on the A
interface by referring to Maintaining the Circuits on the A Interface.
l The circuit resource usage at peak hours is obviously higher than the average in the same
time segment on other days. You can obtain the Mean Number of Busy Circuits on the
A Interface at peak hours on the M2000 Client.
l Traffic in a time segment is obviously higher than that in other time segments of the day.
You can obtain the Traffic Volume on TCH on the M2000 Client.
Possible Cause
Burst traffic is possibly caused by a big event such as a football game or concert in an area within
a period.
Procedure
To relieve congestion in the case of burst traffic, do as follows:
l Enable some half-rate channels in this period to make more channels available. For detailed
operations, refer to Modifying Channel Attributes (Full Rate and Half Rate).
l Add SDCCHs in this period and enable dynamic conversion between SDCCH and TCH.
For detailed operations, refer to Modifying Channel Attributes (TCH and SDCCH).
----End
7.2.3 Troubleshooting TRX Faults

This describes how to troubleshoot TRX faults. When a TRX fault occurs, a TRX-related alarm
is reported.

Possible Causes
The possible causes of TRX faults are as follows:
l The TRX hardware is faulty.

l A failure occurs in transmission between the TRX and the BTS CDU, and a VSWR alarm
is reported.
l An LAPD link is faulty.
Procedure
Step 1 Rectify the fault according to the alarm help. The alarm reported may be 2116 TRX
Configuration Alarm, 2148 TRX Hardware Alarm, 2180 TRX Band Mismatch ARFCN,
2196 TRX Clock Critical Alarm, or 2204 TRX Communication Alarm.
l If the fault persists, go to Step 2.
Step 2 Check the status of the TRX.

1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, click
the corresponding BTS. A dialog box is displayed, as shown in Figure 7-1.
Figure 7-1 Site device panel
2. Determine the TRX status based on the description of the color on the right of Figure
7-1.

l If the TRX status is Error/Locked (Auto), you can infer that the BTS is not powered. Reset
and reload the TRX board.
l If the TRX status is not Error/Locked (Auto), go to Step 3.
Step 3 If the TRX fault cannot be confirmed, check the cable connections and VSWR of the antenna
system. For detailed operations, refer to Testing the Antenna System and Measuring the
VSWR at the Antenna Port. If all pass the check, replace the TRX board and then check the
services.
l If the services are restored, end the troubleshooting.
l If the services are not restored, contact the Huawei Customer Service Center by referring
to 1.3.1 Obtaining Technical Support.
----End
7.2.4 Troubleshooting Interference Problems

This describes how to troubleshoot interference problems. Interference can be detected through
dialing test on the Um interface or through monitoring of the channel interference band.
Fault Symptoms
The interference symptoms are as follows:
l The MS sends channel request messages to two cells each time the MS originates a call.
You can detect this symptom by making test calls and tracing signaling messages on the
Um interface on the BSC6000 Local Maintenance Terminal. For detailed operations,
refer to Tracing CS Domain Messages on the Um Interface.
This symptom indicates that the BCCHs in the two cells are configured with the same
frequency. Thus, in the cell that is selected by mistake, there are many invalid SDCCH
request messages, which leads to congestion. This symptom always occurs at peak hours.
l The level of interference including adjacent-channel interference is higher than the
expected. You can monitor the channel interference band on the BSC6000 Local
Maintenance Terminal. For detailed operations, refer to Monitoring Channel
Interference Band.
When this symptom occurs, the MS cannot receive the commands sent by the BSC and
therefore applies for channels repeatedly, which leads to congestion in the SDCCH or TCH,
especially at peak hours.
Possible Causes
The possible causes of interference are as follows:
l Intra-network interference
l Interference from repeaters
l Interference from other high-power communication equipment
l Hardware fault
Procedure
l For the first fault symptom, configure the BCCHs in the two cells with different frequencies
by referring to Modifying TRX Frequencies.

l For the second fault symptom, rectify the fault by referring to Analysis of Interference
Problems. Alternatively, adjust the frequency hopping mode by referring to Changing the
FH Mode.
----End
7.2.5 Troubleshooting Insufficient Terrestrial Resources

This describes how to troubleshoot insufficient terrestrial resources on the A interface that is not
based on IP. When the terrestrial resources are insufficient, the MS cannot originate a call.
Fault Symptoms
Many circuits are occupied or congested for a long time. You can check the status of the circuits
on the A interface on the BSC6000 Local Maintenance Terminal. For detailed operations,
refer to Maintaining the Circuits on the A Interface.
Possible Causes
The possible causes of insufficient terrestrial resources on the A interface that is not based on
IP are as follows:
l If many circuits are occupied for a long time, you can infer that the configured circuits are
insufficient.
l If the circuits are congested, you can infer that some circuits are blocked or faulty.
Procedure
To rectify the fault, do as follows:
l If many circuits are occupied for a long time, add E1s/T1s on the A interface.
– When the BM and the TC are configured in different subracks, operate according to
Adding an A Interface E1/T1.
– When the BM and the TC are configured in the same subrack, operate according to
Adding an A Interface E1/T1.
l If some circuits are blocked or faulty, do as follows:
– If some circuits are blocked, unblock them by referring to Unblock A Interface CIC
(UBL ACIC).
– If some circuits are faulty, you can infer that a fault occurs in transmission or the interface
board. In this case, operate according to 4.2.9 Troubleshooting E1/T1 Transmission
Faults.
----End
7.2.6 Troubleshooting Insufficient Abis Resources

This describes how to troubleshoot insufficient Abis resources, because of which no call can be
admitted.
Fault Symptoms
Many Abis timeslots are occupied for a long time, which you can check on the BSC6000 Local
Maintenance Terminal by referring to Querying the Status of the Abis Interface Timeslot.

Possible Causes
The possible cause of insufficient Abis resources is that the configuration is improper.
Procedure
To rectify the fault, do as follows:
l Adjust Abis timeslot assignment by referring to and Manually Assigning the Abis
Timeslots.
l Select the Abis Resource Adjustment TCHH Function Switch.
1. On the Management Tree tab page of the BSC6000 Local Maintenance
Terminal, right-click the cell and then select Configure Cell Attributes from the
shortcut menu.
2. Double-click the cell in the Cell view box to add it to the Selected cells box, and then
click Next.
3. Click Set Cell Properties. The Set Cell Attributes dialog box is displayed.
4. Click Call Control. A dialog box is displayed, as shown in Figure 7-2.
Set Abis Resource Adjustment TCHH Function Switch to Yes.
Figure 7-2 Setting Call Control Parameter dialog box
----End

7.3 Typical Cases of Troubleshooting Congestion Faults
7.3.1 Case: TCH Congestion Due to TRX Faults

This describes a typical case of troubleshooting the TCH congestion caused by TRX faults. The
TRX faults lead to the abnormal communication of the TRX board and the increase of TCH
congestion. To rectify the fault, reset or replace the TRX board.
7.3.2 Case: SDCCH Congestion Due to LAC Configuration Faults
This describes a typical case of troubleshooting the SDCCH congestion caused by LAC
configuration faults. To rectify the faults, you need to modify the LAC configuration.
7.3.1 Case: TCH Congestion Due to TRX Faults

This describes a typical case of troubleshooting the TCH congestion caused by TRX faults. The
TRX faults lead to the abnormal communication of the TRX board and the increase of TCH
congestion. To rectify the fault, reset or replace the TRX board.
Fault Symptoms
Query the alarm information and the result shows that the communication of some TRX boards
is abnormal. The traffic statistics information shows that the congestion rate on the TCH
increases.

During call setup, the faults in some TRX boards lead to the decrease of available TCH resources.
Especially in high traffic, a large number of Assignment Request messages are sent, which means
that the TCH resources are unavailable, and therefore the TCHs are shortly congested and paging
access fails.
1. To reset the TRX board, refer to Resetting a TRX.

l If the fault persists, go to 2.
2. Replace the TRX board.
7.3.2 Case: SDCCH Congestion Due to LAC Configuration Faults

This describes a typical case of troubleshooting the SDCCH congestion caused by LAC
configuration faults. To rectify the faults, you need to modify the LAC configuration.
Fault Symptoms
All the MSs in the cell fail to update locations. A large number of Location Updating Reject
messages are traced, which leads to the congestion on the SDCCH.

1. Check the LAC configuration between the MSC and the BSC. You can find the LAC
configuration is inconsistent between the two sides.

2. Modify the LAC configuration on the BSC side to keep it consistent with that on the MSC
side. For details, refer to Step 1 described in 8.2.2 Troubleshooting Data Configuration
Faults.

BSS Troubleshooting Guide 8 Access Faults
8 Access Faults
About This Chapter
This describes access faults in terms of the symptoms, troubleshooting methods, and typical
cases.
8.1 Access Fault Symptoms

This describes the impacts of access faults on services, possible alarms, and involved
8.2 Access Troubleshooting Methods
This describes how to troubleshoot access problems. Basically, when an access problem occurs,
fault.
8.3 Typical Cases of Troubleshooting Access Faults
This describes the typical cases of troubleshooting access faults.

8 Access Faults BSS Troubleshooting Guide
8.1 Access Fault Symptoms

This describes the impacts of access faults on services, possible alarms, and involved
8.1.1 Impacts of Access Faults on Services

This describes the impacts of access faults on services. When an access fault occurs, the MS
cannot receive radio signals or register with the network, the MS drops the call frequently, or
the MS cannot make calls or be called after the registration.
8.1.2 Alarms Related to Access Faults
This describes the alarms related to access faults. The alarms help locate and rectify the faults.
8.1.3 Counters Related to Access Faults
This describes the counters related to access faults. The counters help locate and rectify the
faults.
8.1.1 Impacts of Access Faults on Services

This describes the impacts of access faults on services. When an access fault occurs, the MS
cannot receive radio signals or register with the network, the MS drops the call frequently, or
the MS cannot make calls or be called after the registration.
8.1.2 Alarms Related to Access Faults

This describes the alarms related to access faults. The alarms help locate and rectify the faults.
Table 8-1 lists the alarms related to access faults.
Table 8-1 Alarms related to access faults

Link faults 1000 LAPD OML Fault
103 All SS7 Links Faulty
21525 SCCP DSP Unreachable
Equipment faults 4732 TMU clock critical alarm
5298 CDU VSWR Critical Alarm
4192 TRX communication alarm
2148 TRX Hardware Alarm
21210 CPU Overload
405 Cell Out of Service

8.1.3 Counters Related to Access Faults

This describes the counters related to access faults. The counters help locate and rectify the
faults.
Table 8-2 lists the counters related to access faults.
Table 8-2 Counters related to access faults

Counter Description
CA300J Channel Requests (Circuit Service)
A300H Channel Requests (Packet Call)
A301H Immediate Assignment Commands (PS)
A3010 Immediate Assignment Commands (SDCCH)
A3017 Immediate Assignment Commands (TCHF)
A3018 Immediate Assignment Commands (TCHH)
CA301J Immediate Assignment Commands (Circuit Service)
A301B Immediate Assignment Commands (Non-Call Type)
A301A Immediate Assignment Commands (Call Type)
A302J Rejects to Immediate Assignments (CS)
A302H Rejects to Immediate Assignments (PS)
A3030 Call Setup Indications (SDCCH)
CA3030J Call Setup Indications (SDCCH) (Circuit Service)
CA3039J Call Setup Indications (TCH) (Circuit Service)
A3037 Call Setup Indications (TCHF)
A3038 Call Setup Indications (TCHH)
CA303J Call Setup Indications (Circuit Service)
CA303B Call Setup Indications (Non-Call Type)
CA303H Call Setup Indications (Packet Service)
CA303A Call Setup Indications (Call Type)
CA304 Call Setup Indications Timed Out
CA305 Rejects to Service Requests

8.2 Access Troubleshooting Methods

This describes how to troubleshoot access problems. Basically, when an access problem occurs,
fault.
Procedure
Table 8-3 Access troubleshooting methods
l The number of channel requests is 8.2.1 Troubleshooting Um Interface Quality

smaller than a preset value. Problems
l The number of setup indications is
smaller than a preset value.
l The immediate assignment success rate
is lower than a preset value.
l The call drop rate of the SDCCH is
higher than a preset value.
l The MSC rejects the service request 8.2.2 Troubleshooting Data Configuration
from the MS. Faults
l The number of expirations of the setup
indication timer is larger than a preset
value.
l The immediate assignment success rate
is lower than a preset value.
l The congestion rate of the SDCCH is
higher than a preset value.
l The paging success rate is lower than a
preset value.
A link fault alarm is reported. 4 Link Faults
Technical Support.
----End
8.2.1 Troubleshooting Um Interface Quality Problems

This describes how to troubleshoot Um interface quality problems, because of which the MS
cannot receive signals or the received signals are unstable.

Possible Causes
The possible causes of Um interface quality problems are as follows:
l The equipment is faulty or the network planning is improper. In this case, the coverage of
the network is unsatisfied.
l UL and DL signals are unbalanced on the Um interface, or UL signals are greatly affected
by interference.
Procedure
Step 1 Check whether the equipment is faulty.
On the BSC6000 Local Maintenance Terminal, check the kickoff status of the cell and the
status of each board of the BTS in the Figure 8-1 dialog box. For detailed operations, refer to
Querying BTS Attributes.
Figure 8-1 Check the kickoff status of the cell
If the Operation status is Enabled, check whether each board of the BTS is faulty.
l If faulty, replace the board and the antenna.

Step 2 Check the relevant parameter settings.

click the TRX and then select Configure TRX Attributes from the shortcut menu.
2. In the displayed TRX attribute configuration wizard dialog box, click Configure TRX
Attributes.

3. In the displayed dialog box, select the Device Attributes tab page, as shown in Figure
8-2.
Figure 8-2 Configure TRX Attributes dialog box
Set the Power Level to adjust the TRX power, thus solving the problem of unbalancing between
UL and DL signals.
CAUTION
A higher power level indicates a lower power value. Power level 0 indicates the maximum power
value.

Step 3 Perform frequency scanning and reselect the BCCH frequency for the cell.
1. On the BSC6000 Local Maintenance Terminal, perform frequency scanning to determine
the interference to each frequency. Select a frequency with the lowest interference as the
BCCH frequency. For detailed operations, refer to Configuring Frequency Scan. For the
configuration dialog box, see Figure 8-3.

Figure 8-3 Configure Frequency Scan dialog box
2. After you click Start in the dialog box as shown in Figure 8-3, the BTS starts to scan
frequencies 512 to 517 at the specified time.
On the BSC6000 Local Maintenance Terminal, the frequency scanning result shows the
interference to each frequency in the uplink. The smaller the value, the lower the
interference. For detailed operations, refer to Querying Frequency Scan Results.
Select an idle frequency with the lowest interference as the BCCH frequency of the cell.
CAUTION
After the frequency scanning task is complete, click Stop in the Configure Frequency
Scan dialog box. Otherwise, the BTS scans these frequencies once every day.

----End
8.2.2 Troubleshooting Data Configuration Faults

This describes how to troubleshoot the faults in data configuration. The fault symptoms show
that all the MSs in the cell fail to register in the network, a large number of MSC-rejected services
occur in traffic statistics, the uplink and downlink signals on the Um interface are unbalanced,
or the uplink signals interfere strongly.
Possible Causes
The possible causes are as follows:

l The data configuration is inconsistent between the BSC and the MSC.
l The cell-related parameters are not properly set.
Procedure
Step 1 Check whether the data configuration is inconsistent between the BSC and the MSC.
Determine the fault coverage, that is, whether the fault occurs in all the cells or only a few cells
in the coverage of the BSC.
l If the fault occurs in all the cells in the coverage of the BSC, check the global configuration
data as follows:
– When the BM and the TC are configured in different subracks, see Configuring the
BSC Attributes for details.
– When the BM and the TC are configured in the same subrack, see Configuring the
BSC Attributes for details.
– When the A interface uses the IP transmission mode, see Configuring the BSC
Attributes for details.
l If the fault occurs in a few cells in the coverage of the BSC, check the configuration data
of specified cells as follows:
1. On the BSC6000 Local Maintenance Terminal, right-click a cell on the
Management Tree tab page. Then, choose Configure Cell Attributes.
2. On the Configure Cell Attributes dialog box, select the cell, and click Next.
3. Click Configure Cell Attributes. In the displayed Set Cell Attributes dialog box,
check the following parameters: MCC, MNC, LAC, and CI, as shown in Figure
8-4.

Figure 8-4 Set Cell Attributes dialog box
CAUTION
The parameter configuration mentioned above must be kept consistent between the BSC and the
MSC.
l If the configuration is inconsistent, modify the parameters to keep them consistent.

l If the configuration is consistent, go to Step 2.
Step 2 Check whether the cell access parameters are set properly.
If the access fault occurs in a few cells but not because the MSC rejects services, check whether
the cell access parameters are set properly, and verify the parameters related to the cells in idle
mode and the cell timer, as shown in Figure 8-5 and Figure 8-6.

Figure 8-5 Parameters related to the cells in idle mode
Figure 8-6 Parameters related to the cell timer
l If the fault persists after the parameters are set correctly, contact the Huawei Customer
l If the parameters are set incorrectly, reconfigure the parameters. If the fault persists after
reconfiguration, contact the Huawei Customer Service Center by referring to 1.3.1
----End

8.3 Typical Cases of Troubleshooting Access Faults

This describes the typical cases of troubleshooting access faults.
8.3.1 Case: MS Access Failure Due to Weak Signals

This describes a typical case of troubleshooting the MS access failure due to weak signals. The
MS fails to access the network because the signals are weak. To solve the problem, you can
check the cell coverage and tilt the antenna.
8.3.2 Case: MS Cell Reselection Failure Due to Weak Signals of Neighboring Cells
This describes a typical case of troubleshooting the MS cell reselection failure. The MS fails to
perform cell reselection because the signals in the neighboring cells are weak. To solve the
problem, you can check the data configuration, adjust the power level, or tilt the antenna.
8.3.3 Case: MS Network Disconnection Due to Location Update Period Set Too Small
This describes a typical case of troubleshooting the MS network connection failure. The MS is
disconnected from the network because the location update period is set too small. To solve the
problem, you need to modify related parameters.
8.3.4 Case: MS Network Disconnection Due to Incorrect CGI Configuration
This describes a typical case of troubleshooting the MS network connection failure due to
incorrect CGI configuration. To solve the problem, you can modify the CGI parameters.
8.3.5 Case: MS Access Failure Due to Incorrect CBQ/CBA Setting
This describes a typical case of troubleshooting the MS access failure due to the incorrect CBQ/
CBA setting. To solve the problem, you can modify the related parameters.
8.3.6 Case: MS Access Failure Due to Incorrect Setting of Minimum RACH Access Level
This describes a typical case of troubleshooting the MS access failure due to the incorrect setting
of the minimum RACH access level. To solve the problem, you must modify the related
parameters.
8.3.1 Case: MS Access Failure Due to Weak Signals

This describes a typical case of troubleshooting the MS access failure due to weak signals. The
MS fails to access the network because the signals are weak. To solve the problem, you can
check the cell coverage and tilt the antenna.
Fault Symptoms
The MS is located in the poor coverage of signals and thus fails to access the network due to
weak signals.

1. Check the cell coverage and determine whether the MS is located at the edge of a cell. If
not, go to 2.
2. Reduce the power level of the BCCH TRX of the cell.
3. Check whether the height, location, and azimuth of the antenna are set properly. If not,
adjust them.
4. After adjustment, the MS in its original location can access the network normally.

8.3.2 Case: MS Cell Reselection Failure Due to Weak Signals of

Neighboring Cells
This describes a typical case of troubleshooting the MS cell reselection failure. The MS fails to
perform cell reselection because the signals in the neighboring cells are weak. To solve the
problem, you can check the data configuration, adjust the power level, or tilt the antenna.
Fault Symptoms
The MS in idle mode fails to perform cell reselection. It incurs a call drop first and then registers
in the network.

1. Check whether the neighboring cell mapping data is correct.
2. Check whether the level signal of the neighboring cell is weak. If so, reduce the power level
of the BCCH TRX of the neighboring cell.
3. Check whether the height, location, and azimuth of the neighboring BTS are set properly.
If not, adjust them.
4. Increase the height of the antenna to strengthen the signals of neighboring cells.
5. If the fault persists, set the cell of the non-neighboring BTS as a neighboring cell and
enhance the redundancy of neighboring cells until the MS can perform cell reselection
normally.
6. After the previous adjustment, the MS in idle mode performs cell reselection successfully
and incurs no call drops.
8.3.3 Case: MS Network Disconnection Due to Location Update

Period Set Too Small
This describes a typical case of troubleshooting the MS network connection failure. The MS is
disconnected from the network because the location update period is set too small. To solve the
problem, you need to modify related parameters.
Fault Symptoms
An office has four BTSs, and the network runs normally. One day, however, the MSs are
suddenly disconnected from the network.

1. Check the hardware.
l Check whether the BTS equipment reports alarms. For details, see 8.1.2 Alarms
Related to Access Faults.
l On the BSC6000 Local Maintenance Terminal, check whether all the BSC boards
run normally.
If no alarms are reported or no hardware is faulty, then the BTS hardware has no problem.
2. Check the configuration data.
Recently, the office has no configuration data modified but only the number of MSs greatly
increases. According to the VLR, the number of local MSs is over 4000 and the number of

roaming MSs is more than 5000. The problem may be caused by the sharp increase of MSs,
which burdens the network in the following aspects:
l High TCH congestion rate
If all the TCHs in some areas are occupied, then other MSs cannot make calls.
l High SDCCH congestion rate
If all the SDCCHs in some areas are occupied, then the MSs cannot perform signaling
interaction. In addition, the MSs can neither make or receive calls nor perform location
update, and the location update failure directly leads to MS disconnection from the
network.
3. Check the BSC idle parameters.
The time of periodic location update is set to 12 minutes for the BSC and 30 minutes for
the MSC. The setting means that all the activated MSs initiate a periodic location update
to the SDCCH every 12 minutes. When the number of MSs reaches a certain level, all the
SDCCHs are occupied. At this time, if the MSs initiate the periodic location update again,
the MSs may fail the location update because there are no idle SDCCHs and thus the MSs
will be disconnected from the network.
4. Modify the configuration data.
On the BSC6000 Local Maintenance Terminal, set Period of Periodic Location Update
(6 minutes) to 10, that is, 60 minutes. For details, refer to Step 2 described in 8.2.2
Troubleshooting Data Configuration Faults. In addition, set the period for the MSC to
180 minutes.
8.3.4 Case: MS Network Disconnection Due to Incorrect CGI

Configuration
This describes a typical case of troubleshooting the MS network connection failure due to
incorrect CGI configuration. To solve the problem, you can modify the CGI parameters.
Fault Symptoms
The MS can receive the signals from the BTS but cannot access the network.

1. On the BSC6000 Local Maintenance Terminal, query the status of TRXs and channels.
The TRXs, channels, and the A interface are all normal, but the MS cannot access the
network. Also, the MS sends the location update failure message. For details, refer to
Querying BTS Running Status and Maintaining the Circuits on the A Interface.
The probable cause is that the CGI configuration is inconsistent between the MSC side and
the BSC side.
2. Check the CGI parameter configuration on the BSC side. For details, refer to Step 1
described in 8.2.2 Troubleshooting Data Configuration Faults.
3. Modify the CGI configuration to keep the parameters consistent between the MSC side and
the BSC side. The MS can access the network after the CGI configuration is kept consistent
between the two sides.
8.3.5 Case: MS Access Failure Due to Incorrect CBQ/CBA Setting

This describes a typical case of troubleshooting the MS access failure due to the incorrect CBQ/
CBA setting. To solve the problem, you can modify the related parameters.

Fault Symptoms
The fault symptoms of the MS access failure are as follows:
l The MS displays that it fails to search the network, or the MS displays no information.
l The MS displays that the network list contains no originating network.

1. Check the cell data configuration. For details, refer to Step 2 described in 8.2.2
Troubleshooting Data Configuration Faults.
The parameters Cell_Bar_Access (CBA) and Cell_Bar_Access (CBQ) affect the cell
reselection of the MS.
2. Reset the CBQ and CBA according to the priorities of cell selection and reselection.
3. After the related parameters are modified, the MS can select or reselect the cell normally.
8.3.6 Case: MS Access Failure Due to Incorrect Setting of Minimum

RACH Access Level
This describes a typical case of troubleshooting the MS access failure due to the incorrect setting
of the minimum RACH access level. To solve the problem, you must modify the related
parameters.
Fault Symptoms
The fault symptoms are as follows:
l The MS displays that it fails to search the network, or the MS displays no information.
l The MS searches one or more networks.
l Most of the MSs cannot access the cell.
l No request message is available on the Abis interface.

1. Check the data configuration of the cell. The result shows that the RACH Min. Access
Level is set incorrectly.
RACH Min. Access Level refers to the level threshold for the random access of the MS
to the BTS. When the random access level of the burst timeslot is greater than the value of
RACH Min. Access Level, the BTS considers that the timeslot has an access request, and
determines together with the value of Random Access Error Threshold whether the
RACH access is valid.
2. According to the BTS sensitivity and the MS minimum access level, you can modify the
RACH Min. Access Level parameter and perform the following operations:
(1) On the BSC6000 Local Maintenance Terminal, right-click a cell on the
Management Tree tab page. Then, choose Configure Cell Attributes.
(2) On the Configure Cell Attributes dialog box, select the cell, and click Next.
(3) Click Set Cell Properties. The dialog box Set Cell Attributes is displayed. Click
Call Control. A dialog box is displayed. Click Advanced. A dialog box is displayed,
as shown in Figure 8-7.

Figure 8-7 Call Control dialog box
3. The MS can access the network normally after the parameter is modified.

BSS Troubleshooting Guide 9 PS Service Faults
9 PS Service Faults
About This Chapter
This describes PS service faults in terms of the symptoms, troubleshooting methods, and typical
cases.
9.1 PS Service Fault Symptoms

This describes the impacts of PS service faults on services, possible alarms, and involved
9.2 PS Service Troubleshooting Methods
This describes how to troubleshoot different PS service faults. Basically, when a PS service fault
rectify the fault.
9.3 Typical Cases of Troubleshooting PS Service Faults
This describes the typical cases of troubleshooting PS service faults.

9 PS Service Faults BSS Troubleshooting Guide
9.1 PS Service Fault Symptoms

This describes the impacts of PS service faults on services, possible alarms, and involved
9.1.1 Impacts of PS Service Faults on Services

This describes the impacts of PS service faults on services. When a PS service fault occurs, the
MS cannot access the GPRS network or the MS cannot obtain GPRS services although it can
access the GPRS network.
9.1.2 Alarms Related to PS Service Faults
This describes the BSS alarms related to PS service faults. The alarms help locate and rectify
the faults.
9.1.3 Counters Related to PS Service Faults
This describes the counters related to PS service faults. The counters help locate and rectify the
faults.
9.1.1 Impacts of PS Service Faults on Services

This describes the impacts of PS service faults on services. When a PS service fault occurs, the
MS cannot access the GPRS network or the MS cannot obtain GPRS services although it can
access the GPRS network.
9.1.2 Alarms Related to PS Service Faults

This describes the BSS alarms related to PS service faults. The alarms help locate and rectify
the faults.
Table 9-1 lists the alarms related to the PS service faults in the case of using the external PCU.
Table 9-1 Alarms related to PS service faults (external PCU)
The congestion start threshold and the 21001 LAPD Link Congestion
congestion end threshold of the LAPD links
on the Pb interface are improperly set, or the
LAPD signaling load exceeds the congestion
start threshold of the LAPD links.
The LAPD link on the Pb interface cannot 21002 Broken LAPD Link
receive any messages from the peer end
(PCU).
The E1 transmission is faulty on the Pb 20082 Loss of E1/T1 Frames (LOF)

interface and the bit error rate is high (higher
than 10-6). 20089 Excessive Loss of E1/T1 Signals in
an Hour

Failures in an Hour

20093 E1/T1 Excessive Slip Frames Per

Hour
All the PBSLs between the BSC and the PCU 104 All PBSLs in the PCU Are Faulty
are faulty.
The one-way audio occurs in a PBSL between 105 ONE PBSL Link SINGLE PASS
the BSC and the PCU.
The circuit with an alarm flag is not 127 No Pb Interface Circuit Configured on
configured on the BSC side but on the PCU the BSC side
side.
The circuit with an alarm flag is not 128 No Circuit Configured in the PCU
configured on the PCU side but on the BSC
side.
The BSC sends the PCU the message 134 BSC Unable to Block a Packet Circuit
indicating that the BSC blocks the circuit with
maximum retransmissions, but the PCU does
not respond to the messages.
The BSC sends the PCU the message that the 135 BSC Unable to Unblock a Packet
BSC unblocks the circuit PCU with Circuit
The BSC sends the PCU the message 136 BSC Unable to Reset a Packet Circuit
indicating that the BSC resets the circuit with
Table 9-2 lists the alarms related to the PS service faults in the case of using the built-in PCU.
Table 9-2 Alarms related to PS service faults (built-in PCU)

The delay of the transmission between BTS and BSC in 291 Cell Transmission Delay
the cell is below the lower limit or above the upper limit. Abnormal
The Gb interface is inaccessible, or the Gb data 293 GB BC Faulty

configuration is incorrect, or the bearer channel is
blocked.
The BSC supports GPRS/EGPRS but the actual BTS 294 TRX Config Error
TRXs do not support GPRS/EGPRS.
The GEPUG is faulty, or the NSVC is blocked, or the 331 NSVC Faulty
bearer channel is inaccessible, or the data configuration
is inconsistent between BSC and SGSN.

The GFGUG is faulty, or the network between BSC and 332 NSVL Faulty
SGSN is disconnected, or the data configuration is
inconsistent between BSC and SGSN.
The Gb interface works abnormally. 333 NSE Faulty
The cell distribution fails or is prohibited by the license, 340 Cell PS Service Faulty
or the Um or Gb interface is blocked.
The cell distribution on the DSP exceeds the upper limit. 341 DSP Resource Overload
The PTP BVC signaling flow is abnormal, or the PTP 342 PTP BVC Faulty
BVC is blocked.
The communication link between BSC and SGSN is 343 NSVL Dynamic
faulty, or the data configuration of the SERVER IP/UDP Configuration Process Failure
port is inconsistent between BSC and SGSN.
Among the 22 DSPs of the GDPUP, the redundant 16 344 FAULTY DSP OVER
DSPs are faulty. LIMIT
9.1.3 Counters Related to PS Service Faults

This describes the counters related to PS service faults. The counters help locate and rectify the
faults.
Table 9-3 lists the counters related to PS service faults in the case of using the external PCU.
Table 9-3 Counters related to PS service faults (external PCU)

Counter Description
AL8351 Mean Number of Faulty Circuits on the Pb Interface
AL8353 Mean Number of Blocked Circuits on the Pb Interface
AL8354 Mean Number of Idle Circuits on the Pb Interface
AL8355 Mean Number of Busy Circuits on the Pb Interface
AL8352 Mean Number of Circuits in Maintenance State on the Pb

Interface
R3001A Number of Initially Configured Channels (Static PDCH)

(900/850 Cell)
R3001B Number of Initially Configured Channels (Static PDCH)

(1800/1900 Cell)
R3002A Number of Initially Configured Channels (Dynamic

PDCH) (900/850 Cell)

Counter Description
R3002B Number of Initially Configured Channels (Dynamic

PDCH) (1800/1900 Cell)
R3005A Number of Initially Configured Channels (Static EDGE)

(900/850 Cell)
R3005B Number of Initially Configured Channels (Static EDGE)

(1800/1900 Cell)
R3006A Number of Initially Configured Channels (Dynamic

EDGE) (900/850 Cell)
R3006B Number of Initially Configured Channels (Dynamic

EDGE) (1800/1900 Cell)
AR3011A Mean Number of Dynamically Configured Channels

(PDCH) (900/850 Cell)
AR3011B Mean Number of Dynamically Configured Channels

(PDCH) (1800/1900 Cell)
AR3015A Mean Number of Dynamically Configured Channels

(EDGE) (900/850 Cell)
AR3015B Mean Number of Dynamically Configured Channels

(EDGE) (1800/1900 Cell)
AR3021A Mean Number of Available Channels (PDCH) (900/850

Cell)
AR3021B Mean Number of Available Channels (PDCH) (1800/1900

Cell)
AR3025A Mean Number of Available Channels (EDGE) (900/850

Cell)
AR3025B Mean Number of Available Channels (EDGE) (1800/1900

Cell)
AR3023A Mean Number of Available Channels (TCHs Converted

from Dynamic PDCHs) (900/850 Cell)
AR3023B Mean Number of Available Channels (TCHs Converted

AR3024A Mean Number of Available Channels (PDCHs Converted

AR3024B Mean Number of Available Channels (PDCHs Converted

L0387 Total Number of Messages Received from PCU
L8387 Messages Received from a PCU
R3140 Requests for TCH from the PCU

Counter Description
R3141 Successful Requests for TCH from the PCU
A031 SGSN-Initiated Paging Requests for PS Service
A331 SGSN-Initiated Paging Requests for PS Service
A300H Channel Requests (Packet Call)
A301H Immediate Assignment Commands (PS Service)
A302H Rejects to Immediate Assignments (PS Service)
A3030H Call Setup Indications (PS Service) (SDCCH)
A3037H Call Setup Indications (PS Service) (TCHF)
A3038H Call Setup Indications (PS Service) (TCHH)
CA303H Call Setup Indications (Packet Service)
Table 9-4 lists the counters related to PS service faults in the case of using the built-in PCU.
Table 9-4 Counters related to PS service faults (built-in PCU)

Counter Description
A9406 Number of 11-Bit Single Block Channel

Requests Received on RACH
AA9407 Average Interval of Packet Access

Requests on CCCH (s)
A9408 Number of Packet Channel Requests

Received on PCCCH
AA9409 Average Interval of Packet Access

Requests on PCCCH(s)
A9410 Number of Resource Requests Received on

Uplink PACCH
A9411 Number of Resource Requests Received on

Downlink PACCH
A9501 Number of Uplink Assignments
A9502 Number of Successful Uplink Assignments
A9503 Number of Uplink PS Immediate

Assignments
A9504 Number of Successful Uplink PS

Immediate Assignments

Counter Description
A9505 Number of Uplink Assignments on

PACCH
A9506 Number of Successful Uplink Assignments

on PACCH
A9507 Number of Downlink Assignments
A9508 Number of Successful Downlink

Assignments
A9509 Number of Downlink PS Immediate

Assignments
A9510 Number of Successful Downlink PS

Immediate Assignments
A9511 Number of Downlink Assignments on

PACCH
A9512 Number of Successful Downlink

Assignments on PACCH
A9001 Number of Uplink GPRS TBF

Establishment Attempts
A9002 Number of Successful Uplink GPRS TBF

Establishments
A9003 Number of Failed Uplink GPRS TBF

Establishments due to No Channel
A9004 Number of Failed Uplink GPRS TBF

Establishments due to MS No Response
A9005 Number of Uplink GPRS TBF Normal

Releases
A9006 Number of Uplink GPRS TBF Abnormal

Releases due to N3101 Overflow (MS No
Response)

Response)

Releases due to SUSPEND

Releases due to FLUSH

Releases due to No Channel

Counter Description
A9011 Total Number of Sampled Concurrent

Uplink GPRS TBFs
A9012 Sampling Times of Concurrent Uplink

GPRS TBFs
A9013 Average Number of Concurrent Uplink

GPRS TBFs
A9014 Total Duration of Uplink GPRS TBF (ms)
A9015 Average Duration of Uplink GPRS TBF (s)
A9101 Number of Downlink GPRS TBF

A9102 Number of Successful Downlink GPRS

TBF Establishments
A9103 Number of Failed Downlink GPRS TBF

A9104 Number of Failed Downlink GPRS TBF

A9105 Number of Downlink GPRS TBF Normal

Releases

Abnormal Releases due to N3105 Overflow

Abnormal Releases due to SUSPEND

Abnormal Releases due to FLUSH

Abnormal Releases due to No Channel

Downlink GPRS TBFs
A9111 Sampling Times of Concurrent Downlink

GPRS TBFs
A9112 Average Number of Concurrent Downlink

GPRS TBFs
A9113 Total Duration of Downlink GPRS TBF

(ms)
A9114 Average Duration of Downlink GPRS TBF

(s)

Counter Description
A9201 Number of Uplink EGPRS TBF

A9202 Number of Successful Uplink EGPRS TBF

Establishments
A9203 Number of Failed Uplink EGPRS TBF

A9204 Number of Failed Uplink EGPRS TBF

A9205 Number of Uplink EGPRS TBF Normal

Releases
A9206 Number of Uplink EGPRS TBF Abnormal

Response)

Response)

Releases due to SUSPEND

Releases due to FLUSH

Releases due to No Channel

Uplink EGPRS TBFs
A9212 Sampling Times of Concurrent Uplink

EGPRS TBFs
A9213 Average Number of Concurrent Uplink

GPRS TBFs
A9214 Total Duration of Uplink EGPRS TBF

(ms)
A9215 Average Duration of Uplink EGPRS TBF

(s)
A9301 Number of Downlink EGPRS TBF

A9302 Number of Successful Downlink EGPRS

TBF Establishments
A9303 Number of Failed Downlink EGPRS TBF


Counter Description
A9304 Number of Failed Downlink EGPRS TBF

A9305 Number of Downlink EGPRS TBF Normal

Releases

Abnormal Releases due to N3105 Overflow

Abnormal Releases due to SUSPEND

Abnormal Releases due to FLUSH

Abnormal Releases due to No Channel

Downlink EGPRS TBFs
A9311 Sampling Times of Concurrent Downlink

EGPRS TBFs
A9312 Average Number of Concurrent Downlink

EGPRS TBFs
A9313 Total Duration of Downlink EGPRS TBF

(ms)
A9314 Average Duration of Downlink EGPRS

TBF (s)
R9201 Number of RLC Data Blocks Used on

PDCH
R9202 Total Number of RLC Data Blocks on

PDCH
RR9203 Average PDCH Utilization (%)
L9601 Number of Frames Sent on BC
L9602 Number of Frames Received on BC
L9603 Number of Frames Discarded on BC
L9604 Peak Bytes of NS PDUs Sent on BC
L9605 Peak Bytes of NS PDUs Received on BC
L9701 Number of NS PDUs Sent by NS sublayer

(NSVC)
L9702 Number of NS PDUs Received by NS

Sublayer (NSVC)

Counter Description
L9703 Number of NS PDUs Discarded by NS

Sublayer (NSVC)
L9704 Total Bytes of NS PDUs Sent by NS

Sublayer (NSVC)
L9705 Total Bytes of NS PDUs Received by NS

Sublayer (NSVC)
R9401 Total Sampled DSP CPU Usage
R9402 Sampling Times of DSP CPU Usage
AR9403 Average DSP CPU Usage (%)
R9404 Peak DSP CPU Usage (%)
R9501 Maximum Number of PDCHs Activated

on DSP
R9502 Minimum Number of PDCHs Activated on

DSP
R9503 Total Number of Sampled PDCHs

Activated on DSP
R9504 Sampling Times of PDCH Measurement

on DSP
AR9505 Average Number of PDCHs Activated on

DSP
R9506 Maximum Number of PDCHs Occupied

on DSP
R9507 Minimum Number of PDCHs Occupied on

DSP
R9508 Total Number of Sampled PDCHs

Occupied on DSP
AR9509 Average Number of PDCHs Occupied on

DSP
S9201 Maximum Number of PDCHs Assigned

per BSC
S9202 Total Number of Sampled PDCHs

Assigned per BSC
S9203 Sampling Times of PDCHs Assigned per

BSC
AS9204 Average Number of PDCHs Assigned per

BSC

Counter Description
S9205 Maximum Speed of PS Traffic per BSC

(kbit/s)
S9206 Number of Failed PDCH Assignments due

to Congestion
9.2 PS Service Troubleshooting Methods

This describes how to troubleshoot different PS service faults. Basically, when a PS service fault
rectify the fault.
Procedure
Table 9-5 PS service troubleshooting methods

On the BSC6000 Local Maintenance 9.2.1 Troubleshooting a Cell Not Supporting

Terminal, find that the GPRS Support GPRS
check box is not selected.
On the external PCU LocalWS, check the 9.2.2 Troubleshooting Cell Faults (External
cell status. The result shows that a cell PCU)
malfunctions.
On the external PCU LocalWS, trace the 9.2.3 Troubleshooting Cell Kickoff Failures
messages on the Pb interface and run a cell (External PCU)
reset command. The result shows that a cell
fails to start work.
NOTE
Resetting a cell causes the cell out of service.
Perform this operation only when the cell cannot
offer services properly.
On the external PCU LocalWS, check the 9.2.4 Troubleshooting PDCH Faults
PDCH status. The result shows that a (External PCU)
PDCH malfunctions.
Check the status of LAPD links on the Pb 9.2.5 Troubleshooting LAPD Link Faults
interface. The result shows that an LAPD (External PCU)
link malfunctions.

On the M2000 Client or BSC6000 Local 9.2.6 Troubleshooting Cell Activity State
Maintenance Terminal, check the cell Faults (Built-in PCU)
configurations, physical connections, and
port parameter settings.
NOTE
Resetting a cell causes the cell out of service.
Perform this operation only when the cell cannot
offer services properly.
Find that an MS or a cell cannot perform PS 9.2.7 Troubleshooting Cell Service

services properly. Disruption Faults (Built-in PCU)
Find that the PCU is running properly but 9.2.8 Troubleshooting Global Service
all the ongoing services are disrupted Disruption Faults (Built-in PCU)
suddenly.
NOTE
For details on the PCU commands, refer to 9.2.9 Commands Executed on the PCU Maintenance
Terminal.
Technical Support.
----End
9.2.1 Troubleshooting a Cell Not Supporting GPRS

This describes how to troubleshoot the problem that the MS cannot perform PS services in a
cell.
Possible Causes
The possible cause of a cell not supporting GPRS is that the cell is configured not to support
GPRS. In this case, the system information issued by the BTS does not carry any PS-related
information, and therefore the MS cannot perform PS services in the cell.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, click the
cell and check the cell attributes, as shown in Figure 9-1.

Figure 9-1 Cell attributes
Step 2 On the Cell Attributes tab page, check whether the GPRS Support check box is selected. If it
is not selected, the cell cannot support GPRS.
To enable the cell to support GPRS, select the GPRS Support check box and ensure that the
cell is configured with PDCHs.
----End
9.2.2 Troubleshooting Cell Faults (External PCU)

This describes how to troubleshoot a cell in a malfunctioning state on the external PCU side.
Fault Symptoms
The cell fault symptoms on the external PCU side are as follows:
l The cell has an internal fault, the cell resources are not ready, the equipment is not
initialized, the cell does not support GPRS, the cell does not exist, or the data configuration
of the cell is incorrect.
l If the BSC administrative status of the cell is BLOCKED.
Procedure
On the PCU LocalWS, check the cell status.

NOTE
Terminal.
l If the cell status is Internal fault, do as follows:
1. On the PCU LocalWS, check the CGI of the cell.
2. On the BSC6000 Local Maintenance Terminal, check the MCC, MNC, LAC, and
CI. For detailed operations, refer to Step 1 of 8.2.2 Troubleshooting Data
Configuration Faults.
NOTE
The CI can be displayed in decimal or hexadecimal mode. Set the Cell LAC&CI&RA display
mode to Decimal or Hexadecimal. For detailed operations, refer to Setting Attributes of the
BSC6000 Local Maintenance Terminal. The LAC and CI in the CGI are displayed in
hexadecimal mode.
3. Check whether the CGI on the PCU side is consistent with that on the BSC side.
– In consistent, end the troubleshooting.
– If inconsistent, modify the CGI on the PCU LocalWS or BSC6000 Local
Maintenance Terminal.
l If the cell status is Dependency, do as follows:
Select PBSL from the LAPD Link No. Scope area to check the status of the PBSL on the
BSC side. For detailed operations, refer to Maintaining LAPD Links.
If the State of the PBSL is Failure, rectify the fault by referring to 9.2.5 Troubleshooting
LAPD Link Faults (External PCU).
l If the cell status is Device has not been initialized, do as follows:
1. On the BSC side, check the status of the TRXs configured for the cell.
a. On the Management Tree tab page of the BSC6000 Local Maintenance
Terminal, select a TRX. Then, check the related information on the Site Device
Panel, as shown in Figure 9-2.

Figure 9-2 Site device panel
b. Check the TRX status, as show in Figure 9-2.

– If abnormal, reset or replace the TRX board.
– If normal, go to 1.2.
2. On the BSC side, view the channel type of each TRX timeslot to check whether the
PDCH is configured for the cell. For detailed operations, refer to 1.2.
3. On the PCU LocalWS, run a cell reset command to check whether the cell is restored.
If not, refer to 9.2.3 Troubleshooting Cell Kickoff Failures (External PCU).
l If the cell status is Cell does not support GPRS, do as follows:
Operate according to 9.2.1 Troubleshooting a Cell Not Supporting GPRS.
l If the cell status is Cell does not exist, do as follows:
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, click
the cell and check the cell attributes. If the cell status is Not Activated, change it to
Activated.
l If the cell status is Cell database configuration error, do as follows:
1. Modify the GPRS cell data according to the error prompts on the PCU LocalWS.
2. On the BSC6000 Local Maintenance Terminal, check the channel type of each TRX
timeslot configured for the cell.
a. On the Management Tree tab page of the BSC6000 Local Maintenance
Terminal, click the cell and check the cell attributes.
b. Select a TRX in the Assigned TRXs area, and then click TRX Config.

c. On the Channel Attributes tab page, click Channel No. 0 to 7 in turn to check
all the channel types of the current TRX in Channel Type drop-down list, as
shown in Figure 9-3.
Figure 9-3 Channel attributes
3. Check whether the PBCCH is configured on the BSC side but not configured on the
PCU side. If the configurations are inconsistent on the two sides, modify the
parameters to keep them consistent.
l If the BSC administrative status of the cell is BLOCKED, do as follows:
1. On the BSC6000 Local Maintenance Terminal, check the status of the site and cell
to ensure that the cell is operational. For detailed operations, refer to Querying BTS
Running Status.
2. If the cell is operational, block the cell and then unblock the cell to check the cell status
on the PCU side.
3. On the PCU LocalWS, run the cell reset command, trace the messages on the Pb
interface, and then operate according to 9.2.3 Troubleshooting Cell Kickoff Failures
(External PCU).
----End
9.2.3 Troubleshooting Cell Kickoff Failures (External PCU)

This describes the cell kickoff procedure and the troubleshooting methods in the case that the
PCU is configured outside the BSC.
Context
Figure 9-4 shows the GPRS cell kickoff procedure.

Figure 9-4 GPRS cell kickoff procedure
BSC PCU
PCU_BSC_CELL_RESET
BSC_PCU_CELL_RESET_ACK
PCU_BSC_CELL_CONFIG_REQ
BSC_PCU_CELL_INFO
PCU_BSC_CELL_INFO_CNF
BSC_PCU_CHAN_INFO
PCU_BSC_CHAN_INFO_CNF
.
.
.
BSC_PCU_CHAN_INFO
PCU_BSC_CHAN_INFO_CNF
BSC_PCU_CELL_CONFIG_ACK
.
.
.
PCU_BSC_PDCH_REQ
BSC_PCU_PDCH_ACK
.
.
.
PCU_BSC_PDCH_REQ
BSC_PCU_PDCH_ACK
The GPRS cell kickoff procedure is described as follows:
1. The PCU initializes the cell and sends a PCU_BSC_CELL_RESET message to the BSC
on the Pb interface.
2. After the PCU receives a BSC_PCU_CELL_RESET_ACK message from the BSC, the
PCU sends a PCU_BSC_CELL_CONFIG_REQ message to the BSC, requesting the
configuration information of the cell.
3. The BSC sends a BSC_PCU_CELL_INFO message and multiple
BSC_PCU_CHAN_INFO messages to the PCU. The PCU responds with a
PCU_BSC_CELL_INFO_CNF message and PCU_BSC_CHAN_INFO_CNF messages
respectively. After the BSC sends such a message to the PCU, it waits for the response
from the PCU. The BSC sends another message to the PCU only after it receives the
confirmation message from the PCU.

4. After the BSC receives all the confirmation messages from the PCU, the BSC sends a
BSC_PCU_CELL_CONFIG_ACK message to the PCU, indicating that it has received all
the configuration information of the cell.
5. The PCU sends PCU_BSC_PDCH_REQ messages to the BSC on the Pb interface. The
BSC responds with BSC_PCU_PDCH_ACK messages. These channel request and
acknowledgment messages are processed concurrently.
During the cell kickoff procedure, if the response to a message is timeout, this message is sent
out again. If still timeout after multiple retransmissions, the system takes different measures in
different cases:
l BSC_PCU_CELL_RESET_ACK timeout
In this case, the PCU fails to initialize the cell. It then initializes other cells if necessary
and after that initializes this cell again.
l BSC_PCU_CELL_CONFIG_ACK timeout
In this case, the PCU fails to initialize the cell. It then initializes other cells if necessary
and after that initializes this cell again.
l Other responses timeout
Go to Step 1 to implement cell initialization.
During the cell kickoff procedure, if an NACK message is received, the system take different
measures in different cases:
l After sending a PCU_BSC_CELL_CONFIG_REQ message to the BSC, the PCU may
receive a BSC_PCU_CELL_CONFIG_NACK message from the BSC. The cause may be
that the cell does not exist, the cell does not support GPRS, the BSC is resetting the cell,
or others.
– If the cell does not exist or the cell does not support GPRS, the PCU does not initialize
the cell any longer.
– If the BSC is resetting the cell or the initialization is caused by other reasons, the PCU
initializes other cells and then this cell again.
l After sending a PCU_BSC_PDCH_REQ message from to the BSC, the PCU may receive
a BSC_PCU_PDCH_REQ_NACK message from the BSC. Go to Step 1 to implement cell
initialization.
Procedure
Step 1 On the PCU LocalWS, start Pb interface tracing and run a cell reset command.
Step 2 After sending a PCU_BSC_CELL_CONFIG_REQ message to the BSC, the PCU may receive
a BSC_PCU_CELL_CONFIG_NACK message from the BSC. For different causes, use
different troubleshooting methods, as shown in Table 9-6.

Table 9-6 Cell kickoff troubleshooting methods
Cause Troubleshooting Method
The cell does not exist. 1. On the BSC6000 Local Maintenance

Terminal, check whether the cell exists.
l If the cell does not exist, go to 2.2.
l If the cell exists, go to 2.3.
2. Add the cell on the BSC6000 Local
Maintenance Terminal, or delete the cell
on the PCU LocalWS. For detailed
operations, refer to Adding a BTS (TDM
Transmission Mode) or 9.2.9
Commands Executed on the PCU
Maintenance Terminal respectively.
3. If the fault persists, contact the Huawei
Customer Service Center by referring to
The cell does not support GPRS. Refer to 9.2.1 Troubleshooting a Cell Not
Supporting GPRS.
The BSC is resetting the cell. After the BSC resets the cell, run the cell reset
command again on the PCU LocalWS.
----End
9.2.4 Troubleshooting PDCH Faults (External PCU)

This describes how to troubleshoot a PDCH in a malfunctioning state on the external PCU side.
Fault Symptoms
l The PDCH status is Device has not been initialized or Blocked.
l The BSC administrative status of the PDCH is Blocked.
Procedure
On the PCU LocalWS, check the cell status on the PCU side.
NOTE
For the PCU commands, refer to 9.2.9 Commands Executed on the PCU Maintenance Terminal.
l If the PDCH status is Device has not been initialized, do as follows:
1. On the BSC6000 Local Maintenance Terminal, check the status of the BTS and cell
where the PDCH is located. For detailed operations, refer to Querying BTS Running
Status.
2. On the PCU LocalWS, check the circuit status of the Pb interface by referring to 9.2.9
Commands Executed on the PCU Maintenance Terminal.
– If the circuit status is Uninstalled, check whether the circuit configuration of the
Pb interface on the BSC side is consistent with that on the PCU side. If inconsistent,

modify the data configuration by referring to Configuring the Pb Interface E1/

T1.
– If the circuit status is Faulty, check whether the circuit connection is consistent
with the data configuration and whether the circuit connection is correct. After
correcting the connection, unblock the circuit on the Pb interface by referring to
Unblock Pb Interface CIC(UBL PBCIC).
– If the circuit on the Pb interface still malfunctions, contact the Huawei Customer
3. On the BSC6000 Local Maintenance Terminal, check for idle timeslots on the Abis
interface by referring to Querying the Status of the Abis Interface Timeslot.
– If there is an idle timeslot in the UNINSTALLED state, check the configuration
of the idle timeslot on the BSC side of the Abis interface.
– If there is an idle timeslot in the FAILURE state, check whether the circuit
connection on the Abis interface is consistent with the data configuration.
– Correct the circuit connection. If the idle timeslot on the Abis interface is still in
an abnormal state, contact the Huawei Customer Service Center by referring to
4. On the BSC6000 Local Maintenance Terminal, trace the messages on the Pb
interface by referring to Tracing the Messages on the Pb Interface.
If many PDCH requests are rejected because no PDCH is available, add PDCHs to
the cell.
l If the BSC administrative status of the PDCH is Blocked, do as follows:
1. On the BSC6000 Local Maintenance Terminal, check the channel status by referring
to Monitoring Channel Status.
If the channel is in an abnormal state, block the channel and then unblock it. For
detailed operations, refer to Modifying BTS Administrative State.
2. Check the channel status on the PCU side. If the channel status is still Blocked, contact
the Huawei Customer Service Center by referring to 1.3.1 Obtaining Technical
Support.
l If the PDCH is in any other abnormal state, contact the Huawei Customer Service Center
by referring to 1.3.1 Obtaining Technical Support.
----End
9.2.5 Troubleshooting LAPD Link Faults (External PCU)

This describes how to troubleshoot LAPD link faults, because of which the MS cannot perform
PS services.
Fault Symptoms
An LAPD link is in a faulty state, which you can check on the BSC6000 Local Maintenance
Terminal. The LAPD link is in the DISABLED state, which you can check on the PCU
LocalWS.
Possible Causes
The possible cause of LAPD link malfunctions is circuit insufficiency on the Pb interface. Circuit
insufficiency is further caused by the following reasons:

l The circuits on the Pb interface are too few.

l Some circuits on the Pb interface are blocked or faulty.
NOTE
Terminal.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, check the status of the E1/T1 port.
1. Loop back the E1/T1 port of the LAPD link and then check the loopback status. For detailed
operations, refer to Looping Back the Interface Board Port. If the E1/T1 port is in
loopback mode, click stop to stop the loopback.
2. Loop back the E1/T1 timeslot of the LAPD link and then check the loopback status. For
detailed operations, refer to Looping Back the Interface Board Port Timeslot. If the
timeslot is in loopback mode, click stop to stop the loopback.
3. Check the status of the LAPD link by referring to Maintaining LAPD Links. Check the
status of the LAPD link. If it is not restored, check whether the data configuration of the
LAPD link is consistent with the E1/T1 physical connection.
l If inconsistent, modify the data configuration.
Step 2 On the PCU LocalWS, check the status of the LAPD link.
If the administrative status of the LAPD link is BLOCKED, unblock the LAPD link.
l If the administrative status of the LAPD link is ENABLED, end the troubleshooting.
l If the administrative status of the LAPD link is still abnormal, go to Step 3.
Step 3 On the PCU LocalWS, check the status of the port of the LAPD link.
If the port of the LAPD link is in local or remote loopback, stop the loopback.
l If the administrative status of the LAPD link is ENABLED, end the troubleshooting.
l If the administrative status of the LAPD link is still abnormal, go to Step 4.
Step 4 Perform a loopback test on the E1/T1 lines that carry the LAPD link. This test does not affect
the data services on other E1/T1 lines connected to the L2PU/HLPU or the signaling on the
LAPD link. The specific operations are as follows:
1. On the BSC side, connect the RX end and the TX end of the E1/T1 lines that carry the
LAPD link.
2. On the PCU LocalWS, run the E1/T1 loopback command.
3. Check the loopback status of the E1/T1 lines and the status of the LAPD link.
l If the E1/T1 loopback test succeeds, the status of the LAPD link is ENABLED, which can
be checked on the PCU LocalWS. On the BSC6000 Local Maintenance Terminal, check
whether the configuration of the LAPD link on the BSC side is consistent with that on the
PCU side. For detailed operations, refer to Maintaining LAPD Links. If inconsistent,
modify the data. If the fault persists, go to Step 5.
l If the status of the LAPD link is still DISABLED on the PCU LocalWS, then, on the PCU
side, connect the RX end and the TX end of the E1/T1 lines that carry the LAPD link. If

the E1/T1 loopback test succeeds, you can infer that the E1/T1 lines that carry the LAPD
link are faulty. Replace the E1/T1 cable. If the E1/T1 loopback test fails, go to Step 5.
Step 5 On the PCU LocalWS, perform a loopback test on the board that carries the LAPD link.
CAUTION
This test is performed on all the LAPD links carried on the two L2PUs of the RPPU. Therefore,
the test disrupts the transmission of all traffic and signaling.
Perform the loopback test by running the command mt transRPPUNo 04 2 1 LoopMode.
NOTE
l RPPUNo: number of the board that carries the LAPD link

l LoopMode: loopback mode. The value range is as follows:
l 0: no loopback
l 1: loopback from the LAPD module
l 2: loopback from the CPM on chip 860
l 4: loopback from the E1/T1 controlling chip on the L2PU
l 5: loopback by connecting the RX end and the TX end at the E1/T1 port. This loopback mode
functions like the mt lapd loop set command.
Based on the result of LAPD link loopback, take one of the following measures:
l If the loopback test succeeds in LoopMode 1, 2, 4, or 5, the status of the LAPD link is
ENABLED, which you can check on the PCU LocalWS. Check whether the configuration
of the LAPD link on the BSC side is consistent with that on the PCU side.
l If the loopback test succeeds in LoopMode 1, 2, or 4 but fails in LoopMode 5, you can infer
that the external port for the E1/T1 cable that carries the LAPD link may be faulty and you
need to replace the board.
l If the loopback test fails in LoopMode 1, you can infer that the LAPD module software may
be incorrect and you need to contact Huawei for technical support. If the loopback test
succeeds in LoopMode 1, you can infer that the hardware of the L2PU that carries the LAPD
link may be faulty and you need to replace the board.
Step 6 On the PCU LocalWS, check whether the timeslot configured for the LAPD link is consistent
with that on the BSC side.
Step 7 On the BSC side and the PCU side, separately check whether the E1/T1 physical connection of
the LAPD link is consistent with the data configuration.
----End
9.2.6 Troubleshooting Cell Activity State Faults (Built-in PCU)

This describes how to troubleshoot the cell activity state faults. You can query on the Local
Maintenance Terminal that the activity state of a single cell is abnormal.
Possible Causes
The possible causes of the cell activity state faults are as follows:

l The cell cannot kick off normally or the cell distribution fails.
l The Um interface or the Gb interface is blocked.
Procedure
Step 1 On the Local Maintenance Terminal, run the DSP PSCELL command to verify the state of
a specified cell.
If the cell is inactivated, modify the cell state as follows:
click the cell and then select Configure Cell Attributes from the shortcut menu.
2. In the displayed dialog box, double-click the target cell in the Cell view list box to add it
to the Selected cells list box. Then, click Next.
3. In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A
dialog box is displayed, as shown in Figure 9-5.
Change the Activity State from Activated to Inactivated.

Figure 9-5 Set Cell Attributes dialog box

l If the fault persists, the DSP of the cell is blocked or is being initialized and so you can go
to Step 2.
Step 2 On the Local Maintenance Terminal, run the DSPSTAT command to verify the DSP state.
If the DSP is inoperable or faulty, block the DSP by referring to Unblock DSP(UBL DSP), or
redistribute the GPRS cells on the DSP by referring to Set PS Cell Distribution on DSP(SET
PSCELLTODSP).
Step 3 On the Local Maintenance Terminal, run the DSP PSRES command to verify the cell Um
administration state.
If the cell Um administration state is blocked, check whether the TRXs under this cell is in
normal state. Set the cell Um administration state to unblocked by referring to 7.2.3
Troubleshooting TRX Faults.


Step 4 On the Local Maintenance Terminal, run the DSP PSRES command to verify the cell Gb
administration state.
According to different transmission modes between the BSC and the SGSN, perform different
operations:
l Gb over FR
1. On the BSC6000 Local Maintenance Terminal, view the alarm information and
check whether the alarm 331 NSVC Faulty exists.
– If existent, troubleshoot the fault according to the alarm help.
– If not existent, go to 4.2.
2. On the Local Maintenance Terminal, run the DSP NSVC command to verify the
NSVC state.
– If the NSVC is blocked, unblock it by referring to Unblock NSVC(UBL
NSVC).
– If the NSVC is unblocked, go to 4.3.
3. On the Local Maintenance Terminal, run the DSP BC command to verify the BC
service state.
– If the BC service is unavailable, reconfigure it by referring to Maintaining the
BC.
– If the BC service is available, go to 4.4.
4. On the Local Maintenance Terminal, run the DSP NSVC command to verify
whether the NSVC configuration is consistent between the BSC side and the SGSN
side.
– If the configuration is inconsistent, reconfigure the NSE and NSVC on the BSC
side to keep them consistent with those on the SGSN side. For details, refer to
Configuring the NSE and Configuring the NSVC.
– If the configuration is consistent, go to Step 5.
l Gb over IP
1. On the BSC6000 Local Maintenance Terminal, view the alarm information and
check whether the alarm 332 NSVL Faulty exists.
– If existent, troubleshoot the fault according to the alarm help.
– If not existent, go to the next step.
2. Check whether the IP network from the BSC to the SGSN runs normally.
– If the IP network runs abnormally, check and modify the network by referring to
4.2 Link Troubleshooting Methods.
– If the IP network runs normally, go to the next step.
3. On the Local Maintenance Terminal, run the DSP NSVL command to verify
whether the NSVL configuration is consistent between the BSC side and the SGSN
side.
– If the configuration is inconsistent, reconfigure the NSE and NSVL on the BSC
side to keep them consistent with those on the SGSN side. For details, refer to

Configuring the NSE, Configuring the Local NSVL, and Configuring the
Remote NSVL.
– If the configuration is consistent, go to Step 5.
Step 5 On the Local Maintenance Terminal, run the DSP PTPBVC command to verify the PTP BVC
state.
l If the PTP BVC administration state is blocked, unblock the PTP BVC by referring to
Unblock PTPBVC(UBL PTPBVC).
l If the PTP BVC administration state is unblocked but the fault persists, contact the Huawei
Customer Service Center by referring to 1.3.1 Obtaining Technical Support.
----End
9.2.7 Troubleshooting Cell Service Disruption Faults (Built-in PCU)

This describes how to troubleshoot the faults caused by cell service disruption. When the faults
occur, the MSs in the cell fail to access the network or cannot run the PS services after access.
Possible Causes
The possible causes of cell service disruption faults are as follows:
l The MS is faulty.
l The data configuration is improper.
l The cell does not work normally.
Procedure
Step 1 Check whether the MS or its SIM card is faulty.
l If faulty, modify or replace the MS or SIM card.
Step 2 On the BSC6000 Local Maintenance Terminal, check whether GPRS Support in the basic
attribute parameters is selected.
l If it is not selected, set the parameter to enable the MS to run the PS services in the cell.
l If it is selected, go to Step 3.
Step 3 On the Local Maintenance Terminal, run the DSP PSCELL command to verify whether the
cell is in normal state.
l If abnormal, rectify the fault by referring to 9.2.6 Troubleshooting Cell Activity State
Faults (Built-in PCU).
Step 4 On the BSC6000 Local Maintenance Terminal, check the MCC, MNC, LAC, and CI.
l If the parameters are configured incorrectly, refer to 8.2.2 Troubleshooting Data
Configuration Faults to rectify the fault.
l If the parameters are configured correctly, go to Step 5.
Step 5 On the Local Maintenance Terminal, run the DSP PSRES command to verify the channel
status.

l If the channel is unavailable, check the status of the LAPD link on the BSC6000 Local
Maintenance Terminal; if the OML or RSL is faulty, refer to 4.2 Link Troubleshooting
Methods to rectify the fault.
l If the channel is available, go to Step 6.
Step 6 On the BSC6000 Local Maintenance Terminal, trace the Gb interface SIG and PTP messages.
For details, refer to Tracing SIG Messages on the Gb Interface and Tracing PTP Messages
on the Gb Interface.
After the MS is switched on, check whether the MS ATTACH and PDP Activation messages
are traced. According the reported information, determine the fault type and rectify the fault.
Step 7 On BSC6000 Local Maintenance Terminal, trace the Um interface message. For details, refer
to Tracing PS Domain Messages on the Um Interface.
Check the uplink and downlink messages on the Um interface, and analyze data transmission,
packet assignment, MS access, and immediate assignment to decide whether they are in normal
state. According to the reported information, determine the fault type and rectify the fault.
----End
9.2.8 Troubleshooting Global Service Disruption Faults (Built-in

PCU)
This describes how to troubleshoot the faults that disrupt the services globally. When the faults
occur, all the MSs in the service area of the PCU fail to access the network and cannot run data
services.
Possible Causes
The possible causes of global service disruption are as follows:
l The equipment is faulty.
l A transmission fault occurs.
l The data configuration is incorrect.
l The software program works abnormally.
Procedure
Step 1 Check whether the equipment is faulty.
1. Check and rectify the fault in power supply.
a. Check whether the power supply LED of the BSC power distribution box is in the
normal status.
l If the LED is abnormal, check whether the -48 V DC power cabinet works properly
and whether the power cables are securely connected to the -48V1 and -48V2
wiring terminals on the power distribution box.

WARNING
Be careful when checking the power cabinet and power cables. Misoperations are
dangerous.
l If normal, go to 1.1.b.
b. Check whether all subracks and LAN switches are powered normally.
l If abnormal, check whether the power switches of the subracks or LAN switches
are set to off, and whether the power input connectors on the subracks and LAN
switches and the -48 V power output connectors on the power distribution box are
in good contact.
Step 2 Check and rectify the fault in boards.
On the BSC6000 Local Maintenance Terminal, view the alarm information to check whether
there are hareware-related alarms. On the Device Panel, check whether the hardware is faulty.
To troubleshoot the fault, refer to 9.1.2 Alarms Related to PS Service Faults.

Step 3 Check and rectify the fault in transmission.
Check the ports that connect the BSC and the SGSN or BTS, and check whether the trunk cable
is securely connected to the port on the board.
l If a transmission fault is diagnosed, contact the transmission equipment maintenance

engineer to check and rectify the fault.
Step 4 Check whether the data configuration is incorrect.
The data configuration error occurs in the following cases:
l Incorrect data modification

– Misoperations may cause incorrect data modification.
In such an unexpected case, you can only check the data configuration and correct the
errors if any.
– Improper data modification
It can be anticipated that you modify the data as required but your modification is
improper. In such a case, you should back up the data before modification and restore the
backup data whenever your data modification goes wrong.
l Inconsistent data configuration
If the data is configured correctly on the BSC side, check whether the data is consistent with
that on the SGSN side. If inconsistent, modify the data configuration on the SGSN side.
Based on the previous situations, troubleshoot the fault as follows:


Step 5 Check whether the software program works normally on both BSC and SGSN sides.
On the BSC6000 Local Maintenance Terminal, trace the Um and Gb interface messages and
decide whether the software program is abnormal. For details, see Step 6 and Step 7 described
in 9.2.7 Troubleshooting Cell Service Disruption Faults (Built-in PCU).

----End
9.2.9 Commands Executed on the PCU Maintenance Terminal

This describes the commands frequently used on the PCU maintenance terminal during
troubleshooting.
Table 9-7 lists the commands frequently used on the PCU maintenance terminal.
NOTE
Each PCU MML command consists of keywords and optional parameters. The format of parameters is
defined as follows:
l < >: indicates mandatory items. The items in the angle brackets cannot be omitted when you enter a
command.
l [ ] : indicates optional items. The items in the brackets can be omitted when you enter a command.
l | : The parameter on only one side of this symbol must be entered.
l { }: All the parameters in the brackets must be entered or omitted as a whole.
Table 9-7 Commands executed on the PCU maintenance terminal
Function Command
Checking the status of cells on the PCU mt gcell show state{<BoardNo>all}|<LCNo>|

side <LCName>|<CGI>
Querying the cell attributes mt gcell show attr{<BoardNo>all}|<LCNo>|

<LCName>|<CGI>
Resetting the cells mt gcell show reset{<BoardNo>all}|<LCNo>|

<LCName>|<CGI>
Checking the cell configurations pcu check cellconfig{<LCNo1><LCNo2>...}|all
Checking the status of PDCHs mt pdch show state{<LCNo>|<LCName>|

<CGI>}{<PdchNo>|all}
Checking the status of LAPD links mt lapd show state{<BoardNo>all}|<LapdNo>|

<LapdName>
Unblocking the LAPD links mt lapd unblock{<BoardNo>all}|<LapdNo>|

<LapdName>
Checking the status of the E1 ports mt lapd port show state<BoardNo><L2PUNo>

corresponding to the LAPD links

Function Command
Setting the loopback status of the E1 ports mt lapd port loop

set<BoardNo><PortNo><LoopMode>
LoopMode is of three types:
l NoLoop: no loopback and normal working
mode
l LoopBack: local loopback
l REchoOff: remote loopback
Setting the loopback status of the LAPD mt lapd port loop set{<LapdNo>|
links <LapdName>}<LoopMode>
LoopMode is of two types:
l NoLoop: no loopback and normal working
mode
l FromE1Line: loopback of the E1 cable. You
need to connect the transmitting end and the
receiving end of the E1 cable.
Checking the configurations of the E1 pcu check e1config

ports
Deleting the cells pcu del allofonecell<LCNo>
Checking the status of the circuits on the mt pcic show state{<BSCNo><PcicNo>}|

Pb interface {<BoardNo><E1No><E1Slot>|all}
Blocking the cells mt gcell block {<BoardNo>all}|<LCNo>|

<LCName>|<CGI>
Unblocking the cells mt gcell unblock {<BoardNo>all}|<LCNo>|

<LCName>|<CGI>
Querying the cell attributes pcu show attr<LCNo>|all|

{where<Condition>}[order by <FieldName>]
9.3 Typical Cases of Troubleshooting PS Service Faults

This describes the typical cases of troubleshooting PS service faults.
9.3.1 Case: Intermittent LAPD Links

This describes a typical case of troubleshooting intermittent LAPD links. When the E1 cable on
the Pb interface is faulty and the receiving (RX) end is normal but the transmitting (TX) end is
abnormal, the LAPD links are intermittent. You need to replace the E1 cable.
9.3.2 Case: Broken Links on the Gb Interface
This describes a typical case of troubleshooting broken links on the Gb interface. When the links
on the Gb interface break down, you can check the cable connection, BC, NSVC, and data
configuration.
9.3.3 Case: MS GPRS Failure

This describes a typical case of troubleshooting the faults in data configuration or GPRS network
equipment. The faults may cause the MS to fail the network access.
9.3.4 Case: Unstable GPRS Download Rate
This describes a typical case of troubleshooting the unstable GPRS download rate. The fault is
caused by the factors such as channel resources, coding schemes, and Gb interface flow control.
9.3.1 Case: Intermittent LAPD Links

This describes a typical case of troubleshooting intermittent LAPD links. When the E1 cable on
the Pb interface is faulty and the receiving (RX) end is normal but the transmitting (TX) end is
abnormal, the LAPD links are intermittent. You need to replace the E1 cable.
Fault Symptoms
The intermittent LAPD link fault occurs when the E1 cable on the Pb interface is faulty with its
RX end normal but TX end abnormal.
According to the LAPD protocol, the link setup is regarded as successful when the SAMB frame
is received. Therefore, the LAPD link setup is successful if the RX end is normal. If the TX is
abnormal, the interconnection with the peer end fails and the link is broken when the timer
expires. Therefore, if the RX end is normal but the TX end is abnormal, the LAPD links are
intermittent. In addition, the alarm 20083 Remote E1/T1 Alarm (RAI) is reported.

1. On the PCU side, the RPPU that carries the LAPD links incurs RX and TX self-loop at its
E1 port. The LAPD links are normal, but when the E1 cable is reconnected, the LAPD links
appear intermittent.
2. On the BSC side, the E1 port that carries the LAPD links incurs RX and TX self-loop, and
the LAPD links are still intermittent.
3. After the E1 cable is replaced, the LAPD links are restored to normal.
9.3.2 Case: Broken Links on the Gb Interface

This describes a typical case of troubleshooting broken links on the Gb interface. When the links
on the Gb interface break down, you can check the cable connection, BC, NSVC, and data
configuration.
Fault Symptoms
The Gb interface is blocked and the PS service is disrupted because the Gb links are broken.

1. Check whether the cables and interface boards work normally or whether the connectors
are loose or aging. If so, rectify the fault.
2. Check whether the data configuration is consistent between the BSC and the SGSN. The
data to be checked includes the number of the subrack configured for the bearer channel,
slot number, port number, and DLCI number.
3. Check whether the BC is blocked. If so, unblock the BC. For details, refer toUnblock BC
(UBL BC).

9.3.3 Case: MS GPRS Failure

This describes a typical case of troubleshooting the faults in data configuration or GPRS network
equipment. The faults may cause the MS to fail the network access.
Fault Symptoms
After switch-on, the MS cannot access the network normally, the MS PDP fails to be activated,
and the MS cannot perform data transmission.

1. Check and ensure that the cell is in normal state.
On the Local Maintenance Terminal, run the DSP PSCELL command to verify the
kickoff state of a specified cell.
2. Check and ensure that the PDCH is in normal state.
On the BSC6000 Local Maintenance Terminal, check the channel attributes and ensure
that the PDCH of the cell is in normal state. For details, refer to Check channel
attributes.
3. Check whether the fault is caused by the SGSN.
On the BSC6000 Local Maintenance Terminal, trace the Gb interface message. For
details, refer to Step 6 described in 9.2.7 Troubleshooting Cell Service Disruption Faults
(Built-in PCU).
Check whether the uplink message is traced after the MS is switched on. If the uplink
message is traced, contact the SGSN maintenance engineer to handle the SGSN equipment.
4. On the BSC6000 Local Maintenance Terminal, trace the Um interface and Gb interface
messages. For details, refer to Step 6 and Step 7 described in 9.2.7 Troubleshooting Cell
Service Disruption Faults (Built-in PCU).
Analyze the MS ATTACH, PDP activation, resource assignment, and data transmission
and check whether the regular signaling flow is normal. If the signaling flow is abnormal,
solve the problem according to actual conditions.
9.3.4 Case: Unstable GPRS Download Rate

This describes a typical case of troubleshooting the unstable GPRS download rate. The fault is
caused by the factors such as channel resources, coding schemes, and Gb interface flow control.
Fault Symptoms
When the MS performs GPRS data transmission, especially through the FTP, the download rate
is unstable.

1. The Th and Tc in the NS and BSSGP parameters are set to the default values and therefore
the two parameters are inconsistent with the configuration on the SGSN side. The data
inconsistency affects the Gb flow control mechanism, thus decreasing the GPRS rate.
2. When the built-in PCU is used and the BS and SGSN are interconnected, the Gb parameters
should be set consistently between the two sides.

On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-
click BSC6000 and select Configure BSC Attributes. On the displayed dialog box, select
the NS and BSSGP tab page, as shown in Figure 9-6.
Figure 9-6 NS and BSSGP tab page

BSS Troubleshooting Guide 10 Cell Broadcast Faults
10 Cell Broadcast Faults
About This Chapter
This describes cell broadcast faults in terms of the symptoms, troubleshooting methods, and
typical cases.
10.1 Cell Broadcast Fault Symptoms

This describes the impacts of cell broadcast faults on services, possible alarms, and involved
10.2 Cell Broadcast Troubleshooting Methods
This describes how to troubleshoot cell broadcast faults. Basically, when a cell broadcast fault
rectify the fault.
10.3 Typical Cases of Troubleshooting Cell Broadcast Service Faults
This describes the typical cases of troubleshooting cell broadcast service faults.

10 Cell Broadcast Faults BSS Troubleshooting Guide
10.1 Cell Broadcast Fault Symptoms

This describes the impacts of cell broadcast faults on services, possible alarms, and involved
10.1.1 Impacts of Cell Broadcast Faults on Services

This describes the impacts of cell broadcast faults on services.
10.1.2 Alarms Related to Cell Broadcast Service Faults
This describes the alarms related to cell broadcast service faults. The alarms help locate and
rectify the faults.
10.1.3 Counters Related to Cell Broadcast Service Faults
This describes the counters related to cell broadcast service faults. The counters help locate and
rectify the faults.
10.1.1 Impacts of Cell Broadcast Faults on Services

This describes the impacts of cell broadcast faults on services.
The impacts of cell broadcast faults on services are as follows:
l The cell broadcast function is enabled, but the MS cannot receive cell broadcast messages.
l The CBT fails to broadcast messages. In this case, a Failed to submit message is displayed.
l The simple cell broadcast function is enabled, but the MS cannot receive cell broadcast
messages.
10.1.2 Alarms Related to Cell Broadcast Service Faults

This describes the alarms related to cell broadcast service faults. The alarms help locate and
rectify the faults.
Table 10-1 lists the alarms related to cell broadcast service faults.
Table 10-1 Alarms related to cell broadcast service faults
The network connection is faulty. For 102 Disrupted Connection with the CBC
example, the Ethernet cable is loosely
connected.
10.1.3 Counters Related to Cell Broadcast Service Faults

This describes the counters related to cell broadcast service faults. The counters help locate and
rectify the faults.
Table 10-2 lists the counters related to cell broadcast service faults.

Table 10-2 Counters related to cell broadcast service faults

Counter Description
AL0484 Mean Capacity of BSC Message Library
L0457 WRITE-REPLACE Requests Received by BSC
L0458 KILL Requests Received by BSC
L0459 STATUS-CBCH-QUERY Requests Received by BSC
L0460 STATUS-MESSAGE-QUERY Requests Received by

BSC
L0461 SET-DRX Requests Received by BSC
L0462 RESET Requests Received by BSC
L0463 REPORT Responses to WRITE-REPLACE Requests
L0464 REJECT Responses to WRITE-REPLACE Requests
L0465 REPORT Responses to KILL Requests
L0466 REJECT Responses to KILL Requests
L0467 REPORT Responses to STATUS-CBCH-QUERY

Requests
L0468 REJECT Responses to STATUS-CBCH-QUERY

Requests
L0469 REPORT Responses to STATUS-MESSAGE-

QUERY Requests
L0470 REJECT Responses to STATUS-MESSAGE-QUERY

Requests
L0471 REPORT Responses to SET-DRX Requests
L0472 REJECT Responses to SET-DRX Requests
L0473 RESTART-INDICATION Requests Sent from BSC
L0474 REJECT Responses to RESTART-INDICATION

Requests
L0475 FAILURE-INDICATION Requests Sent from BSC
L0476 CBCH Loading Indications Received by BSC

(Overflow)
L0477 CBCH Loading Indications Received by BSC

(Overflow)
L0478 WRITE-REPLACE Requests (WRITE Requests)

Received by BSC

Counter Description

(WRITE Requests)

(WRITE Requests)
L0481 WRITE-REPLACE Requests (REPLACE Requests)

Received by BSC

(REPLACE Requests)

(REPLACE Requests)
L0486 Disruptions of the BSC-CBC Connection
L0490 Number of Sent Broadcast Short Messages
L0487 CBCH Message Queue Usage
L0489 Average CBCH Message Queue Usage
L0488 Maximum CBCH Message Queue Usage
10.2 Cell Broadcast Troubleshooting Methods

This describes how to troubleshoot cell broadcast faults. Basically, when a cell broadcast fault
rectify the fault.
Procedure
Table 10-3 Cell broadcast troubleshooting methods
The BSC fails to provide the cell broadcast 10.2.1 Troubleshooting Disconnection
service. Between the BSC and the CBC
The CBS.exe file is not running or the SQL Server 10.2.2 Troubleshooting CBS Startup
is not running properly. Failures
Messages to be broadcast cannot be successfully 10.2.3 Troubleshooting a Failure to

sent through the CBS to the BSC. Submit Cell Broadcast Messages to the
BSC

The MS cannot make calls or display the network 10.2.5 Troubleshooting Message
properly. The possible cause is that the cell Reception Failures Caused by the MS
broadcast function is disabled or the number of
the channel for cell broadcast is incorrect.
Messages to be broadcast are successfully sent to 10.2.4 Troubleshooting Incorrect Cell

the BSC through the CBT software. The MS, Broadcast Parameter Settings
however, still cannot receive the cell broadcast
messages.
The BSC cannot provide the simple cell broadcast 10.2.6 Troubleshooting Incorrect
service, and the MS cannot receive cell broadcast Parameter Setting of the Simple Cell
messages. Broadcast
Technical Support.
----End
10.2.1 Troubleshooting Disconnection Between the BSC and the

CBC
This describes how to troubleshoot the faults in the interface between the BSC and the cell
broadcast center (CBC). The fault symptom shows that the BSC fails to provide the cell broadcast
service.
Possible Causes
The possible causes of the disconnection between the BSC and the CBC are as follows:
l The GXPUM board is faulty.

l The IP address route is wrongly configured.
l The transmission cable is faulty.
NOTE
The peer CBC runs normally by default.
Procedure
Step 1 Check whether the GXPUM board is faulty by referring to Querying BSC Board
Information.
l If faulty, rectify the fault by referring to 10.1.2 Alarms Related to Cell Broadcast Service
Faults.
Step 2 Check whether the GOMU/GBAM routing is consistent with the configuration of the CBC.
l If inconsistent, reconfigure the data to keep it consistent. For details, refer to Configuring
Cell Broadcast.

NOTE
Check the GOMU/GBAM routing as follows: on the BSC6000 Local Maintenance Terminal, query the
following Basic Data in the Configure BSC Attributes window: CBC IP, CBC Port, CB Interface
IP, CB Port, and CB Interface Handshake.
Step 3 Check whether the transmission cable is faulty. If faulty, rectify the fault by referring to 4.2.9
Troubleshooting E1/T1 Transmission Faults and 4.2.10 Troubleshooting Optical
Transmission Faults.
Technical Support.
----End
10.2.2 Troubleshooting CBS Startup Failures

This describes how to troubleshoot CBS startup failures. When the CBS fails to be started, the
MS cannot receive cell broadcast messages.
Possible Causes
The possible cause of a CBS startup failure is that the CBS software is closed by mistake or the
SQL Server is malfunctioning.
Procedure
Step 1 Check the running status of the CBS.
l If the CBS.exe file is not running, double-click to run it.
l If the Huawei.exe file is not running, double-click to run it.
Step 2 If neither CBS.exe nor Huawei.exe runs properly, check the cbs.log file in \iMobile\cbs\.
If the cbs.log file includes the following message:

Data source DRIVER={SQL
Server};SERVER=127.0.0.1;Trusted_Connection=yes;DATABASE=iMobi
le:Specified SQL server not found.ConnectionOpen (CreateFile())
You can infer that an error occurs when the SQL Server is started.
Step 3 Check the running status of the SQL Server.
l Check the system tray. If the icon is displayed, you can infer that the SQL Server is
running.
l Check the system tray. If the icon is not displayed, you can infer that the SQL Server
is not started.

Choose Start > Programs > Microsoft SQL Server > Service Manager to start the SQL
Server.
l Check the system tray. If the icon or is displayed, you can infer that the SQL Server
stops running or the running is suspended.
Double-click the icon. In the displayed dialog box, choose Start > Continue (S) to start
or continue to run the SQL Server. If the SQL Server fails to be started, refer to the SQL
Server installation guide to reinstall it.
NOTE
If the iMobile database still fails to be opened, restart the SQL server and then run the CBS.exe file.
----End
10.2.3 Troubleshooting a Failure to Submit Cell Broadcast Messages

to the BSC
This describes how to troubleshoot a failure to submit cell broadcast messages from the CBS to
the BSC.
Possible Causes
The possible causes of such submit failures are as follows:
l The GXPUM on the BSC side is not running properly.
l The CBC is not configured properly on the BSC side.
l The number of cells that support short message broadcast is 0 in the license file on the BSC
side, or no channel for broadcasting short messages is set up in the cells on the BSC side.
Procedure
Step 1 On the BSC Device Panel tab page of the BSC6000 Local Maintenance Terminal, check
whether the GMPS is configured with the GXPUM and whether the GXPUM is running properly.
l If the GXPUT is not configured, configure it by referring to Configuring the GXPUM
and ensure that it can run properly.
l If the GXPUT is not running properly, rectify the fault by referring to Analysis of
Hardware Faults.
l If the GXPUM is configured and it is running properly, go to Step 2.
Step 2 Check the global data configuration of the BSC.
click BSC6000 and select Configure BSC Attributes. A dialog box is displayed, as shown
in Figure 10-1.

Figure 10-1 Configuring BSC attributes
2. On the Basic Data tab page, check whether the settings of the following parameters are
consistent with the actual configuration:
l Support Cell Broadcast
l CBC IP
l CBC Port
l CB Interface IP
l CB Interface Port
l CB Interface Handshake
l If inconsistent, modify the parameter settings to keep them consistent.
Step 3 On the Local Maintenance Terminal, check the license information and check whether the
parameter settings are consistent with the actual configuration. For detailed operations, refer to
Display License Usage Information(DSP LICUSAGE).
l If the number of TRXs that support short message broadcast is 0, you can infer that the cell
broadcasting function is not enabled. In this case, a new license needs to be requested.
l If the number of TRXs that support short message broadcast is 0, you can infer that the cell
broadcasting function is enabled. Go to Step 4.
Step 4 Check whether the CBCH is configured for the TRX.
l If the CBCH is not configured, configure it on the BSC6000 Local Maintenance
Terminal by referring to Configuring Cell Broadcast.
l If the CBCH is configured, go to Step 5.
Technical Support.
----End

10.2.4 Troubleshooting Incorrect Cell Broadcast Parameter Settings

This describes how to troubleshoot incorrect parameter settings for cell broadcast. When the
parameter settings are incorrect, the MS cannot receive cell broadcast messages although the
messages are successfully sent to the BSC through the CBT software.
Possible Causes
The possible causes of parameter setting errors are as follows:
l The number of broadcast support cells exceeds that specified in the BSC license file.
l The cell on which the MS camps is not within the broadcast scope, or the broadcast time
is set incorrectly.
Procedure
Step 1 On the Local Maintenance Terminal, check the AUTHORIZED CBS CELL specified in the
BSC license file. For detailed operations, refer to Display License Usage Information(DSP
LICUSAGE).
Step 2 Check the CBT data configuration to obtain the number of broadcast support cells.
1. Select a message to be broadcast through the CBT software, as shown in Figure 10-2.
Figure 10-2 Selecting a message
2. Right-click the message, and then select Edit from the shortcut menu. A dialog box is

Figure 10-3 Broadcast scope
3. On the Broadcast Scope tab page, calculate the number of selected cells.
Step 3 Compare the number of broadcast support cells specified in the BSC license file with that
specified in the BSC data configuration.
l If the number of selected cells exceeds the number of broadcast support cells specified in
the BSC license file, consult with the customer about whether to apply for a new license.
l If no new license file is required, remove some cells to cause the number of cells within
the limit specified in the BSC license file.
Step 4 Check whether the cell on which the MS camps is within the broadcast scope, as shown in
Figure 10-3. If the cell is not within the broadcast scope, select the cell in which the message
is to be broadcast.
Step 5 Select the broadcast tab page, as shown in Figure 10-4. Check whether the configured broadcast
time is consistent with the required one. If inconsistent, modify the start time and then submit
the message.

Figure 10-4 Editing the message
----End
10.2.5 Troubleshooting Message Reception Failures Caused by the

MS
This describes how to troubleshoot message reception failures caused by the MS. When such a
failure occurs, the MS cannot make calls, display the MNC, or receive cell broadcast messages.
Possible Causes
The possible cause of a message reception failure caused by the MS is that the MS fails to access
the network or the MS disables the function of receiving cell broadcast messages.
Procedure
Step 1 Check whether the MS can make calls and display the MNC.
l If the MS can implement such functions, end the troubleshooting.
l If the MS cannot implement such functions, go to Step 2.
Step 2 Check whether the function of receiving cell broadcast messages is enabled or whether the
number of the channel for cell broadcast is correct.
l If the function of receiving cell broadcast messages is disabled, enable it.

l If the number of the channel for cell broadcast is wrong, correct it.
----End
10.2.6 Troubleshooting Incorrect Parameter Setting of the Simple

Cell Broadcast
This describes how to troubleshoot the incorrect parameter setting of the simple cell broadcast.
The fault symptom shows that the BSC fails to provide simple cell broadcast services and thus
the MS cannot receive the cell broadcast message.
Possible Causes
The possible causes are as follows:
l The simple cell broadcast function is not enabled on the BSC6000 Local Maintenance
Terminal or the related parameters are set incorrectly.
l The cell broadcast message is not configured on the Local Maintenance Terminal.
Procedure
On the BSC6000 Local Maintenance Terminal, enable the simple cell broadcast function and
configure related parameters. For details, refer to Configuring Simplified Cell Broadcast.
----End
10.3 Typical Cases of Troubleshooting Cell Broadcast

Service Faults
This describes the typical cases of troubleshooting cell broadcast service faults.
10.3.1 Case: CBT/OMT/MMT Login Failure

This describes a typical case of troubleshooting the CBT/OMT/MMT login failure. If the user
name on the CBT/OMT/MMT is different from that on the CBS, or if the DCOM configuration
is incorrect, the login to the CBT/OMT/MMT fails.
10.3.1 Case: CBT/OMT/MMT Login Failure

This describes a typical case of troubleshooting the CBT/OMT/MMT login failure. If the user
name on the CBT/OMT/MMT is different from that on the CBS, or if the DCOM configuration
is incorrect, the login to the CBT/OMT/MMT fails.
Fault Symptoms
If the user name on the CBT/OMT/MMT is different from that on the CBS, or if the DCOM
configuration is incorrect, the CBT/OMT/MMT fails to connect to the server.
NOTE
Run the dcomcnfg command to check the DCOM configuration.


1. Log in to the CBT/OMT/MMT as the system administrator. Create a user name that is
identical to that on the CBS.
2. On the Default Properties tab page, select None from the Default Authentication
Level drop-down list.
3. Log in to the CBT/OMT/MMT using the newly created user name and restart the application
programs.


BSS Troubleshooting Guide (V900R008C01 - 01)

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BSS Troubleshooting Guide (V900R008C01 - 01)

Hochgeladen von

Copyright:

Verfügbare Formate

HUAWEI BSC6000 Base Station Subsystem

BSS Troubleshooting Guide

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

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

Trademarks and Permissions

Huawei Proprietary and Confidential

About This Document.....................................................................................................................1

2 Collecting Information for Locating BSS Faults..................................................................2-1

Issue 01 (2008-06-10) Huawei Proprietary and Confidential i

2.13.2 Collecting Messages Traced on the External PCU............................................................................2-24

ii Huawei Proprietary and Confidential Issue 01 (2008-06-10)

5.3.2 Case: Slip Frame Alarm.........................................................................................................................5-8

Issue 01 (2008-06-10) Huawei Proprietary and Confidential iii

8.3.4 Case: MS Network Disconnection Due to Incorrect CGI Configuration.............................................8-13

10 Cell Broadcast Faults.............................................................................................................10-1

iv Huawei Proprietary and Confidential Issue 01 (2008-06-10)

Figure 1-1 Troubleshooting process.....................................................................................................................1-2

Issue 01 (2008-06-10) Huawei Proprietary and Confidential v

Figure 4-9 Modify M3UA Link dialog box (2)..................................................................................................4-32

vi Huawei Proprietary and Confidential Issue 01 (2008-06-10)

Table 1-1 BSS fault location information form....................................................................................................1-8

Issue 01 (2008-06-10) Huawei Proprietary and Confidential vii

About This Document

Product Name Model Product Version

BSC BSC6000 V900R008C01

BTS BTS3012 V300R004&V300R005&V300R006

Issue 01 (2008-06-10) Huawei Proprietary and Confidential 1

2 Huawei Proprietary and Confidential Issue 01 (2008-06-10)

Indicates a hazard with a high level of risk that, if not avoided,

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

Indicates a potentially hazardous situation that, if not avoided,

NOTE Provides additional information to emphasize or supplement

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files,directories,folders,and users are in boldface. For

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

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

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

[ x | y | ... ] Optional alternative items are grouped in square brackets and

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

Issue 01 (2008-06-10) Huawei Proprietary and Confidential 3

[ x | y | ... ] * Alternative items are grouped in braces and separated by vertical

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

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

Key1+Key2 Press the keys concurrently.For example,pressing Ctrl+Alt+A

4 Huawei Proprietary and Confidential Issue 01 (2008-06-10)

1 Introduction to BSS Troubleshooting

About This Chapter

1.1 Troubleshooting Process

Issue 01 (2008-06-10) Huawei Proprietary and Confidential 1-1

1.1 Troubleshooting Process

Figure 1-1 shows the troubleshooting process.

Figure 1-1 Troubleshooting process

Determine the scope

Find the causes

Rectify the fault

Collecting Fault Information

1-2 Huawei Proprietary and Confidential Issue 01 (2008-06-10)

l Status of the LEDs on involved boards