BSC6800 Troubleshooting

7/28/2019 BSC6800 Troubleshooting

1/30

Huawei Confidential. All Rights Reserved

BSC6800 troubleshooting

ISSUE 1.0


2/30

Internal Use2

Objectives

Upon completion of this course, you will be

able to:

Understand the different categories of

BSC6800 faults

Master the procedures for BSC6800

troubleshooting


3/30

Internal Use3

References

Huawei BSC6800 troubleshooting

manual


4/30

Internal Use4

Chapter 1 Overview

Chapter 2 Loading troubleshooting

Chapter 3 Interface troubleshooting

Chapter 4 traffic troubleshooting

Chapter 5 Operation troubleshooting


5/30

Internal Use5

General Flow of Troubleshooting

Generally, troubleshooting should go through four stages:


6/30

Internal Use6


Step 1: Information collection

As fault information provides the basis for troubleshooting,

BSC6800 provides tools to help in acquiring information about

faults.

Alarm Information Analysis

Indicator Status Analysis

Interface & Signaling Tracing

Test/Loopback


7/30Internal Use7


Step 2: Fault Definition

After acquiring information about the fault, the next step is todetermine the scope and category of the fault .BSC6800 has four

different categories of faults


8/30Internal Use8


Step 3: Fault Locating

We should go in deep to locate the source of the trouble

Referenced cases (troubleshooting manual )

Contact Huawei technical support .


9/30Internal Use9


Step 4: Fault Clearing

After locating the source of the fault we should follow the proper

methods to fix the fault (repair cables, replace boards, check

configuration data, etc.)


10/30Internal Use10

summary

To troubleshoot faults in RNC we should first collect information about the

fault then define the category of that fault then locate the real source for thisfault and the last step is to follow the proper way to remove that fault


11/30Internal Use11

Chapter 1 Overview






12/30

Internal Use12

Loading faults

Loading faults may occur during system commissioning or systemresetting.

The common faults include:

BAM Failing to Receive BOOTP Request

No BOOTP Response from BAM

BAM Failing to Receive TFTP Request Loading Abnormality of Boards in WRBS

Loading Abnormality of Boards in WRSS


13/30

Internal Use13

Loading Brief Introduction


14/30

Internal Use14

Loading Faults Description

When loading, the BOOTP request does not appear in load

window on the BAM .

Possible causes:

Possible cause Remarks

The configuration of the external network IPaddress of WMPU does not exist on BAM

None

Failure of the network between BAM and

WRSS, or failure of the optical fiber

connecting WMUX and WRSS

The network between BAM and WRSS provides part of the

path for loading and the optical fiber is the bearer of the

loading path between WMUX and WRSS

Optical port on WLPU in WRSS is deactivated. If the optical interface is deactivated, the optical connectionbetween WRSS and WMUX will be a failure

WBIE (WOSE, WOME , WXIE or WTIE),

WMUX, WSPU, or WFMR failureNone


15/30

Internal Use15

Loading Faults

Locating and troubleshooting

Ping the IP address of WMPU from the BAM to check whether the

network is ok. If not, check the status of intra-netcard indicator of

the BAM. If the light is not shining, check the network cable

between the BAM and the WRSS.

Check whether the port of WLPU and the WMUX boards is the

same type, and the optical fiber between them is suitable, i.e.

Single mode or Multimode Check whether the boards in the WRSS are running well

Check whether WMUX board runs well or not

Check whether WSPU, WFMR or WBIE work


16/30

Internal Use16

Chapter 1 Overview






17/30

Internal Use17

Interface link faults Troubleshooting

Interface link faults refer to the faults in the connections betweenBSC6800 and other equipment such as NodeB and CN.


Iub Interface Signaling Link Fault

Iu Interface Link Fault

Iur Interface Link Fault

Intermittent SAAL Link Failure

AAL2 Connection Setup Failure

IPoA Link Fault


18/30

Internal Use18

Signaling link faults in the Iub interface

Description:

The signalling link faults over Iub interface link result in cellsetup failure or location update failure after cell setup Possible

cause:

The Physical Link blocks.

Some problems on data configuration

Locating and troubleshooting Check whether the status of UNI link or IMA group (DSP

UNILNK/DSP IMAGRP) is faulty. You can locate the fault by

setting local loop and remote loop. (SET DS1LOP) . If the

transmission links are faulty, contact the transmission

maintenance staff for solution.

If the physical link works well, the error must be the data

configuration. Check whether the E1 port and the PVC are

accordant with the NodeBs. (LST SAALLNK)


19/30

Internal Use19

Chapter 1 Overview






20/30

Internal Use20

Service faults troubleshooting

Service faults refer to the faults that disable the BSC6800 from

performing UMTS services. They can be further divided into cell

faults, access faults, CS faults and PS faults.

cell faults include faults during cell setup and after cell setup

(eg. UE can not be normally accessed after cell setup is completed)

Access faults (eg. UE might not access the network when it is just

powered on, or the UE drops out of the network after it worked

normally after power on) CS faults (eg.Calls Cannot Be Connected, No Voice after Calling

Setup, Intermittent Voice)

PS faults (eg. Data Rate Drops Sharply, Data Service Stops

Suddenly)


21/30

Internal Use21

Cell setup faults

NBAP_AUDIT_REQ

NBAP_CELL_SETUP_REQ

NBAP_CELL_SETUP_RSP

NBAP_COMM_TRANSP_CH_SETUP_REQ

NBAP_COMM_TRANSP_CH_SETUP_RSP

NBAP_SYS_INFO_UPDATE_REQ

NBAP_SYS_INFO_UPDATE_RSP

NBAP_AUDIT_RSP

NodeB RNC

Cell setup signaling procedure


22/30

Internal Use22

Cell setup faults

Description

No NBAP_AUDIT_REQ message sent to the NodeB of thetarget cell is found in Iub standard interface message tracing

shown in O&M system.

Possible causes

WFMR abnormal

Iub interface abnormal Locating and troubleshooting

Check whether there are WFMR alarms and DSP-related

alarms.

If so, clear the alarms.

Check the Iub interface link.


23/30

Internal Use23

UEs of Some Type Cannot Access Cell

Description

UEs of some type cannot access cell while UEs of other

types can

Possible cause and troubleshooting

This type of UEs require the cell to be accessed must have

an intra-frequency neighboring cell; otherwise, cell access

will fail.

This fault is not a network fault but due to the UEs specialrequirement for the cell to be accessed. Therefore, it is

recommended to configure the intra-frequency neighboring

cell for each another


24/30

Internal Use24

Chapter 1 Overview






25/30

Internal Use25

Background knowledge

The system consists of three parts --FAM, BAM system and LMT system.

BAMWRSS

M2000

Ethernet

LMT

WRBS

Ethernet

FAM

IPoA


26/30

Internal Use26

Operation Troubleshooting


BAM Installation Faults.

BAM Operation Faults

BAM Dual-Server System Faults

LMT Failing to Log on to BAM

LMT Operation Faults


27/30

Internal Use27

The SNTP Server failure

Fault Description

The SNTP Server fails to start after the BAM software is installed.

Open sntpserver.log

LMT l i f lt


28/30

Internal Use28

LMT login fault

Description The LMT cant log in BAM.

Possible cause and troubleshooting

Check whether the network channel is faulty.

Check whether the BAM is running well.

Check whether The user name and password are right.


29/30

Internal Use29

Summary

RNC has four categories of faults:

1-loading faults

2-Interface link faults

3-service faults

4-O&M faults


30/30

Internal Use

Documents

BSC6800 Troubleshooting