BTS Alarm Dictionary PDF

Alcatel-Lucent GSM
BTS Alarm Dictionary
BTS Document
Reference Guide
Release B11
3BK 21625 AAAA PCZZA Ed.06
BLANK PAGE BREAK
Status
RELEASED
Short title
BTS Alarm Dictionary

All rights reserved. Passing on and copying of this document, use
and communication of its contents not permitted without written
authorization from Alcatel.
2 / 320
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2
Relationships Between SBLs and MOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3
9153 OMC-R Alarm Surveillance Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4
LMT Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.5
BTS Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Class 1: CLK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1
[1,6] MCL-FATAL-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2
[1,12] CLOCK-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3
[1,31] MCL-XCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.4
[1,234] IOM-DISCONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.5
[1,237] HW-DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.6
[1,248] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Class 2: OMU Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.1
[2,1] LOSS OF TWIN CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.2
[2,247] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.3
[2,248] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Class 3: SW-AN Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.1
[3,11] SW-PROBLEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.2
[3,13] TELECOM-CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.3
[3,14] WRONG-CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.4
[3,246] CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Class 5: ENVIR Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
5.1
[5,1] FAN-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
5.2
[5,11] POWER-SUPPLY-U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
5.3
[5,12] POWER-SUPPLY-NU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
5.4
[5,13] CONTROL-UNIT-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
5.5
[5,20] MAINS-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.6
[5,23] POWER-SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
5.7
[5,24] SUBRACK-POWER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5.8
[5,31] TEMPERATURE-WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.9
[5,32] FATAL TEMPERATURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.10
[5,237] HW-DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
5.11
[5,239] HW-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Class 8: Global BTS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
6.1
[8,3] RESYNCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
6.2
[8,4] IGNORE EQUIPMENT OVER 12 TRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
6.3
[8,5] TOO MANY PLUGGED MODULES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
6.4
[8,8] HW-RESYNCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
6.5
[8,30] BCB-LINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
6.6
[8,31] IOM-LINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
6.7
[8,32] MODULE-INSERTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
6.8
[8,247] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
6.9
[8,248] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Class 9: BTS-EXTERNAL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
7.1
[9,1...56] EXT-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
7.2
[9,1] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
7.3
7.4
7.5
3 / 320
Contents
7.6
[9,5] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.7
7.8
7.9
7.10
7.11
[9,10] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.12
7.13
7.14
7.15
7.16
7.17
7.18
7.19
7.20
7.21
7.22
7.23
7.24
7.25
7.26
[9,25] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.27
7.28
7.29
7.30
7.31
7.32
7.33
7.34
7.35
7.36
7.37
7.38
7.39
7.40
7.41
7.42
7.43
7.44
7.45
7.46
7.47
7.48
7.49
7.50
7.51
7.52
7.53
7.54
7.55
7.56
7.57
Class 10: RX-TX Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1
[10,1] RSL-LINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2
[10,3] RX-CABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3
[10,10] TRE-VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4
[10,11] ANTENNA-VSWR-WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 / 320
155
157
159
161
163
165
167
169
171
173
175
177
179
181
183
185
187
189
191
193
195
195
196
196
197
197
198
198
199
199
200
200
201
201
202
202
203
203
204
204
205
205
206
206
207
207
208
208
209
209
210
210
211
212
215
219
222
Contents
10
8.5
[10,12] ANTENNA-VSWR-URGENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6
[10,21] MODULE-FRAME-SIGNAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.7
[10,22] MODULE-CLOCK-SIGNAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.8
[10,51] MODULE-NOT-PRESENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.9
[10,234] IOM-DISCONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.10
[10,237] HW-DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.11
[10,239] HW-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.12
[10,248] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Class 11: BTS-TRANS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1
[11,22] LOOP-TO-EQUIPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2
[11,50] LOSS-OF-INCOMING-SIGNAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3
[11,66] AIS-2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4
[11,81] LOSS-OF-FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5
[11,86] LOSS-OF-CRC-MULTIFRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.6
[11,99] ERROR-RATE >E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.7
[11,100] ERROR-RATE >E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.8
[11,102] ERROR-RATE >E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.9
[11,176] REMOTE-ALARM-INDICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.10
[11,177] PPP ALL1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.11
[11,178] PPP NO RECEIPT OF HDLC SIGNAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.12
[11,179] PPP RECEIPT OF TERMINATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.13
[11,180] HDLC HIGH ERRONEOUS FRAMES RATIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.14
[11,181] HDLC MEDIUM ERRONEOUS FRAMES RATIO . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.15
[11,182] HDLC LOW ERRONEOUS FRAMES RATIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS Alarm Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1
BTS Alarms with Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2
TLV Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
226
230
235
240
245
250
257
268
273
274
277
280
283
286
289
292
295
298
301
302
303
304
305
306
307
308
309
5 / 320
Contents
6 / 320
Preface
Preface
Purpose
The purpose of the alarm dictionary is to provide the operator with a structured
method for handling alarm messages generated by the BTS.
This document contains a list of all BTS alarms, and the actions required to
remove them.
Alarms are displayed at the OMC-R terminal and at the LMT to inform the
operator of system faults.
Note:
Document Pertinence
When a fault occurs, a number of alarms can be generated simultaneously.

These alarms must be analyzed as a group to determine the precise fault.
This document applies to release B11 of the BSS.
This document contains IP transport in the BSS related information. This
feature is available commercially from Release B11 MR3.
Whats New
In Edition 06
Release name was changed in Document pertinence.
The following alarms have been updated:
[3,11] SW-PROBLEM (Section 4.1)
[8,32] MODULE-INSERTED (Section 6.7)
In Edition 05
Description improvement for alarm [5,239] HW-FAILURE (Section 5.11) and
its corrective action.
In Edition 04
Alarm numbers 16, 17 and 18 have been added for alarm [3,14]
WRONG-CONFIGURATION (TRE) (Section 4.3.1).
Alarm number 16 was added for alarm [10,239] HW-FAILURE (TRE) (Section
8.11.1).
Alarm number 7 was added for alarm [1,237] HW-DEGRADED (Section 2.5)
was added.
Corrective action update for alarm number 15 of alarm [3,14]
WRONG-CONFIGURATION (RA) (Section 4.3.2).
Description improvement for alarm [5,24] SUBRACK-POWER (Section 5.7).
7 / 320
Preface
In Edition 03
The alarm Antenna Hopping not supported has been added in [3,14]
WRONG-CONFIGURATION (RA) (Section 4.3.2).
Description improvement in:
State change commands translation (Section 1.2.2)
LMT Alarm Messages (Section 1.4).
In Edition 02
Description improvement in:
[5,237] HW-DEGRADED (EACB) (Section 5.10.2)
[10,239] HW-FAILURE (TRE) (Section 8.11.1)
[5,237] HW-DEGRADED (RA) (Section 5.10.3) was added.
In Edition 01
First release of the document.
This document contains information about the following new features:
New ALMAP FM Module replacing AS in Alarm Type (Section 1.3.2)
Removal of the support of BTS with DRFU in Alarm Description (Section
1.5.2) and TLV Coding (Section 10.2).
Audience
Assumed Knowledge
This document is aimed at telecommunications operators responsible for

performing O&M fault handling and troubleshooting tasks.
The operator must be familiar with the following:
Alcatel-Lucent O&M concepts for the BSS
Fault management
Use of OMC-R and BTS NEM
SBL hierarchies of the BTS
Telecommunications techniques including line transmission and switching.
8 / 320
1 Introduction
1 Introduction
This section describes the structure of the BTS alarm messages.
9 / 320
1 Introduction
1.1 Overview
This alarm dictionary provides additional information that is not displayed in the
alarm messages sent to the OMC-R, BSC or TSS terminals.
The dictionary contains alarm definitions for each alarm type produced by
the BSS.
Each definition describes the:
Alarm description
Impact on System
Methods for further fault isolation
Corrective actions.
The descriptions of the alarms in this document is MO based for OMC -R
terminal purpose. For BTS LMT purpose, the SBL related information is
added in brackets if applicable.
1.2 Relationships Between SBLs and MOs

The BSS generates SBL based alarm indicators. For the 9153 OMC-R
purpose, this information is translated into MO format.
This section defines the relationships between SBL and MO formats.
1.2.1 SBL State to MO State Translation

The SBL state is translated into a related MO status according to following table:
SBL state
MO administrative
state
MO operational
state
MO availability state
MO control state
OPR
Locked
No change
{}
{}
IT
Unlocked
Enabled
{}
{}
FIT
Unlocked
Enabled
Degraded
{}
FLT
Unlocked
Disabled
Failed
{}
EF
Unlocked
Disabled
Dependency/failed
{}
FOS
Unlocked
Disabled
Off-line/failed
{}
SOS
Unlocked
Disabled
Dependency
{}
UT
Locked
No change
Under test
{}
WTC
Shutting down
Enabled
{}
{}
MSD/MSA
Unlocked
No change
{}
suspended
Table 1: SBL state to MO state translation
10 / 320
1 Introduction
1.2.2 State change commands translation

State changes of the MO equipment & functions can be done by OMC-R,
the state changes of the SBLs by the BTS-LMT. The following table shows
the translation of the commands.
OMC-R
LMT
Lock
Disable
Unlock
Init
Shutdown
Disable with WTC
Test
Test
Verify
Verify
Reset
Reset
Restart
Restart
Table 2: OMC-R to LMT state change commands translation

See document 9153 OMC-R Surveillance Handbook for use of the 9153
OMC-R commands, see document BTS NEM User Guide for the use of the
BTS LMT commands.
1.2.3 Mapping of MO Perceived Severity to BSS Alarm Category

The following table shows the mapping between the MO Perceived Severity
and the BSS Alarm Category.
MO Perceived Severity
BSS Alarm Category
BSS Alarm Condition
Cleared
End
Critical
VPMA, SA
Begin
Major
PMA
Begin
Minor
DMA
Begin
Warning
MI
Begin
Indeterminate
all categories
Event
11 / 320
1 Introduction
1.3 9153 OMC-R Alarm Surveillance Information

In the Alarm Surveillance of the 9153 OMC-R efficient means to control,
supervise and manage equipment problems in the MFS are provided.
Alarms or Alarm notifications consist of messages sent by network resources
that have detected problems or failures in the network. These alarms are
displayed in lists while alarm counters keep track of statistics. By clicking on an
alarm in the list, the operator gets detailed information. FM displays information
as described below.
1.3.1 Object Identification

The Object Identification identifies the resource that raised the alarm.
Object identification gives information about:
The resource type (Object Class)
The resource name (Friendly Name). For a board, the Friendly Name also
shows the boards location by rack, shelf and slot. For BTS 9100 outdoor
only: If the alarm message displays the RIT location A,0,0, the RIT is
located in the COMI/CODI side compartment.
12 / 320
1 Introduction
1.3.2 Alarm Type

The Alarm Type identifies the type of problem the alarm refers to.
This information is sub-divided into:
evenType. Table 3 describes the five evenTypes
probable Cause
perceived Severity: gives the severity level of the alarm. Table 4 describes
the severity levels.
evenType
Indicates....
Communication
a problem with a procedure or process used to convey information from

one point to another in the network.
Quality of Service
degradation in the quality of service in the network.
Processing Error
a software or processing fault.
Equipment
an equipment fault.
Environmental
a problem in the enclosure containing the equipment.
Table 3: Event Types
Severity Level
Indicates...
Critical
a serious fault condition which requires immediate corrections. Example: a

managed object goes out of service.
Major
a fault condition which requires urgent correction action. Example: severe

degradation in the operation of a managed object.
Minor
a fault condition which does not affect service but corrective action should
be taken to avoid a more serious fault.
Warning
detection of a potential fault condition. Action should be taken to diagnose

and correct the problem to avoid a more serious fault condition.
Indeterminate
the severity level cannot be defined by the resource which raised the alarm.
Cleared
the alarm was cleared by the resource which raised the alarm.
Table 4: Alarm Severity Levels

In addition the Object Identification and Alarm Type information, all alarms
always give the date and time of the alarm. An alarm may also contain optional
information, such as the notification id. Refer to the FM on-line help for more
detailed information on FM.
13 / 320
1 Introduction
1.4 LMT Alarm Messages

The format of Alarms displayed at a LMT differs from that in the OMC-R.
For more information about the BTS LMT see BTS NEM User Guide.
1.4.1 BTS LMT Alarm Message Parameters

Depending on the type of alarm and in which window it is viewed, an alarm
message contains all or most of the parameters listed in this section.
1.4.1.1 Message Identity

The identity number given to the alarm message stored in the database.
1.4.1.2 Event Time

The time the message was issued at its source or received at the BTS LMT.
1.4.1.3 Classification
The characteristics of the alarm, consisting of:
Alarm Class name and number - as shown in the Alarm Dictionary
Alarm Type name and number - as shown in the Alarm Dictionary
Alarm Number - dependent on the Alarm Class and Type. See the
appropriate dictionary entry for the valid alarm numbers for a particular alarm
Alarm Condition - has one of the following values:
begin - alarm on. For fatal failures, the affected SBL changes state to
FLT or FOS. For non-fatal failures, the affected SBL changes state to FIT
end - alarm off. Indicates the successful recovery of the system. The
affected SBL may not change state if other alarms related to the
SBL are on
event - occurrence of anomaly. No action is required unless it occurs
frequently. Event alarms are of short duration and the affected SBL
does not change state. The system retry/recovery mechanism has
cleared the fault.
1.4.1.4 Location
The origin of the alarm, consisting of:
Unit type
Unit number
SBL type
SBL number and subnumber, if appropriate.
14 / 320
1 Introduction
1.4.1.5 SBL States

If a fatal alarm occurs and the affected SBL changes state to FOS, the system
isolates the faulty equipment if it cannot be initialized. After a repair action, the
operator normally initializes the equipment.
If a fatal alarm occurs and the affected SBL changes state to FLT, the system
resets the faulty equipment. When the alarm ceases, the system automatically
initializes the equipment.
If a non-fatal alarm or event occurs, the affected SBLs are put into the FIT state.
In the worst situation, the equipment operates in a degraded mode.
An SBL has one of the following (current) states:
IT
FIT
Faulty
EF
FOS
OPR
SOS
WTC
UT
NEQ
MSD
MSD AUTO
Refer to the document Operations & Maintenance Principles for a description
of the states.
1.4.1.6 Suspected RIT

The information for the suspected RIT is displayed if the system is able to
determine the location of the fault.
The information consists of:
Unit type
Unit number
RIT type
Physical location - the position of the RIT board within the cabinet, defined
for the rack, shelf and slot. For BTS 9100 outdoor BTS only: If the
alarm message displays the RIT location A,0,0, the RIT is located in the
COMI/CODI side compartment.
If more than one RIT is shown in the list, the RIT most likely to be causing the
fault is indicated. Replace this RIT first and initialize it. If the fault persists,
replace another RIT from the list and initialize it.
15 / 320
1 Introduction
1.4.1.7 Additional Information

Some alarms provide additional information. If the additional information is
displayed as a text message, the original information from the BSS has been
decoded.
If the additional information is not decoded, it is displayed as pairs of
hexadecimal digits. At the BTS NEM, the additional information consists of
numbers in the range 0 to 255. Each number represents the contents of one
pair of digits.
Decoding additional information digits is described in section 10 .
Decoding Additional Information from Alarms
Decoding BTS or BSC additional information must only be attempted by
Alcatel-Lucent support personnel.
If a fault persists after corrective actions have been taken, send a copy of the
alarm message containing the additional information to the Alcatel-Lucent
support office.
16 / 320
1 Introduction
1.5 BTS Alarm Information

This section describes the definition of alarms as they appear on the OMC-R
and the alarm description given in the document.
1.5.1 Alarm Definition

The alarms are defined as follows:
1.5.1.1 specific Problems

This parameter, when present, identifies further refinements to the probable
Cause of the alarm. It qualifies the chosen probable Cause and may be
used by the managed object class to specify a set of identifiers for use in
managed object classes. The parameter is either a set of integers or a set
of object identifiers.
1.5.1.2 eventType
The eventType attribute identifies the basic type of the alarm.
It provides a list of standard types:
Communication: associated with the procedures and/or processes required
to convey information from one point to another.
Quality of Service: associated with a degradation of the quality of service.
Processing Error: associated with a software or processing fault.
Equipment: associated with an equipment fault.
Environmental: associated with a condition relating to an enclosure in
which the equipment resides.
1.5.1.3 probable Cause

This attribute defines the probable cause of the alarm. Its value belongs to
a set of possible values either defined in recommendation X.721, M3100
and GSM 11.12 or defined for a particular Telecommunication Management
Network (TMN) project.
1.5.1.4 perceived Severity

This attribute defines six severity levels. The severity levels indicate how the
capability of the managed object is affected.
The levels are:
Critical: indicates that an immediate corrective action is required. This
severity is reported, when a managed object becomes totally out of service
and its capability must be restored.
Major: indicates that an urgent corrective action is required. This severity
is reported, when there is a severe degradation in the capability of the
managed object and its full capability must be restored.
Minor: indicates a non-service affecting fault condition and that corrective
action should be taken in order to prevent a more serious fault. This severity
is reported, when the detected alarm condition is not currently degrading the
capacity of the managed object.
17 / 320
1 Introduction
Warning: indicates a potential or impending fault, before any significant

effect have been felt. Action(s) should be taken to further diagnose (if
necessary) and correct the problem in order to prevent it from becoming a
more serious service affecting fault.
Indeterminate: indicates that the severity level cannot be defined by the
resource raising the alarm.
Cleared: indicates the clearing of one or more previously alarms for this
managed object with the same Alarm type, Probable Cause and Specific
problems (if given).
1.5.2 Alarm Description

1.5.2.1 Banner
Each BSS alarm definition starts with an identification banner which allows the
location of the appropriate definition. It takes the form:
[7,246] FU CONFIG-FAIL
1.5.2.2 Alarm Description

Alarm Description describes the alarm and, where appropriate, the differences
to the default perceived severities and alarm numbers.
1.5.2.3 Impact on System

The description of the impact on Telecom and O&M system contains a table
indicating which part of the system is affected by the fault in terms of loss,
degradation or none.
For example, if a cell is affected, the cell column in the table contains a
check (X) in either the Loss or Degradation row. For different impact cases
(redundancy, diversity, etc.) other symbols are used.
The table shows the worst case, even though redundancy may be provided.
1.5.2.4 Corrective Actions

So solve the current alarm a graphical workflow chart is used. It shows the
required procedures by checks, tests and actions to determine the fault and
finally to solve the alarm.
Checks, tests and thus resulting corrective actions are provided with a
priority on remote at the OMC-R and then by service on-site, to minimize the
maintenance effort.
By clicking on a dedicated action field, a link to the detailed description of the
task will be opened.
18 / 320
1 Introduction
Start field with alarm number

and alarm name
[5,11] POWERSUPPLYU
Onsite
Check Power
Supplies are
switched on
Remote action fields
Onsite
Check
cables/connectors to
control unit, power
module and EACB
no
Decision field
Alarm
solved
Alarm persists?
yes
Onsite
9100 BTS: Replace
PM08, which LED is
off or red *
Onsite
Onsite
OR
9100 BTS: Replace

PM11, which LED is
off or red *
Decision field
OR
9100 BTS: Replace

PM12, which LED is
off or red *
Power supply
operational?
yes
Onsite
OR
9100 BTS: Replace

PM18, which LED is
off or red *
Onsite action fields
Alarm
solved
no
Contact
System Support
End fields
Figure 1: Graphical workflow for corrective actions

This figure shows an example of a graphical workflow and describes the
different flowchart fields. Useful hints for safety and required tools are added
as appropriate.
19 / 320
1 Introduction
1.5.3 Additional Information

section BTS Alarm Additional Information (Section 10) describes the decoding
of the additional information.
Some alarms provide additional information. If the additional information is
displayed as a text message, the original information from the BSS has been
decoded.
If the additional information is not decoded, it is displayed as pairs of
hexadecimal digits. At the BSC terminal, the additional information consists
of numbers in the range 0 to 255. Each number represents the contents
of one pair of digits.
Decoding Additional Information from Alarms
Decoding BSC additional information must only be attempted by Alcatel-Lucent
support personnel.
If a fault persists after corrective actions have been taken, send a copy of the
alarm message containing the additional information to the Alcatel-Lucent
support office.
20 / 320
2 Class 1: CLK Alarms

This section defines the alarms for the Class 1: CLK alarm class.
21 / 320
2.1 [1,6] MCL-FATAL-AL

specific Problems
MCL-FATAL-AL
event Type
Equipment
probable Cause
Equipment Malfunction
perceived Severity
Major (PMA)
Alarm Description
Fatal internal alarm on the Clock Unit.
Alarm Number
1 : Module faulty with unknown cause due to access failure

2 : The internal clock is defective
4 : Fault on the clock signal is detected by other module
5 : Autorestart failure
If the CLLK is redundant on this BTS, the telecom functions are not affected.
If no redundancy is available however, the cell(s) fed by the reporting CLLK are lost.
BTS 9100: There is no clock redundancy available, so the cells fed by the reporting CLLK are lost, thus
the BTS is lost.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
X(no red.)
X(no red.)
X(no red.)
Degradation
X(no red.)
22 / 320
2.1.1 BTS 9100 Corrective Actions

[1,6] MCLFATALAL
Reset Function
BTS
Clock
operational?
yes
Alarm
solved
no
Onsite
Replace
SUMP, SUMA
Clock
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 2: MCL-FATAL-AL: BTS 9100 Corrective Actions
23 / 320
2.1.2 BTS 9110/9110-E Corrective Actions

[1,6] MCLFATALAL
Reset Function
BTS
Clock
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Onsite
Switch off Battery

Backup Switch and
OR
Main Power switch in
Side Support Cabinet
Switch off mains

power fuse for tower
mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 3: MCL-FATAL-AL: BTS 9110/9110-E Corrective Actions
24 / 320
2.2 [1,12] CLOCK-FAULT

specific Problems
CLOCK-FAULT
event Type
Equipment
probable Cause
Timing Problem
perceived Severity
Major (PMA), Minor (DMA)
Alarm Description
Major (PMA)/Minor (DMA) : Fault on the clock signals detected by several

clock users in the BTS (e.g. FHU, CU, FU).
Major (PMA) : If the CLLK alarm disappears and the OMU loses the alarm
information, this alarm is sent by the OMU as a dummy alarm. It indicates
that the CLLK is FOS and requires operator initialization.
If the alarm has unknown cause, it indicates that more detailed alarms
were reported before and are available at OMC-R.
If the clock system is redundant on this BTS, the telecom functions are not affected.
If, however, no redundancy is available, the channels supported by the CLLK/CLDB are lost.
BTS 9100: There is no clock redundancy available, so the cells fed by the reporting CLLK are lost, thus
the BTS is lost.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
X(no red.)
X(no red.)
X(no red.)
Degradation
X(no red.)
25 / 320

[1,12] CLOCKFAULT
Reset Function
BTS
Clock
operational?
yes
Alarm
solved
no
Onsite
Replace
SUMP, SUMA
Clock
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 4: CLOCK-FAULT: BTS 9100 Corrective Actions
26 / 320

[1,12] CLOCKFAULT
Reset Function
BTS
Clock
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Onsite
Switch off Battery

Backup Switch and OR
Switch off mains

mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 5: CLOCK-FAULT: BTS 9110/9110-E Corrective Actions
27 / 320
2.3 [1,31] MCL-XCLK

specific Problems
MCL-XCLK
event Type
Equipment
probable Cause
perceived Severity
Major (PMA)
Alarm Description
An error has been detected in the input of the External Reference Clock.
Alarm Number
1 : Loss of input signal clock from external reference clock, in slave mode.
2 : Loss of Frame Number input, in slave mode.
3 : Loss of Frame Signal, in slave mode.
If the CLLK is redundant on this BTS the telecom functions are not affected.
If, however, no redundancy is available, the cell(s) fed by the reporting CLLK are lost.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
X(no red.)
X(no red.)
X(no red.)
Degradation
X(no red.)
28 / 320

[1,31] MCLXCLK
Alarm on
feeding clock unit
of master BTS
events?
no
Reset Function
BTS
yes
Solve that
alarm(s) first
Clock
operational?
yes
Alarm
solved
no Onsite
Check
cables/connectors
between clock unit
on master BTS and
reporting clock unit
Onsite
Replace
SUMP, SUMA
Clock
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 6: MCL-XCLK: BTS 9100 Corrective Actions
29 / 320

[1,31] MCLXCLK
Alarm on
feeding clock unit
of master BTS
events?
no
Onsite
Reset Function
BTS
Disconnect mains
power from ACCO
to Basic Unit
Onsite
OR Onsite
yes
Solve that
alarm(s) first
Clock
operational?
no
Check
cables/connectors
between clock unit
on master BTS and
reporting clock unit
Switch off Battery

Backup Switch and
OR Onsite
yes
Switch off mains

mounted BTS
Alarm
solved
Onsite
After 30 s
repower the BTS
Onsite
Replace
BTS A910
no
BTS
operational?
yes
Alarm
solved
yes
BTS
operational?
Alarm
solved
no
Contact
System Support
Figure 7: MCL-XCLK: BTS 9110/9110-E Corrective Actions
30 / 320
2.4 [1,234] IOM-DISCONNECTION

specific Problems
IOM-DISCONNECTION
event Type
Equipment
probable Cause
perceived Severity
Minor (DMA)
Alarm Description
There is a loss of communication with the clock on the IOM bus.
Telecom functions are not affected.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
2.4.1 Corrective Actions

Contact your Alcatel-Lucent system support.
31 / 320
2.5 [1,237] HW-DEGRADED

specific Problems
HW-DEGRADED
event Type
Equipment
probable Cause
perceived Severity
Minor (DMA), Warning (MI)
Alarm Description
The processing of the clock is degraded.
Alarm Number
1: The PCM synchronization is not available.

2: The GPS synchronization is lost.
3: GPS module failure.
4: GPS antenna failure.
5: GPS LNA failure.
6: Not enough satellites are visible.
7: Frequency synchronization is lost.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
Required tools and materials :

PCM test tools
GPS test tools
Replacement tools, see appropriate replacement procedure.
32 / 320
2.5.1 9100 BTS, Alarm Number 1 Corrective Actions

Alarm Number 1
[1,237] HWDEGRADED
Related
transmission
alarms?
yes
Solve this alarms
Alarm persists?
yes
no
WAIT 20 minutes
(Clock
synchronisation
ongoing)
no
no
Alarm persists?
yes
Reset BTS
Alarm persists?
no
yes
Power OFF BTS.

Wait 30 seconds.
Power ON BTS.
Wait until BTS is
operationsl again.
Alarm persists?
no
Alarm
solved
yes
Check / correct
internal 13MHz clock
no
Alarm persists?
yes
Replace
SUMx
no
Alarm persists?
yes
Check E1 link clock

with line provider
no
Alarm persists?
yes
Contact
System Support
Figure 8: HW-DEGRADED: 9100 BTS, Alarm Number 1 Corrective Actions
33 / 320
2.5.2 9100 BTS, Alarm Number 2, 3, 4 , 5 and 6 Corrective Actions

Alarm Number 2, 3, 4, 5 and 6
[1,237] HWDEGRADED
Related
transmission
alarms?
yes
Solve this alarms
Alarm persists?
yes
no
WAIT 20 minutes
(Clock
synchronisation
ongoing)
no
no
Alarm persists?
yes
Check GPS
equipment
no
Alarm persists?
yes
Reset BTS
Alarm persists?
no
Alarm
solved
yes
Power OFF BTS.

Wait 30 seconds.
Power ON BTS.
Wait until BTS is
operationsl again.
Alarm persists?
no
yes
Check / correct
no
Alarm persists?
yes
Replace
SUMx
no
Alarm persists?
yes
Check E1 link clock

with line provider
no
Alarm persists?
yes
Contact
System Support
Figure 9: HW-DEGRADED: BTS 9100, Alarm Number 2, 3, 4, 5 and 6 Corrective Actions
34 / 320
2.5.3 9100 BTS, Alarm Number 7 Corrective Actions

Alarm Number 7
[1,237] HWDEGRADED
Check / correct NTP

server configuration
Alarm persists?
no
Alarm
solved
yes
Contact
System Support
Figure 10: HW-DEGRADED: BTS 9100, Alarm Number 7 Corrective Actions
35 / 320
2.5.4 9110 Micro BTS/9110-E Micro BTS , Alarm Number 1 Corrective

Actions
Alarm Number 1
[1,237] HWDEGRADED
Related
transmission
alarms?
yes
Solve this alarms
Alarm persists?
yes
no
WAIT 20 minutes
(Clock
synchronisation
ongoing)
no
no
Alarm persists?
yes
Reset BTS
Alarm persists?
no
yes
Power OFF BTS.

Wait 30 seconds.
Power ON BTS.
Wait until BTS is
operationsl again.
Alarm persists?
no
Alarm
solved
yes
Check / correct
no
Alarm persists?
yes
Replace
9110 Micro BTS /
9110E Micro BTS
no
Alarm persists?
yes
Check E1 link clock

with line provider
no
Alarm persists?
yes
Contact
System Support
Figure 11: HW-DEGRADED: 9110 Micro BTS/9110-E Micro BTS , Alarm Number 1 Corrective Actions
36 / 320
2.5.5 9110 Micro BTS/9110-E Micro BTS, Alarm Number 2 Corrective

Actions
Alarm Number 2
[1,237] HWDEGRADED
Related
transmission
alarms?
yes
Solve this alarms
Alarm persists?
yes
no
WAIT 20 minutes
(Clock
synchronisation
ongoing)
no
no
Alarm persists?
yes
Check GPS
equipment
no
Alarm persists?
yes
Reset BTS
Alarm persists?
no
Alarm
solved
yes
Power OFF BTS.

Wait 30 seconds.
Power ON BTS.
Wait until BTS is
operationsl again.
Alarm persists?
no
yes
Check / correct
no
Alarm persists?
yes
Replace
9110 Micro BTS /
9110E Micro BTS
no
Alarm persists?
yes
Check E1 link clock

with line provider
no
Alarm persists?
yes
Contact
System Support
Figure 12: HW-DEGRADED: 9110 Micro BTS/9110-E Micro BTS ,Alarm Number 2 Corrective Actions
37 / 320
2.6 [1,248] RESTART

specific Problems
RESTART
event Type
Processing Error
probable Cause
Application Subsystem Failure
perceived Severity
Warning (MI)
Alarm Description
The TRANSandCLOCK has performed a successful autorestart.
Alarm Number
1 : A fatal exception has occurred on a P, or a P SW error is detected

in operational state.
2 : A watchdog reset has occurred.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
38 / 320

[1,248] RESTART
Reset Function
BTS
Clock
operational?
yes
no
Alarm is
reported very
often on one
board?
no
Alarm
solved
yes
Onsite
Replace SUMP,
SUMA
Clock
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 13: RESTART: BTS 9100 Corrective Actions
39 / 320

[1,248] RESTART
Reset Function
BTS
Clock
operational?
Alarm is
reported very
often on one
board?
yes
no
OR
Alarm
solved
yes
Onsite
Disconnect mains
power from ACCO
to Basic Unit
no
Onsite
Onsite
Switch off Battery

Switch off mains power
Backup Switch and
OR fuse for tower mounted
BTS
Onsite
After 30 s
repower the BTS
Onsite
Clock
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 14: RESTART: BTS 9110/9110-E Corrective Actions
40 / 320
3 Class 2: OMU Alarms

This section defines the alarms for the Class 2: OMU alarm class.
41 / 320
3.1 [2,1] LOSS OF TWIN CONFIGURATION

specific Problems
LOSS OF TWIN CONFIGURATION
event Type
Processing Error
probable Cause
softwareProgramAbnomallyTerminated
perceived Severity
Warning (MI)
Alarm Description
This event arrives in seldom circumstances where storage has been

destroyed or is no more readable.
Any other alarms should be checked and repaired first.
The OMU will apply the default twin configuration.
Alarm Number
1 : OMU does not retrieve the twin configuration.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
42 / 320

[2,1] LOSS OF TWIN
CONFIGURATION
Set the desired

configuration from
OMCR if selectable
due to cabling
Alam cleared?
yes
no
On site
From BTS LMT
perform the
modification of the
HW configuration
Alam cleared?
yes
Alarm
solved
no
Replace SUMA board
yes
Alam cleared?
no
Contact
System Support
Figure 15: LOSS OF TWIN CONFIGURATION Corrective Actions
43 / 320
3.2 [2,247] RESET

specific Problems
RESET
event Type
Processing Error
probable Cause
softwareProgramAbnomallyTerminated
perceived Severity
Warning (MI)
Alarm Description
An OMU reset is performed. The Alarm Number indicates the reason for
the reset.
During the reset procedure, the OMU had a BTS software download and
started its operational software. It distributed the configuration data to all
BTSs and rebuilt its internal database.
Alarm Number
3 : Triggered by Watchdog (any reason).

4 : External scenario failure.
5 : Lack of internal resources.
6 : Internal scenario time out.
7 : Microprocessor exception.
8 : Mains alarm end.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
44 / 320
3.2.1 Alarm Number 3 Corrective Actions

The hardware is faulty or there is a bug in the software. If only one BTS is
concerned or the alarm occurs repeatedly, replace the faulty hardware.
[2,247] RESET
Onsite
Onsite
9100:
Replace SUMP,
SUMA, SUMX
OR
9110/9110E Micro
BTS: Replace
9110/9110E Micro
BTS
OMU
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 16: RESET: Alarm Number 3 Corrective Actions

The communication with the BSC is disturbed.
[2,247] RESET
Onsite
Check cables and

connectors to BSC
Onsite
OMU
operational?
yes
Alarm
solved
no
Contact
System Support
45 / 320

There is a problem with the memory allocation.
[2,247] RESET
Contact
System Support

The OMU detects a problem in the running OMU software and attempts to it
clean up.
[2,247] RESET
Contact
System Support
46 / 320

An interrupt caused by an address or by a bus problem.
If the alarm occurs repeatedly :
[2,247] RESET
Onsite
Onsite
9100 BTS:
Replace SUMP,
SUMA, SUMX
9110/9110E Micro
BTS: Replace
9110/9110E Micro
BTS
OR
OMU
operational?
yes
Alarm
solved
no
Contact
System Support

The power supply is again available for the BTS.
47 / 320
3.3 [2,248] RESTART

specific Problems
RESTART
event Type
Processing Error
probable Cause
perceived Severity
Warning (MI)
Alarm Description
An OMU restart is performed successfully. The reason for the restart is

indicated in the Alarm Number field.
During the restart procedure the OMU has restarted its software, distributed
its configuration data to all BTS units, and re-built its internal database.
Alarm Number
1 : Lack of internal resources, allocating the memory.

2 : Triggered for OMU-CPF replacement.
3 : The OMU detects an internal scenario time out in the running OMU
software, and attempts to clean it up.
4 : Microprocessor exception - an interrupt is caused by an address or
a bus problem.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

None. If the problem persists, a reset is triggered automatically.
48 / 320
4 Class 3: SW-AN Alarms

This section defines the alarms for the Class 3: SW-AN alarm class.
49 / 320
4.1 [3,11] SW-PROBLEM

4.1.1 [3,11] SW-PROBLEM (CLLK)
specific Problems
SW-PROBLEM
event Type
Processing Error
probable Cause
software Program Abnormally Terminated
perceived Severity
Nbr 1...3:Major (PMA)

Nbr 4, 5: Minor (DMA), Warning (MI)
Alarm Description
The software is corrupted or bad.
Alarm Number
1 : Error detected during the configuration with saved parameters in

initialization state: saved parameters are corrupted and cannot be used for
the auto-restart sequence.
2 : Error detected during the SW activation procedure in the fault
localization state, or a check-sum error is detected in operational state.
3 : A fatal exception has occurred on P, or a P SW error is detected in a
state other than the operational state.
4 : An error has occurred during the SW activation procedure, triggered
by the OMU in the initialization state. The alarm is not fatal because the
TRANS&CLOCK uses the previous FW.
5 : An error has occurred which is linked to a software download. The
error was detected during the downloading procedure from the OMU in
initialization state (packet sequence, global file checksum). This alarm is
not fatal because the TRANS&CLOCK uses the previous FW.
For the BTS 9100: there is no clock redundancy available, so the cells fed by the reporting CLLK are
lost, thus the BTS is lost.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
X(no red.)
X(no red.)
X(no red.)
Degradation
X(no red.)
50 / 320
4.1.1.1 BTS 9100 Corrective Actions

[3,11] SWPROBLEM
(CLLK)L
Reset Function
BTS
Clock
operational?
yes
Alarm
solved
no
Onsite
Replace
SUMP, SUMA
Clock
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 21: SW-PROBLEM (CLLK): BTS 9100 Corrective Actions
51 / 320
4.1.1.2 BTS 9110/9110-E Corrective Actions

[3,11] SWPROBLEM
(CLLK)
Reset Function
BTS
Clock
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
Onsite
OR
Onsite
Switch off Battery

Backup Switch and
OR
Switch off mains

mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
9110 BTS
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 22: SW-PROBLEM (CLLK): BTS 9110/9110-E Corrective Actions
52 / 320
4.1.2 [3,11] SW-PROBLEM (TRE)

specific Problems
SW-PROBLEM
event Type
Processing Error
probable Cause
perceived Severity
Major (PMA), Warning (MI)
Alarm Description
Alarm Number
1 : An error is detected during the configuration with saved parameters in

Major (PMA) : The local recovery fails.
Warning (MI) : The local recovery is successful.
2 : An error is detected during the SW activation procedure in the fault
localization state or check-sum error detected in operational state.
3: A fatal exception occurred on SCP or a SCP, the software error is
detected in another state than the operational state.
4 : An error detected during the software activation procedure, triggered
by the OMU in initialization state.
5 : An error is linked to software down-load. The error is detected during
the down-loading procedure from the SUM, in initialization state (packet
sequence, global file check-sum, etc.).
6 : A watchdog has occurred and an auto-restart has failed.
7 : A bad parameter is detected in the TRE CPF.
8: LRA triggered on G3 TRE as consequence of SCP RTF supervision
algoritm.
53 / 320
The TRE is no longer usable. The associated eight channels are lost. Independent of frequency hopping
or not, the BSC reduces the number of channels supported by the cell.
If the TRE supporting the BCCH is not concerned, the cell is degraded, calls are lost. (#).
If the TRE supporting the BCCH is concerned and there is BCCH redundancy, recovery mechanisms
regain the cells functionality. (*).
If the TRE supporting the BCCH is concerned and there is no BCCH redundancy, the complete cell
is lost. (X).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
X(no red.)
X(no red.)
X(no red.)#*
Degradation
X(no red.)
#*
54 / 320

Disable RF Power
Use the BTS NEM to disable RA before disconnecting RF cables.
Initialize RA after work.
[3,11] SWPROBLEM
(TRE)
Lock Function
TRE
Unlock Function
TRE
TRE
operational?
yes
Alarm
solved
no
Alarm is
reported from more
than one
TRE?
yes
Contact
System Support
no Onsite
Replace TRE
TRE
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 23: SW-PROBLEM (TRE): BTS 9100 Corrective Actions
55 / 320

[3,11] SWPROBLEM
(TRE)
yes
Reset Function
BTS
BTS
operational?
Alarm
solved
no
Alarm is
reported from more
than one
BTS?
yes
Contact
System Support
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
Onsite
OR
Onsite
Switch off Battery

Backup Switch and
OR
Switch off mains

mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
9110 BTS
yes
Alarm
solved
BTS
operational?
yes
no
Contact
System Support
Figure 24: SW-PROBLEM (TRE): BTS 9110/9110-E Corrective Actions
56 / 320
Alarm
solved
4.1.3 [3,11] SW-PROBLEM (RA)

specific Problems
SW-PROBLEM
event Type
Processing Error
probable Cause
perceived Severity
Alarm Description
Alarm Number
1 : Error detected during the configuration with saved parameters in

2 : Error detected during the SW activation procedure in the fault
localization state or check-sum error detected in operational state.
3: A fatal exception occurred on SCP or a SCP, the SW error is detected in
another state than the operational state.
5 : Error linked to software down-load. Error detected during the
down-loading procedure from the OMU, in initialization state (packet
sequence, global file check-sum, etc.).
The transmission quality is degraded.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
57 / 320

Disable RF Power
[3,11] SWPROBLEM (RA)
Lock Function
RA
Unlock Function
RA
RA
operational?
yes
Alarm
solved
no
Alarm is
reported from more
than one
BTS?
no
yes
Contact
System Support
Onsite
Replace
ANX, ANY, ANC
RA
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 25: SW-PROBLEM (RA): Corrective Actions
58 / 320
4.2 [3,13] TELECOM-CONFIG-FAIL

specific Problems
TELECOM-CONFIG-FAIL
event Type
Processing Error
probable Cause
Configuration Or Customization Error
perceived Severity
Warning (MI)
Alarm Description
A Telecom Configuration Parameter error has been detected.
Alarm Number
1 : There is a rejection of the telecom configuration parameters

related to Hand-Over and Power Control (parameters included
in BS_POWER_CONTROL, MS_POWER_CONTROL or
PREPROCESS_CONFIGURE messages) in the operational state.
A message is missing in the list of telecom messages received.
2 : The TLC_CONFIG_T timer (supervision of reception of telecom
configuration on RSL) has elapsed after an O&M configuration or
re-configuration.
3 : Incorrect sys info 3 parameters have been received in the operational
state.
4 : Inconsistent telecom configuration messages have been received from
the BSC after an O&M reconfiguration.
5 : No correct BCCH info messages have been received from the BSC
after an O&M reconfiguration.
Telecom functions are not affected. The old configuration is still running.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
59 / 320

[3,13] TELECOM
CONFIGFAIL
Check OMU CPF
Correct BTS
Characteristic
Alarm persists?
no
Alarm
solved
yes
Contact
System Support
Figure 26: TELECOM-CONFIG-FAIL: Corrective Actions
60 / 320
4.3 [3,14] WRONG-CONFIGURATION

4.3.1 [3,14] WRONG-CONFIGURATION (TRE)
specific Problems
WRONG-CONFIGURATION
event Type
Processing Error
probable Cause
perceived Severity
Major (PMA)
Alarm Description
The parameters are not consistent with the capacity of the equipment.
Alarm Number
1 : The CDM radio definition per TS is inconsistent with the hopping type.
2 : The CDM frequency range is inconsistent with the actual frequency
range.
3 : The CDM cell range is inconsistent with the extended cell support.
4 : There are files missing in SUM memory for a given module type.
5 : The RSL rate between CDM and Abis is inconsistent.
6 : The CDM capability is inconsistent with the actual capability.
7 : A bad parameter is detected in configuration data.
8 : There is no RSL/TCH mapping available for the TRE.
9 : The RSL mapping is wrong, the TRE does not support a RSL on the
indicated Abis interface.
11 : The TRE does not support the required PS capabilities.
16 : The bandwidth per MC-module is larger than the PA RF BW.
17 : Wrong OML/RSL multiplexing rule.
18 : The multi-carrier class is not compatible with the multi-carrier class
capability.
regain the cells functionality, calls are lost. (*)
is lost. (X).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
X(no red.)
X(no red.)
X(no red.)#*
Degradation
X(no red.)
#*
61 / 320
4.3.1.1 Alarm Number 1, 2, 3, 6, Corrective Actions

[3,14]
WRONGCONFIGURATION
(TRE)
Other
TRE alarms
event?
yes
Solve TRE
alarm(s) first
no
Compare CDM
value with TRE
capability
Correct
parameter values
according to TRE
capability
Reset effected
TCU
Alarm persists?
no
Alarm
solved
yes
Contact
System Support
Figure 27: WRONG-CONFIGURATION (TRE): Alarm Number 1, 2, 3, 6,

Corrective Actions
62 / 320
4.3.1.2 Alarm Number 4, Corrective Actions

[3,14]
WRONGCONFIGURATION
(TRE)
Other
TRE alarms
event?
yes
Solve TRE
alarm(s) first
no
Download the
masterfile and
the application
file
Replace the
masterfile
Reset effected
TCU
Alarm persists?
no
Alarm
solved
yes
Contact
System Support
Figure 28: WRONG-CONFIGURATION (TRE): Alarm Number 4, Corrective

Actions
63 / 320

[3,14]
WRONGCONFIGURATION
(TRE)
Other
TRE alarms
event?
yes
Solve TRE
alarm(s) first
no
Compare CDM value
with RSL rate
Correct parameter
values according to TRE
capability
Reset effected TCU
Alarm persists?
no
Alarm
solved
yes
Contact
System Support

Actions
64 / 320
4.3.1.4 Alarm Number 7, 9, Corrective Actions

[3,14]
WRONGCONFIGURATIO
N (TRE)
Other
TRE alarms
event?
yes
Solve TRE
alarm(s) first
no
Compare CDM
value
Correct
parameter values
according to TRE
capability
Reset effected
TCU
Alarm persists?
no
Alarm
solved
yes
Contact
System Support
Figure 30: WRONG-CONFIGURATION (TRE): Alarm Number 7, 9, Corrective

Actions
65 / 320

[3,14]
WRONGCONFIGURATION
(TRE)
Other
TRE alarms
event?
yes
Solve TRE
alarm(s) first
no
Compare
transmission
settings
Introduce
RSL/TCH
mapping
Initialize TRE
Reset effected
TCU
Alarm persists?
no
Alarm
solved
yes
Contact
System Support

Actions
66 / 320

[3,14]
WRONGCONFIGURATION
(TRE)
Compare CDM
value with BTS
capability
Correct parameter
values with correct
Abis configuration
according to BTS
capability
Reset effected
BTS
Alarm persists?
no
Alarm
solved
yes
Contact
System Support

Actions
67 / 320

[3,14]
WRONGCONFIGURATION
(TRE)
Choose a lower
bandwidth per
MCTRE module.
Alarm persists?
no
Alarm
solved
yes
Contact
System Support

Actions

[3,14]
WRONGCONFIGURATION
(TRE)
For Multicarrier
modules 16 kb/s rate
for RSL is not allowed.
Correct the RSL rate.
Alarm persists?
no
Alarm
solved
yes
Contact
System Support

Actions
68 / 320

[3,14]
WRONGCONFIGURATION
(TRE)
Choose the correct

multicarrier class.
Alarm persists?
no
Alarm
solved
yes
Contact
System Support

Actions
69 / 320
4.3.2 [3,14] WRONG-CONFIGURATION (RA)

specific Problems
WRONG-CONFIGURATION
event Type
Processing Error
probable Cause
perceived Severity
Nbr. 2: Major (PMA)

Nbr. 4, 7, 10: Minor (DMA), Warning (MI)
Alarm Description
Alarm Number
2 : The CDM frequency range is inconsistent with the actual frequency

range.
4 : There are files missing in OMU memory for a given module type.
7 : A bad parameter is detected in configuration data.
The sector cannot provide the required maximum output power (SBL state
FIT, severity DMA).
10 :
The sector cannot provide the required maximum output power (SBL
state FIT, severity DMA)
In case of cell shared, the power of secondary is lower than the one
of the main sector.
In unbalanced TRX output power configuration, at least one of the TREs
of this sector cannot provide the requested output power.
15: Antenna Hopping not supported.
The quality of transmission is degraded.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
70 / 320
4.3.2.1 Alarm Number 2, 7,10, Corrective Actions

[3,14]
WRONGCONFIGURATION
(RA)
Compare CDM
value with RA
capability
Correct
parameter values
according to RA
capability
Reset effected
RA
Alarm persists?
no
Alarm
solved
yes
Contact
System Support
Figure 36: WRONG-CONFIGURATION (RA): Alarm Number 2, 7, 10,

Corrective Actions
71 / 320

[3,14]
WRONGCONFIGURATION
(RA)
Compare CDM
value with RA
capability
Replace
masterfile
Reset effected
RA
Alarm persists?
no
Alarm
solved
yes
Contact
System Support
Figure 37: WRONG-CONFIGURATION (RA): Alarm Number 4, Corrective

Actions
72 / 320
4.3.2.3 Alarm Number 15 Corrective Actions

[3, 14]
WRONGCONFIGURATION
(RA)
No hardware supporting
Antenna Hopping is
available.
There are two solutions:
Onsite
Insert TWIN TRE

module
or
Disable
Antenna Hopping
feature for the impacted
sector
no
Alarm
persists?
Alarm
solved
yes
Contact
System Support
Figure 38: WRONG-CONFIGURATION (RA): Alarm Number 15, Corrective

Action
73 / 320
4.3.3 [3,14] WRONG-CONFIGURATION (BTS)

specific Problems
WRONG-CONFIGURATION
event Type
Processing Error
probable Cause
perceived Severity
Alarm Description
Alarm Number
12 : A configuration with 2 PCM links is not supported.

13 : The OML is not on Abis 1.
14 : The configuration via the Qmux is not allowed with 2 PCM links.
There is no impact.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
74 / 320
4.3.3.1 Alarm Number 12, 14, Corrective Actions

[3,14]
WRONGCONFIGURATION
(BTS)
Compare CDM
value with BTS
capability
Correct
parameter values
according to BTS
capability
Reset effected
BTS
Alarm persists?
no
Alarm
solved
yes
Contact
System Support
Figure 39: WRONG-CONFIGURATION (BTS): Alarm Number 12, 14,

Corrective Actions
75 / 320

[3,14]
WRONGCONFIGURATION
(BTS)
Compare CDM
value with BTS
capability
Place OML TS
on Abis 1
Reset effected
BTS
Alarm persists?
no
Alarm
solved
yes
Contact
System Support
Figure 40: WRONG-CONFIGURATION (BTS): Alarm Number 13, Corrective

Actions
76 / 320
4.4 [3,246] CONFIG-FAIL

4.4.1 [3,246] CONFIG-FAIL (CLLK)
specific Problems
CONFIG-FAIL
event Type
Processing Error
probable Cause
perceived Severity
Nbr 1: Major (PMA))

Nbr 3, 4: Minor (DMA), Warning (MI)
Alarm Description
There is a scenario-failure for TRANS&CLOCK.
Alarm Number
1 : An error in the initialization or re-configuration is detected, due to the

absence of an answer to the message "OMU, UNKNOWN_MESSAGE,
inconvenient sub-state".
3 : A SW downloading or SW activation failure is detected by the
OMU, due to the absence of an answer to the message "OMU.
UNKNOWN_MESSAGE, inconvenient sub -state". This alarm is not fatal
because the TRANS&CLOCK uses the previous SW.
4 : A transmission configuration failure is detected by the OMU due to no
answer to the OMU, an UNKNOWN MESSAGE or an inconvenient substate.
This alarm has no fatal consequences, because the TRANS&CLOCK will
use the previous transmission settings.
For the BTS 9100: there is no clock redundancy available, so the cells fed by the reporting CLLK are
lost, thus the BTS is lost.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
X(no red.)
X(no red.)
X(no red.)
Degradation
X(no red.)
77 / 320

[3,246] CONFIGFAIL
(CLLK)
Check validity of
parameters
Correct parameter
values according
to BTS capability
Reset effected
BTS
Alarm persists?
no
Alarm
solved
no
Alarm
solved
yes
Onsite
Replace
SUMP, SUMA
Alarm persists?
yes
Contact
System Support
Figure 41: CONFIG-FAIL (CLLK): BTS 9100 Corrective Actions
78 / 320

[3,246] CONFIGFAIL
(CLLK)
Check validity of
parameters
Correct parameter
values according
to BTS capability
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Onsite
Switch off Battery

Backup Switch and
BTS
Onsite
After 30 s
repower the BTS
Onsite
Replace
BTS A910
no
BTS
operational?
yes
Alarm
solved
yes
BTS
operational?
Alarm
solved
no
Contact
System Support
Figure 42: CONFIG-FAIL (CLLK): BTS 9110/9110-E Corrective Actions
79 / 320
4.4.2 [3,246] CONFIG-FAIL (RA)

specific Problems
CONFIG-FAIL
event Type
Processing Error
probable Cause
perceived Severity
Nbr 2: Major (PMA)

Nbr 1: Minor (DMA)
Alarm Description
There is a scenario-failure for ANX or RA.
Alarm Number
1 : An error in the initialization is detected due to no answer to OMU,

UNKNOWN_MESSAGE, inconvenient sub-state.
2 : An error in the initialization is detected due to failure in initialization of all
TREs connected to this ANX or RA.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
80 / 320

Disable RF Power
[3,246] CONFIGFAIL (RA)
Lock Function
RA
Unlock Function
RA
RA
operational?
yes
Alarm
solved
no
Onsite
Replace
ANX, ANY, ANC
RA
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 43: CONFIG-FAIL (RA): BTS 9100 Corrective Actions
81 / 320

[3,246] CONFIGFAIL (RA)
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Onsite
Switch off Battery

Backup Switch and
OR
Switch off mains

mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
yes
BTS
operational?
Alarm
solved
no
Contact
System Support
Figure 44: CONFIG-FAIL (RA): BTS 9110/9110-E Corrective Actions
82 / 320
4.4.3 [3,246] CONFIG-FAIL (TRE)

specific Problems
CONFIG-FAIL
event Type
Processing Error
probable Cause
perceived Severity
Major (PMA)
Alarm Description
There is a scenario failure for TRE.

An error in the initialization is detected due to no answer to OMU,
UNKNOWN_MESSAGE, inconvenient sub-state.
regain the cells functionality, calls are lost. (*).
is lost. (X).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
X(no red.)
X(no red.)
X(no red.)#*
Degradation
X(no red.)
#*
83 / 320

Disable RF Power
[3,246] CONFIGFAIL
(TRE)
Lock Function
TRE
Unlock Function
TRE
TRE
operational?
yes
Alarm
solved
no
Onsite
Replace
TRE
TRE
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 45: CONFIG-FAIL (TRE): BTS 9100 Corrective Actions
84 / 320

[3,246] CONFIGFAIL
(TRE)
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Onsite
Switch off Battery

Backup Switch and
OR
Switch off mains

mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 46: CONFIG-FAIL (TRE): BTS 9110/9110-E Corrective Actions
85 / 320
86 / 320
5 Class 5: ENVIR Alarms

This section defines the alarms for the Class 5: ENVIR alarm class.
87 / 320
5.1 [5,1] FAN-ALARM

specific Problems
FAN-ALARM
event Type
Environmental
probable Cause
Heating Or Ventilation Or Cooling System Problem
perceived Severity
Minor (PMA)
Alarm Description
A single fan is faulty - this is a warning, not yet critical.

5 : FAN alarm for 9110-E BTS (Master).
10 : FAN alarm for 9110-E BTS (Slave 1).

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

[5,1] FANALARM
Onsite
Onsite
A9100:
Replace FANU;
FACB
A9110E:
Replace Fan
Cassete
OR
Fan
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 47: FAN-ALARM: Corrective Actions
88 / 320
5.2 [5,11] POWER-SUPPLY-U

specific Problems
POWER-SUPPLY-U
event Type
Equipment
probable Cause
PowerProblem
perceived Severity
Critical (VPMA), Warning (MI)
Alarm Description
At least two power supply modules have failed. Some TRE are switched
OFF autonomously by the BTS.
BTS 9100: At least one PM08/PM11 module is operational.
If PM12/PM18 used: The BTS uses the backup batteries and the available
PM12/PM18 modules.
During a defined delay, the configuration is kept, the Telecom functions are not affected.
After the end of the previous delay, a minimal configuration is selected with the TRE supporting the
BCCH. (#).
If the battery is empty, the cells are lost. (X).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
#X
Degradation
#X
89 / 320

[5,11] POWERSUPPLYU
Onsite
Check Power
Supplies are
switched on
Onsite
Check
control unit, power
module and EACB
no
Alarm
solved
Alarm persists?
yes
Onsite
9100 BTS: Replace
PM08, which LED is
off or red *
Onsite
Onsite
OR
9100 BTS: Replace

PM11, which LED is
off or red *
OR
9100 BTS: Replace

PM12, which LED is
off or red *
Power supply
operational?
no
Contact
System Support
yes
Onsite
OR
9100 BTS: Replace

PM18, which LED is
off or red *
Alarm
solved
* If RIT location is A,0,0,

the RIT is located in 9100 BTS COMI/CODI
outdoor side compartment
Figure 48: POWER-SUPPLY-U: Corrective Actions
90 / 320
5.3 [5,12] POWER-SUPPLY-NU

specific Problems
POWER-SUPPLY-NU
event Type
Equipment
probable Cause
PowerProblem
perceived Severity
Major (PMA)
Alarm Description
A power supply module has failed, but the BTS is still supplied by other
power supply modules in parallel.
BTS 9100: At least one PM08/PM11/PM12/PM18 module is operational
and no TRE is switched OFF.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
91 / 320

[5,12] POWERSUPPLYNU
Onsite
Check Power
Supplies are
switched on
Onsite
Check
control unit, power
module and EACB
no
Alarm
solved
Alarm persists?
yes
Onsite
9100 BTS: Replace
PM08, which LED is
off or red *
Onsite
Onsite
OR
9100 BTS: Replace

PM11, which LED is
off or red *
OR
9100 BTS: Replace

PM12, which LED is
off or red *
Power supply
operational?
no
Contact
System Support
yes
Onsite
OR
9100 BTS: Replace

PM18, which LED is
off or red *
Alarm
solved

the RIT is located in 9100 BTS COMI/CODI
Figure 49: POWER-SUPPLY-NU: Corrective Actions
92 / 320
5.4 [5,13] CONTROL-UNIT-AL

specific Problems
CONTROL-UNIT-AL
event Type
Equipment
probable Cause
PowerProblem
perceived Severity
Nbr 2: Critical (VPMA), Warning (MI)

Nbr 1: Major (PMA), Warning (MI)
Alarm Description
There is a failure of the control unit that supervises the power modules.
Alarm Number
1 : The battery capacity is faulty.

2 : The battery charging voltage is faulty.
The battery is empty and is not used: the Telecom functions are not affected.
The battery is empty and is used: the cells are lost. (X)
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
93 / 320

[5,13] CONTROLUNITAL
Onsite
Check Power
Supplies are
switched on
no
Battery
OK?
Onsite
yes
A9100
BCU1/BCU2, PM12:
Replace
BU41/BU100
Onsite
Onsite
OR
A9100:
Replace BATS
OR
Control Unit
operational?
yes
A9100:
Replace BU101
Onsite
Check cables/connectors
to control unit and EACB
Alarm
solved
no
Contact
System Support
Onsite
A9100: Replace
BCU1, which LED is
off or red *
Onsite
Onsite
OR
A9100: Replace
BCU2, which LED is
off or red *
Power supply
operational?
no
Contact
System Support
OR
yes
A9100: Replace
PM12, which LED is
off or red *
Alarm
solved

the RIT is located in A9100 COMI/CODI
Figure 50: CONTROL-UNIT-AL: Corrective Actions
94 / 320
95 / 320
5.5 [5,20] MAINS-AL

specific Problems
MAINS-AL
event Type
Equipment
probable Cause
PowerProblem
perceived Severity
Critical (VPMA), Warning (MI)
Alarm Description
There is a problem on the BTS mains power supply. No BTS

PM08/PM11/PM12/PM18 power supply is operational. The BTS runs on
the backup batteries.
During a defined delay, the configuration is kept, the Telecom functions are not affected.
After the end of the previous delay, a minimal configuration is selected with the TRE supporting the
BCCH. (#)
If the battery is empty, the cells are lost. (X).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
#X
Degradation
#X
96 / 320

[5,20] MAINSAL
Onsite
Check
control unit and BTS
Onsite
Check external BTS mains
supply and fuses. Setup
supply and replace fuses if
required
no
Alarm
solved
Alarm persists?
yes
Onsite
A9100: Replace
PM08, which LED is
off or red *
Onsite
Onsite
OR
A9100: Replace
PM11, which LED is
off or red *
OR
A9100: Replace
PM12, which LED is
off or red *
Power supply
operational?
no
Contact
System Support
yes
Onsite
OR
A9100: Replace
PM18, which LED is
off or red *
Alarm
solved

Figure 51: MAINS-AL: Corrective Actions
97 / 320
5.6 [5,23] POWER-SHUTDOWN

specific Problems
POWER-SHUTDOWN
event Type
Equipment
probable Cause
PowerProblem
perceived Severity
Major (PMA)
Alarm Description
The shutdown is due to a mains power failure.
Alarm Number
1 : BTS 9100- A TRE is switched off due to a mains alarm (see the
description of the "MAINS_AL" or "POWER SUPPLY_U" alarm).
2 : BTS 9110/9110-E - This alarm is reported for a TRE in slave box when
this slave box is started after the master box during 9110-S start up (timing
differences due to low ambient temperature).
is lost. (X).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
X(no red.)
X(no red.)
X(no red.)#*
Degradation
X(no red.)
#*
98 / 320

[5,23]
POWERSHUTDOWN
Onsite
Check
control unit and BTS
Onsite
Check external BTS mains
supply and fuses. Setup
supply and replace fuses if
required
no
Alarm persists?
Alarm
solved
yes
Onsite
A9100: Replace
PM08, which LED is
off or red *
Onsite
Onsite
OR
A9100: Replace
PM11, which LED is
off or red *
Power supply
operational?
no
Contact
System Support
A9100: Replace
OR PM12, which LED is
off or red *
yes
Alarm
solved

Figure 52: POWER-SHUTDOWN: Alarm Number 1 Corrective Actions
99 / 320

[5,23]
POWERSHUTDOWN
Onsite
Wait for heat up

of the BTS
Onsite
Disable TRE(s)
Onsite
Init TRE(s)
no
Alarm persists?
Alarm
solved
yes
Contact
System Support
Figure 53: POWER-SHUTDOWN: Alarm Number 2 Corrective Actions
100 / 320
5.7 [5,24] SUBRACK-POWER

specific Problems
SUBRACK-POWER
event Type
Equipment
probable Cause
PowerProblem
perceived Severity
Major (PMA)
Alarm Description
This alarm is reported if more than one module of the subrack has power
supply problems.
Alarm Number
1 : Subrack number 1.
...
n : Subrack number n.
There is impact through the HW_FAILURE of class 10 alarms.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
101 / 320

[5,24] SUBRACKPOWER
Onsite
Check
subrack
Onsite
Check AC and DC Circuit

Breakers. Switch breacker(s)
on if required.
no
Alarm
solved
yes
Alarm
solved
Alarm persists?
yes
Check for faulty RITs in
class 10 HW_Failure alarms
on this BTS. Solve that
alarm(s) before repowering
the subrack.
Power supply
operational?
no
Contact
System Support
Figure 54: SUBRACK-POWER: Corrective Actions
102 / 320
5.8 [5,31] TEMPERATURE-WARNING

5.8.1 [5,31] TEMPERATURE-WARNING (BTS)
specific Problems
TEMPERATURE-WARNING
event Type
Environmental
probable Cause
Temperature Unacceptable
perceived Severity
Alarm Description
This is a temperature warning.

The temperature control of the hottest TRE in the BTS has reached the
low threshold value.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
103 / 320

Thermometer
Replacement and cleaning tools, see appropriate replacement procedure.
[5,31]
TEMPERATUREWARNING
(BTS)
yes
Solve that
alarm(s) first
Fan alarm events?
no
Onsite
Check the ambient

temperature.
Onsite
Is
ambient
temperature out of
permitted
limits?
yes
The ambient
temperature must be
reduced.
BTS
Temperature
OK?
yes
Alarm
solved
no
no
Onsite
Contact
System Support
Check and clean

heat exchanger air
intake
BTS
Temperature
OK?
yes
Alarm
solved
no
Contact
System Support
Figure 55: TEMPERATURE-WARNING (BTS): Corrective Actions
104 / 320
5.8.2 [5,31] TEMPERATURE-WARNING (TRE)

specific Problems
TEMPERATURE-WARNING
event Type
Environmental
probable Cause
perceived Severity
Alarm Description
This is a temperature warning.

A MTRE inside the BTS has reached a temperature which is close to the
shut off temperature.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
105 / 320

Thermometer
[5,31] TEMPERATUREWARNING
(TRE)
Fan alarm
events?
yes
Solve that
alarm(s) first
no
Onsite
Check the ambient
temperature.
Onsite
Is
ambient
temperature out of
permitted
limits?
yes
The ambient
temperature must be
reduced.
TRE
Temperature
OK?
yes
Alarm
solved
yes
Alarm
solved
no
no
Contact
System Support
Onsite
Optional
Fan Module
available?
yes
Check and clean

optional Fan
Module
TRE
Temperature
OK?
no
no
Onsite
Contact
System Support
Add optional Fan

Module
TRE
Temperature
OK?
yes
Alarm
solved
no
Contact
System Support
Figure 56: TEMPERATURE-WARNING (TRE): Corrective Actions
106 / 320
5.9 [5,32] FATAL TEMPERATURE

specific Problems
FATAL TEMPERATURE
event Type
Environmental
probable Cause
perceived Severity
Major (PMA)
Alarm Description
This is a fatal temperature alarm.

Internal TRE temperature is higher than the predefined high threshold.
The power amplifier of the TRE automatically switches itself off, in order
to avoid any HW damage.
is lost. (X).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
X(no red.)
X(no red.)
X(no red.)#*
Degradation
X(no red.)
#*
107 / 320

Thermometer
[5,32] FATAL
TEMPERATURE
yes
Solve that
alarm(s) first
Fan alarm events?
no
Onsite
Check the ambient

temperature.
Onsite
Is
ambient
temperature out of
permitted
limits?
yes
The ambient
temperature must be
reduced.
TRE
Temperature
OK?
yes
Alarm
solved
no
no
Onsite
Contact
System Support
Check and clean

heat exchanger air
intake
TRE
Temperature
OK?
yes
Alarm
solved
no
Contact
System Support
Figure 57: FATAL TEMPERATURE: Corrective Actions
108 / 320

5.10.1 [5,237] HW-DEGRADED (BTS)
specific Problems
HW-DEGRADED
event Type
Equipment
probable Cause
perceived Severity
Alarm Description
A problem has been detected on the XIOB/OUTC input ports.
Alarm Number
6 : DC/DC converter 1 failure.

7 : DC/DC converter 2 failure.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
109 / 320

[5,237] HWDEGRADED
(BTS)
Lock Function
BTS
Unlock Function
BTS
DC/DC
converter
operational?
yes
Alarm
solved
no
Onsite
Replace
SUMP, SUMA
DC/DC
converter
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 58: HW-DEGRADED (BTS): Corrective Actions
110 / 320
5.10.2 [5,237] HW-DEGRADED (EACB)

specific Problems
HW-DEGRADED
event Type
Equipment
probable Cause
perceived Severity
Major (PMA)
Alarm Description
A problem has been detected on the input ports
Alarm Number
10 :BTS 9100: A problem has been detected on the XIOB/OUTC input

ports.
BTS 9110/9110-E : A problem has been detected on the input ports during
tests with the MBTS-BCB unit.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
111 / 320
5.10.2.1 Alarm Number 10 BTS 9100 Corrective Actions

[5,237] HWDEGRADED
(EACB)
Lock Function
EACB
Unlock Function
EACB
EACB
operational?
yes
Alarm
solved
no
Onsite
Onsite
A9100:
Replace
XIOB
For RIT OUTC

replacement contact
system support
OR
EACB
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 59: HW-DEGRADED (EACB): BTS 9100 Corrective Actions
112 / 320
5.10.2.2 Alarm Number 10 BTS 9110/9110-E Corrective Actions

[5,237] HWDEGRADED
(EACB)
Reset Function
BTS
MicroBTS
operational?
yes
Alarm
solved
no
Onsite
Switch
MicroBTS
off
Onsite
Switch
MicroBTS
on
MicroBTS
operational?
yes
Alarm
solved
yes
Alarm
solved
no
Replace
MicroBTS
MicroBTS
operational?
no
Contact
System Support
Figure 60: HW-DEGRADED (EACB): BTS 9110/9110-E Corrective Actions
113 / 320
5.10.3 [5,237] HW-DEGRADED (RA)

specific Problems
HW-DEGRADED
event Type
Equipment
probable Cause
perceived Severity
Major (PMA)
Alarm Description
A problem has been detected on the input ports
Alarm Number
11 : TMA current supervision failure

12 : TMA1 current too low
13 : TMA1 current too high
14 : TMA1 short circuit alarm
15 : TMA2 current too low
16 : TMA2 current too high
17 : TMA2 short circuit alarm

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
114 / 320
5.10.3.1 Alarm Number 11..17 Corrective Actions

[5,237] HWDEGRADED
(RA)
Lock Function RA
Unlock Function
RA
RA
operational?
yes
Alarm
solved
no
Onsite
Replace TMA
yes
RA operational?
Alarm
solved
no
Contact
System Support
Figure 61: HW-DEGRADED (RA): Corrective Actions
115 / 320
5.10.4 [5,237] HW-DEGRADED (CCF)

specific Problems
HW-DEGRADED
event Type
Equipment
probable Cause
perceived Severity
Alarm Description
An fan control for front or back row is faulty.
Alarm Number
1 :The complete front row of the fans is faulty. This is detected when either
all front fans generate an alarm or the DC converter of the fan control board
is faulty.
2 :Same as 1, but for the back row instead of the front row.
3 :At least one fan on a left fan unit is faulty.
4 :At least one fan on a middle fan unit is faulty.
5 :At least one fan on a right fan unit is faulty.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

[5,237] HWDEGRADED
(CCF)
Onsite
Replace FACB
Onsite
OR
Replace FANU
Fan
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 62: HW-DEGRADED (CCF): Corrective Actions
116 / 320
5.11 [5,239] HW-FAILURE

5.11.1 [5,239] HW-FAILURE (EACB)
specific Problems
HW-FAILURE
event Type
Equipment
probable Cause
perceived Severity
Major (PMA)
Alarm Description
A hardware failure has been detected.
Alarm Number
2 : This alarm have an unknown cause and indicates that more detailed
alarms were reported before and are available in the OMC.
3 : The BCB detects a malfunction or the extraction of the module.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
117 / 320

[5,239] HWFAILURE
(EACB)
Check for previously

reported alarms o this
function (SBL EACB).
Solve that alarm(s) first.
EACB
operational?
yes
Alarm
solved
no
Onsite
Replace faulty RIT, see

previously reported and
correced alarm
EACB
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 63: HW-FAILURE (EACB): Alarm Number 2 Corrective Actions
118 / 320

[5,239] HWFAILURE
(EACB)
Lock/Unlock EACB
EACB
operational?
yes
no
Reset BTS
EACB
operational?
no
yes
Alarm
solved
Onsite
Insert appropriate
module
EACB
operational?
yes
no
Contact
System Support
Figure 64: HW-FAILURE (EACB): Alarm Number 3 Corrective Actions
119 / 320
5.11.2 [5,239] HW-FAILURE (CCF)

specific Problems
HW-FAILURE
event Type
Equipment
probable Cause
perceived Severity
Major (PMA)
Alarm Description
There is a failure of front and back FAN (e.g. due to power supply failure) or
the alarm has an unknown cause. This alarm indicates that more detailed
alarms were reported before and are available in the OMC.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
120 / 320

[5,239] HWFAILURE
(CCF)
SUBRACK
POWER alarm(s)
events?
yes
Solve that
alarm(s) first.
FAN
operational?
Alarm
solved
no
no
Contact
System Support
Check for previously

reported alarms on this
function (SBL CCF). Solve
that alarm(s).
FAN
operational?
yes
yes
Alarm
solved
yes
Alarm
solved
no
Onsite
Replace FACB
FAN
operational?
no
Contact
System Support
Figure 65: HW-FAILURE (CCF): Corrective Actions
121 / 320
122 / 320
6 Class 8: Global BTS Alarms

This section defines the alarms for the Class 8: Global BTS alarm class.
123 / 320
6.1 [8,3] RESYNCH

specific Problems
RESYNCH
event Type
Processing Error
probable Cause
perceived Severity
Warning (MI)
Alarm Description
Discrepancies are detected between the BSC and OMU database and both
databases have been updated. The OMC-R triggers an update of its own
Alarms in Force and SBL state list.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

None required, the BTS is in service.
124 / 320
6.2 [8,4] IGNORE EQUIPMENT OVER 12 TRE

specific Problems
IGNORE EQUIPMENT OVER 12 TRE
event Type
Processing Error
probable Cause
perceived Severity
Warning (MI)
Alarm Description
Discrepancies are detected between the BSC and OMU database and
both databases have been updated.
The OMC-R triggers an update of its own Alarms in Force and SBL state
list.
Alarm Number
1 : The operator has installed and configured too many TREs, although
there are G3 TREs in the BTS. Equipment over 12 TREs is ignored.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

[8,1] IGNORE EQUIPMENT
OVER 12 TRE
Replace all G3
TREs by G4 TREs
or TWIN TRXs
yes
Alam cleared?
Alarm
solved
no
Contact
System Support
Figure 66: IGNORE EQUIPMENT OVER 12 TRE: Corrective Actions
125 / 320
6.3 [8,5] TOO MANY PLUGGED MODULES

specific Problems
TOO MANY PLUGGED MODULES
event Type
Equipment
probable Cause
perceived Severity
Warning (MI)
Alarm Description
The installed HW configuration exceeds the power dissipation limits.
Alarm Number
1 : Too many TREs are plugged in the rack type.
There is no disturbance of the telecom applications.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

[8,5] TOO MANY PLUGGED
MODULES
Reduce the
installed equipment
Alam cleared?
yes
Alarm
solved
no
Contact
System Support
Figure 67: TOO MANY PLUGGED MODULES: Corrective Actions
126 / 320
6.4 [8,8] HW-RESYNCH

specific Problems
HW-RESYNCH
event Type
Processing Error
probable Cause
perceived Severity
Warning (MI)
Alarm Description
The BTS detects an addition or reduction in SBLs or hardware modification

(different RIT names). Consequently a hardware re-synchronization alarm
is sent. This causes the OMC-R to trigger a hardware, state and alarm
audit. The audit aligns the OMC -R database with the new hardware.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

None required, the BTS is in service.
127 / 320
6.5 [8,30] BCB-LINK

specific Problems
BCB-LINK
event Type
Equipment
probable Cause
perceived Severity
Alarm Description
There is no communication on IOM link.
Alarm Number
1 : The BCB link is unable to detect the presence of the modules.

2 : The BCB Power supply is faulty.
The is no communication on the BCB.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
128 / 320

Disable RF Power
[8,30] BCBLINK
Lock Function
BTS
Unlock Function
BTS
BTS
operational?
no
yes
Alarm
solved
Onsite
Check BCB bus for

shortcuts and
interruptions
Onsite
Replace
SUMP/SUMA
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 68: BCB-LINK: BTS 9100 Corrective Actions
129 / 320

Disable RF Power
[8,30] BCBLINK
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
Onsite
OR
Onsite
Switch off Battery

Backup Switch and
BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 69: BCB-LINK: BTS 9110/9110-E Corrective Actions
130 / 320
6.6 [8,31] IOM-LINK

specific Problems
IOM-LINK
event Type
Equipment
probable Cause
perceived Severity
Major (PMA)
Alarm Description
There is no communication on IOM link.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
131 / 320

Disable RF Power
[8,31] IOMLINK
Lock Function
BTS
Unlock Function
BTS
BTS
operational?
no
yes
Alarm
solved
Onsite
Check BSII bus for

shortcuts and
interruptions
Onsite
Replace
SUMP/SUMA
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 70: IOM-LINK: BTS 9100 Corrective Actions
132 / 320

Disable RF Power
[8,31] IOMLINK
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Onsite
Switch off Battery

Backup Switch and
BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 71: IOM-LINK: BTS 9110/9110-E Corrective Actions
133 / 320
6.7 [8,32] MODULE-INSERTED

6.7.1 [8,32] MODULE-INSERTED (BTS)
specific Problems
MODULE-INSERTED
event Type
Equipment
probable Cause
Replaceable Unit Problem
perceived Severity
Warning (MI)
Alarm Description
The TRE is not connected to any ANX/ANC via RF cable.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

Disable RF Power
134 / 320
[8,32] MODULEINSERTED
(BTS)
Lock Function
BTS
Unlock Function
BTS
yes
BTS
operational?
Alarm
solved
no
Onsite
If the module has been

extracted previously and the
same module inserted
(without operator action), the
connection of the module
could be faulty
Check BTS status
Onsite
Check RF cables and
connectors to TRE and
ANX/ANY/ANC visually
and electrcally. Replace
cable, if required.
yes
BTS
operational?
Alarm
solved
no
Onsite
Replace
ANX,ANY,ANC
Onsite
OR
Replace TRE
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 72: MODULE-INSERTED: BTS 9100 Corrective Actions

Disable RF Power
135 / 320
[8,32]
MODULEINSERTED
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
Onsite
OR
Onsite
Switch off Battery

Backup Switch and
BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
9110 BTS
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 73: MODULE-INSERTED: BTS 9110/9110-E Corrective Actions
6.7.2 [8,32] MODULE-INSERTED (RA)

specific Problems
MODULE-INSERTED
event Type
Equipment
probable Cause
136 / 320
perceived Severity
Warning (MI)
Alarm Description
The inserted TRE is connected to a dedicated ANx via RF cable.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

Disable RF Power
137 / 320
[8,32] MODULEINSERTED
(RA)
Lock Function
BTS
Unlock Function
BTS
yes
BTS
operational?
Alarm
solved
no
Onsite
If the module has been

extracted previously and the
same module inserted
(without operator action), the
connection of the module
could be faulty
Check BTS status
Onsite
Check RF cables in case
the of sector mapping is
not as expected, and
connectors to TRE,
ANX/ANY/ANC visually
and electrcally. Replace
cable, if required.
yes
BTS
operational?
Alarm
solved
no
Onsite
Replace
ANX,ANY,ANC
Onsite
OR
Replace TRE
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 74: MODULE-INSERTED: BTS 9100 Corrective Actions

Disable RF Power
138 / 320
[8,32]
MODULEINSERTED
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
Onsite
OR
Onsite
Switch off Battery

Backup Switch and
BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
9110 BTS
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 75: MODULE-INSERTED: BTS 9110/9110-E Corrective Actions
139 / 320
140 / 320
6.8 [8,247] RESET

6.8.1 [8,247] RESET (BTS)
specific Problems
RESET
event Type
Processing Error
probable Cause
Software Error
perceived Severity
Warning (MI)
Alarm Description
The (power up) reset of the BTS has been performed successfully.
Alarm Number
1 : BTS Power On.

2 : SW discrepancy.
3 : Operator command.
There is no disturbance of the telecom applications, because the BTS was powered down before.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

None required, the BTS is now in service.
141 / 320
6.9 [8,248] RESTART

specific Problems
RESTART
event Type
Equipment
probable Cause
Software Error
perceived Severity
Warning (MI)
Alarm Description
The BTS restarts successfully.
After the previous call interrupt, the BTS is now in service.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

None required.
142 / 320
7 Class 9: BTS-EXTERNAL Alarms

This section defines the alarms for the Class 9: BTS-EXTERNAL alarm class.
143 / 320
7.1 [9,1...56] EXT-ALARM

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
External Alarms are not linked to telecom part of the BTS, they are forseen
to announce events linked to the environment of the BTS.
BTS 9100/9110/9110-E : External alarm (e.g., door open, fire, water)
detected from input port [1 ... 24].
External alarms [25 ... 56] can be raised only by the BTS 9110-E, and are
applicable only in this case.
For Outdoor BTS, some of the 24 external alarms are allocated to the
cabinet, they are already wired and reflect behaviour of other elements in
the BTS: AC main, Air Conditioning unit, door...
For 9100 Indoor BTS, the 24 external alarms are free (customer).
External alarms are seen only at the BTS and BSC terminals. At the
OMC-R, they are translated into customer-defined ASCII text.
To simplify the external alarms declaration, default values are provided with
an alarm translation table.
Telecom functions are not directly affected, if the detected problem is not disturbing the BTS function.
(#) VSWR and LNA alarms (if equipped), indicates a problem on the antenna output, and degradation
may occur.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
X#
X#
144 / 320

[9,1...50] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Trigger customer
specific action
according to reported
alarm (e.g. call fire
brogade)
Check cabling to
sensor, replace
cabling if required.
Onsite
Check sensor
function, replace
sensor if required.
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
Figure 76: EXT-ALARM [9,1...56] : Corrective Actions
145 / 320
7.2 [9,1] EXT-ALARM (Default)

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Critical (VPMA)
Alarm Description
BTS 9100: There is a power supply rectifier failure.
Telecom functions are not directly affected, if the detected problem is not disturbing the BTS function.
Telecom functions are not directly affected, as long as the BTS is battery powered.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
146 / 320

[9,1] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Trigger customer
specific action
according to power
supply rectifier alarm
Check cabling to
sensor, replace
Onsite
Check sensor
function, replace
sensor if required.
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
Figure 77: [9,1] EXT-ALARM: Default Corrective Actions
147 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Critical (VPMA)
Alarm Description
BTS 9100: There is a AC mains power failure.
9110/9110-E: There is a AC mains power failure detected by SSC.
Telecom functions are not directly affected, as long as the BTS is battery powered. Immediate intervention
is necessary, if not the BTS will go down.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
148 / 320

[9,2] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Onsite
Check cabling to
sensor, replace
Check AC power
supply fuses,
breakers, cabl%s,
connectors
Onsite
Onsite
Check sensor
function, replace
sensor if required.
Ensure BTS AC
power supply
External
alarm
persists?
yes
Contact
System Support
no
Alarm
solved
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
149 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
BTS 9100: This is a door/window alarm.
BTS 9110/9110-E : This is a combined alarm for SSC, indicates
problem/malfunction on one of the following SSC aspects:
Door contact
Power supplies
Battery charger
Inner fan alarm
Outer fan alarm
Temperature alarm
Battery back-up "OFF" alarm.
Telecom functions are not affected .

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
150 / 320

[9,3] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Trigger customer
specific action
brogade)
Check cabling to
sensor, replace
Onsite
Check sensor
function, replace
sensor if required.
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
151 / 320

[9,1] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Onsite
Check cabling to
sensor, replace
Check AC power
supply fuses,
breakers, cabl%s,
connectors
Onsite
Onsite
Check sensor
function, replace
sensor if required.
Ensure BTS AC
power supply
Onsite
External
alarm
persists?
Replace SSCPS
no
Alarm
solved
yes
Contact
System Support
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
Figure 80: [9,3] EXT-ALARM: BTS 9110/9110-E Default Corrective Actions
152 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
BTS 9100: This is a door/window alarm override by the allowance key.
BTS 9110/9110-E: This is a door alarm for the micro-BTS master, COBOX
cover open.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
153 / 320

[9,4] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Trigger customer
specific action
according to an open
door or window alarm
when allowance key is
used onsite.
Check cabling to
sensor, replace
Onsite
Check sensor
function, replace
sensor if required.
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
154 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Critical (VPMA)
Alarm Description
BTS 9100: Fire alarm by detection of smoke detector inside the cabinet.
BTS 9110/9110-E: This is a PMS alarm for the micro-BTS master,
equipment not in vertical position.
Telecom functions are not directly affected.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
155 / 320

[9,5] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Trigger customer
specific action
brogade)
Check cabling to
sensor, replace
Onsite
Check sensor
function, replace
sensor if required.
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
156 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Major (PMA)
Alarm Description
BTS 9100: Water break-in by detection of water detection float switch.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
157 / 320

[9,6] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Trigger customer
specific action
according to a water
breakin alarm.
Check cabling to
sensor, replace
Onsite
Check sensor
function, replace
sensor if required.
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
158 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Major (PMA)
Alarm Description
BTS 9100: There is a heating/ventilation/cooling system problem. At least
one fan in the heat exchanger unit is faulty.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
159 / 320

[9,7] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Check cabling to
sensor, replace
Onsite
A9100:
Replace HEAT2
Onsite
Check sensor
function, replace
sensor if required.
External
alarm
persists?
no
Alarm
solved
yes
no
External
alarm
persists?
yes
Contact
System Support
160 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
BTS 9100: The temperature in the equipment rack reached 35 0 C.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
161 / 320

[9,8] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Trigger customer
specific action
according to a hot
equipment room alarm
(e.g. check air
condition unit)
Check cabling to
sensor, replace
Onsite
Check sensor
function, replace
sensor if required.
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
162 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
BTS 9100: The temperature in the equipment room reached 40 0 C.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
163 / 320

[9,9] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Trigger customer
specific action
according to a hot
equipment room alarm
(e.g. check air
condition unit)
Check cabling to
sensor, replace
Onsite
Check sensor
function, replace
sensor if required.
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
164 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
BTS 9100: The antenna mast warning light is faulty.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
165 / 320

[9,10] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Onsite
Check cabling to
sensor, replace
Replace antenna
mast warning light
Onsite
External
alarm
persists?
no
Alarm
solved
Check sensor
function, replace
sensor if required.
yes
Contact
System Support
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
166 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Major (PMA)
Alarm Description
9100 BTS Indoor: The external battery (if equipped) is deep discharged
while supplying the BTS. The BTS will be switched off after 30 - 60 s.
Telecom functions are not directly affected, as long as the BTS is battery powered, but the BTS will be
switched off after 30 - 60 s.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
167 / 320

[9,11] EXTALARM
Alarm was
sent without
cause?
yes
Onsite
Onsite
Check sensor
connection to BTS.
Check cabling to
sensor, replace
no
Onsite
Power
supply alarm
events?
yes
Check sensor function,

replace sensor if
required.
Solve power supply

alarm first
no
Onsite
no
External
alarm
persists?
Ensure BTS AC power

supply
Onsite
yes
Contact
System Support
Check battery
Onsite
A9100:
Replace BU41
External
alarm
persists?
Alarm
solved
OR
A9100:
Replace BU100
Onsite
Onsite
Onsite
OR
A9100:
Replace BATS
OR
A9100:
Replace BU101
no
Alarm
solved
yes
Contact
System Support
168 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
BTS 9110/9110-E: This is a door alarm for the micro-BTS slave1, COBOX
cover open.
Telecom functions are not directly affected, as long as the BTS is battery powered.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
169 / 320

[9,12] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Onsite
Check cabling to
sensor, replace
Check FAN fuses in

COBO, replace fuses
if required.
Onsite
Onsite
Replace FAn
Cassette.
External
alarm
persists?
Check sensor
function, replace
sensor if required.
no
Alarm
solved
External
alarm
persists?
no
Alarm
solved
yes
Onsite
yes
Contact
System Support
Replace Top of
Cover with FAN.
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
170 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
BTS 9110/9110-E: This is a PMS alarm for the micro-BTS slave1,
equipment not in vertical position.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
171 / 320

[9,13] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Onsite
Check cabling to
sensor, replace
Replace antenna
mast warning light
Onsite
External
alarm
persists?
no
Alarm
solved
Check sensor
function, replace
sensor if required.
yes
Contact
System Support
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
Figure 90: [9,13] EXT-ALARM: 9100 Default Corrective Actions
172 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
173 / 320

[9,14] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Onsite
Check cabling to
sensor, replace
Replace antenna
mast warning light
Onsite
External
alarm
persists?
no
Alarm
solved
Check sensor
function, replace
sensor if required.
yes
Contact
System Support
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
Figure 91: [9,14] EXT-ALARM: BTS 9100 Default Corrective Actions
174 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
BTS 9100: This is a door alarm.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
175 / 320

[9,15] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Trigger customer
specific action
according to
open door alarm
Check cabling to
sensor, replace
Onsite
Check sensor
function, replace
sensor if required.
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
176 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Critical (VPMA)
Alarm Description
BTS 9100: This is a power supply inverter alarm.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
177 / 320

[9,16] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Trigger customer
specific action
according to power
supply inverter alarm
Check cabling to
sensor, replace
Onsite
Check sensor
function, replace
sensor if required.
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
178 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
BTS 9100: This is a fatal REK alarm on TRX1, MAB detects a VSWR
problem.
(#) VSWR alarm indicates a problem on the antenna output, and degradation may occur.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
X#
X#
179 / 320

[9,17] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Onsite
Check cabling to
sensor, replace
Check TRX to
antenna cables
visually and
electrically
Onsite
Onsite
Check sensor
function, replace
sensor if required.
Check antenna
Onsite
External
alarm
persists?
Replace MAB of
TRX1
no
Alarm
solved
yes
Contact
System Support
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
180 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
BTS 9100: This is a fatal REK alarm on TRX2, MAB detects a VSWR
problem.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
X#
X#
181 / 320

[9,18] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Onsite
Check cabling to
sensor, replace
Check TRX to
antenna cables
visually and
electrically
Onsite
Onsite
Check sensor
function, replace
sensor if required.
Check antenna
Onsite
External
alarm
persists?
Replace MAB of
TRX2
no
Alarm
solved
yes
Contact
System Support
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
182 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
BTS 9100: This is a fatal REK alarm (if installed) on TRX3, MAB detects a
VSWR problem.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
X#
X#
183 / 320

[9,19] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Onsite
Check cabling to
sensor, replace
Check TRX to
antenna cables
visually and
electrically
Onsite
Onsite
Check sensor
function, replace
sensor if required.
Check antenna
Onsite
External
alarm
persists?
Replace MAB of
TRX3
no
Alarm
solved
yes
Contact
System Support
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
184 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
VSWR problem.
BTS 9110/9110-E: This is a door alarm for the micro-BTS slave 2, COBOX
cover open.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
X#
X#
185 / 320

[9,20] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Onsite
Check cabling to
sensor, replace
Check TRX to
antenna cables
visually and
electrically
Onsite
Onsite
Check sensor
function, replace
sensor if required.
Check antenna
Onsite
External
alarm
persists?
Replace MAB of
TRX4
no
Alarm
solved
yes
Contact
System Support
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
186 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
VSWR problem.
9110/9110-E: This is a PMS alarm for the micro-BTS slave2, equipment
not in vertical position.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
X#
X#
187 / 320

[9,21] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Onsite
Check cabling to
sensor, replace
Check TRX to
antenna cables
visually and
electrically
Onsite
Onsite
Check sensor
function, replace
sensor if required.
Check antenna
Onsite
External
alarm
persists?
Replace MAB of
TRX5
no
Alarm
solved
yes
Contact
System Support
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
188 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
VSWR problem.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
X#
X#
189 / 320

[9,22] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Onsite
Check cabling to
sensor, replace
Check TRX to
antenna cables
visually and
electrically
Onsite
Onsite
Check sensor
function, replace
sensor if required.
Check antenna
Onsite
External
alarm
persists?
Replace MAB of
TRX6
no
Alarm
solved
yes
Contact
System Support
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
190 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
BTS 9100 : This is a REK alarm (if installed) on LNA, at least one receive
path has a LNA problem.
(#) PDU/LNA alarm indicates a problem on the antenna amplifier output, and degradation may occur.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
X#
X#
191 / 320

[9,23] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Check cabling to
sensor, replace
Onsite
Onsite
Check all PDUs for

flashing TRX MAB
LEDs
Check sensor
function, replace
sensor if required.
Onsite
External
alarm
persists?
Replace the MAB

corresponding to the
lashing TRX MAB
LED
no
Alarm
solved
yes
Contact
System Support
External
alarm
persists?
no
Alarm
solved
yes
Contact
System Support
192 / 320

specific Problems
EXT-ALARM
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA)
Alarm Description
BTS 9100: There is a heating/ventilation/cooling system problem. At least
one fan in the heat exchanger unit is faulty.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
193 / 320

[9,7] EXTALARM
Onsite
Alarm was
sent without
cause?
yes
Check sensor
connection to BTS.
no
Onsite
Check cabling to
sensor, replace
Onsite
A9100:
Replace HEAT2
Onsite
Check sensor
function, replace
sensor if required.
External
alarm
persists?
no
Alarm
solved
yes
no
External
alarm
persists?
yes
Contact
System Support
Figure 101: [9,24] EXT-ALARM: 9100 Default Corrective Actions
194 / 320
7.26 [9,25] EXT-ALARM for 9110-E (Default)

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity
Minor (DMA) - in commercial use; complete Begin/End alert sequence..

Indeterminate - event, without End alert..
Warning - out of commercial use; complete Begin/End alert sequence..
Alarm Description
BTS 9110-E: Available and not used.

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
195 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Indeterminate - event, without End alert.
Alarm Description

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity
Minor (DMA) - in commercial use; complete Begin/End alert sequence.

Warning - out of commercial use; complete Begin/End alert sequence.
Alarm Description
BTS 9110-E: This is a door alarm for the micro-BTS slave 11, COBOX
cover open.
196 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
9110-E: This is a PMS alarm for the micro-BTS slave11, equipment not in
vertical position.

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
197 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
198 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
199 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
cover open.
200 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
vertical position.

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
201 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
202 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
203 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
cover open.
204 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
vertical position.

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
205 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
206 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
207 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
cover open.
208 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
vertical position.

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
209 / 320

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description

Specific Problems
EXT-ALARM
Event Type
Equipment
Probable Cause
Indeterminate
Perceived Severity

Alarm Description
210 / 320
8 Class 10: RX-TX Alarms

This section defines the BTS alarms for Class 10: RX-TX alarm class.
211 / 320
8.1 [10,1] RSL-LINK

specific Problems
RSL-LINK
event Type
Communication
probable Cause
Communications Protocol Error
perceived Severity
Warning (MI)
Alarm Description
The Lapd channel RSL between BSC and BTS TRE is faulty.
This can be due to transmission problem or to BSC TCU unavailability
(faulty or operator disabled). In this situation, the TRE performs an
auto-restart after having run a timer (BCCH_CUT_Timer).
The concerned TRE does not carry traffic as long as the Lapd RSL is not reestablished.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
212 / 320

Disable RF Power
[10,1] RSLLINK
Lock Function
BTS
Unlock Function
BTS
BTS
operational?
yes
Alarm
solved
yes
Alarm
solved
yes
Alarm
solved
no
Onsite
Check BTS status
Onsite
Check RSL cables and
connectors to TRE and
SUM visually and
electrcally. Replace
cable, if required.
BTS
operational?
no
Onsite
Replace
SUMP/SUMA
BTS
operational?
no
Contact
System Support
Figure 102: RSL-LINK: BTS 9100 Corrective Actions
213 / 320

Disable RF Power
[10,1] RSLLINK
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Onsite
Switch off Battery

Backup Switch and
OR
Switch off mains

mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 103: RSL-LINK: 9110/9110-E Micro BTS Corrective Actions
214 / 320
8.2 [10,3] RX-CABLE

8.2.1 [10,3] RX-CABLE (TRE)
specific Problems
RX-CABLE
event Type
Equipment
probable Cause
perceived Severity
Major (PMA)
Alarm Description
An error has been detected in the cabling between a TRE and an ANX.
Alarm Number
1 : The DC signal on RX0 has been lost.

2 : The DC signal on RX1 has been lost.
5 : The DC signal on RX0 & RX1 has been lost, or has been lost on RX0
only, when antenna diversity is installed.
The cell is lost.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
215 / 320

Disable RF Power
[10,3] RXCABLE
(TRE)
Lock Function
TRE
Unlock Function
TRE
yes
ANX/ANY/ANC
alarm events?
Solve that alarm

first
no
yes
TRE
operational?
Alarm
solved
no
Onsite
Onsite
Check RX cables to TRE

and ANX/ANY/ANC
visually and electrically
Check BTS status
Onsite
Replace TRE
TRE
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 104: RX-CABLE (TRE):Corrective Actions
216 / 320
8.2.2 [10,3] RX-CABLE (RA)

specific Problems
RX-CABLE
event Type
Equipment
probable Cause
perceived Severity
Nbr 3: Major (PMA)

Nbr 4: Minor (DMA)
Alarm Description
An error has been detected in the cabling between a TRE and an ANX/ANC.
Alarm Number
3 : Several TREs connected to the same ANX/ANC have detected a

cabling error (cabling between TRE and ANX/ANC) on both RX paths, or
on RX0 path only, when antenna diversity is installed.
4 : Several TREs connected to the same ANX/ANC have detected a
cabling error (cabling between TRE and ANX/ANC) on one RX path only,
when antenna diversity is installed.
The cell is lost.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
217 / 320

Disable RF Power
[10,3] RXCABLE
(RA)
Lock Function
RA
Unlock Function
RA
yes
ANX/ANY/ANC
alarm events?
Solve that alarm

first
no
yes
RA
operational?
Alarm
solved
no
Onsite
Check BTS status
Onsite
Check RX cables to TRE
and ANX/ANY/ANC
Onsite
Replace
ANX/ANY/ANC
RA
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 105: RX-CABLE (RA): Corrective Actions
218 / 320
8.3 [10,10] TRE-VSWR

specific Problems
TRE-VSWR
event Type
Equipment
probable Cause
Transmitter Failure
perceived Severity
Major (PMA)
Alarm Description
A fault has been detected by the VSWR supervision on the TRE output
(fault on a TX cable connected to ANX/ANY) during initialization or
operational states. The power amplifier of the TRE automatically switches
itself off, in order to avoid any HW damage.
is lost. (X).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
X#*
Degradation
#*
219 / 320

Disable RF Power
[10,10] TREVSWR
Lock Function
TRE
Unlock Function
TRE
yes
ANX/ANY/ANC
alarm events?
Solve that alarm

first
no
yes
TRE
operational?
Alarm
solved
no
Onsite
Onsite
Check TX cables to TRE

and ANX/ANY/ANC
Check BTS status
Onsite
Replace TRE
TRE
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 106: TRE-VSWR: BTS 9100 Corrective Actions
220 / 320

Disable RF Power
[10,10] TREVSWR
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Check cables to
transmitter antenna
visually and
electrically.
Onsite
Check for antenna problems
(e.g. damage, position,
reflection). Solve antenna
problem.
Onsite
Replace VSWR
detector
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 107: TRE-VSWR: BTS 9110/9110-E Corrective Actions
221 / 320
8.4 [10,11] ANTENNA-VSWR-WARNING

Disable RF Power
Required tools and materials

Antenna Test Tools
Antenna Dummy Load
specific Problems
ANTENNA-VSWR-WARNING
event Type
Equipment
probable Cause
Transmitter Failure
perceived Severity
Alarm Description
A fault has been detected concerning VSWR antenna supervision.
Alarm Number
1 (only for 9100 BTS) : The LOW (first) threshold of antenna 1 VSWR
has been exceeded.
2 (only for 9100 BTS) : The LOW (first) threshold of antenna 2 VSWR
has been exceeded.
3 (only for 9100 BTS) : The LOW (first) thresholds on both antenna 1
and 2 have been exceeded.
4 (only for 9110-E BTS) : VSWR 1 alarm for Master.
5 (only for 9110-E BTS) : VSWR 2 alarm for Master.
6 (only for 9110-E BTS) : VSWR 1 alarm for Slave 1.
222 / 320
Impact
BSS
Cell(s)
Signaling
Calls
Transmission quality is degraded

Loss
Degradation
223 / 320
8.4.1 Corrective Actions for 9100 BTS

[10,11]
ANTENNAVSWRWARNING
Lock Function
RA
Unlock Function
RA
yes
TRE
alarm events?
Solve that alarm

first
no
yes
RA
operational?
Alarm
solved
no
Onsite
Check VSWR Thresholds
Onsite
Check cables to
transmitter antenna
visually and electrically.
Onsite
Check BTS status
Onsite
If not all possible TREs are
equipped, check for missing
dummy load on ANY.
Onsite
Check for antenna
problems (connectors,
damage, position,
reflection)
RA
operational?
yes
Alarm
solved
no
Onsite
Replace ANX, ANY,
ANC, ANB
RA
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 108: ANTENNA-VSWR-WARNING: Corrective Actions for 9100 BTS
224 / 320
8.4.2 Corrective Actions for 9110-E BTS

[10,11]
ANTENNAVSWRWARNING
Lock Function
RA
Unlock Function
RA
TRE
alarm events?
yes
Solve that alarm

first
no
RA
operational?
yes
Alarm
solved
no
Onsite
Check BTS status
Onsite
Onsite
Check cables to
transmitter antenna
visually and electrically.
Onsite
Check for antenna
problems (connectors,
damage, position,
reflection)
no
Onsite
Replace 9110 Micro
BTS/9110E Micro
BTS
BTS
operational?
no
yes
RA
operational?
yes
Alarm
solved
Alarm
solved
no
Contact
System Support
Figure 109: ANTENNA-VSWR-WARNING: Corrective Actions for 9110-E BTS
225 / 320
8.5 [10,12] ANTENNA-VSWR-URGENT

specific Problems
ANTENNA-VSWR-URGENT
event Type
Equipment
probable Cause
Transmitter Failure
perceived Severity
Major (PMA)
Alarm Description
A fault has been detected concerning VSWR antenna supervision.
Alarm Number
1 : The High (second) threshold of antenna 1 VSWR has been exceeded.

2 : The High (second) threshold of antenna 2 VSWR has been exceeded.
3 : The High (second) thresholds on both antenna 1 and 2 have been
exceeded.
The cell is lost.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
226 / 320

Disable RF Power

Antenna Test Tools
Antenna Dummy Load.
[10,12]
ANTENNAVSWR
URGENT
Lock
RA
Unlock
RA
Alarm
disappears?
Yes
Alarm
solved
No
REK
used?
Yes
OMCR
No
REK
alarm(s)?
Yes
Solve REK
alarm(s)
No
VSWRAlarm
disappears?
No
TREAl
arms
Yes
Alarm
solved
Figure 110: ANTENNA-VSWR-URGENT: Corrective Actions
227 / 320
ANTENNAVSWRURGENT (continued)
TREAl
arms
TRE
alarm
events?
Yes
No
OR
OMCR
Lock
TRE(s)
connected to
susp. antenna
Temporary:
OR
OMCR
OMCR
ReduceTX
4
power by Set
Cell Telecom
Parameters
Solve TRE
alarm(s)
No
VSWRAlarm
disappears?
Yes
On
site
Alarm
solved
Figure 111: ANTENNA-VSWR-URGENT: Corrective Actions, continued
228 / 320
On
site
ANTENNAVSWRURGENT (continued)
Onsite
Check BTS status
Onsite
Onsite
Check cables to transmitter

antenna visually and
electrically.
Onsite
If not all possible TREs are

equipped, check for missing
dummy load on ANY.
Onsite

(connectors, damage, position,
reflection)
RA
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 112: ANTENNA-VSWR-URGENT: Corrective Actions, continued

Reduced TX Power
If the transmit power was reduced, set transmit power settings back to previous
values when the problem is solved.
229 / 320
8.6 [10,21] MODULE-FRAME-SIGNAL

8.6.1 [10,21] MODULE-FRAME-SIGNAL (TRE)
specific Problems
MODULE-CLOCK-SIGNAL
event Type
Equipment
probable Cause
Loss Of Signal
perceived Severity
Minor (DMA)
Alarm Description
A fault is detected on a multiframe clock signal from SUM.
Transmission quality is degraded.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
230 / 320

Disable RF Power
[10,21]
MODULEFRAMESIGNAL
(TRE)
Lock Function
TRE
TRE
alarm events?
Unlock Function
TRE
yes
Solve that alarm

first
no
More
than one TRE sends
this alarm?
yes
SUM
Clock alarm
events?
Solve that alarm

first
no
no
Onsite
Check cables to TRE
visually and
electrically.
Onsite
Check SUM
cables/connectors
Onsite
Onsite
Replace
TRE
Replace SUM
TRE
operational?
TRE
operational?
yes
Alarm
solved
yes
Alarm
solved
no
no
Contact
System Support
yes
Contact
System Support
Figure 113: MODULE-FRAME-SIGNAL (TRE): BTS 9100 Corrective Actions
231 / 320

Disable RF Power
[10,21]
MODULEFRAMESIGNAL
(TRE)
no
Reset Function
BTS
yes
BTS
operational?
yes
Master
Clock alarm
events?
Solve that
alarm(s) first
Alarm
solved
no
Onsite
Check cables between master BTS and
reporting slave BTS visually and
electrically.
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Switch off Battery
Backup Switch and
OR
Onsite
Switch off mains
mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
yes
Alarm
solved
no
Replace
BTS A910
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 114: MODULE-FRAME-SIGNAL (TRE): BTS 9110/9110-E Corrective Actions
232 / 320
8.6.2 [10,21] MODULE-FRAME-SIGNAL (RA)

specific Problems
MODULE-FRAME-SIGNAL
event Type
Equipment
probable Cause
Loss Of Signal
perceived Severity
Minor (DMA)
Alarm Description
A fault is detected on a multiframe clock signal from SUM.
Transmission quality is degraded.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
233 / 320

Disable RF Power
[10,21]
MODULEFRAMESIGNAL
(RA)
Lock Function
RA
SUM Clock
alarm events?
Unlock Function
RA
yes
Solve that alarm

first
no
Onsite
Check SUM
cables/connectors
Onsite
Check cables to TRE and
electrically.
Onsite
Replace
ANX,ANY,ANC
yes
Alarm
solved
RA
operational?
no
Contact
System Support
Figure 115: MODULE-FRAME-SIGNAL (RA): Corrective Actions
234 / 320
8.7 [10,22] MODULE-CLOCK-SIGNAL

8.7.1 [10,22] MODULE-CLOCK-SIGNAL (TRE)
specific Problems
MODULE-CLOCK-SIGNAL
event Type
Equipment
probable Cause
Loss Of Signal
perceived Severity
Minor (DMA)
Alarm Description
The input clock signal doesnt allow the TRE module to work.
Alarm Number
1 : Synchronization in clocks and FN has failed during initialization state.

2 : CLKI master clock failure has been detected in the operational state.
is lost. (X).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
X#*
Degradation
#*
235 / 320

Disable RF Power
[10,22]
MODULECLOCKSIGNAL
(TRE)
Lock Function
TRE
TRE
alarm events?
Unlock Function
TRE
yes
Solve that alarm

first
no
More
than one TRE sends
this alarm?
yes
SUM
Clock alarm
events?
Solve that alarm

first
no
no
Onsite
Check cables to TRE
visually and
electrically.
Onsite
Check SUM
cables/connectors
Onsite
Replace
TRE
Onsite
Replace SUM
yes
Alarm
solved
yes
TRE
operational?
TRE
operational?
Alarm
solved
no
no
Contact
System Support
yes
Contact
System Support
Figure 116: MODULE-CLOCK-SIGNAL (TRE): BTS 9100 Corrective Actions
236 / 320

Disable RF Power
[10,22]
MODULECLOCKSIGNAL
(TRE)
no
Reset Function
BTS
yes
BTS
operational?
yes
Master
Clock alarm
events?
Solve that
alarm(s) first
Alarm
solved
no
Onsite
Check cables between master BTS and
reporting slave BTS visually and
electrically.
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Switch off Battery
Onsite
Switch off mains
mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
yes
Alarm
solved
no
Replace
BTS A910
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 117: MODULE-CLOCK-SIGNAL (TRE): BTS 9110/9110-E Corrective Actions
237 / 320
8.7.2 [10,22] MODULE-CLOCK-SIGNAL (RA)

specific Problems
MODULE-CLOCK-SIGNAL
event Type
Equipment
probable Cause
Loss Of Signal
perceived Severity
Minor (DMA)
Alarm Description
The input clock signal on ANX is faulty.
Alarm Number
1 : Synchronization in clocks and frame numbers has failed during

initialization state.
2 : CLKI master clock failure has been detected in the operational state.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
238 / 320

Disable RF Power
[10,22]
MODULECLOCKSIGNAL
(RA)
Lock Function
RA
SUM Clock
alarm events?
Unlock Function
RA
yes
Solve that alarm

first
no
Onsite
Check SUM
cables/connectors
Onsite
Check cables to TRE and
electrically.
Onsite
Replace
ANX,ANY,ANC
yes
Alarm
solved
RA
operational?
no
Contact
System Support
Figure 118: MODULE-CLOCK-SIGNAL: Corrective Actions
239 / 320
8.8 [10,51] MODULE-NOT-PRESENT

8.8.1 [10,51] MODULE-NOT-PRESENT (TRE)
specific Problems
MODULE-NOT-PRESENT
event Type
Equipment
probable Cause
perceived Severity
Major (PMA)
Alarm Description
A TRE module was not initially present, or has recently been extracted.
Alarm Number
1 : The BCB detects the extraction of the module.

2 : There is no associated module for this SBL.
is lost. (X).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
X#*
Degradation
#*
240 / 320

Disable RF Power
[10,51]
MODULENOTPRESENT
(TRE)
Lock Function
TRE
Unlock Function
TRE
TRE
operational?
yes
Alarm
solved
yes
Alarm
solved
no
Onsite
Insert missing TRE
module
Onsite
Initialize the TRE
TRE
operational?
no
Contact
System Support
Figure 119: MODULE-NOT-PRESENT (TRE): BTS 9100 Corrective Actions
241 / 320

Disable RF Power
[10,51]
MODULENOTPRESENT
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Onsite
Switch off Battery

Backup Switch and
OR
Switch off mains

mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 120: MODULE-NOT-PRESENT (TRE): BTS 9110/9110-E Corrective Actions
242 / 320
8.8.2 [10,51] MODULE-NOT-PRESENT (RA)

specific Problems
MODULE-NOT-PRESENT
event Type
Equipment
probable Cause
perceived Severity
Major (PMA)
Alarm Description
An ANC or ANX is not present.
Alarm Number
The BCB detects the absence of the ANX/ANC module and there is no
other ANX/ANC operational in the same sector.
The sector is lost.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
243 / 320

Disable RF Power
[10,51]
MODULENOTPRESENT
(RA)
Lock Function
RA
Unlock Function
RA
TRE
operational?
yes
Alarm
solved
yes
Alarm
solved
no
Onsite
Insert missing
ANX,ANY,ANC
module
Onsite
Initialize the RAn
TRE
operational?
no
Contact
System Support
Figure 121: MODULE-NOT-PRESENT (RA): Corrective Actions
244 / 320
8.9 [10,234] IOM-DISCONNECTION

8.9.1 [10,234] IOM-DISCONNECTION (TRE)
specific Problems
IOM-DISCONNECTION
event Type
Equipment
probable Cause
perceived Severity
Minor (DMA)
Alarm Description
The IOM connection on BSII is faulty.
Telecom functions are not affected, as long as no commands on the Managed Objects (SBLs) TRE or
RA are executed.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
245 / 320

Disable RF Power
[10,234]
IOMDISCONNECTION
(TRE)
Lock Function
TRE
Unlock Function
TRE
TRE
operational?
yes
Alarm
solved
yes
Alarm
solved
no
Onsite
Replace TRE
TRE
operational?
no
Contact
System Support
Figure 122: IOM-DISCONNECTION (TRE): BTS 9100 Corrective Actions
246 / 320

Disable RF Power
[10,234]
IOMDISCONNECTION
(TRE)
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Onsite
Switch off Battery

fuse for tower mounted
BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 123: IOM-DISCONNECTION (TRE): BTS 9110/9110-E Corrective Actions
247 / 320
8.9.2 [10,234] IOM-DISCONNECTION (RA)

specific Problems
IOM-DISCONNECTION
event Type
Equipment
probable Cause
perceived Severity
Minor (DMA)
Alarm Description
The IOM connection on BSII is faulty.
Telecom functions are not affected, as long as no commands on the Managed Objects (SBLs) TRE or
RA are executed.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
248 / 320

Disable RF Power
[10,234]
IOMDISCONNECTION
(RA)
Lock Function
RA
Unlock Function
RA
RA
operational?
yes
Alarm
solved
yes
Alarm
solved
no
Onsite
Replace
ANX/ANY/ANC
RA
operational?
no
Contact
System Support
Figure 124: IOM-DISCONNECTION (RA): Corrective Actions
249 / 320

8.10.1 [10,237] HW-DEGRADED (TRE)
specific Problems
HW-DEGRADED
event Type
Equipment
probable Cause
perceived Severity
Alarm Description
Nbr 3: The BCB link to the module is faulty.

Nbr 12: This is an output power drop error.
Nbr 13: Hardware failure on unused part of twin (The twin in its current
configuration operates correctly. A problem will only occur when the
configuration will be changed.)
The antenna diversity is lost and the quality of reception is degraded.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
250 / 320

Disable RF Power
[10,237]
HWDEGRADED
(TRE)
Lock Function
TRE
Unlock Function
TRE
Onsite
Onsite
yes
Alarm
solved
Onsite
Reengage RIT
no
TRE
operational?
Onsite
Check BCB
cables/connectors
Disengage TRE
Onsite
Disengage, RIT by RIT, all

TREs, ANYs, ANXs, the
SUM and the XIOB
yes
Alarm persists?
Reengage TRE
no
Onsite
yes
Alarm persists?
Replace TRE
no
Onsite
Replace faulty RIT
TRE
operational?
Onsite
yes
Alarm persists?
yes
Alarm
solved
no
Replace BCB flat

cable
Contact
System Support
no
Alarm
solved
TRE
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 125: HW-DEGRADED (TRE): BTS 9100 Corrective Actions
251 / 320

Disable RF Power
[10,237]
HWDEGRADED
(TRE)
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Onsite
Switch off Battery

Backup Switch and
OR
Switch off mains

mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 126: HW-DEGRADED (TRE): BTS 9110/9110-E Corrective Actions
252 / 320
8.10.2 [10,237] HW-DEGRADED (RA)

specific Problems
HW-DEGRADED
event Type
Equipment
probable Cause
perceived Severity
Alarm Description
This is a HW failure, a local recovery action has failed.
Alarm Number
3 : The BCB link to the module is faulty. The information provided by the
BCB terminal of the module is inconsistent. The communication on the
BCB is corrupted by any module.
4 : The antenna VSWR circuitry is defective.
5 : A non-fatal fault has been detected on LNA 1 with 6 dB less gain on RX1.
6 : A non-fatal fault has been detected on LNA 2 with 6 dB less gain on RX2.
7 : A fatal fault has been detected on LNA 1: RX1 is lost. Consequently,
antenna diversity is lost.
8 : A fatal fault has been detected on LNA 2: RX2 is lost. Consequently,
antenna diversity is lost, if used.
9 : A HW failure is detected by auto-test, either in initialization state or in
fault localization state, or by selftest in initialization state.
11 : The module is in operational state but faulty, the Local Recovery
Action failed.
13 : The AGC cannot reach the LNA module. (This alarm occurs only
for the AGC module.)
Alarm Numbers 3, 4, 5, 6, 9, 11: There is no disturbance of the telecom application.

Alarm Numbers 7, 8: The antenna diversity is lost and the quality of reception is degraded.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
253 / 320
8.10.2.1 BTS 9100, Alarm Number 3 Corrective Actions

Disable RF Power
[10,237] HWDEGRADED
(RA)
Lock Function
TRE
Alarm Number 3
Unlock Function
TRE
Onsite
Onsite
yes
Alarm
solved
Onsite
Reengage RIT
no
TRE
operational?
Onsite
Check BCB
cables/connectors
Disengage TRE
Onsite
Disengage, RIT by RIT, all

TREs, ANYs, ANXs, the
SUM and the XIOB
yes
Alarm persists?
Reengage TRE
no
Onsite
yes
Alarm persists?
Replace TRE
no
Onsite
Replace faulty RIT
TRE
operational?
Onsite
yes
Alarm persists?
yes
Alarm
solved
no
Replace BCB flat

cable
Contact
System Support
no
Alarm
solved
TRE
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 127: HW-DEGRADED (RA): BTS 9100, Alarm Number 3 Corrective Actions
254 / 320
8.10.2.2 BTS 9100, Alarm Number 4...11, 13 Corrective Actions

Disable RF Power
[10,237]
HARDWAREDEGRADED
(RA)
Alarm Number 4...11, 13
Lock Function
RA
Unlock Function
RA
yes
RA
operational?
Alarm
solved
no
Onsite
Replace
ANX/ANY/ANC
or
Replace AGC
RA
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 128: HW-DEGRADED (RA): BTS 9100, Alarm Number 4...11 and 13
Corrective Actions
255 / 320

Disable RF Power
[10,237]
HARDWAREDEGRADED
(RA)
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Check cables to
transmitter antenna
visually and
electrically.
Onsite
(e.g. damage, position,
reflection). Solve antenna
problem.
Onsite
Replace VSWR
detector
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 129: HW-DEGRADED (RA): BTS 9100, Alarm Number 3 Corrective Actions
256 / 320
8.11 [10,239] HW-FAILURE

8.11.1 [10,239] HW-FAILURE (TRE)
specific Problems
HW-FAILURE
event Type
Equipment
probable Cause
perceived Severity
Major (PMA), Minor (DMA)
Alarm Description
Major (PMA): This is a HW failure, a local recovery action has failed.

Minor (DMA): The local recovery is successful.
Alarm Number
1: A HW failure is detected by the auto-test, either in initialization state or

in fault localization state, or by selftest in initialization state (failures not
covered by other numbers).
2: The DC/DC converter has failed.
3: A fatal error has been reported by a layer 1 DSP concerning the radio.
4: A fault has been detected at the Entity Control Parallel Link (ECPL)
interface management.
5: One DSP has reported a fatal error in its internal processing.
6: At least one DSP has not answered to the SCP polling.
7: A fatal error has been reported by a layer 1 DSP or the MBED on a
serial internal interface.
8: The FN_SUP timer (FN supervision) elapsed: FCLK interrupt is missing.
9: The internal FNs from layer 1 are not consistent.
11: The module was not in an operational state (no more information is
available). The OMU has performed a Local Recovery Action.
12: The module has no input power.
13: The front panel power switch is set off (Power Off) for the concerned
module.
14: Unknown cause: alarm indicates that more detailed alarms were
reported before and are available at OMC-R.
15: The TRE reported to OMU BSII a failure alarm. The OMU has then
performed on TRE a Local Recovery Action which has failed.
16: TRE internal PLL not locked.
257 / 320
is lost. (X).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
X#*
Degradation
#*
258 / 320
8.11.1.1 9100 BTS, Alarm Number 1...11, 15 and 16 Corrective Actions

Disable RF Power
[10,239] HWFAILURE
(TRE)
Lock Function
TRE
Alarm Number 1, 3...11, 15 & 16
Unlock Function
TRE
TRE
operational?
yes
Alarm
solved
no
TRE alarm
events?
yes
Solve TRE
alarm first
no
Onsite
Check BTS status
Onsite
yes
Alarm persists?
Replace TRE
no
Alarm
solved
TRE
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 130: HW-FAILURE (TRE): 9100 BTS, Alarm Number 1...11, 15 and 16
Corrective Actions
Additionally for alarm number 3: in case the alarm is reported by several
TREs and the additional info contains either DF 3B 03 20 1C 19 DF 3D 14 01
15 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 or DF 3B 03 20 1C
19 DF 3D 22 01 15 00 00 00 00 00 00 00 00 00 00 00 00 xx xx xx xx 00 01 00
00 00 00 00 00 00 00 00 00 xx xx xx xx (whatever xx is) and thus indicating a
L1 status: LD_13MHz, no lock detection for 13 MHz synthesiser (ENCT),
replace the SUMx board as this one causes the alarms.
259 / 320
8.11.1.2 9100 BTS, Alarm Number 12 Corrective Actions

Disable RF Power
[10,239] HWFAILURE
(TRE)
Power alarm
events?
Alarm Number 12
yes
Solve power
alarm first
no
yes
Alarm persists?
no
Alarm
solved
Onsite
Check power supply.
Ensure BTS is
powered correctly.
Onsite
yes
Alarm persists?
Replace TRE
no
Alarm
solved
TRE
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 131: HW-FAILURE (TRE): 9100 BTS, Alarm Number 12 Corrective

Actions
260 / 320
8.11.1.3 9100 BTS, Alarm Number 13 Corrective Actions

[10,239] HWFAILURE
(TRE)
Alarm Number 13
Switch ON the
front panel power
switch
Initialise the TRE
TRE
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 132: HW-FAILURE (TRE): 9100 BTS, Alarm Number 13 Corrective

Actions
261 / 320
8.11.1.4 9110 Micro BTS/9110-E Micro BTS Corrective Actions

[10,239] HWFAILURE
(TRE)
Reset Function
BTS
yes
BTS
operational?
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
Onsite
Switch off Battery

OR Backup Switch and OR
Onsite
Onsite
Switch off mains
mounted BTS
Onsite
Check cables between indicated

clock unit on master BTS and
reporting clock unit.
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 133: HW-FAILURE (TRE): 9110 Micro BTS/9110-E Micro BTS

Corrective Actions
262 / 320
8.11.2 [10,239] HW-FAILURE (RA)

specific Problems
HW-FAILURE
event Type
Equipment
probable Cause
perceived Severity
Major (PMA)
Alarm Description
This is a HW failure, a local recovery action has failed.
Alarm Number
2 : The DC/DC converter of the module failed.

10 : A fatal fault has been detected on both LNA 1 and LNA2: RX1 and
RX2 are lost. Or fault detected on LNA1 only if no antenna diversity
configuration or on LNA2 only for 9110 Micro BTS in no antenna diversity
configuration and MAN is configured with two sectors.
12 : The module has no input power.
14 : Unknown cause, alarm indicates that more detailed alarms were
reported before and are available at OMC-R.
The sector is lost.

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
263 / 320
8.11.2.1 BTS 9100, Alarm Number 2 and 12 Corrective Actions

Disable RF Power
[10,239] HWFAILURE
(RA)
Lock Function
RA
Alarm Number 2 & 12
Unlock Function
RA
RA
operational?
yes
Alarm
solved
no
Power alarm
events?
yes
Solve power
alarm first
no
Onsite
Check power supply.
Ensure ANX/ANC is
powered correctly.
Onsite
yes
Alarm persists?
Replace
ANX/ANY/ANC
no
Alarm
solved
RA
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 134: HW-FAILURE (RA): BTS 9100, Alarm Number 2 and 12 Corrective
Actions
264 / 320

Disable RF Power
[10,239] HWFAILURE
(RA)
Lock Function
RA
Alarm Number 10
Unlock Function
RA
RA
operational?
yes
Alarm
solved
no
Other TRE
alarm
events?
yes
Solve TRE
alarm(s) first
no
Onsite
Check BTS status
Onsite
yes
Alarm persists?
Replace
ANX/ANY/ANC
no
Alarm
solved
RA
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 135: HW-FAILURE (RA): BTS 9100, Alarm Number 10 Corrective

Actions
265 / 320

Disable RF Power
[10,239] HWFAILURE
(RA)
Alarm Number 14
Lock Function
RA
Unlock Function
RA
RA
operational?
yes
Alarm
solved
yes
Solve related
alarm(s) first
no
Other
related alarm
events?
no
RA
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 136: HW-FAILURE (RA): BTS 9100, Alarm Number 14 Corrective

Actions
266 / 320

Disable RF Power
[10,239] HWFAILURE
(RA)
If an alarm on the feeding clock

unit of the master BTS is still
outstanding, the failure is due to
external reasons.
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Onsite
Switch off Battery

Switch off mains

mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 137: HW-FAILURE (RA): BTS 9110/9110-E Corrective Actions
267 / 320
8.12 [10,248] RESTART

8.12.1 [10,248] RESTART (TRE)
specific Problems
RESTART
event Type
Processing Error
probable Cause
perceived Severity
Warning (MI)
Alarm Description
The TRE has (auto)restarted successfully.
Alarm Number
3 : A successful Local Recovery Action has been performed by the SUM

on the TRE, after detection of a recoverable failure (i.e., auto-restart failure,
IOM disconnection).
10 : A fatal exception has occurred on an SCP, or a SCP SW error has
been detected in operational state.
14 : The TS reconfiguration has failed in the operational state because
the TS was already active.
19 : A fatal error has been reported by a layer 1 DSP concerning the radio
in operational state.
20 : Restart due to a watchdog reset for an unknown reason.
22 : A fault has been detected at the ECPL interface management in
operational state.
23 : A DSP has reported a fatal error in its internal processing in the
operational state.
24 : At least one DSP has not answered the SCP polling in the operational
state.
25 : A fatal error has been reported by a layer 1 DSP or MBED on a serial
internal interface in the operational state.
26 : FN_SUP timer (FN supervision) elapsed in the operational state:
FCLK interrupt is missing.
27 : Internal FNs from layer 1 are not consistent in the operational state.
During the restart, the TRE looses all its calls, but after the restart, the TRE is again usable.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
268 / 320

Disable RF Power
If the TRE restarts consecutively after a short period, the parameters sent
are corrupted, or there may be a TRE hardware problem.
[10,248] RESTART
(TRE)
Unlock Function
TRE
Lock Function
TRE
TRE
operational?
yes
Alarm
solved
no
Check configuration
parameters
Correct configuration
parameters
TRE
operational?
yes
Alarm
solved
yes
Alarm
solved
no
Onsite
Replace TRE
TRE
operational?
no
Contact
System Support
Figure 138: RESTART (TRE): BTS 9100 Corrective Actions
269 / 320

Disable RF Power
[10,248] RESTART (TRE)
Reset Function
BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Onsite
Switch off Battery

Switch off mains

mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
BTS
operational?
no
Replace
BTS A910
yes
Alarm
solved
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 139: RESTART (TRE): BTS 9110/9110-E Corrective Actions
270 / 320
8.12.2 [10,248] RESTART (RA)

specific Problems
RESTART
event Type
Processing Error
probable Cause
perceived Severity
Warning (MI)
Alarm Description
The ANX/ANC has (auto)restarted successfully.
Alarm Number
1 : A fatal exception has occurred on P, or a P SW error has been

detected in the operational state.
2 : Watchdog reset has occurred.
3 : A successful Local Recovery Action has been performed by the OMU
on the ANX/ANC, after detection of a recoverable failure (i.e., auto-restart
failure, IOM disconnection).

Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
271 / 320

Disable RF Power
If the ANX/ANC restarts consecutively after a short period, the parameters
sent are corrupted, or there may be a ANX/ANC hardware problem.
[10,248] RESTART (RA)
Lock Function
RA
Unlock Function
RA
RA
operational?
yes
Alarm
solved
no
Onsite
Check configuration
parameters.
Onsite
yes
Alarm persists?
Replace
ANX/ANY/ANC
no
Alarm
solved
RA
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 140: RESTART (RA): Corrective Actions
272 / 320
9 Class 11: BTS-TRANS Alarms

This section defines the BTS alarms for Class 11: BTS-TRANS alarm class.
273 / 320
9.1 [11,22] LOOP-TO-EQUIPMENT

specific Problems
LOOP-TO-EQUIPMENT
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Alarm Description
An external loop is closed on an interface of the module. All channels on

this interface (OML, RSL, TCH) are looped back.
Alarm Number
1 : An external loop is closed (in DSWICH) on Abis interface of the module.

2 : An external loop is closed (in DSWICH) on BSII interface of the module.
As long as the loop is closed, the concerned channels are not available.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
274 / 320

[11,22] LOOPTO
EQUIPMENT
Onsite
Release
external loop
BTS
operational?
yes
Alarm
solved
yes
Alarm
solved
no
Reset BTS
BTS
operational?
no
Onsite
Replace
SUMP/SUMA
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 141: LOOP-TO-EQUIPMENT: BTS 9100 Corrective Actions
275 / 320

[11,22] LOOPTO
EQUIPMENT
Onsite
yes
BTS
operational?
Release external
test loop
no
Alarm
solved
Onsite
Reset
Function BTS
BTS
operational?
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Switch off Battery
Onsite
Switch off mains
mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
Replace
BTS A910
no
BTS
operational?
yes
yes
Alarm
solved
BTS
operational?
Alarm
solved
no
Contact
System Support
Figure 142: LOOP-TO-EQUIPMENT: BTS 9110/9110-E Corrective Actions
276 / 320
9.2 [11,50] LOSS-OF-INCOMING-SIGNAL

specific Problems
LOSS-OF-INCOMING-SIGNAL
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Alarm Description
There is a loss of incoming 2 Mbit/s signal on the Abis link.
LMT :
The corresponding Abis link is lost. If the link towards the BSC is concerned, the BTS is lost (if no
redundancy).
OMC :
Case 1, the link towards the BSC is concerned: The Abis link to the BTS was lost. The Abis link is
reestablished and allows the alarm reception (otherwise, without Abis link, no alarms are reported to
the OMC).
Case 2, link in other direction is concerned: The other BTS in the chain are lost.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
277 / 320

[11,50] LOSSOF
INCOMINGSIGNAL
Abis link
is re
established?
yes
Check/solve
alarms of AIFL
yes
Solve Abis
alarm(s) first
no
Other
Abis alarm(s)
on BSS
events?
no
Onsite
Check Abis
cables/connectors
Onsite
Reset BTS
Abis link
is re
established?
no
yes
Alarm
solved
yes
Alarm
solved
Onsite
Replace
SUMP/SUMA
no
Abis link
is re
established?
no
Contact
System Support
Figure 143: LOSS-OF-INCOMING-SIGNAL: BTS 9100 Corrective Actions
278 / 320

[11,50] LOSSOF
INCOMINGSIGNAL
Onsite
no
Abis link
is re
established?
Reset
Function BTS
yes
Abis link
is re
established?
Check/solve
alarms of AIFL
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
Onsite
OR
Switch off Battery

Onsite
Switch off mains
power fuse for
tower mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
Abis link
is re
established?
yes
Alarm
solved
no
Replace
BTS A910
Abis link
is re
established?
yes
Alarm
solved
no
Contact
System Support
Figure 144: LOSS-OF-INCOMING-SIGNAL: BTS 9110/9110-E Corrective Actions
279 / 320
9.3 [11,66] AIS-2M

specific Problems
AIS-2M
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Alarm Description
The 2 Mbit/s interface is receiving a AIS signal (all one indication).
LMT :
redundancy).
OMC :
the OMC).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
280 / 320
9.3.1 9100 BTS Corrective Actions

[11,66] AIS2M
Related BTS alarms?
yes
Alarm
persists?
Solve this alarms
no
no
yes
yes
Alarm
persists?
Solve this alarms
Related BSC alarms?
no
no
yes
Check related SBL

(OML, RSL)
SBL in fault?
no
Inhibit / allow alarm

reporting
Alarm
persists?
yes
BTS TRANS
settings ok (CRC4)?
no
yes
no
Correct BTS TRANS

settings
no
Alarm
persists?
yes
Alarm
solved
yes
Loop back BTS

originated E1 link at
BTS site
No BSS problem;
Check E1 link with
line provider.
yes
Alarm
persists?
yes
Loop back BTS

BSC site
Alarm
persists?
no
Check BSC local

cabling
Local cabling OK?
no
Solve cabling
problem
Alarm
persists?
yes
yes
Replace
SUMx
no
Alarm
persists?
yes
no
Contact
System Support
Figure 145: AIS-2M: Corrective Actions: 9100 BTS Corrective Actions
281 / 320
9.3.2 9110 Micro BTS/9110-E Micro BTS Corrective Actions

[11,66] AIS2M
Related BTS alarms?
yes
Alarm
persists?
Solve this alarms
no
no
yes
yes
Alarm
persists?
Solve this alarms
Related BSC alarms?
no
no
yes
Check related SBL

(OML, RSL)
SBL in fault?
no

reporting
Alarm
persists?
yes
BTS TRANS
settings ok (CRC4)?
no
yes
no
Correct BTS TRANS

settings
no
Alarm
persists?
yes
Alarm
solved
yes
Loop back BTS

BTS site
No BSS problem;
Check E1 link with
line provider.
yes
Alarm
persists?
yes
Loop back BTS

BSC site
Alarm
persists?
no
Check BSC local

cabling
Local cabling OK?
no
Solve cabling
problem
Alarm
persists?
yes
yes
Replace
9110 Micro BTS /
9110E Micro BTS
no
Alarm
persists?
yes
no
Contact
System Support
Figure 146: AIS-2M: 9110 Micro BTS/9110-E Micro BTS Corrective Actions
282 / 320
9.4 [11,81] LOSS-OF-FRAME-ALIGNMENT

specific Problems
LOSS-OF-FRAME-ALIGNMENT
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Alarm Description
There is a loss of frame alignment on the Abis link.
LMT :
redundancy).
OMC :
the OMC).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
283 / 320

[11,81] LOSSOF
FRAMEALIGNMENT
Abis link
is re
established?
yes
Check/solve
alarms of AIFL
yes
Solve Abis
alarm(s) first
no
Other
Abis alarm(s)
events?
no
Check Transmission
equipment on
all nodes up to BSC
Onsite
Check Abis
cables/connectors
Abis link
is re
established?
yes
Alarm
solved
no
Onsite
Replace
SUMP/SUMA
Abis link
is re
established?
yes
Alarm
solved
no
Contact
System Support
Figure 147: LOSS-OF-FRAME-ALIGNMENT: BTS 9100 Corrective Actions
284 / 320

[11,81] LOSSOF
FRAMEALIGNMENT
Onsite
no
Abis link
is re
established?
Reset
Function BTS
yes
Abis link
is re
established?
Check/solve
alarms of AIFL
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
Onsite
OR
Switch off Battery

Onsite
Switch off mains
power fuse for
tower mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
Abis link
is re
established?
yes
Alarm
solved
no
Replace
BTS A910
Abis link
is re
established?
yes
Alarm
solved
no
Contact
System Support
Figure 148: LOSS-OF-FRAME-ALIGNMENT: BTS 9110/9110-E Corrective Actions
285 / 320
9.5 [11,86] LOSS-OF-CRC-MULTIFRAME-ALIGNMENT

specific Problems
LOSS-OF-CRC-MULTIFRAME-ALIGNMENT
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Alarm Description
The CRC is not used at the remote end or there may be interferences on
the connection.
The CRC multiframe alignment on the Abis link is lost.
LMT :
redundancy).
OMC :
the OMC).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
286 / 320

[11,86]
LOSSOFCRCMULTIFRAME
ALIGNMENT
Abis link
is re
established?
yes
Check/solve
alarms of AIFL
no
CRC
enabled?
no
Enable CRC in
transmission equipment
yes
Onsite
Check Abis
cables/connectors
no
yes
BTS
operational?
Alarm
solved
Onsite
Check
Abis equipment
Onsite
Check
transmission
equipment up to
next node
in Abis chain
Abis link
is re
established?
yes
Alarm
solved
no
Onsite
Replace
SUMP/SUMA
BTS
operational?
yes
Alarm
solved
no
Contact
System Support
Figure 149: LOSS-OF-CRC-MULTIFRAME-ALIGNMENT: BTS 9100 Corrective

Actions
287 / 320

[11,86]
LOSSOFCRCMULTIFRAME
ALIGNMENT
Onsite
no
Abis link
is re
established?
Reset
Function BTS
yes
Abis link
is re
established?
Check/solve
alarms of AIFL
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Switch off Battery
Backup Switch and
OR
Onsite
Switch off mains
power fuse for
tower mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
Abis link
is re
established?
yes
no
Check
transmission
equipment up to
next node
in Abis chain
Abis link
is re
established?
yes
Alarm
solved
no
Onsite
Alarm
solved
Replace
BTS A910
Abis link
is re
established?
yes
Alarm
solved
no
Contact
System Support
Figure 150: LOSS-OF-CRC-MULTIFRAME-ALIGNMENT: BTS 9110/9110-E Corrective Actions
288 / 320
9.6 [11,99] ERROR-RATE >E-3

specific Problems
ERROR-RATE>E-3
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Alarm Description
The error rate of the incoming main system signal on the Abis link is worse
than the threshold value E-3.
LMT :
redundancy).
OMC :
the OMC).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
289 / 320

[11,99] ERRORRATE
> E3
Abis link
quality
OK?
yes
Check/solve
alarms of AIFL
no
Other
yes
PCM Abis alarm(s)
events?
Solve Abis
alarm(s) first
no
Abis link
quality
OK?
yes
Alarm
solved
no
Onsite
Check Abis
cables/connectors
Onsite
Reset BTS
Abis link
quality
OK?
no
yes
Alarm
solved
yes
Alarm
solved
Onsite
Replace
SUMP/SUMA
Abis link
quality
OK?
no
Contact
System Support
Figure 151: ERROR-RATE>E-3: BTS 9100 Corrective Actions
290 / 320

[11,99] ERRORRATE
> E3
Onsite
Abis link
quality
OK?
no
Reset
Function BTS
yes
Abis link
quality
OK?
Check/solve
alarms of AIFL
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Switch off Battery
Onsite
Switch off mains
power fuse for
tower mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
Abis link
quality
OK?
no
Replace
BTS A910
Abis link
quality
OK?
Alarm
solved
no
yes
Alarm
solved
yes
Contact
System Support
Figure 152: ERROR-RATE>E-3: BTS 9110/9110-E Corrective Actions
291 / 320
9.7 [11,100] ERROR-RATE >E-4

specific Problems
ERROR-RATE>E-4
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA), Event (Mi)
Alarm Description
The error rate of the incoming main system signal on the Abis link is worse
than the threshold value E-4.
LMT :
The corresponding Abis link is degraded.
OMC :
Case 1, the link towards the BSC is concerned: The Abis link to the BTS is degraded.
Case 2, link in other direction is concerned: The link to the other BTS in the chain is degraded.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
292 / 320

[11,100] ERRORRATE
> E4
Abis link
quality
OK?
yes
Check/solve
alarms of AIFL
no
Other
yes
PCM Abis alarm(s)
events?
Solve Abis
alarm(s) first
no
Abis link
quality
OK?
yes
Alarm
solved
no
Onsite
Check Abis
cables/connectors
Onsite
Reset BTS
Abis link
quality
OK?
no
yes
Alarm
solved
yes
Alarm
solved
Onsite
Replace
SUMP/SUMA
Abis link
quality
OK?
no
Contact
System Support
293 / 320

[11,100] ERRORRATE
> E4
Onsite
Abis link
quality
OK?
no
Reset
Function BTS
yes
Abis link
quality
OK?
Check/solve
alarms of AIFL
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Switch off Battery
Onsite
Switch off mains
power fuse for
tower mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
Abis link
quality
OK?
no
Abis link
quality
OK?
Replace
BTS A910
Alarm
solved
no
yes
Alarm
solved
yes
Contact
System Support
294 / 320
9.8 [11,102] ERROR-RATE >E-6

specific Problems
ERROR-RATE>E-6
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Alarm Description
The error rate of the incoming main system signal in Abis is worse than the
threshold value E-6.
LMT :
The corresponding Abis link is possibly degraded.
OMC :
Case 1, the link towards the BSC is concerned: The Abis link to the BTS is possibly degraded.
Case 2, link in other direction is concerned: The link to the other BTS in the chain is possibly degraded.
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
(X)
(X)
295 / 320

[11,102] ERRORRATE
> E6
Abis link
quality
OK?
yes
Check/solve
alarms of AIFL
no
Other
yes
PCM Abis alarm(s)
events?
Solve Abis
alarm(s) first
no
Abis link
quality
OK?
yes
Alarm
solved
no
Onsite
Check Abis
cables/connectors
Onsite
Reset BTS
Abis link
quality
OK?
no
yes
Alarm
solved
yes
Alarm
solved
Onsite
Replace
SUMP/SUMA
Abis link
quality
OK?
no
Contact
System Support
296 / 320

[11,102] ERRORRATE
> E6
Onsite
Abis link
quality
OK?
no
Reset
Function BTS
yes
Abis link
quality
OK?
Check/solve
alarms of AIFL
yes
Alarm
solved
no
Onsite
Disconnect mains
power from ACCO
to Basic Unit
OR
Onsite
Switch off Battery
Onsite
Switch off mains
power fuse for
tower mounted BTS
Onsite
After 30 s
repower the BTS
Onsite
Abis link
quality
OK?
no
Abis link
quality
OK?
Replace
BTS A910
Alarm
solved
no
yes
Alarm
solved
yes
Contact
System Support
297 / 320
9.9 [11,176] REMOTE-ALARM-INDICATION

specific Problems
REMOTE-ALARM-INDICATION
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Minor (DMA), Event (Mi)
Alarm Description
An alarm indication from the remote end is detected. The remote end
has set RAI bit in TS0 or F bit in TS 1...31 in order to indicate reception
problems.
LMT :
redundancy).
OMC :
the OMC).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation
298 / 320
9.9.1 9100 BTS Corrective Actions

[11,176] REMOTE
ALARMINDICATION
Related BTS alarms?
yes
Alarm
persists?
Solve this alarms
no
no
yes
yes
Alarm
persists?
Solve this alarms
Related BSC alarms?
no
no
yes
Check related SBL

(OML, RSL)
SBL in fault?
no

reporting
Alarm
persists?
yes
BTS TRANS
settings ok (CRC4)?
no
yes
no
Correct BTS TRANS

settings
no
Alarm
persists?
yes
Alarm
solved
yes
Loop back BTS

BTS site
No BSS problem;
Check E1 link with
line provider.
yes
Alarm
persists?
yes
Loop back BTS

BSC site
Alarm
persists?
no
Check BSC local

cabling
Local cabling OK?
no
Solve cabling
problem
Alarm
persists?
yes
yes
Replace
SUMx
no
Alarm
persists?
yes
no
Contact
System Support
Figure 157: REMOTE-ALARM-INDICATION: 9100 BTS Corrective Actions
299 / 320
9.9.2 9110 Micro BTS/9110-E Micro BTS Corrective Actions

[11,176] REMOTE
ALARMINDICATION
Related BTS alarms?
yes
Alarm
persists?
Solve this alarms
no
no
yes
yes
Alarm
persists?
Solve this alarms
Related BSC alarms?
no
no
yes
Check related SBL

(OML, RSL)
SBL in fault?
no

reporting
Alarm
persists?
yes
BTS TRANS
settings ok (CRC4)?
no
yes
no
Correct BTS TRANS

settings
no
Alarm
persists?
yes
Alarm
solved
yes
Loop back BTS

BTS site
No BSS problem;
Check E1 link with
line provider.
yes
Alarm
persists?
yes
Loop back BTS

BSC site
Alarm
persists?
no
Check BSC local

cabling
Local cabling OK?
no
Solve cabling
problem
Alarm
persists?
yes
yes
Replace
9110 Micro BTS /
9110E Micro BTS
Alarm
persists?
yes
300 / 320
no
no
Contact
System Support
9.10 [11,177] PPP ALL1

specific Problems
PPP ALL1
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Major (PMA)
Alarm Description
All 1s are detected in PPP frames on BTS side.
Alarm Number
1 : PPP All1.
LMT :
redundancy).
OMC :
the OMC).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

[11,177] PPP ALL1
Replace faulty
equipment on remote
end
yes
Alarm cleared?
Alarm
solved
no
Contact
System Support
Figure 158: PPP ALL1: Corrective Actions
301 / 320
9.11 [11,178] PPP NO RECEIPT OF HDLC SIGNAL

specific Problems
PPP NO RECEIPT OF HDLC SIGNAL
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Major (PMA)
Alarm Description
No HDLC signal is received on the BTS side.
Alarm Number
1 : PPP No Receipt of HDLC Signal.
LMT :
redundancy).
OMC :
the OMC).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

[11,178] PPP NO RECEIPT
OF HDLC SIGNAL
Replace faulty
equipment on remote
end
yes
Alarm cleared?
Alarm
solved
no
Contact
System Support
Figure 159: PPP NO RECEIPT OF HDLC SIGNAL: Corrective Actions
302 / 320
9.12 [11,179] PPP RECEIPT OF TERMINATE

specific Problems
PPP RECEIPT OF TERMINATE
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Major (PMA)
Alarm Description
The BTS side received a Terminate signal.
Alarm Number
1 : PPP Receipt of Terminate.
LMT :
redundancy).
OMC :
the OMC).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

[11,179] PPP RECEIPT OF
TERMINATE
Replace faulty
equipment on remote
end
yes
Alarm cleared?
Alarm
solved
no
Contact
System Support
Figure 160: PPP RECEIPT OF TERMINATE: Corrective Actions
303 / 320
9.13 [11,180] HDLC HIGH ERRONEOUS FRAMES RATIO

specific Problems
HDLC HIGH ERRONEOUS FRAMES RATIO
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Major (PMA)
Alarm Description
High ratio of HDLC failures (CRC, frames too long, frames too short,
receipt of abort).
Alarm Number
1 : PPP High Erroneous Frames Ratio.
LMT :
redundancy).
OMC :
the OMC).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

[11,180] PPP HIGH
ERRONEOUS FRAMES
RATIO
Replace faulty
equipment on remote
end
yes
Alarm cleared?
Alarm
solved
no
Contact
System Support
Figure 161: PPP HIGH ERRONEOUS FRAMES RATIO: Corrective Actions
304 / 320
9.14 [11,181] HDLC MEDIUM ERRONEOUS FRAMES RATIO

specific Problems
HDLC MEDIUM ERRONEOUS FRAMES RATIO
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Major (PMA)
Alarm Description
Medium ratio of HDLC failures (CRC, frames too long, frames too short,
receipt of abort).
Alarm Number
1 : PPP Medium Erroneous Frames Ratio.
LMT :
redundancy).
OMC :
the OMC).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

[11,181] PPP MEDIUM
ERRONEOUS FRAMES
RATIO
Replace faulty
equipment on remote
end
yes
Alarm cleared?
Alarm
solved
no
Contact
System Support
Figure 162: PPP MEDIUM ERRONEOUS FRAMES RATIO: Corrective Actions
305 / 320
9.15 [11,182] HDLC LOW ERRONEOUS FRAMES RATIO

specific Problems
HDLC LOW ERRONEOUS FRAMES RATIO
event Type
Equipment
probable Cause
Indeterminate
perceived Severity
Major (PMA)
Alarm Description
Low ratio of HDLC failures (CRC, frames too long, frames too short, receipt
of abort).
Alarm Number
1 : PPP Low Erroneous Frames Ratio.
LMT :
redundancy).
OMC :
the OMC).
Impact
BSS
Cell(s)
Signaling
Calls
Loss
Degradation

[11,182] PPP LOW
ERRONEOUS FRAMES
RATIO
Replace faulty
equipment on remote
end
yes
Alarm cleared?
Alarm
solved
no
Contact
System Support
Figure 163: PPP LOW ERRONEOUS FRAMES RATIO: Corrective Actions
306 / 320
10 BTS Alarm Additional Information

This section describes the additional information supplied by some BTS alarms.
307 / 320
10.1 BTS Alarms with Additional Information

This section describes the BTS alarms that can provide additional information.
Depending on the alarm, the additional information can comprise one or
more TLV codes.
10.1.1 [2,247]
The coding of the additional information for this alarm depends on the alarm
number, as shown in Table 5 . This information is only provided if the OMU has
battery backup for its RAM.
Alarm Number
Bytes
Coding
1-5
TLV120
6 - 24
TLV83
1-5
TLV120
6 - 37
TLV84
1-5
TLV120
6 - 24
TLV83
1-5
TLV120
6 - 176
TLV82
Table 5: Alarm [2,247] TLV Codes
10.1.2 [2,248]
The coding of the additional information for this alarm depends on the alarm
number, as shown in Table 6 .
Alarm Number
Bytes
Coding
1-5
TLV120
6 - 37
TLV84
1-5
TLV120
6 - 24
TLV83
1-5
TLV120
6 - 176
TLV82
Table 6: Alarm [2,248] TLV Codes
308 / 320
10.2 TLV Coding

Additional information is provided in the form of Tag Length Value (TLV) codes
that describe system automatic test results. The first two bytes of additional
information define the TLV code identity number. The third byte defines the
number of succeeding bytes, including itself, that comprise the message.
10.2.1 TLV 81 Coding

The TLV 81 include:
For the CU SBL:
In case of alarm sent by TRE
TLV 49 (FU HW Cap, as received from TRE at re-/ config time)
TLV 243 (BTS_HW_Family)
TLV 59 (Fault_Info from TRE) optional
TLV 61 (Detailed_Results from TRE) optional (n times, n>=1)
For the RA SBL:
In case of alarm sent by ANX
TLV 59 (Fault_Info from ANX/ANC) optional
TLV 61 (Detailed_Results from ANX/ANC) optional (n times, n>=1)
For the CLLK SBL
In case of alarm sent by TRANS & CLOCK / SUM
TLV 59 (Fault_Info from TRANS & CLOCK / SUM) optional
TLV 61 (Detailed_Results from TRANS & CLOCK / SUM) optional (n
times, n>=1)
For the OMU SBL:
In case of OMU autorestart / autoreset
TLV 120 (OMU HW characteristics) optional
TLV 82 (Additional info for m*P exceptions) optional
TLV 83 (Additional info for Scenario problems) optional
TLV 84 (Additional info for Lack of resources) optional
309 / 320
10.2.2 TLV49 Coding

The TLV49 byte definitions are shown in the following table.
Bytes
Description - FU HW Capability
Element Identifier ( = 49)
Length (=4)
FU Generation
0 = G1 FU, G2 FU3
1 = G2 FU2
2 = G2 Micro BTS
3 = DR-FU
4 = 9100 TRE
FF = unknown
FR/DR
bits 7 to 3 - unused (bit 7 is hi-order bit on the left)

bit 2 Enhanced Full Rate -Not Provided (0) Provided (1)
bit 1 Full Rate -Not Provided (0) Provided (1
bit 0 Half Rate -Not Provided (0) Provided (1)
FU CIPHERING
CAPABILITY
bit 7 Encryption with A5/7 algorithm - Not Provided (0) Provided (1)
bit 0 No Encryption - always 1 = provided (always possible)
FF = all algorithms supported. )) never sent by the FUunknown.
RSL RATE
CAPABILITY
bits 7 to 2 - unused (bit 7 is hi-order bit on the left)

bit 1 = 64 Kb/sec - Not Provided (0) Provided (1)
bit 0 = 16 Kb/sec - Not Provided (0) Provided (1)
FF = unknown
310 / 320
10.2.3 TLV59 Coding

TLV59 is used for reporting TRE, AN and TRANS&CLOCK Alarm Type for BTS.
Table 7 shows the definitions of TLV 59 for the TRE faults (9100
BTS only). EVAD indicates the faultcondition: 1 = Eventtype
(EV), 0 = Appearance/Disappearance type (AD). AD indicates the
Appearance/Disappearance state; 1 = Appearance (ON), 0 = Disappearance
(OFF).
ALATYP
ALAN
EVAD
Description of Fault Code
AD
CLKI clock failure (1)
AD
CLKI frame failure
AD
RSL LAPD link failure
AD
Non fatal temperature failure
13
AD
TRE VSWR failure (1)
20
Recoverable failure
0
EV
Microprocessor failure
21
EV
BCCH failure
22
EV
Algorithm failure
23
EV
TLC_CONFIG_T expiry
24
EV
TS reconfiguration failure
25
EV
SYS INFO 3 failure
27
EV
BCCH_CUT timeout
28
EV
Radio failure
29
EV
ECPL failure
30
EV
L1 DSP failure
31
EV
L1 DSP no response failure
32
EV
Internal serial interface failure
33
EV
FCLK IT failure
34
EV
Internal FN failure
21
Handover/Power control algorithms configuration refused

0
25
EV
Missing message
TRE fatal failure (1)
311 / 320
ALATYP
ALAN
EVAD
AD
AD
HW failure
AD
SW failure
AD
CLKI synchronization failure
AD
Autoreconfiguration failure
AD
Configuration failure
AD
BSII failure (2)
AD
IOM LAPD link failure
AD
SW activation failure
AD
Downloading failure
10
AD
HW watchdog reset
11
AD
Configuration file failure
20
AD
Temperature failure
28
AD
Radio failure
29
AD
ECPL failure
30
AD
L1 DSP failure
31
AD
L1 DSP no response failure
32
AD
Internal serial interface failure
33
AD
FCLK IT failure
34
AD
Internal FN failure
Table 7: TLV59 for TRE faults of 9100 BTS

(1) As this alarm is fatal for the module, no alarm disappearance indication is
supplied. The alarm disappearance is detected on Alarm In Force List report.
(2) As the link connection is lost, the failure cannot be spontaneously reported
to the OMU/SUM. But the corresponding alarm is stored in the Alarms In Force
List and may be obtained by the OMU/SUM on Alarm In Force List report (if the
failure has disappeared), as long as the module stays in out of order state (as
the reason for which the OUT OF ORDER state has been entered).
312 / 320
Table 8 shows the definitions of TLV 59 for the AN faults (9100 BTS only). EVAD
indicates the faultcondition: 1 = Eventtype (EV), 0 = Appearance/Disappearance
type (AD). AD indicates the Appearance/Disappearance state; 1 = Appearance
(ON), 0 = Disappearance (OFF).
ALATYP
ALAN
EVAD
AD
CLKI clock failure
LNA failure
0
AD
LNA 1 partial failure
AD
LNA 2 partial failure
AD
LNA 1 total failure
AD
LNA 2 total failure
AD
VSWR circuitry failure
AD
CLKI frame failure
Antenna VSWR failure

0
AD
AN1_VSWR1_AL
AD
AN2_VSWR1_AL
AD
AN1_VSWR2_AL
AD
AN2_VSWR2_AL
14
AD
15
AD
HW failure
16
AD
SW failure
17
AD
Configuration failure
18
AD
19
AD
Downloading failure
20
Recoverable failure
0
EV
10
EV
Watchdog reset
Table 8: TLV59 for AN faults of 9100 BTS
313 / 320
Table 9 shows the definitions of TLV 59 for the TRANS&CLOCK faults

(9100 BTS only). EVAD indicates the faultcondition: 1 = Eventtype
(EV), 0 = Appearance/Disappearance type (AD). AD indicates the
Appearance/Disappearance state; 1 = Appearance (ON), 0 = Disappearance
(OFF).
ALATYP
ALAN
EVAD

Internal CLOCK failure
AD
FN input from master lost
AD
Frame signal input from master lost
AD
Reference clock input from master lost
AD
PCM synchronization unusable
AD
GPS synchronization lost
AD
Oven warm up alarm
14
AD
16
AD
SW failure
18
AD
19
AD
Downloading failure
20
Recoverable failure
0
EV
10
EV
Watchdog reset
25
TRANS&CLOCK fatal failure (1)

1
AD
HW failure
AD
Internal Clock failure
Table 9: TLV59 for TRANS&CLOCK faults of 9100 BTS

(1) As this alarm is fatal for the module, no alarm disappearance indication is
supplied. The alarm disappearance is detected on Alarm In Force List report.
314 / 320
10.2.4 TLV61 Coding

The TLV61 byte definitions are shown in Table 10 .
Bytes
Description
Element Identifier (=61)
1 or 2
Length (2 bytes if length > 127 (1)
Board Identification
Result type
Variable
Results (maximum length is 40 bytes).
Table 10: TLV61 Bytes

(1) For TRE, only one byte is forseen, because the length of the data is <
127 bytes.
TLV61, even if indicated, may not appear in an alarm message. Internal FU
problems, such as a blocked internal bus or a hardware fault, can prevent the
FU controller from receiving it. Several TLV61s can be sent.
* The boards (CDCC, CECC, ...) are numbered as in the rack, starting from the
left hand side (Mark I only).
The definition of the Board Identification bytes for 9100 BTS is shown in Table
11 . A bit set to 1 identifies the board at the origin of the fault detection.
Bit Number
TRE (1)
ANX/ANC
TRANS&CLOCK
(9100 BTS only)
ENCT
CLOCK
DEC
VSWR
TRANS
DEM0
LNA
DEM1
MBED
CUL
SCP
Microprocessor
Table 11: TLV61 Board Identification Bytes for 9100 BTS

(1) The bit positions are fixed by the Host interface within the TRE.
315 / 320
10.2.5 TLV82 Coding

TLV82 provides OMU system automatic test results. The TLV82 byte definitions
are shown in Table 12 .
Bytes
Description - Watchdog Reset
Element identifier ( = 82)
Length ( = 168)
Failure description
0 = Unknown
2 = Bus error
Logic external to micro-processor reports

failure (e.g. handshake failure).
3 = Address error
Access to illegal address (e.g. odd

address for LONG variable), detected by
micro-processor.
4 = Illegal Instruction
5 = Zero Divide
6 = CHK, CHK2 Instruction
7 = cpTRAPcc, TRAPcc, TRAPV Instruction
8 = Privilege Violation
10 = Line 1010 Emulator
11 = Line 1111 Emulator
14 = Format Error
15 = Uninitialized Interrupt
24 = Spurious Interrupt
56 = Configuration Error
316 / 320
59 = MMU :
Branch to Write Violation Code (ATC).
60 = MMU :
Branch to Limit Violation Code.
61 = MMU :
Branch to Supervisor Violation Code.
62 = MMU :
Branch to Bus Error during Table Search

Code.
63 = MMU :
Branch to Page Fault or Invalid Descriptor

Code.
64 = MMU :
Branch to Write Violation Code.
Bytes
Description - Watchdog Reset

65 = Fatal Signal Error
Task name
Status register
User stack pointer
Interrupt stack pointer
Data register 0
Data register 1
Data register 2
Data register 3
Data register 4
Data register 5
Data register 6
Data register 7
Address register 0
Address register 1
Address register 2
Address register 3
Address register 4
Address register 5
Address register 6
92
Complete STACK Frame
Board Status Register (see relevant OMU HW Functional Description).
317 / 320
10.2.6 TLV83 Coding

Bytes
Description - Scenario Problems
Length ( = 16)
Taskname
The name of the task that triggered the autorestart/autoreset (ASCII coded).
SBL Id.
The SBL on which the scenario was running, where:
byte
1+
2
SBL type
byte
3
SBL number
byte
4
SBL sub-number
Internal Message Identifier

Used to identify the internal scenario.
External Reference Number.

Used to identify the external (Abis or MMI) scenario (0 = autonomous).
Scenario Message Identifier.

Used to identify the external or autonomous scenario.
Origin of Action
0
Operator command triggered from OMC-R.
Operator command triggered from BSC terminal.
Operator command triggered from BTS NEM.
Autonomous system action.
Unknown.
Failure Description.
Indicates the reason for an autoreset (i.e., the reason for returning to bootstrap). If a
second autoreset occurs during a download, then the first reason is maintained.
1
318 / 320
Three unsuccessful autorestarts.
Bytes
Description - Scenario Problems

2
No download after being in bootstrap for > 24 hours (sending BTS-OMU-STARTED).

This is the behaviour of the release 1 and 2 OMU PROM (and should be changed
with the next PROM release).
FF
No information (e.g. for restart due to internal scenario Time out).
(hex)
10.2.7 TLV84 Coding

Bytes
Description - Lack of Resources
Length ( = 69)
Taskname
Required Memory Region.
The name of the task that triggered the autorestart/autoreset

(ASCII coded).
The requested memory region.
Message buffer.
Memory allocation.
Memory re-allocation.
Required Memory Size.

The requested memory size in octets.
60
Stackinfo
Information taken directly from the stack:

Supervisor mode - the system stack
User mode - the stack of a particular task.
319 / 320
10.2.8 TLV120 Coding

Bytes
Description
Length ( = 3)
Hardware revision:
0 - Hardware 1 (serial test interface, volatile memory).
1 - Hardware 2 (parallel test interface, non-volatile memory).
RAM size - given as the number of 4 Mbyte blocks.
Flash EPROM:
0 - Not equipped or not accessible.
1 - Equipped.
10.2.9 TLV243 Coding

Bytes
Description
Length ( = 1)
BTS HW family (for the coding, see below).

G3
60
9100 BTS
320 / 320

BTS Alarm Dictionary PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BTS Alarm Dictionary PDF

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent GSM

BTS Alarm Dictionary

3BK 21625 AAAA PCZZA Ed.06

BLANK PAGE BREAK

BTS Alarm Dictionary

3BK 21625 AAAA PCZZA Ed.06

3BK 21625 AAAA PCZZA Ed.06

3BK 21625 AAAA PCZZA Ed.06

3BK 21625 AAAA PCZZA Ed.06

3BK 21625 AAAA PCZZA Ed.06

When a fault occurs, a number of alarms can be generated simultaneously.

3BK 21625 AAAA PCZZA Ed.06

This document is aimed at telecommunications operators responsible for

3BK 21625 AAAA PCZZA Ed.06

3BK 21625 AAAA PCZZA Ed.06

1.2 Relationships Between SBLs and MOs

1.2.1 SBL State to MO State Translation

Table 1: SBL state to MO state translation

3BK 21625 AAAA PCZZA Ed.06

1.2.2 State change commands translation

Disable with WTC

Table 2: OMC-R to LMT state change commands translation

1.2.3 Mapping of MO Perceived Severity to BSS Alarm Category

BSS Alarm Category

BSS Alarm Condition

3BK 21625 AAAA PCZZA Ed.06

1.3 9153 OMC-R Alarm Surveillance Information

1.3.1 Object Identification

3BK 21625 AAAA PCZZA Ed.06

1.3.2 Alarm Type

a problem with a procedure or process used to convey information from

degradation in the quality of service in the network.

a software or processing fault.

a problem in the enclosure containing the equipment.

Table 3: Event Types

a serious fault condition which requires immediate corrections. Example: a

a fault condition which requires urgent correction action. Example: severe

detection of a potential fault condition. Action should be taken to diagnose

Table 4: Alarm Severity Levels

3BK 21625 AAAA PCZZA Ed.06

1.4 LMT Alarm Messages

1.4.1 BTS LMT Alarm Message Parameters

1.4.1.1 Message Identity

1.4.1.2 Event Time

3BK 21625 AAAA PCZZA Ed.06

1.4.1.5 SBL States

1.4.1.6 Suspected RIT

3BK 21625 AAAA PCZZA Ed.06

1.4.1.7 Additional Information

3BK 21625 AAAA PCZZA Ed.06

1.5 BTS Alarm Information

1.5.1 Alarm Definition

1.5.1.1 specific Problems

1.5.1.3 probable Cause

1.5.1.4 perceived Severity

3BK 21625 AAAA PCZZA Ed.06

Warning: indicates a potential or impending fault, before any significant

1.5.2 Alarm Description

1.5.2.2 Alarm Description

1.5.2.3 Impact on System

1.5.2.4 Corrective Actions

3BK 21625 AAAA PCZZA Ed.06

Start field with alarm number