GSM BTS S8000 S8002 S8003 S8006 Fault Clearing

Global System for Mobile Communications (GSM)
Nortel GSM BTS

S8000/S8002/S8003/S8006
Fault Clearing
Release: V18.0 PC2
Document Revision: 18.06
www.nortel.com
411-9001-103
.

Release: V18.0 PC2
Publication: 411-9001-103
Document release date: 20 January 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, S2000 and S8000 are trademarks of Nortel Networks.
All other trademarks are the property of their respective owners.
_ 17+ 18+
Contents
New in this release
Features
17
17
Introduction
19
Chapter 1 How to use this manual
25
1.1 Introduction 25
1.2 The types of spontaneous messages 26
1.2.1 Events detected by the BTS 26
1.2.2 Events detected by the BSC 26
1.3 Description of a fault number sheet 26
1.3.1 Header of the sheet 26
1.3.2 Main body of the sheet 26
1.4 Help 27
1.4.1 Loading the CD-ROM 27
Chapter 2 S8000, S8002, S8003, and S8006 BTS fault

numbers
29
2.1 Fault number: 1051 (S8000, S8002, S8003, and S8006 BTS) 29
2.2.1 Source 0: No response to status request 41
2.2.2 Source 1: Bad hardware reference of manufacturer ID 43
2.2.3 Source 2: SUP stop receipt 46
2.2.4 Source 3: No change to one of BOOT states after reset 48
2.2.5 Source 4: This entity is engaged in another downloadingSource 8: Wrong
software reference on a non downloadable TEI 52
2.2.6 Source 5: Software not compatible with hardware 54
2.2.7 Source 6: File access error 58
2.2.8 Source 7: Repetitive errors (NACK, timeout, ...) while downloading a
file 61
2.2.9 Source 9: No response to download message 61
2.2.10 Source 14: Received CSM LOAD CONTAINER NAK 64
2.2.11 Source 15: File to download empty 66
2.2.12 Source 16: File to download unavailable 68
2.2.13 Source 17: Buffer allocation failure 69

Nortel GSM BTS S8000/S8002/S8003/S8006 Fault Clearing
411-9001-103 18.06 20 January 2010
4
2.2.14 Source 18: Bad sending buffer size value 72
2.2.15 Source 19: Failure during OMU switchover 74
2.2.16 Source 20: Bad TEI sent by BTS in the CSM software update report
message 76
2.2.17 Source 21: CSM software update report with the cause - unknown TEI
- 78
2.2.18 Source 22: CSM software update report with the cause - equipment
failure - 81
2.2.19 Source 23: CSM software update report with the cause - downloading
failure - 83
2.2.20 Source 24: CSM software update report with the cause - not able to
perform- 85
2.2.21 Source 25: CSM software update report with the cause - wrong software
reference - 87
2.2.22 Source 26: CSM software update report with the cause - wrong
configuration reference - 90
2.2.23 Source 27: CSM software update report with the cause - restart request
- 92
2.2.24 Source 28: CSM software update report with the cause - data
inconsistency - 94
2.2.25 Source 29: CSM software update report with the cause - message out of
sequence - 97
2.2.26 Source 30: CSM software update report with the cause - background not
available - 99
2.2.27 Source 31: CSM software update report with the cause - incompatible
RM version - 101
2.2.28 Source 32: CSM software update report with the cause - downloading in
progress - 104
2.2.29 Source 33: Bad report sent by BTS in the CSM software update report
message 106
2.2.30 Source 34: No BTS response on CSM software update init-control
message 108
2.2.31 Source 35: Nack received on the abort requested by operator 111
2.2.32 Source 36: Bad report sent by BTS in the CSM software update abort
message 113
2.2.33 Source 37: No BTS response on CSM software update abort
message 115
2.2.34 Source 38: Flash activate nack with the cause - unknown TEI - 118
2.2.35 Source 39: Flash activate nack with the cause - equipment failure
- 120
2.2.36 Source 40: Flash activate nack with the cause - downloading failure
- 122
2.2.37 Source 41: Flash activate nack with the cause - not able to perform
- 124
2.2.38 Source 42: Flash activate nack with the cause - flash inconsistency
- 127
2.2.39 Source 43: Flash activate nack with the cause - data inconsistency
411-9001-103 18.06 20 January 2010
5
- 129
2.2.40 Source 44: Flash activate nack with the cause - wrong soft ref - 131
2.2.41 Source 45: Flash activate nack with the cause - wrong config ref - 133
2.2.42 Source 46: CSM downloading start nack with the cause - unknown TEI
- 136
2.2.43 Source 47: CSM downloading start nack with the cause - equipment
failure - 138
2.2.44 Source 48: CSM downloading start nack with the cause - downloading
failure - 140
2.2.45 Source 49: CSM downloading start nack with the cause - message out
of sequence - 142
2.2.46 Source 50: CSM downloading start nack with the cause - wrong soft ref
- 145
2.2.47 Source 51: CSM downloading start nack with the cause - wrong config
ref - 147
2.2.48 Source 52: CSM downloading start nack with a bad cause 149
2.2.49 Source 53: No BTS response on CSM downloading start message 152
2.2.50 Source 54: CSM downloading end nack with the cause - unknown TEI
- 154
2.2.51 Source 55: CSM downloading end nack with the cause - equipment
failure - 156
2.2.52 Source 56: CSM downloading end nack with the cause - downloading
failure - 158
2.2.53 Source 57: CSM downloading end nack with the cause - value out of
range - 161
2.2.54 Source 58: CSM downloading end nack with a bad cause 163
2.2.55 Source 59: No BTS response on CSM downloading end message 165
2.2.56 Source 60: CSM load init nack with the cause - equipment failure - 168
2.2.57 Source 61: CSM load init nack with the cause - downloading failure
- 170
2.2.58 Source 62: CSM load init nack with the cause - message out of
sequence - 172
2.2.59 Source 63: CSM load init nack with the cause - wrong file ref - 174
2.2.60 Source 64: CSM load init nack with the cause - window size not allowed
- 177
2.2.61 Source 65: CSM load init nack with the cause - data format error - 179
2.2.62 Source 66: CSM load init nack with a bad cause 181
2.2.63 Source 67: No BTS response on CSM load init message 183
2.2.64 Source 68: CSM load data nack with the cause - equipment failure
- 186
2.2.65 Source 69: CSM load data nack with the cause - downloading failure
- 188
2.2.66 Source 70: CSM load data nack with the cause - message out of
sequence - 190
2.2.67 Source 71: CSM load data nack with the cause - data format error
- 192

411-9001-103 18.06 20 January 2010
6
2.2.68 Source 72: CSM load data nack with the cause - window overflow
- 195
2.2.69 Source 73: CSM load data nack with the cause - data inconsistency
- 197
2.2.70 Source 74: CSM load data nack with the cause - block not received
- 199
2.2.71 Source 75: CSM load data nack with the cause - bad block tag - 201
2.2.72 Source 76: CSM load data nack with the cause - checksum error - 204
2.2.73 Source 77: CSM load data nack with a bad cause 206
2.2.74 Source 78: Unexpected CSM load data ack 208
2.2.75 Source 79: No BTS response on CSM load data message 210
2.2.76 Source 80: CSM load end nack with the cause - equipment failure
- 213
2.2.77 Source 81: CSM load end nack with the cause - downloading failure
- 215
2.2.78 Source 82: CSM load end nack with the cause - value out of range
- 217
2.2.79 Source 83: CSM load end nack with the cause - message out of
sequence - 219
2.2.80 Source 84: CSM load end nack with the cause - data format error
- 222
2.2.81 Source 85: CSM load end nack with the cause - wrong file ref - 224
2.2.82 Source 86: CSM load end nack with the cause - data inconsistency
- 226
2.2.83 Source 87: CSM load end nack with the cause - checksum error - 229
2.2.84 Source 88: CSM load end nack with a bad cause 231
2.2.85 Source 89: No BTS response on CSM load end message 233
2.2.86 Source 90: Bad report sent by BTS during an internal update 235
2.2.87 Source 91: CSM load init nack with the cause - file already open - 238
2.2.88 Source 92: CSM load init nack with the cause - invalid mode - 240
2.2.89 Source 93: CSM load init nack with the cause - file cannot be unloaded
- 242
2.2.90 Source 94: CSM load init nack with the cause - flash flag cannot access
- 244
2.2.91 Source 95: CSM load data nack with the cause - file cannot be unloaded
- 247
2.2.92 Source 96: CSM load data nack with the cause - flash flag cannot
access - 249
2.2.93 Source 97: CSM load data nack with the cause - boot cannot be
unloaded - 251
2.2.94 Source 98: CSM load data nack with the cause - data decode error
- 254
2.2.95 Source 99: CSM load data nack with the cause - table cannot access
- 256
2.2.96 Source 100: CSM load data nack with the cause - RAM mapping error
- 258

411-9001-103 18.06 20 January 2010
7
2.2.97 Source 101: CSM load data nack with the cause - flash access error
- 260
2.2.98 Source 102: CSM load data nack with the cause - flash RAM error
- 263
2.2.99 Source 103: CSM load data nack with the cause - flash erase error
- 265
2.2.100 Source 104: CSM load data nack with the cause - internal abort - 267
2.2.101 Source 105: CSM flash activate response with a bad cause 269
2.2.102 Source 106: DTM error during token allocation 272
2.2.103 Source 107: CSM software update report with the cause: TRX software
incompatibility 274
2.2.104 Source 108: Too many different deliveries in the cell group 276
2.5.1 Source 1: Equipment failure 284
2.5.2 Source 2: Equipment unable to perform such test 285
2.5.3 Source 3: Equipment unable to perform such configuration 286
2.5.4 Source 4: Unknown test 288
2.5.5 Source 5: Cell parameters inconsistency 288
2.5.6 Source 6: Data inconsistency 290
2.5.7 Source 7: Value out of range 291
2.5.8 Source 8: TEI not present 292
2.5.9 Source 9: Unknown Abis PCM_Time_Slot 293
2.5.10 Source 10: Unknown Abis PCM 293
2.5.11 Source 11: Wrong software reference 294
2.5.12 Source 12: Further files required 294
2.5.13 Source 13: Failure during activation 295
2.5.14 Source 14: Data format error 295
2.5.15 Source 15: Window overflow 295
2.5.16 Source 16: Normal completion 295
2.5.17 Source 17: Transfer aborted 295
2.5.18 Source 18: Checksum error 296
2.5.19 Source 19: File incomplete 296
2.5.20 Source 20: File already present and correct 296
2.5.21 Source 21: File cannot be downloaded 296
2.5.22 Source 22: Entity engaged in other download 296
2.5.23 Source 23: Too many signaling timeslots 297
2.5.24 Source 24: Too many TEI connections to physical channel 298
2.5.25 Source 25: Out of sequence message 298
2.5.26 Source 26: Incorrect IEI 300
2.5.27 Source 27: Wrong file reference 300
2.5.28 Source 28: Bad cell number 301
2.5.29 Source 29: Bad related TEI 301

411-9001-103 18.06 20 January 2010
8
2.5.30 Source 30: Bad timeslot 301
2.5.31 Source 31: Window size not allowed 301
2.5.32 Source 32: Flash boot required 301
2.5.33 Source 33: Wrong config reference 302
2.5.34 Source 34: The BTS has not acknowledged the TX power consign
request 302
2.5.35 Source 35: Downloading aborted 307
2.5.36 Source 36: Files missing 307
2.5.37 Source 37: Buffer overflow 308
2.5.38 Source 38: Block not received 308
2.5.39 Source 39: Downloading restart 308
2.5.40 Source 40: Request not supported 308
2.5.41 Source 41: Downloading failure 308
2.5.42 Source 42: Start-up failure 309
2.5.43 Source 43: Maximum number of joker TS 309
2.5.44 Source 44: Bad chain type 312
2.5.45 Source 45: Bad radio timeslot reference 312
2.5.46 Source 46: Bad internal Link EDGE configuration 312
2.5.47 Source 47: Inconsistency mapping 312
2.5.48 Source 48: Inconsistency number of joker DS0 313
2.5.49 Source 49: Invalid mode 313
2.5.50 Source 50: File already open 313
2.5.51 Source 51: File cannot be unloaded 313
2.5.52 Source 52: Boot cannot be unloaded 313
2.5.53 Source 53: Data decode error 314
2.5.54 Source 54: Flash flag cannot access 314
2.5.55 Source 55: Table cannot access 314
2.5.56 Source 56: RAM mapping error 314
2.5.57 Source 57: Flash access error 314
2.5.58 Source 58: Flash write error 315
2.5.59 Source 59: Flash erase error 315
2.5.60 Source 60: Internal abort 315
2.5.61 Source 61: Equipment not able to get external synchronization 315
2.5.62 Source 62: Synchronization in progress 315
2.5.63 Source 63: Dynamic Abis feature not supported 316
2.5.64 Source 64: Inconsistent number of joker DS0 317
2.5.65 Source 65: Exceeded DL joker DS0 pool number 319
2.5.66 Source 255: Non-significant value 321
2.6.1 Source 0: Incorrect priority on transceiver 324
2.6.2 Source 1: Incorrect setting of channel on transceiver 324
2.6.3 Source 2: Cell without BCCH TDM 324
2.6.4 Source 3: Radio Time Slot not used 325
2.6.5 Source 4: Wrong value for BSS TEI in T1 mode 325
411-9001-103 18.06 20 January 2010
9
2.6.6 Source 5: Cell cfg with cavity and dual band not acceptable 325
2.6.7 Source 6: Missing Site management Abis GSM function 325
2.6.8 Source 7: Missing Abis Signalling management Abis GSM function 325
2.6.9 Source 8: Missing Abis traffic management Abis GSM function 326
2.6.10 Source 9: Missing RfTrans management Abis GSM function 326
2.6.11 Source 10: Missing cell management Abis GSM function 326
2.6.12 Source 11: Missing TDMA management Abis GSM function 326
2.6.13 Source 12: Missing TS management Abis GSM function 327
2.6.14 Source 13: The TDMA exists in RDC but the object was not created.
327
2.6.15 Source 14: Too many EDGE TDMAs (more than 16 per site) configured
327
2.9.1 BRC (source: Manual switch on battery power) 351
2.9.2 BRC (source: Automatic switch on battery power) 351
2.9.3 BRC (source: Manual switch on main power) 351
2.9.4 BRC (source: Automatic switch on main power) 352
2.9.5 Cavity (source: Cavity parked after tuning fault (min not found)) 352
2.9.6 Cavity (source: Nack answer from cavity) 354
2.9.7 Cavity (source: Cavity parked after tuning fault (power too low)) 354
2.9.8 Cavity (source: Cavity parked after tuning fault (tuning detector)) 355
2.9.9 CMCF board (source: Unknown message) 355
2.9.10 CMCF board (source: Restart requested by the active board) 356
2.9.11 CMCF (source: Board reset asked by OMC) 356
2.9.12 CMCF board (source: Restart due to hardware watchdog) 357
2.9.13 CMCF boards (source: Restart due to double bus fault) 357
2.9.14 CMCF boards (source: Reset for new Lapd parameters CMCF) 357
2.9.15 CMCF boards (source: ABIS PCM statistics) 358
2.9.16 CSWM board (source: Restart due to hardware watchdog) 358
2.9.17 CSWM board (source: Restart due to double bus fault) 359
2.9.18 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Frequency
collision on FH bus) 359
2.9.19 DRX or eDRX or DRX-ND3 or eDRX2 (source: Restart requested by
the BCF) 360
2.9.20 DRX or eDRX or DRX ND3 or eDRX2 modules (source: FACCH
congestion) 360
2.9.21 DRX or eDRX or DRX ND3 or eDRX2 modules (source: Reset due to
hardware watchdog) 361
2.9.22 DRX or eDRX or DRX ND3 or eDRX2 modules (source: Restart due to
double bus fault) 362
2.9.23 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: BCCH config
dump) 362
2.9.24 DRX or eDRX or DRX-ND3 modules or eDRX2 (source: SACCH config
411-9001-103 18.06 20 January 2010
10
dump) 363
2.9.25 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: L1M config
dump) 363
2.9.26 DRX or eDRX or eDRX2 or DRX-ND3 modules (source: RSL
anomaly) 363
2.9.27 IPM-USER core (source: Restart due to power-on) 364
2.9.28 IPM-USER core (source: Restart due to reset by button) 364
2.9.29 IPM-USER core (source: Restart due to software upgrade) 365
2.9.30 IPM-USER core (source: Restart due to hardware watchdog) 365
2.9.31 IPM-USER core (source: IBOS authentication has failed) 366
2.9.32 IPM-USER core (source: No TCP connection can be set up with
IGM) 366
2.9.33 IPM-USER core (source: Reset requested by IGM with no Ethernet
switch reset) 367
2.9.34 IPM-USER core (source: Reset requested by IGM with Ethernet switch
reset) 367
2.9.35 IPM-USER core (source: Reset requested by IBOS with BIST execution
and Ethernet switch reset) 368
2.9.36 IPM-USER core (source: Reset requested by IBOS with no BIST
execution and Ethernet switch reset) 368
2.9.37 IPM-USER core (source: Reset requested by IBOS with BIST execution
and no Ethernet switch reset) 369
execution nor Ethernet switch reset) 370
2.9.39 IPM-USER core (source: Restart after TML commissioning) 370
2.9.40 IPM-USER core (source: Connection with IGM has been lost (no status
received for 7 keep-alive periods)) 371
2.9.41 IPM-USER core (source: No response to DHCP requests for 15
minutes) 371
2.9.42 IPM-USER core (source: No response to DNS requests for 15
minutes) 372
2.9.43 IPM-USER core (source: Debug) 372
2.9.44 IPM-USER core (source: Soft) 373
2.9.45 RIPM-USER core (source: Restart due to power-on) 373
2.9.46 RIPM-USER core (source: Restart due to reset by button) 374
2.9.47 RIPM-USER core (source: Restart due to software upgrade) 374
2.9.48 RIPM-USER core (source: Restart due to hardware watchdog) 375
2.9.49 RIPM-USER core (source: IBOS authentication has failed) 375
2.9.50 RIPM-USER core (source: No TCP connection can be set up with
IGM) 376
2.9.51 RIPM-USER core (source: Reset requested by IGM with no Ethernet
switch reset) 376
2.9.52 RIPM-USER core (source: Reset requested by IGM with Ethernet switch
reset) 377
2.9.53 RIPM-USER core (source: Reset requested by IBOS with BIST

411-9001-103 18.06 20 January 2010
11
2.9.54 RIPM-USER core (source: Reset requested by IBOS with no BIST
execution and no Ethernet switch reset) 378
execution nor Ethernet switch reset) 379
2.9.57 RIPM-USER core (source: Restart after TML commissioning) 379
2.9.58 RIPM-USER core (source: Connection with IGM has been lost (no
status received for 7 keep-alive periods)) 380
2.9.59 RIPM-USER core (source: No response to DHCP requests for 15
minutes) 380
2.9.60 RIPM-USER core (source: No response to DNS requests for 15
minutes) 381
2.9.61 RIPM-USER core (source: Debug) 381
2.9.62 RIPM-USER core (source: Soft) 382
2.9.63 RIPM-USER core (source: Reset requested by active with BIST
execution) 383
2.9.64 RIPM-USER core (source: Reset requested by active with no BIST
execution) 383
2.9.65 Tx Filters (source: VSWR level 2) 384
2.11 Attribute value change: 1063 (S8000, S8002, S8003, and S8006 BTS) 386
2.12.1 ACU climatic unit (source: Cooler fault) 413
2.12.2 ALCO board (source: Major fault) 416
2.12.3 Battery cabinet (source: Over temperature) 419
2.12.4 Battery cabinet (source: DC power fault) 422
2.12.5 Battery cabinet (source: Doors) 425
2.12.6 BCF cabinet door contact(source: BCF cabinet door contact
detection) 429
2.12.7 BCF cabinet fan (source: BCF cabinet fan fault) 433
2.12.8 BCF power supply (source: Volt) 435
2.12.9 BRC (source: Manual switch on battery power) 438
2.12.10 BRC (source: Automatic switch on battery power) 438
2.12.11 BRC (source: Manual switch on main power) 438
2.12.12 BRC (source: Automatic switch on main power) 438
2.12.13 BRC (source: Battery failure) 439
2.12.14 BRC (source: Monitored battery not present) 440
2.12.15 BRC (source: Internal inconsistency) 441
2.12.16 BTS SYNCHRONIZATION (source: SYNO clock not locked on the
network) 441
2.12.17 BTS synchronization (source: Synchro not locked because OCVXO
is KO) 448
2.12.18 BTS synchronization (source: GPS synchronization unavailable) 451
2.12.19 BTS synchronization (source: Loss of GPS synchronization) 456

411-9001-103 18.06 20 January 2010
12
2.12.20 BTS SYNCHRONIZATION (source: Lack of GPS synchronization
accuracy) 461
2.12.21 BTS SYNCHRONIZATION (source: Master synchronization
unavailable) 466
2.12.22 BTS SYNCHRONIZATION (source: Loss of master GSM time) 471
2.12.23 BTS SYNCHRONIZATION (source: Loss of master SY) 475
2.12.24 Cabinet door (source: Door contact detection) 479
2.12.25 Cavity (source: Cavity out of service) 483
2.12.26 Cavity (source: Cavity parked after tuning fault (min not found)) 485
2.12.27 Cavity (source: Loss of cavity initialization) 487
2.12.28 Cavity (source: Nack answer from cavity) 489
2.12.29 Cavity (source: Cavity parked after tuning fault (power too low)) 490
2.12.30 Cavity (source: Cavity parked after tuning fault (tuning detector
problem)) 492
2.12.31 Cavity (source: Internal software problem) 494
2.12.32 Cavity combiner (source: Power supply) 496
2.12.33 Cavity combiner (source: Tuning detector fault) 498
2.12.34 Cavity combiner (source: Link NOK) 500
2.12.35 C-DACS climatic system (source: Dirty filter) 502
2.12.36 C-DACS climatic system (source: DACS failed) 504
2.12.37 CMCF board (source: MCF_MCF) 507
2.12.38 CMCF board (source: Slave downloading error) 510
2.12.39 CMCF board (source: CMCF_ACT_DUPLEX_INHIBITED) 512
2.12.40 CMCF board (source: CMCF_ACT_ICST) 515
2.12.41 CMCF board (source: Duplex inhibited: feature not supported on
CMCF phase 1) 517
2.12.42 Combiner duplexer LNA or combiner H2 LNA (source: LNA fault) 520
2.12.43 Combiner duplexer VSWR or combiner H2 VSWR (source: VSWR level
1) 524
2) 524
3) 525
2.12.46 Combiner H4D LNA (source: LNA fault) 528
2.12.47 Combiner H4D VSWR (source: VSWR level 1) 532
2.12.50 Compact distribution system (source: Main breaker) 538
2.12.51 CPCMI board (source: Major) 541
2.12.52 CPCMI board (source: Slave downloading error) 541
2.12.53 CSWM board(source: Fault on active-passive CSWM link or on passive
CSWM) 544
2.12.54 CSWM board (source: Slave downloading error) 547
2.12.55 DACS climatic system (source: Dirty filter) 549
2.12.56 DACS climatic system (source: DACS failed) 551
411-9001-103 18.06 20 January 2010
13
2.12.57 Distribution system (source: Main breaker) 557
2.12.58 DRX or DRX-ND3 diversity reception chain (source: Software
detection) 560
2.12.59 DRX or DRX-ND3 main reception chain (source: Software
detection) 565
2.12.60 DRX or DRX-ND3 modules (source: Abis satellite not supported DRX
(ND3)) 569
2.12.61 DRX or DRX-ND3 modules (source: HePA not supported) 570
2.12.62 DRX or DRX-ND3 modules (source: PA configuration exceeded) 573
2.12.63 DRX or eDRX or DRX-ND3 modules (source: BBFILTER ASIC
fault) 576
2.12.64 DRX or eDRX or DRX-ND3 modules (source: The TX has not
acknowledged the power consign request) 580
2.12.65 DRX or eDRX or DRX-ND3 modules (source: RX fault) 585
2.12.66 DRX or eDRX or DRX-ND3 modules (source: L1M first config
failed) 589
2.12.67 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: BCCH first
config failed) 589
2.12.68 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: BCCH second
config failed) 590
2.12.69 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: DRX
link) 591
2.12.70 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: DRX reset by
BSC) 596
2.12.71 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: L1M second
config failed) 597
2.12.72 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Major fault
on TX) 597
2.12.73 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Nack
answer) 602
2.12.74 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: PA DRX
control loop fault) 602
2.12.75 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Post-mortem
dump zone 3) 607
2.12.76 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: SACCH first
config failed) 607
2.12.77 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: SACCH
second config failed) 608
2.12.78 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Self test
failed) 609
2.12.79 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: TRX not
anymore configured) 613
2.12.80 DSC boards (source: Major fault) 616
2.12.81 DSC boards (source: Channel_HSCX) 618
2.12.82 External alarm (source: Alarm) 621
2.12.83 Fan of the base cabinet (source: Cabinet fan fault) 621

411-9001-103 18.06 20 January 2010
14
2.12.84 F-type converters (source: Volt) 624
2.12.85 GTW boards (source: Major fault on GTW) 628
2.12.86 Internal batteries (source: Battery disconnected) 631
2.12.87 IP synchro (source: Unable to lock on IP synchronization) 634
2.12.88 IP synchro (source: Not enough synchronization packets have been
received) 636
2.12.89 IPM-USER commissioning (source: Only one IBOS commissioned at
IPM) 637
2.12.90 IPM-USER commissioning (source: DNS resolution has failed for at
least one IBOS) 638
2.12.91 IPM-USER core (source: IPM BIST failed) 639
2.12.92 IPM-USER core (source: IPM temperature) 640
2.12.93 IPM-USER core (source: DAC unable to lock, synchronization not
possible) 641
2.12.94 Lightning protector (source: Lightning protection fault) 643
2.12.95 Not protected alarm (source: Alarm) 646
2.12.96 Output Rx-splitter D (source: Over current) 646
2.12.97 Output Rx-splitter M (source: Over current) 649
2.12.98 PCM (source: PCM) 652
2.12.99 PCMI boards (source: Major fault on PCMI) 652
2.12.100 Power amplifiers (source: Hardware) 652
2.12.101 Power amplifiers (source: DRX and PA connection) 658
2.12.102 Power amplifiers (source: High temperature ) 663
2.12.103 Power amplifiers (source: High Current ) 667
2.12.104 Power amplifiers (source: PA_PSDW ) 671
2.12.105 Power amplifiers (source: VSWR fault detected by PA) 675
2.12.106 RECAL board (source: Major) 676
2.12.107 RECAL board (source: Slave downloading error) 679
2.12.108 Rectifiers (source: AC fault) 682
2.12.109 Rectifiers (source: DC fault) 686
2.12.110 Rectifiers (source: Over temperature) 688
2.12.111 Rectifiers (source: External battery level 1) 691
2.12.112 Rectifiers (source: PCU protective) 693
2.12.113 Rectifiers (source: Battery on discharges) 697
2.12.114 RIPM-USER core (source: IPM BIST failed) 699
2.12.115 RIPM-USER core (source: IPM temperature) 700
2.12.116 RIPM-USER core (source: DAC unable to lock, synchronization not
possible) 701
2.12.117 RIPM-USER core (source: No link with passive) 703
2.12.118 Rx Filter (source: LNA fault) 704
2.12.119 SYNC boards (source: Major fault on SYNC) 707

411-9001-103 18.06 20 January 2010
15
2.14.1 Source 9: No response to load message 718
2.14.2 Source 10: Received LOAD INIT NACK 718
2.14.3 Source 11: Received LOAD DATA NACK 718
2.14.4 Source 12: Received LOAD END NACK 718
2.14.5 Source 13: Received LOAD READY NACK 718
2.27 Fault number: 1506 (S8000, S8002, S8003, S8006 BTS) 730
2.30 Applicability of the fault numbers to the BTS type 734

411-9001-103 18.06 20 January 2010
16

411-9001-103 18.06 20 January 2010
17
New in this release

The following section describe what is new in this release for Nortel GSM
BTS S8006 Troubleshooting (411-9001-103) for V18.0 P&C 2 release.
Features (page 17)
Features
This document contains no feature updates in this release.

411-9001-103 18.06 20 January 2010
18 New in this release

411-9001-103 18.06 20 January 2010
19
Introduction
This document contains the fault number description and the maintenance
actions required for the S8000, S8002, S8003, and S8006 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 S8000 / S8003 Troubleshooting (411-9001-048)
Nortel GSM BSS Performance Management Observation Counters

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

(411-9001-128)
Nortel GSM BSC 3000 / TCU 3000 Troubleshooting (411-9001-132)
Nortel GSM BSS Overview (411-9001-001)

Nortel GSM BSS Fault Management Maintenance Principles
(411-9001-039)
Nortel GSM BTS S8002 Troubleshooting (411-9001-084)

Nortel GSM BTS S8006 Troubleshooting (411-9001-085)
Nortel GSM BSC 12000HC/TCU 2G Fault Clearing (411-9001-101)
Nortel GSM BSS Fault Clearing Advanced Maintenance Procedures
(411-9001-105)

411-9001-103 18.06 20 January 2010
20 Introduction
Navigation
This document consists of 2 chapters:
Chapter 1 How to use this manual (page 25), "How to use this
manual", describes how to use this maintenance manual.
Chapter 2 S8000, S8002, S8003, and S8006 BTS fault numbers

(page 29), "S8000, S8002, S8003, and S8006 BTS Fault Numbers",
contains the fault number description and the corrective maintenance
procedures applicable to the S8000, S8002, S8003 and S8006 BTS.
Safety regulations
Introduction
All the following steps must be taken during the various cabinet
maintenance procedures in order to guarantee personnel and equipment
safety.
Account must be taken of the following aspects:
general personnel safety instructions

equipment safety instructions
Precautionary messages
Caution, warning, and danger messages indicate possible risks.
CAUTION
Impact on the service and on the equipment
DANGER
Electric shock
DANGER
Environment and personnel protection
CAUTION
ESDS handling precautions

411-9001-103 18.06 20 January 2010
Safety regulations 21
Personnel and equipment safety

General personnel safety instructions
The personnel must obey the safety instructions specific to the installation
site:
rules concerning the premises (see instructions posted on site or in

the building)
rules linked to the general personnel safety instructions
The personnel working on the cabinet must be authorized to work

according to the security standards.
The cabinet main external power supply is switched off by opening the
circuit breaker on the operator box.
The mains power supply supplying the cabinet means that no work must
be done on the cabinet internal wiring without first cutting its external
mains power supply.
This BTS has been evaluated under IEEE C95.1 requirements, regarding
safety levels with respect to human exposure to radio frequency
electromagnetic fields, 3 kHz to 300 GHz.
The leakage fields and equivalent power densities are orders of magnitude
less than the maximum permissible exposures (MPEs) given in the IEEE
safety guidelines.
CAUTION
Working instructions
The personnel working on the cabinet must be authorized to
work according to the security standards.
CAUTION
During all maintenance interventions, and especially when
handling the boards, the operator must wear an antistatic
bracelet.
DANGER
Electric shock
Never replace a power supply when energized.
Equipment safety instructions

S8000 Outdoor BTS The maintenance of an S8000 Outdoor BTS is
possible up to -40 C (~ -40F).
411-9001-103 18.06 20 January 2010
22 Introduction
The BTS stays operational with the open doors at -10C (~ -14F) during
three hours, and at -40C (~ -40F) during one hour.
In the case of rainy or snowy weather, do not open the cabinet doors
without a tent set up beforehand.
DANGER
Electric shock
Ensure that the unused power cable for the Type F power
supply module is capped and secured before powering up the
S8003 BTS and/or performing any maintenance procedure (see
the following figure).

411-9001-103 18.06 20 January 2010
Safety regulations 23

411-9001-103 18.06 20 January 2010
24 Introduction

411-9001-103 18.06 20 January 2010
25
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 S8000, S8002, S8003, and
S8006 BTS for single band GSM 850, 900, 1800, 1900, E--GSM 900, and
GSM-R 900 frequency bands. GSM-R does not apply to the S8006 BTS.
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.
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.
Throughout this document (or section, as it applies), the terms DRX,
e-DRX, DRX-ND3 and eDRX2 are used indistinctly as DRX unless the
document makes a specific reference.
Alarm notifications and contents include specific information about the
particular type of equipment involved on the alarm. For example, alarms
related to DRX-ND3 will include this specific equipment type throughout
the notification.

411-9001-103 18.06 20 January 2010
26 Chapter 1 How to use this manual
V15.0 introduced EDGE and other important features, together with

DRX-ND3 full differentiation. DRX-ND3 is not EDGE compatible. For all
EDGE related alarms, the term DRX does not include DRX-ND3. This
equipment type solves obsolescence problems with DRX.
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 sent as a warning and indicating a transient

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

equipment (fault number 1058)
spontaneous messages indicating a hardware fault without loss of

capacity, triggering no defense actions on the part of the BSC. If there
are defense actions, they are local and controlled by the BTS (fault
number 1067).
1.2.2 Events detected by the BSC

Spontaneous messages are sent by the BSC giving information on the
state of relationship with the BTS or part of it (1051, 1052, 1053, 1054,
1055, 1059, 1073).
1.3 Description of a fault number sheet

A corrective maintenance sheet contains the following information:
the header
the main body composed of eight main paragraphs explaining the 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

411-9001-103 18.06 20 January 2010
1.4 Help
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
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.
1.4 Help
The system provides the user with help at any time. For an in-depth
discussion of Help, refer to Nortel GSM OMC-R Commands Reference Security, Administration, SMS-CB, and Help menus (411-9001-130).
There are two kinds of help available:
on-line help, available from the Help menu in the OMC-R Browser
window, as well as other windows
the Consult BSS Documentation option of the workstation workspace

pop-up menu provides access to on-line BSS documentation stored
on CD-ROM.
Both are provided on the same CD-ROM.
1.4.1 Loading the CD-ROM

To load the CD-ROM from the screen workspace menu, insert the
CD-ROM in the OMC-R server and/or workstation CD-ROM drive.
Installation is complete when the light on the CD-ROM drive is no longer
lit.
411-9001-103 18.06 20 January 2010
27
28 Chapter 1 How to use this manual

411-9001-103 18.06 20 January 2010
29
Chapter 2 S8000, S8002, S8003, and

S8006 BTS fault numbers
Throughout this document (or section, as it applies), the terms DRX,
e-DRX, DRX-ND3 and eDRX2 are used indistinctly as DRX unless the
document makes a specific reference.
Alarm notifications and contents include specific information about the
particular type of equipment involved on the alarm. For example, alarms
related to DRX-ND3 will include this specific equipment type throughout
the notification.
V15.0 introduced EDGE and other important features, together with
DRX-ND3 full differentiation. DRX-ND3 is not EDGE compatible. For all
EDGE related alarms, the term DRX does not include DRX-ND3. This
equipment type solves obsolescence problems with DRX.
2.1 Fault number: 1051 (S8000, S8002, S8003, and S8006 BTS)
Fault number:
1051
: Loss of layer 3 with remote GSM entity
Type
: communicationsAlarm
This problem is associated with a PCM fault. See 411-9001-105 (Nortel

GSM BSS Fault Clearing - Advanced Maintenance Procedures)
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.

411-9001-103 18.06 20 January 2010
30 Chapter 2 S8000, S8002, S8003, and S8006 BTS fault numbers
All the software downloading attempts are indicated, as well as the source
of their failure.
The following Table 1 "Fault number 1052 sources" (page 30) indicates
all the sources of the fault number 1052 for the S8000 Outdoor and
Indoor BTSs with the BCF or CBCF, the S8002 BTSs, the S8003 indoor
BTSs, and the S8006 BTSs. For more information on each source, refer
to the indicated paragraph to know the corrective maintenance procedure
associated with this source.
Table 1
Fault number 1052 sources
Source No.
Paragraph
Source wording
No response to status request
2.2.1 Source 0: No
response to status
request (page 41)
Bad hardware reference of manufacturer ID
2.2.2 Source 1: Bad

hardware reference
of manufacturer ID
(page 43)
SUP stop receipt
No change to one of BOOT states after reset
2.2.4 Source 3: No
change to one of BOOT
states after reset (page
48)
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 52)
Software not compatible with hardware
2.2.6 Source 5: Software

not compatible with
hardware (page 54)
File access error
2.2.7 Source 6: File

access error (page 58)
Repetitive errors (NACK, timeout, ... ) while

downloading a file
2.2.8 Source 7:
Repetitive errors (NACK,
timeout, ...) while
downloading a file
(page 61)
2.2.3 Source 2: SUP stop

receipt (page 46)

411-9001-103 18.06 20 January 2010
Table 1
Fault number 1052 sources (contd.)
Source No.
Paragraph
Source wording
Wrong software reference on a non downloadable TEI
No response to download message
2.2.9 Source 9: No
response to download
message (page 61)
14
CSM load container negative acknowledgement
2.2.10 Source 14:

Received CSM LOAD
CONTAINER NAK
(page 64)
15
File to download empty
2.2.11 Source 15: File

to download empty
(page 66)
16
File to download unavailable
2.2.12 Source 16: File to

download unavailable
(page 68)
17
Buffer allocation failure
2.2.13 Source 17: Buffer

allocation failure (page
69)
18
Bad sending buffer size value
2.2.14 Source 18: Bad

sending buffer size value
(page 72)
19
Failure during OMU switchover
2.2.15 Source 19: Failure

during OMU switchover
(page 74)
20
Bad TEI sent by BTS in the CSM software update

report message

TEI sent by BTS in the
CSM software update
report message (page 76)
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 78)
22
CSM software update report with the cause "equipment

failure"
2.2.5 Source
4: This entity is
engaged in another
downloadingSource 8:
on a non downloadable
TEI (page 52)
2.2.18 Source 22:

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

411-9001-103 18.06 20 January 2010
Table 1
Source No.
Paragraph
Source wording
23
CSM software update report with the cause

"downloading failure"
24
CSM software update report with the cause "not able

to perform"

with the cause - not able
to perform- (page 85)
25
CSM software update report with the cause "wrong soft

ref"

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

config ref"

configuration reference
- (page 90)
27
CSM software update report with the cause "restart

request"

with the cause - restart
request - (page 92)
28
CSM software update report with the cause "data

inconsistency"

with the cause - data
inconsistency - (page 94)
29
CSM software update report with the cause "message

out of sequence"
2.2.25 Source 29:

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

"background not available"
2.2.26 Source 30:

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

"incompatible RM version"
2.2.27 Source 31:

CSM software update
report with the cause incompatible RM version
- (page 101)
2.2.19 Source 23:

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

411-9001-103 18.06 20 January 2010
Table 1
Source No.
Paragraph
Source wording
32

"downloading in progress"
2.2.28 Source 32:

CSM software update
report with the cause downloading in progress
- (page 104)
33
Bad report sent by BTS in the CSM software update

report message

report sent by BTS
in the CSM software
update report message
(page 106)
34
no BTS response on CSM software update init/control

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

received on the abort
requested by operator
(page 111)
36
bad report sent by BTS in the CSM software update

abort message

report sent by BTS
in the CSM software
update abort message
(page 113)
37
no BTS response on CSM software update abort

message
2.2.33 Source 37: No

BTS response on CSM
software update abort
message (page 115)
38
flash activate nack with the cause "unknown TEI"
2.2.34 Source 38: Flash

activate nack with the
cause - unknown TEI
- (page 118)
39
flash activate nack with the cause "equipment failure"

cause - equipment failure
- (page 120)
40
flash activate nack with the cause "downloading failure"

cause - downloading
failure - (page 122)
2.2.30 Source 34:

No BTS response on
CSM software update
init-control message
(page 108)

411-9001-103 18.06 20 January 2010
Table 1
Source No.
Source wording
Paragraph
41
flash activate nack with the cause "not able to perform"

cause - not able to
perform - (page 124)
42
flash activate nack with the cause "flash inconsistency"
2.2.38 Source 42:

Flash activate nack
with the cause - flash
inconsistency - (page
127)
43
flash activate nack with the cause "data inconsistency"

cause - data inconsistency
- (page 129)
44
flash activate nack with the cause "wrong soft ref"

cause - wrong soft ref
- (page 131)
45
flash activate nack with the cause "wrong config ref"

cause - wrong config ref
- (page 133)
46
CSM downloading start nack with the cause "unknown

TEI"

downloading start nack
TEI - (page 136)
47
CSM downloading start nack with the cause "equipment

failure"
2.2.43 Source 47:

CSM downloading start
nack with the cause
(page 138)
48
CSM downloading start nack with the cause

2.2.44 Source 48:

nack with the cause downloading failure -
(page 140)
49
CSM downloading start nack with the cause "message

out of sequence"
2.2.45 Source 49:

nack with the cause message out of sequence
- (page 142)

411-9001-103 18.06 20 January 2010
Table 1
Source No.
Source wording
Paragraph
50
CSM downloading start nack with the cause "wrong soft

ref"

soft ref - (page 145)
51
CSM downloading start nack with the cause "wrong

config ref"

config ref - (page 147)
52
CSM downloading start nack with a bad cause
2.2.48 Source 52:

nack with a bad cause
(page 149)
53
no BTS response on CSM downloading start message
2.2.49 Source 53:

No BTS response on
message (page 152)
54
CSM downloading end nack with the cause "unknown

TEI"

downloading end nack
TEI - (page 154)
55
CSM downloading end nack with the cause "equipment

failure"
2.2.51 Source 55:

CSM downloading end
nack with the cause
(page 156)
56
CSM downloading end nack with the cause

2.2.52 Source 56:

CSM downloading end
nack with the cause downloading failure -
(page 158)
57
CSM downloading end nack with the cause "value out

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

CSM downloading end
nack with a bad cause
(page 163)
59
no BTS response on CSM downloading end message
2.2.55 Source 59:

No BTS response on
CSM downloading end
message (page 165)

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

411-9001-103 18.06 20 January 2010
Table 1
Source No.
Paragraph
Source wording
60
CSM load init nack with the cause "equipment failure"

load init nack with the
- (page 168)
61
CSM load init nack with the cause "downloading failure"

cause - downloading
62
CSM load init nack with the cause "message out of

sequence"

cause - message out of
sequence - (page 172)
63
CSM load init nack with the cause "wrong file ref"

cause - wrong file ref -
(page 174)
64
CSM load init nack with the cause "window size not
allow"

cause - window size not
allowed - (page 177)
65
CSM load init nack with the cause "data format error"

cause - data format error
- (page 179)
66
CSM load init nack with a bad cause

load init nack with a bad
cause (page 181)
67
no BTS response on CSM load init message
68
CSM load data nack with the cause "equipment failure"

load data nack with the
- (page 186)
69
CSM load data nack with the cause "downloading

failure"

cause - downloading

BTS response on CSM
load init message
(page 183)

411-9001-103 18.06 20 January 2010
Table 1
Source No.
Paragraph
Source wording
70
CSM load data nack with the cause "message out of

sequence"

71
CSM load data nack with the cause "data format error"

- (page 192)
72
CSM load data nack with the cause "window overflow"

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

inconsistency"

- (page 197)
74
CSM load data nack with the cause "block not

received"

cause - block not received
- (page 199)
75
CSM load data nack with the cause "bad block tag"

cause - bad block tag
- (page 201)
76
CSM load data nack with the cause "checksum error"

cause - checksum error
- (page 204)
77
CSM load data nack with a bad cause

load data nack with a bad
cause (page 206)
78
unexpected CSM load data ack
2.2.74 Source 78:

Unexpected CSM load
data ack (page 208)
79
no BTS response on CSM load data message

BTS response on CSM
load data message
(page 210)
80
CSM load end nack with the cause "equipment failure"

load end nack with the
- (page 213)

411-9001-103 18.06 20 January 2010
Table 1
Source No.
Paragraph
Source wording
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"

- (page 222)
85
CSM load end nack with the cause "wrong file ref"

cause - wrong file ref -
(page 224)
86
CSM load end nack with the cause "data inconsistency"
87
CSM load end nack with the cause "checksum error"

cause - checksum error
- (page 229)
88
CSM load end nack with a bad cause

load end nack with a bad
cause (page 231)
89
no BTS response on CSM load end message
90
bad report sent by BTS during an internal update

cause - downloading
cause - value out of range
- (page 217)

- (page 226)

BTS response on CSM
load end message
(page 233)
report sent by BTS
during an internal update
(page 235)

411-9001-103 18.06 20 January 2010
Table 1
Source No.
Paragraph
Source wording
91
CSM load init nack with the cause "file already open"

cause - file already open
- (page 238)
92
CSM load init nack with the cause "invalid mode"

cause - invalid mode -
(page 240)
93
CSM load init nack with the cause "file cannot be

unloaded"

cause - file cannot be
unloaded - (page 242)
94
CSM load init nack with the cause "flash flag cannot
access"

cause - flash flag cannot
access - (page 244)
95
CSM load data nack with the cause "file cannot be

unloaded"

cause - file cannot be
96
CSM load data nack with the cause "flash flag cannot
access"

cause - flash flag cannot
access - (page 249)
97
CSM load data nack with the cause "boot cannot be

unloaded"

cause - boot cannot be
98
CSM load data nack with the cause "data decode error"
99
CSM load data nack with the cause "table cannot

access"

cause - table cannot
access - (page 256)
100
CSM load data nack with the cause "ram mapping

error"

cause - RAM mapping
error - (page 258)

cause - data decode error
- (page 254)

411-9001-103 18.06 20 January 2010
Table 1
Source No.
Source wording
Paragraph
101
CSM load data nack with the cause "flash access error"

cause - flash access error
- (page 260)
102
CSM load data nack with the cause "flash ram error"

cause - flash RAM error
- (page 263)
103
CSM load data nack with the cause "flash erase error"

cause - flash erase error
- (page 265)
104
CSM load data nack with the cause "internal abort"
2.2.100 Source 104:

CSM load data nack with
the cause - internal abort
- (page 267)
105
CSM flash activate response with a bad cause
106
DTM error during token allocation
107
CSM software update report with the cause: TRX

software incompatibility
108
Too many different deliveries in the cell group
2.2.101 Source 105:

CSM flash activate
response with a bad
cause (page 269)
2.2.102 Source 106:
DTM error during token
allocation (page 272)
2.2.103 Source
107: CSM software
update report with the
cause: TRX software
incompatibility (page 274)
2.2.104 Source 108:
Too many different
deliveries in the cell
group (page 276)
REACTION OF THE SYSTEM

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

411-9001-103 18.06 20 January 2010
The site is not downloaded.
CAUTION
Service interruption
For the transceiverEquipment object

The TRX is not downloaded. One TDMA is not configured.
CAUTION
Service reduction
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:
S8000 Outdoor + S8000 Indoor + S8002 + S8003 + S8006
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.
Go to step 4.

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

411-9001-103 18.06 20 January 2010
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.
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.
Go to step 4.

"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

411-9001-103 18.06 20 January 2010

Procedures) ).
concerned. Look for alarms concerning the BSC.

"disabled-failed", the TRX is not operational.
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.
The procedure is complete.

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

Source:
(1) Bad hardware reference of manufacturer ID
BTS model:
S8000 Outdoor + S8000 Indoor + S8002 + S8003

+ S8006
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.

411-9001-103 18.06 20 January 2010
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

If a pcmCircuit object is "disabled-failed", look for a
fault number concerning PCMs. See Nortel GSM BSS
Fault Clearing - Advanced Maintenance Procedures
(411-9001-105).

alarm.

above).

1054 (loss of layer 2). See Nortel GSM BSS Fault
Clearing - Advanced Maintenance Procedures
(411-9001-105).


411-9001-103 18.06 20 January 2010


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).

Set the value of the "hardwareRef" parameter to "0".

411-9001-103 18.06 20 January 2010

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

--End--
2.2.3 Source 2: SUP stop receipt

Source:
(2) SUP stop receipt
BTS model:
FAULT ANALYSIS
This source indicates that a supervision stop has been received.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-103 18.06 20 January 2010

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-103 18.06 20 January 2010


above).

Procedures)).


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

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

+ S8006
2.2.4.1 FAULT ANALYSIS

This source indicates that no change occurred to one of the Boot states,
after reset.
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-103 18.06 20 January 2010

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

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

"disabled-failed", and if there are other alarms which could
impact the operation of the site, lock the btsSiteManager
object and then unlock it. If the alarm with the fault number
1052 and the source 3 is still present, process the alarm. Go
to step 4.
If other fault numbers are present, 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.

411-9001-103 18.06 20 January 2010

Procedures)).


above).

Procedures)).

is "disabled" the TRX is not operational. Do not process
On-site maintenance using the OMC-R
Set the operationalState of the entity concerned to "locked" then

"unlocked" to restart the downloading.
If the alarm persists, check if the source 1 appears.

If the source 1 appears, treat it. See Paragraph 2.2.2
Source 1: Bad hardware reference of manufacturer ID
(page 43).
If the source 1 does not appear, go to step 5 if the
btsSiteManager object is concerned, or step 6 if the
transceiverEquipment object is concerned.
If the alarm has disappeared, the downloading has restarted.

Go to step 8.
Reset the following items of equipment:
for the S8000 BTS, the active CSWM board of the BCF or the
active CMCF board of the CBCF
for the S8002 BTS and the S8006 BTS, the active CMCF
board
If the alarm persists, go to step 7. Otherwise, go to step 8.
Reset the DRXs.

411-9001-103 18.06 20 January 2010
If the alarm persists, go to step 7. Otherwise, go to step 8.

7
Replace successively the following items of equipment until the

alarm disappears:
for the S8000 BTS:

the active CSWM board (Field Replaceable Unit) of
the BCF: refer to 411-9001-048 (Nortel GSM BTS
S8000/S8003 Troubleshooting)
or the active CMCF board (Field Replaceable Unit) of
the CBCF: refer to 411-9001-048 (Nortel GSM BTS
then, if necessary, the DRXs (Field Replaceable Unit):
refer to 411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting)
for the S8002 BTS:

the active CMCF board (Field Replaceable Unit) of the
CBCF: refer to 411-9001-084 (Nortel GSM BTS S8002
Troubleshooting)
then, if necessary, the DRXs (Field Replaceable
Unit): refer to 411-9001-084 (Nortel GSM BTS S8002
Troubleshooting)
for the S8003 BTS:

the active CMCF board (Field Replaceable Unit) of
the CBCF: refer to 411-9001-048 (Nortel GSM BTS
S8000/S8003 Troubleshooting).
then, if necessary, the DRXs (Field Replaceable Unit):
Troubleshooting).
for the S8006 BTS:

the active CMCF board (Field Replaceable Unit) of the
CBCF: refer to 411-9001-085 (Nortel GSM BTS S8006
Troubleshooting)
then, if necessary, the DRXs (Field Replaceable
Unit): refer to 411-9001-085 (Nortel GSM BTS S8006
Troubleshooting)
If the alarm has disappeared, go to step 8. Otherwise, call the

manufacturer.
8

--End--

411-9001-103 18.06 20 January 2010
2.2.5 Source 4: This entity is engaged in another downloading

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

downloadable TEI
BTS model:

+ S8006

This source indicates that this entity is engaged in another downloading.
TROUBLESHOOTING
Step
Action
Preliminary checks

Check the state of the site by performing a "Display all"


step 4.

Procedures) ).

object, and then unlock it.
If the alarm with the fault number 1052 and the source 4
or 8 is still present, process the alarm. Go to step 4.
Otherwise, if there are other alarms, such as fault number
1054, process them (concerning fault number 1054 (loss

411-9001-103 18.06 20 January 2010
of layer 2), see 411-9001-105 (Nortel GSM BSS Fault

Clearing - Advanced Maintenance Procedures)



Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures) ).


411-9001-103 18.06 20 January 2010
Restart the active board of the BCF.
If the alarm has disappeared, go to step 5.

If the alarm persists:
For the BSC 3000, call the manufacturer.

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

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

+ S8006

This source indicates that the software is not compatible with the
hardware.
TROUBLESHOOTING
Step
Action
Preliminary checks

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.


411-9001-103 18.06 20 January 2010

step 8.

Procedures)).

"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, and then unlock
it. If the alarm with the fault number 1052 and the source 5 is
still present, process the alarm. Go to step 4.
Otherwise, refer to the fault number 1054 (loss of layer
2) (see 411-9001-105 (Nortel GSM BSS Fault Clearing Advanced Maintenance Procedures)).



Clear the alarm.

concerning cells.

411-9001-103 18.06 20 January 2010

Procedures) ).


above).

Procedures)).

the alarm and do not clear it. Wait for a state change of
the transceiverEquipment object.
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.
Ensure the EFT is correct by checking the value of the

"swVersionRunning" parameter by performing the "Display"
command on the software object associated with the bsc object.
If this is the case, set the object concerned to "locked" then

"unlocked".
If the alarm persists, call the manufacturer.
If this is not the case, go to step 6.

411-9001-103 18.06 20 January 2010
Set the object concerned to "locked".
Download the correct EFT on the item of equipment according

to the following values.
Field
Meaning
Value
XXX
Type of software
BCF : CBC
TRX : DRX/CDR/EDG
ab
Version number
[00 .. 32]
Sub-version number
CBC : [A ..
DRX : [A ..
CDR : [A ..
EDG : [A ..
H]
H]
H]
H]
Edition number
CBC : [1 ..
DRX : [1 ..
CDR : [1 ..
EDG : [1 ..
8]
8]
8]
8]
ef
Revision factor
CBC : [0 ..
DRX : [0 ..
CDR : [0 ..
EDG : [0 ..
32]
32]
32]
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
411-9001-032 (Nortel GSM OMC-R Routine Maintenance
and Troubleshooting)).
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.

411-9001-103 18.06 20 January 2010
If it finds one and only one, it selects it. Then it goes to step
10.
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 411-9001-032 (Nortel GSM OMC-R Routine
Maintenance and Troubleshooting)).
10
The OMC-R starts to download the selected EFT:

a If necessary, it downloads the selected EFT to the BSC disc.
b It locks the related transceiverEquipment object instance
c It sets the sWVersionNew parameter of the 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--
2.2.7 Source 6: File access error

Source:
(6) File access error
BTS model:

+ S8006
FAULT ANALYSIS
This source indicates that the first downloading attempt has failed. The
BSC does not find the software files in one partition of its hard disk.
TROUBLESHOOTING
Step
Action
Preliminary checks

411-9001-103 18.06 20 January 2010



step 6.

Procedures)).

If the alarm with the fault number 1052 and the source 6
is still present, process the alarm. Go to step 4.
Otherwise, if there are other alarms, such as fault number
1054, process them (concerning fault number 1054 (loss
of layer 2), refer to 411-9001-105 (Nortel GSM BSS Fault
Clearing - Advanced Maintenance Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010

concerning cells.
Procedures) ).


above).

Procedures) ).

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

transceiverEquipment object).
Unlock the object concerned.

If the alarm persists:

411-9001-103 18.06 20 January 2010

--End--
2.2.8 Source 7: Repetitive errors (NACK, timeout, ...) while

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

downloading a file
BTS model:

+ S8006
FAULT ANALYSIS
This source indicates that the downloading failed after repetitive
downloading errors. The probable cause could be corresponding software
corrupted in BTS active BSC corruption.
TROUBLESHOOTING
Step
Action
Preliminary checks
Lock the btsSiteManager
Cleanup the corresponding BTS software from BSC.
Activate the software.
Download the software from the MD at the OMC-R to the

BSC disk partition.
Unlock the btsSiteManager.

--End--
2.2.9 Source 9: No response to download message

Source:
(9) No response to download message
BTS model:
FAULT ANALYSIS
This source indicates that the BTS has not replied to a download
message.

411-9001-103 18.06 20 January 2010
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
2.2.10 Source 14: Received CSM LOAD CONTAINER NAK

Source:
(14) Received CSM LOAD CONTAINER NAK
BTS model:

+ S8006
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.

Procedures) ).

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


above).

Procedures)).


411-9001-103 18.06 20 January 2010
Re-download the software from the MD at the OMC--R to the

BSC disk partition:

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

procedure.



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

Source:
(15) File to download empty
BTS model:
FAULT ANALYSIS
This source indicates that the file to download is empty.
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
Clear the alarm.


Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
2.2.12 Source 16: File to download unavailable

Source:
(16) File to download unavailable
BTS model:

+ S8006

411-9001-103 18.06 20 January 2010
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.
Download the software from the MD at the OMC-R to the BSC
disk partition:

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

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


If the alarm persists, go to step 2.
Perform one of the following:

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

Source:
(17) Buffer allocation failure
BTS model:
FAULT ANALYSIS
This source indicates a buffer allocation failure.

411-9001-103 18.06 20 January 2010
2.2.13.1 TROUBLESHOOTING
Procedure 1
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
2.2.14 Source 18: Bad sending buffer size value

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



Clear the alarm.

Procedures) ).

alarm.

411-9001-103 18.06 20 January 2010

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-103 18.06 20 January 2010

Procedures)).


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

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



Clear the alarm.


411-9001-103 18.06 20 January 2010

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010


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:
FAULT ANALYSIS
This source indicates a bad TEI sent by the BTS in the CSM software
update report message.
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010


Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010

concerning cells.
Procedures) ).


above).

Procedures)).


--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:
FAULT ANALYSIS
This source indicates a CSM software update report with the cause
"unknown TEI".
411-9001-103 18.06 20 January 2010
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
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:
FAULT ANALYSIS
"equipment failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-103 18.06 20 January 2010

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-103 18.06 20 January 2010

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:
FAULT ANALYSIS
"downloading failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010


above).

Procedures)).


--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:
FAULT ANALYSIS
This source indicates a CSM software update report with the cause "not
able to perform".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010


Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010

concerning cells.
Procedures) ).


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:

411-9001-103 18.06 20 January 2010
FAULT ANALYSIS
This source indicates a CSM software update report with the cause "wrong
software reference".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-103 18.06 20 January 2010

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

configuration reference"
BTS model:
FAULT ANALYSIS
This source indicates a CSM software update report with the cause "wrong
configuration reference".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-103 18.06 20 January 2010

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-103 18.06 20 January 2010


above).

Procedures)).


--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:
FAULT ANALYSIS
This source indicates a CSM software update report with the cause "restart
request".
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
Clear the alarm.


Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010

concerning cells.
Procedures) ).


above).

Procedures)).


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

inconsistency"
BTS model:

411-9001-103 18.06 20 January 2010
FAULT ANALYSIS
This source indicates a CSM software update report with the cause "data
inconsistency".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-103 18.06 20 January 2010

--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:
FAULT ANALYSIS
"message out of sequence".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-103 18.06 20 January 2010

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-103 18.06 20 January 2010


above).

Procedures)).


--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:
FAULT ANALYSIS
"background not available".
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-103 18.06 20 January 2010
100

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
101

concerning cells.
Procedures) ).


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:

411-9001-103 18.06 20 January 2010
102
FAULT ANALYSIS
"incompatible RM version".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
103
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-103 18.06 20 January 2010
104

--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:
FAULT ANALYSIS
"downloading in progress".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-103 18.06 20 January 2010
105

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-103 18.06 20 January 2010
106


above).

Procedures)).


--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:
FAULT ANALYSIS
This source indicates a bad report sent by the BTS in the CSM software
update report message.
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-103 18.06 20 January 2010
107

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
108

concerning cells.
Procedures) ).


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:

411-9001-103 18.06 20 January 2010
109
FAULT ANALYSIS
This source indicates no BTS response on the CSM software update
init/control message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
110
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-103 18.06 20 January 2010
111

--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:
FAULT ANALYSIS
This source indicates that a Nack has been received on the abort
requested by operator.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-103 18.06 20 January 2010
112

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-103 18.06 20 January 2010
113


above).

Procedures)).


--End--
2.2.32 Source 36: Bad report sent by BTS in the CSM software update
abort message
Source:
(36) Bad report sent by BTS in the CSM software update abort
message
BTS model:
FAULT ANALYSIS
This source indicates a bad report sent by the BTS in the CSM software
update abort message.
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-103 18.06 20 January 2010
114

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
115

concerning cells.
Procedures) ).


above).

Procedures)).


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

message
Source:
(37) No BTS response on CSM software update abort message
BTS model:
FAULT ANALYSIS
This source indicates no BTS response on CSM software update abort
message.
411-9001-103 18.06 20 January 2010
116
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
117


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
118
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:
FAULT ANALYSIS
This source indicates a flash activate nack with the cause unknown TEI.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-103 18.06 20 January 2010
119

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-103 18.06 20 January 2010
120

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:
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "equipment
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
121

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
122


above).

Procedures)).


--End--
2.2.36 Source 40: Flash activate nack with the cause - downloading
Source:
(40) Flash activate nack with the cause "downloading failure"
BTS model:
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "downloading
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010
123

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
124

concerning cells.
Procedures) ).


above).

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:
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "not able to
perform".
411-9001-103 18.06 20 January 2010
125
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
126


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
127
2.2.38 Source 42: Flash activate nack with the cause - flash
Source:
(42) Flash activate nack with the cause "flash inconsistency"
BTS model:
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "flash
inconsistency".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-103 18.06 20 January 2010
128

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-103 18.06 20 January 2010
129

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:
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "data
inconsistency".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
130

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
131


above).

Procedures)).


--End--
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:
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "wrong soft ref".
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-103 18.06 20 January 2010
132

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
133

concerning cells.
Procedures) ).


above).

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:
FAULT ANALYSIS
This source indicates a flash activate nack with the cause "wrong config
ref".
411-9001-103 18.06 20 January 2010
134
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
135


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
136
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:
FAULT ANALYSIS
This source indicates a CSM downloading start nack with the cause
"unknown TEI".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-103 18.06 20 January 2010
137

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-103 18.06 20 January 2010
138

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:
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
139

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
140


above).

Procedures)).


--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:
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010
141


Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
142

concerning cells.
Procedures) ).


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:

411-9001-103 18.06 20 January 2010
143
FAULT ANALYSIS
"message out of sequence".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
144
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-103 18.06 20 January 2010
145

--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:
FAULT ANALYSIS
"wrong soft ref".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-103 18.06 20 January 2010
146

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-103 18.06 20 January 2010
147


above).

Procedures)).


--End--
2.2.47 Source 51: CSM downloading start nack with the cause - wrong
config ref Fault number 1052 : GSM entity downloading failure
Source:
(51) CSM downloading start nack with the cause "wrong config
ref"
BTS model:
FAULT ANALYSIS
"wrong config ref".
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-103 18.06 20 January 2010
148

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
149

concerning cells.
Procedures) ).


above).

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:
FAULT ANALYSIS
This source indicates a CSM downloading start nack with a bad cause.

411-9001-103 18.06 20 January 2010
150
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
151


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
152
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:
FAULT ANALYSIS
This source indicates no BTS response on CSM downloading start
message.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-103 18.06 20 January 2010
153

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-103 18.06 20 January 2010
154

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:
FAULT ANALYSIS
This source indicates a CSM downloading end nack with the cause
"unknown TEI".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
155

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
156


above).

Procedures)).


--End--
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:
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010
157


Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
158

concerning cells.
Procedures) ).


above).

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:

411-9001-103 18.06 20 January 2010
159
FAULT ANALYSIS
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
160
3


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


411-9001-103 18.06 20 January 2010
161

--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:
FAULT ANALYSIS
This source indicates a CSM downloading end nack with the cause "value
out of range".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-103 18.06 20 January 2010
162

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


411-9001-103 18.06 20 January 2010
163


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:
FAULT ANALYSIS
This source indicates a CSM downloading end nack with a bad cause.
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
164
Clear the alarm.


Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
165

concerning cells.
Procedures) ).


above).

Procedures)).


--End--
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:
FAULT ANALYSIS
This source indicates no BTS response on CSM downloading end
message.

411-9001-103 18.06 20 January 2010
166
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
167


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
168
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:
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "equipment
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-103 18.06 20 January 2010
169

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-103 18.06 20 January 2010
170

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:
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "downloading
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
171

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
172


above).

Procedures)).


--End--
2.2.58 Source 62: CSM load init nack with the cause - message out of
sequence Fault number 1052 : GSM entity downloading failure
Source:
(62) CSM load init nack with the cause "message out of
sequence"
BTS model:
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "message out of
sequence".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010
173


Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
174

concerning cells.
Procedures) ).


above).

Procedures)).


--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:
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "wrong file ref".

411-9001-103 18.06 20 January 2010
175
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
176


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
177
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:
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "window size
not allowed".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-103 18.06 20 January 2010
178

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-103 18.06 20 January 2010
179

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:
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "data format
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
180

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
181


above).

Procedures)).


--End--
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:
FAULT ANALYSIS
This source indicates a CSM load init nack with a bad cause.
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-103 18.06 20 January 2010
182

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
183

concerning cells.
Procedures) ).


above).

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:
FAULT ANALYSIS
This source indicates a No BTS response on CSM load init message.

411-9001-103 18.06 20 January 2010
184
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
185


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
186
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:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "equipment
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-103 18.06 20 January 2010
187

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-103 18.06 20 January 2010
188

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:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "downloading
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
189

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
190


above).

Procedures)).


--End--
2.2.66 Source 70: CSM load data nack with the cause - message out of
Source:
(70) CSM load data nack with the cause "message out of
sequence"
BTS model:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "message out
of sequence".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010
191


Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
192

concerning cells.
Procedures) ).


above).

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:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "data format
error".
411-9001-103 18.06 20 January 2010
193
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
194


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
195
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:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "window
overflow".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-103 18.06 20 January 2010
196

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-103 18.06 20 January 2010
197

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:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "data
inconsistency".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
198

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
199


above).

Procedures)).


--End--
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:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "block not
received".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010
200

Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
201

concerning cells.
Procedures) ).


above).

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:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "bad block
tag".

411-9001-103 18.06 20 January 2010
202
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

above).

Procedures) ).


411-9001-103 18.06 20 January 2010
203


Clear the alarm.

concerning cells.
Procedures) ).


above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
204
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:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "checksum
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).

alarm.

411-9001-103 18.06 20 January 2010
205

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).


above).


411-9001-103 18.06 20 January 2010
206

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:
FAULT ANALYSIS
This source indicates a CSM software update report with the cause CSM
load data nack with a bad cause.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
207

Procedures) ).

alarm.

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
208


above).

Procedures)).


--End--
2.2.74 Source 78: Unexpected CSM load data ack

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



411-9001-103 18.06 20 January 2010
209

Clear the alarm.

Procedures) ).

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

above).

number 1054, treat them (concerning fault number
Procedures) ).

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


Clear the alarm.


411-9001-103 18.06 20 January 2010
210

concerning cells.
is not operational. Treat the alarm(s) concerning the
Procedures) ).

Go to step 4.

above).

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:
FAULT ANALYSIS
This source indicates no BTS response on CSM load data message.

411-9001-103 18.06 20 January 2010
211
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-103 18.06 20 January 2010
212

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
213
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:
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "equipment
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-103 18.06 20 January 2010
214

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-103 18.06 20 January 2010
215

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:
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "downloading
failure".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
216

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
217

Go to step 4.

above).

Procedures)).


--End--
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:
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "value out of
range".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010
218

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
219

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
2.2.79 Source 83: CSM load end nack with the cause - message out of
Source:
(83) CSM load end nack with the cause "message out of
sequence"
BTS model:

411-9001-103 18.06 20 January 2010
220
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.

Procedures) ).


above).

Procedures) ).


411-9001-103 18.06 20 January 2010
221
3


Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


411-9001-103 18.06 20 January 2010
222

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



Clear the alarm.

Procedures) ).


411-9001-103 18.06 20 January 2010
223

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

411-9001-103 18.06 20 January 2010
224

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:
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "wrong file ref".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
225

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.

411-9001-103 18.06 20 January 2010
226

Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
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:
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "data
inconsistency".
TROUBLESHOOTING
Step
Action
Preliminary checks

411-9001-103 18.06 20 January 2010
227



Clear the alarm.

Procedures) ).


above).

Procedures) ).




411-9001-103 18.06 20 January 2010
228
Clear the alarm.


concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
229
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:
FAULT ANALYSIS
This source indicates a CSM load end nack with the cause "checksum
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-103 18.06 20 January 2010
230

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-103 18.06 20 January 2010
231

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:
FAULT ANALYSIS
This source indicates a CSM load end nack with a bad cause.
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
232

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
233

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:
FAULT ANALYSIS
This source indicates no BTS response on CSM load end message.
TROUBLESHOOTING
Step
Action
Preliminary checks



411-9001-103 18.06 20 January 2010
234

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
235

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
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:
FAULT ANALYSIS
This source indicates a bad report sent by BTS during an internal update.

411-9001-103 18.06 20 January 2010
236
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-103 18.06 20 January 2010
237

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
238
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:
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "file already
open".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-103 18.06 20 January 2010
239

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-103 18.06 20 January 2010
240

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:
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "invalid mode".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
241

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
242

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:
FAULT ANALYSIS
This source indicates a CSM load init nack with the cause "file cannot be
unloaded".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010
243

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
244

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


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

411-9001-103 18.06 20 January 2010
245
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) ).


above).

Procedures) ).


411-9001-103 18.06 20 January 2010
246
3


Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


411-9001-103 18.06 20 January 2010
247

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

Procedures) ).


411-9001-103 18.06 20 January 2010
248

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

411-9001-103 18.06 20 January 2010
249

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:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "flash flag
cannot access".
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
250
Clear the alarm.


Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.

411-9001-103 18.06 20 January 2010
251

Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
2.2.93 Source 97: CSM load data nack with the cause - boot cannot be
Source:
(97) CSM load data nack with the cause "boot cannot be
unloaded"
BTS model:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "boot cannot
be unloaded".

411-9001-103 18.06 20 January 2010
252
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-103 18.06 20 January 2010
253

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
254
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:
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-103 18.06 20 January 2010
255

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-103 18.06 20 January 2010
256

Procedures)).


--End--
2.2.95 Source 99: CSM load data nack with the cause - table cannot
access Fault number 1052 : GSM entity downloading failure
Source:
(99) CSM load data nack with the cause "table cannot access"
BTS model:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "table cannot
access".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
257

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
258

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:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "RAM mapping
error".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010
259

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
260

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
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:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "flash access
error".
411-9001-103 18.06 20 January 2010
261
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-103 18.06 20 January 2010
262

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
263
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:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "flash RAM
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


411-9001-103 18.06 20 January 2010
264

above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-103 18.06 20 January 2010
265

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 "flash erase error"
BTS model:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "flash erase
error".
TROUBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
266

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
267

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:
FAULT ANALYSIS
This source indicates a CSM load data nack with the cause "internal
abort".
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010
268

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
269

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--
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:
FAULT ANALYSIS
This source indicates a CSM flash activate response with a bad cause.

411-9001-103 18.06 20 January 2010
270
TROBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.

Procedures) ).


above).

Procedures) ).


411-9001-103 18.06 20 January 2010
271

Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


--End--

411-9001-103 18.06 20 January 2010
272
2.2.102 Source 106: DTM error during token allocation

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



Clear the alarm.

Procedures) ).


above).


411-9001-103 18.06 20 January 2010
273

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

Go to step 4.

above).


411-9001-103 18.06 20 January 2010
274

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:
FAULT ANALYSIS
This source indicates a CSM software update report with the cause: TRX
software incompatibility.
TROBLESHOOTING
Step
Action
Preliminary checks



Clear the alarm.


411-9001-103 18.06 20 January 2010
275

Procedures) ).


above).

Procedures) ).



Clear the alarm.

concerning cells.
Procedures) ).

411-9001-103 18.06 20 January 2010
276

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:
FAULT ANALYSIS
This source indicates too many different deliveries in the cell group.
TROBLESHOOTING
Step
Action
Preliminary checks



411-9001-103 18.06 20 January 2010
277

Clear the alarm.

Procedures) ).


above).

Procedures) ).



Clear the alarm.


411-9001-103 18.06 20 January 2010
278

concerning cells.
Procedures) ).

Go to step 4.

above).

Procedures)).


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

411-9001-103 18.06 20 January 2010
279

BSC defense
The BSC tries to restart the BTS (either the btsSiteManager object or the
transceiverEquipment object), to download it, and to reconfigure it.
CAUTION
For as long as the operationalState of the btsSiteManager
object is "disabled-failed", the site is lost. No service is
provided.
CAUTION
Service reduction
For as long as the operationalState of the transceiverEquip
ment object is "disabled", the TRX and one TDMA are lost.
The service is reduced.
TROUBLESHOOTING
Step
Action
Preliminary checks
Look for a fault number 1067 concerning an item of equipment of

the object mentioned in the alarm (fault number 1053).
If there is an alarm with the fault number 1067 concerning

the CSW1/CSW2 boards, process the alarm with the fault
number 1067 first.
If there is an alarm with the fault number 1067 concerning

the transceiverEquipment object (frame processor or RX
module), process the alarm with the fault number 1067 first.
If there are no alarms with the fault number 1067, go to step

2.


411-9001-103 18.06 20 January 2010
280

step 4.

Procedures) ).

"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 is a recurring
problem. If the problem persists, call the manufacturer.

--End--
Fault number:
1054
Loss of layer 2 (or no establishment) with remote GSM entity
Type
communicationsAlarm

Fault number:
1055
Abis negative acknowledgement indication
Type
communicationsAlarm
FAULT ANALYSIS

411-9001-103 18.06 20 January 2010
281
The BSC sends a spontaneous message 1055 when it receives a

non-acknowledgement message (NACK) from a BTS after a configuration
message.
The following indicates all the sources of the fault number 1055 for the
S8000 Outdoor and Indoor BTSs with the BCF or CBCF, the S8002
BTSs, the S8003 BTSs, and the S8006 BTSs. For more information on
each source, refer to the indicated paragraph to know the corrective
maintenance procedure associated with this source.
Table 2
Source
No.
Source wording
Paragraph
Equipment failure
2.5.1 Source 1: Equipment failure (page 284)
Equipment unable to perform such

test
2.5.2 Source 2: Equipment unable to perform

such test (page 285)
Equipment unable to perform such

configuration
2.5.3 Source 3: Equipment unable to perform

such configuration (page 286)
Unknown test
Cell parameters inconsistency
2.5.5 Source 5: Cell parameters inconsistency

(page 288)
Data inconsistency
2.5.6 Source 6: Data inconsistency (page 290)
Value out of range
2.5.7 Source 7: Value out of range (page 291)
TEI not present
Unknown Abis PCM_Time_Slot
2.5.9 Source 9: Unknown Abis PCM_Ti

me_Slot (page 293)
10
Unknown Abis PCM
2.5.10 Source 10: Unknown Abis PCM

(page 293)
11
12
Further files required
13
Failure during activation
14
Data format error
2.5.14 Source 14: Data format error

(page 295)
15
Window overflow
2.5.15 Source 15: Window overflow (page 295)
16
Normal completion
17
Transfer aborted
2.5.4 Source 4: Unknown test (page 288)
2.5.8 Source 8: TEI not present (page 292)
2.5.11 Source 11: Wrong software

reference (page 294)
2.5.12 Source 12: Further files required
(page 294)
2.5.13 Source 13: Failure during activation
(page 295)
2.5.16 Source 16: Normal completion

(page 295)
2.5.17 Source 17: Transfer aborted (page 295)

411-9001-103 18.06 20 January 2010
282
Table 2
Source
No.
Source wording
Paragraph
18
Checksum error
2.5.18 Source 18: Checksum error (page 296)
19
File incomplete
2.5.19 Source 19: File incomplete (page 296)
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 connection 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 301)
29
Bad related TEI
2.5.29 Source 29: Bad related TEI (page 301)
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
37
Buffer overflow
38
Block not received
2.5.20 Source 20: File already present

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

2.5.31 Source 31: Window size not
allowed (page 301)
2.5.32 Source 32: Flash boot required
(page 301)
2.5.33 Source 33: Wrong config reference
(page 302)
2.5.34 Source 34: The BTS has not
acknowledged the TX power consign
request (page 302)
2.5.35 Source 35: Downloading aborted
(page 307)
2.5.36 Source 36: Files missing (page 307)
2.5.37 Source 37: Buffer overflow (page 308)
2.5.38 Source 38: Block not received
(page 308)

411-9001-103 18.06 20 January 2010
283
Table 2
Source
No.
Source wording
Paragraph
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
2.5.46 Source 46: Bad internal Link EDGE

configuration (page 312)
47
Inconsistency mapping
2.5.47 Source 47: Inconsistency mapping

(page 312)
48
Inconsistency number of joker DS0
49
Invalid mode
50
File already open
51
File cannot be unloaded
2.5.51 Source 51: File cannot be unloaded

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

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

(page 314)
56
RAM mapping error
2.5.56 Source 56: RAM mapping error

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

(page 314)
58
Flash write error
2.5.39 Source 39: Downloading restart

(page 308)
2.5.40 Source 40: Request not supported
(page 308)
2.5.41 Source 41: Downloading failure
(page 308)
2.5.42 Source 42: Start-up failure (page 309)
2.5.43 Source 43: Maximum number of
joker TS (page 309)
2.5.44 Source 44: Bad chain type (page 312)
2.5.45 Source 45: Bad radio timeslot
reference (page 312)
2.5.48 Source 48: Inconsistency number

of joker DS0 (page 313)
2.5.49 Source 49: Invalid mode (page 313)
2.5.50 Source 50: File already open
(page 313)
2.5.53 Source 53: Data decode error

(page 314)
2.5.54 Source 54: Flash flag cannot
access (page 314)
2.5.58 Source 58: Flash write error (page 315)

411-9001-103 18.06 20 January 2010
284
Table 2
Source
No.
Paragraph
Source wording
59
Flash erase error
60
Internal abort
2.5.60 Source 60: Internal abort (page 315)
61
Equipment not able to get external

synchronization
2.5.61 Source 61: Equipment not able to get

external synchronization (page 315)
62
Synchronization in progress
63
Dynamic Abis feature not supported
2.5.63 Source 63: Dynamic Abis feature

not supported (page 316)
64
Inconsistent number of Joker DS0
2.5.64 Source 64: Inconsistent number

of joker DS0 (page 317)
65
Exceeded DL joker DS0 pool number
2.5.65 Source 65: Exceeded DL joker DS0

pool number (page 319)
255
Non-significant value
2.5.66 Source 255: Non-significant value

(page 321)
2.5.59 Source 59: Flash erase error

(page 315)
2.5.62 Source 62: Synchronization in

progress (page 315)
FAULT LOCATION
The fault can be located on one of the following:
the btsSiteManager
the bts
the transceiver
the transceiverEquipment
2.5.1 Source 1: Equipment failure

Fault number 1055 : Abis negative acknowledgement indication
Source:
(1) Equipment failure
BTS model:
FAULT ANALYSIS
This source indicates an equipment failure.

411-9001-103 18.06 20 January 2010
285
2.5.2 Source 2: Equipment unable to perform such test

Source:
(2) Equipment unable to perform such test
BTS model:

+ S8006
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.
CAUTION
The site is not configured.
No service is provided.
For the bts object
CAUTION
The cell is not configured.
No service is provided on the cell.
For the transceiver object
CAUTION
Service reduction
The TDMA is not configured.
CAUTION
Service reduction
The TRX is not configured and one TDMA is lost.

411-9001-103 18.06 20 January 2010
286
TROUBLESHOOTING
Modify the parameters declared at the OMC-R.
2.5.3 Source 3: Equipment unable to perform such configuration

Source:
(3) Equipment unable to perform such configuration
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates that the TRX configuration is not possible because of
a DRX frequency band error.
The different sources of non-acknowledgement are:
the DRX is configured in an extended cell and the hardware does not
support this configuration
the defined frequency range is not compatible with the radio board
version
the number of PCMs, or cells, or signaling TSs is too large according

to the hardware configuration
one or more frequencies mismatch the DRX frequency band
the number of requested pools is more than the maximum number of

supported pools
more than 16 EDGE TRX in a "dynamic Abis" site
the equipment is unable to perform such configuration. A wrong

external alarm mask can generate this notification

BSC defense The BSC unconfigures the transceiverEquipment object
concerned by the alarm.
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Perform a "Display" command on the bts object.

411-9001-103 18.06 20 January 2010
287
The "standardIndicator" parameter indicates the frequency band

associated with the DRX module: "gsm", " gsm850", "dcs1800",
"pcs1900", "R gsm", "gsmdcs" or "dcsgsm".
If the "standardIndicator" parameter is "gsm 850pcs", perform

a "Display" command on the transceiverEquipment object.
If the "transceiverEquipmentClass" parameter is "1", the
DRX is "gsm850".
DRX is PCS.
If the "standardIndicator" parameter is "pcsgsm850", perform

DRX is PCS.
DRX is "gsm850".
If the "standardIndicator" parameter is "gsmdcs", perform a

"Display" command on the transceiverEquipment object.
DRX is GSM.
DRX is DCS.
If the "standardIndicator" parameter is "dcsgsm", perform a

DRX is DCS.
DRX is GSM.
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 4. Otherwise,
go to step 3.
The alarm may be due to an error in the DRX replacement.

Replace the DRX (as a Field Replaceable Unit) by:
setting the administrativeState of the transceiverEquipment

object corresponding to the faulty DRX to "locked"

411-9001-103 18.06 20 January 2010
288
CAUTION
Service reduction
In most cases, the transceiverEquipment and one
transceiver are lost.
replacing the DRX module. Refer to:

411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting) for the S8000 BTS
411-9001-084 (Nortel GSM BTS S8002 Troubleshooting)
for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8006 BTS
Go to step 4.
4
Ensure that the DRX used is correct. Modify the value of the
"transceiverEquipmentClass" parameter according to the DRX
frequency band. Go to step 5.

--End--
2.5.4 Source 4: Unknown test

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

Source:
(5) Cell parameters inconsistency
BTS model:
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.

411-9001-103 18.06 20 January 2010
289

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.
Check that the alarm is cleared.

411-9001-103 18.06 20 January 2010
290

--End--
2.5.6 Source 6: Data inconsistency

Source:
(6) Data inconsistency
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates that the PCM list contains identical PCM numbers.

BSC defense
None.
CAUTION
For the bts object
CAUTION
Service reduction
CAUTION
Service reduction
CAUTION
Service reduction
The TRX is not configured. One TDMA is lost.

411-9001-103 18.06 20 January 2010
291
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 as necessary.
Check the configuration associated with the object at the

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

--End--
2.5.7 Source 7: Value out of range

Source:
(7) Value out of range
BTS model:

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

411-9001-103 18.06 20 January 2010
292
Any frequency in the list is in no known band

Number of TEI < 1

BSC defense
None.
For the bts object
CAUTION
Service reduction
TROUBLESHOOTING
Modify the values declared out of range at the OMC-R.
2.5.8 Source 8: TEI not present

Source:
(8) TEI not present
BTS model:

+ S8006
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.

411-9001-103 18.06 20 January 2010
293
CAUTION
Service reduction
CAUTION
Service reduction
2.5.9 Source 9: Unknown Abis PCM_Time_Slot

Source:
(9) Unknown Abis PCM_Time_Slot
BTS model:
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:

+ S8006
FAULT ANALYSIS
This alarm indicates that the PCM is not present in the PCM list.

BSC defense
None.
CAUTION
For the bts object

411-9001-103 18.06 20 January 2010
294
CAUTION
Service reduction
CAUTION
Service reduction
CAUTION
Service reduction
TROUBLESHOOTING
Parameterize the PCM declared unknown at the OMC-R.
2.5.11 Source 11: Wrong software reference

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

Source:
(12) Further files required
BTS model:
FAULT ANALYSIS
This source indicates that further files are required.

411-9001-103 18.06 20 January 2010
2.5.13 Source 13: Failure during activation

Source:
(13) Failure during activation
BTS model:
FAULT ANALYSIS
This source indicates a failure during activation.
2.5.14 Source 14: Data format error

Source:
(14) Data format error
BTS model:
FAULT ANALYSIS
This source indicates a data format error.
2.5.15 Source 15: Window overflow

Source:
(15) Window overflow
BTS model:
FAULT ANALYSIS
This source indicates a window overflow.
2.5.16 Source 16: Normal completion

Source:
(16) Normal completion
BTS model:
FAULT ANALYSIS
This source indicates a normal completion.
2.5.17 Source 17: Transfer aborted

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

411-9001-103 18.06 20 January 2010
295
296
2.5.18 Source 18: Checksum error

Source:
(18) Checksum error
BTS model:
FAULT ANALYSIS
This source indicates a checksum error.
2.5.19 Source 19: File incomplete

Source:
(19) File incomplete
BTS model:
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:
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:
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:
FAULT ANALYSIS
This source indicates that the entity is engaged in other download.

411-9001-103 18.06 20 January 2010
297
2.5.23 Source 23: Too many signaling timeslots

Source:
(23) Too many signaling timeslots
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates the value of the signaling timeslot number is higher
than 6.

BSC defense
None.
CAUTION
For the bts object
CAUTION
Service reduction
CAUTION
Service reduction
CAUTION
Service reduction
TROUBLESHOOTING
Modify the value of the signaling timeslot number.
411-9001-103 18.06 20 January 2010
298
2.5.24 Source 24: Too many TEI connections to physical channel

Source:
(24) Too many TEI connections to physical channel
BTS model:
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:

+ S8006
FAULT ANALYSIS
This alarm indicates that the site configuration message has been received
twice, but with different values by the BTS on the Abis interface. The
message is not accepted due to the BTS state.

BSC defense
None.
CAUTION
For the bts object
CAUTION
Service reduction

411-9001-103 18.06 20 January 2010
299
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 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.


configuration" command on the btsSiteManager to
b. For the base cabinet associated with the extension

cabinet, set the btsSiteManager object to "locked" then
to "unlocked".
c.
If the problem persists, perform the following on-site

maintenance.
For the S8000 BTS, check the cabling between the

extension cabinet and the BCF or CBCF.

411-9001-103 18.06 20 January 2010
300
If the problem persists, replace the ALCO or

RECAL board (Field Replaceable Units). Refer
to 411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting)

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

configuration" command on the btsSiteManager object to
2

--End--
2.5.26 Source 26: Incorrect IEI

Source:
(26) Incorrect IEI
BTS model:
FAULT ANALYSIS
This source indicates an incorrect IEI.
2.5.27 Source 27: Wrong file reference

Source:
(27) Wrong file reference
BTS model:

411-9001-103 18.06 20 January 2010
FAULT ANALYSIS
This source indicates a wrong file reference.
2.5.28 Source 28: Bad cell number

Source:
(28) Bad cell number
BTS model:
FAULT ANALYSIS
This source indicates a bad cell number.
2.5.29 Source 29: Bad related TEI

Source:
(29) Bad related TEI
BTS model:
FAULT ANALYSIS
This source indicates a bad related TEI.
2.5.30 Source 30: Bad timeslot

Source:
(30) Bad timeslot
BTS model:
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:
FAULT ANALYSIS
This source indicates that the window size is not allowed.
2.5.32 Source 32: Flash boot required

Source:
(32) Flash boot required
BTS model:

411-9001-103 18.06 20 January 2010
301
302
FAULT ANALYSIS
This source indicates that a flash boot is required.
2.5.33 Source 33: Wrong config reference

Source:
(33) Wrong config reference
BTS model:
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 power

consign request
BTS model:

+ S8006
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 The BSC configures the transceiverEquipment, but the
associated transceiver object is not configured.
At least one DRX is lost.
CAUTION
Service reduction
It is possible to lose the entire cell linked to the faulty DRX.
CAUTION
Intervention on the site must be immediate: there is a risk of
service loss.
TROUBLESHOOTING
Step
Action
Preliminary checks
411-9001-103 18.06 20 January 2010
303


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

"disabled-dependency", the site is not operational.
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
the alarm and do not clear it. Look for other alarms and
process the problem in order that the btsSiteManager object
becomes "enabled".

"disabled", the site is not operational.
a. As long as the operationalState of the btsSiteManager
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".
b.
As soon as the site is operational (the operationalState

of the btsSiteManager object will be "enabled"), check if
the alarm persists.
Otherwise, go to step 8.
Maintenance using the OMC-R
Perform a "Display" command on the bts object to check if the

cells are concentric.
If the "concentric cell" parameter is "monozone", go to step 3.

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:
For PA: the value of the "bsTxPwrMax" parameter added to

the value to the attenuation of the combiner must be between

411-9001-103 18.06 20 January 2010
304
31dBm and 44dBm, or 32dBm at the band limit for only GSM
1900.
For HePA: the value of the "bsTxPwrMax" parameter added

to the value to the attenuation of the combiner must be
between 34dBm and 47dBm.
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 defines the correct values of the
"bsTxPwrMax" parameter, depending on the combiners used in
the BTS. The "Nack" value is not allowed.
Table 3
PA configuration
Combiners
TxF/D
H2D
H4D
DLU attenuation
51 44
Nack
Nack
Nack
43
Pmax
Nack
Nack
42
Pmax
Nack
Nack
41
Pmax-2
Nack
Nack
40
Pmax-2
Pmax
Nack
39
Pmax-4
Pmax
Nack
38
Pmax-4
Pmax-2
Nack
37
Pmax-6
Pmax-2
Nack
36
Pmax-6
Pmax-4
Pmax
35
Pmax-8
Pmax-4
Pmax
34
Pmax-8
Pmax-6
Pmax-2
33
Pmax-10
Pmax-6
Pmax-2
32
Pmax-10
Pmax-8
Pmax-4
31
Pmax-12
Pmax-8
Pmax-4
30
Pmax-12
Pmax-10
Pmax-6
29
Nack
Pmax-10
Pmax-6
28
Nack
Pmax-12
Pmax-8
27
Nack
Pmax-12
Pmax-8
26
Nack
Nack
Pmax-10
25
Nack
Nack
Pmax-10
24
Nack
Nack
Pmax-12
bsTxPwrMax

411-9001-103 18.06 20 January 2010
Combiners
TxF/D
H2D
H4D
DLU attenuation
23
Nack
Nack
Pmax-12
22 0
Nack
Nack
Nack
Table 4
HePA configuration
Dp
TxF/D
H2D
H4D
51 48
Nack
Nack
Nack
Nack
47
Pmax
Nack
Nack
Nack
46
Pmax
Pmax
Nack
Nack
45
Pmax-2
Nack
Nack
Nack
Nack
Nack
Nack
Pmax
Nack
Combiners
DLU or OMC
attenuation
bsTxPwrMax
44
Pmax-2
43
Pmax-4
42
Pmax-4
41
Pmax-6
40
Pmax-6
Pmax-4
Nack
Pmax-6
Pmax-2
39
38
Nack
Nack
Pmax-8
Pmax-8
Pmax-4
Pmax
Pmax-10
Pmax-10
Pmax-6
Pmax-2
34
Pmax-12
Pmax-12
Pmax-8
Pmax-4
33
Nack
Nack
32
Nack
Nack
Pmax-10
Pmax-6
31
Nack
Nack
30
Nack
Nack
Pmax-12
Pmax-8
29
Nack
Nack
Nack
28
Nack
Nack
Nack
27
Nack
Nack
Nack
26
Nack
Nack
Nack
Pmax-12
25
Nack
Nack
Nack
Nack
24
Nack
Nack
Nack
Nack
23
Nack
Nack
Nack
Nack
37
36
35

411-9001-103 18.06 20 January 2010
Pmax-10
305
306
Combiners
Dp
TxF/D
H2D
H4D
Nack
Nack
Nack
Nack
DLU or OMC
attenuation
22 0
If the value is not correct, change it.

If the value is correct, replace the DRX (Field Replaceable
Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8006 BTS
Go to step 6.
Modify the value of the "bsTxPwrMax" parameter according to


the value to the attenuation of the combiner and reduced of
the value of the "transceiver zone Ref" parameter must be
between 31dBm and 44dBm, or 32dBm at the band limit for
only GSM 1900.

to the value to the attenuation of the combiner and reduced
of the value of the "transceiver zone Ref" parameter must be

The "transceiver zone Ref" parameter is obtained by performing
a "Display" command on the transceiver object.
on the btsSiteManager object. This parameter must not be filled
in for the "dual band" or "dual coupling" values of the "concentric
cell" parameter.
The preceding table defines the correct values of the
the BTS. The "Nack" value is not allowed. The "transceiver zone
Ref" parameter must also be verified.

411-9001-103 18.06 20 January 2010
307

If the value is correct, replace the DRX (Field Replaceable
Unit). Refer to:
Nortel GSM BTS S8000/S8003 Troubleshooting
(411-9001-048) for the S8000 BTS
for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8006 BTS
Go to step 5.
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:
FAULT ANALYSIS
This source indicates that the downloading has been aborted.
2.5.36 Source 36: Files missing

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

411-9001-103 18.06 20 January 2010
308
2.5.37 Source 37: Buffer overflow

Source:
(37) Buffer overflow
BTS model:
FAULT ANALYSIS
This source indicates a buffer overflow.
2.5.38 Source 38: Block not received

Source:
(38) Block not received
BTS model:
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:
FAULT ANALYSIS
This source indicates a downloading restart.
2.5.40 Source 40: Request not supported

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

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

411-9001-103 18.06 20 January 2010
309
2.5.42 Source 42: Start-up failure

Source:
(42) Start-up failure
BTS model:
FAULT ANALYSIS
This source indicates a start-up failure.
2.5.43 Source 43: Maximum number of joker TS

Source:
(43) Maximum number of joker TS
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates that there is 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-103 18.06 20 January 2010
310


Procedures) ).

becomes "enabled".

"disabled-failed".
b. As soon as the site is operational (the operationalState of
the btsSiteManager object will be "enabled"), check if the
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

411-9001-103 18.06 20 January 2010
311
Max number of timeslot per transceiverEquipment

for active board (main + joker): see Table 5
"Maximum number of TS (main and joker) per
transceiverEquipment" (page 311) below
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
5 "Maximum number of TS (main and joker) per
transceiverEquipment" (page 311) below
GPRS capability: "up to CSx"
EDGE capability: "full" / "none"
As a reminder, here are the permitted maximum
values:
Table 5
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-103 18.06 20 January 2010
312

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.
Check that the alarm is cleared.

--End--
2.5.44 Source 44: Bad chain type

Source:
(44) Bad chain type
BTS model:
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:
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:
FAULT ANALYSIS
This source indicates a bad internal link EDGE configuration.
2.5.47 Source 47: Inconsistency mapping

Source:
(47) Inconsistency mapping
BTS model:

411-9001-103 18.06 20 January 2010
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:
FAULT ANALYSIS
This source indicates an inconsistency number of joker DS0.
2.5.49 Source 49: Invalid mode

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

Source:
(50) File already open
BTS model:
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:
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:

411-9001-103 18.06 20 January 2010
313
314
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:
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:
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:
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:
FAULT ANALYSIS
This source indicates a RAM mapping error.
2.5.57 Source 57: Flash access error

Source:
(57) Flash access error
BTS model:

411-9001-103 18.06 20 January 2010
315
FAULT ANALYSIS
This source indicates a flash access error.
2.5.58 Source 58: Flash write error

Source:
(58) Flash write error
BTS model:
FAULT ANALYSIS
This source indicates a flash write error.
2.5.59 Source 59: Flash erase error

Source:
(59) Flash erase error
BTS model:
FAULT ANALYSIS
This source indicates a flash erase error.
2.5.60 Source 60: Internal abort

Source:
(60) Internal abort
BTS model:
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:
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:

411-9001-103 18.06 20 January 2010
316
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:

+ S8006
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-103 18.06 20 January 2010
317
2.5.64 Source 64: Inconsistent number of joker DS0

Source:
(64) Inconsistent number of joker DS0
BTS model:
FAULT ANALYSIS
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
TROUBLESHOOTING
Preliminary checks
Step
Action



411-9001-103 18.06 20 January 2010
318
Clear the alarm.


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

411-9001-103 18.06 20 January 2010
319


--End--
2.5.65 Source 65: Exceeded DL joker DS0 pool number

Source:
(65) Exceeded DL joker DS0 pool number
BTS model:
FAULT ANALYSIS
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 65 "Exceeded DL joker DS0 pool
number".
BSC defense
None.
CAUTION
Service reduction
TROUBLESHOOTING

411-9001-103 18.06 20 January 2010
320

Procedure 2
Preliminary checks
Step
Action


Clear the alarm.

concerning cells.
Procedures)).


above).

Procedures)).


411-9001-103 18.06 20 January 2010
321
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--
2.5.66 Source 255: Non-significant value

Source:
(255) Non-significant value
BTS model:
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.

411-9001-103 18.06 20 January 2010
322
CAUTION
The site is not downloaded.
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 6
Source
No.
Paragraph
Source wording
Incorrect priority on transceiver
2.6.1 Source 0: Incorrect

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

transceiver
2.6.2 Source 1: Incorrect

setting of channel on
transceiver (page 324)

411-9001-103 18.06 20 January 2010
323
Table 6
Source
No.
Paragraph
Source wording
Cell without BCCH TDM
2.6.3 Source 2: Cell without

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

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

mode
Cell cfg with cavity and dual band

not acceptable
2.6.6 Source 5: Cell cfg with

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

function
2.6.7 Source 6: Missing

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

Abis GSM function

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

Abis GSM function
Missing RfTrans management Abis

GSM function

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

function

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

GSM function

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

function

TS management Abis GSM
function (page 327)
2.6.5 Source 4: Wrong

value for BSS TEI in T1
mode (page 325)

Abis traffic management
Abis GSM function
(page 326)

411-9001-103 18.06 20 January 2010
324
Table 6
Source
No.
Paragraph
Source wording
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 327)
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 327)
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:
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:
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:
FAULT ANALYSIS
This alarm indicates a cell without BCCH TDM.

411-9001-103 18.06 20 January 2010
2.6.4 Source 3: Radio Time Slot not used

Fault number 1056
Source:
(3) Radio Time Slot not used
BTS model:
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:
FAULT ANALYSIS
This alarm indicates a wrong value for BSS TEI in T1 mode.
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:
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:
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:

411-9001-103 18.06 20 January 2010
325
326
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:
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:
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:
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:
FAULT ANALYSIS
This alarm indicates a missing TDMA management Abis GSM function.

411-9001-103 18.06 20 January 2010
327
2.6.13 Source 12: Missing TS management Abis GSM function

Fault number 1056
Source:
(12) Missing TS management Abis GSM function
BTS model:
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:
FAULT ANALYSIS
This alarm indicates that the TDMA exists in RDC but the object was not
created.
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:
FAULT ANALYSIS
This alarm indicates that too many EDGE TDMAs (>16 per site) are
configured.
Fault number:
1058
GSM entity configuration regression
Type
processingErrorAlarm

This alarm indicates an entity of the BTS detects an anomaly in its
configuration, reports it to the BSC via this alarm, and de-configures itself.
BSC defense

411-9001-103 18.06 20 January 2010
328
If the site is operational, the BSC unconfigures the btsSiteManager

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

actual connections and the connections declared at the OMC-R.
CAUTION
As long as the operationalState of the btsSiteManager
object is "disabled-f ailed", the site is lost.
CAUTION
Service reduction
As long as the operationalState of the transceiverEquipment
object 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
411-9001-103 18.06 20 January 2010
329
The BSC receives a message from the BTS that it cannot treat for one of
the following reasons:
the message is out of sequence

the message concerns an unknown element, for example, a distant
item of equipment not created at the OMC-R but emitting notifications

BSC defense
None.
None.
TROUBLESHOOTING
For a message on an unknown element (an element not declared at

the OMC-R), switch off the concerned element.
Otherwise, no maintenance action is required.
WARNING
If several 1059 fault numbers are detected by the same cell, call
the manufacturer.
Attribute value change
1060
Abis event reporting a transient default
Type
equipmentAlarm
The spontaneous message 1060 accepts causes and equipment wordings

corresponding to the DRX, eDRX, eDRX2, ND3, ePA, HePA, CMCF phase
1 and CMCF phase 2 fault causes.
The warning 1060 (transient) and the fault number 1067 (begin/end)
accept these items of equipment. The causes are the same for all the DRX
types fault causes.
The spontaneous message 1060 corresponds to a warning and does not
require a maintenance action, except in conjunction with the fault number
1067.

411-9001-103 18.06 20 January 2010
330
The following table indicates all the sources of the fault number 1060 for
the S8000 Outdoor and Indoor BTSs with the BCF or CBCF, the S8002
BTSs, the S8003 BTSs, and the S8006 BTSs. For more information on
each source, refer to the indicated paragraph to know the corrective
Table 7
Source
wording
Source No.
S8000
Indoor
BCF
CBCF
S8000 Out
door
BCF
CBC
F
S800
2
S8003
S8006
Paragra
ph
Battery cabinet
5832705
Over tempe
rature
5832706
DC power
fault
5832707
Doors
5832708
AC power
fault
5832709
Surge
protector
Battery Remote Controller (BRC)

6553601
Manual
switch on
battery
power
2.9.1
BRC
(source:
Manual
switch on
battery
power)
(page
351)
6553602
Automatic
switch on
battery
power
2.9.2
BRC (so
urce: Au
tomatic
switch on
battery
power)
(page
351)

411-9001-103 18.06 20 January 2010
Source No.
Source
wording
S8000
Indoor
BCF
CBCF
S8000 Out
door
BCF
CBC
F
S800
2
S8003
S8006
331
Paragra
ph
6553603
Manual
switch on
main power
2.9.3
BRC
(source:
Manual
switch
on main
power)
(page
351)
6553604
Automatic
switch on
main power
2.9.4
BRC
(source:
Automat
ic switch
on main
power)
(page
352)
Cavity
8388609
Cavity out
of service
2.9.5
Cavity
(source:
Cavity
parked
after tun
ing fault
(min not
found))
(page
352)
2.9.6
Cavity
(source:
Nack ans
wer from
cavity)
(page
354)
Cavity
parked after
tuning fault
(min not
found)
8388610
8388611
Loss of
cavity initi
alization
Nack answe
r from cavity
8388612

411-9001-103 18.06 20 January 2010
332
Source
wording
Source No.
S8000
Indoor
BCF
CBCF
S8000 Out
door
BCF
CBC
F
S800
2
S8003
S8006
2.9.7
Cavity
(source:
Cavity
parked
after tun
ing fault
(power
too low))
(page
354)
2.9.8
Cavity
(source:
Cavity
parked
after tun
ing fault
(tuning
detector
)) (page
355)
Cavity
parked after
tuning fault
(power too
low)
8388613
8388614
8388615
Cavity
parked
after tuning
fault (tuning
detector
problem)
Internal
software
problem
Paragra
ph
C-DACS climatic system

7929857
Dirty filter
7929858
DACS failed
CMCF
CMCF phase 1
CMCF phase 2
9502722
12779522
12845058
Unknown
message
CMCF
CMCF phase 1
CMCF phase 2

411-9001-103 18.06 20 January 2010
2.9.9
CMCF
board
(source:
Unknown
message
) (page
355)
Source No.
Source
wording
S8000
Indoor
BCF
CBCF
S8000 Out
door
BCF
CBC
F
333
S800
2
S8003
S8006
Paragra
ph
9502752
12779552
12845088
Restart due
to reset by
BSC
9502753
12779553
12845089
Restart due
to reset by
reset button
9502754
12779554
12845090
Restart due
to power on
9502755
12779555
12845091
Restart due
to a too
long PCM
scanning
9502756
12779556
12845092
Restart
requested
by the
active board
2.9.10
CMCF
board
(source:
Restart
requeste
d by the
active
board)
(page
356)
9502771
12779571
12845107
Board reset
asked by
OMC
2.9.11
CMCF
(source:
Board
reset
asked by
OMC)
(page
356)
9502757
12779557
12845093
Restart
due to a
software
upgrade

411-9001-103 18.06 20 January 2010
334
Source
wording
Source No.
S8000
Indoor
BCF
CBCF
S8000 Out
door
BCF
CBC
F
S800
2
S8003
S8006
Paragra
ph
9502758
12779558
12845094
Restart due
to hardware
watchdog
2.9.12
CMCF
board
(source:
Restart
due to
hardware
watchdo
g) (page
357)
9502759
12775095
12845095
Restart due
to double
bus fault
2.9.13
CMCF
boards
(source:
Restart
due to
double
bus faul
t) (page
357)
9502760
12779560
12845096
Reset for
new Lapd
parameters
CMCF
2.9.14
CMCF
boards
(source:
Reset
for new
Lapd pa
rameters
CMCF)
(page
357)
CMCF
CMCF phase 1
CMCF phase 2
9502761
12779561
12845097
Restart due
to Syn not
Locked
9502963
12779763
12845299
Statistic
report
9568240
12845040
12910576
Debug

411-9001-103 18.06 20 January 2010
Source
wording
Source No.
S8000
Indoor
BCF
CBCF
S8000 Out
door
BCF
CBC
F
S800
2
S8003
S8006
335
Paragra
ph
CMCF
CMCF phase 1
CMCF phase 2
9568241
12845041
12910577
ABIS PCM
statistics
2.9.15
CMCF
boards
(source:
ABIS
PCM st
atistics)
(page
358)
9568255
12845055
12910591
Soft
CSWM boards
4259842
Unknown
message
on ABIS
interface
4259872
Restart due
to reset by
BSC
4259873
Restart due
to reset by
reset button
4259874
Restart due
to power on
4259875
Restart due
to a too
long PCM
scanning
4259876
Restart
requested
by the
active board
4259877
Restart
due to a
software
upgrade

411-9001-103 18.06 20 January 2010
336
Source No.
Source
wording
S8000
Indoor
BCF
CBCF
S8000 Out
door
BCF
CBC
F
S800
2
S8003
S8006
Paragra
ph
4259878
Restart due
to hardware
watchdog
2.9.16
CSWM
board
(source:
Restart
due to
hardware
watchdo
g) (page
358)
4259879
Restart due
to double
bus fault
2.9.17
CSWM
board
(source:
Restart
due to
double
bus faul
t) (page
359)
4325375
Soft
DACS climatic system

7864321
Dirty filter
7864322
DACS failed
DRX module
9437189
SPU fault
9437441
Restart due
to reset by
reset button
9437187
12582915
12976131
Loss of
PCM link
9437188
12582916
12976132
Loss of
GSM clock
DRX
eDRX
DRX ND3

411-9001-103 18.06 20 January 2010
Source No.
Source
wording
S8000
Indoor
S8000 Out
door
BCF
CBCF
BCF
CBC
F
337
S800
2
S8003
S8006
Paragra
ph
9437192
12582920
12976136
Incorrect Ab
is message
9437195
12582923
12976139
No flag on
FH bus
9437196
12582924
12976140
Frequency
collision on
FH bus
2.9.18
DRX or
eDRX
or DRX
-ND3 or
eDRX2
modules
(source:
Freque
ncy coll
ision on
FH bus)
(page
359)
9437207
12582935
12976151
FACCH
congestion
2.9.20
DRX or
eDRX
or DRX
ND3 or
eDRX2
modules
(source:
FACCH
congestio
n) (page
360)
9437208
12582936
12976152
LAPD
congestion
9437210
12582938
12976154
Underrun
AMNU-SPU
9437425
12583153
12976369
Post mort
em dump
zone 1

411-9001-103 18.06 20 January 2010
338
Source No.
Source
wording
S8000
Indoor
S8000 Out
door
BCF
CBCF
BCF
CBC
F
S800
2
S8003
S8006
Paragra
ph
9437426
12583154
12976370
Post mort
em dump
zone 2
9437440
12583168
12976384
Restart due
to reset by
BSC
9437442
12583170
12976385
Restart due
to power on
9437443
12583171
12976385
Restart
requested
by the BCF
2.9.19
DRX or
eDRX
or DRX
-ND3 or
eDRX2
(source:
Restart
requeste
d by the
BCF)
(page
360)
9437444
12583172
12976386
Restart
due to the
timeout on
the OML
link with
BSC
9437445
12583173
12976387
Restart
due to the
timeout on
the OML
link with
BCF
9437446
12583174
12976388
Restart
due to a
software
upgrade

411-9001-103 18.06 20 January 2010
Source No.
Source
wording
S8000
Indoor
S8000 Out
door
BCF
CBCF
BCF
CBC
F
S800
2
S8003
S8006
339
Paragra
ph
9437447
12583175
13976389
Restart due
to hardware
watchdog
2.9.21
DRX or
eDRX
or DRX
ND3 or
eDRX2
modules
(source:
Reset
due to
hardware
watchdo
g) (page
361)
9437448
12583176
12976390
Restart due
to double
bus fault
2.9.13
CMCF
boards
(source:
Restart
due to
double
bus faul
t) (page
357)
9437449
12583177
12976391
Reset due
to loss of
lock
9437450
12583178
12976392
Restart due
to unknown
software
reset
9437451
12583179
12976393
Restart due
to a loss
of internal
PCM clock
sent by the
BCF

411-9001-103 18.06 20 January 2010
340
Source No.
Source
wording
S8000
Indoor
S8000 Out
door
BCF
CBCF
BCF
CBC
F
S800
2
S8003
S8006
Paragra
ph
9437458
or
12583186
or
12976402
BCCH
config dump
2.9.23
DRX or
eDRX
or DRX
-ND3 or
eDRX2
modules
(source:
BCCH
config
dump)
(page
362)
9437474
or
12583202
or
12976418
SACCH
config dump
2.9.24
DRX or
eDRX or
DRX-N
D3 mod
ules or
eDRX2
(source:
SACCH
config
dump)
(page
363)
9437490
or
12583218
or
12976434
L1M config
dump
2.9.25
DRX or
eDRX
or DRX
-ND3 or
eDRX2
modules
(source:
L1M conf
ig dump)
(page
363)

411-9001-103 18.06 20 January 2010
Source No.
Source
wording
S8000
Indoor
S8000 Out
door
BCF
CBCF
BCF
CBC
F
S800
2
S8003
S8006
341
Paragra
ph
9437491
or
12583219
or
12976435
RSL anoma
ly
2.9.26
DRX or
eDRX or
eDRX2
or DR
X-ND3
modules
(source:
RSL an
omaly)
(page
363)
9502704
12648432
13041648
Debug
4456449
Major fault
4456450
Queue
overflow in
DSC
4456452
Queue OK
4456453
Channel_H
SCX
DSC boards
eDRX2
15204355
Loss of
PCM link
15204356
Loss of
GSM clock
15204360
Incorrect Ab
is message
15204363
No flag on
FH bus

411-9001-103 18.06 20 January 2010
342
Source No.
Source
wording
S8000
Indoor
BCF
CBCF
S8000 Out
door
BCF
CBC
F
S800
2
S8003
S8006
Paragra
ph
15204364
Frequency
collision on
FH bus
2.9.18
DRX or
eDRX
or DRX
-ND3 or
eDRX2
modules
(source:
Freque
ncy coll
ision on
FH bus)
(page
359)
15204375
FACCH
congestion
2.9.20
DRX or
eDRX
or DRX
ND3 or
eDRX2
modules
(source:
FACCH
congestio
n) (page
360)
15204376
LAPD
congestion
15204378
Underrun
AMNU-SPU
15204593
Post mort
em dump
zone 1
15204594
Post mort
em dump
zone 2
15204610
Restart due
to power on

411-9001-103 18.06 20 January 2010
Source No.
Source
wording
S8000
Indoor
BCF
CBCF
S8000 Out
door
BCF
CBC
F
S800
2
S8003
15204611
Restart
requested
by the BCF
15204612
Restart
due to the
timeout on
the OML
link with
BSC
15204613
Restart
due to the
timeout on
the OML
link with
BCF
15204614
Restart
due to a
software
upgrade
15204615
Restart due
to hardware
watchdog

411-9001-103 18.06 20 January 2010
S8006
343
Paragra
ph
2.9.19
DRX or
eDRX
or DRX
-ND3 or
eDRX2
(source:
Restart
requeste
d by the
BCF)
(page
360)
2.9.16
CSWM
board
(source:
Restart
due to
hardware
watchdo
g) (page
358)
344
Source No.
Source
wording
S8000
Indoor
BCF
CBCF
S8000 Out
door
BCF
CBC
F
S800
2
S8003
15204616
Restart due
to double
bus fault
15204617
Reset due
to loss of
lock
15204618
Restart due
to unknown
software
reset
15204619
Restart due
to a loss
of internal
PCM clock
sent by BCF
15204626
BCCH
config dump

411-9001-103 18.06 20 January 2010
S8006
Paragra
ph
2.9.17
CSWM
board
(source:
Restart
due to
double
bus faul
t) (page
359)
2.9.23
DRX or
eDRX
or DRX
-ND3 or
eDRX2
modules
(source:
BCCH
config
dump)
(page
362)
Source No.
Source
wording
S8000
Indoor
BCF
CBCF
S8000 Out
door
BCF
CBC
F
S800
2
S8003
S8006
345
Paragra
ph
15204642
SACCH
config dump
2.9.24
DRX or
eDRX or
DRX-N
D3 mod
ules or
eDRX2
(source:
SACCH
config
dump)
(page
363)
15204658
L1M config
dump
2.9.25
DRX or
eDRX
or DRX
-ND3 or
eDRX2
modules
(source:
L1M conf
ig dump)
(page
363)
15204659
RSL anoma
ly
2.9.26
DRX or
eDRX or
eDRX2
or DR
X-ND3
modules
(source:
RSL an
omaly)
(page
363)
GTW boards
4587522
FIFO-reset
Output Rx-splitter D
9764865
Over curren
t

411-9001-103 18.06 20 January 2010
346
Source No.
Source
wording
S8000
Indoor
BCF
S8000 Out
door
CBCF
S800
2
S8003
S8006
Paragra
ph
CBC
F
BCF
Output Rx-splitter M
9699329
Over curren
t
PCM
6488065
PCM
Rectifiers
5242881
AC fault
5242882
DC fault
5242883
Over tempe
rature
5242884
External
battery level
1
5242885
PCU protect
ive
5242886
Battery on
discharges
2.9.65 T
x Filters
(source:
VSWR
level 2)
(page
384)
Tx Filters
7536642
VSWR level
2
Table 8
Fault number 1060 sources (IP)
S8000
Indoor
Source No.
Source wording
S8000
Outd
oor
S8
00
CB 2
BC CB BC
C
F CF F
F
S8
00
3
S8
00
6
Paragraph
IPM core
15728641
Restart due to
power on
2.9.27 IPM-USER core

(source: Restart due to
power-on) (page 364)

411-9001-103 18.06 20 January 2010
S8000
Indoor
Source No.
Source wording
S8000
Outd
oor
S8
00
CB 2
BC CB BC
C
F CF F
F
S8
00
3
S8
00
6
347
Paragraph
15728642
Restart due to
reset by button

(source: Restart due
to reset by button)
(page 364)
15728643
Restart due to
software upgrade

to software upgrade)
(page 365)
15728644
Restart due
to hardware
watchdog

hardware watchdog)
(page 365)
15728647
IBOS authenticati
on has failed
2.9.31 IPM-USER
core (source: IBOS
authentication has failed)
(page 366)
15728648
No TCP connecti
on can be set up
with IGM
2.9.32 IPM-USER
core (source: No TCP
connection can be set up
with IGM) (page 366)
15728649
Reset requested
by IGM with no
Ethernet switch
reset

(source: Reset requested
by IGM with no Ethernet
switch reset) (page 367)
15728650
Reset requested
by IGM with
Ethernet switch
reset

by IGM with Ethernet
15728651
Reset requested
by IBOS with
BIST execution
and Ethernet
switch reset

by IBOS with BIST
execution and Ethernet
15728652
Reset requested
by IBOS with no
BIST execution
and Ethernet
switch reset

by IBOS with no BIST

411-9001-103 18.06 20 January 2010
348
S8000
Indoor
S8000
Outd
oor
S8
00
CB 2
BC CB BC
C
F CF F
F
S8
00
3
S8
00
6
Paragraph
Source No.
Source wording
15728653
Reset requested
by IBOS with
BIST execution
and no Ethernet
switch reset

by IBOS with BIST
execution and no Ethernet
15728654
Reset requested
by IBOS with no
BIST execution
nor Ethernet
switch reset

execution nor Ethernet
15728655
Restart after TM
L commissioning

(source: Restart after
TML commissioning)
(page 370)
15728656
Connection with
IGM has been
lost (no status
received for
7 keep-alive
periods).

(source: Connection
with IGM has been lost
(no status received for
7 keep-alive periods))
(page 371)
15728659
No response to
DHCP requests
for 15 minutes

(source: No response to
DHCP requests for 15
minutes) (page 371)
15728660
No response to
DNS requests for
15 minutes

(source: No response
to DNS requests for 15
minutes) (page 372)
15728673
Debug
2.9.43 IPM-USER
core (source: Debug)
(page 372)
15728674
Soft

(source: Soft) (page 373)
RIPM-USER core
15794177
Restart due to
power on
2.9.45 RIPM-USER core

power-on) (page 373)

411-9001-103 18.06 20 January 2010
S8000
Indoor
Source No.
Source wording
S8000
Outd
oor
S8
00
CB 2
BC CB BC
C
F CF F
F
S8
00
3
S8
00
6
349
Paragraph
15794178
Restart due to
reset by button
2.9.46 RIPM-USER
core (source: Restart
due to reset by button)
(page 374)
15794179
Restart due to
software upgrade

to software upgrade)
(page 374)
15794180
Restart due
to hardware
watchdog

hardware watchdog)
(page 375)
15794183
IBOS authenticati
on has failed
2.9.49 RIPM-USER
core (source: IBOS
authentication has failed)
(page 375)
15794184
No TCP connecti
on can be set up
with IGM
2.9.50 RIPM-USER
core (source: No TCP
connection can be set up
with IGM) (page 376)
15794185
Reset requested
by IGM with no
Ethernet switch
reset

by IGM with no Ethernet
15794186
Reset requested
by IGM with
Ethernet switch
reset

by IGM with Ethernet
15794187
Reset requested
by IBOS with
BIST execution
and Ethernet
switch reset

by IBOS with BIST
15794188
Reset requested
by IBOS with no
BIST execution
and Ethernet
switch reset


411-9001-103 18.06 20 January 2010
350
S8000
Indoor
S8000
Outd
oor
S8
00
CB 2
BC CB BC
C
F CF F
F
S8
00
3
S8
00
6
Paragraph
Source No.
Source wording
15794189
Reset requested
by IBOS with
BIST execution
and no Ethernet
switch reset
2.9.55 RIPM-USER
core (source: Reset
requested by IBOS with
BIST execution and no
Ethernet switch reset)
(page 378)
15794190
Reset requested
by IBOS with no
BIST execution
nor Ethernet
switch reset

execution nor Ethernet
15794191
Restart after TM
L commissioning

(source: Restart after
TML commissioning)
(page 379)
15794192
Connection with
IGM has been
lost (no status
received for
7 keep_alive
periods).

(source: Connection
with IGM has been lost
(no status received for
7 keep-alive periods))
(page 380)
15794195
No response to
DHCP requests
for 15 minutes

(source: No response to
DHCP requests for 15
minutes) (page 380)
15794196
No response to
DNS requests for
15 minutes

(source: No response
to DNS requests for 15
minutes) (page 381)
15794209
Debug
2.9.61 RIPM-USER
core (source: Debug)
(page 381)
15794210
Soft

(source: Soft) (page 382)

411-9001-103 18.06 20 January 2010
S8000
Indoor
S8000
Outd
oor
S8
00
CB 2
BC CB BC
C
F CF F
F
S8
00
3
S8
00
6
351
Paragraph
Source No.
Source wording
15794193
Reset requested
by active with
BIST execution

by active with BIST
execution) (page 383)
15794194
Reset requested
by active with no
BIST execution

by active with no BIST
execution) (page 383)
2.9.1 BRC (source: Manual switch on battery power)

Fault number 1060
Equipment :
BRC
Source :
(6553601) Manual switch on battery power
BTS model :
S8000 CBCF Outdoor + S8002
FAULT ANALYSIS
This notification indicates that the BTS has been manually (using OMC-R
command) switched from main power to battery.
2.9.2 BRC (source: Automatic switch on battery power)

Fault number 1060
Equipment:
BRC
Source:
(6553602) Automatic switch on battery power
BTS model:
FAULT ANALYSIS
This notification indicates that the BTS has automatically switched from
main power to battery.
2.9.3 BRC (source: Manual switch on main power)

Fault number 1060
Equipment:
BRC
Source:
(6553603) Manual switch on main power
BTS model:
FAULT ANALYSIS
411-9001-103 18.06 20 January 2010
352
This notification indicates that the BTS has been manually switched from
battery to main power.
2.9.4 BRC (source: Automatic switch on main power)

Fault number 1060
Equipment:
BRC
Source:
(6553604) Automatic switch on main power
BTS model:
FAULT ANALYSIS
This notification indicates that the BTS has been automatically switched
from battery to main power.
2.9.5 Cavity (source: Cavity parked after tuning fault (min not found))
Fault number 1060
Abis event reporting a hardware fault
Equipment:
cavity
Source:
(8388610) Cavity parked after tuning fault (min not

found)
BTS model:
S8000 Indoor
FAULT ANALYSIS
This alarm indicates that the cavity is no longer parked on its configuration
frequency.

BSC defense The BSC unconfigures the transceiverEquipment
object concerned and reconfigures the transceiver object on another
transceiverEquipment object (if the TDMA is priority).
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010


353

Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the cavity equipment 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 "cavity" equipment is "failed", the fault is

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

not confirmed. Go to step 5.
Maintenance at the OMC-R
Lock the transceiverEquipment object in order to trigger a new

tuning.

411-9001-103 18.06 20 January 2010
354
If the problem has disappeared, go to step 5.

If the problem persists after several attempts, an on-site
intervention is necessary to locate the problem.

--End--
2.9.6 Cavity (source: Nack answer from cavity)

Fault number 1060
Equipment:
cavity
Source:
(8388612) Nack answer from cavity
BTS model:
S8000 Indoor
FAULT ANALYSIS
This alarm indicates that there was a NACK response on the slave.

BSC defense None
None.
None
TROUBLESHOOTING
Set the administrativeState of the transceiverEquipment object to

"locked".
Set the administrativeState of the transceiverEquipment object to

"unlocked".
2.9.7 Cavity (source: Cavity parked after tuning fault (power too low))
Fault number 1060
Equipment:
cavity
Source:
(8388613) Cavity parked after tuning fault (power

too low)
BTS model:
S8000 Indoor

concerned.

411-9001-103 18.06 20 January 2010
355
One TRX becomes unavailable.
CAUTION
Service reduction
2.9.8 Cavity (source: Cavity parked after tuning fault (tuning detector))
Fault number 1060
Equipment:
cavity
Source:
(8388614) Cavity parked after tuning fault (tuning

detector)
BTS model:
S8000 Indoor

concerned.
CAUTION
Service reduction
2.9.9 CMCF board (source: Unknown message)

Fault number 1060
Equipment:
CMCF or CMCF phase 1 or CMCF phase 2
Source:
(9502722 or 12779522 or 12845058) Unknown

message
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates an unknown Abis message.
BSC defense
None.

411-9001-103 18.06 20 January 2010
356

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

Fault number 1060
Equipment:
Source:
(9502756, 12779556, 12845092) Restart requested by the active

board
BTS model:
FAULT ANALYSIS
This alarm indicates a reset of the passive CMCF requested by the active
CMCF.
IMPACT ON THE SERVICE
No impact on the service.
TROUBLESHOOTING
No maintenance action is required.
2.9.11 CMCF (source: Board reset asked by OMC)

Fault number 1060
Equipment:
Source:
(9502771, 12779571, 12845107) Board reset asked by OMC
BTS model:
FAULT ANALYSIS
This alarm indicates a board reset asked by the OMC-R, for the active
CMCF.
IMPACT ON THE SERVICE
The BTS behavior is identical to a hot switchover:
There is no impact on the traffic and on the configuration.

The passive CMCF becomes active.
The BTS sends a restart event of the reset CMCF.

411-9001-103 18.06 20 January 2010
357
TROUBLESHOOTING
2.9.12 CMCF board (source: Restart due to hardware watchdog)

Fault number 1060
Equipment:
Source:
(9502758 or 12779558 or 12845094) Restart due to

hardware watchdog
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates a restart of the CMCF boards by a hardware
watchdog.
2.9.13 CMCF boards (source: Restart due to double bus fault)

Fault number 1060
Equipment:
Source:
(9502759 or 12779559 or 12845095) Restart due

to double bus fault
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates a restart of the CMCF boards due to a double bus
fault.
TROUBLESHOOTING
If the fault occurs sporadically, no maintenance action is required.
If the fault is repetitive, replace the faulty CMCF. Refer to 411-9001-048
(Nortel GSM BTS S8000/S8003 Troubleshooting).
2.9.14 CMCF boards (source: Reset for new Lapd parameters CMCF)
Fault number 1060
Equipment:
Source:
(9502760) Reset for new Lapd parameters CMCF

411-9001-103 18.06 20 January 2010
358
Source:

Ph1
Source:

Ph2
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates a BTS restart to take into account new Lapd
parameter values from the BSC, so as to use a satellite configuration
(satellite Abis interface).
Even if BSC Lapd parameters are not consistent with BTS values, the
Lapd link can be established and the Status Request can be sent to the
BTS.
When receiving the Status Request, in case of BSC / BTS inconsistency,
the BTS writes the new values in its memory and then restarts to take into
account this new set of parameters.
TROUBLESHOOTING
2.9.15 CMCF boards (source: ABIS PCM statistics)

Fault number 1060
Equipment:
CMCF
Source:
(9568241 or 12845041 or 12910577) ABIS PCM

statistics
BTS model:

+ S8006
FAULT ANALYSIS
This notification appears when the command "Display data information" is
performed on the object "btsSiteManager" at the OMC-R.
2.9.16 CSWM board (source: Restart due to hardware watchdog)

Fault number 1060
Equipment:
CSWM
Source:
(4259878) Restart due to hardware watchdog
BTS model:
FAULT ANALYSIS

411-9001-103 18.06 20 January 2010
359
This alarm indicates a restart of the CSWM boards by a hardware

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

Fault number 1060
Equipment:
CSWM
Source:
(4259879) Restart due to double bus fault
BTS model:
FAULT ANALYSIS
This alarm indicates a restart of the CSWM board due to a double bus
fault.
TROUBLESHOOTING
If the fault is repetitive, replace the faulty CSWM. Refer to 411-9001-048
2.9.18 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:

Frequency collision on FH bus)
Fault number 1060
Equipment:
DRX or eDRX or DRX-ND3 or eDRX2
Source:
9437196 or 12582924 or 12976140 or 15204363

Frequency collision on FH bus
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates that a frequency collision has been encountered on
the FH bus, due to a frequency hopping configuration error.
BSC defense
None.

411-9001-103 18.06 20 January 2010
360
CAUTION
Service quality
The phonic quality is lost.
TROUBLESHOOTING
Check the cell and the frequency hopping laws (the configuration of
Frequency Hopping Laws, or the TDMA configuration if there is not any
hopping).
2.9.19 DRX or eDRX or DRX-ND3 or eDRX2 (source: Restart requested

by the BCF)
Fault number 1060
Equipment:
Source:
(9437443, 12976387, 12583171, 15204611) Restart requested

by the BCF
BTS model:
FAULT ANALYSIS
This alarm indicates a reset of the DRX requested by the BCF. The
BTS informs the BSC of the DRX loss. The DRX is declared faulty and
reconfigured.
BSC defense
None.
The DRX is declared faulty and reconfigured. A restart event of the DRX is
sent to the BSC.
TROUBLESHOOTING
2.9.20 DRX or eDRX or DRX ND3 or eDRX2 modules (source: FACCH

congestion)
Fault number 1060
Equipment:

DRX or eDRX or DRX ND3 or eDRX2

411-9001-103 18.06 20 January 2010
Source:
(9437207 or 12582935 or 12976151 or

15204375) FACCH congestion
BTS model:
S8000 Outdoor + S8000 Indoor + S8002 +

S8003 + S8006
361
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 messages
per 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, the 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
2.9.21 DRX or eDRX or DRX ND3 or eDRX2 modules (source: Reset

due to hardware watchdog)
Fault number 1060
Equipment:


411-9001-103 18.06 20 January 2010
362
Source:
9437447 or 12583175 or 12976389 or

15204615 : restart due to hardware watchdog
BTS model:

S8003 + S8006
FAULT ANALYSIS
This alarm indicates a restart of the DRX by a hardware watchdog.
2.9.22 DRX or eDRX or DRX ND3 or eDRX2 modules (source: Restart

due to double bus fault)
Fault number 1060
Equipment:
Source:
9437448 or 12583176 or 12976390 or

15204616: Restart due to double bus fault
BTS model:

S8003 + S8006
FAULT ANALYSIS
This alarm indicates a restart of the DRX due to a double bus fault.
TROUBLESHOOTING
If the fault is repetitive, replace the faulty DRX. Refer to 411-9001-048
2.9.23 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: BCCH

config dump)
Fault number 1060
Equipment:
Source:
9437458 or 12583186 or 12976402 or

15204626 BCCH config dump
BTS model:

S8003 + S8006
FAULT ANALYSIS
An anomaly has been detected in either a first or second BCCH
configuration. This transient event contains details of the anomaly.
TROUBLESHOOTING

411-9001-103 18.06 20 January 2010
363
2.9.24 DRX or eDRX or DRX-ND3 modules or eDRX2 (source: SACCH

config dump)
Fault number 1060
Equipment:
Source:
9437474 or 12583202 or 12976418 or 15204642

SACCH config dump
BTS model:

+ S8006
FAULT ANALYSIS
An anomaly has been detected in either a first or second SACCH
TROUBLESHOOTING
2.9.25 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: L1M

config dump)
Fault number 1060
Equipment:
Source:
9437490 or 12583218 or 12976434 or

15204658 L1M config dump
BTS model:

S8003 + S8006
FAULT ANALYSIS
An anomaly has been detected in either a first or second L1M
TROUBLESHOOTING
2.9.26 DRX or eDRX or eDRX2 or DRX-ND3 modules (source: RSL

anomaly)
Fault number 1060
Equipment:


411-9001-103 18.06 20 January 2010
364
Source:
9437491 or 12583219 or 12976435 or

15204659 RSL anomaly
BTS model:

S8003 + S8006
FAULT ANALYSIS
A non critical anomaly has been detected on a communication. This
transient event contains details of the anomaly.
TROUBLESHOOTING
2.9.27 IPM-USER core (source: Restart due to power-on)

Fault number 1060 Abis event reporting a transient default
Equipment:
IPM-USER core
Source:
(15728641) Restart due to power-on
BTS model:
S8000 Outdoor + S8000 Indoor
FAULT ANALYSIS
This alarm indicates a restart of the IPM-USER due to a power-on.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.28 IPM-USER core (source: Restart due to reset by button)

Equipment:
IPM-USER core
Source:
(15728642) Restart due to reset by button
BTS model:
FAULT ANALYSIS
This alarm indicates an IPM-USER restart due to reset by button.

411-9001-103 18.06 20 January 2010
365

BSC defense
None.
None.
TROUBLESHOOTING
2.9.29 IPM-USER core (source: Restart due to software upgrade)

Equipment:
IPM-USER core
Source:
(15728643) Restart due to software upgrade
BTS model:
FAULT ANALYSIS
This alarm indicates an IPM-USER restart due to software upgrade (new
software version activation).

BSC defense
None.
None.
TROUBLESHOOTING
2.9.30 IPM-USER core (source: Restart due to hardware watchdog)

Equipment:
IPM-USER core
Source:
(15728644 Restart due to hardware watchdog
BTS model:
FAULT ANALYSIS
This alarm indicates an IPM-USER restart due to hardware watchdog.

411-9001-103 18.06 20 January 2010
366

BSC defense
None.
None.
TROUBLESHOOTING
2.9.31 IPM-USER core (source: IBOS authentication has failed)

Equipment:
IPM-USER core
Source:
(15728647) IBOS authentication has failed
BTS model:
FAULT ANALYSIS
This alarm indicates that the IPM-USER does not succeed to connect and
authenticate to any IBOS.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.32 IPM-USER core (source: No TCP connection can be set up with

IGM)
Equipment:
IPM-USER core
Source:
(15728648) No TCP connection can be set up with IGM
BTS model:
FAULT ANALYSIS
This alarm indicates that no TCP connection can be set up with IGM.

411-9001-103 18.06 20 January 2010
367

BSC defense
None.
None.
TROUBLESHOOTING
2.9.33 IPM-USER core (source: Reset requested by IGM with no

Equipment:
IPM-USER core
Source:
(15728649) Reset requested by IGM with no Ethernet switch reset
BTS model:
FAULT ANALYSIS
This alarm indicates that a reset is requested by the IGM, with no Ethernet
switch reset.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.34 IPM-USER core (source: Reset requested by IGM with Ethernet

switch reset)
Equipment:
IPM-USER core
Source:
(15728650) Reset requested by IGM with Ethernet switch reset
BTS model:

411-9001-103 18.06 20 January 2010
368
FAULT ANALYSIS
This alarm indicates that a reset is requested by the IGM, with an Ethernet
switch reset.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.35 IPM-USER core (source: Reset requested by IBOS with BIST

execution and Ethernet switch reset)
Equipment:
IPM-USER core
Source:
(15728651) Reset requested by IBOS with BIST execution and Ethernet switch
reset
BTS model:
FAULT ANALYSIS
This alarm indicates that the active IPM board has been reset with a BIST
execution. The IBOS has requested an Ethernet switch reset.

BSC defense
None.
None.
TROUBLESHOOTING

Equipment:
IPM-USER core

411-9001-103 18.06 20 January 2010
Source:
(157286512) Reset requested by IBOS with no BIST execution and Ethernet

switch reset
BTS model:
369
FAULT ANALYSIS
This alarm indicates that the active IPM board has been reset without a
BIST execution. The IBOS has requested an Ethernet switch reset.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.37 IPM-USER core (source: Reset requested by IBOS with BIST

execution and no Ethernet switch reset)
Equipment:
IPM-USER core
Source:
(157286513) Reset requested by IBOS with BIST execution and no Ethernet

switch reset
BTS model:
FAULT ANALYSIS
This alarm indicates that the active IPM board has been reset with a BIST
execution. The IBOS has not requested an Ethernet switch reset.

BSC defense
None.
None.
TROUBLESHOOTING

411-9001-103 18.06 20 January 2010
370

execution nor Ethernet switch reset)
Equipment:
IPM-USER core
Source:
(157286514) Reset requested by IBOS with no BIST execution nor Ethernet

switch reset
BTS model:
FAULT ANALYSIS
This alarm indicates that the active IPM board has been reset without a
BIST execution. The IBOS has not requested an Ethernet switch reset.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.39 IPM-USER core (source: Restart after TML commissioning)

Equipment:
IPM-USER core
Source:
(157286515) Restart after TML commissioning
BTS model:
FAULT ANALYSIS
This alarm indicates an IPM-USER restart by the TML, after
commissioning.

BSC defense
None.
None.

411-9001-103 18.06 20 January 2010
371
TROUBLESHOOTING
2.9.40 IPM-USER core (source: Connection with IGM has been lost (no
status received for 7 keep-alive periods))
Equipment:
IPM-USER core
Source:
(157286516) Connection with IGM has been lost (no status received for 7
keep-alive periods)
BTS model:
FAULT ANALYSIS
This alarm indicates that the connection with IGM has been lost (no status
received for 7 keep-alive periods).

BSC defense
None.
None.
TROUBLESHOOTING
2.9.41 IPM-USER core (source: No response to DHCP requests for 15

minutes)
Equipment:
IPM-USER core
Source:
(15728659) No response to DHCP requests for 15 minutes
BTS model:
FAULT ANALYSIS
This alarm indicates no response to DHCP requests for 15 minutes.

BSC defense
None.

411-9001-103 18.06 20 January 2010
372
None.
TROUBLESHOOTING
2.9.42 IPM-USER core (source: No response to DNS requests for 15

minutes)
Equipment:
IPM-USER core
Source:
(15728660) No response to DNS requests for 15 minutes
BTS model:
FAULT ANALYSIS
This alarm indicates no response to DNS requests for 15 minutes.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.43 IPM-USER core (source: Debug)

Equipment:
IPM-USER core
Source:
(15728673) Debug
BTS model:
FAULT ANALYSIS
This alarm indicates that a message sent by the IBOS or IPG is not
acknowledged by the IPM-USER.

BSC defense
None.

411-9001-103 18.06 20 January 2010
None.
TROUBLESHOOTING
2.9.44 IPM-USER core (source: Soft)

Equipment:
IPM-USER core
Source:
(15728674) Soft
BTS model:
FAULT ANALYSIS
This alarm indicates that a trap occurs. The IPM-USER sends the
post-mortem dump zone to the IBOS.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.45 RIPM-USER core (source: Restart due to power-on)

Equipment:
RIPM-USER core
Source:
(15794177) Restart due to power-on
BTS model:
FAULT ANALYSIS
This alarm indicates a restart of the RIPM-USER due to a power-on.

BSC defense
None.

411-9001-103 18.06 20 January 2010
373
374
None.
TROUBLESHOOTING
2.9.46 RIPM-USER core (source: Restart due to reset by button)

Equipment:
RIPM-USER core
Source:
(15794178) Restart due to reset by button
BTS model:
FAULT ANALYSIS
This alarm indicates an RIPM-USER restart due to a reset by button.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.47 RIPM-USER core (source: Restart due to software upgrade)

Equipment:
RIPM-USER core
Source:
(15794179) Restart due to software upgrade
BTS model:
FAULT ANALYSIS
This alarm indicates an RIPM-USER core restart due to software upgrade
(new software version activation).

BSC defense
None.

411-9001-103 18.06 20 January 2010
None.
TROUBLESHOOTING
2.9.48 RIPM-USER core (source: Restart due to hardware watchdog)

Equipment:
RIPM-USER core
Source:
(15794180) Restart due to hardware watchdog
BTS model:
FAULT ANALYSIS
This alarm indicates an RIPM-USER restart due to hardware watchdog.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.49 RIPM-USER core (source: IBOS authentication has failed)

Equipment:
RIPM-USER core
Source:
(15794183) IBOS authentication has failed
BTS model:
FAULT ANALYSIS
This alarm indicates that the RIPM-USER core does not succeed to
connect and authenticate to any IBOS.

BSC defense
None.

411-9001-103 18.06 20 January 2010
375
376
None.
TROUBLESHOOTING
2.9.50 RIPM-USER core (source: No TCP connection can be set up with

IGM)
Equipment:
RIPM-USER core
Source:
(15794184) No TCP connection can be set up with IGM
BTS model:
FAULT ANALYSIS
This alarm indicates that no TCP connection can be set up with the IGM.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.51 RIPM-USER core (source: Reset requested by IGM with no

Equipment:
RIPM-USER core
Source:
(15794185) Reset requested by IGM with no Ethernet switch reset
BTS model:
FAULT ANALYSIS
This alarm indicates that a reset is requested by the IGM, with no Ethernet
switch reset.

BSC defense
None.
411-9001-103 18.06 20 January 2010
377
None.
TROUBLESHOOTING
2.9.52 RIPM-USER core (source: Reset requested by IGM with Ethernet

switch reset)
Equipment:
RIPM-USER core
Source:
(15794186) Reset requested by IGM with Ethernet switch reset
BTS model:
FAULT ANALYSIS
This alarm indicates that a reset is requested by the IGM, with an Ethernet
switch reset.

BSC defense
None.
None.
TROUBLESHOOTING

Equipment:
RIPM-USER core
Source:
(15794187) Reset requested by IBOS with BIST execution and Ethernet switch
reset
BTS model:
FAULT ANALYSIS
This alarm indicates an RIPM-USER core restart with a BIST execution.
The IBOS has requested an Ethernet switch reset.

BSC defense
None.
411-9001-103 18.06 20 January 2010
378

None.
TROUBLESHOOTING

Equipment:
RIPM-USER core
Source:
(15794188) Reset requested by IBOS with no BIST execution and Ethernet

switch reset
BTS model:
FAULT ANALYSIS
This alarm indicates an RIPM-USER core restart without a BIST execution.
The IBOS has requested an Ethernet switch reset.

BSC defense
None.
None.
TROUBLESHOOTING

execution and no Ethernet switch reset)
Equipment:
IPM
Source:
(15794189) Reset requested by IBOS with BIST execution and no Ethernet

switch reset
BTS model:
FAULT ANALYSIS
This alarm indicates an RIPM-USER core restart with a BIST execution.
The IBOS has not requested an Ethernet switch reset.

411-9001-103 18.06 20 January 2010
379

BSC defense
None.
None.
TROUBLESHOOTING

execution nor Ethernet switch reset)
Equipment:
RIPM-USER core
Source:
(15794190) Reset requested by IBOS with no BIST execution nor Ethernet

switch reset
BTS model:
FAULT ANALYSIS
This alarm indicates that the active IPM-USER board has been reset
without a BIST execution. The IBOS has not requested an Ethernet switch
reset.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.57 RIPM-USER core (source: Restart after TML commissioning)

Equipment:
RIPM-USER core
Source:
(15794191) Restart after TML commissioning
BTS model:

411-9001-103 18.06 20 January 2010
380
FAULT ANALYSIS
This alarm indicates an RIPM-USER restart by the TML, after
commissioning.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.58 RIPM-USER core (source: Connection with IGM has been lost
(no status received for 7 keep-alive periods))
Equipment:
RIPM-USER core
Source:
(15794192) Connection with IGM has been lost (no status received for 7
keep-alive periods)
BTS model:
FAULT ANALYSIS
This alarm indicates that the connection with IGM has been lost (no status
received for 7 keep-alive periods).

BSC defense
None.
None.
TROUBLESHOOTING
2.9.59 RIPM-USER core (source: No response to DHCP requests for

15 minutes)
Equipment:
RIPM-USER core

411-9001-103 18.06 20 January 2010
Source:
(15794195) No response to DHCP requests for 15 minutes
BTS model:
381
FAULT ANALYSIS
This alarm indicates no response to DHCP requests for 15 minutes.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.60 RIPM-USER core (source: No response to DNS requests for 15

minutes)
Equipment:
RIPM-USER core
Source:
(15794196) No response to DNS requests for 15 minutes
BTS model:
FAULT ANALYSIS
This alarm indicates no response to DNS requests for 15 minutes.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.61 RIPM-USER core (source: Debug)

Equipment:
RIPM-USER core

411-9001-103 18.06 20 January 2010
382
Source:
(15794209) Debug
BTS model:
FAULT ANALYSIS
This alarm indicates that a message sent by the IBOS or IPG is not
acknowledged by the RIPM-USER.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.62 RIPM-USER core (source: Soft)

Equipment:
RIPM-USER core
Source:
(15794210) Soft
BTS model:
FAULT ANALYSIS
This alarm indicates that a trap occurs. The RIPM-USER sends the
post-mortem dump zone to the IBOS.

BSC defense
None.
None.
TROUBLESHOOTING

411-9001-103 18.06 20 January 2010
383
2.9.63 RIPM-USER core (source: Reset requested by active with BIST

execution)
Equipment:
RIPM-USER core
Source:
(15794193) Reset requested by active with BIST execution
BTS model:
FAULT ANALYSIS
This alarm indicates an RIPM-USER passive core restart with a BIST
execution.

BSC defense
None.
None.
TROUBLESHOOTING
2.9.64 RIPM-USER core (source: Reset requested by active with no

BIST execution)
Equipment:
RIPM-USER core
Source:
(15794194) Reset requested by active with no BIST execution
BTS model:
FAULT ANALYSIS
This alarm indicates an RIPM-USER passive core restart, without a BIST
execution.

BSC defense
None.
None.

411-9001-103 18.06 20 January 2010
384
TROUBLESHOOTING
2.9.65 Tx Filters (source: VSWR level 2)

Fault number 1060
Equipment:
Tx Filter
Source:
(7536642) VSWR level 2
BTS model:
S8000 Outdoor + S8000 Indoor + S8003
FAULT ANALYSIS
This alarm indicates that an abnormal VSWR level has been detected at
the combiner output. The radio link is still operating.
BSC defense
None.
None.
TROUBLESHOOTING
Step
Action
Preliminary checks



not clear it. process the problem on the btsSiteManager
object.
alarm persists.

411-9001-103 18.06 20 January 2010
385
Check that the alarm on the Tx Filter is valid, by performing

a "Display hardware configuration" command on the
If the state of the "VSWR" equipment is "failed", the fault is

If the state of the "VSWR" equipment is "working", the fault is

On-site maintenance from the OMC-R
Check the cabling between the associated Tx Filter and the

antenna.
If it is correct, go to step 4.
If it is not correct, replace it (Shop Replaceable Unit). Go to
step 5.
In the case of alarms with source: level 2, and source: level

3, replace the associated Tx Filter (Field Replaceable Unit).
Refer to 411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting).
Additional checks
Check the alarm state in the "Current Alarm list" window.

Check the state of the replaced equipment by performing

If the state of the "VSWR" equipment is still "failed", call the

manufacturer.
If the state of the "VSWR" equipment is "working", go to step

7.
Clear the alarm.

--End--

411-9001-103 18.06 20 January 2010
386
Fault number:
1061
Abis mapping issue on a TDMA
Type
FAULT ANALYSIS
The alarm 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. Refer to the description of fault number 1063 in 2.11 Attribute
value change: 1063 (S8000, S8002, S8003, and S8006 BTS) (page 386)
The Managed Object (MO) is: transceiver
List of causes:
15: Lack of Abis resources

0: Higher priority TDMA not mapped on Abis
TROUBLESHOOTING
2.11 Attribute value change: 1063 (S8000, S8002, S8003, and S8006
BTS)
Fault number:
1063
TRX allocation for a TDMA
Type
FAULT ANALYSIS

411-9001-103 18.06 20 January 2010
387
An attribute value change 1063 (S8000, S8002, S8003, S8006) 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.
List of causes of the configuration in degraded mode:
(0): "Lack of Abis resources"
(3) "TRX insufficient EDGE capability" when TRX is not able to

respond to 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 <> 2
(2) "Site unsufficient number of DS0" when site is not able to respond
to the TDMA DS0 request
TROUBLESHOOTING
This problem is associated with a bad configuration of EDGE backhaul.
If the cause is (1) "Site not supporting Edge", check the PROM version
of the GTW board.
If the cause is (2) "Site unsufficient number of DS0", check the radio
site mask according to engineering rules.
If the cause is (3) "TRX insufficient EDGE capability", check if there

is an EDRX available on the cell.
Fault number:
1067
Type
equipmentAlarm
The fault number 1067 accepts causes and equipment wordings

corresponding to the eDRX, DRX, DRX-ND3, eDRX2, ePA, HePA, CMCF
phase 1 and CMCF phase 2 fault causes.
The fault numbers 1060 (transient) and 1067 (begin/end) accept these
items of equipment. The causes wording are the same for all DRX types
fault causes.

411-9001-103 18.06 20 January 2010
388
In the case of an equipment fault or a missing item of equipment, 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 hopping
law, for example).
The following table indicates all the sources of the fault number 1067 for
the S8000 Outdoor and Indoor BTSs with the BCF or CBCF, for the S8002
BTSs, for the S8003 BTSs, and for the S8006 BTSs. For more information
on each source, refer to the indicated paragraph to know the corrective
Table 9
Source No.
Source wording
S8000
Indoor
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
S8000
Outdoor
CBCF
BCF
Paragraph
BTS synchronization
3342340
SYNO clock not

locked on the
network
x x
2.12.16 BTS
SYNCHRONIZ
ATION (source:
SYNO clock
not locked on
the network)
(page 441)
3342341
Synchro not locked

because OCVXO
is KO
2.12.17 BTS
synchronization
(source:
Synchro not
locked because
OCVXO is
KO) (page
448)
3342342
Synchro not locked

because PCM is
not stable
3342343
GPS synchronizati
on unavailable
x x

411-9001-103 18.06 20 January 2010
2.12.18 BTS
synchronization
(source: GPS
synchronization
unavailable)
(page 451)
389
Table 9
Source No.
Source wording
S8000
Indoor
BCF
S8000
Outdoor
CBCF
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
Paragraph
3342344
Loss of GPS
synchronization
x x
2.12.19 BTS
synchronization
(source: Loss
of GPS sync
hronization)
(page 456)
3342345
Lack of GPS
synchronization
accuracy
x x
2.12.20 BTS
SYNCHRONIZ
ATION (source:
Lack of GPS
synchronization
accuracy)
(page 461)
3342346
Master synchroniz
ation unavailable
x x
2.12.21 BTS
SYNCHRON
IZATION (so
urce: Master
synchronization
unavailable)
(page 466)
3342347
Loss of Master
GSM time
x x
2.12.22 BTS
SYNCHRONIZ
ATION (source:
Loss of master
GSM time)
(page 471)
3342348
Loss of Master SY
x x
2.12.23 BTS
SYNCHRONIZ
ATION (source:
Loss of master
SY) (page
475)
ACU cooling system

5505031
Cooler fault
ALCO board

411-9001-103 18.06 20 January 2010
2.12.1 ACU
climatic unit
(source: Cooler
fault) (page
413)
390
Table 9
Source No.
S8000
Indoor
Source wording
BCF
4390913
Major fault
CBCF
S8000
Outdoor
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
Paragraph
2.12.2 ALCO
board (source:
Major fault)
(page 416)
Battery cabinet
5832705
Over temperature
2.12.3 Battery
cabinet
(source: Over
temperature)
(page 419)
5832706
DC power fault
2.12.4 Battery
cabinet (sour
ce: DC power
fault) (page
422)
5832707
Doors
2.12.5 Battery
cabinet (sou
rce: Doors)
(page 425)
5832708
AC power fault
5832709
Surge protector
BCF cabinet door

6291457
BCF cabinet door

contact detection
2.12.6 BCF
cabinet door
contact(source:
BCF cabinet
door contact
detection)
(page 429)
2.12.7 BCF
cabinet fan
(source: BCF
cabinet fan
fault) (page
433)
BCF cabinet fan

6356993
BCF cabinet fan
BCF power supply

411-9001-103 18.06 20 January 2010
391
Table 9
Source No.
S8000
Indoor
Source wording
BCF
5373953
Volt
CBCF
S8000
Outdoor
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
Paragraph
2.12.8 BCF
power supply
(source: Volt)
(page 435)
Battery Remote Controller

(BRC)
6553601
Manual switch on
battery power
2.12.9 BRC
(source:
Manual switch
on battery
power) (page
438)
6553602
Automatic switch
on battery power
2.12.10 BRC
(source:
Automatic
switch on
battery power)
(page 438)
6553603
Manual switch on
main power
2.12.11 BRC
(source: Man
ual switch on
main power)
(page 438)
6553604
Automatic switch
on main power
2.12.12 BRC
(source:
Automatic
switch on main
power) (page
438)
2.12.13 BRC
(source:
Battery failure)
(page 439)
Battery Remote Controller

(BRC)
6553605
Battery Failure

411-9001-103 18.06 20 January 2010
392
Table 9
Source No.
S8000
Indoor
Source wording
BCF
S8000
Outdoor
CBCF
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
Paragraph
6553606
Monitored battery
not present
2.12.14 BRC
(source:
Monitored
battery not
present) (page
440)
6553607
Internal Inconsiste
ncy
2.12.15 BRC
(source:
Internal
inconsistency)
(page 441)
Cabinet door
5898241
Door contact
detection
x x
2.12.24
Cabinet
door (source:
Door contact
detection)
(page 479)
Cavity
8388609
Cavity out of
service
2.12.25 Cavity
(source: Cavity
out of service)
(page 483)
8388610
Cavity parked after

tuning fault (min
not found)
2.12.26 Cavity
(source: Cavity
parked after
tuning fault
(min not
found)) (page
485)
8388611
Loss of cavity
initialization
2.12.27 Cavity
(source: Loss
of cavity
initialization)
(page 487)
8386612
Nack answer from

cavity
2.12.28 Cavity
(source: Nack
answer from
cavity) (page
489)

411-9001-103 18.06 20 January 2010
393
Table 9
Source No.
Source wording
S8000
Indoor
BCF
S8000
Outdoor
CBCF
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
Paragraph
8388613
Cavity parked after

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

tuning fault (tuning
detector problem)
2.12.30 Cavity
(source: Cavity
parked after
tuning fault
(tuning detector
problem))
(page 492)
8388615
Internal software
problem
2.12.31 Cavity
(source: Inte
rnal software
problem)
(page 494)
Cavity combiner
8323073
Power supply
2.12.32 Cavity
combiner
(source: Power
supply) (page
496)
8323074
Tuning detector
fault
2.12.33 Cavity
combiner
(source:
Tuning detector
fault) (page
498)
8323076
Link NOK
2.12.34 Cavity
combiner
(source: Link
NOK) (page
500)
C-DACS climatic system

411-9001-103 18.06 20 January 2010
394
Table 9
Source No.
Source wording
S8000
Indoor
BCF
S8000
Outdoor
CBCF
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
Paragraph
7929857
Dirty filter
2.12.35
C-DACS
climatic system
(source: Dirty
filter) (page
502)
7929858
DACS failed
2.12.36
C-DACS
climatic system
(source: DACS
failed) (page
504)
CMCF
CMCF ph 1
CMCF ph 2
9502721
12779521
12845057
Major fault
x x
9502729
12779529
12845065
MCF_MCF
x x
2.12.37 CMCF
board (source:
MCF_MCF)
(page 507)
9568250
12845050
12910586
Slave downloading
error
x x
2.12.38
CMCF board
(source: Slave
downloading
error) (page
510)
12779537
12845073
duplex inhibited:
active board
is background
downloaded
x x
12779538
12845074
CMCF ACT DUPL

EX INHIBITED
x x
2.12.39 CMCF
board (source:
CMCF_ACT
_DUPLEX_I
NHIBITED)
(page 512)
CMCF ph 1
CMCF ph 2

411-9001-103 18.06 20 January 2010
395
Table 9
Source No.
S8000
Indoor
Source wording
BCF
S8000
Outdoor
CBCF
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
Paragraph
CMCF ACT ICST
x x
2.12.40 CMCF
board (source:
CMCF_ACT_
ICST) (page
515)
12779536
duplex inhibited:
EDGE in duplex
mix chain
x x
12779540
duplex inhibited:
feature not
supported on
CMCF phase 1
x x
2.12.41 CMCF
board (source:
Duplex inhibite
d: feature not
supported on
CMCF phase
1) (page 517)
Slave downloading
error
12779539
12845075
CMCF ph 1
CPCMI board
9633786
Combiner duplexer or H2 LNA

5570561
LNA fault
x x
2.12.42
Combiner
duplexer LNA
or combiner H2
LNA (source:
LNA fault)
(page 520)
x x
2.12.43 Comb
iner duplexer
VSWR or
combiner H2
VSWR (source:
VSWR level 1)
(page 524)
Combiner duplexer or H2 VSWR

5636097
VSWR level 1

411-9001-103 18.06 20 January 2010
396
Table 9
Source No.
S8000
Indoor
S8000
Outdoor
BCF
CBCF
BCF
CBCF
S8
0
0
2
Source wording
S8 S8
0 0
0 0
3 6
Paragraph
5636098
VSWR level 2
x x
2.12.44 Comb
iner duplexer
VSWR or
combiner H2
VSWR (source:
VSWR level 2)
(page 524)
5636099
VSWR level 3
x x
2.12.45 Comb
iner duplexer
VSWR or
combiner H2
VSWR (source:
VSWR level 3)
(page 525)
2.12.46
Combiner H4D
LNA (source:
LNA fault)
(page 528)
Combiner H4D LNA

7405569
LNA fault
Combiner H4D VSWR

7471105
VSWR level 1
2.12.47
Combiner H4D
VSWR (source:
VSWR level 1)
(page 532)
7471106
VSWR level 2
2.12.48
Combiner H4D
VSWR (source:
VSWR level 2)
(page 534)
7471107
VSWR level 3
2.12.49
Combiner H4D
VSWR (source:
VSWR level 3)
(page 536)
Compact distribution system

411-9001-103 18.06 20 January 2010
397
Table 9
Source No.
S8000
Indoor
Source wording
BCF
7995393
S8000
Outdoor
CBCF
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
Main breaker
Paragraph
2.12.50
Compact distr
ibution system
(source: Main
breaker) (page
538)
CPCMI board
9568257
Major
x x
2.12.51
CPCMI board
(source:
Major) (page
541)
9633786
Slave downloading
error
x x
2.12.52
CPCMI board
(source: Slave
downloading
error) (page
541)
CSWM boards
4259849
Fault on activepassive CSWM

link or on passive
CSWM
2.12.53
CSWM board(s
ource: Fault on
active-passive
CSWM link
or on passive
CSWM) (page
544)
4325370
Slave downloading
error
2.12.54
CSWM board
(source: Slave
downloading
error) (page
547)
DACS climatic system

7864321
Dirty filter

411-9001-103 18.06 20 January 2010
2.12.55 DACS
climatic system
(source: Dirty
filter) (page
549)
398
Table 9
Source No.
S8000
Indoor
Source wording
BCF
7864322
S8000
Outdoor
CBCF
DACS failed
S8
0
0
2
S8 S8
0 0
0 0
3 6
Paragraph
BCF
CBCF
2.12.61 DRX
or DRX-ND3
modules
(source: HePA
not supported)
(page 570)
x x
2.12.60 DRX
or DRX-ND3
modules
(source: Abis
satellite not
supported DRX
(ND3)) (page
569)
x x
2.12.65 DRX
or eDRX or
DRX-ND3
modules
(source: RX
fault) (page
585)
2.12.56 DACS
climatic system
(source: DACS
failed) (page
551)
2.12.57 Distri
bution system
(source: Main
breaker) (page
557)
Distribution system
5767169
Main breaker
DRX
9437212
HePA not
supported
DRX, DRX ND3

9437214
12976158
Abis satellite not

supported DRX
DRX
eDRX
DRX ND3
9437185
12582913
12976129
RX fault

411-9001-103 18.06 20 January 2010
399
Table 9
Source No.
S8000
Indoor
S8000
Outdoor
BCF
CBCF
BCF
CBCF
S8
0
0
2
Source wording
S8 S8
0 0
0 0
3 6
Paragraph
9437190
12582918
12976134
BBFILTER ASIC
fault
x x
2.12.63 DRX
or eDRX or
DRX-ND3 mod
ules (source:
BBFILTER
ASIC fault)
(page 576)
9437193
12582921
12976137
Self test failed
x x
2.12.78 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: Self
test failed)
(page 609)
9437194
12582922
12976138
Major fault on TX
x x
2.12.72 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: Major
fault on TX)
(page 597)
9437206
12582934
12976150
DRX link
x x
2.12.69 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: DRX
link) (page
591)
9437211
12582939
12976155
(H) (e) PA
configuration not
supported
x x

411-9001-103 18.06 20 January 2010
400
Table 9
Source No.
S8000
Indoor
S8000
Outdoor
BCF
CBCF
BCF
CBCF
S8
0
0
2
Source wording
S8 S8
0 0
0 0
3 6
Paragraph
9437216
12582944
12976160
The TX has not

acknowledged the
power consign
request
x x
2.12.64 DRX
or eDRX or
DRX-ND3
modules
(source: The
TX has not
acknowledged
the power
consign
request) (page
580)
9437217
12582945
12976161
PA DRX control
loop fault
x x
2.12.74 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: PA
DRX control
loop fault)
(page 602)
9437218
12582946
12976162
DRX reset by BCF

after message non
acknowledgement
x x
2.12.73 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: Nack
answer) (page
602)
9437219
12582947
12976163
DRX link NOK

after reset
requested by BSC
x x
2.12.70 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: DRX
reset by BSC)
(page 596)

411-9001-103 18.06 20 January 2010
401
Table 9
Source No.
S8000
Indoor
S8000
Outdoor
BCF
CBCF
BCF
CBCF
S8
0
0
2
Source wording
S8 S8
0 0
0 0
3 6
Paragraph
9502719
12648447
13041663
TRX not anymore

configured
x x
2.12.79 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: TRX
not anymore
configured)
(page 613)
9437211
or
12582939
PA configuration
exceeded
2.12.62 DRX
or DRX-ND3
modules
(source: PA
configuration
exceeded)
(page 573)
Post-mortem dump
zone 3
x x
2.12.75 DRX
or eDRX or
DRX-ND3 or
eDRX2 mod
ules (source:
Post-mortem
dump zone 3)
(page 607)
S8
0
0
2
S8 S8
0 0
0 0
3 6
9437427 or
12583155 or
12976371
Table 10
Fault number 1067 sources (continued)
Source No.
Source
wording
S8000
Indoor
BCF
CBCF
S8000
Outdoor
BCF
CBCF
DRX
eDRX
DRX ND3

411-9001-103 18.06 20 January 2010
Paragraph
402
Table 10
Fault number 1067 sources (continued) (contd.)
Source No.
Source
wording
S8000
Indoor
S8000
Outdoor
BCF
CBCF
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
Paragraph
9437456
or
12583184
or
12976400
BCCH first config

failed
x x
2.12.67 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: BCCH
first config
failed) (page
589)
9437457
or
12583185
or
12976401
BCCH second
config failed
x x
2.12.68 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: BCCH
second config
failed) (page
590)
9437472
or
12583200
or
12976416
SACCH first config

failed
x x
2.12.76 DRX
or eDRX or
DRX-ND3 or
eDRX2 mod
ules (source:
SACCH first
config failed)
(page 607)
9437473
or
12583201
or
12976417
SACCH second
config failed
x x
2.12.77 DRX
or eDRX or
DRX-ND3
or eDRX2
modules (sou
rce: SACCH
second config
failed) (page
608)

411-9001-103 18.06 20 January 2010
403
Table 10
Source No.
Source
wording
S8000
Indoor
S8000
Outdoor
BCF
CBCF
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
Paragraph
9437488
or
12583216
or
12976432
L1M first config

failed
x x
2.12.66 DRX
or eDRX or
DRX-ND3
modules
(source: L1M
first config
failed) (page
589)
9437489
or
12583217
or
12976433
L1M second config

failed
x x
2.12.71 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: L1M
second config
failed) (page
597)
x x
2.12.58 DRX
or DRX-ND3
diversity
reception
chain (source:
Software
detection)
(page 560)
x x
2.12.59 DRX
or DRX-ND3
main reception
chain (source:
Software
detection)
(page 565)
DRX diversity reception chain

6946817
Software detection
DRX main reception chain

6881281
Software detection
DSC boards
4456449
Major fault

411-9001-103 18.06 20 January 2010
2.12.80 DSC
boards (source:
Major fault)
(page 616)
404
Table 10
Source No.
4456453
Source
wording
Channel_HSCX
S8000
Indoor
BCF
S8000
Outdoor
CBCF
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
Paragraph
2.12.81 DSC
boards (source:
Channel_HSC
X) (page 618)
eDRX2
15204361
Self test failed
2.12.78 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: Self
test failed)
(page 609)
15204362
Major fault on TX
2.12.72 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: Major
fault on TX)
(page 597)
15204374
DRX link
2.12.69 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: DRX
link) (page
591)
15204374
DRX link
2.12.69 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: DRX
link) (page
591)

411-9001-103 18.06 20 January 2010
405
Table 10
Source No.
Source
wording
S8000
Indoor
BCF
S8000
Outdoor
CBCF
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
Paragraph
15204385
PA DRX control
loop fault
2.12.73 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: Nack
answer) (page
602)
15204386
DRX reset by BCF

after message non
acknowledgement
2.12.73 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: Nack
answer) (page
602)
15204387
DRX link NOK

after reset
requested by BSC
2.12.70 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: DRX
reset by BSC)
(page 596)
15269887
TRX not anymore

configured
x x
2.12.79 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: TRX
not anymore
configured)
(page 613)
15204624
BCCH first config

failed

411-9001-103 18.06 20 January 2010
2.12.67 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: BCCH
first config
failed) (page
589)
406
Table 10
Source No.
Source
wording
S8000
Indoor
BCF
S8000
Outdoor
CBCF
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
Paragraph
15204625
BCCHsecond
config failed
2.12.68 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: BCCH
second config
failed) (page
590)
15204640
SACCH first config

failed
2.12.76 DRX
or eDRX or
DRX-ND3 or
eDRX2 mod
ules (source:
SACCH first
config failed)
(page 607)
15204641
SACCH second
config failed
2.12.77 DRX
or eDRX or
DRX-ND3
or eDRX2
modules (sou
rce: SACCH
second config
failed) (page
608)
15204656
L1M first config

failed
2.12.66 DRX
or eDRX or
DRX-ND3
modules
(source: L1M
first config
failed) (page
589)

411-9001-103 18.06 20 January 2010
407
Table 10
Source
wording
Source No.
S8000
Indoor
BCF
S8000
Outdoor
CBCF
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
Paragraph
15204657
L1M second config

failed
2.12.71 DRX
or eDRX or
DRX-ND3
or eDRX2
modules
(source: L1M
second config
failed) (page
597)
15204595
Post-mortem dump
zone 3
2.12.75 DRX
or eDRX or
DRX-ND3 or
eDRX2 mod
ules (source:
Post-mortem
dump zone 3)
(page 607)
x x
2.12.95 Not
protected
alarm (source:
Alarm) (page
646)
x x
2.12.82
External
alarm (source:
Alarm) (page
621)
Not protected alarm

3735553
Alarm
External alarm
x
7274497
Fan of the base cabinet

6225921
Cabinet fan fault
F-type converters

411-9001-103 18.06 20 January 2010
2.12.83 Fan
of the base ca
binet (source:
Cabinet fan
fault) (page
621)
408
Table 10
S8000
Outdoor
BCF
CBCF
BCF
CBCF
Volt
Major fault on
GTW
Source No.
5308417
S8000
Indoor
S8
0
0
2
Source
wording
S8 S8
0 0
0 0
3 6
x x
Paragraph
2.12.84 F-type
converters
(source: Volt)
(page 624)
GTW boards
4587521
2.12.85 GTW
boards (source:
Major fault on
GTW) (page
628)
Internal batteries
5439489
Battery disconnect
ed
2.12.94 Lightn
ing protector
(source:
Lightning
protection
fault) (page
643)
2.12.86 Intern
al batteries (s
ource: Battery
disconnected)
(page 631)
Lightning protector
6160385
Lightning
protection fault
Output Rx-splitter D
9764865
Over current
x x
2.12.96 Output
Rx-splitter D
(source: Over
current) (page
646)
Over current
x x
2.12.97 Output
Rx-splitter M
(source: Over
current) (page
649)
Output
Rx-splitter
M
9699329

411-9001-103 18.06 20 January 2010
409
Table 10
S8000
Indoor
S8000
Outdoor
S8 S8
0 0
0 0
3 6
x x
BCF
CBCF
BCF
CBCF
S8
0
0
2
PCM
Major fault on
PCMI
6815745
or
12648449
or
12713985
Hardware
x x
2.12.100
Power ampli
fiers (source:
Hardware)
(page 652)
6815746
or
12648450
or
12713986
DRX and PA
connection
x x
2.12.101
Power ampli
fiers (source:
DRX and PA
connection)
(page 658)
6815747
or
12648451
or
12713987
High temp
x x
2.12.102 Po
wer amplifiers
(source: High
temperature )
(page 663)
6815748
or
12648452
or
12713988
High Current
x x
2.12.103 Po
wer amplifiers
(source: High
Current )
(page 667)
6815750
or
12648454
or
12713990
PA_PSDW
x x
2.12.104
Power ampli
fiers (source:
PA_PSDW )
(page 671)
Source
wording
Source No.
Paragraph
PCM
6488065
2.12.98 PCM
(source: PCM)
(page 652)
PCMI boards
4521985
2.12.99 PCMI
boards (source:
Major fault on
PCMI) (page
652)
PA or ePA
or HePA
PA

411-9001-103 18.06 20 January 2010
410
Table 10
Source No.
6815751
Source
wording
VSWR fault
detected by PA
S8000
Indoor
S8000
Outdoor
S8 S8
0 0
0 0
3 6
BCF
CBCF
BCF
CBCF
S8
0
0
2
x x
2.12.105
Power ampli
fiers (source:
VSWR fault
detected by
PA) (page
675)
Paragraph
RECAL board
9633793
Major
x x
2.12.106
RECAL
board (source:
Major) (page
676)
9699322
Slave downloading
error
x x
2.12.107
RECAL board
(source: Slave
downloading
error) (page
679)
Rectifiers
5242881
AC fault
2.12.108
Rectifiers
(source: AC
fault) (page
682)
5242882
DC fault
2.12.109
Rectifiers
(source: DC
fault) (page
686)
5242883
Over temperature
2.12.110
Rectifiers
(source: Over
temperature)
(page 688)
5242884
External battery
level 1

411-9001-103 18.06 20 January 2010
2.12.111
Rectifiers (s
ource: External
battery level 1)
(page 691)
411
Table 10
Source No.
Source
wording
S8000
Indoor
S8000
Outdoor
BCF
CBCF
BCF
CBCF
S8
0
0
2
S8 S8
0 0
0 0
3 6
x
Paragraph
5242885
PCU protective
5242886
Battery on
discharges
Major fault on
SYNC
LNA Fault
7536642
VSWR level 2
2.12.120 Tx
Filters (source:
VSWR level 2)
(page 709)
7536643
VSWR level 3
2.12.121 Tx
Filters (source:
VSWR level 3)
(page 710)
User alarm
2.12.112
Rectifiers
(source: PCU
protective)
(page 693)
2.12.113
Rectifiers
(source:
Battery on
discharges)
(page 697)
SYNC boards
4325377
2.12.119
SYNC boards
(source:
Major fault on
SYNC) (page
707)
Rx Filter
7602177
2.12.118 Rx
Filter (source:
LNA fault)
(page 704)
Tx Filters
User system
5701633

411-9001-103 18.06 20 January 2010
412
Table 11
Fault number 1067 sources (IP)
Source No.
Cause
wording
S8000
Indoor
BC CB
F CF
S8000
Outd
oor
S8
0
0
BC CB 2
F CF
S8
0
0
3
S8
0
0
6
Paragraph
IPM-USER core
15728672
IPM BIST failed

(source: IPM BIST failed)
(page 639)
15728675
IPM temperature

(source: IPM temperature)
(page 640)
15728688
DAC unable to loc

k, synchronisation
not possible

(source: DAC unable to
lock, synchronization not
possible) (page 641)
RIPM-USER core
15794208
IPM BIST failed

(source: IPM BIST failed)
(page 699)
15794211
IPM temperature

(source: IPM temperature)
(page 700)
15794224
DAC unable to loc

k, synchronisation
not possible

(source: DAC unable to
lock, synchronization not
possible) (page 701)
15794241
No link with
passive

(source: No link with passive)
(page 703)
IP synchro
15859968
Unable to lock on
IP synchronization
2.12.87 IP synchro (source:

Unable to lock on IP
synchronization) (page 634)
15859969
Not enough
synchronization
packets have been
received.
2.12.88 IP synchro (source:

Not enough synchronization
packets have been received)
(page 636)
Ethernet switch

411-9001-103 18.06 20 January 2010
Cause
wording
Source No.
15925760
S8000
Indoor
BC CB
F CF
x
Ethernet switch is
disconnected on
user port
S8000
Outd
oor
S8
0
0
BC CB 2
F CF
S8
0
0
3
S8
0
0
6
413
Paragraph
Ethernet switch (source:

Ethernet switch is
disconnected on used port)
IPM-USER commissioning
15663140
Only one IBOS

commissioned at
IPM
2.12.89 IPM-USER
commissioning (source:
Only one IBOS commissioned
at IPM) (page 637)
15663141
DNS resolution
has failed for at
least one IBOS
2.12.90 IPM-USER
commissioning (source: DNS
resolution has failed for at
least one IBOS) (page 638)
2.12.1 ACU climatic unit (source: Cooler fault)

Fault number 1067
Equipment:
Cooler system
Source:
(5505031) Cooler fault
BTS model:
S8000 Outdoor
FAULT ANALYSIS
This alarm is detected by the ALCO or RECAL board.
It is an "OR" function of all the alarms that are liable to occur on the
climatic unit.
As long as the temperature of the (H)(e)PAs is lower than 60C

(140F), there is no BSC defense action.
As soon as the temperature of the (H)(e)PAs is higher than 60C,

there is a voluntary cut of the (H)(e)PAs. Then the BSC unconfigures
the transceiverEquipment and transceiver objects, and possibly the
btsSiteManager and bts objects.

411-9001-103 18.06 20 January 2010
414
CAUTION
The service is progressively lost.
CAUTION
Intervention on the site must be immediate.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).
and process the problem so that the btsSiteManager

process the problem so that the btsSiteManager object
becomes "enabled".

not clear it. Wait until the state of the btsSiteManager
object becomes "enabled", "disabled-dependency", or
"disabled-failed".
alarm persists.

411-9001-103 18.06 20 January 2010
415
Check that the alarm on the ACU climatic units is valid, by

If the state of a "cooler system" equipment is "failed", the fault

is confirmed. Go to step 3.
If the state of the "cooler system" equipment is "working", the

fault is not confirmed. Go to step 8.
On-site maintenance
Check that the main breaker, the climatic system circuit breaker
and the circuit breaker L2/CB2 are in the "I" position. If they are
not, put them in the "I" position.
Remove the filter of the faulty ACU (see 411-9001-048 (Nortel

GSM BTS S8000/S8003 Troubleshooting)).
Reset the two internal AC and DC circuit breakers of the ACU

(located behind the filter) once.
If the circuit breakers can not be reset, replace the climatic

unit (Field Replaceable Unit). It can be replaced either by
another ACU or by a DACS.
To replace the climatic unit with another ACU, refer
Troubleshooting).
To replace the climatic unit with a DACS, refer to
411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting) to remove the ACU, and to install the
DACS.
Go to step 6.
If the circuit breakers can be reset, measure the ambient

temperature of the cabinet.
If the temperature is between -40C (-40F) and +50C
(+122F), there is an internal problem in the climatic unit.
Replace the climatic unit (Field Replaceable Unit). It can
be replaced either by another ACU or by a DACS.
To replace the climatic unit with another ACU, refer

Troubleshooting).
To replace the climatic unit with a DACS, refer to

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

411-9001-103 18.06 20 January 2010
416
Troubleshooting) to remove the ACU and to install the

DACS.
Go to step 6.
If the temperature is lower than -40C or higher than
+50C, wait for the system to return to a normal
temperature. The cabinet will restart automatically,
triggered by the thermostats.
The high temperature thermostat triggers the cabinet

start-up if the temperature is lower than 61C
(+141.8F).
The low temperature thermostat triggers the cabinet

start-up if the temperature is upper than 9C
(+48.2F).
Go to step 6.
Additional checks

Check the state of the ACU climatic unit by performing a "Display

hardware configuration" command on the btsSiteManager object.
If the state of the "cooler system" equipment is still "failed",

call the manufacturer.
If the state of the "cooler system" equipment is "working", go

to step 8.
Clear the alarm.

--End--
2.12.2 ALCO board (source: Major fault)

Fault number 1067
Equipment:
ALCO
Source:
(4390913) Major fault
BTS model:

411-9001-103 18.06 20 January 2010
417
FAULT ANALYSIS
This alarm indicates an ALCO board failure that may be due to the fuse on
the front panel of the BCF, the power supply voltage on the PWR cable or
the cabling between the BCF and the board.

BSC defense
None.
Impact on the service The BTS no longer supervises all the items of
equipment linked to the ALCO board (distribution system, rectifiers, F-type
converters, BCF power supplies, internal batteries, climatic system, LNA,
VSWR, door contact, lightning protection and battery cabinet).
The S8000 BTS service is no longer supervised, as the BTS cannot inform
the BSC.
CAUTION
The service can be lost, even though the OMC-R does not
indicate any loss.
CAUTION
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
418

Procedures)).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the ALCO board is valid, by

If the state of the "ALCO" equipment is "failed", the fault is

If the state of the "ALCO" equipment is "working", the fault is

On-site maintenance
Check the ALCO board fuse on the BCF front panel for the
S8000 Outdoor or the ALCO/BCF circuit breaker for the S8000
Indoor.
If it is not correct, replace it (Shop Replaceable Unit).
Check the power supply voltage on the PWR cable by measuring

with a voltmeter.

411-9001-103 18.06 20 January 2010
419
If the voltage is lower than -58V and higher than -40V,

replace the ALCO board (Field Replaceable Unit).
Troubleshooting). Go to step 5.
If the voltage is between -58V and -40V, replace the O and

M cable (Shop Replaceable Unit) between the BCF and the
ALCO board. Go to step 5.
Additional checks

Check the state of the ALCO board by performing a "Display

If the state of the "ALCO" equipment is still "failed", call the

manufacturer.
If the state of the "ALCO" equipment is "working", go to step

7.
Clear the alarm.

--End--
2.12.3 Battery cabinet (source: Over temperature)

Fault number 1067
Equipment:
Battery cabinet
Source:
(5832705) Over temperature
BTS model:
S8000 Outdoor
FAULT ANALYSIS
It is triggered by a problem with the climatic unit of the battery cabinet:
the temperature of the battery cabinet has become either too high (over
+ 65C), or too low (below + 5C).

BSC defense
None.
411-9001-103 18.06 20 January 2010
420
None.
CAUTION
Intervene within 24 hours.
TROUBLESHOOTING
Step
Action
Preliminary checks



an object whose state is "disabled-failed" and process the
problem in order that the btsSiteManager object becomes
"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, process the problem on

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

411-9001-105 (Nortel GSM BSS Fault Clearing Advanced Maintenance Procedures)).
If a pcmCircuit object is "disabled-failed":

Look for a fault number concerning PCMs (see



becomes "enabled".


411-9001-103 18.06 20 January 2010
421

"disabled-failed".
alarm persists.
Check that the alarm on the battery cabinet is valid, by

If the state of the "battery cabinet" equipment is "failed", the

fault is confirmed. Go to step 4.
If the state of the "battery cabinet" equipment is "working", the

On-site maintenance
Check the state of the mains power supply on the operator box.
If the mains power supply is correct, it is a PCM fault. Refer

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

and go to step 5.
Replace the heating and ventilation unit of the battery cabinet

(Field Replaceable Unit). Refer to 411-9001-048 (Nortel GSM
BTS S8000/S8003 Troubleshooting). Go to step 5.
Additional checks

Check the state of the battery cabinet by performing a "Display

If the state of the "battery cabinet" equipment is still "failed",

If the state of the "battery cabinet" equipment is "working",

go to step 7.

411-9001-103 18.06 20 January 2010
422
Clear the alarm.

--End--
2.12.4 Battery cabinet (source: DC power fault)

Fault number 1067
Equipment:
Battery cabinet
Source:
(5832706) DC power fault
BTS model:
S8000 Outdoor
FAULT ANALYSIS
This alarm is detected by the ALCO or RECAL board, and occurs when
there is a power supply problem of the battery cabinet.
If the BTS operates on its external batteries, there are no internal batteries.

BSC defense If the S8000 BTS operates on batteries, there is no BSC
defense action until the batteries reach the threshold level. In this case,
the BSC unconfigures the btsSiteManager object. The btsSiteManager,
bts and transceiverEquipment objects change their state: they become
"disabled-dependency". The pcmCircuit of the Abis link becomes
"disabled-failed".
CAUTION
Intervention on the site must be immediate. There is a risk of
site loss.
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
423

"enabled".






becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the battery cabinet is valid, by




411-9001-103 18.06 20 January 2010
424

On-site maintenance
If the alarm appears and there are no external batteries, go to

step 4. Otherwise, go to step 6.
Check the "external battery cabinet" parameter by performing the

"Display" command on the btsSiteManager object.
If the parameter is "present", set its value to "absent".

If the parameter is "absent", go to step 10.

BSS Fault Clearing - Advanced Maintenance Procedures)).

and go to step 6.
Check the state of the circuit breakers of the battery cabinet.
If the circuit breakers of the battery cabinet are not in the "I"
position, put the DC circuit breaker in the "I" position.
In the case of a new break, go to step 7.
If the circuit breakers of the battery cabinets are in the "I"

position, go to step 7.
Check the external batteries (see 411-9001-048 (Nortel GSM

BTS S8000/S8003 Troubleshooting)).
If the test is failed, replace the external batteries (Field

Replaceable Unit). Refer to 411-9001-048 (Nortel GSM BTS
If the test is correct, disconnect the cables of the battery

cabinet. Go to step 9.
Put the DC circuit breaker of the battery cabinet in the "I"

position.
In the case of a new break, replace the DC circuit

breaker of the battery cabinet (Field Replaceable Unit).
Troubleshooting).

411-9001-103 18.06 20 January 2010
425

Otherwise, check the cables between the batteries and the

circuit breaker.
If the cables are correct, go to step 9.
If the cables are not correct, replace them (Shop
Replaceable Unit).
Replace the ALCO or RECAL board (Field Replaceable Units).
For the ALCO board, refer to 411-9001-048 (Nortel GSM BTS

For the RECAL board, refer to 411-9001-048 (Nortel GSM

BTS S8000/S8003 Troubleshooting).
Go to step 10.
Additional checks
10
11

Check the state of the battery cabinet by performing the "Display



go to step 12.
12
Clear the alarm.
13

--End--
2.12.5 Battery cabinet (source: Doors)

Fault number 1067
Equipment:
Battery cabinet
Source:
(5832707) Doors
BTS model:
S8000 Outdoor

411-9001-103 18.06 20 January 2010
426
FAULT ANALYSIS
This alarm indicates that a door is open.

BSC defense
None.
There is no immediate impact.
CAUTION
If an intervention is being performed on the battery cabinet, the
door is open. Therefore, the alarm is normal.
However, if no intervention is being performed on the battery
cabinet, this alarm is not normal. Intervention on the site must
be immediate. If the doors remain open, temperature problems
could arise.
TROUBLESHOOTING
Step
Action
Preliminary checks



"enabled".



411-9001-103 18.06 20 January 2010
427




becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the door contact is valid, by



On-site maintenance


and go to step 12.
If the alarm appears and the door is closed, go to step 5.


411-9001-103 18.06 20 January 2010
428
Check the door contact.

step 6.



go to step 8.

go to step 14.
Check the cable between the door contact and the ALCO or
RECAL board.

step 9.
10


11

go to step 11.

go to step 14.
For the ALCO board, refer to 411-9001-048 (Nortel GSM BTS

For the RECAL board, refer to 411-9001-048 (Nortel GSM

Go to step 12.
411-9001-103 18.06 20 January 2010
429
Additional checks
12
13

Check the state of the battery cabinet by performing the "Display



go to step 14.
14
Clear the alarm.
15

--End--
2.12.6 BCF cabinet door contact

(source: BCF cabinet door contact detection)
Fault number 1067
Equipment:
BCF Cabinet door
Source:
(6291457) BCF cabinet door contact detection
BTS model:
S8000 Indoor
FAULT ANALYSIS
This alarm indicates that the BCF cabinet door has been opened
(begin-of-fault) or closed (end-of-fault).

BSC defense
None.
BSC defense
None.
There is no immediate impact on the service.

411-9001-103 18.06 20 January 2010
430
CAUTION
If an intervention is being performed on the BCF cabinet, the
However, if no intervention is being performed on the BCF
be immediate. If the door remains open, temperature problems
could arise.
TROUBLESHOOTING
Step
Action
Preliminary checks



"enabled".







411-9001-103 18.06 20 January 2010
431

becomes "enabled".

"disabled-failed".
alarm persists.

If the state of the "BCF cabinet door" equipment is "failed",

the fault is confirmed. Go to step 4.
If the state of the "BCF cabinet door" equipment is "working",

the fault is not confirmed. Go to step 14.
On-site maintenance


and go to step 12.
If the alarm appears but the door is closed, go to step 5.

Replace the ALCO board (Field Replaceable Unit). Refer to

411-9001-048 (Nortel GSM BTS S8000/S8003 Troubleshooting).
Then go to step 6.

Check the state of the door contact by performing a "Display


411-9001-103 18.06 20 January 2010
432
If the state of the "BCF door contact" equipment is still

"failed", go to step 8.
If the state of the "BCF door contact" equipment is "working",

go to step 14.
Check the cable between the BCF and the connection panel.

step 9.
10


11

"failed", go to step 11.

go to step 14.
Check the cable between the connection panel and the ALCO
board.

step 12.
Additional checks
12
13

Check the state of the door contact by performing the "Display


"failed", call the manufacturer.

go to step 14.

411-9001-103 18.06 20 January 2010
14
Clear the alarm.
15
433
--End--
2.12.7 BCF cabinet fan (source: BCF cabinet fan fault)

Fault number 1067
Equipment:
BCF Cabinet fan
Source:
(6356993) BCF cabinet fan fault
BTS model:
S8000 Indoor
FAULT ANALYSIS
This alarm indicates that a BCF cabinet fan is faulty.

BSC defense
None.
None.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).


411-9001-103 18.06 20 January 2010
434

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the BCF cabinet fan is valid, by

If the state of the "BCF Cabinet fan" equipment is "failed", the

If the state of the "BCF Cabinet fan" equipment is "working",

On-site maintenance
Check the mains power supply on the operator box.


and go to step 4.
Check the state of the fuse.
step 6.
Replace the faulty fan (Field Replaceable Unit). Refer to

Go to step 6.
Additional checks

411-9001-103 18.06 20 January 2010
435

Check the state of the BCF cabinet fan by performing a "Display

If the state of the "BCF cabinet fan" equipment is still "failed",

If the state of the "BCF cabinet fan" equipment is "working",

go to step 8.
Clear the alarm.

--End--
2.12.8 BCF power supply (source: Volt)

Fault number 1067
Equipment:
Converter BCF
Source:
(5373953) Volt
BTS model:
FAULT ANALYSIS
This alarm is detected by the ALCO board.
This alarm indicates that a BCF power supply is faulty.

BSC defense
None.
None.
TROUBLESHOOTING
Step
Action
Preliminary checks
Perform a "Display all" command on the btsSiteManager object.

411-9001-103 18.06 20 January 2010
436


"enabled".






becomes "enabled".

"disabled-failed".
alarm persists.
Perform a "Display hardware configuration" command on the

btsSiteManager object: the results are displayed in the "Session
log" window.

411-9001-103 18.06 20 January 2010
437
If the state of the "converter BCF" equipment is "failed", the

If the state of the "converter BCF" equipment is "working", the

Fault location
The equipment number indicates which of the three power

supplies is concerned by the alarm. Go to step 4.
On-site maintenance

BSS Fault Clearing - Advanced Maintenance Procedures) ).

and go to step 8.
Replace the BCF power supply (Field Replacement Unit).

Troubleshooting).
Replace the ALCO board (Field Replaceable Unit). Refer to


If the alarm persists, go to step 7 for the S8000 Indoor BTS
or to step 8 for the S8000 Outdoor BTS.
Replace the external alarm cable (Shop Replaceable Unit). Go

to step 8.
Additional checks
Check the alarm state.


btsSiteManager object: the results are displayed in the "Session
log" window.
If the BCF converter equipment is still "failed", call the

manufacturer.
If the BCF converter equipment is "working", go to step 10.

411-9001-103 18.06 20 January 2010
438
10
Clear the alarm.
11

--End--
2.12.9 BRC (source: Manual switch on battery power)

Fault number 1067
Equipment:
BRC
Source:
(6553601) Manual switch on battery power
BTS model:
FAULT ANALYSIS
This notification indicates that the BTS has been manually (using OMC-R
command) switched from main power to battery.
2.12.10 BRC (source: Automatic switch on battery power)

Fault number 1067
Equipment:
BRC
Source:
(6553602) Automatic switch on battery power
BTS model:
FAULT ANALYSIS
from main power to battery.
2.12.11 BRC (source: Manual switch on main power)

Fault number 1067
Equipment:
BRC
Source:
(6553603) Manual switch on main power
BTS model:
FAULT ANALYSIS
2.12.12 BRC (source: Automatic switch on main power)

Fault number 1067
Equipment:

BRC

411-9001-103 18.06 20 January 2010
Source:
(6553604) Automatic switch on main power
BTS model:
439
FAULT ANALYSIS
2.12.13 BRC (source: Battery failure)

Fault number 1067
Equipment:
BRC
Source:
(6553605) Battery failure
BTS model:
FAULT ANALYSIS
The software of the RECAL board in the BTS continuously controls the
state of the battery strings and generates a battery failure alarm to the
BCF when an error is detected on one of them. On switching the power
supply mode, the battery failure alarm is cleared and the control algorithm
is restarted.
The following two types of malfunction are covered:
When the battery is floating or loading:
The battery is considered "bad" when the middle point voltage of one
string gets out of a given range (+/- 1,3V). When the RECAL detects a
battery failure, the BCF generates a notification (fault number 1067). This
notification specifies a battery malfunction with the battery failure cause. A
discharge test is recommended to confirm the battery status. When the
battery is floating or loading, every 10 minutes the value is reported at the
BTS level, computed on average of values sampled every 100 ms.
The battery is in use (discharge)
After a short period of time (60 sec.), the middle point voltage of each
string is computed (average on values sampled every 100 ms) as a
reference. Then, the middle point voltage of each string is periodically
compared to this reference.
The battery is considered bad when the difference between the reference
and the middle point voltage goes outside of a given range (+/- 0,5V) And
the Stringglobal voltage is greater than a given threshold (45,5V) : in order
to avoid generating a battery failure notification in case of huge discharge
due to a main power failure (the variation of the difference between the
reference and the middle point voltage is therefore normal).

411-9001-103 18.06 20 January 2010
440
When the RECAL detects a battery failure, the BCF generates a

notification (fault number 1067). This notification specifies a battery
malfunction with the battery failure cause. Furthermore, the BTS does
not switch to main power and hence the discharge phase goes to the
threshold which triggers an automatic switch to the main power (processed
by the BRC).
When the battery is in use (discharge), every 2 seconds the value is
reported at the BTS level, computed on average of values sampled every
100 ms.
A string is composed of 4 stacks. A double failure in a string (a stack on
each side of the middle point voltage with the same decrease of voltage) is
not detected by this method since the middle point voltage remains in the
given range. However, the analysis of the voltage-time diagram allows the
detection a quick discharge which highlights a battery failure.
The battery malfunction alarm is cleared at the OMC-R on switching the
battery mode (main or battery). When the string is replaced, checks can
be done with the TIL (middle point voltage values, global string voltage
value) without having to wait for BTS detection which will be notified to the
OMC-R.
2.12.14 BRC (source: Monitored battery not present)

Fault number 1067
Equipment:
BRC
Source:
(6553606) Monitored battery not present
BTS model:
FAULT ANALYSIS
When the BRC is not present (or does not work and is detected
as not present), a notification is sent by the BTS to the OMC-R
if the BRC features are activated in the set external contact (the
batteryRemoteControllerPresence parameter is set to present). By
default, this parameter is set to not present.
When the BRC led is ON, it means that the BTS is powered by batteries,
and that rectifiers are OFF (Note that the BRC led is turned ON only if
the user manually switches the BTS from mains to battery using OMC-R.
In case the mains circuit breaker is switched off the BTS automatically
switches to battery and the BRC led will not be turned ON in this case).
Hence, no maintenance is allowed on batteries. If maintenance is done,
then the BTS may be lost due to power shut down.

411-9001-103 18.06 20 January 2010
441
2.12.15 BRC (source: Internal inconsistency)

Fault number 1067
Internal inconsistency
Equipment:
BRC
Source:
(6553607) Internal inconsistency
BTS model:
FAULT ANALYSIS
The notification 1067 (cause Detection of an internal inconsistency) can
be caused by cable P3 or any combination of P3 with another cable. A
lock/unlock on the BTS Site Manager is necessary for the maintenance.
Then, a "switch battery on/off" command from the OMC-R may be required
to switch the power mode to main supply or battery in accordance with
the customer choice.
2.12.16 BTS SYNCHRONIZATION (source: SYNO clock not locked on

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

+ S8006
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 with the radio cabinet clock: the value
of the reference clock of the synchronizing PCM is not in the admitted
interval.

BSC defense As long as the PCM link is operational, there is no BSC
defense action.
Impact on the service As long as the PCM link is operational, there is
no BSC defense action.
If the impact is "non transparent for the BSC" in the notification, the
BSC unconfigures the btsSiteManager object.

411-9001-103 18.06 20 January 2010
442
CAUTION
The service is reduced or lost depending on the
configuration.
If the impact is "transparent for the BSC" in the notification, the BSC
does nothing.
CAUTION
A handover problem can occur between the BTS concerned
and its neighboring BTSs (a Nortel BTS or a BTS of another
manufacturer).
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".


411-9001-103 18.06 20 January 2010
443

"disabled-failed".
b.

the alarm persists.
Check the number of impacted sites.
If only one site is impacted, go to step 3.

If several sites are impacted, go to step 4.
Check the validity of the alarm on the CMCF board by

performing a visual test of the board.
If the "LCKD" LED of the CMCF board is on and the "SKP"

LED of the CPCMI board is on, the fault is confirmed. Go to
step 5.
Otherwise, the fault is not confirmed. Go to step 30.
Check the validity of the alarm on several impacted sites by

performing a visual test of the board.
If the "LCKD" LED of the CMCF board is on and the "SKP"

LED of the CPCMI board is on, the fault is confirmed. Go to
step 11.
Otherwise, the fault is not confirmed. Go to step 30.
Perform a switchover of the CMCF board.

Check if the alarm persists in the "Current Alarm list" window.

Replace the previously active CMCF board (Field Replaceable

Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003

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

the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS

411-9001-103 18.06 20 January 2010
444
Go to step 31.
7
Check the number of PCM links declared.
If there is only one PCM link declared, go to step 8.

If there are several PCM links declared, go to step 9.
Replace the CPCMI board (Field Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003

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


the S8002 BTS

the S8006 BTS

manufacturer.
9
Perform a "Display dynamic data" command on the lapdLink

object to determine which PCM link is used by the lapd.
10
Perform a switchover of the PCM links by setting the

administrativeState of the lapdLink object to "locked".

If the alarm persists, perform this action on each PCM link
again and as long as the alarm persists. At the end,
11
12
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 29.
If the "synchronizing PCM" parameter is not "synchro internal

clock", go to step 12.
Check the number of available TCUs.
13
If there are at least two available TCUs, go to step 13.

If there is only one TCU, go to step 14.
Perform a PCM Ater link switchover by setting the

administrativeState of the pcmCircuit object to "locked".

411-9001-103 18.06 20 January 2010
14
445

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

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

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

the problem concerns the BSC. Go to step 20.
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.
If the frequency is not correct on all the PCM A links, go
to step 16.
If the frequency is not correct on one of the PCM A links,
go to step 17.
If the frequency is correct, the problem does not concern
the TCU but concerns the BSC. Go to step 20.
16
If the frequency is not correct, the problem concerns the

MSC. Look for it and solve it. Then go to step 1.
Replace:
For the TCU 3000, the CEM board (Field Replaceable Unit).
Refer to Nortel GSM BSC 3000 / TCU 3000 Troubleshooting
(411-9001-132).
17
Replace:
For the TCU 3000, the IEM board. Refer to Nortel GSM BSC
3000 / TCU 3000 Troubleshooting (411-9001-132).
18
Perform a "Display all" command on the transcoder object to

check the state of the TCU.

the problem concerns the BSC. Go to step 20.

go to step 19.

411-9001-103 18.06 20 January 2010
446
19
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 IEM board of the TCU 3000. Go
to step 17.

do 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 15. Otherwise
go to step 17.
20
Perform a "Display all" command on the bsc object to check the

correctness of the parameters of the passive chain.
21
22
23
For the BSC 3000, go to step 22.
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 25.
If the frequency of the PCM A link is correct and the

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

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

identify the faulty item.
a Replace the CEM board of the TCU 3000. Refer to Nortel
GSM BSC 3000/TCU 3000 Troubleshooting (411-9001-132).

If the alarm persists, go to step 23b
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. Refer to Nortel GSM BSC 3000/TCU
3000 Troubleshooting (411-9001-132).
24

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

411-9001-103 18.06 20 January 2010
25
447
Measure the frequency of the PCMs (with a PCM analyzer) on

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 26.
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:

If it is the uplink concerned, go to step 28.
If it is the downlink concerned, the problem concerns the
PCMs. Call the transmission operator.
26
Replace the CMCF board (Field Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
If the alarm has disappeared, go to step 33. If the alarm persists,

go to step 27.
27
Replace the CPCMI board (Field Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS

411-9001-103 18.06 20 January 2010
448

manufacturer.
28
Replace:
For the BSC 3000, the CEM board (Field Replaceable Unit).
Refer to Nortel GSM BSC 3000 / TCU 3000 Troubleshooting
(411-9001-132).
29
Make a TCU operational.

As soon as a TCU is operational, go to step 12.
Additional checks
30
31

Check the state of the alarm on the CMCF board by performing a

visual test of the board.
If the "LCKD" LED of the CMCF board is off and the "SKP"
LED of the CPCMI board is off, call the manufacturer.
32
Clear the alarm.
33

--End--
2.12.17 BTS synchronization (source: Synchro not locked because

OCVXO is KO)
Fault number 1067
Equipment:
BTS synchronization
Source:
(3342341) Synchro not locked because OCVXO is

KO
BTS model:

+ S8006
FAULT ANALYSIS
The begin-of-fault alarm indicates that the SYN clock is not able to lock on
the PCM because the OCVXO (oscillator) of the passive CMCF board is
faulty (the BTS is in duplex configuration).

411-9001-103 18.06 20 January 2010
449
The problem occurred either on the passive CMCF board, or on the

previously active CMCF board, which became passive after an automatic
switchover.
The end-of-fault must be manual.

BSC defense
None.
operational.
None, as long as the active CMCF board is
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled". If several faults occur on the BTS
Synchronization item of equipment, only the first generated
fault remains visible at the OMC-R. Other faults are available
in the notification logs.


411-9001-103 18.06 20 January 2010
450

"disabled-failed".
alarm persists.
Check that the alarm on the BTS synchronization equipment of

the BTS is valid, by performing a "Display hardware information"
command (in "standard" mode) on the btsSiteManager object.
Look at the result displayed in the session log window.
If the BTS synchronization equipment is "failed", the fault is

If the BTS synchronization equipment is "working", the fault is

On-site maintenance
Replace the passive CMCF board (Field Replaceable Unit). The

cause "OCVXO KO" can be indicated on the repair note. Refer
to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Then go to step 4.
Additional checks
Check the state of the alarm on the CMCF board by performing a

visual test of the board.
If the passive CMCF board is not operational, call the

manufacturer.
Perform a "Display hardware information" command (in

"standard" mode) on the btsSiteManager object.

411-9001-103 18.06 20 January 2010
451
If the BTS synchronization equipment is still "failed", call the

manufacturer.
If the BTS synchronization equipment is "working", go to step

6.
Clear the alarm.

--End--
2.12.18 BTS synchronization (source: GPS synchronization

unavailable)
Fault number 1067
Equipment:
BTS synchronization
Source:
(3342343) GPS synchronization unavailable
BTS model:
S8000 Outdoor CBCF + S8000 Indoor CBCF
FAULT ANALYSIS
The begin-of-fault alarm indicates that the GPS PPS signal is not present
or not correct, even though the GPS synchronization mode has been
selected at the OMC-R.
The end-of-fault alarm indicates that the GPS synchronization has been
retrieved again and that the BTS synchronized itself on it.
If GPS has become in service but is not accurate enough to be used
as a synchronization source, the end-of-fault "GPS synchronization
unavailable" is sent, and another alarm with begin-of-fault "Lack of GPS
synchronization accuracy" is sent too (refer to Paragraph 2.12.20 BTS
SYNCHRONIZATION (source: Lack of GPS synchronization accuracy)
(page 461)).

BSC defense
None.
Impact on the service None when the BTS remains synchronized on
the Abis link (begin-of-fault).

411-9001-103 18.06 20 January 2010
452
However, when the BTS synchronizes itself on the external

synchronization, it changes its GSM time for the GPS time. This change
of GSM time causes a reset "GSM time modified" of all the TRXs
(end-of-fault).
CAUTION
The service is lost during the TRX reset.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).



411-9001-103 18.06 20 January 2010
453

"disabled-failed".
b.

the alarm persists.

the BTS is valid:
a Perform a "Display data information" command (in "normal"
mode) on the btsSiteManager object.
The "Current synchronization mode" is: "Abis

synchronization due to GPS synchronization unavailable
or lack of accuracy".
The "Available synchronization sources" are: "Abis

synchronization only".
Go to step 2b.
b
Perform a "Display hardware information" command (in

If the BTS synchronization equipment is "failed", the fault

If the BTS synchronization equipment is "working", the

On-site maintenance
On site, check the validity of the alarm by performing a visual

test of the synchronization LEDs on the CMCF boards.
When the GPS synchronization is unavailable, the BTS

remains synchronized through the Abis link, and the LEDs of
the CMCF boards are lit as shown in Table 12 "CMCF boards
LEDs status (BTS synchronized on Abis link)" (page 453).
Then the fault is confirmed.
Table 12
CMCF boards LEDs status (BTS synchronized on Abis link)
LEDs
Active CMCF board
Passive CMCF board
CLK 0, 1, 2
one of them is ON
(displaying the
PCM no. used for
synchronization)
one of them is ON
(displaying the
PCM no. used for
synchronization)

411-9001-103 18.06 20 January 2010
454
Table 12
CMCF boards LEDs status (BTS synchronized on Abis link) (contd.)
LEDs
Active CMCF board
Passive CMCF board
LCKD
OFF
ON (solid green)
HLDVR
OFF
OFF
If the BTS is equipped with a TMU, go to step 4.

If the BTS is equipped with an LMU + EIU, go to step 5.
4

test of the TMU.
If the TMU control LED is OFF, the TMU is not receiving

power. Check the TMU power connections (refer to the TMU
manufacturer documentation) or go to step 6.
If the TMU control LED is flashing green, the TMU is

initializing. Wait for the end of initializing, until the TMU is in a
stable state, such as solid green, flashing yellow or solid red.
If the TMU control LED is solid red, the GPS is out of service,
experiencing a major fault. Go to step 6.
If the TMU control LED is flashing yellow, the GPS is working

but the status of the synchronizing signal is not satisfactory
enough to use it as a synchronization source.
Wait for 30 minutes after the last TMU power up (time
needed to catch satellite signals and converge the
computation of position and time).
If the situation does not improve, check the antenna
connection (AMT connector on the TMU). If necessary,
refer to TMU manufacturer documentation.
If the situation does not improve, the GPS antenna
installation needs to be modified. Go to step 6.
If the TMU control LED is solid green, the GPS is working

and available as synchronization source. Go to step 7.

test of the LMU + EIU:
If the EIU power LED is solid green, the EIU is receiving

power and sending the timing signal to the BTS. Go to step 8.
If the EIU power LED is off, the EIU is not receiving

power. Check the EIU power connections (refer to the EIU
manufacturer documentation) or go to step 6.
Call the TMU (or LMU + EIU) manufacturer.
Check the cable between the TMU and BCFICO board.

411-9001-103 18.06 20 January 2010
455
Unplug the cable between the TMU (RJ45 "BTS" connector)

and BCFICO board (9-pin connector).
Plug the cable again between the TMU and BCFICO board.
Check that the three "CLK 0", "CLK 1" and "CLK 2" LEDs of
the CMCF board blink three times simultaneously for a period
of 2 seconds. Then go to step 9.
Check the cable between the LMU and EIU to the BTS. A Y
cable is used to connect:
the LMU RS-232 cable (ENV/AOA connector) on the one end
Unplug the Y cable.
Plug the Y cable again.
Check that the three "CLK 0", "CLK 1" and "CLK 2" LEDs of
the EIU RS-422 cable (RJ45 connector) on the other end

into the BTS (CBCF port RS-232)
Additional checks
Check the state of the LEDs on the CMCF boards.
If the GPS synchronization is available, the LEDs of the

CMCF boards are lit as shown in Table 13 "CMCF boards
LEDs status (BTS synchronized on GPS)" (page 455). Then
go to step 10.
Table 13
CMCF boards LEDs status (BTS synchronized on GPS)
LEDs
CLK 0, 1, 2
LCKD
HLDVR
10
Active CMCF board
Passive CMCF board
all ON (solid green)
all ON (solid green)
ON (solid green)
ON (solid green)
OFF
OFF
If the LEDs show that the BTS is still synchronized on the

Abis link (refer to Table 12 "CMCF boards LEDs status (BTS
synchronized on Abis link)" (page 453) in step 3), then go to
step 12.
Use the TIL to check that the cable has been correctly connected
and that the BTS receives the GPS synchronization signal.
Connect the TIL to the BTS:

411-9001-103 18.06 20 January 2010
456
11
If the TIL displays "GPS synchronization available", then the

BTS receives 1 Hz PPS clock and PPS frames. Go to step
11.
If the TIL displays "no external synchronization source", then

the BTS does not receive any GPS signal. Go to step 12.

12
Call the manufacturer.
13

--End--
2.12.19 BTS synchronization (source: Loss of GPS synchronization)

Fault number 1067
Equipment:
BTS synchronization
Source:
(3342344) Loss of GPS synchronization
BTS model:
FAULT ANALYSIS
The begin-of-fault alarm indicates that the GPS PPS is no more present.
The BTS detects a loss of GPS synchronization signal when one of the
following events occurs:
when the GPS status = 2 (the GPS is out of service experiencing a

major fault. The TMU control LED is solid red)
when the PPS is not received or not correct
when the GPS time is not correctly incremented by 1 sec. at each PPS
period successively during 3 times
when the serial link between TMU and the BCFICO board is faulty
(CRC KO) or between the LMU and CBCF port
The end-of-fault alarm indicates that the GPS synchronization has been
retrieved again and that the BTS synchronized itself on it.

BSC defense
None.

411-9001-103 18.06 20 January 2010

clock (begin-of-fault).
457
None because the BTS holds over to its internal
When the BTS synchronizes itself on the GPS synchronization, it changes

its GSM time for the GPS time without impact on the service (end-of-fault).
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).


"disabled-failed".
alarm persists.

411-9001-103 18.06 20 January 2010
458

the BTS is valid:
The "Current synchronization mode" is: "hold over mode

due to a loss of GPS synchronization", and the "Available
synchronization sources" are: "Abis synchronization only".
Go to step 2b.
b Perform a "Display hardware information" command (in



On-site maintenance

test of the synchronization LEDs on the CMCF boards.
When the GPS synchronization is lost, the BTS remains

synchronized on its internal clock, and the LEDs of the CMCF
boards are lit as shown in Table 14 "CMCF boards LEDs
status (BTS in holdover after loss of GPS synchro)" (page
458). Then the fault is confirmed.
Table 14
CMCF boards LEDs status (BTS in holdover after loss of GPS
synchro)
LEDs
Active CMCF board
Passive CMCF board
all ON
all ON
LCKD
OFF
ON
HLDVR
ON
ON
CLK 0, 1, 2

4

test of the TMU.

411-9001-103 18.06 20 January 2010
459
experiencing a major fault. Go to step 6.




test of the LMU + EIU:

If the EIU power LED is off, the EIU is not receiving

power. Check the EIU power connections (refer to the EIU
documentation) or go to step 6.
Check the cable between the TMU and BCFICO board.

a Unplug the cable between the TMU and BCFICO board.
b Plug the cable again between the TMU and BCFICO board.
c Check that the three "CLK 0", "CLK 1" and "CLK 2" LEDs of
Check the cables between the LMU and EIU to the BTS. A Y
cable is used to connect:
The LMU RS-232 cable (ENV/AOA connector) on the one

end
The EIU RS-422 cable (RJ45 connector) on the other end

Into the BTS (CBCF port RS-232)
a Unplug the Y cable.

411-9001-103 18.06 20 January 2010
460
b Plug the Y cable again.

c Check that the three "CLK 0", "CLK 1" and "CLK 2" LEDs of
of 2 seconds when the cable is correctly connected. Then go
to step 9.
Additional checks
Check that the BTS is getting resynchronized on the GPS clock:

a The BTS can detect a correct GPS signal three seconds after
the cable (between the BTS and the LMU or TMU) has been
plugged. Note that, at this stage, a "Display data information"
command (in "normal" mode) on the btsSiteManager object
gives the following items of information:

due to a loss of GPS synchronization".
The "Available synchronization sources" are: "Abis + GPS

synchronization".
b Wait until the BTS is completely synchronized on the GPS

clock. It can take some time, depending on how long the
GPS signal has been unavailable.
c When the BTS is completely synchronized on the GPS
clock, the end-of-fault alarm (cause 3342344 "Loss of GPS
synchronization") is sent at the OMC-R.
d Another "Display data information" command (in "normal"
mode) on the btsSiteManager object now gives the following
items of information:
The "Current synchronization mode" is: "Network GPS

synchronized".

synchronization".
e Go to step 10.
10
If the GPS synchronization is available, the LEDs of the

go to step 11.
Table 15
LEDs
Active CMCF board
Passive CMCF board
CLK 0, 1, 2
all ON
all ON

411-9001-103 18.06 20 January 2010
461
Table 15
CMCF boards LEDs status (BTS synchronized on GPS) (contd.)
LEDs
11
Active CMCF board
Passive CMCF board
LCKD
ON
ON
HLDVR
OFF
OFF
If the LEDs show that the BTS is still synchronized on its

internal clock (refer to Table 14 "CMCF boards LEDs status
(BTS in holdover after loss of GPS synchro)" (page 458) in
step 3), then go to step 13.
12

BTS receives 1 Hz PPS clock and PPS frames. Go to step
12.


13
14

--End--
2.12.20 BTS SYNCHRONIZATION (source: Lack of GPS synchronization

accuracy)
Fault number 1067
Equipment:
BTS synchronization
Source:
(3342345) Lack of GPS synchronization accuracy
BTS model:
FAULT ANALYSIS
The begin-of-fault alarm indicates that the timing quality is not sufficient.
The GPS signal is not accurate enough to be used as a synchronization
source. The BTS detects a loss of accuracy when the GPS status goes
from 0 to 1. The GPS is working but the status of the synchronizing signal
is not satisfactory enough to use it as a synchronization source.

411-9001-103 18.06 20 January 2010
462
When the BTS has just been powered up, if the TMU is powered through
the BTS itself, several minutes are needed before the GPS receivers
become active (TMU (or LMU + EIU) being correctly locked and suitable
for BTS synchronization). This begin-of-fault alarm is sent in between.
Otherwise, the probable cause of the alarm is either a problem with the
GPS antenna, or the cable between the antenna and the TMU (or LMU
+ EIU).
The end-of-fault alarm indicates that the GPS PPS has become valid again
and that the BTS synchronized itself on it.

BSC defense
None.
1st case: the GPS signal used to be accurate, and the BTS was
synchronized on it. But it has now become inaccurate, and as a
consequence the BTS has turned into holdover mode and sent the
alarm "Lack of GPS synchronization accuracy" without impact on the
service (begin-of-fault).
When the GPS PPS becomes valid again, the BTS synchronizes itself
on the GPS time without impact on the service (end-of-fault).
2nd case: The BTS has just started up (holdover mode, then
synchronized on the Abis link, followed by the BSC configuration).
But the GPS signal currently lacks accuracy. As a consequence, the
BTS remained synchronized on the Abis link and has sent the alarm
"Lack of GPS synchronization accuracy" without impact on the service
(begin-of-fault).
But when the GPS PPS becomes valid again, the BTS synchronizes
itself on the GPS time. This change of GSM time causes a reset
"GSM time modified" of all the TRXs with an impact on the service
(end-of-fault).
CAUTION
TROUBLESHOOTING
Step
Action
Preliminary checks

411-9001-103 18.06 20 January 2010
463



Procedures) ).


"disabled-failed".
alarm persists.

the BTS is valid:

due to a GPS synchronization lack of accuracy".

synchronization".

411-9001-103 18.06 20 January 2010
464
Go to step 2b.
If the BTS synchronization equipment is "failed", the fault is

If the BTS synchronization equipment is "working", the fault is

On-site maintenance

test of the synchronization LEDs on the CMCF boards. There
are two different cases:
1st case: the GPS signal used to be accurate, and the BTS
was synchronized on it. But it has now become inaccurate,
and the BTS has turned into holdover mode and sent the
alarm "Lack of GPS synchronization accuracy". The LEDs of
LEDs status (BTS in holdover when the GPS synchro lacks
accuracy)" (page 464). The fault is confirmed:
Table 16
CMCF boards LEDs status (BTS in holdover when the GPS
synchro lacks accuracy)
LEDs
Active CMCF board
Passive CMCF board
CLK 0, 1, 2
all ON
all ON
LCKD
OFF
ON
HLDVR
ON
ON
2nd case: the BTS has just started up (holdover mode,

then synchronization on the Abis link, followed by the BSC
configuration). But the GPS signal currently lacks accuracy.
As a consequence, the BTS remained synchronized
on the Abis link and has sent the alarm "Lack of GPS
synchronization accuracy". The LEDs of the CMCF boards
are lit as shown in Table 17 "CMCF boards LEDs status
(BTS synchronized on Abis link)" (page 465). The fault is
confirmed. Note that there will be an impact on the service
at the end-of-fault.

411-9001-103 18.06 20 January 2010
465
Table 17
CMCF boards LEDs status (BTS synchronized on Abis link)
LEDs
Active CMCF board
Passive CMCF board
CLK 0, 1, 2
one of them is ON
(displaying the PCM no.
used for synchronization)
one of them is ON
LCKD
OFF
ON
HLDVR
OFF
OFF

test of the TMU.
experiencing a major fault. This is very unlikely because
this is not consistent with the current alarm "Lack of GPS
synchronization accuracy". Go to step 6.



test of the LMU +EIU:


Additional checks
If the GPS synchronization is accurate, the LEDs of the

go to step 8.

411-9001-103 18.06 20 January 2010
466

Table 18
LEDs
Active CMCF board
Passive CMCF board
all ON
all ON
LCKD
ON
ON
HLDVR
OFF
OFF
CLK 0, 1, 2
If the LEDs show that the BTS is still in holdover mode (refer
to Table 16 "CMCF boards LEDs status (BTS in holdover
when the GPS synchro lacks accuracy)" (page 464)) or is
synchronized on the Abis link (refer to Table 17 "CMCF
boards LEDs status (BTS synchronized on Abis link)" (page
465)), then go to step 10.

BTS receives 1 Hz PPS clock and PPS frames. Go to step 9.


10
Call the BTS manufacturer.
11

--End--
2.12.21 BTS SYNCHRONIZATION (source: Master synchronization

unavailable)
Fault number 1067
Equipment:
BTS synchronization
Source:
(3342346) Master synchronization unavailable
BTS model:
FAULT ANALYSIS
The begin-of-fault alarm indicates that the slave BTS could not
synchronize itself on the master synchronizing BTS.

411-9001-103 18.06 20 January 2010
467
The slave BTS received the set external contact message in "slave" mode,
and checked if the external synchronization signal (both 8 kHz and GSM
time) was present, but it was not. As a consequence, the BTS remained
synchronized on the BSC through the Abis link.
The end-of-fault alarm indicates that the external signal (both 8 kHz
and GSM time) has become available again and that the slave BTS
synchronized itself on it.

BSC defense
None.
Impact on the service None when the slave BTS remains synchronized
on the Abis link (begin-of-fault).
However, when the slave BTS synchronizes itself on the external
synchronization, it changes its GSM time for the master GSM time. This
change of GSM time causes a reset "GSM time modified" of all the TRXs
(end-of-fault).
CAUTION
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

411-9001-103 18.06 20 January 2010
468


"disabled-failed".
alarm persists.

the BTS is valid:

synchronization due to master synchronization not
available".
The "Available synchronization sources" is: "Abis

Go to step 2b.



411-9001-103 18.06 20 January 2010
469
At the OMC-R, check the state of the master synchronizing

BTS. The master BTS must be powered on, to make the
synchronization feature available.
If the master BTS is powered off, go to step 5.

If the master BTS is powered on, go to step 4.

test of the synchronization LEDs of the CMCF boards of the
slave BTS.
When the external synchronization is unavailable, the BTS

LEDs status (slave BTS synchronized on the Abis link)" (page
469). Then the fault is confirmed. Go to step 6.
Table 19
CMCF boards LEDs status (slave BTS synchronized on the Abis
link)
LEDs
Active CMCF board
Passive CMCF board
one of them is ON
(displaying the
PCM no. used for
synchronization)
one of them is ON
LCKD
OFF
ON
HLDVR
OFF
OFF
CLK 0, 1, 2
On site, perform a visual test of the master BTS:
If the master BTS is powered off, power it on. If necessary

Troubleshooting). Then go to step 7.
Check the Y cable between the master and the slave BTS.
The Y cable is a shunt of the PCM between the main and
extension cabinets of the master BTS. It is connected to the
BCFICO board in the main cabinet of the slave BTS, thanks to
two connectors: the master 8 kHz SY is received on the RS232
connector, and the master GSM time is received on the PCM4/5
connector.
a Check the connections to the master BTS, as well as the
whole cable itself (there can be adaptors).
b Unplug the external SY and GSM time connectors on the
slave BTS.

411-9001-103 18.06 20 January 2010
470
c Plug again the external SY and GSM time connectors on the

slave BTS.
d Check that the slave BTS synchronization LEDs "CLK 0",
"CLK 1" and "CLK 2" (on the CMCF board) blink three times
simultaneously for a period of 2 seconds.
e Check that the TRX reset (their LEDs blink until they are
operational again).
CAUTION
Connect the TIL to the slave BTS and check this BTS
receives the external synchronization signal coming from the
master BTS.
the TIL displays "master BTS synchronization available"

when the slave BTS receives 8 kHz clock and GSM time
on its external synchronization connectors. Then go to
step 7.
the TIL displays "no external synchronization source"

when the slave BTS does not receive 8 kHz clock or GSM
time on its external synchronization connectors. Then go
to step 10.
Additional checks
Check the state of the LEDs of the CMCF boards of the slave
synchronized BTS:
If the external synchronization is available, the LEDs of the

LEDs status (slave BTS fully synchro on its master BTS)"
(page 470). Then go to step 8.
Table 20
CMCF boards LEDs status (slave BTS fully synchro on its
master BTS)
LEDs
Active CMCF board
Passive CMCF board
all ON
all ON
LCKD
ON
ON
HLDVR
OFF
OFF
CLK 0, 1, 2
If the LEDs show that the slave BTS is still synchronized on

the Abis link (refer to Table 19 "CMCF boards LEDs status
(slave BTS synchronized on the Abis link)" (page 469) in step
4), then go to step 10.
Check the state of the site:

411-9001-103 18.06 20 January 2010
471

The "Current synchronization mode" is: "slave BTS

correctly synchronized on master signal".
The "Available synchronization sources" are: "Abis +

external synchronization coming from a master BTS".
Go to step 8b.
The BTS synchronization equipment is "working", go to

step 9.

10
11

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

Fault number 1067
Equipment:
BTS synchronization
Source:
(3342347) Loss of master GSM time
BTS model:
FAULT ANALYSIS
The begin-of-fault alarm indicates that the slave BTS lost its external GSM
time signal from the master synchronizing BTS.
As a consequence, the BTS remains synchronized on the master 8 kHz
SY signal. The GSM time sent to the TRX is the one calculated by the
BTS from the last one received from master BTS. There is no break on
GSM time, the TRX still work. The slave GSM time is calculated with the
same rate as the master BTS.

411-9001-103 18.06 20 January 2010
472
The end-of-fault alarm indicates that the GSM time has become available
again and that the slave BTS synchronized itself on it.

BSC defense
None.
on the master 8 kHz SY signal (begin-of-fault).
The slave BTS uses the SY signal as a synchronization source on
condition that no alarm with cause "Loss of master SY" has been sent at
the same time.
If both alarms are present simultaneously, first process the alarm with
cause "Loss of master SY".
However, in the very unlikely event that there is a GSM time break
(between the one received from the master BTS and the last one
calculated by the BCF and sent to the TRX), this break of GSM time
causes a reset "GSM time modified" of all the TRX (end-of-fault).
CAUTION
The service is lost if the TRX reset.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

411-9001-103 18.06 20 January 2010
473

becomes "enabled".

"disabled-failed".
alarm persists.

the BTS is valid:
The "Current synchronization mode" is: "slave BTS

synchronized on master SY but master GSM time has
been lost".

Go to step 2b.


411-9001-103 18.06 20 January 2010
474

connector. The alarm "Loss of master GSM time" can be due to
the GSM time connector being badly plugged.
b Unplug the GSM time connector on the slave BTS.
c Plug again the GSM time connector on the slave BTS.
e Connect the TIL to the slave BTS and check this BTS
receives the external synchronization signal coming from the
master BTS.
The TIL displays "master BTS synchronization available"

step 4.
The TIL displays "no external synchronization source"

to step 6.
Additional checks
synchronized BTS:
If the slave BTS is synchronized on its master BTS, the LEDs

of the CMCF boards are lit as shown in Table 21 "CMCF
boards LEDs status (slave BTS fully synchro on its master
BTS)" (page 474). Go to step 5.
Table 21
master BTS)
LEDs
Active CMCF board
Passive CMCF board
all ON
all ON
LCKD
ON
ON
HLDVR
OFF
OFF
CLK 0, 1, 2
If not, go to step 6.


411-9001-103 18.06 20 January 2010
475
--End--
2.12.23 BTS SYNCHRONIZATION (source: Loss of master SY)

Fault number 1067
Equipment:
BTS synchronization
Source:
(3342348) Loss of master SY
BTS model:
FAULT ANALYSIS
The begin-of-fault alarm indicates that the slave BTS lost its external 8 kHz
SY signal from the master synchronizing BTS.
As a consequence, the BTS synchronizes itself on Abis link (to avoid a
drift of the GSM time if the loss of external synchronization goes on for
long). The GSM time sent to the TRX is the one calculated by the BTS
from the last one received from master BTS, even if the master GSM time
is still available. There is no break on GSM time, the TRX still work but the
synchronization with master BTS is not guaranteed anymore.
The end-of-fault alarm indicates that the external 8 kHz SY signal has
become available again, and that the BTS has resynchronized itself on it.
If the master GSM time is available, the slave BTS uses it.
If not, the BTS carries on calculating its GSM time and sends an
alarm with fault number 1067 source "Loss of master GSM time" (see
Paragraph 2.12.22 BTS SYNCHRONIZATION (source: Loss of master
GSM time) (page 471)).

BSC defense
None.
on the Abis link (begin-of-fault).
However, in the very unlikely event that there is a GSM time break
(between the one received from the master BTS and the last one
calculated by the BCF and sent to the TRX), this break of GSM time
causes a reset "GSM time modified" of all the TRXs (end-of-fault).
411-9001-103 18.06 20 January 2010
476
CAUTION
The service is lost if the TRX reset.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

becomes "enabled".

"disabled-failed".
alarm persists.

the BTS is valid:

411-9001-103 18.06 20 January 2010
477


synchronization due to loss of master SY".

Go to step 2b.


At the OMC-R, check the state of the master synchronizing

BTS. The master BTS must be powered on, to make the
synchronization feature available.
If the master BTS is powered off, go to step 5.


test of the synchronization LEDs on the CMCF boards of the
slave BTS.
If the external synchronization (8 kHz) is lost, the BTS

LEDs status (slave BTS synchronized on Abis link)" (page
477). Then the fault is confirmed. Go to step 6.
Table 22
CMCF boards LEDs status (slave BTS synchronized on Abis link)
LEDs
Active CMCF board
Passive CMCF board
CLK 0, 1, 2
one of them is ON
one of them is ON
LCKD
OFF
ON
HLDVR
OFF
OFF
On site, perform a visual test of the master BTS:

411-9001-103 18.06 20 January 2010
478
If the master BTS is powered off, power it on. If necessary

Troubleshooting). Then go to step 7.
connector. The alarm "Loss of master SY" can be due to the SY
connector being badly plugged.
b Unplug the SY connector on the slave BTS.
c Plug again the SY connector on the slave BTS.
e Connect the TIL to the slave BTS and check this BTS
receives external synchronization signal coming from the
master BTS.
the TIL displays "master BTS synchronization available"

step 7.
the TIL displays "no external synchronization source"

to step 9.
Additional checks
synchronized BTS:
If the external synchronization is available, the LEDs of the

LEDs status (slave BTS fully synchro on its master BTS)"
(page 478). Then go to step 8.
Table 23
master BTS)
LEDs
CLK 0, 1, 2
Active CMCF board
Passive CMCF board
all ON
all ON

411-9001-103 18.06 20 January 2010
479
Table 23
CMCF boards LEDs status (slave BTS fully synchro on its master BTS)
(contd.)
LEDs
Active CMCF board
Passive CMCF board
LCKD
ON
ON
HLDVR
OFF
OFF
If the LEDs show that the slave BTS is still synchronized

through the Abis link (refer to Table 22 "CMCF boards LEDs
status (slave BTS synchronized on Abis link)" (page 477) in
step 4), then go to step 9.

10

--End--
2.12.24 Cabinet door (source: Door contact detection)

Fault number 1067
Equipment:
door contact
Source:
(5898241) Door contact detection
BTS model:

+ S8006
FAULT ANALYSIS
This alarm is detected by the RECAL board.
This alarm indicates that the CBCF cabinet door has been opened
(begin-of-fault) or closed (end-of-fault).

BSC defense
None.
There is no immediate impact.

411-9001-103 18.06 20 January 2010
480
CAUTION
If an intervention is being performed on the CBCF cabinet, the
However, if no intervention is being performed on the CBCF
be immediate. If the doors remain open, temperature problems
could appear.
TROUBLESHOOTING
Step
Action
Preliminary checks



"enabled".







411-9001-103 18.06 20 January 2010
481

becomes "enabled".

"disabled-failed".
alarm persists.

If the state of the "door contact" equipment is "failed", the

If the state of the "door contact" equipment is "working", the

On-site maintenance

to fault number 1054 (see 411-9001-105 (Nortel GSM BSS
Fault Clearing - Advanced Maintenance Procedures)).

and go to step 12.
If the alarm appears but the door is closed, go to step 5.

Check the door contact switch.
If it is not correct, replace it. Then go to step 6.


411-9001-103 18.06 20 January 2010
482

If the state of the "door contact" equipment is still "failed", go

to step 8.
If the state of the "door contact" equipment is "working", go

to step 14.
Check the cable between the door contact and the RECAL
board.

step 9.
10


11
If the state of the "door contact" equipment is still "failed", go

to step 11.

to step 14.
Replace the RECAL board (Field Replaceable Units). Refer to

Go to step 12.
Additional checks
12
13

Check the state of the door contact by performing the "Display

If the state of the "door contact" equipment is still "failed", call

the manufacturer.

to step 14.

411-9001-103 18.06 20 January 2010
14
Clear the alarm.
15
483
--End--
2.12.25 Cavity (source: Cavity out of service)

Fault number 1067
Equipment:
Cavity
Source:
(8388609) Cavity out of service
BTS model:
S8000 Indoor
FAULT ANALYSIS
This alarm indicates that the cavity is unusable.

concerned.
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

411-9001-103 18.06 20 January 2010
484

becomes "enabled".

"disabled-failed".
alarm persists.



On-site maintenance
Replace the combiner (Field Replaceable Unit). Refer to

Go to step 4.
Additional checks

Check the state of the combiner by performing a "Display

If the state of the "cavity" equipment is still "failed", call the

manufacturer.
If the state of the "cavity" equipment is "working", go to step

6.

411-9001-103 18.06 20 January 2010
Clear the alarm.
485
--End--
2.12.26 Cavity (source: Cavity parked after tuning fault (min not found))
Fault number 1067
Equipment:
cavity
Source:
(8388610) Cavity parked after tuning fault (min not

found)
BTS model:
S8000 Indoor
FAULT ANALYSIS
This alarm indicates that the cavity is no longer settled on its configuration
frequency.

BSC defense The BSC unconfigures the transceiverEquipment
object concerned. It reconfigures the transceiver object on another
transceiverEquipment object, if the TDMA is priority.
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
486

Procedures)).

becomes "enabled".

"disabled-failed".
alarm persists.




tuning.


--End--

411-9001-103 18.06 20 January 2010
487
2.12.27 Cavity (source: Loss of cavity initialization)

Fault number 1067
Equipment:
Cavity
Source:
(8388611) Loss of cavity initialization
BTS model:
S8000 Indoor
FAULT ANALYSIS
This alarm indicates that the grading of the cavity has not been performed.

concerned.
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).


411-9001-103 18.06 20 January 2010
488

becomes "enabled".

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



On-site maintenance
Replace the combiner (Field Replaceable Unit). Refer to

Go to step 4.
Additional checks

Check the state of the combiner by performing a "Display

If the state of the "cavity" equipment is still "failed", call the

manufacturer.
If the state of the "cavity" equipment is "working", go to step

6.
Clear the alarm.

411-9001-103 18.06 20 January 2010
489

--End--
2.12.28 Cavity (source: Nack answer from cavity)

Fault number 1067
Equipment:
Cavity
Source:
(8388612) Nack answer from cavity
BTS model:
S8000 Indoor
FAULT ANALYSIS
This alarm indicates that the cavity no longer responds.

concerned.
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).


411-9001-103 18.06 20 January 2010
490

becomes "enabled".

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



Lock the transceiverEquipment object concerned in order to

trigger a reset of the CC8 software and a new tuning sequence.

intervention is necessary.

--End--
2.12.29 Cavity (source: Cavity parked after tuning fault (power too low))
Fault number 1067
Equipment:
Cavity
Source:
(8388613) Cavity parked after tuning fault (power

too low)
BTS model:
S8000 Indoor

411-9001-103 18.06 20 January 2010
491

concerned.
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.

411-9001-103 18.06 20 January 2010
492




tuning.


--End--
2.12.30 Cavity (source: Cavity parked after tuning fault (tuning detector
problem))
Fault number 1067
Equipment:
Cavity
Source:
(8388614) Cavity parked after tuning fault (tuning

detector problems)
BTS model:
S8000 Indoor

concerned.
CAUTION
Service reduction

411-9001-103 18.06 20 January 2010
493
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.




411-9001-103 18.06 20 January 2010
494


tuning.


--End--
2.12.31 Cavity (source: Internal software problem)

Fault number 1067
Equipment:
Cavity
Source:
(8388615) Internal software problem
BTS model:
S8000 Indoor

concerned.
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
495

Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.




tuning.


--End--

411-9001-103 18.06 20 January 2010
496
2.12.32 Cavity combiner (source: Power supply)

Fault number 1067
Equipment:
Cavity combiner
Source:
(8323073) Power supply
BTS model:
S8000 Indoor
FAULT ANALYSIS
This alarm indicates a power supply problem.

BSC defense
None.
None.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".


411-9001-103 18.06 20 January 2010
497

"disabled-failed".
alarm persists.
Check that the alarm on the cavity combiner is valid, by

If the state of the "cavity combiner" equipment is "failed", the

If the state of the "cavity combiner" equipment is "working",

On-site maintenance
If the frequency map has changed and only in this case, replace
the combiner (Field Replaceable Unit). Refer to 411-9001-048
Go to step 4.
Additional checks

Check the state of the cavity combiner by performing a "Display

If the state of the "cavity combiner" equipment is still "failed",


go to step 6.
Clear the alarm.

--End--

411-9001-103 18.06 20 January 2010
498
2.12.33 Cavity combiner (source: Tuning detector fault)

Fault number 1067
Equipment:
Cavity combiner
Source:
(8323074) Tuning detector fault
BTS model:
S8000 Indoor
FAULT ANALYSIS
This alarm indicates that it is not possible to modify the standard frequency
of cavities.

BSC defense
None.
None.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".


411-9001-103 18.06 20 January 2010
499

"disabled-failed".
alarm persists.



On-site maintenance
Go to step 4.
Additional checks




go to step 6.
Clear the alarm.

--End--

411-9001-103 18.06 20 January 2010
500
2.12.34 Cavity combiner (source: Link NOK)

Fault number 1067
Equipment:
Cavity combiner
Source:
(8323076) Link NOK
BTS model:
S8000 Indoor
FAULT ANALYSIS
This alarm indicates that level 3 dialogue has been lost.

BSC defense
None.
None
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".


411-9001-103 18.06 20 January 2010
501

"disabled-failed".
alarm persists.



On-site maintenance
Go to step 4.
Additional checks




go to step 6.
Clear the alarm.

--End--

411-9001-103 18.06 20 January 2010
502
2.12.35 C-DACS climatic system (source: Dirty filter)

Fault number 1067
Equipment:
Compact dacs cooler
Source:
(7929857) Dirty filter
BTS model:
S8002
FAULT ANALYSIS
This alarm occurs when the C-DACS filter is clogged.

BSC defense As soon as the (H)(e)PA temperature is over
60C, the (H)(e)PA are powered off. The BSC unconfigures the
transceiverEquipment objects.
Impact on the service There is no impact on the service until the BTS
and (H)(e)PA have overheated.
CAUTION
Service reduction
CAUTION
The intervention on the site must be within one week.
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
503

Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the C-DACS climatic system is valid, by

If the state of the "compact dacs cooler" equipment is "failed",

If the state of the "compact dacs cooler" equipment is

"working", the fault is not confirmed. Go to step 6.
On-site maintenance
Replace the filter (Field Replaceable Unit). Refer to

411-9001-084 (Nortel GSM BTS S8002 Troubleshooting). Go to
step 4.
Additional checks

Check the state of the C-DACS climatic system by performing


411-9001-103 18.06 20 January 2010
504
If the state of the "compact dacs cooler" equipment is still


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

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

Fault number 1067
Equipment:
Compact dacs cooler
Source:
(7929858) DACS failed
BTS model:
S8002
FAULT ANALYSIS
This alarm indicates a problem on the C-DACS climatic system.
BSC defense As soon as the (H)(e)PA temperature is over 60C, the

(H)(e)PA is powered off. The BSC unconfigures the transceiverEquipment
objects.
Impact on the service There is no impact on the service until the BTS
and (H)(e)PA overheat.
CAUTION
Service reduction
CAUTION
The intervention on the site must be immediate.

411-9001-103 18.06 20 January 2010
505
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the C-DACS climatic system is valid, by

If the state of the "compact dacs cooler" equipment is "failed",



411-9001-103 18.06 20 January 2010
506

On-site maintenance
Check that the L2/CB2 fan circuit breaker (power supply rack) on
the PCU and the climatic circuit breaker (C-AC box) are in the
"I" position.
If this is the case, go to step 5.

Reset the circuit breakers.
If the L2/CB2 circuit breaker cannot be reset:

a. Disconnect the DC wires related to the C-DACS (see
b. Reset the L2/CB2 circuit breaker of the power supply
rack.
In the case of a new break, check the PCU output

cables of the power supply rack. Replace them (Shop
Replaceable Unit). Go to step 5.
Otherwise, the operator can choose whether he

changes the C-DACS (Field Replaceable Unit)
as a whole or he replaces the faulty items (Field
Replaceable Units) of the C-DACS.
CAUTION
To replace faulty items, the personnel
working on the C-DACS must be
authorized to work according to security
standards.
The personnel must be qualified to work
on the C-DACS: they must be well-trained
on the functioning of the unit.
Go to step 5.
If the climatic circuit breaker of the AC box cannot be reset:

a. Disconnect the AC wires related to the C-DACS (see
).
b. Reset the climatic circuit breaker of the AC box.
In the case of a new break, replace the climatic circuit

breaker of the AC box (Field Replaceable Unit).
Refer to 411-9001-084 (Nortel GSM BTS S8002
Additional checks

411-9001-103 18.06 20 January 2010
507

Check the state of the C-DACS climatic system by performing

If the state of the "compact dacs cooler" equipment is still


Clear the alarm.

--End--
2.12.37 CMCF board (source: MCF_MCF)

Fault number 1067
Equipment:
Source:
(9502729 or 12779529 or 12845065) MCF_MCF
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates a loss of link between the active board and the
passive board.
BSC defense
None.
CAUTION
There is no impact on the service unless there is a fault on the
other CMCF board. The service will then be lost.

411-9001-103 18.06 20 January 2010
508
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the CMCF board is valid, by


411-9001-103 18.06 20 January 2010
509
If the state of the "CMCF" equipment is "failed", the fault is

If the state of the "CMCF" equipment is "working", the fault is

If there are BISTs on the board, note their state by performing a

"Display data configuration" command on the btsSiteManager
object.
In this case, look at the result displayed in the "Session log"
window and send these to the manufacturer with the faulty
board.
Replace the faulty CMCF board (Field Replaceable Unit). Refer

to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Go to step 5.
Additional checks

Check the state of the CMCF board by performing a "Display

If the state of the "CMCF" equipment is still "failed", call the

manufacturer.
If the state of the "CMCF" equipment is "working", go to step

7.
Clear the alarm.

--End--

411-9001-103 18.06 20 January 2010
510
2.12.38 CMCF board (source: Slave downloading error)

Fault number 1067
Equipment:
Source:
(9568250 or 12845050 or 12910586) Slave

downloading error
BTS model:

+ S8006
FAULT ANALYSIS
This alarm, sent by the active board, indicates an error during the update
of the passive board by the active one.
BSC defense
None.
The CBCF duplex mode is lost. The CBCF simplex mode continues to
function.
CAUTION
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
511

Procedures)).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the CMCF board is valid, by



On-site maintenance
Perform the following steps in the maintenance window of the

operator.
Remove the active board.
CAUTION
Service reduction
Wait for the BSC defense actions and its start-up.

411-9001-103 18.06 20 January 2010
512
Replace the newly passive CMCF board (Field Replaceable

Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Go to step 7.
Additional checks



manufacturer.

9.
Clear the alarm.
10

--End--
2.12.39 CMCF board (source: CMCF_ACT_DUPLEX_INHIBITED)

Fault number 1067
Equipment:
CMCF phase 1 or CMCF phase 2
Source:
(12779538 or 12845074) CMCF ACT DUPLEX

INHIBITED
BTS model:

+ S8006
FAULT ANALYSIS
This alarms is due to secured loop commissioning error on one BTS of
the loop.

411-9001-103 18.06 20 January 2010
513
This alarms indicates passive CMCF board is not commissioned

accordingly to the mode required (Secured Loop mode is asked while the
secured loop passive CMCF microswitch is not set).
BSC defense
None.
For the btsSiteManager object.
CAUTION
TROUBLESHOOTING
Step
Action
Preliminary checks




the alarm and do not clear it. Go to step 2.

"disabled-failed".
alarm persists.

411-9001-103 18.06 20 January 2010
514
Check that the Secured loop both CMCF microswitch (number

4) are correctly set by performing a "Display data information
/Normal" command on the faulty btsSiteManager.
Check the CMCF switch state in the session log window, "Switch
state" must be in "Secured loop mode" for active and passive
boards. Go to Step 4.
If the Switch state is in "Secured loop mode" for active and

passive boards. Go to Step 4.
If the Switch state is not in Secured loop mode, the CMCF

microswitch number 4 has to be set to ON. Go to Step 3
On-site maintenance
Refer to following technical documents to set passive CMCF

microswitch number 4 to on: "Follow Chapter : replacement of a
CMCF board"
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Go to step 4.
Additional checks


/Normal" command on the btsSiteManager.
Check the CMCF switch state in the session log window,

"Switch state" must be in "Secured loop mode" for active

411-9001-103 18.06 20 January 2010
515
and passive boards. If the state of the "CMCF" equipment is


microswitch number 4 has to be set to ON. Call the
manufacturer.
Clear the alarm.

--End--
2.12.40 CMCF board (source: CMCF_ACT_ICST)

Fault number 1067
Equipment:
CMCF phase 1 or CMCF phase 2
Source:
(12779539 or 12845075) CMCF ACT ICST
BTS model:

+ S8006
FAULT ANALYSIS
This alarms is due to secured loop commissioning error on one BTS of
the loop.
This alarms indicates passive CMCF board is not commissioned
accordingly to the mode required (Secured Loop mode is asked while the
secured loop passive CMCF microswitch is not set).
BSC defense
None.
For the btsSiteManager object.
CAUTION
As long as the operationalState of the btsSiteManager object is
"disabled-- failed", the site is lost. No service is provided.
TROUBLESHOOTING
411-9001-103 18.06 20 January 2010
516
Step
Action
Preliminary checks




the alarm and do not clear it. Go to step 2.

"disabled-failed".
alarm persists.

/Normal" command on the faulty btsSiteManager.
Check the CMCF switch state in the session log window, "Switch
state" must be in "Secured loop mode" for active and passive
boards. Go to Step 4.
If the Switch state be in "Secured loop mode" for active and

passive boards. Go to Step 4.

microswitch number 4 has to be set to ON. Go to Step 3
On-site maintenance
Refer to following technical documents to set passive CMCF

microswitch number 4 to on: Follow Chapter : replacement of a
CMCF board

411-9001-103 18.06 20 January 2010
517
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Go to step 4.
Additional checks
Perform a Lock / Unlock on faulty btsSiteManager



/Normal" command on the btsSiteManager.
Check the CMCF switch state in the session log window,

"Switch state" must be in "Secured loop mode" for active
and passive boards. If the state of the "CMCF" equipment is

microswitch number 4 has to be set to ON. Call the
manufacturer.
Clear the alarm.

--End--
2.12.41 CMCF board (source: Duplex inhibited: feature not supported

on CMCF phase 1)
Fault number 1067
Equipment:
CMCF phase 1
Source:
(12779540) Duplex inhibited: feature not supported

on CMCF phase 1
BTS model:
FAULT ANALYSIS

411-9001-103 18.06 20 January 2010
518
The alarm 1067 with cause 12779540 is sent in two different cases:
Case 1: The CMCF phase 1 board does not support the GPS and the
BTS (master/slave) synchronization features.
The alarm indicates that a CMCF phase 1 board has been plugged
in a BTS configured for synchronization features such as GPS
synchronization or BTS (master/slave) synchronization.
GPS and BTS synchronization features are not allowed in case of

mixed configurations (the active is CMCF phase 2 and passive is
CMCF phase 1) and so the CBCF duplex mode is lost.
As the CMCF phase 1 board does not support synchronization

features, CBCF BTS must only have CMCF phase 2 boards.
The alarm is cleared when the CMCF phase 1 board is plugged

out.
Case 2: The CMCF phase 1 board does not support the Dynamic Abis
feature (which is only compatible with CBCF with CMCF phase 2).
If a passive CMCF phase 1 board is plugged with an active CMCF

phase 2 board, the duplex functionality is inhibited and an alarm
1067 cause 12779540 Duplex inhibited: feature not supported by
CMCF phase 1 is sent on the CMCF phase 1 board.
The fault is cleared when the CMCF phase 1 board is plugged out.
In case a Display data information action is launched at the
OMC-R in this situation, the site Dynamic Abis capability and the
site Dynamic Abis state information are inconsistent.
BSC defense
None.
The CBCF duplex mode is lost. The CBCF simplex mode continues to
function.
CAUTION
active CMCF board. The service will then be lost.
TROUBLESHOOTING
411-9001-103 18.06 20 January 2010
Step
519
Action
Preliminary checks



Procedures)).

becomes "enabled".

"disabled", the site is no operational.
"disabled-failed".
alarm persists.
Check that the alarm on the CMCF board is valid by performing

a "Display hardware information" command mode Standard on
the btsSiteManager object.



411-9001-103 18.06 20 January 2010
520

On-site maintenance
Replace the CMCF Phase 1 board with a CMCF Phase 2 board

(Field Replaceable Unit):
refer to Nortel GSM BTS S8000/S8003 Troubleshooting

(411-9001-048) for the BTS S8000
refer to Nortel GSM BTS S8002 Troubleshooting

(411-9001-084) for the BTS S8002
refer to Nortel GSM BTS S8000/S8003 Troubleshooting

(411-9001-048) for the BTS S8003
refer to Nortel GSM BTS S8006 Troubleshooting

(411-9001-085) for the BTS S8006
Go to step 4.
Additional checks


hardware information" command mode Standard on the

manufacturer.

6.
Clear the alarm.

--End--
2.12.42 Combiner duplexer LNA or combiner H2 LNA (source: LNA

fault)
Fault number 1067
Equipment:
combiner duplexer lna or combiner h2 lna (LNA)
Source:
(5570561) LNA fault
BTS model:

+ S8006
FAULT ANALYSIS

411-9001-103 18.06 20 January 2010
521

This alarm indicates a hardware problem on the low noise amplifier. The
related reception path (main or diversity) is no longer operational for all
the TRXs using the faulty LNA. However, if the other path is still correct,
these TRXs run in a degraded mode.
BSC defense
If there is no reception path, the BSC unconfigures the transceiver
Equipment objects corresponding to the faulty LNA. One or several
transceiverEquipment objects can be lost.
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).


411-9001-103 18.06 20 January 2010
522

becomes "enabled".

"disabled-failed".
alarm persists.
Check the state of F-type converters by performing a "Display

If the state of the "converter F" equipment is "failed", go to

step 4.
If the state of the "converter F" equipment is "working", go to

step 3.
Check that the alarm on the combiner duplexer LNA is valid, by

If the state of the "LNA" equipment is "failed", the fault is

If the state of the "LNA" equipment is "working", the fault is

Look for alarms concerning the F-type converters and process

them.

If the circuit breaker powering the PA is in the "O" position, put it

in the "I" position. Go to step 7.
If the operationalState of the bts object is "disabled" and its

availabilityStatus is "dependency", set the administrativeState of

411-9001-103 18.06 20 January 2010
523
the bts object to "locked", and set the administrativeState of the

associated transceiverEquipment objects to "locked".
7
Replace the RF-combiner (Field Replaceable Unit) associated

with the LNA-combiner. Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Check the cable between the LNA and the connection panel.
For the ALCO board of the S8000 BTS, refer to

411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting)
For the RECAL board of the S8000 BTS, refer to

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


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

10
or RECAL board.

step 11.

411-9001-103 18.06 20 January 2010
524

Additional checks
11
12

Check the state of the equipment by performing a "Display

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

13.
13
Clear the alarm.
14

--End--
2.12.43 Combiner duplexer VSWR or combiner H2 VSWR (source:

VSWR level 1)
Fault number 1067
Equipment:
combiner duplexer vswr or combiner h2 vswr

(VSWR)
Source:
BTS model:

+ S8006
FAULT ANALYSIS

BSC defense
None.
None.

VSWR level 2)
Fault number 1067
Equipment:


411-9001-103 18.06 20 January 2010
525
Source:
BTS model:

+ S8006
FAULT ANALYSIS

BSC defense
None.
None.

VSWR level 3)
Fault number 1067
Equipment:
Source:
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates that the radio link is interrupted in the transmission
direction for all the TRXs using the corresponding antenna. These TRXs
are no longer operational.

BSC defense The BSC unconfigures the transceiverEquipment objects
connected to the RF-combiner that has detected the fault.
CAUTION
Service reduction
CAUTION

411-9001-103 18.06 20 January 2010
526
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the combiner D / H2D VSWR is valid, by




411-9001-103 18.06 20 January 2010
527

Note the contents of the additional fields in the notifications and

send these, if any, to the manufacturer with the faulty item.
Check the cable between the associated RF-combiner and the

interconnection panel.
Replace the associated RF-combiner (Field Replaceable Unit).

Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS

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

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


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


411-9001-103 18.06 20 January 2010
528

8
Check the cable between the interconnection panel and the

ALCO or RECAL board.
If necessary, set the administrativeState of the bts and

transceiverEquipment objects to "unlocked". Go to step 10.
Additional checks
10
11


If the state of the "SWR" equipment is still "failed", call the

manufacturer.
If the state of the "SWR" equipment is "working", go to step

12.
12
Clear the alarm.
13

--End--
2.12.46 Combiner H4D LNA (source: LNA fault)

Fault number 1067
Equipment:
combiner h4 lna (LNA)
Source:
(7405569) LNA fault
BTS model:
FAULT ANALYSIS

411-9001-103 18.06 20 January 2010
529
related reception path (main or diversity) is not operational for all the TRXs
using the faulty LNA. However, if the other path is still correct, these TRXs
run in a degraded mode.

corresponding to the faulty LNA. One or several transceiverEquipment
objects can be lost.
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

becomes "enabled".


411-9001-103 18.06 20 January 2010
530

"disabled-failed".
alarm persists.


step 4.

step 3.
Check that the alarm on the combiner duplexer LNA is valid, by




them.

If the circuit breaker powering the PA is in the "O" position, put it

in the "I" position. Go to step 7.


with the LNA-combiner. Refer to 411-9001-048 (Nortel GSM BTS

411-9001-103 18.06 20 January 2010
531

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

411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting).
10
or RECAL board.

step 11.
Additional checks
11
12



manufacturer.

13.
13
Clear the alarm.
14

--End--

411-9001-103 18.06 20 January 2010
532
2.12.47 Combiner H4D VSWR (source: VSWR level 1)

Fault number 1067
Equipment:
combiner h4 vswr (VSWR)
Source:
BTS model:
FAULT ANALYSIS

BSC defense
None.
None.
TROUBLESHOOTING
Step
Action
Preliminary checks



object.
alarm persists.
Check that the alarm on the combiner H4D VSWR is valid, by


411-9001-103 18.06 20 January 2010
533




Check the cabling between the associated RF-combiner and the

antenna.
In the case of three alarms with source: level 1, source: level 2,

and source: level 3, replace the associated RF-combiner (Field
If necessary, set the administrativeState of the bts object to

"unlocked". Go to step 8.
Additional checks



manufacturer.

10.
10
Clear the alarm.
11

--End--

411-9001-103 18.06 20 January 2010
534

Fault number 1067
Equipment:
Source:
BTS model:
FAULT ANALYSIS

BSC defense
None.
None.
TROUBLESHOOTING
Step
Action
Preliminary checks



object.
alarm persists.


411-9001-103 18.06 20 January 2010
535




Check the cabling between the associated RF-combiner and the

antenna.
In the case of three alarms with source: level 1, source: level 2,

and source: level 3, replace the associated RF-combiner (Field
If necessary, set the administrativeState of the bts object to

"unlocked". Go to step 8.
Additional checks



manufacturer.

10.
10
Clear the alarm.
11

--End--

411-9001-103 18.06 20 January 2010
536

Fault number 1067
Equipment:
Source:
BTS model:
FAULT ANALYSIS
This alarm indicates that the radio link is interrupted in the transmission
direction for all the TRXs using the corresponding antenna. These TRXs
are no longer operational.

connected to the RF-combiner that has detected the fault.
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).


411-9001-103 18.06 20 January 2010
537

becomes "enabled".

"disabled-failed".
alarm persists.





Check the cable between the associated RF-combiner and the

Replace the associated RF-combiner (Field Replaceable

Unit). Refer to 411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting).


411-9001-103 18.06 20 January 2010
538

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

411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting).
Check the cable between the interconnection panel and the

ALCO or RECAL board.
If necessary, set the administrativeState of the bts and

transceiverEquipment objects to "unlocked". Go to step 10.
Additional checks
10
11



manufacturer.

12.
12
Clear the alarm.
13

--End--
2.12.50 Compact distribution system (source: Main breaker)

Fault number 1067
Equipment:

compact distribution

411-9001-103 18.06 20 January 2010
Source:
(7995393) Main breaker
BTS model:
S8002
539
FAULT ANALYSIS
This alarm appears when the cabinet main breaker is disengaged after an
internal short-circuit in the cabinet.
The cabinet then operates on its batteries. The fault number 1067 with the
source "Battery on discharges" on the rectifier equipment is displayed.

BSC defense
None.
CAUTION
If the problem is not corrected, the BTS can be lost.
If the BTS is lost, PCM faults will appear.
TROUBLESHOOTING
Step
Action
Preliminary checks



"enabled".



411-9001-103 18.06 20 January 2010
540




becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the compact distribution system is valid,

by performing a "Display hardware configuration" command on
the btsSiteManager object.
If the state of the "compact distribution" equipment is "failed",

If the state of the "compact distribution" equipment is

On-site maintenance


and go to step 5.
Put the main breaker in the "I" position.

411-9001-103 18.06 20 January 2010
541
If the mains supply is present and if the alarm persists,

replace the C-AC box (Field Replaceable Unit). Refer to
411-9001-084 (Nortel GSM BTS S8002 Troubleshooting). Go
to step 5.
Additional checks

Check the state of the compact distribution system by

If the state of the "compact distribution" equipment is still

If the state of the "compact distribution" equipment is

Clear the alarm.

--End--
2.12.51 CPCMI board (source: Major)

Fault number 1067
Equipment:
CPCMI
Source:
BTS model:

+ S8006

2.12.52 CPCMI board (source: Slave downloading error)

Fault number 1067
Equipment:
CPCMI
Source:
(9633786) Slave downloading error
BTS model:

+ S8006
FAULT ANALYSIS
411-9001-103 18.06 20 January 2010
542
This alarm indicates an error during the downloading sequence of the

CPCMI board by the active CMCF board.
BSC defense
The BSC unconfigures the btsSiteManager object to maintain a minimum
service of communication. This unconfiguration is displayed at the OMC-R
and is temporary. If a transceiverEquipment object is lost, the fault number
1061 appears.
If there is only one PCM link in service, the BTS is completely

unconfigured. If other BTSs are dropped with the faulty BTS, they are
also unconfigured.
If there are several PCM links declared in the configuration, only a part
of the BTS is lost. A fault number 1061 concerning the transceiver
object appears.
If there is a redundant CPCMI board, there is no impact on the service.

If two PCM links are used:
CAUTION
Service reduction
If one PCM link is used:
CAUTION
The service is lost.
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010


543

Procedures)).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the CPCMI board is valid, by

If the state of the "CPCMI" equipment is "failed", the fault is

If the state of the "CPCMI" equipment is "working", the fault is

On-site maintenance
Replace the faulty CPCMI board (Field Replaceable Unit). Refer

to:

411-9001-103 18.06 20 January 2010
544
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Go to step 4.
Additional checks

Check the state of the CPCMI board by performing a "Display

If the state of the "CPCMI" equipment is still "failed", call the

manufacturer.
If the state of the "CPCMI" equipment is "working", go to step

6.
Clear the alarm.

--End--
2.12.53 CSWM board

(source: Fault on active-passive CSWM link or on passive CSWM)
Fault number 1067
Equipment:
CSWM
Source:
(4259849) Fault on active-passive CSWM link or

passive CSWM
BTS model:
FAULT ANALYSIS
This alarm indicates a hardware or software failing on the passive CSWM
board. There is no longer a connection between the active and passive
CSWM board.

411-9001-103 18.06 20 January 2010
545

BSC defense
None.
CAUTION
other CSWM board.
The service will then be lost.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

becomes "enabled".

"disabled-failed".
alarm persists.

411-9001-103 18.06 20 January 2010
546
Check that the alarm on the CSWM board is valid, by

If the state of the "CSWM" equipment is "failed", the fault is

If the state of the "CSWM" equipment is "working", the fault is

Location
The board indicated in the notification is the faulty board.
If there are BISTs on the board, note their state by performing a

"Display data configuration" command on the btsSiteManager
object.
Look at the result displayed in the "Session log" window and
send these to the manufacturer with the faulty board.
Replace the faulty CSWM board (Field Replaceable Unit).

Additional checks

Check the state of the CSWM board by performing a "Display

If the state of the "CSWM" equipment is still "failed", call the

manufacturer.
If the state of the "CSWM" equipment is "working", go to step

8.
Clear the alarm.

--End--

411-9001-103 18.06 20 January 2010
547
2.12.54 CSWM board (source: Slave downloading error)

Fault number 1067
Equipment:
CSWM
Source:
BTS model:
FAULT ANALYSIS
This alarm, sent by the detector board, indicates an error during the
update of the passive board by the active board.

BSC defense
None.
Impact on the service The BCF duplex mode is lost. The BCF simplex
mode continues to function.
CAUTION
other CSWM board.
The service will then be lost.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).


411-9001-103 18.06 20 January 2010
548
becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the CSWM board is valid, by

If the state of the "CSWM" equipment is "failed", the fault is

If the state of the "CSWM" equipment is "working", the fault is

Fault location
The board indicated in the notification is the faulty board.
On-site maintenance
If the faulty CSWM board is the active one, go to step 5.

Set the btsSiteManager object to "locked".
Set the btsSiteManager object to "unlocked".


Additional checks


411-9001-103 18.06 20 January 2010
549
Check the state of the CSWM board by performing a "Display

If the state of the "CSWM" equipment is still "failed", call the

manufacturer.
If the state of the "CSWM" equipment is "working", go to step

10.
10
Clear the alarm.
11

--End--
2.12.55 DACS climatic system (source: Dirty filter)

Fault number 1067
Equipment:
dacsCooler
Source:
(7864321) Dirty filter
BTS model:
S8000 Outdoor + S8006
FAULT ANALYSIS
This alarm occurs when the DACS filter is clogged.
BSC defense
As soon as the (H)(e)PA temperature is over 60C, the (H)(e)PA are
powered off, and the BSC unconfigures the transceiverEquipment objects.
There is no impact on the service until the BTS and (H)(e)PA overheat.
CAUTION
Service reduction

411-9001-103 18.06 20 January 2010
550
CAUTION
Intervention on the site must be within one week.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the DACS climatic system is valid, by

411-9001-103 18.06 20 January 2010
551
If the state of the "dacsCooler" equipment is "failed", the fault

If the state of the "dacsCooler" equipment is "working", the

On-site maintenance
Replace the filter (Field Replaceable Unit).
For the S8000 BTS, refer to 411-9001-048 (Nortel GSM BTS


S8006 Troubleshooting)
Go to step 4.
Additional checks

Check the state of the DACS climatic system by performing

If the state of the "dacsCooler" equipment is still "failed", call

the manufacturer.
If the state of the "dacsCooler" equipment is "working", go to

step 6.
Clear the alarm.

--End--
2.12.56 DACS climatic system (source: DACS failed)

Fault number 1067
Equipment:
dacsCooler
Source:
(7864322) DACS failed
BTS model:
FAULT ANALYSIS

411-9001-103 18.06 20 January 2010
552
This alarm indicates a problem on the DACS climatic system.

BSC defense
As soon as the (H)(e)PA temperature is over 60C, the (H)(e)PA is
powered off. The BSC unconfigures the transceiverEquipment objects.
There is no impact on the service until the BTS and (H)(e)PA overheat.
CAUTION
Service reduction
CAUTION
Intervention on the site must be within one week.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).


411-9001-103 18.06 20 January 2010
553
becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the DACS climatic system is valid, by

If the state of the "dacsCooler" equipment is "failed", the fault

If the state of the "dacsCooler" equipment is "working", the

On-site maintenance
Check that the fan circuit breakers are in the "I" position.
Breakers are located on the power supply rack (if present), GIPS
(if present) and the AC box (if present).
If they are in the "I" position, go to step 5.

If they are in the "O" position, go to step 4.
Reset the circuit breakers.
If the L2/CB2 circuit breaker can not be reset:

a. Disconnect the DC wires related to the DACS (see
411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting) for the S8000 BTS or 411-9001-085
(Nortel GSM BTS S8006 Troubleshooting) for the S8006
BTS).
b. Reset the L2/CB2 circuit breaker of the power supply
rack.

411-9001-103 18.06 20 January 2010
554
If there is a new break, check the PCU output cables

of the power supply rack. Replace them (Shop
Otherwise, the operator can choose whether he

changes the DACS (Field Replaceable Unit) as
a whole or he replaces the faulty items (Field
Replaceable Units) of the DACS. In this case:
for the S8000 BTS, refer to 411-9001-048 (Nortel

GSM BTS S8000/S8003 Troubleshooting) to
detect and replace the faulty item.
for the S8006 BTS, refer to 411-9001-085 (Nortel

GSM BTS S8006 Troubleshooting) to detect and
replace the faulty item.
CAUTION
The personnel replacing faulty DACS
items must be well trained on the
functionalities of the unit, and authorized
to work according to security standards.
Go to step 5.
If the climatic circuit breaker of the AC box can not be reset:

a. Disconnect the AC wires related to the DACS (see
411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting) for the S8000 BTS or 411-9001-085
(Nortel GSM BTS S8006 Troubleshooting) for the S8006
BTS).
b. Reset the climatic circuit breaker of the AC box.
If there is a new break, replace the climatic circuit

breaker of the AC box (Field Replaceable Unit).
For the S8000 BTS, refer to 411-9001-048 (Nortel

GSM BTS S8000/S8003 Troubleshooting)
For the S8006 BTS, refer to 411-9001-085 (Nortel

GSM BTS S8006 Troubleshooting)
Go to step 4.
Additional checks
Perform the following steps:
Check the DACS thermostat state.

If the thermostat is tripped, re-activate it (refer to step 9).

411-9001-103 18.06 20 January 2010
555
a. If the alarm has disappeared, go to step 8.

b. If the alarm persists, go to step 6.
6
Check the state of the DACS climatic system by performing

If the state of the "dacsCooler" equipment is still "failed", call

the manufacturer.
If the state of the "dacsCooler" equipment is "working", go to

step 7.
Clear the alarm.
Re-activation of the DACS thermostat.
Intervention time
a. The intervention time is approximately 20 minutes.
Tools required
a. Stepladder
b. Flat screwdriver
c. Allen wrench
Impact of the replacement on service
DANGER
Electric shock
The BTS does not remain supplied with the mains
power supply, so take care while handling the
equipment.
Location
a. The DACS thermostat is located on the following figure.
a Safety instructions
CAUTION
Wear the antistatic bracelet when performing the
following maintenance procedure.
b Preliminary operations
1. Open the hood and the doors of the cabinet.
2. Put the battery circuit breaker in the "O" position.

411-9001-103 18.06 20 January 2010
556
3. Put the main circuit breaker in the "O" position.

4. Put the "FAN" breakers in the "O" position.
5. Unscrew the four quarter turn fasteners of the DACS
cover and carefully remove it.
c Re-activation of the thermostat
1. Press the red button which is located at the top of the
thermostat.
The thermostat is located between the blowers. It is fixed
on the heater cover (refer to the following figure).
d Additional operations
1. Replace the DACS cover and screw its eight 1/4 turn
fasteners.
2. Put the "FAN" breakers in the "I" position.
3. Put the main circuit breaker in the "I" position.
4. Put the battery circuit breaker in the "I" position.
5. Close the doors and the hood of the cabinet.
10
Clear the alarm.
11

--End--

411-9001-103 18.06 20 January 2010
Figure 1
S8000 Outdoor BTS and S8006 BTS DACS thermostat re-activation
2.12.57 Distribution system (source: Main breaker)

Fault number 1067
Equipment:

Distribution system

411-9001-103 18.06 20 January 2010
557
558
Source:
(5767169) Main breaker
BTS model:
S8000 Outdoor + S8002 + S8006
FAULT ANALYSIS
This alarm appears when the cabinet main breaker is disengaged after an
internal short-circuit in the cabinet.
The cabinet is operating on its batteries, if any. The fault number 1060
with the source "Battery on discharges" is displayed, and may be followed
by a source "External battery level 1" if the batteries are discharged (see
the fault number 1060 source "External battery level 1").
BSC defense
None.
CAUTION
If the problem is not corrected, the BTS can be lost.
If the BTS is lost, PCM faults will appear.
TROUBLESHOOTING
Step
Action
Preliminary checks



"enabled".

411-9001-103 18.06 20 January 2010
559






becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the distribution system is valid, by

If the state of the "distribution system" equipment is "failed",

If the state of the "distribution system" equipment is

On-site maintenance
Check the mains power supply on the operator box, or on the

"Battery and Interface" module, if it is used.

411-9001-103 18.06 20 January 2010
560


and go to step 5.
Put the main breaker in the "I" position.
If the mains supply is present and if the alarm persists,

replace the main breaker (Field Replaceable Unit).
For the S8000 BTS, refer to 411-9001-048 (Nortel GSM
BTS S8002 Troubleshooting).
Go to step 4.
Additional checks

Check the state of the distribution system by performing

If the state of the "distribution system" equipment is still

If the state of the "distribution system" equipment is

Clear the alarm.

--End--
2.12.58 DRX or DRX-ND3 diversity reception chain (source: Software

detection)
Fault number 1067
Equipment:

DRX or DRX-ND3 diversity reception chain

411-9001-103 18.06 20 January 2010
561
Source:
(6946817) Software detection
BTS model:

+ S8006
This alarm is treated by either performing the following procedure or by

performing the procedure associated with the TIL and described in:
411-9001-048 (Nortel GSM BTS S8000/S8003 Troubleshooting) for the

S8000/S8003 BTS
411-9001-084 (Nortel GSM BTS S8002 Troubleshooting) for the S8002

BTS

BTS
FAULT ANALYSIS
This alarm indicates that the DRX or DRX-ND3 detects a received signal
level difference between the main path and the diversity path.
If the maximum of the two levels is higher than -110dB, and the difference
between the two levels is higher than 20dB, the path that has the lower
level is declared faulty.
As soon as the path which has been declared faulty has a signal level
higher than -110dB, or has a signal slightly lower than the signal level of
the other path, the faulty path is declared operational.
BSC defense
None.
CAUTION
Service reduction
The service is not lost but it is degraded: the cellular area has
been decreased.
TROUBLESHOOTING

411-9001-103 18.06 20 January 2010
562
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the DRX or DRX-ND3 module is valid,


411-9001-103 18.06 20 January 2010
563
If the state of the "DRX or DRX-ND3 diversity reception

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

chain" equipment is "working", the fault is not confirmed. Go
to step 9.
On-site maintenance
Check the antenna reception route: RF-combiner, Rx-splitter,

DRX or DRX-ND3.
If any cables have been removed, re-insert them. Go to step

4.
Check that the cables and the connectors are correctly tightened.
If the cables are not correctly tightened, tighten them.

If the cables are correctly tightened and if the alarm persists,

go to step 5. Otherwise, go to step 10.
Replace the DRX or DRX-ND3 module (Field Replaceable Unit).

Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Analyze the alarm.

Replace the RF-combiner (Field Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS

411-9001-103 18.06 20 January 2010
564
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Analyze the alarm.
If the alarm persists, replace the Rx-splitter (Field

Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8006 BTS
Go to step 7.
Additional checks

Check the state of the DRX or DRX-ND3 module by performing


chain" equipment is still "failed", call the manufacturer.

chain" equipment is "working", go to step 9.
Clear the alarm.
10

--End--

411-9001-103 18.06 20 January 2010
565
2.12.59 DRX or DRX-ND3 main reception chain (source: Software

detection)
Fault number 1067
Equipment:
DRX or DRX-ND3 main reception chain
Source:
(6881281) Software detection
BTS model:

+ S8006


S8000/S8003 BTS

BTS

BTS
FAULT ANALYSIS
This alarm indicates that the DRX or DRX-ND3 detects a received signal
level difference between the main path and the diversity path.
If the maximum of the two levels is higher than -110dB, and the difference
between the two levels is higher than 20dB, the path that has the lower
level is declared faulty.
As soon as the path which has been declared faulty has a signal level
higher than -110dB, or has a signal slightly lower than the signal level of
the other path, the faulty path is declared operational.
BSC defense
None.
CAUTION
Service reduction
The service is not lost but it is degraded: the cellular area is
decreased.

411-9001-103 18.06 20 January 2010
566
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.


411-9001-103 18.06 20 January 2010
567
If the state of the "DRX or DRX-ND3 main reception chain"

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

equipment is "working", the fault is not confirmed. Go to step
9.
On-site maintenance
Check the antenna reception route: RF-combiner, Rx-splitter,

DRX or DRX-ND3.
If any cables have been removed, re-insert them. Go to step

4.
Check that the cables and the connectors are correctly tightened.
If the cables are not correctly tightened, tighten them.

If the cables are correctly tightened and if the alarm persists,

go to step 5. Otherwise, go to step 10.

Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Analyze the alarm.

Replace the RF-combiner (Field Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS

411-9001-103 18.06 20 January 2010
568
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Analyze the alarm.
If the alarm persists, replace the Rx-splitter (Field

411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8002 BTS
for the S8003 BTS
for the S8006 BTS
Go to step 7.
Additional checks



equipment is still "failed", call the manufacturer.

equipment is "working", go to step 9.
Clear the alarm.
10

--End--

411-9001-103 18.06 20 January 2010
569
2.12.60 DRX or DRX-ND3 modules (source: Abis satellite not supported

DRX (ND3))
Fault number 1067
Equipment:
DRX or DRX-ND3
Source:
9437214: Abis satellite not supported DRX
Source:
12976158: Abis satellite not supported DRX ND3
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates a hardware incompatibility: the "satellite" BTS is
equipped with either DRX or DRX ND3, whereas it must be equipped
with eDRX only, to be able to support the Abis satellite interface (optional
feature).
BSC defense
After the CBCF has sent an "Enable TRX Ack" message with the
availability status set to "Unavailable", the configuration of the TRX is
stopped at BSC level.
At least one DRX or DRX-ND3 is unavailable.
TROUBLESHOOTING
Replace the DRX or DRX ND3 with eDRX. Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003 Troubleshooting) for

the S8000 BTS

BTS

the S8003 BTS

BTS

411-9001-103 18.06 20 January 2010
570
2.12.61 DRX or DRX-ND3 modules (source: HePA not supported)

Fault number 1067
Equipment:
DRX or DRX-ND3
Source:
(9437212) HePA not supported
BTS model:
S8000 Indoor + S8000 Outdoor + S8002 + S8003
FAULT ANALYSIS
This alarm indicates an HePA installation has been attempted on a DRX or
DRX-ND3. Only eDRX supports HePA.
BSC defense
None.
None.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).


411-9001-103 18.06 20 January 2010
571

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the DRX or DRX-ND3 is valid, by

If the state of the "DRX or DRX-ND3" equipment is "failed",

If the state of the "DRX or DRX-ND3" equipment is "working",

In the case of an S8000 BTS, perform a "Display" command on

the bts object.
The "standardIndicator" parameter indicates the frequency
band associated with the DRX or DRX-ND3 module: "gsm", "
gsm850", "dcs1800", "pcs1900", "R gsm", "gsmdcs" or "dcsgsm".

DRX or DRX-ND3 is "gsm850".
DRX or DRX-ND3 is PCS.


411-9001-103 18.06 20 January 2010
572

DRX or DRX-ND3 is GSM.
DRX or DRX-ND3 is DCS.


Replace the HePA with a PA. Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003

Otherwise, replace the DRX with an eDRX. Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003

Additional checks

Check the state of the DRX or DRX-ND3 by performing


411-9001-103 18.06 20 January 2010
573
If the state of the "DRX or DRX-ND3" equipment is still


go to step 9.
Clear the alarm.
10

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

Fault number 1067
Equipment:
DRX or DRX-ND3
Source:
9437211 or 12582939: PA config. exceeded
BTS model:
FAULT ANALYSIS
This alarm indicates either:
the maximum supported configuration for the HePA/PA has been

reached; the DRX or DRX-ND3 (s) in excess of the supported
configuration cannot be connected.
an HePA installation has been attempted on the S8000 BTS with BCF.
The S8000 BTS with BCF does not support HePA.

BSC defense
None.
None.
TROUBLESHOOTING
Step
Action
Preliminary checks

411-9001-103 18.06 20 January 2010
574


Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the DRX or DRX-ND3 is valid, by




the bts object.

411-9001-103 18.06 20 January 2010
575






For the S8000 BTS with BCF, replace the HePA with a PA. Refer
to:
411-9001-048 (Nortel GSM BTS S8000/S8003

Troubleshooting)
Otherwise, replace an HePA(s) of the cabinet with PA(s) until the

HePA/PA configuration is supported. The replaced HePA can
be the HePA of a DRX or DRX-ND3 that has been successfully
connected. Refer to:

411-9001-103 18.06 20 January 2010
576
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003

Additional checks

Check the state of the DRX or DRX-ND3 by performing


"failed", ensure the maximum supported configuration has not
been reached. Otherwise, call the manufacturer.

go to step 9.
Clear the alarm.
10

--End--
2.12.63 DRX or eDRX or DRX-ND3 modules (source: BBFILTER ASIC

fault)
Fault number 1067
Equipment:
DRX or eDRX or DRX-ND3
Source:
9437190 or 12582918 or 12976134: BBFILTER

ASIC fault
BTS model:

+ S8006


411-9001-103 18.06 20 January 2010
577

S8000/S8003 BTS

BTS

BTS
FAULT ANALYSIS
This alarm indicates a hardware problem.
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 DRX or DRX-ND3 is lost.
CAUTION
Service reduction
The cell linked to the faulty DRX or DRX-ND3 can be lost.
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
578

Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.




the bts object.


411-9001-103 18.06 20 January 2010
579





Set the administrativeState of the transceiverEquipment object

corresponding to the faulty DRX or DRX-ND3 to "locked".
CAUTION
Service reduction
transceiver objects are lost.
Disconnect the PWR cable on the front panel of the DRX

(DRXICO side).

Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS

411-9001-103 18.06 20 January 2010
580
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS

corresponding to the faulty DRX or DRX-ND3 to "unlocked". Go
to step 9.
Additional checks
10




go to step 11.
11
Clear the alarm.
12

--End--
2.12.64 DRX or eDRX or DRX-ND3 modules (source: The TX has not

acknowledged the power consign request)
Fault number 1067
Equipment:
Source:
9437216 or 12582944 or 12976160: The TX has

not ack the power consign request
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates that the power, configured at the OMC-R for the DRX
or eDRX or DRX-ND3 concerned, is not compatible with the DRX or eDRX
or DRX-ND3 hardware.

411-9001-103 18.06 20 January 2010
581
BSC defense
The BSC configures the transceiver equipment, but the associated
transceiver object is not configured.
CAUTION
Service reduction
CAUTION
Intervention on the site must be immediate: there is a risk of
service loss.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".


411-9001-103 18.06 20 January 2010
582

"disabled-failed".
alarm persists.
Perform a "Display" command on the bts object to check if the

cells are concentric.
If the "concentric cell" parameter is "monozone", go to step 3.

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 value to the attenuation of the combiner must be between
31dBm and 44dBm, or 32dBm at the band limit for only GSM
1900.

to the value to the attenuation of the combiner must be

on the btsSiteManager object.
The following table defines the correct values of the
the BTS. The "Nack" value is not allowed.

411-9001-103 18.06 20 January 2010
Combiners
TxF/D
H2D
H4D
DLU
attenuation
51
44
Nack
Nack
Nack
43
Pmax
Nack
Nack
42
Pmax
Nack
Nack
41
Pmax-2
Nack
Nack
40
Pmax-2
Pmax
Nack
39
Pmax-4
Pmax
Nack
38
Pmax-4
Pmax-2
Nack
37
Pmax-6
Pmax-2
Nack
36
Pmax-6
Pmax-4
Pmax
35
Pmax-8
Pmax-4
Pmax
34
Pmax-8
Pmax-6
Pmax-2
33
Pmax-10
Pmax-6
Pmax-2
32
Pmax-10
Pmax-8
Pmax-4
31
Pmax-12
Pmax-8
Pmax-4
30
Pmax-12
Pmax-10
Pmax-6
29
Nack
Pmax-10
Pmax-6
28
Nack
Pmax-12
Pmax-8
27
Nack
Pmax-12
Pmax-8
26
Nack
Nack
Pmax-10
25
Nack
Nack
Pmax-10
24
Nack
Nack
Pmax-12
23
Nack
Nack
Pmax-12
22 0
Nack
Nack
Nack
bsTxPwrMax
583

If the value is correct, replace the DRX or DRX-ND3 (Field
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8002 BTS

411-9001-103 18.06 20 January 2010
584
411-9001-048 (Nortel GSM BTS S8000/S8003

for the S8006 BTS
Go to step 6.
4
Modify the value of the "bsTxPwrMax" parameter according to


the value to the attenuation of the combiner and reduced of
the value of the "transceiver zone Ref" parameter must be
between 31dBm and 44dBm, or 32dBm at the band limit for
only GSM 1900.

to the value to the attenuation of the combiner and reduced
of the value of the "transceiver zone Ref" parameter must be

The "transceiver zone Ref" parameter is obtained by performing
a "Display" command on the transceiver object.
on the btsSiteManager object. This parameter must not be filled
in for the "dual band" or "dual coupling" values of the "concentric
cell" parameter.
The preceding table defines the correct values of the
the BTS. The "Nack" value is not allowed. The "transceiver zone
Ref" parameter should also be verified.

If the value is correct, replace the DRX or DRX-ND3 (Field
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8002 BTS
for the S8003 BTS
for the S8006 BTS
Go to step 5.

411-9001-103 18.06 20 January 2010
585
Additional checks
Clear the alarm.
Set the bts object to "locked".
Set the bts object to "unlocked".

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

Fault number 1067
Equipment:
Source:
9437185 or 12582913 or 12976129: RX fault
BTS model:

+ S8006
It is possible to treat this alarm either by performing the following

procedure or by performing the procedure associated with the TIL and
described in:

the S8000 BTS

the S8003 BTS

BTS

BTS
FAULT ANALYSIS
The TRX is no longer operational.
BSC defense
associated transceiver object. The BSC tries to assure a minimum service
of communication by unconfiguring and reconfiguring the transceiver
object.

411-9001-103 18.06 20 January 2010
586

CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

becomes "enabled".

"disabled-failed".
alarm persists.

411-9001-103 18.06 20 January 2010
587




the bts object.






411-9001-103 18.06 20 January 2010
588

corresponding to the faulty DRX or DRX-ND3 to "locked".
CAUTION
Service reduction
transceiver are lost.

(DRXICO side).
Check the fuse of the DRX INTERCO unit.
If it correct, replace the faulty DRX or DRX-ND3 module

(Field Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8006 BTS
Go to step 10.

step 8.

corresponding to the faulty DRX or DRX-ND3 to "unlocked". Go
to step 9.
Additional checks
10


11


go to step 11.
Clear the alarm.

411-9001-103 18.06 20 January 2010
12
589

--End--
2.12.66 DRX or eDRX or DRX-ND3 modules (source: L1M first config

failed)
Fault number 1067
Equipment:
Source:
9437488 or 12583216 or 12976432 or 15204656:

L1M first config failed
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates that an anomaly has been detected in an L1M
configuration. One new configuration is allowed after clearing the TRX
configuration
BSC defense
An automatic reconfiguration defense action is triggered by the BSC.
TROUBLESHOOTING

first config failed)
Fault number 1067
Equipment:
Source:
9437456 or 12583184 or 12976400 or 15204624:

BCCH first config failed
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates that an anomaly has been detected in a BCCH
configuration.

411-9001-103 18.06 20 January 2010
590
BSC defense
TROUBLESHOOTING

second config failed)
Fault number 1067
Equipment:
Source:
9437457 or 12583185 or 12976401 or 15204625:

BCCH second config failed
BTS model:

+ S8006
FAULT ANALYSIS
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, then unlock it.
Lock the affected bts object, then unlock it.

If the problem persists, call the manufacturer.

--End--

411-9001-103 18.06 20 January 2010
591

link)
Fault number 1067
Equipment:
Source:
9437206 or 12582934 or 12976150 or 15204374:

DRX link
BTS model:

+ S8006


S8000/S8003 BTS

BTS

BTS
FAULT ANALYSIS
This alarm indicates that the BCF has detected the loss or
non-establishment of the dialogue with the DRX or eDRX or DRX-ND3 or
eDRX2.
BSC defense
At least one DRX or eDRX or DRX-ND3 or eDRX2 is lost.
CAUTION
Service reduction
The cell linked to the faulty DRX or eDRX or DRX-ND3 or
eDRX2 can be lost.
TROUBLESHOOTING

411-9001-103 18.06 20 January 2010
592
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the DRX or eDRX or DRX-ND3 or

eDRX2 module is valid, by performing a "Display hardware
configuration" command on the transceiverEquipment object.
If the state of the DRX or eDRX or DRX-ND3 or eDRX2


25.

411-9001-103 18.06 20 January 2010
593

the bts object.
band associated with the DRX or eDRX or DRX-ND3 or eDRX2
module: "gsm", " gsm850", "dcs1800", "pcs1900", "R gsm",
"gsmdcs" or "dcsgsm".

DRX or eDRX or DRX-ND3 or eDRX2 is "gsm850".
DRX or eDRX or DRX-ND3 or eDRX2 is PCS.


DRX or eDRX or DRX-ND3 or eDRX2 is GSM.
DRX or eDRX or DRX-ND3 or eDRX2 is DCS.



corresponding to the faulty DRX or eDRX or DRX-ND3 or eDRX2
to "locked".
CAUTION
Service reduction

411-9001-103 18.06 20 January 2010
594
Check the cable between the DRX or eDRX or DRX-ND3 or

eDRX2 and the DRXICO.
Replace the faulty DRX or eDRX or DRX-ND3 or eDRX2 module

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


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS

to "unlocked".

For a BTS with BCF, go to step 10. For a BTS with CBCF, go
to step 20.
10
Check the state of the GTW board by performing a "Display data

configuration" command on the btsSiteManager.

If it is not correct, perform a switchover of the GTW boards.
11
Replace the GTW board (Field Replaceable Unit). Refer to


if the alarm persists, go to step 12.
12
If there is one redundant DSC board, go to step 13. Otherwise,

go to step 17.
13
Look for the DSC connected to the faulty DRX or DRX-ND3.

411-9001-103 18.06 20 January 2010
14

btsSiteManager object to check the number of available DSC
boards.
15
Perform a "Display data configuration" command on the

btsSiteManager to check which DSC board is faulty.
16
Reset the faulty DSC board.
17
595
If the problem persists, go to step 17.

Replace the DSC board (Field Replaceable Unit). Refer to

CAUTION
If there is not any redundant DSC board, the service
is lost.
18

if the alarm persists, go to step 18.
Perform a switchover of the CSWM boards.

19

20
Check the cable between the CBCF and the DRX or DRX-ND3.

21
Perform a switchover of the CMCF boards.
22

Replace the CMCF board (Field Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS

411-9001-103 18.06 20 January 2010
596
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Go to step 23.
Additional checks
23
24

Check the state of the DRX or eDRX or DRX-ND3 or eDRX2

module by performing a "Display hardware configuration"


25
Clear the alarm.
26

--End--

reset by BSC)
Fault number 1067
Equipment:
Source:
(9437219 or 12582947 or 12976163 or 15204387:

DRX link NOK after reset requested by BSC
BTS model:

+ S8006
FAULT ANALYSIS
This message indicates a reset of the DRX or DRX-ND3 by the BSC.

411-9001-103 18.06 20 January 2010
597
2.12.71 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: L1M

Fault number 1067
Equipment:
Source:
9437489 or 12583217 or 12976433 or 15204657:

L1M second config failed
BTS model:

+ S8006
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--
2.12.72 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Major

fault on TX)
Fault number 1067
Equipment:
Source:
9437194 or 12582922 or 12976138 or 15204362:

Major fault on TX
BTS model:

+ S8006


411-9001-103 18.06 20 January 2010
598

S8000/S8003 BTS

BTS

BTS
FAULT ANALYSIS
This alarm indicates a problem on the DRX or eDRX or DRX-ND3.
For eDRX2, this is a PSU alarm or a PPL out of lock.
BSC defense
CAUTION
Service reduction
eDRX2 can be lost.
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
599

Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.



13.

the bts object.


411-9001-103 18.06 20 January 2010
600






to "locked".
CAUTION
Service reduction

(DRXICO side).
Check the fuse of the DRX INTERCO unit.
If it is correct, replace the faulty DRX or eDRX or DRX-ND3

or eDRX2 module (Field Replaceable Unit). Refer to:

411-9001-103 18.06 20 January 2010
601
411-9001-048 (Nortel GSM BTS S8000/S8003

for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8006 BTS
Go to step 9.

to "unlocked".

step 9.

Replace the (H)(e)PA module (Field Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
10
Check the cable between the (H)(e)PA and the DRX or eDRX
or DRX-ND3 or eDRX2.

step 11.
Additional checks
11


411-9001-103 18.06 20 January 2010
602
12



13
Clear the alarm.
14

--End--
2.12.73 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: Nack

answer)
Fault number 1067
Equipment:
Source:
9437218 or 12582946 or 12976162 or 15204386:

DRX reset by BCF after message non ack.
BTS model:

+ S8006
FAULT ANALYSIS
This message indicates a software anomaly between the BCF and the
DRX or DRX-ND3 or eDRX2.
Call the next level of support.
2.12.74 DRX or eDRX or DRX-ND3 or eDRX2 modules (source: PA DRX

control loop fault)
Fault number 1067
Equipment:
Source:
9437217 or 12582945 or 12976161 or 15204385:

PA DRX control loop fault
BTS model:

+ S8006

411-9001-103 18.06 20 January 2010
603
ATTENTION

S8000/S8003 BTS
411-9001-084 (Nortel GSM BTS S8002 Troubleshooting) for the S8002 BTS
FAULT ANALYSIS
This alarm indicates that the (H)(e)PA emission power - (e,ND3)DRX/(H)(e
)PA control loop configuration has not succeeded.
BSC defense
CAUTION
Service reduction
eDRX2 can be lost.
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
604

Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.



14.

the bts object.


411-9001-103 18.06 20 January 2010
605



DRX or eDRX or DRX-ND3 or eDRX2is GSM.



to "locked". Go to step 6.
CAUTION
Service reduction
Check the cable between the BCF and the DRX or eDRX or
DRX-ND3 or eDRX2.
If it is correct, disconnect the PWR cable on the front panel of

the DRX (DRXICO side). Go to step 7.

Analyze the alarm.

411-9001-103 18.06 20 January 2010
606
Replace the faulty DRX or eDRX or DRX-ND3 or eDRX2 module

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


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS

to "unlocked".
Analyze the alarm.

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


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Analyze the alarm.
10
Check the RF cable between the DRX or eDRX or DRX-ND3 or

eDRX2 and the (H)(e)PA.
11
If it is disconnected, reconnect it.

step 11.
Perform a lock/unlock of the impacted DRX after replacing or

reconnecting the RF cable, in order to recover the service. Go
to step 12.

411-9001-103 18.06 20 January 2010
607
Additional checks
12
13




14
Clear the alarm.
15

--End--
2.12.75 DRX or eDRX or DRX-ND3 or eDRX2 modules (source:

Post-mortem dump zone 3)
Fault number 1067
Equipment:
Source:
9437427 or 12583155 or 12976371 or 15204595: Post-mortem

dump zone 3
BTS model:
FAULT ANALYSIS
This source indicates a post-mortem dump zone 3.

first config failed)
Fault number 1067
Equipment:
Source:
9437472 or 12583200 or 12976416 or 15204640:

SACCH first config failed
BTS model:

+ S8006
FAULT ANALYSIS

411-9001-103 18.06 20 January 2010
608
This alarm indicates that an anomaly has been detected in an SACCH

configuration
BSC defense
TROUBLESHOOTING

Fault number 1067
Equipment:
Source:
9437473 or 12583201 or 12976417 or 15204641:

SACCH second config failed
BTS model:
S8000 Indoor + S8000 Outdoor + S8002 + S8003 +

S8006
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



411-9001-103 18.06 20 January 2010
609

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

test failed)
Fault number 1067
Equipment:
Source:
9437193 or 12582921 or 12976137 or 15204361:

Self test failed
BTS model:

+ S8006


S8000/S8003 BTS

BTS

BTS
FAULT ANALYSIS
This alarm indicates a problem in the hardware self-test of the DRX or
eDRX or DRX-ND3, or eDRX2.
BSC defense

411-9001-103 18.06 20 January 2010
610
CAUTION
Service reduction
eDRX2 can be lost.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.

411-9001-103 18.06 20 January 2010
611



13.

the bts object.





411-9001-103 18.06 20 January 2010
612


corresponding to the faultyDRX or eDRX or DRX-ND3 or eDRX2
to "locked".
CAUTION
Service reduction
transceiver object are lost.

(DRXICO side).
Replace the DRX or eDRX or DRX-ND3 or eDRX2 module (Field

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


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Set the transceiverEquipment object corresponding to the faulty

DRX or eDRX or DRX-ND3 or eDRX2 to "unlocked".

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


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS

411-9001-103 18.06 20 January 2010
10
613
Check the cable between the (H)(e)PA and the DRX or eDRX
or DRX-ND3 or eDRX2.

step 11.
Additional checks
11
12



If the state of the DRX or eDRX or DRX-ND3 or

eDRX2equipment is "working", go to step 13.
13
Clear the alarm.
14

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

anymore configured)
Fault number 1067
Equipment:
Source:
9502719 or 12648447 or 13041663 or 15269887:

TRX not anymore configured
BTS model:

+ S8006
FAULT ANALYSIS
This message indicates an abnormal state change of a DRX or eDRX or
DRX-ND3 or eDRX2, caused by a software problem.

411-9001-103 18.06 20 January 2010
614
BSC defense
CAUTION
Service reduction
The service is not lost but it is degraded: the cellular area is
decreased.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".


411-9001-103 18.06 20 January 2010
615

"disabled-failed".
alarm persists.

eDRX2module is valid by performing a "Display hardware

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

6.
Perform the following actions:
Set the transceiverEquipment object to "locked".

Set the transceiverEquipment object to "unlocked".
Additional checks




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

--End--

411-9001-103 18.06 20 January 2010
616
2.12.80 DSC boards (source: Major fault)

Fault number 1067
Equipment:
DSC
Source:
BTS model:
FAULT ANALYSIS
This alarm indicates a hardware or software failing on the DSC board.
There is no longer a connection between the active CSWM board and the
concerned DSC board.
In the case of monolapd and redundancy of the DSC board, there is no

BSC defense action.
In the case of monolapd and non-redundancy of the DSC board, the

BSC unconfigures all the objects and sends a fault number 1054.
In the case of multilapd and redundancy of the DSC board, there is no

BSC defense action.
In the case of multilapd and non-redundancy of the DSC board, the

BSC unconfigures some transceiverEquipment objects.
In the case of monolapd and redundancy of the DSC board, there is

no impact on the service.
In the case of monolapd and non-redundancy of the DSC board:
CAUTION
In the case of multilapd and redundancy of the DSC board, there is


CAUTION
The service is reduced or lost.

411-9001-103 18.06 20 January 2010
617
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the DSC board is valid, by performing

If the state of the "DSC" equipment is "failed", the fault is

If the state of the "DSC" equipment is "working", the fault is


411-9001-103 18.06 20 January 2010
618

Location
The equipment number specified in the alarm identifies the faulty

DSC board.
On-site maintenance
Replace the faulty DSC board (Field Replaceable Unit). Refer to

Additional checks

Check the state of the DSC board by performing a "Display

If the state of the "DSC" equipment is still "failed", call the

manufacturer.
If the state of the "DSC" equipment is "working", go to step 7.
Clear the alarm.

--End--
2.12.81 DSC boards (source: Channel_HSCX)

Fault number 1067
Equipment:
DSC
Source:
(4456453) Channel_HSCX
BTS model:

This alarm indicates problems concerning self-tests of the DSC board.
This problem cannot be detected while the board is functioning. The
self-tests occur when the board is reset or when the board starts up.
In the case of monolapd and redundancy of the DSC board, there is no

BSC defense action.
In the case of monolapd and non-redundancy of the DSC board, the

BSC unconfigures all the objects and sends a fault number 1054.

411-9001-103 18.06 20 January 2010
619
In the case of multilapd and redundancy of the DSC board, there is no

BSC defense action.

In the case of monolapd and redundancy of the DSC board, there is

In the case of monolapd and non-redundancy of the DSC board:
CAUTION
In the case of multilapd and redundancy of the DSC board, there is


CAUTION
The service is reduced or lost.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

411-9001-103 18.06 20 January 2010
620

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the DSC board is valid, by performing

If the state of the "DSC" equipment is "failed", the fault is

If the state of the "DSC" equipment is "working", the fault is

On-site maintenance
Replace the faulty board (Field Replaceable Unit). Refer to

Additional checks

Check the state of the DSC board by performing a "Display

If the state of the "DSC" equipment is still "failed", call the

manufacturer.
If the state of the "DSC" equipment is "working", go to step 6.
Clear the alarm.

411-9001-103 18.06 20 January 2010
621

--End--
2.12.82 External alarm (source: Alarm)

Fault number 1067
Equipment:
external alarm
Source:
(7274497) Alarm
BTS model:

+ S8006
A supervised external alarm has been detected.. The maintenance action

depends on how the user deals with the alarm. Sixteen external alarms
can be used for each cabinet.
2.12.83 Fan of the base cabinet (source: Cabinet fan fault)

Fault number 1067
Equipment:
cabinet fan
Source:
(6225921) Cabinet fan fault
BTS model:
S8000 Indoor + S8003
FAULT ANALYSIS
This alarm is detected by the ALCO (S8000) or RECAL (S8000 and
S8003) board.
For the S8000 Indoor BTS, this alarm indicates that a base cabinet fan
is faulty.
For the S8003 BTS, this alarm indicates that an abnormally high
temperature level has been reached in the cabinet.
There is an increase in the internal temperature of the BTS base cabinet
until the (H)(e)PAs are powered off at 60C.
BSC defense
If the (H)(e)PAs are powered off, the BSC unconfigures the

411-9001-103 18.06 20 January 2010
622
CAUTION
Service reduction
CAUTION
TROUBLESHOOTING
Step
Action
Preliminary checks



"enabled".







411-9001-103 18.06 20 January 2010
623

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the fan is valid, by performing a "Display

If the state of the "cabinet fan" equipment is "failed", the fault

is confirmed. Go to step 3 (S8000 Indoor BTS) or step 6
(S8003 BTS).
If the state of the "cabinet fan" equipment is "working", the

On-site maintenance for the S8000 Indoor BTS


and go to step 6.
Check the state of the fuse.
step 8.
Replace the faulty fan (Field Replaceable Unit). Refer to

Go to step 8.
On-site maintenance for the S8003 BTS
Check the date of the last air filter replacement. If the filter has
not been replaced within the past six months, replace it. Refer to

411-9001-103 18.06 20 January 2010
624

Go to step 7.
7
Check the state of the fans (Refer to Nortel GSM BTS

S8000/S8003 Troubleshooting (411-9001-048)).
If it is not correct, replace the faulty fan(s) (Field Replaceable
Additional checks

Check the state of the fan by performing a "Display hardware

configuration" command on the btsSiteManager object.
If the state of the "cabinet fan" equipment is still "failed", call

the manufacturer.
If the state of the "cabinet fan" equipment is "working", go to

step 10.
10
Clear the alarm.
11

--End--
2.12.84 F-type converters (source: Volt)

Fault number 1067
Equipment:
converter F
Source:
(5308417) Volt
BTS model:

+ S8006
FAULT ANALYSIS
In this alarm, the equipment number indicates which of the two power
supplies is concerned by the alarm.

411-9001-103 18.06 20 January 2010
625
BSC defense
If the second F-type converter is optional, the BTS detects

alarms on the LNA and the VSWR: the BSC unconfigures the
transceiverEquipment and transceiver objects connected to the LNA
and VSWR.
If the second F-type converter is present and if another fault occurs on

the other, the BSC unconfigures the bts, transceiverEquipment and
transceiver objects.
CAUTION
The service is either reduced or lost.
TROUBLESHOOTING
Step
Action
Preliminary checks



"enabled".



411-9001-103 18.06 20 January 2010
626




becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the F-type converter module is valid, by

If the state of the "converter F" equipment is "failed", the fault

If the state of the "converter F" equipment is "working", the

On-site maintenance


and go to step 11.
Check if there are alarms on all combiner VSWRs and on all

combiner LNAs.

411-9001-103 18.06 20 January 2010
If there are no alarms, go to step 5.

If there are alarms, go to step 10.
Check if, at the same time, the (H)(e)PAs are still powered.
627
If they are not, go to step 6.

If they are, go to step 7.
Check the state of the PA breaker (on the PCU for the rectifier
shelf; on the DCU for the GIPS). If necessary, put it in the "I"
position.
Wait for the end of BSC defense actions. Go to step 11.
Check that the switch on the front panel of the F-type converter
is in the "I" position and that the green led is lit.
If they are, go to step 8.

If they are not, replace the F-type converter (Field
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8006 BTS
Put the switch of the new F-type converter in the "I" position.
Go to step 11.
Put the switch of the F-type converter in the "O" position and
check the fuse in the (H)(e)PA INTERCO unit.
If the fuse is faulty, replace it (Shop Replaceable Unit). Go

to step 10.
If the fuse is correct, go to step 9.
Check the cabling.
10

If it is not correct, replace the cable (Shop Replaceable Unit).
Go to step 11.
Replace the F-type converter (Field Replaceable Unit). Refer to:

411-9001-103 18.06 20 January 2010
628
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


the S8006 BTS
Put the switch of the new F-type converter in the "I" position. Go
to step 11.
Additional checks
11
12


If the state of the "converter F" equipment is still "failed", call

the manufacturer.

step 13.
13
Clear the alarm.
14

--End--
2.12.85 GTW boards (source: Major fault on GTW)

Fault number 1067
Equipment:
GTW
Source:
(4587521) Major fault on GTW
BTS model:
FAULT ANALYSIS
This alarm indicates a hardware or software failing on the GTW board.
There is no longer a connection between the active CSWM board and the
concerned GTW board.

411-9001-103 18.06 20 January 2010
629

BSC defense
None.
CAUTION
If there is a redundant board, all the DRX or DRX-ND3s of the
site are not lost.
However, if there is an alarm on each GTW board, all the DRX
or DRX-ND3 of the site are lost.
CAUTION
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

becomes "enabled".


411-9001-103 18.06 20 January 2010
630

"disabled-failed".
alarm persists.
Check that the alarm on the GTW board is valid, by performing

If the state of the "GTW" equipment is "failed", the fault is

If the state of the "GTW" equipment is "working", the fault is

Location
The equipment number specified in the alarm identifies the faulty

GTW board.
On-site maintenance
Check the alarms on each DRX or DRX-ND3 of the BTS.
If there is an "DRX or DRX-ND3 link" notification on each

DRX or DRX-ND3, the problem concerns the BCF.
Check that there is an active GTW board.
If there is, reset it.
If there is not, reset one of the two boards.
Ensure that one board becomes active.
If there is an alarm on only one DRX or DRX-ND3, go to step

5.
If there are no alarms on the DRX or DRX-ND3s, go to step

6.
Replace the DRX or DRX-ND3 (Field Replaceable Unit). Refer to


Replace the GTW board (Field Replaceable Unit). Refer to



411-9001-103 18.06 20 January 2010
631
Perform a switchover of the CSWM boards.

If the alarm has disappeared, the problem concerns the
previous active CSWM board. Go to step 8.
Replace the previous CSWM active board (Field Replaceable

Additional checks
10

Check the state of the GTW board by performing a "Display

If the state of the "GTW" equipment is still "failed", call the

manufacturer.
If the state of the "GTW" equipment is "working", go to step

11.
11
Clear the alarm.
12

--End--
2.12.86 Internal batteries (source: Battery disconnected)

Fault number 1067
Equipment:
internal battery system
Source:
(5439489) Battery disconnected
BTS model:
FAULT ANALYSIS
This alarm is triggered by an internal battery problem or by a connection
problem between the PCU and the batteries.
BSC defense

411-9001-103 18.06 20 January 2010
632
In principle, there is no defense action.

But if there is a power supply cut, the BSC unconfigures the
btsSiteManager object: all the object states change (the btsSiteManager,
bts and transceiverEquipment objects become "disabled-dependency", and
the pcmCircuit of the ABIS link becomes "disabled-failed").
CAUTION
Service reduction
If the BSC unconfigures the BTS, the service is reduced.
TROUBLESHOOTING
Step
Action
Preliminary checks



"enabled".


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




411-9001-103 18.06 20 January 2010
633

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the internal batteries is valid, by

If the state of the "internal battery system" equipment is

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

On-site maintenance

BSS Fault Clearing - Advanced Maintenance Procedures) ).

and go to step 6.
Check the state of the circuit breaker of the internal batteries.
If the circuit breakers of the batteries are not in the "I"

position, put them in the "I" position.
If there is a new break, go to step 5.
If the circuit breakers of the batteries are in the "I" position,

go to step 4.

411-9001-103 18.06 20 January 2010
634
Check the internal batteries (see 411-9001-048 (Nortel GSM

BTS S8000/S8003 Troubleshooting) for the S8000 BTS or
411-9001-084 (Nortel GSM BTS S8002 Troubleshooting) for the
S8002 BTS).
If the test is failed, replace the internal batteries (Field

411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8002 BTS
Go to step 6.
If the test is correct, disconnect the cables of the internal

batteries. Go to step 6.
Additional checks

Check the state of the internal batteries by performing a "Display

If the state of the "internal battery system" equipment is still


Clear the alarm.

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

Fault number 1067
Equipment:
IP synchro
Source:
(15859968) Unable to lock on IP synchronization
BTS model:
S8000 Indoor + S8000 Outdoor

411-9001-103 18.06 20 January 2010
635
FAULT ANALYSIS
The IPM-USER generates an "Unable to lock" event in case the
IPM-USER synchronization module cannot reach a frequency, locked
within an appropriate delay.
The begin-of fault alarm indicates that the counter "unlocked_state_counte
r" reaches a confirmation threshold.
The end-of-fault alarm indicates that the counter "unlocked_state_counter"
is reset.
The causes for this alarm are:
The network impairment rate is too high for the clock recovery
algorithm to lock. This is the most probable cause.
The IPM-USER local oscillator has experienced a large frequency

skew with age. It is no more able to lock to the BSC reference clock
within its nominal tuning range.
The IPM-USER local oscillator is not stable enough, probably due to

thermal variations.

BSC defense
None.
None.
TROUBLESHOOTING
Procedure 3
Preliminary checks
Step
Action
Check that the alarm on the IPM-USER is valid by performing a

"Display hardware information" command on the IPM object.
ATTENTION
The "Display hardware information" command is not available if a
BTS inventory is already running on the btsSiteManager object.

If the state of the "IPM" equipment is failed, the fault is
confirmed.

411-9001-103 18.06 20 January 2010
636
If the state of the "IPM" equipment is "working", the fault is not

Check the alarm state in the "Current Alarm list" window, and
make sure the alarm has disappeared. The alarm disappears
when the counter "unlock_state_counter" is reset.
Clear the alarm, if still present.

--End--
2.12.88 IP synchro (source: Not enough synchronization packets have

been received)
Equipment:
IP synchro
Source:
(15859969) Not enough synchronization packets have been received
BTS model:
FAULT ANALYSIS
The IPM-USER generates a "CRPN drop rate" alarm if it detects an
unacceptable drop rate in the CRPn (Nortel Clock Recovery Protocol)
flow. The network drop rate is too high for the clock recovery algorithm to
operate with the required precision.
The begin-of fault alarm indicates that the counter "CRPN_High_drop_rate
reaches the confirmation threshold.
The end-of fault alarm indicates that the counter "CRPN_High_drop_rate
is reset.

BSC defense
None.
None.

411-9001-103 18.06 20 January 2010
637
TROUBLESHOOTING
Procedure 4
Preliminary checks
Step
Action

ATTENTION

If the state of the "IPM" equipment is failed, the fault is
confirmed.
If the state of the "IPM" equipment is "working", the fault is not
make sure the alarm has disappeared. The alarm disappears
when the counter "unlock_state_counter" is reset.

--End--
2.12.89 IPM-USER commissioning (source: Only one IBOS

commissioned at IPM)
Fault number 1067
Equipment:
Source:
(15663140) Only one IBOS commissioned at IPM
BTS model:
FAULT ANALYSIS
The IPM-USER generates this alarm if only one IBOS is commissioned.

BSC defense
None.
None.
411-9001-103 18.06 20 January 2010
638
TROUBLESHOOTING
Procedure 5
Preliminary checks
Step
Action

ATTENTION
If the state of the "IPM" equipment is "failed", the fault is

confirmed.
If the state of the "IPM" equipment is "working", the fault is

Contact the TAS to recommission the IPM-USER.
make sure the alarm has disappeared.

--End--
2.12.90 IPM-USER commissioning (source: DNS resolution has failed

for at least one IBOS)
Fault number 1067
Equipment:
Source:
(15663141) DNS resolution has failed for at least one IBOS
BTS model:
FAULT ANALYSIS
The IPM-USER generates this alarm if the DNS resolution has failed for at
least one IBOS.

BSC defense
None.
411-9001-103 18.06 20 January 2010
639
None.
TROUBLESHOOTING
Procedure 6
Preliminary checks
Step
Action

ATTENTION

confirmed.

Contact the TAS to recommission the IPM-USER.

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

Fault number 1067
Equipment:
IPM-USER core
Source:
(15728672) IPM BIST failed
BTS model:
FAULT ANALYSIS
This alarm indicates a BIST failed for the IPM-USER.

BSC defense
None.
411-9001-103 18.06 20 January 2010
640
None.
TROUBLESHOOTING
Procedure 7
Preliminary checks
Step
Action

ATTENTION

confirmed.

Replace the IPM-USER.

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

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

Fault number 1067
Equipment:
IPM-USER core
Source:
(15728675) Temperature
BTS model:
FAULT ANALYSIS
This alarm indicates an excessively high temperature on an IPM-USER.

BSC defense

411-9001-103 18.06 20 January 2010
641
None.
None.
TROUBLESHOOTING
Procedure 8
Preliminary checks
Step
Action

ATTENTION

confirmed.


(411-9001-048).

--End--
2.12.93 IPM-USER core (source: DAC unable to lock, synchronization

not possible)
Fault number 1067
Equipment:
IPM-USER core
Source:
(15728688) DAC unable to lock, synchronization not possible
BTS model:

411-9001-103 18.06 20 January 2010
642
FAULT ANALYSIS
The IPM-USER generates a "Frequency saturation" event in case the local
oscillator cannot be frequency-locked, within its operational tuning range.
The begin-of fault alarm indicates that the current value of the DAC
(Digital-to-Analog Converter) is not within a nominal range. The DAC
value is not within in this range for a time for that reaches the confirmation
threshold.
The end-of-fault alarm indicates that the current DAC value is within a
nominal range. The DAC value is within in this range for a time for that
The IPM-USER local oscillator has experienced a large frequency

within its nominal tuning range. This is the most probable cause.
The network reference frequency is in failure. This is the least probable

cause.

BSC defense
None.
None.
TROUBLESHOOTING
Procedure 9
Preliminary checks
Step
Action

ATTENTION

411-9001-103 18.06 20 January 2010
643

confirmed.


(411-9001-048).

--End--
2.12.94 Lightning protector (source: Lightning protection fault)

Fault number 1067
Equipment:
Lightning Protection
Source:
(6160385) Lightning protection fault
BTS model:
S8000 Outdoor + S8002 + S8006
FAULT ANALYSIS
This alarm indicates if the lightning protector is operational.
If the BTS operates on its batteries, the lightning protector is faulty.

If the BTS does not operate on its batteries, there is a problem of the
detector.

BSC defense
As long as the BTS works on batteries, there is no BSC defense action.
If the BTS is completely powered off, the BSC detects PCM faults
and unconfigures the btsSiteManager, bts, transceiverEquipment and
transceiver objects.
411-9001-103 18.06 20 January 2010
644
CAUTION
Intervention on the site must be immediate: it is possible to lose
the entire site (with potential damages).
TROUBLESHOOTING
Step
Action
Preliminary checks



"enabled".






becomes "enabled".


411-9001-103 18.06 20 January 2010
645

"disabled-failed".
alarm persists.
Check that the alarm on the lightning protector is valid, by

If the state of the "Lightning Protection" equipment is "failed",

If the state of the "Lightning Protection" equipment is

On-site maintenance
Perform a "Display" command on the btsSiteManager object to

check the value of the parameter "lightning protection".
If the value is "absent", set it to "present". Go to step 5.

If the value is "present", go to step 4.
Replace the lightning protector (Field Replaceable Unit).
For the S8000 BTSs, refer to 411-9001-048 (Nortel GSM BTS



Go to step 5.
Additional checks

Check the state of the lightning protector by performing


411-9001-103 18.06 20 January 2010
646
If the state of the "Lightning Protection" equipment is still

If the state of the "Lightning Protection" equipment is

Clear the alarm.

--End--
2.12.95 Not protected alarm (source: Alarm)

Fault number 1067
Equipment:
not protected alarm
Source:
(3735553) Alarm
BTS model:

+ S8006
If the alarm is external, the maintenance action depends on how the

user deals with the alarm. Sixteen external alarms can be used for each
cabinet.
2.12.96 Output Rx-splitter D (source: Over current)

Fault number 1067
Equipment:
rx splitter D
Source:
(9764865) Over current
BTS model:

+ S8006
ATTENTION

S8000 BTS
411-9001-084 (Nortel GSM BTS S8002 Troubleshooting) for the

S8002/S8003 BTS
FAULT ANALYSIS

411-9001-103 18.06 20 January 2010
647
This alarm corresponds to a fault in the reception amplifier of the diversity

path, located in the Rx-splitter. A current over consumption has been
detected on the diversity path. It can be due to a hardware problem on
the cable.
BSC defense
There is no BSC defense action until the fault occurs on the main path
on the Rx-splitter, at which point the BSC unconfigures at least one
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".


411-9001-103 18.06 20 January 2010
648

"disabled-failed".
alarm persists.
Check that the alarm on the output Rx-splitter D is valid, by

If the state of the "rx splitter D" equipment is "failed", the fault
If the state of the "rx splitter D" equipment is "working", the

On-site maintenance
Check the cabling between the DRX or DRX-ND3 and the

Rx-splitter.
If it is correct, replace the Rx-splitter (Field Replaceable Unit).

Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8006 BTS
Go to step 4.

Go to step 4.
Additional checks


411-9001-103 18.06 20 January 2010
649
Check the state of the output Rx-splitter D by performing

If the state of the "rx splitter D" equipment is still "failed", call
the manufacturer.
If the state of the "rx splitter D" equipment is "working", go to

step 6.
Clear the alarm.

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

Fault number 1067
Equipment:
rx splitter M
Source:
(9699329) Over current
BTS model:

+ S8006
ATTENTION

S8000/S8003 BTS
FAULT ANALYSIS
This alarm corresponds to a fault in the reception amplifier of the main
path, located in the Rx-splitter. A current over consumption has been
detected on the main path. It can be due to a hardware problem on the
cable.
BSC defense
There is no BSC defense action until the fault occurs on the diversity
path on the Rx-splitter, at which point the BSC unconfigures at least one

411-9001-103 18.06 20 January 2010
650
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.

411-9001-103 18.06 20 January 2010
651
Check that the alarm on the output Rx-splitter M is valid, by

If the state of the "rx splitter M" equipment is "failed", the fault
If the state of the "rx splitter M" equipment is "working", the

On-site maintenance
Check the cabling between the DRX or DRX-ND3 and the

Rx-splitter.
If it is correct, replace the Rx-splitter (Field Replaceable Unit).

Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8006 BTS
Go to step 4.

Go to step 4.
Additional checks

Check the state of the output Rx-splitter M by performing

If the state of the "rx splitter M" equipment is still "failed", call
the manufacturer.
If the state of the "rx splitter M" equipment is "working", go

to step 6.
Clear the alarm.

411-9001-103 18.06 20 January 2010
652

--End--
2.12.98 PCM (source: PCM)

Fault number 1067
Equipment:
PCM
Source:
(6488065) PCM
BTS model:

+ S8006
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 411-9001-105
(Nortel GSM BSS Fault Clearing - Advanced Maintenance Procedures)
2.12.99 PCMI boards (source: Major fault on PCMI)

Fault number 1067
Equipment:
PCMI
Source:
BTS model:

2.12.100 Power amplifiers (source: Hardware)

Fault number 1067
Equipment:
PA or ePA or HePA
Source:
6815745 or 12648449 or 12713985 Hardware
BTS model:

+ S8006


S8000/S8003 BTS

BTS

BTS
FAULT ANALYSIS
411-9001-103 18.06 20 January 2010
653
This alarm indicates a hardware failure of the (H)(e)PA. The corresponding

TRX is no longer operational.
BSC defense
The BSC unconfigures the transceiverEquipment object using the faulty
(H)(e)PA, at least one transceiver object (therefore one bts object).
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".


411-9001-103 18.06 20 January 2010
654

"disabled-failed".
alarm persists.
Check that the alarm on the power amplifier is valid, by

If the state of the "(H)(e)PA" equipment is "failed", the fault is

If the state of the "(H)(e)PA" equipment is "working", the fault

is not confirmed. Go to step 14.

the bts object.




411-9001-103 18.06 20 January 2010
655



Check that the switch on the front panel of the (H)(e)PA is in the
"I" position or that the power cable of the (H)(e)PA is connected
to the (H)(e)PA interconnections module.


a Set the transceiverEquipment object to "locked".
b Put the switch of the (H)(e)PA in the "I" position or
connect the power cable of the (H)(e)PA to the (H)(e)PA
c Set the transceiverEquipment object to "unlocked".
Check the state of the alarm.

Put the switch of the (H)(e)PA to the "O" position or disconnect

the power cable of the (H)(e)PA from the interconnections
module, and check the fuse of the (H)(e)PA INTERCO unit.
If the fuse is faulty, replace it (Shop Replaceable Unit).

a. Set the transceiverEquipment object to "locked".
b. Put the switch of the (H)(e)PA in the "I" position or
reconnect the power cable of the (H)(e)PA to the
(H)(e)PA interconnections module.
c. Set the transceiverEquipment object to "unlocked".

411-9001-103 18.06 20 January 2010
656
Check the fuse of the faulty (H)(e)PA.

a. Set the transceiverEquipment object to "locked".
b. Put the switch of the (H)(e)PA in the "I" position
or connect the power cable of the (H)(e)PA to the
interconnections module.
c. Set the transceiverEquipment object to "unlocked".

a Set the administrativeState of the transceiverEquipment
corresponding to the faulty (H)(e)PA to "locked".
b Replace the (H)(e)PA module (Field Replaceable Unit). Refer
to:
411-9001-048 (Nortel GSM BTS S8000/S8003


for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


for the S8006 BTS
c Set the administrativeState of the transceiverEquipment

corresponding to the faulty (H)(e)PA to "unlocked".

If the alarm persists, check the state of the power
amplifier by performing a "Display hardware configuration"
If the state of the "(H)(e)PA" equipment is still "failed",
go to step 10.
If the state of the "(H)(e)PA" equipment is "working",
go to step 14.

411-9001-103 18.06 20 January 2010
10
Check if there is a "Self test failed" alarm on the DRX or

DRX-ND3 connected to the (H)(e)PA.
11
657


b Remove the newly inserted (H)(e)PA module and reinsert the
old (H)(e)PA module.
c Replace the DRX or DRX-ND3 module (Field Replacement
Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


for the S8006 BTS
d Set the administrativeState of the transceiverEquipment


go to step 12.
go to step 13.
12

b Remove the newly inserted DRX or DRX-ND3 module and
reinsert the old DRX or DRX-ND3 module.
c Set the administrativeState of the transceiverEquipment
d Check the cables and the connectors between the (H)(e)PAs
and the DRX or DRX-ND3s.
411-9001-103 18.06 20 January 2010
658
If they are correctly tightened, go to step 13.

If they are not correctly tightened, tighten them.
Additional checks
13
Check the state of the power amplifier by performing a "Display

If the state of the "(H)(e)PA" equipment is still "failed", call the

manufacturer.
If the state of the "(H)(e)PA" equipment is "working", go to

step 14.
14
Clear the alarm.
15

--End--
2.12.101 Power amplifiers (source: DRX and PA connection)

Fault number 1067
Equipment:
PA or ePA or HePA
Source:
6815746 or 12648450 or 12713986: DRX and PA

connection
BTS model:

+ S8006


S8000/S8003 BTS

BTS

BTS
FAULT ANALYSIS
This alarm indicates that the numeric link is out of use between the DRX or
DRX-ND3 and the (H)(e)PA. The TRX is no longer operational.
411-9001-103 18.06 20 January 2010
659
BSC defense
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".


411-9001-103 18.06 20 January 2010
660

"disabled-failed".
b.

the alarm persists.
Check that the alarm on the power amplifier is valid, by




the bts object.




411-9001-103 18.06 20 January 2010
661



Ensure the switch on the front panel of the (H)(e)PA is in the "I"
position.

Put the switch of the (H)(e)PA in the "O" position or connect the
power cable of the (H)(e)PA to the interconnections module, and
check the fuse of the (H)(e)PA INTERCO unit.

Check the fuse of the faulty (H)(e)PA.


a
Set the administrativeState of the transceiverEquipment

Replace the (H)(e)PA module (Field Replaceable Unit).

Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


for the S8002 BTS

411-9001-103 18.06 20 January 2010
662
411-9001-048 (Nortel GSM BTS S8000/S8003


for the S8006 BTS


go to step 9.
go to step 13.

b
Remove the newly inserted (H)(e)PA module and reinsert the

old (H)(e)PA module.

Check the cables and the connectors between the (H)(e)PAs

and the DRX or DRX-ND3s.
If they are correctly tightened, go to step 10.

If they are not correctly tightened, tighten them.
10

a

Replace the DRX or DRX-ND3 module (Field Replacement

Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003


for the S8002 BTS

411-9001-103 18.06 20 January 2010
663
411-9001-048 (Nortel GSM BTS S8000/S8003


for the S8006 BTS

Go to step 11.
Additional checks
11
12



manufacturer.

step 13.
13
Clear the alarm.
14

--End--
2.12.102 Power amplifiers (source: High temperature )

Fault number 1067
Equipment:
PA or ePA or HePA
Source:
6815747 or 12648451 or 12713987: High temp
BTS model:

+ S8006


S8000/S8003 BTS

BTS

BTS

411-9001-103 18.06 20 January 2010
664
FAULT ANALYSIS
This alarm indicates an excessively high temperature on the (H)(e)PA.
BSC defense
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".


411-9001-103 18.06 20 January 2010
665

"disabled-failed".
b.

the alarm persists.
Check that the alarm on the power amplifier is valid by








411-9001-103 18.06 20 January 2010
666



Checks
Ensure the cabinet door is closed.
a
If it is closed, go to the next check.
If it is not closed, close it. Allow an appropriate amount of

time for the temperature to decrease. Go to step 7.
Check the running of the DACS climatic system (S8000 Outdoor)

or the Fan (S8000 Indoor, S8002, S8003, and S8006).
a
If it is correct, go to the next check.
If it is not correct, perform a corrective action on the DACS

(S8000 Outdoor) or the Fan (S8000 Indoor, S8002, S8003,
and S8006). Go to step 7.
FRU replacement
a Switch the transceiverEquipment object corresponding to the
faulty (H)(e)PA to "locked".
CAUTION
Service reduction
In most cases, the TRX and one TDMA are lost.
b Replace the faulty (H)(e)PA according to the replacement

procedure. Refer to:

411-9001-103 18.06 20 January 2010
667
411-9001-048 (Nortel GSM BTS S8000/S8003


for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


for the S8006 BTS
c Switch the transceiverEquipment object corresponding to the

replaced (H)(e)PA to "unlocked".
d
Make sure that the fault has been cleared (the alarms are
transferred to the alarm history file of the OMC-R).
Go to step 10.
Additional checks



manufacturer.

step 9.
Clear the alarm.
10

--End--
2.12.103 Power amplifiers (source: High Current )

Fault number 1067
Equipment:
PA or ePA or HePA
Source:
6815748 or 12648452 or 12713988: High Current
BTS model:

+ S8006


411-9001-103 18.06 20 January 2010
668

S8000/S8003 BTS

BTS

BTS
FAULT ANALYSIS
This alarm indicates errors concerning the (H)(e)PA power supply.
It concerns the following errors:
errors on the DC/DC converters of the (H)(e)PA

errors of an excessive power consumption of the (H)(e)PA

BSC defense
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
669

Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.






411-9001-103 18.06 20 January 2010
670





FRU replacement
a
Switch the transceiverEquipment object corresponding to the

CAUTION
Service reduction
Replace the faulty (H)(e)PA according to the replacement

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


for the S8002 BTS

411-9001-103 18.06 20 January 2010
671
411-9001-048 (Nortel GSM BTS S8000/S8003


for the S8006 BTS

Go to step 9.
Additional checks



manufacturer.

step 8.
Clear the alarm.

--End--
2.12.104 Power amplifiers (source: PA_PSDW )

Fault number 1067
Equipment:
PA or ePA or HePA
Source:
6815750 or 12648454 or 12713990: PA_PSDW
BTS model:

+ S8006


411-9001-103 18.06 20 January 2010
672

S8000/S8003 BTS

BTS

BTS
FAULT ANALYSIS
This alarm indicates an excessively high input level on the (H)(e)PA.
BSC defense
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

411-9001-103 18.06 20 January 2010
673

becomes "enabled".

"disabled-failed".
b.

the alarm persists.







411-9001-103 18.06 20 January 2010
674




Checks
a
Check the RF cables between the DRX or DRX-ND3 and the

(H)(e)PA.
If necessary tighten the RF cables.
CAUTION
Tightening torques
The tightening torque of the terminal "RF IN" must
be 0.7 N-m 0.1. Use the 8-mm SMA torque
wrench.
The tightening torque of the terminal "RF OUT"
must be 1.5 N-m 0.1. Use the 19-mm N torque
wrench.

If the alarm disappears, go to step 10.
FRU replacement
a

CAUTION
Service reduction

411-9001-103 18.06 20 January 2010
675
Replace the faulty (H)(e)PA according to the replacement

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


for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003


for the S8006 BTS

Go to step 10.
Additional checks



manufacturer.

step 9.
Clear the alarm.
10

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

Fault number 1067
Equipment:
PA
Source:
6815751: VSWR fault detected by PA
BTS model:

+ S8006

411-9001-103 18.06 20 January 2010
676
FAULT ANALYSIS
This alarm indicates that the PA has detected a VSWR fault and it has
stopped to emit.

using the faulty PA, at least one transceiver object (therefore one bts
object).
CAUTION
Service reduction
TROUBLESHOOTING
This alarm is treated by performing the procedure associated with the TIL
and described in:

the S8000 BTS

BTS

the S8003 BTS

BTS
2.12.106 RECAL board (source: Major)

Fault number 1067
Equipment:
RECAL
Source:
(9633793) Major
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates that the active CMCF board has lost the connection
with the RECAL board.
BSC defense
None.
411-9001-103 18.06 20 January 2010
677

The BTS no longer supervises the equipment linked to its RECAL board
(distribution system, rectifiers, F-type converters, internal batteries, climatic
system, LNA, VSWR, door contact, lightning protection, battery cabinet).
Therefore, the S12000 BTS service is not supervised, as the BTS cannot
inform the BSC.
CAUTION
There is a risk of service loss, even though the OMC-R does not
indicate any loss.
CAUTION
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

becomes "enabled".


411-9001-103 18.06 20 January 2010
678

"disabled-failed".
alarm persists.
Check that the alarm on the RECAL board is valid, by

If the state of the "RECAL" equipment is "failed", the fault is

If the state of the "RECAL" equipment is "working", the fault is

On-site maintenance
Check the RECAL board fuse on the CBCF front panel for the
S8000 Outdoor BTS or the RECAL/CBCF circuit breaker for the
S8000 Indoor BTS.
step 5.

with a voltmeter.

replace the RECAL board (Field Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8006 BTS

411-9001-103 18.06 20 January 2010
679
Go to step 5.
If the voltage is between -58V and -40V, replace the cable

(Shop Replaceable Unit) between the CBCF and the RECAL
board. Go to step 5.
Additional checks

Check the state of the RECAL board by performing a "Display

If the state of the "RECAL" equipment is still "failed", call the

manufacturer.
If the state of the "RECAL" equipment is "working", go to step

7.
Clear the alarm.

--End--
2.12.107 RECAL board (source: Slave downloading error)

Fault number 1067
Equipment:
RECAL
Source:
BTS model:

+ S8006
FAULT ANALYSIS
This alarm indicates an error during the downloading sequence of the
RECAL board by the active CMCF board.
BSC defense
None.

411-9001-103 18.06 20 January 2010
680
The BTS no longer supervises the equipment linked to its RECAL board
(distribution system, rectifiers, F-type converters, internal batteries, climatic
system, LNA, VSWR, door contact, lightning protection, battery cabinet).
Therefore, the S12000 BTS service is not supervised, as the BTS cannot
inform the BSC.
CAUTION
There is a risk of service loss, even though the OMC-R does not
indicate any loss.
CAUTION
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

becomes "enabled".


411-9001-103 18.06 20 January 2010
681

"disabled-failed".
alarm persists.
Check that the alarm on the RECAL board is valid, by

If the state of the "RECAL" equipment is "failed", the fault is

If the state of the "RECAL" equipment is "working", the fault is

On-site maintenance
Check the RECAL board fuse on the CBCF front panel for the
S8000 Outdoor BTS or the RECAL/CBCF circuit breaker for the
S8000 Indoor BTS.
step 5.

with a voltmeter.

replace the RECAL board (Field Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8002 BTS
411-9001-048 (Nortel GSM BTS S8000/S8003
for the S8006 BTS
Go to step 5.
If the voltage is between -58V and -40V, replace the cable

(Shop Replaceable Unit) between the CBCF and the RECAL
board. Go to step 5.

411-9001-103 18.06 20 January 2010
682

Additional checks

Check the state of the RECAL board by performing a "Display

If the state of the "RECAL" equipment is still "failed", call the

manufacturer.
If the state of the "RECAL" equipment is "working", go to step

7.
Clear the alarm.

--End--
2.12.108 Rectifiers (source: AC fault)

Fault number 1067
Equipment:
rectifier 48V
Source:
(5242881) AC fault
BTS model:
FAULT ANALYSIS
The cabinet may be operating on its batteries. If so, the fault number
1060 with source "Battery on discharges" is displayed. This is followed by
another source "External battery level 1" if the battery charge has dropped
below the 45V threshold (see source "External battery level 1").
If the cabinet is not operating on its batteries, the problem may be with
either the rectifiers, the link with the ALCO or RECAL board, or with the
ALCO or RECAL board itself.
BSC defense
As long as the BTS is powered on, there is no BSC defense action.

411-9001-103 18.06 20 January 2010
683
As soon as the BTS is not powered on, the BSC unconfigures the
btsSiteManager object or the bts site or the transceiverEquipment objects.
CAUTION
If the BTS is powered on, there is no impact. If the BTS is
powered off, the service is reduced and could be lost.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

becomes "enabled".

"disabled-failed".
alarm persists.

411-9001-103 18.06 20 January 2010
684
Check that the alarm on the rectifier is valid, by performing

If the state of the "rectifier 48V" equipment is "failed", the fault

If the state of the "rectifier 48V" equipment is "working", the

On-site maintenance
If the source is "AC fault" (always accompanied by a fault

notification with the source "DC fault"), check that the main circuit
breaker and the rectifier breaker are not in the "O" position.
If this is the case, put them in the "I" position. Go to step 4.

Check if the source "AC fault" is accompanied by a fault on the

climatic unit.
If this is the case, the AC power distribution system is

responsible. Solve the problem. Go to step 7.
Check that the red LED of the rectifier is on and the green LED
is off.
If it is, replace the rectifier (Field Replaceable Unit). Refer to:

411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting) for an S8000 BTS with rectifiers of the
six-rectifier type or for an S8000 BTS with rectifiers of the
seven-rectifier type
for the S8002 BTS
for the S8006 BTS
Go to step 8.
Check the power supply circuit between the main circuit breaker
and the rectifier breaker.
If it is correct, replace the rectifier (Field Replaceable Unit).

Refer to:

411-9001-103 18.06 20 January 2010
685
411-9001-048 (Nortel GSM BTS S8000/S8003

Troubleshooting) for an S8000 BTS with rectifiers of the
six-rectifier type or for an S8000 BTS with rectifiers of the
for the S8002 BTS
for the S8006 BTS
Go to step 8.
Check successively the main circuit breaker, the lightning

protector, the filters, and the external power supply circuits
between the site circuit breaker and cabinet.
If the main circuit breaker is not correct:

For an S8000 BTS, replace the main circuit breaker (Field
Replaceable Unit). Refer to 411-9001-048 (Nortel GSM
For an S8002 BTS, replace the C-AC box (Field
For an S8006 BTS, replace the main circuit breaker (Field
Go to step 8.
Otherwise, if the lightning protector is not correct, replace it

(Field Replaceable Unit).
For the S8000 BTSs, refer to 411-9001-048 (Nortel GSM
BTS S8000/S8003 Troubleshooting)
BTS S8002 Troubleshooting)
BTS S8006 Troubleshooting)
Go to step 8.
Otherwise, check the filters and the external power supply

circuits between the site circuit breaker and cabinet. Replace
them (Shop Replaceable Unit) if needed. Go to step 8.
Additional checks


411-9001-103 18.06 20 January 2010
686
Check the state of the rectifier by performing a "Display

If the state of the "rectifier 48V" equipment is still "failed", call

the manufacturer.
If the state of the "rectifier 48V" equipment is "working", go

to step 10.
10
Clear the alarm.
11

--End--
2.12.109 Rectifiers (source: DC fault)

Fault number 1067
Equipment:
rectifier 48V
Source:
(5242882) DC fault
BTS model:
FAULT ANALYSIS
If the only source is "DC fault" (no other fault notifications concerning the
rectifiers), there is a problem on one rectifier.
BSC defense
None.
None.
TROUBLESHOOTING
Step
Action
Preliminary checks


411-9001-103 18.06 20 January 2010


687

Procedures)).

becomes "enabled".

"disabled-failed".
alarm persists.



On-site maintenance
Identify the faulty rectifier by looking for the rectifier that has the
red led on and the green led off.
If this is not the case, replace the rectifier (Field Replaceable

Unit). Refer to:

411-9001-103 18.06 20 January 2010
688
411-9001-048 (Nortel GSM BTS S8000/S8003

Troubleshooting) for the S8000 BTS with rectifiers of the
six-rectifier type or for the S8000 BTS with rectifiers of the
for the S8002 BTS
for the S8006 BTS
Go to step 4.
If this is the case, call the manufacturer.
Additional checks



the manufacturer.

to step 6.
Clear the alarm.

--End--
2.12.110 Rectifiers (source: Over temperature)

Fault number 1067
Equipment:
rectifier 48V
Source:
(5242883) Over temperature
BTS model:
FAULT ANALYSIS
This alarm indicates a temperature problem on the rectifier. When the
temperature is equal to the threshold value (this value depends on each
rectifier and on the adjustment of the rectifier), the rectifier self-protects
and turns off.
411-9001-103 18.06 20 January 2010
689

BSC defense
As soon as the BTS is powered off, the BSC unconfigures the
btsSiteManager object, the bts object, or the transceiverEquipment objects.
CAUTION
If this alarm occurs on the base cabinet, there is a loss of
communications and the service is completely reduced.
CAUTION
If the cabinet has a redundant rectifier and if only on rectifier

is faulty, the cabinet continues to function. However, the
faulty rectifier must be replaced.
If the cabinet does not have a redundant rectifier, the

batteries take over from the faulty rectifier(s). Intervention
on the site depends on the discharge time of the batteries
(see 411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting) Paragraph 3.2.3.3).
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

411-9001-103 18.06 20 January 2010
690

becomes "enabled".

"disabled-failed".
alarm persists.



On-site maintenance
Replace the faulty rectifier (Field Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003

Troubleshooting) for the S8000 BTS with rectifiers of the
six-rectifier type or for the S8000 BTS with rectifiers of the

the S8002 BTS

the S8006 BTS
Additional checks


411-9001-103 18.06 20 January 2010
691


the manufacturer.

to step 6.
Clear the alarm.

--End--
2.12.111 Rectifiers (source: External battery level 1)

Fault number 1067
Equipment:
rectifier 48V
Source:
(5242884) External battery level 1
BTS model:
FAULT ANALYSIS
This alarm can occur if the batteries are not powered when the cabinet
starts up.
This alarm appears after a "Battery on discharges" alarm (fault number
1060), which means that the battery discharge has dropped below the
lower threshold (45V). The (H)(e)PAs, the F-type converters and the DRX
or DRX-ND3s are no longer powered.

BSC defense As long as the BTS is powered on, there is no BSC
defense action.
btsSiteManager object and the transceiverEquipment objects.
CAUTION
Below the 42V threshold, the -48V power supply cuts off and
the BTS/BSC link is lost.

411-9001-103 18.06 20 January 2010
692
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures)).

becomes "enabled".

"disabled-failed".
alarm persists.




411-9001-103 18.06 20 January 2010
693
On-site maintenance
Put the battery circuit breaker on the front panel in the "I"
position, if necessary.
Additional checks



the manufacturer.

to step 6.
Clear the alarm.

--End--
2.12.112 Rectifiers (source: PCU protective)

Fault number 1067
Equipment:
rectifier 48V
Source:
(5242885) PCU protective
BTS model:
FAULT ANALYSIS
This alarm indicates a fault on the circuit breaker L1/CB1 or L3/CB3 of the
PCU (for the rectifier shelf) or the (H)(e)PA and DRX or DRX-ND3 of the
DCU (for the GIPS).
BSC defense
The BSC unconfigures the transceiverEquipment object and one or several
bts objects.

411-9001-103 18.06 20 January 2010
694
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.

411-9001-103 18.06 20 January 2010
695


On-site maintenance
It is necessary to check all the equipment located behind the circuit breakers.
Put the circuit breakers L1/CB1 and L3/CB3 in the "O" position.
Put the circuit breaker L1/CB1 (PA for the GIPS) in the "I"
position.
If there is a new break, the cabling between the PCU

(DCU for the GIPS) and the (H)(e)PAs, or the (H)(e)PAs
themselves, are failed. Replace these cables (Shop
Power off the (H)(e)PAs and the F-type converters. Go to step 6.
Successively power on the F-type converters and then the

(H)(e)PAs.
If there is a new break, the last module powered on is failed.

Replace this module (Field Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting) for the S8000 BTS if the faulty module
is an F-type converter or if the faulty module is a power
amplifier.

for the S8002 BTS if the faulty module is an F-type
converter or if the faulty module is a power amplifier.

for the S8006 BTS if the faulty module is an F-type
converter or if the faulty module is a power amplifier.
Put the circuit breaker L3/CB3 (DRX or DRX-ND3 for the GIPS)
in the "I" position.

411-9001-103 18.06 20 January 2010
696
If there is a new break, the cabling between the PCU (DCU

for the GIPS) and the DRX or DRX-ND3s, themselves, are
failed. Replace these cables (Shop Replaceable Unit). Go
to step 10.
Disconnect all the PWR cables from the front panel of the DRX
or DRX-ND3s (cable on the INTERCO panel first, then on the
DRX or DRX-ND3). Go to step 9.
Successively reconnect the PWR cables on the front panel of the

DRX or DRX-ND3s (cable on the DRX or DRX-ND3 first, then
on the INTERCO panel).
If there is a new break, the last module is failed. Replace this

module: cable (Shop Replaceable Unit) or DRX or DRX-ND3
module (Field Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003
Troubleshooting) for the S8000 BTS DRX or DRX-ND3
module
for the S8002 BTS DRX or DRX-ND3 module
for the S8006 BTS DRX or DRX-ND3 module
Go to step 10.
Additional checks
10
11



the manufacturer.

to step 12.
12
Clear the alarm.
13

--End--

411-9001-103 18.06 20 January 2010
697
2.12.113 Rectifiers (source: Battery on discharges)

Fault number 1067
Equipment:
rectifier 48V
Source:
(5242886) Battery on discharges
BTS model:
FAULT ANALYSIS
This notification occurs when the system switches to the batteries. It
indicates that the battery is discharging. If the voltage drops below the 45
V threshold, a fault notification with the source "External battery level 1" is
issued.
The fault is caused by an AC and/or a DC failure.
BSC defense
btsSiteManager object, the bts object, or the transceiverEquipment objects.
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks




411-9001-103 18.06 20 January 2010
698

Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.



On-site maintenance
Replace the faulty rectifier (Field Replaceable Unit). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003

Troubleshooting) for an S8000 BTS with rectifiers of a
six-rectifier type or for an S8000 BTS with rectifiers of a

the S8002 BTS
Analyze the alarm.

411-9001-103 18.06 20 January 2010
699

Check the power supplies and solve the problem. Go to step 5.
Additional checks



the manufacturer.

to step 7.
Clear the alarm.

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

Fault number 1067
Equipment:
RIPM-USER core
Source:
(15794208) IPM BIST failed
BTS model:
FAULT ANALYSIS
This alarm indicates a BIST failed for the RIPM-USER.

BSC defense
None.
None.

411-9001-103 18.06 20 January 2010
700
TROUBLESHOOTING
Procedure 10
Preliminary checks
Step
Action

ATTENTION

confirmed.

Replace the RIPM-USER

(411-9001-048).

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

Fault number 1067
Equipment:
RIPM-USER core
Source:
(15794211) Temperature
BTS model:
FAULT ANALYSIS
This alarm indicates an excessively high temperature on an RIPM-USER.

BSC defense
None.

411-9001-103 18.06 20 January 2010
701

None.
TROUBLESHOOTING
Procedure 11
Preliminary checks
Step
Action

ATTENTION

confirmed.

Replace the RIPM-USER

(411-9001-048).

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

synchronization not possible)
Fault number 1067
Equipment:
RIPM-USER core
Source:
(15794224) DAC unable to lock, synchronization not possible
BTS model:

411-9001-103 18.06 20 January 2010
702
FAULT ANALYSIS
The RIPM-USER generates a "Frequency saturation" event in case the
local oscillator cannot be frequency-locked, within its operational tuning
range.
The begin-of fault alarm indicates that the current value of the DAC
(Digital-to-Analog Converter) is not within a nominal range. The DAC
value is not within in this range for a time for that reaches the confirmation
threshold.
The end-of-fault alarm indicates that the current DAC value is within a
nominal range. The DAC value is within in this range for a time for that
The RIPM-USER local oscillator has experienced a large frequency

within its nominal tuning range. This is the most probable cause.
The network reference frequency is in failure. This is the least probable

cause.

BSC defense
None.
TROUBLESHOOTING
Procedure 12
Preliminary checks
Step
Action

ATTENTION

confirmed.


411-9001-103 18.06 20 January 2010
703
Replace the RIPM-USER.

(411-9001-048).

--End--
2.12.117 RIPM-USER core (source: No link with passive)

Fault number 1067
Equipment:
RIPM-USER core
Source:
(15794241) No link with passive
BTS model:
FAULT ANALYSIS
This alarm indicates that there is no link between the active RIPM-USER
core and the passive RIPM-USER core.

BSC defense
None.
None.
TROUBLESHOOTING
Procedure 13
Preliminary checks
Step
Action

ATTENTION

411-9001-103 18.06 20 January 2010
704

confirmed.

Replace the RIPM-USER.

(411-9001-048).

--End--
2.12.118 Rx Filter (source: LNA fault)

Fault number 1067
Equipment:
Rx Filter (LNA)
Source:
(7602177) LNA fault
BTS model:
FAULT ANALYSIS
This alarm is detected by the RECAL board.
related reception path (main or diversity) is not operational for the TRXs
using the faulty LNA. However, if the other path is still correct, these TRXs
run in a degraded mode.
BSC defense
If there is no reception path, the BSC unconfigures the transceiver
Equipment objects corresponding to the faulty LNA. One or several
transceiverEquipment objects can be lost.

411-9001-103 18.06 20 January 2010
705
CAUTION
Service reduction
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.


411-9001-103 18.06 20 January 2010
706

step 4.

step 3.
Check that the alarm on the combiner duplexer LNA is valid by




them.

If the L1 (PA for the GIPS) circuit breaker is in the "O" position,
put it in the "I" position. Go to step 7.


with the LNA-combiner. Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003

Troubleshooting).
Replace the RECAL board (Field Replaceable Units). Refer to:
411-9001-048 (Nortel GSM BTS S8000/S8003

Troubleshooting).

411-9001-103 18.06 20 January 2010
707

10
Check the cable between the connection panel and the RECAL
board.

step 11.
Additional checks
11
12



manufacturer.

13.
13
Clear the alarm.
14

--End--
2.12.119 SYNC boards (source: Major fault on SYNC)

Fault number 1067
Equipment:
SYNC
Source:
(4325377) Major fault on SYNC
BTS model:
FAULT ANALYSIS
The equipment number specified in the alarm identifies the faulty SYNC
board.

BSC defense If there is a redundant board, there is no defense action.
If there is an alarm on both SYNC boards, the BSC unconfigures the bts
objects.
411-9001-103 18.06 20 January 2010
708
CAUTION
If there is a redundant board, the site is not lost. Otherwise, the
site is lost.
TROUBLESHOOTING
Step
Action
Preliminary checks



Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the SYNC board is valid, by


411-9001-103 18.06 20 January 2010
709
If the state of the "SYNC" equipment is "failed", the fault is

If the state of the "SYNC" equipment is "working", the fault is

On-site maintenance
Replace the faulty SYNC board (Field Replaceable Unit).

Troubleshooting).
Additional checks

Check the state of the SYNC board by performing a "Display

If the state of the "SYNC" equipment is still "failed", call the

manufacturer.
If the state of the "SYNC" equipment is "working", go to step

6.
Clear the alarm.

--End--

Fault number 1067
Equipment:
Tx Filter (VSWR)
Source:
BTS model:
FAULT ANALYSIS

BSC defense
None.
411-9001-103 18.06 20 January 2010
710
None.

Fault number 1067
Equipment:
Tx Filter (VSWR)
Source:
BTS model:
FAULT ANALYSIS
This alarm indicates that the radio link has been interrupted in the
transmission path for one TRX using the corresponding equipment. This
TRX is no longer operational.
BSC defense
The BSC unconfigures one transceiverEquipment object.
CAUTION
Service reduction
TROUBLESHOOTING
Preliminary checks
Step
Action




411-9001-103 18.06 20 January 2010
711

Procedures) ).

becomes "enabled".

"disabled-failed".
alarm persists.
Check that the alarm on the Tx Filter is valid, by performing

If the state of the "txFilter" equipment is "failed", the fault is

If the state of the "txFilter" equipment is "working", the fault is

On-site maintenance
Check the cabling between the associated Tx Filter and antenna.
step 5.
If there are three alarms with source: level 2, and source:

level 3, replace the associated Tx Filter (Field Replaceable
Additional checks

411-9001-103 18.06 20 January 2010
712

Check the state of the Tx Filter by performing a "Display

If the state of the "txFilter" equipment is still "failed", call the

manufacturer.
If the state of the "txFilter" equipment is "working", go to step

7.
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 or DRX-ND3

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-103 18.06 20 January 2010
713
Each time the downloading fails, 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 24
Source
No.
Source wording
Paragraph
No response to status request
Bad hardware reference or manufacturer ID
Reception Stop from SUP
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
Wrong software reference on a non

downloadable TEI
No response to load message
2.14.1 Source 9:
No response to load
message (page 718)
10
Received LOAD INIT NACK
2.14.2 Source 10:

Received LOAD INIT
NACK (page 718)
11
Received LOAD DATA NACK
2.14.3 Source 11:

Received LOAD
DATA NACK (page
718)
12
Received LOAD END NACK
2.14.4 Source 12:

Received LOAD END
NACK (page 718)
13
Received LOAD READY NACK
14
CSM load container negative acknowledge

ment
15
File to download empty
16
File to download unavailable
17
Buffer allocation failure

411-9001-103 18.06 20 January 2010
2.14.5 Source 13:

Received LOAD
READY NACK
(page 718)
714
Table 24
Source
No.
Source wording
Paragraph
18
Bad sending buffer size value
19
Failure during omu switchover
20
Bad TEI sent by BTS in the CSM software

21

"unknown TEI"
22

"equipment failure"
23

24

"not able to perform"
27

"restart request"
29

"message out of sequence"
32

"downloading in progress"
33
Bad report sent by BTS in the CSM software

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

"equipment failure"
48

49

50

"wrong soft ref"

411-9001-103 18.06 20 January 2010
Table 24
Source
No.
Source wording
Paragraph
51

"wrong config ref"
52
CSM downloading start nack with a bad

cause
53
no BTS response on CSM downloading start

message
55

"equipment failure"
56

57

"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

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
67
no BTS response on CSM load init message
68
CSM load data nack with the cause

"equipment failure"
69

70


411-9001-103 18.06 20 January 2010
715
716
Table 24
Source
No.
Source wording
Paragraph
71

format error"
72
CSM load data nack with the cause "window

overflow"
73

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

not received"
75
CSM load data nack with the cause "bad

block tag"
76

"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

82
CSM load end nack with the cause "value

out of range"
83

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

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

411-9001-103 18.06 20 January 2010
Table 24
Source
No.
Source wording
Paragraph
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"
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

decode error"
99
CSM load data nack with the cause "table

cannot access"
100
CSM load data nack with the cause "ram

mapping error"
101

access error"
102

ram error"
103

erase error"
104
CSM load data nack with the cause "internal

abort"

BSC defense
None.
None.

411-9001-103 18.06 20 January 2010
717
718
2.14.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:

+ S8006

2.14.2 Source 10: Received LOAD INIT NACK

Source:
(10) Received LOAD INIT NACK
BTS model:

+ S8006

2.14.3 Source 11: Received LOAD DATA NACK

Source:
(11) Received LOAD DATA NACK
BTS model:

+ S8006

2.14.4 Source 12: Received LOAD END NACK

Source:
(12) Received LOAD END NACK
BTS model:

+ S8006

2.14.5 Source 13: Received LOAD READY NACK

Source:
(13) Received LOAD READY NACK
BTS model:

+ S8006


411-9001-103 18.06 20 January 2010
719
Fault number:
1077
Update of the activation status of a site
Type
Marking information
FAULT ANALYSIS
This notification is sent to indicate an up-to-date activation status of the
btsSiteManager object concerned, based on downloading results.
The soft activation status can be either 0 ("not ready") or 1 ("ready").
This notification is sent either at the end of a background downloading, or
after a state change of the btsSiteManager object concerned (failure or
unlock), as indicated in the Cause field of the notification:
either "End of background downloading"

or "Downloaded equipment state change"
The notification also contains the software downloading status, which can
be:
either 0 ("performed")
or 1 ("not performed"). If the software downloading status is set to 1
("not performed"), the failure cause is also given in the notification:
0 "CSM file download failure". This cause is sent when the BSC
cannot retrieve the file set to be downloaded. As a remedial action,
the operator has to check the files and restart the download.
1 "CSM equipment not able to perform such a procedure". This

cause is sent when the BTS supports centralized downloading
protocol, but not background downloading (such as the BTS S8000
CSWM). As a consequence, the background downloading is not
started.
2 "unreachable equipment". This cause is sent either when one

equipment (btsSiteManager or transceiverEquipment) is locked or
failed or which flash updating state is "Unknown TEI", or when the
BTS does not support CSM.
3 "background download to be restarted". This cause is sent when

one equipment (btsSiteManager or transceiverEquipment) has had
a major operational state change leading to a new background
download.
4 "already downloaded". This cause is sent when one soft is

asked to be downloaded again without any change on site. The

411-9001-103 18.06 20 January 2010
720
equipment flash updating state is "flash up-to-date, same soft in

RAM".
5 "abort by operator". This cause is sent after the operator has

performed the Abort action. Then the BackgroundActivate action is
forbidden, even if background downloading has been successfully
terminated before the Abort action.

BSC defense
Depending on the activation status ("ready" or "not ready"), the BSC
authorizes or not the activation of the downloaded software.

None.
TROUBLESHOOTING
No maintenance is required, except if a simultaneous failure of equipment
occurred. Look for alarms on the btsSiteManager object concerned.
Refer to the NRP on BTS Background Downloading (DS/BSS/APP/10) to
know more about the background downloading process (download and
activate operations) and the fallback procedure.
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
411-9001-103 18.06 20 January 2010
721
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

GSM BSS Fault Clearing - Advanced Maintenance Procedures).

411-9001-103 18.06 20 January 2010
722
Fault number:
1213
Secured loop unavailable
Type
equipmentAlarm

Fault number:
1214
Secured loop problem
Type
equipmentAlarm

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 continues its configuration attempts. The
situation must be reestablished.
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-103 18.06 20 January 2010
723
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 startup 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-103 18.06 20 January 2010
724
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 are no longer any

handovers, as the neighboring cells are unknown.
If the alarm is received on a standard cell, the problem could have

occurred during the startup or during 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). There will then be an increase in the rate of call
drops.
CAUTION
Service reduction
The geographical mobility of the mobile is reduced.
If the mobile is out of the geographical area of the cell, the
service is reduced.
TROUBLESHOOTING
If the alarm appears during a startup, a problem occurred in the BTS
configuration during installation.
If the alarm appears during a change, check the OMC-R commands
issued before the alarm appeared. Check the changes performed for the
neighboring cells.
If the microCellInstability and microCellStability parameters have a value,
ensure the value is "algo B". If it is not, modify it.

411-9001-103 18.06 20 January 2010
725
Fault number:
1265
Blockage of radio channel(s) in busy state
Type
communicationsAlarm
FAULT ANALYSIS
This alarm indicates that channels were busy during a time period that was
higher than the surveillance period chosen by the operator.
The notification lists all the radio channels of the BTS that were busy
during the traffic surveillance, during the period 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, but that is the

source of the fault number, call the manufacturer.
Increase the value of the surveillance period.


411-9001-103 18.06 20 January 2010
726
Set the transceiver object to "locked", then to "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.
BSC defense
None.
CAUTION
Service reduction
FAULT LOCATION
The notification indicates, for the concerned BTS, the free channel(s).
TROUBLESHOOTING

411-9001-103 18.06 20 January 2010
727
Step
Action
Check the time of the fault number 1266 and identify the faulty
channel.
Analyze the traffic on the network by checking the rate of

call drop (TCH number busy in comparison to cell resource
number). Refer to Nortel GSM BSS Performance Management
- Observation Counters Dictionary (411-9001-125) for the
observation counters.
If the traffic is low, the fault number 1266 is normal.

If the traffic is high (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
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

411-9001-103 18.06 20 January 2010
728
None.
CAUTION
Service reduction
The channels supported by the faulty TRXs 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 return to

service procedure.
Otherwise, stop the maintenance procedure: the state of the

system is normal.
Set the transceiverEquipment object associated with the TDMA

to "locked" then to "unlocked".
Wait for the state of the transceiver object to become "enabled".
Check the state of the channels associated with the TDMA.

--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-103 18.06 20 January 2010
729
Fault number:
1505
No response to BCCH info (SYS 1, 2, 3, 4, 2 bis, 7, 8, 2 ter,

13)
Type
communicationsAlarm
FAULT ANALYSIS
This alarm indicates that the BTS has not answered nine successive
acknowledgment requests BCCH INFO sent by the BSC. As long as
the BSC has not received any response, it repeats the procedure of
acknowledgment request.
BSC defense
None.
CAUTION
TROUBLESHOOTING
Step
Action
If the alarm appears during the downloading of the site and the
TRXs, do not take this alarm into account. Otherwise, go to step
2.
Set the btsSiteManager concerned to "locked" then "unlocked".
If the alarm persists, go to call the manufacturer.


--End--

411-9001-103 18.06 20 January 2010
730
2.27 Fault number: 1506 (S8000, S8002, S8003, S8006 BTS)

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
for a cell with the cause "No measurements available", even if all
TRXs are locked.

BSC defense
411-9001-103 18.06 20 January 2010
731
None.
None.
TROUBLESHOOTING

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

411-9001-103 18.06 20 January 2010
732
TROUBLESHOOTING
Refer to 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 64 per 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.

Fault number 30034: Background downloaded action is aborted
Source:
30315 "BSC restart occurred"
Source:
30316 "Core process is nullex"
BTS model:

+ S8006
FAULT ANALYSIS
This warning is sent to indicate that a background downloading has
aborted.
When the SPR application (a task located on the TMU module of the BSC
3000) disappears, all background downloading contexts managed by it are
lost and cannot be recovered, as they are stored in volatile memory.
To make information in the whole system consistent, the matching
contexts managed by the ADM (task located on OMU) and OMC-R
must also be released. For that purpose, the event 30034 is sent by the
OMC-R signaling SPR loss and then all ongoing background downloading
procedures are aborted.
This can happen in two different situations:
at BSC reset, the warning 30034 source 30315 "BSC restart occurred"
is sent by the OMC-R and contains an empty list of sites managed by
the BSC
when the SPR becomes "nullex": the warning 30034, source 30316
"Core process is nullex" is sent by the OMC-R and contains the list of
sites managed by the instance of SPR application that has been killed

411-9001-103 18.06 20 January 2010
733

BSC defense
On receiving the warning 30034, both the ADM and the OMC-R will clear
the contexts associated with each site found in the list, if such a context
exists. If not, nothing has to be done for the site. The procedure is over,
and all contexts are consistent. No additional dialogue is necessary
between OMC-R and BSC.
Depending on the point that the SPR disappeared, the BTS flash may:
contain Vn software (if the download could not begin at all)

be invalidated (if download was begun but not completed)
contain Vn+1 software (if download has been completed)
As Vn is still stored in the SoftRef_BDA field of the BSC MIB, the BTS will
then be started in the Vn version, with potential offline download of Vn
software in the last 2 cases above.

None.
TROUBLESHOOTING
The command bckgDownload must be re-executed. In the case that only
one software is requested to be downloaded again (without any change on
the site), the download will be accepted but in the notification 1077, the
status for this software will be "Not Performed" with the cause "Already
downloaded".
In case of abort of a bckgDownload with immediate activate, the BDE and
BDA databases will be on Vn+1 whereas the BTS will remain running in
Vn.
To re-align databases, the operator can:
lock/unlock the site, in such a case, this will lead to a realignment to

Vn+1 (that is, a "forced" upgrade)
reinitiate a background download of Vn with or without immediate

activate; in this case an off-line download of Vn will be necessary due
to the previous flash invalidation
manually reset database to Vn by a normal return-to-previous action
Since the flash has been overwritten, a future reset of BTS requiring flash
to restart will induce an off-line download of the running software version.

411-9001-103 18.06 20 January 2010
734
Refer to the NRP on BTS Background Downloading (DS/BSS/APP/10) to

know more about the background downloading process (download and
activate operations) and the fallback procedure.
2.30 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:

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

411-9001-103 18.06 20 January 2010
2.30 Applicability of the fault numbers to the BTS type
735
Table 25
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
1070
1073
1077
1078
1080
1258
1259
1265
1266
1268
1500
1505
1506
1507
1508
30034

411-9001-103 18.06 20 January 2010
736

411-9001-103 18.06 20 January 2010
737
Index
S
S800 Indoor
1060 Abis event reporting a transient
default
Source (15728659) No response
to DHCP requests for 15
minutes: IPM 371
S800 Outdoor
default
minutes: IPM 371
Source (15794191) Restart after
TML commissioning: RIPM 379
S8000
1080 Access fault 720
S8000 Indoor
1052 GSM entity downloading failure
Source (01) Bad hardware
reference of manufacturer ID 43
Source (03) No change to one of
BOOT states after reset 48
Source (04) This entity is engaged
in another downloading 52
Source (05) Software not
compatible with hardware 54
Source (06) File access error 58
Source (07) Repetitive errors
(NACK, timeout, ...) while
downloading a file 61
Source (08) Wrong software
reference on a non
downloadable TEI 52
Source (14) Received CSM LOAD
CONTAINER NAK 64
Source (16) File to download

unavailable 68
1055 Abis negative acknowledgement indication
Source (02) Equipment unable to
perform such test 285
perform such configuration 286
Source (05) Cell parameters
inconsistency 288
Source (10) Unknown Abis PCM 293
Source (23) Too many signaling
timeslots 297
Source (25) Out of sequence
message 298
Source (34) The BTS has not
acknowledged the power
consign request 302
Source (43) Maximum number of
joker TS 309
Source (6) Data inconsistency 290
Source (63) Dynamic Abis feature
not supported 316
Source (64) Inconsistent number
of joker DS0 317
Source (65) Exceeded DL joker
DS0 pool number 319
Source (7) Value out of range 291
Source (8) TEI not present 292
default
Source (12582924) Frequency
collision on FH bus: eDRX 359
Source (12582935) FACCH
congestion: eDRX 360
Source (12583171) Restart
requested by the BCF: eDRX 360

411-9001-103 18.06 20 January 2010
738
Source (12583175) Restart due to

hardware watchdog: eDRX 361
double bus fault: eDRX 362
Source (12583186) BCCH config
dump: eDRX 362
Source (12583202) SACCH config
dump: eDRX 363
Source (12583218) L1M config
dump: eDRX 363
Source (12583219) RSL anomaly:
eDRX 363
Source (12779522) Unknown
message: CMCF 355
requested by the active board:
CMCF phase 1 356
Source (12779558) Restart due
to hardware watchdog: CMCF
phase 1 357
double bus fault: CMCF phase
1 357
Source (12779560) Reset for new
Lapd parameters: CMCF Ph1 357
Source (12779571) Board reset
asked by OMC: CMCF phase 1 356
Source (12845041) ABIS PCM
statistics: CMCF PH1 358
message: CMCF phase 2 355
CMCF phase 2 356
phase 2 357
2 357
Lapd parameters CMCF Ph2 357
collision on FH bus: DRX-ND3 359
congestion: DRX ND3 360

requested by the BCF:
DRX-ND3 360
due to hardware watchdog:
DRX_ND3 361
double bus fault: DRX_ND3 362
dump: DRX_ND3 362
dump: DRX_ND3 363
dump: DRX_ND3 363
DRX_ND3 363
collision on FH bus: eDRX2 359
congestion: eDRX2 360
requested by the BCF: eDRX2 360
DRX_ND3 361
hardware watchdog: eDRX2 361
double bus fault: eDRX2 362
dump: eDRX2 362
dump: eDRX2 363
dump: eDRX2 363
eDRX2 363
power on: IPM 364
reset by button: IPM 364
software upgrade: IPM 365
hardware watchdog: IPM 365
Source (15728647) IBOS
authentication has failed: IPM 366
Source (15728648) No TCP
connection can be set up with
IGM: IPM 366

411-9001-103 18.06 20 January 2010
739
Source (15728649) Reset

requested by IGM with no
Ethernet switch reset: IPM 367
requested by IGM with Ethernet
switch reset: IPM 367
requested by IBOS with BIST
execution and Ethernet switch
reset: IPM 368
requested by IBOS with no
BIST execution and Ethernet
BIST execution nor Ethernet
TML commissioning: IPM 370
Source (15728656) Connection
with IGM has been lost (no
status received for 7 keep-alive
periods): IPM 371
to DNS requests for 15 minutes:
IPM 372
Source (15728673) Debug 372
Source (15728674) Soft: IPM 373
power on: RIPM 373
reset by button: RIPM 374
software upgrade: RIPM 374
hardware watchdog: RIPM 375
authentication has failed: RIPM 375
IGM: RIPM 376
Ethernet switch reset: RIPM 376

switch reset: RIPM 377
reset: RIPM 377
TML commissioning: RIPM 379
periods): RIPM 380
requested by active with BIST
execution: RIPM 383
requested by active with no
BIST execution: RIPM 383
minutes: RIPM 380
RIPM 381
Source (15794209) Debug: RIPM 381
Source (15794210) Soft: RIPM 382
Source (15859969) Not enough
synchronization packets have
been received 636
hardware watchdog: CSWM 358
double bus fault: CSWM 359
Source (7536642) VSWR level 2:
TX Filter 384

411-9001-103 18.06 20 January 2010
740
Source (8388610) Cavity parked

after tuning fault (min not found):
cavity 352
Source (8388612) Nack answer
from cavity: cavity 354
after tuning fault (power too
low): cavity 354
after tuning fault (tuning
detector): cavity 355
collision on FH bus: DRX 359
congestion: DRX 360
requested by the BCF: DRX 360
hardware watchdog: DRX 361
double bus fault: DRX 362
dump: DRX 362
dump: DRX 363
dump: DRX 363
DRX 363
message: CMCF 355
CMCF 356
hardware watchdog: CMCF 357
double bus fault: CMCF 357
Lapd parameters: CMCF 357
asked by OMC: CMCF 356
statistics: CMCF 358
1063 TRX allocation for a TDMA 386
1067 Abis event reporting a
hardware fault 387
471
DRX 591
Source (12582913) RX fault:

eDRX 585
Source (12582918) BBFILTER
ASIC fault: eDRX 576
Source (12582921) Self test failed:
eDRX 609
Source (12582922) Major fault on
TX: eDRX 597
Source (12582934) DRX link:
eDRX 591
Source (12582939) PA config.
exceeded: DRX-ND3 573
Source (12582944) The TX has
not ack the power consign
request: eDRX 580
Source (12582945) PA DRX
control loop fault: eDRX 602
Source (12582946) DRX reset by
BCF after message non ack.:
eDRX 602
Source (12582947) DRX link NOK
after reset requested by BSC:
eDRX 596
Source (12583184) BCCH first
config failed: eDRX 589
Source (12583185) BCCH second
Source (12583200) SACCH first
Source (12583201) SACCH
second config failed: eDRX 608
Source (12583216) L1M first
Source (12583217) L1M second
Source (12648447) TRX not
anymore configured: eDRX 613
Source (12648449 ) Hardware:
ePA 652
Source (12648450) DRX and PA
connection: ePA 658
Source (12648451) High temp:
ePA 663
Source (12648452) High current:
ePA 667
Source (12648454) PA_PSDW:
ePA 671
Source (12713985) Hardware:
(H)(e)PA 652

411-9001-103 18.06 20 January 2010
741

connection: HePA 658
HePA 663
HePA 667
HePA 671
Source (12779529) MCF_MCF:
CMCF phase 1 507
Source (12779538) CMCF ACT
DUPLEX INHIBITED: CMCF
phase 1 512
ICST: CMCF phase 1 515
Source (12779540) Duplex
inhibited: feature not supported
on CMCF phase 1: CMCF
phase 1 517
Source (12845050) Slave
downloading error: CMCF
phase 1 510
CMCF phase 2 507
phase 2 512
phase 2 510
DRX-ND3 585
ASIC fault: DRX-ND3 576
DRX-ND3 609
TX: DRX-ND3 597
DRX-ND3 591
Source (12976158) Abis satellite
not supported DRX ND3:
DRX-ND3 569
request: DRX-ND3 580
control loop fault: DRX-ND3 602

DRX-ND3 602
DRX-ND3 596
config failed: DRX-ND3 589
second config failed: DRX-ND3 608
anymore configured: DRX-ND3 613
eDRX2 609
TX: eDRX2 597
eDRX2 591
control loop fault: eDRX2 602
eDRX2 602
eDRX2 596
config failed: eDRX2 589
second config failed: eDRX2 608
anymore configured: eDRX2 613

411-9001-103 18.06 20 January 2010
742
Source (15663140) Only one IBOS

commissioned at IPM: IPM
commissioning 637
Source (15663141) DNS
resolution has failed for at least
one IBOS: IPM commissioning 638
Source (15728672) BIST failed:
IPM 639
Source (15728675) Temperature:
IPM 640
Source (15728688) DAC unable
to lock, synchronization not
possible: IPM 641
RIPM 699
IPM 700
possible: IPM 701
Source (15794241) No link with
passive: RIPM 703
Source (15859968) Unable to
lock on IP synchronization: IP
synchro 634
Source (3342340) SYNO clock
not locked on the network: BTS
synchronization 441
Source (3342341) Synchro not
locked because OCVXO is KO:
BTS synchronization 448
Source (3342343) GPS
synchronization unavailable:
Source (3342344) Loss of
GPS synchronization: BTS
synchronization 456
Source (3342345) Lack of GPS
synchronization accuracy: BTS
synchronization 461
Source (3342346) Master
Source (3342348) Loss of master
SY: BTS sunchronization 475
Source (3735553) Alarm: Not
protected alarm 646
Source (4259849) Fault on
active-passive CSWM link
or passive CSWM: CSWM 544

downloading error: CSWM 547
SYNC: SYNC 707
Source (4390913) Major fault:
ALCO 416
Source (4456453) Channel_HSCX: DSC 618
PCMI 652
GTW: GTW 628
Source (5242881) AC fault:
Rectifier 48V 682
Source (5242882) DC fault:
Rectifier 48V 686
Source (5242883) Over
temperature: Rectifier 48V 688
Source (5242884) External battery
level 1: Rectifier 48V 691
Source (5242885) PCU protective:
Rectifier 48V 693
Source (5242886) Battery on
discharges: Rectifier 48V 697
Source (5308417) Volt: Converter
F 624
BCF 435
Source (5570561) LNA fault:
Combiner duplexer LNA or
combiner H2 LNA 520
Source (5636097) VSWR level
1: Combiner duplexer vswr or
combiner h2 vswr 524
Source (5898241) Door contact
detection: Door contact 479
Source (6225921) Cabinet fan
fault: Cabinet fan 621
Source (6291457) BCF cabinet
door contact detection: BCF
Cabinet door 429
Source (6356993) BCF cabinet fan
fault: BCF Cabinet fan 433
Source (6488065) PCM: PCM 652

411-9001-103 18.06 20 January 2010
743
Source (6815745) Hardware: PA 652

connection: PA 658
Source (6815747) High temp: PA 663
PA 667
Source (6815750) PA_PSDW: PA 671
Source (6815751) VSWR fault
detected by PA: PA 675
Source (6881281) Software
detection: DRX main reception
chain 565
detection: DRX-ND3 main
reception chain 565
detection: DRX diversity
reception chain 560
detection: DRX-ND3 diversity
reception chain 560
Source (7274497) External alarm 621
Combiner h4 lna (LNA) 528
Source (7471105) VSWR level:
Combiner h4 vswr (VSWR) 532
Txfilter (VSWR) 710
Source (8323073) Power supply:
Cavity combiner 496
Source (8323074) Tuning detector
fault: Cavity combiner 498
Source (8323076) Link NOK:
Cavity combiner 500
Source (8388609) Cavity out of
service: Cavity 483
after tuning fault (min not found):
Cavity 485
Source (8388611) Loss of cavity
initialization: Cavity 487
Source (8388612) Nack answer
from cavity: Cavity 489
after tuning fault (power too
low): Cavity 490

after tuning fault (tuning detector
problems): Cavity 492
Source (8388615) Internal
software problem :Cavity 494
Source (9437185) RX fault: DRX 585
ASIC fault: DRX 576
DRX 609
TX: DRX 597
exceeded: DRX 573
Source (9437212) HePA not
supported: DRX 570
not supported DRX: DRX 569
Source (9437216) The TX has not
ack the power consign request:
DRX 580
Source (9437217) PA DRX control
loop fault: DRX 602
DRX 602
DRX 596
config failed: DRX 589
Source (9437473) SACCH second
Source (9437488) L1M first config
failed: DRX 589
anymore configured: DRX 613
CMCF 507
downloading error: CMCF 510
CPCMI 541

411-9001-103 18.06 20 January 2010
744

downloading error: CPCMI 541
Source (9633793) Major: RECAL 676
downloading error: RECAL 679
Source (9699329) Over current:
Rx splitter M 649
Rx splitter D 646
Source 4456449) Major fault:
DSC 616
Source 7602177) LNA fault: Rx
Filter (LNA) 704
default
Tx filter (VSWR) 709
1070 TRX synchronization failure 712
1073 Attempt of download failure on
a GSM entity 712
Source (09) No response to load
message 718
Source (10) Received LOAD INIT
NACK 718
Source (11) Received LOAD DATA
NACK 718
Source (12) Received LOAD END
NACK 718
Source (13) Received LOAD
READY NACK 718
1077 Update of the activation status
of a site 719
1213 Secured loop unavailable 721
1214 Secured loop problem 722
1258 No BTS response on
preprocessing configuration 722
1259 Negative acknowledgement on
preprocessing command 724
1265 Blockage of radio channel(s) in
busy state 725
free state 726
1268 NO RESPONSE TO A SACCH
FILLING (SYS 5, 6, 5bis, 5ter or
meas_info) 727
1500 Measurement received on
an unknown frequency of
neighboring cell 728
1505 No response to BCCH info

(SYS 1, 2, 3, 4, 2 bis, 7, 8, 2 ter,
13) 729
1506 No distribution available for a
cell 730
1508 Data service impact (SYS 13
size exceeded) 731
30034 Background downloaded
action is aborted
Source (30315) BSC restart
occurred 732
Source (30316) Core process is
nullex 732
S8000 Outdoor
reference on a non
downloadable TEI 52
CONTAINER NAK 64
unavailable 68
inconsistency 288
timeslots 297
message 298
consign request 302

411-9001-103 18.06 20 January 2010
745

joker TS 309
not supported 316
of joker DS0 317
default
dump: eDRX 362
dump: eDRX 363
dump: eDRX 363
eDRX 363
CMCF phase 1 356
phase 1 357
1 357

CMCF phase 2 356
phase 2 357
2 357
DRX-ND3 360
DRX_ND3 361
dump: DRX_ND3 362
dump: DRX_ND3 363
dump: DRX_ND3 363
DRX_ND3 363
dump: eDRX2 362
dump: eDRX2 363

411-9001-103 18.06 20 January 2010
746

dump: eDRX2 363
eDRX2 363
power on: IPM 364
reset by button: IPM 364
software upgrade: IPM 365
hardware watchdog: IPM 365
authentication has failed: IPM 366
IGM: IPM 366
Ethernet switch reset: IPM 367
reset: IPM 368
TML commissioning 370
periods): IPM 371
Source (15728660) Debug 372
IPM 372
Source (15728674) Soft: IPM 373

power on: RIPM 373
reset by button: RIPM 374
software upgrade: RIPM 374
hardware watchdog: RIPM 375
authentication has failed: RIPM 375
IGM: RIPM 376
Ethernet switch reset: RIPM 376
reset: RIPM 377
periods): RIPM 380
requested by active with BIST
execution: RIPM 383
requested by active with no
BIST execution: RIPM 383
minutes: RIPM 380

411-9001-103 18.06 20 January 2010
747

RIPM 381
Source (15794209) Debug: RIPM 381
Source (15794210) Soft: RIPM 382
Source (15859969) Not enough
synchronization packets have
been received 636
Source (6553601) Manual switch
on battery power: BRC 351
Source (6553602) Automatic
switch on battery power: BRC 351
on main power: BRC 351
switch on main power: BRC 352
TX Filter 384
congestion: DRX 360
dump: DRX 362
dump: DRX 363
dump: DRX 363
DRX 363
message: CMCF 355
CMCF 356

hardware fault 387
eDRX 585
eDRX 609
TX: eDRX 597
eDRX 591
request: eDRX 580
eDRX 602
eDRX 596
ePA 652

411-9001-103 18.06 20 January 2010
748

connection: ePA 658
ePA 663
ePA 667
ePA 671
(H)(e)PA 652
HePA 663
HePA 667
HePA 671
CMCF phase 1 507
phase 1 512
phase 1 517
phase 1 510
CMCF phase 2 507
phase 2 512
phase 2 510
DRX-ND3 585
DRX-ND3 609
TX: DRX-ND3 597

DRX-ND3 591
DRX-ND3 569
DRX-ND3 602
DRX-ND3 596
eDRX2 609
TX: eDRX2 597
eDRX2 591
eDRX2 602
eDRX2 596

411-9001-103 18.06 20 January 2010
749

Source (15663140) Only one IBOS
commissioned at IPM: IPM
commissioning 637
Source (15663141) DNS
resolution has failed for at least
one IBOS: IPM commissioning 638
IPM 639
IPM 640
possible: IPM 641
RIPM 699
IPM 700
possible: IPM 701
Source (15794241) No link with
passive: RIPM 703
Source (15859968) Unable to
lock on IP synchronization: IP
synchro 634
synchronization 441
Source (3342343) GPS
GPS synchronization: BTS
synchronization 456
Source (3342345) Lack of GPS
synchronization accuracy: BTS
synchronization 461
Source (3342346) Master

master GSM time: BTS
synchronization 471
Source (3342348) Loss of master
SY: BTS sunchronization 475
protected alarm 646
Source (4259849) Fault on
active-passive CSWM link
or passive CSWM: CSWM 544
downloading error: CSWM 547
SYNC: SYNC 707
ALCO 416
Source (4456453) Channel_HSCX: DSC 618
PCMI 652
GTW: GTW 628
Rectifier 48V 682
Rectifier 48V 686
Source (5242884) External battery
level 1: Rectifier 48V 691
Rectifier 48V 693
F 624
BCF 435
Source (5439489) Battery
disconnected: Internal battery
system 631
Source (5505031) Cooler fault:
Cooler system 413
combiner H2 LNA 520

411-9001-103 18.06 20 January 2010
750

Source (5767169) Main breaker:
Distribution system 557
temperature: battery cabinet 419
Source (5832706) DC power fault:
battery cabinet 422
Source (5832707) Doors: battery
cabinet 425
Source (6160385) Lightning
protection fault: Lightning
Protection 643
Source (6553605) Battery failure:
BRC 439
Source (6553606) Monitored
battery not present: BRC 440
Source (6553607) Internal
inconsistency: BRC 441
connection: PA 658
PA 667
chain 565
reception chain 565

reception chain 560
reception chain 560
Combiner h4 lna (LNA) 528
Txfilter (VSWR) 710
Source (7864321) Dirty filter:
dacsCooler 549
Source (7864322) DACS failed:
dacsCooler 551
ASIC fault: DRX 576
DRX 609
Source (9437194)Major fault on
TX: DRX 597
Source (9437206) DRX link: DRX 591
exceeded: DRX 573
supported: DRX 570
DRX 580
loop fault: DRX 602
DRX 602
DRX 596

411-9001-103 18.06 20 January 2010
751

failed: DRX 589
CMCF 507
CPCMI 541
Rx splitter M 649
Rx splitter D 646
Source 4456449) Major fault:
DSC 616
Filter (LNA) 704
default
a GSM entity 712
message 718
NACK 718
NACK 718
NACK 718
READY NACK 718
of a site 719

busy state 725
free state 726
meas_info) 727
(SYS 1, 2, 3, 4, 2 bis, 7, 8, 2 ter,
13) 729
cell 730
size exceeded) 731
action is aborted
occurred 732
nullex 732
S8002
reference on a non
downloadable TEI 52
CONTAINER NAK 64
unavailable 68

411-9001-103 18.06 20 January 2010
752

inconsistency 288
timeslots 297
message 298
consign request 302
joker TS 309
not supported 316
of joker DS0 317
default
dump: eDRX 362
dump: eDRX 363
dump: eDRX 363
eDRX 363
CMCF phase 1 356

phase 1 357
1 357
CMCF phase 2 356
phase 2 357
2 357
DRX-ND3 360
DRX_ND3 361
dump: DRX_ND3 362
dump: DRX_ND3 363
dump: DRX_ND3 363
DRX_ND3 363

411-9001-103 18.06 20 January 2010
753

congestion: DRX 360
dump: DRX 362
dump: DRX 363
dump: DRX 363
DRX 363
message: CMCF 355
CMCF 356
hardware fault 387

eDRX 585
eDRX 609
TX: eDRX 597
eDRX 591
request: eDRX 580
eDRX 602
eDRX 596
ePA 652
connection: ePA 658
ePA 663
ePA 667
ePA 671
(H)(e)PA 652

411-9001-103 18.06 20 January 2010
754

HePA 663
HePA 667
HePA 671
CMCF phase 1 507
phase 1 512
phase 1 517
phase 1 510
CMCF phase 2 507
phase 2 512
phase 2 510
DRX-ND3 585
DRX-ND3 609
TX: DRX-ND3 597
DRX-ND3 591
DRX-ND3 569

DRX-ND3 602
DRX-ND3 596
synchronization 441
protected alarm 646
Rectifier 48V 682
Rectifier 48V 686
Rectifier 48V 693
F 624
Source (5439489) Battery
disconnected: Internal battery
system 631
combiner H2 LNA 520

411-9001-103 18.06 20 January 2010
755

Protection 643
Source (6553605) Battery failure:
BRC 439
connection: PA 658
PA 667
chain 565
reception chain 565
reception chain 560
reception chain 560
Compact dacs cooler 502
Compact dacs cooler 504
Compact distribution 538

ASIC fault: DRX 576
DRX 609
TX: DRX 597
exceeded: DRX 573
supported: DRX 570
DRX 580
loop fault: DRX 602
DRX 602
DRX 596
failed: DRX 589
CMCF 507
CPCMI 541
Rx splitter M 649

411-9001-103 18.06 20 January 2010
756

Rx splitter D 646
a GSM entity 712
message 718
NACK 718
NACK 718
NACK 718
READY NACK 718
of a site 719
busy state 725
free state 726
meas_info) 727
(SYS 1, 2, 3, 4, 2 bis, 7, 8, 2 ter,
13) 729
cell 730
size exceeded) 731
action is aborted
occurred 732
nullex 732
S8003

reference on a non
downloadable TEI 52
CONTAINER NAK 64
unavailable 68
inconsistency 288
timeslots 297
message 298
consign request 302
joker TS 309
not supported 316
of joker DS0 317
default 363

411-9001-103 18.06 20 January 2010
757

dump: eDRX 362
dump: eDRX 363
dump: eDRX 363
CMCF phase 1 356
phase 1 357
1 357
CMCF phase 2 356
phase 2 357
2 357

DRX-ND3 360
DRX_ND3 361
dump: DRX_ND3 362
dump: DRX_ND3 363
dump: DRX_ND3 363
DRX_ND3 363
dump: eDRX2 362
dump: eDRX2 363
dump: eDRX2 363
eDRX2 363
TX Filter 384
congestion: DRX 360
dump: DRX 362
dump: DRX 363

411-9001-103 18.06 20 January 2010
758

dump: DRX 363
DRX 363
message: CMF 355
CMCF 356
hardware fault 387, 712
eDRX 585
eDRX 609
TX: eDRX 597
eDRX 591
request: eDRX 580
eDRX 602
eDRX 596

ePA 652
connection: ePA 658
ePA 663
ePA 667
ePA 671
(H)(e)PA 652
HePA 663
HePA 667
HePA 671
CMCF phase 1 507
phase 1 512
phase 1 517
phase 1 510
CMCF phase 2 507
phase 2 512

411-9001-103 18.06 20 January 2010
759

phase 2 510
DRX-ND3 585
DRX-ND3 609
TX: DRX-ND3 597
DRX-ND3 591
DRX-ND3 569
DRX-ND3 602
DRX-ND3 596
eDRX2 609
TX: eDRX2 597
eDRX2 591

eDRX2 602
eDRX2 596
synchronization 441
protected alarm 646
F 624
combiner H2 LNA 520
Source (6225921) Cabinet fan
fault: Cabinet fan 621

411-9001-103 18.06 20 January 2010
760

connection: PA 658
Source (6815747) High temp: PA
PA 667
Source (6815750) PA_PSDW: PA
chain 565
reception chain 565
reception chain 560
reception chain 560
Source (7274497) External alarm
Txfilter (VSWR) 710
Source (9437185) RX fault: DRX
ASIC fault: DRX 576
DRX 609
TX: DRX 597
Source (9437206) DRX link: DRX
exceeded: DRX 573
supported: DRX 570
DRX 580
loop fault: DRX 602
DRX 602
DRX 596
663
671
621
585
591

failed: DRX 589
CMCF 507
Rx splitter D 646
Filter (LNA) 704
default
a GSM entity
message 718
NACK 718
NACK 718
NACK 718
READY NACK 718
of a site 719

411-9001-103 18.06 20 January 2010
761

busy state 725
free state 726
meas_info) 727
(SYS 1, 2, 3, 4, 2 bis, 7, 8, 2 ter,
13) 729
cell 730
size exceeded) 731
action is aborted
occurred 732
nullex 732
S8006
hardware fault 569
reference on a non
downloadable TEI 52
CONTAINER NAK 64
unavailable 68

inconsistency 288
timeslots 297
message 298
consign request 302
joker TS 309
not supported 316
of joker DS0 317
default 358
dump: eDRX 362
dump: eDRX 363
dump: eDRX 363
eDRX 363
CMCF phase 1 356

411-9001-103 18.06 20 January 2010
762

phase 1 357
1 357
CMCF phase 2 356
phase 2 357
2 357
DRX-ND3 360
DRX_ND3 361
dump: DRX_ND3 362
dump: DRX_ND3 363
dump: DRX_ND3 363
DRX_ND3 363

congestion: DRX 360
dump: DRX 362
dump: DRX 363
dump: DRX 363
DRX 363
message: CMCF 355
CMCF 356
hardware fault 387
(H)(e)PA 667
eDRX 585
eDRX 609
TX: eDRX 597

411-9001-103 18.06 20 January 2010
763

eDRX 591
request: eDRX 580
eDRX 602
eDRX 596
ePA 652
connection: ePA 658
ePA 663
ePA 671
(H)(e)PA 652
HePA 663
HePA 667
HePA 671
CMCF phase 1 507
phase 1 512

phase 1 517
phase 1 510
CMCF phase 2 507
phase 2 512
phase 2 510
DRX-ND3 585
DRX-ND3 609
TX: DRX-ND3 597
DRX-ND3 591
DRX-ND3 602
DRX-ND3 596

411-9001-103 18.06 20 January 2010
764

synchronization 441
protected alarm 646
Rectifier 48V 682
Rectifier 48V 686
Rectifier 48V 693
F 624
combiner H2 LNA 520
Protection 643
connection: PA 658
PA 667
chain 565

reception chain 565
reception chain 560
reception chain 560
dacsCooler 549
dacsCooler 551
ASIC fault: DRX 576
DRX 609
TX: DRX 597
DRX 580
loop fault: DRX 602
DRX 602
DRX 596
failed: DRX 589
CMCF 507

411-9001-103 18.06 20 January 2010
765

CPCMI 541
Rx splitter M 649
Rx splitter D 646
a GSM entity 712
message 718
NACK 718
NACK 718
NACK 718
READY NACK 718
of a site
1077 Update of the activation
status of a site 719
busy state 725
free state 726
meas_info) 727
(SYS 1, 2, 3, 4, 2 bis, 7, 8, 2 ter,
13) 729

cell 730
size exceeded) 731
action is aborted
occurred 732
nullex 732
Source (9568257) Major fault: CPCMI
hardware fault
CPCMI 541

411-9001-103 18.06 20 January 2010
766

411-9001-103 18.06 20 January 2010

Release: V18.0 PC2
Publication: 411-9001-103
Document revision: 18.06
Document release date: 20 January 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, S2000 and S8000 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

GSM BTS S8000 S8002 S8003 S8006 Fault Clearing

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

GSM BTS S8000 S8002 S8003 S8006 Fault Clearing

Încărcat de

Drepturi de autor:

Formate disponibile

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 S8000, S8002, S8003, and S8006 BTS fault

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)

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

Global System for Mobile Communications (GSM)

18 New in this release

Global System for Mobile Communications (GSM)

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

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

Nortel GSM BSS Performance Management Observation Counters

Nortel GSM OMC-R Commands Reference Objects and Fault menus

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

Nortel GSM BSS Overview (411-9001-001)

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

Global System for Mobile Communications (GSM)

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

general personnel safety instructions

Global System for Mobile Communications (GSM)

Personnel and equipment safety

rules concerning the premises (see instructions posted on site or in

rules linked to the general personnel safety instructions

The personnel working on the cabinet must be authorized to work

Equipment safety instructions

Global System for Mobile Communications (GSM)

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

Global System for Mobile Communications (GSM)

26 Chapter 1 How to use this manual

V15.0 introduced EDGE and other important features, together with

1.2 The types of spontaneous messages

spontaneous messages indicating a hardware fault (fault number 1067)

spontaneous messages sent as a warning and indicating a transient

spontaneous messages indicating the arrival of state changes on an

spontaneous messages indicating a hardware fault without loss of

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

Global System for Mobile Communications (GSM)

This paragraph describes the fault.

Reaction of the system

Impact on the service

On-site maintenance (possibly using the OMC-R)

the Consult BSS Documentation option of the workstation workspace

Both are provided on the same CD-ROM.