Alcatel-Lucent BTS Alarm Dictionary

Alcatel-Lucent GSM
BTS Alarm Dictionary
BTS Document Reference Guide Release B9
3BK 20925 AAAA PCZZA Ed.13
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 / 590
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 1.2 Relationships Between SBLs and MOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 1.3 A1353-RA Alarm Surveillance Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 1.4 LMT Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 1.5 BTS Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Class 1: CLK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.1 [1,1] OCXO-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 2.2 [1,3] CLOCK-FREQ-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.3 [1,6] MCL-FATAL-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 2.4 [1,7] MCL-TEST-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 2.5 [1,8] MCL-DRV-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 2.6 [1,11] MCLU-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 2.7 [1,12] CLOCK-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 2.8 [1,22] MCLR-EA-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 2.9 [1,23] PCM-SYNC-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 2.10 [1,31] MCL-XCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 2.11 [1,234] IOM-DISCONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 2.12 [1,237] HW-DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 2.13 [1,240] MISSING-ENTRY-IN-CPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 2.14 [1,241] INCONSIST-ASSHW-ACTHW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 2.15 [1,246] CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 2.16 [1,247] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 2.17 [1,248] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 2.18 [1,250] NO-ANSWER-DCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 2.19 [1,255] Q1-RELAY-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Class 2: OMU Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 3.1 [2,1] LOSS OF TWIN CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 3.2 [2,247] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 3.3 [2,248] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Class 3: SW-AN Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 4.1 [3,0] UNKNOWN-UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 4.2 [3,1] UNKNOWN-CMD-MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 4.3 [3,2] UNKNOWN-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 4.4 [3,11] SW-PROBLEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 4.5 [3,13] TELECOM-CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 4.6 [3,14] WRONG-CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 4.7 [3,246] CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Class 4: FHU Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 5.1 [4,1] DUMMY-BURST-GEN-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 5.2 [4,5] FN-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 5.3 [4,6] INTERNAL-FN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 5.4 [4,10] FATAL-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 5.5 [4,14] FCLK-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 5.6 [4,15] INT-FCLK-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 5.7 [4,16] OBCLK-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 5.8 [4,17] INTERNAL-OBCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 5.9 [4,240] MISSING-ENTRY-IN-CPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 5.10 [4,246] CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 5.11 [4,247] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 5.12 [4,250] NO-ANSWER-DCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
3 / 590
Contents
5.13 Class 5: 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9 6.10 6.11 6.12 6.13 6.14 6.15 6.16 6.17 6.18 6.19 6.20 Class 6: 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.10 7.11 7.12 7.13 7.14 7.15 7.16 7.17 7.18 7.19 7.20 7.21 7.22 7.23 7.24 7.25 7.26 7.27 7.28 7.29 7.30 7.31 7.32 7.33
[4,255] Q1-RELAY-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENVIR Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,0] POWER-SUPPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,1] FAN-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,2] FAN-ALARM-U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,3] FAN-ALARM-T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,4] BTS-TEMP-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,5] CPLG-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,6] SU-POWER-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,7] TRX-POWER-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,11] POWER-SUPPLY-U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,12] POWER-SUPPLY-NU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,13] CONTROL-UNIT-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,14] MAINS-POWER-SUPPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,15] BATT-DEEP-DISCHARGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,20] MAINS-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,23] POWER-SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,24] SUBRACK-POWER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,31] TEMPERATURE-WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,32] FATAL TEMPERATURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,237] HW-DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [5,239] HW-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,1] LNK-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,2] LNK-DBLE-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,5] RX-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,6] RX-DBLE-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,7] RX-SYN-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,8] RX-SYN-DBLE-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,9] VSWR-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,10] TX-POWER-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,11] TEMP-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,13] TX-SYN-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,14] FCLK-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,15] INTERNAL-FCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,16] OBCLK-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,17] INTERNAL-OBCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,18] REF-FREQ-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,19] INTERNAL-REF-FRQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,34] ANTENNA-VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,35] FRONTEND-RELAY-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,36] FRONTEND-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,37] FATAL-FRONTEND-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,38] BCCH-SWITCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,39] BCCH-SWITCH-FATAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,42] RTMA-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,43] PERU-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,45] TEST-ABORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,46] ALARM-TEST-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,48] RF-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,49] FRONTEND-AMP-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,50] DATA-INCONSIS-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,51] RTC-OUT-OF-BAND-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,52] RTC-FINE-TUNING-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,53] RTC-PARKING-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,54] RTC-SELFTEST-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
151 153 154 160 161 162 163 165 167 169 171 173 175 177 179 181 183 186 188 192 194 201 207 208 211 214 216 218 220 222 225 227 230 232 235 238 240 242 244 247 249 251 253 255 257 259 261 263 265 268 273 275 277 279 281 283
4 / 590
Contents
10
7.34 7.35 7.36 7.37 7.38 7.39 7.40 7.41 7.42 7.43 Class 7: 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 8.10 8.11 8.12 8.13 8.14 8.15 8.16 8.17 8.18 8.19 8.20 8.21 Class 8: 9.1 9.2 9.3 9.4 9.5 9.6 9.7 9.8 9.9 9.10 9.11 9.12 9.13 9.14 9.15 9.16 Class 9: 10.1 10.2 10.3 10.4 10.5 10.6
[6,55] RTC-EXT-CONN-LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,56] RTC-DETECTOR-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,240] MISSING-ENTRY-IN-CPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,241] INCONSIST-ASSHW-ACTHW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,246] CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,247] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,250] NO-ANSWER-DCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,251] SELF-TEST-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,252] SELF-TEST-DBLE-AL (CU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [6,255] Q1-RELAY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FU Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,1] AL-LIST-ER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,3] MCL-LINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,5] BSI-LINK-0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,6] BOTH-BSI-LINKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,7] FHI-LK0-FUL-UNV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,8] FHI-LK1-FUL-UNV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,14] FHU-DUMMY-BURST-GEN-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,31] HW-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,32] NR-SW-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,33] NR-SCP-MP-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,34] BOTH-FHI-LINKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,35] BOTH-CLOCKS-LINKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,36] FU-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,240] MISSING-ENTRY-IN-CPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,241] INCONSIST-ASSHW-ACTHW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,242] INCONSIST-actHW-logConfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,243] INCONSIST-actHW-BTSparam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,245] SW-DLL-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,246] CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,248] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [7,250] NO-ANSWER-DCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-BTS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,3] RESYNCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,4] IGNORE EQUIPMENT OVER 12 TRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,5] TOO MANY PLUGGED MODULES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,6] TB-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,7] Q1-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,8] HW-RESYNCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,26] RACH-CATCHER-LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,30] BCB-LINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,31] IOM-LINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,32] MODULE-INSERTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,246] CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,247] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,248] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,250] NO-ANSWER-DCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,251] SELF-TEST-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [8,255] Q1-RELAY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS-EXTERNAL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [9,1...56] EXT-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [9,1] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [9,2] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [9,3] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [9,4] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [9,5] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
285 287 289 293 298 302 304 308 310 312 317 318 321 323 325 327 329 331 333 335 336 337 340 343 344 346 350 352 354 356 358 360 363 364 365 366 367 369 371 372 374 377 380 383 386 390 391 394 397 401 402 404 407 409 412 414
5 / 590
Contents
11
10.7 [9,6] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.8 [9,7] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.9 [9,8] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.10 [9,9] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.11 [9,10] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.12 [9,11] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.13 [9,12] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.14 [9,13] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.15 [9,14] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.16 [9,15] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.17 [9,16] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.18 [9,17] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.19 [9,18] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.20 [9,19] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.21 [9,20] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.22 [9,21] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.23 [9,22] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.24 [9,23] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.25 [9,24] EXT-ALARM (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.26 [9,25] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.27 [9,26] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.28 [9,27] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.29 [9,28] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.30 [9,29] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.31 [9,30] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.32 [9,31] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.33 [9,32] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.34 [9,33] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.35 [9,34] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.36 [9,35] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.37 [9,36] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.38 [9,37] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.39 [9,38] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.40 [9,39] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.41 [9,40] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.42 [9,41] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.43 [9,42] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.44 [9,43] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.45 [9,44] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.46 [9,45] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.47 [9,46] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.48 [9,47] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.49 [9,48] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.50 [9,49] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.51 [9,50] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.52 [9,51] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.53 [9,52] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.54 [9,53] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.55 [9,54] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.56 [9,55] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.57 [9,56] EXT-ALARM for A9110-E (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 10: RX-TX Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 [10,1] RSL-LINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 [10,3] RX-CABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 [10,10] TRE-VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.4 [10,11] ANTENNA-VSWR-WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5 [10,12] ANTENNA-VSWR-URGENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
416 418 420 422 424 426 428 430 432 434 436 438 440 442 444 446 448 450 452 454 454 455 455 456 456 457 457 458 458 459 459 460 460 461 461 462 462 463 463 464 464 465 465 466 466 467 467 468 468 469 469 471 472 475 479 482 486
6 / 590
Contents
12
13
11.6 [10,21] MODULE-FRAME-SIGNAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.7 [10,22] MODULE-CLOCK-SIGNAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.8 [10,51] MODULE-NOT-PRESENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.9 [10,234] IOM-DISCONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.10 [10,237] HW-DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.11 [10,239] HW-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.12 [10,248] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.13 [10,248] RESTART (RA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 11: BTS-TRANS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1 [11,22] LOOP-TO-EQUIPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 [11,50] LOSS-OF-INCOMING-SIGNAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.3 [11,66] AIS-2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.4 [11,81] LOSS-OF-FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.5 [11,86] LOSS-OF-CRC-MULTIFRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.6 [11,99] ERROR-RATE >E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.7 [11,100] ERROR-RATE >E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.8 [11,102] ERROR-RATE >E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.9 [11,176] REMOTE-ALARM-INDICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Alarm Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.1 BTS Alarms with Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2 TLV Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
490 495 500 505 510 517 528 531 533 534 537 540 542 545 548 551 554 557 559 560 562
7 / 590
Figures
Figures
Figure 1: Graphical workflow for corrective actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Figure 2: OCXO-AL: G1/G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Figure 3: CLOCK-FREQ-AL: G1/G2 BTS, Alarm Number 1, 3 & 4, Corrective Actions at OMC-R . . . . . . . . 35 Figure 4: CLOCK-FREQ-AL: G1/G2 BTS, Alarm Number 1, 3 & 4, Corrective Actions On-Site . . . . . . . . . . 36 Figure 5: CLOCK-FREQ-AL: G2 BTS, Alarm Number 2 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Figure 6: MCL-FATAL-AL: G1/G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Figure 7: MCL-FATAL-AL: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Figure 8: MCL-FATAL-AL: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Figure 9: MCL-TEST-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Figure 10: MCL-DRV-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Figure 11: MCLU-FAULT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Figure 12: CLOCK-FAULT: G1/G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Figure 13: CLOCK-FAULT: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Figure 14: CLOCK-FAULT: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Figure 15: MCL-EA-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Figure 16: PCM-SYNC-AL: G1/G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Figure 17: MCL-XCLK: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Figure 18: MCL-XCLK: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Figure 19: HW-DEGRADED: BTS A9100, Alarm Number 1 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . 61 Figure 20: HW-DEGRADED: BTSA9100, Alarm Number 2 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . 62 Figure 21: HW-DEGRADED: BTS A9110/A9110-E , Alarm Number 1 Corrective Actions . . . . . . . . . . . . . . . 63 Figure 22: HW-DEGRADED: BTS A9110/A9110-E ,Alarm Number 2 Corrective Actions . . . . . . . . . . . . . . . 64 Figure 23: MISSING-ENTRY-IN-CPF: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Figure 24: INCONSIST-ASSHW-ACTHW, Alarm Number 3: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . 68 Figure 25: INCONSIST-ASSHW-ACTHW, Alarm Number 5: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . 69 Figure 26: CONFIG-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Figure 27: RESET: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Figure 28: RESET: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Figure 29: RESTART: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Figure 30: RESTART: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Figure 31: NO-ANSWER-DCL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Figure 32: Q1-RELAY-FAILURE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Figure 33: LOSS OF TWIN CONFIGURATION Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Figure 34: RESET: Alarm Number 1,2 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Figure 35: RESET: Alarm Number 3 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Figure 36: RESET: Alarm Number 4 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Figure 37: RESET: Alarm Number 5 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Figure 38: RESET: Alarm Number 6 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Figure 39: RESET: Alarm Number 7 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8 / 590
Figures
Figure 40: UNKNOWN-UNIT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Figure 41: UNKNOWN-CMD-MSG: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Figure 42: UNKNOWN-ALARM: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Figure 43: SW-PROBLEM (CLLK): BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Figure 44: SW-PROBLEM (CLLK): BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Figure 45: SW-PROBLEM (TRE): BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Figure 46: SW-PROBLEM (TRE): BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Figure 47: SW-PROBLEM (RA): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Figure 48: TELECOM-CONFIG-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Figure 49: WRONG-CONFIGURATION (TRE): Alarm Number 1, 2, 3, 6, Corrective Actions . . . . . . . . . . . 108 Figure 50: WRONG-CONFIGURATION (TRE): Alarm Number 4, Corrective Actions . . . . . . . . . . . . . . . . . . 109 Figure 51: WRONG-CONFIGURATION (TRE): Alarm Number 5, Corrective Actions . . . . . . . . . . . . . . . . . . 110 Figure 52: WRONG-CONFIGURATION (TRE): Alarm Number 7, 9, Corrective Actions . . . . . . . . . . . . . . . . 111 Figure 53: WRONG-CONFIGURATION (TRE): Alarm Number 8, Corrective Actions . . . . . . . . . . . . . . . . . . 112 Figure 54: WRONG-CONFIGURATION (BTS): Alarm Number 11, Corrective Actions . . . . . . . . . . . . . . . . . 113 Figure 55: WRONG-CONFIGURATION (RA): Alarm Number 2, 7, 10, Corrective Actions . . . . . . . . . . . . . 115 Figure 56: WRONG-CONFIGURATION (RA): Alarm Number 4, Corrective Actions . . . . . . . . . . . . . . . . . . . 116 Figure 57: WRONG-CONFIGURATION (BTS): Alarm Number 12, 14, Corrective Actions . . . . . . . . . . . . . 118 Figure 58: WRONG-CONFIGURATION (BTS): Alarm Number 13, Corrective Actions . . . . . . . . . . . . . . . . . 119 Figure 59: CONFIG-FAIL (CLLK): BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Figure 60: CONFIG-FAIL (CLLK): BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Figure 61: CONFIG-FAIL (RA): BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Figure 62: CONFIG-FAIL (RA): BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Figure 63: CONFIG-FAIL (TRE): BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Figure 64: CONFIG-FAIL (TRE): BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Figure 65: DUMMY-BURST-GEN-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Figure 66: FN-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Figure 67: INTERNAL-FN: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Figure 68: FATAL-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Figure 69: FCLK-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Figure 70: INT-FCLK-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Figure 71: OBCLK-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Figure 72: INTERNAL-OBCLK: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Figure 73: MISSING-ENTRY-IN-CPF: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Figure 74: CONFIG-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Figure 75: RESET: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Figure 76: NO-ANSWER-DCL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Figure 77: Q1-RELAY-FAILURE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Figure 78: POWER-SUPPLY (CU): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Figure 79: POWER-SUPPLY (FU): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
9 / 590
Figures
Figure 80: POWER-SUPPLY (RA): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Figure 81: FAN-ALARM: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Figure 82: FAN-ALARM-U: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Figure 83: FAN-ALARM-T: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Figure 84: BTS-TEMP-ALARM: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Figure 85: CPLG-ALARM: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Figure 86: SU-POWER-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Figure 87: TRX-POWER-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Figure 88: POWER-SUPPLY-U: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Figure 89: POWER-SUPPLY-NU: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Figure 90: CONTROL-UNIT-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Figure 91: MAINS-POWER-SUPPLY: G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Figure 92: BATT-DEEP-DISCHARGE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Figure 93: MAINS-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Figure 94: POWER-SHUTDOWN: Alarm Number 1 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Figure 95: POWER-SHUTDOWN: Alarm Number 2 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Figure 96: SUBRACK-POWER: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Figure 97: TEMPERATURE-WARNING (BTS): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Figure 98: TEMPERATURE-WARNING (TRE): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Figure 99: FATAL TEMPERATURE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Figure 100: HW-DEGRADED (BTS): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Figure 101: HW-DEGRADED (EACB): BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Figure 102: HW-DEGRADED (EACB): BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . 198 Figure 103: HW-DEGRADED (EACB): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Figure 104: HW-DEGRADED (CCF): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Figure 105: HW-FAILURE (EACB): Alarm Number 2 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Figure 106: HW-FAILURE (EACB): Alarm Number 3 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Figure 107: HW-FAILURE (CCF): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Figure 108: LNK-AL: G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Figure 109: LNK-AL: G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Figure 110: LNK-DBLE-AL: G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Figure 111: LNK-DBLE-AL: G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Figure 112: RX-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Figure 113: RX-DBLE-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Figure 114: RX-SYN-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Figure 115: RX-SYN-DBLE-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Figure 116: VSWR-AL: G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Figure 117: VSWR-AL: G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Figure 118: TX-POWER-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Figure 119: TEMP-AL: G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
10 / 590
Figures
Figure 120: TEMP-AL: G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Figure 121: TX-SYN-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Figure 122: FCLK-AL (CU): G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Figure 123: FCLK-AL (CU): G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Figure 124: INTERNAL-FCLK (CU): G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Figure 125: INTERNAL-FCLK (CU): G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Figure 126: OBCLK-AL (CU): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Figure 127: INTERNAL-OBCLK (CU): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Figure 128: REF-FREQ-AL (CU): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Figure 129: INTERNAL-REF-FRQ (CU): G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Figure 130: INTERNAL-REF-FRQ (CU): G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Figure 131: ANTENNA-VSWR: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Figure 132: FRONTEND-RELAY-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Figure 133: FRONTEND-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Figure 134: FATAL-FRONTEND-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Figure 135: BCCH-SWITCH: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Figure 136: BCCH-SWITCH-FATAL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 Figure 137: RTMA-ALARM: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Figure 138: PERU-ALARM: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 Figure 139: TEST-ABORTED: G1/G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Figure 140: ALARM-TEST-FAILURE: G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Figure 141: ALARM-TEST-FAILURE: G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Figure 142: RF-FAULT (CU): G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Figure 143: RF-FAULT (CU): G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Figure 144: RF-FAULT (RA): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Figure 145: FRONTEND-AMP-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Figure 146: DATA-INCONSIS-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Figure 147: RTC-OUT-OF-BAND-ALARM: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 Figure 148: RTC-FINE-TUNING-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Figure 149: RTC-PARKING-FAILURE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Figure 150: RTC-SELFTEST-FAILURE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Figure 151: RTC-EXT-CONN-LOST: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Figure 152: RTC-DETECTOR-FAILURE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 Figure 153: MISSING-ENTRY-IN-CPF: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Figure 154: MISSING-ENTRY-IN-CPF: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Figure 155: INCONSIST-ASSHW-ACTHW: Alarm Number 2 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . 294 Figure 156: INCONSIST-ASSHW-ACTHW: Alarm Number 4 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . 295 Figure 157: INCONSIST-ASSHW-ACTHW: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Figure 158: CONFIG-FAIL (CU): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 Figure 159: CONFIG-FAIL (RA): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
11 / 590
Figures
Figure 160: RESET (CU): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Figure 161: NO-ANSWER-DCL (CU): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Figure 162: NO-ANSWER-DCL (RA): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Figure 163: SELF-TEST-AL (CU): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Figure 164: SELF-TEST-DBLE-AL (CU): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Figure 165: Q1-RELAY-FAULT (CU): G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Figure 166: Q1-RELAY-FAULT (CU): G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 Figure 167: Q1-RELAY-FAULT (RA): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Figure 168: AL-LIST-ER: DRFU Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Figure 169: AL-LIST-ER: OMU Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Figure 170: MCL-LINK: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Figure 171: BSI-LINK-0: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 Figure 172: BOTH-BSI-LINKS: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Figure 173: FHI-LK0-FUL-UNV: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Figure 174: FHI-LK1-FUL-UNV: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Figure 175: FHU-DUMMY-BURST-GEN-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Figure 176: HW-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Figure 177: BOTH-FHI-LINKS: G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 Figure 178: BOTH-FHI-LINKS: G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Figure 179: BOTH-CLOCK-LINKS: G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Figure 180: BOTH-CLOCK-LINKS: G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 Figure 181: FU-FAULT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 Figure 182: MISSING-ENTRY-IN-CPF: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 Figure 183: INCONSIST-ASSHW-ACTHW: Alarm Number 1 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . 347 Figure 184: INCONSIST-ASSHW-ACTHW: Alarm Number 8 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . 348 Figure 185: INCONSIST-ASSHW-ACTHW: Alarm Number 9 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . 349 Figure 186: INCONSIST-actHW-logConfig: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 Figure 187: INCONSIST-actHW-BTSparam: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Figure 188: SW-DLL-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Figure 189: CONFIG-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 Figure 190: RESTART: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Figure 191: NO-ANSWER-DCL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Figure 192: IGNORE EQUIPMENT OVER 12 TRE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Figure 193: TOO MANY PLUGGED MODULES: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 Figure 194: TB-FAILURE: G1/G2 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 Figure 195: Q1-FAILURE: G1/G2 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Figure 196: RACH-CATCHER-LOST: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 Figure 197: BCB-LINK: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 Figure 198: BCB-LINK: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Figure 199: IOM-LINK: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
12 / 590
Figures
Figure 200: IOM-LINK: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 Figure 201: MODULE-INSERTED: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Figure 202: MODULE-INSERTED: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . 382 Figure 203: CONFIG-FAIL: G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Figure 204: CONFIG-FAIL: G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 Figure 205: RESET (EACB): G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 Figure 206: RESET (EACB): G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 Figure 207: NO-ANSWER-DCL: G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 Figure 208: NO-ANSWER-DCL: G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 Figure 209: SELF-TEST-AL: G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 Figure 210: SELF-TEST-AL: G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 Figure 211: Q1-RELAY-FAULT: G1 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 Figure 212: Q1-RELAY-FAULT: G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 Figure 213: EXT-ALARM [9,1...56] : Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 Figure 214: [9,1] EXT-ALARM: G2 BTS and BTS A9100 Default Corrective Actions . . . . . . . . . . . . . . . . . . 405 Figure 215: [9,1] EXT-ALARM: BTS A9110/A9110-E Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . 406 Figure 216: [9,2] EXT-ALARM: Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 Figure 217: [9,3] EXT-ALARM: BTS G2 and A9100 Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . 410 Figure 218: [9,3] EXT-ALARM: BTS A9110/A9110-E Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . 411 Figure 219: [9,4] EXT-ALARM: Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Figure 220: [9,5] EXT-ALARM: G2 BTS and BTS A9100 Default Corrective Actions . . . . . . . . . . . . . . . . . . 415 Figure 221: [9,6] EXT-ALARM: G2 BTS and BTS A9100 Default Corrective Actions . . . . . . . . . . . . . . . . . . 417 Figure 222: [9,7] EXT-ALARM: G2 BTS and BTS A9100 Default Corrective Actions . . . . . . . . . . . . . . . . . . 419 Figure 223: [9,8] EXT-ALARM: G2 BTS and BTS A9100 Default Corrective Actions . . . . . . . . . . . . . . . . . . 421 Figure 224: [9,9] EXT-ALARM: Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 Figure 225: [9,10] EXT-ALARM: Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425 Figure 226: [9,11] EXT-ALARM: Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 Figure 227: [9,12] EXT-ALARM: G2 BTS Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 Figure 228: [9,13] EXT-ALARM: BTS G2 and A9100 Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . 431 Figure 229: [9,14] EXT-ALARM: G2 BTS and BTS A9100 Default Corrective Actions . . . . . . . . . . . . . . . . . 433 Figure 230: [9,15] EXT-ALARM: G2 BTS and BTS A9100 Default Corrective Actions . . . . . . . . . . . . . . . . . 435 Figure 231: [9,16] EXT-ALARM: G2 BTS and BTS A9100 Default Corrective Actions . . . . . . . . . . . . . . . . . 437 Figure 232: [9,17] EXT-ALARM: Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 Figure 233: [9,18] EXT-ALARM: Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Figure 234: [9,19] EXT-ALARM: Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Figure 235: [9,20] EXT-ALARM: BTS A9100 Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445 Figure 236: [9,21] EXT-ALARM: BTS A9100 Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 Figure 237: [9,22] EXT-ALARM: Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 Figure 238: [9,23] EXT-ALARM: Default Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 Figure 239: [9,24] EXT-ALARM: G2 BTS and BTS A9100 Default Corrective Actions . . . . . . . . . . . . . . . . . 453
13 / 590
Figures
Figure 240: RSL-LINK: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 Figure 241: RSL-LINK: G2 BTS Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474 Figure 242: RX-CABLE (TRE):Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 Figure 243: RX-CABLE (RA): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478 Figure 244: TRE-VSWR: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480 Figure 245: TRE-VSWR: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481 Figure 246: ANTENNA-VSWR-WARNING: Corrective Actions for A9100 BTS . . . . . . . . . . . . . . . . . . . . . . . . 484 Figure 247: ANTENNA-VSWR-WARNING: Corrective Actions for A9110-E BTS . . . . . . . . . . . . . . . . . . . . . . 485 Figure 248: ANTENNA-VSWR-URGENT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Figure 249: ANTENNA-VSWR-URGENT: Corrective Actions, continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 Figure 250: ANTENNA-VSWR-URGENT: Corrective Actions, continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 Figure 251: MODULE-FRAME-SIGNAL (TRE): BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . 491 Figure 252: MODULE-FRAME-SIGNAL (TRE): BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . 492 Figure 253: MODULE-FRAME-SIGNAL (RA): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 Figure 254: MODULE-CLOCK-SIGNAL (TRE): BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . 496 Figure 255: MODULE-CLOCK-SIGNAL (TRE): BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . 497 Figure 256: MODULE-CLOCK-SIGNAL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 Figure 257: MODULE-NOT-PRESENT (TRE): BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . 501 Figure 258: MODULE-NOT-PRESENT (TRE): BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . 502 Figure 259: MODULE-NOT-PRESENT (RA): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504 Figure 260: IOM-DISCONNECTION (TRE): BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . 506 Figure 261: IOM-DISCONNECTION (TRE): BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . 507 Figure 262: IOM-DISCONNECTION (RA): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509 Figure 263: HW-DEGRADED (TRE): BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 Figure 264: HW-DEGRADED (TRE): BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . 512 Figure 265: HW-DEGRADED (RA): BTS A9100, Alarm Number 3 Corrective Actions . . . . . . . . . . . . . . . . . 514 Figure 266: HW-DEGRADED (RA): BTS A9100, Alarm Number 4...11 and 13 Corrective Actions . . . . . . 515 Figure 267: HW-DEGRADED (RA): BTS A9100, Alarm Number 3 Corrective Actions . . . . . . . . . . . . . . . . . 516 Figure 268: HW-FAILURE (TRE): BTS A9100, Alarm Number 1, 12 and 13 Corrective Actions . . . . . . . . 519 Figure 269: HW-FAILURE (TRE): BTS A9100, Alarm Number 1, 3...11 and 15 Corrective Actions . . . . . . 520 Figure 270: HW-FAILURE (TRE): BTS A9100, Alarm Number 14 Corrective Actions . . . . . . . . . . . . . . . . . . 521 Figure 271: HW-FAILURE (TRE): BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 Figure 272: HW-FAILURE (RA): BTS A9100, Alarm Number 2 and 12 Corrective Actions . . . . . . . . . . . . . 524 Figure 273: HW-FAILURE (RA): BTS A9100, Alarm Number 10 Corrective Actions . . . . . . . . . . . . . . . . . . . 525 Figure 274: HW-FAILURE (RA): BTS A9100, Alarm Number 14 Corrective Actions . . . . . . . . . . . . . . . . . . . 526 Figure 275: HW-FAILURE (RA): BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527 Figure 276: RESTART (TRE): BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 Figure 277: RESTART (TRE): BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 Figure 278: RESTART (RA): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 Figure 279: LOOP-TO-EQUIPMENT: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
14 / 590
Figures
Figure 280: LOOP-TO-EQUIPMENT: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . 536 Figure 281: LOSS-OF-INCOMING-SIGNAL: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . 538 Figure 282: LOSS-OF-INCOMING-SIGNAL: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . 539 Figure 283: AIS-2M: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541 Figure 284: LOSS-OF-FRAME-ALIGNMENT: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . 543 Figure 285: LOSS-OF-FRAME-ALIGNMENT: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . 544 Figure 286: LOSS-OF-CRC-MULTIFRAME-ALIGNMENT: BTS A9100 Corrective Actions . . . . . . . . . . . . . 546 Figure 287: LOSS-OF-CRC-MULTIFRAME-ALIGNMENT: BTS A9110/A9110-E Corrective Actions . . . . 547 Figure 288: ERROR-RATE>E-3: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549 Figure 289: ERROR-RATE>E-3: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550 Figure 290: ERROR-RATE>E-4: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552 Figure 291: ERROR-RATE>E-4: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553 Figure 292: ERROR-RATE>E-6: BTS A9100 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555 Figure 293: ERROR-RATE>E-6: BTS A9110/A9110-E Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556 Figure 294: REMOTE-ALARM-INDICATION: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558 Figure 295: G1, Mark I, TLV53 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567 Figure 296: G1, Mark II, TLV53 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567 Figure 297: G2, FU2, TLV53 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 Figure 298: G1, FU3, TLV53 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 Figure 299: G1, Mark I TLV59 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
15 / 590
Tables
Tables
Table 1: SBL state to MO state translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Table 2: OMC-R to LMT state change commands translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Table 3: Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Table 4: Alarm Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Table 5: Alarm [2,247] TLV Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 Table 6: Alarm [2,248] TLV Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 Table 7: Alarms [7,3], [7,5] to [7,8] and [7,31] to [7,35] TLV Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561 Table 8: Alarm [7,245] TLV Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561 Table 9: Alarm [7,248] TLV Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561 Table 10: NACK Types for TLV35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562 Table 11: Error Numbers for TLV35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565 Table 12: Field Definitions for Fourth and Fifth Bytes of TLV53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569 Table 13: FU Alarms and Alarm Type for TLV53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 Table 14: Bit value description (6th and 7th byte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 Table 15: 8th byte description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572 Table 16: TLV57 Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 Table 17: TLV57 Error Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 Table 18: TLV58 Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574 Table 19: TLV58 Software Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574 Table 20: TLV58 Board Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575 Table 21: TLV58 DSP Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575 Table 22: TLV59 FU Alarm Type 20 Alarms for G1/G2 and Micro-BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577 Table 23: TLV59 for TRE faults of Evolium BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579 Table 24: TLV59 for AN faults of Evolium BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580 Table 25: TLV59 for TRANS&CLOCK faults of Evolium A9100 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581 Table 26: TLV61 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582 Table 27: TLV61 Board Identification Bytes for G1/G2 and Micro-BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583 Table 28: TLV61 Board Identification Bytes for Evolium BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583 Table 29: TLV82 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585 Table 30: TLV83 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587 Table 31: TLV84 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587 Table 32: TLV120 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588 Table 33: TLV243 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
16 / 590
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: Whats New
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.
In Edition 13
The following updates were performed: For alarm [5,237] HW-DEGRADED (EACB) (Section 6.19.2) the alarm numbers 11 to 17 were added For alarm [10,237] HW-DEGRADED (RA) (Section 11.10.2) the alarm number 13 was added.
In Edition 12
The following updates were perfomed: Alarm number 3 was added for alarm [8,247] RESET (BTS) (Section 9.12.1) Alarm number 13 was added for alarm [10,237] HW-DEGRADED (TRE) (Section 11.10.1). Corrective action for alarm [2,1] LOSS OF TWIN CONFIGURATION (Section 3.1) was detailed.
In Edition 11
Description improvement in [9,1...56] EXT-ALARM (Section 10.1).
In Edition 10
Corrective action for alarm [10,239] HW-FAILURE (Section 11.11) number 1, 12 and 13 was updated.
17 / 590
Preface
In Edition 09
Alarm name was corrected for [8,5] TOO MANY PLUGGED MODULES (Section 9.3).
In Edition 08
The following alarms were added: [2,1] LOSS OF TWIN CONFIGURATION (Section 3.1) [8,4] IGNORE EQUIPMENT OVER 12 TRE (Section 9.2) [8,5] TOO MANY PLUGGED MODULES (Section 9.3).
In Edition 07
Description improvement for the alarms: [5,11] POWER-SUPPLY-U (Section 6.9) [5,12] POWER-SUPPLY-NU (Section 6.10) [5,20] MAINS-AL (Section 6.14).
In Edition 06
Description improvement for alarm [10,248] RESTART (Section 11.12)
In Edition 05
Description improvement for alarm [10,11] ANTENNA-VSWR-WARNING (Section 11.4).
In Edition 04
Description improvement for alarm [5,1] FAN-ALARM (Section 6.2).
In Edition 03
Description improvement for alarm [3,14] WRONG-CONFIGURATION (RA) (Section 4.6.2).
In Edition 02
Description improvement for alarm [10,1] RSL-LINK (Section 11.1).
In Edition 01
Creation in B9.
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 O&M concepts for the BSS Fault management Use of OMC-R and BTS terminals SBL hierarchies of the BTS Telecommunications techniques including line transmission and switching.
18 / 590
1 Introduction
1 Introduction
This section describes the structure of the BTS alarm messages.
19 / 590
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 A1353-RA 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
20 / 590
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 A1353-RA Surveillance Handbook for use of the OMC-R commands, see document BTS Terminal 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
21 / 590
1 Introduction
1.3 A1353-RA Alarm Surveillance Information

In the Alarm Surveillance of the A1353-RA 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. AS 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 A9100 outdoor only: If the alarm message displays the RIT location A,0,0, the RIT is located in the COMI/CODI side compartment.
22 / 590
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 AS on-line help for more detailed information on AS.
23 / 590
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 Terminal 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.
24 / 590
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 A9100 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.
25 / 590
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 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 digits is described in section 13. Decoding Additional Information from Alarms Decoding BTS or BSC additional information must only be attempted by Alcatel 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 support office.
26 / 590
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.
27 / 590
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.
28 / 590
1 Introduction
[1,1] OCXOAL
Start field with alarm number and alarm name
Lock Function CLLK Remote action fields Unlock Function CLLK
Clock operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
G1: Replace MCLU, MCLR
OR
G1: Replace MFG
OR
G2: Replace STSE, STSP, STSR
Onsite action fields
Clock 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.
29 / 590
1 Introduction
1.5.3 Additional Information

section BTS Alarm Additional Information (Section 13) 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 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 support office.
30 / 590
2 Class 1: CLK Alarms

This section defines the alarms for the Class 1: CLK alarm class.
31 / 590
2.1 [1,1] OCXO-AL

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number OCXO-AL Equipment Timing Problem Major (PMA) The 13 MHz signal from the indicated MFG is missing. 1: MFG 1 2: MFG 2
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. (X) Impact Loss Degradation BSS X(no red.) Cell(s) X(no red.) Signaling X(no red.) Calls X(no red.) -
32 / 590
2.1.1 G1/G2 BTS Corrective Actions

[1,1] OCXOAL
Lock Function CLLK
Unlock Function CLLK
Clock operational?
yes
Alarm solved
no
Onsite
Onsite
G1: Replace MFG
Onsite OR
OR
Clock operational?
yes
Alarm solved
Figure 2: OCXO-AL: G1/G2 BTS Corrective Actions
33 / 590
2.2 [1,3] CLOCK-FREQ-AL

specific Problems event Type probable Cause perceived Severity Alarm Description CLOCK-FREQ-AL Equipment Timing Problem Major (PMA) The clock signal from the MFG is not reliable due to the reason indicated by the Alarm Number. 1: Default value (G1 & G2 BTS: The problem cannot be analyzed further). 2: The operational temperature is outside the permitted limits (G2 BTS). 3: There is a tuning problem due to malfunctioning of the digital -analog-loop (G2 BTS). 4: EEPROM problems detected (G2 BTS).
Alarm Number
If the CLLK is redundant on this BTS, the telecom functions are not affected. If, however, no redundancy is available, the clock system is not reliable. Thus the telecom functions on the cell(s) fed by the indicated MFG can be affected. Degradation in transmission quality can arise on these cell(s), e.g., BER increasing, interference and handover problems. Impact Loss Degradation BSS X(no red.) Cell(s) X(no red.) Signaling X(no red.) Calls X(no red.)
Required tools and materials: Thermometer Replacement tools, see appropriate replacement procedure.
34 / 590
2.2.1 G1/G2 BTS, Alarm Number 1, 3 & 4 Corrective Actions

Alarm Number 1,3,4
[1,3] CLOCKFREQAL
Lock Function CLLK
Clock operational?
yes
Alarm solved
no
Alarm Number 1 only

Does several BTS, using the PCM via same BSC, have same alarm? yes
Solve PCM link problem
no Line alarms (e.g. AIS) events?
yes
Solve line alarm
no
Replace modules
Figure 3: CLOCK-FREQ-AL: G1/G2 BTS, Alarm Number 1, 3 & 4, Corrective Actions at OMC-R
35 / 590
Replace modules
Onsite
Check BTS status (logical configurations)
Onsite
Onsite
G1: Replace MFG
Onsite
OR
OR
Clock operational?
yes
Alarm solved
Figure 4: CLOCK-FREQ-AL: G1/G2 BTS, Alarm Number 1, 3 & 4, Corrective Actions On-Site
36 / 590
2.2.2 G2 BTS, Alarm Number 2 Corrective Actions

Alarm Number 1
[1,3] CLOCKFREQAL
Lock Function CLLK
no
Clock operational?
yes
Alarm solved
Fan alarm events (e.g. alarms 5,1; 5,2; 5,3)?
no
Was oscillator just plugged in? no
yes Wait 15 minutes
yes
Onsite
Check ambient temperature
Solve fan alarms
Onsite
Ambient temperature outside permitted limits? yes Reduce ambient temperature
Recheck alarm
no yes
Contact System Support
Alarm solved
Clock operational?
Figure 5: CLOCK-FREQ-AL: G2 BTS, Alarm Number 2 Corrective Actions
37 / 590
2.3 [1,6] MCL-FATAL-AL

specific Problems event Type probable Cause perceived Severity Alarm Description MCL-FATAL-AL Equipment Equipment Malfunction Major (PMA) Fatal internal alarm on the Clock Unit.
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 A9100: 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.) -
38 / 590

[1,6] MCLFATALAL
Lock Function CLLK
Clock operational?
yes
Alarm solved
no
Onsite
Check BTS status (logical configuration)
Onsite
Onsite
G1: Replace MFG
Onsite
OR
OR
Clock operational?
yes
Alarm solved
Figure 6: MCL-FATAL-AL: G1/G2 BTS Corrective Actions
39 / 590
2.3.2 BTS A9100 Corrective Actions

[1,6] MCLFATALAL
Reset Function BTS
Clock operational?
yes
Alarm solved
no
Onsite
Replace SUMP, SUMA
Clock operational?
yes
Alarm solved
Figure 7: MCL-FATAL-AL: BTS A9100 Corrective Actions
40 / 590
2.3.3 BTS A9110/A9110-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 8: MCL-FATAL-AL: BTS A9110/A9110-E Corrective Actions
41 / 590
2.4 [1,7] MCL-TEST-AL

specific Problems event Type probable Cause perceived Severity Alarm Description MCL-TEST-AL Equipment Equipment Malfunction Major (PMA) There is an internal selftest alarm on a clock unit.
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.) -
42 / 590
2.4.1 Corrective Actions

[1,7] MCLTESTAL
Lock Function CLLK
Clock operational?
yes
Alarm solved
no
Onsite
Onsite
G1: Replace MFG
Onsite OR
OR
Clock operational?
yes
Alarm solved
Figure 9: MCL-TEST-AL: Corrective Actions
43 / 590
2.5 [1,8] MCL-DRV-AL

specific Problems event Type probable Cause perceived Severity Alarm Description MCL-DRV-AL Equipment InputOutputDeviceError Major (PMA) There is a fault on the output drivers of a clock unit.
44 / 590

[1,8] MCLDRVAL
Lock Function CLLK
Clock operational?
yes
Alarm solved
no
Onsite
Onsite
G1: Replace MFG
Onsite OR
OR
Clock operational?
yes
Alarm solved
Figure 10: MCL-DRV-AL: Corrective Actions
45 / 590
2.6 [1,11] MCLU-FAULT

specific Problems event Type probable Cause perceived Severity Alarm Description MCLU-FAULT Equipment Timing Problem Minor (DMA) The reporting clock unit has detected a fault on the MFG indicated. However, this fault has not yet been detected by the redundant clock unit. The input driver of the reporting clock unit may be faulty, or a replacement of a faulty MFG can still be underway. 1: MFG 1 2: MFG 2
Alarm Number
Telecom functions are not affected. Impact Loss Degradation BSS Cell(s) Signaling Calls -
46 / 590

[10,11] ANTENNAVSWRWARNING
Lock Function RA
Unlock Function RA
TRE alarm events?
yes
Solve that alarm first
no
RA operational?
yes
Alarm solved
no
Onsite Onsite
Check VSWR Thresholds
Check BTS status
Onsite
Onsite
Check cables to transmitter antenna visually and electrically.
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 11: MCLU-FAULT: Corrective Actions
47 / 590
2.7 [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 A9100: 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.) -
48 / 590

[1,12] CLOCKFAULT
Lock Function CLLK
Onsite
Clock operational? no Check cables amd connectors to cabinet
Onsite
Check CLDBs of cabinet
yes Alarm solved Clock operational? yes Alarm solved
no
Onsite
Onsite
G1: Replace MFG
Onsite
OR
OR
Clock operational?
yes
Alarm solved
Figure 12: CLOCK-FAULT: G1/G2 BTS Corrective Actions
49 / 590

[1,12] CLOCKFAULT
Reset Function BTS
Clock operational?
yes
Alarm solved
no
Onsite
Replace SUMP, SUMA
Clock operational?
yes
Alarm solved
Figure 13: CLOCK-FAULT: BTS A9100 Corrective Actions
50 / 590

[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 14: CLOCK-FAULT: BTS A9110/A9110-E Corrective Actions
51 / 590
2.8 [1,22] MCLR-EA-AL

specific Problems event Type probable Cause perceived Severity Alarm Description MCL-EA-AL Equipment Timing Problem Major (PMA) At least one of the clock signals (Frame Number, Frame Clock, Octal Bit Clock, 2.6 MHz signal) sent by the clock unit in the master BTS (G1 BTS: MCLU, G2 BTS: STSE) is not received by the clock unit in the slave BTS (G1 BTS: MCLR, G2 BTS: STSR). If an alarm on the feeding clock unit of the master BTS is still outstanding, the failure is due to external reasons.
52 / 590

[1,22] MCLREAAL
Master clock alarm(s) events?
yes
Solve Master clock alarm
no
Lock Function CLLK
Clock operational?
yes
Alarm solved
no
Onsite
Onsite
G1: Replace MFG
Onsite
OR
OR
Clock operational?
yes
Alarm solved
Figure 15: MCL-EA-AL: Corrective Actions
53 / 590
2.9 [1,23] PCM-SYNC-AL

specific Problems event Type probable Cause perceived Severity Alarm Description PCM-SYNC-AL Communication Loss Of Signal Minor (DMA) The MFG has lost synchronisation with the signal from the PCM Abis Highway.
54 / 590

[1,23] PCMSYNCAL
PCM Abis, AInterface, MSC or signal generator alarm(s) events?
no
Lock Function CLLK
yes Solve that alarm(s) first PCM Clock operational? yes Alarm solved
no
Onsite
G1:Check cables/connectors transmission system to MFGP
Onsite
G2: Check cables/connectors transmission system to STSP
OR
PCM Clock operational?
yes
Alarm solved
no
Onsite
Onsite
G1: Replace MFG
Onsite
OR
OR
PCM Clock operational?
yes
Alarm solved
Figure 16: PCM-SYNC-AL: G1/G2 BTS Corrective Actions
55 / 590
2.10 [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.
56 / 590

[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 17: MCL-XCLK: BTS A9100 Corrective Actions
57 / 590

[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 18: MCL-XCLK: BTS A9110/A9110-E Corrective Actions
58 / 590
2.11 [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.

Contact your Alcatel system support.
59 / 590
2.12 [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.
Required tools and materials: PCM test tools GPS test tools Replacement tools, see appropriate replacement procedure.
60 / 590
2.12.1 BTS A9100, Alarm Number 1 Corrective Actions

Alarm Number 1
[1,237] HWDEGRADED
Line alarm (e.g. AIS) events?
no
Reset Function BTS
yes
Onsite
no Check BTS status (logical configurations)
Clock operational?
Check PCM clock link
yes Alarm solved Clock operational?
yes
Alarm solved
no
Onsite
After 30 s switch BTS on
Onsite
Switch BTS off
Onsite
Clock operational? yes no Replace SUMP, SUMA
Alarm solved
Clock operational?
yes
Alarm solved
Figure 19: HW-DEGRADED: BTS A9100, Alarm Number 1 Corrective Actions
61 / 590
2.12.2 BTS A9100, Alarm Number 2 Corrective Actions

Alarm Number 2
[1,237] HWDEGRADED
Reset Function BTS
Onsite
no Check BTS status (logical configurations)
Clock operational?
Check GPS Equipment
yes Alarm solved
Clock operational?
yes
Alarm solved
no
Onsite
After 30 s switch BTS on
Onsite
Switch BTS off
Onsite
Clock operational? yes no Replace SUMP, SUMA
Alarm solved
Clock operational?
yes
Alarm solved
Figure 20: HW-DEGRADED: BTSA9100, Alarm Number 2 Corrective Actions
62 / 590
2.12.3 BTS A9110/A9110-E , Alarm Number 1 Corrective Actions

Alarm Number 1
[1,237] HWDEGRADED
Line alarms (e.g. AIS) events?
no
Onsite
Onsite
yes Solve that alarm(s) first no Check logical configuration & PCM clock input
OR Onsite
Clock operational?
yes Alarm solved
OR Onsite
Onsite
Onsite
Figure 21: HW-DEGRADED: BTS A9110/A9110-E , Alarm Number 1 Corrective Actions
63 / 590
2.12.4 BTS A9110/A9110-E, Alarm Number 2 Corrective Actions

Alarm Number 2
[1,237] HWDEGRADED
Onsite
Onsite
OR Onsite
Clock operational?
no
Check logical configuration & GPS Equipment
yes Alarm solved
OR Onsite
Onsite
Onsite
Figure 22: HW-DEGRADED: BTS A9110/A9110-E ,Alarm Number 2 Corrective Actions
64 / 590
2.13 [1,240] MISSING-ENTRY-IN-CPF

specific Problems event Type probable Cause perceived Severity Alarm Description MISSING-ENTRY-IN-CPF Processor Error Configuration Or Customization Error Major (PMA) An expected entry in the OMU CPF was not found. Equipment identification for the MCLU/MCLR is not included in the OMU CPF.
If the BTS clock system has redundancy, telecom functions are not affected. If there is no redundancy, the cell is lost. Impact Loss Degradation BSS X(no red.) Cell(s) X(no red.) Signaling X(no red.) Calls X(no red.) -
65 / 590

[1,240] MISSINGENTRYINCPF
Check existing hardware against populated hardware in the OMU CPF for wrong BTS family, characteristic and parameter entries. Use:
Check Cell Activation
Check Cell Logical Parameters
Check Cell Telecom Impact
Check Cell with Hardware
Choose the correct CPF settings by selecting the appropriate BTS characteristics. Use:
Change Cell Type
Modify BTS Characteristics
Modify BTS Hardware Capability
Clock operational?
yes
Alarm solved
Figure 23: MISSING-ENTRY-IN-CPF: Corrective Actions
66 / 590
2.14 [1,241] INCONSIST-ASSHW-ACTHW

specific Problems event Type probable Cause perceived Severity Alarm Description INCONSIST-ASSHW-ACTHW Processing Error Configuration Or Customization Error Major (PMA) The equipped BTS hardware does not match to the assumed hardware capabilities. 3: There is a fault on the assumed hardware, the capability is that of a master BTS but the actual capability is that of a slave (and vice versa). 5: The BTS hardware does not provide extended cell support, but it should be configured as an extended cell.
Alarm Number
If the BTS clock system has redundancy, telecom functions are not affected. If there is no redundancy, the cell is lost. Impact Loss Degradation BSS X(no red.) Cell(s) X(no red.) Signaling X(no red.) Calls X(no red.) -
67 / 590
2.14.1 Alarm Number 3 Corrective Actions

Alarm Number 3
[1,241] INCONSISTASSHWACTHW
Check assumed BTS hardware master/slave capability against the clock units in the BTS. Use:
Onsite Modify actual BTS hardware capability by replacing existing BTS entity by appropriate BTS hardware entity, as descibed in the CMA
Modify assumed BTS Hardware Capability
OR
Onsite
Onsite
G1: Replace MFG
Onsite OR
OR
Clock operational?
yes
Alarm solved
Figure 24: INCONSIST-ASSHW-ACTHW, Alarm Number 3: Corrective Actions
68 / 590

Alarm Number 5
Check cell range definition against clock units. Use:
Onsite
OR
Modify actual BTS hardware capability by replacing existing BTS entity by appropriate BTS hardware entity, as descibed in the CMA
Onsite
Clock operational?
yes
Alarm solved
Figure 25: INCONSIST-ASSHW-ACTHW, Alarm Number 5: Corrective Actions
69 / 590
2.15 [1,246] CONFIG-FAIL

specific Problems event Type probable Cause perceived Severity Alarm Description CONFIG-FAIL Processing Error Configuration Or Customization Error Major (PMA) The configuration has failed for a Clock Unit.
If the clock system is redundant on this BTS and only one Clock Unit configuration failed, the telecom functions are not affected. If, however, no redundancy is available or the configuration of both Clock Units on the BTS failed, the cell(s) fed by the clock system are lost. Impact Loss Degradation BSS X(no red.) Cell(s) X(no red.) Signaling X(no red.) Calls X(no red.) -
70 / 590

[1,246] CONFIGFAIL
If both Clock Units in BTS report this alarm, there is a problem with the parameters (List of Clock Unit delays). If alarm is reported at powerup, there is also a Q1 failure, which provoked the configuration failure.
Check validity of parameters (BTS hardware configuration) on Clock Unit delays. Use Check Cell with Hardware
Restart OMU
yes Clock operational? Alarm solved
no
Onsite
Onsite
G1: Replace MFG
Onsite
OR
OR
Clock operational?
yes
Alarm solved
Figure 26: CONFIG-FAIL: Corrective Actions
71 / 590
2.16 [1,247] RESET

specific Problems event Type probable Cause perceived Severity Alarm Description RESET Processing Error Software Error Warning (MI) The Clock Unit has performed an auto-reset, e.g. following the expiry of a watchdog timer during operational mode or due to a pushbutton reset.
If the clock system is redundant on this BTS the telecom functions are not affected. If, however, no redundancy is available, the call(s) on that BTS are lost due to the lack of clock signals and are not resumed later. Signaling is resumed as soon as the Clock Unit is available again. Impact Loss Degradation BSS X(no red.) Cell(s) X(no red.) Signaling X(no red.) Calls X(no red.) -
72 / 590

[1,247] RESET
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 27: RESET: BTS A9100 Corrective Actions
73 / 590

[1,247] RESET
Reset Function BTS
Clock operational?
yes
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 28: RESET: BTS A9110/A9110-E Corrective Actions
74 / 590
2.17 [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.
75 / 590

[1,248] RESTART
Reset Function BTS
Clock operational?
yes
no
no
Alarm solved
yes
Onsite
Replace SUMP, SUMA
Clock operational?
yes
Alarm solved
Figure 29: RESTART: BTS A9100 Corrective Actions
76 / 590

[1,248] RESTART
Reset Function BTS
Clock operational?
yes
no
Alarm solved
no
yes
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Clock operational? no Replace BTS A910 BTS operational? yes Alarm solved
yes Alarm solved
Figure 30: RESTART: BTS A9110/A9110-E Corrective Actions
77 / 590
2.18 [1,250] NO-ANSWER-DCL

specific Problems event Type probable Cause perceived Severity Alarm Description NO-ANSWER-DCL Processing Error Underlying Resource Unavailable Major (PMA), Minor (DMA) Major (PMA): The configuration/reconfiguration is not possible because the Clock Unit is not answering to commands. Minor (PMA): No answer on the Q1 bus from a Clock Unit, for more than two polling cycles, to polling by the OMU.
Major (PMA): If the clock system is redundant on this BTS, the telecom functions are not affected. If, however, no redundancy is available, the cell will be lost because no configuration can be set. Impact Loss Degradation BSS X(no red.) Cell(s) X(no red.) Signaling X(no red.) Calls X(no red.) -
Minor (DMA): In case of Q1 malfunction there is no disturbance of the telecom applications. In case of clock malfunction and the clock system is redundant on this BTS, there is no disturbance of the telecom application. If, however, no redundancy is available, the result depends on the clock fault, the clocks can eventually go on with the previous configuration. If the fault is fatal, others alarms will appear on other equipment (ex FU on Token bus). Impact Loss Degradation BSS X Cell(s) X(no red.) Signaling X(no red.) Calls X(no red.) -
78 / 590

[1,250] NOANSWERDCL
Lock Function CLLK
Onsite
no Check Q1 bus cable and connectors between OMU and Clock Unit
Clock operational?
yes
Alarm solved
Clock operational?
yes
Alarm solved
no
Onsite
Onsite
G1: Replace MFG
Onsite
OR
OR
Clock operational?
yes
Alarm solved
Figure 31: NO-ANSWER-DCL: Corrective Actions
79 / 590
2.19 [1,255] Q1-RELAY-FAILURE

specific Problems event Type probable Cause perceived Severity Alarm Description Q1-RELAY-FAILURE Equipment Equipment Malfunction Minor (DMA) The Clock Unit cannot disconnect itself from the Q1 Bus.
80 / 590

[1,255] Q1RELAYFAILURE
Lock Function CLLK
Clock operational?
yes
Alarm solved
no
Onsite
Onsite
G1: Replace MFG
Onsite OR
OR
Clock operational?
yes
Alarm solved
Figure 32: Q1-RELAY-FAILURE: Corrective Actions
81 / 590
82 / 590
3 Class 2: OMU Alarms

This section defines the alarms for the Class 2: OMU alarm class.
83 / 590
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.
84 / 590

[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 33: LOSS OF TWIN CONFIGURATION Corrective Actions
85 / 590
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 1: Power-on reset. 2: Reset button pressed by operator. 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.
86 / 590
3.2.1 Alarm Number 1,2 Corrective Actions

[2,247] RESET
Poweron reset?
yes
no
After automatic reset procedure OMU becomes operational yes
Alarm solved
Reset button pressed by operator?
no
Onsite
Check power supply
OMU operational?
yes
Alarm solved
Figure 34: RESET: Alarm Number 1,2 Corrective Actions
87 / 590

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
G1: Replace OMUA
Onsite
G2: Replace SCFE
Onsite OR
A9100: Replace SUMP, SUMA
Onsite
A910: Replace BTS A910
OR
OR
OMU operational?
yes
Alarm solved
Figure 35: 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
88 / 590

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
89 / 590

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

The power supply is again available for the BTS.
90 / 590
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.
91 / 590
92 / 590
4 Class 3: SW-AN Alarms

This section defines the alarms for the Class 3: SW-AN alarm class.
93 / 590
4.1 [3,0] UNKNOWN-UNIT

specific Problems event Type probable Cause perceived Severity Alarm Description UNKNOWN-UNIT Processing Error Configuration Or Customization Error Warning (MI) A message has been received by the OMU, originating from an unknown unit, due to a software error.

If this alarm is sent frequently or by more than one OMU of the same version within a short time period, there can be a problem with the OMU software loaded, or the firmware, of any BTS entity.
[3,0] UNKNOWNUNIT
Check software version validity
Change software version
Unit operational?
yes
Alarm solved
Figure 40: UNKNOWN-UNIT: Corrective Actions
94 / 590
4.2 [3,1] UNKNOWN-CMD-MSG

specific Problems event Type probable Cause perceived Severity Alarm Description UNKNOWN-CMD-MSG Processing Error Software Error Warning (MI) An unknown message has been received by the FU, CLLK, FHU, CU, EACB or RTC originating from the OMU, due to a software or transmission error.

[3,1] UNKNOWN CMDMSG
Check software version validity
Command alarm occurs frequently? yes Contact System Support
no
Alarm solved
Figure 41: UNKNOWN-CMD-MSG: Corrective Actions If this alarm quickly recurs for more than one OMU, or for more than one FU of the same version, there can be a problem with the software or firmware of any BTS unit.
95 / 590
4.3 [3,2] UNKNOWN-ALARM

specific Problems event Type probable Cause perceived Severity Alarm Description UNKNOWN-ALARM Processing Error Configuration Or Customization Error Warning (MI) An unknown alarm (unknown fault code) has been received by the OMU originating from a FU, CLLK, FHU, CU, EACB or RTC, due to a software error.

[3,2] UNKNOWNALARM
Check OMU CPF
Correct BTS Characteristic
Alarm persists?
no
Alarm solved
yes Contact System Support
Figure 42: UNKNOWN-ALARM: Corrective Actions If this alarm is sent frequently or by more than one OMU within a short period of time, there can be a problem with the software.
96 / 590
4.4 [3,11] SW-PROBLEM

4.4.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 A9100: 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.) -
97 / 590
4.4.1.1 BTS A9100 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 43: SW-PROBLEM (CLLK): BTS A9100 Corrective Actions
98 / 590
4.4.1.2 BTS A9110/A9110-E Corrective Actions

[3,11] SWPROBLEM (CLLK)
Reset Function BTS
Clock operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Figure 44: SW-PROBLEM (CLLK): BTS A9110/A9110-E Corrective Actions
99 / 590
4.4.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.
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.)#* -
100 / 590

Disable RF Power Use the BTS Terminal 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 45: SW-PROBLEM (TRE): BTS A9100 Corrective Actions
101 / 590

[3,11] SWPROBLEM (TRE)
Reset Function BTS
BTS operational?
yes Alarm solved
no Alarm is reported from more than one BTS? yes Contact System Support
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Figure 46: SW-PROBLEM (TRE): BTS A9110/A9110-E Corrective Actions
102 / 590
4.4.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
103 / 590

[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 47: SW-PROBLEM (RA): Corrective Actions
104 / 590
4.5 [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 -
105 / 590

[3,13] TELECOM CONFIGFAIL
Check OMU CPF
Correct BTS Characteristic
Alarm persists?
no
Alarm solved
Figure 48: TELECOM-CONFIG-FAIL: Corrective Actions
106 / 590
4.6 [3,14] WRONG-CONFIGURATION

4.6.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.
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 / 590
4.6.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 49: WRONG-CONFIGURATION (TRE): Alarm Number 1, 2, 3, 6, Corrective Actions
108 / 590
4.6.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 50: WRONG-CONFIGURATION (TRE): Alarm Number 4, Corrective Actions
109 / 590

yes
no Compare CDM value with RSL rate
Reset effected TCU
Alarm persists?
no
Alarm solved
110 / 590
4.6.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 52: WRONG-CONFIGURATION (TRE): Alarm Number 7, 9, Corrective Actions
111 / 590

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

[3,14] WRONGCONFIGURATION (BTS)
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
Figure 54: WRONG-CONFIGURATION (BTS): Alarm Number 11, Corrective Actions
113 / 590
4.6.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.
Alarm number 2, 4 and 7: The transmission quality is degraded. Alarm number 10: No disturbance of the telecom applications. Impact Loss Degradation BSS Cell(s) Signaling X(not Nb.10) Calls X(not Nb.10)
114 / 590

[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 55: WRONG-CONFIGURATION (RA): Alarm Number 2, 7, 10, Corrective Actions
115 / 590

[3,14] WRONGCONFIGURATION (RA)
Compare CDM value with RA capability
Replace masterfile
Reset effected RA
Alarm persists?
no
Alarm solved
Figure 56: WRONG-CONFIGURATION (RA): Alarm Number 4, Corrective Actions
4.6.2.3 Alarm Number 10 Corrective Actions

Readjust the maximum output power for the sector. In case of cell shared, take no action if you decided to have different power levels for the main and secondary. Readjust the maximum output power of the sectors if you want to clear the alarm.
116 / 590
4.6.3 [3,14] WRONG-CONFIGURATION (BTS, Alarm Number 12, 13, 14)

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 -
117 / 590

Correct parameter values according to BTS capability
Reset effected BTS
Alarm persists?
no
Alarm solved
Figure 57: WRONG-CONFIGURATION (BTS): Alarm Number 12, 14, Corrective Actions
118 / 590

Place OML TS on Abis 1
Reset effected BTS
Alarm persists?
no
Alarm solved
Figure 58: WRONG-CONFIGURATION (BTS): Alarm Number 13, Corrective Actions
119 / 590

4.7.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 A9100: 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.) -
120 / 590

[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 59: CONFIG-FAIL (CLLK): BTS A9100 Corrective Actions
121 / 590

[3,246] CONFIGFAIL (CLLK)
Check validity of parameters
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Figure 60: CONFIG-FAIL (CLLK): BTS A9110/A9110-E Corrective Actions
122 / 590
4.7.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.
123 / 590

[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 61: CONFIG-FAIL (RA): BTS A9100 Corrective Actions
124 / 590

Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Figure 62: CONFIG-FAIL (RA): BTS A9110/A9110-E Corrective Actions
125 / 590
4.7.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.)#* -
126 / 590

[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 63: CONFIG-FAIL (TRE): BTS A9100 Corrective Actions
127 / 590

[3,246] CONFIGFAIL (TRE)
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Figure 64: CONFIG-FAIL (TRE): BTS A9110/A9110-E Corrective Actions
128 / 590
5 Class 4: FHU Alarms

This section defines the alarms for the Class 4: FHU alarm class.
129 / 590
5.1 [4,1] DUMMY-BURST-GEN-FAIL

specific Problems event Type probable Cause perceived Severity Alarm Description DUMMY-BURST-GEN-FAIL Processing Error Software Major (PMA) The FHU cannot switch the dummy burst generation: OFF for an FU that was isolated and then successfully initialized ON for an FU that is isolated.
If there is antenna diversity, the antenna diversity function is lost and there is a loss of call quality. (#). If there is no antenna diversity (hardware does not support it or the configuration parameters indicate no antenna diversity usage), the cell is lost. (X). Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X #
130 / 590

[4,1] DUMMYBURST GENFAIL
Lock Function FHU
Unlock Function FHU
FHU operational?
yes
Alarm solved
no
Onsite
G1: Replace FQHU
Onsite OR
G2: Replace STSE/STSP/STSR
FHU operational?
yes
Alarm solved
Figure 65: DUMMY-BURST-GEN-FAIL: Corrective Actions
131 / 590
5.2 [4,5] FN-AL

specific Problems event Type probable Cause perceived Severity Alarm Description FN-AL Equipment Timing Problem Minor (DMA) The FHU detects a bad Frame Number on one of the two clock links between the Clock Unit and the FHU. 1: Fault on Clock Link 1. 2: Fault on Clock Link 2.
Alarm Number

[4,5] FNAL
Onsite
Check cables and connectors between Clock Unit and FHU
Reconnect FHU to Clock Unit
FHU operational?
yes
Alarm solved
Figure 66: FN-AL: Corrective Actions
132 / 590
5.3 [4,6] INTERNAL-FN

specific Problems event Type probable Cause perceived Severity Alarm Description INTERNAL-FN Equipment Timing Problem Major (PMA) The FHU detects a bad Frame Number on both clock links between the Clock Unit and the FHU.
If there is antenna diversity, the antenna diversity function is lost and there is a loss of call quality. (#) If there is no antenna diversity (hardware does not support it or the configuration parameters indicate no antenna diversity usage), the cell is lost. ( X) Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X #
133 / 590

[4,6] INTERNALFN
Lock Function FHU
Unlock Function FHU
FHU operational?
yes
Alarm solved
no Onsite Check cables and connectors between Clock Unit and FHU
FHU operational?
yes
Alarm solved
no
Onsite
Replace FQHU
FHU operational?
yes
Alarm solved
Figure 67: INTERNAL-FN: Corrective Actions
134 / 590
5.4 [4,10] FATAL-AL

specific Problems event Type probable Cause perceived Severity Alarm Description FATAL-AL Equipment Equipment Malfunction Major (PMA) There is an internal fatal alarm in the FHU or on the FHI link.
135 / 590

[4,10] FATALAL
Lock Function FHU
Unlock Function FHU
FHU operational?
yes
Alarm solved
no
Onsite
G1: Replace FQHU
Onsite
FHU operational?
yes
Alarm solved
Figure 68: FATAL-AL: Corrective Actions
136 / 590
5.5 [4,14] FCLK-AL

specific Problems event Type probable Cause perceived Severity Alarm Description FCLK-AL Equipment Timing Problem Minor (DMA) The FHU has detected a problem with the Frame Clock on one of the two links. 1: Fault on Clock Link 1. 2: Fault on Clock Link 2.
Alarm Number
137 / 590

[4,14] FCLKAL
Lock Function FHU
Unlock Function FHU
FHU operational?
yes
Alarm solved
FHU operational?
yes
Alarm solved
no
Onsite
Replace FQHU
FHU operational?
yes
Alarm solved
Figure 69: FCLK-AL: Corrective Actions
138 / 590
5.6 [4,15] INT-FCLK-AL

specific Problems event Type probable Cause perceived Severity Alarm Description INT-FCLK-AL Equipment Timing Problem Major (PMA) The FHU has detected a problem on the Frame Clocks of both clock links.
If there is antenna diversity, the antenna diversity function is lost and there is a loss of call quality. (#) If there is no antenna diversity (hardware does not support it or the configuration parameters indicate no antenna diversity usage), the cell is lost. (X). Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X #
139 / 590

[4,15] INTFCLKAL
Lock Function FHU
Unlock Function FHU
FHU operational?
yes
Alarm solved
FHU operational?
yes
Alarm solved
no
Onsite
Replace FQHU
FHU operational?
yes
Alarm solved
Figure 70: INT-FCLK-AL: Corrective Actions
140 / 590
5.7 [4,16] OBCLK-AL

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number OBCLK-AL Equipment Timing Problem Minor (DMA) The FHU detects a problem with the OBCLK on one of the clock links. 1: Fault on Clock Link 1. 2: Fault on Clock Link 2.
141 / 590

[4,16] OBCLKAL
Lock Function FHU
Unlock Function FHU
FHU operational?
yes
Alarm solved
FHU operational?
yes
Alarm solved
no
Onsite
Replace FQHU
FHU operational?
yes
Alarm solved
Figure 71: OBCLK-AL: Corrective Actions
142 / 590
5.8 [4,17] INTERNAL-OBCLK

specific Problems event Type probable Cause perceived Severity Alarm Description INTERNAL-OBCLK Equipment Timing Problem Major (PMA) The FHU detects a problem on the OBCLK of both clock links.

[4,17] INTERNAL OBCLK
Lock Function FHU
Unlock Function FHU
FHU operational?
yes
Alarm solved
no
Onsite
Replace FQHU
FHU operational?
yes
Alarm solved
Figure 72: INTERNAL-OBCLK: Corrective Actions
143 / 590

specific Problems event Type probable Cause perceived Severity Alarm Description MISSING-ENTRY-IN-CPF Processor Error Configuration Or Customization Error Major (PMA) An expected entry in the OMU CPF was not found. The equipment identification for the FHU is not included in the OMU CPF.
If the FHU has redundancy, telecom functions are not affected. If there is no redundancy, the cell is lost. Impact Loss Degradation BSS X(no red.) Cell(s) X(no red.) Signaling X(no red.) Calls X(no red.) -
144 / 590

Change Cell Type
FHU operational?
yes
Alarm solved
145 / 590

specific Problems event Type probable Cause perceived Severity Alarm Description CONFIG-FAIL Processing Error Configuration Or Customization Error Major (PMA) The configuration for an FHU fails.
If there is antenna diversity, the antenna diversity function is lost and there is a loss of call quality. (#) If there is no antenna diversity (hardware does not support it or the configuration parameters indicate no antenna diversity usage), the cell is lost. (X). Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X #
146 / 590

If both FHUs report the same fault then the BTS logical configuration data is incorrect.
[4,246] CONFIGFAIL
Lock Function FHU
Unlock Function FHU
FHU operational?
yes
Alarm solved
no
Correct Cell Logical Parameters
Check validity of parameters: ARFCN, HSN, FHS
Restart OMU
yes FHU operational? Alarm solved
no
Onsite
Check parameters at BTS Terminal
Onsite
Correct parameters at BTS Terminal
FHU operational?
yes
Alarm solved
147 / 590
5.11 [4,247] RESET

specific Problems event Type probable Cause perceived Severity Alarm Description RESET Processing Error Software Error Warning (MI) The FHU performs an auto-reset, e.g. following the expiry of a watchdog timer during operational mode, or due to a push-button reset.
If there is antenna diversity, the antenna diversity function is lost for a short time and there is a loss of call quality. If there is no antenna diversity, there is a loss of calls. The cell and BCCH signaling is lost for around one minute. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -

[4,247] RESET
Lock Function FHU
Unlock Function FHU
FHU operational?
yes
Alarm solved
no
Onsite
G1: Replace FQHU
Onsite
FHU operational?
yes
Alarm solved
Figure 75: RESET: Corrective Actions
148 / 590

specific Problems event Type probable Cause perceived Severity Alarm Description NO-ANSWER-DCL Processing Error Underlying Resource Unavailable Major (PMA), Minor (DMA) Major (PMA): There is no answer on the Q1 bus from an FHU, for more than two polling cycles, to polling by the OMU. Minor (DMA): There is no answer on the Q1 bus from an FHU to commands from the OMU during initialization or reconfiguration.
Major (PMA): The fault is detected during initialization or reconfiguration in all cases (Q1 malfunction). If the BTS is equipped and configured for antenna diversity, the antenna diversity function is lost and there is a loss of call quality. (#) If there is no antenna diversity (hardware does not support it or the configuration parameters indicate no antenna diversity usage), the cell is lost. (X). Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X #
Minor (DMA): In case of Q1 malfunction there is no disturbance of the telecom applications. In case of FHU malfunction, the result depends on the FHU fault, the FHU can eventually go on with the previous configuration. If the fault is fatal, others alarms will appear on other equipment (ex FU on Token bus). Impact Loss Degradation BSS Cell(s) Signaling Calls -
149 / 590

[4,250] NOANSWERDCL
Lock Function FHU
Unlock Function FHU
FHU operational?
yes
Alarm solved
no Onsite Check Q1 cables and connectors between OMU and FHU
FHU operational?
yes
Alarm solved
no
Onsite
G1: Replace FQHU
Onsite
FHU operational?
yes
Alarm solved
150 / 590
5.13 [4,255] Q1-RELAY-FAILURE

specific Problems event Type probable Cause perceived Severity Alarm Description Q1-RELAY-FAILURE Equipment Equipment Malfunction Minor (DMA) There is a failure on the Q1 relay. The FHU cannot disconnect itself from the Q1 bus.
151 / 590

[4,255] Q1RELAYFAILURE
Lock Function FHU
Unlock Function FHU
FHU operational?
yes
Alarm solved
no
Onsite
G1: Replace FQHU
Onsite
FHU operational?
yes
Alarm solved
Figure 77: Q1-RELAY-FAILURE: Corrective Actions
152 / 590
6 Class 5: ENVIR Alarms

This section defines the alarms for the Class 5: ENVIR alarm class.
153 / 590
6.1 [5,0] POWER-SUPPLY

6.1.1 [5,0] POWER-SUPPLY (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description POWER-SUPPLY Equipment PowerProblem Major (PMA), Minor (DMA) Major (PMA): A CUPS Power Supply fails. Minor (DMA): There is an AC/DC Power Supply problem.
The CU 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 CU supporting the BCCH is not concerned, the cell is degraded, calls are lost. (#) If the CU supporting the BCCH is concerned and there is BCCH redundancy, recovery mechanisms regain the cells functionality. (*) If the CU 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.)#* -
154 / 590

[5,0] POWERSUPPLY (CU)
TRX POWERAL events?
yes
Solve this Alarm first
no
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
yes Alarm solved CU operational? Check cables/connectors to mains, batteries, power supplies and EACB
Onsite
Check power supply is switched on
no
Onsite
G1: Replace CPSU
Onsite OR
G2: Replace FCPS
CU operational?
yes
Alarm solved
Figure 78: POWER-SUPPLY (CU): Corrective Actions
155 / 590
6.1.2 [5,0] POWER-SUPPLY (FU)

specific Problems event Type probable Cause perceived Severity Alarm Description POWER-SUPPLY Equipment PowerProblem Major (PMA), Minor (DMA) Major (PMA): A FUPS fails. Minor (DMA): There is an AC/DC Power Supply problem.
The FU 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 FU supporting the BCCH is not concerned, the cell is degraded, calls are lost. (#) If the FU supporting the BCCH is concerned and there is BCCH redundancy, recovery mechanisms regain the cells functionality. (*) If the FU 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.)#* -
156 / 590

[5,0] POWERSUPPLY (FU)
TRX POWERAL events?
yes
Solve this Alarm first
no
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Onsite
yes Alarm solved FU operational? Check cables/connectors to mains, batteries, power supplies, EACB, OMU and FU
Onsite
Check power supply is switched on
no
Onsite
G1: Replace FUPS, TCPS
Onsite OR
G2: Replace FCPS
FU operational?
yes
Alarm solved
Figure 79: POWER-SUPPLY (FU): Corrective Actions
157 / 590
6.1.3 [5,0] POWER-SUPPLY (RA)

specific Problems event Type probable Cause perceived Severity Alarm Description POWER-SUPPLY Equipment PowerProblem Major (PMA), Minor (DMA) Major (PMA): An RTC power supply problem has occurred during configuration. Minor (DMA): An RTC power supply problem was autonomously detected by the OMU.
Major (PMA): The cell is lost. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
158 / 590

[5,0] POWERSUPPLY (RA)
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Onsite
G1: Replace CUPS
Onsite OR
G2: Replace FCPS
RA operational?
yes
Alarm solved
Figure 80: POWER-SUPPLY (RA): Corrective Actions
159 / 590
6.2 [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 A9110-E BTS (Master). 10 : FAN alarm for A9110-E BTS (Slave 1). 20 : FAN alarm for A9110-E BTS (Slave 2). 11 : FAN alarm for A9110-E BTS (Slave 11). 12 : FAN alarm for A9110-E BTS (Slave 12). 21 : FAN alarm for A9110-E BTS (Slave 21). 22 : FAN alarm for A9110-E BTS (Slave 22).

[5,1] FANALARM
Onsite
G1: Replace CFSR; CFSU; TBCF; TCFB; TCFU G2: OR Replace CFU1, CFUA, CFUT
Onsite
A9100: OR Replace FANU; FACB
Onsite
A9110E: Replace Fan Cassete
OR
Fan operational?
yes
Alarm solved
Figure 81: FAN-ALARM: Corrective Actions
160 / 590
6.3 [5,2] FAN-ALARM-U

specific Problems event Type probable Cause perceived Severity Alarm Description FAN-ALARM-U Environmental HeatingOrVentilationOrCoolingSystemProblem Major (PMA) At least two fans are lost - urgent fan alarm.
Temperature problems are expected to occur. This can lead to a general degradation of the transmitted signal quality. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X

[5,1] FANALARM
Onsite
Onsite
Onsite
OR
Fan operational?
yes
Alarm solved
Figure 82: FAN-ALARM-U: Corrective Actions
161 / 590
6.4 [5,3] FAN-ALARM-T

specific Problems event Type probable Cause perceived Severity Alarm Description FAN-ALARM-T Environmental HeatingOrVentilationOrCoolingSystemProblem Minor (DMA) The fan temperature exceeds a given threshold. This is a warning but the situation is not yet critical. FAN-ALARM-U [5,2] is issued when the situation is critical.

[5,1] FANALARM
Onsite
Onsite
Onsite
OR
Fan operational?
yes
Alarm solved
Figure 83: FAN-ALARM-T: Corrective Actions
162 / 590
6.5 [5,4] BTS-TEMP-ALARM

specific Problems event Type probable Cause perceived Severity Alarm Description BTS-TEMP-ALARM Environmental Temperature Unacceptable Minor (DMA) There is a temperature alarm for the complete BTS.
Temperature problems are expected to occur. This can lead to a general degradation of the transmitted signal quality. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X
163 / 590

[5,4] BTSTEMPALARM
Reduce traffic on BTS by blocking resources or barring cells
no Alarm persists?
Alarm solved
yes Onsite Reduce RF power by disable of some CUs
no Alarm persists?
Alarm solved
Figure 84: BTS-TEMP-ALARM: Corrective Actions
164 / 590
6.6 [5,5] CPLG-ALARM

specific Problems event Type probable Cause perceived Severity Alarm Description CPLG-ALARM Environmental Transmitter Failure Minor (DMA), Warning (MI) The alarm is provoked by RTC problems. If a cavity is not tuned correctly, the BTS sends an alarm with the severity Warning (MI) and tries to retune the cavity. If the retune is successful, the alarm disappears, no corrective action is required. The CU power supply is switched off because of the local retuning of the cavity. If the retuning is not successful, the severity of the alarm changes to Minor (DMA). The CU power supply is switched off because of the coupling problem.
Minor (DMA): The CU is no longer usable. The associated eight channels are lost. The BSC reduces the number of channels supported by the cell. If the CU supported the BCCH, redundancy mechanisms regain the cells functionality, calls are lost. If there is no BCCH redundancy, the complete cell is lost. Impact Loss Degradation BSS X(no red.) Cell(s) X(no red.) Signaling X(no red.) Calls X(no red.) -
165 / 590

Warning (MI): No corrective action required. Minor (DMA): Disable RF Power Use the BTS Terminal to disable RA before disconnecting RF cables. Initialize RA after work.
[5,5] CPLGALARM
Onsite
G1: Replace CBC2; CBC4; CEC2; CEC4; FBC2; FCAV; FEC2
Onsite OR
G2: Replace CRBG; CREG; FRBG; FREG; RC4D; RC8D
Onsite OR
G2: DUPD; DUPG; WB2G; WB2D
CU operational?
yes
Alarm solved
Figure 85: CPLG-ALARM: Corrective Actions
166 / 590
6.7 [5,6] SU-POWER-AL

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number SU-POWER-AL Equipment PowerProblem Major (PMA) The SUPS indicated is unavailable as detected by the EACB. 1: SU 1 2: SU 2
If there are two SUPSs, there is no impact on the telecom capabilities. In the case of a single SUPS, the OMU, FHU and CLLK are no longer available and the cell is lost. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
167 / 590

[5,6] SUPOWERAL
Onsite
Check Power Supplies are switched on
Onsite
Check cables/connectors to EACB and SUPS
SU operational?
yes
Alarm solved
no
Onsite
G1: Replace SUPS
Onsite OR
G2: Replace ADPS in MCO2/MCO4
Onsite OR
G2: Replace ADPS in MCI2
Onsite OR
G2: Replace MBPS
SU operational?
yes
Alarm solved
Figure 86: SU-POWER-AL: Corrective Actions
168 / 590
6.8 [5,7] TRX-POWER-AL

specific Problems event Type probable Cause perceived Severity Alarm Description TRX-POWER-AL Equipment PowerProblem Major (PMA) A power supply (AC/DC) failure is resulting in the loss of power for FU and CU. The affected chain is indicated by the Alarm Number. 1: CU 1 and FU 1. 2: CU 2 and FU 2. n: CU n and FU n.
Alarm Number
The affected equipment (CU, FU) 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 FU or CU supporting the BCCH is not concerned, the cell is degraded, calls are lost. (#). If the FU or CU supporting the BCCH is concerned and there is BCCH redundancy, recovery mechanisms regain the cells functionality, calls are lost. (*) If the FU or CU 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.)#* -
169 / 590

[5,7] TRXPOWERAL
Onsite
Onsite
Check cables/connectors to AC/DC and EACB
CU/FU operational?
yes
Alarm solved
no
Onsite
G1: Replace SUPS
Onsite OR
Onsite OR
Onsite OR
G2: Replace MBPS
CU/FU operational?
yes
Alarm solved
Figure 87: TRX-POWER-AL: Corrective Actions
170 / 590
6.9 [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 A9100: 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 -
171 / 590

[5,11] POWERSUPPLYU
Onsite
Onsite
Check cables/connectors to control unit, power module and EACB
no Alarm persists?
Alarm solved
yes
Onsite
Onsite
Onsite
A9100: Replace OR PM08, which LED is off or red *
Onsite
A9100: Replace PM11, which LED is off or red *
Onsite
Onsite
OR
OR
OR
OR
Power supply operational?
yes
Alarm solved
* If RIT location is A,0,0, the RIT is located in A9100 COMI/CODI outdoor side compartment
Figure 88: POWER-SUPPLY-U: Corrective Actions
172 / 590
6.10 [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 A9100: At least one PM08/PM11/PM12/PM18 module is operational and no TRE is switched OFF.
173 / 590

[5,12] POWERSUPPLYNU
Onsite
Onsite
no Alarm persists?
Alarm solved
yes
Onsite
Onsite
Onsite
Onsite
Onsite
Onsite
OR
OR
OR
OR
yes
Alarm solved
Figure 89: POWER-SUPPLY-NU: Corrective Actions
174 / 590
6.11 [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 -
175 / 590

[5,13] CONTROLUNITAL
Onsite
Onsite
Battery OK? no G2: Replace BBU2/BU60
Onsite
A9100 OR BCU1/BCU2, PM12: Replace BU41/BU100
Onsite OR
A9100: Replace BATS
Onsite OR
A9100: Replace BU101
yes
Control Unit operational?
yes
Alarm solved
Onsite
Check cables/connectors to control unit and EACB no Contact System Support
Onsite
G2: Replace BHPS
Onsite
G2: Replace PM06
Onsite
A9100: Replace OR BCU1, which LED is off or red *
Onsite
A9100: Replace OR BCU2, which LED is off or red *
Onsite OR
OR
yes
Alarm solved
Figure 90: CONTROL-UNIT-AL: Corrective Actions
176 / 590
6.12 [5,14] MAINS-POWER-SUPPLY

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number MAINS-POWER-SUPPLY Equipment PowerProblem Critical (VPMA) There is a mains power supply failure. 1: There is a mains power supply failure on a standard G2 BTS.
There is no disturbance of the telecom applications as long as the battery is still working. If the battery is empty, the cells are lost. (X). Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
177 / 590
6.12.1 G2 BTS Corrective Actions

[5,14] MAINSPOWERSUPPLY
Onsite
Onsite
G1: Replace SUPS
Onsite
G2 in MCO2/MCO4: Replace ADPS
Onsite
G2 in MCI2: Replace ADPS
Onsite OR
G2: Replace MBPS
OR
OR
yes
Alarm solved
Figure 91: MAINS-POWER-SUPPLY: G2 BTS Corrective Actions
178 / 590
6.13 [5,15] BATT-DEEP-DISCHARGE

specific Problems event Type probable Cause perceived Severity Alarm Description BATT-DEEP-DISCHARGE Equipment PowerProblem Major (PMA) The battery is deep discharged.
There is no disturbance of the telecom applications as long as the battery is still working. If there is no mains power supply and the battery is empty, the cells are lost. (X). Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
179 / 590

[5,15] BATTDEEPDISCHARGE
Onsite
Check the battery BBU2
Onsite
Check the Battery BU60
OR
Onsite
Battery OK? yes G2: Replace SACE/SCFE
no
Onsite
G2: Replace BBU2
Onsite OR
G2: Replace BU60
Battery OK?
yes
Alarm solved
Battery OK?
yes
Alarm solved
Figure 92: BATT-DEEP-DISCHARGE: Corrective Actions
180 / 590
6.14 [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 -
181 / 590

[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 93: MAINS-AL: Corrective Actions
182 / 590
6.15 [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 A9100- A TRE is switched off due to a mains alarm (see the description of the "MAINS_AL" or "POWER SUPPLY_U" alarm). 2: BTS A9110/A9110-E - This alarm is reported for a TRE in slave box when this slave box is started after the master box during Evolium A9110-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.)#* -
183 / 590

[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
yes
Alarm solved
Figure 94: POWER-SHUTDOWN: Alarm Number 1 Corrective Actions
184 / 590

[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 95: POWER-SHUTDOWN: Alarm Number 2 Corrective Actions
185 / 590
6.16 [5,24] SUBRACK-POWER

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number SUBRACK-POWER Equipment PowerProblem Major (PMA) The subrack is not powered. The number reported is the subrack number. 1: Subrack number 1. ... n: Subrack number n.
There is impact through the HW_FAILURE of class 10 alarms. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
186 / 590

[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 96: SUBRACK-POWER: Corrective Actions
187 / 590
6.17 [5,31] TEMPERATURE-WARNING

6.17.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.
188 / 590

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 97: TEMPERATURE-WARNING (BTS): Corrective Actions
189 / 590
6.17.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.
190 / 590

[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 98: TEMPERATURE-WARNING (TRE): Corrective Actions
191 / 590
6.18 [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.)#* -
192 / 590

[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 99: FATAL TEMPERATURE: Corrective Actions
193 / 590
6.19 [5,237] HW-DEGRADED

6.19.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.
194 / 590

[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 100: HW-DEGRADED (BTS): Corrective Actions
195 / 590
6.19.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 A9100: A problem has been detected on the XIOB/OUTC input ports. BTS A9110/A9110-E : A problem has been detected on the input ports during tests with the MBTS-BCB unit. 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
196 / 590
6.19.2.1 Alarm Number 10 BTS A9100 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 101: HW-DEGRADED (EACB): BTS A9100 Corrective Actions
197 / 590
6.19.2.2 Alarm Number 10 BTS A9110/A9110-E Corrective Actions

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 102: HW-DEGRADED (EACB): BTS A9110/A9110-E Corrective Actions
198 / 590
6.19.2.3 Alarm Number 11..17 Corrective Actions

Lock Function EACB
EACB operational?
yes
Alarm solved
no
Onsite
Replace TMA
EACB operational?
yes
Alarm solved
Figure 103: HW-DEGRADED (EACB): Corrective Actions
199 / 590
6.19.3 [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 104: HW-DEGRADED (CCF): Corrective Actions
200 / 590
6.20 [5,239] HW-FAILURE

6.20.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 the extraction of the module. 4: There is no associated module to this SBL.
201 / 590

[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 105: HW-FAILURE (EACB): Alarm Number 2 Corrective Actions
202 / 590

[5,239] HWFAILURE (EACB)
Onsite
Insert appropriate module
EACB operational?
yes
Alarm solved
Figure 106: HW-FAILURE (EACB): Alarm Number 3 Corrective Actions
203 / 590
6.20.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.
204 / 590

[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 107: HW-FAILURE (CCF): Corrective Actions
205 / 590
206 / 590
7 Class 6: RF alarms
This section defines the alarms for the Class 6: RF alarm class.
207 / 590
7.1 [6,1] LNK-AL

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number LNK-AL Equipment Loss Of Signal Minor (DMA) A link between the FHU and a CU is faulty on the CU side. 1: Fault on Link 1. 2: Fault on Link 2.
If there is antenna diversity, the antenna diversity function is lost and there is a loss of call quality. (#) If there is no antenna diversity, the 8 channels supported by the CU are lost. The BCCH is regained through recovery. (X). Impact Loss Degradation BSS Cell(s) #X Signaling #X Calls X #
208 / 590

[6,1] LNKAL
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
Check FHI cables and connectors to CU and FHU
Onsite
Onsite
Replace Receiver
OR
Replace Transmitter
CU operational?
yes
Alarm solved
Figure 108: LNK-AL: G1 BTS Corrective Actions
209 / 590

[6,1] LNKAL
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
Onsite
Replace Receiver
OR
Replace Transmitter
CU operational?
yes
Alarm solved
Figure 109: LNK-AL: G2 BTS Corrective Actions
210 / 590
7.2 [6,2] LNK-DBLE-AL

specific Problems event Type probable Cause perceived Severity Alarm Description LNK-DBLE-AL Equipment Loss Of Signal Major (PMA) Both links between the FHU and a CU are faulty.
The eight channels supported by the CU are lost. The BCCH is regained through recovery. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
211 / 590

[6,2] LNKDBLEAL
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
Onsite
Replace Receiver
OR
Replace Transmitter
CU operational?
yes
Alarm solved
Figure 110: LNK-DBLE-AL: G1 BTS Corrective Actions
212 / 590

[6,2] LNKDBLEAL
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
Onsite
Replace Receiver
OR
Replace Transmitter
CU operational?
yes
Alarm solved
Figure 111: LNK-DBLE-AL: G2 BTS Corrective Actions
213 / 590
7.3 [6,5] RX-AL

specific Problems event Type probable Cause perceived Severity Alarm Description RX-AL Equipment Receiver Failure Major (PMA), Minor (DMA) A failure has been detected on the receiver of a CU. Major (PMA): The CU is no longer functioning. Minor (DMA): The antenna diversity is lost, but the CU is still functioning. Alarm Number 1: Fault detected on the first receiver. 2: Fault detected on the second receiver.
If the BTS is equipped and configured for antenna diversity, then the antenna diversity function is lost. There is also a loss of call quality. (#). If there is no antenna diversity (hardware does not support it, or the configuration parameters indicate no antenna diversity usage) then the eight channels supported by the CU are lost. The BCCH is regained through recovery. (X). Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X #
214 / 590

[6,5] RXAL
Check software and hardware configuration for atenna diversity.
Diversity configuration OK? no
yes
Onsite
Modify actual Antenna diversity Choose correct CPF capability by OR by selecting replacing the appropriate BTS appropriate antenna characteristics. entity
Lock Function CU
Unlock Function CU
yes Alarm solved CU operational? CU operational?
yes Alarm solved
no
Onsite
Replace G1 Receiver
Onsite
Replace G2 Receiver
OR
CU operational?
yes
Alarm solved
Figure 112: RX-AL: Corrective Actions The fault can be due to external interference.
215 / 590
7.4 [6,6] RX-DBLE-AL

specific Problems event Type probable Cause perceived Severity Alarm Description RX-DBLE-AL Equipment Receiver Failure Major (PMA) A fatal failure is detected on both receivers of the same CU (only in the case of antenna diversity).
216 / 590

[6,6] RXDBLEAL
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite Onsite
Replace both G2 Receivers
Onsite
OR
CU operational?
yes
Alarm solved
Figure 113: RX-DBLE-AL: Corrective Actions
217 / 590
7.5 [6,7] RX-SYN-AL

specific Problems event Type probable Cause perceived Severity Alarm Description RX-SYN-AL Equipment Receiver Failure Major (PMA), Minor (DAM) A failure is detected on the synthesizer in a receiver of a CU. Major (PMA): The CU is no longer functioning. Minor (DMA): The antenna diversity is lost, but the CU is still functioning. Alarm Number 1: Fault detected on the first receiver. 2: Fault detected on the second receiver.
If the BTS is equipped and configured for antenna diversity, then the antenna diversity function is lost. There is also a loss of call quality. (#). If there is no antenna diversity (hardware does not support it, or the configuration parameters indicate no antenna diversity usage) then the eight channels supported by the CU are lost. The BCCH is regained through recovery. (X). Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X #
218 / 590

[6,7] RXSYNAL
Check software and hardware configuration for atenna diversity.
Diversity configuration OK? no
yes
Onsite
Modify actual Antenna diversity Choose correct CPF OR capability by by selecting replacing the appropriate BTS appropriate antenna characteristics. entity
Lock Function CU
Unlock Function CU
yes Alarm solved CU operational? CU operational?
yes Alarm solved
no
Onsite
Replace G1 Receiver
Onsite
Replace G2 Receiver
OR
CU operational?
yes
Alarm solved
Figure 114: RX-SYN-AL: Corrective Actions
219 / 590
7.6 [6,8] RX-SYN-DBLE-AL

specific Problems event Type probable Cause perceived Severity Alarm Description RX-SYN-DBLE-AL Equipment Receiver Failure Major (PMA) A fatal failure has been detected on both synthesizers in the receivers of the same CU (only in case of antenna diversity).
220 / 590

[6,8] RXSYNDBLEAL
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite Onsite
Onsite
OR
CU operational?
yes
Alarm solved
Figure 115: RX-SYN-DBLE-AL: Corrective Actions
221 / 590
7.7 [6,9] VSWR-AL

specific Problems event Type probable Cause perceived Severity Alarm Description VSWR-AL Equipment Transmitter Failure Major (PMA) Alarm has been raised because VSWR > 3 dB.
The eight channels supported by the offending carrier are lost. The BCCH is regained through recovery. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
222 / 590

[6,9] VSWRAL
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
yes Alarm solved CU operational? Check cables/connectors to transmitter antenna visually for damage and for electric function. If required, reconnect/replace cable
no
Check combiner is tuned correctly
Check for combiner alarms. Solve that alarm(s).
CU operational?
yes
Alarm solved
no
Onsite
Replace Combiner
Onsite
Replace Transmitter
OR
CU operational?
yes
Alarm solved
Figure 116: VSWR-AL: G1 BTS Corrective Actions
223 / 590

[6,9] VSWRAL
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no yes Alarm solved CU operational?
Onsite
Check cables/connectors to transmitter antenna visually for damage and for electric function. If required, reconnect/replace cable
no
CU operational?
yes
Alarm solved
no
Onsite
Replace RTC
Onsite
Replace WBC
Onsite
Replace Transmitter
OR
OR
CU operational?
yes
Alarm solved
Figure 117: VSWR-AL: G2 BTS Corrective Actions
224 / 590
7.8 [6,10] TX-POWER-AL

specific Problems event Type probable Cause perceived Severity Alarm Description TX-POWER-AL Equipment Transmitter Failure Major (PMA) The transmitter output power is > 3dB below specification.
The affected equipment (TX) is no longer usable. The associated eight channels are lost. If the TX supporting the BCCH is not concerned, the cell is degraded, calls are lost. (#). If the TX supporting the BCCH is concerned and there is BCCH redundancy, recovery mechanisms regain the BCCH. (*). If the TX 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.)# * -
225 / 590

Required tools and materials: Combiner test tool (e.g. spectrum analyzer) Replacement tools, see appropriate replacement procedure.
[6,10] TXPOWERAL
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
Onsite
yes Alarm solved CU operational? Check cables/connectors to CU and combiner downlink. If required, reconnect/replace cable
no
no
Onsite
Replace G1 Transmitter
Onsite
Replace G2 Transmitter
OR
CU operational?
yes
Alarm solved
no
Onsite
Replace G1 Combiner
Onsite
Onsite
OR
Replace G2 RTC
OR
Replace G2 WBC
CU operational?
yes
Alarm solved
Figure 118: TX-POWER-AL: Corrective Actions
226 / 590
7.9 [6,11] TEMP-AL

specific Problems event Type probable Cause perceived Severity Alarm Description TEMP-AL Environmental Temperature Unacceptable Major (PMA), Minor (DMA) Major (PMA): The temperature of the transmitter is higher than 80 C. The corresponding CU power supply is switched off. Minor (DMA): The temperature of the transmitter is higher than 75 o C o but less than 80 C. Alarm Number 1: The Temperature has reached 75 o C. 2: The Temperature has reached 80 o C.
o
Major (PMA): If the transmitter supporting the BCCH is not concerned, the transmitter cannot be used and the eight channels are lost. (#). If the transmitter supporting the BCCH is concerned and there is BCCH redundancy: the transmitter cannot be used and the eight channels are lost recovery mechanisms regain the BCCH. (*). If the TX 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.)#* -
Minor (DMA): The quality of the transmission may be degraded.
227 / 590

[6,11] TEMPAL
Fan alarm events?
yes
Onsite
Is ambient temperature out of permitted limits? yes The ambient temperature must be reduced. Transmitter Temperature OK? yes Alarm solved
no Onsite Check and clean heat exchanger air intake
Onsite
Replace Cooling Fan TRE Temperature OK? no Transmitter Temperature OK?
OR Onsite
Replace Transmitter
yes
Alarm solved
yes Alarm solved
Figure 119: TEMP-AL: G1 BTS Corrective Actions
228 / 590

[6,11] TEMPAL
Fan alarm events?
yes
Onsite
Is ambient temperature out of permitted limits? yes The ambient temperature must be reduced. Transmitter Temperature OK? yes Alarm solved
no Onsite Check and clean heat exchanger air intake
Onsite
Replace CFU TRE Temperature OK? no Transmitter Temperature OK?
OR Onsite
Replace Transmitter
yes
Alarm solved
yes Alarm solved
Figure 120: TEMP-AL: G2 BTS Corrective Actions
229 / 590
7.10 [6,13] TX-SYN-AL

specific Problems event Type probable Cause perceived Severity Alarm Description TX-SYN-AL Environmental Transmitter Failure Major (PMA) A failure has been detected on the transmitter synthesizer of a CU The transmitter synthesizer is not locked.
Transmission quality is degraded. Depending on the level of degradation, the eight channels supported by the transmitter may be lost. The BCCH is regained through recovery. Impact Impact Loss Degradation BSS BSS X Cell(s) Cell(s) X Signaling Signaling X Calls Calls X -
230 / 590

[6,13] TXSYNAL
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
G1: Replace Transmitter
Onsite
OR
CU operational?
yes
Alarm solved
Figure 121: TX-SYN-AL: Corrective Actions
231 / 590
7.11 [6,14] FCLK-AL

7.11.1 [6,14] FCLK-AL (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description FCLK-AL Equipment Timing Problem Minor (DMA) A failure is detected on one of the clock links of a CU. The CU has automatically switched to the other clock link. 1: Fault on Clock Link 1. 2: Fault on Clock Link 2.
Alarm Number
232 / 590
7.11.1.1 G1 BTS Corrective Actions

[6,14] FCLKAL (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
Replace MCLU, MCLR
Onsite
Onsite OR
OR
Replace MFG
Replace Transmitter
CU operational?
yes
Alarm solved
Figure 122: FCLK-AL (CU): G1 BTS Corrective Actions
233 / 590

[6,14] FCLKAL (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
Replace STSE, STSP, STSR
Onsite
OR
Replace Transmitter
CU operational?
yes
Alarm solved
Figure 123: FCLK-AL (CU): G2 BTS Corrective Actions
234 / 590
7.12 [6,15] INTERNAL-FCLK

7.12.1 [6,15] INTERNAL-FCLK (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description INTERNAL-FCLK Equipment Timing Problem Major (PMA) Both internal frame clock links of a CU are faulty.
235 / 590

[6,15] INTERNALFCLK (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
Check cables/connectors to clock link and CU
CU operational?
yes
Alarm solved
no
Onsite
Replace MCLU, MCLR
Onsite
Onsite
OR
Replace MFG
OR
Replace Transmitter
CU operational?
yes
Alarm solved
Figure 124: INTERNAL-FCLK (CU): G1 BTS Corrective Actions
236 / 590

[6,15] INTERNALFCLK (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
CU operational?
yes
Alarm solved
no
Onsite
Onsite
OR
Replace Transmitter
CU operational?
yes
Alarm solved
Figure 125: INTERNAL-FCLK (CU): G2 BTS Corrective Actions
237 / 590
7.13 [6,16] OBCLK-AL

7.13.1 [6,16] OBCLK-AL (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description OBCLK-AL Equipment Timing Problem Minor (DMA) A failure is detected on one of the Octal Bit Clock Links of a CU. The CU is automatically switched to the other clock link. 1: Fault on Clock Link 1. 2: Fault on Clock Link 2.
Alarm Number
238 / 590

[6,16] OBCLKAL (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
CU operational?
yes
Alarm solved
no
Onsite
Onsite
OR
CU operational?
yes
Alarm solved
Figure 126: OBCLK-AL (CU): Corrective Actions
239 / 590
7.14 [6,17] INTERNAL-OBCLK

7.14.1 [6,17] INTERNAL-OBCLK (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description INTERNAL-OBCLK Equipment Timing Problem Major (PMA) Both Octal Bit Clock Links of a CU are faulty.
240 / 590

[6,17] INTERNALOBCLK (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
CU operational?
yes
Alarm solved
no
Onsite
Onsite
OR
CU operational?
yes
Alarm solved
Figure 127: INTERNAL-OBCLK (CU): Corrective Actions
241 / 590
7.15 [6,18] REF-FREQ-AL

7.15.1 [6,18] REF-FREQ-AL (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description REF-FREQ-AL Equipment Timing Problem Minor (DMA) A failure is detected on one of the clock links carrying the reference frequency of a CU. The CU is automatically switched to the other clock link. Alarm Number 1: Fault on Clock Link 1. 2: Fault on Clock Link 2.
242 / 590

[6,18] REFFREQAL (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
CU operational?
yes
Alarm solved
no
Onsite
Onsite
G1: Replace MFG
Onsite OR
G2: Replace STSE,STSP,STSR
OR
CU operational?
yes
Alarm solved
Figure 128: REF-FREQ-AL (CU): Corrective Actions
243 / 590
7.16 [6,19] INTERNAL-REF-FRQ

7.16.1 [6,19] INTERNAL-REF-FRQ (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description INTERNAL-REF-FRQ Equipment Timing Problem Major (PMA) A failure is detected on both clock links carrying the reference frequency for a CU.
244 / 590

[6,19] INTERNALREFFRQ (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
CU operational?
yes
Alarm solved
no
Onsite
Replace MCLU, MCLR
Onsite
Onsite
OR
Replace MFG
OR
Replace Transmitter
CU operational?
yes
Alarm solved
Figure 129: INTERNAL-REF-FRQ (CU): G1 BTS Corrective Actions
245 / 590

[6,19] INTERNALREFFRQ (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
CU operational?
yes
Alarm solved
no
Onsite
Onsite
OR
Replace Transmitter
CU operational?
yes
Alarm solved
Figure 130: INTERNAL-REF-FRQ (CU): G2 BTS Corrective Actions
246 / 590
7.17 [6,34] ANTENNA-VSWR

specific Problems event Type probable Cause perceived Severity Alarm Description ANTENNA-VSWR Equipment Transmitter Failure Major (PMA), Minor (DMA) A fault is detected in the antenna VSWR. Major (PMA): The VSWR has exceeded threshold level 2. Minor (DMA): The VSWR has exceeded threshold level 1. Alarm Number 1: The VSWR has exceeded threshold level 1. 2: The VSWR has exceeded threshold level 2.
Major (PMA): The complete cell is lost. (X) Minor (DMA): The transmission quality is degraded. (#). Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X #

Required tools and materials Antenna Test Tools
247 / 590
[6,34] ANTENNAVSWR
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
temporarily
Check cable/connectors to transmitter antenna for damage and electric function. Check VSWR threshold switch setting to 1.7 on combiner front panel Check BTS status Reduce transmit power, so cell might come back in traffic. Solve problem as soon as possible
RA operational?
yes
Alarm solved
no
Antenna network problems events?
yes
Solve antenna network problem
no
Antenna problems events?
yes
Solve antenna problem
no
RA operational?
yes
Alarm solved
Figure 131: ANTENNA-VSWR: Corrective Actions Reduced TX Power If the transmit power was reduced, set transmit power settings back to previous values when the problem is solved.
248 / 590
7.18 [6,35] FRONTEND-RELAY-AL

specific Problems event Type probable Cause perceived Severity Alarm Description FRONTEND-RELAY-AL Equipment Equipment Malfunction Minor (DMA) A fault is detected on the RFE relay (For the G1 BTS this alarm is only issued if there is no antenna diversity).
249 / 590

[6,35] FRONTEND RELAYAL
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Onsite
Check cables/connectors from receiver antenna visually and eletrically. Replace cable if required.
Onsite
G1: Replace RFE
Onsite
G2: Replace RFE
OR
RA operational?
yes
Alarm solved
Figure 132: FRONTEND-RELAY-AL: Corrective Actions
250 / 590
7.19 [6,36] FRONTEND-AL

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number FRONTEND-AL Equipment Equipment Malfunction Major (PMA), Minor (DMA) One of the two amplifiers of a RFE is faulty. 1: VSWR has exceeded threshold level 1. 2: VSWR has exceeded threshold level 2.
If the BTS is equipped and configured for antenna diversity, the antenna diversity function is lost. There is a loss of call quality. (#) If there is no antenna diversity, the cell is lost. (X). Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X #
251 / 590

[6,36] FRONTENDAL
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Onsite
Onsite
G1: Replace RFE
Onsite
G2: Replace RFE
OR
RA operational?
yes
Alarm solved
Figure 133: FRONTEND-AL: Corrective Actions
252 / 590
7.20 [6,37] FATAL-FRONTEND-AL

specific Problems event Type probable Cause perceived Severity Alarm Description FATAL-FRONTEND-AL Equipment Equipment Malfunction Major (PMA) The RFE is faulty.
The cell is lost. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
253 / 590

[6,37] FATAL FRONTENDAL
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Onsite
Onsite
G1: Replace RFE
Onsite
G2: Replace RFE
OR
RA operational?
yes
Alarm solved
Figure 134: FATAL-FRONTEND-AL: Corrective Actions
254 / 590
7.21 [6,38] BCCH-SWITCH

specific Problems event Type probable Cause perceived Severity Alarm Description BCCH-SWITCH Processing Error Configuration Or Customization Error Minor (DMA) The BCCH switch status is wrong. The actual BCCH relay position is not the same as the required BCCH switch position in the CDM.
If failure of supervision functions causes the alarm, this has no impact on the telecom functions. If the alarm is due to failure of the switch then the BCCH (and therefore the cell) is lost. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
255 / 590

[6,38] BCCHSWITCH
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Onsite
Check cables/connectors between switch and EACB visually and electrically. Replace cable if required.
Onsite
G1: Replace EACB, EAIB
Onsite
G2: Replace SACE, SCFE
OR
RA operational?
yes
Alarm solved
Figure 135: BCCH-SWITCH: Corrective Actions
256 / 590
7.22 [6,39] BCCH-SWITCH-FATAL

specific Problems event Type probable Cause perceived Severity Alarm Description BCCH-SWITCH-FATAL Equipment Equipment Malfunction Major (PMA) The BCCH switch is faulty (configuration failed for BCCH switch and the switch could not be switched).
The BCCH and therefore the cell is lost. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
257 / 590

[6,38] BCCHSWITCHFATAL
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
RA operational?
yes
Alarm solved
Figure 136: BCCH-SWITCH-FATAL: Corrective Actions
258 / 590
7.23 [6,42] RTMA-ALARM

specific Problems event Type probable Cause perceived Severity Alarm Description RTMA-ALARM Equipment Equipment Malfunction Major (PMA), Minor (DMA) A fault has been detected on the RTMA. Major (PMA): Both amplifier systems do not function correctly. Minor (DMA): One of the two amplifier systems does not function correctly. Alarm Number 1: Indicates a fault in System 1. 2: Indicates a fault in System 2. 255: Indicates a fault in both systems.
Major (PMA): The complete cell is lost. Minor (DMA): No impact on the telecom functions. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
259 / 590

[6,42] RTMA ALARM
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Onsite
Check antenna (DCS1800 only). Replace antenna if required.
Onsite
Check cables/connectors to RTMA, amplifier, antenna, rack unit and tower mounted unit visually and electrically. Replace cable if required.
Onsite
G1: Replace RTMA
Onsite OR
G2: Replace TMA
Onsite OR
G2: Replace RMC
RA operational?
yes
Alarm solved
Figure 137: RTMA-ALARM: Corrective Actions
260 / 590
7.24 [6,43] PERU-ALARM

specific Problems event Type probable Cause perceived Severity Alarm Description PERU-ALARM Equipment Equipment Malfunction Major (PMA), Minor (DMA) A fault has been detected on the pre-amplifier rack unit. Major (PMA): Both amplifier systems do not function correctly. Minor (DMA): One of the two amplifier systems does not function correctly. Alarm Number 1: Indicates a fault in System 1. 2: Indicates a fault in System 2. 255: Indicates a fault in both systems.
Major (PMA): The complete cell is lost. Minor (DMA): No impact on the telecom functions. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
261 / 590

[6,43] PERU ALARM
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Onsite
Check antenna (DCS1800 only). Replace antenna if required.
Onsite
Check cables/connectors to RTMA, amplifier, antenna, rack unit and tower mounted unit visually and electrically. Replace cable if required.
Onsite
G1: Replace RTMA
Onsite OR
G2: Replace TMA
Onsite OR
G2: Replace RMC
RA operational?
yes
Alarm solved
Figure 138: PERU-ALARM: Corrective Actions
262 / 590
7.25 [6,45] TEST-ABORTED

specific Problems event Type probable Cause perceived Severity Alarm Description TEST-ABORTED Equipment Equipment Under Test Warning (MI) Supervision test of alarm lines has been aborted because test is not possible (e.g., problems with the EACB).
263 / 590

[6,45] TESTABORTED
Lock Function RA
Unlock Function RA
EACB alarm events?
yes
Solve EACB alarm(s) first
no
Check OMU CPF against BTS hardware configuration parameters
RA operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
RA operational?
yes
Alarm solved
Figure 139: TEST-ABORTED: G1/G2 BTS Corrective Actions
264 / 590
7.26 [6,46] ALARM-TEST-FAILURE

specific Problems event Type probable Cause perceived Severity Alarm Description ALARM-TEST-FAILURE Equipment Equipment Under Test Warning (MI) Supervision test of alarm lines detected a failure on the Coupling or RFE. That is, the expected change of alarm lines did not occur during the test. 1: Coupling failure. 2: RFE failure.
Alarm Number
265 / 590

[6,46] ALARMTESTFAILURE
Lock Function RA
Unlock Function RA
RFE, EACB or combiner alarm events?
yes
no Check OMU CPF against BTS hardware configuration parameters
RA operational?
yes
Alarm solved
no
Onsite
Onsite
Replace RFE
Onsite
Replace EACB, EAIB
Onsite
Replace Combiner
OR
OR
RA operational?
yes
Alarm solved
Figure 140: ALARM-TEST-FAILURE: G1 BTS Corrective Actions
266 / 590

[6,46] ALARMTESTFAILURE
Lock Function RA
Unlock Function RA
RFE, EACB or combiner alarm events?
yes
no Check OMU CPF against BTS hardware configuration parameters
RA operational?
yes
Alarm solved
no
Onsite
Onsite
Replace RFE
Onsite
Replace SACE, SCFE Replace RTC
Onsite
Replace WBC
Onsite
OR
OR
OR
RA operational?
yes
Alarm solved
Figure 141: ALARM-TEST-FAILURE: G2 BTS Corrective Actions
267 / 590
7.27 [6,48] RF-FAULT

7.27.1 [6,48] RF-FAULT (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description RF-FAULT Equipment Equipment Malfunction Major (PMA) This alarm raised because the OMU has lost the state of the SBL CU and the BSC restored the state of the SBL RA to FOS. The alarm is put in the AIFL.
No further impact on the telecom functions, as the CU is isolated already. Impact Loss Degradation BSS Cell(s) X Signaling Calls -
268 / 590

[6,48] RFFAULT (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
Onsite OR
Replace Receiver
Replace Transmitter
CU operational?
yes
Alarm solved
Figure 142: RF-FAULT (CU): G1 BTS Corrective Actions
269 / 590

[6,48] RFFAULT (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
Onsite OR
Replace Receiver
Replace Transmitter
CU operational?
yes
Alarm solved
Figure 143: RF-FAULT (CU): G2 BTS Corrective Actions
270 / 590
7.27.2 [6,48] RF-FAULT (RA)

specific Problems event Type probable Cause perceived Severity Alarm Description RF-FAULT Equipment Equipment Malfunction Major (PMA) This alarm raised because the OMU has lost the state of the SBL RA and the BSC restored the state of the SBL RA to FOS. The alarm is put in the AIFL.
No further impact on the telecom functions, as the RA is isolated already. Impact Loss Degradation BSS Cell(s) X Signaling Calls -
271 / 590

[6,48] RFFAULT (RA)
Lock Function RA
Unlock Function RA
Onsite
G1: Replace Combiner
Onsite OR
G2: Replace RTC
Onsite OR
G2: Replace WBC
RA operational?
yes
Alarm solved
Figure 144: RF-FAULT (RA): Corrective Actions
272 / 590
7.28 [6,49] FRONTEND-AMP-AL

specific Problems event Type probable Cause perceived Severity Alarm Description FRONTEND-AMP-AL Equipment Equipment Malfunction Minor (DMA) One of the RFE amplifiers is faulty.
There is some disturbance to the telecom functions. Impact Loss Degradation BSS Cell(s) X Signaling X Calls X
273 / 590

[6,49] FRONTENDAMPAL
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Onsite
G1: Replace RFE
Onsite OR
G2: Replace RFE
RA operational?
yes
Alarm solved
Figure 145: FRONTEND-AMP-AL: Corrective Actions
274 / 590
7.29 [6,50] DATA-INCONSIS-AL

specific Problems event Type probable Cause perceived Severity Alarm Description DATA-INCONSIS-AL Equipment Indeterminate Major (PMA) An inconsistency of the populated data concerning the BCCH switch was detected. The inconsistency was between the data in the CDM, and the data in the OMU CPF.
The BTS is unable to handle telecom traffic. The cell is lost. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
275 / 590

[6,50] DATAINCONSISAL]
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Check OMU CPF against BTS BCCH switch configuration parameters, use:
OR
Change BTS Familiy
OR
Change BTS Characteristics
RA operational?
yes
Alarm solved
Figure 146: DATA-INCONSIS-AL: Corrective Actions
276 / 590
7.30 [6,51] RTC-OUT-OF-BAND-ALARM

specific Problems event Type probable Cause perceived Severity Alarm Description RTC-OUT-OF-BAND-ALARM Equipment Transmitter Failure Minor (DMA), Warning (MI) Minor: The indicated cavity is out of bounds. Internal autonomous actions were not able to correct the fault. Warning: The indicated cavity was out of bounds, but internal autonomous actions were able to correct the fault. Alarm Number Indicates the cavity number 1...8.
Minor (DMA): The eight channels supported by the failing cavity are lost. The BCCH is regained through recovery. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
Warning (MI): If frequency hopping is used, during the re-tuning period for the RTCs, the quality of the calls routed through the modified cavity can be degraded (#). If non-hopping, then eight calls are lost during this period. After re-tuning, all channels are available. (X). Impact Loss Degradation BSS Cell(s) X Signaling X Calls X #
277 / 590

Disable RF Power Use the BTS Terminal to disable RA before disconnecting RF cables. Initialize RA after work. If the alarm severity (category) is Minor (DMA) or the alarm with severity (category) Warning (Mi) occurs frequently:
[6,51] RTCOUTOF BANDALARM
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Onsite
Onsite OR
G2: Replace RTC
Onsite OR
G2: Replace WBC
RA operational?
yes
Alarm solved
Figure 147: RTC-OUT-OF-BAND-ALARM: Corrective Actions
278 / 590
7.31 [6,52] RTC-FINE-TUNING-FAIL

specific Problems event Type probable Cause perceived Severity Alarm Description RTC-FINE-TUNING-FAIL Equipment Transmitter Failure Minor (DMA), Warning (MI) Minor: The indicated cavity has a fine tuning failure. Internal autonomous actions were not able to correct the fault. Warning: The indicated cavity had a fine tuning failure, but internal autonomous actions were able to correct the fault. Alarm Number Indicates the cavity number 1...8.
Minor (DMA): The eight channels supported by the failing cavity are lost. The BCCH is regained through recovery. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
Warning (MI): If frequency hopping is used, during the re-tuning period for the RTCs, the quality of the calls routed through the modified cavity can be degraded (#). If non-hopping, then eight calls are lost during this period. After re-tuning, all channels are available. (X). Impact Loss Degradation BSS Cell(s) X Signaling X Calls X #
279 / 590

Disable RF Power Use the BTS Terminal to disable RA before disconnecting RF cables. Initialize RA after work. If the alarm severity (category) is Minor (DMA) or the alarm with severity (category) Warning (Mi) occurs frequently:
[6,52] RTCFINE TUNINGFAIL
Restart OMU
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
Onsite
Onsite OR
G2: Replace RTC
Onsite OR
G2: Replace WBC
RA operational?
yes
Alarm solved
Figure 148: RTC-FINE-TUNING-FAIL: Corrective Actions
280 / 590
7.32 [6,53] RTC-PARKING-FAILURE

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number RTC-PARKING-FAILURE Equipment Transmitter Failure Major (PMA) The indicated cavity fails to reach its parking position. Indicates the cavity number 1...8.
281 / 590

[6,53] RTCPARKINGFAILURE
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Onsite
Onsite OR
G2: Replace RTC
Onsite OR
G2: Replace WBC
RA operational?
yes
Alarm solved
Figure 149: RTC-PARKING-FAILURE: Corrective Actions
282 / 590
7.33 [6,54] RTC-SELFTEST-FAILURE

specific Problems event Type probable Cause perceived Severity Alarm Description RTC-SELFTEST-FAILURE Equipment Transmitter Failure Major (PMA) There is a fault with the RTC. The self-test indicates a problem with the complete RTC.
The BTS is unable to handle telecom traffic. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
283 / 590

[6,54] RTCSELFTESTFAILURE
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Onsite
Check cables/connectors between basic and extension unit
Onsite
Onsite OR
G2: Replace RTC
Onsite OR
G2: Replace WBC
RA operational?
yes
Alarm solved
Figure 150: RTC-SELFTEST-FAILURE: Corrective Actions
284 / 590
7.34 [6,55] RTC-EXT-CONN-LOST

specific Problems event Type probable Cause perceived Severity Alarm Description RTC-EXT-CONN-LOST Equipment Transmitter Failure Major (PMA) The connection to the RTC extension unit is lost.
The channels supported by the RTC extension unit are lost (CU 5 - 8). The BCCH is maintained. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
285 / 590

[6,55] RTCEXT CONNLOST
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite OR
G2: Replace RTC
Onsite OR
G2: Replace WBC
RA operational?
yes
Alarm solved
Figure 151: RTC-EXT-CONN-LOST: Corrective Actions
286 / 590
7.35 [6,56] RTC-DETECTOR-FAILURE

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number RTC-DETECTOR-FAILURE Equipment Transmitter Failure Major (PMA) The RTC detector is faulty. 1: Failure in RTC basic unit. 2: Failure in RTC extension unit.
If the alarm number is 1, the channels supported by the reported RTC (CU 1 - 4) are lost. The BCCH is lost if the basic unit is lost. (#). If the alarm number is 2, the channels supported by the extension unit are lost (CU 5 - 8). (X). Impact Loss Degradation BSS X# Cell(s) X# Signaling X# Calls X# -
287 / 590

[6,56] RTCDETECTORFAILURE
Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
Onsite
OR
G2: Replace RTC
OR
G2: Replace WBC
RA operational?
yes
Alarm solved
Figure 152: RTC-DETECTOR-FAILURE: Corrective Actions
288 / 590

7.36.1 [6,240] MISSING-ENTRY-IN-CPF (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description MISSING-ENTRY-IN-CPF Processor Error Configuration Or Customization Error Major (PMA) An expected entry in the OMU CPF was not found. Equipment identification for a CU is not included in the CPF.
The eight channels supported by the CU are lost. Impact Loss Degradation BSS X Cell(s) X Signaling Calls X -
289 / 590

[6,240] MISSINGENTRYINCPF (CU)
Change Cell Type
Reset BTS
CU operational?
yes
Alarm solved
290 / 590
7.36.2 [6,240] MISSING-ENTRY-IN-CPF (RA)

specific Problems event Type probable Cause perceived Severity Alarm Description MISSING-ENTRY-IN-CPF Processor Error Configuration Or Customization Error Major (PMA) An expected entry in the OMU CPF was not found. Equipment identification for an RTC is not included in the CPF.
All cavities supported by the RTC are lost. The cell is lost. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
291 / 590

[6,240] MISSINGENTRYINCPF (RA)
Change Cell Type
Reset BTS
RA operational?
yes
Alarm solved
292 / 590

7.37.1 [6,241] INCONSIST-ASSHW-ACTHW (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description INCONSIST-ASSHW-ACTHW Processing Error Configuration Or Customization Error Major (PMA) The equipped BTS hardware does not match to the assumed hardware capabilities. 2: The hardware does not provide the requested frequency band. 4: The hardware does not provide advanced timing, but it is configured as the outer cell of an extended cell.
Alarm Number
The eight channels supported by the CU are lost. Impact Loss Degradation BSS X Cell(s) X Signaling Calls X -
293 / 590

Alarm Number 2
Check the network type against CU hardware. Use:
OR
Onsite
G1: Replace Receiver
Onsite
G1: OR Replace Transmitter
Onsite
Onsite OR
OR
CU operational?
yes
Alarm solved
Figure 155: INCONSIST-ASSHW-ACTHW: Alarm Number 2 Corrective Actions
294 / 590

Alarm Number 4
Check the cell range against CU hardware. Use:
Onsite
OR
Modify actual BTS hardware capability by replacing existing BTS entity by appropriate BTS hardware entity, as descibed in the CMA
Onsite
Onsite
Onsite
Onsite OR
OR
CU operational?
yes
Alarm solved
295 / 590
7.37.2 [6,241] INCONSIST-ASSHW-ACTHW (RA)

specific Problems event Type probable Cause perceived Severity Alarm Description INCONSIST-ASSHW-ACTHW Processing Error Configuration Or Customization Error Major (PMA) The BTS hardware does not match the assumed hardware capabilities. The hardware does not provide the requested frequency band.
All cavities supported by the RTC are lost. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
296 / 590

[6,241] INCONSISTASSHWACTHW (RA)
Check the network type against CU hardware. Use:
OR
Onsite
Onsite
Onsite
Onsite OR
OR
RA operational?
yes
Alarm solved
Figure 157: INCONSIST-ASSHW-ACTHW: Corrective Actions
297 / 590

7.38.1 [6,246] CONFIG-FAIL (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description CONFIG-FAIL Processing Error Configuration Or Customization Error Major (PMA) The configuration of the CU is unsuccessful due to a bad configuration parameter or CU problems.
The eight time slots supported by the reporting CU are lost. Through recovery, the BCCH is maintained. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
298 / 590

[6,246] CONFIGFAIL (CU)
Lock Function CU
Unlock Function CU
Other CU alarm(s) events?
yes
Solve CU alarm(s) first
no
CU operational?
yes
Alarm solved
no
Check validity of parameters: ARFN, BSCI
yes
More than one CU reports alarm?
no Correct Configuration Parameters
Onsite
Onsite
Onsite
Onsite OR
OR
CU operational?
yes
Alarm solved
CU operational?
yes
Alarm solved
Figure 158: CONFIG-FAIL (CU): Corrective Actions
299 / 590
7.38.2 [6,246] CONFIG-FAIL (RA)

specific Problems event Type probable Cause perceived Severity Alarm Description CONFIG-FAIL Processing Error Configuration Or Customization Error Major (PMA) The RTC configuration fails.
The BTS is unable to handle telecom traffic, the cell is lost. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
300 / 590

Lock Function RA
Unlock Function RA
RA operational?
yes
Alarm solved
no
Check validity of parameter ARFCN
Correct Cell Logical Parameters
Restart OMU
RA operational?
yes
Alarm solved
no
Onsite
Onsite OR
G2: Replace RTC
Onsite OR
G2: Replace WBC
RA operational?
yes
Alarm solved
Figure 159: CONFIG-FAIL (RA): Corrective Actions
301 / 590
7.39 [6,247] RESET

7.39.1 [6,247] RESET (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description RESET Processing Error Software Error Warning (MI) The CU auto-resets successfully. This is caused, for example, by the expiration of a watchdog timer during operational mode.
If redundancy is used, there is no disturbance of the telecom applications. If redundancy is not used there is a loss of calls, and the cell and BCCH signaling is lost for a short period (0.5 - 1 minute). (X). Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
302 / 590

[6,247] RESET (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
Figure 160: RESET (CU): Corrective Actions
303 / 590

7.40.1 [6,250] NO-ANSWER-DCL (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description NO-ANSWER-DCL Processing Error Underlying Resource Unavailable Major (PMA), Minor (DMA) Major (PMA): No answer on the Q1 bus from a CU when a command is sent from the OMU during initialization or reconfiguration. Minor (DMA): No answer from a CU to two polls from the OMU on the Q1 bus.
Major (PMA): The fault is detected during initialization or reconfiguration in all the cases (Q1 or CU malfunction). Eight channels which were to be supported by the CU are lost. (X). Minor (DMA): In case of Q1 malfunction, there is no disturbance of telecom applications. In case of CU malfunction, the result depends on the fault: the CU can eventually go on with the previous configuration. If the fault is fatal, other alarms will appear on other equipment. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
304 / 590

[6,250] NOANSWERDCL (CU)
Lock Function CU
Restart OMU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Check Token Bus cables/connectors to OMU and CU
Alarm is provoked by loss of EACB as Q1 repeater
yes
All CUs in same cabinet report simultaneously this alarm?
no
Onsite
G1: Replace EACB/EAIB
Onsite
Onsite
Onsite
Onsite OR
OR
CU operational?
yes
Alarm solved
CU operational?
yes
Alarm solved
Figure 161: NO-ANSWER-DCL (CU): Corrective Actions
305 / 590
7.40.2 [6,250] NO-ANSWER-DCL (RA)

specific Problems event Type probable Cause perceived Severity Alarm Description NO-ANSWER-DCL Processing Error Underlying Resource Unavailable Major (PMA), Minor (DMA) Major (PMA): No answer on the Q1 bus from a RTC when a command is sent from the OMU during initialization or reconfiguration. Minor (DMA): No answer from an RTC to two polls from the OMU on the Q1 bus.
Major (PMA): The fault is detected during initialization or reconfiguration in all the cases (Q1 or RTC malfunction). The BTS is lost. (X). Minor (DMA): In case of Q1 malfunction, there is no disturbance of telecom applications. In case of RTC malfunction, the result depends on the fault: the RTC can eventually go on with the previous configuration. If the fault is fatal, other alarms will appear on other equipment. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
306 / 590

[6,250] NOANSWERDCL (RA)
Lock Function RA
Restart OMU
Unlock Function RA
RA operational?
yes
Alarm solved
no
Check Token Bus cables/connectors to OMU and RTC
Alarm is provoked by loss of EACB as Q1 repeater
yes
All RTCs in same cabinet report simultaneously this alarm?
no
Onsite
G1: Replace EACB/EAIB
Onsite
Onsite OR
G2: Replace RTC
Onsite OR
G2: Replace WBC
RA operational?
yes
Alarm solved
RA operational?
yes
Alarm solved
Figure 162: NO-ANSWER-DCL (RA): Corrective Actions
307 / 590
7.41 [6,251] SELF-TEST-AL

7.41.1 [6,251] SELF-TEST-AL (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description SELF-TEST-AL Equipment Equipment Malfunction Major (PMA), Minor (DMA) Major (PMA): A self-test fails on the only receiver of CU. The CU cannot function. Minor (DMA): A self-test fails on one of the two receivers of a CU. The CU can still function. Alarm Number 1: Fault on the first receiver. 1: Fault on the second receiver.
Major (PMA): The eight channels supported by the CU are lost. The BCCH is regained through recovery. ( X). Minor (DMA): The antenna diversity functionality is lost, there is a loss of quality of calls. (#). Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X #
308 / 590

[6,251] SELFTESTAL (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
Onsite OR
CU operational?
yes
Alarm solved
Figure 163: SELF-TEST-AL (CU): Corrective Actions
309 / 590
7.42 [6,252] SELF-TEST-DBLE-AL (CU)

specific Problems event Type probable Cause perceived Severity Alarm Description SELF-TEST-DBLE-AL Equipment Equipment Malfunction Major (PMA) A self-test fails on both receivers of a CU.
310 / 590

[6,252] SELFTEST DBLAL (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
Onsite OR
CU operational?
yes
Alarm solved
Figure 164: SELF-TEST-DBLE-AL (CU): Corrective Actions
311 / 590
7.43 [6,255] Q1-RELAY-FAULT

7.43.1 [6,255] Q1-RELAY-FAULT (CU)
specific Problems event Type probable Cause perceived Severity Alarm Description Q1-RELAY-FAULT Equipment Equipment Malfunction Minor (DMA) Failure on the Q1 relay. The CU cannot disconnect itself from the Q1 bus.
312 / 590

[6,255] Q1RELAY FAULT (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
Onsite
Replace Receiver
OR
Replace Transmitter
CU operational?
yes
Alarm solved
Figure 165: Q1-RELAY-FAULT (CU): G1 BTS Corrective Actions
313 / 590

[6,255] Q1RELAY FAULT (CU)
Lock Function CU
Unlock Function CU
CU operational?
yes
Alarm solved
no
Onsite
Onsite
Replace Receiver
OR
Replace Transmitter
CU operational?
yes
Alarm solved
Figure 166: Q1-RELAY-FAULT (CU): G2 BTS Corrective Actions
314 / 590
7.43.2 [6,255] Q1-RELAY-FAULT (RA)

specific Problems event Type probable Cause perceived Severity Alarm Description Q1-RELAY-FAULT Equipment Equipment Malfunction Minor (DMA) Failure on the Q1 relay. The RTC cannot disconnect itself from the Q1 bus.
315 / 590

[6,255] Q1RELAY FAULT (RA)
Lock Function RA
Unlock Function RA
Onsite
Onsite OR
G2: Replace RTC
Onsite OR
G2: Replace WBC
RA operational?
yes
Alarm solved
Figure 167: Q1-RELAY-FAULT (RA): Corrective Actions
316 / 590
8 Class 7: FU Alarms
This section defines the alarms for the Class 7: FU alarm class.
317 / 590
8.1 [7,1] AL-LIST-ER

specific Problems event Type probable Cause perceived Severity Alarm Description AL-LIST-ER Processing Error Software Error Warning (MI) The FU internal alarms list is erased. This alarm is caused by either: an FU alarm overflow because OMU has not read FU alarms before the FU has reached its maximum storage for alarms or loss of alarm list (as all other data) due to a hardware watchdog (DRFU only) If this alarm occurs consecutively, this can indicate OMU failure or external FU link failure. If there are no or few FU alarms the problem can be due either to: fast external FU link toggling (appearance/disappearance) an OMU problem in the reading of FU alarm (too slow). The OMU recovers the FU internal Alarms in Force list autonomously.
318 / 590
8.1.1 DRFU Corrective Actions

[7,1] ALLISTER
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Alarm 7,33 events?
yes
Solve this alarm
Figure 168: AL-LIST-ER: DRFU Corrective Actions
319 / 590
8.1.2 OMU Corrective Actions

[7,1] ALLISTER
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
OMU alarm(s) events?
yes
Check for OMU alarm(s) (for example 6,247 RESET) to detemine if the OMU was not busy so the FU could not be polled (FU alarm not ready by OMU). Solve this alarm.
Figure 169: AL-LIST-ER: OMU Corrective Actions
320 / 590
8.2 [7,3] MCL-LINK

specific Problems event Type probable Cause perceived Severity Alarm Description MCL-LINK Equipment Timing Problem Minor (DMA) A fault is detected on the clock link indicated. The other link is working correctly. 1: Clock Link 1. 2: Clock Link 2.
Alarm Number
321 / 590

[7,3] MCLLINK
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Onsite
Check cables to clock system and FU
Onsite
G1: Replace Frame Unit
Onsite
OR
FU operational?
yes
Alarm solved
Figure 170: MCL-LINK: Corrective Actions
322 / 590
8.3 [7,5] BSI-LINK-0

specific Problems event Type probable Cause perceived Severity Alarm Description BSI-LINK-0 Communication Loss Of Signal Minor (DMA) A fault is detected on the BSI link by the FU. This alarm is given when the fault appears. If the fault is present during more than one BSI_TIMER (FU TIMER), an OFF alarm is sent and alarm [7,6] is generated. BSI link redundancy is not supported (only BSI link 0 is connected between BIE and BTS).
Telecom functions can be affected. Disturbances are dependent of telecom mechanism (timers, protocol,...) and duration of the fault (maximum is fixed by BSI_TIMER). For example, calls will be released if this fault lasts more than T_SYNC (FU timer) due to remote transcoder alarm. Impact Loss Degradation BSS X Cell(s) X Signaling Calls X
323 / 590

[7,5] BSILINKO
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Onsite
Check cables to BIE on BTS side and FU
Onsite
Onsite
OR
FU operational?
yes
Alarm solved
Figure 171: BSI-LINK-0: Corrective Actions
324 / 590
8.4 [7,6] BOTH-BSI-LINKS

specific Problems event Type probable Cause perceived Severity Alarm Description BOTH-BSI-LINKS Communication Loss Of Signal Major (PMA) A fault is detected on the BSI link of the FU during more than BSI-TIMER (FU-Timer). BSI link redundancy is not supported (only BSI link 0 is connected between BIE and BTS).
The FU is lost, and the eight time slots supported by the FU are lost. The BCCH of the cell is maintained through recovery mechanisms. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
325 / 590

[7,6] BOTHBSILINKS
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Onsite
Check cables to BIE on BTS side and FU
Onsite
Onsite
OR
FU operational?
yes
Alarm solved
Figure 172: BOTH-BSI-LINKS: Corrective Actions
326 / 590
8.5 [7,7] FHI-LK0-FUL-UNV

specific Problems event Type probable Cause perceived Severity Alarm Description FHI-LK0-FUL-UNV Communication Loss Of Signal Minor (DMA) The FHI link 0 is fully unavailable on uplink (eight time slots). This is detected during a FU/CU loop test.
The antenna diversity capability is lost, the quality of calls are degraded. Impact Loss Degradation BSS Cell(s) Signaling X Calls X
327 / 590

[7,7] FHILK0FULUNV
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Onsite
Check cables between FHUs/CUs and FU
Onsite
Onsite
Onsite
OR
OR
FU operational?
yes
Alarm solved
Figure 173: FHI-LK0-FUL-UNV: Corrective Actions
328 / 590
8.6 [7,8] FHI-LK1-FUL-UNV

specific Problems event Type probable Cause perceived Severity Alarm Description FHI-LK1-FUL-UNV Communication Loss Of Signal Major (PMA) The FHI link 1 is fully unavailable on uplink (eight time slots). This is detected during a FU/CU loop test.
The antenna diversity capability is lost, the quality of calls are degraded. Impact Loss Degradation BSS Cell(s) Signaling X Calls X
329 / 590

[7,8] FHILK1FULUNV
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
Onsite
OR
OR
FU operational?
yes
Alarm solved
Figure 174: FHI-LK1-FUL-UNV: Corrective Actions
330 / 590
8.7 [7,14] FHU-DUMMY-BURST-GEN-FAIL

specific Problems event Type probable Cause perceived Severity Alarm Description FHU-DUMMY-BURST-GEN-FAIL Processing Error Software Error Major (PMA) Failure on switching off dummy burst generation for the FU.
The eight time slots supported by the reporting FU are lost. Through reconfiguration, the BCCH is maintained. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
331 / 590

[7,14] FHUDUMMYBURSTGENFAIL
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Alarm 4,1 events?
yes
Solve this alarm.
Figure 175: FHU-DUMMY-BURST-GEN-FAIL: Corrective Actions
332 / 590
8.8 [7,31] HW-FAIL

specific Problems event Type probable Cause perceived Severity Alarm Description HW-FAIL Equipment Equipment Malfunction Major (PMA), Warning (MI) There is an internal hardware failure, or a failure on the external clock links is detected on the FU during auto-test/test. The OMU makes one attempt to overcome the alarm situation autonomously and to reset the FU. Major (PMA): The reset is unsuccessful and the Managed Object (SBL) FU is put to Unlocked/Disabled (FOS). Warning (MI): The reset is successful.
Major (PMA): If there is a FU state change, the eight channels supported by the FU are lost. The BCCH is regained through recovery. (X). Warning (MI): If there is no FU state change, there is no impact on the telecom capabilities. During the auto-test, the calls ongoing were lost. (#). Impact Loss Degradation BSS X Cell(s) X Signaling X# Calls X# -
333 / 590

[7,31] HWFAIL
Lock Function FU
Unlock Function FU
CLLK alarm events?
yes
External clock link is missing, solve CLLK alarm.
no
FU operational?
yes
Alarm solved
Onsite
Check clock cables/connectors visually and elctrically. Relace cable if required.
no Onsite Check BTS status with BTS terminal
FU operational?
yes
Alarm solved
no
Onsite
no
Onsite
OR
FU operational?
yes
Alarm solved
Figure 176: HW-FAIL: Corrective Actions
334 / 590
8.9 [7,32] NR-SW-FAIL

specific Problems event Type probable Cause perceived Severity Alarm Description NR-SW-FAIL Processing Error software Program Abnormally Terminated Major (PMA), Warning (MI) A check-sum error was detected in one of the following during fault localization for: the SCP of the FU the software of the FU the DSP the saved parameters for FU configuration. The OMU makes one attempt to overcome the alarm situation autonomously and to reset the FU. Major (PMA): The reset is unsuccessful and the Managed Object (SBL) FU is put to Unlocked/Disabled (FOS). Warning (MI): The reset is successful.
Major (PMA): If there is a FU state change, the eight channels supported by the FU are lost. The BCCH is regained through recovery (X). Warning (MI): No impact on the telecom capabilities. The calls ongoing were lost. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -

335 / 590
8.10 [7,33] NR-SCP-MP-FAULT

specific Problems event Type probable Cause perceived Severity Alarm Description NR-SCP-MP-FAULT Processing Error software Program Abnormally Terminated Major (PMA), Warning (MI) A non-recoverable FUCO SCP micro-processor fault has occurred. The OMU makes one attempt to overcome the alarm situation and to reset the FU. Major (PMA): The reset is unsuccessful and the Managed Object (SBL) FU is put to Unlocked/Disabled (FOS). Warning (MI): The reset is successful.
Major (PMA): If there is a FU state change, the eight channels supported by the FU are lost. The BCCH is regained through recovery (X). Warning (MI): No impact on the telecom capabilities. The calls ongoing were lost. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -

336 / 590
8.11 [7,34] BOTH-FHI-LINKS

specific Problems event Type probable Cause perceived Severity Alarm Description BOTH-FHI-LINKS Communication Loss Of Signal Major (PMA) Both FHI links are unavailable (eight time slots). The FU is unusable until at least one link becomes available.
The eight time slots supported by the reporting FU are lost. Through recovery, the BCCH is maintained. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
337 / 590

[7,34] BOTHFHILINKS
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
G1: Replace FQHU
OR
FU operational?
yes
Alarm solved
Figure 177: BOTH-FHI-LINKS: G1 BTS Corrective Actions
338 / 590

[7,34] BOTHFHILINKS
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
FU operational?
yes
Alarm solved
Figure 178: BOTH-FHI-LINKS: G2 BTS Corrective Actions
339 / 590
8.12 [7,35] BOTH-CLOCKS-LINKS

specific Problems event Type probable Cause perceived Severity Alarm Description BOTH-CLOCKS-LINKS Equipment Timing Problem Major (PMA) The FU detects faults on both clock links. The FU is unusable until at least one link becomes available.
340 / 590

[7,35] BOTHCLOCKLINKS
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Onsite
Check cables between clock system and FU
Onsite
Onsite
G1: Replace FQHU
OR
FU operational?
yes
Alarm solved
Figure 179: BOTH-CLOCK-LINKS: G1 BTS Corrective Actions
341 / 590

[7,35] BOTHCLOCKLINKS
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Onsite
Check cables between clock system and FU
Onsite
Onsite
OR
FU operational?
yes
Alarm solved
Figure 180: BOTH-CLOCK-LINKS: G2 BTS Corrective Actions
342 / 590
8.13 [7,36] FU-FAULT

specific Problems event Type probable Cause perceived Severity Alarm Description FU-FAULT Equipment Equipment Malfunction Warning (MI) If the FU alarm disappears and the OMU loses the alarm information, FU-FAULT is sent by the OMU as a dummy alarm. This indicates the FU is FOS and an operator initialization is required.
There is no further impact on the telecom capability. Impact Loss Degradation BSS Cell(s) X Signaling X Calls -

[7,36] FUFAULT
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
Figure 181: FU-FAULT: Corrective Actions
343 / 590

specific Problems event Type probable Cause perceived Severity Alarm Description MISSING-ENTRY-IN-CPF Processor Error Configuration Or Customization Error Major (PMA) An expected entry in the OMU CPF was not found. The entry for the FU generation is not included in the CPF.
The eight time slots supported by the FU are lost. The BCCH is maintained through reconfiguration. Impact Loss Degradation BSS X Cell(s) X Signaling Calls X -
344 / 590

Change Cell Type
Reset BTS
FU operational?
yes
Alarm solved
345 / 590

specific Problems event Type probable Cause perceived Severity Alarm Description Alarm Number INCONSIST-ASSHW-ACTHW Processing Error Configuration Or Customization Error Major (PMA) The BTS hardware does not match the assumed hardware capabilities. 1: The BTS hardware does not provide the requested ciphering algorithm. 8: The FU software package received from the OMC-R/BSC does not match the FU hardware. 9: The BTS hardware does not provide the requested configuration for full-rate/half-rate channels.
Alarm number 1 or 9: The eight time slots supported by the FU are lost. The BCCH is maintained through reconfiguration. Alarm number 8: The FU cannot perform telecom functions as the configuration is incomplete. Impact Loss Degradation BSS X Cell(s) X Signaling Calls X -
346 / 590

Alarm Number 1
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Check ciphering capability against BTS hardware. Use:
Onsite Modify actual BTS hardware capability by replacing existing BTS entity by appropriate BTS hardware entity.
OR
Onsite
Onsite OR
FU operational?
yes
Alarm solved
347 / 590

Alarm Number 8
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no Onsite Modify actual BTS hardware capability by replacing existing BTS entity by appropriate BTS hardware entity.
yes
FU software package is correct?
no
Replace software package
Onsite
Onsite OR
FU operational?
yes
Alarm solved
FU operational?
yes
Alarm solved
348 / 590

Alarm Number 9
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Check hardware fullrate/halfrate capability against FU hardware. Use:
Onsite Modify actual BTS hardware capability by replacing existing BTS entity by appropriate BTS hardware entity.
OR
Onsite
Onsite OR
FU operational?
yes
Alarm solved
349 / 590
8.16 [7,242] INCONSIST-actHW-logConfig

specific Problems event Type probable Cause perceived Severity Alarm Description INCONSIST-actHW-logConfig Processing Error Configuration Or Customization Error Major (PMA) The BTS hardware does not match the logical configuration. The hardware does not provide the requested baseband or radio hopping capability.
The eight time slots supported by the FU are lost. The BCCH is maintained through reconfiguration. Impact Loss Degradation BSS X Cell(s) X Signaling Calls X -
350 / 590

[7,242] INCONSIST actHWlogConfig
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
Check frequency definition against number of equipped CUs.
Correct frequncy definition, if required.
FU operational?
yes
Alarm solved
Figure 186: INCONSIST-actHW-logConfig: Corrective Actions
351 / 590
8.17 [7,243] INCONSIST-actHW-BTSparam

specific Problems event Type probable Cause perceived Severity Alarm Description INCONSIST-actHW-BTSparam Processing Error Configuration Or Customization Error Major (PMA) The BTS hardware does not match the BTS parameter setting. The FU cannot support 16 kbit/s.
The eight time slots supported by the reporting FU are lost. Through recovery, the BCCH is maintained. Impact Loss Degradation BSS X Cell(s) X Signaling Calls X -
352 / 590

[7,243] INCONSIST actHWBTSparam
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
Check BSI link type of concerned TCUA and FU hardware.
Correct BSI link type, if required.
FU operational?
yes
Alarm solved
Figure 187: INCONSIST-actHW-BTSparam: Corrective Actions
353 / 590
8.18 [7,245] SW-DLL-FAIL

specific Problems event Type probable Cause perceived Severity Alarm Description SW-DLL-FAIL Processing Error CorruptData Major (PMA) An error is detected during the software down-load from the OMU to the FU.
There is no further impact on the telecom capability of the system (the FU was not in service before the fault occurred). The FU remains isolated until the down-load and initialization is completed. Impact Loss Degradation BSS Cell(s) X Signaling X Calls -
354 / 590

[7,245] SWDLLFAIL
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
Check FU hardware/software compatibility.
Correct compatibility, if required.
FU operational?
yes
Alarm solved
Figure 188: SW-DLL-FAIL: Corrective Actions
355 / 590

specific Problems event Type probable Cause perceived Severity Alarm Description CONFIG-FAIL Processing Error Configuration Or Customization Error Major (PMA) The configuration of the FU is unsuccessful due to a bad configuration parameter or FU problems.
356 / 590

[7,246] CONFIGFAIL
Lock Function FU
Unlock Function FU
other FU alarm events? no
yes
Solve that FU alarm(s) first
FU operational?
yes
Alarm solved
no There is a severe problem with the configuration parameters. Check the parameter validity of cell information elemtent 1/2, BSS parameters, channel configuration, BTS hardware configuration.
no
yes More than one FU reports this alarm?
Onsite
Onsite OR
Correct configuration parameters
FU operational?
yes
FU operational? Alarm solved no
yes
Alarm solved
357 / 590
8.20 [7,248] RESTART

specific Problems event Type probable Cause perceived Severity Alarm Description RESTART Processing Error Software Error Warning (MI) The FU restarts successfully and the trigger for the restart is indicated with the Alarm Number. 1: No reason indicated. 10: SCP or DSP exception. 12: FU telecom configuration problem (e.g., time out or algorithm configuration parameters refused during FU initialization). 13: Other cases (e.g., spurious hardware problems or hardware problems not detected by self-testing). 14: Problems during TS configuration occurred. 15: System information 3 value out of range. 17: Push-button action by operator (no TLV 61 sent). 18: Failure of the LAP-D link for more than "BCCH cut" timer.
Alarm Number
If the FU supporting the BCCH is not concerned, during the restart the FU loses all calls. After the successful restart the FU is usable. If the FU supporting the BCCH is concerned, during the restart the FU loses all calls. After the successful restart the FU is usable. The BCCH is regained through recovery. Impact Loss Degradation BSS Cell(s) X Signaling X Calls X -
358 / 590

[7,248] RESTART
Lock Function FU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Check configuration parameters
Correct configuration parameters (not alarm number 17)
FU operational?
yes
Alarm solved
Figure 190: RESTART: Corrective Actions If the FU restarts repeatedly in a short period of time, there can be a hardware problem, wrong configuration parameters sent, or the FU software can be corrupt.
359 / 590

specific Problems event Type probable Cause perceived Severity Alarm Description NO-ANSWER-DCL Processing Error Underlying Resource Unavailable Major (PMA), Minor (DMA) There is no answer on the Token bus from a FU, to polling from the OMU. Major (PMA): There is no response during initialization or re -configuration scenario. Minor (DMA): There is no answer within more than two polling cycles.
Major (PMA): If detected during initialization or re-configuration of the unit, the unit is isolated. Thus the eight time slots supported by the reported FU are lost. Through recovery, the BCCH is maintained. Minor (DMA): In case of a Token Bus malfunction. There is no impact on the telecom capabilities. In case of FU malfunction, the result depends on the fault. The FU can eventually go on with the previous configuration. If the fault is fatal, other alarms will appear on other equipment. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
360 / 590

[7,250] NOANSWERDCL
Lock Function FU
Restart OMU
Unlock Function FU
FU operational?
yes
Alarm solved
no
Check Token Bus cables/connectors to OMU and FU
yes
RIT is a DRFU?
no
Onsite
G1: Replace DRFU and DRFE
Onsite
Onsite
OR
FU operational?
yes
Alarm solved
FU operational?
yes
Alarm solved
361 / 590
362 / 590
9 Class 8: G-BTS Alarms

This section defines the alarms for the Class 8: G-BTS alarm class.
363 / 590
9.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.
364 / 590
9.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 192: IGNORE EQUIPMENT OVER 12 TRE: Corrective Actions
365 / 590
9.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 193: TOO MANY PLUGGED MODULES: Corrective Actions
366 / 590
9.4 [8,6] TB-FAILURE

specific Problems event Type probable Cause perceived Severity Alarm Description TB-FAILURE Equipment Equipment Malfunction Major (PMA) The communication with all units on the Token Bus, which are In Traffic, is faulty.
Telecom functions are not affected as long as no recovery is needed. If recovery is needed, the cell is lost temporarily and all calls are lost. Impact Loss Degradation BSS Cell(s) Signaling Calls -
367 / 590
9.4.1 G1/G2 Corrective Actions

[8,6] TBFAILURE
Reset BTS
BTS operational?
yes
Alarm solved
no
Check Token Bus cables/connectors at OMU side
Onsite
G1: Replace OMUA
Onsite
G2: Replace SACE/SCFE
OR
BTS operational?
yes
Alarm solved
Figure 194: TB-FAILURE: G1/G2 Corrective Actions
368 / 590
9.5 [8,7] Q1-FAILURE

specific Problems event Type probable Cause perceived Severity Alarm Description Q1-FAILURE Equipment Equipment Malfunction Major (PMA) The communication with all units on the Q1 Bus, which are In Traffic, is faulty.
Telecom functions are not affected as long as no recovery is needed. If recovery is needed, the cell is lost temporarily and all calls are lost. Impact Loss Degradation BSS Cell(s) Signaling Calls -
369 / 590
9.5.1 G1/G2 Corrective Actions

[8,7] Q1FAILURE
Reset BTS
BTS operational?
yes
Alarm solved
no
Check Q1 Bus cabling at OMU side
Onsite
G1: Replace OMUA
Onsite
G2: Replace SACE/SCFE
OR
BTS operational?
yes
Alarm solved
Figure 195: Q1-FAILURE: G1/G2 Corrective Actions
370 / 590
9.6 [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.
371 / 590
9.7 [8,26] RACH-CATCHER-LOST

specific Problems event Type probable Cause perceived Severity Alarm Description RACH-CATCHER-LOST Equipment Receiver Failure Major (PMA) The RACH catcher function of an inner cell BTS is lost. This applies to extended cell configurations only. 1: BCB link is unable to detect the presence of the modules. 2: BCB Power supply is faulty.
Alarm Number
Outgoing calls are not possible for Mobile Stations in the inner cell that camp on the outer cell BCCH frequency. Active calls are not affected. Impact Loss Degradation BSS Cell(s) X (Inner Cell) Signaling X (Inner Cell) Calls -
372 / 590

[8,26] RACHCATCHERLOST
Lock Function BTS
Unlock Function BTS
BTS operational?
yes
Alarm solved
no
CU,FHU, FU or RA alarm(s) events?
yes
Solve that alarm(s)
no
BTS operational?
yes
Alarm solved
Figure 196: RACH-CATCHER-LOST: Corrective Actions
373 / 590
9.8 [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 -
374 / 590

[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 197: BCB-LINK: BTS A9100 Corrective Actions
375 / 590

[8,30] BCBLINK
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
Figure 198: BCB-LINK: BTS A9110/A9110-E Corrective Actions
376 / 590
9.9 [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.
377 / 590

[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 199: IOM-LINK: BTS A9100 Corrective Actions
378 / 590

[8,31] IOMLINK
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
Figure 200: IOM-LINK: BTS A9110/A9110-E Corrective Actions
379 / 590
9.10 [8,32] MODULE-INSERTED

specific Problems event Type probable Cause perceived Severity Alarm Description MODULE-INSERTED Equipment Replaceable Unit Problem Warning (MI) A TRE is inserted but not connected to any ANX/ANC via RF cable.
380 / 590

[8,32] MODULEINSERTED
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 201: MODULE-INSERTED: BTS A9100 Corrective Actions
381 / 590

[8,32] MODULEINSERTED
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
Figure 202: MODULE-INSERTED: BTS A9110/A9110-E Corrective Actions
382 / 590

specific Problems event Type probable Cause perceived Severity Alarm Description CONFIG-FAIL Processing Error Configuration Or Customization Error Major (PMA) The configuration of an EACB has failed.
383 / 590

[8,251] SELFTESTAL
Lock Function EACB
EACB operational?
yes
Alarm solved
no
Onsite
Replace EACB
EACB operational?
yes
Alarm solved
Figure 203: CONFIG-FAIL: G1 BTS Corrective Actions
384 / 590

[8,246] CONFIGFAIL
Lock Function EACB
EACB operational?
yes
Alarm solved
no
Onsite
Replace SACE/SAFE
EACB operational?
yes
Alarm solved
Figure 204: CONFIG-FAIL: G2 BTS Corrective Actions
385 / 590
9.12 [8,247] RESET

9.12.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
386 / 590
9.12.2 [8,247] RESET (EACB)

specific Problems event Type probable Cause perceived Severity Alarm Description RESET Processing Error Software Error Warning (MI) The auto-reset of the EACBs is successful. The auto-reset is triggered by the watchdog or a push-button reset.
Telecom functions are not affected Impact Loss Degradation BSS Cell(s) Signaling Calls -
387 / 590

[8,247] RESET (EACB)
Lock Function EACB
EACB operational?
yes
Alarm solved
no Onsite
Check EACB hardware
EACB operational?
yes
Alarm solved
no Onsite
Replace FQHU
EACB operational?
yes
Alarm solved
Figure 205: RESET (EACB): G1 BTS Corrective Actions
388 / 590

[8,247] RESET (EACB)
Lock Function EACB
EACB operational?
yes
Alarm solved
no Onsite
Check EACB hardware
EACB operational?
yes
Alarm solved
no Onsite
Replace STSE,STSP,STSR
EACB operational?
yes
Alarm solved
Figure 206: RESET (EACB): G2 BTS Corrective Actions
389 / 590
9.13 [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.
390 / 590

specific Problems event Type probable Cause perceived Severity Alarm Description NO-ANSWER-DCL Processing Error Underlying Resource Unavailable Major (PMA), Minor (DMA) There is a transmission problem in the Micro-BTS. Major (PMA): A configuration after power-up is not possible because the EACB is not responding to commands. Minor (DMA): There is no answer from the EACB on two polls from the OMU on the Q1 bus.
Major (PMA): During initialization units supported by this EACB are not switched properly, and therefore the telecom functions may be lost. (X). Minor (DMA): In case of Q1 malfunction, the telecom functions are not affected. In case of EACB malfunction, the result depends on the CU fault, the CU can go on with the previous configuration. If the fault is fatal, other alarms will appear on other equipment. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X
391 / 590

[8,250] NOANSWERDCL
Lock Function EACB
EACB operational?
yes
Alarm solved
no Onsite Check Q1 Bus cables to OMU and EACB/SACE
EACB operational?
yes
Alarm solved
no
Onsite
Replace EACB
EACB operational?
yes
Alarm solved
Figure 207: NO-ANSWER-DCL: G1 BTS Corrective Actions
392 / 590

[8,250] NOANSWERDCL
Lock Function EACB
EACB operational?
yes
Alarm solved
EACB operational?
yes
Alarm solved
no
Onsite
Replace SACE/SCFE
EACB operational?
yes
Alarm solved
Figure 208: NO-ANSWER-DCL: G2 BTS Corrective Actions
393 / 590
9.15 [8,251] SELF-TEST-AL

specific Problems event Type probable Cause perceived Severity Alarm Description SELF-TEST-AL Equipment Equipment Malfunction Major (PMA) This is a self-test alarm from the EACB after power-up, auto-reset, or reset command.
The units supported by this EACB are not switched properly, and therefore the telecom capabilities may be lost. Impact Loss Degradation BSS X Cell(s) X Signaling X Calls X -
394 / 590

[8,251] SELFTESTAL
Lock Function EACB
EACB operational?
yes
Alarm solved
no
Onsite
Replace EACB
EACB operational?
yes
Alarm solved
Figure 209: SELF-TEST-AL: G1 BTS Corrective Actions
395 / 590

[8,251] SELFTESTAL
Lock Function EACB
EACB operational?
yes
Alarm solved
no
Onsite
Replace SACE/SAFE
EACB operational?
yes
Alarm solved
Figure 210: SELF-TEST-AL: G2 BTS Corrective Actions
396 / 590
9.16 [8,255] Q1-RELAY-FAULT

specific Problems event Type probable Cause perceived Severity Alarm Description Q1-RELAY-FAULT Equipment Equipment Malfunction Minor (DMA) The EACB cannot disconnect from the Q1 interface due to relay problems.
397 / 590

[8,255] Q1RELAYFAULT
Lock Function EACB
EACB operational?
yes
Alarm solved
EACB operational?
yes
Alarm solved
no
Onsite
Replace EACB
EACB operational?
yes
Alarm solved
Figure 211: Q1-RELAY-FAULT: G1 BTS Corrective Actions
398 / 590

[8,255] Q1RELAYFAULT
Lock Function EACB
EACB operational?
yes
Alarm solved
EACB operational?
yes
Alarm solved
no
Onsite
Replace SACE/SCFE
EACB operational?
yes
Alarm solved
Figure 212: Q1-RELAY-FAULT: G2 BTS Corrective Actions
399 / 590
400 / 590
10 Class 9: BTS-EXTERNAL Alarms

This section defines the alarms for the Class 9: BTS-EXTERNAL alarm class.
401 / 590
10.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. G2 BTS: External alarm (e.g., door open, fire, water) detected from input port [1 ... 24]. BTS A9100/A9110/A9110-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 A9110-E, and are applicable only in this case. A9100 Outdoor BTS cabinets can handle up to 24 external alarms but 8 inputs are not realised so not usable. The remaining 16 external alarms are used as follows: 5 external alarms inputs are connected to internal sensors (external alarm number 3 to external alarm number 7) and are not configurable 3 external alarm inputs are protected (external alarms number 10, 13 and 14) and configurable 8 external alarms inputs (external alarms number 17 to 24) are free and configurable For A9100 Indoor BTS the external alarms are configurable and available as follows: 24 external alarms for CIMI/CIDI and CIMA/CIDE cabinet variants 16 external alarms for MBI cabinet variants 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#
402 / 590

[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 213: EXT-ALARM [9,1...56] : Corrective Actions
403 / 590
10.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 G2/A9100: There is a power supply rectifier failure. BTS A9110/A9110-E: There is a SSC battery deep discharge.
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 -
404 / 590
10.2.1 G2 BTS and BTS A9100 Corrective Actions

[9,1] EXTALARM
Onsite
yes
Onsite
Trigger customer specific action according to power supply rectifier alarm
Onsite
no
Alarm solved
Figure 214: [9,1] EXT-ALARM: G2 BTS and BTS A9100 Default Corrective Actions
405 / 590

[9,1] EXTALARM
Onsite
yes
Onsite
Trigger customer specific action according to power supply rectifier alarm
Onsite
no
Alarm solved
Figure 215: [9,1] EXT-ALARM: BTS A9110/A9110-E Default Corrective Actions
406 / 590

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 G2/A9100: There is a AC mains power failure. A9110/A9110-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 -
407 / 590

[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
Figure 216: [9,2] EXT-ALARM: Default Corrective Actions
408 / 590

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 G2/A9100: This is a door/window alarm. BTS A9110/A9110-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 -
409 / 590
10.4.1 BTS G2 and A9100 Corrective Actions

[9,3] EXTALARM
Onsite
yes
Onsite
Onsite
no
Alarm solved
Figure 217: [9,3] EXT-ALARM: BTS G2 and A9100 Default Corrective Actions
410 / 590

[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 218: [9,3] EXT-ALARM: BTS A9110/A9110-E Default Corrective Actions
411 / 590

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 G2/A9100: This is a door/window alarm override by the allowance key. BTS A9110: Available and not used. BTS A9110-E: This is a door alarm for the micro-BTS master, COBOX cover open.
412 / 590

[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
413 / 590

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 G2/A9100: Fire alarm by detection of smoke detector inside the cabinet. BTS A9110: Available and not used. BTS A9110-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 -
414 / 590

[9,5] EXTALARM
Onsite
yes
Onsite
Onsite
no
Alarm solved
415 / 590

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 G2/A9100: Water break-in by detection of water detection float switch. BTS A9110/A9110-E: Available and not used.
416 / 590

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

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 G2/A9100: There is a heating/ventilation/cooling system problem. At least one fan in the heat exchanger unit is faulty. BTS A9110/A9110-E: Available and not used.
418 / 590

[9,7] EXTALARM
Onsite
Onsite Onsite
G2: Replace HEAT
Onsite
A9100: Replace HEAT2 Check cabling to sensor, replace cabling if required.
OR
Onsite
Check sensor function, replace sensor if required. External alarm persists? no Alarm solved
External alarm persists?
no
Alarm solved
419 / 590

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 G2/A9100: The temperature in the equipment rack reached 35 0C. BTS A9110/A9110-E: Available and not used.
420 / 590

[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
421 / 590

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 G2/A9100: The temperature in the equipment room reached 40 0C. BTS A9110/A9110-E: Available and not used.
422 / 590

[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
423 / 590

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 G2/A9100: The antenna mast warning light is faulty. BTS A9110/A9110-E: Available and not used.
424 / 590

[9,10] EXTALARM
Onsite

Onsite
yes
Onsite
Replace antenna mast warning light
Onsite
no
Alarm solved
no
Alarm solved
425 / 590

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 G2/A9100 Indoor: The external battery (if equipped) is deep discharged while supplying the BTS. The BTS will be switched off after 30 - 60 s. BTS A9110/A9110-E: Available and not used.
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 -
426 / 590
10.12.1 G2 BTS and A9100 Corrective Actions

[9,11] EXTALARM
Onsite
Onsite
Onsite
Power supply alarm events? no Onsit e Ensure BTS AC power supply
yes
Solve power supply alarm first
no
Alarm solved
yes
Onsit e
Check battery
Onsite
Onsite
Onsite
Onsite
Onsite
Onsite
G2: Replace BBU2
OR
G2: Replace BU60
OR
A9100: Replace BU41
OR
OR
A9100: Replace BATS
OR
no
Alarm solved
427 / 590

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 G2: The BHPS temperature sensor is faulty. Thus HEAT is disabled and HEXU fans run in full speed. BTS A9110: Available and not used. BTS A9110-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 -
428 / 590

[9,12] EXTALARM
Onsite
Check BHPS sensor connection.
Onsite
Onsite
no
Alarm solved
Figure 227: [9,12] EXT-ALARM: G2 BTS Default Corrective Actions
429 / 590

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 G2/A9100: The antenna mast warning light is faulty. BTS A9110: Available and not used. BTS A9110-E: This is a PMS alarm for the micro-BTS slave1, equipment not in vertical position.
430 / 590
10.14.1 BTS G2 and A9100 Corrective Actions

[9,13] EXTALARM
Onsite

Onsite
yes
Onsite
Onsite
no
Alarm solved
no
Alarm solved
Figure 228: [9,13] EXT-ALARM: BTS G2 and A9100 Default Corrective Actions
431 / 590

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 G2/A9100: The antenna mast warning light is faulty. BTS A9110/A9110-E: Available and not used.
432 / 590

[9,14] EXTALARM
Onsite

Onsite
yes
Onsite
Onsite
no
Alarm solved
no
Alarm solved
433 / 590

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 G2/A9100: This is a door alarm. BTS A9110/A9110-E: Available and not used.
434 / 590

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

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 G2/A9100: This is a power supply inverter alarm. BTS A9110/A9110-E: Available and not used.
436 / 590

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

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 A9100: This is a fatal REK alarm on TRX1, MAB detects a VSWR problem. BTS A9110/A9110-E: Available and not used.
(#) VSWR alarm indicates a problem on the antenna output, and degradation may occur. Impact Loss Degradation BSS Cell(s) X# Signaling Calls X#
438 / 590

[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
439 / 590

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 A9100: This is a fatal REK alarm on TRX2, MAB detects a VSWR problem. BTS A9110/A9110-E: Available and not used.
440 / 590

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

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 A9100: This is a fatal REK alarm (if installed) on TRX3, MAB detects a VSWR problem. BTS A9110/A9110-E: Available and not used.
442 / 590

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

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 A9100: This is a fatal REK alarm (if installed) on TRX4, MAB detects a VSWR problem. BTS A9110: Available and not used. BTS A9110-E: This is a door alarm for the micro-BTS slave 2, COBOX cover open.
444 / 590

[9,20] EXTALARM
Onsite
Onsite Onsite
Onsite
Onsite
Check antenna
Onsite
Replace MAB of TRX4
Alarm solved
Figure 235: [9,20] EXT-ALARM: BTS A9100 Default Corrective Actions
445 / 590

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 A9100: This is a fatal REK alarm (if installed) on TRX5, MAB detects a VSWR problem. BTS A9110: Available and not used. BTS A9110-E: This is a PMS alarm for the micro-BTS slave2, equipment not in vertical position.
446 / 590

[9,21] EXTALARM
Onsite
Onsite Onsite
Onsite
Onsite
Check antenna
Onsite
Replace MAB of TRX5
Alarm solved
Figure 236: [9,21] EXT-ALARM: BTS A9100 Default Corrective Actions
447 / 590

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 A9100: This is a fatal REK alarm (if installed) on TRX6, MAB detects a VSWR problem. BTS A9110/A9110-E: Available and not used.
448 / 590

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

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 A9100 : This is a REK alarm (if installed) on LNA, at least one receive path has a LNA problem. BTS A9110/A9110-E: Available and not used.
(#) 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#
450 / 590

[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
451 / 590

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 G2/A9100: There is a heating/ventilation/cooling system problem. At least one fan in the heat exchanger unit is faulty. BTS A9110/A9110-E: Available and not used.
452 / 590

[9,7] EXTALARM
Onsite
Onsite Onsite
G2: Replace HEAT
Onsite
A9100: Replace HEAT2 Check cabling to sensor, replace cabling if required.
OR
Onsite
Check sensor function, replace sensor if required. External alarm persists? no Alarm solved
no
Alarm solved
453 / 590
10.26 [9,25] EXT-ALARM for A9110-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 A9110-E: Available and not used.

454 / 590

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 A9110-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 A9110-E: This is a door alarm for the micro-BTS slave 11, COBOX cover open.
455 / 590

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. A9110-E: This is a PMS alarm for the micro-BTS slave11, equipment not in vertical position.

456 / 590


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 A9110-E: Available and not used.
457 / 590


458 / 590


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 A9110-E: This is a door alarm for the micro-BTS slave 12, COBOX cover open.
459 / 590

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. A9110-E: This is a PMS alarm for the micro-BTS slave12, equipment not in vertical position.

460 / 590


461 / 590


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 A9110-E: Available and not used.
462 / 590


463 / 590

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. A9110-E: This is a PMS alarm for the micro-BTS slave21, equipment not in vertical position.

464 / 590


465 / 590


466 / 590


467 / 590

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. A9110-E: This is a PMS alarm for the micro-BTS slave22, equipment not in vertical position.

468 / 590


469 / 590
470 / 590
11 Class 10: RX-TX Alarms

This section defines the BTS alarms for Class 10: RX-TX alarm class.
471 / 590
11.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
472 / 590

[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 240: RSL-LINK: BTS A9100 Corrective Actions
473 / 590

[10,1] RSLLINK
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
Figure 241: RSL-LINK: G2 BTS Corrective Actions
474 / 590
11.2 [10,3] RX-CABLE

11.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.
475 / 590

[10,3] RXCABLE (TRE)
Lock Function TRE
Unlock Function TRE
ANX/ANY/ANC alarm events?
yes
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 242: RX-CABLE (TRE):Corrective Actions
476 / 590
11.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.
477 / 590

[10,3] RXCABLE (RA)
Lock Function RA
Unlock Function RA
yes
no
RA operational?
yes
Alarm solved
no
Onsite
Check RX cables to TRE and ANX/ANY/ANC visually and electrically
Onsite
Check BTS status
Onsite
Replace ANX/ANY/ANC
RA operational?
yes
Alarm solved
Figure 243: RX-CABLE (RA): Corrective Actions
478 / 590
11.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#* -
479 / 590

[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 244: TRE-VSWR: BTS A9100 Corrective Actions
480 / 590

[10,10] TREVSWR
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
Figure 245: TRE-VSWR: BTS A9110/A9110-E Corrective Actions
481 / 590
11.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 A9100 BTS): The LOW (first) threshold of antenna 1 VSWR has been exceeded. 2 (only for A9100 BTS): The LOW (first) threshold of antenna 2 VSWR has been exceeded. 3 (only for A9100 BTS): The LOW (first) thresholds on both antenna 1 and 2 have been exceeded. 4 (only for A9110-E BTS): VSWR 1 alarm for Master. 5 (only for A9110-E BTS): VSWR 2 alarm for Master. 6 (only for A9110-E BTS): VSWR 1 alarm for Slave 1. 7 (only for A9110-E BTS): VSWR 2 alarm for Slave 1. 8 (only for A9110-E BTS): VSWR 1 alarm for Slave 2. 9 (only for A9110-E BTS): VSWR 2 alarm for Slave 2. 10 (only for A9110-E BTS): VSWR 1 alarm for Slave 11. 11 (only for A9110-E BTS): VSWR 2 alarm for Slave 11. 12 (only for A9110-E BTS): VSWR 1 alarm for Slave 12. 13 (only for A9110-E BTS): VSWR 2 alarm for Slave 12. 14 (only for A9110-E BTS): VSWR 1 alarm for Slave 21. 15 (only for A9110-E BTS): VSWR 2 alarm for Slave 21. 16 (only for A9110-E BTS): VSWR 1 alarm for Slave 22. 17 (only for A9110-E BTS): VSWR 2 alarm for Slave 22.
482 / 590
Impact
BSS
Cell(s)
Signaling
Calls
Transmission quality is degraded Loss Degradation X X
483 / 590
11.4.1 Corrective Actions for A9100 BTS

Lock Function RA
Unlock Function RA
TRE alarm events?
yes
no
RA operational?
yes
Alarm solved
no
Onsite Onsite
Check BTS status
Onsite
Onsite
Onsite
RA operational?
yes
Alarm solved
Figure 246: ANTENNA-VSWR-WARNING: Corrective Actions for A9100 BTS
484 / 590
11.4.2 Corrective Actions for A9110-E BTS

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
RA operational?
yes
Alarm solved
Figure 247: ANTENNA-VSWR-WARNING: Corrective Actions for A9110-E BTS
485 / 590
11.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.
486 / 590

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 248: ANTENNA-VSWR-URGENT: Corrective Actions
487 / 590
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 249: ANTENNA-VSWR-URGENT: Corrective Actions, continued
488 / 590
On site
ANTENNAVSWRURGENT (continued)
Onsite
Check BTS status
Onsite
Onsite
Onsite
Onsite
RA operational?
yes
Alarm solved
Figure 250: 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.
489 / 590
11.6 [10,21] MODULE-FRAME-SIGNAL

11.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
490 / 590

[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 251: MODULE-FRAME-SIGNAL (TRE): BTS A9100 Corrective Actions
491 / 590

[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 252: MODULE-FRAME-SIGNAL (TRE): BTS A9110/A9110-E Corrective Actions
492 / 590
11.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
493 / 590

[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 253: MODULE-FRAME-SIGNAL (RA): Corrective Actions
494 / 590
11.7 [10,22] MODULE-CLOCK-SIGNAL

11.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#* -
495 / 590

[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 254: MODULE-CLOCK-SIGNAL (TRE): BTS A9100 Corrective Actions
496 / 590

[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 255: MODULE-CLOCK-SIGNAL (TRE): BTS A9110/A9110-E Corrective Actions
497 / 590
11.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.
498 / 590

[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 256: MODULE-CLOCK-SIGNAL: Corrective Actions
499 / 590
11.8 [10,51] MODULE-NOT-PRESENT

11.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#* -
500 / 590

[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 257: MODULE-NOT-PRESENT (TRE): BTS A9100 Corrective Actions
501 / 590

[10,51] MODULENOTPRESENT
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
Figure 258: MODULE-NOT-PRESENT (TRE): BTS A9110/A9110-E Corrective Actions
502 / 590
11.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 -
503 / 590

[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 259: MODULE-NOT-PRESENT (RA): Corrective Actions
504 / 590
11.9 [10,234] IOM-DISCONNECTION

11.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 -
505 / 590

[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 260: IOM-DISCONNECTION (TRE): BTS A9100 Corrective Actions
506 / 590

[10,234] IOMDISCONNECTION (TRE)
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
Figure 261: IOM-DISCONNECTION (TRE): BTS A9110/A9110-E Corrective Actions
507 / 590
11.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 -

508 / 590
[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 262: IOM-DISCONNECTION (RA): Corrective Actions
509 / 590
11.10 [10,237] HW-DEGRADED

11.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
510 / 590

[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 263: HW-DEGRADED (TRE): BTS A9100 Corrective Actions
511 / 590

[10,237] HWDEGRADED (TRE)
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
Figure 264: HW-DEGRADED (TRE): BTS A9110/A9110-E Corrective Actions
512 / 590
11.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 RX1. 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: RX1 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
513 / 590
11.10.2.1 BTS A9100, 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 265: HW-DEGRADED (RA): BTS A9100, Alarm Number 3 Corrective Actions
514 / 590
11.10.2.2 BTS A9100, 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 266: HW-DEGRADED (RA): BTS A9100, Alarm Number 4...11 and 13 Corrective Actions
515 / 590

[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 267: HW-DEGRADED (RA): BTS A9100, Alarm Number 3 Corrective Actions
516 / 590
11.11 [10,239] HW-FAILURE

11.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.
517 / 590
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#* -
518 / 590
11.11.1.1 BTS A9100, Alarm Number 1, 12 and 13 Corrective Actions

[10,239] HWFAILURE (TRE)
Alarm Number 1, 12 & 13
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 268: HW-FAILURE (TRE): BTS A9100, Alarm Number 1, 12 and 13 Corrective Actions
519 / 590
11.11.1.2 BTS A9100, Alarm Number 1, 3...11 and 15 Corrective Actions

Alarm Number 1, 3...11 & 15
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
yes Alarm persists?
Replace TRE
no Alarm solved yes
TRE operational?
Alarm solved
Figure 269: HW-FAILURE (TRE): BTS A9100, Alarm Number 1, 3...11 and 15 Corrective Actions
520 / 590

Alarm Number 14
Lock Function TRE
Unlock Function TRE
TRE operational?
yes
Alarm solved
no
Other related alarm events?
yes
Solve related alarm(s) first
no
TRE operational?
yes
Alarm solved
Figure 270: HW-FAILURE (TRE): BTS A9100, Alarm Number 14 Corrective Actions
521 / 590

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 271: HW-FAILURE (TRE): BTS A9110/A9110-E Corrective Actions
522 / 590
11.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 Evolium A9110 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 -
523 / 590
11.11.2.1 BTS A9100, 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 272: HW-FAILURE (RA): BTS A9100, Alarm Number 2 and 12 Corrective Actions
524 / 590

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 273: HW-FAILURE (RA): BTS A9100, Alarm Number 10 Corrective Actions
525 / 590

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 274: HW-FAILURE (RA): BTS A9100, Alarm Number 14 Corrective Actions
526 / 590

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 275: HW-FAILURE (RA): BTS A9110/A9110-E Corrective Actions
527 / 590
11.12 [10,248] RESTART

11.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 -
528 / 590

Disable RF Power Use the BTS Terminal 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 276: RESTART (TRE): BTS A9100 Corrective Actions
529 / 590

[10,248] RESTART (TRE)
Reset Function BTS
BTS operational?
yes
Alarm solved
no
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Alarm solved
Figure 277: RESTART (TRE): BTS A9110/A9110-E Corrective Actions
530 / 590
11.13 [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).
531 / 590

Disable RF Power Use the BTS Terminal 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 278: RESTART (RA): Corrective Actions
532 / 590
12 Class 11: BTS-TRANS Alarms

This section defines the BTS alarms for Class 11: BTS-TRANS alarm class.
533 / 590
12.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 -
534 / 590

[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 279: LOOP-TO-EQUIPMENT: BTS A9100 Corrective Actions
535 / 590

[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 280: LOOP-TO-EQUIPMENT: BTS A9110/A9110-E Corrective Actions
536 / 590
12.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 -
537 / 590

[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 281: LOSS-OF-INCOMING-SIGNAL: BTS A9100 Corrective Actions
538 / 590

[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 282: LOSS-OF-INCOMING-SIGNAL: BTS A9110/A9110-E Corrective Actions
539 / 590
12.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).
540 / 590

[11,66] AIS2M
yes
no Check Transmission equipment on all nodes up to BSC or end of Abis chain
Abis link is re established? no
yes
Alarm solved
Figure 283: AIS-2M: Corrective Actions
541 / 590
12.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.
542 / 590

[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 284: LOSS-OF-FRAME-ALIGNMENT: BTS A9100 Corrective Actions
543 / 590

[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 285: LOSS-OF-FRAME-ALIGNMENT: BTS A9110/A9110-E Corrective Actions
544 / 590
12.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.
545 / 590

[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 286: LOSS-OF-CRC-MULTIFRAME-ALIGNMENT: BTS A9100 Corrective Actions
546 / 590

[11,86] LOSSOFCRCMULTIFRAME ALIGNMENT
Onsite
Onsite
Onsite
Onsite
OR
Onsite
Onsite
Check transmission equipment up to next node in Abis chain
no
yes
Alarm solved
yes Alarm solved
Onsite
Replace BTS A910 Abis link is re established? no Contact System Support yes Alarm solved
Figure 287: LOSS-OF-CRC-MULTIFRAME-ALIGNMENT: BTS A9110/A9110-E Corrective Actions
547 / 590
12.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.
548 / 590

[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 288: ERROR-RATE>E-3: BTS A9100 Corrective Actions
549 / 590

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 289: ERROR-RATE>E-3: BTS A9110/A9110-E Corrective Actions
550 / 590
12.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
551 / 590

yes
no
no
yes
Alarm solved
Onsite
Onsite
Reset BTS
no
Onsite
Replace SUMP/SUMA
yes
Alarm solved
552 / 590

Onsite
Onsite
Onsite
Onsite
OR
Onsite
Onsite
yes Alarm solved
553 / 590
12.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)
554 / 590

yes
no
no
yes
Alarm solved
Onsite
Onsite
Reset BTS
no
Onsite
Replace SUMP/SUMA
yes
Alarm solved
555 / 590

Onsite
Onsite
Onsite
Onsite
OR
Onsite
Onsite
yes Alarm solved
556 / 590
12.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.
557 / 590

[11,176] REMOTE ALARMINDICATION
yes
no Check Transmission equipment on all nodes up to BSC or end of Abis chain
yes
Alarm solved
Figure 294: REMOTE-ALARM-INDICATION: Corrective Actions
558 / 590
13 BTS Alarm Additional Information

This section describes the additional information supplied by some BTS alarms.
559 / 590
13.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.
[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
[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
[7,1]
The additional information for this alarm is TLV53 coded.
560 / 590
[7,3], [7,5] to [7,8] and [7,31] to [7,35]
The additional information for these alarms are TLV53 and TLV61 coded, as shown in Table 7. Byte Number 1 10 Several TLV61s can follow Table 7: Alarms [7,3], [7,5] to [7,8] and [7,31] to [7,35] TLV Codes Coding Start of TLV53 Start of TLV61
[7,30] [7,245]
The additional information for this alarms is TLV53 coded. The additional information for this alarms is TLV35 coded, or TLV 57 and TLV 58 coded, depending on the value of Byte 2. Byte 2 Value 23 (hex) 39 (hex) Byte Numbers 1-6 1-4 5 - 10 Table 8: Alarm [7,245] TLV Codes Coding TLV35 TLV57 TLV58
[7,246] [7,248]
The additional information for these alarms is TLV35 coded. The additional information for this alarms is TLV59 and TLV61 coded, as shown in Table 9. Byte Number 1 11 Several TLV61s can follow Table 9: Alarm [7,248] TLV Codes Coding Start of TLV59 Start of TLV61
561 / 590
13.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.
13.2.1 TLV35 Coding

The TLV35 byte definitions are shown in Tthe following table. Bytes 2 1 1 2 Description Element Identifier ( = 35) Length Ack: 0, NACK: 1 NACK Reason (optional field)
NACK Reason
The NACK Reason field provides more information concerning the message rejection. When messages are received from the OMU, the FU uses the two-byte NACK Reason field as follows: The first byte defines the NACK Type, as shown in Table 10 The second byte defines the Error Number, as shown in Table 11.
NACK Type 1 2 3 4 5 6 7
Description An unknown message was received. The FU was not in a convenient substate when the message was received. Error during software downloading. Error during configuration file downloading or configuration messages sequencing error. Wrong parameter in the configuration file. Wrong parameter in the CONFIGURATION DATA message. Wrong parameter in the FUIF LINK SELECT message.
Table 10: NACK Types for TLV35
562 / 590
NACK Type 1 2 3
Error Number
Description Not relevant. Not relevant.
1 2 3 4 5 6 7 8 9 10
Record sequence number error. File header error. Record type error. Sequence error. Software checksum error. Time out error at the beginning of the SCP downloading. Block sequence number error. File length error. Record length error. Time out error from an FU entity. Record sequence number error. File header error. Record type error. Sequence error. File length error.
1 2 3 4 8
563 / 590
NACK Type 5
Error Number
Description The identity of the wrong parameter is given in brackets.
Maximum number of PAGING REQUEST messages out of range (PG_FULL). Polling period of FUIF is zero (FUISUP_PR). Time out for FUIF response is zero (FUISUP_TO). Polling period of MFP is zero (MFPSUP_PR). Time out for MFP response is zero (MFPSUP_TO). I_LAPD_MAX_RX out of range. AG_FULL out of range. I_LAPD_MAX_TX out of range. UI_LAPD_MAX_TX out of range. Wrong checking for T_MEAS. Wrong checking for T_Sync. BSI_TIMER = 0. The name of the wrong parameter is given in brackets.
2 3 4 5 6 7 8 9 10 11 12 6 1 2 3 6 4 5 6 7
Interference band value out of range (INTFBDi). Wrong order between two interference band values (INTFBDi). Channel configuration value out of range (CHCCONFi). Channel configuration value not allowed. Too many SDCCH channels (the whole set of CHCCONFi). TEI out of range. CCCH slots do not belong to an allowed distribution (i.e., TS0 only, TS0 & TS2, TS0 & TS2 & TS4, TS0 & TS2 & TS4& TS6). NETWORK_TYPE out of range. BTS ciphering capabilities cannot be supported by the FU. Wrong value for at least one of T310x_y_STOP parameter (x = 5 or 6; y = F or D). All parameters have been checked and are correct, but B_parameter cannot be changed in this state.
8 9 10
11
564 / 590
NACK Type 7
Error Number
Description The name of the wrong parameter is given in brackets.
Antenna diversity not allowed (ANTENN_DIV). Note, antenna diversity is always available in a G2 with two FU boards. All parameters have been checked and are correct, but B_parameter cannot be changed in this state.
Table 11: Error Numbers for TLV35
565 / 590
13.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 = Evolium A9100 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
566 / 590
13.2.3 TLV53 Coding

The TLV53 byte definitions are shown in the following figures.
G1, Mark I
The TLV53 byte definitions for G1, Mark l are shown in the following figure.
Element Identifier (=53) 1st Byte Element Identifier (=53) 2nd Byte
*
DMDT 2
EVAD ALAN DMDT 1
AD DMDT 0 BSI
Length (=6) HWSW FNF CDCC 1 CDCC 0 CLLK spare 9th Byte
FI ALATYP CECC
INT FUIF FHI
EXT FUCO DMDT 3
* *
bit number 7 6 5 4
3 2 1
* Not Relevant
Figure 295: G1, Mark I, TLV53 Bytes
G1, Mark II
The TLV53 byte definitions for G1, Mark ll are shown in Figure 296.
*
DMDT 2
EVAD ALAN DMDT 1
AD DMDT 0 BSI
Length (=6) HWSW FNF CDCC 1 CDCC 0 CLLK spare 9th Byte
FI ALATYP CECC
INT FUIF FHI
EXT FUCO DMDT 3
* *
bit number 7 6 5 4
3 2 1
* Not Relevant
Figure 296: G1, Mark II, TLV53 Bytes
G2, FU 2
The TLV53 byte definitions for G2, FU 2 are shown in the following figure.
567 / 590
*
0
EVAD ALAN 0
AD 0 BSI
Length (=6) HWSW FNF DMOD CDEC CLLK spare 9th Byte
FI ALATYP CECC
INT FUIF FHI
EXT FUCO 0
* *
bit number
7 6 5 4 3 2 1
* Not Relevant
Figure 297: G2, FU2, TLV53 Bytes
MOD without antenna diversity DMAD with antenna diversity
G2, FU 3
The TLV53 byte definitions for G2, FU 3 are shown in the following figure.
*
0
EVAD ALAN 0
AD 0 BSI
Length (=6) HWSW FNF 0 0
FI ALATYP 0 CLLK
INT 0 FHI
EXT FUCO 0
* *
bit number 7 spare 9th Byte 6 5 4
* Not Relevant
Figure 298: G1, FU3, TLV53 Bytes
568 / 590
Fourth and Fifth Bytes

Field Name EVAD 1 0 AD 1 0 HWSW 1 0 FNF 1 0 FI 1 0 INT 1 0 EXT 1 0 ALAN ALATYP Value
The field definitions for the fourth and fifth bytes of TLV53 are shown in the following table. Description Alarm Condition Event. Begin/End alarm. Significant only if EVAD=0 Begin. End. Hardware or Software alarm HW SW Alarm Severity Fatal. Non-fatal. Alarm Mode Failure. Incident. Internal Entities At least one internal FU entity is involved. See Table 14. No internal FU entity is involved. External entities At least one external FU entity is involved. See Table 15. No external FU entity is involved. Alarm Number (i.e., TS number for FHI link unavailability at TS number level). Alarm Type.
Table 12: Field Definitions for Fourth and Fifth Bytes of TLV53
569 / 590
Alarms
The FU alarms and alarm types for TLV53 are shown in Table 13. G1, G2 FU2/FU3 DRFU X
ALATYP 1
ALAN 0
Name of Fault Code SCP-MP-FAULT
Description of Fault Code SCP micro-processor fault, detected in operational state.
Micro-BTS X
NON-SCP-MP-FAULT Non-SCP micro-processor fault, detected in operational state. AL-LIST-ER Alarm list erased, detected in operational state. LAPD link lost. MCLU link 0 lost. MCLU link 1 lost. BSI link 0 lost. Both BSI links lost. FHI link 0 fully available uplink. FHI link 1 fully available uplink.
4 5 6 7 8 9 10 11
0 0 0 0 0 0 0 0
LAPD-LINK MCLU-LINK-1 MCLU-LINK-2 BSI-LINK-0 BOTH-BSI-LINK FHI-LNK-0-FUL-UN FHI-LNK-1-FUL-UN
X X X X X X X X
X -
FHI-LINK-0-UN-TDMA FHI link 0 unavailable at TDMA frame level. FHI-LINK-1-UN-TDMA FHI link 1 unavailable at TDMA frame level. INT-HW-FAIL NR-SCP-MP-FAULT Hardware failure. Non-recoverable SCP micro-processor fault. (FU is not in operational state.) Non-recoverable software failure. (Bad checksum.) Alarm list erased. (Detected in state other than operational.) FU rejects telecom parameters from BSC. One or more messages missing: preprocess configure, MS power control, BS power control. Irrelevant parameters. Both MCLU links failed.
12
16 17
0 0
X X
18
NR-SW-FAILURE
19
AL-LIST-ER
21
TELECOM-REJ
TELECOM-REJ (0)
1 22 0
TELECOM-REJ (1) BOTH-MCLU-LINKS
X X
X -
570 / 590
ALATYP 23 25
ALAN 0 0
Name of Fault Code BOTH-FHI-LINKS FATAL-FUB-FAULT FATAL-FUB-FAULT (0) FATAL-FUB-FAULT (1)
Description of Fault Code Both FHI links failed. Fatal FUB fault. Hardware failure detected by autotest.
G1, G2 FU2/FU3 DRFU X -
Micro-BTS X
Non-recoverable SCP micro-processor fault. (FU not in operational state.)
FATAL-FUB-FAULT (2)
Non-recoverable SCP software failure. (Checksum error detected during fault localization state, FU-RESTART sequences for SCP/DSP FU SW, or saved parameters for FU configuration.) Clock failure during initialization. FN failure during initialization. -
3 4
FATAL-FUB-FAULT (3) FATAL-FUB-FAULT (4)
X X
26
FUB-BBSI-LINK-FAULT BBSI link problem still exists after BBSI-TIMER expires. (Equivalent to G1/G2: BOTH-BSI-LINKS.) FUB-BBSI-LINK-TROUBLE BBSI link problem existed for less than BBSI-TIMER period.
27
Table 13: FU Alarms and Alarm Type for TLV53
Sixth and Seventh Bytes
If the INT bit in the fourth byte of TLV53 has a value of 1, the bits FUCO, FUIF, CECC, CDCC 0, CDCC 1, DMDT 0, DMDT 1, DMDT 2, DMDT 3, DMOD, FICE, DADE, and DEDE indicate the fault situation of the board in terms of internal entities to the FU. The definition of each bit, correlated with the FI bit in the fourth byte, is shown in the following table. Bit Value 0 and FI = 0 0 and FI = 1 1 and FI = 0 1 and FI = 1 Description The board has not detected any fault. The board is not faulty. The board has detected a fault. The board is faulty.
Table 14: Bit value description (6th and 7th byte)
571 / 590
Eighth Byte
If the EXT bit in the fourth byte of TLV53 has a value of 1, the BSI, CLLK and FHI fields indicate the fault situation in terms of external entities to the FU. The definition of each field in the eighth byte is shown in the following table. Field Name BSI 00 01 10 11 CLLK 00 01 10 11 FHI 00 01 10 11 Value Description BSIA Inputs No link is faulty. Only link 0 is faulty. Not relevant. Both links (0 & 1) are faulty. FCLU Inputs No clock links are faulty. Clock link 0 is faulty. Clock link 1 is faulty. Both clock links (0 & 1) are faulty. FU Inputs No FHI links are faulty. FHI link 0 is faulty. FHI link 1 is faulty. Both FHI links (0 & 1) are faulty.
Table 15: 8th byte description
572 / 590
13.2.4 TLV57 Coding

The TLV57 byte definitions are shown in the following table. Bytes 2 1 1 Description Element Identifier (=57) Length (=1) Error type during software downloading. See Table 17.
Table 16: TLV57 Coding
Error Type
Table 17 shows the error type. Error Type 01 02 03 04 05 06 07 08 09 0A
Description Record sequence number error. File header error. Record type error. Sequence error. Software checksum error. Time out error at the beginning of the SCP downloading. Block sequence number error. File length error. Record length error. Time out error from an FU entity.
Table 17: TLV57 Error Types
573 / 590
13.2.5 TLV58 Coding

The TLV58 byte definitions are shown in Table 18. Bytes 2 1 1 1 1 Description Element Identifier ( = 58) Length ( = 3) Software Identity. See Table 19. Board Identity. See Table 20. DSP Identity. See Table 21.
Table 18: TLV58 Coding
Software Identity
Table 19 shows the software identity. Software Identity 00 DRFU DRSCP (SCP software) 01 DRMFP (MFP software) 02 DRENC (ENC software) 03 DRDEM (DEM software) 04 DRDEC (DEC software) 05 DRTMUX (TRXMUX software) 06 DRBED (BED software) FF Table 19: TLV58 Software Identity Not identified
574 / 590
Board Identity
Board Identity 00 01 02 03 04 05 06 07 08
Table 20 shows the board identity. G1 MKII FUCO FUIF CECC CDEC CDEC DMOD/DMAD DMOD/DMAD DMAD DMAD DRFU DRFU (G1) -
Table 20: TLV58 Board Identity
Note: DSP Identity
If several boards are concerned, only the board with the shortest mnemonic is identified. Table 21 shows the DSP identity. Type G1 FU/G2 FU3 Description FUCO board: 00 - SCP 01 - MFP FUE boards: Bit i refers to DSP number i. DRFU DEM and DEC processors: Bit i refers to DSP number i. SCP, MFP, and RXP processors, and BED and TRXMUX FPGAs: DSP identification is meaningless because there is one specific software package for each processor. Table 21: TLV58 DSP Identity
575 / 590
13.2.6 TLV59 Coding

TLV59 is used for reporting FU Alarm Type 20 (G1/G2 and Micro-BTS) and for TRE, AN and TRANS&CLOCK Alarm Type for Evolium BTS. The TLV59 codes have the same definitions as TLV53, as described in Section 13.2.3., except that the ALAN and ALATYP fields each occupy a separate byte. Consequently, there are 10 bytes in TLV59 codes compared to 9 bytes for TLV53 codes. As an example, the TLV59 byte definitions for G1, Mark l are shown in Figure 299.
EVAD
AD
Length (=6) HWSW FNF ALAN ALATYP CDCC 1 CDCC 0
FI
INT
EXT
DMDT 2
DMDT 1
DMDT 0 BSI
CECC CLLK
FUIF FHI
FUCO DMDT 3
* *
bit number 7 6 5 4 spare 10th Byte
* Not Relevant
Figure 299: G1, Mark I TLV59 Bytes
576 / 590
Table 22 shows the definitions of TLV 59 FU Alarm Type 20 alarms (G1/G2 and Micro-BTS only). G1, G2 FU2/FU3 DRFU X X
ALATYP ALAN 20 0 2
Name of Fault Code REC-SW-FAIL REC-SW-FAIL (0) REC-SW-FAIL (2)
Description of Fault Code Recoverable software failure. SCP or DSP exception. FU telecom configuration failure. (Time out elapsed or algorithm configuration parameters refused during FU initialization). Other recoverable cases, such as spurious hardware problem, or hardware problem not detected by tests. TS configuration failure.
Micro-BTS X X
REC-SW-FAIL (3)
4 5 6
REC-SW-FAIL (4) REC-SW-FAIL (5) REC-SW-FAIL (6)
X X
SYS-INFO 3 parameters out of range. X G1/G2 FU, DRFU: Failure of both BSI, both FHI, or both MCLU links detected in operational or fault localization states. Micro-BTS: BBSI link fault detected in operational state. X
7 8
REC-SW-FAIL (7) REC-SW-FAIL (8)
Pushbutton reset. Failure of LAPD link for more than BCCH Cut Timer value.
X X
Table 22: TLV59 FU Alarm Type 20 Alarms for G1/G2 and Micro-BTS
577 / 590
Table 23 shows the definitions of TLV 59 for the TRE faults (Evolium 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 0 1 AD AD 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) Microprocessor failure HW failure
578 / 590
ALATYP
ALAN 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
Description of Fault Code 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 23: TLV59 for TRE faults of Evolium 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).
579 / 590
Table 24 shows the definitions of TLV 59 for the AN faults (Evolium 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 24: TLV59 for AN faults of Evolium BTS
580 / 590
Table 25 shows the definitions of TLV 59 for the TRANS&CLOCK faults (Evolium A9100 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 25: TLV59 for TRANS&CLOCK faults of Evolium A9100 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.
581 / 590
13.2.7 TLV61 Coding

The TLV61 byte definitions are shown in Table 26. 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 26: 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 definition of the Board Identification bytes for G1, G2 and Micro -BTS is shown in Table 27. A bit set to 1 identifies the board at the origin of the fault detection. G1 Bit Number 0 MARK II FUCO G2 FU 3 FUCO FU 4 FUCO Micro-BTS MBPG/MBEG MBPD/MBED MBPG/MBEG MBPD/MBED MBPG/MBEG MBPD/MBED MBPG/MBEG MBPD/MBED MBPG/MBEG MBPD/MBED MBPG/MBEG MBPD/MBED MBPG/MBEG MBPD/MBED
FUIF
FICE
DRFU
CECC
FICE
DRFU
CDEC
DEDE/DADE
DRFU
CDEC
DEDE/DADE
DRFU
DMOD/DMAD
DEDE/DADE
DRFU
DMOD/DMAD
DEDE/DADE
DRFU
582 / 590
G1 Bit Number 7 MARK II DMAD
G2 FU 3 DADE FU 4 DRFU Micro-BTS MBPG/MBEG MBPD/MBED MBPG/MBEG MBPD/MBED
DMAD
DADE
DRFU
Table 27: TLV61 Board Identification Bytes for G1/G2 and Micro-BTS * 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 Evolium BTS is shown in Table 28. A bit set to 1 identifies the board at the origin of the fault detection. TRANS&CLOCK (Evolium A9100 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 28: TLV61 Board Identification Bytes for Evolium BTS (1) The bit positions are fixed by the Host interface within the TRE.
583 / 590
13.2.8 TLV82 Coding

TLV82 provides OMU system automatic test results. The TLV82 byte definitions are shown in Table 29. 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 :
584 / 590
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 29: TLV82 Bytes
585 / 590
13.2.9 TLV83 Coding

The TLV83 byte definitions are shown in Table 30. 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 terminal. 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.
586 / 590
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 30: TLV83 Bytes
13.2.10 TLV84 Coding

The TLV84 byte definitions are shown in Table 31. 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.
587 / 590

The TLV120 byte definitions are shown in Table 32. 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 32: TLV120 Bytes
588 / 590

The TLV243 byte definitions are shown in Table 33. Bytes 2 1 1 Description Element Identifier ( = 243) Length ( = 1) BTS HW family (for the coding, see below). G1 00 01 02 10 11 12 13 14 15 G2 20 21 22 23 24 25 30 31 32 33 50 G1 MKI (not sent by BTS) G1 MKI / SU HW1 G1 MKI / SU HW2 G1 MKII (not sent by BTS) G1 MKII / max. 4 TRE / 2.20 m) G1 MKII / max. 3 + 5 TRE / 2.20 m) G1 MKII / max. 3 TRE / 2.20 m) G1 MKII / max. 2 + 5 TRE / 2.20 m) G1 Compact BTS [optionally extended with MKII] G2 Indoor (not sent by BTS) G2 Mini Indoor G2 Std / 1.25 m / Indoor G2 Std / 2.00 m / Indoor G2Optimized Sectored Site Configurator (OSSC) Indoor G2 Mini Indoor / max. 1 TRE G2 Outdoor (not sent by BTS) G2 Mini Outdoor G2 Std. / 1.20 m / Outdoor G2 OSSC Outdoor G2 Micro BTS G3 60 Evolium A9100 BTS
589 / 590
BLANK PAGE BREAK
590 / 590

Alcatel-Lucent BTS Alarm Dictionary

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Alcatel-Lucent BTS Alarm Dictionary

Enviado por

Direitos autorais:

Formatos disponíveis

Alcatel-Lucent GSM

BTS Alarm Dictionary

BTS Document Reference Guide Release B9

3BK 20925 AAAA PCZZA Ed.13

BLANK PAGE BREAK

Status Short title

RELEASED BTS Alarm Dictionary

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

Note: Whats New

3BK 20925 AAAA PCZZA Ed.13

Audience Assumed Knowledge

3BK 20925 AAAA PCZZA Ed.13

3BK 20925 AAAA PCZZA Ed.13

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 20925 AAAA PCZZA Ed.13

1.2.2 State change commands translation

1.2.3 Mapping of MO Perceived Severity to BSS Alarm Category

3BK 20925 AAAA PCZZA Ed.13

1.3 A1353-RA Alarm Surveillance Information

1.3.1 Object Identification

3BK 20925 AAAA PCZZA Ed.13

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 20925 AAAA PCZZA Ed.13

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 20925 AAAA PCZZA Ed.13

1.4.1.5 SBL States

1.4.1.6 Suspected RIT

3BK 20925 AAAA PCZZA Ed.13

1.4.1.7 Additional Information

3BK 20925 AAAA PCZZA Ed.13

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 20925 AAAA PCZZA Ed.13

1.5.2 Alarm Description