alarm dictionary bsc-tc ed20.pdf

Alcatel BSS

BSC & TC Alarm Dictionary

BSC & TC Document

Reference Guide

Release B9

3BK 20918 AAAA PCZZA Ed.20P06

Status IN PREPARATION

Short title BSC & TC Alarm Dic.

All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel.

BLANK PAGE BREAK

2 / 630 IN PREPARATION 3BK 20918 AAAA PCZZA Ed.20P06

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.2 A1353-RA AS Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.3 LMT Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.4 Alarm Information Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2 Class 32: BSC-ENVIRON Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.1 [32,0] CONV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.2 [32,1] BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3 Class 33: PROCESSOR Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.1 [33,0] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.2 [33,1] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.3 [33,3] ACCESS-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.4 [33,4] RELC-OV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.5 [33,7] TAKEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.6 [33,9] SDCCH-OVRL-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4 Class 35: N7 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.1 [35,0] LNK-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.2 [35,2] RTE-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.3 [35,3] INC-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

5 Class 36: TRUNK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5.1 [36,0] LFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565.2 [36,3] RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575.3 [36,4] AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595.4 [36,5] SLIP-OV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615.5 [36,6] SLIP-UN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635.6 [36,7] LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.7 [36,10] CRCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675.8 [36,11] CHO-EERH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695.9 [36,12] CRC4-BERH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.10 [36,13] CRC4-BERL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

6 Class 38: X.25 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

6.1 [38,0] MODEM-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746.2 [38,1] LINK-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766.3 [38,2] PROT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

7 Class 39: BSC-SW-ANOMALY Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

7.1 [39,1] OSN-NON-RECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827.2 [39,3] OSN-PROCEDURAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837.3 [39,5] USR-NONRECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847.4 [39,7] HWR-NONRECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857.5 [39,18] SANITY-TIMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

8 Class 42: TELECOM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

8.1 [42,1] NACK-MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888.2 [42,2] OVERLOAD-MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908.3 [42,3] START-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918.4 [42,7] NO-RESET-CIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938.5 [42,9] OVERLOAD-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958.6 [42,12] TEL-PAIR-LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968.7 [42,13] BSC-TRAFFIC-REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988.8 [42,14] GPRS-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

3BK 20918 AAAA PCZZA Ed.20P06 IN PREPARATION 3 / 630

Contents

9 Class 43: CELL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019.1 [43,0] LOSS-OF-BCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029.2 [43,1] LOSS-OF-SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049.3 [43,2] LOSS-OF-TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1069.4 [43,3] LOSS-OF-ALL-CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1089.5 [43,4] CELL-TRAFFIC-REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109.6 [43,5] OVERLOAD-BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1129.7 [43,248] CONFIGURED POOLS NOT FULLY USABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

10 Class 44: BTS-OM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11710.1 [44,0] AUDIT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11810.2 [44,1] PROTOCOL-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12010.3 [44,2] RECONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12110.4 [44,3] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12310.5 [44,5] SW-ACTIVATE-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12510.6 [44,6] CONFIG-DATA-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12710.7 [44,7] OMU-SELFTEST-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12910.8 [44,10] ABORT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13110.9 [44,11] PRELOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13210.10 [44,12] BTS-HW-CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

11 Class 45: CHANNEL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13511.1 [45,0] CH-UNBLOCK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13611.2 [45,1] CH-BLOCK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13811.3 [45,2] BSC-CIC-UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14011.4 [45,3] MSC-CIC-UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14211.5 [45,4] END-OF-REP-OF-UNBLOCK-PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

12 Class 46: BACKUP-MEDIUM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14512.1 [46,0] SYNC CORRUPTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14612.2 [46,1] UNSYNC-OTHER-CORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14712.3 [46,4] SECFILE-ROLLBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14912.4 [46,5] SINGLE-UPD-ROLLBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15112.5 [46,6] DUT-ROLLBACK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15312.6 [46,7] DISC-OOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15512.7 [46,8] DISC-PARITY-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

13 Class 47: GLOBAL-BSC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15913.1 [47,2] AUTO-BSC-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16013.2 [47,3] AUTO-BSC-RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16113.3 [47,4] BSC-SYNC-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16213.4 [47,5] BTS-SYNC-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16313.5 [47,6] AUDIT-COMPLETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16413.6 [47,7] BSC-HW-RESYNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16513.7 [47,8] AIFL-FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16613.8 [47,9] CBC-CONNECTION-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16713.9 [47,11] ABIS-TS-ALLOC-FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16913.10 [47,12] INSUFFICIENT-TCU-RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17013.11 [47,13] TRE-SECTOR-MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17213.12 [47,14] LACK-OF-TCU-SPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17413.13 [47,15] SWRPL-IN-PROGRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17513.14 [47,16] MAX-TRE-EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17713.15 [47,17] MLPPP-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17913.16 [47,18] MLPPP-PARTIAL-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18113.17 [47,19] DLS-RESTORATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18313.18 [47,20] NTP-DRIFT-TIME-ALERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18413.19 [47,21] NTP-TIME-SERVER-UNREACHABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18613.20 [47,22] NTP-DRIFT-TIME-EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18813.21 [47,23] MAX-HDLC-EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190


Contents

14 Class 48: TR-OM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19314.1 [48,0] AUDIT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19414.2 [48,1] PROTOCOL-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

15 Class 49: ALERTER Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19715.1 [49,0] LOW-TRAF-SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19815.2 [49,1] CH-INCONSIST-SUSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20015.3 [49,2] TCH-BLOCK-SUSPECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20215.4 [49,3] TCH-OCCUP-SHORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

16 Class 50: BSC EXTERNAL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

16.1 [50,1] EXT-ALARM-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20616.2 [50,2] EXT-ALARM-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20816.3 [50,3] EXT-ALARM-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21016.4 [50,4] EXT-ALARM-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21216.5 [50,5] EXT-ALARM-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21416.6 [50,6] EXT-ALARM-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21616.7 [50,7] EXT-ALARM-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21816.8 [50,8] EXT-ALARM-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22016.9 [50,9] EXT-ALARM-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22216.10 [50,10] EXT-ALARM-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

17 Class 51: SWITCH G2 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

17.1 [51,0] TRANSIENT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22817.2 [51,1] SWITCH-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22917.3 [51,2] ROUTINE-TEST-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23317.4 [51,3] GLOBAL-ROUTINE-TEST-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

18 Class 52: BSC CLOCK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23718.1 [52,0] LOSS-OF-SEL-CLK-INP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23818.2 [52,1] LOSS-OF-CLK-GEN-FN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24018.3 [52,2] SWITCH-TO-LOCAL-CLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24118.4 [52,3] LOSS-OF-SYSTEM-CLOCK-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24318.5 [52,4] LOSS-OF-SYSTEM-CLOCK-B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24418.6 [52,5] LOSS-OF-CLK-DISTR-FN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24518.7 [52,6] BSC-RUN-ON-LOCAL-CLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24618.8 [52,7] LOC-CLK-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

19 Class 53: BROADCAST BUS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24919.1 [53,0] LOSS-OF-ONE-BROAD-BUS-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25019.2 [53,1] LOSS-OF-BOTH-BROAD-BUS-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25119.3 [53,2] DMA-PROBLEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25219.4 [53,3] LOSS-OF-ONE-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25319.5 [53,4] LOSS-OF-BOTH-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25419.6 [53,5] DEGRAD-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25519.7 [53,6] LOSS-OF-ONE-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25619.8 [53,7] LOSS-OF-BOTH-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25719.9 [53,8] DEGRAD-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

20 Class 54: BTS-POOL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

20.1 [54,1] EXTRA TS NOT FULLY USABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

21 Class 66: TSC-TRUNK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26321.1 [66,21] LOOP-TO-ITF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26421.2 [66,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26521.3 [66,50] TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26621.4 [66,66] AIS-2-MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26821.5 [66,81] FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27021.6 [66,86] CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27221.7 [66,99] BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274


Contents

21.8 [66,100] BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27621.9 [66,102] BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27821.10 [66,176] FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28021.11 [66,208] I1I2-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28221.12 [66,210] TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28421.13 [66,211] LOSS-OF-CLK-2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

22 Class 67: TSC-CHANNEL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28922.1 [67,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29022.2 [67,72] AIS-16-KB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29122.3 [67,122] TRAU-SYNCHRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29322.4 [67,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29522.5 [67,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29722.6 [67,131] INT-BUS-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

23 Class 70: TSC-SW-ANOMALY Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30123.1 [70,219] SW-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

24 Class 71: TSC-ENVIRON Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

24.1 [71,0] POWER-SUPPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

25 Class 73: BSC-ADAPT Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30925.1 [73,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31025.2 [73,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31125.3 [73,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31325.4 [73,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31525.5 [73,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31625.6 [73,203] LOSS-OF-ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31825.7 [73,212] LOSS-OF-CLK-8M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32025.8 [73,213] LOSS-OF-CLK-BOTH-8M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32225.9 [73,216] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32425.10 [73,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32525.11 [73,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32725.12 [73,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

26 Class 74: BTS-ADAPT Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

26.1 [74,20] BLOCKED-FROM-USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33226.2 [74,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33426.3 [74,23] TESTMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33526.4 [74,122] SYNCHRO-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33626.5 [74,124] SYNC-AL-CLOCKR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33826.6 [74,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34026.7 [74,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34226.8 [74,139] MISSING-UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34426.9 [74,141] FORCED-CNTRL-ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34626.10 [74,142] INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34726.11 [74,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34926.12 [74,159] DIAG-TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35026.13 [74,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35126.14 [74,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35326.15 [74,245] LOCAL-REINIT-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35526.16 [74,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35726.17 [74,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

27 Class 75: TCSM-ADAPT Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36127.1 [75,20] BLOCKED-FROM-USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36227.2 [75,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36327.3 [75,112] FAN-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36427.4 [75,122] SYNCHRO-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36527.5 [75,124] SYNCHRO-AL-CLOCKR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367


Contents

27.6 [75,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36927.7 [75,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37127.8 [75,136] FIRST-DSP-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37327.9 [75,139] MISSING-UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37527.10 [75,141] FORCED-CNTRL-ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37727.11 [75,142] INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37827.12 [75,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38027.13 [75,159] DIAG-TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38127.14 [75,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38227.15 [75,208] TRIB-TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38427.16 [75,209] INT-BUS-FLT-G25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38627.17 [75,210] ATER-TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38827.18 [75,211] LOSS-OF-CLK-2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39027.19 [75,216] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39227.20 [75,221] TRIB-TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39327.21 [75,222] TRIB-AIS-2MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39527.22 [75,223] TRIB-FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39727.23 [75,224] TRIB-CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39927.24 [75,225] TRIB-BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40027.25 [75,226] TRIB-BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40227.26 [75,227] TRIB-BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40427.27 [75,228] TRIB-FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40627.28 [75,231] ATER-TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40827.29 [75,232] ATER-AIS-2MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41027.30 [75,233] ATER-FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41227.31 [75,234] ATER-CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41427.32 [75,235] ATER-BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41527.33 [75,236] ATER-BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41727.34 [75,237] ATER-BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41927.35 [75,238] ATER-FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42127.36 [75,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42327.37 [75,245] LOCAL-REINIT-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42527.38 [75,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42727.39 [75,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

28 Class 96: PROCESS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43128.1 [96,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43228.2 [96,1] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43328.3 [96,2] MULTIPLE-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43428.4 [96,3] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436

29 Class 97: ATCA-PROCESSOR Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43729.1 [97,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43829.2 [97,1] TAKEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43929.3 [97,2] RLC-OV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44029.4 [97,3] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44229.5 [97,4] APPLICATION-FATAL-TERMINATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44429.6 [97,5] SYSTEM-FATAL-TERMINATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44529.7 [97,6] UNPLUGGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44629.8 [97,8] FW-UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44729.9 [97,10] FATAL-HW-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44829.10 [97,11] TEMPERATURE-CRITICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44929.11 [97,12] TEMPERATURE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45129.12 [97,13] TEMPERATURE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45329.13 [97,14] VOLTAGE-CRITICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45529.14 [97,15] VOLTAGE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45729.15 [97,16] VOLTAGE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45929.16 [97,17] ETHERNET-LINK-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461


Contents

29.17 [97,20] CONFIGURATION-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46329.18 [97,21] TAKEOVER-REFUSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46429.19 [97,30] N7-DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46529.20 [97,31] HDLC-HANDLER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46629.21 [97,32] Q1-HANDLER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46729.22 [97,33] RW-HANDLER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46829.23 [97,34] TDM-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46929.24 [97,35] E1-FRAMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47029.25 [97,36] TP-MAIN-SW-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47129.26 [97,37] TP-MAIN-FILE-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47229.27 [97,38] TP-MAIN-ACCESS-PB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47329.28 [97,39] SS7-SW-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47529.29 [97,50] NE1OE-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47629.30 [97,51] E1-SL-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478

30 Class 98: ATCA-SWITCH Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47930.1 [98,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48030.2 [98,6] UNPLUGGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48130.3 [98,8] FW-UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48230.4 [98,10] FATAL-HW-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48330.5 [98,11] TEMPERATURE-CRITICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48430.6 [98,12] TEMPERATURE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48630.7 [98,13] TEMPERATURE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48830.8 [98,14] VOLTAGE-CRITICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49030.9 [98,15] VOLTAGE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49230.10 [98,16] VOLTAGE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49430.11 [98,18] IP-ROUTER-LINK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496

31 Class 99: ATCA-SHELF Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49931.1 [99,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50031.2 [99,6] UNPLUGGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50131.3 [99,8] FW-UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50231.4 [99,10] FATAL-HW-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50331.5 [99,11] TEMPERATURE-CRITICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50431.6 [99,12] TEMPERATURE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50631.7 [99,13] TEMPERATURE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50831.8 [99,14] VOLTAGE-CRITICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51031.9 [99,15] VOLTAGE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51231.10 [99,16] VOLTAGE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51431.11 [99,18] SHELF-MANAGER-ACCESS-PB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51631.12 [99,19] FAN-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517

32 Class 100: LIU-SHELF Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519

32.1 [100,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52032.2 [100,1] MUX-TAKEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52132.3 [100,4] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52232.4 [100,6] UNPLUGGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52332.5 [100,8] FW-UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52432.6 [100,17] PEM-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52532.7 [100,18] 48V-REDUNDANCY-LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52632.8 [100,50] NE1OE-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52832.9 [100,51] E1-SL-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530

33 Class 101: BSC-TRANS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53333.1 [101,0] LIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53433.2 [101,1] AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53633.3 [101,2] LFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53833.4 [101,4] BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54033.5 [101,5] RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542


Contents

33.6 [101,6] BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54433.7 [101,7] BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54633.8 [101,8] FRAME-SLIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548

34 BSC/TC Alarm Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55134.1 Restart and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55234.2 Reset and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56834.3 System Support Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56934.4 Other BSC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56934.5 TC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615

35 Consequences of an SBL State Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623


Figures

FiguresFigure 1: Graphical Flowchart for Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Figure 2: SWITCH-FAIL: Corrective Actions for Write Violation Overflow, Loss of Sync Overflow and Init FailAlarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Figure 3: SWITCH-FAIL: Corrective Actions for Loss of Sync Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Figure 4: SWITCH-FAIL: Corrective Actions for HW Fault Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232


Tables

TablesTable 1: Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Table 2: Alarm Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Table 3: Alarm Definition: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Table 4: Mapping of MO Perceived Severity to LMT Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Table 5: Additional Information for Restart and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552

Table 6: FMM-IDs in Bytes 4 and 5 for Restart Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562

Table 7: Error Types in Bytes 10 and 11 for Restart Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567

Table 8: Additional Information for Reset and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568

Table 9: System Support Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569

Table 10: Additional Information for Alarm [33,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569

Table 11: Additional Information for Alarms [34,0] to [34,2] and [34,4] to [34,6] . . . . . . . . . . . . . . . . . . . . . . . . 569


Table 13: Test Segment Results for Alarm [34,3], [51,1] (Byte 0) and [51,2] (One Byte Only) . . . . . . . . . . . 572

Table 14: Test Fault Type for Alarm [34,3], [51,1] (Byte 1) and [51,2] (One Byte Only) . . . . . . . . . . . . . . . . . 576

Table 15: TDM Connection Test Results (Bytes 6 to 21) for Alarm [34,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576




Table 19: Additional Information for Alarm [35,3], Layout 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579

Table 20: Additional Information for Alarm [35,3], Layout 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579

Table 21: Example of Additional Information for Alarm [35,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579


Table 23: Additional Information for Alarm [36,14] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580




Table 27: Additional information for Alarm [42,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581






Table 33: Additional Information for Alarms [43,0] to [43,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588


Table 35: Additional Information for Alarms [44,0], [44,5] and [44,6] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590


Table 37: Additional Information for Alarms [46, 0], [46,1] and [46,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591




Tables


Table 41: Additional Information for Alarms [49,2] and [49,3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593


Table 43: Additional Information for Alarm [51,1] - First Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595

Table 44: Additional Information for Alarm [51,1] - Subsequent Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596

Table 45: TDM Test Result Byte Descriptions for Alarm [51,1] and [51,2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597

Table 46: Detailed TDM Test Results for Alarm [51,1] and [51,2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597


Table 48: Example for an Unsuccessful Test Results Format for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . 598

Table 49: Relationship IAD/NA to RIT and Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611


Table 51: Additional Information for Alarms [52,1], [52,5] and [52,7] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613

Table 52: Additional Information for Alarms [53,0], [53,1], [53,3], [53,4], [53,6] and [53,7] . . . . . . . . . . . . . . 613


Table 54: Additional Information for Alarms [53,5] and [53,8] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614

Table 55: Additional Information for Alarm [70,219] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615

Table 56: Additional Information for Alarm [73,022] to [73,216] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615

Table 57: Additional Information for Alarm [74,20] to [74,202] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616

Table 58: Additional Information for Alarm [75,20] to [75,247] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617

Table 59: MT120 Board - Equipment Reset/Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618

Table 60: MT120 Board, Range >80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618

Table 61: MT120 Board, Error Types, Range <80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619

Table 62: MT120 board, Error Types, Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622


Preface

Preface

Purpose The purpose of the alarm dictionary is to provide the operator with a structuredmethod for handling alarm messages generated by the BSC and the TC.

This document contains a list of all BSC and TC alarms, and the actionsrequired to nullify them.

Alarms are displayed at the OMC-R terminal and at the LMT to inform theoperator of system faults.

Note: When a fault occurs, a number of alarms can be generated simultaneously.These alarms must be analyzed as a group to determine the precise fault.

What’s New In Edition 20The following alarms were added:

[97,8] FW-UPGRADE (Section 29.8)



[100,8] FW-UPGRADE (Section 32.5).Description improvement for:

[42,12] TEL-PAIR-LOST (Section 8.6)

[42,14] GPRS-RESET (Section 8.8)

[75,148] RESET (Section 27.12).The following alarms were removed:

[36,14] CLA

[36,15] OOR

[47,0] SYNC-REQUEST.


Preface

In Edition 07Alarms for A9130 BSC Eviolution were added.Description improvement in:


[42,13] BSC-TRAFFIC-REPORT (Section 8.7)


[75,148] RESET (Section 27.12)

[100,50] NE1OE-FAILURE (Section 32.8)

In Edition 06Description improvement for alarms:

[33,3] ACCESS-FAILURE (Section 3.3)

[33,4] RELC-OV (Section 3.4)

[33,9] SDCCH-OVRL-BSC (Section 3.6)

[52,2] SWITCH-TO-LOCAL-CLK (Section 18.3)

[52,6] BSC-RUN-ON-LOCAL-CLK (Section 18.7)

[67,72] AIS-16-KB (Section 22.2)

[67,122] TRAU-SYNCHRO (Section 22.3).

In Edition 05Description improvement for alarm [46,7] DISC-OOS (Section 12.6).

In Edition 04Description improvement for alarm [47,14] LACK-OF-TCU-SPACE (Section13.12).

In Edition 03Description improvement for alarms [47,11] ABIS-TS-ALLOC-FAILED (Section13.9) and [47,12] INSUFFICIENT-TCU-RES (Section 13.10).

In Edition 02Alarm [43,248] CONFIGURED POOLS NOT FULLY USABLE (Section 9.7)was added.Description improvement for [43,2] LOSS-OF-TCH (Section 9.3).Description improvement for alarms of class 49:

[49,0] LOW-TRAF-SDCCH (Section 15.1)

[49,1] CH-INCONSIST-SUSP (Section 15.2)

[49,2] TCH-BLOCK-SUSPECT (Section 15.3)

[49,3] TCH-OCCUP-SHORT (Section 15.4)The following alarms were updated for commercial usage:

[43,0] LOSS-OF-BCCH (Section 9.1)

[43,1] LOSS-OF-SDCCH (Section 9.2)

[43,2] LOSS-OF-TCH (Section 9.3)


Preface

[43,3] LOSS-OF-ALL-CHAN (Section 9.4)

[52,0] LOSS-OF-SEL-CLK-INP (Section 18.1)

[52,1] LOSS-OF-CLK-GEN-FN (Section 18.2)

[52,3] LOSS-OF-SYSTEM-CLOCK-A (Section 18.4)

[52,4] LOSS-OF-SYSTEM-CLOCK-B (Section 18.5)

[52,5] LOSS-OF-CLK-DISTR-FN (Section 18.6)

[53,0] LOSS-OF-ONE-BROAD-BUS-BSC (Section 19.1)

[53,1] LOSS-OF-BOTH-BROAD-BUS-BSC (Section 19.2)

[53,3] LOSS-OF-ONE-BROAD-BUS-RACK (Section 19.4)

[53,4] LOSS-OF-BOTH-BROAD-BUS-RACK (Section 19.5)

[53,6] LOSS-OF-ONE-BROAD-BUS-CE (Section 19.7)

[53,7] LOSS-OF-BOTH-BROAD-BUS-CE (Section 19.8)

[66,211] LOSS-OF-CLK-2M (Section 21.13)

[73,203] LOSS-OF-ACT (Section 25.6)

[73,212] LOSS-OF-CLK-8M (Section 25.7)

[73,213] LOSS-OF-CLK-BOTH-8M (Section 25.8)

[75,211] LOSS-OF-CLK-2M (Section 27.18)Description improvement for alarms:

[53,0] LOSS-OF-ONE-BROAD-BUS-BSC (Section 19.1)

[53,1] LOSS-OF-BOTH-BROAD-BUS-BSC (Section 19.2)

[53,2] DMA-PROBLEM (Section 19.3)

[53,3] LOSS-OF-ONE-BROAD-BUS-RACK (Section 19.4)

[53,4] LOSS-OF-BOTH-BROAD-BUS-RACK (Section 19.5)

[52,5] LOSS-OF-CLK-DISTR-FN (Section 18.6)

[53,6] LOSS-OF-ONE-BROAD-BUS-CE (Section 19.7)

[53,7] LOSS-OF-BOTH-BROAD-BUS-CE (Section 19.8)

[53,8] DEGRAD-BROAD-BUS-CE (Section 19.9)

Consequences of an SBL State Change (Section 35)

[35,2] RTE-REP (Section 4.2)

[43,2] LOSS-OF-TCH (Section 9.3)Description improvement for alarms:

[35,0] LNK-REP (Section 4.1)

[35,2] RTE-REP (Section 4.2)

[35,3] INC-REP (Section 4.3)

[42,13] BSC-TRAFFIC-REPORT (Section 8.7) .


Preface

In Edition 01For dinamic Abis feature the new alarm [54,1] Extra-ts-not-fully-usable is raisedinstead of alarm [43,248] Configured-pools-not[fully]-usable.The alarm [51,3] "global-routine-test-rep" is removed because it will not besent to OMC any more, from B9.

Audience This document is aimed at telecommunications operators responsible forperforming O&M fault handling and troubleshooting tasks.

Assumed Knowledge The operator must be familiar with the following:

Alcatel O&M concepts for the BSS

MO scenario

Fault management

Use of OMC-R and BSC terminals

SBL hierarchies of the BTS, BSC and TC

Telecommunications techniques including line transmission and switching.


1 Introduction

1 Introduction

This section describes the structure of alarm messages.


1 Introduction

1.1 OverviewThis alarm dictionary provides additional information that is not displayed in thealarm messages sent to the OMC-R, BSC or TC terminals.

The dictionary contains alarm definitions for each alarm type produced bythe BSS.

Each definition describes the:

Alarm definition

Alarm description

Impact on System

Methods for further fault isolation

Corrective actions.

1.2 A1353-RA AS Alarm InformationIn the A1353-RA OMC-R, Alarm Surveillance provides an efficient means tocontrol, supervise and manage equipment problems in the BSS.

Alarms or Alarm notifications consist of messages sent by network resourcesthat have detected problems or failures in the network. These alarms aredisplayed in lists while alarm counters keep track of statistics. By clicking on analarm in the list, the operator gets detailed information. AS displays informationas described below.

1.2.1 Object Identification

The Object Identification identifies the resource that raised the alarm.

Object identification gives information about:

The resource type (Object Class)

The resource name (Friendly Name). For a board, the Friendly Name alsoshows the board’s location by rack, shelf and slot.


1 Introduction

1.2.2 Alarm Type

The Alarm Type identifies the type of problem the alarm refers to.

This information is sub-divided into:

eventType. Table 1 describes the five eventTypes.

probableCause

perceivedSeverity: gives the severity level of the alarm. Table 2 describesthe severity levels.

eventType Indicates...

Communication a problem with a procedure or process used to convey information fromone point to another in the network.

Quality of Service degradation in the quality of service in the network.

Processing Error a software or processing fault.

Equipment an equipment fault.

Environmental a problem in the enclosure containing the equipment.

Table 1: Event Types

Severity Level Indicates...

Critical a serious fault condition which requires immediate correction. Example: amanaged object goes out of service.

Major a fault condition which requires urgent corrective action. Example: severedegradation in the operation of a managed object.

Minor a fault condition which does not affect service but corrective action shouldbe taken to avoid a more serious fault.

Warning detection of a potential fault condition. Action should be taken to diagnoseand correct the problem to avoid a more serious fault condition.

Indeterminate the severity level cannot be defined by the resource which raised the alarm.

Cleared the alarm was cleared by the resource which raised the alarm.

Table 2: Alarm Severity Levels

In addition to the Object Identification and Alarm Type information, all alarmsalways give the date and time of the alarm. An alarm may also contain optionalinformation, such as the notification id. Refer to the AS on-line help for moredetailed information on AS.


1 Introduction

1.3 LMT Alarm MessagesThe format of Alarms displayed at a LMT differs from that in the OMC -R.

Depending on the type of alarm and where it is viewed, an alarm messagecontains all or most of the parameters listed in this section.

1.3.1 Message Identity

The identity number given to the alarm message stored in the OMC-R database.

1.3.2 Event Time

The time the message was issued at its source or received at the OMC-R.

1.3.3 Location

The origin of the alarm, consisting of:

Network element - the BSS identity

Unit type:

bts

bsc

tcsm

bie

tsc

bss.

Unit number:

0 or 1 for a tcsm

0 to 40 for a bie

1 for a bsc, tsc or bss

1 to 40 for a bts.

SBL type

SBL number and subnumber, if appropriate. For example, RTS (3, 4) is RTSnumber 4 of FU3 (the parent SBL).


1 Introduction

1.3.4 Classification

The characteristics of the alarm, consisting of:

Alarm Class name and number - as shown in the Contents list of the

Alarm Dictionary

Alarm Type name and number - as shown in the Contents list of the Alarm

Dictionary

Alarm Number - dependent on the Alarm Class and Type. See theappropriate dictionary entry for the valid alarm numbers for a particular alarm

Alarm Condition - has one of the following values:

begin - alarm on. For fatal failures, the affected SBL changes state to

FLT or FOS. For non-fatal failures, the affected SBL changes state to FIT

end - alarm off. Indicates the successful recovery of the system. The

affected SBL may not change state if other alarms related to theSBL are on

event - occurrence of anomaly. No action is required unless it occurs

frequently. Event alarms are of short duration and the affected SBLdoes not change state. The system retry/recovery mechanism has

cleared the fault.

If a fatal alarm occurs and the affected SBL changes state to FOS, the systemisolates the faulty equipment if it cannot be initialized. After a repair action, theoperator normally initializes the equipment.

If a fatal alarm occurs and the affected SBL changes state to FLT, the systemresets the faulty equipment. When the alarm ceases, the system automaticallyinitializes the equipment.

If a non-fatal alarm or event occurs, the affected SBL’s are put into the FIT state.In the worst situation, the equipment operates in a degraded mode.


1 Introduction

1.3.5 SBL States

An SBL has one of the following (current) states:

IT

FIT

Faulty

EF

FOS

OPR

SOS

WTC

UT

NEQ

MSD

MSD AUTO.

Refer to the Operations & Maintenance Principles for a description of the states.

1.3.6 RIT List

The information for the suspected RIT(s) is displayed if the system is able todetermine the location of the fault.

The information consists of:

Unit type - bts, bsc, tscm, bie, tsc or bss

Unit number -

0 or 1 for a tcsm

0 to 40 for a bie

1 for a bsc, tsc or bss

1 to 40 for a bts.

Physical location - the position of the RIT board within the cabinet. For

example, [A, 4, 21] indicates the board in slot 21 of rack 4 of cabinet A.For BSC and BTS equipment, the cabinets are identified as 1, 2, 3, etc.

instead of A, B, C, etc.

RIT type - the name of the RIT board.

If more than one RIT is shown in the list, the RIT most likely to be causing thefault is indicated. Replace this RIT first and initialize it. If the fault persists,replace another RIT from the list and initialize it.


1 Introduction

1.4 Alarm Information FormatEach alarm definition and description in the dictionary is structured as follows:

1.4.1 Alarm Definition

MO format LMT format

Banner Banner

specificProblems Alarm Class & [number] - Alarm Type & [number]

eventType -

probableCause -

perceived Severity Category

SBL SBL

Table 3: Alarm Definition:

1.4.2 Alarm Description

The Alarm description is structured as follows:

Alarm Description

Impact on System

Failure Identification Strategy (if applicable)

Corrective Actions.

1.4.3 Alarm Definition

1.4.3.1 BannerEach BSS alarm definition starts with an identification banner which allows thelocation of the appropriate definition. It takes the form:

[36, 7] TRUNK - LOS

1.4.3.2 eventTypeThe eventType attribute identifies the basic type of the alarm. Table 1 describesthe event Types.

1.4.3.3 specificProblemsThe specificProblems provides the alarm class name.

1.4.3.4 probableCauseThis attribute provides additional information as to the probable cause ofthe alarm. Its value belongs to a set of possible values either defined inrecommendation X.721 (for those that have a wide applicability) or defined fora particular TMN project.


1 Introduction

1.4.3.5 perceivedSeverityThis attribute gives the severity level of the alarm. Table 2 describes theseverity level.

The table below provides a mapping between the severity level shown inAS and at the LMT.

MO Severity LMT Category

Critical VPMA, SA

Major PMA

Minor DMA

Warning MI

Table 4: Mapping of MO Perceived Severity to LMT Category

1.4.4 Alarm Description

1.4.4.1 Alarm DescriptionThe Alarm Description describes the alarm and, where appropriate, thedifferences to the default perceived severities.

1.4.4.2 Impact on TelecomThis field describes the impact on the Telecom system behavior. It alsocontains a table indicating which part of the system is affected by the fault interms of loss, degradation or none.

For example, if a cell is affected, the cell column in the table contains a tick (X) ineither the Loss or Degradation row. The tick can be doubled in any one column(XX), indicating the primary impact of the alarm. If the column has a tick in theNone row, that part of the system is unaffected by the fault. For different impactcases (redundancy, diversity, etc.) more symbols, like ladders (#), are used.

The table indicates the worst case, even though redundancy may be provided.

1.4.4.3 Impact on SystemThe impact on the system is defined in terms of Telecom and/or O&M.;


1 Introduction

1.4.4.4 Failure Identification StrategySometimes more information is necessary to determine the precise fault. TheFailure Identification Strategy lists the checks and tests to perform to obtainthis information.

The additional data is gathered from:

Diagnosis/tests to be applied - appropriate on-site or remote diagnostic and

test procedures to perform

Complex system alarm correlation - other checks that can provide moreinformation about the fault.

Checks that determine whether:

The failure is provoked by a problem external to the reporting unit

Multiple or repetitive failures are reported by one or more similar SBLs

The performance of the affected subsystem is degraded. Newperformance measurements can be compared with previous

measurements.

Resource and data verification - checks that determine whether:

Hardware is serviceable or available. The items checked are passive

items, such as cables, links and boards that do not report their state, andempty slots in subracks

Software versions and parameter settings are correct.

1.4.4.5 Corrective ActionsA description of the recovery actions to be performed by the operator ormaintenance staff. The recovery actions are based on the information providedby the alarm message or the results of diagnostic actions.

To solve the alarm, a graphical flowchart is used. It shows the required checks,tests and actions to be performed to determine the fault and to solve thealarm. The figure below shows an example of a flowchart and describesthe different flowchart fields.

Click on a dedicated action field to display the detailed description of the task.

Some alarms provide additional information. If it is displayed as a text message,the original information from the BSS has been decoded.


1 Introduction

[32,0] CONV

Alarmsolved

yesConverteroperational?

no

On−site

ContactSystem Support

Restart faulty converter by disengaging/engaging RIT

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

On−site

On−site

Replace BSC RIT

Alarmsolved


no

Start field with alarm numberand alarm name

On−site action fields

Decision field

On−site action fields

Decision field

End Field

Figure 1: Graphical Flowchart for Corrective Actions

If the additional information is not decoded, it is displayed as pairs ofhexadecimal digits as described in BSC/TC Alarm Additional Information(Section 34). At the BSC terminal, the additional information consists ofnumbers in the range 0 to 255. Each number represents the contents of onepair of digits.

Decoding Additional Information from AlarmsDecoding BSC additional information must only be attempted by Alcatel systemsupport personnel.If a fault persists after corrective actions have been taken, send a copy of thealarm message containing the additional information to the Alcatel SystemSupport office.


2 Class 32: BSC-ENVIRON Alarms


This section defines the BSC alarms for the Class 32: BSC-ENVIRON alarmclass.



2.1 [32,0] CONV

specificProblems BSC-ENVIRON [32] CONV [0]

eventType Equipment

probableCause PowerProblem

perceivedSeverity Critical (VPMA)

Alarm Description A9120 BSC Evolution: The convertor condition is detected by theS-CPR. A fault can be detected for a particular convertor. This is doneby monitoring the scan point on the controlling S-CPR. One scan pointexists for each convertor.The redundant power supply is available.

Applicability A9120 BSC

Impact on System There are two convertors which provide power for each shelf. Thisprovides redundancy and, in the event of one convertor failing, theother convertor provides the power supply. In the event of the twoconvertors failing, no power is provided to the shelf. However, if bothconvertors powering the S-CPR fail, the battery back-up then providesits power supply. Evolium A9120 BSC:The BSC is able to distinguish between the different convertors withthe Evolium A9120 BSC implementation and cabling. Therefore theRIT of the affected convertor is indicated in the alarm.There is no impact on traffic because the power supplies are in parallel.See Consequences of an SBL State Change.

Impact Trunk(s) Cell/BTS(s) Signaling Call Handling O&M Capabilities

Loss No No No No No

Degradation No No No No No



2.1.1 Corrective Action

[32,0] CONV

Alarmsolved


no

On−site


Restart faulty converter by disengaging/engaging RIT

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

On−site

On−site

Replace BSC RIT

Alarmsolved


no

graphics/2081821002.cgm



2.2 [32,1] BAT

specificProblems BSC-ENVIRON [32] BAT [1]

eventType Equipment



Alarm Description The battery alarm condition can only be detected by the CPR which itcontrols. There is one battery controlling each S-CPR. So, if a batteryis removed, the CPR goes down and no fault is detected. Only a faultin the actual battery operation can be detected and this is done bymonitoring the scan point on the controlling S-CPR. One scan point isprovided for each battery. There is a physical connection between thebattery and the CPR. When this connection is broken, it is detectedby hardware via the scan points.


Impact on System S-CPR-ACTIVES-CPR (A9120 BSC):The memory board is implemented on a daughter board, plugged onthe CPRC. The CMFA board, (the flash-based board) indicates aproblem with the battery. The battery is empty and has no power toback up. The normal lifespan of a battery is 10 years.The BSC is able to detect a fault, low voltage, on the correct battery dueto the fact that two scan points are used, one on CPR1 for battery Aand one on CPR2 for battery B. The RIT for both batteries is the same.See Consequences of an SBL State Change.


Loss No No No No No





[32,1] BAT

Alarmsolved

yesBatteryoperational?

no

On−site

Replace SYS−CPRC


Identify the suspected SYS−CPRC.

On−site

graphics/2081832001_g2.cgm


3 Class 33: PROCESSOR Alarms


This section defines the BSC alarms for the Class 33: PROCESSOR alarmclass.



3.1 [33,0] RESTART

specificProblems PROCESSOR [33] RESTART [0]

eventType Processing Error

probableCause SoftwareError

perceivedSeverity Indeterminate

Alarm Description An autonomous restart of a processor has occurred because of afailure condition on the processor.


Impact on System In case of CPR:——————-The SBL state remains unchanged. The operating system and all FMMare sequentially re-initialized.S-CPR - Simplex: SDCCH allocation is not possible for some seconds.New telecommunication transactions fail. There is no impact on currentcalls.Standby S-CPR - Duplex Telecom functions are not affected. If BSCor BTS processors are being loaded by the standby CPR, loading isstopped and then resumed when the restart is complete.Active S-CPR - Duplex: A takeover occurs if the standby CPR and itsdisk are IT; the standby CPR now becomes active. SDCCH allocationis not possible for some seconds. New telecommunication transactionsfail. Communication with the OMC-R is lost for some seconds.OSI-CPR - Simplex: Telecom functions are not affected. If the restarthappens at a five minute boundary and the CPR has to carry out PMactivities, 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. Ifthe restarted processor is an OSI-CPR that manages the OSIcommunications with the OMC-R, some file transfers may beinterrupted. If this happens, the OMC-R requests the information again.Active OSI-CPR - Duplex: Telecom functions are not affected. If theactive OSI-CPR is restarted, and the standby OSI-CPR and its diskare IT, the standby immediately takes over its functions and becomesactive. If the restart happens at a five minute boundary and the CPRhas to carry out PM activities, the restart can cause some problemswith file production (such as, loss of last five minute contribution,missing files). If the restarted processor is an OSI-CPR that managesthe OSI communications with the OMC-R, some file transfers may beinterrupted. If this happens, the OMC-R requests the information again.



Impact on System (cont’) In case of DTC:——————The SBL state remains unchanged. All stable calls assigned on TCHsremain unaffected. Some Signaling messages can be lost. This canaffect 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 sometransactions 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 sometransactions in progress. Call setup in SDCCH phase/handover fails.

Note: For every processor restart, an attempt has been made tominimize the impact on the system. Recovery after a processor restartdepends on the action taken.The following corrections are performed by the system:* Restart the action* Resume the action* Initiate an audit* Terminate the action.

See consequences of an SBL State Change.


Loss No No No No No

Degradation Yes (if DTC) No Yes (if CPR,DTC, TCU orTSC)

Yes (if CPR,DTC or TCU)

Yes (if TSC)


The processor returns to service automatically. If the restart procedure failsor there are too many restarts within a certain time frame, the processor isreloaded.

See BSC/TC Alarm Additional Information (Section 34) for the byte definition.



3.2 [33,1] RESET

specificProblems PROCESSOR [33] RESET [1]




Alarm Description An autonomous reload (reboot) of a processor occurred successfully.


Impact on System 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 someminutes. 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 itsdisk are IT; the standby CPR now becomes active. SDCCH allocationis not possible for some seconds. New and existing telecommunicationtransactions fail. Communication with the OMC-R is lost for someseconds. If there is an autonomous reboot of one S-CPR and a restartof 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.25link to the OMC-R, communication with the OMC-R is lost for someseconds. If the reset/reload (reboot) processor is an OSI-CPRthat manages the OSI communication with the OMC-R, some filetransfers may be interrupted. If this happens, the OMC-R requests theinformation again.* Active OSI-CPR - Duplex: Telecom functions are not affected.If the master performs a Reset, the standby immediately takes over itsfunctions. If the reset happens at a five minute boundary, there may beproblems with production of PM files.

specificProblems PROCESSOR [33] RESET [1]




Alarm Description An autonomous reload (reboot) of a processor occurred successfully.





In case of CPR:—————The impact depends on the type of CPR.* S-CPR - Simplex: SDCCH/TCH allocation is not possible for someminutes. 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 itsdisk are IT; the standby CPR now becomes active. SDCCH allocationis not possible for some seconds. New and existing telecommunicationtransactions fail. Communication with the OMC-R is lost for someseconds. If there is an autonomous reboot of one S-CPR and a restartof 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.25link to the OMC-R, communication with the OMC-R is lost for someseconds. If the reset/reload (reboot) processor is an OSI-CPRthat manages the OSI communication with the OMC-R, some filetransfers may be interrupted. If this happens, the OMC-R requests theinformation again.* Active OSI-CPR - Duplex: Telecom functions are not affected.If the master performs a Reset, the standby immediately takes over itsfunctions. If the reset happens at a five minute boundary, there may beproblems with production of PM files.

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 processorare lost.

For every processor reset/reload (reboot), an attempt has been madeto minimize the impact on the system. Recovery after a processorreset depends on the action taken.

The following corrections are performed by the system:

* Restart the action* Resume the action* Initiate an audit* Terminate the action.

For the consequences of an SBL state change, see Consequencesof an SBL State Change.




Loss Yes (if DTC) Yes (if CPRor TCU)

Yes (if CPR,DTC, TCU orTSC)

Yes (if CPR,DTC or TCU)

Yes (if CPR, TCU orTSC)



The processor returns to service automatically. If the restart procedure failsor there are too many restarts within a certain time frame, the processor isreloaded.

See BSC/TC Alarm Additional Information (Section 34) for the byte definition.



3.3 [33,3] ACCESS-FAILURE

specificProblems PROCESSOR [33] ACCESS-FAILURE [3]

eventType Equipment

probableCause EquipmentMalfunction

perceivedSeverity Major (PMA)

Alarm Description The self-maintenance part of the system (i.e., Heartbeat) detected anunreachable processor and informs central maintenance.


Impact on System If a reload request is not received from the processor, the processorSBL is FLT and an alarm is sent with alarm type Access Fail. Theprocessor is not accessible.

If CPR:O&M capacity is degraded.

If DTC:For every type of DTC, there is always the release of the transactionswhich 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 effecton the calls.*If the DTC manages a N�7 link, as long as there are other N�7 linksin service, there is no loss of calls.(degradation can happen if theremaining capacity is too small.*If the DTC manages a GSL, as long as there are other GSL for thecorresponding GPU, there is no loss of transactions (degradation canhappen 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 willinsure 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 forthe same Q1 modules (for example, no possible extension/modificationof BTS connected on depending BIE).

See also Consequences of an SBL State Change.




Loss Yes (if DTC) Yes (if CPR,DTC orTCU)

Yes (if TSC) Yes (if CPR) Yes (if CPR, TCU orTSC)

Degradation No Yes (if TCUand cellshave TRXmapped onother TCU)

Yes (if DTC orTCU)

Yes (if DTC orTCU)

Yes (if CPR or TCU)


[33,3] ACCESS−FAIL

Alarmsolved

yesAccessoperational?

no


yesSubsequent alarm(s) events?

no

Solve that alarm(s) first

MO is Unlocked/

enabled?

yes

no

Check for BSC switch problems

On−site

Replace CPR/DTC/TCU/TSC




3.4 [33,4] RELC-OV

specificProblems PROCESSOR [33] RELC-OV [4]

eventType Equipment



Alarm Description The processor has been declared FOS and is removed from service.This is done because there have been too many processor reloadswithin a certain time frame for a specific processor.The loader keeps a record of the number of reload attempts for eachprocessor within a certain time frame. If too many reload attemptsoccur, central maintenance auto-disables the processor, unless theprocessor is an S-CPRA (simplex). The auto-disabled processor isblocked from use.


Impact on System If a reload request is not received from the processor, the processorSBL is FLT and an alarm is sent with alarm type Access Fail. Theprocessor is not accessible.

If CPR:O&M capacity is degraded.

If DTC:For every type of DTC, there is always the release of the transactionswhich 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 effecton the calls.*If the DTC manages a N�7 link, as long as there are other N�7 linksin service, there is no loss of calls. (degradation can happen if theremaining capacity is too small*If the DTC manages a GSL, as long as there are other GSL for thecorresponding GPU, there is no loss of transactions (degradation canhappen 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 willinsure 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 forthe same Q1 modules (for example, no possible extension/modificationof BTS connected on depending BIE).





Loss Yes (if DTC) Yes (if CPR) Yes (if CPR orTSC)

Yes (if CPR) Yes (if CPR, TCU orTSC)

Degradation No Yes (if TCUand cellshave TRXmapped onother TCU)

Yes (if DTC orTCU)

Yes (if DTC orTCU)

No


[33,4] RELOC−OV

Alarmsolved

yes

Alarm persists?

no


Lock CPR/DTC/TCU/TSC

On−site

Replace CPR/DTC/TCU/TSC

TestCPR/DTC/TCU/TSC

VerifyCPR/DTC/TCU/TSC

Unlock CPR/DTC/TCU/TSC

Alarmsolved

yes

Alarm persists?

no




3.5 [33,7] TAKEOVER

specificProblems PROCESSOR [33] TAKEOVER [7]


probableCause SoftwareProgramAbnormallyTerminated


Alarm Description There has been a change in the active processor in the case of anactive/standby processor pair. The active/standby processor pairs inthe BSC are the CPRs or the DTC TCH-RM. This alarm identifies theprocessor that is now active and is the new master. The previouslyactive processor goes into standby mode.

This alarm is generated only when a takeover occurs.Another alarm or an operator action causing the take-over can lead toextra impact on the telecom traffic.



If CPR:During a takeover an attempt is made to minimize the impact on thesystem and ongoing transactions with the OMC-R. Recovery after aCPR takeover depends on the action taken.

The following corrective actions are performed by the system:* Restart the action* Resume the action* Initiate an audit* Terminate the action.

If DTC TCH-RM:During a take-over no radio channel allocation is possible for a shortperiod.



Loss No Yes (if DTCTCH-RM)

Yes (if DTCTCH-RM)

Yes (if DTCTCH-RM)

No

Degradation No No Yes (if CPR) Yes (if CPR) Yes (if CPR)




[33,7] TAKEOVER

Alarmsolved

yes

Alarm persists?

no


Lock CPR/DTC

TestCPR/DTC

VerifyCPR/DTC

Unlock CPR/DTC




3.6 [33,9] SDCCH-OVRL-BSC

specificProblems PROCESSOR [33] SDCCH-OVRL-BSC [9]

eventType Equipment

probableCause PerformanceDegraded

perceivedSeverity Warning (MI)

Alarm Description The load on TCU is excessive due to a high number of simultaneouslyactive SDCCH.


Impact on System The BSC applies in this case a delayed release of the SDCCH.This decreases the TCU load but increases the SDCCH occupancy,thus leading to more lack of SDCCH resources to establish newtransactions.


Loss No No No No No

Degradation No No Yes Yes No


[33,9] SDCCH−OVRL−BSC

Alarmsolved

yes

Alarm persists?

no


Remap the RSL to spread the load of SDCCH among other TCUs (flatten hot spots).



4 Class 35: N7 Alarms


This section defines the BSC alarms for the Class 35: N7 alarm class.



4.1 [35,0] LNK-REP

specificProblems N7 [35] LNK-REP [0]

eventType Communication

probableCause TransmitterFailure

perceivedSeverity Minor (DMA)

Alarm Description This message can represent either an event or a change of status. If itis an event, it indicates a change of link state . If it is a state change, itindicates a change of traffic state.


A9130 BSC

Impact on System 1. Change of Link state.This alarm is commonly caused by a clock problem. If it is accompaniedby SLIP_UNDER_RUN, SLIP_OVER_RUN alarms, there is a lack ofsynchronisation of the 2 Mbits signals arriving on the BSC. And thetransmission boards settings are incorrect. A high error rate on thetransmission lines (BER 10-4) has forced use of the transmissionmodules internal clock.

2. Change of traffic stateThere is a persistent problem on the N7 link. If the alarm isaccompanied by transmission alarms, there is a transmission problem.Otherwise the problem is caused by an incident at the MSC.

For A9120 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 A9130 BSC Evolution: The alarm is accompanied by FRAME-SLIP[101,8] alarm related to the corresponding ATR SBL.


Loss No No No No No





[35,0] LNK−REP

Alarmsolved

yesAlarm persists?

no

On−site

Replace Sync Input module

Solve Clock alarm(s) first

On−site

Replace transmission lines equipment

Check/correct transmission board

settings

yes

2−Mbit/s Sync inputs OK?

no

yesClock alarm events?

no− There is a lack of synchronization of the 2 MBit/s signals arriving at the BSC.or− The transmission board settings are incorrect.or− A high error rate on the transmissionlines forced the use of the transmission modules internal clock.

yesSLIP... alarm events?

no

Alarmsolved

Alarm persists?

no

On−site

yes

Transmission lines OK?

no

On−site


yes




4.2 [35,2] RTE-REP

specificProblems N7 [35] RTE-REP [2]


probableCause ResponseTimeExcessive


Alarm Description A destination became accessible or inaccessible. The alarm numberrepresents the DPC of the MSC.


A9130 BSC

Impact on System This alarm can come from transmission problem on the Ater mux oron the Atr. In this case, the N�7 alarm is a single consequence ofthese problems and operator can ignore it and he shall first solve thetransmission problems. This alarm is generated for every BSC restart,reset or reload.

See Consequences of an SBL State Change.

When the RTE-REP alarm is ’ON’, the communication with the MSC islost, there is no more possible traffic, the BSC bars automatically allthe cells. When the RTE-REP alarm is ’OFF’, the BSC unbars thecell:- either step by step (by group of access classes)- or in one shot,depending on the parameter T18.


Loss No Yes No No No





[35,2] RTE−REP

Check transmission or reset

ASMB/ASMC

yesN7 system works correctly at

peer side?

no

Alarm persists?

no


Alarmsolved

Alarm persists?

no

yes

yes

yes




4.3 [35,3] INC-REP

specificProblems N7 [35] INC-REP [3]




Alarm Description An incident report is generated whenever the BSC receives a messagewith either a DPC, OPC or an SSF label part different from theexpected one.It is also generated when on changeover/changeback, too many MSUsare received from other DTCs. Excessive incident report generation isavoided 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.


A9130 BSC

Impact on System The SBL state is not changed. See Consequences of an SBL StateChange.


Loss No No No No No





[35,3] INC−REP

yes

N7 system of DPC, OPC

or SSF OK?

no

Alarmsolved

Alarm persists?

no


yes

Solve N7 problem, use N7 monitor

On−site

Replace DTC



5 Class 36: TRUNK Alarms


This section defines the BSC alarms for the Class 36: TRUNK alarm class.



5.1 [36,0] LFA

specificProblems TRUNK [36] LFA [0]


probableCause LossOfFrame


Alarm Description The trunk supervisor detected a loss of frame alignment. This alarm isbasedon received data in channel 0, before re-timing.


Impact on System A loop test is done by the DTC to verify if the failure is internal (FLT)or external (EF).See Consequences of an SBL State Change.


Loss No No No No No

Degradation Yes No No Yes No


[36,0] LFA

yes

Trunk system works correctly at

peer side?

no

Alarmsolved

Alarm persists?

no

yes

Trigger recovery action on peer side and wait until trunk becomes available.





5.2 [36,3] RAI

specificProblems TRUNK [36] RAI [3]


probableCause FarEndReceiverFailure


Alarm Description The DTC (A9120 BSC) or the TP-GSM (A9130 BSC) has detected aRAI (Remote Alarm Indication) on the Trunk.


A9130 BSC

Impact on System Whenever a failure occurs, the trunk is autonomously disabled.Blocking and release of all associated A-channels is carried outdepending on whether the ’ignore 2 Mbit/s flag’ is set.The RAI alarm is generated by the BSC in response to a receivedtransmission alarm, (i.e., LIS, AIS, LFA, EER, BERH). This is the BSCview of transmission, so check for transmission alarms.

Note: On A9120 BSC, a local loop test is done by the DTC to verify ifthe failure is external (EF) or internal (FLT).



Loss Yes No No No No

Degradation No No Yes No No




[36,3] RAI

yes


peer side?

no

Alarmsolved

Alarm persists?

no yes




Transmission alarm (LIS, AIS; LFA,

EER, BERH) events?

yes

no




5.3 [36,4] AIS

specificProblems TRUNK [36] AIS [4]


probableCause Ais


Alarm Description The DTC (A9120 BSC) or the TP-GSM (A9130 BSC) has detected allones indication (AIS, Alarm Indication Signal) on the Trunk: Less thanfour zeros in four consecutive frames means AIS.


A9130 BSC

Impact on System A trunk AIS alarm is detected by the BSC. This is the BSC view oftransmission, so it is important to check for transmission alarms.The trunk is autonomously disabled. Blocking and release of allassociated A-channels is carried outdepending on whether the ignore 2 Mbit/s flag is set or not.

Note: On A9120 BSC, a local loop test is done by the DTC to verify ifthe failure is external (EF) or internal (FLT).




Degradation No No No Yes No




[36,4] AIS

yes


peer side?

no

Alarmsolved

Alarm persists?

no ContactSystem Support

yes

Trigger recovery action on peer side and wait until trunk

becomes available.


Transmission alarm (LIS, AIS; LFA,

EER, BERH) events?

yes

no




5.4 [36,5] SLIP-OV

specificProblems TRUNK [36] SLIP-OV [5]

eventType Equipment

probableCause TimingProblem


Alarm Description The trunk supervisor has detected a slip overrun. An additional signal,DIR, indicates the direction of the slip. An indication will mean that theexternal frequency clock extracted from its own PCM link is greater,external clock faster than the internal frequency clock selected by theBSC.


Impact on System The SBL state remains unchanged. See Consequences of an SBLState Change.


Loss No No No No No





[36,5] SLIP−OV

yes

Transmission board settings

OK?

no

Alarmsolved

Alarm persists?


yes

Correct Transmissionboards settings


Clock or Synchronization alarm

events?

yes

no




5.5 [36,6] SLIP-UN

specificProblems TRUNK [36] SLIP-UN [6]

eventType Equipment



Alarm Description The trunk supervisor has detected slip underrun. A fault is indicatedevery time a slip occurs. An additional signal, DIR, indicates thedirection of the slip. No indication will mean that the external frequencyclock extracted from its own PCM link is less, external clock slowerthan the internal frequency clock selected by the BSC.




Loss No No No No No





[36,6] SLIP−UN

yes

Transmission board settings

OK?

no

Alarmsolved

Alarm persists?

no yes

Correct Transmissionboards settings



Clock or Synchronization alarm

events?

yes

no




5.6 [36,7] LOS

specificProblems TRUNK [36] LOS [7]


probableCause LossOfSignal


Alarm Description The trunk supervisor detected a LOS. Whenever a failure occurs, aloop test is done by the DTC to verify if the failure is internal or external.


Impact on System A local loop test is done to verify if the failure is external (EF) or internal(FLT) by own circuit at the DTC. A-Trunk LOS alarm is detected by theBSC. This is the BSC view of transmission, so check for transmissionalarms. The trunk is autonomously disabled. Blocking and releaseof all associated A-channels is carried out depending on whetherthe ’ignore 2 Mbit/s flag’ is set. See Consequences of an SBL StateChange.







[36,7] LOS

yes


peer side?

no

Alarmsolved

Alarm persists?

no yes




Transmission alarm (LIS, AIS; LFA, EER, BERH)

events?

yes

no




5.7 [36,10] CRCA

specificProblems TRUNK [36] CRCA [10]




Alarm Description This alarm is a quality alarm. It indicates that the number of cyclicredundancy checks reached a certain threshold. The alarm is onlyissued if the fault persists for more than 100[thinsp]ms.


Impact on System A local loop test is done to verify if the failure is external or internal byown circuit at the DTC. When the CRCA threshold has been reached,a mechanism is started to search for the new frame alignment tore-synchronize the trunk. See Consequences of an SBL State Change.







[36,10] CRCA

yes


peer side?

no

Alarmsolved

Alarm persists?

no yes




Transmission alarm (LIS, AIS; LFA, EER, BERH)

events?

yes

no




5.8 [36,11] CHO-EERH

specificProblems TRUNK [36] CHO-EERH [11]


probableCause DegradedSignal


Alarm Description ERRH is bit errors measured on the frame alignment signal. Anexcessive error rate has been detected in CH0 >= 10 E-3. The faultis not necessarily on the submultiplexer. The location depends on thedistribution of channel 0 throughout the transmission system.


Impact on System See Consequences of an SBL State Change.





[36,11] CH0−EERH

yes


peer side?

no

Alarmsolved

Alarm persists?

no yes




Transmission alarm (LIS, AIS; LFA, BERH)

events?

yes

no




5.9 [36,12] CRC4-BERH

specificProblems TRUNK [36] CRC4-BERH [12]


probableCause ExcessiveBER


Alarm Description This alarm indicates that the BER high measurement based on CRC4error detection exceeds 10 E-3.







[36,12] CRC4−BERH

yes


peer side?

no

Alarmsolved

Alarm persists?

no yes




Transmission alarm events?

yes

no




5.10 [36,13] CRC4-BERL

specificProblems TRUNK [36] CRC4-BERL [13]




Alarm Description The BER based on CRC4 error detection exceeded 10 E-6, but wasbelow the rate 10 E-3. The trunk is functioning at an extremely goodrate.




Loss No No No No No



None - the trunk is functioning at an extremely good rate.


6 Class 38: X.25 Alarms


This section defines the BSC alarms for the Class 38: X.25 alarm class.



6.1 [38,0] MODEM-FLT

specificProblems X.25 [38] MODEM-FLT [0]


probableCause CommunicationSubsystemFailure


Alarm Description The modem used in the X.25 connection is faulty, or the local terminalpower is off.


Impact on System An X.25 can connect the BSC to the BSC local terminal or the BSCto the OMC-R. When both X.25 connections become faulty, theconnection between the BSC and the other entity is broken.

If the alarm occurs in relation to the link with the OMC-R, the BSC isof course unable to send the alarm to the OMC-R. However, if a localterminal is connected, the BSC sends the alarm to the terminal.

When the BSC is unable to send an alarm to the OMC-R, the BSC triesrepeatedly to send the alarms BSC_SYNC_REQUEST for BSC alarmsand TSC_BTS_SYNC_REQUEST for TSC and BTS alarms.

When the alarm is eventually received, the OMC-R triggers an alarmaudit for the BSC alarms and an alarm audit for the TSC and BTSalarms. See Consequences of an SBL State Change.


Loss No No No No Yes





[38,0] MODEM−FLT

Alarmsolved

yes

Alarm persists?

no



yesBSC SYNC−REQUEST

alarm events?

noOn−site

Check/repair/replace X.25 connection

On−site

Check/repair/replace X.25 modem

On−site

Check/repower/repair/replace

local BSC terminal




6.2 [38,1] LINK-FLT

specificProblems X.25 [38] LINK-FLT [1]


probableCause CommunicationProtocolError


Alarm Description The X.25 L2 is disconnected, although the L1 can still be present.




Loss No No No No No

Degradation No No No No Yes




[38,1] LINK−FLT

Lock X.25

Unlock X.25

yes

X.25 link works correctly at

peer side?

no

Alarmsolved

Alarm persists?

yes

Trigger recovery action on peer side and wait until

X.25 link becomes available.


Alarm persists?

no

yes

no




6.3 [38,2] PROT

specificProblems X.25 [38] PROT [2]




Alarm Description An X.25 network layer (that is, L3) protocol problem occurred. An X.25protocol problem can be caused by one of the following:: *Secondtimeout on restart confirmation *Second timeout on clear confirmation.




Loss No No No No No





[38,2] PROT

Lock X.25

Unlock X.25

yes

X.25 link works correctly at

peer side?

no

Alarmsolved

Alarm persists?

no

yes

Trigger recovery action on peer side and wait until

X.25 link becomes available.


Alarm persists?

no

yes

Second timeout

on:

clear confirmation

restart confirmation



7 Class 39: BSC-SW-ANOMALY Alarms


This section defines the BSC alarms for the Class 39: BSC-SW-ANOMALYalarm class.



7.1 [39,1] OSN-NON-RECOVERABLE

specificProblems BSC-SW-ANOMALY [39] OSN-NON-RECOVERABLE [1]



perceivedSeverity Indeterminate (MI)

Alarm Description If the function call is not accepted by the OS, then an OSN NonRecoverable Error is generated. The error handler receives a OSNnon-recoverable error. This triggers a processor restart.


A9130 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.


Loss No No No 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 sequencenumber and the user data. The meaning of the user sequence number and theuser data is different for every module.



7.2 [39,3] OSN-PROCEDURAL

specificProblems BSC-SW-ANOMALY [39] OSN-PROCEDURAL [3]




Alarm Description An application request of an OSN primitive was passed to the stackwith incorrect parameters.


A9130 BSC




Loss No No No No No






7.3 [39,5] USR-NONRECOVERABLE

specificProblems BSC-SW-ANOMALY [39] USR-NONRECOVERABLE [5]




Alarm Description An application has generated a software error indicating a fault whichdoes not cause a malfunction. Subsequently, further errors havebeen detected which cause the software to malfunction, a User NonRecoverable Error is generated. The processor is restarted.


A9130 BSC

Impact on System The SBL state remains unchanged.The impact depends on the processor type. See Processor Restart[33,0].



Loss No No No No No






7.4 [39,7] HWR-NONRECOVERABLE

specificProblems BSC-SW-ANOMALY [39] HWR-NONRECOVERABLE [7]

eventType Equipment



Alarm Description The error handler received information concerning a hardwarenon-recoverable error.


A9130 BSC

Impact on System The SBL state remains unchanged.The impact depends on the processor type. See Processor Restart[33,0].



Loss No No No No No






7.5 [39,18] SANITY-TIMER

specificProblems BSC-SW-ANOMALY [39] SANITY-TIMER [18]




Alarm Description A hardware sanity timer NMI expired. This is because an applicationhas run too long or is running in a loop. This causes the processor toreload.


Impact on System Expiration of the sanity timer caused a processor reload. All ongoingtransactions through the processors are released in a controlledmanner towards the MSC, with WTC. The impact depends on theprocessor type. See Processor Restart [33,0]. See Consequencesof an SBL State Change.


Loss No No No No No





8 Class 42: TELECOM Alarms


This section defines the BSC alarms for the Class 42: TELECOM alarm class.



8.1 [42,1] NACK-MSC

specificProblems TELECOM [42] NACK-MSC [1]




Alarm Description The BSC did not receive a RESET ACK message from the MSC beforeexpiration of timer T4.


A9130 BSC

Impact on System The SBL state remains unchanged. See Consequences of an SBLState Change. The BSC repeats the reset procedure indefinitely untilthe MSC sends a positive acknowledgment.


Loss No No No No No





[42,1] NACK−MSC

yesRESET and RESET_ACK message events?

no

Alarmsolved

Alarm persists?

no


yes

Repair/replace N7 component


N7 alarm events?yes

no

On−site




8.2 [42,2] OVERLOAD-MSC

specificProblems TELECOM [42] OVERLOAD-MSC [2]

eventType Quality of Service

probableCause Congestion


Alarm Description An overload message was received from the MSC and this triggeredan overload reaction.

While timer T5 remains activated after receipt of an overload message,it inhibits the effect of any further overload messages. When timer T5expires, overload messages provoke traffic reduction again.


A9130 BSC

Impact on System The SBL state remains unchanged. Traffic is reduced; at least oneuser class is barred in all cells. See Consequences of an SBL StateChange.


Loss No No No No No

Degradation No Yes No Yes No


None - an autonomous overload reaction is triggered.



8.3 [42,3] START-RESET

specificProblems TELECOM [42] START-RESET [3]




Alarm Description A reset procedure has started in the BSC. The alarm indicates whetherthe reset is requested by the MSC, or if the reset was due to loss ofcommunication with the MSC, (i.e., timer TI expired in the BSC).


A9130 BSC

Impact on System The SBL state remains unchanged. All calls are cleared in the BSC.See Consequences of an SBL State Change.


Loss No No No Yes No





[42,3] START−RESET

Alarmsolved

Alarm persists?

no


yes

Trigger action on MSC side


Local communication alarm events?

yes

no




8.4 [42,7] NO-RESET-CIC

specificProblems TELECOM [42] NO-RESET-CIC [7]




Alarm Description The BSC requested the reset of a CIC towards the MSC. This resetrequest is attempted a predefined number of times. If, following themaximum number of retries, the BSC still has not received the RESETCIC ACK, then this alarm is issued.


A9130 BSC

Impact on System The SBL state remains unchanged. This A-channel is releasedinternally by the BSC. See Consequences of an SBL State Change.


Loss No No No No No





[42,7] NO−RESET−CIC

Alarmsolved

Alarm persists?

no


yes

Trigger CIC recovery action at MSC side


Transmission or trunk alarm events?

yes

no




8.5 [42,9] OVERLOAD-BSC

specificProblems TELECOM [42] OVERLOAD-BSC [9]

eventType Equipment

probableCause ProcessorProblem


Alarm Description This alarm is sent by the BSC to report an BSC processor overload.


A9130 BSC

Impact on System The SBL state remains unchanged. The BSC is overloaded. SeeConsequences of an SBL State Change.


Loss No No No No No



[42,9] OVERLOAD−BSC



Processor related board alarm

events?

yes

no




8.6 [42,12] TEL-PAIR-LOST

specificProblems TELECOM [42] TEL-PAIR-LOST [12]

eventType Equipment



Alarm Description This is the ID of the TCH-DTC pair lost.


Impact on System This alarm is issued because there happened a state change of oneDTC.Since the TCH-DTC pairs handles calls, all calls handled by this pairare lost and all cells managed by this pair cannot anymore establishcalls. All these cells are disabled.


Loss No Yes No Yes No





[42,12] TEL−PAIR−LOST

yes

Alarm persists?

no


Lock reported DTC

On−site

Replacereported faulty DTC

Testreported DTC

Verifyreported DTC

Unlock reported DTC

Alarmsolved

yes

Alarm persists?

no

Any DTC was reset?no

Wait for DTC restart

Alarm persists?

yes

Alarmsolved

yes

no




8.7 [42,13] BSC-TRAFFIC-REPORT

specificProblems TELECOM [42] BSC-TRAFFIC-REPORT [13]




Alarm Description Sent by the BSC when: * An MSC_OVERLOAD/BSC_OVERLOADis received and no BSS actions are running. * AnMSC_OVERLOAD/BSC_OVERLOAD is received and BSSactions are running, but filter timer T17 is not running. * Following asystem action: SW activate, BSC restart, the traffic has been reducedand is now increased step by step at each expiry of timer T18. * TheRACH parameters are changed on the system level (BSS RACH).


A9130 BSC

Impact on System The SBL state remains unchanged. MSs belonging to the barredaccess classes can no longer access the system. This corresponds toa modification of the barred MS classes (either increase, or decrease).Additionnal info give the current status.


Loss No No No No No





[42,13] BSC−TRAFFIC−REPORT

Alarmsolved

Alarm persists?

no


yes

Analyze additional information bytes


Related alarm events?

yes

no




8.8 [42,14] GPRS-RESET

specificProblems TELECOM [42] GPRS-RESET [14]




Alarm Description This alarm is used when a RESET command arrives from the MFS orwhen all GSL, all GPRS application process or TCH-RM pairs aredown. A RESET can also occur in the case of an excessive amount oflack of acknowledgments between the MFS and the BSC. To get theorigin of the GPRS reset, the alarm number shall reflect the origin , inthe following way:0. Resumed reset due to S_CPR take-over, original trigger is unknown1. All GSL links are down (detected by TSM_GPRS)2. No DTC GPRSAP available (very unprobable)or all GSL links aredown(detected by GPRSAP/GOM ) (TSM_GPRS receives message1260 ),3. Lack of acknowledgment received from MFS on some specialBSCGP messages(BSS TRAFFIC CONTROL after 2 repetitions).4. Loss of a pair of TCH_RM5. RESET triggered by MFS. (This covers the BSC RESET triggeredby MFS following BSC SW activation, or a BSC reset as MFS seesloss of GSL for a while, or a BSC RESET when MFS can not receiveacknowledement on some special BSCGP message,even after severalrepetitions) This alarm is used when a reset command arrives from theMFS, or when the BSC sends a reset command to the MFS becauseall GSL, or all GPRS application processes, or a TCH_RM pair is/aredown.


A9130 BSC

Impact on System The SBL state remains unchanged. A reset of the MFS affects GPRSfunctionality only.


Loss No No No No No

Degradation No No Yes Yes Yes


None - an autonomous reset is triggered.


9 Class 43: CELL Alarms


This section defines the BSC alarms for the Class 43: CELL alarm class.



9.1 [43,0] LOSS-OF-BCCH

specificProblems CELL [43] LOSS-OF-BCCH [0]



perceivedSeverity Major (PMA), Warning if out of commercial use

Alarm Description The transceiver time slot configured to carry the BCCH is unavailablefor telecommunication purposes.


A9130 BSC

Impact on System A BCCH must exist for each cell in order to transmit system informationto the MS. This enables the MS to assign calls within the cell. Sincethe BCCH is no longer able to transmit system information, calls arenot assigned in the cell. A BCCH channel can be lost when equipmentcarrying a BCCH fails or is disabled. The BTS-TEL is FIT and athree-minute timer is started to allow the Frame Unit to reload. Ifthe 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 involvesreconfiguration of another channel as a BCCH, at the expense of thecurrentconfiguration of the channel. Recovery means blocking/unblockingaction, stateupdate and perhaps a reconfiguration action (if redundant resourcesare available).When the BCCH is recovered, another alarm is generated for the lostchannel involved in the reconfiguration. When the Loss of BCCH alarmis active, no other cell type alarm is sent for this cell to indicate furtherloss or gain of channels. This continues unless the BCCH channelbecomes available. See Consequences of an SBL State Change.


Loss No Yes Yes Yes No





[43,0] BSC−TRAFFIC−REPORT

Alarmsolved

Alarm persists?

no


yes


Trigger maintenance action on that alarm(s)

RelatedBTS alarm events?

yes

no




9.2 [43,1] LOSS-OF-SDCCH

specificProblems CELL [43] LOSS-OF-SDCCH [1]



perceivedSeverity Minor (DMA), Warning if out of commercial use

Alarm Description One or more transmission time slots configured to carry the SDCCHare unavailable for telecommunication purposes.


A9130 BSC

Impact on System Loss of the SDCCH leads to a decrease in call setup and handovercapacity,fewer numbers of SDCCHs are available to handle call setup andhandover.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 toSDCCH.Since the SDCCH is a vital resource, recovery must be attempted.This involves reconfiguration of another channel as an SDCCH, at theexpense of the current configuration of the channel. Recovery meansblocking/unblocking action, state update and perhaps a reconfigurationaction (if redundant resources are available). When the SDCCH isrecovered, another alarm is generated for the lost channel involved inthe reconfiguration. See Consequences of an SBL StateChange.


Loss No No No No No

Degradation No Yes Yes Yes No




[43,1] LOSS−OF−SDCCH

Alarmsolved

Alarm persists?

no


yes



RelatedBTS alarm

events?

yes

no




9.3 [43,2] LOSS-OF-TCH

specificProblems CELL [43] LOSS-OF-TCH [2]




Alarm Description One or more transceiver time slots configured to carry the TCH areunavailable for telecommunication purposes.


A9130 BSC

Impact on System Loss of a TCH leads to a decrease in traffic capacity as there are feweravailable TCHs to carry calls.A TCH might be lost due to a successful recovery of the TRX/TCUwhere the TCH channels are configured.The loss of TCHs channels activates only the blocking part of recovery,with no reconfiguration. See Consequences of an SBL State Change.


Loss No No No No No

Degradation No Yes No Yes No




[43,2] LOSS−OF−TCH

Alarmsolved

Alarm persists?

no


yes



RelatedBTS alarm

events?

yes

no




9.4 [43,3] LOSS-OF-ALL-CHAN

specificProblems CELL [43] LOSS-OF-ALL-CHAN [3]




Alarm Description All transceiver time slots of a BTS are unavailable for telecommunicationpurposes.The alarm condition is a begin or an end, never an event.This alarm is generated in the following circumstances:*The BTS-TEL goes to FLT due to a configuration failure, (i.e., BTS-OM= FLT)*All the RSLs go faulty, SBL BTS-TEL is set to FLT.Loss of all channels can also result from the BTS-OM link becomingFLT/FOS. This causes the BTS-TEL to go to FLT when configurationdata is sent to the BTS.


A9130 BSC

Impact on System All channels in the cell are unavailable. If configuration data cannotbe sent to the BTS, or BTS-TEL is FLT, the cell is barred. A MobileStationnever selects this cell for call setup; there is no call handling in the cell.When the BCCH alarm is active no other cell type alarm is sent for thiscell toindicate further loss or gain of channels. This continues unless theBCCHchannel becomes available.See Consequences of an SBL State Change.


Loss No Yes No Yes Yes





[43,3] LOSS−OF−ALL−CHAN

Alarmsolved

Alarm persists?

no


yes

LockBTS−OM

Trigger maintenance action on that

alarm(s)

Related BTS alarm events?

yes

no

UnlockBTS−OM

All RSLs in BTS faulty?

yes

no

RESET BTS for reconfiguration




9.5 [43,4] CELL-TRAFFIC-REPORT

specificProblems CELL [43] CELL-TRAFFIC-REPORT [4]




Alarm Description Sent by the BSC when: *A BTS_OVERLOAD message is receivedfrom a BCCH transceiver *A BTS_OVERLOAD message is receivedfrom a non-BCCH transceiver and the leaky-bucket counter overflows*A TCU processor overload is detected in case of A9120 BSC*There is a change of the RACH parameters on cell level (dynamicRACH).


A9130 BSC

Impact on System The SBL state remains unchanged.MSs belonging to the barred access classes can no longer access thesystem.See Consequences of an SBL State Change.


Loss No No No No No





[43,4] CELL−TRAFFIC−REPORT

Alarmsolved

Alarm persists?


yes



Related BTS alarm events?

yes

no

BTS−OVERLOAD alarm coming

from BCCH TRX?

yes

no

ReduceBTS load

Solve that alarm(s)

TCU processor overload

alarm events?*

yes

Correct RACH parameters

Dynamic RACH parameters on

cell level OK?

no

no

yes

no




9.6 [43,5] OVERLOAD-BTS

specificProblems CELL [43] OVERLOAD-BTS [5]




Alarm Description Sent by the BSC to report a change in the overall BTS telecom activity.It is sent when a BTS_OVERLOAD message is received and the timerT1 is not running.


A9130 BSC

Impact on System The SBL state remains unchanged.MSs belonging to the barred access classes can no longer access thesystem.See Consequences of an SBL State Change.


Loss No No No No No





[43,5] OVERLOAD−BTS

Alarmsolved

Alarm persists?

no


yes

Trigger maintenance action on that

alarm(s)

RelatedBTS alarm

events?

yes

no

Solve that alarm(s)

TCU alarm events?

yes

no




9.7 [43,248] CONFIGURED POOLS NOT FULLY USABLE

specificProblems CELL [43] CONFIGURED POOLS NOT FULLY USABLE [248]


probableCause performanceDegraded


Alarm Description Cell is degraded, in HSDS at least one EXTS is lost.This problem can be caused by one of the following:* Any pool mapped to non-IT second Abis, HSDS state is changed toDegraded* 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 ischanged to Partially Degraded* There is at least one pool of type greater than 2 which is linked toa Evolium A9100 TRE, the pool has to be truncated. HSDS state ischanged 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.


A9130 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.


Loss No No No No No

Degradation No Yes No No No




HSDS state is degraded?

TCU that any pool

mapped to is IT?

Alarm persists?

[43,248] CONFIGURED POOLS NOT [FULLY] USABLE

None

Check the second Abis that any

pools mapped to

Check for TCU problem

Contact System Support

Alarm solved

yes

no

yes

yes

no

no



10 Class 44: BTS-OM Alarms


This section defines the BSC alarms for the Class 44: BTS-OM alarm class.



10.1 [44,0] AUDIT-FAIL

specificProblems BTS-OM [44] AUDIT-FAIL [0]




Alarm Description A failure occurs in the BSC-BTS audit. A failure in the BSC-BTS Auditscenario is considered to be any failure occurring between the requestfor an Audit from the BSC and reception of the Conf_compl messagefrom the BTS. This Alarm is never sent as a result of no reception ofAn ACK. This alarm is also sent when CDM sending fails in cases NOTunder software activation and reconfiguration, i.e. OMU restart, CDMsending on logical data change, etc.


A9130 BSC

Impact on System When BTS-OM is FLT but OML is up, the BSC triggers an audit everytwo minutes until one succeeds. The BTS still handles calls, but ifa reconfiguration occurs and the BTS-OM is FLT, BTS-TEL goes toFLT. The message OMU started, indicating that the BTS (OMU) hasauto-reset, can result in a new BTS/OMU downloading scenario. In theevent of a successful download, the BTS-OM becomes IT. When theBTS-OM goes from FLT to IT due to success of a BSC-BTS audit, orreset BTS/OMU, an alarm END for all alarm types audit failure is sent.See Consequences of an SBL State Change.







[44,0] AUDIT−FAIL

Alarmsolved

Alarm persists?

no


yes

Reset BTS or OML TCU

OML up?yesno No operator

action required




10.2 [44,1] PROTOCOL-FAIL

specificProblems BTS-OM [44] PROTOCOL-FAIL [1]




Alarm Description A protocol failure on the Abis interface occurred. An ’ACK’ to somemessage was not received after three retries.


A9130 BSC

Impact on System When the BTS-OM is FLT but OML is up, the BSC triggers an auditevery two minutes until one succeeds. The BTS still handles calls, butif a reconfiguration occurs and BTS-OM is FLT, BTS-TEL goes to FLT.

The message OMU started, indicating that the BTS (OMU) has autoreset, can result in a new BTS/OMU download scenario. In theevent of a successful download, the BTS-OM becomes IT. When theBTS-OM goes from FLT to IT due to success of a BSC-BTS audit, orBTS/OMU reset, an END for all alarm types ’protocol failure’ is sent.See Consequences of an SBL State Change.





[44,1] PROTOCOL−FAIL

Alarmsolved

Alarm persists?


yes


OML up?yesno No operator

action required




10.3 [44,2] RECONFIG-FAIL

specificProblems BTS-OM [44] RECONFIG-FAIL [2]


probableCause ConfigurationOrCustomizationError


Alarm Description This alarm is sent as a result of a failure to do a required reconfigurationaction, triggered due to loss of vital resources or due to failure inconveying CDM to the BTS.


A9130 BSC

Impact on System When the BTS-OM is FLT but OML is up, the BSC triggers an auditevery two minutes until one succeeds. The BTS still handles calls,but if a reconfiguration occurs and BTS-OM is FLT, BTS-TEL goesto FLT. The message ‘OMU started’, indicating that BTS (OMU) hasauto-reset, can result in a new BTS/OMU download scenario. In theevent of a successful download, the BTS-OM becomes IT. WhenBTS-OM goes from FLT to IT due to success of a BSC-BTS audit, orBTS/OMU reset, an alarm ’END’ for all alarm types ’Reconfig_failure’is sent. See Consequences of an SBL State Change.







[44,2] RECONFIG−FAIL

Alarmsolved

Alarm persists?

no


yes


OML up?

yes

no

No operator action required




10.4 [44,3] DOWNLOAD-FAIL

specificProblems BTS-OM [44] DOWNLOAD-FAIL [3]




Alarm Description Three download attempts failed. Any failure fromBTS-DOWNLOAD-REQ until a successful BTS-DOWNLOAD-REPis considered a download failure.


A9130 BSC

Impact on System The OMU updates the BTS-OM to FOS after three download attemptsby the BSC have failed (i.e., BTS-DOWNLOAD-REQ until a successfulBTS-DOWNLOAD-REP). See Consequences of an SBL State Change.







[44,3] DOWNLOAD−FAIL

Alarm persists?

no


yes

Check files on standby CPR disk

BTS or OMU restart events?

yes

no

Lock BTS−OM

Unlock BTS−OM

Reload correct data file from software package

Data files on standby CPR

disk ok?

yes

no

Alarmsolved

Alarm persists?

no

yes




10.5 [44,5] SW-ACTIVATE-FAIL

specificProblems BTS-OM [44] SW-ACTIVATE-FAIL [5]




Alarm Description This configuration failure alarm indicates that a software activationfailed following a download attempt.


A9130 BSC

Impact on System If the software activation failure requires operator intervention, BTS-OMgoes to FOS. Otherwise, it goes to FLT. See Consequences of an SBLState Change.







[44,5] SW−ACTIVATE−FAIL

Alarmsolved

Alarm persists?

no


yes

Correct BTS hardware or CPR hawrdware data

BTS hardware corresponds to hardware

data on standby CPR disk?

yes

no

Lock BTS−OM

Unlock BTS−OM

Alarm persists?

no

yes




10.6 [44,6] CONFIG-DATA-FAIL

specificProblems BTS-OM [44] CONFIG-DATA-FAIL [6]




Alarm Description There is a problem with the configuration data because of a logicalparameter modification or the restart of the BTS or OMU.


A9130 BSC








[44,6] CONFIG−DATA−FAIL

Alarmsolved

Alarm persists?

no


yes


BTS/OMU restarts?

Data files on standby CPR

disk ok?

yes

no

Logical parametersmodified?

no

yes

Logical parameters are valid?

no

yes

Reload correct data file from software package

yes

no

Lock BTS−OM

Unlock BTS−OM




10.7 [44,7] OMU-SELFTEST-FAIL

specificProblems BTS-OM [44] OMU-SELFTEST-FAIL [7]

eventType Equipment



Alarm Description The OMU failed its self-test.


A9130 BSC








[44,7] OML−SELFTEST−FAIL

Alarmsolved

yes

Alarm persists?

no


Lock BTS−OM

On−site

G2: Replacereported faulty OMU

Unlock BTS−OM

Alarmsolved

yes

Alarm persists?

no




10.8 [44,10] ABORT-FAIL

specificProblems BTS-OM [44] ABORT-FAIL [10]




Alarm Description The Abort failure alarm indicates that the attempt to remove thepreloaded BTS software files has failed.


A9130 BSC



Loss No No No No No



[44,10] ABORT−FAIL


Retrigger remove action

Alarmsolved

yes

Alarm persists?

no




10.9 [44,11] PRELOAD-FAIL

specificProblems BTS-OM [44] PRELOAD-FAIL [11]




Alarm Description This alarm indicates that preloading of the BTS software has failed.


A9130 BSC



Loss No No No No No




10.10 [44,12] BTS-HW-CONFIG-FAIL

specificProblems BTS-OM [44] BTS-HW-CONFIG-FAIL [12]

eventType Equipment



Alarm Description This alarm indicates that the BTS extension/reduction has failed due arestriction in the BTS-HW. During an audit, added or removed TREsare detected and reported to the BSC. If the Auto-alloc flag is set onthe Abis, the BSC will attempt to allocate TCUs and TSs. This can fail,if the BTS is created with certain characteristics and the BTS cannotsupport these characteristics.


A9130 BSC



Loss No No No No No



[44,12] BTS−HW−CONFIG−FAIL


Correct characteristics

BTS characteristic

correspond to BTS HW capabilities

files?

yes

no


Alarmsolved

Alarm persists?

no

yes



11 Class 45: CHANNEL Alarms


This section defines the BSC alarms for the Class 45: CHANNEL alarm class.



11.1 [45,0] CH-UNBLOCK-FAIL

specificProblems CHANNEL [45] CH-UNBLOCK-FAIL [0]




Alarm Description A timeout expired for the MSC to send an acknowledgement to theBSC in response to an A-channel unblocking message.


A9130 BSC



Loss No No No No No

Degradation Yes No Yes Yes No




[45,0] CH−UNBLOCK−FAIL

Lock ACH Unlock ACH


N7 links operational?

no

yes

Repair/replace N7 equipment

Trigger N7 checks at MSC side

Alarmsolved

Alarm persists?

no

yes

On−site

Alarmsolved

Alarm persists?

no

yes

Alarmsolved

Alarm persists?

no

yes




11.2 [45,1] CH-BLOCK-FAIL

specificProblems CHANNEL [45] CH-BLOCK-FAIL [1]




Alarm Description A timeout expired for the MSC to send an acknowledgement to theBSC in response to an A-channel blocking message.


A9130 BSC



Loss No No No No No





[45,1] CH−BLOCK−FAIL

Lock ACH Unlock ACH


N7 links operational?

no

yes

Repair/replace N7 equipment

Trigger N7 checks at MSC side

Alarmsolved

Alarm persists?

no

yes

On−site

Alarmsolved

Alarm persists?

no

yes

Alarmsolved

Alarm persists?

no

yes




11.3 [45,2] BSC-CIC-UNKNOWN

specificProblems CHANNEL [45] BSC-CIC-UNKNOWN [2]




Alarm Description This alarm is sent out in response to a request initiated by theBSC which specifies a circuit which is not equipped in the MSC. Onreception of an unequipped circuit message from the BSC, the MSCshould remove the indicated circuits from further selection.


A9130 BSC

Impact on System The SBL state remains unchanged. A database inconsistency existswhich could cause problems at a later stage. This fault is for oneA-channel, although there is a strong possibility that faults exist onother A-channels at the A Interface. On reception of an unequippedcircuit message from the BSC, the MSC removes the indicated circuitsfrom further selection. See Consequences of an SBL State Change.


Loss No No No No No





[45,2] BSC−CIC−UNKNOWN

Lock assoc. A−trunk

Unlock assoc. A−trunk to bring ACH back in service,

as faults can exist for other A−channels on A−trunk


Alarmsolved

Alarm persists?

no

yes




11.4 [45,3] MSC-CIC-UNKNOWN

specificProblems CHANNEL [45] MSC-CIC-UNKNOWN [3]




Alarm Description The MSC initiated a request. The request specifies a circuit which isunequipped in the BSC.


A9130 BSC

Impact on System The SBL state remains unchanged. If the circuit indicated in themessage is not equipped in the BSC, the BSC ignores the circuit.The BSC does not make any response to the circuit and refuses therequest 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 * BSCknows the circuit but recognizes it as not equipped * DTC controllingthe circuit is faulty and the response MSC-CIC-UNKNOWN is notsent. A database inconsistency exists which can cause problems at alater stage. This fault is for one A-channel, although there is a strongpossibility that faults exist on other A-channels at the A Interface. SeeConsequences of an SBL State Change.


Loss No No No No No





[45,3] MSC−CIC−UNKNOWN

Lock aossc. A−trunk




Alarmsolved

Alarm persists?

no

yes




11.5 [45,4] END-OF-REP-OF-UNBLOCK-PROC

specificProblems CHANNEL [45] END-OF-REP-OF-UNBLOCK-PROC [4]




Alarm Description The number of unblock requests exceeded a predefined number ofallowable attempts (i.e. 255).


A9130 BSC



Loss No No No No No



[45,4] END−OF−REP−OF−UBLOCK−PROC

Lock aossc. ACH




Alarmsolved

Alarm persists?

no

yes



12 Class 46: BACKUP-MEDIUM Alarms


This section defines the BSC alarms for the Class 46: BACKUP-MEDIUMalarm class.



12.1 [46,0] SYNC CORRUPTED

specificProblems BACKUP-MEDIUM [46] SYNC CORRUPTED [0]




Alarm Description A processor restart has occurred before the twin fiIe is closed during atwinupdate. The Active CPRA will detect that the twin file was not closedproperlybefore the report. The twin file status is changed to synchronizedcorruptedand the alarm SYNC_CORR is generated.


Impact on System The SBL state remains unchanged. Telecom functions are notaffected, but PM is impacted. CPRA (Duplex/Simplex) - PerformanceManagement: When a twin file is being extended, the extendedpart is lost because the twin file was not properly closed. If the twinfile is a PM file, the last performance information can be lost. SeeConsequences of an SBL State Change.


Loss No No No No No



None - wait for the next twin file update.

See Other BSC Alarms (Section 34.4) for the byte definition.



12.2 [46,1] UNSYNC-OTHER-CORR

specificProblems BACKUP-MEDIUM [46] UNSYNC-OTHER-CORR [1]




Alarm Description This alarm occurs when the twin file on the own CPRA is notsynchronized and a twin file update is successful on the own CPRAbut failed on the other CPRA. The twin file status is changed tounsynchronized other corrupted and the alarm UNSYN_OTHER_C isgenerated.


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 standbyCPRA is synchronized as fast as possible, although a small delaydoes exist. If a restart occurs now on the active CPRA (databaseupdate was completely done), it is possible that not all the updates areforwarded to the standby. The standby CPRA now becomes activeand detects that the tais not yet completely available. The new activeCPRA then tries to retrieve the missing data, from its mate. This takestime, because it has to wait until its mate is running again. When thisis done, the databases are again synchronized. If, in the meantime,a database update arrives on a new active CPR, then this update isdone, although the missing data has still not been retrieved from themate CPRA. This is necessary; otherwise all the applications are heldup until the mate CPRA is running. If the latter has a hard failure, itnever becomes available. When the missing data is not retrieved fromits mate, the database/disk subsystem generates an alarm unsyncother corrupted. It forces the new standby CPR to synchronize with thenew active CPRA, whenever it comes on line. The missing data is lostand all other modified data on the active CPRA is synchronized withthe standby CPRA. CPRA (SIMPLEX) If the CPRA runs in simplex, thisalarm is never issued. See Consequences of an SBL State Change.


Loss – – – – –

Degradation – – – – Yes




[46,1] UNSYNC−OTHER−CORR

Resynchronize OMC−R with BSC by

performing an audit

Repeat the lost transactions

Alarmsolved

yes

Alarm persists?

no





12.3 [46,4] SECFILE-ROLLBACK

specificProblems BACKUP-MEDIUM [46] SECFILE-ROLLBACK [4]




Alarm Description An open transaction was found in the security file during initialization.This means that a transaction requiring several updates of thedatabase was interrupted by a hardware fault, software fault, takeoveror a CPRA reload. The BSC performs a rollback of the transaction.


Impact on System The SBL state remains unchanged. Telecom functions are notaffected, but Configuration Management is impacted. ConfigurationManagement: The interrupted transaction is lost as the BSC returnedto its previous state. The OMC-R operator may have received anegative acknowledgement to his request for the modification of alogical parameter/action on software/database replacement. SeeConsequences of an SBL State Change.


Loss – – – – –





[46,4] SECFILE−ROLLBACK

Resynchronize OMC−R with BSC by

performing an audit

Repeat the lost transactions

Alarmsolved

yes

Alarm persists?

no


yesNACKs

received on operator requests?

no

Repeat the operator request




12.4 [46,5] SINGLE-UPD-ROLLBACK

specificProblems BACKUP-MEDIUM [46] SINGLE-UPD-ROLLBACK [5]




Alarm Description When a single update fails and security is requested, the application isinformed that the update failed and a rollback is done, to retrieve theold/original values. If the rollback cannot be executed, then an alarmsingle rollback failure is generated.


Impact on System The SBL state remains unchanged. This failure is also issuedwhenever the CPRA runs in simplex. Telecom functions are notaffected, but Configuration Management is impacted. ConfigurationManagement: The interrupted transaction is lost as the BSC attemptsto return to its previous state. The OMC-R operator may havereceived a negative acknowledgement to his request for modificationof logical parameter/action on software/database replacement. SeeConsequences of an SBL State Change.


Loss – – – – –





[46,5] SINGLE−UPD−ROLLBACK

Re−trigger the update

Run Software/database with old DLS/values

Alarmsolved

yes

Alarm persists?

no


yes

Alarm persists?

no Alarmsolved




12.5 [46,6] DUT-ROLLBACK-FAIL

specificProblems BACKUP-MEDIUM [46] DUT-ROLLBACK-FAIL [6]




Alarm Description A series of database updates can be done simultaneously with anapplication and can start a data-update-transaction. By this request,the security system is enabled and all the old/new database valuesare stored in a security file. This transaction is started and endedby the application. If the application receives a successful end oftransaction, then all the updates are correctly executed and consistent.If something goes wrong during this transaction, then a rollback isexecuted over all the modified data relations. The user is informedabout the unsuccessful database updates. If due to some reason,the user cannot be informed about this rollback action, then an alarmDUT_RLB_FAIL is generated.When this failure occurs, the subsequent alarm will be generated whenthe CPRA runs in simplex.


Impact on System The SBL state remains unchanged. Telecom functions are not affected.Configuration Management: The interrupted transaction is lost as theBSC attempts to return to its previous state. The OMC-R operatormay have received a negative acknowledgement to his requestfor modification of logical parameter/action on software/databasereplacement. See Consequences of an SBL State Change.


Loss – – – – –





[46,6] DUT−ROLLBACK−FAIL

Re−trigger the data update


yes

Alarm persists?

no Alarmsolved




12.6 [46,7] DISC-OOS

specificProblems BACKUP-MEDIUM [46] DISC-OOS [7]

eventType Equipment

probableCause InputOutputDeviceError


Alarm Description During a restart/reload/reboot, the SSD on the standby S-CPRA orO-CPRA was checked and found to be unformatted.


Impact on System Telecom functions are not affected. See Consequences of an SBLState Change.


Loss – – – – –





[46,7] DISC−OOS

yes

Alarm persists?


Reformat SSD on S−CPRA

or O−CPRA

On−site

Replace suspected CPR

Copy all files from active to standby CPRA

Alarmsolved

yes

Alarm occurs often for a specific DISK?

no

no

Lock/unlock the disk from

OMC−R

Alarm persists?

yes

Alarmsolved

no




12.7 [46,8] DISC-PARITY-ERROR

specificProblems BACKUP-MEDIUM [46] DISC-PARITY-ERROR [8]

eventType Equipment

probableCause InputOutputDeviceError


Alarm Description During a restart/reload/reboot, the SSD on the standby S-CPRA waschecked and a parity error was detected.


Impact on System Telecom functions are not affected. See Consequences of an SBLState Change.


Loss – – – – –





[46,8] DISC−PARITY−ERROR

yes

Alarm persists?

no


Reformat SSD on S−CPRA

On−site

Replace suspected CPR

Initialize DISK

Alarmsolved

yes

Alarm occurs often for a specific DISK?

no



13 Class 47: GLOBAL-BSC Alarms


This section defines the BSC alarms for the Class 47: GLOBAL-BSC alarmclass.



13.1 [47,2] AUTO-BSC-RESET

specificProblems GLOBAL-BSC [47] AUTO-BSC-RESET [2]




Alarm Description An autonomous reboot/reset of the BSC occurred. The alarm is alwayssent to both the OMC-R and the local terminal.


A9130 BSC

Impact on System The SBL state remains unchanged.The impact depends on what has occurred, as described above. SeeProcessor Reset [33,1].


Loss No No No No No



None - this information is always sent after an autonomous reboot/reset ofthe BSC.



13.2 [47,3] AUTO-BSC-RESTART

specificProblems GLOBAL-BSC [47] AUTO-BSC-RESTART [3]




Alarm Description The BSC was successfully restarted from the OMC-R or BSC localterminal.


A9130 BSC

Impact on System The SBL state remains unchanged.The impact depends on what has occurred, as described above. Seeprocessor restart [33,0].


Loss No No No No No



None - this information is always sent after an autonomous restart of the BSC.



13.3 [47,4] BSC-SYNC-REQ

specificProblems GLOBAL-BSC [47] BSC-SYNC-REQ [4]




Alarm Description All BSC alarms are stored on one I/O queue. A BSC Sync Request isonly sent if the BSC I/O own queue overflow occurs.An overflow may occur on an OMC-R interface if:* There is no OSI CPRA* The X.25 link for A9120 BSC or the Ethernet link for A9130 BSC isdown* The OMC-R is not active.


A9130 BSC



Loss No No No No No



None - on reception of the alarm, the OMC-R starts a BSC alarm audit.



13.4 [47,5] BTS-SYNC-REQ

specificProblems GLOBAL-BSC [47] BTS-SYNC-REQ [5]




Alarm Description An overflow may occur on an OMC-R interface if:* There is no OSI CPRA* The X.25 link for A9120 BSC or the Ethernet link for A9130 BSC isdown* The OMC-R is not active.


A9130 BSC



Loss No No No No No



None - on reception of the alarm, the OMC-R starts a BTS alarm audit.



13.5 [47,6] AUDIT-COMPLETED

specificProblems GLOBAL-BSC [47] AUDIT-COMPLETED [6]




Alarm Description The BSC was successfully reset or restarted from the OMC-R or BSClocal terminal.


A9130 BSC

Impact on System The SBL state remains unchanged.The impact depends on what has occurred, as described above. SeeProcessor Reset [33,1].


Loss No No No No No



None - this information is always sent after an successful reset or restart ofthe BSC.



13.6 [47,7] BSC-HW-RESYNC

specificProblems GLOBAL-BSC [47] BSC-HW-RESYNC [7]

eventType Equipment

probableCause Indeterminate


Alarm Description This alarm is generated after BSC extension or reduction. The BSCsends this alarm to the OMC-R.


A9130 BSC



Loss No No No No No



None - on reception of the alarm, the OMC-R triggers audits to resynchronizewith the BSC.



13.7 [47,8] AIFL-FULL

specificProblems GLOBAL-BSC [47] AIFL-FULL [8]

eventType Equipment



Alarm Description The BSC alarms list is full.




Loss No No No No No



[47,8] AIFL−FULL

Solve remaining alarms


System generates too

many alarms in short time period?

no

yes

Alarmsolved




13.8 [47,9] CBC-CONNECTION-FAILURE

specificProblems GLOBAL-BSC [47] CBC-CONNECTION-FAILURE [9]

eventType Equipment



Alarm Description The alarm is generated when there is a problem with the connectiontowards the CBC.


A9130 BSC



Loss No No No No No





[47,9] CBC−CONNECTION−FAILURE

Solve X.25 alarm(s) first

Correct X.25 parameters


X.25 parameters

OK?

no

yes

Repair/replace X.25 equipment

X.25 alarm events?

no

yes

On−site

Alarmsolved

Alarm persists?

no

yes

Alarmsolved

Alarm persists?

no

yes

X.25 links

operational?

no

yes




13.9 [47,11] ABIS-TS-ALLOC-FAILED

specificProblems GLOBAL-BSC [47] ABIS-TS-ALLOC-FAILED [11]




Alarm Description This alarm is raised to indicate that TS allocation in the case ofauto-detection of a TRE has failed.


A9130 BSC

Impact on System The SBL state remains unchanged.The TRE detected via the Audit will not be operational, no TSs willbe allocated.


Loss No No No No No

Degradation No Yes Yes Yes Yes


[47,11] ABIS−TS−ALLOC−FAILED

Check multiplexing parameters used by this BTS. If the Abis conveys only Evolium BTS remove

Q1 TS if it exists


Alarmsolved

Alarm persists?

no

yes




13.10 [47,12] INSUFFICIENT-TCU-RES

specificProblems GLOBAL-BSC [47] INSUFFICIENT-TCU-RES [12]




Alarm Description This alarm is raised to indicate that TCU allocation, in the case ofauto-detection of a TRE, has failed due to insufficient TCU resources.


A9130 BSC

Impact on System The SBL state remains unchanged.The TRE detected via the Audit will not be operational, no TCU willbe allocated.


Loss No No No No No



[47,12] INSUFFICIENT−TCU−RES

Check occupancy of the TSU and make place in the TSU using one of the following

methods


Alarmsolved

Alarm cleared?

no

yes

Trigger a TSU reshuffling

Decrease Max−Extra−TS−Primary if there is a 2 Abis BTS and the TCU supporting the second Abis link has still free resources

Move one BTS from this TSU to another one



13.11 [47,13] TRE-SECTOR-MISMATCH

specificProblems GLOBAL-BSC [47] TRE-SECTOR-MISMATCH [13]




Alarm Description This alarm is raised in the case of a mismatch in a TRE sector betweenthe sector defined via the Create-TRE command and the sector inwhich the TRE is equipped, as indicated via the BSC-BTS Audit.


A9130 BSC

Impact on System The SBL state remains unchanged.The TRE is not operational.


Loss No No No No No





[47,13] TRE−SECTOR−MISMATCH

Define correct sector via Create−TRE command

Alarmsolved

Alarm persists?

no

yes

Remove TRE from incorrect sector via

Delete−TRE command

Equip TRE in correct sector to correspond to defined TRE

via Create−TRE command


Alarm persists?

no

yes

Remove TRE

On−site

On−siteOR




13.12 [47,14] LACK-OF-TCU-SPACE

specificProblems GLOBAL-BSC [47] LACK-OF-TCU-SPACE [14]


probableCause UnderlyingResourceUnavailable


Alarm Description This alarm is raised to indicate that TCU allocation, in the case ofauto-detection of a TRE, has failed due to the TCU allocation beingtoo fragmented.


Impact on System The SBL state remains unchanged.The TRE detected via the Audit will not be operational, no TCU will beallocated. A TCU can be allocated if reshuffling is requested.


Loss No No No No No



[47,14] TCUTOO FRAGMENTED

Reshuffle TCUs via Compact RSL/TCU remapping

andManually add−on the TRE on

BSC


Alarmsolved

Alarm persists?

no

yes




13.13 [47,15] SWRPL-IN-PROGRESS

specificProblems GLOBAL-BSC [47] SWRPL-IN-PROGRESS [15]

eventType Equipment



Alarm Description This alarm is raised to indicate that an audit has occurred and thatthe BSC was informed of equipment addition or removal, but theBSC could not process this information, as the BSC was undergoingsoftware replacement.


A9130 BSC

Impact on System An audit is triggered when BTS-OM is initialized and the BSC isinformed of BTS equipment which is added or removed.The SBL state remains unchanged.The BSC is undergoing a software replacement.


Loss No No No No No





[47,15] SWRPL−IN−PROGRESS

If no audit is started, trigger new audit


Alarmsolved

Alarm persists?

no

yes

Wait for new autonomous audit




13.14 [47,16] MAX-TRE-EXCEEDED

specificProblems GLOBAL-BSC [47] MAX-TRE-EXCEEDED [16]

eventType Equipment



Alarm Description This alarm is raised to indicate that an audit has occurred, indicatingan addition of TREs when the maximum number of TREs alreadyexists in the BSC.


A9130 BSC

Impact on System The SBL state remains unchanged.The TREs detected via the audit cannot be auto-allocated as themaximum number of TREs already exists in the BSC.


Loss No No No No No





[47,16] MAX−TRE−EXCEEDED

Delete unrequired TRE data. TRE(s) must be not equipped,

if auto−allocate is set for the Abis


Alarmsolved

Alarm persists?

no

yes

Remove reported TRE(s)

On−site

Alarm persists?

no

yes

Alarmsolved




13.15 [47,17] MLPPP-FAILURE

specificProblems GLOBAL-BSC [47] MLPPP-FAILURE [17]




Alarm Description The IP link defined on the Ater interface is not available following failureof all the PPP links created to carry it.


Impact on System The impacted SBL state is not changed.

The MxBSC is connected to the CBC and the OMC-R through an IPlink. If the IP link is defined over the Ater interface it is carried byseveral PPP links using a timeslot of the Ater interface.When all PPP links become faulty, the connection between the BSCand the other entity is broken.When this failure situation occurs, the BSC is unable to send the alarmto the OMC-R. However, if a local terminal is connected, the BSCsends the alarm to the terminal.When the BSC is unable to send an alarm to the OMC-R, the BSC triesrepeatedly to send the alarms BSC_SYNC_REQUEST for BSC alarmsand TSC_BTS_SYNC_REQUEST for TSC and BTS alarms.When the alarm is eventually received, the OMC-R triggers an alarmaudit for the BSC alarms and an alarm audit for the TSC and BTSalarms.







[47, 17] MLPPP−FAILURE


Fix E1 links to MSC problems

E1 links to MSC are ok?

E1 path to PPP router is ok?

PPP router is ok?

yes

yes

yes

Fix E1 links to PPP router problems

Fix PPP router problems

Alarm persists?

Alarm persists?

Alarm persists?

no

no

no

Alarmsolved

no

no

no

yes

yes

yes




13.16 [47,18] MLPPP-PARTIAL-FAILURE

specificProblems GLOBAL-BSC [47] MLPPP-PARTIAL-FAILURE [18]




Alarm Description At least one PPP link defined to carry IP on Ater has failed, but thelink is still available.



The MxBSC is connected to the CBC and the OMC-R through an IPlink. If the IP link is defined over the Ater interface it is carried byseveral PPP links using a timeslot of the Ater interface. When somePPP links become faulty (but not all), the connection between theBSC and the other entity is kept but the bandwidth is reduced. O&Mcongestion may happen.There may be simultaneous transmission alarms on A or on Atermuxwhich can be at the origin of this alarm. If there are none, the origin ofthe problem is at MSC side.


Loss No No No No No





[47, 18] MLPPP−PARTIAL−FAILURE


Fix E1 links to MSC problems

E1 links to MSC are ok?

E1 path to PPP router is ok?

PPP router is ok?

yes

yes

yes

Fix E1 links to PPP router problems

Fix PPP router problems

Alarm persists?

Alarm persists?

Alarm persists?

no

no

no

Alarmsolved

no

no

no

yes

yes

yes




13.17 [47,19] DLS-RESTORATION

specificProblems GLOBAL-BSC [47] DLS-RESTORATION [19]


probableCause CorruptData


Alarm Description S-CPR VCE cannot start due to a corruption of the DLS. A previousversion of the DLS has been restored.



The restored BSC DLS is several days or several weeks old. The BSSconfiguration it contains may be obsolete and inconsistencies with therest 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 willpoint out which BTS need immediate correction. But even withoutalarm, operator has to take care to reconfigure the BSC.


Loss If configchanged

If configchanged

If configchanged

If configchanged

If config changed

Degradation - - - - -


Contact your Alcatel system support so the cause of the error can be examined.The information must be analyzed by qualified personnel.



13.18 [47,20] NTP-DRIFT-TIME-ALERT

specificProblems GLOBAL-BSC [47] NTP-DRIFT-TIME-ALERT [20]




Alarm Description The active OMCP has detected that there is a time drift of less than100s with the time server defined in the peer entities.



During operations like SBL reset or unlock OMC-R cleans up the list ofalarms for the impacted SBL. The clean up is done per comparisonbetween the OMC-R time of the operation and the BSC timestamps ofalarms. So the time drift between the BSC and the NTP server maylead to inconsistencies in alarm status between BSC and OMC-R. PMfile reporting may also be not synchronized. But the operational impactis null.

PM file reporting may also be not synchronized. But the operationalimpact is null.


Loss No No No No No





[47, 20] NTP DRIFT TIME ALERT


Correct NTP time server settings in

BSC

NTP time server settings in BSC

are ok?

Time setting in time server is ok?

yes

yes

Correct time setting in time server

Alarm persists?

Alarm persists?

Alarm persists?

no

no

Alarmsolved

no

no

no

yes

yes

yes

Wait for time gap to dissapear or reset

BSC

Alarmsolved




13.19 [47,21] NTP-TIME-SERVER-UNREACHABLE

specificProblems GLOBAL-BSC [47] NTP-TIME-SERVER-UNREACHABLE [21]




Alarm Description The NTP timer server defined in the MxBSC peer entity is unreachable.



During operations like SBL reset or unlock OMC-R cleans up the list ofalarms for the impacted SBL. The clean up is done per comparisonbetween the OMC-R time of the operation and the BSC timestamps ofalarms. So the time drift between the BSC and the NTP server maylead to inconsistencies in alarm status between BSC and OMC-R. PMfile reporting may also be not synchronized. But the operational impactis null.PM file reporting may also be not synchronized. But the operationalimpact is null.


Loss No No No No No







BSC


are ok?


yes

yes


Alarm persists?

Alarm persists?

Ethernet netwrk settings are ok?

no

no

Alarmsolved

no

no

no

yes

yes

yes

[47, 21] NTP TIME SERVER UNREACHABLE

Correct Ethernet network settings

Alarm persists?

no

yes




13.20 [47,22] NTP-DRIFT-TIME-EXCEEDED

specificProblems GLOBAL-BSC [47] NTP-DRIFT-TIME-EXCEEDED [22]




Alarm Description The active OMCP has detected that there is a time drift of more than100s with the time server defined in the peer entities.



During operations like SBL reset or unlock OMC-R cleans up the list ofalarms for the impacted SBL. The clean up is done per comparisonbetween the OMC-R time of the operation and the BSC timestamps ofalarms. So the time drift between the BSC and the NTP server maylead to inconsistencies in alarm status between BSC and OMC-R.PMfile reporting may also be not synchronized. But the operational impactis null.PM file reporting may also be not synchronized. But the operationalimpact is null.


Loss No No No No No







BSC


are ok?


yes

yes


Alarm persists?

Alarm persists?

no

no

Alarmsolved

no

no

no

yes

yes

Reset BSCAlarm

persists?

yes

[47, 22] NTP DRIFT TIME EXCEEDED




13.21 [47,23] MAX-HDLC-EXCEEDED

specificProblems GLOBAL-BSC [47] MAX-HDLC-EXCEEDED [23]




Alarm Description During TRE auto-detection mechanism, no HDLC handler can beallocated for the RSL on the TP-GSM board.



The new TRE detected during the BSC/BTS audit are not operationalbecause there is no more HDLC controller available to handle the RSL


Loss No No No No No





[47, 23] MAX HDLC EXCEEDED

Alarmsolved

yes

Alarm persists?

no


Change the multiplexing mode of

another BTS

Perform one of the following actions to

clear the alarm

Move the impacted BTS or other BTS to

another BSC

Change the multiplexing mode of the BTS where the TREs were added



14 Class 48: TR-OM Alarms


This section defines the BSC alarms for the Class 48: TR-OM alarm class.



14.1 [48,0] AUDIT-FAIL

specificProblems TR-OM [48] AUDIT-FAIL [0]




Alarm Description Due to a failure in the BSC-TSC audit, TR-OM changed from FLT/ITto FLT.


Impact on System TSL is up. When the TR-OM is FLT but the TSL is up, the BSC triggersan audit every two minutes until an audit succeeds.

TSL is down - corrective action required.



Loss – – – – –



[48,0] AUDIT−FAIL

Reset TSC


Alarmsolved

Alarm persists?

no

yes




14.2 [48,1] PROTOCOL-FAIL

specificProblems TR-OM [48] PROTOCOL-FAIL [1]




Alarm Description The TR-OM goes to FLT if there is protocol failure on the Abis interface;an ACK to some message is not received after three[hairsp]requiredretries.

An attempt is always made to respond by means of an ACK or NACKto a Request/Report/Ind message from the TSC regardless of thecontext. This however, cannot occur when there is a loss of LAPDand a protocol error is registered.




Loss – – – – –



[48,1] PROTOCOL−FAIL

Reset TSC


Alarmsolved

Alarm persists?

no

yes

TSL is down only:



15 Class 49: ALERTER Alarms


This section defines the BSC alarms for the Class 49: ALERTER alarm class.



15.1 [49,0] LOW-TRAF-SDCCH

specificProblems ALERTER [49] LOW-TRAF-SDCCH [0]




Alarm Description There is abnormally low traffic on SDCCHs in a cell compared withother BSS cells.


A9130 BSC

Impact on System This alarm inform the operator that there is abnormally low SDCCHtraffic in a cell compared with other cells. This is an informationmessage and no system defensive actions are taken.


Loss No No No No No





[49,0] TRAFF−SDCCH


Alarmsolved

Alarm persists?

no

yes

Related BTS alarm

events?

no

yes Solve related BTS alarm(s) first

Alarmsolved

Alarm persists?

no

yes

Related BSC alarm

events?

no

yes Solve related BSC alarm(s)





15.2 [49,1] CH-INCONSIST-SUSP

specificProblems ALERTER [49] CH-INCONSIST-SUSP [1]




Alarm Description There is an inconsistency in the terrestrial channel states.


A9130 BSC

Impact on System This alarm is generated when the number of seizure failures exceeds apre-assigned threshold value. The threshold is the maximum numberof seizures per circuit that is set by the operator on a BSS basis. Thisis an information message and no system defensive actions are taken.


Loss No No No No No





[49,1] CH−INCONSIST−SUSP

Alarmsolved

Alarm persists?

noyes

Byte related alarm

events?

no

yes Solve Byte relating alarm(s) first

Related DTC/Trunk/N7 alarm

events?

no

yesSolve that alarm(s)






15.3 [49,2] TCH-BLOCK-SUSPECT

specificProblems ALERTER [49] TCH-BLOCK-SUSPECT [2]




Alarm Description Traffic channel behavior is abnormal and calls remain on the channelsfor an extended length of time. It is suspected that the traffic channelsare blocked.


A9130 BSC

Impact on System This alarm is generated when the call duration for all traffic channels ina cell exceeds a pre-assigned threshold value (1...255 minutes). Thethreshold is set by the operator on a BSS basis.

This is an information message and no system defensive actions aretaken.


Loss No No No No No



[49,2] TCH−BLOCK−SUSPECT

Alarmsolved

Alarm persists?

noyes

TCH related hardware

problems?

no

yes Solve TCH related hardware problems






15.4 [49,3] TCH-OCCUP-SHORT

specificProblems ALERTER [49] TCH-OCCUP-SHORT [3]




Alarm Description The average traffic channel seizure time is considered to be too short.


A9130 BSC

Impact on System This alarm informs the operator that there has been abnormally shorttraffic duration on a traffic channel. This is an information messageand no system defensive actions are taken.


Loss No No No No No



[49,3] TCH−OCCUP−SHORT

Alarmsolved

Alarm persists?

noyes

TCH related hardware

problems?

no

yes Solve TCH related hardware problemst





16 Class 50: BSC EXTERNAL Alarms


This section defines the BSC alarms for the Class 50: BSC EXTERNALalarm class.



16.1 [50,1] EXT-ALARM-1

specificProblems BSC EXTERNAL [50] EXT-ALARM-1 [1]

eventType Equipment


perceivedSeverity Customer dependent

Alarm Description A probable cause and category is provided in a customer-dependenttable residing in the OMC-R. The OMC-R table describes the externalalarm.


Impact on System The SBL state remains unchanged. No system impact.


Loss – – – – –

Degradation – – – – –




[50,1] EXT−ALARM−1

no


External alarm

persists?

yes

Alarmsolved

yesAlarm was sent without

cause?

no

Trigger customer specific action according to

reported alarm (e.g. call fire brigade)

Check sensor function, replace sensor if required.

On−site

Check sensor connection to BSC. Reconnect sensor

if required.

On−site

Check cabling to sensor, replace cabling if required.

On−site




16.2 [50,2] EXT-ALARM-2


eventType Equipment







Loss – – – – –






no


External alarm

persists?

yes

Alarmsolved


cause?

no

Trigger customer−specific action according to



On−site


if required.

On−site


On−site




16.3 [50,3] EXT-ALARM-3


eventType Equipment







Loss – – – – –






no


External alarm

persists?

yes

Alarmsolved


cause?




On−site


if required.

On−site


On−siteno




16.4 [50,4] EXT-ALARM-4


eventType Equipment







Loss – – – – –

