ALU BSC-TC Alarm Dictionary
-
Upload
rdmiguel19836 -
Category
Documents
-
view
82 -
download
8
description
Transcript of ALU BSC-TC Alarm Dictionary
Alcatel BSS
BSC & TC Alarm Dictionary
BSC & TC Document
Reference Guide
Release B9
3BK 20918 AAAA PCZZA Ed.06
Status RELEASED
Short title BSC & TC Alarm Dic.
All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel.
BLANK PAGE BREAK
2 / 533 3BK 20918 AAAA PCZZA Ed.06
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.2 A1353-RA AS Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.3 LMT Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.4 Alarm Information Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2 Class 32: BSC-ENVIRON Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.1 [32,0] CONV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.2 [32,1] BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3 Class 33: PROCESSOR Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.1 [33,0] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.2 [33,1] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.3 [33,3] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513.4 [33,4] RELC-OV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543.5 [33,7] TAKEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573.6 [33,9] SDCCH-OVRL-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593.7 [33,251] AUDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4 Class 34: SWITCH Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.1 [34,251] AUDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5 Class 35: N7 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675.1 [35,0] LNK-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.2 [35,2] RTE-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.3 [35,3] INC-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.4 [35,251] AUDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6 Class 36: TRUNK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776.1 [36,0] LFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786.2 [36,3] RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796.3 [36,4] AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816.4 [36,5] SLIP-OV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.5 [36,6] SLIP-UN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856.6 [36,7] LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876.7 [36,10] CRCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896.8 [36,11] CH0-EERH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916.9 [36,12] CRC4-BERH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926.10 [36,13] CRC4-BERL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936.11 [36,251] AUDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
7 Class 38: X.25 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977.1 [38,0] MODEM-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987.2 [38,1] LINK-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007.3 [38,2] PROT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1027.4 [38,251] AUDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8 Class 39: BSC-SW-ANOMALY Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8.1 [39,1] OSN-NONRECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1088.2 [39,3] OSN-PROCEDURAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1098.3 [39,4] OSN-RECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108.4 [39,5] USER-NONRECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1118.5 [39,6] USER-RECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1128.6 [39,7] HWR-NONRECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138.7 [39,18] SANITY-TIMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
9 Class 42: TELECOM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
3BK 20918 AAAA PCZZA Ed.06 3 / 533
Contents
9.1 [42,1] NACK-MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169.2 [42,2] OVERLOAD-MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1189.3 [42,3] START-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1199.4 [42,7] NO-RESET-CIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1219.5 [42,9] OVERLOAD-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1239.6 [42,12] TEL-PAIR-LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1249.7 [42,13] BSC-TRAFFIC-REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269.8 [42,14] GPRS-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
10 Class 43: CELL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
10.1 [43,0] LOSS-OF-BCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13010.2 [43,1] LOSS-OF-SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13210.3 [43,2] LOSS-OF-TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13410.4 [43,3] LOSS-OF-ALL-CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13610.5 [43,4] CELL-TRAFFIC-REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13810.6 [43,5] OVERLOAD-BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14010.7 [43,248] CONFIGURED POOLS NOT [FULLY] USABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
11 Class 44: BTS-OM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14511.1 [44,0] AUDIT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14611.2 [44,1] PROTOCOL-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14811.3 [44,2] RECONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14911.4 [44,3] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15111.5 [44,5] SW-ACTIVATE-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15311.6 [44,6] CONFIG-DATA-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15511.7 [44,7] OMU-SELFTEST-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15711.8 [44,10] ABORT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15911.9 [44,11] PRELOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16011.10 [44,12] BTS-HW-CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
12 Class 45: CHANNEL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16312.1 [45,0] CH-UNBLOCK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16412.2 [45,1] CH-BLOCK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16612.3 [45,2] BSC-CIC-UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16812.4 [45,3] MSC-CIC-UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17012.5 [45,4] END-OF-REP-OF-UBLOCK-PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17212.6 [45,251] AUDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
13 Class 46: BACKUP-MEDIUM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
13.1 [46,0] SYNC-CORRUPTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17613.2 [46,1] UNSYNC-OTHER-CORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17713.3 [46,4] SECFILE-ROLLBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17913.4 [46,5] SINGLE-UPD-ROLLBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18113.5 [46,6] DUT-ROLLBACK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18313.6 [46,7] DISC-OOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18513.7 [46,8] DISC-PARITY-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
14 Class 47: GLOBAL-BSC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18914.1 [47,1] SCCP-NOT-AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19014.2 [47,2] AUTO-BSC-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19214.3 [47,3] AUTO-BSC-RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19314.4 [47,4] BSC-SYNC-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19414.5 [47,5] BTS-SYNC-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19514.6 [47,6] AUDIT-COMPLETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19614.7 [47,7] BSC-HW-RESYNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19714.8 [47,8] AIFL-FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19814.9 [47,9] CBC-CONNECTION-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19914.10 [47,11] ABIS-TS-ALLOC-FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20114.11 [47,12] INSUFFICIENT-TCU-RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20214.12 [47,13] TRE-SECTOR-MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
4 / 533 3BK 20918 AAAA PCZZA Ed.06
Contents
14.13 [47,14] TCU TOO FRAGMENTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20514.14 [47,15] SWRPL-IN-PROGRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20614.15 [47,16] MAX-TRE-EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
15 Class 48: TR-OM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21115.1 [48,0] AUDIT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21215.2 [48,1] PROTOCOL-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
16 Class 49: ALERTOR Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
16.1 [49,0] TRAFF-SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21616.2 [49,1] CH-INCONSIST-SUSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21816.3 [49,2] TCH-BLOCK-SUSPECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22016.4 [49,3] TCH-OCCUP-SHORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
17 Class 50: BSC-EXTERNAL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22317.1 [50,1] EXT-ALARM-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22417.2 [50,2] EXT-ALARM-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22617.3 [50,3] EXT-ALARM-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22817.4 [50,4] EXT-ALARM-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23017.5 [50,5] EXT-ALARM-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23217.6 [50,6] EXT-ALARM-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23417.7 [50,7] EXT-ALARM-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23617.8 [50,8] EXT-ALARM-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23817.9 [50,9] EXT-ALARM-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24017.10 [50,10] EXT-ALARM-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
18 Class 51: SWITCH-G2 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24518.1 [51,0] TRANSIENT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24618.2 [51,1] SWITCH-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24718.3 [51,2] ROUTINE-TEST-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
19 Class 52: BSC-Clock Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25319.1 [52,0] LOSS-OF-SEL-CLK-INP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25419.2 [52,1] LOSS-OF-CLK-GEN-FN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25619.3 [52,2] SWITCH-TO-LOCAL-CLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25819.4 [52,3] LOSS-OF-SYSTEM-CLOCK-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26019.5 [52,4] LOSS-OF-SYSTEM-CLOCK-B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26119.6 [52,5] LOSS-OF-CLK-DISTR-FN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26219.7 [52,6] BSC-RUN-ON-LOCAL-CLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26419.8 [52,7] LOC-CLK-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
20 Class 53: Broadcast-Bus Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26720.1 [53,0] LOSS-OF-ONE-BROAD-BUS-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26820.2 [53,1] LOSS-OF-BOTH-BROAD-BUS-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26920.3 [53,2] DMA-PROBLEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27020.4 [53,3] LOSS-OF-ONE-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27220.5 [53,4] LOSS-OF-BOTH-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27320.6 [53,5] DEGRAD-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27420.7 [53,6] LOSS-OF-ONE-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27520.8 [53,7] LOSS-OF-BOTH-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27620.9 [53,8] DEGRAD-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
21 Class 54: BTS-EXTRA-TS-POOL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
21.1 [54,1] EXTRA TS NOT FULLY USABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
22 Class 66: TSC-TRUNK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28322.1 [66,21] LOOP-TO-ITF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28422.2 [66,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28522.3 [66,50] TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28622.4 [66,66] AIS-2-MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28822.5 [66,81] FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
3BK 20918 AAAA PCZZA Ed.06 5 / 533
Contents
22.6 [66,86] CRC-MFRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29222.7 [66,99] BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29422.8 [66,100] BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29622.9 [66,102] BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29822.10 [66,176] FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30022.11 [66,208] I1I2-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30222.12 [66,210] TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30422.13 [66,211] LOSS-OF-CLOCK-2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
23 Class 67: TSC-CHANNEL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
23.1 [67,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31023.2 [67,65] AIS-64-KB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31123.3 [67,72] AIS-16-KB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31323.4 [67,122] TRAU-SYNCHRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31523.5 [67,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31723.6 [67,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31923.7 [67,131] INT-BUS-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
24 Class 70: TSC-SW-ANOMALY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32324.1 [70,219] SW-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
25 Class 71: TSC-ENVIRON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32725.1 [71,0] POWER-SUPPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
26 Class 73:BSC-ADAPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33126.1 [73,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33226.2 [73,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33326.3 [73,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33526.4 [73,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33726.5 [73,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33826.6 [73,203] LOSS-OF-ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34026.7 [73,212] LOSS-OF-CLK-8M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34226.8 [73,213] LOSS-OF-CLK-BOTH-8M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34426.9 [73,216] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34626.10 [73,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34726.11 [73,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34826.12 [73,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
27 Class 74: BTS-ADAPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35127.1 [74,20] BLOCKED-FROM-USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35227.2 [74,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35427.3 [74,23] TESTMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35527.4 [74,122] SYNCHRO-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35627.5 [74,124] SYNC-AL-CLOCKR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35827.6 [74,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36027.7 [74,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36227.8 [74,139] MISSING-UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36427.9 [74,141] FORCED-CNTRL-ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36627.10 [74,142] INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36727.11 [74,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36927.12 [74,159] DIAG-TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37027.13 [74,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37127.14 [74,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37327.15 [74,245] LOCAL-REINIT-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37527.16 [74,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37727.17 [74,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
28 Class 75: TCSM-ADAPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38128.1 [75,20] BLOCKED-FROM-USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38228.2 [75,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
6 / 533 3BK 20918 AAAA PCZZA Ed.06
Contents
28.3 [75,112] FAN-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38528.4 [75,122] SYNCHRO-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38628.5 [75,124] SYNCHRO-AL-CLOCKR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38828.6 [75,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39028.7 [75,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39228.8 [75,136] FIRST-DSP-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39428.9 [75,139] MISSING-UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39628.10 [75,141] FORCED-CNTRL-ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39828.11 [75,142] INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40028.12 [75,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40228.13 [75,159] DIAG-TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40328.14 [75,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40428.15 [75,208] TRIB-TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40628.16 [75,209] INT-BUS-FLT-G25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40828.17 [75,210] ATER-TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41028.18 [75,211] LOSS-OF-CLOCK-2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41228.19 [75,216] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41428.20 [75,221] TRIB-TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41528.21 [75,222] TRIB-AIS-2MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41728.22 [75,223] TRIB-FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41828.23 [75,224] TRIB-CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42028.24 [75,225] TRIB-BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42128.25 [75,226] TRIB-BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42328.26 [75,227] TRIB-BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42528.27 [75,228] TRIB-FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42728.28 [75,231] ATER-TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42928.29 [75,232] ATER-AIS-2MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43128.30 [75,233] ATER-FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43328.31 [75,234] ATER-CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43528.32 [75,235] ATER-BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43728.33 [75,236] ATER-BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43928.34 [75,237] ATER-BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44128.35 [75,238] ATER-FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44328.36 [75,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44528.37 [75,245] LOCAL-REINIT-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44728.38 [75,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44928.39 [75,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
29 BSC/TC Alarm Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
29.1 Restart and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45429.2 Reset and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47029.3 System Support Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47129.4 Other BSC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47129.5 TC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
30 Consequences of an SBL State Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
3BK 20918 AAAA PCZZA Ed.06 7 / 533
Figures
FiguresFigure 1: Graphical Flowchart for Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 2: CONV: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 3: BAT: A9120 BSC Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 4: ACCESS-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 5: RELC-OVL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 6: TAKEOVER: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 7: SDCCH-OVRL-BSC: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 8: AUDIT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 9: AUDIT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 10: LNK-REP: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 11: RTE-REP: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 12: INC-REP: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 13: AUDIT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 14: LFA: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 15: RAI: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 16: AIS: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 17: SLIP-OV: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 18: SLIP-UN: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 19: LOS: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 20: CRCA: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 21: CH0-EERH: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 22: CRC4-BERH: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 23: AUDIT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Figure 24: MODEM-FLT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 25: LINK-FLT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Figure 26: PROT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 27: AUDIT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 28: NACK-MSC: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Figure 29: START-RESET: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 30: NO-RESET-CIC: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Figure 31: OVERLOAD-BSC: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Figure 32: TEL-PAIR-LOST: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 33: BSC-TRAFFIC-REPORT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 34: LOSS-OF-BCCH: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Figure 35: LOSS-OF-SDCCH: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 36: LOSS-OF-TCH: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Figure 37: LOSS-OF-ALL-CHAN: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Figure 38: CELL-TRAFFIC-REPORT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 39: OVERLOAD-BTS: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
8 / 533 3BK 20918 AAAA PCZZA Ed.06
Figures
Figure 40: CONFIGURED POOLS NOT [FULLY] USABLE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . 143
Figure 41: AUDIT-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Figure 42: PROTOCOL-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 43: RECONFIG-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Figure 44: DOWNLOAD-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Figure 45: SW-ACTIVATE-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 46: CONFIG-DATA-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 47: OMU-SELFTEST-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Figure 48: ABORT-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Figure 49: PRELOAD-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Figure 50: BTS-HW-CONFIG-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 51: CH-UNBLOCK-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Figure 52: CH-BLOCK-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Figure 53: BSC-CIC-UNKNOWN: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 54: MSC-CIC-UNKNOWN: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Figure 55: END-OF-REP-OF-UBLOCK-PROC: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Figure 56: AUDIT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Figure 57: UNSYNC-OTHER-CORR: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Figure 58: SECFILE-ROLLBACK: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Figure 59: SINGLE-UPD-ROLLBACK: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Figure 60: DUT-ROLLBACK-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Figure 61: DISC-OOS: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Figure 62: DISC-PARITY-ERROR: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Figure 63: SCCP-NOT-AVAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Figure 64: AIFL-FULL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Figure 65: CBC-CONNECTION-FAILURE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Figure 66: ABIS-TS-ALLOC-FAILED: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Figure 67: INSUFFICIENT-TCU-RES: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Figure 68: TRE-SECTOR-MISMATCH: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Figure 69: TCU-DEFRAGMENTED: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Figure 70: SWRPL-IN-PROGRESS: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Figure 71: MAX-TRE-EXCEEDED: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Figure 72: AUDIT-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Figure 73: PROTOCOL-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Figure 74: TRAFF-SDCCH: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Figure 75: CH-INCONSIST-SUSP: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Figure 76: TCH-BLOCK-SUSPECT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Figure 77: TCH-OCCUP-SHORT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Figure 78: EXT-ALARM-1: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Figure 79: EXT-ALARM-2: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
3BK 20918 AAAA PCZZA Ed.06 9 / 533
Figures
Figure 80: EXT-ALARM-3: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Figure 81: EXT-ALARM-4: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Figure 82: EXT-ALARM-5: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Figure 83: EXT-ALARM-6: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Figure 84: EXT-ALARM-7: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Figure 85: EXT-ALARM-8: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Figure 86: EXT-ALARM-9: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Figure 87: EXT-ALARM-10: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Figure 88: TRANSIENT-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Figure 89: SWITCH-FAIL: Corrective Actions for Write Violation Overflow, Loss of Sync Overflow and Init FailAlarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Figure 90: SWITCH-FAIL: Corrective Actions for Loss of Sync Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Figure 91: SWITCH-FAIL: Corrective Actions for HW Fault Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Figure 92: ROUTINE-TEST-REP: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Figure 93: LOSS-OF-SEL-CLK-INP: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Figure 94: LOSS-OF-CLK-GEN-FN: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Figure 95: SWITCH-TO-LOCAL-CLK: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Figure 96: LOSS-OF-SYSTEM-CLOCK-A: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Figure 97: LOSS-OF-SYSTEM-CLOCK-B: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Figure 98: LOSS-OF-CLK-DISTR-FN: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Figure 99: BSC-RUN-ON-LOCAL-CLK: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Figure 100: LOC-CLK-FAILURE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Figure 101: LOSS-OF-ONE-BROAD-BUS-BSC: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Figure 102: LOSS-OF-BOTH-BROAD-BUS-BSC: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Figure 103: DMA-PROBLEM (CPR/DTC/TCU): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Figure 104: LOSS-OF-ONE-BROAD-BUS-RACK: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Figure 105: LOSS-OF-BOTH-BROAD-BUS-RACK: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Figure 106: DEGRAD-BROAD-BUS-RACK: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Figure 107: LOSS-OF-ONE-BROAD-BUS-CE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Figure 108: LOSS-OF-BOTH-BROAD-BUS-CE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Figure 109: DEGRAD-BROAD-BUS-CE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Figure 110: EXTRA TS NOT FULLY USABLE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Figure 111: LOOP-TO-ITF: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Figure 112: LOOP-TO-EQUIP: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Figure 113: TWO-MB-MISSING: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Figure 114: AIS-2-MB: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Figure 115: FRAME-ALIGNMENT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Figure 116: CRC-MFRAME-ALIGNMENT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Figure 117: BER-10E-3: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Figure 118: BER-10E-4: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Figure 119: BER-10E-6: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
10 / 533 3BK 20918 AAAA PCZZA Ed.06
Figures
Figure 120: FAR-END-ALARM: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Figure 121: I1I2-AIS: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Figure 122: TRANS-FLT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Figure 123: LOSS-OF-CLOCK-2M: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Figure 124: LOOP-TO-EQUIP: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Figure 125: AIS-64-KB: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Figure 126: AIS-16-KB: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Figure 127: TRAU-SYNCHRO: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Figure 128: EQUIPMENT-FAULT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Figure 129: MEMORY-FAULT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Figure 130: INT-BUS-FAULT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Figure 131: SW-FAULT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Figure 132: POWER-SUPPLY: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Figure 133: LOOP-TO-EQUIP: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Figure 134: EQUIPMENT-FAULT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Figure 135: MEMORY-FAULT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Figure 136: NO-Q1-CONN: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Figure 137: LOSS-OF-ACT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Figure 138: LOSS-OF-CLK-8M: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Figure 139: LOSS-OF-CLK-BOTH-8M: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Figure 140: SET-PROD-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Figure 141: DOWNLOAD-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Figure 142: ACCESS-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Figure 143: BLOCKED-FROM-USE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Figure 144: LOOP-TO-EQUIP: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Figure 145: SYNCHRO-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Figure 146: SYNC-AL-CLOCKR: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Figure 147: EQUIPMENT-FAULT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Figure 148: MEMORY-FAULT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Figure 149: MISSING-UNIT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Figure 150: FORCED-CNTRL-ON: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Figure 151: INSTALLATION: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Figure 152: NO-Q1-CONN: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Figure 153: SET-PROD-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Figure 154: LOCAL-REINIT-REQ: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Figure 155: DOWNLOAD-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Figure 156: ACCESS-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Figure 157: BLOCKED-FROM-USE: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Figure 158: LOOP-TO-EQUIP: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Figure 159: FAN-ALARM: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
3BK 20918 AAAA PCZZA Ed.06 11 / 533
Figures
Figure 160: SYNCHRO-AL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Figure 161: SYNCHRO-AL-CLOCKR: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Figure 162: EQUIPMENT-FAUL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Figure 163: MEMORY-FAULT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Figure 164: FIRST-DSP-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Figure 165: MISSING-UNIT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Figure 166: FORCED-CNTRL-ON: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Figure 167: INSTALLATION: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Figure 168: NO-Q1-CONN: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Figure 169: TRIB-TRANS-FLT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Figure 170: INT-BUS-FLT-G25: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Figure 171: ATER-TRANS-FLT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Figure 172: LOSS-OF-CLOCK-2M: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Figure 173: TRIB-TWO-MB-MISSING: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Figure 174: TRIB-AIS-2MB: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Figure 175: TRIB-FRAME-ALIGNMENT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Figure 176: TRIB-CRC-MFRAME-ALGN: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Figure 177: TRIB-BER-10E-3: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Figure 178: TRIB-BER-10E-4: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Figure 179: TRIB-BER-10E-6: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Figure 180: TRIB-FAR-END-ALARM: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Figure 181: ATER-TWO-MB-MISSING: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Figure 182: ATER-AIS-2MB: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Figure 183: ATER-FRAME-ALIGNMENT: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Figure 184: ATER-CRC-MFRAME-ALGN: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Figure 185: ATER-BER-10E-3: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Figure 186: ATER-BER-10E-4: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Figure 187: ATER-BER-10E-6: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Figure 188: ATER-FAR-END-ALARM: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Figure 189: SET-PROD-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Figure 190: LOCAL-REINIT-REQ: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Figure 191: DOWNLOAD-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Figure 192: ACCESS-FAIL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
12 / 533 3BK 20918 AAAA PCZZA Ed.06
Tables
TablesTable 1: Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 2: Alarm Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 3: Alarm Definition: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 4: Mapping of MO Perceived Severity to LMT Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 5: NE Hardware Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Table 6: NE Hardware RIT Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Table 7: Additional Information for Restart and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Table 8: FMM-IDs in Bytes 4 and 5 for Restart Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Table 9: Error Types in Bytes 10 and 11 for Restart Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Table 10: Additional Information for Reset and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Table 11: System Support Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Table 12: Additional Information for Alarm [33,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Table 13: Additional Information for Alarms [34,0] to [34,2] and [34,4] to [34,6] . . . . . . . . . . . . . . . . . . . . . . . . 471
Table 14: Additional Information for Alarm [34,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Table 15: Test Segment Results for Alarm [34,3], [51,1] (Byte 0) and [51,2] (One Byte Only) . . . . . . . . . . . 474
Table 16: Test Fault Type for Alarm [34,3], [51,1] (Byte 1) and [51,2] (One Byte Only) . . . . . . . . . . . . . . . . . 478
Table 17: TDM Connection Test Results (Bytes 6 to 21) for Alarm [34,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Table 18: Additional Information for Alarm [34,7] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Table 19: Additional Information for Alarm [35,0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Table 20: Additional Information for Alarm [35,2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Table 21: Additional Information for Alarm [35,3], Layout 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Table 22: Additional Information for Alarm [35,3], Layout 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Table 23: Example of Additional Information for Alarm [35,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Table 24: Additional Information for Alarm [35,4] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Table 25: Additional Information for Alarm [36,14] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Table 26: Additional Information for Alarm [36,15] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Table 27: Additional Information for Alarm [38,0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Table 28: Additional Information for Alarm [38,2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Table 29: Additional information for Alarm [42,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Table 30: Additional Information for Alarm [42,5] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Table 31: Additional Information for Alarm [42,6] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Table 32: Additional Information for Alarm [42,9] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Table 33: Additional Information for Alarm [42,12] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Table 34: Additional Information for Alarm [42,13] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Table 35: Additional Information for Alarms [43,0] to [43,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Table 36: Additional Information for Alarm [43,4] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Table 37: Additional Information for Alarms [44,0], [44,5] and [44,6] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Table 38: Additional Information for Alarm [44,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Table 39: Additional Information for Alarms [46, 0], [46,1] and [46,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
3BK 20918 AAAA PCZZA Ed.06 13 / 533
Tables
Table 40: Additional Information for Alarm [47,9] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Table 41: Additional Information for Alarm [49,0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Table 42: Additional Information for Alarm [49,1] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Table 43: Additional Information for Alarms [49,2] and [49,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Table 44: Additional Information for Alarm [51,0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Table 45: Additional Information for Alarm [51,1] - First Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Table 46: Additional Information for Alarm [51,1] - Subsequent Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Table 47: TDM Test Result Byte Descriptions for Alarm [51,1] and [51,2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Table 48: Detailed TDM Test Results for Alarm [51,1] and [51,2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Table 49: Additional Information for Alarm [51,2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Table 50: Example for an Unsuccessful Test Results Format for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Table 51: Relationship IAD/NA to RIT and Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Table 52: Additional Information for Alarm [51,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Table 53: Additional Information for Alarms [52,1], [52,5] and [52,7] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Table 54: Additional Information for Alarms [53,0], [53,1], [53,3], [53,4], [53,6] and [53,7] . . . . . . . . . . . . . . 514
Table 55: Additional Information for Alarm [53,2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Table 56: Additional Information for Alarms [53,5] and [53,8] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Table 57: Additional Information for Alarm [70,219] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Table 58: Additional Information for Alarm [73,022] to [73,216] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Table 59: Additional Information for Alarm [74,20] to [74,202] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Table 60: Additional Information for Alarm [75,20] to [75,417] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Table 61: MT120 Board &Mdash; Equipment Reset/Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Table 62: MT120 Board, Range >80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Table 63: MT120 Board, Error Types, Range <80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Table 64: MT120 board, Error Types, Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
14 / 533 3BK 20918 AAAA PCZZA Ed.06
Preface
Preface
Purpose The purpose of the alarm dictionary is to provide the operator with a structuredmethod for handling alarm messages generated by the BSC and the TC.
This document contains a list of all BSC and TC alarms, and the actionsrequired to nullify them.
Alarms are displayed at the OMC-R terminal and at the LMT to inform theoperator of system faults.
Note: 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.
What’s New In Edition 06Description improvement for alarms
[33,3] ACCESS-FAIL (Section 3.3)
[33,4] RELC-OV (Section 3.4)
[33,9] SDCCH-OVRL-BSC (Section 3.6)
[52,2] SWITCH-TO-LOCAL-CLK (Section 19.3)
[52,6] BSC-RUN-ON-LOCAL-CLK (Section 19.7)
[67,65] AIS-64-KB (Section 23.2)
[67,72] AIS-16-KB (Section 23.3)
[67,122] TRAU-SYNCHRO (Section 23.4).
In Edition 05Description improvement for alarm [46,7] DISC-OOS (Section 13.6).
In Edition 04Description improvement for alarm [47,14] TCU TOO FRAGMENTED (Section14.13).
In Edition 03
3BK 20918 AAAA PCZZA Ed.06 15 / 533
Preface
Description improvement for alarms [47,11] ABIS-TS-ALLOC-FAILED (Section14.10) and [47,12] INSUFFICIENT-TCU-RES (Section 14.11).
In Edition 02Alarm [43,248] CONFIGURED POOLS NOT [FULLY] USABLE (Section 10.7)was added.Description improvement for [43,2] LOSS-OF-TCH (Section 10.3).Description improvement for alarms of class 49:
[49,0] TRAFF-SDCCH (Section 16.1)
[49,1] CH-INCONSIST-SUSP (Section 16.2)
[49,2] TCH-BLOCK-SUSPECT (Section 16.3)
[49,3] TCH-OCCUP-SHORT (Section 16.4)The following alarms were updated for commercial usage:
[43,0] LOSS-OF-BCCH (Section 10.1)
[43,1] LOSS-OF-SDCCH (Section 10.2)
[43,2] LOSS-OF-TCH (Section 10.3)
[43,3] LOSS-OF-ALL-CHAN (Section 10.4)
[52,0] LOSS-OF-SEL-CLK-INP (Section 19.1)
[52,1] LOSS-OF-CLK-GEN-FN (Section 19.2)
[52,3] LOSS-OF-SYSTEM-CLOCK-A (Section 19.4)
[52,4] LOSS-OF-SYSTEM-CLOCK-B (Section 19.5)
[52,5] LOSS-OF-CLK-DISTR-FN (Section 19.6)
[53,0] LOSS-OF-ONE-BROAD-BUS-BSC (Section 20.1)
[53,1] LOSS-OF-BOTH-BROAD-BUS-BSC (Section 20.2)
[53,3] LOSS-OF-ONE-BROAD-BUS-RACK (Section 20.4)
[53,4] LOSS-OF-BOTH-BROAD-BUS-RACK (Section 20.5)
[53,6] LOSS-OF-ONE-BROAD-BUS-CE (Section 20.7)
[53,7] LOSS-OF-BOTH-BROAD-BUS-CE (Section 20.8)
[66,211] LOSS-OF-CLOCK-2M (Section 22.13)
[73,203] LOSS-OF-ACT (Section 26.6)
[73,212] LOSS-OF-CLK-8M (Section 26.7)
[73,213] LOSS-OF-CLK-BOTH-8M (Section 26.8)
[75,211] LOSS-OF-CLOCK-2M (Section 28.18)Description improvement for alarms:
[53,0] LOSS-OF-ONE-BROAD-BUS-BSC (Section 20.1)
[53,1] LOSS-OF-BOTH-BROAD-BUS-BSC (Section 20.2)
[53,2] DMA-PROBLEM (Section 20.3)
[53,3] LOSS-OF-ONE-BROAD-BUS-RACK (Section 20.4)
16 / 533 3BK 20918 AAAA PCZZA Ed.06
Preface
[53,4] LOSS-OF-BOTH-BROAD-BUS-RACK (Section 20.5)
[52,5] LOSS-OF-CLK-DISTR-FN (Section 19.6)
[53,6] LOSS-OF-ONE-BROAD-BUS-CE (Section 20.7)
[53,7] LOSS-OF-BOTH-BROAD-BUS-CE (Section 20.8)
[53,8] DEGRAD-BROAD-BUS-CE (Section 20.9)
Consequences of an SBL State Change (Section 30)
[35,2] RTE-REP (Section 5.2)
[43,2] LOSS-OF-TCH (Section 10.3)Description improvement for alarms:
[35,0] LNK-REP (Section 5.1)
[35,2] RTE-REP (Section 5.2)
[35,3] INC-REP (Section 5.3)
[42,13] BSC-TRAFFIC-REPORT (Section 9.7) .
In Edition 01For dinamic Abis feature the new alarm [54,1] Extra-ts-not-fully-usable is raisedinstead of alarm [43,248] Configured-pools-not[fully]-usable.The alarm [51,3] ”global-routine-test-rep” is removed because it will not besent to OMC any more, from B9.
Audience This document is aimed at telecommunications operators responsible forperforming O&M; fault handling and troubleshooting tasks.
3BK 20918 AAAA PCZZA Ed.06 17 / 533
Preface
Assumed Knowledge The operator must be familiar with the following:
Alcatel O&M; concepts for the BSS
MO scenario
Fault management
Use of OMC-R and BSC terminals
SBL hierarchies of the BTS, BSC and TC
Telecommunications techniques including line transmission and switching.
18 / 533 3BK 20918 AAAA PCZZA Ed.06
1 Introduction
1 Introduction
This section describes the structure of alarm messages.
3BK 20918 AAAA PCZZA Ed.06 19 / 533
1 Introduction
1.1 OverviewThis alarm dictionary provides additional information that is not displayed in thealarm messages sent to the OMC-R, BSC or TC terminals.
The dictionary contains alarm definitions for each alarm type produced bythe BSS.
Each definition describes the:
Alarm definition
Alarm description
Impact on System
Methods for further fault isolation
Corrective actions.
1.2 A1353-RA AS Alarm InformationIn the A1353-RA OMC-R, Alarm Surveillance provides an efficient means tocontrol, supervise and manage equipment problems in the BSS.
Alarms or Alarm notifications consist of messages sent by network resourcesthat have detected problems or failures in the network. These alarms aredisplayed in lists while alarm counters keep track of statistics. By clicking on analarm in the list, the operator gets detailed information. AS displays informationas described below.
1.2.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 alsoshows the board’s location by rack, shelf and slot.
20 / 533 3BK 20918 AAAA PCZZA Ed.06
1 Introduction
1.2.2 Alarm Type
The Alarm Type identifies the type of problem the alarm refers to.
This information is sub-divided into:
eventType. Table 1 describes the five eventTypes.
probableCause
perceivedSeverity: gives the severity level of the alarm. Table 2 describesthe severity levels.
eventType Indicates...
Communication a problem with a procedure or process used to convey information fromone point to another in the network.
Quality of Service degradation in the quality of service in the network.
Processing Error a software or processing fault.
Equipment an equipment fault.
Environmental a problem in the enclosure containing the equipment.
Table 1: Event Types
Severity Level Indicates...
Critical a serious fault condition which requires immediate correction. Example: amanaged object goes out of service.
Major a fault condition which requires urgent corrective action. Example: severedegradation in the operation of a managed object.
Minor a fault condition which does not affect service but corrective action shouldbe taken to avoid a more serious fault.
Warning detection of a potential fault condition. Action should be taken to diagnoseand correct the problem to avoid a more serious fault condition.
Indeterminate the severity level cannot be defined by the resource which raised the alarm.
Cleared the alarm was cleared by the resource which raised the alarm.
Table 2: Alarm Severity Levels
In addition to the Object Identification and Alarm Type information, all alarmsalways give the date and time of the alarm. An alarm may also contain optionalinformation, such as the notification id. Refer to the AS on-line help for moredetailed information on AS.
3BK 20918 AAAA PCZZA Ed.06 21 / 533
1 Introduction
1.3 LMT Alarm MessagesThe format of Alarms displayed at a LMT differs from that in the OMC -R.
Depending on the type of alarm and where it is viewed, an alarm messagecontains all or most of the parameters listed in this section.
1.3.1 Message Identity
The identity number given to the alarm message stored in the OMC-R database.
1.3.2 Event Time
The time the message was issued at its source or received at the OMC-R.
1.3.3 Location
The origin of the alarm, consisting of:
Network element - the BSS identity
Unit type:
bts
bsc
tcsm
bie
tsc
bss.
Unit number:
0 or 1 for a tcsm
0 to 40 for a bie
1 for a bsc, tsc or bss
1 to 40 for a bts.
SBL type
SBL number and subnumber, if appropriate. For example, RTS (3, 4) is RTSnumber 4 of FU3 (the parent SBL).
22 / 533 3BK 20918 AAAA PCZZA Ed.06
1 Introduction
1.3.4 Classification
The characteristics of the alarm, consisting of:
Alarm Class name and number - as shown in the Contents list of the
Alarm Dictionary
Alarm Type name and number - as shown in the Contents list of the Alarm
Dictionary
Alarm Number - dependent on the Alarm Class and Type. See theappropriate 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 theSBL are on
event - occurrence of anomaly. No action is required unless it occurs
frequently. Event alarms are of short duration and the affected SBLdoes not change state. The system retry/recovery mechanism has
cleared the fault.
If a fatal alarm occurs and the affected SBL changes state to FOS, the systemisolates the faulty equipment if it cannot be initialized. After a repair action, theoperator normally initializes the equipment.
If a fatal alarm occurs and the affected SBL changes state to FLT, the systemresets the faulty equipment. When the alarm ceases, the system automaticallyinitializes the equipment.
If a non-fatal alarm or event occurs, the affected SBL’s are put into the FIT state.In the worst situation, the equipment operates in a degraded mode.
3BK 20918 AAAA PCZZA Ed.06 23 / 533
1 Introduction
1.3.5 SBL States
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 Operations & Maintenance Principles for a description of the states.
1.3.6 RIT List
The information for the suspected RIT(s) is displayed if the system is able todetermine the location of the fault.
The information consists of:
Unit type - bts, bsc, tscm, bie, tsc or bss
Unit number -
0 or 1 for a tcsm
0 to 40 for a bie
1 for a bsc, tsc or bss
1 to 40 for a bts.
Physical location - the position of the RIT board within the cabinet. For
example, [A, 4, 21] indicates the board in slot 21 of rack 4 of cabinet A.For BSC and BTS equipment, the cabinets are identified as 1, 2, 3, etc.
instead of A, B, C, etc.
RIT type - the name of the RIT board.
If more than one RIT is shown in the list, the RIT most likely to be causing thefault is indicated. Replace this RIT first and initialize it. If the fault persists,replace another RIT from the list and initialize it.
24 / 533 3BK 20918 AAAA PCZZA Ed.06
1 Introduction
1.4 Alarm Information FormatEach alarm definition and description in the dictionary is structured as follows:
1.4.1 Alarm Definition
MO format LMT format
Banner Banner
specificProblems Alarm Class & [number] - Alarm Type & [number]
eventType -
probableCause -
perceived Severity Category
SBL SBL
Table 3: Alarm Definition:
1.4.2 Alarm Description
The Alarm description is structured as follows:
Alarm Description
Impact on System
Failure Identification Strategy (if applicable)
Corrective Actions.
1.4.3 Alarm Definition
1.4.3.1 BannerEach BSS alarm definition starts with an identification banner which allows thelocation of the appropriate definition. It takes the form:
[36, 7] TRUNK - LOS
1.4.3.2 eventTypeThe eventType attribute identifies the basic type of the alarm. Table 1 describesthe event Types.
1.4.3.3 specificProblemsThe specificProblems provides the alarm class name.
1.4.3.4 probableCauseThis attribute provides additional information as to the probable cause ofthe alarm. Its value belongs to a set of possible values either defined inrecommendation X.721 (for those that have a wide applicability) or defined fora particular TMN project.
3BK 20918 AAAA PCZZA Ed.06 25 / 533
1 Introduction
1.4.3.5 perceivedSeverityThis attribute gives the severity level of the alarm. Table 2 describes theseverity level.
The table below provides a mapping between the severity level shown inAS and at the LMT.
MO Severity LMT Category
Critical VPMA, SA
Major PMA
Minor DMA
Warning MI
Table 4: Mapping of MO Perceived Severity to LMT Category
1.4.4 Alarm Description
1.4.4.1 Alarm DescriptionThe Alarm Description describes the alarm and, where appropriate, thedifferences to the default perceived severities.
1.4.4.2 Impact on TelecomThis field describes the impact on the Telecom system behavior. It alsocontains a table indicating which part of the system is affected by the fault interms of loss, degradation or none.
For example, if a cell is affected, the cell column in the table contains a tick ( ) ineither the Loss or Degradation row. The tick can be doubled in any one column( ), indicating the primary impact of the alarm. If the column has a tick in theNone row, that part of the system is unaffected by the fault. For different impactcases (redundancy, diversity, etc.) more symbols, like ladders (#), are used.
The table indicates the worst case, even though redundancy may be provided.
1.4.4.3 Impact on SystemThe impact on the system is defined in terms of Telecom and/or O&M.;
26 / 533 3BK 20918 AAAA PCZZA Ed.06
1 Introduction
1.4.4.4 Failure Identification StrategySometimes more information is necessary to determine the precise fault. TheFailure Identification Strategy lists the checks and tests to perform to obtainthis information.
The additional data is gathered from:
Diagnosis/tests to be applied - appropriate on-site or remote diagnostic and
test procedures to perform
Complex system alarm correlation - other checks that can provide moreinformation about the fault.
Checks that determine whether:
The failure is provoked by a problem external to the reporting unit
Multiple or repetitive failures are reported by one or more similar SBLs
The performance of the affected subsystem is degraded. Newperformance measurements can be compared with previous
measurements.
Resource and data verification - checks that determine whether:
Hardware is serviceable or available. The items checked are passive
items, such as cables, links and boards that do not report their state, andempty slots in subracks
Software versions and parameter settings are correct.
1.4.4.5 Corrective ActionsA description of the recovery actions to be performed by the operator ormaintenance staff. The recovery actions are based on the information providedby the alarm message or the results of diagnostic actions.
To solve the alarm, a graphical flowchart is used. It shows the required checks,tests and actions to be performed to determine the fault and to solve thealarm. The figure below shows an example of a flowchart and describesthe different flowchart fields.
Click on a dedicated action field to display the detailed description of the task.
Some alarms provide additional information. If it is displayed as a text message,the original information from the BSS has been decoded.
3BK 20918 AAAA PCZZA Ed.06 27 / 533
1 Introduction
[32,0] CONV
Alarmsolved
yesConverteroperational?
no
On−site
ContactSystem Support
Restart faulty converter by disengaging/engaging RIT
Identify the faulty DC/DC converter indicated by red illuminated LED.
On−site
On−site
Replace BSC RIT
Alarmsolved
yesConverteroperational?
no
Start field with alarm numberand alarm name
On−site action fields
Decision field
On−site action fields
Decision field
End Field
Figure 1: Graphical Flowchart for Corrective Actions
If the additional information is not decoded, it is displayed as pairs ofhexadecimal digits as described in BSC/TC Alarm Additional Information(Section 29). At the BSC terminal, the additional information consists ofnumbers in the range 0 to 255. Each number represents the contents of onepair of digits.
Decoding Additional Information from AlarmsDecoding BSC additional information must only be attempted by Alcatel systemsupport personnel.If a fault persists after corrective actions have been taken, send a copy of thealarm message containing the additional information to the Alcatel SystemSupport office.
28 / 533 3BK 20918 AAAA PCZZA Ed.06
2 Class 32: BSC-ENVIRON Alarms
2 Class 32: BSC-ENVIRON Alarms
This section defines the BSC alarms for the Class 32: BSC-ENVIRON alarmclass.
3BK 20918 AAAA PCZZA Ed.06 29 / 533
2 Class 32: BSC-ENVIRON Alarms
2.1 [32,0] CONV
specificProblems CONV
eventType Equipment
probableCause PowerProblem
perceivedSeverity Critical (VPMA)
Alarm Description A9120 BSC
The convertor condition is detected by the S-CPR. A fault can bedetected for a particular convertor. This is done by monitoring thescan point on the controlling S-CPR. One scan point exists for eachconvertor.
The redundant power supply is available.
Impact on System There are two convertors which provide power for each shelf. Thisprovides redundancy and, in the event of one convertor failing, theother convertor provides the power supply. In the event of the twoconvertors failing, no power is provided to the shelf. However, if bothconvertors powering the S-CPR fail, the battery back-up then providesits power supply.
Evolium A9120 BSC
The BSC is able to distinguish between the different convertors withthe Evolium A9120 BSC implementation and cabling. Therefore theRIT of the affected convertor is indicated in the alarm.
There is no impact on traffic because the power supplies are in parallel.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s) Signaling Call Handling O&M; Capabilities
Loss
Degradation
30 / 533 3BK 20918 AAAA PCZZA Ed.06
2 Class 32: BSC-ENVIRON Alarms
2.1.1 Corrective Actions
[32,0] CONV
Alarmsolved
yesConverteroperational?
no
On−site
ContactSystem Support
Restart faulty converter by disengaging/engaging RIT
Identify the faulty DC/DC converter indicated by red illuminated LED.
On−site
On−site
Replace BSC RIT
Alarmsolved
yesConverteroperational?
no
Figure 2: CONV: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 31 / 533
2 Class 32: BSC-ENVIRON Alarms
2.2 [32,1] BAT
specificProblems: BAT
eventType: Equipment
probableCause: PowerProblem
perceivedSeverity: Critical (VPMA)
Alarm Description The battery alarm condition can only be detected by the CPR which itcontrols. There is one battery controlling each S-CPR. So, if a batteryis removed, the CPR goes down and no fault is detected. Only a faultin the actual battery operation can be detected and this is done bymonitoring the scan point on the controlling S-CPR. One scan point isprovided for each battery. There is a physical connection between thebattery and the CPR. When this connection is broken, it is detectedby hardware via the scan points.
Impact on System S-CPR-ACTIVE
S-CPR (G2 BSC)
The memory board is implemented on a daughter board, plugged onthe CPRC. The CMFA board, (the flash-based board) indicates aproblem with the battery. The battery is empty and has no power toback up. The normal lifespan of a battery is 10 years.
The BSC is able to detect a fault, low voltage, on the correct battery dueto the fact that two scan points are used, one on CPR1 for battery Aand one on CPR2 for battery B. The RIT for both batteries is the same.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
32 / 533 3BK 20918 AAAA PCZZA Ed.06
2 Class 32: BSC-ENVIRON Alarms
2.2.1 G2-BSC Corrective Actions
[32,1] BAT
Alarmsolved
yesBatteryoperational?
no
On−site
Replace SYS−CPRC
ContactSystem Support
Identify the suspected SYS−CPRC.
On−site
Figure 3: BAT: A9120 BSC Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 33 / 533
2 Class 32: BSC-ENVIRON Alarms
34 / 533 3BK 20918 AAAA PCZZA Ed.06
3 Class 33: PROCESSOR Alarms
3 Class 33: PROCESSOR Alarms
This section defines the BSC alarms for the Class 33: PROCESSOR alarmclass.
3BK 20918 AAAA PCZZA Ed.06 35 / 533
3 Class 33: PROCESSOR Alarms
3.1 [33,0] RESTART
3.1.1 [33,0] RESTART (CPR)
specificProblems: RESTART
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Warning (MI)
Alarm Description An autonomous restart of a processor has occurred because of afailure condition on the processor.
Impact on System The SBL state remains unchanged.
The operating system and all FMM are sequentially re-initialized.
S-CPR - Simplex:
SDCCH allocation is not possible for some seconds. Newtelecommunication transactions fail.
There is no impact on current calls.
Standby S-CPR - Duplex:
Telecom functions are not affected.
If BSC or BTS processors are being loaded by the standby CPR,loading is stopped and then resumed when the restart is complete.
Active S-CPR - Duplex:
A takeover occurs if the standby CPR and its disk are IT; the standbyCPR now becomes active.
SDCCH allocation is not possible for some seconds. Newtelecommunication transactions fail. Communication with the OMC-Ris lost for some seconds.
OSI-CPR - Simplex:
Telecom functions are not affected.
If the restart happens at a five minute boundary and the CPR has tocarry out PM activities, the restart can cause some problems with fileproduction (such as, loss of last five minute contribution and missingfiles).
Standby OSI-CPR - Duplex:
The standby CPR is restarted.
If the restarted processor is an OSI-CPR that manages the OSIcommunications with the OMC-R, some file transfers may beinterrupted. If this happens, the OMC-R requests the information again.
36 / 533 3BK 20918 AAAA PCZZA Ed.06
3 Class 33: PROCESSOR Alarms
Impact on System (continued) Active OSI-CPR - Duplex:
Telecom functions are not affected.
If the active OSI-CPR is restarted, and the standby OSI-CPR andits disk are IT, the standby immediately takes over its functions andbecomes active.
If the restart happens at a five minute boundary and the CPR has tocarry out PM activities, the restart can cause some problems with fileproduction (such as, loss of last five minute contribution, missing files).
If the restarted processor is an OSI-CPR that manages the OSIcommunications with the OMC-R, some file transfers may beinterrupted. If this happens, the OMC-R requests the information again.
Note: For every processor restart, an attempt is made to minimize theimpact on the system. Recovery after a processor restart dependson the action taken.
The following corrections are performed by the system:
Restart the action
Resume the action
Initiate an audit
Terminate the action.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - -
3.1.1.1 Corrective ActionsThe processor returns to service automatically. If the restart procedure failsor there are too many restarts within a certain time frame, the processor isreloaded.
See BSC/TC Alarm Additional Information (Section 29) for the byte definition.
3BK 20918 AAAA PCZZA Ed.06 37 / 533
3 Class 33: PROCESSOR Alarms
3.1.2 [33,0] RESTART (DTC)
specificProblems: RESTART
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Warning (MI)
Alarm Description An autonomous restart of a processor occurred because of a failurecondition on the processor.
Impact on System The SBL state remains unchanged.
All stable calls assigned on TCHs remain unaffected
Some Signaling messages can be lost. This can affect sometransactions in progress.
Note: For every processor restart, an attempt has been made tominimize the impact on the system. Recovery after a processor restartdepends on the action taken.
The following corrections are performed by the system:
Restart the action
Resume the action
Initiate an audit
Terminate the action.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - -
3.1.2.1 Corrective ActionsThe processor returns to service automatically. If the restart procedure failsor there are too many restarts within a certain time frame, the processor isreloaded.
See BSC/TC Alarm Additional Information (Section 29) for the byte definition.
38 / 533 3BK 20918 AAAA PCZZA Ed.06
3 Class 33: PROCESSOR Alarms
3.1.3 [33,0] RESTART (TCU)
specificProblems: RESTART
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Warning (MI)
Alarm Description An autonomous restart of a processor occurred because of a failurecondition on the processor.
Impact on System The SBL state remains unchanged.
All stable calls are unaffected.
Some Signaling messages can be lost, which can affect sometransactions in progress.
Call setup in SDCCH phase/handover fails.
Note: For every processor restart, an attempt has been made tominimize the impact on the system. Recovery after a processor restartdepends on the action taken.
The following corrections are performed by the system:
Restart the action
Resume the action
Initiate an audit
Terminate the action.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - -
3.1.3.1 Corrective ActionsThe processor returns to service automatically. If the restart procedure failsor there are too many restarts within a certain time frame, the processor isreloaded.
See BSC/TC Alarm Additional Information (Section 29) for the byte definition.
3BK 20918 AAAA PCZZA Ed.06 39 / 533
3 Class 33: PROCESSOR Alarms
3.1.4 [33,0] RESTART (TSC)
specificProblems: RESTART
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Warning (MI)
Alarm Description An autonomous restart of a processor occurred because of a failurecondition on the processor.
Impact on System The SBL state remains unchanged.
All stable calls are unaffected.
Some Signaling messages can be lost, which can affect sometransactions in progress.
Call setup in SDCCH phase/handover fails.
Note: For every processor restart, an attempt has been made tominimize the impact on the system. Recovery after a processor restartdepends on the action taken.
The following corrections are performed by the system:
Restart the action
Resume the action
Initiate an audit
Terminate the action.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - -
3.1.4.1 Corrective ActionsNone – The processor returns to service automatically. If the restart procedurefails or there are too many restarts within a certain time frame, the processor isreloaded.
See BSC/TC Alarm Additional Information (Section 29) for the byte definition.
40 / 533 3BK 20918 AAAA PCZZA Ed.06
3 Class 33: PROCESSOR Alarms
3.2 [33,1] RESET
3.2.1 [33,1] RESET (CPR/DTC/TCU/TSC)
specificProblems: RESET
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Major (PMA)
Alarm Description An autonomous reload (reboot) of a processor occurred successfully.
Impact on System The SBL state remains unchanged.
CPR
The impact depends on the type of CPR.
S-CPR - Simplex:
SDCCH/TCH allocation is not possible for some minutes. New andexisting telecommunication transactions fail.
Standby S-CPR - Duplex:
Telecom functions are not affected.
Active S-CPR - Duplex:
A takeover occurs if the standby CPR and its disk are IT; the standbyCPR now becomes active.
SDCCH allocation is not possible for some seconds. New and existingtelecommunication transactions fail.
Communication with the OMC-R is lost for some seconds.
If there is an autonomous reboot of one S-CPR and a restart of theother CPR, the whole system can crash.
3BK 20918 AAAA PCZZA Ed.06 41 / 533
3 Class 33: PROCESSOR Alarms
Impact on System OSI-CPR - Simplex:
Telecom functions are not affected.
Standby OSI-CPR - Duplex:
If the OSI-CPR is handling the X.25 link to the OMC-R, communicationwith the OMC-R is lost for some seconds.
If the reset/reload (reboot) processor is an OSI-CPR that managesthe OSI communication with the OMC-R, some file transfers may beinterrupted. If this happens, the OMC-R requests the information again.
Active OSI-CPR - Duplex:
Telecom functions are not affected.
If the master performs a Reset, the standby immediately takes over itsfunctions. If the reset happens at a five minute boundary, there may beproblems with production of PM files.
Note: For every processor reset/reload (reboot), an attempt is madeto minimize the impact on the system. Recovery after a processorreset depends on the action taken.
The following corrections are performed by the system:
Restart the action
Resume the action
Initiate an audit
Terminate the action.
For the consequences of an SBL CPR state change, seeConsequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s) Signaling CallHandling
O&M; Capabilities
Loss -
Degradation - - - - -
42 / 533 3BK 20918 AAAA PCZZA Ed.06
3 Class 33: PROCESSOR Alarms
Impact on System DTC
All calls managed by the processor are lost.
For every processor reset/reload (reboot), an attempt is made tominimize the impact on the system. Recovery after a processor resetdepends on the action taken.
The following corrections are performed by the system:
Restart the action
Resume the action
Initiate an audit
Terminate the action.
For the consequences of an SBL DTC state change, seeConsequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - -
Degradation - - - - -
Impact on System TCU
All calls managed by the processor are lost.
For every processor reset/reload (reboot), an attempt has been madeto minimize the impact on the system. Recovery after a processorreset depends on the action taken.
The following corrections are performed by the system:
Restart the action
Resume the action
Initiate an audit
Terminate the action.
For the consequences of an SBL TCU state change, seeConsequences of an SBL State Change (Section 30).
3BK 20918 AAAA PCZZA Ed.06 43 / 533
3 Class 33: PROCESSOR Alarms
Impact Trunk(s) Cell/BTS(s) Signaling CallHandling
O&M; Capabilities
Loss -
Degradation - - - - -
Impact on System TSC
All transmission Signaling and downloading managed by the processorare lost.
For every processor reset/reload (reboot), an attempt has been madeto minimize the impact on the system. Recovery after a processorreset depends on the action taken.
The following corrections are performed by the system:
Restart the action
Resume the action
Initiate an audit
Terminate the action.
For the consequences of an SBL TSC state change, seeConsequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s) TransmissionSignaling
CallHandling
O&M;Capabilities
Loss - - -
Degradation - - - - -
3.2.1.1 Corrective ActionsIf the reload is successful, the processor returns to service automatically. If itdoes not, contact Alcatel system support.
See BSC/TC Alarm Additional Information (Section 29) for the byte definition.
44 / 533 3BK 20918 AAAA PCZZA Ed.06
3 Class 33: PROCESSOR Alarms
3.2.2 [33,1] RESET (CPR)
specificProblems: RESET
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Indeterminate
Alarm Description An autonomous reload (reboot) of a processor occurred.
3BK 20918 AAAA PCZZA Ed.06 45 / 533
3 Class 33: PROCESSOR Alarms
Impact on System The SBL state remains unchanged.
The impact depends on the CPR.
S-CPR - Simplex:
SDCCH/TCH allocation is not possible for some minutes. New and existingtelecommunication transactions fail.
Standby S-CPR - Duplex:
Telecom functions are not affected.
Active S-CPR - Duplex:
A takeover occurs if the standby CPR and its disk are IT; the standby CPRnow becomes active.
SDCCH allocation is not possible for some seconds. New and existingtelecommunication transactions fail.
Communication with the OMC-R is lost for some seconds.
If there is an autonomous reboot of one S-CPR and a restart of the other CPR,the whole system can crash.
OSI-CPR - Simplex:
Telecom functions are not affected.
Impact on System Standby OSI-CPR - Duplex:
If the OSI-CPR is handling the X.25 link to the OMC-R, communication withthe OMC-R is lost for some seconds.
If the reset/reload (reboot) processor is an OSI-CPR that manages the OSIcommunication with the OMC-R, some file transfers may be interrupted. If thishappens, the OMC-R requests the information again.
Active OSI-CPR - Duplex:
Telecom functions are not affected.
If the master performs a Reset, the standby immediately takes over its functions.If the reset happens at a five minute boundary, there may be problems withproduction of PM files.
Note: For every processor reset/reload (reboot), an attempt is made to minimizethe impact on the system. Recovery after a processor reset depends on theaction taken.
The following corrections are performed by the system:
Restart the action
Resume the action
Terminate the action.
See Consequences of an SBL State Change (Section 30).
46 / 533 3BK 20918 AAAA PCZZA Ed.06
3 Class 33: PROCESSOR Alarms
Impact Trunk(s) Cell/BTS(s) Signaling CallHandling
O&M; Capabilities
Loss -
Degradation - - - - -
3.2.2.1 Corrective ActionsIf the reload is successful, the processor returns to service automatically. If itdoes not, contact Alcatel system support.
See BSC/TC Alarm Additional Information (Section 29) for the byte definition.
3BK 20918 AAAA PCZZA Ed.06 47 / 533
3 Class 33: PROCESSOR Alarms
3.2.3 [33,1] RESET (DTC)
specificProblems: RESET
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Major (PMA)
Alarm Description An autonomous reload (reboot) of a processor has occurred.
Impact on System All calls managed by the processor are lost.
For every processor reset/reload (reboot), an attempt is made tominimize the impact on the system. Recovery after a processor resetdepends on the action taken.
The following corrections are performed by the system:
Restart the action
Resume the action
Initiate an audit
Terminate the action.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - -
Degradation - - - - -
3.2.3.1 Corrective ActionsIf the reload is successful, the processor returns to service automatically. If itdoes not, contact Alcatel system support.
See BSC/TC Alarm Additional Information (Section 29) for the byte definition.
48 / 533 3BK 20918 AAAA PCZZA Ed.06
3 Class 33: PROCESSOR Alarms
3.2.4 [33,1] RESET (TCU)
specificProblems: RESET
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Major (PMA)
Alarm Description An autonomous reload (reboot) of a processor occurred.
Impact on System All calls managed by the processor are lost.
For every processor reset/reload (reboot), an attempt has been madeto minimize the impact on the system. Recovery after a processorreset depends on the action taken.
The following corrections are performed by the system:
Restart the action
Resume the action
Initiate an audit
Terminate the action.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
3.2.4.1 Corrective ActionsIf the reload is successful, the processor returns to service automatically. If itdoes not, contact Alcatel system support.
See BSC/TC Alarm Additional Information (Section 29) for the byte definition.
3BK 20918 AAAA PCZZA Ed.06 49 / 533
3 Class 33: PROCESSOR Alarms
3.2.5 [33,1] RESET (TSC)
specificProblems: RESET
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Major (PMA)
Alarm Description An autonomous reload (reboot) of a processor has occurred.
Impact on System All transmission Signaling and downloading managed by the processorare lost.
For every processor reset/reload (reboot), an attempt has been madeto minimize the impact on the system. Recovery after a processorreset depends on the action taken.
The following corrections are performed by the system:
Restart the action
Resume the action
Initiate an audit
Terminate the action.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - -
Degradation - - - - -
3.2.5.1 Corrective ActionsIf the reload is successful, the processor returns to service automatically. If itdoes not, contact Alcatel system support.
See BSC/TC Alarm Additional Information (Section 29) for the byte definition.
50 / 533 3BK 20918 AAAA PCZZA Ed.06
3 Class 33: PROCESSOR Alarms
3.3 [33,3] ACCESS-FAIL
specificProblems: ACCESS-FAIL
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Major (PMA)
Alarm Description The self-maintenance part of the system (i.e., Heartbeat) detected anunreachable processor and informs central maintenance.
Impact on System If a reload request is not received from the processor, the processorSBL is FLT and an alarm is sent with alarm type ’Access Fail’. Theprocessor is not accessible.
CPR
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - -
Impact on System DTC
All calls managed by the processor are lost.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - -
Degradation - - -
3BK 20918 AAAA PCZZA Ed.06 51 / 533
3 Class 33: PROCESSOR Alarms
Impact on System TCU
If the impacted cells have TRX mapped on other TCU, recovery willinsure to keep the TRX with highest priorities.
If this is not the case, the cells are lost.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - -
Degradation - -
Impact on System TSC
There is no supervision anymore for the Q1 modules controlled by thisTSC (TC, ASMB, BIE, possibly BTS).
There is no possibility to perform evolution of the hardwareconfiguration for the same Q1 modules.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) TransmissionSignaling
CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - - -
52 / 533 3BK 20918 AAAA PCZZA Ed.06
3 Class 33: PROCESSOR Alarms
3.3.1 Corrective Actions
[33,3] ACCESS−FAIL
Alarmsolved
yesAccessoperational?
no
ContactSystem Support
yesSubsequent alarm(s) events?
no
Solve that alarm(s) first
MO is Unlocked/
enabled?
yes
no
Check for BSC switch problems
On−site
Replace CPR/DTC/TCU/TSC
Figure 4: ACCESS-FAIL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 53 / 533
3 Class 33: PROCESSOR Alarms
3.4 [33,4] RELC-OV
specificProblems: RELC-OV
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Major (PMA)
Alarm Description The processor has been declared FOS and is removed from service.This is done because there have been too many processor reloadswithin a certain time frame for a specific processor.
The loader keeps a record of the number of reload attempts for eachprocessor within a certain time frame. If too many reload attemptsoccur, central maintenance auto-disables the processor, unless theprocessor is an S-CPRA (simplex). The auto-disabled processor isblocked from use.
Impact on System CPR
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - -
Impact on System DTC
All calls managed by the processor are lost.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - -
54 / 533 3BK 20918 AAAA PCZZA Ed.06
3 Class 33: PROCESSOR Alarms
Impact on System TCU
If the impacted cells have TRX mapped on other TCU, recovery willinsure to keep the TRX with highest priorities
If this is not the case, the cells are lost.
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - -
Degradation - -
Impact on System TSC
There is no supervision anymore for the Q1 modules controlled by thisTSC (TC, ASMB, BIE, possibly BTS).
There is no possibility to perform evolution of the hardwareconfiguration for the same Q1 modules.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) TransmissionSignaling
CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 55 / 533
3 Class 33: PROCESSOR Alarms
3.4.1 Corrective Actions
[33,4] RELOC−OV
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
Lock CPR/DTC/TCU/TSC
On−site
Replace CPR/DTC/TCU/TSC
TestCPR/DTC/TCU/TSC
VerifyCPR/DTC/TCU/TSC
Unlock CPR/DTC/TCU/TSC
Alarmsolved
yes
Alarm persists?
no
Figure 5: RELC-OVL: Corrective Actions
56 / 533 3BK 20918 AAAA PCZZA Ed.06
3 Class 33: PROCESSOR Alarms
3.5 [33,7] TAKEOVER
specificProblems: TAKEOVER
eventType: ProcessingError
probableCause: softwareProgramAbnormallyTerminated
perceivedSeverity: Warning (MI)
Alarm Description There has been a change in the active processor in the case of anactive/standby processor pair. The active/standby processor pairs inthe BSC are the CPRs or the DTC TCH-RM. This alarm identifies theprocessor that is now active and is the new master. The previouslyactive processor goes into standby mode.
This alarm is generated only when a takeover occurs.
Another alarm or an operator action causing the take-over can lead toextra impact on the telecom traffic.
Impact on System The SBL state remains unchanged.
CPR
During a takeover an attempt is made to minimize the impact on thesystem and ongoing transactions with the OMC-R. Recovery after aCPR takeover depends on the action taken.
The following corrective actions are performed by the system:
Restart the action
Resume the action
Initiate an audit
Terminate the action.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 57 / 533
3 Class 33: PROCESSOR Alarms
Impact on System DTC TCH-RM
During a take-over no radio channel allocation is possible for a shortperiod.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - -
3.5.1 Corrective Actions
[33,7] TAKEOVER
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
Lock CPR/DTC
TestCPR/DTC
VerifyCPR/DTC
Unlock CPR/DTC
Figure 6: TAKEOVER: Corrective Actions
58 / 533 3BK 20918 AAAA PCZZA Ed.06
3 Class 33: PROCESSOR Alarms
3.6 [33,9] SDCCH-OVRL-BSC
specificProblems: SDCCH-OVRL-BSC
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Warning (MI)
Alarm Description The load on the TCU is excessive due to a high number ofsimultaneously active SDCCHs.
Impact on System The BSC applies in this case a delayed release of the SDCCH.This decreases the TCU load but increases the SDCCH occupancy,thus leading to more lack of SDCCH resources to establish newtransactions.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - -
3.6.1 Corrective Actions
[33,9] SDCCH−OVRL−BSC
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
Remap the RSL to spread the load of SDCCH among other TCUs (flatten hot spots).
Figure 7: SDCCH-OVRL-BSC: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 59 / 533
3 Class 33: PROCESSOR Alarms
Remaping the RSL can be done:
In case the operator has concentrated the definition of SDCCH in few
TRX and the cell is mapped on several TCU, he should modify the cellconfiguration in order to better spread the load on different TRX , then he
should trigger the complete unmapping of all the TRX of the cell.
If the cell is mapped only on one TCU, if TRE are multiplexed together,operator shall first change the multiplexing mode of the BTS, selecting,
for example, the ’high signalling load’.Then he should trigger the flattenhop spot reshuffling.
60 / 533 3BK 20918 AAAA PCZZA Ed.06
3 Class 33: PROCESSOR Alarms
3.7 [33,251] AUDIT
specificProblems: AUDIT
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Minor (DMA)
Alarm Description A maintenance audit freed an SBL that remained in an intermediatemaintenance state (AUTO-MSD) following a restart, reload, reboot or atakeover. The audit consists of an autonomous disable followed by aninitialize. If the Initialize command fails, the device is FLT.
Impact on System CPR
All calls managed by the processor are lost.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
Impact on System DTC
All calls managed by the processor are lost.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - -
3BK 20918 AAAA PCZZA Ed.06 61 / 533
3 Class 33: PROCESSOR Alarms
Impact on System TCU
All calls managed by the processor are lost.
If a TCUA processor is involved in a processor audit, and the resultis unsuccessful, recovery action (blocking and reconfiguration ifredundant resources exist) is needed. This applies if the TCUA carriesthe BCCH or an SDCCH.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation -
3.7.1 Corrective Actions
[33,251] AUDIT
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
Lock CPR/DTC/
TCU
On−site
G2: Replace CPR/DTC/TCU
TestCPR/DTC/
TCU
VerifyCPR/DTC/
TCU
Unlock CPR/DTC/
TCU
Alarmsolved
yes
Alarm persists?
no
Figure 8: AUDIT: Corrective Actions
62 / 533 3BK 20918 AAAA PCZZA Ed.06
4 Class 34: SWITCH Alarms
4 Class 34: SWITCH Alarms
This section defines the BSC alarms for the Class 34: SWITCH alarm class.
3BK 20918 AAAA PCZZA Ed.06 63 / 533
4 Class 34: SWITCH Alarms
4.1 [34,251] AUDIT
specificProblems: AUDIT
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Minor (DMA)
Alarm Description A maintenance audit freed an SBL that remained in the AUTO-MSDstate following a restart, reload, reboot or a takeover. The auditconsists of an autonomous disable followed by an initialize. If theInitialize command fails, the device is FOS.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - -
Degradation - - - - -
64 / 533 3BK 20918 AAAA PCZZA Ed.06
4 Class 34: SWITCH Alarms
4.1.1 Corrective Actions
[34,251] AUDIT
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
Lock SWITCH
On−site
Replace CPR/DTC/TCU
TestSWITCH
VerifySWITCH
Unlock SWITCH
Alarmsolved
yes
Alarm persists?
no
Figure 9: AUDIT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 65 / 533
4 Class 34: SWITCH Alarms
66 / 533 3BK 20918 AAAA PCZZA Ed.06
5 Class 35: N7 Alarms
5 Class 35: N7 Alarms
This section defines the BSC alarms for the Class 35: N7 alarm class.
3BK 20918 AAAA PCZZA Ed.06 67 / 533
5 Class 35: N7 Alarms
5.1 [35,0] LNK-REP
specificProblems: LNK-REP
eventType: Communication
probableCause: TransmitterFailure
perceivedSeverity: Minor (DMA)
Alarm Description This message can represent either an event or a change of status. If itis an event, it indicates a change of link state . If it is a state change, itindicates a change of traffic state.
Impact on System 1. Change of Link state. This alarm is commonly caused bya clock problem. If it is accompanied by SLIP_UNDER_RUN,SLIP_OVER_RUN alarms, there is a lack of synchronisation of the2 Mbits signals arriving on the BSC. And the transmission boardssettings are incorrect. A high error rate on the transmission lines (BER10-4) has forced use of the transmission modules internal clock.2. Change of traffic state. There is a persistent problem on the N7link. If the alarm is accompanied by transmission alarms, there is atransmission problem. Otherwise the problem is caused by an incidentat the MSC. The alarm is accompanied by either a SLIP-OV [36,5] orSLIP-UN [36,6] alarm related to the corresponding ATR SBL.
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
68 / 533 3BK 20918 AAAA PCZZA Ed.06
5 Class 35: N7 Alarms
5.1.1 Corrective Actions
The SBL normally returns to IT without operator intervention. Do not run aDisable command because you would need to keep trying to initialize theSBL until successful.
[35,0] LNK−REP
Alarmsolved
yesAlarm persists?
no
On−site
Replace Sync Input module
Solve Clock alarm(s) first
On−site
Replace transmission lines equipment
Check/correct transmission board
settings
yes
2−Mbit/s Sync inputs OK?
no
yesClock alarm events?
no− There is a lack of synchronization of the 2 MBit/s signals arriving at the BSC.or− The transmission board settings are incorrect.or− A high error rate on the transmissionlines forced the use of the transmission modules internal clock.
yesSLIP... alarm events?
no
Alarmsolved
Alarm persists?
no
On−site
yes
Transmission lines OK?
no
On−site
ContactSystem Support
yes
Figure 10: LNK-REP: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 69 / 533
5 Class 35: N7 Alarms
5.2 [35,2] RTE-REP
specificProblems: RTE-REP
eventType: Communication
probableCause: ResponseTimeExcessive
perceivedSeverity: Critical (VPMA)
Alarm Description A destination became accessible or inaccessible.
Alarm Number The alarm number represents the DPC of the MSC.
Impact on System This alarm can come from transmission problem on the Ater mux oron the Atr. In this case, the N�7 alarm is a single consequence ofthese problems and operator can ignore it and he shall first solve thetransmission problems. This alarm is generated for every BSC restart,reset or reload.
See Consequences of an SBL State Change (Section 30).
When the RTE-REP alarm is ’ON’, the communication with the MSCis lost, there is no more possible traffic, the BSC bars automaticallyall the cells.
When the RTE-REP alarm is ’OFF’, the BSC unbars the cell:
- either step by step (by group of access classes)
- or in one shot, depending on the parameter T18
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M;Capabilities
Loss - - - -
Degradation - - - - -
70 / 533 3BK 20918 AAAA PCZZA Ed.06
5 Class 35: N7 Alarms
5.2.1 Corrective Actions
[35,2] RTE−REP
Check transmission or reset
ASMB/ASMC
yesN7 system works correctly at
peer side?
no
Alarm persists?
no
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
yes
yes
Figure 11: RTE-REP: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 71 / 533
5 Class 35: N7 Alarms
5.3 [35,3] INC-REP
specificProblems: INC-REP
eventType: Communication
probableCause: Scvfee alarm description below
perceivedSeverity: Warning (MI)
Alarm Description An incident report is generated whenever the BSC receives a messagewith either a DPC, OPC or an SSF label part different from theexpected one.
It is also generated when on changeover/changeback, too many MSUsare received from other DTCs.
Excessive incident report generation is avoided by limiting the numberof reports per unit time.
Infrequent software error.
Note:This alarm can be produced at a maximum of once an hour.
Impact on System The SBL state is not changed.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
72 / 533 3BK 20918 AAAA PCZZA Ed.06
5 Class 35: N7 Alarms
5.3.1 Corrective Actions
[35,3] INC−REP
yes
N7 system of DPC, OPC
or SSF OK?
no
Alarmsolved
Alarm persists?
no
ContactSystem Support
yes
Solve N7 problem, use N7 monitor
On−site
Replace DTC
Figure 12: INC-REP: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 73 / 533
5 Class 35: N7 Alarms
5.4 [35,251] AUDIT
specificProblems: AUDIT
eventType: Communication
probableCause: UnderlyingResourceUnavailable
perceivedSeverity: Minor (DMA)
Alarm Description A maintenance audit freed an SBL that remained in the AUTO-MSDstate following a restart, reload, reboot or a takeover. A maintenanceaudit consists of an autonomous disable followed by an initialize. If theInitialize command fails, the device is FLT.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - - -
74 / 533 3BK 20918 AAAA PCZZA Ed.06
5 Class 35: N7 Alarms
5.4.1 Corrective Actions
[35,251] AUDIT
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
Lock N7
On−site
Replace suspected RIT
TestN7
VerifyN7
Unlock N7
yes
Alarm persists?
no
Figure 13: AUDIT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 75 / 533
5 Class 35: N7 Alarms
76 / 533 3BK 20918 AAAA PCZZA Ed.06
6 Class 36: TRUNK Alarms
6 Class 36: TRUNK Alarms
This section defines the BSC alarms for the Class 36: TRUNK alarm class.
3BK 20918 AAAA PCZZA Ed.06 77 / 533
6 Class 36: TRUNK Alarms
6.1 [36,0] LFA
specificProblems: LFA
eventType: Communication
probableCause: LossOfFrame
perceivedSeverity: Major (PMA)
Alarm Description The trunk supervisor detected a loss of frame alignment. This alarm isbased on received data in channel 0, before re-timing.
Impact on System A loop test is done by the DTC to verify if the failure is internal (FLT)or external (EF).
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - -
6.1.1 Corrective Actions
[36,0] LFA
yes
Trunk system works correctly at
peer side?
no
Alarmsolved
Alarm persists?
no
yes
Trigger recovery action on peer side and wait until trunk becomes available.
ContactSystem Support
Figure 14: LFA: Corrective Actions
78 / 533 3BK 20918 AAAA PCZZA Ed.06
6 Class 36: TRUNK Alarms
6.2 [36,3] RAI
specificProblems: RAI
eventType: Communication
probableCause: farEndReceivedFailure
perceivedSeverity: Major (PMA)
Alarm Description The trunk supervisor detected a RAI, also known as a FEA.
Impact on System Whenever a failure occurs, a loop test is done by the DTC to verifyif the failure is internal or external. The trunk is then autonomouslydisabled. Blocking and release of all associated A-channels is carriedout depending on whether the ’ignore 2 Mbit/s flag’ is set.
The RAI alarm is generated by the BSC in response to a receivedtransmission alarm, (i.e., LIS, AIS, LFA, EER, BERH). This is the BSCview of transmission, so check for transmission alarms.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - -
3BK 20918 AAAA PCZZA Ed.06 79 / 533
6 Class 36: TRUNK Alarms
6.2.1 Corrective Actions
[36,3] RAI
yes
Trunk system works correctly at
peer side?
no
Alarmsolved
Alarm persists?
no yes
Trigger recovery action on peer side and wait until trunk becomes available.
ContactSystem Support
Solve that alarm(s) first
Transmission alarm (LIS, AIS; LFA,
EER, BERH) events?
yes
no
Figure 15: RAI: Corrective Actions
80 / 533 3BK 20918 AAAA PCZZA Ed.06
6 Class 36: TRUNK Alarms
6.3 [36,4] AIS
specificProblems: AIS
eventType: Communication
probableCause: AIS
perceivedSeverity: Major (PMA)
Alarm Description The trunk supervisor detected an all ones indication (i.e., AIS). Lessthan four zeros in four consecutive frames means AIS.
Whenever a failure occurs, a loop test is done by the DTC, to verify ifthe failure is internal or external.
Impact on System A local loop test is done to verify if the failure is external (EF) or internal(FLT) by own circuit at the DTC.
A trunk AIS alarm is detected by the BSC. This is the BSC view oftransmission, so it is important to check for transmission alarms.
The trunk is then autonomously disabled. Blocking and release of allassociated A-channels is carried out depending on whether the ’ignore2 Mbit/s flag’ is set or not.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - -
3BK 20918 AAAA PCZZA Ed.06 81 / 533
6 Class 36: TRUNK Alarms
6.3.1 Corrective Actions
[36,4] AIS
yes
Trunk system works correctly at
peer side?
no
Alarmsolved
Alarm persists?
no ContactSystem Support
yes
Trigger recovery action on peer side and wait until trunk
becomes available.
Solve that alarm(s) first
Transmission alarm (LIS, AIS; LFA,
EER, BERH) events?
yes
no
Figure 16: AIS: Corrective Actions
82 / 533 3BK 20918 AAAA PCZZA Ed.06
6 Class 36: TRUNK Alarms
6.4 [36,5] SLIP-OV
specificProblems: SLIP-OV
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Warning (MI)
Alarm Description The trunk supervisor has detected a slip overrun. An additional signal,DIR, indicates the direction of the slip. An indication will mean that theexternal frequency clock extracted from its own PCM link is greater,’external clock faster’ than the internal frequency clock selected bythe BSC.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 83 / 533
6 Class 36: TRUNK Alarms
6.4.1 Corrective Actions
[36,5] SLIP−OV
yes
Transmission board settings
OK?
no
Alarmsolved
Alarm persists?
no ContactSystem Support
yes
Correct Transmissionboards settings
Solve that alarm(s) first
Clock or Synchronization alarm
events?
yes
no
Figure 17: SLIP-OV: Corrective Actions
84 / 533 3BK 20918 AAAA PCZZA Ed.06
6 Class 36: TRUNK Alarms
6.5 [36,6] SLIP-UN
specificProblems: SLIP-UN
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Warning (MI)
Alarm Description The trunk supervisor has detected slip underrun. A fault is indicatedevery time a slip occurs. An additional signal, DIR, indicates thedirection of the slip. No indication will mean that the external frequencyclock extracted from its own PCM link is less, ’external clock slower’than the internal frequency clock selected by the BSC.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 85 / 533
6 Class 36: TRUNK Alarms
6.5.1 Corrective Actions
[36,6] SLIP−UN
yes
Transmission board settings
OK?
no
Alarmsolved
Alarm persists?
no yes
Correct Transmissionboards settings
ContactSystem Support
Solve that alarm(s) first
Clock or Synchronization alarm
events?
yes
no
Figure 18: SLIP-UN: Corrective Actions
86 / 533 3BK 20918 AAAA PCZZA Ed.06
6 Class 36: TRUNK Alarms
6.6 [36,7] LOS
specificProblems: LOS
eventType: Communication
probableCause: LossOfSignal
perceivedSeverity: Major (PMA)
Alarm Description The trunk supervisor detected a LOS. Whenever a failure occurs, aloop test is done by the DTC to verify if the failure is internal or external.
Impact on System A local loop test is done to verify if the failure is external (EF) or internal(FLT) by own circuit at the DTC.
A-Trunk LOS alarm is detected by the BSC. This is the BSC viewof transmission, so check for transmission alarms. The trunk isautonomously disabled. Blocking and release of all associatedA-channels is carried out depending on whether the ’ignore 2 Mbit/sflag’ is set.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - - -
3BK 20918 AAAA PCZZA Ed.06 87 / 533
6 Class 36: TRUNK Alarms
6.6.1 Corrective Actions
[36,7] LOS
yes
Trunk system works correctly at
peer side?
no
Alarmsolved
Alarm persists?
no yes
Trigger recovery action on peer side and wait until trunk becomes available.
ContactSystem Support
Solve that alarm(s) first
Transmission alarm (LIS, AIS; LFA, EER, BERH)
events?
yes
no
Figure 19: LOS: Corrective Actions
88 / 533 3BK 20918 AAAA PCZZA Ed.06
6 Class 36: TRUNK Alarms
6.7 [36,10] CRCA
specificProblems: CRCA
eventType: Communication
probableCause: LossOfFrame
perceivedSeverity: Warning (MI)
Alarm Description This alarm is a quality alarm. It indicates that the number of cyclicredundancy checks reached a certain threshold. The alarm is onlyissued if the fault persists for more than 100 ms.
Impact on System A local loop test is done to verify if the failure is external or internalby own circuit at the DTC.
When the CRCA threshold has been reached, a mechanism is startedto search for the new frame alignment to re-synchronize the trunk.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s)
Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - -
3BK 20918 AAAA PCZZA Ed.06 89 / 533
6 Class 36: TRUNK Alarms
6.7.1 Corrective Actions
[36,10] CRCA
yes
Trunk system works correctly at
peer side?
no
Alarmsolved
Alarm persists?
no yes
Trigger recovery action on peer side and wait until trunk becomes available.
ContactSystem Support
Solve that alarm(s) first
Transmission alarm (LIS, AIS; LFA, EER, BERH)
events?
yes
no
Figure 20: CRCA: Corrective Actions
90 / 533 3BK 20918 AAAA PCZZA Ed.06
6 Class 36: TRUNK Alarms
6.8 [36,11] CH0-EERH
specificProblems: CH0-EERH
eventType: Communication
probableCause: DegradedSignal
perceivedSeverity: Major (PMA)
Alarm Description ERRH is bit errors measured on the frame alignment signal. Anexcessive error rate has been detected in CH0 >= 10 E-3. The faultis not necessarily on the submultiplexer. The location depends on thedistribution of channel 0 throughout the transmission system.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s)
Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - -
6.8.1 Corrective Actions
[36,11] CH0−EERH
yes
Trunk system works correctly at
peer side?
no
Alarmsolved
Alarm persists?
no yes
Trigger recovery action on peer side and wait until trunk becomes available.
ContactSystem Support
Solve that alarm(s) first
Transmission alarm (LIS, AIS; LFA, BERH)
events?
yes
no
Figure 21: CH0-EERH: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 91 / 533
6 Class 36: TRUNK Alarms
6.9 [36,12] CRC4-BERH
specificProblems: CRC4-BERH
eventType: Communication
probableCause: excessiveBerr
perceivedSeverity: Major (PMA)
Alarm Description This alarm indicates that the BER high measurement based on CRC4error detection exceeds 10 E-3.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - -
6.9.1 Corrective Actions
[36,12] CRC4−BERH
yes
Trunk system works correctly at
peer side?
no
Alarmsolved
Alarm persists?
no yes
Trigger recovery action on peer side and wait until trunk becomes available.
ContactSystem Support
Solve that alarm(s) first
Transmission alarm events?
yes
no
Figure 22: CRC4-BERH: Corrective Actions
92 / 533 3BK 20918 AAAA PCZZA Ed.06
6 Class 36: TRUNK Alarms
6.10 [36,13] CRC4-BERL
specificProblems: CRC4-BERL
eventType: Communication
probableCause: DegradedSignal
perceivedSeverity: Minor (DMA)
Alarm Description The BER based on CRC4 error detection exceeded 10 E-6, but wasbelow the rate 10 E-3.
The trunk is functioning at an extremely good rate.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
6.10.1 Corrective Actions
None – the trunk is functioning at an extremely good rate.
3BK 20918 AAAA PCZZA Ed.06 93 / 533
6 Class 36: TRUNK Alarms
6.11 [36,251] AUDIT
specificProblems: AUDIT
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Minor (DMA)
Alarm Description A maintenance audit freed an SBL that remained in the AUTO-MSDstate following a restart, reload, reboot or a takeover. A maintenanceaudit consists of an autonomous disable followed by an initialize. If theInitialize command fails, the device is FLT.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - -
Degradation - - - - -
94 / 533 3BK 20918 AAAA PCZZA Ed.06
6 Class 36: TRUNK Alarms
6.11.1 Corrective Actions
[36,251] AUDIT
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
Lock ATR
On−site
Replace suspected RIT
TestATR
VerifyATR
Unlock ATR
yes
Alarm persists?
no
Figure 23: AUDIT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 95 / 533
6 Class 36: TRUNK Alarms
96 / 533 3BK 20918 AAAA PCZZA Ed.06
7 Class 38: X.25 Alarms
7 Class 38: X.25 Alarms
This section defines the BSC alarms for the Class 38: X.25 alarm class.
3BK 20918 AAAA PCZZA Ed.06 97 / 533
7 Class 38: X.25 Alarms
7.1 [38,0] MODEM-FLT
specificProblems: MODEM-FLT
eventType: Communication
probableCause: CommunicationSubsystemFailure
perceivedSeverity: Major (PMA)
Alarm Description The modem used in the X.25 connection is faulty, or the local terminalpower is off.
Impact on System An X.25 can connect the BSC to the BSC local terminal or the BSCto the OMC-R. When both X.25 connections become faulty, theconnection between the BSC and the other entity is broken.
If the alarm occurs in relation to the link with the OMC-R, the BSC isof course unable to send the alarm to the OMC-R. However, if a localterminal is connected, the BSC sends the alarm to the terminal.
When the BSC is unable to send an alarm to the OMC-R, the BSC triesrepeatedly to send the alarms BSC_SYNC_REQUEST for BSC alarmsand TSC_BTS_SYNC_REQUEST for TSC and BTS alarms.
When the alarm is eventually received, the OMC-R triggers an alarmaudit for the BSC alarms and an alarm audit for the TSC and BTSalarms.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - - -
98 / 533 3BK 20918 AAAA PCZZA Ed.06
7 Class 38: X.25 Alarms
7.1.1 Corrective Actions
[38,0] MODEM−FLT
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
Solve that alarm(s) first
yesBSC SYNC−REQUEST
alarm events?
noOn−site
Check/repair/replace X.25 connection
On−site
Check/repair/replace X.25 modem
On−site
Check/repower/repair/replace
local BSC terminal
Figure 24: MODEM-FLT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 99 / 533
7 Class 38: X.25 Alarms
7.2 [38,1] LINK-FLT
specificProblems: LINK-FLT
eventType: Communication
probableCause: CommunicationProtocolError
perceivedSeverity: Major (PMA)
Alarm Description The X.25 L2 is disconnected, although the L1 can still be present.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s)
Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - -
100 / 533 3BK 20918 AAAA PCZZA Ed.06
7 Class 38: X.25 Alarms
7.2.1 Corrective Actions
[38,1] LINK−FLT
Lock X.25
Unlock X.25
yes
X.25 link works correctly at
peer side?
no
Alarmsolved
Alarm persists?
yes
Trigger recovery action on peer side and wait until
X.25 link becomes available.
ContactSystem Support
Alarm persists?
no
yes
no
Figure 25: LINK-FLT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 101 / 533
7 Class 38: X.25 Alarms
7.3 [38,2] PROT
specificProblems: PROT
eventType: Communication
probableCause: CommunicationProtocolError
perceivedSeverity: Warning (MI)
Alarm Description An X.25 network layer (that is, L3) protocol problem occurred.
An X.25 protocol problem can be caused by one of the following:
Second timeout on restart confirmation
Second timeout on clear confirmation.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - -
102 / 533 3BK 20918 AAAA PCZZA Ed.06
7 Class 38: X.25 Alarms
7.3.1 Corrective Actions
[38,2] PROT
Lock X.25
Unlock X.25
yes
X.25 link works correctly at
peer side?
no
Alarmsolved
Alarm persists?
no
yes
Trigger recovery action on peer side and wait until
X.25 link becomes available.
ContactSystem Support
Alarm persists?
no
yes
Second timeout
on:
clear confirmation
restart confirmation
Figure 26: PROT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 103 / 533
7 Class 38: X.25 Alarms
7.4 [38,251] AUDIT
specificProblems: AUDIT
eventType: Communication
eventType: Communication
probableCause: UnderlyingResourceUnavailable
perceivedSeverity: Minor (DMA)
Alarm Description A maintenance audit freed an SBL that remained in the AUTO-MSDstate following a restart, reload, reboot or a takeover. A maintenanceaudit consists of an autonomous disable followed by an initialize. If theInitialize command fails, the device is FLT.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - - -
104 / 533 3BK 20918 AAAA PCZZA Ed.06
7 Class 38: X.25 Alarms
7.4.1 Corrective Actions
[38,251] AUDIT
yes
Alarm persists?
no
ContactSystem Support
Lock X.25
On−site
Replace suspected X.25 RIT
TestX.25
VerifyX.25
Unlock X.25
Alarmsolved
yes
Alarm persists?
no
Figure 27: AUDIT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 105 / 533
7 Class 38: X.25 Alarms
106 / 533 3BK 20918 AAAA PCZZA Ed.06
8 Class 39: BSC-SW-ANOMALY Alarms
8 Class 39: BSC-SW-ANOMALY Alarms
This section defines the BSC alarms for the Class 39: BSC-SW-ANOMALYalarm class.
3BK 20918 AAAA PCZZA Ed.06 107 / 533
8 Class 39: BSC-SW-ANOMALY Alarms
8.1 [39,1] OSN-NONRECOVERABLE
specificProblems: OSN-NONRECOVERABLE
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Warning (MI)
Alarm Description If the function call is not accepted by the OS, then an OSN NonRecoverable Error is generated. The error handler receives a OSNnon-recoverable error. This triggers a processor restart.
Impact on System The SBL state remains unchanged.
The impact depends on the processor type. See Processor Restart[33,0].
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
8.1.1 Corrective Actions
Contact your Alcatel system support so the cause of the error can be examined.The information must be analyzed by qualified personnel using the sequencenumber and the user data. The meaning of the user sequence number and theuser data is different for every module.
108 / 533 3BK 20918 AAAA PCZZA Ed.06
8 Class 39: BSC-SW-ANOMALY Alarms
8.2 [39,3] OSN-PROCEDURAL
specificProblems: OSN-PROCEDURAL
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Warning (MI)
Alarm Description An application request of an OSN primitive was passed to the stackwith incorrect parameters.
Impact on System The SBL state remains unchanged
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
8.2.1 Corrective Actions
Contact your Alcatel system support so the cause of the error can be examined.The information must be analyzed by qualified personnel using the sequencenumber and the user data. The meaning of the user sequence number and theuser data is different for every module.
3BK 20918 AAAA PCZZA Ed.06 109 / 533
8 Class 39: BSC-SW-ANOMALY Alarms
8.3 [39,4] OSN-RECOVERABLE
specificProblems: OSN-RECOVERABLE
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Warning (MI)
Alarm Description The OSN reported a recoverable error. A functionally incorrect OSNprimitive application was requested. The processor is not restarted.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
8.3.1 Corrective Actions
Contact your Alcatel system support so the cause of the error can be examined.The information must be analyzed by qualified personnel using the sequencenumber and the user data. The meaning of the user sequence number and theuser data is different for every module.
110 / 533 3BK 20918 AAAA PCZZA Ed.06
8 Class 39: BSC-SW-ANOMALY Alarms
8.4 [39,5] USER-NONRECOVERABLE
specificProblems: USER-NONRECOVERABLE
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Warning (MI)
Alarm Description An application has generated a software error indicating a fault whichdoes not cause a malfunction. Subsequently, further errors havebeen detected which cause the software to malfunction, a User NonRecoverable Error is generated. The processor is restarted.
Impact on System The SBL state remains unchanged.
The impact depends on the processor type. See Processor Restart[33,0].
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
8.4.1 Corrective Actions
Contact your Alcatel system support so the cause of the error can be examined.The information must be analyzed by qualified personnel using the sequencenumber and the user data. The meaning of the user sequence number and theuser data is different for every module.
3BK 20918 AAAA PCZZA Ed.06 111 / 533
8 Class 39: BSC-SW-ANOMALY Alarms
8.5 [39,6] USER-RECOVERABLE
specificProblems: USER-RECOVERABLE
eventType: ProcessingError
probableCause: SoftwareError
perceivedSeverity: Warning (MI)
Alarm Description An application generated a software error indicating a fault that has nofurther operational effect.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
8.5.1 Corrective Actions
Contact your Alcatel system support so the cause of the error can be examined.The information must be analyzed by qualified personnel using the sequencenumber and the user data. The meaning of the user sequence number and theuser data is different for every module.
112 / 533 3BK 20918 AAAA PCZZA Ed.06
8 Class 39: BSC-SW-ANOMALY Alarms
8.6 [39,7] HWR-NONRECOVERABLE
specificProblems: HWR-NONRECOVERABLE
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Warning (MI)
Alarm Description The error handler received information concerning a hardwarenon-recoverable error.
Impact on System The SBL state remains unchanged.
The impact depends on the processor type. See Processor Restart[33,0].
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
8.6.1 Corrective Actions
Contact your Alcatel system support so the cause of the error can be examined.The information must be analyzed by qualified personnel using the sequencenumber and the user data. The meaning of the user sequence number and theuser data is different for every module.
3BK 20918 AAAA PCZZA Ed.06 113 / 533
8 Class 39: BSC-SW-ANOMALY Alarms
8.7 [39,18] SANITY-TIMER
specificProblems: SANITY-TIMER
eventType: ProcessingError
probableCause: softwareProgramAbnormallyTerminated
perceivedSeverity: Warning (MI)
Alarm Description A hardware sanity timer NMI expired. This is because an applicationhas run too long or is running in a loop. This causes the processor toreload.
Impact on System Expiration of the sanity timer caused a processor reload. All ongoingtransactions through the processors are released in a controlledmanner towards the MSC, with WTC.
The impact depends on the processor type. See Processor Restart[33,0].
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s)
Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
8.7.1 Corrective Actions
Contact your Alcatel system support so the cause of the error can be examined.The information must be analyzed by qualified personnel using the sequencenumber and the user data. The meaning of the user sequence number and theuser data is different for every module.
114 / 533 3BK 20918 AAAA PCZZA Ed.06
9 Class 42: TELECOM Alarms
9 Class 42: TELECOM Alarms
This section defines the BSC alarms for the Class 42: TELECOM alarm class.
3BK 20918 AAAA PCZZA Ed.06 115 / 533
9 Class 42: TELECOM Alarms
9.1 [42,1] NACK-MSC
specificProblems: NACK-MSC
eventType: Communication
probableCause: ResponseTimeExcessive
perceivedSeverity: Warning (MI)
Alarm Description The BSC did not receive a RESET ACK message from the MSC beforeexpiration of timer T4.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
The BSC repeats the reset procedure indefinitely until the MSC sendsa positive acknowledgment.
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
116 / 533 3BK 20918 AAAA PCZZA Ed.06
9 Class 42: TELECOM Alarms
9.1.1 Corrective Actions
[42,1] NACK−MSC
yesRESET and RESET_ACK message events?
no
Alarmsolved
Alarm persists?
no
ContactSystem Support
yes
Repair/replace N7 component
Solve that alarm(s) first
N7 alarm events?yes
no
On−site
Figure 28: NACK-MSC: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 117 / 533
9 Class 42: TELECOM Alarms
9.2 [42,2] OVERLOAD-MSC
specificProblems: OVERLOAD-MSC
eventType: QualityOfService
probableCause: Congestion
perceivedSeverity: Warning (MI)
Alarm Description An overload message was received from the MSC and this triggeredan overload reaction.
While timer T5 remains activated after receipt of an overload message,it inhibits the effect of any further overload messages. When timer T5expires, overload messages provoke traffic reduction again.
Impact on System The SBL state remains unchanged.
Traffic is reduced; at least one user class is barred in all cells.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s)
Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - -
9.2.1 Corrective Actions
None – an autonomous overload reaction is triggered.
118 / 533 3BK 20918 AAAA PCZZA Ed.06
9 Class 42: TELECOM Alarms
9.3 [42,3] START-RESET
specificProblems: START-RESET
eventType: QualityOfService
probableCause: PerformanceDegraded
perceivedSeverity: Warning (MI)
Alarm Description A reset procedure has started in the BSC. The alarm indicates whetherthe reset is requested by the MSC, or if the reset was due to loss ofcommunication with the MSC, (i.e., timer TI expired in the BSC).
Impact on System The SBL state remains unchanged.
All calls are cleared in the BSC.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 119 / 533
9 Class 42: TELECOM Alarms
9.3.1 Corrective Actions
Operator at OMC-R
[42,3] START−RESET
Alarmsolved
Alarm persists?
no
ContactSystem Support
yes
Trigger action on MSC side
Solve that alarm(s) first
Local communication alarm events?
yes
no
Figure 29: START-RESET: Corrective Actions
120 / 533 3BK 20918 AAAA PCZZA Ed.06
9 Class 42: TELECOM Alarms
9.4 [42,7] NO-RESET-CIC
specificProblems: NO-RESET-CIC
eventType: Communication
probableCause: ResponseTimeExcessive
perceivedSeverity: Warning (MI)
Alarm Description The BSC requested the reset of a CIC towards the MSC. This reset requestis attempted a predefined number of times. If, following the maximum numberof retries, the BSC still has not received the RESET CIC ACK, then thisalarm is issued.
Impact on System The SBL state remains unchanged.
This A-channel is released internally by the BSC.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s)
Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - -
3BK 20918 AAAA PCZZA Ed.06 121 / 533
9 Class 42: TELECOM Alarms
9.4.1 Corrective Actions
[42,7] NO−RESET−CIC
Alarmsolved
Alarm persists?
no
ContactSystem Support
yes
Trigger CIC recovery action at MSC side
Solve that alarm(s) first
Transmission or trunk alarm events?
yes
no
Figure 30: NO-RESET-CIC: Corrective Actions
122 / 533 3BK 20918 AAAA PCZZA Ed.06
9 Class 42: TELECOM Alarms
9.5 [42,9] OVERLOAD-BSC
specificProblems: OVERLOAD-BSC
eventType: Equipment
probableCause: ProcessorProblem
perceivedSeverity: Major (PMA)
Alarm Description This alarm is sent by the BSC to report an BSC processor overload.
Impact on System The SBL state remains unchanged
The BSC is overloaded.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - -
9.5.1 Corrective Actions
[42,9] OVERLOAD−BSC
ContactSystem Support
Solve that alarm(s) first
Processor related board alarm
events?
yes
no
Figure 31: OVERLOAD-BSC: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 123 / 533
9 Class 42: TELECOM Alarms
9.6 [42,12] TEL-PAIR-LOST
specificProblems: TEL-PAIR-LOST
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Critical (VPMA)
Alarm Description Sent by the BSC to report the loss of a TCH-DTC pair.
Alarm Number This is the ID of the TCH-DTC pair lost.
Impact on System The SBL state remains unchanged.
Since the TCH-DTC pair handles calls, there is a degradation in thecall handling facilities of the BSC.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - -
124 / 533 3BK 20918 AAAA PCZZA Ed.06
9 Class 42: TELECOM Alarms
9.6.1 Corrective Actions
[42,12] TEL−PAIR−LOST
yes
Alarm persists?
no
ContactSystem Support
Lock reported DTC
On−site
Replacereported faulty DTC
Testreported DTC
Verifyreported DTC
Unlock reported DTC
Alarmsolved
yes
Alarm persists?
no
Figure 32: TEL-PAIR-LOST: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 125 / 533
9 Class 42: TELECOM Alarms
9.7 [42,13] BSC-TRAFFIC-REPORT
specificProblems: BSC-TRAFFIC-REPORT
eventType: QualityOfService
probableCause: Congestion
perceivedSeverity: Warning (MI)
Alarm Description Sent by the BSC when:
An MSC_OVERLOAD/BSC_OVERLOAD is received and no BSSactions are running
An MSC_OVERLOAD/BSC_OVERLOAD is received and BSS
actions are running, but filter timer T17 is not running
Following a system action: SW activate, BSC restart, the traffic hasbeen reduced and is now increased step by step at each expiry of
timer T18.
The RACH parameters are changed on the system level (BSS
RACH).
Impact on System The SBL state remains unchanged.
MSs belonging to the barred access classes can no longer accessthe system.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
126 / 533 3BK 20918 AAAA PCZZA Ed.06
9 Class 42: TELECOM Alarms
9.7.1 Corrective Actions
[42,13] BSC−TRAFFIC−REPORT
Alarmsolved
Alarm persists?
no
ContactSystem Support
yes
Analyze additional information bytes
Solve that alarm(s) first
Related alarm events?
yes
no
Figure 33: BSC-TRAFFIC-REPORT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 127 / 533
9 Class 42: TELECOM Alarms
9.8 [42,14] GPRS-RESET
specificProblems: GPRS-RESET
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description This alarm is used when a RESET command arrives from the MFS orwhen all GSL, all GPRS application process or TCH-RM pairs aredown. A RESET can also occur in the case of an excessive amount oflack of acknowledgments between the MFS and the BSC.
Impact on System The SBL state remains unchanged.
A reset of the MFS affects GPRS functionality only.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) MFS Signaling MFS CallHandling
MFS O&M;Capabilities
Loss - -
Degradation - - - - -
9.8.1 Corrective Actions
None – an autonomous reset is triggered.
128 / 533 3BK 20918 AAAA PCZZA Ed.06
10 Class 43: CELL Alarms
10 Class 43: CELL Alarms
This section defines the BSC alarms for the Class 43: CELL alarm class.
3BK 20918 AAAA PCZZA Ed.06 129 / 533
10 Class 43: CELL Alarms
10.1 [43,0] LOSS-OF-BCCH
specificProblems: LOSS-OF-BCCH
eventType: QualityOfService
probableCause: PerfomanceDegraded
perceivedSeverity: Major (PMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description The transceiver time slot configured to carry the BCCH is unavailablefor telecommunication purposes.
Impact on System A BCCH must exist for each cell in order to transmit system informationto the MS. This enables the MS to assign calls within the cell. Sincethe BCCH is no longer able to transmit system information, calls arenot assigned in the cell.
A BCCH channel can be lost when equipment carrying a BCCHfails or is disabled. The BTS-TEL is FIT and a three-minute timer isstarted to allow the Frame Unit to reload. If the Frame Unit is reloadedsuccessfully, then BTS-TEL goes to IT; otherwise BTS-TEL goes toFLT.
Since the BCCH is a vital resource, recovery must be attempted.Recovery involves reconfiguration of another channel as a BCCH, atthe expense of the current configuration of the channel. Recoverymeans blocking/unblocking action, state update and perhaps areconfiguration action (if redundant resources are available). When theBCCH is recovered, another alarm is generated for the lost channelinvolved in the reconfiguration.
When the Loss of BCCH alarm is active, no other cell type alarmis sent for this cell to indicate further loss or gain of channels. Thiscontinues unless the BCCH channel becomes available.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
130 / 533 3BK 20918 AAAA PCZZA Ed.06
10 Class 43: CELL Alarms
10.1.1 Corrective Actions
[43,0] BSC−TRAFFIC−REPORT
Alarmsolved
Alarm persists?
no
ContactSystem Support
yes
Analyze additional information bytes
Trigger maintenance action on that alarm(s)
RelatedBTS alarm events?
yes
no
Figure 34: LOSS-OF-BCCH: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 131 / 533
10 Class 43: CELL Alarms
10.2 [43,1] LOSS-OF-SDCCH
specificProblems: LOSS-OF-SDCCH
eventType: QualityOfService
probableCause: PerfomanceDegraded
perceivedSeverity: Minor (DMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description One or more transmission time slots configured to carry the SDCCHare unavailable for telecommunication purposes.
Impact on System Loss of the SDCCH leads to a decrease in call setup and handovercapacity, fewer numbers of SDCCHs are available to handle call setupand handover.
SDCCH channels can be lost for one of the following reasons:
Equipment carrying an SDCCH fails or is disabled
An SDCCH might be lost due to a successful recovery of a BCCH,the configuration of the failing control channel TRX. TS is changed
to SDCCH.
Since the SDCCH is a vital resource, recovery must be attempted.This involves reconfiguration of another channel as an SDCCH, at theexpense of the current configuration of the channel. Recovery meansblocking/unblocking action, state update and perhaps a reconfigurationaction (if redundant resources are available). When the SDCCH isrecovered, another alarm is generated for the lost channel involved inthe reconfiguration.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - -
132 / 533 3BK 20918 AAAA PCZZA Ed.06
10 Class 43: CELL Alarms
10.2.1 Corrective Actions
[43,1] LOSS−OF−SDCCH
Alarmsolved
Alarm persists?
no
ContactSystem Support
yes
Analyze additional information bytes
Trigger maintenance action on that alarm(s)
RelatedBTS alarm
events?
yes
no
Figure 35: LOSS-OF-SDCCH: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 133 / 533
10 Class 43: CELL Alarms
10.3 [43,2] LOSS-OF-TCH
specificProblems: LOSS-OF-TCH
eventType: QualityOfService
probableCause: PerfomanceDegraded
perceivedSeverity: Minor (DMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description One or more transceiver time slots configured to carry the TCH areunavailable for telecommunication purposes.
Impact on System Loss of a TCH leads to a decrease in traffic capacity as there are feweravailable TCHs to carry calls.
A TCH might be lost due to a successful recovery of the TRX/TCUwhere the TCH channels are configured.
The loss of TCHs channels activates only the blocking part of recovery,with no reconfiguration.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - -
134 / 533 3BK 20918 AAAA PCZZA Ed.06
10 Class 43: CELL Alarms
10.3.1 Corrective Actions
[43,2] LOSS−OF−TCH
Alarmsolved
Alarm persists?
no
ContactSystem Support
yes
Analyze additional information bytes
Trigger maintenance action on that alarm(s)
RelatedBTS alarm
events?
yes
no
Figure 36: LOSS-OF-TCH: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 135 / 533
10 Class 43: CELL Alarms
10.4 [43,3] LOSS-OF-ALL-CHAN
specificProblems: LOSS-OF-ALL-CHAN
eventType: QualityOfService
probableCause: PerfomanceDegraded
perceivedSeverity: Major (PMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description All transceiver time slots of a BTS are unavailable for telecommunicationpurposes.The alarm condition is a begin or an end, never an event.
This alarm is generated in the following circumstances:
The BTS-TEL goes to FLT due to a configuration failure, (i.e.,
BTS-OM = FLT)
All the RSLs go faulty, SBL BTS-TEL is set to FLT.
Loss of all channels can also result from the BTS-OM link becomingFLT/FOS. This causes the BTS-TEL to go to FLT when configurationdata is sent to the BTS.
Impact on System All channels in the cell are unavailable. If configuration data cannot besent to the BTS, or BTS-TEL is FLT, the cell is barred. A Mobile Stationnever selects this cell for call setup; there is no call handling in the cell.
When the BCCH alarm is active no other cell type alarm is sent for thiscell to indicate further loss or gain of channels. This continues unlessthe BCCH channel becomes available.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
136 / 533 3BK 20918 AAAA PCZZA Ed.06
10 Class 43: CELL Alarms
10.4.1 Corrective Actions
[43,3] LOSS−OF−ALL−CHAN
Alarmsolved
Alarm persists?
no
ContactSystem Support
yes
LockBTS−OM
Trigger maintenance action on that
alarm(s)
Related BTS alarm events?
yes
no
UnlockBTS−OM
All RSLs in BTS faulty?
yes
no
RESET BTS for reconfiguration
Figure 37: LOSS-OF-ALL-CHAN: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 137 / 533
10 Class 43: CELL Alarms
10.5 [43,4] CELL-TRAFFIC-REPORT
specificProblems: CELL-TRAFFIC-REPORT
eventType: QualityOfService
probableCause: PerfomanceDegraded
perceivedSeverity: Warning (MI)
Alarm Description Sent by the BSC when:
A BTS_OVERLOAD message is received from a BCCH transceiver
A BTS_OVERLOAD message is received from a non-BCCHtransceiver and the leaky-bucket counter overflows
A TCU processor overload is detected
There is a change of the RACH parameters on cell level (dynamicRACH).
Impact on System The SBL state remains unchanged.
MSs belonging to the barred access classes can no longer accessthe system.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
138 / 533 3BK 20918 AAAA PCZZA Ed.06
10 Class 43: CELL Alarms
10.5.1 Corrective Actions
[43,4] CELL−TRAFFIC−REPORT
Alarmsolved
Alarm persists?
ContactSystem Support
yes
Analyze additional information bytes
Trigger maintenance action on that alarm(s)
Related BTS alarm events?
yes
no
BTS−OVERLOAD alarm coming
from BCCH TRX?
yes
no
ReduceBTS load
Solve that alarm(s)
TCU processor overload
alarm events?*
yes
Correct RACH parameters
Dynamic RACH parameters on
cell level OK?
no
no
yes
no
Figure 38: CELL-TRAFFIC-REPORT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 139 / 533
10 Class 43: CELL Alarms
10.6 [43,5] OVERLOAD-BTS
specificProblems: OVERLOAD-BTS
eventType: QualityOfService
probableCause: Congestion
perceivedSeverity: Warning (MI)
Alarm Description Sent by the BSC to report a change in the overall BTS telecom activity.It is sent when a BTS_OVERLOAD message is received and the timerT1 is not running.
Impact on System The SBL state remains unchanged.
MSs belonging to the barred access classes can no longer accessthe system.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
140 / 533 3BK 20918 AAAA PCZZA Ed.06
10 Class 43: CELL Alarms
10.6.1 Corrective Actions
[43,5] OVERLOAD−BTS
Alarmsolved
Alarm persists?
no
ContactSystem Support
yes
Trigger maintenance action on that
alarm(s)
RelatedBTS alarm
events?
yes
no
Solve that alarm(s)
TCU alarm events?
yes
no
Figure 39: OVERLOAD-BTS: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 141 / 533
10 Class 43: CELL Alarms
10.7 [43,248] CONFIGURED POOLS NOT [FULLY] USABLE
specificProblems: CONFIGURED POOLS NOT [FULLY] USABLE
eventType: QualityOfService
probableCause: PerformanceDegraded
perceivedSeverity: Minor (DMA)
Alarm Description Cell is degraded, in HSDS at least one EXTS is lost.
This problem can be caused by one of the following:
Any pool mapped to non-IT second Abis, HSDS state is changedto ’Degraded’
Any pool mapped to non-IT TCU, HSDS state is changed to
’Degraded’
There is at least one pool that is left unmapped, HSDS state is
changed to ’Partially Degraded’
There is at least one pool of type greater than 2 which is linked to aEvolium A9100 TRE, the pool has to be truncated. HSDS state is
changed to ’Partially Degraded’.
The alarm is independent of the fact that HSDS is activated or not.
Impact on System No impact on BTS_TEL.
If HSDS state is ’Degraded’, this cell cannot support the HSDS(EGPRS); the running PS in EGPRS is degraded to GPRS.
If HSDS state is ’Partially Degraded’, this cell still supports the HSDS.
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M Capabilities
Loss - - - - -
Degradation - - - -
142 / 533 3BK 20918 AAAA PCZZA Ed.06
10 Class 43: CELL Alarms
10.7.1 Corrective Actions
HSDS state is degraded?
TCU that any pool
mapped to is IT?
Alarm persists?
[43,248] CONFIGURED POOLS NOT [FULLY] USABLE
None
Check the second Abis that any
pools mapped to
Check for TCU problem
Contact System Support
Alarm solved
yes
no
yes
yes
no
no
Figure 40: CONFIGURED POOLS NOT [FULLY] USABLE: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 143 / 533
10 Class 43: CELL Alarms
144 / 533 3BK 20918 AAAA PCZZA Ed.06
11 Class 44: BTS-OM Alarms
11 Class 44: BTS-OM Alarms
This section defines the BSC alarms for the Class 44: BST-OM alarm class.
3BK 20918 AAAA PCZZA Ed.06 145 / 533
11 Class 44: BTS-OM Alarms
11.1 [44,0] AUDIT-FAIL
specificProblems: AUDIT-FAIL
eventType: Communication
probableCause: CommunicationSubsystemFailure
perceivedSeverity: Minor (DMA)
Alarm Description A failure occurs in the BSC-BTS audit. A failure in the BSC-BTS Auditscenario is considered to be any failure occurring between the requestfor an Audit from the BSC and reception of the Conf_compl messagefrom the BTS. This Alarm is never sent as a result of no receptionof ’An ACK’.
This alarm is also sent when CDM sending fails in cases NOT undersoftware activation and reconfiguration, i.e. OMU restart, CDM sendingon logical data change, etc.
Impact on System When BTS-OM is FLT but OML is up, the BSC triggers an audit everytwo minutes until one succeeds. The BTS still handles calls, but if areconfiguration occurs and the BTS-OM is FLT, BTS-TEL goes to FLT.
The message ’OMU started’, indicating that the BTS (OMU) hasauto-reset, can result in a new BTS/OMU downloading scenario. In theevent of a successful download, the BTS-OM becomes IT.
When the BTS-OM goes from FLT to IT due to success of a BSC-BTSaudit, or reset BTS/OMU, an alarm ’END’ for all alarm types ’auditfailure’ is sent.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - - - -
146 / 533 3BK 20918 AAAA PCZZA Ed.06
11 Class 44: BTS-OM Alarms
11.1.1 Corrective Actions
[44,0] AUDIT−FAIL
Alarmsolved
Alarm persists?
no
ContactSystem Support
yes
Reset BTS or OML TCU
OML up?yesno No operator
action required
Figure 41: AUDIT-FAIL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 147 / 533
11 Class 44: BTS-OM Alarms
11.2 [44,1] PROTOCOL-FAIL
specificProblems: PROTOCOL-FAIL
eventType: Communication
probableCause: CommunicationProtocolError
perceivedSeverity: Minor (DMA)
Alarm Description A protocol failure on the Abis interface occurred. An ’ACK’ to somemessage was not received after three retries.
Impact on System When the BTS-OM is FLT but OML is up, the BSC triggers an auditevery two minutes until one succeeds. The BTS still handles calls, butif a reconfiguration occurs and BTS-OM is FLT, BTS-TEL goes to FLT.
The message ’OMU started’, indicating that the BTS (OMU) has autoreset, can result in a new BTS/OMU download scenario. In the eventof a successful download, the BTS-OM becomes IT.
When the BTS-OM goes from FLT to IT due to success of a BSC-BTSaudit, or BTS/OMU reset, an ’END’ for all alarm types ’protocol failure’is sent.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - - -
11.2.1 Corrective Actions
[44,1] PROTOCOL−FAIL
Alarmsolved
Alarm persists?
no ContactSystem Support
yes
Reset BTS or OML TCU
OML up?yesno No operator
action required
Figure 42: PROTOCOL-FAIL: Corrective Actions
148 / 533 3BK 20918 AAAA PCZZA Ed.06
11 Class 44: BTS-OM Alarms
11.3 [44,2] RECONFIG-FAIL
specificProblems: RECONFIG-FAIL
eventType: ProcessingError
probableCause: ConfigurationOrCustomizationError
perceivedSeverity: Minor (DMA)
Alarm Description This alarm is sent as a result of a failure to do a required reconfigurationaction, triggered due to loss of vital resources or due to failure inconveying CDM to the BTS.
Impact on System When the BTS-OM is FLT but OML is up, the BSC triggers an auditevery two minutes until one succeeds. The BTS still handles calls, butif a reconfiguration occurs and BTS-OM is FLT, BTS-TEL goes to FLT.
The message ‘OMU started’, indicating that BTS (OMU) hasauto-reset, can result in a new BTS/OMU download scenario. In theevent of a successful download, the BTS-OM becomes IT.
When BTS-OM goes from FLT to IT due to success of a BSC-BTSaudit, or BTS/OMU reset, an alarm ’END’ for all alarm types’Reconfig_failure’ is sent.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 149 / 533
11 Class 44: BTS-OM Alarms
11.3.1 Corrective Actions
[44,2] RECONFIG−FAIL
Alarmsolved
Alarm persists?
no
ContactSystem Support
yes
Reset BTS or OML TCU
OML up?
yes
no
No operator action required
Figure 43: RECONFIG-FAIL: Corrective Actions
150 / 533 3BK 20918 AAAA PCZZA Ed.06
11 Class 44: BTS-OM Alarms
11.4 [44,3] DOWNLOAD-FAIL
specificProblems: DOWNLOAD-FAIL
eventType: ProcessingError
probableCause: ConfigurationOrCustomizationError
perceivedSeverity: Minor (DMA)
Alarm Description Three download attempts failed. Any failure fromBTS-DOWNLOAD-REQ until a successful BTS-DOWNLOAD-REPis considered a download failure.
Impact on System The OMU updates the BTS-OM to FOS after three download attemptsby the BSC have failed (i.e., BTS-DOWNLOAD-REQ until a successfulBTS-DOWNLOAD-REP).
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 151 / 533
11 Class 44: BTS-OM Alarms
11.4.1 Corrective Actions
[44,3] DOWNLOAD−FAIL
Alarm persists?
no
ContactSystem Support
yes
Check files on standby CPR disk
BTS or OMU restart events?
yes
no
Lock BTS−OM
Unlock BTS−OM
Reload correct data file from software package
Data files on standby CPR
disk ok?
yes
no
Alarmsolved
Alarm persists?
no
yes
Figure 44: DOWNLOAD-FAIL: Corrective Actions
152 / 533 3BK 20918 AAAA PCZZA Ed.06
11 Class 44: BTS-OM Alarms
11.5 [44,5] SW-ACTIVATE-FAIL
specificProblems: SW-ACTIVATE-FAIL
eventType: ProcessingError
probableCause: ConfigurationOrCustomizationError
perceivedSeverity: Minor (DMA)
Alarm Description This configuration failure alarm indicates that a software activationfailed following a download attempt.
Impact on System If the software activation failure requires operator intervention, BTS-OMgoes to FOS. Otherwise, it goes to FLT.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s)
Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 153 / 533
11 Class 44: BTS-OM Alarms
11.5.1 Corrective Actions
[44,5] SW−ACTIVATE−FAIL
Alarmsolved
Alarm persists?
no
ContactSystem Support
yes
Correct BTS hardware or CPR hawrdware data
BTS hardware corresponds to hardware
data on standby CPR disk?
yes
no
Lock BTS−OM
Unlock BTS−OM
Alarm persists?
no
yes
Figure 45: SW-ACTIVATE-FAIL: Corrective Actions
154 / 533 3BK 20918 AAAA PCZZA Ed.06
11 Class 44: BTS-OM Alarms
11.6 [44,6] CONFIG-DATA-FAIL
specificProblems: CONFIG-DATA-FAIL
eventType: ProcessingError
probableCause: ConfigurationOrCustomizationError
perceivedSeverity: Minor (DMA)
Alarm Description There is a problem with the configuration data because of a logicalparameter modification or the restart of the BTS or OMU.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 155 / 533
11 Class 44: BTS-OM Alarms
11.6.1 Corrective Actions
[44,6] CONFIG−DATA−FAIL
Alarmsolved
Alarm persists?
no
ContactSystem Support
yes
ContactSystem Support
BTS/OMU restarts?
Data files on standby CPR
disk ok?
yes
no
Logical parametersmodified?
no
yes
Logical parameters are valid?
no
yes
Reload correct data file from software package
yes
no
Lock BTS−OM
Unlock BTS−OM
Figure 46: CONFIG-DATA-FAIL: Corrective Actions
156 / 533 3BK 20918 AAAA PCZZA Ed.06
11 Class 44: BTS-OM Alarms
11.7 [44,7] OMU-SELFTEST-FAIL
specificProblems: OMU-SELFTEST-FAIL
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Minor (DMA)
Alarm Description The OMU failed its self-test.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 157 / 533
11 Class 44: BTS-OM Alarms
11.7.1 Corrective Actions
[44,7] OML−SELFTEST−FAIL
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
Lock BTS−OM
On−site
G2: Replacereported faulty OMU
Unlock BTS−OM
Alarmsolved
yes
Alarm persists?
no
Figure 47: OMU-SELFTEST-FAIL: Corrective Actions
158 / 533 3BK 20918 AAAA PCZZA Ed.06
11 Class 44: BTS-OM Alarms
11.8 [44,10] ABORT-FAIL
specificProblems: ABORT-FAIL
eventType: ProcessingError
probableCause: ConfigurationOrCustomizationError
perceivedSeverity: Minor (DMA)
Alarm Description The Abort failure alarm indicates that the attempt to remove thepreloaded BTS software files has failed.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
11.8.1 Corrective Actions
[44,10] ABORT−FAIL
ContactSystem Support
Retrigger remove action
Alarmsolved
yes
Alarm persists?
no
Figure 48: ABORT-FAIL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 159 / 533
11 Class 44: BTS-OM Alarms
11.9 [44,11] PRELOAD-FAIL
specificProblems: PRELOAD-FAIL
eventType: ProcessingError
probableCause: ConfigurationOrCustomizationError
perceivedSeverity: Minor (DMA)
Alarm Description This alarm indicates that preloading of the BTS software has failed.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
11.9.1 Corrective Actions
Figure 49: PRELOAD-FAIL: Corrective Actions
160 / 533 3BK 20918 AAAA PCZZA Ed.06
11 Class 44: BTS-OM Alarms
11.10 [44,12] BTS-HW-CONFIG-FAIL
specificProblems: BTS-HW-HW-CONFIG-FAIL
eventType: ProcessingError
probableCause: ConfigurationOrCustomizationError
perceivedSeverity: Minor (DMA)
Alarm Description This alarm indicates that the BTS extension/reduction has failed due arestriction in the BTS-HW. During an audit, added or removed TREsare detected and reported to the BSC. If the ’Auto-alloc’ flag is set onthe Abis, the BSC will attempt to allocate TCUs and TSs. This can fail,if the BTS is created with certain characteristics and the BTS cannotsupport these characteristics.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
11.10.1 Corrective Actions
[44,12] BTS−HW−CONFIG−FAIL
ContactSystem Support
Correct characteristics
BTS characteristic
correspond to BTS HW capabilities
files?
yes
no
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Figure 50: BTS-HW-CONFIG-FAIL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 161 / 533
11 Class 44: BTS-OM Alarms
G2 BTS BTS A9100
BIUMD SMBI SMFG SUME
QMUX-TS [0,6,2] [1..31,0,2] [0,6,2][1..31,0/2/4/6,2]
[0,6,2][1..31,0/2/4/6,2]
[0,6,2][1..31,0/2/4/6,2]
R-TS [1..31,0, 4/8]* [1..31,0,4/8] [1..31,0,4/8] [1..31,0,4/8]
S-TS [0,3,2] [15,4,2]*[17,4,2]*
[0,6,2][1..31,0/2/4/6,2]
[0,6,2][1..31,0/2/4/6,2]
[0,6,2][1..31,0/2/4/6,2]
Traffic channel any mapping any mapping any mapping any mapping
Topology chain/ring chain/ring chain/ring chain/ring
x-connect table allowed but onlyin chain and w/oRC-TS
allowed but onlyin chain and w/oRC-TS
allowed but onlyin chain and w/oRC-TS
allowed but onlyin chain and w/oRC-TS
usable- TS allowed allowed allowed allowed
auto-alloc allowed allowed allowed allowed
MUX Rule MUX Rule = NoMUX only allowed
Any MUX Rule allowed
MUX Rate MUX Rate =MUX-rate-BTS onlyallowed
Any MUX Rateallowed
[x,y,z] means TS x, bit y (numbered from 0 to 7) and length z. * Can only be mapped on a free channel.
Table 5: NE Hardware Restrictions
SMBI SMBI
SMFG MBEG or MBLG or MBL1G or MBL1D or
SUME SUMP
Table 6: NE Hardware RIT Mapping
162 / 533 3BK 20918 AAAA PCZZA Ed.06
12 Class 45: CHANNEL Alarms
12 Class 45: CHANNEL Alarms
This section defines the BSC alarms for the Class 45: CHANNEL alarm class.
3BK 20918 AAAA PCZZA Ed.06 163 / 533
12 Class 45: CHANNEL Alarms
12.1 [45,0] CH-UNBLOCK-FAIL
specificProblems: CH-UNBLOCK-FAIL
eventType: Communication
probableCause: CommunicationProtocolError
perceivedSeverity: Minor (DMA)
Alarm Description A timeout expired for the MSC to send an acknowledgement to theBSC in response to an A-channel unblocking message.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - -
164 / 533 3BK 20918 AAAA PCZZA Ed.06
12 Class 45: CHANNEL Alarms
12.1.1 Corrective Actions
[45,0] CH−UNBLOCK−FAIL
Lock ACH Unlock ACH
ContactSystem Support
N7 links operational?
no
yes
Repair/replace N7 equipment
Trigger N7 checks at MSC side
Alarmsolved
Alarm persists?
no
yes
On−site
Alarmsolved
Alarm persists?
no
yes
Alarmsolved
Alarm persists?
no
yes
Figure 51: CH-UNBLOCK-FAIL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 165 / 533
12 Class 45: CHANNEL Alarms
12.2 [45,1] CH-BLOCK-FAIL
specificProblems: CH-BLOCK-FAIL
eventType: Communication
probableCause: CommunicationProtocolError
perceivedSeverity: Warning (MI)
Alarm Description A timeout expired for the MSC to send an acknowledgement to theBSC in response to an A-channel blocking message.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - -
166 / 533 3BK 20918 AAAA PCZZA Ed.06
12 Class 45: CHANNEL Alarms
12.2.1 Corrective Actions
[45,1] CH−BLOCK−FAIL
Lock ACH Unlock ACH
ContactSystem Support
N7 links operational?
no
yes
Repair/replace N7 equipment
Trigger N7 checks at MSC side
Alarmsolved
Alarm persists?
no
yes
On−site
Alarmsolved
Alarm persists?
no
yes
Alarmsolved
Alarm persists?
no
yes
Figure 52: CH-BLOCK-FAIL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 167 / 533
12 Class 45: CHANNEL Alarms
12.3 [45,2] BSC-CIC-UNKNOWN
specificProblems: BSC-CIC-UNKNOWN
eventType: ProcessingError
probableCause: ConfigurationOrCustomizationError
perceivedSeverity: Warning (MI)
Alarm Description This alarm is sent out in response to a request initiated by the BSCwhich specifies a circuit which is not equipped in the MSC.
On reception of an unequipped circuit message from the BSC, theMSC should remove the indicated circuits from further selection.
Impact on System The SBL state remains unchanged.
A database inconsistency exists which could cause problems at alater stage. This fault is for one A-channel, although there is a strongpossibility that faults exist on other A-channels at the A Interface. Onreception of an unequipped circuit message from the BSC, the MSCremoves the indicated circuits from further selection.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - -
168 / 533 3BK 20918 AAAA PCZZA Ed.06
12 Class 45: CHANNEL Alarms
12.3.1 Corrective Actions
[45,2] BSC−CIC−UNKNOWN
Lock assoc. A−trunk
Unlock assoc. A−trunk to bring ACH back in service,
as faults can exist for other A−channels on A−trunk
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Figure 53: BSC-CIC-UNKNOWN: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 169 / 533
12 Class 45: CHANNEL Alarms
12.4 [45,3] MSC-CIC-UNKNOWN
specificProblems: MSC-CIC-UNKNOWN
eventType: ProcessingError
probableCause: ConfigurationOrCustomizationError
perceivedSeverity: Warning (MI)
Alarm Description The MSC initiated a request. The request specifies a circuit which isunequipped in the BSC.
Impact on System The SBL state remains unchanged.
If the circuit indicated in the message is not equipped in the BSC, theBSC ignores the circuit. The BSC does not make any response to thecircuit and refuses the request for the resource.
A circuit is not equipped in the BSC if the:
Circuit is used for N7 Signaling
Circuit is unknown to the BSC
BSC knows the circuit but recognizes it as not equipped
DTC controlling the circuit is faulty and the response
MSC-CIC-UNKNOWN is not sent.
A database inconsistency exists which can cause problems at a laterstage. This fault is for one A-channel, although there is a strongpossibility that faults exist on other A-channels at the A Interface.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - -
170 / 533 3BK 20918 AAAA PCZZA Ed.06
12 Class 45: CHANNEL Alarms
12.4.1 Corrective Actions
[45,3] MSC−CIC−UNKNOWN
Lock aossc. A−trunk
Unlock assoc. A−trunk to bring ACH back in service,
as faults can exist for other A−channels on A−trunk
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Figure 54: MSC-CIC-UNKNOWN: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 171 / 533
12 Class 45: CHANNEL Alarms
12.5 [45,4] END-OF-REP-OF-UBLOCK-PROC
specificProblems: END-OF-REP-OF-UBLOCK-PROC
eventType: Communication
probableCause: CommunicationProtocolError
perceivedSeverity: Critical (VPMA)
Alarm Description The number of unblock requests exceeded a predefined number ofallowable attempts (i.e. 255).
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - -
12.5.1 Corrective Actions
[45,4] END−OF−REP−OF−UBLOCK−PROC
Lock aossc. ACH
Unlock assoc. A−trunk to bring ACH back in service,
as faults can exist for other A−channels on A−trunk
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Figure 55: END-OF-REP-OF-UBLOCK-PROC: Corrective Actions
172 / 533 3BK 20918 AAAA PCZZA Ed.06
12 Class 45: CHANNEL Alarms
12.6 [45,251] AUDIT
specificProblems: AUDIT
eventType: ProcessingError
probableCause: softwareProgramAbnormallyTerminated
perceivedSeverity: Minor (DMA)
Alarm Description An SBL which remained in an intermediate maintenance state(AUTO-MSD) following a restart, reload, reboot or a takeover wasfreed by a maintenance audit. A maintenance audit consists of anautonomous disable followed by an initialize. If the Initialize commandfails, the SBL is FLT.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s)
Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - -
3BK 20918 AAAA PCZZA Ed.06 173 / 533
12 Class 45: CHANNEL Alarms
12.6.1 Corrective Actions
[45,251] AUDIT
Lock aossc. A−channel
Unlock assoc. A−channel to bring ACH back in service,
as faults can exist for other A−channels on A−trunk
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
On−site
Replace suspected RIT
Alarmsolved
yes
Alarm persists?
no
Figure 56: AUDIT: Corrective Actions
174 / 533 3BK 20918 AAAA PCZZA Ed.06
13 Class 46: BACKUP-MEDIUM Alarms
13 Class 46: BACKUP-MEDIUM Alarms
This section defines the BSC alarms for the Class 46: BACKUP-MEDIUMalarm class.
3BK 20918 AAAA PCZZA Ed.06 175 / 533
13 Class 46: BACKUP-MEDIUM Alarms
13.1 [46,0] SYNC-CORRUPTED
specificProblems: SYNC-CORRUPTED
eventType: ProcessingError
probableCause: softwareProgramAbnormallyTerminated
perceivedSeverity: Warning (MI)
Alarm Description A processor restart has occurred before the twin fiIe is closed duringa twin update. The Active CPRA will detect that the twin file was notclosed properly before the report. The twin file status is changed tosynchronized corrupted and the alarm ’SYNC_CORR’ is generated.
Impact on System The SBL state remains unchanged.
Telecom functions are not affected, but PM is impacted.
CPRA (Duplex/Simplex) - Performance Management
When a twin file is being extended, the extended part is lost becausethe twin file was not properly closed. If the twin file is a PM file, the lastperformance information can be lost.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
13.1.1 Corrective Actions
None – wait for the next twin file update.
See Other BSC Alarms (Section 29.4) for the byte definition.
176 / 533 3BK 20918 AAAA PCZZA Ed.06
13 Class 46: BACKUP-MEDIUM Alarms
13.2 [46,1] UNSYNC-OTHER-CORR
specificProblems: UNSYNC-OTHER-CORR
eventType: ProcessingError
probableCause: softwareProgramAbnormallyTerminated
perceivedSeverity: Warning (MI)
Alarm Description This alarm occurs when the twin file on the own CPRA is not synchronized anda twin file update is successful on the own CPRA but failed on the other CPRA.The twin file status is changed to unsynchronized other corrupted and thealarm ’UNSYN_OTHER_C’ is generated.
Impact on System The SBL state remains unchanged.
Some previously acknowledged commands are lost.
CPRA (DUPLEX): Performance Management
Telecom functions are not affected, but PM is impacted.
If some updates are to be done on the active CPRA, then the standby CPRA issynchronized as fast as possible, although a small delay does exist. If a restartoccurs now on the active CPRA (database update was completely done), it ispossible that not all the updates are forwarded to the standby. The standbyCPRA now becomes active and detects that the data is not yet completelyavailable. The new active CPRA then tries to retrieve the missing data, from itsmate. This takes time, because it has to wait until its mate is running again.When this is done, the databases are again synchronized.
If, in the meantime, a database update arrives on a new active CPR, then thisupdate is done, although the missing data has still not been retrieved fromthe mate CPRA. This is necessary; otherwise all the applications are heldup until the mate CPRA is running. If the latter has a hard failure, it neverbecomes available. When the missing data is not retrieved from its mate,the database/disk subsystem generates an alarm ’unsync other corrupted’.It forces the new standby CPR to synchronize with the new active CPRA,whenever it comes on line. The missing data is lost and all other modified dataon the active CPRA is synchronized with the standby CPRA.
CPRA (SIMPLEX)
If the CPRA runs in simplex, this alarm is never issued.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - -
3BK 20918 AAAA PCZZA Ed.06 177 / 533
13 Class 46: BACKUP-MEDIUM Alarms
13.2.1 Corrective Actions
[46,1] UNSYNC−OTHER−CORR
Resynchronize OMC−R with BSC by
performing an audit
Repeat the lost transactions
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
Figure 57: UNSYNC-OTHER-CORR: Corrective Actions
Note: When duplex is in operation, the BSC manages synchronization betweenthe two disks. When an update cannot be performed on one disk (for example,due to a processor RESTART), the disks are temporarily unsynchronized. Aperiodic background task resynchronizes the disks every five minutes. If thesynchronization fails because of a hardware failure, the operator is informed byan alarm message.
178 / 533 3BK 20918 AAAA PCZZA Ed.06
13 Class 46: BACKUP-MEDIUM Alarms
13.3 [46,4] SECFILE-ROLLBACK
specificProblems: SEC-FILE-ROLLBACK
eventType: ProcessingError
probableCause: softwareProgramAbnormallyTerminated
perceivedSeverity: Warning (MI)
Alarm Description An open transaction was found in the security file during initialization.This means that a transaction requiring several updates of thedatabase was interrupted by a hardware fault, software fault, takeoveror a CPRA reload. The BSC performs a rollback of the transaction.
Impact on System The SBL state remains unchanged.
Telecom functions are not affected, but Configuration Managementis impacted.
Configuration Management
The interrupted transaction is lost as the BSC returned to itsprevious state. The OMC-R operator may have received a negativeacknowledgement to his request for the modification of a logicalparameter/action on software/database replacement.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - -
3BK 20918 AAAA PCZZA Ed.06 179 / 533
13 Class 46: BACKUP-MEDIUM Alarms
13.3.1 Corrective Actions
[46,4] SECFILE−ROLLBACK
Resynchronize OMC−R with BSC by
performing an audit
Repeat the lost transactions
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
yesNACKs
received on operator requests?
no
Repeat the operator request
Figure 58: SECFILE-ROLLBACK: Corrective Actions
180 / 533 3BK 20918 AAAA PCZZA Ed.06
13 Class 46: BACKUP-MEDIUM Alarms
13.4 [46,5] SINGLE-UPD-ROLLBACK
specificProblems: SINGLE-UPD-ROLLBACK
eventType: ProcessingError
probableCause: softwareProgramAbnormallyTerminated
perceivedSeverity: Warning (MI)
Alarm Description When a single update fails and security is requested, the application isinformed that the update failed and a rollback is done, to retrieve theold/original values.
If the rollback cannot be executed, then an alarm ’single rollbackfailure’ is generated.
Impact on System The SBL state remains unchanged.
This failure is also issued whenever the CPRA runs in simplex.
Telecom functions are not affected, but Configuration Managementis impacted.
Configuration Management
The interrupted transaction is lost as the BSC attempts to returnto its previous state. The OMC-R operator may have received anegative acknowledgement to his request for modification of logicalparameter/action on software/database replacement.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - -
3BK 20918 AAAA PCZZA Ed.06 181 / 533
13 Class 46: BACKUP-MEDIUM Alarms
13.4.1 Corrective Actions
[46,5] SINGLE−UPD−ROLLBACK
Re−trigger the update
Run Software/database with old DLS/values
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
yes
Alarm persists?
no Alarmsolved
Figure 59: SINGLE-UPD-ROLLBACK: Corrective Actions
182 / 533 3BK 20918 AAAA PCZZA Ed.06
13 Class 46: BACKUP-MEDIUM Alarms
13.5 [46,6] DUT-ROLLBACK-FAIL
specificProblems: DUT-ROLLBACK-FAIL
eventType: ProcessingError
probableCause: softwareProgramAbnormallyTerminated
perceivedSeverity: Warning (MI)
Alarm Description A series of database updates can be done simultaneously with anapplication and can start a ’data-update-transaction’. By this request,the security system is enabled and all the old/new database values arestored in a security file. This transaction is started and ended by theapplication. If the application receives a successful ’end of transaction’,then all the updates are correctly executed and consistent.
If something goes wrong during this transaction, then a rollback isexecuted over all the modified data relations. The user is informedabout the unsuccessful database updates.
If due to some reason, the user cannot be informed about this rollbackaction, then an alarm ’DUT_RLB_FAIL’ is generated.
When this failure occurs, the subsequent alarm will be generated whenthe CPRA runs in simplex.
Impact on System The SBL state remains unchanged.
Telecom functions are not affected.
Configuration Management
The interrupted transaction is lost as the BSC attempts to returnto its previous state. The OMC-R operator may have received anegative acknowledgement to his request for modification of logicalparameter/action on software/database replacement.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - -
3BK 20918 AAAA PCZZA Ed.06 183 / 533
13 Class 46: BACKUP-MEDIUM Alarms
13.5.1 Corrective Actions
[46,6] DUT−ROLLBACK−FAIL
Re−trigger the data update
ContactSystem Support
yes
Alarm persists?
no Alarmsolved
Figure 60: DUT-ROLLBACK-FAIL: Corrective Actions
184 / 533 3BK 20918 AAAA PCZZA Ed.06
13 Class 46: BACKUP-MEDIUM Alarms
13.6 [46,7] DISC-OOS
specificProblems: DISC-OOS
eventType: Equipment
probableCause: InputOutputDeviceError
perceivedSeverity: Minor (DMA)
Alarm Description During a restart/reload/reboot, the SSD on the standby S-CPRA or O-CPRAwas checked and found to be unformatted.
Impact on System Telecom functions are not affected.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - -
3BK 20918 AAAA PCZZA Ed.06 185 / 533
13 Class 46: BACKUP-MEDIUM Alarms
13.6.1 Corrective Actions
[46,7] DISC−OOS
yes
Alarm persists?
ContactSystem Support
Reformat SSD on S−CPRA
or O−CPRA
On−site
Replace suspected CPR
Copy all files from active to standby CPRA
Alarmsolved
yes
Alarm occurs often for a specific DISK?
no
no
Lock/unlock the disk from
OMC−R
Alarm persists?
yes
Alarmsolved
no
Figure 61: DISC-OOS: Corrective Actions
186 / 533 3BK 20918 AAAA PCZZA Ed.06
13 Class 46: BACKUP-MEDIUM Alarms
13.7 [46,8] DISC-PARITY-ERROR
specificProblems: DISC-PARITY-ERROR
eventType: Equipment
probableCause: InputOutputDeviceError
perceivedSeverity: Minor (DMA)
Alarm Description During a restart/reload/reboot, the SSD on the standby S-CPRA waschecked and a parity error was detected.
Impact on System Telecom functions are not affected.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
3BK 20918 AAAA PCZZA Ed.06 187 / 533
13 Class 46: BACKUP-MEDIUM Alarms
13.7.1 Corrective Actions
[46,8] DISC−PARITY−ERROR
yes
Alarm persists?
no
ContactSystem Support
Reformat SSD on S−CPRA
On−site
Replace suspected CPR
Initialize DISK
Alarmsolved
yes
Alarm occurs often for a specific DISK?
no
Figure 62: DISC-PARITY-ERROR: Corrective Actions
188 / 533 3BK 20918 AAAA PCZZA Ed.06
14 Class 47: GLOBAL-BSC Alarms
14 Class 47: GLOBAL-BSC Alarms
This section defines the BSC alarms for the Class 47: GLOBAL-BSC alarmclass.
3BK 20918 AAAA PCZZA Ed.06 189 / 533
14 Class 47: GLOBAL-BSC Alarms
14.1 [47,1] SCCP-NOT-AVAIL
specificProblems: SCCP-NOT-AVAIL
eventType: QualityOfService
probableCause: Congestion
perceivedSeverity: Critical (SA)
Alarm Description There are insufficient N7 resources due to failures to open a newSCCP connection or to send blocking/unblocking messages.
Also the dimensioning of N7 links is probably incorrect.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - -
190 / 533 3BK 20918 AAAA PCZZA Ed.06
14 Class 47: GLOBAL-BSC Alarms
14.1.1 Corrective Actions
[47,1] SCCP−NOT−AVAIL
Solve N7 alarm(s) first
Correct N7 parameters
ContactSystem Support
N7 parameters
OK?
no
yes
Repair/replace N7 equipment
N7 alarm events?
no
yes
On−site
Alarmsolved
Alarm persists?
no
yes
Alarmsolved
Alarm persists?
no
yes
N7 links
operational?
no
yes
Increase N7 resources
On−site
Figure 63: SCCP-NOT-AVAIL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 191 / 533
14 Class 47: GLOBAL-BSC Alarms
14.2 [47,2] AUTO-BSC-RESET
specificProblems: AUTO-BSC-RESET
eventType: ProcessingError
probableCause: softwareProgramAbnormallyTerminated
perceivedSeverity: Warning (MI)
Alarm Description An autonomous reboot/reset of the BSC occurred. The alarm is alwayssent to both the OMC-R and the local terminal.
Impact on System The SBL state remains unchanged.
The impact depends on what has occurred, as described above. SeeProcessor Reset [33,1].
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
14.2.1 Corrective Actions
None – this information is always sent after an autonomous reboot/reset ofthe BSC.
192 / 533 3BK 20918 AAAA PCZZA Ed.06
14 Class 47: GLOBAL-BSC Alarms
14.3 [47,3] AUTO-BSC-RESTART
specificProblems: AUTO-BSC-RESTART
eventType: ProcessingError
probableCause: softwareProgramAbnormallyTerminated
perceivedSeverity: Warning (MI)
Alarm Description The BSC was successfully restarted from the OMC-R or BSC localterminal.
Impact on System The SBL state remains unchanged.
The impact depends on what has occurred, as described above. Seeprocessor restart [33,0].
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
14.3.1 Corrective Actions
None - this information is always sent after an autonomous restart of the BSC.
3BK 20918 AAAA PCZZA Ed.06 193 / 533
14 Class 47: GLOBAL-BSC Alarms
14.4 [47,4] BSC-SYNC-REQ
specificProblems: BSC-SYNC-REQ
eventType: Communication
probableCause: CommunicationSubsystemFailure
perceivedSeverity: Warning (MI)
Alarm Description All BSC alarms are stored on one I/O queue. A BSC Sync Request isonly sent if the BSC I/O own queue overflow occurs.
An overflow may occur on an OMC-R interface if:
There is no OSI CPRA
The X.25 link is down
The OMC-R is not active.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
14.4.1 Corrective Actions
None – on reception of the alarm, the OMC-R starts a BSC alarm audit.
194 / 533 3BK 20918 AAAA PCZZA Ed.06
14 Class 47: GLOBAL-BSC Alarms
14.5 [47,5] BTS-SYNC-REQ
specificProblems: BTS-SYNC-REQ
eventType: Communication
probableCause: CommunicationSubsystemFailure
perceivedSeverity: Warning (MI)
Alarm Description All BTS alarms are stored in one I/O queue. A BTS Sync Request isonly sent if the BTS I/O queue overflow occurs.
An overflow may occur on an OMC-R interface if:
There is no OSI CPRA
The X.25 link is down
The OMC-R not active.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
14.5.1 Corrective Actions
None – on reception of the alarm, the OMC-R starts a BTS alarm audit.
3BK 20918 AAAA PCZZA Ed.06 195 / 533
14 Class 47: GLOBAL-BSC Alarms
14.6 [47,6] AUDIT-COMPLETED
specificProblems: AUDIT-COMPLETED
eventType: ProcessingError
probableCause: softwareProgramAbnormallyTerminated
perceivedSeverity: Warning (MI)
Alarm Description The BSC was successfully reset or restarted from the OMC-R or BSClocal terminal.
Impact on System The SBL state remains unchanged.
The impact depends on what has occurred, as described above. SeeProcessor Reset [33,1].
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
14.6.1 Corrective Actions
None – this information is always sent after an successful reset or restart ofthe BSC.
196 / 533 3BK 20918 AAAA PCZZA Ed.06
14 Class 47: GLOBAL-BSC Alarms
14.7 [47,7] BSC-HW-RESYNC
specificProblems: BSC-HW-RESYNC
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Warning (MI)
Alarm Description This alarm is generated after BSC extension or reduction. The BSCsends this alarm to the OMC-R.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/BTS(s)
Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - -
14.7.1 Corrective Actions
None – on reception of the alarm, the OMC-R triggers audits to resynchronizewith the BSC.
3BK 20918 AAAA PCZZA Ed.06 197 / 533
14 Class 47: GLOBAL-BSC Alarms
14.8 [47,8] AIFL-FULL
specificProblems: AIFL-FULL
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Warning (MI)
Alarm Description The BSC alarms list is full.
Impact on System The SBL state remains unchanged.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
14.8.1 Corrective Actions
[47,8] AIFL−FULL
Solve remaining alarms
ContactSystem Support
System generates too
many alarms in short time period?
no
yes
Alarmsolved
Figure 64: AIFL-FULL: Corrective Actions
198 / 533 3BK 20918 AAAA PCZZA Ed.06
14 Class 47: GLOBAL-BSC Alarms
14.9 [47,9] CBC-CONNECTION-FAILURE
specificProblems: CBC-CONNECTION-FAILURE
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Major (PMA)
Alarm Description The alarm is generated when there is a problem with the connectiontowards the CBC.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
3BK 20918 AAAA PCZZA Ed.06 199 / 533
14 Class 47: GLOBAL-BSC Alarms
14.9.1 Corrective Actions
[47,9] CBC−CONNECTION−FAILURE
Solve X.25 alarm(s) first
Correct X.25 parameters
ContactSystem Support
X.25 parameters
OK?
no
yes
Repair/replace X.25 equipment
X.25 alarm events?
no
yes
On−site
Alarmsolved
Alarm persists?
no
yes
Alarmsolved
Alarm persists?
no
yes
X.25 links
operational?
no
yes
Figure 65: CBC-CONNECTION-FAILURE: Corrective Actions
200 / 533 3BK 20918 AAAA PCZZA Ed.06
14 Class 47: GLOBAL-BSC Alarms
14.10 [47,11] ABIS-TS-ALLOC-FAILED
specificProblems: ABIS-TS-ALLOC-FAILED
eventType: ProcessingError
probableCause: ConfigurationOrCustomizationError
perceivedSeverity: Warning (MI)
Alarm Description This alarm is raised to indicate that TS allocation in the case ofauto-detection of a TRE has failed.
Impact on System The SBL state remains unchanged.
The TRE detected via the Audit will not be operational, no TSs willbe allocated.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation -
14.10.1 Corrective Actions
[47,11] ABIS−TS−ALLOC−FAILED
Check multiplexing parameters used by this BTS. If the Abis conveys only Evolium BTS remove
Q1 TS if it exists
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Figure 66: ABIS-TS-ALLOC-FAILED: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 201 / 533
14 Class 47: GLOBAL-BSC Alarms
14.11 [47,12] INSUFFICIENT-TCU-RES
specificProblems: INSUFFICENT-TCU-RES
eventType: ProcessingError
probableCause: ConfigurationOrCustomizationError
perceivedSeverity: Warning (MI)
Alarm Description This alarm is raised to indicate that TCU allocation, in the case ofauto-detection of a TRE, has failed due to insufficient TCU resources.
Impact on System The SBL state remains unchanged.
The TRE detected via the Audit will not be operational, no TCU willbe allocated.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation -
14.11.1 Corrective Actions
[47,12] INSUFFICIENT−TCU−RES
Check occupancy of the TSU and make place in the TSU using one of the following
methods
ContactSystem Support
Alarmsolved
Alarm cleared?
no
yes
Trigger a TSU reshuffling
Decrease Max−Extra−TS−Primary if there is a 2 Abis BTS and the TCU supporting the second Abis link has still free resources
Move one BTS from this TSU to another one
Figure 67: INSUFFICIENT-TCU-RES: Corrective Actions
202 / 533 3BK 20918 AAAA PCZZA Ed.06
14 Class 47: GLOBAL-BSC Alarms
14.12 [47,13] TRE-SECTOR-MISMATCH
specificProblems: TRE-SECTOR-MISMATCH
eventType: ProcessingError
probableCause: ConfigurationOrCustomizationError
perceivedSeverity: Warning (MI)
Alarm Description This alarm is raised in the case of a mismatch in a TRE sector betweenthe sector defined via the Create-TRE command and the sector inwhich the TRE is equipped, as indicated via the BSC-BTS Audit.
Impact on System The SBL state remains unchanged.
The TRE is not operational
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation -
3BK 20918 AAAA PCZZA Ed.06 203 / 533
14 Class 47: GLOBAL-BSC Alarms
14.12.1 Corrective Actions
[47,13] TRE−SECTOR−MISMATCH
Define correct sector via Create−TRE command
Alarmsolved
Alarm persists?
no
yes
Remove TRE from incorrect sector via
Delete−TRE command
Equip TRE in correct sector to correspond to defined TRE
via Create−TRE command
ContactSystem Support
Alarm persists?
no
yes
Remove TRE
On−site
On−siteOR
Figure 68: TRE-SECTOR-MISMATCH: Corrective Actions
204 / 533 3BK 20918 AAAA PCZZA Ed.06
14 Class 47: GLOBAL-BSC Alarms
14.13 [47,14] TCU TOO FRAGMENTED
specificProblems: TCU TOO FRAGEMENTED
eventType: Equipment
probableCause: InputOutputDeviceError
perceivedSeverity: Warning (MI)
Alarm Description This alarm is raised to indicate that TCU allocation, in the case ofauto-detection of a TRE, has failed due to the TCU allocation beingtoo fragmented.
Impact on System The SBL state remains unchanged.
The TRE detected via the Audit will not be operational, no TCU will beallocated. A TCU can be allocated if reshuffling is requested.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation -
14.13.1 Corrective Actions
[47,14] TCUTOO FRAGMENTED
Reshuffle TCUs via Compact RSL/TCU remapping
andManually add−on the TRE on
BSC
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Figure 69: TCU-DEFRAGMENTED: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 205 / 533
14 Class 47: GLOBAL-BSC Alarms
14.14 [47,15] SWRPL-IN-PROGRESS
specificProblems: SWRPL-IN-ROGRESS
eventType: Equipment
probableCause: InputOutputDeviceError
perceivedSeverity: Warning (MI)
Alarm Description This alarm is raised to indicate that an audit has occurred and that the BSCwas informed of equipment addition or removal, but the BSC could not processthis information, as the BSC was undergoing software replacement.
Impact on System An audit is triggered when BTS-OM is initialized and the BSC is informed ofBTS equipment which is added or removed.
The SBL state remains unchanged.
The BSC is undergoing a software replacement.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation -
206 / 533 3BK 20918 AAAA PCZZA Ed.06
14 Class 47: GLOBAL-BSC Alarms
14.14.1 Corrective Actions
[47,15] SWRPL−IN−PROGRESS
If no audit is started, trigger new audit
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Wait for new autonomous audit
Figure 70: SWRPL-IN-PROGRESS: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 207 / 533
14 Class 47: GLOBAL-BSC Alarms
14.15 [47,16] MAX-TRE-EXCEEDED
specificProblems: MAX-TRE-EXCEEDED
eventType: Equipment
probableCause: InputOutputDeviceError
perceivedSeverity: Warning (MI)
Alarm Description This alarm is raised to indicate that an audit has occurred, indicatingan addition of TREs when the maximum number of TREs alreadyexists in the BSC.
Impact on System The SBL state remains unchanged.
The TREs detected via the audit cannot be auto-allocated as themaximum number of TREs already exists in the BSC.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation -
208 / 533 3BK 20918 AAAA PCZZA Ed.06
14 Class 47: GLOBAL-BSC Alarms
14.15.1 Corrective Actions
[47,16] MAX−TRE−EXCEEDED
Delete unrequired TRE data. TRE(s) must be not equipped,
if auto−allocate is set for the Abis
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Remove reported TRE(s)
On−site
Alarm persists?
no
yes
Alarmsolved
Figure 71: MAX-TRE-EXCEEDED: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 209 / 533
14 Class 47: GLOBAL-BSC Alarms
210 / 533 3BK 20918 AAAA PCZZA Ed.06
15 Class 48: TR-OM Alarms
15 Class 48: TR-OM Alarms
This section defines the BSC alarms for the Class 48: TR–OM alarm class.
3BK 20918 AAAA PCZZA Ed.06 211 / 533
15 Class 48: TR-OM Alarms
15.1 [48,0] AUDIT-FAIL
specificProblems: AUDIT-FAIL
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description Due to a failure in the BSC-TSC audit, TR-OM changed from FLT/ITto FLT.
Impact on System TSL is up. When the TR-OM is FLT but the TSL is up, the BSC triggersan audit every two minutes until an audit succeeds.
TSL is down - corrective action required.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
15.1.1 Corrective Actions
[48,0] AUDIT−FAIL
Reset TSC
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Figure 72: AUDIT-FAIL: Corrective Actions
212 / 533 3BK 20918 AAAA PCZZA Ed.06
15 Class 48: TR-OM Alarms
15.2 [48,1] PROTOCOL-FAIL
specificProblems: PROTOCOL-FAIL
eventType: Communication
probableCause: CommunicationSubsystemFailure
perceivedSeverity: Minor (DMA)
Alarm Description The TR-OM goes to FLT if there is protocol failure on the Abis interface;an ’ACK’ to some message is not received after threerequired retries.
An attempt is always made to respond by means of an ACK or NACKto a Request/Report/Ind message from the TSC regardless of thecontext. This however, cannot occur when there is a loss of LAPDand a protocol error is registered.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
15.2.1 Corrective Actions
[48,1] PROTOCOL−FAIL
Reset TSC
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
TSL is down only:
Figure 73: PROTOCOL-FAIL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 213 / 533
15 Class 48: TR-OM Alarms
214 / 533 3BK 20918 AAAA PCZZA Ed.06
16 Class 49: ALERTOR Alarms
16 Class 49: ALERTOR Alarms
This section defines the BSC alarms for the Class 49: ALERTOR alarm class.
3BK 20918 AAAA PCZZA Ed.06 215 / 533
16 Class 49: ALERTOR Alarms
16.1 [49,0] TRAFF-SDCCH
specificProblems: LOW-TRAFF-SDCCH
eventType: QualityOfService
probableCause: PerfomanceDegraded
perceivedSeverity: Major (PMA)
Alarm Description There is abnormally low traffic on SDCCHs in a cell compared withother BSS cells.
Impact on System This alarm inform the operator that there is abnormally low SDCCHtraffic in a cell compared with other cells.
This is an information message and no system defensive actions aretaken.
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
216 / 533 3BK 20918 AAAA PCZZA Ed.06
16 Class 49: ALERTOR Alarms
16.1.1 Corrective Actions
[49,0] TRAFF−SDCCH
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Related BTS alarm
events?
no
yes Solve related BTS alarm(s) first
Alarmsolved
Alarm persists?
no
yes
Related BSC alarm
events?
no
yes Solve related BSC alarm(s)
ContactSystem Support
Figure 74: TRAFF-SDCCH: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 217 / 533
16 Class 49: ALERTOR Alarms
16.2 [49,1] CH-INCONSIST-SUSP
specificProblems: CH-INCONSIST-SUSP
eventType: QualityOfService
probableCause: PerfomanceDegraded
perceivedSeverity: Major (PMA)
Alarm Description There is an inconsistency in the terrestrial channel states.
Impact on System This alarm is generated when the number of seizure failures exceeds apre-assigned threshold value. The threshold is the maximum numberof seizures per circuit that is set by the operator on a BSS basis.
This is an information message and no system defensive actions aretaken.
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
218 / 533 3BK 20918 AAAA PCZZA Ed.06
16 Class 49: ALERTOR Alarms
16.2.1 Corrective Actions
[49,1] CH−INCONSIST−SUSP
Alarmsolved
Alarm persists?
noyes
Byte related alarm
events?
no
yes Solve Byte relating alarm(s) first
Related DTC/Trunk/N7 alarm
events?
no
yesSolve that alarm(s)
ContactSystem Support
Analyze additional information bytes
Figure 75: CH-INCONSIST-SUSP: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 219 / 533
16 Class 49: ALERTOR Alarms
16.3 [49,2] TCH-BLOCK-SUSPECT
specificProblems: TCH-BLOCK-SUSPECT
eventType: QualityOfService
probableCause: PerfomanceDegraded
perceivedSeverity: Major (PMA)
Alarm Description Traffic channel behavior is abnormal and calls remain on the channelsfor an extended length of time. It is suspected that the traffic channelsare blocked.
Impact on System This alarm is generated when the call duration for all traffic channels ina cell exceeds a pre-assigned threshold value (1...255 minutes). Thethreshold is set by the operator on a BSS basis.
This is an information message and no system defensive actions aretaken.
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
16.3.1 Corrective Actions
[49,2] TCH−BLOCK−SUSPECT
Alarmsolved
Alarm persists?
noyes
TCH related hardware
problems?
no
yes Solve TCH related hardware problems
ContactSystem Support
Analyze additional information bytes
Figure 76: TCH-BLOCK-SUSPECT: Corrective Actions
220 / 533 3BK 20918 AAAA PCZZA Ed.06
16 Class 49: ALERTOR Alarms
16.4 [49,3] TCH-OCCUP-SHORT
specificProblems: TCH-OCCUP-SHORT
eventType: QualityOfService
probableCause: PerfomanceDegraded
perceivedSeverity: Major (PMA)
Alarm Description The average traffic channel seizure time is considered to be too short.
Impact on System This alarm informs the operator that there has been abnormally shorttraffic duration on a traffic channel.
This is an information message and no system defensive actions aretaken.
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
16.4.1 Corrective Actions
[49,3] TCH−OCCUP−SHORT
Alarmsolved
Alarm persists?
noyes
TCH related hardware
problems?
no
yes Solve TCH related hardware problemst
ContactSystem Support
Analyze additional information bytes
Figure 77: TCH-OCCUP-SHORT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 221 / 533
16 Class 49: ALERTOR Alarms
222 / 533 3BK 20918 AAAA PCZZA Ed.06
17 Class 50: BSC-EXTERNAL Alarms
17 Class 50: BSC-EXTERNAL Alarms
This section defines the BSC alarms for the Class 50: BSC-EXTERNALalarm class.
3BK 20918 AAAA PCZZA Ed.06 223 / 533
17 Class 50: BSC-EXTERNAL Alarms
17.1 [50,1] EXT-ALARM-1
specificProblems: EXT-ALARM-1
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: CUSTOMER DEPENDENT
Alarm Description A probable cause and category is provided in a customer-dependenttable residing in the OMC-R. This probable cause should accuratelyand informatively describe the external alarm.
Impact on System The SBL state remains unchanged.
No system impact.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
224 / 533 3BK 20918 AAAA PCZZA Ed.06
17 Class 50: BSC-EXTERNAL Alarms
17.1.1 Corrective Actions
[50,1] EXT−ALARM−1
no
ContactSystem Support
External alarm
persists?
yes
Alarmsolved
yesAlarm was sent without
cause?
no
Trigger customer specific action according to
reported alarm (e.g. call fire brigade)
Check sensor function, replace sensor if required.
On−site
Check sensor connection to BSC. Reconnect sensor
if required.
On−site
Check cabling to sensor, replace cabling if required.
On−site
Figure 78: EXT-ALARM-1: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 225 / 533
17 Class 50: BSC-EXTERNAL Alarms
17.2 [50,2] EXT-ALARM-2
specificProblems: EXT-ALARM-2
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: CUSTOMER DEPENDENT
Alarm Description A probable cause and category is provided in a customer-dependenttable residing in the OMC-R. The OMC-R table describes the externalalarm.
Impact on System The SBL state remains unchanged.
No system impact.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
226 / 533 3BK 20918 AAAA PCZZA Ed.06
17 Class 50: BSC-EXTERNAL Alarms
17.2.1 Corrective Actions
[50,2] EXT−ALARM−2
no
ContactSystem Support
External alarm
persists?
yes
Alarmsolved
yesAlarm was sent without
cause?
no
Trigger customer−specific action according to
reported alarm (e.g. call fire brigade)
Check sensor function, replace sensor if required.
On−site
Check sensor connection to BSC. Reconnect sensor
if required.
On−site
Check cabling to sensor, replace cabling if required.
On−site
Figure 79: EXT-ALARM-2: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 227 / 533
17 Class 50: BSC-EXTERNAL Alarms
17.3 [50,3] EXT-ALARM-3
specificProblems: EXT-ALARM-3
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: CUSTOMER DEPENDENT
Alarm Description A probable cause and category is provided in a customer-dependenttable residing in the OMC-R. The OMC-R table describes the externalalarm.
Impact on System The SBL state remains unchanged.
No system impact.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
228 / 533 3BK 20918 AAAA PCZZA Ed.06
17 Class 50: BSC-EXTERNAL Alarms
17.3.1 Corrective Actions
[50,3] EXT−ALARM−3
no
ContactSystem Support
External alarm
persists?
yes
Alarmsolved
yesAlarm was sent without
cause?
Trigger customer−specific action according to
reported alarm (e.g. call fire brigade)
Check sensor function, replace sensor if required.
On−site
Check sensor connection to BSC. Reconnect sensor
if required.
On−site
Check cabling to sensor, replace cabling if required.
On−siteno
Figure 80: EXT-ALARM-3: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 229 / 533
17 Class 50: BSC-EXTERNAL Alarms
17.4 [50,4] EXT-ALARM-4
specificProblems: EXT-ALARM-4
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: CUSTOMER DEPENDENT
Alarm Description A probable cause and category is provided in a customer-dependenttable residing in the OMC-R. The OMC-R table describes the externalalarm.
Impact on System The SBL state remains unchanged.
No system impact.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
230 / 533 3BK 20918 AAAA PCZZA Ed.06
17 Class 50: BSC-EXTERNAL Alarms
17.4.1 Corrective Actions
[50,4] EXT−ALARM−4
no
ContactSystem Support
External alarm
persists?
yes
Alarmsolved
yesAlarm was sent without
cause?
no
Trigger customer−specific action according to
reported alarm (e.g. call fire brigade)
Check sensor function, replace sensor if required.
On−site
Check sensor connection to BSC. Reconnect sensor
if required.
On−site
Check cabling to sensor, replace cabling if required.
On−site
Figure 81: EXT-ALARM-4: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 231 / 533
17 Class 50: BSC-EXTERNAL Alarms
17.5 [50,5] EXT-ALARM-5
specificProblems: EXT-ALARM-5
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: CUSTOMER DEPENDENT
Alarm Description A probable cause and category is provided in a customer-dependenttable residing in the OMC-R. The OMC-R table describes the externalalarm.
Impact on System The SBL state remains unchanged.
No system impact.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
232 / 533 3BK 20918 AAAA PCZZA Ed.06
17 Class 50: BSC-EXTERNAL Alarms
17.5.1 Corrective Actions
[50,5] EXT−ALARM−5
no
ContactSystem Support
External alarm
persists?
yes
Alarmsolved
yesAlarm was sent without
cause?
no
Trigger customer−specific action according to
reported alarm (e.g. call fire brigade)
Check sensor function, replace sensor if required.
On−site
Check sensor connection to BSC. Reconnect sensor
if required.
On−site
Check cabling to sensor, replace cabling if required.
On−site
Figure 82: EXT-ALARM-5: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 233 / 533
17 Class 50: BSC-EXTERNAL Alarms
17.6 [50,6] EXT-ALARM-6
specificProblems: EXT-ALARM-6
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: CUSTOMER DEPENDENT
Alarm Description A probable cause and category is provided in a customer-dependenttable residing in the OMC-R. The OMC-R table describes the externalalarm.
Impact on System The SBL state remains unchanged.
No system impact.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
234 / 533 3BK 20918 AAAA PCZZA Ed.06
17 Class 50: BSC-EXTERNAL Alarms
17.6.1 Corrective Actions
[50,6] EXT−ALARM−6
no
ContactSystem Support
External alarm
persists?
yes
Alarmsolved
yesAlarm was sent without
cause?
no
Trigger customer−specific action according to
reported alarm (e.g. call fire brigade)
Check sensor function, replace sensor if required.
On−site
Check sensor connection to BSC. Reconnect sensor
if required.
On−site
Check cabling to sensor, replace cabling if required.
On−site
Figure 83: EXT-ALARM-6: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 235 / 533
17 Class 50: BSC-EXTERNAL Alarms
17.7 [50,7] EXT-ALARM-7
specificProblems: EXT-ALARM-7
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: CUSTOMER DEPENDENT
Alarm Description A probable cause and category is provided in a customer-dependenttable residing in the OMC-R. The OMC-R table describes the externalalarm.
Impact on System The SBL state remains unchanged.
No system impact.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
236 / 533 3BK 20918 AAAA PCZZA Ed.06
17 Class 50: BSC-EXTERNAL Alarms
17.7.1 Corrective Actions
[50,7] EXT−ALARM−7
no
ContactSystem Support
External alarm
persists?
yes
Alarmsolved
yesAlarm was sent without
cause?
no
Trigger customer−specific action according to
reported alarm (e.g. call fire brigade)
Check sensor function, replace sensor if required.
On−site
Check sensor connection to BSC. Reconnect sensor
if required.
On−site
Check cabling to sensor, replace cabling if required.
On−site
Figure 84: EXT-ALARM-7: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 237 / 533
17 Class 50: BSC-EXTERNAL Alarms
17.8 [50,8] EXT-ALARM-8
specificProblems: EXT-ALARM-8
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: CUSTOMER DEPENDENT
Alarm Description A probable cause and category is provided in a customer-dependenttable residing in the OMC-R. The OMC-R table describes the externalalarm.
Impact on System The SBL state remains unchanged.
No system impact.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
238 / 533 3BK 20918 AAAA PCZZA Ed.06
17 Class 50: BSC-EXTERNAL Alarms
17.8.1 Corrective Actions
[50,8] EXT−ALARM−8
no
ContactSystem Support
External alarm
persists?
yes
Alarmsolved
yesAlarm was sent without
cause?
no
Trigger customer−specific action according to
reported alarm (e.g. call fire brigade)
Check sensor function, replace sensor if required.
On−site
Check sensor connection to BSC. Reconnect sensor
if required.
On−site
Check cabling to sensor, replace cabling if required.
On−site
Figure 85: EXT-ALARM-8: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 239 / 533
17 Class 50: BSC-EXTERNAL Alarms
17.9 [50,9] EXT-ALARM-9
specificProblems: EXT-ALARM-9
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: CUSTOMER DEPENDENT
Alarm Description A probable cause and category is provided in a customer-dependenttable residing in the OMC-R. The OMC-R table describes the externalalarm.
Impact on System The SBL state remains unchanged.
No system impact.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
240 / 533 3BK 20918 AAAA PCZZA Ed.06
17 Class 50: BSC-EXTERNAL Alarms
17.9.1 Corrective Actions
[50,9] EXT−ALARM−9
no
ContactSystem Support
External alarm
persists?
yes
Alarmsolved
yesAlarm was sent without
cause?
no
Trigger customer−specific action according to
reported alarm (e.g. call fire brigade)
Check sensor function, replace sensor if required.
On−site
Check sensor connection to BSC. Reconnect sensor
if required.
On−site
Check cabling to sensor, replace cabling if required.
On−site
Figure 86: EXT-ALARM-9: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 241 / 533
17 Class 50: BSC-EXTERNAL Alarms
17.10 [50,10] EXT-ALARM-10
specificProblems: EXT-ALARM-10
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: CUSTOMER DEPENDENT
Alarm Description A probable cause and category is provided in a customer-dependenttable residing in the OMC-R. The OMC-R table describes the externalalarm.
Impact on System The SBL state remains unchanged.
No system impact.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
242 / 533 3BK 20918 AAAA PCZZA Ed.06
17 Class 50: BSC-EXTERNAL Alarms
17.10.1 Corrective Actions
[50,10] EXT−ALARM−10
no
ContactSystem Support
External alarm
persists?
yes
Alarmsolved
yesAlarm was sent without
cause?
no
Trigger customer−specific action according to
reported alarm (e.g. call fire brigade)
Check sensor function, replace sensor if required.
On−site
Check sensor connection to BSC. Reconnect sensor
if required.
On−site
Check cabling to sensor, replace cabling if required.
On−site
Figure 87: EXT-ALARM-10: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 243 / 533
17 Class 50: BSC-EXTERNAL Alarms
244 / 533 3BK 20918 AAAA PCZZA Ed.06
18 Class 51: SWITCH-G2 Alarms
18 Class 51: SWITCH-G2 Alarms
This section defines the BSC alarms for the Class 51: SWITCH-G2 alarm class.
3BK 20918 AAAA PCZZA Ed.06 245 / 533
18 Class 51: SWITCH-G2 Alarms
18.1 [51,0] TRANSIENT-FAIL
specificProblems: TRANSIENT-FAIL
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Warning (MI)
Alarm Description The switch detected a momentary fault.
Impact on System The SBL state remains unchanged.
The switch element remains IT/FIT. Some interference is likely oncurrent calls through the switch.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
18.1.1 Corrective Actions
[51,0] TRANSIENT−FAIL
noContact
System Support
Alarm persists?
yes
Alarmsolved
yesSWITCH−
FAILalarm
events?
no
Solve SWITCH−FAIL alarm(s)
ContactSystem Support
Figure 88: TRANSIENT-FAIL: Corrective Actions
246 / 533 3BK 20918 AAAA PCZZA Ed.06
18 Class 51: SWITCH-G2 Alarms
18.2 [51,1] SWITCH-FAIL
specificProblems: SWITCH-FAIL
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Major (PMA)
Alarm Description The switch element is isolated from the operational software due to apersistent fault.
Impact on System If an alarm is internally present on a link, the switch connected to thelink is updated to FIT.
If the number of faulty links on the switch is >= (number of links presenton the switch -1) /2, the switch is updated to FOS.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
3BK 20918 AAAA PCZZA Ed.06 247 / 533
18 Class 51: SWITCH-G2 Alarms
18.2.1 Corrective Actions for Write Violation Overflow, Loss of SyncOverflow and Init Fail Alarms
[51,1] SWITCH−FAIL
no
ContactSystem Support
Alarm persists?
yes
Alarmsolved
Check cabling to switch, replace
cabling if required.
Analyze additional information bytes
Two alarms are generated for a link, one alarm for each affected switch.
Lock faultySWITCH
Unlock faultySWITCH
On−site
For Write Violation Overflow, Loss of Sync Overflow and Init Fail alarms:
Figure 89: SWITCH-FAIL: Corrective Actions for Write Violation Overflow, Lossof Sync Overflow and Init Fail Alarms
248 / 533 3BK 20918 AAAA PCZZA Ed.06
18 Class 51: SWITCH-G2 Alarms
18.2.2 Corrective Actions for Loss of Sync Alarm
[51,1] SWITCH−FAIL
no
ContactSystem Support
Alarm persists?
yes
Alarmsolved
Check cabling to switch, replace
cabling if required.
Analyze additional information bytes
Two alarms are generated for a link, one alarm for each affected switch.
Lock faultySWITCH
Unlock faultySWITCH
On−site
For Loss of Sync alarms:
Replace/repair clock generator/repeater
noLast clock generator/repeater
operational?
yes
Replace/repair clock extractor
noLast clock extractor
operational?
yes
Trigger repar action at MSC side
noMSC/trunk provides clock pulse
to BSC?
yes
Figure 90: SWITCH-FAIL: Corrective Actions for Loss of Sync Alarm
3BK 20918 AAAA PCZZA Ed.06 249 / 533
18 Class 51: SWITCH-G2 Alarms
18.2.3 Corrective Actions for HW Fault Alarm
[51,1] SWITCH−FAIL
no
ContactSystem Support
Alarm persists?
yes
Alarmsolved
Check links to faulty switch,
replace cabling if required.
Analyze additional information bytes
Two alarms are generated for a link, one alarm for each affected switch.
On−site
For HW Fault alarms:
On−site
Replace reported faulty switch
Alarmsolved
yesSwitchoperational?
no
Figure 91: SWITCH-FAIL: Corrective Actions for HW Fault Alarm
250 / 533 3BK 20918 AAAA PCZZA Ed.06
18 Class 51: SWITCH-G2 Alarms
18.3 [51,2] ROUTINE-TEST-REP
specificProblems: ROUTINE-TEST-REP
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Warning (MI)
Alarm Description A network switch link failure was detected during a routine networktunnel test. The link remains available to the operational software.
Impact on System The SBL state remains unchanged.
The switch is still able to carry traffic. However no operator actions canbe performed and will be NACK with the Error Code ’busy by rt’.
In the case of a routine test of a link and a switch and the ’testexecuted’, all Test-raw-data is filled in.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
3BK 20918 AAAA PCZZA Ed.06 251 / 533
18 Class 51: SWITCH-G2 Alarms
18.3.1 Corrective Actions
[51,2] ROUTINE−TEST−REP
Analyze additionalinformation bytes
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
no
On−site
Replace suspected switch
On−site
Repair/replace hardware
yes
Switch hardware
OK?
no
On−site
Repair/replace hardware
yes
Switch cabling
OK?
ContactSystem Support
Figure 92: ROUTINE-TEST-REP: Corrective Actions
252 / 533 3BK 20918 AAAA PCZZA Ed.06
19 Class 52: BSC-Clock Alarms
19 Class 52: BSC-Clock Alarms
This section defines the BSC alarms for the Class 52: BSC–Clock alarm class.
3BK 20918 AAAA PCZZA Ed.06 253 / 533
19 Class 52: BSC-Clock Alarms
19.1 [52,0] LOSS-OF-SEL-CLK-INP
specificProblems: LOSS-OF-SEL-CLK-INP
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Major (PMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description The CLK-GEN detects that all external references have failed. Inaddition, the local clock has also failed.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
254 / 533 3BK 20918 AAAA PCZZA Ed.06
19 Class 52: BSC-Clock Alarms
19.1.1 Corrective Actions
[52,0] LOSS−OF−SEL−CLK−INP
Solve Ater alarm(s) first
yes
Alarm persists?
no
ContactSystem Support
Ateralarm
events?
no
yes
Solve DTC alarm(s)
DTCalarm
events?
no
yes
Alarmsolved
yes
Alarm persists?
no
On−site
Replace Ater trunk extracted
by the 3 DTCs
Figure 93: LOSS-OF-SEL-CLK-INP: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 255 / 533
19 Class 52: BSC-Clock Alarms
19.2 [52,1] LOSS-OF-CLK-GEN-FN
specificProblems: LOSS-OF-CLK-GEN-FN
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Major (PMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description The CLK-GEN is lost due to one of the following:
Reference selector failure
PLL out of range
Absence of own clock
Watchdog timer expiry
Access failure.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
256 / 533 3BK 20918 AAAA PCZZA Ed.06
19 Class 52: BSC-Clock Alarms
19.2.1 Corrective Actions
[52,1] LOSS−OF−CLK−GEN−FN
Analyze additional information bytes
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
On−site
Replace suspected Clock RIT
Figure 94: LOSS-OF-CLK-GEN-FN: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 257 / 533
19 Class 52: BSC-Clock Alarms
19.3 [52,2] SWITCH-TO-LOCAL-CLK
specificProblems: SWITCH-TO-LOCAL-CLK
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Minor (DMA)
Alarm Description Due to loss of all external clocks, the CLK-GEN has selected a localclock.
If only one CLK-GEN has detected this situation, there is no impact onthe clock distributed throughout the BSC as the SYS-BCLA will selectthe clock provided by the other CLK-GEN.
If both CLK-GEN detect this problem, then BSC produces alarm [52,6],which corresponds to the usage in BSC of a local clock.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
258 / 533 3BK 20918 AAAA PCZZA Ed.06
19 Class 52: BSC-Clock Alarms
19.3.1 Corrective Actions
It is strongly recommended to refit external clock (Ater 1-3) inputs to CLK-GEN,as loss of the other CLK-GEN will lead to alarm ’BSC-RUN-ON-LOCAL-CLK’being issued. This alarm has important repercussion on this BSS part. Seesuspected RITs information for DTCs which extract the clock signal for thisCLK_GEN.
[52,2] SWITCH−TO−LOCAL−CLK
Solve DTC/Ater alarm(s) first
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
DTC/ Ateralarm
events?
no
yes
Solve transmission alarm(s)
Transmissionalarm
events?
no
yes
Trigger clock source checks at MSC side
Figure 95: SWITCH-TO-LOCAL-CLK: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 259 / 533
19 Class 52: BSC-Clock Alarms
19.4 [52,3] LOSS-OF-SYSTEM-CLOCK-A
specificProblems: LOSS-OF-SYSTEM-CLK-A
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Minor (DMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description The System Clock A failure is detected by CLK-REP.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
19.4.1 Corrective Actions
[52,3] LOSS−OF−SYSTEM−CLOCK−A
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
On−site
Replace suspected
System Clock A
The rack number is indicated by the CLK−REP SBL number
Figure 96: LOSS-OF-SYSTEM-CLOCK-A: Corrective Actions
260 / 533 3BK 20918 AAAA PCZZA Ed.06
19 Class 52: BSC-Clock Alarms
19.5 [52,4] LOSS-OF-SYSTEM-CLOCK-B
specificProblems: LOSS-OF-SYSTEM-CLK-B
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Minor (DMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description A System Clock B failure is detected by CLK-REP.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
19.5.1 Corrective Actions
[52,4] LOSS−OF−SYSTEM−CLOCK−B
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
On−site
Replace suspected
System Clock B
The rack number is indicated by the CLK−REP SBL number
Figure 97: LOSS-OF-SYSTEM-CLOCK-B: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 261 / 533
19 Class 52: BSC-Clock Alarms
19.6 [52,5] LOSS-OF-CLK-DISTR-FN
specificProblems: LOSS-OF-CLK-DISTR-FN
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Major (PMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description The CLK-REP is lost due to one of the following:
Reference selector failure
PLL out of range
Absence of own clock
Watchdog timer expiry
Access failure.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - -
262 / 533 3BK 20918 AAAA PCZZA Ed.06
19 Class 52: BSC-Clock Alarms
19.6.1 Corrective Actions
[52,5] LOSS−OF−CLK−DISTR−FN
Analyze additional information bytes
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
On−site
Replace suspected
Clock repeater
The rack number is indicated by CLK−REP SBL number.
Figure 98: LOSS-OF-CLK-DISTR-FN: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 263 / 533
19 Class 52: BSC-Clock Alarms
19.7 [52,6] BSC-RUN-ON-LOCAL-CLK
specificProblems: BSC-RUN-ON-LOCAL-CLK
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Major (PMA)
Alarm Description This alarm is generated when the BSC is running on the local clock.
Impact on System The BTS cannot function correctly if using the local BSC clock.
Depending on the difference between the local clock and the clockused on the remaining Ater links, the impact can be small (degradation,only retransmissions, alarms Slip-un-run, Slip-ov-run, various synchroalarms) or can be very important (loss) preventing stable calls.
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - -
264 / 533 3BK 20918 AAAA PCZZA Ed.06
19 Class 52: BSC-Clock Alarms
19.7.1 Corrective Actions
It is strongly recommended to refit the CLK-REP, extracting the Ater clock bythe DTC from 2 Mbit trunks (three are available per CLK-GEN) as indicated bythe ’Friendly Name’ on the OMC-R or ’Suspect RIT’ on the LMT.
[52,6] BSC−RUN−ON−LOCAL−CLK
Solve DTC/Ater alarm(s) first
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
DTC/Ateralarm
events?
no
yes
Solve transmission alarm(s)
Transmissionalarm
events?
no
yes
Trigger clock source checks at MSC side
Figure 99: BSC-RUN-ON-LOCAL-CLK: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 265 / 533
19 Class 52: BSC-Clock Alarms
19.8 [52,7] LOC-CLK-FAILURE
specificProblems: LOC-CLK-FAILURE
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Major (PMA)
Alarm Description Due to detection of the Local Clock Failure the CLK-GEN is degraded.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
19.8.1 Corrective Actions
[52,7] LOC−CLK−FAILURE
Analyze additional information bytes
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
On−site
Replace suspected Clock RIT
Figure 100: LOC-CLK-FAILURE: Corrective Actions
266 / 533 3BK 20918 AAAA PCZZA Ed.06
20 Class 53: Broadcast-Bus Alarms
20 Class 53: Broadcast-Bus Alarms
This section defines the BSC alarms for the Class 53: Broadcast–Bus alarmclass.
3BK 20918 AAAA PCZZA Ed.06 267 / 533
20 Class 53: Broadcast-Bus Alarms
20.1 [53,0] LOSS-OF-ONE-BROAD-BUS-BSC
specificProblems: LOSS-OF-ONE-BROAD-BUS-BSC
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Major (PMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description The BSC has detected loss of one BC bus in the BSC.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
20.1.1 Corrective Actions
[53,0] LOSS−OF−ONE−BROAD−BUS−BSC
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
On−site
Replace suspected RIT
The Broadcast Bus is indicated by the BC−SYS−BUS SBL number.
Figure 101: LOSS-OF-ONE-BROAD-BUS-BSC: Corrective Actions
268 / 533 3BK 20918 AAAA PCZZA Ed.06
20 Class 53: Broadcast-Bus Alarms
20.2 [53,1] LOSS-OF-BOTH-BROAD-BUS-BSC
specificProblems: LOSS-OF-BOTH-BROAD-BUS-BSC
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Critical (VPMA) - in commercial use, Warning (MI) - out of commercialuse
Alarm Description The BSC has detected loss of both broadcast buses in the BSC.
Impact on System There are significant telecom impacts: LAC paging mode is not workinganymore, thus preventing Mobile terminating calls. GPRS resetprocedure does not work anymore and leads to loss of GPRS traffic.For the consequences of an SBL state change, see Consequences ofan SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - -
20.2.1 Corrective Actions
[53,1] LOSS−OF−BOTH−BROAD−BUS−BSC
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
On−site
G2: Replace both BCLA−SYS boards
Figure 102: LOSS-OF-BOTH-BROAD-BUS-BSC: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 269 / 533
20 Class 53: Broadcast-Bus Alarms
20.3 [53,2] DMA-PROBLEM
20.3.1 [53,2] DMA-PROBLEM (BSC)
specificProblems: DMA-PROBLEM
eventType: Communication
probableCause: CommunicationSubsystemFailure
perceivedSeverity: Major (PMA)
Alarm Description The BSC has detected DMA problems in a high percentage of CEsin the BSC.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
20.3.1.1 Corrective ActionsContact your Alcatel system support.
270 / 533 3BK 20918 AAAA PCZZA Ed.06
20 Class 53: Broadcast-Bus Alarms
20.3.2 [53,2] DMA-PROBLEM (CPR/DTC/TCU)
specificProblems: DMA-PROBLEM
eventType: Communication
probableCause: CommunicationSubsystemFailure
perceivedSeverity: Minor (DMA)
Alarm Description The BSC has detected a high number of DMA problems in the CE.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
20.3.2.1 Corrective Actions
[53,2] DMA−PROBLEM (CPR/DTC/TCU)
Alarmsolved
yesAlarm persists?
no ContactSystem Support
DMA−PROBLEM (BSC) alarm
events?
no
yes
On−site
Replace suspected
CPR/DTC/TCU
Figure 103: DMA-PROBLEM (CPR/DTC/TCU): Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 271 / 533
20 Class 53: Broadcast-Bus Alarms
20.4 [53,3] LOSS-OF-ONE-BROAD-BUS-RACK
specificProblems: LOSS-OF-ONE-BROAD-BUS-RACK
eventType: Equipment
probableCause: LanError
perceivedSeverity: Major (PMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description The BSC has detected a loss of one broadcast bus on a RACK.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
20.4.1 Corrective Actions
[53,3] LOSS−OF−ONE−BROAD−BUS−RACK
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
On−site
Replace suspected RIT
The Broadcast Bus is indicated by the BC_RACK_BUS SBL number.
Figure 104: LOSS-OF-ONE-BROAD-BUS-RACK: Corrective Actions
272 / 533 3BK 20918 AAAA PCZZA Ed.06
20 Class 53: Broadcast-Bus Alarms
20.5 [53,4] LOSS-OF-BOTH-BROAD-BUS-RACK
specificProblems: LOSS-OF-BOTH-BROAD-BUS-RACK
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Critical (VPMA) - in commercial use, Warning (MI) - out of commercialuse
Alarm Description The BSC has detected loss of both broadcast buses on a RACK.
Impact on System There are significant telecom impacts: LAC paging mode is not workinganymore, thus preventing Mobile terminating calls. GPRS resetprocedure does not work anymore and leads to loss of GPRS traffic.For the consequences of an SBL state change, see Consequences ofan SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - -
20.5.1 Corrective Actions
[53,4] LOSS−OF−BOTH−BROAD−BUS−RACK
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
On−site
G2: Replace both BCLA boards
Figure 105: LOSS-OF-BOTH-BROAD-BUS-RACK: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 273 / 533
20 Class 53: Broadcast-Bus Alarms
20.6 [53,5] DEGRAD-BROAD-BUS-RACK
specificProblems: DEGRAD-BROAD-BUS-RACK
eventType: Equipment
probableCause: LanError
perceivedSeverity: Minor (DMA)
Alarm Description The BSC has detected a degradation in the quality of one of thebroadcast buses on a RACK.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
20.6.1 Corrective Actions
[53,5] DEGRAD−BROAD−BUS−RACK
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
On−site
Replace suspected RIT
The Broadcast Bus is indicated by the BC_RACK_BUS SBL number.
Figure 106: DEGRAD-BROAD-BUS-RACK: Corrective Actions
274 / 533 3BK 20918 AAAA PCZZA Ed.06
20 Class 53: Broadcast-Bus Alarms
20.7 [53,6] LOSS-OF-ONE-BROAD-BUS-CE
specificProblems: LOSS-OF-ONE-BROAD-BUS-CE
eventType: Equipment
probableCause: LanError
perceivedSeverity: Minor (DMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description The BSC has detected loss of one broadcast bus to a CE.
Impact on System No redundancy on broadcast bus. For the consequences of an SBLstate change, see Consequences of an SBL State Change (Section30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
20.7.1 Corrective Actions
broadcase board and the concerned CE board.Figure 107: LOSS-OF-ONE-BROAD-BUS-CE: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 275 / 533
20 Class 53: Broadcast-Bus Alarms
20.8 [53,7] LOSS-OF-BOTH-BROAD-BUS-CE
specificProblems: LOSS-OF-BOTH-BROAD-BUS-CE
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Critical (VPMA) - in commercial use, Warning (MI) - out of commercialuse
Alarm Description The BSC has detected loss of both broadcast buses to a CE.
Impact on System There are significant telecom impacts: LAC paging mode is not workinganymore, thus preventing Mobile terminating calls. GPRS resetprocedure does not work anymore and leads to loss of GPRS traffic.For the consequences of an SBL state change, see Consequences ofan SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - -
20.8.1 Corrective Actions
[53,7] LOSS−OF−BOTH−−BROAD−BUS−CE
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
On−site
Replace suspected RIT
The Broadcast Bus is indicated by the BC_RACK_BUS SBL number.
Figure 108: LOSS-OF-BOTH-BROAD-BUS-CE: Corrective Actions
276 / 533 3BK 20918 AAAA PCZZA Ed.06
20 Class 53: Broadcast-Bus Alarms
20.9 [53,8] DEGRAD-BROAD-BUS-CE
specificProblems: DEGRAD-BROAD-BUS-CE
eventType: Equipment
probableCause: LanError
perceivedSeverity: Minor (DMA)
Alarm Description The BSC has detected a degradation in the quality of one of thebroadcast buses to a CE.
Impact on System Some broadcasted messages may be lost for this CE, for example,some paging messages can be lost . For the consequences of an SBLstate change, see Consequences of an SBL State Change (Section30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - -
20.9.1 Corrective Actions
[53,8] DEGRAD−BROAD−BUS−CE
Alarmsolved
yesAlarm
persists?
no
DEGRAD−BROAD−BUS−RACK alarm
events?
no
yes
ContactSystem Support
On−site
G2: Replace suspected
broadcast bus RIT
Figure 109: DEGRAD-BROAD-BUS-CE: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 277 / 533
20 Class 53: Broadcast-Bus Alarms
278 / 533 3BK 20918 AAAA PCZZA Ed.06
21 Class 54: BTS-EXTRA-TS-POOL Alarms
21 Class 54: BTS-EXTRA-TS-POOL Alarms
This section defines the BTS pool alarms for the Class 54: BTS-POOL alarmclass.
3BK 20918 AAAA PCZZA Ed.06 279 / 533
21 Class 54: BTS-EXTRA-TS-POOL Alarms
21.1 [54,1] EXTRA TS NOT FULLY USABLE
specificProblems: EXTRA ABIS TIME SLOT NOT FULLY USABLE
eventType: QualityOfService
probableCause: TCU or the second Abis link failure
perceivedSeverity: Minor (DMA)
Alarm Description In case of TCU failure/end failure, 2nd Abis failure/end failure orBTS config-complete, the alarm is evaluated. This alarm is on BTSlevel, linked to a new SBL BTS-POOL per BTS. The new addedSBL, BTS-POOL, is always IT and not involved in SBL-state-audit,Furthermore, no operation on the SBL is allowed.
Impact on System The new added SBL does not impact MAINT/ALARM modules. InOMC side, after HW audit, if the BTS is type of Evolium, OMC createsBTS-POOL for that BTS. And OMC will clear the alarm in case of alarmaudit or receiving END alarm.
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
280 / 533 3BK 20918 AAAA PCZZA Ed.06
21 Class 54: BTS-EXTRA-TS-POOL Alarms
21.1.1 Corrective Actions
Figure 110: EXTRA TS NOT FULLY USABLE: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 281 / 533
21 Class 54: BTS-EXTRA-TS-POOL Alarms
282 / 533 3BK 20918 AAAA PCZZA Ed.06
22 Class 66: TSC-TRUNK Alarms
22 Class 66: TSC-TRUNK Alarms
This section defines the TC alarms for the Class 66: TSC–TRUNK alarm class.
3BK 20918 AAAA PCZZA Ed.06 283 / 533
22 Class 66: TSC-TRUNK Alarms
22.1 [66,21] LOOP-TO-ITF
specificProblems: LOOP-TO-ITF
eventType: Equipment
probableCause: EquipmentUnderTest
perceivedSeverity: Major (PMA)
Alarm Description An external loop is activated. A loop cannot be activated/deactivatedusing the OMC-R.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
ABIS-HWAY-TP
Loss -
Degradation - - - - -
SBL A-PCM-TP and SBL ATER-HWAY-TP
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
22.1.1 Corrective Actions
[66,21] LOOP−TO−ITF
Remove the loopback settings, though normal conditions return
after a preset control timeout.
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
Figure 111: LOOP-TO-ITF: Corrective Actions
284 / 533 3BK 20918 AAAA PCZZA Ed.06
22 Class 66: TSC-TRUNK Alarms
22.2 [66,22] LOOP-TO-EQUIP
specificProblems: LOOP-TO-EQUIP
eventType: Equipment
probableCause: EquipmentUnderTest
perceivedSeverity: Major (PMA)
Alarm Description An external loop is activated. A loop cannot be activated/deactivatedusing the OMC-R.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
ABIS-HWAY-TP
Loss -
Degradation - - - - -
SBL A-PCM-TP and SBL ATER-HWAY-TP
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
22.2.1 Corrective Actions
[66,22] LOOP−TO−EQUIP
Remove the loopback settings, though normal conditions return
after a preset control timeout.
Alarmsolved
yes
Alarm persists?
no
ContactSystem Support
Figure 112: LOOP-TO-EQUIP: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 285 / 533
22 Class 66: TSC-TRUNK Alarms
22.3 [66,50] TWO-MB-MISSING
specificProblems: TWO-MB-MISSING
eventType: Communication
probableCause: LossOfSignal
perceivedSeverity: Major (PMA)
Alarm Description Loss of an incoming 2M signal. The loss of the incoming digital signalat 2048 kbit/s is considered as loss of an incoming 2M signal.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
ABIS-HWAY-TP
Loss -
Degradation - - - - -
SBL A-PCM-TP and SBL ATER-HWAY-TP
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - -
Degradation - - - - -
286 / 533 3BK 20918 AAAA PCZZA Ed.06
22 Class 66: TSC-TRUNK Alarms
22.3.1 Corrective Actions
[66,50] TWO−MB−MISSING
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
ABIS/APCM/ATER alarm
events?
no
yes
Repair/replace Receiver
2M link−related
alarm events?
no
yes
On−site
Alarmsolved
Alarm persists?
noyes
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local trunk cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 113: TWO-MB-MISSING: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 287 / 533
22 Class 66: TSC-TRUNK Alarms
22.4 [66,66] AIS-2-MB
specificProblems: AIS-2-MB
eventType: Communication
probableCause: LocalNodeTransmissionError
perceivedSeverity: Minor (DMA)
Alarm Description The 2 Mbit/s interface is receiving an AIS signal ’all ones indication’.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
ABIS-HWAY-TP
Loss -
Degradation - - - - -
SBL A-PCM-TP and SBL ATER-HWAY-TP
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - -
Degradation - - - - -
288 / 533 3BK 20918 AAAA PCZZA Ed.06
22 Class 66: TSC-TRUNK Alarms
22.4.1 Corrective Actions
[66,66] AIS−2−MB
Remove loop
Solve that alarm(s)
Contact
System Support
ABIS/
APCM/ATER alarm
events?
no
yes
Loop
activated?
no
yes
Alarm
solved
Alarm
persists?
no
yes
Alarm
solved
Alarm
persists?
no
yes
Trigger remote signal
path and transmitter
tests on MSC side
Figure 114: AIS-2-MB: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 289 / 533
22 Class 66: TSC-TRUNK Alarms
22.5 [66,81] FRAME-ALIGNMENT
specificProblems: FRAME-ALIGNMENT
eventType: Communication
probableCause: LossOfFrame
perceivedSeverity: Major (PMA)
Alarm Description The 2 Mbit/s signal frame alignment is lost. Traffic is not possible. TS 0is reserved for frame alignment, alarms and network synchronizationinformation and should not be used for Signaling or speech purposes.The frame alignment signal is monitored to determine if the framealignment has been lost. The frame alignment will be assumed to havebeen lost when three consecutive incorrect frame alignment signalshave been received.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
ABIS-HWAY-TP
Loss -
Degradation - - - - -
SBL A-PCM-TP and SBL ATER-HWAY-TP
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
290 / 533 3BK 20918 AAAA PCZZA Ed.06
22 Class 66: TSC-TRUNK Alarms
22.5.1 Corrective Actions
[66,81] FRAME−ALIGNMENT
Correct timeslot 0 settings
Solve that alarm(s)
ContactSystem Support
ABIS/APCM/ATER alarm
events?
no
yes
Timeslot 0 settings
OK?
no
yes
Alarm persists?
no
Alarmsolved
Alarm persists?
no
yes
Trigger remote signal path and transmitter tests on MSC side
yes
Figure 115: FRAME-ALIGNMENT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 291 / 533
22 Class 66: TSC-TRUNK Alarms
22.6 [66,86] CRC-MFRAME-ALIGNMENT
specificProblems: CRC-MFRAME-ALIGNMENT
eventType: Communication
probableCause: LossOfFrame
perceivedSeverity: Major (PMA)
Alarm Description Expected patterns not received on TS0 of the PCM (CRC multiframe).The CRC is not used in the remote end or there may be interferenceson the connection.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
ABIS-HWAY-TP
Loss -
Degradation - - - - -
SBL A-PCM-TP and SBL ATER-HWAY-TP
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
292 / 533 3BK 20918 AAAA PCZZA Ed.06
22 Class 66: TSC-TRUNK Alarms
22.6.1 Corrective Actions
[66,86] CRC−MFRAME−ALIGNMENT
Correct timeslot 0 CRC settings
ContactSystem Support
Timeslot 0 CRC settings
OK?
no
yes
Alarm persists?
no
yes
Alarmsolved
Alarm persists?
no
yes
Trigger tests of remote CRC activation on MSC side
Figure 116: CRC-MFRAME-ALIGNMENT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 293 / 533
22 Class 66: TSC-TRUNK Alarms
22.7 [66,99] BER-10E-3
specificProblems: BER-10E-3
eventType: Communication
probableCause: DegradedSignal
perceivedSeverity: Major (PMA)
Alarm Description Signal input BER worse than 1 in 1000. The error rate of the incomingmain system signal is worse than the preset threshold value of 10E-3.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
ABIS-HWAY-TP
Loss -
Degradation - - - - -
SBL A-PCM-TP and SBL ATER-HWAY-TP
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
294 / 533 3BK 20918 AAAA PCZZA Ed.06
22 Class 66: TSC-TRUNK Alarms
22.7.1 Corrective Actions
[66,99] BER−10E−3
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
ABIS/APCM/ATER alarm
events?
no
yes
Repair/replace Receiver
Link−relatedalarm events?
no
yes
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)
Related receiver alarm
events?
no
yes
Local trunk cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 117: BER-10E-3: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 295 / 533
22 Class 66: TSC-TRUNK Alarms
22.8 [66,100] BER-10E-4
specificProblems: BER-10E-4
eventType: Communication
probableCause: DegradedSignal
perceivedSeverity: Minor (DMA)
Alarm Description Signal input BER worse than 1 in a 10000. The error rate of theincoming main system signal is worse than the preset threshold valueof 10E-4.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
296 / 533 3BK 20918 AAAA PCZZA Ed.06
22 Class 66: TSC-TRUNK Alarms
22.8.1 Corrective Actions
[66,100] BER−10E−4
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
ABIS/APCM/ATER alarm
events?
no
yes
Repair/replace Receiver
Link−relatedalarm events?
no
yes
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Localtrunk cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 118: BER-10E-4: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 297 / 533
22 Class 66: TSC-TRUNK Alarms
22.9 [66,102] BER-10E-6
specificProblems: BER-10E-6
eventType: Communication
probableCause: DegradedSignal
perceivedSeverity: Minor (DMA)
Alarm Description Signal input BER worse than 1 in a million. The error rate of theincoming main system signal is worse than the preset threshold valueof 10E-6.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
298 / 533 3BK 20918 AAAA PCZZA Ed.06
22 Class 66: TSC-TRUNK Alarms
22.9.1 Corrective Actions
[66,102] BER−10E−6
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
ABIS/APCM/ATER alarm
events?
no
yes
Repair/replace Receiver
Link−relatedalarm events?
no
yes
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local trunk cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 119: BER-10E-6: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 299 / 533
22 Class 66: TSC-TRUNK Alarms
22.10 [66,176] FAR-END-ALARM
specificProblems: FAR-END-ALARM
eventType: Communication
probableCause: LocalNodeTransmissionError
perceivedSeverity: Minor (DMA)
Alarm Description The equipment at the remote end has acknowledged the faultycondition of the interface signal. Alarm indication from the remote endis detected when bit 3 of channel TS 0 changes state from 0 to 1 inthose frames not containing the frame alignment signal.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
ABIS-HWAY-TP
Loss -
Degradation - - - - -
SBL A-PCM-TP and SBL ATER-HWAY-TP
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
300 / 533 3BK 20918 AAAA PCZZA Ed.06
22 Class 66: TSC-TRUNK Alarms
22.10.1 Corrective Actions
[66,176] FAR−END−
ALARM
Solve that alarm(s)
Contact
System Support
ABIS/
APCM/ATER alarm
events?
no
yes
Alarm
solved
Alarm
persists?
no
yes
Solve that alarm(s)
Related
receiver alarm
events?
no
yes
Trigger remote signal
path and transmitter
tests on MSC side
Figure 120: FAR-END-ALARM: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 301 / 533
22 Class 66: TSC-TRUNK Alarms
22.11 [66,208] I1I2-AIS
specificProblems: I1I2-AIS
eventType: Communication
probableCause: LocalNodeTransmissionError
perceivedSeverity: Minor (DMA)
Alarm Description An AIS was received on the time slot carrying tributary informationon the Ater Mux Interface. The AIS condition is detected on the TSwhich carries the tributary information on the Ater Mux interface.If transparent AIS is not detected on TS 0, then the alarm octet ischecked to see if an I1I2_AIS alarm has occurred as redundant AIS.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
302 / 533 3BK 20918 AAAA PCZZA Ed.06
22 Class 66: TSC-TRUNK Alarms
22.11.1 Corrective Actions
[66,208] I1L2−AIS
Remove loop
ContactSystem Support
Ateralarm events?
no
yes
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)
Loop is activated?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 121: I1I2-AIS: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 303 / 533
22 Class 66: TSC-TRUNK Alarms
22.12 [66,210] TRANS-FLT
specificProblems: TRANS-FLT
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Warning (MI)
Alarm Description The PCM event counter threshold value is exceeded, which results inthe generation of this 2 Mbit/s interface alarm. For each PCM event, acounter is increased. At certain intervals, the counter will be decreasedby 1. When the threshold value is exceeded, this alarm is generatedfor the 2 Mbit/s interface.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
304 / 533 3BK 20918 AAAA PCZZA Ed.06
22 Class 66: TSC-TRUNK Alarms
22.12.1 Corrective Actions
[66,210] TRANS−FLT
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
ABIS/APCM/ATER alarm
events?
no
yes
Repair/replace Receiver
Link−relatedalarm events?
no
yes
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local trunk cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 122: TRANS-FLT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 305 / 533
22 Class 66: TSC-TRUNK Alarms
22.13 [66,211] LOSS-OF-CLOCK-2M
specificProblems: LOSS-OF-CLOCK-2M
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Minor (DMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description The 2 MHz clock source is lost. Once the PAD detects the loss of the 2MHz clock source, the next clock source will be selected if available.The firmware will detect the missing clock source number.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
306 / 533 3BK 20918 AAAA PCZZA Ed.06
22 Class 66: TSC-TRUNK Alarms
22.13.1 Corrective Actions
[66,211] LOSS−OF−CLOCK−2M
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
ABIS/APCM/ATER alarm
events?
no
yes
Repair/replace Receiver
Link−relatedalarm events?
no
yes
On−site Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local trunk cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 123: LOSS-OF-CLOCK-2M: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 307 / 533
22 Class 66: TSC-TRUNK Alarms
308 / 533 3BK 20918 AAAA PCZZA Ed.06
23 Class 67: TSC-CHANNEL Alarms
23 Class 67: TSC-CHANNEL Alarms
This section defines the TC alarms for the Class 67: TSC–CHANNEL alarmclass.
3BK 20918 AAAA PCZZA Ed.06 309 / 533
23 Class 67: TSC-CHANNEL Alarms
23.1 [67,22] LOOP-TO-EQUIP
specificProblems: LOOP-TO-EQUIP
eventType: Equipment
probableCause: EquipmentUnderTest
perceivedSeverity: Major (PMA)
Alarm Description A loop has been activated.
A loop cannot be activated/deactivated using the OMC-R.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - - - -
23.1.1 Corrective Actions
[67,22] LOOP−
TO−EQUIP
Remove loop
Contact
System Support
Alarm
solved
Alarm
persists?
no
yes
Figure 124: LOOP-TO-EQUIP: Corrective Actions
310 / 533 3BK 20918 AAAA PCZZA Ed.06
23 Class 67: TSC-CHANNEL Alarms
23.2 [67,65] AIS-64-KB
specificProblems: AIS-64-KB
eventType: Communication
probableCause: LocalNodeTransmissionError
perceivedSeverity: Minor (DMA)
Alarm Description This is an internal BSC alarm.
The A-Interface TCHs are receiving an AIS signal (all ones).
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 311 / 533
23 Class 67: TSC-CHANNEL Alarms
23.2.1 Corrective Actions
[67,65] AIS−64−KB
Solve that alarm(s)
ContactSystem Support
TC−16 alarm events?
no
yes
Repair/replace Receiver
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
LocalAter cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 125: AIS-64-KB: Corrective Actions
312 / 533 3BK 20918 AAAA PCZZA Ed.06
23 Class 67: TSC-CHANNEL Alarms
23.3 [67,72] AIS-16-KB
specificProblems: AIS-16-KB
eventType: Communication
probableCause: LocalNodeTransmissionError
perceivedSeverity: Minor (DMA)
Alarm Description This is an internal BSC alarm.
The Ater-Interface TCHs are receiving an AIS signal (all ones).
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 313 / 533
23 Class 67: TSC-CHANNEL Alarms
23.3.1 Corrective Actions
[67,72] AIS−16−KB
Solve that alarm(s)
ContactSystem Support
TC−16alarm events?
no
yes
Repair/replace Receiver
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local Ater cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 126: AIS-16-KB: Corrective Actions
314 / 533 3BK 20918 AAAA PCZZA Ed.06
23 Class 67: TSC-CHANNEL Alarms
23.4 [67,122] TRAU-SYNCHRO
specificProblems: TRAU-SYNCHRO
eventType: Equipment
probableCause: TimingProblem
perceivedSeverity: Minor (DMA)
Alarm Description This is an internal BSC alarm.
The TRAU cannot synchronize to the BTS. The speech path is brokenbetween the TRE and the Transcoder. This only occurs during callhandling.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 315 / 533
23 Class 67: TSC-CHANNEL Alarms
23.4.1 Corrective Actions
[67,122] TRAU−SYNCHRO
Solve that alarm(s)
ContactSystem Support
BTS/BSC−Adapt alarm events?
no
yes
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)Abis alarm
events?
no
yes
Solve that alarm(s)
TCU/SWITCH/DTC
alarm events?
noyes
Figure 127: TRAU-SYNCHRO: Corrective Actions
316 / 533 3BK 20918 AAAA PCZZA Ed.06
23 Class 67: TSC-CHANNEL Alarms
23.5 [67,128] EQUIPMENT-FAULT
specificProblems: EQUIPMENT-FAULT
eventType: Equipment
probableCause: EquipmentMalfunction
perceivedSeverity: Major (PMA)
Alarm Description An internal fault has been detected on a board.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 317 / 533
23 Class 67: TSC-CHANNEL Alarms
23.5.1 Corrective Actions
[67,131] INT−BUS−FAULT
Alarmsolved
Alarm persists?
no
yes
On−site
Replace DT16/TC−16
Lock TC−16
Alarmsolved
yes
Alarm persists?
no
Unlock TC−16
ContactSystem Support
Alarm persists?
no
yes
On−site
Replace MT120
Lock MT120
yes
Alarm persists?
no
Unlock MT120
G2 TC A925 TC
Figure 128: EQUIPMENT-FAULT: Corrective Actions
318 / 533 3BK 20918 AAAA PCZZA Ed.06
23 Class 67: TSC-CHANNEL Alarms
23.6 [67,130] MEMORY-FAULT
specificProblems: MEMORY-FAULT
eventType: ProcessingError
probableCause: CorruptData
perceivedSeverity: Major (PMA)
Alarm Description An EEPROM memory write access has been unsuccessful.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 319 / 533
23 Class 67: TSC-CHANNEL Alarms
23.6.1 Corrective Actions
[67,130] MEMORY−FAULT
Analyze alarm number
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)DT16/TC−16
alarm events?
no
yes
On−site
Replace DT16/TC−16
Lock TC−16
Alarmsolved
yes
Alarm persists?
no
Unlock TC−16
Figure 129: MEMORY-FAULT: Corrective Actions
320 / 533 3BK 20918 AAAA PCZZA Ed.06
23 Class 67: TSC-CHANNEL Alarms
23.7 [67,131] INT-BUS-FAULT
specificProblems: INT-BUS-FAULT
eventType: ProcessingError
probableCause: CorruptData
perceivedSeverity: Major (PMA)
Alarm Description An internal fault has been detected on board.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 321 / 533
23 Class 67: TSC-CHANNEL Alarms
23.7.1 Corrective Actions
[67,131] INT−BUS−FAULT
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
On−site
Replace DT16/TC−16
Lock TC−16
Alarmsolved
yes
Alarm persists?
no
Unlock TC−16
Figure 130: INT-BUS-FAULT: Corrective Actions
322 / 533 3BK 20918 AAAA PCZZA Ed.06
24 Class 70: TSC-SW-ANOMALY
24 Class 70: TSC-SW-ANOMALY
This section defines the TC alarms for the Class 70: TSC–SW–ANOMALYalarm class.
3BK 20918 AAAA PCZZA Ed.06 323 / 533
24 Class 70: TSC-SW-ANOMALY
24.1 [70,219] SW-FAULT
specificProblems: SW-FAULT
eventType: ProcessingError
probableCause: ApplicationSubsystemFailure
perceivedSeverity: Warning (MI)
Alarm Description The software which runs on the TSCA board detects an error.
Impact On System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
324 / 533 3BK 20918 AAAA PCZZA Ed.06
24 Class 70: TSC-SW-ANOMALY
24.1.1 Corrective Actions
[70,219] SW−FAULT
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
On−site
Replace TSC
Lock TSC
yes
Alarm persists?
no
Unlock TSC
PressTSC reset button
Disengage & replugg TSC
On−site
On−site
Figure 131: SW-FAULT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 325 / 533
24 Class 70: TSC-SW-ANOMALY
326 / 533 3BK 20918 AAAA PCZZA Ed.06
25 Class 71: TSC-ENVIRON
25 Class 71: TSC-ENVIRON
This section defines the TC alarms for the Class 71: TSC–ENVIRON alarmclass.
3BK 20918 AAAA PCZZA Ed.06 327 / 533
25 Class 71: TSC-ENVIRON
25.1 [71,0] POWER-SUPPLY
specificProblems: POWER-SUPPLY
eventType: Equipment
probableCause: PowerProblem
perceivedSeverity: Major (PMA)
Alarm Description An operating voltage is missing or out of range. All or some of thefunctions on the reporting board are not working.
Impact On System If the power supply fails and the CPU on any board is not working, thepower supply alarm may not be sent.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
BTS-ADAPT = FIT
Loss - - - - -
Degradation -
BTS-ADAPT = FLT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
SM-ADAPT = FIT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - -
SM-ADAPT = FLT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
TC-ADAPT = FLT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
328 / 533 3BK 20918 AAAA PCZZA Ed.06
25 Class 71: TSC-ENVIRON
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - (N7) -
Degradation - - - - -
25.1.1 Corrective Actions
[71,0] POWER−SUPPLY
Analyze alarm number
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)Other
alarm on RIT events?
no
yes
On−site
Alarmsolved
yes
Alarm persists?
no
Solve that alarm(s)DC/DC
converter alarm events?
no
yes
On−site
Replace suspected TSS RIT
On−site
Check supply cabling, connectors, fuses
Input voltage on
suspected RITOK
no
yes
Figure 132: POWER-SUPPLY: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 329 / 533
25 Class 71: TSC-ENVIRON
330 / 533 3BK 20918 AAAA PCZZA Ed.06
26 Class 73:BSC-ADAPT
26 Class 73:BSC-ADAPT
This section defines the TC alarms for the Class 73: BSC–ADAPT alarm class.
3BK 20918 AAAA PCZZA Ed.06 331 / 533
26 Class 73:BSC-ADAPT
26.1 [73,22] LOOP-TO-EQUIP
specificProblems: LOOP-TO-EQUIP
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description A loop is activated on one of the eight BSC interfaces. A loop cannotbe activated/deactivated using the OMC-R.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
26.1.1 Corrective Actions
[73,22] LOOP−TO−EQUIP
Remove loopback setting
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
When a loop is activated, it deactivates after a preset control timeout.
Figure 133: LOOP-TO-EQUIP: Corrective Actions
332 / 533 3BK 20918 AAAA PCZZA Ed.06
26 Class 73:BSC-ADAPT
26.2 [73,128] EQUIPMENT-FAULT
specificProblems: EQUIPMENT-FAULT
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description There is a basic operational malfunction. An internal fault has beendetected on board.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 333 / 533
26 Class 73:BSC-ADAPT
26.2.1 Corrective Actions
[73,128] EQUIPMENT−FAULT
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)BIUA
alarm events?
no
yes
On−site
Replace BIUA
Lock BSC−ADAPT
Alarmsolved
yes
Alarm persists?
no
Unlock BSC−ADAPT
Figure 134: EQUIPMENT-FAULT: Corrective Actions
334 / 533 3BK 20918 AAAA PCZZA Ed.06
26 Class 73:BSC-ADAPT
26.3 [73,130] MEMORY-FAULT
specificProblems: MEMORY-FAULT
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description An EEPROM memory write access has been unsuccessful.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 335 / 533
26 Class 73:BSC-ADAPT
26.3.1 Corrective Actions
[73,130] MEMORY−FAULT
Analyze alarm number
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)BIU
alarm events?
no
yes
On−site
Replace BIU
Lock BSC−ADAPT
Alarmsolved
yes
Alarm persists?
no
Unlock BSC−ADAPT
Figure 135: MEMORY-FAULT: Corrective Actions
336 / 533 3BK 20918 AAAA PCZZA Ed.06
26 Class 73:BSC-ADAPT
26.4 [73,148] RESET
specificProblems: RESET
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Warning (MI)
Alarm Description An autonomous load of the CE occurred. The module has undergoneserious service interruption, but has recovered.
The reset_buffer is checked to see if the board leaves the reset mode.After startup, hardware tests on memory and interfaces are performed,and the process jumps to the software entry point.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
26.4.1 Corrective Actions
None, – this alarm reports the autonomous load of the CE only.
See TC Alarms (Section 29.5) for the Alarm number description.
3BK 20918 AAAA PCZZA Ed.06 337 / 533
26 Class 73:BSC-ADAPT
26.5 [73,202] NO-Q1-CONN
specificProblems: NO-Q1-CONN
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description There is a connection problem on the QMux bus, no response isreceived from the network element. The TSC is unable to find any orcertain network elements connected to the primary or secondary bus.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - -
Degradation - - - - -
338 / 533 3BK 20918 AAAA PCZZA Ed.06
26 Class 73:BSC-ADAPT
26.5.1 Corrective Actions
[73,202] NO−Q1−CONN
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)Alarm on
suspected RIT events?
no
yes
On−site
Check/Replace Qmux equipment
yes
Alarm persists?
no
Solve that alarm(s) Transmissionalarm events?
no
yes
Correct Address
Qmux address in DLS
OK?
no
yes
Figure 136: NO-Q1-CONN: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 339 / 533
26 Class 73:BSC-ADAPT
26.6 [73,203] LOSS-OF-ACT
specificProblems: LOSS-OF-ACT
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description Loss of Activity due to link failure. Each incoming BS interface link canbe scanned in order to detect a malfunction (disconnection of a cable).Only one link can be scanned at a time. The firmware gives a resetto this alarm bit. A certain time later, the firmware reads the alarmbit in order to detect a link failure.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
340 / 533 3BK 20918 AAAA PCZZA Ed.06
26 Class 73:BSC-ADAPT
26.6.1 Corrective Actions
[73,203] LOSS−
OF−ACT
Contact
System Support
yes
Solve that alarm(s)
BIUA
alarm
events?
no
yes
Lock
BIUA
Alarm
solved
Alarm
persists?
no
Unlock
BIUA
Solve that alarm(s)
Transmission
alarm
events?
no
yes
Figure 137: LOSS-OF-ACT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 341 / 533
26 Class 73:BSC-ADAPT
26.7 [73,212] LOSS-OF-CLK-8M
specificProblems: LOSS-OF-CLK-8M
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description The BSC-BIE is provided with two external 8 MHz clock references.This alarm is generated when the loss of one of the default clocks isdetected by a PAD.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
342 / 533 3BK 20918 AAAA PCZZA Ed.06
26 Class 73:BSC-ADAPT
26.7.1 Corrective Actions
[73,212] LOSS−OF−CLOCK−8M
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)Clock alarm events?
no
yes
On−site
Replace BCLA
Alarmsolved
yes
Alarm persists?
no
Solve that alarm(s)BCLAalarm
events?
no
yes
Figure 138: LOSS-OF-CLK-8M: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 343 / 533
26 Class 73:BSC-ADAPT
26.8 [73,213] LOSS-OF-CLK-BOTH-8M
specificProblems: LOSS-OF-CLK-BOTH-8M
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description Both 8 MHz clock sources are lost. The internal clock is selected.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
344 / 533 3BK 20918 AAAA PCZZA Ed.06
26 Class 73:BSC-ADAPT
26.8.1 Corrective Actions
[73,213] LOSS−OF−CLOCK−BOTH−8M
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)Clock alarm events?
no
yes
On−site
Replace BCLA
Alarmsolved
yes
Alarm persists?
no
Solve that alarm(s)BCLAalarm
events?
no
yes
Figure 139: LOSS-OF-CLK-BOTH-8M: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 345 / 533
26 Class 73:BSC-ADAPT
26.9 [73,216] RESTART
specificProblems: RESTART
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Warning (MI)
Alarm Description An autonomous restart of the CE has occurred. The operating systemand all processes are re-initialized sequentially. All non-volatileprotected data is cleared and a new initialization of the dynamic datahas taken place
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
26.9.1 Corrective Actions
None – this alarm reports an autonomous restart of the CE only.
346 / 533 3BK 20918 AAAA PCZZA Ed.06
26 Class 73:BSC-ADAPT
26.10 [73,241] SET-PROD-FAIL
specificProblems: SET-PROD-FAIL
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description This alarm indicates the NE settings production has failed. The equipmentsettings are not in line with the DLS.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
26.10.1 Corrective Actions
[73,241] SET−PROD−FAIL
ContactSystem Support
yes
Lock BSC−ADAPT
Alarmsolved
Alarm persists?
no
Unlock BSC−ADAPT
Correct DSL settingsDSL
settings OK?
no
yes
Figure 140: SET-PROD-FAIL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 347 / 533
26 Class 73:BSC-ADAPT
26.11 [73,246] DOWNLOAD-FAIL
specificProblems: DOWNLOAD-FAIL
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description This alarm indicates the programming of the BSC-ADAPT has failed.Modification of BSC-Adapt parameters has occurred in the BSC, anddownloading of the BSC-Adapt has been initiated but has failed.
Impact on System The equipment settings are not in line with the DLS.
See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
348 / 533 3BK 20918 AAAA PCZZA Ed.06
26 Class 73:BSC-ADAPT
26.11.1 Corrective Actions
[73,246] DOWNLOAD−
FAIL
Contact
System Support
yes
Lock
BSC−ADAPT
Alarm
solved
Alarm
persists?
no
Unlock
BSC−ADAPT
Correct DSL settingsDSL
settings OK?
no
yes
Figure 141: DOWNLOAD-FAIL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 349 / 533
26 Class 73:BSC-ADAPT
26.12 [73,247] ACCESS-FAIL
specificProblems: ACCESS-FAIL
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description This alarm indicates the programming of the BSC-ADAPT has failed.Modification of BSC-Adapt parameters has occurred in the BSC andaccess attempts towards the BSC-ADAPT has failed. The equipmentsettings are not in line with the DLS and will be replaced.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
26.12.1 Corrective Actions
[73,247] ACCESS−
FAIL
Contact
System Support
yes
Alarm
solved
Alarm
persists?
no
Solve that alarm(s)TCU/TSL/NE
alarm events?
no
yes
Figure 142: ACCESS-FAIL: Corrective Actions
350 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27 Class 74: BTS-ADAPT
This section defines the TC alarms for the Class 74: BTS–ADAPT alarm class.
3BK 20918 AAAA PCZZA Ed.06 351 / 533
27 Class 74: BTS-ADAPT
27.1 [74,20] BLOCKED-FROM-USE
specificProblems: BLOCKED-FROM-USE
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description Unit is not in use due to a configuration error. If the same time slotsare allocated for two boards, then the allocations on one board areblocked from use.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
352 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27.1.1 Corrective Actions
[74,20] BLOCKED−FROM−USE
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Correct time slotsettings
Time slot settings OK?
no
yes
On−site
Disengage andreplug SMBS board
yes
Alarm persists and SMBS was
powered off/on?
no
Solve that alarm(s)BCLAalarm
events?
no
yes
Figure 143: BLOCKED-FROM-USE: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 353 / 533
27 Class 74: BTS-ADAPT
27.2 [74,22] LOOP-TO-EQUIP
specificProblems: LOOP-TO-EQUIP
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description A loop is activated on the BSC interface link.
A loop cannot be activated/deactivated using the OMC-R.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation -
27.2.1 Corrective Actions
[74,22] LOOP−TO−EQUIP
Remove BSC interface loop
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
When a loop is activated, it deactivates after apreset control timeout.
Figure 144: LOOP-TO-EQUIP: Corrective Actions
354 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27.3 [74,23] TESTMODE
specificProblems: TESTMODE
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description The equipment, or part of it, is under test. Normal operation issuspended.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
27.3.1 Corrective Actions
None – equipment is under test.
See TC Alarms (Section 29.5) for the Alarm number description.
3BK 20918 AAAA PCZZA Ed.06 355 / 533
27 Class 74: BTS-ADAPT
27.4 [74,122] SYNCHRO-AL
specificProblems: SYNCHRO-AL
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description The primary synchronization source is missing or not selected. Themodule switches to the secondary source.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
356 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27.4.1 Corrective Actions
[74,122] SYNCHRO−AL
Contact
System Support
Alarm
solved
Alarm
persists?
no
yes
Solve that alarm(s)Clock alarm
events?
no
yes
On−site
Check/Replace
clock cabling
Alarm
solved
yes
Alarm
persists?
no
Solve that alarm(s)
PCM
alarm
events?
no
yes
Figure 145: SYNCHRO-AL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 357 / 533
27 Class 74: BTS-ADAPT
27.5 [74,124] SYNC-AL-CLOCKR
specificProblems: SYNC-AL-CLOCKR
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description Synchronizing fault in clock recovery has occurred. The synchronizingsignal is missing.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
358 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27.5.1 Corrective Actions
[74,124] SYNC−AL−
CLOCKR
Contact
System Support
Alarm
solved
Alarm
persists?
no
yes
Solve that alarm(s)Clock alarm
events?
no
yes
On−site
Check/Replace
clock cabling
Alarm
solved
yes
Alarm
persists?
no
Solve that alarm(s)
PCM
alarm
events?
no
yes
Correct clock settings
Clock
configuration
settings OK?
no
yes
Figure 146: SYNC-AL-CLOCKR: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 359 / 533
27 Class 74: BTS-ADAPT
27.6 [74,128] EQUIPMENT-FAULT
specificProblems: EQUIPMENT-FAULT
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description There is a basic operational malfunction. An internal fault has beendetected on a board.
Impact on System See Consequences of an SBL State Change (Section 30).
BTS-ADAPT = FLT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
BTS-ADAPT = FIT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation -
360 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27.6.1 Corrective Actions
[74,128] EQUIPMENT−
FAULT
Contact
System Support
Alarm
solved
Alarm
persists?
no
yes
On−site
Replace
suspected RIT
Lock
BTS−ADAPT
Alarm
solved
yes
Alarm
persists?
no
Unlock
BTS−ADAPT
Figure 147: EQUIPMENT-FAULT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 361 / 533
27 Class 74: BTS-ADAPT
27.7 [74,130] MEMORY-FAULT
specificProblems: MEMORY-FAULT
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description An EEPROM memory write access has been unsuccessful.
Impact on System See Consequences of an SBL State Change (Section 30).
BTS-ADAPT = FLT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
BTS-ADAPT = FIT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation -
362 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27.7.1 Corrective Actions
[74,130] MEMORY−FAULT
Analyze alarm number
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)BIU
alarm events?
no
yes
On−site
Replace BIU
Lock BTS−ADAPT
Alarmsolved
yes
Alarm persists?
no
Unlock BTS−ADAPT
Figure 148: MEMORY-FAULT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 363 / 533
27 Class 74: BTS-ADAPT
27.8 [74,139] MISSING-UNIT
specificProblems: MISSING-UNIT
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description A defined slave unit is missing from the configuration. The board isnot connected, no response is received from the slave board. Theaccessed unit is not installed into the configuration although it isdefined as being equipped.
(Transmission equipment is organized into ’master modules’ - thosepolled by the TSC via the Q1 bus - and ’slave modules’ that aremonitored by the master modules).
Impact on System See Consequences of an SBL State Change (Section 30).
BTS-ADAPT=FLT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
BTS-ADAPT=FIT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation -
364 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27.8.1 Corrective Actions
[74,139] MISSING−UNIT
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)BTS RIT alarm events?
no
yes
On−site
Replug/Replace suspected RIT
Lock BTS−ADAPT
yes
Alarm persists?
no
Unlock BTS−ADAPT
Figure 149: MISSING-UNIT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 365 / 533
27 Class 74: BTS-ADAPT
27.9 [74,141] FORCED-CNTRL-ON
specificProblems: FORCED-CNTRL-ON
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description A forced control (loop, changeover, etc.) is activated.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
27.9.1 Corrective Actions
[74,141] FORCED−
CONTROL−ON
Contact
System Support
Alarm
solved
Alarm
persists?
no
yes
Remove
forced controlThe normal condition
returns after a preset timeout.
Figure 150: FORCED-CNTRL-ON: Corrective Actions
366 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27.10 [74,142] INSTALLATION
specificProblems: INSTALLATION
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description Installation incorrectly performed. This alarm can also appears as anevent when the board is manipulated.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 367 / 533
27 Class 74: BTS-ADAPT
27.10.1 Corrective Actions
[74,142] INSTALLATION
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)BTS RIT alarm events?
no
yes
On−site
Replug/Replace suspected RIT
Lock BTS−ADAPT
yes
Alarm persists?
no
Unlock BTS−ADAPT
Figure 151: INSTALLATION: Corrective Actions
368 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27.11 [74,148] RESET
specificProblems: RESET
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Warning (MI)
Alarm Description An autonomous load of the CE occurred. The module has undergoneserious service interruption, but has recovered.
The reset/restart buffer is checked to see if the board leaves the resetmode. After startup, hardware tests on memory and interfaces areperformed, and the process jumps to the software entry point.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
27.11.1 Corrective Actions
None, – this alarm reports the autonomous load of the CE only.
See TC Alarms (Section 29.5) for the Alarm number description.
3BK 20918 AAAA PCZZA Ed.06 369 / 533
27 Class 74: BTS-ADAPT
27.12 [74,159] DIAG-TESTS
specificProblems: DIAG-TESTS
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description A diagnostic test is running.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
27.12.1 Corrective Actions
None – the operator has activated the TEST function to obtain more detailedinformation.
See TC Alarms (Section 29.5) for the Alarm number description.
370 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27.13 [74,202] NO-Q1-CONN
specificProblems: NO-Q1-CONN
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description A connection problem occurred on the Qmux bus, no responsereceived from the network element. The TSC is unable to find any orcertain network elements connected to the primary or secondary bus.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation -
3BK 20918 AAAA PCZZA Ed.06 371 / 533
27 Class 74: BTS-ADAPT
27.13.1 Corrective Actions
[74,202] NO−Q1−CONN
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s) Alarm on BTS RIT events?
no
yes
On−site
Check/Replace Qmux equipment
Alarmsolved
yes
Alarm persists?
no
Solve that alarm(s) Transmission
alarm events?
no
yes
Correct AddressQmux
address in DLS OK?
no
yes
Figure 152: NO-Q1-CONN: Corrective Actions
372 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27.14 [74,241] SET-PROD-FAIL
specificProblems: SET-PROD-FAIL
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description This alarm indicates the NE settings production has failed. Theequipment settings are not in line with the DLS.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 373 / 533
27 Class 74: BTS-ADAPT
27.14.1 Corrective Actions
[74,241] SET−PROD−FAIL
ContactSystem Support
yes
Lock BSC−ADAPT
Alarmsolved
Alarm persists?
no
Unlock BSC−ADAPT
Correct DSL settingsDSL
settings OK?
no
yes
Figure 153: SET-PROD-FAIL: Corrective Actions
374 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27.15 [74,245] LOCAL-REINIT-REQ
specificProblems: LOCAL-REINIT-REQ
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description This alarm indicates programming is required locally. Modification ofBTS-Adapt parameters has occurred in the BSC, but the setting atthe BTS_Adapt must be carried out locally and cannot be carried outremotely. The equipment settings are not in line with the DLS.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 375 / 533
27 Class 74: BTS-ADAPT
27.15.1 Corrective Actions
[74,245] LOCAL−
REINIT−REQ
Contact
System Support
Alarm
solved
Alarm
persists?
no
yes
Correct settings
BTS
parameter settings
OK?
no
yes
Disable BSC−ADAPT
Init BSC−ADAPT
Figure 154: LOCAL-REINIT-REQ: Corrective Actions
376 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27.16 [74,246] DOWNLOAD-FAIL
specificProblems: DOWNLOAD-FAIL
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description This alarm indicates that programming of the BTS-ADAPT has failed.Modification of BTS-Adapt parameters has occurred in the BSC, anddownloading of the BTS_Adapt has been initiated but has failed. Theequipment settings are not in line with the DLS.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 377 / 533
27 Class 74: BTS-ADAPT
27.16.1 Corrective Actions
[74,246] DOWNLOAD−
FAIL
Contact
System Support
Alarm
solved
Alarm
persists?
no
yes
Correct settings
DLS
settings
OK?
no
yes
Lock BSC−ADAPT
Unlock BSC−ADAPT
Figure 155: DOWNLOAD-FAIL: Corrective Actions
378 / 533 3BK 20918 AAAA PCZZA Ed.06
27 Class 74: BTS-ADAPT
27.17 [74,247] ACCESS-FAIL
specificProblems: ACCESS-FAIL
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description This alarm indicates that programming of the BTS-ADAPT has failed.Modification of BTS-Adapt parameters has occurred in the BSC, butaccess towards the BTS-Adapt has failed. The equipment settings arenot in line with the DLS.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss -
Degradation - - - - -
27.17.1 Corrective Actions
[74,247] ACCESS−FAIL
Contact
System Support
Alarm
solved
Alarm
persists?
no
yes
Solve that alarm(s)
TCU/TSL/NE
alarm
events?
no
yes
Figure 156: ACCESS-FAIL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 379 / 533
27 Class 74: BTS-ADAPT
380 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28 Class 75: TCSM-ADAPT
This section defines the TC alarms for the Class 75: TCSM–ADAPT alarmclass.
3BK 20918 AAAA PCZZA Ed.06 381 / 533
28 Class 75: TCSM-ADAPT
28.1 [75,20] BLOCKED-FROM-USE
specificProblems: BLOCKED-FROM-USE
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description Unit is not in use due to a configuration error. If the same time slotsare allocated for two boards, then the allocations on one board areblocked from use.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
28.1.1 Corrective Actions
[75,20] BLOCKED−
FROM−USE
Contact
System Support
Alarm
solved
Alarm
persists?
no
yes
Correct time
slot settings
Time slot
settings OK?
no
yes
Figure 157: BLOCKED-FROM-USE: Corrective Actions
382 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.2 [75,22] LOOP-TO-EQUIP
specificProblems: LOOP-TO-EQUIP
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description A loop is activated.
A loop cannot be activated/deactivated using the OMC-R.
Impact on System See Consequences of an SBL State Change (Section 30).
SM-ADAPT = FLT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
SM-ADAPT = FIT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - -
TC-ADAPT = IT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 383 / 533
28 Class 75: TCSM-ADAPT
28.2.1 Corrective Actions
[75,22] LOOP−TO−EQUIP
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Remove BSC interface loop
Figure 158: LOOP-TO-EQUIP: Corrective Actions
384 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.3 [75,112] FAN-ALARM
specificProblems: FAN-ALARM
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Critical (VPMA)
Alarm Description The Fan rotation speed has been detected to be lower than theminimum threshold value for that speed or a temperature higher thannormal operating value has been detected in the rack.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - - - -
28.3.1 Corrective Actions
[75,112] FAN−ALARM
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Replace fan unit
On−site
Figure 159: FAN-ALARM: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 385 / 533
28 Class 75: TCSM-ADAPT
28.4 [75,122] SYNCHRO-AL
specificProblems: SYNCHRO-AL
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description The primary synchronization source is missing. The module switchesto the secondary source.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
386 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.4.1 Corrective Actions
[75,122] SYNCHRO−AL
Contact
System Support
Alarm
solved
Alarm
persists?
no
yes
Solve that alarm(s)
Clock
alarm
events?
no
yes
On−site
Check/Replace
Clock equipment
Alarm
solved
yes
Alarm
persists?
no
Solve that alarm(s)
PCM
alarm
events?
no
yes
Figure 160: SYNCHRO-AL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 387 / 533
28 Class 75: TCSM-ADAPT
28.5 [75,124] SYNCHRO-AL-CLOCKR
specificProblems: SYNCHRO-CLOCKR
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description Synchronizing fault in clock recovery has occurred. The synchronizingsignal is missing.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
388 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.5.1 Corrective Actions
[75,124] SYNCHRO−
AL−CLOCKR
Contact
System Support
Alarm
solved
Alarm
persists?
no
yes
Solve that alarm(s)
Clock
alarm
events?
no
yes
On−site
Check/Replace
Clock equipment
Alarm
solved
yes
Alarm
persists?
no
Solve that alarm(s)
PCM
alarm
events?
no
yes
Correct clock
configuration settings
Clock
configuration
settings
OK?
no
yes
Figure 161: SYNCHRO-AL-CLOCKR: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 389 / 533
28 Class 75: TCSM-ADAPT
28.6 [75,128] EQUIPMENT-FAULT
specificProblems: EQUIPMENT-FAULT
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description There is a basic operational malfunction. An internal fault has beendetected on a board.
Impact on System See Consequences of an SBL State Change (Section 30).
SM-ADAPT = FLT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
SM-ADAPT = FIT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - -
TC_ADAPT = FLT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - -
390 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.6.1 Corrective Actions
[75,128] EQUIPMENT−FAULT
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Lock SM−ADAPT/TC_ADAP
T
On−site
Replace suspected RIT
Alarmsolved
yes
Alarm persists?
no
Unlock SM−ADAPT/TC_ADAP
T
Figure 162: EQUIPMENT-FAUL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 391 / 533
28 Class 75: TCSM-ADAPT
28.7 [75,130] MEMORY-FAULT
specificProblems: MEMORY-FAULT
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description For G2 TC: an EEPROM memory write access has been unsuccessful.
For A9125 TC: more than one DSP has failed and channels are lost.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
392 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.7.1 Corrective Actions
[75,130] MEMORY−FAULT
Analyze alarm number
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)BIU
alarm events?
no
yes
On−site
Replace BIU
Lock SM−ADAPT/TC−ADAPT
Alarmsolved
yes
Alarm persists?
no
Unlock SM−ADAPT/TC−ADAPT
Reset MT120
Replace MT120
Alarm persists?
Alarm persists?
ContactSystem Support
no
no
yesOn−site
G2 TC A925 TC
Figure 163: MEMORY-FAULT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 393 / 533
28 Class 75: TCSM-ADAPT
28.8 [75,136] FIRST-DSP-FAIL
specificProblems: FIRST-DSP-FAIL
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description One out of the twelve DSPs of a MT120 has failed. All channels ofthis DSP are fully recovered and are now handled by the other elevenDSPs. If no further DSPs have failed (e.g. MEMORY-FAULT) thenthis MT120 is still able to handle all resources (up to 120 channels),but it works in a degraded mode, as it cannot recover any additionalDSP failure.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - -
394 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.8.1 Corrective Actions
[75,136] FIRST−DSP−FAIL
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
On−site
Replace MT120
Alarmsolved
yes
Alarm persists?
no
Reset MT120
Figure 164: FIRST-DSP-FAIL: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 395 / 533
28 Class 75: TCSM-ADAPT
28.9 [75,139] MISSING-UNIT
specificProblems: MISSING-UNIT
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description A defined slave unit is missing from the configuration. The slave boardis not connected, there is no response received from the slave board.The accessed unit is not installed into the configuration although itis defined to be equipped.
(Transmission equipment is organized into ’master modules’ - thosepolled by the TSC via the Q1 bus - and ’slave modules’ that aremonitored by the master modules).
Impact on System See Consequences of an SBL State Change (Section 30).
SM-ADAPT = FIT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
TC-ADAPT = FLT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
396 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.9.1 Corrective Actions
[75,139] MISSING−UNIT
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)BTS RIT alarm events?
no
yes
On−site
Replug/Replace suspected RIT
Lock SM−ADAPT/TC−ADAPT
yes
Alarm persists?
no
Unlock SM−ADAPT/TC−ADAPT
Figure 165: MISSING-UNIT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 397 / 533
28 Class 75: TCSM-ADAPT
28.10 [75,141] FORCED-CNTRL-ON
specificProblems: FORCED-CNTRL-ON
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description Forced control (loop, changeover etc.) is activated.
Impact on System See Consequences of an SBL State Change (Section 30).
SM_ADAPT = FLT
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - -
Degradation - - - - -
SM_ADAPT = FIT
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - -
TC_ADAPT = FLT
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - - -
398 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.10.1 Corrective Actions
[75,141] FORCED−CONTROL−ON
ContactSystem Support
Alarmsolved
Alarm persists?
no yes
Remove forced control
The normal condition returns after a preset timeout.
Figure 166: FORCED-CNTRL-ON: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 399 / 533
28 Class 75: TCSM-ADAPT
28.11 [75,142] INSTALLATION
specificProblems: INSTALLATION
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description Installation incorrectly performed, or appears as an event when theboard is manipulated.
Impact on System See Consequences of an SBL State Change (Section 30).
SBL SM-ADAPT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
SBL TC-ADAPT
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - -
400 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.11.1 Corrective Actions
[75,142] INSTALLATION
ContactSystem Support
Alarmsolved
Alarm persists?
no
yes
Solve that alarm(s)
Alarm on suspected
RIT events?
no
yes
On−site
Replug/Replace suspected RIT
Lock SM−ADAPT/TC−ADAPT
yes
Alarm persists?
no
Unlock SM−ADAPT/TC−ADAPT
Figure 167: INSTALLATION: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 401 / 533
28 Class 75: TCSM-ADAPT
28.12 [75,148] RESET
specificProblems: RESET
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Warning (MI)
Alarm Description An autonomous load of the CE occurred. The module has undergoneserious service interruption, but has recovered.
The reset_buffer is checked to see if the board leaves the reset mode.After startup, hardware tests on memory and interfaces are performed,and the process jumps to the software entry point.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
28.12.1 Corrective Actions
None, – this alarm reports the autonomous load of the CE only.
See TC Alarms (Section 29.5) for the Alarm number description.
402 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.13 [75,159] DIAG-TESTS
specificProblems: DIAG-TESTS
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description A diagnostic test is running.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
28.13.1 Corrective Actions
None – the operator has activated the TEST function to obtain more detailedinformation.
See TC Alarms (Section 29.5) for the Alarm number description.
3BK 20918 AAAA PCZZA Ed.06 403 / 533
28 Class 75: TCSM-ADAPT
28.14 [75,202] NO-Q1-CONN
specificProblems: NO-Q1-CONN
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description No response received from the network element. The TSC is unableto find any or certain network elements connected to the primary orsecondary bus.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - - - -
404 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.14.1 Corrective Actions
[75,202] NO−Q1−CONN
ContactSystem Support
Alarmsolved
Alarm persists?
no yes
Solve that alarm(s) alarm on
suspected RIT events?
no
yes
On−site
Check/Replace Qmux equipment
yes
Alarm persists?
no
Solve that alarm(s) Transmissionalarm events?
no
yes
Correct Address
Qmux address in DLS
OK?
yes
no
Figure 168: NO-Q1-CONN: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 405 / 533
28 Class 75: TCSM-ADAPT
28.15 [75,208] TRIB-TRANS-FLT
specificProblems: TRIB-TRANS-FLT
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Warning (MI)
Alarm Description The PCM event counter threshold value is exceeded on one tributaryinterface, which results in the generation of this 2 Mbit/s alarm. Foreach PCM event, a counter is increased. At certain intervals, thecounter will be decreased by 1. When the threshold value is exceeded,this alarm is generated for that 2 Mbit/s interface.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
406 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.15.1 Corrective Actions
[75,208] TRIB−TRANS−FLT
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
PCMalarm events?
no
yes
Repair/replace Tributary interface
Link−related alarm events?
no
yes
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Tributary interface
operational?
no yes
Solve that alarm(s)Related
tributary alarm events?
no
yes
Local tributary cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 169: TRIB-TRANS-FLT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 407 / 533
28 Class 75: TCSM-ADAPT
28.16 [75,209] INT-BUS-FLT-G25
specificProblems: INT-BUS-FLT-G25
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description An internal bus fault has occurred on one or both TCIL links (internalO&M; bus between MT120) inside the A9125 TC rack. The TCIL linksare duplicated HDLC multi-master busses. These TCIL links conveyinternal messages as well as external Qmux messages (coming fromthe TSC). In case of the bus not working, Qmux polling of boards notdirectly receiving the primary or secondary links, cannot be done.The O&M; data flow is broken, the rack cannot be supervised, butthe telecom data path still works.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - - - -
408 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.16.1 Corrective Actions
[75,209] INT−BUS−FLT−G25
Board ataddress 75?
ContactSystem Support
MT120 highestaddress?
MT120lowest
address?
Board at address16?
Put a spareat address 16
Put a spareat address 75
Replace MT120
Last boardwith
alarm?
Alarmsolved
Alarm persists?
Replace MT120
Alarm persists?
yes
yes
yes
yes
no
no
no
no
no
Alarmsolved
no
yes no
Figure 170: INT-BUS-FLT-G25: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 409 / 533
28 Class 75: TCSM-ADAPT
28.17 [75,210] ATER-TRANS-FLT
specificProblems: ATER-TRANS-FLT
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Warning (MI)
Alarm Description The PCM event counter threshold value is exceeded on one ATERinterface, which results in the generation of this 2 Mbit/s alarm. Foreach PCM event, a counter is increased. At certain intervals, thecounter will be decreased by 1. When the threshold value is exceeded,this alarm is generated for that 2 Mbit/s interface.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
410 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.17.1 Corrective Actions
[75,210] ATER−TRANS−FLT
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
PCM/ATER alarm events?
no
yes
Repair/replace Ater interface
Other Ater alarm
events?
no
yes
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Ater interface
operational?
no yes
Solve that alarm(s)Ater
interface alarm events?
no
yes
Local Ater cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 171: ATER-TRANS-FLT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 411 / 533
28 Class 75: TCSM-ADAPT
28.18 [75,211] LOSS-OF-CLOCK-2M
specificProblems: LOSS-OF-CLOCK-2M
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA) - in commercial use, Warning (MI) - out of commercial use
Alarm Description The 2 MHz clock source is lost. Once the PAD detects the loss of the2 MHz clock source, the next clock source will be selected if available.The firmware will detect the missing clock source number.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
412 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.18.1 Corrective Actions
[75,211] LOSS−OF−CLOCK−2M
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
APCM alarm events?
no
yes
Repair/replace Receiver
Link related alarm
events?
no
yes
On−site Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local trunk cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 172: LOSS-OF-CLOCK-2M: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 413 / 533
28 Class 75: TCSM-ADAPT
28.19 [75,216] RESTART
specificProblems: RESTART
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Warning (MI)
Alarm Description An autonomous processor restart has occurred. The operating systemand all processes are re-initialized sequentially. A new initializationof the dynamic data takes place.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
28.19.1 Corrective Actions
None – this alarm reports an autonomous restart of the CE only.
See TC Alarms (Section 29.5) for the Alarm number description.
414 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.20 [75,221] TRIB-TWO-MB-MISSING
specificProblems: TRIB-TWO-MB-MISSING
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description The 2 Mbit/s on one tributary interface is not receiving a signal. Theloss of the incoming digital signal at 2048 kbit/s is considered as aloss of the incoming 2M signal.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 415 / 533
28 Class 75: TCSM-ADAPT
28.20.1 Corrective Actions
[75,221] TRIB−TWO−MB−MISSING
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
SM−ADAPTalarm events?
no
yes
Repair/replace Receiver
Link related alarm
events?
no
yes
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 173: TRIB-TWO-MB-MISSING: Corrective Actions
416 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.21 [75,222] TRIB-AIS-2MB
specificProblems: TRIB-AIS-2MB
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description The 2 Mbit/s on one tributary interface is receiving an AIS signal (all ones).
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
28.21.1 Corrective Actions
[75,222] TRIB−AIS−2MB
Remove loop
Correct transmission settings
ContactSystem Support
Transmission signal settings
OK?
no
yes
Loop activated?
no
yes
Alarmsolved
Alarm persists?
no yes
Solve that alarm(s)Remote
transmitter alarm(s) events?
no
yes
Trigger remote transmitter test
Figure 174: TRIB-AIS-2MB: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 417 / 533
28 Class 75: TCSM-ADAPT
28.22 [75,223] TRIB-FRAME-ALIGNMENT
specificProblems: TRIB-OF-FRAME-ALIGNMENT
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description The 2 Mbit/s signal frame alignment on one tributary interface is lost.Traffic is not possible. TS0 is reserved for frame alignment, alarmsand network synchronization information and should not be usedfor Signaling or speech purposes. The frame alignment signal ismonitored to determine if the frame alignment has been lost. The framealignment will be assumed to have been lost when three consecutiveincorrect frame alignment signals have been received.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
418 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.22.1 Corrective Actions
[75,223] TRIB−FRAME−ALIGNMENT
Remove loop
Correct transmission settings
ContactSystem Support
Transmission signal settings
OK?
no
yes
Loop activated?
no
yes
Alarmsolved
Alarm persists?
no yes
Solve that alarm(s)Remote
transmitter alarm(s) events?
no
yes
Trigger remote transmitter test
Figure 175: TRIB-FRAME-ALIGNMENT: Corrective Actions
3BK 20918 AAAA PCZZA Ed.06 419 / 533
28 Class 75: TCSM-ADAPT
28.23 [75,224] TRIB-CRC-MFRAME-ALGN
specificProblems: TRIB-CRC-MFRAME-ALGN
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description The expected patterns not received on TS0 of the PCM (CRCmultiframe) on one tributary interface. The CRC is not used in theremote end or there may be interferences on the connection.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
28.23.1 Corrective Actions
[75,224] TRIB−CRC−MFRAME−ALGN
Correct CRC settings
ContactSystem Support
Time slot 0 CRCl settings
OK?
no
yes
Alarmsolved
Alarm persists?
no yes
Solve that alarm(s)Remote
CRC alarm(s) events?
no
yes
Trigger remote signal path tests
Figure 176: TRIB-CRC-MFRAME-ALGN: Corrective Actions
420 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.24 [75,225] TRIB-BER-10E-3
specificProblems: TRIB-BER-10E-3
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description The signal input BER is worse than 1 in 1000 on one tributary interface.The error rate of the incoming main system signal is worse than thepreset threshold value of 10E-3.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 421 / 533
28 Class 75: TCSM-ADAPT
28.24.1 Corrective Actions
[75,225] TRIB−BER−10E−3
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
SM−ADAPTalarm events?
no
yes
Repair/replace Receiver
Link related alarm
events?
no
yes
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 177: TRIB-BER-10E-3: Corrective Actions
422 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.25 [75,226] TRIB-BER-10E-4
specificProblems: TRIB-BER-10E-4
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description Signal input BER worse than 1 in a 10000 on one tributary interface.The error rate of the incoming main system signal is worse than thepreset threshold value of 10E-4.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 423 / 533
28 Class 75: TCSM-ADAPT
28.25.1 Corrective Actions
[75,226] TRIB−BER−10E−4
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
SM−ADAPTalarm events?
no
yes
Repair/replace Receiver
Link related alarm
events?
no
yes
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 178: TRIB-BER-10E-4: Corrective Actions
424 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.26 [75,227] TRIB-BER-10E-6
specificProblems: TRIB-BER-10E-6
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description Signal input BER worse than 1 in a million on one tributary interface.The error rate of the incoming main system signal is worse than thepreset threshold value of 10E-6.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 425 / 533
28 Class 75: TCSM-ADAPT
28.26.1 Corrective Actions
[75,227] TRIB−BER−10E−6
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
SM−ADAPTalarm events?
no
yes
Repair/replace Receiver
Link related alarm
events?
no
yes
On−site Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 179: TRIB-BER-10E-6: Corrective Actions
426 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.27 [75,228] TRIB-FAR-END-ALARM
specificProblems: TRIB-FAR-END-ALARM
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description The equipment at the remote end has acknowledged the faultycondition of the interface signal, on one tributary interface. Alarmindication from the remote end is detected when bit 3 of channel TS0changes state from 0 to 1 in those frames not containing the framealignment signal.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 427 / 533
28 Class 75: TCSM-ADAPT
28.27.1 Corrective Actions
[75,228] TRIB−FAR−END−ALARM
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
SM−ADAPTalarm events?
no
yes
Repair/replace Receiver
Link related alarm
events?
no
yes
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 180: TRIB-FAR-END-ALARM: Corrective Actions
428 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.28 [75,231] ATER-TWO-MB-MISSING
specificProblems: ATER-TWO-MB-MISSING
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description The 2 Mbit/s interface on one Ater interface is not receiving a signal.The loss of the incoming digital signal at 2048 kbit/s is considered as aloss of the incoming 2M signal.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - -
3BK 20918 AAAA PCZZA Ed.06 429 / 533
28 Class 75: TCSM-ADAPT
28.28.1 Corrective Actions
[75,231] ATER−TWO−MB−MISSING
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
TC−ADAPTalarm events?
no
yes
Repair/replace Receiver
Ater related alarm
events?
no
yes
On−siteAlarm
persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local Ater cabling
OK?
no
yes
Trigger remote signal path and transmitter
tests on BSC side
Figure 181: ATER-TWO-MB-MISSING: Corrective Actions
430 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.29 [75,232] ATER-AIS-2MB
specificProblems: ATER-AIS-2MB
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description The 2 Mbit/s interface on one Ater interface is receiving an AIS signal(all ones).
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - -
3BK 20918 AAAA PCZZA Ed.06 431 / 533
28 Class 75: TCSM-ADAPT
28.29.1 Corrective Actions
[75,232] ATER−AIS−2MB
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
TC−ADAPTalarm events?
no
yes
Repair/replace Receiver
Ater related alarm
events?
no
yes
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Remove activated loops
Loops activated?
no
yes
Local Ater cabling
OK?
no
yes
Trigger remote signal path and transmitter
tests on BSC side
Figure 182: ATER-AIS-2MB: Corrective Actions
432 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.30 [75,233] ATER-FRAME-ALIGNMENT
specificProblems: ATER-FRAME-ALIGNMENT
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description The 2 Mbit/s signal frame alignment on one Ater interface is lost.Traffic is not possible. TS0 is reserved for frame alignment, alarmsand network synchronization information and should not be usedfor Signaling or speech purposes. The frame alignment signal ismonitored to determine if the frame alignment has been lost. The framealignment will be assumed to have been lost when three consecutiveincorrect frame alignment signals have been received.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - -
3BK 20918 AAAA PCZZA Ed.06 433 / 533
28 Class 75: TCSM-ADAPT
28.30.1 Corrective Actions
[75,233] ATER−FRAME−ALIGNMENT
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
TC−ADAPTalarm events?
no
yes
Repair/replace Receiver
Ater related alarm
events?
no
yes
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Correct the settingsTime slot 0 settings OK?
yes
no
Local Ater cabling
OK?
no
yes
Trigger remote signal path and transmitter
tests on BSC side
Figure 183: ATER-FRAME-ALIGNMENT: Corrective Actions
434 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.31 [75,234] ATER-CRC-MFRAME-ALGN
specificProblems: ATER-CRC-MFRAME-ALGN
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description The expected patterns not received on TS0 of the PCM (CRCmultiframe) on one Ater interface. The CRC is not used in the remoteend or there maybe interferences on the connection.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - -
3BK 20918 AAAA PCZZA Ed.06 435 / 533
28 Class 75: TCSM-ADAPT
28.31.1 Corrective Actions
[75,234] ATER−CRC−MFRAME−ALGN
Correct CRC settings
ContactSystem Support
Time Slot 0 CRC settings
OK?
no
yes
Alarmsolved
Alarm persists?
Solve that alarm(s)Remote
CRC alarm(s) events?
no
yes
yesno
Figure 184: ATER-CRC-MFRAME-ALGN: Corrective Actions
436 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.32 [75,235] ATER-BER-10E-3
specificProblems: ATER-BER-10E-3
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description Signal input BER worse than 1 in 1000 on one Ater interface. Theerror rate of the incoming main system signal is worse than the presetthreshold value of 10E-3.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - -
Degradation - - -
3BK 20918 AAAA PCZZA Ed.06 437 / 533
28 Class 75: TCSM-ADAPT
28.32.1 Corrective Actions
[75,235] ATER−BER−10E−3
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
TC−ADAPTalarm events?
no
yes
Repair/replace Receiver
Relatedalarm events?
no
yes
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 185: ATER-BER-10E-3: Corrective Actions
438 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.33 [75,236] ATER-BER-10E-4
specificProblems: ATER-BER-10E-4
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description Signal input BER worse than 1 in a 10000 on one Ater interface. Theerror rate of the incoming main system signal is worse than the presetthreshold value of 10E-4.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 439 / 533
28 Class 75: TCSM-ADAPT
28.33.1 Corrective Actions
[75,236] ATER−BER−10E−4
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
TC−ADAPTalarm events?
no
yes
Repair/replace Receiver
Related alarm events?
no
yes
On−siteAlarm
persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 186: ATER-BER-10E-4: Corrective Actions
440 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.34 [75,237] ATER-BER-10E-6
specificProblems: ATER-BER-10E-6
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description Signal input BER worse than 1 in a million on one Ater interface. Theerror rate of the incoming main system signal is worse than the presetthreshold value of 10E-6.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 441 / 533
28 Class 75: TCSM-ADAPT
28.34.1 Corrective Actions
[75,237] ATER−BER−10E−6
Solve thatalarm(s) first
Solve that alarm(s)
ContactSystem Support
TC−ADAPTalarm events?
no
yes
Repair/replace Receiver
Related alarm events?
no
yes
On−site
Alarm persists?
noyes
Alarmsolved
Alarm persists?
no
yes
Receiver operational?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Local cabling
OK?
no
yes
Trigger remote signal path and transmitter tests on MSC side
Figure 187: ATER-BER-10E-6: Corrective Actions
442 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.35 [75,238] ATER-FAR-END-ALARM
specificProblems: FAR-END-ALARM
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Major (PMA)
Alarm Description The equipment at the remote end has acknowledged the faultycondition of the interface signal, on one Ater interface. Alarm indicationfrom the remote end is detected when bit 3 of channel TS0 changesstate from 0 to 1 in those frames not containing the frame alignmentsignal.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - -
Degradation - - - - -
3BK 20918 AAAA PCZZA Ed.06 443 / 533
28 Class 75: TCSM-ADAPT
28.35.1 Corrective Actions
[75,238] ATER−FAR−END−ALARM
ContactSystem Support
TC−ADAPTalarm events?
no
yes
Alarm persists?
no
Alarmsolved
Alarm persists?
no yes
Solve that alarm(s)Related
receiver alarm events?
no
yes
Trigger remote signal path and transmitter
tests on BSC side
yes
Figure 188: ATER-FAR-END-ALARM: Corrective Actions
444 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.36 [75,241] SET-PROD-FAIL
specificProblems: SET-PROD-FAIL
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description This alarm indicates the NE settings production has failed. Theequipment settings are not in line with the DLS.
Impact on System See Consequences of an SBL State Change (Section 30).
SM-ADAPT
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - -
Degradation - - - - -
TC-ADAPT
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - -
3BK 20918 AAAA PCZZA Ed.06 445 / 533
28 Class 75: TCSM-ADAPT
28.36.1 Corrective Actions
[75,241] SET−PROD−FAIL
ContactSystem Support
yes
Lock SM/TC−ADAPT
Alarmsolved
Alarm persists?
no
Unlock SM/TC−ADAPT
Correct DSL settingsDSL
settings OK?
no
yes
Figure 189: SET-PROD-FAIL: Corrective Actions
446 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.37 [75,245] LOCAL-REINIT-REQ
specificProblems: LOCAL-REINIT-REQ
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description This alarm indicates that programming is required locally. Modificationof SM-ADAPT/TC-ADAPT parameters has occurred in the BSC, butthe setting at the SM-ADAPT/TC-ADAPT must be carried out locallyand cannot be carried out remotely. The equipment settings are notin line with the DLS.
Impact on System See Consequences of an SBL State Change (Section 30).
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
SM-ADAPT
All calls managed by the processor are lost with or without WTC as specified by the operator.
Loss - -
Degradation - - - - -
TC-ADAPT
All calls managed by the processor are lost with or without WTC as specified by the operator.
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - -
3BK 20918 AAAA PCZZA Ed.06 447 / 533
28 Class 75: TCSM-ADAPT
28.37.1 Corrective Actions
[75,245] LOCAL−REINIT−REQ
ContactSystem Support
Alarmsolved
Alarm persists?
no yes
Correct settingsBTS
parameter settingsOK?
no
yes
Disable SM/TC−ADAPT
Init SM/TC−ADAPT
Figure 190: LOCAL-REINIT-REQ: Corrective Actions
448 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.38 [75,246] DOWNLOAD-FAIL
specificProblems: DOWNLOAD-FAIL
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description This alarm indicates that programming of the SM-ADAPT/TC-ADAPThas failed. Modification of SM-ADAPT/TC-ADAPT parameters hasoccurred in the BSC, and downloading of the SM_ADAPT/TC-ADAPThas been initiated but has failed. The equipment settings are not inline with the DLS.
Impact on System See Consequences of an SBL State Change (Section 30).
SM-ADAPT
All calls managed by the processor are lost with or without WTC as specified by the operator.
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - -
Degradation - - - - -
TC-ADAPT
All calls managed by the processor are lost with or without WTC as specified by the operator.
Impact Trunk(s) Cell/ BTS(s) Signaling CallHandling
O&M; Capabilities
Loss - - - - -
Degradation - -
3BK 20918 AAAA PCZZA Ed.06 449 / 533
28 Class 75: TCSM-ADAPT
28.38.1 Corrective Actions
[75,246] DOWNLOAD−FAIL
ContactSystem Support
yes
Lock SM/TC−ADAPT
Alarmsolved
Alarm persists?
no
Unlock SM/TC−ADAPT
Correct DSL settingsDSL
settings OK?
no
yes
Figure 191: DOWNLOAD-FAIL: Corrective Actions
450 / 533 3BK 20918 AAAA PCZZA Ed.06
28 Class 75: TCSM-ADAPT
28.39 [75,247] ACCESS-FAIL
specificProblems: ACCESS-FAIL
eventType: Equipment
probableCause: Indeterminate
perceivedSeverity: Minor (DMA)
Alarm Description This alarm indicates that programming of the SM-ADAPT/TC-ADAPThas failed. Modification of SM/TC-ADAPTt parameters has occurred inthe BSC, and access towards the SM-ADAPT/TC-ADAPT has failed.The equipment settings are not in line with the DLS.
Impact on System See Consequences of an SBL State Change (Section 30).
SM-ADAPT
All calls managed by the processor are lost with or without WTC as specified by the operator.
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - -
Degradation - - - - -
TC-ADAPT
All calls managed by the processor are lost with or without WTC as specified by the operator.
Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss - - - - -
Degradation - -
3BK 20918 AAAA PCZZA Ed.06 451 / 533
28 Class 75: TCSM-ADAPT
28.39.1 Corrective Actions
[75,247] ACCESS−FAIL
ContactSystem Support
Alarmsolved
Alarm persists?
no yes
Solve that alarm(s)TCU/TSL/NE alarm events?
no
yes
Figure 192: ACCESS-FAIL: Corrective Actions
452 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29 BSC/TC Alarm Additional Information
This section describes the additional information supplied by some BSC/TCalarms.
3BK 20918 AAAA PCZZA Ed.06 453 / 533
29 BSC/TC Alarm Additional Information
29.1 Restart and Software Anomaly AlarmsThis section describes the additional information provided by the followingRestart alarm [33,0] and BSC Software Anomaly alarms [39,1], [39,3], [39,4],[39,5], [39,6], [39,7].
The Restart and Software Anomaly alarm byte definitions are shown in thefollowing table.
ByteNumber Description
0 - 1 Interface Address.
This specifies the connection of the processor to the internal switch of the BSC:
Byte 0: On-Board Controller Interface identity
Byte 1: Network address, enabling identification of the SBL links from the processor to
the internal switch.
2 This specifies the Logical Control Element-Identification. The SBL type specifies theprocessor type. There is no longer a direct relationship between LCE-ID and CE number.
3 Always 0.
4 - 5 Finite Message Machine (FMM) -ID, this identifies the task/process. It is the instructionpointer of the fault. Example: ’1E’ hex = SCCP ’1F’; hex = N7 SLH (N7 Signaling linkhandler).
6 - 7 Instruction Pointer of the processor address where the fault happened. The first byte isthe LSB.
8 - 9 Code Segment of the processor address where the fault happened. The first byte is the LSB.
10 - 11 Error type, see Table 9. The first byte is the LSB.
12 Sequence number. This is used to distinguish between similar error types.
13 Not relevant.
14 - 15 User Data 0. User data providing additional information.
16 - 17 User Data 1. User data providing additional information.
18 - 19 User Data 2. User data providing additional information.
20 - 21 User Data 3. User data providing additional information.
Table 7: Additional Information for Restart and Software Anomaly Alarms
454 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29.1.1 Finite Message Machine
The Finite Message Machine - Identity (FMM-ID) in Bytes 4 and 5 is defined inthe following table.
Dec Hex FMM-ID Meaning
1 01 ME-INIT-TCU Initialize TCU (ME = Management Entity).
2 02 ME-INIT-DTC Initialize DTC.
3 03 ME-INIT-CPR Initialize CPR.
4 04 ME-TWIN-FILE Twin file.
5 05 ME-REMOTE-SSD-ITF Remote Solid State Disk interface.
6 06 ME-ALARM-TCU-DTC TCU/DTC alarm.
7 07 ME-REMOTE-FILE Remote file.
8 08 ME-ALARM-CPR CPR alarm.
9 09 ME-MAINT-TCU-DTC TCU/ DTC maintenance.
10 0A DBASE-AUDIT-HLDCHCK Database audit handler check.
11 0B ME-MAINTENANCE-CPR CPR maintenance.
14 0E ME-HSK-1 ME housekeeping.
15 0F TCU-TRF-LDC TCU traffic local data collector.
16 10 DTC-TRF-LDC DTC traffic local data collector.
17 11 ME-MEASUREMENTS-CPR CPR measurement.
18 12 ME-BTS-TCU BTS O&M; TCU.
19 13 ME-BTS-CPR BTS O&M; CPR.
20 14 ME-REMOTE-LOADER Remote loader.
21 15 ME-LOADER Loader.
22 16 DH-DTC-TCU DTC/TCU.
23 17 LME-NETW-MAINT-MSTR Network maintenance master.
24 18 RF-MGT-L3 RF management.
25 19 BSC-LAPD-L2 BSC LAPD.
26 1A ME-COPY-FILE Copy file.
27 1B LME-NETW-ROUTINES Network routines.
3BK 20918 AAAA PCZZA Ed.06 455 / 533
29 BSC/TC Alarm Additional Information
Dec Hex FMM-ID Meaning
28 1C LME-NETW-MAINT Network maintenance.
29 1D BSSAP BSS Application Part.
30 1E SCCP Signaling Connection Control Part.
31 1F M7-SLH Signaling link handler for N7.
32 20 CALL-CONTROL-ACT Active CPR call control.
33 21 LME-M7-DTC Link maintenance entity for N7.
34 22 ME-TCSM TCSM.
35 23 ME-MMC MMC.
36 24 ME-DISK-HDLR Disk handler.
38 26 TCH-RM TCH resource manager.
39 27 LE-L3-L2-X.25 Link entity for L3, L# X.25.
40 28 LME-X.25 Link maintenance entity for X.25.
41 29 SLNM Signaling link network manager (N7).
42 2A SM Signaling manager (N7).
43 2B ME-DBASE-TEST-FMM Database test FMM.
44 2C L4E-TRANSPORT Transport.
45 2D L5E-SESSION Session.
46 2E L6E-PRESENTATION Presentation.
47 2F L7E-OSMAE OSMAE.
48 30 L7E-OSMAP OSMAP.
49 31 L7E-FTAM FTAM.
50 32 DTC-N-7-LDC DTC N7 local data collector.
51 33 ME-TRACE-DEBUG-MSTR Trace/debug master.
52 34 CALL-CONTROL-TCU TCU call control.
53 35 ME-EMPTY Empty.
54 36 BSC-HEART-BEAT-CTL BSC heartbeat control.
55 37 TRADEB-SLAVE-F Trace/debug slave.
56 38 ME-EMPTY-SLAVE Empty slave.
456 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
Dec Hex FMM-ID Meaning
57 39 RATA-TCU Read and Throw Away TCU (test only).
58 3A REMOTE-REQUEST-HDLR Remote request handler.
59 3B REPL-REL-SYNC Replaced Relation Sync.
60 3C BACK-UP-DATA-HDLR Backup data handler.
61 3D ME-SECURITY-FILE Security file.
62 3E ROLL-BACK-HDLR Rollback handler.
63 3F RATA-DTC Read and Throw Away DTC (test only).
64 40 RATA-CPR Read and Throw Away CPR (test only).
66 42 CPR-N-7-LDC CPR N7 local data collector.
67 43 ME-BSC-SW-REPLACE BSC software replacement.
68 44 TONE-DTMF-DH-FMM DTMF tone device handler.
69 45 CALL-CONTROL-DTC DTC call control.
70 46 ME-SUBSCR-ADMIN-CPR Subscriber administration CPR.
73 49 OBCI-NH-TEST-FMM On-board controller network handler test.
74 4A ME-HSK-2 ME housekeeping.
75 4B ME-HSK-3 ME housekeeping.
76 4C RATA-CPR-OSI Read and Throw Away CPR (test only).
77 4D ME-MMC-TCU MMC TCU.
78 4E ME-INIT-CPR-OSI Initialize OSI-CPR.
79 4F ME-ALARM-CPR-OSI OSI-CPR alarm.
80 50 ME-MAINT-CPR-OSI OSI-CPR maintenance.
81 51 CPR-TRF-LDC CPR traffic local data collector.
82 52 RMH-MSG-HANDLER Remote message handler.
83 53 RECOVERY-ME Recovery.
84 54 DH-CPR CPR device handler.
85 55 TELECOM-SUPERV-MOD Telecom supervision module.
86 56 ASN-ABIS ASN Abis.
87 57 ASN1-CONV ASN1 converter.
3BK 20918 AAAA PCZZA Ed.06 457 / 533
29 BSC/TC Alarm Additional Information
Dec Hex FMM-ID Meaning
88 58 ME-LOCAL-MAINT-CPR CPR local maintenance.
89 59 ME-LOCAL-ALARM-CPR CPR local alarm.
90 5A ME-HSK-LOCAL Local ME housekeeping.
91 5B ME-HSK-4 Housekeeping 4
92 5C LOC-OVRL-CTL Local overload control.
93 5D TRACE-COORDINATOR Trace Coordinator.
94 5E TRACE-ADMINISTRATOR Trace Administrator.
95 5F TCU-BTS-LDC BTS local data collector for TCU.
96 60 ME-MEAS-ADMIN Measurement administrator.
97 61 ME-MEAS-RECOVERY Measurement of recovery.
98 62 ME-HSK-5 ME housekeeping.
99 63 ME-MEAS-CENTRAL-COLL Central measurement collector.
100 64 RECOV-SL-ME Recovery of Signaling links.
101 65 ME-HSK-6 ME housekeeping.
102 66 ME-HSK-7 ME housekeeping.
103 67 ME-MAINT-DTC DTC maintenance.
104 68 ME-MAINT-TCU TCU maintenance.
105 69 ME-EMPTY-1386 Empty FMM for 1386.
106 6A ME-EMPTY-SLAVE-1386 Empty FMM for slave 1386.
107 6B BSC-SCSI-CONTROL Housekeeping.
108 6C RTS-MANAGER RTS Manager.
109 6D RTS-RECONFIGURE Reconfigure RTS.
110 6E OMU-SIMULATOR OMU simulator.
111 6F FU-SIMULATOR FU simulator.
112 70 MSC-SIMULATOR MSC simulator.
113 71 SMS-CB-MASTER SMS-CB master.
114 72 SMS-CB-LOCAL SMS-CB local.
115 73 DH-DTC DTC device handler.
458 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
Dec Hex FMM-ID Meaning
116 74 DH-TCU TCU device handler.
117 75 TCSM-ME-CPR TCS on the CPR.
118 76 TCSM-ME-TCU TSC on the TCU.
119 77 USAGE-STATE-MASTER Usage State on Demand master.
120 78 USAGE-STATE-SLAVE Usage State on Demand slave.
121 79 M7-TEST-FMM N7 test.
122 7A TRX-MANAGER TRX manager on the CPR.
123 7B TRX-REMAPPER TRX remapper on the CPR.
124 7C ME-FMM-INIT Initialize FMM.
125 7D FMM-SPARE-0 Spare FMM.
126 7E FMM-SPARE-1 Spare FMM.
127 7F FMM-SPARE-2 Spare FMM.
128 80 FMM-SPARE-3 Spare FMM.
129 81 FMM-SPARE-4 Spare FMM.
130 82 FMM-SPARE-5 Spare FMM.
131 83 FMM-SPARE-6 Spare FMM.
132 84 FMM-SPARE-7 Spare FMM.
133 85 SCCP-SCMG Signaling Connection Control Part managementprocedure for the S -CPR.
134 86 FMM-SCM-TEST SCM test module.
135 87 ME-DISK-HDLR-386 Disk handler for the 386 processor.
136 88 ME-BCLA-HANDLER BCLA handler on the scanning DTCS.
137 89 RATA-CPR-OSI Receive and Throw Away (test module).
138 8A TRACE-LDC Trace on local data collectors.
139 8B ALERTOR-MASTER Master Alertor (not used).
140 8C ALERTOR-SLAVE Slave Alertor (not used).
141 8D BSC-HEARTBEAT-G2 Heartbeat on the Evolium A9120 BSC.
142 8E ME-LOCAL-ALARM Local alarm handler.
3BK 20918 AAAA PCZZA Ed.06 459 / 533
29 BSC/TC Alarm Additional Information
Dec Hex FMM-ID Meaning
143 8F ME-EXT-RED Extension/reduction handler.
144 90 TCH-RM-LDC TCH-RM local data collector.
145 91 RATA-ABS3-AY Receive and Throw Away (test module).
146 92 RATA-ATR4-AY Receive and Throw Away (test module).
147 93 RATA-SYS4-AY Receive and Throw Away (test module).
148 94 RATA-OSI3-AY Receive and Throw Away (test module).
149 95 RATA-BCC1-AY Receive and Throw Away (test module).
150 96 RATA-TCU Receive and Throw Away (test module).
151 97 RATA-DTC Receive and Throw Away (test module).
152 98 RATA-CPR Receive and Throw Away (test module).
153 99 RATA-CPR-OSI Receive and Throw Away (test module).
154 9A RATA-SYS-AY Receive and Throw Away (test module).
155 9B RATA-OSIS-AY Receive and Throw Away (test module).
156 9C MEAS-COORDINATOR Message coordinator on the O-CPR.
157 9D CC-DATA-COLLECTOR Cumulative collector.
158 9E CC-RESULT-HANDLER Cumulative result collector.
159 9F DER-RESULTS-HANDLER Discrete Event Register result handler.
160 A0 CENTRAL-ALERTOR Central Alertor on the O-CPR.
161 A1 C_ALERTOR Alertor (not used).
162 A2 ME-MAINT-MSTER-TEST Master maintenance test module.
163 A3 LME-OFF-LINE-TEST Off-line test module.
164 A4 RATA_ABS3_AD Receive and Throw Away (test module).
165 A5 RATA_ATR4_AD Receive and Throw Away (test module).
166 A6 RATA_SYS4_AD Receive and Throw Away (test module).
167 A7 RATA_OSI3_AD Receive and Throw Away (test module).
168 A8 RATA_BBC1_AD Receive and Throw Away (test module).
169 A9 ME_ASN1_CONV2 ASN1 Convertor module 2.
170 AA ME_BROADCAST_MGT Broadcast bus maintenance module.
460 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
Dec Hex FMM-ID Meaning
171 AB L4_CONVERGENCE Convergence function for SMSCB.
172 AC RATA_ABS1_AE Receive and Throw Away (test module).
173 AD RATA_ATR1_AE Receive and Throw Away (test module).
174 AE RATA_SYS1_AE Receive and Throw Away (test module).
175 AF RATA_OSI1_AE Receive and Throw Away (test module).
176 B0 RATA_ABS3_AE Receive and Throw Away (test module).
177 B1 RATA_ATR4_AE Receive and Throw Away (test module).
178 B2 RATA_SYS4_AE Receive and Throw Away (test module).
179 B3 RATA_OSI3_AE Receive and Throw Away (test module).
180 B4 RATA_BBC1_AE Receive and Throw Away (test module).
181 B5 ME_CLK_MAINT_MSTR Clock maintenance module.
182 B6 ME_BC_MAINT_MSTR Broadcast bus maintenance module.
183 B7 ME_ALARM_CORRELATOR Alarm correlator module.
184 B8 RATA_ABS1_AH Receive and Throw Away (test module).
185 B9 RATA_ATR1_AH Receive and Throw Away (test module).
186 BA RATA_SYS1_AH Receive and Throw Away (test module).
187 BB RATA_OSI1_AH Receive and Throw Away (test module).
188 BC RATA_ABS3_AH Receive and Throw Away (test module).
189 BD RATA_ATR4_AH Receive and Throw Away (test module).
190 BE RATA_SYS4_AH Receive and Throw Away (test module).
191 BF RATA_OSI3_AH Receive and Throw Away (test module).
192 C0 RATA_BBC1_AH Receive and Throw Away (test module).
194 C2 CF_INTERPRETER Command file interpreter.
195 C3 FMM_INIT_G2 FMM init module for Evolium A9120 BSC.
196 C4 ME_PRELOADER_G2 Loader module for Evolium A9120 BSC.
197 C5 ME_SYSTEM_NIT System init module.
198 C6 ME_PRELOADER PreLoader module.
3BK 20918 AAAA PCZZA Ed.06 461 / 533
29 BSC/TC Alarm Additional Information
Dec Hex FMM-ID Meaning
199 C7 GPRSAP_FMM GPRS module (similar to BSSAP for Telecom).Responsible for the handling of commands fromthe MFS except O&M; and paging messages.
200 C8 RATA_ABS1_AP Receive and Throw Away (test module).
201 C9 RATA_ATR1_AP Receive and Throw Away (test module).
202 CA RATA_SYS1_AP Receive and Throw Away (test module).
203 CB RATA_OSI1_AP Receive and Throw Away (test module).
204 CC RATA_ABS3_AP Receive and Throw Away (test module).
205 CD RATA_ATR4_AP Receive and Throw Away (test module).
206 CE RATA_SYS4_AP Receive and Throw Away (test module).
207 CF RATA_OSI3_AP Receive and Throw Away (test module).
208 D0 RATA_BBC1_AP Receive and Throw Away (test module).
209 D1 ME_BTS_EXT_RED BTS Extension reduction module.
210 D2 FM_TRANS FM module for transmission.
212 D4 HSK_LOC_DTC Load housekeeping on the DTC.
213 D5 HSK_LOC_TCU Load housekeeping on the TCU.
214 D6 L3_DIS Module responsible for the GPRS signaling linkbetween the MFS and the BSC.
215 D7 DTC_LAPD_L2_FMM LAPD Layer 2 module on the DTC.
216 D8 RF_GPRS_FMM GPRS module (similar to RFMGT for telecom).Responsible for relaying commands from/toRFMGT on the TCU and allocation call bufferson the TCU side.
217 D9 CONF_TRANS_CPR Configuration transmission module on the CPR.
218 DA CONF_TRANS_LOCAL Configuration transmission module on the TCUs.
219 DB TSM_GPRS GPRS module (similar to TSM in telecom).Responsible for central data for the GPRS.Located on the S_CPR pair.
220 DC RATA_ABS3_AQ Receive and Throw Away (test module).
221 DD RATA_ATR4_AQ Receive and Throw Away (test module).
222 DE RATA_SYS4_AQ Receive and Throw Away (test module).
223 DF RATA_OSI3_AQ Receive and Throw Away (test module).
462 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
Dec Hex FMM-ID Meaning
224 E0 RATA_BBC1_AQ Receive and Throw Away (test module).
225 E1 PAGING Paging module, responsible for the handling ofpaging messages located on the GPRSAP’sDTCs.
232 E2 FM_TRANS_CORR FM module for transmission.
233 E3 OSND_TEST OSN_D test module.
234 E4 ME_HSK_7 Housekeeping module 7.
235 E5 TSC_MMI TSC Man Mahine Interface module.
241 F1 RATA_ABS3_AT Receive and Throw Away (test module).
242 F2 RATA_ATR4_AT Receive and Throw Away (test module).
243 F3 RATA_SYS4_AT Receive and Throw Away (test module).
244 F4 RATA_OSI3_AT Receive and Throw Away (test module).
245 F5 RATA_BBC1_AT Receive and Throw Away (test module).
246 F6 CENTRAL_RMS Radio Measurement Stat.
247 F7 TCU_RMS_LDC Radio Measurement Stat on each TCU.
248 F8 ABIS_RM ABIS Resource Manager module.
249 F9 COCO Connection control.
250 FA RFM_CCCH RFM CCCH Handler.
251 FB GOM GPRS O&M; module, responsible for the O&M;between the MFS and the BSC.
252 FC ME_ABIS_HCM_SCHED Hardware Configuration Management actionscheduler
253 FD ME_ABIS_PORT_HDLR Hardware Configuration Management Abishandler.
254 FE HCM_BTS_DATA_HDLR Hardware Configuration Management BTS datahandler.
255 FF HCM_TRAF_RES_HDLR Hardware Configuration Management trafficresource handler.
256 100 HCM_SIGN_RES_HDLR Hardware Configuration Management signalingresource handler.
257 101 HCM_MCB_MAPPER Hardware Configuration Management multiplexingcontrol block.
3BK 20918 AAAA PCZZA Ed.06 463 / 533
29 BSC/TC Alarm Additional Information
Dec Hex FMM-ID Meaning
258 102 ME_HSK_ABIS HSK ABIS module.
259 103 CF_INTERPRETER_2 Command file interpreter module 2.
Table 8: FMM-IDs in Bytes 4 and 5 for Restart Alarms
29.1.2 Error Types
The Error Types in Bytes 10 and 11 are defined in the following table.
Type(Dec) Type (Hex) Error Name
0 00 DUMMY
1 01 SYSTEM_RESTART
2 02 SYSTEM_REBOOT
3 03 SYSTEM_RELOAD
4 04 TRADEB_ERROR_CALL
5 05 ME_INIT_GLOB_INIT
6 06 ME_INIT_TAKE_OVER
7 07 ME_INIT_TIME OUT
8 08 L1_TRUNK_FAILURE
9 09 DBASE_ACC_FAILURE
10 0A NO_TRUNK_CELLS
11 0B ILC_INIT_FAILURE
12 0C ILC_DMA_UNDERRUN
13 0D ILC_DMA_OVERRUN
14 0E OBCI_HW_FLT
15 0F OBCI_SW_FLT
16 10 SSD_ACCESS_FAIL
17 11 DATABASE_ERROR
18 12 DATABASE_DATA_INC
19 13 INC_MESS_DATA
464 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
Type(Dec) Type (Hex) Error Name
20 14 ICLP_FAILURE
21 15 BS_CH_RLS_FAIL
22 16 CH_CONF_ERROR
23 17 MEAS_TYPE_ERROR
24 18 NO_LOCAL_REFERENCE_AVAILABLE
25 19 WRONG_TMS_TYPE
26 1A MASTER_FILE_CORRUPTED
27 1B MASTER_FILE_DISK_ERROR
28 1C ILC_DE_QUEUE_TWICE
29 1D ILC_EN_QUEUE_TWICE
30 1E ILC_NO_FR_CELL
31 1F BOOTSTRAP_ERR
32 20 NMI
33 21 UNEXPECTED_INT
34 22 INT_DATA_INC
35 23 MTF_RSL_SMALL
36 24 PR_DISABLE
37 25 PR_RESTART
38 26 OPEN_FILE_FLT
39 27 READ_REC_FLT
40 28 CLOSE_FILE_FLT
41 29 FCB_LOC_TO_OMU
42 2A WRONG_TCB_FIG
43 2B ERR_LOAD_REQ
44 2C ERR_ACK_NACK
45 2D OUT_OF_STATE
46 2E INTL_CATASTR
3BK 20918 AAAA PCZZA Ed.06 465 / 533
29 BSC/TC Alarm Additional Information
Type(Dec) Type (Hex) Error Name
47 2F SPC_ALARM
48 30 INTL_DATA_FLT
49 31 GSM_0808_MSG_UNKNOWN
50 32 GSM_0808_MSG_UNEXPEC
51 33 GSM_0808_IEI_UNEXPEC
52 34 GSM_0808_IE_FORM-ERR
53 35 GSM_0808_IE_SEM_ERR
54 36 GSM_0408_MSG_UNKNOWN
55 37 GSM_0408_MSG_UNEXPECTED
56 38 GSM_0408_PRTDISC_ERROR
57 39 GSM_0408_IE_FORM_ERROR
58 3A GSM_0408_IE_SEM_ERROR
59 3B INTERNAL_MESSAGE_UNKNOWN
60 3C INTERNAL_MESSAGE_UNEXPECTED
61 3D TCHRM_NO_ANSWER
62 3E TCHRM_RF_NO_ANSWER
63 3F TRADEB_LBS
65 41 CANCEL_EXPIRED_TIMER
66 42 TOO_MANY_RESTARTS
67 43 STAND_ALONE
68 44 OBCI_LINK_HW_FAULT
69 45 NETWORK_CONFIGURATIOM
70 46 OBCI_LINK_OS
71 47 INPUT_MAINT
72 48 MAINT_SEQUENCE
73 49 XMEM_FAULT
74 50 XMCK_FAULT
466 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
Type(Dec) Type (Hex) Error Name
77 4D GSM_0858_MS_UNEXPECTED
78 4E GSM_0808_CIC_UNKNOWN
79 4F CONF_CH_DISREP
80 50 ERROR_REPORT_FROM_BTS
81 51 RF_CHANNEL_RELEASE_FAILURE
82 52 ASN1_DECODE_FAILURE
83 53 ASN1_ENCODE_FAILURE
84 54 SW_REPLACEMENT_DATA_ERROR
85 55 INCORRECT_FILE_CONTENT
86 56 UPDATE_SW_SYSREC_FAILURE
87 57 READ_SW_SYSREC_FAILURE
88 58 MAX_SMAP_RETRIES
89 59 HEARTBEAT_ERROR
90 5A HEARTBEAT_RESET
91 5B NO_RESET_CIC_ACK
92 5C DIVIDE_ERROR
93 5D INV_TSS
94 5E STA_EXC
95 5F CIPHERING_DATA_INCONSISTENT
96 60 UNKNOWN_CIRC_RECEIVED
97 61 UNKNOWN_CIRC_TRANSMIT
98 62 INVALID_ACCESS_TYPE
99 63 EXPANSION_FAILED
100 64 OBCI_RESET
101 65 NO_MORE_DESCRIPTORS
102 66 INVALID_DESCRIPTOR_TYPE
103 67 INVALID_SELECTOR
3BK 20918 AAAA PCZZA Ed.06 467 / 533
29 BSC/TC Alarm Additional Information
Type(Dec) Type (Hex) Error Name
104 68 LOG_LIN_CONV_ERR
187 BB INVALID_OPCODE
188 BC DOUBLE_FAULT
189 BD SEGMENT_NOT_PRESENT
191 BF GEN_PROT
192 C0 PAGE_FAULT
679 2A7 C2_OVERFLOW
680 2A8 C2_NULL_PTR
681 2A9 PRCSS_END
682 2AA C2_RANGEFAIL
683 2AB C2_RTS
1055 41F NO_SUPVISION_PROCESS_CONTROL_BLOCK
1056 420 NO_APPLICATION_PROCESS_CONTROL_BLOCK
1057 421 PROCESS_CONTROL_BLOCK_OV1
1058 422 PROCESS_CONTROL_BLOCK_OV2
1059 423 DE_Q_TWICE
1060 424 NO_SUPV_STACK
1061 425 NO_TCB
1062 426 NO_MAIL LINK
1063 427 EN_Q_TWICE
1064 428 NO_APPLICATION_STACK
1065 429 INVALID_JOB_TYPE
1066 42A NO_TIMER_ML
1067 42B INVALID_MREQ_SIZE
1068 42C NO_UMEM_BLOCK
1069 42D NO_MESSAGE_BUFFER
1070 42E INVALID_MESSAGE_TYPE
468 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
Type(Dec) Type (Hex) Error Name
1071 42F INVALID_FMM_ID
1072 430 INVALID_MESSAGE_PRIORITY
1073 431 INVALID_OSINF_TYPE
1074 432 INVALID_SCFI
1075 433 CFGI_NOT_SET
1076 434 SANITY_TIME OUT
1077 435 ILLEGAL_CALL
1078 436 STACK_CHECK
1079 437 INVALID_CLOCK_VALUE
1097 449 INVALID_MESSAGE_BASIC_TO_DESTINATION
Table 9: Error Types in Bytes 10 and 11 for Restart Alarms
3BK 20918 AAAA PCZZA Ed.06 469 / 533
29 BSC/TC Alarm Additional Information
29.2 Reset and Software Anomaly AlarmsThis section describes the additional information provided by the followingReset alarm [33,1] and Software Anomaly alarms [33,4], [33,5], [39,18].
The Reset and Software Anomaly alarm byte definitions are shown in thefollowing table.
ByteNumber Description
0 - 1 IAD.
This specifies the connection of the processor to the internal switch of the BSC:
Byte 0: OBCI identity
Byte 1: Network address, enabling identification of the SBL links from the processor tothe internal switch.
2 This specifies the LCE-ID. The SBL type specifies the processor type. There is no longer adirect relationship between LCE-ID and CE number.
3 Always 0.
4 - 5 Not relevant.
6 - 7 IP of the processor address where the fault happened. The first byte is the LSB.
8 - 9 CS of the processor address where the fault happened. The first byte is the LSB.
10 - 11 Not relevant.
12 - 13 Not relevant.
14 - 15 User Data 0. User data providing additional information.
16 - 17 User Data 1. User data providing additional information.
18 - 19 User Data 2. User data providing additional information.
20 - 21 User Data 3. User data providing additional information.
Table 10: Additional Information for Reset and Software Anomaly Alarms
470 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29.3 System Support MachineThis subsection describes the System Support Machine (SSM) MessageIdentification.
DEC NO HEX NO MEANING
65535 FFFF This value simply indicates that the error occurs in an SSM.
Table 11: System Support Machine
29.4 Other BSC AlarmsThis section describes the additional information provided by other BSC alarms.
29.4.1 [33,3]
The additional information bytes for this alarm are defined in the following table.
Byte Number (Intel notation - 1st byte is Least Significant Byte (LSB)) Meaning
Format 1: 0 and 1
2
3
4
FF
CE identity
0
FF
Format 2: See BSC/TC Alarm Additional Information (Section 29).
Table 12: Additional Information for Alarm [33,3]
29.4.2 [34,0] to [34,2] and [34,4] to [34,6]
The additional information byte for these alarms is defined in the following table.
Byte Number Meaning
0 Switch port number on which the alarm was generated.
Table 13: Additional Information for Alarms [34,0] to [34,2] and [34,4] to [34,6]
3BK 20918 AAAA PCZZA Ed.06 471 / 533
29 BSC/TC Alarm Additional Information
29.4.3 [34,3]
The additional information bytes for this alarm are defined in Tables 14 to17, below.
Test Results ExplanationByteNumber Meaning Test Not Executed Test Executed
0 Test-segment Value 0 assigned Test segment failure. See Table 15.
1 Test-flt-type - Test fault type. See Table 16.
2 Test-raw-data (0) Link NetworkAddress
-
3 Test-raw-data (1) Value 255 assigned Switch Network Address.
4 Test-raw-data (2) - Link Type.
5 Test-raw-data (3) - Port Number.
6 Test-raw-data (4) - Test Result of TDM connection between port0 and the port given in Raw Data (3). SeeTable 17.
7 Test-raw-data (5) - Test Result of TDM connection between port1 and the port given in Raw Data (3). SeeTable 17.
8 Test-raw-data (6) - Test Result of TDM connection between port2 and the port given in Raw Data (3). SeeTable 17.
9 Test-raw-data (7) - Test Result of TDM connection between port3 and the port given in Raw Data (3). SeeTable 17.
10 Test-raw-data (8) - Test Result of TDM connection between port4 and the port given in Raw Data (3). SeeTable 17.
11 Test-raw-data (9) - Test Result of TDM connection between port5 and the port given in Raw Data (3). SeeTable 17.
12 Test-raw-data (10) - Test Result of TDM connection between port6 and the port given in Raw Data (3). SeeTable 17.
13 Test-raw-data (11) - Test Result of TDM connection between port7 and the port given in Raw Data (3). SeeTable 17.
14 Test-raw-data (12) - Test Result of TDM connection between port8 and the port given in Raw Data (3). SeeTable 17.
472 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
Test Results ExplanationByteNumber Meaning Test Not Executed Test Executed
15 Test-raw-data (13) - Test Result of TDM connection between port9 and the port given in Raw Data (3). SeeTable 17.
16 Test-raw-data (14) - Test Result of TDM connection between portA and the port given in Raw Data (3). SeeTable 17.
Table 14: Additional Information for Alarm [34,3]
Test Results ExplanationByteNumber Meaning Test Not Executed Test Executed
17 Test-raw-data (15) - Test Result of TDM connection between portB and the port given in Raw Data (3). SeeTable 17.
18 Test-raw-data (16) - Test Result of TDM connection between portC and the port given in Raw Data (3). SeeTable 17.
19 Test-raw-data (17) - Test Result of TDM connection between portD and the port given in Raw Data (3). SeeTable 17.
20 Test-raw-data (18) - Test Result of TDM connection between portE and the port given in Raw Data (3). SeeTable 17.
21 Test-raw-data (19) - Test Result of TDM connection between portF and the port given in Raw Data (3). SeeTable 17.
TestSegment Description
1 Get channel, send a request of MAINTENANCE_PACKET to find a free channel. Waitfor EOP_SENT or NACK.
Send a request of tunnel word for maintenance interrogate CH0, test if it is accepted,wait for message.
Only for diagnostic test, before starting test, it needs to send ’mask a CH0 alarm’ to modifymask, send maintenance interrupt and maintenance command to change status of ports.
3BK 20918 AAAA PCZZA Ed.06 473 / 533
29 BSC/TC Alarm Additional Information
TestSegment Description
2 Send a request of tunnel word for maintenance command CH0, with set maintenancebusy and alarm shutoff, test if it is accepted.
Send a request of tunnel word for maintenance interrogate CH0, test if it is accepted andwait for message.
3 Get channel, send a request of MAINTENANCE_PACKET with maintenance select onport under test.
4 Send a request of tunnel word for maintenance command CH0 with reset alarm shutoff.Test if it is accepted.
Send a request of tunnel word for maintenance interrogate CH0, test if it is accepted andwait for message.
5 Send a request of MAINTENANCE_PACKET with normal select on port under test. Waitfor NACK.
6 Send a request of tunnel word for maintenance command CH0 with reset maintenancebusy. Test if it is accepted.
Send a request of tunnel word for maintenance interrogate CH0, test if it is accepted andwait for message.
8 Send a packet with seven interrogates. Verify that the pointer correctly decremented.
9 Send packet of escape words. The transmitted and received packet are compared.
10 Set a path, send a packet of escape words. The transmitted and received packet iscompared.
11 Re-select path. Wait for NACK.
12 Send maintenance packet with maintenance select on port under test.
Wait for NACK and write violation alarm.
13 Send packet of escape words. The transmitted and received packets are compared (TDMbus).
14 Set up permanent path via test depth, towards own OBCI, with test pattern attached.
15 Try to set up a temporary path towards the permanent path. This should be rejected.
16 Try to set up a temporary path towards the permanent path, using maintenance selects.The AS bit is 0, so an alarm should be generated.
Table 15: Test Segment Results for Alarm [34,3], [51,1] (Byte 0) and [51,2] (One Byte Only)
474 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
Fault Type Description
0 No errors.
1 Not accepted tunnel word interrogate.
2 timeout tunnel word interrogate.
3 Not accepted tunnel word command.
4 Received tunnel alarm.
5 Message out of sequence.
6 No channel available.
7 Not accepted tunnel word interrogate.
8 All channels NACKed, maintenance packet not sent.
9 timeout for msg 158.
10 Wrong pointer received.
11 Timeout for msg 157.
12 Not accepted tunnel word command.
13 Not accepted tunnel word interrogate.
14 Wrong pointer received.
15 Timeout for msg 157.
16 No channel available.
17 Timeout no event msg received.
18 Timeout for msg second path.
19 Timeout for msg first path.
20 Not accepted tunnel word command.
21 Not accepted tunnel word interrogate.
22 Wrong pointer received.
23 Timeout for msg 157.
24 No NACK received but 2 EOP.
25 Timeout no NACK received.
26 Not accepted tunnel word command.
27 Not accepted tunnel word interrogate.
3BK 20918 AAAA PCZZA Ed.06 475 / 533
29 BSC/TC Alarm Additional Information
Fault Type Description
28 Wrong pointer received.
29 Timeout for msg 157.
30 Wrong pointer decrement after EOP.
31 Wrong pointer decremented before EOP.
32 Timeout for msg 158.
33 Wrong pkt received before EOP.
34 Wrong pkt received after EOP.
35 Timeout for msg 158.
36 All channels NACKed, maintenance pkt not sent.
37 Wrong pkt received after EOP.
38 Wrong pkt received before EOP.
39 Timeout for msg 158.
40 Timeout for msg 158.
41 Timeout for all msg.
42 Timeout for msg 151 and msg second path.
43 Timeout for msg 151 and msg first path.
44 Timeout for msg 151.
45 Timeout for msg first path and second.
46 Timeout for msg second path.
47 Timeout for msg first path.
48 Timeout wrong sequence message.
49 Values incompatible with Z_TUNNEL_type, Z_TEST_PORT.B_side andZ_TEST_PORT.B_depth.
50 Wrong sequence message
51 Result of Maintenance Interrogate:
ACI=0 - all channels idle
MB=0 - maintenance busy
AS=0 - alarm shutoff.
52 ACI=0 MB=0 AS=1
476 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
Fault Type Description
53 ACI=0 MB=1 AS=0
54 ACI=0 MB=1 AS=1
55 ACI=1 MB=0 AS=0
56 ACI=1 MB=0 AS=1
57 ACI=1 MB=1 AS=0
58 ACI=1 MB=1 AS=1
59 TDM test bus fail, resource seize fail.
60 TDM bus fail.
61 Overall timer has expired.
62 Overall timer has expired.
63 Cable test has failed.
64 Wrong PTR decremented after EOP.
65 Wrong PTR decremented after EOP.
66 Timeout for msg 158.
67 Plug Test Error.
68 DCDC State Change.
69 Send tunnel word not accepted.
70 Timeout msg for msg 157.
71 Processor does not control BCLA.
72 BCLA: wrong ID.
73 BCLA: this is not the rack BCLA.
74 BCLA: this is not the sys BCLA.
75 BCLA: the write register has failed.
76 BCU pattern test has failed.
3BK 20918 AAAA PCZZA Ed.06 477 / 533
29 BSC/TC Alarm Additional Information
Fault Type Description
77 BCU fail bit set.
78 No system test allowed according an R_xx.
Table 16: Test Fault Type for Alarm [34,3], [51,1] (Byte 1) and [51,2] (One Byte Only)
Nibble Test Result Explanation
High 0
1
Connection not tested.
Connection tested.
Low 0
1
2
3
Test OK.
Bad test packet and no EOPS received.
Bad test packet and EOPS received.
Timeout.
Table 17: TDM Connection Test Results (Bytes 6 to 21) for Alarm [34,3]
29.4.4 [34,7]
The additional information bytes for this alarm are defined in the following table.
Byte Number Meaning Test Results Explanation
Not applicable Test Successful. Test unsuccessful.
0 Test-raw-data (0)
1 Test-raw-data (1)
Number of times a routine test has run.
2 Test-raw-data (2)
3 Test-raw-data (3)
Number of tunnels.
4 Test-raw-data (4)
5 Test-raw-data (5)
Number of tested tunnels.
6 Test-raw-data (6)
7 Test-raw-data (7)
Number of successful tunnels.
8 Test-raw-data (8)
9 Test-raw-data (9)
Value 255 assigned.
Number of unsuccessful tunnels.
Table 18: Additional Information for Alarm [34,7]
478 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29.4.5 [35,0]
The additional information bytes for this alarm are defined in the following table.
Byte Number Meaning (Intel notation - 1st byte is LSB)
0 Origin of the problem. 00H No message.
01H Stop CMD from level 3.
02H T1 timeout (Align ready).
03H SIO received during align ready.
04H SIOS received during align ready.
05H T2 timeout (Not aligned).
06H T3 timeout (Aligned).
07H SIOS received during aligned.
08H Align Error Rate Threshold (AERM) reached.
09H LSSU received while in service.
0AH Abnormal FIB received.
0BH Abnormal BSN received.
0CH Signal unit error rate threshold reached (SUERM).
0DH T7 timeout (Acknowledge).
0EH T6 timeout (Congestion).
0FH Abnormal hardware condition Tx.
10H Abnormal hardware condition Rx.
FFH Suppress.
1 Present link traffic state. 80H In traffic.
40H Traffic before unavailable.
10H Remote blocked.
00H Not in traffic.
Table 19: Additional Information for Alarm [35,0]
3BK 20918 AAAA PCZZA Ed.06 479 / 533
29 BSC/TC Alarm Additional Information
29.4.6 [35,2]
The additional information bytes for this alarm are defined as shown below.
Byte Number Meaning (Intel Notation - 1st byte is LSB)
0 and 1 DPC of the MSC (same as the alarm number).
2 and 3 SSF of the MSC.
Table 20: Additional Information for Alarm [35,2]
29.4.7 [35,3]
There are two possible layouts for the INC-REP Alarm.
Alarm layout 1 occurs every hour to prevent an overload situation on the BSC.The additional information bytes for alarm layout 1 are defined in Table 21.
Alarm layout 2 occurs on every alarm event. The additional information bytesfor alarm layout 2 are defined in Table 22.
Table 23 shows an example of additional information for Alarm [35,3].
Word Number Meaning (Intel Notation - 1st byte is LSB)
0 Value = 0: Invalid SSF received.
Value = 1: Invalid DPC received.
Value = 2:
Invalid OPC received or
Status Indicator (SI) =0: Signaling Network Management Message and Signaling
Link Code (SLC) not existing or
SI=1: Signaling Network Testing and Maintenance Message (SNTM) and SLCdifferent from one SLC.
1 100H*SLC + SSF received.
(SLC is described in section 15.2 of ITU-T Rec. Q704).
(SSF is described in section 14.2.2 of ITU-T Rec. Q704).
2 SI received.
(SI is described in section 14.2.1 of ITU-T Rec. Q704).
3 MSG_TYPE HO/H1 received.
(SI=0 is described in section 15 of ITU-T Rec. Q704).
(SI=1 is described in section 5 of ITU-T Rec. Q707).
4 DPC received.
(DPC is described in section 15.2 of ITU-T Rec. Q704).
480 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
Word Number Meaning (Intel Notation - 1st byte is LSB)
5 OPC received.
(OPC is described in section 15.2 of ITU-T Rec. Q704).
6 SSF received.
(SSF is described in section 14.2 of ITU-T Rec. Q704).
7 DPC expected (Value fromDLS).
8 OPC expected (Value from DLS).
9 SSF expected (Value from DLS).
Table 21: Additional Information for Alarm [35,3], Layout 1
Word Number Meaning (Intel Notation - 1st byte is LSB)
0 Value = 10: Changeback refused (described in ITU-T Rec. Q704).
2 - 18 Value = FF
Table 22: Additional Information for Alarm [35,3], Layout 2
Data Word Value Meaning
02 00 0 0002H invalid OPC or
0c 0c 1 0C0CH SLC= 0CH SSF= 0CH
01 00 2 0001H SI= SNTM
11 00 3 0011H MSG Type = SLTM*
31 02 4 0231H DPC received
0a 02 5 020AH OPC received
0c 00 6 000CH SSF received
31 02 7 0231H DPC expected
0a 02 8 020AH OPC expected
0c 00 9 000CH SSF expected
Table 23: Example of Additional Information for Alarm [35,3]
* SLTM = Signaling Link Test Message
3BK 20918 AAAA PCZZA Ed.06 481 / 533
29 BSC/TC Alarm Additional Information
29.4.8 Result of Example
Fact: Received values correspond to expected values and SI = 1.
Conclusion: SLC is different from own SLC (SLC received is 0CH).
Reaction: Check in DLS for relation of R_N7_CONF. In example SLC definitionfor N7-7 is 04H.
Final result: SLC definitions for N7-7 are different between MSC and BSC.
29.4.9 [35,4]
The additional information bytes for this alarm are defined in the table below.
Byte Number Meaning (Intel Notation - 1st byte is LSB)
0 Logical Control Element identity where link resides.
1 DTN identity where link resides.
2 to 9 Null value.
Table 24: Additional Information for Alarm [35,4]
29.4.10 [36,14]
The additional information byte for this alarm is defined in below.
Byte Number Meaning
0 0: own clock; source of alarm.
1: mate clock; source of alarm.
Table 25: Additional Information for Alarm [36,14]
29.4.11 [36,15]
The additional information byte for this alarm is defined below.
Byte Number Meaning
0 0: PLL out of range.
1: clock failure.
Table 26: Additional Information for Alarm [36,15]
482 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29.4.12 [38,0]
The additional information byte for this alarm is defined in below.
Byte Number Meaning
0 Display of the modem signals.
Table 27: Additional Information for Alarm [38,0]
29.4.13 [38,2]
The additional information bytes for this alarm are defined below.
Byte Number Meaning
0 Identification of the link where the problem occurred.
1 and 2 Identification of the channel where the problem occurred.
3 and 4 Description of the problem.
Table 28: Additional Information for Alarm [38,2]
29.4.14 [42,3]
The additional information byte for this alarm is defined below.
Byte Number Meaning
0 Cause of the reset procedure:
00: reset from MSC.
01: MSC communication lost or internal reason.
Table 29: Additional information for Alarm [42,3]
3BK 20918 AAAA PCZZA Ed.06 483 / 533
29 BSC/TC Alarm Additional Information
29.4.15 [42,5]
The additional information bytes for this alarm are defined in the following table.
Byte Number Meaning
Alarm cause:
0 BSC reload/reboot
1 CPRA reload/reboot
2 BSC restart
3 CPRA restart
4 CPRA takeover
5 MSC unavailable
6 Reset from MSC
7 Overload from MSC
8 Timer T6 expired
9 Timer T6 expired
10 MSC available
11 Timer T2 expired
12 Overload from BTS
13 TCUA overload
14 DTC overload
15 Sign link congestion.
Timer T6 indicates an MSC originated end of an overload period, the system returnsto normal.
0
Timer T2 indicates a BTS originated end of an overload period, the system returns tonormal.
1 - 2 LAC. #FF if not defined.
3 - 4 Cell Id. #FF if not defined.
: : :
: : For N (40) cells
: : :
484 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
Byte Number Meaning
4N-3 to 4N-2 LAC. #FF if not defined.
4N-1 to 4N Cell Id. #FF if not defined.
Table 30: Additional Information for Alarm [42,5]
29.4.16 [42,6]
The additional information bytes for this alarm are defined in the following table.
Byte Number Meaning
Alarm cause:
0 BSC reload/reboot
1 CPRA reload/reboot
2 BSC restart
3 CPRA restart
4 CPRA takeover
5 MSC unavailable
6 Reset from MSC
7 Overload from MSC
8 Timer T6 expired
9 Timer T6 expired
10 MSC available
11 Timer T2 expired
12 Overload from BTS
13 TCUA overload
14 DTC overload
15 Sign link congestion.
Timer T6 indicates an MSC-originated end of an overload period, the system returnsto normal.
0
Timer T2 indicates a BTS-originated end of an overload period, the system returnsto normal.
1 - 2 LAC. #FF if not defined.
3BK 20918 AAAA PCZZA Ed.06 485 / 533
29 BSC/TC Alarm Additional Information
Byte Number Meaning
3 - 4 Cell Id. #FF if not defined.
5 - 6 Current RACH.
This information gives the reason a message was sent and the new access classvalues. The RACH parameter is specified using 16 bits. The right hand bit correspondsto Access class 0.
Value 10 for an Access class specifies emergency calls only.
Value 0 for an Access class specifies that calls are authorized.
7 - 8 Starting RACH.
This information gives the reason a message was sent and the new access classvalues. The RACH parameter is specified using 16 bits. The right hand bit correspondsto Access class 0.
Value 10 for an Access class specifies emergency calls only.
Value 0 for an Access class specifies that calls are authorized.
: : :
: : For N (40) cells
: : :
8N-7 to 8N-6 LAC. #FF if not defined.
8N-5 to 8N-4 Cell Id. #FF if not defined.
8N-3 to 8N-2 Current RACH.
This information gives the reason a message was sent and the new access classvalues. The RACH parameter is specified using 16 bits. The right hand bit correspondsto Access class 0.
Value 10 for an Access class specifies emergency calls only.
Value 0 for an Access class specifies that calls are authorized.
8N-1 to 8N Starting RACH.
This information gives the reason a message was sent and the new access classvalues. The RACH parameter is specified using 16 bits. The right hand bit correspondsto Access class 0.
Value 10 for an Access class specifies emergency calls only.
Value 0 for an Access class specifies that calls are authorized.
Table 31: Additional Information for Alarm [42,6]
486 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29.4.17 [42,9]
The additional information bytes for this alarm are defined below.
Byte Number Meaning
0 SBL unit type
1 SBL unit number
2-3 SBL type
4 SBL number
5 SBL sub-number
6-13 Overload level buffer pool 1-8
00 = No Overload
01 = SCCP Overload
02 = Overload Level 1
03 = Overload Level 2
14 Processor occupancy (%)
Table 32: Additional Information for Alarm [42,9]
29.4.18 [42,12]
The additional information bytes for this alarm are defined below.
Byte Number Meaning
0 - 1 LAC of cell
2 - 3 CI of cell
: : For N number of cells lost (60 maximum)
4N-4 to 4N-3 LAC of cell
4N-2 to 4N-1 CI of cell
Table 33: Additional Information for Alarm [42,12]
3BK 20918 AAAA PCZZA Ed.06 487 / 533
29 BSC/TC Alarm Additional Information
29.4.19 [42,13]
The additional information bytes for this alarm are defined below.
Byte Number Meaning
Alarm cause:
0 BSC reload/reboot
1 CPRA reload/reboot
2 BSC restart
3 CPRA restart
4 CPRA takeover
5 MSC unavailable
6 Reset from MSC
7 Overload from MSC
8 Timer T18 expired
9 MSC available
10 End of reset procedure
11 Not applicable
12 Not applicable
13 Not applicable
14 DTC overload
15 CPR overload
16 Signaling link congestion
17 Not applicable
18 Overload parameter modify
19 Cumulative counter null
0
Timer T18 indicates a BSC-originated end of an overload period, the system returnsto normal.
488 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
Byte Number Meaning
1 - 2 This information gives the reason a message was sent, and the new access classvalues on System Level GSM TS 04.08.
The RACH parameter is specified using 16 bits. The right hand bit corresponds toAccess class 0.
Bit 0..9, 11..15 = 0 for an Access class means that Access control class is not barredon System Level.
Bit 10 = 0 means emergency calls are allowed on System Level to all MSs.
Bit 10 = 1 means emergency calls are not allowed on System Level except for MSs thatbelong to one of the classes between 11..15.
Byte 1 contains Bits 15 - 08
Byte 2 contains Bits 07 - 00
Byte 3 = Cell Bar Access
Byte 4 = Cell Bar Qualifier on System Level GSM TS 04.08 and 05.08.
Cell Bar Quality Cell Bar Access Cell SelectionPriority
Status for CellReselection
0 0 Normal Normal
0 1 Barred Barred
1 0 Low Normal
3 - 4
1 1 Low Normal
Table 34: Additional Information for Alarm [42,13]
29.4.20 [43,0] to [43,3]
The additional information bytes for these alarms are defined below.
Byte Number Meaning
0 - 1 Number of available BCCH.
2 - 3 Number of available SDCCH.
4 - 5 Number of available TCH.
6 TRX identity.
7 Current TEI (RSLNumber)
#FF if no RSL is mapped.
8 BEQ–Number
9 Baseband State: 0 = Not available
1 = Available
3BK 20918 AAAA PCZZA Ed.06 489 / 533
29 BSC/TC Alarm Additional Information
Byte Number Meaning
10 Radio Part State: 0 = Not available
1 = Available
: : :
: : For N configured TRXs (Maximum 8).
: : :
5N + 1 TRX identity. -
5N + 2 Current TEI (RSLnumber)
#FF if no RSL is mapped.
5N + 3 BEQ number. -
5N + 4 Baseband State: 0 = Not available
1 = Available
5N + 5 Radio Part State: 0 = Not available
1 = Available
5N + 6 Separator #FF
5N + 7 Separator #FF
5N + 8 CU number. -
5N + 9 BEQ number. -
5N + 10 to 5N +11
ARFCN used. -
5N + 12 ARFCN available. -
: : :
: : For N configured TRXs (Maximum 8).
: : -
9N + 6 CU number.
9N + 7 BEQ number.
9N + 8 to 9N + 9 ARFCN used.
9N + 10 ARFCN available.
Table 35: Additional Information for Alarms [43,0] to [43,3]
490 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29.4.21 [43,4]
The additional information bytes for this alarm are defined in the following table.
Byte Number Meaning
Alarm cause:
0 BSC reload/reboot
1 CPRA reload/reboot
2 BSC restart
3 CPRA restart
4 CPRA takeover
5 Not applicable
6 Not applicable
7 Not applicable
8 Not applicable
9 Not applicable
10 Not applicable
11 Timer T2 expired
12 Overload from BTS
13 TCUA overload
14 Not applicable
15 Not applicable
16 Not applicable
17 Bar/unbar cell request
18 Overload parameter modify
19 TCC null
0
Timer T2 indicates a BSC-originated end of an overload period, the system returnsto normal.
3BK 20918 AAAA PCZZA Ed.06 491 / 533
29 BSC/TC Alarm Additional Information
Byte Number Meaning
1 - 2 This information gives the reason a message was sent, and the new access classvalues on Cell Level (Dynamic RACH) GSM TS 04.08.
The RACH parameter is specified using 16 bits. The right hand bit corresponds toAccess class 0.
Bit 0..9, 11..15 = 0 for an Access class means that Access control class is not barredon Cell Level.
Bit 10 = 0 means emergency calls are allowed in the cell to all MSs.
Bit 10 = 1 means emergency calls are not allowed in the cell except for MSs that belongto one of the classes between 11..15.
Byte 1 contains Bits 15 - 08.
Byte 2 contains Bits 07 - 00.
3 - 4 Byte 3 = Cell Bar Access
Byte 4 = Cell Bar Qualifier on System Level GSM TS 04.08 and 05.08.
- Cell Bar Quality Cell Bar Access Cell SelectionPriority
Status for CellReselection
- 0 0 Normal Normal
- 0 1 Barred Barred
- 1 0 Low Normal
- 1 1 Low Normal
Table 36: Additional Information for Alarm [43,4]
29.4.22 [44,0], [44,5] and [44,6]
The additional information bytes for these alarms are defined below.
Byte Number Meaning
0 + 1 Abis Error Code.
2 + 3 Error Number (that is, Record Number).
Table 37: Additional Information for Alarms [44,0], [44,5] and [44,6]
492 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29.4.23 [44,3]
The additional information bytes for this alarm are defined below.
Byte Number Meaning
0 + 1 Abis Error Code.
2 + 3 File Number.
4 + 5 Error Number (that is, Record Number).
Table 38: Additional Information for Alarm [44,3]
29.4.24 [46,0], [46,1] and [46,3]
The additional information bytes for these alarms are defined below.
Byte Number Meaning
0 + 1 Twin File number.
2 + 3 Twin file PCS of the twin file in alarm.
Table 39: Additional Information for Alarms [46, 0], [46,1] and [46,3]
29.4.25 [47,9]
The additional information bytes for this alarm are defined below.
Byte Number 0+ 1 Meaning
0 CBC Outgoing Connection association prematurely terminated internally.
1 CBC O/G association prematurely terminated externally.
2 Network connection refused.
3 Network connection timeout.
4 BIND parameters not populated.
5 CBC O/G association setup timeout.
6 CBC O/G association refused - not entitled.
7 CBC O/G association refused - invalid Id or password.
Table 40: Additional Information for Alarm [47,9]
3BK 20918 AAAA PCZZA Ed.06 493 / 533
29 BSC/TC Alarm Additional Information
29.4.26 [49,0]
The additional information bytes for this alarm are defined below.
Byte Number Meaning
0 + 1 LAC of Cell.
2 + 3 CI of Cell.
4 + 5 Threshold Value 1.
6 + 7 Threshold Value 2.
Table 41: Additional Information for Alarm [49,0]
29.4.27 [49,1]
The additional information bytes for this alarm are defined as shown below.
Byte Number Meaning
0 + 1 LAC of Cell.
2 + 3 CI of Cell.
4 + 5 Threshold Value 1.
6 + 7 Threshold Value 2.
8 + 9 SBL type (DTC).
10 + 11 SBL number (DTC number).
Table 42: Additional Information for Alarm [49,1]
494 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29.4.28 [49,2] and [49,3]
The additional information bytes for these alarms are defined as follows.
Byte Number Meaning
0 + 1 LAC of Cell.
2 + 3 CI of Cell.
4 + 5 Threshold Value 1.
6 + 7 Threshold Value 2.
8 + 9 SBL type (DTC).
10 + 11 SBL number (DTC number).
12 + 13 Transceiver identity.
14 + 15 Time slot number.
Table 43: Additional Information for Alarms [49,2] and [49,3]
29.4.29 [51,0]
The additional information bytes for this alarm are defined in the table below.
Byte Number Meaning
0 - 1 Network address.
2 Bits 3-0: Switch port number (values 0-15) on which the alarm was generated.
Bits 7-4: Reason for alarm.
0= An unsynchronized write access occurred within a switch element internal hardwarelogic. This caused a mismatch generating a transient write violation alarm.
1= Loss of synchronization with the internal 4 Mbit/s signal. A transient ’loss-of-sync’alarm has been generated.
Table 44: Additional Information for Alarm [51,0]
3BK 20918 AAAA PCZZA Ed.06 495 / 533
29 BSC/TC Alarm Additional Information
29.4.30 [51,1]
The additional information bytes for this alarm are defined in Tables 45, 46,47 and 48.
The blocks of additional information must be considered together in order toanalyze the alarm information correctly.
1. The first block of additional information indicates the network address ofswitch, the link states and, if required, the necessary fault reason.
2. The subsequent blocks of additional information indicate the test results ofthe link. For every failed test, a block of additional data is filled in.
The relationship between the Interface Address (IAD) / Network Address(NA) (Hex) and the RIT is given in Table 51 for BSC racks 1, 2 and 3. Thetable contains the relationships for all completely equipped racks and theRIT position in the rack, shelf and slot.
ByteNumber Meaning
0 - 1 NetworkAddress.
Bits 3-0: Faulttype
0= No Reason.
1= Write Violation. Several unsynchronized write accesses occurredwithin a switch element’s internal hardware logic. This caused amismatch, generating a transient write violation alarm.
2= Write Violation Overflow. Several unsynchronized write accessesoccurred within a switch element’s internal hardware logic. This causeda mismatch, generating a write violation overflow alarm.
3= Loss of Sync. The switch detected a loss of synchronization with theinternal 4 Mbit/s signal. All calls through the switch are lost. An alarm issent for the switch indicating a permanent loss of synchronization.
4= Loss of Sync Overflow. The switch detected a large number oftransient losses of synchronization with the internal 4 Mbit/s signalwithin a specified time frame.
5= HW Fault. Hardware failure detected.
6= Init-Ini-Fail. A link initialization failed during an initialization actionon a switch SBL.
7= Operator Request. An operator request has failed.
2 - 17
Bits 7-4: Linkstate
0= In Service1= Out of service2= Autonomous out of service3= Undefined4= Faulty In Service5= Alarm shutoff6= Not equipped link
18 - 19 Not used. (#FF) -
Table 45: Additional Information for Alarm [51,1] - First Block
There are 16 ports. Byte 2 represents Port 0, Byte 3 represents Port 1, andso on.
496 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
If additional blocks of information are displayed, each one indicates the resultsof a failed link test. Refer to the table below.
Byte Number Meaning Descriptions
0 Test Segment See Test-Segment Table 15.
1 Test-Fault-type See Test-Fault-Type Table 16.
2 - 3 Link-Network-Address -
4 - 19 TDM-Test-Results See Table 47 for TDM Test Result Byte descriptions.
Table 46: Additional Information for Alarm [51,1] - Subsequent Blocks
If Test Segment and Test-Fault-Type are both at 0, the test did not executeor a timeout was received. In this case, the TDM-Test-Results values willbe set to #FF.
Byte Number Test Results Explanation
4 Test Result of TDM connection between port 0 and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
5 Test Result of TDM connection between port 1 and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
6 Test Result of TDM connection between port 2 and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
7 Test Result of TDM connection between port 3 and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
8 Test Result of TDM connection between port 4 and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
9 Test Result of TDM connection between port 5 and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
10 Test Result of TDM connection between port 6 and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
11 Test Result of TDM connection between port 7 and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
12 Test Result of TDM connection between port 8 and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
13 Test Result of TDM connection between port 9 and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
14 Test Result of TDM connection between port A and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
15 Test Result of TDM connection between port B and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
3BK 20918 AAAA PCZZA Ed.06 497 / 533
29 BSC/TC Alarm Additional Information
Byte Number Test Results Explanation
16 Test Result of TDM connection between port C and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
17 Test Result of TDM connection between port D and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
18 Test Result of TDM connection between port E and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
19 Test Result of TDM connection between port F and the port given by the Link NetworkAddress. See Table 48 for detailed TDM test results.
Table 47: TDM Test Result Byte Descriptions for Alarm [51,1] and [51,2]
Nibble Test Result Explanation
High 0
1
Connection not tested.
Connection tested.
Low 0
1
2
3
Test OK.
Bad test packet and no EOPS received.
Bad test packet and EOPS received.
Timeout.
Table 48: Detailed TDM Test Results for Alarm [51,1] and [51,2]
The TDM is the internal multiplex bus of the switch. The TDM test makes a sortof loop between the port under test and all the equipped ports of the switch.
For example:
If port 2 is under test, a loop will be made between
port 2 -> port 0
port 2 -> port 1
...
port 2 -> port F.
The relationship between the Interface Address (IAD) / Network Address(NA) (Hex) and the RIT is given in Table 51 for BSC racks 1, 2 and 3. Thetable contains the relationships for all completely equipped racks and the RITposition in the rack, shelf and slot.
498 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29.4.31 [51,2]
The additional information bytes for this alarm are defined below.
Test Results Byte Number Meaning Byte Description
Test Segment one byte only See Table 15.
Test Fault Type one byte only See Table 16.
Test Raw Data 0 + 1
2 + 3
4 - 19
Switch Network Address.
Link Network Address.
TDM
For relation of Switch NetworkAddress to board, see Table 51.
Associated port is under test.
For TDM Test Result Bytedescription, see Table 47.
Table 49: Additional Information for Alarm [51,2]
Test Result Unsuccessful (some failures) Unsuccessful (tests not executed)
Test Segment 13 0
Test Fault Type 60 0
Test Raw Data H’00
H’10
H’10
H’10
H’45
H’10
H’10
H’10
H’00
H’12
H’10
H’10
H’40
H’10
H’10
H’10
H’13
H’10
H’10
H’10
H’00
H’FF
H’FF
H’FF
H’45
H’FF
H’FF
H’FF
H’00
H’FF
H’FF
H’FF
H’40
H’FF
H’FF
H’FF
H’FF
H’FF
H’FF
H’FF
Table 50: Example for an Unsuccessful Test Results Format for Link/Switch
If the Test Segment and the Test-Fault-Type are both at 0, the test did notexecute or a timeout was received. In this case, the TDM-Test -Resultsvalues will be set to #FF.
The relationship between the Interface Address (IAD) (Hex) / Network Address(NA) and the RIT is given in Table 51 for BSC racks 1, 2 and 3. The tablecontains the relationships for all completely equipped racks and the RITposition in the rack, shelf and slot.
3BK 20918 AAAA PCZZA Ed.06 499 / 533
29 BSC/TC Alarm Additional Information
For detailed information about BSC configurations, refer to the (BSC Cabinetand Subrack Description).
IAD/NA (Hex) RIT (Type) Position (Rack.Shelf.Slot)
0000 CPRCAB 1.8.17
0000 SWCHAB 1.8.37
0001 CPRCAB 1.8.19
0002 CPRCAC 1.8.21
0003 CPRCAC 1.8.25
0004 CPRCAA 1.8.29
0005 CPRCAA 1.8.31
0008 SWCHAA 1.7.1
0009 SWCHAA 1.7.3
000A SWCHAA 1.7.5
000B SWCHAA 1.7.7
000C SWCHAA 1.7.9
000D SWCHAA 1.7.11
000E SWCHAA 1.7.13
000F SWCHAA 1.7.15
0010 TCUC 1.7.29
0010 SWCHAB 1.7.45
0011 TCUC 1.7.31
0012 TCUC 1.7.33
0013 TCUC 1.7.35
0014 TCUC 1.7.37
0015 TCUC 1.7.39
0016 TCUC 1.7.41
0017 TCUC 1.7.43
0020 SWCHAB 1.6.9
0020 DTCC 1.6.13
500 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
IAD/NA (Hex) RIT (Type) Position (Rack.Shelf.Slot)
0021 DTCC 1.6.15
0022 DTCC 1.6.17
0023 DTCC 1.6.19
0024 DTCC 1.6.23
0025 DTCC 1.6.25
0026 DTCC 1.6.27
0027 DTCC 1.6.29
0030 SWCHAB 1.6.41
0030 DTCC 1.6.45
0031 DTCC 1.6.47
0032 DTCC 1.6.49
0033 DTCC 1.6.51
0034 DTCC 1.6.55
0035 DTCC 1.6.57
0036 DTCC 1.6.59
0037 DTCC 1.6.61
0040 SWCHAB 1.8.39
0050 SWCHAB 1.7.47
0060 SWCHAB 1.6.11
0070 SWCHAB 1.6.43
0088 SWCHAA 1.8.45
0089 SWCHAA 1.8.47
008A SWCHAA 1.8.49
008B SWCHAA 1.8.51
008C SWCHAA 1.8.53
008D SWCHAA 1.8.55
008E SWCHAA 1.8.57
008F SWCHAA 1.8.59
3BK 20918 AAAA PCZZA Ed.06 501 / 533
29 BSC/TC Alarm Additional Information
IAD/NA (Hex) RIT (Type) Position (Rack.Shelf.Slot)
0098 SWCHAA 1.2.1
0099 SWCHAA 1.2.3
009A SWCHAA 1.2.5
009B SWCHAA 1.2.7
009C SWCHAA 1.2.9
009D SWCHAA 1.2.11
009E SWCHAA 1.2.13
009F SWCHAA 1.2.15
00A8 SWCHAA 1.2.21
00A9 SWCHAA 1.2.23
00AA SWCHAA 1.2.25
00AB SWCHAA 1.2.27
00AC SWCHAA 1.2.29
00AD SWCHAA 1.2.31
00AE SWCHAA 1.2.33
00AF SWCHAA 1.2.35
00B8 SWCHAA 1.2.41
00B9 SWCHAA 1.2.43
00BA SWCHAA 1.2.45
00BB SWCHAA 1.2.47
00BC SWCHAA 1.2.49
00BD SWCHAA 1.2.51
00BE SWCHAA 1.2.53
00BF SWCHAA 1.2.55
00C8 SWCHAA 2.8.45
00C9 SWCHAA 2.8.47
00CA SWCHAA 2.8.49
00CB SWCHAA 2.8.51
502 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
IAD/NA (Hex) RIT (Type) Position (Rack.Shelf.Slot)
00CC SWCHAA 2.8.53
00CD SWCHAA 2.8.55
00CE SWCHAA 2.8.57
00CF SWCHAA 2.8.59
00D8 SWCHAA 2.2.1
00D9 SWCHAA 2.2.3
00DA SWCHAA 2.2.5
00DB SWCHAA 2.2.7
00DC SWCHAA 2.2.9
00DD SWCHAA 2.2.11
00DE SWCHAA 2.2.13
00DF SWCHAA 2.2.15
00E8 SWCHAA 2.2.21
00E9 SWCHAA 2.2.23
00EA SWCHAA 2.2.25
00EB SWCHAA 2.2.27
00EC SWCHAA 2.2.29
00ED SWCHAA 2.2.31
00EE SWCHAA 2.2.33
00EF SWCHAA 2.2.35
00F8 SWCHAA 2.2.41
00F9 SWCHAA 2.2.43
00FA SWCHAA 2.2.45
00FB SWCHAA 2.2.47
00FC SWCHAA 2.2.49
00FD SWCHAA 2.2.51
00FE SWCHAA 2.2.53
00FF SWCHAA 2.2.55
3BK 20918 AAAA PCZZA Ed.06 503 / 533
29 BSC/TC Alarm Additional Information
IAD/NA (Hex) RIT (Type) Position (Rack.Shelf.Slot)
0100 SWCHAB 1.4.25
0100 TCUC 1.4.9
0101 TCUC 1.4.11
0102 TCUC 1.4.13
0103 TCUC 1.4.15
0104 TCUC 1.4.17
0105 TCUC 1.4.19
0106 TCUC 1.4.21
0107 TCUC 1.4.23
0108 SWCHAA 1.6.5
0109 SWCHAA 1.6.7
010A SWCHAA 1.6.37
010B SWCHAA 1.6.39
010C SWCHAA 1.3.5
010D SWCHAA 1.3.7
010E SWCHAA 1.3.37
010F SWCHAA 1.3.39
0110 TCUC 1.4.41
0110 SWCHAB 1.4.57
0111 TCUC 1.4.43
0112 TCUC 1.4.45
0113 TCUC 1.4.47
0114 TCUC 1.4.49
0115 TCUC 1.4.51
0116 TCUC 1.4.53
0117 TCUC 1.4.55
0120 SWCHAB 1.3.9
0120 DTCC 1.3.13
504 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
IAD/NA (Hex) RIT (Type) Position (Rack.Shelf.Slot)
0121 DTCC 1.3.15
0122 DTCC 1.3.17
0123 DTCC 1.3.19
0124 DTCC 1.3.23
0125 DTCC 1.3.25
0126 DTCC 1.3.27
0127 DTCC 1.3.29
0130 SWCHAB 1.3.41
0130 TCUC 1.3.45
0131 TCUC 1.3.47
0132 TCUC 1.3.49
0133 TCUC 1.3.51
0134 TCUC 1.3.53
0135 TCUC 1.3.55
0136 TCUC 1.3.57
0137 TCUC 1.3.59
0140 SWCHAB 1.4.27
0150 SWCHAB 1.4.59
0160 SWCHAB 1.3.11
0170 SWCHAB 1.3.43
0200 TCUC 2.8.17
0200 SWCHAB 2.8.37
0201 TCUC 2.8.19
0202 TCUC 2.8.21
0203 TCUC 2.8.25
0204 TCUC 2.8.29
0205 TCUC 2.8.31
0206 TCUC 2.8.33
3BK 20918 AAAA PCZZA Ed.06 505 / 533
29 BSC/TC Alarm Additional Information
IAD/NA (Hex) RIT (Type) Position (Rack.Shelf.Slot)
0207 TCUC 2.8.35
0208 SWCHAA 2.7.1
0209 SWCHAA 2.7.3
020A SWCHAA 2.7.5
020B SWCHAA 2.7.7
020C SWCHAA 2.7.9
020D SWCHAA 2.7.11
020E SWCHAA 2.7.13
020F SWCHAA 2.7.15
0210 TCUC 2.7.29
0210 SWCHAB 2.7.45
0211 TCUC 2.7.31
0212 TCUC 2.7.33
0213 TCUC 2.7.35
0214 TCUC 2.7.37
0215 TCUC 2.7.39
0216 TCUC 2.7.41
0217 TCUC 2.7.43
0220 SWCHAB 2.6.9
0220 DTCC 2.6.13
0221 DTCC 2.6.15
0222 DTCC 2.6.17
0223 DTCC 2.6.19
0224 DTCC 2.6.23
0225 DTCC 2.6.25
0226 DTCC 2.6.27
0227 DTCC 2.6.29
0230 SWCHAB 2.6.41
506 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
IAD/NA (Hex) RIT (Type) Position (Rack.Shelf.Slot)
0230 DTCC 2.6.45
0231 DTCC 2.6.47
0232 DTCC 2.6.49
0233 DTCC 2.6.51
0234 DTCC 2.6.55
0235 DTCC 2.6.57
0236 DTCC 2.6.59
0237 DTCC 2.6.61
0240 SWCHAB 2.8.39
0250 SWCHAB 2.7.47
0260 SWCHAB 2.6.11
0270 SWCHAB 2.6.43
0300 TCUC 2.4.9
0300 SWCHAB 2.4.25
0301 TCUC 2.4.11
0302 TCUC 2.4.13
0303 TCUC 2.4.15
0304 TCUC 2.4.17
0305 TCUC 2.4.19
0306 TCUC 2.4.21
0307 TCUC 2.4.23
0308 SWCHAA 2.6.5
0309 SWCHAA 2.6.7
030A SWCHAA 2.6.37
030B SWCHAA 2.6.39
030C SWCHAA 2.3.5
030D SWCHAA 2.3.7
030E SWCHAA 2.3.37
3BK 20918 AAAA PCZZA Ed.06 507 / 533
29 BSC/TC Alarm Additional Information
IAD/NA (Hex) RIT (Type) Position (Rack.Shelf.Slot)
030F SWCHAA 2.3.39
0310 SWCHAB 2.4.57
0310 TCUC 2.4.41
0311 TCUC 2.4.43
0312 TCUC 2.4.45
0313 TCUC 2.4.47
0314 TCUC 2.4.49
0315 TCUC 2.4.51
0316 TCUC 2.4.53
0317 TCUC 2.4.55
0320 SWCHAB 2.3.9
0320 DTCC 2.3.13
0321 DTCC 2.3.15
0322 DTCC 2.3.17
0323 DTCC 2.3.19
0324 DTCC 2.3.23
0325 DTCC 2.3.25
0326 DTCC 2.3.27
0327 DTCC 2.3.29
0330 SWCHAB 2.3.41
0330 TCUC 2.3.45
0331 TCUC 2.3.47
0332 TCUC 2.3.49
0333 TCUC 2.3.51
0334 TCUC 2.3.53
0335 TCUC 2.3.55
0336 TCUC 2.3.57
0337 TCUC 2.3.59
508 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
IAD/NA (Hex) RIT (Type) Position (Rack.Shelf.Slot)
0340 SWCHAB 2.4.27
0350 SWCHAB 2.4.59
0360 SWCHAB 2.3.11
0370 SWCHAB 2.3.43
0400 SWCHAB 3.8.37
0400 TCUC 3.8.17
0401 TCUC 3.8.19
0402 TCUC 3.8.21
0403 TCUC 3.8.25
0404 TCUC 3.8.29
0405 TCUC 3.8.31
0406 TCUC 3.8.33
0407 TCUC 3.8.35
0408 SWCHAA 3.7.1
0409 SWCHAA 3.7.3
040A SWCHAA 3.7.5
040B SWCHAA 3.7.7
040C SWCHAA 3.7.9
040D SWCHAA 3.7.11
040E SWCHAA 3.7.13
040F SWCHAA 3.7.15
0410 SWCHAB 3.7.45
0410 TCUC 3.7.29
0411 TCUC 3.7.31
0412 TCUC 3.7.33
0413 TCUC 3.7.35
0414 TCUC 3.7.37
0415 TCUC 3.7.39
3BK 20918 AAAA PCZZA Ed.06 509 / 533
29 BSC/TC Alarm Additional Information
IAD/NA (Hex) RIT (Type) Position (Rack.Shelf.Slot)
0416 TCUC 3.7.41
0417 TCUC 3.7.43
0420 SWCHAB 3.6.9
0420 DTCC 3.6.13
0421 DTCC 3.6.15
0422 DTCC 3.6.17
0423 DTCC 3.6.19
0424 DTCC 3.6.23
0425 DTCC 3.6.25
0426 DTCC 3.6.27
0427 DTCC 3.6.29
0430 SWCHAB 3.6.41
0430 DTCC 3.6.45
0431 DTCC 3.6.47
0432 DTCC 3.6.49
0433 DTCC 3.6.51
0434 DTCC 3.6.55
0435 DTCC 3.6.57
0436 DTCC 3.6.59
0437 DTCC 3.6.61
0440 SWCHAB 3.8.39
0450 SWCHAB 3.7.47
0460 SWCHAB 3.6.11
0470 SWCHAB 3.6.43
0500 TCUC 3.4.9
0500 SWCHAB 3.4.25
0501 TCUC 3.4.11
0502 TCUC 3.4.13
510 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
IAD/NA (Hex) RIT (Type) Position (Rack.Shelf.Slot)
0503 TCUC 3.4.15
0504 TCUC 3.4.17
0505 TCUC 3.4.19
0506 TCUC 3.4.21
0507 TCUC 3.4.23
0508 SWCHAA 3.6.5
0509 SWCHAA 3.6.7
050A SWCHAA 3.6.37
050B SWCHAA 3.6.39
050C SWCHAA 3.3.5
050D SWCHAA 3.3.7
050E SWCHAA 3.3.37
050F SWCHAA 3.3.39
0510 TCUC 3.4.41
0510 SWCHAB 3.4.57
0511 TCUC 3.4.43
0512 TCUC 3.4.45
0513 TCUC 3.4.47
0514 TCUC 3.4.49
0515 TCUC 3.4.51
0516 TCUC 3.4.53
0517 TCUC 3.4.55
0520 SWCHAB 3.3.9
0520 DTCC 3.3.13
0521 DTCC 3.3.15
0522 DTCC 3.3.17
0523 DTCC 3.3.19
0524 DTCC 3.3.23
3BK 20918 AAAA PCZZA Ed.06 511 / 533
29 BSC/TC Alarm Additional Information
IAD/NA (Hex) RIT (Type) Position (Rack.Shelf.Slot)
0525 DTCC 3.3.25
0526 DTCC 3.3.27
0527 DTCC 3.3.29
0530 SWCHAB 3.3.41
0530 TCUC 3.3.45
0531 TCUC 3.3.47
0532 TCUC 3.3.49
0533 TCUC 3.3.51
0534 TCUC 3.3.53
0535 TCUC 3.3.55
0536 TCUC 3.3.57
0537 TCUC 3.3.59
0540 SWCHAB 3.4.27
0550 SWCHAB 3.4.59
0560 SWCHAB 3.3.11
0570 SWCHAB 3.3.43
Table 51: Relationship IAD/NA to RIT and Position
512 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29.4.32 [51,3]
The additional information bytes for this alarm are defined in the following table.These bytes indicate the case when testing runs successfully.
Byte Number Meaning Test Results Explanation
0 TEST-RAW-DATA(0)
1 TEST-RAW-DATA(1)
Number of times a routinetest has run.
2 TEST-RAW-DATA(2)
3 TEST-RAW-DATA(3)
Number of tunnels.
4 TEST-RAW-DATA(4)
5 TEST-RAW-DATA(5)
Number of tested tunnels.
6 TEST-RAW-DATA(6)
7 TEST-RAW-DATA(7)
Number of successfultunnels.
8 TEST-RAW-DATA(8)
9 TEST-RAW-DATA(9)
Value 255 assigned.
Number of unsuccessfultunnels.
Table 52: Additional Information for Alarm [51,3]
In the unsuccessful cases, the decoding of the byte information is describedin the Link/Switch Test Results section of the Operations & MaintenanceReference Guide.
3BK 20918 AAAA PCZZA Ed.06 513 / 533
29 BSC/TC Alarm Additional Information
29.4.33 [52,1], [52,5] and [52,7]
The additional information bytes for these alarms are defined below.
Byte Number Value Meaning
0 Local clock failure.
1 Reference selector failure.
2 PLL out of range (POOR).
3 Absence of own clock (CLKABS).
4 Watchdog timer expiry (WD).
0-1
5 Access failure (ACCESS-FAIL).
Table 53: Additional Information for Alarms [52,1], [52,5] and [52,7]
29.4.34 [53,0], [53,1], [53,3], [53,4], [53,6] and [53,7]
The additional information bytes for these alarms are defined below.
Byte Number Value Meaning
0-1 0 LOS detected.
Table 54: Additional Information for Alarms [53,0], [53,1], [53,3], [53,4], [53,6] and [53,7]
514 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29.4.35 [53,2]
The additional information bytes for this alarm is defined as follows.
Byte Number Value Meaning
0-1 0 DMA overrun detected by the Broadcast Control Unit inprocessors.
1 DMA underrun detected by the BCU in processors.
Table 55: Additional Information for Alarm [53,2]
29.4.36 [53,5] and [53,8]
The additional information bytes for these alarms are defined below.
Byte Number Value Meaning
0-1 0 CRC detected on broadcast bus to SBL.
1 FTL detected on broadcast bus to SBL.
Table 56: Additional Information for Alarms [53,5] and [53,8]
3BK 20918 AAAA PCZZA Ed.06 515 / 533
29 BSC/TC Alarm Additional Information
29.5 TC AlarmsThis section describes the additional information provided by other TC alarms.
29.5.1 [67,22] to [67,130]
The TC-16 SBL Alarm number is always 1.
29.5.2 [70,219]
The Error is defined below.
NAME SIZE DESCRIPTION
RecoveryLevel
1 The action taken by the TSC to recover from the error(RESET/RESTART/REPORT/NONE).
Error Type 1 The actual error type which is reported by the TSC modules.
Filename 20 Zero-terminated string that gives the filename of the module which reportedthe error.
SPARE 2 -
Line nbr 4 Line number in the file where the error was risen.
Param1 4 Parameter with extra debugging information.
Param2 4 Parameter with extra debugging information.
Table 57: Additional Information for Alarm [70,219]
29.5.3 [73,022] to [73,216]
The alarm numbers are defined as follows.
Alarm NbrHW boards SBLs Provided inthe Alarm
RITS Providedin the Alarm
Board Interface Error
BSI Interface
- 1..8BIUA HWBoards
BSC_ADAPT BIUA
00 - -
Table 58: Additional Information for Alarm [73,022] to [73,216]
516 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29.5.4 [74,20] to [74,202]
The alarm numbers are defined as follows.
Alarm NbrHW boards SBLs Providedin the Alarm
RITS Providedin the Alarm
Board Interface Error
BSI Interface
00 - -SMBI Master
- 11..16
20 - -
G2 BTS HWBOARDS
SMBI Slave
- 21..26
00 - -uBTS HWBOARDS
SMFG
- 11,12,16
00 - -A9100BTS HWBOARDS
BTS_ADAPT
SUM
- 11
Table 59: Additional Information for Alarm [74,20] to [74,202]
3BK 20918 AAAA PCZZA Ed.06 517 / 533
29 BSC/TC Alarm Additional Information
29.5.5 [75,20] to [75,247]
The alarm numbers are defined below.
Alarm NbrHW boards SBLsProvided inthe Alarm
RITSProvided inthe Alarm Board Interface
ErrorATERInterface
TributaryInterface
- 00 - - -
- - 10 - 1st
- - 20 - 2nd
- - 30 - 3rd
-
ASMB
- 40 - 4th
- 00 - - -
- - 10 - 1st
- - 20 - 2nd
- - 30 - 3rd
AlcatelSM2M HWBoards TCG2
-
ASMC
- 40 - 4th
TC-ADAPT 00 - - -AlcatelTRCU TCG2
ATBX
- 02 -
Table 60: Additional Information for Alarm [75,20] to [75,417]
518 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29.5.6 MT120 Board Equipment Reset
The equipment reset/reset fields are described below.
Field Name Size (Bytes) +Type
Meaning
Restart Countervalue
-
Autonomous/Operator This parameter indicates if the reset occurs because of anoperator request or autonomously.
Error Type
One UnsignedCharacter.
Range 60...80 is MT120 specific. The reset structure dependson the hardware type. The hardware type MT120 is mappedonto a range of Error Type from 60 to 80. All the error typeswhich do not belong to this set have the following format, seeTable 63.
Table 61: MT120 Board &Mdash; Equipment Reset/Reset
29.5.7 MT120 &Mdash; Error Range >80
Refer to the table below.
Field Name Size (Bytes) +Type
Meaning
Program Identity Program identity of the process which reports the alarm.
User Data Segment
One UnsignedCharacter.
User Data Segment.
Table 62: MT120 Board, Range >80
3BK 20918 AAAA PCZZA Ed.06 519 / 533
29 BSC/TC Alarm Additional Information
29.5.8 MT120 Board, Range <80
The following table defines the error types for the MT120 board with a rangeless than 80.
Error Type TypeNumber
RecoveryLevel
Description Action AdditionalInfo
Power-on 60 Reset When the MT120is powered on, thisalarm is built.
All memory which belongsto the application iscleared, is set to 00. Thestartup is done with thedefault configuration.
OTPhardwarewatchdog
61 Reset The HW watchdogtimer has expiredcaused by a loopsomewhere in thecode.
A reset is always triggered.In the reset sequence, thelast correct software (1 of3 possibilities) is activated.All memory is cleared. Theconfiguration is saved intoflash memory otherwise.If corrupted, the defaultconfiguration is applied.
None.
OTP externalor internalscenariofailure
62 Reset/Restart An external orinternal scenariohas failed due to atimeout expiration.
A reset/restart is triggered,the OTP comes back to anoperational state using thesaved configuration.
OTP lackof internalresources
63 Reset/Restart This error occurs,when there is nomemory free for theapplications.
OTPexception
64 Reset/Restart An exception hasoccurred, a detailedlist is given inthe additionalinformation, seeTable 64.
OTP SDTcrash
65 Reset/Restart An error hasoccurred in thegenerated code.
DSPpost-mortem
66 Reset/Restart An error hasoccurred in theDSP.
MT120auto-testfailure
67 Reset A hardware errorhas been detectedby the auto-tests.
A buffer is built afterprocessor reset/restart.
See Table64
Table 63: MT120 Board, Error Types, Range <80
520 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
29.5.9 MT120 Board, Error Types
The following table describes the additional information given for the MT120board error types.
Error Type Size Description
Taskname 4 Task name in ASCII which has caused theauto-restart/auto-reset.
MID 2 Internal Message Identifier to identify the internal scenario.
Reference 2 External reference number (Ater Mux or MMI) to identifythe scenario, 0 is for autonomous.
Scenario id 2 Scenario message identifier used to identify the external orautonomous scenario.
0 Operator scenario from the OMC-R
1 Operator from the BSC terminal
2 Operator from the TC terminal
4 Autonomous action
Origin ofaction
1
5 Unknown
01 Indicates three successful auto-restarts.
OTP external orinternal scenariofailure.
FailureDescription
1
FF No information.
Taskname 4 Task name in ASCII which has caused theauto-restart/auto-reset.
0 Message buffer
1 Memory allocation
Memoryregion
1
2 Memory re-allocation
Memory size 4 The requested memory size which could not be served.
OTP external orinternal scenariofailure.
Stack Info 60 The information is taken from the stack.
3BK 20918 AAAA PCZZA Ed.06 521 / 533
29 BSC/TC Alarm Additional Information
Error Type Size Description
Taskname 4 Task name in ASCII which has caused theauto-restart/auto-reset.
01 System Reset
02 Machine Reset
03 Data Storage
04 Instruction storage
06 Alignment
07 Program
08 Floating point unavailable
OD Trace
OE Floating Point assist
10 Software emulation
13 Instruction TLB error
Interrupt entry 1
14 Data TLB error
SRR0 4
SRR1 4
See MPC860 UMD, Interrupts section.
See MPC860 UMD, Interrupts section, only 3 bits arereported.
bit0 MRS.IP
bit1 MRS.ME
MRS 1
bit2 MRS.LE
See MPC860 UMD, Interrupts section, only 3 bits arereported.
bit0 DSISR BIT 1
bit1 DSISR BIT 4
DSISR 1
bit2 DSISR BIT 6
DAR 4
IR 4
See MPC860 UMD, Interrupts section.
OTP exception
Stack Info 60 The information is taken from the stack.
522 / 533 3BK 20918 AAAA PCZZA Ed.06
29 BSC/TC Alarm Additional Information
Error Type Size Description
Taskname 4 Task name in ASCII which has caused theauto-restart/auto-reset.
IR 4 Link register, it gives the program counter in SDT-generatedcode where the error has occurred.
Signal 4 Signal value (in case of an error on a signal).
OTP SDT crash
State 4 State of the autonon when the signal was received.
Error 4 The post-mortem value.DSPpost-mortem
More N Additional Information.
Severity 1 Non-fatal or fatal error detected during auto-tests.
Entity 1 Faulty processor.
Status 1 Detailed step in DSP autotest.
Test 1 Faulty testnumber
-
Error 1 Error code -
Length 1 Length inbytes
-
MT120 auto-testfailure
Info N Additionalinformation
-
Table 64: MT120 board, Error Types, Additional Information
3BK 20918 AAAA PCZZA Ed.06 523 / 533
29 BSC/TC Alarm Additional Information
524 / 533 3BK 20918 AAAA PCZZA Ed.06
30 Consequences of an SBL State Change
30 Consequences of an SBL State Change
This section defines the alarm impact on the system due to an SBL statechange.
3BK 20918 AAAA PCZZA Ed.06 525 / 533
30 Consequences of an SBL State Change
SBL nameSBLstate Impact on system
IT The telecom and O&M link between the BSC and the BTS or twoBTSs is functioning correctly.
FIT Degradation in the telecom and O&M link between the BSC andthe BTS or two BTSs.
FLT Loss of telecom and O&M link between the BSC and the BTS ortwo BTSs.
ABIS-HWAY-TP
OPR The alarm reporting on the transmission link is disabled.
IT Gain of a terrestrial traffic channel to the MSC. The channel canbe used for traffic.
ACH
FLT/FOS Causes loss of a terrestrial traffic channel to the MSC. The channelwill no longer be used for traffic.
IT The telecom link between the TC and the MSC is functioningcorrectly.
FIT Degradation in the telecom and O&M link between the TC andthe MSC.
FLT Loss of telecom and O&M link between the TC and the MSC.
A-PCM-TP
OPR The alarm reporting on the transmission link is disabled.
IT The link between the two submultiplexers is functioning correctly.
FLT Loss of link between the two submultiplexers.
ATER-HWAY-TP
OPR The alarm reporting on the transmission link is disabled.
IT Gain of speech or data connections over this trunk. If the ATR backin service can be used for clock extraction and the BSC is currentlyusing its local clock as the reference, then the BSC tries to switchback to the external clock provided by the ATR.
ATR
FLT/EF Causes loss of speech or data connections over this trunk. If theATR is used for clock extraction, the BSC selects another ATR andpossibly another DTC/BCL-SYS. If no other ATR is available, theBSC uses its local clock. The trunk will no longer be used for traffic.
IT Gain of the backup facility.BATTERY
FLT Causes loss of the backup facility, normally activated on loss ofpower to the RAM disk.
526 / 533 3BK 20918 AAAA PCZZA Ed.06
30 Consequences of an SBL State Change
SBL nameSBLstate Impact on system
IT The rack broadcast bus is distributed to the associated CEs.
FIT Either there is a degradation for the full rack, or there is a failurefor one or 2 CE. This state has no telecom impact if the otherBC-RACK-BUS is IT.
FLT This branch of the broadcast bus is not working anymore. Thisstate has no telecom impact if the other BC-RACK-BUS is IT.
BC-RACK-BUS
OPR The rack broadcast bus (BC_RACK_BUS SBL) is disabled by theoperator.
IT The system broadcast bus is distributed correctly to all racks.BC-SYS-BUS
OPR The system broadcast bus (BC_SYS_BUS SBL) is disabled bythe Operator.
IT The BSC is working correctly.BSC
FIT When two CLK-REP of the same rack (rack not containing the
BCLA-SYS-boards) are failing.
When the BSC is running on a local clock.
Loss of both broadcast buses in the BSC either only at a CE
level, or at rack level, or at system level. LAC paging messages
do not work except for the first 3 cells of the LAC, thuspreventing Mobile terminating calls for the other cells, GPRS
reset procedure do not work anymore. Processors cannotbe preloaded, thus lengthening outages in SW replacement
procedure. RMS measurements are no more started norstopped.
A high number of BSC processors have reported DMA
problems.
IT The BIUA board, which multiplexes BS trunks onto an ABISHWAY-TP at BSC side, is functioning correctly.
FIT There is a degradation in the service provided by the BIUA board,which multiplexes BS trunks onto an ABIS HWAY-TP at BSC side.
FLT/FOS The BSC transmission board (BUIA), which multiplexes BStrunks onto an ABIS HWAY-TP at BSC side, is lost. It cannot beprogrammed or accessed.
BSC-ADAPT
OPR The BIUA board, which multiplexes BS trunks onto an ABISHWAY-TP at BSC side, is disabled.
This state has no impact on the telecom functions of the board,only on the O&M part.
IT The BTS-BIE, which demultiplexes Abis channels from an ABISHWAY-TP at BTS side, is functioning correctly.
FIT There is a degradation in the service provided by BTS-BIE board,which demultiplexes Abis channels from an ABIS HWAY-TP atBTS side.
FLT/FOS The BTS-BIE board, which demultiplexes Abis channels from anABIS HWAY-TP at BTS side, is lost. It cannot be programmed oraccessed.
BTS-ADAPT
OPR This state has no impact on the telecom functions of the board,only on the O&M part.
3BK 20918 AAAA PCZZA Ed.06 527 / 533
30 Consequences of an SBL State Change
SBL nameSBLstate Impact on system
IT Gain of full O&M availability of the cell from the BSC point of view.
FLT/FOS Loss of O&M availability of the cell from the BSC point of view.
BTS-OM
OPR Loss of O&M availability of the cell from the BSC point of view.
IT Gain of telecom availability of the cell from the BSC point of view.
FLT Loss of telecom availability of the cell from the BSC point of view.
FIT Degradation of telecom availability of the cell from the BSC pointof view.
BTS-TEL
OPR Loss of telecom availability of the cell from the BSC point of view.
IT The clock generator works correctly.
FIT The clock has detected the loss of its local clock. There is noimpact on the service.
FLT If only one CLK-GEN is unavailable, there is no impact on theservice. BSC will use the clock provided by the other CLK-GEN.
CLK-GEN
OPR Clock generation is disabled by the operator.
IT The clock repeater works correctly.
FIT The clock repeater loses either System Clock A or System Clock B.
FLT A failure is detected in the BCLA-RACK board. No Clock referenceis repeated.
CLK-REP
OPR The clock repeater is disabled by the operator.
IT The convertor is working correctly.CONV
FLT There is no impact on traffic because the power supplies are inparallel.
IT The CPR is working correctly.CPR
OPR The standby CPR will become the master CPR and takes over allfunctions.
S-CPR Duplex FLT/FOS The standby S-CPR will become the master System CPR andtakes over all functions. SW/DB replacement actions will not beallowed.
O-CPR DUPLEX FLT/FOS The standby O-CPR will become the master O-CPR and takes overall functions. If the old master was carrying the X.25 link with theOMC-R, this link is lost and scheduled performance measurementjobs are not reactivated in due time.
S-CPR/O-CPR FIT The processor has reported a high number of DMA problems.
528 / 533 3BK 20918 AAAA PCZZA Ed.06
30 Consequences of an SBL State Change
SBL nameSBLstate Impact on system
FLT The broadcast processor is not broadcasting.
OPR The broadcast processor is not broadcasting.
CPR (BC_CPR)
NEQ The BC_CPR SBL is not defined in the BSC database.
IT/FIT No impact.DISC
FOS The impact depends on the type of associated CPR and whetherthe CPRs are running in duplex or not.
If the disk goes to FOS, it can no longer be selected for loading ofany BSC CEs or BTSs.
Possible Operator Actions:
Re-init the disk and evaluate the system behavior. If the disk
goes FOS again, then the following option should be applied:
Replace SYS-CPRA.
3BK 20918 AAAA PCZZA Ed.06 529 / 533
30 Consequences of an SBL State Change
SBL nameSBLstate Impact on system
Speech or data connections to the MSC or MFS:
IT These connections are re-established. New connections arepossible. Change back of the SCCP connections on the N7handled by the DTCs occurs.
FLT/FOS These connections on the associated PCM (1/4 of an Atermux) arelost. No new connections are possible.
Depending on the DTC assignation, other function can be affected:
If the DTC carries a TCH resource manager, there is no extraeffect on the calls.
If the DTC carries N7, the SCCP connections are abortedafter some time. N7 Signaling will be handled by other DTCs
(=changeover). Degradation can happen if the remaining
capacity is too small.
If DTC carries BSSAP/GPRSAP, all concerned SCCP
connections are lost.
If the DTC manages a GSL, as long as there are other GSLfor the corresponding GPU, there is no loss of transactions
(degradation can happen if the remaining capacity is too small).
FIT The processor has reported a high number of DMA problems.
DTC
OPR These connections on the associated PCM (1/4 of an Atermux) arelost. No new connections are possible.
Depending on the DTC assignation, other function can be affected:
If the DTC carries a TCH resource manager, there is no extraeffect on the calls.
If the DTC carries N7, the SCCP connections are aborted
after some time. N7 Signaling will be handled by other DTCs(=changeover). Degradation can happen if the remaining
capacity is too small.
If DTC carries BSSAP/GPRSAP, all concerned SCCPconnections are lost.
If the DTC manages a GSL, as long as there are other GSLfor the corresponding GPU, there is no loss of transactions
(degradation can happen if the remaining capacity is too small).
IT N7 Signaling can now be handled by the N7 link (=changeback).
FLT/EF N7 Signaling will be handled by another N7 link (=changeover).
N7
OPR N7 Signaling will be handled by another N7 link (=changeover).
530 / 533 3BK 20918 AAAA PCZZA Ed.06
30 Consequences of an SBL State Change
SBL nameSBLstate Impact on system
IT Communication with the OMU is re-established. Can have animpact on the BTS_O&M state.
OML
FLT Causes loss of communication with the OMU. Will have an impacton the BTS_O&M state, depending on the kind of transactionstarted by the BSC when the OML is down.
IT Communication with the TRE/TRX is established. Gain intelecommunication resource allocation capability on the BTS.
RSL
FLT The RSL SBL may cause loss of communication with the FrameUnit. Leads to a reduced telecommunication resource allocationcapability on the BTS.
IT The multiplexing on the ATER side is functioning correctly.
FIT The multiplexing on the ATER side is degraded.
FLT/FOS The multiplexing board ASMC (It sub-multiplexes A-trunks at theTranscoder)/ASMB (It sub-multiplexes A-trunks at the BSC) isnot functioning correctly. Complete multiplexing on the Ater sideis not being done.
SM-ADAPT
OPR The multiplexing board ASMC/ASMB are disabled. Completemultiplexing on the Ater is not being done.
IT All links associated with the Switch are IT. All links associated withthe switch can be used.
FLT Causes loss of speech or data connections over this switch. Thisswitch can no longer be used. More than 51% of links associatedto Switch are FLT.
SWITCH
FIT Causes loss of some speech or data connections over this switch.This switch can still be used. Less than 51% of links associatedto Switch are FLT.
IT The link adaption between the MSC and the Submultiplexer isfunctioning correctly.
FIT The link adaption between the MSC and the Submultiplexer isdegraded.
FLT The link adaption between the MSC and the Submultiplexer is notfunctioning correctly.
TC-ADAPT
OPR The link adaption between the MSC and the Submultiplexer isdisabled. On-going calls are not lost, no new calls can be initiated.
3BK 20918 AAAA PCZZA Ed.06 531 / 533
30 Consequences of an SBL State Change
SBL nameSBLstate Impact on system
IT Communication with TRE/TRX and/or OMU and/or TSC isestablished. See RSL and/or OML and/or TSL.
FLT/FOS Causes loss of communication with Frame Unit(s) and/or OMUand/or TSC. See RSL and/or OML and/or TSL.
TCU
FIT The processor has reported a high number of DMA problems
IT The A-interface channels managed by the BSC are functioningcorrectly.
FIT The A-interface channels managed by the BSC are degraded.
FLT The A-interface channels managed by the BSC are not functioningcorrectly.
TC-16
OPR The A-interface channels managed by the BSC are disabled.
IT Gain of transmission O&M availability from the BSC point of view.TR-OM
FLT Loss of transmission O&M availability from the BSC point of view.
IT The transmission processor controlling transmission O&M isfunctioning correctly.
TSC
FIT The transmission processor controlling transmission O&M isdegraded.
IT Communication with the TSC is established. Could have an impacton the TR_O&M state.
FLT Causes loss of communication with the TSC. Could have animpact on the TR_O&M state, depending on the kind of transactionstarted by the BSC when the TSL is down.
TSL
FLT/FOS The transmission processor controlling transmission O&M is notfunctioning correctly. Downloading to the TSC has failed.
IT Connection between the BSC and a local terminal or OMC-Ris established.
FLT If there is no X.25 redundancy, causes loss of connection betweenthe BSC and a local terminal or OMC-R.
X.25
OPR If there is no X.25 redundancy, causes loss of connection betweenthe BSC and a local terminal or OMC-R.
532 / 533 3BK 20918 AAAA PCZZA Ed.06
30 Consequences of an SBL State Change
BLANK PAGE BREAK
3BK 20918 AAAA PCZZA Ed.06 533 / 533