Maintenance Manual Troubleshooting

Chapter 1 Overview 1-1.........................................................................................

1.1 General Troubleshooting Procedure 1-1......................................................1.2 Fault Analysis and Location Methods 1-3.....................................................1.3 Technical Support 1-5..................................................................................

Chapter 2 Speech Call Fault 2-1...........................................................................

2.1 MS Access Failure 2-1.................................................................................2.1.1 MS Failed to Find Network upon Power-up 2-1...................................2.1.2 Slow Network Access 2-4....................................................................2.1.3 Some MSs Failed to Access Network 2-6............................................2.1.4 IS-95 MS Accessed CDMA 1X Network Illegally 2-8...........................

2.2 MOC Failure 2-10...........................................................................................2.2.1 Assignment Failure (no radio resource available) 2-10..........................2.2.2 Assignment Failure (requested terrestrial resource unavailable) 2-15...2.2.3 Clear Command (protocol error between BSC and MSC) 2-17.............2.2.4 Clear Command (authentication failure) 2-19........................................2.2.5 N_DISCONNECT_IND Received 2-23..................................................

2.3 MTC Failure 2-27............................................................................................2.3.1 BSC Not Received Paging Request 2-27..............................................2.3.2 BSC Not Received Paging Response 2-30............................................2.3.3 Assignment Failure (no radio resource available) 2-44..........................

2.4 Speech Quality Problems 2-46.......................................................................2.4.1 Echo 2-46...............................................................................................2.4.2 Voice Loopback 2-51.............................................................................2.4.3 Single Pass 2-54....................................................................................2.4.4 Cross-talk 2-57.......................................................................................2.4.5 Noise 2-59..............................................................................................

Chapter 3 Encrypted Speech Call Fault 3-1.........................................................

3.1 Encrypted Speech Call Failure 3-1...............................................................

Chapter 4 Voice Service Negotiation Fault 4-1...................................................

4.1 Voice Service Negotiation Failure 4-1..........................................................

Chapter 5 E911 Emergency Call Fault 5-1...........................................................

5.1 E911 Emergency Call Failure 5-1.................................................................

Chapter 6 Registration Fault 6-1...........................................................................

6.1 MS Failed to Initiate Registration 6-1...........................................................6.2 MS Registration Failed 6-6...........................................................................6.3 Mass Registration Messages Received 6-8.................................................

Chapter 7 Authentication Fault 7-1......................................................................

7.1 MS Global Challenge Failed 7-1...................................................................7.2 MS Unique Challenge Failed 7-5..................................................................7.3 MS SSD Update Failed 7-8..........................................................................7.4 Authentication Not Initiated 7-9....................................................................

Chapter 8 Short Message Fault 8-1......................................................................

8.1 MS Failed to Receive Short Message 8-1....................................................8.2 Centralized Sending of Short Messages Resulted in SystemAbnormality 8-2..................................................................................................

Chapter 9 Service Redirection Fault 9-1..............................................................

9.1 Service Redirection Failed 9-1.....................................................................

Chapter 10 Handoff Fault 10-1................................................................................

10.1 MS Failed to Trigger Hard Handoff 10-1......................................................10.2 Handoff Required Reject (requested terrestrial resourceunavailable) 10-5..................................................................................................10.3 Failed to Trigger Inter-band Class Hard Handoff 10-7.................................

Chapter 11 Packet Data Service Fault 11-1...........................................................

11.1 Occasional Data Call Failure 11-1................................................................11.2 Data Call Failure 11-5...................................................................................

11.2.1 No Messages on A Interface 11-5........................................................11.2.2 Only Reverse Message on A9 Interface 11-7......................................11.2.3 Only Reverse Message on A11 Interface 11-12....................................11.2.4 Call Disconnected Several Seconds after the Connection 11-16..........

11.3 Data Service Handoff Failure 11-18...............................................................

Chapter 12 Quasi-Concurrent Service Fault 12-1.................................................

12.1 Failed to Trigger Quasi-Concurrent Service 12-1.........................................12.1.1 Not Receiving Clear Command Message 12-1....................................12.1.2 Not Sending Service Option Control Message 12-2............................12.1.3 Data Service Call Suspended and Call Establishment Failed 12-5.....

Chapter 13 Circuit Data Service Fault 13-1............................................................

13.1 Asynchronous Data Service Call Failure 13-1..............................................13.1.1 MS cannot Access Hyper Terminal 13-1..............................................13.1.2 Mobile-Originated/Mobile-Terminated Asynchronous DataCall Failure 13-3..............................................................................................

13.2 Facsimile Call Failure 13-6...........................................................................13.2.1 PC (G3) Facsimile Call Failure 13-6....................................................13.2.2 Analog Facsimile Call Failure 13-8......................................................

Chapter 14 CDR Fault 14-1......................................................................................

14.1 No CDR information 14-1.............................................................................

Chapter 15 RFMT Fault 15-1....................................................................................

15.1 Starting RFMT Trace Task Failed 15-1........................................................

Chapter 16 Switching Module Fault 16-1...............................................................

16.1 Event Alarm for Active/Standby Port Switchover 16-1.................................16.2 Optical Interface Out of Frame Alarm 16-4...................................................16.3 Optical Interface Loss of Frame Alarm 16-7.................................................16.4 Optical Interface Loss of Signal Alarm 16-7.................................................16.5 Event Alarm of CLPC Loss of System Clock 16-8........................................16.6 Clock Switchover Event Alarm 16-11.............................................................

Chapter 17 Link and Circuit Fault 17-1..................................................................

17.1 Abis Interface Link Fault 17-1.......................................................................17.1.1 E1/T1 Signal Loss 17-1........................................................................17.1.2 E1/T1 Frame Out-of-sync 17-5............................................................17.1.3 E1/T1 Remote Alarm 17-7...................................................................17.1.4 E1/T1 Alarm Indication Signal 17-8......................................................17.1.5 E1/T1 CRC4 Multiframe Out-of-sync 17-9...........................................17.1.6 E1/T1 Link Loopback 17-11...................................................................17.1.7 E1/T1 1-hour Slip Frame Threshold Crossed 17-12..............................17.1.8 E1/T1 Link BER Threshold Crossed 17-14............................................17.1.9 IMA Link Out of Frame 17-15.................................................................17.1.10 Inter-link IMA Out of Synchronization 17-17........................................17.1.11 IMA Link Remote Receiving Defect 17-19...........................................17.1.12 Receiving End of IMA Link Failed 17-20..............................................17.1.13 IMA/UNI Link Cell Delimitation Loss 17-20..........................................17.1.14 Insufficient Active Links in IMA Group 17-22.......................................

17.2 A1 Interface Signaling Link Fault 17-23..........................................................17.2.1 E1/T1 Alarm 17-23.................................................................................17.2.2 MTP Link Failure 17-23..........................................................................

17.3 A2 Interface Circuit Fault 17-31......................................................................

Chapter 18 BTS Management Fault 18-1...............................................................

18.1 BAM Failed to Ping or Log on to BTS through Telnet 18-1..........................18.2 BTS (Carrier) Unavailable 18-8....................................................................

Chapter 19 Clock Fault 19-1....................................................................................

19.1 Inadequate Satellites Traced by GCKP 19-1................................................19.2 Locking Satellite Signals Failed 19-3............................................................

19.3 Abnormal MS Time Display 19-5..................................................................

Chapter 20 Operation and Maintenance System Fault 20-1.................................

20.1 Failed to Ping External Network IP of CMPU from BAM 20-1......................20.2 BAM Fault 20-8.............................................................................................

20.2.1 BAM Installation Failed 20-8................................................................20.2.2 BAM Uninstall Failed 20-10....................................................................20.2.3 Exchange and Load Processes Abnormal 20-13...................................20.2.4 Starting TFTP Failed and Load Service Abnormal 20-14......................

20.3 WS Fault 20-15...............................................................................................20.3.1 Intermittent Interruption between WS and BAM 20-15...........................20.3.2 WS Login Failure 20-16.........................................................................

20.4 Loading Problem 20-18..................................................................................20.4.1 BAM Received No BOOTP Request for Board Loading 20-18..............20.4.2 BAM Failed to Send BOOT REPLAY to BSC Boards 20-22..................20.4.3 CFMR DSP Loading Failed 20-26..........................................................

Appendix A Template for Troubleshooting Cases A-1.......................................

Appendix B Abbreviations and Acronyms B-1....................................................

HUAWEI

Airbridge cBSC6600 CDMA Base Station Controller Maintenance Manual - Troubleshooting

V100R003

Airbridge cBSC6600 CDMA Base Station Controller

Maintenance Manual

Volume Troubleshooting

Manual Version T2-030355-20040420-C-1.30

Product Version V100R003

BOM 31033355

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.

About This Manual

Release Notes

This manual applies to Airbridge cBSC6600 CDMA Base Station Controller V100R003.

Related Manuals

The related manuals are listed in the following table.

Manual Content

Airbridge cBSC6600 CDMA Base Station Controller Documentation Guide

Describes documentation package of the cBSC6600, including the organization, content and methods of using it.

Airbridge cBSC6600 CDMA Base Station Controller Compliance and Safety Manual

Describes regulatory compliance statement and regulatory compliance information of the cBSC6600, and safety information needed to install and maintain the equipment.

Airbridge cBSC6600 CDMA Base Station Controller Technical Manual-System Description

Introduces the development of the CDMA network, and the product features, system configuration, system functions, related operation and maintenance, and technical specifications of the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Technical Manual-System Architecture

Describes the general architecture of the cBSC6600, the subracks, clock system, O&M system, and power supply system, and signal flows.

Airbridge cBSC6600 CDMA Base Station Controller Technical Manual-Interfaces and Protocols

Details the external interfaces, related protocols and standards, and typical service flows for the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Technical Manual-System Function

Introduces the supporting bands, networking capacity, radio channel management, power control, handoff decision, performance management, alarm management, dynamic configuration, and reliability design of the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Hardware Description Manual

Details the structures and working principles of the cables, boards, subracks, and cabinets of the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Installation Manual-Hardware Installation

Covers the hardware installation of the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Installation Manual-Software Installation

Describes the software installation of the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Installation Manual-System Commissioning

Describes procedures of commissioning the cBSC6600 after the hardware and software installation to ensure normal operation.

Airbridge cBSC6600 CDMA Base Station Controller Operation Manual-Data Configuration

Covers the data configuration of the cBSC6600 for large-capacity and small-capacity offices.

Airbridge cBSC6600 CDMA Base Station Controller Maintenance Manual-Routine Maintenance

Describes contents and methods of routine maintenance over the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Maintenance Manual-Troubleshooting

Details the troubleshooting for the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Maintenance Manual-Parts Replacement

Presents procedures and methods of replacing boards and components of the cBSC6600.

Organization

This manual gives the guidelines on fault location and troubleshooting for Airbridge cBSC6600 CDMA Base Station Controller. It consists of 15 chapters and one appendix.

Chapter 1 Overview: Introduces the general troubleshooting procedure, methods commonly used in fault analysis and location, and the technical support system of Huawei.

Chapter 2 Speech Call Fault: Contains troubleshooting suggestions on various speech call faults.

Chapter 3 Encrypted Speech Call Fault: Contains troubleshooting suggestions on various encrypted speech call faults.

Chapter 4 Voice Service Negotiation Fault: Contains troubleshooting suggestions on various faults of Voice Service Negotiation.

Chapter 5 E911 Emergency Call Fault: Contains troubleshooting suggestions on various faults of E911 emergency call.

Chapter 6 Registration Fault: Contains troubleshooting suggestions on various faults occurred in registration.

Chapter 7 Authentication Fault: Contains troubleshooting suggestions on various faults occurred in authentication.

Chapter 8 Short Message Fault: Contains troubleshooting suggestions on various short message faults.

Chapter 9 Service Redirection Fault: Contains troubleshooting suggestions on various faults occurred in service redirection.

Chapter 10 Handoff Fault: Contains troubleshooting suggestions on various handoff faults.

Chapter 11 Packet Data Service Fault: Contains troubleshooting suggestions on various data service faults.

Chapter 12 Quasi-Concurrent Service Fault: Contains troubleshooting suggestions on various faults of quasi-concurrent service.

Chapter 13 Circuit Data Service Fault: Contains troubleshooting suggestions on various circuited data service faults.

Chapter 14 CDR Fault: Contains troubleshooting suggestions on various faults of CDR.

Chapter 15 RFMT Fault: Contains troubleshooting suggestions on various faults of RFMT.

Chapter 16 Switching Module Fault: Contains troubleshooting suggestions on various Switching Module faults.

Chapter 17 Link and Circuit Fault: Contains troubleshooting suggestions on various link and circuit faults.

Chapter 18 BTS Management Fault: Contains troubleshooting suggestions on various faults occurred in BTS management.

Chapter 19 Clock Fault: Contains troubleshooting suggestions on various clock faults.

Chapter 20 Operation and Maintenance System Fault: Contains troubleshooting suggestions on various faults of operation and maintenance system.

Appendix: Contains the template used for writing troubleshooting cases, as well as the abbreviations and acronyms used in the manual.

Intended Audience

The manual is intended for the following readers:

Installation engineers and technicians Operation and maintenance personnel Technical marketing specialists

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.

Boldface Headings are in Boldface.

Courier New Terminal Display is in Courier New.

II. Command conventions


Boldface The keywords of a command line are in Boldface.

italic Command arguments are in italic.

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

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

[ x | y | ... ] Optional alternative items are grouped in square brackets and separated by vertical bars. One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated by vertical bars. A minimum of one or a maximum of all can be selected.

[ x | y | ... ] * Optional alternative items are grouped in square brackets and separated by vertical bars. Many or none can be selected.

III. GUI conventions


< > Button names are inside angle brackets. For example, click the <OK> button.

[ ] Window names, menu items, data table and field names are inside square brackets. For example, pop up the [New User] window.

/ Multi-level menus are separated by forward slashes. For example, [File/Create/Folder].

IV. Keyboard operation

Format Description

<Key> Press the key with the key name inside angle brackets. For example, <Enter>, <Tab>, <Backspace>, or <A>.

<Key1+Key2> Press the keys concurrently. For example, <Ctrl+Alt+A> means the three keys should be pressed concurrently.

<Key1, Key2> Press the keys in turn. For example, <Alt, A> means the two keys should be pressed in turn.

V. Mouse operation

Action Description

Click Press the left button or right button quickly (left button by default).

Double Click Press the left button twice continuously and quickly.

Drag Press and hold the left button and drag it to a certain position.

VI. 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, Warning, Danger: Means reader be extremely careful during the

operation.

Note, Comment, Tip, Knowhow, Thought: Means a complementary description.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Table of Contents

i

Table of Contents

Chapter 1 Overview....................................................................................................................... 1-1 1.1 General Troubleshooting Procedure.................................................................................. 1-1 1.2 Fault Analysis and Location Methods................................................................................ 1-3 1.3 Technical Support .............................................................................................................. 1-5

Chapter 2 Speech Call Fault......................................................................................................... 2-1 2.1 MS Access Failure............................................................................................................. 2-1

2.1.1 MS Failed to Find Network upon Power-up ............................................................ 2-1 2.1.2 Slow Network Access.............................................................................................. 2-4 2.1.3 Some MSs Failed to Access Network..................................................................... 2-6 2.1.4 IS-95 MS Accessed CDMA 1X Network Illegally .................................................... 2-8

2.2 MOC Failure..................................................................................................................... 2-10 2.2.1 Assignment Failure (no radio resource available)................................................. 2-10 2.2.2 Assignment Failure (requested terrestrial resource unavailable) ......................... 2-15 2.2.3 Clear Command (protocol error between BSC and MSC).................................... 2-17 2.2.4 Clear Command (authentication failure) ............................................................... 2-19 2.2.5 N_DISCONNECT_IND Received.......................................................................... 2-23

2.3 MTC Failure ..................................................................................................................... 2-27 2.3.1 BSC Not Received Paging Request ..................................................................... 2-27 2.3.2 BSC Not Received Paging Response................................................................... 2-30 2.3.3 Assignment Failure (no radio resource available)................................................. 2-44

2.4 Speech Quality Problems ................................................................................................ 2-46 2.4.1 Echo ...................................................................................................................... 2-46 2.4.2 Voice Loopback..................................................................................................... 2-51 2.4.3 Single Pass ........................................................................................................... 2-54 2.4.4 Cross-talk .............................................................................................................. 2-57 2.4.5 Noise ..................................................................................................................... 2-59

Chapter 3 Encrypted Speech Call Fault ...................................................................................... 3-1 3.1 Encrypted Speech Call Failure .......................................................................................... 3-1

Chapter 4 Voice Service Negotiation Fault................................................................................. 4-1 4.1 Voice Service Negotiation Failure...................................................................................... 4-1

Chapter 5 E911 Emergency Call Fault......................................................................................... 5-1 5.1 E911 Emergency Call Failure ............................................................................................ 5-1

Chapter 6 Registration Fault ........................................................................................................ 6-1 6.1 MS Failed to Initiate Registration....................................................................................... 6-1 6.2 MS Registration Failed ...................................................................................................... 6-6 6.3 Mass Registration Messages Received ............................................................................ 6-8


ii

Chapter 7 Authentication Fault .................................................................................................... 7-1 7.1 MS Global Challenge Failed .............................................................................................. 7-1 7.2 MS Unique Challenge Failed ............................................................................................. 7-5 7.3 MS SSD Update Failed...................................................................................................... 7-8 7.4 Authentication Not Initiated................................................................................................ 7-9

Chapter 8 Short Message Fault.................................................................................................... 8-1 8.1 MS Failed to Receive Short Message ............................................................................... 8-1 8.2 Centralized Sending of Short Messages Resulted in System Abnormality ....................... 8-2

Chapter 9 Service Redirection Fault............................................................................................ 9-1 9.1 Service Redirection Failed................................................................................................. 9-1

Chapter 10 Handoff Fault............................................................................................................ 10-1 10.1 MS Failed to Trigger Hard Handoff................................................................................ 10-1 10.2 Handoff Required Reject (requested terrestrial resource unavailable) ......................... 10-5 10.3 Failed to Trigger Inter-band Class Hard Handoff........................................................... 10-7

Chapter 11 Packet Data Service Fault ....................................................................................... 11-1 11.1 Occasional Data Call Failure ......................................................................................... 11-1 11.2 Data Call Failure ............................................................................................................ 11-5

11.2.1 No Messages on A Interface............................................................................... 11-5 11.2.2 Only Reverse Message on A9 Interface ............................................................. 11-7 11.2.3 Only Reverse Message on A11 Interface ......................................................... 11-12 11.2.4 Call Disconnected Several Seconds after the Connection ............................... 11-16

11.3 Data Service Handoff Failure....................................................................................... 11-18

Chapter 12 Quasi-Concurrent Service Fault............................................................................. 12-1 12.1 Failed to Trigger Quasi-Concurrent Service .................................................................. 12-1

12.1.1 Not Receiving Clear Command Message........................................................... 12-1 12.1.2 Not Sending Service Option Control Message ................................................... 12-2 12.1.3 Data Service Call Suspended and Call Establishment Failed ............................ 12-5

Chapter 13 Circuit Data Service Fault ....................................................................................... 13-1 13.1 Asynchronous Data Service Call Failure ....................................................................... 13-1

13.1.1 MS cannot Access Hyper Terminal..................................................................... 13-1 13.1.2 Mobile-Originated/Mobile-Terminated Asynchronous Data Call Failure............. 13-3

13.2 Facsimile Call Failure .................................................................................................... 13-6 13.2.1 PC (G3) Facsimile Call Failure............................................................................ 13-6 13.2.2 Analog Facsimile Call Failure.............................................................................. 13-8

Chapter 14 CDR Fault.................................................................................................................. 14-1 14.1 No CDR information....................................................................................................... 14-1

Chapter 15 RFMT Fault ............................................................................................................... 15-1 15.1 Starting RFMT Trace Task Failed.................................................................................. 15-1


iii

Chapter 16 Switching Module Fault........................................................................................... 16-1 16.1 Event Alarm for Active/Standby Port Switchover........................................................... 16-1 16.2 Optical Interface Out of Frame Alarm............................................................................ 16-4 16.3 Optical Interface Loss of Frame Alarm .......................................................................... 16-7 16.4 Optical Interface Loss of Signal Alarm .......................................................................... 16-7 16.5 Event Alarm of CLPC Loss of System Clock................................................................. 16-8 16.6 Clock Switchover Event Alarm..................................................................................... 16-11

Chapter 17 Link and Circuit Fault .............................................................................................. 17-1 17.1 Abis Interface Link Fault ................................................................................................ 17-1

17.1.1 E1/T1 Signal Loss ............................................................................................... 17-1 17.1.2 E1/T1 Frame Out-of-sync.................................................................................... 17-5 17.1.3 E1/T1 Remote Alarm........................................................................................... 17-7 17.1.4 E1/T1 Alarm Indication Signal............................................................................. 17-8 17.1.5 E1/T1 CRC4 Multiframe Out-of-sync .................................................................. 17-9 17.1.6 E1/T1 Link Loopback ........................................................................................ 17-11 17.1.7 E1/T1 1-hour Slip Frame Threshold Crossed ................................................... 17-12 17.1.8 E1/T1 Link BER Threshold Crossed ................................................................. 17-14 17.1.9 IMA Link Out of Frame ...................................................................................... 17-15 17.1.10 Inter-link IMA Out of Synchronization ............................................................. 17-17 17.1.11 IMA Link Remote Receiving Defect ................................................................ 17-19 17.1.12 Receiving End of IMA Link Failed ................................................................... 17-20 17.1.13 IMA/UNI Link Cell Delimitation Loss ............................................................... 17-20 17.1.14 Insufficient Active Links in IMA Group ............................................................ 17-22

17.2 A1 Interface Signaling Link Fault ................................................................................. 17-23 17.2.1 E1/T1 Alarm ...................................................................................................... 17-23 17.2.2 MTP Link Failure ............................................................................................... 17-23

17.3 A2 Interface Circuit Fault ............................................................................................. 17-31

Chapter 18 BTS Management Fault ........................................................................................... 18-1 18.1 BAM Failed to Ping or Log on to BTS through Telnet ................................................... 18-1 18.2 BTS (Carrier) Unavailable.............................................................................................. 18-8

Chapter 19 Clock Fault ............................................................................................................... 19-1 19.1 Inadequate Satellites Traced by GCKP......................................................................... 19-1 19.2 Locking Satellite Signals Failed..................................................................................... 19-3 19.3 Abnormal MS Time Display ........................................................................................... 19-5

Chapter 20 Operation and Maintenance System Fault ............................................................ 20-1 20.1 Failed to Ping External Network IP of CMPU from BAM ............................................... 20-1 20.2 BAM Fault ...................................................................................................................... 20-8

20.2.1 BAM Installation Failed ....................................................................................... 20-8 20.2.2 BAM Uninstall Failed......................................................................................... 20-10 20.2.3 Exchange and Load Processes Abnormal........................................................ 20-13 20.2.4 Starting TFTP Failed and Load Service Abnormal ........................................... 20-14


iv

20.3 WS Fault ...................................................................................................................... 20-15 20.3.1 Intermittent Interruption between WS and BAM................................................ 20-15 20.3.2 WS Login Failure............................................................................................... 20-16

20.4 Loading Problem.......................................................................................................... 20-18 20.4.1 BAM Received No BOOTP Request for Board Loading................................... 20-18 20.4.2 BAM Failed to Send BOOT REPLAY to BSC Boards....................................... 20-22 20.4.3 CFMR DSP Loading Failed............................................................................... 20-26

Appendix A Template for Troubleshooting Cases.....................................................................A-1

Appendix B Abbreviations and Acronyms .................................................................................B-1

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 1 Overview

1-1

Chapter 1 Overview

1.1 General Troubleshooting Procedure

Figure 1-1 shows the general troubleshooting procedure.

Start

Collect information

Diagnose faults

Locate faults

Clear faults

End

Figure 1-1 Troubleshooting flowchart

I. Collect information — to acquire raw data as much as possible

Fault information is the basis for troubleshooting. You should collect the following data:

Fault symptoms Time, site, and frequency Scope and impact Equipment operational status before a fault occurs The operations performed over the equipment before the occurrence of the fault,

and the result of these operations Measures taken to handle the fault, and the results Alarms and correlated or concomitant alarms generated upon the occurrence of

the fault The status of board indicators upon the occurrence of the fault


1-2

II. Diagnose faults — to determine the scope and type of the fault

By symptoms, BSC faults are classified to two categories: service faults and functional faults.

service faults:

Speech Call Fault Encrypted Speech Call Fault Voice Service Negotiation Fault E911 Emergency Call Fault Registration Fault Authentication Fault Short Message Fault Service Redirection Fault Handoff Fault Packet Data Service Fault Quasi-Concurrent Service Fault Circuit Data Service Fault

functional faults:

CDR Fault RFMT Fault Switching Module Fault Link and Circuit Fault BTS Management Fault Clock Fault Operation and Maintenance System Fault

You can diagnose and locate the faults according to the symptoms. A fault, however, may fall into several categories. For example, a speech call fault may result from a clock fault. For the troubleshooting of this type of fault, see the clock fault section instead of the section about speech call faults.

III. Locate faults — to find the specific causes

A fault may result from several causes. You can find out the specific cause by analyzing all the possible causes and eliminating the irrelevant ones.

The types of service faults are limited, and the symptoms are relatively simple, but the failure causes can be complicated. A symptom may result from multiple causes. Therefore, the faults are hard to locate.

To locate a service fault,

1) Start interface and signaling trace, and locate the fault in the signaling flow (flow interruption point) by comparing it with the flow defined in the protocol.


1-3

2) Analyze the cell value of the messages in the signaling flow, and perform the preliminary diagnosis.

If the data configuration related to the protocol is wrong, directly modify the configuration.

If the fault occurs to the interface, locate the fault from the lower protocol layer to the upper protocol layer.

There are multiple types of system operational fault, but generally each type of fault corresponds to a definite cause, and the system can also provide alarms and error prompts accordingly. Therefore, you can clear faults according to the troubleshooting suggestions or the error prompts.

For common location methods, see section 1.2 Fault Analysis and Location Methods.

IV. Clear faults — to take proper measures to clear faults and resume the system

This is the last step in the troubleshooting. You can clear faults and resume the system with proper measures, such as checking connections, replacing boards, modifying configuration data, switching over systems, and resetting boards. For different faults, follow different operation specifications accordingly.

After the operations, you should test the system to ensure that the fault is cleared.

To avoid the reoccurrence of the same type of fault, you should review the whole procedure of the troubleshooting, record the key points in handling the fault, and note down the countermeasures against this type of fault and improvements.

1.2 Fault Analysis and Location Methods

I. Alarm information analysis

The BSC alarm system offers alarm information in the form of sound, light, or screen output.

You can locate the cause of a specific fault by analyzing the alarm information. As the BSC alarm management system can output complete alarm information, you can use the information to locate fault causes directly or together with other methods.

II. Indicator status analysis

The BSC boards are equipped with RUN and ALM indicators. Some of the boards also have functional or featured indicators. Besides the working statuses of corresponding boards, most of the indicators can also reflect such working statuses as links, optical channels, nodes, and active-standby systems. The statuses are one of the important bases of fault analysis and location.


1-4

By analyzing the indicator statuses, you can get a general idea about the fault location or cause, and determine whether the operational status of the related hardware and the physical connection of interface link are normal.

III. Interface and signaling trace

The analysis of the signaling messages traced helps locate the cause of the service faults.

IV. Service demonstration analysis

You can initiate certain services such as mobile originated call or data service to define the scope and type of a fault, and check whether the fault is cleared.

Service demonstration is used to locate service faults. You can locate the approximate scope and type of the fault according to the result of service demonstration. After taking corresponding measures, you can implement the service to check whether the fault is cleared.

V. Performance measurement analysis

You can create performance measurement tasks in the BSC performance management system to analyze the possible causes and scope of faults based on the performance measurement results.

Performance measurement results are one of the original information sources for locating system resource faults.

VI. Instrument and meter analysis

You can analyze and locate a fault based on the specific data measured by using the instruments and meters. The visual and quantized data directly reflects the essence of fault. Hence, this method is popular in power supply tests, signaling analyses, and BER detections.

Instrument and meter analysis is used locate interface physical link faults, system clock faults, and equipment hardware faults.

VII. Test and loopback

You can use instruments, meters, and software to test the relevant technical indices of transmission channels and trunk equipment that are possibly in faulty status. According to the test results, you can judge whether the equipment is faulty or likely to get faulty.

You can employ the hardware or software to perform loopback on transmission equipment or a transmission channel. After the loopback, you can find out whether the settings of relevant hardware and software parameters are normal according to the


1-5

conditions of transmission equipment/channels, service status, and signaling interoperation.

The loopback test is one of the most frequently-used methods to locate transmission problems and determine whether the settings of trunk parameters are correct.

VIII. Analysis through comparison and replacement

You can compare the symptoms or features of faulty parts with those of the normal parts to find out causes. This method applies to the faults occurred in a limited scope.

In the case that you cannot locate the fault after replacing the possibly-faulty parts with spare parts, you can exchange the possible-faulty parts (such as board or optical fiber) with the ones in normal operation, and observe the changes.

This method applies to the complicated hardware faults.

IX. Switchover and reset

You can switch services from the active board to the standby one, and compare the system operational status before and after the switchover. In this way you can check the operational conditions of the active board or the active-standby relations.

You can reset the system to restart it partially or entirely by manual to check whether the software operates abnormal, or the program stops responding.

Caution:

Switchover or reset may affect the system operation. Avoid using this method unless necessary.

1.3 Technical Support

If you fail to find enough information to locate or solve a fault, you can turn to the following sources for further assistance.

Technical Support Department in Huawei’s headquarters Technical Support Center of the local office Technical Support Website (http://support.huawei.com) Customer Service Center ([email protected])


1-6

Note:

The contact information of the local office in your area is available at the technical support website.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 2 Speech Call Fault

2-1

Chapter 2 Speech Call Fault

2.1 MS Access Failure

2.1.1 MS Failed to Find Network upon Power-up

I. Symptom explanation

After a mobile station (MS) is powered up in a certain area, it cannot find the network. As a result, the services are unavailable.

The [Debug] window on the MS or the drive test equipment connected with the MS shows that the MS attempts to search the network but fails.

II. Troubleshooting

See Figure 2-1 for the troubleshooting procedure.


2-2

Query the current status ofthe carrier (1)

Is the administrative status"Blocked" and the operational

status "Enabled"?

Is the operational status"Disabled", or does the

query fail?

Check and restorethe BSC-BTS link, or

reset the BTS

Conduct drive test (3)

Is the test place located ina blind spot?

Optimize network (4)

Unblock the carrier (2)

Conduct dialing test (5)

End

Y

N

Y

Y

Measure BTS output power

Is BTS output powerabnormal?

Restore the BTSoutput power

Y

Y

N

N

N

Query alarm information atthe alarm information

system

Is there a BTS standingwave alarm?

Handle the alarm

Y

N

Figure 2-1 Troubleshooting flowchart for MS access failure

Steps:

1) Query the current status of the carrier at the BSC side.

Execute the command DSP RES in the Service Maintenance System.

Example DSP RES: CN=20, SCTID=0, CRRID=0;

Result %%DSP RES: CN=20, SCTID=0, CRRID=0;%%

RETCODE = 0 Execution succeeded

Query Result

------------

Cell Sector Carrier AdministrativeStatus OperationalStatus

UsageStatus


2-3

20 0 0 Lock Enable Idle

( Record Number = 1 )

Total Reports: 1

--- END

2) Unblock the carrier.

a) In the Service Maintenance System, execute the command UBL RES to unblock a carrier. For example:

UBL RES: CN=20, SCTID=0, CRRID=0;

b) Check whether the carrier is unblocked.

Execute the command DSP RES to check the status of a carrier. Example DSP RES: CN=20, SCTID=0, CRRID=0;

Result %%DSP RES: CN=20, SCTID=0, CRRID=0;%%


Query Result

------------

Cell Sector Carrier AdministrativeStatus OperationalStatus

UsageStatus

20 0 0 Unlock Enable Idle

( Record Number = 1 )

Total Reports: 1

--- END

3) Conduct drive test.

Originate calls on the site, especially in the places where signals are shielded owing to topographical factors, such as in an elevator and at the corners of a building.

4) Optimize the network.

Improve the network coverage and try to prevent blind spots.


2-4

5) Conduct dialing test.

Observe the signal strength indicator on the MS in idle status and originate calls with the MS.

2.1.2 Slow Network Access


The access process is very slow. It takes about seven seconds on an average and sometimes much longer for the MS to access the network.

II. Troubleshooting


Query the BSC reverse powercontrol parameters and access

parameter messages (1)

Is the parameterconfiguration correct?

Modify the reverse powercontrol parameters andaccess parameters (2)


End

N

Conduct drive test (3)

Is the radio environmentpoor and the Ec/lo too high?

Optimize network

Y

Y

N

Y

Check the BTS operation

Figure 2-2 Troubleshooting flowchart for MS slow network access

Steps:

1) Query the BSC reverse power control parameters and access parameter messages.

a) Execute the command LST RRMINF to query BSC reverse power control parameters. For example:


2-5

LST RRMINF: CN=8, SCTID=0, CRRID=10, RRMINF=RCLPC;

b) Execute the command LST SYSMSGPARA to query BSC access parameter messages. For example:

LST SYSMSGPARA: CN=8, SCTID=0, CRRID=10, CCMINF=APM;

The value of the "Time of Response Timeout" should not be too long, whereas that of the "Specified Tx Power Offset" should not be too small.

2) Modify the reverse power control parameters and access parameters.

a) Increase the value of parameter "NOM_PWR (Specified Tx Power Offset)".

"NOM_PWR" serves as the modifying factor when the MS evaluates the open loop transmit power.

If this parameter is too small, the close loop amendment using reverse power control measurement may not correct the deviation generated in open loop evaluation. The low initial access power may result in the initial access failure for several times. The value range is -8 – 7 dB, as specified in the protocol.

You may execute the command MOD APM to modify the NOM_PWR (Specified Tx Power Offset). For example:

MOD APM: CN=20, SCTID=0, CRRID=0, NOMPWR=8;

b) Decrease the value of parameter "ACC_TMO" in the access parameter messages .

"ACC_TMO" determines the time duration from the time when the access channel sends the access probe until the time when the BTS receives this access probe.

Actual Access Timeout = (2 + ACC_TMO) %80 ms. The value range of ACC_TMO is 0 – 15, where the "0" corresponds to 160 ms, with an increment of 80 ms.

If this parameter is too small, the wait-for-response time will not be long enough. Thus, some unnecessary probes may be sent, causing heavy load of the access channel and high probability of collision.

If this parameter is too great, each access may require multiple attempts. This may slow down the access attempt procedure.

When the initial power is low and wait-for-response time is long, the next access attempt is initiated in a long period (more than 400 ms). As a result, the network access slows down.

You may execute the command MOD APM to modify the "ACC_TMO". For example:

MOD APM: CN=20, SCTID=0, CRRID=0, ACCTMO=1;

3) Conduct drive test.


2-6

Perform a drive test on the site and observe whether the places with slow access features:

Poor signal strength High signal fluctuation Frequent IMSI detach for the MS in idle status

If the drive test equipment shows that the MS-received signal pilot is lower than -12 dB, the signal is poor.

If the drive test equipment shows that the strength of the signal received by the MS changes too much, the signal fluctuates greatly.


Use the MS to originate calls and compare the access time of the MS before and after modification.

Use the drive test equipment to observe the time duration from the time when the first originating message is sent till the time when the service connection message (or service selection response) is received. If the average access speed of the MS is 3 – 4 seconds, the fault is cleared.

Caution:

If the values of parameters "NOM_PWR" and "ACC_TMO" are set too large or small, it may affect the network quality. Therefore, you should modify these two parameters according to the actual situation, and take a test after the modification.

The slow call connection is usually due to the "NOM_PWR" and "ACC_TMO". Therefore, you should consider the coordination of these two parameters during modification.

2.1.3 Some MSs Failed to Access Network


Some MSs can find the network, but failed to access it owing to improper system parameter or MS version.

II. Troubleshooting



2-7

Query the MS protocolversion and model (2)

Is the protocol versioncorrect?

Modify the protocol versioninto the one supported by

the network (3)


End

N

Query the BSC protocolversion (1)

Y

Figure 2-3 Troubleshooting flowchart for MS access failure

Steps:

1) Query the protocol version of the BSC.

Execute the command LST MDU in the Service Maintenance System. Example: LST MDU:;

Result: %%LST MDU:;%%


Module Basic Information

------------------------

Subrack No. Module ID Protocol Version Min. Protocol Version Band Class

4 0 6 1 1900MHz

5 19 2 1 1900MHz

(Total result = 2)

--- END


2-8

2) Query the protocol version and model of the MS.

For some MSs of protocol version 6, you should use the overhead message of later version. If the BSC protocol version is earlier than 4, the MS of protocol version 6 will fail to access the network owing to the difference in the overhead message structures.

For the MS of earlier protocol version, you should use the overhead message of earlier version. If the BSC protocol version is later than 4, the MS of earlier protocol version will fail to access the network owing to the difference in the overhead message structures.

3) Modify the protocol version into the one supported by the network.

Execute the command MOD PREV in the Service Maintenance System. For example:

MOD PREV: FN=4, PREV=4, MINPREV=2;


Conduct a dialing test using the faulty MS and the MSs of different protocol versions (such as versions 1, 4, and 6).

2.1.4 IS-95 MS Accessed CDMA 1X Network Illegally


The IS-95 MS accessed the network that allows the CDMA 1X MS only.

II. Troubleshooting



2-9

Query the minimum protocolversion set by the BSC (1)

Is the setting of minimum protocol

version wrong?

Modify the minimumprotocol version into the onesupported by the network (2)


End

Y

Check the consistency of thehost data and BAM data

Is the host dataconsistent with the

BAM data?

Re-configure the minimumprotocol version supported

by the network (4)

N

N

Y

Y

Figure 2-4 Troubleshooting flowchart forillegal access of IS-95 MSs to CDMA 1X network

Steps:

1) Query the minimum protocol version of the BSC.

Execute the command LST MDU in the Service Maintenance System.Example LST MDU: FN=4, MN=0;

Result %%LST MDU: FN=4, MN=0;%%


Module Basic Information

------------------------

Subrack No. Module ID Protocol Version Min. Protocol Version Band Class

4 0 6 1 800MHz

(Total result = 1)

--- END

2) Modify the minimum protocol version to the one supported by the network.


2-10

Execute the command MOD PREV to modify the protocol version. For example:


In the CDMA 1X network that prohibits the access of IS95 MS, you should set both min_prev and prev to 6.

3) Check the consistency of the host data and the BAM data.

Execute the command STR CRC in the Service Maintenance System. For example:

STR CRC: FN=4, BTP=CSPU;

4) Re-configure the minimum protocol version supported by the network.

Execute the command MOD PREV in the Service Maintenance System. For example:


This fault seldom occurs. It may result from data inconsistency. In this case, contact Huawei technical support engineers to locate and clear the fault.


Conduct a dialing test using the IS-95 MS and the IS-2000 MS at the same time. Normally, the IS-2000 MS can access the CDMA 1X network, while the IS-95 MS cannot.

2.2 MOC Failure

2.2.1 Assignment Failure (no radio resource available)


A mobile-originated call (MOC) fails. You can trace the A1 interface signaling of this MOC procedure through the Service Maintenance System.

The signaling tracing result shows that the cause value of the Assignment Failure message is " no radio resource available, 0x21".

II. Troubleshooting (AAL2 traffic link fault)



2-11

BTS is configuredwith wrong links

Query the AAL2 trafficlinks currently-configured

at BSC side (1)

Query the AAL2 trafficlinks currently-configured

at BTS side (2)

Check whether the AAL2links configured at bothsides are consistent. (3)

Is a new link required?

Configure an AAL2 trafficlink at BTS side (6)

Configure AAL2 traffic linksat BSC (4)

YY

N

Y

Y N

End


N

N

IsBSC configured with

necessary AAL2links?

Is BTS configuredwith more AAL2 links

than BSC?

Delete the incorrectly-configured AAL2 traffic link

Figure 2-5 Troubleshooting flowchart for assignment failure owing to AAL2 traffic link fault

Steps:

1) At the BSC side, query the AAL2 traffic links currently-configured between the BSC and the BTS.

Execute the command LST AAL2PATH in the Service Maintenance System.

Example LST AAL2PATH: PATHANI="129.11.17.116", PATHID=1;

Result %%LST AAL2PATH: PATHANI="129.11.17.116", PATHID=1;%%


AAL2 Path

---------


2-12

Ajacent Node Flag Path ID Subrack No. Slot No. Port No. AAL2 VPI AAL2

VCI Path Ownership Control Path ID Control Subrack No. Control Board

Type Bandwidth (M)

129.11.17.116 1 4 0 43 1 250

Local Node 80.17.130.0 4 CSPU 1.60

(Total result = 1)

--- END

2) At the BTS side, query the AAL2 traffic links configured between the BSC and the BTS.

Execute the command LST BTSLNK in the Service Maintenance System. Example LST BTSLNK:;

Result %%LST BTSLNK:;%%


BTS Link Information

--------------------

BTS ID Link Type Subrack No. Slot No. Connection Mode E1

Sequence Bandwidth (M) Link Flag BOOTP Flag

0 O&M Link 4 0 IMA Mode 1(2)

0.11 1-255 2-44


0.11 1-255 4-45

(Total result = 2)


--------------------


Sequence Bandwidth (M) Link Flag

0 Signaling Link 4 0 IMA Mode 1(2)

0.11 1-254

0 Traffic Link 4 0 IMA Mode 1(2)

1.60 1-250-1


0.11 1-254


2-13


1.60 1-250-1

(Total result = 4)

--- END

3) Check whether the AAL2 traffic links configured at the BTS side are consistent with those configured at the BSC side.

Compare the AAL2 traffic links configured at both BSC and BTS. They should have the correspondence as listed in Table 2-1.

Table 2-1 BSC-BTS AAL2 traffic link correspondence

Result queried at BSC side Result queried at BTS side

AAL2 VPI 1 VPI at BSC 1

AAL2 VCI 250 VCI at BSC 250

Path ID 1 PVC index 1

4) At the BSC side, configure the AAL2 traffic links between the BSC and the BTS.

Execute the command ADD BTSTRFLNK in the Service Maintenance System. For example, configure an AAL2 traffice link at the BSC side. VPI: 1; VCI: 250; PVCIDX: 1.

ADD BTSTRFLNK: BTSID=0, SN=SN0, LM=IMA, IMAGN=0, TRFLNKLST="1-250-1",

LNKBW=BW1.6M;

5) Delete the specified AAL2 traffic link at the BTS side.

Execute the command RMV BTSTERTRFLNK in the Service Maintenance System. For example, delete an AAL2 traffic link at the BTS side.VPI: 1; VCI: 250.

RMV BTSTERTRFLNK: BTSID=0, BCPMID=0, BTSAALTP=AAL2, BTSVCI=250;

6) At the BTS side, configure the AAL2 traffic links between the BSC and the BTS.

For example, configure an AAL2 traffic link at the BTS side. In the Service Maintenance System, execute the command:

ADD BTSTERTRFLNK: BTSID=0, BCIMID=0, LNKGRPID=0, LNKPOR=0, BCPMID=0,

BSCAALTP=AAL2, BSCVCI=250, BTSAALTP=AAL2, BTSVCI=250, PVCIDX=1;



2-14

Use the MS to originate calls. The call test should involve all the AAL2 traffic links related to the above modifications.

For example:

If the number of AAL2 traffic links configured between the BSC and the BTS is "n", originate calls for n+1 times.

Through the Service Maintenance System, trace the Abis interface signaling of all the MOC procedures made in the dialing test and observe the Abis Connect messages.

If all the AAL2 traffic link indexes involved in the modifications are identical with the "Traffic Circuit ID" contained in the Abis Connect messages traced, the fault is cleared.

Caution:

The VCCI value in the parameter TRFLNKLST related to the command ADD BTSTRFLNK at the BSC side must be consistent with the PVCIDX value related to the command ADD BTSTERTRFLNK at the BTS side, as listed in Table 2-2.

Table 2-2 Parameter correspondence between ADD BTSTRFLNK and ADD BTSTERTRFLNK

Network element BSC BTS

Command ADD BTSTRFLNK ADD BTSTERTRFLNK

Parameter Serial No.

TRFLNKLST (VPI-VCI-VCCI)

BSCVPI BSCVCI PVCIDX

1 1 250 1

2 1 249 2

3

1-250-1, 1-249-2, 1-248-3 1 248 3

III. Troubleshooting (clock fault)

Clock fault may also result in assignment failure in MOC procedure. For detailed troubleshooting method, see section 20.4.3, “CFMR DSP Loading Faile”.


2-15

2.2.2 Assignment Failure (requested terrestrial resource unavailable)


An MOC fails. You can trace the A1 interface signaling of this MOC procedure through the Service Maintenance System.

The signaling tracing result shows that the cause value of the Assignment Failure message is "requested terrestrial resource unAVAIL, 0x22".

II. Troubleshooting (EVC resources unavailable)


Query the allocationinformation of the EVC

resources (2)

Are the EVC resourcesused up?

Adjust the allocation ofEVC resources (3)


End

Y

Determine the speechservice options employed in

the current call (1)

N

Figure 2-6 Troubleshooting flowchart for assignment failure owing to EVC resources unavailable

Steps:

1) Determine the speech service options employed in the current call.

In the Service Maintenance System, click [Trace/A1 interface trace] to query the speech services employed in the call.

2) Query the allocation information of the EVC resources.

If the EVC resources required by the service are fully occupied, or there are no related EVC resources, assignment failure will occur since the terrestrial circuit is unavailable.


2-16

Execute the command DSP DSPTCSTAT to query the EVC resources in the subrack where the circuit assigned resides.

Example DSP DSPTCSTAT: FN=4;

Result %%DSP DSPTCSTAT: FN=4;%%


Query Result

------------

UseEVRC+Q8KTotalTimeslots = 160

UseEVRC+Q8KIdleTimeslots = 160

UseEVRC+Q13KTotalTimeslots = 160

UseEVRC+Q13KIdleTimeslots = 160

UseQ8K+Q13KTotalTimeslots = 192

UseQ8K+Q13KIdleTimeslots = 192

--- END

3) Adjust the allocation of EVC resources.

If no idle timeslots can be allocated for the service option requested by the MS, it is possible that the proportion of EVC voice code allocation algorithm is not appropriate.

If the proportion is appropriate, but the EVC resources are insufficient and less than the radio channel resources, you should expand the capacity and add more CEVCs.

You can adjust the allocation proportion of EVC resources according to the traffic measurement result, the allocation of various resources, and the times of assignment failures for each type of resources.

You can execute the command MOD EVCDSP to modify EVC resources allocation proportion. For example:

MOD EVCDSP: FN=4, LODPRGMTP=EVRC+QCELP8K;


Originate calls using the MS. The test involves the speech calls of all types of services. You can observe the EVC resources occupancy especially when the traffic is heavy.


2-17

III. Troubleshooting (A2 circuit fault)

During the MOC process, the Assignment Failure message is received and the cause value is "required terrestrial resource unavailable". The call fails since the MSC cannot have available CIC resources to set up the call.

See section 17.3, ”A2 Interface Circuit Fault” for the detailed troubleshooting method.

2.2.3 Clear Command (protocol error between BSC and MSC)



The signaling tracing result shows that the MSC sends a Clear Command directly after receiving the CM Service request from the BSC, with a cause value of "protocol error between BSC and MSC, 0x60".

II. Troubleshooting


Compare the tw o A-interfaceprotocol v ersions queried (2)

Are the tw o A-interface protocol v ersions

consistent?

Modify A-interfaceprotocol v ersion to ensure

consistency (3)

Conduct dialing test(4)

End

N

Query A-interface protocolv ersion of BSC and MSC (1)

Y

Figure 2-7 Troubleshooting flowchart for MOC failure owing to inconsistency of A-interface versions

Steps:

1) Query the A-interface protocol versions of BSC and MSC.


2-18

Execute the command LST BSCINF to query the A-interface protocol version of BSC.

Example LST BSCINF:;

Result %%LST BSCINF:;%%


BSC Basic Information

---------------------

BSC IP Address = 129.11.17.4

BSC Subnet Mask = 255.255.0.0

Manufacturer ID = 3

Entity ID = 45381

Mobile Country Code = 460

Mobile Network Code = 3

MSC ID = 0x123456

A-interface Version No. = IOS4.1

PN Code Increment = 4

CSWS Subrack Type = E1 Switching

RFN Clock Board = UTCP board

(Total result = 1)

--- END

To query the A-interface protocol version of MSC, contact the MSC maintenance engineer.

2) Compare the A-interface protocol versions of BSC and MSC.

The A-interface protocol versions of MSC and BSC should match with each other.

If the A-interface protocol version of BSC is "IOS4.1", you should configure that of MSC to be at least IOS4.0. If the A-interface protocol version of MSC is lower than that of BSC, calls cannot be connected.

If the A-interface protocol version of MSC is higher than that of BSC, calls can be connected, but some services will be restricted.

3) Modify the A-interface protocol versions of BSC and MSC to ensure the consistency.

Execute the command MOD BSCINF to modify the A-interface protocol version of BSC. For example: MOD BSCINF: APVER=IOS4.1;


2-19

Contact the MSC maintenance engineer to modify the A-interface protocol version of MSC.


Originate calls using both the IS-2000 MS and the IS-95 MS.

2.2.4 Clear Command (authentication failure)



The signaling tracing result shows that the MSC sends a Clear Command, with a cause value of "Authentication Failure, 0x1A".

II. Troubleshooting



2-20

Check whether BSC allowsglobal challenge (1)

Is the global challengeallowed?

Check MS and HLR/ACauthentication parameters (3)

Are the authenticationparameters properly set?

Modify MS or HLR/ACauthentication parameters (4)

Perform SSD update andauthentication test on MS (5)

Is the fault cleared after theSSD update?

Inhibit authentication ofspecific MS (6)

Enable BSC global challenge(2)


End

N

Y

Y

N

Y

N

Figure 2-8 Troubleshooting flowchart for MOC failure owing to authentication failure

Steps:

1) Query whether the BSC allows global challenge.

Execute the command LST SYSMSGPARA in the Service Maintenance System.

Example LST SYSMSGPARA: CN=20, SCTID=0, CRRID=0, CCMINF=AUTH;

Result %%LST SYSMSGPARA: CN=20, SCTID=0, CRRID=0, CCMINF=AUTH;%%


Authentication Information

--------------------------


2-21

Cell ID Sector ID Carrier ID Authentication Flag Auth Random Check Value …

20 0 0 Not Authenticate 100.00…

(Total result = 1)

--- END

Note:

If the HLR/AC needs to authenticate the MS, you should enable the global challenge of the BSC. The BSS informs the MS of the authentication request through overhead messages to ensure the AUTHR is calculated based on the RAND and then reported to the MSC.

The authentication parameters include AUTHR, RAND (determined by the BSC), RANDC, and COUNT. The HLR/AC authenticates the MS according to these parameters.

2) Enable BSC global challenge.

Execute the command MOD AUTH in the Service Maintenance System. For example:

MOD AUTH: CN=20, SCTID=0, CRRID=0, AUTH=YES;

Table 2-3 lists the [AUTH] field values in the AUTH_PARA data table.

Table 2-3 Description of AUTH in AUTH_PARA data table

AUTH field value Meaning

0 The message does not contain relevant authentication information unit.

1 The message contains relevant authentication information unit.

3) Query MS/R_UIM and HLR/AC authentication parameters.

Check the HLR/AC and MS/Removable User Identity Module (R_UIM). Similar to the Subscriber Identity Module (SIM) in GSM system, the R_UIM serves as the identification card of CDMA MS that is related to subscriber security. The MS with the R_UIM employs the UIM ID to identify its R_UIM in authentication instead of the ESN.

The values of IMSI, ESN and A_Key should be verified. Ask the HLR/AC, MS or R_UIM maintenance engineers for help.

4) Modify MS/R_UIM or HLR/AC authentication parameters.

Modify the authentication parameters of HLR/AC or MS/R_UIM to make them consistent with each other.


2-22

The values of IMS, ESN or A_Key should be verified. Contact the HLR/AC and MS/UIM maintenance engineers for help.

5) Perform SSD update and authentication test on MS.

To ensure SSD consistency between the HLR/AC and the MS, update the SSD manually.

Trigger an SSD update procedure by executing related commands at the HLR/AC, or by deleting the subscriber first and then redifining the subscriber at the HLR. For details, contact the HLR/AC maintenance engineers.

Check whether the global challenge signaling procedures of other legal MSs are successful. If the global challenge is successful, the call proceeding will continue.

If a certain MS and R_UIM always fail in authentication, insert the R_UIM into another MS that passed authentication or and insert another R_UIM that passed authentication into original MS, and conduct the comparison test. Observe the authentication procedure, and find out the cause of the failure.

insert the R_UIM into another MS that passed authentication or and insert another R_UIM that passed authentication into original MS,

6) Inhibit the authentication of specific MS.

The MS is incapable of authentication in the following cases:

After the authentication function is enabled in the BSC, the MS still fails to report authentication parameters in origination message, paging response, registration, and short message, or the authentication parameters are incomplete.

The SSD cannot be updated normally (see Chapter 5, “Authentication Fault” for details).

When the authentication parameters are set correctly, conduct comparison tests for the R_UIM. The specific R_UIM fails in the authentication.

In the HLR/AC, disable the authentication function for the MS (or faulty R_UIM) that does not support it, and the fault can be cleared.

Ask the HLR/AC maintenance engineers for help.


Use the MS to originate calls, accept calls and send short messages, and observe whether the operations are successful.


2-23

2.2.5 N_DISCONNECT_IND Received



The signaling tracing result shows that the BSC receives an N_DISCONNECT_IND after sending a CM Service Request. Hence a call failure occurs.

II. Troubleshooting



2-24

Check A1 interface signalinglink (1)

Is the A1 interface signalinglink faulty?

Check BSSAP networkindicator consistency between

BSC and MSC (3)

Are the BSSAP networkindicators inconsistent?

Modify the BSSAP networkindicators (4)

Check the consistency ofSCCP subsystem Nos. (5)

Are the Nos. inconsistent?

MSC fault

Clear the fault of the A1 interfacesignaling link (2)


End

Y

N

N

N

Y

Modify the SCCP subsystemNos. (6)

Y

Figure 2-9 Troubleshooting flowchart for MOC failure owing to N_DISCONNECT_INDs received

Steps:

1) Check whether the A1 interface signaling link is normal.

See Chapter 17, “Link and Circuit Fault” for details.

2) Clear the fault of the A1-interface signaling link.

See Chapter 17, “Link and Circuit Fault” for details.


2-25

3) Check whether the BSSAP network indicators at the BSC and at the MSC are consistent.

Execute the command LST SCCPSSN in the Service Maintenance System to query the BSSAP network indicator configuration at the BSC.

Example LST SCCPSSN: SSNIDX=0;

Result: %%LST SCCPSSN: SSNIDX=0;%%


SCCP Subsystem

--------------

Subsystem Index = 0

Network Indicator = National

Subsystem No. = BSSAP/A Interface

DSP = 0x00E003

OSP = 0x00D00A

Local Related Subsystem 1 = Invalid





Backup Subsystem Index = Invalid

(Total result = 1)

--- END

To query the BSSAP network indicator configuration at the MSC, contact the MSC maintenance engineers.

4) Modify BSSAP network indicators.

This is for the purpose of data consistency between the BSC and the MSC.

Execute the command ADD N7DPC in the Service Maintenance System to modify the BSSAP network indicators at the BSC. For example:

ADD N7DPC: NI=NATC, SPCLEN=BIT24, DPC="0x00E003";

After executing the command, format the data and reset the BSC to make the data valid.

To modify the BSSAP network indicators at the MSC, contact the MSC maintenance engineers.


2-26

5) Check whether the SCCP subsystem Nos. of BSC and MSC are consistent.

A fault occurs if the SCCP subsystem Nos. are inconsistent.

Execute the command LST SCCPSSN in the Service Maintenance System to query the SCCP subsystem Nos. of the BSC.

Example LST SCCPSSN:SSNIDX=0;

Result %%LST SCCPSSN: SSNIDX=0;%%


SCCP Subsystem

--------------

Subsystem Index = 0

Network Indicator = National

Subsystem No. = BSSAP/A Interface

DSP = 0x00E003

OSP = 0x00D00A






Backup Subsystem Index = Invalid

(Total result = 1)

--- END

To query the SCCP subsystem Nos. of MSC, ask the MSC maintenance engineers for help.

6) Modify SCCP subsystem Nos. to ensure data consistency.

Execute the command MOD SCCPSSN in the Service Maintenance System to modify the SCCP subsystem Nos. at the BSC. For example:

MOD SCCPSSN: SSNIDX=0, SSN=BSSAPI;

To modify the SCCP subsystem Nos. of MSC, contact the MSC maintenance engineers.



2-27

Use the MS to make MOCs and MTCs.

2.3 MTC Failure

2.3.1 BSC Not Received Paging Request


The MS in idle state fails to receive calls after power-up. You can trace the A1 interface signaling of the called MS through the Service Maintenance System.

The signaling tracing result shows that the MSC has not issued a Paging Request to the BSC.

II. Troubleshooting



2-28

Query the called MSinformation registered in

HLR (1)

Query the settinginformation of the called

MS (2)

Query BSC Switch-onRegistration Flag (3)

Perform called MS switch-on registration (6)

Enable switch-onregistration (4) Clear MSC/HLR fault (5)


End

Y

N

Y

N Y

N

BSC not receive PagingRequest

Is the switch-onregistrationenabled?

Is the MS data consistent with the

HLR data?

Called MS re-registers inHLR.

Has the called MS already

performed switch-onregistration?

Figure 2-10 Troubleshooting flowchart for BSC not Receive Paging Request Message

Steps:

1) Query the subscription information of the called MS in the HLR.

Query the subscriber’s IMSI, MDN and ESN registered in the HLR. Ask the HLR maintenance engineers for help.

2) Query the setting information of the called MS.

Use the super password to query the ESN of the MS and the pre-set IMSI and MDN.

3) Query the BSC Power-up Registration Flag.


Example


2-29

LST SYSMSGPARA: CN=20, SCTID=0, CRRID=0, CCMINF=SPM;

Result %%LST SYSMSGPARA: CN=20, SCTID=0, CRRID=0, CCMINF=SPM;%%


System Parameter Message

------------------------

Cell ID = 20

Sector ID = 0

Carrier ID = 0

Registration Zone = 0

Reserved Registration Zones = 0

Zone Timer Duration = 60 Minutes

Multiple SIDs Storage Flag = No

Multiple NIDs Storage Flag = No

Paging Channel Number = 1

Max. Timeslot Period Index = 1

Local Registration Flag = Automatic registration

is required for local MSs (non-roaming MSs)

SID Roaming Registration Flag = Automatic registration

is required for MSs roaming from other SID

NID Roaming Registration Flag = Automatic registration

is required for MSs roaming from other NID

Power-up Registration Flag = Registered

Power-down Registration Flag = Registered

System Message Parameter Change Registration Flag = Registered

Time Registration = 30.893Minutes

Distance Registration = Not Registered

Rescan Flag = Not Scan

BS Latitude = North Latitude0hours0minutes0seconds

BS Longitude = East Longitude0hours0minutes0seconds

(Total result = 1)

--- END

If the "Power-up Registration Flag" is "Registered", the power-up registration is enabled. Otherwise, the power-up registration is disabled.

4) Enable BSC Power-up Registration.

Execute the command MOD SPM in the Service Maintenance System. Suppose the cell ID of the called MS is 20, the sector ID is 0, and the carrier ID is 0, execute:

MOD SPM: CN=20, SCTID=0, CRRID=0, PWRUP=YES;


2-30

After executing this command, repeat step 3 to check the modification.

5} Clear MSC and HLR fault.

If the subscriber information in the HLR is correct and the MS has registered after power-up, it is not a BSC fault.

If the MSC has not issued a Paging Request yet, contact the maintenance engineers of MSC and HLR to locate and remove the fault.

6) Perform power-up registration for the called MS.

Power up the called MS for registration.


Originate an MOC first. If the call fails, see section 2.2 for troubleshooting.

If the MOC is successful, make MTCs. During the test, click [Airbridge cBSS Maintenance/Maintenance/Review A1 Interface Tracing] to view the A1 interface signaling of the BSC serving the called MS. If the Paging Request message issued by the MSC is found, the fault is cleared.

2.3.2 BSC Not Received Paging Response


An MTC fails. If tracing the Um interface signaling on the MTC flow through the Service Maintenance System, you detect that the BSC receives no Paging Response.

II. Troubleshooting (IMSI inconsistent)

Symptom 1

The signaling trace result shows that there is no response after the MSC sends a paging request to the BSC.

The Mobile Country Code (MCC) of the MS is "450", and the value cannot be modified.

Symptom 2

The signaling trace result shows that the IMSI in the HLR is 460000094001xxxx, while the IMSI in the Paging Request sent from the MSC to the BSC is 46003094001xxxx.



2-31

Query MSC dataconfiguration (1)

Query MS parameters


Modify data configuration(7)

End

Modify MSC and HLR dataconfiguration (2)

Modify data configuration(4)

BSC internal processingerror

MS fault

N

Y

Y

Y

Y

N

N

N

MTC fails

Are the GT translation data and subscriber information

defined in HLR correct?

Is the Paging Request messageconsistent with BSC data? (3)

Are the MS parameters consistent with subscriber information defined in

HLR? (6)

Does BSC issue the Paging Requestmessage? (5)

Y

Figure 2-11 Troubleshooting flowchart for IMSI inconsistency

Steps:

1) Query MSC data configuration.

Query the registration information of the MS and the GT translation data respectively. For the specific operation on the MSC, ask the MSC maintenance engineers for help.


2-32

2) Modify MSC and HLR data configuration.

If the GT translation data is configured incorrectly, ask the MSC maintenance engineer to modify it.

If the MS registration information is incorrect, ask the HLR maintenance engineers to modify it.

3) Check whether the Paging Request is consistent with the BSC data configuration.

In the Service Maintenance System, click [Maintenance/Trace/A1 Interface Message Tracing] to view the A1 interface signaling traced. Check whether the IMSI and target cell information in the paging message are consistent with the actual configuration of BSC.

4) Modify data configuration.

If the content of the Paging Request is inconsistent with the BSC data configured, check whether the MSC data or BSC data is configured incorrectly.

For the incorrectly-configured BSC data, execute the command ADD CELL or RMV CELL to modify it.

For the incorrectly-configured MSC data, ask MSC maintenance engineers for help.

5) Check whether the BSC sends a Paging Request.

In Service Maintenance System, trace Um interface signaling of MS, and check whether BSC sends a Paging Request to MS.

If the BSC sends no Paging Request , it is a BSC internal processing error.

6) Check whether the MS parameters are consistent with the subscriber information defined in the HLR.

Query the MCC and IMSI of the MS using super password, and check whether they are consistent with those assigned to the MS in the HLR. If consistent, the MS may be faulty.

7) Modify data configuration.

If the MS parameters are not consistent with the subscriber information defined in the HLR, enter the function setup menu of the MS with super password and modify the MCC and IMSI of the MS.


2-33

If certain parameters of the MS cannot be modified (for example, the MCC of the MS is set to 450, and the value cannot be modified), the IMSI should be converted through the MSC. For the specific operation on the MSC, contact the MSC maintenance engineers.


Conduct a dialing test using the MS (serving as the called party). If the MTC succeeds, the fault is cleared.

III. Troubleshooting (LA/cell data not configured)

Symptom 1

The MSC needs to send a Paging Request to multiple signaling points of the BSC. However, some of the BSC signaling points fail to receive this message.

Symptom 2

After the BSC receives the Paging Request sent by the MSC, it does not send a Page message to the cell specified in the Paging Request.



2-34

Trace A1 interface signaling (1)

Query BSC cell configuration (2)

Query MSC LA and cellinformation (3)

Compare MSC and BSC cellconfiguration (4)

Is the configurationconsistent ?

Modify MSC LA and cellconfiguration (5)

Verify data consistency

End

Other problems (6)

N

Y

BSC not receive PagingResponse message

Figure 2-12 Troubleshooting flowchart for MTC failure owing to LA/cell data not configured

Steps:

1) Trace A1 interface signaling.

In the Service Maintenance System, click [Maintenance/Trace/A1 Interface Message Tracing] to view the A1 interface signaling tracing of each signaling point, and record the signaling points that do not receive the Paging Request.

2) Query cell configuration at the BSC.

Execute the command LST CELL to query the cell configuration at the BSC.

Example LST CELL:

Result


2-35

%%LST CELL:;%%


Cell Information

----------------

BTS ID BTS Name Cell ID Sector ID PN Code System ID Network ID

0 BTS0000 20 0 40 12062 6

1 BTS0001 21 0 48 12062 6

Data Packet Area ID Location Area Code BS ID Forced Assignment Allowed

Flag

3 0x0003 0 Prohibited

3 0x0003 0 Prohibited

(Total result = 2)

--- END

3) Query LA/cell configuration at the MSC.

Ask the MSC maintenance engineers to query the location area (LA) and cell configuration at the MSC.

4) Compare cell configuration at the MSC and the BSC.

Compare whether the cell configuration at the MSC and that at the BSC are consistent.

If inconsistent, modify the BSC and MSC data configuration. If consistent, the fault may result from other factors, and further analysis is necessary.

5) Modify location area and cell configuration.

You should perform this operation at the MSC side. Ask the MSC maintenance engineers for help.

6) Other causes.

If the MTC failure results from other factors, refer to the analysis of other cases.


2-36

Note:

During an MTC, after getting the current LA and cell information of the called MS from the VLR database (VDB), the MSC queries the signaling points covered in the LA/cell according to the LA and cell data configured in LA/Cell Data table. Then, the MSC sends a Paging Request to those signaling points. After receiving the Paging Request, the BSC checks whether its cell table contains the same LA/cell data as those listed in the cell list information element carried in the Paging Request. If so, the BSC sends the Paging Request to those LAs/cells. Otherwise, the BSC sends no Paging Request.

IV. Troubleshooting (MS registration abnormally)

The BSC fails to receive any Page Response, because the MS does not register normally.


Query MS registrationstatus (1)


End

Modify zone registrationparameters (2)

Enable Zone Registration(2)

Set Switch-onRegistration Flag to

"Registered" (2)

N

N

Y

Y

N


Is the Switch-onRegistration enabled?

Are the zoneregistration parameters set

correctly?

Y

Is the Zone Registrationenabled?

Figure 2-13 Troubleshooting flowchart for MTC failed owing to MS registration failure


2-37

Steps:

1) Query MS registration status.


Example LST SYSMSGPARA: CN=21, SCTID=0, CRRID=0, CCMINF=SPM;




------------------------

Cell ID = 21

Sector ID = 0

Carrier ID = 0








Local Registration Flag = Automatic

registration is required for local MSs (non-roaming MSs)

SID Roaming Registration Flag = Automatic registration

is required for MSs roaming from other SID

NID Roaming Registration Flag = Automatic registration

is required for MSs roaming from other NID







BS Latitude = North Latitude 0 hours 0 minutes

0 seconds

BS Longitude = East Longitude 0 hours 0 minutes

0 seconds

(Total result = 1)

--- END

In the parameter "Reserved Registration Zones=0", "0" means "not open area".


2-38

2) Modify registration flag.

Execute the command MOD SPM to set the "Switch_on Registration Flag" and "Switch_off Registration Flag" to "Registered".

If the parameter "Reserved Registration Zones" is set to "0" when zone registration is required, use the command MOD SPM to modify it.

For example, to set the "Power-up Registration Flag" and "Power-down Registration Flag" to "Registered", the "Reserved Registration Zones" to "1", and the "Zone Timer Duration" to M1 (1 minute), execute the command in the Service Maintenance System:

MOD SPM: CN=21, SCTID=0, CRRID=0, REGZN=0, TOTALZN=1, ZNTMR=M1, PWRUP=YES,

PWRDWN=YES;


Activate A-interface tracing in the Service Maintenance System, and then switch on and off the MS. If the system can trace the registration message, the fault is cleared.

Note:

During an MTC, the MSC judges the current status of the MS according to the subscriber data saved in the VLR, and determines whether to and how to send a Paging Request. If the status of the MS changes (for example, it is switched off or moves to other LA), but the MS fails to register the location update in time owing to certain causes, the system fails to update the subscriber data in the VLR (for example, fails to activate the registration) accordingly. In this case, the system may fail to page the MS. The cases of inactivated registration include:

The Power-up Registration Flag is "Not registered": After the MS power-up, the system fails to trigger the power-down registration procedure since the Power-down Registration Flag is set to "Not registered". As a result, the subscriber data saved in the VLR cannot be updated. When the MS is paged, the MSC sends a Paging Request according to the subscriber data saved in the VLR. At that time, the MS is powered down. Therefore, there is no response to the Paging Request. As a result, the system fails to page the MS.

The "Reserved Registration Zones" is "0": After the MS is registered in LA 1, the information of the subscriber in LA 1 is saved in the VLR. When the MS moves to LA 2, the MS does not trigger the registration procedure since the "Reserved Registration Zones" is set to "0". As a result, the subscriber data saved in the VLR is not updated. When the MS is called, the MSC sends a Paging Request to LA 1 according to the subscriber data saved in the VLR. The MS in LA 2 fails to receive that message, and thus fails to return a Paging Response.


2-39

V. Troubleshooting (incorrect registration-specific parameter configuration)

The BSC fails to receive any Page Response owing to the improper configuration of the zone registration-specific parameters.


Query system parametermessage (1)

Modify Registration Zone(3)

Other problems (6)

Modify zone registrationparameters (5)

Conduct dialing test

End

N

Y

N

Y


Is Registration Zoneset correctly? (2)

Are zone registrationparameters set correctly?

(4)

Y

Figure 2-14 Troubleshooting flowchart for MTC failure owing to incorrect registration-specific parameter configuration

Steps:

1) Query system parameter messages.






------------------------


2-40

Cell ID = 20

Sector ID = 0

Carrier ID = 0










SID Roaming Registration Flag = Automatic registration is

required for MSs roaming from other SID

NID Roaming Registration Flag = Automatic registration is

required for MSs roaming from other NID







BS Latitude = North Latitude 0 hours 0

minutes 0 seconds

BS Longitude = East Longitude 0 hours 0 minutes 0 seconds

(Total result = 1)

--- END

You can query the parameters such as "Registration Zone", "Reserved Registration Zones (TOTAL_ZONES)", and "Zone Timer Duration (ZONE_TIMER)".

2) Query the configuration of the registration zone.


If two different cells are configured as the same registration zone, the MS will not trigger zone registration. In this case, ask the network planning engineers to modify it.

3) Modify registration zone.

For the improperly-configured registration zone field, contact the network planning engineers to modify it.

Execute the command MOD SPM in the Service Maintenance System. For example:


2-41

MOD SPM: CN=20, SCTID=0, CRRID=0, REGZN=1;

4) Check zone registration parameters.


It is suggested that you set the parameters as below:

Reserved Registration Zones = 1 Zone Timer Duration = M1 (1 minute)

5) Modify parameters related to zone registration.

Execute the command MOD SPM in the Service Maintenance System. For example:

MOD SPM: CN=20, SCTID=0, CRRID=0, TOTALZN=1, ZNTMR=M1;

6) Other causes.

If no system parameter error occurs, refer to other related cases for troubleshooting.


After modifying the relevant system configuration parameters, perform idle handoff between two cells (configured as two different registration zones). Click [Airbridge cBSS Maintenance/Maintenance/View A Interface Tracing] and observe whether the MS initiates the registration. The registration type is "Zone Registration".

After the registration is successful, observe whether MOCs and MTCs are normal.

VI. Troubleshooting (fault of expand boundary page)

A). Fault of expand boundary page based on real LAC

Symptom:

After receiving the Paging Request from the MSC, the BSC does not send the Page Message to the neighbor link access control (LAC) of the one specified by the Paging Request.

To analyze and clear the fault of expand boundary page based on real LAC, proceed as follows:

1) Check the setting of the expand boundary page mode


2-42

Check whether the expand boundary page mode is set to “base on real LAC” through the maintenance console using the following command:

LST EBPGPARA:;

If the current expand boundary page mode is not “base on real LAC”, you can execute the following command through the maintenance console to change it.

MOD EBPGPARA: EXTBNDPAGEMODE=REALPAGE, STRATTIME=2;

In the above command, STARTTIME is a start parameter. After the above setting, if the BSC cannot receive the Page Response for twice successively, it will extend the page range based on real LAC and send the Page Message to the neighbor LAC.

2) Check the neighbor LAC setting

Execute the following command through the maintenance console to check the neighbor LAC setting:

LST NBRLAC:;

If the neighbor relation has not been configured, you can add it through the maintenance console. For example, to add the neighbor relation between LAC1 (0 x 0001) and LAC2 (0 x 0002), execute the following command:

ADD NBRLAC: REALLAC="0x0001", NBRLAC1="0x0002";

B). Fault of expand boundary page based on idle handoff relation

Symptom:

After receiving the Paging Request from the MSC, the BSC does not send the Page Message to the neighbor cell that has idle handoff relation with the cell specified by the Paging Request.

To analyze and clear the fault of border extension page based on idle neighborhood, proceed as follows:

1) Check the setting of expand boundary page mode

Check whether the expand boundary page mode is set to “base on idle neighborhood” through the maintenance console using the following command:

LST EBPGPARA:;

If the current border extension page mode is not “base on idle neighborhood”, you can execute the following command through the maintenance console to change it.

MOD EBPGPARA: EXTBNDPAGEMODE=NBRPAGE, STRATTIME=2;


2-43

2) Check border cell setting

Execute the following command through the maintenance console to check the border cell setting:

LST CELL:;

If the border cell setting is incorrect, you can change it through the maintenance console. For example, to change cell 1 (0 x 01) to a border cell, execute the following command:

MOD CELL: CN=1, IFBORDCELL=YES;

3) Check the setting of idle neighborhood relation

Execute the following command through the maintenance console to check the setting of idle neighborhood relation:

LST NBRCDMACH: NBRINF=IDLENBR;

If the idle neighborhood relation is not configured between two border cells, you can add it through the maintenance console. For example, to add idle neighborhood relation between cell1 and cell 2, execute the following command:

ADD NBRCDMACH: CCDMACH="1-1-1-1", NBRCDMACHS="2-2-2-2", SFFLAG=SINGLE,

DFFLAG=SINGLE, NBFLAG=SINGLE;

C). Fault of MSC expand boundary page

Symptom:

The MSC switches on the expand boundary page, but the paging fails.

To analyze and clear the fault of the expand boundary page, proceed as follows:

1) Check the setting of expand boundary page mode

To check whether the expand boundary page mode is “base on MSC”, execute the command:

LST EBPGPARA:;

If the current border extension page mode is not “base on MSC”, you can execute the following command through the maintenance console to change it.

MOD EBPGPARA: EXTBNDPAGEMODE=INTERBSC;

2) Check whether the MSC can process the cross-signaling point Page Response


2-44

If the BSC does not support the cross-signaling point Page Response, disable the cross-signaling point paging message transfer function of the BSC using the following command:

MOD SOFTPARA: SRVMN=CCM, PRMNO=20, PRMV="0x00000000";

If the MSC supports the cross-signaling point Page Response, enable the cross-signaling point paging message transfer function of the BSC using the following command:


2.3.3 Assignment Failure (no radio resource available)


The MOC fails for several times successively. The A interface signaling tracing on the BSC and MSC shows that the MSC receives an Assignment Failure. In addition, the BTS overload alarm occurs on the BSC alarm console.

II. Troubleshooting



2-45

Query BTS load information(1)

Is the BTS load reportedconsistent with the actual

value? (2)

Clear the BTS fault (3)

Optmize the network (4)

BTS load is decreased

End

Y

N


Figure 2-15 Troubleshooting flowchart for assignment failure due to BTS overload

Steps:

1) Query BTS load information.

For example, execute the following command to query the load of the sector carrier whose carrier ID is 0, sector ID is 0, and cell ID is 20.

DSP RADIORESINDICATION: CN=20, SCTID=0, CRRID=0;

2) Check whether the BTS load reported is consistent with actual situation.

If the BTS cannot report the actual load, it is possible that:

The BTS is faulty. The basic access threshold configured on the BSC is improper.


2-46

Note:

The forward load of BTS is closely relevant to the number of forward common channels configured to the BSC and the number of data service subscribers served by the BTS. The more the forward common channels and data service subscribers are configured, the heavier the forward load of the BTS becomes. When the forward load exceeds the basic access threshold set for the BSC, the BSC restricts the calls and therefore assignment failure occurs..

3) Clear the BTS fault.

Contact the BTS maintenance engineers to clear the fault.

4) Optimize the network.

If the load reported reflects the real status of the BTS, ask the network optimization engineers to optimize the network so as to decrease the load.

If network optimization is unnecessary, increase the BSC basic access threshold with the help of the network optimization engineers.


Originate an MOC or conduct a paging test at the expected BTS load. If the MS can originate the call or paging normally, it indicates the fault has been cleared.

2.4 Speech Quality Problems

2.4.1 Echo


The two parties involved in a call can communicate normally. However, one hears his own voice when speaking. Weaker than normal voice, the echo may occur at the beginning of or throughout the conversation.

II. Troubleshooting (electrical echo)

Echo comprises electrical echo and acoustic echo. The troubleshooting measures vary with the types of echo.



2-47

Echo occurs to MS-to-PSTNcall

Does echo appear in somefixed phones only?

Fault of fixed phone (1)

Y

NDoes echo probability exceed

normal range? (2)

Is MSC configured with EC ?Y

Is BSC configured with EC ?

Check EC data configuration(4)

Is EC configuration correct?

Modify EC configuration (5)


End

Remove fault at MSC (3)N

Normal

EC is not configured in thesystem

Configure EC

N

Y

Y

N

N

Y

Figure 2-16 Troubleshooting flowchart for electrical echo


2-48

Steps:

1) Check whether echoes result from the fault of a telephone.

The fault may have occurred to the subscriber board or subscriber line of a telephone or the telephone itself.

Ask the maintenance engineers of public switched telephone network (PSTN) to locate and remove the fault.

2) Check whether the echo probability exceeds the value range allowed.

The echo probability allowed is 0 – 5%. Measure the echo probability. If it is small, conduct a large number of dialing tests on different types of fixed network phones (local or toll). The echo probability lower than 5% is regarded as normal.

3) Ask the MSC maintenance engineers to remove the fault.

4) Check EC data configuration.

a) Query data configuration of EC unit:

Execute the command LST EVCEC in the Service Maintenance System. For example:

LST EVCEC: FN=5, SN=4, IDX=0;

b) Check the following parameters of EC. The default values are:

Network Level Attenuation = 6 dB Tail Return Loss = 6 dB Nonlinear Processor = On

Modify them according to actual situation.

c) Query EC working status:

Execute the command DSP ECSTATUS to query the configuration of EC unit. For example:

DSP ECSTAT: FN=5, SN=4, OPT=ECUNIT, ECNO=0;

The normal status should be "Started".

5) Modify EC data configuration.

a) Check EC data configuration. If it is not the default value, check whether special modification is made according to actual situation.

b) If the EC status is "Disable", execute the command SET ECENABLE to enable the EC. For example:


2-49

SET ECENABLE: FN=5, SN=4, ECNO=0, OPT=ENABLE;


Conduct dialing tests to check whether the fault is cleared. Use different fixed network phones at different offices to conduct dialing tests (at least for 100 times), and measure the echo probability. If the echo probability is lower than 5%, it means the fault is removed.

III. Troubleshooting (acoustic echo)


Y

Fault of peer end (4)Does echo appear

in some MSs?

Fault of MS (2)

Is EC level gain normal?

Collect the model of MSswith echo (5)

N

Y

N

N

Y

Query EVC DSP and EClevel gain (3)

Optimize the network (6)


End

Echo appears at localend in MOC (1)

Is peer MS is in localCDMA network?

Figure 2-17 Troubleshooting flowchart for acoustic echo

Steps:


2-50

1) Clear the echo heard at local end during the MTC.

Generally, when the peer party is a mobile subscriber, the echo heard at the local end is acoustic echo. You can determine the acoustic echo as below:

As the volume of the MS speaker is turned down, the echo decreases or disappears.

2) Clear the echo caused by the MS.

The speaker and the microphone of the MS are not well isolated. Such kind of fault cannot be cleared.

The MS volume is extremely large. You can solve the fault by turning down the volume.

Some MSs, such as S200, may have echoes when connecting with an earphone. In this case, ask the MS manufacturer to remove the fault.

3) Check EVC DSP and EC level gain.

Forward and reverse level gain adjustment is enabled on the EVC DSP. The value of the level gain depends on whether the EC is configured at the BSC. If the level gain of the CDMA system is too high, the probability of the acoustic echo may increase.

a) Execute the command LST EVCDSP to query EVC DSP forward level gain and reverse level gain. For example:

LST EVCDSP: FN=5, SN=4, IDX=0;

b) Execute the command LST EVCECPARA to query EC network level attenuation. For example:

LST EVCEC: FN=5, SN=4, IDX=0;

c) Judge whether CDMA system satisfies the conditions listed in Table 2-4. If not, the echo results from the MS. Otherwise, ask the technical support engineers to locate the fault.

Table 2-4 Conditions for CDMA system not introducing acoustic echo gain

CDMA intra-office call CDMA outgoing and incoming call

EC configured at MSC

(Forward Level Gain + Reverse Level Gain)= 0 dB

(Forward Level Gain + Reverse Level Gain - Network Level Attenuation)= 0 dB

EC configured at BSC



Note:

EC Network Level Attenuation is expressed by +dB.


2-51

4) Clear the fault of the peer end.

Ask the maintenance engineers of the peer system to remove the fault or have the peer MS repaired.

5) Collect the information of the MSs, where echoes occur.

Collect the information such as the model of the MSs, echo probability, and the times of echo occurrences.

6) Optimize the network according to the information collected.

Based on the echo probability and MS model collected, determine whether adjustment and optimization are necessary or not.


Conduct dialing test using different types of MSs to check whether the fault is cleared. If echoes appear over an individual MS, just conduct dialing tests with the faulty MS.

2.4.2 Voice Loopback


After a call is connected, one party can hear his own voice only. Single pass or cross-talk may occur at the same time.

II. Troubleshooting

Voice loopback normally results from incorrect E1/T1 connection. Sometimes, for the purpose of test, loopback is manually set using software. If the loopback is not removed after the test, it may also lead to voice loopback.



2-52

Y

Fault of MSC side (1)

N

Y

Check whether loopback isset via AIE software (3)

Check E1/T1 connectionbetween MSC and BSC (2)

Correct setup?

End

Adjust E1/T1 connectionbetween MSC and BSC

N

Is fault removed?N

Modify AIE loopback data (4)


Y

N

Is voice loopback only found in outgoing

calls?

Voice loopback

Y

is the connectioncorrect?

Figure 2-18 Troubleshooting flowchart for voice loopback

Steps:

1) Check whether the voice loopback results from the fault at the MSC side.

If loopback only occurs to outgoing calls, the fault exists in the MSC. Ask MSC maintenance engineers to locate and remove the fault.

2) Check E1/T1 connection between the MSC and the BSC.

The E1/T1 connection causing voice loopback includes:

Externally-selflooped E1/T1 line. Improperly-connected E1/T1 lines between different equipment such as MSC,

BSC, and DDF. In this case, alarm may occur sometimes.


2-53

Check the E1/T1 connection between the cabinet and the DDF, and that between the DDF and the peer equipment.

3) Check whether loopback is set using AIE software.

Execute the command DSP E1T1STAT to show the status of E1/TI. For example:

DSP E1T1STAT: FN=5, SN=SLOT0, BTP=CAIE, LNKNO=0;

Check whether E1/T1 is in one of the following statuses: "Local Loopback", "Remote Loopback", "Payload Loopback", and "Single Loopback". If yes, alarm occurs in the Alarm Management System. Remove the fault according to the alarm information reported.

Note:

Currently, the loopbacks set using software in CDMA system includes: CAIE/CXIE E1/T1 link or E1/T1 single channel timeslot loopback set through the maintenance console TDM and HPI single channel timeslot loopback set through the debugging console CFMR single subscriber loopback set through the debugging console Single channel timeslot loopback set in MSC of certain version

Among the four types of loopbacks, the last three are valid in a single call only. As the system releases the call, the loopback disappears automatically. The CAIE/CXIE loopback is valid unless you remove it. After loopback is configured on the CXIE, the corresponding resources are unavailable. Therefore, the voice loopback cannot occur. In this case, check the CAIE loopback.

4) Modify CAIE loopback data.

Execute the command SET LPBACKE1T1 in the Service Maintenance System.

For example:

SET LPBACKE1T1: FN=5, SN=SLOT0, BTP=CAIE, LNKNO=0, OPT=NOLOOPBACK


Conduct dialing tests to check whether the fault is cleared.


2-54

2.4.3 Single Pass


One party in a call can hear the voice of the peer party, while the other can not. Cross-talk or loopback may occur at the same time.

II. Troubleshooting

Possible causes include:

E1/T1 link is incorrectly connected or loopback is set manually. See section 2.4.2 for troubleshooting.

Transmission failure occurs to the system.



2-55

Single pass

Is single pass found inoutgoing calls only?

N

Check MSC-BSC E1/T1connection (2)

Is the connection correct?

Locate fault through loopback(3)

Is it fault of MSC side?

N


End

Adjust MSC-BSC E1/T1connection

Is fault removed?

Remove fault of MSC side (1)Y

Y

N

N

Y

Y

Figure 2-19 Troubleshooting flowchart for single pass

Steps:

1) Remove the fault of MSC side.

If single pass is found in outgoing calls only, the MSC is faulty. Ask the MSC maintenance engineers to locate and remove the fault.


See section 2.4.2 for details.


2-56

3) Locate fault using loopback.

The purpose is to determine whether the fault exists at the BSS or the MSC.

a) Maintain the conversation and collect relevant resource information:

Execute the command DSP IMSI to query the resources seized by the call and calculate the AIE E1/T1 timeslot seized by each mobile subscriber.

b) Set AIE timeslot loopback corresponding to the MS.

Execute the command SET LPBKE1/T1 in the Service Maintenance System. For example:

SET LPBACKE1T1: FN=5, SN=SLOT0, BTP=CAIE, LNKNO=0, OPT=SINGLE, TSN=1

If the voice of one's own appears after the loopback, the BSC is normal. Locate fault at the MSC side.

Note:

To set signaling timeslot loopback or to modify E1/T1 loopback will result in call drops and affect the normal functions of the overall network.

c) Remove AIE timeslot loopback.


SET LPBACKE1T1: FN=5, SN=SLOT0, BTP=CAIE, LNKNO=0, OPT=NOLOOPBACK

If further confirmation is required, contact the MSC maintenance engineers to set loopback at the MSC.

Note:

The BSN queried with the command DSP IMSI is related to E1/T1 timeslot. You should calculate the E1/T1 timeslot of AIE seized by mobile subscriber as below: E1/T1 No. =

BSN/32 (take the integer), timeslot No.= BSN/32 (take the remainder). For example, if the BSN is 60, the call uses timeslot 28 of E1/T1 1.

Number E1s/T1s according to the following rules: The E1/T1 on CAIE 0 is from 0 to 63 from the bottom up. The E1/T1 on CAIE 15 is from 64 to 127 from the top down.

Timeslot here refers to the CAIE timeslot calculated based on the resource information queried.


Conduct dialing test to check whether the fault is cleared.


2-57

2.4.4 Cross-talk


For the two parties (A and B) involved in a call, A hears the voice of other people instead of B. Single pass or voice loopback may occur at the same time.

II. Troubleshooting


Cross talk

Is cross talk found in outgoingcalls only?

N

Check MSC-BSC E1/T1connection (2)


Locate fault through loopback(3)

is it fault of MSC side?

N


End

Adjust MSC-BSC E1/T1connection

Is fault removed?

Remove the fault at MSC side(1)

YY

N

N

Y

Y

Figure 2-20 Troubleshooting flowchart for cross-talk


2-58

Steps:

1) Remove the fault at the MSC side.

If cross-talk is found in outgoing calls only, the MSC is faulty. Ask the MSC maintenance engineers to locate and remove the fault.



3) Locate fault using loopback.

The purpose is to determine whether the fault exists at the BSS or the MSC.

a) Maintain the conversation and collect relevant resource information:

Execute the command DSP IMSI to query the resources occupied by the call and calculate the AIE E1/T1 timeslot seized by each mobile subscriber.

b) Set AIE timeslot loopback corresponding to the MS. If the call is originated between MSs, AIE timeslot loopback should be set for the two MSs respectively.

Execute the command SET LPBKE1/T1 to set AIE timeslot loopback. For example:

SET LPBKE1/T1: FN=5, SN=Slot0, E1/T1N=0, LOOPMODE=SINGLE, TS=1;

If cross-talk disappears, instead, the voice of one's own appears after the loopback, the BSS is normal. Locate the fault at the MSC side.

c) Remove AIE timeslot loopback:


SET LPBKE1/T1: FN=5, SN=Slot0, E1/T1N=0, LOOPMODE=NOLOOPBACK;

If further confirmation is required, contact the MSC maintenance engineers to set loopback at the MSC.

Note:

The BSN queried with the command DSP IMSI is related to E1/T1 timeslot. You should calculate the E1/T1 timeslot of AIE seized by mobile subscriber as below: E1/T1 No. =

BSN/32 (take the integer), timeslot No.= BSN/32 (take the remainder). For example, if BSN is 60, the call uses the timeslot No.28 of E1/T1 No.1.

Number E1s/T1s according to the following rules: The E1/T1 on CAIE No.0 is from 0 to 63 from the bottom up. The E1/T1 on CAIE No.15 is from 64 to 127 from the top down.

Timeslot here refers to the CAIE timeslot calculated based on the resource information queried.


2-59



Note:

The cross-talk results from incorrect E1/T1 connection or loopback manually set. See section 2.4.2 for troubleshooting.

2.4.5 Noise


During the conversation, one party hears intermittent or continuous noise.

II. Troubleshooting

See Figure 2-21 for troubleshooting procedure.


2-60

Is clock abnormal?N

Remove fault at MSCside (3)

Is it fault of MSC side?

Is it fault of MS?

Y

Y

N

Check whether the fault iscaused by MS (4)

Remove MS fault

Locate fault by loopback(2)

End

Y

Check whether clock isnormal (1)

Remove clock fault


Noise

N

Figure 2-21 Troubleshooting flowchart for noise

Steps:

1) Check whether the clock is normal.

In CDMA system, check the synchronization of the satellite signal receiver, BTS/BSC internal clock synchronization and BSC and MSC clock synchronization.

See Chapter 13, “BTS Management Fault” for details.

2) Locate fault by loopback.

The purpose is to determine whether the fault exists at the BSS or the MSC. The loopback mode is similar to that described in section 2.4.3


2-61


If the noise results from BSS fault, check line connection. If the noise results from MSC fault, locate and remove the fault at the MSC side.

3) Remove the fault at the MSC side.

Ask the MSC maintenance engineers to remove the fault.

Note:

When the MSC is connected with other offices, if the A law or u law codes on E1/T1 are not consistent, strong noises occur.

4) Check whether the MS is faulty.

Conduct dialing tests using different MSs and check whether fault only occurs to some specific MSs.

Contact the MS manufacturer if the MS is found faulty.



Note:

Possible causes of noise: Clock synchronization is not good. The line transmission is of poor quality or the transmission line is in poor contact. In the system related to the call processing, certain equipment is faulty or the performance is

degraded. The terminal is faulty. The radio quality is inferior or the radio interference is strong. The line coding modes are not consistent.

This section only describes the basic troubleshooting measures. Since the causes of noise are complicated, troubleshooting measures vary in actual conditions.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 3 Encrypted Speech Call Fault

3-1

Chapter 3 Encrypted Speech Call Fault

3.1 Encrypted Speech Call Failure


The mobile-originated calls (MOCs) and mobile-terminated calls (MTCs) requiring authentication only are successful. But if the MS sets the speech ciphering mode as enhanced speech encryption, all the MOCs and MTCs requiring authentication and encryption fail.

Trough the service maintenance system, you can trace the A1 interface signaling of the MOC and MTC procedures.

The signaling tracing result shows that the cause value of the Assignment Failure message is "equipment failure, 0x20".

II. Troubleshooting


Trace Abisinterface (1)

Receive BTS Long Code transition

response (2)

N

BTS Long Codetransition succeeds

(4)

Y

BTS fails (3)

Adjust thetimer(5)

Conductdialing test (6)

N

Y

End

Figure 3-1 Troubleshooting flowchart for encrypted speech call failure

Steps:


3-2

1) Trace Abis interface.

In the interface of service maintenance system, trace the Abis interface signaling for the MOC and MTC procedures.

2) Receive BTS Long Code transition response.

The BSC notifies the BTS of using private Long Code Mask through an Abis-Physical Transition Directive message. The BTS returns an Abis-Physical Transition Directive Ack to indicate whether the long code transition succeeds.

Check whether the BSC receives the Abis-Physical Transition Directive Ack sent by the BTS in the signaling flow obtained in step 1). If not, it indicates that fault occurs in the processing of the BTS or message transmission.

3) BTS fails.

Contact the BTS maintenance engineers for handling.

4) BTS Long Code transition succeeds.

Check the explanation of the Abis-Physical Transition Directive Ack in the signaling flow obtained in step 1).

If the "pMC Cause Value" is 0, it indicates that the BTS Long Code transition succeeds.

Otherwise, it indicates the BTS Long Code transition fails.

5) Adjust the duration of the timer.

In the service maintenance system, execute the command LST TMR to query and MOD TMR to modify the duration of timers 13 and 20.

Query the duration of timers 13 and 20 in the CCM of the BSC. LST TMR: MN=CCM, TMRID=13;

LST TMR: MN=CCM, TMRID=20;

Increase or decrease the duration of timers 13 and 20 simultaneously. The duration of timer 13 should be greater than that of timer 20.

If the BTS Long Code transition fails, it is recommended to increase the duration of timers 13 and 20 properly based on the query result.

For example, increase the duration of timer 13 from 2 s to 3 s, and that of timer 20 from 1 s to 2 s.

MOD TMR: MN=CCM, TMRID=13, TMRV=3000;

MOD TMR: MN=CCM, TMRID=20, TMRV=2000;


3-3


When the MS sets the speech ciphering mode to enhanced speech encryption, the MOCs and MTCs are successful. Thus the fault is cleared.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 4 Voice Service Negotiation Fault

4-1

Chapter 4 Voice Service Negotiation Fault

4.1 Voice Service Negotiation Failure


When the MS or the BSC initiates the voice service negotiation, the MS fails to originate the call and Assignment Failure is displayed in the output window of the Service Maintenance System.

II. Troubleshooting


Enable the voice servicenegotiation switch on the BSC.(2)

Change the DSP loading programtype of CEVC.(6)

Change the voice servicenegotiation policy of BSC. (4)

END

The voice servicenegotiation switch is enabled

on BSC.(1)

The voice service negotiationpolicy of BSC meets therequirement of MS.(3)

N

The DSP loading programtype of CEVC meets therequirement of MS.(5)

Y

N

N

Y

Conduct dialing test.(7)

Figure 4-1 Troubleshooting flowchart for voice service negotiation fault

Steps:

1) The voice service negotiation switch is enabled on the BSC.

Execute the following command in the Service Maintenance System:

LST SOFTPARA: SRVMN=CCM, PRMNO=7;


4-2

Result:

%%LST SOFTPARA: SRVMN=CCM, PRMNO=7;%%


Software Parameter

------------------

Service Module ID Software Parameter No. Software Parameter Value

CCM 7 0x00000002

(Total result = 1)

--- END

Note:

Software parameter 7 controls the voice service negotiation. The default value is 0x00000002, which is specified as below: 1) Bits 0 – 1: Controls the voice service negotiation 00: Not support EPACA function 01: Supports EPACA function 00: Not support voice service negotiation function 10: Support voice service negotiation function 2) Bits 2 – 31: Reserved.

2) Enable the voice service negotiation switch on the BSC.



If bits 0 – 1 of software parameter 7 are changed to 0x2, it indicates that the BSC supports the voice service negotiation. If bits 0 – 1 of software parameter 7 are changed to 0x0, it indicates that the BSC does not support the voice service negotiation.

3) The voice service negotiation policy of BSC meets the requirement of MS.


LST SRVNEGPARA:;


4-3

Result:

%%LST SRVNEGPARA:;%%


Service Negotiation Parameters

------------------------------

Service Negotiation Parameter

Rate set 2 SO negotiate to rate set1 SO

(Total result = 1)

--- END

4) Change the voice service negotiation policy of BSC.


MOD SRVNEGPARA: SRVNEGPARA=PARA0;

Note:

The service negotiation policy includes: Use SO Request by MS: Use the CODEC that the MS requires. Use SO Request by MS and 8K Must Negotiate to EVRC: Use the CODEC that the MS requires and

negotiate 8 k to EVRC. Rate Set 2 SO Negotiate to Rate Set 1 SO. Negotiation is EVRC-8k-13k. Negotiation is EVRC-13k-8k.

5) The DSP loading program type of CEVC meets the requirement of MS.

Generally, the DSP loading program type of CEVC supports 8k, EVRC, and 13k.

In the Service Maintenance System, execute the following command to query loading program types of the DSP chips of all CEVCs:

LST EVCDSP:;

Result:

%LST EVCDSP:;%%



4-4

CEVC DSP Parameter

------------

…… ……

DSP Loading Program Type = EVRC+QCELP8K

…… ……

V110 Switch = Off

--- END

6) Change the DSP loading program type of CEVC.

If the DSP loading program types of all CEVCs cannot meet the requirement, execute the following command in the Service Maintenance System to set specified CODEC:

MOD EVCDSP: FN=5, SN=3, DSPIDX=1, LODPRGMTP=QCELP8K+QCELP13K;;


Conduct dialing tests and observe whether the MS or BSC can perform the voice service negotiation.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 5 E911 Emergency Call Fault

5-1

Chapter 5 E911 Emergency Call Fault

5.1 E911 Emergency Call Failure


The MS fails to initiate an E911 emergency call in idle or connected status.

II. Troubleshooting


Check the status of E911emergency call switch .(1)

Emergency call switch is not enabled.

Check the A interface protocolversion of BSC and that of

MSC.(3)

Enable the switch of E911emergency call service on

BSC.(2)

The A interface protocolversion of BSC does not

match that of MSC.

Change A interface protocolversion of BSC.(4)

Y

N

Y

NMO message processing is

incorrect.(5)

Solve problems on MOmessage processing.(6)


End

Y

N

MSC fault

Figure 5-1 Troubleshooting flowchart for emergency call failure

Steps:

1) Check the status of E911 emergency call switch.



Result:



5-2


Software Parameter

------------------


CCM 28 0x00000000

(Total result = 1)

--- END

Note:

Software parameter 28 controls the E911 emergency call service. The default value is 0 x 00000000, which is specified as below:

Bits 0 – 1: Switch of emergency call service 00: Not support emergency call 01: Supports emergency call and is compatible with A interface 3GPP2.A.S0001-A 10: Supports emergency call and is compatible with A interface 3GPP2.A.S0001-A version2.0 Bits 2 – 31: Reserved.

2) Enable the switch of E911 emergency call service on the BSC.



If bits 0 – 1 of software parameter 28 is changed to 0x01, it indicates that the BSC supports E911 emergency call that is compatible with A interface 3GPP2.A.S0001-A.

If bits 0 – 1 of software parameter 28 is changed to 0x02, it indicates that the BSC supports E911 emergency call that is compatible with A interface 3GPP2.A.S0001-A version2.0.

Note:

The A interface protocol version of BSC must match that of MSC. When BSC supports emergency call.

3) Check the A interface protocol version of BSC and that of MSC.

For detailed operation on the MSC, contact MSC maintenance engineers.


5-3

4) Change the A interface protocol version of BSC.



Change bits 0 – 1 of software parameter 28 to support E911 emergency call service, and the A interface protocol version to the one matching that of the MSC.

5) MO message processing is incorrect.

The processing of the emergency call initiated by a MS in idle status is the same as that of an ordinary call.

For the faults occur when the control parameter of E911 emergency call is correct, see 2.2, “MOC Failure”.

6) Solve problems on MO message processing.

See “2.2 MOC Failure”.


Initiate an E911 emergency call when the MS is in idle and conversation statuses respectively, and then observe whether the call succeeds.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 6 Registration Fault

6-1

Chapter 6 Registration Fault

6.1 MS Failed to Initiate Registration


MS fails to initiate time-based registration or fails to initiate registration when: It is powered up.

It is powered down. It performs an idle handoff to a new location area. It roams to other areas.

You can trace no registration message through the service maintenance system.

II. Troubleshooting



6-2

Query neighboring cellsparameters (2)

Is the registration-relatedparameter message

properly set?

Y

Modify system parametermessage (3)

Query cell parameters (4)


End

Y

Query system parametermessage (1)

Query MS registrationparameters (5)

Are the MS registrationparameters properly set?

N

Modify MS registrationparameters (6)

N

Figure 6-1 Troubleshooting flowchart for MS failure to initiate registration

Steps:

1) Query system parameter messages.

Execute the command LST SYSMSGPARA in the service maintenance system.





------------------------

Cell ID = 20


6-3

Sector ID = 0

Carrier ID = 0










SID Roaming Registration Flag = Automatic

registration is required for MSs roaming from other SID

NID Roaming Registration Flag = Automatic

registration is required for MSs roaming from other NID

Switch-on Registration Flag = Registered

Switch-off Registration Flag = Registered





BS Latitude = North Latitude0h

ours0minutes0seconds

BS Longitude = East Longitude0h


(Total result = 1)

--- END


6-4

Note:

Check whether the system parameter messages are correct, especially the following fields: Local Registration Flag: If you do not set it to "Automatic registration is required for local MSs

(non-roaming MSs)", all the local MSs (that is, the MSs sharing the same home SID/NID with the local network) initiate no registration automatically.

SID Roaming Registration Flag: If you do not set it to "Automatic registration is required for MSs roaming from other SID", all the MSs roaming from other SIDs (that is, the MSs sharing different SIDs with the local network) initiate no registration automatically.

NID Roaming Registration Flag: If you do not set to "Automatic registration is required for MSs roaming from other NID", all the MSs roaming from other NIDs initiate no registration automatically. Note that this setup is invalid to the MS roaming from the area with the NID 65535, which matches all the other NIDs.

Power-up Registration Flag: It specifies whether registration is required upon the MS power-up. You should set it to "Registered' in an operating network.

Power-down Registration Flag: It specifies whether registration is required upon the MS power-down. You should set it to "Registered' in an operating network.

System Message Parameter Change Registration Flag: It specifies whether registration is required after the system parameters are modified. You should set it to "Registered" in a commercialized network.

Time Registration: If you set it to "0", the system initiates no time-based registration. Registration Zone: Zone for registration. It should be the same as the LAC in an operating network. Reserved Registration Zones: If you set it to "0", the system performs no zone-based registration.

2) Query cell parameters configured.

Execute the command LST CELL to query cell parameters related with registration.

For example:

LST CELL: CN=20, SCTID=0;

If registration is required when the MS performs idle handoff from other cells to local cell, the following parameters should be compared: System ID (SID), Network ID (NID), and Registration Zone. The registration zone may/may not be the same as the local area code.

When the system parameter message is correct, if one or several parameters are different among the system IDs, network IDs, or Registration Zones of two neighboring cells, registration will be initiated automatically after the MS performs an idle handoff.

3) Modify system parameter messages.

Execute the command MOD SPM in the service maintenance system. For example:


6-5

MOD SPM: CN=20, SCTID=0, CRRID=0, REGZN=3, TOTALZN=1, HOMEREG=YES,

FORSIDREG=YES, FORNIDREG=YES, PWRUP=YES, PWRDWN=YES, PRMREG=YES,

REGPRD=67;

If registration is required when the MS moves from other cells to the local cell, you can modify the Registration Zone.

4) Modify cell parameters.

Execute the command MOD CELL in the service maintenance system. For example:

MOD CELL: CN=20, SCTID=0, SID=12062, NID=6, LAC=" 0X3";

If registration is required when the MS moves from other cells to the local cell, you can modify cell parameters, that is, to make the parameters of other cells different from those of the local cell.

5) Query MS registration parameters configured.

You may query the MS registration parameters for analysis when a few MSs cannot initiate registration normally.

For some MSs, you can set the registration parameters to control the initiation of registration. Contact the MS manufacturer for specific methods.

6) Modify MS registration parameters.

You may modify MS registration parameters when a few MSs cannot initiate registration.

For some MSs, you can set the registration parameters to control the initiation of registration. If registration cannot be initiated owing to incorrect MS setting, you should modify the parameters related to registration. Contact the MS manufacturer for specific methods.


Conduct dialing tests using the MS and observe:

The time-based registration performed The registration performed when the MS is powered up, powered down, and

handed off to new location areas and roams to other area

If the registration of the MS is successful, the fault is cleared.


6-6

6.2 MS Registration Failed


The MSC rejects the power-up registration initiated by the MS.

II. Troubleshooting


Check BSC and MSC dataconfiguration (1)

Is the data configurationcorrect?

Y

Modify BSC and MSC dataconfiguration (2)


END

N

Check subscriber informationdefined in HLR (3)

Is the subscriber datacorrect?

Modify subscriber datadefined in HLR (4)

N

N

Check authentication (5)

Is the authenticationnormal?

Remove authenticationfault (6)

NSS fault

Y

Y

Figure 6-2 Troubleshooting flowchart for MS registration failure

Steps:

1) Query BSC and MSC data configuration.

Check whether the cell configuration of the BSC (where the MS that fails in the registration resides) and that of the corresponding MSC are consistent. If they are


6-7

inconsistent, the cell ID reported by the BSC cannot be found in the MSC. Therefore, the MSC will reject the location update message reported by the BSC.

a) Execute the command LST CELL to query the cell configuration of BSC.

For example:

LST CELL: CN=20, SCTID=0;

b) Query the cell configuration of MSC, compare it with the above query results and contact the MSC maintenance engineers to handle the problem.

2) Modify BSC and MSC data configuration.

Modify BSC and MSC data configuration to make the cell data consistent.

See section 2.3.2, “BSC Not Received Paging Response” for details.

3) Check whether the MS is correctly defined in the HLR.

If the MS is not defined in the HLR correctly, the MSC will reject the location update message reported by the BSC and result in a registration failure.

Contact the MSC maintenance engineers for handling.

4) Modify subscriber information defined in the HLR.

Contact the MSC maintenance engineers for handling.

5) Check whether the authentication is normal.

Authentication failure will also result in registration failure.

See Chapter 7, "Authentication Fault" for details.

6) Clear the fault occurred in authentication.

See Chapter 7, “Authentication Fault” for details.


Conduct dialing tests and observe whether the MS can perform the registrations such as power-up registration and power-down registration.


6-8

6.3 Mass Registration Messages Received


Under some circumstances, especially after system upgrade or expansion, the system may receive a large number of registration messages.

II. Troubleshooting


Check whether systemparameters are modified (1)

Have the system parametersbeen modified?

N

Modify system parameters inbatches (2)


End

N

Check registration period (3)

Is the registration periodproperly set?

Modify registration period (4)

Y

Y

Figure 6-3 Troubleshooting flowchart for system receiving lots of registration messages

Steps:

1) Check whether system parameters are modified.

If some network parameters, such as System ID, Network ID, and Registration Zone, are modified, the MS will report registration messages.

If you modify a large number of network parameters at the same time (for example, modify the network parameters of dozens of or even hundreds of carriers at the same


6-9

time), a large quantity of MSs will report registration messages simultaneously in a short period and result in impact to the network.

2) Modify system parameters in batches.

If modifying a large number of cell parameters, especially the parameters related to registration (such as System ID, Network ID, and Registration Zone) in cut-over, system upgrade, system expansion or daily operation and maintenance, you should carry out the modification in batches.

Alternatively, you can block each carrier first, and then modify the parameters one by one. After modifying all the parameters, unblock the carriers one by one.

3) Check whether the "Time Registration" is set properly.

If you set the "Time Registration" too short, the system may initiates too many registrations.

Execute the command LST SYSMSGPARA to query the parameter.




System Parameter Messages

------------------------

Cell ID = 20

Sector ID = 0

Carrier ID = 0








Local Registration Flag = Automatic regist

ration is required for local MSs (non-roaming MSs)

SID Roaming Registration Flag = Automatic regist

ration is required for MSs roaming from other SID

NID Roaming Registration Flag = Automatic regist

ration is required for MSs roaming from other NID


6-10

Switch-on Registration Flag = Registered

Switch-off Registration Flag = Registered


Time Registration = 43.691 Minutes



BS Latitude = North Latitude0h


BS Longitude = East Longitude0h


(Total result = 1)

--- END

4) Modify the "Registration Period".

Execute the command MOD SPM in the service maintenance system. For example:

MOD SPM: CN=20, SCTID=0, CRRID=0, REGPRD=60;

The meaning of the "Registration Period" is as below:

(2Registration period/4) % 0.08 second.

Suppose the registration period is 60 (as shown in the above example), the MS will initiate a time registration every other 43.691 minutes.


Observe whether the number of registrations can be controlled within a specified range and the system operation is not affected.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 7 Authentication Fault

7-1

Chapter 7 Authentication Fault

7.1 MS Global Challenge Failed


Symptom 1

After the MS initiates registration, the BSS sends a Location Update Request to the MSC. The MSC returns a Location Update Reject message, rejecting the registration of the MS.

Symptom 2

In a mobile-originated call (MOC), after receiving a CM Service message from the BSS, the MSC returns a Clear Command with the cause value of 0X1A or the N_DISCONNECT_IND to release the call.

Symptom 3

In a mobile-terminated call (MTC), after receiving a Paging Response from the BSS, the MSC returns a Clear Command with the cause value of 0X1A or the N_DISCONNECT_IND to release the call.

II. Troubleshooting



7-2

MS global challenge failed

Specific MS or all MSs failed?All MSs

Y

BSC data configuration error

Is the authentication functionenabled at BSC? (1)

Enable the authenticationfunction at BSC (2)

Y

Query A_Key set on the MSand the HLR (3)

Are the A_Keys of the MS andthe HLR consistent?

MS not support R-UIM:A_Key set incorrectly

Modify the A_Key of MS orMSC (4) Replace R-UIM (5)

Is the authenticationsuccessful?

Initiate SSDupdate from MSC (8)

Is the SSD update procedurecorrect (9)?

Replace R-UIM

Is the authenticationinformation carried by the

registration or the originationmessage? (7)

Y

Enable A1 interface tracing atBSC (6)


End

MS not support authentication;remove authentication (10)

Specific MS

N

N

Y N

N

N

Y

Figure 7-1 Troubleshooting flowchart for MS global challenge failure


7-3

Steps:

1) Query authentication configuration at the BSC side.

Execute the command LST SYSMSGPARA in the service maintenance system.


Result %%LST SYSMSGPARA: CN=20, SCTID=0, CRRID=0, CCMINF=AUTH;%%



--------------------------

Cell ID Sector ID Carrier ID Authentication Flag Auth Random Check Value

20 0 0 Not Authenticate 100.00

(Total result = 1)

--- END

The "Authentication Flag" is set as "Not Authenticate", which means authentication is disabled at the BSC.

2) Enable the authentication at the BSC side.

Execute the command MOD AUTH in the service maintenance system.

Example MOD AUTH: CN=20, SCTID=0, CRRID=0, AUTH=YES, RAND=100;

Result %%MOD AUTH: CN=20, SCTID=0, CRRID=0, AUTH=YES, RAND=100;%%


Sending result for every CPU

----------------------------

Frame Card Type Result

4 CSPU Setting data has been sent to host

--- END

To enable the authentication at the BSC, set "AUTH" to "Yes".

3) Query the A-Key set on the HLR and the MS.

You can query the A-Key of MS by entering the super password.

To query the A-Key of the HLR corresponding to the MS at the HLR side, contact the HLR maintenance engineers.


7-4

4) Modify the A-Key on the MS or the HLR.

To modify the A-Key of MS, enter the super password and then change the value into that of MSC.

To modify the A-Key of the HLR serving the MS, ask the HLR maintenance engineers for help.

5) Replace R_UIM.

Insert the R_UIM of the MS which failed in the authentication to the MS that passed authentication. If authentication still fails, the R_UIM is faulty. Replace the R_UIM.

6) Activate Um interface tracing at the BSC.

In the service maintenance system, click [Maintenance/Trace/Um Interface Message Tracing] to view the registration messages, origination messages, or paging response messages reported to the BSC by the MS through the Um interface.

7) Check whether authentication information is carried in the registration messages, origination messages, or paging response messages.

Check the registration messages, origination messages, and page response messages traced over the Um interface and see whether these messages contain the authentication field. If no authentication information is found, the MS does not support authentication function.

8) Initiate shared secret data (SSD) update at the MSC.

Delete from the HLR the information of the subscriber who always fails in global challenge, and re-define the subscriber. For the detailed operations, contact the HLR maintenance engineers.

Initiate the SSD update at the MSC (contact the MSC maintenance engineers for help).

9) Check whether the SSD update procedure is correct.

If the SSD update is successful, the MSC will automatically trigger a unique challenge procedure, and the SSDs at both the network side and the MS side used for authentication will be consistent. Thus, authentication failure caused by the SSD inconsistency is removed.


7-5

10) If the MS does not support the authentication function, disable the authentication at the MSC.

If the MS does not support the authentication function, the authentication of the MS is disabled at the HLR. For the detailed operation, contact the HLR maintenance engineers.


If the MS can perform the registration, the MOC, or the paging services, the fault is cleared.

7.2 MS Unique Challenge Failed


Symptom 1

In the service maintenance system, click [Maintenance/Trace/A1 Interface Message Tracing] to view the messages traced at A1 interface and Um interface, you will find that:

1) The MSC sends the Authentication Request message to the BSC. 2) After returning an Authentication Response to the MSC, the BSC receives a Clear

Command from the MSC. Symptom 2

In the service maintenance system, click [Maintenance/Trace/Um Interface Message Tracing] to view the messages traced at Um interface, you will find that: After sending an Authentication Challenge message to the MS, the BSC receives no Authentication Challenge Response from the MS.

II. Troubleshooting



7-6

Check A_Key data of MSCand MS (1)

Modify A_Key data at HLR (2)

Modify A_Key data of MS (3)

Disable authentication of MS(5) Conduct dialing test (6)

End

Y

Y

N

N

N

MS unique challenge failed

Y Does the MS supportunique challenge?

(4)

Is the A_Key at MSmodified?

Is the A-Key at HLRproperly set?

Figure 7-2 Troubleshooting flowchart for MS unique challenge failure

Steps:

1) Check whether the A-Key of HLR and that of MS are consistent.

a) Query the A-Key of the MS saved on the HLR. Contact the HLR maintenance engineers for help.

b) Query A-Key of MS: Enter the super password on the MS and query the value.

c) Check whether the A-Key of MS and that saved on the HLR are consistent.

2) Modify the A-Key data saved on the HLR.

If the A-Key is not configured correctly at the HLR side, contact the HLR maintenance engineers to modify it.

3) Modify the A-Key data of the MS.


7-7

If the modification of the A-Key on the MS causes the inconsistency of A-Key, modify the A-Key on MS again.

To modify the A-Key of MS, enter the super password and then modify the value to be consistent with that saved on the HLR.

4) Check whether the MS supports unique challenge.

In the service maintenance system, click [Maintenance/Trace/A1 Interface Message Tracing] to view the A1 interface signaling traced. If the BSC receives no Authentication Challenge Response after sending an Authentication Challenge message to the MS, the MS does not support unique challenge.

5) Disable authentication for the MS at the HLR.

For the detailed operation, contact the HLR maintenance engineers.


If the failure results from the inconsistency of A-Key data, proceed as below:

a) Delete the subscriber data from the HLR and then re-define it.

b) Initiate an SSD update procedure at the MSC (the SSD update procedure will automatically trigger a unique challenge procedure).

c) In the service maintenance system, click [Maintenance/Trace/A1 Interface Message Tracing] to view the signaling messages traced at A1 interface.

If the BSC receives no Clear Command after sending an Authentication Response to the MSC, the fault is removed.

It is unnecessary to conduct dialing tests if the MS does not support unique challenge.

Note:

Possible causes to unique challenge failure include: The A-Key entered when the MS registers in the HLR is inconsistent with that saved in the MS. When

defined in the HLR, the subscriber must enter the A-Key data of the MS. If the entered A-Key data is incorrect, the A-Key data saved in HLR will be inconsistent with that saved in the MS. As a result, the SSD_A_NEW generated based on the SSD, and the AUTHU then calculated at the MS and that at the network side will be inconsistent, causing unique challenge failure.

The modification of A-Key data saved in MS causes A-Key data inconsistency. The A-Key data saved in the MS can be modified and edited. So, if it is modified, A-Key data inconsistency will be caused, resulting in unique challenge failure.


7-8

7.3 MS SSD Update Failed


Symptom 1

The messages traced at Um interface shows that the BSC sends a Base Station Challenge Confirmation Order message to the MS, while the MS returns an SSD Update Rejection Order message.

Symptom 2

The messages traced at A1 interface shows that the BSC sends an SSD Update Response with a cause value of "0x3B (SSD update rejected)" to the MSC.

II. Troubleshooting


Query A_Key data sav edat MSC

Is the A_Key correct?Modify A_Key data sav edat MSC (1)

Query A_Key data sav edin MS

Modify A_Key data sav ed inMS (2)


End

MS does not support theSSD update

N

Y

Y

N

MS SSD update failed

Is the A_Key of MS consistent w ith the one

sav ed at MSC?

Figure 7-3 Troubleshooting flowchart for MS SSD update failure


7-9

Steps:

1) Modify the A-Key saved at the MSC side.

Query the A-Key saved at the MSC side and modify it if necessary (for the detailed operation, contact the MSC mainetnance engineers).

2) Modify the A-Key saved in the MS.

Query the A-Key data saved in the MS using super password and modify it if necessary.


Initiate an SSD update procedure at the MSC and observe whether SSD update can be performed successfully.

If the SSD update of this MS is successful, the fault is cleared.

Note:

When defined in HLR, the subscriber must enter the A-Key data of the MS. If the entered A-Key data is incorrect, the A-Key data saved in the HLR/AC will be inconsistent with that saved in the MS. As a result, the SSD_A_NEW generated based on the SSD and the SSD_B_NEW calculated at both sides are inconsistent, causing SSD update failure. In addition, the A-Key data saved in the MS can be edited or modified. If it is modified, A-Key data inconsistency between the MS and the HLR/AC will be caused, resulting in SSD update failure.

7.4 Authentication Not Initiated


The authentication of the MS is required, but the system implements no authentication.

Symptom 1

Illegal MSs originate calls successfully.

Symptom 2

Illegal MSs are paged successfully.

Symptom 3

No relevant SSD update is implemented when a legal subscriber registers and originates calls for the first time.


7-10

II. Troubleshooting

The fault usually results from the setting of Authentication Flag, which is set to "Not Authenticate".



7-11

Query authentication flag atBSC (1)

Is the authenticationfunction enabled?

Query Authentication Flagset as MSC (2)


Query Authentication Flagset at HLR (3)

Query Authentication Flag forspecific MS in HLR (4)

Set the Authentication Flagto "Authenticate"


End




Other problems

N

Y

N

Y

N

Y

Y

N

Authentication on MS notperformed


Is the authenticationenabled?

Figure 7-4 Troubleshooting flowchart for authentication not initiated

Steps:

1) Query the Authentication Flag set at the BSC side.


7-12

Execute the command LST SYSMSGPARA to check whether "Authentication Flag" is set to "Authenticate".


Result: %%LST SYSMSGPARA: CN=20, SCTID=0, CRRID=0, CCMINF=AUTH;%%



--------------------------

Cell ID Sector ID Carrier ID Authentication Flag Auth Random Check

Value

20 0 0 Not Authenticate 100.00

(Total result = 1)

--- END

If the Authentication Flag is set to "Not Authenticate" (as shown in the above result), modify it using the command MOD AUTH.

Example MOD AUTH: CN=20, SCTID=0, CRRID=0, AUTH=YES, RAND=100;

Result %%MOD AUTH: CN=20, SCTID=0, CRRID=0, AUTH=YES, RAND=100;%%


Sending result for every CPU

----------------------------

Frame Card Type Result

4 CSPU Setting data has been sent to host

--- END

2) Query the Authentication Flag set at the MSC side.

In MAP Configuration Data table, the field "Authenticate or not" defines whether authentication is to be implemented on the MSs in the coverage of MSC. Enable the authentication if necessary.

For the detailed operation, contact the MSC maintenance engineers.

3) Query the Authentication Flag set at the HLR.

The "authentication" in the dialog box [Define a subscriber] specifies whether the authentication is required for the MS.

4) Query the Authentication Flag configured for a specific MS in the HLR.


7-13

The BSC and the MSC specify whether authentication is to be implemented on the MSs moving in each system, while the HLR specifies whether authentication is to be implemented on a specific MS.

If the authentication for a specific MS is required, while the Authentication Flag is set to "Not authenticate" in the HLR, the system will implement no authentication on that MS.

For the detailed operation, contact the MSC maintenance engineers.


Make MOCs and MTCs using an illegal MS. If the calls fail, the fault is removed.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 8 Short Message Fault

8-1

Chapter 8 Short Message Fault

8.1 MS Failed to Receive Short Message


The MS cannot receive short message normally.

II. Troubleshooting


END

Does error occur to theprocessing of paging

messages?

Check whether any faultoccurs to the processing of

paging messages (1)

Conduct a dialing test (3)

END

Remove the error of pagingmessage processing (2)

N

Short message authority inHLR or fault of MSC/ACD

Y

Figure 8-1 Troubleshooting flowchart for MS failure of receiving short message

Steps:

1) Check whether any fault occurs to the processing of paging messages.

Although forward short messages can be transferred in many ways, they are generally carried by paging messages.

2) Remove the fault of paging message processing.

Refer to section 2.3, "MTC failure" for details.


8-2

3) Conduct a dialing test.

Send short messages of various lengths from the message center (MC) or other MSs, and observe whether the MS can receive the short messages normally.

Caution:

The implementation of short message service is closely related to the subscriber authority defined in the HLR, and the processing of the MSC and MC. It is recommended to trace the messages during troubleshooting procedure.

The MS is essential to the implementation of short message service. In band 450 MHz CDMA system, some H100 MSs and S200 MSs cannot display calling numbers.

8.2 Centralized Sending of Short Messages Resulted in System Abnormality


During the centralized sending of short messages, if the sending speed is not well controlled, the CPU of the CSPU will be overloaded, causing abnormality of part of the system.

II. Troubleshooting



8-3

Does the centralizedsending of short messages

cause the exception?

Check the sending mode ofshort messages (1)

Conduct a dialing test (3)

END

Stop the sending or decreasethe sending speed (2)

Y

N

Figure 8-2 Troubleshooting flowchart for system abnormality due to centralized sending of short messages

Steps:

1) Check the sending mode of short messages.

You should check the following information:

Sending speed of short messages in the MC Times that a short message is resent at the MC Times that a short message is resent at the MSC BSC networking scale and the number of BTSs under each module Current traffic

2) Stop the centralized sending of short messages or decrease the sending speed.

a) Stop the point-to-point short message sending when you observe the following cases:

Too heavy traffic at A-interface (over 20 short message pagings each second) Too high CPU occupancy (more than 70%) of CSPU in the BSC Other alarms

b) Adjust the parameters.

Reduce the number of short messages sent each second. Control the sending speed and the number of messages resent. Disable the resending of short message at the MC.


8-4

Set the times of short message resending at the MSC to "2" and the resending interval to "5 seconds".

If the number of BTSs in a location area under the module is less than or equal to 16, the recommended number of short messages sent each second should be less than 5.

If the number of BTSs is more than 16 and less than or equal to 32, the recommended number of short messages sent each second should be less than 4.

If the number of BTSs is more than 32, the recommended number of short messages sent each second should be less than 3.

3) Conduct a dialing test.

Conduct a dialing test and observe the traffic at the CPU occupancy of CSPU and A-interface.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 9 Service Redirection Fault

9-1

Chapter 9 Service Redirection Fault

9.1 Service Redirection Failed


Symptom 1

It is expected that, through service redirection function, the IS-95 MSs register to IS-95 cell and IS2000 MSs register to IS2000 cell. In actual circumstance, IS-95 MSs register to IS2000 cell, and IS2000 MSs register to IS-95 cell, or the MS registration fails.

Symptom 2

It is expected that, through service redirection function, the IS-95 MSs establish calls in the IS-95 cell and IS2000 MSs establish calls in the IS2000 cell. In actual circumstance, IS-95 MSs establish calls in the IS2000 cell and IS2000 MSs establish calls in the IS-95 cell.

Symptom 3

When one cell or multiple cells are overloaded and the newly accessed MSs are expected to be redirected to the cell with a lighter load, the redirection fails, and the MSs still register to the cell with a heavy load.

Symptom 4

When one cell or multiple cells are overloaded and the new calls are expected to be redirected to the cell with a lighter load, the redirection fails, and MSs still establish calls in the cell with a heavy load.

II. Troubleshooting

See Figure 9-1 for the troubleshooting procedures:


9-2

The MS doesn't supportserv ice redirection.

Single MS

It may result from BSCside data configuration

Is the sub-redirectionmessage sent? (1)

Query current carrierconfiguration ty pe (2)

All MSs

Decode redirectionmessage

YN

Query serv ice redirectiondata configuration (6)

MS doesn't supportredirection function

YN

Modify N2D, S2D, band and frequencyas the corresponding parameters in

target sy stem

Conduct dialing test(7)

End

Y

Configure carrier as 95/2000 independent cell (3)

95/2000 combined cell

95/2000 independent cell

Y

N

N

Are the N2D/S2D band andfrequency configured as target

sy stem parameters?

Are the N2D/S2D band and frequency configured as the

target sy stem parameters? (5)

Is the redirection sw itch set to ON? (4)

Serv ice redirection failed

Set redirection sw itchto be ON

Does theredirection of single MS or

all MSs fail?

Figure 9-1 Troubleshooting flowchart for service redirection failure

Steps:

1) Confirm that the service redirection message has been sent.

In the service maintenance system, click [Maintenance/Trace/Um Interface Message Tracing] to trace whether the BSC has sent the service redirection message (SRDM) to MSs.

2) Check the type of the current carrier.

Execute the command LST RRMINF to check the type of current serving carrier.


9-3

Example LST RRMINF: CN=20, SCTID=0, CRRID=0, RRMINF=SRCFG;

Result %%LST RRMINF: CN=20, SCTID=0, CRRID=0, RRMINF=SRCFG;%%


Service Redirection Information

-------------------------------

Cell ID = 20

Sector ID = 0

Carrier ID = 0

Pilot Type = IS95A/IS95B/IS2000

Combined Cell

Allow Service Redirection based on Current Cell Type = Not Allowed

Redirection on Congestion Switch = Disabled

Redirection on Illegal MS Switch = Disabled

Service Redirection Function Switch 2 = Disabled

Service Redirection Function Switch 3 = Disabled

System ID = 0

Network ID = 0

Band Class = 800MHz

Frequency 1 for Service Redirection = None






(Total result = 1)

--- END

The content after "Pilot Type" is the current "Pilot Type" configured for the carrier. For the specific meaning of each carrier, see the description in Table 9-1.

3) Configure the carrier as IS-95 or IS2000 independent cell.

Judge whether the carrier configuration is correct according to the carrier type queried in step 2. If the carrier type is not required, you can configure the carriers according to the on-site requirements.

For the specific parameter configuration, see Table 9-1.

For example, if you want to modify the carrier (pilot) type with the parameters of cell ID "20", sector ID "0" and carrier ID "0" as IS2000 cell, execute the command:

MOD SRCFG: CN=20, SCTID=0, CRRID=0, PLTTP=IS2000;


9-4

4) Check whether the service redirection switch is On.

Execute the command LST RRMINF to check the setting of service redirection switch.

Example LST RRMINF: CN=20, SCTID=0, CRRID=0, RRMINF=SRCFG;

Result %%LST RRMINF: CN=20, SCTID=0, CRRID=0, RRMINF=SRCFG;%%


The service redirection switches include "Allow Service Redirection based on Current Cell Type", "Redirection on Congestion Switch" and "Redirection on Illegal MS Switch". For the redirection types and meaning of each switch, see Table 9-1.

If the service redirection switch is Off, you can execute the command MOD SRCFG to enable the switch. For example:

MOD SRCFG: CN=20, SCTID=0, CRRID=0, IFCELLTP=YES, SRLODSWT=ON, SRSWT1=ON;

5) Check whether [System ID], [Network ID], [Band Class] and [Frequency] in the message are the parameters for the target system.

If the parameters in the message are inconsistent with those configured in the target system, errors may exist in the data configuration for service redirection.

6) Query the data configuration for service redirection

[System ID], [Network ID], [Band Class] and [Frequency] in the data script should be consistent with those in the target system to which the MS is redirected. Otherwise, the MS will fail to find the target system.

If inconsistency exists, execute the following command to modify the configuration:

MOD SRCFG: CN=20, SCTID=0, CRRID=0, SRSID=4, SRNID=1, BNDCLS=BC800,

SRFRQ1=78, SRFRQ2=160, SRFRQ3=252, SRFRQ4=242, SRFRQ5=283, SRFRQ6=184;

Note:

The service redirection parameters such as [System ID], [Network ID], [Band Class] and [Frequency] in database (DB) should be configured as the same as those of the system that the MS is redirected to.


9-5

Table 9-1 Service redirection configuration

Attribute Range Data type Attribute description Index flag

PILOT_TYPE 0 – 7 DBT_UINT8,*

The current carrier types: TYP0—S95A/95B cell; TYP1—IS2000 cell; TYP2—IS95A/IS2000 combined cell; TYP3—IS95A/IS95B/IS2000 combined cell. The judgment is subject to the actual situation. If TYP3 is configured, this means to disable the redirection function between different cells.

TYP0: redirecting 2000MS TYP1: redirecting 95A/B MS TYP2: redirecting 95B MSTYP3: Not perform redirection between different cells

SR_CELLTYPE_SWITCH 8 bits DBT_UINT8,*

Allow Service Redirection based on Current Cell Type: NO=Not Allowed; YES =Allowed.

SR_LOAD_ SWITCH 8 bits DBT_UINT8,* Redirection on Congestion Switch:

NO=Disabled; YES=Enabled

SR_SWITCH1 8 bits DBT_UINT8,* Redirection on Illegal MS Switch: YES=Enabled; NO=Disabled

SR_SWITCH2 8 bits DBT_UINT8,* Service Redirection Function Switch 2

For function extension in the future

SR_SWITCH3 8 bits DBT_UINT8,* Service Redirection Function Switch 3

For function extension in the future

SR_SID 15 bit DBT_UINT16,* System ID The configuration depends upon the target cells.

SR_NID 16 bit DBT_UINT16,* Network ID The configuration depends upon the target cells.

BAND_CLASS 5 bits DBT_UINT8,* Band Class=[00000] (Cellular)=[00001] (PCS)

The configuration depends upon the target cells.

SR_FREQ1 INTEGER (0..2047) DBT_UINT16,* Frequency 1 for service redirection Target frequency 1







9-6

Note:

Every record represents the service redirection configuration allowed by the current carrier. Up to six redirection frequencies can be configured for each record, and the frequency not configured

is 0xffff (the configuration is subject to the sequence). The current carrier types indicate the directions and selection of the redirection. If the current cell is

IS-95, the system will instruct IS2000 MS to redirect the service; if the current cell is IS2000, the system will instruct IS-95 MS to redirect the service.

The maximum number of records in Service Redirection Configuration table is 960.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 10 Handoff Fault

10-1

Chapter 10 Handoff Fault

10.1 MS Failed to Trigger Hard Handoff


The MS fails to trigger hard handoff in the border areas, resulting in an increased FER and call drops.

II. Troubleshooting


END

Check the related hard handoffalgorithm is enabled (2)

Check BTS cov erage in hardhandoff area (1)

Check hard handoff decisionthreshold (3)


Figure 10-1 Troubleshooting flowchart for incorrect configuration of hard handoff algorithm

Steps:

1) Check BTS coverage in the hard handoff area.

a) Check BTS coverage in the hard handoff area, such as signal receiving and transmitting and engineering parameters of BTS (including downtilt, azimuth, and height of the antenna).

b) Check the service maintenance system for alarms.

2) Check that the related hard handoff algorithm is enabled.

Execute the command LST RRMINF to check the status of hard handoff algorithm.The query command varies with the hard handoff algorithm. See Table 10-1 for details.


10-2

Example LST RRMINF: CN=20, SCTID=0, CRRID=0, RRMINF=PHOALG;

Result %%LST RRMINF: CN=20, SCTID=0, CRRID=0, RRMINF=PHOALG;%%


Handoff Algorithm Switch Parameter

----------------------------------

Cell ID = 20

Sector ID = 0

Carrier ID = 0

Co-frequency HHO Switch = On

Handdown HHO Switch = Off

Direct HHO Switch = Off

(Total result = 1)

--- END

Note:

The following table shows the configurations of hard handoff algorithms:

Table 10-1 Configurations of hard handoff algorithms

Algorithm Meaning Query command

Modification command Default value

Co-frequency hard handoff algorithm

1: Enable 0: Disable

LST RRMINF MOD PHOALG 1

Pseudo pilot hard handoff algorithm


LST BSCHO MOD BSCHO 1

Mobile assisted hard handoff algorithm


LST BSCHO MOD BSCHO 1

HANDDOWN hard handoff algorithm



RTD (direct) hard handoff algorithm



When enabling a specific hard handoff algorithm, you should disable the others.

3) Check hard handoff decision threshold.


10-3

Execute the command LST RRMINF to check the hard handoff decision threshold:

Example LST RRMINF: CN=20, SCTID=0, CRRID=0, RRMINF=SAMEFREQ;

Result %%LST RRMINF: CN=20, SCTID=0, CRRID=0, RRMINF=SAMEFREQ;%%


Co-frequency HHO Parameter

--------------------------

Cell ID = 20

Sector ID = 0

Carrier ID = 0

Co-frequency HHO T_ADD = 28

Co-frequency HHO Absolute Threshold = 24

Co-frequency HHO Relative Threshold = 8

(Total result = 1)

--- END


10-4

Note:

The above command is used to query the threshold of co-frequency hard handoff. You may select the related command for the algorithm to be queried.

Table 10-2 shows the basic configuration of hard handoff algorithms. You can modify a threshold using the corresponding command.

Table 10-2 Configuration of hard handoff threshold

Field Modification command

Meaning of command

Recommended value

Ec/Io absolute threshold of RTD hard handoff 24

RTD threshold of RTD hard handoff

MOD DRCT Set thresholds of RTD (direct) hard handoff 0: Reserved

Ec/Io absolute threshold of HANDDOWN hard handoff 24

Maximum loop delay threshold of HANDDOWN hard handoff

MOD HNDDWN Set thresholds of

HANDDOWN hard handoff 0: Reserved

T_ADD value of pseudo pilot hard handoff 28

Ec/Io absolute threshold of pseudo pilot hard handoff 24

Relative threshold of pseudo hard handoff

MOD HHOBPLT Set thresholds of

pseudo pilot hard handoff

8

T_ADD value of co-frequency hard handoff 28

Ec/Io absolute threshold of co-frequency hard handoff 24

Relative threshold of co-frequency hard handoff

MOD HHOSFConfigure thresholds of co-frequency hard handoff

8

When the threshold of a hard handoff algorithm is set to an excessively high value, the related hard handoff will be difficult to trigger on the hard handoff border. It is because the signal strength of target pilot can hardly reach the threshold and thus call drop happens. However, a very low threshold for a hard handoff may result in “Ping-Pong” handoff in border areas.


Conduct dialing tests in the areas where the fault and call drops occur. If the MS can trigger the hard handoff process normally and no call drop occurs, the fault is removed.


10-5

10.2 Handoff Required Reject (requested terrestrial resource unavailable)


The BSC receives a Handoff Required Reject message containing the cause value “requested terrestrial resource unavailable”, which means the MSC cannot obtain any available circuit identification code (CIC) for the target BSC. Thus the handoff cannot go on.

You may click [Maintenance/Trace/A1 Interface Message Tracing] in the service maintenance system to view the messages traced at A1 interface.

II. Troubleshooting

See Figure 10-2 for the troubleshooting procedures.

The A2 circuit is faulty. (2)

Modify the configuration of the MSC orthe BSC.(4)

Verify the result（7)

N

Y

Y

N

Is the location area and the cell configuration of the BSC consistent

with that of the MSC? (3)

END

BSC receives the Handoff RequiredReject message during the hard handoff

Modify the configuration of the source BSC orthe target BSC(6)

Y

Y

N

Is the configuration of the source BSC consistent with that of the

traget BSC?(5)

Is the A2 circuit of thetarget BSC normal? (1)

Figure 10-2 Troubleshooting flowchart when the handoff required reject message is received

Steps:


10-6

1) Check the A2 circuit of the target BSC

Execute the command DSP A2 to check the A2 circuit of the target BSC.

In normal cases, the CIC status of trunk circuit should be “Idle”. If the CIC status is “Fault”, it means the A2 circuit is faulty.

2) Check A2 circuit for any error

If A2 circuit is faulty, see section 9.3, "A2 Interface Circuit Fault" for troubleshooting.

3) Check whether the location area and the cell configuration of the target BSC is consistent with that of the MSC.

To ensure that the MS can trigger a hard handoff normally between BSCs of the same MSC, the data of BSCs must be consistent with those of the MSC.

Contact MSC engineers to query the LAC and cell data of the MSC.

4) Modify the configuration of the MSC or the BSC

The data of the MSC should be modified by MSC engineers.

5) Check whether the data configuration of the source BSC is consistent with that of the target BSC.

To ensure the normal hard handoff between the two BSCs, the data configuration of the source BSC must be consistent with that of the target BSC.

Execute the command LST CELL to query the cell data configuration of the source BSC.

Execute the command LST CDMACH to query the configuration of the external pilots and the command LST NBRCDMACH to query the configuration of the relationship of neighbor pilot.

Compare the data configuration of the source BSC and the target BSC, primarily the configuration of the external pilot and the relationship of neighbor pilot.

6) Modify the configuration of the source BSC or the target BSC.

If you find any consistency, you can modify the configuration accordingly:

If the configuration of the target cell is wrong, remove the wrong configuration by using the command RMV OUTCDMACH and then add the new one by using the command ADD OUTCDMACH.


10-7

If the correspondence between the cell and the carrier is wrong, correct it by using the command MOD OUTCDMACH.

If the neighborhood relationship of the carrier is improperly configured, remove the wrong configuration by using the command RMV NBRCDMACH and add the new one by using the command ADD NBRCDMACH.

7) Verify the result.

In the service maintenance system, click [Maintenance/Trace/A1 Interface Message Tracing] to view the messages traced at A1 interface. If no Handoff Required Reject message containing the cause value “requested terrestrial resource unavailable” is originated during the hard handoff, the fault is removed.

10.3 Failed to Trigger Inter-band Class Hard Handoff


The neighbor cell of the border cell is the cell with different band classes. A MS fails to trigger the hard handoff when moving to the cell with different band classes. The MS does not trigger (inter-band class) hard handoff when moving to the border, and the BSC system does not issue Handoff Direction Message to the MS.

II. Troubleshooting



10-8

The MS support the targetband class.(1)

Replace with the MS supporting thetarget band class.

END

The switch of inter-band class hardhandoff is enabled (2)

Enable the switch of inter-band classhard handoff.(3)

Neighbor relation of different bandclasses is configured.(4)

Add the neighbor relation of differentband classes.(5)

Direct hard handoff is configuredwith the carrier with different band

classes.(6)

Add the direct hard handoff target.(7)

Check other hard handoff parameters ofdifferent band classes.(8)

Test.(9)

N

Y

N

N

N

Y

Y

Y

Figure 10-3 Troubleshooting flowchart for failing to trigger the inter-band class hard handoff

Steps:

1) The MS supports the target band class.


10-9

2) The switch of inter-band class hard handoff is enabled.

In the Service Maintenance System, execute the command to check whether the switch of BSC inter-band class hard handoff is enabled.

LST BSCHO:;

3) Enable the switch of inter-band class hard handoff.

In the Service Maintenance System, execute the command to enable the switch of BSC inter-band class hard handoff, for example:

MOD BSCHO: BANDHHOSW=ON;

4) Neighbor relation of different band classes is configured.

To guide the MS to search for the pilot of different band classes when the MS detects bad forward pilot, it is required to configure the neighbor relation of different band classes for this carrier sector correctly.

In the Service Maintenance System, execute the command to check whether the carrier with different band classes is configured in the neighbor set.

LST NBRCDMACH: NBRINF=DFNBR, BTSID=1, CN=10, SCTID=0;

5) Add the neighbor relation of different band classes.

In the Service Maintenance System, execute the command to add the carrier with different band classes for the neighbor set, for example:

ADD DFRNBRCDMACH: CCDMACH="1-10-0-78", NBRCDMACHS="961-20-0-450", SFFLAG=NULL,

DFFLAG=SINGLE, NBFLAG=SINGLE, DFRSN=2;

6) Direct hard handoff is configured with the carrier with different band classes.

When the MS moves to the edge of BTS coverage, the delay becomes large. If there is no appropriate soft handoff target and the MS has no detection report of different band classes, direct hard handoff is required.

In the Service Maintenance System, execute the command to check whether the direct hard handoff is configured with the carrier with different band classes.

LST DRCTTRG: BTSID=1, CN=10, SCTID=0;

7) Add the direct hard handoff target.


10-10

In the Service Maintenance System, execute the command to add the carrier with different band classes to be the target of direct hard handoff.

ADD DRCTTRG: CCDMACH="1-10-0-78", NBRCDMACHS="961-20-0-450";

8) Check other hard handoff parameters of different band classes.

The check of other parameters is the same as that of the hard handoff parameters of the same band, the checking flow please see Figure 10-1.

9) Test.

Make test calls again in the fault area. If the handoff can go normally, the troubleshooting succeeds.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 11 Packet Data Service Fault

11-1

Chapter 11 Packet Data Service Fault

Note:

Make sure that speech service is normal before you start the troubleshooting for data service fault.

11.1 Occasional Data Call Failure


Data calls originated by the MS fail occasionally.

II. Troubleshooting



11-2

Is wireless environmentstable?

Conduct dialingtest (6)

N

Y

N

Y

N

Y

N

Y

It results from networkconfiguration (5)

Optimize network

It results from PDSNconfiguration problem (4)

Check wirelessenvironment

End

Are all PDSNs normaland available? (2)

Is PCF configured withPDSNs? (1)

Do IP addresses conflict? (3)

Figure 11-1 Troubleshooting flowchart for occasional data call failure

Steps:

1) Check whether packet control function (PCF) is configured with multiple packet data serving nodes (PDSNs)

Execute the LST PDSN command to check the configuration:

Example LST PDSN:;

Result %%LST PDSN:;%%


PDSN Basic Information

----------------------

PDSN IP Address = 129.11.17.136


11-3

Secret Parameter Index = 0x00000100

Secret Key = 0x31323334353637383930313233343536

Verification Algorithm Mode = Prefix plus Suffix

Verification Algorithm = MD5

Re-transmit Protection Mode = Time Stamp

(Total result = 1)

--- END

The "Total result" indicates the number of PDSNs configured in the PCF. In the above example, one PDSN is configured, and the IP address is 129.11.17.136.

2) Check whether the connections of all PDSNs are normal and available

a) Check physical connections between the PCF and each PDSN. Specifically, check network cable connections, or ping the PCF from the PDSN. You may also connect a laptop to an Ethernet switch (it is 3026 usually) that connects to the CDMA high-speed access controller (CHAC). In latter case, check whether the PDSN is pinged successfully, so as to confirm the bottom link between the PCF and PDSN.

For example, to locate the fault by pinging with a laptop:

i) Connect the laptop to an Ethernet switch that connects to CHAC optical interface.

ii) Set the IP address of the laptop to be in the same network segment as that of the PCF, with no IP conflict.

iii) If the IP address of the PCF is 129.11.17.201, set the IP address of the laptop to 129.11.17.209.

iv) Execute the ping 129.11.17.136 at the laptop The 129.11.17.136 is PDSN's IP).

If the PDSN cannot be pinged through, this indicates that error exists on the physical links between the PCF and PDSN.

b) Check whether PCF parameter configured in each PDSN is consistent with that in the PCF, including secret parameter index, secret key, verification algorithm mode, verification algorithm and re-transmit protection mode.

You may execute the command LST PDSN to show the information of all PDSNs configured in the PCF.

The command for querying the parameters of the PDSNs varies with the manufacturer. For example, for the PDSN manufactured by 3COM, the query command is LIST VHA SA.


11-4

Caution:

If you want to ping the PCF at the PDSN, you should log in to the PDSN through Telnet mode to execute the ping command, and shouldby no means ping it at PDSN maintenance workstation. If the laptop is connected to an Ethernet switch that connects to the PCF for pinging the PDSN, the IP address of the laptop should be set to be in the same network segment as the PCF.

3) Check whether the IP planning of the PDSN or the PCF is correct.

Check for IP conflict in the network where the PCF and PDSN are located. The commands to show the IP addresses of the PDSN and PCF are as follows:

LST PDSN:;

LST PCF;

The result of executing the command LST PCF is as follows:

%%LST PCF:;%%


PCF Basic Information

---------------------

Subrack No. IP Address Address Network Mask

2 129.11.17.201 255.255.0.0

(Total result = 1)

--- END

In the result, the IP address of the PCF is 129.11.17.201.

4) Check PDSN configuration.

For the PDSN whose physical connection is abnormal and cannot be corrected, you may delete it from the PCF to prevent originating any connection to the PDSN.

For the PDSN with inconsistent parameter configuration at both ends, you may modify the configuration or delete the PDSN.

You can remove the PDSN in the PCF using the command RMV PDSN (with the parameter of "PDSN IP Address"). For example:

RMV PDSN: PDSNIP="129.11.17.136";

You can modify PDSN parameters in the PCF using the command MOD PDSN. For example:


11-5

MOD PDSN: PDSNIP="129.11.17.136", SCRKEY="1234567890123456", SPI="0x100",

CIPHALGM=PRESUFFIX, CIPHALG=MD5, RPM=TMSTMP;

Instead of resetting the related boards, the above commands take effect upon the execution.

You can use the command LST PDSN to check the PDSN configuration after the removal of the PDSN or the modification of PDSN parameters.

5) Check network configuration.

You should correctly configure network equipment according to IP network configuration requirements.


Initiate a data call to check whether the fault is removed.

11.2 Data Call Failure

11.2.1 No Messages on A Interface


The data calls initiated by the MS always fail. There is no message traced on A1, A9 and A11 interfaces.

II. Troubleshooting



11-6

Can the MS be used for data service?

End

N

Y

N

Y

It results from theconfiguration of wireless

modem.

MS dial-up configurationproblem


N

Y

N

Y

Data service call failed, and thereare no message at A interface

Is the configuration of wirelessmodem correct? (2)Is the MS dial-up configuration

correct? (1)

Can the wireless modem be used for calling data

service?

Figure 11-2 Troubleshooting flowchart for no messages on A-interface

Steps:

1) Check whether MS dial-up configuration is correct.

If the MS is used for dial-up, observe whether the MS screen displays the corresponding data service. If not, check the configuration of the terminal, for example, whether the port rate of the terminal is consistent with that of the computer, whether the setting of port ID is correct, or whether the setting of dial-up attributes is correct.

2) Check whether the configuration of wireless modem is correct.

The wireless modem has an indicator to show its working status.

If the wireless modem works normally, the indicator will flash at a frequency of 2Hz.

If the wireless modem works abnormally, the indicator will flash fast.


11-7

You can observe the indicator to determine whether the wireless modem is correctly configured.

You also need to check whether the port configuration and relevant parameters are correct.


Initiate a data call to check whether the fault is removed.

11.2.2 Only Reverse Message on A9 Interface


Data calls originated by the MS fail. Only reverse message (from the BSC to PCF) is traced on A9 interface.

II. Troubleshooting



11-8

End

N

Y

N

Y

N

Y

It results from IPconfiguration (5)

It results from data inFAM and BAM (6)

It results from dataconfiguration of

transport layer (7)

Check BSC IP and PCF IP (1)


Data service call failed, andonly reverse message exists at

A9 interface

Are BSC and PCF IP in the same network

segment? (2)

Is the configuration of transportlayer correct? (4)

Is the data in FAM and BAMidentical? (3)

Figure 11-3 Troubleshooting flowchart for reverse message on A9 interface during data call

Steps:

1) Check IP addresses of the BSC and PCF.

a) Execute the command LST BSCINF to show IP address of the BSC.

Example LST BSCINF:;

Result %%LST BSCINF:;%%


BSC Basic Information

---------------------

BSC IP Address = 129.11.17.1

BSC Subnet Mask = 255.255.0.0

Manufacturer ID = 3


11-9

Entity ID = 45381

Mobile Country Code = 460

Mobile Network Code = 3

MSC ID = 0x123456

A-interface Version No. = IOS4.1

PN Code Increment = 4

CSWS Subrack Type = E1 Switching

RFN Clock Board = UTCP board

(Total result = 1)

--- END

In the result, the IP address of BSC is 129.11.17.1.

b) Execute the following command to show IP address of the PCF :

LST PCF:;

2) Check whether IP addresses of the BSC and PCF are in the same network segment.

Generally, the first two digits of the IP addresses of the BSCand PCF should be consistent. For example, the IP address of the BSC is 129.11.17.1 and that of the PCF is 129.11.17.201.

If the two are not in the same network segment, the message will be lost.

3) Check whether the data in the BSC and BAM are consistent.

Execute the command STR CRC to check whether the data of the BSC is consistent with that of the BAM.

Example

Compare the data of CPCU in subrack 2 between the BSC and BAM.

STR CRC: FN=2, BTP=CPCU;

Result %%STR CRC: FN=2, BTP=CPCU;%%


CRC result

----------

Table ID Table description CRC result

0 BSC System Information Table Identical

4 Millisecond Timer Description Table Identical


11-10

10 Software Parameter Table Identical

85 PIM Parameter Table Identical

94 PDSN Parameter Table Identical

95 CPCU System Parameter Table Identical

(Total result = 6)

--- END

The "Identical" indicates that the data of the BSC is consistent with that of the BAM in 6 tables in total.

Note:

The parameters related to the command STR CRC are [Subrack No.] and [Board Type]. Normally, it is to check the data configuration of CRMU, CSPU, CPCU and various CMUXs.

4) Check whether the configuration of transport layer is correct.

If the data in the BSC and BAM is consistent, or it is hard to judge whether their data is consistent, you should check the configuration of transport layer, including the channel configuration between the CSPU and CRMU, between the CRMU and CPCU, between the CRMU and its subordinate CMUX, between the CPCU and its subordinate CMUX, and between CMUXs.

You may use the command LST IPCPVC to check the channel configuration.

Example

Check IPC channel configuration of CSPU in slot 12 of subrack 4.

LST IPCPVC: FRAMENO=2, SLOTNO=12;

Result %%LST IPCPVC: FN=4, SN=12;%%


IPC PVC

-------

Source Subrack No. Source VCI Destination VPI

Source Slot No. Destination Subrack No. Destination VCI

Source Subsystem No. Destination Slot No. Bandwidth(M)

Source VPI Destination Subsystem No.

4 0 0 2 82 4 12 0 2 82 2.00

4 1 0 2 83 4 12 0 2 83 2.00

4 2 0 2 84 4 12 0 2 84 2.00


11-11

4 11 0 2 85 4 12 0 2 85 2.00

4 12 0 2 86 2 2 0 5 85 2.00

4 12 0 2 81 4 7 0 2 81 2.00

5 12 0 2 86 4 12 0 2 87 2.00

(Total result = 7)

--- END

You can determine the existence of IPC channel from the CSPU to CRMU according to the Source Subrack No., Destination Subrack No., Source Slot No., and Destination Slot No.

In the above result, the CRMU is located in slot 2 and subrack 2, and the above listed IPC contains the configuration (the 5th line), which indicates that IPC channel exists between the CSPU and CRMU.

5) Clear IP address configuration problem.

a) Modify IP addresses of the BSC and PCF.

IP addresses of the BSC and PCF do not support dynamic modification. However, you may delete the incorrect PCF data, and then add the correct one.

For example, you may execute the following commands to delete and add the IP address.

RMV PCF: FN=2;

ADD PCF: FN=2, PCFIP="129.11.17.230", PCFSNM="255.255.0.0";

The CPCU should be reset after the modification.

b) Check whether IP address of the PCF is successfully modified using LST PCF.

c) Update IP address of the BSC in ADD BSCINF and PCF IP address in ADD PCF in the script so that the script is consistent with the actual configuration.

For example, you may execute the following commands to update the IP addresses:

ADD BSCINF: BSCID="129.11.17.1", BSCSNM="255.255.0.0", MRKTID=3,

ENTID=45381, MCC=460, MNC=3, MSCID="0x123456", APVER=IOS4.1, PNINC=4,

MAXSDB=80, SWT=SWT_8850, RFNBRDCLK=UTCP;

ADD PCF: FN=2, PCFIP="129.11.17.230", PCFSNM="255.255.0.0";

6) Clear data problem between the BSC and BAM

Reset the boards whose data is inconsistent between the BSC and BAM, including related CMUXs.


11-12

7) Clear data configuration problem of transport layer

Modify data configuration of transport layer.


Initiate a call.

In Airbridge cBSS Maintenance, click [Maintenance/Trace/A9 Interface Message Tracing] to trace the messages on this interface. If the traced messages are normal, the fault is cleared.

11.2.3 Only Reverse Message on A11 Interface


The data calls originated by the MS fail. The messages traced on interfaces show that both forward and reverse messages are traced at A9 interface, while only reverse message (from the PCF to PDSN) is traced on A11 interface.

II. Troubleshooting



11-13


End

N

Y

N

Y

N

Y

It results from networkconnection (4)

It results from equipmentconfiguration (5)

Check physical connectionbetween CHAC and PDSN (1)


Are the port IP configurationand route configuration ofPDSN and AAA correct?

(2)

Trace PDSN RP interfaceand check whether reverseA11 message is received

(3)

Figure 11-4 Troubleshooting flowchart for data call failure and only reverse message existing at A11 interface

Steps:

1) Check the physical connection between the CHAC and PDSN.

a) Check whether the physical connection between the CHAC and the optical module switch is normal by observing the indicator of the optical module switch.

Take 3025 as an example. If the Giga indicator is on, it indicates that signals exist at the optical interface. If the Giga indicator flashes, it indicates that data is being transmitted.

(b) Check whether self-negotiation mode of CHAC and that of switch optical module port are consistent. Generally, both should be "Self-negotiation" or "Auto".

Execute the command LST HACPRT to view the working mode of optical interface in CHAC. Two modes are available: "Self-negotiation" and "1000M-Full".

(c) If the PCF is not in the same network segment as the PDSN, the PCF gateway should be configured. Check whether the system is configured with PCF gateway, but fails to connect to PDSN through the gateway equipment (router).


11-14

You may execute the command LST PCFGW to check whether PCF gateway is properly configured.

The IP address of the gateway is the address of the router port connecting to the CHAC. The address and IP address of the PCF should be in the same network segment.

Example LST PCFGW:;

Result %%LST PCFGW:;%%


PCF Gateway Basic Information

-----------------------------

Subrack No. Gateway Address Gateway Mask

3 129.11.17.254 255.255.0.0

(Total result = 1)

--- END

The results show that subrack 3 is configured with PCF gateway, IP address of the gateway is 129.11.17.254, and mask is 255.255.0.0.

d) If the gateway is configured, check whether the IP address and mask of the gateway are correct, and whether it is consistent with gateway equipment (router). Check whether the settings of the CHAC and PDSN port are correct.

2) Check whether IP address configuration and route configuration of the PDSN and AAA port are correct.

In the PDSN and authentication, authorization, and accounting (AAA), check whether IP address configuration is correct, and whether the correct route option is configured. You may ask PDSN and AAA maintenance engineers for help.

3) Trace PDSN RP interface and check whether the reverse A11 message is received

Trace RP interface message in the PDSN, and observe whether the PDSN receives A11 message sent from the PCF. If not, check the physical connection between the CHAC and PDSN, and whether the data configuration of transport layer between the CDMA PCF control unit (CPCU) and CHAC is correct. As these operation involve the PDSN, contact PDSN maintenance engineer for help.


11-15

The data between CPCU and CHAC is borne through the IPOA. You may check the channel configuration between these two boards using LST IPOAPVC.

Example

To check IPOA channel configuration of the CPCU in slot 4 of subrack 2, execute:

LST IPOAPVC: FN=2, SN=4;

Result %%LST IPOAPVC: FN=2, SN=4;%%


IPOA PVC

--------

Source Subrack No. = 2

Source Slot No. = 2

Source VPI = 5

Source VCI = 88

Source Board Peer IP Address = 129.11.17.204

Source Board Local IP Address = 129.11.17.4

Destination Subrack No. = 2

Destination Slot No. = 4

Destination VPI = 5

Destination VCI = 88

Destination Board Peer IP Address = 129.11.17.4

Destination Board Local IP Address = 129.11.17.204

Rx Bandwidth (M) = 2

Tx Bandwidth (M) = 2

Source Subrack No. = 2

Source Slot No. = 6

Source VPI = 1

Source VCI = 83

Source Board Peer IP Address = 80.8.141.0

Source Board Local IP Address = 80.8.203.0

Destination Subrack No. = 2

Destination Slot No. = 4

Destination VPI = 1

Destination VCI = 83

Destination Board Peer IP Address = 0.0.0.0

Destination Board Local IP Address = 129.11.17.204

Rx Bandwidth (M) = 0

Tx Bandwidth (M) = 0

(Total result = 2)


11-16

--- END

You can find the configuration of IPOA channel between the CPCU and CHAC according to the listed "Subrack No.", "Slot No." and "IP Address".

In the above example, the IP address of the CHAC in slot 6 of subrack 2 is 80.8.203.0. If it is contained in the IPOA returned, the IPOA channel exists between the CPCU and CHAC.

4) Clear network connection problem.

This problem usually is resulted from unreliable connection of the network cable , router configuration error, data script error, PDSN or AAA route configuration error. Check network connection according to step 1 and step 3. Then initiate a call for verification.

5) Clear equipment configuration problem.

You can check the PDSN and AAA server configuration according to instructions and network planning. You may contact PDSN and AAA server maintenance engineer for help.


Initiate a call to check whether the fault is cleared.

11.2.4 Call Disconnected Several Seconds after the Connection


The MS originates a data call. The call is disconnected several seconds after the connection. The call setup fails. Both forward and reverse messages are traced on the A9 and A11 interfaces.

II. Troubleshooting



11-17

End

N

Y

N

Y

It results from parameterconfiguration of PDSN or

PCF (5)

It results from parameterconfiguration of PPP or

AAA (6)

Check the cause value ofA11 reply message (1)

Trace PPP message (3)


Is A11 registration requestsuccessful?

(2)

Is PPP negotiationsuccessful? (4)

Figure 11-5 Troubleshooting flowchart for data call disconnected several seconds after the connection

Steps:

1) Check the cause value of A11 reply message.

a) In the traced A11 message, check the cause value of PDSN reply message.

b) Check the code field in A11-Registration-Reply message, which contains values like:

0x00: Accepted. A11 access succeeded. 0x83: Mobile-node-failed-authentication. A11 access failed, which is generally

resulted from the inconsistency of the parameters configured in the PCF and PDSN.

2) Check whether A11 registration request is successful.

Check A11-Registration-Reply message: 0x00 means success; others mean failure.

3) Trace peer-peer protocol (PPP) message

Trace PPP message in the PDSN, and observe PPP negotiation procedure.

For the operations on the PDSN, ask PDSN maintenance engineer for help.


11-18

4) Check whether PPP negotiation is successful

Trace PPP message at PDSN server, and analyze whether PPP negotiation is successful.

For the operations on the PDSN, ask PDSN maintenance engineer for help.

Note:

Generally, the failure cause is "Authentication Failure". If the problem is caused by incorrect username or password, you can contact AAA server maintenance engineer to acquire the correct username and password, and modify dialing username and password to complete PPP negotiation.

5) Clear PDSN or PCF parameters configuration problem

If the problem results from PDSN or PCF parameter configuration, see the descriptions on checking PDSN configuration in section 11.1 Occasional Data Call Failure.

6) Clear PPP or AAA parameters configuration problem

Check whether the dial-up username and password in the terminal are consistent with those in AAA server.

If the setup is incorrect, contact AAA server maintenance engineer for the correct username and password, and modify dial-up username and password.


Initiate a call to check whether the fault is removed.

11.3 Data Service Handoff Failure


Data service handoff always fails.

II. Troubleshooting

See Figure 11-6 for the troubleshooting procedure:


11-19

End

N

Y

N

Y

It results from wirelessenvironment (3)

It results from protocolinconsistency (4)


Data service handoff failed

Is the wirelessenvironment good? (1)

Are the protocol versions ofPCF and PDSN identical?

(2)

Figure 11-6 Troubleshooting flowchart for data service handoff failure

Steps:

1) Check radio environment

If the data call is successful, this indicates that A11 interface link is normal and the handoff failure is caused by the radio environment. You can test radio quality through voice calls or other methods.

2) Check whether the protocol versions of the PCF and PDSN are consistent

If the protocol versions of the PDSN and PCF are inconsistent, the handoff message will be improperly decoded, and the PDSN loses the message.

You may execute LST BSCINFO in the BSC to check PCF protocol version. You may also get the version No. through the value of APVER field in the script

using the following command. In the example, the protocol version is "IOS4.1". ADD BSCINF: BSCID="129.11.17.1", BSCSNM="255.255.0.0", MRKTID=3,

ENTID=45381, MCC=460, MNC=3, MSCID="0x123456", APVER=IOS4.1, PNINC=4,

MAXSDB=80, SWT=SWT_8850, RFNBRDCLK=UTCP;

3) Clear radio network problem.


11-20

Refer to the troubleshooting suggestions for voice handoff problems.

4) Clear the protocol inconsistency problem.

Upgrade the BSC or PDSN, to keep protocol consistency at both sides.

Contact PDSN maintenance engineer for help if PDSN software should be upgraded.


Originate calls and perform handoff to check whether the fault is removed.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 12 Quasi-Concurrent Service Fault

12-1

Chapter 12 Quasi-Concurrent Service Fault

12.1 Failed to Trigger Quasi-Concurrent Service

12.1.1 Not Receiving Clear Command Message


A MS is called when processing data service. Through tracing A1 interface signaling message on the MS, it is found that the MSC does not send Clear Command Message.

II. Troubleshooting


Query parameter setting of quasi-concurrent service of called MS in

HLR. (1)

Setting inHLR does not support quasi-

concurrent service.Query the version of MSC .(3)

Change parameter setting of quasi-concurrent service of called MS in

HLR.(2)

MSC doesnot support quasi-concurrent

service.

Upgrade MSC version.(4)


End

Y

N

Y

N

Figure 12-1 Troubleshooting flowchart for Clear Command Message receiving failure

Steps:

1) Query the parameter setting of the quasi-concurrent service of the called MS in the HLR.


12-2

Check the parameter setting to see whether the MS supports the quasi-concurrent service. For detailed operation on HLR, contact HLR maintenance engineers.

2) Change the parameter setting of the quasi-concurrent service of the called MS in the HLR.

Change the parameter setting to make the MS support quasi-concurrent service. For detailed operation on HLR, contact HLR maintenance engineers.

3) Check whether the MSC version supports the quasi-concurrent service.

The quasi-concurrent service needs support from the MSC. Check whether the current MSC version supports the quasi-concurrent service. For detailed operation on MSC, contact MSC maintenance engineers.

4) Upgrade the MSC version.

Upgrade the MSC version to make it support the quasi-concurrent service. For detailed operation on MSC, contact MSC maintenance engineers.


Make a call to a MS that is processing data service. In the Service Maintenance System, start the A1 interface signaling tracing on the BSC that is serving the called MS. If the MSC sends a Clear Command Message to the BSC, the troubleshooting succeeds. Check whether the called MS can suspend the data service and establish a call. If the call establishment fails, you need further troubleshooting.

12.1.2 Not Sending Service Option Control Message


A MS is called when processing data service. Through tracing Um interface signaling message on the MS, it is found that the BSC does not send Service Option Control Message.

II. Troubleshooting



12-3

Query the status of quasi-concurrent service switch.(1)

The switch is notenabled.

Query the cause value of quasi-concurrent service release and that

of Clear Command release.(3)

Enable quasi-concurrent serviceswitch on BSC.(2)

Cause values donot match.

Change release cause value ofquasi-concurrent service in BSC

configuration.(4)


End

Y

N

Y

N

Figure 12-2 Troubleshooting flowchart for Service Option Control sending failure

Steps:

1) Query the status of quasi-concurrent service switch.



Result:



Software Parameter

------------------


CCM 27 0x00001265

(Total result = 1)


12-4

--- END

Note:

Software parameter 27 controls the quasi-concurrent service. The default value is 0 x 00001265, which is specified as below:

Bit 0 (least-significant bit): Control switch of the quasi-concurrent service. 0: support; 1: not support. Bits 1 – 8: Dormant time for data service (the default value is 50, namely, 5 seconds). Bits 9 – 15: Cause value of the call release (the default value is 0×09). Bits 16 – 31: Reserved.

2) Enable the quasi-concurrent service switch on the BSC.

Execute the following command for modification in the Service Maintenance System:


Change the bit of software parameter 27 from 0 to 1.

3) Query the value of quasi-concurrent service release and that of Clear Command release.

In the Service Maintenance System, execute the following command to query the cause value of the quasi-concurrent service release configured on the BSC. LST SOFTPARA: SRVMN=CCM, PRMNO=27;

In the returned software parameter value, bits 9 – 15 indicate the release cause value. The default value is 0x09.

To query the cause value of the Clear Command release, you need to start the A1 interface signaling tracing for the BSC that is serving the called MS. The Clear Command sent by the traced MSC contains the release cause value.

4) Change the cause value of the quasi-concurrent service release in the BSC configuration.

Execute the command for modification in the Service Maintenance System:


Change bits 9 – 15 of software parameter 27 to the matching release cause value.



12-5

Make a call to the MS processing data service. In the Service Maintenance System, start the Um interface signaling tracing for the BSC that is serving the called MS. If the BSC sends Service Option Control, the troubleshooting succeeds. Check whether the called MS can suspend data service and establish a call. If the call establishment fails, you need further troubleshooting.

12.1.3 Data Service Call Suspended and Call Establishment Failed


A MS is called when processing data service. The data service of the called MS is suspended, but the call establishment fails.

II. Troubleshooting


Paging message processing is

incorrect.(1)HLR or MSC is faulty.

Solve problems on pagingmessage processing.(2)


End

Y

N

Figure 12-3 Troubleshooting flowchart of call establishment failure

Steps:

1) Paging message processing is incorrect.

The difference between the quasi-concurrent service and the common MTC is the process that the MSC informs the called MS of the suspension of the data service. After the BSC sends the Service Option Control, the call processing is the same as that of the common MTC.

For problems after the data service suspension, see “2.3 MTC Failure”.


12-6

2) Solve problems on paging message processing

To solve the problems on paging, see “2.3 MTC Failure”.


Make a call to the MS processing data service. Check whether the called MS can suspend the data service and establish a call.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 13 Circuit Data Service Fault

13-1

Chapter 13 Circuit Data Service Fault

Note:

You should check the following items before removing circuit data service faults: Make sure the speech service is normal. The solution of Huawei CDMA system circuit data service supports two IWF networking modes: The

IWF is located in the BSC or in the MSC. This chapter is applicable to the former. See user manual of the MS and make sure it supports circuit data service and the IWF switch of the

BSC is on. You can query the status of the IWF switch using the command LST SOFTPARA. In the service

maintenance system, execute the command LST SOFTPARA to quey software parameter 6 of the CCM. The value "0x00000000" means that the switch is off. The value "0x00000001" means that the switch is on. You can also turn on the switch using the command MOD SOFTPARA.

13.1 Asynchronous Data Service Call Failure

13.1.1 MS cannot Access Hyper Terminal


The MS fails to connect the hyper terminal and thus cannot originate asynchronous data call. .

II. Troubleshooting



13-2

END

Set the rates(2)

N

Y Y

N

Is the MS rate consistent with the serial port

rate of hyper terminal?(1)

Replace thedata line

Is the serial port of hyper terminal

available?(4)

Replace the serial port(5)

Conduct verification(6)

Is data linedamaged?(3)

Figure 13-1 Troubleshooting flowchart for MS connection failure

Steps:

1) Make sure the MS rate is consistent with the serial port rate of hyper terminal.

The MS can communicate with the hyper terminal only when the rate settings of the MS and of the corresponding serial port of the hyper terminal are consistent.

As for asynchronous data call service, you can set the rate of the MS to 19,200 kbps or 115,200 kbit/s.

For how to query the configured rate of the MS, see the relevant documents of the MS.

To query the configured rate of the serial port of the hyper terminal, select [File/Attribute] to open the [Attribute] dialog box, and then click <Configuration> to pop up the [COM Attribute] dialog box to check the baud rate.

2) Set the rates.

For how to set the rate of the MS, see the relevant documents of the MS. To set the serial port rate of the hyper terminal, refer to step 1).

3) Check whether the data line is intact.

Check whether the data line between the MS and the hyper terminal is intact.


13-3

If you are not sure about it, replace the data line. Then check whether the fault is cleared.

4) Make sure the serial port of hyper terminal is available.

If the serial port of the hyper terminal connecting with the MS is damaged or occupied by other application, use other serial ports.

5) Replace the serial port.

After replacing the serial port, reset the serial port rate and keep it consistent with the rate of the MS.


If the MS can connect with the hyper terminal well, it indicates the fault is cleared.

13.1.2 Mobile-Originated/Mobile-Terminated Asynchronous Data Call Failure


Asynchronous data calls originated or terminated by the MS always fail. The hyper terminal connecting with the MS displays "NO CARRIER".

II. Troubleshooting



13-4

Is the called party set to asynchronous data

receiving mode?(3)

Set the receiving mode ofthe called party(4)

Does MS subscribeasynchronous data service

in HLR?(1)

Subscribe asynchronousdata service in HLR(2)

Does the called party hookoff?(7)

Set automatic hookoff modefor the called party(8)

Does the called partyring?(5)

Confirm the AT command(6)

Conduct verification(10) Is the configuration of theCIWF correct?(9)

END

N

Y

Y

Y

Y

N

N

N

Figure 13-2 Troubleshooting flowchart for mobile-originated/mobile-terminated asynchronous data call failure

Steps:

1) Check whether the MS subscribes to asynchronous data service in the HLR.

The service option of the asynchronous data is 4, 12 or 4,100. Check in the HLR whether the MS subscribes to these services.

2) Subscribe to asynchronous data service in the HLR.

For how to subscribe to asynchronous data service in the HLR, contact HLR maintenance engineers.

3) Check whether the called party is set to asynchronous data receiving mode.

4) Set the receiving mode of the called party.

If the called party is an MS, you must set the MS to asynchronous data receiving mode. For the specific setting method, see the user guide of the MS.

If the called party is a modem of a fixed station, there is no need to set the receiving mode.


13-5

5) Check whether the called party rings.

After the calling party originates an asynchronous data call, check whether the called party rings.

The hyper terminal of the called party should display "RING". If it displays nothing, check whether the AT command used by the calling party is correct.

6) Confirm the AT command.

The calling party can originate asynchronous data calls by using ATDT or ATD commands. Since some MSs do not support ATDT commands, it is recommended to use ATD commands.

7) Check whether the called party hooks off.

If the called party does not hook off after ringing, the asynchronous data call cannot be set up.

8) Set automatic hookoff mode for the called party.

You can issue the AT command to set automatic hookoff through the called hyper terminal:

ATS0=n

Where, n indicates the called party hooks off automatically after ringing n times.

9) Check whether the configuration of the CIWF is correct.

Check the following items:

Whether the CIWF is available. Whether the configuration of the MODEM chip of the CIWF is correct.

The CIWF is available only when the following requirements are satisfied:

The CIWF runs normally. You can use the command DSP FRMINFO to query the operational status of the CIWF.

The management of the CIWF is enabled. You can use the command DSP FRMINFO to query the operational status of the CIWF.

At least one MD channel and one PSTN channel are in "IDLE" status. You can use the command DSP IWFLCHANNEL to query the status of the channel.

The interface IP configuration of the CIWF is correct. You can use the command DSP IWFITIP to query the IP configuration of the interface.


13-6

The IP address pool configuration of the CIWF is correct. The IP addresses are available. You can use the command DSP IWFIPPOOLINFO to query the configuration.

Configure the MODEM chip parameters properly:

The MODEM chip parameters include A law and µ law. The parameters vary with different countries. It is recommended to configure them according to the actual application.

You can use the command LST IWFMODEM to query the parameters.


If the MS can originate or terminate asynchronous data calls, it indicates that the fault is cleared.

13.2 Facsimile Call Failure

13.2.1 PC (G3) Facsimile Call Failure


The PC (G3) facsimile calls originated by the MS always fail.

II. Troubleshooting



13-7

Does the MS subscribe to PC (G3) facsimile

service?(2)

Subscribe to PC (G3) facsimileservice in the HLR(3)

Are the facsimile software and the MS

properly set?(1)


Is the called party set to PC (G3) facsimile

receiving mode?(4)

Set the called party to PC(G3) facsimile receiving

mode(5)


END

N

Y

Y

YN

N

N Does the called party hookoff?(7)

Set automatic receivingmode for the called facsimile

application(8)

N

Y

Y

Figure 13-3 Troubleshooting flowchart for PC (G3) facsimile call failure

Steps:

1) Check whether the facsimile software and the MS are properly set.

See relevant documents to check whether the MS and the facsimile are properly set and they can communicate with each other normally.

2) Check whether the MS subscribes to PC (G3) facsimile service.

The service option of the PC (G3) facsimile is 5, 13, or 4101. Check in the HLR whether the MS subscribes to this service.

3) Subscribe to PC (G3) facsimile service in the HLR.

For how to subscribe to facsimile service in the HLR, contact HLR maintenance engineers.

4) Check whether the called party is set to PC (G3) facsimile receiving mode.


13-8

5) Set the called party to PC (G3) facsimile receiving mode.

If the called party is an MS, you must set the MS to PC (G3) facsimile receiving mode. For the specific setting method, see the user guide of the MS.



When the calling party originates a PC (G3) facsimile call, the facsimile software at the called party side normally displays the incoming call or generates prompt tone.

If it displays nothing and the called number is correct, you shall check whether the MS and the facsimile software at the calling party side are compatible.


If the called party does not hook off after ringing, the PC (G3) facsimile call cannot be set up.

8) Set automatic receiving mode for the called facsimile application.

The facsimile can be set to automatic receiving mode or manual receiving mode.

It is recommended to set it to automatic receiving mode. If you set it to manual receiving mode, you must start the receiving program when there is incoming call or prompt tone.


See the relevant contents in step 9) in section 13.1.2 Mobile-Originated/Mobile-Terminated Asynchronous Data Call Failure.


If the MS can originate PC (G3) facsimile calls, it indicates that the fault is cleared.

13.2.2 Analog Facsimile Call Failure


The analog facsimile calls originated by the MS always fail.


13-9

II. Troubleshooting



13-10

Does the MS subscribe to analog facsimile

service?(2)

Subscribe to analogfacsimile service in the

HLR(3)

Does the MS support analog facsimile

service?(1)


Check whether the callednumber is correct

Is the calledparty set to analog facsimile

receiving mode?(4)

Set the called party toanalog facsimile receiving

mode(5)


END

N

Y

Y

YN

N

N Does the called party hookoff?(7)

Set automatic receivingmode for the called facsimile

machine(8)

N

Y

Y

Figure 13-4 Troubleshooting flowchart for analog facsimile call failure

Steps:

1) Check whether the MS supports analog facsimile service.

See relevant documents of the MS and facsimile software to make sure the MS supports analog facsimile service.

Generally, the MS can support the analog facsimile service only when equipped with an additional facsimile card. The facsimile card is optional. You must check whether the facsimile card is installed before sending the analog facsimile with the MS.

2) Check whether the MS subscribes to analog facsimile service.

The service option of the analog facsimile is 20, or 21. Check in the HLR whether the MS subscribes to this service.

3) Subscribe to analog facsimile service in the HLR.

For how to subscribe to analog facsimile service in the HLR, contact HLR maintenance engineers.

4) Check whether the called party is set to analog facsimile receiving mode.


13-11

5) Set the called party to analog facsimile receiving mode

If the called party is an MS, you must set the MS to analog facsimile receiving mode. For the specific setting method, see the user guide of the MS.



When the calling party originates analog facsimile calls, the called party usually rings. If there is no ring, check whether the called number is correct.

Note:

When the facsimile machine at OMC side originates the analog facsimile call, it is required to add prefix to the called number. If the prefix is not added, the MS originates speech call. For the content of the prefix, see the relevant document of the MS.


If the called party does not hook off after ringing, the analog facsimile call cannot be set up.

8) Set automatic receiving mode for the called facsimile machine.

The facsimile can be set to automatic receiving mode or manual receiving mode.

It is recommended to set it to automatic receiving mode. If you set it to manual receiving mode, you must start the receiving program when there is incoming call or prompt tone.


See the relevant contents in step 9) in section 13.1.2 Mobile-Originated/Mobile-Terminated Asynchronous Data Call Failure.


If the MS can originate analog facsimile calls, it indicates that the fault is cleared.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 14 CDR Fault

14-1

Chapter 14 CDR Fault

14.1 No CDR information


The call detail record (CDR) information cannot be displayed.

II. Troubleshooting



14-2

Start CDR service process.

The CDR server isinstalled in the BAM.(1)

END

Check the connection between CDRservers in BSC and in BAM.(3)

Check IP address of CDR server.(4)

Check setting of CDR filter switch.(5)

Adjust flow control level forforbidding CDR sending.(8)

Install CDR service program.

The CDR service processis normal.(2)

N

Y

There is incoming call.(6)

The system is in flowcontrol protection status.(7)

N

Y

N

N

Y

Y

Test.(9)

Figure 14-1 Troubleshooting flowchart for CDR fault

Steps:

1) The CDR server is installed in the BAM.

Check the background service process through BAM manager. If there is no CDR service process, you need to install the CDR server.

2) The CDR service process is normal.

Check the service process through BAM manager. If the service process is not in running status, start the service process.


14-3

3) Check the connection between CDR servers in BSC and in BAM.

For example, in the WINDOWS operating system, select [Start/Run…]; and then execute the command cmd to enter MS-DOS. Execute the Ping command to check whether the communication link status of CSPU (IP address: 129.0.0.1) is normal.

ping 129.0.0.1

4) Check IP address of CDR server.

In the Service Maintenance System, execute the following command to check whether the IP address of the foreground CDR server is set correctly:

LST DATASVRIP;

If the IP address of the CDR server is set incorrectly in the BSC, execute the command in the Service Maintenance System to change it. For example, change the IP address of the CDR server to 10.11.12.13:

MOD DATASVRIP: CDRIP="10.11.12.13";

5) Check setting of CDR filter switch.

In the Service Maintenance System, execute the following command to check whether the CDR filter switch is set correctly:

LST CDRFILTER:;

You can also check the CDR filter switch status of the specified subrack and call release. For example, to check the CDR filter switch status of subrack 2 and call release type 1, execute the following command in the Service Maintenance System:

LST CDRFILTER: FN=2, CFC=1;

If the CDR filter switch is set incorrectly, execute the command in the Service Maintenance System to change the setting. For example, to enable the CDR filter switch of subrack 2 and call release type 1, execute the following command:

MOD CDRFILTER: FN=2, CFC=1, SWT=ON;

6) There is incoming call.

Check whether is any incoming call. If not, you cannot see the CDR.


14-4

7) The system is in flow control protection status.

If the flow control grade of the system reaches or exceeds the level forbidding CDR sending, you cannot see the CDR.

In the Service Maintenance System, execute the following command to query the flow control grade that forbids sending CDR.

LST SOFTPARA: SRVMN=CDR, PRMNO=1;

8) Adjust flow control level for forbidding CDR sending.

If you need to adjust the flow control grade that forbids sending CDR to 4, execute the following command in the Service Maintenance System:

MOD SOFTPARA: SRVMN=CDR, PRMNO=1, PRMV="0x00000004";

8) Test.

Check whether there is any CDR information in the Service Maintenance System. If yes, the troubleshooting succeeds.

Maintenance Manual – Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 15 RFMT Fault

15-1

Chapter 15 RFMT Fault

15.1 Starting RFMT Trace Task Failed


The Service Maintenance System fails to carry out the radio frequency measurement tool (RFTM) trace task when the following command is executed:

SET RFMT: OPT=PILOT_CALL_TRACE, SWITCH_PLT=START, CN=10, SCTID=0, CRRID=10;

Result: %%SET RFMT: OPT=PILOT_CALL_TRACE, SWITCH_PLT=START, CN=10, SCTID=0,

CRRID=10;%%

RETCODE = 30322

--- END

II. Troubleshooting


The RFMT trace tasksalready exist.(1)

Stop radio resourcemonitoring.(4)

Test.(5)

Stop the RFMT tracetasks.(2)

END

N

Y

Radio resource monitoringhas started.(3)

N

Y

Figure 15-1 Troubleshooting flowchart of start failure of RFMT trace task

Steps:


15-2

1) The RFMT trace tasks already exist.

In the Service Maintenance System, execute the following command to check whether the trace task already exists:

DSP RFMT:;

Result: %%DSP RFMT:;%%


Query Result

------------

( Total result = 0 )

--- END

Note:

If the query result is not empty, the trace task type is “Specify IMSI call trace", and the task number reaches 10, it indicates that the RFMT trace task has been started. You cannot add new tasks.

2) Stop the RFMT trace task.

According to the query result in step 1, execute the following command in the Service Maintenance System to stop corresponding RFMT trace task:

SET RFMT: OPT=PILOT_CALL_TRACE, SWITCH_PLT=STOP;

Note:

You can execute the following command in the Service Maintenance System to stop all RFMT trace tasks: SET RFMT: OPT=CLOSE_ALL_RFMT_TRACE;

3) Radio resource monitoring has started.

If no RFMT trace task has been started, select the “Maintenance” tab in the Service Maintenance System. Then click “Review Radio Resource Monitoring” under the node “Review Radio Resource Monitoring” to check whether there is output information in the output window. If yes, the radio resource monitoring is started.

4) Stop radio resource monitoring.


15-3

If the radio resource monitoring is started, right-click the “Review Radio Resource Monitoring” under the node “Review Radio Resource Monitoring”, and then select [Stop] on the shortcut menu.

5) Test.

After stopping the original trace task, start the trace task needed.

SET RFMT: OPT=PILOT_CALL_TRACE, SWITCH_PLT=START, CN=10, SCTID=0,

CRRID=10;

If the returned result indicates that the RFMT task is started successfully, the troubleshooting succeeds.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 16 Switching Module Fault

16-1

Chapter 16 Switching Module Fault

Note:

Set the print option of the CMPU serial port to "connecting with the BAM" upon the startup of the CMPU. Then the alarms of the switching module will be reported to the BAM.

The alarms of the switching module is handled the same way as other alarms of the BSC. For details, see the on-line help of the alarm management system.

Caution:

The restart of the CMPU may result in the interruption of the system service. Please contact the Huawei engineers to make the setting related to the alarm information of the switching module.

The O&M commands of the switching module take effect upon execution. Be cautious in executing them. Please contact the Huawei engineers to do operations involving the O&M commands of the switching module.

16.1 Event Alarm for Active/Standby Port Switchover


The event alarm for active/standby port switchover is generated on the alarm management system.

II. Troubleshooting

If the active-standby port switchover of the CLPC is successful, the service will not be affected. However you should locate the switchover cause. If the switchover fails, the service will be interrupted.



16-2

Check connectors oroptical fibers for error.

(3)

Replace the CLPCboard

END

Y

Y

N

N

The error occur tothe peer CMUX. (1)

The error occur tothe local port. (2)

Figure 16-1 Troubleshooting procedure for event alarm for active/standby port switchover

Steps:

1) The error occurs to the peer CMUX.

If a major alarm exists on the active port but not on the standby port, the active-standby switchover must have occurred. If the peer CMUX is faulty and the optical interface does not work, the major alarm will be generated on the optical interface of CLPC.

You can use the command DSP FRMINFO to query the status of the peer CMUX of the original active port on which the switchover occurs.

For example, to query the status of the CMUX on the slot 7 of subrack 3, execute the following command:

DSP FRMINFO: FN=3;

If the status displayed in “disable”, it means this CMUX is faulty.

2) The error occurs to the local port.

Execute the command DSP SWBRDINFO to query the operational status of the CLPC where the original active port resides. %%DSP SWBRDINFO: SN=9;%%



16-3

Query Result

------------

Slot No. = 9

Board Type = CLPC

Board Status = Normal

Mother Board Type = LPUB

Type of Subboard 1 = ATM155

Type of Subboard 2 = None



( Records = 1 )

--- END

If the CLPC is working normally, execute the command DSP SWATMPORT to check whether any alarm occurs to original active port.

%%DSP SWATMPORT: SN=9, SSN=0, PN=0;%%


Query Result

------------

Slot No. = 9

Subslot No. = 0

Slot No. = 0

Port Status = UP

Port Signaling Status = DOWN

Interface Rate(Mbps) = 155

Maximum Number of VPCs = 241

Maximum Number of VCCs = 4096

Number of VPCs Configured = 3

Number of VCCs Configured = 2

VC Sub-space = 1024

Type of UPC and VPC = NPC


16-4

Loopback or Not = FALSE

Maximum Input Bandwidth(MB) = 149760

Maximum Output Bandwidth(MB) = 149760

Currently-Available Input Bandwidth(MB) = 149760

Currently-Available Output Bandwidth(MB) = 149760

Port Alarm Status = FALSE //If there is any

alarm, it means that optical fiber of the CMUX is inserted reversely or broken.

( Records = 1 )

--- END

3) Check connectors or optical fibers for error.

If the connector is not firmly connected, or the optical fiber is damaged, handle the problems as follows:

Check whether the connector is firmly connected. If not, secure the connection and see whether the alarm is cleared.

If the optical fiber is damaged, replace the optical fiber and then see whether the CLPC optical interface alarm is cleared.

16.2 Optical Interface Out of Frame Alarm


The optical interface out of frame (OOF) alarm is generated.

II. Troubleshooting

The OOF fault will affect the service and the communication quality. Figure 16-2 shows the troubleshooting procedure.


16-5

The error occur to the connector or the optical

fiber. (1)

The CLPC is faulty. (3)

Handle the problemsconcerning connectors or

optical fibers (2)

END

Replace the board

Y

Y

N

N

Figure 16-2 Troubleshooting procedure for the optical interface OOF alarm

Steps:

1) The error occurs to the connector or the optical fiber.

Observe whether the following two cases exist:

The connector is not firmly connected. Or the connector has been loosed for a moment.

The optical fiber is damaged.

2) Handle the problems concerning connectors or the optical fibers.

Check whether the connector is firmly connected. If not, secure the connection and see whether the alarm is cleared.

If the optical fiber is damaged, replace the optical fiber and then see whether the CLPC optical interface alarm is cleared.

3) The CLPC is faulty.



Query Result

------------

Slot No. = 9

Board Type = CLPC



16-6






( Records = 1 )

--- END

If the CLPC is working normally, execute the command DSP SWATMPORT to check whether any alarm occurs to original active port.

If you detect any major alarm, or the system prompts no active port exists, then the sub-board where the port is located may be faulty. In this case, you should replace the sub-board.

%%DSP SWATMPORT: SN=9, SSN=0, PN=0;%%


Query Result

------------

Slot No. = 9

Subslot No. = 0

Slot No. = 0

Port Status = UP // The "up" state means the port is working normally.

Port Signaling Status = DOWN

Interface Rate(Mbps) = 155

Maximum Number of VPCs = 241

Maximum Number of VCCs = 4096

Number of VPCs Configured = 3

Number of VCCs Configured = 2

VC Sub-space = 1024

Type of UPC and VPC = NPC

Loopback or Not = FALSE

Maximum Input Bandwidth(MB) = 149760


16-7

Maximum Output Bandwidth(MB) = 149760

Currently-Available Input Bandwidth(MB) = 149760

Currently-Available Output Bandwidth(MB) = 149760

Port Alarm Status = FALSE

( Records = 1 )

--- END

16.3 Optical Interface Loss of Frame Alarm


The optical interface loss of frame (LOF) alarm is generated.

II. Troubleshooting

The LOF fault will affect the service and the communication quality. The LOF alarm is usually generated together with the OOF alarm. Their troubleshooting procedures are identical.

For the troubleshooting procedures, see the description in section 16.2 Optical Interface Out of Frame Alarm.

16.4 Optical Interface Loss of Signal Alarm


The optical interface loss of signal (LOS) alarm is generated.

II. Troubleshooting

The LOS fault will lead to the interruption of service. The LOS alarm is usually generated together with the OOF and LOF alarms. Their troubleshooting procedures are identical.

For the troubleshooting procedures, see the description in section 16.2 Optical Interface Out of Frame Alarm.


16-8

16.5 Event Alarm of CLPC Loss of System Clock


Event alarm of CLPC loss of system clock is generated.

II. Troubleshooting


The CLPC is faulty. (1)

The CLKC is faulty.(2)

Switch over the CLKC(3)

Replace the CLPC

END

N

Y

Y

N

Figure 16-3 Troubleshooting procedure for event alarm of CLPC loss of system clock

Steps:

1) The CLPC is faulty.



Query Result

------------

Slot No. = 9

Board Type = CLPC




16-9





( Records = 1 )

--- END

2) The CLKC is faulty.

The CLPC line clock is generated through the phase lock of the signal of the local oscillator and CNET clock signal. The event alarm of CLPC loss of system clock is generated possibly because something is wrong with the clock signal sent by CNET.

If this event alarm only occurs to a certain CLPC, this CLPC may be faulty. If this alarm occurs to all the CLPCs, the CLKC may be faulty.

Execute the command DSP SWBRDINFO to query the operational status of the CNET.

%%DSP SWBRDINFO: SN=0;%%


Query Result

------------

Slot No. = 0

Board Type = CMPU


Mother Board Type = MPUB





( Records = 1 )

--- END


16-10

If the CNET is working normally, execute the command DSP SWCLKSTAT to check whether any clock is available to send to the CLPC.

%%DSP SWCLKSTAT:;%%


Query Result

------------

Current Clock Source Priority = 4

Clock Source Selection Method = 1

Slot No. of Active Clock Board = 7 //It means active

clock board is working normally. If "Slot No. of Actvie Clock Board" is "-", it

means the board is working abnormally.

Working Mode of Clock Board = CLOCK_MODE_3G

Status of Current Phase-Locked Loop = CLK_TRACE

Slot No. = -

Subslot No. = -

Port No. = -

Reference Source Index = 0

Reference Source Type = SELF

Availability of Clock Source = UNKNOWN



Slot No. of Active Clock Board = 7



Slot No. = -

Subslot No. = -

Port No. = -


Reference Source Type = GPS1

Availability of Clock Source = USABLE



16-11





Slot No. = -

Subslot No. = -

Port No. = -


Reference Source Type = bits1-2mhz


( Records = 3 )

--- END

When the output clock of the master CLKC is abnormal, auto switchover occurs to the CLKC. In this case, you should reset the faulty CLKC. (After the auto switchover, the faulty CLKC becomes the slave CLKC.)This reset operation does not affect the service.

3) Switch over the CLKC.

Execute the command SWP SWCLKBRD to switch over the CLKCs.

SWP SWCLKBRD: SN=8;

Caution:

The execution of the command SWP SWCLKBRD may result in the interruption of service. Be cautious when using this command.

16.6 Clock Switchover Event Alarm


The clock switchover event alarm is generated.


16-12

II. Troubleshooting


The CLKC is faulty.(1)

The clock signal of the localoscillator is lost. (2)

Replace the CLKC.

END

N

Y

Y

N

Figure 16-4 Troubleshooting procedure for clock switchover event alarm

Steps:

1) The CLKC is faulty.

Execute the command DSP SWBRDINFO to check the operational status of the original CLKC.



Query Result

------------

Slot No. = 9

Board Type = CLPC








16-13

( Records = 1 )

--- END

2) The clock signal of the local oscillator is lost.

Execute the command DSP SWCLKSTAT.

%%DSP SWCLKSTAT:;%%


Query Result

------------



Slot No. of Active Clock Board = 7 //It means active

clock board is working normally. If "Slot No. of Actvie Clock Board" is "-", it

means the board is working abnormally.



Slot No. = -

Subslot No. = -

Port No. = -









Slot No. = -

Subslot No. = -

Port No. = -


16-14


Reference Source Type = GPS1







Slot No. = -

Subslot No. = -

Port No. = -


Reference Source Type = bits1-2mhz


( Records = 3 )

--- END

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 17 Link and Circuit Fault

17-1

Chapter 17 Link and Circuit Fault

17.1 Abis Interface Link Fault

17.1.1 E1/T1 Signal Loss


E1/T1 signal loss alarm of certain link is generated in the alarm management system.

If the link is configured as UNI mode, the service borne in this link will be interrupted.

If the link is configured as inverse multiplexing on ATM (IMA) mode, the service capacity borne in IMA group will decrease in the case that IMA group still has other normal links (one or more links constitute an IMA group).

II. Troubleshooting



17-2

Cancel loopback (2)

Handle connection components and cable(5)

END

Replace board or configure BTS to other idlelinks (3)

Handle problem between DDF and opticaltransmision equipment (6)

N

Y

Y

NDoes the error occur from DDF

to BSC? (4)

Is CXIE interface chip normal? (1)

Are the TX and RX cables properlyconnected?

Connect the cables properlyN

Y

Figure 17-1 Troubleshooting flowchart for E1/T1 signal loss alarm

Note:

The segment-by-segment loopback mode is usually used to locate E1/T1 fault. Judge whether a segment is normal through the loopback of each segment. If the alarm is cleared after loopback, this segment is normal. If the alarm still exists, the fault must result from this segment.

Steps:

1) Set the link as local loopback to judge whether the problem results from this CXIE interface chip.

a) Check the E1/T1 link status using DSP E1T1STAT.

For example, to query the E1/T1 link status of the board in slot 0 of subrack 3, execute:

DSP E1T1STAT: FN=3, SN=SLOT0, BTP=CXIE, LNKNO=4;

b) Set the loopback of the E1/T1 link.


17-3

Execute the command SET LPBACKE1T1 to set the loopback of the E1/T1 link. For example:

SET LPBACKE1T1: FN=3, SN=SLOT0, BTP=CXIE, LNKNO=4, OPT=INWARDLOOP;

After SET LPBACKE1T1 is executed, E1/T1 interface chip of Abis interface CXIE will be in internal loopback status. If E1/T1 signal loss alarm is cleared, internal CXIE interface chip is normal. You should further locate the fault.

2) Cancel loopback

Execute the command SET LPBACKE1T1 to cancel the loopback. For example:

SET LPBACKE1T1: FN=3, SN=SLOT0, BTP=CXIE, LNKNO=4, OPT=NOLOOPBACK;

3) Replace the board, or configure BTS onto other idle link

If any error occurs to the chip of the CXIE, replace the board or configure the BTS to other idle links.

As the CXIE board is connected to multiple BTSs, and resetting of it will lead to disconnection between BTSs. Hence, the replacement should be performed when the traffic is small.

If the CXIE board cannot be replaced within a certain period, configure the BTS to which the faulty link is connected to other idle E1/T1 interface of the CXIE. However, the data of this BTS should be re-configured.

a) Execute LST BTSLNK to display the current BTS configuration. For example:

LST BTSLNK: FN=3, SN=SN0, BTSID=2;

b) If the E1 port of the CXIE has an idle E1, you can directly add the idle E1, and then delete the unavailable E1.

To add idle E1, execute: ADD IMALNK: FN=3, SN=SN0, IMAGN=2, E1LST="6,7";

To delete unavailable E1, execute: RMV IMALNK: FN=3, SN=SN0, IMAGN=2, E1LST="4,5";

Caution:

Before a BTS is deleted, you should first delete the radio resource configuration of the BTS. Make sure to delete the BTS when it bears no service.


17-4

Delete the current BTS configuration using the following commands: RMV CDMACH: CN=12, SCTID=0, CRRIDLST="0,1";

RMV CDMACH: CN=12, SCTID=1, CRRIDLST="0,1";

RMV CELL: CN=12, SCTIDLST="0,1";

RMV BSCBTSINF: BTSID=2;

Note:

You may delete the whole BTS directly or delete the links of this BTS for convenient operation. The links of BTS are related to E1. To avoid data inconsistency, it is recommended to delete the whole BTS using this command.

Add the new BTS configuration information using the following commands: ADD IMAGRP: FN=3, SN=SN0, BTP=CXIE, XIEIMAGN=9, XIEE1LST="22,23",

XIEOIETXCLKMD=CTC, TXFRMLEN=L128;

ADD BSCBTSINF: BTSTP=IBSC, MN=0, IBTSID=2, OMIP="129.8.10.3",

SIGIP="129.11.17.118";

ADD BTSOMLNK: BTSID=2, FN=3, SN=SN0, LM=IMA, IMAGN=9, BTPFLG="2-45",

OMLNKFLG="1-255";

ADD BTSSIGLNK: BTSID=2, FN=3, SN=SN0, LM=IMA, IMAGN=9, SIGLNKFLG="1-254";

ADD BTSTRFLNK: BTSID=2, FN=3, SN=SN0, LM=IMA, IMAGN=9,

TRFLNKLST="1-250-1", LNKBW=BW1.6M;

4) Check whether the problem lies in the connection between BSC and DDF

In DDF, perform short-circuit on E1/T1 RX/TX line from BSC. Observe whether E1/T1 signal loss alarm disappears on the alarm management system:

If the alarm disappears, the connection between BSC and DDF is normal; If the alarm still exists, the connection between BSC and DDF is abnormal.

E1/T1 signal loss alarm means that the receiving part of BSC is faulty, so troubleshooting should focus on this part.

5) Check connection components and cables

The fault may result from the following two causes:

The problem of connection components, for example, the connector is not firmly inserted, or the dry-solder-joint exists in the connector.

The problem of cable, for example, the cable is broken.


17-5

For the former case, observe whether the connection components are loose, and insert the connection components firmly. Then check whether E1/T1 signal loss alarm is cleared.

For the latter case, detect it directly with multimeter, or observe whether the cable is damaged. Generally, the possibility of cable damage is little.

You can replace Abis interface cable to solve the above two problems.

6) Clear the problem of connection between DDF and optical transmission equipment

You may refer to step 4 and step 5 to solve the problem of connection between DDF and optical transmission equipment.

For the problem of optical transmission equipment, contact maintenance engineers for help.

If BSC is directly connected to BTS without optical transmission equipment, perform troubleshooting according to step 4 and step 5 through segment-by-segment loopback.

17.1.2 E1/T1 Frame Out-of-sync


E1/T1 frame out-of-sync alarm is generated in the alarm management system.

If the link is configured as UNI mode, the service borne in the link will be interrupted.

If the link is configured as IMA mode, the service capacity borne in IMA group will decrease in the case that IMA group still has other normal links (one or more links constitute an IMA group).

II. Troubleshooting



17-6

Is the length of transmisisonline appropriate? (1) Adjusst its length

Is the transmission line normal?(2)

Solv e transmission problem

Is the local board faulty ? (3)

Is the peer board faulty ? (4)See E1/T1 Signal Loss

Alarm

N

Y

N

Y

N

Y

N

Y

END

Figure 17-2 Troubleshooting flowchart for E1/T1 frame out-of-sync

Note:

E1/T1 frame out-of-sync alarm means the receive end of the BSC cannot locate the initial position of frame.

E1/T1 fault can be located through segment-by-segment loopback: if the alarm is cleared after loopback, this segment is normal; if the alarm still exists after loopback, the fault results from this segment.

Steps:

1) Check whether the length of transmission line is appropriate

a) Check whether the length of the E1/T1 cable between the local end and trunk (or peer end) is more than 500 m.

b) Check whether the length of the single-mode optical fiber between the local end and trunk (or peer end) is more than 8 km.

c) If the transmission line is too long, adjust the trunk.


17-7

2) Check whether the transmission line is normal

Check whether the grounding of E1/T1 cable is normal, and whether the shielding layer of cable is damaged.

Use BER tester if possible. If the BER is more than 10-3, the frame out-of-sync will occur. In this case, you should contact the transmission engineer.

3) Local board fault

Link signal loss means no signal can be received; frame out-of-sync means the signal is received but the serial number of frame header cannot be identified.

The location of E1/T1 signal loss alarm is still applicable to the location of frame out-of-sync alarm, namely, location with segment-by-segment method. For details, see section 17.1.1 E1/T1 Signal Loss.

4) Clear peer board fault

See section 17.1.1 E1/T1 Signal Loss for details.

17.1.3 E1/T1 Remote Alarm


E1/T1 remote alarm of certain link is generated in the alarm management system.

If the link is configured as UNI mode, the service borne in the link will be interrupted.

If the link is configured as IMA mode, the service capacity borne in IMA group will decrease in the case that IMA group still has other normal links (one or more links constitute an IMA group).

II. Troubleshooting

The troubleshooting method is identical with that in section 17.1.2 E1/T1 Frame Out-of-sync. Emphasis is laid on checking E1/T1 transmission link (the cable is marked with TX).


17-8

Note:

E1/T1 remote alarm means the peer end equipment connected to BSC is in frame out-of-sync status or signal loss status.

If the reception of the local end is normal, this alarm will be reported. That is, BSC receive line should be normal, and the problem lies in BSC transmission line. The alarm can also be located with segment-by-segment loopback.

17.1.4 E1/T1 Alarm Indication Signal


Alarm indication signal (AIS) of certain link is generated in the alarm management system.

If the link is configured as UNI mode, the service borne in the link is interrupted. If the link is configured as IMA mode, the service capacity borne in IMA group will

decrease in the case that IMA group still has other normal links (one or more links constitute an IMA group).

II. Troubleshooting


Is the peer equipment in localloopback (1)?

Cancel local loopback (2)

Y

END

Is the upper-lev eltransmission equipmnet in

LOS/LFA alarm? (3)

Solv e transmission equipmnetproblem

Y

N N

Figure 17-3 Troubleshooting flowchart for E1/T1 AIS

Note:

AIS means the peer end equipment is unavailable. You should check the working state of peer equipment.


17-9

Steps:

1) Check whether the peer equipment is in local loopback status

Execute DSP E1T1STAT to query BTS E1/T1 status. For example:


2) Cancel local loopback

If the peer equipment is in local loopback status, execute SET LPBACKE1T1 to cancel the loopback. For example:


3) Check whether the LOS/LFA alarm occurs to upper-level transmission equipment.

For example, if BSC is connected to BTS through optical transmission equipment, and the transmission line from BTS to optical transmission equipment is broken, BSC will receive an alarm indication signal. For this problem, contact the transmission engineer.

17.1.5 E1/T1 CRC4 Multiframe Out-of-sync


E1/T1 CRC4 multiframe out-of-sync alarm (E1/T1 CRC4 LMFA alarm) of certain link is generated in the alarm management system.

II. Troubleshooting

See the Figure 17-4 for troubleshooting procedure.


17-10

Configure them to beidentical (2)

Is BER relativ elylarger?

Check E1/T1 cable andsolv e transmission

problem

END

Is local and remoteframe format identical?

(1)

Y

N

Y

N

Figure 17-4 Troubleshooting flowchart for E1/T1 CRC4 multiframe out-of-sync alarm

Note:

The cause of E1/T1 CRC4 multiframe out-of-sync is that link receive end fails to locate the initial position of multiframe, and this fault can be detected from receive end. The transmission link from BTS to BSC is faulty.

Steps:

1) Check whether the local frame format is identical with remote one in E1 mode.

If they are not identical (for example, local equipment is configured with multiframe CRC4, but the peer equipment is not), check the setting of E1 mode.

a) Execute LST E1T1 to query BSC link mode. For example:

LST E1T1: FN=3, SN=SN0;

b) Execute DSP E1T1STAT to query E1/T1 link status. For example:


2) Configure local frame format to be identical with remote frame format

Execute MOD E1T1 to set BSC link frame format. For example:

MOD E1T1: FN=3, SN=SN0, BTP=CXIE, XIELNKTP=CRCE1;

(Assume the remote equipment is configured as E1 with CRC, set the local equipment to be identical with the remote one).


17-11

3) Check the BER

If BER obtained by using BER tester is larger than 10-6, Check whether the grounding of E1/T1 cable is normal, and whether the shielding layer of cable is damaged.

17.1.6 E1/T1 Link Loopback


E1/T1 link loopback alarm of certain link is generated in the alarm management system.

II. Troubleshooting

See the Figure 17-5 for troubleshooting procedure:

Query E1/T1 link status (1)

Set the link as "NoLoopback mode" (2)

Y

N

END

Is the link in loopbackstatus?

Figure 17-5 Troubleshooting for E1/T1 link loopback alarm

Note:

E1/T1 link loopback is an alarm indicating that current link is set as loopback. This alarm can be cleared when the loopback of the link is cancelled.

Steps:


17-12

1) Query E1/T1 link status

Execute DSP E1T1STAT to query E1/T1 link status. For example:


This alarm is generated when the link is in any one of the following statuses: local loopback, remote loopback, load loopback or single channel loopback.

2) Set the link as "No Loopback mode"

Check whether E1/T1 link is in loopback status. If so, this alarm needs not to be handled; if not, this link should be set as "No Loopback mode".

Execute the command SET LPBACKE1T1 to set E1/T1 to be in no loopback mode. For example:


17.1.7 E1/T1 1-hour Slip Frame Threshold Crossed


E1/T1 1-hour slip frame threshold crossed alarm of certain link is generated in the alarm management system, and the trunk service allocated to this E1/T1 is affected.

For the speech service, the conversation quality may decrease. For the data service, the package may be lost, or the data cannot be transmitted

when BER is high.

II. Troubleshooting

See Figure 17-6 for troubleshooting procedure.


17-13

Query BTS configurationinfo (1)

Configure IMA group/UNIlink (2)

Query BTS clockconfiguration (3)

Configure BTS clock asBSC slav e clock (5)

N

Y

N

Y

N

Y

END

Is BTS reset in 1-hour?

Is BTS clock BSCslav e clock? (4)

Is IMA group/UNIlink configured?

Figure 17-6 Troubleshooting for E1/T1 1-hour slip frame threshold crossed

Note:

Slip frame alarm is usually caused by clock out-of-synchronization of BTS and BSC.

Steps:

1) Query BTS configuration information

For Abis interface, BTS should lock BSC clock. Check whether BTS is configured with IMA group or UNI link. If not, the clock between BSC and BTS is out of synchronization, and the slip frame alarm will be generated.

Execute the command LST BTSLNK to query link configuration information. For example:


2) Configure IMA group/UNI link

a) Execute the following commands to configure IMA link:


17-14

ADD BTSLNKGRP: BTSID=1, BRDID=0, LNKGRPID=0, LNKGRPTP=IMA;

ADD BTSLNK: BTSID=1, BRDID=0, LNKID=0, LNKGRPID=0;


b) Execute the following commands to configure UNI link.

ADD BTSLNKGRP: BTSID=1, BRDID=0, LNKGRPID=1, LNKGRPTP=UNI;


3) Check whether BTS is reset within 1 hour

The slip frame is generated when BTS is powered on and IMA/UNI link is not configured. So if BTS is reset within one hour, this alarm needs not to be handled.

4) Query BTS clock configuration

Check whether BTS clock is configured as BSC slave clock. You may execute the command DSP BTSCFG to query BTS clock configuration. For example:

DSP BTSCFG: BTSID=1, CFGID=BTSE1CLKM;

5) Configure BTS clock as BSC slave clock

Set BTS clock as BSC slave clock using the command SET BTSLNKCLKM. For example:

SET BTSLNKCLKM: BTSID=2, BRDID=0, LNKID=3, CLKM=SLAVE;

17.1.8 E1/T1 Link BER Threshold Crossed


E1/T1 link BER threshold crossed alarm of certain link is generated in the alarm management system, and the trunk service allocated to this E1/T1 is affected.

For the speech service, the conversation quality may decrease. For the data service, the package may be lost, or the data cannot be transmitted

when BER is high.


17-15

II. Troubleshooting

The troubleshooting of the alarm is as follows:

1) Check whether the grounding of E1/T1 cable is normal, and whether the shielding layer of cable is damaged.

2) Use BER tester if possible. If BER is more than 10-6 and E1/T1 cable is normal, the transmission line quality may be poor. Contact the transmission engineer for help.

Note:

If 1-hour framing error or 1-hour CRC error statistic exceeds alarm threshold, the E1/T1 link BER threshold crossed alarm will be generated, indicating that E1/T1 line BER exceeds 10-6.

If E1/T1 signal loss, E1/T1 frame out-of-sync, E1/T1 alarm indication, or E1 multiframe out-of-sync alarms occurs within one hour, the system will not report E1/T1 link BER threshold crossed alarm.

17.1.9 IMA Link Out of Frame


IMA link out of frame alarm is generated in the alarm management system, and this IMA link will not be used for service bearing.

If the link is configured as IMA mode, the service capacity born in IMA group will decrease in the case that IMA group still has other normal links (one or more links constitute an IMA group). Otherwise, the service borne in this group will be interrupted.

II. Troubleshooting



17-16

Does IMA link haveE1/T1 fault? (1)

Is the data in BSC and its interconnected BTS

consistent? (2)

Is the connectionincorrect? (3)

Clear E1/T1 link fault

Configure them to beconsistent

Correctly connect thelink

END

Y

Y

N

N

Y

N

Figure 17-7 Troubleshooting flowchart for IMA link out of frame

Note:

IMA link fault is usually caused by E1/T1 link fault. So you should first check E1/T1 link status, and then the link according to IMA characteristics.

Steps:

1) Query E1/T1 link status

Execute the command DSP E1T1STAT to query E1/T1 link status. For example:


For the troubleshooting of E1/T1 link alarm, see sections 17.1.1 E1/T1 Signal Loss and 17.1.8 E1/T1 Link BER Threshold Crossed.

2) Check whether the data in BTS and BSC are consistent

a) Execute scramble query command DSP LNKSCRCOD. For example:

DSP LNKSCRCOD: FN=3, SN=SLOT0, BTP=CXIE, LNKNO=4;

b) If "Scramble option" of BTS and BSC is configured as "OMA_TC_ENABLE" or as "OMA_TC_DISABLE", it is normal. Otherwise, set the data in BTS to be consistent with that in BSC.


17-17

Execute the command SET LNKTC to set IMA scramble. For example:

SET LNKTC: FN=3, SN=SLOT0, BTP=CXIE, LNKNO=4, OPT=IMA_TC_DISABLE;

(If BTS is set as OMA_TC_DISABLE, BSC should be set to be identical with it).

c) If the configuration of scramble is normal, you should check whether the link interconnected to the peer end is configured as IMA link.

Execute the command to query the link. For example:


d) If the peer link is not configured as IMA link, you can perform IMA link configuration using the following commands:




3) Check whether the link is wrongly connected

a) Check whether the link of a local IMA group is respectively connected to the links in two IMA groups.

b) Check whether the receive end of the link is in cross-connection mode;

c) Check whether the link is connected to different BTSs. For example, the initial link is looped back and activated, and then connected to another BTS; or the link is connected from one BTS to another. If the connection is correct, execute the command RST IMAGRP to recover IMA group. For example:

RST IMAGRP: FN=3, SN=SLOT0, IMAGN=2;

17.1.10 Inter-link IMA Out of Synchronization


Inter-link IMA out of synchronization alarm is generated in the alarm management system, and this link cannot be used for service bearing. If the link is configured as IMA mode, the service capacity borne in IMA group will decrease in the case that IMA group still has other normal links (one or more links constitute an IMA group). Otherwise, the service borne in IMA group will be interrupted.


17-18

II. Troubleshooting


View operation log (1)

View max inter-link delaydifference in IMA group?

(2)

Is the alarm cleared?

Link adjustment (3)

N

Y

N

Y

Y

N

END

Does the link undergo different

trunks?

Is the alarm clearedin 10 seconds?

Figure 17-8 Troubleshooting flowchart for inter-link IMA out of synchronization

Steps:

1) View operation log.

View the operation log at the BAM. If this link is newly added, or once disconnected but now recovered, this symptom is normal.

2) Check IMA group maximum inter-link delay difference.

If the alarm is not cleared in ten seconds, query the configuration of this IMA group.

Then check the IMA group maximum inter-link delay difference. Contact Huawei engineer to confirm the value.


17-19

Execute the command LST IMAGRP to query the configuration of IMA group. For example:

LST IMAGRP: FN=3, SN=SN0, IMAGN=9;

Note:

The delay is required for data transmission on Abis interface. So the inter-link delay difference should not be too large. Otherwise, the service cannot be correctly transmitted even if IMA group is in normal status.

The maximum inter-link delay difference should not be too small, for example, less than 5ms. If the value is too small, some of the links cannot be added to IMA group, that is, this link cannot bear the service.

3) Adjust links

If the delay tolerance still fails after adjustment, the transmission engineer should detect whether this link passes through different trunks when it is compared with other links.

If so, adjust the trunk cable to make the link in IMA group pass through the same trunk.

If not, guarantee the inter-link delay difference to be in the specified range. If the inter-link delay difference cannot be in the specified range, delete this link.

17.1.11 IMA Link Remote Receiving Defect


IMA link remote receiving defect alarm is generated in the alarm management system, and this link cannot be used for service bearing. If the link is configured as IMA mode, the service capacity borne in IMA group will decrease in the case that IMA group still has other normal links (one or more links constitute an IMA group). Otherwise, the service borne in IMA group will be interrupted.

II. Troubleshooting

Steps:

1) Query E1/T1 link status corresponding to this alarm.


17-20

Execute the command DSP E1T1STAT to query E1/T1 link status corresponding to this alarm. For example:


Observe whether E1/T1 remote alarm is generated. If so, see section 17.1.3 E1/T1 Remote Alarm for troubleshooting method.

2) Query the ineffective status of peer IMA link.

Execute the command DSP IMALNKSTAT to query the ineffective status of peer IMA link. For example:

DSP IMALNKSTAT: FN=3, SN=SLOT0, LNKNO=4;

Check whether IMA/UNI link cell delimitation loss, IMA link out of frame, and inter-link IMA out of synchronization alarms occur to peer IMA link. If so, see sections 17.1.13 IMA/UNI Link Cell Delimitation Loss, 17.1.9 IMA Link Out of Frame, and 17.1.10 Inter-link IMA Out of Synchronization respectively for the troubleshooting methods.

17.1.12 Receiving End of IMA Link Failed


Receiving end of IMA link failed alarm is generated in the alarm management system, and this link cannot be used for service bearing. If the link is configured as IMA mode, the service capacity borne in IMA group will decrease in the case that IMA group still has other normal links (one or more links constitute an IMA group). Otherwise, the service borne in IMA group will be interrupted.

II. Troubleshooting

This alarm is usually caused by incorrect connection. So check the link connection first.

See step 3 in section 17.1.9 IMA Link Out of Frame for details.

17.1.13 IMA/UNI Link Cell Delimitation Loss


An IMA/UNI link cell delimitation loss (IMA/UNI link LOCD) alarm is generated in the alarm management system, and this link cannot be used to carry the traffic.


17-21

If the link is configured as the UNI mode, the traffic carried by this link will be interrupted.

If the link is configured as IMA mode, the traffic carried by the IMA group will decrease in the case that IMA group still has other normal links (one or more links constitute an IMA group). Otherwise, the service borne in IMA group will be interrupted.

II. Troubleshooting

Note:

The cause of IMA/UNI link cell delimitation loss alarm is that the cell cannot be received. So you should check whether the interruption exists in each part of the transmission.

Steps:

1) Query E1/T1 link status.

Execute the command DSP E1T1STAT query E1/T1 link status. For example:


If the link status is of signal loss or frame out-of-sync, see section 17.1.1 E1/T1 Signal Loss or 17.1.2 E1/T1 Frame Out-of-sync for troubleshooting methods.

2) Query the configuration of peer link.

Execute the command LST BTSLNK to query the configuration of peer link. For example:


If the peer link is not configured as IMA/UNI one, this link should be configured to be identical with the type of BSC link.

3) Configure IMA link.

Execute the following commands to configure IMA link.





17-22

4) Configure UNI link.

Execute the following commands to configure UNI link.

ADD BTSLNKGRP: BTSID=1, BRDID=0, LNKGRPID=1, LNKGRPTP=UNI;


17.1.14 Insufficient Active Links in IMA Group


Insufficient active links in IMA group alarm is generated in the alarm management system, and this IMA group cannot bear the service.

II. Troubleshooting


Y

N

Query IMA link configured inIMA group (1)

Query state of IMA linkconfigured in IMA group (2)

See sections 10.1.9, 10.1.10,and 10.1.13 for troublshooting

Does peer IMA linkhav e alarm (3)?

END

Figure 17-9 Troubleshooting flowchart for insufficient active links in IMA group

Note:

Insufficient active links in IMA group result from the link failure, causing the number of links activated in the group is less than the minimum (which is configured when IMA group is added).


17-23

Steps:

1) Query IMA link configured in IMA group

Execute LST IMAGRP to query IMA link configured in IMA group. For example:

LST IMAGRP: FN=3, SN=SN0, IMAGN=9;

2) Query IMA link status in IMA group

Execute DSP IMALNKSTAT to query IMA link status in IMA group. For example:

DSP IMALNKSTAT: FN=3, SN=SLOT0, LNKNO=5;

3) Check whether the alarm exists in peer IMA link

Check whether the IMA link cell delimitation loss, IMA link out of frame, and inter-link IMA out of synchronization alarms occur to the peer IMA link. If so, see sections 17.1.13 IMA/UNI Link Cell Delimitation Loss, 17.1.9 IMA Link Out of Frame, and 17.1.10 Inter-link IMA Out of Synchronization respectively for troubleshooting methods.

17.2 A1 Interface Signaling Link Fault

17.2.1 E1/T1 Alarm

See sections 17.1.1 E1/T1 Signal Loss and 17.1.8 E1/T1 Link BER Threshold Crossed for troubleshooting method.

17.2.2 MTP Link Failure


Symptom 1

When "TransferService" is "No" and "LinkActivated" "Yes", the link of MTP2 is faulty. If the link of MTP2 is faulty, so is the link of MTP3. That is, if "LinkActivated" is "Yes", "TransferService" is generally "No". You should locate the specific MTP link fault.

Symptom 2


17-24

When "TransferService" is "No" and "LinkFault" "No", the link status of MTP2 is normal, but that of MTP3 is abnormal. You should locate the specific MTP link fault.

You may execute the command DSP N7LNK to query MTP link status.

Example DSP N7LNK: OPT=OPC, OPC="0x00D00A";

Result %%DSP N7LNK: OPT=OPC, OPC="0x00D00A";%%


Query Result

------------

ModuleNo. LinkNo. TransferService LinkActivated LinkBlocked

LinkFault

0 0 Yes Yes No No

LocalManagementInhibit RemoteManagementInhibit LinkCongested

Switchover Switchback

No No No No No

SLS

000102030405060708090A0B0C0D0E0F

(Records = 1)

--- END

The troubleshooting is based on two statuses of "TransferService" and "LinkActivated". The former represents the link status of MTP3; while the latter the link status of MTP2.

Note:

SS7 link faults can be located through querying SS7 alarm information: query SS7 alarm in maintenance console; execute LST ALMINF to acquire the detailed information to locate the problem.

II. Troubleshooting

MTP2 link fault



17-25

Is CAIEcorresponding to the

link normal? (2)

Is E1 corresponding tothis link available?

(3)

Is E1 connection identicalwith the requirement?

(4)

Troubleshooting ofCAIE

Troubleshooting of E1

Adjust physicalconnection

END

Y

Y

N

N Is the transmissionquality normal? (5)

Troubleshooting oftransmission fault

Check the results (7)

MSC problem(6)

Is CLAPcorresponding to the

link normal? (1)Troubleshooting of

CLAP

Y

N

N

N

Y

Y

Figure 17-10 Troubleshooting flowchart for MTP2 link fault:

Steps:

1) Query the status of CLAP corresponding to the faulty link

Execute the command DSP FRMINFO to query the status of CLAP:

Example DSP FRMINFO: FN=5;

Result %%DSP FRMINFO: FN=5;%%



17-26

Query Result

------------

Slot No. Board Type ATMBusInterface OperationalStatus

AdministrativeStatus Active_StandbyStatus

0 CXIE 0 Available Enable Master

1 CFMR 1 Available Enable Master

2 CFMR - Unavailable Enable -


7 CMUX 7 Available Enable Master

8 CMUX - Unavailable Enable -

9 CEVC 9 Available Enable Master

10 CEVC - Unavailable Enable -

11 CLAP - Unavailable Enable -

12 CSPU 12 Available Enable Master

13 CSPU - Unavailable Enable -

14 CIWF - Unavailable - -

15 CAIE 15 Available Enable Master

(Records = 16)

--- END

If "OperationalStatus" of the CLAP is "Unavailable", you should first replace it.

2) Query whether the CAIE corresponding to the link is normal

Execute the command DSP FRMINFO to query the status of the CAIE.




Query Result

------------






17-27







11 CLAP 11 Available Enable Master




15 CAIE - Unavailable Enable -

If "OperationalStatus" of CAIE is "Unavailable", firstly replace it.

3) Query whether the status of E1 corresponding to the link is normal

Execute the command DSP E1T1STAT to query the status of E1.

Example DSP E1T1STAT: FN=5, SN=SLOT0, BTP=CAIE;

Result %%DSP E1T1STAT: FN=5, SN=SLOT0, BTP=CAIE;%%


Query Result

------------

Slot E1/T1No. E1/T1OperationalStatus

15 0 Available

15 1 Has_loss-of-signal_alarm





(Records = 6)

--- END

If "E1/T1OperationalStatus" corresponding to the link is "Has_loss-of-signal_alarm", you should firstly replace the faulty E1 line.


17-28

4) Check whether the physical connection is consistent with the requirements

Check whether E1 connection is consistent with data configuration, and whether the crossed pair exists. If their physical connections are not consistent, you should establish the physical connection again.

Note:

The normal connection of E1 line and the connection of crossed pair are shown as below:

A E1 Rx

A E1 Tx

B E1 Tx

B E1 Rx

C E1 Rx

C E1 Tx

D E1 Tx

D E1 Rx

A E1 Rx

A E1 Tx

B E1 Tx

B E1 Rx

C E1 Rx

C E1 Tx

D E1 Tx

D E1 Rx

Normal connection

Crossed pair

Figure 17-11 E1 line connection (normal connection/crossed pair)

5) Check the quality of transmission between BSC and MSC

Check whether the transmission quality is poor and whether the BER is too high by using BER tester. If BER is too high, you should first solve transmission quality problem.


17-29

6) Clear MSC fault.

Contact MSC engineer for help.

7) Check the results.

Execute the command DSP N7LNK to check MTP link fault status.




Query Result

------------

ModuleNo. LinkNo. TransferService LinkActivated LinkBlocked LinkFault

0 0 Yes Yes No No



No No No No No

SLS

000102030405060708090A0B0C0D0E0F

(Records = 1)

--- END

If "LinkFault" is "No", it indicates that MTP2 is normal.

MTP3 link fault

See Figure 17-12 for the troubleshooting procedure in the case that MTP1 link is normal while MTP 3 link is faulty.


17-30

MSC problem (3)

Adjust dataconfiguration

Adjust physicalconnection

Verify (4)

N

N

Y

Y

END

Is E1 connection w iththe requirement? (2)

Is data configuration is

identical w ith MSC?(1)

Figure 17-12 Troubleshooting flowchart for MTP3 link fault

Note:

The problem that "MTP2 link is normal while MTP3 link is faulty" is usually caused by the inconsistency between data configurations of both BTS and MSC. So you should first check whether the data configurations at BSC side and MSC side are consistent.

Steps:

1) Check whether the data configuration in BSC and MSC are identical

a) Check whether the destination point code (DPC) of BSC is consistent with that in MSC;

b) Check whether the DPC of BSC (14-bit or 24-bit) is consistent with that in MSC. The DPC of two interconnected signaling points should be consistent;

c) Check whether the signaling link codes (SLCs) at two ends of the faulty link are consistent. It is required that SLCs in the same link at BSC side and MSC side should be the same, while SLCs of the same signaling point and different links should be different.

For MSC fault, contact MSC maintenance engineer for help.


17-31

2) Check whether the physical connection is consistent with the requirements

Check whether E1 connection is consistent with data configuration, and whether the crossed pair exists. If their physical connections are inconsistent, you should establish the physical connection again according to data configuration.

3) Clear MSC fault

If the physical connection is correct, contact MSC maintenance engineer for help.

4) Verify

Execute the command DSP N7LNK to check MTP3 link fault status.




Query Result

------------

ModuleNo. LinkNo. TransferService LinkActivated LinkBlocked LinkFault

0 0 Yes Yes No No



No No No No No

SLS

000102030405060708090A0B0C0D0E0F

(Records = 1)

--- END

If "TransferService" is "Yes", this means that MTP3 is normal.

17.3 A2 Interface Circuit Fault


If you execute DSP A2 to query trunk circuit status, the normal result is as shown in the following figure:


17-32

Figure 17-13 Querying trunk circuit status (A2 interface circuit is normal)

"CICStatus" of synchronization and signaling link timeslots (they are usually timeslot 0 and timeslot 16 of E1) is "Unequipped". "CICStatus" of trunk circuit is normally "Idle". If "CICStatus" is "Fault", this indicates that A2 interface circuit is faulty, as shown in Figure 17-14.

Figure 17-14 Querying trunk circuit status (A2 interface circuit is faulty)


17-33

II. Troubleshooting

See Figure 17-15 for the troubleshooting procedure:

Is physical status ofeach board normal?

(2)

Is the connection of E1line in DDF correct? (3)

Is the state of E1normal? (4)

Replace the board

Re-connect E1 line

Replace E1 line

END

Y

Y

N

Is E1 interface boardat MSC side normal?

(1)MSC side problem

Y

N

N

N

Y

Check the results (5)

Figure 17-15 Troubleshooting flowchart for A2 interface circuit fault

Steps:

1) Check the E1 interface board at MSC side

You can ask MSC engineers to check whether the E1 interface board, which is located at the MSC side and connected to BSC, is normal.

Note:

A2 interface circuit is used for connection between BSC and MSC. When A2 interface circuit is faulty, you should first check whether the fault is caused by MSC side, namely. E1 interface board at MSC side is abnormal, or MSC status is abnormal (including MSC not power-on), and so on.


17-34

2) Check the physical status of each board

Execute DSP FRMINFO to query the status of each board. Observe whether AIE and RMU are normal. If the board is faulty (the corresponding "OperationalStatus" is "Unavailable"), replace it first.




Query Result

------------











11 CLAP 11 Available Enable Master




15 CAIE 15 Unavailable Enable Master

(Records = 13)

--- END

3) Check E1 connection in distribution frame

Ask MSC maintenance engineer to check E1 connection in distribution frame, and check whether the cable is wrongly connected at two sides.

You can use the auxiliary means: performing self-loop to E1 in distribution frame, and then querying the corresponding E1 physical status using DSP E1T1STAT.


17-35

Note:

Since there are many E1s between BSC and MSC, E1 may be wrongly connected in distribution frame. If an E1 is not connected according to the data script, A2 circuit will be faulty, and only one party during conversation can hear the voice in the speech service.

4) Check E1 status

Execute DSP E1T1STAT to query E1 status. If fault still exists, the problem may be resulted from E1 line. Replace the corresponding E1 line.

5) Check the results.

Execute the command DSP A2 to check the result.

Example DSP A2: OPC="0x00d004", NI=NATC, SCIC=0, ECIC=64;

Result %%DSP A2: OPC="0x00d004", NI=NATC, SCIC=0, ECIC=64;%%


Query Result

------------

CICNo. CICStatus OccupiedStatus

0 Unequipped Unequipped

1 Idle Idle

2 Idle Idle

3 Idle Idle

4 Idle Idle

5 Idle Idle

6 Idle Idle

7 Idle Idle

8 Idle Idle

9 Idle Idle

10 Idle Idle

11 Idle Idle

12 Idle Idle

13 Idle Idle

14 Idle Idle

15 Idle Idle


17-36

16 Unequipped Unequipped

17 Idle Idle

18 Idle Idle

19 Idle Idle

20 Idle Idle

(Records = 21)

--- END

Other than the unequipped synchronization and signaling timeslot, both "CICStatus" and "OccupiedStatus" of other timeslots are "Idle", and this indicates that the fault has been cleared.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 18 BTS Management Fault

18-1

Chapter 18 BTS Management Fault

18.1 BAM Failed to Ping or Log on to BTS through Telnet


Symptom 1

It is failed to ping the O&M IP address of the BTS from BAM, though the BCKM at BTS and the CBIE at BSC are normal.

Symptom 2

It is failed to log on to the BTS from BAM through Telnet, though the BCKM at BTS and the CBIE at BSC are normal.

II. Troubleshooting



18-2

Query E1 links configuredto BTS. (1)

Y

END

Test.(14)

Query the IP routeconfigured to 8850 and

BAM. (5)

N

Query E1 link status.(2)

Adjust physical connectionaccording to dataconfiguration. (4)

Delete the route incorrectlyconfigured. (7)

Add new routeconfiguration. (8)

Query IPOA PVC configuration. (9)

Query 8850 PVC and standby PVCconfiguration. (11)

Compare the VPI and VCIinformation and check the BOOTP

configuration.(12)

N

Y

N

Modify the configuration.(13)

The link configuration isconsistent with physical

connection.(3)

The route isconfiguration correct.

(6)

The route is notconfigured.

The configuration isconsistent.

Query BTS BOOTP information and thecorrespondence between the subrack

and the optical interface. (10)

The route ismis-configured.

Y

N

Y

Figure 18-1 Troubleshooting flowchart for BTS ping failure

Steps:

1) Query the E1 links configured to BTS.

Execute the command LST BTSLNK to list the E1 links configured to the BTS.

Example LST BTSLNK:;


18-3

Result: %%LST BTSLNK:;%%



--------------------


Sequence Bandwidth (M) Link Flag BOOTP Flag

0 O&M Link 4 0 IMA Mode 0(0,1)

0.11 1-255 2-44


0.11 1-255 4-45

(Total result = 2)


--------------------


Sequence Bandwidth (M) Link Flag

0 Signaling Link 4 0 IMA Mode 0(0,1)

0.11 1-254

0 Traffic Link 4 0 IMA Mode 0(0,1)

1.60 1-250-1


0.11 1-254


1.60 1-250-1

(Total result = 4)

--- END

2) Query E1 link status.

Execute the command DSP E1T1STAT to query the E1 link status.

Example DSP E1T1STAT: FN=4, SN=SLOT0;

Result %%DSP E1T1STAT: FN=4, SN=SLOT0, BTP=CBIE;%%


Query Result

------------

Slot E1/T1No. E1/T1OperationalStatus


18-4

0 0 Available

0 1 Available

0 2 Available


…… …… ……


(Records = 24)

--- END

3) The link configuration is consistent with physical connection.

As shown in step one, E1 No.1 is to be connected to BTS 0 and E1 No.2 to BTS 2. If they are connected incorrectly, the BTS cannot be pinged through on the BAM.

4) Adjust physical connection according to data configuration.

Connect the E1 link to the BTS correctly according to the configuration.

5) Query the IP route configured to 8850 and BAM.

a) Query the IP route of 8850

In the Service Maintenance System, execute the command:

LST SWIPRT: LSTFORMAT=VERTICAL;

b) Query the IP route configured to BAM

In the DOS environment, execute the following command:

route print

Result:

======================================================================

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 10.129.11.254 10.129.10.253 1

…… …… …… ……

129.8.0.0 255.255.0.0 10.12.3.64 10.12.3.128 1

//BTS O&M link route.

…… …… …… ……

255.255.255.255 255.255.255.255 10.129.10.253 10.129.10.253 1

======================================================================


18-5

6) The route is configuration correct.

The IP address of BTS can be pinged if the route is "129.8.0.0" and the route mask is "255.255.0.0". Otherwise, the route configuration is incorrect.

7) Delete the incorrect route configuration.

If the route configuration is incorrect, you need to delete it using the following commands.

In the Service Maintenance System, execute the command: RMV SWIPRT: RTDEST="129.8.0.0";

Execute the following command in the DOS environment: route delete 129.8.0.0

8) Add new route configuration.

In the Service Maintenance System, execute the command: ADD SWIPRT: RTDEST="129.8.0.0", RTDESTMASK="255.252.0.0",

NEXTHOP="192.1.1.4";

Execute the following command in the DOS environment: route add 129.8.0.0 mask 255.255.0.0 10.12.3.64

9) Query IPOA PVC configuration.

Execute the command LST IPOAPVC to query IPOA configuration.

Example LST IPOAPVC: FN=4, SN=7;

Result %%LST IPOAPVC: FN=4, SN=7;%%


IPOA PVC

--------

Subrack No. Slot No. VPI VCI Peer IP Address Local IP Address Bandwidth

(M)

4 7 2 44 129.8.10.4 129.8.10.2 0.11

4 7 4 45 129.8.10.5 129.8.10.2 0.11

(Total result = 2)


18-6

--- END

You can obtain the VPI and VCI of the BTS O&M link configured in the results.

10) Query the BTS BOOTP information and the correspondence between the subrack and the optical interface.

a) Query the BOOTP configuration information, including the VPI, VCI, and the correspondence between the subrack and the optical interface of CLPC.

Example LST BTSBTPINFO:;

Result %%LST BTSBTPINFO:;%%


BTS BOOTP Information

---------------------

BTS ID BTS Name LPU Slot No. LPU Subslot No. Optical port No. VPI

No. VCI No. BTS Gateway IP Address BTS Gateway Mask

0 BTS0 4 0 0 2 44

129.8.10.2 255.255.0.0

2 BTS2 4 0 0 4 45

129.8.10.2 255.255.0.0

(Number of results = 2)

Total reports : 1

--- END

b) Query the correspondence between the subrack and the optical interface of CLPC.

Example: LST FRMPRTMAP:;

Result: %%LST FRMPRTMAP:;%%


Subrack-Optical Interface Correspondence

------------------

CSWS Subrack Type Subrack No. CLPU Slot No. CLPU Subslot No. Optical

Port No.


18-7

8850 Switching 2 3 0 0






(Total result = 6)

--- END

c) Compare the BOOTP configuration information and the subrack-optical interface correspondence. If the data is inconsistant, modify the BOOTP configuration information according to the execution result of the command LST FRMPRTMAP. (For modification method, see step 13).

11) Query 8850 PVC and standby PVC configuration.


DSP SWREDPORT: SN=3;

12) Compare the VPI and VCI information and check the BOOTP configuration.

a) Compare the VPI and VCI information queried in step 9 and step 10. If data inconsistency is found, modify the VPI and VCI according to the value queried using the command LST IPOAPVC.

b) Compare the correspondence information between CLPC and optical interface queried in step 10 and step 11.

If the BSC supports the active-standby switchover function and the BTS supports the BOOTP configuration of the active and standby optical interfaces, two records should be configured in the BOOTP information of a BTS, respectively for the active optical port (for example, 3/0/2) and the standby optical port (for example, 2/2/2).

If the BSC supports the active-standby switchover function, but the BTS does not support the BOOTP configuration of the active and standby optical interfaces, only one piece of BOOTP configuration information can be added. Therefore, the optical port, through which the BOOTP information is received, must be the active one.


18-8

13) Modify the configuration.

If data inconsistency is found in step 12, modify the BOOTP information according to the value queried using the command LST IPOAPVC.

You can delete the BOOTP information incorrectly configured using the command RMV BTSBTPINFO and then add the new BOOTP information using the command ADD BTSBTPINFO. If CMUX is configured with active and standby optical ports, the active optical port No. (3/0/2) must be entered. Otherwise, the BTS still cannot be pinged through.

14) Test.

If the BTS can be pinged through on the BAM or the BAM can log on to the BTS through Telnet, the fault is cleared.

18.2 BTS (Carrier) Unavailable


Symptom 1

The BTS can be pinged through from BAM, but all the carriers are unavailable. The CTRX at BTS and the CSPU at BSC are normal.

Symptom 2

The BTS can be pinged through from BAM, but a certain carrier is unavailable. The CTRX at BTS and the CSPU at BSC are normal.

II. Troubleshooting

The fault is generally caused by the inconsistency of data like:

Cell IDs Carrier IDs Optical port configuration and physical connection BTS Signaling IP addresses



18-9

END

Query cell IDconfiguration. (1)

Query carrier ID and opticalport configuration. (2)

Query BTS Signaling IPaddresses. (3)

Modify BTS offline scriptaccording to BSC data. (4)

Re-configure the BTS. (5)

Figure 18-2 Troubleshooting flowchart for BTS unavailable

1) Query the cell ID configured.

Configuration script at BSC side: ADD CELL: BTSID=1, CN=1, SCTIDLST="0", PNLST="40", SID=12062, NID=6,

PZID=3, LAC="0x3", IFASSALW=NO;

Configuration script at BTS side: ADD BTSCELL: BTSID=1, LOCALCELLID=1, LOCALSECTORID=0, DIVM=NTD;

The "CN" value in the command ADD CELL should be the same as the "LOCALCELLID" value in command ADD BTSCELL. Otherwise, all the carriers of the BTS will be unavailable.

2) Query carrier ID and optical port configuration.

Configuration script at BSC side: ADD CDMACH: CN=1, SCTID=0, CRRIDLST="0", ARFCNLST="160";

Configuration script at BTS side: ADD BTSBTRM: BTSID=1, BTRMID=0, LOCALCELLID=1, LOCALSECTORID=0, CRRID=0,

CPLID=0, BTRMDIVM=NTD, BRDMID=0, FIBPN=1, FIBTS=1;

The "CRRIDLST" value in the command ADD CDMACH must be consistent with the "CRRID" value in the command ADD BTSBTRM.


18-10

The "FIBPN" value in the command ADD BTSBTRM must be consistent with the actual physical connection.

The incorrect configuration of the channel number and optical interface data may cause the start failure of a certain carrier.

3) Query BTS Signaling IP addresses.

Configuration script at BSC side: ADD BSCBTSINF: BTSTP=IBSC, MN=0, IBTSID=1, OMIP="129.8.10.4",

SIGIP="80.17.130.116";

Configuration script at BTS side: SET BTSTERSIGLNK: BTSID=1, BRDID=0, IPVER=IPV4, BSCIP="80.17.130.0",

BSCAALTP=AAL5, BTSIP="80.17.130.116", BTSAALTP=AAL5;

The "SIGIP" value in the command ADD BSCBTSINF must be consistent with the "BTSIP" value in the command SET BTSTERSIGLNK; otherwise, all the carriers under the BTS will be unavailable.

4) Modify BTS offline configuration script according to BSC data.

If data inconsistency is found, modify the BTS data configuration script according to the data configuration of BSC.

5) Re-configure the BTS.

Execute the command CLR BTSCFG to clear the BTS configuration first.

Example

CLR BTSCFG: BTSID=1;

Then, re-configure the BTS with new BTS script.

6) Test

Check whether all carriers are available. If yes, the troubleshooting succeeds.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 19 Clock Fault

19-1

Chapter 19 Clock Fault

19.1 Inadequate Satellites Traced by GCKP

I. Symptom

The ALM indicator on GCKP keeps on. In the Service Maintenance System, execute the command to query the number of satellites traced by GCKP. The result shows that the number of traced satellites is inadequate.

Example:

DSP SATCARD:SN=0:;

Result:

%%DSP SATCARD: SN=0;%%


Query Result

------------

CardType = UTONCORE

GpsMode = GPS mode

GpsState = Position hold

GpsSatelliteNumber = 8

GlonassSatelliteNumber = 0

OtherSatelliteNumber = 0

LongitudeOfSatelliteReceiver = East Longitude 114

Degree(s) 3 Minute(s) 15 Second(s)

LatitudeOfSatelliteReceiver = North Latitude 22

Degree(s) 39 Minute(s) 20 Second(s)

AltitudeOfSatelliteReceiver(Meter) = 113

MaskAngle(Degree) = 5

AntennaState = Normal

--- END

This fault of Inadequate Satellites Traced by GCKP occurs when:

The number of satellites traced by the GPS satellite card (UTONCORE or M12+) is less than four (in non-position hold mode).


19-2

The number of GPS satellites, and the number of GPS/GLONASS satellites traced by the GPS/GLONASS satellite card (JGG20, JGG80 or K161T) is less than four and five respectively.

The number of satellites traced by the satellite card is less than or equals four (in position hold mode).

II. Troubleshooting

See Figure 19-1for the troubleshooting procedure.

END

Connect the antennaproperly.(2)

Check the connection ofthe antenna and feeder

to ensure that.(1)

Figure 19-1 Troubleshooting flowchart for Inadequate Satellites Traced by GCKP

Steps:

1) Check the connection of the antenna and feeder to ensure that.

a) The antenna is vertical and facing the sky.

b) There is no obstruction around the antenna.

c) There is no high-frequency interference source, such as paging station, around the antenna.

d) The antenna and the feeder are properly connected.

e) The feeder is well installed.

f) The feeder and the GCKP are connected properly.

2) Connect the antenna properly.

Connect the antenna and the feeder properly, especially at the interfaces and inside the GCKP.


19-3

19.2 Locking Satellite Signals Failed

I. Symptom

Any of the following cases indicates that UTCP fails to lock the satellite.

1) When UTCP works with ESR8750: After UTCP is powered on or reset, if the ALM indicator flashes with a frequency of 0.5 Hz over 20 minutes and the ACT indicator keeps off, UTCP fails to lock the satellite.

2) When UTCP works with ESR8750: In the running status, if the ALM indicator flashes with a frequency of 0.5 Hz but the ACT indicator keeps on, UTCP may fail to lock the satellite.

3) When UTCP works with ESR8850: After UTCP is powered on or reset, if the ALM indicator flashes with a frequency of 0.5 Hz over 20 minutes and the ACT indicator keeps off, UTCP may fail to lock the satellite.

4) When UTCP works with ESR8850: In the running status, if the ALM indicator flashes with a frequency of 0.5 Hz but the ACT indicator keeps on, UTCP may fail to lock the satellite.

II. Troubleshooting


END

Y Y

NN

The DIP switches areset properly.(2)

Set the DIP switchescorrectly (3)

Check the statuses of theDIP switches on UTCP.(1)

The antenna is connected properly.(4)

Connect the antennaproperly (5)

Figure 19-2 Troubleshooting flowchart for UTCP failure in locking satellite

Steps:

1) Check the statuses of the DIP switches on UTCP.

Pull out the UTCP from the subrack, and check and record the statuses of the DIP switches.


19-4

2) The DIP switches are set properly.

Check whether the DIP switch statuses are correct based on the description in Table 19-1.

Table 19-1 UTCP DIP switches

SW1 SW2 SW3 SW4

8850 + GPS Single-mode Satellite Signal Receiver On Off Off Off

8850 + GPS/GLONASS Dual-mode Satellite Signal Receiver Off On Off Off

Note:

The GPS single-mode satellite signal receiver differs from the GPS/GLONASS dual-mode satellite signal receiver in number of pins. The former has 10 pins, while the latter has 30 pins.

3) Set the DIP switches correctly.

Set the DIP switches according to Table 19-1.

4) The antenna is connected properly.

a) Check whether the antenna is vertical and facing the sky.

b) Check whether there is obstacle around the antenna.

c) Check whether there is high-frequency interference source, such as paging station, around the antenna.

d) Check whether the antenna and the feeder are properly connected.

e) Check whether the feeder is normal.

f) Check whether the feeder and the GCKP are connected properly.

5) Connect the antenna properly.

Connect the antenna and the feeder properly and make sure the connectors are secured.


19-5

19.3 Abnormal MS Time Display


The time displayed on an MS in some areas is incorrect. For example, the time displayed on the MS of the same model in different areas differs by two hours.

II. Troubleshooting


Query the local timeoffset configured. (1)

Modify the local timeoffset.(2)

Re-access thenetwork.(3)

END

Figure 19-3 Troubleshooting flowchart for MS abnormal time display

1) Query the local time offset configured.

MS displays the time of the current location area according to GPS time and local time offset.

If the local time offset configured for each CIPS/CBMS of BSC is inconsistent with each other, the time displayed on the same MS in different areas may be different.

You may execute the command LST SYSMSGPARA to query the local time offset.

Example LST SYSMSGPARA: CN=20, SCTID=0, CRRID=0, CCMINF=SCHM;

Result %%LST SYSMSGPARA: CN=20, SCTID=0, CRRID=0, CCMINF=SCHM;%%


Sync Channel Message Parameter

------------------------------

Cell ID = 20

Sector ID = 0

Carrier ID = 0


19-6

Local Time Offset = GMT+08:00

Paging Channel Rate = 9600bps

CDMA Channel No. = 160

Extended CDMA Channel No. = 160

(Total result = 1)

--- END

2) Modify the local time offset.

If the local time offset is configured incorrectly, modify it according to actual situation.

You can use the command MOD SCHM to modify the time offset. For example:

MOD SCHM: CN=20, SCTID=0, CRRID=0, LOCTMOFF=LF48;

The "LTMOFF" in the command is the "Local Time Offset". The value "32" stands for "Greenwich time". With the unit of 30 minutes, the time difference between two neighboring time zones is 2. That is, add 2 for the time zone eastwards, and subtract 2 from the time zone westwards.

3) Re-access the network.

The local time offset is contained in synchronization channel message. The synchronization channel message be received only after the MS re-searches the network. Therefore, after the local time offset is modified, the MS time will be updated only after the MS re-accesses the network.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Chapter 20 Operation and Maintenance System Fault

20-1

Chapter 20 Operation and Maintenance System Fault

20.1 Failed to Ping External Network IP of CMPU from BAM


It is failed to ping the external network IP of the CDMA main process unit (CMPU) in switching subrack (8850) from BAM.

II. Troubleshooting



20-2

The connection is correct. Query the CMPU external network IPand the port status (3)

They are in the same network segment and CMPU network

interface is changed to UP

Check the network cablebetween BAM and 8850 (1)

Query IP of BAM connected to CMPU external network interface(4)

Configure CMPU external networkinterface IP and change CMPU

external network interface to UP (5)

Query ARP information ofCMPU and BAM (6)

They are consistent

Check the consistency ofARP information in CMPU

and BAM (7)

Delete incorrect ARPinformation (8)

Query BAM routeinformation (9)

The route informationis sufficient

Add route in BAM (11)

Select correct network cable

Ping the external network IPaddress of CMPU from BAM (2)

END

N

NN

N

Y

Y

Y

Y

Figure 20-1 Troubleshooting flowchart for failure of pinging external network IP Address of CMPU from BAM


20-3

Steps:

1) Check the network cable between BAM and 8850

Their connections are in two modes:

When BAM is directly connected to 8850, use the straight-through network cable. When BAM is connected to 8850 through LAN switch (HUB), use the cross-over

network cable for the connections between 8850 and LAN Switch, and between BAM and LAN Switch.

2) Ping the external network IP address of CMPU from BAM

In Windows operating system, select [Start/Run], and execute Command to enter MS-DOS window. Ping the IP address to check whether the communication between BAM and CMPU is normal.

Example C\>ping 10.12.3.64

Result Pinging 10.12.3.64 with 32 bytes of data:

Reply from 10.12.3.64: bytes=32 time<10ms TTL=255




The above information indicates that the communication between BAM and CMPU is normal.

3) Query the CMPU external network IP and the port status

Log on to the CMPU external network interface (or the serial port connected to CMPU) through Telnet, and then execute show interface Ethernet 0/0/0 (or show interface Ethernet 1/0/0) to query external network IP and port status of CMPU of the switching subrack (8850).

For example:

ESR#show interface ethernet 0/0/0

Ethernet0/0/0 is up, line protocol is up //Indicating port status

is UP

……

Internet Address is 10.12.3.64/24 //Indicating external network

IPaddress is 10.12.3.64

IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is

00e0.fc09.33bd //MAC address of external network interface


20-4

……

0 output error

Note:

Before delivery or during the first installation of 8850, the external network address of CMPU must be set to 10.12.3.64 and that of mask to 255.255.255.0. If the data configuration does not meet that requirement during troubleshooting, the initial data configuration may be incorrect or the configuration has been changed during the operation. You must reconfigure the data correctly through serial ports.

4) Query IP of BAM connected to CMPU external network interface

In Windows operating system, select [Start/Run], and execute Command to enter MS-DOS window. Execute ipconfig/all to check the IP address of BAM connected to CMPU external network interface.

Example C:\> ipconfig /all

Result Ethernet adapter AMDPCN1:

Description : AMD PCNET Family Ethernet Adapter

Physical Address : 00-02-55-58-BA-36 //Adapter MAC address

DHCP Enabled : No

IP Address : 10.12.3.128 //Adapter IP address

Subnet Mask : 255.255.255.0

Default Gateway :

5) Configure CMPU external network interface IP and change CMPU external network interface to UP

Log on to CMPU external network interface (or the serial port connected to CMPU) through Telnet, configure external network interface IP address of CMPU and change CMPU external network interface to UP.

For example:

ESR#configure terminal

Enter configuration commands, one per line. Ctrl + Z to end

ESR(config)#interface ethernet 0/0/0

ESR(config-if-Ethernet0/0/0)#ip address 10.12.3.64 255.255.255.0


20-5

ESR(config-if-Ethernet0/0/0)#

ESR(config-if-Ethernet0/0/0)#no shutdown

ESR(config-if-Ethernet0/0/0)# end

ESR#write

6) Query ARP information of CMPU and BAM

a) Query address resolution protocol (ARP) information of external network interface of CMPU

Log on to the CMPU external network interface (or the serial port connected to CMPU) through Telnet, and execute show arp to query ARP information of external network interface of CMPU.

For example:

ESR#show arp

Total : 2, Interface : 1, Static : 0, Dynamic : 1

IpAddress Mac_Address Type

===================================================

10.12.3.64 00e0.fc09.33bd Interface

10.12.3.128 0002.5558.ba36 Dynamic

===================================================

10:47:38:390 5/17/2003

b) Query ARP information of BAM network interface connected to CMPU

In Windows operating system, select [Start/Run], and execute Command to enter MS-DOS window. Execute arp -a to query ARP information of BAM network interface connected to CMPU.

For example:

C:\> arp -a

Interface: 10.12.3.128 on Interface 2

Internet Address Physical Address Type

10.12.3.64 00-e0-fc-09-33-bd dynamic

7) Check the consistency of ARP information in CMPU and BAM

Based on results acquired from steps 3, 4 and 6, check the correspondence of ARP information between CMPU and BAM according to Table 20-1.


20-6

Table 20-1 Correspondence of ARP information between CMPU and BAM

Query result of CMPU Query result of BAM

Its IP address 10.12.3.64 Its IP address 10.12.3.128

Its MAC address 00-e0-fc-09-33-bd Its MAC address 00-02-55-58-BA-36

ARP info 10.12.3.128 0002.5558.ba36 ARP info 10.12.3.64 00-e0-fc-09-33-bd

Note:

ARP information is the binding relation for peer IP address and medium access control (MAC) address. The above results should be identical. Otherwise, you should delete them according to step 8.

8) Delete incorrect ARP information

a) Delete the incorrect ARP information of external network interface of CMPU. Two methods are available:

Disconnect and then connect the network cable between CMPU external network interface and LAN switch (do not conduct this operation on the network cable between BAM and LAN switch).

Note:

When the network cable between CMPU external network interface and LAN Switch is disconnected, CMPU external network interface will be in Down status, and the previously generated ARP information will be deleted.

When the network cable is connected again, CMPU will automatically resolute ARP information. Therefore, the incorrect ARP information of CMPU external network interface is deleted.

Log on to the CMPU external network interface (or the serial port connected to CMPU) through Telnet, and execute no arp to delete the incorrect ARP information of CMPU external network interface.

For example:

ESR#configure terminal

Enter configuration commands, one per line. Ctrl + Z to end.

ESR(config)#interface ethernet 0/0/0

ESR(config-if-Ethernet0/0/0)#no arp 10.12.3.128


20-7

Delete ARP success!

b) Delete the incorrect ARP information of BAM

In Windows operating system, select [Start/Run], and execute Command to enter MS-DOS window. Then execute arp –d to delete ARP information of BAM network interface connected to CMPU.

For example:

C:\> arp –d 10.12.3.64

9) Query BAM route information

In Windows operating system, select [Start/Run], and execute Command to enter MS-DOS window. Execute route print to query BAM route info.

For example:

C:\> route print

======================================================================

Interface List

0x1 ........................... MS TCP Loopback interface

0x2 ...00 02 55 58 ba 36 ...... AMD PCNET Family Ethernet Adapter

0x3 ...00 03 47 6b f2 c9 ...... Intel 8255x-based Integrated Fast Ethernet

======================================================================

======================================================================

Active Routes:


0.0.0.0 0.0.0.0 10.129.11.254 10.129.10.103 1

10.12.3.0 255.255.255.0 10.12.3.64 10.12.3.128 1

…… …… …… …… ……

10) The route information is sufficient

After step 9, you can see that Destination and Netmask are 0.0.0.0, which is the default route. The default route is in route table. If the forwarding IP address of destination IP address cannot be found, the destination IP address of forwarding IP address is the gateway of the default route.

When BAM has multiple adapters, several default routes will be generated in Windows. When BAM does not have the specific route, the Windows system cannot decide which default route to select. Therefore, if the following specific route does not exist, it should be added.

For the loading of other boards in BSC, add the corresponding route.


0.0.0.0 0.0.0.0 10.129.11.254 10.129.10.103 1


20-8

10.12.3.0 255.255.255.0 10.12.3.64 10.12.3.128 1

11) Add route in BAM

In Windows operating system, select [Start/Run], and execute Command to enter MS-DOS window. Execute route add to add route information in BAM. For example:

C:\>route –p add 10.12.3.0 mask 255.255.255.0 10.12.3.64

C:\>route –p add 80.8.0.0 mask 255.252.0.0 10.12.3.64

Add default route:

C:\>route –p add 0.0.0.0 mask 0.0.0.0 10.12.3.64 –p

Note:

Brief introduction to BAM route commands: To execute a route command, you can select [Start/Run] in Windows operating system, and execute Command to enter MS-DOS window. Then you can execute the corresponding route command. The frequent route commands include: arp –a : Display current ARP info arp –d ip_address : Delete the binding between this IP and MAC address route print : Display route table route add : Add route route delete : Delete route Ipconfig : Display IP/Mask/Gateway of each adapter

20.2 BAM Fault

20.2.1 BAM Installation Failed


Symptom 1

BAM installation fails due to database initialization failure as shown in Figure 20-2.

Figure 20-2 The database initialization failure

Symptom 2


20-9

BAM installation fails because the previous BAM program is not uninstalled as shown in Figure 20-3.

Figure 20-3 BAM server or WS found

II. Troubleshooting


Uninstall BAM program (1)

BAM program haS error.

It is database initialization error.

Disconnect all applicationprograms to SQL Server. (2)

Delete BAM databasemanually. (3)

Re-execute installationprogram

END

N

Y

Y

N

Figure 20-4 Troubleshooting flowchart for BAM installation failure

Steps:

1) Uninstall BAM program

Select [Start/Programs/AirBridge cBSS cdma 1X Administration System/Uninstall Airbridge cBSC6600 System], or execute Uninstall.EXE under installation directory to uninstall BAM program. If BAM uninstall fails, see 13.2.2 for troubleshooting.


20-10

2) Disconnect all application programs to SQL Server

Click [Control Panel] (or [Administrative Tools] in Windows2000). Then run [Service]. Select MS SQL Server in service list, and shutdown the service. Now all applications connected to this SQL Server are disconnected.

Then, restart the service after the operation.

3) Delete BAM database manually

After step 2, you can start [SQL Server Enterprise Manager]. Under database node, right-click on the icons of BAM, Alarm and Perf, and click [Delete]; or select them and click [Delete] to delete them.

20.2.2 BAM Uninstall Failed


When BTS software or BSC software are uninstalled, the uninstall files cannot be found or opened. As a result, BAM uninstall fails, as shown in Figure 20-5.

Figure 20-5 BAM uninstall failure

II. Troubleshooting



20-11

BTS BAM can beuninstalled.

Stop all running BAMprograms. (1)

Delete BTS installationinformation in the registry. (2)

Delete or modify the relevant filesunder the BAM installation directory. (3)

END

Y

Uninstall BSS BAM

Delete all contents underBAM installation directory. (6)

Y

Delete the BSS installationinformation in the registry. (5)

N N

BAM Server is uninstalled.

Delete the relevant contentsin the file cdma2000.ini. (4)

Y

END

N

Figure 20-6 Troubleshooting flowchart for BAM uninstall failure

Steps:

1) Stop all running BAM programs.

In the Windows operating system, select [Start/Control Panel/Service] and stop the BAM service and the SMirror service (the synchronization program of the WS and the BAM.).

In the BAM Manager, select [File/Close All], and stop all BAM service processes. Then, exit BAM Manager.

Note:

After exiting the BAM Manger, start the BAM uninstall program within five minutes. Otherwise, the BAM services will automatically re-start the computer without giving any prompt.


20-12

2) Delete BTS installation information in the registry.

In Windows operating system, select [Start/Run]. Execute regedit to open "Registry Editor". Delete the following registration item in the registry:

[My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\HuaWei\cdma2000\ Installation\BTS]

3) Delete or modify the relevant files under the BAM installation directory.

a) Delete d:\AirBridge\OnlineHelp\bsstoc.idx under BAM installation directory.

b) Delete d:\Airbridge\data\bsstoc.idx under the BAM installation directory.

c) Copy c:\winnt\bscdoc.idx to d:\Airbridge\onlinehelp of BAM installation directory, and change its name into Bsstoc.idx.

d) Copy c:\winnt\bscdoc.idx to d:\Airbridge\data of BAM installation directory, and change its name into Bsstoc.idx.

4) Delete the relevant contents in the file cdma2000.ini.

Delete all contents related to BDataman and BMaintain in BAM installation directory d:\Airbridge\cdma2000.ini.

5) Delete the BSS installation information in the registry.

In the Windows Operating System, select [Start/Run]. Execute regedit to open "Registry Editor". Delete:

[My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\HuaWei\cdma2000].

6) Delete all contents under BAM installation directory.

Delete all files and directories under BAM installation directory (d:\Airbridge).

Note:

Possible causes for BAM uninstall failure include: the uninstall files are deleted; uninstall files are damaged as uninstall procedure is abnormally interrupted; the computer is not restarted after BAM software is installed. The faults can be cleared by manually uninstalling BAM.


20-13

20.2.3 Exchange and Load Processes Abnormal


In BAM Manager, the Exchange and Load processes are in abnormal status, as shown in Figure 20-7.

Figure 20-7 Exchange and Load processes in abnormal status

II. Troubleshooting


InnerNetAddr in cdma2000.iniis different from the actualinternal network IP in BAM

Restart Exchange and Loadprocesses in BAM manager (2)

Y

Modify InnerNetAddr incdma2000.ini to be identical withthe internal network IP in BAM (1)

N

END

Figure 20-8 Troubleshooting flowchart for Exchange and Load exceptions

Steps:


20-14

1) Modify InnerNetAddr in cdma2000.ini to be identical with the internal network IP in BAM.

Open file cdma2000.ini with Notepad or other editor tools, and find [System], and modify InnerNetAddr field of BAM as the actual IP address of BAM.

Or, modify the IP address of BAM into the value of the field InnerNetAddr (generally 10.12.3.128).

2) Restart Exchange and Load processes in BAM manager.

Open BAM Manager, and restart Exchange and Load processes.

Note:

When Load and Exchange are performing initialization, they read BAM internal network IP address from cdma2000.ini. If this IP address is different from the actual IP address, "Initialization Failed" will occur. On the interface, the status of Exchange and Load in BAM manager is abnormal.

20.2.4 Starting TFTP Failed and Load Service Abnormal


In the BAM Manager, the Load service is always in the abnormal status and cannot be started. See Figure 20-9.

Figure 20-9 Load service in abnormal status


20-15

II. Troubleshooting

Figure 20-10 shows the troubleshooting procedures when the Load service is in the abnormal status.

Query the status of TFTP

The TFTP is started

Quit the TFTP daemon

Query the status of theLoad service

END

Y

N

Figure 20-10 Troubleshooting flowchart when the Load service is in the abnormal status

Note:

When started, both TFTP and Load occupy the 69 port. Hence, the running of the TFTP will lead to the abnormality of the Load service.

20.3 WS Fault

20.3.1 Intermittent Interruption between WS and BAM


Symptom 1

After logging on BAM through MML WS, the connection between MML WS and BAM is interrupted every 10 seconds.

Symptom 2


20-16

BAM can be pinged through on the WS. However, the WS cannot be pinged through on the BAM.

II. Troubleshooting

Note:

BAM is configured with at least two network adapters: one internal network adapter and one external network adapter. The internal network adapter is connected to the BSC host, while the external network adapter is connected to the WS.

If the route to the WS IP address configured on BAM is not right, BAM cannot send the IP packages to the WS properly. Therefore, BAM can be pinged through on the WS. However, the WS cannot be pinged through on the BAM. As a result, MML Server automatically disconnects from the WS, which leads to the intermittent interruption of the communication between the WS and the BAM.

The following shows the procedures to clear the fault of intermittent interruption of the communication between the WS and the BAM:

1) In the Windows operating system, select [Start/Run]. Execute Command to enter the MS-DOS window. Execute the command route print to query the BAM route information currently configured.

2) If the route from the BAM to the WS is not configured, add it accordingly.

In the Windows operating system of the BAM, execute the command route -p add to add the permanent route to the WS.

Assume BAM external network IP address is 16.17.18.120, and WS IP address is 16.17.18.20, and external network gateway is 16.17.18.254. Add the route information to the WS by using the following command:

route -p add 16.17.18.0 mask 255.255.255.0 16.17.18.254

20.3.2 WS Login Failure


In Windows2000, the Airbridge WS cannot be normally connected with the default setting due to the dual-IP configuration.

OMC comprises one BAM, one maintenance terminal, and one emergency WS.

BAM has two adapters: one is configured with 130.5.1.11, and the other is configured with 10.12.3.128. Here, 130.5.1.x is the external network segment and allocated to M2000; while 10.12.x.x is the internal network segment and allocated to BSC.

The operating system for the maintenance terminal is Windows 2000, with only one adapter installed with Airbridge WS and M2000 WS. This maintenance terminal is configured with two IPs: 130.5.1.x and 10.12.x.x network segments.


20-17

When a WS is added at BAM, the IP with 130.5.1.x network segment can be normally added. When the Airbridge WS is connected to BAM, the BAM shows that this WS does not exist, and the Airbridge WS only has the GUEST authority.

II. Troubleshooting


Show the actual IPbetween WS and BAM (1)

Use the actual IP as WS IPto re-register WS (2)

WS is registered viaADD WS

END

IP of the registered WS is the same as the

actual one

Y

N

Y

N

Y

N

An adapter is binding with 2 IPs

Test (3)

Figure 20-11 Troubleshooting flowchart for WS login failure

Steps:

1) Show the actual IP between WS and BAM.

If you are sure the WS is registered, you can view the actual IP between WS and BAM using the command netstat –n in Windows OS. Assume the actual IP is IP1, and WS IP upon registration is IP2.If IP1 and IP2 are different, you should re-register IP1.

2) Use the actual IP as WS IP to re-register WS.

Use the actual IP as WS IP to re-register WS with ADD WS.


20-18

3) Verify the result.

When IP2 (the IP for registering WS) is identical with IP1 (the actual IP), the WS can log on BAM normally.

Note:

The WS information added through ADD WS is stored in the database table by BAM (including the WS name and IP).When the WS originates the connection to the BAM, the BAM check the peer IP connected to Transport Control Protocol (TCP). If there is no corresponding record for this IP address in the above-mentioned database table, BAM consider the WS is not recorded and it only has GUEST authority.

A WS with 130.5.1.x is successfully added; but, when this WS is connected to BAM, the system prompts that this WS is not registered. The IP connected to BAM is not 130.5.1.x, so this problem occurs. This may result from one adapter of WS binding with two IP addresses.

20.4 Loading Problem

20.4.1 BAM Received No BOOTP Request for Board Loading


When the system is powered on or the board is reset, a board in BSC cannot start normally.

Open BAM manager to show [Load] window, press <CTRL+SHIFT+F12> to display the debugging menu, click [File/View/Start Tracing] to perform message tracing, you will find that no BOOTP request is reported to BAM as shown in Figure 20-12. RUN indicator of the board is flashing fast, requesting for data loading.

Figure 20-12 BAM Receiving No BOOTP request


20-19

II. Troubleshooting


Ping the external networkIP address of 8850 CMPU

from BAM(1)

The pinging issuccessful?

Check whether 8850boards are normal (3)

It is normal

Query the 8850 (switchingmodule) data related to

BOOTP (4)

The data is incomplete orincorrect?

Modify the relevant dataconfiguration (5)

Replace the boardObserve the alarm status ofCLPC optical interface (6)

The red indicator is on

Optical fiber Rx and Tx arewrongly connected or

broken. Re-connect theoptical fiber.

See "Failed to PingExternal Network IP of

CMPU from BAM".

BAM Load processreceives BOOTP request

(2)

END

N

Y

Y

Y

N

N

N

Y

Figure 20-13 Troubleshooting flowchart for BAM receiving no BOOTP request for board loading

Steps:

1) Ping the external network IP address of 8850 CMPU from BAM.

a) Select [Start/Run] to enter MS-DOS window.

b) Check whether the communication between BAM and 8850 is normal by executing Ping command. If the response packet from the peer end is received as follows, the communication is normal.

C\>ping 10.12.3.64

Pinging 10.12.3.64 with 32 bytes of data:






20-20

2) BAM Load process receives BOOTP request.

Open BAM manager to show Load process window, and press <CTRL+SHIFT+F12> to display the debugging menu. Select [View/Start Tracing] in Load process. You can see that BOOTP request is displayed in Load window, as shown in Figure 20-14.

Figure 20-14 BAM Load process receiving BOOTP request

3) Check whether 8850 boards are normal.

In the Service Maintenance System, execute the command:

DSP SWBRDINFO: SN=9;

Result:



Query Result

------------

Slot No. = 9

Board Type = CLPC








20-21

( Records = 1 )

--- END

4) Query the 8850 (switching module) data related to BOOTP

Check the configuration or status of the following:

Internal network IP address of BAM in cdma2000.ini

Open the cdma2000.ini file and check whether the InnerNetAddr under [System] has been configured as the internal network IP (10.12.3.128) of BAM. The BAM sends that IP address to 8850 when the 8850 starts working; then 8850 take it as the DHCP Server address. Make sure that the IP address is correct.

IPoA

Execute the command LST SWIPOAPVC to query IPoA information. Check whether the peer IP address and subrack number correspond with the actually bound optical interface.

Optical interface corresponding to the CLPC connected with the BSC subrack

Executed the command DSP SWATMPORT to check whether the corresponding optical interface is activated.

5) Modify the relevant data configuration

Compare the actual configuration with the requirements in step 4 to check whether there is any missing data or error data. If so, reconfigure the data using the MML.

Configure the internal network IP address of BAM.

Open the cdma2000.ini file using the editor and then configure InnerNetAddr under [System] as the actual internal IP address (10.12.3.128) of the BAM.

Reconfigure IPoA data.

Make sure the subrack that cannot receive the BOOTP request and the optical interface of the CLPC is connected with the subrack. If the binding relation between the subrack and the optical interface is incorrect, execute RMV SWFRMPORT to remove it, and then execute SET SWFRMPORT to create a correct one.

Activate the corresponding optical interface.

If the corresponding optical interface is inactive, execute the command ACT SWATMPORT to activate it.


20-22

6) Observe the alarm status of CLPC optical interface

Observe CLPC optical interface alarm. Two methods are available for showing CLPC alarm status:

Observe the indicator: If the red indicator of optical interface is ON, the alarm occurs.

Query the optical interface status with show interface through CMPU serial port or after logging on to 8850 external network interface through Telnet. ESR#show interface atm 11/0/0

Interface atm11/0/0 is UP

……

Alarm status: OFF

Interface alias name: NULL

Incoming cells are 0x0000227B

Outcoming cells are 0x0001A6FD

Note:

CLPC optical interface generates the corresponding alarm only when it is in active status. Otherwise, the alarm information does not exist.

20.4.2 BAM Failed to Send BOOT REPLAY to BSC Boards


When the system is powered on or the board is reset, a board in BSC cannot start normally.

Open BAM manager, and trace the message through Load process window, you can find that some BOOTP requests are sent to BAM, but the loading board serial port still displays: Error of BOOTP, because the BOOTP REPLY of BAM is not correctly sent to BSC board required for loading.

II. Troubleshooting



20-23

Observe Load processwindow (1)

BOOTP RELY FAILED is printed

Query BAM routeinformation (3)

The route is incomplete or incorrect

Add route in BAM (4)

Query the route of 8850 (5)

The route is incomplete or incorrect

Add the correspondingroute in 8850 (6)

Modify or add the correspondingrelation between subrack and

CLPC optical interface (2)

Observe Load processwindow

END

N

Y

Y

N

Y

N

Figure 20-15 Troubleshooting flowchart for the failure of sending BOOTP REPLY to BSC boards

Steps:

1) Observe Load process window

Open BAM manager to show the Load process window, and press <CTRL+SHIFT+F12> to display the debugging menu. Select [File/View/Start Tracing] to perform message tracing. You can see BOOTP request displayed in the Load window of BAM as shown in Figure 20-16.

Figure 20-16 Load window receiving BOOTP request and failing to send BOOT REPLY


20-24

2) Modify or add the corresponding relation between subrack and CLPC optical interface

If the Load window displays "Failed to obtain BOOTP reply information. Please check config data!", this indicates that CLPC optical interface connection relation is not consistent with the physical configuration.

The correspondence between the subrack and the CLPC optical interface cannot be modified. When this correspondence is not consistent with the physical configuration, remove it first and then add the new correspondence.

In Maintenance Management System, execute ADD FRMPRTMAP to add the corresponding relation between subrack and CLPC optical interface.

Example ADD FRMPRTMAP: SWT=SWT_8850,FN=2,SN=SN11,SSN=2,PN=0;

Result %%ADD FRMPRTMAP: SWT=SWT_8850, FN=2, SN=SN11, SSN=2, PN=0;%%

RETCODE = 0 //Execution is successful.

--- END

If the binding relation between the subrack and the optical interface configured on 8850 is incorrect, execute the following commands in the Service Maintenance System to remove the original binging relation and then create a new one.

RMV SWFRMPORT: FN=2;

SET SWFRMPORT: FN=2, SN=11, SSN=2, PN=0;

3) Query BAM route information

Select [Start/Run] to enter MS-DOS window. Query route information with route print:

C:\> route print

======================================================================

Interface List

0x1 ........................... MS TCP Loopback interface

0x2 ...00 02 55 58 ba 36 ...... AMD PCNET Family Ethernet Adapter

0x3 ...00 03 47 6b f2 c9 ...... Intel 8255x-based Integrated Fast Ethernet

======================================================================

======================================================================

Active Routes:


0.0.0.0 0.0.0.0 10.129.11.254 10.129.10.103 1

10.12.3.0 255.255.255.0 10.12.3.64 10.12.3.128 1

10.12.3.128 255.255.255.255 127.0.0.1 127.0.0.1 1


20-25

10.129.10.0 255.255.254.0 10.129.10.103 10.129.10.103 1

10.129.10.103 255.255.255.255 127.0.0.1 127.0.0.1 1

10.255.255.255 255.255.255.255 10.12.3.128 10.12.3.128 1

4) Add route in BAM

Select [Start/Run] to enter MS-DOS window. Add the route by executing the command route add.

The route loaded for BSC board and BTS board should be added in the BAM.

a) Add the specific route

C:\>route –p add 10.12.3.0 mask 255.255.255.0 10.12.3.64

C:\>route –p add 80.0.0.0 mask 255.0.0.0 10.12.3.64

C:\>route –p add 129.0.0.0 mask 255.0.0.0 10.12.3.64

b) Add the default route

C:\>route –p add 0.0.0.0 mask 0.0.0.0 10.12.3.64

5) Query the route of 8850

In the Service Maintenance System, execute the following command to query the route information on 8850:

LST SWIPRT LSTFORMAT=HORIZONTAL;

Result:

%%LST SWIPRT: LSTFORMAT=HORIZONTAL;%%

RETCODE = 0 Execution Succeed.

Query IP Route

--------------

SUBRACK NAME Logical slot No. Subslot No. Destination network address

Destination address mask Forward route address

CSWS 0 0 80.8.0.0

255.252.0.0 192.1.1.2

CSWS 0 0 80.12.0.0

255.252.0.0 192.1.1.3


--- END


20-26

6) Add the corresponding route in 8850

In the Service Maintenance System, execute the following commands to add route information:

ADD SWIPRT: RTDEST="80.12.0.0", RTDESTMASK="255.252.0.0",

NEXTHOP="192.1.1.3";

ADD SWIPRT: RTDEST="129.10.0.0", RTDESTMASK="255.255.0.0",

NEXTHOP="192.1.1.2";

20.4.3 CFMR DSP Loading Failed


During the system debugging or start, the loading of CDMA Radio Frame Process Board (CFMR) is successful, but the loading of CFMR Digital Signal Processor (DSP) fails.

When the command DSP DSPCPUUSAGE is executed to query the DSP CPU occupancy of the CFMR, the CPU occupancy of a certain DSP is displayed as “-“, indicating that this DSP is not loaded successfully.

Note:

In the normal case, the CUP occupancy should be 4% after the DSP of the CFMR is loaded successfully.

II. Troubleshooting

The CFMR DSP loading failure is generally caused by the fact that the Reduced TDMA Frame Number (RFN) required for loading is not correctly sent to CFMR DSP. See Figure 20-17 for the troubleshooting procedure.


20-27

Query the system clock line(1)

The connection is correctQuery GPS status and

8850 clock configuration(3)

The configuration iscorrect

Modify 8850 clockconfiguration (4)

Perform connectionaccording to Step 1

Load the CFMR DSP byforce (2)

END

N

Y

Y

Y

The setting of DIP switchis correct

Modify the setting ofUTCP DIP switch

N

Y

N

N

Check antenna feddersystem (5)

The connection is normal

Correctly connect theantenna feeder system

Check UTCP DIP switchstatus(6)

Query whether CMUXloading files can match the

switching subrack (7)

The match relation iscorrect

Set the correct matchrelation

Y

N

Figure 20-17 Troubleshooting flowchart for CFMR DSP loading failure

Steps:

1) Query the system clock line

Check whether the system clock line is correctly connected.

For the connection of system clock lines in coordinated universal time provider board (UTCP) scheme, see Figure 20-18.

For the connection of system clock lines in GPS/GLONASS and clock processing board (GCKP) scheme, see Figure 20-19.


20-28

CMUX(CRPS)CNETCAIE

UTCP

RUN ACTALM

CLK1

CLK2

E1/T1

E1/T1

E1/T1

E1/T1

RUN

ALM

ACT

CLK IN0

CLK IN1

CLK OUT0

CLK OUT1

CLK IN2

CLK IN3

RUN

CLK

ACT

TXRX

ETH

1PPS

COM1

COM2

RUN

ALM

ACT

RESET

Figure 20-18 Physical connection of BSC clock system (UTCP scheme)

Caution:

There is no signal output from the output port on the right of UTCP panel. Do not connect the system clock line to it.


20-29

RUN ALM ACT COM IN0 IN1 TEST ANT

TXRX

ETH

1PPS

COM1

COM2

RUN

ALM

ACT

RESET

7#CMUX(CRPS/CRMS)

CAIE

GCKP1

ETH_BCOM_BCLK_B ETH_ACOM_ACLK_A

GCKB

TXRX

ETH

1PPS

COM1

COM2

RUN

ALM

ACT

RESET

8#CMUX(CRPS/CRMS)

GCKP2

CAIE

CLK1

CLK2

E1/T1

E1/T1

E1/T1

E1/T1

RUN

ALM

ACT

RUN ALM ACT COM IN0 IN1 TEST ANT

CLK1

CLK2

E1/T1

E1/T1

E1/T1

E1/T1

RUN

ALM

ACT

Figure 20-19 Physical connection of BSC clock system (GCKP scheme)

2) Load the CFMR DSP by force.

Example

LOD DSP: FN=2, SN=4, CTLKEY=BAMFLS;

3) Query GPS status and 8850 clock configuration.

For UTCP + 8850 scheme, the correct configuration should be:

-- GPS: available;

-- CLKC operational mode: 3G mode;

-- Clock status: Trace;

-- PVC: Multicast PVC and Time PVC.

In the Service Maintenance System, execute the command to query the current clock status Example:


20-30

DSP SWCLKSTAT:;

Result: %%DSP SWCLKSTAT:;%%


Query Result

------------


Clock Source Selection Method = Preemptive Automatic

Switchover Strategy



Status of Current Phase-Locked Loop = CLK_SELF_VIBRATE

Slot No. = -

Subslot No. = -

Port No. = -




( Records = 1 )

--- END

In the Service Maintenance System, execute the following command to query the operational mode of the satellite receiver. Example:

LST SWUTCPMODE: LSTFORMAT=VERTICAL;

Result: %%LST SWUTCPMODE: LSTFORMAT=VERTICAL;%%


Query Satellite Receiver Mode

-----------------------------

GPS source = GPS1

Working mode of satellite receiver = BOTH


--- END

In the Service Maintenance System, execute the following command to query Time PVC:

LST SWPVC: VCI=251, LSTFORMAT=VERTICAL;


20-31

The returned result is as follows: %%LST SWPVC: VCI=251, LSTFORMAT=VERTICAL;%%


Query PVC

---------

LPC slot No. = 4

LPC subslot No. = 0

LPC port No. = 0

VPI borne = 1

VCI borne = 251

PVC USAGE = Time PVC


--- END

For 8850+GCKP scheme, the absolute time information is directly sent to CDMA system MUltipleXer unit (CMUX) of CDMA Resource and Packet Subrack (CRPS) by GCKP. Therefore, 8850 only needs to be configured with the multicast Permanent Virtual Connection (PVC).

In the Service Maintenance System, execute the following command to query RFN PVC:

LST SWPVC: VCI=255, LSTFORMAT=VERTICAL;

Result:

%%LST SWPVC: VCI=255, LSTFORMAT=VERTICAL;%%


Query PVC

-------

LPC slot No A = 2

LPC subslot No A = 0

LPC port No A = 1

VL VPI A = 1

VL VCI A = 255

LPC slot No B = 2

LPC subslot No B = 0

LPC port No B = 0

VL VPI B = 1

VL VCI B = 255

PVC USAGE = RFN



20-32

--- END

4) Modify 8850 clock configuration

UTCP scheme

In UTCP clock scheme, the synchronization configuration of BSC clock system includes the following parts: clock mode configuration, multicast PVC configuration, and clock channel configuration. For details, see the Table 20-2.

Table 20-2 Synchronization configuration description of UTCP clock scheme

Purpose of configuration Operation procedures

Clock mode configuration

Set the operational mode of the clock module (CLKC) on the CNET. 1 Set the operational mode of the clock board to 3G mode. 2 Set the satellite receiving mode of UTCP:

SET SWUTCPMODE: GPSSRC=GPS1, UTCPMODE=GPS;

If UTCP connects with CLK IN0, select gps 1 as the satellite receiving mode; if UTCP connects with CLK IN1, select gps2.

Multicast PVC configuration

Multicast PVC is mainly used for CRPS/CRMS to transmit the absolute time cell to each CIPS/CBMS.The port of CMUX connected to CRPS/CRMS is configured as p2mp-root; the port of CMUX connected to CIPS/CBMS is configured as p2mp-leaf.(Here, only configure the port of active CMUX ). When configuring the binding relation between the subrack and the optical interface, the system automatically configures the RFN multicast PVC. Query the multicast PVC using LST SWPVC (VPI=1,VCI=255): LST SWPVC: VPI=1, VCI=255, LSTFORMAT=VERTICAL;

Clock channel configuration

The purpose of configuring clock channel is to create a dedicated PVC, for CMPU to forward the absolute time cell to CMUX of CRPS. When configuring the binding relation between the CRPS/CRMS and the optical interface, the system automatically configures the Time PVC. Query the multicast PVC using LST SWPVC (VPI=1,VCI=251): LST SWPVC: VPI=1, VCI=251, LSTFORMAT=VERTICAL;

GCKP scheme

In GCKP clock scheme, the time synchronization of BSC clock system only requires to configure the multicast PVC for transmitting the absolute time cell. For details, see Table 20-3.


20-33

Table 20-3 Synchronization configuration description of GCKP clock scheme

Purpose of configuration Operation step

Multicast PVC configuration

Multicast PVC is mainly used for CRPS/CRMS to transmit the absolute time cell to each CIPS/CBMS.The port of CMUX connected to CRPS/CRMS is configured as p2mp-root; the port of CMUX connected to CIPS/CBMS is configured as p2mp-leaf.(Here, only configure the port of active CMUX). When configuring the binding relation the subrack and the optical interface, the system automatically configures the RFN multicast PVC. You can execute the command LST SWPVC to query the multicast PVC (VPI=1,VCI=255):LST SWPVC: VPI=1, VCI=255, LSTFORMAT=VERTICAL;.

5) Check antenna fedder system.

Check whether each part is firmly connected, whether the screw is fixed, and whether the antenna is well connected.

6) Check UTCP DIP switch status.

You can skip this step if the GCKP scheme is used.

The description of UTCP DIP switch status is shown in Table 20-4.

Table 20-4 Description of UTCP DIP switch status

DIP switch SW1 SW2 SW3 SW4

8850+GPS Single-mode Satellite Signal Receiver On Off Off Off

8850+GPS/GLONASS Dual-mode Satellite Signal Receiver Off On Off Off

Caution:

The satellite searching speed of UTCP is slow. Do not reset UTCP unless necessary. If UTCP is not disassembled, you cannot view UTCP DIP switch status. Therefore, you can make step 6 as the last step.

7) Query whether CMUX loading files can match the switching subrack.

The different clock configuration schemes should be loaded with the different MUX.BIN files. The following two MUX.BIN files are used.


20-34

I00MUX0.bin (GCKP): it is the BIN file supporting GCKP. It can support small capacity configuration + GCKP scheme, and also support large capacity (8850) + GCKP scheme;

I00MUX0.bin (8850): it only supports the 8850+UTCP scheme. Because the UTCPs used in the offices cannot be upgraded to GCKP in a short time, this file will exist until UTCP is no longer used by the network system. The version of the 8850 can be the feature train or V5R003.

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Appendix A Template for Troubleshooting Cases

A-1

Appendix A Template for Troubleshooting Cases

Title [Mandatory. Service type (optional) + Failure cause + Symptom. It should be less than 30 characters.]

Symptom description [Mandatory. It contains version information (including the version of the equipment interconnected), networking information and the description of the fault. ]

Version information:

Networking information:

Fault description:

Alarm information [Optional. Take down the alarm information reported.]

Fault analysis [Mandatory. The analysis should be clear and logical in style or meaning. ]

Troubleshooting [Mandatory. The troubleshooting procedure should be paragraphed as "1, 2, and 3…" for better understanding.]

1.

2.

3.

Suggestions and summary

Appendix [Optional. Only one appendix is permitted.]

Filename:

[The appendix can be one of the following: txt; html; htm; lwp; pdf; zip; bmp; 123; jpg; rtf; HTM; HTML; doc; JPG]

Other information [Optional. With a limit of 500 characters.]

Maintenance Manual - Troubleshooting Airbridge cBSC6600 CDMA Base Station Controller Appendix B Abbreviations and Acronyms

B-1

Appendix B Abbreviations and Acronyms

Abbreviations Full spelling

#

3GPP2 3rd Generation Partnership Project 2

A

A1/A2

A3/A7

A8/A9

A10/A11 AAL ATM Adaptation Layer

AAL1 ATM Adaptation Layer type 1



Abis ABR Available Bit Rate

AC Authentication Center

ACH Access Channel

ADDS Application Data Delivery Service

AEC Acoustic Echo Control

ALC Automatic Level Control

AMPS Advanced Mobile Phone System

ANSI American National Standard Institute

API Application Program Interface

ARFCN Absolute Radio Frequency-Channel Number

ARP Address Resolution Protocol

ASCII American Standard Code for Information Interchange

ASIC Application Specific Integrated Circuit

ATM Asynchronous Transfer Mode

B BAM Back Administration Module


B-2


BCD Binary Coded Decimal

BHCA Busy Hour Calling Attempt

BIOS Basic Input Output System

BITS Building Integrated Timing Supply system

BOOTP Bootstrap Protocol

BSC Base Station Controller

BSS Base Station Subsystem

BSSAP Base Station Subsystem Application Part

BSSMAP Base Station Subsystem Management-Application Part

BTS Base Transceiver Station

C CAIE CDMA A Interface Equipment

CBMS CDMA Basic processing Subrack

CBPU CDMA Buffer Process Unit

CBR Constant Bit Rate

CBUR CDMA Business Rack

CC Call Control

CCITT Consultative Committee of International Telegraphy and Telephony

CCRM CDMA Satellite synchronization Clock Receiver Module

CCTR CDMA ConTroller Rack

CDMA Code Division Multiple Access

CDR Call Detail Record

CEVC CDMA Enhanced Vocoder with echo Canceller board

CEVD CDMA Enhanced Vocoder with echo canceller Disable

CFMR CDMA radio frame process (FP MAC RLC) board

CHAC CDMA High-speed Access Controller

CIC Circuit Identification Code

CIMS CDMA Integrated Management System

CIPS CDMA Integrated Processing Subrack

CLAP CDMA Link Access Protocol board

CLKC ClocK C

CLKM CLocK processing Module

CLPC CDMA Line Process Unit


B-3


CLPU CDMA Line Process Unit

CMI Coded Mark Inversion

CMM Capability Maturity Module

CMPU CDMA Main Process Unit

CMUX CDMA system MUltipleXer unit

CNET CDMA NETwork transfer and switch

COIE CDMA single mode Optical Interface Equipment

CPCU CDMA PCF Control Unit

CPMS CDMA Packet Module Subrack

CPPU CDMA Packet Process Unit

CPU Center Processing Unit

CRC Cyclical Redundancy Check

CRMS CDMA Resources Management Subrack

CRMU CDMA Resource Management Unit

CRPS CDMA Resource and Packet Subrack

CSAR CDMA SAR Process Unit

CSPU CDMA Signal Process Unit

CSTU CDMA Synchronous Transport Unit

CSWS CDMA Switch Subrack

CTCS CDMA TransCoder Subrack

CXIE CDMA general (X) Interface Equipment

D DB Data Base

DBMS Data Base Management System

DC Direct Current

DCCH Dedicated Control CHannel

DDF Digital Distribution Frame

DDN Digital Data Network

DPC Destination Point Code

DSP Digital Signal Processor

DTAP Direct Transfer Application Part

DTMF Dual Tone Multi Frequency

E


B-4


EC Echo Canceller

EIA Electronics Industry Association

EIB Erasure Indicator Bit

EIR Equipment Identity Register

EMC Electro-Magnetic Compatibility

EMI ElectroMagnetic Interference

EMS ElectroMagnetic Susceptibility

EPLD Erasable Programmable logic Device

ESD Electrostatic Discharge

ETS European Telecommunication Standards

ETSI European Telecommunication Standards Institute

EVRC Enhanced Variable Rate Codec

F FA Foreign Agent

FAM Front Administration Module

FCC Federal Communications Commission

FCH Fundamental Channel

FE Fast Ethernet

FER Frame Error Rate

FID Function Identification

F-PCH Forward Paging Channel

FPGA Field Programmable Gate Array

F-QPCH Forward Quick Paging Channel

F/R-FCH Forward/Reverse Fundamental Channel

F/R-PICH Forward/Reverse Pilot Channel

F/R-SCH Forward/Reverse Supplemental Channel

F-SYNCH Forward Synchronous Channel

FTP File Transfer Protocol

G GCKB GPS/GLONASS& ClocK Subrack Backplane

GCKP GPS/GLONASS& ClocK Processing Board

GE Gigabit Ethernet

GLONASS Global Navigation Satellite System


B-5


GMSC Gateway Mobile-services Switching Center

GPS Global Position System

GRE Generic Routing Encapsulation

GSM Global System for Mobile Communication

GT Global Title

H HA Home Agent

HDLC High level Data Link Control

HHO Hard Handoff

HLR Home Location Register

HPA High Power Amplifier

HPT Higher Order Path Termination

I IAC Initial Alignment Control ICMP Internet Control Message Protocol

IEC International Electrotechnical Commission

IEEE Institute of Electrical and Electronics Engineers

IMA Inverse Multiplexing on ATM

IMT-2000 International Mobile Telecommunication 2000

IOS Interoperability Specification

IP Internet Protocol

IPC Inter-process Communication

IPOA IP Over ATM

ISDN Integrated Services Digital Network

IS-2000 Interim Standards 2000

IS-95 Interim Standards 95

ISDN Integrated Services Digital Network

ISLP Inter System Link Protocol

ISO International Standards Organization

ISUP ISDN User Part

ITU International Telecommunications Union

ITU-T ITU Telecommunication Standardization Sector


B-6


J

K

L LAC Link Access Control

LAN Local Area Network

LDP Label Distribution Protocol

LVL

M MAC Medium Access Control

MAP Mobile Application Part

MIP Mobile Internet Protocol

MRTIE Maximum Relative Time Interval Error

MM Mobility Management

MML Man Machine Language

MS Mobile Station

MSC Mobile Switching Center

MTBF Mean Time Between Failures

MTP Message Transfer Part

MuxPDU Multiplex Sublayer Protocol Data Unit

N NMS Network Management System

NMT Nordic Mobile Telephone System

O OAM Operation, Administration and Maintenance

OMC Operation & Maintenance Center

OML Operation & Maintenance Link

OOP Object-Oriented Programming

OSI Open System Interconnection

P PC Personal Computer

PCF Packet Control Function

PCI Protocol Control Information


B-7


PCM Pulse Code Modulation

PDH Pleisochronous Digital Hierarchy

PDSN Packet Data Service Node

PDU Packet Data Unit

PID Process Identification

PLMN Public Land Mobile Network

PN Pseudo Number

PPP Peer-Peer Protocol

PSTN Public Switched Telephone Network

PVC Permanent Virtual Connenction

PVP Permanent Virtual Path

Q QCELP Qualcomm Code Excited Linear Predictive codec

QOF Quasi Orthogonal Function

QoS Quality of Service

R RANDU Unique Random Variable

RC Rate Configuration

RFMT Radio Frequency Measurement Tool

RFN Reduced TDMA Frame Number

RLP Radio Link Protocol

ROM Read Only Memory

S SAR Segmentation And Reassembly

SCCP Signaling Connection and Control Part

SCH Supplemental Channel

SCHM Sync Channel Message

SDB Short Data Burst

SDH Synchronous Digital Hierarchy

SDRAM Synchronous Dynamic Random Access Memory

SDU Selection/Distribution Unit

SHO Soft Handoff


B-8


SLC Signaling Link Code

SLS Signaling Link Selection

SMS Short Message Service

SNMP Simple Network Management Protocol

SONET Synchronous Optical Network

SPVC Soft Permanent Virtual Connection

SPVP Soft Permanent Virtual Path

SSD Shared Secret Data

SSM Synchronization Status Message

SSN Sub-System Number

SSP Service Switching Point

SSSAR Special Service Segmentation and Reassemble

STM Synchronous Transfer Mode

SVC Switching Virtual Connection

T TACS Total Access Communication System

TC TransCoder

TCAP Transaction Capability Application Part

TCE Traffic Channel Elements

TCH Traffic Channel

TCP Transport Control Protocol

TDD Time Division Duplex

TDM Time Division Multiplex

TFO Tandem Free Option

TRAU Transcoder/Adaptor Unit

TTL TRAU-Transcoder Link

U UBR Unspecified Bit Rate

UDP User Datagram Protocol

UDT Unit Data

UNI User-to-Network Interface

UTCP UTC (Coordinated Universal Time) Provider Board


B-9


V VCC Virtual Channel Connection

VCI Virtual Channel Identifier

VBR Variable Bit Rate

VBR-nrt Non-Real Time Variable Bit Rate

VBR-rt Real Time Variable Bit Rate

VPI Virtual Path Identifier

VOS Virtual Operating System

W WCDMA Wideband Code Division Multiple Access

WS Work Station

X XUDT Enhanced Unit Data

Y

Z

Documents

Maintenance Manual Troubleshooting