BTS Alarm Dictionary

Alcatel-Lucent GSM
BTS Alarm Dictionary
BTS Document Reference Guide Release B11
3BK 21625 AAAA PCZZA Ed.06
BLANK PAGE BREAK
Status Short title
RELEASED 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 [9,2] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 7.4 [9,3] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 7.5 [9,4] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
3 / 320
Contents
7.6 [9,5] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.7 [9,6] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.8 [9,7] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.9 [9,8] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.10 [9,9] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.11 [9,10] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.12 [9,11] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.13 [9,12] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.14 [9,13] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.15 [9,14] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.16 [9,15] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.17 [9,16] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.18 [9,17] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.19 [9,18] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.20 [9,19] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.21 [9,20] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.22 [9,21] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.23 [9,22] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.24 [9,23] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.25 [9,24] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.26 [9,25] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.27 [9,26] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.28 [9,27] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.29 [9,28] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.30 [9,29] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.31 [9,30] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.32 [9,31] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.33 [9,32] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.34 [9,33] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.35 [9,34] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.36 [9,35] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.37 [9,36] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.38 [9,37] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.39 [9,38] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.40 [9,39] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.41 [9,40] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.42 [9,41] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.43 [9,42] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.44 [9,43] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.45 [9,44] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.46 [9,45] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.47 [9,46] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.48 [9,47] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.49 [9,48] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.50 [9,49] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.51 [9,50] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.52 [9,51] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.53 [9,52] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.54 [9,53] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.55 [9,54] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.56 [9,55] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.57 [9,56] EXT-ALARM for 9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
4 / 320
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: MO administrative state Locked Unlocked Unlocked Unlocked Unlocked Unlocked Unlocked Locked Shutting down Unlocked MO operational state No change Enabled Enabled Disabled Disabled Disabled Disabled No change Enabled No change
SBL state OPR IT FIT FLT EF FOS SOS UT WTC MSD/MSA
MO availability state {} {} Degraded Failed Dependency/failed Off-line/failed Dependency Under test {} {}
MO control state {} {} {} {} {} {} {} {} {} 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 Lock Unlock Shutdown Test Verify Reset Restart LMT Disable Init Disable with WTC Test Verify Reset 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 Cleared Critical Major Minor Warning Indeterminate BSS Alarm Category VPMA, SA PMA DMA MI all categories BSS Alarm Condition End Begin Begin Begin Begin 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 Communication Indicates.... a problem with a procedure or process used to convey information from one point to another in the network. degradation in the quality of service in the network. a software or processing fault. an equipment fault. a problem in the enclosure containing the equipment.
Quality of Service Processing Error Equipment Environmental Table 3: Event Types
Severity Level Critical
Indicates... a serious fault condition which requires immediate corrections. Example: a managed object goes out of service. a fault condition which requires urgent correction action. Example: severe degradation in the operation of a managed object. a fault condition which does not affect service but corrective action should be taken to avoid a more serious fault. detection of a potential fault condition. Action should be taken to diagnose and correct the problem to avoid a more serious fault condition. the severity level cannot be defined by the resource which raised the alarm. the alarm was cleared by the resource which raised the alarm.
Major
Minor
Warning
Indeterminate Cleared 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
[5,11] POWERSUPPLYU
Start field with alarm number and alarm name
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 persists?
Alarm solved
yes
Onsite
9100 BTS: Replace PM08, which LED is off or red *
Onsite
Onsite
Onsite
OR
OR
OR
Onsite action fields
Decision field
Power supply operational?
yes
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 event Type probable Cause perceived Severity Alarm Description Alarm Number MCL-FATAL-AL Equipment Equipment Malfunction Major (PMA) Fatal internal alarm on the Clock Unit. 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 Loss Degradation BSS X(no red.) Cell(s) X(no red.) Signaling X(no red.) Calls 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
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
Onsite
Switch off Battery Backup Switch and OR Main Power switch in Side Support Cabinet
Onsite
Switch off mains power fuse for tower mounted BTS
OR
Onsite
After 30 s repower the BTS
Onsite
BTS operational? no Replace BTS A910
yes Alarm solved BTS operational? yes Alarm solved
Figure 3: MCL-FATAL-AL: BTS 9110/9110-E Corrective Actions
24 / 320
2.2 [1,12] CLOCK-FAULT

specific Problems event Type probable Cause perceived Severity Alarm Description CLOCK-FAULT Equipment Timing Problem Major (PMA), Minor (DMA) 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 Loss Degradation BSS X(no red.) Cell(s) X(no red.) Signaling X(no red.) Calls 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
Figure 4: CLOCK-FAULT: BTS 9100 Corrective Actions
26 / 320

[1,12] CLOCKFAULT
Reset Function BTS
Clock operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
yes Alarm solved BTS operational? yes
Alarm solved
Figure 5: CLOCK-FAULT: BTS 9110/9110-E Corrective Actions
27 / 320
2.3 [1,31] MCL-XCLK

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number MCL-XCLK Equipment Equipment Malfunction Major (PMA) An error has been detected in the input of the External Reference Clock. 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 Loss Degradation BSS X(no red.) Cell(s) X(no red.) Signaling X(no red.) Calls X(no red.) -
28 / 320

[1,31] MCLXCLK
Alarm on feeding clock unit of master BTS events?
no
Reset Function BTS
yes yes Alarm solved
Solve that alarm(s) first
Clock operational?
no Onsite Check cables/connectors between clock unit on master BTS and reporting clock unit
Onsite
Replace SUMP, SUMA
Clock operational?
yes
Alarm solved
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
yes Solve that alarm(s) first Clock operational? no Check cables/connectors between clock unit on master BTS and reporting clock unit
OR Onsite
Switch off Battery Backup Switch and Main Power switch in Side Support Cabinet
yes Alarm solved
OR Onsite
Onsite
Onsite
Replace BTS A910 no BTS operational?
yes Alarm solved yes BTS operational? Alarm solved
Figure 7: MCL-XCLK: BTS 9110/9110-E Corrective Actions
30 / 320
2.4 [1,234] IOM-DISCONNECTION

specific Problems event Type probable Cause perceived Severity Alarm Description IOM-DISCONNECTION Equipment Equipment Malfunction Minor (DMA) There is a loss of communication with the clock on the IOM bus.
Telecom functions are not affected. Impact Loss Degradation BSS Cell(s) Signaling Calls -
2.4.1 Corrective Actions

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

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number HW-DEGRADED Equipment Equipment Malfunction Minor (DMA), Warning (MI) The processing of the clock is degraded. 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.
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? no
yes
Solve this alarms
Alarm persists?
no
yes
WAIT 20 minutes (Clock synchronisation ongoing)
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?
no
no WAIT 20 minutes (Clock synchronisation ongoing)
yes
no Alarm persists?
yes
Check GPS equipment
no Alarm persists?
yes
Reset BTS
Alarm persists?
no
yes
Alarm solved
Alarm persists?
no
yes
no Alarm persists?
yes
Replace SUMx
no Alarm persists?
yes
no Alarm persists?
yes
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
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?
no
no WAIT 20 minutes (Clock synchronisation ongoing)
yes
no Alarm persists?
yes
Reset BTS
Alarm persists?
no
yes
Alarm persists?
no
Alarm solved
yes
no Alarm persists?
yes
Replace 9110 Micro BTS / 9110E Micro BTS
no Alarm persists?
yes
no Alarm persists?
yes
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? no
yes
Solve this alarms
Alarm persists?
no
yes
WAIT 20 minutes (Clock synchronisation ongoing)
no Alarm persists?
yes
Check GPS equipment
no Alarm persists?
yes
Reset BTS
Alarm persists?
no
yes
Alarm solved
Alarm persists?
no
yes
no Alarm persists?
yes
no Alarm persists?
yes
no Alarm persists?
yes
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 event Type probable Cause perceived Severity Alarm Description Alarm Number RESTART Processing Error Application Subsystem Failure Warning (MI) The TRANSandCLOCK has performed a successful autorestart. 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.
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
Figure 13: RESTART: BTS 9100 Corrective Actions
39 / 320

[1,248] RESTART
Reset Function BTS
Clock operational?
yes
Alarm is reported very often on one board?
no
Alarm solved
no
yes
Onsite
Onsite
Onsite
OR
Switch off Battery Switch off mains power Backup Switch and OR fuse for tower mounted Main Power switch in BTS Side Support Cabinet
Onsite
Onsite
Clock operational? no Replace BTS A910 BTS operational? yes Alarm solved
yes Alarm solved
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 event Type probable Cause perceived Severity Alarm Description LOSS OF TWIN CONFIGURATION Processing Error softwareProgramAbnomallyTerminated Warning (MI) 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.
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?
Figure 15: LOSS OF TWIN CONFIGURATION Corrective Actions
43 / 320
3.2 [2,247] RESET

specific Problems event Type probable Cause perceived Severity Alarm Description RESET Processing Error softwareProgramAbnomallyTerminated Warning (MI) 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.
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
9100: Replace SUMP, SUMA, SUMX
Onsite
9110/9110E Micro BTS: Replace 9110/9110E Micro BTS
OR
OMU operational?
yes
Alarm solved
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
45 / 320

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

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

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

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

specific Problems event Type probable Cause perceived Severity Alarm Description RESTART Processing Error Application Subsystem Failure Warning (MI) 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.

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 event Type probable Cause perceived Severity SW-PROBLEM Processing Error software Program Abnormally Terminated Nbr 1...3:Major (PMA) Nbr 4, 5: Minor (DMA), Warning (MI) Alarm Description Alarm Number The software is corrupted or bad. 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.
If the CLLK is redundant on this BTS, the telecom functions are not affected. 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 Loss Degradation BSS X(no red.) Cell(s) X(no red.) Signaling X(no red.) Calls 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
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
Onsite
Onsite
OR
Onsite
Onsite
BTS operational? no Replace 9110 BTS
yes yes
Alarm solved
BTS operational?
Alarm solved
Figure 22: SW-PROBLEM (CLLK): BTS 9110/9110-E Corrective Actions
52 / 320
4.1.2 [3,11] SW-PROBLEM (TRE)

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number SW-PROBLEM Processing Error software Program Abnormally Terminated Major (PMA), Warning (MI) The software is corrupted or bad. 1 : An error is detected during the configuration with saved parameters in initialization state: saved parameters are corrupted and cannot be used for the auto-restart sequence. 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. Major (PMA) : The local recovery fails. Warning (MI) : The local recovery is successful. 3: A fatal exception occurred on SCP or a SCP, the software error is detected in another state than the operational state. Major (PMA) : The local recovery fails. Warning (MI) : The local recovery is successful. 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 Loss Degradation BSS X(no red.) Cell(s) X(no red.) #* Signaling X(no red.) Calls 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
no Onsite
Replace TRE
TRE operational?
yes
Alarm solved
Figure 23: SW-PROBLEM (TRE): BTS 9100 Corrective Actions
55 / 320

[3,11] SWPROBLEM (TRE)
yes Reset Function BTS BTS operational? Alarm solved
no yes Contact System Support
Alarm is reported from more than one BTS?
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
yes yes
Alarm solved
BTS operational?
Alarm solved
Figure 24: SW-PROBLEM (TRE): BTS 9110/9110-E Corrective Actions
56 / 320
4.1.3 [3,11] SW-PROBLEM (RA)

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number SW-PROBLEM Processing Error software Program Abnormally Terminated Minor (DMA), Warning (MI) The software is corrupted or bad. 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 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 Loss Degradation BSS Cell(s) Signaling X Calls X
57 / 320

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

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number TELECOM-CONFIG-FAIL Processing Error Configuration Or Customization Error Warning (MI) A Telecom Configuration Parameter error has been detected. 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 Loss Degradation BSS Cell(s) Signaling Calls -
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 event Type probable Cause perceived Severity Alarm Description Alarm Number WRONG-CONFIGURATION Processing Error Configuration Or Customization Error Major (PMA) The parameters are not consistent with the capacity of the equipment. 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.
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, calls are lost. (*) If the TRE supporting the BCCH is concerned and there is no BCCH redundancy, the complete cell is lost. (X). Impact Loss Degradation BSS X(no red.) Cell(s) X(no red.) #* Signaling X(no red.) Calls 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
Figure 27: WRONG-CONFIGURATION (TRE): Alarm Number 1, 2, 3, 6, Corrective Actions
62 / 320
4.3.1.2 Alarm Number 4, Corrective Actions

Other TRE alarms event? no Download the masterfile and the application file
yes
Replace the masterfile
Reset effected TCU
Alarm persists?
no
Alarm solved
Figure 28: WRONG-CONFIGURATION (TRE): Alarm Number 4, Corrective Actions
63 / 320

yes
no Compare CDM value with RSL rate
Reset effected TCU
Alarm persists?
no
Alarm solved
64 / 320
4.3.1.4 Alarm Number 7, 9, Corrective Actions

[3,14] WRONGCONFIGURATIO N (TRE)
yes
no Compare CDM value
Reset effected TCU
Alarm persists?
no
Alarm solved
Figure 30: WRONG-CONFIGURATION (TRE): Alarm Number 7, 9, Corrective Actions
65 / 320

yes
no Compare transmission settings
Introduce RSL/TCH mapping
Initialize TRE
Reset effected TCU
Alarm persists?
no
Alarm solved
66 / 320

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
67 / 320

Choose a lower bandwidth per MCTRE module.
Alarm persists?
no
Alarm solved

For Multicarrier modules 16 kb/s rate for RSL is not allowed. Correct the RSL rate.
Alarm persists?
no
Alarm solved
68 / 320

Choose the correct multicarrier class.
Alarm persists?
no
Alarm solved
69 / 320
4.3.2 [3,14] WRONG-CONFIGURATION (RA)

specific Problems event Type probable Cause perceived Severity WRONG-CONFIGURATION Processing Error Configuration Or Customization Error Nbr. 2: Major (PMA) Nbr. 4, 7, 10: Minor (DMA), Warning (MI) Alarm Description Alarm Number The parameters are not consistent with the capacity of the equipment. 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 Loss Degradation BSS Cell(s) Signaling X Calls X
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
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
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
Disable Antenna Hopping feature for the impacted sector
Insert TWIN TRE module
or
no Alarm persists? Alarm solved
yes
Figure 38: WRONG-CONFIGURATION (RA): Alarm Number 15, Corrective Action
73 / 320
4.3.3 [3,14] WRONG-CONFIGURATION (BTS)

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number WRONG-CONFIGURATION Processing Error Configuration Or Customization Error Minor (DMA), Warning (MI) The parameters are not consistent with the capacity of the equipment. 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 Loss Degradation BSS Cell(s) Signaling Calls -
74 / 320
4.3.3.1 Alarm Number 12, 14, Corrective Actions

[3,14] WRONGCONFIGURATION (BTS)
Correct parameter values according to BTS capability
Reset effected BTS
Alarm persists?
no
Alarm solved
Figure 39: WRONG-CONFIGURATION (BTS): Alarm Number 12, 14, Corrective Actions
75 / 320

[3,14] WRONGCONFIGURATION (BTS)
Place OML TS on Abis 1
Reset effected BTS
Alarm persists?
no
Alarm solved
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 event Type probable Cause perceived Severity CONFIG-FAIL Processing Error Configuration Or Customization Error Nbr 1: Major (PMA)) Nbr 3, 4: Minor (DMA), Warning (MI) Alarm Description Alarm Number There is a scenario-failure for TRANS&CLOCK. 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.
If the CLLK is redundant on this BTS, the telecom functions are not affected. 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 Loss Degradation BSS X(no red.) Cell(s) X(no red.) Signaling X(no red.) Calls X(no red.) -
77 / 320

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

[3,246] CONFIGFAIL (CLLK)
Check validity of parameters
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
yes Alarm solved yes BTS operational? Alarm solved
Figure 42: CONFIG-FAIL (CLLK): BTS 9110/9110-E Corrective Actions
79 / 320
4.4.2 [3,246] CONFIG-FAIL (RA)

specific Problems event Type probable Cause perceived Severity CONFIG-FAIL Processing Error Configuration Or Customization Error Nbr 2: Major (PMA) Nbr 1: Minor (DMA) Alarm Description Alarm Number There is a scenario-failure for ANX or RA. 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.
80 / 320

[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
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
Onsite
Onsite
OR
Onsite
Onsite
Figure 44: CONFIG-FAIL (RA): BTS 9110/9110-E Corrective Actions
82 / 320
4.4.3 [3,246] CONFIG-FAIL (TRE)

specific Problems event Type probable Cause perceived Severity Alarm Description CONFIG-FAIL Processing Error Configuration Or Customization Error Major (PMA) 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.
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, calls are lost. (*). If the TRE supporting the BCCH is concerned and there is no BCCH redundancy, the complete cell is lost. (X). Impact Loss Degradation BSS X(no red.) Cell(s) X(no red.) #* Signaling X(no red.) Calls X(no red.)#* -
83 / 320

[3,246] CONFIGFAIL (TRE)
Lock Function TRE
Unlock Function TRE
TRE operational?
yes
Alarm solved
no
Onsite
Replace TRE
TRE operational?
yes
Alarm solved
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
Onsite
Onsite
OR
Onsite
Onsite
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 event Type probable Cause perceived Severity Alarm Description FAN-ALARM Environmental Heating Or Ventilation Or Cooling System Problem Minor (PMA) 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). 20 : FAN alarm for 9110-E BTS (Slave 2). 11 : FAN alarm for 9110-E BTS (Slave 11). 12 : FAN alarm for 9110-E BTS (Slave 12). 21 : FAN alarm for 9110-E BTS (Slave 21). 22 : FAN alarm for 9110-E BTS (Slave 22).

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

specific Problems event Type probable Cause perceived Severity Alarm Description POWER-SUPPLY-U Equipment PowerProblem Critical (VPMA), Warning (MI) 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 Loss Degradation BSS #X Cell(s) X # Signaling X Calls #X -
89 / 320

[5,11] POWERSUPPLYU
Onsite
Check Power Supplies are switched on
Onsite
no Alarm persists?
Alarm solved
yes
Onsite
Onsite
Onsite
Onsite
OR
OR
OR
yes
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 event Type probable Cause perceived Severity Alarm Description POWER-SUPPLY-NU Equipment PowerProblem Major (PMA) 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.
91 / 320

[5,12] POWERSUPPLYNU
Onsite
Onsite
no Alarm persists?
Alarm solved
yes
Onsite
Onsite
Onsite
Onsite
OR
OR
OR
yes
Alarm solved
* If RIT location is A,0,0, the RIT is located in 9100 BTS COMI/CODI outdoor side compartment
Figure 49: POWER-SUPPLY-NU: Corrective Actions
92 / 320
5.4 [5,13] CONTROL-UNIT-AL

specific Problems event Type probable Cause perceived Severity CONTROL-UNIT-AL Equipment PowerProblem Nbr 2: Critical (VPMA), Warning (MI) Nbr 1: Major (PMA), Warning (MI) Alarm Description Alarm Number There is a failure of the control unit that supervises the power modules. 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 Loss Degradation BSS X Cell(s) X Signaling X Calls X -
93 / 320

[5,13] CONTROLUNITAL
Onsite
Battery OK?
no
Onsite
A9100 BCU1/BCU2, PM12: Replace BU41/BU100
Onsite
A9100: Replace BATS
Onsite
A9100: Replace BU101
yes
OR
OR
Onsite
yes
Check cables/connectors to control unit and EACB
Control Unit operational?
Alarm solved
Onsite
A9100: Replace BCU1, which LED is off or red *
Onsite
A9100: Replace BCU2, which LED is off or red *
Onsite
A9100: Replace PM12, which LED is off or red *
OR
OR
yes
Alarm solved
* If RIT location is A,0,0, the RIT is located in A9100 COMI/CODI outdoor side compartment
Figure 50: CONTROL-UNIT-AL: Corrective Actions
94 / 320
95 / 320
5.5 [5,20] MAINS-AL

specific Problems event Type probable Cause perceived Severity Alarm Description MAINS-AL Equipment PowerProblem Critical (VPMA), Warning (MI) 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 Loss Degradation BSS #X Cell(s) X # Signaling X Calls #X -
96 / 320

[5,20] MAINSAL
Onsite
Check cables/connectors to 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
Onsite OR
Onsite
Onsite
OR
OR
yes
Alarm solved
Figure 51: MAINS-AL: Corrective Actions
97 / 320
5.6 [5,23] POWER-SHUTDOWN

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number POWER-SHUTDOWN Equipment PowerProblem Major (PMA) The shutdown is due to a mains power failure. 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).
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 Loss Degradation BSS X(no red.) Cell(s) X(no red.) #* Signaling X(no red.) Calls X(no red.)#* -
98 / 320

[5,23] POWERSHUTDOWN
Onsite
Check cables/connectors to 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
Onsite OR
Onsite
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
Figure 53: POWER-SHUTDOWN: Alarm Number 2 Corrective Actions
100 / 320
5.7 [5,24] SUBRACK-POWER

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

[5,24] SUBRACKPOWER
Onsite
Check cables/connectors to subrack

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

5.8.1 [5,31] TEMPERATURE-WARNING (BTS)
specific Problems event Type probable Cause perceived Severity Alarm Description TEMPERATURE-WARNING Environmental Temperature Unacceptable Major (PMA), Warning (MI) This is a temperature warning. The temperature control of the hottest TRE in the BTS has reached the low threshold value.
103 / 320

Required tools and materials : Thermometer Replacement and cleaning tools, see appropriate replacement procedure.
[5,31] TEMPERATUREWARNING (BTS)
yes Fan alarm events?
no Onsite
Check the ambient temperature.
Onsite
Is ambient temperature out of permitted limits? no Onsite Check and clean heat exchanger air intake
yes
The ambient temperature must be reduced.
BTS Temperature OK?
yes
Alarm solved
BTS Temperature OK?
yes
Alarm solved
Figure 55: TEMPERATURE-WARNING (BTS): Corrective Actions
104 / 320
5.8.2 [5,31] TEMPERATURE-WARNING (TRE)

specific Problems event Type probable Cause perceived Severity Alarm Description TEMPERATURE-WARNING Environmental Temperature Unacceptable Major (PMA), Warning (MI) This is a temperature warning. A MTRE inside the BTS has reached a temperature which is close to the shut off temperature.
105 / 320

[5,31] TEMPERATUREWARNING (TRE)
Fan alarm events?
yes
no Onsite Check the ambient temperature.
Onsite
Is ambient temperature out of permitted limits? no
yes
TRE Temperature OK? no Contact System Support
yes
Alarm solved
Onsite
Optional Fan Module available? no
yes
Check and clean optional Fan Module
TRE Temperature OK?
yes
Alarm solved
no
Onsite
Add optional Fan Module
TRE Temperature OK? no Contact System Support
yes
Alarm solved
Figure 56: TEMPERATURE-WARNING (TRE): Corrective Actions
106 / 320
5.9 [5,32] FATAL TEMPERATURE

specific Problems event Type probable Cause perceived Severity Alarm Description FATAL TEMPERATURE Environmental Temperature Unacceptable Major (PMA) 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.
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, calls are lost. (*) If the TRE supporting the BCCH is concerned and there is no BCCH redundancy, the complete cell is lost. (X). Impact Loss Degradation BSS X(no red.) Cell(s) X(no red.) #* Signaling X(no red.) Calls X(no red.)#* -
107 / 320

[5,32] FATAL TEMPERATURE
yes Fan alarm events?
no Onsite
Check the ambient temperature.
Is ambient temperature out of permitted limits? no Onsite Check and clean heat exchanger air intake
Onsite
yes
TRE Temperature OK?
yes
Alarm solved
TRE Temperature OK?
yes
Alarm solved
Figure 57: FATAL TEMPERATURE: Corrective Actions
108 / 320

5.10.1 [5,237] HW-DEGRADED (BTS)
specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number HW-DEGRADED Equipment Equipment Malfunction Major (PMA), Warning (MI) A problem has been detected on the XIOB/OUTC input ports. 6 : DC/DC converter 1 failure. 7 : DC/DC converter 2 failure.
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
Figure 58: HW-DEGRADED (BTS): Corrective Actions
110 / 320
5.10.2 [5,237] HW-DEGRADED (EACB)

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number HW-DEGRADED Equipment Equipment Malfunction Major (PMA) A problem has been detected on the input ports 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.
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
A9100: Replace XIOB
Onsite
For RIT OUTC replacement contact system support
OR
EACB operational?
yes
Alarm solved
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
yes
Alarm solved
no
Replace MicroBTS
yes
Alarm solved
Figure 60: HW-DEGRADED (EACB): BTS 9110/9110-E Corrective Actions
113 / 320
5.10.3 [5,237] HW-DEGRADED (RA)

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number HW-DEGRADED Equipment Equipment Malfunction Major (PMA) A problem has been detected on the input ports 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
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
Figure 61: HW-DEGRADED (RA): Corrective Actions
115 / 320
5.10.4 [5,237] HW-DEGRADED (CCF)

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number HW-DEGRADED Equipment Equipment Malfunction Minor (DMA), Warning (MI) An fan control for front or back row is faulty. 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.

[5,237] HWDEGRADED (CCF)
Onsite
Onsite
Replace FACB
OR
Replace FANU
Fan operational?
yes
Alarm solved
no
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 event Type probable Cause perceived Severity Alarm Description Alarm Number HW-FAILURE Equipment Equipment Malfunction Major (PMA) A hardware failure has been detected. 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.
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
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?
yes
Alarm solved
no
Onsite
Insert appropriate module
EACB operational?
yes
Figure 64: HW-FAILURE (EACB): Alarm Number 3 Corrective Actions
119 / 320
5.11.2 [5,239] HW-FAILURE (CCF)

specific Problems event Type probable Cause perceived Severity Alarm Description HW-FAILURE Equipment Equipment Malfunction Major (PMA) 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.
120 / 320

[5,239] HWFAILURE (CCF)
SUBRACK POWER alarm(s) events?
yes
Solve that alarm(s) first.
FAN operational?
yes
Alarm solved
no
Check for previously reported alarms on this function (SBL CCF). Solve that alarm(s).
FAN operational?
yes
Alarm solved
no
Onsite
Replace FACB
FAN operational?
yes
Alarm solved
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 event Type probable Cause perceived Severity Alarm Description RESYNCH Processing Error Configuration Or Customization Error Warning (MI) 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.

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

specific Problems event Type probable Cause perceived Severity Alarm Description IGNORE EQUIPMENT OVER 12 TRE Processing Error Configuration Or Customization Error Warning (MI) 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.

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

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number TOO MANY PLUGGED MODULES Equipment Configuration Or Customization Error Warning (MI) The installed HW configuration exceeds the power dissipation limits. 1 : Too many TREs are plugged in the rack type.
There is no disturbance of the telecom applications. Impact Loss Degradation BSS Cell(s) Signaling Calls -

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

specific Problems event Type probable Cause perceived Severity Alarm Description HW-RESYNCH Processing Error Configuration Or Customization Error Warning (MI) 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.

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

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number BCB-LINK Equipment Equipment Malfunction Major (PMA), Warning (MI) There is no communication on IOM link. 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 Loss Degradation BSS Cell(s) Signaling Calls -
128 / 320

[8,30] BCBLINK
Lock Function BTS
Unlock Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Check BCB bus for shortcuts and interruptions
Onsite
Replace SUMP/SUMA
BTS operational?
yes
Alarm solved
Figure 68: BCB-LINK: BTS 9100 Corrective Actions
129 / 320

[8,30] BCBLINK
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
Figure 69: BCB-LINK: BTS 9110/9110-E Corrective Actions
130 / 320
6.6 [8,31] IOM-LINK

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

[8,31] IOMLINK
Lock Function BTS
Unlock Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Check BSII bus for shortcuts and interruptions
Onsite
Replace SUMP/SUMA
BTS operational?
yes
Alarm solved
Figure 70: IOM-LINK: BTS 9100 Corrective Actions
132 / 320

[8,31] IOMLINK
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
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 event Type probable Cause perceived Severity Alarm Description MODULE-INSERTED Equipment Replaceable Unit Problem Warning (MI) The TRE is not connected to any ANX/ANC via RF cable.

134 / 320
[8,32] MODULEINSERTED (BTS)
Lock Function BTS
Unlock Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Check BTS status
Onsite
Check RF cables and connectors to TRE and ANX/ANY/ANC visually and electrcally. Replace cable, if required.
If the module has been extracted previously and the same module inserted (without operator action), the connection of the module could be faulty
BTS operational?
yes
Alarm solved
no
Onsite
Replace ANX,ANY,ANC
Onsite
OR
Replace TRE
BTS operational?
yes
Alarm solved
Figure 72: MODULE-INSERTED: BTS 9100 Corrective Actions

135 / 320
[8,32] MODULEINSERTED
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
yes yes
Alarm solved
BTS operational?
Alarm solved
Figure 73: MODULE-INSERTED: BTS 9110/9110-E Corrective Actions
6.7.2 [8,32] MODULE-INSERTED (RA)

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

137 / 320
[8,32] MODULEINSERTED (RA)
Lock Function BTS
Unlock Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
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.
If the module has been extracted previously and the same module inserted (without operator action), the connection of the module could be faulty
BTS operational?
yes
Alarm solved
no
Onsite
Replace ANX,ANY,ANC
Onsite
OR
Replace TRE
BTS operational?
yes
Alarm solved
Figure 74: MODULE-INSERTED: BTS 9100 Corrective Actions

138 / 320
[8,32] MODULEINSERTED
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
yes yes
Alarm solved
BTS operational?
Alarm solved
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 event Type probable Cause perceived Severity Alarm Description Alarm Number RESET Processing Error Software Error Warning (MI) The (power up) reset of the BTS has been performed successfully. 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 Loss Degradation BSS Cell(s) Signaling Calls -

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

specific Problems event Type probable Cause perceived Severity Alarm Description RESTART Equipment Software Error Warning (MI) The BTS restarts successfully.
After the previous call interrupt, the BTS is now in service. Impact Loss Degradation BSS Cell(s) Signaling Calls -

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 event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) 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 Loss Degradation BSS Cell(s) X# Signaling Calls X#
144 / 320

[9,1...50] EXTALARM
Onsite
Alarm was sent without cause? no
yes
Check sensor connection to BTS.
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? yes Contact System Support
no
Alarm solved
Figure 76: EXT-ALARM [9,1...56] : Corrective Actions
145 / 320
7.2 [9,1] EXT-ALARM (Default)

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Critical (VPMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. 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 Loss Degradation BSS Cell(s) Signaling Calls -
146 / 320

[9,1] EXTALARM
Onsite
yes
Onsite
Trigger customer specific action according to power supply rectifier alarm
Onsite
no
Alarm solved
Figure 77: [9,1] EXT-ALARM: Default Corrective Actions
147 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Critical (VPMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. 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 Loss Degradation BSS Cell(s) Signaling Calls -
148 / 320

[9,2] EXTALARM
Onsite
yes
Onsite Onsite
Check AC power supply fuses, breakers, cabl%s, connectors

Onsite
Onsite
Ensure BTS AC power supply
no
Alarm solved
no
Alarm solved
149 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. 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 Loss Degradation BSS Cell(s) Signaling Calls -
150 / 320

[9,3] EXTALARM
Onsite
yes
Onsite
Onsite
no
Alarm solved
151 / 320

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

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. 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.
153 / 320

[9,4] EXTALARM
Onsite
yes
Onsite
Trigger customer specific action according to an open door or window alarm when allowance key is used onsite.
Onsite
no
Alarm solved
154 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Critical (VPMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. 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 Loss Degradation BSS Cell(s) Signaling Calls -
155 / 320

[9,5] EXTALARM
Onsite
yes
Onsite
Onsite
no
Alarm solved
156 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Major (PMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: Water break-in by detection of water detection float switch.
157 / 320

[9,6] EXTALARM
Onsite
yes
Onsite
Trigger customer specific action according to a water breakin alarm.
Onsite
no
Alarm solved
158 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Major (PMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: There is a heating/ventilation/cooling system problem. At least one fan in the heat exchanger unit is faulty.
159 / 320

[9,7] EXTALARM
Onsite
Onsite
Onsite
A9100: Replace HEAT2
Onsite
External alarm persists?
no
Alarm solved
no
yes
yes
160 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: The temperature in the equipment rack reached 35 0 C.
161 / 320

[9,8] EXTALARM
Onsite
yes
Onsite
Trigger customer specific action according to a hot equipment room alarm (e.g. check air condition unit)
Onsite
no
Alarm solved
162 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: The temperature in the equipment room reached 40 0 C.
163 / 320

[9,9] EXTALARM
Onsite
yes
Onsite
Trigger customer specific action according to a hot equipment room alarm (e.g. check air condition unit)
Onsite
no
Alarm solved
164 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: The antenna mast warning light is faulty.
165 / 320

[9,10] EXTALARM
Onsite

Onsite
yes
Onsite
Replace antenna mast warning light
Onsite
no
Alarm solved
no
Alarm solved
166 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Major (PMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. 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 Loss Degradation BSS Cell(s) Signaling Calls -
167 / 320

[9,11] EXTALARM
Onsite
Onsite
Onsite
Power supply alarm events? no
yes
Solve power supply alarm first
Onsite
no Ensure BTS AC power supply External alarm persists? Alarm solved
Onsite
Check battery
Onsite
Onsite
Onsite
Onsite
A9100: Replace BU41
OR
OR
A9100: Replace BATS
OR
no Alarm solved
168 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. 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 Loss Degradation BSS Cell(s) Signaling Calls -
169 / 320

[9,12] EXTALARM
Onsite
Alarm was sent without cause? yes Check sensor connection to BTS.
no Onsite Check FAN fuses in COBO, replace fuses if required.
Onsite
Onsite Onsite
Replace FAn Cassette. Check sensor function, replace sensor if required.
no
Alarm solved External alarm persists? no Alarm solved
yes
Onsite
Replace Top of Cover with FAN.
no
Alarm solved
170 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: The antenna mast warning light is faulty. BTS 9110/9110-E: This is a PMS alarm for the micro-BTS slave1, equipment not in vertical position.
171 / 320

[9,13] EXTALARM
Onsite

Onsite
yes
Onsite
Onsite
no
Alarm solved
no
Alarm solved
Figure 90: [9,13] EXT-ALARM: 9100 Default Corrective Actions
172 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: The antenna mast warning light is faulty.
173 / 320

[9,14] EXTALARM
Onsite

Onsite
yes
Onsite
Onsite
no
Alarm solved
no
Alarm solved
Figure 91: [9,14] EXT-ALARM: BTS 9100 Default Corrective Actions
174 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: This is a door alarm.
175 / 320

[9,15] EXTALARM
Onsite
yes
Onsite
Trigger customer specific action according to open door alarm
Onsite
no
Alarm solved
176 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Critical (VPMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: This is a power supply inverter alarm.
177 / 320

[9,16] EXTALARM
Onsite
yes
Onsite
Trigger customer specific action according to power supply inverter alarm
Onsite
no
Alarm solved
178 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. 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 Loss Degradation BSS Cell(s) X# Signaling Calls X#
179 / 320

[9,17] EXTALARM
Onsite
Onsite Onsite
Check TRX to antenna cables visually and electrically Check cabling to sensor, replace cabling if required.
Onsite
Onsite
Check antenna
Onsite
Replace MAB of TRX1
Alarm solved
180 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: This is a fatal REK alarm on TRX2, MAB detects a VSWR problem.
181 / 320

[9,18] EXTALARM
Onsite
Onsite Onsite
Onsite
Onsite
Check antenna
Onsite
Replace MAB of TRX2
Alarm solved
182 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: This is a fatal REK alarm (if installed) on TRX3, MAB detects a VSWR problem.
183 / 320

[9,19] EXTALARM
Onsite
Onsite Onsite
Onsite
Onsite
Check antenna
Onsite
Replace MAB of TRX3
Alarm solved
184 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: This is a fatal REK alarm (if installed) on TRX4, MAB detects a VSWR problem. BTS 9110/9110-E: This is a door alarm for the micro-BTS slave 2, COBOX cover open.
185 / 320

[9,20] EXTALARM
Onsite
Onsite Onsite
Onsite
Onsite
Check antenna
Onsite
Replace MAB of TRX4
Alarm solved
186 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: This is a fatal REK alarm (if installed) on TRX5, MAB detects a VSWR problem. 9110/9110-E: This is a PMS alarm for the micro-BTS slave2, equipment not in vertical position.
187 / 320

[9,21] EXTALARM
Onsite
Onsite Onsite
Onsite
Onsite
Check antenna
Onsite
Replace MAB of TRX5
Alarm solved
188 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: This is a fatal REK alarm (if installed) on TRX6, MAB detects a VSWR problem.
189 / 320

[9,22] EXTALARM
Onsite
Onsite Onsite
Onsite
Onsite
Check antenna
Onsite
Replace MAB of TRX6
Alarm solved
190 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. 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 Loss Degradation BSS Cell(s) X# Signaling Calls X#
191 / 320

[9,23] EXTALARM
Onsite
Onsite
Onsite
Check all PDUs for flashing TRX MAB LEDs
Onsite
Onsite
Replace the MAB corresponding to the lashing TRX MAB LED External alarm persists? no Alarm solved
Alarm solved
192 / 320

specific Problems event Type probable Cause perceived Severity Alarm Description EXT-ALARM Equipment Indeterminate Minor (DMA) To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9100: There is a heating/ventilation/cooling system problem. At least one fan in the heat exchanger unit is faulty.
193 / 320

[9,7] EXTALARM
Onsite
Onsite
Onsite
A9100: Replace HEAT2
Onsite
no
Alarm solved
no
yes
yes
Figure 101: [9,24] EXT-ALARM: 9100 Default Corrective Actions
194 / 320
7.26 [9,25] EXT-ALARM for 9110-E (Default)

Specific Problems Event Type Probable Cause Perceived Severity EXT-ALARM Equipment Indeterminate 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.

195 / 320

Specific Problems Event Type Probable Cause Perceived Severity EXT-ALARM Equipment Indeterminate 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 Event Type Probable Cause Perceived Severity EXT-ALARM Equipment Indeterminate 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 To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9110-E: This is a door alarm for the micro-BTS slave 11, COBOX cover open.
196 / 320

Specific Problems Event Type Probable Cause Perceived Severity EXT-ALARM Equipment Indeterminate 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 To simplify the external alarms declaration, default values are provided with an alarm translation table. 9110-E: This is a PMS alarm for the micro-BTS slave11, equipment not in vertical position.

197 / 320


Specific Problems Event Type Probable Cause Perceived Severity EXT-ALARM Equipment Indeterminate 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.
198 / 320


199 / 320


Specific Problems Event Type Probable Cause Perceived Severity EXT-ALARM Equipment Indeterminate 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 To simplify the external alarms declaration, default values are provided with an alarm translation table. BTS 9110-E: This is a door alarm for the micro-BTS slave 12, COBOX cover open.
200 / 320

Specific Problems Event Type Probable Cause Perceived Severity EXT-ALARM Equipment Indeterminate 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 To simplify the external alarms declaration, default values are provided with an alarm translation table. 9110-E: This is a PMS alarm for the micro-BTS slave12, equipment not in vertical position.

201 / 320


202 / 320


Specific Problems Event Type Probable Cause Perceived Severity EXT-ALARM Equipment Indeterminate 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.
203 / 320


204 / 320

Specific Problems Event Type Probable Cause Perceived Severity EXT-ALARM Equipment Indeterminate 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 To simplify the external alarms declaration, default values are provided with an alarm translation table. 9110-E: This is a PMS alarm for the micro-BTS slave21, equipment not in vertical position.

205 / 320


206 / 320


207 / 320


208 / 320

Specific Problems Event Type Probable Cause Perceived Severity EXT-ALARM Equipment Indeterminate 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 To simplify the external alarms declaration, default values are provided with an alarm translation table. 9110-E: This is a PMS alarm for the micro-BTS slave22, equipment not in vertical position.

209 / 320


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 event Type probable Cause perceived Severity Alarm Description RSL-LINK Communication Communications Protocol Error Warning (MI) 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 Loss Degradation BSS Cell(s) X Signaling X Calls X
212 / 320

[10,1] RSLLINK
Lock Function BTS
Unlock Function BTS
BTS operational?
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?
yes
Alarm solved
no
Onsite
Replace SUMP/SUMA
BTS operational?
yes
Alarm solved
Figure 102: RSL-LINK: BTS 9100 Corrective Actions
213 / 320

[10,1] RSLLINK
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
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 event Type probable Cause perceived Severity Alarm Description Alarm Number RX-CABLE Equipment Configuration Or Customization Error Major (PMA) An error has been detected in the cabling between a TRE and an ANX. 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 Loss Degradation BSS X Cell(s) X Signaling X Calls X -
215 / 320

[10,3] RXCABLE (TRE)
Lock Function TRE
Unlock Function TRE
ANX/ANY/ANC alarm events?
yes
Solve that alarm first
no
TRE operational?
yes
Alarm solved
no
Onsite
Check RX cables to TRE and ANX/ANY/ANC visually and electrically
Onsite
Check BTS status
Onsite
Replace TRE
TRE operational?
yes
Alarm solved
Figure 104: RX-CABLE (TRE):Corrective Actions
216 / 320
8.2.2 [10,3] RX-CABLE (RA)

specific Problems event Type probable Cause perceived Severity RX-CABLE Equipment Configuration Or Customization Error Nbr 3: Major (PMA) Nbr 4: Minor (DMA) Alarm Description Alarm Number An error has been detected in the cabling between a TRE and an ANX/ANC. 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.
217 / 320

[10,3] RXCABLE (RA)
Lock Function RA
Unlock Function RA
yes
no
RA operational?
yes
Alarm solved
no
Onsite
Check BTS status
Onsite
Check RX cables to TRE and ANX/ANY/ANC visually and electrically
Onsite
Replace ANX/ANY/ANC
RA operational?
yes
Alarm solved
Figure 105: RX-CABLE (RA): Corrective Actions
218 / 320
8.3 [10,10] TRE-VSWR

specific Problems event Type probable Cause perceived Severity Alarm Description TRE-VSWR Equipment Transmitter Failure Major (PMA) 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.
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 Loss Degradation BSS X Cell(s) X #* Signaling X Calls X#* -
219 / 320

[10,10] TREVSWR
Lock Function TRE
Unlock Function TRE
yes
no
TRE operational?
yes
Alarm solved
no
Onsite
Check TX cables to TRE and ANX/ANY/ANC visually and electrically
Onsite
Check BTS status
Onsite
Replace TRE
TRE operational?
yes
Alarm solved
Figure 106: TRE-VSWR: BTS 9100 Corrective Actions
220 / 320

[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
Figure 107: TRE-VSWR: BTS 9110/9110-E Corrective Actions
221 / 320
8.4 [10,11] ANTENNA-VSWR-WARNING

Required tools and materials Antenna Test Tools Antenna Dummy Load
specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number
ANTENNA-VSWR-WARNING Equipment Transmitter Failure Minor (DMA), Warning (MI) A fault has been detected concerning VSWR antenna supervision. 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. 7 (only for 9110-E BTS) : VSWR 2 alarm for Slave 1. 8 (only for 9110-E BTS) : VSWR 1 alarm for Slave 2. 9 (only for 9110-E BTS) : VSWR 2 alarm for Slave 2. 10 (only for 9110-E BTS) : VSWR 1 alarm for Slave 11. 11 (only for 9110-E BTS) : VSWR 2 alarm for Slave 11. 12 (only for 9110-E BTS) : VSWR 1 alarm for Slave 12. 13 (only for 9110-E BTS) : VSWR 2 alarm for Slave 12. 14 (only for 9110-E BTS) : VSWR 1 alarm for Slave 21. 15 (only for 9110-E BTS) : VSWR 2 alarm for Slave 21. 16 (only for 9110-E BTS) : VSWR 1 alarm for Slave 22. 17 (only for 9110-E BTS) : VSWR 2 alarm for Slave 22.
222 / 320
Impact
BSS
Cell(s)
Signaling
Calls
Transmission quality is degraded Loss Degradation X X
223 / 320
8.4.1 Corrective Actions for 9100 BTS

[10,11] ANTENNAVSWRWARNING
Lock Function RA
Unlock Function RA
TRE alarm events?
yes
no
RA operational?
yes
Alarm solved
no
Onsite
Onsite
Check VSWR Thresholds
Check BTS status
Onsite
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
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
no
RA operational?
yes
Alarm solved
no
Onsite
Check BTS status
Onsite
Onsite
Onsite
Check for antenna problems (connectors, damage, position, reflection) no
Onsite
Replace 9110 Micro BTS/9110E Micro BTS no RA operational? yes Alarm solved
BTS operational?
yes
Alarm solved
Figure 109: ANTENNA-VSWR-WARNING: Corrective Actions for 9110-E BTS
225 / 320
8.5 [10,12] ANTENNA-VSWR-URGENT

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number ANTENNA-VSWR-URGENT Equipment Transmitter Failure Major (PMA) A fault has been detected concerning VSWR antenna supervision. 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.
226 / 320

Required tools and materials : 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
TREAl arms
No
VSWRAlarm disappears?
Yes
Alarm solved
Figure 110: ANTENNA-VSWR-URGENT: Corrective Actions
227 / 320
TREAl arms
ANTENNAVSWRURGENT (continued)
TRE alarm events? No
Yes
OR
Temporary:
OR
OMCR OMCR
OMCR
Lock TRE(s) connected to susp. antenna
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
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
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 event Type probable Cause perceived Severity Alarm Description MODULE-CLOCK-SIGNAL Equipment Loss Of Signal Minor (DMA) A fault is detected on a multiframe clock signal from SUM.
Transmission quality is degraded. Impact Loss Degradation BSS Cell(s) Signaling X Calls X
230 / 320

[10,21] MODULEFRAMESIGNAL (TRE)
Lock Function TRE
Unlock Function TRE
TRE alarm events?
yes
no
More than one TRE sends this alarm?
yes
SUM Clock alarm events?
yes
no
no
Onsite
Check cables to TRE visually and electrically.
Onsite
Check SUM cables/connectors
Onsite
Replace TRE
Onsite
Replace SUM
yes Alarm solved TRE operational? TRE operational?
yes
Alarm solved
Figure 113: MODULE-FRAME-SIGNAL (TRE): BTS 9100 Corrective Actions
231 / 320

[10,21] MODULEFRAMESIGNAL (TRE)
Reset Function BTS
no
Master Clock alarm events?
yes Solve that alarm(s) first
BTS operational? no Onsite
yes
Alarm solved
Check cables between master BTS and reporting slave BTS visually and electrically.
Onsite
Onsite
Onsite
OR
Onsite
Onsite
BTS operational? no Replace BTS A910 BTS operational? yes Alarm solved
yes Alarm solved
no
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 event Type probable Cause perceived Severity Alarm Description MODULE-FRAME-SIGNAL Equipment Loss Of Signal Minor (DMA) A fault is detected on a multiframe clock signal from SUM.
Transmission quality is degraded. Impact Loss Degradation BSS Cell(s) Signaling X Calls X
233 / 320

[10,21] MODULEFRAMESIGNAL (RA)
Lock Function RA
Unlock Function RA
yes
no
Onsite
Onsite
Check cables to TRE and antenna visually and electrically.
Onsite
Replace ANX,ANY,ANC
yes Alarm solved RA operational?
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 event Type probable Cause perceived Severity Alarm Description Alarm Number MODULE-CLOCK-SIGNAL Equipment Loss Of Signal Minor (DMA) The input clock signal doesnt allow the TRE module to work. 1 : Synchronization in clocks and FN has failed during initialization state. 2 : CLKI master clock failure has been detected in the operational state.
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 Loss Degradation BSS X Cell(s) X #* Signaling X Calls X#* -
235 / 320

[10,22] MODULECLOCKSIGNAL (TRE)
Lock Function TRE
Unlock Function TRE
TRE alarm events?
yes
no
More than one TRE sends this alarm?
yes
yes
no
no
Onsite
Check cables to TRE visually and electrically.
Onsite
Onsite
Replace TRE
Onsite
Replace SUM
yes Alarm solved TRE operational? TRE operational?
yes
Alarm solved
Figure 116: MODULE-CLOCK-SIGNAL (TRE): BTS 9100 Corrective Actions
236 / 320

[10,22] MODULECLOCKSIGNAL (TRE)
Reset Function BTS
no
Master Clock alarm events?
yes Solve that alarm(s) first
BTS operational? no Onsite
yes
Alarm solved
Check cables between master BTS and reporting slave BTS visually and electrically.
Onsite
Onsite
Onsite
OR
Onsite
Onsite
BTS operational? no Replace BTS A910 BTS operational? yes Alarm solved
yes Alarm solved
no
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 event Type probable Cause perceived Severity Alarm Description Alarm Number MODULE-CLOCK-SIGNAL Equipment Loss Of Signal Minor (DMA) The input clock signal on ANX is faulty. 1 : Synchronization in clocks and frame numbers has failed during initialization state. 2 : CLKI master clock failure has been detected in the operational state.
238 / 320

[10,22] MODULECLOCKSIGNAL (RA)
Lock Function RA
Unlock Function RA
yes
no
Onsite
Onsite
Check cables to TRE and antenna visually and electrically.
Onsite
Replace ANX,ANY,ANC
yes Alarm solved RA operational?
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 event Type probable Cause perceived Severity Alarm Description Alarm Number MODULE-NOT-PRESENT Equipment Replaceable Unit Problem Major (PMA) A TRE module was not initially present, or has recently been extracted. 1 : The BCB detects the extraction of the module. 2 : There is no associated module for this SBL.
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, calls are lost. (*) If the TRE supporting the BCCH is concerned and there is no BCCH redundancy, the complete cell is lost. (X). Impact Loss Degradation BSS X Cell(s) X #* Signaling X Calls X#* -
240 / 320

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

[10,51] MODULENOTPRESENT
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
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 event Type probable Cause perceived Severity Alarm Description Alarm Number MODULE-NOT-PRESENT Equipment Replaceable Unit Problem Major (PMA) An ANC or ANX is not present. 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 Loss Degradation BSS X Cell(s) X Signaling X Calls X -
243 / 320

[10,51] MODULENOTPRESENT (RA)
Lock Function RA
Unlock Function RA
TRE operational?
yes
Alarm solved
no
Onsite
Insert missing ANX,ANY,ANC module
Onsite
Initialize the RAn
TRE operational?
yes
Alarm solved
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 event Type probable Cause perceived Severity Alarm Description IOM-DISCONNECTION Equipment Equipment Malfunction Minor (DMA) 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 Loss Degradation BSS Cell(s) Signaling Calls -
245 / 320

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

[10,234] IOMDISCONNECTION (TRE)
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
Figure 123: IOM-DISCONNECTION (TRE): BTS 9110/9110-E Corrective Actions
247 / 320
8.9.2 [10,234] IOM-DISCONNECTION (RA)

specific Problems event Type probable Cause perceived Severity Alarm Description IOM-DISCONNECTION Equipment Equipment Malfunction Minor (DMA) 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 Loss Degradation BSS Cell(s) Signaling Calls -
248 / 320

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

8.10.1 [10,237] HW-DEGRADED (TRE)
specific Problems event Type probable Cause perceived Severity Alarm Description HW-DEGRADED Equipment Equipment Malfunction Minor (DMA), Warning (MI) 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 Loss Degradation BSS Cell(s) Signaling Calls X
250 / 320

[10,237] HWDEGRADED (TRE)
Lock Function TRE
Unlock Function TRE
Onsite
yes Alarm solved TRE operational? no Check BCB cables/connectors
Onsite
Disengage TRE
Onsite
Onsite
Disengage, RIT by RIT, all TREs, ANYs, ANXs, the SUM and the XIOB
Onsite
yes Reengage TRE Alarm persists?
Reengage RIT
no
Onsite
yes Alarm persists? Replace TRE
no Onsite
Replace faulty RIT
TRE operational?
yes
Alarm solved
Onsite
yes Alarm persists? Replace BCB flat cable
no Alarm solved yes
TRE operational?
Alarm solved
Figure 125: HW-DEGRADED (TRE): BTS 9100 Corrective Actions
251 / 320

[10,237] HWDEGRADED (TRE)
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
Figure 126: HW-DEGRADED (TRE): BTS 9110/9110-E Corrective Actions
252 / 320
8.10.2 [10,237] HW-DEGRADED (RA)

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number HW-DEGRADED Equipment Equipment Malfunction Minor (DMA), Warning (MI) This is a HW failure, a local recovery action has failed. 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 Loss Degradation BSS Cell(s) Signaling Calls X
253 / 320
8.10.2.1 BTS 9100, Alarm Number 3 Corrective Actions

[10,237] HWDEGRADED (RA)
Alarm Number 3
Lock Function TRE
Unlock Function TRE
Onsite
yes Alarm solved TRE operational? no Check BCB cables/connectors
Onsite
Disengage TRE
Onsite
Onsite
Disengage, RIT by RIT, all TREs, ANYs, ANXs, the SUM and the XIOB
Onsite
yes Reengage TRE Alarm persists?
Reengage RIT
no
Onsite
no Onsite
Replace faulty RIT
TRE operational?
yes
Alarm solved
Onsite
yes Alarm persists? Replace BCB flat cable
no Alarm solved yes
TRE operational?
Alarm solved
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

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

[10,237] HARDWAREDEGRADED (RA)
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Check for antenna problems (e.g. damage, position, reflection). Solve antenna problem.
Onsite
Replace VSWR detector
Onsite
Alarm solved
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 event Type probable Cause perceived Severity Alarm Description HW-FAILURE Equipment Equipment Malfunction Major (PMA), Minor (DMA) 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
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, calls are lost. (*) If the TRE supporting the BCCH is concerned and there is no BCCH redundancy, the complete cell is lost. (X). Impact Loss Degradation BSS X Cell(s) X #* Signaling X Calls X#* -
258 / 320
8.11.1.1 9100 BTS, Alarm Number 1...11, 15 and 16 Corrective Actions

[10,239] HWFAILURE (TRE)
Alarm Number 1, 3...11, 15 & 16
Lock Function TRE
Unlock Function TRE
TRE operational?
yes
Alarm solved
no
TRE alarm events?
yes
Solve TRE alarm first
no
Onsite
Check BTS status
Onsite
no Alarm solved
TRE operational?
yes
Alarm solved
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

Alarm Number 12
Power alarm events?
yes
Solve power alarm first
no
yes
Alarm persists?
no
Alarm solved
Onsite
Check power supply. Ensure BTS is powered correctly.
Onsite
no
Alarm solved
TRE operational?
yes
Alarm solved
no
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

Alarm Number 13
Switch ON the front panel power switch
Initialise the TRE
TRE operational?
yes
Alarm solved
no
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

Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
Switch off Battery OR Backup Switch and OR Main Power switch in Side Support Cabinet
Onsite
Check cables between indicated clock unit on master BTS and reporting clock unit.
Onsite
Onsite
Alarm solved
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 event Type probable Cause perceived Severity Alarm Description Alarm Number HW-FAILURE Equipment Equipment Malfunction Major (PMA) This is a HW failure, a local recovery action has failed. 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 Loss Degradation BSS X Cell(s) X Signaling X Calls X -
263 / 320
8.11.2.1 BTS 9100, Alarm Number 2 and 12 Corrective Actions

[10,239] HWFAILURE (RA)
Alarm Number 2 & 12
Lock Function RA
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 yes
RA operational?
Alarm solved
Figure 134: HW-FAILURE (RA): BTS 9100, Alarm Number 2 and 12 Corrective Actions
264 / 320

Alarm Number 10
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Other TRE alarm events?
yes
no
Onsite
Check BTS status
Onsite
no Alarm solved yes
RA operational?
Alarm solved
Figure 135: HW-FAILURE (RA): BTS 9100, Alarm Number 10 Corrective Actions
265 / 320

Alarm Number 14
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Other related alarm events?
yes
Solve related alarm(s) first
no
RA operational?
yes
Alarm solved
Figure 136: HW-FAILURE (RA): BTS 9100, Alarm Number 14 Corrective Actions
266 / 320

Reset Function BTS
If an alarm on the feeding clock unit of the master BTS is still outstanding, the failure is due to external reasons.
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
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 event Type probable Cause perceived Severity Alarm Description Alarm Number RESTART Processing Error Application Subsystem Failure Warning (MI) The TRE has (auto)restarted successfully. 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 Loss Degradation BSS Cell(s) X Signaling X Calls X -
268 / 320

Disable RF Power Use the BTS NEM to disable RA before disconnecting RF cables. Initialize RA after work. 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)
Lock Function TRE
Unlock Function TRE
TRE operational?
yes
Alarm solved
no
Check configuration parameters
Correct configuration parameters
TRE operational?
yes
Alarm solved
no Onsite
Replace TRE
TRE operational?
yes
Alarm solved
Figure 138: RESTART (TRE): BTS 9100 Corrective Actions
269 / 320

[10,248] RESTART (TRE)
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
Figure 139: RESTART (TRE): BTS 9110/9110-E Corrective Actions
270 / 320
8.12.2 [10,248] RESTART (RA)

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number RESTART Processing Error Application Subsystem Failure Warning (MI) The ANX/ANC has (auto)restarted successfully. 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).
271 / 320

Disable RF Power Use the BTS NEM to disable RA before disconnecting RF cables. Initialize RA after work. 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
no Alarm solved yes
RA operational?
Alarm solved
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 event Type probable Cause perceived Severity Alarm Description LOOP-TO-EQUIPMENT Equipment Indeterminate Major (PMA), Warning (MI) An external loop is closed on an interface of the module. All channels on this interface (OML, RSL, TCH) are looped back. 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.
Alarm Number
As long as the loop is closed, the concerned channels are not available. Impact Loss Degradation BSS Cell(s) X Signaling X Calls X -
274 / 320

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

[11,22] LOOPTO EQUIPMENT
Onsite
Release external test loop BTS operational? yes Alarm solved
no
Onsite
BTS operational? yes Alarm solved
Reset Function BTS
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
yes yes Alarm solved BTS operational? Alarm solved
Figure 142: LOOP-TO-EQUIPMENT: BTS 9110/9110-E Corrective Actions
276 / 320
9.2 [11,50] LOSS-OF-INCOMING-SIGNAL

specific Problems event Type probable Cause perceived Severity Alarm Description LOSS-OF-INCOMING-SIGNAL Equipment Indeterminate Major (PMA), Warning (MI) 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 Loss Degradation BSS Cell(s) X Signaling X Calls X -
277 / 320

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

[11,50] LOSSOF INCOMINGSIGNAL
Onsite
Abis link is re established? no Reset Function BTS
yes Check/solve alarms of AIFL Abis link is re established? no yes Alarm solved
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Abis link is re established? no Replace BTS A910 Abis link is re established? no Contact System Support yes Alarm solved
yes Alarm solved
Figure 144: LOSS-OF-INCOMING-SIGNAL: BTS 9110/9110-E Corrective Actions
279 / 320
9.3 [11,66] AIS-2M

specific Problems event Type probable Cause perceived Severity Alarm Description AIS-2M Equipment Indeterminate Minor (DMA), Warning (MI) The 2 Mbit/s interface is receiving a AIS signal (all one indication).
280 / 320
9.3.1 9100 BTS Corrective Actions

[11,66] AIS2M
Related BTS alarms?
yes
Solve this alarms
Alarm persists?
no
no
yes
yes Related BSC alarms? Solve this alarms
Alarm persists?
no
no
yes
Check related SBL (OML, RSL)
SBL in fault?
no
Inhibit / allow alarm reporting
Alarm persists?
no
yes
yes
BTS TRANS settings ok (CRC4)?
no
Correct BTS TRANS settings
Alarm persists?
no
Alarm solved
yes
yes
Loop back BTS originated E1 link at BTS site yes yes Loop back BTS originated E1 link at BSC site no
No BSS problem; Check E1 link with line provider.
Alarm persists?
Alarm persists?
Check BSC local cabling
Local cabling OK?
no
Solve cabling problem
Alarm persists?
no
yes
yes
Replace SUMx
Alarm persists?
no
yes
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
Solve this alarms
Alarm persists?
no
no
yes
Alarm persists?
no
no
yes
SBL in fault?
no
Alarm persists?
no
yes
yes
no
Alarm persists?
no
Alarm solved
yes
yes
Alarm persists?
Alarm persists?
Local cabling OK?
no
Alarm persists?
no
yes
yes
Alarm persists?
no
yes
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 event Type probable Cause perceived Severity Alarm Description LOSS-OF-FRAME-ALIGNMENT Equipment Indeterminate Major (PMA), Warning (MI) There is a loss of frame alignment on the Abis link.
283 / 320

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

[11,81] LOSSOF FRAMEALIGNMENT
Onsite
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Abis link is re established? no Replace BTS A910 Abis link is re established? no Contact System Support yes Alarm solved
yes Alarm solved
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 event Type probable Cause perceived Severity Alarm Description LOSS-OF-CRC-MULTIFRAME-ALIGNMENT Equipment Indeterminate Major (PMA), Warning (MI) 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.
286 / 320

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

[11,86] LOSSOFCRCMULTIFRAME ALIGNMENT
Onsite
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Check transmission equipment up to next node in Abis chain
no
Abis link is re established? no
yes
Alarm solved
yes Alarm solved
Onsite
Replace BTS A910 Abis link is re established? no Contact System Support yes Alarm solved
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 event Type probable Cause perceived Severity Alarm Description ERROR-RATE>E-3 Equipment Indeterminate Major (PMA), Warning (MI) The error rate of the incoming main system signal on the Abis link is worse than the threshold value E-3.
289 / 320

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

Onsite
Abis link quality OK? no Reset Function BTS
yes Check/solve alarms of AIFL Abis link quality OK? no yes Alarm solved
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Abis link quality OK? no Replace BTS A910 Abis link quality OK? no Contact System Support yes Alarm solved
yes Alarm solved
Figure 152: ERROR-RATE>E-3: BTS 9110/9110-E Corrective Actions
291 / 320
9.7 [11,100] ERROR-RATE >E-4

specific Problems event Type probable Cause perceived Severity Alarm Description ERROR-RATE>E-4 Equipment Indeterminate Minor (DMA), Event (Mi) 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 Loss Degradation BSS Cell(s) Signaling X Calls X
292 / 320

yes
no
no
yes
Alarm solved
Onsite
Onsite
Reset BTS
no
Onsite
Replace SUMP/SUMA
yes
Alarm solved
293 / 320

Onsite
Onsite
Onsite
Onsite
OR
Onsite
Onsite
yes Alarm solved
294 / 320
9.8 [11,102] ERROR-RATE >E-6

specific Problems event Type probable Cause perceived Severity Alarm Description ERROR-RATE>E-6 Equipment Indeterminate Minor (DMA), Warning (MI) 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 Loss Degradation BSS Cell(s) Signaling (X) Calls (X)
295 / 320

yes
no
no
yes
Alarm solved
Onsite
Onsite
Reset BTS
no
Onsite
Replace SUMP/SUMA
yes
Alarm solved
296 / 320

Onsite
Onsite
Onsite
Onsite
OR
Onsite
Onsite
yes Alarm solved
297 / 320
9.9 [11,176] REMOTE-ALARM-INDICATION

specific Problems event Type probable Cause perceived Severity Alarm Description REMOTE-ALARM-INDICATION Equipment Indeterminate Minor (DMA), Event (Mi) 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.
298 / 320
9.9.1 9100 BTS Corrective Actions

[11,176] REMOTE ALARMINDICATION
Related BTS alarms?
yes
Solve this alarms
Alarm persists?
no
no
yes
Alarm persists?
no
no
yes
SBL in fault?
no
Alarm persists?
no
yes
yes
no
Alarm persists?
no
Alarm solved
yes
yes
Alarm persists?
Alarm persists?
Local cabling OK?
no
Alarm persists?
no
yes
yes
Replace SUMx
Alarm persists?
no
yes
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
Solve this alarms
Alarm persists?
no
no
yes
Alarm persists?
no
no
yes
SBL in fault?
no
Alarm persists?
no
yes
yes
no
Alarm persists?
no
Alarm solved
yes
yes
Alarm persists?
Alarm persists?
Local cabling OK?
no
Alarm persists?
no
yes
yes
Alarm persists?
no
yes
300 / 320
9.10 [11,177] PPP ALL1

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number PPP ALL1 Equipment Indeterminate Major (PMA) All 1s are detected in PPP frames on BTS side. 1 : PPP All1.

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

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number PPP NO RECEIPT OF HDLC SIGNAL Equipment Indeterminate Major (PMA) No HDLC signal is received on the BTS side. 1 : PPP No Receipt of HDLC Signal.

[11,178] PPP NO RECEIPT OF HDLC SIGNAL
yes Alarm cleared?
Alarm solved
no
Figure 159: PPP NO RECEIPT OF HDLC SIGNAL: Corrective Actions
302 / 320
9.12 [11,179] PPP RECEIPT OF TERMINATE

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number PPP RECEIPT OF TERMINATE Equipment Indeterminate Major (PMA) The BTS side received a Terminate signal. 1 : PPP Receipt of Terminate.

[11,179] PPP RECEIPT OF TERMINATE
yes Alarm cleared?
Alarm solved
no
Figure 160: PPP RECEIPT OF TERMINATE: Corrective Actions
303 / 320
9.13 [11,180] HDLC HIGH ERRONEOUS FRAMES RATIO

specific Problems event Type probable Cause perceived Severity Alarm Description HDLC HIGH ERRONEOUS FRAMES RATIO Equipment Indeterminate Major (PMA) High ratio of HDLC failures (CRC, frames too long, frames too short, receipt of abort). 1 : PPP High Erroneous Frames Ratio.
Alarm Number

[11,180] PPP HIGH ERRONEOUS FRAMES RATIO
yes Alarm cleared?
Alarm solved
no
Figure 161: PPP HIGH ERRONEOUS FRAMES RATIO: Corrective Actions
304 / 320
9.14 [11,181] HDLC MEDIUM ERRONEOUS FRAMES RATIO

specific Problems event Type probable Cause perceived Severity Alarm Description HDLC MEDIUM ERRONEOUS FRAMES RATIO Equipment Indeterminate Major (PMA) Medium ratio of HDLC failures (CRC, frames too long, frames too short, receipt of abort). 1 : PPP Medium Erroneous Frames Ratio.
Alarm Number

[11,181] PPP MEDIUM ERRONEOUS FRAMES RATIO
yes Alarm cleared?
Alarm solved
no
Figure 162: PPP MEDIUM ERRONEOUS FRAMES RATIO: Corrective Actions
305 / 320
9.15 [11,182] HDLC LOW ERRONEOUS FRAMES RATIO

specific Problems event Type probable Cause perceived Severity Alarm Description HDLC LOW ERRONEOUS FRAMES RATIO Equipment Indeterminate Major (PMA) Low ratio of HDLC failures (CRC, frames too long, frames too short, receipt of abort). 1 : PPP Low Erroneous Frames Ratio.
Alarm Number

[11,182] PPP LOW ERRONEOUS FRAMES RATIO
yes Alarm cleared?
Alarm solved
no
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 4 Bytes 1-5 6 - 24 5 1-5 6 - 37 6 1-5 6 - 24 7 1-5 6 - 176 Table 5: Alarm [2,247] TLV Codes Coding TLV120 TLV83 TLV120 TLV84 TLV120 TLV83 TLV120 TLV82
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 1 Bytes 1-5 6 - 37 3 1-5 6 - 24 4 1-5 6 - 176 Table 6: Alarm [2,248] TLV Codes Coding TLV120 TLV84 TLV120 TLV83 TLV120 TLV82
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 2 1 1 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 1 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) 1 FU CIPHERING CAPABILITY bit 7 Encryption with A5/7 algorithm - Not Provided (0) Provided (1) bit 6 Encryption with A5/6 algorithm - Not Provided (0) Provided (1) bit 5 Encryption with A5/5 algorithm - Not Provided (0) Provided (1) bit 4 Encryption with A5/4 algorithm - Not Provided (0) Provided (1) bit 3 Encryption with A5/3 algorithm - Not Provided (0) Provided (1) bit 2 Encryption with A5/2 algorithm - Not Provided (0) Provided (1) bit 1 Encryption with A5/1 algorithm - Not Provided (0) Provided (1) bit 0 No Encryption - always 1 = provided (always possible) FF = all algorithms supported. )) never sent by the FUunknown. 1 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 1 5 6 9 13 20 0 21 22 23 24 25 27 28 29 30 31 32 33 34 21 0 25 EV EV EV EV EV EV EV EV EV EV EV EV EV EV EV ALAN 0 0 0 0 0 EVAD AD AD AD AD AD Description of Fault Code CLKI clock failure (1) CLKI frame failure RSL LAPD link failure Non fatal temperature failure TRE VSWR failure (1) Recoverable failure Microprocessor failure BCCH failure Algorithm failure TLC_CONFIG_T expiry TS reconfiguration failure SYS INFO 3 failure BCCH_CUT timeout Radio failure ECPL failure L1 DSP failure L1 DSP no response failure Internal serial interface failure FCLK IT failure Internal FN failure Handover/Power control algorithms configuration refused Missing message TRE fatal failure (1)
311 / 320
ALATYP
ALAN 0 1 2 3 4 5 6 7 8 9 10 11 20 28 29 30 31 32 33 34
EVAD AD AD AD AD AD AD AD AD AD AD AD AD AD AD AD AD AD AD AD AD
Description of Fault Code Microprocessor failure HW failure SW failure CLKI synchronization failure Autoreconfiguration failure Configuration failure BSII failure (2) IOM LAPD link failure SW activation failure Downloading failure HW watchdog reset Configuration file failure Temperature failure Radio failure ECPL failure L1 DSP failure L1 DSP no response failure Internal serial interface failure FCLK IT failure 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 1 2 0 1 2 3 4 5 7 0 1 2 3 14 15 16 17 18 19 20 0 10 EV EV 0 0 0 0 0 0 AD AD AD AD AD AD AD AD AD AD 0 0 AD AD AD AD AD AD ALAN 0 EVAD AD Description of Fault Code CLKI clock failure LNA failure LNA 1 partial failure LNA 2 partial failure LNA 1 total failure LNA 2 total failure VSWR circuitry failure CLKI frame failure Antenna VSWR failure AN1_VSWR1_AL AN2_VSWR1_AL AN1_VSWR2_AL AN2_VSWR2_AL Microprocessor failure HW failure SW failure Configuration failure SW activation failure Downloading failure Recoverable failure Microprocessor failure 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 3 0 1 2 3 4 8 14 16 18 19 20 0 10 25 1 3 AD AD EV EV 0 0 0 0 0 AD AD AD AD AD AD AD AD AD AD ALAN EVAD Description of Fault Code Internal CLOCK failure FN input from master lost Frame signal input from master lost Reference clock input from master lost PCM synchronization unusable GPS synchronization lost Oven warm up alarm Microprocessor failure SW failure SW activation failure Downloading failure Recoverable failure Microprocessor failure Watchdog reset TRANS&CLOCK fatal failure (1) HW failure 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 2 1 or 2 2 1 Variable Description Element Identifier (=61) Length (2 bytes if length > 127 (1) Board Identification Result type 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. TRANS&CLOCK (9100 BTS only) CLOCK TRANS -
Bit Number 0 1 2 3 4 5 6
TRE (1) ENCT DEC DEM0 DEM1 MBED CUL SCP
ANX/ANC VSWR LNA 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 2 1 1 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). Access to illegal address (e.g. odd address for LONG variable), detected by micro-processor.
3 = Address error
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 59 = MMU : 60 = MMU : 61 = MMU : 62 = MMU : Branch to Write Violation Code (ATC). Branch to Limit Violation Code. Branch to Supervisor Violation Code. Branch to Bus Error during Table Search Code. Branch to Page Fault or Invalid Descriptor Code. Branch to Write Violation Code.
63 = MMU :
64 = MMU :
316 / 320
Bytes
Description - Watchdog Reset 65 = Fatal Signal Error
4 2 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 92 1
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 Complete STACK Frame Board Status Register (see relevant OMU HW Functional Description).
Table 12: TLV82 Bytes
317 / 320
10.2.6 TLV83 Coding

The TLV83 byte definitions are shown in Table 13 . Bytes 2 1 4 4 Description - Scenario Problems Element Identifier ( = 83) Length ( = 16) Taskname SBL Id. byte 1+ 2 byte 3 byte 4 2 The name of the task that triggered the autorestart/autoreset (ASCII coded). The SBL on which the scenario was running, where: SBL type
SBL number
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 1 2 4 5 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 Three unsuccessful autorestarts.
318 / 320
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) Table 13: TLV83 Bytes
10.2.7 TLV84 Coding

The TLV84 byte definitions are shown in Table 14 . Bytes 2 1 4 Description - Lack of Resources Element Identifier ( = 84) Length ( = 69) Taskname The name of the task that triggered the autorestart/autoreset (ASCII coded).
Required Memory Region. The requested memory region. 0 1 2 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

The TLV120 byte definitions are shown in Table 15 . Bytes 2 1 1 Description Element Identifier ( = 120) Length ( = 3) Hardware revision: 0 - Hardware 1 (serial test interface, volatile memory). 1 - Hardware 2 (parallel test interface, non-volatile memory). 1 1 RAM size - given as the number of 4 Mbyte blocks. Flash EPROM: 0 - Not equipped or not accessible. 1 - Equipped. Table 15: TLV120 Bytes
10.2.9 TLV243 Coding

The TLV243 byte definitions are shown in Table 16 . Bytes 2 1 1 Description Element Identifier ( = 243) Length ( = 1) BTS HW family (for the coding, see below). G3 60 9100 BTS
320 / 320

BTS Alarm Dictionary

Uploaded by

Document Information

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

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent GSM

BTS Alarm Dictionary

BTS Document Reference Guide Release B11

3BK 21625 AAAA PCZZA Ed.06

BLANK PAGE BREAK

Status Short title

RELEASED 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

Note: Document Pertinence

3BK 21625 AAAA PCZZA Ed.06

Audience Assumed Knowledge

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

SBL state OPR IT FIT FLT EF FOS SOS UT WTC MSD/MSA

MO availability state {} {} Degraded Failed Dependency/failed Off-line/failed Dependency Under test {} {}

MO control state {} {} {} {} {} {} {} {} {} suspended

Table 1: SBL state to MO state translation

3BK 21625 AAAA PCZZA Ed.06

1.2.2 State change commands translation

1.2.3 Mapping of MO Perceived Severity to BSS Alarm Category

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

Quality of Service Processing Error Equipment Environmental Table 3: Event Types

Severity Level Critical

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

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 and alarm name

no Decision field Alarm persists?

Onsite action fields

Power supply operational?

no Contact System Support

3BK 21625 AAAA PCZZA Ed.06

1.5.3 Additional Information

3BK 21625 AAAA PCZZA Ed.06