BSC & TC Alarm Dictionary

Alcatel-Lucent GSM
BSC & TC Alarm Dictionary
BSC & TC Document Reference Guide Release B11
3BK 21618 AAAA PCZZA Ed.16
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 / 778
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 1.2 9153 OMC-R AS Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 1.3 LMT Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 1.4 Alarm Information Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Class 32: BSC-ENVIRON Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.1 [32,0] CONV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 2.2 [32,1] BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Class 33: PROCESSOR Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 3.1 [33,0] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 3.2 [33,1] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 3.3 [33,3] ACCESS-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 3.4 [33,4] RELC-OV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 3.5 [33,7] TAKEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 3.6 [33,9] SDCCH-OVRL-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Class 35: N7 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 4.1 [35,0] LNK-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 4.2 [35,2] RTE-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 4.3 [35,3] INC-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 4.4 [35,4] ASL-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 4.5 [35,5] RMH-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 4.6 [35,6] MSC-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 4.7 [35,7] MSC_DEGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Class 36: TRUNK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 5.1 [36,0] LFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 5.2 [36,3] RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 5.3 [36,4] AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 5.4 [36,5] SLIP-OV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 5.5 [36,6] SLIP-UN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 5.6 [36,7] LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 5.7 [36,10] CRCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 5.8 [36,11] CHO-EERH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 5.9 [36,12] CRC4-BERH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 5.10 [36,13] CRC4-BERL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Class 38: X.25 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 6.1 [38,0] MODEM-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 6.2 [38,1] LINK-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 6.3 [38,2] PROT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Class 39: BSC-SW-ANOMALY Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 7.1 [39,1] OSN-NON-RECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 7.2 [39,3] OSN-PROCEDURAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 7.3 [39,5] USR-NONRECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 7.4 [39,7] HWR-NONRECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 7.5 [39,18] SANITY-TIMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Class 42: TELECOM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 8.1 [42,1] NACK-MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 8.2 [42,2] OVERLOAD-MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 8.3 [42,3] START-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 8.4 [42,7] NO-RESET-CIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
3 / 778
Contents
10
11
12
13
8.5 [42,9] OVERLOAD-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6 [42,12] TEL-PAIR-LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7 [42,13] BSC-TRAFFIC-REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8 [42,14] GPRS-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9 [42,15] TCH-RM-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.10 [42,16] MSC-TRAFFIC-REDUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 43: CELL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1 [43,0] LOSS-OF-BCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2 [43,1] LOSS-OF-SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3 [43,2] LOSS-OF-TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4 [43,3] LOSS-OF-ALL-CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.5 [43,4] CELL-TRAFFIC-REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.6 [43,5] OVERLOAD-BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.7 [43,6] TRX-MAPPING-CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.8 [43,248] CONFIGURED POOLS NOT FULLY USABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 44: BTS-OM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.1 [44,0] AUDIT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2 [44,1] PROTOCOL-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3 [44,2] RECONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.4 [44,3] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.5 [44,5] SW-ACTIVATE-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.6 [44,6] CONFIG-DATA-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.7 [44,7] OMU-SELFTEST-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.8 [44,10] ABORT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.9 [44,11] PRELOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.10 [44,12] BTS-HW-CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 45: CHANNEL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 [45,0] CH-UNBLOCK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 [45,1] CH-BLOCK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 [45,2] BSC-CIC-UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.4 [45,3] MSC-CIC-UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5 [45,4] END-OF-REP-OF-UNBLOCK-PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 46: BACKUP-MEDIUM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1 [46,0] SYNC CORRUPTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 [46,1] UNSYNC-OTHER-CORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.3 [46,2] UNSYNC-OWN-CORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.4 [46,3] SYNC-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.5 [46,4] SECFILE-ROLLBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.6 [46,5] SINGLE-UPD-ROLLBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.7 [46,6] DUT-ROLLBACK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.8 [46,7] DISC-OOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.9 [46,8] DISC-PARITY-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 47: GLOBAL-BSC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.1 [47,2] AUTO-BSC-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2 [47,3] AUTO-BSC-RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.3 [47,4] BSC-SYNC-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.4 [47,5] BTS-SYNC-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.5 [47,6] AUDIT-COMPLETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6 [47,7] BSC-HW-RESYNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.7 [47,8] AIFL-FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.8 [47,9] CBC-CONNECTION-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.9 [47,11] ABIS-TS-ALLOC-FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.10 [47,12] INSUFFICIENT-TCU-RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.11 [47,13] TRE-SECTOR-MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.12 [47,14] LACK-OF-TCU-SPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
103 104 106 108 110 111 113 114 116 118 120 122 124 126 127 129 130 132 134 136 138 140 142 144 145 147 149 150 152 154 156 158 159 160 161 163 164 165 167 169 171 173 175 176 177 178 179 180 181 182 183 185 186 187 189
4 / 778
Contents
14
15
16
17
18
19
13.13 [47,15] SWRPL-IN-PROGRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.14 [47,16] MAX-TRE-EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.15 [47,17] MLPPP-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.16 [47,18] MLPPP-PARTIAL-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.17 [47,19] DLS-RESTORATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.18 [47,20] NTP-DRIFT-TIME-ALERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.19 [47,21] NTP-TIME-SERVER-UNREACHABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.20 [47,22] NTP-DRIFT-TIME-EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.21 [47,23] MAX-HDLC-EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.22 [47,24] MUX-SECTOR-NOT-COMP-2ABIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.23 [47,25] TC-HW-RESYNCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.24 [47,26] TRAU-CP-OUT-OF-RANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.25 [47,27] TRAU-CP-ON-DEDICATED-ATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.26 [47,28] TRAU-CP-DOUBLE-DECLARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.27 [47,30] TRANS-CONFIG-IMPOSSIBLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.28 [47,40] CS-TEL-TEST-NOK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.29 [47,41] PS-TEL-TEST-NOK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.30 [47,103] BTS-TC-RESHUFFLING-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.31 [47,200] N7-CONF-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 48: TR-OM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.1 [48,0] AUDIT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.2 [48,1] PROTOCOL-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 49: ALERTER Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1 [49,0] LOW-TRAF-SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2 [49,1] CH-INCONSIST-SUSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3 [49,2] TCH-BLOCK-SUSPECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4 [49,3] TCH-OCCUP-SHORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 50: BSC EXTERNAL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.1 [50,1] EXT-ALARM-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2 [50,2] EXT-ALARM-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.3 [50,3] EXT-ALARM-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.4 [50,4] EXT-ALARM-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.5 [50,5] EXT-ALARM-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.6 [50,6] EXT-ALARM-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.7 [50,7] EXT-ALARM-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.8 [50,8] EXT-ALARM-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.9 [50,9] EXT-ALARM-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.10 [50,10] EXT-ALARM-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 51: SWITCH G2 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1 [51,0] TRANSIENT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.2 [51,1] SWITCH-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.3 [51,2] ROUTINE-TEST-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.4 [51,3] GLOBAL-ROUTINE-TEST-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 52: BSC CLOCK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.1 [52,0] LOSS-OF-SEL-CLK-INP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2 [52,1] LOSS-OF-CLK-GEN-FN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.3 [52,2] SWITCH-TO-LOCAL-CLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.4 [52,3] LOSS-OF-SYSTEM-CLOCK-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.5 [52,4] LOSS-OF-SYSTEM-CLOCK-B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.6 [52,5] LOSS-OF-CLK-DISTR-FN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.7 [52,6] BSC-RUN-ON-LOCAL-CLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.8 [52,7] LOC-CLK-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 53: BROADCAST BUS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.1 [53,0] LOSS-OF-ONE-BROAD-BUS-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
190 192 194 196 198 199 201 203 205 207 208 209 210 211 212 213 214 216 217 219 220 221 223 224 226 228 229 231 232 234 236 238 240 242 244 246 248 250 253 254 255 259 261 263 264 266 267 269 270 271 272 274 275 276
5 / 778
Contents
20 21
22
23 24 25
19.2 [53,1] LOSS-OF-BOTH-BROAD-BUS-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.3 [53,2] DMA-PROBLEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.4 [53,3] LOSS-OF-ONE-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.5 [53,4] LOSS-OF-BOTH-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.6 [53,5] DEGRAD-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.7 [53,6] LOSS-OF-ONE-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.8 [53,7] LOSS-OF-BOTH-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.9 [53,8] DEGRAD-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 54: BTS-POOL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.1 [54,1] EXTRA TS NOT FULLY USABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 66: TSC-TRUNK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.1 [66,21] LOOP-TO-ITF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 [66,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3 [66,50] TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4 [66,66] AIS-2-MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.5 [66,81] FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.6 [66,86] CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.7 [66,99] BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.8 [66,100] BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.9 [66,102] BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.10 [66,176] FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.11 [66,208] I1I2-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.12 [66,210] TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.13 [66,211] LOSS-OF-CLK-2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.14 [66,225] TU-LOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.15 [66,226] TU-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.16 [66,227] LP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.17 [66,228] LP-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.18 [66,229] LP-PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.19 [66,230] LP-J2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.20 [66,231] E1-AIS-2MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.21 [66,232] E1-FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.22 [66,233] E1-CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.23 [66,234] E1-BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.24 [66,235] E1-BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.25 [66,236] E1-RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 67: TSC-CHANNEL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.1 [67,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2 [67,72] AIS-16-KB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3 [67,122] TRAU-SYNCHRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.4 [67,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.5 [67,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.6 [67,131] INT-BUS-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 70: TSC-SW-ANOMALY Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.1 [70,219] SW-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 71: TSC-ENVIRON Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.1 [71,0] POWER-SUPPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 73: BSC-ADAPT Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.1 [73,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.2 [73,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.3 [73,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.4 [73,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.5 [73,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.6 [73,203] LOSS-OF-ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
277 278 279 280 281 282 283 284 285 286 289 290 291 292 294 296 298 300 302 304 306 308 310 312 314 315 316 317 318 319 320 321 322 323 324 325 327 328 329 331 333 335 337 339 340 343 344 347 348 349 351 353 354 356
6 / 778
Contents
26
27
25.7 [73,212] LOSS-OF-CLK-8M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.8 [73,213] LOSS-OF-CLK-BOTH-8M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.9 [73,216] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.10 [73,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.11 [73,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.12 [73,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 74: BTS-ADAPT Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.1 [74,20] BLOCKED-FROM-USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.2 [74,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.3 [74,23] TESTMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.4 [74,122] SYNCHRO-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.5 [74,124] SYNC-AL-CLOCKR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.6 [74,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.7 [74,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.8 [74,139] MISSING-UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.9 [74,141] FORCED-CNTRL-ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.10 [74,142] INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.11 [74,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.12 [74,159] DIAG-TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.13 [74,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.14 [74,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.15 [74,245] LOCAL-REINIT-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.16 [74,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.17 [74,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 75: TCSM-ADAPT Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.1 [75,20] BLOCKED-FROM-USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.2 [75,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.3 [75,112] FAN-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.4 [75,122] SYNCHRO-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.5 [75,124] SYNCHRO-AL-CLOCKR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.6 [75,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.7 [75,130] DSP-LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.8 [75,136] FIRST-DSP-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.9 [75,139] MISSING-UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.10 [75,141] FORCED-CNTRL-ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.11 [75,142] INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.12 [75,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.13 [75,159] DIAG-TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.14 [75,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.15 [75,208] TRIB-TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.16 [75,209] INT-BUS-FLT-G25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.17 [75,210] ATER-TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.18 [75,211] LOSS-OF-CLK-2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.19 [75,216] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.20 [75,221] TRIB-TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.21 [75,222] TRIB-AIS-2MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.22 [75,223] TRIB-FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.23 [75,224] TRIB-CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.24 [75,225] TRIB-BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.25 [75,226] TRIB-BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.26 [75,227] TRIB-BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.27 [75,228] TRIB-FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.28 [75,231] ATER-TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.29 [75,232] ATER-AIS-2MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.30 [75,233] ATER-FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.31 [75,234] ATER-CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
358 360 362 363 364 366 367 368 370 371 372 374 376 378 380 382 383 385 386 387 389 391 393 395 397 398 399 400 401 403 405 407 409 411 413 414 416 417 418 420 422 424 426 428 429 431 433 435 436 438 440 442 444 446 448 450
7 / 778
Contents
28
29
27.32 [75,235] ATER-BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.33 [75,236] ATER-BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.34 [75,237] ATER-BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.35 [75,238] ATER-FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.36 [75,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.37 [75,245] LOCAL-REINIT-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.38 [75,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27.39 [75,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 96: PROCESS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.1 [96,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.2 [96,1] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.3 [96,2] MULTIPLE-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.4 [96,3] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 97: ATCA-PROCESSOR Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.1 [97,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.2 [97,1] TAKEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.3 [97,2] RLC-OV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.4 [97,3] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.5 [97,4] APPLICATION-FATAL-TERMINATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.6 [97,5] SYSTEM-FATAL-TERMINATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.7 [97,6] UNPLUGGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.8 [97,7] FW-UPGRADE-UNSUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.9 [97,8] FW-UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.10 [97,9] FIRMWARE-INCOMPATIBILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.11 [97,10] FATAL-HW-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.12 [97,11] TEMPERATURE-CRITICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.13 [97,12] TEMPERATURE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.14 [97,14] VOLTAGE-FATAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.15 [97,15] VOLTAGE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.16 [97,16] VOLTAGE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.17 [97,17] ETHERNET-LINK-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.18 [97,18] IPMI-FIRMWARE-NOT-UP-TO-DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.19 [97,19] FIRMWARE-NOT-UP-TO-DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.20 [97,20] CONFIGURATION-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.21 [97,21] TAKEOVER-REFUSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.22 [97,22] CPU-OVERLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.23 [97,23] BSC-CONF-UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.24 [97,30] N7-DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.25 [97,31] HDLC-HANDLER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.26 [97,32] Q1-HANDLER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.27 [97,33] RW-HANDLER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.28 [97,34] TDM-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.29 [97,35] E1-FRAMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.30 [97,36] TP-MAIN-SW-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.31 [97,37] TP-MAIN-FILE-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.32 [97,38] TP-MAIN-ACCESS-PB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.33 [97,39] SS7-SW-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.34 [97,40] CS-TEL-TEST-NOK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.35 [97,50] NE1OE-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.36 [97,51] E1-SL-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.37 [97,60] TP-CAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.38 [97,61] TPIP-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.39 [97,62] CONFIG-IP-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.40 [97,63] CONFIG-IP-INPUT-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.41 [97,64] CONFIG-IP-RUNTIME-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.42 [97,65] DRIVERS-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
451 453 455 457 459 460 462 464 465 466 467 468 470 473 474 475 476 477 479 480 481 482 483 484 485 486 488 490 492 494 496 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 514 515 516 518 519 520 521 522 523 524
8 / 778
Contents
30
31
32
29.43 [97,66] HW-DIAGNOSIS-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.44 [97,67] INTER-TP-ACCESS-PB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 98: ATCA-SWITCH Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.1 [98,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.2 [98,3] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.3 [98,6] UNPLUGGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.4 [98,7] FW-UPGRADE-UNSUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.5 [98,8] FW-UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.6 [98,9] FIRMWARE-INCOMPATIBILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.7 [98,10] FATAL-HW-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.8 [98,11] TEMPERATURE-FATAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.9 [98,12] TEMPERATURE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.10 [98,13] TEMPERATURE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.11 [98,14] VOLTAGE-FATAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.12 [98,15] VOLTAGE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.13 [98,16] VOLTAGE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.14 [98,18] IP-ROUTER-LINK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.15 [98,19] TELECOM-LINK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.16 [98,20] OAM-LINK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.17 [98,21] FIRMWARE-NOT-UP-TO-DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.18 [98,22] IP-CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.19 [98,23] ASIG-OVER-IP-LINK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30.20 [98,24] BSS-OVER-IP-LINK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 99: ATCA-SHELF Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 [99,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2 [99,3] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.3 [99,6] UNPLUGGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.4 [99,7] FW-UPGRADE-UNSUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.5 [99,8] FW-UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.6 [99,9] FIRMWARE-INCOMPATIBILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.7 [99,10] FATAL-HW-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.8 [99,11] TEMPERATURE-FATAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.9 [99,12] TEMPERATURE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.10 [99,13] TEMPERATURE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.11 [99,14] VOLTAGE-FATAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.12 [99,15] VOLTAGE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.13 [99,16] VOLTAGE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.14 [99,17] ETHERNET-LINK-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.15 [99,18] SHELF-MANAGER-ACCESS-PB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.16 [99,19] FAN-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.17 [99,20] FIRMWARE-NOT-UP-TO-DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.18 [99,21] IPMI-BUS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 100: LIU-SHELF Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.1 [100,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.2 [100,1] MUX-TAKEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.3 [100,4] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.4 [100,6] UNPLUGGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.5 [100,7] FW-UPGRADE-UNSUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.6 [100,8] FW-UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.7 [100,9] FIRMWARE-INCOMPATIBILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.8 [100,19] FIRMWARE-NOT-UP-TO-DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.9 [100,20] LIU_SHELF_PEM_OWN_VBAT_LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.10 [100,21] LIU_SHELF_RED_VBAT_LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.11 [100,22] PEM_OWN_12V_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.12 [100,23] TOO_HIGH_TEMPERATURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.13 [100,24] PEM_NOT_RESPONDING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
525 526 527 528 529 530 531 532 533 535 538 540 542 544 546 548 550 552 554 556 557 559 561 563 564 565 566 567 568 569 571 573 575 577 579 581 582 583 585 586 587 588 591 592 593 594 595 596 597 598 599 600 601 602 603 605
9 / 778
Contents
33
34
35
32.14 [100,50] NE1OE-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.15 [100,51] E1-SL-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 101: BSC-TRANS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.1 [101,0] LIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.2 [101,1] AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.3 [101,2] LFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.4 [101,4] BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.5 [101,5] RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.6 [101,6] BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.7 [101,7] BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.8 [101,8] FRAME-SLIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.9 [101,9] PPP-LNK-LOOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.10 [101,10] PPP-NO-HDLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.11 [101,11] PPP-NO-LCP-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.12 [101,12] PPP-CONF-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.13 [101,13] PPP-HIGH-ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.14 [101,14] OML-MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.15 [101,20] SFP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.16 [101,21] LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.17 [101,22] LOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.18 [101,23] MS-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.19 [101,24] MS-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.20 [101,25] MS-BER-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.21 [101,26] MS-BER-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.22 [101,28] SFP-NOT-SUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.23 [101,31] AU-LOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.24 [101,32] AU-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.25 [101,41] HP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.26 [101,42] HP-PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.27 [101,43] HP-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.28 [101,44] HP-LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.29 [101,51] TU-LOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.30 [101,52] TU-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.31 [101,55] LP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.32 [101,56] LP-PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.33 [101,57] LP-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.34 [101,60] PPP-CROSS-CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.35 [101,61] PPP-LCP-TER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.36 [101,62] PPP-LOW-ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.37 [101,63] PPP-MED-ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.38 [101,100] STM1-TAKEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 104: TC-OM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34.1 [104,0] TC-INIT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34.2 [104,1] TC-INIT-SUCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class 105: TRANSCODER Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35.1 [105,0] POWER-SUPPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35.2 [105,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35.3 [105,130] DSP LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35.4 [105,136] FIRST-DSP-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35.5 [105,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35.6 [105,210] TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35.7 [105,211] LOSS-OF-CLK-2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35.8 [105,216] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35.9 [105,238] ACTIVE-HSI-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35.10 [105,239] REDUNDANT-HSI-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
607 609 611 612 614 616 618 620 622 624 626 628 630 631 632 633 635 637 638 640 642 643 644 645 647 648 650 651 652 654 655 657 659 660 662 664 665 666 667 668 669 671 672 673 675 676 677 679 681 683 684 686 687 688 690
10 / 778
Contents
36
37
BSC/TC Alarm Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36.1 Restart and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36.2 Reset and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36.3 System Support Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36.4 Other BSC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36.5 TC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36.6 BTS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consequences of an SBL State Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37.1 9120 BSC SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37.2 9130 BSC Evolution SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
693 694 710 711 711 756 763 765 766 773
11 / 778
Figures
Figures
Figure 1: Graphical Flowchart for Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Figure 2: SWITCH-FAIL: Corrective Actions for Write Violation Overflow, Loss of Sync Overflow and Init Fail Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Figure 3: SWITCH-FAIL: Corrective Actions for Loss of Sync Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Figure 4: SWITCH-FAIL: Corrective Actions for HW Fault Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
12 / 778
Tables
Tables
Table 1: Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Table 2: Alarm Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Table 3: Alarm Definition: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Table 4: Mapping of MO Perceived Severity to LMT Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Table 5: Additional Information for Restart and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694 Table 6: FMM-IDs in Bytes 4 and 5 for Restart Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704 Table 7: Error Types in Bytes 10 and 11 for Restart Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709 Table 8: Additional Information for Reset and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710 Table 9: System Support Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711 Table 10: Additional Information for Alarm [33,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711 Table 11: Additional Information for Alarms [34,0] to [34,2] and [34,4] to [34,6] . . . . . . . . . . . . . . . . . . . . . . . . 711 Table 12: Additional Information for Alarm [34,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713 Table 13: Test Segment Results for Alarm [34,3], [51,1] (Byte 0) and [51,2] (One Byte Only) . . . . . . . . . . . 714 Table 14: Test Fault Type for Alarm [34,3], [51,1] (Byte 1) and [51,2] (One Byte Only) . . . . . . . . . . . . . . . . . 718 Table 15: TDM Connection Test Results (Bytes 6 to 21) for Alarm [34,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718 Table 16: Additional Information for Alarm [34,7] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718 Table 17: Additional Information for Alarm [35,0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719 Table 18: Additional Information for Alarm [35,2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720 Table 19: Additional Information for Alarm [35,3], Layout 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721 Table 20: Additional Information for Alarm [35,3], Layout 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721 Table 21: Example of Additional Information for Alarm [35,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721 Table 22: Additional Information for Alarm [35,4] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722 Table 23: Additional Information for Alarm [36,14] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722 Table 24: Additional Information for Alarm [36,15] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722 Table 25: Additional Information for Alarm [38,0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723 Table 26: Additional Information for Alarm [38,2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723 Table 27: Additional information for Alarm [42,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723 Table 28: Additional Information for Alarm [42,5] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725 Table 29: Additional Information for Alarm [42,6] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726 Table 30: Additional Information for Alarm [42,9] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727 Table 31: Additional Information for Alarm [42,12] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727 Table 32: Additional Information for Alarm [42,13] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729 Table 33: Additional Information for Alarms [43,0] to [43,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730 Table 34: Additional Information for Alarm [43,4] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732 Table 35: Additional Information for Alarms [44,0], [44,5] and [44,6] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732 Table 36: Additional Information for Alarm [44,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733 Table 37: Additional Information for Alarms [46, 0], [46,1] and [46,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733 Table 38: Additional Information for Alarm [47,9] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733 Table 39: Additional Information for Alarm [49,0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
13 / 778
Tables
Table 40: Additional Information for Alarm [49,1] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734 Table 41: Additional Information for Alarms [49,2] and [49,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735 Table 42: Additional Information for Alarm [51,0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735 Table 43: Additional Information for Alarm [51,1] - First Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736 Table 44: Additional Information for Alarm [51,1] - Subsequent Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737 Table 45: TDM Test Result Byte Descriptions for Alarm [51,1] and [51,2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738 Table 46: Detailed TDM Test Results for Alarm [51,1] and [51,2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738 Table 47: Additional Information for Alarm [51,2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739 Table 48: Example for an Unsuccessful Test Results Format for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . 739 Table 49: Relationship IAD/NA to RIT and Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752 Table 50: Additional Information for Alarm [51,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753 Table 51: Additional Information for Alarms [52,1], [52,5] and [52,7] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754 Table 52: Additional Information for Alarms [53,0], [53,1], [53,3], [53,4], [53,6] and [53,7] . . . . . . . . . . . . . . 754 Table 53: Additional Information for Alarm [53,2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754 Table 54: Additional Information for Alarms [53,5] and [53,8] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755 Table 55: Additional Information for Alarm [101,8] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755 Table 56: Additional Information for Alarm [70,219] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756 Table 57: Additional Information for Alarm [73,022] to [73,216] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756 Table 58: Additional Information for Alarm [75,20] to [75,247] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757 Table 59: MT120 Board - Equipment Reset/Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758 Table 60: MT120 Board, Range >80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758 Table 61: MT120 Board, Error Types, Range <80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759 Table 62: MT120 board, Error Types, Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762 Table 63: Additional Information for Alarm [74,20] to [74,202] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
14 / 778
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: Document Pertinence
When a fault occurs, a number of alarms can be generated simultaneously. These alarms must be analyzed as a group to determine the precise fault. This document applies to release B11 of the BSS. This document contains IP transport in the BSS related information. This feature is available commercially from Release B11 MR2.
Whats New
In Edition 16
Section [101,8] (Section 36.4.37) was added.
In Edition 15
The alarm [97,18] IPMI-FIRMWARE-NOT-UP-TO-DATE (Section 29.18) was added.
In Edition 14
Description improvement for alarm [97,1] TAKEOVER (Section 29.2). Alarm [97,67] INTER-TP-ACCESS-PB (Section 29.44) was added. Corrective action improvement for alarm [99,10] FATAL-HW-FAILURE (Section 31.7). System impact was updated for alarms: [35,4] ASL-REP (Section 4.4) [35,5] RMH-REP (Section 4.5) [42,16] MSC-TRAFFIC-REDUCTION (Section 8.10) [43,6] TRX-MAPPING-CHANGE (Section 9.7) [47,28] TRAU-CP-DOUBLE-DECLARED (Section 13.26)
15 / 778
Preface
[104,0] TC-INIT-FAIL (Section 34.1) [104,1] TC-INIT-SUCC (Section 34.2). Applicability was updated for alarms: [47,26] TRAU-CP-OUT-OF-RANGE (Section 13.24) [47,27] TRAU-CP-ON-DEDICATED-ATER (Section 13.25) [47,28] TRAU-CP-DOUBLE-DECLARED (Section 13.26) [47,200] N7-CONF-FAILURE (Section 13.31) [51,3] GLOBAL-ROUTINE-TEST-REP (Section 17.4) Class 101: BSC-TRANS Alarms (Section 33) [104,0] TC-INIT-FAIL (Section 34.1) [104,1] TC-INIT-SUCC (Section 34.2). Impact table was updated for alarms: [47,19] DLS-RESTORATION (Section 13.17) [48,0] AUDIT-FAIL (Section 14.1) [48,1] PROTOCOL-FAIL (Section 14.2) Class 50: BSC EXTERNAL Alarms (Section 16) Class 73: BSC-ADAPT Alarms (Section 25) [96,3] ACCESS-FAIL (Section 28.4) [99,9] FIRMWARE-INCOMPATIBILITY (Section 31.6) [100,50] NE1OE-FAILURE (Section 32.14).
In Edition 13
Section BTS Alarms (Section 36.6) was created.
In Edition 12
The following have been added: [98,21] FIRMWARE-NOT-UP-TO-DATE (Section 30.17) [99,20] FIRMWARE-NOT-UP-TO-DATE (Section 31.17). The following have been updated: [97,9] FIRMWARE-INCOMPATIBILITY (Section 29.10) [97,19] FIRMWARE-NOT-UP-TO-DATE (Section 29.19) [98,9] FIRMWARE-INCOMPATIBILITY (Section 30.6) [99,9] FIRMWARE-INCOMPATIBILITY (Section 31.6) [100,9] FIRMWARE-INCOMPATIBILITY (Section 32.7) [100,19] FIRMWARE-NOT-UP-TO-DATE (Section 32.8).
In Edition 11
Description improvement for alarm [98,10] FATAL-HW-FAILURE (Section 30.7). Applicability was updated for alarm [46,1] UNSYNC-OTHER-CORR (Section 12.2).
16 / 778
Preface
Corrective action was updated for alarms: [35,6] MSC-REP (Section 4.6) [43,3] LOSS-OF-ALL-CHAN (Section 9.4) [44,1] PROTOCOL-FAIL (Section 10.2).
In Edition 10
Alarm description was updated for alarm [42,2] OVERLOAD-MSC (Section 8.2). Severity was updated for alarm [35,6] MSC-REP (Section 4.6). Impacted SBL was updated for STM1 related alarms in Class 101: BSC-TRANS Alarms (Section 33).
In Edition 09
Alarm [43,6] TRX-MAPPING-CHANGE (Section 9.7) was added. Alarm severity was changed for alarms: [35,6] MSC-REP (Section 4.6) [42,16] MSC-TRAFFIC-REDUCTION (Section 8.10). Description improvement for alarms: [43,0] LOSS-OF-BCCH (Section 9.1) [43,1] LOSS-OF-SDCCH (Section 9.2) [43,2] LOSS-OF-TCH (Section 9.3) [47,40] CS-TEL-TEST-NOK (Section 13.28) [47,41] PS-TEL-TEST-NOK (Section 13.29) [97,23] BSC-CONF-UNAVAILABLE (Section 29.23) [97,40] CS-TEL-TEST-NOK (Section 29.34) [97,65] DRIVERS-FAILURE (Section 29.42) [97,66] HW-DIAGNOSIS-FAILURE (Section 29.43) [98,24] BSS-OVER-IP-LINK-FAIL (Section 30.20).
In Edition 08
The following alarms have been added: [47,103] BTS-TC-RESHUFFLING-FAIL (Section 13.30) [99,21] IPMI-BUS-FAIL (Section 31.18). [101,14] OML-MODE (Section 33.14) [101,41] HP-UNEQ (Section 33.25). Description improvement for alarms: [97,65] DRIVERS-FAILURE (Section 29.42) [97,66] HW-DIAGNOSIS-FAILURE (Section 29.43) [98,11] TEMPERATURE-FATAL (Section 30.8) [99,11] TEMPERATURE-FATAL (Section 31.8). Section Overview was updated with the commercial name for the TCIF/TCIFI boards.
17 / 778
Preface
In Edition 07
The following alarms have been added: [47,40] CS-TEL-TEST-NOK (Section 13.28) [47,41] PS-TEL-TEST-NOK (Section 13.29) [97,23] BSC-CONF-UNAVAILABLE (Section 29.23) [97,40] CS-TEL-TEST-NOK (Section 29.34) [98,22] IP-CONFIG-FAIL (Section 30.18) [98,23] ASIG-OVER-IP-LINK-FAIL (Section 30.19) [98,24] BSS-OVER-IP-LINK-FAIL (Section 30.20). Improvements have been made in: [71,0] POWER-SUPPLY (Section 24.1) [97,17] ETHERNET-LINK-FAILURE (Section 29.17)
In Edition 06
Alarm Description have been improved for [42,14] GPRS-RESET (Section 8.8).
In Edition 05
Corrective Action have been improved for the following alarms: [42,12] TEL-PAIR-LOST (Section 8.6) [42,15] TCH-RM-FAULT (Section 8.9) [47,22] NTP-DRIFT-TIME-EXCEEDED (Section 13.20) [52,1] LOSS-OF-CLK-GEN-FN (Section 18.2) [98,3] ACCESS-FAIL (Section 30.2) [99,3] ACCESS-FAIL (Section 31.2) Corrective action from alarm [35,7] MSC_DEGRADE (Section 4.7) had been updated.
In Edition 04
Improvement done in [101,25] MS-BER-6 (Section 33.20).
In Edition 03
Description improvement for: [35,4] ASL-REP (Section 4.4) [35,5] RMH-REP (Section 4.5) [42,12] TEL-PAIR-LOST (Section 8.6) [42,15] TCH-RM-FAULT (Section 8.9) [47,22] NTP-DRIFT-TIME-EXCEEDED (Section 13.20) [52,1] LOSS-OF-CLK-GEN-FN (Section 18.2) [98,3] ACCESS-FAIL (Section 30.2) [99,3] ACCESS-FAIL (Section 31.2)
18 / 778
Preface
[99,10] FATAL-HW-FAILURE (Section 31.7).
In Edition 02
Corrective action have been added for the following alarms: [101,10] PPP-NO-HDLC (Section 33.10) [101,11] PPP-NO-LCP-REP (Section 33.11) [101,12] PPP-CONF-FAIL (Section 33.12) [101,20] SFP-UNEQ (Section 33.15) [101,21] LOS (Section 33.16) [101,22] LOF (Section 33.17) [101,23] MS-AIS (Section 33.18) [101,24] MS-RDI (Section 33.19) [101,25] MS-BER-6 (Section 33.20) [101,26] MS-BER-3 (Section 33.21) [101,28] SFP-NOT-SUP (Section 33.22) [101,31] AU-LOP (Section 33.23) [101,32] AU-AIS (Section 33.24) [101,42] HP-PLM (Section 33.26) [101,43] HP-RDI (Section 33.27) [101,44] HP-LOM (Section 33.28) [101,51] TU-LOP (Section 33.29) [101,52] TU-AIS (Section 33.30) [101,55] LP-UNEQ (Section 33.31) [101,56] LP-PLM (Section 33.32) [101,57] LP-RDI (Section 33.33) [101,60] PPP-CROSS-CON (Section 33.34) [101,61] PPP-LCP-TER (Section 33.35) [101,62] PPP-LOW-ERR (Section 33.36) [101,63] PPP-MED-ERR (Section 33.37) [101,100] STM1-TAKEOVER (Section 33.38)
In Edition 01
Update due to feature NEW ALMAP FM MODULE REPLACEMENT AS. First release of the document.
19 / 778
Preface
Audience Assumed Knowledge
This document is aimed at telecommunications operators responsible for performing O&M fault handling and troubleshooting tasks. The operator must be familiar with the following: Alcatel O&M concepts for the BSS 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.
20 / 778
1 Introduction
1 Introduction
This section describes the structure of alarm messages.
21 / 778
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.
Note:
The following convention applies for a 9125 TC equipped with a TC STM1 IP subrack: TC STM1 interface board is also referred as TCIF TC STM1 IP interface board is also referred as TCIFI.
1.2 9153 OMC-R AS Alarm Information

In the 9153 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.
22 / 778
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.
23 / 778
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).
24 / 778
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.
25 / 778
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.
26 / 778
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.
27 / 778
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.;
28 / 778
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.
29 / 778
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 36). 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.
30 / 778
2 Class 32: BSC-ENVIRON Alarms

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

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-ENVIRON [32] CONV [0] Equipment PowerProblem Critical (VPMA) 9120 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. 9120 BSC 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. 9120 BSC: The BSC is able to distinguish between the different convertors with the 9120 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.
Applicability Impact on System
Impact Loss Degradation
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
O&M; Capabilities No No
32 / 778
2.1.1 Corrective Action

[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
33 / 778
2.2 [32,1] BAT

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-ENVIRON [32] BAT [1] Equipment PowerProblem Critical (VPMA) There is a battery on each S_CPR. This battery feeds the SRAM where the DLS is stored. The output power of the battery is monitored and the alarm reflects that the output power dropped below a pre-defined threshold. At alarm occurrence, this is still no impact on the service but if operator does not replace the battery, the output power will still decrease, leading to problems of access to the DLS the battery and the CPR. 9120 BSC At alarm occurrence, this is still no impact on the service but if operator does not replace the battery, the output power will still decrease, leading to problems of access to the DLS the battery and the CPR.See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
34 / 778

[32,1] BAT
Onsite
Identify the suspected SYSCPRC.
Onsite
Replace SYSCPRC
Battery operational?
yes
Alarm solved
no
Contact System Support
35 / 778
36 / 778
3 Class 33: PROCESSOR Alarms

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

specificProblems eventType probableCause perceivedSeverity Alarm Description PROCESSOR [33] RESTART [0] Processing Error SoftwareError Indeterminate An autonomous restart of a processor has occurred because of a failure condition on the processor.
38 / 778
9120 BSC In case of CPR: 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. 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. In case of DTC: 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. In case of TCU: 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. In case of TSC: 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.
39 / 778
Trunk(s) No Yes (if DTC)
Cell/BTS(s) No No
Signaling No Yes (if CPR, DTC, TCU or TSC)
Call Handling No Yes (if CPR, DTC or TCU)
O&M; Capabilities No Yes (if TSC)

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 36) for the byte definition.
40 / 778
3.2 [33,1] RESET

specificProblems eventType probableCause perceivedSeverity Alarm Description PROCESSOR [33] RESET [1] Processing Error SoftwareError Indeterminate An autonomous reload (reboot) of a processor occurred successfully.
41 / 778
9120 BSC The SBL state remains unchanged. In case of 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. * 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. In case if DTC: All calls managed by the processor are lost. In case of TCU: All calls managed by the processor are lost. In case of 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: *Reset * Resume the action * Initiate an audit * Terminate the action.
42 / 778
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

The processor returns to service automatically. If the reset procedure fails or there are too many resets within a certain time frame, the processor is reloaded. See BSC/TC Alarm Additional Information (Section 36) for the byte definition.
43 / 778
3.3 [33,3] ACCESS-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description PROCESSOR [33] ACCESS-FAILURE [3] Equipment EquipmentMalfunction Major (PMA) The self-maintenance part of the system (i.e., Heartbeat) detected an unreachable processor and informs central maintenance. 9120 BSC 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. If CPR: O&M capacity is degraded. If DTC: For every type of DTC, there is always the release of the transactions which were established on the associated 2Mbits (1/4 of an Ater mux). Then the extra effect depends on the function of this DTC: *If the DTC carries a TCH resource manager, there is no extra effect on the calls. *If the DTC manages a N7 link, as long as there are other N7 links in service, there is no loss of calls.(degradation can happen if the remaining capacity is too small. *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). *If the DTC supports BSSAP, the corresponding calls are lost. If 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. If TSC: *No supervision anymore for the Q1 modules controlled by this TSC (TC, ASMB, BIE, possibly BTS) *No possibility to perform evolution of the hardware configuration for the same Q1 modules (for example, no possible extension/modification of BTS connected on depending BIE). See also Consequences of an SBL State Change.
44 / 778
Impact Loss
Trunk(s) Yes (if DTC)
Cell/BTS(s) Yes (if CPR, DTC or TCU) Yes (if TCU and cells have TRX mapped on other TCU)
Signaling Yes (if TSC)
Call Handling Yes (if CPR)
O&M; Capabilities Yes (if CPR, TCU or TSC)
Degradation
No
Yes (if DTC or TCU)
Yes (if DTC or TCU)
Yes (if CPR or TCU)

[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
45 / 778
3.4 [33,4] RELC-OV

specificProblems eventType probableCause perceivedSeverity Alarm Description PROCESSOR [33] RELC-OV [4] 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. 9120 BSC 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. If CPR: O&M capacity is degraded. If DTC: For every type of DTC, there is always the release of the transactions which were established on the associated 2Mbits (1/4 of an Ater mux). Then the extra effect depends on the function of this DTC: *If the DTC carries a TCH resource manager, there is no extra effect on the calls. *If the DTC manages a N7 link, as long as there are other N7 links in service, there is no loss of calls. (degradation can happen if the remaining capacity is too small *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). *If the DTC supports BSSAP, the corresponding calls are lost. If 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. If TSC: *No supervision anymore for the Q1 modules controlled by this TSC (TC, ASMB, BIE, possibly BTS) *No possibility to perform evolution of the hardware configuration for the same Q1 modules (for example, no possible extension/modification of BTS connected on depending BIE). See also Consequences of an SBL State Change.
46 / 778
Impact Loss
Trunk(s) Yes (if DTC)
Cell/BTS(s) Yes (if CPR)
Signaling Yes (if CPR or TSC) Yes (if DTC or TCU)
Call Handling Yes (if CPR)
O&M; Capabilities Yes (if CPR, TCU or TSC) No
Degradation
No
Yes (if TCU and cells have TRX mapped on other TCU)
Yes (if DTC or TCU)

[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
47 / 778
3.5 [33,7] TAKEOVER

specificProblems eventType probableCause perceivedSeverity Alarm Description PROCESSOR [33] TAKEOVER [7] Processing Error SoftwareProgramAbnormallyTerminated Indeterminate 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. Applicability Impact on System 9120 BSC The SBL state remains unchanged. If 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. If DTC TCH-RM: During a take-over no radio channel allocation is possible for a short period. See also Consequences of an SBL State Change.
Impact Loss
Trunk(s) No
Cell/BTS(s) Yes (if DTC TCH-RM) No
Signaling Yes (if DTC TCH-RM) Yes (if CPR)
Call Handling Yes (if DTC TCH-RM) Yes (if CPR)
O&M; Capabilities No
Degradation
No
Yes (if CPR)
48 / 778

[33,7] TAKEOVER
Lock CPR/DTC
Test CPR/DTC
Verify CPR/DTC
Unlock CPR/DTC
Alarm solved
no
Alarm persists?
49 / 778
3.6 [33,9] SDCCH-OVRL-BSC

specificProblems eventType probableCause perceivedSeverity Alarm Description PROCESSOR [33] SDCCH-OVRL-BSC [9] Equipment PerformanceDegraded Warning (MI) The load on TCU is excessive due to a high number of simultaneously active SDCCH. 9120 BSC 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.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No Yes
Call Handling No Yes

[33,9] SDCCHOVRLBSC
Remap the RSL to spread the load of SDCCH among other TCUs (flatten hot spots).
Alarm solved
no
Alarm persists?
50 / 778
4 Class 35: N7 Alarms

This section defines the BSC alarms for the Class 35: N7 alarm class.
51 / 778
4.1 [35,0] LNK-REP

specificProblems eventType probableCause perceivedSeverity Alarm Description N7 [35] LNK-REP [0] 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. 9120 BSC 9130 BSC Impact on System 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. For 9120 BSC:The alarm is accompanied by either a SLIP-OV [36,5] or SLIP-UN [36,6] alarm related to the corresponding ATR SBL. For 9130 BSC Evolution: The alarm is accompanied by FRAME-SLIP [101,8] alarm related to the corresponding ATR SBL.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
52 / 778

[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
53 / 778
4.2 [35,2] RTE-REP

specificProblems eventType probableCause perceivedSeverity Alarm Description N7 [35] RTE-REP [2] Communication ResponseTimeExcessive Critical (VPMA) A destination became accessible or inaccessible. The alarm number represents the DPC of the MSC. 9120 BSC 9130 BSC Impact on System 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.the alarm may be raised during TP takeover too; in case of TP takeover, when alarm occurs, access-class are bared only after T_I timer expiration and on-going calls are not affected.
Applicability
See Consequences of an SBL State Change. 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.
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling No No
Call Handling No No
54 / 778

[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?
55 / 778
4.3 [35,3] INC-REP

specificProblems eventType probableCause perceivedSeverity Alarm Description N7 [35] INC-REP [3] Communication ResponseTimeExcessive Indeterminate 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. Applicability 9120 BSC 9130 BSC Impact on System The SBL state is not changed. See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
56 / 778

[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
57 / 778
4.4 [35,4] ASL-REP

specificProblems eventType probableCause perceivedSeverity Alarm Description N7 [35] ASL-REP [4] Communication communicationSubsystemFailure Minor(DMA) this alarm is reported whenever one SCTP association is broken or established. 9130 BSC If begin alarm reported, the SBL will change to FLT, if end alarm reported, the SBL will change to IT.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No Yes
Call Handling No No

None - the SBL normally returns to IT state without operator intervention. Do not run a Disable command because you need to keep trying to initialize it until is successful.
58 / 778
4.5 [35,5] RMH-REP

specificProblems eventType probableCause perceivedSeverity Alarm Description N7 [35] RMH-REP [5] Communication communicationSubsystemFailure Minor(DMA) this alarm is for the feature Multi-Homing and it is only reported for the ASL that has the remote endpoint with 2 IP addresses. It is reported whenever one of the IP addresses status is changed while the SCTP association status keep in traffic. 9130 BSC If begin alarm reported, the SBL will change to FIT, if end alarm reported, the SBL will change to IT.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - the SBL normally returns to IT state without operator intervention. Do not run a Disable command because you need to keep trying to initialize it until is successful.
59 / 778
4.6 [35,6] MSC-REP

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System N7 [35] MSC-REP [6] Communication communicationSubsystemFailure Critical (VPMA) this alarm is reported when there is no IT ASL. 9130 BSC An alarm begin will make SBL change to FLT, it means there is no IT ASL to take traffic, that is the traffic function is not available of this MSC.
Trunk(s) No No
Cell/BTS(s) No No
Signaling Yes No
Call Handling Yes No

[35, 6] MSCREP
yes ASL are disabled? Init ASL
Alarm persists?
no
no
yes
BSCMSC telecom IP connectivity is ok? yes
no Solve IP issues
Alarm persists?
no
Alarm solved
yes
MSC interface/system is ok? yes
no Solve MSC issues
Alarm persists?
no
60 / 778
4.7 [35,7] MSC_DEGRADE

specificProblems eventType probableCause perceivedSeverity Alarm Description N7 [35] MSC_DEGRADE [7] communication communicationSubsystemFailure Minor (DMA) This alarm is most caused by one IP network problem, for one MSC there is not enough IT ASL to take traffic. 9130 BSC An alarm begin will make the SBL change to FIT, it means not enough ASL link to take traffic, and the traffic will be degrade.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No Yes
61 / 778

[35, 7] MSCDEGRADE
If ASL is disabled, init ASL
Alarm persists? yes
no
IP connectivity BSCMSC OK?
no
Solve the IP connectivity BSCMSC
Alarm solved
yes
Alarm persists?
no
yes
62 / 778
5 Class 36: TRUNK Alarms

This section defines the BSC alarms for the Class 36: TRUNK alarm class.
63 / 778
5.1 [36,0] LFA

specificProblems eventType probableCause perceivedSeverity Alarm Description TRUNK [36] LFA [0] 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. 9120 BSC 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.
Trunk(s) No Yes
Cell/BTS(s) No No
Signaling No No

[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?
64 / 778
5.2 [36,3] RAI

specificProblems eventType probableCause perceivedSeverity Alarm Description TRUNK [36] RAI [3] Communication FarEndReceiverFailure Major (PMA) The DTC (9120 BSC) or the TP-GSM (9130 BSC Evolution) has detected a RAI (Remote Alarm Indication) on the Trunk. 9120 BSC 9130 BSC Impact on System Whenever a failure occurs, 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. RAI is the signal sent on the E1 by a remote transmission node as a response to the detection of a fatal transmission fault (AIS, LIS, LFA.). This is the BSC view of transmission, so check for transmission alarms. Note: On 9120 BSC, a local loop test is done by the DTC to verify if the failure is external (EF) or internal (FLT). See Consequences of an SBL State Change.
Applicability
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling No Yes
Call Handling No No
65 / 778

[36,3] RAI
Transmission alarm (LIS, AIS; LFA, EER, BERH) events?
yes
no
no
yes yes
Alarm solved
no
Alarm persists?
66 / 778
5.3 [36,4] AIS

specificProblems eventType probableCause perceivedSeverity Alarm Description TRUNK [36] AIS [4] Communication Ais Major (PMA) The DTC (9120 BSC) or the TP-GSM (9130 BSC Evolution) has detected all ones indication (AIS, Alarm Indication Signal) on the Trunk: Less than four zeros in four consecutive frames means AIS. 9120 BSC 9130 BSC Impact on System 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 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. Note: On 9120 BSC, a local loop test is done by the DTC to verify if the failure is external (EF) or internal (FLT). See Consequences of an SBL State Change.
Applicability
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling No No
67 / 778

[36,4] AIS
yes
no
no
yes no yes
Alarm solved
Alarm persists?
68 / 778
5.4 [36,5] SLIP-OV

specificProblems eventType probableCause perceivedSeverity Alarm Description TRUNK [36] SLIP-OV [5] Equipment TimingProblem Indeterminate 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. 9120 BSC The SBL state remains unchanged. See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
69 / 778

[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
70 / 778
5.5 [36,6] SLIP-UN

specificProblems eventType probableCause perceivedSeverity Alarm Description TRUNK [36] SLIP-UN [6] Equipment TimingProblem Indeterminate 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. 9120 BSC The SBL state remains unchanged. See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
71 / 778

[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?
72 / 778
5.6 [36,7] LOS

specificProblems eventType probableCause perceivedSeverity Alarm Description TRUNK [36] LOS [7] 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. 9120 BSC 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.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling No No
73 / 778

[36,7] LOS
yes
no
no
yes Alarm solved no Alarm persists? yes Contact System Support
74 / 778
5.7 [36,10] CRCA

specificProblems eventType probableCause perceivedSeverity Alarm Description TRUNK [36] CRCA [10] Communication LossOfFrame Indeterminate 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[thinsp]ms. 9120 BSC 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.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling No No
75 / 778

[36,10] CRCA
yes
no
no
76 / 778
5.8 [36,11] CHO-EERH

specificProblems eventType probableCause perceivedSeverity Alarm Description TRUNK [36] CHO-EERH [11] Communication DegradedSignal Indeterminate 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. 9120 BSC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling No No

[36,11] CH0EERH
Transmission alarm (LIS, AIS; LFA, BERH) events?
yes
no
no
77 / 778
5.9 [36,12] CRC4-BERH

specificProblems eventType probableCause perceivedSeverity Alarm Description TRUNK [36] CRC4-BERH [12] Communication ExcessiveBER Major (PMA) This alarm indicates that the BER high measurement based on CRC4 error detection exceeds 10 E-3. 9120 BSC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling No No

[36,12] CRC4BERH
Transmission alarm events?
yes
no
no
78 / 778
5.10 [36,13] CRC4-BERL

specificProblems eventType probableCause perceivedSeverity Alarm Description TRUNK [36] CRC4-BERL [13] 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. 9120 BSC The SBL state remains unchanged. See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - the trunk is functioning at an extremely good rate.
79 / 778
80 / 778
6 Class 38: X.25 Alarms

This section defines the BSC alarms for the Class 38: X.25 alarm class.
81 / 778
6.1 [38,0] MODEM-FLT

specificProblems eventType probableCause perceivedSeverity Alarm Description X.25 [38] MODEM-FLT [0] Communication CommunicationSubsystemFailure Major (PMA) The modem used in the X.25 connection is faulty, or the local terminal power is off. 9120 BSC 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.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
O&M; Capabilities Yes No
82 / 778

[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?
83 / 778
6.2 [38,1] LINK-FLT

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System X.25 [38] LINK-FLT [1] Communication CommunicationProtocolError Major (PMA) The X.25 L2 is disconnected, although the L1 can still be present. 9120 BSC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
O&M; Capabilities No Yes
84 / 778

[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
85 / 778
6.3 [38,2] PROT

specificProblems eventType probableCause perceivedSeverity Alarm Description X.25 [38] PROT [2] 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. 9120 BSC The SBL state remains unchanged.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
86 / 778

[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
87 / 778
88 / 778
7 Class 39: BSC-SW-ANOMALY Alarms

This section defines the BSC alarms for the Class 39: BSC-SW-ANOMALY alarm class.
89 / 778
7.1 [39,1] OSN-NON-RECOVERABLE

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-SW-ANOMALY [39] OSN-NON-RECOVERABLE [1] Processing Error SoftwareError Indeterminate (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. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. The impact depends on the processor type. See Processor Restart [33,0]. See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

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.
90 / 778
7.2 [39,3] OSN-PROCEDURAL

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-SW-ANOMALY [39] OSN-PROCEDURAL [3] Processing Error SoftwareError Indeterminate (MI) An application request of an OSN primitive was passed to the stack with incorrect parameters. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

91 / 778
7.3 [39,5] USR-NONRECOVERABLE

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-SW-ANOMALY [39] USR-NONRECOVERABLE [5] Processing Error SoftwareError Indeterminate (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. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. The impact depends on the processor type. See Processor Restart [33,0]. See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

92 / 778
7.4 [39,7] HWR-NONRECOVERABLE

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-SW-ANOMALY [39] HWR-NONRECOVERABLE [7] Equipment EquipmentMalfunction Indeterminate (MI) The error handler received information concerning a hardware non-recoverable error. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. The impact depends on the processor type. See Processor Restart [33,0]. See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

93 / 778
7.5 [39,18] SANITY-TIMER

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-SW-ANOMALY [39] SANITY-TIMER [18] Processing Error SoftwareProgramAbnormallyTerminated Indeterminate (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. 9130 BSC 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.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

94 / 778
8 Class 42: TELECOM Alarms

This section defines the BSC alarms for the Class 42: TELECOM alarm class.
95 / 778
8.1 [42,1] NACK-MSC

specificProblems eventType probableCause perceivedSeverity Alarm Description TELECOM [42] NACK-MSC [1] Communication ResponseTimeExcessive Indeterminate The BSC did not receive a RESET ACK message from the MSC before expiration of timer T4. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. See Consequences of an SBL State Change. The BSC repeats the reset procedure indefinitely until the MSC sends a positive acknowledgment.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
96 / 778

[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?
97 / 778
8.2 [42,2] OVERLOAD-MSC

specificProblems eventType probableCause perceivedSeverity Alarm Description TELECOM [42] OVERLOAD-MSC [2] Quality of Service Congestion Indeterminate An overload message was received from the MSC and this triggered an overload reaction. While timer T17 remains activated after receipt of an overload message, it inhibits the effect of any further overload messages. When timer T17 expires, overload messages provoke traffic reduction again. When A-FLEX is activated, the alarm which applies is [42,16] MSC-TRAFFIC-REDUCTION, number 1 9120 BSC 9130 BSC 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.
Applicability
Trunk(s) No No
Cell/BTS(s) No Yes
Signaling No No

None - an autonomous overload reaction is triggered.
98 / 778
8.3 [42,3] START-RESET

specificProblems eventType probableCause perceivedSeverity Alarm Description TELECOM [42] START-RESET [3] Quality of Service PerformanceDegraded Indeterminate 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). 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. All calls are cleared in the BSC. See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
99 / 778

[42,3] STARTRESET
Local communication alarm events?
yes
no
Trigger action on MSC side
Alarm solved
no
Alarm persists?
100 / 778
8.4 [42,7] NO-RESET-CIC

specificProblems eventType probableCause perceivedSeverity Alarm Description TELECOM [42] NO-RESET-CIC [7] Communication ResponseTimeExcessive Indeterminate 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. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. This A-channel is released internally by the BSC. See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
101 / 778

[42,7] NORESETCIC
Transmission or trunk alarm events?
yes
no
Trigger CIC recovery action at MSC side
Alarm solved
no
Alarm persists?
102 / 778
8.5 [42,9] OVERLOAD-BSC

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability TELECOM [42] OVERLOAD-BSC [9] Equipment ProcessorProblem Major (PMA) This alarm is sent by the BSC to report an BSC processor overload. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. The BSC is overloaded. See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No

[42,9] OVERLOADBSC
Processor related board alarm events?
yes
no
103 / 778
8.6 [42,12] TEL-PAIR-LOST

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability TELECOM [42] TEL-PAIR-LOST [12] Equipment EquipmentMalfunction Critical (VPMA) This is the ID of the TCH-DTC pair lost. 9120 BSC 9130 BSC Impact on System This alarm is issued because there happened a state change of one DTC. Since the TCH-DTC pairs handles calls, all calls handled by this pair are lost and all cells managed by this pair cannot anymore establish calls. All these cells are disabled.
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling No Yes
Call Handling Yes Yes
104 / 778

[42,12] TELPAIRLOST
9130 BSC Evolution
9130 Evolution or 9120 BSC?
9120 BSC
Contact System Support Any DTC was reset?
no
Lock reported DTC
Test reported DTC
yes Verify reported DTC
Wait for DTC restart
Alarm persists?
yes
Unlock reported DTC
no no Alarm solved Alarm persists?
yes
Onsite
Alarm solved
Replace reported faulty DTC
no
Alarm persists?
yes
105 / 778
8.7 [42,13] BSC-TRAFFIC-REPORT

specificProblems eventType probableCause perceivedSeverity Alarm Description TELECOM [42] BSC-TRAFFIC-REPORT [13] Quality of Service Congestion Indeterminate 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). 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. MSs belonging to the barred access classes can no longer access the system. This corresponds to a modification of the barred MS classes (either increase, or decrease). Additionnal info give the current status.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
106 / 778

[42,13] BSCTRAFFICREPORT
Analyze additional information bytes
Related alarm events?
yes
107 / 778
8.8 [42,14] GPRS-RESET

specificProblems eventType probableCause perceivedSeverity Alarm Description TELECOM [42] GPRS-RESET [14] Processing Error SoftwareError Indeterminate 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. To get the origin of the GPRS reset, the alarm number shall reflect the origin , in the following way: 0. Resumed reset due to S_CPR take-over, original trigger is unknown 1. All GSL links are down (detected by TSM_GPRS) 2. No DTC GPRSAP available (very unprobable)or all GSL links are down(detected by GPRSAP/GOM ). (TSM_GPRS receives message 1260 ) 3. Lack of acknowledgment received from MFS on some special BSCGP messages(BSS TRAFFIC CONTROL after 2 repetitions). 4. Loss of a pair of TCH_RM 5. RESET triggered by MFS. (This covers the BSC RESET triggered by MFS following BSC SW activation, or a BSC reset as MFS sees loss of GSL for a while, or a BSC RESET when MFS can not receive acknowledement on some special BSCGP message,even after several repetitions) This alarm is used when a reset command arrives from the MFS, or when the BSC sends a reset command to the MFS because all GSL, or all GPRS application processes, or a TCH_RM pair is/are down. Cause 6: MFS version is changed. Cause 7: BSC could not receive STATE CHANGE ACK from MFS in time. Cause 8.TSM_GPRS start the Abis configuration indicaiton. Normally there will be a Abis configuration indication ACK comes form MFS as feedback, but if there is no Abis configuration indication ACK, CAUSE 8 raised. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. A reset of the MFS affects GPRS functionality only.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No Yes
108 / 778

None - an autonomous reset is triggered.
109 / 778
8.9 [42,15] TCH-RM-FAULT

specificProblems eventType probableCause perceivedSeverity Alarm Description TELECOM [42] TCH-RM-FAULT [15] Equipment EquipmentMalfunction Critical (VPMA) This alarm happens when the TCH-RM processes on both OMCP are faulty 9130 BSC This alarm is issued because there happened a state change of TCH-RM DTC. Since the TCH-DTC pairs handles calls, all calls are lost and all cells cannot anymore establish calls. All these cells are disabled.
Trunk(s) YES NO
Cell/BTS(s) YES NO
Signaling YES NO
Call Handling YES NO
O&M; Capabilities NO NO

110 / 778
8.10 [42,16] MSC-TRAFFIC-REDUCTION

specificProblems eventType probableCause perceivedSeverity Alarm Description TELECOM [42] MSC-TRAFFIC-REDUCTION [16] Quality of Service congestion Major (PMA) This alarm indicates that the MSC load balance status has been changed for the feature A-Flex:the MSC is excluded or included in the load balance from BSC point view. Alarm number 1 is raised In case the MSC is excluded due to overload; Alarm number 2 is raised in case the MSC is excluded due to the operator requested off-loading; Alarm number 3 is raised in case the MSC is excluded due to the Telecom reset 9130 BSC If begin alarm reported, the SBL will change to FIT, if end alarm reported, the SBL will change to IT.
Trunk(s) No No
Cell/BTS(s) No No
Signaling Yes No
111 / 778

[46, 12] MSCTRAFFICREDUCTION
None an autonomous overload reaction is triggered
1 Alarm Type?
2 Alarm triggered by the operator
Local communication alarm events?
yes
no
Trigger action on MSC side
Alarm solved
no
Alarm persists?
yes
112 / 778
9 Class 43: CELL Alarms

This section defines the BSC alarms for the Class 43: CELL alarm class.
113 / 778
9.1 [43,0] LOSS-OF-BCCH

specificProblems eventType probableCause perceivedSeverity Alarm Description CELL [43] LOSS-OF-BCCH [0] Quality of Service PerformanceDegraded Major (PMA), Warning if out of commercial use The transceiver time slot configured to carry the BCCH is unavailable for telecommunication purposes. 9120 BSC 9130 BSC Impact on System 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, if BCCH channel is recovered, the SBL state will change to IT, if BCCH channel isnt recovered, the SBL state will change to FLT.
Applicability
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No
114 / 778

[43,0] LOSSOFBCCH
Wait 5 min (BCCH recovery ongoing)
Related BTS alarms?
yes
Solve this alarms
Alarm persists?
no
no
yes
Related transmission alarms? no
yes
Solve this alarms
Alarm persists?
no
yes
Related BSC alarms? no
yes
Solve this alarms
Alarm persists?
no
yes
Lock / unlock Cell in RNUSM
Alarm solved
Error message in follow up window? no
yes
Solve this problem
Alarm persists?
no
yes
Alarm persists?
Lock / unlock RA
Alarm persists?
no
no Alarm solved
yes
Modify BCCH frequency
Alarm persists?
no
yes
115 / 778
9.2 [43,1] LOSS-OF-SDCCH

specificProblems eventType probableCause perceivedSeverity Alarm Description CELL [43] LOSS-OF-SDCCH [1] Quality of Service PerformanceDegraded Minor (DMA), Warning if out of commercial use One or more transmission time slots configured to carry the SDCCH are unavailable for telecommunication purposes. 9120 BSC 9130 BSC Impact on System 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 StateChange, if SDCCH channel is recovered, the SBL state will change to IT, if SDCCH channel isnt recovered, the SBL state will change to FIT.
Applicability
Trunk(s) No No
Cell/BTS(s) No Yes
Signaling No Yes
116 / 778

[43,1] LOSSOFSDCCH
Related BTS alarm events?
yes
Trigger maintenance action on that alarm(s)
no no Alarm persists?
Alarm solved
117 / 778
9.3 [43,2] LOSS-OF-TCH

specificProblems eventType probableCause perceivedSeverity Alarm Description CELL [43] LOSS-OF-TCH [2] Quality of Service PerformanceDegraded Minor (DMA), Warning if out of commercial use One or more transceiver time slots configured to carry the TCH are unavailable for telecommunication purposes. 9120 BSC 9130 BSC Impact on System 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, the SBL state will change to FIT.
Applicability
Trunk(s) No No
Cell/BTS(s) No Yes
Signaling No No
118 / 778

[43,2] LOSSOFTCH
More TRX as TRE/RSL?
yes
Correct cell configuration
Alarm persists?
no
no
yes
Identify the faulty RSL / TRE in USD window
Lock / unlock the faulty RSL / TRE
Alarm persists?
no
Alarm solved
yes
yes Related BTS alarms? Solve this alarms
Alarm persists?
no
no
yes
yes Related BSC alarms? Solve this alarms
Alarm persists?
no
no
yes
119 / 778
9.4 [43,3] LOSS-OF-ALL-CHAN

specificProblems eventType probableCause perceivedSeverity Alarm Description CELL [43] LOSS-OF-ALL-CHAN [3] Quality of Service PerformanceDegraded Major (PMA), Warning if 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. 9120 BSC 9130 BSC 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.
Applicability
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling No No
120 / 778

[43,3] LOSSOF ALLCHAN
Related BTS alarms? no
yes
Solve this alarms
Alarm persists? yes
no
Related transmission alarms? no
yes
Solve this alarms
Alarm persists? yes
no
Related BSC alarms? no
yes
Solve this alarms
Alarm persists? yes
no
no yes OML failed? Lock/Unlock OML yes Check BTS and power supply Alarm persists? yes no
OML failed?
no
All BTS cells are impacted? no
yes
Reset BTS
Alarm persists? yes
no
Contact System Support no Alarm solved
Identify the faulty RSL / TRE in USD window
Lock / unlock the faulty RSL / TRE Reset related TCU
Alarm persists?
yes
Lock / unlock Cell in RNUSM
Error message in follow up window? no
yes
Solve this problem
Alarm persists? yes
no
Alarm persists?
yes
Lock / unlock RA
Alarm persists?
no
no
yes Delete / recreate cell
Alarm solved
yes
Alarm persists?
no
121 / 778
9.5 [43,4] CELL-TRAFFIC-REPORT

specificProblems eventType probableCause perceivedSeverity Alarm Description CELL [43] CELL-TRAFFIC-REPORT [4] Quality of Service PerformanceDegraded Indeterminate 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 in case of 9120 BSC *There is a change of the RACH parameters on cell level (dynamic RACH). 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. MSs belonging to the barred access classes can no longer access the system.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
122 / 778

[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
123 / 778
9.6 [43,5] OVERLOAD-BTS

specificProblems eventType probableCause perceivedSeverity Alarm Description CELL [43] OVERLOAD-BTS [5] Quality of Service Congestion Indeterminate 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. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. MSs belonging to the barred access classes can no longer access the system.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
124 / 778

[43,5] OVERLOADBTS
yes
no
TCU alarm events?
yes
Solve that alarm(s)
125 / 778
9.7 [43,6] TRX-MAPPING-CHANGE

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability CELL [43] TRX-MAPPING-CHANGE [6] congestion/network fail Indeterminate This event alarm is indicate TRX/RSL mapping is changed or not. 9120 BSC 9130 BSC Impact on System No impact.
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
O&M; Capabilities no no

None.
126 / 778
9.8 [43,248] CONFIGURED POOLS NOT FULLY USABLE

specificProblems eventType probableCause perceivedSeverity Alarm Description CELL [43] CONFIGURED POOLS NOT FULLY USABLE [248] Quality of Service performanceDegraded Minor (DMA), Warning if out of commercial use 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 9100 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. Note: this alarm can only be sent by a B8 BSS. Applicability 9120 BSC 9130 BSC 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) No No
Cell/BTS(s) No Yes
Signaling No No
Call Handling No No
127 / 778

[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?
128 / 778
10 Class 44: BTS-OM Alarms

This section defines the BSC alarms for the Class 44: BTS-OM alarm class.
129 / 778
10.1 [44,0] AUDIT-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-OM [44] AUDIT-FAIL [0] Communication CommunicationSubsystemFailure Minor (DMA), Warning if out of commercial use 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. 9120 BSC 9130 BSC 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.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
130 / 778

[44,0] AUDITFAIL
Reset BTS or OML TCU
no OML up?
yes
No operator action required
Alarm solved
no
Alarm persists?
131 / 778
10.2 [44,1] PROTOCOL-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-OM [44] PROTOCOL-FAIL [1] Communication CommunicationProtocolError Minor (DMA), Warning if out of commercial use A protocol failure on the Abis interface occurred. An ACK to some message was not received after three retries. 9120 BSC 9130 BSC Impact on System 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.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
132 / 778

[44,1] PROTOCOLFAIL
Other BTS alarms are active?
yes Solve BTS alarms
no
no OML link is up?
Lock/Unlock OML and reset OML TCU
yes OML link is up?
yes
no
Check BTS and power supply
Alarm solved
Alarm persists?
no
133 / 778
10.3 [44,2] RECONFIG-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-OM [44] RECONFIG-FAIL [2] Processing Error ConfigurationOrCustomizationError Minor (DMA), Warning if out of commercial use 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. 9120 BSC 9130 BSC Impact on System 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.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
134 / 778

[44,2] RECONFIGFAIL
Reset BTS or OML TCU
no OML up?
yes
Alarm solved
no
Alarm persists?
No operator action required
yes
135 / 778
10.4 [44,3] DOWNLOAD-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-OM [44] DOWNLOAD-FAIL [3] Processing Error ConfigurationOrCustomizationError Minor (DMA), Warning if out of commercial use Three download attempts failed. Any failure from BTS-DOWNLOAD-REQ until a successful BTS-DOWNLOAD-REP is considered a download failure. 9120 BSC 9130 BSC Impact on System 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.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
136 / 778

[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
137 / 778
10.5 [44,5] SW-ACTIVATE-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-OM [44] SW-ACTIVATE-FAIL [5] Processing Error ConfigurationOrCustomizationError Minor (DMA), Warning if out of commercial use This configuration failure alarm indicates that a software activation failed following a download attempt. 9120 BSC 9130 BSC Impact on System 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.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
138 / 778

[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
139 / 778
10.6 [44,6] CONFIG-DATA-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-OM [44] CONFIG-DATA-FAIL [6] Processing Error ConfigurationOrCustomizationError Minor (DMA), Warning if out of commercial use There is a problem with the configuration data because of a logical parameter modification or the restart of the BTS or OMU. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
140 / 778

[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?
141 / 778
10.7 [44,7] OMU-SELFTEST-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability BTS-OM [44] OMU-SELFTEST-FAIL [7] Equipment EquipmentMalfunction Minor (DMA), Warning if out of commercial use The OMU failed its self-test. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
142 / 778

[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
143 / 778
10.8 [44,10] ABORT-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-OM [44] ABORT-FAIL [10] Processing Error ConfigurationOrCustomizationError Minor (DMA), Warning if out of commercial use The Abort failure alarm indicates that the attempt to remove the preloaded BTS software files has failed. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[44,10] ABORT FAIL
Retrigger remove action
Alarm solved
no
Alarm persists?
144 / 778
10.9 [44,11] PRELOAD-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability BTS-OM [44] PRELOAD-FAIL [11] Processing Error ConfigurationOrCustomizationError Minor (DMA), Warning if out of commercial use This alarm indicates that preloading of the BTS software has failed. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
145 / 778
146 / 778
10.10 [44,12] BTS-HW-CONFIG-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-OM [44] BTS-HW-CONFIG-FAIL [12] Equipment ConfigurationOrCustomizationError Minor (DMA), Warning if out of commercial use 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. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[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
147 / 778
148 / 778
11 Class 45: CHANNEL Alarms

This section defines the BSC alarms for the Class 45: CHANNEL alarm class.
149 / 778
11.1 [45,0] CH-UNBLOCK-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description CHANNEL [45] CH-UNBLOCK-FAIL [0] 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. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No Yes
Cell/BTS(s) No No
Signaling No Yes
150 / 778

[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
151 / 778
11.2 [45,1] CH-BLOCK-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description CHANNEL [45] CH-BLOCK-FAIL [1] Communication CommunicationProtocolError Indeterminate A timeout expired for the MSC to send an acknowledgement to the BSC in response to an A-channel blocking message. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No Yes
152 / 778

[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
153 / 778
11.3 [45,2] BSC-CIC-UNKNOWN

specificProblems eventType probableCause perceivedSeverity Alarm Description CHANNEL [45] BSC-CIC-UNKNOWN [2] Processing Error ConfigurationOrCustomizationError Indeterminate 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. 9120 BSC 9130 BSC 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.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No Yes
154 / 778

[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
155 / 778
11.4 [45,3] MSC-CIC-UNKNOWN

specificProblems eventType probableCause perceivedSeverity Alarm Description CHANNEL [45] MSC-CIC-UNKNOWN [3] Processing Error ConfigurationOrCustomizationError Indeterminate The MSC initiated a request. The request specifies a circuit which is unequipped in the BSC. 9120 BSC 9130 BSC Impact on System 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.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No Yes
156 / 778

[45,3] MSCCIC UNKNOWN
Lock aossc. Atrunk
Alarm persists?
no
Alarm solved
157 / 778
11.5 [45,4] END-OF-REP-OF-UNBLOCK-PROC

specificProblems eventType probableCause perceivedSeverity Alarm Description CHANNEL [45] END-OF-REP-OF-UNBLOCK-PROC [4] Communication CommunicationProtocolError Critical (VPMA) The number of unblock requests exceeded a predefined number of allowable attempts (i.e. 255). 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No Yes
Cell/BTS(s) No No
Signaling No Yes

[45,4] ENDOFREP OFUBLOCKPROC
Lock aossc. ACH
Alarm persists?
no
Alarm solved
158 / 778
12 Class 46: BACKUP-MEDIUM Alarms

This section defines the BSC alarms for the Class 46: BACKUP-MEDIUM alarm class.
159 / 778
12.1 [46,0] SYNC CORRUPTED

specificProblems eventType probableCause perceivedSeverity Alarm Description BACKUP-MEDIUM [46] SYNC CORRUPTED [0] Processing Error 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. 9120 BSC 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.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - wait for the next twin file update. See Other BSC Alarms (Section 36.4) for the byte definition.
160 / 778
12.2 [46,1] UNSYNC-OTHER-CORR

specificProblems eventType probableCause perceivedSeverity Alarm Description BACKUP-MEDIUM [46] UNSYNC-OTHER-CORR [1] Processing Error 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. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. Some previously acknowledged commands are lost. CPRA (DUPLEX): Performance Management Telecom functions are not affected, but PM is impacted. If some updates are to be done on the active CPRA, then the standby CPRA 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 tais 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.
Applicability
161 / 778
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling
O&M; Capabilities Yes

[46,1] UNSYNC OTHERCORR
Resynchronize OMCR with BSC by performing an audit
Repeat the lost transactions
Alarm persists?
no
Alarm solved
162 / 778
12.3 [46,2] UNSYNC-OWN-CORR

specificProblems eventType probableCause perceivedSeverity Alarm Description BACKUP-MEDIUM [46] UNSYNC-OWN-CORR [2] Processing Error SoftwareProgramAbnormallyTerminated Warning (MI) This alarm occurs when the twin file on the other CPRA is not synchronized and a twin file update is successful on the other CPRA but failed on the own CPRA. The twin file status is changed to unsynchronized own corrupted and the alarm is generated. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged
Applicability
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
O&M; Capabilities no yes

None - wait for the next twin file update.
163 / 778
12.4 [46,3] SYNC-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description BACKUP-MEDIUM [46] SYNC-FAIL [3] Processing Error SoftwareProgramAbnormallyTerminated Warning (MI) This alarm occurs when its trying to synchronize the unsynchronized twin files on both OCPR and SCPR during initilization period, but the result is unsucessful. And the twin file status is still keeping as the original status without unchange. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged
Applicability
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
O&M; Capabilities no yes

None - wait for the next twin file update.
164 / 778
12.5 [46,4] SECFILE-ROLLBACK

specificProblems eventType probableCause perceivedSeverity Alarm Description BACKUP-MEDIUM [46] SECFILE-ROLLBACK [4] Processing Error 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. 9120 BSC 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.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling
165 / 778

[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
166 / 778
12.6 [46,5] SINGLE-UPD-ROLLBACK

specificProblems eventType probableCause perceivedSeverity Alarm Description BACKUP-MEDIUM [46] SINGLE-UPD-ROLLBACK [5] Processing Error 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. 9120 BSC 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.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling
167 / 778

[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
168 / 778
12.7 [46,6] DUT-ROLLBACK-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description BACKUP-MEDIUM [46] DUT-ROLLBACK-FAIL [6] Processing Error 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. 9120 BSC 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.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling
169 / 778

[46,6] DUT ROLLBACKFAIL
Retrigger the data update
Alarm persists?
no
Alarm solved
170 / 778
12.8 [46,7] DISC-OOS

specificProblems eventType probableCause perceivedSeverity Alarm Description BACKUP-MEDIUM [46] DISC-OOS [7] 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. 9120 BSC Telecom functions are not affected. See Consequences of an SBL State Change.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling
171 / 778

[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?
172 / 778
12.9 [46,8] DISC-PARITY-ERROR

specificProblems eventType probableCause perceivedSeverity Alarm Description BACKUP-MEDIUM [46] DISC-PARITY-ERROR [8] Equipment InputOutputDeviceError Minor (DMA) During a restart/reload/reboot, the SSD on the standby S-CPRA was checked and a parity error was detected. 9120 BSC Telecom functions are not affected. See Consequences of an SBL State Change.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling
173 / 778

[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?
174 / 778
13 Class 47: GLOBAL-BSC Alarms

This section defines the BSC alarms for the Class 47: GLOBAL-BSC alarm class.
175 / 778
13.1 [47,2] AUTO-BSC-RESET

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] AUTO-BSC-RESET [2] Processing Error SoftwareProgramAbnormallyTerminated Indeterminate (MI) An autonomous reboot/reset of the BSC occurred. The alarm is always sent to both the OMC-R and the local terminal. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. The impact depends on what has occurred, as described above. See Processor Reset [33,1].
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

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

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] AUTO-BSC-RESTART [3] Processing Error SoftwareProgramAbnormallyTerminated Indeterminate (MI) The BSC was successfully restarted from the OMC-R or BSC local terminal. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. The impact depends on what has occurred, as described above. See processor restart [33,0].
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - this information is always sent after an autonomous restart of the BSC.
177 / 778
13.3 [47,4] BSC-SYNC-REQ

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] BSC-SYNC-REQ [4] Communication CommunicationSubsystemFailure Indeterminate (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 for 9120 BSC or the Ethernet link for 9130 BSC Evolution is down * The OMC-R is not active. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - on reception of the alarm, the OMC-R starts a BSC alarm audit.
178 / 778
13.4 [47,5] BTS-SYNC-REQ

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] BTS-SYNC-REQ [5] Communication CommunicationSubsystemFailure Indeterminate (MI) An overflow may occur on an OMC-R interface if: * There is no OSI CPRA * The X.25 link for 9120 BSC or the Ethernet link for 9130 BSC Evolution is down * The OMC-R is not active. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None on reception of the alarm, the OMC-R starts a BTS alarm audit.
179 / 778
13.5 [47,6] AUDIT-COMPLETED

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] AUDIT-COMPLETED [6] Processing Error SoftwareProgramAbnormallyTerminated Indeterminate (MI) The BSC was successfully reset or restarted from the OMC-R or BSC local terminal. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. The impact depends on what has occurred, as described above. See Processor Reset [33,1].
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

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

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] BSC-HW-RESYNC [7] Equipment Indeterminate Indeterminate (MI) This alarm is generated after BSC extension or reduction. The BSC sends this alarm to the OMC-R. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

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

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System GLOBAL-BSC [47] AIFL-FULL [8] Equipment EquipmentMalfunction Indeterminate (MI) The BSC alarms list is full. 9120 BSC The SBL state remains unchanged.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[47,8] AIFLFULL
System generates too many alarms in short time period?
no
Solve remaining alarms
Alarm solved
182 / 778
13.8 [47,9] CBC-CONNECTION-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] CBC-CONNECTION-FAILURE [9] Equipment EquipmentMalfunction Major (PMA) The Alarm is reported in the following cases: 1. Network connection Timeout 2. Network connection Refused. 3 .The CBC O/G association setup timeout 4. The CBC O/G association setup refused(invalid ID or password) 5. CBC O/G association prematurely terminated internally or externally 9120 BSC 9130 BSC Impact on System CBC function cant be implemented and consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
183 / 778

[47,9] CBC CONNECTIONFAILURE
Network configuration is ok?
no
Correct network configuration
Alarm persists?
no
yes
yes
Launch SMSCB CMDMODE STOP then START CMDMODE
Alarm persists?
no
Alarm solved
yes
184 / 778
13.9 [47,11] ABIS-TS-ALLOC-FAILED

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] ABIS-TS-ALLOC-FAILED [11] Processing Error ConfigurationOrCustomizationError Indeterminate (MI) This alarm is raised to indicate that TS allocation in the case of auto-detection of a TRE has failed. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. The TRE detected via the Audit will not be operational, no TSs will be allocated.
Applicability
Trunk(s) No No
Cell/BTS(s) No Yes
Signaling No Yes

[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
185 / 778
13.10 [47,12] INSUFFICIENT-TCU-RES

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] INSUFFICIENT-TCU-RES [12] Processing Error ConfigurationOrCustomizationError Indeterminate (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. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. The TRE detected via the Audit will not be operational, no TCU will be allocated.
Applicability
Trunk(s) No No
Cell/BTS(s) No Yes
Signaling No Yes

[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
186 / 778
13.11 [47,13] TRE-SECTOR-MISMATCH

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] TRE-SECTOR-MISMATCH [13] Processing Error ConfigurationOrCustomizationError Indeterminate (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. 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged. The TRE is not operational.
Applicability
Trunk(s) No No
Cell/BTS(s) No Yes
Signaling No Yes
187 / 778

[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
188 / 778
13.12 [47,14] LACK-OF-TCU-SPACE

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] LACK-OF-TCU-SPACE [14] Quality of Service UnderlyingResourceUnavailable Indeterminate (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. 9120 BSC 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.
Trunk(s) No No
Cell/BTS(s) No Yes
Signaling No Yes

[47,14] TCU TOO FRAGMENTED
Reshuffle TCUs via Compact RSL/TCU remapping and Manually addon the TRE on BSC
Alarm persists?
no
Alarm solved
189 / 778
13.13 [47,15] SWRPL-IN-PROGRESS

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] SWRPL-IN-PROGRESS [15] Equipment Indeterminate Indeterminate (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. 9120 BSC 9130 BSC Impact on System 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.
Applicability
Trunk(s) No No
Cell/BTS(s) No Yes
Signaling No Yes
190 / 778

[47,15] SWRPL INPROGRESS
Wait for new autonomous audit
If no audit is started, trigger new audit
Alarm persists?
no
Alarm solved
191 / 778
13.14 [47,16] MAX-TRE-EXCEEDED

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] MAX-TRE-EXCEEDED [16] Equipment Congestion Indeterminate (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. 9120 BSC 9130 BSC Impact on System 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.
Applicability
Trunk(s) No No
Cell/BTS(s) No Yes
Signaling No Yes
192 / 778

[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
193 / 778
13.15 [47,17] MLPPP-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] MLPPP-FAILURE [17] Communication CommunicationSubsystemFailure Critical (VPMA) The IP link defined on the Ater interface is not available following failure of all the PPP links created to carry it. 9130 BSC The impacted SBL state is not changed. The MxBSC is connected to the CBC and the OMC-R through an IP link. If the IP link is defined over the Ater interface it is carried by several PPP links using a timeslot of the Ater interface. When all PPP links become faulty, the connection between the BSC and the other entity is broken. When this failure situation occurs, the BSC is 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.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
194 / 778

[47, 17] MLPPPFAILURE
E1 links to MSC are ok?
no
Fix E1 links to MSC problems
Alarm persists?
no
yes
yes
E1 path to PPP router is ok?
no
Fix E1 links to PPP router problems
Alarm persists?
no
Alarm solved
yes
yes
PPP router is ok?
no
Fix PPP router problems
Alarm persists?
no
yes
yes
195 / 778
13.16 [47,18] MLPPP-PARTIAL-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] MLPPP-PARTIAL-FAILURE [18] Communication CommunicationSubsystemFailure Minor (DMA) At least one PPP link defined to carry IP on Ater has failed, but the link is still available. 9130 BSC The impacted SBL state is not changed. The MxBSC is connected to the CBC and the OMC-R through an IP link. If the IP link is defined over the Ater interface it is carried by several PPP links using a timeslot of the Ater interface. When some PPP links become faulty (but not all), the connection between the BSC and the other entity is kept but the bandwidth is reduced. O&M congestion may happen. There may be simultaneous transmission alarms on A or on Atermux which can be at the origin of this alarm. If there are none, the origin of the problem is at MSC side.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
196 / 778

[47, 18] MLPPPPARTIALFAILURE
E1 links to MSC are ok?
no
Fix E1 links to MSC problems
Alarm persists?
no
yes
yes
E1 path to PPP router is ok?
no
Fix E1 links to PPP router problems
Alarm persists?
no
Alarm solved
yes
yes
PPP router is ok?
no
Fix PPP router problems
Alarm persists?
no
yes
yes
197 / 778
13.17 [47,19] DLS-RESTORATION

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] DLS-RESTORATION [19] Processing Error CorruptData Indeterminate (MI) S-CPR VCE cannot start due to a corruption of the DLS. A previous version of the DLS has been restored. 9130 BSC The impacted SBL state is not changed. The restored BSC DLS is several days or several weeks old. The BSS configuration it contains may be obsolete and inconsistencies with the rest of the network can appear and have to be solved by the operator. Regarding Logical parameters, it is possible to trigger "force config" operation from OMC-R to correct all radio parameters. Regarding Hardware Management, the BSC will impose its view. There is no other way that replays operations from OMC-R. Alarms will point out which BTS need immediate correction. But even without alarm, operator has to take care to reconfigure the BSC.
Impact Loss
Trunk(s) If config changed No
Cell/BTS(s) If config changed No
Signaling If config changed No
Call Handling If config changed No
O&M; Capabilities If config changed
Degradation
No

Contact your Alcatel system support so the cause of the error can be examined. The information must be analyzed by qualified personnel.
198 / 778
13.18 [47,20] NTP-DRIFT-TIME-ALERT

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] NTP-DRIFT-TIME-ALERT [20] Processing Error TimingProblem Minor (DMA) The active OMCP has detected that there is a time drift of more than 100s with the time server defined in the peer entities. 9130 BSC The impacted SBL state is not changed. During operations like SBL reset or unlock OMC-R cleans up the list of alarms for the impacted SBL. The clean up is done per comparison between the OMC-R time of the operation and the BSC timestamps of alarms. So the time drift between the BSC and the NTP server may lead to inconsistencies in alarm status between BSC and OMC-R. PM file reporting may also be not synchronized. But the operational impact is null. PM file reporting may also be not synchronized. But the operational impact is null.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
199 / 778

[47, 20] NTP DRIFT TIME ALERT
NTP time server settings in BSC are ok?
no
Correct NTP time server settings in BSC
Alarm persists?
no
yes
yes
Alarm solved
Time setting in time server is ok?
no
Correct time setting in time server
Alarm persists?
no
yes
yes
Wait for time gap to dissapear or reset BSC
Alarm persists?
no
yes Replace OMCP board that is active when alarm occurs
Alarm solved
Alarm persists? yes
no
200 / 778
13.19 [47,21] NTP-TIME-SERVER-UNREACHABLE

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System GLOBAL-BSC [47] NTP-TIME-SERVER-UNREACHABLE [21] Processing Error TimingProblem Minor (DMA) The NTP timer server defined in the MxBSC peer entity is unreachable. 9130 BSC The impacted SBL state is not changed. During operations like SBL reset or unlock OMC-R cleans up the list of alarms for the impacted SBL. The clean up is done per comparison between the OMC-R time of the operation and the BSC timestamps of alarms. So the time drift between the BSC and the NTP server may lead to inconsistencies in alarm status between BSC and OMC-R. PM file reporting may also be not synchronized. But the operational impact is null. PM file reporting may also be not synchronized. But the operational impact is null.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
201 / 778

[47, 21] NTP TIME SERVER UNREACHABLE
NTP time no server settings in BSC are ok?
Alarm persists?
no
yes
yes
no
Alarm persists?
no
Alarm solved
yes
yes
Ethernet netwrk settings are ok?
no
Correct Ethernet network settings
Alarm persists?
no
yes
202 / 778
13.20 [47,22] NTP-DRIFT-TIME-EXCEEDED

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] NTP-DRIFT-TIME-EXCEEDED [22] Processing Error TimingProblem Major (PMA) The active OMCP has detected that there is a time drift of more than 1000s with the time server defined in the peer entities. 9130 BSC After NTP drift exceeded 1000 sec. MXBSC started to reset that lead to traffic outage. The impacted SBL state is not changed. During operations like SBL reset or unlock OMC-R cleans up the list of alarms for the impacted SBL. The clean up is done per comparison between the OMC-R time of the operation and the BSC timestamps of alarms. So the time drift between the BSC and the NTP server may lead to inconsistencies in alarm status between BSC and OMC-R.PM file reporting may also be not synchronized. But the operational impact is null. PM file reporting may also be not synchronized. But the operational impact is null.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
203 / 778

[47, 22] NTP DRIFT TIME EXCEEDED
NTP time no server settings in BSC are ok?
Alarm persists?
no
yes
yes
no
Alarm persists?
no
Alarm solved
yes
yes
Replace OMCP board that is active when alarm occurs
Alarm persists?
no
yes
204 / 778
13.21 [47,23] MAX-HDLC-EXCEEDED

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] MAX-HDLC-EXCEEDED [23] Processing Error TimingProblem Indeterminate (MI) During TRE auto-detection mechanism, no HDLC handler can be allocated for the RSL on the TP-GSM board. 9130 BSC The impacted SBL state is not changed. The new TRE detected during the BSC/BTS audit are not operational because there is no more HDLC controller available to handle the RSL
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
205 / 778

[47, 23] MAX HDLC EXCEEDED
Perform one of the following actions to clear the alarm
Change the multiplexing mode of the BTS where the TREs were added
Change the multiplexing mode of another BTS
Move the impacted BTS or other BTS to another BSC
Alarm persists?
no
Alarm solved
206 / 778
13.22 [47,24] MUX-SECTOR-NOT-COMP-2ABIS

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] MUX-SECTOR-NOT-COMP-2ABIS [24] Processing Error ConfigurationOrCustomizationError Indeterminate During TRE allocation, there is no enough space on primary abis link, the TRE cannot be allocated on secondary abis link because the multiplexing mode is per sector 9120 BSC 9130 BSC Impact on System The SBL state remains unchanged The TRE will not be operational, no TS will be allocated
Applicability
Trunk(s) NO NO
Cell/BTS(s) NO YES
Signaling NO YES
Call Handling NO YES
O&M; Capabilities NO YES

[47,24] MUXSECTORNOT COMP2ABIS
Delete existing TRE(s)
Recreate TRE(s) according to Abis capacity
Alarm persists?
no
Alarm solved
207 / 778
13.23 [47,25] TC-HW-RESYNCH

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] TC-HW-RESYNCH [25] Processing Error EquipmentMalfunction Minor (DMA) Consider new MT120 boards introduction. The BSC has to discover them at MT120 replacement at TC extension or at periodical audit. At the end of the discovery phase, if the BSC detects any discrepancies with the DLS, the BSC sends an alarm to the OMC. 9130 BSC The SBL state remains unchanged.
Trunk(s) No NO
Cell/BTS(s) No NO
Signaling No NO
Call Handling No NO
O&M; Capabilities NO Yes

[47, 25] TCHWRESYNCH
Alarm persists?
no
Alarm solved
yes
208 / 778
13.24 [47,26] TRAU-CP-OUT-OF-RANGE

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System GLOBAL-BSC [47] TRAU-CP-OUT-OF-RANGE [26] Processing Error EquipmentMalfunction Minor (DMA) ID OF MT120 is our of valid range 9130 BSC ID OF MT120 is our of valid range
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[47, 26] TRAUCPOUT_OFRANGE
Check TC rack at TC side
Alarm persists?
no
Alarm solved
yes
209 / 778
13.25 [47,27] TRAU-CP-ON-DEDICATED-ATER

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System GLOBAL-BSC [47] TRAU-CP-ON-DEDICATED-ATER [27] Processing Error EquipmentMalfunction Minor (DMA) ID of TRAU-CP is on dedicated PS AterMUX 9130 BSC ID of TRAU-CP is on dedicated PS AterMUX
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no

[47, 27] TRAUCPONDEDICATEDATER
Check Mt120 at TC side
Alarm persists?
no
Alarm solved
yes
210 / 778
13.26 [47,28] TRAU-CP-DOUBLE-DECLARED

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] TRAU-CP-DOUBLE-DECLARED [28] Processing Error equipmentIdentifierDuplication Critical (VPMA) This alarm is sent when the atermux ID of MT120 is the same that of another MT120. 9130 BSC No impact.
Trunk(s) No NO
Cell/BTS(s) No NO
Signaling No NO
Call Handling No NO

[47, 28] TRAUCPDOUBLEDECLARED
Alarm persists?
no
Alarm solved
yes
211 / 778
13.27 [47,30] TRANS-CONFIG-IMPOSSIBLE

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] TRANS-CONFIG-IMPOSSIBLE [30] Equipment EquipmentMalfunction Critical (VPMA) This alarm is sent during BSC startup and neither of the 2 TPGSMs has the required capabilities. BSC does not configure TP. The boards are still running but no RSL comes up as TP is not configured 9130 BSC FIT when alarm begins , IT when alarm ends
Trunk(s) YES NO
Cell/BTS(s) YES NO
Signaling YES NO

[47,30] TRANSCONFIGIMPOSSIBLE
Onsite
Replace TP board with correct version
Alarm persists?
no
Alarm solved
212 / 778
13.28 [47,40] CS-TEL-TEST-NOK

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] CS-TEL-TEST-NOK [40] Communication communicationSubsystemFailure Minor(DMA) Upon the CS telecome outage suspecting for the whole BSC, the telecom test for Abis interface is triggered and the test result is NOK. 9130 BSC The SBL BSC will change to FIT.
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no

[47, 40] CSTELTESTNOK
Check the DLS and replace it if not OK.
Alarm persists?
no
Alarm solved
213 / 778
13.29 [47,41] PS-TEL-TEST-NOK

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] PS-TEL-TEST-NOK [41] Communication communicationSubsystemFailure Minor(DMA) Upon the PS telecome outage suspecting for the whole BSC, the telecom test for BSCGP interface is triggered and the test result is NOK. 9130 BSC The SBL BSC will change to FIT.
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
214 / 778

[47, 41] PSTELTESTNOK
Perform an OMCP takeover.
Alarm persists?
no
yes
Reinitialize GPRS.
Alarm solved
Alarm persists?
no
yes
215 / 778
13.30 [47,103] BTS-TC-RESHUFFLING-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System GLOBAL-BSC [47] BTS-TC-RESHUFFLING-FAIL [103] Processing Error SoftwareProgramError Indetermidate Indicate BTS_TC_RESHUFFLING is fail. 9130 BSC IP bts is not successfully mapped on TC
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no

[47, 103] BTSTCRESHUFFLINGFAIL
Trigger the reshuffling operation again
Alarm persists?
no
Alarm solved
yes
216 / 778
13.31 [47,200] N7-CONF-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description GLOBAL-BSC [47] N7-CONF-FAILURE [200] Equipment EquipmentMalfunction Major(PMA) wrong N7 over IP related configuration in DLS, for example invalid IP@, port number and so on. 9130 BSC No call can be allowed
Trunk(s) No No
Cell/BTS(s) No No
Signaling Yes(Ater) No

[47, 200] N7CONFFAILURE
Correct the wrong configuration in DLS
Alarm persists?
no
Alarm solved
yes
217 / 778
218 / 778
14 Class 48: TR-OM Alarms

This section defines the BSC alarms for the Class 48: TR-OM alarm class.
219 / 778
14.1 [48,0] AUDIT-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description TR-OM [48] AUDIT-FAIL [0] Communication CommunicationSubsystemFailure Indeterminate Due to a failure in the BSC-TSC audit, TR-OM changed from FLT/IT to FLT. 9120 BSC 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.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[48,0] AUDITFAIL
Reset TSC
Alarm persists?
no
Alarm solved
220 / 778
14.2 [48,1] PROTOCOL-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description TR-OM [48] PROTOCOL-FAIL [1] Communication CommunicationProtocolError 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 three[hairsp]required 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. Applicability Impact on System 9120 BSC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

TSL is down only:
[48,1] PROTOCOLFAIL
Reset TSC
Alarm solved
no
Alarm persists?
221 / 778
222 / 778
15 Class 49: ALERTER Alarms

This section defines the BSC alarms for the Class 49: ALERTER alarm class.
223 / 778
15.1 [49,0] LOW-TRAF-SDCCH

specificProblems eventType probableCause perceivedSeverity Alarm Description ALERTER [49] LOW-TRAF-SDCCH [0] Quality of Service PerformanceDegraded Major (PMA) There is abnormally low traffic on SDCCHs in a cell compared with other BSS cells. 9120 BSC 9130 BSC Impact on System 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.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
224 / 778

[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
225 / 778
15.2 [49,1] CH-INCONSIST-SUSP

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability ALERTER [49] CH-INCONSIST-SUSP [1] Quality of Service PerformanceDegraded Major (PMA) There is an inconsistency in the terrestrial channel states. 9120 BSC 9130 BSC Impact on System 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) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
226 / 778

[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
227 / 778
15.3 [49,2] TCH-BLOCK-SUSPECT

specificProblems eventType probableCause perceivedSeverity Alarm Description ALERTER [49] TCH-BLOCK-SUSPECT [2] Quality of Service PerformanceDegraded 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. 9120 BSC 9130 BSC Impact on System 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.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[49,2] TCHBLOCK SUSPECT
TCH related hardware problems?
yes
Solve TCH related hardware problems
no Contact System Support yes Alarm persists? no Alarm solved
228 / 778
15.4 [49,3] TCH-OCCUP-SHORT

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability ALERTER [49] TCH-OCCUP-SHORT [3] Quality of Service PerformanceDegraded Major (PMA) The average traffic channel seizure time is considered to be too short. 9120 BSC 9130 BSC Impact on System 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) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[49,3] TCHOCCUP SHORT
TCH related hardware problems?
yes
Solve TCH related hardware problemst
no Contact System Support yes Alarm persists? no Alarm solved
229 / 778
230 / 778
16 Class 50: BSC EXTERNAL Alarms

This section defines the BSC alarms for the Class 50: BSC EXTERNAL alarm class.
231 / 778
16.1 [50,1] EXT-ALARM-1

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC EXTERNAL [50] EXT-ALARM-1 [1] 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. 9120 BSC The SBL state remains unchanged. No system impact.
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
232 / 778

[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
233 / 778
16.2 [50,2] EXT-ALARM-2

Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
234 / 778

[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
235 / 778
16.3 [50,3] EXT-ALARM-3

Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
236 / 778

[50,3] EXTALARM3
Onsite
yes
Onsite
Onsite
External alarm persists? yes
no
Alarm solved
237 / 778
16.4 [50,4] EXT-ALARM-4

Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
238 / 778

[50,4] EXTALARM4
Onsite
yes
Onsite
Onsite
no
Alarm solved
239 / 778
16.5 [50,5] EXT-ALARM-5

Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
240 / 778

[50,5] EXTALARM5
Onsite
Alarm was sent without cause?
yes
no
Onsite
Onsite
no
Alarm solved
241 / 778
16.6 [50,6] EXT-ALARM-6

Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
242 / 778

[50,6] EXTALARM6
Onsite
yes
no
Onsite
Onsite
no
Alarm solved
243 / 778
16.7 [50,7] EXT-ALARM-7

Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
244 / 778

[50,7] EXTALARM7
Onsite
yes
no
Onsite
Onsite
no
Alarm solved
245 / 778
16.8 [50,8] EXT-ALARM-8

Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
246 / 778

[50,8] EXTALARM8
Onsite
yes
Onsite
Onsite
no
Alarm solved
247 / 778
16.9 [50,9] EXT-ALARM-9

Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
248 / 778

[50,9] EXTALARM9
Onsite
yes
Onsite
Onsite
no
Alarm solved
249 / 778
16.10 [50,10] EXT-ALARM-10

Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
250 / 778

[50,10] EXTALARM10
Onsite
yes
Onsite
Onsite
no
Alarm solved
251 / 778
252 / 778
17 Class 51: SWITCH G2 Alarms

This section defines the BSC alarms for the Class 51: SWITCH G2 alarm class.
253 / 778
17.1 [51,0] TRANSIENT-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System SWITCH G2 [51] TRANSIENT-FAIL [0] Equipment EquipmentMalfunction Warning (MI) The switch detected a momentary fault. 9120 BSC 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.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No

[51,0] TRANSIENTFAIL
SWITCH FAIL alarm events? no
yes
Solve SWITCHFAIL alarm(s)
Alarm persists?
no
Alarm solved
yes
254 / 778
17.2 [51,1] SWITCH-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description SWITCH G2 [51] SWITCH-FAIL [1] Equipment EquipmentMalfunction Major (PMA) The switch element is isolated from the operational software due to a persistent fault. 9120 BSC 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.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
255 / 778
17.2.1 Corrective Actions

17.2.1.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 2: SWITCH-FAIL: Corrective Actions for Write Violation Overflow, Loss of Sync Overflow and Init Fail Alarms
256 / 778
17.2.1.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 3: SWITCH-FAIL: Corrective Actions for Loss of Sync Alarm
257 / 778
17.2.1.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 4: SWITCH-FAIL: Corrective Actions for HW Fault Alarm
258 / 778
17.3 [51,2] ROUTINE-TEST-REP

specificProblems eventType probableCause perceivedSeverity Alarm Description SWITCH G2 [51] ROUTINE-TEST-REP [2] 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. 9120 BSC 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.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
259 / 778

[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
260 / 778
17.4 [51,3] GLOBAL-ROUTINE-TEST-REP

specificProblems eventType probableCause perceivedSeverity Alarm Description SWITCH G2 [51] GLOBAL-ROUTINE-TEST-REP [3] Equipment EquipmentMalfunction Indeterminate (MI) This alarm is sent to indicate both successful and unsuccessful test results. A global network routine test can fail because: * One cycle of the routine test failed, or * One cycle of the routine test failed indicating a link where the error occurred. Note: this alarm can only be sent by a B8 (or previous release) BSS. Applicability Impact on System 9120 BSC 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 global routine test of a link and a switch and the test executed, all Test-raw-data is filled in. For the consequences of an SBL state change, see Chapter Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
261 / 778

[51,3] GLOBAL ROUTINETESTREP
ROUTINE TESTREP alarm events?
yes
Solve ROUTINE TESTREP alarm
no
Wait for next routine test report
Alarm persists?
no
Alarm solved
262 / 778
18 Class 52: BSC CLOCK Alarms

This section defines the BSC alarms for the Class 52: BSC CLOCK alarm class.
263 / 778
18.1 [52,0] LOSS-OF-SEL-CLK-INP

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC CLOCK [52] LOSS-OF-SEL-CLK-INP [0] Equipment TimingProblem Major (PMA) The CLK-GEN detects that all external references have failed. In addition, the local clock has also failed. 9120 BSC See consequences of an SBL state change.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling
264 / 778

[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?
265 / 778
18.2 [52,1] LOSS-OF-CLK-GEN-FN

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC CLOCK [52] LOSS-OF-CLK-GEN-FN [1] Equipment TimingProblem Major (PMA) 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. 9120 BSC See consequences of an SBL state change.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling

[52,1] LOSSOF CLKGENFN
Identify AterMux reference clock and unplug it
Alarm persists?
no
yes Alarm solved
Replace suspected Clock RIT
Alarm persists?
no
yes
266 / 778
18.3 [52,2] SWITCH-TO-LOCAL-CLK

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC CLOCK [52] SWITCH-TO-LOCAL-CLK [2] Equipment TimingProblem Minor (DMA) Due to loss of all external clocks, the CLK-GEN has selected a local clock. 9120 BSC 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 sends the alarm [52,6], which corresponds to the usage in BSC of a local clock. See consequences of an SBL state change.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling
267 / 778

[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
268 / 778
18.4 [52,3] LOSS-OF-SYSTEM-CLOCK-A

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC CLOCK [52] LOSS-OF-SYSTEM-CLOCK-A [3] Equipment TimingProblem Minor (DMA) The System Clock A failure is detected by CLK-REP. 9120 BSC See consequences of an SBL state change
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling

[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
269 / 778
18.5 [52,4] LOSS-OF-SYSTEM-CLOCK-B

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC CLOCK [52] LOSS-OF-SYSTEM-CLOCK-B [4] Equipment TimingProblem Minor (DMA) A System Clock B failure is detected by CLK-REP. 9120 BSC See consequences of an SBL state change
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling

[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
270 / 778
18.6 [52,5] LOSS-OF-CLK-DISTR-FN

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC CLOCK [52] LOSS-OF-CLK-DISTR-FN [5] Equipment TimingProblem Major (PMA) 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. 9120 BSC See consequences of an SBL state change.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling

[52,5] LOSSOF CLKDISTRFN
Onsite
Replace suspected Clock repeater
The rack number is indicated by CLKREP SBL number.
Alarm solved
no
Alarm persists?
yes
271 / 778
18.7 [52,6] BSC-RUN-ON-LOCAL-CLK

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC CLOCK [52] BSC-RUN-ON-LOCAL-CLK [6] Equipment TimingProblem Major (PMA) This alarm is generated when the BSC is running on the local clock. 9120 BSC 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 effect 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.
Impact Loss
Trunk(s)
Cell/BTS(s) Yes (depending on clock gap) Yes (depending on clock gap)
Signaling Yes (depending on clock gap)
Call Handling Yes (depending on clock gap)
O&M; Capabilities
Degradation
Yes (depending on clock gap)
Yes (depending on clock gap)
272 / 778

[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
273 / 778
18.8 [52,7] LOC-CLK-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC CLOCK [52] LOC-CLK-FAILURE [7] Equipment TimingProblem Major (PMA) Due to detection of the Local Clock Failure the CLK-GEN is degraded. 9120 BSC See consequences of an SBL state change.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling

[52,7] LOC CLKFAILURE
Onsite
Replace suspected Clock RIT
Alarm solved
no
Alarm persists?
274 / 778
19 Class 53: BROADCAST BUS Alarms

This section defines the BSC alarms for the Class 53: BROADCAST BUS alarm class.
275 / 778
19.1 [53,0] LOSS-OF-ONE-BROAD-BUS-BSC

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BROADCAST BUS [53] LOSS-OF-ONE-BROAD-BUS-BSC [0] Equipment EquipmentMalfunction Major (PMA) The BSC has detected loss of one BC bus in the BSC. 9120 BSC See consequences of an SBL state change.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling

[53,0] LOSSOFONE BROADBUSBSC
Onsite
Replace suspected RIT
The Broadcast Bus is indicated by the BCSYSBUS SBL number.
Alarm solved
no
Alarm persists?
276 / 778
19.2 [53,1] LOSS-OF-BOTH-BROAD-BUS-BSC

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BROADCAST BUS [53] LOSS-OF-BOTH-BROAD-BUS-BSC [1] Equipment TimingProblem Critical (VPMA) The BSC has detected loss of both broadcast buses in the BSC. 9120 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.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling Yes

[53,1] LOSSOFBOTH BROADBUSBSC
Onsite
G2: Replace both BCLASYS boards
Alarm solved
no
Alarm persists?
277 / 778
19.3 [53,2] DMA-PROBLEM

specificProblems eventType probableCause perceivedSeverity Alarm Description BROADCAST BUS [53] DMA-PROBLEM [2] Communication CommunicationSubsystemFailure Major (PMA) For BSC: The BSC has detected DMA problems in a high percentage of Ces in the BSC. For CPR/DTC/TCU: The BSC has detected a high number of DMA problems in the CE. 9120 BSC See Consequences of an SBL State Change.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling

[53,2] DMAPROBLEM (CPR/DTC/TCU)
DMAPROBLEM (BSC) alarm events?
yes
no
Onsite
Replace suspected CPR/DTC/TCU
Alarm solved
no
Alarm persists?
yes
278 / 778
19.4 [53,3] LOSS-OF-ONE-BROAD-BUS-RACK

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BROADCAST BUS [53] LOSS-OF-ONE-BROAD-BUS-RACK [3] Equipment LanError Major (PMA) The BSC has detected a loss of one broadcast bus on a RACK. 9120 BSC See Consequences of an SBL State Change.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling

[53,3] LOSSOFONE BROADBUSRACK
Onsite
The Broadcast Bus is indicated by the BC_RACK_BUS SBL number.
Alarm solved
no
Alarm persists?
yes
279 / 778
19.5 [53,4] LOSS-OF-BOTH-BROAD-BUS-RACK

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BROADCAST BUS [53] LOSS-OF-BOTH-BROAD-BUS-RACK [4] Equipment TimingProblem Critical (VPMA) The BSC has detected loss of both broadcast buses on a RACK. 9120 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.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling Yes

[53,4] LOSSOFBOTH BROADBUSRACK
Onsite
G2: Replace both BCLA boards
Alarm solved
no
Alarm persists?
yes
280 / 778
19.6 [53,5] DEGRAD-BROAD-BUS-RACK

specificProblems eventType probableCause perceivedSeverity Alarm Description BROADCAST BUS [53] DEGRAD-BROAD-BUS-RACK [5] Equipment LanError Minor (DMA) The BSC has detected a degradation in the quality of one of the broadcast buses on a RACK. 9120 BSC See Consequences of an SBL State Change.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling

[53,5] DEGRAD BROADBUSRACK
Onsite
Alarm solved
no
Alarm persists?
yes
281 / 778
19.7 [53,6] LOSS-OF-ONE-BROAD-BUS-CE

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BROADCAST BUS [53] LOSS-OF-ONE-BROAD-BUS-CE [6] Equipment LanError Minor (DMA) The BSC has detected loss of one broadcast bus to a CE. 9120 BSC No redundancy on broadcast bus. For the consequences of an SBL state change, see Consequences of an SBL State Change.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling

[53,6] LOSSOFONE BROADBUSCE
Onsite
Replace cabling to suspected RIT
Alarm solved
no
Alarm persists?
282 / 778
19.8 [53,7] LOSS-OF-BOTH-BROAD-BUS-CE

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BROADCAST BUS [53] LOSS-OF-BOTH-BROAD-BUS-CE [7] Equipment TimingProblem Critical (VPMA) The BSC has detected loss of both broadcast buses to a CE. 9120 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.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling Yes

[53,7] LOSSOFBOTH BROADBUSCE
Onsite
Alarm solved
no
Alarm persists?
283 / 778
19.9 [53,8] DEGRAD-BROAD-BUS-CE

specificProblems eventType probableCause perceivedSeverity Alarm Description BROADCAST BUS [53] DEGRAD-BROAD-BUS-CE [8] Equipment LanError Minor (DMA) The BSC has detected a degradation in the quality of one of the broadcast buses to a CE. 9120 BSC 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.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling Yes

[53,8] DEGRAD BROADBUSCE
DEGRAD BROADBUS RACK alarm events?
yes
no
Onsite
G2: Replace suspected broadcast bus RIT
Alarm solved
no
Alarm persists?
yes
284 / 778
20 Class 54: BTS-POOL Alarms

This section defines the BSC alarms for the Class 54: BTS-POOL alarm class.
285 / 778
20.1 [54,1] EXTRA TS NOT FULLY USABLE

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-POOL [54] EXTRA TS NOT FULLY USABLE [1] Quality of Service PerformanceDegraded Minor (DMA), , Warning if out of commercial use For 9120 BSC: In case of TCU failure/end failure, 2nd Abis failure/end failure or BTS config-complete, the alarm is evaluated. For 9130 BSC Evolution: In case of 2nd Abis failure/end failure 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. 9120 BSC 9130 BSC Impact on System The new added SBL does not impact MAINT/ALARM modules. In OMC side, after HW audit, if the BTS is type of 9100 , OMC creates BTS-POOL for that BTS. And OMC will clear the alarm in case of alarm audit or receiving END alarm.
Applicability
Trunk(s) No No
Cell/BTS(s) No Yes
Signaling No No
Call Handling No No
286 / 778
287 / 778
288 / 778
21 Class 66: TSC-TRUNK Alarms

This section defines the BSC alarms for the Class 66: TSC-TRUNK alarm class.
289 / 778
21.1 [66,21] LOOP-TO-ITF

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-TRUNK [66] LOOP-TO-ITF [21] Equipment EquipmentUnderTest Major (PMA) An external loop is activated. A loop cannot be activated/deactivated using the OMC-R. 9120 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Impact Loss
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling Yes
Yes (if Yes (if Yes A-PCM-TP ABIS-HWAY-TP) or SBL ATER-HWAY-TP) No No No
Degradation
No
No

[66,21] LOOPTOITF
Remove the loopback settings, though normal conditions return after a preset control timeout.
Alarm solved
no
Alarm persists?
290 / 778
21.2 [66,22] LOOP-TO-EQUIP

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-TRUNK [66] LOOP-TO-EQUIP [22] Equipment EquipmentUnderTest Major (PMA) An external loop is activated. A loop cannot be activated/deactivated using the OMC-R. 9120 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Impact Loss
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling Yes
O&M; Capabilities Yes (if ABIS-HWAY-TP)
Degradation
No
No

[66,22] LOOPTOEQUIP
Remove the loopback settings, though normal conditions return after a preset control timeout.
Alarm solved
no
Alarm persists?
291 / 778
21.3 [66,50] TWO-MB-MISSING

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-TRUNK [66] TWO-MB-MISSING [50] 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. 9120 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Impact Loss
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling Yes
Degradation
No
No
292 / 778

[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
293 / 778
21.4 [66,66] AIS-2-MB

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability TSC-TRUNK [66] AIS-2-MB [66] Communication LocalNodeTransmissionError Minor (DMA) The 2 Mbit/s interface is receiving an AIS signal all ones indication. 9120 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Impact Loss
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling Yes
Degradation
No
No
294 / 778

[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
295 / 778
21.5 [66,81] FRAME-ALIGNMENT

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-TRUNK [66] FRAME-ALIGNMENT [81] 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. 9120 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Impact Loss
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling Yes
Degradation
No
No
296 / 778

[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?
297 / 778
21.6 [66,86] CRC-MFRAME-ALGN

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-TRUNK [66] CRC-MFRAME-ALGN [86] 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. 9120 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Impact Loss
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling Yes
Degradation
No
No
298 / 778

[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
299 / 778
21.7 [66,99] BER-10E-3

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-TRUNK [66] BER-10E-3 [99] 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. 9120 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Impact Loss
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling Yes
Degradation
No
No
300 / 778

[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
301 / 778
21.8 [66,100] BER-10E-4

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-TRUNK [66] BER-10E-4 [100] 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. 9120 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
302 / 778

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

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-TRUNK [66] BER-10E-6 [102] 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. 9120 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
304 / 778

[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
305 / 778
21.10 [66,176] FAR-END-ALARM

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-TRUNK [66] FAR-END-ALARM [176] 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. 9120 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Impact Loss
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling Yes
Degradation
No
No
306 / 778

[66,176] FAREND ALARM
no
yes
Related Solve that alarm(s) receiver alarm events?
no
Alarm persists?
no
Alarm solved
307 / 778
21.11 [66,208] I1I2-AIS

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-TRUNK [66] I1I2-AIS [208] 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. 9120 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling Yes No
308 / 778

[66,208] I1L2AIS
Loop is activated?
no
yes
Ater alarm events?
Remove loop no
Alarm persists?
no
Alarm solved
309 / 778
21.12 [66,210] TRANS-FLT

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-TRUNK [66] TRANS-FLT [210] Equipment EquipmentMalfunction Indeterminate 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. 9120 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
310 / 778

[66,210] TRANSFLT
no
yes
no
yes
Solve that alarm(s)
yes
Alarm persists?
no
no
yes
Alarm persists?
no
Alarm solved
311 / 778
21.13 [66,211] LOSS-OF-CLK-2M

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-TRUNK [66] LOSS-OF-CLK-2M [211] Equipment TimingProblem Minor (DMA) 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. 9120 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling Yes No
312 / 778

[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
313 / 778
21.14 [66,225] TU-LOP

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-TRUNK [66] TU-LOP [225] Communication LocalNodeTransmissionError Minor (DMA) tributary unit 12 loss of pointer, E1 evel alarm in case of STM1 in TC, Only reported over TCSL G2 TC and 9125 TC Ater-HW-TP(TC) or A-PCM-TP is updated to FLT
Impact Loss
Trunk(s) Yes (if A-PCM-TP) No
Cell/BTS(s) No
Signaling Yes if it carries N7 No
Call Handling Yes
Degradation
No
No
No
314 / 778
21.15 [66,226] TU-AIS

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TSC-TRUNK [66] TU-AIS [226] Communication LocalNodeTransmissionError Minor (DMA) Tributary Unit 12 Alarm Indication Signal G2 TC and 9125 TC Ater-HW-TP(TC) or A-PCM-TP is updated to FLT
Impact Loss
Trunk(s) Yes (if A-PCM-TP ) No
Cell/BTS(s) No
Signaling Yes if it carries N7
Call Handling Yes
Degradation
No
No
No
No
315 / 778
21.16 [66,227] LP-UNEQ

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TSC-TRUNK [66] LP-UNEQ [227] Communication LocalNodeTransmissionError Minor (DMA) Low Path Unequipped G2 TC and 9125 TC Ater-HW-TP(TC) or A-PCM-TP is updated to FLT
Impact Loss
Cell/BTS(s) No
Call Handling Yes
Degradation
No
No
No
No
316 / 778
21.17 [66,228] LP-RDI

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TSC-TRUNK [66] LP-RDI [228] Communication LocalNodeTransmissionError Minor (DMA) Low Path Remote Defect indication G2 TC and 9125 TC Ater-HW-TP(TC) or A-PCM-TP is updated to FLT
Impact Loss
Cell/BTS(s) No
Call Handling Yes
Degradation
No
No
No
No
317 / 778
21.18 [66,229] LP-PLM

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TSC-TRUNK [66] LP-PLM [229] Communication LocalNodeTransmissionError Minor (DMA) Low Path Payload Label Mismatch G2 TC and 9125 TC Ater-HW-TP(TC) or A-PCM-TP is updated to FLT
Impact Loss
Cell/BTS(s) No
Call Handling Yes
Degradation
No
No
No
No
318 / 778
21.19 [66,230] LP-J2

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TSC-TRUNK [66] LP-J2 [230] Communication LocalNodeTransmissionError Minor (DMA) J2 path trace mismatch G2 TC and 9125 TC Ater-HW-TP(TC) or A-PCM-TP is updated to FLT
Impact Loss
Cell/BTS(s) No
Call Handling Yes
Degradation
No
No
No
No
319 / 778
21.20 [66,231] E1-AIS-2MB

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TSC-TRUNK [66] E1-AIS-2MB [231] Communication LocalNodeTransmissionError Minor (DMA) Alarm Indication Signal G2 TC and 9125 TC Ater-HW-TP(TC) or A-PCM-TP is updated to FLT
Impact Loss
Cell/BTS(s) No
Call Handling Yes
Degradation
No
No
No
No
320 / 778
21.21 [66,232] E1-FRAME-ALIGNMENT

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TSC-TRUNK [66] E1-FRAME-ALIGNMENT [232] Communication LocalNodeTransmissionError Minor (DMA) Loss of Frame alignment G2 TC and 9125 TC Ater-HW-TP(TC) or A-PCM-TP is updated to FLT
Impact Loss
Cell/BTS(s) No
Call Handling Yes
Degradation
No
No
No
No
321 / 778
21.22 [66,233] E1-CRC-MFRAME-ALGN

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TSC-TRUNK [66] E1-CRC-MFRAME-ALGN [233] Communication LocalNodeTransmissionError Minor (DMA) Loss of CRC4 multiframe alignment G2 TC and 9125 TC Ater-HW-TP(TC) or A-PCM-TP is updated to FLT
Impact Loss
Cell/BTS(s) No
Call Handling Yes
Degradation
No
No
No
No
322 / 778
21.23 [66,234] E1-BER-10E-3

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TSC-TRUNK [66] E1-BER-10E-3 [234] Communication LocalNodeTransmissionError Minor (DMA) Bit error rate >10E-3 G2 TC and 9125 TC Ater-HW-TP(TC) or A-PCM-TP is updated to FLT
Impact Loss
Cell/BTS(s) No
Call Handling Yes
Degradation
No
No
No
No
323 / 778
21.24 [66,235] E1-BER-10E-4

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TSC-TRUNK [66] E1-BER-10E-4 [235] Communication LocalNodeTransmissionError Minor (DMA) Bit error rate >10E-4 G2 TC and 9125 TC Ater-HW-TP(TC) or A-PCM-TP is updated to FIT
Impact Loss
Cell/BTS(s) No
Call Handling Yes
Degradation
No
No
No
No
324 / 778
21.25 [66,236] E1-RAI

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TSC-TRUNK [66] E1-RAI [236] Communication LocalNodeTransmissionError Minor (DMA) Remote Alarm Indication G2 TC and 9125 TC Ater-HW-TP(TC) or A-PCM-TP is updated to FLT
Impact Loss
Cell/BTS(s) No
Call Handling Yes
Degradation
No
No
No
No
325 / 778
326 / 778
22 Class 67: TSC-CHANNEL Alarms

This section defines the BSC alarms for the Class 67: TSC-CHANNEL alarm class.
327 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-CHANNEL [67] LOOP-TO-EQUIP [22] Equipment EquipmentUnderTest Major (PMA) A loop has been activated. A loop cannot be activated/deactivated using the OMC-R. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No

[67,22] LOOP TOEQUIP
Remove loop
Alarm persists?
no
Alarm solved
328 / 778
22.2 [67,72] AIS-16-KB

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-CHANNEL [67] AIS-16-KB [72] Communication LocalNodeTransmissionError Minor (DMA) The Ater-Interface TCHs are receiving an AIS signal (all ones). Note: This alarm is not sent to the OMC, only to the BSC Terminal. Applicability Impact on System G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
329 / 778

[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
330 / 778
22.3 [67,122] TRAU-SYNCHRO

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-CHANNEL [67] TRAU-SYNCHRO [122] Equipment TimingProblem Minor (DMA) The TRAU cannot synchronize to the BTS. The speech path is broken between the TRE and the Transcoder. This only occurs during call handling. Note: This alarm is not sent to the OMC, only to the BSC Terminal. Applicability Impact on System G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
331 / 778

[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
332 / 778
22.4 [67,128] EQUIPMENT-FAULT

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TSC-CHANNEL [67] EQUIPMENT-FAULT [128] Equipment EquipmentMalfunction Major (PMA) An internal fault has been detected on a board. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
333 / 778

[67,128] EQUIPMENTFAULT
G2 TC
A925 TC
Lock TC16
Lock MT120
Unlock TC16
Unlock MT120
Alarm persists?
no
Alarm solved
no
Alarm persists?
Onsite
yes
Onsite
yes
Replace DT16/TC16
or
Replace MT120
Replace MT120
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes
334 / 778
22.5 [67,130] MEMORY-FAULT

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TSC-CHANNEL [67] MEMORY-FAULT [130] Processing Error CorruptData Major (PMA) An EEPROM memory write access has been unsuccessful. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
335 / 778

[67,130] MEMORY FAULT
G2 TC G2 TC or 9125 TC?
9125 TC
Analyze alarm number
DT16/TC16 alarm events? no
yes
MT120 alarm events?
no
yes
Alarm persists?
yes
Lock TC16
no
Lock MT 120
Unlock TC16
Unlock MT120
Alarm persists?
no
Alarm solved
no
Alarm persists?
Onsite
yes
yes
Replace DT16/TC16
or
Replace MT120
Replace MT120
Alarm persists?
no
Alarm solved
no
Alarm persists?
336 / 778
22.6 [67,131] INT-BUS-FAULT

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TSC-CHANNEL [67] INT-BUS-FAULT [131] Equipment EquipmentMalfunction Major (PMA) An internal fault has been detected on board. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
337 / 778

[67,131] INTBUSFAULT
G2 TC
A925 TC
Lock TC16
Lock MT120
Unlock TC16
Unlock MT120
Alarm persists?
no
Alarm solved
no
Alarm persists?
Onsite
yes
Onsite
yes
Replace DT16/TC16
or
Replace MT120
Replace MT120
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes
338 / 778
23 Class 70: TSC-SW-ANOMALY Alarms

This section defines the BSC alarms for the Class 70: TSC-SW-ANOMALY alarm class.
339 / 778
23.1 [70,219] SW-FAULT

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-SW-ANOMALY [70] SW-FAULT [219] Processing Error ApplicationSubsystemFailure Critical (VPMA) The software which runs on the TSCA board (9120 BSC) or the TSC process (A(130 BSC) has detected an error. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
340 / 778

[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
341 / 778
342 / 778
24 Class 71: TSC-ENVIRON Alarms

This section defines the BSC alarms for the Class 71: TSC-ENVIRON alarm class.
343 / 778
24.1 [71,0] POWER-SUPPLY

specificProblems eventType probableCause perceivedSeverity Alarm Description TSC-ENVIRON [71] POWER-SUPPLY [0] 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. 9120 BSC 9130 BSC G2 TC and 9125 TC Impact on System 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.
Applicability
Impact Loss
Trunk(s) Yes (if SM-ADAPT = FLT or TC-ADAPT = FLT)
Cell/BTS(s) Yes (if BTS-ADAPT = FLT)
Signaling Yes (if BTS-ADAPT = FLT, SM-ADAPT = FLT or TC-ADAPT = FLT) Yes (if BTS-ADAPT = FIT or SM-ADAPT = FIT)
Call Handling Yes (if BTS-ADAPT = FLT, SM-ADAPT = FLT or TC-ADAPT = FLT) Yes (if BTS-ADAPT = FIT or SM-ADAPT = FIT)
O&M; Capabilities Yes (if BTS-ADAPT = FLT)
Degradation
Yes (if SM-ADAPT = FIT)
Yes (if BTS-ADAPT = FIT)
344 / 778

[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
345 / 778
346 / 778
25 Class 73: BSC-ADAPT Alarms

This section defines the BSC alarms for the Class 73: BSC-ADAPT alarm class.
347 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-ADAPT [73] LOOP-TO-EQUIP [22] Equipment EquipmentUnderTest Major (PMA) A loop is activated on one of the eight BSC interfaces. A loop cannot be activated/deactivated using the OMC-R. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No

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

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-ADAPT [73] EQUIPMENT-FAULT [128] Equipment EquipmentMalfunction Major (PMA) There is a basic operational malfunction. An internal fault has been detected on board. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No
349 / 778

[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
350 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-ADAPT [73] MEMORY-FAULT [130] Equipment EquipmentMalfunction Major (PMA) An EEPROM memory write access has been unsuccessful. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No
351 / 778

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
352 / 778
25.4 [73,148] RESET

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-ADAPT [73] RESET [148] Processing Error SoftwareError Indeterminate An autonomous load 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No

None - this alarm reports the autonomous load. See TC Alarms (Section 36.5) for the Alarm number description.
353 / 778
25.5 [73,202] NO-Q1-CONN

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-ADAPT [73] NO-Q1-CONN [202] Processing Error UnderlyingResourceUnavailable 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
354 / 778

[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?
355 / 778
25.6 [73,203] LOSS-OF-ACT

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-ADAPT [73] LOSS-OF-ACT [203] Equipment EquipmentMalfunction Minor (DMA) 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
356 / 778

[73,203] LOSS OFACT
Lock BIUA
Unlock BIUA
no
BIUA alarm events?
no
Alarm persists?
no
Alarm solved
357 / 778
25.7 [73,212] LOSS-OF-CLK-8M

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-ADAPT [73] LOSS-OF-CLK-8M [212] Equipment EquipmentMalfunction Minor (DMA) 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
358 / 778

[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
359 / 778
25.8 [73,213] LOSS-OF-CLK-BOTH-8M

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-ADAPT [73] LOSS-OF-CLK-BOTH-8M [213] Equipment EquipmentMalfunction Major (PMA) Both 8 MHz clock sources are lost. The internal clock is selected. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No
360 / 778

[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
361 / 778
25.9 [73,216] RESTART

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-ADAPT [73] RESTART [216] Processing Error ApplicationSubsystemFailure Indeterminate An autonomous restart 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - this alarm reports an autonomous restart.
362 / 778
25.10 [73,241] SET-PROD-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-ADAPT [73] SET-PROD-FAIL [241] Processing Error ConfigurationOrCustomizationError Minor (DMA) This alarm indicates the NE settings production has failed. The equipment settings are not in line with the DLS. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No

[73,241] SETPRODFAIL
no Correct DSL settings
DSL settings OK?
yes
Lock BSCADAPT
Unlock BSCADAPT
Alarm solved
no
Alarm persists?
363 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-ADAPT [73] DOWNLOAD-FAIL [246] Processing Error ConfigurationOrCustomizationError Minor (DMA), Warning if out of commercial use 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. G2 TC and 9125 TC The equipment settings are not in line with the DLS. See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No
364 / 778

[73,246] DOWNLOAD FAIL
DSL settings OK?
yes
Lock BSCADAPT
Unlock BSCADAPT
Alarm persists?
no
Alarm solved
365 / 778
25.12 [73,247] ACCESS-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-ADAPT [73] ACCESS-FAIL [247] Equipment EquipmentMalfunction 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No

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

This section defines the BSC alarms for the Class 74: BTS-ADAPT alarm class.
367 / 778
26.1 [74,20] BLOCKED-FROM-USE

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-ADAPT [74] BLOCKED-FROM-USE [20] Processing Error ConfigurationOrCustomizationError Minor (DMA), Warning if out of commercial use 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. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No
368 / 778

[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?
369 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-ADAPT [74] LOOP-TO-EQUIP [22] Equipment EquipmentUnderTest Major (PMA), Warning if out of commercial use A loop is activated on the BSC interface link. A loop cannot be activated/deactivated using the OMC-R. Applicability 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No Yes
Signaling No Yes

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

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-ADAPT [74] TESTMODE [23] Equipment EquipmentUnderTest Major (PMA), Warning if out of commercial use The equipment, or part of it, is under test. Normal operation is suspended. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No

None - equipment is under test. See TC Alarms (Section 36.5) for the Alarm number description.
371 / 778
26.4 [74,122] SYNCHRO-AL

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-ADAPT [74] SYNCHRO-AL [122] Equipment TimingProblem Minor (DMA), Warning if out of commercial use The primary synchronization source is missing or not selected. The module switches to the secondary source. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
372 / 778

[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
373 / 778
26.5 [74,124] SYNC-AL-CLOCKR

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-ADAPT [74] SYNC-AL-CLOCKR [124] Equipment TimingProblem Major (PMA), Warning if out of commercial use Synchronizing fault in clock recovery has occurred. The synchronizing signal is missing. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No
374 / 778

[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
375 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-ADAPT [74] EQUIPMENT-FAULT [128] Equipment EquipmentMalfunction Major (PMA), Warning if out of commercial use There is a basic operational malfunction. An internal fault has been detected on a board. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Impact Loss
Trunk(s) No
Cell/BTS(s) Yes (if BTS-ADAPT = FLT) Yes (if BTS-ADAPT = FIT)
Signaling Yes (if BTS-ADAPT = FLT) Yes (if BTS-ADAPT = FIT)
Call Handling Yes (if BTS-ADAPT = FLT) Yes (if BTS-ADAPT = FIT)
Degradation
No
376 / 778

Lock BTSADAPT
Unlock BTSADAPT
Alarm persists?
no
Alarm solved
yes
Onsite
Alarm persists?
no
Alarm solved
377 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability BTS-ADAPT [74] MEMORY-FAULT [130] Processing Error CorruptData Major (PMA), Warning if out of commercial use An EEPROM memory write access has been unsuccessful. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Impact Loss
Trunk(s) No
Degradation
No
378 / 778

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
379 / 778
26.8 [74,139] MISSING-UNIT

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-ADAPT [74] MISSING-UNIT [139] Processing Error ConfigurationOrCustomizationError Major (PMA), Warning if out of commercial use 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). 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Impact Loss
Trunk(s) No
Degradation
No
380 / 778

[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?
381 / 778
26.9 [74,141] FORCED-CNTRL-ON

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability BTS-ADAPT [74] FORCED-CNTRL-ON [141] Equipment EquipmentUnderTest Major (PMA), Warning if out of commercial use A forced control (loop, changeover, etc.) is activated. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No

[74,141] FORCED CONTROLON
Remove forced control
The normal condition returns after a preset timeout.
Alarm persists?
no
Alarm solved
382 / 778
26.10 [74,142] INSTALLATION

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-ADAPT [74] INSTALLATION [142] Processing Error ConfigurationOrCustomizationError Major (PMA), Warning if out of commercial use Installation incorrectly performed. This alarm can also appears as an event when the board is manipulated. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No
383 / 778

[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?
384 / 778
26.11 [74,148] RESET

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-ADAPT [74] RESET [148] Processing Error SoftwareError Indeterminate 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. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No

None, - this alarm reports the autonomous load of the CE only. See TC Alarms (Section 36.5) for the Alarm number description.
385 / 778
26.12 [74,159] DIAG-TESTS

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability BTS-ADAPT [74] DIAG-TESTS [159] Equipment EquipmentUnderTest Major (PMA), Warning if out of commercial use A diagnostic test is running. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No

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

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-ADAPT [74] NO-Q1-CONN [202] Processing Error UnderlyingResourceUnavailable Minor (DMA), Warning if out of commercial use 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. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No Yes
Signaling No Yes
387 / 778

[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
388 / 778
26.14 [74,241] SET-PROD-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-ADAPT [74] SET-PROD-FAIL [241] Processing Error ConfigurationOrCustomizationError Minor (DMA), Warning if out of commercial use This alarm indicates the NE settings production has failed. The equipment settings are not in line with the DLS. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No
389 / 778

DSL settings OK?
yes
Lock BSCADAPT
Unlock BSCADAPT
Alarm solved
no
Alarm persists?
390 / 778
26.15 [74,245] LOCAL-REINIT-REQ

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-ADAPT [74] LOCAL-REINIT-REQ [245] Equipment EquipmentUnderTest Minor (DMA), Warning if out of commercial use 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. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No
391 / 778

[74,245] LOCAL REINITREQ
BTS parameter settings OK?
no Correct settings
yes
Disable BSCADAPT
Init BSCADAPT
Alarm persists?
no
Alarm solved
392 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-ADAPT [74] DOWNLOAD-FAIL [246] Processing Error ConfigurationOrCustomizationError Minor (DMA), Warning if out of commercial use 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. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No
393 / 778

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

specificProblems eventType probableCause perceivedSeverity Alarm Description BTS-ADAPT [74] ACCESS-FAIL [247] Equipment EquipmentMalfunction Minor (DMA), Warning if out of commercial use 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. 9120 BSC 9130 BSC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) Yes No
Signaling Yes No

[74,247] ACCESSFAIL
TCU/TSL/NE alarm events?
no
Alarm persists?
no
Alarm solved
395 / 778
396 / 778
27 Class 75: TCSM-ADAPT Alarms

This section defines the BSC alarms for the Class 75: TCSM-ADAPT alarm class.
397 / 778
27.1 [75,20] BLOCKED-FROM-USE

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] BLOCKED-FROM-USE [20] Processing Error ConfigurationOrCustomizationError 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling Yes No

[75,20] BLOCKED FROMUSE
Time slot settings OK?
no
Correct time slot settings
yes
Alarm persists?
no
Alarm solved
398 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] LOOP-TO-EQUIP [22] Equipment EquipmentUnderTest Major (PMA) A loop is activated. A loop cannot be activated/deactivated using the OMC-R. G2 TC and 9125 TC See Consequences of an SBL State Change.
Impact Loss
Trunk(s) Yes (if SM-ADAPT = FLT) Yes (if SM-ADAPT = FIT)
Cell/BTS(s) No
Signaling Yes (if SM-ADAPT = FLT) Yes (if SM-ADAPT = FIT)
Call Handling Yes (if SM-ADAPT = FLT) Yes (if SM-ADAPT = FIT)
Degradation
No
No

Remove BSC interface loop
Alarm persists? no yes Contact System Support
Alarm solved
399 / 778
27.3 [75,112] FAN-ALARM

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] FAN-ALARM [112] Environmental HeatingOrVentilationOrCoolingSystemProblem Major (PMA) 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[75,112] FANALARM
Onsite
Replace fan unit
Alarm persists?
no
Alarm solved
400 / 778
27.4 [75,122] SYNCHRO-AL

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] SYNCHRO-AL [122] Equipment TimingProblem Minor (DMA) The primary synchronization source is missing. The module switches to the secondary source. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
401 / 778

[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
402 / 778
27.5 [75,124] SYNCHRO-AL-CLOCKR

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] SYNCHRO-AL-CLOCKR [124] Equipment TimingProblem Major (PMA) Synchronizing fault in clock recovery has occurred. The synchronizing signal is missing. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
403 / 778

[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
404 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] EQUIPMENT-FAULT [128] Equipment EquipmentMalfunction Major (PMA) There is a basic operational malfunction. An internal fault has been detected on a board. G2 TC and 9125 TC See Consequences of an SBL State Change.
Impact Loss
Trunk(s) Yes (if SM-ADAPT = FLT) Yes (if SM-ADAPT = FIT or TC_ADAPT = FLT)
Cell/BTS(s) No
Signaling Yes (if SM-ADAPT = FLT) Yes (if SM-ADAPT = FIT or TC_ADAPT = FLT)
Call Handling Yes (if SM-ADAPT = FLT) Yes (if SM-ADAPT = FIT or TC_ADAPT = FLT)
Degradation
No
No
405 / 778

Lock SMADAPT/TC_ADAP T
Unlock SMADAPT/TC_ADAP T
Alarm persists?
no
Alarm solved
yes
Onsite
Alarm persists?
no
Alarm solved
406 / 778
27.7 [75,130] DSP-LOSS

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] DSP-LOSS [130] Processing Error CorruptData Major (PMA) For G2 TC: an EEPROM memory write access has been unsuccessful. For MT120: more than one DSP has failed and the impact is only the loss of a number of channels, that is only trunk degradation. Signalling is not lost neither. G2 TC and 9125 TC See Consequences of an SBL State Change.
Impact Loss
Trunk(s) Yes(for G2 TC) Yes(for MT120)
Cell/BTS(s) No
Signaling Yes(for G2 TC)
Call Handling Yes(for G2 TC)
Degradation
No
No
No
No
407 / 778

[75,130] DSPLOSS
BIU alarm events?
G2 TC
no
9125 TC
Lock SMADAPT/ TCADAPT Reset MT120 Unlock SMADAPT/ TCADAPT
Alarm persists?
no
Alarm solved
no
Alarm persists?
Onsite
yes
Onsite
yes
Replace BIU
or
Replace MT120
Replace MT120
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes Contact System Support Contact System Support
408 / 778
27.8 [75,136] FIRST-DSP-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] FIRST-DSP-FAIL [136] Equipment EquipmentMalfunction 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
409 / 778

[75,136] FIRST DSPFAIL
Reset MT120
Alarm persists?
no
Alarm solved
Onsite
yes
9125 TC
Replace MT120
Replace MT120
Alarm persists?
no
Alarm solved
410 / 778
27.9 [75,139] MISSING-UNIT

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] MISSING-UNIT [139] Processing Error ConfigurationOrCustomizationError 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). G2 TC and 9125 TC See Consequences of an SBL State Change.
Impact Loss
Trunk(s) Yes (if SM-ADAPT = FIT or TC-ADAPT = FLT) No
Cell/BTS(s) No
Signaling Yes (if SM-ADAPT = FIT or TC-ADAPT = FLT) No
Call Handling Yes (if SM-ADAPT = FIT or TC-ADAPT = FLT) No
Degradation
No
No
411 / 778

[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?
412 / 778
27.10 [75,141] FORCED-CNTRL-ON

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TCSM-ADAPT [75] FORCED-CNTRL-ON [141] Equipment EquipmentUnderTest Major (PMA) Forced control (loop, changeover etc.) is activated. G2 TC and 9125 TC See Consequences of an SBL State Change.
Impact Loss
Trunk(s) Yes (if SM_ADAPT = FLT) Yes (if SM_ADAPT = FIT or TC_ADAPT = FLT)
Cell/BTS(s) No
Signaling No
Call Handling Yes (if SM_ADAPT = FLT) Yes (if SM_ADAPT = FIT or TC_ADAPT = FLT)
Degradation
No
No
No

[75,141] FORCED CONTROLON
Remove forced control
The normal condition returns after a preset timeout.
Alarm solved
no
Alarm persists?
yes
413 / 778
27.11 [75,142] INSTALLATION

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] INSTALLATION [142] Processing Error ConfigurationOrCustomizationError Major (PMA) Installation incorrectly performed, or appears as an event when the board is manipulated. G2 TC and 9125 TC See Consequences of an SBL State Change.
Impact Loss
Trunk(s) Yes (if SBL SM-ADAPT) Yes (if SBL TC-ADAPT)
Cell/BTS(s) No
Signaling Yes (if SBL SM-ADAPT) Yes (if SBL TC-ADAPT)
Call Handling Yes (if SBL SM-ADAPT) Yes (if SBL TC-ADAPT)
Degradation
No
No
414 / 778

[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?
415 / 778
27.12 [75,148] RESET

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] RESET [148] Processing Error SoftwareError Indeterminate An autonomous load of the TC SM-ADAPT 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. This cannot happen as this module has only firmware. G2 TC and 9125 TC Some calls may be lost
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - this alarm reports the autonomous load of the BTS_ADAPT only. See TC Alarms (Section 36.5) for the Alarm number description.
416 / 778
27.13 [75,159] DIAG-TESTS

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TCSM-ADAPT [75] DIAG-TESTS [159] Equipment EquipmentUnderTest Major (PMA) A diagnostic test is running. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling Yes No

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

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] NO-Q1-CONN [202] Processing Error UnderlyingResourceUnavailable 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
418 / 778

[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
419 / 778
27.15 [75,208] TRIB-TRANS-FLT

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] TRIB-TRANS-FLT [208] Communication DegradedSignal Indeterminate 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
420 / 778

[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
421 / 778
27.16 [75,209] INT-BUS-FLT-G25

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] INT-BUS-FLT-G25 [209] Equipment EquipmentMalfunction 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
422 / 778

[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
no Board at address16? Put a spare at address 16
9125 TC
Replace MT120
Replace MT120
yes
Last board with alarm?
no
Alarm solved
no
Alarm persists?
yes
Replace MT120
Replace MT120
G2 TC
9125 TC
G2 TC or 9125 TC?
yes
Alarm persists?
no Alarm solved
423 / 778
27.17 [75,210] ATER-TRANS-FLT

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] ATER-TRANS-FLT [210] Communication DegradedSignal Indeterminate 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
424 / 778

[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
425 / 778
27.18 [75,211] LOSS-OF-CLK-2M

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] LOSS-OF-CLK-2M [211] Equipment TimingProblem Minor (DMA) The 2 MHz clock source is lost. Once the PAD detects the loss of the 2MHz clock source, the next clock source will be selected if available. The firmware will detect the missing clock source number. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling Yes No
426 / 778

[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
427 / 778
27.19 [75,216] RESTART

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] RESTART [216] Processing Error SoftwareError Indeterminate n autonomous processor restart has occurred. The operating system and all processes are re-initialized sequentially. A new initialization of the dynamic data takes place. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - this alarm reports an autonomous restart. See TC Alarms (Section 36.5) for the Alarm number description.
428 / 778
27.20 [75,221] TRIB-TWO-MB-MISSING

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] TRIB-TWO-MB-MISSING [221] Communication LossOfSignal 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling Yes No
429 / 778

[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
430 / 778
27.21 [75,222] TRIB-AIS-2MB

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] TRIB-AIS-2MB [222] Communication Ais Minor (DMA) The 2 Mbit/s on one tributary interface is receiving an AIS signal (all ones). G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling Yes No
431 / 778

[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
432 / 778
27.22 [75,223] TRIB-FRAME-ALIGNMENT

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] TRIB-FRAME-ALIGNMENT [223] Communication LossOfFrame 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling Yes No
433 / 778

[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
434 / 778
27.23 [75,224] TRIB-CRC-MFRAME-ALGN

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] TRIB-CRC-MFRAME-ALGN [224] Communication LossOfFrame 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling Yes No

[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
435 / 778
27.24 [75,225] TRIB-BER-10E-3

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] TRIB-BER-10E-3 [225] Communication DegradedSignal 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling Yes No
436 / 778

[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
437 / 778
27.25 [75,226] TRIB-BER-10E-4

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] TRIB-BER-10E-4 [226] Communication DegradedSignal 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
438 / 778

[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
439 / 778
27.26 [75,227] TRIB-BER-10E-6

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] TRIB-BER-10E-6 [227] Communication DegradedSignal 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
440 / 778

[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
441 / 778
27.27 [75,228] TRIB-FAR-END-ALARM

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] TRIB-FAR-END-ALARM [228] Communication LocalNodeTransmissionError 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling No No
442 / 778

[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
443 / 778
27.28 [75,231] ATER-TWO-MB-MISSING

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] ATER-TWO-MB-MISSING [231] Communication LossOfSignal 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling No Yes
444 / 778

[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
445 / 778
27.29 [75,232] ATER-AIS-2MB

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] ATER-AIS-2MB [232] Communication Ais Minor (DMA) The 2 Mbit/s interface on one Ater interface is receiving an AIS signal (all ones). G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling No Yes
446 / 778

[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
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
447 / 778
27.30 [75,233] ATER-FRAME-ALIGNMENT

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] ATER-FRAME-ALIGNMENT [233] Communication LossOfFrame 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No Yes
Cell/BTS(s) No No
Signaling No Yes
448 / 778

[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
449 / 778
27.31 [75,234] ATER-CRC-MFRAME-ALGN

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] ATER-CRC-MFRAME-ALGN [234] Communication LossOfFrame 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No Yes
Cell/BTS(s) No No
Signaling No Yes

[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
450 / 778
27.32 [75,235] ATER-BER-10E-3

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] ATER-BER-10E-3 [235] Communication DegradedSignal 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling No Yes
451 / 778

[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
452 / 778
27.33 [75,236] ATER-BER-10E-4

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] ATER-BER-10E-4 [236] Communication DegradedSignal 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
453 / 778

[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
454 / 778
27.34 [75,237] ATER-BER-10E-6

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] ATER-BER-10E-6 [237] Communication DegradedSignal 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
455 / 778

[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
456 / 778
27.35 [75,238] ATER-FAR-END-ALARM

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] ATER-FAR-END-ALARM [238] Communication LocalNodeTransmissionError Minor (DMA) 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling No No
457 / 778

[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
458 / 778
27.36 [75,241] SET-PROD-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] SET-PROD-FAIL [241] Processing Error ConfigurationOrCustomizationError Minor (DMA) This alarm indicates the NE settings production has failed. The equipment settings are not in line with the DLS. G2 TC and 9125 TC See Consequences of an SBL State Change.
Impact Loss
Trunk(s) Yes (if SM-ADAPT) Yes (if TC-ADAPT)
Cell/BTS(s) No
Signaling Yes (if SM-ADAPT) Yes (if TC-ADAPT)
Call Handling Yes (if SM-ADAPT) Yes (if TC-ADAPT)
Degradation
No
No

DSL settings OK?
yes
Lock SM/TCADAPT
Unlock SM/TCADAPT
Alarm solved
no
Alarm persists?
yes
459 / 778
27.37 [75,245] LOCAL-REINIT-REQ

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] LOCAL-REINIT-REQ [245] Equipment EquipmentUnderTest 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. G2 TC and 9125 TC SM-ADAPT: All calls managed by the processor are lost with or without WTC as specified by the operator. TC-ADAPT: All calls managed by the processor are lost with or without WTC as specified by the operator. See Consequences of an SBL State Change.
Impact Loss
Cell/BTS(s) No
Degradation
No
No
460 / 778

[75,245] LOCAL REINITREQ
no Correct settings
BTS parameter settings OK? yes
Disable SM/TCADAPT
Init SM/TCADAPT
Alarm solved
no
Alarm persists?
yes
461 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] DOWNLOAD-FAIL [246] 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. G2 TC and 9125 TC SM-ADAPT:All calls managed by the processor are lost with or without WTC as specified by the operator. TC-ADAPT: All calls managed by the processor are lost with or without WTC as specified by the operator. See Consequences of an SBL State Change.
Impact Loss
Cell/BTS(s) No
Degradation
No
No
462 / 778

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

specificProblems eventType probableCause perceivedSeverity Alarm Description TCSM-ADAPT [75] ACCESS-FAIL [247] Equipment EquipmentMalfunction 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. G2 TC and 9125 TC SM-ADAPT: All calls managed by the processor are lost with or without WTC as specified by the operator. TC-ADAPT: All calls managed by the processor are lost with or without WTC as specified by the operator. See Consequences of an SBL State Change.
Impact Loss
Cell/BTS(s) No
Degradation
No
No

[75,247] ACCESSFAIL
TCU/TSL/NE alarm events?
no
Alarm solved
no
Alarm persists?
yes
464 / 778
28 Class 96: PROCESS Alarms

This section defines the BSC alarms for the Class 96: PROCESS alarm class.
465 / 778
28.1 [96,0] RESET

specificProblems eventType probableCause perceivedSeverity Alarm Description PROCESS [96] RESET [0] Processing Error SoftwareError Indeterminate (MI) The VCE has been successfully reset. The service managed by this VCE is lost. 9130 BSC The impacted SBL state is not changed. In case CPR or DTC TCH-RM (running on OMCP board): All stable calls are not affected. Due to TCH-RM takeover some signaling messages can be lost which can affect some transactions in progress (call setup or handovers). Some CMISE exchanges or file transfers with OMC-R may be interrupted. If this happens, the OMC-R requests the information again. In case TCU: All calls carried by TRX managed by the TCU are lost. New calls can be established after the reset. If the TCU carries OML, O&M operations with BTS are stopped. In case of DTC (except TCH-RM DTC running on OMCP board): All calls carried by the Atrunk managed by the DTC process are lost. For DTC carrying SCCP, all SCCP connections managed by the DTC process are lost. New calls can be established by using other Atrunks and other SCCP DTC. In case of TSC: All transmission downloading managed by the process are lost.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - The VCE has been successfully reset.
466 / 778
28.2 [96,1] RESTART

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System PROCESS [96] RESTART [1] Processing Error SoftwareError Indeterminate (MI) The VCE has successfully restarted. No service (call) was lost. 9130 BSC The impacted SBL state is not changed. In case CPR: There is no telecom impact. Some CMISE exchanges or file transfers with OMC-R may be interrupted. If this happens, the OMC-R requests the information again. In case TCU or DTC (including TCH-RM DTC mapped on OMCP board): All stable calls are not affected. Some signaling messages can be lost which can affect some transactions in progress (call setup or handovers). In case of TSC: All transmission downloading managed by the process are lost.
Impact Loss
Trunk(s) No
Cell/BTS(s) No
Signaling No
Call Handling Possible (if TCU or DTC) No
Degradation
No
No
No
Yes (if CPR)

None - The VCE has been successfully restarted.
467 / 778
28.3 [96,2] MULTIPLE-RESET

specificProblems eventType probableCause perceivedSeverity Alarm Description PROCESS [96] MULTIPLE-RESET [2] Processing Error SoftwareError Major (PMA) The VCE has reset more than 3 times in 1 hour, and is no longer recreated. 9130 BSC The impacted SBL state is set to FLT. In case CPR or DTC TCH-RM (mapped on OMCP board): All stable calls are not affected. Due to TCH-RM takeover some signaling messages can be lost which can affect some transactions in progress (call setup or handovers). Some CMISE exchanges or file transfers with OMC-R may be interrupted. If this happens, the OMC-R requests the information again. In case TCU: All calls carried by TRX managed by the TCU are lost. If the TCU carries OML, O&M operations with BTS are stopped. In case of DTC (except TCH-RM DTC mapped on OMCP board). All calls carried by the Atrunk managed by the DTC process are lost. For DTC carrying SCCP, all SCCP connections managed by the DTC process are lost. New calls can be established by using other Atrunks and other SCCP DTC. In case of TSC: All transmission configuration and transmission supervision managed by the process are lost.
Impact Loss
Trunk(s) Yes (if DTC except TCH-RM DTC mapped on OMCP) -
Cell/BTS(s) Yes (if TCU and all TRX are carried by this TCU)
Signaling Yes (if TCU or if DTC carries N7 or GSL)
Call Handling Yes (if CPR, TCU or DTC)
O&M; Capabilities Yes (if TCU carries OML)
Degradation
Yes (if TCU and some TRX are carried by other TCU)
No
No
Yes (ifCPR or DTC TCH-RM (mapped on OMCP board)
468 / 778

[96, 2] MULTIPLE RESET
Board carrying the process is ok?
no
Solve other board related alarms
Reset the process
Alarm persists?
no
yes
yes
Reset the board carrying the process
Alarm persists?
no
Alarm solved
Status of other boards is ok?
no
Solve other boards related alarms
Alarm persists?
no
yes
469 / 778
28.4 [96,3] ACCESS-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System PROCESS [96] ACCESS-FAIL [3] Equipment EquipmentMalfunction Major (PMA) The VCE cannot be created. 9130 BSC The impacted SBL state is set to FLT. For detailled impacts, See Process, Multiple Reset [96,2]
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
470 / 778

[96, 3] ACCESS FAIL
Reset the target VCE
Alarm persists?
no
yes
Reset the board hosting the VCE
Alarm solved
Alarm persists?
no
yes
471 / 778
472 / 778
29 Class 97: ATCA-PROCESSOR Alarms

This section defines the BSC alarms for the Class 97: ATCA-PROCESSOR alarm class.
473 / 778
29.1 [97,0] RESET

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] RESET [0] Processing Error SoftwareError Indeterminate Board reset was successfully. If the board was active a switchover was performed. 9130 BSC The impacted SBL state is not changed. There is no system impact if the board is the standby OMCP, CCP or TP. If the board is the active OMCP, CCP or TP, the BSC triggers a takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

None - The board has been successfully reset.
474 / 778
29.2 [97,1] TAKEOVER

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-PROCESSOR [97] TAKEOVER [1] Processing Error SoftwareProgramAbnormallyTerminated Indeterminate A board takeover was performed due to a failure on the active board. 9130 BSC The impacted SBL state is not changed. In case of OMCP (CP-HW #1 or CP-HW #2): - All stable calls are not affected. - Due to TCH-RM takeover some signaling messages can be lost which can affect some transactions in progress (call setup or handovers). - Some file transfers with OMC-R may be interrupted. If this happens, the OMC-R requests the information again. - All transmission downloading managed by the TSC are lost . In case CCP (other CP-HW): - All calls carried by TRX managed by TCU of this CCP and all calls carried by the Atrunk managed by DTC of this CCP and all SCCP connections managed by DTC of this CCP are lost. New calls can be established after the takeover occurs. In case of TP-HW: total N7 down (normally for 2-3 seconds), no new calls while N7s are down,External Hos (inter-BSC), SMS and other services may be impacted.
Trunk(s) No Yes (if CCP)
Cell/BTS(s) No Yes (if CCP)
Signaling Yes (if TP) Yes (if CCP)
Call Handling Yes (if CCP) Yes (if OMCP)
O&M; Capabilities No Yes (if OMCP or CCP)

None - A board takeover was successfully performed.
475 / 778
29.3 [97,2] RLC-OV

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] RLC-OV [2] Equipment EquipmentMalfunction Major (PMA) The board has reset more than three times in one hour and was powered-off. 9130 BSC The impacted SBL state is changed to FLT. System impacts are due to previous reset event. System impacts are due to previous reset event (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[97, 2] RLC OV
Other Event alarms for the board are present?
yes
Solve boards related alarms
Alarm persists?
no
yes
Onsite
Replace board
Alarm persists?
no
Alarm solved
yes
476 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] ACCESS-FAIL [3] Equipment EquipmentMalfunction Major (PMA) The board cannot start because of problems in the INIT sequence. It powered off. List of possible causes: - Timeout on Board Ready - Timeout on NE1oE contact message (TP-GSM) - Timeout of MXPF service request for this board. - Initial configuration request rejected by TP-GSM (checks of config files failed). This alarm may happen when handles are opened 9130 BSC The impacted SBL state is changed to FLT. There is no system impact if the board is the standby OMCP, CCP or TP. If the board is the active OMCP, CCP or TP, the BSC triggers a takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
477 / 778

[97, 3] ACCESS FAIL
Other ATCA shelf related alarms are present?
yes
Solve other alarms
Alarm persists?
no
Reset board
Onsite
yes
Alarm persists?
no
Alarm solved
478 / 778
29.5 [97,4] APPLICATION-FATAL-TERMINATION

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-PROCESSOR [97] APPLICATION-FATAL-TERMINATION [4] Processing Error ApplicationSubsystemFailure Indeterminate The board was reset due to BSC fatal process termination. 9130 BSC The impacted SBL state is not changed. The problem could happen only on active OMCP and when it happens the BSC triggers a takeover.
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

None.
479 / 778
29.6 [97,5] SYSTEM-FATAL-TERMINATION

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-PROCESSOR [97] SYSTEM-FATAL-TERMINATION [5] Processing Error SoftwareError Indeterminate The board was reset due to platform fatal process termination. 9130 BSC The impacted SBL state is not changed. There is no system impact if the board is the standby OMCP or CCP. If the board is the active OMCP or CCP, the BSC triggers a takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

None.
480 / 778
29.7 [97,6] UNPLUGGED

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] UNPLUGGED [6] Equipment Unavailable Minor (DMA) The board was removed from the ATCA shelf. Alarm will be cleared st bord re-insertion. 9130 BSC The impacted SBL state is changed to FLT. There is no system impact if the board is the standby OMCP, CCP or TP. If the board is the active OMCP, CCP or TP, the BSC triggers a takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[97, 6] UNPLUGGED
Board is correctly inserted?
no Reinsert the board
Alarm persists?
no
Alarm solved
yes
481 / 778
29.8 [97,7] FW-UPGRADE-UNSUCCESS

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] FW-UPGRADE-UNSUCCESS [7] Equipment EquipmentMalfunction Critical (VPMA) The alarm is reported when firmware upgrade is triggered successfully, but it fails to upgrade 9130 BSC If alarm "FIRMWARE_NOT_UTD" is reported before, there is no impact to related SBL. If alarm "FIRMWARE_INCOMP" is reported before, the related SBL will change to FLT.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[97, 7] FWUPGRADEUNSUCCESS
Trigger firmware upgrade again
Alarm persists?
no
Alarm solved
yes
482 / 778
29.9 [97,8] FW-UPGRADE

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] FW-UPGRADE [8] Processing Error UnderlyingResourceUnavailable minor(DMA) Operator has launched firmware upgrade in the board on the field. All operations on this board(lock,reset) are rejected while this alarm is active. 9130 BSC The impacted SBL is set to FLT.
Trunk(s)
Cell/BTS(s)
Signaling
Call Handling
O&M; Capabilities

None - the operator has launched firmware upgrade in the board.
483 / 778
29.10 [97,9] FIRMWARE-INCOMPATIBILITY

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] FIRMWARE-INCOMPATIBILITY [9] Equipment EquipmentMalfunction Major (PMA) If the firmware version is not compatible with BSC application, the alarm will be reported. 9130 BSC Two cases: 1) No scenario is ongoing for specific OMCP, CCP and TP If the related SBL is IT/FIT and the version check messageis received, the related SBL will be changed to FIT. 2) There is scenario ongoing for specific OMCP, CCP and TP. Typically, OMCP, CCP and TP startup scenario. If version check message is received, no state change for related SBL. Typically, the state is from MSD/MSA to MSD/MSA.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
484 / 778
29.11 [97,10] FATAL-HW-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] FATAL-HW-FAILURE [10] Equipment EquipmentMalfunction Major (PMA) Operator has launched firmware upgrade in the board on the field. All operations on this board(lock,reset) are rejected while this alarm is active. 9130 BSC The impacted SBL state is changed to FLT.
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[97, 10] FATALHWFAILURE
Onsite
Alarm persists?
no
Alarm solved
485 / 778
29.12 [97,11] TEMPERATURE-CRITICAL

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] TEMPERATURE-CRITICAL [11] Environmental HeatingOrVentilationOrCoolingSystemProblem Critical (VPMA) Hardware or environmental fatal alarm. Temperature of the unit is over the "critical" threshold. The station is stopped.Room or chassis air conditioning is defective, or the unit over heats. 9130 BSC The impacted SBL state is changed to FLT. There is no system impact if the board is the standby OMCP, CCP or TP. If the board is the active OMCP, CCP or TP, the BSC triggers a takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
486 / 778

[97, 11] TEMPERATURE CRITICAL
Fan status is ok?
no
Solve fan related problems
Alarm persists?
no
yes
yes
Alarm solved
Environment status is ok?
no
Solve environment related problems
Alarm persists?
no
yes
yes
Onsite
Alarm persists?
no
Alarm solved
487 / 778
29.13 [97,12] TEMPERATURE-MAJOR

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] TEMPERATURE-MAJOR [12] Environmental HeatingOrVentilationOrCoolingSystemProblem Major (PMA) Hardware or environmental non-fatal alarm. The unit temperature is over the "major" threshold. The station is still running.The room or chassis air conditioning unit is defective, or the card over heats. 9130 BSC The impacted SBL is set to FIT. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
488 / 778

[97, 12] TEMPERATURE MAJOR
no Fan status is ok?
Alarm persists?
no
yes
yes
Alarm solved
no
Alarm persists?
no
yes
yes
Onsite
Alarm persists?
no
Alarm solved
489 / 778
29.14 [97,14] VOLTAGE-FATAL

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] VOLTAGE-FATAL [14] Equipment PowerProblem Critical (VPMA) Power supply voltage is over "critical" threshold. The functional status is impacted and the FRU is powered off. 9130 BSC The impacted SBL state is changed to FLT. There is no system impact if the board is the standby OMCP, CCP or TP. If the board is the active OMCP, CCP or TP, the BSC triggers a takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -
490 / 778

[97, 14] VOLTAGE FATAL
PEM status is ok?
no
Solve PEM related problems
Alarm persists?
no
yes
yes
Alarm solved
Site power supply status is ok?
no
Solve site power supply related problems
Alarm persists?
no
yes
yes
Onsite
Alarm persists?
no
Alarm solved
491 / 778
29.15 [97,15] VOLTAGE-MAJOR

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] VOLTAGE-MAJOR [15] Equipment PowerProblem Major (PMA) Power supply voltage is over "major" threshold. The functional status may be impacted.The power status is severely degraded. 9130 BSC The impacted SBL is set to FIT. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
492 / 778

[97, 15] VOLTAGE MAJOR
PEM status is ok?
no
Alarm persists?
no
yes
yes
Alarm solved
no
Alarm persists?
no
yes
yes
Onsite
Alarm persists?
no
Alarm solved
493 / 778
29.16 [97,16] VOLTAGE-MINOR

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] VOLTAGE-MINOR [16] Equipment PowerProblem Minor (DMA) Power supply voltage is over "minor" threshold. The functional status is not impacted. The power status is degraded. 9130 BSC The impacted SBL is set to FIT. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
494 / 778

[97, 16] VOLTAGE MINOR
PEM status is ok?
no
Alarm persists?
no
yes
yes
Alarm solved
no
Alarm persists?
no
yes
yes
Onsite
Alarm persists?
no
Alarm solved
495 / 778
29.17 [97,17] ETHERNET-LINK-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] ETHERNET-LINK-FAILURE [17] Equipment EquipmentMalfunction MI One Ethernet link of the FRU is down. In case active OMCP is impacted: Any Ethernet link failure will result in a reset of that OMCP and a takeover. In all other cases: If the failure is not on the active Ethernet connection, the alarm is raised and no auto defense is done by the BSC. If the alarm is on the active Ethernet connection, then process supervision mechanisms will trigger an IP failover in the BSC. Consequently the failed link will then become the "not active one" and the alarm is raised. 9130 BSC The impacted SBL state is changed. No system impact due to the active/standby function and IP failover
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
496 / 778

[97, 17] ETHERNET LINK FAILURE
Reset the board raising the alarm
Alarm persists?
no
yes
Check SSW status
Replace the board raising the alarm
Alarm persists?
no
Alarm solved
yes
Onsite
Replace SSW for the standby IP plane *
Alarm persists?
no
yes
*: The active IP plane may be mapped on the active or the standby SSW. There is no correlation between the two. In order to identify the standby IP plane, check which is the active and standby shelf manager. The active IP plane is linked to the active SMM. Mapping SSW-SMM: SMM(1) is connected to SSW(1) and SMM(2) to SSW(2).
497 / 778
29.18 [97,18] IPMI-FIRMWARE-NOT-UP-TO-DATE

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] IPMI-FIRMWARE-NOT-UP-TO-DATE [18] Equipment EquipmentMalfunction Minor (DMA) When the board is started, an automatic check of the IPMC firmware version is performed. This alarm is reported to OMC-R if it is not the latest version. 9130 BSC The ALARM shows that the current IPMC FW version running on TP board does not fit with the up-to-date FW version. FW version will auto update. There is no other system impact.
Trunk(s) NO NO
Cell/BTS(s) NO NO
Signaling NO NO
Call Handling NO NO
29.18.1 IPMI-FIRMWARE-NOT-UP-TO-DATE
The IPMC FW version running on TP board is automatic updated.
498 / 778
29.19 [97,19] FIRMWARE-NOT-UP-TO-DATE

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] FIRMWARE-NOT-UP-TO-DATE [19] Equipment EquipmentMalfunction Minor (DMA) When the board is started, an automatic check of the firmware version is performed. This alarm is reported to OMC-R if it is not the supported version. 9130 BSC The ALARM shows that the current FW version running on OMCP, CCP and TP boards does not fit with the up-to-date FW version. The SBL of impacted OMCP, CCP and TP is set to FIT. There is no other system impact.
Trunk(s) NO NO
Cell/BTS(s) NO NO
Signaling NO NO
Call Handling NO NO

[97, 19] FIRMWARE NOT UP TO DATE
Perform firmware upgrade procedure
Alarm persists?
no
Alarm solved
yes
499 / 778
29.20 [97,20] CONFIGURATION-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-PROCESSOR [97] CONFIGURATION-FAILURE [20] Processing Error ConfigurationOrCustomizationError Minor (DMA) An TP-GSM configuration error occured. 9130 BSC The impacted SBL state is changed to FIT. The new TP configuration is not taken into account. There may be transmission inconsistencies between the BSC and the BTS, the MFS or the TC. The new TP configuration is not taken into account. There may be transmission inconsistencies between the BSC and the BTS, the MFS or the TC.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - An TP-GSM configuration error occured.
500 / 778
29.21 [97,21] TAKEOVER-REFUSED

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] TAKEOVER-REFUSED [21] Processing Error SoftwareProgramAbnormallyTerminated Indeterminate An TP-GSM configuration error occurred. No takeover was possible due to unavailable stand-by board. 9130 BSC The impacted SBL state is not changed. All CS and PS traffic, all telecom or O&M signalling are stopped during the reset of the TP board. If the link between the BSC and the OMC-R is through Ater, the communication with OMC-R is also stopped during the reset of the TP board. Once the TP board is reset, the BSC comes back into traffic.
Trunk(s) No Yes
Cell/BTS(s) No Yes
Signaling No Yes

None - No takeover was possible due to unavailable stand-by board.
501 / 778
29.22 [97,22] CPU-OVERLOAD

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] CPU-OVERLOAD [22] Equipment processorProblem Indeterminate (MI) If the CPU load is crossing up or crossing down very quickly between two CPU overload levels at once, then the event alarm will be sent when the first crossing level is reached. 9130 BSC Auto TP takeover is triggered and related SBL state is depended on corresponding actions
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No

None - No action since auto TP takeover is triggered.
502 / 778
29.23 [97,23] BSC-CONF-UNAVAILABLE

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] BSC-CONF-UNAVAILABLE [23] Equipment Indeterminate Minor(DMA) The configuration running in BSC could not be recognized by TPGSM. Only the BSC-OMCR connection is available. 9130 BSC The related TP-HW will change to FIT.
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no

[97, 23] BSCCONFUNAVAILABLE
Check the DLS and if it is not OK replace it.
Alarm persists?
no
Alarm solved
yes
503 / 778
29.24 [97,30] N7-DEVICE

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] N7-DEVICE [30] Equipment EquipmentMalfunction Indeterminate A major failure is detected in the Power Quicc of the TPGSM board. The Power Quicc carries the MTP2 and MTP1 layers of the SS7 stacks. 9130 BSC The impacted SBL state is not changed. When this problem is detected, the BSC triggers a TP takeover and TP reset. System impacts are due to the TP takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[97, 30] N7 DEVICE
Onsite
Replace suspected RIT, if alarm occurs repetitively
Alarm persists?
no
Alarm solved
504 / 778
29.25 [97,31] HDLC-HANDLER

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-PROCESSOR [97] HDLC-HANDLER [31] Equipment EquipmentMalfunction Indeterminate A major failure is detected in the HDLC handler of the TPGSM board. 9130 BSC The impacted SBL state is not changed When this problem is detected, the BSC triggers a TP takeover and TP reset. System impacts are due to the TP takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[97, 31] HDLC HANDLER
Onsite
Alarm persists?
no
Alarm solved
505 / 778
29.26 [97,32] Q1-HANDLER

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-PROCESSOR [97] Q1-HANDLER [32] Equipment EquipmentMalfunction Indeterminate A major failure is detected in the Qmux handler of the TPGSM board. 9130 BSC The impacted SBL state is not changed. When this problem is detected, the BSC triggers a TP takeover and TP reset. System impacts are due to the TP takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[97, 32] Q1 HANDLER
Onsite
Alarm persists?
no
Alarm solved
506 / 778
29.27 [97,33] RW-HANDLER

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] RW-HANDLER [33] Equipment EquipmentMalfunction Indeterminate A major failure is detected in the Read/Write handler of the TPGSM board. 9130 BSC The impacted SBL state is not changed. When this problem is detected, the BSC triggers a TP takeover and TP reset. System impacts are due to the TP takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[97, 33] RW HANDLER
Onsite
Alarm persists?
no
Alarm solved
507 / 778
29.28 [97,34] TDM-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-PROCESSOR [97] TDM-FAILURE [34] Equipment EquipmentMalfunction Indeterminate A major failure is detected in the TDM switch of the TPGSM board. 9130 BSC The impacted SBL state is not changed. When this problem is detected, the BSC triggers a TP takeover and TP reset. System impacts are due to the TP takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[97, 34] TDM FAILURE
Onsite
Alarm persists?
no
Alarm solved
508 / 778
29.29 [97,35] E1-FRAMER

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-PROCESSOR [97] E1-FRAMER [35] Equipment EquipmentMalfunction Indeterminate A major failure is detected in the E1 handlers of the TPGSM board. 9130 BSC The impacted SBL state is not changed. When this problem is detected, the BSC triggers a TP takeover and TP reset. System impacts are due to the TP takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[97, 35] E1 FRAMER
Onsite
Alarm persists?
no
Alarm solved
509 / 778
29.30 [97,36] TP-MAIN-SW-ERROR

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] TP-MAIN-SW-ERROR [36] Equipment EquipmentMalfunction Indeterminate A major failure is detected in the TP_MAIN process of the TPGSM board. 9130 BSC The impacted SBL state is not changed. When this problem is detected, the BSC triggers a TP takeover and TP reset. System impacts are due to the TP takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

None - A major failure was detected in a process of the TPGSM board.
510 / 778
29.31 [97,37] TP-MAIN-FILE-ERROR

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] TP-MAIN-FILE-ERROR [37] Equipment EquipmentMalfunction Indeterminate TPGSM board download is not successfully and the configuration from the OMCP board. is used. 9130 BSC The impacted SBL state is not changed. When this problem is detected, the BSC triggers a TP takeover and TP reset. System impacts are due to the TP takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

None - TPGSM board download was not successfully.
511 / 778
29.32 [97,38] TP-MAIN-ACCESS-PB

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] TP-MAIN-ACCESS-PB [38] Equipment EquipmentMalfunction Indeterminate Data exchanges between the active and standby boards are not successful. 9130 BSC The impacted SBL state is not changed. When this problem is detected, the BSC triggers a TP takeover and TP reset. System impacts are due to the TP takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities No -
512 / 778

[97, 38] TP MAIN ACCESS PB
Hardware related alarms are present?
yes
Solve hardware relatedvalarms
Alarm persists?
no
Alarm solved
no
yes
Reset standby TP board
Alarm persists?
no
Alarm solved
yes
513 / 778
29.33 [97,39] SS7-SW-ERROR

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-PROCESSOR [97] SS7-SW-ERROR [39] Equipment EquipmentMalfunction Indeterminate A major failure is detected in the TP_SS7 process of the TPGSM board. 9130 BSC The impacted SBL state is not changed. When this problem is detected, the BSC triggers a TP takeover and TP reset. System impacts are due to the TP takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

None - A major failure was detected in the TP_SS7 process of the TPGSM board.
514 / 778
29.34 [97,40] CS-TEL-TEST-NOK

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] CS-TEL-TEST-NOK [40] Communication communicationSubsystemFailure Minor(DMA) Upon the CS telecome outage suspecting for one CCP, the telecom test for Abis interface is triggered and the test result is not OK. 9130 BSC related CCP will change to FIT
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no

[97, 40] CSTELTESTNOK
Reset the related CCP board.
Alarm persists?
no
Alarm solved
yes
515 / 778
29.35 [97,50] NE1OE-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-PROCESSOR [97] NE1OE-FAILURE [50] Equipment EquipmentMalfunction Indeterminate There is a failure of the NE1oE module on TP-GSM. 9130 BSC The impacted SBL state is not changed. When this problem is detected, the BSC triggers a TP takeover and TP reset. System impacts are due to the TP takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
516 / 778

[97, 50] NE1OE FAILURE
SSW status ok?
no
Solve SSW related problems
Alarm persists?
no
Alarm solved
yes
yes
Onsite
Replace TP board
Alarm persists?
no
Alarm solved
517 / 778
29.36 [97,51] E1-SL-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] E1-SL-FAILURE [51] Equipment EquipmentMalfunction Indeterminate NE1oE module on the TP-GSM has reported a 16E1 SL failure with the processing part 9130 BSC The impacted SBL state is not changed. When this problem is detected, the BSC triggers a TP takeover and TP reset. System impacts are due to the TP takeover (see ATCA-PROCESSOR [97], TAKEOVER [1]).
Trunk(s) -
Cell/BTS(s) -
Signaling -
Call Handling -
O&M; Capabilities -

[97, 51] E1 SL FAILURE
Onsite
Replace TP board if alarm occurs repetitively
Alarm persists?
no
Alarm solved
518 / 778
29.37 [97,60] TP-CAP

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] TP-CAP [60] Equipment EquipmentMalfunction Major (PMA) Two case that the alarm will be sent: 1. During BSC startup, if HSL or IPoE1 is enabled, but TPGSM does not have the corresponding capabilities, cant support so many Atermux. TPGSM is forced to power off. 2. When STM-1 feature is activated, if TP version is less than 3 (TP1&TP2). TPGSM is forced to power off. 9130 BSC FOS when alarm begins, IT when alarm ends
Trunk(s) NO NO
Cell/BTS(s) NO NO
Signaling NO NO
Call Handling NO NO

[97,60] TPCAP
Onsite
Replace TP board with correct version
Alarm persists?
no
Alarm solved
519 / 778
29.38 [97,61] TPIP-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] TPIP-FAILURE [61] Equipment EquipmentMalfunction Indeterminate (MI) It indicates the status of TPIP daughter board of TPGSM. TPGSM send a notification mpTpgNotifyFailure when it detects TPIP failure or end of failure. 9130 BSC FLT when alarm begins, FLT/IT when alarm ends
Trunk(s) NO NO
Cell/BTS(s) NO NO
Signaling NO NO
Call Handling NO NO

[97, 61] TPIPFAILURE
no
IPOverE1 is activated?
yes
Onsite
Replace TP board
Alarm persists?
no
Alarm solved
520 / 778
29.39 [97,62] CONFIG-IP-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-PROCESSOR [97] CONFIG-IP-FAILURE [62] Equipment EquipmentMalfunction Indeterminate (MI) Config IP address failure 9130 BSC FLT when alarm begins, IT when alarm ends
Trunk(s) NO NO
Cell/BTS(s) NO NO
Signaling NO NO
Call Handling NO NO

[97, 62] CONFIGIPFAILURE
Check DLS for IP configuration
Alarm persists?
no
Alarm solved
yes
521 / 778
29.40 [97,63] CONFIG-IP-INPUT-ERROR

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-PROCESSOR [97] CONFIG-IP-INPUT-ERROR [63] Equipment EquipmentMalfunction Indeterminate (MI) input parameter of Config IP address is not correct. 9130 BSC FLT when alarm begins, IT when alarm ends
Trunk(s) NO NO
Cell/BTS(s) NO NO
Signaling NO NO
Call Handling NO NO

[97, 63] CONFIGIPINPUTERROR
Alarm persists?
no
Alarm solved
yes
522 / 778
29.41 [97,64] CONFIG-IP-RUNTIME-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] CONFIG-IP-RUNTIME-FAILURE [64] Equipment EquipmentMalfunction Indeterminate (MI) this alarm is sent out when config IP address store parameter in disk failure 9130 BSC FLT when alarm begins, IT when alarm ends
Trunk(s) NO NO
Cell/BTS(s) NO NO
Signaling NO NO
Call Handling NO NO

[97, 64] CONFIGIPRUNTIMEFAILURE
Alarm persists?
no
Alarm solved
yes
523 / 778
29.42 [97,65] DRIVERS-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] DRIVERS-FAILURE [65] Equipment EquipmentMalfunction PMA(Major) when the TP startup , the driver load error log file should be checked , if there is no any error ,tp will startup normally , otherwise , tp will sent the alarm to bsc ,and wait for poweroff. 9130 BSC TP board will be power off.
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no

[97, 65] DRIVERSFAILURE
There is a hardware problem. Replace TP board.
Alarm persists?
no
Alarm solved
yes
524 / 778
29.43 [97,66] HW-DIAGNOSIS-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] HW-DIAGNOSIS-FAILURE [66] Equipment EquipmentMalfunction PMA(Major) TP will check the status file(which is store the hw-diagnosis), and send the alarm if there is any error. 9130 BSC The notified TPGSM board will reset.
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no

[97, 66] HWDIAGNOSISFAILURE
There is a hardware problem. Replace TP board.
Alarm persists?
no
Alarm solved
yes
525 / 778
29.44 [97,67] INTER-TP-ACCESS-PB

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-PROCESSOR [97] INTER-TP-ACCESS-PB [67] Equipment EquipmentMalfunction PMA(Major) BSC sends this alarm when the TPGSM detects the Time Out alarm on the TPGSM link between both TPGSM used to carry the STM1 APS data, The notified TPGSM has its SBL TP-HW state changed to FIT. 9130 BSC If the alarm is on at active TP board, The STM1 signal carried from the Standby board cannot be used any more, The STM1 paths are no more in 1+1 redundancy, Whether a STM1 TTP on the Active board is in FLT, the traffic of this STM1 itf is lost. See the BSC-Trans alarm for the STM1-TTP and STM1-itf SBL. If the alarm is on at standby TP board, no impact until the borad became to active.
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no

[97, 67] INTERTP ACCESSPB
Reset the TP board
Alarm persists?
no
Alarm solved
yes
526 / 778
30 Class 98: ATCA-SWITCH Alarms

This section defines the BSC alarms for the Class 98: ATCA-SWITCH alarm class.
527 / 778
30.1 [98,0] RESET

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-SWITCH [98] RESET [0] Processing Error SoftwareError Indeterminate The Switch board has reset 9130 BSC The impacted SBL state is not changed. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - The Switch board was reset.
528 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] ACCESS-FAIL [3] Equipment EquipmentMalfunction Major (PMA) The board cannot start because of problems in the INIT sequence (Timeout on Board Ready or timeout of MXPF service request for this board.) or handles of the boards are opened. The board is powered off 9130 BSC The impacted SBL state is changed to FLT. There is no system impact if mate board works well.
Trunk(s) NO NO
Cell/BTS(s) NO NO
Signaling NO NO
Call Handling NO NO

[98, 3] ACCESS FAIL
Reset target board
Alarm persists?
no
Alarm solved
yes
529 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] UNPLUGGED [6] Equipment Unavailable Minor (DMA) The board has been removed from the ATCA shelf. The alarm is cleared at board re-insertion. 9130 BSC The board is powered off and the impacted SBL is set to FLT. All traffic is redirected to the other SSW-HW. But if the alarm occurs on the first SSW-HW, the communication with the external alarm box is lost (if it is one is installed).
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
O&M; Capabilities No Yes (if OMC-R is connected directly)

[98, 6] UNPLUGGED
no
Reinsert the board
Alarm persists?
no
Alarm solved
yes
530 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] FW-UPGRADE-UNSUCCESS [7] Equipment EquipmentMalfunction Critical (VPMA) The alarm is reported when firmware upgrade is triggered successfully, but it fails to upgrade 9130 BSC If alarm "FIRMWARE_NOT_UTD" is reported before, there is no impact to related SBL. If alarm "FIRMWARE_INCOMP" is reported before, the related SBL will change to FLT.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

Alarm persists?
no
Alarm solved
yes
531 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] FW-UPGRADE [8] Processing Error UnderlyingResourceUnavailable Minor(DMA) Operator has launched firmware upgrade in the board on the field. All operations on this board(lock,reset) are rejected while this alarm is active. 9130 BSC The impacted SBL is set to FLT.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

532 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] FIRMWARE-INCOMPATIBILITY [9] Equipment EquipmentMalfunction Major (PMA) If the firmware version is not compatible with BSC application, the alarm will be reported. 9130 BSC Two cases: 1) No scenario is ongoing for specific SSW If the related SBL is IT/FIT and the version check messageis received, the related SBL will be changed to FIT. 2) There is scenario ongoing for specific SSW. Typically, SSW startup scenario. If version check message is received, no state change for related SBL. Typically, the state is from MSD/MSA to MSD/MSA.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
533 / 778

[98, 9] FIRMWAREINCOMPATIBILITY
no
Any scenario ongoing for SSW?
yes
Reset or unplug/plug SSW to trigger firmware upgrade
Firmware upgrade is triggered automatically. Pay attention to conditions to trigger firmware upgrade successfully
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes
yes
534 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] FATAL-HW-FAILURE [10] Equipment EquipmentMalfunction Major (PMA) The alarm can be raised in two cases, but with different target states. Case 1: fatal alarm with target state = FLT There is a hardware fault on the switch and it is powered off. Case 2: non fatal alarm with target state = FIT When the negotiated bitrate of a mandatory 1Gbps ethernet link of the SSW is found to be less than 1 Gbps. The bitrate of Gbit Ethernet links is auto-negotiated between the peers of the connection. The SSW port bitrates, for mandatory Gbps Ethernet ports, are checked in the following conditions: - Ethernet connected FRU is inserted (or power on) - Ethernet connected FRU is reset - BSC system initialization (including BSC power on, BSC reset) - At predefined intervals - every 15 minutes. The ports that are mandatory 1Gbps are blade FRU ports (TPGSM, CCP, OMCP) and MUX connection (nE1oE). If the bitrate is found to be less than 1Gbps, the alarm is raised. Applicability Impact on System 9130 BSC Case 1: The SSW board is powered off and the impacted SBL is set to FLT. All traffic is redirected to the other SSW-HW. But if the alarm occurs on the first SSW-HW, the communication with the external alarms box is lost (if one is installed). Case 2: The alarm is non-fatal and the SSW SBL is set to FIT. The BSC may have reduced performance due to bandwidth bottlenecks. In case the MUX connection is impacted, the lower bitrate may have an impact on the nE1oE performance (and E1 states) dependent on the number of E1 configured in the BSC. It is advised to trigger a RESET of the concerned SSW SBL in order to switch IP traffic to the redundant SSW plane.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
535 / 778
30.7.1 Corrective Action for Case 1

[98, 10] FATAL HW FAILURE
Onsite
Alarm persists? no
Replace SSW
yes
Onsite
Alarm persists? no Alarm solved
Replace SSW ARTM
yes
Onsite
Replace ARTM or FRU * Alarm persists? no
yes
* ARTM or FRU to be determined from the port number in additional data
536 / 778
30.7.2 Corrective Action for Case 2

The impacted port number on the SSW can be found in the additional data of the alarm. The problem can be due to peer of the concerned Ethernet link.
Port 18
Port number is 18 or other?
Any other port number
Onsite
Alarm persists? no
Replace SSW
yes
Onsite
Alarm persists? no no Alarm persists?
Onsite
Replace SSW ARTM
Replace SSW
yes
Alarm solved
yes
Onsite Onsite
Replace MUX Alarm persists? no no Alarm persists? Replace FRU *
yes yes
Replace cable between SSW ARTM port 2 and MUX
Alarm persists?
yes
Contact System Support * ARTM or FRU to be determined from the port number in additional data
537 / 778
30.8 [98,11] TEMPERATURE-FATAL

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] TEMPERATURE-FATAL [11] Environmental HeatingOrVentilationOrCoolingSystemProblem Critical (VPMA) Hardware or environmental fatal alarm. Temperature of the unit is over the "critical" threshold. The SSW is switched off. "critical" threshold: >80 degrees or < -10 degree. Applicability Impact on System 9130 BSC The board is powered off and the impacted SBL is set to FLT. All traffic is redirected to the other SSW-HW. But if the alarm occurs on the first SSW-HW, the communication with the external alarm box is lost (if one is installed).
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
538 / 778

[98, 11] TEMPERATURE FATAL
Fan status is ok?
no
Alarm persists?
no
yes
yes
Alarm solved
no
Alarm persists?
no
yes
yes
Onsite
Replace SSW
Alarm persists?
no
Alarm solved
539 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] TEMPERATURE-MAJOR [12] Environmental HeatingOrVentilationOrCoolingSystemProblem Major (PMA) Hardware or environmental major alarm. Temperature of the unit is over the "major" threshold. That may impact the functional status. "major" threshold: 80 degree > temp>75degrees or -10 degree < temp < -5 degree Applicability Impact on System 9130 BSC The impacted SBL is set to FIT. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
540 / 778

Fan status is ok?
no
Alarm persists?
no
yes
yes
Alarm solved
no
Alarm persists?
no
yes
yes
Onsite
Replace SSW
Alarm persists?
no
Alarm solved
541 / 778
30.10 [98,13] TEMPERATURE-MINOR

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] TEMPERATURE-MINOR [13] Environmental HeatingOrVentilationOrCoolingSystemProblem Minor (DMA) Hardware or environmental minor alarm. Temperature of the unit is over the "minor" threshold. The functional status is not impacted. "minor" threshold: 75 degree> temp>65degrees or -5 degree<temp< 0 degree Applicability Impact on System 9130 BSC The impacted SBL is set to FIT. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
542 / 778

[98, 13] TEMPERATURE MINOR
Fan status is ok?
no
Alarm persists?
no
yes
yes
Alarm solved
no
Alarm persists?
no
yes
yes
Onsite
Replace SSW
Alarm persists?
no
Alarm solved
543 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] VOLTAGE-FATAL [14] Equipment PowerProblem Critical (VPMA) Power supply voltage is over "critical" threshold. The functional status is impacted and the SSW is powered off. 9130 BSC The board is powered off and the impacted SBL is set to FLT. All traffic is redirected to the other SSW-HW. But if the alarm occurs on the first SSW-HW, the communication with the external alarm box is lost (if one is installed).
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
544 / 778

PEM status is ok?
no
Alarm persists?
no
yes
yes
Alarm solved
no
Alarm persists?
no
yes
yes
Onsite
Replace SSW
Alarm persists?
no
Alarm solved
545 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] VOLTAGE-MAJOR [15] Equipment PowerProblem Major (PMA) Power supply voltage is over "major" threshold. The functional status may be impacted.The power status is severely degraded. 9130 BSC The impacted SBL is set to FIT. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
546 / 778

[98, 15] VOLTAGE MAJOR
PEM status is ok?
no
Alarm persists?
no
yes
yes
Alarm solved
no
Alarm persists?
no
yes
yes
Onsite
Replace SSW
Alarm persists?
no
Alarm solved
547 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] VOLTAGE-MINOR [16] Equipment PowerProblem Minor (DMA) Power supply voltage is over "minor" threshold. The functional status is not impacted. The power status is degraded. 9130 BSC The impacted SBL is set to FIT. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
548 / 778

[98, 16] VOLTAGE MINOR
PEM status is ok?
no
Alarm persists?
no
yes
yes
Alarm solved
no
Alarm persists?
no
yes
yes
Onsite
Replace SSW
Alarm persists?
no
Alarm solved
549 / 778
30.14 [98,18] IP-ROUTER-LINK-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] IP-ROUTER-LINK-FAIL [18] Equipment Indeterminate Minor (DMA) The router to the external network is not reachable, the link is down or the router is out of service. 9130 BSC The impacted SBL is set to FIT. The external traffic towards the OMC-R or the CBC is redirected to the other SSW-HW and the other IP router link. Some file transfers with OMC-R may be interrupted, but if this happens the OMC-R requests the information again. If the alarm occurs on the first SSW-HW, the communication with the external alarm box is lost (if one is installed).
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
550 / 778

[98, 18] IP ROUTER LINK FAILED
Reset SSW
Alarm persists?
no
Alarm solved
yes
no IP router status is ok?
Solve router related issues
Alarm persists?
no
yes
IP router configuration is ok?
no
Correct IP router configuration
Alarm persists?
no
Alarm solved
yes
no Ethernet cable is ok?
Replace Ethernet cable
Alarm persists?
no
yes
551 / 778
30.15 [98,19] TELECOM-LINK-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] TELECOM-LINK-FAIL [19] Equipment Indeterminate Major (PMA) This alarm is generated when the telecom router is not reachable through this switch 9130 BSC The impacted SBL is set to FIT.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
552 / 778

[98, 19] TELECOMLINKFAIL
Reset SSW
Alarm persists?
no
yes
Check IP router status/configuration
Alarm persists?
no
Alarm solved
yes
Check Ethernet cable
Alarm persists?
no
yes
553 / 778
30.16 [98,20] OAM-LINK-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] OAM-LINK-FAIL [20] Equipment Indeterminate Major (PMA) This alarm is generated when the O&M router is not reachable through this switch 9130 BSC The impacted SBL is set to FIT.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
554 / 778

[98, 20] OAMLINKFAIL
Reset SSW
Alarm persists?
no
yes
Alarm persists?
no
Alarm solved
yes
Alarm persists?
no
yes
555 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SWITCH [98] FIRMWARE-NOT-UP-TO-DATE [21] Equipment EquipmentMalfunction Minor (DMA) When the board is started, an automatic check of the firmware version is performed. This alarm is reported to OMC-R if it is not the supported version. 9130 BSC The ALARM shows that the current FW version running on SSW boards does not fit with the up-to-date FW version. The SBL of impacted SSW is set to FIT. There is no other system impact.
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no

Alarm persists?
no
Alarm solved
yes
556 / 778
30.18 [98,22] IP-CONFIG-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-SWITCH [98] IP-CONFIG-FAIL [22] Equipment Indeterminate Major(PMA) The alarm is generatel when IP config fail 9130 BSC The impacted SBL is set to FIT.
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
O&M; Capabilities no Yes (if OMC-R is connected directly)
557 / 778

[98, 22] IPCONFIGFAIL
Reset SSW
Alarm persists?
no
yes
Alarm persists?
no
Alarm solved
yes
Alarm persists?
no
yes
558 / 778
30.19 [98,23] ASIG-OVER-IP-LINK-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-SWITCH [98] ASIG-OVER-IP-LINK-FAIL [23] Equipment Indeterminate Major (PMA) The alarm is generated when A singnal over IP link fail 9130 BSC The impacted SBL is set to FIT.
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
559 / 778

[98, 23] ASIGOVERIPLINKFAIL
Reset SSW
Alarm persists?
no
yes
Alarm persists?
no
Alarm solved
yes
Alarm persists?
no
yes
560 / 778
30.20 [98,24] BSS-OVER-IP-LINK-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-SWITCH [98] BSS-OVER-IP-LINK-FAIL [24] Equipment Indeterminate Major (PMA) The alarm is generated when BSS over IP link fail. 9130 BSC The impacted SBL is set to FIT.
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
561 / 778

[98, 24] BSSOVERIPLINKFAIL
Reset SSW
Alarm persists?
no
yes
Alarm persists?
no
Alarm solved
yes
Alarm persists?
no
yes
562 / 778
31 Class 99: ATCA-SHELF Alarms

This section defines the BSC alarms for the Class 99: ATCA-SHELF alarm class.
563 / 778
31.1 [99,0] RESET

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-SHELF [99] RESET [0] Processing Error SoftwareError Indeterminate The board has reset. 9130 BSC The state of the SBL is not changed. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - The board was reset.
564 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] ACCESS-FAIL [3] Equipment EquipmentMalfunction Major (PMA) The board cannot start because of problems in the INIT sequence (Timeout on Board Ready or timeout of MXPF service request for this board.) or handles of the boards are opened. The board is powered off. 9130 BSC The impacted SBL(SMM is not impacted) state is changed to FLT. There is no system impact if the mate board works well.
Trunk(s) NO NO
Cell/BTS(s) NO NO
Signaling NO NO
Call Handling NO NO

[99, 3] ACCESS FAIL
Reset target board
Alarm persists?
no
Alarm solved
yes
565 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] UNPLUGGED [6] Equipment Unavailable Minor (DMA) The board has been removed from the ATCA shelf. The alarm is cleared at board re-insertion. 9130 BSC The impacted SBL is set to FLT. There is no other system impact: shelf managers, personality cards, fans and PEM are redundant. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[99, 6] UNPLUGGED
no
Reinsert the board
Alarm persists?
no
Alarm solved
yes
566 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] FW-UPGRADE-UNSUCCESS [7] Equipment EquipmentMalfunction Critical (VPMA) The alarm is reported when firmware upgrade is triggered successfully, but it fails to upgrade 9130 BSC If alarm "FIRMWARE_NOT_UTD" is reported before, there is no impact to related SBL. If alarm "FIRMWARE_INCOMP" is reported before, the related SBL will change to FLT.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

Alarm persists?
no
Alarm solved
yes
567 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] FW-UPGRADE [8] Processing Error UnderlyingResourceUnavailable minor(DMA) Operator has launched firmware upgrade in the board on the field.All operations on this board(lock,reset) are rejected while this alarm is active. 9130 BSC The impacted SBL is set to FLT.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
31.5.1 Corrective Actions

568 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] FIRMWARE-INCOMPATIBILITY [9] Equipment EquipmentMalfunction Major (PMA) If the firmware version is not compatible with BSC application, the alarm will be reported. 9130 BSC Two cases: 1) No scenario is ongoing for specific SMM, PEM, FAN, PC If the related SBL is IT/FIT and the version check messageis received, the related SBL will be changed to FIT. 2) There is scenario ongoing for specific SMM, PEM, FAN, PC. Typically, SMM, PEM, FAN, PC startup scenario. If version check message is received, no state change for related SBL. Typically, the state is from MSD/MSA to MSD/MSA.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
569 / 778

[99, 9] FIRMWAREINCOMPATIBILITY
no
Any scenario ongoing for SMM/ PEM/FAN/PC?
yes
Reset or unplug/plug SMM/PEM/FAN/PC to trigger firmware upgrade
Firmware upgrade is triggered automatically. Pay attention to conditions to trigger firmware upgrade successfully
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes
yes
570 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] FATAL-HW-FAILURE [10] Equipment EquipmentMalfunction Major (PMA) There is a hardware fault on the FRU or, in case of standby SMM, the handles of the boards are opened. The FRU is powered off. Alarm on FAN(1) SBL: A special case is the occurrence of this alarm on a FAN(1) SBL. In this case the alarm indicates that a IPMB communication problem has been detected in the ATCA shelf. The FAN(1) SBL has been reused for backward compatibility reasons (patch on previous releases). IPMB communication quality is checked online by the application using a utility that is running on the standby SMM. Every 5 minutes the results of this check are analyzed. If a new problem is detected, then the standby SMM is reset and the test is repeated. If the problem is confirmed, the alarm is raised. Applicability Impact on System 9130 BSC Case 1: Occurrence on SMM SBL: The board is powered off and the SBL is set to FLT. There is no other system impact since the FRU is redundant. Case 2: PEM, Personality Card: No impact. Case 3: FAN(1) SBL: IPMB communication errors are occurring and this may lead to lost resources from platform middleware point of view. Provided the right patch level is applied for this lost resource problem, there should be no operational impact on the BSC. O&M functionality and accuracy may be reduced.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
571 / 778

SMM Impacted FRU is?
FAN
PEM or PC
yes
Single ON/OFF occurrence?
no
Replace SMM
Keep monitoring the BSC yes Is alarm mapped on the same board? no
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes
yes If most boards are impacted is it a shelf issue
Note:
Detailed information can be seen in the Additional Information. The corresponding relation between IPMI address and physical slot is like this:
IPMI Physical Address slot 9A 96 92 8E 8A 86 82 01 02 03 04 05 06 07
IPMI Address 84 88 8C 90 94 98 9C
Physical slot 08 09 10 11 12 13 14
IPMI Address C0 C2 C4 C6 14 16 10
Physical slot 33 34 35 36 29 50 65
IPMI Address 12 C8 CA CC CE
Physical slot 66 81 82 83 84
572 / 778
31.8 [99,11] TEMPERATURE-FATAL

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] TEMPERATURE-FATAL [11] Environmental HeatingOrVentilationOrCoolingSystemProblem Critical (VPMA) Hardware or environmental fatal alarm. Temperature of the unit is over the "critical" threshold. The board is switched off. "critical" threshold: >65 degrees or < -10 degree. Applicability Impact on System 9130 BSC The board is powered off and the impacted SBL is set to FLT. There is no other system impact: shelf managers, fans and PEM are redundant. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
573 / 778

[99, 11] TEMPERATURE FATAL
Fan status is ok?
no
Alarm persists?
no
yes
yes
Alarm solved
no
Alarm persists?
no
yes
yes
Onsite
Replace faulty board
Alarm persists?
no
Alarm solved
574 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] TEMPERATURE-MAJOR [12] Environmental HeatingOrVentilationOrCoolingSystemProblem Major (PMA) Hardware or environmental major alarm. Temperature of the unit is over the "major" threshold. That may impact the functional status. "major" threshold: (60-65 degree) or (-10-0) Applicability Impact on System 9130 BSC The impacted SBL is set to FIT. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
575 / 778

Fan status is ok?
no
Alarm persists?
no
yes
yes
Alarm solved
no
Alarm persists?
no
yes
yes
Onsite
Alarm persists?
no
Alarm solved
576 / 778
31.10 [99,13] TEMPERATURE-MINOR

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] TEMPERATURE-MINOR [13] Environmental HeatingOrVentilationOrCoolingSystemProblem Minor (DMA) Hardware or environmental minor alarm. Temperature of the unit is over the "minor" threshold. The functional status is not impacted. "Minor" threshold: (5560 degree) or (05degree) Applicability Impact on System 9130 BSC The impacted SBL is set to FIT. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
577 / 778

[99, 13] TEMPERATURE MINOR
Fan status is ok?
no
Alarm persists?
no
yes
yes
Alarm solved
no
Alarm persists?
no
yes
yes
Onsite
Alarm persists?
no
Alarm solved
578 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] VOLTAGE-FATAL [14] Equipment PowerProblem Critical (VPMA) Power supply voltage is over "critical" threshold. The functional status is impacted and the board is powered off. Detail threshold are as following: Input Voltage: LoCri=-40.00 or HiCri=-98.00 or Output Voltage: LoCri=-38.80 or HiCri=-96.80 or Output Current: HiCri =54.80 Any one of above thresshold is reached, the alarm will be sent 9130 BSC The board is powered off and the impacted SBL is set to FLT. There is no other system impact: PEM are redundant.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
579 / 778

PEM status is ok?
no
Alarm persists?
no
yes
yes
Alarm solved
no
Alarm persists?
no
yes
yes
Onsite
Alarm persists?
no
Alarm solved
580 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] VOLTAGE-MAJOR [15] Equipment PowerProblem Major (PMA) Power supply voltage is over "major" threshold. The functional status may be impacted.The power status is severely degraded. Detail threshold are as following: Input Voltage: LoMaj=-40.80 or HiMaj=-72.00 or Output Voltage: LoMaj=-40.00 or HiMaj=-70.80 or Output Current: HiMaj =48.80 Any one of above thresshold is reached, the alarm will be sent 9130 BSC The impacted SBL is set to FIT. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

No corrective action is required for this alarm. It is removed from more recent BSC software versions.
581 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] VOLTAGE-MINOR [16] Equipment PowerProblem Minor (DMA) Power supply voltage is over "minor" threshold. The functional status is not impacted. The power status is degraded. Detail threshold are as following: Input Voltage: LoMin=-44.00 or HiMin=-62.00 or Output Voltage: LoMin=-42.80 or HiMin=-60.80 or Output Current: HiMin =44.80 Any one of above thresshold is reached, the alarm will be sent 9130 BSC The impacted SBL is set to FIT. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

No corrective action is required for this alarm. It is removed from more recent BSC software versions.
582 / 778
31.14 [99,17] ETHERNET-LINK-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] ETHERNET-LINK-FAILURE [17] Equipment Indeterminate Indeterminate One of the two Ethernet links of the FRU is down. The board is reset by the BSC application. 9130 BSC The impacted SBL state is not changed. System impacts are due to previous reset event (see ATCA-SHELF [99], RESET [0]).
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
583 / 778

[99, 17] ETHERNET LINK FAILURE
yes
SSW status is ok?
no
Onsite
Replace SSW
Alarm persists?
no
Alarm solved
584 / 778
31.15 [99,18] SHELF-MANAGER-ACCESS-PB

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] SHELF-MANAGER-ACCESS-PB [18] Equipment EquipmentMalfunction Major (PMA) The shelf management board not reachable. Either the board is out of service, or the ethernet link between the board and the OMCP is down. 9130 BSC The impacted SBL is set to FLT. There is no other system impact: the second shelf manager becomes active.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - The shelf management board is not reachable.
585 / 778
31.16 [99,19] FAN-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System ATCA-SHELF [99] FAN-FAILURE [19] Equipment coolingFanFailure Major (PMA) One of the chassiss fan units has failed. The platform is still running. 9130 BSC The impacted SBL is set to FLT. There is no other system impact: other cooling fans increased their speed. There is no other system impact: other cooling fans increase their speed.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[99, 19] FAN FAILURE
Onsite
Replace FAN
Alarm persists?
no
Alarm solved
586 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] FIRMWARE-NOT-UP-TO-DATE [20] Equipment EquipmentMalfunction Minor (DMA) When the board is started, an automatic check of the firmware version is performed. This alarm is reported to OMC-R if it is not the supported version. 9130 BSC The ALARM shows that the current FW version running on FAN, PEM, SMM, PC boards does not fit with the up-to-date FW version. The SBL of impacted FAN, PEM, SMM, PC is set to FIT. There is no other system impact.
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no

[99, 20] FIRMWARENOTUPTODATE
Alarm persists?
no
Alarm solved
yes
587 / 778
31.18 [99,21] IPMI-BUS-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description ATCA-SHELF [99] IPMI-BUS-FAIL [21] Equipment EquipmentMalfunction Minor(DMA) An IPMB communication problem has been detected in the ATCA shelf. IPMB communication quality is checked online by the application using a utility which is running on the standby SMM. Every 5 minutes the results of this check are analyzed. Before raising the alarm, a new problem needs to be confirmed in the next 5 minute test period. Applicability Impact on System 9130 BSC IPMB communication errors are occurring and this may lead to lost resources from platform middleware point of view. Due to SW workarounds since B10MR2, there should be no operational impact on the BSC. O&M functionality and accuracy may be reduced (missing alarms). FW upgrade of IPMI firmware of FRUs may fail due to these IPMI communication problems.
Trunk(s) no no
Cell/BTS(s) no no
Signaling no no
Call Handling no no
588 / 778

[99,21] IPMIBUSFAIL
yes
Single ON / OFF occurrence?
no
Keep monitoring the BSC
no Alarm persists?
Alarm solved
yes
589 / 778
590 / 778
32 Class 100: LIU-SHELF Alarms

This section defines the BSC alarms for the Class 100: LIU-SHELF alarm class.
591 / 778
32.1 [100,0] RESET

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System LIU-SHELF [100] RESET [0] Processing Error SoftwareError Indeterminate The MUX board has reset. 9130 BSC The BSC triggers a MUX takeover.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - The MUX board was reset.
592 / 778
32.2 [100,1] MUX-TAKEOVER

specificProblems eventType probableCause perceivedSeverity Alarm Description LIU-SHELF [100] MUX-TAKEOVER [1] Equipment EquipmentMalfunction Indeterminate MUX board switchover has occurred, there is no impact on telecom traffic. 9130 BSC The impacted SBL state is not changed. There is no system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - MUX board switchover was performed.
593 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description LIU-SHELF [100] ACCESS-FAIL [4] Equipment EquipmentMalfunction Major (PMA) Alarm on LIU board, reported when both MUX boards report a serial link failure. 9130 BSC The impacted SBL state is changed to FLT. All BTS of all Abis managed by the faulty ETU are lost. It is no more possible to have telecom traffic or O&M supervision with these BTS. All Atermux managed by the faulty ETU are lost. On going telecom traffic using these Atermux is stopped. New traffic and signaling will be established by using Atermux managed by another ETU.
Trunk(s) Yes No
Cell/BTS(s) Yes No
Signaling Yes No

[100, 4] ACCESS FAIL
Onsite
Replace LIU board
Alarm persists?
no
Alarm solved
yes
594 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System LIU-SHELF [100] UNPLUGGED [6] Equipment Unavailable Minor (DMA) LIU board is detected as unplugged by the LIU shelf. 9130 BSC The impacted SBL state is changed to FLT. All BTS of all Abis managed by the faulty ETU are lost. It is no more possible to have telecom traffic or O&M supervision with these BTS. All Atermux managed by the faulty ETU are lost. On going telecom traffic using these Atermux is stopped. New traffic and signaling couldwill be established by using Atermux managed by another ETU.
Trunk(s) Yes No
Cell/BTS(s) Yes No
Signaling Yes No

[100, 6] UNPLUGGED
no
Reinsert the board
Alarm persists?
no
Alarm solved
yes
595 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description LIU-SHELF [100] FW-UPGRADE-UNSUCCESS [7] Equipment EquipmentMalfunction Critical (VPMA) The alarm is reported when firmware upgrade is triggered successfully, but it fails to upgrade 9130 BSC If alarm "FIRMWARE_NOT_UTD" is reported before, there is no impact to related SBL. If alarm "FIRMWARE_INCOMP" is reported before, the related SBL will change to FLT.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

Alarm persists?
no
Alarm solved
yes
596 / 778
32.6 [100,8] FW-UPGRADE

specificProblems eventType probableCause perceivedSeverity Alarm Description LIU-SHELF [100] FW-UPGRADE [8] Processing Error UnderlyingResourceUnavailable Minor(DMA) Operator has launched firmware upgrade in the board on this field. All operations on this board(reset) are rejected while this alarm is active. 9130 BSC The impacted SBL is set to FLT.
Trunk(s) YES NO
Cell/BTS(s) YES NO
Signaling YES NO
O&M; Capabilities YES NO

597 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description LIU-SHELF [100] FIRMWARE-INCOMPATIBILITY [9] Equipment EquipmentMalfunction Major (PMA) If the firmware version is not compatible with BSC application, the alarm will be reported. 9130 BSC Two cases: 1) No scenario is ongoing for specific MUX If the related SBL is IT/FIT and the version check messageis received, the related SBL will be changed to FIT. 2) There is scenario ongoing for specific MUX. Typically, MUX startup scenario. If version check message is received, no state change for related SBL. Typically, the state is from MSD/MSA to MSD/MSA.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
598 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description LIU-SHELF [100] FIRMWARE-NOT-UP-TO-DATE [19] Equipment EquipmentMalfunction Minor (DMA) When the board is started, an automatic check of the NE1oE firmware version is performed. This alarm is reported to OMC-R if it is not the supported version. 9130 BSC The ALARM shows that the current NE1oE FW version running on MUX boards does not fit with the up-to-date NE1oE FW version. The SBL of impacted MUX is set to FIT. There is no other system impact.
Trunk(s) NO NO
Cell/BTS(s) NO NO
Signaling NO NO
Call Handling NO NO

Alarm persists?
no
Alarm solved
yes
599 / 778
32.9 [100,20] LIU_SHELF_PEM_OWN_VBAT_LOSS

specificProblems eventType probableCause perceivedSeverity Alarm Description LIU-SHELF [100] LIU_SHELF_PEM_OWN_VBAT_LOSS [20] Equipment EquipmentMalfunction Minor (DMA) The 48 V redundancy from target PEM of E1 shelf has been lost. The functional status is not impacted. 9130 BSC The impacted SBL is set to FIT. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[100, 20] LIU_SHELF_PEM_OWN _VBAT_LOSS
Onsite
Check that 48 V redundancy between the two PEMs of E1 shelf is connected
Alarm cleared?
yes
Alarm solved
no
600 / 778
32.10 [100,21] LIU_SHELF_RED_VBAT_LOSS

specificProblems eventType probableCause perceivedSeverity Alarm Description LIU-SHELF [100] LIU_SHELF_RED_VBAT_LOSS [21] Equipment EquipmentMalfunction Minor (DMA) The 48 V redundancy from Other PEM of E1 shelf has been lost. The functional status is not impacted. 9130 BSC The impacted SBL is set to FIT. There is no other system impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[100, 21] LIU_SHELF _RED_VBAT_LOSS
Onsite
Check that 48 V redundancy between the two PEMs of E1 shelf is connected
Alarm cleared?
yes
Alarm solved
no
601 / 778
32.11 [100,22] PEM_OWN_12V_FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description LIU-SHELF [100] PEM_OWN_12V_FAILURE [22] Equipment EquipmentMalfunction Major (PMA) A failure of the 12VDC output of on Power Entry Module in the LIU shelf has been detected. 9130 BSC The impacted SBL state is set to FLT. There is no other system impact: Power supply redundancy is assured by the other LIU PEM.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[100, 22] PEM_OWN_12V_FAIL
Onsite
Replace PEM
Alarm persists?
no
Alarm solved
yes
602 / 778
32.12 [100,23] TOO_HIGH_TEMPERATURE

specificProblems eventType probableCause perceivedSeverity Alarm Description LIU-SHELF [100] TOO_HIGH_TEMPERATURE [23] Equipment EquipmentMalfunction Minor (DMA) A too high temperature has been detected on the LIU PEM. If the internal temperature in the LIU PEM exceeds 80 degrees celcius, this alarm is raised. As such there is no operational impact on the LIU PEM. The PEM is not shutdown, there is no autonomous defense. However, the LIU shelf should be checked because further temperature increase could damage the FRU Applicability Impact on System 9130 BSC The impacted SBL state is set to FIT. There is no other system impact: power is handled by the other PEM. In case a PEM failure would occur, power supply redundancy is assured by the other LIU PEM.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
603 / 778

[100, 23] TOO_HIGH_TEMP
Environmental conditions are ok?
no
Fix environmental problems
Alarm persists?
no
Alarm solved
yes
yes
Onsite
If alarm is not present the other PEM too, replace faulty PEM
Alarm persists?
no
Alarm solved
604 / 778
32.13 [100,24] PEM_NOT_RESPONDING

specificProblems eventType probableCause perceivedSeverity Alarm Description LIU-SHELF [100] PEM_NOT_RESPONDING [24] Equipment EquipmentMalfunction Major (PMA) The LIU PEM is not responding to O&M queries. Status is unknown. O&M of the LIU PEM is done by the active MUX board through an I2C bus. There is no response of the LIU PEM to queries by the active MUX board. This problem could be due to a communication failure on the internal I2C bus (hardware failure) or the LIU PEM could be removed. If both LIU PEM boards are in fault (PEM_NOT_RESPONDING) then there is likely a hardware problem on the I2C interface of the active MUX board. If the fault is only reported on one PEM board, then the problem is located on that board. Applicability Impact on System 9130 BSC The impacted SBL state is set to FLT. There is no other system impact. In case of a fatal PEM failure or PEM removal, power supply redundancy is assured by the other LIU PEM.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
605 / 778

[100, 24] PEM_NOT_RESPOND
no
Reinsert the board
Alarm persists?
no
Alarm solved
yes
yes
Both LIU PEM show the PEM_NOT_RESPOND alarm?
yes
Trigger MUX takeover
Alarm persists?
no
Replace standby MUX
no
yes
Onsite
Replace faulty PEM
Alarm persists?
no
Alarm solved
606 / 778
32.14 [100,50] NE1OE-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description LIU-SHELF [100] NE1OE-FAILURE [50] Equipment EquipmentMalfunction Major (PMA) MUX board cannot start due to problems in the INIT sequence and is powered off. 9130 BSC The impacted SBL state is changed from IT to FLT. When this problem is detected, the BSC triggers a MUX reset and a MUX takeover. System impacts are due to the MUX reset (see LIU-SHELF [100], RESET [0]).
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
607 / 778

[100, 50] NE1OE FAILURE
yes SSW alarms present? Solve SSW alarms
Alarm persists?
no
no
yes
Alarm solved
Ethernet cable no between ATCA shelf and LIU shelf is ok?
Replace Ethernet cable
Alarm persists?
no
yes
Onsite
yes
Replace MUX
Alarm persists?
no
Alarm solved
608 / 778
32.15 [100,51] E1-SL-FAILURE

specificProblems eventType probableCause perceivedSeverity Alarm Description LIU-SHELF [100] E1-SL-FAILURE [51] Equipment EquipmentMalfunction Major (PMA) The 16E1 serial link between the MUX and this LIU board has failed. This failure concerns only one of the MUX, so it is not the LIU board failure. 9130 BSC The impacted SBL state is not changed. When this problem is detected, the BSC triggers a MUX reset and a MUX takeover. There is no system impact: the traffic uses the other E1 serial link between the MUX and the LIU board.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
609 / 778

[100, 51] E1 SL FAILURE
Onsite
Replace LIU board
Alarm persists?
no
Alarm solved
yes
Onsite
Replace MUX
Alarm persists?
no
Alarm solved
610 / 778
33 Class 101: BSC-TRANS Alarms

This section defines the BSC alarms for the Class 101: BSC-TRANS alarm class.
611 / 778
33.1 [101,0] LIS

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] LIS [0] Communication LossOfSignal Major (PMA) Loss of Incoming Signal (LIS) is detected on a given E1 link. 9130 BSC The impacted SBL is set to FLT. For ABIS-HWAY-TP, the link between the BSC and all BTS of the Abis is lost. It is no more possible to have telecom traffic or O&M supervision with these BTS. For ATER-HWAY-TP, the link between the BSC and the MFS or the TC is lost. On going telecom traffic using this ATER-HWAY-TP is stopped. New traffic and signaling will be established by using the other ATER-HWAY-TP.
Trunk(s) Yes (if Ater) No
Cell/BTS(s) Yes (if Abis) No
Signaling Yes (if Abis) Yes (if Ater)
Call Handling Yes (if Abis) Yes (if Ater)
O&M; Capabilities Yes (if Abis) No
612 / 778

[101, 0] LIS
Related TP, MUX or LIU alarms are present? no
yes
Solve these alarms
Alarm persists?
no
yes
Related BTS/TC alarms are present?
yes Solve these alarms
Alarm persists?
no
Alarm solved
no Check related SBL (N7, OML, RSL, GSL, MLPPP)
yes
SBL in fault?
no
Inhibit / allow alarm reporting
Alarm persists?
no
yes
yes
Loop back BSC originated E1 link at BSC site.
Alarm persists?
no
Loop back originated E1 link at BTS / TC site
Alarm persists?
yes
No BSS problem; Check E1 link with line provider
yes
no Check BTS / TC local cabling
no Local cabling ok?
Solve cabling problem
Alarm persists?
no
Alarm solved
yes
yes
613 / 778
33.2 [101,1] AIS

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-TRANS [101] AIS [1] Communication Ais Minor (DMA) Alarm Indication Signal (AIS) is detected on a given E1 link. In addition to the above G2BSC case, a new case in MX is : AIS END alarm is used to clear all active alarms in BSC AIFL when E1 alarm disappears on this E1 link, this AIS END alarm will be converted into event alarm which is reproted to OMC. 9130 BSC The impacted SBL is set to FLT. For ABIS-HWAY-TP, the link between the BSC and all BTS of the Abis is lost. It is no more possible to have telecom traffic or O&M supervision with these BTS. For ATER-HWAY-TP, the link between the BSC and the MFS or the TC is lost. On going telecom traffic using this ATER-HWAY-TP is stopped. New traffic and signaling will be established by using the other ATER-HWAY-TP.
614 / 778

[101, 1] AIS
yes
Solve these alarms
Alarm persists?
no
yes
Alarm persists?
no
Alarm solved
yes
SBL in fault?
no
Alarm persists?
no
yes
yes
Alarm persists?
no
Alarm persists?
yes
yes
Alarm persists?
no
Alarm solved
yes
yes
615 / 778
33.3 [101,2] LFA

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] LFA [2] Communication LossOfFrame Major (PMA) Loss of Frame Alignment (LFA) is detected on a given E1 link. 9130 BSC The impacted SBL is set to FLT. For ABIS-HWAY-TP, the link between the BSC and all BTS of the Abis is lost. It is no more possible to have telecom traffic or O&M supervision with these BTS. For ATER-HWAY-TP, the link between the BSC and the MFS or the TC is lost. On going telecom traffic using this ATER-HWAY-TP is stopped. New traffic and signaling will be established by using the other ATER-HWAY-TP.
616 / 778

[101, 2] LFA
yes
Solve these alarms
Alarm persists?
no
yes
Alarm persists?
no
Alarm solved
yes
SBL in fault?
no
Alarm persists?
no
yes
yes
Alarm persists?
no
Alarm persists?
yes
yes
Alarm persists?
no
Alarm solved
yes
yes
617 / 778
33.4 [101,4] BER-10E-3

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] BER-10E-3 [4] Communication DegradedSignal Major (PMA) Bit Error Rate of 10E-3 (BER 10-3) is detected on a given E1 link. 9130 BSC The impacted SBL is set to FLT. For ABIS-HWAY-TP, the link between the BSC and all BTS of the Abis is lost. It is no more possible to have telecom traffic or O&M supervision with these BTS. For ATER-HWAY-TP, the link between the BSC and the MFS or the TC is lost. On going telecom traffic using this ATER-HWAY-TP is stopped. New traffic and signaling will be established by using the other ATER-HWAY-TP.
618 / 778

[101, 4] BER 10E3
yes
Solve these alarms
Alarm persists?
no
yes
Alarm persists?
no
Alarm solved
yes
SBL in fault?
no
Alarm persists?
no
yes
yes
Alarm persists?
no
Alarm persists?
yes
yes
Alarm persists?
no
Alarm solved
yes
yes
619 / 778
33.5 [101,5] RAI

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] RAI [5] Communication FarEndReceiverFailure Minor (DMA) Remote Alarm Indication (RAI) is detected on a given E1 link. 9130 BSC The impacted SBL is set to FLT. For ABIS-HWAY-TP, the link between the BSC and all BTS of the Abis is lost. It is no more possible to have telecom traffic or O&M supervision with these BTS. For ATER-HWAY-TP, the link between the BSC and the MFS or the TC is lost. On going telecom traffic using this ATER-HWAY-TP is stopped. New traffic and signaling will be established by using the other ATER-HWAY-TP.
620 / 778

[101, 5] RAI
yes
Solve these alarms
Alarm persists?
no
yes
Alarm persists?
no
Alarm solved
yes
SBL in fault?
no
Alarm persists?
no
yes
yes
Alarm persists?
no
Alarm persists?
yes
yes
Alarm persists?
no
Alarm solved
yes
yes
621 / 778
33.6 [101,6] BER-10E-4

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] BER-10E-4 [6] Communication DegradedSignal Minor (DMA) Bit Error Rate of 10E-4 (BER 10-4) is detected on a given E1 link. 9130 BSC There is a small degradation of the speech and packet quality and few frame repetitions on Telecom or O&M signaling links.
Trunk(s) No Yes
Cell/BTS(s) No Yes
Signaling No Yes
622 / 778

[101, 6] BER 10E4
yes
Solve these alarms
Alarm persists?
no
yes
Alarm persists?
no
Alarm solved
yes
SBL in fault?
no
Alarm persists?
no
yes
yes
Alarm persists?
no
Alarm persists?
yes
yes
Alarm persists?
no
Alarm solved
yes
yes
623 / 778
33.7 [101,7] BER-10E-6

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] BER-10E-6 [7] Communication DegradedSignal Minor (DMA) Bit Error Rate of 10E-6 (BER 10-6) is detected on a given E1 link. 9130 BSC There is a small degradation of the speech and packet quality and few frame repetitions on Telecom or O&M signaling links.
Trunk(s) No Yes
Cell/BTS(s) No Yes
Signaling No Yes
624 / 778

[101, 7] BER 10E6
yes
Solve these alarms
Alarm persists?
no
yes
Alarm persists?
no
Alarm solved
yes
SBL in fault?
no
Alarm persists?
no
yes
yes
Alarm persists?
no
Alarm persists?
yes
yes
Alarm persists?
no
Alarm solved
yes
yes
625 / 778
33.8 [101,8] FRAME-SLIP

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-TRANS [101] FRAME-SLIP [8] Communication LossOfFrame Indeterminate This event is notified when the BSC detects at least one E1 (not locked) with frame slips. E1 is considered with frame slip if the number of frame slips monitored during the previous 15 minutes exceeds the threshold SLIP-COUNTER-THRESHOLD. 9130 BSC There is a small degradation of the speech quality and few frame repetitions on Telecom or O&M signaling links.
Trunk(s) No Yes
Cell/BTS(s) No Yes
Signaling No Yes
626 / 778

[101, 8] FRAME SLIP
yes
Solve these alarms
Alarm persists?
no
yes
Alarm persists?
no
Alarm solved
yes
SBL in fault?
no
Alarm persists?
no
yes
yes
Alarm persists?
no
Alarm persists?
yes
yes
Alarm persists?
no
Alarm solved
yes
yes
627 / 778
33.9 [101,9] PPP-LNK-LOOP

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] PPP-LNK-LOOP [9] Communication transmitFailure Major (DMA) Link looped-back 9130 BSC The impacted SBL is set to FLT.
Signaling Yes (if Abis) No
628 / 778

101, 9] PPPLINKLOOP
If TP, MUX or LIU board alarms are present, solve it
Alarm persists?
no
yes
Check local cabling
Alarm persists?
no
Alarm solved
yes Trigger remote signal path and transmitter test on MSC side
Alarm persists?
no
yes
629 / 778
33.10 [101,10] PPP-NO-HDLC

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] PPP-NO-HDLC [10] Communication transmitFailure Major (DMA) No HDLC for PPP link 9130 BSC The impacted SBL is set to FLT.

[101, 10] PPPNOHDLC
E1 link connection at Abis or Ater ok?
no
Fix E1 link connection at Abis or Ater
no Alarm persists?
yes
Alarm solved
Alarm persists?
no
yes
yes
630 / 778
33.11 [101,11] PPP-NO-LCP-REP

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] PPP-NO-LCP-REP [11] Communication transmitFailure Major (DMA) Non receipt of LCP Echo-Reply 9130 BSC The impacted SBL is set to FLT.
Trunk(s) No No
Call Handling Yes (if Abis) No

[101, 11] PPPNOLCPREP
no
no Alarm persists?
yes
Alarm solved
Alarm persists?
no
yes
yes
631 / 778
33.12 [101,12] PPP-CONF-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] PPP-CONF-FAIL [12] Communication transmitFailure Major (DMA) LCP configuration option negotiation failure 9130 BSC The impacted SBL is set to FLT.
Trunk(s) No No

[101, 12] PPPCONFFAIL
no
no Alarm persists?
yes
Alarm solved
Alarm persists?
no
yes
yes
632 / 778
33.13 [101,13] PPP-HIGH-ERR

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-TRANS [101] PPP-HIGH-ERR [13] Communication transmitFailure Major (DMA) This alarm can only happen when IP over E1 is configured and it is raised for 3 reasons: - the quality of the PCM is very poor and therefore the ratio of bad frames is very high, - the connected equipment (BTS) is not configured as the BSC, - there are cross connects between BSC and BTS. 9130 BSC The impacted SBL is set to FLT.
Trunk(s) No No
633 / 778

[101, 13] PPPHIGHERR
Check E1 link connection at Abis or Ater
Alarm persists?
no
yes
Trigger manually the OML mode, via the command: reset Abis_Hway_TP of the concerned Abis
Alarm solved
Alarm persists?
no
yes
634 / 778
33.14 [101,14] OML-MODE

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-TRANS [101] OML-MODE [14] Communication transmitFailure Major(PMA) Indicate the related Abis_Hway_TP is in OML mode. The OML mode is meaningful in the context of an E1 configured with the IP (framed or unframed) transport mode. The purpose of this mode is to come back to transitional TDM transport mode on this E1, only for the OML exchange and not for traffic, assuming that this TDM configuration is possible for any BTS whatever its Software and its configuration. The OML mode is consecutive to a transmission problem with at least one BTS in the chain. Normally, the system can automatically come out of the OML mode 9130 BSC The concerned BTS are out of service during the OML mode.
Trunk(s) no no
Cell/BTS(s) yes no
Signaling no no
Call Handling no no
635 / 778

[101,14] OMLMODE
no
The system automatically comes out of the OML mode?
yes
Check the configuration, version of BTS
Alarm persists?
no
Alarm solved
yes
636 / 778
33.15 [101,20] SFP-UNEQ

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] SFP-UNEQ [20] Communication LocalNodeTransmissionError Minor (DMA) small form-factor pluggable not 9130 BSC The impacted SBL is set to FLT.
Trunk(s) No No

[101, 20] SFPUNEQ
BSC equipped with SFP module? no
yes
Check if the SFP module is correct installed
Alarm persists?
no
Insert SFP module
Alarm solved Alarm persists? yes Contact System Support yes
no
637 / 778
33.16 [101,21] LOS

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] LOS [21] Equipment lossOfSignal Minor (DMA) Section Loss of Signal 9130 BSC The impacted SBL is set to FLT.
Trunk(s) No No
Cell/BTS(s) Yes IF abis No
Signaling Yes if Abis No
O&M; Capabilities Yes if Abis No
638 / 778

[101, 21] LOS
Remote equipment ok?
no
Fix the remote equipment problems
Alarm persists?
no
yes
yes
Alarm solved
Link to remote equipment ok?
no Fix the link Alarm persists?
no
yes
yes
Alarm persists?
no
yes
639 / 778
33.17 [101,22] LOF

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] LOF [22] Equipment lossOfFrame Minor (DMA) Section Loss of Frame 9130 BSC The impacted SBL is set to FLT.
Trunk(s) No No
640 / 778

[101, 22] LOF
no
Alarm persists?
no
yes
yes
Alarm solved
Configuration setting ok?
no Update configuration setting Alarm persists?
no
yes
yes
Alarm persists?
no
yes
641 / 778
33.18 [101,23] MS-AIS

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] MS-AIS [23] Equipment aIS Minor (DMA) Multiplex Section Alarm Indication Signal 9130 BSC The impacted SBL is set to FLT.
Trunk(s) No No

[101, 23] MSAIS
no
Alarm persists?
no
yes
yes
Alarm persists?
yes
Alarm solved
no
642 / 778
33.19 [101,24] MS-RDI

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] MS-RDI [24] Equipment remoteNodeTransmissionError Minor (DMA) Multiplex Section Remote Defect Indication 9130 BSC The impacted SBL is set to FLT.
Trunk(s) No No

[101, 24] MSRDI
no
Alarm persists?
no
yes
yes
Alarm persists?
yes
Alarm solved
no
643 / 778
33.20 [101,25] MS-BER-6

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] MS-BER-6 [25] Equipment degradedSignal Minor (DMA) Multiplex Section Bit Error Rate 10-6 9130 BSC The impacted SBL is set to FIT.
Trunk(s) No No

[101, 25] MSBER6
no
Alarm persists?
no
yes
yes
Alarm persists?
yes
Alarm solved
no
644 / 778
33.21 [101,26] MS-BER-3

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] MS-BER-3 [26] Equipment degradedSignal Minor (DMA) Multiplex Section Bit Error Rate 10-3 9130 BSC The impacted SBL is set to FLT.
Trunk(s) No No
645 / 778

[101, 26] MSBER3
no
Alarm persists?
no
yes
yes
Alarm solved
Link to remote equipment ok?
no Fix the link Alarm persists?
no
yes
yes
Alarm persists?
no
yes
646 / 778
33.22 [101,28] SFP-NOT-SUP

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] SFP-NOT-SUP [28] Equipment EquipmentMalfunction Minor (DMA) Small Form-Factor Pluggable not supported 9130 BSC No state impact
Trunk(s) No No

[101, 28] SFPNOTSUP
The SFP module is installed?
yes
Check if the SFP module is correct installed
Alarm persists?
no
no
Insert SFP module
Alarm solved Alarm persists? yes Contact System Support yes
no
647 / 778
33.23 [101,31] AU-LOP

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] AU-LOP [31] Equipment lossOfPointer Minor (DMA) Administrative Unit 4 Loss of Pointer 9130 BSC The impacted SBL is set to FLT
Trunk(s) No No
648 / 778

[101, 31] AULOP
no
Alarm persists?
no
yes
yes
Alarm solved
no
yes
yes
Alarm persists?
no
yes
649 / 778
33.24 [101,32] AU-AIS

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] AU-AIS [32] Equipment aIS Minor (DMA) Administrative Unit 4 Alarm Indication Signal 9130 BSC The impacted SBL is set to FLT
Trunk(s) No No

[101, 32] AUAIS
no
Alarm persists?
no
yes
yes
Alarm persists?
yes
Alarm solved
no
650 / 778
33.25 [101,41] HP-UNEQ

specificProblems eventType probableCause perceivedSeverity Alarm Description BSC-TRANS [101] HP-UNEQ [41] Equipment EquipmentMalfunction Minor (DMA) High Order Path Unequipped: The HOP is not configured on the remote entity 9130 BSC The impacted SBL is set to FLT .The STM1 interace is faulty
Trunk(s) No No

[101, 41] HPUNEQ
Check the remote STM1 declaration and correct it if needed.
Alarm persists?
no
Alarm solved
yes
651 / 778
33.26 [101,42] HP-PLM

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] HP-PLM [42] Equipment payloadTypeMismatch Minor (DMA) High Order Path Payload Label Mismatch 9130 BSC The impacted SBL is set to FLT .
Trunk(s) No No
652 / 778

[101, 42] HPPLM
no
Alarm persists?
no
yes
yes
Alarm solved
no
yes
yes
Alarm persists?
no
yes
653 / 778
33.27 [101,43] HP-RDI

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] HP-RDI [43] Equipment remoteNodeTransmissionError Minor (DMA) High Order Path Remote Defect Indication 9130 BSC The impacted SBL is set to FLT .
Trunk(s) No No

[101, 43] HPRDI
no
Alarm persists?
no
yes
yes
Alarm persists?
yes
Alarm solved
no
654 / 778
33.28 [101,44] HP-LOM

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] HP-LOM [44] Equipment lossOfFrame Major (DMA) High Order Path Loss of Multiframe 9130 BSC The impacted SBL is set to FLT .
Trunk(s) No No
655 / 778

[101, 44] HPLOM
no
Alarm persists?
no
yes
yes
Alarm solved
no
yes
yes
Alarm persists?
no
yes
656 / 778
33.29 [101,51] TU-LOP

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] TU-LOP [51] Equipment lossOfPointer Major (DMA) Tributary Unit 12 Loss of Pointer 9130 BSC The impacted SBL is set to FLT .
Trunk(s) No No
Cell/BTS(s) Yes if Abis No
Call Handling Yes if abis No
657 / 778

[101, 51] TULOP
no
Alarm persists?
no
yes
yes
Alarm solved
no
yes
yes
Alarm persists?
no
yes
658 / 778
33.30 [101,52] TU-AIS

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] TU-AIS [52] Equipment aIS Major (DMA) Tributary Unit 12 Alarm Indication Signal 9130 BSC The impacted SBL is set to FLT .
Trunk(s) No No

[101, 52] TUAIS
no
Alarm persists?
no
yes
yes
Alarm persists?
yes
Alarm solved
no
659 / 778
33.31 [101,55] LP-UNEQ

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] LP-UNEQ [55] Equipment EquipmentMalfunction Major (DMA) Low Path Unequipped 9130 BSC The impacted SBL is set to FLT .
Trunk(s) No No
660 / 778

[101, 55] LPUNEQ
no
Alarm persists?
no
yes
yes
Alarm solved
no
yes
yes
Alarm persists?
no
yes
661 / 778
33.32 [101,56] LP-PLM

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] LP-PLM [56] Equipment payloadTypeMismatch Major (DMA) Low Path Payload Label Mismatch 9130 BSC The impacted SBL is set to FLT .
Trunk(s) No No
662 / 778

[101, 56] LPPLM
no
Alarm persists?
no
yes
yes
Alarm solved
no
yes
yes
Alarm persists?
no
yes
663 / 778
33.33 [101,57] LP-RDI

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] LP-RDI [57] Equipment remoteNodeTransmissionError Major (DMA) Low Path Remote Defect Indication 9130 BSC The impacted SBL is set to FLT .
Trunk(s) No No

[101, 57] LPRDI
no
Alarm persists?
no
yes
yes
Alarm persists?
yes
Alarm solved
no
664 / 778
33.34 [101,60] PPP-CROSS-CON

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] PPP-CROSS-CON [60] Communication transmitFailure Major (DMA) MLPPP cross connected 9130 BSC The impacted SBL is set to FLT .
Trunk(s) No No

[101, 60] PPPCROSSCON
PPP connection is crossconnected?
yes Fix the PPP connection Alarm persists?
no
no
yes
Alarm persists?
yes
Alarm solved
no
665 / 778
33.35 [101,61] PPP-LCP-TER

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] PPP-LCP-TER [61] Communication transmitFailure Major (DMA) On LCP terminate REQ 9130 BSC The impacted SBL is set to FLT .
Trunk(s) No No

[101, 61] PPPLCPTER
PPP configuration ok?
no
Correct PPP configuration
Alarm persists?
no
yes
yes
Alarm persists?
yes
Alarm solved
no
666 / 778
33.36 [101,62] PPP-LOW-ERR

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] PPP-LOW-ERR [62] Communication transmitFailure Minor (DMA) Low erroneous PPP frame 9130 BSC The impacted SBL is set to FIT .
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[101, 62] PPPLOWERR
PPP link status ok? yes
no Fix PPP link
Alarm persists?
no
yes
Alarm persists?
yes
Alarm solved
no
667 / 778
33.37 [101,63] PPP-MED-ERR

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] PPP-MED-ERR [63] Communication transmitFailure Major (DMA) Low erroneous PPP frame 9130 BSC The impacted SBL is set to FLT .
Trunk(s) No No
Call Handling yes No

[101, 63] PPPMEDERR
PPP link status ok? yes
no Fix PPP link
Alarm persists?
no
yes
Alarm persists?
yes
Alarm solved
no
668 / 778
33.38 [101,100] STM1-TAKEOVER

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System BSC-TRANS [101] STM1-TAKEOVER [100] Processing Error SoftwareProgramAbnormallyTerminated Minor (DMA) This alarm indicates a STM1-TTP takeover 9130 BSC No impact
Trunk(s) No No
Cell/BTS(s) no No
Signaling No No
Call Handling No No

None- No action needed.
669 / 778
670 / 778
34 Class 104: TC-OM Alarms

This section defines the BSC alarms for the Class 104: TC-OM alarm class.
671 / 778
34.1 [104,0] TC-INIT-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description TC-OM [104] TC-INIT-FAIL [0] Processing Error EquipmentMalfunction TC initialization is unsucc: maybe TC-HW-Audit, or TC-conf-req or TC-Alarm audit failed. 9130 BSC No impact.
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling Yes No

[104, 0] TCINITFAIL
If TCOM is FOS, init TCOM from TC NEM or OMCR
Alarm persists?
no
Alarm solved
yes
672 / 778
34.2 [104,1] TC-INIT-SUCC

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability Impact on System TC-OM [104] TC-INIT-SUCC [1] Processing Error congestion/network fail TC initialization is succ. 9130 BSC No impact.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None. The TC initialization is successful.
673 / 778
674 / 778
35 Class 105: TRANSCODER Alarms

This section defines the BSC alarms for the Class 105: TRANSCODER alarm class.
675 / 778
35.1 [105,0] POWER-SUPPLY

specificProblems eventType probableCause perceivedSeverity Alarm Description Applicability TRANSCODER [105] POWER-SUPPLY [0] Equipment TimingProblem Minor (DMA) One of both MT120 power supply is in fault 9130 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

[105, 0] POWERSUPPLY
Check MT120 Power Supply
Alarm persists?
no
Alarm solved
yes
676 / 778

specificProblems eventType probableCause perceivedSeverity Alarm Description TRANSCODER [105] EQUIPMENT-FAULT [128] Equipment EquipmentMalfunction Major (PMA) There is a basic operational malfunction. An internal fault has been detected on a board. 9130 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Impact Loss
Trunk(s) Yes (if TRAU-CP= FLT) Yes (if TRAU-CP = FIT)
Cell/BTS(s) No
Signaling Yes (if TRAU-CP = FLT) Yes (if TRAU-CP = FIT)
Call Handling Yes (if TRAU-CP = FLT) Yes (if TRAU-CP = FIT )
Degradation
No
No
677 / 778

[105,128] EQUIPMENTFAULT
Reset corresponding MT120 board.
Alarm persists?
no
yes
9125 TC
Replace corresponding MT120 board.
Replace corresponding MT120 board.
Alarm solved
Alarm persists?
no
yes
678 / 778
35.3 [105,130] DSP LOSS

specificProblems eventType probableCause perceivedSeverity Alarm Description TRANSCODER [105] DSP LOSS [130] Processing Error CorruptData Major (PMA) For MT120: more than one DSP has failed and the impact is only the loss of a number of channels, that is only trunk degradation. Signalling is not lost neither. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No Yes(for MT120)
Cell/BTS(s) No No
Signaling No No
Call Handling No No
679 / 778

[105,130] DSPLOSS
BIU alarm events?
G2 TC
no
9125 TC
Lock SMADAPT/ TCADAPT Reset MT120 Unlock SMADAPT/ TCADAPT
Alarm persists?
no
Alarm solved
no
Alarm persists?
Onsite
yes
Onsite
yes
Replace BIU
Replace MT120
Replace MT120
Alarm persists?
no
Alarm solved
no
Alarm persists?
yes Contact System Support Contact System Support
680 / 778
35.4 [105,136] FIRST-DSP-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description TRANSCODER [105] FIRST-DSP-FAIL [136] Equipment EquipmentMalfunction 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. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
681 / 778

[105,136] FIRST DSPFAIL
Reset MT120
Alarm persists?
no
Alarm solved
yes
G2 TC
9125 TC G2 TC or 9125 TC?
Replace MT120
Replace MT120
Alarm persists?
no
Alarm solved
yes
682 / 778
35.5 [105,148] RESET

specificProblems eventType probableCause perceivedSeverity Alarm Description TRANSCODER [105] RESET [148] Processing Error SoftwareError Indeterminate An autonomous load of the TC MT120 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. This cannot happen as this module has only firmware. G2 TC and 9125 TC Some calls may be lost
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None - this alarm reports the autonomous load of the BTS_ADAPT only.
683 / 778
35.6 [105,210] TRANS-FLT

specificProblems eventType probableCause perceivedSeverity Alarm Description TRANSCODER [105] TRANS-FLT [210] Communication DegradedSignal Indeterminate 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. 9130 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
684 / 778

[105,210] ATER TRANSFLT
Other Ater alarm events?
no
yes PCM/ATER alarm events? Solve that alarm(s) first
no
yes
Ater interface alarm events?
yes
Alarm persists?
no
no
Ater interface operational?
yes
Onsite no Local Ater cabling OK?
Repair/replace Ater interface
yes
Alarm persists?
no
Alarm solved
685 / 778
35.7 [105,211] LOSS-OF-CLK-2M

specificProblems eventType probableCause perceivedSeverity Alarm Description TRANSCODER [105] LOSS-OF-CLK-2M [211] Equipment TimingProblem Minor (DMA) The 2 MHz clock source is lost. Once the PAD detects the loss of the 2MHz clock source, the next clock source will be selected if available. The firmware will detect the missing clock source number. 9130 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling Yes No
686 / 778
35.8 [105,216] RESTART

specificProblems eventType probableCause perceivedSeverity Alarm Description TRANSCODER [105] RESTART [216] Processing Error SoftwareError Indeterminate n autonomous processor restart has occurred. The operating system and all processes are re-initialized sequentially. A new initialization of the dynamic data takes place. G2 TC and 9125 TC See Consequences of an SBL State Change.
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No

None. This alarm reports an autonomous restart.
687 / 778
35.9 [105,238] ACTIVE-HSI-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description TRANSCODER [105] ACTIVE-HSI-FAIL [238] Equipment TimingProblem Minor (DMA) HSI with active TCIF failed, or HSI with both active and standby TCIF failed. No telecom function. 9130 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) Yes No
Cell/BTS(s) No No
Signaling Yes No
688 / 778

[105,238] ACTIVEHSIFAIL
Check the HSI cable. If both link failed replace the corresponding cable
no Alarm persists?
yes
Restart TCIF and MT120 boards
Alarm solved
Alarm persists?
no
yes
689 / 778
35.10 [105,239] REDUNDANT-HSI-FAIL

specificProblems eventType probableCause perceivedSeverity Alarm Description TRANSCODER [105] REDUNDANT-HSI-FAIL [239] Equipment TimingProblem Minor (DMA) HSI with standby TCIF failed. No impact on O&M or Telecom. Risk for telecom loss if TCIF takeover. 9130 BSC G2 TC and 9125 TC Impact on System See Consequences of an SBL State Change.
Applicability
Trunk(s) No No
Cell/BTS(s) No No
Signaling No No
Call Handling No No
690 / 778

[105,239] REDUNDANTHSIFAIL
Check the HSI cable.
no Alarm persists?
yes
Restart TCIF and MT120 boards
Alarm solved
Alarm persists?
no
yes
691 / 778
692 / 778
36 BSC/TC Alarm Additional Information

This section describes the additional information supplied by some BSC/TC alarms.
693 / 778
36.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 7. 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 5: Additional Information for Restart and Software Anomaly Alarms
694 / 778
36.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.
695 / 778
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.
696 / 778
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.
697 / 778
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.
698 / 778
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 9120 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
699 / 778
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.
700 / 778
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 9120 BSC. Loader module for Evolium 9120 BSC. System init module. PreLoader module.
701 / 778
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
702 / 778
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
703 / 778
Dec 258 259
Hex 102 103
FMM-ID ME_HSK_ABIS CF_INTERPRETER_2
Meaning HSK ABIS module. Command file interpreter module 2.
Table 6: FMM-IDs in Bytes 4 and 5 for Restart Alarms
36.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
704 / 778
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
705 / 778
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
706 / 778
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
707 / 778
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
708 / 778
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 7: Error Types in Bytes 10 and 11 for Restart Alarms
709 / 778
36.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 8: Additional Information for Reset and Software Anomaly Alarms
710 / 778
36.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 9: System Support Machine
36.4 Other BSC Alarms

This section describes the additional information provided by other BSC alarms.
36.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 10: Additional Information for Alarm [33,3] Meaning FF CE identity 0 FF
See BSC/TC Alarm Additional Information (Section 36).
36.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 11: Additional Information for Alarms [34,0] to [34,2] and [34,4] to [34,6]
711 / 778
36.4.3 [34,3]
The additional information bytes for this alarm are defined in Tables 12 to 15, 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 13. Test fault type. See Table 14. -
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 15. Test Result of TDM connection between port 1 and the port given in Raw Data (3). See Table 15. Test Result of TDM connection between port 2 and the port given in Raw Data (3). See Table 15. Test Result of TDM connection between port 3 and the port given in Raw Data (3). See Table 15. Test Result of TDM connection between port 4 and the port given in Raw Data (3). See Table 15. Test Result of TDM connection between port 5 and the port given in Raw Data (3). See Table 15. Test Result of TDM connection between port 6 and the port given in Raw Data (3). See Table 15. Test Result of TDM connection between port 7 and the port given in Raw Data (3). See Table 15. Test Result of TDM connection between port 8 and the port given in Raw Data (3). See Table 15.
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)
712 / 778
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 15. Test Result of TDM connection between port A and the port given in Raw Data (3). See Table 15.
16
Test-raw-data (14)
Table 12: 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 15. Test Result of TDM connection between port C and the port given in Raw Data (3). See Table 15. Test Result of TDM connection between port D and the port given in Raw Data (3). See Table 15. Test Result of TDM connection between port E and the port given in Raw Data (3). See Table 15. Test Result of TDM connection between port F and the port given in Raw Data (3). See Table 15.
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.
713 / 778
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 13: Test Segment Results for Alarm [34,3], [51,1] (Byte 0) and [51,2] (One Byte Only)
714 / 778
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.
715 / 778
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
716 / 778
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.
717 / 778
Fault Type 77 78
Description BCU fail bit set. No system test allowed according an R_xx.
Table 14: 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 15: TDM Connection Test Results (Bytes 6 to 21) for Alarm [34,3]
36.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.
718 / 778
36.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 17: Additional Information for Alarm [35,0]
719 / 778
36.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.
36.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 19. Alarm layout 2 occurs on every alarm event. The additional information bytes for alarm layout 2 are defined in Table 20. Table 21 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).
720 / 778
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 19: 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 20: 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 21: Example of Additional Information for Alarm [35,3] * SLTM = Signaling Link Test Message
721 / 778
36.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.
36.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.
36.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 23: Additional Information for Alarm [36,14]
36.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 24: Additional Information for Alarm [36,15]
722 / 778
36.4.12 [38,0]
The additional information byte for this alarm is defined in below. Byte Number 0 Meaning Display of the modem signals.
36.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.
36.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 27: Additional information for Alarm [42,3]
723 / 778
36.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 :
724 / 778
Byte Number 4N-3 to 4N-2 4N-1 to 4N
Meaning LAC. Cell Id. #FF if not defined. #FF if not defined.
36.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.
725 / 778
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 29: Additional Information for Alarm [42,6]
726 / 778
36.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 (%)
36.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
727 / 778
36.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.
728 / 778
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
36.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
729 / 778
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 33: Additional Information for Alarms [43,0] to [43,3]
730 / 778
36.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.
731 / 778
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
36.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 35: Additional Information for Alarms [44,0], [44,5] and [44,6]
732 / 778
36.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).
36.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 37: Additional Information for Alarms [46, 0], [46,1] and [46,3]
36.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.
733 / 778
36.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.
36.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).
734 / 778
36.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 41: Additional Information for Alarms [49,2] and [49,3]
36.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 42: Additional Information for Alarm [51,0]
735 / 778
36.4.30 [51,1]
The additional information bytes for this alarm are defined in Tables 43, 44, 45 and 46. 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 49 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 43: 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.
736 / 778
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 13. See Test-Fault-Type Table 14. See Table 45 for TDM Test Result Byte descriptions.
Table 44: 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 46 for detailed TDM test results. Test Result of TDM connection between port 1 and the port given by the Link Network Address. See Table 46 for detailed TDM test results. Test Result of TDM connection between port 2 and the port given by the Link Network Address. See Table 46 for detailed TDM test results. Test Result of TDM connection between port 3 and the port given by the Link Network Address. See Table 46 for detailed TDM test results. Test Result of TDM connection between port 4 and the port given by the Link Network Address. See Table 46 for detailed TDM test results. Test Result of TDM connection between port 5 and the port given by the Link Network Address. See Table 46 for detailed TDM test results. Test Result of TDM connection between port 6 and the port given by the Link Network Address. See Table 46 for detailed TDM test results. Test Result of TDM connection between port 7 and the port given by the Link Network Address. See Table 46 for detailed TDM test results. Test Result of TDM connection between port 8 and the port given by the Link Network Address. See Table 46 for detailed TDM test results. Test Result of TDM connection between port 9 and the port given by the Link Network Address. See Table 46 for detailed TDM test results. Test Result of TDM connection between port A and the port given by the Link Network Address. See Table 46 for detailed TDM test results. Test Result of TDM connection between port B and the port given by the Link Network Address. See Table 46 for detailed TDM test results.
10
11
12
13
14
15
737 / 778
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 46 for detailed TDM test results. Test Result of TDM connection between port D and the port given by the Link Network Address. See Table 46 for detailed TDM test results. Test Result of TDM connection between port E and the port given by the Link Network Address. See Table 46 for detailed TDM test results. Test Result of TDM connection between port F and the port given by the Link Network Address. See Table 46 for detailed TDM test results.
17
18
19
Table 45: 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 46: 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 49 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.
738 / 778
36.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 13. See Table 14. For relation of Switch Network Address to board, see Table 49. Associated port is under test. For TDM Test Result Byte description, see Table 45. Table 47: 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 48: 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 49 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.
739 / 778
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
740 / 778
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
741 / 778
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
742 / 778
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
743 / 778
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
744 / 778
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
745 / 778
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
746 / 778
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
747 / 778
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
748 / 778
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
749 / 778
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
750 / 778
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
751 / 778
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 49: Relationship IAD/NA to RIT and Position
752 / 778
36.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 50: 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.
753 / 778
36.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 51: Additional Information for Alarms [52,1], [52,5] and [52,7]
36.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 52: Additional Information for Alarms [53,0], [53,1], [53,3], [53,4], [53,6] and [53,7]
36.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.
754 / 778
36.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 54: Additional Information for Alarms [53,5] and [53,8]
36.4.37 [101,8]
The additional information bytes for this alarms are defined below. Byte Number 1 2 3 4 Byte... n n+1 n+2 n+3 Byte... Remark: locked E1 are not reported. Table 55: Additional Information for Alarm [101,8] 251 Tag for ATER-HWAY-TP. Number of faulty ATER-HWAY-TP. ATER-HWAY-TP number of the first faulty Ater. ATER-HWAY-TP number of the second faulty Ater. Value 250 Meaning Tag for ABIS-HWAY-TP. Number of faulty ABIS-HWAY-TP. ABIS-HWAY-TP number of the first faulty Abis ABIS-HWAY-TP number of the second faulty Abis Byte
Note:
Locked E1 are not reported.
755 / 778
36.5 TC Alarms
This section describes the additional information provided by other TC alarms.
36.5.1 [67,22] to [67,130]

The TC-16 SBL Alarm number is always 1.
36.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
36.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 57: Additional Information for Alarm [73,022] to [73,216] Interface Error 1..8 BSI Interface
756 / 778
36.5.4 [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 58: Additional Information for Alarm [75,20] to [75,247]
757 / 778
36.5.5 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 61.
Error Type
Table 59: MT120 Board - Equipment Reset/Reset
36.5.6 MT120 - 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 60: MT120 Board, Range >80
758 / 778
36.5.7 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 62. 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 62 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 61: MT120 Board, Error Types, Range <80
759 / 778
36.5.8 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.
760 / 778
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.
761 / 778
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 62: MT120 board, Error Types, Additional Information
762 / 778
36.6 BTS Alarms

This section describes the additional information provided by other BTS alarms.
36.6.1 [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 uBTS HW BOARDS BTS_ADAPT SMFG 00 9100 BTS HW BOARDS SUM 00 Interface Error 11,12,16 11 BSI Interface
Table 63: Additional Information for Alarm [74,20] to [74,202]
763 / 778
764 / 778
37 Consequences of an SBL State Change

This section defines the alarm impact on the system due to an SBL state change.
765 / 778
37.1 9120 BSC SBLs

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.If related to the second Abis, for a second Abis BTS, the TS on the second Abis are no more used. 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. 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
766 / 778
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) are failing. When the BSC is running on a local clock. Loss of both broadcast buses in the BSC either only at a CE level, or at rack level, or at system level. LAC paging messages do not work except for the first 3 cells of the LAC, thus preventing Mobile terminating calls for the other cells, GPRS reset procedure do not work anymore. Processors cannot be preloaded, thus lengthening outages in SW replacement procedure. RMS measurements are no more started nor stopped. A high number of BSC processors have reported DMA problems.
FLT
OPR
BC-SYS-BUS
IT OPR
BSC
IT FIT
767 / 778
SBL name BSC-ADAPT
SBL state IT
Impact on system The BIUA board, which multiplexes BS trunks onto an ABIS HWAY-TP at BSC side, is functioning correctly. There is a degradation in the service provided by the BIUA board, which multiplexes BS trunks onto an ABIS HWAY-TP at BSC side. The BSC transmission board (BUIA), which multiplexes BS trunks onto an ABIS HWAY-TP at BSC side, is lost. It cannot be programmed or accessed. The BIUA board, which multiplexes BS trunks onto an ABIS HWAY-TP at BSC side, is disabled. This state has no impact on the telecom functions of the board, only on the O&M part.
FIT
FLT/FOS
OPR
BSS-TEL
IT
Gain of telecom availability of all the cells of a BSC from BSC point of view. Loss of telecom availability of all cells of a BSC from the BSC point of view. Degradation of telecom availability of all cells of a BSC from the BSC point of view. Loss of telecom availability of all cells of a BSC from the BSC point of view. 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. 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. If parameters must be changed the cell mapped on this BTS become out of service. Loss of O&M availability of the cell from the BSC point of view. If parameters must be changed the cell mapped on this BTS become out of service. Gain of telecom availability of the extra Abis TS
FLT
FIT
OPR
BTS-ADAPT
IT
FIT
FLT/FOS
OPR
BTS-OM
IT FLT/FOS
OPR
BTS-POOL
IT
768 / 778
SBL name BTS-TEL
SBL state IT FLT FIT
Impact on system 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. If only one CLK-REP is unavailable, there is no impact on the service. If no CLK-REP is available 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.
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
769 / 778
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.
DTC
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
770 / 778
SBL name GSL
SBL state IT FLT
Impact on system GPRS signalisation is working correctly. GPRS signalisation is not working correctly. 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). 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 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.
N7
IT FLT/EF OPR
OML
IT
FLT
RSL
IT
OPR
FLT
SM-ADAPT
IT FIT FLT/FOS
OPR
SWITCH
IT
FLT
FIT
771 / 778
SBL name TC-ADAPT
SBL state IT
Impact on system 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. 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. 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 concerned TC-16 SBL are not functioning correctly. The A-interface channels managed by the concerned TC-16 SBL 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. 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.
FIT
FLT
OPR
TCU
IT
FLT/FOS
OPR
FIT TC-16 IT
FIT FLT
OPR
TR-OM
IT FLT
TSC
IT
FIT
X.25
IT
FLT
OPR
772 / 778
37.2 9130 BSC Evolution SBLs

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.If related to the second Abis, for a second Abis BTS, the TS on the second Abis are no more used. 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. If no other ATR is available, the BSC uses its local clock. The trunk will no longer be used for traffic.
FIT
FLT
OPR
ACH
IT
FLT/FOS
A-PCM-TP
IT
FIT
FLT OPR ATER-HWAY-TP IT FLT OPR ATR IT
FLT/EF
773 / 778
SBL name BSC
SBL state IT FIT
Impact on system The BSC is working correctly. There is a persistent problem on the N7 links. New calls can not be established.
BSS-TEL
IT
Gain of telecom availability of all the cells of a BSC from BSC point of view. Loss of telecom availability of all cells of a BSC from the BSC point of view. Degradation of telecom availability of all cells of a BSC from the BSC point of view. Loss of telecom availability of all cells of a BSC from the BSC point of view. The BTS-BIE, which demultiplexes Abis channels from an ABIS HWAY-TP at BTS side, is functioning correctly.
FLT
FIT
OPR
BTS-ADAPT
FIT
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. 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. If parameters must be changed the cell mapped on this BTS become out of service. Loss of O&M availability of the cell from the BSC point of view. If parameters must be changed the cell mapped on this BTS become out of service. Gain of telecom availability of the extra Abis TS
FLT/FOS
OPR
BTS-OM
IT FLT/FOS
OPR
BTS-POOL
IT
774 / 778
SBL name BTS-TEL
SBL state IT FLT FIT
Impact on system 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 board is working correctly. The board is not working correctly. The standby board will become active and takes over all the functions. In case there is no more CP-HW operational a part of the cells and a part of interfaces (Abis, Ater) will be lost. The board is disabled by the operator. The standby board will become active and takes over all the functions. The application software works correctly. The application software does not work correctly. This corresponds to the double fault seen on CP-HW, a part of the cells and a part of interfaces (Abis, Ater) would be lost The CPR is working correctly. All stable calls are not affected. Due to TCH-RM takeover some signaling messages can be lost which can affect some transactions in progress (call setup or handovers). Some CMISE exchanges or file transfers with OMC-R may be interrupted. Anew instance of the process takes over all functions.
OPR CP-HW IT FLT
OPR
CP-LOG
IT FLT
CPR
IT FLT
775 / 778
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).
FLT/FOS
ECU
IT
Concentration unit for all E1 links collected by MUX board is working correctly. Concentration unit for all E1 links collected by MUX board is not working correctly of the MUX board lost the connection with the OMCP board. The standby board will become active and takes over all the functions. Concentration unit for all E1 links collected by LIU board is working correctly. One 16 E1 serial link failed. Concentration unit for all E1 links collected by LIU board is not working correctly. All E1 connected on the LIU are lost. Fan unit is working correctly. Fan unit is not working correctly. GPRS signalisation is working correctly. GPRS signalisation is not working correctly. If there are not enough resources available data transactions can fail due due to signalling links congestion.
FLT
ETU
IT
FIT FLT
FAN
IT FLT
GSL
IT FLT
776 / 778
SBL name N7
SBL state IT FLT/EF
Impact on system N7 Signaling can now be handled by the N7 link (=changeback). N7 Signaling will be handled by another N7 link (=changeover). If there are not enough resources available calls can fail due due to signalling links congestion. N7 Signaling will be handled by another N7 link (=changeover). 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. The power entry module is working correctly. The power entry module is not working correctly. There is no impact on traffic because the power supplies are in parallel. 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 RSL SBL may cause loss of communication with the Frame Unit. Leads to a reduced telecommunication resource allocation capability on the BTS. The SMM board is working correctly. The SMM board is not working correctly. The standby board will become active and takes over all the functions. The SMM board was disabled by the operator. The standby board will become active and takes over all the functions. The SSW board is working correctly. The SSW board is not working correctly. The standby board will become active and takes over all the functions. The SSW board was disabled by the operator. The standby board will become active and takes over all the functions. If the SSW supports the connection to the external alarm box the connection is lost and the external alarms will not be supervised.
OPR OML IT
FLT
PEM
IT FLT
RSL
IT
OPR
FLT
SMM
IT FLT
OPR
SSW-HW
IT FLT
OPR
777 / 778
SBL name TC-ADAPT
SBL state IT
Impact on system 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. Communication with TRE/TRX and/or OMU and/or TSC is established. See RSL and/or OML and/or TSL. All calls carried by TRX managed by the TCU process are lost. New calls can be established after a new instance is started.Causes loss of communication with Frame Unit(s) and/or OMU and/or TSC. 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 concerned TC-16 SBL are not functioning correctly. The A-interface channels managed by the concerned TC-16 SBL are disabled. The TP board is working correctly. Non fatal alarms are present in TPGSM board or configuration change due to extension/reduction failed to apply to TPGSM board. The TP board is not working correctly. The standby board will become active and takes over all the functions. The board is disabled by the operator. The standby board will become active and takes over all the functions. 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. All transmission downloading managed by the process is lost.
FIT
FLT
OPR
TCU
IT
FLT
TC-16
IT
FIT FLT
OPR
TP-HW
IT FIT
FLT
OPR
TR-OM
IT FLT
TSC
IT
FLT
778 / 778

BSC &amp; TC Alarm Dictionary - B11

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSC &amp; TC Alarm Dictionary - B11

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent GSM

BSC & TC Document Reference Guide Release B11

3BK 21618 AAAA PCZZA Ed.16

BLANK PAGE BREAK

Status Short title

RELEASED BSC & TC Alarm Dic.

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

Note: Document Pertinence

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

[99,10] FATAL-HW-FAILURE (Section 31.7).

3BK 21618 AAAA PCZZA Ed.16

Audience Assumed Knowledge

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

1.2 9153 OMC-R AS Alarm Information

1.2.1 Object Identification

3BK 21618 AAAA PCZZA Ed.16

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 21618 AAAA PCZZA Ed.16

1.3 LMT Alarm Messages

1.3.1 Message Identity

1.3.2 Event Time

3BK 21618 AAAA PCZZA Ed.16

3BK 21618 AAAA PCZZA Ed.16

1.3.5 SBL States

1.3.6 RIT List

3BK 21618 AAAA PCZZA Ed.16

1.4 Alarm Information Format

1.4.1 Alarm Definition

1.4.2 Alarm Description

1.4.3 Alarm Definition

3BK 21618 AAAA PCZZA Ed.16

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 21618 AAAA PCZZA Ed.16

1.4.4.4 Failure Identification Strategy

1.4.4.5 Corrective Actions

3BK 21618 AAAA PCZZA Ed.16

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

BSC & TC Alarm Dictionary - B11

BSC & TC Alarm Dictionary - B11