BTS S2000H - S2000L - E-Cell Fault Clearing

Global System for Mobile Communications (GSM)
Nortel GSM BTS

S2000H/S2000L/e-cell Fault
Clearing
Release: V18.0 PC2
Document Revision: 18.05
www.nortel.com
411-9001-104
.

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 are
subject 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+
Contents
New in this release
Features
19
19
Introduction
21
Chapter 1 How to use this manual
23
1.1 Introduction 23
1.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
27
2.1 Fault number: 1051 (S2000 H/L BTS) 27

2.2.1 Source 0: No response to status request 36
2.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: Wrong
software 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 a
file 54
2.2.9 Source 9: No response to download message 55
2.2.10 Source 14: Received CSM LOAD CONTAINER NAK 57
2.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 report
message 69
Nortel GSM BTS S2000H/S2000L/e-cell Fault Clearing
411-9001-104 18.05 2 February 2010
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 - equipment
failure - 74
2.2.19 Source 23: CSM software update report with the cause - downloading
failure - 76
2.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 software
reference - 81
2.2.22 Source 26: CSM software update report with the cause - wrong
configuration 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 - data
inconsistency - 88
2.2.25 Source 29: CSM software update report with the cause - message out of
sequence - 90
2.2.26 Source 30: CSM software update report with the cause - background not
available - 93
2.2.27 Source 31: CSM software update report with the cause - incompatible
RM version - 95
2.2.28 Source 32: CSM software update report with the cause - downloading in
progress - 97
2.2.29 Source 33: Bad report sent by BTS in the CSM software update report
message 100
2.2.30 Source 34: No BTS response on CSM software update init-control
message 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 abort
message 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
- 118
2.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
- 129
2.2.43 Source 47: CSM downloading start nack with the cause - equipment
failure - 131
2.2.44 Source 48: CSM downloading start nack with the cause - downloading
failure - 134
2.2.45 Source 49: CSM downloading start nack with the cause - message out
of 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 config
ref - 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 - 150
2.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 of
range - 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 - 165
2.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 of
sequence - 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
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 of
sequence - 213
2.2.80 Source 84: CSM load end nack with the cause - data format error
- 215
2.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
- 235
2.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 cannot
access - 242
2.2.93 Source 97: CSM load data nack with the cause - boot cannot be
unloaded - 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
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 288
2.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
2.5.34 Source 34: The BTS has not acknowledged the TX power consign
request 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 305
2.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 308
2.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
2.6.10
2.6.11
2.6.12
2.6.13
2.6.14
Source 9: Missing RfTrans management Abis GSM function 318

Source 10: Missing cell management Abis GSM function 319
Source 11: Missing TDMA management Abis GSM function 319
Source 12: Missing TS management Abis GSM function 319
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) configured
320
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 C
reset 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) 363
2.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
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 consign
request) 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) (S2000H
BTS) 403
2.11.22 DRX diversity reception chain (source: Software detection) (S2000L
BTS) 405
2.11.23 DRX main reception chain (source: Software detection) (S2000H
BTS) 408
2.11.24 DRX main reception chain (source: Software detection) (S2000L
BTS) 410
2.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 450
2.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
2.17
2.18
2.19
2.20
2.21
2.22
2.23
2.24
Fault number: 1259 (S2000 H/L BTS)

Fault number: 1508 (S2000H/L) 460
Applicability of the fault numbers to the
454
455
456
457
458
459
BTS type
461
Chapter 3 e-cell fault numbers
463
3.1 Fault number: 1051 (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 report
message 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 - equipment
failure - 504
3.2.19 Source 23: CSM software update report with the cause - downloading
failure - 506
3.2.20 Source 24: CSM software update report with the cause - not able to
perform- 509
3.2.21 Source 25: CSM software update report with the cause - wrong software
reference - 511
configuration reference - 513
3.2.23 Source 27: CSM software update report with the cause - restart request
- 516
411-9001-104 18.05 2 February 2010
12
inconsistency - 518
3.2.25 Source 29: CSM software update report with the cause - message out
of sequence - 520
3.2.26 Source 30: CSM software update report with the cause - background
not available - 523
3.2.27 Source 31: CSM software update report with the cause - incompatible
RM version - 525
3.2.28 Source 32: CSM software update report with the cause - downloading in
progress - 527
3.2.29 Source 33: Bad report sent by BTS in the CSM software update report
message 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 abort
message 537
message 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 - equipment
failure - 561
3.2.44 Source 48: CSM downloading start nack with the cause - downloading
failure - 564
3.2.45 Source 49: CSM downloading start nack with the cause - message out
of 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 config
ref - 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
- 577
3.2.51 Source 55: CSM downloading end nack with the cause - equipment
failure - 580
3.2.52 Source 56: CSM downloading end nack with the cause - downloading
failure - 582
3.2.53 Source 57: CSM downloading end nack with the cause - value out of
range - 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
sequence - 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
- 600
3.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
sequence - 614
3.2.67 Source 71: CSM load data nack with the cause - data format error
- 616
3.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 634
3.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

411-9001-104 18.05 2 February 2010
14
sequence - 643
- 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 cannot
access - 672
unloaded - 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
- 681
3.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 software
incompatibility 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
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 717
3.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 consign
request 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
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 736
3.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 non
acknowledged) 749
3.8.12 PMOD (source: Restart due to the timeout on the OML link with
BSC) 749
BCF) 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
3.10 Attribute value change: 1063 (e-cell) 753
3.11.1 Abis BTS synchro (source: SYNO clock not locked on the
network) 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) 794
3.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) 811
3.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
3.22
3.23
3.24
3.25
Fault number:
Fault number:
Fault number:
Fault number:
1505
1506
1507
1508
(e-cell)
(e-cell)
(e-cell)
(e-cell)
834
835
836
836

411-9001-104 18.05 2 February 2010
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)
Features
This document contains no feature updates in this release.

411-9001-104 18.05 2 February 2010
20 New in this release

411-9001-104 18.05 2 February 2010
21
Introduction
This document contains the fault number description and the maintenance
actions required for the S2000 H/L and e-cell Base Transceiver Station
(BTS).
Prerequisites
It is recommended that the readers also become familiar with the following
technical documents:
Nortel GSM BSS Documentation Roadmap (411-9001-000)
Nortel GSM BTS S2000H/S2000L Troubleshooting (411-9001-049)
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 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 Introduction
Navigation
This document consists of 3 chapters:
Chapter 1 How to use this manual (page 23), describes how to use
this maintenance manual.
Chapter 2 S2000 H/L BTS fault numbers (page 27), contains the
fault number description and the corrective maintenance procedures
applicable to the S2000 H/L BTS.
Chapter 3 e-cell fault numbers (page 463), contains the fault number
description and the corrective maintenance procedures applicable to
the e-cell BTS.

411-9001-104 18.05 2 February 2010
23
Chapter 1 How to use this manual

1.1 Introduction
This manual contains the fault number description and the corrective
maintenance procedures applicable to the S2000 H/L BTS and e-cell for
GSM 850, 900, 1800, and 1900.
The general principles and messages required for BSS maintenance
are described in: Nortel GSM BSS Fault Management - Maintenance
Principles (411-9001-039)
The network maintenance is based on the graphical supervision of the
network at the OMC-R.
It is also based on the identification and the replacement of faulty items of
equipment, 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 replacement

procedures given in the manuals that describe the on-site procedures
When a faulty item of equipment sends an alarm to the OMC-R, this

alarm is identified by a fault number. This manual gives the procedures
associated with the various fault numbers.
1.2 The types of spontaneous messages

1.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 of
capacity, triggering no defense actions on the part of the BSC. If there
are any defense actions, they are local and controlled by the BTS (fault
number 1067).

411-9001-104 18.05 2 February 2010
24 Chapter 1 How to use this manual
spontaneous messages indicating a transient event for warning (fault

number 1060)
spontaneous messages indicating the arrival of state changes on an

equipment (fault number 1058)
1.2.2 Events detected by the BSC

Spontaneous messages are sent by the BSC giving information on the
state of relationships 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 three main paragraphs explaining the fault
number treatment
1.3.1 Header of the sheet

The 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 the
service.
Troubleshooting
This paragraph gives the procedures to be followed to repair the fault
and return to the operational conditions.
Preliminary checks

411-9001-104 18.05 2 February 2010
1.3 Description of a fault number sheet 25
These checks are used to ensure that the fault is confirmed and
that the messages identifying a faulty element are in the OMC-R
logs 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 the
exchanged element into correct operation.
Additional checks
This paragraph shows how to check that the fault has been
cleared.

411-9001-104 18.05 2 February 2010
26 Chapter 1 How to use this manual

411-9001-104 18.05 2 February 2010
27
Chapter 2 S2000 H/L BTS fault

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

Fault number:
1052
GSM entity downloading failure
Type
communicationsAlarm/processingErrorAlarm/ equipmentAlarm
FAULT ANALYSIS
This message identifies the impacted element but not the faulty element. It
indicates a software downloading error concerning a transceiverEquipment
object or a btsSiteManager object.
All the software downloading attempts are indicated, as well as the source
of their failure.
Table 1 "Fault number 1052 sources" (page 28) indicates all the sources
of the fault number 1052 for the S2000 H/L BTS. For more information
on each source, see the indicated paragraph to know the corrective
maintenance procedure associated with this source.

411-9001-104 18.05 2 February 2010
28 Chapter 2 S2000 H/L BTS fault numbers

Table 1
Fault number 1052 sources
Source
No.
Source wording
Paragraph
No response to status
request
2.2.1 Source 0: No response to status

request (page 36)
Bad hardware reference

or manufacturer ID
2.2.2 Source 1: Bad hardware reference

or manufacturer ID (page 38)
SUP stop receipt
2.2.3 Source 2: SUP stop receipt

(page 40)
No change to one of
BOOT after reset
2.2.4 Source 3: No change to one of

BOOT after reset (page 43)
This entity is engaged

in another downloading
2.2.5 Source 4: This entity is engaged

in another downloadingSource 8:
Wrong software reference on a non
downloadable TEI (page 45)
Software not compatible

with hardware
2.2.6 Source 5: Software not compatible

with hardware (page 47)
File access error
2.2.7 Source 6: File access error

(page 51)
Repetitive errors
(NACK, timeout, ...)
while downloading a file
2.2.8 Source 7:Repetitive errors (NACK,

timeout, ...) while downloading a
file (page 54)
Wrong software
reference on a non
downloadable TEI
2.2.5 Source 4: This entity is engaged

in another downloadingSource 8:
downloadable TEI (page 45)
No response to
download message
2.2.9 Source 9: No response to download

message (page 55)
14
CSM load container

negative acknowle
dgement
2.2.10 Source 14: Received CSM LOAD

CONTAINER NAK (page 57)
15
File to download empty
2.2.11 Source 15: File to download

empty (page 59)
16
File to download
unavailable

unavailable (page 62)
17
Buffer allocation failure
2.2.13 Source 17: Buffer allocation

failure (page 62)
18
Bad sending buffer

size value
2.2.14 Source 18: Bad sending buffer

size value (page 65)
19
Failure during OMU

switchover
2.2.15 Source 19: Failure during OMU

switchover (page 67)

411-9001-104 18.05 2 February 2010
Table 1
Fault number 1052 sources (contd.)
Source
No.
Source wording
Paragraph
20
Bad TEI sent by BTS

in the CSM software
update report message
2.2.16 Source 20: Bad TEI sent by

BTS in the CSM software update report
message (page 69)
21
CSM software update

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

update report with the cause - unknown
TEI - (page 72)
22
CSM software update

equipment failure

update report with the cause - equipment
failure - (page 74)
23
CSM software update

"downloading failure"
2.2.19 Source 23: CSM software update

report with the cause - downloading
failure - (page 76)
24
CSM software update

"not able to perform"

update report with the cause - not able
to perform- (page 79)
25
CSM software update

"wrong soft ref"

report with the cause - wrong software
reference - (page 81)
26
CSM software update

"wrong config ref"

report with the cause - wrong configuration
reference - (page 83)
27
CSM software update

"restart request"

update report with the cause - restart
request - (page 86)
28
CSM software update

"data inconsistency"

update report with the cause - data
inconsistency - (page 88)
29
CSM software update

"message out of
sequence"

report with the cause - message out
of sequence - (page 90)
30
CSM software update

"background not
available"

report with the cause - background not
available - (page 93)
31
CSM software update

"incompatible RM
version"

report with the cause - incompatible
RM version - (page 95)

411-9001-104 18.05 2 February 2010
Table 1
Source
No.
Source wording
Paragraph
32
CSM software update

"downloading in
progress"

report with the cause - downloading
in progress - (page 97)
33
Bad report sent by BTS

in the CSM software
2.2.29 Source 33: Bad report sent by

BTS in the CSM software update report
message (page 100)
34
No BTS response on
CSM software update
init/control message
2.2.30 Source 34: No BTS response

on CSM software update init-control
message (page 102)
35
Nack received on the

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

abort requested by operator (page 104)
36
Bad report sent by BTS

in the CSM software
update abort message
2.2.32 Source 36: Bad report sent by

BTS in the CSM software update abort
message (page 107)
37
No BTS response on
CSM software update
abort message

on CSM software update abort
message (page 109)
38
Flash activate nack with

the cause "unknown
TEI"
2.2.34 Source 38: Flash activate

nack with the cause - unknown TEI
- (page 111)
39

the cause "equipment
failure"

nack with the cause - equipment
failure - (page 113)
40

the cause "downloading
failure"

nack with the cause - downloading
41
Flash activate nack

with the cause "not able
to perform"

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

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

with the cause - data inconsistency
- (page 122)
44
Flash activate nack

with the cause "wrong
soft ref"

nack with the cause - wrong soft ref
- (page 125)

411-9001-104 18.05 2 February 2010
Table 1
Source
No.
Source wording
Paragraph
45
Flash activate nack

config ref"

nack with the cause - wrong config
ref - (page 127)
46
CSM downloading start

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

start nack with the cause - unknown
TEI - (page 129)
47

nack with the cause
"equipment failure"

start nack with the cause - equipment
48

nack with the cause

start nack with the cause - downloading
49
CSM downloading
start nack with the
cause "message out
of sequence"

start nack with the cause - message out
50

nack with the cause
"wrong soft ref"

start nack with the cause - wrong soft
ref - (page 138)
51

nack with the cause
"wrong config ref"

start nack with the cause - wrong
config ref - (page 141)
52

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

nack with a bad cause (page 143)
53
No BTS response on
message

on CSM downloading start message
(page 145)
54
CSM downloading end

nack with the cause
"unknown TEI"

end nack with the cause - unknown
TEI - (page 147)
55
CSM downloading end

nack with the cause
"equipment failure"

end nack with the cause - equipment
56
CSM downloading end

nack with the cause

end nack with the cause - downloading
57
CSM downloading end

nack with the cause
"value out of range"

end nack with the cause - value out
of range - (page 154)

411-9001-104 18.05 2 February 2010
Table 1
Source
No.
Source wording
Paragraph
58
CSM downloading end

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

59
no BTS response on
CSM downloading end
message

on CSM downloading end message
(page 159)
60
CSM load init nack with

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

the cause - equipment failure - (page 161)
61

the cause "downloading
failure"
2.2.57 Source 61: CSM load init

62

the cause "message
CSM
init nack
out ofload
sequence"
file ref"

nack with the cause - message out of
2.2.59 Source
63: CSM
load165)
init nack with
sequence
- (page
the cause - wrong file ref - (page 168)
64
CSM load init nack

with the cause "window
size not allow"

nack with the cause - window size not
allowed - (page 170)
65
CSM load init nack

format error"

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

a bad cause
2.2.62 Source 66: CSM load init nack

with a bad cause (page 175)
67
No BTS response on
CSM load init message
2.2.63 Source 67: No BTS response on

CSM load init message (page 177)
68
CSM load data

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

69
CSM load data

nack with the cause

70
CSM load data

nack with the cause
"message out of
sequence"

sequence - (page 184)
71
CSM load data nack

format error"

nack with the cause - data format
error - (page 186)
63

411-9001-104 18.05 2 February 2010
Table 1
Source
No.
Source wording
Paragraph
72
CSM load data nack

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

with the cause - window overflow
- (page 188)
73
CSM load data nack

inconsistency"

- (page 190)
74
CSM load data nack

with the cause "block
not received"

with the cause - block not received
- (page 193)
75
CSM load data nack

with the cause "bad
block tag"

nack with the cause - bad block tag
- (page 195)
76
CSM load data

nack with the cause
"checksum error"

nack with the cause - checksum
error - (page 197)
77
CSM load data nack

with a bad cause

78
Unexpected CSM load

data ack
2.2.74 Source 78: Unexpected CSM

load data ack (page 202)
79
No BTS response
on CSM load data
message

CSM load data message (page 204)
80
CSM load end nack

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

81
CSM load end nack

with the cause

82
CSM load end nack

with the cause "value
out of range"

nack with the cause - value out of
range - (page 211)
83
CSM load end nack

with the cause
"message out of
sequence"

sequence - (page 213)
84
CSM load end nack

format error"

error - (page 215)

411-9001-104 18.05 2 February 2010
Table 1
Source
No.
Source wording
Paragraph
85
CSM load end nack

file ref"

nack with the cause - wrong file ref
- (page 217)
86
CSM load end nack

inconsistency"
2.2.82 Source 86: CSM load end nack

- (page 220)
87
CSM load end nack

with the cause
"checksum error"

error - (page 222)
88
CSM load end nack

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

89
No BTS response on
CSM load end message

CSM load end message (page 226)
90
Bad report sent by

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

during an internal update (page 229)
91
CSM load init nack

with the cause "file
already open"

the cause - file already open - (page 231)
92
CSM load init nack

with the cause "invalid
mode"

the cause - invalid mode - (page 233)
93

the cause "file cannot
be unloaded"

nack with the cause - file cannot be
unloaded - (page 235)
94

the cause "flash flag
cannot access"
2.2.90 Source 94: CSM load init nack

with the cause - flash flag cannot
access - (page 238)
95
CSM load data nack

with the cause "file
cannot be unloaded"

nack with the cause - file cannot be
96
CSM load data nack

flag cannot access"

nack with the cause - flash flag cannot
access - (page 242)
97
CSM load data nack

with the cause "boot
cannot be unloaded"

nack with the cause - boot cannot be

411-9001-104 18.05 2 February 2010
Table 1
Source
No.
Source wording
Paragraph
98
CSM load data nack

decod error"

nack with the cause - data decode
error - (page 247)
99
CSM load data nack

with the cause "table
cannot access"

nack with the cause - table cannot
access - (page 249)
100
CSM load data nack

with the cause "ram
mapping error"

nack with the cause - RAM mapping
error - (page 251)
101
CSM load data nack

access error"

nack with the cause - flash access
error - (page 254)
102
CSM load data nack

ram error"

nack with the cause - flash RAM
error - (page 256)
103
CSM load data nack

erase error"

nack with the cause - flash erase
error - (page 258)
104
CSM load data nack

with the cause "internal
abort"

nack with the cause - internal abort
- (page 260)
REACTION OF THE SYSTEM

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

The site is not downloaded.
CAUTION
Service interruption
The service is reduced or lost depending on the
configuration.
Case of the transceiverEquipment object

The TRX is not downloaded, one TDMA is not configured.
411-9001-104 18.05 2 February 2010
ATTENTION
The 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 ANALYSIS
This source indicates that the BTS has not replied to the status request.
TROUBLESHOOTING
Step
Action
Preliminary checks
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.
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.

"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 411-9001-105 (Nortel
GSM BSS Fault Clearing - Advanced Maintenance
Procedures) ).
If a lapdLink object is "disabled-failed", the BSC is
concerned. Look for alarms concerning the BSC .

"disabled-failed", the site is not operational.

411-9001-104 18.05 2 February 2010
If the fault number 1052 is the only alarm, process the

alarm.
Otherwise, if there are other alarms, set the
btsSiteManager object to "locked" and then to
"unlocked" to confirm the problem.
If the fault number 1052 is still present, treat it (see

above).
If other fault numbers are present, such as fault

number 1054, process them (concerning fault number
1054 (loss of layer 2), refer to 411-9001-105 (Nortel
Procedures) ).

"disabled", the site is not operational. Do not process the
alarm and do not clear it. Wait for a state change of the
btsSiteManager object.
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.

"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 the btsSiteManager object is "disabled-failed", the site
is not operational. process the alarm(s) concerning the
Procedures) ).
concerned. Look for alarms concerning the BSC.

"disabled-failed", the TRX is not operational.

411-9001-104 18.05 2 February 2010

alarm. Go to step 4.
transceiverEquipment object to "locked" and then
to "unlocked" to confirm the problem.

above).

Procedures)).
If the operationalState of the transceiverEquipment object

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

--End--
2.2.2 Source 1: Bad hardware reference or manufacturer ID

(1) Bad hardware reference or manufacturer ID S2000 H/L
Source:
BTS model:
FAULT ANALYSIS
This source indicates that the first downloading attempt failed.
The alarm indicates that the "hardwareRef" parameter, obtained by
performing the "Display" command on the btsSiteManager object and
the transceiverEquipment object, is not in accordance with the PROM
numbers on the boards.
TROUBLESHOOTING
Preliminary checks
Step
Action


411-9001-104 18.05 2 February 2010


Clear the alarm.

number concerning PCMs (see Nortel GSM BSS Fault
Clearing - Advanced Maintenance (411-9001-105) ).
concerned. Look for alarms about the BSC.

If the fault number 1052 is the only alarm, treat the alarm.
Go to step 4.
btsSiteManager object to "locked" then to "unlocked" to
confirm the problem.

above).
If other fault numbers are present too, such as fault

number 1054, treat them (concerning fault number
1054 (loss of layer 2), see Nortel GSM BSS Fault

"disabled", the site is not operational. Do not treat the
Check the state of the DRX by performing the "Display all"


"enabled", the DRX is operational.
Clear the alarm.

"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

concerning cells.
is not operational. Treat the alarm(s) concerning the
If a pcmCicruit object is "disabled-failed", look for a fault

"disabled-failed", the DRX is not operational.
Go to step 6.

above).


is "disabled" the DRX is not operational. Do not treat the
Case of the btsSiteManager object for the S2000 H/L BTS
Set the value of the "hardwareRef" parameter to "0".
Case of the transceiverEquipment object for the S2000 H/L BTS
Modify the value of the "hardwareRef" parameter: set it to "0".

--End--

Source:
(2) SUP stop receipt
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
FAULT ANALYSIS
This source indicates that a supervision stop has been received.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010

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

(3) No change to one of BOOT after reset
S2000 H/L
Source:
BTS model:
TROUBLESHOOTING
Preliminary checks
Step
Action



"enabled", the site is operational. Clear the alarm and go to
step 6.


"disabled-failed", and if there are other alarms which could
impact the operation of the site, lock the btsSiteManager
object. Then unlock it.
If the alarm with the fault number 1052 and the source 3
is still present, treat the alarm. Go to step 4.
number 1054, treat them. Concerning fault number 1054
(loss of layer 2), see Nortel GSM BSS Fault Clearing Advanced Maintenance (411-9001-105) .


411-9001-104 18.05 2 February 2010
3
Check the state of the DRX by performing the "Display all"


Clear the alarm.

concerning cells.

Go to step 4.
transceiverEquipment object to "locked" then to

above).


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

"unlocked" to restart the downloading.

411-9001-104 18.05 2 February 2010
If the alarm persists, check if the source 1 appears.

If the source 1 appears, treat it. See Paragraph 2.2.2
Source 1: Bad hardware reference or manufacturer ID
(page 38).
If the source 1 does not appear, go to step 5.
If the alarm has disappeared, the downloading has restarted.

Go to step 6.
Replace the following items:
the base or extension module of the S2000H "EP" BTS:

see Nortel GSM BTS S2000H/S2000L Troubleshooting
(411-9001-049).
the main module of the S2000H "FP" BTS: see Nortel GSM
BTS S2000H/S2000L Troubleshooting (411-9001-049).
the base or extension module of the S2000L "EP" BTS:

(411-9001-049).
the main module of the S2000L "FP" BTS: see Nortel GSM
BTS S2000H/S2000L Troubleshooting (411-9001-049).
If the alarm has disappeared, go to step 6. Otherwise, call the

manufacturer.
6

--End--
2.2.5 Source 4: This entity is engaged in another downloading

Source 8: Wrong software reference on a non downloadable TEI
(4) This entity is engaged in another downloading
(8) Wrong software reference on a non downloadable TEI
S2000 H/L
Source:
Source:
BTS model:
TROUBLESHOOTING
Preliminary checks
Step
Action


411-9001-104 18.05 2 February 2010


step 4.


or 8 is still present, treat the alarm. Call the manufacturer.
Otherwise, if there are other alarms, such as fault number
1054, treat them (concerning fault number 1054 (loss of
layer 2), see Nortel GSM BSS Fault Clearing - Advanced
Maintenance (411-9001-105) ).



Clear the alarm.

concerning cells.

411-9001-104 18.05 2 February 2010


If the fault number 1052 is the only alarm, treat it. Call the
manufacturer.

above).



--End--
2.2.6 Source 5: Software not compatible with hardware

Source:
BTS model:
(5) Software not compatible with hardware

S2000 H/L
FAULT ANALYSIS
This alarm indicates an inconsistency between the hardware items of
equipment and the software (EFT) downloaded from the OMC-R.
TROUBLESHOOTING
Preliminary checks
Step
Action

411-9001-104 18.05 2 February 2010

If the transceiverEquipment object is concerned, check
whether the "DRX automatic downloading" is activated or not:
If the "DRX automatic downloading" is activated, go to
step 8.
If the "DRX automatic downloading" is not activated, go
to step 3.


step 8.


"disabled-failed", and if there is an alarm with the fault
number 1054, followed by alarms with fault numbers 1051,
1052, 1053, lock the btsSiteManager object. Then unlock it.
Otherwise, see the fault number 1054 (loss of layer
2) (see Nortel GSM BSS Fault Clearing - Advanced
Maintenance (411-9001-105) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010

concerning cells.

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

above).


Check that the value of the "hardwareRef" parameter is

consistent with the PROM numbers on the boards, by performing
a "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 one
indicated in the notification
set the btsSiteManager object to "unlocked"
If the value of the "hardwareRef" parameter is correct, go to

step 5.
Check if the EFT is correct by checking the value of the

"swVersionRunning" parameter and this by performing a

411-9001-104 18.05 2 February 2010
"Display" command on the software object associated with the

bsc, btsSiteManager and transceiverEquipment objects.
If it 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 11.
If it is not the case, go to step 6.
Set the object concerned to "locked".
Download the good EFT on the item of equipment according to

the following values.
Field
Meaning
Value
XXX
Type of software
BCF: SBC
TRX: CDR
ab
Version number
[08 .. 32]
Sub-version number
BCF: [A .. H]
TRX: [A .. H]
Edition number
BCF: [1 .. 8]
TRX: [1 .. 8]
ef
Revision factor
BCF: [01 .. 32]

TRX: [01 .. 32]
If the name of the EFT is correct, call the manufacturer.

Otherwise, modify the value and set the object concerned to
"unlocked".
If the "Automatic downloading" is activated, the OMC-R starts to

perform the downloading just after it received fault number 1052
cause 5:.
a The OMC-R reads the BTS hardware reference quoted in the
fault number.
b The OMC-R deduces the name of the EFT to be downloaded
from a correspondence table.
c The OMC-R searches for the EFT in its database:
If it does not find one, the OMC-R goes to step 9.

If it finds one and only one, the OMC-R goes to step 10.
If it finds more than one, it lets the operator choose. A
critical alarm with fault number 30076 is emitted to report
that the automatic downloading failed (see Nortel GSM
OMC-R Troubleshooting (411-9001-032)).

411-9001-104 18.05 2 February 2010
The OMC-R searches for the delivery name of the BTS the DRX
belongs to. Then, for all BTS with the same delivery name under
the same BSC, the OMC-R searches for the right EFT.
If it finds one and only one, it selects it. Then it goes to step
10.
If it finds more than one, it lets the operator choose. A critical

alarm with fault number 30076 is emitted to report that the
automatic downloading failed (see Nortel GSM OMC-R
Troubleshooting (411-9001-032)).
If it does not find one, the OMC-R searches for an EFT

suitable to all the BTS with the same delivery name in all the
BSC.
If it finds one and only one, it selects it. Then it goes to
step 10.
If it finds more than one, or none, it lets the operator
choose. A critical alarm with fault number 30076 is
emitted to report that the automatic downloading
failed (see Nortel GSM OMC-R Troubleshooting
(411-9001-032)).
10
The OMC-R starts to download the selected EFT:

a If necessary, it downloads the selected EFT to the BSC disc.
b It locks the related transceiverEquipment object instance
c It sets the sWVersionNew parameter of the new
transceiverEquipment software object with the new EFT
name.
d It activates the new version.
e It unlocks the related transceiverEquipment object instance.
f
11
As a consequence, the fault number 1052 with cause 5 is

automatically cleared.

--End--

Source:
BTS model:
(6) File access error

S2000 H/L
FAULT ANALYSIS
This source indicates that the first downloading attempt failed. The BSC
does not find the software files in one partition of its hard disk.
411-9001-104 18.05 2 February 2010
TROUBLESHOOTING
Preliminary checks
Step
Action



step 5.


is still present, treat the alarm, go to step 4.
Maintenance (411-9001-105) ).




411-9001-104 18.05 2 February 2010
Clear the alarm.


concerning cells.

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

above).


is "disabled" the site is not operational. Do not treat the
Download the software from the MD at the OMC-R to the BSC

disk partition.
To download a BCF software, see the downloading

procedure (see in Nortel GSM BSS Configuration - Operating
Procedures (411-9001-034).).
To download a DRX software, see the downloading

procedure (see in Nortel GSM BSS Configuration - Operating
Procedures (411-9001-034).).

411-9001-104 18.05 2 February 2010
Then lock the object concerned (either btsSiteManager or

transceiverEquipment object).
Unlock the object concerned.


--End--
2.2.8 Source 7:
Repetitive errors (NACK, timeout, ...) while downloading a file
Fault number 1052: GSM entity downloading failure
Source:
(7) Repetitive errors (NACK, timeout, ...) while downloading

a file
BTS model:
S2000 H/L
FAULT ANALYSIS
This source indicates that the download failed after repetitive downloading
errors. The probable cause could be corrupted corresponding active BTS
software in the BSC.
TROUBLESHOOTING
Preliminary checks
Step
Action
Lock the btsSiteManager.
Cleanup the corresponding BTS software from the BSC.
Activate the software.
Download the software from the MD at the OMC-R to the

BSC disk partition.
Unlock the btsSiteManager.

--End--

411-9001-104 18.05 2 February 2010
2.2.9 Source 9: No response to download message

Source:
(9) No response to download message
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that the BTS has not replied to a download
message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010

Procedures)).


--End--
2.2.10 Source 14: Received CSM LOAD CONTAINER NAK

Source:
(14) Received CSM LOAD CONTAINER NAK
BTS model:
S2000H/L
FAULT ANALYSIS
This message is received after attempts to download the software are
failed by the BSC. This source is because the Load file of TRX/BCF
residing in the BSC is corrupt.
TROUBLESHOOTING
Step
Action
Preliminary checks
Check the notification and identify the object concerned.

Check the state of the site by performing the Display all


step 6.


411-9001-104 18.05 2 February 2010

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

object, and then unlock it.
If the alarm with the fault number 1052 and the source 6 is
present, process the alarm. Go to step 4.
if there are other alarms, such as fault number 1054, process

them (concerning fault number 1054 (loss of layer 2), see
411-9001-105 (Nortel GSM BSS Fault Clearing - Advanced
Maintenance Procedures)



Clear the alarm.

Look for a parent object that is not operational.
concerning cells.
Procedures)).


411-9001-104 18.05 2 February 2010


above).

Procedures)).

Re-download the software from the MD at the OMC--R to the

BSC disk partition:
To download a BCF software, refer to the downloading

procedure.
To download a TRX software, refer to the downloading

procedure.
Lock the object concerned (either btsSiteManager or



--End--
2.2.11 Source 15: File to download empty

Source:
(15) File to download empty
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that the file to download is empty.

411-9001-104 18.05 2 February 2010
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
2.2.12 Source 16: File to download unavailable

Source:
(16) File to download unavailable
BTS model:
S2000 H/L
FAULT ANALYSIS
This source indicates that the downloading attempt has failed because
the file to be downloaded cannot be found in the catalog file (either
because the catalog file itself is not valid, or the name of the file has been
improperly copied in the BTS or BSC software).
TROUBLESHOOTING
Step
Action
Preliminary checks
Cleanup the load from BTS partition of active BSC hard disk.
disk partition:

procedure in Nortel GSM BSS Configuration - Operating
Procedures (411-9001-034)..
To download TRX software, see the downloading procedure

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


If the alarm persists, go to step 2.
Perform the following action:
For the BSC 3000, call the manufacturer.

--End--
2.2.13 Source 17: Buffer allocation failure

Source:
(17) Buffer allocation failure
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
FAULT ANALYSIS
This source indicates a buffer allocation failure.
TROUBLESHOOTING
Procedure 1
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).


411-9001-104 18.05 2 February 2010

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
4

--End--
2.2.14 Source 18: Bad sending buffer size value

Source:
(18) Bad sending buffer size value
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a bad sending of the buffer size value.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010


above).

Procedures)).


--End--
2.2.15 Source 19: Failure during OMU switchover

Source:
(19) Failure during OMU switchover
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a failure during the OMU switchover.
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-104 18.05 2 February 2010
Clear the alarm.


Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.16 Source 20: Bad TEI sent by BTS in the CSM software update
report message
Source:
(20) Bad TEI sent by BTS in the CSM software update report
message
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
FAULT ANALYSIS
This source indicates a bad TEI sent by the BTS in the CSM software
update report message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010

--End--
2.2.17 Source 21: CSM software update report with the cause unknown TEI Fault number 1052 : GSM entity downloading failure
Source:
(21) CSM software update report with the cause "unknown TEI"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM software update report with the cause
"unknown TEI".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010


above).

Procedures)).


--End--
2.2.18 Source 22: CSM software update report with the cause equipment failure Fault number 1052 : GSM entity downloading failure
Source:
(22) CSM software update report with the cause "equipment

failure"
BTS model:
S2000H/L
FAULT ANALYSIS
"equipment failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.19 Source 23: CSM software update report with the cause downloading failure Fault number 1052 : GSM entity downloading failure
Source:
(23) CSM software update report with the cause "downloading

failure"
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
FAULT ANALYSIS
"downloading failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010

--End--
2.2.20 Source 24: CSM software update report with the cause - not able
to performFault number 1052 : GSM entity downloading failure
Source:
(24) CSM software update report with the cause "not able to
perform"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM software update report with the cause "not
able to perform".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010


above).

Procedures)).


--End--
software reference Fault number 1052 : GSM entity downloading failure
Source:
(25) CSM software update report with the cause "wrong software
reference"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM software update report with the cause "wrong
software reference".
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
configuration reference Fault number 1052 : GSM entity downloading failure
Source:
(26) CSM software update report with the cause "wrong

configuration reference"
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
FAULT ANALYSIS
configuration reference".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010

--End--
2.2.23 Source 27: CSM software update report with the cause - restart
request Fault number 1052 : GSM entity downloading failure
Source:
(27) CSM software update report with the cause "restart request"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM software update report with the cause "restart
request".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010


above).

Procedures)).


--End--
inconsistency Fault number 1052 : GSM entity downloading failure
Source:
(28) CSM software update report with the cause "data

inconsistency"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM software update report with the cause "data
inconsistency".
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.25 Source 29: CSM software update report with the cause message out of sequence Fault number 1052 : GSM entity downloading failure
Source:
(29) CSM software update report with the cause "message out
of sequence"
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
FAULT ANALYSIS
"message out of sequence".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010

--End--
2.2.26 Source 30: CSM software update report with the cause background not available Fault number 1052 : GSM entity downloading failure
Source:
(30) CSM software update report with the cause "background

not available"
BTS model:
S2000H/L
FAULT ANALYSIS
"background not available".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010


above).

Procedures)).


--End--
2.2.27 Source 31: CSM software update report with the cause incompatible RM version Fault number 1052 : GSM entity downloading failure
Source:
(31) CSM software update report with the cause "incompatible

RM version"
BTS model:
S2000H/L
FAULT ANALYSIS
"incompatible RM version".
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.28 Source 32: CSM software update report with the cause downloading in progress Fault number 1052 : GSM entity downloading failure
Source:
(32) CSM software update report with the cause "downloading in

progress"
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
FAULT ANALYSIS
"downloading in progress".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
100

--End--
2.2.29 Source 33: Bad report sent by BTS in the CSM software update
report message
Source:
(33) Bad report sent by BTS in the CSM software update report
message
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a bad report sent by the BTS in the CSM software
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
101

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010
102


above).

Procedures)).


--End--
2.2.30 Source 34: No BTS response on CSM software update

init-control message
Source:
(34) No BTS response on CSM software update init/control

message
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates no BTS response on the CSM software update
init/control message.
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
103

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
104

concerning cells.
Procedures) ).


above).

Procedures)).


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

Source:
(35) Nack received on the abort requested by operator
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that a Nack has been received on the abort
requested by operator.

411-9001-104 18.05 2 February 2010
105
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
106


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
107
abort message
Source:
(36) Bad report sent by BTS in the CSM software update abort
message
BTS model:
S2000H/L
FAULT ANALYSIS
update abort message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
108

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
109

Procedures)).


--End--

message
Source:
(37) No BTS response on CSM software update abort message
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates no BTS response on CSM software update abort
message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
110

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
111


above).

Procedures)).


--End--
2.2.34 Source 38: Flash activate nack with the cause - unknown TEI Fault number 1052 : GSM entity downloading failure
Source:
(38) Flash activate nack with the cause "unknown TEI"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a flash activate nack with the cause unknown TEI.
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
112

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
113

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.35 Source 39: Flash activate nack with the cause - equipment
failure Fault number 1052 : GSM entity downloading failure
Source:
(39) Flash activate nack with the cause "equipment failure"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "equipment
failure".
411-9001-104 18.05 2 February 2010
114
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
115


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
116
2.2.36 Source 40: Flash activate nack with the cause - downloading
Source:
(40) Flash activate nack with the cause "downloading failure"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "downloading
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
117

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
118

Procedures)).


--End--
2.2.37 Source 41: Flash activate nack with the cause - not able to
perform Fault number 1052 : GSM entity downloading failure
Source:
(41) Flash activate nack with the cause "not able to perform"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "not able to
perform".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
119

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
120


above).

Procedures)).


--End--
2.2.38 Source 42: Flash activate nack with the cause - flash
Source:
(42) Flash activate nack with the cause "flash inconsistency"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a Flash activate nack with the cause "flash
inconsistency".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
121

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
122

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.39 Source 43: Flash activate nack with the cause - data
Source:
(43) Flash activate nack with the cause "data inconsistency"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a Flash activate nack with the cause "data
inconsistency".
411-9001-104 18.05 2 February 2010
123
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
124


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
125
2.2.40 Source 44: Flash activate nack with the cause - wrong soft ref Fault number 1052 : GSM entity downloading failure
Source:
(44) Flash activate nack with the cause "wrong soft ref"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "wrong soft ref".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
126

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
127

Procedures)).


--End--
2.2.41 Source 45: Flash activate nack with the cause - wrong config
ref Fault number 1052 : GSM entity downloading failure
Source:
(45) Flash activate nack with the cause "wrong config ref"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "wrong config
ref".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
128

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
129


above).

Procedures)).


--End--
2.2.42 Source 46: CSM downloading start nack with the cause unknown TEI Fault number 1052 : GSM entity downloading failure
Source:
(46) CSM downloading start nack with the cause "unknown TEI"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM downloading start nack with the cause
"unknown TEI".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
130

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
131

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.43 Source 47: CSM downloading start nack with the cause equipment failure Fault number 1052 : GSM entity downloading failure
Source:
(47) CSM downloading start nack with the cause "equipment

failure"
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
132
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
133
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
134

--End--
2.2.44 Source 48: CSM downloading start nack with the cause downloading failure Fault number 1052 : GSM entity downloading failure
Source:
(48) CSM downloading start nack with the cause "downloading

failure"
BTS model:
S2000H/L
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
135

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010
136


above).

Procedures)).


--End--
2.2.45 Source 49: CSM downloading start nack with the cause message out of sequence Fault number 1052 : GSM entity downloading failure
Source:
(49) CSM downloading start nack with the cause "message out
of sequence"
BTS model:
S2000H/L
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
137

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
138

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.46 Source 50: CSM downloading start nack with the cause - wrong
soft ref Fault number 1052 : GSM entity downloading failure
Source:
(50) CSM downloading start nack with the cause "wrong soft ref"
BTS model:
S2000H/L
FAULT ANALYSIS
"wrong soft ref".
411-9001-104 18.05 2 February 2010
139
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
140


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
141
config ref Fault number 1052 : GSM entity downloading failure
Source:
(51) CSM downloading start nack with the cause "wrong config
ref"
BTS model:
S2000H/L
FAULT ANALYSIS
"wrong config ref".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
142

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
143

Procedures)).


--End--
2.2.48 Source 52: CSM downloading start nack with a bad cause
Source:
(52) CSM downloading start nack with a bad cause
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM downloading start nack with a bad cause.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
144

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
145


above).

Procedures)).


--End--
2.2.49 Source 53: No BTS response on CSM downloading start

message
Source:
(53) No BTS response on CSM downloading start message
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates no BTS response on CSM downloading start
message.
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
146

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
147

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.50 Source 54: CSM downloading end nack with the cause unknown TEI Fault number 1052 : GSM entity downloading failure
Source:
(54) CSM downloading end nack with the cause "unknown TEI"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM downloading end nack with the cause
"unknown TEI".
411-9001-104 18.05 2 February 2010
148
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
149


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
150
2.2.51 Source 55: CSM downloading end nack with the cause equipment failure Fault number 1052 : GSM entity downloading failure
Source:
(55) CSM downloading end nack with the cause "equipment

failure"
BTS model:
S2000H/L
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
151

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
152

Procedures)).


--End--
2.2.52 Source 56: CSM downloading end nack with the cause downloading failure Fault number 1052 : GSM entity downloading failure
Source:
(56) CSM downloading end nack with the cause "downloading

failure"
BTS model:
S2000H/L
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
153

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
154


above).

Procedures)).


--End--
2.2.53 Source 57: CSM downloading end nack with the cause - value
out of range Fault number 1052 : GSM entity downloading failure
Source:
(57) CSM downloading end nack with the cause "value out of
range"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM downloading end nack with the cause "value
out of range".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
155


Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
156

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.54 Source 58: CSM downloading end nack with a bad cause
Source:
(58) CSM downloading end nack with a bad cause
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM downloading end nack with a bad cause.

411-9001-104 18.05 2 February 2010
157
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
158


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
159
2.2.55 Source 59: No BTS response on CSM downloading end message

Source:
(59) No BTS response on CSM downloading end message
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates no BTS response on CSM downloading end
message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
160

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
161

Procedures)).


--End--
2.2.56 Source 60: CSM load init nack with the cause - equipment failure
Source:
(60) CSM load init nack with the cause "equipment failure"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "equipment
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
162

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
163


above).

Procedures)).


--End--
2.2.57 Source 61: CSM load init nack with the cause - downloading
Source:
(61) CSM load init nack with the cause "downloading failure"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "downloading
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
164

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
165

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
sequence Fault number 1052 : GSM entity downloading failure
Source:
(62) CSM load init nack with the cause "message out of
sequence"
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
166
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "message out of
sequence".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
167
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
168

--End--
2.2.59 Source 63: CSM load init nack with the cause - wrong file ref Fault number 1052 : GSM entity downloading failure
Source:
(63) CSM load init nack with the cause "wrong file ref"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "wrong file ref".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
169

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010
170


above).

Procedures)).


--End--
2.2.60 Source 64: CSM load init nack with the cause - window size not
allowed Fault number 1052 : GSM entity downloading failure
Source:
(64) CSM load init nack with the cause "window size not
allowed"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "window size
not allowed".
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
171

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
172

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.61 Source 65: CSM load init nack with the cause - data format error
Source:
(65) CSM load init nack with the cause "data format error"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "data format
error".
411-9001-104 18.05 2 February 2010
173
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
174


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
175
2.2.62 Source 66: CSM load init nack with a bad cause
Source:
(66) CSM load init nack with a bad cause
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load init nack with a bad cause.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
176

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
177

Procedures)).


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

Source:
(67) No BTS response on CSM load init message
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a No BTS response on CSM load init message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
178

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
179


above).

Procedures)).


--End--
2.2.64 Source 68: CSM load data nack with the cause - equipment
Source:
(68) CSM load data nack with the cause "equipment failure"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "equipment
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
180

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
181

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.65 Source 69: CSM load data nack with the cause - downloading
Source:
(69) CSM load data nack with the cause "downloading failure"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "downloading
failure".
411-9001-104 18.05 2 February 2010
182
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
183


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
184
Source:
(70) CSM load data nack with the cause "message out of
sequence"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "message out
of sequence".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
185

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
186

Procedures)).


--End--
2.2.67 Source 71: CSM load data nack with the cause - data format
error Fault number 1052 : GSM entity downloading failure
Source:
(71) CSM load data nack with the cause "data format error"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "data format
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
187

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
188


above).

Procedures)).


--End--
2.2.68 Source 72: CSM load data nack with the cause - window
overflow Fault number 1052 : GSM entity downloading failure
Source:
(72) CSM load data nack with the cause "window overflow"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "window
overflow".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
189

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
190

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.69 Source 73: CSM load data nack with the cause - data
Source:
(73) CSM load data nack with the cause "data inconsistency"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "data
inconsistency".
411-9001-104 18.05 2 February 2010
191
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
192


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
193
2.2.70 Source 74: CSM load data nack with the cause - block not
received Fault number 1052 : GSM entity downloading failure
Source:
(74) CSM load data nack with the cause "block not received"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "block not
received".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
194

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
195

Procedures)).


--End--
2.2.71 Source 75: CSM load data nack with the cause - bad block tag Fault number 1052 : GSM entity downloading failure
Source:
(75) CSM load data nack with the cause "bad block tag"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "bad block
tag".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
196

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
197


above).

Procedures)).


--End--
2.2.72 Source 76: CSM load data nack with the cause - checksum error
Source:
(76) CSM load data nack with the cause "checksum error"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "checksum
error".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
198

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
199

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.73 Source 77: CSM load data nack with a bad cause
Source:
(77) CSM load data nack with a bad cause
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM software update report with the cause CSM
load data nack with a bad cause.

411-9001-104 18.05 2 February 2010
200
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
201


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
202
2.2.74 Source 78: Unexpected CSM load data ack

Source:
(78) Unexpected CSM load data ack
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates an unexpected CSM load data ack.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).


411-9001-104 18.05 2 February 2010
203

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-104 18.05 2 February 2010
204

Procedures)).

is "disabled", the TRX is not operational. Do not treat the

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

Source:
(79) No BTS response on CSM load data message
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates no BTS response on CSM load data message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

411-9001-104 18.05 2 February 2010
205


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010
206
Go to step 4.

above).

Procedures)).


--End--
2.2.76 Source 80: CSM load end nack with the cause - equipment
Source:
(80) CSM load end nack with the cause "equipment failure"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "equipment
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-104 18.05 2 February 2010
207
Clear the alarm.


Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.

411-9001-104 18.05 2 February 2010
208

Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
2.2.77 Source 81: CSM load end nack with the cause - downloading
Source:
(81) CSM load end nack with the cause "downloading failure"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "downloading
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks
411-9001-104 18.05 2 February 2010
209



Clear the alarm.

Procedures) ).


above).

Procedures) ).




411-9001-104 18.05 2 February 2010
210
Clear the alarm.


concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
211
2.2.78 Source 82: CSM load end nack with the cause - value out of
range Fault number 1052 : GSM entity downloading failure
Source:
(82) CSM load end nack with the cause "value out of range"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "value out of
range".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
212

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-104 18.05 2 February 2010
213

Procedures)).


--End--
Source:
(83) CSM load end nack with the cause "message out of
sequence"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "message out
of sequence".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
214

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
215

Go to step 4.

above).

Procedures)).


--End--
Source:
(84) CSM load end nack with the cause "data format error"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "data format
error".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
216

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
217

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
2.2.81 Source 85: CSM load end nack with the cause - wrong file ref Fault number 1052 : GSM entity downloading failure
Source:
(85) CSM load end nack with the cause "wrong file ref"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "wrong file ref".

411-9001-104 18.05 2 February 2010
218
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-104 18.05 2 February 2010
219

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
220
2.2.82 Source 86: CSM load end nack with the cause - data
Source:
(86) CSM load end nack with the cause "data inconsistency"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "data
inconsistency".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
221

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-104 18.05 2 February 2010
222

Procedures)).


--End--
2.2.83 Source 87: CSM load end nack with the cause - checksum error Fault number 1052 : GSM entity downloading failure
Source:
(87) CSM load end nack with the cause "checksum error"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "checksum
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
223

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
224

Go to step 4.

above).

Procedures)).


--End--
2.2.84 Source 88: CSM load end nack with a bad cause
Source:
(88) CSM load end nack with a bad cause
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load end nack with a bad cause.
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
225

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
226

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


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

Source:
(89) No BTS response on CSM load end message
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates no BTS response on CSM load end message.

411-9001-104 18.05 2 February 2010
227
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-104 18.05 2 February 2010
228

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
229
2.2.86 Source 90: Bad report sent by BTS during an internal update
Source:
(90) Bad report sent by BTS during an internal update
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a bad report sent by BTS during an internal update.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).


411-9001-104 18.05 2 February 2010
230

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-104 18.05 2 February 2010
231

Procedures)).


--End--
2.2.87 Source 91: CSM load init nack with the cause - file already open
Source:
(91) CSM load init nack with the cause "file already open"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "file already
open".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
232

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
233

Go to step 4.

above).

Procedures)).


--End--
2.2.88 Source 92: CSM load init nack with the cause - invalid mode Fault number 1052 : GSM entity downloading failure
Source:
(92) CSM load init nack with the cause "invalid mode"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "invalid mode".
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
234

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
235

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
2.2.89 Source 93: CSM load init nack with the cause - file cannot be
unloaded Fault number 1052 : GSM entity downloading failure
Source:
(93) CSM load init nack with the cause "file cannot be unloaded"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "file cannot be
unloaded".
411-9001-104 18.05 2 February 2010
236
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-104 18.05 2 February 2010
237

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
238
2.2.90 Source 94: CSM load init nack with the cause - flash flag cannot
access Fault number 1052 : GSM entity downloading failure
Source:
(94) CSM load init nack with the cause "flash flag cannot
access"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "flash flag
cannot access".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
239

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-104 18.05 2 February 2010
240

Procedures)).


--End--
2.2.91 Source 95: CSM load data nack with the cause - file cannot be
Source:
(95) CSM load data nack with the cause "file cannot be
unloaded"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "file cannot
be unloaded".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
241

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
242

Go to step 4.

above).

Procedures)).


--End--
2.2.92 Source 96: CSM load data nack with the cause - flash flag
cannot access Fault number 1052 : GSM entity downloading failure
Source:
(96) CSM load data nack with the cause "flash flag cannot
access"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "flash flag
cannot access".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
243


Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
244

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
Source:
(97) CSM load data nack with the cause "boot cannot be
unloaded"
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
245
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "boot cannot
be unloaded".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-104 18.05 2 February 2010
246
3


Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


411-9001-104 18.05 2 February 2010
247

--End--
2.2.94 Source 98: CSM load data nack with the cause - data decode
Source:
(98) CSM load data nack with the cause "data decode error"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "data decode
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
248

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

411-9001-104 18.05 2 February 2010
249

above).

Procedures)).


--End--
2.2.95 Source 99: CSM load data nack with the cause - table cannot
Source:
(99) CSM load data nack with the cause "table cannot access"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "table cannot
access".
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-104 18.05 2 February 2010
250
Clear the alarm.


Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.

411-9001-104 18.05 2 February 2010
251

Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
2.2.96 Source 100: CSM load data nack with the cause - RAM mapping
Source:
(100) CSM load data nack with the cause "RAM mapping error"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "RAM mapping
error".
TROUBLESHOOTING
Step
Action
Preliminary checks
411-9001-104 18.05 2 February 2010
252



Clear the alarm.

Procedures) ).


above).

Procedures) ).




411-9001-104 18.05 2 February 2010
253
Clear the alarm.


concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
254
2.2.97 Source 101: CSM load data nack with the cause - flash access
Source:
(101) CSM load data nack with the cause "flash access error"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "flash access
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
255

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-104 18.05 2 February 2010
256

Procedures)).


--End--
2.2.98 Source 102: CSM load data nack with the cause - flash RAM
Source:
(102) CSM load data nack with the cause "flash RAM error"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "flash RAM
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
257

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
258

Go to step 4.

above).

Procedures)).


--End--
2.2.99 Source 103: CSM load data nack with the cause - flash erase
Source:
(103) CSM load data nack with the cause "lash erase error"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "lash erase
error".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
259

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
260

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
2.2.100 Source 104: CSM load data nack with the cause - internal abort
Source:
(104) CSM load data nack with the cause "internal abort"
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "internal
abort".
411-9001-104 18.05 2 February 2010
261
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-104 18.05 2 February 2010
262

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
263
2.2.101 Source 105: CSM flash activate response with a bad cause
Source:
(105) CSM flash activate response with a bad cause
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM flash activate response with a bad cause.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
264

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-104 18.05 2 February 2010
265

Procedures)).


--End--
2.2.102 Source 106: DTM error during token allocation

Source:
(106) DTM error during token allocation
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a DTM error during token allocation.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
266

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
267

Go to step 4.

above).

Procedures)).


--End--
2.2.103 Source 107: CSM software update report with the cause: TRX
software incompatibility
Source:
(107) CSM software update report with the cause: TRX software
incompatibility
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a CSM software update report with the cause: TRX
software incompatibility.
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
268


Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
269

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
2.2.104 Source 108: Too many different deliveries in the cell group
Source:
(108) Too many different deliveries in the cell group
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates too many different deliveries in the cell group.

411-9001-104 18.05 2 February 2010
270
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-104 18.05 2 February 2010
271

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
272

Fault number:
1053
GSM entity configuration regression
Type
qualityOfServiceAlarm
FAULT ANALYSIS
The BSC detects a difference of the state between that known by the BSC
and that received from the BTS after a status request.
BSC defense
The BSC tries to restart the BTS (either the btsSiteManager object or the
transceiverEquipment object), to download it again and to reconfigure it.
CAUTION
For as long as the operationalState of the btsSiteManager
object is "disabled-failed", the site is lost.
ATTENTION
For as long as the operationalState of the transceiverEquipment object is
"disabled", the DRX and one TDMA are lost.
TROUBLESHOOTING
Preliminary checks
Step
Action
Look for a fault number 1067 concerning an item of equipment of

the object mentioned in the alarm (fault number 1053). If there is
not any alarm with the fault number 1067, go to step 2.
Check the state of the site by performing a "Display all"


411-9001-104 18.05 2 February 2010
273

step 4.


"disabled-failed", the site is not operational. Go to step 3.

Wait for the end of restart. Then look for the origin of the
problem by analyzing the notification log and looking at the
notifications with the fault number 1060 that indicate the source
of the BTS restart. Also check whether this problem often occurs
or not. If the problem persists, call the manufacturer.

--End--

Fault number:
1054
Loss of layer 2 (or no establishment) with remote GSM entity
Type
communicationsAlarm
This problem is associated with a PCM fault. see Nortel GSM BSS Fault
Clearing - Advanced Maintenance (411-9001-105) .

Fault number:
1055
Abis negative acknowledgement indication
Type
communicationsAlarm

411-9001-104 18.05 2 February 2010
274
FAULT ANALYSIS
The BSC sends a spontaneous message 1055 when it receives a
non-acknowledgement message (NACK) from a BTS after a configuration
message.
The following Table 2 "Fault number 1055 sources" (page 274) indicates
all the sources of the fault number 1055 for the S2000 H/L BTS. For more
information on each source, see the indicated paragraph to know the
corrective maintenance procedure associated with this source.
Table 2
Source
No.
Source wording
Paragraph
Equipment failure
Equipment unable to perform such test
2.5.2 Source 2: Equipment unable to

perform such test (page 278)
Invalid configuration
2.5.3 Source 3: Invalid configuration

(page 279)
Unknown test
Cell parameters inconsistency
Data inconsistency
2.5.6 Source 6: Data inconsistency

(page 282)
Value out of range
2.5.7 Source 7: Value out of range

(page 284)
TEI not present
Unknown Abis PCM_Time_Slot
10
Unknown Abis PCM
11
Wrong software reference
12
Further files required
13
Failure during activation
14
Data format error
2.5.1 Source 1: Equipment failure

(page 278)
2.5.4 Source 4: Unknown test

(page 281)
2.5.5 Source 5: Cell parameters
inconsistency (page 281)
2.5.8 Source 8: TEI not present

(page 285)
2.5.9 Source 9: Unknown Abis
PCM_Time_Slot (page 286)
PCM (page 286)
2.5.11 Source 11: Wrong software
reference (page 287)
2.5.12 Source 12: Further files
required (page 287)
2.5.13 Source 13: Failure during
activation (page 287)
2.5.14 Source 14: Data format error
(page 288)

411-9001-104 18.05 2 February 2010
275
Table 2
Source
No.
Source wording
Paragraph
15
Window overflow
16
Normal completion
17
Transfer aborted
2.5.17 Source 17: Transfer aborted

(page 288)
18
Checksum error
2.5.18 Source 18: Checksum error

(page 288)
19
File incomplete
2.5.19 Source 19: File incomplete

(page 289)
20
File already present and correct
21
File cannot be downloaded
22
Entity engaged in other download
23
Too many signaling timeslots
24
Too many TEI connections to physical

channel
25
Out of sequence message
26
Incorrect IEI
27
Wrong file reference
28
Bad cell number
2.5.28 Source 28: Bad cell number

(page 294)
29
Bad related TEI
2.5.29 Source 29: Bad related TEI

(page 294)
30
Bad timeslot
31
Window size not allowed
32
Flash boot required
2.5.15 Source 15: Window overflow

(page 288)
2.5.16 Source 16: Normal completion
(page 288)
2.5.20 Source 20: File already present

and correct (page 289)
2.5.21 Source 21: File cannot be
downloaded (page 289)
2.5.22 Source 22: Entity engaged in
other download (page 289)
2.5.23 Source 23: Too many signaling
timeslots (page 289)
2.5.24 Source 24: Too many TEI
connections to physical channel
(page 291)
2.5.25 Source 25: Out of sequence
message (page 291)
2.5.26 Source 26: Incorrect IEI
(page 293)
2.5.27 Source 27: Wrong file reference
(page 293)
2.5.30 Source 30: Bad timeslot

(page 294)
2.5.31 Source 31: Window size not
allowed (page 294)
2.5.32 Source 32: Flash boot required
(page 294)

411-9001-104 18.05 2 February 2010
276
Table 2
Source
No.
Source wording
Paragraph
33
Wrong config reference
34
The BTS has not acknowledged the

TX power consign request
35
Downloading aborted
2.5.35 Source 35: Downloading

aborted (page 300)
36
Files missing
2.5.36 Source 36: Files missing

(page 300)
37
Buffer overflow
38
Block not received
39
Downloading restart

restart (page 301)
40
Request not supported
2.5.40 Source 40: Request not

supported (page 301)
41
Downloading failure

failure (page 301)
42
Start-up failure
43
Maximum number of joker timeslots
44
Bad chain type
45
Bad radio timeslot reference
2.5.45 Source 45: Bad radio timeslot

46
Bad internal link EDGE configuration
2.5.46 Source 46: Bad internal Link

EDGE configuration (page 305)
47
Inconsistent mapping
48
Inconsistent number of joker DS0
49
Invalid mode
50
File already open
2.5.33 Source 33: Wrong config

2.5.34 Source 34: The BTS has not
acknowledged the TX power consign
request (page 295)
2.5.37 Source 37: Buffer overflow

(page 300)
2.5.38 Source 38: Block not received
(page 301)
2.5.42 Source 42: Start-up failure

(page 301)
2.5.43 Source 43: Maximum number
of joker TS (page 302)
2.5.44 Source 44: Bad chain type
(page 305)
2.5.47 Source 47: Inconsistency

mapping (page 305)
2.5.48 Source 48: Inconsistency number
of joker DS0 (page 305)
2.5.49 Source 49: Invalid mode
(page 306)
2.5.50 Source 50: File already
open (page 306)

411-9001-104 18.05 2 February 2010
277
Table 2
Source
No.
Paragraph
Source wording
51
File cannot be unloaded

unloaded (page 306)
52
Boot cannot be unloaded
2.5.52 Source 52: Boot cannot be

unloaded (page 306)
53
Data decode error
54
Flash flag cannot access
55
Table cannot access
2.5.55 Source 55: Table cannot

access (page 307)
56
RAM mapping error
2.5.56 Source 56: RAM mapping

error (page 307)
57
Flash access error
2.5.57 Source 57: Flash access

error (page 307)
58
Flash write error
2.5.58 Source 58: Flash write error

(page 307)
59
Flash erase error
2.5.59 Source 59: Flash erase error

(page 308)
60
Internal abort
61
Equipment not able to get external

synchronization
62
Synchronization in progress
63
Dynamic Abis feature not supported
2.5.63 Source 63: Dynamic Abis feature

not supported (page 308)
64
Inconsistent number of joker DS0
2.5.64 Source 64: Inconsistent number

255
Non-significant value
2.5.53 Source 53: Data decode

error (page 306)
2.5.54 Source 54: Flash flag cannot
access (page 307)
2.5.60 Source 60: Internal abort

(page 308)
2.5.61 Source 61: Equipment not able to
get external synchronization (page 308)
2.5.62 Source 62: Synchronization
in progress (page 308)
2.5.66 Source 255: Non-significant

value (page 314)
FAULT LOCATION
The objects to suspect are as follows:
the btsSiteManager
the bts

411-9001-104 18.05 2 February 2010
278
the transceiver
the transceiverEquipment

Fault number 1055 : Abis negative acknowledgement indication
Source:
(1) Equipment failure
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates an equipment failure.
2.5.2 Source 2: Equipment unable to perform such test

Source:
(2) Equipment unable to perform such test
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates that the PCM number, the cell number, and/or the
number of time slots declared at the OMC-R are higher than those of the
hardware configuration of the BTS.
BSC defense
None.
For the btsSiteManager object
CAUTION
The site is not configured.
For the bts object
CAUTION
The cell is not configured.
For the transceiver object

411-9001-104 18.05 2 February 2010
279
CAUTION
Service reduction
The TDMA is not configured.
For the transceiverEquipment object
CAUTION
Service reduction
The TRX is not configured and one TDMA is lost.
TROUBLESHOOTING
Modify the parameters declared at the OMC-R.
2.5.3 Source 3: Invalid configuration

Fault number 1055: Abis negative acknowledgement indication
Source:
(3) Invalid configuration
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates that the TRX configuration is not possible because of
a DRX frequency band error.
BSC defense
The BSC unconfigures the transceiverEquipment object concerned by the
alarm.
CAUTION
TROUBLESHOOTING
Step
Action
Perform a "Display" command on the bts object.

411-9001-104 18.05 2 February 2010
280
The "standardIndicator" parameter indicates the frequency

band associated with the DRX module: "gsm", "extended gsm",
"dcs1800", "pcs1900", "R gsm", "gsmdcs" or "dcsgsm".
If the "standardIndicator" parameter is "gsmdcs", perform a

"Display" command on the transceiverEquipment object.
If the "transceiverEquipmentClass" parameter is "1", it
means that the DRX is GSM.
means that the DRX is DCS.
If the "standardIndicator" parameter is "dcsgsm", perform a

Check the DRX frequency band declared at the OMC-R with the
PEC or CPC code of the DRX present in the cabinet.
If the DRX frequency band is the same as the one indicated

by the "transceiverEquipmentClass" parameter, clear the
If the DRX frequency band is not the same as the one

indicated by the "transceiverEquipmentClass" parameter and
if the DRX has just been replaced, go to step 3, otherwise,
go to step 4.
The alarm may be due to an error in the DRX replacement. So

replace the DRX (Field Replaceable Unit) by:
setting the administrativeState of the transceiverEquipment

object corresponding to the faulty DRX to "locked"
CAUTION
In most cases, the transceiverEquipment and one
transceiver are lost.
replacing the DRX module. see Nortel GSM BTS

S2000H/S2000L Troubleshooting (411-9001-049)
Go to step 4.
4
Make sure that the DRX used is correct, so modify the value of
the "transceiverEquipmentClass" parameter according to the
DRX frequency band. Go to step 5.

411-9001-104 18.05 2 February 2010
281

--End--

Source:
(4) Unknown test
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates an unknown test.
2.5.5 Source 5: Cell parameters inconsistency

Source:
(5) Cell parameters inconsistency
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates that the TEI value that is configured on the TRX is
greater than the maximum number of TRX authorized by hardware rules
in a cell.
BSC defense
None.
The bts object is in a "disabled/failed" state.
CAUTION
No service is provided on the cell.

411-9001-104 18.05 2 February 2010
282
CAUTION
Service reduction
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Perform a "Display" command on the affected TRX object.

The "teiTransceiverEqpt" parameter indicates the TEI value
associated with the TRX module.
The value of the "teiTransceiverEqpt" parameter should be within
the range specified by the S2000 H/L BTS engineering rules for
the corresponding configuration reference and associated DLUs.
Lock the affected TRX object.
Change the value of "teiTransceiverEqpt" so that it conforms to

the engineering rules specified above.
Unlock the TRX object.
Check that the alarm is cleared.

--End--

Source:
(6) Data inconsistency
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates that the PCM list contains PCM identical numbers.
411-9001-104 18.05 2 February 2010
283

BSC defense
None.
CAUTION
For the bts object
CAUTION
CAUTION
Service reduction
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Check the PCM cabling.
If the cabling is correct, go to step 2.

If the cabling is not correct, replace the cables if necessary.

411-9001-104 18.05 2 February 2010
284
Check the configuration associated with the object at the

OMC-R. If necessary, modify the PCM numbers declared at the
OMC-R.

--End--

Source:
(7) Value out of range
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates that the cell configuration is not possible due to an
incorrect value.
The different sources of non-acknowledgement are:
BCCH frequency value in no known band

BSIC > 63
Diversity Flag is set to a value other than Enabled or Disabled
Max Power for Cell > 55 dBm
Frequency Hopping Flag is set to a value different from the following:
ENABLED_BCCH_STUFF
ENABLED_NO_BCCH_STUFF
DISABLED_BCCH_STUFF
DISABLED_NO_BCCH_STUFF
Number of frequency band = 0 or > 2

Any frequency in the list is in no known band
Number of TEI < 1

BSC defense None.
For the bts object

411-9001-104 18.05 2 February 2010
285
CAUTION
Service reduction
TROUBLESHOOTING
Modify the values declared out of range at the OMC-R.

Source:
(8) TEI not present
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates that the TEI of the associated transceiver equipment
is:
not between 32 and 55
or
is not in the permitted list of TEI of the corresponding CELL

Configuration

BSC defense None.
CAUTION
Service reduction
CAUTION
Service reduction

411-9001-104 18.05 2 February 2010
286
2.5.9 Source 9: Unknown Abis PCM_Time_Slot

Source:
(9) Unknown Abis PCM_Time_Slot
BTS model:
S8000 Outdoor + S8000 Indoor + S8002 + S8003 + S8006
FAULT ANALYSIS
This source indicates an unknown Abis PCM Time Slot.
2.5.10 Source 10: Unknown Abis PCM

Source:
(10) Unknown Abis PCM
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates that the PCM is not present in the PCM list.
BSC defense
None.
CAUTION
For the bts object
CAUTION

411-9001-104 18.05 2 February 2010
CAUTION
Service reduction
CAUTION
Service reduction
TROUBLESHOOTING
Parametrize the PCM declared unknown at the OMC-R.
2.5.11 Source 11: Wrong software reference

Source:
(11) Wrong software reference
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a wrong software reference.
2.5.12 Source 12: Further files required

Source:
(12) Further files required
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that further files are required.
2.5.13 Source 13: Failure during activation

Source:
(13) Failure during activation
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a failure during activation.

411-9001-104 18.05 2 February 2010
287
288

Source:
(14) Data format error
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a data format error.

Source:
(15) Window overflow
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a window overflow.

Source:
(16) Normal completion
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a normal completion.

Source:
(17) Transfer aborted
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates an aborted transfer.

Source:
(18) Checksum error
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a checksum error.

411-9001-104 18.05 2 February 2010

Source:
(19) File incomplete
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates an incomplete file.
2.5.20 Source 20: File already present and correct

Source:
(20) File already present and correct
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a file already present and correct.
2.5.21 Source 21: File cannot be downloaded

Source:
(21) File cannot be downloaded
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that the file cannot be downloaded.
2.5.22 Source 22: Entity engaged in other download

Source:
(22) Entity engaged in other download
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that the entity is engaged in other download.
2.5.23 Source 23: Too many signaling timeslots

Source:
(23) Too many signaling timeslots
BTS model:
S2000 H/L
FAULT ANALYSIS
411-9001-104 18.05 2 February 2010
289
290
This alarm indicates the value of signaling timeslot number is higher than
6.
BSC defense
None.
CAUTION
For the bts object
CAUTION
CAUTION
Service reduction
CAUTION
Service reduction
TROUBLESHOOTING
Modify the value of the signaling timeslot number.

411-9001-104 18.05 2 February 2010
291
2.5.24 Source 24: Too many TEI connections to physical channel

Source:
(24) Too many TEI connections to physical channel
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that there are too many TEI connections to the
physical channel.
2.5.25 Source 25: Out of sequence message

Source:
(25) Out of sequence message
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates that the message of site configuration has been
received twice but with different values by the BTS on the Abis interface.
The message is not accepted because of the state of the BTS.
BSC defense
None.
CAUTION
For the bts object
CAUTION

411-9001-104 18.05 2 February 2010
292
CAUTION
Service reduction
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Check the configuration associated with the object.
For the btsSiteManager object:

Check the logical configuration of the btsSiteManager
object (teiBtsSiteManager, bscSitePcmList, radioSiteMask
parameters).
If it is not correct, set the object to "locked".
Modify the configuration.
Set the object to "unlocked".
If it is not correct, perform the "Display hardware
configuration" command on the btsSiteManager object to
identify the faulty element.
For the bts object

a. Check the logical configuration of the bts object and its
objects.

If it is correct, perform the "Display hardware

configuration" command on the btsSiteManager to
b. In the case of the base cabinet associated with the

extension cabinet, set the btsSiteManager object to
"locked" then to "unlocked".

411-9001-104 18.05 2 February 2010
293
a. Set the administrativeState of the transceiver object to

"shuttingDown".
b. Check the logical configuration of the transceiver object
(channelType, absoluteRFChannelNo parameters for
each channel).
c. Set the administrativeState of the transceiver object to
"unlocked".

Check the logical configuration of the transceiverEquipment
object (teiTransceiverEqpt parameter).

2

--End--

Source:
(26) Incorrect IEI
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates an incorrect IEI.

Source:
(27) Wrong file reference
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a wrong file reference.

411-9001-104 18.05 2 February 2010
294

Source:
(28) Bad cell number
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a bad cell number.

Source:
(29) Bad related TEI
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a bad related TEI.

Source:
(30) Bad timeslot
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a bad timeslot.
2.5.31 Source 31: Window size not allowed

Source:
(31) Window size not allowed
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that the window size is not allowed.

Source:
(32) Flash boot required
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that a flash boot is required.

411-9001-104 18.05 2 February 2010
295
2.5.33 Source 33: Wrong config reference

Source:
(33) Wrong config reference
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a wrong config reference.
2.5.34 Source 34: The BTS has not acknowledged the TX power
consign request
Source:
(34) The BTS has not acknowledged the TX power

consign request
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates that the power, configured at the OMC-R for the TX
concerned, is not compatible with the TX hardware.
BSC defense
The BSC unconfigures the faulty transceiverEquipment object and the
associated transceiver object. It tries to assure a minimum service of
communication by unconfiguring and reconfiguring the transceiver object.
At least one TRX is lost.
CAUTION
Service reduction
It is possible to lose the whole cell linked to the faulty TRX.
CAUTION
The intervention on the site must be immediate: there is a risk
of service loss.
TROUBLESHOOTING

411-9001-104 18.05 2 February 2010
296

Preliminary checks
Step
Action


"enabled", the site is operational. Go to step 2.

"disabled-dependency", the site is not operational.
Look for an object whose state is "disabled-failed" and
treat the problem in order that the btsSiteManager object
becomes "enabled".

Do not treat the alarm and do not clear it.
Look for other alarms and treat the problem in order that
the btsSiteManager object becomes "enabled". If a fault
number 1054 (loss of layer 2) has appeared, see the
fault number 1054 (see Nortel GSM BSS Fault Clearing Advanced Maintenance (411-9001-105) ).

"disabled", the site is not operational.
a. As long as the operationalState of the btsSiteManager
object is "disabled", do not treat the alarm and do
not clear it. Wait that the state of the btsSiteManager
object becomes "enabled", "disabled-dependency", or
"disabled-failed".
b. As soon as the site is operational (the operationalState of
the btsSiteManager object will be "enabled"), check if the
alarm still persists.
Check that the alarm on the TX module is valid, by performing

a "Display hardware configuration" command on the
Look at the result displayed in the "Session log" window.
If the state of the "TX" equipment is "failed", the fault is

confirmed. Go to step 3.
If the state of the "TX" equipment is "working", the fault is not

Maintenance using the OMC-R
Perform a "Display" command on the bts object to check if the

cells are concentric.

411-9001-104 18.05 2 February 2010
297
If the "concentric cell" parameter is "monozone", go to step 4.

If the "concentric cell" parameter is "concentric" or "dual
band" or "dual coupling", go to step 5.
Check the value of the "bsTxPwrMax" parameter according to

the following information.
The value of the "bsTxPwrMax" parameter added to the value to
the attenuation of the combiner must be between 31dBm and
44dBm, or 32dBm at the band limit for GSM 1900 only.
The "bsTxPwrMax" parameter is a parameter of the
powerControl object associated with the bts object.
The "Attenuation" parameter is obtained by a "Display" command
on the btsSiteManager object.
The following table allows to know directly the good values of the
"bsTxPwrMax" parameter depending on the combiners used in
the BTS. The "Nack" value is not admitted.
BTS model
S2000H/L Indoor
Combiners
H2
H4
H2D
Cavity/Duplexer
Cavity
DLU
attenuation
51 to 45
Nack
Nack
Nack
Nack
Nack
Nack
Nack
44
Nack
Nack
Nack
Nack
Nack
Nack
Nack
43
Nack
Nack
Nack
Nack
Nack
Nack
Nack
42
Nack
Nack
Nack
Nack
Nack
Pmax
Nack
41
Nack
Nack
Nack
Pmax
Nack
Pmax
Pmax
40
Pmax
Nack
Pmax
Pmax
Pmax
Pmax-2
Pmax
39
Pmax
Nack
Pmax
Pmax-2
Pmax
Pmax-2
Pmax-2
38
Pmax-2
Nack
Pmax-2
Pmax-2
Pmax-2
Pmax-4
Pmax-2
37
Pmax-2
Pmax
Pmax-2
Pmax-4
Pmax-2
Pmax-4
Pmax-4
36
Pmax-4
Pmax
Pmax-4
Pmax-4
Pmax-4
Pmax-6
Pmax-4
35
Pmax-4
Pmax-2
Pmax-4
Pmax-6
Pmax-4
Pmax-6
Pmax-6
34
Pmax-6
Pmax-2
Pmax-6
Pmax-6
Pmax-6
Pmax-8
Pmax-6
33
Pmax-6
Pmax-4
Pmax-6
Pmax-8
Pmax-6
Pmax-8
Pmax-8
32
Pmax-8
Pmax-4
Pmax-8
Pmax-8
Pmax-8
Pmax-10
Pmax-8
31
Pmax-8
Pmax-6
Pmax-8
Pmax-1
0
Pmax-8
Pmax-10
Pmax-1
0
30
Pmax-10
Pmax-6
Pmax-10
Pmax-1
0
Pmax-10
Pmax-12
Pmax-1
0
bsTxPwrMax

411-9001-104 18.05 2 February 2010
298
BTS model
S2000H/L Indoor
Combiners
H2
H4
H2D
Cavity/Duplexer
Cavity
DLU
attenuation
29
Pmax-10
Pmax-8
Pmax-10
Pmax-1
2
Pmax-10
Pmax-12
Pmax-1
2
28
Pmax-12
Pmax-8
Pmax-12
Pmax-1
2
Pmax-12
Nack
Pmax-1
2
27
Pmax-12
Pmax-10
Pmax-12
Nack
Pmax-12
Nack
Nack
26
Nack
Pmax-10
Nack
Nack
Nack
Nack
Nack
25
Nack
Pmax-12
Nack
Nack
Nack
Nack
Nack
24
Nack
Pmax-12
Nack
Nack
Nack
Nack
Nack
23
Nack
Nack
Nack
Nack
Nack
Nack
Nack
22 to 21
Nack
Nack
Nack
Nack
Nack
Nack
Nack
bsTxPwrMax
BTS model
S2000 H/L Outdoor
Combiners
Duplexer
H2
DLU
attenuation
51 to 45
Nack
Nack
Nack
44
Nack
Nack
Nack
43
Pmax
Nack
Nack
42
Pmax
Pmax
Nack
41
Pmax-2
Pmax
Nack
40
Pmax-2
Pmax-2
Pmax
39
Pmax-4
Pmax-2
Pmax
38
Pmax-4
Pmax-4
Pmax-2
37
Pmax-6
Pmax-4
Pmax-2
36
Pmax-6
Pmax-6
Pmax-4
35
Pmax-8
Pmax-6
Pmax-4
34
Pmax-8
Pmax-8
Pmax-6
33
Pmax-10
Pmax-8
Pmax-6
32
Pmax-10
Pmax-10
Pmax-8
31
Pmax-12
Pmax-10
Pmax-8
bsTxPwrMa
x

411-9001-104 18.05 2 February 2010
BTS model
299
S2000 H/L Outdoor
Combiners
Duplexer
H2
DLU
attenuation
30
Pmax-12
Pmax-12
Pmax-10
29
Nack
Pmax-12
Pmax-10
28
Nack
Nack
Pmax-12
27
Nack
Nack
Pmax-12
26
Nack
Nack
Nack
25
Nack
Nack
Nack
24
Nack
Nack
Nack
23
Nack
Nack
Nack
22 to 21
Nack
Nack
Nack
bsTxPwrMa
x
If the value is not correct, change it.

If the value is correct, replace the TX module (Field
Replaceable Unit). See the replacement procedure given
in Nortel GSM BTS S2000H/S2000L Troubleshooting
(411-9001-049).
Then go to step 6.
5
Modify the value of the "bsTxPwrMax" parameter according to

the attenuation of the combiner and reduced of the value of the
"transceiver zone Ref" parameter must be between 31dBm and
The "transceiver zone Ref" parameter is obtained by performing
a "Display" command on the transceiver object.
ATTENTION
This parameter must not be filled in for the "dual band" or "dual
coupling" values of the "concentric cell" parameter.
The preceding table allows to know the good values of the


411-9001-104 18.05 2 February 2010
300
the BTS. The "Nack" value is not admitted. However, do not

forget to consider the "transceiver zone Ref" parameter.

Replaceable Unit). see the replacement procedure given
in Nortel GSM BTS S2000H/S2000L Troubleshooting
(411-9001-049).
Then go to step 6.
Additional checks
Clear the alarm.
Set the bts object to "locked".
Set the bts object to "unlocked".

--End--
2.5.35 Source 35: Downloading aborted

Source:
(35) Downloading aborted
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that the downloading has been aborted.

Source:
(36) Files missing
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that files are missing.

Source:
(37) Buffer overflow
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a buffer overflow.
411-9001-104 18.05 2 February 2010

Source:
(38) Block not received
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that a block has not been received.
2.5.39 Source 39: Downloading restart

Source:
(39) Downloading restart
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a downloading restart.
2.5.40 Source 40: Request not supported

Source:
(40) Request not supported
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a request not supported.
2.5.41 Source 41: Downloading failure

Source:
(41) Downloading failure
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a downloading failure..

Source:
(42) Start-up failure
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a start-up failure.

411-9001-104 18.05 2 February 2010
301
302
2.5.43 Source 43: Maximum number of joker TS

Source:
(43) Maximum number of joker TS
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates that there an inconsistency between the number of
joker TS requested by the operator and the BTS capability.
Joker TS provisioning per TDMA is dependent on hardware constraints
(both BCF/CBCF chains must have the same type of hardware) and also
on existing backhaul configuration.

BSC defense The transceiver object is not configured by the BSC.
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



If a fault number 1054 (loss of layer 2) has appeared,
refer to the fault number 1054 (see 411-9001-105 (Nortel
Procedures) ).
If not, look for an object whose state is "disabled-failed"
and process the problem in order that the btsSiteManager
object becomes "enabled".

"disabled-failed", the site is not operational. Do not process

411-9001-104 18.05 2 February 2010
303
the alarm and do not clear it. Look for other alarms and
process the problem in order that the btsSiteManager object
becomes "enabled".

object is "disabled", do not process the alarm and do
not clear it. Wait for the state of the btsSiteManager
object to become "enabled", "disabled-dependency", or
"disabled-failed".
alarm persists.
Otherwise, go to step 5.
Explore the site capability:

a Perform a "Display hardware information" command
("standard" mode) on the btsSiteManager object at the
OMC-R.
The OMC-R displays the site type (BCF, or CBCF with CMCF
phase 1 or phase 2) and state (working or failed).
b Perform a "Display data information" command (with "EDGE"
option) on the btsSiteManager object at the OMC-R.
The OMC-R displays the GPRS and EDGE capabilities
of each TRX. This will give the maximum number of joker
TS supported by the BCF/CBCF and TRXs. Look for the
following items of information:
Hardware btsSiteManager capability

Max number of timeslot per transceiverEquipment
for active board (main + joker): see Table 3
"Maximum number of TS (main and joker) per
transceiverEquipment" (page 304) below
Max number of timeslot per transceiverEquipment for
passive board (main + joker):
Duplex site consistency: "identical capabilities" / "non
identical capabilities"
Hardware transceiverEquipment capability

411-9001-104 18.05 2 February 2010
304
Max number of timeslot (main + joker): see Table

3 "Maximum number of TS (main and joker) per
GPRS capability: "up to CSx"
EDGE capability: "full" / "none"
As a reminder, here are the permitted maximum
values:
Table 3
Maximum number of TS (main and joker) per transceiverEquipment
Type of site
Maximum number of timeslot (main + joker) per

transceiverEquipment
BCF old GTW PROM
BCF new GTW PROM
CBCF CMCF phase 1
CBCF CMCF phase 2
Check the configuration of the transceiver object concerned, and

compare it with the capabilities analyzed in step 2.
As a reminder, here are the value ranges of the parameters
related to joker TS:
numberOfJokerDS0
[0..4] for S8000 BCF
[0..6] for S8000 CBCF
jokerPerMainTarget
[0..4]
The recommended values are 2, 3 or 4, depending on
operator Abis configuration (numberOfJokerDS0) and
estimated EDGE TDMA throughput.
If the configuration is not correct, set the transceiver object

to "locked".
Set the transceiver object to "unlocked".
If the configuration is correct, save the information gathered

in step 2, as well as the site configuration, and then call the
manufacturer.

--End--

411-9001-104 18.05 2 February 2010

Source:
(44) Bad chain type
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a bad chain type.
2.5.45 Source 45: Bad radio timeslot reference

Source:
(45) Bad radio timeslot reference
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a bad radio timeslot reference.
2.5.46 Source 46: Bad internal Link EDGE configuration

Source:
(46) Bad internal Link EDGE configuration
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a bad internal link EDGE configuration.
2.5.47 Source 47: Inconsistency mapping

Source:
(47) Inconsistency mapping
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates an inconsistency mapping.
2.5.48 Source 48: Inconsistency number of joker DS0

Source:
(48) Inconsistency number of joker DS0
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates an inconsistency number of joker DS0.

411-9001-104 18.05 2 February 2010
305
306

Source:
(49) Invalid mode
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates an invalid mode.
2.5.50 Source 50: File already open

Source:
(50) File already open
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that the file is already open.
2.5.51 Source 51: File cannot be unloaded

Source:
(51) File cannot be unloaded
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that the file cannot be unloaded.
2.5.52 Source 52: Boot cannot be unloaded

Source:
(52) Boot cannot be unloaded
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that the boot cannot be unloaded.
2.5.53 Source 53: Data decode error

Source:
(53) Data decode error
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
FAULT ANALYSIS
This source indicates a data decode error.
2.5.54 Source 54: Flash flag cannot access

Source:
(54) Flash flag cannot access
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates an access problem to the flash flag.
2.5.55 Source 55: Table cannot access

Source:
(55) Table cannot access
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates an access problem to a table.
2.5.56 Source 56: RAM mapping error

Source:
(56) RAM mapping error
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a RAM mapping error.
2.5.57 Source 57: Flash access error

Source:
(57) Flash access error
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a flash access error.

Source:
(58) Flash write error
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
307
308
FAULT ANALYSIS
This source indicates a flash write error.

Source:
(59) Flash erase error
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a flash erase error.

Source:
(60) Internal abort
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates an internal abort.
2.5.61 Source 61: Equipment not able to get external synchronization

Source:
(61) Equipment not able to get external synchronization
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates that an equipment is not able to get the external
synchronization.
2.5.62 Source 62: Synchronization in progress

Source:
(62) Synchronization in progress
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a synchronization in progress.
2.5.63 Source 63: Dynamic Abis feature not supported

Source:
(63) Dynamic Abis feature not supported
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
309
FAULT ANALYSIS
At the reception of a "site config" message with dynamic Abis feature
activated, if one of the CMCF of the BTS is a phase 1, a "site config Nack"
message with the cause Dynamic Abis feature not supported is sent to
the BSC. The BSC must stop the configuration of the BTS.
Besides, in case of inconsistencies detected by the BTS, the BTS sends a
"traffic connect Nack" message with the cause Dynamic Abis feature not
supported (in response of a received "traffic connect" message)
Moreover in case a BTS is equipped with an eDRX that supports the
dynamic Abis feature, but with an S8000 BCF, then the dynamic Abis
feature is not supported by the BTS.
BSC defense
The BSC stops the configuration of the BTS.
CAUTION
Service reduction
The BTS is not configured.
TROUBLESHOOTING
Modify the BTS configuration:
either deactivate the dynamic Abis feature

or upgrade the BTS (replace CMCF phase 1 with CMCF phase 2, or
replace BCF with CBCF)
2.5.64 Source 64: Inconsistent number of joker DS0

Source:
(64) Inconsistent number of joker DS0
BTS model:
S2000H/L
FAULT ANALYSIS

411-9001-104 18.05 2 February 2010
310
When proceeding with the dynamic Abis feature, the BTS receives the
following information from the BSC: a poolRef which represents the
pool reference on Abis to which a EDGE TDMA belongs (traffic connect
message)
If the BSC has requested more jokers in the pool than the capacity
indicated through the status report message, then this is a case of internal
inconsistencies detected by the BTS, and as a consequence the BTS
sends a traffic connect nack message (in response of a received traffic
connect message) with the cause 64 "Inconsistent number of joker DS0".
Then this alarm indicates that the number of DS0 inside one poolRef
exceeds the pool maximum capability.
BSC defense
None.
CAUTION
Service reduction
The TRX is not configured. One TDMA is lost.
TROUBLESHOOTING
Preliminary checks
Step
Action


Clear the alarm.


411-9001-104 18.05 2 February 2010
311

concerning cells.
Procedures)).


above).

Procedures)).

As soon as the TRX is operational (the operationalState
of the transceiverEquipment object will be "enabled"),
check if the alarm persists.
Set the object concerned to "locked", then to "unlocked".


--End--

411-9001-104 18.05 2 February 2010
312
2.5.65 Source 65: Exceeded DL joker DS0 pool number

Source:
(65) Exceeded DL joker DS0 pool number
BTS model:
S20000H/L
FAULT ANALYSIS
message)
connect message) with the cause 65 "Exceeded DL joker DS0 pool
number".
BSC defense
None.
CAUTION
Service reduction
TROUBLESHOOTING
Procedure 2
Preliminary checks
Step
Action



411-9001-104 18.05 2 February 2010
313
Clear the alarm.


concerning cells.
Procedures)).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
314


--End--
2.5.66 Source 255: Non-significant value

Source:
(255) Non-significant value
BTS model:
S2000H/L
FAULT ANALYSIS
This source indicates a non-significant value.

Fault number:
1056
Incorrect parameter settings at the OMC-R
Type
equipmentAlarm
FAULT ANALYSIS
Fault number 1056 is sent when BSC detects an incorrect BDA
configuration for a btsSiteManager, bts, transceiverEquipment or
transceiver.
The managed object stays in a disabled/failed state.
CAUTION

411-9001-104 18.05 2 February 2010
315
CAUTION
Service reduction
The TRX is not downloaded. One TDMA is not configured.
TROUBLESHOOTING
Step
Action
Lock the impacted bts object.
Correct the OMC-R parameters.
If the parameters are correct, perform an audit BDA on the

BSC.
If the audit does not reveal inconsistencies between the
BDA and the BDE, go to step 3.
If the audit reveals differences, perform a "off line reset
BDA". Then execute a "build BDA" of the BSC (always
in automatic mode). For more information on these
commands, refer to Nortel GSM BSS Configuration Operating Procedures (411-9001-034). Then go to step 3.
Unlock the bts object.

--End--
Table 4
Source
No.
Paragraph
Source wording
Incorrect priority on transceiver
2.6.1 Source 0: Incorrect

priority on transceiver
(page 316)
Incorrect setting of channel on

transceiver
2.6.2 Source 1: Incorrect

setting of channel on
transceiver (page 317)
Cell without BCCH TDM
2.6.3 Source 2: Cell without

BCCH TDM (page 317)
Radio Time Slot not used
2.6.4 Source 3: Radio Time

Slot not used (page 317)
Wrong value for BSS TEI in T1

mode
2.6.5 Source 4: Wrong

value for BSS TEI in T1
mode (page 317)

411-9001-104 18.05 2 February 2010
316
Table 4
Source
No.
Paragraph
Source wording
Cell cfg with cavity and dual band

not acceptable
2.6.6 Source 5: Cell cfg with

cavity and dual band not
acceptable (page 318)
Missing Site management Abis GSM

function
2.6.7 Source 6: Missing

Site management Abis GSM
function (page 318)
Missing Abis Signalling management

Abis GSM function

Abis Signalling management
Abis GSM function (page
318)
Missing Abis Traffic management

Abis GSM function
Missing RfTrans management Abis

GSM function

RfTrans management Abis
GSM function (page 318)
10
Missing cell management Abis GSM

function

cell management Abis GSM
function (page 319)
11
Missing TDMA management Abis

GSM function

TDMA management Abis
GSM function (page 319)
12
Missing TS management Abis GSM

function

TS management Abis GSM
function (page 319)
13
The TDMA exists in RDC but the

object was not created.
2.6.14 Source 13: The

TDMA exists in RDC but
the object was not created.
(page 319)
14
Too many EDGE TDMAs (>16 per

site) configured
2.6.15 Source 14: Too

many EDGE TDMAs (more
than 16 per site) configured
(page 320)

Abis traffic management
Abis GSM function
(page 318)
2.6.1 Source 0: Incorrect priority on transceiver

Fault number 1056
Incorrect parameter setting at the OMC-R level
Source:
(0) Incorrect priority on transceiver
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
317
FAULT ANALYSIS
This alarm indicates an incorrect priority setting on the transceiver, at the
OMC-R.
2.6.2 Source 1: Incorrect setting of channel on transceiver

Fault number 1056
Source:
(1) Incorrect setting of channel on transceiver
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates an incorrect setting of channel on the transceiver
object at the OMC-R.
2.6.3 Source 2: Cell without BCCH TDM

Fault number 1056
Source:
(2) Cell without BCCH TDM
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates a cell without BCCH TDM.
2.6.4 Source 3: Radio Time Slot not used

Fault number 1056
Source:
(3) Radio Time Slot not used
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates a radio Time Slot not used.
2.6.5 Source 4: Wrong value for BSS TEI in T1 mode

Fault number 1056
Source:
(4) Wrong value for BSS TEI in T1 mode
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates a wrong value for BSS TEI in T1 mode.

411-9001-104 18.05 2 February 2010
318
2.6.6 Source 5: Cell cfg with cavity and dual band not acceptable
Fault number 1056
Source:
(5) Cell cfg with cavity and dual band not acceptable
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates a cell configuration with cavity and dual band (not
acceptable).
2.6.7 Source 6: Missing Site management Abis GSM function

Fault number 1056
Source:
(6) Missing Site management Abis GSM function
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates a missing Site management Abis GSM function.
2.6.8 Source 7: Missing Abis Signalling management Abis GSM

function
Fault number 1056
Source:
(7) Missing Abis Signalling management Abis GSM function
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates a Missing Abis Signalling management Abis GSM
function.
2.6.9 Source 8: Missing Abis traffic management Abis GSM function

Fault number 1056
Source:
(8) Missing Abis traffic management Abis GSM function
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates a missing Abis traffic management Abis GSM
function.
2.6.10 Source 9: Missing RfTrans management Abis GSM function

Fault number 1056
Source:
(9) Missing RfTrans management Abis GSM function
BTS model:
S2000H/L

411-9001-104 18.05 2 February 2010
319
FAULT ANALYSIS
This alarm indicates a missing RfTrans management Abis GSM function.
2.6.11 Source 10: Missing cell management Abis GSM function

Fault number 1056
Source:
(10) Missing cell management Abis GSM function
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates a missing cell management Abis GSM function.
2.6.12 Source 11: Missing TDMA management Abis GSM function

Fault number 1056
Source:
(11) Missing TDMA management Abis GSM function
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates a missing TDMA management Abis GSM function.
2.6.13 Source 12: Missing TS management Abis GSM function

Fault number 1056
Source:
(12) Missing TS management Abis GSM function
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates a missing TS management Abis GSM function.
2.6.14 Source 13: The TDMA exists in RDC but the object was not
created.
Fault number 1056
Source:
(13) The TDMA exists in RDC but the object was not created.
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates that the TDMA exists in RDC but the object was not
created.

411-9001-104 18.05 2 February 2010
320
2.6.15 Source 14: Too many EDGE TDMAs (more than 16 per site)
configured
Fault number 1056
Source:
(14) Too many EDGE TDMAs (>16 per site) configured
BTS model:
S2000H/L
FAULT ANALYSIS
This alarm indicates that too many EDGE TDMAs (>16 per site) are
configured.

Fault number:
1058
Type
processingErrorAlarm

An entity of the BTS detects an anomaly in its configuration, reports it to
the BSC by this alarm, and de-configures itself.
BSC defense
If the site is already operational, the BSC unconfigures the

btsSiteManager object and tries to reconfigure it.
If the site is not operational, there is a problem of connection between

the connections and the connections declared at the OMC-R.
CAUTION
For as long as the operationalState of the btsSiteManager is
"disabled-failed", the site is lost.
CAUTION
Service reduction
For as long as the operationalState of the transceiverEquip
ment is "disabled", the TRX and one TDMA are lost.
TROUBLESHOOTING

411-9001-104 18.05 2 February 2010
321
Step
Action
Set the pcmCircuit object to "locked".
Untwine the PCM links.
Set the pcmCircuit object to "unlocked".


--End--

Fault number:
1059
Invalid message received on Abis interface on O and M link
Type
communicationsAlarm
FAULT ANALYSIS
The BSC receives a message from the BTS that it cannot treat because:
either this message is out of sequence

or this message concerns an unknown element, that is a distant item of
equipment not created at the OMC-R but emitting notifications

BSC defense
None.
None.
TROUBLESHOOTING
In the case of a message on an unknown element (not declared at the

OMC-R), switch off this element.
Otherwise, do nothing.

411-9001-104 18.05 2 February 2010
322
CAUTION
Working instructions
If several fault numbers 1059 are detected by the same cell,
call the manufacturer.

Fault number:
1060
Abis event reporting a transient default
Type
equipmentAlarm
The spontaneous message 1060 corresponds to a warning and does not

require a maintenance action, except in conjunction with the 1067 fault
number.
The following table indicates all the sources of the fault number 1060
for the S2000 H/L BTS. For more information on each source, see the
indicated paragraph to know the corrective maintenance procedure
associated with this source.
Table 5
Equipme
nt
Source
No.
Source wording
Paragraph
9437187
Loss of PCM link
9437188
Loss of GSM clock
9437196
Frequency collision on FH bus
2.9.1 DRX (source: Frequency

collision on FH bus) (page 324)
9437199
Beginning of TX isolation for

maintenance
2.9.2 DRX (source: Beginning

of TX isolation for maintenance)
(page 324)
9437200
End of TX isolation for

maintenance
2.9.3 DRX (source: End of TX

isolation for maintenance) (page
325)
9437207
FACCH congestion
2.9.4 DRX (source: FACCH

congestion) (page 325)
9437208
LAPD congestion
9437210
Underrun AMNU-SPU
9437218
Nack answer
2.9.5 DRX (source: Nack answer)

(page 326)
9437219
Reset DRX by BSC
2.9.6 DRX (source: DRX reset by

BSC) (page 327)
DRX

411-9001-104 18.05 2 February 2010
Equipme
nt
SBCF
SBCF
323
Source
No.
Source wording
Paragraph
9437220
DRX-PA link down on start-up
9437425
Post mortem dump zone 1
9437426
9437427
9437440
Restart due to reset by BSC
9437441
Restart due to reset by reset

button
9437442
Restart due to power on
6422530
Unknown message on Abis

interface
2.9.7 SBCF board (source:

Unknown message on Abis
interface) (page 327)
6422560
2.9.8 SBCF board (source: Restart

due to reset by BSC) (page 327)
6422561

button
2.9.9 SBCF boards (source:

button) (page 327)
6422562

Restart due to power on) (page
328)
6422563
Restart due to a too long PCM

scanning

scanning) (page 328)
6422564
Restart requested by the active

board

Restart requested by the active
board) (page 328)
6422565
Restart due to a software upgrade

Restart due to a software upgrade)
(page 329)
6422566
Restart due to hardware watchdog

Restart due to hardware
watchdog) (page 329)
6422567
Restart due to double bus fault

Restart due to double bus fault)
(page 329)
6422568
Restart due to Man Machine

Interface I and C reset button

restart due to Man Machine
Interface I and C reset button)
(page 329)
6488063
Software dump

411-9001-104 18.05 2 February 2010
324
2.9.1 DRX (source: Frequency collision on FH bus)

Fault number 1060 Abis event reporting a hardware fault
Equipment:
DRX
Source:
(9437196) Frequency collision on FH bus
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates that a frequency collision has been encountered on
the FH bus. This alarm indicates a mistake in Frequency Hopping Laws.
BSC defense
None.
ATTENTION
The phonic quality is lost.
TROUBLESHOOTING
Check the cell and the Hopping Laws (namely the configuration of
Frequency Hopping Laws or the TDMA configuration if there is not any
hopping).
2.9.2 DRX (source: Beginning of TX isolation for maintenance)

Equipment:
DRX
Source:
(9437199) Beginning of TX isolation for maintenance
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates that the DRX has been isolated for maintenance by
the TIL. So the DRX is ready for local tests.
BSC defense

411-9001-104 18.05 2 February 2010
325
The BSC unconfigures the transceiverEquipment object and possibly the

cell object.
ATTENTION
2.9.3 DRX (source: End of TX isolation for maintenance)

Equipment:
DRX
Source:
(9437200) End of TX isolation for maintenance
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates that the TIL has reintegrated the DRX, after having
isolated it for maintenance.
BSC defense
The BSC reconfigures the transceiver object and possibly the cell object,
that were unconfigured for maintenance.
None.
TROUBLESHOOTING
Set the transceiverEquipment object to "locked" and then to

"unlocked".
Clear the alarm.
2.9.4 DRX (source: FACCH congestion)

Fault number 1060
Equipment:
DRX
Source:
(9437207) FACCH congestion
BTS model:
S2000 H/L

411-9001-104 18.05 2 February 2010
326
FAULT ANALYSIS
FACCH "Fast associated Control Channel" is one of the dedicated control
channels.
It is associated to a TCH channel and is used to exchange fast signaling
messages with the MS.
In compliance with GSM Rec. 5.03, a FACCH for TCH/FR is coded
over 8 bursts and for TCH/HR over 6 bursts. This imposes a maximum
transmission rate for FACCH messages, above which the messages are
queued. The queuing mechanism allows for up to 3 FACCH messagesfor
each channel (per sub-channel for TCH/HR) to be waiting for transmission.
When this limit is exceeded, the BTS sends the notification FACCH
Congestion and the waiting messages are discarded. A Timer mechanism
ensures that the dropped messages are repeated.
FACCH congestion is usually linked to handover activity (for speed and
priority reasons, FACCH channel is especially used for handover process).
Increased handover activity equals a greater risk of FACCH congestion.

BSC defense None
Impact on the service The only impact is that handovers may be
delayed by up to 160 ms, the time between 2 repetitions of the FACCH
message.
There will no impact on the counters and no dropped calls, nor service
denied.
TROUBLESHOOTING
No maintenance action is required.
2.9.5 DRX (source: Nack answer)

Fault number 1060: Abis event reporting a hardware fault
Equipment:
DRX
Source:
(9437218) Nack answer
BTS model:
S2000 H/L
FAULT ANALYSIS
This message indicates a software anomaly between the BCF and the
DRX.
Call the next level of support.

411-9001-104 18.05 2 February 2010
2.9.6 DRX (source: DRX reset by BSC)

Fault number 1060: Abis event reporting a hardware fault
Equipment:
DRX
Source:
(9437219) DRX reset by BSC
BTS model:
S2000 H/L
FAULT ANALYSIS
This message indicates a reset of the DRX by the BSC.
2.9.7 SBCF board (source: Unknown message on Abis interface)

Fault number 1060 Abis event reporting a transient default
Equipment:
SBCF
Source:
(6422530) Unknown message on Abis interface
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates an unknown Abis message.
BSC defense
None.
2.9.8 SBCF board (source: Restart due to reset by BSC)

Equipment:
SBCF
Source:
(6422560) Restart due to reset by BSC
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates a restart of an SBCF board due to a reset by the
BSC.
2.9.9 SBCF boards (source: Restart due to reset by reset button)

Equipment:
SBCF

411-9001-104 18.05 2 February 2010
327
328
Source:
(6422561) Restart due to reset by reset button
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates a restart of an SBCF board due to a reset by the reset
button.
2.9.10 SBCF boards (source: Restart due to power on)

Equipment:
SBCF
Source:
(6422562) Restart due to power on
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates a restart of an SBCF board due to a power on.
2.9.11 SBCF boards (source: Restart due to a too long PCM scanning)
Equipment:
SBCF
Source:
(6422563) Restart due to a too long PCM scanning
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates a restart of an SBCF board due to a too long PCM
scanning.
2.9.12 SBCF boards (source: Restart requested by the active board)

Fault number 1060
Abis event reporting a hardware fault
Equipment:
SBCF
Source:
(6422564) Restart requested by the active board
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates a restart of an SBCF board has been requested by
the active board.
411-9001-104 18.05 2 February 2010
329
2.9.13 SBCF boards (source: Restart due to a software upgrade)

Fault number 1060
Equipment:
SBCF
Source:
(6422565) Restart due to a software upgrade
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates a restart of an SBCF board due to a software
upgrade.
2.9.14 SBCF boards (source: Restart due to hardware watchdog)

Fault number 1060
Equipment:
SBCF
Source:
(6422566) Restart due to a hardware watchdog
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates a restart of an SBCF board due to a hardware
watchdog.
2.9.15 SBCF boards (source: Restart due to double bus fault)

Fault number 1060
Equipment:
SBCF
Source:
(6422567) Restart due to a double bus fault
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates a restart of an SBCF board due to a double bus fault.
2.9.16 SBCF boards (source: restart due to Man Machine Interface I

and C reset button)
Fault number 1060
Equipment:

SBCF

411-9001-104 18.05 2 February 2010
330
Source:
(6422568) Restart due to a Man Machine Interface I

and C reset button
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates a restart of an SBCF board due to a Man machine
Interface Iand C reset button.

Fault number:
1061
Abis mapping issue for a TDMA
Type

Fault number:
1067
Type
equipmentAlarm
In the case of an equipment fault or a missing equipment item, the BTS

sends a 1067 message to the OMC-R through the BSC specifying the
faulty equipment and the source. In some cases, the BSC starts a defense
action (PCM switchover, TRX state change, reconfiguration of frequency
hopping laws, ...).
If there is one alarm, the type and position of the element are specified
in the alarm.
For more information on each source, see the indicated paragraph to know
the corrective maintenance procedure associated with this source.
Table 6
Equipment
ABIS BTS
SYNCHRO
Source No.
3342340
Paragraph
Source wording
SYNO clock not locked
on the network
2.11.1 ABIS_BTS_SYNCHRO
(source: SYNO clock not
locked on the network)
(S2000H BTS) (page 344)
2.11.2 ABIS_BTS_SYNCHRO
(source: SYNO clock not locked

411-9001-104 18.05 2 February 2010
Equipment
Source No.
331
Paragraph
Source wording
on the network) (S2000L

BTS) (page 349)
AC power supply
6619137
Power fault
Cabinet high
temperature alarm
7012353
Threshold exceeded
2.11.5 Cabinet high temperature

alarm (source: Threshold
exceeded) (page 360)
Cabinet low
temperature alarm
7077889
Threshold exceeded
2.11.6 Cabinet low temperature

alarm (source: Threshold
DC power supply
6684673
Power fault
2.11.7 DC power supply

(source: Power fault)
(S2000H BTS) (page 366)
2.11.8 DC power supply
(source: Power fault) (S2000L)
(page 369)
External alarm
8257537
External alarm
2.11.9 External alarm (source:

External alarm) (page 373)
9437185
RX fault
9437187
Loss of PCM link
9437190
BBFILTER ASIC FAULT
9437193
Self test failed
9437194
Major fault on TX
9437206
DRX link
DRX
2.11.3 AC power supply

(S2000H BTS) (page 354)
(source: Power fault) (S2000L
BTS) (page 357)
2.11.10 DRX (source: RX

fault) (page 373)
2.11.11 DRX (source: Loss of
PCM link) (page 376)
2.11.12 DRX (source:
BBFILTER ASIC fault)
(page 378)
2.11.13 DRX (source: Self test
failed) (page 381)
2.11.14 DRX (source:
Major fault on TX)
(S2000H BTS) (page 383)
2.11.15 DRX (source: Major
fault on TX) (S2000L BTS)
(page 386)
2.11.16 DRX (source: DRX
link) (S2000H BTS) (page 388)
2.11.17 DRX (source: DRX link)
(S2000L BTS) (page 391)

411-9001-104 18.05 2 February 2010
332
Equipment
Source No.
Paragraph
Source wording
9437216
The TX has not

acknowledged the
power consign request
2.11.18 DRX (source: The TX

has not acknowledged the power
consign request) (page 393)
9437217
PA DRX control loop

fault
2.11.19 DRX (source: PA

DRX control loop fault)
(S2000H BTS) (page 397)
2.11.20 DRX (source: PA DRX
control loop fault) (S2000L
BTS) (page 400)
DRX diversity
reception chain
6946817
Software detection
2.11.21 DRX diversity

reception chain (source:
Software detection)
(S2000H BTS) (page 403)
2.11.22 DRX diversity reception
chain (source: Software
detection) (S2000L BTS)
(page 405)
DRX main reception

chain
6881281
Software detection
2.11.23 DRX main

reception chain (source:
Software detection)
(S2000H BTS) (page 408)
2.11.24 DRX main reception
chain (source: Software
(page 410)
LNA
5570561
LNA fault
2.11.25 LNA (source:

Software detection)
(S2000H BTS) (page 412)
2.11.26 LNA (source: Software
(page 415)
PA
6815745
Hardware
2.11.27 PA (source: Hardware)

(S2000H BTS) (page 417)
(S2000L BTS) (page 419)
6815746
DRX/PA connection
2.11.29 PA (source:
DRX/PA connection)
(S2000H BTS) (page 421)
2.11.30 PA (source: DRX/PA
connection) (S2000L BTS)
(page 424)
6488065
PCM
2.11.31 PCM (source: PCM)

(page 426)
PCM

411-9001-104 18.05 2 February 2010
Equipment
Source No.
7798785
RX-splitter D
RX-splitter M
333
Paragraph
Source wording
Over current
2.11.32 RX splitter D
(source: Over current)
(S2000H BTS) (page 426)
2.11.33 RX splitter D (source:
Over current) (S2000L BTS)
(page 429)
Over current
2.11.34 RX splitter M
(S2000H BTS) (page 431)
2.11.35 RX splitter M (source:
(page 434)
2.11.36 Splitter output
(S2000H BTS) (page 436)
2.11.37 Splitter output (source:
(page 438)
Splitter output
7340033
Over current
Transmit antenna
6750209
VSWR
VGA (only for

S2000H BTS)
6029313
Fault on VGA
2.11.38 Transmit
antenna (source: VSWR)
(S2000H BTS) (page 441)
2.11.39 Transmit antenna
(source: VSWR) (S2000L
BTS) (page 443)
2.11.40 VGA (source: Fault on
VGA) (S2000H BTS) (page 446)
The red triangular icon of the I and C interface is ON, when an equipment
failure is detected on the BTS.
For the S2000L "FP" BTS, a fault on an element other than the "Battery
and Interface" module or the internal battery leads to the replacement of
one of the following elements:
the main module

the LPRF module
For the S2000L "EP" BTS, a fault on an element other than the "Battery
and Interface" module or the internal battery leads to the replacement of
the following element:
the base or extension module
For the S2000H "FP" BTS, a fault on an element other than the "Battery
and Interface" module leads to the replacement of one of the following
elements:

411-9001-104 18.05 2 February 2010
334
the main module

the RF supply module
the HPRF module
For the S2000H "EP" BTS, a fault on an element other than the "Battery
and Interface" module leads to the replacement of one of the following
elements:
the base or extension module

the HPRF module
The following tables indicate the cross-reference between the equipment

and the sheets for the S2000L BTS
Table 7
SBCF location
Equipment
type
Equipment
number
Cabinet
Paragraph
SBCF
BASE
Nortel GSM BTS S2000H/S2000L

Troubleshooting (411-9001-049)
Table 8
SALCO location
Equipment
type
Equipment
number
Cabinet
Paragraph
SALCO
EXTENSION

Table 9
PA location
Equipment
type
Equipment
number
Cabinet
Paragraph
PA
BASE
PA
BASE

PA
EXTENSION
PA
EXTENSION

(extension)

411-9001-104 18.05 2 February 2010
335
Table 10
LNA location
Equipment
type
Equipment
number
Cabinet
LNA
BASE
LNA
BASE
LNA
BASE
LNA
BASE
LNA
EXTENSION
LNA
EXTENSION
Paragraph
for S2000L EP or FP

Troubleshooting (411-9001-049) for
S2000L EP or FP (extension)
Table 11
PCM location
Equipment
type
Equipment
number
Cabinet
Paragraph
PCM
BASE
PCM
BASE

for S2000L EP or FP
Table 12
AC power supply location
Equipment
type
Equipment
number
Cabinet
Paragraph
AC POWER
SUPPLY
BASE

S2000L EP or FP
AC POWER
SUPPLY
EXTENSION

Table 13
DC power supply location
Equipment
type
Equipment
number
Cabinet
Paragraph
DC POWER
SUPPLY
BASE

S2000L EP or FP
DC POWER
SUPPLY
EXTENSION


411-9001-104 18.05 2 February 2010
336
Table 14
External contact location
Equipment
type
Equipment
number
Cabinet
Paragraph
External Contact
BASE
External Contact
BASE

for S2000L EP or FP
External Contact
BASE
External Contact
BASE
External Contact
BASE
External Contact
BASE
Table 15
DRX location
Equipment
type
Equipment
number
Cabinet
Paragraph
DRX
BASE
DRX
BASE

for S2000L EP or FP
DRX
EXTENSION
DRX
EXTENSION
Equipment
type
Equipment
number
Cabinet
Paragraph
Transmit
antenna
BASE
Transmit
antenna
BASE

for S2000L EP or FP
Transmit
antenna
EXTENSION
Transmit
antenna
EXTENSION

Table 16
Transmit antenna location


411-9001-104 18.05 2 February 2010
337
Table 17
Cabinet high temperature alarm location
Equipment
type
Equipment
number
Cabinet
Paragraph
Cabinet high
temperature
alarm
BASE

for S2000L EP or FP
Cabinet high
temperature
alarm
EXTENSION

Table 18
Cabinet low temperature alarm location
Equipment
type
Equipment
number
Cabinet
Paragraph
Cabinet low
temperature
alarm
BASE

for S2000L EP or FP
Cabinet low
temperature
alarm
EXTENSION

Paragraph
Table 19
DRX main reception chain location
Equipment
type
Equipment
number
Cabinet
DRX Main
reception chain
BASE
DRX Main
reception chain
BASE
DRX Main
reception chain
EXTENSION
DRX Main
reception chain
EXTENSION

for S2000L EP or FP

Table 20
DRX diversity reception chain location
Equipment
type
Equipment
number
Cabinet
DRX Diversity
reception chain
BASE
DRX Diversity
reception chain
BASE
Paragraph
for S2000L EP or FP

411-9001-104 18.05 2 February 2010
338
Table 20
DRX diversity reception chain location (contd.)
Equipment
type
Equipment
number
Cabinet
DRX Diversity
reception chain
EXTENSION
DRX Diversity
reception chain
EXTENSION
Paragraph
Table 21
SYN location
Equipment
type
Equipment
number
Cabinet
Paragraph
SYN
BASE

for S2000L EP or FP
Table 22
RX main connector location
Equipment
type
Equipment
number
Cabinet
Paragraph
RX main
connector
BASE
RX main
connector
BASE

S2000L EP or FP
RX main
connector
EXTENSION
RX main
connector
EXTENSION

Table 23
RX diversity connector location
Equipment
type
Equipment
number
Cabinet
RX diversity
connector
BASE
RX diversity
connector
BASE
RX diversity
connector
EXTENSION
RX diversity
connector
EXTENSION
Paragraph
for S2000L EP or FP


411-9001-104 18.05 2 February 2010
339

and the sheets for the S2000H BTS
Table 24
SBCF location
Equipment
type
Equipment
number
Cabinet
Paragraph
SBCF
BASE

for S2000H EP or FP
Table 25
SALCO location
Equipment
type
Equipment
number
Cabinet
Paragraph
SALCO
EXTENSION

S2000H EP or FP
Table 26
PA location
Equipment
type
Equipment
number
Cabinet
PA
High Power
Module 0 (BASE)
PA
High Power
Module 1 (BASE)
PA
High Power
Module 0 (EXTE
NSION)
PA
High Power
Module 1 (EXTE
NSION)
Equipment
type
Equipment
number
Cabinet
LNA
High Power
Module 0 (BASE)
LNA
High Power
Module 0 (BASE)
LNA
High Power
Module 1 (BASE)
Paragraph


(extension)
Table 27
LNA location
Paragraph


411-9001-104 18.05 2 February 2010
340
Equipment
type
Equipment
number
Cabinet
LNA
High Power
Module 1 (BASE)
LNA
High Power
Module 0
(EXTENSION)
LNA
High Power
Module 1
(EXTENSION)
Equipment
type
Equipment
number
Cabinet
Paragraph
VGA
BASE
VGA
BASE

for S2000H EP
VGA
EXTENSION
VGA
EXTENSION

S2000H EP (extension)
Equipment
type
Equipment
number
Cabinet
Paragraph
PCM
BASE

for S2000H EP or FP
PCM
BASE
Equipment
type
Equipment
number
Cabinet
Paragraph
AC POWER
SUPPLY
BASE

for S2000H EP or FP
AC POWER
SUPPLY
EXTENSION

Paragraph

(extension)
Table 28
VGA location
Table 29
PCM location
Table 30

411-9001-104 18.05 2 February 2010
341
Table 31
DC power supply location
Equipment
type
Equipment
number
Cabinet
Paragraph
DC POWER
SUPPLY
BASE
DC POWER
SUPPLY
EXTENSION

for S2000H EP or FP
Equipment
type
Equipment
number
Cabinet
Paragraph
External
Contact
BASE
External
Contact
BASE
External
Contact
BASE
External
Contact
BASE
External
Contact
BASE
External
Contact
BASE
Equipment
type
Equipment
number
Cabinet
Paragraph
DRX
BASE
DRX
BASE

for S2000H EP or FP
DRX
EXTENSION
DRX
EXTENSION
Table 32
External contact location

for S2000H EP or FP
Table 33
DRX location


411-9001-104 18.05 2 February 2010
342
Table 34
Transmit antenna location
Equipment
type
Equipment
number
Cabinet
Transmit antenna
High Power
Module 0 (BASE)
Transmit antenna
High Power
Module 1 (BASE)
Transmit antenna
High Power
Module 0
(EXTENSION)
Transmit antenna
High Power
Module 1
(EXTENSION)
Paragraph

Table 35
Cabinet high temperature alarm location
Equipment
type
Equipment
number
Cabinet
Paragraph
Cabinet high
temperature
alarm
BASE

for S2000H EP or FP
Cabinet high
temperature
alarm
EXTENSION

for S2000H EP
Table 36
Cabinet low temperature alarm location
Equipment
type
Equipment
number
Cabinet
Paragraph
Cabinet low
temperature
alarm
BASE

for S2000H EP or FP
Cabinet low
temperature
alarm
EXTENSION

for S2000H EP

411-9001-104 18.05 2 February 2010
343
Table 37
DRX main reception chain location
Equipment
type
Equipment
number
Cabinet
DRX Main
reception chain
BASE
DRX Main
reception chain
BASE
DRX Main
reception chain
EXTENSION
DRX Main
reception chain
EXTENSION
Paragraph

for S2000H EP or FP
Table 38
DRX diversity reception chain location
Equipment
type
Equipment
number
Cabinet
Paragraph
DRX Diversity
reception chain
BASE

for S2000H EP or FP
DRX Diversity
reception chain
BASE
DRX Diversity
reception chain
EXTENSION
DRX Diversity
reception chain
EXTENSION

for S2000H EP
Equipment
type
Equipment
number
Cabinet
Paragraph
SYN
BASE

for S2000H EP or FP
Table 39
SYN location

411-9001-104 18.05 2 February 2010
344
Table 40
RX main connector location
Equipment
type
Equipment
number
Cabinet
Paragraph
RX main
connector
BASE
RX main
connector
BASE

for S2000H EP or FP
RX main
connector
EXTENSION
RX main
connector
EXTENSION

for S2000H EP
Table 41
RX diversity connector location
Equipment
type
Equipment
number
Cabinet
Paragraph
RX diversity
connector
BASE
RX diversity
connector
BASE

for S2000H EP or FP
RX diversity
connector
EXTENSION
RX diversity
connector
EXTENSION

for S2000H EP
2.11.1 ABIS_BTS_SYNCHRO (source: SYNO clock not locked on the

network) (S2000H BTS)
Fault number 1067
Equipment:
ABIS_BTS_SYNCHRO
Source:
(3342340) SYNO clock not locked on the

network
BTS model:
S2000H
FAULT ANALYSIS
A BTS works on its internal clock and provides the other BTSs with it
through the PCM links.
This alarm indicates a problem on the clock of the radio cabinet: the value
of the reference clock of the synchronizing PCM is not in the admitted
interval.

411-9001-104 18.05 2 February 2010
345

BSC defense and impact on the service As long as the PCM link is
operational, there is not any BSC defense action.
If, in the notification the "impact" field is "non transparent for the BSC",
the BSC unconfigures the btsSiteManager object.
CAUTION
configuration.
If, in the notification the "impact" field is "transparent for the BSC", the
BSC does not anything.
CAUTION
A handover problem can appear between the BTS
concerned and its neighboring BTSs (S8000 or S80002
BTS, or BTS of another manufacturer).
TROUBLESHOOTING
Step
Action



see the fault number 1054 (see Nortel GSM BSS Fault
and treat the problem in order that the btsSiteManager
object becomes back "enabled".

"disabled-failed", the site is not operational. Do not treat the
alarm and do not clear it. Look for other alarms and treat the
problem in order that the btsSiteManager object becomes
back "enabled".

object is "disabled", do not treat the alarm and do not

411-9001-104 18.05 2 February 2010
346
clear it. Wait that the state of the btsSiteManager object

becomes back "enabled", "disabled-dependency", or
"disabled-failed".
Check the number of impacted sites.
the main module of the S2000H "FP" BTS. See Nortel GSM
BTS S2000H/S2000L Troubleshooting (411-9001-049). Go
to step 21.
the base or extension module of the S2000H "EP" BTS.

See Nortel GSM BTS S2000H/S2000L Troubleshooting
(411-9001-049). Go to step 21.
Perform a "Display dynamic data" command on the bsc object to

determine which TCU gives the clock to the network.
If the "synchronizing PCM" parameter is "synchro internal

clock", go to step 19.
If the "synchronizing PCM" parameter is not "synchro internal

Check the number of available TCUs.

If there is at least two available TCUs, go to step 6.
If there is only one TCU, go to step 7.
Perform a PCM Ater link switchover by setting the

administrativeState of the pcmCircuit object to "locked".
If several sites are impacted, go to step 4.
Replace:
If only one site is impacted, go to step 3.

Measure the frequency of the PCM A downlinks (with a PCM

analyzer).
If the frequency is correct, measure the frequency of the PCM

A uplinks.

411-9001-104 18.05 2 February 2010
347
If the frequency is not correct on all the PCM A links, go

to step 8.
If the frequency is not correct on one of the PCM A links,
go to step 9.
If the frequency is correct, the problem does not concern
the TCU but concerns the BSC. Go to step 12.
Replace the CEM board (Field Replaceable Unit) of the TCU

3000. see Nortel GSM BSC 3000/TCU 3000 Troubleshooting
(411-9001-132).
11
12

Replace the IEM board (Field Replaceable Unit) of the TCU

(411-9001-132).
10
If the frequency is not correct, the problem concerns the

MSC. Look for it and solve it. Then go to step 1.

Perform a "Display all" command on the transcoder object to

check the state of the TCU.
If the operationalState of the transcoder object is "enabled",

the problem concerns the BSC. Go to step 12.
If the operationalState of the transcoder object is "disabled",

go to step 11.
Perform a PCM A link switchover by setting the administrativeSta

te of the pcmCircuit object to "locked". Then perform a "Display
all" command on the transcoder object to check the state of the
TCU.

the problem concerns the TDTI board. Go to step 9.

perform the same operation twice: either the operationalState
of the transcoder object becomes "enabled", or the
operationalState of the transcoder object remains "disabled".
If the operationalState is "enabled", go to step 7. Otherwise
go to step 9.
Perform a "Display all" command on the bsc object to check the

correctness of the parameters of the passive chain.

411-9001-104 18.05 2 February 2010
348
13
14
Measure the frequency of the PCMs (with a PCM analyzer) on

the MSC side, on the BSC side and on the TCU side.
If the frequency of the PCM A link is correct and the

frequency of the PCM Ater link is correct, go to step 16.

frequency of the PCM Ater link is not correct, go to step 14.
If the frequency of the PCM A link is not correct, if it is the

downlink concerned, go to step 15, and if it is the uplink
concerned, go to step 14.
Replace the following items of equipment one after the other to

identify the faulty one.
a Replace the CEM board (Field Replaceable Unit) of the TCU
(411-9001-132).

If the alarm persists, go to step 14b.
b Remove the newly inserted CEM board and reinsert the old
CEM board. Then replace the IEM board (Field Replaceable
Unit) of the TCU 3000. see Nortel GSM BSC 3000/TCU 3000
Troubleshooting (411-9001-132).

15
The problem concerns the MSC. Solve it and then go to step 1.
16

the BSC side, on the TCU side and on the BTS side.
If the frequency of the PCM Abis link is correct and

the frequency of the PCM Ater link is correct, call the
transmission operator.
If the frequency of the PCM Abis link is not correct and the
frequency of the PCM Ater link is correct:
If it is the uplink concerned and if there is one BTS, go to
step 17.
If it is the uplink concerned and if there are several BTSs,
the problem concerns the PCMs. Call the transmission
operator.
If it is the downlink concerned, the problem concerns the
PCMs. Call the transmission operator.
If the frequency of the PCM Ater link is not correct:

411-9001-104 18.05 2 February 2010
349
If it is the uplink concerned, go to step 18.

17
Replace:
18
the main module of the S2000H "FP" BTS. see Nortel GSM
BTS S2000H/S2000L Troubleshooting (411-9001-049) Go
to step 20.

(411-9001-049) Go to step 20.
Replace the CEM board (Field Replaceable Unit) of the BSC

(411-9001-132).
19

Make a TCU operational.

As soon as a TCU is operational, go to step 5.
Additional checks
20
Check the alarm state in the "Current Alarm list" window.

21
Clear the alarm.
22

--End--
2.11.2 ABIS_BTS_SYNCHRO (source: SYNO clock not locked on the

network) (S2000L BTS)
Fault number 1067
Equipment:
ABIS_BTS_SYNCHRO
Source:
(3342340) SYNO clock not locked on the

network
BTS model:
S2000L
FAULT ANALYSIS
interval.
411-9001-104 18.05 2 February 2010
350

If, in the notification the impact is "non transparent for the BSC", the
BSC unconfigures the btsSiteManager object.
CAUTION
configuration.
If, in the notification the impact is "transparent for the BSC", the BSC
does not anything.
CAUTION
concerned and its neighboring BTSs (S8000 BTS, or BTS of
another manufacturer).
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".


411-9001-104 18.05 2 February 2010
351

"disabled-failed".
the main module of the S2000L "FP" BTS. see Nortel GSM
to step 4.
the base or extension module of the S2000L "EP" BTS.

(411-9001-049) Go to step 4.





administrativeState of the pcmCircuit object to "locked".
Replace:


analyzer).

411-9001-104 18.05 2 February 2010
352

A uplinks.
to step 8.
go to step 9.

(411-9001-132).
11


(411-9001-132).
10





go to step 11.

TCU.


do the same operation twice: either the operationalState
If the operationalState is "enabled", go to step 8step 7.


411-9001-104 18.05 2 February 2010
353
12

13

14

frequency of the PCM Ater link is correct, go to step 19step
17.

frequency of the PCM Ater link is not correct, go to step 14.

downlink concerned, go to step 18, and if it is the uplink
concerned, go to step 14.

(411-9001-132).


15
16



411-9001-104 18.05 2 February 2010
354

step 17.
operator.

17
18
Replace:
to step 4.

(411-9001-049) Go to step 4.
Replace the CEM board (Field Replaceable Unit) of the BSC

(411-9001-132).
19


Additional checks
20

21
Clear the alarm.
22

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

Fault number 1067
Equipment:

AC power supply

411-9001-104 18.05 2 February 2010
Source:
(6619137) Power fault
BTS model:
S2000H
355
FAULT ANALYSIS
The AC power supply has failed. Therefore, this failure indicates that the
battery is powering the BTS.
The power backup for an S2000H BTS is approximately 15 minutes at
25C with the "Battery and Interface" module.

BSC defense If the BTS operates on its battery, there is not any BSC
defense action.
When the battery is lost, the BSC unconfigures the btsSiteManager object.
CAUTION
When this alarm appears, the BTS operates with the "Battery
and Interface" module.
If there is no "Battery and Interface" module, the service is lost.
TROUBLESHOOTING
Preliminary checks
Step
Action



"disabled-dependency", the site is not operational. Look
for an object whose state is "disabled-failed" and treat the
back "enabled".
If no object is concerned and if a fault number 1054 (loss
of layer 2) has appeared:
If the cabinet is out of order, treat the problem on the

cabinet. Go to step 3.
Otherwise, see the fault number 1054 (see Nortel

(411-9001-105) ).
If a pcmCircuit object is "disabled-failed":

411-9001-104 18.05 2 February 2010
356

Look for a fault number concerning PCMs (see Nortel

(411-9001-105) ).


back "enabled".

"disabled-failed".
Check that the alarm on the equipment is valid, by performing

If the state of the "AC power supply" equipment is "failed", the

fault is confirmed. Go to step 4.
If the state of the "AC power supply" equipment is "working",

the fault is not confirmed. Go to step 9.
On-site maintenance
Check the mains power supply on the operator box, or on the

"Battery and Interface" module, if it is used.
If the mains power supply is correct, it is a PCM fault. see

the fault number 1054 (see Nortel GSM BSS Fault Clearing Advanced Maintenance (411-9001-105) ).
If not, solve the problem concerning the mains power supply

and go to step 7.
Check that the batteries are present.

411-9001-104 18.05 2 February 2010
357

If the mains power supply is correct, go to step 6.

and go to step 7.
Replace:
the RF supply module of the S2000H "FP" BTS. see Nortel

GSM BTS S2000H/S2000L Troubleshooting (411-9001-049)
Go to step 7.

(411-9001-049) Go to step 7.
Additional checks

Check the state of the equipment by performing a "Display

hardware configuration" command on the btsSitManager object.
If the state of the "AC power supply" equipment is still

"failed", call the manufacturer.

go to step 9.
Clear the alarm.
10

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

Fault number 1067
Equipment:
AC power supply
Source:
BTS model:
S2000L
FAULT ANALYSIS

411-9001-104 18.05 2 February 2010
358
The power backup for a S2000L BTS is approximately 15 minutes at 25C

with the internal battery.

defense action.
CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action



back "enabled".


(411-9001-105) ).


(411-9001-105) ).


411-9001-104 18.05 2 February 2010
359

back "enabled".

"disabled-failed".



On-site maintenance



and go to step 7.
Check that the internal batteries are present.


and go to step 7.
Replace:
411-9001-104 18.05 2 February 2010
360
to step 7.

(411-9001-049) Go to step 7.
Additional checks


hardware configuration" command on the btsSiteManager object.


go to step 9.
Clear the alarm.
10

--End--
2.11.5 Cabinet high temperature alarm (source: Threshold exceeded)

Fault number 1067
Equipment:
Cabinet high temperature alarm
Source:
(7012353) Threshold exceeded
BTS model:
S2000 H/L
FAULT ANALYSIS
The beginning of fault appears when the temperature is upper than 75C.
Then the DRX are switched off until the return to a normal temperature.
The end of fault appears when the temperature is lower than 70C. Then
the SBCF restarts the DRX and the DRX configuration.
BSC defense

411-9001-104 18.05 2 February 2010
361
When the DRX are switched off, the BSC unconfigures the associated
transceiverEquipment objects.
The BSC waits for the end of fault to perform the reconfiguration.
There is the loss of all the transceiverEquipment, bts, and transceiver
objects.
CAUTION
The service is reduced or lost depending on the configuration.
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".


411-9001-104 18.05 2 February 2010
362

"disabled-failed".

If the state of the "cabinet high temperature alarm" equipment

is "failed", the fault is confirmed. Go to step 3.

is "working", the fault is not confirmed. Go to step 6.
On-site maintenance
Control the environment to check if the alarm is normal or not:
If the alarm detection is normal, wait for the system to

return to a normal temperature. The cabinet will restart
automatically. Go to step 4.
If the alarm detection is not normal, replace:

the main module for the S2000L "FP" BTS. see
Nortel GSM BTS S2000H/S2000L Troubleshooting
(411-9001-049) Go to step 4.
the main module for the S2000H "FP" BTS. see
(411-9001-049) Go to step 4.
(411-9001-049) Go to step 4.
(411-9001-049) Go to step 4.
Additional checks



411-9001-104 18.05 2 February 2010
363

is still "failed", call the manufacturer.

is "working", go to step 6.
Clear the alarm.

--End--
2.11.6 Cabinet low temperature alarm (source: Threshold exceeded)

Fault number 1067
Equipment:
Cabinet low temperature alarm
Source:
BTS model:
S2000 H/L
FAULT ANALYSIS
The beginning of alarm appears when the temperature is lower than -15C.
Then the heaters are started and the DRX are switched off until the return
to a normal temperature.
The end of alarm appears when the temperature is upper than -10C. Then
the SBCF restarts the DRX and the DRX configuration.
BSC defense
When the DRX are switched off, the BSC unconfigures the associated
TRX on reception of the DRX link source.
The BSC waits for the end of fault of the DRX to perform the
reconfiguration.
There is the loss of all the transceiverEquipment, bts, and transceiver
objects.

411-9001-104 18.05 2 February 2010
364
CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".


411-9001-104 18.05 2 February 2010
365
If the state of the "cabinet low temperature alarm" equipment

is "failed", the fault is confirmed. Go to step 3.

is "working", the fault is not confirmed. Go to step 6.
On-site maintenance
Control the environment to check if the alarm is normal or not:
If the alarm detection is normal, wait for the system to

return to a normal temperature. The cabinet will restart
automatically. Go to step 4.
If the alarm detection is not normal, replace:

(411-9001-049) Go to step 4.
(411-9001-049) Go to step 4.
the base or extension module for the S2000L "EP" BTS.
(411-9001-049) Go to step 4.
the base or extension module for the S2000H "EP" BTS.
(411-9001-049) Go to step 4.
Additional checks



is still "failed", call the manufacturer.

is "working", go to step 6.
Clear the alarm.

--End--

411-9001-104 18.05 2 February 2010
366
2.11.7 DC power supply (source: Power fault) (S2000H BTS)

Fault number 1067
Equipment:
DC power supply
Source:
BTS model:
S2000H
FAULT ANALYSIS
The battery of the S2000H BTS is located in the "Battery and Interface"
module.
This alarm is an "OR" function of the 48V alarm and of the presence of the
battery temperature sensor.
If a DC power supply alarm occurs alone, there is a problem on the battery
of the "Battery and Interface" module.
If a DC power supply alarm occurs with an AC power supply alarm, the
BTS is running on its battery. This alarm indicates that AC power supply
has failed and the DC power supply has dropped below the charge
threshold of the battery (42 V).

defense action.
CAUTION
The DC power supply will be shutdown very shortly (maximum
30 seconds).
TROUBLESHOOTING
Preliminary checks
Step
Action


411-9001-104 18.05 2 February 2010


back "enabled".
367



(411-9001-105) ).


(411-9001-105) ).


back "enabled".

"disabled-failed".


411-9001-104 18.05 2 February 2010
368
If the state of the "DC power supply" equipment is "failed",

the fault is confirmed. Go to step 4.
If the state of the "DC power supply" equipment is "working",

On-site maintenance
Check if the "Power fault" source also appears on the "AC power
supply" equipment:
If it is case, the AC power distribution system is responsible.

The cabinet runs on the "Battery and Interface" module.
Solve the AC power supply problem. Go to step 9.
If not, it is a PCM fault. see the fault number 1054 (see

Nortel GSM BSS Fault Clearing - Advanced Maintenance
(411-9001-105) ).
supply" equipment:

If not, go to step 5.
Check the 48V voltage on the DC rail in the battery compartment

of the "Battery and Interface" module (between 8 and 13 points):
If the voltage is upper than 48V, check the battery

temperature sensor. Go to step 6.
If the voltage is below 48V, replace the battery of the

"Battery and Interface" module (with the associated
temperature sensor). see Nortel GSM BTS S2000H/S2000L
Troubleshooting (411-9001-049) Go to step 9.
Disconnect the "Battery and Interface" module (the cabinet runs

on AC power supply). Go to step 7.
Check the battery temperature sensor on the DC rail in the

battery compartment of the "Battery and Interface" module
(between 11 and 12 points):
If the value is approximately 2 k , go to step 8.

If the value is not approximately 2 k , replace the battery
of the "Battery and Interface" module (with the associated
Check the cable between the cabinet and the "Battery and
Interface" module.
411-9001-104 18.05 2 February 2010
369
If the cable is correct, replace:

(411-9001-049) Go to step 9.
the base or extension module for the S2000H "EP" BTS.
(411-9001-049) Go to step 9.
If the cable is not correct, replace it. Go to step 8.
Additional checks
10


If the state of the "DC power supply" equipment is still


go to step 11.
11
Clear the alarm.
12

--End--
2.11.8 DC power supply (source: Power fault) (S2000L)

Fault number 1067
Equipment:
DC power supply
Source:
BTS model:
S2000L
FAULT ANALYSIS
If a DC power supply alarm occurs alone, there is a problem on the battery
of the "Battery and Interface" module.
If a DC power supply alarm occurs with an AC power supply alarm, the
BTS is running on its battery. This alarm indicates that AC power supply
has failed and the DC power supply has dropped below the charge
threshold of the battery (42 V).

411-9001-104 18.05 2 February 2010
370

defense action.
CAUTION
The DC power supply will be shutdown very shortly (maximum
30 seconds).
TROUBLESHOOTING
Preliminary checks
Step
Action



back "enabled".


(411-9001-105) ).


(411-9001-105) ).


411-9001-104 18.05 2 February 2010
371

back "enabled".

"disabled-failed".

If the state of the "DC power supply" equipment is "failed",


On-site maintenance
supply" equipment:

If not, it is a PCM fault. see the fault number 1054 (see

Nortel GSM BSS Fault Clearing - Advanced Maintenance
(411-9001-105) ).
supply" equipment:

If not, go to step 5.

411-9001-104 18.05 2 February 2010
372
Check if a "Battery and Interface" module is present:
If there is no "Battery and Interface" module, replace:

the base or extension module for the S2000L "EP" BTS.
(411-9001-049) Go to step 10.
(411-9001-049) Go to step 10.
If there is a "Battery and Interface" module, go to step 6.
Check the 48V voltage on the DC rail in the battery compartment

of the "Battery and Interface" module (between 8 and 13 points):
If the voltage is upper than 48V, check the battery

temperature sensor. Go to step 7.
If the voltage is below 48V, replace the battery of the

"Battery and Interface" module (with the associated
Disconnect the "Battery and Interface" module (the cabinet runs

on AC power supply). Go to step 8.
Check the battery temperature sensor on the DC rail in the

battery compartment of the "Battery and Interface" module
(between 11 and 12 points):
If the value is approximately 2 k , go to step 9.

If the value is not approximately 2 k , replace the battery
of the "Battery and Interface" module (with the associated
Check the cable between the cabinet and the "Battery and
Interface" module.
If the cable is correct, replace:

the main module of the S2000L "FP" BTS. see
(411-9001-049) Go to step 10.
(411-9001-049) Go to step 10.
If the cable is not correct, replace it. Go to step 10.
Additional checks
10

411-9001-104 18.05 2 February 2010
11
373


If the state of the "DC power supply" equipment is still


go to step 12.
12
Clear the alarm.
13

--End--
2.11.9 External alarm (source: External alarm)

Fault number 1067
Equipment:
External alarm
Source:
(8257537) External alarm
BTS model:
S2000 H/L
If the alarm is external, the maintenance action depends on how the user
deals with the alarm. Six external alarms can be used for the base unit.
2.11.10 DRX (source: RX fault)

Equipment:
DRX
Source:
(9437185) RX fault
BTS model:
S2000 H/L
FAULT ANALYSIS
The DRX is not operational any more.
BSC defense
The BSC unconfigures the faulty DRX and the associated
transceiverEquipment object. It tries to assure a minimum service of

411-9001-104 18.05 2 February 2010
374

At least one DRX is lost.
CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".

411-9001-104 18.05 2 February 2010
375
Check that the alarm on the DRX module is valid, by

performing a "Display hardware configuration" command on the
If the state of the "DRX" equipment is "failed", the fault is

If the state of the "DRX" equipment is "working", the fault is

not confirmed. Go to step 8.
Set the administrativeState of the transceiverEquipment object

corresponding to the faulty DRX to "locked".
Replace:
to step 5.
to step 5.

(411-9001-049) Go to step 5.

(411-9001-049) Go to step 5.
Additional checks

corresponding to the faulty DRX to "unlocked".

Check the state of the DRX module by performing a "Display

If the state of the "DRX" equipment is still "failed", call the

manufacturer.
If the state of the "DRX" equipment is "working", go to step 8.
Clear the alarm.

411-9001-104 18.05 2 February 2010
376

--End--
2.11.11 DRX (source: Loss of PCM link)

Fault number 1067
Equipment:
DRX
Source:
(9437187) Loss of PCM link
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates that the DRX has not found the synchronization bits.
BSC defense
The BSC unconfigures the faulty DRX and the associated transceiver and
transceiverEquipment objects. It tries to assure a minimum service of
CAUTION
The service is reduced or lost, depending on the configuration.
TROUBLESHOOTING
Preliminary checks
Step
Action




411-9001-104 18.05 2 February 2010
377


back "enabled".

"disabled-failed".




CAUTION
Service reduction
In most cases, the TRX and one TDMA are lost.
Replace:

411-9001-104 18.05 2 February 2010
378
to step 5.
to step 5.

(411-9001-049) Go to step 5.

(411-9001-049) Go to step 5.
Additional checks



hardware configuration" command on the transceiverEquipment
object.

manufacturer.
Clear the alarm.

--End--
2.11.12 DRX (source: BBFILTER ASIC fault)

Equipment:
DRX
Source:
(9437190) BBFILTER ASIC fault
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates a hardware problem.

411-9001-104 18.05 2 February 2010
379

BSC defense
communication by unconfiguring and reconfiguring the transceiver.
CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".


411-9001-104 18.05 2 February 2010
380

"disabled-failed".

btsSiteManager object



Replace:
to step 5.
to step 5.

(411-9001-049) Go to step 5.

(411-9001-049) Go to step 5.
Additional checks




411-9001-104 18.05 2 February 2010
381

manufacturer.
Clear the alarm.

--End--
2.11.13 DRX (source: Self test failed)

Equipment:
DRX
Source:
(9437193) Self test failed
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates a problem in the hardware self-tests of the DRX.
BSC defense
CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action

411-9001-104 18.05 2 February 2010
382



back "enabled".

"disabled-failed".

btsSiteManager object



Replace:

411-9001-104 18.05 2 February 2010
383
to step 5.
to step 5.

(411-9001-049) Go to step 5.

(411-9001-049) Go to step 5.
Additional checks




manufacturer.
Clear the alarm.

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

Fault number 1067
Equipment:
DRX
Source:
(9437194) Major fault on TX
BTS model:
S2000H
FAULT ANALYSIS
This alarm indicates a problem on the DRX.

411-9001-104 18.05 2 February 2010
384

BSC defense The BSC unconfigures the faulty DRX and the associated
transceiver and transceiverEquipment objects. It tries to assure a
minimum service of communication by unconfiguring and reconfiguring
the transceiver object.
Impact on the service At least one DRX is lost, but it is possible to lose
the whole cell linked to the faulty DRX.
CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".


411-9001-104 18.05 2 February 2010
385

"disabled-failed".
Check that the alarm on the DRX module is valid by performing




Check the connection between the base or extension module

and the HPRF module.
If the connection is correct, go to step 5.

If not, replace it. Go to step 7.
Replace:
to step 7.

(411-9001-049) Go to step 7.
Replace the HPRF module. see Nortel GSM BTS

S2000H/S2000L Troubleshooting (411-9001-049) Go to step 9.
Additional checks

Check the alarm state:

If the alarm persists, set the administrativeState of the
transceiverEquipment object corresponding to the faulty DRX
to "locked" and go to step 6.

411-9001-104 18.05 2 February 2010
386

corresponding to the faulty DRX to "unlocked". Then check the
alarm state in the "Current Alarm list" window.
10



manufacturer.
If the state of the "DRX" equipment is "working", go to step

11.
11
Clear the alarm.
12

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

Fault number 1067
Equipment:
DRX
Source:
BTS model:
S2000L
FAULT ANALYSIS
This alarm indicates a problem on the DRX.

CAUTION

411-9001-104 18.05 2 February 2010
387
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".
Check that the alarm on the DRX module is valid by performing




411-9001-104 18.05 2 February 2010
388


Check the connection between the main module and the LPRF
module (S2000L "FP").

Replace:
the LPRF module of the S2000L "FP" BTS. see Nortel GSM
to step 6.

(411-9001-049) Go to step 6.
Additional checks



If the state of the "DRX" equipment is still"failed", call the

manufacturer.
Clear the alarm.
10

--End--
2.11.16 DRX (source: DRX link) (S2000H BTS)

Equipment:
DRX
Source:
(9437206) DRX link
BTS model:
S2000H

411-9001-104 18.05 2 February 2010
389
FAULT ANALYSIS
This alarm indicates that the SBCF has detected the loss or the
nonestablishment of the dialog box with the DRX.

CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".


411-9001-104 18.05 2 February 2010
390

"disabled-failed".




Replace:

(411-9001-049) Go to step 5.
to step 5.
Additional checks



object.

manufacturer.

411-9001-104 18.05 2 February 2010
Clear the alarm.
391
--End--
2.11.17 DRX (source: DRX link) (S2000L BTS)

Fault number 1067
Equipment:
DRX
Source:
(9437206) DRX link
BTS model:
S2000L
FAULT ANALYSIS
This alarm indicates that the SBCF has detected the loss or the
nonestablishment of the dialog box with the DRX.

CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action




411-9001-104 18.05 2 February 2010
392


back "enabled".

"disabled-failed".




Replace:
to step 5.

(411-9001-049) Go to step 5.

411-9001-104 18.05 2 February 2010
393
Additional checks




manufacturer.
Clear the alarm.

--End--
2.11.18 DRX (source: The TX has not acknowledged the power consign
request)
Fault number 1067
Equipment:
DRX
Source:
(9437216) The TX has not acknowledged the power

consign request
BTS model:
S2000 H/L
FAULT ANALYSIS
This alarm indicates that the power, configured at the OMC-R for the DRX
concerned, is not compatible with the DRX hardware.
BSC defense

411-9001-104 18.05 2 February 2010
394
CAUTION
Service reduction
It is possible to lose the whole cell linked to the faulty DRX. So
the service is reduced.
CAUTION
The intervention on the site must be immediate: there is a risk of
service loss .
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".

411-9001-104 18.05 2 February 2010
395






The value of the "bsTxPwrMax" parameter added to the value
to the attenuation of the duplexer must be between 31dBm and
44dBm for the S2000H and between 23dBm and 36dBm for the
S2000L.
The following table lists the correct values of the "bsTxPwrMax"
parameter. The "Nack" value is not allowed.
If the value is correct, replace:

(411-9001-049) Go to step 6.
the main module of the S2000H "FP" BTS. see
(411-9001-049) Go to step 6.

411-9001-104 18.05 2 February 2010
396

(411-9001-049) Go to step 6.
(411-9001-049) Go to step 6.
If the value is not correct, modify it according the following

table. Go to step 6.
Coupling system
Duplexer
Duplexer
DLU attenuation
0 (S2000H)
1 (S2000L)
51 143
Nack
Nack
44
Pmax
Nack
43
Pmax
Nack
42
Pmax-2
Nack
41
Pmax-2
Nack
40
Pmax-4
Nack
39
Pmax-4
Nack
38
Pmax-6
Nack
37
Pmax-6
Nack
36
Pmax-8
Pmax
35
Pmax-8
Pmax
34
Pmax-10
Pmax-2
33
Pmax-10
Pmax-2
32
Pmax-12
Pmax-4
31
Pmax-12
Pmax-4
30
Nack
Pmax-6
29
Nack
Pmax-6
28
Nack
Pmax-8
27
Nack
Pmax-8
26
Nack
Pmax-10
25
Nack
Pmax-10
24
Nack
Pmax-12
23
Nack
Pmax-12
22 0
Nack
Nack
bsTxPwrMax


411-9001-104 18.05 2 February 2010
397

the attenuation of the duplexer and reduced of the value of the
44dBm for the S2000H and between 23dBm and 36dBm for the
S2000L.
"bsTxPwrMax" parameter. The "Nack" value is not admitted.
However, do not forget to consider the "transceiver zone Ref"
parameter.
If the value is correct, replace:

(411-9001-049) Go to step 6.
the main module of the S2000H "FP" BTS. see
(411-9001-049) Go to step 6.
(411-9001-049) Go to step 6.
(411-9001-049) Go to step 6.
If the value is not correct, modify it according the following

table. Go to step 6.
Additional checks
Clear the alarm, if necessary.

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

Fault number 1067
Equipment:

DRX

411-9001-104 18.05 2 February 2010
398
Source:
(9437217) PA DRX control loop fault
BTS model:
S2000H
FAULT ANALYSIS
This alarm indicates that the DRX has not succeeded in the PA emission
power configuration with the DRX/PA control loop.

CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".


411-9001-104 18.05 2 February 2010
399

"disabled-failed".




corresponding to the faulty DRX to "locked". Go to step 4.
CAUTION
Service reduction
In most cases, the transceiver and one
transceiverEquipment objets are lost.


Replace:
to step 7.

(411-9001-049) Go to step 7.


411-9001-104 18.05 2 February 2010
400

Additional checks


transceiverEquipment object corresponding to the faulty DRX

corresponding to the faulty DRX to "unlocked". Then check the
10



manufacturer.
If the state of the "DRX" equipment is "working", go to step

11.
11
Clear the alarm.
12

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

Fault number 1067
Equipment:
DRX
Source:
BTS model:
S2000L
FAULT ANALYSIS
This alarm indicates that the DRX has not succeeded in the PA emission
power configuration with the DRX/PA control loop.


411-9001-104 18.05 2 February 2010
401
CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".

411-9001-104 18.05 2 February 2010
402




corresponding to the faulty DRX to "locked". Go to step 4.
CAUTION
Service reduction
In most cases, the transceiver and transceiverEquipm
ent objects are lost.
Check the connection between the base module and the LPRF
module (S2000L "FP" BTS only).

Replace:
to step 6.

(411-9001-049) Go to step 6.
Additional checks




manufacturer.

411-9001-104 18.05 2 February 2010
Clear the alarm.
10

--End--
2.11.21 DRX diversity reception chain (source: Software detection)

(S2000H BTS)
Fault number 1067
Equipment:
DRX diversity reception chain
Source:
(6946817) Software detection
BTS model:
S2000H
FAULT ANALYSIS
The DRX software (= the BTS) has detected a fault in the DRX main
reception chain.
An algorithm based on a function with the following parameters:
the level difference between the two chains

the number of busy TCH channels
the time
performs a mutual supervision of the two reception chains.

BSC defense None
ATTENTION
TROUBLESHOOTING
Preliminary checks
Step
Action




411-9001-104 18.05 2 February 2010
403
404


back "enabled".

"disabled-failed".
Check that the alarm on the "drx diversity reception chain"

equipment is valid, by performing a "Display hardware
configuration" command on the btsSiteManager object.
If the state of the "drx diversity reception chain" equipment is

"failed", the fault is confirmed. Go to step 3.

"working", the fault is not confirmed. Go to step 8.
On-site maintenance
Check the RF cable between the HPRF module and the RF

supply module.
Otherwise, replace it. Go to step 6.
Check the antenna connection on the faulty chain.
If the cable is correct, go to step 4.

If the connection is not correct, replace it. Go to step 6.
Replace:
411-9001-104 18.05 2 February 2010
405

Go to step 6.

(411-9001-049) Go to step 6.
Additional checks


object.

still "failed", call the manufacturer.

"working", go to step 8.
Clear the alarm.

--End--
2.11.22 DRX diversity reception chain (source: Software detection)

(S2000L BTS)
Fault number 1067
Equipment:
DRX diversity reception chain
Source:
BTS model:
S2000L
FAULT ANALYSIS
reception chain.

the time

411-9001-104 18.05 2 February 2010
406

BSC defense None
ATTENTION
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".

411-9001-104 18.05 2 February 2010
407
Check that the alarm on the "drx diversity reception chain"

configuration" command on the transceiverEquipment object.


On-site maintenance

Replace:
to step 5.

(411-9001-049) Go to step 5.
Additional checks



still "failed", call the manufacturer.

Clear the alarm.

--End--

411-9001-104 18.05 2 February 2010
408
2.11.23 DRX main reception chain (source: Software detection)

(S2000H BTS)
Fault number 1067
Equipment:
DRX main reception chain
Source:
BTS model:
S2000H
FAULT ANALYSIS
reception chain.

the time

BSC defense None
ATTENTION
TROUBLESHOOTING
Preliminary checks
Step
Action





411-9001-104 18.05 2 February 2010
409
back "enabled".

"disabled-failed".
Check that the alarm on the "drx main reception chain" module
is valid, by performing a "Display hardware configuration"
If the state of the "drx main reception chain" equipment is


On-site maintenance
Check the RF cable between the HPRF module and the RF

supply module.
Otherwise, replace it. Go to step 6.
If the cable is correct, go to step 4.

If the connection is not correct, replace it. Go to step 6.
Replace:

Go to step 6.

(411-9001-049) Go to step 6.

411-9001-104 18.05 2 February 2010
410

Additional checks


object.
If the state of the "drx main reception chain" equipment is still


Clear the alarm.

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

BTS)
Fault number 1067
Equipment:
DRX main reception chain
Source:
BTS model:
S2000L
FAULT ANALYSIS
reception chain.

the time

BSC defense None

411-9001-104 18.05 2 February 2010
411
ATTENTION
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".
Check that the alarm on the "drx main reception chain"


411-9001-104 18.05 2 February 2010
412


On-site maintenance

Replace:
to step 5.

(411-9001-049) Go to step 5.
Additional checks

Check the state of the "drx main reception chain" equipment by

If the state of the "drx main reception chain" equipment is still


Clear the alarm.

--End--
2.11.25 LNA (source: Software detection) (S2000H BTS)

Fault number 1067
Equipment:

LNA

411-9001-104 18.05 2 February 2010
Source:
(5570561) LNA fault
BTS model:
S2000H
413
FAULT ANALYSIS
This alarm indicates a hardware problem on the low noise amplifier. The
related reception path (main or diversity) is not operational any more for all
the DRX using the faulty LNA. However all these DRX run in a degraded
mode if the other path is still correct.

BSC defense The BSC unconfigures the transceiverEquipment objects
corresponding to the faulty LNA. One or several transceiverEquipment
objects can be lost.
ATTENTION
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".


411-9001-104 18.05 2 February 2010
414

"disabled-failed".
Check that the alarm on the LNA is valid, by performing

If the state of the "LNA" equipment is "failed", the fault is

If the state of the "LNA" equipment is "working", the fault is

Set the administrativeState of the transceiver and

transceiverEquipment objects to "locked".


transceiverEquipment objects to "unlocked". Go to step 6.
Additional checks


If the state of the "LNA" equipment is still "failed", call the

manufacturer.
If the state of the "LNA" equipment is "working", go to step 8.
Clear the alarm.

--End--

411-9001-104 18.05 2 February 2010
415
2.11.26 LNA (source: Software detection) (S2000L BTS)

Fault number 1067
Abis event reporting a hardware

fault
Equipment:
LNA
Source:
(5570561) LNA fault
BTS model:
S2000L
FAULT ANALYSIS
This alarm indicates a hardware problem on the low noise amplifier. The
related reception path (main or diversity) is not operational any more for all
the DRX using the faulty LNA. However all these DRX run in a degraded
mode if the other path is still correct.

corresponding to the faulty LNA. One or several transceiverEquipment
objects can be lost.
ATTENTION
TROUBLESHOOTING
Preliminary checks
Step
Action





411-9001-104 18.05 2 February 2010
416

back "enabled".

"disabled-failed".
Check that the alarm on the LNA is valid, by performing

If the state of the "LNA" equipment is "failed", the fault is

If the state of the "LNA" equipment is "working", the fault is


transceiverEquipment objects to "locked".
Replace:
to step 5.

(411-9001-049) Go to step 5.
Additional checks

transceiverEquipment objects to "unlocked". Go to step 6.


411-9001-104 18.05 2 February 2010
417
If the state of the "LNA" equipment is still "failed", call the

manufacturer.
If the state of the "LNA" equipment is "working", go to step 8.
Clear the alarm.

--End--
2.11.27 PA (source: Hardware) (S2000H BTS)

Fault number 1067
Equipment:
PA
Source:
(6815745) Hardware
BTS model:
S2000H
FAULT ANALYSIS
This alarm indicates a hardware failure of the PA. The corresponding DRX
is not operational any more.

BSC defense The BSC unconfigures the transceiverEquipment object
using the faulty PA, at least one transceiver object so one bts object.
ATTENTION
TROUBLESHOOTING
Preliminary checks
Step
Action




411-9001-104 18.05 2 February 2010
418


back "enabled".

"disabled-failed".
Check that the alarm on the PA is valid, by performing a "Display

If the state of the "PA" equipment is "failed", the fault is

If the state of the "PA" equipment is "working", the fault is not

Set the administrativeState of the transceiverEquipment object,

corresponding to the faulty PA, to "locked".


corresponding to the faulty PA, to "unlocked". Go to step 6.
Additional checks


411-9001-104 18.05 2 February 2010
419
Check the state of the PA by performing a "Display hardware

If the state of the "PA" equipment is still "failed", call the

manufacturer.
If the state of the "PA" equipment is "working", go to step 8.
Clear the alarm.

--End--
2.11.28 PA (source: Hardware) (S2000L BTS)

Fault number 1067
Equipment:
PA
Source:
(6815745) Hardware
BTS model:
S2000L
FAULT ANALYSIS
This alarm indicates a hardware failure of the PA. The corresponding DRX
is not operational any more.

ATTENTION
TROUBLESHOOTING
Preliminary checks
Step
Action




411-9001-104 18.05 2 February 2010
420


back "enabled".

"disabled-failed".




corresponding to the faulty PA, to "locked".
Replace:
to step 5.

(411-9001-049) Go to step 5.

411-9001-104 18.05 2 February 2010
421

corresponding to the faulty PA, to "unlocked". Go to step 6.
Additional checks

Check the state of the PA by performing a "Display hardware


manufacturer.
Clear the alarm.

--End--
2.11.29 PA (source: DRX/PA connection) (S2000H BTS)

Fault number 1067
Equipment:
PA
Source:
(6815746) DRX/PA connection
BTS model:
S2000H
FAULT ANALYSIS
This alarm indicates that the numeric link is out of use between the DRX
and the PA. The TRX is not operational any more.

CAUTION

411-9001-104 18.05 2 February 2010
422
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".




411-9001-104 18.05 2 February 2010
423

corresponding to the faulty PA to "locked".


Replace:
to step 7.

(411-9001-049) Go to step 7.

Additional checks

corresponding to the faulty PA to "unlocked". Go to step 8.
11

transceiverEquipment object corresponding to the faulty PA

corresponding to the faulty PA to "unlocked". Then check the
10

Check the state of the PA module by performing a "Display


manufacturer.
Clear the alarm.

411-9001-104 18.05 2 February 2010
424
12

--End--
2.11.30 PA (source: DRX/PA connection) (S2000L BTS)

Fault number 1067
Equipment:
PA
Source:
(6815746) DRX/PA connection
BTS model:
S2000L
FAULT ANALYSIS
This alarm indicates that the numeric link is out of use between the DRX
and the PA. The TRX is not operational any more.

CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action





411-9001-104 18.05 2 February 2010
425

back "enabled".

"disabled-failed".




corresponding to the faulty PA to "locked".
Check the cable connection between the main module and the
LPRF module, if possible.

Replace:
to step 6.

(411-9001-049) Go to step 6.
Additional checks

corresponding to the faulty PA to "unlocked". Go to step 7.

411-9001-104 18.05 2 February 2010
426

Check the state of the PA module by performing a "Display

object.

manufacturer.
Clear the alarm.
10

--End--

Fault number 1067
Equipment:
PCM
Source:
(6488065) PCM
BTS model:
S2000 H/L
This alarm can indicate a manual action on the PCM links (lock/unlock
when the BTS is connected to a BSC 3000).
This alarm can also be associated with a PCM fault. see Nortel GSM BSS
Fault Clearing - Advanced Maintenance (411-9001-105) .
2.11.32 RX splitter D (source: Over current) (S2000H BTS)

Fault number 1067
Equipment:
RX splitter D
Source:
(7798785) Over current
BTS model:
S2000H
FAULT ANALYSIS
This alarm corresponds to a fault in the reception amplifier of the diversity
path, located in the Rx-splitter. A current overconsumption has been
detected on the diversity path. It may be due to a hardware problem on
the cable.

BSC defense None.

411-9001-104 18.05 2 February 2010
427
None.
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".
Check that the alarm on the Rx-splitter D is valid, by


411-9001-104 18.05 2 February 2010
428
If the state of the "splitter output" equipment is "failed", the

If the state of the "splitter output" equipment is "working", the

fault is not confirmed. Go to step 11.

to "locked".


Replace:
to step 7.

(411-9001-049) Go to step 7.

Additional checks
Set the administrativeState of the transceiverEquipment object to

"unlocked". Go to step 8.

transceiverEquipment object to "locked" and go to step 6.

to "unlocked".Then check the alarm state in the "Current Alarm
list" window.
10

Check the state of the RX-splitter D module by performing


411-9001-104 18.05 2 February 2010
429
If the state of the "splitter output" equipment is still "failed",

If the state of the "splitter output" equipment is "working", go

to step 11.
11
Clear the alarm.
12

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

Fault number 1067
Equipment:
RX splitter D
Source:
BTS model:
S2000L
FAULT ANALYSIS
This alarm corresponds to a fault in the reception amplifier of the diversity
detected on the diversity path. It may be due to a hardware problem on
the cable.

BSC defense None.
None.
TROUBLESHOOTING
Preliminary checks
Step
Action




411-9001-104 18.05 2 February 2010
430


back "enabled".

"disabled-failed".
Check that the alarm on the Rx-splitter D is valid, by




to "locked".
LPRF module (S2000L "FP" BTS only).

Replace:

411-9001-104 18.05 2 February 2010
431
to step 6.

(411-9001-049) Go to step 6.
Additional checks


Check the state of the RX-splitter D module by performing



to step 9.
Clear the alarm.
10

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

Fault number 1067
Equipment:
RX splitter M
Source:
BTS model:
S2000H
FAULT ANALYSIS
This alarm corresponds to a fault in the reception amplifier of the main
detected on the main path. It may be due to a hardware problem on the
cable.

BSC defense None.
None.

411-9001-104 18.05 2 February 2010
432
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".
Check that the alarm on the Rx-splitter M is valid, by




411-9001-104 18.05 2 February 2010
433

to "locked".


Replace:
to step 7.

(411-9001-049) Go to step 7.

Additional checks

11


to "unlocked". Then check the alarm state in the "Current Alarm
list" window.
10

Check the state of the RX-splitter M module by performing



to step 11.
Clear the alarm.

411-9001-104 18.05 2 February 2010
434
12

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

Fault number 1067
Equipment:
RX splitter M
Source:
BTS model:
S2000L
FAULT ANALYSIS
cable.

BSC defense None.
None.
TROUBLESHOOTING
Preliminary checks
Step
Action





411-9001-104 18.05 2 February 2010
435

back "enabled".

"disabled-failed".
Check that the alarm on the Rx-splitter M is valid, by




to "locked".
LPRF module (S2000L "FP" BTS only).

If not, replace it. go to step 6.
Replace:
to step 6.

(411-9001-049) Go to step 6.
Additional checks


411-9001-104 18.05 2 February 2010
436




to step 9.
Clear the alarm.
10

--End--
2.11.36 Splitter output (source: Over current) (S2000H BTS)

Fault number 1067
Equipment:
Splitter output
Source:
BTS model:
S2000H
FAULT ANALYSIS
cable.

BSC defense None.
None.
TROUBLESHOOTING
Preliminary checks
Step
Action


411-9001-104 18.05 2 February 2010


437


back "enabled".

"disabled-failed".
Check that the alarm is valid, by performing a "Display hardware




to "locked".



411-9001-104 18.05 2 February 2010
438
Replace:
to step 7.

(411-9001-049) Go to step 7.

Additional checks



to "unlocked". Then check the alarm state in the "Current Alarm
list" window.
10

Check the state of the module by performing a "Display



to step 11.
11
Clear the alarm.
12

--End--
2.11.37 Splitter output (source: Over current) (S2000L BTS)

Fault number 1067
Equipment:
Splitter output
Source:
BTS model:
S2000L

411-9001-104 18.05 2 February 2010
439
FAULT ANALYSIS
cable.

BSC defense None.
None.
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".

411-9001-104 18.05 2 February 2010
440




to "locked".
LPRF module, if possible.

Replace:

(411-9001-049) Go to step 6.
to step 6.
Additional checks





to step 9.
Clear the alarm.

411-9001-104 18.05 2 February 2010
10
441

--End--
2.11.38 Transmit antenna (source: VSWR) (S2000H BTS)

Fault number 1067
Equipment:
Transmit antenna
Source:
(6750209) VSWR
BTS model:
S2000H
FAULT ANALYSIS
This alarm indicates that the radio link has been interrupted in the
transmission direction for all the DRX using the corresponding antenna. So
these DRX are not operational any more.

corresponding to the antenna.
CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action





411-9001-104 18.05 2 February 2010
442
back "enabled".

"disabled-failed".
Check that the alarm on the antenna is valid, by performing

If the state of the "transmit antenna" equipment is "failed", the

If the state of the "transmit antenna" equipment is "working",

On-site maintenance

to "locked".
Check the connection between the antenna and the HPRF

module indicated in the alarm.

If not, replace it. go to step 6.

S2000H/S2000L Troubleshooting (411-9001-049) Go to step 6
Additional checks



411-9001-104 18.05 2 February 2010
443
Check the state of the antenna by performing a "Display

If the state of the "transmit antenna" equipment is still "failed",


go to step 9.
Clear the alarm.
10
Perform a transmission test:
11
Set the administrativeState of the transceiverEquipment

objects to "locked".
Configure in emission the DRX corresponding to the antenna.

Use the TIL to perform an emission test (reflected power =
6W).

--End--
2.11.39 Transmit antenna (source: VSWR) (S2000L BTS)

Fault number 1067
Equipment:
Transmit antenna
Source:
(6750209) VSWR
BTS model:
S2000L
FAULT ANALYSIS
This alarm indicates that the radio link has been interrupted in the
transmission direction for all the DRX using the corresponding antenna. So
these DRX are not operational any more.

corresponding to the antenna.
CAUTION

411-9001-104 18.05 2 February 2010
444
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".
Check that the alarm on the antenna is valid, by performing

If the state of the "transmit antenna" equipment is "failed", the



411-9001-104 18.05 2 February 2010
445

to "locked".
Check the connection between the antenna and the LPRF

module indicated in the alarm (S2000L "FP" BTS only).

Replace:
to step 6.

(411-9001-049) Go to step 6.
Additional checks


Check the state of the antenna by performing a "Display

If the state of the "transmit antenna" equipment is still "failed",


go to step 9.
Clear the alarm.
10
Perform a transmission test:
Set the administrativeState of the transceiverEquipment

objects to "locked".
Configure in transmission the DRX corresponding to the

antenna.
Use the TIL to perform an transmission test (reflected power

= 1.2W).

411-9001-104 18.05 2 February 2010
446
11

--End--
2.11.40 VGA (source: Fault on VGA) (S2000H BTS)

Fault number 1067
Equipment:
VGA
Source:
(6029313) Fault on VGA
BTS model:
S2000H
FAULT ANALYSIS
This alarm indicates a hardware problem on the VGA. The related
reception path (main or diversity) is not operational any more for all the
DRX using the faulty VGA. However, if the path is still correct, all the DRX
run in a degraded mode.

corresponding to the faulty VGA.
CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action




411-9001-104 18.05 2 February 2010
447

back "enabled".

"disabled-failed".
Check that the alarm on the VGA is valid, by performing

If the state of the "VGA" equipment is "failed", the fault is

If the state of the "VGA" equipment is "working", the fault is

On-site maintenance

to "locked".
Replace:

(411-9001-049) Go to step 5.
the RF supply module for the S2000H "FP" BTS. see Nortel
Go to step 5.
Additional checks



411-9001-104 18.05 2 February 2010
448
Check the state of the VGA by performing a "Display hardware

If the state of the "VGA" equipment is still "failed", call the

manufacturer.
If the state of the "VGA" equipment is "working", go to step 8.
Clear the alarm.

--End--

Fault number:
1070
TRX synchronization failure
Type
equipmentAlarm

Fault number:
1073
Attempt of download failure on a GSM entity
Type
communicationsAlarm
FAULT ANALYSIS
This notification, issued by the BSC, appears when the downloading of
a new software release has failed.
When the downloading is successful, the site or the DRX requests

a reset of the entity by the BSC (reception by the BSC of a LOAD
READY NACK, issued by the BTS). The fault number 1073 is issued
alone after reception of this LOAD READY NACK. The BTS is
operational.
When the downloading is not successful (error in a file), the

downloading stops and another downloading is performed
automatically. The downloading starts from scratch.

411-9001-104 18.05 2 February 2010
449
Each time the downloading fails again, the fault number 1073 is
issued.
After four failed attempts (and four fault numbers 1073 issued), a
new downloading starts. If it fails, the fault number 1052 is issued
alone.
Table 42
source
No.
Paragraph
Source wording
Bad hardware reference or manufacturer ID
No change to one of BOOT after reset
This entity is engaged in another downloading
File access error
Repetitive errors (NACK, timeout, ...) while

downloading a file

downloadable TEI
No response to LOAD message
10
Received LOAD INIT NACK
11
Received message LOAD DATA NACK
2.13.3 Source 11: Received

message LOAD DATA NACK
(page 450)
12
Received message LOAD END NACK

message LOAD END NACK
(page 450)
13
Received message

message (page 450)
2.13.1 Source 9: No response to

LOAD message (page 450)
2.13.2 Source 10: Received LOAD
INIT NACK (page 450)

BSC defense
None.
None.

411-9001-104 18.05 2 February 2010
450
2.13.1 Source 9: No response to LOAD message

Fault number 1073 : Attempt of download failure on a GSM entity
Source:
(9) No response to LOAD message
BTS model:
S2000 H/L
2.13.2 Source 10: Received LOAD INIT NACK

Source:
(10) Received LOAD INIT NACK
BTS model:
S2000 H/L
2.13.3 Source 11: Received message LOAD DATA NACK

Source:
(11) Received message LOAD DATA NACK
BTS model:
S2000 H/L
2.13.4 Source 12: Received message LOAD END NACK

Source:
(12) Received message LOAD END NACK
BTS model:
S2000 H/L
2.13.5 Source 13: Received message

Source:
(13) Received message
BTS model:
S2000 H/L

411-9001-104 18.05 2 February 2010
451

Fault number:
1080
Access fault
Type
equipmentAlarm
FAULT ANALYSIS
This fault number indicates a communication problem between the BSC
and the BTS. More precisely, there is an issue between the SPR and
Access software modules of the BSC (SPR defense on opening or closing
a link or dialog).
List of causes:
0 No response from Access for chnl cnx request

1 Nack from Access for chnl cnx request
2 No response from Access for chnl dcnx request
3 Nack from Access for chnl dcnx request
4 No response from Access for chnl switchover request
5 Nack from Access for chnl switchover request
6 No response from Access for OML open diag request
7 Nack from Access for OML open diag request
8 No response from Access for OML close diag request
9 Nack from Access for OML close diag request
10 No response from Access for RSL open diag request
11 Nack from Access for RSL open diag request
12 No response from Access for RSL close diag request
13 Nack from Access for RSL close diag request
14 No response from Access for GSL open diag request
15 Nack from Access for GSL open diag request
16 No response from Access for GSL close diag request
17 Nack from Access for GSL close diag request

BSC defense
The BSC tries to use other LAPD channels to reach the BTS.

411-9001-104 18.05 2 February 2010
452

TROUBLESHOOTING
If the BSC succeeds in using other LAPD channels, then no maintenance
action is required.
If the BSC fails, then other fault numbers are sent to the OMC-R.
2.15 Fault number: 1165 (S2000H, S2000L)

Fault number
1165
At least one terrestrial circuit is HSCSD-blocked.
Type
equipmentAlarm
This problem is associated with a PCM fault. See 411-9001-105 (Nortel

GSM BSS Fault Clearing - Advanced Maintenance Procedures).

Fault number:
1258
No BTS response on preprocessing configuration
Type
equipmentAlarm
FAULT ANALYSIS
This fault number indicates a non-response of a transceiverEquipment
object to an L1M request. The BTS issues this alarm after five
unsuccessful attempts to warn users that the data handled by the BSC
may not be consistent with the data actually received by the BTS.
In spite of this handling, the BSC goes on its configuration attempts. The
situation must be re-established.
The message loss, due to disruptions on the Abis link, is sufficient for
the creation of this notification, but insufficient to release the defense
mechanism of the transceiverEquipment object.
BSC defense
None.

411-9001-104 18.05 2 February 2010
453
CAUTION
The service is lost.
TROUBLESHOOTING
Step
Action
Check the time of the alarm appearance and note the different
commands performed at the OMC-R on the cell concerned and
on the neighboring cells, if any.
Check which parameters are concerned by the notification: those

of the cell or those of the neighboring cells.
Check if it is a start-up or a change, in order to understand the

commands performed in the notification log.
Check the state of the bts, pcmCircuit, btsSiteManager and

Perform a "display dynamic data" on the transceiver object.
Ensure that the state of the parameter "allocationState" is

"available".
If the state of the parameter "allocationState" is not
"available", the BTS has not recognized or not received
the messages from the BSC.
If the state of the parameter "rmpConfState" is "not

configured", the fault is confirmed. Go to step 6.
To create an adjacent cell on the bts object:
Select the bts object.
In the dialog box, select either the "adjacentCellReselection"

or "adjacentCellHandover" object.
Go to the "Objects" menu and select the "Create Child"

option. This opens a dialog box which allows the operator to
select various dependent objects.

--End--

411-9001-104 18.05 2 February 2010
454

Fault number:
1259
Negative acknowledgement on preprocessing command
Type
equipmentAlarm
FAULT ANALYSIS
This alarm can be received on either a standard cell or on a neighboring
cell.
If the alarm is received on a neighboring cell, there is not handover any

more (because the neighboring cells are unknown).
If the alarm is received on a standard cell, the problem can be

occurred during the start-up or a change.

BSC defense
None.
If the alarm is received on a neighboring cell, calls are still possible.
Nevertheless, the calls cannot be moved on the neighboring cells (no
handover is possible). Then there will be an increase in the rate of call
drops.
ATTENTION
The geographical mobility of the mobile is reduced.
If the mobile is out of its geographical area of the cell where it is, the service is
reduced.
TROUBLESHOOTING
If the alarm appears during a start-up, a problem occurred in the BTS
configuration during the installation.
If the alarm appears during a change, look at the last commands at the
OMC-R few times before the alarm appearance. Look at the changes
performed for the neighboring cells.
Check that, if the microCellInstability and microCellStability parameters
have a value, have the value "algo B". Otherwise, modify it.

411-9001-104 18.05 2 February 2010
455

Fault number:
1265
Blockage of radio channel(s) in busy state
Type
communicationsAlarm
FAULT ANALYSIS
This alarm indicates that some channels were busy by a call during a time
period that is higher than the surveillance period whose period has been
chosen by the operator.
The notification lists all the radio channels of the BTS that were busy
during the traffic surveillance, whose period has been chosen by the
operator.
BSC defense
None.
None.
FAULT LOCATION
The notification indicates, for the concerned BTS, the busy channel(s).
TROUBLESHOOTING
Step
Action
Check the time of the fault number 1265 and identify the faulty
channel.
Check the call duration in comparison with the surveillance

period by checking the radResSupBusytimer parameter of the
bsc object.
If the call duration is equal or higher than the value of the

surveillance period, go to step 3.
If it is not the call duration that is concerned and that is the

source of the fault number, call the manufacturer.
Increase the value of the surveillance period.

411-9001-104 18.05 2 February 2010
456

Set the transceiver object to "locked" then "unlocked".


--End--

Fault number:
1266
Blockage of radio channel(s) in free state
Type
communicationsAlarm
FAULT ANALYSIS
When the radResSupervision parameter is "true", a notification with the
fault number 1266 is sent periodically to the OMC-R.
The notification indicates all the BTS radio channels that have been
continuously free for the previous notification.
This period is determined by the radResSupFreetimer parameter of the
bsc object. This parameter sets the maximum duration of non utilization
for a radio channel.
BSC defense
None.
ATTENTION
FAULT LOCATION
The notification indicates, for the concerned BTS, the free channel(s).
TROUBLESHOOTING

411-9001-104 18.05 2 February 2010
457
Step
Action
channel.
Analyze the traffic on the network by checking the rate of call

drop (TCH number busy in comparison to cell resource number).
see Nortel GSM BSS Parameter Reference (411-9001-124).
If the traffic is low, the fault number 1266 is normal.

If the traffic is important (almost equal to the TCH number
in the cell), the faulty channels are not used. Call the
manufacturer.
Analyze the traffic on the network by checking the rate of

SDCCH allocation failures.
Check the synthetic counter C8706 (cellSdcchResourceFailure
Ratio).
If the counter value is low (SDCCH blocking is not observed),

the fault number 1266 is normal.
If the counter value is high (SDCCH blocking is observed),

and still fault number 1266 is observed, this requires further
investigation. Call the manufacturer.
--End--

Fault number:
1268
No response to a SACCH filling (SYS 5, 6, 5 bis or 5 ter)
Type
communicationsAlarm
FAULT ANALYSIS
This alarm indicates that the BTS has not answered nine successive
acknowledgment requests SACCH filling sent by the BSC. As long
as the BSC has not received response, it repeats the procedure of
acknowledgment request.
BSC defense
None.

411-9001-104 18.05 2 February 2010
458
ATTENTION
The service is reduced because the channels supported by the faulty TRX are
not available for calls.
TROUBLESHOOTING
Step
Action
Look for the TRX supported the TDMA quoted in the alarm by
performing a "Display all" command on the transceiverEquipment
objects.
Check the state of the channels associated with the TDMA.
If all the channels are not available, perform the procedure of

return to service.
Otherwise, stop the maintenance procedure because the

state of the system is normal.
Set the transceiverEquipment object associated with the TDMA

to "locked" then to "unlocked".
Wait that the state of the transceiver object becomes "enabled".

--End--

Fault number:
1500
Measurement received on an unknown frequency of

neighboring cell
Type
communicationsAlarm
FAULT ANALYSIS
This alarm indicates that a measurement has been received on an
unknown frequency of a neighboring cell in GSM 900 or GSM 1800 mode.
The message is sent at the end of the communication.

411-9001-104 18.05 2 February 2010
459

Fault number:
1505
No response to a BCCH info (SYS 1, 2, 3, 4, 2 bis, 7, 8, 2 ter,

13)
Type
communicationsAlarm
FAULT ANALYSIS
acknowledgment requests BCCH info sent by the BSC. As long as
the BSC has not received any response, it repeats the procedure of
BSC defense
None.
CAUTION
TROUBLESHOOTING
Step
Action
If the alarm appears during the downloading, do not take into

account this alarm. Otherwise, go to step 2.
Set the btsSiteManager concerned to "locked" then "unlocked".

The problem concerns the old passive chain of the BSC. Look
for alarms concerning the BSC and treat them.

--End--

411-9001-104 18.05 2 February 2010
460
2.23 Fault number: 1508 (S2000H/L)

Fault number:
1508
Data service impact (SYS 13 size exceeded)
Type
Hardware anomaly
FAULT ANALYSIS
When the operator configures maximum hopping frequencies (64
frequencies) and activates GPRS or EGPRS in a cell, then "System
Information 13 rest octet" size exceeds 21 octets. As a result the "System
Information 13 rest octet" field is truncated and this begin-of-fault alarm
is sent.
64 frequencies is the maximum number granted by the OMC-R (semantic
control). But operators must also take into account Engineering
recommendations given in BSS Parameters User Guide (BPUG).
The end-of-fault alarm is sent after the "System Information 13 rest octet"
field size has become equal to 21 octets or less.

BSC defense
None.

CAUTION
There is a partial or full impact on data service (whereas CS
traffic is still maintained).
The information relative to data services on impacted cell(s) are
not fully sent to the BTS.
TROUBLESHOOTING
see BSS Parameter User Guide (BPUG PE/DCL/DD/0036) to configure
the cell (cellAllocation and mobileAllocation parameters for the bts object)
in order to respect Engineering recommendations (maximum hopping
frequency number) and to have the "System Information 13 rest octet" field
size equal to 21 octets or less.
Normally, the maximum number of frequencies that can be set up with
cellAllocation parameter is 64for each frequency band. However, due
to SI13 size constraints, when GPRS or EDGE is activated in the cell
and there is at least one hopping data TDMA, the limitation becomes a
maximum of 49 frequencies.
where n is the number of non-hopping frequencies in the cell.
411-9001-104 18.05 2 February 2010
2.24 Applicability of the fault numbers to the BTS type
461
2.24 Applicability of the fault numbers to the BTS type

This paragraph contains the list of all the BTS fault numbers. For each
fault, it indicates the BTSs to which the fault applies. Each fault number
is described in a technical document, specific to the BTS. Refer to the
following technical documents to know more about the fault numbers, for
each BTS:
Nortel GSM BTS S8000/S8002/S8003/S8006 Fault Clearing

(411-9001-103)
Nortel GSM BTS S2000H/S2000L/e-cell Fault Clearing (411-9001-104)

Nortel GSM BTS S12000 Fault Clearing (411-9001-143)
Nortel GSM BTS 6000 and 18000 Fault Clearing (411-9001-161)
Nortel GSM BTS 9000 Fault Clearing (411-9001-214)
Table 43
Applicability of the fault numbers to the BTS type
S8000,
S8002,
S8003,
S8006
S2000H/L
e-cell
S12000
BTS 18000
BTS 6000
BTS 9000
411-9001103
411-9001104
411-9001104
411-9001143
411-9001161
411-9001161
411-9001214
1051
1052
1053
1054
1055
1056
1058
1059
1060
1061
1063
1064
1065
1067
1070
1073
1077

411-9001-104 18.05 2 February 2010
462
Table 43
Applicability of the fault numbers to the BTS type (contd.)
S8000,
S8002,
S8003,
S8006
S2000H/L
e-cell
S12000
BTS 18000
BTS 6000
BTS 9000
411-9001103
411-9001104
411-9001104
411-9001143
411-9001161
411-9001161
411-9001214
1078
1080
1258
1259
1265
1266
1268
1500
1505
1506
1507
1508
30034

411-9001-104 18.05 2 February 2010
463

3.1 Fault number: 1051 (e-cell)
Fault number:
1051
Loss of layer 3 with remote GSM entity
Type
communicationsAlarm
Clearing - Advanced Maintenance (411-9001-105)

Fault number:
1052
Type
communicationsAlarm/processingErrorAlarm/equipmentAlarm
FAULT ANALYSIS
This message identifies the impacted element but not the faulty element. It
indicates a software downloading error concerning a transceiverEquipment
object or a btsSiteManager object.
All the software downloading attempts are indicated, as well as the source
of their failure.
Table 44 "Fault number 1052 sources" (page 463) indicates all the sources
of the fault number 1052 for the e-cell. For more information on each
source, see the indicated paragraph to know the corrective maintenance
procedure associated with this source.
Table 44
source
No.
0
Paragraph
Source wording
No response to status request
3.2.1 Source 0: No response to

status request (page 472)

411-9001-104 18.05 2 February 2010
464
Table 44
source
No.
Paragraph
Source wording
3.2.2 Source 1: Bad hardware

reference or manufacturer ID
(page 474)
SUP stop receipt

(page 475)
3.2.4 Source 3: No change to one

BOOT after reset (page 478)
Software not compatible with hardware
File access error
Repetitive errors (NACK, timeout, ... ) while

downloading a file

downloadable TEI
14
CSM load container negative acknowledgement
15
3.2.5 Source 4: This entity is

engaged in another downloading
Source 8: Wrong software reference
on a non downloadable TEI
(page 479)
3.2.6 Source 5: Software not
compatible with hardware
(page 480)
3.2.7 Source 6: File access
error (page 483)
3.2.8 Source 7: Repetitive
errors (NACK, timeout, ...) while
3.2.5 Sourcea 4:
This
entity
is
downloading
file
(page
484)
engaged in another downloading
Source 8: Wrong software reference
on a non downloadable TEI
3.2.10 Source
14: Received
(page 479)
CSM LOAD CONTAINER NAK
(page 487)
empty (page 489)
16
File to download unavailable

unavailable (page 492)
17
3.2.13 Source 17: Buffer allocation

failure (page 492)
18
Bad sending buffer size value
3.2.14 Source 18: Bad sending

buffer size value (page 495)
19
Failure during OMU switchover

OMU switchover (page 497)
20
Bad TEI sent by BTS in the CSM software

3.2.16 Source 20: Bad TEI sent by

BTS in the CSM software update
report message (page 499)

411-9001-104 18.05 2 February 2010
465
Table 44
source
No.
Source wording
Paragraph
21
CSM software update report with the

cause "unknown TEI"

update report with the cause unknown TEI - (page 502)
22
CSM software update report with the cause

"equipment failure"

update report with the cause equipment failure - (page 504)
23


update report with the cause downloading failure - (page 506)
24

"not able to perform"

update report with the cause - not
able to perform- (page 509)
25

cause "wrong soft ref"

update report with the cause - wrong
software reference - (page 511)
26

cause "wrong config ref"

update report with the cause - wrong
configuration reference - (page 513)
27

cause "restart request"

update report with the cause - restart
request - (page 516)
28

"data inconsistency"

update report with the cause - data
29

"message out of sequence"

update report with the cause
- message out of sequence -
(page 520)
30

"background not available"

- background not available -
(page 523)
31

"incompatible RM version"

- incompatible RM version -
(page 525)
32

"downloading in progress"

- downloading in progress -
(page 527)

411-9001-104 18.05 2 February 2010
466
Table 44
source
No.
Source wording
Paragraph
33
Bad report sent by BTS in the CSM software

3.2.29 Source 33: Bad report sent

by BTS in the CSM software update
report message (page 530)
34
no BTS response on CSM software update

init/control message
3.2.30 Source 34: No BTS

response on CSM software update
init-control message (page 532)
35
nack received on the abort requested

by operator
3.2.31 Source 35: Nack received

on the abort requested by operator
(page 534)
36
bad report sent by BTS in the CSM software

update abort message
3.2.32 Source 36: Bad report sent

by BTS in the CSM software update
abort message (page 537)
37
no BTS response on CSM software update

abort message

response on CSM software update
abort message (page 539)
38
flash activate nack with the cause

"unknown TEI"

nack with the cause - unknown
TEI - (page 541)
39

"equipment failure"

40


41
flash activate nack with the cause "not

able to perform"

nack with the cause - not able to
perform - (page 548)
42
flash activate nack with the cause "flash

inconsistency"

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

inconsistency"

nack with the cause - data
44

"wrong soft ref"

nack with the cause - wrong soft
ref - (page 555)
45

"wrong config ref"

nack with the cause - wrong config
ref - (page 557)

411-9001-104 18.05 2 February 2010
467
Table 44
source
No.
Source wording
Paragraph
46
CSM downloading start nack with the

cause "unknown TEI"
3.2.42 Source 46: CSM

downloading start nack with the
cause - unknown TEI - (page 559)
47
CSM downloading start nack with the cause

"equipment failure"

downloading start nack with
the cause - equipment failure
- (page 561)
48


cause - downloading failure -
(page 564)
49

"message out of sequence"

cause - message out of sequence
- (page 566)
50

cause "wrong soft ref"

cause - wrong soft ref - (page 568)
51

cause "wrong config ref"

downloading start nack with
the cause - wrong config ref
- (page 571)
52
CSM downloading start nack with a bad cause

downloading start nack with a
bad cause (page 573)
53
no BTS response on CSM downloading

start message

response on CSM downloading
start message (page 575)
54
CSM downloading end nack with the

cause "unknown TEI"

downloading end nack with the
cause - unknown TEI - (page 577)
55
CSM downloading end nack with the cause

"equipment failure"

downloading end nack with
the cause - equipment failure
- (page 580)
56


cause - downloading failure -
(page 582)

411-9001-104 18.05 2 February 2010
468
Table 44
source
No.
Source wording
Paragraph
57

"value out of range"

cause - value out of range -
(page 584)
58
CSM downloading end nack with a bad cause

downloading end nack with a
bad cause (page 586)
59
no BTS response on CSM downloading

end message

response on CSM downloading
end message (page 589)
60
CSM load init nack with the cause

"equipment failure"

61


62
CSM load init nack with the cause "message

out of sequence"

nack with the cause - message out
63

"wrong file ref"

nack with the cause - wrong file
ref - (page 598)
64
CSM load init nack with the cause "window

size not allow"

nack with the cause - window size
not allowed - (page 600)
65
CSM load init nack with the cause "data

format error"

error - (page 602)
66
CSM load init nack with a bad cause

67
no BTS response on CSM load init message

response on CSM load init
message (page 607)
68
CSM load data nack with the cause

"equipment failure"

69



411-9001-104 18.05 2 February 2010
469
Table 44
source
No.
Source wording
Paragraph
70
CSM load data nack with the cause "message

out of sequence"

71
CSM load data nack with the cause "data

format error"

error - (page 616)
72

"window overflow"

nack with the cause - window
overflow - (page 618)
73

inconsistency"
3.2.69 Source 73: CSM load

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

not received"

nack with the cause - block not
received - (page 623)
75

"bad block tag"

nack with the cause - bad block
tag - (page 625)
76

"checksum error"

error - (page 627)
77
CSM load data nack with a bad cause

78
unexpected CSM load data ack
3.2.74 Source 78: Unexpected

CSM load data ack (page 632)
79
no BTS response on CSM load data message

response on CSM load data
message (page 634)
80
CSM load end nack with the cause

"equipment failure"

81


82
CSM load end nack with the cause "value

out of range"

nack with the cause - value out
of range - (page 641)
83
CSM load end nack with the cause "message

out of sequence"


411-9001-104 18.05 2 February 2010
470
Table 44
source
No.
Source wording
Paragraph
84
CSM load end nack with the cause "data

format error"

error - (page 645)
85

"wrong file ref"

nack with the cause - wrong file
ref - (page 647)
86
CSM load end nack with the cause "data

inconsistency"

end nack with the cause - data
87

"checksum error"

error - (page 652)
88
CSM load end nack with a bad cause

89
no BTS response on CSM load end message

response on CSM load end
message (page 656)
90
bad report sent by BTS during an

internal update
3.2.86 Source 90: Bad report

sent by BTS during an internal
update (page 659)
91
CSM load init nack with the cause "file

already open"

nack with the cause - file already
open - (page 661)
92

"invalid mode"

init nack with the cause - invalid
mode - (page 663)
93
CSM load init nack with the cause "file

cannot be unloaded"

nack with the cause - file cannot
be unloaded - (page 665)
94
CSM load init nack with the cause "flash

flag cannot access"

nack with the cause - flash flag
cannot access - (page 668)
95
CSM load data nack with the cause "file

cannot be unloaded"

nack with the cause - file cannot
96
CSM load data nack with the cause "flash

flag cannot access"

nack with the cause - flash flag
cannot access - (page 672)

411-9001-104 18.05 2 February 2010
471
Table 44
source
No.
Source wording
Paragraph
97
CSM load data nack with the cause "boot

cannot be unloaded"

nack with the cause - boot cannot
98

decod error"

nack with the cause - data decode
error - (page 677)
99
CSM load data nack with the cause "table

cannot access"

nack with the cause - table cannot
access - (page 679)
100
CSM load data nack with the cause "ram

mapping error"

data nack with the cause - RAM
mapping error - (page 681)
101

access error"

data nack with the cause - flash
access error - (page 684)
102

"flash ram error"

RAM error - (page 686)
103

erase error"

erase error - (page 688)
104

"internal abort"

data nack with the cause - internal
abort - (page 690)

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


411-9001-104 18.05 2 February 2010
472
CAUTION
ATTENTION
3.2.1 Source 0: No response to status request

Source:
(0) No response to status request
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that the BTS has not replied to the status request.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

411-9001-104 18.05 2 February 2010
473

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010
474


above).

Procedures)).


--End--
3.2.2 Source 1: Bad hardware reference or manufacturer ID

Fault number 1052: GSM entity downloading failure
Source:
(1) Bad hardware reference or manufacturer ID
BTS model:
e-cell
FAULT ANALYSIS
The alarm indicates that the "hardwareRef" parameter, obtained by
performing the "Display" command on the btsSiteManager object, is not in
accordance with the PROM numbers on the boards.
TROUBLESHOOTING
Preliminary checks
Step
Action



411-9001-104 18.05 2 February 2010
475
Clear the alarm.



Go to step 2.
btsSiteManager object to "locked" then to "unlocked" to
confirm the problem.

above).


Case of the btsSiteManager object for the e-cell
Set the value of the "hardwareRef" parameter to "0".

--End--

Source:
(2) SUP stop receipt
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that a supervision stop has been received.

411-9001-104 18.05 2 February 2010
476
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
477


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
478
3.2.4 Source 3: No change to one BOOT after reset

Fault number 1052:
Source:
(3) No change to one of BOOT after reset
BTS model:
e-cell
TROUBLESHOOTING
Preliminary checks
Step
Action


step 2.



Set the operationalState of the entity concerned to "locked" then

"unlocked" to restart the downloading.
If the alarm persists, check if the source 1 appears.

411-9001-104 18.05 2 February 2010
479
If the source 1 appears, treat it. See Paragraph 3.2.2

Source 1: Bad hardware reference or manufacturer ID
(page 474).
If the source 1 does not appear, go to step 3.
If the alarm has disappeared, the downloading has restarted.

Go to step 4.
Replace the radio cabinet: see Nortel GSM BTS e-cell

If the alarm has disappeared, go to step 4. Otherwise, call the
manufacturer.

--End--
3.2.5 Source 4: This entity is engaged in another downloading

Source 8: Wrong software reference on a non downloadable TEI
Fault number 1052:
Source:
(4) This entity is engaged in another downloading
Source:
(8) Wrong software reference on a non downloadable TEI
BTS model:
e-cell
TROUBLESHOOTING
Preliminary checks
Step
Action


step 2.



411-9001-104 18.05 2 February 2010
480

or 8 is still present, call the manufacturer.
Maintenance (411-9001-105) ).


--End--
3.2.6 Source 5: Software not compatible with hardware

Fault number 1052:
Source:
(5) Software not compatible with hardware
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates an inconsistency between the hardware items of
equipment and the software (EFT) downloaded from the OMC-R.
TROUBLESHOOTING
Preliminary checks
Step
Action
Check whether the "DRX automatic downloading" is activated

or not:
If the "DRX automatic downloading" is activated, go to step 6.

If the "DRX automatic downloading" is not activated, go to
step 2.


411-9001-104 18.05 2 February 2010
481

step 5.



Check if the EFT is correct by checking the value of the

"swVersionRunning" parameter and this by performing a
"Display" command on the software object associated with the
bsc, btsSiteManager and transceiverEquipment objects.
If it is the case, set the object concerned to "locked" then

"unlocked".
If it is not the case, go to step 4.
Set the object concerned to "locked".
Download the good EFT on the item of equipment according to

the following values.
Field
XXX
Meaning
Type of software
Value
PIC
TRX : CDRX

411-9001-104 18.05 2 February 2010
482
Field
Meaning
Value
ab
Version number
[08 .. 32]
Sub-version number
BCF : [A .. H]
TRX : [A .. H]
Edition number
BCF : [1 .. 8]
TRX : [1 .. 8]
ef
Revision factor
BCF : [01 .. 32]

TRX : [01 .. 32]
If the name of the EFT is correct, call the manufacturer.

Otherwise, modify the value and set the object concerned to
If the "Automatic downloading" is activated, the OMC-R starts to

perform the downloading just after it received fault number 1052
cause 5:
a The OMC-R reads the BTS hardware reference quoted in the
fault number.
b The OMC-R deduces the name of the EFT to be downloaded
from a correspondence table.
c The OMC-R searches for the EFT in its database:
If it does not find one, the OMC-R goes to step 7.

If it finds one and only one, the OMC-R goes to step 8.
If it finds more than one, it lets the operator choose. A
critical alarm with fault number 30076 is emitted to report
that the automatic downloading failed (see Nortel GSM
OMC-R Troubleshooting(411-9001-032).
The OMC-R searches for the delivery name of the BTS the DRX
belongs to. Then, for all BTS with the same delivery name under
the same BSC, the OMC-R searches for the right EFT.
If it finds one and only one, it selects it. Then it goes to step
8.
If it finds more than one, it lets the operator choose. A critical

alarm with fault number 30076 is emitted to report that the
automatic downloading failed (see Nortel GSM OMC-R
Troubleshooting (411-9001-032)).
If it does not find one, the OMC-R searches for an EFT

suitable to all the BTS with the same delivery name in all the
BSC.

411-9001-104 18.05 2 February 2010
483
If it finds one and only one, it selects it. Then it goes to

step 8.
If it finds more than one, or none, it lets the operator
choose. A critical alarm with fault number 30076 is
emitted to report that the automatic downloading
failed (see Nortel GSM OMC-R Troubleshooting
(411-9001-032)).
8
The OMC-R starts to download the selected EFT:

a If necessary, it downloads the selected EFT to the BSC disc.
b It locks the related transceiverEquipment object instance
c It sets the sWVersionNew parameter of the new
transceiverEquipment software object with the new EFT
name.
d It activates the new version.
e It unlocks the related transceiverEquipment object instance.
f
As a consequence, the fault number 1052 with cause 5 is

automatically cleared.

--End--

Fault number 1052:
Source:
(6) File access error
BTS model:
e-cell
FAULT ANALYSIS
TROUBLESHOOTING
Preliminary checks
Step
Action


411-9001-104 18.05 2 February 2010
484

step 3.


is still present, treat the alarm, go to step 2.
Maintenance (411-9001-105) ).

Download the software.

If the alarm persists, go to call the manufacturer.

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

downloading a file
BTS model:
e-cell
411-9001-104 18.05 2 February 2010
485
3.2.9 Source 9: No response to download message

Source:
(9) No response to download message
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that the BTS has not replied to a download
message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
486

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
487

Procedures)).


--End--
3.2.10 Source 14: Received CSM LOAD CONTAINER NAK

Source:
(14) Received CSM LOAD CONTAINER NAK
BTS model:
e-cell
FAULT ANALYSIS
This message is received after attempts to download the software are
failed by the BSC. This source is because the Load file of TRX/BCF
residing in the BSC is corrupt.
TROUBLESHOOTING
Step
Action
Preliminary checks
Check the notification and identify the object concerned.

Check the state of the site by performing the Display all


step 6.


411-9001-104 18.05 2 February 2010
488

Procedures) ).

object, and then unlock it.
If the alarm with the fault number 1052 and the source 6 is
present, process the alarm. Go to step 4.
if there are other alarms, such as fault number 1054, process

them (concerning fault number 1054 (loss of layer 2), see
411-9001-105 (Nortel GSM BSS Fault Clearing - Advanced
Maintenance Procedures)



Clear the alarm.

concerning cells.
Procedures)).


411-9001-104 18.05 2 February 2010
489


above).

Procedures)).

Re-download the software from the MD at the OMC--R to the

BSC disk partition:
To download a BCF software, refer to the downloading

procedure.
To download a TRX software, refer to the downloading

procedure.



--End--
3.2.11 Source 15: File to download empty

Source:
(15) File to download empty
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that the file to download is empty.

411-9001-104 18.05 2 February 2010
490
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
491


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
492
3.2.12 Source 16: File to download unavailable

Source:
(16) File to download unavailable
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that the downloading attempt has failed because
the file to be downloaded cannot be found in the catalog file (either
because the catalog file itself is not valid, or the name of the file has been
improperly copied in the BTS or BSC software).
TROUBLESHOOTING
Step
Action
Preliminary checks
Cleanup the load from BTS partition of active BSC hard disk.
disk partition:

procedure in Nortel GSM BSS Configuration - Operating
Procedures (411-9001-034).
To download TRX software, see the downloading procedure

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

transceiverEquipment object)
Unlock the object concerned

Perform one of the following
For the BSC 3000, call the manufacturer

--End--
3.2.13 Source 17: Buffer allocation failure

Source:
(17) Buffer allocation failure
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
493
FAULT ANALYSIS
This source indicates a buffer allocation failure.
TROUBLESHOOTING
Procedure 3
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).


411-9001-104 18.05 2 February 2010
494

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
495
4

--End--
3.2.14 Source 18: Bad sending buffer size value

Source:
(18) Bad sending buffer size value
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a bad sending of the buffer size value.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
496

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010
497


above).

Procedures)).


--End--
3.2.15 Source 19: Failure during OMU switchover

Source:
(19) Failure during OMU switchover
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a failure during the OMU switchover.
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-104 18.05 2 February 2010
498
Clear the alarm.


Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
499

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
3.2.16 Source 20: Bad TEI sent by BTS in the CSM software update
report message
Source:
(20) Bad TEI sent by BTS in the CSM software update report
message
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
500
FAULT ANALYSIS
This source indicates a bad TEI sent by the BTS in the CSM software
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
501
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
502

--End--
3.2.17 Source 21: CSM software update report with the cause unknown TEI Fault number 1052 : GSM entity downloading failure
Source:
(21) CSM software update report with the cause "unknown TEI"
BTS model:
e-cell
FAULT ANALYSIS
"unknown TEI".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
503

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010
504


above).

Procedures)).


--End--
3.2.18 Source 22: CSM software update report with the cause equipment failure Fault number 1052 : GSM entity downloading failure
Source:
(22) CSM software update report with the cause "equipment

failure"
BTS model:
e-cell
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
505

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
506

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
3.2.19 Source 23: CSM software update report with the cause downloading failure Fault number 1052 : GSM entity downloading failure
Source:
(23) CSM software update report with the cause "downloading

failure"
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
507
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
508
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
509

--End--
3.2.20 Source 24: CSM software update report with the cause - not able
to performFault number 1052 : GSM entity downloading failure
Source:
(24) CSM software update report with the cause "not able to
perform"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM software update report with the cause "not
able to perform".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
510

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010
511


above).

Procedures)).


--End--
software reference Fault number 1052 : GSM entity downloading failure
Source:
(25) CSM software update report with the cause "wrong software
reference"
BTS model:
e-cell
FAULT ANALYSIS
software reference".
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
512

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
513

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
configuration reference Fault number 1052 : GSM entity downloading failure
Source:
(26) CSM software update report with the cause "wrong

configuration reference"
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
514
FAULT ANALYSIS
configuration reference".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
515
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
516

--End--
3.2.23 Source 27: CSM software update report with the cause - restart
request Fault number 1052 : GSM entity downloading failure
Source:
(27) CSM software update report with the cause "restart request"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM software update report with the cause "restart
request".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
517

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010
518


above).

Procedures)).


--End--
Source:
(28) CSM software update report with the cause "data

inconsistency"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM software update report with the cause "data
inconsistency".
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
519

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
520

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
3.2.25 Source 29: CSM software update report with the cause message out of sequence Fault number 1052 : GSM entity downloading failure
Source:
(29) CSM software update report with the cause "message out
of sequence"
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
521
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
522
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
523

--End--
3.2.26 Source 30: CSM software update report with the cause background not available Fault number 1052 : GSM entity downloading failure
Source:
(30) CSM software update report with the cause "background

not available"
BTS model:
e-cell
FAULT ANALYSIS
"background not available".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
524

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010
525


above).

Procedures)).


--End--
3.2.27 Source 31: CSM software update report with the cause incompatible RM version Fault number 1052 : GSM entity downloading failure
Source:
(31) CSM software update report with the cause "incompatible

RM version"
BTS model:
e-cell
FAULT ANALYSIS
"incompatible RM version".
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
526

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
527

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
3.2.28 Source 32: CSM software update report with the cause downloading in progress Fault number 1052 : GSM entity downloading failure
Source:
(32) CSM software update report with the cause "downloading in

progress"
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
528
FAULT ANALYSIS
"downloading in progress".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
529
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
530

--End--
report message
Source:
(33) Bad report sent by BTS in the CSM software update report
message
BTS model:
e-cell
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
531

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010
532


above).

Procedures)).


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

init-control message
Source:
(34) No BTS response on CSM software update init/control

message
BTS model:
e-cell
FAULT ANALYSIS
This source indicates no BTS response on the CSM software update
init/control message.
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
533

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
534

concerning cells.
Procedures) ).


above).

Procedures)).


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

Source:
(35) Nack received on the abort requested by operator
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that a Nack has been received on the abort
requested by operator.

411-9001-104 18.05 2 February 2010
535
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
536


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
537
abort message
Source:
(36) Bad report sent by BTS in the CSM software update abort
message
BTS model:
e-cell
FAULT ANALYSIS
update abort message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
538

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
539

Procedures)).


--End--

message
Source:
(37) No BTS response on CSM software update abort message
BTS model:
e-cell
FAULT ANALYSIS
This source indicates no BTS response on CSM software update abort
message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
540

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
541


above).

Procedures)).


--End--
3.2.34 Source 38: Flash activate nack with the cause - unknown TEI Fault number 1052 : GSM entity downloading failure
Source:
(38) Flash activate nack with the cause "unknown TEI"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a flash activate nack with the cause unknown TEI.
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
542

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
543

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
3.2.35 Source 39: Flash activate nack with the cause - equipment
Source:
(39) Flash activate nack with the cause "equipment failure"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "equipment
failure".
411-9001-104 18.05 2 February 2010
544
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
545


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
546
3.2.36 Source 40: Flash activate nack with the cause - downloading
Source:
(40) Flash activate nack with the cause "downloading failure"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "downloading
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
547

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
548

Procedures)).


--End--
3.2.37 Source 41: Flash activate nack with the cause - not able to
perform Fault number 1052 : GSM entity downloading failure
Source:
(41) Flash activate nack with the cause "not able to perform"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "not able to
perform".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
549

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
550


above).

Procedures)).


--End--
3.2.38 Source 42: Flash activate nack with the cause - flash
Source:
(42) Flash activate nack with the cause "flash inconsistency"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a Flash activate nack with the cause "flash
inconsistency".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
551

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
552

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
3.2.39 Source 43: Flash activate nack with the cause - data
Source:
(43) Flash activate nack with the cause "data inconsistency"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a Flash activate nack with the cause "data
inconsistency".
411-9001-104 18.05 2 February 2010
553
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
554


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
555
3.2.40 Source 44: Flash activate nack with the cause - wrong soft ref Fault number 1052 : GSM entity downloading failure
Source:
(44) Flash activate nack with the cause "wrong soft ref"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "wrong soft ref".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
556

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
557

Procedures)).


--End--
3.2.41 Source 45: Flash activate nack with the cause - wrong config
ref Fault number 1052 : GSM entity downloading failure
Source:
(45) Flash activate nack with the cause "wrong config ref"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "wrong config
ref".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
558

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
559


above).

Procedures)).


--End--
3.2.42 Source 46: CSM downloading start nack with the cause unknown TEI Fault number 1052 : GSM entity downloading failure
Source:
(46) CSM downloading start nack with the cause "unknown TEI"
BTS model:
e-cell
FAULT ANALYSIS
"unknown TEI".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
560

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
561

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
3.2.43 Source 47: CSM downloading start nack with the cause equipment failure Fault number 1052 : GSM entity downloading failure
Source:
(47) CSM downloading start nack with the cause "equipment

failure"
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
562
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
563
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
564

--End--
3.2.44 Source 48: CSM downloading start nack with the cause downloading failure Fault number 1052 : GSM entity downloading failure
Source:
(48) CSM downloading start nack with the cause "downloading

failure"
BTS model:
e-cell
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
565

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010
566


above).

Procedures)).


--End--
3.2.45 Source 49: CSM downloading start nack with the cause message out of sequence Fault number 1052 : GSM entity downloading failure
Source:
(49) CSM downloading start nack with the cause "message out
of sequence"
BTS model:
e-cell
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
567

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
568

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
soft ref Fault number 1052 : GSM entity downloading failure
Source:
(50) CSM downloading start nack with the cause "wrong soft ref"
BTS model:
e-cell
FAULT ANALYSIS
"wrong soft ref".
411-9001-104 18.05 2 February 2010
569
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
570


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
571
config ref Fault number 1052 : GSM entity downloading failure
Source:
(51) CSM downloading start nack with the cause "wrong config
ref"
BTS model:
e-cell
FAULT ANALYSIS
"wrong config ref".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
572

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
573

Procedures)).


--End--
3.2.48 Source 52: CSM downloading start nack with a bad cause
Source:
(52) CSM downloading start nack with a bad cause
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM downloading start nack with a bad cause.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
574

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
575


above).

Procedures)).


--End--
3.2.49 Source 53: No BTS response on CSM downloading start

message
Source:
(53) No BTS response on CSM downloading start message
BTS model:
e-cell
FAULT ANALYSIS
This source indicates no BTS response on CSM downloading start
message.
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
576

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
577

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
3.2.50 Source 54: CSM downloading end nack with the cause unknown TEI Fault number 1052 : GSM entity downloading failure
Source:
(54) CSM downloading end nack with the cause "unknown TEI"
BTS model:
e-cell
FAULT ANALYSIS
"unknown TEI".
411-9001-104 18.05 2 February 2010
578
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
579


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
580
3.2.51 Source 55: CSM downloading end nack with the cause equipment failure Fault number 1052 : GSM entity downloading failure
Source:
(55) CSM downloading end nack with the cause "equipment

failure"
BTS model:
e-cell
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
581

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
582

Procedures)).


--End--
3.2.52 Source 56: CSM downloading end nack with the cause downloading failure Fault number 1052 : GSM entity downloading failure
Source:
(56) CSM downloading end nack with the cause "downloading

failure"
BTS model:
e-cell
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
583

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
584


above).

Procedures)).


--End--
3.2.53 Source 57: CSM downloading end nack with the cause - value
out of range Fault number 1052 : GSM entity downloading failure
Source:
(57) CSM downloading end nack with the cause "value out of
range"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM downloading end nack with the cause "value
out of range".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
585


Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
586

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
3.2.54 Source 58: CSM downloading end nack with a bad cause
Source:
(58) CSM downloading end nack with a bad cause
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM downloading end nack with a bad cause.

411-9001-104 18.05 2 February 2010
587
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
588


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
589
3.2.55 Source 59: No BTS response on CSM downloading end message

Source:
(59) No BTS response on CSM downloading end message
BTS model:
e-cell
FAULT ANALYSIS
This source indicates no BTS response on CSM downloading end
message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
590

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
591

Procedures)).


--End--
3.2.56 Source 60: CSM load init nack with the cause - equipment failure
Source:
(60) CSM load init nack with the cause "equipment failure"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "equipment
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
592

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
593


above).

Procedures)).


--End--
3.2.57 Source 61: CSM load init nack with the cause - downloading
Source:
(61) CSM load init nack with the cause "downloading failure"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "downloading
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
594

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
595

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
Source:
(62) CSM load init nack with the cause "message out of
sequence"
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
596
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "message out of
sequence".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
597
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
598

--End--
3.2.59 Source 63: CSM load init nack with the cause - wrong file ref Fault number 1052 : GSM entity downloading failure
Source:
(63) CSM load init nack with the cause "wrong file ref"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "wrong file ref".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
599

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-104 18.05 2 February 2010
600


above).

Procedures)).


--End--
3.2.60 Source 64: CSM load init nack with the cause - window size not
allowed Fault number 1052 : GSM entity downloading failure
Source:
(64) CSM load init nack with the cause "window size not
allowed"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "window size
not allowed".
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
601

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
602

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
3.2.61 Source 65: CSM load init nack with the cause - data format error
Source:
(65) CSM load init nack with the cause "data format error"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "data format
error".
411-9001-104 18.05 2 February 2010
603
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
604


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
605
3.2.62 Source 66: CSM load init nack with a bad cause
Source:
(66) CSM load init nack with a bad cause
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load init nack with a bad cause.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
606

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
607

Procedures)).


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

Source:
(67) No BTS response on CSM load init message
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a No BTS response on CSM load init message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
608

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
609


above).

Procedures)).


--End--
3.2.64 Source 68: CSM load data nack with the cause - equipment
Source:
(68) CSM load data nack with the cause "equipment failure"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "equipment
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
610

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
611

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
3.2.65 Source 69: CSM load data nack with the cause - downloading
Source:
(69) CSM load data nack with the cause "downloading failure"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "downloading
failure".
411-9001-104 18.05 2 February 2010
612
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
613


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
614
Source:
(70) CSM load data nack with the cause "message out of
sequence"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "message out
of sequence".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
615

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
616

Procedures)).


--End--
3.2.67 Source 71: CSM load data nack with the cause - data format
Source:
(71) CSM load data nack with the cause "data format error"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "data format
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
617

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
618


above).

Procedures)).


--End--
3.2.68 Source 72: CSM load data nack with the cause - window
overflow Fault number 1052 : GSM entity downloading failure
Source:
(72) CSM load data nack with the cause "window overflow"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "window
overflow".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
619

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
620

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
3.2.69 Source 73: CSM load data nack with the cause - data
Source:
(73) CSM load data nack with the cause "data inconsistency"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "data
inconsistency".
411-9001-104 18.05 2 February 2010
621
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
622


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
623
3.2.70 Source 74: CSM load data nack with the cause - block not
received Fault number 1052 : GSM entity downloading failure
Source:
(74) CSM load data nack with the cause "block not received"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "block not
received".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-104 18.05 2 February 2010
624

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-104 18.05 2 February 2010
625

Procedures)).


--End--
3.2.71 Source 75: CSM load data nack with the cause - bad block tag Fault number 1052 : GSM entity downloading failure
Source:
(75) CSM load data nack with the cause "bad block tag"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "bad block
tag".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
626

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
627


above).

Procedures)).


--End--
3.2.72 Source 76: CSM load data nack with the cause - checksum error
Source:
(76) CSM load data nack with the cause "checksum error"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "checksum
error".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
628

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
629

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
3.2.73 Source 77: CSM load data nack with a bad cause
Source:
(77) CSM load data nack with a bad cause
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM software update report with the cause CSM
load data nack with a bad cause.

411-9001-104 18.05 2 February 2010
630
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-104 18.05 2 February 2010
631


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
632
3.2.74 Source 78: Unexpected CSM load data ack

Source:
(78) Unexpected CSM load data ack
BTS model:
e-cell
FAULT ANALYSIS
This source indicates an unexpected CSM load data ack.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).


411-9001-104 18.05 2 February 2010
633

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-104 18.05 2 February 2010
634

Procedures)).


--End--
3.2.75 Source 79: No BTS response on CSM load data message

Source:
(79) No BTS response on CSM load data message
BTS model:
e-cell
FAULT ANALYSIS
This source indicates no BTS response on CSM load data message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
635

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
636

Go to step 4.

above).

Procedures)).


--End--
3.2.76 Source 80: CSM load end nack with the cause - equipment
Source:
(80) CSM load end nack with the cause "equipment failure"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "equipment
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
637

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
638

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
3.2.77 Source 81: CSM load end nack with the cause - downloading
Source:
(81) CSM load end nack with the cause "downloading failure"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "downloading
failure".
411-9001-104 18.05 2 February 2010
639
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-104 18.05 2 February 2010
640

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
641
3.2.78 Source 82: CSM load end nack with the cause - value out of
range Fault number 1052 : GSM entity downloading failure
Source:
(82) CSM load end nack with the cause "value out of range"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "value out of
range".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
642

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-104 18.05 2 February 2010
643

Procedures)).


--End--
Source:
(83) CSM load end nack with the cause "message out of
sequence"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "message out
of sequence".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
644

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
645

Go to step 4.

above).

Procedures)).


--End--
Source:
(84) CSM load end nack with the cause "data format error"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "data format
error".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
646

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
647

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
3.2.81 Source 85: CSM load end nack with the cause - wrong file ref Fault number 1052 : GSM entity downloading failure
Source:
(85) CSM load end nack with the cause "wrong file ref"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "wrong file ref".

411-9001-104 18.05 2 February 2010
648
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-104 18.05 2 February 2010
649

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
650
3.2.82 Source 86: CSM load end nack with the cause - data
Source:
(86) CSM load end nack with the cause "data inconsistency"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "data
inconsistency".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
651

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-104 18.05 2 February 2010
652

Procedures)).


--End--
3.2.83 Source 87: CSM load end nack with the cause - checksum error Fault number 1052 : GSM entity downloading failure
Source:
(87) CSM load end nack with the cause "checksum error"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "checksum
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
653

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
654

Go to step 4.

above).

Procedures)).


--End--
3.2.84 Source 88: CSM load end nack with a bad cause
Source:
(88) CSM load end nack with a bad cause
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load end nack with a bad cause.
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
655

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
656

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


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

Source:
(89) No BTS response on CSM load end message
BTS model:
e-cell
FAULT ANALYSIS
This source indicates no BTS response on CSM load end message.

411-9001-104 18.05 2 February 2010
657
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-104 18.05 2 February 2010
658

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
659
3.2.86 Source 90: Bad report sent by BTS during an internal update
Source:
(90) Bad report sent by BTS during an internal update
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a bad report sent by BTS during an internal update.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).


411-9001-104 18.05 2 February 2010
660

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-104 18.05 2 February 2010
661

Procedures)).


--End--
3.2.87 Source 91: CSM load init nack with the cause - file already open
Source:
(91) CSM load init nack with the cause "file already open"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "file already
open".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
662

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
663

Go to step 4.

above).

Procedures)).


--End--
3.2.88 Source 92: CSM load init nack with the cause - invalid mode Fault number 1052 : GSM entity downloading failure
Source:
(92) CSM load init nack with the cause "invalid mode"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "invalid mode".
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-104 18.05 2 February 2010
664

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
665

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
3.2.89 Source 93: CSM load init nack with the cause - file cannot be
Source:
(93) CSM load init nack with the cause "file cannot be unloaded"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "file cannot be
unloaded".
411-9001-104 18.05 2 February 2010
666
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-104 18.05 2 February 2010
667

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
668
3.2.90 Source 94: CSM load init nack with the cause - flash flag cannot
Source:
(94) CSM load init nack with the cause "flash flag cannot
access"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "flash flag
cannot access".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
669

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-104 18.05 2 February 2010
670

Procedures)).


--End--
3.2.91 Source 95: CSM load data nack with the cause - file cannot be
Source:
(95) CSM load data nack with the cause "file cannot be
unloaded"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "file cannot
be unloaded".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
671

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
672

Go to step 4.

above).

Procedures)).


--End--
3.2.92 Source 96: CSM load data nack with the cause - flash flag
cannot access Fault number 1052 : GSM entity downloading failure
Source:
(96) CSM load data nack with the cause "flash flag cannot
access"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "flash flag
cannot access".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
673


Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
674

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
Source:
(97) CSM load data nack with the cause "boot cannot be
unloaded"
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
675
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "boot cannot
be unloaded".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-104 18.05 2 February 2010
676
3


Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


411-9001-104 18.05 2 February 2010
677

--End--
3.2.94 Source 98: CSM load data nack with the cause - data decode
Source:
(98) CSM load data nack with the cause "data decode error"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "data decode
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
678

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

411-9001-104 18.05 2 February 2010
679

above).

Procedures)).


--End--
3.2.95 Source 99: CSM load data nack with the cause - table cannot
Source:
(99) CSM load data nack with the cause "table cannot access"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "table cannot
access".
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-104 18.05 2 February 2010
680
Clear the alarm.


Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.

411-9001-104 18.05 2 February 2010
681

Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
3.2.96 Source 100: CSM load data nack with the cause - RAM mapping
Source:
(100) CSM load data nack with the cause "RAM mapping error"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "RAM mapping
error".
TROUBLESHOOTING
Step
Action
Preliminary checks
411-9001-104 18.05 2 February 2010
682



Clear the alarm.

Procedures) ).


above).

Procedures) ).




411-9001-104 18.05 2 February 2010
683
Clear the alarm.


concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
684
3.2.97 Source 101: CSM load data nack with the cause - flash access
Source:
(101) CSM load data nack with the cause "flash access error"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "flash access
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
685

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-104 18.05 2 February 2010
686

Procedures)).


--End--
3.2.98 Source 102: CSM load data nack with the cause - flash RAM
Source:
(102) CSM load data nack with the cause "flash RAM error"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "flash RAM
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
687

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
688

Go to step 4.

above).

Procedures)).


--End--
3.2.99 Source 103: CSM load data nack with the cause - flash erase
Source:
(103) CSM load data nack with the cause "lash erase error"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "lash erase
error".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
689

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
690

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
3.2.100 Source 104: CSM load data nack with the cause - internal abort
Source:
(104) CSM load data nack with the cause "internal abort"
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "internal
abort".
411-9001-104 18.05 2 February 2010
691
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-104 18.05 2 February 2010
692

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
693
3.2.101 Source 105: CSM flash activate response with a bad cause
Source:
(105) CSM flash activate response with a bad cause
BTS model:
E-cell
FAULT ANALYSIS
This source indicates a CSM flash activate response with a bad cause.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-104 18.05 2 February 2010
694

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-104 18.05 2 February 2010
695

Procedures)).


--End--
3.2.102 Source 106: DTM error during token allocation

Source:
(106) DTM error during token allocation
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a DTM error during token allocation.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-104 18.05 2 February 2010
696

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-104 18.05 2 February 2010
697

Go to step 4.

above).

Procedures)).


--End--
3.2.103 Source 107: CSM software update report with the cause: TRX
software incompatibility
Source:
(107) CSM software update report with the cause: TRX software
incompatibility
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a CSM software update report with the cause: TRX
software incompatibility.
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-104 18.05 2 February 2010
698


Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-104 18.05 2 February 2010
699

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
3.2.104 Source 108: Too many different deliveries in the cell group
Source:
(108) Too many different deliveries in the cell group
BTS model:
e-cell
FAULT ANALYSIS
This source indicates too many different deliveries in the cell group.

411-9001-104 18.05 2 February 2010
700
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-104 18.05 2 February 2010
701

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-104 18.05 2 February 2010
702

Fault number:
1053
Type
qualityOfServiceAlarm
FAULT ANALYSIS
The BSC detects a difference of the state between that known by the BSC
and that received from the BTS after a status request.

BSC defense
The BSC tries to restart the BTS, to download it again and to reconfigure
it.
CAUTION
For as long as the operationalState of the btsSiteManager
object is "disabled-failed", the site is lost.
CAUTION
Service reduction
ment object is "disabled", the TRX and one TDMA are lost.
TROUBLESHOOTING
Preliminary checks
Step
Action
Look for a fault number 1067 concerning an item of equipment of

the object mentioned in the alarm (fault number 1053). If there is
not any alarm with the fault number 1067, go to step 2.


411-9001-104 18.05 2 February 2010
703

step 4.


"disabled-failed", the site is not operational. Go to step 3.

Wait for the end of restart.
If the alarm persists, call the manufacturer. Go to step 4.

--End--

Fault number:
1054
Loss of layer 2 (or no establishment) with remote GSM entity
Type
communicationsAlarm

Fault number:
1055
Type
communicationsAlarm
FAULT ANALYSIS
The BSC sends a spontaneous message 1055 when it receives a
non-acknowledgement message (NACK) from a BTS after a configuration
message.

411-9001-104 18.05 2 February 2010
704
The following Table 45 "Fault number 1055 sources" (page 704) indicates
all the sources of the fault number 1055 for the e-cell. For more
information on each source, see the indicated paragraph to know the
corrective maintenance procedure associated with this source.
Table 45
Source
No.
Source wording
Paragraph
Equipment failure
Equipment unable to perform such

test
Invalid configuration
Unknown test
Cell parameters inconistency
Data inconsistency

(page 712)
Value out of range

(page 713)
TEI not present
Unknown Abis PCM_Time_Slot
10
Unknown Abis PCM
11
Wrong software reference
12
Further files required
13
Failure during activation
14
Data format error

(page 716)
15
Window overflow

(page 716)
16
Normal completion
17
Transfer aborted

(page 707)
perform such test (page 708)
perform such configuration (page 709)
3.5.4 Source 4: Unknown test (page 710)
3.5.5 Source 5: Cell parameters
inconsistency (page 710)
3.5.8 Source 8: TEI not present (page 713)

PCM_Time_Slot (page 714)
PCM (page 714)
3.5.11 Source 11: Wrong software
(page 715)
activation (page 716)

(page 716)
(page 716)

411-9001-104 18.05 2 February 2010
705
Table 45
Source
No.
Source wording
Paragraph
18
Checksum error

(page 717)
19
File incomplete

(page 717)
20
File already present and correct
21
File cannot be downloaded
22
Entity engaged in other download
23
Too many signaling timeslots
3.5.23 Source 23: Too many signaling

timeslots (page 718)
24
Too many TEI connections to

physical channel
3.5.24 Source 24: Too many TEI

connections to physical channel (page 719)
25
Out of sequence message
26
Incorrect IEI
27
Wrong file reference
28
Bad cell number

(page 722)
29
Bad related TEI

(page 722)
30
Bad timeslot
31
Window size not allowed
32
Flash boot required
33
Wrong config reference
34
The BTS has not acknowledged the

TX power consign request
35
Downloading aborted
36
Files missing
3.5.20 Source 20: File already present

and correct (page 717)
downloaded (page 717)
3.5.22 Source 22: Entity engaged in
other download (page 718)
3.5.25 Source 25: Out of sequence

message (page 719)
3.5.26 Source 26: Incorrect IEI (page 721)
(page 722)
3.5.30 Source 30: Bad timeslot (page 722)

3.5.31 Source 31: Window size not
allowed (page 722)
(page 723)
3.5.33 Source 33: Wrong config
3.5.34 Source 34: The BTS has not
acknowledged the TX power consign
request (page 723)
aborted (page 728)
3.5.36 Source 36: Files missing (page 728)

411-9001-104 18.05 2 February 2010
706
Table 45
Source
No.
Source wording
Paragraph
37
Buffer overflow
38
Block not received
39
Downloading restart
40
Request not supported
41
Downloading failure
42
Start up failure
43
Maximum number of joker TS
44
Bad chain type
45
Bad radio timeslot reference
46
Bad internal link EDGE configuration
47
Inconsistency mapping
48
Inconsistency number of joker DS0
49
Invalid mode
50
File already open
51
File cannot be unloaded

unloaded (page 734)
52
Boot cannot be unloaded
3.5.52 Source 52: Boot cannot be

unloaded (page 734)
53
Data decode error
54
Flash flag cannot access
55
Table cannot access

(page 729)
(page 729)
restart (page 729)
(page 729)
failure (page 729)
(page 730)
3.5.43 Source 43: Maximum number
of joker TS (page 730)
(page 733)
3.5.45 Source 45: Bad radio timeslot
3.5.46 Source 46: Bad internal Link EDGE
configuration (page 733)
3.5.47 Source 47: Inconsistency
mapping (page 733)
3.5.48 Source 48: Inconsistency number
3.5.49 Source 49: Invalid mode (page 734)
(page 734)

(page 735)
3.5.54 Source 54: Flash flag cannot
access (page 735)
3.5.55 Source 55: Table cannot
access (page 735)

411-9001-104 18.05 2 February 2010
707
Table 45
Source
No.
Paragraph
Source wording
56
RAM mapping error
3.5.56 Source 56: RAM mapping

error (page 735)
57
Flash access error

(page 735)
58
Flash write error

(page 736)
59
Flash erase error

(page 736)
60
Internal abort
61
Equipment not able to get external

synchronization
62
Synchronization in progress
63
Dynamic Abis feature not supported
3.5.63 Source 63: Dynamic Abis feature

not supported (page 737)
64
Inconsistent number of Joker DS0
3.5.64 Source 64: Inconsistent number

255
Non-significant value

(page 736)
3.5.61 Source 61: Equipment not able to
get external synchronization (page 736)
3.5.62 Source 62: Synchronization in
progress (page 736)
3.5.66 Source 255: Non-significant

value (page 742)
FAULT LOCATION
The objects to suspect are as follows:
the btsSiteManager
the bts
the transceiver
the transceiverEquipment

Source:
(1) Equipment failure
BTS model:
e-cell
FAULT ANALYSIS
This source indicates an equipment failure.

411-9001-104 18.05 2 February 2010
708
3.5.2 Source 2: Equipment unable to perform such test

Source:
(2) Equipment unable to perform such test
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that the PCM number, the cell number, and/or the
number of timeslots declared at the OMC-R are higher than those of the
hardware configuration of the BTS.

BSC defense None.
CAUTION
No service is provided.
For the bts object
CAUTION
CAUTION
Service reduction
CAUTION
Service reduction
TROUBLESHOOTING
Modify the parameters declared at the OMC-R.

411-9001-104 18.05 2 February 2010
709
3.5.3 Source 3: Equipment unable to perform such configuration

Source:
(3) Equipment unable to perform such configuration
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that the TRX configuration is not possible because of
a DRX frequency band error.

BSC defense The BSC unconfigures the tranceiverEquipment object
concerned by the alarm.
ATTENTION
TROUBLESHOOTING
Step
Action
Perform a "Display" command on the bts object.

The "standardIndicator" parameter indicates the frequency
band associated with the DRX module: "gsm", "extended gsm",
"dcs1800", "pcs1900", "R gsm", "gsmdcs" or "dcsgsm".
If the "standardIndicator" parameter is "gsmdcs", perform a

If the "standardIndicator" parameter is "dcsgsm", perform a

Check the DRX frequency band declared at the OMC-R with the
PEC or CPC code of the DRX present in the cabinet.

411-9001-104 18.05 2 February 2010
710
If the DRX frequency band is the same as the one indicated

by the "transceiverEquipmentClass" parameter, clear the
If the DRX frequency band is not the same as the one

indicated by the "transceiverEquipmentClass" parameter and
if the DRX has just been replaced, go to step 3, otherwise,
go to step 4.
The alarm may be due to an error in the DRX replacement. So

replace the DRX (Field Replaceable Unit) by:
setting the administrativeState of the transceiverEquipment

object corresponding to the faulty DRX to "locked"
CAUTION
Service reduction
In most cases, the transceiverEquipment and one
transceiver are lost.
replacing the DRX module. see :

Nortel GSM BTS e-cell Troubleshooting (411-9001-090)f
or the e-cell
Go to step 4.
4
Make sure that the DRX used is correct, so modify the value of
the "transceiverEquipmentClass" parameter according to the
DRX frequency band. Go to step 5.

--End--

Source:
(4) Unknown test
BTS model:
e-cell
FAULT ANALYSIS
This source indicates an unknown test.
3.5.5 Source 5: Cell parameters inconsistency

Source:
(5) Cell parameters inconsistency
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
711
FAULT ANALYSIS
This alarm indicates that at least one TEI of the list is included in another
bts object than that the cell specified. The list of TEI contains twice the
same TEI.

BSC defense None.
For the bts object
CAUTION
CAUTION
Service reduction
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Perform a "Display" command on the affected transceiverEqui

pment object.
The "teiTransceiverEqpt" parameter indicates the TEI value
associated with the TRX module.
The value of the "teiTransceiverEqpt" parameter should be within
the range specified by the S8000 BTS engineering rules for the
corresponding configuration reference and associated DLUs.
Lock the affected transceiverEquipment object.
Change the value of "teiTransceiverEqpt" so that it conforms to

the engineering rules specified above.
Unlock the transceiverEquipment object.

411-9001-104 18.05 2 February 2010
712

--End--

Source:
(6) Data inconsistency
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that the PCM list contains PCM identical numbers.

BSC defense None.
CAUTION
No service is provided.
For the bts object
CAUTION
ATTENTION
ATTENTION

411-9001-104 18.05 2 February 2010
713
TROUBLESHOOTING
Step
Action
Check the PCM cabling.
If the cabling is correct, go to step 2.

If the cabling is not correct, replace the cables if necessary.
Check the configuration associated with the object at the

OMC-R. If necessary, modify the PCM numbers declared at the
OMC-R.

--End--

Source:
(7) Value out of range
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates a value out of range.

Source:
(8) TEI not present
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that the TEI of the associated transceiver equipment
is:
not between 32 and 55
or
is not in the permitted list of TEI of the corresponding CELL

Configuration

411-9001-104 18.05 2 February 2010
714

BSC defense None.
CAUTION
Service reduction
CAUTION
Service reduction
3.5.9 Source 9: Unknown Abis PCM_Time_Slot

Source:
(9) Unknown Abis PCM_Time_Slot
BTS model:
e-cell
FAULT ANALYSIS
This source indicates an unknown Abis PCM Time Slot.
3.5.10 Source 10: Unknown Abis PCM

Source:
(10) Unknown Abis PCM
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that the PCM is not present in the PCM list.

BSC defense None.

411-9001-104 18.05 2 February 2010
CAUTION
For the bts object
CAUTION
CAUTION
Service reduction
CAUTION
Service reduction
TROUBLESHOOTING
Parametrize the PCM declared unknown at the OMC-R.
3.5.11 Source 11: Wrong software reference

Source:
(11) Wrong software reference
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a wrong software reference.

Source:
(12) Further files required
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
715
716
FAULT ANALYSIS
This source indicates that further files are required.
3.5.13 Source 13: Failure during activation

Source:
(13) Failure during activation
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a failure during activation.

Source:
(14) Data format error
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a data format error.

Source:
(15) Window overflow
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a window overflow.

Source:
(16) Normal completion
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a normal completion.

Source:
(17) Transfer aborted
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
FAULT ANALYSIS
This source indicates an aborted transfer.

Source:
(18) Checksum error
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a checksum error.

Source:
(19) File incomplete
BTS model:
e-cell
FAULT ANALYSIS
This source indicates an incomplete file.
3.5.20 Source 20: File already present and correct

Source:
(20) File already present and correct
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a file already present and correct.
3.5.21 Source 21: File cannot be downloaded

Source:
(21) File cannot be downloaded
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that the file cannot be downloaded.

411-9001-104 18.05 2 February 2010
717
718
3.5.22 Source 22: Entity engaged in other download

Source:
(22) Entity engaged in other download
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that the entity is engaged in other download.
3.5.23 Source 23: Too many signaling timeslots

Source:
(23) Too many signaling timeslots
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates the value of signaling timeslot number is higher than
6.

BSC defense None.
CAUTION
For the bts object
CAUTION

411-9001-104 18.05 2 February 2010
CAUTION
Service reduction
CAUTION
Service reduction
TROUBLESHOOTING
Modify the value of the signaling timeslot number.
3.5.24 Source 24: Too many TEI connections to physical channel

Source:
(24) Too many TEI connections to physical channel
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that there are too many TEI connections to the
physical channel.
3.5.25 Source 25: Out of sequence message

Fault number 1055:
Source:
(25) Out of sequence message
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that the message of site configuration has been
received twice but with different values. The message is not accepted
because of the state of the BTS.

BSC defense None.

411-9001-104 18.05 2 February 2010
719
720
CAUTION
For the bts object
CAUTION
CAUTION
Service reduction
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Check the configuration associated with the object.
For the btsSiteManager object:

Check the logical configuration of the btsSiteManager
object (teiBtsSiteManager, bscSitePcmList, radioSiteMask
parameters).
If it is not correct, perform the "Display hardware
For the bts object

a. Check the logical configuration of the bts object and its
objects.

411-9001-104 18.05 2 February 2010


configuration" command on the btsSiteManager to
721
b. In the case of the base unit associated with the extension

unit, set the btsSiteManager object to "locked" then to
"unlocked".

a. Set the administrativeState of the transceiver object to
"shuttingDown".
b. Check the logical configuration of the transceiver object
(channelType, absoluteRFChannelNo parameters for
each channel).
c. Set the administrativeState of the transceiver object to
"unlocked".

Check the logical configuration of the transceiverEquipment
object (teiTransceiverEqpt parameter).

2

--End--

Source:
(26) Incorrect IEI
BTS model:
e-cell
FAULT ANALYSIS
This source indicates an incorrect IEI.

411-9001-104 18.05 2 February 2010
722

Source:
(27) Wrong file reference
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a wrong file reference.

Source:
(28) Bad cell number
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a bad cell number.

Source:
(29) Bad related TEI
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a bad related TEI.

Source:
(30) Bad timeslot
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a bad timeslot.
3.5.31 Source 31: Window size not allowed

Source:
(31) Window size not allowed
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that the window size is not allowed.

411-9001-104 18.05 2 February 2010
723

Source:
(32) Flash boot required
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that a flash boot is required.
3.5.33 Source 33: Wrong config reference

Source:
(33) Wrong config reference
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a wrong config reference.
3.5.34 Source 34: The BTS has not acknowledged the TX power
consign request
Source:
(34) The BTS has not acknowledged the TX power

consign request
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that the power, configured at the OMC-R for the TX
concerned, is not compatible with the TX hardware.

BSC defense The BSC unconfigures the faulty transceiverEquipment
object and the associated transceiver object. It tries to assure a minimum
service of communication by unconfiguring and reconfiguring the
transceiver object.
At least one TRX is lost.
CAUTION
Service reduction
It is possible to lose the whole cell linked to the faulty TRX.

411-9001-104 18.05 2 February 2010
724
CAUTION
of service loss.
TROUBLESHOOTING
Preliminary checks
Step
Action



Look for an object whose state is "disabled-failed" and
treat the problem in order that the btsSiteManager object
becomes "enabled".

Do not treat the alarm and do not clear it.
Look for other alarms and treat the problem in order that
the btsSiteManager object becomes "enabled". If a fault
number 1054 (loss of layer 2) has appeared, see the
fault number 1054 (see Nortel GSM BSS Fault Clearing Advanced Maintenance (411-9001-105) ).

object is "disabled", do not treat the alarm and do
not clear it. Wait that the state of the btsSiteManager
object becomes "enabled", "disabled-dependency", or
"disabled-failed".
Check that the alarm on the TX module is valid, by performing


411-9001-104 18.05 2 February 2010
725
If the state of the "TX" equipment is "failed", the fault is

If the state of the "TX" equipment is "working", the fault is not




the attenuation of the combiner must be between 31dBm and
The following table allows to know directly the good values of the
the BTS. The "Nack" value is not admitted.
e-cell (ind)
BTS model
Combiners
H2
H4
H2D
Cavity/
Duplexer
DLU
attenuation
51 to 45
Nack
Nack
Nack
Nack
Nack
Nack
Nack
44
Nack
Nack
Nack
Nack
Nack
Nack
Nack
43
Nack
Nack
Nack
Nack
Nack
Nack
Nack
42
Nack
Nack
Nack
Nack
Nack
Pmax
Nack
41
Nack
Nack
Nack
Pmax
Nack
Pmax
Pmax
40
Pmax
Nack
Pmax
Pmax
Pmax
Pmax-2
Pmax
39
Pmax
Nack
Pmax
Pmax-2
Pmax
Pmax-2
Pmax-2
38
Pmax-2
Nack
Pmax-2
Pmax-2
Pmax-2
Pmax-4
Pmax-2
37
Pmax-2
Pmax
Pmax-2
Pmax-4
Pmax-2
Pmax-4
Pmax-4
Cavity
bsTxPwrMax

411-9001-104 18.05 2 February 2010
726
e-cell (ind)
BTS model
Combiners
H2
H4
H2D
Cavity/
Duplexer
DLU
attenuation
36
Pmax-4
Pmax
Pmax-4
Pmax-4
Pmax-4
Pmax-6
Pmax-4
35
Pmax-4
Pmax-2
Pmax-4
Pmax-6
Pmax-4
Pmax-6
Pmax-6
34
Pmax-6
Pmax-2
Pmax-6
Pmax-6
Pmax-6
Pmax-8
Pmax-6
33
Pmax-6
Pmax-4
Pmax-6
Pmax-8
Pmax-6
Pmax-8
Pmax-8
32
Pmax-8
Pmax-4
Pmax-8
Pmax-8
Pmax-8
Pmax-10
Pmax-8
31
Pmax-8
Pmax-6
Pmax-8
Pmax-10
Pmax-8
Pmax-10
Pmax-10
30
Pmax-10
Pmax-6
Pmax-10
Pmax-10
Pmax-10
Pmax-12
Pmax-10
29
Pmax-10
Pmax-8
Pmax-10
Pmax-12
Pmax-10
Pmax-12
Pmax-12
28
Pmax-12
Pmax-8
Pmax-12
Pmax-12
Pmax-12
Nack
Pmax-12
27
Pmax-12
Pmax-10
Pmax-12
Nack
Pmax-12
Nack
Nack
26
Nack
Pmax-10
Nack
Nack
Nack
Nack
Nack
25
Nack
Pmax-12
Nack
Nack
Nack
Nack
Nack
24
Nack
Pmax-12
Nack
Nack
Nack
Nack
Nack
23
Nack
Nack
Nack
Nack
Nack
Nack
Nack
22 to 21
Nack
Nack
Nack
Nack
Nack
Nack
Nack
Cavity
bsTxPwrMax
BTS model
e-cell (Outdoor)
Combiners
Duplexer
H2
DLU
attenuation
51 to 45
Nack
Nack
Nack
44
Nack
Nack
Nack
43
Pmax
Nack
Nack
42
Pmax
Pmax
Nack
41
Pmax-2
Pmax
Nack
40
Pmax-2
Pmax-2
Pmax
39
Pmax-4
Pmax-2
Pmax
38
Pmax-4
Pmax-4
Pmax-2
37
Pmax-6
Pmax-4
Pmax-2
36
Pmax-6
Pmax-6
Pmax-4
bsTxPwrMax

411-9001-104 18.05 2 February 2010
BTS model
727
e-cell (Outdoor)
Combiners
Duplexer
H2
DLU
attenuation
35
Pmax-8
Pmax-6
Pmax-4
34
Pmax-8
Pmax-8
Pmax-6
33
Pmax-10
Pmax-8
Pmax-6
32
Pmax-10
Pmax-10
Pmax-8
31
Pmax-12
Pmax-10
Pmax-8
30
Pmax-12
Pmax-12
Pmax-10
29
Nack
Pmax-12
Pmax-10
28
Nack
Nack
Pmax-12
27
Nack
Nack
Pmax-12
26
Nack
Nack
Nack
25
Nack
Nack
Nack
24
Nack
Nack
Nack
23
Nack
Nack
Nack
22 to 21
Nack
Nack
Nack
bsTxPwrMax

Replaceable Unit). see the replacement procedure given in:
or the e-cell
Then go to step 6.
5
Modify the value of the "bsTxPwrMax" parameter according to

the attenuation of the combiner and reduced of the value of the

411-9001-104 18.05 2 February 2010
728
ATTENTION
This parameter must not be filled in for the "dual band" or "dual
coupling" values of the "concentric cell" parameter.

the BTS. The "Nack" value is not admitted. However, do not
forget to consider the "transceiver zone Ref" parameter.

Replaceable Unit). see the replacement procedure given in:
or the e-cell
Then go to step 6.
Additional checks
Clear the alarm.

--End--
3.5.35 Source 35: Downloading aborted

Source:
(35) Downloading aborted
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that the downloading has been aborted.

Source:
(36) Files missing
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that files are missing.

411-9001-104 18.05 2 February 2010

Source:
(37) Buffer overflow
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a buffer overflow.

Source:
(38) Block not received
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that a block has not been received.
3.5.39 Source 39: Downloading restart

Source:
(39) Downloading restart
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a downloading restart.

Source:
(40) Request not supported
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a request not supported.
3.5.41 Source 41: Downloading failure

Source:
(41) Downloading failure
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a downloading failure..

411-9001-104 18.05 2 February 2010
729
730

Source:
(42) Start-up failure
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a start-up failure.
3.5.43 Source 43: Maximum number of joker TS

Source:
(43) Maximum number of joker TS
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that there an inconsistency between the number of
joker TS requested by the operator and the BTS capability.
Joker TS provisioning per TDMA is dependent on hardware constraints
(both BCF/CBCF chains must have the same type of hardware) and also
on existing backhaul configuration.

BSC defense The transceiver object is not configured by the BSC.
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-104 18.05 2 February 2010
731

refer to the fault number 1054 (see 411-9001-105 (Nortel
Procedures) ).
and process the problem in order that the btsSiteManager
object becomes "enabled".

"disabled-failed", the site is not operational. Do not process
the alarm and do not clear it. Look for other alarms and
process the problem in order that the btsSiteManager object
becomes "enabled".

object is "disabled", do not process the alarm and do
not clear it. Wait for the state of the btsSiteManager
object to become "enabled", "disabled-dependency", or
"disabled-failed".
alarm persists.
Explore the site capability:

a Perform a "Display hardware information" command
("standard" mode) on the btsSiteManager object at the
OMC-R.
The OMC-R displays the site type (BCF, or CBCF with CMCF
phase 1 or phase 2) and state (working or failed).
b Perform a "Display data information" command (with "EDGE"
option) on the btsSiteManager object at the OMC-R.
The OMC-R displays the GPRS and EDGE capabilities
of each TRX. This will give the maximum number of joker
TS supported by the BCF/CBCF and TRXs. Look for the
following items of information:
Hardware btsSiteManager capability

Max number of timeslot per transceiverEquipment
for active board (main + joker): see Table 46

411-9001-104 18.05 2 February 2010
732
"Maximum number of TS (main and joker) per

Max number of timeslot per transceiverEquipment for
passive board (main + joker):
Duplex site consistency: "identical capabilities" / "non
identical capabilities"
Hardware transceiverEquipment capability

Max number of timeslot (main + joker): see Table
46 "Maximum number of TS (main and joker) per
GPRS capability: "up to CSx"
EDGE capability: "full" / "none"
As a reminder, here are the permitted maximum
values:
Table 46
Maximum number of TS (main and joker) per transceiverEquipment
Type of site
Maximum number of timeslot (main + joker) per

transceiverEquipment
BCF old GTW PROM
BCF new GTW PROM
CBCF CMCF phase 1
CBCF CMCF phase 2
Check the configuration of the transceiver object concerned, and

compare it with the capabilities analyzed in step 2.
As a reminder, here are the value ranges of the parameters
related to joker TS:
numberOfJokerDS0
[0..4] for S8000 BCF
[0..6] for S8000 CBCF
jokerPerMainTarget
[0..4]
The recommended values are 2, 3 or 4, depending on
operator Abis configuration (numberOfJokerDS0) and
estimated EDGE TDMA throughput.
If the configuration is not correct, set the transceiver object

to "locked".

411-9001-104 18.05 2 February 2010
733

Set the transceiver object to "unlocked".
If the configuration is correct, save the information gathered

in step 2, as well as the site configuration, and then call the
manufacturer.

--End--

Source:
(44) Bad chain type
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a bad chain type.
3.5.45 Source 45: Bad radio timeslot reference

Source:
(45) Bad radio timeslot reference
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a bad radio timeslot reference.
3.5.46 Source 46: Bad internal Link EDGE configuration

Source:
(46) Bad internal Link EDGE configuration
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a bad internal link EDGE configuration.
3.5.47 Source 47: Inconsistency mapping

Source:
(47) Inconsistency mapping
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
734
FAULT ANALYSIS
This source indicates an inconsistency mapping.
3.5.48 Source 48: Inconsistency number of joker DS0

Source:
(48) Inconsistency number of joker DS0
BTS model:
e-cell
FAULT ANALYSIS
This source indicates an inconsistency number of joker DS0.

Source:
(49) Invalid mode
BTS model:
e-cell
FAULT ANALYSIS
This source indicates an invalid mode.

Source:
(50) File already open
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that the file is already open.
3.5.51 Source 51: File cannot be unloaded

Source:
(51) File cannot be unloaded
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that the file cannot be unloaded.
3.5.52 Source 52: Boot cannot be unloaded

Source:
(52) Boot cannot be unloaded
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
FAULT ANALYSIS
This source indicates that the boot cannot be unloaded.

Source:
(53) Data decode error
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a data decode error.
3.5.54 Source 54: Flash flag cannot access

Source:
(54) Flash flag cannot access
BTS model:
e-cell
FAULT ANALYSIS
This source indicates an access problem to the flash flag.
3.5.55 Source 55: Table cannot access

Source:
(55) Table cannot access
BTS model:
e-cell
FAULT ANALYSIS
This source indicates an access problem to a table.
3.5.56 Source 56: RAM mapping error

Source:
(56) RAM mapping error
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a RAM mapping error.

Source:
(57) Flash access error
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
735
736
FAULT ANALYSIS
This source indicates a flash access error.

Source:
(58) Flash write error
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a flash write error.

Source:
(59) Flash erase error
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a flash erase error.

Source:
(60) Internal abort
BTS model:
e-cell
FAULT ANALYSIS
This source indicates an internal abort.
3.5.61 Source 61: Equipment not able to get external synchronization

Source:
(61) Equipment not able to get external synchronization
BTS model:
e-cell
FAULT ANALYSIS
This source indicates that an equipment is not able to get the external
synchronization.
3.5.62 Source 62: Synchronization in progress

Source:
(62) Synchronization in progress
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
737
FAULT ANALYSIS
This source indicates a synchronization in progress.
3.5.63 Source 63: Dynamic Abis feature not supported

Source:
(63) Dynamic Abis feature not supported
BTS model:
e-cell
FAULT ANALYSIS
At the reception of a "site config" message with dynamic Abis feature
activated, if one of the CMCF of the BTS is a phase 1, a "site config Nack"
message with the cause Dynamic Abis feature not supported is sent to
the BSC. The BSC must stop the configuration of the BTS.
Besides, in case of inconsistencies detected by the BTS, the BTS sends a
"traffic connect Nack" message with the cause Dynamic Abis feature not
supported (in response of a received "traffic connect" message)
Moreover in case a BTS is equipped with an eDRX that supports the
dynamic Abis feature, but with an S8000 BCF, then the dynamic Abis
feature is not supported by the BTS.
BSC defense
The BSC stops the configuration of the BTS.
CAUTION
Service reduction
The BTS is not configured.
TROUBLESHOOTING
Modify the BTS configuration:
either deactivate the dynamic Abis feature

or upgrade the BTS (replace CMCF phase 1 with CMCF phase 2, or
replace BCF with CBCF)

411-9001-104 18.05 2 February 2010
738
3.5.64 Source 64: Inconsistent number of joker DS0

Source:
(64) Inconsistent number of joker DS0
BTS model:
e-cell
FAULT ANALYSIS
message)
connect message) with the cause 64 "Inconsistent number of joker DS0".
Then this alarm indicates that the number of DS0 inside one poolRef
exceeds the pool maximum capability.
BSC defense
None.
CAUTION
Service reduction
TROUBLESHOOTING
Preliminary checks
Step
Action



411-9001-104 18.05 2 February 2010
739
Clear the alarm.


concerning cells.
Procedures)).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
740


--End--
3.5.65 Source 65: Exceeded DL joker DS0 pool number

Source:
(65) Exceeded DL joker DS0 pool number
BTS model:
e-cell
FAULT ANALYSIS
message)
connect message) with the cause 65 "Exceeded DL joker DS0 pool
number".
BSC defense
None.
CAUTION
Service reduction
TROUBLESHOOTING

411-9001-104 18.05 2 February 2010
741
Procedure 4
Preliminary checks
Step
Action


Clear the alarm.

concerning cells.
Procedures)).


above).

Procedures)).


411-9001-104 18.05 2 February 2010
742



--End--
3.5.66 Source 255: Non-significant value

Source:
(255) Non-significant value
BTS model:
e-cell
FAULT ANALYSIS
This source indicates a non-significant value.

Fault number:
1058
Type

An entity of the BTS detects an anomaly in its configuration, reports it to
the BSC by this alarm, and de-configures itself.
BSC defense
If the site is already operational, the BSC unconfigures the

btsSiteManager object and tries to reconfigures it.
If the site is not operational, there is a problem of connection between

the connections and the connections declared at the OMC-R.

411-9001-104 18.05 2 February 2010
743
CAUTION
For as long as the operationalState of the btsSiteManager is
"disabled-failed", the site is lost.
CAUTION
Service reduction
ment is "disabled", the TRX and one TDMA are lost.
TROUBLESHOOTING
Step
Action
Set the pcmCircuit object to "locked".
Untwine the PCM links.
Set the pcmCircuit object to "unlocked".


--End--

Fault number:
1059
Invalid message received on Abis interface on O and M link
Type
communicationsAlarm
FAULT ANALYSIS
The BSC receives a message from the BTS that it cannot treat because:
either this message is out of sequence

or this message concerns an unknown element, that is a distant item of
equipment not created at the OMC-R but emitting notifications

411-9001-104 18.05 2 February 2010
744

BSC defense
None.

None.
TROUBLESHOOTING
In the case of a message on an unknown element (not declared at the

OMC-R), switch off this element.
Otherwise, do nothing.
CAUTION
Working instructions
If several fault numbers 1059 are detected by the same cell, call
the manufacturer.

Fault number:
1060
Type
equipmentAlarm
The spontaneous message 1060 corresponds to a warning and does not

require a maintenance action, except in conjunction with the 1067 fault
number.
The following table indicates all the sources of the fault number 1060
for the e-cell. For more information on each source, see the indicated
paragraph to know the corrective maintenance procedure associated with
this source.
Equipme
nt
PMNU
source No.
Paragraph
Source wording
3145730
Message unknown
3.8.1 PMNU (source: Message

unknown) (page 746)
3145732
Loss of GSM clock
3145752
LAPD congestion
3145760
3.8.2 PMNU (source: Restart due

to reset by BSC) (page 746)
3145761

button
3.8.3 PMNU (source: Restart due to

reset by reset button) (page 746)
3145762

to power on) (page 746)

411-9001-104 18.05 2 February 2010
Equipme
nt
PMOD
745
source No.
Source wording
Paragraph
3145763

scanning

to a too long PCM scanning)
(page 747)
3145764
Restart requested by the

active board
3.8.6 PMNU (source: Restart

requested by the active board)
(page 747)
3145765
Restart due to a software

upgrade
3.8.7 PMNU (source: restart due to

a software upgrade) (page 747)
3145766
Restart due to hardware

watchdog
3.8.8 PMNU (source: Restart due to

a hardware watchdog) (page 748)
3145767
Restart due to loss of lock
3211263
Software dump
3276803
Loss of PCM link
3276823
FACCH congestion
3276826
Underrun
3276834
PMOD reset by BCF after

message non acknowledged
3.8.11 PMOD (source: PMOD

reset by BCF after message non
acknowledged) (page 749)
3277060
Restart due to the timeout on

the OML link with BSC
3.8.12 PMOD (source: Restart

due to the timeout on the OML link
with BSC) (page 749)
3277061
Restart due to the timeout on

the OML link with BCF
3.8.13 PMOD (source: Restart

due to the timeout on the OML link
with BCF) (page 750)
3277062
Restart due to a software

upgrade
3.8.14 PMOD (source: Restart due

to a software upgrade) (page 750)
3277074
BCCH config dump
3277090
SACCH config dump
3277106
L1M config dump
3277107
RSL anomaly
PMOD

to loss of lock) (page 748)
3.8.10 PMOD (source: FACCH

congestion) (page 748)
-
3.8.15 PMOD (source: BCCH

config dump) (page 750)
3.8.16 PMOD (source: SACCH
config dump) (page 751)
3.8.17 PMOD (source: L1M config
dump) (page 751)
3.8.18 PMOD (source: RSL
anomaly) (page 751)

411-9001-104 18.05 2 February 2010
746
3.8.1 PMNU (source: Message unknown)

Fault number 1060
Equipment:
PMNU
Source :
(3145730) Message unknown
BTS model :
e-cell
FAULT ANALYSIS
This alarm indicates an unknown Abis message.

BSC defense None.
3.8.2 PMNU (source: Restart due to reset by BSC)

Fault number 1060
Equipment:
PMNU
Source:
(3145760) Restart due to reset by BSC
BTS model :
e-cell
FAULT ANALYSIS
This alarm indicates a restart of the PMNU due to a reset by the BSC.
3.8.3 PMNU (source: Restart due to reset by reset button)

Fault number 1060
Equipment:
PMNU
Source:
(3145761) Restart due to reset by the reset button
BTS model :
e-cell
FAULT ANALYSIS
This alarm indicates a restart of the PMNU due to a reset by the reset
button.
3.8.4 PMNU (source: Restart due to power on)

Fault number 1060
Equipment:
PMNU
Source:
(3145762) Restart due to power on
BTS model :
e-cell

411-9001-104 18.05 2 February 2010
FAULT ANALYSIS
This alarm indicates a restart of the PMNU due to a power on.
3.8.5 PMNU (source: Restart due to a too long PCM scanning)

Fault number 1060
Equipment:
PMNU
Source:
(3145763) Restart due to a too long PCM scanning
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates a restart of the PMNU due to a too long PCM
scanning.
3.8.6 PMNU (source: Restart requested by the active board)

Fault number 1060
Equipment:
PMNU
Source:
(3145764) Restart requested by the active board
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates a restart of the PMNU is requested by the active
board.
3.8.7 PMNU (source: restart due to a software upgrade)

Fault number 1060
Equipment:
PMNU
Source:
BTS model :
e-cell
FAULT ANALYSIS
This alarm indicates a restart of the PMNU due to a software upgrade.

411-9001-104 18.05 2 February 2010
747
748
3.8.8 PMNU (source: Restart due to a hardware watchdog)

Fault number 1060
Equipment :
PMNU
Source:
(3145766) Restart due to a hardware watchdog
BTS model :
e-cell
FAULT ANALYSIS
This alarm indicates a restart of the PMNU due to a hardware watchdog.
3.8.9 PMNU (source: Restart due to loss of lock)

Fault number 1060
Equipment:
PMNU
Source:
(3145767) Restart due to loss of lock
BTS model :
e-cell
FAULT ANALYSIS
This alarm indicates a restart of the PMNU due to loss of lock.
3.8.10 PMOD (source: FACCH congestion)

Fault number 1060
Equipment:
PMOD
Source:
(3276823) FACCH congestion
BTS model:
e-cell
FAULT ANALYSIS
FACCH "Fast associated Control Channel" is one of the dedicated control
channels.
It is associated to a TCH channel and is used to exchange fast signaling
messages with the MS.
In compliance with GSM Rec. 5.03, a FACCH for TCH/FR is coded
over 8 bursts and for TCH/HR over 6 bursts. This imposes a maximum
transmission rate for FACCH messages, above which the messages are
queued. The queuing mechanism allows for up to 3 FACCH messagesfor
each channel (per sub-channel for TCH/HR) to be waiting for transmission.

411-9001-104 18.05 2 February 2010
749
When this limit is exceeded, the BTS sends the notification FACCH
Congestion and the waiting messages are discarded. A Timer mechanism
ensures that the dropped messages are repeated.
FACCH congestion is usually linked to handover activity (for speed and
priority reasons, FACCH channel is especially used for handover process).
Increased handover activity equals a greater risk of FACCH congestion.

BSC defense
None

The only impact is that handovers may be delayed by up to 160 ms, the
time between 2 repetitions of the FACCH message.
There will no impact on the counters and no dropped calls, nor service
denied.
TROUBLESHOOTING
3.8.11 PMOD (source: PMOD reset by BCF after message non

acknowledged)
Fault number 1060
Equipment:
PMOD
Source:
(3276834) PMOD reset by BCF after message non

acknowledged
BTS model :
e-cell
FAULT ANALYSIS
This alarm indicates that the PMOD is reset by the BCF after a
non-acknowledged message.
BSC)
Fault number 1060
Equipment:
PMOD
Source:
(3277060) Restart due to the timeout on the OML link

with BSC
BTS model :
e-cell

411-9001-104 18.05 2 February 2010
750
FAULT ANALYSIS
This alarm indicates that the PMOD is restarted due to the timeout on the
OML link with BSC.
BCF)
Fault number 1060
Equipment:
PMOD
Source:
(3277061) Restart due to the timeout on the OML link

with BCF
BTS model :
e-cell
FAULT ANALYSIS
This alarm indicates that the PMOD is restarted due to the timeout on the
OML link with BCF.
3.8.14 PMOD (source: Restart due to a software upgrade)

Fault number 1060
Equipment:
PMOD
Source:
BTS model :
e-cell
FAULT ANALYSIS
This alarm indicates that the PMOD is restarted due to a software
upgrade.
3.8.15 PMOD (source: BCCH config dump)

Fault number 1060
Equipment:
PMOD
Source:
(3277074) BCCH config dump
BTS model :
e-cell
FAULT ANALYSIS
An anomaly has been detected in either a first or second BCCH
configuration. This transient event contains details of the anomaly.

411-9001-104 18.05 2 February 2010
TROUBLESHOOTING
3.8.16 PMOD (source: SACCH config dump)

Fault number 1060
Equipment:
PMOD
Source:
(3277090) SACCH config dump
BTS model :
e-cell
FAULT ANALYSIS
An anomaly has been detected in either a first or second SACCH
TROUBLESHOOTING
3.8.17 PMOD (source: L1M config dump)

Fault number 1060
Equipment:
PMOD
Source:
(3277106) L1M config dump
BTS model :
e-cell
FAULT ANALYSIS
An anomaly has been detected in either a first or second L1M
TROUBLESHOOTING
3.8.18 PMOD (source: RSL anomaly)

Fault number 1060
Equipment:
PMOD
Source:
(3277107) RSL anomaly
BTS model :
e-cell
FAULT ANALYSIS
A non-critical anomaly has been detected on a communication. This
transient event contains details of the anomaly.

411-9001-104 18.05 2 February 2010
751
752

Fault number :
1061
Abis mapping issue for a TDMA
Type
FAULT ANALYSIS
1061 is sent when TDMA is not connected or disconnected due to Abis
resources limitations. When EDGE is activated, TDMA mask field does not
represent the TCH mapping over TDMA but the following:
When a TDMA cannot be mapped over Abis because a higher priority
TDMA has been blocked and non mapped, the TDMA mask "00000000" is
given to operator meaning "Higher priority TDMA not mapped on Abis".
When a TDMA cannot be mapped over Abis because there are not
enough resources, the TDMA mask "11111111" is given to operator
meaning "Lack of Abis resources".
Correlated notification: the attribute value change 1063 is also sent
to notify the mapping TDMA TRX and when degraded mode is used,
the cause of it. A field is added to specify if configuration is nominal or
degraded. see the description of fault number 1063 in
Message definition : VAL_SPR_CODANO_RES_TDMA
Message operation code: Codano 1061
Object: transceiver
Anomaly code: Warning 1061
Alarm Criteria: Start/End
Structure definition:
Field
Size
Site
Site number within the

BSC
TRX
TRX number within

the site
TDMA Mask
(1) Definition:
15: Lack of Abis resources

0: Higher priority TDMA not mapped on Abis

411-9001-104 18.05 2 February 2010
Meaning
(1)
3.10 Attribute value change: 1063 (e-cell)
753
TROUBLESHOOTING
3.10 Attribute value change: 1063 (e-cell)

Attribute value change:
1063
TRX allocation for a TDMA
Type
FAULT ANALYSIS
An attribute value change 1063 is used to notify the mapping TDMA TRX
and when degraded mode is used, the cause of it. A field is added to
specify if configuration is nominal or degraded.
Message definition : VAL_SPR_CODANO_TRX_TDMA
Object: transceiver
Anomaly code: attribute value change 1063
Alarm Criteria: no
Structure definition:
Field
Size
TRX
Cause
TRX id
1
Degraded Configurati
on
Meaning
0: False (default) /
1: True
(1)
(1): Cause of the configuration in degraded mode:
(0): "Lack of Abis resources"
(2) "Site unsufficient number of DS0", when the site is not able to
respond to the TDMA DS0 request
(3): "TRX insufficient Edge capability", when the TRX is not able to
respond to the TDMA DS0 request
(255): "not significant", when the transceiver object is "Enabled"

without a degraded cause.
(1): "Site not supporting Edge", when site EDGE capability is not equal
to 2.
TROUBLESHOOTING
Cause (2):
411-9001-104 18.05 2 February 2010
754
This problem is associated with a bad configuration of EDGE backhaul.

The site is not able to respond to the TDMA DS0 request.
Check the radio site mask according to engineering rules.

Fault number:
1067
Type
equipmentAlarm
In the case of an equipment fault or a missing equipment item, the BTS

sends a 1067 message to the BSC specifying the faulty equipment and
the source.
For more information on each source, see the indicated paragraph to know
the corrective maintenance procedure associated with this source.
Equipment
source No.
Paragraph
Source wording
Abis BTS synchro
3342340
SYNO clock not locked on

the network
3.11.1 Abis BTS synchro

(source: SYNO clock not
locked on the network)
(page 758)
AC power supply
6619137
Power fault

(page 763)
External alarm
7274497
External alarm
3.11.3 External alarm

(source: External alarm)
(page 766)
Internal temperature
8060929
Threshold exceeded
6815745
Hardware
3.11.5 PA (source:
Hardware) (page 768)
PA
6815777
PA DRX control loop fault
3.11.6 PA (source: PA
DRX control loop fault)
(page 773)
PCM
6488065
PCM
3.11.4 Internal temperature

(source: Threshold

(page 778)

411-9001-104 18.05 2 February 2010
Equipment
source No.
755
Paragraph
Source wording
3145737
Base-extension
communication fault
3211262
Self test failed
3145777
Hardware
3.11.10 PMNU (source:

3276806
BBFILTER ASIC FAULT
3.11.11 PMOD (source:

BBFILTER ASIC fault)
(page 789)
3276809
Self test failed
3276810
Major fault on TX
3276832
The TX has not

acknowledged the power
consign request
3277072
BCCH first config failed
3277073
BCCH second config failed
3277088
SACCH first config failed
3277089
SACCH second config failed

SACCH second config
failed) (page 807)
3277104
L1M first config failed

L1M first config failed)
(page 808)
PMOD
3277105
L1M second config failed

L1M second config failed)
(page 809)
PSU
3407873
PSU failure
3.11.21 PSU (source: PSU

failure) (page 809)
PMNU
PMOD
3.11.8 PMNU (source:

Base-extension
communication fault)
(page 778)
3.11.9 PMNU (source: Self
test failed) (page 780)
3.11.12 PMOD (source: Self

test failed) (page 794)
Major fault on TX) (page
798)
3.11.14 PMOD (source: The
TX has not acknowledged
the power consign request)
(page 803)
BCCH first config failed)
(page 806)
BCCH second config failed)
(page 806)
SACCH first config failed)
(page 807)

411-9001-104 18.05 2 February 2010
756
Equipment
RDRX
source No.
Paragraph
Source wording
3211265
RX fault
3211266
Hardware
3.11.22 RDRX (source: RX

fault) (page 811)
3.11.23 RDRX (source:

and the sheets for the e-cell.
Table 47
PMNU location
Equipment type
Equipment
number
Unit
Paragraph
PMNU
BASE
PMNU
EXTENSION
Nortel GSM
BTS e-cell
Troubleshooting
(411-9001-090)
Equipment type
Equipment
number
Unit
Paragraph
RDRX
BASE
RDRX
BASE
Nortel GSM
BTS e-cell
Troubleshooting
(411-9001-090)
RDRX
EXTENSION
RDRX
EXTENSION
Nortel GSM
BTS e-cell
Troubleshooting
(411-9001-090)
Equipment type
Equipment
number
Unit
Paragraph
PMOD
BASE
PMOD
BASE
Nortel GSM
BTS e-cell
Troubleshooting
(411-9001-090)
PMOD
EXTENSION
PMOD
EXTENSION
Table 48
RDRX location
Table 49
PMOD location

411-9001-104 18.05 2 February 2010
Nortel GSM
BTS e-cell
Troubleshooting
(411-9001-090)
757
Table 50
PA location
Equipment type
Equipment
number
Unit
Paragraph
PA
BASE
PA
BASE
Nortel GSM
BTS e-cell
Troubleshooting
(411-9001-090)
PA
EXTENSION
PA
EXTENSION
Nortel GSM
BTS e-cell
Troubleshooting
(411-9001-090)
Equipment type
Equipment
number
Unit
Paragraph
PCM
None
PCM
None
Nortel GSM
BTS e-cell
Troubleshooting
(411-9001-090)
Equipment
number
Unit
Paragraph
None
Nortel GSM
BTS e-cell
Troubleshooting
(411-9001-090)
Table 51
PCM location
Table 52
Abis BTS synchro location
Equipment type
ABIS BTS
SYNCHRO
Table 53
External alarm location
Equipment
number
Unit
Paragraph
EXTERNAL ALARM
BASE
EXTERNAL ALARM
BASE
EXTERNAL ALARM
BASE
EXTERNAL ALARM
BASE
Nortel GSM
BTS e-cell
Troubleshoo
ting (411-90
01-090)
EXTERNAL ALARM
EXTENSION
EXTERNAL ALARM
EXTENSION
Equipment type

411-9001-104 18.05 2 February 2010
Nortel GSM
BTS e-cell
Troubleshoo
ting (411-90
01-090)
758
Table 53
External alarm location (contd.)
Equipment
number
Unit
Paragraph
EXTERNAL ALARM
EXTENSION
EXTERNAL ALARM
EXTENSION
Nortel GSM
BTS e-cell
Troubleshoo
ting (411-90
01-090)
Equipment type
Table 54
Equipment
number
Unit
Paragraph
AC POWER
SUPPLY
None
AC POWER
SUPPLY
None
Nortel GSM
BTS e-cell
Troubleshooting
(411-9001-090)
Equipment type
Equipment
number
Unit
Paragraph
PSU
BASE
PSU
EXTENSION
Nortel GSM
BTS e-cell
Troubleshooting
(411-9001-090)
Equipment
number
Unit
Paragraph
INTERNAL
TEMPERATURE
BASE
INTERNAL
TEMPERATURE
EXTENSION
Nortel GSM
BTS e-cell
Troubleshooting
(411-9001-090)
Equipment type
Table 55
PSU location
Table 56
Internal temperature location
Equipment type
3.11.1 Abis BTS synchro (source: SYNO clock not locked on the
network)
Fault number 1067
Equipment:
ABIS BTS SYNCHRO
Source:
(3342340) SYNO clock not locked on the network
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
759
FAULT ANALYSIS
interval.

If, in the notification the "impact" field is "non transparent for the BSC",
the BSC unconfigures the btsSiteManager object.
CAUTION
configuration.
If, in the notification the "impact" field is "transparent for the BSC", the
BSC does not do anything.
CAUTION
concerned and its neighboring BTSs (S8000 or S8002 BTS,
S2000 H/L BTS, or BTS of another manufacturer).
TROUBLESHOOTING
Preliminary checks
Step
Action





411-9001-104 18.05 2 February 2010
760

back "enabled".

"disabled-failed".

Replace the radio cabinet. see Nortel GSM BTS e-cell





administrativeSt ate of the pcmCircuit object to "locked".


analyzer).

A uplinks.

411-9001-104 18.05 2 February 2010
761

to step 8.
go to step 9.

(411-9001-132).
11
12


(411-9001-132).
10

If the alarm has disappeared, go to step 22




go to step 11.

TCU.


do the same operation twice: either the operationalState
If the operationalState is "enabled", go to step 7. Otherwise
go to step 9.


411-9001-104 18.05 2 February 2010
762
13
14


frequency of the PCM Ater link is correct, go to step 19step
16.

frequency of the PCM Ater link is not correct, go to step
17step 14.

downlink concerned, go to step 18step 15, and if it is the
uplink concerned, go to step 17step 14.

(411-9001-132).


15
16


step 17.
operator.

411-9001-104 18.05 2 February 2010
763

17

18
Replace the IEM board (Field Replaceable Unit) of the BSC

(411-9001-132).
19


Additional checks
20

21
Clear the alarm.
22

--End--
3.11.2 AC power supply (source: Power fault)

Fault number 1067Abis event reporting a hardware fault
Equipment:
AC power supply
Source:
BTS model:
e-cell
FAULT ANALYSIS
The power backup for an e-cell is approximately 15 minutes at 25C with
the optional battery pack of the PSU.
The alarm may appear on the base or/and extension unit.

defense action.
411-9001-104 18.05 2 February 2010
764
When the battery is lost, the BSC deconfigures the btsSiteManager object.
CAUTION
Equipment damage
When this alarm appears, the BTS operates with battery pack
of the PSU.
TROUBLESHOOTING
Preliminary checks
Step
Action



back "enabled".
If the unit is out of order, treat the problem on the unit.

Go to step 3.

(411-9001-105) ).
If the unit is out of order, treat the problem on the unit.

Go to step 3.

(411-9001-105) ).


back "enabled".


411-9001-104 18.05 2 February 2010
765

"disabled-failed".



On-site maintenance
Check the mains power supply on the operator box.


and go to step 6.
Check the mains power supply on the operator box.

and go to step 6.
Replace the PSU. see Nortel GSM BTS e-cell Troubleshooting

(411-9001-090). Go to step 6.
Additional checks



411-9001-104 18.05 2 February 2010
766


go to step 8.
Clear the alarm.

--End--
3.11.3 External alarm (source: External alarm)

Equipment:
External alarm
Source:
(7274497) External alarm
BTS model:
e-cell
If the alarm is external, the maintenance action depends on how the user
deals with the alarm. Eight external alarms can be used for the e-cell.
3.11.4 Internal temperature (source: Threshold exceeded)

Equipment:
Internal temperature
Source:
BTS model:
e-cell
FAULT ANALYSIS
The beginning of fault appears when the internal temperature is too high.
Then the LPA are switched off until the return to a normal temperature.
The service is lost whereas the radio cabinet is still working.
The end of fault appears when the temperature returns normal. Then the
LPA restarts.

BSC defense When the PAs are switched off, the BSC deconfigures the
associated transceiverEquipment objects.
The BSC waits for the end of fault to perform the reconfiguration.
Impact on the service There is the loss of all the transceiverEquipment,
bts, and transceiver objects.
411-9001-104 18.05 2 February 2010
767
CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".


411-9001-104 18.05 2 February 2010
768
If the state of the "internal temperature" equipment is "failed",

If the state of the "internal temperature" equipment is

On-site maintenance
Check the external temperature.
If the temperature is upper than 50C, wait for the return to a

normal temperature. The unit will restart automatically. Go
to step 5.
If the temperature is lower than 50C, go to step 4.
Check the heatsinks.
Else, go to step 6.
If they are dirty, clean them. Go to step 5.


Go to step 7.
Additional checks

If the state of the "internal temperature" equipment is still

If the state of the "internal temperature" equipment is


--End--

Equipment:
PA

411-9001-104 18.05 2 February 2010
Source:
(6815745) Hardware
BTS model:
e-cell
769
FAULT ANALYSIS
This alarm indicates a hardware failure of the LPA. The corresponding
RDRX is not operational any more.

using the faulty LPA, at least one transceiver object so one bts object.
CAUTION
The service is reduced or lost.
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".


411-9001-104 18.05 2 February 2010
770

"disabled-failed".
Check that the alarm on the LPA is valid, by performing



In case of:
a base e-cell. Go to step 4.

an extension e-cell.
For an O4 configuration (mono band), go to step 7.
For the other configurations, go to step 8.
Determine the type of configuration (see Nortel GSM BSS Fault

For a "Drop and Insert" configuration, see step 5.

For other configurations, see step 6.
Replace the radio cabinet:
of the base e-cell in a chain "Drop and Insert" configuration,

go to step 9.
of the base e-cell in a "Drop and Insert" configuration with

redundancy, go to step 10.
Perform the following actions to minimize the impacts on the

other transceiverEquipment objects of a same btsSiteManager.
Set to "shuttingDown" the administrativeState of the bts

object.
Set to "locked" the administrativeState of all the

transceiverEquipment and btsSiteManager objects.

411-9001-104 18.05 2 February 2010
771
Replace the radio cabinet according to the notification. see

Nortel GSM BTS e-cell Troubleshooting (411-9001-090).
Set to "unlocked" the btsSiteManager, bts, and

Go to step 11.
7

other transceiverEquipment objects of a same btsSiteManager
object.

object.
Set to "locked" the administrativeState of the two

transceiverEquipment objects associated to the extension
unit.
Set to "unlocked" the administrativeState of the bts object.

The service returns on the two transceiverEquipment objects
of the base unit.
Disconnect the cable between the base and the extension

unit.
Replace the radio cabinet of the extension unit. see Nortel

GSM BTS e-cell Troubleshooting (411-9001-090). A 1067
alarm with "base-extension communication fault" source
appears: do not treat it.
Set to "unlocked" the administrativeState of the two

unit.
Go to step 11.
8


object associated to the extension unit.

unit.

unit.


411-9001-104 18.05 2 February 2010
772


transceiverEquipment and bts objects associated to the
extension unit.
Go to step 11.
9

and on the other btsSiteManager objects of the chain.

object(s) located after the btsSiteManager which is out of
order.

object of the out of order btsSiteManager object.
Set to "locked" the transceiverEquipment and btsSiteManager

objects associated to base unit.

Alarms can appear on the other btsSiteManager objects of
the chain: do not treat them.

Go to step 11.
10

and on the other btsSiteManager objects of the loop.
Set to "shuttingDown" all the bts objects of the loop.
Disconnect (PCM links) the e-cell to replace.

Set to "unlocked" the administrativeState of the

btsSiteManager, bts, and two transceiverEquipment objects
associated to the base unit.

transceiverEquipment and btsSiteManager objects associated
to the base unit.
Set to "unlocked" all the previously bts objects (except the bts
object associated to the replaced BTS).
Go to step 11.

411-9001-104 18.05 2 February 2010
773
Additional checks
11
12

Check the state of the LPA by performing a "Display hardware


manufacturer.
13
Clear the alarm.
14

--End--
3.11.6 PA (source: PA DRX control loop fault)

Equipment:
PA
Source:
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that the RDRX has not succeeded in the LPA
emission power configuration with the DRX/LPA control loop.

BSC defense The BSC unconfigures the faulty LPA and the associated
CAUTION

411-9001-104 18.05 2 February 2010
774
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".
Check that the alarm on the LPA module is valid, by




411-9001-104 18.05 2 February 2010
775
In case of:




go to step 9.



object.



Go to step 11.
7

object.

object.

unit.

of the base unit.

411-9001-104 18.05 2 February 2010
776

unit.


unit.
Go to step 11.
8



unit.

unit.


extension unit.
Go to step 11.
9


order.




411-9001-104 18.05 2 February 2010
777


Go to step 11.
10

Disconnect (PCM links) the radio cabinet to replace.



to the base unit.
Go to step 11.
Additional checks
11
12

Check the state of the LPA by performing a "Display hardware


manufacturer.
13
Clear the alarm.
14

--End--

411-9001-104 18.05 2 February 2010
778

Equipment:
PCM
Source:
(6488065) PCM
BTS model:
e-cell
This alarm can indicate a manual action on the PCM links (lock/unlock
when the BTS is connected to a BSC 3000).
This alarm can also be associated with a PCM fault. see Nortel GSM BSS
Fault Clearing - Advanced Maintenance (411-9001-105) .
3.11.8 PMNU (source: Base-extension communication fault)

Equipment:
PMNU
Source:
(3145737) Base-extension communication fault
BTS model:
e-cell
FAULT ANALYSIS
The link between the base and the extension unit is failed.
There is no more communication between the base and the extension unit.

Impact on the service The two transceiverEquipment objects associated
to the concerned extension unit are lost.
ATTENTION
TROUBLESHOOTING
Preliminary checks
Step
Action




411-9001-104 18.05 2 February 2010
779


back "enabled".

"disabled-failed".

If the state of the "PMNU" equipment is "failed", the fault is

If the state of the "PMNU" equipment is "working", the fault is

On-site maintenance
Check the status of the extension unit, by looking at the power

led located on the "Test and Configuration" interface.
If the led is ON, it indicates that the radio cabinet is powered.

Go to step 4.
If the led is OFF, the radio cabinet is not powered with

-48VDC. Go to step 5.
Check the cable between the base unit and the extension unit.
If it is correct, go to step 5.
If not, replace the cable. Go to step 6.

411-9001-104 18.05 2 February 2010
780
Replace the radio cabinet of the extension unit. see Nortel GSM
BTS e-cell Troubleshooting (411-9001-090). Go to step 6.
Additional checks

Check the state of the PMNU module by performing a "Display

If the state of the "PMNU" equipment is still "failed", call the

manufacturer.
If the state of the "PMNU" equipment is "working", go to step

8.
Clear the alarm.

--End--
3.11.9 PMNU (source: Self test failed)

Equipment:
PMNU
Source:
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates a hardware problem in the start-up self-tests.

CAUTION

411-9001-104 18.05 2 February 2010
781
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".

configuration" command on the btsSiteManager object



411-9001-104 18.05 2 February 2010
782
Check the values of the bists, by performing a "Display data

If one BIST is "failed", the fault is confirmed. Go to step 4.

If the BISTs are "OK", the fault is not confirmed. Go to step
14.
In case of:




go to step 10.



object.



Go to step 12.
8

object.

411-9001-104 18.05 2 February 2010
783

object.

unit.

of the base unit.

unit.


unit.
Go to step 12.
9



unit.

unit.

appears : do not treat it.

extension unit.
Go to step 12.
10


411-9001-104 18.05 2 February 2010
784

order.




Go to step 12.
11

Replace the radio cabinet of the base unit according to the

notification. see Nortel GSM BTS e-cell Troubleshooting
(411-9001-090).


to the base unit.
Go to step 12.
Additional checks
12
13



411-9001-104 18.05 2 February 2010
785

manufacturer.

14.
14
Clear the alarm.
15

--End--
3.11.10 PMNU (source: Hardware)

Equipment:
PMNU
Source:
(3145777) Hardware
BTS model:
e-cell
FAULT ANALYSIS

CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action




411-9001-104 18.05 2 February 2010
786


back "enabled".

"disabled-failed". .



In case of:




411-9001-104 18.05 2 February 2010
787

go to step 9.



object.



Go to step 11.
7

object.

object.

unit.

of the base unit.

unit.


unit.
Go to step 11.
8


411-9001-104 18.05 2 February 2010
788


unit.

unit.


extension unit.
Go to step 11.
9


order.


objects associated to the base unit.


Go to step 11.
10


to the base unit.

411-9001-104 18.05 2 February 2010
789

(411-9001-090).

Go to step 11.
Additional checks
11
12



manufacturer.

13.
13
Clear the alarm.
14

--End--
3.11.11 PMOD (source: BBFILTER ASIC fault)

Fault number 1067
Equipment:
PMOD
Source:
(3276806) BBFILTER ASIC fault
BTS model:
e-cell
FAULT ANALYSIS

BSC defense The BSC unconfigures the faulty RDRX and the
associated transceiver and transceiverEquipment objects. It tries to assure
a minimum service of communication by unconfiguring and reconfiguring
the transceiver.
411-9001-104 18.05 2 February 2010
790
Only one transceiverEquipment object is lost.
CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".


411-9001-104 18.05 2 February 2010
791
If the state of the "PMOD" equipment is "failed", the fault is

If the state of the "PMOD" equipment is "working", the fault is

In case of:




go to step 9.



object.



Go to step 11.
7

object.

411-9001-104 18.05 2 February 2010
792

object.

unit.

of the base unit.

unit.


unit.
Go to step 11.
8



unit.

unit.


extension unit.
Go to step 11.
9


411-9001-104 18.05 2 February 2010
793

order.




Go to step 11.
10


(411-9001-090).


to the base unit.
Go to step 11.
Additional checks
11
12



411-9001-104 18.05 2 February 2010
794
If the state of the "PMOD" equipment is still "failed", call the

manufacturer.
If the state of the "PMOD" equipment is "working", go to step

13.
13
Clear the alarm.
14

--End--
3.11.12 PMOD (source: Self test failed)

Fault number 1067
Equipment:
PMOD
Source:
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates a problem in the hardware self-tests of the DRX.

CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action


411-9001-104 18.05 2 February 2010


795


back "enabled".

"disabled-failed".



In case of:


411-9001-104 18.05 2 February 2010
796



go to step 9.



object.



Go to step 11.
7

object.

object.

unit.

of the base unit.

unit.


unit.

411-9001-104 18.05 2 February 2010
797
Go to step 11.
8



unit.

unit.


extension unit.
Go to step 11.
9


order.




Go to step 11.
10


411-9001-104 18.05 2 February 2010
798
Disconnect (PCM links) the e-cell to replace.



to the base unit.
Go to step 11.
Additional checks
11
12



manufacturer.

13.
13
Clear the alarm.
14

--End--
3.11.13 PMOD (source: Major fault on TX)

Equipment:
PMOD
Source:
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates a loss of traffic synchronization between the TRX and
the TCU.
411-9001-104 18.05 2 February 2010
799

CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".


411-9001-104 18.05 2 February 2010
800

"disabled-failed".
Check that the alarm is valid by performing a "Display hardware



In case of:




go to step 9.



object.


411-9001-104 18.05 2 February 2010
801


Go to step 11.
7

object.

object.

unit.

of the base unit.

unit.


unit.
Go to step 11.
8



unit.

unit.


411-9001-104 18.05 2 February 2010
802


extension unit.
Go to step 11.
9


order.




Go to step 11.
10




to the base unit.
Go to step 11.

411-9001-104 18.05 2 February 2010
803
Additional checks
11
12



manufacturer.

13.
13
Clear the alarm.
14

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

consign request)
Fault number 1067
Equipment:
PMOD
Source:
(3276832) The TX has not acknowledged the power

consign request
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that the sent power consign is bad.

At least on DRX is lost.
CAUTION
Service reduction
It is possible to lose the whole cell linked to the faulty DRX.

411-9001-104 18.05 2 February 2010
804
CAUTION
of service loss.
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".


411-9001-104 18.05 2 February 2010
805



If the "concentric cell" parameter is "concentric", go to step 4.

If the "concentric cell" parameter is "monozone", "dualband"
or " ", go to step 5.

the attenuation of the duplexer must be between 19 dBm and 32
dBm for the e-cell.
powerControl object associated with the bts object. The
"Attenuation" parameter is obtained by a "Display" command on
the btsSiteManager object.
The following table lists the correct values of the "bsTxPwrMax"
parameter. The "Nack" value is not allowed.
If the value is correct, replace the radio cabinet. see Nortel

GSM BTS e-cell Troubleshooting (411-9001-090). Go to step
9.
If the value is not correct, modify it. Go to step 9.

the attenuation of the duplexer and reduced of the value of the
"transceiver zone Ref" parameter must be between 19 dBm and
32 dBm for the e-cell.
The previous table allows to know the good values of the
"bsTxPwrMax" parameter. The "Nack" value is not admitted.

411-9001-104 18.05 2 February 2010
806
However, do not forget to consider the "transceiver zone Ref"

parameter.
If the value is correct, replace the radio cabinet. see Nortel

GSM BTS e-cell Troubleshooting (411-9001-090). Go to step
9.
If the value is not correct, modify it. Go to step 9.
Additional checks
Clear the alarm.

--End--
3.11.15 PMOD (source: BCCH first config failed)

Fault number 1067
Equipment:
PMOD
Source:
(3277072) BCCH first config failed
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that an anomaly has been detected in a BCCH
configuration. One new configuration is allowed after clearing the TRX
configuration.

BSC defense An automatic reconfiguration defense action is triggered
by the BSC.
TROUBLESHOOTING
3.11.16 PMOD (source: BCCH second config failed)

Fault number 1067
Equipment:
PMOD
Source:
(3277073) BCCH second config failed
BTS model:
e-cell
FAULT ANALYSIS

411-9001-104 18.05 2 February 2010
807
This alarm indicates that a second anomaly has been detected in a BCCH
configuration. The TRX may no longer be reconfigured, it can now only
be locked or unlocked at any level.
TROUBLESHOOTING
Step
Action
Lock the transceiverEquipment object, and then unlock it.

Lock the bts object, and then unlock it.

If the problem persists, call the manufacturer.

--End--
3.11.17 PMOD (source: SACCH first config failed)

Fault number 1067
Equipment:
PMOD
Source:
(3277088) SACCH first config failed
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that an anomaly has been detected in an SACCH
configuration

by the BSC.
TROUBLESHOOTING
3.11.18 PMOD (source: SACCH second config failed)

Equipment:
PMOD

411-9001-104 18.05 2 February 2010
808
Source:
(3277089) SACCH second config failed
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that a second anomaly has been detected in an
SACCH configuration. The TRX may no longer be reconfigured, it can now
only be locked or unlocked at any level.
TROUBLESHOOTING
Step
Action



--End--
3.11.19 PMOD (source: L1M first config failed)

Equipment:
PMOD
Source:
(3277104) L1M first config failed
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that an anomaly has been detected in an L1M
configuration

by the BSC.
TROUBLESHOOTING

411-9001-104 18.05 2 February 2010
809
3.11.20 PMOD (source: L1M second config failed)

Fault number 1067
Equipment:
PMOD
Source:
(3277105) L1M second config failed
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates that a second anomaly has been detected in an L1M
configuration. The TRX may no longer be reconfigured, it can now only
be locked or unlocked at any level.
TROUBLESHOOTING
Step
Action



--End--
3.11.21 PSU (source: PSU failure)

Fault number 1067
Equipment:
PSU
Source:
(3407873) PSU failure
BTS model:
e-cell
FAULT ANALYSIS
The PSU is failed. Therefore, this failure indicates that the battery pack
is powering the BTS.
The power back up is approximately 15 minutes with the battery pack.

411-9001-104 18.05 2 February 2010
810

defense action.
When the battery is lost, the BSC deconfigures the btsSiteManager object.
CAUTION
If the alarm appears on the base unit, the service is lost.
If the alarm appears on the extension unit, two transceiverEquip
ment objects are lost. The service is reduced.
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".

411-9001-104 18.05 2 February 2010
811

If the state of the "PSU" equipment is "failed", the fault is

If the state of the "PSU" equipment is "working", the fault is

On-site maintenance
Replace the PSU. see Nortel GSM BTS e-cell Troubleshooting

(411-9001-090). Go to step 4.
Additional checks


If the state of the "PSU" equipment is still "failed", call the

manufacturer.
If the state of the "PSU" equipment is "working", go to step 7.
Clear the alarm.

--End--
3.11.22 RDRX (source: RX fault)

Fault number 1067
Equipment:
RDRX
Source:
(3211265) RX fault
BTS model:
e-cell
FAULT ANALYSIS
The DRX is not operational any more. The RX PLL is out of lock.

411-9001-104 18.05 2 February 2010
812

BSC defense The BSC deconfigures the faulty DRX and the associated
transceiverEquipment object. It tries to assure a minimum service of
CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action




back "enabled".

"disabled-failed".

411-9001-104 18.05 2 February 2010
813

If the state of the "RDRX" equipment is "failed", the fault is

If the state of the "RDRX" equipment is "working", the fault is

In case of:




go to step 9.



object.



Go to step 11.

411-9001-104 18.05 2 February 2010
814

object.

object.

unit.

of the base unit.

unit.


unit.
Go to step 11.
8



unit.

unit.


extension unit.
Go to step 11.
9


411-9001-104 18.05 2 February 2010
815

order.




Go to step 11.
10




to the base unit.
Go to step 11.
Additional checks
11
12

Check the state of the RDRX module by performing a "Display


411-9001-104 18.05 2 February 2010
816
If the state of the "RDRX" equipment is still "failed", call the

manufacturer.
If the state of the "RDRX" equipment is "working", go to step

13.
13
Clear the alarm.
14

--End--
3.11.23 RDRX (source: Hardware)

Fault number 1067
Equipment:
RDRX
Source:
(3211266) Hardware
BTS model:
e-cell
FAULT ANALYSIS
This alarm indicates an internal hardware failure of the radio cabinet.

BSC defense The BSC unconfigures the two transceiver objects.
Impact on the service If the alarm appears on the base unit, the two
transceiverEquipment objects of the base unit are lost.
If the alarm appears on the extension unit, the two transceiverEquipment
objects of the extension unit are lost.
CAUTION
TROUBLESHOOTING
Preliminary checks
Step
Action


411-9001-104 18.05 2 February 2010


817


back "enabled".

"disabled-failed".
Check that the alarm on the RDRX is valid, by performing

If the state of the "RDRX" equipment is "failed", the fault is

If the state of the "RDRX" equipment is "working", the fault is

In case of:


411-9001-104 18.05 2 February 2010
818



go to step 9.



object.



Go to step 11.
7

object.

object.

unit.

of the base unit.

unit.


unit.

411-9001-104 18.05 2 February 2010
819
Go to step 11.
8



unit.

unit.


extension unit.
Go to step 11.
9


order.




Go to step 11.
10


411-9001-104 18.05 2 February 2010
820



to the base unit.
Go to step 11.
Additional checks
11
12

Check the state of the RDRX by performing a "Display hardware

If the state of the "RDRX" equipment is still "failed", call the

manufacturer.
If the state of the "RDRX" equipment is "working", go to step

13.
13
Clear the alarm.
14

--End--

Fault number:
1070
TRX synchronization failure
Type
equipmentAlarm

411-9001-104 18.05 2 February 2010
821

Fault number:
1073
Attempt of download failure on a GSM entity
Type
communicationsAlarm
FAULT ANALYSIS
This notification, issued by the BSC, appears when the downloading of
a new software release has failed.
When the downloading is successful, the site or the DRX requests

a reset of the entity by the BSC (reception by the BSC of a LOAD
READY NACK, issued by the BTS). The fault number 1073 is issued
alone after reception of this LOAD READY NACK. The BTS is
operational.
When the downloading is not successful (error in a file), the

downloading stops and another downloading is performed
automatically. The downloading starts from scratch.
Each time the downloading fails again, the fault number 1073 is
issued.
After four failed attempts (and four fault numbers 1073 issued), a
new downloading starts. If it fails, the fault number 1052 is issued
alone.
Table 57
source
No.
Paragraph
Source wording
No response to status request
Reception Stop from SUP
File access error
Repetitive errors (NACK, timeout, ... ) while downloading

a file
Wrong software reference on a non downloadable TEI
No response to LOAD message
3.13.1 Source 9: No
response to LOAD
message (page 825)

411-9001-104 18.05 2 February 2010
822
Table 57
source
No.
Paragraph
Source wording
10
Received LOAD INIT NACK
11
Received message LOAD DATA NACK
3.13.3 Source 11:

Received message LOAD
DATA NACK (page 826)
12
Received message LOAD END NACK
3.13.4 Source 12:

Received message LOAD
END NACK (page 826)
13
Received message LOAD READY NACK
14
CSM load container negative acknowledgement
15
16
File to download unavailable
17
18
Bad sending buffer size value
19
Failure during omu switchover
20
Bad TEI sent by BTS in the CSM software update report

message
21
CSM software update report with the cause "unknown

TEI"
22
CSM software update report with the cause "equipment

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

failure"
24
CSM software update report with the cause "not able to

perform"
27
CSM software update report with the cause "restart

request"
29
CSM software update report with the cause "message out

of sequence"
32
CSM software update report with the cause "downloading

in progress"
33
Bad report sent by BTS in the CSM software update

report message
3.13.2 Source 10:

Received LOAD INIT
NACK (page 825)
3.13.5 Source 13:

Received message
(page 826)

411-9001-104 18.05 2 February 2010
Table 57
source
No.
Source wording
Paragraph
34
no BTS response on CSM software update init/control

message
35
nack received on the abort requested by operator
36
bad report sent by BTS in the CSM software update abort

message
37
no BTS response on CSM software update abort

message
47
CSM downloading start nack with the cause "equipment

failure"
48

49
CSM downloading start nack with the cause "message

out of sequence"
50
CSM downloading start nack with the cause "wrong soft

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

config ref"
52
CSM downloading start nack with a bad cause
53
no BTS response on CSM downloading start message
55
CSM downloading end nack with the cause "equipment

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

failure"
57
CSM downloading end nack with the cause "value out of

range"
58
CSM downloading end nack with a bad cause
59
no BTS response on CSM downloading end message
60
CSM load init nack with the cause "equipment failure"
61
CSM load init nack with the cause "downloading failure"
62
CSM load init nack with the cause "message out of

sequence"
63
CSM load init nack with the cause "wrong file ref"
64
CSM load init nack with the cause "window size not
allow"
65
CSM load init nack with the cause "data format error"
66
CSM load init nack with a bad cause

411-9001-104 18.05 2 February 2010
823
824
Table 57
source
No.
Source wording
Paragraph
67
no BTS response on CSM load init message
68
CSM load data nack with the cause "equipment failure"
69
CSM load data nack with the cause "downloading failure"
70
CSM load data nack with the cause "message out of

sequence"
71
CSM load data nack with the cause "data format error"
72
CSM load data nack with the cause "window overflow"
73
CSM load data nack with the cause "data inconsistency"
74
CSM load data nack with the cause "block not received"
75
CSM load data nack with the cause "bad block tag"
76
CSM load data nack with the cause "checksum error"
77
CSM load data nack with a bad cause
78
unexpected CSM load data ack
79
no BTS response on CSM load data message
80
CSM load end nack with the cause "equipment failure"
81
CSM load end nack with the cause "downloading failure"
82
CSM load end nack with the cause "value out of range"
83
CSM load end nack with the cause "message out of

sequence"
84
CSM load end nack with the cause "data format error"
85
CSM load end nack with the cause "wrong file ref"
86
CSM load end nack with the cause "data inconsistency"
87
CSM load end nack with the cause "checksum error"
88
CSM load end nack with a bad cause
89
no BTS response on CSM load end message
90
bad report sent by BTS during an internal update
91
CSM load init nack with the cause "file already open"
92
CSM load init nack with the cause "invalid mode"
93
CSM load init nack with the cause "file cannot be

unloaded"
94
CSM load init nack with the cause "flash flag cannot
access"

411-9001-104 18.05 2 February 2010
825
Table 57
source
No.
Source wording
Paragraph
95
CSM load data nack with the cause "file cannot be

unloaded"
96
CSM load data nack with the cause "flash flag cannot
access"
97
CSM load data nack with the cause "boot cannot be

unloaded"
98
CSM load data nack with the cause "data decod error"
99
CSM load data nack with the cause "table cannot access"
100
CSM load data nack with the cause "ram mapping error"
101
CSM load data nack with the cause "flash access error"
102
CSM load data nack with the cause "flash ram error"
103
CSM load data nack with the cause "flash erase error"
104
CSM load data nack with the cause "internal abort"

BSC defense
None.

None.
3.13.1 Source 9: No response to LOAD message

Fault number 1073: Attempt of download failure on a GSM entity
Source:
(9) No response to LOAD message
BTS model:
e-cell
3.13.2 Source 10: Received LOAD INIT NACK

Source:
(10) Received LOAD INIT NACK
BTS model:
e-cell

411-9001-104 18.05 2 February 2010
826
3.13.3 Source 11: Received message LOAD DATA NACK

Source:
(11) Received message LOAD DATA NACK
BTS model:
e-cell
3.13.4 Source 12: Received message LOAD END NACK

Source:
(12) Received message LOAD END NACK
BTS model:
e-cell
3.13.5 Source 13: Received message

Source:
(13) Received message
BTS model:
e-cell

Fault number:
1080
Access fault
Type
equipmentAlarm
FAULT ANALYSIS
This fault number indicates a communication problem between the BSC
and the BTS. More precisely, there is an issue between the SPR and
Access software modules of the BSC (SPR defense on opening or closing
a link or dialog).
List of causes:
0 No response from Access for chnl cnx request

1 Nack from Access for chnl cnx request
2 No response from Access for chnl dcnx request
3 Nack from Access for chnl dcnx request
4 No response from Access for chnl switchover request

411-9001-104 18.05 2 February 2010
827
5 Nack from Access for chnl switchover request

6 No response from Access for OML open diag request
7 Nack from Access for OML open diag request
8 No response from Access for OML close diag request
9 Nack from Access for OML close diag request
10 No response from Access for RSL open diag request
11 Nack from Access for RSL open diag request
12 No response from Access for RSL close diag request
13 Nack from Access for RSL close diag request
14 No response from Access for GSL open diag request
15 Nack from Access for GSL open diag request
16 No response from Access for GSL close diag request
17 Nack from Access for GSL close diag request

BSC defense
The BSC tries to use other LAPD channels to reach the BTS.
TROUBLESHOOTING
If the BSC succeeds in using other LAPD channels, then no maintenance
action is required.
If the BSC fails, then other fault numbers are sent to the OMC-R.

Fault number
1165
At least one terrestrial circuit is HSCSD-blocked.
Type
equipmentAlarm
This problem is associated with a PCM fault. See 411-9001-105 (Nortel

GSM BSS Fault Clearing - Advanced Maintenance Procedures).

411-9001-104 18.05 2 February 2010
828

Fault number:
1258
No BTS response on preprocessing configuration
Type
equipmentAlarm
FAULT ANALYSIS
This fault number indicates a non-response of a transceiverEquipment
object to an L1M request. The BTS issues this alarm after five
unsuccessful attempts to warn users that the data handled by the BSC
may not be consistent with the data actually received by the BTS.
In spite of this handling, the BSC goes on its configuration attempts. The
situation must be re-established.
The message loss, due to disruptions on the Abis link, is sufficient for
the creation of this notification, but insufficient to release the defense
mechanism of the transceiverEquipment object.

BSC defense
None.

CAUTION
TROUBLESHOOTING
Step
Action
Check the time of the alarm appearance and note the different
commands performed at the OMC-R on the cell concerned and
on the neighboring cells, if any.
Check which parameters are concerned by the notification: those

of the cell or those of the neighboring cells.
Check if it is a start-up or a change, in order to understand the

commands performed in the notification log.
Check the state of the bts, pcmCircuit, btsSiteManager and

Perform a "display dynamic data" on the transceiver object.

411-9001-104 18.05 2 February 2010
829
Ensure that the state of the parameter "allocationState" is

"available".
If the state of the parameter "allocationState" is not
"available", the BTS has not recognized or not received
the messages from the BSC.
If the state of the parameter "rmpConfState" is "not

configured", the fault is confirmed. Go to step 6.
To create an adjacent cell on the bts object:
Select the bts object.
In the dialog box, select either the "adjacentCellReselection"

or "adjacentCellHandover" object.
Go to the "Objects" menu and select the "Create Child"

option. This opens a dialog box which allows the operator to
select various dependent objects.

--End--

Fault number:
1259
Negative acknowledgement on preprocessing command
Type
equipmentAlarm
FAULT ANALYSIS
This alarm can be received on either a standard cell or on a neighboring
cell.
If the alarm is received on a neighboring cell, there is not handover any

more (because the neighboring cells are unknown).
If the alarm is received on a standard cell, the problem can be

occurred during the start-up or a change.

BSC defense
None.

411-9001-104 18.05 2 February 2010
830

If the alarm is received on a neighboring cell, calls are still possible.
Nevertheless, the calls cannot be moved on the neighboring cells (no
handover is possible). Then there will be an increase in the rate of call
drops.
ATTENTION
The geographical mobility of the mobile is reduced.
If the mobile is out of its geographical area of the cell where it is, the service is
reduced.
TROUBLESHOOTING
If the alarm appears during a start-up, a problem occurred in the BTS
configuration during the installation.
If the alarm appears during a change, look at the last commands at the
OMC-R few times before the alarm appearance. Look at the changes
performed for the neighboring cells.
Check that, if the microCellInstability and microCellStability parameters
have a value, have the value "algo B". Otherwise, modify it.

Fault number:
1265
Blockage of radio channel(s) in busy state
Type
communicationsAlarm
FAULT ANALYSIS
This alarm indicates that some channels were busy by a call during a time
period that is higher than the surveillance period whose period has been
chosen by the operator.
The notification lists all the radio channels of the BTS that were busy
during the traffic surveillance, whose period has been chosen by the
operator.

BSC defense
None.

None.
FAULT LOCATION
The notification indicates, for the concerned BTS, the busy channel(s).
411-9001-104 18.05 2 February 2010
831
TROUBLESHOOTING
Step
Action
channel.
Check the call duration in comparison with the surveillance

period by checking the radResSupBusytimer parameter of the
bsc object.
If the call duration is equal or higher than the value of the

surveillance period, go to step 3.
If it is not the call duration that is concerned and that is the

source of the fault number, call the manufacturer.
Increase the value of the surveillance period.

Set the transceiver object to "locked" then "unlocked".


--End--

Fault number:
1266
Blockage of radio channel(s) in free state
Type
communicationsAlarm
FAULT ANALYSIS
When the radResSupervision parameter is "true", a notification with the
1266 fault number is sent periodically to the OMC-R.
The notification indicates all the BTS radio channels that have been
continuously free for the previous notification.
This period is determined by the radResSupFreetimer parameter of the
bsc object. This parameter sets the maximum duration of non utilization
for a radio channel.

411-9001-104 18.05 2 February 2010
832

BSC defense
None.

ATTENTION
FAULT LOCATION
The notification indicates, for the concerned BTS, the free channel(s).
TROUBLESHOOTING
Step
Action
channel.
Analyze the traffic on the network by checking the rate of call

drop (TCH number busy in comparison to cell resource number).
see Nortel GSM BSS Parameter Reference (411-9001-124).
If the traffic is low, the fault number 1266 is normal.

If the traffic is important (almost equal to the TCH number
in the cell), the faulty channels are not used. Call the
manufacturer.
Analyze the traffic on the network by checking the rate of

SDCCH allocation failures.
Check the synthetic counter C8706 (cellSdcchResourceFailure
Ratio).
If the counter value is low (SDCCH blocking is not observed),

the fault number 1266 is normal.
If the counter value is high (SDCCH blocking is observed),

and still fault number 1266 is observed, this requires further
investigation. Call the manufacturer.
--End--

Fault number:
1268
NO RESPONSE TO A SACCH FILLING (SYS 5, 6, 5bis, 5ter

or meas_info)
Type
communicationsAlarm

411-9001-104 18.05 2 February 2010
833
FAULT ANALYSIS
acknowledgment requests SACCH FILLING sent by the BSC. As long
as the BSC has not received response, it repeats the procedure of

BSC defense
None.

ATTENTION
The service is reduced because the channels supported by the faulty TRX are
not available for calls.
TROUBLESHOOTING
Step
Action
Look for the TRX supported the TDMA quoted in the alarm by
performing a "Display all" command on the transceiverEquipment
objects.
If all the channels are not available, perform the procedure of

return to service.
Otherwise, stop the maintenance procedure because the

state of the system is normal.
Set the transceiverEquipment object associated with the TDMA

to "locked" then to "unlocked".
Wait that the state of the transceiver object becomes "enabled".

--End--

Fault number:
1500
Measurement received on an unknown frequency of

neighboring cell
Type
communicationsAlarm

411-9001-104 18.05 2 February 2010
834
FAULT ANALYSIS
This alarm indicates that a measurement has been received on an
unknown frequency of a neighboring cell in GSM 900 or GSM 1800 mode.
The message is sent at the end of the communication.

Fault number:
1505
No response to a BCCH INFO (SYS 1, 2, 3, 4, 2 bis, 7, 8, 2 ter,

13)
Type
communicationsAlarm
FAULT ANALYSIS
acknowledgment requests SYS INFO sent by the BSC. As long as
the BSC has not received any response, it repeats the procedure of

BSC defense
None.

CAUTION
TROUBLESHOOTING
Step
Action
If the alarm appears during the downloading, do not take into

account this alarm. Otherwise, go to step 2.
Set the btsSiteManager concerned to "locked" then "unlocked".

The problem concerns the old passive chain of the BSC. Look
for alarms concerning the BSC and treat them.

411-9001-104 18.05 2 February 2010
835

--End--

Fault number:
1506
No distribution available for a cell
Type
communicationsAlarm
FAULT ANALYSIS
This warning indicates that no distribution is available for the cell
concerned.
To help network monitoring, the distribution at TDMA level of some
measurements done on radio interface is provided for the TRX of given
cells and on a periodic time frame. Distributions are collected by the BSC
and aggregated in a file that is uploaded by the OMC-R.
The available distributions are the following:
power control steps

RxLev and RxQual
FER uplink
Timing advance
SNR
RxLev rescaled to Pmax
TEPMOS
FER downlink
Downlink voice quality indicator
List of causes:
0 "No stop_distribution_ack received":

If for all TRXs of a cell the BTS has sent no stop_distribution_ack
message to the BSC, then the BSC emits a notification
1506 no distribution available for a cell with the cause "No
stop_distribution_ack received", even if all TRXs are locked.
1 "No measurements available":

If for all TRXs of a cell the BTS has sent no measurements at all to the
BSC, then the BSC emits a notification 1506 no distribution available

411-9001-104 18.05 2 February 2010
836
for a cell with the cause "No measurements available", even if all
TRXs are locked.
BSC defense
None.
TROUBLESHOOTING

Fault number:
1507
Interference matrix running
Type
Attribute value change
FAULT ANALYSIS
This attribute value change indicates whether the Interference Matrix
process has started or is finished.
If the "endInterferenceMAtrix " field equals 0, the attribute value change
notifies the end of Interference Matrix process for the associated cell.
If the "endInterferenceMAtrix " field equals 1, the IM process is started.
TROUBLESHOOTING
No maintenance is required.

Fault number:
1508
Data service impact (SYS 13 size exceeded)
Type
Quality of Service Alarm
FAULT ANALYSIS
When the operator configures maximum hopping frequencies (64
frequencies) and activates GPRS or EGPRS in a cell, then "System
Information 13 rest octet" size exceeds 21 octets. As a result the "System
Information 13 rest octet" field is truncated and this begin-of-fault alarm
is sent.

411-9001-104 18.05 2 February 2010
837
64 frequencies is the maximum number granted by the OMC-R (semantic

control). But operators must also take into account Engineering
recommendations given in BSS Parameters User Guide (BPUG).
The end-of-fault alarm is sent after the "System Information 13 rest octet"
field size has become equal to 21 octets or less.

BSC defense
None.

CAUTION
There is a partial or full impact on data service (whereas CS
traffic is still maintained).
The information relative to data services on impacted cell(s) are
not fully sent to the BTS.
TROUBLESHOOTING
see BSS Parameter User Guide (BPUG PE/DCL/DD/0036) to configure
the cell (cellAllocation and mobileAllocation parameters for the bts object)
in order to respect Engineering recommendations (maximum hopping
frequency number) and to have the "System Information 13 rest octet" field
size equal to 21 octets or less.
Normally, the maximum number of frequencies that can be set up with
cellAllocation parameter is 64for each frequency band. However, due
to SI13 size constraints, when GPRS or EDGE is activated in the cell
and there is at least one hopping data TDMA, the limitation becomes a
maximum of 49 - n frequencies.
where n is the number of non-hopping frequencies in the cell.

411-9001-104 18.05 2 February 2010
838

411-9001-104 18.05 2 February 2010
839
Index
E
e-cell
1051 Loss of layer 3 with remote
GSM entity 463
1052 GSM entity downloading
failure 463
Source (01) Bad hardware
reference or manufacturer ID 474
Source (03) No change of one of
BOOT after reset 478
Source (04) This entity is engaged
in another downloading 479
Source (05) Software not
compatible with hardware 480
Source (06) File access error 483
Source (07) Repetitive errors
(NACK, timeout, ...) while
downloading a file 484
Source (08) Wrong software
reference on a non
downloadable TEI 479
Source (16) File to download
unavailable 492
1053 GSM entity configuration
regression 702
1054 Loss of layer 2 (or no
establishment) with remote
GSM entity 703
1055 Abis negative acknowledgement indication 703
Source (02) Equipment unable to
perform such test 708
Source (03) Invalid configuration 709
Source (06) Data inconsistency 712
Source (10) Unknown Abis PCM 714
Source (23) Too many signaling
timeslots 718
Source (25) Out of sequence

message 719
Source (34) The BTS has not
acknowledged the TX power
consign request 723
Source (65) Exceeded DL joker
DS0 pool number 740
regression 742
1059 Invalid message received on
Abis interface on O and M link 743
1060 Abis event reporting a
hardware fault
Source (3277074) BCCH config
dump: PMOD 750
Source (3277090) SACCH config
dump: PMOD 751
Source (3277106) L1M config
dump: PMOD 751
Source (3277107) RSL anomaly:
PMOD 751
1060 Abis event reporting a transient
default 744
Source (3145730) Message
unknown: PMNU 746
Source (3145760) Restart due to
reset by BSC: PMNU 746
Source (3145761) Restart due
to reset by the reset button:
PMNU 746
power on: PMNU 746
Source (3145763) Restart due to a
too long PCM scanning: PMNU 747
Source (3145764) Restart
requested by the active board:
PMNU 747

411-9001-104 18.05 2 February 2010
840

software upgrade: PMNU 747
hardware watchdog: PMNU 748
loss of lock: PMNU 748
Source (3276823) FACCH
congestion: PMOD 748
Source (3276834) PMOD reset
by BCF after message non
acknowledged: PMOD 749
the timeout on the OML link with
BSC: PMOD 749
the timeout on the OML link with
BCF: PMOD 750
software upgrade: PMOD 750
1061 Abis mapping issue for a
TDMA 752
1063 TRX allocation for a TDMA 753
hardware fault 754
Source (3145737) Base-extension
communication fault: PMNU 778
Source (3145777) Hardware:
PMNU 785
Source (3211262) Self test failed:
PMNU 780
Source (3211265) RX fault:
RDRX 811
Source (3211266) Hardware:
RDRX 816
Source (3276806) BBFILTER
ASIC fault: PMOD 789
PMOD 794
Source (3276810) Major fault on
TX: PMOD 798
Source (3276832) The TX has
not acknowledged the power
consign request: PMOD 803
Source (3277072) BCCH first
config failed: PMOD 806
Source (3277073) BCCH second
Source (3277088) SACCH first
Source (3277089) SACCH second

Source (3277104) L1M first config
failed: PMOD 808809
Source (3342340) SYNO clock not
locked on the network: ABIS
BTS SYNCHRO 758
Source (3407873) PSU failure:
PSU 809
Source (6488065) PCM: PCM 778
Source (6619137) Power fault: AC
power supply 763
Source (6815745) Hardware: PA 768
Source (6815777) PA DRX control
loop fault: PA 773
Source (7274497) External alarm:
External alarm 766
Source (8060929) Threshold
exceeded: Internal temperature 766
1070 TRX synchronization failure 820
1073 Attempt of download failure on
a GSM entity 821
Source (09) No response to LOAD
message 825
Source (10) Received LOAD INIT
NACK 825
Source (11) Received message
LOAD DATA NACK 826
LOAD END NACK 826
Source (13) Received message 826
1080 Access fault 826
1258 No BTS response on
preprocessing configuration 828
1259 Negative acknowledgement on
preprocessing command 829
1265 Blockage of radio channel(s) in
busy state 830
free state 831
1268 No response to a SACCH
FILLING (SYS 5, 6, 5 bis or 5
ter) 832
1268 NO RESPONSE TO A SACCH
FILLING (SYS 5, 6, 5bis, 5ter or
meas_info) 832
1500 Measurement received on
an unknown frequency of
neighboring cell 833

411-9001-104 18.05 2 February 2010
841
1505 No response to a BCCH INFO

(SYS 1, 2, 3, 4, 2 bis, 7, 8, 2 ter,
13) 834
1506 No distribution available for a
cell 835
1507 Interference matrix running 836
1508 Data service impact (SYS 13
size exceeded) 836
S
S2000H
GSM entity 27
1052 GSM entity downloading failure 27
BOOT after reset 43
reference on a non
downloadable TEI 45
unavailable 62
regression 272
GSM entity 273
Source (05) Cell parameters
inconsistency 281
timeslots 289
message 291

consign request 295
DS0 pool number 312
1056 Incorrect parameter settings at
the OMC-R 314
regression 320
default 322
Source (6422530) Unknown
message on Abis interface:
SBCF 327
reset by BSC: SBCF 327
reset by reset button: SBCF 327
power on: SBCF 328
too long PCM scanning: SBCF 328
SBCF 328
software upgrade: SBCF 329
hardware watchdog: SBCF 329
double bus fault: SBCF 329
Man Machine Interface I and C
reset button: SBCF 329
Source (9437196) Frequency
collision on FH bus: DRX 324
Source (9437199) Beginning of TX
isolation for maintenance: DRX 324
Source (9437200) End of TX
congestion: DRX 325
Source (9437218) Nack answer:
DRX 326
Source (9437219) DRX reset by
BSC: DRX 327
TDMA 330

411-9001-104 18.05 2 February 2010
842

hardware fault 330
Source (3342340) SYNO clock
not locked on the network:
ABIS_BTS_SYNCHRO 344
Source (5570561) LNA fault: LNA 412
Source (6029313) Fault on VGA:
VGA 446
power supply 354
Source (6684673) Power fault: DC
power supply 366
Source (6750209) VSWR:
Transmit antenna 441
Source (6815746) DRX/PA
connection: PA 421
Source (6881281) Software
detection: DRX main reception
chain 408
detection: DRX diversity
reception chain 403
exceeded: Cabinet high
temperature alarm 360
exceeded: Cabinet low
Source (7340033) Over current:
Splitter output 436
Rx splitter M 431
Rx splitter D 426
External alarm 373
Source (9437185) RX fault: DRX 373
Source (9437187) Loss of PCM
link: DRX 376
ASIC fault: DRX 378
DRX 381
TX: DRX 383
Source (9437206) DRX link: DRX 388

consign request: DRX 393
loop fault: DRX 397
a GSM entity 448
message 450
NACK 450
LOAD DATA NACK 450
LOAD END NACK 450
busy state 455
free state 456
1268 No response to a SACCH filling
(SYS 5, 6, 5 bis or 5 ter) 457
neighbouring cell 458
1505 No response to a BCCH info
(SYS 1, 2, 3, 4, 2 bis, 7, 8, 2 ter,
13) 459
size exceeded) 460
S2000L
GSM entity 27
1052 GSM entity downloading failure 27
BOOT after reset 43

411-9001-104 18.05 2 February 2010
843

reference on a non
downloadable TEI 45
unavailable 62
regression 272
GSM entity 273
Source (05) Cell parameters
inconsistency 281
timeslots 289
message 291
consign request 295
DS0 pool number 312
1056 Incorrect parameter settings at
the OMC-R 314
regression 320
default 322
Source (6422530) Unknown
message on Abis interface:
SBCF 327
reset by BSC: SBCF 327
reset by reset button: SBCF 327
power on: SBCF 328
too long PCM scanning: SBCF 328

SBCF 328
software upgrade: SBCF 329
hardware watchdog: SBCF 329
double bus fault: SBCF 329
Man Machine Interface I and C
reset button: SBCF 329
Source (9437196) Frequency
collision on FH bus: DRX 324
Source (9437199) Beginning of TX
Source (9437200) End of TX
congestion: DRX 325
Source (9437218) Nack answer:
DRX 326
Source (9437219) DRX reset by
BSC: DRX 327
TDMA 330
hardware fault 330
Source (3342340) SYNO clock
not locked on the network:
ABIS_BTS_SYNCHRO 349
Source (5570561) LNA fault: LNA 415
power supply 357
Source (6684673) Power fault: DC
power supply 369
Source (6750209) VSWR:
Transmit antenna 443
Source (6815746) DRX/PA
connection: PA 424
detection: DRX main reception
chain 410
detection: DRX diversity
reception chain 405

411-9001-104 18.05 2 February 2010
844

exceeded: Cabinet high
exceeded: Cabinet low
Splitter output 438
Rx splitter M 434
Rx splitter D 429
External alarm 373
Source (9437185) RX fault: DRX 373
Source (9437187) Loss of PCM
link: DRX 376
ASIC fault: DRX 378
DRX 381
TX: DRX 386
Source (9437206) DRX link: DRX 391
consign request: DRX 393
loop fault: DRX 400
a GSM entity 448
message 450
NACK 450
LOAD DATA NACK 450
LOAD END NACK 450
busy state 455
free state 456
1268 No response to a SACCH filling

(SYS 5, 6, 5 bis or 5 ter) 457
neighboring cell 458
1505 No response to a BCCH info
(SYS 1, 2, 3, 4, 2 bis, 7, 8, 2 ter,
13) 459
size exceeded) 460
S8000 Indoor
1052 GSM entity downloading failure
Source (14) Received CSM LOAD
CONTAINER NAK 487
S8000 Outdoor
CONTAINER NAK 487
S8002
CONTAINER NAK 487
S8003
CONTAINER NAK 487
S8006
CONTAINER NAK 487

411-9001-104 18.05 2 February 2010

Release: V18.0 PC2
Publication: 411-9001-104
Document revision: 18.05
Document release date: 2 February 2010
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, 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.
_ 17+ 18+
To provide feedback or to report a problem in this document, go to www.nortel.com/documentfeedback.

www.nortel.com

BTS S2000H - S2000L - E-Cell Fault Clearing

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BTS S2000H - S2000L - E-Cell Fault Clearing

Uploaded by

Copyright:

Available Formats

Global System for Mobile Communications (GSM)

Nortel GSM BTS

Global System for Mobile Communications (GSM)

All other trademarks are the property of their respective owners.

Chapter 1 How to use this manual

Chapter 2 S2000 H/L BTS fault numbers

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

Global System for Mobile Communications (GSM)

Global System for Mobile Communications (GSM)

Global System for Mobile Communications (GSM)

Source 9: Missing RfTrans management Abis GSM function 318

Global System for Mobile Communications (GSM)

Global System for Mobile Communications (GSM)

Fault number: 1259 (S2000 H/L BTS)

Chapter 3 e-cell fault numbers

3.1 Fault number: 1051 (e-cell) 463

Global System for Mobile Communications (GSM)

Global System for Mobile Communications (GSM)

Global System for Mobile Communications (GSM)

Global System for Mobile Communications (GSM)

Global System for Mobile Communications (GSM)

New in this release

Features (page 19)

Global System for Mobile Communications (GSM)

20 New in this release

Global System for Mobile Communications (GSM)

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

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

Nortel GSM BSS Overview (411-9001-001)

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

Global System for Mobile Communications (GSM)

Global System for Mobile Communications (GSM)

Chapter 1 How to use this manual

locating and identifying the faulty items of equipment, using information

replacing the faulty items of equipment, using the replacement

When a faulty item of equipment sends an alarm to the OMC-R, this

1.2 The types of spontaneous messages

spontaneous messages indicating a hardware fault (fault number 1067)

Global System for Mobile Communications (GSM)

24 Chapter 1 How to use this manual

spontaneous messages indicating a transient event for warning (fault

spontaneous messages indicating the arrival of state changes on an

1.2.2 Events detected by the BSC

1.3 Description of a fault number sheet

1.3.1 Header of the sheet

the fault number and possibly the source

1.3.2 Main body of the sheet

Reaction of the system

Impact on the service

Global System for Mobile Communications (GSM)

1.3 Description of a fault number sheet 25

On-site maintenance (possibly using the OMC-R)

Global System for Mobile Communications (GSM)

26 Chapter 1 How to use this manual

Global System for Mobile Communications (GSM)

Chapter 2 S2000 H/L BTS fault

Loss of layer 3 with remote GSM entity

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

GSM entity downloading failure

Global System for Mobile Communications (GSM)

28 Chapter 2 S2000 H/L BTS fault numbers

2.2.1 Source 0: No response to status

Bad hardware reference