GSM BTS S8000 S8002 S8003 S8006 Fault Clearing

7/21/2019 GSM BTS S8000 S8002 S8003 S8006 Fault Clearing

1/766

Global System for Mobile Communications (GSM)

Nortel GSM BTSS8000/S8002/S8003/S8006Fault ClearingRelease: V18.0 PC2Document Revision: 18.06

www.nortel.com

411-9001-103.


2/766


3/766

3.

Contents

New in this release 17Features 17

Introduction 19

Chapter 1 How to use this manual 25

1.1 Introduction 251.2 The types of spontaneous messages 26

1.2.1 Events detected by the BTS 26

1.2.2 Events detected by the BSC 26

1.3 Description of a fault number sheet 26

1.3.1 Header of the sheet 26

1.3.2 Main body of the sheet 26

1.4 Help 27

1.4.1 Loading the CD-ROM 27

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

numbers 292.1 Fault number: 1051 (S8000, S8002, S8003, and S8006 BTS) 292.2 Fault number: 1052 (S8000, S8002, S8003, and S8006 BTS) 29

2.2.1 Source 0: No response to status request 41

2.2.2 Source 1: Bad hardware reference of manufacturer ID 43

2.2.3 Source 2: SUP stop receipt 46

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

2.2.5 Source 4: This entity is engaged in another downloadingSource 8: Wrongsoftware reference on a non downloadable TEI 52

2.2.6 Source 5: Software not compatible with hardware 54

2.2.7 Source 6: File access error 58

2.2.8 Source 7: Repetitive errors (NACK, timeout, ...) while downloading afile 61

2.2.9 Source 9: No response to download message 61

2.2.10 Source 14: Received CSM LOAD CONTAINER NAK 64

2.2.11 Source 15: File to download empty 66

2.2.12 Source 16: File to download unavailable 68

2.2.13 Source 17: Buffer allocation failure 69

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

411-9001-103 18.06 20 January 2010

Copyright 1999-2009 Nortel Networks. All Rights Reserved.


4/766

4

2.2.14 Source 18: Bad sending buffer size value 72

2.2.15 Source 19: Failure during OMU switchover 74

2.2.16 Source 20: Bad TEI sent by BTS in the CSM software update reportmessage 76

2.2.17 Source 21: CSM software update report with the cause - unknown TEI

- 78

2.2.18 Source 22: CSM software update report with the cause - equipmentfailure - 81

2.2.19 Source 23: CSM software update report with the cause - downloadingfailure - 83

2.2.20 Source 24: CSM software update report with the cause - not able toperform- 85

2.2.21 Source 25: CSM software update report with the cause - wrong softwarereference - 87

2.2.22 Source 26: CSM software update report with the cause - wrongconfiguration reference - 90

2.2.23 Source 27: CSM software update report with the cause - restart request- 92

2.2.24 Source 28: CSM software update report with the cause - data

inconsistency - 94

2.2.25 Source 29: CSM software update report with the cause - message out ofsequence - 97

2.2.26 Source 30: CSM software update report with the cause - background notavailable - 99

2.2.27 Source 31: CSM software update report with the cause - incompatibleRM version - 101

2.2.28 Source 32: CSM software update report with the cause - downloading inprogress - 104

2.2.29 Source 33: Bad report sent by BTS in the CSM software update reportmessage 106

2.2.30 Source 34: No BTS response on CSM software update init-controlmessage 108

2.2.31 Source 35: Nack received on the abort requested by operator 111

2.2.32 Source 36: Bad report sent by BTS in the CSM software update abortmessage 113

2.2.33 Source 37: No BTS response on CSM software update abortmessage 115

2.2.34 Source 38: Flash activate nack with the cause - unknown TEI - 118

2.2.35 Source 39: Flash activate nack with the cause - equipment failure

- 1202.2.36 Source 40: Flash activate nack with the cause - downloading failure

- 122

2.2.37 Source 41: Flash activate nack with the cause - not able to perform- 124

2.2.38 Source 42: Flash activate nack with the cause - flash inconsistency- 127

2.2.39 Source 43: Flash activate nack with the cause - data inconsistency


411-9001-103 18.06 20 January 2010



5/766

5

- 129

2.2.40 Source 44: Flash activate nack with the cause - wrong soft ref - 131

2.2.41 Source 45: Flash activate nack with the cause - wrong config ref - 133

2.2.42 Source 46: CSM downloading start nack with the cause - unknown TEI- 136

2.2.43 Source 47: CSM downloading start nack with the cause - equipment

failure - 138

2.2.44 Source 48: CSM downloading start nack with the cause - downloadingfailure - 140

2.2.45 Source 49: CSM downloading start nack with the cause - message outof sequence - 142

2.2.46 Source 50: CSM downloading start nack with the cause - wrong soft ref- 145

2.2.47 Source 51: CSM downloading start nack with the cause - wrong configref - 147

2.2.48 Source 52: CSM downloading start nack with a bad cause 149

2.2.49 Source 53: No BTS response on CSM downloading start message 1522.2.50 Source 54: CSM downloading end nack with the cause - unknown TEI

- 154

2.2.51 Source 55: CSM downloading end nack with the cause - equipmentfailure - 156

2.2.52 Source 56: CSM downloading end nack with the cause - downloading

failure - 158

2.2.53 Source 57: CSM downloading end nack with the cause - value out ofrange - 161

2.2.54 Source 58: CSM downloading end nack with a bad cause 163

2.2.55 Source 59: No BTS response on CSM downloading end message 165

2.2.56 Source 60: CSM load init nack with the cause - equipment failure - 1682.2.57 Source 61: CSM load init nack with the cause - downloading failure

- 170

2.2.58 Source 62: CSM load init nack with the cause - message out ofsequence - 172

2.2.59 Source 63: CSM load init nack with the cause - wrong file ref - 174

2.2.60 Source 64: CSM load init nack with the cause - window size not allowed- 177

2.2.61 Source 65: CSM load init nack with the cause - data format error - 179

2.2.62 Source 66: CSM load init nack with a bad cause 181

2.2.63 Source 67: No BTS response on CSM load init message 183

2.2.64 Source 68: CSM load data nack with the cause - equipment failure- 186

2.2.65 Source 69: CSM load data nack with the cause - downloading failure- 188

2.2.66 Source 70: CSM load data nack with the cause - message out ofsequence - 190

2.2.67 Source 71: CSM load data nack with the cause - data format error- 192


411-9001-103 18.06 20 January 2010



6/766

6

2.2.68 Source 72: CSM load data nack with the cause - window overflow- 195

2.2.69 Source 73: CSM load data nack with the cause - data inconsistency- 197

2.2.70 Source 74: CSM load data nack with the cause - block not received

- 1992.2.71 Source 75: CSM load data nack with the cause - bad block tag - 201

2.2.72 Source 76: CSM load data nack with the cause - checksum error - 204

2.2.73 Source 77: CSM load data nack with a bad cause 206

2.2.74 Source 78: Unexpected CSM load data ack 208

2.2.75 Source 79: No BTS response on CSM load data message 210

2.2.76 Source 80: CSM load end nack with the cause - equipment failure- 213

2.2.77 Source 81: CSM load end nack with the cause - downloading failure- 215

2.2.78 Source 82: CSM load end nack with the cause - value out of range

- 2172.2.79 Source 83: CSM load end nack with the cause - message out of

sequence - 219

2.2.80 Source 84: CSM load end nack with the cause - data format error- 222

2.2.81 Source 85: CSM load end nack with the cause - wrong file ref - 224

2.2.82 Source 86: CSM load end nack with the cause - data inconsistency- 226

2.2.83 Source 87: CSM load end nack with the cause - checksum error - 229

2.2.84 Source 88: CSM load end nack with a bad cause 231

2.2.85 Source 89: No BTS response on CSM load end message 233

2.2.86 Source 90: Bad report sent by BTS during an internal update 2352.2.87 Source 91: CSM load init nack with the cause - file already open - 238

2.2.88 Source 92: CSM load init nack with the cause - invalid mode - 240

2.2.89 Source 93: CSM load init nack with the cause - file cannot be unloaded- 242

2.2.90 Source 94: CSM load init nack with the cause - flash flag cannot access- 244

2.2.91 Source 95: CSM load data nack with the cause - file cannot be unloaded- 247

2.2.92 Source 96: CSM load data nack with the cause - flash flag cannotaccess - 249

2.2.93 Source 97: CSM load data nack with the cause - boot cannot beunloaded - 251

2.2.94 Source 98: CSM load data nack with the cause - data decode error- 254

2.2.95 Source 99: CSM load data nack with the cause - table cannot access- 256

2.2.96 Source 100: CSM load data nack with the cause - RAM mapping error- 258


411-9001-103 18.06 20 January 2010



7/766

7

2.2.97 Source 101: CSM load data nack with the cause - flash access error- 260

2.2.98 Source 102: CSM load data nack with the cause - flash RAM error- 263

2.2.99 Source 103: CSM load data nack with the cause - flash erase error

- 2652.2.100 Source 104: CSM load data nack with the cause - internal abort - 267

2.2.101 Source 105: CSM flash activate response with a bad cause 269

2.2.102 Source 106: DTM error during token allocation 272

2.2.103 Source 107: CSM software update report with the cause: TRX softwareincompatibility 274

2.2.104 Source 108: Too many different deliveries in the cell group 276

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



2.5.1 Source 1: Equipment failure 284

2.5.2 Source 2: Equipment unable to perform such test 285

2.5.3 Source 3: Equipment unable to perform such configuration 286

2.5.4 Source 4: Unknown test 288

2.5.5 Source 5: Cell parameters inconsistency 288

2.5.6 Source 6: Data inconsistency 290

2.5.7 Source 7: Value out of range 291

2.5.8 Source 8: TEI not present 292

2.5.9 Source 9: Unknown Abis PCM_Time_Slot 293

2.5.10 Source 10: Unknown Abis PCM 293

2.5.11 Source 11: Wrong software reference 294

2.5.12 Source 12: Further files required 2942.5.13 Source 13: Failure during activation 295

2.5.14 Source 14: Data format error 295

2.5.15 Source 15: Window overflow 295

2.5.16 Source 16: Normal completion 295

2.5.17 Source 17: Transfer aborted 295

2.5.18 Source 18: Checksum error 296

2.5.19 Source 19: File incomplete 296

2.5.20 Source 20: File already present and correct 296

2.5.21 Source 21: File cannot be downloaded 296

2.5.22 Source 22: Entity engaged in other download 296

2.5.23 Source 23: Too many signaling timeslots 2972.5.24 Source 24: Too many TEI connections to physical channel 298

2.5.25 Source 25: Out of sequence message 298

2.5.26 Source 26: Incorrect IEI 300

2.5.27 Source 27: Wrong file reference 300

2.5.28 Source 28: Bad cell number 301

2.5.29 Source 29: Bad related TEI 301


411-9001-103 18.06 20 January 2010



8/766

8

2.5.30 Source 30: Bad timeslot 301

2.5.31 Source 31: Window size not allowed 301

2.5.32 Source 32: Flash boot required 301

2.5.33 Source 33: Wrong config reference 302

2.5.34 Source 34: The BTS has not acknowledged the TX power consignrequest 302

2.5.35 Source 35: Downloading aborted 307

2.5.36 Source 36: Files missing 307

2.5.37 Source 37: Buffer overflow 308

2.5.38 Source 38: Block not received 308

2.5.39 Source 39: Downloading restart 308

2.5.40 Source 40: Request not supported 308

2.5.41 Source 41: Downloading failure 308

2.5.42 Source 42: Start-up failure 309

2.5.43 Source 43: Maximum number of joker TS 309

2.5.44 Source 44: Bad chain type 3122.5.45 Source 45: Bad radio timeslot reference 312

2.5.46 Source 46: Bad internal Link EDGE configuration 312

2.5.47 Source 47: Inconsistency mapping 312

2.5.48 Source 48: Inconsistency number of joker DS0 313

2.5.49 Source 49: Invalid mode 313

2.5.50 Source 50: File already open 313

2.5.51 Source 51: File cannot be unloaded 313

2.5.52 Source 52: Boot cannot be unloaded 313

2.5.53 Source 53: Data decode error 314

2.5.54 Source 54: Flash flag cannot access 314

2.5.55 Source 55: Table cannot access 3142.5.56 Source 56: RAM mapping error 314

2.5.57 Source 57: Flash access error 314

2.5.58 Source 58: Flash write error 315

2.5.59 Source 59: Flash erase error 315

2.5.60 Source 60: Internal abort 315

2.5.61 Source 61: Equipment not able to get external synchronization 315

2.5.62 Source 62: Synchronization in progress 315

2.5.63 Source 63: Dynamic Abis feature not supported 316

2.5.64 Source 64: Inconsistent number of joker DS0 317

2.5.65 Source 65: Exceeded DL joker DS0 pool number 319

2.5.66 Source 255: Non-significant value 321


2.6.1 Source 0: Incorrect priority on transceiver 324

2.6.2 Source 1: Incorrect setting of channel on transceiver 324

2.6.3 Source 2: Cell without BCCH TDM 324

2.6.4 Source 3: Radio Time Slot not used 325

2.6.5 Source 4: Wrong value for BSS TEI in T1 mode 325


411-9001-103 18.06 20 January 2010



9/766

9

2.6.6 Source 5: Cell cfg with cavity and dual band not acceptable 325

2.6.7 Source 6: Missing Site management Abis GSM function 325

2.6.8 Source 7: Missing Abis Signalling management Abis GSM function 325

2.6.9 Source 8: Missing Abis traffic management Abis GSM function 326

2.6.10 Source 9: Missing RfTrans management Abis GSM function 326

2.6.11 Source 10: Missing cell management Abis GSM function 326

2.6.12 Source 11: Missing TDMA management Abis GSM function 326

2.6.13 Source 12: Missing TS management Abis GSM function 327

2.6.14 Source 13: The TDMA exists in RDC but the object was not created.327

2.6.15 Source 14: Too many EDGE TDMAs (more than 16 per site) configured327




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

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

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

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

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

2.9.6 Cavity (source: Nack answer from cavity) 354

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

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

2.9.9 CMCF board (source: Unknown message) 355

2.9.10 CMCF board (source: Restart requested by the active board) 356

2.9.11 CMCF (source: Board reset asked by OMC) 356

2.9.12 CMCF board (source: Restart due to hardware watchdog) 3572.9.13 CMCF boards (source: Restart due to double bus fault) 357

2.9.14 CMCF boards (source: Reset for new Lapd parameters CMCF) 357

2.9.15 CMCF boards (source: ABIS PCM statistics) 358

2.9.16 CSWM board (source: Restart due to hardware watchdog) 358

2.9.17 CSWM board (source: Restart due to double bus fault) 359

2.9.18 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Frequencycollision on FH bus) 359

2.9.19 DRX or eDRX or DRX-ND3 or eDRX2 (source: Restart requested bythe BCF) 360

2.9.20 DRX or eDRX or DRX ND3 or eDRX2 modules (source: FACCH

congestion) 3602.9.21 DRX or eDRX or DRX ND3 or eDRX2 modules (source: Reset due to

hardware watchdog) 361

2.9.22 DRX or eDRX or DRX ND3 or eDRX2 modules (source: Restart due todouble bus fault) 362

2.9.23 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: BCCH configdump) 362

2.9.24 DRX or eDRX or DRX-ND3 modules or eDRX2 (source: SACCH config


411-9001-103 18.06 20 January 2010

http://-/?-http://-/?-http://-/?-http://-/?-


10/766


11/766

11

2.9.54 RIPM-USER core (source: Reset requested by IBOS with no BISTexecution and Ethernet switch reset) 378

2.9.55 RIPM-USER core (source: Reset requested by IBOS with BISTexecution and no Ethernet switch reset) 378

2.9.56 RIPM-USER core (source: Reset requested by IBOS with no BIST

execution nor Ethernet switch reset) 3792.9.57 RIPM-USER core (source: Restart after TML commissioning) 379

2.9.58 RIPM-USER core (source: Connection with IGM has been lost (nostatus received for 7 keep-alive periods)) 380

2.9.59 RIPM-USER core (source: No response to DHCP requests for 15minutes) 380

2.9.60 RIPM-USER core (source: No response to DNS requests for 15

minutes) 381

2.9.61 RIPM-USER core (source: Debug) 381

2.9.62 RIPM-USER core (source: Soft) 382

2.9.63 RIPM-USER core (source: Reset requested by active with BIST

execution) 3832.9.64 RIPM-USER core (source: Reset requested by active with no BIST

execution) 383

2.9.65 Tx Filters (source: VSWR level 2) 384


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


2.12.1 ACU climatic unit (source: Cooler fault) 413

2.12.2 ALCO board (source: Major fault) 416

2.12.3 Battery cabinet (source: Over temperature) 419

2.12.4 Battery cabinet (source: DC power fault) 422

2.12.5 Battery cabinet (source: Doors) 4252.12.6 BCF cabinet door contact(source: BCF cabinet door contact

detection) 429

2.12.7 BCF cabinet fan (source: BCF cabinet fan fault) 433

2.12.8 BCF power supply (source: Volt) 435

2.12.9 BRC (source: Manual switch on battery power) 438

2.12.10 BRC (source: Automatic switch on battery power) 438

2.12.11 BRC (source: Manual switch on main power) 438

2.12.12 BRC (source: Automatic switch on main power) 438

2.12.13 BRC (source: Battery failure) 439

2.12.14 BRC (source: Monitored battery not present) 440

2.12.15 BRC (source: Internal inconsistency) 441

2.12.16 BTS SYNCHRONIZATION (source: SYNO clock not locked on thenetwork) 441

2.12.17 BTS synchronization (source: Synchro not locked because OCVXOis KO) 448

2.12.18 BTS synchronization (source: GPS synchronization unavailable) 451

2.12.19 BTS synchronization (source: Loss of GPS synchronization) 456


411-9001-103 18.06 20 January 2010



12/766

12

2.12.20 BTS SYNCHRONIZATION (source: Lack of GPS synchronizationaccuracy) 461

2.12.21 BTS SYNCHRONIZATION (source: Master synchronizationunavailable) 466

2.12.22 BTS SYNCHRONIZATION (source: Loss of master GSM time) 471

2.12.23 BTS SYNCHRONIZATION (source: Loss of master SY) 475

2.12.24 Cabinet door (source: Door contact detection) 479

2.12.25 Cavity (source: Cavity out of service) 483

2.12.26 Cavity (source: Cavity parked after tuning fault (min not found)) 485

2.12.27 Cavity (source: Loss of cavity initialization) 487

2.12.28 Cavity (source: Nack answer from cavity) 489

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

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

2.12.31 Cavity (source: Internal software problem) 494

2.12.32 Cavity combiner (source: Power supply) 496

2.12.33 Cavity combiner (source: Tuning detector fault) 498

2.12.34 Cavity combiner (source: Link NOK) 500

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

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

2.12.37 CMCF board (source: MCF_MCF) 507

2.12.38 CMCF board (source: Slave downloading error) 510

2.12.39 CMCF board (source: CMCF_ACT_DUPLEX_INHIBITED) 512

2.12.40 CMCF board (source: CMCF_ACT_ICST) 515

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

2.12.42 Combiner duplexer LNA or combiner H2 LNA (source: LNA fault) 5202.12.43 Combiner duplexer VSWR or combiner H2 VSWR (source: VSWR level

1) 524

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

2.12.45 Combiner duplexer VSWR or combiner H2 VSWR (source: VSWR level3) 525

2.12.46 Combiner H4D LNA (source: LNA fault) 528

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



2.12.50 Compact distribution system (source: Main breaker) 538

2.12.51 CPCMI board (source: Major) 541

2.12.52 CPCMI board (source: Slave downloading error) 541

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

2.12.54 CSWM board (source: Slave downloading error) 547

2.12.55 DACS climatic system (source: Dirty filter) 549

2.12.56 DACS climatic system (source: DACS failed) 551


411-9001-103 18.06 20 January 2010



13/766

13

2.12.57 Distribution system (source: Main breaker) 557

2.12.58 DRX or DRX-ND3 diversity reception chain (source: Softwaredetection) 560

2.12.59 DRX or DRX-ND3 main reception chain (source: Softwaredetection) 565

2.12.60 DRX or DRX-ND3 modules (source: Abis satellite not supported DRX(ND3)) 569

2.12.61 DRX or DRX-ND3 modules (source: HePA not supported) 570

2.12.62 DRX or DRX-ND3 modules (source: PA configuration exceeded) 573

2.12.63 DRX or eDRX or DRX-ND3 modules (source: BBFILTER ASICfault) 576

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

2.12.65 DRX or eDRX or DRX-ND3 modules (source: RX fault) 585

2.12.66 DRX or eDRX or DRX-ND3 modules (source: L1M first configfailed) 589

2.12.67 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: BCCH firstconfig failed) 589

2.12.68 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: BCCH secondconfig failed) 590

2.12.69 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: DRXlink) 591

2.12.70 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: DRX reset byBSC) 596

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

config failed) 597

2.12.72 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Major faulton TX) 597

2.12.73 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Nackanswer) 602

2.12.74 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: PA DRXcontrol loop fault) 602

2.12.75 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Post-mortemdump zone 3) 607

2.12.76 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: SACCH firstconfig failed) 607

2.12.77 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: SACCHsecond config failed) 608

2.12.78 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Self test

failed) 6092.12.79 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: TRX not

anymore configured) 613

2.12.80 DSC boards (source: Major fault) 616

2.12.81 DSC boards (source: Channel_HSCX) 618

2.12.82 External alarm (source: Alarm) 621

2.12.83 Fan of the base cabinet (source: Cabinet fan fault) 621


411-9001-103 18.06 20 January 2010



14/766

14

2.12.84 F-type converters (source: Volt) 624

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

2.12.86 Internal batteries (source: Battery disconnected) 631

2.12.87 IP synchro (source: Unable to lock on IP synchronization) 634

2.12.88 IP synchro (source: Not enough synchronization packets have beenreceived) 636

2.12.89 IPM-USER commissioning (source: Only one IBOS commissioned atIPM) 637

2.12.90 IPM-USER commissioning (source: DNS resolution has failed for atleast one IBOS) 638

2.12.91 IPM-USER core (source: IPM BIST failed) 639

2.12.92 IPM-USER core (source: IPM temperature) 640

2.12.93 IPM-USER core (source: DAC unable to lock, synchronization notpossible) 641

2.12.94 Lightning protector (source: Lightning protection fault) 643

2.12.95 Not protected alarm (source: Alarm) 646

2.12.96 Output Rx-splitter D (source: Over current) 646

2.12.97 Output Rx-splitter M (source: Over current) 649

2.12.98 PCM (source: PCM) 652

2.12.99 PCMI boards (source: Major fault on PCMI) 652

2.12.100 Power amplifiers (source: Hardware) 652

2.12.101 Power amplifiers (source: DRX and PA connection) 658

2.12.102 Power amplifiers (source: High temperature ) 663

2.12.103 Power amplifiers (source: High Current ) 667

2.12.104 Power amplifiers (source: PA_PSDW ) 671

2.12.105 Power amplifiers (source: VSWR fault detected by PA) 675

2.12.106 RECAL board (source: Major) 6762.12.107 RECAL board (source: Slave downloading error) 679

2.12.108 Rectifiers (source: AC fault) 682

2.12.109 Rectifiers (source: DC fault) 686

2.12.110 Rectifiers (source: Over temperature) 688

2.12.111 Rectifiers (source: External battery level 1) 691

2.12.112 Rectifiers (source: PCU protective) 693

2.12.113 Rectifiers (source: Battery on discharges) 697

2.12.114 RIPM-USER core (source: IPM BIST failed) 699

2.12.115 RIPM-USER core (source: IPM temperature) 700

2.12.116 RIPM-USER core (source: DAC unable to lock, synchronization not

possible) 7012.12.117 RIPM-USER core (source: No link with passive) 703

2.12.118 Rx Filter (source: LNA fault) 704

2.12.119 SYNC boards (source: Major fault on SYNC) 707





411-9001-103 18.06 20 January 2010



15/766

15


2.14.1 Source 9: No response to load message 718

2.14.2 Source 10: Received LOAD INIT NACK 718

2.14.3 Source 11: Received LOAD DATA NACK 718

2.14.4 Source 12: Received LOAD END NACK 718

2.14.5 Source 13: Received LOAD READY NACK 718










2.24 Fault number: 1268 (S8000, S8002, S8003, and S8006 BTS) 7272.25 Fault number: 1500 (S8000, S8002, S8003, and S8006 BTS) 728


2.27 Fault number: 1506 (S8000, S8002, S8003, S8006 BTS) 730



2.30 Applicability of the fault numbers to the BTS type 734


411-9001-103 18.06 20 January 2010



16/766

16


411-9001-103 18.06 20 January 2010



17/766


18/766

18 New in this release


411-9001-103 18.06 20 January 2010



19/766

19.

Introduction

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

PrerequisitesIt is recommended that the readers also become familiar with the following

technical documents:

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

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 18.06 20 January 2010



20/766

20 Introduction

NavigationThis document consists of 2 chapters:

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

Chapter 2 S8000, S8002, S8003, and S8006 BTS fault numbers(page 29), "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 18.06 20 January 2010



21/766

Safety regulations 21

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 18.06 20 January 2010



22/766

22 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 18.06 20 January 2010



23/766


24/766

24 Introduction


411-9001-103 18.06 20 January 2010



25/766

25.

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 18.06 20 January 2010



26/766

26 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 analysis


411-9001-103 18.06 20 January 2010



27/766

1.4 Help 27

This paragraph describes the fault.

Reaction of the system

BSC defense

This paragraph describes the defense actions taken by the BSC.

Impact on the service

This paragraph gives the consequences of the alarm for theservice.

Troubleshooting

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

Preliminary checks

These 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 checks

This paragraph shows how to check that the fault has beencleared.

1.4 Help The 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 18.06 20 January 2010



28/766

28 Chapter 1 How to use this manual


411-9001-103 18.06 20 January 2010



29/766

29.

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 18.06 20 January 2010



30/766

30 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 30) 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 2.2.1 Source 0: Noresponse to statusrequest (page 41)

1 Bad hardware reference of manufacturer ID 2.2.2 Source 1: Badhardware referenceof manufacturer ID

(page 43)

2 SUP stop receipt 2.2.3 Source 2: SUP stopreceipt (page 46)

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

48)

4 This entity is engaged in another downloading 2.2.5 Source

4: This entity isengaged in another

downloadingSource 8:Wrong software reference

on a non downloadableTEI (page 52)

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

hardware (page 54)

6 File access error 2.2.7 Source 6: Fileaccess error (page 58)

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

2.2.8 Source 7:Repetitive errors (NACK,

timeout, ...) whiledownloading a file

(page 61)


411-9001-103 18.06 20 January 2010



31/766


Table 1Fault number 1052 sources (contd.)


8 Wrong software reference on a non downloadable TEI 2.2.5 Source

4: This entity isengaged in another

downloadingSource 8:Wrong software reference

on a non downloadableTEI (page 52)

9 No response to download message 2.2.9 Source 9: Noresponse to download

message (page 61)

14 CSM load container negative acknowledgement 2.2.10 Source 14:Received CSM LOAD

CONTAINER NAK(page 64)

15 File to download empty 2.2.11 Source 15: Fileto download empty

(page 66)

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

(page 68)

17 Buffer allocation failure 2.2.13 Source 17: Bufferallocation failure (page

69)

18 Bad sending buffer size value 2.2.14 Source 18: Badsending buffer size value(page 72)

19 Failure during OMU switchover 2.2.15 Source 19: Failureduring OMU switchover

(page 74)

20 Bad TEI sent by BTS in the CSM software updatereport message

2.2.16 Source 20: BadTEI sent by BTS in theCSM software update

report message (page 76)

21 CSM software update report with the cause "unknown

TEI"

2.2.17 Source 21: CSM

software update reportwith the cause - unknownTEI - (page 78)

22 CSM software update report with the cause "equipmentfailure"

2.2.18 Source 22:CSM software updatereport with the cause

- equipment failure -(page 81)


411-9001-103 18.06 20 January 2010



32/766




23 CSM software update report with the cause

"downloading failure"

2.2.19 Source 23:

CSM software updatereport with the cause -downloading failure -

(page 83)

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

2.2.20 Source 24: CSMsoftware update report

with the cause - not ableto perform- (page 85)

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

2.2.21 Source 25: CSMsoftware update reportwith the cause - wrong

software reference -(page 87)

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

2.2.22 Source 26: CSMsoftware update reportwith the cause - wrong

configuration reference- (page 90)

27 CSM software update report with the cause "restartrequest"

2.2.23 Source 27: CSMsoftware update reportwith the cause - restart

request - (page 92)

28 CSM software update report with the cause "data

inconsistency"


software update reportwith the cause - data

inconsistency - (page 94)

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

2.2.25 Source 29:CSM software updatereport with the cause -

message out of sequence- (page 97)

30 CSM software update report with the cause"background not available"


background not available- (page 99)

31 CSM software update report with the cause"incompatible RM version"


incompatible RM version

- (page 101)


411-9001-103 18.06 20 January 2010



33/766




32 CSM software update report with the cause

"downloading in progress"

2.2.28 Source 32:

CSM software updatereport with the cause -

downloading in progress- (page 104)

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

2.2.29 Source 33: Badreport sent by BTS

in the CSM softwareupdate report message

(page 106)

34 no BTS response on CSM software update init/controlmessage

2.2.30 Source 34:No BTS response onCSM software updateinit-control message

(page 108)

35 nack received on the abort requested by operator 2.2.31 Source 35: Nackreceived on the abort

requested by operator(page 111)

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

2.2.32 Source 36: Badreport sent by BTS

in the CSM softwareupdate abort message

(page 113)

37 no BTS response on CSM software update abortmessage

2.2.33 Source 37: NoBTS response on CSMsoftware update abortmessage (page 115)

38 flash activate nack with the cause "unknown TEI" 2.2.34 Source 38: Flashactivate nack with thecause - unknown TEI

- (page 118)

39 flash activate nack with the cause "equipment failure" 2.2.35 Source 39: Flashactivate nack with the

cause - equipment failure

- (page 120)40 flash activate nack with the cause "downloading failure" 2.2.36 Source 40: Flash

activate nack with thecause - downloadingfailure - (page 122)


411-9001-103 18.06 20 January 2010



34/766




41 flash activate nack with the cause "not able to perform" 2.2.37 Source 41: Flash

activate nack with thecause - not able to

perform - (page 124)

42 flash activate nack with the cause "flash inconsistency" 2.2.38 Source 42:Flash activate nack

with the cause - flashinconsistency - (page

127)

43 flash activate nack with the cause "data inconsistency" 2.2.39 Source 43: Flashactivate nack with the

cause - data inconsistency- (page 129)

44 flash activate nack with the cause "wrong soft ref" 2.2.40 Source 44: Flashactivate nack with thecause - wrong soft ref

- (page 131)

45 flash activate nack with the cause "wrong config ref" 2.2.41 Source 45: Flashactivate nack with the

cause - wrong config ref- (page 133)

46 CSM downloading start nack with the cause "unknownTEI"

2.2.42 Source 46: CSMdownloading start nack

with the cause - unknown

TEI - (page 136)

47 CSM downloading start nack with the cause "equipmentfailure"

2.2.43 Source 47:CSM downloading start

nack with the cause- equipment failure -

(page 138)

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


nack with the cause -downloading failure -

(page 140)

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


nack with the cause -message out of sequence

- (page 142)


411-9001-103 18.06 20 January 2010



35/766




50 CSM downloading start nack with the cause "wrong soft

ref"


downloading start nackwith the cause - wrong

soft ref - (page 145)

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

2.2.47 Source 51: CSMdownloading start nackwith the cause - wrongconfig ref - (page 147)

52 CSM downloading start nack with a bad cause 2.2.48 Source 52:CSM downloading startnack with a bad cause

(page 149)

53 no BTS response on CSM downloading start message 2.2.49 Source 53:No BTS response on

CSM downloading startmessage (page 152)

54 CSM downloading end nack with the cause "unknownTEI"

2.2.50 Source 54: CSMdownloading end nack

with the cause - unknownTEI - (page 154)

55 CSM downloading end nack with the cause "equipmentfailure"

2.2.51 Source 55:CSM downloading end

nack with the cause- equipment failure -

(page 156)

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

2.2.52 Source 56:CSM downloading endnack with the cause -downloading failure -

(page 158)

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

2.2.53 Source 57: CSMdownloading end nack

with the cause - value outof range - (page 161)

58 CSM downloading end nack with a bad cause 2.2.54 Source 58:

CSM downloading endnack with a bad cause

(page 163)

59 no BTS response on CSM downloading end message 2.2.55 Source 59:No BTS response on

CSM downloading end

message (page 165)


411-9001-103 18.06 20 January 2010



36/766


37/766




70 CSM load data nack with the cause "message out of

sequence"


load data nack with thecause - message out ofsequence - (page 190)

71 CSM load data nack with the cause "data format error" 2.2.67 Source 71: CSMload data nack with the

cause - data format error- (page 192)

72 CSM load data nack with the cause "window overflow" 2.2.68 Source 72: CSMload data nack with the

cause - window overflow- (page 195)

73 CSM load data nack with the cause "datainconsistency"

2.2.69 Source 73: CSMload data nack with the


74 CSM load data nack with the cause "block notreceived"


cause - block not received- (page 199)

75 CSM load data nack with the cause "bad block tag" 2.2.71 Source 75: CSMload data nack with thecause - bad block tag

- (page 201)

76 CSM load data nack with the cause "checksum error" 2.2.72 Source 76: CSMload data nack with thecause - checksum error

- (page 204)

77 CSM load data nack with a bad cause 2.2.73 Source 77: CSMload data nack with a bad

cause (page 206)

78 unexpected CSM load data ack 2.2.74 Source 78:Unexpected CSM loaddata ack (page 208)

79 no BTS response on CSM load data message 2.2.75 Source 79: NoBTS response on CSMload data message

(page 210)

80 CSM load end nack with the cause "equipment failure" 2.2.76 Source 80: CSMload end nack with the

cause - equipment failure- (page 213)


411-9001-103 18.06 20 January 2010



38/766




81 CSM load end nack with the cause "downloading

failure"


load end nack with thecause - downloadingfailure - (page 215)

82 CSM load end nack with the cause "value out of range" 2.2.78 Source 82: CSMload end nack with the

cause - value out of range- (page 217)

83 CSM load end nack with the cause "message out ofsequence"

2.2.79 Source 83: CSMload end nack with the

cause - message out ofsequence - (page 219)

84 CSM load end nack with the cause "data format error" 2.2.80 Source 84: CSMload end nack with the

cause - data format error- (page 222)

85 CSM load end nack with the cause "wrong file ref" 2.2.81 Source 85: CSMload end nack with thecause - wrong file ref -

(page 224)

86 CSM load end nack with the cause "data inconsistency" 2.2.82 Source 86: CSMload end nack with the


87 CSM load end nack with the cause "checksum error" 2.2.83 Source 87: CSMload end nack with the

cause - checksum error- (page 229)

88 CSM load end nack with a bad cause 2.2.84 Source 88: CSMload end nack with a bad

cause (page 231)

89 no BTS response on CSM load end message 2.2.85 Source 89: NoBTS response on CSM

load end message(page 233)

90 bad report sent by BTS during an internal update 2.2.86 Source 90: Badreport sent by BTS

during an internal update(page 235)


411-9001-103 18.06 20 January 2010



39/766




91 CSM load init nack with the cause "file already open" 2.2.87 Source 91: CSM

load init nack with thecause - file already open

- (page 238)

92 CSM load init nack with the cause "invalid mode" 2.2.88 Source 92: CSMload init nack with the

cause - invalid mode -(page 240)

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

2.2.89 Source 93: CSMload init nack with thecause - file cannot be

unloaded - (page 242)

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

2.2.90 Source 94: CSMload init nack with the

cause - flash flag cannotaccess - (page 244)

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

2.2.91 Source 95: CSMload data nack with thecause - file cannot be

unloaded - (page 247)

96 CSM load data nack with the cause "flash flag cannotaccess"


cause - flash flag cannotaccess - (page 249)

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

2.2.93 Source 97: CSMload data nack with thecause - boot cannot beunloaded - (page 251)

98 CSM load data nack with the cause "data decode error" 2.2.94 Source 98: CSMload data nack with the

cause - data decode error- (page 254)

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


cause - table cannot

access - (page 256)

100 CSM load data nack with the cause "ram mappingerror"

2.2.96 Source 100: CSMload data nack with thecause - RAM mapping

error - (page 258)


411-9001-103 18.06 20 January 2010



40/766


41/766


42/766


43/766


GSM 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 transceiverEquipment object is"disabled-failed", the TRX is not operational.

If the fault number 1052 is the only alarm, process thealarm. Go to step 4.

Otherwise, if there are other alarms, set thetransceiverEquipment object to "locked" and thento "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, process them (concerning fault number

1054 (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 processthe alarm and do not clear it. Wait for a state change of thetransceiverEquipment object.

4 The procedure is complete.

--End--

2.2.2 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.


411-9001-103 18.06 20 January 2010



44/766


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.

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 afault number concerning PCMs. SeeNortel GSM BSSFault Clearing - Advanced Maintenance Procedures(411-9001-105).

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, process thealarm.

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


If other fault numbers are present, such as faultnumber 1054, process them (concerning fault number1054 (loss of layer 2). See Nortel GSM BSS Fault

Clearing - Advanced Maintenance Procedures(411-9001-105).

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


411-9001-103 18.06 20 January 2010



45/766


46/766


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


--End--

2.2.3 Source 2: SUP stop receipt


Source: (2) SUP stop receipt

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

FAULT ANALYSISThis source indicates that a supervision stop has been received.

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 operationalState of the btsSiteManager object is"enabled", the site is operational.

Clear the alarm.



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 a 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", the site is not operational.


411-9001-103 18.06 20 January 2010



47/766


If the fault number 1052 is the only alarm, process thealarm.

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


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


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 the operationalState of the transceiverEquipment object is"disabled-dependency", the TRX is not operational.Look for a parent object which is not operational.

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

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

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.



411-9001-103 18.06 20 January 2010



48/766





If other fault numbers are present, such as faultnumber 1054, process 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 processthe alarm and do not clear it. Wait for a state change of thetransceiverEquipment object.


--End--

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


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

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

2.2.4.1 FAULT ANALYSISThis source indicates that no change occurred to one of the Boot states,after reset.

TROUBLESHOOTING

Step Action

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





411-9001-103 18.06 20 January 2010



49/766


50/766


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 transceiverEquipment objectis "disabled" the TRX is not operational. Do not processthe alarm 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. If the source 1 appears, treat it. See Paragraph2.2.2

Source 1: Bad hardware reference of manufacturer ID(page 43).

If the source 1 does not appear, go to step 5 if thebtsSiteManager object is concerned, or step 6 if thetransceiverEquipment 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.


411-9001-103 18.06 20 January 2010



51/766


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) 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/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 S8002Troubleshooting)

for the S8003 BTS:

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/S8003Troubleshooting).

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--


411-9001-103 18.06 20 January 2010



52/766


2.2.5 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


2.2.5.1 FAULT ANALYSISThis source indicates that this entity is engaged in another downloading.

TROUBLESHOOTING

Step Action

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



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"enabled", the site is operational. Clear the alarm and go tostep 4.




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 4or 8 is still present, process the alarm. Go to step 4.

Otherwise, if there are other alarms, such as fault number1054, process them (concerning fault number 1054 (loss


411-9001-103 18.06 20 January 2010



53/766


of layer 2), see 411-9001-105 (Nortel GSM BSS FaultClearing - Advanced Maintenance Procedures)

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

btsSiteManager 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.


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

Look for a parent object which is not operational. If a bts object is "disabled-dependency", look for alarms

concerning cells.








If other fault numbers are present, such as faultnumber 1054, process 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 process


411-9001-103 18.06 20 January 2010



54/766


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

On-site maintenance using the OMC-R4 Restart the active board of the BCF.

If the alarm has disappeared, go to step 5. If the alarm persists:

For the BSC 3000, call the manufacturer.


--End--

2.2.6 Source 5: Software not compatible with hardware

Fault number 1052 : GSM entity downloading failureSource: (5) Software not compatible with hardware


2.2.6.1 FAULT ANALYSISThis source indicates that the software is not compatible with thehardware.

TROUBLESHOOTING

Step Action

Preliminary checks

1 Look at the notification and identify the object concerned.


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, go

to step 3.



411-9001-103 18.06 20 January 2010



55/766


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

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 a pcmCircuit object is "disabled-failed", look for a faultnumber concerning PCMs (see 411-9001-105 (NortelGSM 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 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, process 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 the operationalState of the transceiverEquipment object is"disabled-dependency", the TRX is not operational.Look for a parent object which is not operational.

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


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


411-9001-103 18.06 20 January 2010



56/766


GSM BSS Fault Clearing - Advanced MaintenanceProcedures) ).








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

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 18.06 20 January 2010



57/766


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".

GSM BTS S8000 S8002 S8003 S8006 Fault Clearing

Documents

Transcript of GSM BTS S8000 S8002 S8003 S8006 Fault Clearing