BTS 8000 Fault Finding.pdf

7/26/2019 BTS 8000 Fault Finding.pdf

1/475

Global System for Mobile Communications (GSM)

Nortel GSM BTSS8000/S8002/S8003/S8006Fault ClearingRelease: 16.0Document Revision: 16.07

www.nortel.com

411-9001-103.


2/475

Global System for Mobile Communications (GSM)

Release: 16.0

Publication: 411-9001-103

Document status: Standard

Document release date: 28 May 2008

Copyright 1999, 2008 Nortel Networks

All Rights Reserved.

Sourced in Canada, France, and the United States of America.

LEGAL NOTICE

While the information in this document is believed to be accurate and reliable, except as otherwise expressly

agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF

ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are

subject to change without notice.

Nortel, the Nortel logo, the Globemark, S2000 and S8000 are trademarks of Nortel Networks.

All other trademarks are the property of their respective owners.

.


3/475

3.

Contents

New in this release 9Features 9

BSC e3 support of BTS SW background downloading (25316) 9

S8000 and S12000 eDRX2 900 MHz (34633) 9

Other changes 11

Introduction 13

Chapter 1 How to use this manual 191.1 Introduction 19

1.2 The types of spontaneous messages 20

1.2.1 Events detected by the BTS 20

1.2.2 Events detected by the BSC 20

1.3 Description of a fault number sheet 20

1.3.1 Header of the sheet 20

1.3.2 Main body of the sheet 20

1.4 Help 21

1.4.1 Loading the CD-ROM 21

Chapter 2 S8000, S8002, S8003, and S8006 BTS faultnumbers 232.1 Fault number: 1051 (S8000, S8002, S8003, and S8006 BTS) 23

2.2 Fault number: 1052 (S8000, S8002, S8003, and S8006 BTS) 23

2.2.1 Source 1: Bad hardware reference of manufacturer ID 29

2.2.2 Source 3: No change to one of BOOT states after reset 32

2.2.3 Source 5: Software not compatible with hardware 35

2.2.4 Source 6: File access error 39

2.2.5 Source 7: Repetitive errors (NACK, timeout, ...) while downloading a

file 422.2.6 Source 4: This entity is engaged in another downloadingSource 8: Wrong

software reference on a non downloadable TEI 43

2.2.7 Source 14: Received CSM LOAD CONTAINER NAK 45

2.2.8 Source 16: File to download unavailable 48



Global System for Mobile Communications (GSM)Nortel GSM BTS S8000/S8002/S8003/S8006 Fault Clearing

411-9001-103 16.07 Standard

28 May 2008Copyright 1999, 2008 Nortel Networks

.


4/475

4


2.5.1 Source 2: Equipment unable to perform such test 54

2.5.2 Source 3: Equipment unable to perform such configuration 55

2.5.3 Source 5: Cell parameters inconsistency 57

2.5.4 Source 6: Data inconsistency 59

2.5.5 Source 7: Value out of range 60

2.5.6 Source 8: TEI not present 61

2.5.7 Source 10: Unknown Abis PCM 62

2.5.8 Source 23: Too many signaling timeslots 63

2.5.9 Source 25: Out of sequence message 64

2.5.10 Source 34: The BTS has not acknowledged the TX power consignrequest 66

2.5.11 Source 43: Maximum number of joker TS 71



2.8 Fault number: 1059 (S8000, S8002, S8003, and S8006 BTS) 772.9 Fault number: 1060 (S8000, S8002, S8003, and S8006 BTS) 77

2.9.1 BRC (source: Manual switch on battery power) 94

2.9.2 BRC (source: Automatic switch on battery power) 95

2.9.3 BRC (source: Manual switch on main power) 95

2.9.4 BRC (source: Automatic switch on main power) 95

2.9.5 Cavity (source: Cavity parked after tuning fault (min not found)) 95

2.9.6 Cavity (source: Nack answer from cavity) 97

2.9.7 Cavity (source: Cavity parked after tuning fault (power too low)) 98

2.9.8 Cavity (source: Cavity parked after tuning fault (tuning detector)) 98

2.9.9 CMCF board (source: Unknown message) 99

2.9.10 CMCF board (source: Restart due to hardware watchdog) 992.9.11 CMCF boards (source: Restart due to double bus fault) 100

2.9.12 CMCF boards (source: Reset for new Lapd parameters CMCF) 100

2.9.13 CMCF boards (source: ABIS PCM statistics) 101

2.9.14 CSWM board (source: Restart due to hardware watchdog) 101

2.9.15 CSWM board (source: Restart due to double bus fault) 101

2.9.16 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Frequencycollision on FH bus) 102

2.9.17 DRX or eDRX or DRX ND3 or eDRX2 modules (source: FACCHcongestion) 102

2.9.18 DRX or eDRX or DRX ND3 or eDRX2 modules (source: Reset due to

hardware watchdog) 1032.9.19 DRX or eDRX or DRX ND3 or eDRX2 modules (source: Restart due to

double bus fault) 104

2.9.20 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: BCCH configdump) 104

2.9.21 DRX or eDRX or DRX-ND3 modules or eDRX2 (source: SACCH configdump) 104

2.9.22 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: L1M config


411-9001-103 16.07 Standard


.


5/475

5

dump) 105

2.9.23 DRX or eDRX or eDRX2 or DRX-ND3 modules (source: RSLanomaly) 105

2.9.24 Tx Filters (source: VSWR level 2) 106


2.11 Attribute value change: 1063 (S8000, S8002, S8003, and S8006 BTS) 108


2.12.1 BTS SYNCHRONIZATION (source: SYNO clock not locked on thenetwork) 133

2.12.2 BTS synchronization (source: Synchro not locked because OCVXO isKO) 150

2.12.3 BTS synchronization (source: GPS synchronization unavailable) 152

2.12.4 BTS synchronization (source: Loss of GPS synchronization) 157

2.12.5 BTS SYNCHRONIZATION (source: Lack of GPS synchronizationaccuracy) 162

2.12.6 BTS SYNCHRONIZATION (source: Master synchronization

unavailable) 1672.12.7 BTS SYNCHRONIZATION (source: Loss of master GSM time) 172

2.12.8 BTS SYNCHRONIZATION (source: Loss of master SY) 176

2.12.9 ACU climatic unit (source: Cooler fault) 180

2.12.10 ALCO board (source: Major fault) 183

2.12.11 Battery cabinet (source: Over temperature) 186

2.12.12 Battery cabinet (source: DC power fault) 189

2.12.13 Battery cabinet (source: Doors) 192

2.12.14 BCF cabinet door contact(source: BCF cabinet door contactdetection) 196

2.12.15 BCF cabinet fan (source: BCF cabinet fan fault) 200

2.12.16 BCF power supply (source: Volt) 202

2.12.17 BRC (source: Manual switch on battery power) 205

2.12.18 BRC (source: Automatic switch on battery power) 205

2.12.19 BRC (source: Manual switch on main power) 205

2.12.20 BRC (source: Automatic switch on main power) 205

2.12.21 BRC (source: Battery failure) 206

2.12.22 BRC (source: Monitored battery not present) 207

2.12.23 BRC (source: Internal inconsistency) 207

2.12.24 Cabinet door (source: Door contact detection) 208

2.12.25 Cavity (source: Cavity out of service) 211

2.12.26 Cavity (source: Cavity parked after tuning fault (min not found)) 2132.12.27 Cavity (source: Loss of cavity initialization) 215

2.12.28 Cavity (source: Nack answer from cavity) 217

2.12.29 Cavity (source: Cavity parked after tuning fault (power too low)) 219

2.12.30 Cavity (source: Cavity parked after tuning fault (tuning detectorproblem)) 221

2.12.31 Cavity (source: Internal software problem) 223

2.12.32 Cavity combiner (source: Power supply) 224


411-9001-103 16.07 Standard


.


6/475

6

2.12.33 Cavity combiner (source: Tuning detector fault) 226

2.12.34 Cavity combiner (source: Link NOK) 228

2.12.35 C-DACS climatic system (source: Dirty filter) 230

2.12.36 C-DACS climatic system (source: DACS failed) 232

2.12.37 CMCF board (source: MCF_MCF) 236

2.12.38 CMCF board (source: Slave downloading error) 238

2.12.39 CMCF board (source: CMCF_ACT_DUPLEX_INHIBITED) 241

2.12.40 CMCF board (source: CMCF_ACT_ICST) 243

2.12.41 CMCF board (source: Duplex inhibited: feature not supported onCMCF phase 1) 246

2.12.42 Combiner duplexer LNA or combiner H2 LNA (source: LNA fault) 249

2.12.43 Combiner duplexer VSWR or combiner H2 VSWR (source: VSWR level1) 253

2.12.44 Combiner duplexer VSWR or combiner H2 VSWR (source: VSWR level2) 253

2.12.45 Combiner duplexer VSWR or combiner H2 VSWR (source: VSWR level

3) 254

2.12.46 Combiner H4D LNA (source: LNA fault) 257

2.12.47 Combiner H4D VSWR (source: VSWR level 1) 260



2.12.50 Compact distribution system (source: Main breaker) 267

2.12.51 CPCMI board (source: Major) 270

2.12.52 CPCMI board (source: Slave downloading error) 270

2.12.53 CSWM board(source: Fault on active-passive CSWM link or on passiveCSWM) 273

2.12.54 CSWM board (source: Slave downloading error) 275

2.12.55 DACS climatic system (source: Dirty filter) 277

2.12.56 DACS climatic system (source: DACS failed) 280

2.12.57 Distribution system (source: Main breaker) 286

2.12.58 DRX or eDRX or DRX-ND3 modules (source: RX fault) 289

2.12.59 DRX or eDRX or DRX-ND3 modules (source: BBFILTER ASICfault) 292

2.12.60 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Self testfailed) 296

2.12.61 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Major faulton TX) 301

2.12.62 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: DRXlink) 305

2.12.63 DRX or DRX-ND3 modules (source: Abis satellite not supported DRX(ND3)) 311

2.12.64 DRX or eDRX or DRX-ND3 modules (source: The TX has notacknowledged the power consign request) 312

2.12.65 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: PA DRXcontrol loop fault) 316


411-9001-103 16.07 Standard


.


7/475

7

2.12.66 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Nackanswer) 321

2.12.67 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: DRX reset byBSC) 321

2.12.68 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: TRX not

anymore configured) 3222.12.69 DRX or DRX-ND3 modules (source: PA configuration exceeded) 324

2.12.70 DRX or DRX-ND3 modules (source: HePA not supported) 328

2.12.71 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: BCCH first

config failed) 331

2.12.72 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: BCCH secondconfig failed) 331

2.12.73 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: SACCH firstconfig failed) 332

2.12.74 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: SACCHsecond config failed) 333

2.12.75 DRX or eDRX or DRX-ND3 modules (source: L1M first configfailed) 334

2.12.76 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: L1M second

config failed) 334

2.12.77 DRX or DRX-ND3 diversity reception chain (source: Softwaredetection) 335

2.12.78 DRX or DRX-ND3 main reception chain (source: Softwaredetection) 339

2.12.79 DSC boards (source: Major fault) 343

2.12.80 DSC boards (source: Channel_HSCX) 345

2.12.81 External alarm (source: Alarm) 348

2.12.82 Not protected alarm (source: Alarm) 3482.12.83 Fan of the base cabinet (source: Cabinet fan fault) 348

2.12.84 F-type converters (source: Volt) 352

2.12.85 GTW boards (source: Major fault on GTW) 356

2.12.86 Internal batteries (source: Battery disconnected) 359

2.12.87 Lightning protector (source: Lightning protection fault) 362

2.12.88 Output Rx-splitter D (source: Over current) 365

2.12.89 Output Rx-splitter M (source: Over current) 368

2.12.90 PCM (source: PCM) 370

2.12.91 PCMI boards (source: Major fault on PCMI) 371

2.12.92 Power amplifiers (source: Hardware) 371

2.12.93 Power amplifiers (source: DRX and PA connection) 3772.12.94 Power amplifiers (source: High temperature ) 382

2.12.95 Power amplifiers (source: High Current ) 386

2.12.96 Power amplifiers (source: PA_PSDW ) 389

2.12.97 Power amplifiers (source: VSWR fault detected by PA) 393

2.12.98 RECAL board (source: Major) 394

2.12.99 RECAL board (source: Slave downloading error) 397


411-9001-103 16.07 Standard


.


8/475

8

2.12.100 Rectifiers (source: AC fault) 400

2.12.101 Rectifiers (source: DC fault) 404

2.12.102 Rectifiers (source: Over temperature) 406

2.12.103 Rectifiers (source: External battery level 1) 409

2.12.104 Rectifiers (source: PCU protective) 411

2.12.105 Rectifiers (source: Battery on discharges) 415

2.12.106 SYNC boards (source: Major fault on SYNC) 417

2.12.107 Rx Filter (source: LNA fault) 419





2.14.1 Source 9: No response to load message 431

2.14.2 Source 10: Received LOAD INIT NACK 431

2.14.3 Source 11: Received LOAD DATA NACK 431

2.14.4 Source 12: Received LOAD END NACK 4312.14.5 Source 13: Received LOAD READY NACK 431












2.26 Fault number: 1508 (S8000, S8002, S8003, S8006 BTS) 443

2.27 Fault number: 30034 (S8000, S8002, S8003, S8006 BTS) 444

2.28 List of fault numbers common to all BTS types 446


411-9001-103 16.07 Standard


.


9/475

9.

New in this release

FeaturesThe following sections detail whats new in theNortel GSM BTS S8000Fault Clearingguide for release V16.0.

See the following sections for information about feature changes:

BSC e3 support of BTS SW background downloading (25316) (page9)

S8000 and S12000 eDRX2 900 MHz (34633) (page 9)

BSC e3 support of BTS SW background downloading (25316)This feature allows new software to be downloaded to a BTS while thisBTS carries GSM/GPRS traffic (on a live network).

The impact of this feature is: added Section 2.15 fault number 1077 andSection 2.25 fault number 30034.

S8000 and S12000 eDRX2 900 MHz (34633)This feature introduces the eDRX2 900MHz in the S8000 BTS equippedwith a CBCF module and in the S12000 BTS.

The impacts of this feature are:

Fault number 1060 - added sources for eDRX2:

loss of PCM link

loss of GSM clock

Incorrect Abis message No flag on FH bus

2.9.16 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:Frequency collision on FH bus) (page 102)

2.9.17 DRX or eDRX or DRX ND3 or eDRX2 modules (source:FACCH congestion) (page 102)


411-9001-103 16.07 Standard


.


10/475

10 New in this release

LAPD congestion

underrun AMNU-SPU

postmortem dump zone 1

postmortem dump zone 2

restart due to power-on

restart requested by the BCF

reset due to timeout on OML link with BSC

reset due to timeout on OML link with BCF

restart due to a software upgrade

2.9.18 DRX or eDRX or DRX ND3 or eDRX2 modules (source:Reset due to hardware watchdog) (page 103)

2.9.19 DRX or eDRX or DRX ND3 or eDRX2 modules (source:

Restart due to double bus fault) (page 104) reset due to loss of lock

restart due to unknown software reset

restart due to a loss of internal PCM clock sent by BCF

2.9.20 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:BCCH config dump) (page 104)

2.9.21 DRX or eDRX or DRX-ND3 modules or eDRX2 (source:SACCH config dump) (page 104)

2.9.22 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:

L1M config dump) (page 105) 2.9.23 DRX or eDRX or eDRX2 or DRX-ND3 modules (source:

RSL anomaly) (page 105)

Fault number 1067 - added sources for eDRX2:

2.12.60 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:Self test failed) (page 296)

2.12.61 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:Major fault on TX) (page 301)

2.12.62 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:DRX link) (page 305)

2.12.65 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:PA DRX control loop fault) (page 316)

2.12.66 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:Nack answer) (page 321)

2.12.67 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:DRX reset by BSC) (page 321)


411-9001-103 16.07 Standard


.


11/475

Other changes 11

2.12.68 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:TRX not anymore configured) (page 322)

2.12.71 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:BCCH first config failed) (page 331)

2.12.72 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:BCCH second config failed) (page 331)

2.12.73 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:SACCH first config failed) (page 332)

2.12.74 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:SACCH second config failed) (page 333)

2.12.75 DRX or eDRX or DRX-ND3 modules (source: L1M firstconfig failed) (page 334)

2.12.76 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:L1M second config failed) (page 334)

Other changesSee the following sections for information about changes that are notfeature-related:

Replaced all occurrences of BSC 2G with BSC 12000HC

Index cleanup (removed forbidden characters: *, /, &)

Removed troubleshooting procedures for fault number 1052 formercauses

32 "new DRX hardware not compliant with old software" (Section2.2.8)

33 "Old DRX hardware not compliant with new software" (Section2.2.9)

Added new causes to fault number 1052 (Section 2.2) and faultnumber 1073 (Section 2.14)

Updated section 2.12.4 (fault number 1067 cause 3342344 "Loss ofGPS synchronization" on BTS synchronization)

Updated section 2.12.89 (fault number 1067 cause 6488065 "PCM"on PCM)

Added the description of new fault number 1508

Added the description of fault number 1060 cause 9437207, 12582935,12976151 "FACCH congestion" on DRX modules

Updated fault number 1266

Updated fault number 1067:


411-9001-103 16.07 Standard


.


12/475

12 New in this release

2.12.82 Not protected alarm (source: Alarm) (page 348) notprotected alarm (3735553): updated wording (not protected alarminstead of external alarms)

2.12.81 External alarm (source: Alarm) (page 348) new alarm

(7274497): external alarm


411-9001-103 16.07 Standard


.


13/475

13.

Introduction

This document contains the fault number description and the maintenanceactions required for the S8000, S8002, S8003, and S8006 BTS.

PrerequisitesNortel GSM BSS Documentation roadmap (411-9001-000)

It is recommended that the readers also become familiar with the followingtechnical documents:

Nortel GSM BSS Overview (411-9001-001)

Nortel GSM BSS Fault Management Maintenance Principles(411-9001-039)

Nortel GSM BTS S8000 / S8003 Troubleshooting (411-9001-048)

Nortel GSM BTS S8002 Troubleshooting (411-9001-084)

Nortel GSM BTS S8006 Troubleshooting (411-9001-085)

Nortel GSM BSC 12000HC/TCU 2G Fault Clearing (411-9001-101)

Nortel GSM BSS Fault Clearing Advanced Maintenance Procedures(411-9001-105)

Nortel GSM BSS Performance Management Observation CountersDictionary (411-9001-125)

Nortel GSM OMC-R Commands Reference Objects and Fault menus(411-9001-128)

Nortel GSM BSC 3000 / TCU 3000 Troubleshooting (411-9001-132)


411-9001-103 16.07 Standard


.


14/475

14 Introduction

NavigationThis document consists of 2 chapters:

Chapter 1 How to use this manual (page 19), "How to use thismanual", describes how to use this maintenance manual.

Chapter 2 S8000, S8002, S8003, and S8006 BTS fault numbers(page 23), "S8000, S8002, S8003, and S8006 BTS Fault Numbers",contains the fault number description and the corrective maintenanceprocedures applicable to the S8000, S8002, S8003 and S8006 BTS.

Safety regulationsIntroduction

All the following steps must be taken during the various cabinetmaintenance procedures in order to guarantee personnel and equipmentsafety.

Account must be taken of the following aspects:

general personnel safety instructions

equipment safety instructions

Precautionary messagesCaution, warning, and danger messages indicate possible risks.

CAUTIONImpact on the service and on the equipment

DANGERElectric shock

DANGEREnvironment and personnel protection

CAUTIONESDS handling precautions


411-9001-103 16.07 Standard


.


15/475

Safety regulations 15

Personnel and equipment safetyGeneral personnel safety instructions

The personnel must obey the safety instructions specific to the installationsite:

rules concerning the premises (see instructions posted on site or inthe building)

rules linked to the general personnel safety instructions

The personnel working on the cabinet must be authorized to workaccording to the security standards.

The cabinet main external power supply is switched off by opening thecircuit breaker on the operator box.

The mains power supply supplying the cabinet means that no work mustbe done on the cabinet internal wiring without first cutting its externalmains power supply.

This BTS has been evaluated under IEEE C95.1 requirements, regardingsafety levels with respect to human exposure to radio frequencyelectromagnetic fields, 3 kHz to 300 GHz.

The leakage fields and equivalent power densities are orders of magnitudeless than the maximum permissible exposures (MPEs) given in the IEEEsafety guidelines.

CAUTIONWorking instructionsThe personnel working on the cabinet must be authorized towork according to the security standards.

CAUTIONESDS handling precautionsDuring all maintenance interventions, and especially whenhandling the boards, the operator must wear an antistaticbracelet.

DANGERElectric shockNever replace a power supply when energized.

Equipment safety instructionsS8000 Outdoor BTS The maintenance of an S8000 Outdoor BTS ispossible up to -40 C (~ -40 F).


411-9001-103 16.07 Standard


.


16/475

16 Introduction

The BTS stays operational with the open doors at -10 C (~ -14 F) duringthree hours, and at -40 C (~ -40 F) during one hour.

In the case of rainy or snowy weather, do not open the cabinet doorswithout a tent set up beforehand.

DANGERElectric shockEnsure that the unused power cable for the Type F powersupply module is capped and secured before powering up theS8003 BTS and/or performing any maintenance procedure (seethe following figure).


411-9001-103 16.07 Standard


.


17/475

Safety regulations 17


411-9001-103 16.07 Standard


.


18/475

18 Introduction


411-9001-103 16.07 Standard


.


19/475

19.

Chapter 1 How to use this manual

1.1 IntroductionThis manual contains the fault number description and the correctivemaintenance procedures applicable to the S8000, S8002, S8003, andS8006 BTS for single band GSM 850, 900, 1800, 1900, E--GSM 900, andGSM-R 900 frequency bands. GSM-R does not apply to the S8006 BTS.

The general principles and messages required for BSS maintenance aredescribed in Nortel GSM BSS Fault Management - Maintenance Principles(411-9001-039).

The network maintenance is based on the graphical supervision of thenetwork.

It is also based on the identification and the replacement of faulty items ofequipment, using the alarms and the notifications.

This process is divided into two steps: locating and identifying the faulty items of equipment, using information

given in this manual

replacing the faulty items of equipment, using the replacementprocedures given in the manuals that describe the on-site procedures

When a faulty item of equipment sends an alarm to the OMC-R, thisalarm is identified by a fault number. This manual gives the proceduresassociated with the various fault numbers.

Throughout this document (or section, as it applies), the terms DRX,

e-DRX, DRX-ND3 and eDRX2 are used indistinctly as DRX unless thedocument makes a specific reference.

Alarm notifications and contents include specific information about theparticular type of equipment involved on the alarm. For example, alarmsrelated to DRX-ND3 will include this specific equipment type throughoutthe notification.


411-9001-103 16.07 Standard


.


20/475

20 Chapter 1 How to use this manual

V15.0 introduced EDGE and other important features, together withDRX-ND3 full differentiation. DRX-ND3 is not EDGE compatible. For allEDGE related alarms, the term DRXdoes not include DRX-ND3. Thisequipment type solves obsolescence problems with DRX.

1.2 The types of spontaneous messages1.2.1 Events detected by the BTS

The following are types of spontaneous message:

spontaneous messages indicating a hardware fault (fault number 1067)

spontaneous messages indicating a hardware fault without loss ofcapacity, triggering no defense actions on the part of the BSC. If thereare defense actions, they are local and controlled by the BTS (faultnumber 1067).

spontaneous messages sent as a warning and indicating a transientevent (fault number 1060)

spontaneous messages indicating the arrival of state changes on anequipment (fault number 1058)

1.2.2 Events detected by the BSCSpontaneous messages are sent by the BSC giving information on thestate of relationship with the BTS or part of it (1051, 1052, 1053, 1054,1055, 1059, 1073).

1.3 Description of a fault number sheet

A corrective maintenance sheet contains the following information: the header

the main body composed of eight main paragraphs explaining the faultnumber treatment

1.3.1 Header of the sheetThe header contains the following information:

the fault number and possibly the source

the alarm type

1.3.2 Main body of the sheetThe main body contains the following information:

Fault analysisThis paragraph describes the fault.

Reaction of the system


411-9001-103 16.07 Standard


.


21/475

1.4 Help 21

BSC defenseThis paragraph describes the defense actions taken by the BSC.

Impact on the serviceThis paragraph gives the consequences of the alarm for theservice.

TroubleshootingThis paragraph gives the procedures to be followed to repair the faultand return to the operational conditions.

Preliminary checksThese checks are used to ensure that the fault is confirmed andthat the messages identifying a faulty element are in the OMC-Rlogs before the start of repair work.

On-site maintenance (possibly using the OMC-R)This paragraph is used to start the repair work and to bring theexchanged element into correct operation.

Additional checksThis paragraph shows how to check that the fault has beencleared.

1.4 HelpThe system provides the user with help at any time. For an in-depthdiscussion of Help, refer to Nortel GSM OMC-R Commands Reference -Security, Administration, SMS-CB, and Help menus (411-9001-130).

There are two kinds of help available:

on-line help, available from theHelpmenu in the OMC-R Browserwindow, as well as other windows

theConsult BSS Documentationoption of the workstation workspacepop-up menu provides access to on-line BSS documentation storedon CD-ROM.

Both are provided on the same CD-ROM.

1.4.1 Loading the CD-ROMTo load the CD-ROM from the screen workspace menu, insert theCD-ROM in the OMC-R server and/or workstation CD-ROM drive.

Installation is complete when the light on the CD-ROM drive is no longerlit.


411-9001-103 16.07 Standard


.


22/475

22 Chapter 1 How to use this manual


411-9001-103 16.07 Standard


.


23/475

23.

Chapter 2 S8000, S8002, S8003, andS8006 BTS fault numbers

Throughout this document (or section, as it applies), the terms DRX,e-DRX, DRX-ND3 and eDRX2 are used indistinctly as DRX unless thedocument makes a specific reference.

Alarm notifications and contents include specific information about theparticular type of equipment involved on the alarm. For example, alarmsrelated to DRX-ND3 will include this specific equipment type throughoutthe notification.

V15.0 introduced EDGE and other important features, together withDRX-ND3 full differentiation. DRX-ND3 is not EDGE compatible. For allEDGE related alarms, the term DRXdoes not include DRX-ND3. Thisequipment type solves obsolescence problems with DRX.

2.1 Fault number: 1051 (S8000, S8002, S8003, and S8006 BTS)Fault number:

1051 : Loss of layer 3 with remote GSM entity

Type : communicationsAlarm

This problem is associated with a PCM fault. See 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced Maintenance Procedures)

2.2 Fault number: 1052 (S8000, S8002, S8003, and S8006 BTS)

Fault number:

1052 : GSM entity downloading failure

Type : communicationsAlarm/processingErrorAlarm/equipmentAlarm

FAULT ANALYSIS

This message identifies the impacted element but not the faulty element. Itindicates a software downloading error concerning a transceiverEquipmentobject or a btsSiteManager object.


411-9001-103 16.07 Standard


.


24/475

24 Chapter 2 S8000, S8002, S8003, and S8006 BTS fault numbers

All the software downloading attempts are indicated, as well as the sourceof their failure.

The followingTable 1 "Fault number 1052 sources" (page 24) indicatesall the sources of the fault number 1052 for the S8000 Outdoor and

Indoor BTSs with the BCF or CBCF, the S8002 BTSs, the S8003 indoorBTSs, and the S8006 BTSs. For more information on each source, referto the indicated paragraph to know the corrective maintenance procedureassociated with this source.

Table 1Fault number 1052 sources

Source No. Source wording Paragraph

0 No response to status request -

1 Bad hardware reference of manufacturer ID 2.2.1 Source 1: Bad

hardware referenceof manufacturer ID

(page 29)

2 SUP stop receipt -

3 No change to one of BOOT states after reset 2.2.2 Source 3: Nochange to one of BOOTstates after reset (page

32)

4 This entity is engaged in another downloading 2.2.6 Source4: This entity is

engaged in anotherdownloadingSource 8:

Wrong software referenceon a non downloadable

TEI (page 43)

5 Software not compatible with hardware 2.2.3 Source 5: Softwarenot compatible with

hardware (page 35)

6 File access error 2.2.4 Source 6: Fileaccess error (page 39)

7 Repetitive errors (NACK, timeout, ... ) whiledownloading a file

2.2.5 Source 7:Repetitive errors (NACK,

timeout, ...) while

downloading a file(page 42)


411-9001-103 16.07 Standard


.


25/475


Table 1Fault number 1052 sources (contd.)


8 Wrong software reference on a non downloadable TEI 2.2.6 Source

4: This entity isengaged in another

downloadingSource 8:Wrong software reference

on a non downloadableTEI (page 43)

14 CSM load container negative acknowledgement -

15 File to download empty -

16 File to download unavailable 2.2.8 Source 16: File todownload unavailable

(page 48)

17 Buffer allocation failure -

18 Bad sending buffer size value -

19 Failure during OMU switchover -

20 Bad TEI sent by BTS in the csm software update reportmessage

-

21 Csm software update report with the cause "unknownTEI"

-

22 Csm software update report with the cause "equipmentfailure"

-

23 Csm software update report with the cause"downloading failure"

-

24 Csm software update report with the cause "not ableto perform"

-

25 Csm software update report with the cause "wrong softref"

-

26 Csm software update report with the cause "wrongconfig ref"

-

27 Csm software update report with the cause "restartrequest"

-

28 Csm software update report with the cause "data

inconsistency"

-

29 Csm software update report with the cause "messageout of sequence"

-

30 Csm software update report with the cause

"background not available"

-


411-9001-103 16.07 Standard


.


26/475




31 Csm software update report with the cause

"incompatible RM version"

-

32 Csm software update report with the cause"downloading in progress"

-

33 Bad report sent by BTS in the csm software updatereport message

-

34 no BTS response on csm software update init/controlmessage

-

35 nack received on the abort requested by operator -

36 bad report sent by BTS in the csm software updateabort message

-

37 no BTS response on csm software update abortmessage

-

38 flash activate nack with the cause "unknown TEI" -

39 flash activate nack with the cause "equipment failure" -

40 flash activate nack with the cause "downloading failure" -

41 flash activate nack with the cause "not able to perform" -

42 flash activate nack with the cause "flash inconsistency" -

43 flash activate nack with the cause "data inconsistency" -

44 flash activate nack with the cause "wrong soft ref" -

45 flash activate nack with the cause "wrong config ref" -

46 csm downloading start nack with the cause "unknownTEI"

-

47 csm downloading start nack with the cause "equipmentfailure"

-

48 csm downloading start nack with the cause"downloading failure"

-

49 csm downloading start nack with the cause "messageout of sequence"

-

50 csm downloading start nack with the cause "wrong soft

ref"

-

51 csm downloading start nack with the cause "wrongconfig ref"

-

52 csm downloading start nack with a bad cause -

53 no BTS response on csm downloading start message -


411-9001-103 16.07 Standard


.


27/475




54 csm downloading end nack with the cause "unknown

TEI"

-

55 csm downloading end nack with the cause "equipmentfailure"

-

56 csm downloading end nack with the cause"downloading failure"

-

57 csm downloading end nack with the cause "value outof range"

-

58 csm downloading end nack with a bad cause -

59 no BTS response on csm downloading end message -

60 csm load init nack with the cause "equipment failure" -

61 csm load init nack with the cause "downloading failure" -

62 csm load init nack with the cause "message out ofsequence"

-

63 csm load init nack with the cause "wrong file ref" -

64 csm load init nack with the cause "window size notallow"

-

65 csm load init nack with the cause "data format error" -

66 csm load init nack with a bad cause -

67 no BTS response on csm load init message -

68 csm load data nack with the cause "equipment failure" -

69 csm load data nack with the cause "downloadingfailure"

-

70 csm load data nack with the cause "message out ofsequence"

-

71 csm load data nack with the cause "data format error" -

72 csm load data nack with the cause "window overflow" -

73 csm load data nack with the cause "data inconsistency" -

74 csm load data nack with the cause "block not received" -

75 csm load data nack with the cause "bad block tag" -

76 csm load data nack with the cause "checksum error" -

77 csm load data nack with a bad cause -

78 unexpected csm load data ack -

79 no BTS response on csm load data message -

80 csm load end nack with the cause "equipment failure" -


411-9001-103 16.07 Standard


.


28/475




81 csm load end nack with the cause "downloading failure" -

82 csm load end nack with the cause "value out of range" -

83 csm load end nack with the cause "message out of

sequence"

-

84 csm load end nack with the cause "data format error" -

85 csm load end nack with the cause "wrong file ref" -

86 csm load end nack with the cause "data inconsistency" -

87 csm load end nack with the cause "checksum error" -

88 csm load end nack with a bad cause -

89 no BTS response on csm load end message -

90 bad report sent by BTS during an internal update -

91 csm load init nack with the cause "file already open" -

92 csm load init nack with the cause "invalid mode" -

93 csm load init nack with the cause "file cannot beunloaded"

-

94 csm load init nack with the cause "flash flag cannotaccess"

-

95 csm load data nack with the cause "file cannot beunloaded"

-

96 csm load data nack with the cause "flash flag cannotaccess" -

97 csm load data nack with the cause "boot cannot beunloaded"

-

98 csm load data nack with the cause "data decod error" -

99 csm load data nack with the cause "table cannotaccess"

-

100 csm load data nack with the cause "ram mapping error" -

101 csm load data nack with the cause "flash access error" -

102 csm load data nack with the cause "flash ram error" -

103 csm load data nack with the cause "flash erase error" -

104 csm load data nack with the cause "internal abort" -

REACTION OF THE SYSTEM

BSC defense


411-9001-103 16.07 Standard


.


29/475


The BSC attempts a maximum of five BCF or TRX software downloading.If the five attempts fail, the BSC sends a fault number 1052 and a statechange on the btsSiteManager object to "disabled-failed".

Impact on the service

For the btsSiteManager objectThe site is not downloaded.

CAUTIONService interruption

For the transceiverEquipment objectThe TRX is not downloaded. One TDMA is not configured.

CAUTION

Service reduction

2.2.1 Source 1: Bad hardware reference of manufacturer ID

Fault number 1052 : GSM entity downloading failure

Source: (1) Bad hardware reference of manufacturer ID

BTS model: S8000 Outdoor + S8000 Indoor + S8002 + S8003

+ S8006

FAULT ANALYSISThis source indicates that the first downloading attempt failed.

The alarm indicates that the "hardwareRef" parameter, obtained byperforming the "Display" command on the btsSiteManager object andthe transceiverEquipment object, is not in accordance with the PROMnumbers on the boards.

TROUBLESHOOTING

Step Action

Preliminary checks

1 Look at the notification and identify the object concerned.

If the btsSiteManager object is concerned, go to step 2.

If the transceiverEquipment object is concerned, go to step 3.


411-9001-103 16.07 Standard


.


30/475


2 Check the state of the site by performing the "Display all"command on the btsSiteManager object.

If the operationalState of the btsSiteManager object is"enabled", the site is operational.

Clear the alarm. The procedure is complete.

If the operationalState of the btsSiteManager object is"disabled-dependency", the site is not operational. Look foran object whose state is "disabled-failed".

If a pcmCircuit object is "disabled-failed", look for a faultnumber concerning PCMs (see 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures) ).

If a lapdLink object is "disabled-failed", the BSC isconcerned. Look for alarms concerning the BSC .

If the operationalState of the btsSiteManager object is"disabled-failed", the site is not operational.

If the fault number 1052 is the only alarm, treat the alarm.

Otherwise, if there are other alarms, set thebtsSiteManager object to "locked" and then to"unlocked" to confirm the problem.

If the fault number 1052 is still present, treat it (seeabove).

If other fault numbers are present, such as faultnumber 1054, treat them (concerning fault number1054 (loss of layer 2), refer to 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures) ).

If the operationalState of the btsSiteManager object is"disabled", the site is not operational. Do not treat thealarm and do not clear it. Wait for a state change of thebtsSiteManager object.

3 Check the state of the TRX by performing the "Display all"command on the transceiverEquipment object.

If the operationalState of the transceiverEquipment object is"enabled", the TRX is operational.

Clear the alarm.

The procedure is complete.

If the operationalState of the transceiverEquipment object is"disabled-dependency", the TRX is not operational.Look for a parent object which is not operational.


411-9001-103 16.07 Standard


.


31/475


If a bts object is "disabled-dependency", look for alarmsconcerning cells.

If the btsSiteManager object is "disabled-failed", the siteis not operational. Treat the alarm(s) concerning thebtsSiteManager object.


If a lapdLink object is "disabled-failed", the BSC isconcerned. Look for alarms concerning the BSC.

If the operationalState of the transceiverEquipment object is"disabled-failed", the TRX is not operational.

If the fault number 1052 is the only alarm, treat the alarm.Go to step 6.

Otherwise, if there are other alarms, set thetransceiverEquipment object to "locked" and thento "unlocked" to confirm the problem.


If other fault numbers are present, such as faultnumber 1054, treat them (concerning fault number1054 (loss of layer 2), refer to 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures)).

If the operationalState of the transceiverEquipment objectis "disabled", the TRX is not operational. Do not treat thealarm and do not clear it. Wait for a state change of thetransceiverEquipment object.

For the btsSiteManager object4 Set the value of the "hardwareRef" parameter to "0".

5 The procedure is complete.

For the transceiverEquipment object6 Modify the value of the "hardwareRef" parameter: set it to "0".


--End--


411-9001-103 16.07 Standard


.


32/475


2.2.2 Source 3: No change to one of BOOT states after reset


Source: (3) No change to one of BOOT states after reset


+ S8006

TROUBLESHOOTING

Step Action

Preliminary checks1 Look at the notification and identify the object concerned.




If the operationalState of the btsSiteManager object is"enabled", the site is operational. Clear the alarm and go tostep 8.


If a pcmCircuit object is "disabled-failed", look for a faultnumber concerning PCMs (see 411-9001-105 (Nortel

GSM BSS Fault Clearing - Advanced MaintenanceProcedures)).

If an lapdLink object is "disabled-failed", the BSC isconcerned. Look for alarms concerning the BSC.

If the operationalState of the btsSiteManager object is"disabled-failed", and if there are other alarms which couldimpact the operation of the site, lock the btsSiteManagerobject and then unlock it. If the alarm with the fault number1052 and the source 3 is still present, treat the alarm. Go tostep 4.If other fault numbers are present, such as fault number1054, treat them. Concerning fault number 1054 (loss of layer

2), see 411-9001-105 (Nortel GSM BSS Fault Clearing -Advanced Maintenance Procedures)



411-9001-103 16.07 Standard


.


33/475




Clear the alarm. The procedure is complete.




If a pcmCircuit object is "disabled-failed", look for a faultnumber concerning PCMs (see 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures)).




Otherwise, if there are other alarms, set the

transceiverEquipment object to "locked" and thento "unlocked" to confirm the problem.



If the operationalState of the transceiverEquipment objectis "disabled" the TRX is not operational. Do not treat thealarm and do not clear it. Wait for a state change of thetransceiverEquipment object.

On-site maintenance using the OMC-R4 Set the operationalState of the entity concerned to "locked" then

"unlocked" to restart the downloading.

If the alarm persists, check if the source 1 appears.


411-9001-103 16.07 Standard


.


34/475


If the source 1 appears, treat it. See Paragraph2.2.1Source 1: Bad hardware reference of manufacturer ID(page 29).

If the source 1 does not appear, go to step 5 if thebtsSiteManager object is concerned, or step 6 if the

transceiverEquipment object is concerned.

If the alarm has disappeared, the downloading has restarted.Go to step 8.

5 Reset the following items of equipment:

for the S8000 BTS, the active CSWM board of the BCF or theactive CMCF board of the CBCF

for the S8002 BTS and the S8006 BTS, the active CMCFboardIf the alarm persists, go to step 7. Otherwise, go to step 8.

6 Reset the DRXs.

If the alarm persists, go to step 7. Otherwise, go to step 8.

7 Replace successively the following items of equipment until thealarm disappears:

for the S8000 BTS:

the active CSWM board (Field Replaceable Unit) ofthe BCF: refer to 411-9001-048 (Nortel GSM BTSS8000/S8003 Troubleshooting)

or the active CMCF board (Field Replaceable Unit) of

the CBCF: refer to 411-9001-048 (Nortel GSM BTSS8000/S8003 Troubleshooting)

then, if necessary, the DRXs (Field Replaceable Unit):refer to 411-9001-048 (Nortel GSM BTS S8000/S8003Troubleshooting)

for the S8002 BTS:

the active CMCF board (Field Replaceable Unit) of theCBCF: refer to 411-9001-084 (Nortel GSM BTS S8002Troubleshooting)

then, if necessary, the DRXs (Field ReplaceableUnit): refer to 411-9001-084 (Nortel GSM BTS S8002

Troubleshooting)

for the S8003 BTS:


411-9001-103 16.07 Standard


.


35/475


the active CMCF board (Field Replaceable Unit) ofthe CBCF: refer to 411-9001-048 (Nortel GSM BTSS8000/S8003 Troubleshooting).

then, if necessary, the DRXs (Field Replaceable Unit):refer to 411-9001-048 (Nortel GSM BTS S8000/S8003

Troubleshooting).

for the S8006 BTS:

the active CMCF board (Field Replaceable Unit) of theCBCF: refer to 411-9001-085 (Nortel GSM BTS S8006Troubleshooting)

then, if necessary, the DRXs (Field ReplaceableUnit): refer to 411-9001-085 (Nortel GSM BTS S8006Troubleshooting)

If the alarm has disappeared, go to step 8. Otherwise, call themanufacturer.


--End--

2.2.3 Source 5: Software not compatible with hardware


Source: (5) Software not compatible with hardware

BTS model: S8000 Outdoor + S8000 Indoor + S8002 + S8003+ S8006

TROUBLESHOOTING

Step Action

Preliminary checks



If the transceiverEquipment object is concerned, checkwhether the "DRX automatic downloading" is activated or not:

If the "DRX automatic downloading" is activated, go tostep 8.

If the "DRX automatic downloading" is not activated, goto step 3.



411-9001-103 16.07 Standard


.


36/475



If the operationalState of the btsSiteManager object is"disabled-dependency", the site is not operational. Look for

an object whose state is "disabled-failed".


If an lapdLink object is "disabled-failed", the BSC isconcerned. Look for alarms concerning the BSC .

If the operationalState of the btsSiteManager object is"disabled-failed", and if there is an alarm with the faultnumber 1054, followed by alarms with fault numbers 1051,1052, 1053, lock the btsSiteManager object, and then unlockit. If the alarm with the fault number 1052 and the source 5 isstill present, treat the alarm. Go to step 4.Otherwise, refer to the fault number 1054 (loss of layer2) (see 411-9001-105 (Nortel GSM BSS Fault Clearing -Advanced Maintenance Procedures)).


3 Check the state of the TRX by performing the "Display all"

command on the transceiverEquipment object. If the operationalState of the transceiverEquipment object is

"enabled", the TRX is operational.

Clear the alarm.





If a pcmCircuit object is "disabled-failed", look for a faultnumber concerning PCMs (see 411-9001-105 (Nortel


411-9001-103 16.07 Standard


.


37/475


GSM BSS Fault Clearing - Advanced MaintenanceProcedures) ).






If other fault numbers are present, such as faultnumber 1054, treat them (concerning fault number

1054 (loss of layer 2), refer to 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures)).


On-site maintenance using the OMC-R

4 Check that the value of the "hardwareRef" parameter isconsistent with the PROM numbers on the boards, by performinga "Display" command on the btsSiteManager object.

If the value of the "hardwareRef" parameter is set to 0:

set the btsSiteManager object to "locked"

set the value of the "hardwareRef" parameter to the oneindicated in the notification

set the btsSiteManager object to "unlocked"

If the value of the "hardwareRef" parameter is correct, go tostep 5.

5 Ensure the EFT is correct by checking the value of the"swVersionRunning" parameter by performing the "Display"command on the software object associated with the bsc object.

If this is the case, set the object concerned to "locked" then"unlocked".

If the alarm persists, call the manufacturer.

If the alarm has disappeared, go to step 8.

If this is not the case, go to step 6.


411-9001-103 16.07 Standard


.


38/475


6 Set the object concerned to "locked".

7 Download the correct EFT on the item of equipment accordingto the following values.

Field Meaning Value

XXX Type of software BCF : CBCTRX : DRX/CDR/EDG

ab Version number [00 .. 32]

c Sub-version number CBC : [A .. H]DRX : [A .. H]CDR : [A .. H]EDG : [A .. H]

d Edition number CBC : [1 .. 8]DRX : [1 .. 8]CDR : [1 .. 8]EDG : [1 .. 8]

ef Revision factor CBC : [0 .. 32]DRX : [0 .. 32]CDR : [0 .. 32]EDG : [0 .. 32]

If the name of the EFT is correct, call the manufacturer.

Otherwise, modify the value and set the object concerned to"unlocked".

8 If the "Automatic downloading" is activated, the OMC-R starts toperform the downloading just after it received fault number 1052

cause 5:a The OMC-R reads the BTS hardware reference quoted in the

fault number.

b The OMC-R deduces the name of the EFT to be downloadedfrom a correspondence table.

c The OMC-R searches for the EFT in its database:

If it does not find one, the OMC-R goes to step 9.

If it finds one and only one, the OMC-R goes to step 10.

If it finds more than one, it lets the operator choose.

A critical alarm with fault number 30076 is emittedto report that the automatic downloading failed (see411-9001-032 (Nortel GSM OMC-R Routine Maintenanceand Troubleshooting)).

9 The OMC-R searches for the delivery name of the BTS the DRXbelongs to. Then, for all BTS with the same delivery name underthe same BSC, the OMC-R searches for the right EFT.


411-9001-103 16.07 Standard


.


39/475


If it finds one and only one, it selects it. Then it goes to step10.

If it does not find one, the OMC-R searches for an EFTsuitable to all the BTS with the same delivery name in all theBSC.

If it finds one and only one, it selects it. Then it goes tostep 10.

If it finds more than one, or none, it lets the operatorchoose. A critical alarm with fault number 30076 isemitted to report that the automatic downloading failed(see 411-9001-032 (Nortel GSM OMC-R RoutineMaintenance and Troubleshooting)).

10 The OMC-R starts to download the selected EFT:

a If necessary, it downloads the selected EFT to the BSC disc.

b It locks the related transceiverEquipment object instance

c It sets the sWVersionNew parameter of the newtransceiverEquipment software object with the new EFTname.

d It activates the new version.

e It unlocks the related transceiverEquipment object instance.

f As a consequence, the fault number 1052 with cause 5 isautomatically cleared.


--End--

2.2.4 Source 6: File access error


Source: (6) File access error


FAULT ANALYSIS

This source indicates that the first downloading attempt has failed. TheBSC does not find the software files in one partition of its hard disk.

TROUBLESHOOTING

Step Action

Preliminary checks


411-9001-103 16.07 Standard


.


40/475








If a pcmCircuit object is "disabled-failed", look for a faultnumber concerning PCMs (see 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced Maintenance

Procedures)). If an lapdLink object is "disabled-failed", the BSC is

concerned. Look for alarms concerning the BSC.

If the operationalState of the btsSiteManager object is"disabled-failed", and if there are other alarms which couldimpact the operation of the site, lock the btsSiteManagerobject, and then unlock it.

If the alarm with the fault number 1052 and the source 6is still present, treat the alarm. Go to step 4.

Otherwise, if there are other alarms, such as fault number

1054, treat them (concerning fault number 1054 (loss oflayer 2), refer to 411-9001-105 (Nortel GSM BSS FaultClearing - Advanced Maintenance Procedures) ).




Clear the alarm.




411-9001-103 16.07 Standard


.


41/475










If other fault numbers are present, such as faultnumber 1054, treat them (concerning fault number1054 (loss of layer 2), refer to 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures) ).


On-site maintenance using the OMC-R4 Download the software from the MD at the OMC-R to the BSC

disk partition:

To download a BCF software, refer to the downloadingprocedure.

To download a TRX software, refer to the downloadingprocedure.

Lock the object concerned (either btsSiteManager ortransceiverEquipment object).

Unlock the object concerned.

If the alarm has disappeared, go to step 6 .

If the alarm persists:


411-9001-103 16.07 Standard


.


42/475


For the BSC 12000HC, go to step 5.

For the BSC 3000, call the manufacturer.

5 Perform a BSC chain switchover.

If the alarm has disappeared, go to step 6. If the alarm persists, call the manufacturer.


--End--

2.2.5 Source 7: Repetitive errors (NACK, timeout, ...) whiledownloading a file


Source: (7) Repetitive errors (NACK, timeout, ...) whiledownloading a file


FAULT ANALYSISThis source indicates that the downloading failed after repetitivedownloading errors. The probable cause could be corresponding softwarecorrupted in BTS active BSC corruption.

TROUBLESHOOTING

Step Action

Preliminary checks1 Perform a BSC chain switchover.

Lock and unlock the btsSiteManager.


If the alarm persists, go to step 2.

2 Lock the btsSiteManager

Cleanup the corresponding BTS software from BSC. Download the software from the MD at the OMC-R to the

BSC disk partition.

Activate the software.

Unlock the btsSiteManager.


411-9001-103 16.07 Standard


.


43/475



--End--

2.2.6 Source 4: This entity is engaged in another downloadingSource 8: Wrong software reference on a non downloadable TEI


Source: (4) This entity is engaged in another downloading

Source: (8) Wrong software reference on a nondownloadable TEI


TROUBLESHOOTING

Step Action

Preliminary checks




2 Check the state of the site by performing a "Display all"command on the btsSiteManager object.





If the operationalState of the btsSiteManager object is"disabled-failed", and if there are other alarms which couldimpact the operation of the site, lock the btsSiteManagerobject, and then unlock it.


411-9001-103 16.07 Standard


.


44/475


If the alarm with the fault number 1052 and the source 4or 8 is still present, treat the alarm. Go to step 4.

Otherwise, if there are other alarms, such as fault number1054, treat them (concerning fault number 1054 (lossof layer 2), see 411-9001-105 (Nortel GSM BSS Fault

Clearing - Advanced Maintenance Procedures)




Clear the alarm.









Otherwise, if there are other alarms, set the

transceiverEquipment object to "locked" and thento "unlocked" to confirm the problem.


If other fault numbers are present, such as faultnumber 1054, treat them (concerning fault number1054 (loss of layer 2), refer to 411-9001-105 (Nortel


411-9001-103 16.07 Standard


.


45/475


GSM BSS Fault Clearing - Advanced MaintenanceProcedures) ).

If the operationalState of the transceiverEquipment objectis "disabled" the TRX is not operational. Do not treat thealarm and do not clear it. Wait for a state change of the

transceiverEquipment object.


4 Restart the active board of the BCF.


If the alarm persists:







--End--

2.2.7 Source 14: Received CSM LOAD CONTAINER NAK


Source: (14) Received CSM LOAD CONTAINER NAKBTS model: S8000 Outdoor + S8000 Indoor + S8002 + S8003

+ S8006

FAULT ANALYSISThis message is received after attempts to download the software arefailed by the BSC. This source is because the Load file of TRX/BCFresiding in the BSC is corrupt.

TROUBLESHOOTING

Step Action

Preliminary checks

1 Check the notification and identify the object concerned.




411-9001-103 16.07 Standard


.


46/475


2 Check the state of the site by performing the Display allcommand on the btsSiteManager object.





If the operationalState of the btsSiteManager object is

"disabled-failed", and if there are other alarms which couldimpact the operation of the site, lock the btsSiteManagerobject, and then unlock it.

If the alarm with the fault number 1052 and the source 6 ispresent, treat the alarm. Go to step 4.

if there are other alarms, such as fault number 1054, treatthem (concerning fault number 1054 (loss of layer 2), see411-9001-105 (Nortel GSM BSS Fault Clearing - AdvancedMaintenance Procedures)

If the operationalState of the btsSiteManager object is"disabled", the site is not operational. Do not treat the

alarm and do not clear it. Wait for a state change of thebtsSiteManager object.



Clear the alarm.


If the operationalState of the transceiverEquipment object is

"disabled-dependency", the TRX is not operational.Look for a parent object that is not operational.




411-9001-103 16.07 Standard


.


47/475



If an lapdLink object is "disabled-failed", the BSC is

concerned. Look for alarms concerning the BSC.






If the operationalState of the transceiverEquipment objectis "disabled", the TRX is not operational. Do not treat thealarm and do not clear it. Wait for a state change of thetransceiverEquipment object.


4 Re-download the software from the MD at the OMC--R to theBSC disk partition:

To download a BCF software, refer to the downloadingprocedure.

To download a TRX software, refer to the downloadingprocedure.

5 Lock the object concerned (either btsSiteManager ortransceiverEquipment object).

6 Unlock the object concerned.



--End--


411-9001-103 16.07 Standard


.


48/475


2.2.8 Source 16: File to download unavailable


Source: (16) File to download unavailable


+ S8006

FAULT ANALYSISThis source indicates that the downloading attempt has failed becausethe file to be downloaded cannot be found in the catalog file (eitherbecause the catalog file itself is not valid, or the name of the file has beenimproperly copied in the BTS or BSC software).

TROUBLESHOOTING

Step Action

Preliminary checks

1 Cleanup the load from BTS partition of active BSC hard disk.Download the software from the MD at the OMC-R to the BSCdisk partition:

To download a BCF software, refer to the downloadingprocedure in 411-9001-034 (Nortel GSM BSS Configuration -Operating Procedures).

To download TRX software, refer to the downloadingprocedure in 411-9001-034 (Nortel GSM BSS Configuration -Operating Procedures).

Lock the object concerned (either btsSiteManager ortransceiverEquipment object).

Unlock the object concerned.


If the alarm persists, go to step 2.

2 Perform one of the following:







411-9001-103 16.07 Standard


.


49/475



--End--

2.3 Fault number: 1053 (S8000, S8002, S8003, and S8006 BTS)Fault number:

1053 : GSM entity configuration regression

Type : qualityOfServiceAlarm

FAULT ANALYSIS

The BSC detects a difference of the state between that known by the BSCand that received from the BTS after a status request.

REACTION OF THE SYSTEM

BSC defense

The BSC tries to restart the BTS (either the btsSiteManager object or thetransceiverEquipment object), to download it, and to reconfigure it.

Impact on the service

For the btsSiteManager object

CAUTIONService interruption

For as long as the operationalState of the btsSiteManagerobject is "disabled-failed", the site is lost. No service isprovided.

For the transceiverEquipment object

CAUTIONService reductionFor as long as the operationalState of the transceiverEquip

ment object is "disabled", the TRX and one TDMA are lost.The service is reduced.

TROUBLESHOOTING

Step Action

Preliminary checks

1 Look for a fault number 1067 concerning an item of equipment ofthe object mentioned in the alarm (fault number 1053).


411-9001-103 16.07 Standard


.


50/475


If there is an alarm with the fault number 1067 concerning theCSW1/CSW2 boards, treat the alarm with the fault number1067 first.

If there is an alarm with the fault number 1067 concerningthe transceiverEquipment object (frame processor or RX

module), treat the alarm with the fault number 1067 first.

If there are no alarms with the fault number 1067, go to step2.

2 Check the state of the site by performing a "Display all"command on the btsSiteManager object.


If the operationalState of the btsSiteManager object is

"disabled-dependency", the site is not operational. Look foran object whose state is "disabled-failed".



If the operationalState of the btsSiteManager object is"disabled-failed", the site is not operational. Go to step 3.


3 Wait for the end of restart. Then look for the origin of theproblem by analyzing the notification log and looking at

BTS 8000 Fault Finding.pdf

Documents

Transcript of BTS 8000 Fault Finding.pdf