54461517 BSS Troubleshooting Guide V900R008C01 01

HUAWEI BSC6000 Base Station Subsystem V900R008

BSS Troubleshooting Guide

Issue Date INTERNAL

01 2008-06-10

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 http://www.huawei.com [email protected]

Website: Email:

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

NoticeThe 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 BSC6000 Base Station Subsystem BSS Troubleshooting Guide

Contents

ContentsAbout This Document.....................................................................................................................1 1 Introduction to BSS Troubleshooting....................................................................................1-11.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-12.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 Copyright Huawei Technologies Co., Ltd i

Contents

HUAWEI BSC6000 Base Station Subsystem BSS Troubleshooting Guide 2.13.2 Collecting Messages Traced on the External PCU............................................................................2-24

3 Common Faults...........................................................................................................................3-13.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-14.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-15.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 Copyright Huawei Technologies Co., Ltd Issue 01 (2008-06-10)


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-16.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-17.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-18.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 Copyright Huawei Technologies Co., Ltd iii

Contents

HUAWEI BSC6000 Base Station Subsystem 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-19.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-110.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


Issue 01 (2008-06-10)


Figures

FiguresFigure 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 Copyright Huawei Technologies Co., Ltd v

Figures


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


Issue 01 (2008-06-10)


Tables

TablesTable 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)


vii


About This Document

About This DocumentPurposeThis 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 l l

Complaints from subscribers Faults detected in regular maintenance Burst equipment faults

Product VersionThe following table lists the product versions related to this document. Product Name BSC BTS Model BSC6000 BTS3012 BTS3012AE BTS3006C BTS3002E BTS3036/BTS3900 GSM BTS3036A/BTS3900A GSM DBS3036/DBS3900 GSM Product Version V900R008C01 V300R004&V300R005&V300R006 V300R005&V300R006 V300R005&V300R006 V300R005 V300R008 V300R008 V300R008

Intended AudienceThis document is intended for:l l l

System engineers Technical support engineers Maintenance engineersHuawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 1

Issue 01 (2008-06-10)

About This Document


Change HistoryFor changes in the document, refer to Changes in BSS Troubleshooting Guide.

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

Conventions1. Symbol Conventions The following symbols may be found in this document. They are defined as follows2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 01 (2008-06-10)


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. Indicates a hazard with a medium or low level of risk which, if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save your time. Provides additional information to emphasize or supplement important points of the main text.

DANGER

WARNING

CAUTIONTIP

NOTE

2. General Conventions Convention Times New Roman Boldface Italic Courier New 3. Command Conventions Convention Boldface Italic [] {x | y | ...} [ x | y | ... ] { x | y | ... } * Description The keywords of a command line are in boldface. Command arguments are in italic. Items (keywords or arguments) in square brackets [ ] are optional. Alternative items are grouped in braces and separated by vertical bars.One is selected. Optional alternative items are grouped in square brackets and separated by vertical bars.One or none is selected. Alternative items are grouped in braces and separated by vertical bars.A minimum of one or a maximum of all can be selected. Description Normal paragraphs are in Times New Roman. Names of files,directories,folders,and users are in boldface. For example,log in as user root . Book titles are in italics. Terminal display is in Courier New.

Issue 01 (2008-06-10)


3

About This Document


Convention [ x | y | ... ] *

Description 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 Convention Boldface > Description 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 Convention Key Key1+Key2 Key1,Key2 Description Press the key.For example,press Enter and press Tab. Press the keys concurrently.For example,pressing Ctrl+Alt+A means the three keys should be pressed concurrently. Press the keys in turn.For example,pressing Alt,A means the two keys should be pressed in turn.

6. Mouse Operation Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.

4


Issue 01 (2008-06-10)


1 Introduction to BSS Troubleshooting

1

Introduction to BSS Troubleshooting

About This ChapterThis 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)


1-1



1.1 Troubleshooting ProcessThis 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 and services are restored? Yes End

No

Obtain Huawei Technical Support

Collecting Fault InformationBefore troubleshooting, you need to collect the following information:l l l l l l

Fault symptoms Fault occurrence time, site, and frequency Fault scope and impact Operational status of the equipment before the fault occurs Operations performed on the equipment before the fault occurs, and the consequence Alarms and associated alarms when the fault occursHuawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 01 (2008-06-10)

1-2

HUAWEI BSC6000 Base Station Subsystem BSS Troubleshooting Guidel l


Status of the LEDs on involved boards 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. 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. Observe board LEDs and the alarm management system on the LMT to obtain information about the running status of software and hardware. 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.

l

l

l

Determining the Scope and Type of the FaultAfter 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 l l l l l l l

3 Common Faults 4 Link Faults 5 Clock Faults 6 Handover Faults 7 Congestion Faults 8 Access Faults 9 PS Service Faults 10 Cell Broadcast FaultsNOTE

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. In addition, this document describes how to analyze and locate common faults, such as one-way audio, no audio, and noise.

l

Finding the Causes of the FaultBy 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.Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 1-3

Issue 01 (2008-06-10)

1 Introduction to BSS TroubleshootingNOTE


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 FaultAfter 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 l

Use different procedures for different faults. Check the system again after the troubleshooting to ensure that the fault is completely rectified. To avoid the occurrence of similar faults, record the causes of the fault and take preventive or corrective measures.

l

Checking the Equipment and ServicesAfter 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 CenterCollect 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 MethodsCommon 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 AnalysisRaw 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.1-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 01 (2008-06-10)



Alarm Information AnalysisAlarm 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 AnalysisAn 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 TestA 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.

MeasurementMeasurement 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 StatisticsPerformance 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 TracingInterface 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.Issue 01 (2008-06-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 1-5



Common Test and Loopback TestA 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 InterchangeYou 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 ResetSwitchover 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 l

Compared with other methods, switchover and reset are auxiliary methods. 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. Usually, the reset operation disrupts the ongoing services and even brings the system down.

l

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 SupportYou 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.Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 01 (2008-06-10)

1-6



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 SupportThis describes how to contact Huawei for technical support.

Procedurel l Dial the customer service number of Huawei: 4008302118 or (+86-755) 2856 0000. Fax a properly written feedback form to Huawei (0755-28560111) or the local office. l l 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.

Send an E-mail to [email protected]. 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 TroubleshootingThe 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 InformationThe general fault information to be collected is as follows:l l l l l

Full name of the office Name and phone number of the contact person Time when the fault occurs Detailed description of the fault symptoms Host software version of the equipmentHuawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 1-7

Issue 01 (2008-06-10)

1 Introduction to BSS Troubleshootingl l


Measures taken after the fault occurs and the result Severity level of the fault and the time required for rectifying the fault

Collecting Fault Location InformationThe fault location information to be collected is as follows:l l l l l l l l l l l l

BSC configuration data M2000 performance measurement information BSC performance measurement information BSS alarm information BSS log information GBAM/GOMU information Messages traced on the BSC M2000 TRACE files Channel status information Board bar code information Voice tuning information 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 FormAfter 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 Complainer Complaint Time Response Time Telephone Warranty Expired? Yes No Device Type Host Software Version

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 InstructionIssue 01 (2008-06-10)

1-8




Handling result (attachment allowed):Operator: Date:

Outstanding issue:

Issue 01 (2008-06-10)


1-9


2 Collecting Information for Locating BSS Faults

2

Collecting Information for Locating BSS Faults

About This ChapterWhen 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 M2000Issue 01 (2008-06-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 2-1



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-2


Issue 01 (2008-06-10)



2.1 Collecting the Local InformationThis 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.

Prerequisitel l

The LMT runs normally. The communication between the LMT and the BSC is normal.

ContextIf 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 l l

Core Dump: mirror file of the realtime running of the server Pfm: performance statistics file Log: oprlog (operation log), dbglog (debugging log), runlog (running log), lstlog (lastword log), chrlog (CHR log), btslog (BTS log), and frqlog (frequency scan log). Alarm: alarm log file

l

ProcedureStep 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 l

Click the Collect BTS information tab. On the tab page, select the BTSs of which the information needs to be collected. 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.

Issue 01 (2008-06-10)


2-3



Figure 2-1 Collecting BSC local information

Step 4 Click Cancel. Collecting the BSC local information is complete. ----End

2.2 Collecting BSC Configuration DataThis describes how to collect BSC configuration data for troubleshooting.

Prerequisitel l l

The LMT runs properly. The BSC is functional. The communication between the LMT and the BSC is normal.

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

2-4


Issue 01 (2008-06-10)



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 InformationThis describes how to collect M2000 performance measurement information for troubleshooting.

Prerequisitel l

The M2000 runs properly. The communication between the M2000 and the BSC is proper.

ProcedureStep 1 On the M2000 Client, choose Performance > Query Result on the menu. A dialog box is displayed, as shown in Figure 2-3.

Issue 01 (2008-06-10)


2-5



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

2-6


Issue 01 (2008-06-10)



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 InformationThis describes how to collect BSC performance measurement information for troubleshooting.

Prerequisitel l

The communication between the LMT and the GBAM or the GOMU is proper. The communication between the Telnet client and the GBAM or the GOMU is proper.

ProcedureStep 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 InformationThis 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 FilesThis describes how to collect BSS alarm log files and upload the log files to the LMT.Issue 01 (2008-06-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 2-7



Prerequisitel l l

The LMT runs properly. The communication between the LMT and the BSC is normal. The communication between the LMT and the alarm box is normal.

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

2-8


Issue 01 (2008-06-10)



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. ----EndIssue 01 (2008-06-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 2-9



2.5.2 Collecting BSS Alarm InformationThis describes how to collect BSS alarm information for troubleshooting.

Prerequisitel l

The communication between the LMT and the GBAM or the GOMU is proper. The communication between the Telnet client and the GBAM or the GOMU is proper.

ProcedureStep 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 InformationThis 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 FilesThis describes how to collect BSC log files for troubleshooting.

Prerequisitel l

The LMT runs properly. The communication between the LMT and the BSC is normal.Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 01 (2008-06-10)

2-10



ProcedureStep 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

Issue 01 (2008-06-10)


2-11



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 FilesThis describes how to collect BTS log files for troubleshooting.

Prerequisitel l l

The LMT runs properly. The communication between the LMT and the BSC is normal. The communication between the BSC and the BTS is normal.NOTE

The following steps are taken as examples for logging in to the server.

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

2-12


Issue 01 (2008-06-10)

HUAWEI BSC6000 Base Station Subsystem BSS Troubleshooting Guidel


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.

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

----EndIssue 01 (2008-06-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 2-13



2.6.3 Collecting LMT Log FilesThis describes how to collect LMT log files for troubleshooting.

Prerequisitel l

The LMT runs properly. The communication between the LMT and the BSC is normal.

ProcedureYou can get the LMT log files from the LMT installation directory \BscObj\Office Name \LmtLog. ----End

2.7 Collecting GBAM/GOMU InformationThis 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 for troubleshooting. 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 ModelThis describes how to collect the information about the GBAM model from its label.

ProcedureSearch 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 ProcessesThis describes how to collect the running information about the GBAM/GOMU local processes for troubleshooting.2-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 01 (2008-06-10)



Context

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

ProcedureStep 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 ProcessesThis describes how to collect the running information about the GBAM/GOMU core processes for troubleshooting.

Context

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

Issue 01 (2008-06-10)


2-15



ProcedureStep 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/GOMUThis describes how to collect other information about the GBAM/GOMU for troubleshooting.

ContextNOTE

You can get other information about the GBAM/GOMU from the shared directory of the GBAM/GOMU.

Procedurel To get the history operation information about the user, do as follows: 1. 2. 3. l 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. Run the cp .bash_history /BSC6000/install command to copy the .bash_history file to the shared directory of the GBAM/GOMU. 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. 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. 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

To get the information about the abnormal restart of the GBAM/GOMU, do as follows: 1. 2.

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:Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 01 (2008-06-10)

2-16



1. 2. 3. 4. l

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. Run the cd /var/log/samba command to enter the /var/log/samba directory. Run the cp log.smbd /BSC6000 command to copy the log.smbd file to the shared directory of the GBAM/GOMU. 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. 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. Run the lspci | grep Ethernet command. After the result is displayed, capture it using a relevant application, and save it for future use.

To get the information about the Ethernet cards of the GBAM/GOMU, do as follows: 1. 2.

----End

2.8 Collecting Messages Traced on the BSCThis describes how to collect signaling messages and user message on the BSC for troubleshooting.

Prerequisitel l l

The LMT runs properly. The communication between the BSC and the BTS is normal. The communication between the BSC and the MSC is normal.

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

ProcedureFor the detailed operations, refer to Configuring Message Tracing. ----End

2.9 Collecting TRACE Files of the M2000This describes how to collect the TRACE files of the M2000 server and M2000 client for troubleshooting.Issue 01 (2008-06-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 2-17



Procedurel Collect the TRACE file of the M2000 server. 1. 2. Visit the directory IP address of the M2000 server/export/home/omc/var/logs through FTP. 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.

CAUTIONTo 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 InformationThis describes how to collect the channel status information for troubleshooting.

Prerequisitel l l

The LMT runs properly. The communication between the LMT and the BSC is normal. The communication between the BSC and the BTS is normal.

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

2-18


Issue 01 (2008-06-10)



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 InformationThis describes how to collect bar code information of a BSC board for troubleshooting.

Prerequisitel l

The LMT runs properly. The communication between the LMT and the BSC is normal.

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

Issue 01 (2008-06-10)


2-19



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 InformationThis des

54461517 BSS Troubleshooting Guide V900R008C01 01

Documents

Transcript of 54461517 BSS Troubleshooting Guide V900R008C01 01