GSM BTS S2000H_S2000L_e-Cell Fault Clearing (411-9001-104_18.05)

8/18/2019 GSM BTS S2000H_S2000L_e-Cell Fault Clearing (411-9001-104_18.05)

1/844


2/844

Global System for Mobile Communications (GSM)

Release: V18.0 PC2

Publication: 411-9001-104

Document release date: 2 February 2010

Copyright © 1999-2009 Nortel Networks. All Rights Reserved.

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 aresubject to change without notice.

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

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, S8000 and S2000 are trademarks of Nortel Networks.

All other trademarks are the property of their respective owners.

_ 17+ 18+

All other trademarks are the property of their respective owners.

.


3/844

3.

Contents

New in this release 19Features 19

Introduction 21

Chapter 1 How to use this manual 23

1.1 Introduction 231.2 The types of spontaneous messages 23

1.2.1 Events detected by the BTS 23

1.2.2 Events detected by the BSC 24

1.3 Description of a fault number sheet 24

1.3.1 Header of the sheet 24

1.3.2 Main body of the sheet 24

Chapter 2 S2000 H/L BTS fault numbers 272.1 Fault number: 1051 (S2000 H/L BTS) 27

2.2 Fault number: 1052 (S2000 H/L BTS) 27

2.2.1 Source 0: No response to status request 362.2.2 Source 1: Bad hardware reference or manufacturer ID 38

2.2.3 Source 2: SUP stop receipt 40

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

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

2.2.6 Source 5: Software not compatible with hardware 47

2.2.7 Source 6: File access error 51

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

2.2.9 Source 9: No response to download message 55

2.2.10 Source 14: Received CSM LOAD CONTAINER NAK 572.2.11 Source 15: File to download empty 59

2.2.12 Source 16: File to download unavailable 62

2.2.13 Source 17: Buffer allocation failure 62

2.2.14 Source 18: Bad sending buffer size value 65

2.2.15 Source 19: Failure during OMU switchover 67

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

Global System for Mobile Communications (GSM)Nortel GSM BTS S2000H/S2000L/e-cell Fault Clearing

411-9001-104 18.05 2 February 2010



4/844

4

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

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

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

failure - 762.2.20 Source 24: CSM software update report with the cause - not able to

perform- 79

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

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

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

- 86

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

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

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

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

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

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

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

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

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

2.2.33 Source 37: No BTS response on CSM software update abort

message 109

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

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

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

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

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

- 120

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

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

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

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


411-9001-104 18.05 2 February 2010



5/844

5

- 129

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

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

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

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

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

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

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

2.2.50 Source 54: CSM downloading end nack with the cause - unknown TEI- 147

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

failure - 1502.2.52 Source 56: CSM downloading end nack with the cause - downloading

failure - 152

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

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

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

2.2.56 Source 60: CSM load init nack with the cause - equipment failure - 161

2.2.57 Source 61: CSM load init nack with the cause - downloading failure- 163

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

sequence - 1652.2.59 Source 63: CSM load init nack with the cause - wrong file ref - 168

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

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

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

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

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

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

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

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

- 186

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

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


411-9001-104 18.05 2 February 2010



6/844

6

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

2.2.71 Source 75: CSM load data nack with the cause - bad block tag - 195

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

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

2.2.74 Source 78: Unexpected CSM load data ack 202

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

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

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

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

2.2.79 Source 83: CSM load end nack with the cause - message out ofsequence - 213

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

- 2152.2.81 Source 85: CSM load end nack with the cause - wrong file ref - 217

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

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

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

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

2.2.86 Source 90: Bad report sent by BTS during an internal update 229

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

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

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

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

- 238

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

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

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

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

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

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

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

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


411-9001-104 18.05 2 February 2010



7/844

7

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

2.2.100 Source 104: CSM load data nack with the cause - internal abort - 260

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

2.2.102 Source 106: DTM error during token allocation 265

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

incompatibility 267

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




2.5.1 Source 1: Equipment failure 278

2.5.2 Source 2: Equipment unable to perform such test 278

2.5.3 Source 3: Invalid configuration 279

2.5.4 Source 4: Unknown test 281

2.5.5 Source 5: Cell parameters inconsistency 281

2.5.6 Source 6: Data inconsistency 282

2.5.7 Source 7: Value out of range 284

2.5.8 Source 8: TEI not present 285

2.5.9 Source 9: Unknown Abis PCM_Time_Slot 286

2.5.10 Source 10: Unknown Abis PCM 286

2.5.11 Source 11: Wrong software reference 287

2.5.12 Source 12: Further files required 287

2.5.13 Source 13: Failure during activation 287

2.5.14 Source 14: Data format error 288

2.5.15 Source 15: Window overflow 288

2.5.16 Source 16: Normal completion 2882.5.17 Source 17: Transfer aborted 288

2.5.18 Source 18: Checksum error 288

2.5.19 Source 19: File incomplete 289

2.5.20 Source 20: File already present and correct 289

2.5.21 Source 21: File cannot be downloaded 289

2.5.22 Source 22: Entity engaged in other download 289

2.5.23 Source 23: Too many signaling timeslots 289

2.5.24 Source 24: Too many TEI connections to physical channel 291

2.5.25 Source 25: Out of sequence message 291

2.5.26 Source 26: Incorrect IEI 293

2.5.27 Source 27: Wrong file reference 293

2.5.28 Source 28: Bad cell number 294

2.5.29 Source 29: Bad related TEI 294

2.5.30 Source 30: Bad timeslot 294

2.5.31 Source 31: Window size not allowed 294

2.5.32 Source 32: Flash boot required 294

2.5.33 Source 33: Wrong config reference 295


411-9001-104 18.05 2 February 2010



8/844

8

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

2.5.35 Source 35: Downloading aborted 300

2.5.36 Source 36: Files missing 300

2.5.37 Source 37: Buffer overflow 300

2.5.38 Source 38: Block not received 301

2.5.39 Source 39: Downloading restart 301

2.5.40 Source 40: Request not supported 301

2.5.41 Source 41: Downloading failure 301

2.5.42 Source 42: Start-up failure 301

2.5.43 Source 43: Maximum number of joker TS 302

2.5.44 Source 44: Bad chain type 305

2.5.45 Source 45: Bad radio timeslot reference 305

2.5.46 Source 46: Bad internal Link EDGE configuration 305

2.5.47 Source 47: Inconsistency mapping 305

2.5.48 Source 48: Inconsistency number of joker DS0 3052.5.49 Source 49: Invalid mode 306

2.5.50 Source 50: File already open 306

2.5.51 Source 51: File cannot be unloaded 306

2.5.52 Source 52: Boot cannot be unloaded 306

2.5.53 Source 53: Data decode error 306

2.5.54 Source 54: Flash flag cannot access 307

2.5.55 Source 55: Table cannot access 307

2.5.56 Source 56: RAM mapping error 307

2.5.57 Source 57: Flash access error 307

2.5.58 Source 58: Flash write error 307

2.5.59 Source 59: Flash erase error 3082.5.60 Source 60: Internal abort 308

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

2.5.62 Source 62: Synchronization in progress 308

2.5.63 Source 63: Dynamic Abis feature not supported 308

2.5.64 Source 64: Inconsistent number of joker DS0 309

2.5.65 Source 65: Exceeded DL joker DS0 pool number 312

2.5.66 Source 255: Non-significant value 314


2.6.1 Source 0: Incorrect priority on transceiver 316

2.6.2 Source 1: Incorrect setting of channel on transceiver 317

2.6.3 Source 2: Cell without BCCH TDM 317

2.6.4 Source 3: Radio Time Slot not used 317

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

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

2.6.7 Source 6: Missing Site management Abis GSM function 318

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

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


411-9001-104 18.05 2 February 2010



9/844

9

2.6.10 Source 9: Missing RfTrans management Abis GSM function 318

2.6.11 Source 10: Missing cell management Abis GSM function 319

2.6.12 Source 11: Missing TDMA management Abis GSM function 319

2.6.13 Source 12: Missing TS management Abis GSM function 319

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

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




2.9.1 DRX (source: Frequency collision on FH bus) 324

2.9.2 DRX (source: Beginning of TX isolation for maintenance) 324

2.9.3 DRX (source: End of TX isolation for maintenance) 325

2.9.4 DRX (source: FACCH congestion) 325

2.9.5 DRX (source: Nack answer) 326

2.9.6 DRX (source: DRX reset by BSC) 327

2.9.7 SBCF board (source: Unknown message on Abis interface) 327

2.9.8 SBCF board (source: Restart due to reset by BSC) 327

2.9.9 SBCF boards (source: Restart due to reset by reset button) 327

2.9.10 SBCF boards (source: Restart due to power on) 328

2.9.11 SBCF boards (source: Restart due to a too long PCM scanning) 328

2.9.12 SBCF boards (source: Restart requested by the active board) 328

2.9.13 SBCF boards (source: Restart due to a software upgrade) 329

2.9.14 SBCF boards (source: Restart due to hardware watchdog) 329

2.9.15 SBCF boards (source: Restart due to double bus fault) 329

2.9.16 SBCF boards (source: restart due to Man Machine Interface I and Creset button) 329



2.11.1 ABIS_BTS_SYNCHRO (source: SYNO clock not locked on the network)(S2000H BTS) 344

2.11.2 ABIS_BTS_SYNCHRO (source: SYNO clock not locked on the network)(S2000L BTS) 349

2.11.3 AC power supply (source: Power fault) (S2000H BTS) 354

2.11.4 AC power supply (source: Power fault) (S2000L BTS) 357

2.11.5 Cabinet high temperature alarm (source: Threshold exceeded) 360

2.11.6 Cabinet low temperature alarm (source: Threshold exceeded) 3632.11.7 DC power supply (source: Power fault) (S2000H BTS) 366

2.11.8 DC power supply (source: Power fault) (S2000L) 369

2.11.9 External alarm (source: External alarm) 373

2.11.10 DRX (source: RX fault) 373

2.11.11 DRX (source: Loss of PCM link) 376

2.11.12 DRX (source: BBFILTER ASIC fault) 378


411-9001-104 18.05 2 February 2010



10/844

10

2.11.13 DRX (source: Self test failed) 381

2.11.14 DRX (source: Major fault on TX) (S2000H BTS) 383

2.11.15 DRX (source: Major fault on TX) (S2000L BTS) 386

2.11.16 DRX (source: DRX link) (S2000H BTS) 388

2.11.17 DRX (source: DRX link) (S2000L BTS) 391

2.11.18 DRX (source: The TX has not acknowledged the power consignrequest) 393

2.11.19 DRX (source: PA DRX control loop fault) (S2000H BTS) 397

2.11.20 DRX (source: PA DRX control loop fault) (S2000L BTS) 400

2.11.21 DRX diversity reception chain (source: Software detection) (S2000HBTS) 403

2.11.22 DRX diversity reception chain (source: Software detection) (S2000LBTS) 405

2.11.23 DRX main reception chain (source: Software detection) (S2000HBTS) 408

2.11.24 DRX main reception chain (source: Software detection) (S2000L

BTS) 4102.11.25 LNA (source: Software detection) (S2000H BTS) 412

2.11.26 LNA (source: Software detection) (S2000L BTS) 415

2.11.27 PA (source: Hardware) (S2000H BTS) 417

2.11.28 PA (source: Hardware) (S2000L BTS) 419

2.11.29 PA (source: DRX/PA connection) (S2000H BTS) 421

2.11.30 PA (source: DRX/PA connection) (S2000L BTS) 424

2.11.31 PCM (source: PCM) 426

2.11.32 RX splitter D (source: Over current) (S2000H BTS) 426

2.11.33 RX splitter D (source: Over current) (S2000L BTS) 429

2.11.34 RX splitter M (source: Over current) (S2000H BTS) 431

2.11.35 RX splitter M (source: Over current) (S2000L BTS) 434

2.11.36 Splitter output (source: Over current) (S2000H BTS) 436

2.11.37 Splitter output (source: Over current) (S2000L BTS) 438

2.11.38 Transmit antenna (source: VSWR) (S2000H BTS) 441

2.11.39 Transmit antenna (source: VSWR) (S2000L BTS) 443

2.11.40 VGA (source: Fault on VGA) (S2000H BTS) 446



2.13.1 Source 9: No response to LOAD message 450

2.13.2 Source 10: Received LOAD INIT NACK 450

2.13.3 Source 11: Received message LOAD DATA NACK 4502.13.4 Source 12: Received message LOAD END NACK 450

2.13.5 Source 13: Received message 450


FAULT ANALYSIS 451

2.15 Fault number: 1165 (S2000H, S2000L) 452



411-9001-104 18.05 2 February 2010



11/844

11







2.23 Fault number: 1508 (S2000H/L) 460

2.24 Applicability of the fault numbers to the BTS type 461

Chapter 3 e-cell fault numbers 4633.1 Fault number: 1051 (e-cell) 463

3.2 Fault number: 1052 (e-cell) 463

3.2.1 Source 0: No response to status request 472

3.2.2 Source 1: Bad hardware reference or manufacturer ID 474

3.2.3 Source 2: SUP stop receipt 475

3.2.4 Source 3: No change to one BOOT after reset 478

3.2.5 Source 4: This entity is engaged in another downloading Source 8:Wrong software reference on a non downloadable TEI 479

3.2.6 Source 5: Software not compatible with hardware 480

3.2.7 Source 6: File access error 483

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

file 484

3.2.9 Source 9: No response to download message 485

3.2.10 Source 14: Received CSM LOAD CONTAINER NAK 487

3.2.11 Source 15: File to download empty 489

3.2.12 Source 16: File to download unavailable 492

3.2.13 Source 17: Buffer allocation failure 492

3.2.14 Source 18: Bad sending buffer size value 495

3.2.15 Source 19: Failure during OMU switchover 497

3.2.16 Source 20: Bad TEI sent by BTS in the CSM software update reportmessage 499

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

3.2.18 Source 22: CSM software update report with the cause - equipmentfailure - 504

3.2.19 Source 23: CSM software update report with the cause - downloadingfailure - 506

3.2.20 Source 24: CSM software update report with the cause - not able to

perform- 5093.2.21 Source 25: CSM software update report with the cause - wrong software

reference - 511

3.2.22 Source 26: CSM software update report with the cause - wrongconfiguration reference - 513

3.2.23 Source 27: CSM software update report with the cause - restart request- 516

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


411-9001-104 18.05 2 February 2010



12/844

12

inconsistency - 518

3.2.25 Source 29: CSM software update report with the cause - message outof sequence - 520

3.2.26 Source 30: CSM software update report with the cause - backgroundnot available - 523

3.2.27 Source 31: CSM software update report with the cause - incompatibleRM version - 525

3.2.28 Source 32: CSM software update report with the cause - downloading inprogress - 527

3.2.29 Source 33: Bad report sent by BTS in the CSM software update reportmessage 530

3.2.30 Source 34: No BTS response on CSM software update init-control

message 532

3.2.31 Source 35: Nack received on the abort requested by operator 534

3.2.32 Source 36: Bad report sent by BTS in the CSM software update abortmessage 537

3.2.33 Source 37: No BTS response on CSM software update abortmessage 539

3.2.34 Source 38: Flash activate nack with the cause - unknown TEI - 541

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

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

3.2.37 Source 41: Flash activate nack with the cause - not able to perform- 548

3.2.38 Source 42: Flash activate nack with the cause - flash inconsistency- 550

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

3.2.40 Source 44: Flash activate nack with the cause - wrong soft ref - 555

3.2.41 Source 45: Flash activate nack with the cause - wrong config ref - 557

3.2.42 Source 46: CSM downloading start nack with the cause - unknown TEI- 559

3.2.43 Source 47: CSM downloading start nack with the cause - equipmentfailure - 561

3.2.44 Source 48: CSM downloading start nack with the cause - downloadingfailure - 564

3.2.45 Source 49: CSM downloading start nack with the cause - message outof sequence - 566

3.2.46 Source 50: CSM downloading start nack with the cause - wrong soft ref- 568

3.2.47 Source 51: CSM downloading start nack with the cause - wrong configref - 571

3.2.48 Source 52: CSM downloading start nack with a bad cause 573

3.2.49 Source 53: No BTS response on CSM downloading start message 575

3.2.50 Source 54: CSM downloading end nack with the cause - unknown TEI


411-9001-104 18.05 2 February 2010



13/844

13

- 577

3.2.51 Source 55: CSM downloading end nack with the cause - equipmentfailure - 580

3.2.52 Source 56: CSM downloading end nack with the cause - downloadingfailure - 582

3.2.53 Source 57: CSM downloading end nack with the cause - value out ofrange - 584

3.2.54 Source 58: CSM downloading end nack with a bad cause 586

3.2.55 Source 59: No BTS response on CSM downloading end message 589

3.2.56 Source 60: CSM load init nack with the cause - equipment failure - 591

3.2.57 Source 61: CSM load init nack with the cause - downloading failure- 593

3.2.58 Source 62: CSM load init nack with the cause - message out ofsequence - 595

3.2.59 Source 63: CSM load init nack with the cause - wrong file ref - 598

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

- 6003.2.61 Source 65: CSM load init nack with the cause - data format error - 602

3.2.62 Source 66: CSM load init nack with a bad cause 605

3.2.63 Source 67: No BTS response on CSM load init message 607

3.2.64 Source 68: CSM load data nack with the cause - equipment failure- 609

3.2.65 Source 69: CSM load data nack with the cause - downloading failure- 611

3.2.66 Source 70: CSM load data nack with the cause - message out ofsequence - 614

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

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

- 618

3.2.69 Source 73: CSM load data nack with the cause - data inconsistency- 620

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

3.2.71 Source 75: CSM load data nack with the cause - bad block tag - 625

3.2.72 Source 76: CSM load data nack with the cause - checksum error - 627

3.2.73 Source 77: CSM load data nack with a bad cause 629

3.2.74 Source 78: Unexpected CSM load data ack 632

3.2.75 Source 79: No BTS response on CSM load data message 6343.2.76 Source 80: CSM load end nack with the cause - equipment failure

- 636

3.2.77 Source 81: CSM load end nack with the cause - downloading failure- 638

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

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


411-9001-104 18.05 2 February 2010



14/844

14

sequence - 643

3.2.80 Source 84: CSM load end nack with the cause - data format error- 645

3.2.81 Source 85: CSM load end nack with the cause - wrong file ref - 647

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

- 650

3.2.83 Source 87: CSM load end nack with the cause - checksum error - 652

3.2.84 Source 88: CSM load end nack with a bad cause 654

3.2.85 Source 89: No BTS response on CSM load end message 656

3.2.86 Source 90: Bad report sent by BTS during an internal update 659

3.2.87 Source 91: CSM load init nack with the cause - file already open - 661

3.2.88 Source 92: CSM load init nack with the cause - invalid mode - 663

3.2.89 Source 93: CSM load init nack with the cause - file cannot be unloaded- 665

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

- 668

3.2.91 Source 95: CSM load data nack with the cause - file cannot be unloaded- 670

3.2.92 Source 96: CSM load data nack with the cause - flash flag cannotaccess - 672

3.2.93 Source 97: CSM load data nack with the cause - boot cannot beunloaded - 674

3.2.94 Source 98: CSM load data nack with the cause - data decode error- 677

3.2.95 Source 99: CSM load data nack with the cause - table cannot access- 679

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

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

- 684

3.2.98 Source 102: CSM load data nack with the cause - flash RAM error- 686

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

3.2.100 Source 104: CSM load data nack with the cause - internal abort - 690

3.2.101 Source 105: CSM flash activate response with a bad cause 693

3.2.102 Source 106: DTM error during token allocation 695

3.2.103 Source 107: CSM software update report with the cause: TRX softwareincompatibility 697

3.2.104 Source 108: Too many different deliveries in the cell group 699




3.5.1 Source 1: Equipment failure 707

3.5.2 Source 2: Equipment unable to perform such test 708

3.5.3 Source 3: Equipment unable to perform such configuration 709


411-9001-104 18.05 2 February 2010



15/844

15

3.5.4 Source 4: Unknown test 710

3.5.5 Source 5: Cell parameters inconsistency 710

3.5.6 Source 6: Data inconsistency 712

3.5.7 Source 7: Value out of range 713

3.5.8 Source 8: TEI not present 713

3.5.9 Source 9: Unknown Abis PCM_Time_Slot 714

3.5.10 Source 10: Unknown Abis PCM 714

3.5.11 Source 11: Wrong software reference 715

3.5.12 Source 12: Further files required 715

3.5.13 Source 13: Failure during activation 716

3.5.14 Source 14: Data format error 716

3.5.15 Source 15: Window overflow 716

3.5.16 Source 16: Normal completion 716

3.5.17 Source 17: Transfer aborted 716

3.5.18 Source 18: Checksum error 717

3.5.19 Source 19: File incomplete 7173.5.20 Source 20: File already present and correct 717

3.5.21 Source 21: File cannot be downloaded 717

3.5.22 Source 22: Entity engaged in other download 718

3.5.23 Source 23: Too many signaling timeslots 718

3.5.24 Source 24: Too many TEI connections to physical channel 719

3.5.25 Source 25: Out of sequence message 719

3.5.26 Source 26: Incorrect IEI 721

3.5.27 Source 27: Wrong file reference 722

3.5.28 Source 28: Bad cell number 722

3.5.29 Source 29: Bad related TEI 722

3.5.30 Source 30: Bad timeslot 722

3.5.31 Source 31: Window size not allowed 722

3.5.32 Source 32: Flash boot required 723

3.5.33 Source 33: Wrong config reference 723

3.5.34 Source 34: The BTS has not acknowledged the TX power consignrequest 723

3.5.35 Source 35: Downloading aborted 728

3.5.36 Source 36: Files missing 728

3.5.37 Source 37: Buffer overflow 729

3.5.38 Source 38: Block not received 729

3.5.39 Source 39: Downloading restart 729

3.5.40 Source 40: Request not supported 729

3.5.41 Source 41: Downloading failure 729

3.5.42 Source 42: Start-up failure 730

3.5.43 Source 43: Maximum number of joker TS 730

3.5.44 Source 44: Bad chain type 733

3.5.45 Source 45: Bad radio timeslot reference 733

3.5.46 Source 46: Bad internal Link EDGE configuration 733


411-9001-104 18.05 2 February 2010



16/844

16

3.5.47 Source 47: Inconsistency mapping 733

3.5.48 Source 48: Inconsistency number of joker DS0 734

3.5.49 Source 49: Invalid mode 734

3.5.50 Source 50: File already open 734

3.5.51 Source 51: File cannot be unloaded 734

3.5.52 Source 52: Boot cannot be unloaded 734

3.5.53 Source 53: Data decode error 735

3.5.54 Source 54: Flash flag cannot access 735

3.5.55 Source 55: Table cannot access 735

3.5.56 Source 56: RAM mapping error 735

3.5.57 Source 57: Flash access error 735

3.5.58 Source 58: Flash write error 736

3.5.59 Source 59: Flash erase error 736

3.5.60 Source 60: Internal abort 736

3.5.61 Source 61: Equipment not able to get external synchronization 736

3.5.62 Source 62: Synchronization in progress 7363.5.63 Source 63: Dynamic Abis feature not supported 737

3.5.64 Source 64: Inconsistent number of joker DS0 738

3.5.65 Source 65: Exceeded DL joker DS0 pool number 740

3.5.66 Source 255: Non-significant value 742




3.8.1 PMNU (source: Message unknown) 746

3.8.2 PMNU (source: Restart due to reset by BSC) 746

3.8.3 PMNU (source: Restart due to reset by reset button) 746

3.8.4 PMNU (source: Restart due to power on) 746

3.8.5 PMNU (source: Restart due to a too long PCM scanning) 747

3.8.6 PMNU (source: Restart requested by the active board) 747

3.8.7 PMNU (source: restart due to a software upgrade) 747

3.8.8 PMNU (source: Restart due to a hardware watchdog) 748

3.8.9 PMNU (source: Restart due to loss of lock) 748

3.8.10 PMOD (source: FACCH congestion) 748

3.8.11 PMOD (source: PMOD reset by BCF after message nonacknowledged) 749

3.8.12 PMOD (source: Restart due to the timeout on the OML link with

BSC) 749

3.8.13 PMOD (source: Restart due to the timeout on the OML link withBCF) 750

3.8.14 PMOD (source: Restart due to a software upgrade) 750

3.8.15 PMOD (source: BCCH config dump) 750

3.8.16 PMOD (source: SACCH config dump) 751

3.8.17 PMOD (source: L1M config dump) 751

3.8.18 PMOD (source: RSL anomaly) 751


411-9001-104 18.05 2 February 2010



17/844

17


3.10 Attribute value change: 1063 (e-cell) 753


3.11.1 Abis BTS synchro (source: SYNO clock not locked on thenetwork) 758

3.11.2 AC power supply (source: Power fault) 763

3.11.3 External alarm (source: External alarm) 766

3.11.4 Internal temperature (source: Threshold exceeded) 766

3.11.5 PA (source: Hardware) 768

3.11.6 PA (source: PA DRX control loop fault) 773

3.11.7 PCM (source: PCM) 778

3.11.8 PMNU (source: Base-extension communication fault) 778

3.11.9 PMNU (source: Self test failed) 780

3.11.10 PMNU (source: Hardware) 785

3.11.11 PMOD (source: BBFILTER ASIC fault) 789

3.11.12 PMOD (source: Self test failed) 7943.11.13 PMOD (source: Major fault on TX) 798

3.11.14 PMOD (source: The TX has not acknowledged the power consign

request) 803

3.11.15 PMOD (source: BCCH first config failed) 806

3.11.16 PMOD (source: BCCH second config failed) 806

3.11.17 PMOD (source: SACCH first config failed) 807

3.11.18 PMOD (source: SACCH second config failed) 807

3.11.19 PMOD (source: L1M first config failed) 808

3.11.20 PMOD (source: L1M second config failed) 809

3.11.21 PSU (source: PSU failure) 809

3.11.22 RDRX (source: RX fault) 8113.11.23 RDRX (source: Hardware) 816



3.13.1 Source 9: No response to LOAD message 825

3.13.2 Source 10: Received LOAD INIT NACK 825

3.13.3 Source 11: Received message LOAD DATA NACK 826

3.13.4 Source 12: Received message LOAD END NACK 826

3.13.5 Source 13: Received message 826


FAULT ANALYSIS 826









411-9001-104 18.05 2 February 2010



18/844

18






411-9001-104 18.05 2 February 2010



19/844

19.

New in this release

The following section describe what is new in this release for Nortel GSM BTS S8006 Troubleshooting (411-9001-104) for V18.0 P&C 2 release.

“Features” (page 19)

FeaturesThis document contains no feature updates in this release.


411-9001-104 18.05 2 February 2010



20/844

20 New in this release


411-9001-104 18.05 2 February 2010



21/844

21.

Introduction

This document contains the fault number description and the maintenanceactions required for the S2000 H/L and e-cell Base Transceiver Station(BTS).

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

• Nortel GSM BSS Documentation Roadmap (411-9001-000)

• Nortel GSM BSS Overview (411-9001-001)

• Nortel GSM BSS Fundamentals - Operating Principles (411-9001-007)

• Nortel GSM BSS Configuration - Operating Procedures (411-9001-034)

• Nortel GSM BTS S2000H/S2000L Fundamentals (411-9001-035)

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

• Nortel GSM BTS S2000H/S2000L Troubleshooting (411-9001-049)

• Nortel GSM BTS Commissioning - TML User Guide (411-9001-051)

• Nortel GSM BTS e-cell Troubleshooting (411-9001-090)

• Nortel GSM BSS Parameter Reference (411-9001-124)

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


411-9001-104 18.05 2 February 2010



22/844

22 Introduction

NavigationThis document consists of 3 chapters:

• Chapter 1 “How to use this manual” (page 23), describes how to usethis maintenance manual.

• Chapter 2 “S2000 H/L BTS fault numbers” (page 27), contains thefault number description and the corrective maintenance proceduresapplicable to the S2000 H/L BTS.

• Chapter 3 “e-cell fault numbers” (page 463), contains the fault numberdescription and the corrective maintenance procedures applicable tothe e-cell BTS.


411-9001-104 18.05 2 February 2010



23/844

23.

Chapter 1 How to use this manual

1.1 IntroductionThis manual contains the fault number description and the correctivemaintenance procedures applicable to the S2000 H/L BTS and e-cell forGSM 850, 900, 1800, and 1900.

The general principles and messages required for BSS maintenanceare described in: Nortel GSM BSS Fault Management - Maintenance Principles (411-9001-039)

The network maintenance is based on the graphical supervision of thenetwork at the OMC-R.

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

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 any defense actions, they are local and controlled by the BTS (faultnumber 1067).


411-9001-104 18.05 2 February 2010



24/844

24 Chapter 1 How to use this manual

• spontaneous messages indicating a transient event for warning (faultnumber 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 relationships with the BTS or part of it (1051, 1052, 1053, 1054,1055, 1059, 1073).

1.3 Description of a fault number sheetA corrective maintenance sheet contains the following information:

• the header

• the main body composed of three 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 sheet

The main body contains the following information:• Fault analysis

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


411-9001-104 18.05 2 February 2010



25/844

1.3 Description of a fault number sheet 25

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.


411-9001-104 18.05 2 February 2010



26/844

26 Chapter 1 How to use this manual


411-9001-104 18.05 2 February 2010



27/844

27.

Chapter 2 S2000 H/L BTS faultnumbers

2.1 Fault number: 1051 (S2000 H/L BTS)

Fault number:

1051 : Loss of layer 3 with remote GSM entity

Type : communicationsAlarm

This problem is associated with a PCM fault. see: Nortel GSM BSS Fault Clearing - Advanced Maintenance Procedures (411-9001-105)

2.2 Fault number: 1052 (S2000 H/L 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.

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

Table 1 "Fault number 1052 sources" (page 28) indicates all the sourcesof the fault number 1052 for the S2000 H/L BTS. For more information

on each source, see the indicated paragraph to know the correctivemaintenance procedure associated with this source.


411-9001-104 18.05 2 February 2010



28/844

28 Chapter 2 S2000 H/L BTS fault numbers

Table 1Fault number 1052 sources

SourceNo.

Source wording Paragraph

0 No response to statusrequest 2.2.1 “Source 0: No response to statusrequest” (page 36)

1 Bad hardware referenceor manufacturer ID

2.2.2 “Source 1: Bad hardware referenceor manufacturer ID” (page 38)

2 SUP stop receipt 2.2.3 “Source 2: SUP stop receipt”(page 40)

3 No change to one ofBOOT after reset

2.2.4 “Source 3: No change to one ofBOOT after reset” (page 43)

4 This entity is engagedin another downloading

2.2.5 “Source 4: This entity is engagedin another downloadingSource 8:

Wrong software reference on a non

downloadable TEI” (page 45)

5 Software not compatiblewith hardware

2.2.6 “Source 5: Software not compatiblewith hardware” (page 47)

6 File access error 2.2.7 “Source 6: File access error”(page 51)

7 Repetitive errors

(NACK, timeout, ...)while downloading a file

2.2.8 “Source 7:Repetitive errors (NACK,

timeout, ...) while downloading afile” (page 54)

8 Wrong softwarereference on a nondownloadable TEI

2.2.5 “Source 4: This entity is engagedin another downloadingSource 8:

Wrong software reference on a nondownloadable TEI” (page 45)

9 No response todownload message

2.2.9 “Source 9: No response to downloadmessage” (page 55)

14 CSM load containernegative acknowle

dgement

2.2.10 “Source 14: Received CSM LOADCONTAINER NAK” (page 57)

15 File to download empty 2.2.11 “Source 15: File to downloadempty” (page 59)

16 File to downloadunavailable

2.2.12 “Source 16: File to downloadunavailable” (page 62)

17 Buffer allocation failure 2.2.13 “Source 17: Buffer allocationfailure” (page 62)

18 Bad sending buffersize value

2.2.14 “Source 18: Bad sending buffersize value” (page 65)

19 Failure during OMUswitchover

2.2.15 “Source 19: Failure during OMUswitchover” (page 67)


411-9001-104 18.05 2 February 2010



29/844


Table 1Fault number 1052 sources (cont’d.)

SourceNo.


20 Bad TEI sent by BTSin the CSM software

update report message

2.2.16 “Source 20: Bad TEI sent byBTS in the CSM software update report

message” (page 69)

21 CSM software updatereport with the cause

’unknown TEI’

2.2.17 “Source 21: CSM softwareupdate report with the cause - unknown

TEI -” (page 72)


’equipment failure’

2.2.18 “Source 22: CSM softwareupdate report with the cause - equipment

failure -” (page 74)


"downloading failure"

2.2.19 “Source 23: CSM software updatereport with the cause - downloading

failure -” (page 76)24 CSM software update

report with the cause"not able to perform"

2.2.20 “Source 24: CSM softwareupdate report with the cause - not able

to perform-” (page 79)


"wrong soft ref"

2.2.21 “Source 25: CSM software updatereport with the cause - wrong software

reference -” (page 81)


"wrong config ref"

2.2.22 “Source 26: CSM software updatereport with the cause - wrong configuration

reference -” (page 83)

27 CSM software update

report with the cause"restart request"

2.2.23 “Source 27: CSM software

update report with the cause - restartrequest -” (page 86)


"data inconsistency"

2.2.24 “Source 28: CSM softwareupdate report with the cause - data

inconsistency -” (page 88)


"message out ofsequence"

2.2.25 “Source 29: CSM software updatereport with the cause - message out

of sequence -” (page 90)

30 CSM software updatereport with the cause"background not

available"

2.2.26 “Source 30: CSM software updatereport with the cause - background notavailable -” (page 93)


"incompatible RMversion"

2.2.27 “Source 31: CSM software updatereport with the cause - incompatible

RM version -” (page 95)


411-9001-104 18.05 2 February 2010



30/844



SourceNo.



"downloading inprogress"

2.2.28 “Source 32: CSM software updatereport with the cause - downloading

in progress -” (page 97)

33 Bad report sent by BTSin the CSM software

update report message

2.2.29 “Source 33: Bad report sent byBTS in the CSM software update report


34 No BTS response onCSM software updateinit/control message

2.2.30 “Source 34: No BTS responseon CSM software update init-control


35 Nack received on the

abort requested byoperator

2.2.31 “Source 35: Nack received on the

abort requested by operator” (page 104)

36 Bad report sent by BTSin the CSM software

update abort message

2.2.32 “Source 36: Bad report sent byBTS in the CSM software update abort


37 No BTS response onCSM software update

abort message

2.2.33 “Source 37: No BTS responseon CSM software update abort


38 Flash activate nack withthe cause "unknown

TEI"

2.2.34 “Source 38: Flash activatenack with the cause - unknown TEI

-” (page 111)

39 Flash activate nack withthe cause "equipment

failure"

2.2.35 “Source 39: Flash activatenack with the cause - equipment


40 Flash activate nack withthe cause "downloading

failure"

2.2.36 “Source 40: Flash activatenack with the cause - downloading


41 Flash activate nackwith the cause "not able

to perform"

2.2.37 “Source 41: Flash activatenack with the cause - not able to

perform -” (page 118)

42 Flash activate nack

with the cause "flash

inconsistency"

2.2.38 “Source 42: Flash activate nack

with the cause - flash inconsistency

-” (page 120)

43 Flash activate nackwith the cause "data

inconsistency"

2.2.39 “Source 43: Flash activate nackwith the cause - data inconsistency

-” (page 122)

44 Flash activate nackwith the cause "wrong

soft ref"

2.2.40 “Source 44: Flash activatenack with the cause - wrong soft ref

-” (page 125)


411-9001-104 18.05 2 February 2010



31/844



SourceNo.


45 Flash activate nackwith the cause "wrong

config ref"

2.2.41 “Source 45: Flash activatenack with the cause - wrong config

ref -” (page 127)

46 CSM downloading startnack with the cause

"unknown TEI"

2.2.42 “Source 46: CSM downloadingstart nack with the cause - unknown

TEI -” (page 129)

47 CSM downloading startnack with the cause"equipment failure"

2.2.43 “Source 47: CSM downloadingstart nack with the cause - equipment




2.2.44 “Source 48: CSM downloadingstart nack with the cause - downloading

failure -” (page 134)49 CSM downloading

start nack with thecause "message out

of sequence"

2.2.45 “Source 49: CSM downloadingstart nack with the cause - message out

of sequence -” (page 136)


"wrong soft ref"

2.2.46 “Source 50: CSM downloadingstart nack with the cause - wrong soft

ref -” (page 138)


"wrong config ref"

2.2.47 “Source 51: CSM downloadingstart nack with the cause - wrong

config ref -” (page 141)

52 CSM downloading startnack with a bad cause

2.2.48 “Source 52: CSM downloading startnack with a bad cause” (page 143)

53 No BTS response onCSM downloading start

message

2.2.49 “Source 53: No BTS responseon CSM downloading start message”

(page 145)

54 CSM downloading endnack with the cause

"unknown TEI"

2.2.50 “Source 54: CSM downloadingend nack with the cause - unknown

TEI -” (page 147)


"equipment failure"

2.2.51 “Source 55: CSM downloadingend nack with the cause - equipment




2.2.52 “Source 56: CSM downloadingend nack with the cause - downloading


57 CSM downloading endnack with the cause"value out of range"

2.2.53 “Source 57: CSM downloadingend nack with the cause - value out

of range -” (page 154)


411-9001-104 18.05 2 February 2010



32/844



SourceNo.


58 CSM downloading endnack with a bad cause

2.2.54 “Source 58: CSM downloading endnack with a bad cause” (page 156)

59 no BTS response onCSM downloading end

message

2.2.55 “Source 59: No BTS responseon CSM downloading end message”

(page 159)

60 CSM load init nack withthe cause "equipment

failure"

2.2.56 “Source 60: CSM load init nack withthe cause - equipment failure -” (page 161)

61 CSM load init nack withthe cause "downloading

failure"

2.2.57 “Source 61: CSM load initnack with the cause - downloading


62 CSM load init nack withthe cause "message

out of sequence"

2.2.58 “Source 62: CSM load initnack with the cause - message out of

sequence -” (page 165)63 CSM load init nack

with the cause "wrongfile ref"

2.2.59 “Source 63: CSM load init nack with

the cause - wrong file ref -” (page 168)

64 CSM load init nackwith the cause "window

size not allow"

2.2.60 “Source 64: CSM load initnack with the cause - window size not

allowed -” (page 170)

65 CSM load init nack

with the cause "dataformat error"


the cause - data format error -” (page 172)

66 CSM load init nack witha bad cause

2.2.62 “Source 66: CSM load init nackwith a bad cause” (page 175)

67 No BTS response onCSM load init message

2.2.63 “Source 67: No BTS response onCSM load init message” (page 177)

68 CSM load datanack with the cause"equipment failure"

2.2.64 “Source 68: CSM load datanack with the cause - equipment


69 CSM load datanack with the cause


2.2.65 “Source 69: CSM load datanack with the cause - downloading


70 CSM load datanack with the cause

"message out ofsequence"

2.2.66 “Source 70: CSM load datanack with the cause - message out of

sequence -” (page 184)

71 CSM load data nack

with the cause "dataformat error"

2.2.67 “Source 71: CSM load data

nack with the cause - data formaterror -” (page 186)


411-9001-104 18.05 2 February 2010



33/844



SourceNo.


72 CSM load data nackwith the cause "window

overflow"

2.2.68 “Source 72: CSM load data nackwith the cause - window overflow

-” (page 188)

73 CSM load data nackwith the cause "data

inconsistency"

2.2.69 “Source 73: CSM load data nackwith the cause - data inconsistency

-” (page 190)

74 CSM load data nackwith the cause "block

not received"

2.2.70 “Source 74: CSM load data nackwith the cause - block not received

-” (page 193)

75 CSM load data nackwith the cause "bad

block tag"

2.2.71 “Source 75: CSM load datanack with the cause - bad block tag

-” (page 195)76 CSM load data

nack with the cause"checksum error"

2.2.72 “Source 76: CSM load datanack with the cause - checksum

error -” (page 197)

77 CSM load data nackwith a bad cause

2.2.73 “Source 77: CSM load data nackwith a bad cause” (page 199)

78 Unexpected CSM loaddata ack

2.2.74 “Source 78: Unexpected CSMload data ack” (page 202)

79 No BTS response

on CSM load datamessage

2.2.75 “Source 79: No BTS response on

CSM load data message” (page 204)

80 CSM load end nackwith the cause

"equipment failure"

2.2.76 “Source 80: CSM load endnack with the cause - equipment


81 CSM load end nack

with the cause"downloading failure"

2.2.77 “Source 81: CSM load end

nack with the cause - downloadingfailure -” (page 208)

82 CSM load end nackwith the cause "value

out of range"

2.2.78 “Source 82: CSM load endnack with the cause - value out of

range -” (page 211)

83 CSM load end nack

with the cause"message out of

sequence"

2.2.79 “Source 83: CSM load end

nack with the cause - message out ofsequence -” (page 213)

84 CSM load end nackwith the cause "data

format error"

2.2.80 “Source 84: CSM load endnack with the cause - data format



411-9001-104 18.05 2 February 2010



34/844



SourceNo.


85 CSM load end nackwith the cause "wrong

file ref"

2.2.81 “Source 85: CSM load endnack with the cause - wrong file ref

-” (page 217)

86 CSM load end nackwith the cause "data

inconsistency"

2.2.82 “Source 86: CSM load end nackwith the cause - data inconsistency

-” (page 220)

87 CSM load end nackwith the cause

"checksum error"

2.2.83 “Source 87: CSM load endnack with the cause - checksum


88 CSM load end nackwith a bad cause

2.2.84 “Source 88: CSM load end nackwith a bad cause” (page 224)

89 No BTS response onCSM load end message

2.2.85 “Source 89: No BTS response onCSM load end message” (page 226)

90 Bad report sent byBTS during an internal

update

2.2.86 “Source 90: Bad report sent by BTSduring an internal update” (page 229)

91 CSM load init nackwith the cause "file

already open"

2.2.87 “Source 91: CSM load init nack withthe cause - file already open -” (page 231)

92 CSM load init nack

with the cause "invalidmode"


the cause - invalid mode -” (page 233)

93 CSM load init nack withthe cause "file cannot

be unloaded"

2.2.89 “Source 93: CSM load initnack with the cause - file cannot be

unloaded -” (page 235)

94 CSM load init nack withthe cause "flash flag

cannot access"

2.2.90 “Source 94: CSM load init nackwith the cause - flash flag cannot

access -” (page 238)

95 CSM load data nackwith the cause "file

cannot be unloaded"

2.2.91 “Source 95: CSM load datanack with the cause - file cannot be


96 CSM load data nackwith the cause "flashflag cannot access"

2.2.92 “Source 96: CSM load datanack with the cause - flash flag cannot


97 CSM load data nackwith the cause "bootcannot be unloaded"

2.2.93 “Source 97: CSM load datanack with the cause - boot cannot be



411-9001-104 18.05 2 February 2010



35/844



SourceNo.


98 CSM load data nackwith the cause "data

decod error"

2.2.94 “Source 98: CSM load datanack with the cause - data decode


99 CSM load data nackwith the cause "table

cannot access"

2.2.95 “Source 99: CSM load datanack with the cause - table cannot


100 CSM load data nackwith the cause "ram

mapping error"

2.2.96 “Source 100: CSM load datanack with the cause - RAM mapping


101 CSM load data nackwith the cause "flash

access error"

2.2.97 “Source 101: CSM load datanack with the cause - flash access

error -” (page 254)102 CSM load data nack

with the cause "flashram error"

2.2.98 “Source 102: CSM load datanack with the cause - flash RAM


103 CSM load data nackwith the cause "flash

erase error"

2.2.99 “Source 103: CSM load datanack with the cause - flash erase


104 CSM load data nackwith the cause "internal

abort"

2.2.100 “Source 104: CSM load datanack with the cause - internal abort

-” (page 260)

REACTION OF THE SYSTEM

BSC defense

The BSC attempts a maximum of five software downloadings. If the fiveattempts fail, the BSC sends a fault number 1052 and a state change onthe btsSiteManager object to "disabled-failed".

Impact on the service

• Case of the btsSiteManager object

The site is not downloaded.

CAUTIONService interruptionThe service is reduced or lost depending on theconfiguration.

• Case of the transceiverEquipment object

The TRX is not downloaded, one TDMA is not configured.


411-9001-104 18.05 2 February 2010



36/844


ATTENTIONThe service is reduced.

2.2.1 Source 0: No response to status request

Fault number 1052 : GSM entity downloading failure

Source: (0) No response to status request

BTS model: S2000H/L

FAULT ANALYSISThis source indicates that the BTS has not replied to the status request.

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 a faultnumber concerning PCMs (see 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures) ).

— 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-104 18.05 2 February 2010



37/844


— 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 the fault number 1052 is still present, treat it (seeabove).

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

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.

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


411-9001-104 18.05 2 February 2010



38/844


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

4 The procedure is complete.

--End--

2.2.2 Source 1: Bad hardware reference or manufacturer ID


Source:BTS model:

(1) Bad hardware reference or manufacturer ID S2000 H/L

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.

TROUBLESHOOTINGPreliminary checks

Step Action





411-9001-104 18.05 2 February 2010



39/844




— Clear the alarm. — The procedure is complete.


— If a pcmCircuit object is "disabled-failed", look for a faultnumber concerning PCMs (see Nortel GSM BSS FaultClearing - Advanced Maintenance (411-9001-105) ).

— If a lapdLink object is "disabled-failed", the BSC isconcerned. Look for alarms about 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.Go to step 4.

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


– If other fault numbers are present too, such as faultnumber 1054, treat them (concerning fault number1054 (loss of layer 2), see Nortel GSM BSS FaultClearing - Advanced Maintenance (411-9001-105) ).

• 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 DRX by performing the "Display all"command on the transceiverEquipment object.

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



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


411-9001-104 18.05 2 February 2010



40/844



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

— If a pcmCicruit object is "disabled-failed", look for a faultnumber concerning PCMs (see Nortel GSM BSS FaultClearing - Advanced Maintenance (411-9001-105) ).


• If the operationalState of the transceiverEquipment object is"disabled-failed", the DRX 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 the

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


– If other fault numbers are present too, such as faultnumber 1054, treat them (concerning fault number1054 (loss of layer 2), see Nortel GSM BSS FaultClearing - Advanced Maintenance (411-9001-105) ).

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

transceiverEquipment object.

Case of the btsSiteManager object for the S2000 H/L BTS 4 Set the value of the "hardwareRef" parameter to "0".


Case of the transceiverEquipment object for the S2000 H/L BTS 6 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: S2000H/L


411-9001-104 18.05 2 February 2010



41/844


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

TROUBLESHOOTING

Step Action

Preliminary checks










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

— 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) ).

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


411-9001-104 18.05 2 February 2010



42/844


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



• 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 the btsSiteManager object is "disabled-failed", the siteis not operational. process the alarm(s) concerning thebtsSiteManager object.



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

Procedures)).• If the operationalState of the transceiverEquipment object

is "disabled", the TRX is not operational. Do not processthe alarm and do not clear it. Wait for a state change of thetransceiverEquipment object.


411-9001-104 18.05 2 February 2010



43/844



--End--

2.2.4 Source 3: No change to one of BOOT after resetFault number 1052 : GSM entity downloading failure

Source:BTS model:

(3) No change to one of BOOT after resetS2000 H/L

TROUBLESHOOTINGPreliminary checks

Step Action





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

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

number concerning PCMs (see Nortel GSM BSS FaultClearing - Advanced Maintenance (411-9001-105) ).

— If a lapdLink object is "disabled-failed", the BSC isconcerned. Look for alarms about 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. Then unlock it.

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

— If other fault numbers are present too, such as faultnumber 1054, treat them. Concerning fault number 1054(loss of layer 2), see Nortel GSM BSS Fault Clearing -Advanced Maintenance (411-9001-105) .

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


411-9001-104 18.05 2 February 2010



44/844


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

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

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



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


Documents

GSM BTS S2000H_S2000L_e-Cell Fault Clearing (411-9001-104_18.05)