UTRAN Trainning Troubleshooting

2012

General Introduction to

BSC 6900 Operation and

Maintenance

BSC68-69 Series

UTRAN Trainning Troubleshooting

FOREWORD
This training mainly provides the elementary
methods and methods to locate common faults of
RNC

2012

C ONTENTS
1. Troubleshooting Overview
2. Collecting Fault Location Data
3. Troubleshooting Cases

Page3

BSC68-69 Series

Page4

UTRAN Trainning Troubleshooting

TROUBLESHOOTING OVERVIEW

2012

TROUBLESHOOTING OVERVIEW

Step 1: Collecting Fault Information

RAN
Troubleshooting
Process

Page5

BSC68-69 Series

Information Item

Collection Method

Fault symptoms, as well as the

occurrence time, place, frequency

Consult the customer service

center

Running state of the equipment,

operations and related results before the
fault occurrence, and measures taken
afterwards

Consult the O&M staff

Alarms and associated alarms, states of

board LEDs

Observe board indicators and

alarm management system on
the LMT

Area and impact of the fault

Perform service demonstration,

performance measurement, and
interface and signaling tracing

Page6

UTRAN Trainning Troubleshooting

2012

TROUBLESHOOTING OVERVIEW

TROUBLESHOOTING OVERVIEW

Step 2: Defining Fault Area and Type

Clock faults

Functional subsystem
faults

Interface link faults

RF performance faults

RAN faults
Voice faults
VP faults
Service faults

PS faults
Access faults
Handover faults

Page7

BSC68-69 Series

Step 3: Diagnosing Fault Causes(1)

Locating faults in the functional subsystem
Troubleshoot these faults through board LEDs (which will blink
abnormally), alarms, and error prompts
Locating faults in services
For faults in voice services or packet switched services
check the Iu, Iub, and Uu interfaces in turn and then
determine whether the fault occurs to the RAN based on the
symptoms on the interface
If the fault occurs to the internal component of the RAN, you
should further locate it
For faults in handover or access to the network
start the signaling tracing and comparing it with the
protocols to locate the fault
Page8

UTRAN Trainning Troubleshooting

TROUBLESHOOTING OVERVIEW
Step 3: Diagnosing Fault Causes (2)
Common Fault Location Methods
user tracing

interface signaling tracing

traffic measurement
alarm analysis
test analysis
network packet catchers
comparison and double replacement

GENEX series tools and OMStar

Page9

BSC68-69 Series

2012

TROUBLESHOOTING OVERVIEW
Step 4: Clearing the Fault
Checking the cables, replacing the boards, modifying the
data configuration, switching over the systems, and
resetting the boards
Different procedures should be applied to different
faults
Reviewing the whole troubleshooting process
Step 5: Checking the Equipment or Services
Checking whether the system works properly by
querying the states of board LEDs and alarm LEDs
Performing dialing test to ensure that the services are
operational
Page10

UTRAN Trainning Troubleshooting

TROUBLESHOOTING OVERVIEW
Step 6: Contacting Huawei for Technical Support
Collect necessary fault information and contact Huawei
for technical support
Huawei Contact Information
Telephone: (86-755) 28560000
Fax: (86-755) 28560111
E-mail: support@huawei.com
Website: http://support.huawei.com

Page11

BSC68-69 Series

2012

C ONTENTS
1. Troubleshooting Overview
2. Collecting Fault Location Data
3. Troubleshooting Cases

Page12

UTRAN Trainning Troubleshooting

COLLECTING RNC FAULT LOCATION DATA

Types of RNC Fault Location Data
Error logs from the RNC FAM
RNC alarm data
Error logs from a BAM server
Operation Logs
RNC Self-Diagnostic Output Data
Call Data Record (CDR)
Signaling tracing messages
RNC configuration data
Page13

BSC68-69 Series

2012

COLLECTING RNC FAULT LOCATION DATA

Collecting Error logs from the RNC FAM
Collecting text log files
The file path is BSC6800 Installation Directory
BAM\Common\Famlog\fmt
File format:
FNLOGyyyymmddhhmmss_yyyymmddhhmmss.log.zip
FN: subrack number, 2 digits
yyyy: year mm: month dd: day hh: hour mm: minute ss:
second
Collecting CHR data (Call History Record)
The file path is BSC6800 Installation Directory
BAM\Common\Famlog\txt
File format:
FNLOGyyyymmddhhmmss_yyyymmddhhmmss.log.zip
Page14

UTRAN Trainning Troubleshooting

COLLECTING RNC FAULT LOCATION DATA

Collecting RNC alarm data
The past and present RNC alarm data are recorded on the
LMT, which indicates the running or changing status of the
RNC
Open the Alarm Browse window and select the fault alarms.
Right-click and select Save All Alarms. Save them as .txt files
Collecting Error logs from a BAM server
Error logs from a BAM server include the event logs, SQL
Server logs, and BAM module running logs
Run the COL LOG command on the LMT, the log file name
and file path will be displayed
Page15

BSC68-69 Series

2012

COLLECTING RNC FAULT LOCATION DATA

Collecting Operation Logs
Run the EXP LOG command on the LMT
The generated file is saved in BAM main eara path\FTP

The file is named as RNC-Y2008M01D09H13N01S52Y2008M05D09H13N02S09-OLOG.txt

Collecting RNC Self-Diagnostic Output Data
Running the TST SYS command on the LMT, the system can
automatically detect the fault in the devices or signaling links
The self-diagnostic result is saved in the BAM in \LOADDATA\FAD on
the BAM server
WRBS self-diagnostic file: WRBS**FadResultYYYY-MMDD-HHMM.txt

Page16

WRSS self-diagnostic file: WRSS**FADRESULTYYYY-MMDD-HHMM.txt

UTRAN Trainning Troubleshooting

COLLECTING RNC FAULT LOCATION DATA

Collecting Call Data Tracing Message (CDT)

Start the LMT and click the Maintenance tab in

the left pane. Select CDT
When the CDT tracing window is displayed, enter
the IMSI number in the IMSI box. Click OK to
start tracing
Call the UE to obtain the call detail message
The message can be automatically saved as a file on
the LMT under a constant directory

Page17

BSC68-69 Series

2012

COLLECTING RNC FAULT LOCATION DATA

Collecting Signaling tracing messages on standard interface
Trace the messages on standard interfaces on the LMT
Save the messages in the file under the LMT installation
directory
Collecting RNC configuration data
Run the EXP CFGMML command on the LMT
The generated file is saved in BAM main area path\FTP
The default file is named as CFGMMLYYYYMMDDHHMMSS.txt

Page18

UTRAN Trainning Troubleshooting

PUSH-BUTTON RNC DATA COLLECTION

2012

C ONTENTS

Push-Button RNC Data Collection Guidelines

Run the COL LOG command on the LMT

The returned messages include the file path and
file name for saving fault data

1. Troubleshooting Overview
2. Collecting Fault Location Data
3. Troubleshooting Cases

Page19

BSC68-69 Series

Page20

10

UTRAN Trainning Troubleshooting

2012

TROUBLESHOOTING CASES
Refer to Product Manual of <RAN
Troubleshooting Guide>

Page21

BSC68-69 Series

11

UTRAN Trainning Troubleshooting

OBJECTIVES

2012

C ONTENTS

Upon completion of this course, you will be able to:

Describe RAN troubleshooting process
Outline E1/T1 fault typical handling
Outline FE/GE fault typical handling

1. Troubleshooting Overview
2. E1/T1 Fault Troubleshooting
3. FE/GE Fault Troubleshooting

Page23

BSC68-69 Series

Page24

12

UTRAN Trainning Troubleshooting

2012

RAN TROUBLESHOOTING PROCESS

Start
Collecting fault information

Determining the fault area and types

Diagnosing fault causes

Clearing the faults

The services
are resotred?

COLLECTING FAULT INFORMATION

No

Fault symptoms
Time, location, and frequency
Area and impact
Running status of the equipment before a fault occurs
Operations and related results before a fault occurs
Measures and related effects after a fault occurs
Alarms and associated alarms when a fault occurs
States of board LEDs when a fault occurs

Contacting Huawei for

Technical Support

Yes

End
Page25

BSC68-69 Series

Page26

13

UTRAN Trainning Troubleshooting

2012

DETERMINING THE FAULT AREA AND TYPE

DIAGNOSING FAULT CAUSES

RAN faults

Faults in the
functional subsystem

Faults in services

Faults in RAN radio

frequency performance

Faults in RAN interface links

Faults in RAN clocks

Faults in handover

Faults in network access

Faults in packet switched

services

BSC68-69 Series

Faults in VP services

Faults in voice services

Page27

Locating faults in the functional subsystem

Base on LED information, alarm handling suggestions, or
error prompts
Locating faults in services
CS or PS service fault
Check the Iu, Iub, and Uu interfaces
Check the RNP/RNO parameters
Handover or access fault
Start the signaling tracing and comparing it with the
protocols

Page28

14

UTRAN Trainning Troubleshooting

2012

CLEARING AND VERIFYING THE FAULT

HUAWEI TECHNICAL SUPPORT

Clearing the Fault

Modifying the data configuration

Switching over the systems
Checking the cables
Replacing the boards

Telephone: 0086-755-28560000
Fax: 0086-755-28560111
E-mail: support@huawei.com
Website: http://support.huawei.com

Verifying the Fault

After the faults clearing, check LEDs and alarms,
and perform dialing test to ensure that the
services are operational
Page29

BSC68-69 Series

Page30

15

UTRAN Trainning Troubleshooting

QUESTIONS

1. How to collect fault information? please list

at least 3 ways.
2. How to get the product manual of latest
version?

2012

C ONTENTS
1. Troubleshooting Overview
2. E1/T1 Fault Troubleshooting
3. FE/GE Fault Troubleshooting

3. Some customers complain that it is very hard

to make a success call at about 11:00~12:00
AM, and these complains just occurs in a
small area. Based on the information, what
will you do?
Page31

BSC68-69 Series

Page32

16

UTRAN Trainning Troubleshooting

C ONTENTS

2012

E1/T1 OVERVIEW
Bit rate: 2048kbit/s

2. E1/T1 Fault Troubleshooting

2.1 E1/T1 Overview

Impedance:
120 ohm, balance, twisted pair cable
75 ohm, unbalance, coaxial cable

2.2 E1/T1 Typical Fault

Line code:HDB3 or AMI

2.3 E1/T1 Fault Typical Handling

Frame structure:
CRC4 Multi Frame
Double Frame

Plastic jacket
Metallic shield
Dielectric isolator
Centre core

Scramble Switch: On or Off

Page33

BSC68-69 Series

Page34

17

UTRAN Trainning Troubleshooting

C ONTENTS
2. E1/T1 Fault Troubleshooting
2.1 E1/T1 Overview
2.2 E1/T1 Typical Fault
2.3 E1/T1 Fault Typical Handling

Page35

BSC68-69 Series

2012

E1/T1 TYPICAL FAULT

Configuration Mismatch (Frame Structure,

Line Code, Scramble)
Impedance Fault (E1/T1 mode DIP Switch,
grounding)
Physical Connection Fault (wrong connection,
cross connection)
Transmission Quality Fault (Bit Error Rate Too
High, Excessive Slip Frames)
Page36

18

UTRAN Trainning Troubleshooting

2012

PHYSICAL CONNECTION FAULT

C ONTENTS
2. E1/T1 Fault Troubleshooting
2.1 E1/T1 Overview

L1_TX

L1_RX

L1_RX

L1_TX

B1

L1_TX

L1_RX

L1_RX

L1_TX

2.2 E1/T1 Typical Fault

B1

2.3 E1/T1 Fault Typical Handling

A

Page42

BSC68-69 Series

L2_TX

L2_RX

L2_RX

L2_TX

B2

L2_TX

L2_RX

L2_RX

L2_TX

B2

Page43

19

UTRAN Trainning Troubleshooting

E1/T1 FAULT TYPICAL HANDLING

Querying Alarm
Querying E1/T1 State
Loop back
Offline Test
Online Test (Only for NodeB)

Page44

BSC68-69 Series

2012

QUERYING E1/T1 STATE

NodeB side, DSP E1T1 to query:
E1/T1 link running state

RNC side, DSP E1T1 to query:

link running state, link type, loop back type

line impedance
clock mode
TX frame format, expected RX frame format
TX line coding mode, RX line coding mode
Error count

Page45

20

UTRAN Trainning Troubleshooting

2012

LOOP BACK

ONLINE TEST (ONLY FOR NODEB)

SET E1T1LOP

NodeB: STR E1T1ONLTST

NOLOOP
A

L1_TX

L1_RX

L1_RX

L1_TX

when MML is

LOCAL
A

BSC68-69 Series

Figures show
the states

REMOTE

Page46

Note:

L1_TX

L1_RX

L1_RX

L1_TX

L1_TX

L1_RX

L1_RX

L1_TX

executed on
A side

Not interruption to service

Applicable to line with bit errors but free from
faults
If the Periodical Report Switch is "OFF", the test
result will be reported only after the STR
E1T1ONLTST is executed

NodeB: STP E1T1ONLTST

Page47

21

UTRAN Trainning Troubleshooting

2012

OFFLINE TEST

OFFLINE TEST

Mode1:
1. RNC: SET E1T1LOP (REMOTE)

Mode2
1. NodeB: SET E1T1LOP (REMOTE)
TX

RX

RX

TX

TX

RX

RX

TX

RNC

2. NodeB: STR E1T1OFFLTST

RNC

NodeB

3. NodeB: STP E1T1OFFLTST

Note: DO NOT forget to stop E1T1 test!
DO NOT forget to set loopback as
NOLOOP after the test!

Page49

BSC68-69 Series

Success

Failed

TX

RX

RX

TX

TX

RX

RX

TX

NodeB

NodeB

RNC

2. RNC: STR E1T1TST

3. RNC: DSP E1T1TST
4. RNC: STP E1T1TST
Note: DO NOT forget to stop E1T1 test!
DO NOT forget to set loopback as
NOLOOP after the test!
NodeB

RNC

BER=20%

Page51

22

UTRAN Trainning Troubleshooting

2012

E1/T1 FAULT HANDLING PRINCIPLE

QUESTIONS

Query first, Handling second

Loop back first, Test second
Online test first, Offline test second
Far first, Near second
TX

RX

RX

TX

TX

RX

RX

TX

TX

RX

RNC

RNC

TX

RX

TX

TX

RX

TX

RX

TX

RNC

BSC68-69 Series

TX

A RX
A RX

RNC

Page53

TX

A RX

A RX

RX
TX
RX
TX
RX

TX

B RX

TX

B RX

TX

TX

B RX

RX

TX

TX

B RX

RX

Case1: There are 10 NodeB connect to a same

RNC subrack, one of the NodeB has 4E1s, all
the E1s BER is too high to provide normal
service, but other NodeBs transmission is
normal. What kind of fault it is? How to
handle the fault?

NodeB
TX
RX
NodeB
TX
RX
NodeB
TX
RX
NodeB
TX

Case2:In case1, for the NodeB, if just 1E1 is in

high BER, and other E1s are normal. What
kind of fault it is? How to handle the fault?
Page54

23

UTRAN Trainning Troubleshooting

C ONTENTS

2012

FE/GE OVERVIEW

1. Troubleshooting Overview
2. E1/T1 Fault Troubleshooting
3. FE/GE Fault Troubleshooting

Straight
Through
Cable
Diagram
Crossover
Cable
Diagram

Page55

BSC68-69 Series

Page56

24

UTRAN Trainning Troubleshooting

BOARD WITH FE/GE

WMP

T
NodeB

UTRP

3900

2012

FE/GE FAULT TYPICAL HANDLING

Checking the cable and connector

Checking the parameter of the FE
MML: DSP ETHPORT , LST ETHPORT

PING
Fault Isolation

UTRP

PC connect to
NodeB, Check the
port alarm

Alarm is cleared

Yes

Peer fault
No

No

BSC681
0

FG2

PC connect to Peer,
Check PCs ETH
LED

LED is On
Yes

Page57

BSC68-69 Series

NodeB ETH port

fault. Use RST
ETHPORT and RST
BRD, check the chip
abnormal alrm

Page58

25

UTRAN Trainning Troubleshooting

2012

S UMMARY
RAN Troubleshooting Process
Typical Handling for E1/T1 Fault
Typical Handling for FE/GE Fault

Page60

BSC68-69 Series

26