ALU BSC-TC Alarm Dictionary

Alcatel BSS
BSC & TC Alarm Dictionary
BSC & TC Document Reference Guide Release B9
3BK 20918 AAAA PCZZA Ed.06
BLANK PAGE BREAK
Status Short title
RELEASED BSC & TC Alarm Dic.

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
2 / 533
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 1.2 A1353-RA AS Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 1.3 LMT Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 1.4 Alarm Information Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Class 32: BSC-ENVIRON Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 2.1 [32,0] CONV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 2.2 [32,1] BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Class 33: PROCESSOR Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 3.1 [33,0] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 3.2 [33,1] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 3.3 [33,3] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 3.4 [33,4] RELC-OV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.5 [33,7] TAKEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 3.6 [33,9] SDCCH-OVRL-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 3.7 [33,251] AUDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Class 34: SWITCH Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 4.1 [34,251] AUDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Class 35: N7 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 5.1 [35,0] LNK-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 5.2 [35,2] RTE-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 5.3 [35,3] INC-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 5.4 [35,251] AUDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Class 36: TRUNK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 6.1 [36,0] LFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 6.2 [36,3] RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 6.3 [36,4] AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 6.4 [36,5] SLIP-OV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 6.5 [36,6] SLIP-UN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 6.6 [36,7] LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 6.7 [36,10] CRCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 6.8 [36,11] CH0-EERH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 6.9 [36,12] CRC4-BERH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 6.10 [36,13] CRC4-BERL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 6.11 [36,251] AUDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Class 38: X.25 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 7.1 [38,0] MODEM-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 7.2 [38,1] LINK-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 7.3 [38,2] PROT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 7.4 [38,251] AUDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Class 39: BSC-SW-ANOMALY Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 8.1 [39,1] OSN-NONRECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 8.2 [39,3] OSN-PROCEDURAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 8.3 [39,4] OSN-RECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 8.4 [39,5] USER-NONRECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 8.5 [39,6] USER-RECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 8.6 [39,7] HWR-NONRECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 8.7 [39,18] SANITY-TIMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Class 42: TELECOM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
4 5
3 / 533
Contents
10
11
12
13
14
9.1 [42,1] NACK-MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2 [42,2] OVERLOAD-MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3 [42,3] START-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4 [42,7] NO-RESET-CIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.5 [42,9] OVERLOAD-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.6 [42,12] TEL-PAIR-LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.7 [42,13] BSC-TRAFFIC-REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.8 [42,14] GPRS-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 43: CELL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.1 [43,0] LOSS-OF-BCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2 [43,1] LOSS-OF-SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3 [43,2] LOSS-OF-TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.4 [43,3] LOSS-OF-ALL-CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.5 [43,4] CELL-TRAFFIC-REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.6 [43,5] OVERLOAD-BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.7 [43,248] CONFIGURED POOLS NOT [FULLY] USABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 44: BTS-OM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 [44,0] AUDIT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 [44,1] PROTOCOL-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 [44,2] RECONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.4 [44,3] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5 [44,5] SW-ACTIVATE-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6 [44,6] CONFIG-DATA-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.7 [44,7] OMU-SELFTEST-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.8 [44,10] ABORT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.9 [44,11] PRELOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.10 [44,12] BTS-HW-CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 45: CHANNEL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1 [45,0] CH-UNBLOCK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 [45,1] CH-BLOCK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.3 [45,2] BSC-CIC-UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.4 [45,3] MSC-CIC-UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.5 [45,4] END-OF-REP-OF-UBLOCK-PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.6 [45,251] AUDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 46: BACKUP-MEDIUM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.1 [46,0] SYNC-CORRUPTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2 [46,1] UNSYNC-OTHER-CORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.3 [46,4] SECFILE-ROLLBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.4 [46,5] SINGLE-UPD-ROLLBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.5 [46,6] DUT-ROLLBACK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6 [46,7] DISC-OOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.7 [46,8] DISC-PARITY-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 47: GLOBAL-BSC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.1 [47,1] SCCP-NOT-AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.2 [47,2] AUTO-BSC-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3 [47,3] AUTO-BSC-RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.4 [47,4] BSC-SYNC-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.5 [47,5] BTS-SYNC-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6 [47,6] AUDIT-COMPLETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.7 [47,7] BSC-HW-RESYNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.8 [47,8] AIFL-FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.9 [47,9] CBC-CONNECTION-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.10 [47,11] ABIS-TS-ALLOC-FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.11 [47,12] INSUFFICIENT-TCU-RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.12 [47,13] TRE-SECTOR-MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
116 118 119 121 123 124 126 128 129 130 132 134 136 138 140 142 145 146 148 149 151 153 155 157 159 160 161 163 164 166 168 170 172 173 175 176 177 179 181 183 185 187 189 190 192 193 194 195 196 197 198 199 201 202 203
4 / 533
Contents
15
16
17
18
19
20
21 22
14.13 [47,14] TCU TOO FRAGMENTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.14 [47,15] SWRPL-IN-PROGRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.15 [47,16] MAX-TRE-EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 48: TR-OM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1 [48,0] AUDIT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2 [48,1] PROTOCOL-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 49: ALERTOR Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.1 [49,0] TRAFF-SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2 [49,1] CH-INCONSIST-SUSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.3 [49,2] TCH-BLOCK-SUSPECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.4 [49,3] TCH-OCCUP-SHORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 50: BSC-EXTERNAL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1 [50,1] EXT-ALARM-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.2 [50,2] EXT-ALARM-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.3 [50,3] EXT-ALARM-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.4 [50,4] EXT-ALARM-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.5 [50,5] EXT-ALARM-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.6 [50,6] EXT-ALARM-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.7 [50,7] EXT-ALARM-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.8 [50,8] EXT-ALARM-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.9 [50,9] EXT-ALARM-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.10 [50,10] EXT-ALARM-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 51: SWITCH-G2 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.1 [51,0] TRANSIENT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2 [51,1] SWITCH-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.3 [51,2] ROUTINE-TEST-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 52: BSC-Clock Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.1 [52,0] LOSS-OF-SEL-CLK-INP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.2 [52,1] LOSS-OF-CLK-GEN-FN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.3 [52,2] SWITCH-TO-LOCAL-CLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.4 [52,3] LOSS-OF-SYSTEM-CLOCK-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.5 [52,4] LOSS-OF-SYSTEM-CLOCK-B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.6 [52,5] LOSS-OF-CLK-DISTR-FN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.7 [52,6] BSC-RUN-ON-LOCAL-CLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.8 [52,7] LOC-CLK-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 53: Broadcast-Bus Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.1 [53,0] LOSS-OF-ONE-BROAD-BUS-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.2 [53,1] LOSS-OF-BOTH-BROAD-BUS-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.3 [53,2] DMA-PROBLEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.4 [53,3] LOSS-OF-ONE-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.5 [53,4] LOSS-OF-BOTH-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.6 [53,5] DEGRAD-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.7 [53,6] LOSS-OF-ONE-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.8 [53,7] LOSS-OF-BOTH-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.9 [53,8] DEGRAD-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 54: BTS-EXTRA-TS-POOL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.1 [54,1] EXTRA TS NOT FULLY USABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 66: TSC-TRUNK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.1 [66,21] LOOP-TO-ITF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2 [66,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3 [66,50] TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.4 [66,66] AIS-2-MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.5 [66,81] FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
205 206 208 211 212 213 215 216 218 220 221 223 224 226 228 230 232 234 236 238 240 242 245 246 247 251 253 254 256 258 260 261 262 264 266 267 268 269 270 272 273 274 275 276 277 279 280 283 284 285 286 288 290
5 / 533
Contents
23
24 25 26
27
28
22.6 [66,86] CRC-MFRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.7 [66,99] BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.8 [66,100] BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.9 [66,102] BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.10 [66,176] FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.11 [66,208] I1I2-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.12 [66,210] TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.13 [66,211] LOSS-OF-CLOCK-2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 67: TSC-CHANNEL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.1 [67,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.2 [67,65] AIS-64-KB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.3 [67,72] AIS-16-KB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.4 [67,122] TRAU-SYNCHRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.5 [67,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.6 [67,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.7 [67,131] INT-BUS-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 70: TSC-SW-ANOMALY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.1 [70,219] SW-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 71: TSC-ENVIRON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.1 [71,0] POWER-SUPPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 73:BSC-ADAPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.1 [73,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.2 [73,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.3 [73,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.4 [73,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.5 [73,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.6 [73,203] LOSS-OF-ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.7 [73,212] LOSS-OF-CLK-8M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.8 [73,213] LOSS-OF-CLK-BOTH-8M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.9 [73,216] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.10 [73,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.11 [73,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.12 [73,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 74: BTS-ADAPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.1 [74,20] BLOCKED-FROM-USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.2 [74,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.3 [74,23] TESTMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.4 [74,122] SYNCHRO-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.5 [74,124] SYNC-AL-CLOCKR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.6 [74,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.7 [74,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.8 [74,139] MISSING-UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.9 [74,141] FORCED-CNTRL-ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.10 [74,142] INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.11 [74,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.12 [74,159] DIAG-TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.13 [74,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.14 [74,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.15 [74,245] LOCAL-REINIT-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.16 [74,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.17 [74,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 75: TCSM-ADAPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.1 [75,20] BLOCKED-FROM-USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.2 [75,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
292 294 296 298 300 302 304 306 309 310 311 313 315 317 319 321 323 324 327 328 331 332 333 335 337 338 340 342 344 346 347 348 350 351 352 354 355 356 358 360 362 364 366 367 369 370 371 373 375 377 379 381 382 383
6 / 533
Contents
29
30
28.3 [75,112] FAN-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.4 [75,122] SYNCHRO-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.5 [75,124] SYNCHRO-AL-CLOCKR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.6 [75,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.7 [75,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.8 [75,136] FIRST-DSP-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.9 [75,139] MISSING-UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.10 [75,141] FORCED-CNTRL-ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.11 [75,142] INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.12 [75,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.13 [75,159] DIAG-TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.14 [75,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.15 [75,208] TRIB-TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.16 [75,209] INT-BUS-FLT-G25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.17 [75,210] ATER-TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.18 [75,211] LOSS-OF-CLOCK-2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.19 [75,216] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.20 [75,221] TRIB-TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.21 [75,222] TRIB-AIS-2MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.22 [75,223] TRIB-FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.23 [75,224] TRIB-CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.24 [75,225] TRIB-BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.25 [75,226] TRIB-BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.26 [75,227] TRIB-BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.27 [75,228] TRIB-FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.28 [75,231] ATER-TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.29 [75,232] ATER-AIS-2MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.30 [75,233] ATER-FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.31 [75,234] ATER-CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.32 [75,235] ATER-BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.33 [75,236] ATER-BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.34 [75,237] ATER-BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.35 [75,238] ATER-FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.36 [75,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.37 [75,245] LOCAL-REINIT-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.38 [75,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.39 [75,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC/TC Alarm Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.1 Restart and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.2 Reset and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.3 System Support Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.4 Other BSC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.5 TC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consequences of an SBL State Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
385 386 388 390 392 394 396 398 400 402 403 404 406 408 410 412 414 415 417 418 420 421 423 425 427 429 431 433 435 437 439 441 443 445 447 449 451 453 454 470 471 471 516 525
7 / 533
Figures
Figures
Figure 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
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
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 Fail Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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
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
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
Tables
Tables
Table 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
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
Preface
Preface
Purpose
The purpose of the alarm dictionary is to provide the operator with a structured method for handling alarm messages generated by the BSC and the TC. This document contains a list of all BSC and TC alarms, and the actions required to nullify them. Alarms are displayed at the OMC-R terminal and at the LMT to inform the operator of system faults.
Note: Whats New
When a fault occurs, a number of alarms can be generated simultaneously. These alarms must be analyzed as a group to determine the precise fault.
In Edition 06
Description 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 05
Description improvement for alarm [46,7] DISC-OOS (Section 13.6).
In Edition 04
Description improvement for alarm [47,14] TCU TOO FRAGMENTED (Section 14.13).
In Edition 03
15 / 533
Preface
Description improvement for alarms [47,11] ABIS-TS-ALLOC-FAILED (Section 14.10) and [47,12] INSUFFICIENT-TCU-RES (Section 14.11).
In Edition 02
Alarm [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
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 01
For dinamic Abis feature the new alarm [54,1] Extra-ts-not-fully-usable is raised instead of alarm [43,248] Configured-pools-not[fully]-usable. The alarm [51,3] global-routine-test-rep is removed because it will not be sent to OMC any more, from B9.
Audience
This document is aimed at telecommunications operators responsible for performing O&M; fault handling and troubleshooting tasks.
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
1 Introduction
1 Introduction
This section describes the structure of alarm messages.
19 / 533
1 Introduction
1.1 Overview
This alarm dictionary provides additional information that is not displayed in the alarm messages sent to the OMC-R, BSC or TC terminals. The dictionary contains alarm definitions for each alarm type produced by the 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 Information

In the A1353-RA OMC-R, Alarm Surveillance provides an efficient means to control, supervise and manage equipment problems in the BSS. Alarms or Alarm notifications consist of messages sent by network resources that have detected problems or failures in the network. These alarms are displayed in lists while alarm counters keep track of statistics. By clicking on an alarm in the list, the operator gets detailed information. AS displays information as described below.
1.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 also shows the boards location by rack, shelf and slot.
20 / 533
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 describes the severity levels. eventType Communication Indicates... a problem with a procedure or process used to convey information from one point to another in the network. degradation in the quality of service in the network. a software or processing fault. an equipment fault. a problem in the enclosure containing the equipment.
Quality of Service Processing Error Equipment Environmental Table 1: Event Types
Severity Level Critical
Indicates... a serious fault condition which requires immediate correction. Example: a managed object goes out of service. a fault condition which requires urgent corrective action. Example: severe degradation in the operation of a managed object. a fault condition which does not affect service but corrective action should be taken to avoid a more serious fault. detection of a potential fault condition. Action should be taken to diagnose and correct the problem to avoid a more serious fault condition. the severity level cannot be defined by the resource which raised the alarm. the alarm was cleared by the resource which raised the alarm.
Major
Minor
Warning
Indeterminate Cleared Table 2: Alarm Severity Levels
In addition to the Object Identification and Alarm Type information, all alarms always give the date and time of the alarm. An alarm may also contain optional information, such as the notification id. Refer to the AS on-line help for more detailed information on AS.
21 / 533
1 Introduction
1.3 LMT Alarm Messages

The 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 message contains 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 RTS number 4 of FU3 (the parent SBL).
22 / 533
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 the appropriate dictionary entry for the valid alarm numbers for a particular alarm Alarm Condition - has one of the following values: begin - alarm on. For fatal failures, the affected SBL changes state to FLT or FOS. For non-fatal failures, the affected SBL changes state to FIT end - alarm off. Indicates the successful recovery of the system. The affected SBL may not change state if other alarms related to the SBL are on event - occurrence of anomaly. No action is required unless it occurs frequently. Event alarms are of short duration and the affected SBL does not change state. The system retry/recovery mechanism has cleared the fault. If a fatal alarm occurs and the affected SBL changes state to FOS, the system isolates the faulty equipment if it cannot be initialized. After a repair action, the operator normally initializes the equipment. If a fatal alarm occurs and the affected SBL changes state to FLT, the system resets the faulty equipment. When the alarm ceases, the system automatically initializes the equipment. If a non-fatal alarm or event occurs, the affected SBLs are put into the FIT state. In the worst situation, the equipment operates in a degraded mode.
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 to determine 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 the fault is indicated. Replace this RIT first and initialize it. If the fault persists, replace another RIT from the list and initialize it.
24 / 533
1 Introduction
1.4 Alarm Information Format

Each alarm definition and description in the dictionary is structured as follows:
1.4.1 Alarm Definition

MO format Banner specificProblems eventType probableCause perceived Severity SBL Table 3: Alarm Definition: LMT format Banner Alarm Class & [number] - Alarm Type & [number] Category SBL
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 Banner
Each BSS alarm definition starts with an identification banner which allows the location of the appropriate definition. It takes the form: [36, 7] TRUNK - LOS
1.4.3.2 eventType
The eventType attribute identifies the basic type of the alarm. Table 1 describes the event Types.
1.4.3.3 specificProblems
The specificProblems provides the alarm class name.
1.4.3.4 probableCause
This attribute provides additional information as to the probable cause of the alarm. Its value belongs to a set of possible values either defined in recommendation X.721 (for those that have a wide applicability) or defined for a particular TMN project.
25 / 533
1 Introduction
1.4.3.5 perceivedSeverity
This attribute gives the severity level of the alarm. Table 2 describes the severity level. The table below provides a mapping between the severity level shown in AS and at the LMT. MO Severity Critical Major Minor Warning LMT Category VPMA, SA PMA DMA MI
Table 4: Mapping of MO Perceived Severity to LMT Category
1.4.4 Alarm Description

1.4.4.1 Alarm Description
The Alarm Description describes the alarm and, where appropriate, the differences to the default perceived severities.
1.4.4.2 Impact on Telecom

This field describes the impact on the Telecom system behavior. It also contains a table indicating which part of the system is affected by the fault in terms of loss, degradation or none. For example, if a cell is affected, the cell column in the table contains a tick ( ) in either 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 the None row, that part of the system is unaffected by the fault. For different impact cases (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 System

The impact on the system is defined in terms of Telecom and/or O&M.;
26 / 533
1 Introduction
1.4.4.4 Failure Identification Strategy

Sometimes more information is necessary to determine the precise fault. The Failure Identification Strategy lists the checks and tests to perform to obtain this 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 more information 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. New performance 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, and empty slots in subracks Software versions and parameter settings are correct.
1.4.4.5 Corrective Actions

A description of the recovery actions to be performed by the operator or maintenance staff. The recovery actions are based on the information provided by 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 the alarm. The figure below shows an example of a flowchart and describes the 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.
27 / 533
1 Introduction
[32,0] CONV
Start field with alarm number and alarm name
Onsite
Identify the faulty DC/DC converter indicated by red illuminated LED.
Onsite
Onsite action fields
Restart faulty converter by disengaging/engaging RIT
Decision field Converter operational? yes Alarm solved
no
Onsite
Replace BSC RIT
Onsite action fields
Decision field Converter operational? yes Alarm solved
no Contact System Support
End Field
Figure 1: Graphical Flowchart for Corrective Actions If the additional information is not decoded, it is displayed as pairs of hexadecimal digits as described in BSC/TC Alarm Additional Information (Section 29). At the BSC terminal, the additional information consists of numbers in the range 0 to 255. Each number represents the contents of one pair of digits. Decoding Additional Information from Alarms Decoding BSC additional information must only be attempted by Alcatel system support personnel. If a fault persists after corrective actions have been taken, send a copy of the alarm message containing the additional information to the Alcatel System Support office.
28 / 533
2 Class 32: BSC-ENVIRON Alarms

This section defines the BSC alarms for the Class 32: BSC-ENVIRON alarm class.
29 / 533
2.1 [32,0] CONV

specificProblems eventType probableCause perceivedSeverity Alarm Description CONV Equipment PowerProblem Critical (VPMA) A9120 BSC The convertor condition is detected by the S-CPR. A fault can be detected for a particular convertor. This is done by monitoring the scan point on the controlling S-CPR. One scan point exists for each convertor. The redundant power supply is available. Impact on System There are two convertors which provide power for each shelf. This provides redundancy and, in the event of one convertor failing, the other convertor provides the power supply. In the event of the two convertors failing, no power is provided to the shelf. However, if both convertors powering the S-CPR fail, the battery back-up then provides its power supply. Evolium A9120 BSC The BSC is able to distinguish between the different convertors with the Evolium A9120 BSC implementation and cabling. Therefore the RIT 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 Loss Degradation
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling
O&M; Capabilities
30 / 533
2.1.1 Corrective Actions

[32,0] CONV
Onsite
Identify the faulty DC/DC converter indicated by red illuminated LED.
Onsite
Restart faulty converter by disengaging/engaging RIT
Converter operational?
yes
Alarm solved
no
Onsite
Replace BSC RIT
Converter operational?
yes
Alarm solved
Figure 2: CONV: Corrective Actions
31 / 533
2.2 [32,1] BAT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description BAT Equipment PowerProblem Critical (VPMA) The battery alarm condition can only be detected by the CPR which it controls. There is one battery controlling each S-CPR. So, if a battery is removed, the CPR goes down and no fault is detected. Only a fault in the actual battery operation can be detected and this is done by monitoring the scan point on the controlling S-CPR. One scan point is provided for each battery. There is a physical connection between the battery and the CPR. When this connection is broken, it is detected by hardware via the scan points. S-CPR-ACTIVE S-CPR (G2 BSC) The memory board is implemented on a daughter board, plugged on the CPRC. The CMFA board, (the flash-based board) indicates a problem with the battery. The battery is empty and has no power to back up. The normal lifespan of a battery is 10 years. The BSC is able to detect a fault, low voltage, on the correct battery due to the fact that two scan points are used, one on CPR1 for battery A and one on CPR2 for battery B. The RIT for both batteries is the same. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
32 / 533
2.2.1 G2-BSC Corrective Actions

[32,1] BAT
Onsite
Identify the suspected SYSCPRC.
Onsite
Replace SYSCPRC
Battery operational?
yes
Alarm solved
no
Contact System Support
Figure 3: BAT: A9120 BSC Corrective Actions
33 / 533
34 / 533
3 Class 33: PROCESSOR Alarms

This section defines the BSC alarms for the Class 33: PROCESSOR alarm class.
35 / 533
3.1 [33,0] RESTART

3.1.1 [33,0] RESTART (CPR)
specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description RESTART ProcessingError SoftwareError Warning (MI) An autonomous restart of a processor has occurred because of a failure condition on the processor. 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. New telecommunication 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 standby CPR now becomes active. SDCCH allocation is not possible for some seconds. New telecommunication transactions fail. Communication with the OMC-R is 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 to carry out PM activities, the restart can cause some problems with file production (such as, loss of last five minute contribution and missing files). Standby OSI-CPR - Duplex: The standby CPR is restarted. If the restarted processor is an OSI-CPR that manages the OSI communications with the OMC-R, some file transfers may be interrupted. If this happens, the OMC-R requests the information again.
Impact on System
36 / 533
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 and its disk are IT, the standby immediately takes over its functions and becomes active. If the restart happens at a five minute boundary and the CPR has to carry out PM activities, the restart can cause some problems with file production (such as, loss of last five minute contribution, missing files). If the restarted processor is an OSI-CPR that manages the OSI communications with the OMC-R, some file transfers may be interrupted. If this happens, the OMC-R requests the information again. Note: For every processor restart, an attempt is made to minimize the impact on the system. Recovery after a processor restart 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).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

The processor returns to service automatically. If the restart procedure fails or there are too many restarts within a certain time frame, the processor is reloaded. See BSC/TC Alarm Additional Information (Section 29) for the byte definition.
37 / 533
3.1.2 [33,0] RESTART (DTC)

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description RESTART ProcessingError SoftwareError Warning (MI) An autonomous restart of a processor occurred because of a failure condition on the processor. The SBL state remains unchanged. All stable calls assigned on TCHs remain unaffected Some Signaling messages can be lost. This can affect some transactions in progress. Note: For every processor restart, an attempt has been made to minimize the impact on the system. Recovery after a processor restart 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 on System
Impact
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

38 / 533
3.1.3 [33,0] RESTART (TCU)

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description RESTART ProcessingError SoftwareError Warning (MI) An autonomous restart of a processor occurred because of a failure condition on the processor. The SBL state remains unchanged. All stable calls are unaffected. Some Signaling messages can be lost, which can affect some transactions in progress. Call setup in SDCCH phase/handover fails. Note: For every processor restart, an attempt has been made to minimize the impact on the system. Recovery after a processor restart 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 on System
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

39 / 533
3.1.4 [33,0] RESTART (TSC)

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description RESTART ProcessingError SoftwareError Warning (MI) An autonomous restart of a processor occurred because of a failure condition on the processor. The SBL state remains unchanged. All stable calls are unaffected. Some Signaling messages can be lost, which can affect some transactions in progress. Call setup in SDCCH phase/handover fails. Note: For every processor restart, an attempt has been made to minimize the impact on the system. Recovery after a processor restart 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 on System
Impact
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

None The processor returns to service automatically. If the restart procedure fails or there are too many restarts within a certain time frame, the processor is reloaded. See BSC/TC Alarm Additional Information (Section 29) for the byte definition.
40 / 533
3.2 [33,1] RESET

3.2.1 [33,1] RESET (CPR/DTC/TCU/TSC)
specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System RESET ProcessingError SoftwareError Major (PMA) An autonomous reload (reboot) of a processor occurred successfully. 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 and existing 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 standby CPR now becomes active. SDCCH allocation is not possible for some seconds. New and existing telecommunication 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.
41 / 533
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, communication with the OMC-R is lost for some seconds. If the reset/reload (reboot) processor is an OSI-CPR that manages the OSI communication with the OMC-R, some file transfers may be interrupted. 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 its functions. If the reset happens at a five minute boundary, there may be problems with production of PM files. Note: For every processor reset/reload (reboot), an attempt is made to minimize the impact on the system. Recovery after a processor reset 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, see Consequences of an SBL State Change (Section 30).
Impact
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling
O&M; Capabilities
Loss Degradation
42 / 533
Impact on System
DTC All calls managed by the processor are lost. For every processor reset/reload (reboot), an attempt is made to minimize the impact on the system. Recovery after a processor reset 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 DTC state change, 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
TCU All calls managed by the processor are lost. For every processor reset/reload (reboot), an attempt has been made to minimize the impact on the system. Recovery after a processor reset 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, see Consequences of an SBL State Change (Section 30).
43 / 533
Impact
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling
O&M; Capabilities
Loss Degradation
Impact on System
TSC All transmission Signaling and downloading managed by the processor are lost. For every processor reset/reload (reboot), an attempt has been made to minimize the impact on the system. Recovery after a processor reset 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, see Consequences of an SBL State Change (Section 30).
Impact
Trunk(s)
Cell/BTS(s)
Transmission Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

If the reload is successful, the processor returns to service automatically. If it does not, contact Alcatel system support. See BSC/TC Alarm Additional Information (Section 29) for the byte definition.
44 / 533
3.2.2 [33,1] RESET (CPR)

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description RESET ProcessingError SoftwareError Indeterminate An autonomous reload (reboot) of a processor occurred.
45 / 533
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 existing 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 standby CPR now becomes active. SDCCH allocation is not possible for some seconds. New and existing telecommunication 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 with the OMC-R is lost for some seconds. If the reset/reload (reboot) processor is an OSI-CPR that manages the OSI communication with the OMC-R, some file transfers may be interrupted. 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 its functions. If the reset happens at a five minute boundary, there may be problems with production of PM files. Note: For every processor reset/reload (reboot), an attempt is made to minimize the impact on the system. Recovery after a processor reset depends on the action 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
Impact
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling
O&M; Capabilities
Loss Degradation

47 / 533
3.2.3 [33,1] RESET (DTC)

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System RESET ProcessingError SoftwareError Major (PMA) An autonomous reload (reboot) of a processor has occurred. All calls managed by the processor are lost. For every processor reset/reload (reboot), an attempt is made to minimize the impact on the system. Recovery after a processor reset 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 -

48 / 533
3.2.4 [33,1] RESET (TCU)

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System RESET ProcessingError SoftwareError Major (PMA) An autonomous reload (reboot) of a processor occurred. All calls managed by the processor are lost. For every processor reset/reload (reboot), an attempt has been made to minimize the impact on the system. Recovery after a processor reset 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).
Trunk(s) -
Cell/BTS(s)
Signaling
Call Handling
O&M; Capabilities

49 / 533
3.2.5 [33,1] RESET (TSC)

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System RESET ProcessingError SoftwareError Major (PMA) An autonomous reload (reboot) of a processor has occurred. All transmission Signaling and downloading managed by the processor are lost. For every processor reset/reload (reboot), an attempt has been made to minimize the impact on the system. Recovery after a processor reset 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

50 / 533
3.3 [33,3] ACCESS-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ACCESS-FAIL Equipment EquipmentMalfunction Major (PMA) The self-maintenance part of the system (i.e., Heartbeat) detected an unreachable processor and informs central maintenance. If a reload request is not received from the processor, the processor SBL is FLT and an alarm is sent with alarm type Access Fail. The processor is not accessible. CPR See Consequences of an SBL State Change (Section 30).
Impact on System
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
Call Handling -
O&M; Capabilities
Loss Degradation -
51 / 533
Impact on System
TCU If the impacted cells have TRX mapped on other TCU, recovery will insure 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
Call Handling -
O&M; Capabilities
Loss Degradation
Impact on System
TSC There is no supervision anymore for the Q1 modules controlled by this TSC (TC, ASMB, BIE, possibly BTS). There is no possibility to perform evolution of the hardware configuration for the same Q1 modules. See Consequences of an SBL State Change (Section 30).
Impact
Trunk(s)
Cell/ BTS(s)
Transmission Signaling -
Call Handling -
O&M; Capabilities
Loss
Degradation -
52 / 533

[33,3] ACCESSFAIL
Subsequent alarm(s) events?
yes
Solve that alarm(s) first
no
MO is Unlocked/ enabled?
yes
Check for BSC switch problems
no
Onsite
Replace CPR/DTC/TCU/TSC
Access operational?
yes
Alarm solved
no
Figure 4: ACCESS-FAIL: Corrective Actions
53 / 533
3.4 [33,4] RELC-OV

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description RELC-OV Equipment EquipmentMalfunction Major (PMA) The processor has been declared FOS and is removed from service. This is done because there have been too many processor reloads within a certain time frame for a specific processor. The loader keeps a record of the number of reload attempts for each processor within a certain time frame. If too many reload attempts occur, central maintenance auto-disables the processor, unless the processor is an S-CPRA (simplex). The auto-disabled processor is blocked from use. Impact on System CPR 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
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation -
54 / 533
Impact on System
TCU If the impacted cells have TRX mapped on other TCU, recovery will insure to keep the TRX with highest priorities If this is not the case, the cells are lost.
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
Impact on System
TSC There is no supervision anymore for the Q1 modules controlled by this TSC (TC, ASMB, BIE, possibly BTS). There is no possibility to perform evolution of the hardware configuration for the same Q1 modules. See Consequences of an SBL State Change (Section 30).
Impact
Trunk(s)
Cell/ BTS(s) Transmission Signaling -
Call Handling -
O&M; Capabilities
Loss Degradation
55 / 533

[33,4] RELOCOV
Lock CPR/DTC/ TCU/TSC
Test CPR/DTC/ TCU/TSC
Verify CPR/DTC/ TCU/TSC
Unlock CPR/DTC/ TCU/TSC
Alarm solved
no
Alarm persists?
yes
Onsite
Replace CPR/DTC/TCU/TSC
Alarm solved
no
Alarm persists?
yes Contact System Support
Figure 5: RELC-OVL: Corrective Actions
56 / 533
3.5 [33,7] TAKEOVER

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TAKEOVER ProcessingError softwareProgramAbnormallyTerminated Warning (MI) There has been a change in the active processor in the case of an active/standby processor pair. The active/standby processor pairs in the BSC are the CPRs or the DTC TCH-RM. This alarm identifies the processor that is now active and is the new master. The previously active 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 to extra 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 the system and ongoing transactions with the OMC-R. Recovery after a CPR 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
Call Handling
O&M; Capabilities
Loss Degradation
57 / 533
Impact on System
DTC TCH-RM During a take-over no radio channel allocation is possible for a short period. See Consequences of an SBL State Change (Section 30).
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

[33,7] TAKEOVER
Lock CPR/DTC
Test CPR/DTC
Verify CPR/DTC
Unlock CPR/DTC
Alarm solved
no
Alarm persists?
Figure 6: TAKEOVER: Corrective Actions
58 / 533
3.6 [33,9] SDCCH-OVRL-BSC

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SDCCH-OVRL-BSC Equipment Indeterminate Warning (MI) The load on the TCU is excessive due to a high number of simultaneously active SDCCHs. 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 new transactions. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

[33,9] SDCCHOVRLBSC
Remap the RSL to spread the load of SDCCH among other TCUs (flatten hot spots).
Alarm solved
no
Alarm persists?
Figure 7: SDCCH-OVRL-BSC: Corrective Actions
59 / 533
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 cell configuration 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 flatten hop spot reshuffling.
60 / 533
3.7 [33,251] AUDIT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description AUDIT ProcessingError SoftwareError Minor (DMA) A maintenance audit freed an SBL that remained in an intermediate maintenance state (AUTO-MSD) following a restart, reload, reboot or a takeover. The audit consists of an autonomous disable followed by an initialize. If the Initialize command fails, the device is FLT. CPR All calls managed by the processor are lost. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling O&M; Capabilities
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
61 / 533
Impact on System
TCU All calls managed by the processor are lost. If a TCUA processor is involved in a processor audit, and the result is unsuccessful, recovery action (blocking and reconfiguration if redundant resources exist) is needed. This applies if the TCUA carries the BCCH or an SDCCH. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[33,251] AUDIT
Lock CPR/DTC/ TCU
Test CPR/DTC/ TCU
Verify CPR/DTC/ TCU
Unlock CPR/DTC/ TCU
Alarm solved
no
Alarm persists?
yes
Onsite
G2: Replace CPR/DTC/TCU
Alarm solved
no
Alarm persists?
Figure 8: AUDIT: Corrective Actions
62 / 533
4 Class 34: SWITCH Alarms

This section defines the BSC alarms for the Class 34: SWITCH alarm class.
63 / 533
4.1 [34,251] AUDIT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description AUDIT Equipment EquipmentMalfunction Minor (DMA) A maintenance audit freed an SBL that remained in the AUTO-MSD state following a restart, reload, reboot or a takeover. The audit consists of an autonomous disable followed by an initialize. If the Initialize command fails, the device is FOS. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling
Call Handling
O&M; Capabilities -
64 / 533

[34,251] AUDIT
Lock SWITCH
Test SWITCH
Verify SWITCH
Unlock SWITCH
Alarm solved
no
Alarm persists?
yes
Onsite
Replace CPR/DTC/TCU
Alarm solved
no
Alarm persists?
65 / 533
66 / 533
5 Class 35: N7 Alarms

This section defines the BSC alarms for the Class 35: N7 alarm class.
67 / 533
5.1 [35,0] LNK-REP

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LNK-REP Communication TransmitterFailure Minor (DMA) This message can represent either an event or a change of status. If it is an event, it indicates a change of link state . If it is a state change, it indicates a change of traffic state. 1. Change of Link state. This alarm is commonly caused by a clock problem. If it is accompanied by SLIP_UNDER_RUN, SLIP_OVER_RUN alarms, there is a lack of synchronisation of the 2 Mbits signals arriving on the BSC. And the transmission boards settings are incorrect. A high error rate on the transmission lines (BER 10-4) has forced use of the transmission modules internal clock. 2. Change of traffic state. There is a persistent problem on the N7 link. If the alarm is accompanied by transmission alarms, there is a transmission problem. Otherwise the problem is caused by an incident at the MSC. The alarm is accompanied by either a SLIP-OV [36,5] or SLIP-UN [36,6] alarm related to the corresponding ATR SBL.
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
68 / 533

The SBL normally returns to IT without operator intervention. Do not run a Disable command because you would need to keep trying to initialize the SBL until successful.
[35,0] LNKREP
Clock alarm events?
yes
Solve Clock alarm(s) first
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 transmission lines forced the use of the transmission modules internal clock.
SLIP... alarm events?
yes
Check/correct transmission board settings
no
Onsite
Alarm solved
Onsite
no
Alarm persists?
Replace Sync Input module
no
2Mbit/s Sync inputs OK?
yes
yes
Onsite Onsite
Replace transmission lines equipment
no
Transmission lines OK?
yes
Alarm persists?
yes
no Alarm solved
Figure 10: LNK-REP: Corrective Actions
69 / 533
5.2 [35,2] RTE-REP

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Alarm Number Impact on System RTE-REP Communication ResponseTimeExcessive Critical (VPMA) A destination became accessible or inaccessible. The alarm number represents the DPC of the MSC. This alarm can come from transmission problem on the Ater mux or on the Atr. In this case, the N7 alarm is a single consequence of these problems and operator can ignore it and he shall first solve the transmission 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 MSC is lost, there is no more possible traffic, the BSC bars automatically all 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
Call Handling -
O&M; Capabilities -
Loss Degradation
70 / 533

[35,2] RTEREP
N7 system works correctly at peer side?
yes
no
Alarm solved
no
Alarm persists?
Check transmission or reset ASMB/ASMC yes
yes
no
Alarm persists?
Figure 11: RTE-REP: Corrective Actions
71 / 533
5.3 [35,3] INC-REP

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description INC-REP Communication Scvfee alarm description below Warning (MI) An incident report is generated whenever the BSC receives a message with either a DPC, OPC or an SSF label part different from the expected one. It is also generated when on changeover/changeback, too many MSUs are received from other DTCs. Excessive incident report generation is avoided by limiting the number of 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
Call Handling -
O&M; Capabilities
Loss Degradation
72 / 533

[35,3] INCREP
Solve N7 problem, use N7 monitor
no
N7 system of DPC, OPC or SSF OK?
yes
Onsite
Replace DTC
Alarm solved
no
Alarm persists?
yes
Figure 12: INC-REP: Corrective Actions
73 / 533
5.4 [35,251] AUDIT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description AUDIT Communication UnderlyingResourceUnavailable Minor (DMA) A maintenance audit freed an SBL that remained in the AUTO-MSD state following a restart, reload, reboot or a takeover. A maintenance audit consists of an autonomous disable followed by an initialize. If the Initialize command fails, the device is FLT. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
74 / 533

[35,251] AUDIT
Lock N7
Test N7
Verify N7
Unlock N7
no
Alarm persists?
yes
Onsite
Alarm solved
Replace suspected RIT
no
Alarm persists?
75 / 533
76 / 533
6 Class 36: TRUNK Alarms

This section defines the BSC alarms for the Class 36: TRUNK alarm class.
77 / 533
6.1 [36,0] LFA

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LFA Communication LossOfFrame Major (PMA) The trunk supervisor detected a loss of frame alignment. This alarm is based on received data in channel 0, before re-timing. 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 on System
Trunk(s) -
Cell/ BTS(s) Signaling -
Call Handling O&M; Capabilities -

[36,0] LFA
Trigger recovery action on peer side and wait until trunk becomes available.
no
Trunk system works correctly at peer side?
yes
Alarm solved
no
Alarm persists?
Figure 14: LFA: Corrective Actions
78 / 533
6.2 [36,3] RAI

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System RAI Communication farEndReceivedFailure Major (PMA) The trunk supervisor detected a RAI, also known as a FEA. Whenever a failure occurs, a loop test is done by the DTC to verify if the failure is internal or external. The trunk is then autonomously disabled. Blocking and release of all associated A-channels is carried out depending on whether the ignore 2 Mbit/s flag is set. The RAI alarm is generated by the BSC in response to a received transmission alarm, (i.e., LIS, AIS, LFA, EER, BERH). This is the BSC view of transmission, so check for transmission alarms. See Consequences of an SBL State Change (Section 30).
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation -
79 / 533

[36,3] RAI
Transmission alarm (LIS, AIS; LFA, EER, BERH) events?
yes
no
no
yes yes
Alarm solved
no
Alarm persists?
Figure 15: RAI: Corrective Actions
80 / 533
6.3 [36,4] AIS

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description AIS Communication AIS Major (PMA) The trunk supervisor detected an all ones indication (i.e., AIS). Less than four zeros in four consecutive frames means AIS. Whenever a failure occurs, a loop 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 AIS alarm is detected by the BSC. This is the BSC view of transmission, so it is important to check for transmission alarms. The trunk is then autonomously disabled. Blocking and release of all associated A-channels is carried out depending on whether the ignore 2 Mbit/s flag is set or not. See Consequences of an SBL State Change (Section 30).
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation -
81 / 533

[36,4] AIS
yes
no
no
yes no yes
Alarm solved
Alarm persists?
Figure 16: AIS: Corrective Actions
82 / 533
6.4 [36,5] SLIP-OV

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SLIP-OV Equipment TimingProblem Warning (MI) The trunk supervisor has detected a slip overrun. An additional signal, DIR, indicates the direction of the slip. An indication will mean that the external frequency clock extracted from its own PCM link is greater, external clock faster than the internal frequency clock selected by the BSC. The SBL state remains unchanged. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
83 / 533

[36,5] SLIPOV
Clock or Synchronization alarm events?
yes
no
Correct Transmission boards settings
no
Transmission board settings OK?
yes
Alarm solved
no
Alarm persists?
yes
Figure 17: SLIP-OV: Corrective Actions
84 / 533
6.5 [36,6] SLIP-UN

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SLIP-UN Equipment TimingProblem Warning (MI) The trunk supervisor has detected slip underrun. A fault is indicated every time a slip occurs. An additional signal, DIR, indicates the direction of the slip. No indication will mean that the external frequency clock extracted from its own PCM link is less, external clock slower than the internal frequency clock selected by the BSC. The SBL state remains unchanged. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
85 / 533

[36,6] SLIPUN
Clock or Synchronization alarm events?
yes
no
Correct Transmission boards settings
no
Transmission board settings OK?
yes no yes
Alarm solved
Alarm persists?
Figure 18: SLIP-UN: Corrective Actions
86 / 533
6.6 [36,7] LOS

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOS Communication LossOfSignal Major (PMA) The trunk supervisor detected a LOS. Whenever a failure occurs, a loop test is done by the DTC to verify if the failure is internal or external. 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 view of transmission, so check for transmission alarms. The trunk is autonomously disabled. Blocking and release of all associated A-channels is carried out depending on whether the ignore 2 Mbit/s flag is set. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s)
87 / 533

[36,7] LOS
yes
no
no
yes Alarm solved no Alarm persists? yes Contact System Support
Figure 19: LOS: Corrective Actions
88 / 533
6.7 [36,10] CRCA

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description CRCA Communication LossOfFrame Warning (MI) This alarm is a quality alarm. It indicates that the number of cyclic redundancy checks reached a certain threshold. The alarm is only issued if the fault persists for more than 100 ms. A local loop test is done to verify if the failure is external or internal by own circuit at the DTC. When the CRCA threshold has been reached, a mechanism is started to search for the new frame alignment to re-synchronize the trunk. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation -
89 / 533

[36,10] CRCA
yes
no
no
Figure 20: CRCA: Corrective Actions
90 / 533
6.8 [36,11] CH0-EERH

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description CH0-EERH Communication DegradedSignal Major (PMA) ERRH is bit errors measured on the frame alignment signal. An excessive error rate has been detected in CH0 >= 10 E-3. The fault is not necessarily on the submultiplexer. The location depends on the distribution of channel 0 throughout the transmission system. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation -

[36,11] CH0EERH
Transmission alarm (LIS, AIS; LFA, BERH) events?
yes
no
no
Figure 21: CH0-EERH: Corrective Actions
91 / 533
6.9 [36,12] CRC4-BERH

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description CRC4-BERH Communication excessiveBerr Major (PMA) This alarm indicates that the BER high measurement based on CRC4 error detection exceeds 10 E-3. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation -

[36,12] CRC4BERH
Transmission alarm events?
yes
no
no
Figure 22: CRC4-BERH: Corrective Actions
92 / 533
6.10 [36,13] CRC4-BERL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description CRC4-BERL Communication DegradedSignal Minor (DMA) The BER based on CRC4 error detection exceeded 10 E-6, but was below 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
Call Handling -
O&M; Capabilities
Loss Degradation

None the trunk is functioning at an extremely good rate.
93 / 533
6.11 [36,251] AUDIT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description AUDIT Equipment EquipmentMalfunction Minor (DMA) A maintenance audit freed an SBL that remained in the AUTO-MSD state following a restart, reload, reboot or a takeover. A maintenance audit consists of an autonomous disable followed by an initialize. If the Initialize command fails, the device is FLT. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
Loss Degradation
94 / 533

[36,251] AUDIT
Lock ATR
Test ATR
Verify ATR
Unlock ATR
no
Alarm persists?
yes Onsite Alarm solved Replace suspected RIT
no
Alarm persists?
95 / 533
96 / 533
7 Class 38: X.25 Alarms

This section defines the BSC alarms for the Class 38: X.25 alarm class.
97 / 533
7.1 [38,0] MODEM-FLT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description MODEM-FLT Communication CommunicationSubsystemFailure Major (PMA) The modem used in the X.25 connection is faulty, or the local terminal power is off. An X.25 can connect the BSC to the BSC local terminal or the BSC to the OMC-R. When both X.25 connections become faulty, the connection between the BSC and the other entity is broken. If the alarm occurs in relation to the link with the OMC-R, the BSC is of course unable to send the alarm to the OMC-R. However, if a local terminal 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 tries repeatedly to send the alarms BSC_SYNC_REQUEST for BSC alarms and TSC_BTS_SYNC_REQUEST for TSC and BTS alarms. When the alarm is eventually received, the OMC-R triggers an alarm audit for the BSC alarms and an alarm audit for the TSC and BTS alarms. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
98 / 533

[38,0] MODEMFLT
BSC SYNCREQUEST alarm events?
yes
no Onsite Check/repair/replace X.25 connection
Onsite Check/repair/replace X.25 modem
Onsite Check/repower/ repair/replace local BSC terminal
Alarm solved
no
Alarm persists?
Figure 24: MODEM-FLT: Corrective Actions
99 / 533
7.2 [38,1] LINK-FLT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System LINK-FLT Communication CommunicationProtocolError Major (PMA) The X.25 L2 is disconnected, although the L1 can still be present. See Consequences of an SBL State Change (Section 30).
Impact
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
100 / 533

[38,1] LINKFLT
Lock X.25
Unlock X.25
Trigger recovery action on peer side and wait until X.25 link becomes available.
no
X.25 link works correctly at peer side?
yes
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes
Figure 25: LINK-FLT: Corrective Actions
101 / 533
7.3 [38,2] PROT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description PROT Communication CommunicationProtocolError Warning (MI) 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
Call Handling -
O&M; Capabilities
Loss Degradation
102 / 533

[38,2] PROT
Lock X.25
Unlock X.25
Second timeout on:
clear confirmation
restart confirmation
Trigger recovery action on peer side and wait until X.25 link becomes available.
no
X.25 link works correctly at peer side?
yes
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes
Figure 26: PROT: Corrective Actions
103 / 533
7.4 [38,251] AUDIT

specificProblems: eventType: eventType: probableCause: perceivedSeverity: Alarm Description AUDIT Communication Communication UnderlyingResourceUnavailable Minor (DMA) A maintenance audit freed an SBL that remained in the AUTO-MSD state following a restart, reload, reboot or a takeover. A maintenance audit consists of an autonomous disable followed by an initialize. If the Initialize command fails, the device is FLT. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
104 / 533

[38,251] AUDIT
Lock X.25
Test X.25
Verify X.25
Unlock X.25
no
Alarm persists?
yes Onsite Alarm solved Replace suspected X.25 RIT
no
Alarm persists?
105 / 533
106 / 533
8 Class 39: BSC-SW-ANOMALY Alarms

This section defines the BSC alarms for the Class 39: BSC-SW-ANOMALY alarm class.
107 / 533
8.1 [39,1] OSN-NONRECOVERABLE

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description OSN-NONRECOVERABLE ProcessingError SoftwareError Warning (MI) If the function call is not accepted by the OS, then an OSN Non Recoverable Error is generated. The error handler receives a OSN non-recoverable error. This triggers a processor restart. 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 on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

Contact your Alcatel system support so the cause of the error can be examined. The information must be analyzed by qualified personnel using the sequence number and the user data. The meaning of the user sequence number and the user data is different for every module.
108 / 533
8.2 [39,3] OSN-PROCEDURAL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description OSN-PROCEDURAL ProcessingError SoftwareError Warning (MI) An application request of an OSN primitive was passed to the stack with incorrect parameters. The SBL state remains unchanged See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

109 / 533
8.3 [39,4] OSN-RECOVERABLE

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description OSN-RECOVERABLE ProcessingError SoftwareError Warning (MI) The OSN reported a recoverable error. A functionally incorrect OSN primitive application was requested. The processor is not restarted. The SBL state remains unchanged. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

110 / 533
8.4 [39,5] USER-NONRECOVERABLE

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description USER-NONRECOVERABLE ProcessingError SoftwareError Warning (MI) An application has generated a software error indicating a fault which does not cause a malfunction. Subsequently, further errors have been detected which cause the software to malfunction, a User Non Recoverable Error is generated. The processor is restarted. 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 on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

111 / 533
8.5 [39,6] USER-RECOVERABLE

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description USER-RECOVERABLE ProcessingError SoftwareError Warning (MI) An application generated a software error indicating a fault that has no further operational effect. The SBL state remains unchanged. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -

112 / 533
8.6 [39,7] HWR-NONRECOVERABLE

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description HWR-NONRECOVERABLE Equipment EquipmentMalfunction Warning (MI) The error handler received information concerning a hardware non-recoverable error. 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 on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

113 / 533
8.7 [39,18] SANITY-TIMER

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SANITY-TIMER ProcessingError softwareProgramAbnormallyTerminated Warning (MI) A hardware sanity timer NMI expired. This is because an application has run too long or is running in a loop. This causes the processor to reload. Expiration of the sanity timer caused a processor reload. All ongoing transactions through the processors are released in a controlled manner 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 on System
Impact
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

114 / 533
9 Class 42: TELECOM Alarms

This section defines the BSC alarms for the Class 42: TELECOM alarm class.
115 / 533
9.1 [42,1] NACK-MSC

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description NACK-MSC Communication ResponseTimeExcessive Warning (MI) The BSC did not receive a RESET ACK message from the MSC before expiration of timer T4. The SBL state remains unchanged. See Consequences of an SBL State Change (Section 30). The BSC repeats the reset procedure indefinitely until the MSC sends a positive acknowledgment.
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
116 / 533

[42,1] NACKMSC
yes N7 alarm events?
no
Onsite RESET and RESET_ACK message events? yes Repair/replace N7 component
no Alarm solved no Alarm persists?
Figure 28: NACK-MSC: Corrective Actions
117 / 533
9.2 [42,2] OVERLOAD-MSC

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description OVERLOAD-MSC QualityOfService Congestion Warning (MI) An overload message was received from the MSC and this triggered an overload reaction. While timer T5 remains activated after receipt of an overload message, it inhibits the effect of any further overload messages. When timer T5 expires, 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
Call Handling -
O&M; Capabilities
Loss Degradation

None an autonomous overload reaction is triggered.
118 / 533
9.3 [42,3] START-RESET

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description START-RESET QualityOfService PerformanceDegraded Warning (MI) A reset procedure has started in the BSC. The alarm indicates whether the reset is requested by the MSC, or if the reset was due to loss of communication with the MSC, (i.e., timer TI expired in the BSC). The SBL state remains unchanged. All calls are cleared in the BSC. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
Loss Degradation
119 / 533

[42,3] STARTRESET
Local communication alarm events?
yes
no
Trigger action on MSC side
Alarm solved
no
Alarm persists?
Operator at OMC-R
Figure 29: START-RESET: Corrective Actions
120 / 533
9.4 [42,7] NO-RESET-CIC

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description NO-RESET-CIC Communication ResponseTimeExcessive Warning (MI) The BSC requested the reset of a CIC towards the MSC. This reset request is attempted a predefined number of times. If, following the maximum number of retries, the BSC still has not received the RESET CIC ACK, then this alarm is issued. The SBL state remains unchanged. This A-channel is released internally by the BSC. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
121 / 533

[42,7] NORESETCIC
Transmission or trunk alarm events?
yes
no
Trigger CIC recovery action at MSC side
Alarm solved
no
Alarm persists?
Figure 30: NO-RESET-CIC: Corrective Actions
122 / 533
9.5 [42,9] OVERLOAD-BSC

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System OVERLOAD-BSC Equipment ProcessorProblem Major (PMA) This alarm is sent by the BSC to report an BSC processor overload. 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
Call Handling -
O&M; Capabilities
Loss Degradation

[42,9] OVERLOADBSC
Processor related board alarm events?
yes
no
Figure 31: OVERLOAD-BSC: Corrective Actions
123 / 533
9.6 [42,12] TEL-PAIR-LOST

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Alarm Number Impact on System TEL-PAIR-LOST Equipment EquipmentMalfunction Critical (VPMA) Sent by the BSC to report the loss of a TCH-DTC pair. This is the ID of the TCH-DTC pair lost. The SBL state remains unchanged. Since the TCH-DTC pair handles calls, there is a degradation in the call handling facilities of 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
124 / 533

[42,12] TELPAIRLOST
Lock reported DTC
Test reported DTC
Verify reported DTC
Unlock reported DTC
no
Alarm persists?
yes Onsite
Alarm solved
Replace reported faulty DTC
no
Alarm persists?
Figure 32: TEL-PAIR-LOST: Corrective Actions
125 / 533
9.7 [42,13] BSC-TRAFFIC-REPORT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description BSC-TRAFFIC-REPORT QualityOfService Congestion Warning (MI) Sent by the BSC when: An MSC_OVERLOAD/BSC_OVERLOAD is received and no BSS actions 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 has been 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 access the system. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
126 / 533

[42,13] BSCTRAFFICREPORT
Analyze additional information bytes
Related alarm events?
yes
Figure 33: BSC-TRAFFIC-REPORT: Corrective Actions
127 / 533
9.8 [42,14] GPRS-RESET

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description GPRS-RESET Equipment Indeterminate Major (PMA) This alarm is used when a RESET command arrives from the MFS or when all GSL, all GPRS application process or TCH-RM pairs are down. A RESET can also occur in the case of an excessive amount of lack of acknowledgments between the MFS and the BSC. The SBL state remains unchanged. A reset of the MFS affects GPRS functionality only. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
MFS Signaling
MFS Call Handling
MFS O&M; Capabilities
Loss Degradation

None an autonomous reset is triggered.
128 / 533
10 Class 43: CELL Alarms

This section defines the BSC alarms for the Class 43: CELL alarm class.
129 / 533
10.1 [43,0] LOSS-OF-BCCH

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOSS-OF-BCCH QualityOfService PerfomanceDegraded Major (PMA) - in commercial use, Warning (MI) - out of commercial use The transceiver time slot configured to carry the BCCH is unavailable for telecommunication purposes. A BCCH must exist for each cell in order to transmit system information to the MS. This enables the MS to assign calls within the cell. Since the BCCH is no longer able to transmit system information, calls are not assigned in the cell. A BCCH channel can be lost when equipment carrying a BCCH fails or is disabled. The BTS-TEL is FIT and a three-minute timer is started to allow the Frame Unit to reload. If the Frame Unit is reloaded successfully, then BTS-TEL goes to IT; otherwise BTS-TEL goes to FLT. Since the BCCH is a vital resource, recovery must be attempted. Recovery involves reconfiguration of another channel as a BCCH, at the expense of the current configuration of the channel. Recovery means blocking/unblocking action, state update and perhaps a reconfiguration action (if redundant resources are available). When the BCCH is recovered, another alarm is generated for the lost channel involved in the reconfiguration. When the Loss of BCCH alarm is active, no other cell type alarm is sent for this cell to indicate further loss or gain of channels. This continues unless the BCCH channel becomes available. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities -
130 / 533

[43,0] BSCTRAFFICREPORT
Related BTS alarm events?
yes
Trigger maintenance action on that alarm(s)
no no
Alarm solved
Alarm persists?
Figure 34: LOSS-OF-BCCH: Corrective Actions
131 / 533
10.2 [43,1] LOSS-OF-SDCCH

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOSS-OF-SDCCH QualityOfService PerfomanceDegraded Minor (DMA) - in commercial use, Warning (MI) - out of commercial use One or more transmission time slots configured to carry the SDCCH are unavailable for telecommunication purposes. Loss of the SDCCH leads to a decrease in call setup and handover capacity, fewer numbers of SDCCHs are available to handle call setup and 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 the expense of the current configuration of the channel. Recovery means blocking/unblocking action, state update and perhaps a reconfiguration action (if redundant resources are available). When the SDCCH is recovered, another alarm is generated for the lost channel involved in the reconfiguration. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
132 / 533

[43,1] LOSSOFSDCCH
yes
no no Alarm persists?
Alarm solved
Figure 35: LOSS-OF-SDCCH: Corrective Actions
133 / 533
10.3 [43,2] LOSS-OF-TCH

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOSS-OF-TCH QualityOfService PerfomanceDegraded Minor (DMA) - in commercial use, Warning (MI) - out of commercial use One or more transceiver time slots configured to carry the TCH are unavailable for telecommunication purposes. Loss of a TCH leads to a decrease in traffic capacity as there are fewer available TCHs to carry calls. A TCH might be lost due to a successful recovery of the TRX/TCU where 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 on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
134 / 533

[43,2] LOSSOFTCH
yes
Figure 36: LOSS-OF-TCH: Corrective Actions
135 / 533
10.4 [43,3] LOSS-OF-ALL-CHAN

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOSS-OF-ALL-CHAN QualityOfService PerfomanceDegraded Major (PMA) - in commercial use, Warning (MI) - out of commercial use All transceiver time slots of a BTS are unavailable for telecommunication purposes.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 becoming FLT/FOS. This causes the BTS-TEL to go to FLT when configuration data is sent to the BTS. Impact on System All channels in the cell are unavailable. If configuration data cannot be sent to the BTS, or BTS-TEL is FLT, the cell is barred. A Mobile Station never 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 this cell to indicate further loss or gain of channels. This continues unless the BCCH channel becomes available. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s)
Signaling -
Call Handling
O&M; Capabilities
136 / 533

[43,3] LOSSOF ALLCHAN
Lock BTSOM
Unlock BTSOM
yes
no All RSLs in BTS faulty? yes
RESET BTS for reconfiguration
no
Alarm solved
no
Alarm persists?
yes
Figure 37: LOSS-OF-ALL-CHAN: Corrective Actions
137 / 533
10.5 [43,4] CELL-TRAFFIC-REPORT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description CELL-TRAFFIC-REPORT QualityOfService PerfomanceDegraded Warning (MI) Sent by the BSC when: A BTS_OVERLOAD message is received from a BCCH transceiver A BTS_OVERLOAD message is received from a non-BCCH transceiver and the leaky-bucket counter overflows A TCU processor overload is detected There is a change of the RACH parameters on cell level (dynamic RACH). Impact on System The SBL state remains unchanged. MSs belonging to the barred access classes can no longer access the system. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
138 / 533

[43,4] CELLTRAFFICREPORT
yes
no
BTSOVERLOAD alarm coming from BCCH TRX?
yes
Reduce BTS load
no
TCU processor overload alarm events?* no
yes
Solve that alarm(s)
Dynamic RACH parameters on cell level OK? yes
no
Correct RACH parameters
Alarm solved
no
Alarm persists?
yes
Figure 38: CELL-TRAFFIC-REPORT: Corrective Actions
139 / 533
10.6 [43,5] OVERLOAD-BTS

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description OVERLOAD-BTS QualityOfService Congestion Warning (MI) 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 timer T1 is not running. The SBL state remains unchanged. MSs belonging to the barred access classes can no longer access the system. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Call Handling -
O&M; Capabilities -
140 / 533

[43,5] OVERLOADBTS
yes
no
TCU alarm events?
yes
Solve that alarm(s)
Figure 39: OVERLOAD-BTS: Corrective Actions
141 / 533
10.7 [43,248] CONFIGURED POOLS NOT [FULLY] USABLE

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description CONFIGURED POOLS NOT [FULLY] USABLE QualityOfService PerformanceDegraded Minor (DMA) 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 changed to 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 a Evolium 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.
Trunk(s) -
Call Handling -
O&M Capabilities -
142 / 533

[43,248] CONFIGURED POOLS NOT [FULLY] USABLE
HSDS state is degraded?
yes
TCU that any pool mapped to is IT?
yes
Check the second Abis that any pools mapped to
no
no Check for TCU problem
None
Alarm solved
no
Alarm persists?
Figure 40: CONFIGURED POOLS NOT [FULLY] USABLE: Corrective Actions
143 / 533
144 / 533
11 Class 44: BTS-OM Alarms

This section defines the BSC alarms for the Class 44: BST-OM alarm class.
145 / 533
11.1 [44,0] AUDIT-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description AUDIT-FAIL Communication CommunicationSubsystemFailure Minor (DMA) A failure occurs in the BSC-BTS audit. A failure in the BSC-BTS Audit scenario is considered to be any failure occurring between the request for an Audit from the BSC and reception of the Conf_compl message from the BTS. This Alarm is never sent as a result of no reception of An ACK. This alarm is also sent when CDM sending fails in cases NOT under software activation and reconfiguration, i.e. OMU restart, CDM sending on logical data change, etc. Impact on System When BTS-OM is FLT but OML is up, the BSC triggers an audit every two minutes until one succeeds. The BTS still handles calls, but if a reconfiguration occurs and the BTS-OM is FLT, BTS-TEL goes to FLT. The message OMU started, indicating that the BTS (OMU) has auto-reset, can result in a new BTS/OMU downloading scenario. In the event of a successful download, the BTS-OM becomes IT. When the BTS-OM goes from FLT to IT due to success of a BSC-BTS audit, or reset BTS/OMU, an alarm END for all alarm types audit failure is sent. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities
146 / 533

[44,0] AUDITFAIL
Reset BTS or OML TCU
no OML up?
yes
No operator action required
Alarm solved
no
Alarm persists?
Figure 41: AUDIT-FAIL: Corrective Actions
147 / 533
11.2 [44,1] PROTOCOL-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description PROTOCOL-FAIL Communication CommunicationProtocolError Minor (DMA) A protocol failure on the Abis interface occurred. An ACK to some message was not received after three retries. When the BTS-OM is FLT but OML is up, the BSC triggers an audit every two minutes until one succeeds. The BTS still handles calls, but if a reconfiguration occurs and BTS-OM is FLT, BTS-TEL goes to FLT. The message OMU started, indicating that the BTS (OMU) has auto reset, can result in a new BTS/OMU download scenario. In the event of a successful download, the BTS-OM becomes IT. When the BTS-OM goes from FLT to IT due to success of a BSC-BTS audit, or BTS/OMU reset, an END for all alarm types protocol failure is sent. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

[44,1] PROTOCOLFAIL
no OML up?
yes
Alarm solved
no
Alarm persists?
yes
Figure 42: PROTOCOL-FAIL: Corrective Actions
148 / 533
11.3 [44,2] RECONFIG-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description RECONFIG-FAIL ProcessingError ConfigurationOrCustomizationError Minor (DMA) This alarm is sent as a result of a failure to do a required reconfiguration action, triggered due to loss of vital resources or due to failure in conveying CDM to the BTS. When the BTS-OM is FLT but OML is up, the BSC triggers an audit every two minutes until one succeeds. The BTS still handles calls, but if a reconfiguration occurs and BTS-OM is FLT, BTS-TEL goes to FLT. The message OMU started, indicating that BTS (OMU) has auto-reset, can result in a new BTS/OMU download scenario. In the event of a successful download, the BTS-OM becomes IT. When BTS-OM goes from FLT to IT due to success of a BSC-BTS audit, 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 on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities
149 / 533

[44,2] RECONFIGFAIL
no OML up?
yes
Alarm solved
no
Alarm persists?
yes
Figure 43: RECONFIG-FAIL: Corrective Actions
150 / 533
11.4 [44,3] DOWNLOAD-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description DOWNLOAD-FAIL ProcessingError ConfigurationOrCustomizationError Minor (DMA) Three download attempts failed. Any failure from BTS-DOWNLOAD-REQ until a successful BTS-DOWNLOAD-REP is considered a download failure. The OMU updates the BTS-OM to FOS after three download attempts by the BSC have failed (i.e., BTS-DOWNLOAD-REQ until a successful BTS-DOWNLOAD-REP). See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities
151 / 533

[44,3] DOWNLOADFAIL
BTS or OMU restart events?
yes
Check files on standby CPR disk
no
Lock BTSOM
Unlock BTSOM
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes
yes
Data files on standby CPR disk ok?
yes
no
Reload correct data file from software package
Figure 44: DOWNLOAD-FAIL: Corrective Actions
152 / 533
11.5 [44,5] SW-ACTIVATE-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SW-ACTIVATE-FAIL ProcessingError ConfigurationOrCustomizationError Minor (DMA) This configuration failure alarm indicates that a software activation failed following a download attempt. If the software activation failure requires operator intervention, BTS-OM goes to FOS. Otherwise, it goes to FLT. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
153 / 533

[44,5] SWACTIVATEFAIL
Correct BTS hardware or CPR hawrdware data
no
BTS hardware corresponds to hardware data on standby CPR disk?
yes
Lock BTSOM
Unlock BTSOM
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes
yes
Figure 45: SW-ACTIVATE-FAIL: Corrective Actions
154 / 533
11.6 [44,6] CONFIG-DATA-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description CONFIG-DATA-FAIL ProcessingError ConfigurationOrCustomizationError Minor (DMA) There is a problem with the configuration data because of a logical parameter modification or the restart of the BTS or OMU. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
155 / 533

[44,6] CONFIGDATAFAIL
BTS/OMU restarts?
yes
no
Data files on standby CPR disk ok?
no
yes
Logical parameters modified?
yes
no
Logical parameters are valid? yes
no
Reload correct data file from software package
Lock BTSOM
Unlock BTSOM Contact System Support
Alarm solved
no
Alarm persists?
Figure 46: CONFIG-DATA-FAIL: Corrective Actions
156 / 533
11.7 [44,7] OMU-SELFTEST-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System OMU-SELFTEST-FAIL Equipment EquipmentMalfunction Minor (DMA) The OMU failed its self-test. See Consequences of an SBL State Change (Section 30).
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
157 / 533

[44,7] OMLSELFTEST FAIL
Lock BTSOM
Unlock BTSOM
Alarm persists?
no
Alarm solved
yes
Onsite
G2: Replace reported faulty OMU
Alarm persists?
no
Alarm solved
Figure 47: OMU-SELFTEST-FAIL: Corrective Actions
158 / 533
11.8 [44,10] ABORT-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ABORT-FAIL ProcessingError ConfigurationOrCustomizationError Minor (DMA) The Abort failure alarm indicates that the attempt to remove the preloaded BTS software files has failed. The SBL state remains unchanged. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[44,10] ABORT FAIL
Retrigger remove action
Alarm solved
no
Alarm persists?
Figure 48: ABORT-FAIL: Corrective Actions
159 / 533
11.9 [44,11] PRELOAD-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System PRELOAD-FAIL ProcessingError ConfigurationOrCustomizationError Minor (DMA) This alarm indicates that preloading of the BTS software has failed. The SBL state remains unchanged. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
Figure 49: PRELOAD-FAIL: Corrective Actions
160 / 533
11.10 [44,12] BTS-HW-CONFIG-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description BTS-HW-HW-CONFIG-FAIL ProcessingError ConfigurationOrCustomizationError Minor (DMA) This alarm indicates that the BTS extension/reduction has failed due a restriction in the BTS-HW. During an audit, added or removed TREs are detected and reported to the BSC. If the Auto-alloc flag is set on the Abis, the BSC will attempt to allocate TCUs and TSs. This can fail, if the BTS is created with certain characteristics and the BTS cannot support these characteristics. The SBL state remains unchanged. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[44,12] BTSHW CONFIGFAIL
BTS characteristic correspond to BTS HW capabilities files? yes
no
Correct characteristics
Alarm persists? Contact System Support yes Contact System Support
no
Alarm solved
Figure 50: BTS-HW-CONFIG-FAIL: Corrective Actions
161 / 533
G2 BTS BIUMD QMUX-TS [0,6,2] [1..31,0,2] SMBI [0,6,2] [1..31,0/2/4/6,2] [1..31,0,4/8] [0,6,2] [1..31,0/2/4/6,2] any mapping chain/ring allowed but only in chain and w/o RC-TS allowed allowed SMFG [0,6,2] [1..31,0/2/4/6,2] [1..31,0,4/8] [0,6,2] [1..31,0/2/4/6,2] any mapping chain/ring allowed but only in chain and w/o RC-TS allowed allowed
BTS A9100 SUME [0,6,2] [1..31,0/2/4/6,2] [1..31,0,4/8] [0,6,2] [1..31,0/2/4/6,2] any mapping chain/ring allowed but only in chain and w/o RC-TS allowed allowed
R-TS S-TS
[1..31,0, 4/8]* [0,3,2] [15,4,2]* [17,4,2]* any mapping chain/ring allowed but only in chain and w/o RC-TS allowed allowed MUX Rule = No MUX only allowed MUX Rate = MUX-rate-BTS only allowed
Traffic channel Topology x-connect table
usable- TS auto-alloc MUX Rule
Any MUX Rule allowed
MUX Rate
Any MUX Rate allowed
[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 SMFG SUME
SMBI MBEG or SUMP MBLG or MBL1G or MBL1D or
Table 6: NE Hardware RIT Mapping
162 / 533
12 Class 45: CHANNEL Alarms

This section defines the BSC alarms for the Class 45: CHANNEL alarm class.
163 / 533
12.1 [45,0] CH-UNBLOCK-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description CH-UNBLOCK-FAIL Communication CommunicationProtocolError Minor (DMA) A timeout expired for the MSC to send an acknowledgement to the BSC in response to an A-channel unblocking message. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
164 / 533

[45,0] CHUNBLOCK FAIL
Lock ACH
Unlock ACH
Alarm persists?
no
Alarm solved
yes Onsite N7 links operational? no Repair/replace N7 equipment
yes
Alarm persists?
no
Alarm solved
yes
Trigger N7 checks at MSC side
Alarm persists?
no
Alarm solved
Figure 51: CH-UNBLOCK-FAIL: Corrective Actions
165 / 533
12.2 [45,1] CH-BLOCK-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description CH-BLOCK-FAIL Communication CommunicationProtocolError Warning (MI) A timeout expired for the MSC to send an acknowledgement to the BSC in response to an A-channel blocking message. The SBL state remains unchanged. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
166 / 533

[45,1] CHBLOCK FAIL
Lock ACH
Unlock ACH
Alarm persists?
no
Alarm solved
yes Onsite N7 links operational? no Repair/replace N7 equipment
yes
Alarm persists?
no
Alarm solved
yes
Trigger N7 checks at MSC side
Alarm persists?
no
Alarm solved
Figure 52: CH-BLOCK-FAIL: Corrective Actions
167 / 533
12.3 [45,2] BSC-CIC-UNKNOWN

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description BSC-CIC-UNKNOWN ProcessingError ConfigurationOrCustomizationError Warning (MI) This alarm is sent out in response to a request initiated by the BSC which specifies a circuit which is not equipped in the MSC. On reception of an unequipped circuit message from the BSC, the MSC 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 a later stage. This fault is for one A-channel, although there is a strong possibility that faults exist on other A-channels at the A Interface. On reception of an unequipped circuit message from the BSC, the MSC removes the indicated circuits from further selection. See Consequences of an SBL State Change (Section 30).
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
168 / 533

[45,2] BSCCIC UNKNOWN
Lock assoc. Atrunk
Unlock assoc. Atrunk to bring ACH back in service, as faults can exist for other Achannels on Atrunk
Alarm persists?
no
Alarm solved
Figure 53: BSC-CIC-UNKNOWN: Corrective Actions
169 / 533
12.4 [45,3] MSC-CIC-UNKNOWN

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description MSC-CIC-UNKNOWN ProcessingError ConfigurationOrCustomizationError Warning (MI) The MSC initiated a request. The request specifies a circuit which is unequipped in the BSC. The SBL state remains unchanged. If the circuit indicated in the message is not equipped in the BSC, the BSC ignores the circuit. The BSC does not make any response to the circuit 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 later stage. This fault is for one A-channel, although there is a strong possibility that faults exist on other A-channels at the A Interface. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
170 / 533

[45,3] MSCCIC UNKNOWN
Lock aossc. Atrunk
Alarm persists?
no
Alarm solved
Figure 54: MSC-CIC-UNKNOWN: Corrective Actions
171 / 533
12.5 [45,4] END-OF-REP-OF-UBLOCK-PROC

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description END-OF-REP-OF-UBLOCK-PROC Communication CommunicationProtocolError Critical (VPMA) The number of unblock requests exceeded a predefined number of allowable attempts (i.e. 255). See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[45,4] ENDOFREP OFUBLOCKPROC
Lock aossc. ACH
Alarm persists?
no
Alarm solved
Figure 55: END-OF-REP-OF-UBLOCK-PROC: Corrective Actions
172 / 533
12.6 [45,251] AUDIT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description AUDIT ProcessingError softwareProgramAbnormallyTerminated Minor (DMA) An SBL which remained in an intermediate maintenance state (AUTO-MSD) following a restart, reload, reboot or a takeover was freed by a maintenance audit. A maintenance audit consists of an autonomous disable followed by an initialize. If the Initialize command fails, the SBL is FLT. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
173 / 533

[45,251] AUDIT
Lock aossc. Achannel
Unlock assoc. Achannel to bring ACH back in service, as faults can exist for other Achannels on Atrunk
Alarm persists?
no
Alarm solved
yes
Onsite
Alarm persists?
no
Alarm solved
174 / 533
13 Class 46: BACKUP-MEDIUM Alarms

This section defines the BSC alarms for the Class 46: BACKUP-MEDIUM alarm class.
175 / 533
13.1 [46,0] SYNC-CORRUPTED

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SYNC-CORRUPTED ProcessingError softwareProgramAbnormallyTerminated Warning (MI) A processor restart has occurred before the twin fiIe is closed during a twin update. The Active CPRA will detect that the twin file was not closed properly before the report. The twin file status is changed to synchronized corrupted and the alarm SYNC_CORR is generated. 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 because the twin file was not properly closed. If the twin file is a PM file, the last performance information can be lost. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

None wait for the next twin file update. See Other BSC Alarms (Section 29.4) for the byte definition.
176 / 533
13.2 [46,1] UNSYNC-OTHER-CORR

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description UNSYNC-OTHER-CORR ProcessingError softwareProgramAbnormallyTerminated Warning (MI) This alarm occurs when the twin file on the own CPRA is not synchronized and a 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 the alarm UNSYN_OTHER_C is generated. 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 is synchronized as fast as possible, although a small delay does exist. If a restart occurs now on the active CPRA (database update was completely done), it is possible that not all the updates are forwarded to the standby. The standby CPRA now becomes active and detects that the data is not yet completely available. The new active CPRA then tries to retrieve the missing data, from its mate. 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 this update is done, although the missing data has still not been retrieved from the mate CPRA. This is necessary; otherwise all the applications are held up until the mate CPRA is running. If the latter has a hard failure, it never becomes 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 data on 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 on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
177 / 533

[46,1] UNSYNC OTHERCORR
Resynchronize OMCR with BSC by performing an audit
Repeat the lost transactions
Alarm persists?
no
Alarm solved
Figure 57: UNSYNC-OTHER-CORR: Corrective Actions Note: When duplex is in operation, the BSC manages synchronization between the two disks. When an update cannot be performed on one disk (for example, due to a processor RESTART), the disks are temporarily unsynchronized. A periodic background task resynchronizes the disks every five minutes. If the synchronization fails because of a hardware failure, the operator is informed by an alarm message.
178 / 533
13.3 [46,4] SECFILE-ROLLBACK

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SEC-FILE-ROLLBACK ProcessingError softwareProgramAbnormallyTerminated Warning (MI) An open transaction was found in the security file during initialization. This means that a transaction requiring several updates of the database was interrupted by a hardware fault, software fault, takeover or a CPRA reload. The BSC performs a rollback of the transaction. The SBL state remains unchanged. Telecom functions are not affected, but Configuration Management is impacted. Configuration Management The interrupted transaction is lost as the BSC returned to its previous state. The OMC-R operator may have received a negative acknowledgement to his request for the modification of a logical parameter/action on software/database replacement. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
179 / 533

[46,4] SECFILE ROLLBACK
NACKs received on operator requests? no
yes
Repeat the operator request
Resynchronize OMCR with BSC by performing an audit
Repeat the lost transactions
Alarm persists?
no
Alarm solved
Figure 58: SECFILE-ROLLBACK: Corrective Actions
180 / 533
13.4 [46,5] SINGLE-UPD-ROLLBACK

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SINGLE-UPD-ROLLBACK ProcessingError softwareProgramAbnormallyTerminated Warning (MI) When a single update fails and security is requested, the application is informed that the update failed and a rollback is done, to retrieve the old/original values. If the rollback cannot be executed, then an alarm single rollback failure 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 Management is impacted. Configuration Management The interrupted transaction is lost as the BSC attempts to return to its previous state. The OMC-R operator may have received a negative acknowledgement to his request for modification of logical parameter/action on software/database replacement. See Consequences of an SBL State Change (Section 30).
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
181 / 533

[46,5] SINGLE UPDROLLBACK
Retrigger the update
Alarm persists?
no
Alarm solved
yes
Run Software/database with old DLS/values
Alarm persists?
no
Alarm solved
Figure 59: SINGLE-UPD-ROLLBACK: Corrective Actions
182 / 533
13.5 [46,6] DUT-ROLLBACK-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description DUT-ROLLBACK-FAIL ProcessingError softwareProgramAbnormallyTerminated Warning (MI) A series of database updates can be done simultaneously with an application and can start a data-update-transaction. By this request, the security system is enabled and all the old/new database values are stored in a security file. This transaction is started and ended by the application. 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 is executed over all the modified data relations. The user is informed about the unsuccessful database updates. If due to some reason, the user cannot be informed about this rollback action, then an alarm DUT_RLB_FAIL is generated. When this failure occurs, the subsequent alarm will be generated when the 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 return to its previous state. The OMC-R operator may have received a negative acknowledgement to his request for modification of logical parameter/action on software/database replacement. See Consequences of an SBL State Change (Section 30).
Impact
Trunk(s)
Cell/ BTS(s) Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
183 / 533

[46,6] DUT ROLLBACKFAIL
Retrigger the data update
Alarm persists?
no
Alarm solved
Figure 60: DUT-ROLLBACK-FAIL: Corrective Actions
184 / 533
13.6 [46,7] DISC-OOS

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description DISC-OOS Equipment InputOutputDeviceError Minor (DMA) During a restart/reload/reboot, the SSD on the standby S-CPRA or O-CPRA was checked and found to be unformatted. Telecom functions are not affected. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
185 / 533

[46,7] DISCOOS
Lock/unlock the disk from OMCR
Alarm solved
no
Alarm persists?
yes
Reformat SSD on SCPRA or OCPRA
Copy all files from active to standby CPRA
no
Alarm occurs often for a specific DISK?
yes
Onsite
Alarm solved Replace suspected CPR
no
Alarm persists?
Figure 61: DISC-OOS: Corrective Actions
186 / 533
13.7 [46,8] DISC-PARITY-ERROR

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description DISC-PARITY-ERROR Equipment InputOutputDeviceError Minor (DMA) During a restart/reload/reboot, the SSD on the standby S-CPRA was checked and a parity error was detected. Telecom functions are not affected. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
187 / 533

[46,8] DISC PARITYERROR
Reformat SSD on SCPRA
Initialize DISK
no
Alarm occurs often for a specific DISK?
yes
Onsite
Alarm solved
Replace suspected CPR
no
Alarm persists?
Figure 62: DISC-PARITY-ERROR: Corrective Actions
188 / 533
14 Class 47: GLOBAL-BSC Alarms

This section defines the BSC alarms for the Class 47: GLOBAL-BSC alarm class.
189 / 533
14.1 [47,1] SCCP-NOT-AVAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SCCP-NOT-AVAIL QualityOfService Congestion Critical (SA) There are insufficient N7 resources due to failures to open a new SCCP 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).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
190 / 533

[47,1] SCCP NOTAVAIL
N7 alarm events?
yes
Solve N7 alarm(s) first
no
N7 parameters OK? yes
no
Correct N7 parameters
Alarm persists?
no
Alarm solved
yes Onsite N7 links operational? yes Onsite Increase N7 resources no Repair/replace N7 equipment
Alarm persists?
no
Alarm solved
Figure 63: SCCP-NOT-AVAIL: Corrective Actions
191 / 533
14.2 [47,2] AUTO-BSC-RESET

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description AUTO-BSC-RESET ProcessingError softwareProgramAbnormallyTerminated Warning (MI) An autonomous reboot/reset of the BSC occurred. The alarm is always sent to both the OMC-R and the local terminal. The SBL state remains unchanged. The impact depends on what has occurred, as described above. See Processor Reset [33,1]. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -

None this information is always sent after an autonomous reboot/reset of the BSC.
192 / 533
14.3 [47,3] AUTO-BSC-RESTART

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description AUTO-BSC-RESTART ProcessingError softwareProgramAbnormallyTerminated Warning (MI) The BSC was successfully restarted from the OMC-R or BSC local terminal. The SBL state remains unchanged. The impact depends on what has occurred, as described above. See processor restart [33,0]. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

None - this information is always sent after an autonomous restart of the BSC.
193 / 533
14.4 [47,4] BSC-SYNC-REQ

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description BSC-SYNC-REQ Communication CommunicationSubsystemFailure Warning (MI) All BSC alarms are stored on one I/O queue. A BSC Sync Request is only 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).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

None on reception of the alarm, the OMC-R starts a BSC alarm audit.
194 / 533
14.5 [47,5] BTS-SYNC-REQ

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description BTS-SYNC-REQ Communication CommunicationSubsystemFailure Warning (MI) All BTS alarms are stored in one I/O queue. A BTS Sync Request is only 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).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

None on reception of the alarm, the OMC-R starts a BTS alarm audit.
195 / 533
14.6 [47,6] AUDIT-COMPLETED

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description AUDIT-COMPLETED ProcessingError softwareProgramAbnormallyTerminated Warning (MI) The BSC was successfully reset or restarted from the OMC-R or BSC local terminal. The SBL state remains unchanged. The impact depends on what has occurred, as described above. See Processor Reset [33,1]. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Call Handling -
O&M; Capabilities
Loss Degradation

None this information is always sent after an successful reset or restart of the BSC.
196 / 533
14.7 [47,7] BSC-HW-RESYNC

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description BSC-HW-RESYNC Equipment Indeterminate Warning (MI) This alarm is generated after BSC extension or reduction. The BSC sends this alarm to the OMC-R. The SBL state remains unchanged. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

None on reception of the alarm, the OMC-R triggers audits to resynchronize with the BSC.
197 / 533
14.8 [47,8] AIFL-FULL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System AIFL-FULL Equipment EquipmentMalfunction Warning (MI) The BSC alarms list is full. The SBL state remains unchanged. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -

[47,8] AIFLFULL
System generates too many alarms in short time period?
no
Solve remaining alarms
Alarm solved
Figure 64: AIFL-FULL: Corrective Actions
198 / 533
14.9 [47,9] CBC-CONNECTION-FAILURE

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description CBC-CONNECTION-FAILURE Equipment EquipmentMalfunction Major (PMA) The alarm is generated when there is a problem with the connection towards the CBC. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
199 / 533

[47,9] CBC CONNECTIONFAILURE
X.25 alarm events?
yes
Solve X.25 alarm(s) first
no
X.25 parameters OK? yes
no
Correct X.25 parameters
Alarm persists?
no
Alarm solved
yes Onsite X.25 links operational? yes no Repair/replace X.25 equipment
Alarm persists?
no
Alarm solved
Figure 65: CBC-CONNECTION-FAILURE: Corrective Actions
200 / 533
14.10 [47,11] ABIS-TS-ALLOC-FAILED

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ABIS-TS-ALLOC-FAILED ProcessingError ConfigurationOrCustomizationError Warning (MI) This alarm is raised to indicate that TS allocation in the case of auto-detection of a TRE has failed. The SBL state remains unchanged. The TRE detected via the Audit will not be operational, no TSs will be allocated. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[47,11] ABISTS ALLOCFAILED
Check multiplexing parameters used by this BTS. If the Abis conveys only Evolium BTS remove Q1 TS if it exists
Alarm persists?
no
Alarm solved
Figure 66: ABIS-TS-ALLOC-FAILED: Corrective Actions
201 / 533
14.11 [47,12] INSUFFICIENT-TCU-RES

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description INSUFFICENT-TCU-RES ProcessingError ConfigurationOrCustomizationError Warning (MI) This alarm is raised to indicate that TCU allocation, in the case of auto-detection of a TRE, has failed due to insufficient TCU resources. The SBL state remains unchanged. The TRE detected via the Audit will not be operational, no TCU will be allocated. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[47,12] INSUFFICIENT TCURES
Check occupancy of the TSU and make place in the TSU using one of the following methods
Trigger a TSU reshuffling
Decrease MaxExtraTSPrimary 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
Alarm cleared?
yes
Alarm solved
Figure 67: INSUFFICIENT-TCU-RES: Corrective Actions
202 / 533
14.12 [47,13] TRE-SECTOR-MISMATCH

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TRE-SECTOR-MISMATCH ProcessingError ConfigurationOrCustomizationError Warning (MI) This alarm is raised in the case of a mismatch in a TRE sector between the sector defined via the Create-TRE command and the sector in which the TRE is equipped, as indicated via the BSC-BTS Audit. The SBL state remains unchanged. The TRE is not operational See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
203 / 533

[47,13] TRESECTORMISMATCH
OR Onsite Remove TRE from incorrect sector via DeleteTRE command
Remove TRE
Onsite Define correct sector via CreateTRE command Equip TRE in correct sector to correspond to defined TRE via CreateTRE command
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes
Figure 68: TRE-SECTOR-MISMATCH: Corrective Actions
204 / 533
14.13 [47,14] TCU TOO FRAGMENTED

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TCU TOO FRAGEMENTED Equipment InputOutputDeviceError Warning (MI) This alarm is raised to indicate that TCU allocation, in the case of auto-detection of a TRE, has failed due to the TCU allocation being too fragmented. The SBL state remains unchanged. The TRE detected via the Audit will not be operational, no TCU will be allocated. A TCU can be allocated if reshuffling is requested. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[47,14] TCU TOO FRAGMENTED
Reshuffle TCUs via Compact RSL/TCU remapping and Manually addon the TRE on BSC
Alarm persists?
no
Alarm solved
Figure 69: TCU-DEFRAGMENTED: Corrective Actions
205 / 533
14.14 [47,15] SWRPL-IN-PROGRESS

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SWRPL-IN-ROGRESS Equipment InputOutputDeviceError Warning (MI) This alarm is raised to indicate that an audit has occurred and that the BSC was informed of equipment addition or removal, but the BSC could not process this information, as the BSC was undergoing software replacement. An audit is triggered when BTS-OM is initialized and the BSC is informed of BTS 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 on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
206 / 533

[47,15] SWRPL INPROGRESS
Wait for new autonomous audit
If no audit is started, trigger new audit
Alarm persists?
no
Alarm solved
Figure 70: SWRPL-IN-PROGRESS: Corrective Actions
207 / 533
14.15 [47,16] MAX-TRE-EXCEEDED

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description MAX-TRE-EXCEEDED Equipment InputOutputDeviceError Warning (MI) This alarm is raised to indicate that an audit has occurred, indicating an addition of TREs when the maximum number of TREs already exists in the BSC. The SBL state remains unchanged. The TREs detected via the audit cannot be auto-allocated as the maximum number of TREs already exists in the BSC. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
208 / 533

[47,16] MAXTRE EXCEEDED
Onsite Remove reported TRE(s)
Alarm persists?
no
Alarm solved
yes
Delete unrequired TRE data. TRE(s) must be not equipped, if autoallocate is set for the Abis
Alarm persists?
no
Alarm solved
Figure 71: MAX-TRE-EXCEEDED: Corrective Actions
209 / 533
210 / 533
15 Class 48: TR-OM Alarms

This section defines the BSC alarms for the Class 48: TROM alarm class.
211 / 533
15.1 [48,0] AUDIT-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description AUDIT-FAIL Equipment Indeterminate Minor (DMA) Due to a failure in the BSC-TSC audit, TR-OM changed from FLT/IT to FLT. TSL is up. When the TR-OM is FLT but the TSL is up, the BSC triggers an audit every two minutes until an audit succeeds. TSL is down - corrective action required. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[48,0] AUDITFAIL
Reset TSC
Alarm persists?
no
Alarm solved
Figure 72: AUDIT-FAIL: Corrective Actions
212 / 533
15.2 [48,1] PROTOCOL-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description PROTOCOL-FAIL Communication CommunicationSubsystemFailure Minor (DMA) 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 NACK to a Request/Report/Ind message from the TSC regardless of the context. This however, cannot occur when there is a loss of LAPD and a protocol error is registered. Impact on System See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

TSL is down only:
[48,1] PROTOCOLFAIL
Reset TSC
Alarm solved
no
Alarm persists?
Figure 73: PROTOCOL-FAIL: Corrective Actions
213 / 533
214 / 533
16 Class 49: ALERTOR Alarms

This section defines the BSC alarms for the Class 49: ALERTOR alarm class.
215 / 533
16.1 [49,0] TRAFF-SDCCH

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOW-TRAFF-SDCCH QualityOfService PerfomanceDegraded Major (PMA) There is abnormally low traffic on SDCCHs in a cell compared with other BSS cells. This alarm inform the operator that there is abnormally low SDCCH traffic in a cell compared with other cells. This is an information message and no system defensive actions are taken.
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
216 / 533

[49,0] TRAFFSDCCH
yes
Solve related BTS alarm(s) first
no
Alarm persists?
no
Alarm solved
yes
Related BSC alarm events?
yes
Solve related BSC alarm(s)
no no
Alarm persists?
Alarm solved
Figure 74: TRAFF-SDCCH: Corrective Actions
217 / 533
16.2 [49,1] CH-INCONSIST-SUSP

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System CH-INCONSIST-SUSP QualityOfService PerfomanceDegraded Major (PMA) There is an inconsistency in the terrestrial channel states. This alarm is generated when the number of seizure failures exceeds a pre-assigned threshold value. The threshold is the maximum number of seizures per circuit that is set by the operator on a BSS basis. This is an information message and no system defensive actions are taken.
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
218 / 533

[49,1] CHINCONSIST SUSP
Byte related alarm events? no
yes
Solve Byte relating alarm(s) first
Related DTC/Trunk/N7 alarm events?
yes Solve that alarm(s)
no yes Alarm persists? no Alarm solved
Figure 75: CH-INCONSIST-SUSP: Corrective Actions
219 / 533
16.3 [49,2] TCH-BLOCK-SUSPECT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TCH-BLOCK-SUSPECT QualityOfService PerfomanceDegraded Major (PMA) Traffic channel behavior is abnormal and calls remain on the channels for an extended length of time. It is suspected that the traffic channels are blocked. This alarm is generated when the call duration for all traffic channels in a cell exceeds a pre-assigned threshold value (1...255 minutes). The threshold is set by the operator on a BSS basis. This is an information message and no system defensive actions are taken.
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[49,2] TCHBLOCK SUSPECT
TCH related hardware problems?
yes
Solve TCH related hardware problems
no Contact System Support yes Alarm persists? no Alarm solved
Figure 76: TCH-BLOCK-SUSPECT: Corrective Actions
220 / 533
16.4 [49,3] TCH-OCCUP-SHORT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System TCH-OCCUP-SHORT QualityOfService PerfomanceDegraded Major (PMA) The average traffic channel seizure time is considered to be too short. This alarm informs the operator that there has been abnormally short traffic duration on a traffic channel. This is an information message and no system defensive actions are taken.
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[49,3] TCHOCCUP SHORT
TCH related hardware problems?
yes
Solve TCH related hardware problemst
no Contact System Support yes Alarm persists? no Alarm solved
Figure 77: TCH-OCCUP-SHORT: Corrective Actions
221 / 533
222 / 533
17 Class 50: BSC-EXTERNAL Alarms

This section defines the BSC alarms for the Class 50: BSC-EXTERNAL alarm class.
223 / 533
17.1 [50,1] EXT-ALARM-1

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description EXT-ALARM-1 Equipment Indeterminate CUSTOMER DEPENDENT A probable cause and category is provided in a customer-dependent table residing in the OMC-R. This probable cause should accurately and informatively describe the external alarm. The SBL state remains unchanged. No system impact. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
224 / 533

[50,1] EXTALARM1
Onsite
Alarm was sent without cause? no
yes
Check sensor connection to BSC. Reconnect sensor if required.
Onsite
Trigger customer specific action according to reported alarm (e.g. call fire brigade)
Check cabling to sensor, replace cabling if required.
Onsite
Check sensor function, replace sensor if required.
External alarm persists? yes Contact System Support
no
Alarm solved
Figure 78: EXT-ALARM-1: Corrective Actions
225 / 533
17.2 [50,2] EXT-ALARM-2

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description EXT-ALARM-2 Equipment Indeterminate CUSTOMER DEPENDENT A probable cause and category is provided in a customer-dependent table residing in the OMC-R. The OMC-R table describes the external alarm. The SBL state remains unchanged. No system impact. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
226 / 533

[50,2] EXTALARM2
Onsite
yes
Onsite
Trigger customerspecific action according to reported alarm (e.g. call fire brigade)
Onsite
External alarm persists? yes
no
Alarm solved
227 / 533
17.3 [50,3] EXT-ALARM-3

Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
228 / 533

[50,3] EXTALARM3
Onsite
yes
Onsite
Onsite
External alarm persists? yes
no
Alarm solved
229 / 533
17.4 [50,4] EXT-ALARM-4

Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
230 / 533

[50,4] EXTALARM4
Onsite
yes
Onsite
Onsite
no
Alarm solved
231 / 533
17.5 [50,5] EXT-ALARM-5

Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
232 / 533

[50,5] EXTALARM5
Onsite
Alarm was sent without cause?
yes
no
Onsite
Onsite
no
Alarm solved
233 / 533
17.6 [50,6] EXT-ALARM-6

Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
234 / 533

[50,6] EXTALARM6
Onsite
yes
no
Onsite
Onsite
no
Alarm solved
235 / 533
17.7 [50,7] EXT-ALARM-7

Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
236 / 533

[50,7] EXTALARM7
Onsite
yes
no
Onsite
Onsite
no
Alarm solved
237 / 533
17.8 [50,8] EXT-ALARM-8

Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
238 / 533

[50,8] EXTALARM8
Onsite
yes
Onsite
Onsite
no
Alarm solved
239 / 533
17.9 [50,9] EXT-ALARM-9

Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
240 / 533

[50,9] EXTALARM9
Onsite
yes
Onsite
Onsite
no
Alarm solved
241 / 533
17.10 [50,10] EXT-ALARM-10

Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
242 / 533

[50,10] EXTALARM10
Onsite
yes
Onsite
Onsite
no
Alarm solved
243 / 533
244 / 533
18 Class 51: SWITCH-G2 Alarms

This section defines the BSC alarms for the Class 51: SWITCH-G2 alarm class.
245 / 533
18.1 [51,0] TRANSIENT-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System TRANSIENT-FAIL Equipment EquipmentMalfunction Warning (MI) The switch detected a momentary fault. The SBL state remains unchanged. The switch element remains IT/FIT. Some interference is likely on current calls through the switch. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[51,0] TRANSIENTFAIL
SWITCH FAIL alarm events? no
yes
Solve SWITCHFAIL alarm(s)
Alarm persists?
no
Alarm solved
yes
Figure 88: TRANSIENT-FAIL: Corrective Actions
246 / 533
18.2 [51,1] SWITCH-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SWITCH-FAIL Equipment EquipmentMalfunction Major (PMA) The switch element is isolated from the operational software due to a persistent fault. If an alarm is internally present on a link, the switch connected to the link is updated to FIT. If the number of faulty links on the switch is >= (number of links present on the switch -1) /2, the switch is updated to FOS. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
247 / 533
18.2.1 Corrective Actions for Write Violation Overflow, Loss of Sync Overflow and Init Fail Alarms
For Write Violation Overflow, Loss of Sync Overflow and Init Fail alarms:
[51,1] SWITCHFAIL
Onsite Check cabling to switch, replace cabling if required.
Two alarms are generated for a link, one alarm for each affected switch.
Lock faulty SWITCH
Unlock faulty SWITCH
Alarm persists?
no
Alarm solved
Figure 89: SWITCH-FAIL: Corrective Actions for Write Violation Overflow, Loss of Sync Overflow and Init Fail Alarms
248 / 533
18.2.2 Corrective Actions for Loss of Sync Alarm

For Loss of Sync alarms:
[51,1] SWITCHFAIL
Last clock generator/repeater operational? yes
no
Replace/repair clock generator/repeater
Last clock extractor operational? yes
no
Replace/repair clock extractor
MSC/trunk provides clock pulse to BSC? yes Onsite Check cabling to switch, replace cabling if required.
no
Trigger repar action at MSC side
Lock faulty SWITCH
Unlock faulty SWITCH
Alarm persists?
no
Alarm solved
Figure 90: SWITCH-FAIL: Corrective Actions for Loss of Sync Alarm
249 / 533
18.2.3 Corrective Actions for HW Fault Alarm

For HW Fault alarms:
[51,1] SWITCHFAIL
Onsite Check links to faulty switch, replace cabling if required.
Switch operational?
yes
Alarm solved
no
Onsite
Replace reported faulty switch
Alarm persists?
no
Alarm solved
Figure 91: SWITCH-FAIL: Corrective Actions for HW Fault Alarm
250 / 533
18.3 [51,2] ROUTINE-TEST-REP

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ROUTINE-TEST-REP Equipment EquipmentMalfunction Warning (MI) A network switch link failure was detected during a routine network tunnel test. The link remains available to the operational software. The SBL state remains unchanged. The switch is still able to carry traffic. However no operator actions can be 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 test executed, all Test-raw-data is filled in. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
251 / 533

[51,2] ROUTINE TESTREP
Onsite
Replace suspected switch
Onsite
Switch hardware OK?
no
Repair/ replace hardware
yes
Onsite
Switch cabling OK?
no
Repair/ replace hardware
yes Contact System Support Alarm persists? no Alarm solved
Figure 92: ROUTINE-TEST-REP: Corrective Actions
252 / 533
19 Class 52: BSC-Clock Alarms

This section defines the BSC alarms for the Class 52: BSCClock alarm class.
253 / 533
19.1 [52,0] LOSS-OF-SEL-CLK-INP

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOSS-OF-SEL-CLK-INP Equipment TimingProblem Major (PMA) - in commercial use, Warning (MI) - out of commercial use The CLK-GEN detects that all external references have failed. In addition, the local clock has also failed. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
254 / 533

[52,0] LOSSOF SELCLKINP
Ater alarm events?
yes
Solve Ater alarm(s) first
no
DTC alarm events?
yes
Solve DTC alarm(s)
no
no
Alarm persists?
yes
Onsite
Alarm solved
Replace Ater trunk extracted by the 3 DTCs
no
Alarm persists?
Figure 93: LOSS-OF-SEL-CLK-INP: Corrective Actions
255 / 533
19.2 [52,1] LOSS-OF-CLK-GEN-FN

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOSS-OF-CLK-GEN-FN Equipment TimingProblem Major (PMA) - in commercial use, Warning (MI) - out of commercial use 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).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
256 / 533

[52,1] LOSSOF CLKGENFN
Onsite
Replace suspected Clock RIT
Alarm persists?
no
Alarm solved
yes
Figure 94: LOSS-OF-CLK-GEN-FN: Corrective Actions
257 / 533
19.3 [52,2] SWITCH-TO-LOCAL-CLK

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SWITCH-TO-LOCAL-CLK Equipment TimingProblem Minor (DMA) Due to loss of all external clocks, the CLK-GEN has selected a local clock. If only one CLK-GEN has detected this situation, there is no impact on the clock distributed throughout the BSC as the SYS-BCLA will select the 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).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
258 / 533

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. See suspected RITs information for DTCs which extract the clock signal for this CLK_GEN.
[52,2] SWITCH TOLOCALCLK
DTC/ Ater alarm events? no
yes
Solve DTC/Ater alarm(s) first
yes
Solve transmission alarm(s)
no
Trigger clock source checks at MSC side
Alarm persists?
no
Alarm solved
Figure 95: SWITCH-TO-LOCAL-CLK: Corrective Actions
259 / 533
19.4 [52,3] LOSS-OF-SYSTEM-CLOCK-A

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System LOSS-OF-SYSTEM-CLK-A Equipment TimingProblem Minor (DMA) - in commercial use, Warning (MI) - out of commercial use The System Clock A failure is detected by CLK-REP. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[52,3] LOSSOF SYSTEMCLOCKA
Onsite
Replace suspected System Clock A
The rack number is indicated by the CLKREP SBL number
Alarm persists?
no
Alarm solved
Figure 96: LOSS-OF-SYSTEM-CLOCK-A: Corrective Actions
260 / 533
19.5 [52,4] LOSS-OF-SYSTEM-CLOCK-B

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System LOSS-OF-SYSTEM-CLK-B Equipment TimingProblem Minor (DMA) - in commercial use, Warning (MI) - out of commercial use A System Clock B failure is detected by CLK-REP. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[52,4] LOSSOF SYSTEMCLOCKB
Onsite
Replace suspected System Clock B
The rack number is indicated by the CLKREP SBL number
Alarm persists?
no
Alarm solved
Figure 97: LOSS-OF-SYSTEM-CLOCK-B: Corrective Actions
261 / 533
19.6 [52,5] LOSS-OF-CLK-DISTR-FN

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOSS-OF-CLK-DISTR-FN Equipment TimingProblem Major (PMA) - in commercial use, Warning (MI) - out of commercial use 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)
Call Handling -
O&M; Capabilities
Loss Degradation
262 / 533

[52,5] LOSSOF CLKDISTRFN
Onsite
Replace suspected Clock repeater
The rack number is indicated by CLKREP SBL number.
Alarm solved
no
Alarm persists?
yes
Figure 98: LOSS-OF-CLK-DISTR-FN: Corrective Actions
263 / 533
19.7 [52,6] BSC-RUN-ON-LOCAL-CLK

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System BSC-RUN-ON-LOCAL-CLK Equipment TimingProblem Major (PMA) This alarm is generated when the BSC is running on the local clock. The BTS cannot function correctly if using the local BSC clock. Depending on the difference between the local clock and the clock used on the remaining Ater links, the impact can be small (degradation, only retransmissions, alarms Slip-un-run, Slip-ov-run, various synchro alarms) or can be very important (loss) preventing stable calls.
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities -
264 / 533

It is strongly recommended to refit the CLK-REP, extracting the Ater clock by the DTC from 2 Mbit trunks (three are available per CLK-GEN) as indicated by the Friendly Name on the OMC-R or Suspect RIT on the LMT.
[52,6] BSCRUN ONLOCALCLK
DTC/Ater alarm events? no
yes
Solve DTC/Ater alarm(s) first
yes
Solve transmission alarm(s)
no
Trigger clock source checks at MSC side
Alarm solved
no
Alarm persists?
yes
Figure 99: BSC-RUN-ON-LOCAL-CLK: Corrective Actions
265 / 533
19.8 [52,7] LOC-CLK-FAILURE

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System LOC-CLK-FAILURE Equipment TimingProblem Major (PMA) Due to detection of the Local Clock Failure the CLK-GEN is degraded. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[52,7] LOC CLKFAILURE
Onsite
Replace suspected Clock RIT
Alarm solved
no
Alarm persists?
Figure 100: LOC-CLK-FAILURE: Corrective Actions
266 / 533
20 Class 53: Broadcast-Bus Alarms

This section defines the BSC alarms for the Class 53: BroadcastBus alarm class.
267 / 533
20.1 [53,0] LOSS-OF-ONE-BROAD-BUS-BSC

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System LOSS-OF-ONE-BROAD-BUS-BSC Equipment EquipmentMalfunction Major (PMA) - in commercial use, Warning (MI) - out of commercial use The BSC has detected loss of one BC bus in the BSC. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[53,0] LOSSOFONE BROADBUSBSC
Onsite
The Broadcast Bus is indicated by the BCSYSBUS SBL number.
Alarm solved
no
Alarm persists?
Figure 101: LOSS-OF-ONE-BROAD-BUS-BSC: Corrective Actions
268 / 533
20.2 [53,1] LOSS-OF-BOTH-BROAD-BUS-BSC

specificProblems: eventType: probableCause: perceivedSeverity: LOSS-OF-BOTH-BROAD-BUS-BSC Equipment TimingProblem Critical (VPMA) - in commercial use, Warning (MI) - out of commercial use The BSC has detected loss of both broadcast buses in the BSC. There are significant telecom impacts: LAC paging mode is not working anymore, thus preventing Mobile terminating calls. GPRS reset procedure does not work anymore and leads to loss of GPRS traffic. For the consequences of an SBL state change, see Consequences of an SBL State Change (Section 30).
Alarm Description Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[53,1] LOSSOFBOTH BROADBUSBSC
Onsite
G2: Replace both BCLASYS boards
Alarm solved
no
Alarm persists?
Figure 102: LOSS-OF-BOTH-BROAD-BUS-BSC: Corrective Actions
269 / 533
20.3 [53,2] DMA-PROBLEM

20.3.1 [53,2] DMA-PROBLEM (BSC)
specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description DMA-PROBLEM Communication CommunicationSubsystemFailure Major (PMA) The BSC has detected DMA problems in a high percentage of CEs in the BSC. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

Contact your Alcatel system support.
270 / 533
20.3.2 [53,2] DMA-PROBLEM (CPR/DTC/TCU)

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System DMA-PROBLEM Communication CommunicationSubsystemFailure Minor (DMA) The BSC has detected a high number of DMA problems in the CE. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[53,2] DMAPROBLEM (CPR/DTC/TCU)
DMAPROBLEM (BSC) alarm events?
yes
no
Onsite
Replace suspected CPR/DTC/TCU
Alarm solved
no
Alarm persists?
yes
Figure 103: DMA-PROBLEM (CPR/DTC/TCU): Corrective Actions
271 / 533
20.4 [53,3] LOSS-OF-ONE-BROAD-BUS-RACK

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System LOSS-OF-ONE-BROAD-BUS-RACK Equipment LanError Major (PMA) - in commercial use, Warning (MI) - out of commercial use The BSC has detected a loss of one broadcast bus on a RACK. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[53,3] LOSSOFONE BROADBUSRACK
Onsite
The Broadcast Bus is indicated by the BC_RACK_BUS SBL number.
Alarm solved
no
Alarm persists?
yes
Figure 104: LOSS-OF-ONE-BROAD-BUS-RACK: Corrective Actions
272 / 533
20.5 [53,4] LOSS-OF-BOTH-BROAD-BUS-RACK

specificProblems: eventType: probableCause: perceivedSeverity: LOSS-OF-BOTH-BROAD-BUS-RACK Equipment TimingProblem Critical (VPMA) - in commercial use, Warning (MI) - out of commercial use The BSC has detected loss of both broadcast buses on a RACK. There are significant telecom impacts: LAC paging mode is not working anymore, thus preventing Mobile terminating calls. GPRS reset procedure does not work anymore and leads to loss of GPRS traffic. For the consequences of an SBL state change, see Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[53,4] LOSSOFBOTH BROADBUSRACK
Onsite
G2: Replace both BCLA boards
Alarm solved
no
Alarm persists?
yes
Figure 105: LOSS-OF-BOTH-BROAD-BUS-RACK: Corrective Actions
273 / 533
20.6 [53,5] DEGRAD-BROAD-BUS-RACK

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description DEGRAD-BROAD-BUS-RACK Equipment LanError Minor (DMA) The BSC has detected a degradation in the quality of one of the broadcast buses on a RACK. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[53,5] DEGRAD BROADBUSRACK
Onsite
Alarm solved
no
Alarm persists?
yes
Figure 106: DEGRAD-BROAD-BUS-RACK: Corrective Actions
274 / 533
20.7 [53,6] LOSS-OF-ONE-BROAD-BUS-CE

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System LOSS-OF-ONE-BROAD-BUS-CE Equipment LanError Minor (DMA) - in commercial use, Warning (MI) - out of commercial use The BSC has detected loss of one broadcast bus to a CE. No redundancy on broadcast bus. For the consequences of an SBL state change, see Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

broadcase board and the concerned CE board.
Figure 107: LOSS-OF-ONE-BROAD-BUS-CE: Corrective Actions
275 / 533
20.8 [53,7] LOSS-OF-BOTH-BROAD-BUS-CE

specificProblems: eventType: probableCause: perceivedSeverity: LOSS-OF-BOTH-BROAD-BUS-CE Equipment TimingProblem Critical (VPMA) - in commercial use, Warning (MI) - out of commercial use The BSC has detected loss of both broadcast buses to a CE. There are significant telecom impacts: LAC paging mode is not working anymore, thus preventing Mobile terminating calls. GPRS reset procedure does not work anymore and leads to loss of GPRS traffic. For the consequences of an SBL state change, see Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[53,7] LOSSOFBOTH BROADBUSCE
Onsite
Alarm solved
no
Alarm persists?
Figure 108: LOSS-OF-BOTH-BROAD-BUS-CE: Corrective Actions
276 / 533
20.9 [53,8] DEGRAD-BROAD-BUS-CE

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description DEGRAD-BROAD-BUS-CE Equipment LanError Minor (DMA) The BSC has detected a degradation in the quality of one of the broadcast buses to a CE. Some broadcasted messages may be lost for this CE, for example, some paging messages can be lost . For the consequences of an SBL state change, see Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[53,8] DEGRAD BROADBUSCE
DEGRAD BROADBUS RACK alarm events?
yes
no
Onsite
G2: Replace suspected broadcast bus RIT
Alarm solved
no
Alarm persists?
yes
Figure 109: DEGRAD-BROAD-BUS-CE: Corrective Actions
277 / 533
278 / 533
21 Class 54: BTS-EXTRA-TS-POOL Alarms

This section defines the BTS pool alarms for the Class 54: BTS-POOL alarm class.
279 / 533
21.1 [54,1] EXTRA TS NOT FULLY USABLE

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description EXTRA ABIS TIME SLOT NOT FULLY USABLE QualityOfService TCU or the second Abis link failure Minor (DMA) In case of TCU failure/end failure, 2nd Abis failure/end failure or BTS config-complete, the alarm is evaluated. This alarm is on BTS level, linked to a new SBL BTS-POOL per BTS. The new added SBL, BTS-POOL, is always IT and not involved in SBL-state-audit, Furthermore, no operation on the SBL is allowed. The new added SBL does not impact MAINT/ALARM modules. In OMC side, after HW audit, if the BTS is type of Evolium, OMC creates BTS-POOL for that BTS. And OMC will clear the alarm in case of alarm audit or receiving END alarm.
Impact on System
Trunk(s) -
Call Handling -
O&M; Capabilities -
280 / 533
Figure 110: EXTRA TS NOT FULLY USABLE: Corrective Actions
281 / 533
282 / 533
22 Class 66: TSC-TRUNK Alarms

This section defines the TC alarms for the Class 66: TSCTRUNK alarm class.
283 / 533
22.1 [66,21] LOOP-TO-ITF

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOOP-TO-ITF Equipment EquipmentUnderTest Major (PMA) An external loop is activated. A loop cannot be activated/deactivated using the OMC-R. See Consequences of an SBL State Change (Section 30).
Impact On System
Impact ABIS-HWAY-TP Loss Degradation
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
SBL A-PCM-TP and SBL ATER-HWAY-TP Impact Loss Degradation Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities

[66,21] LOOPTOITF
Remove the loopback settings, though normal conditions return after a preset control timeout.
Alarm solved
no
Alarm persists?
Figure 111: LOOP-TO-ITF: Corrective Actions
284 / 533
22.2 [66,22] LOOP-TO-EQUIP

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOOP-TO-EQUIP Equipment EquipmentUnderTest Major (PMA) An external loop is activated. A loop cannot be activated/deactivated using the OMC-R. See Consequences of an SBL State Change (Section 30).
Impact On System
Trunk(s)
Call Handling
O&M; Capabilities
SBL A-PCM-TP and SBL ATER-HWAY-TP Impact Loss Degradation Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities -

[66,22] LOOPTOEQUIP
Remove the loopback settings, though normal conditions return after a preset control timeout.
Alarm solved
no
Alarm persists?
Figure 112: LOOP-TO-EQUIP: Corrective Actions
285 / 533
22.3 [66,50] TWO-MB-MISSING

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TWO-MB-MISSING Communication LossOfSignal Major (PMA) Loss of an incoming 2M signal. The loss of the incoming digital signal at 2048 kbit/s is considered as loss of an incoming 2M signal. See Consequences of an SBL State Change (Section 30).
Impact On System
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 -
286 / 533

[66,50] TWOMB MISSING
2M linkrelated alarm events? yes Solve that alarm(s) first
no
ABIS/ APCM/ATER alarm events? yes
no
Related receiver alarm events? no
Solve that alarm(s)
yes
Alarm persists?
no
no
Receiver operational?
yes
Onsite Repair/replace Receiver no Local trunk cabling OK? yes Trigger remote signal path and transmitter tests on MSC side
Alarm persists?
no
Alarm solved
Figure 113: TWO-MB-MISSING: Corrective Actions
287 / 533
22.4 [66,66] AIS-2-MB

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact On System AIS-2-MB Communication LocalNodeTransmissionError Minor (DMA) The 2 Mbit/s interface is receiving an AIS signal all ones indication. 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 -
288 / 533

[66,66] AIS2MB
ABIS/ APCM/ATER alarm events?
no
Loop activated?
yes Remove loop
no
Alarm persists?
no
Alarm solved
yes
Trigger remote signal path and transmitter tests on MSC side
Alarm persists?
no
Alarm solved
Figure 114: AIS-2-MB: Corrective Actions
289 / 533
22.5 [66,81] FRAME-ALIGNMENT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description FRAME-ALIGNMENT Communication LossOfFrame Major (PMA) The 2 Mbit/s signal frame alignment is lost. Traffic is not possible. TS 0 is reserved for frame alignment, alarms and network synchronization information and should not be used for Signaling or speech purposes. The frame alignment signal is monitored to determine if the frame alignment has been lost. The frame alignment will be assumed to have been lost when three consecutive incorrect frame alignment signals have been received. See Consequences of an SBL State Change (Section 30).
Impact On System
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
290 / 533

[66,81] FRAME ALIGNMENT
ABIS/ APCM/ATER alarm events? no
Correct timeslot 0 settings
no
Timeslot 0 settings OK?
yes yes Trigger remote signal path and transmitter tests on MSC side
Alarm persists?
no no
Alarm solved
Alarm persists?
Figure 115: FRAME-ALIGNMENT: Corrective Actions
291 / 533
22.6 [66,86] CRC-MFRAME-ALIGNMENT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description CRC-MFRAME-ALIGNMENT Communication LossOfFrame Major (PMA) Expected patterns not received on TS0 of the PCM (CRC multiframe). The CRC is not used in the remote end or there may be interferences on the connection. See Consequences of an SBL State Change (Section 30).
Impact On System
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
292 / 533

[66,86] CRCMFRAME ALIGNMENT
Correct timeslot 0 CRC settings
no
Timeslot 0 CRC settings OK?
yes
Alarm persists?
yes
Trigger tests of remote CRC activation on MSC side
no
Alarm solved
no
Alarm persists?
yes
Figure 116: CRC-MFRAME-ALIGNMENT: Corrective Actions
293 / 533
22.7 [66,99] BER-10E-3

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description BER-10E-3 Communication DegradedSignal Major (PMA) Signal input BER worse than 1 in 1000. The error rate of the incoming main system signal is worse than the preset threshold value of 10E-3. See Consequences of an SBL State Change (Section 30).
Impact On System
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
294 / 533

[66,99] BER10E3
Linkrelated alarm events?
no
yes ABIS/ APCM/ATER alarm events? yes no
Solve that alarm(s)
yes
Alarm persists?
no
no
yes
Alarm persists?
no
Alarm solved
Figure 117: BER-10E-3: Corrective Actions
295 / 533
22.8 [66,100] BER-10E-4

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description BER-10E-4 Communication DegradedSignal Minor (DMA) Signal input BER worse than 1 in a 10000. The error rate of the incoming main system signal is worse than the preset threshold value of 10E-4. See Consequences of an SBL State Change (Section 30).
Impact On System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
296 / 533

[66,100] BER10E4
no
yes
no
yes
Solve that alarm(s)
yes
Alarm persists?
no
no
yes
Alarm persists?
no
Alarm solved
297 / 533
22.9 [66,102] BER-10E-6

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description BER-10E-6 Communication DegradedSignal Minor (DMA) Signal input BER worse than 1 in a million. The error rate of the incoming main system signal is worse than the preset threshold value of 10E-6. See Consequences of an SBL State Change (Section 30).
Impact On System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
298 / 533

[66,102] BER10E6
no
yes
no
Solve that alarm(s) first yes Related receiver alarm events? no yes Solve that alarm(s)
Solve that alarm(s)
yes
Alarm persists?
no
no
yes
Onsite Repair/replace Receiver no Local trunk cabling OK? yes
Alarm persists?
no
Alarm solved
299 / 533
22.10 [66,176] FAR-END-ALARM

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description FAR-END-ALARM Communication LocalNodeTransmissionError Minor (DMA) The equipment at the remote end has acknowledged the faulty condition of the interface signal. Alarm indication from the remote end is detected when bit 3 of channel TS 0 changes state from 0 to 1 in those frames not containing the frame alignment signal. See Consequences of an SBL State Change (Section 30).
Impact On System
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
300 / 533

[66,176] FAREND ALARM
no
yes
Related Solve that alarm(s) receiver alarm events?
no
Alarm persists?
no
Alarm solved
Figure 120: FAR-END-ALARM: Corrective Actions
301 / 533
22.11 [66,208] I1I2-AIS

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description I1I2-AIS Communication LocalNodeTransmissionError Minor (DMA) An AIS was received on the time slot carrying tributary information on the Ater Mux Interface. The AIS condition is detected on the TS which carries the tributary information on the Ater Mux interface. If transparent AIS is not detected on TS 0, then the alarm octet is checked to see if an I1I2_AIS alarm has occurred as redundant AIS. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling
O&M; Capabilities -
302 / 533

[66,208] I1L2AIS
Loop is activated?
no
yes
Ater alarm events?
Remove loop no
Alarm persists?
no
Alarm solved
Figure 121: I1I2-AIS: Corrective Actions
303 / 533
22.12 [66,210] TRANS-FLT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TRANS-FLT Equipment EquipmentMalfunction Warning (MI) The PCM event counter threshold value is exceeded, which results in the generation of this 2 Mbit/s interface alarm. For each PCM event, a counter is increased. At certain intervals, the counter will be decreased by 1. When the threshold value is exceeded, this alarm is generated for the 2 Mbit/s interface. See Consequences of an SBL State Change (Section 30).
Impact On System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
304 / 533

[66,210] TRANSFLT
no
yes
no
yes
Solve that alarm(s)
yes
Alarm persists?
no
no
yes
Alarm persists?
no
Alarm solved
Figure 122: TRANS-FLT: Corrective Actions
305 / 533
22.13 [66,211] LOSS-OF-CLOCK-2M

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOSS-OF-CLOCK-2M Equipment TimingProblem Minor (DMA) - in commercial use, Warning (MI) - out of commercial use The 2 MHz clock source is lost. Once the PAD detects the loss of the 2 MHz clock source, the next clock source will be selected if available. The firmware will detect the missing clock source number. See Consequences of an SBL State Change (Section 30).
Impact On System
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling
O&M; Capabilities -
306 / 533

[66,211] LOSSOF CLOCK2M
no
yes
ABIS/ APCM/ATER alarm events? yes
no
Solve that alarm(s)
Onsite
yes
Alarm persists?
no
no
yes
Repair/replace Receiver
no
Local trunk cabling OK? yes
Alarm persists?
no
Alarm solved
Figure 123: LOSS-OF-CLOCK-2M: Corrective Actions
307 / 533
308 / 533
23 Class 67: TSC-CHANNEL Alarms

This section defines the TC alarms for the Class 67: TSCCHANNEL alarm class.
309 / 533

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOOP-TO-EQUIP Equipment EquipmentUnderTest Major (PMA) 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).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling
O&M; Capabilities -

[67,22] LOOP TOEQUIP
Remove loop
Alarm persists?
no
Alarm solved
310 / 533
23.2 [67,65] AIS-64-KB

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description AIS-64-KB Communication LocalNodeTransmissionError Minor (DMA) 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).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling
O&M; Capabilities -
311 / 533

[67,65] AIS64KB
TC16 alarm events?
no
yes
Solve that alarm(s)
yes
Alarm persists?
no
no
yes
Onsite Repair/replace Receiver no Local Ater cabling OK? yes Trigger remote signal path and transmitter tests on MSC side
Alarm persists?
no
Alarm solved
Figure 125: AIS-64-KB: Corrective Actions
312 / 533
23.3 [67,72] AIS-16-KB

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description AIS-16-KB Communication LocalNodeTransmissionError Minor (DMA) 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).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling
O&M; Capabilities -
313 / 533

[67,72] AIS16KB
TC16 alarm events?
no
yes
Solve that alarm(s)
yes
Alarm persists?
no
no
yes
Onsite Repair/replace Receiver no Local Ater cabling OK? yes
Alarm persists?
no
Alarm solved
Figure 126: AIS-16-KB: Corrective Actions
314 / 533
23.4 [67,122] TRAU-SYNCHRO

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TRAU-SYNCHRO Equipment TimingProblem Minor (DMA) This is an internal BSC alarm. The TRAU cannot synchronize to the BTS. The speech path is broken between the TRE and the Transcoder. This only occurs during call handling. Impact On System See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling
O&M; Capabilities -
315 / 533

[67,122] TRAU SYNCHRO
BTS/BSCAdapt alarm events?
no
yes
Abis alarm events? yes
Solve that alarm(s)
Solve that alarm(s) no TCU/ SWITCH/DTC alarm events? yes no no
Solve that alarm(s)
Alarm persists?
Alarm solved
Figure 127: TRAU-SYNCHRO: Corrective Actions
316 / 533
23.5 [67,128] EQUIPMENT-FAULT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact On System EQUIPMENT-FAULT Equipment EquipmentMalfunction Major (PMA) An internal fault has been detected on a board. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling
O&M; Capabilities -
317 / 533

[67,131] INTBUSFAULT
G2 TC
A925 TC
Lock TC16
Lock MT120
Unlock TC16
Unlock MT120
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes
Onsite Onsite
yes
Replace DT16/TC16
Replace MT120
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes
Figure 128: EQUIPMENT-FAULT: Corrective Actions
318 / 533
23.6 [67,130] MEMORY-FAULT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact On System MEMORY-FAULT ProcessingError CorruptData Major (PMA) An EEPROM memory write access has been unsuccessful. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling
O&M; Capabilities -
319 / 533

[67,130] MEMORY FAULT
Analyze alarm number
DT16/TC16 alarm events? no
yes
Solve that alarm(s)
Lock TC16
Unlock TC16
Alarm persists?
no
Alarm solved
yes
Onsite
Replace DT16/TC16
Alarm persists?
no
Alarm solved
Figure 129: MEMORY-FAULT: Corrective Actions
320 / 533
23.7 [67,131] INT-BUS-FAULT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact On System INT-BUS-FAULT ProcessingError CorruptData Major (PMA) An internal fault has been detected on board. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling
O&M; Capabilities -
321 / 533

[67,131] INTBUSFAULT
Lock TC16
Unlock TC16
Alarm persists?
no
Alarm solved
yes
Onsite
Replace DT16/TC16
Alarm persists?
no
Alarm solved
Figure 130: INT-BUS-FAULT: Corrective Actions
322 / 533
24 Class 70: TSC-SW-ANOMALY

This section defines the TC alarms for the Class 70: TSCSWANOMALY alarm class.
323 / 533
24.1 [70,219] SW-FAULT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact On System SW-FAULT ProcessingError ApplicationSubsystemFailure Warning (MI) The software which runs on the TSCA board detects an error. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
324 / 533

[70,219] SW FAULT
Lock TSC
Unlock TSC
Alarm persists?
no
yes
Onsite
Press TSC reset button
Onsite
Disengage & replugg TSC
Onsite
Replace TSC
Alarm persists?
no
Alarm solved
Figure 131: SW-FAULT: Corrective Actions
325 / 533
326 / 533
25 Class 71: TSC-ENVIRON

This section defines the TC alarms for the Class 71: TSCENVIRON alarm class.
327 / 533
25.1 [71,0] POWER-SUPPLY

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description POWER-SUPPLY Equipment PowerProblem Major (PMA) An operating voltage is missing or out of range. All or some of the functions on the reporting board are not working. If the power supply fails and the CPU on any board is not working, the power supply alarm may not be sent. See Consequences of an SBL State Change (Section 30).
Impact On System
Impact BTS-ADAPT = FIT Loss Degradation
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
BTS-ADAPT = FLT Impact Loss Degradation SM-ADAPT = FIT Impact Loss Degradation SM-ADAPT = FLT Impact Loss Degradation TC-ADAPT = FLT Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
328 / 533
Trunk(s)
Cell/ BTS(s) -
Signaling (N7) -
Call Handling
O&M; Capabilities -

[71,0] POWER SUPPLY
DC/DC converter alarm events? no
yes
Solve that alarm(s)
Other alarm on RIT events? no
yes
Solve that alarm(s)
Alarm persists?
no
Alarm solved
yes
Onsite Onsite
Input voltage on suspected RIT OK yes
no
Check supply cabling, connectors, fuses
Onsite
Replace suspected TSS RIT
Alarm persists?
no
Alarm solved
Figure 132: POWER-SUPPLY: Corrective Actions
329 / 533
330 / 533
26 Class 73:BSC-ADAPT
This section defines the TC alarms for the Class 73: BSCADAPT alarm class.
331 / 533

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOOP-TO-EQUIP Equipment Indeterminate Major (PMA) A loop is activated on one of the eight BSC interfaces. A loop cannot be activated/deactivated using the OMC-R. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities -

Remove loopback setting
When a loop is activated, it deactivates after a preset control timeout.
Alarm persists?
no
Alarm solved
332 / 533

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description EQUIPMENT-FAULT Equipment Indeterminate Major (PMA) There is a basic operational malfunction. An internal fault has been detected on board. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
333 / 533

[73,128] EQUIPMENT FAULT
Lock BSCADAPT
Unlock BSCADAPT
BIUA alarm events? no
yes
Solve that alarm(s)
Alarm persists?
no
Alarm solved
yes
Onsite
Replace BIUA
Alarm persists?
no
Alarm solved
334 / 533

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System MEMORY-FAULT Equipment Indeterminate Major (PMA) An EEPROM memory write access has been unsuccessful. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s)
Signaling
335 / 533

BIU alarm events? no
yes
Solve that alarm(s)
Lock BSCADAPT
Unlock BSCADAPT
Alarm persists?
no
Alarm solved
yes
Onsite
Replace BIU
Alarm persists?
no
Alarm solved
336 / 533
26.4 [73,148] RESET

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description RESET Equipment Indeterminate Warning (MI) An autonomous load of the CE occurred. The module has undergone serious 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).
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities

None, this alarm reports the autonomous load of the CE only. See TC Alarms (Section 29.5) for the Alarm number description.
337 / 533
26.5 [73,202] NO-Q1-CONN

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description NO-Q1-CONN Equipment Indeterminate Minor (DMA) There is a connection problem on the QMux bus, no response is received from the network element. The TSC is unable to find any or certain network elements connected to the primary or secondary bus. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
338 / 533

[73,202] NO Q1CONN
Alarm on suspected RIT events? no
yes
Solve that alarm(s)
yes
Solve that alarm(s)
no
no Correct Address
Qmux address in DLS OK? yes
no
Alarm persists?
yes
Onsite
Check/Replace Qmux equipment
Alarm solved
no
Alarm persists?
Figure 136: NO-Q1-CONN: Corrective Actions
339 / 533
26.6 [73,203] LOSS-OF-ACT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOSS-OF-ACT Equipment Indeterminate Minor (DMA) - in commercial use, Warning (MI) - out of commercial use Loss of Activity due to link failure. Each incoming BS interface link can be scanned in order to detect a malfunction (disconnection of a cable). Only one link can be scanned at a time. The firmware gives a reset to this alarm bit. A certain time later, the firmware reads the alarm bit in order to detect a link failure. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
340 / 533

[73,203] LOSS OFACT
Lock BIUA
Unlock BIUA
no
BIUA alarm events?
no
Alarm persists?
no
Alarm solved
Figure 137: LOSS-OF-ACT: Corrective Actions
341 / 533
26.7 [73,212] LOSS-OF-CLK-8M

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOSS-OF-CLK-8M Equipment Indeterminate Minor (DMA) - in commercial use, Warning (MI) - out of commercial use 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 is detected by a PAD. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
342 / 533

[73,212] LOSS OFCLOCK8M
Clock alarm events?
yes
Solve that alarm(s)
no
BCLA alarm events? no
yes
Solve that alarm(s)
Alarm persists?
no
Alarm solved
yes
Onsite
Replace BCLA
Alarm persists?
no
Alarm solved
Figure 138: LOSS-OF-CLK-8M: Corrective Actions
343 / 533
26.8 [73,213] LOSS-OF-CLK-BOTH-8M

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System LOSS-OF-CLK-BOTH-8M Equipment Indeterminate Major (PMA) - in commercial use, Warning (MI) - out of commercial use Both 8 MHz clock sources are lost. The internal clock is selected. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
344 / 533

[73,213] LOSS OFCLOCKBOTH8M
Clock alarm events?
yes
Solve that alarm(s)
no
yes
Solve that alarm(s)
Alarm persists?
no
Alarm solved
yes
Onsite
Replace BCLA
Alarm persists?
no
Alarm solved
Figure 139: LOSS-OF-CLK-BOTH-8M: Corrective Actions
345 / 533
26.9 [73,216] RESTART

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description RESTART Equipment Indeterminate Warning (MI) An autonomous restart of the CE has occurred. The operating system and all processes are re-initialized sequentially. All non-volatile protected data is cleared and a new initialization of the dynamic data has taken place See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

None this alarm reports an autonomous restart of the CE only.
346 / 533
26.10 [73,241] SET-PROD-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SET-PROD-FAIL Equipment Indeterminate Minor (DMA) This alarm indicates the NE settings production has failed. The equipment settings are not in line with the DLS. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities

[73,241] SETPRODFAIL
no Correct DSL settings
DSL settings OK?
yes
Lock BSCADAPT
Unlock BSCADAPT
Alarm solved
no
Alarm persists?
Figure 140: SET-PROD-FAIL: Corrective Actions
347 / 533

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description DOWNLOAD-FAIL Equipment Indeterminate Minor (DMA) This alarm indicates the programming of the BSC-ADAPT has failed. Modification of BSC-Adapt parameters has occurred in the BSC, and downloading of the BSC-Adapt has been initiated but has failed. The equipment settings are not in line with the DLS. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
348 / 533

[73,246] DOWNLOAD FAIL
DSL settings OK?
yes
Lock BSCADAPT
Unlock BSCADAPT
Alarm persists?
no
Alarm solved
349 / 533
26.12 [73,247] ACCESS-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ACCESS-FAIL Equipment Indeterminate Minor (DMA) This alarm indicates the programming of the BSC-ADAPT has failed. Modification of BSC-Adapt parameters has occurred in the BSC and access attempts towards the BSC-ADAPT has failed. The equipment settings are not in line with the DLS and will be replaced. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities

[73,247] ACCESS FAIL
yes TCU/TSL/NE alarm events? Solve that alarm(s)
no
Alarm persists?
no
Alarm solved
350 / 533
27 Class 74: BTS-ADAPT

This section defines the TC alarms for the Class 74: BTSADAPT alarm class.
351 / 533
27.1 [74,20] BLOCKED-FROM-USE

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description BLOCKED-FROM-USE Equipment Indeterminate Minor (DMA) Unit is not in use due to a configuration error. If the same time slots are allocated for two boards, then the allocations on one board are blocked from use. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
352 / 533

[74,20] BLOCKED FROMUSE
Correct time slot settings
no
Time slot settings OK?
yes
no
Alarm persists and SMBS was powered off/on?
yes
Onsite
Disengage and replug SMBS board
Alarm solved
no
Alarm persists?
Figure 143: BLOCKED-FROM-USE: Corrective Actions
353 / 533

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOOP-TO-EQUIP Equipment Indeterminate Major (PMA) 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).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

Remove BSC interface loop
When a loop is activated, it deactivates after a preset control timeout.
Alarm solved
no
Alarm persists?
yes
354 / 533
27.3 [74,23] TESTMODE

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TESTMODE Equipment Indeterminate Major (PMA) The equipment, or part of it, is under test. Normal operation is suspended. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities

None equipment is under test. See TC Alarms (Section 29.5) for the Alarm number description.
355 / 533
27.4 [74,122] SYNCHRO-AL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SYNCHRO-AL Equipment Indeterminate Minor (DMA) The primary synchronization source is missing or not selected. The module switches to the secondary source. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
356 / 533

[74,122] SYNCHROAL
Clock alarm events?
no
PCM alarm events?
no
Alarm persists?
no
Alarm solved
yes
Onsite
Check/Replace clock cabling
Alarm persists?
no
Alarm solved
Figure 145: SYNCHRO-AL: Corrective Actions
357 / 533
27.5 [74,124] SYNC-AL-CLOCKR

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SYNC-AL-CLOCKR Equipment Indeterminate Major (PMA) Synchronizing fault in clock recovery has occurred. The synchronizing signal is missing. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
358 / 533

[74,124] SYNCAL CLOCKR
Clock alarm events?
no
PCM alarm events?
no
Clock configuration settings OK?
no Correct clock settings
yes
Alarm persists?
no
Alarm solved
yes
Onsite
Check/Replace clock cabling
Alarm persists?
no
Alarm solved
Figure 146: SYNC-AL-CLOCKR: Corrective Actions
359 / 533

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description EQUIPMENT-FAULT Equipment Indeterminate Major (PMA) There is a basic operational malfunction. An internal fault has been detected on a board. See Consequences of an SBL State Change (Section 30).
Impact on System
BTS-ADAPT = FLT Impact Loss Degradation BTS-ADAPT = FIT Impact Loss Degradation Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
360 / 533

Lock BTSADAPT
Unlock BTSADAPT
Alarm persists?
no
Alarm solved
yes
Onsite
Alarm persists?
no
Alarm solved
361 / 533

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System MEMORY-FAULT Equipment Indeterminate Major (PMA) An EEPROM memory write access has been unsuccessful. See Consequences of an SBL State Change (Section 30).
BTS-ADAPT = FLT Impact Loss Degradation Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
BTS-ADAPT = FIT Impact Loss Degradation Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities -
362 / 533

BIU alarm events? no
yes
Solve that alarm(s)
Lock BTSADAPT
Unlock BTSADAPT
Alarm persists?
no
Alarm solved
yes
Onsite
Replace BIU
Alarm persists?
no
Alarm solved
363 / 533
27.8 [74,139] MISSING-UNIT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description MISSING-UNIT Equipment Indeterminate Major (PMA) A defined slave unit is missing from the configuration. The board is not connected, no response is received from the slave board. The accessed unit is not installed into the configuration although it is defined as being equipped. (Transmission equipment is organized into master modules - those polled by the TSC via the Q1 bus - and slave modules that are monitored by the master modules). Impact on System See Consequences of an SBL State Change (Section 30).
BTS-ADAPT=FLT Impact Loss Degradation BTS-ADAPT=FIT Impact Loss Degradation Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
364 / 533

[74,139] MISSING UNIT
BTS RIT alarm events?
yes
Solve that alarm(s)
no
Lock BTSADAPT
Unlock BTSADAPT
no
Alarm persists?
yes
Onsite
Replug/Replace suspected RIT
Alarm solved
no
Alarm persists?
Figure 149: MISSING-UNIT: Corrective Actions
365 / 533
27.9 [74,141] FORCED-CNTRL-ON

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System FORCED-CNTRL-ON Equipment Indeterminate Major (PMA) A forced control (loop, changeover, etc.) is activated. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities

[74,141] FORCED CONTROLON
Remove forced control
The normal condition returns after a preset timeout.
Alarm persists?
no
Alarm solved
Figure 150: FORCED-CNTRL-ON: Corrective Actions
366 / 533
27.10 [74,142] INSTALLATION

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description INSTALLATION Equipment Indeterminate Major (PMA) Installation incorrectly performed. This alarm can also appears as an event when the board is manipulated. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
367 / 533

[74,142] INSTALLATION
BTS RIT alarm events?
yes
Solve that alarm(s)
no
Lock BTSADAPT
Unlock BTSADAPT
no
Alarm persists?
yes
Onsite
Alarm solved
no
Alarm persists?
Figure 151: INSTALLATION: Corrective Actions
368 / 533
27.11 [74,148] RESET

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description RESET Equipment Indeterminate Warning (MI) An autonomous load of the CE occurred. The module has undergone serious service interruption, but has recovered. The reset/restart 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).
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities

369 / 533
27.12 [74,159] DIAG-TESTS

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System DIAG-TESTS Equipment Indeterminate Major (PMA) A diagnostic test is running. See Consequences of an SBL State Change (Section 30).
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities

None the operator has activated the TEST function to obtain more detailed information. See TC Alarms (Section 29.5) for the Alarm number description.
370 / 533
27.13 [74,202] NO-Q1-CONN

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description NO-Q1-CONN Equipment Indeterminate Minor (DMA) A connection problem occurred on the Qmux bus, no response received from the network element. The TSC is unable to find any or certain network elements connected to the primary or secondary bus. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
371 / 533

[74,202] NO Q1CONN
Alarm on BTS RIT events? no
yes
Solve that alarm(s)
Transmission alarm events? no
yes
Solve that alarm(s)
Qmux address in DLS OK? no
yes
Correct Address
Alarm persists?
no
Alarm solved
yes
Onsite
Alarm persists?
no
Alarm solved
372 / 533
27.14 [74,241] SET-PROD-FAIL

Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
373 / 533

DSL settings OK?
yes
Lock BSCADAPT
Unlock BSCADAPT
Alarm solved
no
Alarm persists?
374 / 533
27.15 [74,245] LOCAL-REINIT-REQ

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOCAL-REINIT-REQ Equipment Indeterminate Minor (DMA) This alarm indicates programming is required locally. Modification of BTS-Adapt parameters has occurred in the BSC, but the setting at the BTS_Adapt must be carried out locally and cannot be carried out remotely. The equipment settings are not in line with the DLS. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
375 / 533

[74,245] LOCAL REINITREQ
BTS parameter settings OK?
no Correct settings
yes
Disable BSCADAPT
Init BSCADAPT
Alarm persists?
no
Alarm solved
Figure 154: LOCAL-REINIT-REQ: Corrective Actions
376 / 533

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description DOWNLOAD-FAIL Equipment Indeterminate Minor (DMA) This alarm indicates that programming of the BTS-ADAPT has failed. Modification of BTS-Adapt parameters has occurred in the BSC, and downloading of the BTS_Adapt has been initiated but has failed. The equipment settings are not in line with the DLS. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
377 / 533

[74,246] DOWNLOAD FAIL
DLS settings OK?
no Correct settings
yes
Lock BSCADAPT
Unlock BSCADAPT
Alarm persists?
no
Alarm solved
378 / 533
27.17 [74,247] ACCESS-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ACCESS-FAIL Equipment Indeterminate Minor (DMA) This alarm indicates that programming of the BTS-ADAPT has failed. Modification of BTS-Adapt parameters has occurred in the BSC, but access towards the BTS-Adapt has failed. The equipment settings are not in line with the DLS. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities

[74,247] ACCESSFAIL
TCU/TSL/NE alarm events?
no
Alarm persists?
no
Alarm solved
379 / 533
380 / 533
28 Class 75: TCSM-ADAPT

This section defines the TC alarms for the Class 75: TCSMADAPT alarm class.
381 / 533
28.1 [75,20] BLOCKED-FROM-USE

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description BLOCKED-FROM-USE Equipment Indeterminate Minor (DMA) Unit is not in use due to a configuration error. If the same time slots are allocated for two boards, then the allocations on one board are blocked from use. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling
O&M; Capabilities -

[75,20] BLOCKED FROMUSE
Time slot settings OK?
no
Correct time slot settings
yes
Alarm persists?
no
Alarm solved
Figure 157: BLOCKED-FROM-USE: Corrective Actions
382 / 533

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOOP-TO-EQUIP Equipment Indeterminate Major (PMA) 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 Loss Degradation SM-ADAPT = FIT Impact Loss Degradation TC-ADAPT = IT Impact Loss Degradation Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities -
383 / 533

Remove BSC interface loop
Alarm persists? no yes Contact System Support
Alarm solved
384 / 533
28.3 [75,112] FAN-ALARM

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description FAN-ALARM Equipment Indeterminate Critical (VPMA) The Fan rotation speed has been detected to be lower than the minimum threshold value for that speed or a temperature higher than normal operating value has been detected in the rack. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation

[75,112] FANALARM
Onsite
Replace fan unit
Alarm persists?
no
Alarm solved
Figure 159: FAN-ALARM: Corrective Actions
385 / 533
28.4 [75,122] SYNCHRO-AL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SYNCHRO-AL Equipment Indeterminate Minor (DMA) The primary synchronization source is missing. The module switches to the secondary source. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
386 / 533

[75,122] SYNCHROAL
Clock alarm events?
no
PCM alarm events?
no
Alarm persists?
no
Alarm solved
yes
Onsite
Check/Replace Clock equipment
Alarm persists?
no
Alarm solved
Figure 160: SYNCHRO-AL: Corrective Actions
387 / 533
28.5 [75,124] SYNCHRO-AL-CLOCKR

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description SYNCHRO-CLOCKR Equipment Indeterminate Major (PMA) Synchronizing fault in clock recovery has occurred. The synchronizing signal is missing. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
388 / 533

[75,124] SYNCHRO ALCLOCKR
Clock alarm events?
no
PCM alarm events?
no
Clock configuration settings OK? no Correct clock configuration settings
yes
Alarm persists?
no
Alarm solved
yes
Onsite
Check/Replace Clock equipment
Alarm persists?
no
Alarm solved
Figure 161: SYNCHRO-AL-CLOCKR: Corrective Actions
389 / 533

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description EQUIPMENT-FAULT Equipment Indeterminate Major (PMA) There is a basic operational malfunction. An internal fault has been detected on a board. See Consequences of an SBL State Change (Section 30).
Impact on System
SM-ADAPT = FLT Impact Loss Degradation SM-ADAPT = FIT Impact Loss Degradation TC_ADAPT = FLT Impact Loss Degradation Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities -
390 / 533

Lock SMADAPT/TC_ADAP T
Unlock SMADAPT/TC_ADAP T
Alarm persists?
no
Alarm solved
yes
Onsite
Alarm persists?
no
Alarm solved
Figure 162: EQUIPMENT-FAUL: Corrective Actions
391 / 533

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description MEMORY-FAULT Equipment Indeterminate Major (PMA) 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).
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling
O&M; Capabilities -
392 / 533

BIU alarm events?
yes
Solve that alarm(s)
G2 TC
no
A925 TC
Lock SMADAPT/ TCADAPT Reset MT120 Unlock SMADAPT/ TCADAPT
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes
Onsite Onsite
yes
Replace BIU
Replace MT120
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes Contact System Support Contact System Support
393 / 533
28.8 [75,136] FIRST-DSP-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description FIRST-DSP-FAIL Equipment Indeterminate Major (PMA) One out of the twelve DSPs of a MT120 has failed. All channels of this DSP are fully recovered and are now handled by the other eleven DSPs. If no further DSPs have failed (e.g. MEMORY-FAULT) then this MT120 is still able to handle all resources (up to 120 channels), but it works in a degraded mode, as it cannot recover any additional DSP failure. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
394 / 533

[75,136] FIRST DSPFAIL
Reset MT120
Alarm persists?
no
Alarm solved
Onsite
yes
Replace MT120
Alarm persists?
no
Alarm solved
Figure 164: FIRST-DSP-FAIL: Corrective Actions
395 / 533
28.9 [75,139] MISSING-UNIT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description MISSING-UNIT Equipment Indeterminate Major (PMA) A defined slave unit is missing from the configuration. The slave board is not connected, there is no response received from the slave board. The accessed unit is not installed into the configuration although it is defined to be equipped. (Transmission equipment is organized into master modules - those polled by the TSC via the Q1 bus - and slave modules that are monitored by the master modules). Impact on System See Consequences of an SBL State Change (Section 30).
SM-ADAPT = FIT Impact Loss Degradation TC-ADAPT = FLT Impact Loss Degradation Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities -
396 / 533

[75,139] MISSING UNIT
BTS RIT alarm events? no
yes
Solve that alarm(s)
Lock SMADAPT/ TCADAPT
Unlock SMADAPT/ TCADAPT
no
Alarm persists?
yes
Onsite
Alarm solved
no
Alarm persists?
Figure 165: MISSING-UNIT: Corrective Actions
397 / 533
28.10 [75,141] FORCED-CNTRL-ON

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System FORCED-CNTRL-ON Equipment Indeterminate Major (PMA) Forced control (loop, changeover etc.) is activated. 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
398 / 533

[75,141] FORCED CONTROLON
Remove forced control
The normal condition returns after a preset timeout.
Alarm solved
no
Alarm persists?
yes
Figure 166: FORCED-CNTRL-ON: Corrective Actions
399 / 533
28.11 [75,142] INSTALLATION

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description INSTALLATION Equipment Indeterminate Major (PMA) Installation incorrectly performed, or appears as an event when the board is manipulated. See Consequences of an SBL State Change (Section 30).
Impact on System
SBL SM-ADAPT Impact Loss Degradation SBL TC-ADAPT Impact Loss Degradation Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities -
400 / 533

[75,142] INSTALLATION
Alarm on suspected RIT events? no Lock SMADAPT/ TCADAPT
yes
Solve that alarm(s)
Unlock SMADAPT/ TCADAPT
no
Alarm persists?
yes
Onsite
Alarm solved
no
Alarm persists?
Figure 167: INSTALLATION: Corrective Actions
401 / 533
28.12 [75,148] RESET

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description RESET Equipment Indeterminate Warning (MI) An autonomous load of the CE occurred. The module has undergone serious 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).
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

402 / 533
28.13 [75,159] DIAG-TESTS

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System DIAG-TESTS Equipment Indeterminate Major (PMA) A diagnostic test is running. See Consequences of an SBL State Change (Section 30).
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling
O&M; Capabilities -

None the operator has activated the TEST function to obtain more detailed information. See TC Alarms (Section 29.5) for the Alarm number description.
403 / 533
28.14 [75,202] NO-Q1-CONN

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description NO-Q1-CONN Equipment Indeterminate Minor (DMA) No response received from the network element. The TSC is unable to find any or certain network elements connected to the primary or secondary bus. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities
404 / 533

[75,202] NO Q1CONN
alarm on suspected RIT events? no
no
no Correct Address
Qmux address in DLS OK? yes
no
Alarm persists?
yes
Onsite
Alarm solved
no
Alarm persists?
yes
405 / 533
28.15 [75,208] TRIB-TRANS-FLT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TRIB-TRANS-FLT Equipment Indeterminate Warning (MI) The PCM event counter threshold value is exceeded on one tributary interface, which results in the generation of this 2 Mbit/s alarm. For each PCM event, a counter is increased. At certain intervals, the counter will be decreased by 1. When the threshold value is exceeded, this alarm is generated for that 2 Mbit/s interface. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
406 / 533

[75,208] TRIB TRANSFLT
no
yes PCM alarm events? Solve that alarm(s) first
no
yes
Related tributary alarm events? no
Solve that alarm(s)
yes
Alarm persists?
no
no Onsite Repair/replace Tributary interface
Tributary interface operational?
yes
no
Local tributary cabling OK? yes
Alarm persists?
no
Alarm solved
yes
Figure 169: TRIB-TRANS-FLT: Corrective Actions
407 / 533
28.16 [75,209] INT-BUS-FLT-G25

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description INT-BUS-FLT-G25 Equipment Indeterminate Major (PMA) An internal bus fault has occurred on one or both TCIL links (internal O&M; bus between MT120) inside the A9125 TC rack. The TCIL links are duplicated HDLC multi-master busses. These TCIL links convey internal messages as well as external Qmux messages (coming from the TSC). In case of the bus not working, Qmux polling of boards not directly receiving the primary or secondary links, cannot be done. The O&M; data flow is broken, the rack cannot be supervised, but the telecom data path still works. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities
408 / 533

[75,209] INTBUS FLTG25
Put a spare at address 75
no
Board at address 75?
yes
MT120 highest address?
no
MT120 lowest address? no
yes
Board at address16?
no
Put a spare at address 16
Replace MT120
yes
Last board with alarm?
no
Alarm solved
no
Alarm persists?
yes
Replace MT120
yes
Alarm persists?
no Alarm solved
Figure 170: INT-BUS-FLT-G25: Corrective Actions
409 / 533
28.17 [75,210] ATER-TRANS-FLT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ATER-TRANS-FLT Equipment Indeterminate Warning (MI) The PCM event counter threshold value is exceeded on one ATER interface, which results in the generation of this 2 Mbit/s alarm. For each PCM event, a counter is increased. At certain intervals, the counter will be decreased by 1. When the threshold value is exceeded, this alarm is generated for that 2 Mbit/s interface. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
410 / 533

[75,210] ATER TRANSFLT
Other Ater alarm events? yes
no
PCM/ATER alarm events? Solve that alarm(s) first
no
yes
Ater interface alarm events?
Solve that alarm(s) no
yes
Alarm persists?
no
no
Ater interface operational?
yes
Onsite Repair/replace Ater interface no Local Ater cabling OK? yes Trigger remote signal path and transmitter tests on MSC side
Alarm persists?
no
Alarm solved
Figure 171: ATER-TRANS-FLT: Corrective Actions
411 / 533
28.18 [75,211] LOSS-OF-CLOCK-2M

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOSS-OF-CLOCK-2M Equipment Indeterminate Minor (DMA) - in commercial use, Warning (MI) - out of commercial use The 2 MHz clock source is lost. Once the PAD detects the loss of the 2 MHz clock source, the next clock source will be selected if available. The firmware will detect the missing clock source number. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling
O&M; Capabilities -
412 / 533

[75,211] LOSSOF CLOCK2M
Link related alarm events?
no
yes APCM alarm events? Solve that alarm(s) first
no
yes
Solve that alarm(s)
Onsite
yes
Alarm persists?
no
no
yes
no
Local trunk cabling OK?
yes Trigger remote signal path and transmitter tests on MSC side
Alarm persists?
no
Alarm solved
yes
Figure 172: LOSS-OF-CLOCK-2M: Corrective Actions
413 / 533
28.19 [75,216] RESTART

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description RESTART Equipment Indeterminate Warning (MI) An autonomous processor restart has occurred. The operating system and all processes are re-initialized sequentially. A new initialization of the dynamic data takes place. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

None this alarm reports an autonomous restart of the CE only. See TC Alarms (Section 29.5) for the Alarm number description.
414 / 533
28.20 [75,221] TRIB-TWO-MB-MISSING

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TRIB-TWO-MB-MISSING Equipment Indeterminate Major (PMA) The 2 Mbit/s on one tributary interface is not receiving a signal. The loss of the incoming digital signal at 2048 kbit/s is considered as a loss of the incoming 2M signal. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling
O&M; Capabilities -
415 / 533

[75,221] TRIBTWO MBMISSING
no
yes SMADAPT alarm events? Solve that alarm(s) first yes
no
Solve that alarm(s)
yes
Alarm persists?
no
no
yes
Onsite Repair/replace Receiver no Local cabling OK? yes
Alarm persists?
no
Alarm solved
yes
Figure 173: TRIB-TWO-MB-MISSING: Corrective Actions
416 / 533
28.21 [75,222] TRIB-AIS-2MB

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description Impact on System TRIB-AIS-2MB Equipment Indeterminate Minor (DMA) The 2 Mbit/s on one tributary interface is receiving an AIS signal (all ones). See Consequences of an SBL State Change (Section 30).
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling
O&M; Capabilities -

[75,222] TRIB AIS2MB
Loop activated?
yes Remove loop
no
Transmission signal settings OK? no
yes
Remote transmitter alarm(s) events? no
Correct transmission settings
Trigger remote transmitter test
Alarm solved
no
Alarm persists?
yes
Figure 174: TRIB-AIS-2MB: Corrective Actions
417 / 533
28.22 [75,223] TRIB-FRAME-ALIGNMENT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TRIB-OF-FRAME-ALIGNMENT Equipment Indeterminate Major (PMA) The 2 Mbit/s signal frame alignment on one tributary interface is lost. Traffic is not possible. TS0 is reserved for frame alignment, alarms and network synchronization information and should not be used for Signaling or speech purposes. The frame alignment signal is monitored to determine if the frame alignment has been lost. The frame alignment will be assumed to have been lost when three consecutive incorrect frame alignment signals have been received. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling
O&M; Capabilities -
418 / 533

[75,223] TRIB FRAMEALIGNMENT
Loop activated?
yes Remove loop
no
Transmission signal settings OK?
yes
no
Remote transmitter alarm(s) events? no
Correct transmission settings
Trigger remote transmitter test
Alarm solved
no
Alarm persists?
yes
Figure 175: TRIB-FRAME-ALIGNMENT: Corrective Actions
419 / 533
28.23 [75,224] TRIB-CRC-MFRAME-ALGN

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TRIB-CRC-MFRAME-ALGN Equipment Indeterminate Major (PMA) The expected patterns not received on TS0 of the PCM (CRC multiframe) on one tributary interface. The CRC is not used in the remote end or there may be interferences on the connection. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling
O&M; Capabilities -

[75,224] TRIB CRCMFRAMEALGN
Time slot 0 CRCl settings OK?
yes
Remote CRC alarm(s) events?
no
no
Correct CRC settings
Trigger remote signal path tests
Alarm solved
no
Alarm persists?
yes
Figure 176: TRIB-CRC-MFRAME-ALGN: Corrective Actions
420 / 533
28.24 [75,225] TRIB-BER-10E-3

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TRIB-BER-10E-3 Equipment Indeterminate Major (PMA) 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 the preset threshold value of 10E-3. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s)
Cell/ BTS(s) -
Signaling
Call Handling
O&M; Capabilities -
421 / 533

[75,225] TRIB BER10E3
no
yes
SMADAPT alarm events?
no
yes
Solve that alarm(s)
yes
Alarm persists?
no
no
yes
Onsite Repair/replace Receiver no Local cabling OK? yes Trigger remote signal path and transmitter tests on MSC side
Alarm persists?
no
Alarm solved
yes
Figure 177: TRIB-BER-10E-3: Corrective Actions
422 / 533
28.25 [75,226] TRIB-BER-10E-4

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TRIB-BER-10E-4 Equipment Indeterminate Minor (DMA) 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 the preset threshold value of 10E-4. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
423 / 533

[75,226] TRIB BER10E4
Link related alarm events? yes
no
SMADAPT alarm events? Solve that alarm(s) first yes
no
Solve that alarm(s)
yes
Alarm persists?
no
no Onsite
yes
no
Local cabling OK? yes Trigger remote signal path and transmitter tests on MSC side
Alarm persists?
no
Alarm solved
424 / 533
28.26 [75,227] TRIB-BER-10E-6

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TRIB-BER-10E-6 Equipment Indeterminate Minor (DMA) 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 the preset threshold value of 10E-6. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
425 / 533

[75,227] TRIB BER10E6
no
yes SMADAPT alarm events? Solve that alarm(s) first
no
yes
Solve that alarm(s)
Onsite
yes
Alarm persists?
no
no
yes
no
Local cabling OK? yes
Alarm persists?
no
Alarm solved
yes
426 / 533
28.27 [75,228] TRIB-FAR-END-ALARM

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description TRIB-FAR-END-ALARM Equipment Indeterminate Minor (DMA) The equipment at the remote end has acknowledged the faulty condition of the interface signal, on one tributary interface. Alarm indication from the remote end is detected when bit 3 of channel TS0 changes state from 0 to 1 in those frames not containing the frame alignment signal. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
Loss Degradation -
427 / 533

[75,228] TRIB FARENDALARM
no
yes SMADAPT alarm events? Solve that alarm(s) first yes Related receiver alarm events? no yes Solve that alarm(s) no
Solve that alarm(s)
yes
Alarm persists?
no
no
yes
Onsite no Local cabling OK? yes
Alarm persists?
no
Alarm solved
Figure 180: TRIB-FAR-END-ALARM: Corrective Actions
428 / 533
28.28 [75,231] ATER-TWO-MB-MISSING

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ATER-TWO-MB-MISSING Equipment Indeterminate Major (PMA) 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 a loss of the incoming 2M signal. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s)
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
429 / 533

[75,231] ATER TWOMBMISSING
Ater related alarm events? yes
no
TCADAPT alarm events? Solve that alarm(s) first
no
yes Related receiver alarm events? Solve that alarm(s) no yes Solve that alarm(s)
Onsite
yes
Alarm persists?
no
no
yes
no
Local Ater cabling OK? yes
Trigger remote signal path and transmitter tests on BSC side
Alarm persists?
no
Alarm solved
yes
Figure 181: ATER-TWO-MB-MISSING: Corrective Actions
430 / 533
28.29 [75,232] ATER-AIS-2MB

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ATER-AIS-2MB Equipment Indeterminate Major (PMA) The 2 Mbit/s interface on one Ater interface is receiving an AIS signal (all ones). See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s)
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
431 / 533

[75,232] ATER AIS2MB
Ater related alarm events?
no
yes
TCADAPT alarm events?
no
Solve that alarm(s) first yes Loops activated? yes Remove activated loops
Solve that alarm(s) no
yes
Alarm persists?
no
no
yes
Onsite no Local Ater cabling OK? yes Trigger remote signal path and transmitter tests on BSC side
Alarm persists?
no
Alarm solved
Figure 182: ATER-AIS-2MB: Corrective Actions
432 / 533
28.30 [75,233] ATER-FRAME-ALIGNMENT

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ATER-FRAME-ALIGNMENT Equipment Indeterminate Major (PMA) The 2 Mbit/s signal frame alignment on one Ater interface is lost. Traffic is not possible. TS0 is reserved for frame alignment, alarms and network synchronization information and should not be used for Signaling or speech purposes. The frame alignment signal is monitored to determine if the frame alignment has been lost. The frame alignment will be assumed to have been lost when three consecutive incorrect frame alignment signals have been received. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
433 / 533

[75,233] ATER FRAMEALIGNMENT
Ater related alarm events?
no
yes
no
Solve that alarm(s) first yes Time slot 0 settings OK? no Correct the settings
Solve that alarm(s)
yes
yes
Alarm persists?
no
no
yes
Onsite no Local Ater cabling OK? yes Trigger remote signal path and transmitter tests on BSC side
Alarm persists?
no
Alarm solved
Figure 183: ATER-FRAME-ALIGNMENT: Corrective Actions
434 / 533
28.31 [75,234] ATER-CRC-MFRAME-ALGN

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ATER-CRC-MFRAME-ALGN Equipment Indeterminate Major (PMA) The expected patterns not received on TS0 of the PCM (CRC multiframe) on one Ater interface. The CRC is not used in the remote end or there maybe interferences on the connection. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
435 / 533

[75,234] ATER CRCMFRAMEALGN
Time Slot 0 CRC settings OK?
yes
no
Remote CRC alarm(s) events?
Correct CRC settings
no
Alarm solved
no
Alarm persists?
yes
Figure 184: ATER-CRC-MFRAME-ALGN: Corrective Actions
436 / 533
28.32 [75,235] ATER-BER-10E-3

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ATER-BER-10E-3 Equipment Indeterminate Major (PMA) Signal input BER worse than 1 in 1000 on one Ater interface. The error rate of the incoming main system signal is worse than the preset threshold value of 10E-3. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s)
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
437 / 533

[75,235] ATER BER10E3
no
yes
no
Solve that alarm(s) first yes Related receiver alarm events? no yes Solve that alarm(s)
Solve that alarm(s)
yes
Alarm persists?
no
no
yes
Onsite no Local cabling OK? yes Trigger remote signal path and transmitter tests on MSC side
Alarm persists?
no
Alarm solved
Figure 185: ATER-BER-10E-3: Corrective Actions
438 / 533
28.33 [75,236] ATER-BER-10E-4

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ATER-BER-10E-4 Equipment Indeterminate Minor (DMA) Signal input BER worse than 1 in a 10000 on one Ater interface. The error rate of the incoming main system signal is worse than the preset threshold value of 10E-4. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
439 / 533

[75,236] ATER BER10E4
no
yes
no
yes
Solve that alarm(s)
yes Onsite
Alarm persists?
no
no
yes
no
Local cabling OK? yes Trigger remote signal path and transmitter tests on MSC side
Alarm persists?
no
Alarm solved
yes
440 / 533
28.34 [75,237] ATER-BER-10E-6

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ATER-BER-10E-6 Equipment Indeterminate Minor (DMA) Signal input BER worse than 1 in a million on one Ater interface. The error rate of the incoming main system signal is worse than the preset threshold value of 10E-6. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s) -
Cell/ BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
441 / 533

[75,237] ATER BER10E6
no
yes TCADAPT alarm events? Solve that alarm(s) first yes
no
Related receiver alarm events?
Solve that alarm(s)
no
yes
Alarm persists?
no
no
yes
Onsite Repair/replace Receiver no Local cabling OK? yes Trigger remote signal path and transmitter tests on MSC side
Alarm persists?
no
Alarm solved
442 / 533
28.35 [75,238] ATER-FAR-END-ALARM

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description FAR-END-ALARM Equipment Indeterminate Major (PMA) The equipment at the remote end has acknowledged the faulty condition of the interface signal, on one Ater interface. Alarm indication from the remote end is detected when bit 3 of channel TS0 changes state from 0 to 1 in those frames not containing the frame alignment signal. See Consequences of an SBL State Change (Section 30).
Impact on System
Trunk(s)
Cell/ BTS(s) -
Signaling -
Call Handling
O&M; Capabilities -
443 / 533

[75,238] ATER FARENDALARM
yes
no
no
Alarm persists?
yes
Trigger remote signal path and transmitter tests on BSC side
Alarm solved
no
Alarm persists?
yes
Figure 188: ATER-FAR-END-ALARM: Corrective Actions
444 / 533
28.36 [75,241] SET-PROD-FAIL

Impact on System
SM-ADAPT Impact Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities
Loss Degradation TC-ADAPT Impact Trunk(s) -
Cell/ BTS(s)
Signaling
Call Handling -
O&M; Capabilities
Loss Degradation
445 / 533

DSL settings OK?
yes
Lock SM/TCADAPT
Unlock SM/TCADAPT
Alarm solved
no
Alarm persists?
yes
446 / 533
28.37 [75,245] LOCAL-REINIT-REQ

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description LOCAL-REINIT-REQ Equipment Indeterminate Minor (DMA) This alarm indicates that programming is required locally. Modification of SM-ADAPT/TC-ADAPT parameters has occurred in the BSC, but the setting at the SM-ADAPT/TC-ADAPT must be carried out locally and cannot be carried out remotely. The equipment settings are not in line with the DLS. See Consequences of an SBL State Change (Section 30).
Impact on System
Impact SM-ADAPT
Trunk(s)
Cell/ BTS(s)
Signaling
Call Handling
O&M; Capabilities
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 Loss Degradation Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities -
447 / 533

[75,245] LOCAL REINITREQ
no Correct settings
BTS parameter settings OK? yes
Disable SM/TCADAPT
Init SM/TCADAPT
Alarm solved
no
Alarm persists?
yes
Figure 190: LOCAL-REINIT-REQ: Corrective Actions
448 / 533

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description DOWNLOAD-FAIL Equipment Indeterminate Minor (DMA) This alarm indicates that programming of the SM-ADAPT/TC-ADAPT has failed. Modification of SM-ADAPT/TC-ADAPT parameters has occurred in the BSC, and downloading of the SM_ADAPT/TC-ADAPT has been initiated but has failed. The equipment settings are not in line with the DLS. See Consequences of an SBL State Change (Section 30).
Impact on System
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
449 / 533

[75,246] DOWNLOADFAIL
DSL settings OK?
yes
Lock SM/TCADAPT
Unlock SM/TCADAPT
Alarm solved
no
Alarm persists?
yes
450 / 533
28.39 [75,247] ACCESS-FAIL

specificProblems: eventType: probableCause: perceivedSeverity: Alarm Description ACCESS-FAIL Equipment Indeterminate Minor (DMA) This alarm indicates that programming of the SM-ADAPT/TC-ADAPT has failed. Modification of SM/TC-ADAPTt parameters has occurred in the BSC, and access towards the SM-ADAPT/TC-ADAPT has failed. The equipment settings are not in line with the DLS. See Consequences of an SBL State Change (Section 30).
Impact on System
SM-ADAPT All calls managed by the processor are lost with or without WTC as specified by the operator. Impact Loss Degradation TC-ADAPT All calls managed by the processor are lost with or without WTC as specified by the operator. Impact Loss Degradation Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities Trunk(s) Cell/ BTS(s) Signaling Call Handling O&M; Capabilities -
451 / 533

[75,247] ACCESSFAIL
TCU/TSL/NE alarm events?
no
Alarm solved
no
Alarm persists?
yes
452 / 533
29 BSC/TC Alarm Additional Information

This section describes the additional information supplied by some BSC/TC alarms.
453 / 533
29.1 Restart and Software Anomaly Alarms

This section describes the additional information provided by the following Restart 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 the following table. Byte Number 0-1
Description 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.
This specifies the Logical Control Element-Identification. The SBL type specifies the processor type. There is no longer a direct relationship between LCE-ID and CE number. Always 0. Finite Message Machine (FMM) -ID, this identifies the task/process. It is the instruction pointer of the fault. Example: 1E hex = SCCP 1F; hex = N7 SLH (N7 Signaling link handler). Instruction Pointer of the processor address where the fault happened. The first byte is the LSB. Code Segment of the processor address where the fault happened. The first byte is the LSB. Error type, see Table 9. The first byte is the LSB. Sequence number. This is used to distinguish between similar error types. Not relevant. User Data 0. User data providing additional information. User Data 1. User data providing additional information. User Data 2. User data providing additional information. User Data 3. User data providing additional information.
3 4-5
6-7
8-9 10 - 11 12 13 14 - 15 16 - 17 18 - 19 20 - 21
Table 7: Additional Information for Restart and Software Anomaly Alarms
454 / 533
29.1.1 Finite Message Machine

The Finite Message Machine - Identity (FMM-ID) in Bytes 4 and 5 is defined in the following table. Dec 1 2 3 4 5 6 7 8 9 10 11 14 15 16 17 18 19 20 21 22 23 24 25 26 27 Hex 01 02 03 04 05 06 07 08 09 0A 0B 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B FMM-ID ME-INIT-TCU ME-INIT-DTC ME-INIT-CPR ME-TWIN-FILE ME-REMOTE-SSD-ITF ME-ALARM-TCU-DTC ME-REMOTE-FILE ME-ALARM-CPR ME-MAINT-TCU-DTC DBASE-AUDIT-HLDCHCK ME-MAINTENANCE-CPR ME-HSK-1 TCU-TRF-LDC DTC-TRF-LDC ME-MEASUREMENTS-CPR ME-BTS-TCU ME-BTS-CPR ME-REMOTE-LOADER ME-LOADER DH-DTC-TCU LME-NETW-MAINT-MSTR RF-MGT-L3 BSC-LAPD-L2 ME-COPY-FILE LME-NETW-ROUTINES Meaning Initialize TCU (ME = Management Entity). Initialize DTC. Initialize CPR. Twin file. Remote Solid State Disk interface. TCU/DTC alarm. Remote file. CPR alarm. TCU/ DTC maintenance. Database audit handler check. CPR maintenance. ME housekeeping. TCU traffic local data collector. DTC traffic local data collector. CPR measurement. BTS O&M; TCU. BTS O&M; CPR. Remote loader. Loader. DTC/TCU. Network maintenance master. RF management. BSC LAPD. Copy file. Network routines.
455 / 533
Dec 28 29 30 31 32 33 34 35 36 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
Hex 1C 1D 1E 1F 20 21 22 23 24 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38
FMM-ID LME-NETW-MAINT BSSAP SCCP M7-SLH CALL-CONTROL-ACT LME-M7-DTC ME-TCSM ME-MMC ME-DISK-HDLR TCH-RM LE-L3-L2-X.25 LME-X.25 SLNM SM ME-DBASE-TEST-FMM L4E-TRANSPORT L5E-SESSION L6E-PRESENTATION L7E-OSMAE L7E-OSMAP L7E-FTAM DTC-N-7-LDC ME-TRACE-DEBUG-MSTR CALL-CONTROL-TCU ME-EMPTY BSC-HEART-BEAT-CTL TRADEB-SLAVE-F ME-EMPTY-SLAVE
Meaning Network maintenance. BSS Application Part. Signaling Connection Control Part. Signaling link handler for N7. Active CPR call control. Link maintenance entity for N7. TCSM. MMC. Disk handler. TCH resource manager. Link entity for L3, L# X.25. Link maintenance entity for X.25. Signaling link network manager (N7). Signaling manager (N7). Database test FMM. Transport. Session. Presentation. OSMAE. OSMAP. FTAM. DTC N7 local data collector. Trace/debug master. TCU call control. Empty. BSC heartbeat control. Trace/debug slave. Empty slave.
456 / 533
Dec 57 58 59 60 61 62 63 64 66 67 68 69 70 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87
Hex 39 3A 3B 3C 3D 3E 3F 40 42 43 44 45 46 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57
FMM-ID RATA-TCU REMOTE-REQUEST-HDLR REPL-REL-SYNC BACK-UP-DATA-HDLR ME-SECURITY-FILE ROLL-BACK-HDLR RATA-DTC RATA-CPR CPR-N-7-LDC ME-BSC-SW-REPLACE TONE-DTMF-DH-FMM CALL-CONTROL-DTC ME-SUBSCR-ADMIN-CPR OBCI-NH-TEST-FMM ME-HSK-2 ME-HSK-3 RATA-CPR-OSI ME-MMC-TCU ME-INIT-CPR-OSI ME-ALARM-CPR-OSI ME-MAINT-CPR-OSI CPR-TRF-LDC RMH-MSG-HANDLER RECOVERY-ME DH-CPR TELECOM-SUPERV-MOD ASN-ABIS ASN1-CONV
Meaning Read and Throw Away TCU (test only). Remote request handler. Replaced Relation Sync. Backup data handler. Security file. Rollback handler. Read and Throw Away DTC (test only). Read and Throw Away CPR (test only). CPR N7 local data collector. BSC software replacement. DTMF tone device handler. DTC call control. Subscriber administration CPR. On-board controller network handler test. ME housekeeping. ME housekeeping. Read and Throw Away CPR (test only). MMC TCU. Initialize OSI-CPR. OSI-CPR alarm. OSI-CPR maintenance. CPR traffic local data collector. Remote message handler. Recovery. CPR device handler. Telecom supervision module. ASN Abis. ASN1 converter.
457 / 533
Dec 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115
Hex 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73
FMM-ID ME-LOCAL-MAINT-CPR ME-LOCAL-ALARM-CPR ME-HSK-LOCAL ME-HSK-4 LOC-OVRL-CTL TRACE-COORDINATOR TRACE-ADMINISTRATOR TCU-BTS-LDC ME-MEAS-ADMIN ME-MEAS-RECOVERY ME-HSK-5 ME-MEAS-CENTRAL-COLL RECOV-SL-ME ME-HSK-6 ME-HSK-7 ME-MAINT-DTC ME-MAINT-TCU ME-EMPTY-1386 ME-EMPTY-SLAVE-1386 BSC-SCSI-CONTROL RTS-MANAGER RTS-RECONFIGURE OMU-SIMULATOR FU-SIMULATOR MSC-SIMULATOR SMS-CB-MASTER SMS-CB-LOCAL DH-DTC
Meaning CPR local maintenance. CPR local alarm. Local ME housekeeping. Housekeeping 4 Local overload control. Trace Coordinator. Trace Administrator. BTS local data collector for TCU. Measurement administrator. Measurement of recovery. ME housekeeping. Central measurement collector. Recovery of Signaling links. ME housekeeping. ME housekeeping. DTC maintenance. TCU maintenance. Empty FMM for 1386. Empty FMM for slave 1386. Housekeeping. RTS Manager. Reconfigure RTS. OMU simulator. FU simulator. MSC simulator. SMS-CB master. SMS-CB local. DTC device handler.
458 / 533
Dec 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133
Hex 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F 80 81 82 83 84 85
FMM-ID DH-TCU TCSM-ME-CPR TCSM-ME-TCU USAGE-STATE-MASTER USAGE-STATE-SLAVE M7-TEST-FMM TRX-MANAGER TRX-REMAPPER ME-FMM-INIT FMM-SPARE-0 FMM-SPARE-1 FMM-SPARE-2 FMM-SPARE-3 FMM-SPARE-4 FMM-SPARE-5 FMM-SPARE-6 FMM-SPARE-7 SCCP-SCMG
Meaning TCU device handler. TCS on the CPR. TSC on the TCU. Usage State on Demand master. Usage State on Demand slave. N7 test. TRX manager on the CPR. TRX remapper on the CPR. Initialize FMM. Spare FMM. Spare FMM. Spare FMM. Spare FMM. Spare FMM. Spare FMM. Spare FMM. Spare FMM. Signaling Connection Control Part management procedure for the S -CPR. SCM test module. Disk handler for the 386 processor. BCLA handler on the scanning DTCS. Receive and Throw Away (test module). Trace on local data collectors. Master Alertor (not used). Slave Alertor (not used). Heartbeat on the Evolium A9120 BSC. Local alarm handler.
134 135 136 137 138 139 140 141 142
86 87 88 89 8A 8B 8C 8D 8E
FMM-SCM-TEST ME-DISK-HDLR-386 ME-BCLA-HANDLER RATA-CPR-OSI TRACE-LDC ALERTOR-MASTER ALERTOR-SLAVE BSC-HEARTBEAT-G2 ME-LOCAL-ALARM
459 / 533
Dec 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170
Hex 8F 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA
FMM-ID ME-EXT-RED TCH-RM-LDC RATA-ABS3-AY RATA-ATR4-AY RATA-SYS4-AY RATA-OSI3-AY RATA-BCC1-AY RATA-TCU RATA-DTC RATA-CPR RATA-CPR-OSI RATA-SYS-AY RATA-OSIS-AY MEAS-COORDINATOR CC-DATA-COLLECTOR CC-RESULT-HANDLER DER-RESULTS-HANDLER CENTRAL-ALERTOR C_ALERTOR ME-MAINT-MSTER-TEST LME-OFF-LINE-TEST RATA_ABS3_AD RATA_ATR4_AD RATA_SYS4_AD RATA_OSI3_AD RATA_BBC1_AD ME_ASN1_CONV2 ME_BROADCAST_MGT
Meaning Extension/reduction handler. TCH-RM local data collector. Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Message coordinator on the O-CPR. Cumulative collector. Cumulative result collector. Discrete Event Register result handler. Central Alertor on the O-CPR. Alertor (not used). Master maintenance test module. Off-line test module. Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). ASN1 Convertor module 2. Broadcast bus maintenance module.
460 / 533
Dec 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 194 195 196 197 198
Hex AB AC AD AE AF B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF C0 C2 C3 C4 C5 C6
FMM-ID L4_CONVERGENCE RATA_ABS1_AE RATA_ATR1_AE RATA_SYS1_AE RATA_OSI1_AE RATA_ABS3_AE RATA_ATR4_AE RATA_SYS4_AE RATA_OSI3_AE RATA_BBC1_AE ME_CLK_MAINT_MSTR ME_BC_MAINT_MSTR ME_ALARM_CORRELATOR RATA_ABS1_AH RATA_ATR1_AH RATA_SYS1_AH RATA_OSI1_AH RATA_ABS3_AH RATA_ATR4_AH RATA_SYS4_AH RATA_OSI3_AH RATA_BBC1_AH CF_INTERPRETER FMM_INIT_G2 ME_PRELOADER_G2 ME_SYSTEM_NIT ME_PRELOADER
Meaning Convergence function for SMSCB. Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Clock maintenance module. Broadcast bus maintenance module. Alarm correlator module. Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Command file interpreter. FMM init module for Evolium A9120 BSC. Loader module for Evolium A9120 BSC. System init module. PreLoader module.
461 / 533
Dec 199
Hex C7
FMM-ID GPRSAP_FMM
Meaning GPRS module (similar to BSSAP for Telecom). Responsible for the handling of commands from the MFS except O&M; and paging messages. Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). BTS Extension reduction module. FM module for transmission. Load housekeeping on the DTC. Load housekeeping on the TCU. Module responsible for the GPRS signaling link between the MFS and the BSC. LAPD Layer 2 module on the DTC. GPRS module (similar to RFMGT for telecom). Responsible for relaying commands from/to RFMGT on the TCU and allocation call buffers on the TCU side. Configuration transmission module on the CPR. Configuration transmission module on the TCUs. GPRS module (similar to TSM in telecom). Responsible for central data for the GPRS. Located on the S_CPR pair. Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module).
200 201 202 203 204 205 206 207 208 209 210 212 213 214
C8 C9 CA CB CC CD CE CF D0 D1 D2 D4 D5 D6
RATA_ABS1_AP RATA_ATR1_AP RATA_SYS1_AP RATA_OSI1_AP RATA_ABS3_AP RATA_ATR4_AP RATA_SYS4_AP RATA_OSI3_AP RATA_BBC1_AP ME_BTS_EXT_RED FM_TRANS HSK_LOC_DTC HSK_LOC_TCU L3_DIS
215 216
D7 D8
DTC_LAPD_L2_FMM RF_GPRS_FMM
217 218 219
D9 DA DB
CONF_TRANS_CPR CONF_TRANS_LOCAL TSM_GPRS
220 221 222 223
DC DD DE DF
RATA_ABS3_AQ RATA_ATR4_AQ RATA_SYS4_AQ RATA_OSI3_AQ
462 / 533
Dec 224 225
Hex E0 E1
FMM-ID RATA_BBC1_AQ PAGING
Meaning Receive and Throw Away (test module). Paging module, responsible for the handling of paging messages located on the GPRSAPs DTCs. FM module for transmission. OSN_D test module. Housekeeping module 7. TSC Man Mahine Interface module. Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Receive and Throw Away (test module). Radio Measurement Stat. Radio Measurement Stat on each TCU. ABIS Resource Manager module. Connection control. RFM CCCH Handler. GPRS O&M; module, responsible for the O&M; between the MFS and the BSC. Hardware Configuration Management action scheduler Hardware Configuration Management Abis handler. Hardware Configuration Management BTS data handler. Hardware Configuration Management traffic resource handler. Hardware Configuration Management signaling resource handler. Hardware Configuration Management multiplexing control block.
232 233 234 235 241 242 243 244 245 246 247 248 249 250 251
E2 E3 E4 E5 F1 F2 F3 F4 F5 F6 F7 F8 F9 FA FB
FM_TRANS_CORR OSND_TEST ME_HSK_7 TSC_MMI RATA_ABS3_AT RATA_ATR4_AT RATA_SYS4_AT RATA_OSI3_AT RATA_BBC1_AT CENTRAL_RMS TCU_RMS_LDC ABIS_RM COCO RFM_CCCH GOM
252
FC
ME_ABIS_HCM_SCHED
253
FD
ME_ABIS_PORT_HDLR
254
FE
HCM_BTS_DATA_HDLR
255
FF
HCM_TRAF_RES_HDLR
256
100
HCM_SIGN_RES_HDLR
257
101
HCM_MCB_MAPPER
463 / 533
Dec 258 259
Hex 102 103
FMM-ID ME_HSK_ABIS CF_INTERPRETER_2
Meaning HSK ABIS module. 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) 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Type (Hex) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13
Error Name DUMMY SYSTEM_RESTART SYSTEM_REBOOT SYSTEM_RELOAD TRADEB_ERROR_CALL ME_INIT_GLOB_INIT ME_INIT_TAKE_OVER ME_INIT_TIME OUT L1_TRUNK_FAILURE DBASE_ACC_FAILURE NO_TRUNK_CELLS ILC_INIT_FAILURE ILC_DMA_UNDERRUN ILC_DMA_OVERRUN OBCI_HW_FLT OBCI_SW_FLT SSD_ACCESS_FAIL DATABASE_ERROR DATABASE_DATA_INC INC_MESS_DATA
464 / 533
Type (Dec) 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46
Type (Hex) 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E
Error Name ICLP_FAILURE BS_CH_RLS_FAIL CH_CONF_ERROR MEAS_TYPE_ERROR NO_LOCAL_REFERENCE_AVAILABLE WRONG_TMS_TYPE MASTER_FILE_CORRUPTED MASTER_FILE_DISK_ERROR ILC_DE_QUEUE_TWICE ILC_EN_QUEUE_TWICE ILC_NO_FR_CELL BOOTSTRAP_ERR NMI UNEXPECTED_INT INT_DATA_INC MTF_RSL_SMALL PR_DISABLE PR_RESTART OPEN_FILE_FLT READ_REC_FLT CLOSE_FILE_FLT FCB_LOC_TO_OMU WRONG_TCB_FIG ERR_LOAD_REQ ERR_ACK_NACK OUT_OF_STATE INTL_CATASTR
465 / 533
Type (Dec) 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 65 66 67 68 69 70 71 72 73 74
Type (Hex) 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 41 42 43 44 45 46 47 48 49 50
Error Name SPC_ALARM INTL_DATA_FLT GSM_0808_MSG_UNKNOWN GSM_0808_MSG_UNEXPEC GSM_0808_IEI_UNEXPEC GSM_0808_IE_FORM-ERR GSM_0808_IE_SEM_ERR GSM_0408_MSG_UNKNOWN GSM_0408_MSG_UNEXPECTED GSM_0408_PRTDISC_ERROR GSM_0408_IE_FORM_ERROR GSM_0408_IE_SEM_ERROR INTERNAL_MESSAGE_UNKNOWN INTERNAL_MESSAGE_UNEXPECTED TCHRM_NO_ANSWER TCHRM_RF_NO_ANSWER TRADEB_LBS CANCEL_EXPIRED_TIMER TOO_MANY_RESTARTS STAND_ALONE OBCI_LINK_HW_FAULT NETWORK_CONFIGURATIOM OBCI_LINK_OS INPUT_MAINT MAINT_SEQUENCE XMEM_FAULT XMCK_FAULT
466 / 533
Type (Dec) 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103
Type (Hex) 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67
Error Name GSM_0858_MS_UNEXPECTED GSM_0808_CIC_UNKNOWN CONF_CH_DISREP ERROR_REPORT_FROM_BTS RF_CHANNEL_RELEASE_FAILURE ASN1_DECODE_FAILURE ASN1_ENCODE_FAILURE SW_REPLACEMENT_DATA_ERROR INCORRECT_FILE_CONTENT UPDATE_SW_SYSREC_FAILURE READ_SW_SYSREC_FAILURE MAX_SMAP_RETRIES HEARTBEAT_ERROR HEARTBEAT_RESET NO_RESET_CIC_ACK DIVIDE_ERROR INV_TSS STA_EXC CIPHERING_DATA_INCONSISTENT UNKNOWN_CIRC_RECEIVED UNKNOWN_CIRC_TRANSMIT INVALID_ACCESS_TYPE EXPANSION_FAILED OBCI_RESET NO_MORE_DESCRIPTORS INVALID_DESCRIPTOR_TYPE INVALID_SELECTOR
467 / 533
Type (Dec) 104 187 188 189 191 192 679 680 681 682 683 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070
Type (Hex) 68 BB BC BD BF C0 2A7 2A8 2A9 2AA 2AB 41F 420 421 422 423 424 425 426 427 428 429 42A 42B 42C 42D 42E
Error Name LOG_LIN_CONV_ERR INVALID_OPCODE DOUBLE_FAULT SEGMENT_NOT_PRESENT GEN_PROT PAGE_FAULT C2_OVERFLOW C2_NULL_PTR PRCSS_END C2_RANGEFAIL C2_RTS NO_SUPVISION_PROCESS_CONTROL_BLOCK NO_APPLICATION_PROCESS_CONTROL_BLOCK PROCESS_CONTROL_BLOCK_OV1 PROCESS_CONTROL_BLOCK_OV2 DE_Q_TWICE NO_SUPV_STACK NO_TCB NO_MAIL LINK EN_Q_TWICE NO_APPLICATION_STACK INVALID_JOB_TYPE NO_TIMER_ML INVALID_MREQ_SIZE NO_UMEM_BLOCK NO_MESSAGE_BUFFER INVALID_MESSAGE_TYPE
468 / 533
Type (Dec) 1071 1072 1073 1074 1075 1076 1077 1078 1079 1097
Type (Hex) 42F 430 431 432 433 434 435 436 437 449
Error Name INVALID_FMM_ID INVALID_MESSAGE_PRIORITY INVALID_OSINF_TYPE INVALID_SCFI CFGI_NOT_SET SANITY_TIME OUT ILLEGAL_CALL STACK_CHECK INVALID_CLOCK_VALUE INVALID_MESSAGE_BASIC_TO_DESTINATION
Table 9: Error Types in Bytes 10 and 11 for Restart Alarms
469 / 533
29.2 Reset and Software Anomaly Alarms

This section describes the additional information provided by the following Reset alarm [33,1] and Software Anomaly alarms [33,4], [33,5], [39,18]. The Reset and Software Anomaly alarm byte definitions are shown in the following table. Byte Number 0-1
Description 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 to the internal switch.
This specifies the LCE-ID. The SBL type specifies the processor type. There is no longer a direct relationship between LCE-ID and CE number. Always 0. Not relevant. IP of the processor address where the fault happened. The first byte is the LSB. CS of the processor address where the fault happened. The first byte is the LSB. Not relevant. Not relevant. User Data 0. User data providing additional information. User Data 1. User data providing additional information. User Data 2. User data providing additional information. User Data 3. User data providing additional information.
3 4-5 6-7 8-9 10 - 11 12 - 13 14 - 15 16 - 17 18 - 19 20 - 21
Table 10: Additional Information for Reset and Software Anomaly Alarms
470 / 533
29.3 System Support Machine

This subsection describes the System Support Machine (SSM) Message Identification. DEC NO 65535 HEX NO FFFF MEANING This value simply indicates that the error occurs in an SSM.
Table 11: System Support Machine
29.4 Other BSC Alarms

This 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)) Format 1: 0 and 1 2 3 4 Format 2: Table 12: Additional Information for Alarm [33,3] Meaning FF CE identity 0 FF
See BSC/TC Alarm Additional Information (Section 29).
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 0 Meaning 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]
471 / 533
29.4.3 [34,3]
The additional information bytes for this alarm are defined in Tables 14 to 17, below. Test Results Explanation Byte Number 0 1 2 Meaning Test-segment Test-flt-type Test-raw-data (0) Test Not Executed Value 0 assigned Link Network Address Value 255 assigned Test Executed Test segment failure. See Table 15. Test fault type. See Table 16. -
3 4 5 6
Test-raw-data (1) Test-raw-data (2) Test-raw-data (3) Test-raw-data (4)
Switch Network Address. Link Type. Port Number. Test Result of TDM connection between port 0 and the port given in Raw Data (3). See Table 17. Test Result of TDM connection between port 1 and the port given in Raw Data (3). See Table 17. Test Result of TDM connection between port 2 and the port given in Raw Data (3). See Table 17. Test Result of TDM connection between port 3 and the port given in Raw Data (3). See Table 17. Test Result of TDM connection between port 4 and the port given in Raw Data (3). See Table 17. Test Result of TDM connection between port 5 and the port given in Raw Data (3). See Table 17. Test Result of TDM connection between port 6 and the port given in Raw Data (3). See Table 17. Test Result of TDM connection between port 7 and the port given in Raw Data (3). See Table 17. Test Result of TDM connection between port 8 and the port given in Raw Data (3). See Table 17.
Test-raw-data (5)
Test-raw-data (6)
Test-raw-data (7)
10
Test-raw-data (8)
11
Test-raw-data (9)
12
Test-raw-data (10)
13
Test-raw-data (11)
14
Test-raw-data (12)
472 / 533
Test Results Explanation Byte Number 15 Meaning Test-raw-data (13) Test Not Executed Test Executed Test Result of TDM connection between port 9 and the port given in Raw Data (3). See Table 17. Test Result of TDM connection between port A and the port given in Raw Data (3). See Table 17.
16
Test-raw-data (14)
Table 14: Additional Information for Alarm [34,3]
Test Results Explanation Byte Number 17 Meaning Test-raw-data (15) Test Not Executed Test Executed Test Result of TDM connection between port B and the port given in Raw Data (3). See Table 17. Test Result of TDM connection between port C and the port given in Raw Data (3). See Table 17. Test Result of TDM connection between port D and the port given in Raw Data (3). See Table 17. Test Result of TDM connection between port E and the port given in Raw Data (3). See Table 17. Test Result of TDM connection between port F and the port given in Raw Data (3). See Table 17.
18
Test-raw-data (16)
19
Test-raw-data (17)
20
Test-raw-data (18)
21
Test-raw-data (19)
Test Segment 1
Description Get channel, send a request of MAINTENANCE_PACKET to find a free channel. Wait for 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 modify mask, send maintenance interrupt and maintenance command to change status of ports.
473 / 533
Test Segment 2
Description Send a request of tunnel word for maintenance command CH0, with set maintenance busy and alarm shutoff, test if it is accepted. Send a request of tunnel word for maintenance interrogate CH0, test if it is accepted and wait for message.
Get channel, send a request of MAINTENANCE_PACKET with maintenance select on port under test. 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 and wait for message.
Send a request of MAINTENANCE_PACKET with normal select on port under test. Wait for NACK. Send a request of tunnel word for maintenance command CH0 with reset maintenance busy. Test if it is accepted. Send a request of tunnel word for maintenance interrogate CH0, test if it is accepted and wait for message.
8 9 10
Send a packet with seven interrogates. Verify that the pointer correctly decremented. Send packet of escape words. The transmitted and received packet are compared. Set a path, send a packet of escape words. The transmitted and received packet is compared. Re-select path. Wait for NACK. Send maintenance packet with maintenance select on port under test. Wait for NACK and write violation alarm.
11 12
13
Send packet of escape words. The transmitted and received packets are compared (TDM bus). Set up permanent path via test depth, towards own OBCI, with test pattern attached. Try to set up a temporary path towards the permanent path. This should be rejected. 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.
14 15 16
Table 15: Test Segment Results for Alarm [34,3], [51,1] (Byte 0) and [51,2] (One Byte Only)
474 / 533
Fault Type 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
Description No errors. Not accepted tunnel word interrogate. timeout tunnel word interrogate. Not accepted tunnel word command. Received tunnel alarm. Message out of sequence. No channel available. Not accepted tunnel word interrogate. All channels NACKed, maintenance packet not sent. timeout for msg 158. Wrong pointer received. Timeout for msg 157. Not accepted tunnel word command. Not accepted tunnel word interrogate. Wrong pointer received. Timeout for msg 157. No channel available. Timeout no event msg received. Timeout for msg second path. Timeout for msg first path. Not accepted tunnel word command. Not accepted tunnel word interrogate. Wrong pointer received. Timeout for msg 157. No NACK received but 2 EOP. Timeout no NACK received. Not accepted tunnel word command. Not accepted tunnel word interrogate.
475 / 533
Fault Type 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
Description Wrong pointer received. Timeout for msg 157. Wrong pointer decrement after EOP. Wrong pointer decremented before EOP. Timeout for msg 158. Wrong pkt received before EOP. Wrong pkt received after EOP. Timeout for msg 158. All channels NACKed, maintenance pkt not sent. Wrong pkt received after EOP. Wrong pkt received before EOP. Timeout for msg 158. Timeout for msg 158. Timeout for all msg. Timeout for msg 151 and msg second path. Timeout for msg 151 and msg first path. Timeout for msg 151. Timeout for msg first path and second. Timeout for msg second path. Timeout for msg first path. Timeout wrong sequence message. Values incompatible with Z_TUNNEL_type, Z_TEST_PORT.B_side and Z_TEST_PORT.B_depth. Wrong sequence message Result of Maintenance Interrogate: ACI=0 - all channels idle MB=0 - maintenance busy AS=0 - alarm shutoff.
50 51
52
ACI=0 MB=0 AS=1
476 / 533
Fault Type 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76
Description ACI=0 MB=1 AS=0 ACI=0 MB=1 AS=1 ACI=1 MB=0 AS=0 ACI=1 MB=0 AS=1 ACI=1 MB=1 AS=0 ACI=1 MB=1 AS=1 TDM test bus fail, resource seize fail. TDM bus fail. Overall timer has expired. Overall timer has expired. Cable test has failed. Wrong PTR decremented after EOP. Wrong PTR decremented after EOP. Timeout for msg 158. Plug Test Error. DCDC State Change. Send tunnel word not accepted. Timeout msg for msg 157. Processor does not control BCLA. BCLA: wrong ID. BCLA: this is not the rack BCLA. BCLA: this is not the sys BCLA. BCLA: the write register has failed. BCU pattern test has failed.
477 / 533
Fault Type 77 78
Description BCU fail bit set. 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 High
Test Result 0 1
Explanation Connection not tested. Connection tested. Test OK. Bad test packet and no EOPS received. Bad test packet and EOPS received. Timeout.
Low
0 1 2 3
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 Not applicable 0 1 2 3 4 5 6 7 8 9 Test-raw-data (0) Test-raw-data (1) Test-raw-data (2) Test-raw-data (3) Test-raw-data (4) Test-raw-data (5) Test-raw-data (6) Test-raw-data (7) Test-raw-data (8) Test-raw-data (9) Number of unsuccessful tunnels. Number of successful tunnels. Number of tested tunnels. Number of tunnels. Meaning Test Results Explanation Test Successful. Value 255 assigned. Test unsuccessful. Number of times a routine test has run.
478 / 533
29.4.5 [35,0]
The additional information bytes for this alarm are defined in the following table. Byte Number 0 Meaning (Intel notation - 1st byte is LSB) 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]
479 / 533
29.4.6 [35,2]
The additional information bytes for this alarm are defined as shown below. Byte Number 0 and 1 2 and 3 Meaning (Intel Notation - 1st byte is LSB) DPC of the MSC (same as the alarm number). SSF of the MSC.
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 bytes for alarm layout 2 are defined in Table 22. Table 23 shows an example of additional information for Alarm [35,3]. Word Number 0 Meaning (Intel Notation - 1st byte is LSB) 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 SLC different 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
Word Number 5
Meaning (Intel Notation - 1st byte is LSB) OPC received. (OPC is described in section 15.2 of ITU-T Rec. Q704).
SSF received. (SSF is described in section 14.2 of ITU-T Rec. Q704).
7 8 9
DPC expected (Value fromDLS). OPC expected (Value from DLS). SSF expected (Value from DLS).
Table 21: Additional Information for Alarm [35,3], Layout 1
Word Number 0 2 - 18
Meaning (Intel Notation - 1st byte is LSB) Value = 10: Changeback refused (described in ITU-T Rec. Q704). Value = FF
Table 22: Additional Information for Alarm [35,3], Layout 2
Data 02 00 0c 0c 01 00 11 00 31 02 0a 02 0c 00 31 02 0a 02 0c 00
Word 0 1 2 3 4 5 6 7 8 9
Value 0002H 0C0CH 0001H 0011H 0231H 020AH 000CH 0231H 020AH 000CH
Meaning invalid OPC or SLC= 0CH SSF= 0CH SI= SNTM MSG Type = SLTM* DPC received OPC received SSF received DPC expected OPC expected SSF expected
Table 23: Example of Additional Information for Alarm [35,3] * SLTM = Signaling Link Test Message
481 / 533
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 definition for 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 0 1 2 to 9 Meaning (Intel Notation - 1st byte is LSB) Logical Control Element identity where link resides. DTN identity where link resides. Null value.
29.4.10 [36,14]
The additional information byte for this alarm is defined in below. Byte Number 0 Meaning 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 0 Meaning 0: PLL out of range. 1: clock failure. Table 26: Additional Information for Alarm [36,15]
482 / 533
29.4.12 [38,0]
The additional information byte for this alarm is defined in below. Byte Number 0 Meaning Display of the modem signals.
29.4.13 [38,2]
The additional information bytes for this alarm are defined below. Byte Number 0 1 and 2 3 and 4 Meaning Identification of the link where the problem occurred. Identification of the channel where the problem occurred. Description of the problem.
29.4.14 [42,3]
The additional information byte for this alarm is defined below. Byte Number 0 Meaning Cause of the reset procedure: 00: reset from MSC. 01: MSC communication lost or internal reason. Table 29: Additional information for Alarm [42,3]
483 / 533
29.4.15 [42,5]
The additional information bytes for this alarm are defined in the following table. Byte Number 0 Meaning Alarm cause: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 BSC reload/reboot CPRA reload/reboot BSC restart CPRA restart CPRA takeover MSC unavailable Reset from MSC Overload from MSC Timer T6 expired Timer T6 expired MSC available Timer T2 expired Overload from BTS TCUA overload DTC overload Sign link congestion.
Timer T6 indicates an MSC originated end of an overload period, the system returns to normal. Timer T2 indicates a BTS originated end of an overload period, the system returns to normal. 1-2 3-4 : : : LAC. Cell Id. : : : #FF if not defined. #FF if not defined. : For N (40) cells :
484 / 533
Byte Number 4N-3 to 4N-2 4N-1 to 4N
Meaning LAC. Cell Id. #FF if not defined. #FF if not defined.
29.4.16 [42,6]
The additional information bytes for this alarm are defined in the following table. Byte Number 0 Meaning Alarm cause: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 BSC reload/reboot CPRA reload/reboot BSC restart CPRA restart CPRA takeover MSC unavailable Reset from MSC Overload from MSC Timer T6 expired Timer T6 expired MSC available Timer T2 expired Overload from BTS TCUA overload DTC overload Sign link congestion.
Timer T6 indicates an MSC-originated end of an overload period, the system returns to normal. Timer T2 indicates a BTS-originated end of an overload period, the system returns to normal. 1-2 LAC. #FF if not defined.
485 / 533
Byte Number 3-4 5-6
Meaning Cell Id. Current RACH. This information gives the reason a message was sent and the new access class values. The RACH parameter is specified using 16 bits. The right hand bit corresponds to Access class 0. Value 10 for an Access class specifies emergency calls only. Value 0 for an Access class specifies that calls are authorized. #FF if not defined.
7-8
Starting RACH. This information gives the reason a message was sent and the new access class values. The RACH parameter is specified using 16 bits. The right hand bit corresponds to 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-7 to 8N-6 8N-5 to 8N-4 8N-3 to 8N-2
: : : LAC. Cell Id. Current RACH.
: For N (40) cells : #FF if not defined. #FF if not defined.
This information gives the reason a message was sent and the new access class values. The RACH parameter is specified using 16 bits. The right hand bit corresponds to 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 class values. The RACH parameter is specified using 16 bits. The right hand bit corresponds to 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
29.4.17 [42,9]
The additional information bytes for this alarm are defined below. Byte Number 0 1 2-3 4 5 6-13 Meaning SBL unit type SBL unit number SBL type SBL number SBL sub-number Overload level buffer pool 1-8 00 = No Overload 01 = SCCP Overload 02 = Overload Level 1 03 = Overload Level 2 14 Processor occupancy (%)
29.4.18 [42,12]
The additional information bytes for this alarm are defined below. Byte Number 0-1 2-3 : 4N-4 to 4N-3 4N-2 to 4N-1 Meaning LAC of cell CI of cell : For N number of cells lost (60 maximum) LAC of cell CI of cell
487 / 533
29.4.19 [42,13]
The additional information bytes for this alarm are defined below. Byte Number 0 Meaning Alarm cause: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 BSC reload/reboot CPRA reload/reboot BSC restart CPRA restart CPRA takeover MSC unavailable Reset from MSC Overload from MSC Timer T18 expired MSC available End of reset procedure Not applicable Not applicable Not applicable DTC overload CPR overload Signaling link congestion Not applicable Overload parameter modify Cumulative counter null
Timer T18 indicates a BSC-originated end of an overload period, the system returns to normal.
488 / 533
Byte Number 1-2
Meaning This information gives the reason a message was sent, and the new access class values on System Level GSM TS 04.08. The RACH parameter is specified using 16 bits. The right hand bit corresponds to Access class 0. Bit 0..9, 11..15 = 0 for an Access class means that Access control class is not barred on 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 that belong to 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 Selection Priority Normal Barred Low Low Status for Cell Reselection Normal Barred Normal Normal
0 0 1 1
0 1 0 1
29.4.20 [43,0] to [43,3]

The additional information bytes for these alarms are defined below. Byte Number 0-1 2-3 4-5 6 7 Meaning Number of available BCCH. Number of available SDCCH. Number of available TCH. TRX identity. Current TEI (RSL Number) BEQNumber Baseband State: 0 = Not available 1 = Available #FF if no RSL is mapped.
8 9
489 / 533
Byte Number 10
Meaning Radio Part State: 0 = Not available 1 = Available
: : : 5N + 1 5N + 2
: : : TRX identity. Current TEI (RSL number) BEQ number. Baseband State:
: For N configured TRXs (Maximum 8). : #FF if no RSL is mapped.
5N + 3 5N + 4
0 = Not available 1 = Available
5N + 5
Radio Part State:
0 = Not available 1 = Available
5N + 6 5N + 7 5N + 8 5N + 9 5N + 10 to 5N + 11 5N + 12 : : : 9N + 6 9N + 7 9N + 8 to 9N + 9 9N + 10 CU number. BEQ number. ARFCN used.
Separator #FF Separator #FF -
ARFCN available. : : : CU number. BEQ number. ARFCN used. ARFCN available.
: For N configured TRXs (Maximum 8). -
Table 35: Additional Information for Alarms [43,0] to [43,3]
490 / 533
29.4.21 [43,4]
The additional information bytes for this alarm are defined in the following table. Byte Number 0 Meaning Alarm cause: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 BSC reload/reboot CPRA reload/reboot BSC restart CPRA restart CPRA takeover Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable Timer T2 expired Overload from BTS TCUA overload Not applicable Not applicable Not applicable Bar/unbar cell request Overload parameter modify TCC null
Timer T2 indicates a BSC-originated end of an overload period, the system returns to normal.
491 / 533
Byte Number 1-2
Meaning This information gives the reason a message was sent, and the new access class values on Cell Level (Dynamic RACH) GSM TS 04.08. The RACH parameter is specified using 16 bits. The right hand bit corresponds to Access class 0. Bit 0..9, 11..15 = 0 for an Access class means that Access control class is not barred on 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 belong to 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 Selection Priority Normal Barred Low Low
Status for Cell Reselection Normal Barred Normal Normal
0 0 1 1
0 1 0 1
29.4.22 [44,0], [44,5] and [44,6]

The additional information bytes for these alarms are defined below. Byte Number 0+1 2+3 Meaning Abis Error Code. Error Number (that is, Record Number).
Table 37: Additional Information for Alarms [44,0], [44,5] and [44,6]
492 / 533
29.4.23 [44,3]
The additional information bytes for this alarm are defined below. Byte Number 0+1 2+3 4+5 Meaning Abis Error Code. File Number. Error Number (that is, Record Number).
29.4.24 [46,0], [46,1] and [46,3]

The additional information bytes for these alarms are defined below. Byte Number 0+1 2+3 Meaning Twin File number. 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 0 1 2 3 4 5 6 7
Meaning CBC Outgoing Connection association prematurely terminated internally. CBC O/G association prematurely terminated externally. Network connection refused. Network connection timeout. BIND parameters not populated. CBC O/G association setup timeout. CBC O/G association refused - not entitled. CBC O/G association refused - invalid Id or password.
493 / 533
29.4.26 [49,0]
The additional information bytes for this alarm are defined below. Byte Number 0+1 2+3 4+5 6+7 Meaning LAC of Cell. CI of Cell. Threshold Value 1. Threshold Value 2.
29.4.27 [49,1]
The additional information bytes for this alarm are defined as shown below. Byte Number 0+1 2+3 4+5 6+7 8+9 10 + 11 Meaning LAC of Cell. CI of Cell. Threshold Value 1. Threshold Value 2. SBL type (DTC). SBL number (DTC number).
494 / 533
29.4.28 [49,2] and [49,3]

The additional information bytes for these alarms are defined as follows. Byte Number 0+1 2+3 4+5 6+7 8+9 10 + 11 12 + 13 14 + 15 Meaning LAC of Cell. CI of Cell. Threshold Value 1. Threshold Value 2. SBL type (DTC). SBL number (DTC number). Transceiver identity. 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 0-1 2 Meaning Network address. 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 hardware logic. 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]
495 / 533
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 to analyze the alarm information correctly. 1. The first block of additional information indicates the network address of switch, the link states and, if required, the necessary fault reason. 2. The subsequent blocks of additional information indicate the test results of the 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. The table contains the relationships for all completely equipped racks and the RIT position in the rack, shelf and slot. Byte Number 0-1 2 - 17
Meaning Network Address. Bits 3-0: Fault type 0= No Reason. 1= Write Violation. Several unsynchronized write accesses occurred within a switch elements internal hardware logic. This caused a mismatch, generating a transient write violation alarm. 2= Write Violation Overflow. Several unsynchronized write accesses occurred within a switch elements internal hardware logic. This caused a mismatch, generating a write violation overflow alarm. 3= Loss of Sync. The switch detected a loss of synchronization with the internal 4 Mbit/s signal. All calls through the switch are lost. An alarm is sent for the switch indicating a permanent loss of synchronization. 4= Loss of Sync Overflow. The switch detected a large number of transient losses of synchronization with the internal 4 Mbit/s signal within a specified time frame. 5= HW Fault. Hardware failure detected. 6= Init-Ini-Fail. A link initialization failed during an initialization action on a switch SBL. 7= Operator Request. An operator request has failed. Bits 7-4: Link state 0= In Service 1= Out of service 2= Autonomous out of service 3= Undefined 4= Faulty In Service 5= Alarm shutoff 6= 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, and so on.
496 / 533
If additional blocks of information are displayed, each one indicates the results of a failed link test. Refer to the table below. Byte Number 0 1 2-3 4 - 19 Meaning Test Segment Test-Fault-type Link-Network-Address TDM-Test-Results Descriptions See Test-Segment Table 15. See Test-Fault-Type Table 16. 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 execute or a timeout was received. In this case, the TDM-Test-Results values will be set to #FF. Byte Number 4 Test Results Explanation Test Result of TDM connection between port 0 and the port given by the Link Network Address. See Table 48 for detailed TDM test results. Test Result of TDM connection between port 1 and the port given by the Link Network Address. See Table 48 for detailed TDM test results. Test Result of TDM connection between port 2 and the port given by the Link Network Address. See Table 48 for detailed TDM test results. Test Result of TDM connection between port 3 and the port given by the Link Network Address. See Table 48 for detailed TDM test results. Test Result of TDM connection between port 4 and the port given by the Link Network Address. See Table 48 for detailed TDM test results. Test Result of TDM connection between port 5 and the port given by the Link Network Address. See Table 48 for detailed TDM test results. Test Result of TDM connection between port 6 and the port given by the Link Network Address. See Table 48 for detailed TDM test results. Test Result of TDM connection between port 7 and the port given by the Link Network Address. See Table 48 for detailed TDM test results. Test Result of TDM connection between port 8 and the port given by the Link Network Address. See Table 48 for detailed TDM test results. Test Result of TDM connection between port 9 and the port given by the Link Network Address. See Table 48 for detailed TDM test results. Test Result of TDM connection between port A and the port given by the Link Network Address. See Table 48 for detailed TDM test results. Test Result of TDM connection between port B and the port given by the Link Network Address. See Table 48 for detailed TDM test results.
10
11
12
13
14
15
497 / 533
Byte Number 16
Test Results Explanation Test Result of TDM connection between port C and the port given by the Link Network Address. See Table 48 for detailed TDM test results. Test Result of TDM connection between port D and the port given by the Link Network Address. See Table 48 for detailed TDM test results. Test Result of TDM connection between port E and the port given by the Link Network Address. See Table 48 for detailed TDM test results. Test Result of TDM connection between port F and the port given by the Link Network Address. See Table 48 for detailed TDM test results.
17
18
19
Table 47: TDM Test Result Byte Descriptions for Alarm [51,1] and [51,2]
Nibble High
Test Result 0 1
Explanation Connection not tested. Connection tested. Test OK. Bad test packet and no EOPS received. Bad test packet and EOPS received. Timeout.
Low
0 1 2 3
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 sort of 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. The table contains the relationships for all completely equipped racks and the RIT position in the rack, shelf and slot.
498 / 533
29.4.31 [51,2]
The additional information bytes for this alarm are defined below. Test Results Test Segment Test Fault Type Test Raw Data Byte Number one byte only one byte only 0+1 2+3 4 - 19 Switch Network Address. Link Network Address. TDM Meaning Byte Description See Table 15. See Table 16. For relation of Switch Network Address to board, see Table 51. Associated port is under test. For TDM Test Result Byte description, see Table 47. Table 49: Additional Information for Alarm [51,2]
Test Result Test Segment Test Fault Type Test Raw Data
Unsuccessful (some failures) 13 60 H00 H10 H10 H10 H45 H10 H10 H10 H00 H12 H10 H10 H40 H10 H10 H10 H13 H10 H10 H10
Unsuccessful (tests not executed) 0 0 H00 HFF HFF HFF H45 HFF HFF HFF H00 HFF HFF HFF H40 HFF HFF HFF HFF HFF HFF HFF
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 not execute or a timeout was received. In this case, the TDM-Test -Results values 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 table contains the relationships for all completely equipped racks and the RIT position in the rack, shelf and slot.
499 / 533
For detailed information about BSC configurations, refer to the (BSC Cabinet and Subrack Description). IAD/NA (Hex) 0000 0000 0001 0002 0003 0004 0005 0008 0009 000A 000B 000C 000D 000E 000F 0010 0010 0011 0012 0013 0014 0015 0016 0017 0020 0020 RIT (Type) CPRCAB SWCHAB CPRCAB CPRCAC CPRCAC CPRCAA CPRCAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA TCUC SWCHAB TCUC TCUC TCUC TCUC TCUC TCUC TCUC SWCHAB DTCC Position (Rack.Shelf.Slot) 1.8.17 1.8.37 1.8.19 1.8.21 1.8.25 1.8.29 1.8.31 1.7.1 1.7.3 1.7.5 1.7.7 1.7.9 1.7.11 1.7.13 1.7.15 1.7.29 1.7.45 1.7.31 1.7.33 1.7.35 1.7.37 1.7.39 1.7.41 1.7.43 1.6.9 1.6.13
500 / 533
IAD/NA (Hex) 0021 0022 0023 0024 0025 0026 0027 0030 0030 0031 0032 0033 0034 0035 0036 0037 0040 0050 0060 0070 0088 0089 008A 008B 008C 008D 008E 008F
RIT (Type) DTCC DTCC DTCC DTCC DTCC DTCC DTCC SWCHAB DTCC DTCC DTCC DTCC DTCC DTCC DTCC DTCC SWCHAB SWCHAB SWCHAB SWCHAB SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA
Position (Rack.Shelf.Slot) 1.6.15 1.6.17 1.6.19 1.6.23 1.6.25 1.6.27 1.6.29 1.6.41 1.6.45 1.6.47 1.6.49 1.6.51 1.6.55 1.6.57 1.6.59 1.6.61 1.8.39 1.7.47 1.6.11 1.6.43 1.8.45 1.8.47 1.8.49 1.8.51 1.8.53 1.8.55 1.8.57 1.8.59
501 / 533
IAD/NA (Hex) 0098 0099 009A 009B 009C 009D 009E 009F 00A8 00A9 00AA 00AB 00AC 00AD 00AE 00AF 00B8 00B9 00BA 00BB 00BC 00BD 00BE 00BF 00C8 00C9 00CA 00CB
RIT (Type) SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA
502 / 533
IAD/NA (Hex) 00CC 00CD 00CE 00CF 00D8 00D9 00DA 00DB 00DC 00DD 00DE 00DF 00E8 00E9 00EA 00EB 00EC 00ED 00EE 00EF 00F8 00F9 00FA 00FB 00FC 00FD 00FE 00FF
RIT (Type) SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA
503 / 533
IAD/NA (Hex) 0100 0100 0101 0102 0103 0104 0105 0106 0107 0108 0109 010A 010B 010C 010D 010E 010F 0110 0110 0111 0112 0113 0114 0115 0116 0117 0120 0120
RIT (Type) SWCHAB TCUC TCUC TCUC TCUC TCUC TCUC TCUC TCUC SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA TCUC SWCHAB TCUC TCUC TCUC TCUC TCUC TCUC TCUC SWCHAB DTCC
504 / 533
IAD/NA (Hex) 0121 0122 0123 0124 0125 0126 0127 0130 0130 0131 0132 0133 0134 0135 0136 0137 0140 0150 0160 0170 0200 0200 0201 0202 0203 0204 0205 0206
RIT (Type) DTCC DTCC DTCC DTCC DTCC DTCC DTCC SWCHAB TCUC TCUC TCUC TCUC TCUC TCUC TCUC TCUC SWCHAB SWCHAB SWCHAB SWCHAB TCUC SWCHAB TCUC TCUC TCUC TCUC TCUC TCUC
505 / 533
IAD/NA (Hex) 0207 0208 0209 020A 020B 020C 020D 020E 020F 0210 0210 0211 0212 0213 0214 0215 0216 0217 0220 0220 0221 0222 0223 0224 0225 0226 0227 0230
RIT (Type) TCUC SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA TCUC SWCHAB TCUC TCUC TCUC TCUC TCUC TCUC TCUC SWCHAB DTCC DTCC DTCC DTCC DTCC DTCC DTCC DTCC SWCHAB
506 / 533
IAD/NA (Hex) 0230 0231 0232 0233 0234 0235 0236 0237 0240 0250 0260 0270 0300 0300 0301 0302 0303 0304 0305 0306 0307 0308 0309 030A 030B 030C 030D 030E
RIT (Type) DTCC DTCC DTCC DTCC DTCC DTCC DTCC DTCC SWCHAB SWCHAB SWCHAB SWCHAB TCUC SWCHAB TCUC TCUC TCUC TCUC TCUC TCUC TCUC SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA
507 / 533
IAD/NA (Hex) 030F 0310 0310 0311 0312 0313 0314 0315 0316 0317 0320 0320 0321 0322 0323 0324 0325 0326 0327 0330 0330 0331 0332 0333 0334 0335 0336 0337
RIT (Type) SWCHAA SWCHAB TCUC TCUC TCUC TCUC TCUC TCUC TCUC TCUC SWCHAB DTCC DTCC DTCC DTCC DTCC DTCC DTCC DTCC SWCHAB TCUC TCUC TCUC TCUC TCUC TCUC TCUC TCUC
508 / 533
IAD/NA (Hex) 0340 0350 0360 0370 0400 0400 0401 0402 0403 0404 0405 0406 0407 0408 0409 040A 040B 040C 040D 040E 040F 0410 0410 0411 0412 0413 0414 0415
RIT (Type) SWCHAB SWCHAB SWCHAB SWCHAB SWCHAB TCUC TCUC TCUC TCUC TCUC TCUC TCUC TCUC SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAB TCUC TCUC TCUC TCUC TCUC TCUC
509 / 533
IAD/NA (Hex) 0416 0417 0420 0420 0421 0422 0423 0424 0425 0426 0427 0430 0430 0431 0432 0433 0434 0435 0436 0437 0440 0450 0460 0470 0500 0500 0501 0502
RIT (Type) TCUC TCUC SWCHAB DTCC DTCC DTCC DTCC DTCC DTCC DTCC DTCC SWCHAB DTCC DTCC DTCC DTCC DTCC DTCC DTCC DTCC SWCHAB SWCHAB SWCHAB SWCHAB TCUC SWCHAB TCUC TCUC
510 / 533
IAD/NA (Hex) 0503 0504 0505 0506 0507 0508 0509 050A 050B 050C 050D 050E 050F 0510 0510 0511 0512 0513 0514 0515 0516 0517 0520 0520 0521 0522 0523 0524
RIT (Type) TCUC TCUC TCUC TCUC TCUC SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA SWCHAA TCUC SWCHAB TCUC TCUC TCUC TCUC TCUC TCUC TCUC SWCHAB DTCC DTCC DTCC DTCC DTCC
511 / 533
IAD/NA (Hex) 0525 0526 0527 0530 0530 0531 0532 0533 0534 0535 0536 0537 0540 0550 0560 0570
RIT (Type) DTCC DTCC DTCC SWCHAB TCUC TCUC TCUC TCUC TCUC TCUC TCUC TCUC SWCHAB SWCHAB SWCHAB SWCHAB
Position (Rack.Shelf.Slot) 3.3.25 3.3.27 3.3.29 3.3.41 3.3.45 3.3.47 3.3.49 3.3.51 3.3.53 3.3.55 3.3.57 3.3.59 3.4.27 3.4.59 3.3.11 3.3.43
Table 51: Relationship IAD/NA to RIT and Position
512 / 533
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 0 Meaning TEST-RAW-DATA (0) TEST-RAW-DATA (1) TEST-RAW-DATA (2) TEST-RAW-DATA (3) TEST-RAW-DATA (4) TEST-RAW-DATA (5) TEST-RAW-DATA (6) TEST-RAW-DATA (7) TEST-RAW-DATA (8) TEST-RAW-DATA (9) Number of unsuccessful tunnels. Number of successful tunnels. Number of tested tunnels. Number of tunnels. Test Results Explanation Value 255 assigned. Number of times a routine test has run.
Table 52: Additional Information for Alarm [51,3] In the unsuccessful cases, the decoding of the byte information is described in the Link/Switch Test Results section of the Operations & Maintenance Reference Guide.
513 / 533
29.4.33 [52,1], [52,5] and [52,7]

The additional information bytes for these alarms are defined below. Byte Number 0-1 Value 0 1 2 3 4 5 Meaning Local clock failure. Reference selector failure. PLL out of range (POOR). Absence of own clock (CLKABS). Watchdog timer expiry (WD). 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 0-1 Value 0 Meaning LOS detected.
Table 54: Additional Information for Alarms [53,0], [53,1], [53,3], [53,4], [53,6] and [53,7]
514 / 533
29.4.35 [53,2]
The additional information bytes for this alarm is defined as follows. Byte Number 0-1 Value 0 Meaning DMA overrun detected by the Broadcast Control Unit in processors. DMA underrun detected by the BCU in processors.
29.4.36 [53,5] and [53,8]

The additional information bytes for these alarms are defined below. Byte Number 0-1 Value 0 1 Meaning CRC detected on broadcast bus to SBL. FTL detected on broadcast bus to SBL.
Table 56: Additional Information for Alarms [53,5] and [53,8]
515 / 533
29.5 TC Alarms
This 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 Recovery Level Error Type Filename SIZE 1 DESCRIPTION The action taken by the TSC to recover from the error (RESET/RESTART/REPORT/NONE). The actual error type which is reported by the TSC modules. Zero-terminated string that gives the filename of the module which reported the error. Line number in the file where the error was risen. Parameter with extra debugging information. Parameter with extra debugging information.
1 20
SPARE Line nbr Param1 Param2
2 4 4 4
29.5.3 [73,022] to [73,216]

The alarm numbers are defined as follows. HW boards SBLs Provided in the Alarm RITS Provided in the Alarm Alarm Nbr Board BIUA HW Boards BSC_ADAPT BIUA 00 Table 58: Additional Information for Alarm [73,022] to [73,216] Interface Error 1..8 BSI Interface
516 / 533
29.5.4 [74,20] to [74,202]

The alarm numbers are defined as follows. HW boards SBLs Provided in the Alarm RITS Provided in the Alarm Alarm Nbr Board G2 BTS HW BTS_ADAPT BOARDS SMBI Master 00 SMBI Slave 20 uBTS HW BOARDS SMFG 00 A9100 BTS HW BOARDS SUM 00 Interface Error 11..16 21..26 11,12,16 11 BSI Interface
Table 59: Additional Information for Alarm [74,20] to [74,202]
517 / 533
29.5.5 [75,20] to [75,247]

The alarm numbers are defined below. HW boards SBLs Provided in the Alarm RITS Provided in the Alarm Alarm Nbr Board Interface Error 10 20 30 40 10 20 30 40 02 ATER Interface 1st 2nd 3rd 4th Tributary Interface 1st 2nd 3rd 4th
Alcatel SM2M HW Boards TC G2
ASMB
00 -
ASMC
00 -
Alcatel TRCU TC G2
TC-ADAPT
ATBX
00 -
Table 60: Additional Information for Alarm [75,20] to [75,417]
518 / 533
29.5.6 MT120 Board Equipment Reset

The equipment reset/reset fields are described below. Field Name Size (Bytes) + Type One Unsigned Character. Meaning
Restart Counter value
Autonomous/Operator
This parameter indicates if the reset occurs because of an operator request or autonomously. Range 60...80 is MT120 specific. The reset structure depends on the hardware type. The hardware type MT120 is mapped onto a range of Error Type from 60 to 80. All the error types which do not belong to this set have the following format, see Table 63.
Error Type
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 One Unsigned Character. Meaning
Program Identity User Data Segment
Program identity of the process which reports the alarm. User Data Segment.
Table 62: MT120 Board, Range >80
519 / 533
29.5.8 MT120 Board, Range <80

The following table defines the error types for the MT120 board with a range less than 80. Error Type Type Number 60 Recovery Level Reset Description Action Additional Info None.
Power-on
When the MT120 is powered on, this alarm is built.
All memory which belongs to the application is cleared, is set to 00. The startup is done with the default configuration. A reset is always triggered. In the reset sequence, the last correct software (1 of 3 possibilities) is activated. All memory is cleared. The configuration is saved into flash memory otherwise. If corrupted, the default configuration is applied.
OTP hardware watchdog
61
Reset
The HW watchdog timer has expired caused by a loop somewhere in the code.
OTP external or internal scenario failure OTP lack of internal resources
62
Reset/Restart An external or internal scenario has failed due to a timeout expiration. Reset/Restart This error occurs, when there is no memory free for the applications. Reset/Restart An exception has occurred, a detailed list is given in the additional information, see Table 64. Reset/Restart An error has occurred in the generated code. Reset/Restart An error has occurred in the DSP. Reset A hardware error has been detected by the auto-tests.
A reset/restart is triggered, See Table the OTP comes back to an 64 operational state using the saved configuration. A buffer is built after processor reset/restart.
63
OTP exception
64
OTP SDT crash
65
DSP post-mortem
66
MT120 auto-test failure
67
Table 63: MT120 Board, Error Types, Range <80
520 / 533
29.5.9 MT120 Board, Error Types

The following table describes the additional information given for the MT120 board error types. Error Type OTP external or internal scenario failure. Taskname Size 4 Description Task name in ASCII which has caused the auto-restart/auto-reset. Internal Message Identifier to identify the internal scenario. External reference number (Ater Mux or MMI) to identify the scenario, 0 is for autonomous. Scenario message identifier used to identify the external or autonomous scenario. 0 1 2 4 5 Failure Description 1 01 FF OTP external or internal scenario failure. Taskname 4 Operator scenario from the OMC-R Operator from the BSC terminal Operator from the TC terminal Autonomous action Unknown Indicates three successful auto-restarts. No information.
MID Reference
2 2
Scenario id
Origin of action
Task name in ASCII which has caused the auto-restart/auto-reset. 0 1 2 Message buffer Memory allocation Memory re-allocation
Memory region
Memory size Stack Info
4 60
The requested memory size which could not be served. The information is taken from the stack.
521 / 533
Error Type OTP exception Taskname
Size 4
Description Task name in ASCII which has caused the auto-restart/auto-reset. 01 02 03 04 06 07 08 OD OE 10 13 14 System Reset Machine Reset Data Storage Instruction storage Alignment Program Floating point unavailable Trace Floating Point assist Software emulation Instruction TLB error Data TLB error
Interrupt entry
SRR0 SRR1 MRS
4 4 1
See MPC860 UMD, Interrupts section.
See MPC860 UMD, Interrupts section, only 3 bits are reported. bit0 bit1 bit2 MRS.IP MRS.ME MRS.LE
DSISR
See MPC860 UMD, Interrupts section, only 3 bits are reported. bit0 bit1 bit2 DSISR BIT 1 DSISR BIT 4 DSISR BIT 6
DAR IR Stack Info
4 4 60
See MPC860 UMD, Interrupts section.
The information is taken from the stack.
522 / 533
Error Type OTP SDT crash Taskname
Size 4
Description Task name in ASCII which has caused the auto-restart/auto-reset. Link register, it gives the program counter in SDT-generated code where the error has occurred. Signal value (in case of an error on a signal). State of the autonon when the signal was received. The post-mortem value. Additional Information. Non-fatal or fatal error detected during auto-tests. Faulty processor. Detailed step in DSP autotest. Faulty test number -
IR
Signal State DSP post-mortem Error More MT120 auto-test failure Severity Entity Status Test
4 4 4 N 1 1 1 1
Error Length
1 1
Error code Length in bytes -
Info
Additional information
Table 64: MT120 board, Error Types, Additional Information
523 / 533
524 / 533
30 Consequences of an SBL State Change

This section defines the alarm impact on the system due to an SBL state change.
525 / 533
SBL name ABIS-HWAY-TP
SBL state IT
Impact on system The telecom and O&M link between the BSC and the BTS or two BTSs is functioning correctly. Degradation in the telecom and O&M link between the BSC and the BTS or two BTSs. Loss of telecom and O&M link between the BSC and the BTS or two BTSs. The alarm reporting on the transmission link is disabled. Gain of a terrestrial traffic channel to the MSC. The channel can be used for traffic. Causes loss of a terrestrial traffic channel to the MSC. The channel will no longer be used for traffic. The telecom link between the TC and the MSC is functioning correctly. Degradation in the telecom and O&M link between the TC and the MSC. Loss of telecom and O&M link between the TC and the MSC. The alarm reporting on the transmission link is disabled. The link between the two submultiplexers is functioning correctly. Loss of link between the two submultiplexers. The alarm reporting on the transmission link is disabled. Gain of speech or data connections over this trunk. If the ATR back in service can be used for clock extraction and the BSC is currently using its local clock as the reference, then the BSC tries to switch back to the external clock provided by the ATR. Causes loss of speech or data connections over this trunk. If the ATR is used for clock extraction, the BSC selects another ATR and possibly another DTC/BCL-SYS. If no other ATR is available, the BSC uses its local clock. The trunk will no longer be used for traffic. Gain of the backup facility. Causes loss of the backup facility, normally activated on loss of power to the RAM disk.
FIT
FLT
OPR ACH IT
FLT/FOS
A-PCM-TP
IT
FIT
FLT OPR ATER-HWAY-TP IT FLT OPR ATR IT
FLT/EF
BATTERY
IT FLT
526 / 533
SBL name BC-RACK-BUS
SBL state IT FIT
Impact on system The rack broadcast bus is distributed to the associated CEs. Either there is a degradation for the full rack, or there is a failure for one or 2 CE. This state has no telecom impact if the other BC-RACK-BUS is IT. This branch of the broadcast bus is not working anymore. This state has no telecom impact if the other BC-RACK-BUS is IT. The rack broadcast bus (BC_RACK_BUS SBL) is disabled by the operator. The system broadcast bus is distributed correctly to all racks. The system broadcast bus (BC_SYS_BUS SBL) is disabled by the Operator. The BSC is working correctly. When two CLK-REP of the same rack (rack not containing the BCLA-SYS-boards) failing. BS trunks onto an ABIS The BIUA board, whichare multiplexes HWAY-TP at BSC is functioning correctly. When the BSC side, is running on a local clock.
FLT
OPR
BC-SYS-BUS
IT OPR
BSC
IT FIT
BSC-ADAPT
IT
FIT
FLT/FOS
OPR
BTS-ADAPT
IT
There is of a degradation in the service provided by the BIUA board, Loss both broadcast buses in the BSC either only at a CE which multiplexes trunks onto an ABIS at BSC side. level, or at rackBS level, or at system level.HWAY-TP LAC paging messages do not work except for the first 3 cells of the LAC, thus The BSC transmission board (BUIA), which multiplexes BS preventing terminating theis other GPRS trunks onto anMobile ABIS HWAY-TP atcalls BSCfor side, lost. cells, It cannot be reset procedure do not work anymore. Processors cannot programmed or accessed. be preloaded, thus lengthening outages in SW replacement The BIUA board, which multiplexes BS onto an ABIS procedure. RMS measurements aretrunks no more started nor HWAY-TP at BSC side, is disabled. stopped. This state has no impact on the telecom functions of the board, A on high number of BSC processors have reported DMA only the O&M part. problems. The BTS-BIE, which demultiplexes Abis channels from an ABIS HWAY-TP at BTS side, is functioning correctly. There is a degradation in the service provided by BTS-BIE board, which demultiplexes Abis channels from an ABIS HWAY-TP at BTS side. The BTS-BIE board, which demultiplexes Abis channels from an ABIS HWAY-TP at BTS side, is lost. It cannot be programmed or accessed. This state has no impact on the telecom functions of the board, only on the O&M part.
FIT
FLT/FOS
OPR
527 / 533
SBL name BTS-OM
SBL state IT FLT/FOS OPR
Impact on system Gain of full O&M availability of the cell from the BSC point of view. Loss of O&M availability of the cell from the BSC point of view. Loss of O&M availability of the cell from the BSC point of view. Gain of telecom availability of the cell from the BSC point of view. Loss of telecom availability of the cell from the BSC point of view. Degradation of telecom availability of the cell from the BSC point of view. Loss of telecom availability of the cell from the BSC point of view. The clock generator works correctly. The clock has detected the loss of its local clock. There is no impact on the service. If only one CLK-GEN is unavailable, there is no impact on the service. BSC will use the clock provided by the other CLK-GEN. Clock generation is disabled by the operator. The clock repeater works correctly. The clock repeater loses either System Clock A or System Clock B. A failure is detected in the BCLA-RACK board. No Clock reference is repeated. The clock repeater is disabled by the operator. The convertor is working correctly. There is no impact on traffic because the power supplies are in parallel. The CPR is working correctly. The standby CPR will become the master CPR and takes over all functions. The standby S-CPR will become the master System CPR and takes over all functions. SW/DB replacement actions will not be allowed. The standby O-CPR will become the master O-CPR and takes over all functions. If the old master was carrying the X.25 link with the OMC-R, this link is lost and scheduled performance measurement jobs are not reactivated in due time. The processor has reported a high number of DMA problems.
BTS-TEL
IT FLT FIT
OPR CLK-GEN IT FIT
FLT
OPR CLK-REP IT FIT FLT
OPR CONV IT FLT
CPR
IT OPR
S-CPR Duplex
FLT/FOS
O-CPR DUPLEX
FLT/FOS
S-CPR/O-CPR
FIT
528 / 533
SBL name CPR (BC_CPR)
SBL state FLT OPR NEQ
Impact on system The broadcast processor is not broadcasting. The broadcast processor is not broadcasting. The BC_CPR SBL is not defined in the BSC database. No impact. The impact depends on the type of associated CPR and whether the CPRs are running in duplex or not. If the disk goes to FOS, it can no longer be selected for loading of any 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.
DISC
IT/FIT FOS
529 / 533
SBL name DTC
SBL state
Impact on system
Speech or data connections to the MSC or MFS: IT These connections are re-established. New connections are possible. Change back of the SCCP connections on the N7 handled by the DTCs occurs. These connections on the associated PCM (1/4 of an Atermux) are lost. 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 extra effect 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 SCCP connections are lost. If the DTC manages a GSL, as long as there are other GSL for the corresponding GPU, there is no loss of transactions (degradation can happen if the remaining capacity is too small). FIT OPR The processor has reported a high number of DMA problems. These connections on the associated PCM (1/4 of an Atermux) are lost. 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 extra effect 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 SCCP connections are lost. If the DTC manages a GSL, as long as there are other GSL for the corresponding GPU, there is no loss of transactions (degradation can happen if the remaining capacity is too small).
FLT/FOS
N7
IT FLT/EF OPR
N7 Signaling can now be handled by the N7 link (=changeback). N7 Signaling will be handled by another N7 link (=changeover). N7 Signaling will be handled by another N7 link (=changeover).
530 / 533
SBL name OML
SBL state IT
Impact on system Communication with the OMU is re-established. Can have an impact on the BTS_O&M state. Causes loss of communication with the OMU. Will have an impact on the BTS_O&M state, depending on the kind of transaction started by the BSC when the OML is down. Communication with the TRE/TRX is established. Gain in telecommunication resource allocation capability on the BTS. The RSL SBL may cause loss of communication with the Frame Unit. Leads to a reduced telecommunication resource allocation capability on the BTS. The multiplexing on the ATER side is functioning correctly. The multiplexing on the ATER side is degraded. The multiplexing board ASMC (It sub-multiplexes A-trunks at the Transcoder)/ASMB (It sub-multiplexes A-trunks at the BSC) is not functioning correctly. Complete multiplexing on the Ater side is not being done. The multiplexing board ASMC/ASMB are disabled. Complete multiplexing on the Ater is not being done. All links associated with the Switch are IT. All links associated with the switch can be used. Causes loss of speech or data connections over this switch. This switch can no longer be used. More than 51% of links associated to Switch are FLT. Causes loss of some speech or data connections over this switch. This switch can still be used. Less than 51% of links associated to Switch are FLT. The link adaption between the MSC and the Submultiplexer is functioning correctly. The link adaption between the MSC and the Submultiplexer is degraded. The link adaption between the MSC and the Submultiplexer is not functioning correctly. The link adaption between the MSC and the Submultiplexer is disabled. On-going calls are not lost, no new calls can be initiated.
FLT
RSL
IT
FLT
SM-ADAPT
IT FIT FLT/FOS
OPR
SWITCH
IT
FLT
FIT
TC-ADAPT
IT
FIT
FLT
OPR
531 / 533
SBL name TCU
SBL state IT
Impact on system Communication with TRE/TRX and/or OMU and/or TSC is established. See RSL and/or OML and/or TSL. Causes loss of communication with Frame Unit(s) and/or OMU and/or TSC. See RSL and/or OML and/or TSL. The processor has reported a high number of DMA problems The A-interface channels managed by the BSC are functioning correctly. The A-interface channels managed by the BSC are degraded. The A-interface channels managed by the BSC are not functioning correctly. The A-interface channels managed by the BSC are disabled. Gain of transmission O&M availability from the BSC point of view. Loss of transmission O&M availability from the BSC point of view. The transmission processor controlling transmission O&M is functioning correctly. The transmission processor controlling transmission O&M is degraded. Communication with the TSC is established. Could have an impact on the TR_O&M state. Causes loss of communication with the TSC. Could have an impact on the TR_O&M state, depending on the kind of transaction started by the BSC when the TSL is down. The transmission processor controlling transmission O&M is not functioning correctly. Downloading to the TSC has failed. Connection between the BSC and a local terminal or OMC-R is established. If there is no X.25 redundancy, causes loss of connection between the BSC and a local terminal or OMC-R. If there is no X.25 redundancy, causes loss of connection between the BSC and a local terminal or OMC-R.
FLT/FOS
FIT TC-16 IT
FIT FLT
OPR TR-OM IT FLT TSC IT
FIT
TSL
IT
FLT
FLT/FOS
X.25
IT
FLT
OPR
532 / 533
BLANK PAGE BREAK
533 / 533

ALU BSC-TC Alarm Dictionary

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ALU BSC-TC Alarm Dictionary

Загружено:

Авторское право:

Доступные форматы

Alcatel BSS

BSC & TC Alarm Dictionary

BSC & TC Document Reference Guide Release B9

3BK 20918 AAAA PCZZA Ed.06

BLANK PAGE BREAK

Status Short title

RELEASED BSC & TC Alarm Dic.

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

Note: Whats New

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

1.2 A1353-RA AS Alarm Information

1.2.1 Object Identification

3BK 20918 AAAA PCZZA Ed.06

1.2.2 Alarm Type

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

Severity Level Critical

Indeterminate Cleared Table 2: Alarm Severity Levels

3BK 20918 AAAA PCZZA Ed.06

1.3 LMT Alarm Messages

1.3.1 Message Identity

1.3.2 Event Time

3BK 20918 AAAA PCZZA Ed.06

3BK 20918 AAAA PCZZA Ed.06

1.3.5 SBL States

1.3.6 RIT List

3BK 20918 AAAA PCZZA Ed.06

1.4 Alarm Information Format

1.4.1 Alarm Definition

1.4.2 Alarm Description

1.4.3 Alarm Definition

3BK 20918 AAAA PCZZA Ed.06

Table 4: Mapping of MO Perceived Severity to LMT Category

1.4.4 Alarm Description

1.4.4.2 Impact on Telecom

1.4.4.3 Impact on System

3BK 20918 AAAA PCZZA Ed.06

1.4.4.4 Failure Identification Strategy

1.4.4.5 Corrective Actions

3BK 20918 AAAA PCZZA Ed.06

Start field with alarm number and alarm name

Identify the faulty DC/DC converter indicated by red illuminated LED.

Onsite action fields

Restart faulty converter by disengaging/engaging RIT

Decision field Converter operational? yes Alarm solved

Replace BSC RIT

Onsite action fields

Decision field Converter operational? yes Alarm solved

no Contact System Support