nodeb maintenance manual-troubleshooting.pdf

8/14/2019 NodeB Maintenance Manual-Troubleshooting.pdf

http://slidepdf.com/reader/full/nodeb-maintenance-manual-troubleshootingpdf 1/50

Chapter 1 General Troubleshooting Procedure and Methods 1-1....................

1.1 About This Chapter 1-1................................................................................

1.2 Maintenance Personnel Qualifications 1-1...................................................

1.3 Major Instruments and Meters 1-2................................................................1.4 Troubleshooting Procedure 1-2....................................................................

1.4.1 Collecting Fault Information 1-3...........................................................

1.4.2 Locating and Clearing Faults 1-4.........................................................

1.4.3 Verifying Troubleshooting Result 1-4...................................................

1.5 Methods for Locating Faults 1-4...................................................................

1.5.1 Analyzing Original Information 1-4.......................................................

1.5.2 Analyzing Alarm Information 1-5..........................................................

1.5.3 Analyzing Indicator States 1-5.............................................................

1.5.4 Analyzing Interface Signaling Tracing Message 1-5............................1.5.5 Analyzing Faults with Apparatus and Meters 1-5.................................

1.5.6 Analyzing Faults Through Comparison and Interchange 1-6...............

1.5.7 Analyzing Faults with Performance Measurement andStatistics 1-6..................................................................................................

1.6 Contacting Huawei Technical Support 1-6...................................................

1.6.1 Technical Support System 1-6.............................................................

1.6.2 Contact Approaches to Technical Support 1-6....................................

1.6.3 Service Flow for Customer Complaints 1-7..........................................

1.6.4 Preparations before Seeking Technical Support 1-7...........................

Chapter 2 Locating and Handling Cell Faults 2-1...............................................


2.2 Fundamental Knowledge 2-1........................................................................

2.3 Logical Cell Cannot Be Set Up 2-1...............................................................

2.4 The 120-ohm E1 Cable is Abnormal 2-3......................................................

2.5 Cell Cannot Be Set up and Multi-Frame Out-of-Sync Alarm IsReported at RNC 2-5..........................................................................................

2.6 Only One Cell Can Be Set up After Modification of Cell Radius 2-6............2.7 RNC Deletes Cell after Receiving Cell and Common TransportChannel Setup Response Message from NodeB 2-6.........................................

2.8 RNC Sends a CELL SETUP REQUEST Message and NodeBResponds with a CELL SETUP FAIL Message Directly 2-8...............................

Chapter 3 Locating and Handling Service Faults 3-1.........................................


3.2 UE Sends RRC CONN REQ and RNC Responds with RRC CONNREJ 3-1...............................................................................................................

3.3 Calls Are Dropped Due to Soft Handover Failure 3-2..................................

3.4 Only Hard Handover Succeeds during High-Speed Services 3-2................



3.5 Multiple 384 kbps Data Services Fail to Be Activated 3-3............................

Chapter 4 Locating and Handling O&M Faults 4-1.............................................


4.2 Downloading Software Lasts Too Long or Fails 4-1.....................................4.3 Starting Built-in FTP Server Fails 4-2...........................................................

4.4 Logging in to NodeB in Near End Fails after NodeB Is Restartedupon Completion of Downloading Data Configuration File 4-3...........................

4.5 Signals in a Cell Are Weak 4-4.....................................................................

4.6 Copying Files through Telnet Fails 4-5.........................................................

Appendix A Flow Chart A-1...................................................................................

A.1 Overview A-1................................................................................................

A.2 Cell Setup A-2..............................................................................................

A.3 Location Updating A-4..................................................................................

A.4 Call Initiation A-6..........................................................................................

A.5 Call Termination A-9.....................................................................................

A.6 PDP Activation & Deactivation A-12...............................................................

Index .................................................................................................................



HUAWEI

WCDMA NodeB

Maintenance Manual - Troubleshooting

V100R003



WCDMA NodeB

Maintenance Manual

Volume Troubleshooting

Manual Version T2-030377-20040930-C-1.31

Product Version V100R003

BOM 31033277

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support

and service. Please feel free to contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, P. R. China

Postal Code: 518129

Website: http://www.huawei.com

Email: [email protected]



Copyright © 2004 Huawei Technologies Co., Ltd.

All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any

means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks

, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800,

TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN,

HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye,

Lansway, SmartAX, infoX, TopEng are trademarks of Huawei Technologies Co.,

Ltd.

All other trademarks mentioned in this manual are the property of their respective

holders.

Notice

The information in this manual is subject to change without notice. Every effort has

been made in the preparation of this manual to ensure accuracy of the contents, but

all statements, information, and recommendations in this manual do not constitute

the warranty of any kind, express or implied.



Summary of Updates

This section provides the update history of this manual and introduces the contents of

subsequent updates.

Update History

This manual is updated for a major product version to maintain consistency with system

hardware or software versions and to incorporate customer suggestions.

Manual Version Notes

T2-030377-20040220-C-1.30 Initial commercial release

T2-030377-20040930-C-1.31 Second commercial release

Updates of Contents

Updates between manual versions are cumulative. Therefore, the latest manual

version contains all updates made to previous versions.

Updates Made between Versions 1.31 and 1.30

1) Adding index.

2) Adding "About This Chapter" in every chapter.

3) Simplifying and optimizing the contents in Chapter 1.

4) Optimizing the procedure of handling each type of faults and presenting specific

command to be used.



About This Manual

Release Notes

The product version corresponds to the manual is WCDMA NodeB V100R003.

Organization

This manual includes four chapters, one appendix and one index:

Chapter 1 General Troubleshooting Procedure and Methods: present major methods

and devices for troubleshooting.

Chapter 2 Cell Faults: presents major troubleshooting methods for cell faults.

Chapter 3 Service Faults: presents major troubleshooting methods for service faults.

Chapter 4 Operation & Maintenance Faults: presents major troubleshooting methods

for operation & maintenance faults.

Appendix A Flow Chart: presents several major flow charts

Index Lists indexes of the manual.

Intended Audience

The manual is intended for the following readers:

Technical supporters for WCDMA system

Telecommunication management personnel

WCDMA system engineers

Conventions

The manual uses the following conventions:

I. General conventions

Convention Description

Arial Normal paragraphs are in Arial.

Arial Narrow

Warnings, cautions, notes and tips are in Arial Narrow.



Convention Description

Bold Headings, Command, Command Description are in boldface.

Terminal Display Terminal Display is in Courier New; message input by the user via the

terminal is in boldface.

II. Symbols

Eye-catching symbols are also used in the manual to highlight the points worthy of

special attention during the operation. They are defined as follows:

Caution: Means reader be extremely careful during the operation.

Note: Means a complementary description.



Maintenance Manual – TroubleshootingWCDMA NodeB Table of Contents

i

Table of Contents Table of Contents .............................................................................................................................. I Chapter 1 General Troubleshooting Procedure and Methods.................................................. 1-1

1.1 About This Chapter............................................................................................................ 1-1 1.2 Maintenance Personnel Qualifications .............................................................................. 1-1 1.3 Major Instruments and Meters........................................................................................... 1-2 1.4 Troubleshooting Procedure ............................................................................................... 1-2

1.4.1 Collecting Fault Information .................................................................................... 1-3 1.4.2 Locating and Clearing Faults .................................................................................. 1-4 1.4.3 Verifying Troubleshooting Result ............................................................................ 1-4

1.5 Methods for Locating Faults .............................................................................................. 1-4 1.5.1 Analyzing Original Information ................................................................................ 1-4 1.5.2 Analyzing Alarm Information ................................................................................... 1-5 1.5.3 Analyzing Indicator States....................................................................................... 1-5 1.5.4 Analyzing Interface Signaling Tracing Message..................................................... 1-5 1.5.5 Analyzing Faults with Apparatus and Meters.......................................................... 1-5 1.5.6 Analyzing Faults Through Comparison and Interchange........................................ 1-6 1.5.7 Analyzing Faults with Performance Measurement and Statistics........................... 1-6

1.6 Contacting Huawei Technical Support .............................................................................. 1-6 1.6.1 Technical Support System ...................................................................................... 1-6 1.6.2 Contact Approaches to Technical Support ............................................................. 1-6 1.6.3 Service Flow for Customer Complaints................................................................... 1-7 1.6.4 Preparations before Seeking Technical Support .................................................... 1-7

Chapter 2 Locating and Handling Cell Faults............................................................................. 2-1 2.1 About This Chapter............................................................................................................ 2-1 2.2 Fundamental Knowledge................................................................................................... 2-1 2.3 Logical Cell Cannot Be Set Up .......................................................................................... 2-1 2.4 The 120-Ω E1 Cable is Abnormal...................................................................................... 2-3 2.5 Cell Cannot Be Set up and Multi-Frame Out-of-Sync Alarm Is Reported at RNC ............ 2-5 2.6 Only One Cell Can Be Set up After Modification of Cell Radius ....................................... 2-6 2.7 RNC Deletes Cell after Receiving Cell and Common Transport Channel Setup Response

Message from NodeB.............................................................................................................. 2-6 2.8 RNC Sends a CELL SETUP REQUEST Message and NodeB Responds with a CELL

SETUP FAIL Message Directly................................................................................................ 2-8 Chapter 3 Locating and Handling Service Faults ...................................................................... 3-1

3.1 About This Chapter............................................................................................................ 3-1 3.2 UE Sends RRC CONN REQ and RNC Responds with RRC CONN REJ ........................ 3-1 3.3 Calls Are Dropped Due to Soft Handover Failure.............................................................. 3-2



Maintenance Manual – TroubleshootingWCDMA NodeB Table of Contents

ii

3.4 Only Hard Handover Succeeds during High-Speed Services........................................... 3-2 3.5 Multiple 384 kbps Data Services Fail to Be Activated ....................................................... 3-3

Chapter 4 Locating and Handling O&M Faults........................................................................... 4-1 4.1 About This Chapter............................................................................................................ 4-1 4.2 Downloading Software Lasts Too Long or Fails................................................................ 4-1 4.3 Starting Built-in FTP Server Fails ...................................................................................... 4-2 4.4 Logging in to NodeB in Near End Fails after NodeB Is Restarted upon Completion of

Downloading Data Configuration File ...................................................................................... 4-3 4.5 Signals in a Cell Are Weak ................................................................................................4-4 4.6 Copying Files through Telnet Fails.................................................................................... 4-5

Appendix A Flow Chart.................................................................................................................A-1 A.1 Overview............................................................................................................................A-1 A.2 Cell Setup..........................................................................................................................A-2 A.3 Location Updating .............................................................................................................A-4 A.4 Call Initiation ......................................................................................................................A-6 A.5 Call Termination ................................................................................................................A-9 A.6 PDP Activation & Deactivation........................................................................................A-12

Index ................................................................................................................................................ i-1



Maintenance Manual – Troubleshooting WCDMA NodeB

Chapter 1General Troubleshooting Procedure and Methods

1-2

Routing between NodeB and other network elements

Internal signaling and data flow of NodeB

UMTS networking

Network structure and channel allocation of associated transport equipment

III. Ability in Equipment Operations To locate a fault effectively, you have to be certificated and be familiar with operations

associated with NodeB. It is advised that some serious faults be handled by the

personnel trained by Huawei.

In addition, you havev to keep in mind the following:

Which operations lead to partial or entire service failure.

Which operations cause damage to the equipment.

Which operations can be taken as emergency measures or backup measures.

1.3 Major Instruments and Meters You may need the following instruments and meters to help fault locating and

troubleshooting expecially when you cannot locate a fault either through alarm system

or O&M system:

Multimeter

NetHawk

Spectrum analyzer

Power meter

Antenna and feeder tester

1.4 Troubleshooting Procedure

Figure 1-1 shows general troubleshooting procedure.





1-3

Start

End

Collect fault

information

Clear the fault

Locate the fault

Verify the fault

Figure 1-1 General troubleshooting procedure

1.4.1 Collecting Fault Information

I. Fault Information to Collect Fault information collection is a prerequisite for troubleshooting, providing important

basis for fault locating. Before carrying out troubleshooting, collect the following fault

informaiton as more as possible:

Fault symptoms

Occurrence time, place and frequency

Fault coverage, category and associated consequences

Equipment running status before occurrence of a fault

Operations done on the equipment and the corresponding operating results

Alarms occurring when a fault takes place

Board indicator status when a fault occurs

Software version information and log information when a fault occurs Signaling tracing result (including the information of Uu, Iub and Iu interface) when

a fault occurs

Measures taken to handle the fault and the corresponding effect

II. Methods to Collect Fault Information Collect fault information in the following ways:

Inquire of the fault complainer or the staff at the customer service center about the

fault symptoms, fault occurrence time, place and frequency.





1-4

Inquire of the associated maintenance personnel about routine running status,

fault symptoms, operations done before the occurrence of the fault, measures

taken to handle the fault and the corresponding effect.

Obtain information about software/hardware running status through boardindicators, O&M system and alarm management system.

Locate the fault categories and consequences through service demonstration,

performance measurement, and interface/signaling tracing.

III. Points for Attention in Fault Information Collection

Keep the following items in mind when collecting fault information:

Make sure to collect the associated fault information to locate a fault correctly,

especially in case of a serious fault. Avoid random troubleshooting by all means.

Keep in touch with maintenance personnel of other offices or service departments

for information communication and technical aids.

Note:

Make analysis and judgment of a fault based on not only fault symptoms, but also various original

information collected, for example, system running log.

1.4.2 Locating and Clearing Faults NodeB faults falls into the following three categories:

Cell faults

Service faults

O&M faults

The procedure to diagnose faults is to define the range and category of a certain fault

based on the fault information.

Check whether there are corresponding alarms reported. If any, handle the alarms

according to alarm prompts. Otherwise, locate the faults according to fault symptoms

and clear them based on corresponding troubleshooting instructions.

1.4.3 Verifying Troubleshooting Result After clearing a fault, verify that you have correctly cleared the fault through the

troubleshooting methods suggested. This step is mandatory.

1.5 Methods for Locating Faults 1.5.1 Analyzing Original Information

Obtain original information from the following approaches:

Complaints of users and other offices





1-5

Fault information collected during maintenance

Information collected in the initial troubleshooting stage.

Original information analysis helps to locate fault coverage and determines fault

categories. If you are fully expeirenced, skip this step and go to fault locating.

1.5.2 Analyzing Alarm Information Alarm information refers to that output by the alarm control module in the NodeB. You

can collect alarm information through the following approaches::

Alarm tone

LED indicator

Alarm management system

Alarm information reported by alarm managenent system of LMT includes:

Alarm meaning

Possible causes

Handling suggestions

The above information covers various aspects such as hardware, softeware, RF,

transport, and so on. It provides a significant basis for troubleshooting.

1.5.3 Analyzing Indicator States

On each board in NodeB, there are running status indicators and alarm indicators.

They directly reflect working states of boards, circuits, links and nodes.

Analyzing indicator states is a procedure to locate a possible cause range for a fault in

the initial troubleshooting stage. Because indicator state analysis cannot provide all

possible informaition, it usually works with alarm informaitn analysis.

1.5.4 Analyzing Interface Signaling Tracing Message Interface signaling tracing plays an important role in locating service failures during call

connection or signaling coordination between NodeB and RNC. Generally, you can find

out the cause for a call failure directly from the tracing results.

You can trace Iub interface signaling by the standard interface tracing function of

NodeB O&M system. You can also carry out interface signaling tracing through devices

of a third party, such as NetHawk.

1.5.5 Analyzing Faults with Apparatus and Meters It is a common method to locate a fault with apparatus and meters. Since measurement

data obtained by using apparatus and meters reflects the essence of a fault visually,

apparatus and meters are widely used in power test, signaling tracing, waveform

analysis, bit error rate (BER) detection, and so on.





1-6

1.5.6 Analyzing Faults Through Comparison and Interchange You can compare the working status of a faulty part with that of a normal one to find out

causes. This method applies to the faults in a limited scope.

If you cannot locate a fault after replacing the possibly faulty parts, interchange the

possibly faulty parts (for example, boards or optical fibers) with the ones in normal

operation. After that, observe the running states of both to locate the fault. This method

applies to rather complex occasions.

1.5.7 Analyzing Faults with Performance Measurement and Statistics You can analyze some key performances and resources, such as CPU/DSP occupancy,

and E1 BER, by using the performance measurement and statistics function provided

by O&M system. Judge whether the system is in normal operation by comparing themeasurement results with the corresponding values of normal operation.

1.6 Contacting Huawei Technical Support If you cannot clear a fault by following the instructions in this manual in routine

maintenance or troubleshooting procedure, contact Huawei technical support

engineers.

1.6.1 Technical Support System Huawei Technical Support System includes:

Huawei Technical Support Department

Technical Support Center of Huawei local offices

Technical Support Website

Customer Service Center

1.6.2 Contact Approaches to Technical Support

Contact Huawei for technical support through:

Email: [email protected] Website: http://support.huawei.com

Note:

Contact approaches to Huawei local offices are available in the technical support website

http://support.huawei.com.





1-7

1.6.3 Service Flow for Customer Complaints

Huawei has developed a service flow for customer complaints. The following describes

Huawei service flow for you to ask for technical support efficiently.

I. Feeding back Problems

You can feed back problems of Huawei products by telephone, fax, regular mail, email,

and so on. You can also feed back your problems to engineers in Huawei local offices

who will record the problems in Huawei Problem Management System and take care of

the problem handling process.

II. Handling Problems

Customer Service Center distributes product problems to corresponding technical

support engineers. Upon receipt of the problems, technical support engineers contactthe corresponding maintenance personnel of the network of the complainer for more

information and then handle the faults in the following way:

The enginners instruct the complainer to clear the fault by phone if the fault is

caused by improper operations or if the fault is not a serious one and can be easily

cleared.

The engineers perform remote maintenance (if possible) if they cannot help to

remove the fault either by phone or by fax.

The engineers provide other aids to handle the faults, for example, field

maintenance, if they cannot help to remove the fault by phone, by fax or by remotemaintenance.

1.6.4 Preparations before Seeking Technical Support Before turning to Huawei technical support system for troubleshooting, make the

following preparations to handle the trouble more efficiently.

I. Collecting Fault Information

Collect the following fault information for efficient troubleshooting:

Office name (full name)

Contact person and telephone number

Fault occurrence time

Fault description

Host software version

Measures taken to clear a fault and the effect

Fault severity level and expected date for troubleshooting

II. Making Preparations for Debugging Make preparations for debugging before turning to Huawei technical support system for

troubleshooting help.



Maintenance Manual – Troubleshooting WCDMA NodeB Chapter 2 Locating and Handling Cell Faults

2-1

Chapter 2 Locating and Handling Cell Faults

2.1 About This Chapter

This chapter introduces cell fault locating and handling as follows:

Fundamental Knowledge

Logical Cell Cannot Be Set Up

The 120-Ω E1 Cable is Abnormal

Cell Cannot Be Set up and Multi-Frame Out-of-Sync Alarm Is Reported at RNC

Only One Cell Can Be Set up After Modification of Cell Radius

RNC Deletes Cell after Receiving Cell and Common Transport Channel Setup

Response Message from NodeB

RNC Sends a CELL SETUP REQUEST Message and NodeB Responds with a

CELL SETUP FAIL Message Directly

2.2 Fundamental Knowledge When local cell resources configured for NodeB are available, NodeB sends the

resource state to the RNC through either Resource State Indication procedure or Audit

procedure. Upon receipt of resource state information, the RNC initiates a Cell Setup

procedure to set up a logical cell. A cell provides normal services when thecorresponding logical cell has been set up and is available. Requirements associated

with cell setup include:

Parameters of NodeB local cells are correctly configured.

Board working state is logically available.

Transport data is correctly configured.

Transport links are properly connected.

Cell setup parameters configured in the RNC are reasonable.

When all the first three requirements are satisfied, the local cell of NodeB can be

regarded as available. When all the five requirements are satisfied, a logical cell can beset up successfully.

2.3 Logical Cell Cannot Be Set Up

I. Fault Symptoms 1) Symptom 1

The logical cell cannot be set up.

Use DSP CELL to query the local cell resources on the NodeB O&M system and

find that the local cell resources are available.




2-2

Use DSP CP to query the states of both NCP and CCP on the NodeB O&M system

and find that the states of both NCP and CCP are normal.

Use ADT RES to request the RNC for resource audit on NodeB O&M system. The

RNC does not send resource audit command, but continuously sends the NBAPRESET REQ message to the NodeB.

Start Iub interface tracing on the NodeB O&M system and the tracing message

shown in Figure 2-1 is displayed.

Figure 2-1 Iub interface tracing message

2) Symptom 2

The logical cell cannot be set up.

Use DSP CELL to query the local cell resources on the NodeB O&M system and

find that the local cell resources are available.

Use DSP CP to query the states of both NCP and CCP on the NodeB O&M system

and find that the states of both NCP and CCP are normal.

The RNC sends only a resource audit command but no CELL SETUP REQUEST

message.

II. Troubleshooting Clear the fault as described below.

For the first case:

Use DSP CP to query states of NCP and CCP on NodeB O&M system. If states of both

NCP and CCP are normal, it means both the physical layer (such as E1) and the link

layer (UNI and IMA) are normal and the most possible cause is that the configuration

data of NCP and CCP in the NodeB are inconsistent with that in the RNC.

1) Use LST CP to query data configured for NCP and CCP on NodeB O&M system,

especially their VPI and VCI.

2) Use LST IUBP to query data configured for NCP and CCP on RNC O&M system.




2-3

3) Compare the configuration for NCP and CCP in NodeB with that in the RNC. And

will find there is any inconsistency

4) Use RMV CP to remove the NCP and CCP on NodeB O&M system

5) Use ADD CP to add NCP and CCP on NodeB O&M system. modify them asconsistent with that in the RNC.

For the second case:

1) Check whether the maximum downlink power in the audit message from the

NodeB is smaller than that configured in the RNC. For example, if the maximum

downlink power from the NodeB is 398 (unit: 0.1 dBm) and the value configured in

the RNC is 400 (unit: 0.1 dBm), the logical cell cannot be set up.

2) On the O&M system , use MOD CELL to modify the maximum transmit power of cell

in the RNC to that no more than the reported value in NodeB.

3) If the logical cell can be set up successfully in this case, it indicates the fault has

been cleared. Otherwise, follow the next step to clear the fault.

4) On the NodeB O&M system, use DSP CELL to check whether the local cell ID is

consistent with that negotiated with the RNC.

5) If not, use RMV LOCELL to delete the cell on the NodeB O&M system..

6) On the NodeB O&M system, use ADD LOCELL to add a new local cell with the

local cell ID is the same as that negotiated with the RNC.

III. Verification After the measures above, if the cell setup between the RNC and the NodeB succeeds,

including cell setup, common transport channel setup and system message updating, itmeans you have cleared the fault.

2.4 The 120- E1 Cable is Abnormal I. Fault Symptoms

A 120-Ω E1 cable connects the NodeB to the RNC properly, and the data configuration

is correct. However, the state of the E1 cable state is abnormal when queried with DSP

E1T1.

II. Troubleshooting Generally, the fault is caused by incorrect setting of DIP switches on the NDTI and E1

lightning protection board. Therefore, clear the fault by correcting settings of DIP

switches. Figure 2-2 shows the DIP switches on the NDTI.

The grounding status of the Rx end of E1 cables are set on the two E1 lightning

protection boards on the top of the NodeB cabinet, as illustrated in Figure 2-3.

J4: used to set the grounding status of the Tx end of E1/T1 cables

J5: used to set the grounding status of the Rx end of E1/T1 cables




2-4

S7

S8

S11

S9

S10

S7

S8

S9

S10

S4

S3

S6

S5

J9

J2J2J2

J3

J21 J22

board indicators

Figure 2-2 DIP switches on NDTI

Figure 2-3 E1 lightning protection boards on cabinet top

Note:

For description of DIP switches on the NDTI, refer to board information in online help of NodeB O&M

system.




2-5

Clear the fault as follows:

1) Set digit 1 of the S11 to “ON” position, and digit 2 to “OFF” position.

2) Set digit 1, 2, 3, 4 of S3, S4, S5 and S6 to “OFF” position.

3) To set the Tx end as grounded, connect a customized DB25 female socket to J4.

4) To set the Rx end as grounded, connect a customized DB25 female socket to J5.

III. Verification

Use DSP E1T1WORKMODE to query E1 work mode on the NodeB O&M system. If the

line matching impedance of the query result is 120Ω, it means the fault has been

cleared.

Use DSP E1T1 to check whether the state of E1 cable is normal on the NodeB O&M

system. If yes, it means that the fault has been cleared.

2.5 Cell Cannot Be Set up and Multi-Frame Out-of-SyncAlarm Is Reported at RNC

I. Fault Symptoms

The fault has the following symptoms:

The tracing message of the Iub interface shows that the cell is deleted and set up

repeatedly. Meanwhile, there is multi-frame out-of-synchronization alarm in the

RNC and the alarm cannot be cleared.

Use DSP E1T1 to query the state of the E1 cable on the NodeB O&M system and

find that the state is normal.

II. Troubleshooting

The most possible cause for this fault is that E1 working mode in the NodeB is not

consistent with that in the RNC. Clear the fault in the steps described in the following:

1) Use DSP E1T1WORKMODE to query E1 work mode on the NodeB O&M system.

2) Use DSP E1T1 to query E1 work mode on the RNC O&M system.

3) Compare the two work modes.

4) On the NodeB O&M system, use SET E1T1WORKMODE to modify the E1 work

mode to be consistent with that in RNC.

III. Verification After the E1 working mode of the NodeB is consistent with that of the RNC, check

whether the multi-frame out-of-synchronization alarm in the RNC is automatically

cleared and whether the cell can be successfully set up.




2-6

2.6 Only One Cell Can Be Set up After Modification of CellRadius

I. Fault Symptoms

Before the modification of cell radius, both the two cells, cell 0 and cell 2, can be set up

normally. After their radius is modified from 256*78 m to 1536*78 m, cell 2 fails to be set

up.

On the NodeB O&M system, use DSP CELL to query the state of the local cell and find

that it is unavailable due to lack of baseband resources.

II. Troubleshooting The fault must be caused by lack of access resources. A set of access resources

includes an access ASIC and an access DSP. When the cell radius is smaller than or

equal to 384*78 m, a set of access resources can support three cells. When the cell

radius is greater than 384*78 m, it can support only one cell.


1) Check the number of NULPs.

2) If there is only one NULP and a cell whose radius is greater than 384*78 m is

required, Use ADD BRD to add one NULP on the NodeB O&M system, and insert

one NULP in NodeB cabinet.

3) Otherwise, on the NodeB O&M system, use MOD LOCELL to modify the radius

of both cells as smaller than or equal to 384*78 m.

III. Verification After the procedure above, both cells can be successfully set up.

2.7 RNC Deletes Cell after Receiving Cell and CommonTransport Channel Setup Response Message from NodeB

I. Fault Symptoms The RNC sends a CELL SETUP REQUEST message to the NodeB, and the NodeBreports a CELL SETUP RESPONSE message to the RNC. After that, RNC sends two

COMMON TRANSPORT CHANNEL SETUP REQUEST messages. Upon receipt of

two COMMON TRANSPORT CHANNEL SETUP RESPONSE messages from the

NodeB, the RNC then sends a CELL DELETION REQUEST message instead of a

SYSTEM INFORMATION UPDATE REQUEST message to the NodeB.

There is no alarm at the NodeB or the RNC.




2-7

II. Troubleshooting The fault lies on Iub interface user plane. In this case, perform the following steps to

check whether the user plane data configuration and hardware connection of the

NodeB is consistent with those at the RNC.


1) Use LST AAL2PATH to query data configuration of AAL2 path on the NodeB O&M

system.

2) Use LST AAL2PATH to query data configuration of AAL2 path on the RNC O&M

system.

3) Check whether the data configuration of the AAL2 path in the NodeB is consistent

with that in the RNC.

The data configuration is consistent. Go to step 7).

The data configuration is not consistent. Go to step 4).

4) If there is any inconsistency, use RMV AAL2PATH to delete the AAL2 path on the

NodeB O&M system.

5) On the NodeB O&M system, use ADD AAL2PATH to add an AAL2 path, and

modify data configuration as consistent with that in the RNC.

6) Check whether the fault is cleared. Refer to “III. Verification”.

The fault is cleared. The fault handling ends.

The fault is not cleared. Go to step 7).

7) Check that the E1/T1 or STM1 ports configured with AAL2 path between the

NodeB and the RNC are connected correctly.8) Re-connect them if they are not connected correctly.

9) Check whether the fault is cleared. Refer to “III. Verification”.

The fault is cleared. The fault handling ends.

The fault is not cleared. Go to step 10).

10) On the NodeB O&M system, query the ATM address of ALCAP configured in the

NodeB though LST AAL2NODE.

11) On the RNC O&M system, query the corresponding data of RNC through LST

AAL2RT.

12) Check whether the ATM address of ALCAP configured in NodeB is consistent with

that in RNC.

13) If not consistent, use RMV AAL2NODE to delete ALACP on the NodeB O&M

system.

14) Use ADD AAL2NODE to add ALCAP on the NodeB O&M system. The

configuration data at NodeB is consistent with that at RNC.

III. Verification After the procedure above, if Cell Setup procedure succeeds, including cell setup,

common transport channel setup and system message updating, it means the fault has

been cleared.




2-8

2.8 RNC Sends a CELL SETUP REQUEST Message andNodeB Responds with a CELL SETUP FAIL Message Directly

I. Fault Symptoms


Cell setup fails. The RNC sends a CELL SETUP REQUEST message to set up a

cell, but NodeB responds directly with a CELL SETUP FAIL message.

Use DSP CELL on the NodeB O&M system to query the state of the cell and find

that the local cell is available and the logical cell unavailable.

II. Troubleshooting


1) Check the cause value of the fault in the CELL SETUP FAIL message from the

NodeB to see whether it is “semantic error(4):01 48”.

2) If yes, check the UARFCN in the CELL SETUP REQUEST message through

standard interface tracing on the O&M system.

3) If the difference between the two UARFCN parameters is not 190*5, it indicates

the difference between frequencies configured in the RNC is not 190 MHz. In this

case, use MOD CELLSETUP to modify the uplink and downlink frequencies on

the RNC O&M system so that their difference is 190 MHz.

4) Use LST CELL to query the modification result on the RNC O&M system.

5) If the modification is effective, use ACT CELL to activate the cell. 6) Use LST LOCELLCFGQ to query local cell configuration on the NodeB O&M

system. Check cell radius and cell inner handover radius.

7) If cell radius is smaller than cell inner handover radius, the logical cell is

unavailable. Use MOD LOCELL to modify local cell parameters. Generally, the

cell inner handover radius is 2*78 m, and cell radius is the actual cell physical

radius.

III. Verification After the procedure above, the logical cell can be set up normally. The local cell and

logical cell are both available.



Maintenance Manual – TroubleshootingWCDMA NodeB

Chapter 3 Locating and Handling ServiceFaults

3-1

Chapter 3 Locating and Handling Service Faults 3.1 About This Chapter

NodeB-supported services include voice call service and call hold, PDP activation and

sustaining, soft handover, softer handover, inter-frequency hard handover,

intra-frequency hard handover, and so on.

This chapter introduces service fault locating and handling as follows:

UE Sends RRC CONN REQ and RNC Responds with RRC CONN REJ

Calls Are Dropped Due to Soft Handover Failure

Only Hard Handover Succeeds during High-Speed Services Multiple 384 kbps Data Services Fail to Be Activated

3.2 UE Sends RRC CONN REQ and RNC Responds with RRCCONN REJ

I. Fault Symptoms On the Uu interface, the UE sends a RRC CONN REQ message, but RNC responds

with a RRC CONN REJ message. In addition, on the Iub interface, the RNC sends a RL

SETUP REQ message and the NodeB responds with a RL SETUP RSP message.However, the RNC does not send an AAL2 ESTABLISH REQUEST message.

II. Troubleshooting This fault is caused by the inconsistent setting of CCP parameters between the RNC

and the NodeB.


1) Use LST CP to query the CCP port configuration of the NodeB on the NodeB O&M

system.

2) Use LST SAALINK to query the CCP parameter configuration of the RNC on theRNC O&M system.

3) Check that the setting of CCP parameters (including CCP port No., VPI, VCI, UNI

port No., IMA group No.) in the NodeB is consistent with that in the RNC.

4) If they are inconsistent, use RMV CP to remove the CCP.

5) Use ADD CP to a new CCP and make the new CCP consistent with that in the

RNC on the NodeB O&M system.

III. Verification Power off the UE and then power it on again to verify whether the fault has been

cleared. Observe the Uu interface messages from the RNC. If the RNC responds with a





3-2

RRC CONN SETUP message instead of RRC CONN REJ message, it indicates RRC

connection has been set up successfully and the fault has been cleared.

3.3 Calls Are Dropped Due to Soft Handover FailureI. Fault Symptoms

Calls are dropped in the course of soft handover. Soft handover fails.

II. Troubleshooting

Start single user tracing on the RNC O&M system and you may find the following two

cases:

Case 1: There are new links added for this user in the course of soft handover, but

there is no RL LINK RESTORE message on the Iub interface. Clear the fault as follows:

1) Query cell configuration parameter on the NodeB O&M system by using LST

LOCELLCFG.

2) Check whether cell inner handover radius is close or equal to cell radius.

3) Modify the cell inner handover radius to 2*78 m by using MOD LOCELL if it is too

large.

Case 2: There are no links newly added for this user in the course of soft handover.


1) Query the configuration parameters of the neighboring cell on the RNC O&M

system by using LST INTRAFREQCELL.2) Configure a neighboring cell correctly by using MOD INTRAFREQCELL if there

are no neighboring cells.

3) If cell neighboring relationship in the RNC is correct, compare the configuration

parameters of both cells on the RNC O&M system by using LST CELL.

4) Check whether the downlink primary scrambling codes of both cells are the same.

5) If yes, modify either of them by using MOD CELLSETUP to make them different.

III. Verification

After the procedure above, no calls are dropped and soft handover is successful.

3.4 Only Hard Handover Succeeds during High-SpeedServices

I. Fault Symptoms

Only hard handover, instead of soft handover, succeeds during 384 kbps services.

II. Troubleshooting

This fault occurs because the decision threshold of RNC handover rate is too low.






3-3

1) Check that the “BEBitRateThd” is D384 on the RNC O&M system by using LST

HOCOMM.

2) Modify “BEBitRateThd” to D384 on the RNC O&M system by using SET

HOCOMM.

III. Verification

After value modification of “BEBitRateThd”, 384 kbps service is available after soft

handover. Soft handover of 384 kbps service is successful.

3.5 Multiple 384 kbps Data Services Fail to Be Activated

I. Fault Symptoms

Not multiple high-speed (384 kbps) services but low-speed (64 kbps) services can be

activated successfully.

II. Troubleshooting

This fault occurs especially when there are not enough transport bandwidth resources.


1) Start standard interface tracing on the NodeB O&M system, as shown in Figure

3-1.

Figure 3-1 Iub interface messages in fault condition

Observe the Iub interface messages and you will find that the NodeB responds with an

AAL2 RELEASE CONFIRM message, after RNC delivers an AAL2 ESTABLISH

REQUEST message, as shown in Figure 3-1. Note that under normal cases, the

NodeB should respond with an AAL2 ESTABLISH CONFIRM message, as shown in

Figure 3-2.





3-4

Figure 3-2 Iub interface messages in normal condition

2) Double click the AAL2 RELEASE CONFIRM to see the message contents, as

shown in Figure 3-3. The cause of the fault is displayed as lack of transport

bandwidth resource on the user plane.

Figure 3-3 AAL2 RELEASE CONFIRM message content

3) Re-configure transport resources based on actual situation. For example, add an

AAL2 PATH link after negotiation with the RNC, because the 384 kbps service

occupies a bandwidth of about 500 kbps.

III. Verification

After the procedure above, multiple 384 kbps services can be activated successfully.



Maintenance Manual – TroubleshootingWCDMA NodeB Chapter 4 Locating and Handling O&M Faults

4-1

Chapter 4 Locating and Handling O&M Faults

4.1 About This Chapter

This chapter introduces O&M fault locating and handling as follows:

Downloading Software Lasts Too Long or Fails

Starting Built-in FTP Server Fails

Logging in to NodeB in Near End Fails after NodeB Is Restarted upon Completion

of Downloading Data Configuration File

Signals in a Cell Are Weak

Copying Files through Telnet Fails

Note:

This manual does not introduce such basic operations and maintenance as RF channel calibration, clock

source setting and NodeB version upgrading.

4.2 Downloading Software Lasts Too Long or Fails

I. Fault Symptoms

During software upgrading, it takes several hours to download the software package, or

the software package fails to be downloaded.

II. Troubleshooting

Generally, this fault occurs because of poor network quality. Clear the fault as follows:

1) Click [Start/Run].

2) Enter “ping XX.XX.XX.XX” where “XX.XX.XX.XX” refers to the IP address of the

NMPT or NodeB IPoA and observe the returned result.

If it takes long for the system to return ping result, it indicates the network path is

too long or the IPoA bandwidth is too narrow.

If timeout occurs continually, it indicates the network is in poor connection and

some packets may have been lost.

3) In near end maintenance mode, connect the LMT with the NMPT directly with a

crossover cable to clear the interference of poor network quality.

4) For maintenance over IPoA through RNC, check on the RNC O&M system

whether the IPoA bandwidth is too narrow by using LST IPOAPVC and LST

ATMTRF. Generally, the transport rate depends on the transmit end. For IPoA of




4-2

64 kbps configuration, the downloading procedure may last two hours. Increase

the IPoA bandwidth to speed up software downloading progress based on the

actual situation.

III. Verification

After the above procedure, you can speed up and succeed in downloading the

software.

4.3 Starting Built-in FTP Server Fails

I. Fault Symptoms

During the start of the NodeB O&M system, a dialog box is displayed, prompting failure

to start the built-in FTP Server.

II. Troubleshooting

The cause of this fault is that an FTP Server has already been running in this computer.


1) Click [Start/Run].

2) Enter “ftp://XX.XX.XX.XX” where “ftp://XX.XX.XX.XX” refers to the IP address of

the local computer.

If the computer has started the FTP Server, a message will be displayed,

prompting the user to enter user name and password, or the FTP Service interface

will be displayed directly.

If the local computer has no FTP Server, an error message will be displayed, as

shown in Figure 4-1.

Figure 4-1 FTP Server error message

3) Check whether there are other commercial FTP Servers started by observing the

task bar on the local computer.

4) Stop them if any.

5) If the operating system on the local computer is windows 2000, check whether it

has started the FTP Server by clicking [Start/Settings/Control Panel].




4-3

6) Select [Management Tool/Service] to check whether the system has started the

FTP Server.

7) Stop the FTP Server if yes.

III. Verification

Stop other FTP services and restart the LMT, the built-in FTP Server can be started

normally.

4.4 Logging in to NodeB in Near End Fails after NodeB IsRestarted upon Completion of Downloading DataConfiguration File

I. Fault Symptoms

In near end maintenance mode, you can log in to the NodeB normally through the LMT

before downloading data configuration file. However, after the NodeB is restarted upon

the completion of downloading data configuration file, you cannot log in to the NodeB

through the LMT.

In this case, board indicators are normal.

However, you can still log in to the NodeB over IPoA

II. Troubleshooting

The fault may be caused by incorrect setting of IP address of near end maintenance

channel.

During the configuration of data configuration file, if you have forgotten the IP address

setting of the near end maintenance channel, the default IP address 17.21.2.15 will be

taken in the data configuration file.


Method 1

Log in to the NodeB over IPoA link through the O&M system.

Configure the IP address for the near end maintenance channel by using SET IP.

Use LST IP to check whether the IP address is successfully configured.

Method 2

Log in to NodeB over IPoA link through the LMT.

Open the data configuration file on the configuration management system to

modify attributes of the NodeB.

Modify the local IP address as the value demanded.

Download the data configuration file again.

Restart the NodeB.




4-4

III. Verification

After the procedure above, you can log in to the NodeB in the near end normally.

4.5 Signals in a Cell Are Weak

I. Fault Symptoms


Signals in a cell are weak. Even in the direction of main lobe and at the foot of the

NodeB, the test device still cannot detect signals.

Start the 141 test to perform downlink channel correction and the Reflected Power

of NLPA Too Large alarm is reported.

II. Troubleshooting


1) Check the NLPA from the following aspects:

The output connector of NLPA is fastened.

The cable connection between NLPA and NDDL is normal.

The NLPA output ports and the antennas are connected.

2) Check the NDDL from the following aspects:

The cable between NDDL ANT output port and cabinet top is connected.

The connector is fastened.

The corresponding port on the cabinet top port connects to the antenna and feedersystem.

The NDDL is put in position.

The fixing screws on the NDDL are fastened.

3) Remove the NDDL.

4) Check whether the blind mating connectors, as shown in Figure 4-2, at the back of

the NDDL are damaged or improperly connected. Pay special attention to TXA

and TXB connectors.

5) Repair or replace the connectors if they are damaged, or even replace the NDDL if

necessary. Re-connect the connectors if they are not properly connected.




4-5

Figure 4-2 NDDL blind mating connector

6) Replace NLPA and NDDL one by one.

III. Verification

After the procedure above, the fault is cleared if the test device can detect signals of

normal intensity.

4.6 Copying Files through Telnet Fails

I. Fault Symptoms

Either at the near end or at the far end, you fail in copying files from the computer to the

NodeB or from the NodeB to the computer through Telnet.

II. Troubleshooting

If you can log in to NodeB through Telnet, it indicates that the network is working

normally. Failure in copying files is mostly likely caused by improper operations or

incorrect settings.


1) Respectively set the user name, password, and default path to “aa”, “123”, and

“C:\” for the FTP Server.

2) Run version on the Telnet, and you will get the following printout information:

-> version

VxWorks (for Motorola MPC8260 ADS) version 5.4.

Kernel: WIND version 2.5.



Maintenance Manual – TroubleshootingWCDMA NodeB Appendix A Flow Chart

A-1

Appendix A Flow Chart

A.1 Overview

This chapter presents several major flow charts, including cell setup, location updating,

call initiation, call termination and PDP activation/deactivation. Any failure occurring to

any step between UE and UTRAN may cause trouble in the corresponding procedure.




A-2

A.2 Cell Setup

N C P : C e l l S e t u p R e q u e s t

N o d e B C R N C

N C P : C e l l S e t u p R e s p o n s e

R e s o u r c e-

c h e c k

N C P : A u d i t R e s p o n s e

N C P : A u d i t R e q u e s t

N C P : C o m m o n t r a n s p o r tc h a n n e l S e t u p R e q u e s t

N C P : C o m m o n t r a n s p o r tc h a n n e l S e t u p R e s p o n s e

A L C A P : Q A A L 2 E s t a b l i s h R e q u e s t

A L C A P : Q A A L 2 E s t a b l i s h C o n f i r m

N C P : C o m m o n t r a n s p o r tc h a n n e l S e t u p R e s p o n s e



N C P : C o m m o n t r a n s p o r tc h a n n e l S e t u p R e q u e s t


E s t a b l i s h C o n f i r m A L C A P : Q A A L 2



F A C H F P : D L S y n c h r o n i z a t i o nc o n t r o l f r a m e

F A C H F P : U L S y n c h r o n i z a t i o n

c o n t r o l f r a m e

F A C H F P : D L S y n c h r o n i z a t i o nc o n t r o l f r a m e

F A C H F P : U L S y n c h r o n i z a t i o n

c o n t r o l f r a m e P C H F P : D L S y n c h r o n i z a t i o n

o n t r o l f r a m e

P C H F P : U L S y n c h r o n i z a t i o nc o n t r o l f r a m e

P C H F P : D L N o d eS y n c h r o n i z a t i o n c o n t r o l f r a m e

P C H F P : U L N o d e

S y n c h r o n i z a t i o n c o n t r o l f r a m e

N C P : R e s o u r c e s t a t e in d i c a t io n

Figure A-1 Cell setup

As shown in Figure A-1, RNC initiates an Audit Request, and NodeB acknowledges it

with an Audit Response. RNC sends a Cell Setup Request upon receipt of the Audit

Response. After the cell setup procedure finishes, the procedure to setup common

channels, common measurement and system message updating starts. The success




A-3

of system message updating indicates completion of cell setup. In this case, UE can

stay and make calls in this cell. Location for cell faults must refer to cell state, Iub

interface tracing messages, fault information of NodeB alarm management system.




A-5

As shown in Figure A-2, the location updating procedure involves RACH random

access, radio link setup, transport channel synchronization, radio link deletion and

DCCH/CCCH data transport.




A-8

As shown in Figure A-3 and Figure A-4, call initiation is a procedure of RRC connection

setup and RAB assignment. RRC connection setup is a procedure to establish 3.4K

radio link and perform high-level signaling interworking on this link. RAB assignment is

a procedure to reconfigure the radio link for the corresponding service to meet therequirements for transport service.

Note:

RAB represents radio access bearing. It is a term of high-level protocol and corresponds to service type

and transport layer FP respectively. RAB may contain multiple RBs, which corresponds to DCHs of the

transport layer respectively.




A-9

A.5 Call Termination

Downlink Synchronisation

UE Node B

Serving RNS

Serving

RNC

DCH-FPDCH-FP

RRCRRC

CCCH : RRC Connection Request

NBAP Radio Link Setup Response

NBAP

NBAP Radio Link Setup Request

CCCH : RRC Connection Setup

Start RX

Start TX

RRC

RRC

DCCH : RRC Connection Setup Complete

DCH-FPDCH-FPUplink Synchronisation

NBAP

Q.AAL2Q.AAL2

Q.AAL2 Establish Request

Establish Confirm

Inital Direct Transfer

RRC

RANAPRANAP

CN

Initial UE Message

RANAPRANAP

DCCH

Direct Transfer

RANAPRANAP

Direct Transfer

:

Direct TransferDCCH::

Direct TransferDCCH ::

RRCDownlink

RRC

RRC

RRC

Uplink

RRC

RRC

RRC

RRC

(Paging Response)

(Setup)

RAB Assignment Request

RANAP

RANAPEstablishment( )

Q.AAL2

Q.AAL2Q.AAL2

Q.AAL2 Establish Request

Establish Confirm

Q.AAL2

NBAPPrepare

NBAPRadio Link Reconfiguration

NBAPRadio Link Reconfiguration NBAPReady

RANAPRANAPPaging

Paging

(Call Confirm)

RANAP

RLC RLCDCCH : RR C Connection Setup Complete ack

Figure A-5 Call termination (1)




A-11

As shown in Figure A-5 and Figure A-6, the call termination procedure is similar to call

initiation procedure except that there is a paging procedure ahead in the call initiation

procedure.

Paging procedure: Once UE registers in a network system, it will be arranged in apaging group. If an UE in a paging group is being paged, NodeB will send the

corresponding periodic Paging Indication (PI) over the PICH channel. Upon detection

of PI, UE wakes up from the dormant state and check whether there are any paging

messages in the next PCH frame. UE initiates random access if any, or backs to the

dormant state to go on monitoring PICH if otherwise.




A-13

UE

Node B

Serving RNSServing

RNCCN

RRC

DCCH : Radio Bearer Setup

DCCH : Radio Bearer Setup Complete

Apply new transport format set

RRC

RRC

RRC

RRC

RAB Assignment ResponseRANAP RANAP

RANAPRANAP

Direct Transfer

( Act. PDP Accept )

RRC

RRC

RANAP

Direct Transfer

RANAP Direct TransferRANAP

RANAP

RANAPRANAP

RANAPRANAP

RANAPRANAP

Iu Release Command

Iu Release CompleteQ.AAL2Q.AAL2

Q.AAL2Q.AAL2 Release Request

Release Complete

Q.AAL2Q.AAL2

Q.AAL2Q.AAL2 Release Request

Release Complete

DCCH :: Downlink Direct Transferr (0a42)RRC

DCCH :: Downlink

RRCRRC

RRC

RRC

RRC

RRC

RRC RRC

RRC

RRC

Direct Transferr(8a47)

DCCH : RRC Connection

DCCH : RRC Connection

Release

Release Complete

NBAP Radio Link Deletion

NBAP Radio LinkDeletion

NBAP

NBAPComplete

DCCH : Radio Bearer Setup Complete ack RLCRLC

激活成功DCCH:Uplink Direct Transfer(0a46)

(Dea. PDP Request)RANAP

RAB Assignment Request

(Dea. PDP Accept)

Prepare NBAP NBAP

Radio Link Reconfiguration

NBAPRadio Link Reconfiguration

Ready

Q.AAL2Q.AAL2

Q.AAL2Q.AAL2

Radio Link Reconfiguration

Commit

RANAP

NBAP

NBAP NBAP

Radio Bearer Release Request

Radio Bearer Release Complete

RAB Assignment Response

去激活完成

Release Request

Release Co mplete

PDP activation successful

Completion of

deactivation

Figure A-8 PDP activation and deactivation (2)




A-14

As shown in Figure A-7 and Figure A-8, PDP activation procedure is similar to call

initiation procedure except that the bearing service is different. The connection setup in

the call initiation procedure bears AMR voice and that in PDP setup bears data service.

PDP deactivation procedure is similar to the UE initiated call termination procedure.



Maintenance Manual – Troubleshooting WCDMA NodeB Index

Index

Numerics

120-Ω E1 cable is abnormal, 2-3

384 kbps data services fail, 3-3

C

call initiation, A-6

call termination, A-9

calls are dropped, 3-2 cell cannot be set up, 2-5

cell set up fail, 2-8

cell setup, A-2

cells faults, 2-1

cells fundamental knowledge, 2-1

collecting fault information, 1-3

contacting huawei technical support, 1-6

copying files through telnet fails, 4-5

D

downloading software fails, 4-1

downloading software lasts too long, 4-1

F

fault, clearing, 1-4

fault, collecting information, 1-3

fault, locating, 1-4

flow char, A-1

G

general methods, 1-1

I

instruments and meters, 1-2

L

logging in to NodeB fails, 4-3

logical cell cannot be set up, 2-1

M

maintenance personnel qualification

ability, 1-2

knowledge, 1-1

technical expertise, 1-1

methods for locating faults

analyzing alarm information, 1-5

analyzing faults through comparison, 1-6

analyzing faults with meters, 1-5

analyzing faults with performance, 1-6

analyzing indicator states, 1-5

analyzing interface signaling, 1-5

analyzing original information, 1-4

O

O&M faults, 4-1

only hard handover succeeds, 3-2

only one cell can be set up, 2-6

P

PDP activation & deactivation, A-12

R

RNC deletes cell, 2-6

RRC connect is rejected, 3-1

S

service faults, 3-1

signals in a cell are weak, 4-4

starting built-in FTP server fails, 4-2

T

nodeb maintenance manual-troubleshooting.pdf

Documents