bsc & tc alarm dictionary - b11

Alcatel-Lucent GSM

BSC & TC Alarm Dictionary

BSC & TC Document

Reference Guide

Release B11

3BK 21618 AAAA PCZZA Ed.16

Status RELEASED

Short title BSC & TC Alarm Dic.

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

BLANK PAGE BREAK

2 / 778 3BK 21618 AAAA PCZZA Ed.16

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.2 9153 OMC-R AS Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.3 LMT Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241.4 Alarm Information Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2 Class 32: BSC-ENVIRON Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.1 [32,0] CONV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.2 [32,1] BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3 Class 33: PROCESSOR Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.1 [33,0] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.2 [33,1] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.3 [33,3] ACCESS-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.4 [33,4] RELC-OV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.5 [33,7] TAKEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.6 [33,9] SDCCH-OVRL-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4 Class 35: N7 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4.1 [35,0] LNK-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.2 [35,2] RTE-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.3 [35,3] INC-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.4 [35,4] ASL-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.5 [35,5] RMH-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.6 [35,6] MSC-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.7 [35,7] MSC_DEGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

5 Class 36: TRUNK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635.1 [36,0] LFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.2 [36,3] RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.3 [36,4] AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675.4 [36,5] SLIP-OV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695.5 [36,6] SLIP-UN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.6 [36,7] LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735.7 [36,10] CRCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.8 [36,11] CHO-EERH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775.9 [36,12] CRC4-BERH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785.10 [36,13] CRC4-BERL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

6 Class 38: X.25 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816.1 [38,0] MODEM-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826.2 [38,1] LINK-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846.3 [38,2] PROT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

7 Class 39: BSC-SW-ANOMALY Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897.1 [39,1] OSN-NON-RECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907.2 [39,3] OSN-PROCEDURAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917.3 [39,5] USR-NONRECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927.4 [39,7] HWR-NONRECOVERABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937.5 [39,18] SANITY-TIMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

8 Class 42: TELECOM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958.1 [42,1] NACK-MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968.2 [42,2] OVERLOAD-MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988.3 [42,3] START-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998.4 [42,7] NO-RESET-CIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

3BK 21618 AAAA PCZZA Ed.16 3 / 778

Contents

8.5 [42,9] OVERLOAD-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038.6 [42,12] TEL-PAIR-LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048.7 [42,13] BSC-TRAFFIC-REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068.8 [42,14] GPRS-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1088.9 [42,15] TCH-RM-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108.10 [42,16] MSC-TRAFFIC-REDUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

9 Class 43: CELL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1139.1 [43,0] LOSS-OF-BCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1149.2 [43,1] LOSS-OF-SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169.3 [43,2] LOSS-OF-TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1189.4 [43,3] LOSS-OF-ALL-CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1209.5 [43,4] CELL-TRAFFIC-REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1229.6 [43,5] OVERLOAD-BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1249.7 [43,6] TRX-MAPPING-CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269.8 [43,248] CONFIGURED POOLS NOT FULLY USABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

10 Class 44: BTS-OM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12910.1 [44,0] AUDIT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13010.2 [44,1] PROTOCOL-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13210.3 [44,2] RECONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13410.4 [44,3] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13610.5 [44,5] SW-ACTIVATE-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13810.6 [44,6] CONFIG-DATA-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14010.7 [44,7] OMU-SELFTEST-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14210.8 [44,10] ABORT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14410.9 [44,11] PRELOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14510.10 [44,12] BTS-HW-CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

11 Class 45: CHANNEL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14911.1 [45,0] CH-UNBLOCK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15011.2 [45,1] CH-BLOCK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15211.3 [45,2] BSC-CIC-UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15411.4 [45,3] MSC-CIC-UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15611.5 [45,4] END-OF-REP-OF-UNBLOCK-PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

12 Class 46: BACKUP-MEDIUM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

12.1 [46,0] SYNC CORRUPTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16012.2 [46,1] UNSYNC-OTHER-CORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16112.3 [46,2] UNSYNC-OWN-CORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16312.4 [46,3] SYNC-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16412.5 [46,4] SECFILE-ROLLBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16512.6 [46,5] SINGLE-UPD-ROLLBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16712.7 [46,6] DUT-ROLLBACK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16912.8 [46,7] DISC-OOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17112.9 [46,8] DISC-PARITY-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

13 Class 47: GLOBAL-BSC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17513.1 [47,2] AUTO-BSC-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17613.2 [47,3] AUTO-BSC-RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17713.3 [47,4] BSC-SYNC-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17813.4 [47,5] BTS-SYNC-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17913.5 [47,6] AUDIT-COMPLETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18013.6 [47,7] BSC-HW-RESYNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18113.7 [47,8] AIFL-FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18213.8 [47,9] CBC-CONNECTION-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18313.9 [47,11] ABIS-TS-ALLOC-FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18513.10 [47,12] INSUFFICIENT-TCU-RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18613.11 [47,13] TRE-SECTOR-MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18713.12 [47,14] LACK-OF-TCU-SPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

4 / 778 3BK 21618 AAAA PCZZA Ed.16

Contents

13.13 [47,15] SWRPL-IN-PROGRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19013.14 [47,16] MAX-TRE-EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19213.15 [47,17] MLPPP-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19413.16 [47,18] MLPPP-PARTIAL-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19613.17 [47,19] DLS-RESTORATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19813.18 [47,20] NTP-DRIFT-TIME-ALERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19913.19 [47,21] NTP-TIME-SERVER-UNREACHABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20113.20 [47,22] NTP-DRIFT-TIME-EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20313.21 [47,23] MAX-HDLC-EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20513.22 [47,24] MUX-SECTOR-NOT-COMP-2ABIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20713.23 [47,25] TC-HW-RESYNCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20813.24 [47,26] TRAU-CP-OUT-OF-RANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20913.25 [47,27] TRAU-CP-ON-DEDICATED-ATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21013.26 [47,28] TRAU-CP-DOUBLE-DECLARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21113.27 [47,30] TRANS-CONFIG-IMPOSSIBLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21213.28 [47,40] CS-TEL-TEST-NOK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21313.29 [47,41] PS-TEL-TEST-NOK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21413.30 [47,103] BTS-TC-RESHUFFLING-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21613.31 [47,200] N7-CONF-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

14 Class 48: TR-OM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21914.1 [48,0] AUDIT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22014.2 [48,1] PROTOCOL-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

15 Class 49: ALERTER Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

15.1 [49,0] LOW-TRAF-SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22415.2 [49,1] CH-INCONSIST-SUSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22615.3 [49,2] TCH-BLOCK-SUSPECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22815.4 [49,3] TCH-OCCUP-SHORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

16 Class 50: BSC EXTERNAL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23116.1 [50,1] EXT-ALARM-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23216.2 [50,2] EXT-ALARM-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23416.3 [50,3] EXT-ALARM-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23616.4 [50,4] EXT-ALARM-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23816.5 [50,5] EXT-ALARM-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24016.6 [50,6] EXT-ALARM-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24216.7 [50,7] EXT-ALARM-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24416.8 [50,8] EXT-ALARM-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24616.9 [50,9] EXT-ALARM-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24816.10 [50,10] EXT-ALARM-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

17 Class 51: SWITCH G2 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25317.1 [51,0] TRANSIENT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25417.2 [51,1] SWITCH-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25517.3 [51,2] ROUTINE-TEST-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25917.4 [51,3] GLOBAL-ROUTINE-TEST-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

18 Class 52: BSC CLOCK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

18.1 [52,0] LOSS-OF-SEL-CLK-INP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26418.2 [52,1] LOSS-OF-CLK-GEN-FN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26618.3 [52,2] SWITCH-TO-LOCAL-CLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26718.4 [52,3] LOSS-OF-SYSTEM-CLOCK-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26918.5 [52,4] LOSS-OF-SYSTEM-CLOCK-B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27018.6 [52,5] LOSS-OF-CLK-DISTR-FN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27118.7 [52,6] BSC-RUN-ON-LOCAL-CLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27218.8 [52,7] LOC-CLK-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

19 Class 53: BROADCAST BUS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

19.1 [53,0] LOSS-OF-ONE-BROAD-BUS-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

3BK 21618 AAAA PCZZA Ed.16 5 / 778

Contents

19.2 [53,1] LOSS-OF-BOTH-BROAD-BUS-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27719.3 [53,2] DMA-PROBLEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27819.4 [53,3] LOSS-OF-ONE-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27919.5 [53,4] LOSS-OF-BOTH-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28019.6 [53,5] DEGRAD-BROAD-BUS-RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28119.7 [53,6] LOSS-OF-ONE-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28219.8 [53,7] LOSS-OF-BOTH-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28319.9 [53,8] DEGRAD-BROAD-BUS-CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

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

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

21 Class 66: TSC-TRUNK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28921.1 [66,21] LOOP-TO-ITF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29021.2 [66,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29121.3 [66,50] TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29221.4 [66,66] AIS-2-MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29421.5 [66,81] FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29621.6 [66,86] CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29821.7 [66,99] BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30021.8 [66,100] BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30221.9 [66,102] BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30421.10 [66,176] FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30621.11 [66,208] I1I2-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30821.12 [66,210] TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31021.13 [66,211] LOSS-OF-CLK-2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31221.14 [66,225] TU-LOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31421.15 [66,226] TU-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31521.16 [66,227] LP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31621.17 [66,228] LP-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31721.18 [66,229] LP-PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31821.19 [66,230] LP-J2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31921.20 [66,231] E1-AIS-2MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32021.21 [66,232] E1-FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32121.22 [66,233] E1-CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32221.23 [66,234] E1-BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32321.24 [66,235] E1-BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32421.25 [66,236] E1-RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

22 Class 67: TSC-CHANNEL Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

22.1 [67,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32822.2 [67,72] AIS-16-KB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32922.3 [67,122] TRAU-SYNCHRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33122.4 [67,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33322.5 [67,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33522.6 [67,131] INT-BUS-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

23 Class 70: TSC-SW-ANOMALY Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33923.1 [70,219] SW-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

24 Class 71: TSC-ENVIRON Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34324.1 [71,0] POWER-SUPPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

25 Class 73: BSC-ADAPT Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

25.1 [73,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34825.2 [73,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34925.3 [73,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35125.4 [73,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35325.5 [73,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35425.6 [73,203] LOSS-OF-ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

6 / 778 3BK 21618 AAAA PCZZA Ed.16

Contents

25.7 [73,212] LOSS-OF-CLK-8M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35825.8 [73,213] LOSS-OF-CLK-BOTH-8M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36025.9 [73,216] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36225.10 [73,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36325.11 [73,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36425.12 [73,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

26 Class 74: BTS-ADAPT Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36726.1 [74,20] BLOCKED-FROM-USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36826.2 [74,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37026.3 [74,23] TESTMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37126.4 [74,122] SYNCHRO-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37226.5 [74,124] SYNC-AL-CLOCKR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37426.6 [74,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37626.7 [74,130] MEMORY-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37826.8 [74,139] MISSING-UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38026.9 [74,141] FORCED-CNTRL-ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38226.10 [74,142] INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38326.11 [74,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38526.12 [74,159] DIAG-TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38626.13 [74,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38726.14 [74,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38926.15 [74,245] LOCAL-REINIT-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39126.16 [74,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39326.17 [74,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

27 Class 75: TCSM-ADAPT Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39727.1 [75,20] BLOCKED-FROM-USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39827.2 [75,22] LOOP-TO-EQUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39927.3 [75,112] FAN-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40027.4 [75,122] SYNCHRO-AL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40127.5 [75,124] SYNCHRO-AL-CLOCKR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40327.6 [75,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40527.7 [75,130] DSP-LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40727.8 [75,136] FIRST-DSP-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40927.9 [75,139] MISSING-UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41127.10 [75,141] FORCED-CNTRL-ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41327.11 [75,142] INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41427.12 [75,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41627.13 [75,159] DIAG-TESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41727.14 [75,202] NO-Q1-CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41827.15 [75,208] TRIB-TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42027.16 [75,209] INT-BUS-FLT-G25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42227.17 [75,210] ATER-TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42427.18 [75,211] LOSS-OF-CLK-2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42627.19 [75,216] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42827.20 [75,221] TRIB-TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42927.21 [75,222] TRIB-AIS-2MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43127.22 [75,223] TRIB-FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43327.23 [75,224] TRIB-CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43527.24 [75,225] TRIB-BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43627.25 [75,226] TRIB-BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43827.26 [75,227] TRIB-BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44027.27 [75,228] TRIB-FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44227.28 [75,231] ATER-TWO-MB-MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44427.29 [75,232] ATER-AIS-2MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44627.30 [75,233] ATER-FRAME-ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44827.31 [75,234] ATER-CRC-MFRAME-ALGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450

3BK 21618 AAAA PCZZA Ed.16 7 / 778

Contents

27.32 [75,235] ATER-BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45127.33 [75,236] ATER-BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45327.34 [75,237] ATER-BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45527.35 [75,238] ATER-FAR-END-ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45727.36 [75,241] SET-PROD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45927.37 [75,245] LOCAL-REINIT-REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46027.38 [75,246] DOWNLOAD-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46227.39 [75,247] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464

28 Class 96: PROCESS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465

28.1 [96,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46628.2 [96,1] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46728.3 [96,2] MULTIPLE-RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46828.4 [96,3] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470

29 Class 97: ATCA-PROCESSOR Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47329.1 [97,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47429.2 [97,1] TAKEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47529.3 [97,2] RLC-OV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47629.4 [97,3] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47729.5 [97,4] APPLICATION-FATAL-TERMINATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47929.6 [97,5] SYSTEM-FATAL-TERMINATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48029.7 [97,6] UNPLUGGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48129.8 [97,7] FW-UPGRADE-UNSUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48229.9 [97,8] FW-UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48329.10 [97,9] FIRMWARE-INCOMPATIBILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48429.11 [97,10] FATAL-HW-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48529.12 [97,11] TEMPERATURE-CRITICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48629.13 [97,12] TEMPERATURE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48829.14 [97,14] VOLTAGE-FATAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49029.15 [97,15] VOLTAGE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49229.16 [97,16] VOLTAGE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49429.17 [97,17] ETHERNET-LINK-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49629.18 [97,18] IPMI-FIRMWARE-NOT-UP-TO-DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49829.19 [97,19] FIRMWARE-NOT-UP-TO-DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49929.20 [97,20] CONFIGURATION-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50029.21 [97,21] TAKEOVER-REFUSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50129.22 [97,22] CPU-OVERLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50229.23 [97,23] BSC-CONF-UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50329.24 [97,30] N7-DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50429.25 [97,31] HDLC-HANDLER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50529.26 [97,32] Q1-HANDLER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50629.27 [97,33] RW-HANDLER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50729.28 [97,34] TDM-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50829.29 [97,35] E1-FRAMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50929.30 [97,36] TP-MAIN-SW-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51029.31 [97,37] TP-MAIN-FILE-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51129.32 [97,38] TP-MAIN-ACCESS-PB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51229.33 [97,39] SS7-SW-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51429.34 [97,40] CS-TEL-TEST-NOK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51529.35 [97,50] NE1OE-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51629.36 [97,51] E1-SL-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51829.37 [97,60] TP-CAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51929.38 [97,61] TPIP-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52029.39 [97,62] CONFIG-IP-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52129.40 [97,63] CONFIG-IP-INPUT-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52229.41 [97,64] CONFIG-IP-RUNTIME-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52329.42 [97,65] DRIVERS-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524

8 / 778 3BK 21618 AAAA PCZZA Ed.16

Contents

29.43 [97,66] HW-DIAGNOSIS-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52529.44 [97,67] INTER-TP-ACCESS-PB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526

30 Class 98: ATCA-SWITCH Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

30.1 [98,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52830.2 [98,3] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52930.3 [98,6] UNPLUGGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53030.4 [98,7] FW-UPGRADE-UNSUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53130.5 [98,8] FW-UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53230.6 [98,9] FIRMWARE-INCOMPATIBILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53330.7 [98,10] FATAL-HW-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53530.8 [98,11] TEMPERATURE-FATAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53830.9 [98,12] TEMPERATURE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54030.10 [98,13] TEMPERATURE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54230.11 [98,14] VOLTAGE-FATAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54430.12 [98,15] VOLTAGE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54630.13 [98,16] VOLTAGE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54830.14 [98,18] IP-ROUTER-LINK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55030.15 [98,19] TELECOM-LINK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55230.16 [98,20] OAM-LINK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55430.17 [98,21] FIRMWARE-NOT-UP-TO-DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55630.18 [98,22] IP-CONFIG-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55730.19 [98,23] ASIG-OVER-IP-LINK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55930.20 [98,24] BSS-OVER-IP-LINK-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561

31 Class 99: ATCA-SHELF Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56331.1 [99,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56431.2 [99,3] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56531.3 [99,6] UNPLUGGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56631.4 [99,7] FW-UPGRADE-UNSUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56731.5 [99,8] FW-UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56831.6 [99,9] FIRMWARE-INCOMPATIBILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56931.7 [99,10] FATAL-HW-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57131.8 [99,11] TEMPERATURE-FATAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57331.9 [99,12] TEMPERATURE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57531.10 [99,13] TEMPERATURE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57731.11 [99,14] VOLTAGE-FATAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57931.12 [99,15] VOLTAGE-MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58131.13 [99,16] VOLTAGE-MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58231.14 [99,17] ETHERNET-LINK-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58331.15 [99,18] SHELF-MANAGER-ACCESS-PB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58531.16 [99,19] FAN-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58631.17 [99,20] FIRMWARE-NOT-UP-TO-DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58731.18 [99,21] IPMI-BUS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588

32 Class 100: LIU-SHELF Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59132.1 [100,0] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59232.2 [100,1] MUX-TAKEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59332.3 [100,4] ACCESS-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59432.4 [100,6] UNPLUGGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59532.5 [100,7] FW-UPGRADE-UNSUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59632.6 [100,8] FW-UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59732.7 [100,9] FIRMWARE-INCOMPATIBILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59832.8 [100,19] FIRMWARE-NOT-UP-TO-DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59932.9 [100,20] LIU_SHELF_PEM_OWN_VBAT_LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60032.10 [100,21] LIU_SHELF_RED_VBAT_LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60132.11 [100,22] PEM_OWN_12V_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60232.12 [100,23] TOO_HIGH_TEMPERATURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60332.13 [100,24] PEM_NOT_RESPONDING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605

3BK 21618 AAAA PCZZA Ed.16 9 / 778

Contents

32.14 [100,50] NE1OE-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60732.15 [100,51] E1-SL-FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609

33 Class 101: BSC-TRANS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611

33.1 [101,0] LIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61233.2 [101,1] AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61433.3 [101,2] LFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61633.4 [101,4] BER-10E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61833.5 [101,5] RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62033.6 [101,6] BER-10E-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62233.7 [101,7] BER-10E-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62433.8 [101,8] FRAME-SLIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62633.9 [101,9] PPP-LNK-LOOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62833.10 [101,10] PPP-NO-HDLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63033.11 [101,11] PPP-NO-LCP-REP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63133.12 [101,12] PPP-CONF-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63233.13 [101,13] PPP-HIGH-ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63333.14 [101,14] OML-MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63533.15 [101,20] SFP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63733.16 [101,21] LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63833.17 [101,22] LOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64033.18 [101,23] MS-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64233.19 [101,24] MS-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64333.20 [101,25] MS-BER-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64433.21 [101,26] MS-BER-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64533.22 [101,28] SFP-NOT-SUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64733.23 [101,31] AU-LOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64833.24 [101,32] AU-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65033.25 [101,41] HP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65133.26 [101,42] HP-PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65233.27 [101,43] HP-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65433.28 [101,44] HP-LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65533.29 [101,51] TU-LOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65733.30 [101,52] TU-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65933.31 [101,55] LP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66033.32 [101,56] LP-PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66233.33 [101,57] LP-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66433.34 [101,60] PPP-CROSS-CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66533.35 [101,61] PPP-LCP-TER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66633.36 [101,62] PPP-LOW-ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66733.37 [101,63] PPP-MED-ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66833.38 [101,100] STM1-TAKEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669

34 Class 104: TC-OM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

34.1 [104,0] TC-INIT-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67234.2 [104,1] TC-INIT-SUCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673

35 Class 105: TRANSCODER Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675

35.1 [105,0] POWER-SUPPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67635.2 [105,128] EQUIPMENT-FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67735.3 [105,130] DSP LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67935.4 [105,136] FIRST-DSP-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68135.5 [105,148] RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68335.6 [105,210] TRANS-FLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68435.7 [105,211] LOSS-OF-CLK-2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68635.8 [105,216] RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68735.9 [105,238] ACTIVE-HSI-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68835.10 [105,239] REDUNDANT-HSI-FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690

10 / 778 3BK 21618 AAAA PCZZA Ed.16

Contents

36 BSC/TC Alarm Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69336.1 Restart and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69436.2 Reset and Software Anomaly Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71036.3 System Support Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71136.4 Other BSC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71136.5 TC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75636.6 BTS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763

37 Consequences of an SBL State Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765

37.1 9120 BSC SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76637.2 9130 BSC Evolution SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773

3BK 21618 AAAA PCZZA Ed.16 11 / 778

Figures

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

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

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

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

12 / 778 3BK 21618 AAAA PCZZA Ed.16

Tables

TablesTable 1: Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Table 2: Alarm Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Table 3: Alarm Definition: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

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

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

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

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

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

Table 9: System Support Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711

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

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


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

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

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




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

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

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


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




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






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


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


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



3BK 21618 AAAA PCZZA Ed.16 13 / 778

Tables


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


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

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

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

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


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

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


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

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


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


Table 56: Additional Information for Alarm [70,219] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756

Table 57: Additional Information for Alarm [73,022] to [73,216] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756

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

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

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

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

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

Table 63: Additional Information for Alarm [74,20] to [74,202] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763

14 / 778 3BK 21618 AAAA PCZZA Ed.16

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.

Document Pertinence This document applies to release B11 of the BSS.

This document contains IP transport in the BSS related information. Thisfeature is available commercially from Release B11 MR2.

What’s New In Edition 16Section [101,8] (Section 36.4.37) was added.

In Edition 15The alarm [97,18] IPMI-FIRMWARE-NOT-UP-TO-DATE (Section 29.18) wasadded.

In Edition 14Description improvement for alarm [97,1] TAKEOVER (Section 29.2).Alarm [97,67] INTER-TP-ACCESS-PB (Section 29.44) was added.Corrective action improvement for alarm [99,10] FATAL-HW-FAILURE (Section31.7).System impact was updated for alarms:

[35,4] ASL-REP (Section 4.4)

[35,5] RMH-REP (Section 4.5)

[42,16] MSC-TRAFFIC-REDUCTION (Section 8.10)

[43,6] TRX-MAPPING-CHANGE (Section 9.7)

[47,28] TRAU-CP-DOUBLE-DECLARED (Section 13.26)

3BK 21618 AAAA PCZZA Ed.16 15 / 778

Preface

[104,0] TC-INIT-FAIL (Section 34.1)

[104,1] TC-INIT-SUCC (Section 34.2).Applicability was updated for alarms:

[47,26] TRAU-CP-OUT-OF-RANGE (Section 13.24)

[47,27] TRAU-CP-ON-DEDICATED-ATER (Section 13.25)

[47,28] TRAU-CP-DOUBLE-DECLARED (Section 13.26)

[47,200] N7-CONF-FAILURE (Section 13.31)

[51,3] GLOBAL-ROUTINE-TEST-REP (Section 17.4)

Class 101: BSC-TRANS Alarms (Section 33)

[104,0] TC-INIT-FAIL (Section 34.1)

[104,1] TC-INIT-SUCC (Section 34.2).Impact table was updated for alarms:

[47,19] DLS-RESTORATION (Section 13.17)

[48,0] AUDIT-FAIL (Section 14.1)

[48,1] PROTOCOL-FAIL (Section 14.2)

Class 50: BSC EXTERNAL Alarms (Section 16)

Class 73: BSC-ADAPT Alarms (Section 25)

[96,3] ACCESS-FAIL (Section 28.4)

[99,9] FIRMWARE-INCOMPATIBILITY (Section 31.6)

[100,50] NE1OE-FAILURE (Section 32.14).

In Edition 13Section BTS Alarms (Section 36.6) was created.

In Edition 12The following have been added:

[98,21] FIRMWARE-NOT-UP-TO-DATE (Section 30.17)

[99,20] FIRMWARE-NOT-UP-TO-DATE (Section 31.17).The following have been updated:


[97,19] FIRMWARE-NOT-UP-TO-DATE (Section 29.19)




[100,19] FIRMWARE-NOT-UP-TO-DATE (Section 32.8).

In Edition 11Description improvement for alarm [98,10] FATAL-HW-FAILURE (Section 30.7).Applicability was updated for alarm [46,1] UNSYNC-OTHER-CORR (Section12.2).

16 / 778 3BK 21618 AAAA PCZZA Ed.16

Preface

Corrective action was updated for alarms:

[35,6] MSC-REP (Section 4.6)

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

[44,1] PROTOCOL-FAIL (Section 10.2).

In Edition 10Alarm description was updated for alarm [42,2] OVERLOAD-MSC (Section 8.2).Severity was updated for alarm [35,6] MSC-REP (Section 4.6).Impacted SBL was updated for STM1 related alarms in Class 101:BSC-TRANS Alarms (Section 33).

In Edition 09Alarm [43,6] TRX-MAPPING-CHANGE (Section 9.7) was added.Alarm severity was changed for alarms:

[35,6] MSC-REP (Section 4.6)

[42,16] MSC-TRAFFIC-REDUCTION (Section 8.10).Description improvement for alarms:

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

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

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

[47,40] CS-TEL-TEST-NOK (Section 13.28)

[47,41] PS-TEL-TEST-NOK (Section 13.29)

[97,23] BSC-CONF-UNAVAILABLE (Section 29.23)


[97,65] DRIVERS-FAILURE (Section 29.42)

[97,66] HW-DIAGNOSIS-FAILURE (Section 29.43)

[98,24] BSS-OVER-IP-LINK-FAIL (Section 30.20).

In Edition 08The following alarms have been added:

[47,103] BTS-TC-RESHUFFLING-FAIL (Section 13.30)

[99,21] IPMI-BUS-FAIL (Section 31.18).

[101,14] OML-MODE (Section 33.14)

[101,41] HP-UNEQ (Section 33.25).Description improvement for alarms:

[97,65] DRIVERS-FAILURE (Section 29.42)

[97,66] HW-DIAGNOSIS-FAILURE (Section 29.43)

[98,11] TEMPERATURE-FATAL (Section 30.8)

[99,11] TEMPERATURE-FATAL (Section 31.8).Section Overview was updated with the commercial name for the TCIF/TCIFIboards.

3BK 21618 AAAA PCZZA Ed.16 17 / 778

Preface

In Edition 07The following alarms have been added:


[47,41] PS-TEL-TEST-NOK (Section 13.29)

[97,23] BSC-CONF-UNAVAILABLE (Section 29.23)


[98,22] IP-CONFIG-FAIL (Section 30.18)

[98,23] ASIG-OVER-IP-LINK-FAIL (Section 30.19)

[98,24] BSS-OVER-IP-LINK-FAIL (Section 30.20).Improvements have been made in:

[71,0] POWER-SUPPLY (Section 24.1)

[97,17] ETHERNET-LINK-FAILURE (Section 29.17)

In Edition 06Alarm Description have been improved for [42,14] GPRS-RESET (Section 8.8).

In Edition 05Corrective Action have been improved for the following alarms:

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

[42,15] TCH-RM-FAULT (Section 8.9)

[47,22] NTP-DRIFT-TIME-EXCEEDED (Section 13.20)

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


[99,3] ACCESS-FAIL (Section 31.2)Corrective action from alarm [35,7] MSC_DEGRADE (Section 4.7) had beenupdated.

In Edition 04Improvement done in [101,25] MS-BER-6 (Section 33.20).

In Edition 03Description improvement for:

[35,4] ASL-REP (Section 4.4)

[35,5] RMH-REP (Section 4.5)

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

[42,15] TCH-RM-FAULT (Section 8.9)

[47,22] NTP-DRIFT-TIME-EXCEEDED (Section 13.20)

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



18 / 778 3BK 21618 AAAA PCZZA Ed.16

Preface

[99,10] FATAL-HW-FAILURE (Section 31.7).

In Edition 02Corrective action have been added for the following alarms:

[101,10] PPP-NO-HDLC (Section 33.10)

[101,11] PPP-NO-LCP-REP (Section 33.11)

[101,12] PPP-CONF-FAIL (Section 33.12)

[101,20] SFP-UNEQ (Section 33.15)

[101,21] LOS (Section 33.16)

[101,22] LOF (Section 33.17)

[101,23] MS-AIS (Section 33.18)

[101,24] MS-RDI (Section 33.19)

[101,25] MS-BER-6 (Section 33.20)

[101,26] MS-BER-3 (Section 33.21)

[101,28] SFP-NOT-SUP (Section 33.22)

[101,31] AU-LOP (Section 33.23)

[101,32] AU-AIS (Section 33.24)

[101,42] HP-PLM (Section 33.26)

[101,43] HP-RDI (Section 33.27)

[101,44] HP-LOM (Section 33.28)

[101,51] TU-LOP (Section 33.29)

[101,52] TU-AIS (Section 33.30)

[101,55] LP-UNEQ (Section 33.31)

[101,56] LP-PLM (Section 33.32)

[101,57] LP-RDI (Section 33.33)

[101,60] PPP-CROSS-CON (Section 33.34)

[101,61] PPP-LCP-TER (Section 33.35)

[101,62] PPP-LOW-ERR (Section 33.36)

[101,63] PPP-MED-ERR (Section 33.37)

[101,100] STM1-TAKEOVER (Section 33.38)

In Edition 01Update due to feature NEW ALMAP FM MODULE REPLACEMENT AS.First release of the document.

3BK 21618 AAAA PCZZA Ed.16 19 / 778

Preface

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.

20 / 778 3BK 21618 AAAA PCZZA Ed.16

1 Introduction

1 Introduction

This section describes the structure of alarm messages.

3BK 21618 AAAA PCZZA Ed.16 21 / 778

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.

Note: The following convention applies for a 9125 TC equipped with a TC STM1 -IP subrack:

TC STM1 interface board is also referred as TCIF

TC STM1 IP interface board is also referred as TCIFI.

1.2 9153 OMC-R AS Alarm InformationIn the 9153 OMC-R, Alarm Surveillance provides an efficient means to control,supervise and manage equipment problems in the BSS.

Alarms or Alarm notifications consist of messages sent by network 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.

22 / 778 3BK 21618 AAAA PCZZA Ed.16

1 Introduction

1.2.2 Alarm Type

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

This information is sub-divided into:

eventType. Table 1 describes the five eventTypes.

probableCause

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

eventType Indicates...

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

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

Processing Error a software or processing fault.

Equipment an equipment fault.

Environmental a problem in the enclosure containing the equipment.

Table 1: Event Types

Severity Level Indicates...

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

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

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

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

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

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

Table 2: Alarm Severity Levels

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

3BK 21618 AAAA PCZZA Ed.16 23 / 778

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

24 / 778 3BK 21618 AAAA PCZZA Ed.16

1 Introduction

1.3.4 Classification

The characteristics of the alarm, consisting of:

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

Alarm Dictionary

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

Dictionary

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

Alarm Condition - has one of the following values:

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

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

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

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

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

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

cleared the fault.

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

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

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

3BK 21618 AAAA PCZZA Ed.16 25 / 778

1 Introduction

1.3.5 SBL States

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

IT

FIT

Faulty

EF

FOS

OPR

SOS

WTC

UT

NEQ

MSD

MSD AUTO.

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

1.3.6 RIT List

The information for the suspected RIT(s) is displayed if the system is able 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.

26 / 778 3BK 21618 AAAA PCZZA Ed.16

1 Introduction

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

1.4.1 Alarm Definition

MO format LMT format

Banner Banner

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

eventType -

probableCause -

perceived Severity Category

SBL SBL

Table 3: Alarm Definition:

1.4.2 Alarm Description

The Alarm description is structured as follows:

Alarm Description

Impact on System

Failure Identification Strategy (if applicable)

Corrective Actions.

1.4.3 Alarm Definition

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

[36, 7] TRUNK - LOS

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

1.4.3.3 specificProblemsThe specificProblems provides the alarm class name.

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

3BK 21618 AAAA PCZZA Ed.16 27 / 778

1 Introduction

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

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

MO Severity LMT Category

Critical VPMA, SA

Major PMA

Minor DMA

Warning MI

Table 4: Mapping of MO Perceived Severity to LMT Category

1.4.4 Alarm Description

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

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

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

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

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

28 / 778 3BK 21618 AAAA PCZZA Ed.16

1 Introduction

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

The additional data is gathered from:

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

test procedures to perform

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

Checks that determine whether:

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

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

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

measurements.

Resource and data verification - checks that determine whether:

Hardware is serviceable or available. The items checked are passive

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

Software versions and parameter settings are correct.

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

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

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

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

3BK 21618 AAAA PCZZA Ed.16 29 / 778

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 36). 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.

30 / 778 3BK 21618 AAAA PCZZA Ed.16

2 Class 32: BSC-ENVIRON Alarms


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

3BK 21618 AAAA PCZZA Ed.16 31 / 778


2.1 [32,0] CONV

specificProblems BSC-ENVIRON [32] CONV [0]

eventType Equipment

probableCause PowerProblem

perceivedSeverity Critical (VPMA)

Alarm Description 9120 BSC: The convertor condition is detected by the S-CPR. A faultcan be detected for a particular convertor. This is done by monitoringthe scan point on the controlling S-CPR. One scan point exists for eachconvertor.The redundant power supply is available.

Applicability 9120 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. 9120 BSC:The BSC is able to distinguish between the different convertors withthe 9120 BSC implementation and cabling. Therefore the RIT of theaffected 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

32 / 778 3BK 21618 AAAA PCZZA Ed.16


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

3BK 21618 AAAA PCZZA Ed.16 33 / 778


2.2 [32,1] BAT

specificProblems BSC-ENVIRON [32] BAT [1]

eventType Equipment



Alarm Description There is a battery on each S_CPR.This battery feeds the SRAM where the DLS is stored.The output power of the battery is monitored and the alarm reflects thatthe output power dropped below a pre-defined threshold.At alarm occurrence, this is still no impact on the service but if operatordoes not replace the battery, the output power will still decrease,leading to problems of access to the DLS the battery and the CPR.


Impact on System At alarm occurrence, this is still no impact on the service but if operatordoes not replace the battery, the output power will still decrease,leading to problems of access to the DLS the battery and the CPR.SeeConsequences of an SBL State Change.


Loss No No No No No


34 / 778 3BK 21618 AAAA PCZZA Ed.16



[32,1] BAT

Alarmsolved

yesBatteryoperational?

no

On−site

Replace SYS−CPRC


Identify the suspected SYS−CPRC.

On−site

3BK 21618 AAAA PCZZA Ed.16 35 / 778


36 / 778 3BK 21618 AAAA PCZZA Ed.16

3 Class 33: PROCESSOR Alarms


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

3BK 21618 AAAA PCZZA Ed.16 37 / 778


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.

38 / 778 3BK 21618 AAAA PCZZA Ed.16



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.

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.3BK 21618 AAAA PCZZA Ed.16 39 / 778



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 36) for the byte definition.

40 / 778 3BK 21618 AAAA PCZZA Ed.16


3.2 [33,1] RESET

specificProblems PROCESSOR [33] RESET [1]




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

3BK 21618 AAAA PCZZA Ed.16 41 / 778



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.

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:*Reset* Resume the action* Initiate an audit* Terminate the action.

42 / 778 3BK 21618 AAAA PCZZA Ed.16



Loss No No No No No



The processor returns to service automatically. If the reset procedure fails orthere are too many resets within a certain time frame, the processor is reloaded.

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

3BK 21618 AAAA PCZZA Ed.16 43 / 778


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 N7 link, as long as there are other N7 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.

44 / 778 3BK 21618 AAAA PCZZA Ed.16



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

3BK 21618 AAAA PCZZA Ed.16 45 / 778


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 N7 link, as long as there are other N7 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).


46 / 778 3BK 21618 AAAA PCZZA Ed.16



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

3BK 21618 AAAA PCZZA Ed.16 47 / 778


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)

48 / 778 3BK 21618 AAAA PCZZA Ed.16



[33,7] TAKEOVER

Alarmsolved

yes

Alarm persists?

no


Lock CPR/DTC

TestCPR/DTC

VerifyCPR/DTC

Unlock CPR/DTC

3BK 21618 AAAA PCZZA Ed.16 49 / 778


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

50 / 778 3BK 21618 AAAA PCZZA Ed.16

4 Class 35: N7 Alarms


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

3BK 21618 AAAA PCZZA Ed.16 51 / 778


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.


9130 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 9120 BSC:The alarm is accompanied by either a SLIP-OV [36,5] orSLIP-UN [36,6] alarm related to the corresponding ATR SBL.For 9130 BSC Evolution: The alarm is accompanied by FRAME-SLIP[101,8] alarm related to the corresponding ATR SBL.


Loss No No No No No


52 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 53 / 778


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.


9130 BSC

Impact on System This alarm can come from transmission problem on the Ater mux oron the Atr. In this case, the N7 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.the alarm may be raised during TP takeover too;in case of TP takeover, when alarm occurs, access-class are baredonly after T_I timer expiration and on-going calls are not affected.

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


54 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 55 / 778


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.


9130 BSC

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


Loss No No No No No


56 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 57 / 778


4.4 [35,4] ASL-REP

specificProblems N7 [35] ASL-REP [4]


probableCause communicationSubsystemFailure

perceivedSeverity Minor(DMA)

Alarm Description this alarm is reported whenever one SCTP association is broken orestablished.


Impact on System If begin alarm reported, the SBL will change to FLT, if end alarmreported, the SBL will change to IT.


Loss No No No No No

Degradation No No Yes No No


None - the SBL normally returns to IT state without operator intervention.

Do not run a Disable command because you need to keep trying to initialize ituntil is successful.

58 / 778 3BK 21618 AAAA PCZZA Ed.16


4.5 [35,5] RMH-REP

specificProblems N7 [35] RMH-REP [5]




Alarm Description this alarm is for the feature Multi-Homing and it is only reported for theASL that has the remote endpoint with 2 IP addresses. It is reportedwhenever one of the IP addresses status is changed while the SCTPassociation status keep in traffic.


Impact on System If begin alarm reported, the SBL will change to FIT, if end alarmreported, the SBL will change to IT.


Loss No No No No No



None - the SBL normally returns to IT state without operator intervention.

Do not run a Disable command because you need to keep trying to initialize ituntil is successful.

3BK 21618 AAAA PCZZA Ed.16 59 / 778


4.6 [35,6] MSC-REP

specificProblems N7 [35] MSC-REP [6]




Alarm Description this alarm is reported when there is no IT ASL.


Impact on System An alarm begin will make SBL change to FLT, it means there is no ITASL to take traffic, that is the traffic function is not available of this MSC.


Loss No No Yes Yes No



[35, 6] MSC−REP

Alarmsolved

yes


ASL are disabled? Init ASL Alarm persists?

BSC−MSC telecom IP connectivity

is ok?

Solve IP issues Alarm persists?

MSCinterface/system

is ok?Solve MSC issues Alarm

persists?

no

no

no

no

no

yes

yes

no

yes

yes

yes

60 / 778 3BK 21618 AAAA PCZZA Ed.16


4.7 [35,7] MSC_DEGRADE

specificProblems N7 [35] MSC_DEGRADE [7]

eventType communication



Alarm Description This alarm is most caused by one IP network problem, for one MSC’there is not enough IT ASL to take traffic.


Impact on System An alarm begin will make the SBL change to FIT, it means not enoughASL link to take traffic, and the traffic will be degrade.


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 61 / 778



[35, 7] MSC−DEGRADE

Alarmsolved

yes

Alarm persists?

no


If ASL is disabled, init ASL

IP connectivity BSC−MSC OK?

Alarm persists?

Solve the IP connectivity BSC−MSC

no

yes

no

yes

62 / 778 3BK 21618 AAAA PCZZA Ed.16

5 Class 36: TRUNK Alarms


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

3BK 21618 AAAA PCZZA Ed.16 63 / 778


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.


64 / 778 3BK 21618 AAAA PCZZA Ed.16


5.2 [36,3] RAI

specificProblems TRUNK [36] RAI [3]


probableCause FarEndReceiverFailure


Alarm Description The DTC (9120 BSC) or the TP-GSM (9130 BSC Evolution) hasdetected a RAI (Remote Alarm Indication) on the Trunk.


9130 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.RAI is the signal sent on the E1 by a remote transmission node as aresponse to the detection of a fatal transmission fault (AIS, LIS, LFA.).This is the BSC view of transmission, so check for transmission alarms.

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



Loss Yes No No No No

Degradation No No Yes No No

3BK 21618 AAAA PCZZA Ed.16 65 / 778



[36,3] RAI

yes


peer side?

no

Alarmsolved

Alarm persists?

no yes




Transmission alarm (LIS, AIS; LFA,

EER, BERH) events?

yes

no

66 / 778 3BK 21618 AAAA PCZZA Ed.16


5.3 [36,4] AIS

specificProblems TRUNK [36] AIS [4]


probableCause Ais


Alarm Description The DTC (9120 BSC) or the TP-GSM (9130 BSC Evolution) hasdetected all ones indication (AIS, Alarm Indication Signal) on the Trunk:Less than four zeros in four consecutive frames means AIS.


9130 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 9120 BSC, a local loop test is done by the DTC to verify if thefailure is external (EF) or internal (FLT).




Degradation No No No Yes No

3BK 21618 AAAA PCZZA Ed.16 67 / 778



[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

68 / 778 3BK 21618 AAAA PCZZA Ed.16


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


3BK 21618 AAAA PCZZA Ed.16 69 / 778



[36,5] SLIP−OV

yes

Transmission board settings

OK?

no

Alarmsolved

Alarm persists?


yes

Correct Transmissionboards settings


Clock or Synchronization alarm

events?

yes

no

70 / 778 3BK 21618 AAAA PCZZA Ed.16


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


3BK 21618 AAAA PCZZA Ed.16 71 / 778



[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

72 / 778 3BK 21618 AAAA PCZZA Ed.16


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.




3BK 21618 AAAA PCZZA Ed.16 73 / 778



[36,7] LOS

yes


peer side?

no

Alarmsolved

Alarm persists?

no yes




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

events?

yes

no

74 / 778 3BK 21618 AAAA PCZZA Ed.16


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.




3BK 21618 AAAA PCZZA Ed.16 75 / 778



[36,10] CRCA

yes


peer side?

no

Alarmsolved

Alarm persists?

no yes




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

events?

yes

no

76 / 778 3BK 21618 AAAA PCZZA Ed.16


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

3BK 21618 AAAA PCZZA Ed.16 77 / 778


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

78 / 778 3BK 21618 AAAA PCZZA Ed.16


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.

3BK 21618 AAAA PCZZA Ed.16 79 / 778


80 / 778 3BK 21618 AAAA PCZZA Ed.16

6 Class 38: X.25 Alarms


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

3BK 21618 AAAA PCZZA Ed.16 81 / 778


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


82 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 83 / 778


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

84 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 85 / 778


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


86 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 87 / 778


88 / 778 3BK 21618 AAAA PCZZA Ed.16

7 Class 39: BSC-SW-ANOMALY Alarms


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

3BK 21618 AAAA PCZZA Ed.16 89 / 778


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.


9130 BSC

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


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.

90 / 778 3BK 21618 AAAA PCZZA Ed.16


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.


9130 BSC




Loss No No No No No




3BK 21618 AAAA PCZZA Ed.16 91 / 778


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.


9130 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




92 / 778 3BK 21618 AAAA PCZZA Ed.16


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.


9130 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




3BK 21618 AAAA PCZZA Ed.16 93 / 778


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




94 / 778 3BK 21618 AAAA PCZZA Ed.16

8 Class 42: TELECOM Alarms


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

3BK 21618 AAAA PCZZA Ed.16 95 / 778


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.


9130 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


96 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 97 / 778


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 T17 remains activated after receipt of an overloadmessage, it inhibits the effect of any further overload messages.When timer T17 expires, overload messages provoke traffic reductionagain. When A-FLEX is activated, the alarm which applies is [42,16]MSC-TRAFFIC-REDUCTION, number 1


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

98 / 778 3BK 21618 AAAA PCZZA Ed.16


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


9130 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


3BK 21618 AAAA PCZZA Ed.16 99 / 778



[42,3] START−RESET

Alarmsolved

Alarm persists?

no


yes

Trigger action on MSC side


Local communication alarm events?

yes

no

100 / 778 3BK 21618 AAAA PCZZA Ed.16


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.


9130 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


3BK 21618 AAAA PCZZA Ed.16 101 / 778



[42,7] NO−RESET−CIC

Alarmsolved

Alarm persists?

no


yes

Trigger CIC recovery action at MSC side


Transmission or trunk alarm events?

yes

no

102 / 778 3BK 21618 AAAA PCZZA Ed.16


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.


9130 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

3BK 21618 AAAA PCZZA Ed.16 103 / 778


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.


9130 BSC

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


104 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

9130 Evolution or 9120 BSC?

9120 BSC9130 BSC Evolution


3BK 21618 AAAA PCZZA Ed.16 105 / 778


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


9130 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


106 / 778 3BK 21618 AAAA PCZZA Ed.16



[42,13] BSC−TRAFFIC−REPORT

Alarmsolved

Alarm persists?

no


yes

Analyze additional information bytes


Related alarm events?

yes

no

3BK 21618 AAAA PCZZA Ed.16 107 / 778


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. Cause 6: MFS version is changed.Cause 7: BSC could not receive STATE CHANGE ACK from MFS intime. Cause 8.TSM_GPRS start the Abis configuration indicaiton.Normally there will be a Abis configuration indication ACK comes formMFS as feedback, but if there is no Abis configuration indication ACK,CAUSE 8 raised.


9130 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

108 / 778 3BK 21618 AAAA PCZZA Ed.16



None - an autonomous reset is triggered.

3BK 21618 AAAA PCZZA Ed.16 109 / 778


8.9 [42,15] TCH-RM-FAULT

specificProblems TELECOM [42] TCH-RM-FAULT [15]

eventType Equipment



Alarm Description This alarm happens when the TCH-RM processes on both OMCPare faulty


Impact on System This alarm is issued because there happened a state change ofTCH-RM DTC.Since the TCH-DTC pairs handles calls, all calls are lost and all cellscannot anymore establish calls. All these cells are disabled.


Loss YES YES YES YES NO

Degradation NO NO NO NO NO


Contact System Support

110 / 778 3BK 21618 AAAA PCZZA Ed.16


8.10 [42,16] MSC-TRAFFIC-REDUCTION

specificProblems TELECOM [42] MSC-TRAFFIC-REDUCTION [16]


probableCause congestion


Alarm Description This alarm indicates that the MSC load balance status has beenchanged for the feature A-Flex:the MSC is excluded or included in theload balance from BSC point view. Alarm number 1 is raised In casethe MSC is excluded due to overload; Alarm number 2 is raised incase the MSC is excluded due to the operator requested off-loading;Alarm number 3 is raised in case the MSC is excluded due to theTelecom reset


Impact on System If begin alarm reported, the SBL will change to FIT, if end alarmreported, the SBL will change to IT.


Loss No No Yes No No


3BK 21618 AAAA PCZZA Ed.16 111 / 778



[46, 12] MSC−TRAFFIC−REDUCTION

Alarm Type?

None − an autonomous overload reaction is triggered

Alarm triggered by the operator

1 2

3

Alarmsolved

Alarm persists?

no


yes

Trigger action on MSC side


Local communication alarm events?

yes

no

112 / 778 3BK 21618 AAAA PCZZA Ed.16

9 Class 43: CELL Alarms


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

3BK 21618 AAAA PCZZA Ed.16 113 / 778


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.


9130 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, ifBCCH channel is recovered, the SBL state will change to IT, if BCCHchannel isn’t recovered, the SBL state will change to FLT.


Loss No Yes Yes Yes No


114 / 778 3BK 21618 AAAA PCZZA Ed.16



[43,0] LOSS−OF−BCCH

Alarmsolved

Alarm persists?

no


yes

Wait 5 min (BCCH recovery ongoing)

Solve this alarmsRelatedBTS alarms?

yes

no

Alarm persists?

no

yes

Solve this alarmsRelated

transmission alarms?

yes

no

Alarm persists?

no

yes

Solve this alarmsRelatedBSC alarms?

yes

no

Alarm persists?

no

yes

Solve this problemError

message in follow up window?

yes

no

Lock / unlock Cell in RNUSM

Lock / unlock RA

Modify BCCH frequency

Alarm persists?

Alarm persists?

Alarm persists?

Alarmsolved

yes

yes

no

no

no

3BK 21618 AAAA PCZZA Ed.16 115 / 778


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.


9130 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 involvedin the reconfiguration. See Consequences of an SBL StateChange,if SDCCH channel is recovered, the SBL state will change to IT, ifSDCCH channel isn’t recovered, the SBL state will change to FIT.


Loss No No No No No

Degradation No Yes Yes Yes No

116 / 778 3BK 21618 AAAA PCZZA Ed.16



[43,1] LOSS−OF−SDCCH

Alarmsolved

Alarm persists?

no


yes


Trigger maintenance action on that alarm(s)

RelatedBTS alarm

events?

yes

no

3BK 21618 AAAA PCZZA Ed.16 117 / 778


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.


9130 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,the SBL state will change to FIT.


Loss No No No No No

Degradation No Yes No Yes No

118 / 778 3BK 21618 AAAA PCZZA Ed.16



[43,2] LOSS−OF−TCH

Alarmsolved

no


yes

Identify the faulty RSL / TRE in USD window

yes

no

More TRX as TRE/RSL?

Correct cell configuration

Alarm persists?

Lock / unlock the faulty RSL / TRE

Alarm persists?

Related BTS alarms?

Related BSC alarms?

Solve this alarms

Solve this alarms

Alarm persists?

Alarm persists?

yes

yes

yes

yes

no

no

no

no

no

yes

3BK 21618 AAAA PCZZA Ed.16 119 / 778


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.


9130 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


120 / 778 3BK 21618 AAAA PCZZA Ed.16



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


yes

Alarmsolved

Alarm persists?

no

yes

Solve this alarmsRelatedBTS alarms?

yes

no

Alarm persists?

no

yes

Solve this alarmsRelated

transmission alarms?

yes

no

Alarm persists?

no

yes

Solve this alarmsRelatedBSC alarms?

yes

no

Identify the faulty RSL / TRE in USD window

Lock / unlock the faulty RSL / TRE

Reset related TCU

Alarm persists?

Alarm persists?

no

yes

Solve this problemError

message in follow up window?

yes

no

Lock / unlock Cell in RNUSM

Lock / unlock RAAlarm

persists?Alarm

persists?

yes

no

no

Delete / recreate cell

Alarm persists?

Alarmsolved

yes

yes

no

no

All BTS cells are impacted?

Reset BTSAlarm

persists?no

no

yes


yes

OML failed? Lock/Unlock OML

OML failed? Check BTS and power supply

Alarm persists?

no

no

noyesyes

yes

3BK 21618 AAAA PCZZA Ed.16 121 / 778


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 9120 BSC*There is a change of the RACH parameters on cell level (dynamicRACH).


9130 BSC

Impact on System The SBL state remains unchanged.MSs belonging to the barred access classes can no longer accessthe system.


Loss No No No No No


122 / 778 3BK 21618 AAAA PCZZA Ed.16



[43,4] CELL−TRAFFIC−REPORT

Alarmsolved

Alarm persists?


yes


Trigger maintenance action on that alarm(s)

Related BTS alarm events?

yes

no

BTS−OVERLOAD alarm coming

from BCCH TRX?

yes

no

ReduceBTS load

Solve that alarm(s)

TCU processor overload

alarm events?*

yes

Correct RACH parameters

Dynamic RACH parameters on

cell level OK?

no

no

yes

no

3BK 21618 AAAA PCZZA Ed.16 123 / 778


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.


9130 BSC

Impact on System The SBL state remains unchanged.MSs belonging to the barred access classes can no longer accessthe system.


Loss No No No No No


124 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 125 / 778


9.7 [43,6] TRX-MAPPING-CHANGE

specificProblems CELL [43] TRX-MAPPING-CHANGE [6]

eventType –

probableCause congestion/network fail


Alarm Description This event alarm is indicate TRX/RSL mapping is changed or not.


9130 BSC

Impact on System No impact.


Loss no no no no no

Degradation no no no no no


None.

126 / 778 3BK 21618 AAAA PCZZA Ed.16


9.8 [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 to a9100 TRE, the pool has to be truncated. HSDS state is changed toPartially 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.


9130 BSC

Impact on System No impact on BTS_TEL.

If HSDS state is Degraded, this cell cannot support the HSDS(EGPRS); the running PS in EGPRS is degraded to GPRS.If HSDS state is Partially Degraded, this cell still supports the HSDS.


Loss No No No No No

Degradation No Yes No No No

3BK 21618 AAAA PCZZA Ed.16 127 / 778



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

128 / 778 3BK 21618 AAAA PCZZA Ed.16

10 Class 44: BTS-OM Alarms


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

3BK 21618 AAAA PCZZA Ed.16 129 / 778


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.


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




130 / 778 3BK 21618 AAAA PCZZA Ed.16



[44,0] AUDIT−FAIL

Alarmsolved

Alarm persists?

no


yes

Reset BTS or OML TCU

OML up?yesno No operator

action required

3BK 21618 AAAA PCZZA Ed.16 131 / 778


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.


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




132 / 778 3BK 21618 AAAA PCZZA Ed.16



[44,1] PROTOCOL−FAIL

Alarm persists?

no


yes

yesno

Alarm solved

Other BTS alarms are active?

Solve BTS alarms

OML link is up?Lock/Unlock OML and

reset OML TCUOML link is up?

Check BTS and power supply

yes

yes

no

no

3BK 21618 AAAA PCZZA Ed.16 133 / 778


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.


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




134 / 778 3BK 21618 AAAA PCZZA Ed.16



[44,2] RECONFIG−FAIL

Alarmsolved

Alarm persists?

no


yes

Reset BTS or OML TCU

OML up?

yes

no

No operator action required

3BK 21618 AAAA PCZZA Ed.16 135 / 778


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.


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




136 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 137 / 778


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.


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




138 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 139 / 778


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.


9130 BSC





140 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 141 / 778


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.


9130 BSC





142 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 143 / 778


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.


9130 BSC



Loss No No No No No



[44,10] ABORT−FAIL


Retrigger remove action

Alarmsolved

yes

Alarm persists?

no

144 / 778 3BK 21618 AAAA PCZZA Ed.16


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.


9130 BSC



Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 145 / 778



146 / 778 3BK 21618 AAAA PCZZA Ed.16


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.


9130 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

3BK 21618 AAAA PCZZA Ed.16 147 / 778


148 / 778 3BK 21618 AAAA PCZZA Ed.16

11 Class 45: CHANNEL Alarms


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

3BK 21618 AAAA PCZZA Ed.16 149 / 778


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.


9130 BSC



Loss No No No No No

Degradation Yes No Yes Yes No

150 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 151 / 778


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.


9130 BSC



Loss No No No No No


152 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 153 / 778


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.


9130 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


154 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 155 / 778


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.


9130 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


156 / 778 3BK 21618 AAAA PCZZA Ed.16



[45,3] MSC−CIC−UNKNOWN

Lock aossc. A−trunk




Alarmsolved

Alarm persists?

no

yes

3BK 21618 AAAA PCZZA Ed.16 157 / 778


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


9130 BSC



Loss No No No No No



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

Lock aossc. ACH




Alarmsolved

Alarm persists?

no

yes

158 / 778 3BK 21618 AAAA PCZZA Ed.16

12 Class 46: BACKUP-MEDIUM Alarms


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

3BK 21618 AAAA PCZZA Ed.16 159 / 778


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 36.4) for the byte definition.

160 / 778 3BK 21618 AAAA PCZZA Ed.16


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.


9130 BSC

Impact on System The SBL state remains unchanged.Some previously acknowledged commands are lost.

CPRA (DUPLEX): Performance Management

Telecom functions are not affected, but PM is impacted.

If some updates are to be done on the active CPRA, then the 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.

3BK 21618 AAAA PCZZA Ed.16 161 / 778



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


162 / 778 3BK 21618 AAAA PCZZA Ed.16


12.3 [46,2] UNSYNC-OWN-CORR

specificProblems BACKUP-MEDIUM [46] UNSYNC-OWN-CORR [2]




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


9130 BSC

Impact on System The SBL state remains unchanged


Loss no no no no no

Degradation no no no no yes



3BK 21618 AAAA PCZZA Ed.16 163 / 778


12.4 [46,3] SYNC-FAIL

specificProblems BACKUP-MEDIUM [46] SYNC-FAIL [3]




Alarm Description This alarm occurs when it’s trying to synchronize the unsynchronizedtwin files on both OCPR and SCPR during initilization period, but theresult is unsucessful. And the twin file status is still keeping as theoriginal status without unchange.


9130 BSC

Impact on System The SBL state remains unchanged


Loss no no no no no

Degradation no no no no yes



164 / 778 3BK 21618 AAAA PCZZA Ed.16


12.5 [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 – – – – –


3BK 21618 AAAA PCZZA Ed.16 165 / 778



[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

166 / 778 3BK 21618 AAAA PCZZA Ed.16


12.6 [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 – – – – –


3BK 21618 AAAA PCZZA Ed.16 167 / 778



[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

168 / 778 3BK 21618 AAAA PCZZA Ed.16


12.7 [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 – – – – –


3BK 21618 AAAA PCZZA Ed.16 169 / 778



[46,6] DUT−ROLLBACK−FAIL

Re−trigger the data update


yes

Alarm persists?

no Alarmsolved

170 / 778 3BK 21618 AAAA PCZZA Ed.16


12.8 [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 – – – – –


3BK 21618 AAAA PCZZA Ed.16 171 / 778



[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

172 / 778 3BK 21618 AAAA PCZZA Ed.16


12.9 [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 – – – – –


3BK 21618 AAAA PCZZA Ed.16 173 / 778



[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

174 / 778 3BK 21618 AAAA PCZZA Ed.16

13 Class 47: GLOBAL-BSC Alarms


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

3BK 21618 AAAA PCZZA Ed.16 175 / 778


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.


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

176 / 778 3BK 21618 AAAA PCZZA Ed.16


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.


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

3BK 21618 AAAA PCZZA Ed.16 177 / 778


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 9120 BSC or the Ethernet link for 9130 BSCEvolution is down* The OMC-R is not active.


9130 BSC



Loss No No No No No



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

178 / 778 3BK 21618 AAAA PCZZA Ed.16


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 9120 BSC or the Ethernet link for 9130 BSCEvolution is down* The OMC-R is not active.


9130 BSC



Loss No No No No No



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

3BK 21618 AAAA PCZZA Ed.16 179 / 778


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.


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

180 / 778 3BK 21618 AAAA PCZZA Ed.16


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.


9130 BSC



Loss No No No No No



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

3BK 21618 AAAA PCZZA Ed.16 181 / 778


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

182 / 778 3BK 21618 AAAA PCZZA Ed.16


13.8 [47,9] CBC-CONNECTION-FAILURE

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

eventType Equipment



Alarm Description The Alarm is reported in the following cases:1. Network connection Timeout2. Network connection Refused.3 .The CBC O/G association setup timeout4. The CBC O/G association setup refused(invalid ID or password)5. CBC O/G association prematurely terminated internally or externally


9130 BSC

Impact on System CBC function can’t be implemented and consequences of an SBLState Change.


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 183 / 778



[47,9] CBC−CONNECTION−FAILURE

Correct network configuration

Launch SMS−CB CMD−MODE STOP

then START CMD−MODE


noNetwork configuration

is ok?

no

yes

Alarmsolved

Alarm persists?

no

yes

Alarm persists?

yes

184 / 778 3BK 21618 AAAA PCZZA Ed.16


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.


9130 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

3BK 21618 AAAA PCZZA Ed.16 185 / 778


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.


9130 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

186 / 778 3BK 21618 AAAA PCZZA Ed.16


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.


9130 BSC

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


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 187 / 778



[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

188 / 778 3BK 21618 AAAA PCZZA Ed.16


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

3BK 21618 AAAA PCZZA Ed.16 189 / 778


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.


9130 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


190 / 778 3BK 21618 AAAA PCZZA Ed.16



[47,15] SWRPL−IN−PROGRESS

If no audit is started, trigger new audit


Alarmsolved

Alarm persists?

no

yes

Wait for new autonomous audit

3BK 21618 AAAA PCZZA Ed.16 191 / 778


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.


9130 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


192 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 193 / 778


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.




194 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 195 / 778


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


196 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 197 / 778


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



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

198 / 778 3BK 21618 AAAA PCZZA Ed.16


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


3BK 21618 AAAA PCZZA Ed.16 199 / 778



[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

Replace OMCPboard that is active when alarm occurs

Alarm persists?

yes

no

200 / 778 3BK 21618 AAAA PCZZA Ed.16


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


3BK 21618 AAAA PCZZA Ed.16 201 / 778





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

202 / 778 3BK 21618 AAAA PCZZA Ed.16


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 than1000s with the time server defined in the peer entities.


Impact on System After NTP drift exceeded 1000 sec. MXBSC started to reset that leadto traffic outage. The impacted SBL state is not changed.

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.




3BK 21618 AAAA PCZZA Ed.16 203 / 778




BSC


are ok?


yes

yes


Alarm persists?

Alarm persists?

no

no

Alarmsolved

no

no

no

yes

yes

Alarm persists?

[47, 22] NTP DRIFT TIME EXCEEDED


Replace OMCPboard that is active when alarm occurs

yes

204 / 778 3BK 21618 AAAA PCZZA Ed.16


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


3BK 21618 AAAA PCZZA Ed.16 205 / 778



[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

206 / 778 3BK 21618 AAAA PCZZA Ed.16


13.22 [47,24] MUX-SECTOR-NOT-COMP-2ABIS

specificProblems GLOBAL-BSC [47] MUX-SECTOR-NOT-COMP-2ABIS [24]




Alarm Description During TRE allocation, there is no enough space on primary abis link,the TRE cannot be allocated on secondary abis link because themultiplexing mode is ’per sector’


9130 BSC

Impact on System The SBL state remains unchangedThe TRE will not be operational, no TS will be allocated


Loss NO NO NO NO NO

Degradation NO YES YES YES YES


[47,24] MUX−SECTOR−NOT−COMP−2ABIS


Alarmsolved

Alarm persists?

no

yes

Delete existing TRE(s)

Re−create TRE(s) according to Abis

capacity

3BK 21618 AAAA PCZZA Ed.16 207 / 778


13.23 [47,25] TC-HW-RESYNCH

specificProblems GLOBAL-BSC [47] TC-HW-RESYNCH [25]




Alarm Description Consider new MT120 boards introduction. The BSC has to discoverthem at MT120 replacement at TC extension or at periodical audit. Atthe end of the discovery phase, if the BSC detects any discrepancieswith the DLS, the BSC sends an alarm to the OMC.




Loss No No No No NO

Degradation NO NO NO NO Yes


[47, 25] TC−HW−RESYNCH

Alarmsolved

yes

Alarm persists?

no


208 / 778 3BK 21618 AAAA PCZZA Ed.16


13.24 [47,26] TRAU-CP-OUT-OF-RANGE

specificProblems GLOBAL-BSC [47] TRAU-CP-OUT-OF-RANGE [26]




Alarm Description ID OF MT120 is our of valid range


Impact on System ID OF MT120 is our of valid range


Loss No No No No No



[47, 26] TRAU−CP−OUT_OF−RANGE

Alarmsolved

yes

Alarm persists?

no


Check TC rack at TC side

3BK 21618 AAAA PCZZA Ed.16 209 / 778


13.25 [47,27] TRAU-CP-ON-DEDICATED-ATER

specificProblems GLOBAL-BSC [47] TRAU-CP-ON-DEDICATED-ATER [27]




Alarm Description ID of TRAU-CP is on dedicated PS AterMUX


Impact on System ID of TRAU-CP is on dedicated PS AterMUX


Loss no no no no no



[47, 27] TRAU−CP−ON−DEDICATED−ATER

Alarmsolved

yes

Alarm persists?

no


Check Mt120 at TC side

210 / 778 3BK 21618 AAAA PCZZA Ed.16


13.26 [47,28] TRAU-CP-DOUBLE-DECLARED

specificProblems GLOBAL-BSC [47] TRAU-CP-DOUBLE-DECLARED [28]


probableCause equipmentIdentifierDuplication


Alarm Description This alarm is sent when the atermux ID of MT120 is the same thatof another MT120.




Loss No No No No NO



[47, 28] TRAU−CP−DOUBLE−DECLARED

Alarmsolved

yes

Alarm persists?

no


3BK 21618 AAAA PCZZA Ed.16 211 / 778


13.27 [47,30] TRANS-CONFIG-IMPOSSIBLE

specificProblems GLOBAL-BSC [47] TRANS-CONFIG-IMPOSSIBLE [30]

eventType Equipment



Alarm Description This alarm is sent during BSC startup and neither of the 2 TPGSMshas the required capabilities. BSC does not configure TP. The boardsare still running but no RSL comes up as TP is not configured


Impact on System FIT when alarm begins , IT when alarm ends


Loss YES YES YES YES NO



[47,30] TRANS−CONFIG−IMPOSSIBLE


yes

Replace TP board with correct version

On−site

Alarm persists?

noAlarmsolved

212 / 778 3BK 21618 AAAA PCZZA Ed.16


13.28 [47,40] CS-TEL-TEST-NOK

specificProblems GLOBAL-BSC [47] CS-TEL-TEST-NOK [40]




Alarm Description Upon the CS telecome outage suspecting for the whole BSC, thetelecom test for Abis interface is triggered and the test result is NOK.


Impact on System The SBL BSC will change to FIT.


Loss no no no no no



[47, 40] CS−TEL−TEST−NOK


yes

Check the DLS and replace it if not OK.

Alarm persists?

noAlarmsolved

3BK 21618 AAAA PCZZA Ed.16 213 / 778


13.29 [47,41] PS-TEL-TEST-NOK

specificProblems GLOBAL-BSC [47] PS-TEL-TEST-NOK [41]




Alarm Description Upon the PS telecome outage suspecting for the whole BSC, thetelecom test for BSCGP interface is triggered and the test result isNOK.


Impact on System The SBL BSC will change to FIT.


Loss no no no no no


214 / 778 3BK 21618 AAAA PCZZA Ed.16



[47, 41] PS−TEL−TEST−NOK


yes

Perform an OMCP takeover.

Alarm persists?

no

Alarmsolved

Re−initialize GPRS.

Alarm persists?

no

yes

3BK 21618 AAAA PCZZA Ed.16 215 / 778


13.30 [47,103] BTS-TC-RESHUFFLING-FAIL

specificProblems GLOBAL-BSC [47] BTS-TC-RESHUFFLING-FAIL [103]


probableCause SoftwareProgramError

perceivedSeverity Indetermidate

Alarm Description Indicate BTS_TC_RESHUFFLING is fail.


Impact on System IP bts is not successfully mapped on TC


Loss no no no no no



[47, 103] BTS−TC−RESHUFFLING−FAIL

Alarmsolved

yes

Alarm persists?

no


Trigger the reshuffling operation

again

216 / 778 3BK 21618 AAAA PCZZA Ed.16


13.31 [47,200] N7-CONF-FAILURE

specificProblems GLOBAL-BSC [47] N7-CONF-FAILURE [200]

eventType Equipment


perceivedSeverity Major(PMA)

Alarm Description wrong N7 over IP related configuration in DLS, for example invalidIP@, port number and so on.


Impact on System No call can be allowed


Loss No No Yes(Ater) Yes No



[47, 200] N7−CONF−FAILURE

Alarmsolved

yes

Alarm persists?

no


Correct the wrong configuration in DLS

3BK 21618 AAAA PCZZA Ed.16 217 / 778


218 / 778 3BK 21618 AAAA PCZZA Ed.16

14 Class 48: TR-OM Alarms


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

3BK 21618 AAAA PCZZA Ed.16 219 / 778


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 No No No No No



[48,0] AUDIT−FAIL

Reset TSC


Alarmsolved

Alarm persists?

no

yes

220 / 778 3BK 21618 AAAA PCZZA Ed.16


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 No No No No No



[48,1] PROTOCOL−FAIL

Reset TSC


Alarmsolved

Alarm persists?

no

yes

TSL is down only:

3BK 21618 AAAA PCZZA Ed.16 221 / 778


222 / 778 3BK 21618 AAAA PCZZA Ed.16

15 Class 49: ALERTER Alarms


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

3BK 21618 AAAA PCZZA Ed.16 223 / 778


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.


9130 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


224 / 778 3BK 21618 AAAA PCZZA Ed.16



[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)


3BK 21618 AAAA PCZZA Ed.16 225 / 778


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.


9130 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


226 / 778 3BK 21618 AAAA PCZZA Ed.16



[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)



3BK 21618 AAAA PCZZA Ed.16 227 / 778


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.


9130 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



228 / 778 3BK 21618 AAAA PCZZA Ed.16


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.


9130 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



3BK 21618 AAAA PCZZA Ed.16 229 / 778


230 / 778 3BK 21618 AAAA PCZZA Ed.16

16 Class 50: BSC EXTERNAL Alarms


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

3BK 21618 AAAA PCZZA Ed.16 231 / 778


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 no no no no no


232 / 778 3BK 21618 AAAA PCZZA Ed.16



[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

3BK 21618 AAAA PCZZA Ed.16 233 / 778


16.2 [50,2] EXT-ALARM-2


eventType Equipment







Loss no no no no no


234 / 778 3BK 21618 AAAA PCZZA Ed.16




no


External alarm

persists?

yes

Alarmsolved


cause?

no

Trigger customer−specific action according to



On−site


if required.

On−site


On−site

3BK 21618 AAAA PCZZA Ed.16 235 / 778


16.3 [50,3] EXT-ALARM-3


eventType Equipment







Loss no no no no no


236 / 778 3BK 21618 AAAA PCZZA Ed.16




no


External alarm

persists?

yes

Alarmsolved


cause?




On−site


if required.

On−site


On−siteno

3BK 21618 AAAA PCZZA Ed.16 237 / 778


16.4 [50,4] EXT-ALARM-4


eventType Equipment







Loss no no no no no


238 / 778 3BK 21618 AAAA PCZZA Ed.16




no


External alarm

persists?

yes

Alarmsolved


cause?

no




On−site


if required.

On−site


On−site

3BK 21618 AAAA PCZZA Ed.16 239 / 778


16.5 [50,5] EXT-ALARM-5


eventType Equipment







Loss no no no no no


240 / 778 3BK 21618 AAAA PCZZA Ed.16




no


External alarm

persists?

yes

Alarmsolved


cause?

no




On−site


if required.

On−site


On−site

3BK 21618 AAAA PCZZA Ed.16 241 / 778


16.6 [50,6] EXT-ALARM-6


eventType Equipment







Loss no no no no no


242 / 778 3BK 21618 AAAA PCZZA Ed.16




no


External alarm

persists?

yes

Alarmsolved


cause?

no




On−site


if required.

On−site


On−site

3BK 21618 AAAA PCZZA Ed.16 243 / 778


16.7 [50,7] EXT-ALARM-7


eventType Equipment







Loss no no no no no


244 / 778 3BK 21618 AAAA PCZZA Ed.16




no


External alarm

persists?

yes

Alarmsolved


cause?

no




On−site


if required.

On−site


On−site

3BK 21618 AAAA PCZZA Ed.16 245 / 778


16.8 [50,8] EXT-ALARM-8


eventType Equipment







Loss no no no no no


246 / 778 3BK 21618 AAAA PCZZA Ed.16




no


External alarm

persists?

yes

Alarmsolved


cause?

no




On−site


if required.

On−site


On−site

3BK 21618 AAAA PCZZA Ed.16 247 / 778


16.9 [50,9] EXT-ALARM-9


eventType Equipment







Loss no no no no no


248 / 778 3BK 21618 AAAA PCZZA Ed.16




no


External alarm

persists?

yes

Alarmsolved


cause?

no




On−site


if required.

On−site


On−site

3BK 21618 AAAA PCZZA Ed.16 249 / 778


16.10 [50,10] EXT-ALARM-10


eventType Equipment







Loss no no no no no


250 / 778 3BK 21618 AAAA PCZZA Ed.16




no


External alarm

persists?

yes

Alarmsolved


cause?

no




On−site


if required.

On−site


On−site

3BK 21618 AAAA PCZZA Ed.16 251 / 778


252 / 778 3BK 21618 AAAA PCZZA Ed.16

17 Class 51: SWITCH G2 Alarms


This section defines the BSC alarms for the Class 51: SWITCH G2 alarm class.

3BK 21618 AAAA PCZZA Ed.16 253 / 778


17.1 [51,0] TRANSIENT-FAIL

specificProblems SWITCH G2 [51] TRANSIENT-FAIL [0]

eventType Equipment



Alarm Description The switch detected a momentary fault.


Impact on System The SBL state remains unchanged. The switch element remainsIT/FIT. Some interference is likely on current calls through the switch.See Consequences of an SBL State Change.


Loss No No No No No



[51,0] TRANSIENT−FAIL

noContact

System Support

Alarm persists?

yes

Alarmsolved

yesSWITCH−

FAILalarm

events?

no

Solve SWITCH−FAIL alarm(s)


254 / 778 3BK 21618 AAAA PCZZA Ed.16


17.2 [51,1] SWITCH-FAIL

specificProblems SWITCH G2 [51] SWITCH-FAIL [1]

eventType Equipment



Alarm Description The switch element is isolated from the operational software due to apersistent fault.


Impact on System If an alarm is internally present on a link, the switch connected to thelink is updated to FIT. If the number of faulty links on the switch is >=(number of links present on the switch -1) /2, the switch is updated toFOS. See Consequences of an SBL State Change.


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 255 / 778


17.2.1 Corrective Actions

17.2.1.1 Corrective Actions for Write Violation Overflow, Loss of Sync Overflowand Init Fail Alarms

[51,1] SWITCH−FAIL

no


Alarm persists?

yes

Alarmsolved

Check cabling to switch, replace

cabling if required.


Two alarms are generated for a link, one alarm for each affected switch.

Lock faultySWITCH

Unlock faultySWITCH

On−site

For Write Violation Overflow, Loss of Sync Overflow and Init Fail alarms:

Figure 2: SWITCH-FAIL: Corrective Actions for Write Violation Overflow, Lossof Sync Overflow and Init Fail Alarms

256 / 778 3BK 21618 AAAA PCZZA Ed.16


17.2.1.2 Corrective Actions for Loss of Sync Alarm


no


Alarm persists?

yes

Alarmsolved

Check cabling to switch, replace

cabling if required.



Lock faultySWITCH

Unlock faultySWITCH

On−site

For Loss of Sync alarms:

Replace/repair clock generator/repeater

noLast clock generator/repeater

operational?

yes

Replace/repair clock extractor

noLast clock extractor

operational?

yes

Trigger repar action at MSC side

noMSC/trunk provides clock pulse

to BSC?

yes

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

3BK 21618 AAAA PCZZA Ed.16 257 / 778


17.2.1.3 Corrective Actions for HW Fault Alarm


no


Alarm persists?

yes

Alarmsolved

Check links to faulty switch,

replace cabling if required.



On−site

For HW Fault alarms:

On−site

Replace reported faulty switch

Alarmsolved

yesSwitchoperational?

no

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

258 / 778 3BK 21618 AAAA PCZZA Ed.16


17.3 [51,2] ROUTINE-TEST-REP

specificProblems SWITCH G2 [51] ROUTINE-TEST-REP [2]

eventType Equipment



Alarm Description A network switch link failure was detected during a routine networktunnel test. The link remains available to the operational software.


Impact on System The SBL state remains unchanged. The switch is still able to carrytraffic. However no operator actions can be performed and will beNACK with the Error Code busy by rt. In the case of a routine test of alink and a switch and the test executed, all Test-raw-data is filled in.


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 259 / 778



[51,2] ROUTINE−TEST−REP

Analyze additionalinformation bytes

Alarmsolved

yes

Alarm persists?

no


no

On−site

Replace suspected switch

On−site

Repair/replace hardware

yes

Switch hardware

OK?

no

On−site

Repair/replace hardware

yes

Switch cabling

OK?


260 / 778 3BK 21618 AAAA PCZZA Ed.16


17.4 [51,3] GLOBAL-ROUTINE-TEST-REP

specificProblems SWITCH G2 [51] GLOBAL-ROUTINE-TEST-REP [3]

eventType Equipment



Alarm Description This alarm is sent to indicate both successful and unsuccessful testresults. A global network routine test can fail because:* One cycle of the routine test failed, or* One cycle of the routine test failed indicating a link where the erroroccurred.

Note: this alarm can only be sent by a B8 (or previous release) BSS.



The switch is still able to carry traffic. However no operator actions canbe performed and will be NACK with the error code busy by rt.In the case of a global routine test of a link and a switch and the testexecuted, all Test-raw-data is filled in.

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


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 261 / 778



[51,3] GLOBAL−ROUTINE−TEST−REP

Solve ROUTINE−TEST−REP alarm

Alarmsolved

yes

Alarm persists?

no


ROUTINE−TEST−REP

alarm events?

no

yes

Wait for next routine test report

262 / 778 3BK 21618 AAAA PCZZA Ed.16

18 Class 52: BSC CLOCK Alarms


This section defines the BSC alarms for the Class 52: BSC CLOCK alarm class.

3BK 21618 AAAA PCZZA Ed.16 263 / 778


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

specificProblems BSC CLOCK [52] LOSS-OF-SEL-CLK-INP [0]

eventType Equipment



Alarm Description The CLK-GEN detects that all external references have failed. Inaddition, the local clock has also failed.


Impact on System See consequences of an SBL state change.


Loss – – – – –


264 / 778 3BK 21618 AAAA PCZZA Ed.16



[52,0] LOSS−OF−SEL−CLK−INP

Solve Ater alarm(s) first

yes

Alarm persists?

no


Ateralarm

events?

no

yes

Solve DTC alarm(s)

DTCalarm

events?

no

yes

Alarmsolved

yes

Alarm persists?

no

On−site

Replace Ater trunk extracted

by the 3 DTCs

3BK 21618 AAAA PCZZA Ed.16 265 / 778


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

specificProblems BSC CLOCK [52] LOSS-OF-CLK-GEN-FN [1]

eventType Equipment



Alarm Description The CLK-GEN is lost due to one of the following: *Reference selectorfailure * PLL out of range * Absence of own clock * Watchdog timerexpiry * Access failure.




Loss – – – – –



[52,1] LOSS−OF−CLK−GEN−FN

Alarmsolved

Alarm persists?

no


Replace suspected Clock RIT

Identify Ater−Mux reference clock and

unplug it

Alarm persists?

yes

yes

no

266 / 778 3BK 21618 AAAA PCZZA Ed.16


18.3 [52,2] SWITCH-TO-LOCAL-CLK

specificProblems BSC CLOCK [52] SWITCH-TO-LOCAL-CLK [2]

eventType Equipment



Alarm Description Due to loss of all external clocks, the CLK-GEN has selected a localclock.


Impact on System If only one CLK-GEN has detected this situation, there is no impact onthe clock distributed throughout the BSC as the SYS-BCLA will selectthe clock provided by the other CLK-GEN.If both CLK-GEN detect this problem, then BSC sends the alarm[52,6], which corresponds to the usage in BSC of a local clock. Seeconsequences of an SBL state change.


Loss – – – – –


3BK 21618 AAAA PCZZA Ed.16 267 / 778



[52,2] SWITCH−TO−LOCAL−CLK

Solve DTC/Ater alarm(s) first

Alarmsolved

yes

Alarm persists?

no


DTC/ Ateralarm

events?

no

yes

Solve transmission alarm(s)

Transmissionalarm

events?

no

yes

Trigger clock source checks at MSC side

268 / 778 3BK 21618 AAAA PCZZA Ed.16


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

specificProblems BSC CLOCK [52] LOSS-OF-SYSTEM-CLOCK-A [3]

eventType Equipment



Alarm Description The System Clock A failure is detected by CLK-REP.


Impact on System See consequences of an SBL state change


Loss – – – – –



[52,3] LOSS−OF−SYSTEM−CLOCK−A

Alarmsolved

yes

Alarm persists?

no


On−site

Replace suspected

System Clock A

The rack number is indicated by the CLK−REP SBL number

3BK 21618 AAAA PCZZA Ed.16 269 / 778


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

specificProblems BSC CLOCK [52] LOSS-OF-SYSTEM-CLOCK-B [4]

eventType Equipment



Alarm Description A System Clock B failure is detected by CLK-REP.


Impact on System See consequences of an SBL state change


Loss – – – – –



[52,4] LOSS−OF−SYSTEM−CLOCK−B

Alarmsolved

yes

Alarm persists?

no


On−site

Replace suspected

System Clock B

The rack number is indicated by the CLK−REP SBL number

270 / 778 3BK 21618 AAAA PCZZA Ed.16


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

specificProblems BSC CLOCK [52] LOSS-OF-CLK-DISTR-FN [5]

eventType Equipment



Alarm Description The CLK-REP is lost due to one of the following: *Reference selectorfailure * PLL out of range * Absence of own clock * Watchdog timerexpiry * Access failure.




Loss – – – – –



[52,5] LOSS−OF−CLK−DISTR−FN


Alarmsolved

yes

Alarm persists?

no


On−site

Replace suspected

Clock repeater

The rack number is indicated by CLK−REP SBL number.

3BK 21618 AAAA PCZZA Ed.16 271 / 778


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

specificProblems BSC CLOCK [52] BSC-RUN-ON-LOCAL-CLK [6]

eventType Equipment



Alarm Description This alarm is generated when the BSC is running on the local clock.


Impact on System The BTS cannot function correctly if using the local BSC clock.Depending on the difference between the local clock and the clockused on the remaining Ater links, the effect can be small (degradation,only retransmissions, alarms Slip-un-run, Slip-ov-run, various synchroalarms or can be very important (loss) preventing stable calls.


Loss – Yes(dependingon clockgap)

Yes(depending onclock gap)


–

Degradation – Yes(dependingon clockgap)



–

272 / 778 3BK 21618 AAAA PCZZA Ed.16



[52,6] BSC−RUN−ON−LOCAL−CLK

Solve DTC/Ater alarm(s) first

Alarmsolved

yes

Alarm persists?

no


DTC/Ateralarm

events?

no

yes

Solve transmission alarm(s)

Transmissionalarm

events?

no

yes

Trigger clock source checks at MSC side

3BK 21618 AAAA PCZZA Ed.16 273 / 778


18.8 [52,7] LOC-CLK-FAILURE

specificProblems BSC CLOCK [52] LOC-CLK-FAILURE [7]

eventType Equipment



Alarm Description Due to detection of the Local Clock Failure the CLK-GEN is degraded.




Loss – – – – –



[52,7] LOC−CLK−FAILURE


Alarmsolved

yes

Alarm persists?

no


On−site

Replace suspected Clock RIT

274 / 778 3BK 21618 AAAA PCZZA Ed.16

19 Class 53: BROADCAST BUS Alarms


This section defines the BSC alarms for the Class 53: BROADCAST BUSalarm class.

3BK 21618 AAAA PCZZA Ed.16 275 / 778


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

specificProblems BROADCAST BUS [53] LOSS-OF-ONE-BROAD-BUS-BSC [0]

eventType Equipment



Alarm Description The BSC has detected loss of one BC bus in the BSC.




Loss – – – – –



[53,0] LOSS−OF−ONE−BROAD−BUS−BSC

Alarmsolved

yes

Alarm persists?

no


On−site

Replace suspected RIT

The Broadcast Bus is indicated by the BC−SYS−BUS SBL number.

276 / 778 3BK 21618 AAAA PCZZA Ed.16


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

specificProblems BROADCAST BUS [53] LOSS-OF-BOTH-BROAD-BUS-BSC [1]

eventType Equipment



Alarm Description The BSC has detected loss of both broadcast buses in the BSC.


Impact on System There are significant telecom impacts: LAC paging mode is not workinganymore, thus preventing Mobile terminating calls. GPRS resetprocedure does not work anymore and leads to loss of GPRS traffic.For the consequences of an SBL state change, see Consequencesof an SBL State Change.


Loss – – – – –

Degradation – – – Yes Yes


[53,1] LOSS−OF−BOTH−BROAD−BUS−BSC

Alarmsolved

yes

Alarm persists?

no


On−site

G2: Replace both BCLA−SYS boards

3BK 21618 AAAA PCZZA Ed.16 277 / 778


19.3 [53,2] DMA-PROBLEM

specificProblems BROADCAST BUS [53] DMA-PROBLEM [2]




Alarm Description For BSC: The BSC has detected DMA problems in a high percentageof Ces in the BSC. For CPR/DTC/TCU: The BSC has detected a highnumber of DMA problems in the CE.




Loss – – – – –



[53,2] DMA−PROBLEM (CPR/DTC/TCU)

Alarmsolved

yesAlarm persists?


DMA−PROBLEM (BSC) alarm

events?

no

yes

On−site

Replace suspected

CPR/DTC/TCU

278 / 778 3BK 21618 AAAA PCZZA Ed.16


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

specificProblems BROADCAST BUS [53] LOSS-OF-ONE-BROAD-BUS-RACK [3]

eventType Equipment

probableCause LanError


Alarm Description The BSC has detected a loss of one broadcast bus on a RACK.




Loss – – – – –



[53,3] LOSS−OF−ONE−BROAD−BUS−RACK

Alarmsolved

yes

Alarm persists?

no


On−site


The Broadcast Bus is indicated by the BC_RACK_BUS SBL number.

3BK 21618 AAAA PCZZA Ed.16 279 / 778


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

specificProblems BROADCAST BUS [53] LOSS-OF-BOTH-BROAD-BUS-RACK [4]

eventType Equipment



Alarm Description The BSC has detected loss of both broadcast buses on a RACK.




Loss – – – – –



[53,4] LOSS−OF−BOTH−BROAD−BUS−RACK

Alarmsolved

yes

Alarm persists?

no


On−site

G2: Replace both BCLA boards

280 / 778 3BK 21618 AAAA PCZZA Ed.16


19.6 [53,5] DEGRAD-BROAD-BUS-RACK

specificProblems BROADCAST BUS [53] DEGRAD-BROAD-BUS-RACK [5]

eventType Equipment



Alarm Description The BSC has detected a degradation in the quality of one of thebroadcast buses on a RACK.




Loss – – – – –



[53,5] DEGRAD−BROAD−BUS−RACK

Alarmsolved

yes

Alarm persists?

no


On−site



3BK 21618 AAAA PCZZA Ed.16 281 / 778


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

specificProblems BROADCAST BUS [53] LOSS-OF-ONE-BROAD-BUS-CE [6]

eventType Equipment



Alarm Description The BSC has detected loss of one broadcast bus to a CE.


Impact on System No redundancy on broadcast bus. For the consequences of an SBLstate change, see Consequences of an SBL State Change.


Loss – – – – –



[53,6] LOSS−OF−ONE−−BROAD−BUS−CE


Alarmsolved

yes

Alarm persists?

no


On−site

Replace cabling to

suspected RIT


282 / 778 3BK 21618 AAAA PCZZA Ed.16


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

specificProblems BROADCAST BUS [53] LOSS-OF-BOTH-BROAD-BUS-CE [7]

eventType Equipment



Alarm Description The BSC has detected loss of both broadcast buses to a CE.




Loss – – – – –



[53,7] LOSS−OF−BOTH−−BROAD−BUS−CE

Alarmsolved

yes

Alarm persists?

no


On−site



3BK 21618 AAAA PCZZA Ed.16 283 / 778


19.9 [53,8] DEGRAD-BROAD-BUS-CE

specificProblems BROADCAST BUS [53] DEGRAD-BROAD-BUS-CE [8]

eventType Equipment



Alarm Description The BSC has detected a degradation in the quality of one of thebroadcast buses to a CE.


Impact on System Some broadcasted messages may be lost for this CE, for example,some paging messages can be lost . For the consequences of an SBLstate change, see Consequences of an SBL State Change.


Loss – – – – –



[53,8] DEGRAD−BROAD−BUS−CE

Alarmsolved

yesAlarm

persists?

no

DEGRAD−BROAD−BUS−RACK alarm

events?

no

yes


On−site

G2: Replace suspected

broadcast bus RIT

284 / 778 3BK 21618 AAAA PCZZA Ed.16

20 Class 54: BTS-POOL Alarms


This section defines the BSC alarms for the Class 54: BTS-POOL alarm class.

3BK 21618 AAAA PCZZA Ed.16 285 / 778


20.1 [54,1] EXTRA TS NOT FULLY USABLE

specificProblems BTS-POOL [54] EXTRA TS NOT FULLY USABLE [1]



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

Alarm Description For 9120 BSC: In case of TCU failure/end failure, 2nd Abis failure/endfailure or BTS config-complete, the alarm is evaluated.For 9130 BSC Evolution: In case of 2nd Abis failure/end failure thealarm is evaluated.This alarm is on BTS level, linked to a new SBL BTS-POOL per BTS.The new added SBL, BTS-POOL, is always IT and not involved inSBL-state-audit, Furthermore, no operation on the SBL is allowed.


9130 BSC

Impact on System The new added SBL does not impact MAINT/ALARM modules. InOMC side, after HW audit, if the BTS is type of 9100 , OMC createsBTS-POOL for that BTS. And OMC will clear the alarm in case of alarmaudit or receiving END alarm.


Loss No No No No No

Degradation No Yes No No No

286 / 778 3BK 21618 AAAA PCZZA Ed.16



3BK 21618 AAAA PCZZA Ed.16 287 / 778


288 / 778 3BK 21618 AAAA PCZZA Ed.16

21 Class 66: TSC-TRUNK Alarms


This section defines the BSC alarms for the Class 66: TSC-TRUNK alarm class.

3BK 21618 AAAA PCZZA Ed.16 289 / 778


21.1 [66,21] LOOP-TO-ITF

specificProblems TSC-TRUNK [66] LOOP-TO-ITF [21]

eventType Equipment

probableCause EquipmentUnderTest


Alarm Description An external loop is activated. A loop cannot be activated/deactivatedusing the OMC-R.


G2 TC and 9125 TC



Loss Yes (ifA-PCM-TPor SBLATER-HWAY-TP)

Yes (ifABIS-HWAY-TP)

Yes Yes Yes



[66,21] LOOP−TO−ITF

Remove the loopback settings, though normal conditions return

after a preset control timeout.

Alarmsolved

yes

Alarm persists?

no


290 / 778 3BK 21618 AAAA PCZZA Ed.16


21.2 [66,22] LOOP-TO-EQUIP

specificProblems TSC-TRUNK [66] LOOP-TO-EQUIP [22]

eventType Equipment



Alarm Description An external loop is activated. A loop cannot be activated/deactivatedusing the OMC-R.


G2 TC and 9125 TC





Yes Yes Yes (ifABIS-HWAY-TP)



[66,22] LOOP−TO−EQUIP

Remove the loopback settings, though normal conditions return

after a preset control timeout.

Alarmsolved

yes

Alarm persists?

no


3BK 21618 AAAA PCZZA Ed.16 291 / 778


21.3 [66,50] TWO-MB-MISSING

specificProblems TSC-TRUNK [66] TWO-MB-MISSING [50]




Alarm Description Loss of an incoming 2M signal. The loss of the incoming digital signalat 2048 kbit/s is considered as loss of an incoming 2M signal.


G2 TC and 9125 TC







292 / 778 3BK 21618 AAAA PCZZA Ed.16



[66,50] TWO−MB−MISSING

Solve thatalarm(s) first

Solve that alarm(s)


ABIS/APCM/ATER alarm

events?

no

yes

Repair/replace Receiver

2M link−related

alarm events?

no

yes

On−site

Alarmsolved

Alarm persists?

noyes

Alarm persists?

no

yes

Receiver operational?

no yes

Solve that alarm(s)Related

receiver alarm events?

no

yes

Local trunk cabling

OK?

no

yes

Trigger remote signal path and transmitter tests on MSC side

3BK 21618 AAAA PCZZA Ed.16 293 / 778


21.4 [66,66] AIS-2-MB

specificProblems TSC-TRUNK [66] AIS-2-MB [66]


probableCause LocalNodeTransmissionError


Alarm Description The 2 Mbit/s interface is receiving an AIS signal all ones indication.


G2 TC and 9125 TC







294 / 778 3BK 21618 AAAA PCZZA Ed.16



[66,66] AIS−2−MB

Remove loop

Solve that alarm(s)

Contact

System Support

ABIS/

APCM/ATER alarm

events?

no

yes

Loop

activated?

no

yes

Alarm

solved

Alarm

persists?

no

yes

Alarm

solved

Alarm

persists?

no

yes

Trigger remote signal

path and transmitter

tests on MSC side

3BK 21618 AAAA PCZZA Ed.16 295 / 778


21.5 [66,81] FRAME-ALIGNMENT

specificProblems TSC-TRUNK [66] FRAME-ALIGNMENT [81]




Alarm Description The 2 Mbit/s signal frame alignment is lost. Traffic is not possible. TS 0is reserved for frame alignment, alarms and network synchronizationinformation and should not be used for Signaling or speech purposes.The frame alignment signal is monitored to determine if the framealignment has been lost. The frame alignment will be assumed to havebeen lost when three consecutive incorrect frame alignment signalshave been received.


G2 TC and 9125 TC







296 / 778 3BK 21618 AAAA PCZZA Ed.16



[66,81] FRAME−ALIGNMENT

Correct timeslot 0 settings

Solve that alarm(s)



events?

no

yes

Timeslot 0 settings

OK?

no

yes

Alarm persists?

no

Alarmsolved

Alarm persists?

no

yes


yes

3BK 21618 AAAA PCZZA Ed.16 297 / 778


21.6 [66,86] CRC-MFRAME-ALGN

specificProblems TSC-TRUNK [66] CRC-MFRAME-ALGN [86]




Alarm Description Expected patterns not received on TS0 of the PCM (CRC multiframe).The CRC is not used in the remote end or there may be interferenceson the connection.


G2 TC and 9125 TC







298 / 778 3BK 21618 AAAA PCZZA Ed.16



[66,86] CRC−MFRAME−ALIGNMENT

Correct timeslot 0 CRC settings


Timeslot 0 CRC settings

OK?

no

yes

Alarm persists?

no

yes

Alarmsolved

Alarm persists?

no

yes

Trigger tests of remote CRC activation on MSC side

3BK 21618 AAAA PCZZA Ed.16 299 / 778


21.7 [66,99] BER-10E-3

specificProblems TSC-TRUNK [66] BER-10E-3 [99]




Alarm Description Signal input BER worse than 1 in 1000. The error rate of the incomingmain system signal is worse than the preset threshold value of 10E-3.


G2 TC and 9125 TC







300 / 778 3BK 21618 AAAA PCZZA Ed.16



[66,99] BER−10E−3


Solve that alarm(s)



events?

no

yes


Link−relatedalarm events?

no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes

Solve that alarm(s)

Related receiver alarm

events?

no

yes

Local trunk cabling

OK?

no

yes


3BK 21618 AAAA PCZZA Ed.16 301 / 778


21.8 [66,100] BER-10E-4





Alarm Description Signal input BER worse than 1 in a 10000. The error rate of theincoming main system signal is worse than the preset threshold valueof 10E-4.


G2 TC and 9125 TC



Loss No No No No No


302 / 778 3BK 21618 AAAA PCZZA Ed.16



[66,100] BER−10E−4


Solve that alarm(s)



events?

no

yes



no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Localtrunk cabling

OK?

no

yes


3BK 21618 AAAA PCZZA Ed.16 303 / 778


21.9 [66,102] BER-10E-6





Alarm Description Signal input BER worse than 1 in a million. The error rate of theincoming main system signal is worse than the preset threshold valueof 10E-6.


G2 TC and 9125 TC



Loss No No No No No


304 / 778 3BK 21618 AAAA PCZZA Ed.16



[66,102] BER−10E−6


Solve that alarm(s)



events?

no

yes



no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Local trunk cabling

OK?

no

yes


3BK 21618 AAAA PCZZA Ed.16 305 / 778


21.10 [66,176] FAR-END-ALARM

specificProblems TSC-TRUNK [66] FAR-END-ALARM [176]




Alarm Description The equipment at the remote end has acknowledged the faultycondition of the interface signal. Alarm indication from the remote endis detected when bit 3 of channel TS 0 changes state from 0 to 1 inthose frames not containing the frame alignment signal.


G2 TC and 9125 TC







306 / 778 3BK 21618 AAAA PCZZA Ed.16



[66,176] FAR−END−

ALARM

Solve that alarm(s)

Contact

System Support

ABIS/

APCM/ATER alarm

events?

no

yes

Alarm

solved

Alarm

persists?

no

yes

Solve that alarm(s)

Related

receiver alarm

events?

no

yes

Trigger remote signal

path and transmitter

tests on MSC side

3BK 21618 AAAA PCZZA Ed.16 307 / 778


21.11 [66,208] I1I2-AIS

specificProblems TSC-TRUNK [66] I1I2-AIS [208]




Alarm Description An AIS was received on the time slot carrying tributary informationon the Ater Mux Interface. The AIS condition is detected on the TSwhich carries the tributary information on the Ater Mux interface.If transparent AIS is not detected on TS 0, then the alarm octet ischecked to see if an I1I2_AIS alarm has occurred as redundant AIS.


G2 TC and 9125 TC



Loss Yes No Yes Yes No


308 / 778 3BK 21618 AAAA PCZZA Ed.16



[66,208] I1L2−AIS

Remove loop


Ateralarm events?

no

yes

Alarmsolved

Alarm persists?

no

yes

Solve that alarm(s)

Loop is activated?

no

yes


3BK 21618 AAAA PCZZA Ed.16 309 / 778


21.12 [66,210] TRANS-FLT

specificProblems TSC-TRUNK [66] TRANS-FLT [210]

eventType Equipment



Alarm Description The PCM event counter threshold value is exceeded, which results inthe generation of this 2 Mbit/s interface alarm. For each PCM event, acounter is increased. At certain intervals, the counter will be decreasedby 1. When the threshold value is exceeded, this alarm is generatedfor the 2 Mbit/s interface.


G2 TC and 9125 TC



Loss No No No No No


310 / 778 3BK 21618 AAAA PCZZA Ed.16



[66,210] TRANS−FLT


Solve that alarm(s)



events?

no

yes



no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Local trunk cabling

OK?

no

yes


3BK 21618 AAAA PCZZA Ed.16 311 / 778


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

specificProblems TSC-TRUNK [66] LOSS-OF-CLK-2M [211]

eventType Equipment



Alarm Description The 2 MHz clock source is lost. Once the PAD detects the loss of the 2MHz clock source, the next clock source will be selected if available.The firmware will detect the missing clock source number.


G2 TC and 9125 TC





312 / 778 3BK 21618 AAAA PCZZA Ed.16



[66,211] LOSS−OF−CLOCK−2M


Solve that alarm(s)



events?

no

yes



no

yes

On−site Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Local trunk cabling

OK?

no

yes


3BK 21618 AAAA PCZZA Ed.16 313 / 778


21.14 [66,225] TU-LOP

specificProblems TSC-TRUNK [66] TU-LOP [225]




Alarm Description tributary unit 12 loss of pointer, E1 evel alarm in case of STM1 in TC,Only reported over TCSL

Applicability G2 TC and 9125 TC

Impact on System Ater-HW-TP(TC) or A-PCM-TP is updated to FLT


Loss Yes (ifA-PCM-TP)

No Yes if it carriesN7

Yes No



314 / 778 3BK 21618 AAAA PCZZA Ed.16


21.15 [66,226] TU-AIS

specificProblems TSC-TRUNK [66] TU-AIS [226]




Alarm Description Tributary Unit 12 Alarm Indication Signal






Yes No


3BK 21618 AAAA PCZZA Ed.16 315 / 778


21.16 [66,227] LP-UNEQ

specificProblems TSC-TRUNK [66] LP-UNEQ [227]




Alarm Description Low Path Unequipped






Yes No


316 / 778 3BK 21618 AAAA PCZZA Ed.16


21.17 [66,228] LP-RDI

specificProblems TSC-TRUNK [66] LP-RDI [228]




Alarm Description Low Path Remote Defect indication






Yes No


3BK 21618 AAAA PCZZA Ed.16 317 / 778


21.18 [66,229] LP-PLM

specificProblems TSC-TRUNK [66] LP-PLM [229]




Alarm Description Low Path Payload Label Mismatch






Yes No


318 / 778 3BK 21618 AAAA PCZZA Ed.16


21.19 [66,230] LP-J2

specificProblems TSC-TRUNK [66] LP-J2 [230]




Alarm Description J2 path trace mismatch






Yes No


3BK 21618 AAAA PCZZA Ed.16 319 / 778


21.20 [66,231] E1-AIS-2MB

specificProblems TSC-TRUNK [66] E1-AIS-2MB [231]




Alarm Description Alarm Indication Signal






Yes No


320 / 778 3BK 21618 AAAA PCZZA Ed.16


21.21 [66,232] E1-FRAME-ALIGNMENT

specificProblems TSC-TRUNK [66] E1-FRAME-ALIGNMENT [232]




Alarm Description Loss of Frame alignment






Yes No


3BK 21618 AAAA PCZZA Ed.16 321 / 778


21.22 [66,233] E1-CRC-MFRAME-ALGN

specificProblems TSC-TRUNK [66] E1-CRC-MFRAME-ALGN [233]




Alarm Description Loss of CRC4 multiframe alignment






Yes No


322 / 778 3BK 21618 AAAA PCZZA Ed.16


21.23 [66,234] E1-BER-10E-3

specificProblems TSC-TRUNK [66] E1-BER-10E-3 [234]




Alarm Description Bit error rate >10E-3






Yes No


3BK 21618 AAAA PCZZA Ed.16 323 / 778


21.24 [66,235] E1-BER-10E-4

specificProblems TSC-TRUNK [66] E1-BER-10E-4 [235]




Alarm Description Bit error rate >10E-4


Impact on System Ater-HW-TP(TC) or A-PCM-TP is updated to FIT




Yes No


324 / 778 3BK 21618 AAAA PCZZA Ed.16


21.25 [66,236] E1-RAI

specificProblems TSC-TRUNK [66] E1-RAI [236]




Alarm Description Remote Alarm Indication






Yes No


3BK 21618 AAAA PCZZA Ed.16 325 / 778


326 / 778 3BK 21618 AAAA PCZZA Ed.16

22 Class 67: TSC-CHANNEL Alarms


This section defines the BSC alarms for the Class 67: TSC-CHANNEL alarmclass.

3BK 21618 AAAA PCZZA Ed.16 327 / 778



specificProblems TSC-CHANNEL [67] LOOP-TO-EQUIP [22]

eventType Equipment



Alarm Description A loop has been activated. A loop cannot be activated/deactivatedusing the OMC-R.







[67,22] LOOP−

TO−EQUIP

Remove loop

Contact

System Support

Alarm

solved

Alarm

persists?

no

yes

328 / 778 3BK 21618 AAAA PCZZA Ed.16


22.2 [67,72] AIS-16-KB

specificProblems TSC-CHANNEL [67] AIS-16-KB [72]




Alarm Description The Ater-Interface TCHs are receiving an AIS signal (all ones).

Note: This alarm is not sent to the OMC, only to the BSC Terminal.






3BK 21618 AAAA PCZZA Ed.16 329 / 778



[67,72] AIS−16−KB

Solve that alarm(s)


TC−16alarm events?

no

yes


On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Local Ater cabling

OK?

no

yes


330 / 778 3BK 21618 AAAA PCZZA Ed.16


22.3 [67,122] TRAU-SYNCHRO

specificProblems TSC-CHANNEL [67] TRAU-SYNCHRO [122]

eventType Equipment



Alarm Description The TRAU cannot synchronize to the BTS. The speech path is brokenbetween the TRE and the Transcoder. This only occurs during callhandling.

Note: This alarm is not sent to the OMC, only to the BSC Terminal.






3BK 21618 AAAA PCZZA Ed.16 331 / 778



[67,122] TRAU−SYNCHRO

Solve that alarm(s)


BTS/BSC−Adapt alarm events?

no

yes

Alarmsolved

Alarm persists?

no

yes

Solve that alarm(s)Abis alarm

events?

no

yes

Solve that alarm(s)

TCU/SWITCH/DTC

alarm events?

noyes

332 / 778 3BK 21618 AAAA PCZZA Ed.16


22.4 [67,128] EQUIPMENT-FAULT

specificProblems TSC-CHANNEL [67] EQUIPMENT-FAULT [128]

eventType Equipment



Alarm Description An internal fault has been detected on a board.






3BK 21618 AAAA PCZZA Ed.16 333 / 778



[67,128] EQUIPMENT−FAULT

Alarmsolved

Alarm persists?

no

yes

On−site

Replace DT16/TC−16

Lock TC−16

Alarmsolved

yes

Alarm persists?

no

Unlock TC−16


Alarm persists?

no

yes

On−site

Replace MT120

Lock MT120

yes

Alarm persists?

no

Unlock MT120

G2 TC A925 TC

Replace MT120

or

334 / 778 3BK 21618 AAAA PCZZA Ed.16


22.5 [67,130] MEMORY-FAULT

specificProblems TSC-CHANNEL [67] MEMORY-FAULT [130]




Alarm Description An EEPROM memory write access has been unsuccessful.






3BK 21618 AAAA PCZZA Ed.16 335 / 778



[67,130] MEMORY−FAULT

Analyze alarm number


Alarmsolved

Alarm persists?

no

yes

Solve that alarm(s)DT16/TC−16

alarm events?

no

yes

On−site


Lock TC−16

Alarmsolved

yes

Alarm persists?

no

Unlock TC−16

Replace MT120

Alarm persists?

G2 TC or 9125 TC?


MT120 alarm events?

Lock MT 120

Unlock MT120

Alarm persists?

Replace MT120

Alarm persists?


no

no

no

yes

yesyes

yes

yes

no

9125 TCG2 TC

or

336 / 778 3BK 21618 AAAA PCZZA Ed.16


22.6 [67,131] INT-BUS-FAULT

specificProblems TSC-CHANNEL [67] INT-BUS-FAULT [131]

eventType Equipment



Alarm Description An internal fault has been detected on board.






3BK 21618 AAAA PCZZA Ed.16 337 / 778



[67,131] INT−BUS−FAULT

Alarmsolved

Alarm persists?

no

yes

On−site


Lock TC−16

Alarmsolved

yes

Alarm persists?

no

Unlock TC−16


Alarm persists?

no

yes

On−site

Replace MT120

Lock MT120

yes

Alarm persists?

no

Unlock MT120

G2 TC A925 TC

Replace MT120

or

338 / 778 3BK 21618 AAAA PCZZA Ed.16

23 Class 70: TSC-SW-ANOMALY Alarms


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

3BK 21618 AAAA PCZZA Ed.16 339 / 778


23.1 [70,219] SW-FAULT

specificProblems TSC-SW-ANOMALY [70] SW-FAULT [219]


probableCause ApplicationSubsystemFailure


Alarm Description The software which runs on the TSCA board (9120 BSC) or the TSCprocess (A(130 BSC) has detected an error.


9130 BSC



Loss No No No No No


340 / 778 3BK 21618 AAAA PCZZA Ed.16



[70,219] SW−FAULT


Alarmsolved

Alarm persists?

no

yes

On−site

Replace TSC

Lock TSC

yes

Alarm persists?

no

Unlock TSC

PressTSC reset button

Disengage & replugg TSC

On−site

On−site

3BK 21618 AAAA PCZZA Ed.16 341 / 778


342 / 778 3BK 21618 AAAA PCZZA Ed.16

24 Class 71: TSC-ENVIRON Alarms


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

3BK 21618 AAAA PCZZA Ed.16 343 / 778


24.1 [71,0] POWER-SUPPLY

specificProblems TSC-ENVIRON [71] POWER-SUPPLY [0]

eventType Equipment



Alarm Description An operating voltage is missing or out of range. All or some of thefunctions on the reporting board are not working.


9130 BSC

G2 TC and 9125 TC

Impact on System If the power supply fails and the CPU on any board is not working,the power supply alarm may not be sent. See Consequences of anSBL State Change.


Loss Yes (ifSM-ADAPT= FLT orTC-ADAPT= FLT)

Yes (ifBTS-ADAPT= FLT)

Yes (ifBTS-ADAPT= FLT,SM-ADAPT= FLT orTC-ADAPT =FLT)

Yes (ifBTS-ADAPT= FLT,SM-ADAPT= FLT orTC-ADAPT =FLT)

Yes (if BTS-ADAPT =FLT)

Degradation Yes (ifSM-ADAPT= FIT)

Yes (ifBTS-ADAPT= FIT)

Yes (ifBTS-ADAPT= FIT orSM-ADAPT= FIT)

Yes (ifBTS-ADAPT= FIT orSM-ADAPT= FIT)

Yes (if BTS-ADAPT =FIT)

344 / 778 3BK 21618 AAAA PCZZA Ed.16



[71,0] POWER−SUPPLY



Alarmsolved

Alarm persists?

no

yes

Solve that alarm(s)Other

alarm on RIT events?

no

yes

On−site

Alarmsolved

yes

Alarm persists?

no

Solve that alarm(s)DC/DC

converter alarm events?

no

yes

On−site

Replace suspected TSS RIT

On−site

Check supply cabling, connectors, fuses

Input voltage on

suspected RITOK

no

yes

3BK 21618 AAAA PCZZA Ed.16 345 / 778


346 / 778 3BK 21618 AAAA PCZZA Ed.16

25 Class 73: BSC-ADAPT Alarms


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

3BK 21618 AAAA PCZZA Ed.16 347 / 778



specificProblems BSC-ADAPT [73] LOOP-TO-EQUIP [22]

eventType Equipment



Alarm Description A loop is activated on one of the eight BSC interfaces. A loop cannotbe activated/deactivated using the OMC-R.




Loss No Yes Yes Yes No




Remove loopback setting


Alarmsolved

Alarm persists?

no

yes

When a loop is activated, it deactivates after a preset control timeout.

348 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems BSC-ADAPT [73] EQUIPMENT-FAULT [128]

eventType Equipment



Alarm Description There is a basic operational malfunction. An internal fault has beendetected on board.




Loss No Yes Yes Yes Yes


3BK 21618 AAAA PCZZA Ed.16 349 / 778





Alarmsolved

Alarm persists?

no

yes

Solve that alarm(s)BIUA

alarm events?

no

yes

On−site

Replace BIUA

Lock BSC−ADAPT

Alarmsolved

yes

Alarm persists?

no

Unlock BSC−ADAPT

350 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems BSC-ADAPT [73] MEMORY-FAULT [130]

eventType Equipment









3BK 21618 AAAA PCZZA Ed.16 351 / 778






Alarmsolved

Alarm persists?

no

yes

Solve that alarm(s)BIU

alarm events?

no

yes

On−site

Replace BIU

Lock BSC−ADAPT

Alarmsolved

yes

Alarm persists?

no

Unlock BSC−ADAPT

352 / 778 3BK 21618 AAAA PCZZA Ed.16


25.4 [73,148] RESET

specificProblems BSC-ADAPT [73] RESET [148]




Alarm Description An autonomous load occurred. The module has undergone seriousservice interruption, but has recovered. The reset_buffer is checked tosee if the board leaves the reset mode. After startup, hardware testson memory and interfaces are performed, and the process jumps tothe software entry point.







None - this alarm reports the autonomous load.

See TC Alarms (Section 36.5) for the Alarm number description.

3BK 21618 AAAA PCZZA Ed.16 353 / 778


25.5 [73,202] NO-Q1-CONN

specificProblems BSC-ADAPT [73] NO-Q1-CONN [202]




Alarm Description There is a connection problem on the Qmux bus, no response isreceived from the network element. The TSC is unable to find any orcertain network elements connected to the primary or secondary bus.






354 / 778 3BK 21618 AAAA PCZZA Ed.16



[73,202] NO−Q1−CONN


Alarmsolved

Alarm persists?

no

yes

Solve that alarm(s)Alarm on

suspected RIT events?

no

yes

On−site

Check/Replace Qmux equipment

yes

Alarm persists?

no

Solve that alarm(s) Transmissionalarm events?

no

yes

Correct Address

Qmux address in DLS

OK?

no

yes

3BK 21618 AAAA PCZZA Ed.16 355 / 778


25.6 [73,203] LOSS-OF-ACT

specificProblems BSC-ADAPT [73] LOSS-OF-ACT [203]

eventType Equipment



Alarm Description Loss of Activity due to link failure. Each incoming BS interface link canbe scanned in order to detect a malfunction (disconnection of a cable).Only one link can be scanned at a time. The firmware gives a resetto this alarm bit. A certain time later, the firmware reads the alarmbit in order to detect a link failure.




Loss No No No No No


356 / 778 3BK 21618 AAAA PCZZA Ed.16



[73,203] LOSS−

OF−ACT

Contact

System Support

yes

Solve that alarm(s)

BIUA

alarm

events?

no

yes

Lock

BIUA

Alarm

solved

Alarm

persists?

no

Unlock

BIUA

Solve that alarm(s)

Transmission

alarm

events?

no

yes

3BK 21618 AAAA PCZZA Ed.16 357 / 778


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

specificProblems BSC-ADAPT [73] LOSS-OF-CLK-8M [212]

eventType Equipment



Alarm Description The BSC-BIE is provided with two external 8 MHz clock references.This alarm is generated when the loss of one of the default clocks isdetected by a PAD.




Loss No No No No No


358 / 778 3BK 21618 AAAA PCZZA Ed.16





Alarmsolved

Alarm persists?

no

yes

Solve that alarm(s)Clock alarm events?

no

yes

On−site

Replace BCLA

Alarmsolved

yes

Alarm persists?

no

Solve that alarm(s)BCLAalarm

events?

no

yes

3BK 21618 AAAA PCZZA Ed.16 359 / 778


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

specificProblems BSC-ADAPT [73] LOSS-OF-CLK-BOTH-8M [213]

eventType Equipment



Alarm Description Both 8 MHz clock sources are lost. The internal clock is selected.






360 / 778 3BK 21618 AAAA PCZZA Ed.16



[73,213] LOSS−OF−CLOCK−BOTH−8M


Alarmsolved

Alarm persists?

no

yes

Solve that alarm(s)Clock alarm events?

no

yes

On−site

Replace BCLA

Alarmsolved

yes

Alarm persists?

no


events?

no

yes

3BK 21618 AAAA PCZZA Ed.16 361 / 778


25.9 [73,216] RESTART

specificProblems BSC-ADAPT [73] RESTART [216]




Alarm Description An autonomous restart has occurred. The operating system and allprocesses are re-initialized sequentially. All non-volatile protected datais cleared and a new initialization of the dynamic data has taken place.




Loss No No No No No



None - this alarm reports an autonomous restart.

362 / 778 3BK 21618 AAAA PCZZA Ed.16


25.10 [73,241] SET-PROD-FAIL

specificProblems BSC-ADAPT [73] SET-PROD-FAIL [241]




Alarm Description This alarm indicates the NE settings production has failed. Theequipment settings are not in line with the DLS.







[73,241] SET−PROD−FAIL


yes

Lock BSC−ADAPT

Alarmsolved

Alarm persists?

no

Unlock BSC−ADAPT

Correct DSL settingsDSL

settings OK?

no

yes

3BK 21618 AAAA PCZZA Ed.16 363 / 778



specificProblems BSC-ADAPT [73] DOWNLOAD-FAIL [246]




Alarm Description This alarm indicates the programming of the BSC-ADAPT has failed.Modification of BSC-Adapt parameters has occurred in the BSC, anddownloading of the BSC-Adapt has been initiated but has failed.


Impact on System The equipment settings are not in line with the DLS. See Consequencesof an SBL State Change.




364 / 778 3BK 21618 AAAA PCZZA Ed.16



[73,246] DOWNLOAD−

FAIL

Contact

System Support

yes

Lock

BSC−ADAPT

Alarm

solved

Alarm

persists?

no

Unlock

BSC−ADAPT


settings OK?

no

yes

3BK 21618 AAAA PCZZA Ed.16 365 / 778


25.12 [73,247] ACCESS-FAIL

specificProblems BSC-ADAPT [73] ACCESS-FAIL [247]

eventType Equipment



Alarm Description This alarm indicates the programming of the BSC-ADAPT has failed.Modification of BSC-Adapt parameters has occurred in the BSC andaccess attempts towards the BSC-ADAPT has failed. The equipmentsettings are not in line with the DLS and will be replaced.







[73,247] ACCESS−

FAIL

Contact

System Support

yes

Alarm

solved

Alarm

persists?

no

Solve that alarm(s)TCU/TSL/NE

alarm events?

no

yes

366 / 778 3BK 21618 AAAA PCZZA Ed.16

26 Class 74: BTS-ADAPT Alarms


This section defines the BSC alarms for the Class 74: BTS-ADAPT alarm class.

3BK 21618 AAAA PCZZA Ed.16 367 / 778


26.1 [74,20] BLOCKED-FROM-USE

specificProblems BTS-ADAPT [74] BLOCKED-FROM-USE [20]




Alarm Description Unit is not in use due to a configuration error. If the same time slotsare allocated for two boards, then the allocations on one board areblocked from use.


9130 BSC





368 / 778 3BK 21618 AAAA PCZZA Ed.16



[74,20] BLOCKED−FROM−USE


Alarmsolved

Alarm persists?

no

yes

Correct time slotsettings

Time slot settings OK?

no

yes

On−site

Disengage andreplug SMBS board

yes

Alarm persists and SMBS was

powered off/on?

no


events?

no

yes

3BK 21618 AAAA PCZZA Ed.16 369 / 778



specificProblems BTS-ADAPT [74] LOOP-TO-EQUIP [22]

eventType Equipment



Alarm Description A loop is activated on the BSC interface link.

A loop cannot be activated/deactivated using the OMC-R.


9130 BSC



Loss No No No No No




Remove BSC interface loop


Alarmsolved

Alarm persists?

no

yes

When a loop is activated, it deactivates after apreset control timeout.

370 / 778 3BK 21618 AAAA PCZZA Ed.16


26.3 [74,23] TESTMODE

specificProblems BTS-ADAPT [74] TESTMODE [23]

eventType Equipment



Alarm Description The equipment, or part of it, is under test. Normal operation issuspended.


9130 BSC






None - equipment is under test.


3BK 21618 AAAA PCZZA Ed.16 371 / 778


26.4 [74,122] SYNCHRO-AL

specificProblems BTS-ADAPT [74] SYNCHRO-AL [122]

eventType Equipment



Alarm Description The primary synchronization source is missing or not selected. Themodule switches to the secondary source.


9130 BSC



Loss No No No No No


372 / 778 3BK 21618 AAAA PCZZA Ed.16



[74,122] SYNCHRO−AL

Contact

System Support

Alarm

solved

Alarm

persists?

no

yes

Solve that alarm(s)Clock alarm

events?

no

yes

On−site

Check/Replace

clock cabling

Alarm

solved

yes

Alarm

persists?

no

Solve that alarm(s)

PCM

alarm

events?

no

yes

3BK 21618 AAAA PCZZA Ed.16 373 / 778


26.5 [74,124] SYNC-AL-CLOCKR

specificProblems BTS-ADAPT [74] SYNC-AL-CLOCKR [124]

eventType Equipment



Alarm Description Synchronizing fault in clock recovery has occurred. The synchronizingsignal is missing.


9130 BSC





374 / 778 3BK 21618 AAAA PCZZA Ed.16



[74,124] SYNC−AL−

CLOCKR

Contact

System Support

Alarm

solved

Alarm

persists?

no

yes

Solve that alarm(s)Clock alarm

events?

no

yes

On−site

Check/Replace

clock cabling

Alarm

solved

yes

Alarm

persists?

no

Solve that alarm(s)

PCM

alarm

events?

no

yes

Correct clock settings

Clock

configuration

settings OK?

no

yes

3BK 21618 AAAA PCZZA Ed.16 375 / 778



specificProblems BTS-ADAPT [74] EQUIPMENT-FAULT [128]

eventType Equipment



Alarm Description There is a basic operational malfunction. An internal fault has beendetected on a board.


9130 BSC



Loss No Yes (ifBTS-ADAPT= FLT)




Degradation No Yes (ifBTS-ADAPT= FIT)




376 / 778 3BK 21618 AAAA PCZZA Ed.16



[74,128] EQUIPMENT−

FAULT

Contact

System Support

Alarm

solved

Alarm

persists?

no

yes

On−site

Replace

suspected RIT

Lock

BTS−ADAPT

Alarm

solved

yes

Alarm

persists?

no

Unlock

BTS−ADAPT

3BK 21618 AAAA PCZZA Ed.16 377 / 778



specificProblems BTS-ADAPT [74] MEMORY-FAULT [130]






9130 BSC











378 / 778 3BK 21618 AAAA PCZZA Ed.16






Alarmsolved

Alarm persists?

no

yes


alarm events?

no

yes

On−site

Replace BIU

Lock BTS−ADAPT

Alarmsolved

yes

Alarm persists?

no

Unlock BTS−ADAPT

3BK 21618 AAAA PCZZA Ed.16 379 / 778


26.8 [74,139] MISSING-UNIT

specificProblems BTS-ADAPT [74] MISSING-UNIT [139]




Alarm Description A defined slave unit is missing from the configuration. The board isnot connected, no response is received from the slave board. Theaccessed unit is not installed into the configuration although it isdefined as being equipped. (Transmission equipment is organized intomaster modules - those polled by the TSC via the Q1 bus - and slavemodules that are monitored by the master modules).


9130 BSC











380 / 778 3BK 21618 AAAA PCZZA Ed.16



[74,139] MISSING−UNIT


Alarmsolved

Alarm persists?

no

yes

Solve that alarm(s)BTS RIT alarm events?

no

yes

On−site

Replug/Replace suspected RIT

Lock BTS−ADAPT

yes

Alarm persists?

no

Unlock BTS−ADAPT

3BK 21618 AAAA PCZZA Ed.16 381 / 778


26.9 [74,141] FORCED-CNTRL-ON

specificProblems BTS-ADAPT [74] FORCED-CNTRL-ON [141]

eventType Equipment



Alarm Description A forced control (loop, changeover, etc.) is activated.


9130 BSC






[74,141] FORCED−

CONTROL−ON

Contact

System Support

Alarm

solved

Alarm

persists?

no

yes

Remove

forced controlThe normal condition

returns after a preset timeout.

382 / 778 3BK 21618 AAAA PCZZA Ed.16


26.10 [74,142] INSTALLATION

specificProblems BTS-ADAPT [74] INSTALLATION [142]




Alarm Description Installation incorrectly performed. This alarm can also appears as anevent when the board is manipulated.


9130 BSC





3BK 21618 AAAA PCZZA Ed.16 383 / 778



[74,142] INSTALLATION


Alarmsolved

Alarm persists?

no

yes


no

yes

On−site


Lock BTS−ADAPT

yes

Alarm persists?

no

Unlock BTS−ADAPT

384 / 778 3BK 21618 AAAA PCZZA Ed.16


26.11 [74,148] RESET

specificProblems BTS-ADAPT [74] RESET [148]




Alarm Description An autonomous load of the CE occurred. The module has undergoneserious service interruption, but has recovered. The reset/restart bufferis checked to see if the board leaves the reset mode. After startup,hardware tests on memory and interfaces are performed, and theprocess jumps to the software entry point.


9130 BSC






None, - this alarm reports the autonomous load of the CE only.


3BK 21618 AAAA PCZZA Ed.16 385 / 778


26.12 [74,159] DIAG-TESTS

specificProblems BTS-ADAPT [74] DIAG-TESTS [159]

eventType Equipment



Alarm Description A diagnostic test is running.


9130 BSC






None - the operator has activated the TEST function to obtain more detailedinformation.


386 / 778 3BK 21618 AAAA PCZZA Ed.16


26.13 [74,202] NO-Q1-CONN

specificProblems BTS-ADAPT [74] NO-Q1-CONN [202]




Alarm Description A connection problem occurred on the Qmux bus, no responsereceived from the network element. The TSC is unable to find any orcertain network elements connected to the primary or secondary bus.


9130 BSC



Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 387 / 778



[74,202] NO−Q1−CONN


Alarmsolved

Alarm persists?

no

yes

Solve that alarm(s) Alarm on BTS RIT events?

no

yes

On−site


Alarmsolved

yes

Alarm persists?

no

Solve that alarm(s) Transmission

alarm events?

no

yes

Correct AddressQmux

address in DLS OK?

no

yes

388 / 778 3BK 21618 AAAA PCZZA Ed.16


26.14 [74,241] SET-PROD-FAIL

specificProblems BTS-ADAPT [74] SET-PROD-FAIL [241]






9130 BSC





3BK 21618 AAAA PCZZA Ed.16 389 / 778





yes

Lock BSC−ADAPT

Alarmsolved

Alarm persists?

no

Unlock BSC−ADAPT


settings OK?

no

yes

390 / 778 3BK 21618 AAAA PCZZA Ed.16


26.15 [74,245] LOCAL-REINIT-REQ

specificProblems BTS-ADAPT [74] LOCAL-REINIT-REQ [245]

eventType Equipment



Alarm Description This alarm indicates programming is required locally. Modification ofBTS-Adapt parameters has occurred in the BSC, but the setting atthe BTS_Adapt must be carried out locally and cannot be carried outremotely. The equipment settings are not in line with the DLS.


9130 BSC





3BK 21618 AAAA PCZZA Ed.16 391 / 778



[74,245] LOCAL−

REINIT−REQ

Contact

System Support

Alarm

solved

Alarm

persists?

no

yes

Correct settings

BTS

parameter settings

OK?

no

yes

Disable BSC−ADAPT

Init BSC−ADAPT

392 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems BTS-ADAPT [74] DOWNLOAD-FAIL [246]




Alarm Description This alarm indicates that programming of the BTS-ADAPT has failed.Modification of BTS-Adapt parameters has occurred in the BSC, anddownloading of the BTS_Adapt has been initiated but has failed. Theequipment settings are not in line with the DLS.


9130 BSC





3BK 21618 AAAA PCZZA Ed.16 393 / 778



[74,246] DOWNLOAD−

FAIL

Contact

System Support

Alarm

solved

Alarm

persists?

no

yes

Correct settings

DLS

settings

OK?

no

yes

Lock BSC−ADAPT

Unlock BSC−ADAPT

394 / 778 3BK 21618 AAAA PCZZA Ed.16


26.17 [74,247] ACCESS-FAIL

specificProblems BTS-ADAPT [74] ACCESS-FAIL [247]

eventType Equipment



Alarm Description This alarm indicates that programming of the BTS-ADAPT has failed.Modification of BTS-Adapt parameters has occurred in the BSC, butaccess towards the BTS-Adapt has failed. The equipment settings arenot in line with the DLS.


9130 BSC







Contact

System Support

Alarm

solved

Alarm

persists?

no

yes

Solve that alarm(s)

TCU/TSL/NE

alarm

events?

no

yes

3BK 21618 AAAA PCZZA Ed.16 395 / 778


396 / 778 3BK 21618 AAAA PCZZA Ed.16

27 Class 75: TCSM-ADAPT Alarms


This section defines the BSC alarms for the Class 75: TCSM-ADAPT alarmclass.

3BK 21618 AAAA PCZZA Ed.16 397 / 778


27.1 [75,20] BLOCKED-FROM-USE

specificProblems TCSM-ADAPT [75] BLOCKED-FROM-USE [20]




Alarm Description Unit is not in use due to a configuration error. If the same time slotsare allocated for two boards, then the allocations on one board areblocked from use.







[75,20] BLOCKED−

FROM−USE

Contact

System Support

Alarm

solved

Alarm

persists?

no

yes

Correct time

slot settings

Time slot

settings OK?

no

yes

398 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems TCSM-ADAPT [75] LOOP-TO-EQUIP [22]

eventType Equipment



Alarm Description A loop is activated. A loop cannot be activated/deactivated using theOMC-R.




Loss Yes (ifSM-ADAPT= FLT)

No Yes (ifSM-ADAPT= FLT)

Yes (ifSM-ADAPT= FLT)

No

Degradation Yes (ifSM-ADAPT= FIT)

No Yes (ifSM-ADAPT= FIT)

Yes (ifSM-ADAPT= FIT)

No




Alarmsolved

Alarm persists?

no

yes

Remove BSC interface loop

3BK 21618 AAAA PCZZA Ed.16 399 / 778


27.3 [75,112] FAN-ALARM

specificProblems TCSM-ADAPT [75] FAN-ALARM [112]

eventType Environmental

probableCause HeatingOrVentilationOrCoolingSystemProblem


Alarm Description The Fan rotation speed has been detected to be lower than theminimum threshold value for that speed or a temperature higher thannormal operating value has been detected in the rack.




Loss No No No No No



[75,112] FAN−ALARM


Alarmsolved

Alarm persists?

no

yes

Replace fan unit

On−site

400 / 778 3BK 21618 AAAA PCZZA Ed.16


27.4 [75,122] SYNCHRO-AL

specificProblems TCSM-ADAPT [75] SYNCHRO-AL [122]

eventType Equipment



Alarm Description The primary synchronization source is missing. The module switchesto the secondary source.




Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 401 / 778



[75,122] SYNCHRO−AL

Contact

System Support

Alarm

solved

Alarm

persists?

no

yes

Solve that alarm(s)

Clock

alarm

events?

no

yes

On−site

Check/Replace

Clock equipment

Alarm

solved

yes

Alarm

persists?

no

Solve that alarm(s)

PCM

alarm

events?

no

yes

402 / 778 3BK 21618 AAAA PCZZA Ed.16


27.5 [75,124] SYNCHRO-AL-CLOCKR

specificProblems TCSM-ADAPT [75] SYNCHRO-AL-CLOCKR [124]

eventType Equipment



Alarm Description Synchronizing fault in clock recovery has occurred. The synchronizingsignal is missing.




Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 403 / 778



[75,124] SYNCHRO−

AL−CLOCKR

Contact

System Support

Alarm

solved

Alarm

persists?

no

yes

Solve that alarm(s)

Clock

alarm

events?

no

yes

On−site

Check/Replace

Clock equipment

Alarm

solved

yes

Alarm

persists?

no

Solve that alarm(s)

PCM

alarm

events?

no

yes

Correct clock

configuration settings

Clock

configuration

settings

OK?

no

yes

404 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems TCSM-ADAPT [75] EQUIPMENT-FAULT [128]

eventType Equipment







Loss Yes (ifSM-ADAPT= FLT)

No Yes (ifSM-ADAPT= FLT)

Yes (ifSM-ADAPT= FLT)

No

Degradation Yes (ifSM-ADAPT= FIT orTC_ADAPT= FLT)

No Yes (ifSM-ADAPT= FIT orTC_ADAPT= FLT)

Yes (ifSM-ADAPT= FIT orTC_ADAPT= FLT)

No

3BK 21618 AAAA PCZZA Ed.16 405 / 778





Alarmsolved

Alarm persists?

no

yes

Lock SM−ADAPT/TC_ADAP

T

On−site


Alarmsolved

yes

Alarm persists?

no

Unlock SM−ADAPT/TC_ADAP

T

406 / 778 3BK 21618 AAAA PCZZA Ed.16


27.7 [75,130] DSP-LOSS

specificProblems TCSM-ADAPT [75] DSP-LOSS [130]




Alarm Description For G2 TC: an EEPROM memory write access has been unsuccessful.For MT120: more than one DSP has failed and the impact is only theloss of a number of channels, that is only trunk degradation. Signallingis not lost neither.




Loss Yes(for G2TC)

No Yes(for G2 TC) Yes(for G2 TC) No

Degradation Yes(forMT120)

No No No No

3BK 21618 AAAA PCZZA Ed.16 407 / 778



[75,130] DSP−LOSS



Alarmsolved

Alarm persists?

no

yes


alarm events?

no

yes

On−site

Replace BIU

Lock SM−ADAPT/TC−ADAPT

Alarmsolved

yes

Alarm persists?

no

Unlock SM−ADAPT/TC−ADAPT

Reset MT120

Replace MT120

Alarm persists?

Alarm persists?


no

no

yesOn−site

G2 TC 9125 TC

Replace MT120

or

408 / 778 3BK 21618 AAAA PCZZA Ed.16


27.8 [75,136] FIRST-DSP-FAIL

specificProblems TCSM-ADAPT [75] FIRST-DSP-FAIL [136]

eventType Equipment



Alarm Description One out of the twelve DSPs of a MT120 has failed. All channels ofthis DSP are fully recovered and are now handled by the other elevenDSPs. If no further DSPs have failed (e.g. MEMORY-FAULT) thenthis MT120 is still able to handle all resources (up to 120 channels),but it works in a degraded mode, as it cannot recover any additionalDSP failure.




Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 409 / 778



[75,136] FIRST−DSP−FAIL


Alarmsolved

Alarm persists?

no

yes

On−site

Replace MT120

Alarmsolved

yes

Alarm persists?

no

Reset MT120

Replace MT120

G2 TC or 9125 TC?G2 TC 9125 TC

410 / 778 3BK 21618 AAAA PCZZA Ed.16


27.9 [75,139] MISSING-UNIT

specificProblems TCSM-ADAPT [75] MISSING-UNIT [139]




Alarm Description A defined slave unit is missing from the configuration. The slave boardis not connected, there is no response received from the slave board.The accessed unit is not installed into the configuration although it isdefined to be equipped. (Transmission equipment is organized intomaster modules - those polled by the TSC via the Q1 bus - and slavemodules that are monitored by the master modules).




Loss Yes (ifSM-ADAPT= FIT orTC-ADAPT= FLT)

No Yes (ifSM-ADAPT= FIT orTC-ADAPT =FLT)

Yes (ifSM-ADAPT= FIT orTC-ADAPT =FLT)

No


3BK 21618 AAAA PCZZA Ed.16 411 / 778



[75,139] MISSING−UNIT


Alarmsolved

Alarm persists?

no

yes


no

yes

On−site



yes

Alarm persists?

no


412 / 778 3BK 21618 AAAA PCZZA Ed.16


27.10 [75,141] FORCED-CNTRL-ON

specificProblems TCSM-ADAPT [75] FORCED-CNTRL-ON [141]

eventType Equipment



Alarm Description Forced control (loop, changeover etc.) is activated.




Loss Yes (ifSM_ADAPT= FLT)

No No Yes (ifSM_ADAPT= FLT)

No

Degradation Yes (ifSM_ADAPT= FIT orTC_ADAPT= FLT)

No No Yes (ifSM_ADAPT= FIT orTC_ADAPT= FLT)

No


[75,141] FORCED−CONTROL−ON


Alarmsolved

Alarm persists?

no yes

Remove forced control

The normal condition returns after a preset timeout.

3BK 21618 AAAA PCZZA Ed.16 413 / 778


27.11 [75,142] INSTALLATION

specificProblems TCSM-ADAPT [75] INSTALLATION [142]




Alarm Description Installation incorrectly performed, or appears as an event when theboard is manipulated.




Loss Yes (if SBLSM-ADAPT)

No Yes (if SBLSM-ADAPT)

Yes (if SBLSM-ADAPT)

No

Degradation Yes (if SBLTC-ADAPT)

No Yes (if SBLTC-ADAPT)

Yes (if SBLTC-ADAPT)

No

414 / 778 3BK 21618 AAAA PCZZA Ed.16



[75,142] INSTALLATION


Alarmsolved

Alarm persists?

no

yes

Solve that alarm(s)

Alarm on suspected

RIT events?

no

yes

On−site



yes

Alarm persists?

no


3BK 21618 AAAA PCZZA Ed.16 415 / 778


27.12 [75,148] RESET

specificProblems TCSM-ADAPT [75] RESET [148]




Alarm Description An autonomous load of the TC SM-ADAPT occurred. The modulehas undergone serious service interruption, but has recovered.Thereset_buffer is checked to see if the board leaves the reset mode. Afterstartup, hardware tests on memory and interfaces are performed, andthe process jumps to the software entry point. This cannot happenas this module has only firmware.


Impact on System Some calls may be lost


Loss No No No No No



None - this alarm reports the autonomous load of the BTS_ADAPT only.


416 / 778 3BK 21618 AAAA PCZZA Ed.16


27.13 [75,159] DIAG-TESTS

specificProblems TCSM-ADAPT [75] DIAG-TESTS [159]

eventType Equipment



Alarm Description A diagnostic test is running.







None - the operator has activated the TEST function to obtain more detailedinformation.


3BK 21618 AAAA PCZZA Ed.16 417 / 778


27.14 [75,202] NO-Q1-CONN

specificProblems TCSM-ADAPT [75] NO-Q1-CONN [202]




Alarm Description No response received from the network element. The TSC is unableto find any or certain network elements connected to the primary orsecondary bus.






418 / 778 3BK 21618 AAAA PCZZA Ed.16



[75,202] NO−Q1−CONN


Alarmsolved

Alarm persists?

no yes

Solve that alarm(s) alarm on

suspected RIT events?

no

yes

On−site


yes

Alarm persists?

no

Solve that alarm(s) Transmissionalarm events?

no

yes

Correct Address

Qmux address in DLS

OK?

yes

no

3BK 21618 AAAA PCZZA Ed.16 419 / 778


27.15 [75,208] TRIB-TRANS-FLT

specificProblems TCSM-ADAPT [75] TRIB-TRANS-FLT [208]




Alarm Description The PCM event counter threshold value is exceeded on one tributaryinterface, which results in the generation of this 2 Mbit/s alarm. Foreach PCM event, a counter is increased. At certain intervals, thecounter will be decreased by 1. When the threshold value is exceeded,this alarm is generated for that 2 Mbit/s interface.




Loss No No No No No


420 / 778 3BK 21618 AAAA PCZZA Ed.16



[75,208] TRIB−TRANS−FLT


Solve that alarm(s)


PCMalarm events?

no

yes

Repair/replace Tributary interface

Link−related alarm events?

no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes

Tributary interface

operational?

no yes


tributary alarm events?

no

yes

Local tributary cabling

OK?

no

yes


3BK 21618 AAAA PCZZA Ed.16 421 / 778


27.16 [75,209] INT-BUS-FLT-G25

specificProblems TCSM-ADAPT [75] INT-BUS-FLT-G25 [209]

eventType Equipment



Alarm Description An internal bus fault has occurred on one or both TCIL links (internalO&M bus between MT120) inside the A9125 TC rack. The TCIL linksare duplicated HDLC multi-master busses. These TCIL links conveyinternal messages as well as external Qmux messages (coming fromthe TSC). In case of the bus not working, Qmux polling of boards notdirectly receiving the primary or secondary links, cannot be done.The O&M data flow is broken, the rack cannot be supervised, but thetelecom data path still works.






422 / 778 3BK 21618 AAAA PCZZA Ed.16



[75,209] INT−BUS−FLT−G25

Board ataddress 75?


MT120 highest

address?

MT120lowest

address?

Board at address16?

Put a spareat address 16

Put a spareat address 75

Replace MT120

Last boardwith

alarm?

Alarmsolved

Alarm persists?

Alarm persists?

yes

yes

yes

yes

no

no

no

no

no

Alarmsolved

no

yes no

G2 TC or 9125 TC?

Replace MT120

G2 TC 9125 TC

G2 TC or 9125 TC?

Replace MT120

Replace MT120

G2 TC 9125 TC

3BK 21618 AAAA PCZZA Ed.16 423 / 778


27.17 [75,210] ATER-TRANS-FLT

specificProblems TCSM-ADAPT [75] ATER-TRANS-FLT [210]




Alarm Description The PCM event counter threshold value is exceeded on one ATERinterface, which results in the generation of this 2 Mbit/s alarm. Foreach PCM event, a counter is increased. At certain intervals, thecounter will be decreased by 1. When the threshold value is exceeded,this alarm is generated for that 2 Mbit/s interface.




Loss No No No No No


424 / 778 3BK 21618 AAAA PCZZA Ed.16



[75,210] ATER−TRANS−FLT


Solve that alarm(s)


PCM/ATER alarm events?

no

yes

Repair/replace Ater interface

Other Ater alarm

events?

no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes

Ater interface

operational?

no yes

Solve that alarm(s)Ater

interface alarm events?

no

yes

Local Ater cabling

OK?

no

yes


3BK 21618 AAAA PCZZA Ed.16 425 / 778


27.18 [75,211] LOSS-OF-CLK-2M

specificProblems TCSM-ADAPT [75] LOSS-OF-CLK-2M [211]

eventType Equipment



Alarm Description The 2 MHz clock source is lost. Once the PAD detects the loss of the2MHz clock source, the next clock source will be selected if available.The firmware will detect the missing clock source number.






426 / 778 3BK 21618 AAAA PCZZA Ed.16





Solve that alarm(s)


APCM alarm events?

no

yes


Link related alarm

events?

no

yes


noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Local trunk cabling

OK?

no

yes


3BK 21618 AAAA PCZZA Ed.16 427 / 778


27.19 [75,216] RESTART

specificProblems TCSM-ADAPT [75] RESTART [216]




Alarm Description n autonomous processor restart has occurred. The operating systemand all processes are re-initialized sequentially. A new initializationof the dynamic data takes place.




Loss No No No No No



None - this alarm reports an autonomous restart.


428 / 778 3BK 21618 AAAA PCZZA Ed.16


27.20 [75,221] TRIB-TWO-MB-MISSING

specificProblems TCSM-ADAPT [75] TRIB-TWO-MB-MISSING [221]




Alarm Description The 2 Mbit/s on one tributary interface is not receiving a signal. Theloss of the incoming digital signal at 2048 kbit/s is considered as aloss of the incoming 2M signal.






3BK 21618 AAAA PCZZA Ed.16 429 / 778



[75,221] TRIB−TWO−MB−MISSING


Solve that alarm(s)


SM−ADAPTalarm events?

no

yes


Link related alarm

events?

no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Local cabling

OK?

no

yes


430 / 778 3BK 21618 AAAA PCZZA Ed.16


27.21 [75,222] TRIB-AIS-2MB

specificProblems TCSM-ADAPT [75] TRIB-AIS-2MB [222]


probableCause Ais


Alarm Description The 2 Mbit/s on one tributary interface is receiving an AIS signal (allones).






3BK 21618 AAAA PCZZA Ed.16 431 / 778



[75,222] TRIB−AIS−2MB

Remove loop

Correct transmission settings


Transmission signal settings

OK?

no

yes

Loop activated?

no

yes

Alarmsolved

Alarm persists?

no yes

Solve that alarm(s)Remote

transmitter alarm(s) events?

no

yes

Trigger remote transmitter test

432 / 778 3BK 21618 AAAA PCZZA Ed.16


27.22 [75,223] TRIB-FRAME-ALIGNMENT

specificProblems TCSM-ADAPT [75] TRIB-FRAME-ALIGNMENT [223]




Alarm Description The 2 Mbit/s signal frame alignment on one tributary interface is lost.Traffic is not possible. TS0 is reserved for frame alignment, alarmsand network synchronization information and should not be usedfor Signaling or speech purposes. The frame alignment signal ismonitored to determine if the frame alignment has been lost. The framealignment will be assumed to have been lost when three consecutiveincorrect frame alignment signals have been received.






3BK 21618 AAAA PCZZA Ed.16 433 / 778



[75,223] TRIB−FRAME−ALIGNMENT

Remove loop

Correct transmission settings


Transmission signal settings

OK?

no

yes

Loop activated?

no

yes

Alarmsolved

Alarm persists?

no yes


transmitter alarm(s) events?

no

yes

Trigger remote transmitter test

434 / 778 3BK 21618 AAAA PCZZA Ed.16


27.23 [75,224] TRIB-CRC-MFRAME-ALGN

specificProblems TCSM-ADAPT [75] TRIB-CRC-MFRAME-ALGN [224]




Alarm Description The expected patterns not received on TS0 of the PCM (CRCmultiframe) on one tributary interface. The CRC is not used in theremote end or there may be interferences on the connection.







[75,224] TRIB−CRC−MFRAME−ALGN

Correct CRC settings


Time slot 0 CRCl settings

OK?

no

yes

Alarmsolved

Alarm persists?

no yes


CRC alarm(s) events?

no

yes

Trigger remote signal path tests

3BK 21618 AAAA PCZZA Ed.16 435 / 778


27.24 [75,225] TRIB-BER-10E-3

specificProblems TCSM-ADAPT [75] TRIB-BER-10E-3 [225]




Alarm Description The signal input BER is worse than 1 in 1000 on one tributary interface.The error rate of the incoming main system signal is worse than thepreset threshold value of 10E-3.






436 / 778 3BK 21618 AAAA PCZZA Ed.16



[75,225] TRIB−BER−10E−3


Solve that alarm(s)



no

yes


Link related alarm

events?

no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Local cabling

OK?

no

yes


3BK 21618 AAAA PCZZA Ed.16 437 / 778


27.25 [75,226] TRIB-BER-10E-4





Alarm Description Signal input BER worse than 1 in a 10000 on one tributary interface.The error rate of the incoming main system signal is worse than thepreset threshold value of 10E-4.




Loss No No No No No


438 / 778 3BK 21618 AAAA PCZZA Ed.16



[75,226] TRIB−BER−10E−4


Solve that alarm(s)



no

yes


Link related alarm

events?

no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Local cabling

OK?

no

yes


3BK 21618 AAAA PCZZA Ed.16 439 / 778


27.26 [75,227] TRIB-BER-10E-6





Alarm Description Signal input BER worse than 1 in a million on one tributary interface.The error rate of the incoming main system signal is worse than thepreset threshold value of 10E-6.




Loss No No No No No


440 / 778 3BK 21618 AAAA PCZZA Ed.16



[75,227] TRIB−BER−10E−6


Solve that alarm(s)



no

yes


Link related alarm

events?

no

yes


noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Local cabling

OK?

no

yes


3BK 21618 AAAA PCZZA Ed.16 441 / 778


27.27 [75,228] TRIB-FAR-END-ALARM

specificProblems TCSM-ADAPT [75] TRIB-FAR-END-ALARM [228]




Alarm Description The equipment at the remote end has acknowledged the faultycondition of the interface signal, on one tributary interface. Alarmindication from the remote end is detected when bit 3 of channel TS0changes state from 0 to 1 in those frames not containing the framealignment signal.




Loss Yes No No Yes No


442 / 778 3BK 21618 AAAA PCZZA Ed.16



[75,228] TRIB−FAR−END−ALARM


Solve that alarm(s)



no

yes


Link related alarm

events?

no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Local cabling

OK?

no

yes


3BK 21618 AAAA PCZZA Ed.16 443 / 778


27.28 [75,231] ATER-TWO-MB-MISSING

specificProblems TCSM-ADAPT [75] ATER-TWO-MB-MISSING [231]




Alarm Description The 2 Mbit/s interface on one Ater interface is not receiving a signal.The loss of the incoming digital signal at 2048 kbit/s is considered as aloss of the incoming 2M signal.






444 / 778 3BK 21618 AAAA PCZZA Ed.16



[75,231] ATER−TWO−MB−MISSING


Solve that alarm(s)


TC−ADAPTalarm events?

no

yes


Ater related alarm

events?

no

yes

On−siteAlarm

persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Local Ater cabling

OK?

no

yes

Trigger remote signal path and transmitter

tests on BSC side

3BK 21618 AAAA PCZZA Ed.16 445 / 778


27.29 [75,232] ATER-AIS-2MB

specificProblems TCSM-ADAPT [75] ATER-AIS-2MB [232]


probableCause Ais


Alarm Description The 2 Mbit/s interface on one Ater interface is receiving an AIS signal(all ones).






446 / 778 3BK 21618 AAAA PCZZA Ed.16



[75,232] ATER−AIS−2MB


Solve that alarm(s)



no

yes


Ater related alarm

events?

no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes

Remove activated loops

Loops activated?

no

yes

Local Ater cabling

OK?

no

yes


tests on BSC side

3BK 21618 AAAA PCZZA Ed.16 447 / 778


27.30 [75,233] ATER-FRAME-ALIGNMENT

specificProblems TCSM-ADAPT [75] ATER-FRAME-ALIGNMENT [233]




Alarm Description The 2 Mbit/s signal frame alignment on one Ater interface is lost.Traffic is not possible. TS0 is reserved for frame alignment, alarmsand network synchronization information and should not be usedfor Signaling or speech purposes. The frame alignment signal ismonitored to determine if the frame alignment has been lost. The framealignment will be assumed to have been lost when three consecutiveincorrect frame alignment signals have been received.




Loss No No No No No


448 / 778 3BK 21618 AAAA PCZZA Ed.16



[75,233] ATER−FRAME−ALIGNMENT


Solve that alarm(s)



no

yes


Ater related alarm

events?

no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes

Correct the settingsTime slot 0 settings OK?

yes

no

Local Ater cabling

OK?

no

yes


tests on BSC side

3BK 21618 AAAA PCZZA Ed.16 449 / 778


27.31 [75,234] ATER-CRC-MFRAME-ALGN

specificProblems TCSM-ADAPT [75] ATER-CRC-MFRAME-ALGN [234]




Alarm Description The expected patterns not received on TS0 of the PCM (CRCmultiframe) on one Ater interface. The CRC is not used in the remoteend or there maybe interferences on the connection.




Loss No No No No No



[75,234] ATER−CRC−MFRAME−ALGN

Correct CRC settings


Time Slot 0 CRC settings

OK?

no

yes

Alarmsolved

Alarm persists?


CRC alarm(s) events?

no

yes

yesno

450 / 778 3BK 21618 AAAA PCZZA Ed.16


27.32 [75,235] ATER-BER-10E-3

specificProblems TCSM-ADAPT [75] ATER-BER-10E-3 [235]




Alarm Description Signal input BER worse than 1 in 1000 on one Ater interface. Theerror rate of the incoming main system signal is worse than the presetthreshold value of 10E-3.






3BK 21618 AAAA PCZZA Ed.16 451 / 778



[75,235] ATER−BER−10E−3


Solve that alarm(s)



no

yes


Relatedalarm events?

no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Local cabling

OK?

no

yes


452 / 778 3BK 21618 AAAA PCZZA Ed.16


27.33 [75,236] ATER-BER-10E-4





Alarm Description Signal input BER worse than 1 in a 10000 on one Ater interface. Theerror rate of the incoming main system signal is worse than the presetthreshold value of 10E-4.




Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 453 / 778



[75,236] ATER−BER−10E−4


Solve that alarm(s)



no

yes



no

yes

On−siteAlarm

persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Local cabling

OK?

no

yes


454 / 778 3BK 21618 AAAA PCZZA Ed.16


27.34 [75,237] ATER-BER-10E-6





Alarm Description Signal input BER worse than 1 in a million on one Ater interface. Theerror rate of the incoming main system signal is worse than the presetthreshold value of 10E-6.




Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 455 / 778



[75,237] ATER−BER−10E−6


Solve that alarm(s)



no

yes



no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes


no yes



no

yes

Local cabling

OK?

no

yes


456 / 778 3BK 21618 AAAA PCZZA Ed.16


27.35 [75,238] ATER-FAR-END-ALARM

specificProblems TCSM-ADAPT [75] ATER-FAR-END-ALARM [238]




Alarm Description The equipment at the remote end has acknowledged the faultycondition of the interface signal, on one Ater interface. Alarm indicationfrom the remote end is detected when bit 3 of channel TS0 changesstate from 0 to 1 in those frames not containing the frame alignmentsignal.




Loss Yes No No Yes No


3BK 21618 AAAA PCZZA Ed.16 457 / 778



[75,238] ATER−FAR−END−ALARM



no

yes

Alarm persists?

no

Alarmsolved

Alarm persists?

no yes



no

yes


tests on BSC side

yes

458 / 778 3BK 21618 AAAA PCZZA Ed.16


27.36 [75,241] SET-PROD-FAIL

specificProblems TCSM-ADAPT [75] SET-PROD-FAIL [241]








Loss Yes (ifSM-ADAPT)

No Yes (ifSM-ADAPT)

Yes (ifSM-ADAPT)

No

Degradation Yes (ifTC-ADAPT)

No Yes (ifTC-ADAPT)

Yes (ifTC-ADAPT)

No




yes

Lock SM/TC−ADAPT

Alarmsolved

Alarm persists?

no

Unlock SM/TC−ADAPT


settings OK?

no

yes

3BK 21618 AAAA PCZZA Ed.16 459 / 778


27.37 [75,245] LOCAL-REINIT-REQ

specificProblems TCSM-ADAPT [75] LOCAL-REINIT-REQ [245]

eventType Equipment



Alarm Description This alarm indicates that programming is required locally. Modificationof SM-ADAPT/TC-ADAPT parameters has occurred in the BSC, butthe setting at the SM-ADAPT/TC-ADAPT must be carried out locallyand cannot be carried out remotely. The equipment settings are notin line with the DLS.


Impact on System SM-ADAPT: All calls managed by the processor are lost with or withoutWTC as specified by the operator. TC-ADAPT: All calls managedby the processor are lost with or without WTC as specified by theoperator. See Consequences of an SBL State Change.



No Yes (ifSM-ADAPT)

Yes (ifSM-ADAPT)

No


No Yes (ifTC-ADAPT)

Yes (ifTC-ADAPT)

No

460 / 778 3BK 21618 AAAA PCZZA Ed.16



[75,245] LOCAL−REINIT−REQ


Alarmsolved

Alarm persists?

no yes

Correct settingsBTS

parameter settingsOK?

no

yes

Disable SM/TC−ADAPT

Init SM/TC−ADAPT

3BK 21618 AAAA PCZZA Ed.16 461 / 778



specificProblems TCSM-ADAPT [75] DOWNLOAD-FAIL [246]

eventType Equipment



Alarm Description This alarm indicates that programming of the SM-ADAPT/TC-ADAPThas failed. Modification of SM-ADAPT/TC-ADAPT parameters hasoccurred in the BSC, and downloading of the SM_ADAPT/TC-ADAPThas been initiated but has failed. The equipment settings are not inline with the DLS.


Impact on System SM-ADAPT:All calls managed by the processor are lost with or withoutWTC as specified by the operator. TC-ADAPT: All calls managedby the processor are lost with or without WTC as specified by theoperator. See Consequences of an SBL State Change.



No Yes (ifSM-ADAPT)

Yes (ifSM-ADAPT)

No


No Yes (ifTC-ADAPT)

Yes (ifTC-ADAPT)

No

462 / 778 3BK 21618 AAAA PCZZA Ed.16



[75,246] DOWNLOAD−FAIL


yes

Lock SM/TC−ADAPT

Alarmsolved

Alarm persists?

no

Unlock SM/TC−ADAPT


settings OK?

no

yes

3BK 21618 AAAA PCZZA Ed.16 463 / 778


27.39 [75,247] ACCESS-FAIL

specificProblems TCSM-ADAPT [75] ACCESS-FAIL [247]

eventType Equipment



Alarm Description This alarm indicates that programming of the SM-ADAPT/TC-ADAPThas failed. Modification of SM/TC-ADAPTt parameters has occurred inthe BSC, and access towards the SM-ADAPT/TC-ADAPT has failed.The equipment settings are not in line with the DLS.


Impact on System SM-ADAPT: All calls managed by the processor are lost with or withoutWTC as specified by the operator. TC-ADAPT: All calls managedby the processor are lost with or without WTC as specified by theoperator. See Consequences of an SBL State Change.



No Yes (ifSM-ADAPT)

Yes (ifSM-ADAPT)

No


No Yes (ifTC-ADAPT)

Yes (ifTC-ADAPT)

No




Alarmsolved

Alarm persists?

no yes

Solve that alarm(s)TCU/TSL/NE alarm events?

no

yes

464 / 778 3BK 21618 AAAA PCZZA Ed.16

28 Class 96: PROCESS Alarms


This section defines the BSC alarms for the Class 96: PROCESS alarm class.

3BK 21618 AAAA PCZZA Ed.16 465 / 778


28.1 [96,0] RESET

specificProblems PROCESS [96] RESET [0]




Alarm Description The VCE has been successfully reset. The service managed by thisVCE is lost.



In case CPR or DTC TCH-RM (running on OMCP board):All stable calls are not affected. Due to TCH-RM takeover somesignaling messages can be lost which can affect some transactions inprogress (call setup or handovers). Some CMISE exchanges or filetransfers with OMC-R may be interrupted. If this happens, the OMC-Rrequests the information again.

In case TCU:All calls carried by TRX managed by the TCU are lost. New callscan be established after the reset. If the TCU carries OML, O&Moperations with BTS are stopped.

In case of DTC (except TCH-RM DTC running on OMCP board):All calls carried by the Atrunk managed by the DTC process are lost.For DTC carrying SCCP, all SCCP connections managed by the DTCprocess are lost. New calls can be established by using other Atrunksand other SCCP DTC.

In case of TSC:All transmission downloading managed by the process are lost.


Loss No No No No No



None - The VCE has been successfully reset.

466 / 778 3BK 21618 AAAA PCZZA Ed.16


28.2 [96,1] RESTART

specificProblems PROCESS [96] RESTART [1]




Alarm Description The VCE has successfully restarted. No service (call) was lost.



In case CPR:There is no telecom impact. Some CMISE exchanges or file transferswith OMC-R may be interrupted. If this happens, the OMC-R requeststhe information again.

In case TCU or DTC (including TCH-RM DTC mapped on OMCPboard):All stable calls are not affected. Some signaling messages can belost which can affect some transactions in progress (call setup orhandovers).

In case of TSC:All transmission downloading managed by the process are lost.


Loss No No No Possible (ifTCU or DTC)

No

Degradation No No No No Yes (if CPR)


None - The VCE has been successfully restarted.

3BK 21618 AAAA PCZZA Ed.16 467 / 778


28.3 [96,2] MULTIPLE-RESET

specificProblems PROCESS [96] MULTIPLE-RESET [2]




Alarm Description The VCE has reset more than 3 times in 1 hour, and is no longerrecreated.


Impact on System The impacted SBL state is set to FLT.

In case CPR or DTC TCH-RM (mapped on OMCP board):All stable calls are not affected. Due to TCH-RM takeover somesignaling messages can be lost which can affect some transactions inprogress (call setup or handovers). Some CMISE exchanges or filetransfers with OMC-R may be interrupted. If this happens, the OMC-Rrequests the information again.

In case TCU:All calls carried by TRX managed by the TCU are lost. If the TCUcarries OML, O&M operations with BTS are stopped. In case of DTC(except TCH-RM DTC mapped on OMCP board). All calls carried bythe Atrunk managed by the DTC process are lost. For DTC carryingSCCP, all SCCP connections managed by the DTC process are lost.New calls can be established by using other Atrunks and other SCCPDTC.

In case of TSC:All transmission configuration and transmission supervision managedby the process are lost.


Loss Yes (ifDTC exceptTCH-RMDTC mappedon OMCP)

Yes (if TCUand all TRXare carriedby this TCU)

Yes (if TCU orif DTC carriesN7 or GSL)

Yes (if CPR,TCU or DTC)

Yes (if TCU carriesOML)

Degradation - Yes (if TCUand someTRX arecarried byother TCU)

No No Yes (ifCPR or DTCTCH-RM (mapped onOMCP board)

468 / 778 3BK 21618 AAAA PCZZA Ed.16




Solve other board related alarms

Board carrying the process is ok?

Alarm persists?

yes

yes

Alarm persists?

Alarm persists?

no

no

Alarmsolved

no

no

yes

Solve other boards related alarms

yes

[96, 2] MULTIPLE RESET

Reset the process

Reset the board carrying the process

Status of other boards is ok?

no

3BK 21618 AAAA PCZZA Ed.16 469 / 778


28.4 [96,3] ACCESS-FAIL

specificProblems PROCESS [96] ACCESS-FAIL [3]

eventType Equipment



Alarm Description The VCE cannot be created.



For detailled impacts, See Process, Multiple Reset [96,2]


Loss No No No No No


470 / 778 3BK 21618 AAAA PCZZA Ed.16



[96, 3] ACCESS FAIL

Alarmsolved

yes

Alarm persists?

no


Reset the board hosting the VCE

Reset the target VCE

Alarm persists?

yes

no

3BK 21618 AAAA PCZZA Ed.16 471 / 778


472 / 778 3BK 21618 AAAA PCZZA Ed.16

29 Class 97: ATCA-PROCESSOR Alarms


This section defines the BSC alarms for the Class 97: ATCA-PROCESSORalarm class.

3BK 21618 AAAA PCZZA Ed.16 473 / 778


29.1 [97,0] RESET

specificProblems ATCA-PROCESSOR [97] RESET [0]




Alarm Description Board reset was successfully. If the board was active a switchoverwas performed.


Impact on System The impacted SBL state is not changed.There is no system impact if the board is the standby OMCP, CCP orTP.If the board is the active OMCP, CCP or TP, the BSC triggers a takeover(see ATCA-PROCESSOR [97], TAKEOVER [1]).


Loss - - - - -

Degradation - - - - -


None - The board has been successfully reset.

474 / 778 3BK 21618 AAAA PCZZA Ed.16


29.2 [97,1] TAKEOVER

specificProblems ATCA-PROCESSOR [97] TAKEOVER [1]




Alarm Description A board takeover was performed due to a failure on the active board.



In case of OMCP (CP-HW #1 or CP-HW #2):- All stable calls are not affected.- Due to TCH-RM takeover some signaling messages can be lost whichcan affect some transactions in progress (call setup or handovers).- Some file transfers with OMC-R may be interrupted. If this happens,the OMC-R requests the information again.- All transmission downloading managed by the TSC are lost .

In case CCP (other CP-HW):- All calls carried by TRX managed by TCU of this CCP and all callscarried by the Atrunk managed by DTC of this CCP and all SCCPconnections managed by DTC of this CCP are lost. New calls can beestablished after the takeover occurs.

In case of TP-HW:total N7 down (normally for 2-3 seconds), no new calls while N7sare down,External Hos (inter-BSC), SMS and other services may beimpacted.


Loss No No Yes (if TP) Yes (if CCP) No

Degradation Yes (if CCP) Yes (if CCP) Yes (if CCP) Yes (if OMCP) Yes (if OMCP or CCP)


None - A board takeover was successfully performed.

3BK 21618 AAAA PCZZA Ed.16 475 / 778


29.3 [97,2] RLC-OV

specificProblems ATCA-PROCESSOR [97] RLC-OV [2]

eventType Equipment



Alarm Description The board has reset more than three times in one hour and waspowered-off.


Impact on System The impacted SBL state is changed to FLT. System impacts are due toprevious reset event.

System impacts are due to previous reset event (seeATCA-PROCESSOR [97], TAKEOVER [1]).


Loss - - - - -



[97, 2] RLC OV

Alarmsolved

yes

Alarm persists?

no


On−site

Replace board

Solve boards related alarms

Other Event alarms for the board

are present?

Alarm persists?

no

yes

yes

476 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems ATCA-PROCESSOR [97] ACCESS-FAIL [3]

eventType Equipment



Alarm Description The board cannot start because of problems in the INIT sequence. Itpowered off.List of possible causes:- Timeout on Board Ready- Timeout on NE1oE contact message (TP-GSM)- Timeout of MXPF service request for this board.- Initial configuration request rejected by TP-GSM (checks of configfiles failed).This alarm may happen when handles are opened


Impact on System The impacted SBL state is changed to FLT.

There is no system impact if the board is the standby OMCP, CCP orTP.If the board is the active OMCP, CCP or TP, the BSC triggers a takeover(see ATCA-PROCESSOR [97], TAKEOVER [1]).


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 477 / 778



[97, 3] ACCESS FAIL

Alarmsolved

yes

Alarm persists?

no


On−siteReplace suspected RIT

Solve other alarmsOther ATCA

shelf related alarms are present?

Alarm persists?

Reset board

noyes

yes

478 / 778 3BK 21618 AAAA PCZZA Ed.16


29.5 [97,4] APPLICATION-FATAL-TERMINATION

specificProblems ATCA-PROCESSOR [97] APPLICATION-FATAL-TERMINATION [4]




Alarm Description The board was reset due to BSC fatal process termination.



The problem could happen only on active OMCP and when it happensthe BSC triggers a takeover.


Loss - - - - -



None.

3BK 21618 AAAA PCZZA Ed.16 479 / 778


29.6 [97,5] SYSTEM-FATAL-TERMINATION

specificProblems ATCA-PROCESSOR [97] SYSTEM-FATAL-TERMINATION [5]




Alarm Description The board was reset due to platform fatal process termination.



There is no system impact if the board is the standby OMCP or CCP.If the board is the active OMCP or CCP, the BSC triggers a takeover(see ATCA-PROCESSOR [97], TAKEOVER [1]).


Loss - - - - -



None.

480 / 778 3BK 21618 AAAA PCZZA Ed.16


29.7 [97,6] UNPLUGGED

specificProblems ATCA-PROCESSOR [97] UNPLUGGED [6]

eventType Equipment

probableCause Unavailable


Alarm Description The board was removed from the ATCA shelf. Alarm will be clearedst bord re-insertion.





Loss - - - - -



[97, 6] UNPLUGGED

Re−insert the boardBoard is correctly

inserted?Alarmsolved

yes

Alarm persists?

no


yes

no

3BK 21618 AAAA PCZZA Ed.16 481 / 778


29.8 [97,7] FW-UPGRADE-UNSUCCESS

specificProblems ATCA-PROCESSOR [97] FW-UPGRADE-UNSUCCESS [7]

eventType Equipment



Alarm Description The alarm is reported when firmware upgrade is triggered successfully,but it fails to upgrade


Impact on System If alarm "FIRMWARE_NOT_UTD" is reported before, there is noimpact to related SBL.If alarm "FIRMWARE_INCOMP" is reported before, the related SBLwill change to FLT.


Loss No No No No No



[97, 7] FW−UPGRADE−UNSUCCESS

Alarmsolved

yes

Alarm persists?

no


Trigger firmware upgrade again

482 / 778 3BK 21618 AAAA PCZZA Ed.16


29.9 [97,8] FW-UPGRADE

specificProblems ATCA-PROCESSOR [97] FW-UPGRADE [8]



perceivedSeverity minor(DMA)

Alarm Description Operator has launched firmware upgrade in the board on the field. Alloperations on this board(lock,reset) are rejected while this alarm isactive.


Impact on System The impacted SBL is set to FLT.


Loss – – – – –

Degradation – – – – –


None - the operator has launched firmware upgrade in the board.

3BK 21618 AAAA PCZZA Ed.16 483 / 778


29.10 [97,9] FIRMWARE-INCOMPATIBILITY

specificProblems ATCA-PROCESSOR [97] FIRMWARE-INCOMPATIBILITY [9]

eventType Equipment



Alarm Description If the firmware version is not compatible with BSC application, thealarm will be reported.


Impact on System Two cases:1) No scenario is ongoing for specific OMCP, CCP and TPIf the related SBL is IT/FIT and the version check messageis received,the related SBL will be changed to FIT.2) There is scenario ongoing for specific OMCP, CCP and TP. Typically,OMCP, CCP and TP startup scenario.If version check message is received, no state change for related SBL.Typically, the state is from MSD/MSA to MSD/MSA.


Loss No No No No No



484 / 778 3BK 21618 AAAA PCZZA Ed.16


29.11 [97,10] FATAL-HW-FAILURE

specificProblems ATCA-PROCESSOR [97] FATAL-HW-FAILURE [10]

eventType Equipment







Loss - - - - -



[97, 10] FATAL−HW−FAILURE

Alarmsolved

yes

Alarm persists?

no


On−site


3BK 21618 AAAA PCZZA Ed.16 485 / 778


29.12 [97,11] TEMPERATURE-CRITICAL

specificProblems ATCA-PROCESSOR [97] TEMPERATURE-CRITICAL [11]




Alarm Description Hardware or environmental fatal alarm. Temperature of the unit is overthe "critical" threshold. The station is stopped.Room or chassis airconditioning is defective, or the unit over heats.





Loss - - - - -


486 / 778 3BK 21618 AAAA PCZZA Ed.16



[97, 11] TEMPERATURE CRITICAL

Alarmsolved

yes

Alarm persists?

no


On−site


Solve fan related problems

Fan status is ok? Alarm persists?

Environment status is ok?

Solve environment related problems

Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

no

no

3BK 21618 AAAA PCZZA Ed.16 487 / 778


29.13 [97,12] TEMPERATURE-MAJOR

specificProblems ATCA-PROCESSOR [97] TEMPERATURE-MAJOR [12]




Alarm Description Hardware or environmental non-fatal alarm. The unit temperature isover the "major" threshold. The station is still running.The room orchassis air conditioning unit is defective, or the card over heats.


Impact on System The impacted SBL is set to FIT. There is no other system impact.


Loss No No No No No


488 / 778 3BK 21618 AAAA PCZZA Ed.16



Alarmsolved

yes

Alarm persists?

no


On−site



Fan status is ok?Alarm

persists?



Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

[97, 12] TEMPERATURE MAJOR

no

no

3BK 21618 AAAA PCZZA Ed.16 489 / 778


29.14 [97,14] VOLTAGE-FATAL

specificProblems ATCA-PROCESSOR [97] VOLTAGE-FATAL [14]

eventType Equipment



Alarm Description Power supply voltage is over "critical" threshold. The functional statusis impacted and the FRU is powered off.





Loss - - - - -


490 / 778 3BK 21618 AAAA PCZZA Ed.16



Alarmsolved

yes

Alarm persists?

no


On−site


Solve PEM related problems

PEM status is ok? Alarm persists?

Site power supply status is ok?

Solve site power supply related

problems

Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

no

no

[97, 14] VOLTAGE FATAL

3BK 21618 AAAA PCZZA Ed.16 491 / 778


29.15 [97,15] VOLTAGE-MAJOR

specificProblems ATCA-PROCESSOR [97] VOLTAGE-MAJOR [15]

eventType Equipment



Alarm Description Power supply voltage is over "major" threshold. The functional statusmay be impacted.The power status is severely degraded.




Loss No No No No No


492 / 778 3BK 21618 AAAA PCZZA Ed.16



Alarmsolved

yes

Alarm persists?

no


On−site






problems

Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

no

no

[97, 15] VOLTAGE MAJOR

3BK 21618 AAAA PCZZA Ed.16 493 / 778


29.16 [97,16] VOLTAGE-MINOR

specificProblems ATCA-PROCESSOR [97] VOLTAGE-MINOR [16]

eventType Equipment



Alarm Description Power supply voltage is over "minor" threshold. The functional status isnot impacted. The power status is degraded.




Loss No No No No No


494 / 778 3BK 21618 AAAA PCZZA Ed.16



Alarmsolved

yes

Alarm persists?

no


On−site






problems

Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

no

no

[97, 16] VOLTAGE MINOR

3BK 21618 AAAA PCZZA Ed.16 495 / 778


29.17 [97,17] ETHERNET-LINK-FAILURE

specificProblems ATCA-PROCESSOR [97] ETHERNET-LINK-FAILURE [17]

eventType Equipment


perceivedSeverity MI

Alarm Description One Ethernet link of the FRU is down.In case active OMCP is impacted:Any Ethernet link failure will result in a reset of that OMCP and atakeover.In all other cases:If the failure is not on the active Ethernet connection, the alarm israised and no auto defense is done by the BSC.If the alarm is on the active Ethernet connection, then processsupervision mechanisms will trigger an IP failover in the BSC.Consequently the failed link will then become the "not active one" andthe alarm is raised.


Impact on System The impacted SBL state is changed.No system impact due to the active/standby function and IP failover


Loss No No No No No


496 / 778 3BK 21618 AAAA PCZZA Ed.16



yes

Alarm persists?

no


On−site

Replace SSW for the standby

IP plane *

Reset the board raising the alarm

Alarm persists?

Alarm persists?Alarmsolved

no

yes

yes

[97, 17] ETHERNET LINK FAILURE

Check SSW status

Replace the board raising the alarm

no

*: The active IP plane may be mapped on the active or the standby SSW. Thereis no correlation between the two.

In order to identify the standby IP plane, check which is the active and standbyshelf manager. The active IP plane is linked to the active SMM.

Mapping SSW-SMM: SMM(1) is connected to SSW(1) and SMM(2) to SSW(2).

3BK 21618 AAAA PCZZA Ed.16 497 / 778


29.18 [97,18] IPMI-FIRMWARE-NOT-UP-TO-DATE

specificProblems ATCA-PROCESSOR [97] IPMI-FIRMWARE-NOT-UP-TO-DATE [18]

eventType Equipment



Alarm Description When the board is started, an automatic check of the IPMC firmwareversion is performed. This alarm is reported to OMC-R if it is not thelatest version.


Impact on System The ALARM shows that the current IPMC FW version running on TPboard does not fit with the up-to-date FW version. FW version will autoupdate. There is no other system impact.


Loss NO NO NO NO NO


29.18.1 IPMI-FIRMWARE-NOT-UP-TO-DATE

The IPMC FW version running on TP board is automatic updated.

498 / 778 3BK 21618 AAAA PCZZA Ed.16


29.19 [97,19] FIRMWARE-NOT-UP-TO-DATE

specificProblems ATCA-PROCESSOR [97] FIRMWARE-NOT-UP-TO-DATE [19]

eventType Equipment



Alarm Description When the board is started, an automatic check of the firmware versionis performed. This alarm is reported to OMC-R if it is not the supportedversion.


Impact on System The ALARM shows that the current FW version running on OMCP,CCP and TP boards does not fit with the up-to-date FW version. TheSBL of impacted OMCP, CCP and TP is set to FIT. There is no othersystem impact.


Loss NO NO NO NO NO



[97, 19] FIRMWARE NOT UP TO DATE

Alarmsolved

yes

Alarm persists?

no


Perform firmware upgrade procedure

3BK 21618 AAAA PCZZA Ed.16 499 / 778


29.20 [97,20] CONFIGURATION-FAILURE

specificProblems ATCA-PROCESSOR [97] CONFIGURATION-FAILURE [20]




Alarm Description An TP-GSM configuration error occured.


Impact on System The impacted SBL state is changed to FIT. The new TP configurationis not taken into account. There may be transmission inconsistenciesbetween the BSC and the BTS, the MFS or the TC.

The new TP configuration is not taken into account. There may betransmission inconsistencies between the BSC and the BTS, the MFSor the TC.


Loss No No No No No



None - An TP-GSM configuration error occured.

500 / 778 3BK 21618 AAAA PCZZA Ed.16


29.21 [97,21] TAKEOVER-REFUSED

specificProblems ATCA-PROCESSOR [97] TAKEOVER-REFUSED [21]




Alarm Description An TP-GSM configuration error occurred. No takeover was possibledue to unavailable stand-by board.



All CS and PS traffic, all telecom or O&M signalling are stopped duringthe reset of the TP board. If the link between the BSC and the OMC-Ris through Ater, the communication with OMC-R is also stopped duringthe reset of the TP board.Once the TP board is reset, the BSC comes back into traffic.


Loss No No No No No

Degradation Yes Yes Yes Yes Yes


None - No takeover was possible due to unavailable stand-by board.

3BK 21618 AAAA PCZZA Ed.16 501 / 778


29.22 [97,22] CPU-OVERLOAD

specificProblems ATCA-PROCESSOR [97] CPU-OVERLOAD [22]

eventType Equipment

probableCause processorProblem


Alarm Description If the CPU load is crossing up or crossing down very quickly betweentwo CPU overload levels at once, then the event alarm will be sentwhen the first crossing level is reached.


Impact on System Auto TP takeover is triggered and related SBL state is depended oncorresponding actions


Loss No No No No No



None - No action since auto TP takeover is triggered.

502 / 778 3BK 21618 AAAA PCZZA Ed.16


29.23 [97,23] BSC-CONF-UNAVAILABLE

specificProblems ATCA-PROCESSOR [97] BSC-CONF-UNAVAILABLE [23]

eventType Equipment



Alarm Description The configuration running in BSC could not be recognized by TPGSM.Only the BSC-OMCR connection is available.


Impact on System The related TP-HW will change to FIT.


Loss no no no no no



[97, 23] BSC−CONF−UNAVAILABLE


yes

Check the DLS and if it is not OK replace it.

Alarm persists?

noAlarmsolved

3BK 21618 AAAA PCZZA Ed.16 503 / 778


29.24 [97,30] N7-DEVICE

specificProblems ATCA-PROCESSOR [97] N7-DEVICE [30]

eventType Equipment



Alarm Description A major failure is detected in the Power Quicc of the TPGSM board.The Power Quicc carries the MTP2 and MTP1 layers of the SS7 stacks.



When this problem is detected, the BSC triggers a TP takeoverand TP reset. System impacts are due to the TP takeover (seeATCA-PROCESSOR [97], TAKEOVER [1]).


Loss - - - - -



[97, 30] N7 DEVICE

Alarmsolved

yes

Alarm persists?

no


On−site

Replace suspected RIT, if

alarm occurs repetitively

504 / 778 3BK 21618 AAAA PCZZA Ed.16


29.25 [97,31] HDLC-HANDLER

specificProblems ATCA-PROCESSOR [97] HDLC-HANDLER [31]

eventType Equipment



Alarm Description A major failure is detected in the HDLC handler of the TPGSM board.


Impact on System The impacted SBL state is not changed



Loss - - - - -



Alarmsolved

yes

Alarm persists?

no


On−site



[97, 31] HDLC HANDLER

3BK 21618 AAAA PCZZA Ed.16 505 / 778


29.26 [97,32] Q1-HANDLER

specificProblems ATCA-PROCESSOR [97] Q1-HANDLER [32]

eventType Equipment



Alarm Description A major failure is detected in the Qmux handler of the TPGSM board.





Loss - - - - -



Alarmsolved

yes

Alarm persists?

no


On−site



[97, 32] Q1 HANDLER

506 / 778 3BK 21618 AAAA PCZZA Ed.16


29.27 [97,33] RW-HANDLER

specificProblems ATCA-PROCESSOR [97] RW-HANDLER [33]

eventType Equipment



Alarm Description A major failure is detected in the Read/Write handler of the TPGSMboard.





Loss - - - - -



Alarmsolved

yes

Alarm persists?

no


On−site



[97, 33] RW HANDLER

3BK 21618 AAAA PCZZA Ed.16 507 / 778


29.28 [97,34] TDM-FAILURE

specificProblems ATCA-PROCESSOR [97] TDM-FAILURE [34]

eventType Equipment



Alarm Description A major failure is detected in the TDM switch of the TPGSM board.





Loss - - - - -



Alarmsolved

yes

Alarm persists?

no


On−site



[97, 34] TDM FAILURE

508 / 778 3BK 21618 AAAA PCZZA Ed.16


29.29 [97,35] E1-FRAMER

specificProblems ATCA-PROCESSOR [97] E1-FRAMER [35]

eventType Equipment



Alarm Description A major failure is detected in the E1 handlers of the TPGSM board.





Loss - - - - -



Alarmsolved

yes

Alarm persists?

no


On−site



[97, 35] E1 FRAMER

3BK 21618 AAAA PCZZA Ed.16 509 / 778


29.30 [97,36] TP-MAIN-SW-ERROR

specificProblems ATCA-PROCESSOR [97] TP-MAIN-SW-ERROR [36]

eventType Equipment



Alarm Description A major failure is detected in the TP_MAIN process of the TPGSMboard.





Loss - - - - -



None - A major failure was detected in a process of the TPGSM board.

510 / 778 3BK 21618 AAAA PCZZA Ed.16


29.31 [97,37] TP-MAIN-FILE-ERROR

specificProblems ATCA-PROCESSOR [97] TP-MAIN-FILE-ERROR [37]

eventType Equipment



Alarm Description TPGSM board download is not successfully and the configuration fromthe OMCP board. is used.





Loss - - - - -



None - TPGSM board download was not successfully.

3BK 21618 AAAA PCZZA Ed.16 511 / 778


29.32 [97,38] TP-MAIN-ACCESS-PB

specificProblems ATCA-PROCESSOR [97] TP-MAIN-ACCESS-PB [38]

eventType Equipment



Alarm Description Data exchanges between the active and standby boards are notsuccessful.





Loss - - - - No


512 / 778 3BK 21618 AAAA PCZZA Ed.16



[97, 38] TP MAIN ACCESS PB

Alarmsolved

yes

Alarm persists?

no


Reset standby TP board

Solve hardware relatedvalarms

Hardware related alarms are

present?

Alarm persists?

Alarmsolved

no

no yes

yes

3BK 21618 AAAA PCZZA Ed.16 513 / 778


29.33 [97,39] SS7-SW-ERROR

specificProblems ATCA-PROCESSOR [97] SS7-SW-ERROR [39]

eventType Equipment



Alarm Description A major failure is detected in the TP_SS7 process of the TPGSM board.





Loss - - - - -



None - A major failure was detected in the TP_SS7 process of the TPGSMboard.

514 / 778 3BK 21618 AAAA PCZZA Ed.16


29.34 [97,40] CS-TEL-TEST-NOK

specificProblems ATCA-PROCESSOR [97] CS-TEL-TEST-NOK [40]




Alarm Description Upon the CS telecome outage suspecting for one CCP, the telecomtest for Abis interface is triggered and the test result is not OK.


Impact on System related CCP will change to FIT


Loss no no no no no



[97, 40] CS−TEL−TEST−NOK


yes

Reset the related CCP board.

Alarm persists?

noAlarmsolved

3BK 21618 AAAA PCZZA Ed.16 515 / 778


29.35 [97,50] NE1OE-FAILURE

specificProblems ATCA-PROCESSOR [97] NE1OE-FAILURE [50]

eventType Equipment



Alarm Description There is a failure of the NE1oE module on TP-GSM.





Loss No No No No No


516 / 778 3BK 21618 AAAA PCZZA Ed.16



[97, 50] NE1OE FAILURE

Alarmsolved

yes

Alarm persists?

no


On−site

Replace TP board

Solve SSW related problems

SSW status ok?Alarm

persists?

yesyes

no Alarmsolved

no

3BK 21618 AAAA PCZZA Ed.16 517 / 778


29.36 [97,51] E1-SL-FAILURE

specificProblems ATCA-PROCESSOR [97] E1-SL-FAILURE [51]

eventType Equipment



Alarm Description NE1oE module on the TP-GSM has reported a 16E1 SL failure withthe processing part





Loss - - - - -



[97, 51] E1 SL FAILURE

Alarmsolved

yes

Alarm persists?

no


On−site

Replace TP board if alarm occurs

repetitively

518 / 778 3BK 21618 AAAA PCZZA Ed.16


29.37 [97,60] TP-CAP

specificProblems ATCA-PROCESSOR [97] TP-CAP [60]

eventType Equipment



Alarm Description Two case that the alarm will be sent:1. During BSC startup, if HSL or IPoE1 is enabled, but TPGSMdoes not have the corresponding capabilities, can’t support so manyAtermux. TPGSM is forced to power off.2. When STM-1 feature is activated, if TP version is less than 3(TP1&TP2). TPGSM is forced to power off.


Impact on System FOS when alarm begins, IT when alarm ends


Loss NO NO NO NO NO



[97,60] TP−CAP


yes

Replace TP board with correct version

On−site

Alarm persists?

noAlarmsolved

3BK 21618 AAAA PCZZA Ed.16 519 / 778


29.38 [97,61] TPIP-FAILURE

specificProblems ATCA-PROCESSOR [97] TPIP-FAILURE [61]

eventType Equipment



Alarm Description It indicates the status of TPIP daughter board of TPGSM. TPGSMsend a notification mpTpgNotifyFailure when it detects TPIP failureor end of failure.


Impact on System FLT when alarm begins, FLT/IT when alarm ends


Loss NO NO NO NO NO



[97, 61] TPIP−FAILURE

Alarmsolved

yes

Alarm persists?

no


On−site

Replace TP board

IPOverE1 is activated?

yesno

520 / 778 3BK 21618 AAAA PCZZA Ed.16


29.39 [97,62] CONFIG-IP-FAILURE

specificProblems ATCA-PROCESSOR [97] CONFIG-IP-FAILURE [62]

eventType Equipment



Alarm Description Config IP address failure


Impact on System FLT when alarm begins, IT when alarm ends


Loss NO NO NO NO NO



[97, 62] CONFIG−IP−FAILURE

Alarmsolved

yes

Alarm persists?

no


Check DLS for IP configuration

3BK 21618 AAAA PCZZA Ed.16 521 / 778


29.40 [97,63] CONFIG-IP-INPUT-ERROR

specificProblems ATCA-PROCESSOR [97] CONFIG-IP-INPUT-ERROR [63]

eventType Equipment



Alarm Description input parameter of Config IP address is not correct.




Loss NO NO NO NO NO



[97, 63] CONFIG−IP−INPUT−ERROR

Alarmsolved

yes

Alarm persists?

no



522 / 778 3BK 21618 AAAA PCZZA Ed.16


29.41 [97,64] CONFIG-IP-RUNTIME-FAILURE

specificProblems ATCA-PROCESSOR [97] CONFIG-IP-RUNTIME-FAILURE [64]

eventType Equipment



Alarm Description this alarm is sent out when config IP address store parameter in diskfailure




Loss NO NO NO NO NO



[97, 64] CONFIG−IP−RUNTIME−FAILURE

Alarmsolved

yes

Alarm persists?

no



3BK 21618 AAAA PCZZA Ed.16 523 / 778


29.42 [97,65] DRIVERS-FAILURE

specificProblems ATCA-PROCESSOR [97] DRIVERS-FAILURE [65]

eventType Equipment


perceivedSeverity PMA(Major)

Alarm Description when the TP startup , the driver load error log file should be checked ,if there is no any error ,tp will startup normally , otherwise , tp will sentthe alarm to bsc ,and wait for poweroff.


Impact on System TP board will be power off.


Loss no no no no no



[97, 65] DRIVERS−FAILURE

Alarmsolved

yes

Alarm persists?

no


There is a hardware problem.

Replace TP board.

524 / 778 3BK 21618 AAAA PCZZA Ed.16


29.43 [97,66] HW-DIAGNOSIS-FAILURE

specificProblems ATCA-PROCESSOR [97] HW-DIAGNOSIS-FAILURE [66]

eventType Equipment



Alarm Description TP will check the status file(which is store the hw-diagnosis), and sendthe alarm if there is any error.


Impact on System The notified TPGSM board will reset.


Loss no no no no no



[97, 66] HW−DIAGNOSIS−FAILURE

Alarmsolved

yes

Alarm persists?

no


There is a hardware problem.

Replace TP board.

3BK 21618 AAAA PCZZA Ed.16 525 / 778


29.44 [97,67] INTER-TP-ACCESS-PB

specificProblems ATCA-PROCESSOR [97] INTER-TP-ACCESS-PB [67]

eventType Equipment



Alarm Description BSC sends this alarm when the TPGSM detects the Time Out alarmon the TPGSM link between both TPGSM used to carry the STM1 APSdata, The notified TPGSM has its SBL TP-HW state changed to FIT.


Impact on System If the alarm is on at active TP board, The STM1 signal carried from theStandby board cannot be used any more, The STM1 paths are nomore in 1+1 redundancy, Whether a STM1 TTP on the Active boardis in FLT, the traffic of this STM1 itf is lost. See the BSC-Trans alarmfor the STM1-TTP and STM1-itf SBL. If the alarm is on at standby TPboard, no impact until the borad became to active.


Loss no no no no no



[97, 67] INTER−TP− ACCESS−PB

Alarmsolved

yes

Alarm persists?

no


Reset the TP board

526 / 778 3BK 21618 AAAA PCZZA Ed.16

30 Class 98: ATCA-SWITCH Alarms


This section defines the BSC alarms for the Class 98: ATCA-SWITCH alarmclass.

3BK 21618 AAAA PCZZA Ed.16 527 / 778


30.1 [98,0] RESET

specificProblems ATCA-SWITCH [98] RESET [0]




Alarm Description The Switch board has reset


Impact on System The impacted SBL state is not changed. There is no other systemimpact.


Loss No No No No No



None - The Switch board was reset.

528 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems ATCA-SWITCH [98] ACCESS-FAIL [3]

eventType Equipment



Alarm Description The board cannot start because of problems in the INIT sequence(Timeout on Board Ready or timeout of MXPF service request for thisboard.) or handles of the boards are opened. The board is powered off


Impact on System The impacted SBL state is changed to FLT.There is no system impact if mate board works well.


Loss NO NO NO NO NO



[98, 3] ACCESS FAIL

Alarmsolved


Reset target board

Alarm persists?

no

yes

3BK 21618 AAAA PCZZA Ed.16 529 / 778



specificProblems ATCA-SWITCH [98] UNPLUGGED [6]

eventType Equipment



Alarm Description The board has been removed from the ATCA shelf. The alarm iscleared at board re-insertion.


Impact on System The board is powered off and the impacted SBL is set to FLT.All traffic is redirected to the other SSW-HW. But if the alarm occurs onthe first SSW-HW, the communication with the external alarm box islost (if it is one is installed).


Loss No No No No No

Degradation No No No No Yes (if OMC-R isconnected directly)


[98, 6] UNPLUGGED

yesContact

System Support

Re−insert the boardBoard is correctly inserted?

Alarm persists?

Alarmsolved

no

yes

no

530 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems ATCA-SWITCH [98] FW-UPGRADE-UNSUCCESS [7]

eventType Equipment







Loss No No No No No




Alarmsolved

yes

Alarm persists?

no



3BK 21618 AAAA PCZZA Ed.16 531 / 778



specificProblems ATCA-SWITCH [98] FW-UPGRADE [8]








Loss No No No No No




532 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems ATCA-SWITCH [98] FIRMWARE-INCOMPATIBILITY [9]

eventType Equipment





Impact on System Two cases:1) No scenario is ongoing for specific SSWIf the related SBL is IT/FIT and the version check messageis received,the related SBL will be changed to FIT.2) There is scenario ongoing for specific SSW. Typically, SSW startupscenario.If version check message is received, no state change for related SBL.Typically, the state is from MSD/MSA to MSD/MSA.


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 533 / 778



[98, 9] FIRMWARE−INCOMPATIBILITY

Reset or unplug/plugSSW to trigger firmware

upgrade

Alarmsolved

yes

Alarm persists?

no


Any scenario ongoing for

SSW?

no yes

Firmware upgrade is triggered automatically.

Pay attention to conditions to trigger firmware

upgrade successfully

yes

Alarm persists?

no


534 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems ATCA-SWITCH [98] FATAL-HW-FAILURE [10]

eventType Equipment



Alarm Description The alarm can be raised in two cases, but with different target states.

Case 1: fatal alarm with target state = FLTThere is a hardware fault on the switch and it is powered off.Case 2: non fatal alarm with target state = FITWhen the negotiated bitrate of a mandatory 1Gbps ethernet link of theSSW is found to be less than 1 Gbps.The bitrate of Gbit Ethernet links is auto-negotiated between the peersof the connection.

The SSW port bitrates, for mandatory Gbps Ethernet ports, arechecked in the following conditions:- Ethernet connected FRU is inserted (or power on)- Ethernet connected FRU is reset- BSC system initialization (including BSC power on, BSC reset)- At predefined intervals - every 15 minutes.The ports that are mandatory 1Gbps are blade FRU ports (TPGSM,CCP, OMCP) and MUX connection (nE1oE).If the bitrate is found to be less than 1Gbps, the alarm is raised.


Impact on System Case 1: The SSW board is powered off and the impacted SBL is set toFLT.All traffic is redirected to the other SSW-HW. But if the alarm occurs onthe first SSW-HW, the communication with the external alarms box islost (if one is installed).Case 2: The alarm is non-fatal and the SSW SBL is set to FIT.The BSC may have reduced performance due to bandwidthbottlenecks.In case the MUX connection is impacted, the lower bitrate may have animpact on the nE1oE performance (and E1 states) dependent on thenumber of E1 configured in the BSC.It is advised to trigger a RESET of the concerned SSW SBL in order toswitch IP traffic to the redundant SSW plane.


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 535 / 778


30.7.1 Corrective Action for Case 1

[98, 10] FATAL HW FAILURE

Alarmsolved

yes

Alarm persists?

no


On−site

Replace SSW

Replace SSW ARTM

Replace ARTM or FRU *

Alarm persists?

Alarm persists?

no

no

yes

yes

On−site

On−site

* ARTM or FRU to be determined from the port number in additional data

536 / 778 3BK 21618 AAAA PCZZA Ed.16


30.7.2 Corrective Action for Case 2

The impacted port number on the SSW can be found in the additional data ofthe alarm.

The problem can be due to peer of the concerned Ethernet link.


Alarmsolved

yes

Alarm persists?

no


On−site

Replace SSW

Replace SSW ARTM

Replace MUX

Alarm persists?

Alarm persists?

no

no

yes

yes

On−site

On−site

* ARTM or FRU to be determined from the port number in additional data

Port number is 18 or other?

yes

Alarm persists?

no

On−site

Replace SSW

Replace FRU *

Alarm persists?

no

yes

yes

On−site

Replace cable between SSW ARTM

port 2 and MUX

Alarm persists?

Port 18 Any other port number

3BK 21618 AAAA PCZZA Ed.16 537 / 778


30.8 [98,11] TEMPERATURE-FATAL

specificProblems ATCA-SWITCH [98] TEMPERATURE-FATAL [11]




Alarm Description Hardware or environmental fatal alarm. Temperature of the unit is overthe "critical" threshold. The SSW is switched off.

"critical" threshold:>80 degrees or < -10 degree.


Impact on System The board is powered off and the impacted SBL is set to FLT.All traffic is redirected to the other SSW-HW. But if the alarm occurson the first SSW-HW, the communication with the external alarm boxis lost (if one is installed).


Loss No No No No No


538 / 778 3BK 21618 AAAA PCZZA Ed.16



Alarmsolved

yes

Alarm persists?

no


On−site

Replace SSW



persists?



Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

no

no

[98, 11] TEMPERATURE FATAL

3BK 21618 AAAA PCZZA Ed.16 539 / 778



specificProblems ATCA-SWITCH [98] TEMPERATURE-MAJOR [12]




Alarm Description Hardware or environmental major alarm. Temperature of the unit isover the "major" threshold. That may impact the functional status.

"major" threshold:80 degree > temp>75degrees or -10 degree < temp < -5 degree




Loss No No No No No


540 / 778 3BK 21618 AAAA PCZZA Ed.16



Alarmsolved

yes

Alarm persists?

no


On−site

Replace SSW





Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

no

no


3BK 21618 AAAA PCZZA Ed.16 541 / 778


30.10 [98,13] TEMPERATURE-MINOR

specificProblems ATCA-SWITCH [98] TEMPERATURE-MINOR [13]




Alarm Description Hardware or environmental minor alarm. Temperature of the unit isover the "minor" threshold. The functional status is not impacted.

"minor" threshold:75 degree> temp>65degrees or -5 degree<temp< 0 degree




Loss No No No No No


542 / 778 3BK 21618 AAAA PCZZA Ed.16



Alarmsolved

yes

Alarm persists?

no


On−site

Replace SSW





Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

no

no

[98, 13] TEMPERATURE MINOR

3BK 21618 AAAA PCZZA Ed.16 543 / 778



specificProblems ATCA-SWITCH [98] VOLTAGE-FATAL [14]

eventType Equipment



Alarm Description Power supply voltage is over "critical" threshold. The functional statusis impacted and the SSW is powered off.


Impact on System The board is powered off and the impacted SBL is set to FLT.All traffic is redirected to the other SSW-HW. But if the alarm occurson the first SSW-HW, the communication with the external alarm boxis lost (if one is installed).


Loss No No No No No


544 / 778 3BK 21618 AAAA PCZZA Ed.16



Alarmsolved

yes

Alarm persists?

no


On−site

Replace SSW





problems

Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

no

no


3BK 21618 AAAA PCZZA Ed.16 545 / 778



specificProblems ATCA-SWITCH [98] VOLTAGE-MAJOR [15]

eventType Equipment



Alarm Description Power supply voltage is over "major" threshold. The functional statusmay be impacted.The power status is severely degraded.




Loss No No No No No


546 / 778 3BK 21618 AAAA PCZZA Ed.16



Alarmsolved

yes

Alarm persists?

no


On−site

Replace SSW





problems

Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

no

no

[98, 15] VOLTAGE MAJOR

3BK 21618 AAAA PCZZA Ed.16 547 / 778



specificProblems ATCA-SWITCH [98] VOLTAGE-MINOR [16]

eventType Equipment



Alarm Description Power supply voltage is over "minor" threshold. The functional status isnot impacted. The power status is degraded.




Loss No No No No No


548 / 778 3BK 21618 AAAA PCZZA Ed.16



Alarmsolved

yes

Alarm persists?

no


On−site

Replace SSW





problems

Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

no

no

[98, 16] VOLTAGE MINOR

3BK 21618 AAAA PCZZA Ed.16 549 / 778


30.14 [98,18] IP-ROUTER-LINK-FAIL

specificProblems ATCA-SWITCH [98] IP-ROUTER-LINK-FAIL [18]

eventType Equipment



Alarm Description The router to the external network is not reachable, the link is down orthe router is out of service.


Impact on System The impacted SBL is set to FIT.The external traffic towards the OMC-R or the CBC is redirected to theother SSW-HW and the other IP router link. Some file transfers withOMC-R may be interrupted, but if this happens the OMC-R requeststhe information again.If the alarm occurs on the first SSW-HW, the communication with theexternal alarm box is lost (if one is installed).


Loss No No No No No


550 / 778 3BK 21618 AAAA PCZZA Ed.16



[98, 18] IP ROUTER LINK FAILED

Alarmsolved

yes

no


Reset SSW

Alarm persists?

IP router status is ok?

IP router configuration is ok?

Ethernet cable is ok?

Alarmsolved

no

Solve router related issues

Correct IP router configuration

Replace Ethernet cable

Alarm persists?

Alarm persists?

Alarm persists?

yes

yes

yes

no

no

no

no

no

yes

3BK 21618 AAAA PCZZA Ed.16 551 / 778


30.15 [98,19] TELECOM-LINK-FAIL

specificProblems ATCA-SWITCH [98] TELECOM-LINK-FAIL [19]

eventType Equipment



Alarm Description This alarm is generated when the telecom router is not reachablethrough this switch


Impact on System The impacted SBL is set to FIT.


Loss No No No No No


552 / 778 3BK 21618 AAAA PCZZA Ed.16



[98, 19] TELECOM−LINK−FAIL

Alarmsolved

yes

Alarm persists?

no


Reset SSW

Check IP router status/configuration

Alarm persists?

Check Ethernet cable

Alarm persists?

no

no

yes

yes

3BK 21618 AAAA PCZZA Ed.16 553 / 778


30.16 [98,20] OAM-LINK-FAIL

specificProblems ATCA-SWITCH [98] OAM-LINK-FAIL [20]

eventType Equipment



Alarm Description This alarm is generated when the O&M router is not reachable throughthis switch




Loss No No No No No


554 / 778 3BK 21618 AAAA PCZZA Ed.16



[98, 20] OAM−LINK−FAIL

Alarmsolved

yes

Alarm persists?

no


Reset SSW


Alarm persists?


Alarm persists?

no

no

yes

yes

3BK 21618 AAAA PCZZA Ed.16 555 / 778



specificProblems ATCA-SWITCH [98] FIRMWARE-NOT-UP-TO-DATE [21]

eventType Equipment





Impact on System The ALARM shows that the current FW version running on SSWboards does not fit with the up-to-date FW version. The SBL ofimpacted SSW is set to FIT. There is no other system impact.


Loss no no no no no




Alarmsolved

yes

Alarm persists?

no



556 / 778 3BK 21618 AAAA PCZZA Ed.16


30.18 [98,22] IP-CONFIG-FAIL

specificProblems ATCA-SWITCH [98] IP-CONFIG-FAIL [22]

eventType Equipment



Alarm Description The alarm is generatel when IP config fail




Loss no no no no no

Degradation no no no no Yes (if OMC-R isconnected directly)

3BK 21618 AAAA PCZZA Ed.16 557 / 778



[98, 22] IP−CONFIG−FAIL

Alarmsolved

yes

Alarm persists?

no


Reset SSW


Alarm persists?


Alarm persists?

no

no

yes

yes

558 / 778 3BK 21618 AAAA PCZZA Ed.16


30.19 [98,23] ASIG-OVER-IP-LINK-FAIL

specificProblems ATCA-SWITCH [98] ASIG-OVER-IP-LINK-FAIL [23]

eventType Equipment



Alarm Description The alarm is generated when A singnal over IP link fail




Loss no no no no no


3BK 21618 AAAA PCZZA Ed.16 559 / 778



[98, 23] ASIG−OVER−IP−LINK−FAIL

Alarmsolved

yes

Alarm persists?

no


Reset SSW


Alarm persists?


Alarm persists?

no

no

yes

yes

560 / 778 3BK 21618 AAAA PCZZA Ed.16


30.20 [98,24] BSS-OVER-IP-LINK-FAIL

specificProblems ATCA-SWITCH [98] BSS-OVER-IP-LINK-FAIL [24]

eventType Equipment



Alarm Description The alarm is generated when BSS over IP link fail.




Loss no no no no no


3BK 21618 AAAA PCZZA Ed.16 561 / 778



[98, 24] BSS−OVER−IP−LINK−FAIL

Alarmsolved

yes

Alarm persists?

no


Reset SSW


Alarm persists?


Alarm persists?

no

no

yes

yes

562 / 778 3BK 21618 AAAA PCZZA Ed.16

31 Class 99: ATCA-SHELF Alarms


This section defines the BSC alarms for the Class 99: ATCA-SHELF alarmclass.

3BK 21618 AAAA PCZZA Ed.16 563 / 778


31.1 [99,0] RESET

specificProblems ATCA-SHELF [99] RESET [0]




Alarm Description The board has reset.


Impact on System The state of the SBL is not changed. There is no other system impact.


Loss No No No No No



None - The board was reset.

564 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems ATCA-SHELF [99] ACCESS-FAIL [3]

eventType Equipment



Alarm Description The board cannot start because of problems in the INIT sequence(Timeout on Board Ready or timeout of MXPF service request for thisboard.) or handles of the boards are opened. The board is powered off.


Impact on System The impacted SBL(SMM is not impacted) state is changed to FLT.There is no system impact if the mate board works well.


Loss NO NO NO NO NO



[99, 3] ACCESS FAIL

Alarmsolved


Reset target board

Alarm persists?

no

yes

3BK 21618 AAAA PCZZA Ed.16 565 / 778



specificProblems ATCA-SHELF [99] UNPLUGGED [6]

eventType Equipment



Alarm Description The board has been removed from the ATCA shelf. The alarm iscleared at board re-insertion.


Impact on System The impacted SBL is set to FLT. There is no other system impact: shelfmanagers, personality cards, fans and PEM are redundant.

There is no other system impact.


Loss No No No No No



yesContact

System Support


Alarm persists?

Alarmsolved

no

yes

no

[99, 6] UNPLUGGED

566 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems ATCA-SHELF [99] FW-UPGRADE-UNSUCCESS [7]

eventType Equipment







Loss No No No No No




Alarmsolved

yes

Alarm persists?

no



3BK 21618 AAAA PCZZA Ed.16 567 / 778



specificProblems ATCA-SHELF [99] FW-UPGRADE [8]



perceivedSeverity minor(DMA)

Alarm Description Operator has launched firmware upgrade in the board on the field.Alloperations on this board(lock,reset) are rejected while this alarm isactive.




Loss No No No No No


31.5.1 Corrective Actions


568 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems ATCA-SHELF [99] FIRMWARE-INCOMPATIBILITY [9]

eventType Equipment





Impact on System Two cases:1) No scenario is ongoing for specific SMM, PEM, FAN, PCIf the related SBL is IT/FIT and the version check messageis received,the related SBL will be changed to FIT.2) There is scenario ongoing for specific SMM, PEM, FAN, PC.Typically, SMM, PEM, FAN, PC startup scenario.If version check message is received, no state change for related SBL.Typically, the state is from MSD/MSA to MSD/MSA.


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 569 / 778



[99, 9] FIRMWARE−INCOMPATIBILITY

Reset or unplug/plugSMM/PEM/FAN/PC to

trigger firmware upgrade

Alarmsolved

yes

Alarm persists?

no


Any scenario ongoing for SMM/

PEM/FAN/PC?

no yes

Firmware upgrade is triggered automatically.

Pay attention to conditions to trigger firmware

upgrade successfully

yes

Alarm persists?

no


570 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems ATCA-SHELF [99] FATAL-HW-FAILURE [10]

eventType Equipment



Alarm Description There is a hardware fault on the FRU or, in case of standby SMM, thehandles of the boards are opened.The FRU is powered off.

Alarm on FAN(1) SBL:A special case is the occurrence of this alarm on a FAN(1) SBL.In this case the alarm indicates that a IPMB communication problemhas been detected in the ATCA shelf.The FAN(1) SBL has been reused for backward compatibility reasons(patch on previous releases).

IPMB communication quality is checked online by the application usinga utility that is running on the standby SMM.Every 5 minutes the results of this check are analyzed.If a new problem is detected, then the standby SMM is reset and thetest is repeated.If the problem is confirmed, the alarm is raised.


Impact on System Case 1: Occurrence on SMM SBL:The board is powered off and the SBL is set to FLT. There is no othersystem impact since the FRU is redundant.Case 2: PEM, Personality Card:No impact.Case 3: FAN(1) SBL:IPMB communication errors are occurring and this may lead to lostresources from platform middleware point of view.Provided the right patch level is applied for this lost resource problem,there should be no operational impact on the BSC.O&M functionality and accuracy may be reduced.


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 571 / 778




Alarmsolved

yes

Alarm persists?

no


Impacted FRU is?SMM

PEM or PC

FAN

Replace SMMReplace

suspected RITKeep monitoring the

BSC

Single ON/OFF occurrence?


noyes

Is alarm mapped on the same

board?

If most boards are impacted is it a shelf

issue


Alarm persists?

no

yes

yes

no

Note: Detailed information can be seen in the Additional Information.

The corresponding relation between IPMI address and physical slot is like this:

IPMIAddress

Physicalslot

IPMIAddress

Physicalslot

IPMIAddress

Physicalslot

IPMIAddress

Physicalslot

9A 01 84 08 C0 33 12 66

96 02 88 09 C2 34 C8 81

92 03 8C 10 C4 35 CA 82

8E 04 90 11 C6 36 CC 83

8A 05 94 12 14 29 CE 84

86 06 98 13 16 50

82 07 9C 14 10 65

572 / 778 3BK 21618 AAAA PCZZA Ed.16


31.8 [99,11] TEMPERATURE-FATAL

specificProblems ATCA-SHELF [99] TEMPERATURE-FATAL [11]




Alarm Description Hardware or environmental fatal alarm. Temperature of the unit is overthe "critical" threshold. The board is switched off.

"critical" threshold:>65 degrees or < -10 degree.


Impact on System The board is powered off and the impacted SBL is set to FLT. There isno other system impact: shelf managers, fans and PEM are redundant.

There is no other system impact.


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 573 / 778



Alarmsolved

yes

Alarm persists?

no


On−site

Replace faulty board



persists?



Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

no

no

[99, 11] TEMPERATURE FATAL

574 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems ATCA-SHELF [99] TEMPERATURE-MAJOR [12]




Alarm Description Hardware or environmental major alarm. Temperature of the unit isover the "major" threshold. That may impact the functional status.

"major" threshold:(60—-65 degree) or (-10—-0)




Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 575 / 778



Alarmsolved

yes

Alarm persists?

no


On−site




persists?



Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

no

no


576 / 778 3BK 21618 AAAA PCZZA Ed.16


31.10 [99,13] TEMPERATURE-MINOR

specificProblems ATCA-SHELF [99] TEMPERATURE-MINOR [13]




Alarm Description Hardware or environmental minor alarm. Temperature of the unit isover the "minor" threshold. The functional status is not impacted.

"Minor" threshold:(55—60 degree) or (0—5degree)




Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 577 / 778



Alarmsolved

yes

Alarm persists?

no


On−site




persists?



Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

no

no

[99, 13] TEMPERATURE MINOR

578 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems ATCA-SHELF [99] VOLTAGE-FATAL [14]

eventType Equipment



Alarm Description Power supply voltage is over "critical" threshold. The functional statusis impacted and the board is powered off.Detail threshold are as following:– Input Voltage: LoCri=-40.00 or HiCri=-98.00or– Output Voltage: LoCri=-38.80 or HiCri=-96.80or– Output Current: HiCri =54.80Any one of above thresshold is reached, the alarm will be sent


Impact on System The board is powered off and the impacted SBL is set to FLT. There isno other system impact: PEM are redundant.


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 579 / 778



Alarmsolved

yes

Alarm persists?

no


On−site






problems

Alarm persists?

Alarmsolved

no

no

yes

yes yes

yes

no

no


580 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems ATCA-SHELF [99] VOLTAGE-MAJOR [15]

eventType Equipment



Alarm Description Power supply voltage is over "major" threshold. The functional statusmay be impacted.The power status is severely degraded.Detail threshold are as following:– Input Voltage: LoMaj=-40.80 or HiMaj=-72.00or– Output Voltage: LoMaj=-40.00 or HiMaj=-70.80or– Output Current: HiMaj =48.80Any one of above thresshold is reached, the alarm will be sent




Loss No No No No No



No corrective action is required for this alarm. It is removed from more recentBSC software versions.

3BK 21618 AAAA PCZZA Ed.16 581 / 778



specificProblems ATCA-SHELF [99] VOLTAGE-MINOR [16]

eventType Equipment



Alarm Description Power supply voltage is over "minor" threshold. The functional status isnot impacted. The power status is degraded.Detail threshold are as following:– Input Voltage: LoMin=-44.00 or HiMin=-62.00or– Output Voltage: LoMin=-42.80 or HiMin=-60.80or– Output Current: HiMin =44.80Any one of above thresshold is reached, the alarm will be sent




Loss No No No No No



No corrective action is required for this alarm. It is removed from more recentBSC software versions.

582 / 778 3BK 21618 AAAA PCZZA Ed.16


31.14 [99,17] ETHERNET-LINK-FAILURE

specificProblems ATCA-SHELF [99] ETHERNET-LINK-FAILURE [17]

eventType Equipment



Alarm Description One of the two Ethernet links of the FRU is down. The board is resetby the BSC application.


Impact on System The impacted SBL state is not changed. System impacts are due toprevious reset event (see ATCA-SHELF [99], RESET [0]).


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 583 / 778



[99, 17] ETHERNET LINK FAILURE

Alarmsolved

yes

Alarm persists?

no


On−site

Replace SSW

SSW status is ok?yes

no

584 / 778 3BK 21618 AAAA PCZZA Ed.16


31.15 [99,18] SHELF-MANAGER-ACCESS-PB

specificProblems ATCA-SHELF [99] SHELF-MANAGER-ACCESS-PB [18]

eventType Equipment



Alarm Description The shelf management board not reachable. Either the board is out ofservice, or the ethernetlink between the board and the OMCP is down.



There is no other system impact: the second shelf manager becomesactive.


Loss No No No No No



None - The shelf management board is not reachable.

3BK 21618 AAAA PCZZA Ed.16 585 / 778


31.16 [99,19] FAN-FAILURE

specificProblems ATCA-SHELF [99] FAN-FAILURE [19]

eventType Equipment

probableCause coolingFanFailure


Alarm Description One of the chassis’s fan units has failed. The platform is still running.


Impact on System The impacted SBL is set to FLT. There is no other system impact: othercooling fans increased their speed.

There is no other system impact: other cooling fans increase theirspeed.


Loss No No No No No



[99, 19] FAN FAILURE

Alarmsolved

yes

Alarm persists?

no


On−site

Replace FAN

586 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems ATCA-SHELF [99] FIRMWARE-NOT-UP-TO-DATE [20]

eventType Equipment





Impact on System The ALARM shows that the current FW version running on FAN, PEM,SMM, PC boards does not fit with the up-to-date FW version. TheSBL of impacted FAN, PEM, SMM, PC is set to FIT. There is no othersystem impact.


Loss no no no no no



[99, 20] FIRMWARE−NOT−UP−TO−DATE

Alarmsolved

yes

Alarm persists?

no



3BK 21618 AAAA PCZZA Ed.16 587 / 778


31.18 [99,21] IPMI-BUS-FAIL

specificProblems ATCA-SHELF [99] IPMI-BUS-FAIL [21]

eventType Equipment



Alarm Description An IPMB communication problem has been detected in the ATCA shelf.

IPMB communication quality is checked online by the application usinga utility which is running on the standby SMM.Every 5 minutes the results of this check are analyzed.Before raising the alarm, a new problem needs to be confirmed in thenext 5 minute test period.


Impact on System IPMB communication errors are occurring and this may lead to lostresources from platform middleware point of view.Due to SW workarounds since B10MR2, there should be no operationalimpact on the BSC.O&M functionality and accuracy may be reduced (missing alarms).FW upgrade of IPMI firmware of FRUs may fail due to these IPMIcommunication problems.


Loss no no no no no


588 / 778 3BK 21618 AAAA PCZZA Ed.16



[99,21] IPMI−BUS−FAIL

Keep monitoring the BSC

Single ON / OFF occurrence?


noyes

Alarm persists? Alarmsolved

yes

no

3BK 21618 AAAA PCZZA Ed.16 589 / 778


590 / 778 3BK 21618 AAAA PCZZA Ed.16

32 Class 100: LIU-SHELF Alarms


This section defines the BSC alarms for the Class 100: LIU-SHELF alarm class.

3BK 21618 AAAA PCZZA Ed.16 591 / 778


32.1 [100,0] RESET

specificProblems LIU-SHELF [100] RESET [0]




Alarm Description The MUX board has reset.


Impact on System The BSC triggers a MUX takeover.


Loss No No No No No



None - The MUX board was reset.

592 / 778 3BK 21618 AAAA PCZZA Ed.16


32.2 [100,1] MUX-TAKEOVER

specificProblems LIU-SHELF [100] MUX-TAKEOVER [1]

eventType Equipment



Alarm Description MUX board switchover has occurred, there is no impact on telecomtraffic.


Impact on System The impacted SBL state is not changed. There is no system impact.


Loss No No No No No



None - MUX board switchover was performed.

3BK 21618 AAAA PCZZA Ed.16 593 / 778



specificProblems LIU-SHELF [100] ACCESS-FAIL [4]

eventType Equipment



Alarm Description Alarm on LIU board, reported when both MUX boards report a seriallink failure.



All BTS of all Abis managed by the faulty ETU are lost. It is no morepossible to have telecom traffic or O&M supervision with these BTS.All Atermux managed by the faulty ETU are lost. On going telecomtraffic using these Atermux is stopped. New traffic and signaling will beestablished by using Atermux managed by another ETU.


Loss Yes Yes Yes Yes Yes



[100, 4] ACCESS FAIL

Alarmsolved

yes

Alarm persists?

no


On−site

Replace LIU board

594 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems LIU-SHELF [100] UNPLUGGED [6]

eventType Equipment



Alarm Description LIU board is detected as unplugged by the LIU shelf.



All BTS of all Abis managed by the faulty ETU are lost. It is no morepossible to have telecom traffic or O&M supervision with these BTS. AllAtermux managed by the faulty ETU are lost. On going telecom trafficusing these Atermux is stopped. New traffic and signaling couldwill beestablished by using Atermux managed by another ETU.


Loss Yes Yes Yes Yes Yes



yesContact

System Support


Alarm persists?

Alarmsolved

no

yes

no

[100, 6] UNPLUGGED

3BK 21618 AAAA PCZZA Ed.16 595 / 778



specificProblems LIU-SHELF [100] FW-UPGRADE-UNSUCCESS [7]

eventType Equipment







Loss No No No No No




Alarmsolved

yes

Alarm persists?

no



596 / 778 3BK 21618 AAAA PCZZA Ed.16


32.6 [100,8] FW-UPGRADE

specificProblems LIU-SHELF [100] FW-UPGRADE [8]




Alarm Description Operator has launched firmware upgrade in the board on this field. Alloperations on this board(reset) are rejected while this alarm is active.




Loss YES YES YES YES YES




3BK 21618 AAAA PCZZA Ed.16 597 / 778



specificProblems LIU-SHELF [100] FIRMWARE-INCOMPATIBILITY [9]

eventType Equipment





Impact on System Two cases:1) No scenario is ongoing for specific MUXIf the related SBL is IT/FIT and the version check messageis received,the related SBL will be changed to FIT.2) There is scenario ongoing for specific MUX. Typically, MUX startupscenario.If version check message is received, no state change for related SBL.Typically, the state is from MSD/MSA to MSD/MSA.


Loss No No No No No



598 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems LIU-SHELF [100] FIRMWARE-NOT-UP-TO-DATE [19]

eventType Equipment



Alarm Description When the board is started, an automatic check of the NE1oE firmwareversion is performed. This alarm is reported to OMC-R if it is not thesupported version.


Impact on System The ALARM shows that the current NE1oE FW version running onMUX boards does not fit with the up-to-date NE1oE FW version. TheSBL of impacted MUX is set to FIT. There is no other system impact.


Loss NO NO NO NO NO




Alarmsolved

yes

Alarm persists?

no



3BK 21618 AAAA PCZZA Ed.16 599 / 778


32.9 [100,20] LIU_SHELF_PEM_OWN_VBAT_LOSS

specificProblems LIU-SHELF [100] LIU_SHELF_PEM_OWN_VBAT_LOSS [20]

eventType Equipment



Alarm Description The 48 V redundancy from target PEM of E1 shelf has been lost. Thefunctional status is not impacted.




Loss No No No No No



[100, 20] LIU_SHELF_PEM_OWN

_VBAT_LOSS

Alarm cleared? Alarmsolved


no

yes

Check that 48 V redundancy

between the two PEMs of E1 shelf

is connected

On−site

600 / 778 3BK 21618 AAAA PCZZA Ed.16


32.10 [100,21] LIU_SHELF_RED_VBAT_LOSS

specificProblems LIU-SHELF [100] LIU_SHELF_RED_VBAT_LOSS [21]

eventType Equipment



Alarm Description The 48 V redundancy from Other PEM of E1 shelf has been lost. Thefunctional status is not impacted.




Loss No No No No No



[100, 21] LIU_SHELF _RED_VBAT_LOSS

Alarm cleared? Alarmsolved


no

yes

Check that 48 V redundancy

between the two PEMs of E1 shelf

is connected

On−site

3BK 21618 AAAA PCZZA Ed.16 601 / 778


32.11 [100,22] PEM_OWN_12V_FAILURE

specificProblems LIU-SHELF [100] PEM_OWN_12V_FAILURE [22]

eventType Equipment



Alarm Description A failure of the 12VDC output of on Power Entry Module in the LIUshelf has been detected.


Impact on System The impacted SBL state is set to FLT.There is no other system impact: Power supply redundancy is assuredby the other LIU PEM.


Loss No No No No No



Alarmsolved

yes

Alarm persists?

no


On−site

Replace PEM

[100, 22] PEM_OWN_12V_FAIL

602 / 778 3BK 21618 AAAA PCZZA Ed.16


32.12 [100,23] TOO_HIGH_TEMPERATURE

specificProblems LIU-SHELF [100] TOO_HIGH_TEMPERATURE [23]

eventType Equipment



Alarm Description A too high temperature has been detected on the LIU PEM.

If the internal temperature in the LIU PEM exceeds 80 degrees celcius,this alarm is raised.As such there is no operational impact on the LIU PEM. The PEM isnot shutdown, there is no autonomous defense.However, the LIU shelf should be checked because further temperatureincrease could damage the FRU


Impact on System The impacted SBL state is set to FIT.

There is no other system impact: power is handled by the other PEM.In case a PEM failure would occur, power supply redundancy isassured by the other LIU PEM.


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 603 / 778



Alarmsolved

yes

Alarm persists?

no


On−site

If alarm is not present the other PEM too, replace

faulty PEM

yes

Fix environmental problems

Environmental conditions are ok?

Alarm persists?

Alarmsolved

no

yes

no

[100, 23] TOO_HIGH_TEMP

604 / 778 3BK 21618 AAAA PCZZA Ed.16


32.13 [100,24] PEM_NOT_RESPONDING

specificProblems LIU-SHELF [100] PEM_NOT_RESPONDING [24]

eventType Equipment



Alarm Description The LIU PEM is not responding to O&M queries. Status is unknown.

O&M of the LIU PEM is done by the active MUX board through an I2Cbus.There is no response of the LIU PEM to queries by the active MUXboard.

This problem could be due to a communication failure on the internalI2C bus (hardware failure) or the LIU PEM could be removed.If both LIU PEM boards are in fault (PEM_NOT_RESPONDING) thenthere is likely a hardware problem on the I2C interface of the activeMUX board.If the fault is only reported on one PEM board, then the problem islocated on that board.



There is no other system impact. In case of a fatal PEM failure or PEMremoval, power supply redundancy is assured by the other LIU PEM.


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 605 / 778



Alarmsolved

yes

Alarm persists?

no


On−site

Replace faulty PEM

yes


Alarm persists?

Alarmsolved

no

yes

no

[100, 24] PEM_NOT_RESPOND

Both LIU PEM show the

PEM_NOT_RESPOND alarm?

Trigger MUX takeover

Alarm persists?

Replace standby MUX

yes

yesno

no

606 / 778 3BK 21618 AAAA PCZZA Ed.16


32.14 [100,50] NE1OE-FAILURE

specificProblems LIU-SHELF [100] NE1OE-FAILURE [50]

eventType Equipment



Alarm Description MUX board cannot start due to problems in the INIT sequence andis powered off.


Impact on System The impacted SBL state is changed from IT to FLT.

When this problem is detected, the BSC triggers a MUX reset anda MUX takeover. System impacts are due to the MUX reset (seeLIU-SHELF [100], RESET [0]).


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 607 / 778



[100, 50] NE1OE FAILURE

Alarmsolved

yes

Alarm persists?

no


On−site

Replace MUX

Solve SSW alarmsSSW alarms present?Alarm

persists?

Ethernet cable between ATCA shelf and

LIU shelf is ok?

Replace Ethernet cable

Alarm persists?

Alarmsolved

no

no

no

no

yes

yes yes

yes

608 / 778 3BK 21618 AAAA PCZZA Ed.16


32.15 [100,51] E1-SL-FAILURE

specificProblems LIU-SHELF [100] E1-SL-FAILURE [51]

eventType Equipment



Alarm Description The 16E1 serial link between the MUX and this LIU board has failed.This failure concerns only one of the MUX, so it is not the LIU boardfailure.


Impact on System The impacted SBL state is not changed. When this problem isdetected, the BSC triggers a MUX reset and a MUX takeover.

There is no system impact: the traffic uses the other E1 serial linkbetween the MUX and the LIU board.


Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 609 / 778



[100, 51] E1 SL FAILURE

Alarmsolved

yes

Alarm persists?

no


On−site

Replace MUX

Replace LIU board

Alarm persists?

On−site

Alarmsolved

no

yes

610 / 778 3BK 21618 AAAA PCZZA Ed.16

33 Class 101: BSC-TRANS Alarms


This section defines the BSC alarms for the Class 101: BSC-TRANS alarmclass.

3BK 21618 AAAA PCZZA Ed.16 611 / 778


33.1 [101,0] LIS

specificProblems BSC-TRANS [101] LIS [0]




Alarm Description Loss of Incoming Signal (LIS) is detected on a given E1 link.



For ABIS-HWAY-TP, the link between the BSC and all BTS of theAbis is lost. It is no more possible to have telecom traffic or O&Msupervision with these BTS.For ATER-HWAY-TP, the link between the BSC and the MFS or theTC is lost. On going telecom traffic using this ATER-HWAY-TP isstopped. New traffic and signaling will be established by using theother ATER-HWAY-TP.


Loss Yes (if Ater) Yes (if Abis) Yes (if Abis) Yes (if Abis) Yes (if Abis)

Degradation No No Yes (if Ater) Yes (if Ater) No

612 / 778 3BK 21618 AAAA PCZZA Ed.16



[101, 0] LIS

Alarmsolved

yes

Alarm persists?

no


Loop back BSC originated E1 link at

BSC site.

Solve these alarms

Related TP, MUX

or LIU alarms are present?

Alarm persists?

Related BTS/TC alarms are present?

Solve these alarms Alarm persists?

Alarmsolved

no

yes

yes

yes

yes

no

no

no

SBL in fault?Inhibit / allow alarm

reportingAlarm

persists?

no

yesyes

no

Check related SBL (N7, OML, RSL,

GSL, MLPPP)

Loop back originated E1 link at BTS / TC

site

Alarm persists?

No BSS problem; Check E1 link with

line provider

Check BTS / TC local cabling

Local cabling ok?Alarm

persists?Solve cabling

problem

yes yes

yes

no

no

no

3BK 21618 AAAA PCZZA Ed.16 613 / 778


33.2 [101,1] AIS

specificProblems BSC-TRANS [101] AIS [1]


probableCause Ais


Alarm Description Alarm Indication Signal (AIS) is detected on a given E1 link.In addition to the above G2BSC case, a new case in MX is : AIS ENDalarm is used to clear all active alarms in BSC AIFL when E1 alarmdisappears on this E1 link, this AIS END alarm will be converted intoevent alarm which is reproted to OMC.







614 / 778 3BK 21618 AAAA PCZZA Ed.16



[101, 1] AIS

Alarmsolved

yes

Alarm persists?

no



BSC site.

Solve these alarms

Related TP, MUX


Alarm persists?



Alarmsolved

no

yes

yes

yes

yes

no

no

no


reportingAlarm

persists?

no

yesyes

no

Check related SBL (N7, OML, RSL, GSL, MLPPP)


site

Alarm persists?


line provider




problem

yes yes

yes

no

no

no

3BK 21618 AAAA PCZZA Ed.16 615 / 778


33.3 [101,2] LFA

specificProblems BSC-TRANS [101] LFA [2]




Alarm Description Loss of Frame Alignment (LFA) is detected on a given E1 link.







616 / 778 3BK 21618 AAAA PCZZA Ed.16



[101, 2] LFA

Alarmsolved

yes

Alarm persists?

no



BSC site.

Solve these alarms

Related TP, MUX


Alarm persists?



Alarmsolved

no

yes

yes

yes

yes

no

no

no


reportingAlarm

persists?

no

yesyes

no


GSL, MLPPP)


site

Alarm persists?


line provider




problem

yes yes

yes

no

no

no

3BK 21618 AAAA PCZZA Ed.16 617 / 778


33.4 [101,4] BER-10E-3

specificProblems BSC-TRANS [101] BER-10E-3 [4]




Alarm Description Bit Error Rate of 10E-3 (BER 10-3) is detected on a given E1 link.







618 / 778 3BK 21618 AAAA PCZZA Ed.16



[101, 4] BER 10E−3

Alarmsolved

yes

Alarm persists?

no



BSC site.

Solve these alarms

Related TP, MUX


Alarm persists?



Alarmsolved

no

yes

yes

yes

yes

no

no

no


reportingAlarm

persists?

no

yesyes

no


GSL, MLPPP)


site

Alarm persists?


line provider




problem

yes yes

yes

no

no

no

3BK 21618 AAAA PCZZA Ed.16 619 / 778


33.5 [101,5] RAI

specificProblems BSC-TRANS [101] RAI [5]


probableCause FarEndReceiverFailure


Alarm Description Remote Alarm Indication (RAI) is detected on a given E1 link.







620 / 778 3BK 21618 AAAA PCZZA Ed.16



[101, 5] RAI

Alarmsolved

yes

Alarm persists?

no



BSC site.

Solve these alarms

Related TP, MUX


Alarm persists?



Alarmsolved

no

yes

yes

yes

yes

no

no

no


reportingAlarm

persists?

no

yesyes

no



site

Alarm persists?


line provider




problem

yes yes

yes

no

no

no

3BK 21618 AAAA PCZZA Ed.16 621 / 778


33.6 [101,6] BER-10E-4







Impact on System There is a small degradation of the speech and packet quality and fewframe repetitions on Telecom or O&M signaling links.


Loss No No No No No


622 / 778 3BK 21618 AAAA PCZZA Ed.16



[101, 6] BER 10E−4

Alarmsolved

yes

Alarm persists?

no



BSC site.

Solve these alarms

Related TP, MUX


Alarm persists?



Alarmsolved

no

yes

yes

yes

yes

no

no

no


reportingAlarm

persists?

no

yesyes

no


GSL, MLPPP)


site

Alarm persists?


line provider




problem

yes yes

yes

no

no

no

3BK 21618 AAAA PCZZA Ed.16 623 / 778


33.7 [101,7] BER-10E-6







Impact on System There is a small degradation of the speech and packet quality and fewframe repetitions on Telecom or O&M signaling links.


Loss No No No No No


624 / 778 3BK 21618 AAAA PCZZA Ed.16



[101, 7] BER 10E−6

Alarmsolved

yes

Alarm persists?

no



BSC site.

Solve these alarms

Related TP, MUX


Alarm persists?



Alarmsolved

no

yes

yes

yes

yes

no

no

no


reportingAlarm

persists?

no

yesyes

no


GSL, MLPPP)


site

Alarm persists?


line provider




problem

yes yes

yes

no

no

no

3BK 21618 AAAA PCZZA Ed.16 625 / 778


33.8 [101,8] FRAME-SLIP

specificProblems BSC-TRANS [101] FRAME-SLIP [8]




Alarm Description This event is notified when the BSC detects at least one E1 (notlocked) with frame slips. E1 is considered with frame slip if the numberof frame slips monitored during the previous 15 minutes exceeds thethreshold SLIP-COUNTER-THRESHOLD.


Impact on System There is a small degradation of the speech quality and few framerepetitions on Telecom or O&M signaling links.


Loss No No No No No


626 / 778 3BK 21618 AAAA PCZZA Ed.16



[101, 8] FRAME SLIP

Alarmsolved

yes

Alarm persists?

no



BSC site.

Solve these alarms

Related TP, MUX


Alarm persists?



Alarmsolved

no

yes

yes

yes

yes

no

no

no


reportingAlarm

persists?

no

yesyes

no



site

Alarm persists?


line provider




problem

yes yes

yes

no

no

no

3BK 21618 AAAA PCZZA Ed.16 627 / 778


33.9 [101,9] PPP-LNK-LOOP

specificProblems BSC-TRANS [101] PPP-LNK-LOOP [9]


probableCause transmitFailure

perceivedSeverity Major (DMA)

Alarm Description Link looped-back





Degradation No No No Yes (if Ater) No

628 / 778 3BK 21618 AAAA PCZZA Ed.16



101, 9] PPP−LINK−LOOP

Alarmsolved

yes

Alarm persists?

no


If TP, MUX or LIU board alarms are present, solve it

Check local cabling

Alarm persists?


test on MSC side

Alarm persists?

no

no

yes

yes

3BK 21618 AAAA PCZZA Ed.16 629 / 778


33.10 [101,10] PPP-NO-HDLC

specificProblems BSC-TRANS [101] PPP-NO-HDLC [10]




Alarm Description No HDLC for PPP link







[101, 10] PPP−NO−HDLC

Alarmsolved

yes


Fix E1 link connection at Abis

or Ater

Alarm persists?

no

Alarm persists?

yes

no

E1 link connection at Abis or Ater

ok?

yes

no

630 / 778 3BK 21618 AAAA PCZZA Ed.16


33.11 [101,11] PPP-NO-LCP-REP

specificProblems BSC-TRANS [101] PPP-NO-LCP-REP [11]




Alarm Description Non receipt of LCP Echo-Reply




Loss No Yes (if Abis) Yes (if Abis) Yes (if Abis) Yes (if Abis)



[101, 11] PPP−NO−LCP−REP

Alarmsolved

yes



or Ater

Alarm persists?

no

Alarm persists?

yes

no


ok?

yes

no

3BK 21618 AAAA PCZZA Ed.16 631 / 778


33.12 [101,12] PPP-CONF-FAIL

specificProblems BSC-TRANS [101] PPP-CONF-FAIL [12]




Alarm Description LCP configuration option negotiation failure







[101, 12] PPP−CONF−FAIL

Alarmsolved

yes



or Ater

Alarm persists?

no

Alarm persists?

yes

no


ok?

yes

no

632 / 778 3BK 21618 AAAA PCZZA Ed.16


33.13 [101,13] PPP-HIGH-ERR

specificProblems BSC-TRANS [101] PPP-HIGH-ERR [13]




Alarm Description This alarm can only happen when IP over E1 is configured and it israised for 3 reasons:- the quality of the PCM is very poor and therefore the ratio of badframes is very high,- the connected equipment (BTS) is not configured as the BSC,- there are cross connects between BSC and BTS.






3BK 21618 AAAA PCZZA Ed.16 633 / 778



[101, 13] PPP−HIGH−ERR

Alarmsolved

yes


Check E1 link connection at Abis or

Ater

Alarm persists?

no

Trigger manually the OML mode, via the

command: reset Abis_Hway_TP of the concerned Abis

Alarm persists?

yes

no

634 / 778 3BK 21618 AAAA PCZZA Ed.16


33.14 [101,14] OML-MODE

specificProblems BSC-TRANS [101] OML-MODE [14]




Alarm Description Indicate the related Abis_Hway_TP is in OML mode.The OML mode is meaningful in the context of an E1 configured withthe IP (framed or unframed) transport mode.The purpose of this mode is to come back to transitional TDM transportmode on this E1, only for the OML exchange and not for traffic,assuming that this TDM configuration is possible for any BTS whateverits Software and its configuration.The OML mode is consecutive to a transmission problem with at leastone BTS in the chain.Normally, the system can automatically come out of the OML mode


Impact on System The concerned BTS are out of service during the OML mode.


Loss no yes no no no


3BK 21618 AAAA PCZZA Ed.16 635 / 778



[101,14] OML−MODE

Check the configuration, version

of BTS

The system automatically

comes out of the OML mode?


no yes

Alarmsolved

Alarm persists?no

yes

636 / 778 3BK 21618 AAAA PCZZA Ed.16


33.15 [101,20] SFP-UNEQ

specificProblems BSC-TRANS [101] SFP-UNEQ [20]




Alarm Description small form-factor pluggable not







[101, 20] SFP−UNEQ

Alarmsolved

yes


Check if the SFP module is correct

installed

Alarm persists?

no

yes

no

BSC equipped with SFP module?

yes

Insert SFP module

Alarm persists?

no

3BK 21618 AAAA PCZZA Ed.16 637 / 778


33.16 [101,21] LOS

specificProblems BSC-TRANS [101] LOS [21]

eventType Equipment

probableCause lossOfSignal


Alarm Description Section Loss of Signal




Loss No Yes IF abis Yes if Abis Yes Yes if Abis


638 / 778 3BK 21618 AAAA PCZZA Ed.16



[101, 21] LOS

Alarmsolved


Alarm persists?

noRemote equipment

ok?

noLink to remote

equipment ok?

Alarm persists?

Fix the link

Fix the remote equipment problems

Alarm persists?

no

no

no

yes

yes

yes

yesyes

3BK 21618 AAAA PCZZA Ed.16 639 / 778


33.17 [101,22] LOF

specificProblems BSC-TRANS [101] LOF [22]

eventType Equipment

probableCause lossOfFrame


Alarm Description Section Loss of Frame






640 / 778 3BK 21618 AAAA PCZZA Ed.16



[101, 22] LOF

Alarmsolved


Alarm persists?

noRemote equipment

ok?

noConfiguration setting

ok?

Alarm persists?

Update configuration setting


Alarm persists?

no

no

no

yes

yes

yes

yesyes

3BK 21618 AAAA PCZZA Ed.16 641 / 778


33.18 [101,23] MS-AIS

specificProblems BSC-TRANS [101] MS-AIS [23]

eventType Equipment

probableCause aIS


Alarm Description Multiplex Section Alarm Indication Signal







[101, 23] MS−AIS

AlarmsolvedContact

System Support

Alarm persists?

noRemote equipment

ok?

no

Alarm persists?


no

yes

yesyes

642 / 778 3BK 21618 AAAA PCZZA Ed.16


33.19 [101,24] MS-RDI

specificProblems BSC-TRANS [101] MS-RDI [24]

eventType Equipment

probableCause remoteNodeTransmissionError


Alarm Description Multiplex Section Remote Defect Indication







[101, 24] MS−RDI

AlarmsolvedContact

System Support

Alarm persists?

noRemote equipment

ok?

no

Alarm persists?


no

yes

yesyes

3BK 21618 AAAA PCZZA Ed.16 643 / 778


33.20 [101,25] MS-BER-6

specificProblems BSC-TRANS [101] MS-BER-6 [25]

eventType Equipment

probableCause degradedSignal


Alarm Description Multiplex Section Bit Error Rate 10-6







[101, 25] MS−BER−6

AlarmsolvedContact

System Support

Alarm persists?

noRemote equipment

ok?

no

Alarm persists?


no

yes

yesyes

644 / 778 3BK 21618 AAAA PCZZA Ed.16


33.21 [101,26] MS-BER-3

specificProblems BSC-TRANS [101] MS-BER-3 [26]

eventType Equipment

probableCause degradedSignal


Alarm Description Multiplex Section Bit Error Rate 10-3






3BK 21618 AAAA PCZZA Ed.16 645 / 778



[101, 26] MS−BER−3

Alarmsolved


Alarm persists?

noRemote equipment

ok?

noLink to remote

equipment ok?

Alarm persists?

Fix the link


Alarm persists?

no

no

no

yes

yes

yes

yesyes

646 / 778 3BK 21618 AAAA PCZZA Ed.16


33.22 [101,28] SFP-NOT-SUP

specificProblems BSC-TRANS [101] SFP-NOT-SUP [28]

eventType Equipment



Alarm Description Small Form-Factor Pluggable not supported


Impact on System No state impact





[101, 28] SFP−NOT−SUP

Alarmsolved

yes


Check if the SFP module is correct

installed

Alarm persists?

no

yes

no

The SFP module is installed?

yes

Insert SFP module

Alarm persists?

no

3BK 21618 AAAA PCZZA Ed.16 647 / 778


33.23 [101,31] AU-LOP

specificProblems BSC-TRANS [101] AU-LOP [31]

eventType Equipment

probableCause lossOfPointer


Alarm Description Administrative Unit 4 Loss of Pointer


Impact on System The impacted SBL is set to FLT




648 / 778 3BK 21618 AAAA PCZZA Ed.16



[101, 31] AU−LOP

Alarmsolved


Alarm persists?

noRemote equipment

ok?


ok?

Alarm persists?



Alarm persists?

no

no

no

yes

yes

yes

yesyes

3BK 21618 AAAA PCZZA Ed.16 649 / 778


33.24 [101,32] AU-AIS

specificProblems BSC-TRANS [101] AU-AIS [32]

eventType Equipment

probableCause aIS


Alarm Description Administrative Unit 4 Alarm Indication Signal


Impact on System The impacted SBL is set to FLT





[101, 32] AU−AIS

AlarmsolvedContact

System Support

Alarm persists?

noRemote equipment

ok?

no

Alarm persists?


no

yes

yesyes

650 / 778 3BK 21618 AAAA PCZZA Ed.16


33.25 [101,41] HP-UNEQ

specificProblems BSC-TRANS [101] HP-UNEQ [41]

eventType Equipment



Alarm Description High Order Path Unequipped: The HOP is not configured on theremote entity


Impact on System The impacted SBL is set to FLT .The STM1 interace is faulty





[101, 41] HP−UNEQ

Alarmsolved


noAlarm persists?

Check the remote STM1 declaration

and correct it if needed.

yes

3BK 21618 AAAA PCZZA Ed.16 651 / 778


33.26 [101,42] HP-PLM

specificProblems BSC-TRANS [101] HP-PLM [42]

eventType Equipment

probableCause payloadTypeMismatch


Alarm Description High Order Path Payload Label Mismatch


Impact on System The impacted SBL is set to FLT .




652 / 778 3BK 21618 AAAA PCZZA Ed.16



[101, 42] HP−PLM

Alarmsolved


Alarm persists?

noRemote equipment

ok?


ok?

Alarm persists?



Alarm persists?

no

no

no

yes

yes

yes

yesyes

3BK 21618 AAAA PCZZA Ed.16 653 / 778


33.27 [101,43] HP-RDI

specificProblems BSC-TRANS [101] HP-RDI [43]

eventType Equipment



Alarm Description High Order Path Remote Defect Indication







[101, 43] HP−RDI

AlarmsolvedContact

System Support

Alarm persists?

noRemote equipment

ok?

no

Alarm persists?


no

yes

yesyes

654 / 778 3BK 21618 AAAA PCZZA Ed.16


33.28 [101,44] HP-LOM

specificProblems BSC-TRANS [101] HP-LOM [44]

eventType Equipment

probableCause lossOfFrame


Alarm Description High Order Path Loss of Multiframe






3BK 21618 AAAA PCZZA Ed.16 655 / 778



[101, 44] HP−LOM

Alarmsolved


Alarm persists?

noRemote equipment

ok?


ok?

Alarm persists?



Alarm persists?

no

no

no

yes

yes

yes

yesyes

656 / 778 3BK 21618 AAAA PCZZA Ed.16


33.29 [101,51] TU-LOP

specificProblems BSC-TRANS [101] TU-LOP [51]

eventType Equipment

probableCause lossOfPointer


Alarm Description Tributary Unit 12 Loss of Pointer




Loss No Yes if Abis Yes if Abis Yes if abis No


3BK 21618 AAAA PCZZA Ed.16 657 / 778



[101, 51] TU−LOP

Alarmsolved


Alarm persists?

noRemote equipment

ok?


ok?

Alarm persists?



Alarm persists?

no

no

no

yes

yes

yes

yesyes

658 / 778 3BK 21618 AAAA PCZZA Ed.16


33.30 [101,52] TU-AIS

specificProblems BSC-TRANS [101] TU-AIS [52]

eventType Equipment

probableCause aIS


Alarm Description Tributary Unit 12 Alarm Indication Signal







[101, 52] TU−AIS

AlarmsolvedContact

System Support

Alarm persists?

noRemote equipment

ok?

no

Alarm persists?


no

yes

yesyes

3BK 21618 AAAA PCZZA Ed.16 659 / 778


33.31 [101,55] LP-UNEQ

specificProblems BSC-TRANS [101] LP-UNEQ [55]

eventType Equipment



Alarm Description Low Path Unequipped






660 / 778 3BK 21618 AAAA PCZZA Ed.16



[101, 55] LP−UNEQ

Alarmsolved


Alarm persists?

noRemote equipment

ok?


ok?

Alarm persists?



Alarm persists?

no

no

no

yes

yes

yes

yesyes

3BK 21618 AAAA PCZZA Ed.16 661 / 778


33.32 [101,56] LP-PLM

specificProblems BSC-TRANS [101] LP-PLM [56]

eventType Equipment

probableCause payloadTypeMismatch


Alarm Description Low Path Payload Label Mismatch






662 / 778 3BK 21618 AAAA PCZZA Ed.16



[101, 56] LP−PLM

Alarmsolved


Alarm persists?

noRemote equipment

ok?


ok?

Alarm persists?



Alarm persists?

no

no

no

yes

yes

yes

yesyes

3BK 21618 AAAA PCZZA Ed.16 663 / 778


33.33 [101,57] LP-RDI

specificProblems BSC-TRANS [101] LP-RDI [57]

eventType Equipment



Alarm Description Low Path Remote Defect Indication







[101, 57] LP−RDI

AlarmsolvedContact

System Support

Alarm persists?

noRemote equipment

ok?

no

Alarm persists?


no

yes

yesyes

664 / 778 3BK 21618 AAAA PCZZA Ed.16


33.34 [101,60] PPP-CROSS-CON

specificProblems BSC-TRANS [101] PPP-CROSS-CON [60]




Alarm Description MLPPP cross connected







[101, 60] PPP−CROSS−CON

AlarmsolvedContact

System Support

Alarm persists?

noPPP connection is

cross−connected?

no

Alarm persists?

Fix the PPPconnection

no

yes

yes

yes

3BK 21618 AAAA PCZZA Ed.16 665 / 778


33.35 [101,61] PPP-LCP-TER

specificProblems BSC-TRANS [101] PPP-LCP-TER [61]




Alarm Description On LCP terminate REQ







[101, 61] PPP−LCP−TER

AlarmsolvedContact

System Support

Alarm persists?

noPPPconfiguration

ok?

no

Alarm persists?

Correct PPP configuration

no

yes

yesyes

666 / 778 3BK 21618 AAAA PCZZA Ed.16


33.36 [101,62] PPP-LOW-ERR

specificProblems BSC-TRANS [101] PPP-LOW-ERR [62]




Alarm Description Low erroneous PPP frame


Impact on System The impacted SBL is set to FIT .


Loss No No No No No



[101, 62] PPP−LOW−ERR

AlarmsolvedContact

System Support

Alarm persists?

noPPPlink

status ok?

no

Alarm persists?

Fix PPP linkno

yes

yesyes

3BK 21618 AAAA PCZZA Ed.16 667 / 778


33.37 [101,63] PPP-MED-ERR

specificProblems BSC-TRANS [101] PPP-MED-ERR [63]




Alarm Description Low erroneous PPP frame




Loss No Yes if Abis Yes if Abis yes No



[101, 63] PPP−MED−ERR

AlarmsolvedContact

System Support

Alarm persists?

noPPPlink

status ok?

no

Alarm persists?

Fix PPP linkno

yes

yesyes

668 / 778 3BK 21618 AAAA PCZZA Ed.16


33.38 [101,100] STM1-TAKEOVER

specificProblems BSC-TRANS [101] STM1-TAKEOVER [100]




Alarm Description This alarm indicates a STM1-TTP takeover


Impact on System No impact


Loss No no No No No



None- No action needed.

3BK 21618 AAAA PCZZA Ed.16 669 / 778


670 / 778 3BK 21618 AAAA PCZZA Ed.16

34 Class 104: TC-OM Alarms


This section defines the BSC alarms for the Class 104: TC-OM alarm class.

3BK 21618 AAAA PCZZA Ed.16 671 / 778


34.1 [104,0] TC-INIT-FAIL

specificProblems TC-OM [104] TC-INIT-FAIL [0]



perceivedSeverity –

Alarm Description TC initialization is unsucc: maybe TC-HW-Audit, or TC-conf-req orTC-Alarm audit failed.




Loss Yes No Yes Yes Yes



[104, 0] TC−INIT−FAIL

Alarmsolved

yes

Alarm persists?

no


If TC−OM is FOS, init TC−OM from TC NEM or OMC−R

672 / 778 3BK 21618 AAAA PCZZA Ed.16


34.2 [104,1] TC-INIT-SUCC

specificProblems TC-OM [104] TC-INIT-SUCC [1]


probableCause congestion/network fail

perceivedSeverity –

Alarm Description TC initialization is succ.




Loss No No No No No



None. The TC initialization is successful.

3BK 21618 AAAA PCZZA Ed.16 673 / 778


674 / 778 3BK 21618 AAAA PCZZA Ed.16

35 Class 105: TRANSCODER Alarms


This section defines the BSC alarms for the Class 105: TRANSCODER alarmclass.

3BK 21618 AAAA PCZZA Ed.16 675 / 778


35.1 [105,0] POWER-SUPPLY

specificProblems TRANSCODER [105] POWER-SUPPLY [0]

eventType Equipment



Alarm Description One of both MT120 power supply is in fault


G2 TC and 9125 TC



Loss No No No No No



[105, 0] POWER−SUPPLY

Alarmsolved

yes

Alarm persists?

no


Check MT120 Power Supply

676 / 778 3BK 21618 AAAA PCZZA Ed.16



specificProblems TRANSCODER [105] EQUIPMENT-FAULT [128]

eventType Equipment





G2 TC and 9125 TC



Loss Yes (ifTRAU-CP=FLT)

No Yes (ifTRAU-CP =FLT)

Yes (ifTRAU-CP =FLT)

No

Degradation Yes (ifTRAU-CP =FIT)

No Yes (ifTRAU-CP =FIT)

Yes (ifTRAU-CP =FIT )

No

3BK 21618 AAAA PCZZA Ed.16 677 / 778




Reset corresponding MT120 board.

Alarmsolved

yes

Alarm persists?

no


Replace corresponding MT120 board.

yes

Alarm persists?

no

G2 TC or 9125 TC?

Replace corresponding MT120 board.

G2 TC 9125 TC

678 / 778 3BK 21618 AAAA PCZZA Ed.16


35.3 [105,130] DSP LOSS

specificProblems TRANSCODER [105] DSP LOSS [130]




Alarm Description For MT120: more than one DSP has failed and the impact is only theloss of a number of channels, that is only trunk degradation. Signallingis not lost neither.




Loss No No No No No

Degradation Yes(forMT120)

No No No No

3BK 21618 AAAA PCZZA Ed.16 679 / 778



[105,130] DSP−LOSS



Alarmsolved

Alarm persists?

no

yes


alarm events?

no

yes

On−site

Replace BIU


Alarmsolved

yes

Alarm persists?

no


Reset MT120

Replace MT120

Alarm persists?

Alarm persists?


no

no

yesOn−site

G2 TC 9125 TC

Replace MT120

680 / 778 3BK 21618 AAAA PCZZA Ed.16


35.4 [105,136] FIRST-DSP-FAIL

specificProblems TRANSCODER [105] FIRST-DSP-FAIL [136]

eventType Equipment



Alarm Description One out of the twelve DSPs of a MT120 has failed. All channels ofthis DSP are fully recovered and are now handled by the other elevenDSPs. If no further DSPs have failed (e.g. MEMORY-FAULT) thenthis MT120 is still able to handle all resources (up to 120 channels),but it works in a degraded mode, as it cannot recover any additionalDSP failure.




Loss No No No No No


3BK 21618 AAAA PCZZA Ed.16 681 / 778



[105,136] FIRST−DSP−FAIL


Alarmsolved

Alarm persists?

no

yes

Replace MT120

Alarmsolved

yes

Alarm persists?

no

Reset MT120

G2 TC or 9125 TC?

Replace MT120

G2 TC 9125 TC

682 / 778 3BK 21618 AAAA PCZZA Ed.16


35.5 [105,148] RESET

specificProblems TRANSCODER [105] RESET [148]




Alarm Description An autonomous load of the TC MT120 occurred. The module hasundergone serious service interruption, but has recovered.Thereset_buffer is checked to see if the board leaves the reset mode. Afterstartup, hardware tests on memory and interfaces are performed, andthe process jumps to the software entry point. This cannot happenas this module has only firmware.


Impact on System Some calls may be lost


Loss No No No No No



None - this alarm reports the autonomous load of the BTS_ADAPT only.

3BK 21618 AAAA PCZZA Ed.16 683 / 778


35.6 [105,210] TRANS-FLT

specificProblems TRANSCODER [105] TRANS-FLT [210]




Alarm Description The PCM event counter threshold value is exceeded on one ATERinterface, which results in the generation of this 2 Mbit/s alarm. Foreach PCM event, a counter is increased. At certain intervals, thecounter will be decreased by 1. When the threshold value is exceeded,this alarm is generated for that 2 Mbit/s interface.


G2 TC and 9125 TC



Loss No No No No No


684 / 778 3BK 21618 AAAA PCZZA Ed.16



[105,210] ATER−TRANS−FLT


Solve that alarm(s)


PCM/ATER alarm events?

no

yes

Repair/replace Ater interface

Other Ater alarm

events?

no

yes

On−site

Alarm persists?

noyes

Alarmsolved

Alarm persists?

no

yes

Ater interface

operational?

no yes

Solve that alarm(s)Ater

interface alarm events?

no

yes

Local Ater cabling

OK?

no

yes


3BK 21618 AAAA PCZZA Ed.16 685 / 778


35.7 [105,211] LOSS-OF-CLK-2M

specificProblems TRANSCODER [105] LOSS-OF-CLK-2M [211]

eventType Equipment



Alarm Description The 2 MHz clock source is lost. Once the PAD detects the loss of the2MHz clock source, the next clock source will be selected if available.The firmware will detect the missing clock source number.


G2 TC and 9125 TC





686 / 778 3BK 21618 AAAA PCZZA Ed.16


35.8 [105,216] RESTART

specificProblems TRANSCODER [105] RESTART [216]




Alarm Description n autonomous processor restart has occurred. The operating systemand all processes are re-initialized sequentially. A new initializationof the dynamic data takes place.




Loss No No No No No



None. This alarm reports an autonomous restart.

3BK 21618 AAAA PCZZA Ed.16 687 / 778


35.9 [105,238] ACTIVE-HSI-FAIL

specificProblems TRANSCODER [105] ACTIVE-HSI-FAIL [238]

eventType Equipment



Alarm Description HSI with active TCIF failed, or HSI with both active and standby TCIFfailed. No telecom function.


G2 TC and 9125 TC





688 / 778 3BK 21618 AAAA PCZZA Ed.16



[105,238] ACTIVE−HSI−FAIL

Restart TCIF and MT120 boards


Alarm persists?no

yes

Alarmsolved

Alarm persists?

no

yes

Check the HSI cable.If both link failed

replace the corresponding cable

3BK 21618 AAAA PCZZA Ed.16 689 / 778


35.10 [105,239] REDUNDANT-HSI-FAIL

specificProblems TRANSCODER [105] REDUNDANT-HSI-FAIL [239]

eventType Equipment



Alarm Description HSI with standby TCIF failed. No impact on O&M or Telecom. Riskfor telecom loss if TCIF takeover.


G2 TC and 9125 TC



Loss No No No No No


690 / 778 3BK 21618 AAAA PCZZA Ed.16



[105,239] REDUNDANT−HSI−FAIL

Restart TCIF and MT120 boards


Alarm persists?no

yes

Alarmsolved

Alarm persists?

no

yes

Check the HSI cable.

3BK 21618 AAAA PCZZA Ed.16 691 / 778


692 / 778 3BK 21618 AAAA PCZZA Ed.16

36 BSC/TC Alarm Additional Information


This section describes the additional information supplied by some BSC/TCalarms.

3BK 21618 AAAA PCZZA Ed.16 693 / 778


36.1 Restart and Software Anomaly AlarmsThis section describes the additional information provided by the followingRestart alarm [33,0] and BSC Software Anomaly alarms [39,1], [39,3], [39,4],[39,5], [39,6], [39,7].

The Restart and Software Anomaly alarm byte definitions are shown in thefollowing table.

ByteNumber Description

0 - 1 Interface Address.

This specifies the connection of the processor to the internal switch of the BSC:

Byte 0: On-Board Controller Interface identity

Byte 1: Network address, enabling identification of the SBL links from the processor to

the internal switch.

2 This specifies the Logical Control Element-Identification. The SBL type specifies theprocessor type. There is no longer a direct relationship between LCE-ID and CE number.

3 Always 0.

4 - 5 Finite Message Machine (FMM) -ID, this identifies the task/process. It is the instructionpointer of the fault. Example: ’1E’ hex = SCCP ’1F’; hex = N7 SLH (N7 Signaling linkhandler).

6 - 7 Instruction Pointer of the processor address where the fault happened. The first byte isthe LSB.

8 - 9 Code Segment of the processor address where the fault happened. The first byte is the LSB.

10 - 11 Error type, see Table 7. The first byte is the LSB.

12 Sequence number. This is used to distinguish between similar error types.

13 Not relevant.

14 - 15 User Data 0. User data providing additional information.




Table 5: Additional Information for Restart and Software Anomaly Alarms

694 / 778 3BK 21618 AAAA PCZZA Ed.16


36.1.1 Finite Message Machine

The Finite Message Machine - Identity (FMM-ID) in Bytes 4 and 5 is defined inthe following table.

Dec Hex FMM-ID Meaning

1 01 ME-INIT-TCU Initialize TCU (ME = Management Entity).

2 02 ME-INIT-DTC Initialize DTC.

3 03 ME-INIT-CPR Initialize CPR.

4 04 ME-TWIN-FILE Twin file.

5 05 ME-REMOTE-SSD-ITF Remote Solid State Disk interface.

6 06 ME-ALARM-TCU-DTC TCU/DTC alarm.

7 07 ME-REMOTE-FILE Remote file.

8 08 ME-ALARM-CPR CPR alarm.

9 09 ME-MAINT-TCU-DTC TCU/ DTC maintenance.

10 0A DBASE-AUDIT-HLDCHCK Database audit handler check.

11 0B ME-MAINTENANCE-CPR CPR maintenance.

14 0E ME-HSK-1 ME housekeeping.

15 0F TCU-TRF-LDC TCU traffic local data collector.

16 10 DTC-TRF-LDC DTC traffic local data collector.

17 11 ME-MEASUREMENTS-CPR CPR measurement.

18 12 ME-BTS-TCU BTS O&M; TCU.

19 13 ME-BTS-CPR BTS O&M; CPR.

20 14 ME-REMOTE-LOADER Remote loader.

21 15 ME-LOADER Loader.

22 16 DH-DTC-TCU DTC/TCU.

23 17 LME-NETW-MAINT-MSTR Network maintenance master.

24 18 RF-MGT-L3 RF management.

25 19 BSC-LAPD-L2 BSC LAPD.

26 1A ME-COPY-FILE Copy file.

27 1B LME-NETW-ROUTINES Network routines.

3BK 21618 AAAA PCZZA Ed.16 695 / 778



28 1C LME-NETW-MAINT Network maintenance.

29 1D BSSAP BSS Application Part.

30 1E SCCP Signaling Connection Control Part.

31 1F M7-SLH Signaling link handler for N7.

32 20 CALL-CONTROL-ACT Active CPR call control.

33 21 LME-M7-DTC Link maintenance entity for N7.

34 22 ME-TCSM TCSM.

35 23 ME-MMC MMC.

36 24 ME-DISK-HDLR Disk handler.

38 26 TCH-RM TCH resource manager.

39 27 LE-L3-L2-X.25 Link entity for L3, L# X.25.

40 28 LME-X.25 Link maintenance entity for X.25.

41 29 SLNM Signaling link network manager (N7).

42 2A SM Signaling manager (N7).

43 2B ME-DBASE-TEST-FMM Database test FMM.

44 2C L4E-TRANSPORT Transport.

45 2D L5E-SESSION Session.

46 2E L6E-PRESENTATION Presentation.

47 2F L7E-OSMAE OSMAE.

48 30 L7E-OSMAP OSMAP.

49 31 L7E-FTAM FTAM.

50 32 DTC-N-7-LDC DTC N7 local data collector.

51 33 ME-TRACE-DEBUG-MSTR Trace/debug master.

52 34 CALL-CONTROL-TCU TCU call control.

53 35 ME-EMPTY Empty.

54 36 BSC-HEART-BEAT-CTL BSC heartbeat control.

55 37 TRADEB-SLAVE-F Trace/debug slave.

56 38 ME-EMPTY-SLAVE Empty slave.

696 / 778 3BK 21618 AAAA PCZZA Ed.16



57 39 RATA-TCU Read and Throw Away TCU (test only).

58 3A REMOTE-REQUEST-HDLR Remote request handler.

59 3B REPL-REL-SYNC Replaced Relation Sync.

60 3C BACK-UP-DATA-HDLR Backup data handler.

61 3D ME-SECURITY-FILE Security file.

62 3E ROLL-BACK-HDLR Rollback handler.

63 3F RATA-DTC Read and Throw Away DTC (test only).

64 40 RATA-CPR Read and Throw Away CPR (test only).

66 42 CPR-N-7-LDC CPR N7 local data collector.

67 43 ME-BSC-SW-REPLACE BSC software replacement.

68 44 TONE-DTMF-DH-FMM DTMF tone device handler.

69 45 CALL-CONTROL-DTC DTC call control.

70 46 ME-SUBSCR-ADMIN-CPR Subscriber administration CPR.

73 49 OBCI-NH-TEST-FMM On-board controller network handler test.

74 4A ME-HSK-2 ME housekeeping.

75 4B ME-HSK-3 ME housekeeping.

76 4C RATA-CPR-OSI Read and Throw Away CPR (test only).

77 4D ME-MMC-TCU MMC TCU.

78 4E ME-INIT-CPR-OSI Initialize OSI-CPR.

79 4F ME-ALARM-CPR-OSI OSI-CPR alarm.

80 50 ME-MAINT-CPR-OSI OSI-CPR maintenance.

81 51 CPR-TRF-LDC CPR traffic local data collector.

82 52 RMH-MSG-HANDLER Remote message handler.

83 53 RECOVERY-ME Recovery.

84 54 DH-CPR CPR device handler.

85 55 TELECOM-SUPERV-MOD Telecom supervision module.

86 56 ASN-ABIS ASN Abis.

87 57 ASN1-CONV ASN1 converter.

3BK 21618 AAAA PCZZA Ed.16 697 / 778



88 58 ME-LOCAL-MAINT-CPR CPR local maintenance.

89 59 ME-LOCAL-ALARM-CPR CPR local alarm.

90 5A ME-HSK-LOCAL Local ME housekeeping.

91 5B ME-HSK-4 Housekeeping 4

92 5C LOC-OVRL-CTL Local overload control.

93 5D TRACE-COORDINATOR Trace Coordinator.

94 5E TRACE-ADMINISTRATOR Trace Administrator.

95 5F TCU-BTS-LDC BTS local data collector for TCU.

96 60 ME-MEAS-ADMIN Measurement administrator.

97 61 ME-MEAS-RECOVERY Measurement of recovery.

98 62 ME-HSK-5 ME housekeeping.

99 63 ME-MEAS-CENTRAL-COLL Central measurement collector.

100 64 RECOV-SL-ME Recovery of Signaling links.



103 67 ME-MAINT-DTC DTC maintenance.

104 68 ME-MAINT-TCU TCU maintenance.

105 69 ME-EMPTY-1386 Empty FMM for 1386.

106 6A ME-EMPTY-SLAVE-1386 Empty FMM for slave 1386.

107 6B BSC-SCSI-CONTROL Housekeeping.

108 6C RTS-MANAGER RTS Manager.

109 6D RTS-RECONFIGURE Reconfigure RTS.

110 6E OMU-SIMULATOR OMU simulator.

111 6F FU-SIMULATOR FU simulator.

112 70 MSC-SIMULATOR MSC simulator.

113 71 SMS-CB-MASTER SMS-CB master.

114 72 SMS-CB-LOCAL SMS-CB local.

115 73 DH-DTC DTC device handler.

698 / 778 3BK 21618 AAAA PCZZA Ed.16



116 74 DH-TCU TCU device handler.

117 75 TCSM-ME-CPR TCS on the CPR.

118 76 TCSM-ME-TCU TSC on the TCU.

119 77 USAGE-STATE-MASTER Usage State on Demand master.

120 78 USAGE-STATE-SLAVE Usage State on Demand slave.

121 79 M7-TEST-FMM N7 test.

122 7A TRX-MANAGER TRX manager on the CPR.

123 7B TRX-REMAPPER TRX remapper on the CPR.

124 7C ME-FMM-INIT Initialize FMM.

125 7D FMM-SPARE-0 Spare FMM.

126 7E FMM-SPARE-1 Spare FMM.

127 7F FMM-SPARE-2 Spare FMM.

128 80 FMM-SPARE-3 Spare FMM.





133 85 SCCP-SCMG Signaling Connection Control Part managementprocedure for the S -CPR.

134 86 FMM-SCM-TEST SCM test module.

135 87 ME-DISK-HDLR-386 Disk handler for the 386 processor.

136 88 ME-BCLA-HANDLER BCLA handler on the scanning DTCS.

137 89 RATA-CPR-OSI Receive and Throw Away (test module).

138 8A TRACE-LDC Trace on local data collectors.

139 8B ALERTOR-MASTER Master Alertor (not used).

140 8C ALERTOR-SLAVE Slave Alertor (not used).

141 8D BSC-HEARTBEAT-G2 Heartbeat on the Evolium 9120 BSC.

142 8E ME-LOCAL-ALARM Local alarm handler.

3BK 21618 AAAA PCZZA Ed.16 699 / 778



143 8F ME-EXT-RED Extension/reduction handler.

144 90 TCH-RM-LDC TCH-RM local data collector.

145 91 RATA-ABS3-AY Receive and Throw Away (test module).

146 92 RATA-ATR4-AY Receive and Throw Away (test module).

147 93 RATA-SYS4-AY Receive and Throw Away (test module).

148 94 RATA-OSI3-AY Receive and Throw Away (test module).

149 95 RATA-BCC1-AY Receive and Throw Away (test module).

150 96 RATA-TCU Receive and Throw Away (test module).

151 97 RATA-DTC Receive and Throw Away (test module).

152 98 RATA-CPR Receive and Throw Away (test module).

153 99 RATA-CPR-OSI Receive and Throw Away (test module).

154 9A RATA-SYS-AY Receive and Throw Away (test module).

155 9B RATA-OSIS-AY Receive and Throw Away (test module).

156 9C MEAS-COORDINATOR Message coordinator on the O-CPR.

157 9D CC-DATA-COLLECTOR Cumulative collector.

158 9E CC-RESULT-HANDLER Cumulative result collector.

159 9F DER-RESULTS-HANDLER Discrete Event Register result handler.

160 A0 CENTRAL-ALERTOR Central Alertor on the O-CPR.

161 A1 C_ALERTOR Alertor (not used).

162 A2 ME-MAINT-MSTER-TEST Master maintenance test module.

163 A3 LME-OFF-LINE-TEST Off-line test module.

164 A4 RATA_ABS3_AD Receive and Throw Away (test module).

165 A5 RATA_ATR4_AD Receive and Throw Away (test module).

166 A6 RATA_SYS4_AD Receive and Throw Away (test module).

167 A7 RATA_OSI3_AD Receive and Throw Away (test module).

168 A8 RATA_BBC1_AD Receive and Throw Away (test module).

169 A9 ME_ASN1_CONV2 ASN1 Convertor module 2.

170 AA ME_BROADCAST_MGT Broadcast bus maintenance module.

700 / 778 3BK 21618 AAAA PCZZA Ed.16



171 AB L4_CONVERGENCE Convergence function for SMSCB.

172 AC RATA_ABS1_AE Receive and Throw Away (test module).

173 AD RATA_ATR1_AE Receive and Throw Away (test module).

174 AE RATA_SYS1_AE Receive and Throw Away (test module).

175 AF RATA_OSI1_AE Receive and Throw Away (test module).

176 B0 RATA_ABS3_AE Receive and Throw Away (test module).

177 B1 RATA_ATR4_AE Receive and Throw Away (test module).

178 B2 RATA_SYS4_AE Receive and Throw Away (test module).

179 B3 RATA_OSI3_AE Receive and Throw Away (test module).

180 B4 RATA_BBC1_AE Receive and Throw Away (test module).

181 B5 ME_CLK_MAINT_MSTR Clock maintenance module.

182 B6 ME_BC_MAINT_MSTR Broadcast bus maintenance module.

183 B7 ME_ALARM_CORRELATOR Alarm correlator module.

184 B8 RATA_ABS1_AH Receive and Throw Away (test module).

185 B9 RATA_ATR1_AH Receive and Throw Away (test module).

186 BA RATA_SYS1_AH Receive and Throw Away (test module).

187 BB RATA_OSI1_AH Receive and Throw Away (test module).

188 BC RATA_ABS3_AH Receive and Throw Away (test module).

189 BD RATA_ATR4_AH Receive and Throw Away (test module).

190 BE RATA_SYS4_AH Receive and Throw Away (test module).

191 BF RATA_OSI3_AH Receive and Throw Away (test module).

192 C0 RATA_BBC1_AH Receive and Throw Away (test module).

194 C2 CF_INTERPRETER Command file interpreter.

195 C3 FMM_INIT_G2 FMM init module for Evolium 9120 BSC.

196 C4 ME_PRELOADER_G2 Loader module for Evolium 9120 BSC.

197 C5 ME_SYSTEM_NIT System init module.

198 C6 ME_PRELOADER PreLoader module.

3BK 21618 AAAA PCZZA Ed.16 701 / 778



199 C7 GPRSAP_FMM GPRS module (similar to BSSAP for Telecom).Responsible for the handling of commands fromthe MFS except O&M; and paging messages.

200 C8 RATA_ABS1_AP Receive and Throw Away (test module).

201 C9 RATA_ATR1_AP Receive and Throw Away (test module).

202 CA RATA_SYS1_AP Receive and Throw Away (test module).

203 CB RATA_OSI1_AP Receive and Throw Away (test module).

204 CC RATA_ABS3_AP Receive and Throw Away (test module).

205 CD RATA_ATR4_AP Receive and Throw Away (test module).

206 CE RATA_SYS4_AP Receive and Throw Away (test module).

207 CF RATA_OSI3_AP Receive and Throw Away (test module).

208 D0 RATA_BBC1_AP Receive and Throw Away (test module).

209 D1 ME_BTS_EXT_RED BTS Extension reduction module.

210 D2 FM_TRANS FM module for transmission.

212 D4 HSK_LOC_DTC Load housekeeping on the DTC.

213 D5 HSK_LOC_TCU Load housekeeping on the TCU.

214 D6 L3_DIS Module responsible for the GPRS signaling linkbetween the MFS and the BSC.

215 D7 DTC_LAPD_L2_FMM LAPD Layer 2 module on the DTC.

216 D8 RF_GPRS_FMM GPRS module (similar to RFMGT for telecom).Responsible for relaying commands from/toRFMGT on the TCU and allocation call bufferson the TCU side.

217 D9 CONF_TRANS_CPR Configuration transmission module on the CPR.

218 DA CONF_TRANS_LOCAL Configuration transmission module on the TCUs.

219 DB TSM_GPRS GPRS module (similar to TSM in telecom).Responsible for central data for the GPRS.Located on the S_CPR pair.

220 DC RATA_ABS3_AQ Receive and Throw Away (test module).

221 DD RATA_ATR4_AQ Receive and Throw Away (test module).

222 DE RATA_SYS4_AQ Receive and Throw Away (test module).

223 DF RATA_OSI3_AQ Receive and Throw Away (test module).

702 / 778 3BK 21618 AAAA PCZZA Ed.16



224 E0 RATA_BBC1_AQ Receive and Throw Away (test module).

225 E1 PAGING Paging module, responsible for the handling ofpaging messages located on the GPRSAP’sDTCs.

232 E2 FM_TRANS_CORR FM module for transmission.

233 E3 OSND_TEST OSN_D test module.

234 E4 ME_HSK_7 Housekeeping module 7.

235 E5 TSC_MMI TSC Man Mahine Interface module.

241 F1 RATA_ABS3_AT Receive and Throw Away (test module).

242 F2 RATA_ATR4_AT Receive and Throw Away (test module).

243 F3 RATA_SYS4_AT Receive and Throw Away (test module).

244 F4 RATA_OSI3_AT Receive and Throw Away (test module).

245 F5 RATA_BBC1_AT Receive and Throw Away (test module).

246 F6 CENTRAL_RMS Radio Measurement Stat.

247 F7 TCU_RMS_LDC Radio Measurement Stat on each TCU.

248 F8 ABIS_RM ABIS Resource Manager module.

249 F9 COCO Connection control.

250 FA RFM_CCCH RFM CCCH Handler.

251 FB GOM GPRS O&M; module, responsible for the O&M;between the MFS and the BSC.

252 FC ME_ABIS_HCM_SCHED Hardware Configuration Management actionscheduler

253 FD ME_ABIS_PORT_HDLR Hardware Configuration Management Abishandler.

254 FE HCM_BTS_DATA_HDLR Hardware Configuration Management BTS datahandler.

255 FF HCM_TRAF_RES_HDLR Hardware Configuration Management trafficresource handler.

256 100 HCM_SIGN_RES_HDLR Hardware Configuration Management signalingresource handler.

257 101 HCM_MCB_MAPPER Hardware Configuration Management multiplexingcontrol block.

3BK 21618 AAAA PCZZA Ed.16 703 / 778



258 102 ME_HSK_ABIS HSK ABIS module.

259 103 CF_INTERPRETER_2 Command file interpreter module 2.

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

36.1.2 Error Types

The Error Types in Bytes 10 and 11 are defined in the following table.

Type(Dec) Type (Hex) Error Name

0 00 DUMMY

1 01 SYSTEM_RESTART

2 02 SYSTEM_REBOOT

3 03 SYSTEM_RELOAD

4 04 TRADEB_ERROR_CALL

5 05 ME_INIT_GLOB_INIT

6 06 ME_INIT_TAKE_OVER

7 07 ME_INIT_TIME OUT

8 08 L1_TRUNK_FAILURE

9 09 DBASE_ACC_FAILURE

10 0A NO_TRUNK_CELLS

11 0B ILC_INIT_FAILURE

12 0C ILC_DMA_UNDERRUN

13 0D ILC_DMA_OVERRUN

14 0E OBCI_HW_FLT

15 0F OBCI_SW_FLT

16 10 SSD_ACCESS_FAIL

17 11 DATABASE_ERROR

18 12 DATABASE_DATA_INC

19 13 INC_MESS_DATA

704 / 778 3BK 21618 AAAA PCZZA Ed.16



20 14 ICLP_FAILURE

21 15 BS_CH_RLS_FAIL

22 16 CH_CONF_ERROR

23 17 MEAS_TYPE_ERROR

24 18 NO_LOCAL_REFERENCE_AVAILABLE

25 19 WRONG_TMS_TYPE

26 1A MASTER_FILE_CORRUPTED

27 1B MASTER_FILE_DISK_ERROR

28 1C ILC_DE_QUEUE_TWICE

29 1D ILC_EN_QUEUE_TWICE

30 1E ILC_NO_FR_CELL

31 1F BOOTSTRAP_ERR

32 20 NMI

33 21 UNEXPECTED_INT

34 22 INT_DATA_INC

35 23 MTF_RSL_SMALL

36 24 PR_DISABLE

37 25 PR_RESTART

38 26 OPEN_FILE_FLT

39 27 READ_REC_FLT

40 28 CLOSE_FILE_FLT

41 29 FCB_LOC_TO_OMU

42 2A WRONG_TCB_FIG

43 2B ERR_LOAD_REQ

44 2C ERR_ACK_NACK

45 2D OUT_OF_STATE

46 2E INTL_CATASTR

3BK 21618 AAAA PCZZA Ed.16 705 / 778



47 2F SPC_ALARM

48 30 INTL_DATA_FLT

49 31 GSM_0808_MSG_UNKNOWN

50 32 GSM_0808_MSG_UNEXPEC

51 33 GSM_0808_IEI_UNEXPEC

52 34 GSM_0808_IE_FORM-ERR

53 35 GSM_0808_IE_SEM_ERR

54 36 GSM_0408_MSG_UNKNOWN

55 37 GSM_0408_MSG_UNEXPECTED

56 38 GSM_0408_PRTDISC_ERROR

57 39 GSM_0408_IE_FORM_ERROR

58 3A GSM_0408_IE_SEM_ERROR

59 3B INTERNAL_MESSAGE_UNKNOWN

60 3C INTERNAL_MESSAGE_UNEXPECTED

61 3D TCHRM_NO_ANSWER

62 3E TCHRM_RF_NO_ANSWER

63 3F TRADEB_LBS

65 41 CANCEL_EXPIRED_TIMER

66 42 TOO_MANY_RESTARTS

67 43 STAND_ALONE

68 44 OBCI_LINK_HW_FAULT

69 45 NETWORK_CONFIGURATIOM

70 46 OBCI_LINK_OS

71 47 INPUT_MAINT

72 48 MAINT_SEQUENCE

73 49 XMEM_FAULT

74 50 XMCK_FAULT

706 / 778 3BK 21618 AAAA PCZZA Ed.16



77 4D GSM_0858_MS_UNEXPECTED

78 4E GSM_0808_CIC_UNKNOWN

79 4F CONF_CH_DISREP

80 50 ERROR_REPORT_FROM_BTS

81 51 RF_CHANNEL_RELEASE_FAILURE

82 52 ASN1_DECODE_FAILURE

83 53 ASN1_ENCODE_FAILURE

84 54 SW_REPLACEMENT_DATA_ERROR

85 55 INCORRECT_FILE_CONTENT

86 56 UPDATE_SW_SYSREC_FAILURE

87 57 READ_SW_SYSREC_FAILURE

88 58 MAX_SMAP_RETRIES

89 59 HEARTBEAT_ERROR

90 5A HEARTBEAT_RESET

91 5B NO_RESET_CIC_ACK

92 5C DIVIDE_ERROR

93 5D INV_TSS

94 5E STA_EXC

95 5F CIPHERING_DATA_INCONSISTENT

96 60 UNKNOWN_CIRC_RECEIVED

97 61 UNKNOWN_CIRC_TRANSMIT

98 62 INVALID_ACCESS_TYPE

99 63 EXPANSION_FAILED

100 64 OBCI_RESET

101 65 NO_MORE_DESCRIPTORS

102 66 INVALID_DESCRIPTOR_TYPE

103 67 INVALID_SELECTOR

3BK 21618 AAAA PCZZA Ed.16 707 / 778



104 68 LOG_LIN_CONV_ERR

187 BB INVALID_OPCODE

188 BC DOUBLE_FAULT

189 BD SEGMENT_NOT_PRESENT

191 BF GEN_PROT

192 C0 PAGE_FAULT

679 2A7 C2_OVERFLOW

680 2A8 C2_NULL_PTR

681 2A9 PRCSS_END

682 2AA C2_RANGEFAIL

683 2AB C2_RTS

1055 41F NO_SUPVISION_PROCESS_CONTROL_BLOCK

1056 420 NO_APPLICATION_PROCESS_CONTROL_BLOCK

1057 421 PROCESS_CONTROL_BLOCK_OV1

1058 422 PROCESS_CONTROL_BLOCK_OV2

1059 423 DE_Q_TWICE

1060 424 NO_SUPV_STACK

1061 425 NO_TCB

1062 426 NO_MAIL LINK

1063 427 EN_Q_TWICE

1064 428 NO_APPLICATION_STACK

1065 429 INVALID_JOB_TYPE

1066 42A NO_TIMER_ML

1067 42B INVALID_MREQ_SIZE

1068 42C NO_UMEM_BLOCK

1069 42D NO_MESSAGE_BUFFER

1070 42E INVALID_MESSAGE_TYPE

708 / 778 3BK 21618 AAAA PCZZA Ed.16



1071 42F INVALID_FMM_ID

1072 430 INVALID_MESSAGE_PRIORITY

1073 431 INVALID_OSINF_TYPE

1074 432 INVALID_SCFI

1075 433 CFGI_NOT_SET

1076 434 SANITY_TIME OUT

1077 435 ILLEGAL_CALL

1078 436 STACK_CHECK

1079 437 INVALID_CLOCK_VALUE

1097 449 INVALID_MESSAGE_BASIC_TO_DESTINATION

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

3BK 21618 AAAA PCZZA Ed.16 709 / 778


36.2 Reset and Software Anomaly AlarmsThis section describes the additional information provided by the followingReset alarm [33,1] and Software Anomaly alarms [33,4], [33,5], [39,18].

The Reset and Software Anomaly alarm byte definitions are shown in thefollowing table.

ByteNumber Description

0 - 1 IAD.

This specifies the connection of the processor to the internal switch of the BSC:

Byte 0: OBCI identity

Byte 1: Network address, enabling identification of the SBL links from the processor tothe internal switch.

2 This specifies the LCE-ID. The SBL type specifies the processor type. There is no longer adirect relationship between LCE-ID and CE number.

3 Always 0.

4 - 5 Not relevant.

6 - 7 IP of the processor address where the fault happened. The first byte is the LSB.

8 - 9 CS of the processor address where the fault happened. The first byte is the LSB.

10 - 11 Not relevant.

12 - 13 Not relevant.





Table 8: Additional Information for Reset and Software Anomaly Alarms

710 / 778 3BK 21618 AAAA PCZZA Ed.16


36.3 System Support MachineThis subsection describes the System Support Machine (SSM) MessageIdentification.

DEC NO HEX NO MEANING

65535 FFFF This value simply indicates that the error occurs in an SSM.

Table 9: System Support Machine

36.4 Other BSC AlarmsThis section describes the additional information provided by other BSC alarms.

36.4.1 [33,3]

The additional information bytes for this alarm are defined in the following table.

Byte Number (Intel notation - 1st byte is Least Significant Byte (LSB)) Meaning

Format 1: 0 and 1

2

3

4

FF

CE identity

0

FF

Format 2: See BSC/TC Alarm Additional Information (Section 36).

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

36.4.2 [34,0] to [34,2] and [34,4] to [34,6]

The additional information byte for these alarms is defined in the following table.

Byte Number Meaning

0 Switch port number on which the alarm was generated.

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

3BK 21618 AAAA PCZZA Ed.16 711 / 778


36.4.3 [34,3]

The additional information bytes for this alarm are defined in Tables 12 to15, below.

Test Results ExplanationByteNumber Meaning Test Not Executed Test Executed

0 Test-segment Value 0 assigned Test segment failure. See Table 13.

1 Test-flt-type - Test fault type. See Table 14.

2 Test-raw-data (0) Link NetworkAddress

-

3 Test-raw-data (1) Value 255 assigned Switch Network Address.

4 Test-raw-data (2) - Link Type.

5 Test-raw-data (3) - Port Number.

6 Test-raw-data (4) - Test Result of TDM connection between port0 and the port given in Raw Data (3). SeeTable 15.









712 / 778 3BK 21618 AAAA PCZZA Ed.16




16 Test-raw-data (14) - Test Result of TDM connection between portA and the port given in Raw Data (3). SeeTable 15.



17 Test-raw-data (15) - Test Result of TDM connection between portB and the port given in Raw Data (3). SeeTable 15.

18 Test-raw-data (16) - Test Result of TDM connection between portC and the port given in Raw Data (3). SeeTable 15.

19 Test-raw-data (17) - Test Result of TDM connection between portD and the port given in Raw Data (3). SeeTable 15.

20 Test-raw-data (18) - Test Result of TDM connection between portE and the port given in Raw Data (3). SeeTable 15.

21 Test-raw-data (19) - Test Result of TDM connection between portF and the port given in Raw Data (3). SeeTable 15.

TestSegment Description

1 Get channel, send a request of MAINTENANCE_PACKET to find a free channel. Waitfor EOP_SENT or NACK.

Send a request of tunnel word for maintenance interrogate CH0, test if it is accepted,wait for message.

Only for diagnostic test, before starting test, it needs to send ’mask a CH0 alarm’ to modifymask, send maintenance interrupt and maintenance command to change status of ports.

3BK 21618 AAAA PCZZA Ed.16 713 / 778


TestSegment Description

2 Send a request of tunnel word for maintenance command CH0, with set maintenancebusy and alarm shutoff, test if it is accepted.

Send a request of tunnel word for maintenance interrogate CH0, test if it is accepted andwait for message.

3 Get channel, send a request of MAINTENANCE_PACKET with maintenance select onport under test.

4 Send a request of tunnel word for maintenance command CH0 with reset alarm shutoff.Test if it is accepted.


5 Send a request of MAINTENANCE_PACKET with normal select on port under test. Waitfor NACK.

6 Send a request of tunnel word for maintenance command CH0 with reset maintenancebusy. Test if it is accepted.


8 Send a packet with seven interrogates. Verify that the pointer correctly decremented.

9 Send packet of escape words. The transmitted and received packet are compared.

10 Set a path, send a packet of escape words. The transmitted and received packet iscompared.

11 Re-select path. Wait for NACK.

12 Send maintenance packet with maintenance select on port under test.

Wait for NACK and write violation alarm.

13 Send packet of escape words. The transmitted and received packets are compared (TDMbus).

14 Set up permanent path via test depth, towards own OBCI, with test pattern attached.

15 Try to set up a temporary path towards the permanent path. This should be rejected.

16 Try to set up a temporary path towards the permanent path, using maintenance selects.The AS bit is 0, so an alarm should be generated.

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

714 / 778 3BK 21618 AAAA PCZZA Ed.16


Fault Type Description

0 No errors.

1 Not accepted tunnel word interrogate.

2 timeout tunnel word interrogate.

3 Not accepted tunnel word command.

4 Received tunnel alarm.

5 Message out of sequence.

6 No channel available.


8 All channels NACKed, maintenance packet not sent.

9 timeout for msg 158.

10 Wrong pointer received.

11 Timeout for msg 157.





16 No channel available.

17 Timeout no event msg received.

18 Timeout for msg second path.

19 Timeout for msg first path.





24 No NACK received but 2 EOP.

25 Timeout no NACK received.



3BK 21618 AAAA PCZZA Ed.16 715 / 778





30 Wrong pointer decrement after EOP.

31 Wrong pointer decremented before EOP.


33 Wrong pkt received before EOP.

34 Wrong pkt received after EOP.


36 All channels NACKed, maintenance pkt not sent.

37 Wrong pkt received after EOP.

38 Wrong pkt received before EOP.



41 Timeout for all msg.

42 Timeout for msg 151 and msg second path.

43 Timeout for msg 151 and msg first path.


45 Timeout for msg first path and second.

46 Timeout for msg second path.

47 Timeout for msg first path.

48 Timeout wrong sequence message.

49 Values incompatible with Z_TUNNEL_type, Z_TEST_PORT.B_side andZ_TEST_PORT.B_depth.

50 Wrong sequence message

51 Result of Maintenance Interrogate:

ACI=0 - all channels idle

MB=0 - maintenance busy

AS=0 - alarm shutoff.

52 ACI=0 MB=0 AS=1

716 / 778 3BK 21618 AAAA PCZZA Ed.16



53 ACI=0 MB=1 AS=0

54 ACI=0 MB=1 AS=1

55 ACI=1 MB=0 AS=0

56 ACI=1 MB=0 AS=1

57 ACI=1 MB=1 AS=0

58 ACI=1 MB=1 AS=1

59 TDM test bus fail, resource seize fail.

60 TDM bus fail.

61 Overall timer has expired.

62 Overall timer has expired.

63 Cable test has failed.

64 Wrong PTR decremented after EOP.

65 Wrong PTR decremented after EOP.


67 Plug Test Error.

68 DCDC State Change.

69 Send tunnel word not accepted.

70 Timeout msg for msg 157.

71 Processor does not control BCLA.

72 BCLA: wrong ID.

73 BCLA: this is not the rack BCLA.

74 BCLA: this is not the sys BCLA.

75 BCLA: the write register has failed.

76 BCU pattern test has failed.

3BK 21618 AAAA PCZZA Ed.16 717 / 778



77 BCU fail bit set.

78 No system test allowed according an R_xx.

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

Nibble Test Result Explanation

High 0

1

Connection not tested.

Connection tested.

Low 0

1

2

3

Test OK.

Bad test packet and no EOPS received.

Bad test packet and EOPS received.

Timeout.

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

36.4.4 [34,7]


Byte Number Meaning Test Results Explanation

Not applicable Test Successful. Test unsuccessful.

0 Test-raw-data (0)

1 Test-raw-data (1)

Number of times a routine test has run.

2 Test-raw-data (2)

3 Test-raw-data (3)

Number of tunnels.

4 Test-raw-data (4)

5 Test-raw-data (5)

Number of tested tunnels.

6 Test-raw-data (6)

7 Test-raw-data (7)

Number of successful tunnels.

8 Test-raw-data (8)

9 Test-raw-data (9)

Value 255 assigned.

Number of unsuccessful tunnels.


718 / 778 3BK 21618 AAAA PCZZA Ed.16


36.4.5 [35,0]


Byte Number Meaning (Intel notation - 1st byte is LSB)

0 Origin of the problem. 00H No message.

01H Stop CMD from level 3.

02H T1 timeout (Align ready).

03H SIO received during align ready.

04H SIOS received during align ready.

05H T2 timeout (Not aligned).

06H T3 timeout (Aligned).

07H SIOS received during aligned.

08H Align Error Rate Threshold (AERM) reached.

09H LSSU received while in service.

0AH Abnormal FIB received.

0BH Abnormal BSN received.

0CH Signal unit error rate threshold reached (SUERM).

0DH T7 timeout (Acknowledge).

0EH T6 timeout (Congestion).

0FH Abnormal hardware condition Tx.

10H Abnormal hardware condition Rx.

FFH Suppress.

1 Present link traffic state. 80H In traffic.

40H Traffic before unavailable.

10H Remote blocked.

00H Not in traffic.


3BK 21618 AAAA PCZZA Ed.16 719 / 778


36.4.6 [35,2]

The additional information bytes for this alarm are defined as shown below.

Byte Number Meaning (Intel Notation - 1st byte is LSB)

0 and 1 DPC of the MSC (same as the alarm number).

2 and 3 SSF of the MSC.


36.4.7 [35,3]

There are two possible layouts for the INC-REP Alarm.

Alarm layout 1 occurs every hour to prevent an overload situation on the BSC.The additional information bytes for alarm layout 1 are defined in Table 19.

Alarm layout 2 occurs on every alarm event. The additional information bytesfor alarm layout 2 are defined in Table 20.

Table 21 shows an example of additional information for Alarm [35,3].

Word Number Meaning (Intel Notation - 1st byte is LSB)

0 Value = 0: Invalid SSF received.

Value = 1: Invalid DPC received.

Value = 2:

Invalid OPC received or

Status Indicator (SI) =0: Signaling Network Management Message and Signaling

Link Code (SLC) not existing or

SI=1: Signaling Network Testing and Maintenance Message (SNTM) and SLCdifferent from one SLC.

1 100H*SLC + SSF received.

(SLC is described in section 15.2 of ITU-T Rec. Q704).

(SSF is described in section 14.2.2 of ITU-T Rec. Q704).

2 SI received.

(SI is described in section 14.2.1 of ITU-T Rec. Q704).

3 MSG_TYPE HO/H1 received.

(SI=0 is described in section 15 of ITU-T Rec. Q704).

(SI=1 is described in section 5 of ITU-T Rec. Q707).

4 DPC received.

(DPC is described in section 15.2 of ITU-T Rec. Q704).

720 / 778 3BK 21618 AAAA PCZZA Ed.16



5 OPC received.

(OPC is described in section 15.2 of ITU-T Rec. Q704).

6 SSF received.

(SSF is described in section 14.2 of ITU-T Rec. Q704).

7 DPC expected (Value fromDLS).

8 OPC expected (Value from DLS).

9 SSF expected (Value from DLS).

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


0 Value = 10: Changeback refused (described in ITU-T Rec. Q704).

2 - 18 Value = FF

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

Data Word Value Meaning

02 00 0 0002H invalid OPC or

0c 0c 1 0C0CH SLC= 0CH SSF= 0CH

01 00 2 0001H SI= SNTM

11 00 3 0011H MSG Type = SLTM*

31 02 4 0231H DPC received

0a 02 5 020AH OPC received

0c 00 6 000CH SSF received

31 02 7 0231H DPC expected

0a 02 8 020AH OPC expected

0c 00 9 000CH SSF expected

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

* SLTM = Signaling Link Test Message

3BK 21618 AAAA PCZZA Ed.16 721 / 778


36.4.8 Result of Example

Fact: Received values correspond to expected values and SI = 1.

Conclusion: SLC is different from own SLC (SLC received is 0CH).

Reaction: Check in DLS for relation of R_N7_CONF. In example SLC definitionfor N7-7 is 04H.

Final result: SLC definitions for N7-7 are different between MSC and BSC.

36.4.9 [35,4]

The additional information bytes for this alarm are defined in the table below.

Byte Number Meaning (Intel Notation - 1st byte is LSB)

0 Logical Control Element identity where link resides.

1 DTN identity where link resides.

2 to 9 Null value.


36.4.10 [36,14]

The additional information byte for this alarm is defined in below.

Byte Number Meaning

0 0: own clock; source of alarm.

1: mate clock; source of alarm.


36.4.11 [36,15]

The additional information byte for this alarm is defined below.

Byte Number Meaning

0 0: PLL out of range.

1: clock failure.


722 / 778 3BK 21618 AAAA PCZZA Ed.16


36.4.12 [38,0]

The additional information byte for this alarm is defined in below.

Byte Number Meaning

0 Display of the modem signals.


36.4.13 [38,2]

The additional information bytes for this alarm are defined below.

Byte Number Meaning

0 Identification of the link where the problem occurred.

1 and 2 Identification of the channel where the problem occurred.

3 and 4 Description of the problem.


36.4.14 [42,3]

The additional information byte for this alarm is defined below.

Byte Number Meaning

0 Cause of the reset procedure:

00: reset from MSC.

01: MSC communication lost or internal reason.

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

3BK 21618 AAAA PCZZA Ed.16 723 / 778


36.4.15 [42,5]


Byte Number Meaning

Alarm cause:

0 BSC reload/reboot

1 CPRA reload/reboot

2 BSC restart

3 CPRA restart

4 CPRA takeover

5 MSC unavailable

6 Reset from MSC

7 Overload from MSC

8 Timer T6 expired

9 Timer T6 expired

10 MSC available

11 Timer T2 expired

12 Overload from BTS

13 TCUA overload

14 DTC overload

15 Sign link congestion.

Timer T6 indicates an MSC originated end of an overload period, the system returnsto normal.

0

Timer T2 indicates a BTS originated end of an overload period, the system returns tonormal.

1 - 2 LAC. #FF if not defined.

3 - 4 Cell Id. #FF if not defined.

: : :

: : For N (40) cells

: : :

724 / 778 3BK 21618 AAAA PCZZA Ed.16


Byte Number Meaning

4N-3 to 4N-2 LAC. #FF if not defined.

4N-1 to 4N Cell Id. #FF if not defined.


36.4.16 [42,6]


Byte Number Meaning

Alarm cause:

0 BSC reload/reboot


2 BSC restart

3 CPRA restart

4 CPRA takeover

5 MSC unavailable

6 Reset from MSC

7 Overload from MSC

8 Timer T6 expired

9 Timer T6 expired

10 MSC available

11 Timer T2 expired


13 TCUA overload

14 DTC overload

15 Sign link congestion.

Timer T6 indicates an MSC-originated end of an overload period, the system returnsto normal.

0

Timer T2 indicates a BTS-originated end of an overload period, the system returnsto normal.

1 - 2 LAC. #FF if not defined.

3BK 21618 AAAA PCZZA Ed.16 725 / 778


Byte Number Meaning

3 - 4 Cell Id. #FF if not defined.

5 - 6 Current RACH.

This information gives the reason a message was sent and the new access classvalues. The RACH parameter is specified using 16 bits. The right hand bit correspondsto Access class 0.

Value 10 for an Access class specifies emergency calls only.

Value 0 for an Access class specifies that calls are authorized.

7 - 8 Starting RACH.




: : :

: : For N (40) cells

: : :

8N-7 to 8N-6 LAC. #FF if not defined.

8N-5 to 8N-4 Cell Id. #FF if not defined.

8N-3 to 8N-2 Current RACH.




8N-1 to 8N Starting RACH.





726 / 778 3BK 21618 AAAA PCZZA Ed.16


36.4.17 [42,9]


Byte Number Meaning

0 SBL unit type

1 SBL unit number

2-3 SBL type

4 SBL number

5 SBL sub-number

6-13 Overload level buffer pool 1-8

00 = No Overload

01 = SCCP Overload

02 = Overload Level 1

03 = Overload Level 2

14 Processor occupancy (%)


36.4.18 [42,12]


Byte Number Meaning

0 - 1 LAC of cell

2 - 3 CI of cell

: : For N number of cells lost (60 maximum)

4N-4 to 4N-3 LAC of cell

4N-2 to 4N-1 CI of cell


3BK 21618 AAAA PCZZA Ed.16 727 / 778


36.4.19 [42,13]


Byte Number Meaning

Alarm cause:

0 BSC reload/reboot


2 BSC restart

3 CPRA restart

4 CPRA takeover

5 MSC unavailable

6 Reset from MSC

7 Overload from MSC

8 Timer T18 expired

9 MSC available

10 End of reset procedure

11 Not applicable

12 Not applicable

13 Not applicable

14 DTC overload

15 CPR overload

16 Signaling link congestion

17 Not applicable

18 Overload parameter modify

19 Cumulative counter null

0

Timer T18 indicates a BSC-originated end of an overload period, the system returnsto normal.

728 / 778 3BK 21618 AAAA PCZZA Ed.16


Byte Number Meaning

1 - 2 This information gives the reason a message was sent, and the new access classvalues on System Level GSM TS 04.08.

The RACH parameter is specified using 16 bits. The right hand bit corresponds toAccess class 0.

Bit 0..9, 11..15 = 0 for an Access class means that Access control class is not barredon System Level.

Bit 10 = 0 means emergency calls are allowed on System Level to all MSs.

Bit 10 = 1 means emergency calls are not allowed on System Level except for MSs thatbelong to one of the classes between 11..15.

Byte 1 contains Bits 15 - 08

Byte 2 contains Bits 07 - 00

Byte 3 = Cell Bar Access

Byte 4 = Cell Bar Qualifier on System Level GSM TS 04.08 and 05.08.

Cell Bar Quality Cell Bar Access Cell SelectionPriority

Status for CellReselection

0 0 Normal Normal

0 1 Barred Barred

1 0 Low Normal

3 - 4

1 1 Low Normal


36.4.20 [43,0] to [43,3]

The additional information bytes for these alarms are defined below.

Byte Number Meaning

0 - 1 Number of available BCCH.

2 - 3 Number of available SDCCH.

4 - 5 Number of available TCH.

6 TRX identity.

7 Current TEI (RSLNumber)

#FF if no RSL is mapped.

8 BEQ–Number

9 Baseband State: 0 = Not available

1 = Available

3BK 21618 AAAA PCZZA Ed.16 729 / 778


Byte Number Meaning

10 Radio Part State: 0 = Not available

1 = Available

: : :

: : For N configured TRXs (Maximum 8).

: : :

5N + 1 TRX identity. -

5N + 2 Current TEI (RSLnumber)

#FF if no RSL is mapped.

5N + 3 BEQ number. -

5N + 4 Baseband State: 0 = Not available

1 = Available

5N + 5 Radio Part State: 0 = Not available

1 = Available

5N + 6 Separator #FF

5N + 7 Separator #FF

5N + 8 CU number. -

5N + 9 BEQ number. -

5N + 10 to 5N +11

ARFCN used. -

5N + 12 ARFCN available. -

: : :

: : For N configured TRXs (Maximum 8).

: : -

9N + 6 CU number.

9N + 7 BEQ number.

9N + 8 to 9N + 9 ARFCN used.

9N + 10 ARFCN available.

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

730 / 778 3BK 21618 AAAA PCZZA Ed.16


36.4.21 [43,4]


Byte Number Meaning

Alarm cause:

0 BSC reload/reboot


2 BSC restart

3 CPRA restart

4 CPRA takeover

5 Not applicable

6 Not applicable

7 Not applicable

8 Not applicable

9 Not applicable

10 Not applicable

11 Timer T2 expired


13 TCUA overload

14 Not applicable

15 Not applicable

16 Not applicable

17 Bar/unbar cell request

18 Overload parameter modify

19 TCC null

0

Timer T2 indicates a BSC-originated end of an overload period, the system returnsto normal.

3BK 21618 AAAA PCZZA Ed.16 731 / 778


Byte Number Meaning

1 - 2 This information gives the reason a message was sent, and the new access classvalues on Cell Level (Dynamic RACH) GSM TS 04.08.

The RACH parameter is specified using 16 bits. The right hand bit corresponds toAccess class 0.

Bit 0..9, 11..15 = 0 for an Access class means that Access control class is not barredon Cell Level.

Bit 10 = 0 means emergency calls are allowed in the cell to all MSs.

Bit 10 = 1 means emergency calls are not allowed in the cell except for MSs that belongto one of the classes between 11..15.

Byte 1 contains Bits 15 - 08.

Byte 2 contains Bits 07 - 00.

3 - 4 Byte 3 = Cell Bar Access

Byte 4 = Cell Bar Qualifier on System Level GSM TS 04.08 and 05.08.

- Cell Bar Quality Cell Bar Access Cell SelectionPriority

Status for CellReselection

- 0 0 Normal Normal

- 0 1 Barred Barred

- 1 0 Low Normal

- 1 1 Low Normal


36.4.22 [44,0], [44,5] and [44,6]


Byte Number Meaning

0 + 1 Abis Error Code.

2 + 3 Error Number (that is, Record Number).

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

732 / 778 3BK 21618 AAAA PCZZA Ed.16


36.4.23 [44,3]


Byte Number Meaning

0 + 1 Abis Error Code.

2 + 3 File Number.

4 + 5 Error Number (that is, Record Number).


36.4.24 [46,0], [46,1] and [46,3]


Byte Number Meaning

0 + 1 Twin File number.

2 + 3 Twin file PCS of the twin file in alarm.

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

36.4.25 [47,9]


Byte Number 0+ 1 Meaning

0 CBC Outgoing Connection association prematurely terminated internally.

1 CBC O/G association prematurely terminated externally.

2 Network connection refused.

3 Network connection timeout.

4 BIND parameters not populated.

5 CBC O/G association setup timeout.

6 CBC O/G association refused - not entitled.

7 CBC O/G association refused - invalid Id or password.


3BK 21618 AAAA PCZZA Ed.16 733 / 778


36.4.26 [49,0]


Byte Number Meaning

0 + 1 LAC of Cell.

2 + 3 CI of Cell.

4 + 5 Threshold Value 1.



36.4.27 [49,1]

The additional information bytes for this alarm are defined as shown below.

Byte Number Meaning

0 + 1 LAC of Cell.

2 + 3 CI of Cell.



8 + 9 SBL type (DTC).

10 + 11 SBL number (DTC number).


734 / 778 3BK 21618 AAAA PCZZA Ed.16


36.4.28 [49,2] and [49,3]

The additional information bytes for these alarms are defined as follows.

Byte Number Meaning

0 + 1 LAC of Cell.

2 + 3 CI of Cell.



8 + 9 SBL type (DTC).

10 + 11 SBL number (DTC number).

12 + 13 Transceiver identity.

14 + 15 Time slot number.

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

36.4.29 [51,0]

The additional information bytes for this alarm are defined in the table below.

Byte Number Meaning

0 - 1 Network address.

2 Bits 3-0: Switch port number (values 0-15) on which the alarm was generated.

Bits 7-4: Reason for alarm.

0= An unsynchronized write access occurred within a switch element internal hardwarelogic. This caused a mismatch generating a transient write violation alarm.

1= Loss of synchronization with the internal 4 Mbit/s signal. A transient ’loss-of-sync’alarm has been generated.


3BK 21618 AAAA PCZZA Ed.16 735 / 778


36.4.30 [51,1]

The additional information bytes for this alarm are defined in Tables 43, 44,45 and 46.

The blocks of additional information must be considered together in order toanalyze the alarm information correctly.

1. The first block of additional information indicates the network address ofswitch, the link states and, if required, the necessary fault reason.

2. The subsequent blocks of additional information indicate the test results ofthe link. For every failed test, a block of additional data is filled in.

The relationship between the Interface Address (IAD) / Network Address(NA) (Hex) and the RIT is given in Table 49 for BSC racks 1, 2 and 3. Thetable contains the relationships for all completely equipped racks and theRIT position in the rack, shelf and slot.

ByteNumber Meaning

0 - 1 NetworkAddress.

Bits 3-0: Faulttype

0= No Reason.

1= Write Violation. Several unsynchronized write accesses occurredwithin a switch element’s internal hardware logic. This caused amismatch, generating a transient write violation alarm.

2= Write Violation Overflow. Several unsynchronized write accessesoccurred within a switch element’s internal hardware logic. This causeda mismatch, generating a write violation overflow alarm.

3= Loss of Sync. The switch detected a loss of synchronization with theinternal 4 Mbit/s signal. All calls through the switch are lost. An alarm issent for the switch indicating a permanent loss of synchronization.

4= Loss of Sync Overflow. The switch detected a large number oftransient losses of synchronization with the internal 4 Mbit/s signalwithin a specified time frame.

5= HW Fault. Hardware failure detected.

6= Init-Ini-Fail. A link initialization failed during an initialization actionon a switch SBL.

7= Operator Request. An operator request has failed.

2 - 17

Bits 7-4: Linkstate

0= In Service1= Out of service2= Autonomous out of service3= Undefined4= Faulty In Service5= Alarm shutoff6= Not equipped link

18 - 19 Not used. (#FF) -

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

There are 16 ports. Byte 2 represents Port 0, Byte 3 represents Port 1, andso on.

736 / 778 3BK 21618 AAAA PCZZA Ed.16


If additional blocks of information are displayed, each one indicates the resultsof a failed link test. Refer to the table below.

Byte Number Meaning Descriptions

0 Test Segment See Test-Segment Table 13.

1 Test-Fault-type See Test-Fault-Type Table 14.

2 - 3 Link-Network-Address -

4 - 19 TDM-Test-Results See Table 45 for TDM Test Result Byte descriptions.

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

If Test Segment and Test-Fault-Type are both at 0, the test did not executeor a timeout was received. In this case, the TDM-Test-Results values willbe set to #FF.

Byte Number Test Results Explanation

4 Test Result of TDM connection between port 0 and the port given by the Link NetworkAddress. See Table 46 for detailed TDM test results.










14 Test Result of TDM connection between port A and the port given by the Link NetworkAddress. See Table 46 for detailed TDM test results.

15 Test Result of TDM connection between port B and the port given by the Link NetworkAddress. See Table 46 for detailed TDM test results.

3BK 21618 AAAA PCZZA Ed.16 737 / 778


Byte Number Test Results Explanation

16 Test Result of TDM connection between port C and the port given by the Link NetworkAddress. See Table 46 for detailed TDM test results.

17 Test Result of TDM connection between port D and the port given by the Link NetworkAddress. See Table 46 for detailed TDM test results.

18 Test Result of TDM connection between port E and the port given by the Link NetworkAddress. See Table 46 for detailed TDM test results.

19 Test Result of TDM connection between port F and the port given by the Link NetworkAddress. See Table 46 for detailed TDM test results.

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

Nibble Test Result Explanation

High 0

1

Connection not tested.

Connection tested.

Low 0

1

2

3

Test OK.

Bad test packet and no EOPS received.

Bad test packet and EOPS received.

Timeout.

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

The TDM is the internal multiplex bus of the switch. The TDM test makes a sortof loop between the port under test and all the equipped ports of the switch.

For example:

If port 2 is under test, a loop will be made between

port 2 -> port 0

port 2 -> port 1

...

port 2 -> port F.

The relationship between the Interface Address (IAD) / Network Address(NA) (Hex) and the RIT is given in Table 49 for BSC racks 1, 2 and 3. Thetable contains the relationships for all completely equipped racks and the RITposition in the rack, shelf and slot.

738 / 778 3BK 21618 AAAA PCZZA Ed.16


36.4.31 [51,2]


Test Results Byte Number Meaning Byte Description

Test Segment one byte only See Table 13.

Test Fault Type one byte only See Table 14.

Test Raw Data 0 + 1

2 + 3

4 - 19

Switch Network Address.

Link Network Address.

TDM

For relation of Switch NetworkAddress to board, see Table 49.

Associated port is under test.

For TDM Test Result Bytedescription, see Table 45.


Test Result Unsuccessful (some failures) Unsuccessful (tests not executed)

Test Segment 13 0

Test Fault Type 60 0

Test Raw Data H’00

H’10

H’10

H’10

H’45

H’10

H’10

H’10

H’00

H’12

H’10

H’10

H’40

H’10

H’10

H’10

H’13

H’10

H’10

H’10

H’00

H’FF

H’FF

H’FF

H’45

H’FF

H’FF

H’FF

H’00

H’FF

H’FF

H’FF

H’40

H’FF

H’FF

H’FF

H’FF

H’FF

H’FF

H’FF

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

If the Test Segment and the Test-Fault-Type are both at 0, the test did notexecute or a timeout was received. In this case, the TDM-Test -Resultsvalues will be set to #FF.

The relationship between the Interface Address (IAD) (Hex) / Network Address(NA) and the RIT is given in Table 49 for BSC racks 1, 2 and 3. The tablecontains the relationships for all completely equipped racks and the RITposition in the rack, shelf and slot.

3BK 21618 AAAA PCZZA Ed.16 739 / 778


For detailed information about BSC configurations, refer to the (BSC Cabinetand Subrack Description).

IAD/NA (Hex) RIT (Type) Position (Rack.Shelf.Slot)

0000 CPRCAB 1.8.17

0000 SWCHAB 1.8.37

0001 CPRCAB 1.8.19

0002 CPRCAC 1.8.21

0003 CPRCAC 1.8.25

0004 CPRCAA 1.8.29

0005 CPRCAA 1.8.31

0008 SWCHAA 1.7.1

0009 SWCHAA 1.7.3

000A SWCHAA 1.7.5

000B SWCHAA 1.7.7

000C SWCHAA 1.7.9

000D SWCHAA 1.7.11

000E SWCHAA 1.7.13

000F SWCHAA 1.7.15

0010 TCUC 1.7.29

0010 SWCHAB 1.7.45

0011 TCUC 1.7.31

0012 TCUC 1.7.33

0013 TCUC 1.7.35

0014 TCUC 1.7.37

0015 TCUC 1.7.39

0016 TCUC 1.7.41

0017 TCUC 1.7.43

0020 SWCHAB 1.6.9

0020 DTCC 1.6.13

740 / 778 3BK 21618 AAAA PCZZA Ed.16



0021 DTCC 1.6.15

0022 DTCC 1.6.17

0023 DTCC 1.6.19

0024 DTCC 1.6.23

0025 DTCC 1.6.25

0026 DTCC 1.6.27

0027 DTCC 1.6.29

0030 SWCHAB 1.6.41

0030 DTCC 1.6.45

0031 DTCC 1.6.47

0032 DTCC 1.6.49

0033 DTCC 1.6.51

0034 DTCC 1.6.55

0035 DTCC 1.6.57

0036 DTCC 1.6.59

0037 DTCC 1.6.61

0040 SWCHAB 1.8.39

0050 SWCHAB 1.7.47

0060 SWCHAB 1.6.11

0070 SWCHAB 1.6.43

0088 SWCHAA 1.8.45

0089 SWCHAA 1.8.47

008A SWCHAA 1.8.49

008B SWCHAA 1.8.51

008C SWCHAA 1.8.53

008D SWCHAA 1.8.55

008E SWCHAA 1.8.57

008F SWCHAA 1.8.59

3BK 21618 AAAA PCZZA Ed.16 741 / 778



0098 SWCHAA 1.2.1

0099 SWCHAA 1.2.3

009A SWCHAA 1.2.5

009B SWCHAA 1.2.7

009C SWCHAA 1.2.9

009D SWCHAA 1.2.11

009E SWCHAA 1.2.13

009F SWCHAA 1.2.15

00A8 SWCHAA 1.2.21

00A9 SWCHAA 1.2.23

00AA SWCHAA 1.2.25

00AB SWCHAA 1.2.27

00AC SWCHAA 1.2.29

00AD SWCHAA 1.2.31

00AE SWCHAA 1.2.33

00AF SWCHAA 1.2.35

00B8 SWCHAA 1.2.41

00B9 SWCHAA 1.2.43

00BA SWCHAA 1.2.45

00BB SWCHAA 1.2.47

00BC SWCHAA 1.2.49

00BD SWCHAA 1.2.51

00BE SWCHAA 1.2.53

00BF SWCHAA 1.2.55

00C8 SWCHAA 2.8.45

00C9 SWCHAA 2.8.47

00CA SWCHAA 2.8.49

00CB SWCHAA 2.8.51

742 / 778 3BK 21618 AAAA PCZZA Ed.16



00CC SWCHAA 2.8.53

00CD SWCHAA 2.8.55

00CE SWCHAA 2.8.57

00CF SWCHAA 2.8.59

00D8 SWCHAA 2.2.1

00D9 SWCHAA 2.2.3

00DA SWCHAA 2.2.5

00DB SWCHAA 2.2.7

00DC SWCHAA 2.2.9

00DD SWCHAA 2.2.11

00DE SWCHAA 2.2.13

00DF SWCHAA 2.2.15

00E8 SWCHAA 2.2.21

00E9 SWCHAA 2.2.23

00EA SWCHAA 2.2.25

00EB SWCHAA 2.2.27

00EC SWCHAA 2.2.29

00ED SWCHAA 2.2.31

00EE SWCHAA 2.2.33

00EF SWCHAA 2.2.35

00F8 SWCHAA 2.2.41

00F9 SWCHAA 2.2.43

00FA SWCHAA 2.2.45

00FB SWCHAA 2.2.47

00FC SWCHAA 2.2.49

00FD SWCHAA 2.2.51

00FE SWCHAA 2.2.53

00FF SWCHAA 2.2.55

3BK 21618 AAAA PCZZA Ed.16 743 / 778



0100 SWCHAB 1.4.25

0100 TCUC 1.4.9

0101 TCUC 1.4.11

0102 TCUC 1.4.13

0103 TCUC 1.4.15

0104 TCUC 1.4.17

0105 TCUC 1.4.19

0106 TCUC 1.4.21

0107 TCUC 1.4.23

0108 SWCHAA 1.6.5

0109 SWCHAA 1.6.7

010A SWCHAA 1.6.37

010B SWCHAA 1.6.39

010C SWCHAA 1.3.5

010D SWCHAA 1.3.7

010E SWCHAA 1.3.37

010F SWCHAA 1.3.39

0110 TCUC 1.4.41

0110 SWCHAB 1.4.57

0111 TCUC 1.4.43

0112 TCUC 1.4.45

0113 TCUC 1.4.47

0114 TCUC 1.4.49

0115 TCUC 1.4.51

0116 TCUC 1.4.53

0117 TCUC 1.4.55

0120 SWCHAB 1.3.9

0120 DTCC 1.3.13

744 / 778 3BK 21618 AAAA PCZZA Ed.16



0121 DTCC 1.3.15

0122 DTCC 1.3.17

0123 DTCC 1.3.19

0124 DTCC 1.3.23

0125 DTCC 1.3.25

0126 DTCC 1.3.27

0127 DTCC 1.3.29

0130 SWCHAB 1.3.41

0130 TCUC 1.3.45

0131 TCUC 1.3.47

0132 TCUC 1.3.49

0133 TCUC 1.3.51

0134 TCUC 1.3.53

0135 TCUC 1.3.55

0136 TCUC 1.3.57

0137 TCUC 1.3.59

0140 SWCHAB 1.4.27

0150 SWCHAB 1.4.59

0160 SWCHAB 1.3.11

0170 SWCHAB 1.3.43

0200 TCUC 2.8.17

0200 SWCHAB 2.8.37

0201 TCUC 2.8.19

0202 TCUC 2.8.21

0203 TCUC 2.8.25

0204 TCUC 2.8.29

0205 TCUC 2.8.31

0206 TCUC 2.8.33

3BK 21618 AAAA PCZZA Ed.16 745 / 778



0207 TCUC 2.8.35

0208 SWCHAA 2.7.1

0209 SWCHAA 2.7.3

020A SWCHAA 2.7.5

020B SWCHAA 2.7.7

020C SWCHAA 2.7.9

020D SWCHAA 2.7.11

020E SWCHAA 2.7.13

020F SWCHAA 2.7.15

0210 TCUC 2.7.29

0210 SWCHAB 2.7.45

0211 TCUC 2.7.31

0212 TCUC 2.7.33

0213 TCUC 2.7.35

0214 TCUC 2.7.37

0215 TCUC 2.7.39

0216 TCUC 2.7.41

0217 TCUC 2.7.43

0220 SWCHAB 2.6.9

0220 DTCC 2.6.13

0221 DTCC 2.6.15

0222 DTCC 2.6.17

0223 DTCC 2.6.19

0224 DTCC 2.6.23

0225 DTCC 2.6.25

0226 DTCC 2.6.27

0227 DTCC 2.6.29

0230 SWCHAB 2.6.41

746 / 778 3BK 21618 AAAA PCZZA Ed.16



0230 DTCC 2.6.45

0231 DTCC 2.6.47

0232 DTCC 2.6.49

0233 DTCC 2.6.51

0234 DTCC 2.6.55

0235 DTCC 2.6.57

0236 DTCC 2.6.59

0237 DTCC 2.6.61

0240 SWCHAB 2.8.39

0250 SWCHAB 2.7.47

0260 SWCHAB 2.6.11

0270 SWCHAB 2.6.43

0300 TCUC 2.4.9

0300 SWCHAB 2.4.25

0301 TCUC 2.4.11

0302 TCUC 2.4.13

0303 TCUC 2.4.15

0304 TCUC 2.4.17

0305 TCUC 2.4.19

0306 TCUC 2.4.21

0307 TCUC 2.4.23

0308 SWCHAA 2.6.5

0309 SWCHAA 2.6.7

030A SWCHAA 2.6.37

030B SWCHAA 2.6.39

030C SWCHAA 2.3.5

030D SWCHAA 2.3.7

030E SWCHAA 2.3.37

3BK 21618 AAAA PCZZA Ed.16 747 / 778



030F SWCHAA 2.3.39

0310 SWCHAB 2.4.57

0310 TCUC 2.4.41

0311 TCUC 2.4.43

0312 TCUC 2.4.45

0313 TCUC 2.4.47

0314 TCUC 2.4.49

0315 TCUC 2.4.51

0316 TCUC 2.4.53

0317 TCUC 2.4.55

0320 SWCHAB 2.3.9

0320 DTCC 2.3.13

0321 DTCC 2.3.15

0322 DTCC 2.3.17

0323 DTCC 2.3.19

0324 DTCC 2.3.23

0325 DTCC 2.3.25

0326 DTCC 2.3.27

0327 DTCC 2.3.29

0330 SWCHAB 2.3.41

0330 TCUC 2.3.45

0331 TCUC 2.3.47

0332 TCUC 2.3.49

0333 TCUC 2.3.51

0334 TCUC 2.3.53

0335 TCUC 2.3.55

0336 TCUC 2.3.57

0337 TCUC 2.3.59

748 / 778 3BK 21618 AAAA PCZZA Ed.16



0340 SWCHAB 2.4.27

0350 SWCHAB 2.4.59

0360 SWCHAB 2.3.11

0370 SWCHAB 2.3.43

0400 SWCHAB 3.8.37

0400 TCUC 3.8.17

0401 TCUC 3.8.19

0402 TCUC 3.8.21

0403 TCUC 3.8.25

0404 TCUC 3.8.29

0405 TCUC 3.8.31

0406 TCUC 3.8.33

0407 TCUC 3.8.35

0408 SWCHAA 3.7.1

0409 SWCHAA 3.7.3

040A SWCHAA 3.7.5

040B SWCHAA 3.7.7

040C SWCHAA 3.7.9

040D SWCHAA 3.7.11

040E SWCHAA 3.7.13

040F SWCHAA 3.7.15

0410 SWCHAB 3.7.45

0410 TCUC 3.7.29

0411 TCUC 3.7.31

0412 TCUC 3.7.33

0413 TCUC 3.7.35

0414 TCUC 3.7.37

0415 TCUC 3.7.39

3BK 21618 AAAA PCZZA Ed.16 749 / 778



0416 TCUC 3.7.41

0417 TCUC 3.7.43

0420 SWCHAB 3.6.9

0420 DTCC 3.6.13

0421 DTCC 3.6.15

0422 DTCC 3.6.17

0423 DTCC 3.6.19

0424 DTCC 3.6.23

0425 DTCC 3.6.25

0426 DTCC 3.6.27

0427 DTCC 3.6.29

0430 SWCHAB 3.6.41

0430 DTCC 3.6.45

0431 DTCC 3.6.47

0432 DTCC 3.6.49

0433 DTCC 3.6.51

0434 DTCC 3.6.55

0435 DTCC 3.6.57

0436 DTCC 3.6.59

0437 DTCC 3.6.61

0440 SWCHAB 3.8.39

0450 SWCHAB 3.7.47

0460 SWCHAB 3.6.11

0470 SWCHAB 3.6.43

0500 TCUC 3.4.9

0500 SWCHAB 3.4.25

0501 TCUC 3.4.11

0502 TCUC 3.4.13

750 / 778 3BK 21618 AAAA PCZZA Ed.16



0503 TCUC 3.4.15

0504 TCUC 3.4.17

0505 TCUC 3.4.19

0506 TCUC 3.4.21

0507 TCUC 3.4.23

0508 SWCHAA 3.6.5

0509 SWCHAA 3.6.7

050A SWCHAA 3.6.37

050B SWCHAA 3.6.39

050C SWCHAA 3.3.5

050D SWCHAA 3.3.7

050E SWCHAA 3.3.37

050F SWCHAA 3.3.39

0510 TCUC 3.4.41

0510 SWCHAB 3.4.57

0511 TCUC 3.4.43

0512 TCUC 3.4.45

0513 TCUC 3.4.47

0514 TCUC 3.4.49

0515 TCUC 3.4.51

0516 TCUC 3.4.53

0517 TCUC 3.4.55

0520 SWCHAB 3.3.9

0520 DTCC 3.3.13

0521 DTCC 3.3.15

0522 DTCC 3.3.17

0523 DTCC 3.3.19

0524 DTCC 3.3.23

3BK 21618 AAAA PCZZA Ed.16 751 / 778



0525 DTCC 3.3.25

0526 DTCC 3.3.27

0527 DTCC 3.3.29

0530 SWCHAB 3.3.41

0530 TCUC 3.3.45

0531 TCUC 3.3.47

0532 TCUC 3.3.49

0533 TCUC 3.3.51

0534 TCUC 3.3.53

0535 TCUC 3.3.55

0536 TCUC 3.3.57

0537 TCUC 3.3.59

0540 SWCHAB 3.4.27

0550 SWCHAB 3.4.59

0560 SWCHAB 3.3.11

0570 SWCHAB 3.3.43

Table 49: Relationship IAD/NA to RIT and Position

752 / 778 3BK 21618 AAAA PCZZA Ed.16


36.4.32 [51,3]

The additional information bytes for this alarm are defined in the following table.These bytes indicate the case when testing runs successfully.

Byte Number Meaning Test Results Explanation

0 TEST-RAW-DATA(0)

1 TEST-RAW-DATA(1)

Number of times a routinetest has run.

2 TEST-RAW-DATA(2)

3 TEST-RAW-DATA(3)

Number of tunnels.

4 TEST-RAW-DATA(4)

5 TEST-RAW-DATA(5)

Number of tested tunnels.

6 TEST-RAW-DATA(6)

7 TEST-RAW-DATA(7)

Number of successfultunnels.

8 TEST-RAW-DATA(8)

9 TEST-RAW-DATA(9)

Value 255 assigned.

Number of unsuccessfultunnels.


In the unsuccessful cases, the decoding of the byte information is describedin the Link/Switch Test Results section of the Operations & MaintenanceReference Guide.

3BK 21618 AAAA PCZZA Ed.16 753 / 778


36.4.33 [52,1], [52,5] and [52,7]


Byte Number Value Meaning

0 Local clock failure.

1 Reference selector failure.

2 PLL out of range (POOR).

3 Absence of own clock (CLKABS).

4 Watchdog timer expiry (WD).

0-1

5 Access failure (ACCESS-FAIL).

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

36.4.34 [53,0], [53,1], [53,3], [53,4], [53,6] and [53,7]



0-1 0 LOS detected.

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

36.4.35 [53,2]

The additional information bytes for this alarm is defined as follows.


0-1 0 DMA overrun detected by the Broadcast Control Unit inprocessors.

1 DMA underrun detected by the BCU in processors.


754 / 778 3BK 21618 AAAA PCZZA Ed.16


36.4.36 [53,5] and [53,8]



0-1 0 CRC detected on broadcast bus to SBL.

1 FTL detected on broadcast bus to SBL.

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

36.4.37 [101,8]

The additional information bytes for this alarms are defined below.


1 250 Tag for ABIS-HWAY-TP.

2 Number of faulty ABIS-HWAY-TP.

3 ABIS-HWAY-TP number of the first faulty Abis

4 ABIS-HWAY-TP number of the second faulty Abis Byte

Byte...

n 251 Tag for ATER-HWAY-TP.

n+1 Number of faulty ATER-HWAY-TP.

n+2 ATER-HWAY-TP number of the first faulty Ater.

n+3 ATER-HWAY-TP number of the second faulty Ater.

Byte...

Remark: locked E1 are not reported.


Note: Locked E1 are not reported.

3BK 21618 AAAA PCZZA Ed.16 755 / 778


36.5 TC AlarmsThis section describes the additional information provided by other TC alarms.

36.5.1 [67,22] to [67,130]

The TC-16 SBL Alarm number is always 1.

36.5.2 [70,219]

The Error is defined below.

NAME SIZE DESCRIPTION

RecoveryLevel

1 The action taken by the TSC to recover from the error(RESET/RESTART/REPORT/NONE).

Error Type 1 The actual error type which is reported by the TSC modules.

Filename 20 Zero-terminated string that gives the filename of the module which reportedthe error.

SPARE 2 -

Line nbr 4 Line number in the file where the error was risen.

Param1 4 Parameter with extra debugging information.

Param2 4 Parameter with extra debugging information.


36.5.3 [73,022] to [73,216]

The alarm numbers are defined as follows.

Alarm NbrHW boards SBLs Provided inthe Alarm

RITS Providedin the Alarm

Board Interface Error

BSI Interface

- 1..8BIUA HWBoards

BSC_ADAPT BIUA

00 - -

Table 57: Additional Information for Alarm [73,022] to [73,216]

756 / 778 3BK 21618 AAAA PCZZA Ed.16


36.5.4 [75,20] to [75,247]

The alarm numbers are defined below.

Alarm NbrHW boards SBLsProvided inthe Alarm

RITSProvided inthe Alarm Board Interface

ErrorATERInterface

TributaryInterface

- 00 - - -

- - 10 - 1st

- - 20 - 2nd

- - 30 - 3rd

-

ASMB

- 40 - 4th

- 00 - - -

- - 10 - 1st

- - 20 - 2nd

- - 30 - 3rd

AlcatelSM2M HWBoards TCG2

-

ASMC

- 40 - 4th

TC-ADAPT 00 - - -AlcatelTRCU TCG2

ATBX

- 02 -


3BK 21618 AAAA PCZZA Ed.16 757 / 778


36.5.5 MT120 Board Equipment Reset

The equipment reset/reset fields are described below.

Field Name Size (Bytes) +Type

Meaning

Restart Countervalue

-

Autonomous/Operator This parameter indicates if the reset occurs because of anoperator request or autonomously.

Error Type

One UnsignedCharacter.

Range 60...80 is MT120 specific. The reset structure dependson the hardware type. The hardware type MT120 is mappedonto a range of Error Type from 60 to 80. All the error typeswhich do not belong to this set have the following format, seeTable 61.

Table 59: MT120 Board - Equipment Reset/Reset

36.5.6 MT120 - Error Range >80

Refer to the table below.

Field Name Size (Bytes) +Type

Meaning

Program Identity Program identity of the process which reports the alarm.

User Data Segment

One UnsignedCharacter.

User Data Segment.

Table 60: MT120 Board, Range >80

758 / 778 3BK 21618 AAAA PCZZA Ed.16


36.5.7 MT120 Board, Range <80

The following table defines the error types for the MT120 board with a rangeless than 80.

Error Type TypeNumber

RecoveryLevel

Description Action AdditionalInfo

Power-on 60 Reset When the MT120is powered on, thisalarm is built.

All memory which belongsto the application iscleared, is set to 00. Thestartup is done with thedefault configuration.

OTPhardwarewatchdog

61 Reset The HW watchdogtimer has expiredcaused by a loopsomewhere in thecode.

A reset is always triggered.In the reset sequence, thelast correct software (1 of3 possibilities) is activated.All memory is cleared. Theconfiguration is saved intoflash memory otherwise.If corrupted, the defaultconfiguration is applied.

None.

OTP externalor internalscenariofailure

62 Reset/Restart An external orinternal scenariohas failed due to atimeout expiration.

A reset/restart is triggered,the OTP comes back to anoperational state using thesaved configuration.

OTP lackof internalresources

63 Reset/Restart This error occurs,when there is nomemory free for theapplications.

OTPexception

64 Reset/Restart An exception hasoccurred, a detailedlist is given inthe additionalinformation, seeTable 62.

OTP SDTcrash

65 Reset/Restart An error hasoccurred in thegenerated code.

DSPpost-mortem

66 Reset/Restart An error hasoccurred in theDSP.

MT120auto-testfailure

67 Reset A hardware errorhas been detectedby the auto-tests.

A buffer is built afterprocessor reset/restart.

See Table62

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

3BK 21618 AAAA PCZZA Ed.16 759 / 778


36.5.8 MT120 Board, Error Types

The following table describes the additional information given for the MT120board error types.

Error Type Size Description

Taskname 4 Task name in ASCII which has caused theauto-restart/auto-reset.

MID 2 Internal Message Identifier to identify the internal scenario.

Reference 2 External reference number (Ater Mux or MMI) to identifythe scenario, 0 is for autonomous.

Scenario id 2 Scenario message identifier used to identify the external orautonomous scenario.

0 Operator scenario from the OMC-R

1 Operator from the BSC terminal

2 Operator from the TC terminal

4 Autonomous action

Origin ofaction

1

5 Unknown

01 Indicates three successful auto-restarts.

OTP external orinternal scenariofailure.

FailureDescription

1

FF No information.


0 Message buffer

1 Memory allocation

Memoryregion

1

2 Memory re-allocation

Memory size 4 The requested memory size which could not be served.

OTP external orinternal scenariofailure.

Stack Info 60 The information is taken from the stack.

760 / 778 3BK 21618 AAAA PCZZA Ed.16




01 System Reset

02 Machine Reset

03 Data Storage

04 Instruction storage

06 Alignment

07 Program

08 Floating point unavailable

OD Trace

OE Floating Point assist

10 Software emulation

13 Instruction TLB error

Interrupt entry 1

14 Data TLB error

SRR0 4

SRR1 4

See MPC860 UMD, Interrupts section.

See MPC860 UMD, Interrupts section, only 3 bits arereported.

bit0 MRS.IP

bit1 MRS.ME

MRS 1

bit2 MRS.LE

See MPC860 UMD, Interrupts section, only 3 bits arereported.

bit0 DSISR BIT 1

bit1 DSISR BIT 4

DSISR 1

bit2 DSISR BIT 6

DAR 4

IR 4

See MPC860 UMD, Interrupts section.

OTP exception

Stack Info 60 The information is taken from the stack.

3BK 21618 AAAA PCZZA Ed.16 761 / 778




IR 4 Link register, it gives the program counter in SDT-generatedcode where the error has occurred.

Signal 4 Signal value (in case of an error on a signal).

OTP SDT crash

State 4 State of the autonon when the signal was received.

Error 4 The post-mortem value.DSPpost-mortem

More N Additional Information.

Severity 1 Non-fatal or fatal error detected during auto-tests.

Entity 1 Faulty processor.

Status 1 Detailed step in DSP autotest.

Test 1 Faulty testnumber

-

Error 1 Error code -

Length 1 Length inbytes

-

MT120 auto-testfailure

Info N Additionalinformation

-

Table 62: MT120 board, Error Types, Additional Information

762 / 778 3BK 21618 AAAA PCZZA Ed.16


36.6 BTS AlarmsThis section describes the additional information provided by other BTS alarms.

36.6.1 [74,20] to [74,202]

The alarm numbers are defined as follows.

Alarm NbrHW boards SBLs Providedin the Alarm

RITS Providedin the Alarm

Board Interface Error

BSI Interface

00 - -uBTS HWBOARDS

SMFG

- 11,12,16

00 - -9100BTS HWBOARDS

BTS_ADAPT

SUM

- 11


3BK 21618 AAAA PCZZA Ed.16 763 / 778


764 / 778 3BK 21618 AAAA PCZZA Ed.16

37 Consequences of an SBL State Change


This section defines the alarm impact on the system due to an SBL statechange.

3BK 21618 AAAA PCZZA Ed.16 765 / 778


37.1 9120 BSC SBLs

SBL nameSBLstate Impact on system

IT The telecom and O&M link between the BSC and the BTS or twoBTSs is functioning correctly.

FIT Degradation in the telecom and O&M link between the BSC andthe BTS or two BTSs.

FLT Loss of telecom and O&M link between the BSC and the BTS ortwo BTSs.

ABIS-HWAY-TP

OPR The alarm reporting on the transmission link is disabled.If relatedto the second Abis, for a second Abis BTS, the TS on the secondAbis are no more used.

IT Gain of a terrestrial traffic channel to the MSC. The channel canbe used for traffic.

ACH

FLT/FOS Causes loss of a terrestrial traffic channel to the MSC. The channelwill no longer be used for traffic.

IT The telecom link between the TC and the MSC is functioningcorrectly.

FIT Degradation in the telecom and O&M link between the TC andthe MSC.

FLT Loss of telecom and O&M link between the TC and the MSC.

A-PCM-TP

OPR The alarm reporting on the transmission link is disabled.

IT The link between the two submultiplexers is functioning correctly.

FLT Loss of link between the two submultiplexers.

ATER-HWAY-TP


IT Gain of speech or data connections over this trunk. If the ATR backin service can be used for clock extraction and the BSC is currentlyusing its local clock as the reference, then the BSC tries to switchback to the external clock provided by the ATR.

ATR

FLT/EF Causes loss of speech or data connections over this trunk. If theATR is used for clock extraction, the BSC selects another ATR. Ifno other ATR is available, the BSC uses its local clock. The trunkwill no longer be used for traffic.

IT Gain of the backup facility.BATTERY

FLT Causes loss of the backup facility, normally activated on loss ofpower to the RAM disk.

766 / 778 3BK 21618 AAAA PCZZA Ed.16



IT The rack broadcast bus is distributed to the associated CEs.

FIT Either there is a degradation for the full rack, or there is a failurefor one or 2 CE. This state has no telecom impact if the otherBC-RACK-BUS is IT.

FLT This branch of the broadcast bus is not working anymore. Thisstate has no telecom impact if the other BC-RACK-BUS is IT.

BC-RACK-BUS

OPR The rack broadcast bus (BC_RACK_BUS SBL) is disabled by theoperator.

IT The system broadcast bus is distributed correctly to all racks.BC-SYS-BUS

OPR The system broadcast bus (BC_SYS_BUS SBL) is disabled bythe Operator.

IT The BSC is working correctly.BSC

FIT When two CLK-REP of the same rack (rack not containing the

BCLA-SYS-boards) are failing.

When the BSC is running on a local clock.

Loss of both broadcast buses in the BSC either only at a CE

level, or at rack level, or at system level. LAC paging messages

do not work except for the first 3 cells of the LAC, thuspreventing Mobile terminating calls for the other cells, GPRS

reset procedure do not work anymore. Processors cannotbe preloaded, thus lengthening outages in SW replacement

procedure. RMS measurements are no more started norstopped.

A high number of BSC processors have reported DMA

problems.

3BK 21618 AAAA PCZZA Ed.16 767 / 778



IT The BIUA board, which multiplexes BS trunks onto an ABISHWAY-TP at BSC side, is functioning correctly.

FIT There is a degradation in the service provided by the BIUA board,which multiplexes BS trunks onto an ABIS HWAY-TP at BSC side.

FLT/FOS The BSC transmission board (BUIA), which multiplexes BStrunks onto an ABIS HWAY-TP at BSC side, is lost. It cannot beprogrammed or accessed.

BSC-ADAPT

OPR The BIUA board, which multiplexes BS trunks onto an ABISHWAY-TP at BSC side, is disabled.

This state has no impact on the telecom functions of the board,only on the O&M part.

IT Gain of telecom availability of all the cells of a BSC from BSCpoint of view.

FLT Loss of telecom availability of all cells of a BSC from the BSCpoint of view.

FIT Degradation of telecom availability of all cells of a BSC from theBSC point of view.

BSS-TEL

OPR Loss of telecom availability of all cells of a BSC from the BSCpoint of view.

IT The BTS-BIE, which demultiplexes Abis channels from an ABISHWAY-TP at BTS side, is functioning correctly.

FIT There is a degradation in the service provided by BTS-BIE board,which demultiplexes Abis channels from an ABIS HWAY-TP atBTS side.

FLT/FOS The BTS-BIE board, which demultiplexes Abis channels from anABIS HWAY-TP at BTS side, is lost. It cannot be programmed oraccessed.

BTS-ADAPT

OPR This state has no impact on the telecom functions of the board,only on the O&M part.

IT Gain of full O&M availability of the cell from the BSC point of view.

FLT/FOS Loss of O&M availability of the cell from the BSC point of view. Ifparameters must be changed the cell mapped on this BTS becomeout of service.

BTS-OM

OPR Loss of O&M availability of the cell from the BSC point of view. Ifparameters must be changed the cell mapped on this BTS becomeout of service.

BTS-POOL IT Gain of telecom availability of the extra Abis TS

768 / 778 3BK 21618 AAAA PCZZA Ed.16



IT Gain of telecom availability of the cell from the BSC point of view.

FLT Loss of telecom availability of the cell from the BSC point of view.

FIT Degradation of telecom availability of the cell from the BSC pointof view.

BTS-TEL

OPR Loss of telecom availability of the cell from the BSC point of view.

IT The clock generator works correctly.

FIT The clock has detected the loss of its local clock. There is noimpact on the service.

FLT If only one CLK-GEN is unavailable, there is no impact on theservice. BSC will use the clock provided by the other CLK-GEN.

CLK-GEN

OPR Clock generation is disabled by the operator.

IT The clock repeater works correctly.

FIT The clock repeater loses either System Clock A or System Clock B.

FLT A failure is detected in the BCLA-RACK board. If only oneCLK-REP is unavailable, there is no impact on the service. If noCLK-REP is available no Clock reference is repeated.

CLK-REP

OPR The clock repeater is disabled by the operator.

IT The convertor is working correctly.CONV

FLT There is no impact on traffic because the power supplies are inparallel.

IT The CPR is working correctly.CPR

OPR The standby CPR will become the master CPR and takes over allfunctions.

S-CPR Duplex FLT/FOS The standby S-CPR will become the master System CPR andtakes over all functions. SW/DB replacement actions will not beallowed.

O-CPR DUPLEX FLT/FOS The standby O-CPR will become the master O-CPR and takes overall functions. If the old master was carrying the X.25 link with theOMC-R, this link is lost and scheduled performance measurementjobs are not reactivated in due time.

S-CPR/O-CPR FIT The processor has reported a high number of DMA problems.

3BK 21618 AAAA PCZZA Ed.16 769 / 778



FLT The broadcast processor is not broadcasting.

OPR The broadcast processor is not broadcasting.

CPR (BC_CPR)

NEQ The BC_CPR SBL is not defined in the BSC database.

Speech or data connections to the MSC or MFS:

IT These connections are re-established. New connections arepossible. Change back of the SCCP connections on the N7handled by the DTCs occurs.

FLT/FOS These connections on the associated PCM (1/4 of an Atermux) arelost. No new connections are possible.

Depending on the DTC assignation, other function can be affected:

If the DTC carries a TCH resource manager, there is no extraeffect on the calls.

If the DTC carries N7, the SCCP connections are abortedafter some time. N7 Signaling will be handled by other DTCs

(=changeover). Degradation can happen if the remaining

capacity is too small.

If DTC carries BSSAP/GPRSAP, all concerned SCCP

connections are lost.

If the DTC manages a GSL, as long as there are other GSLfor the corresponding GPU, there is no loss of transactions

(degradation can happen if the remaining capacity is too small).

FIT The processor has reported a high number of DMA problems.

DTC

OPR These connections on the associated PCM (1/4 of an Atermux) arelost. No new connections are possible.



If the DTC carries N7, the SCCP connections are aborted

after some time. N7 Signaling will be handled by other DTCs(=changeover). Degradation can happen if the remaining


If DTC carries BSSAP/GPRSAP, all concerned SCCPconnections are lost.



770 / 778 3BK 21618 AAAA PCZZA Ed.16



GSL IT GPRS signalisation is working correctly.

FLT GPRS signalisation is not working correctly.

IT N7 Signaling can now be handled by the N7 link (=changeback).

FLT/EF N7 Signaling will be handled by another N7 link (=changeover).

N7

OPR N7 Signaling will be handled by another N7 link (=changeover).

IT Communication with the OMU is re-established. Can have animpact on the BTS_O&M state.

OML

FLT Causes loss of communication with the OMU. Will have an impacton the BTS_O&M state, depending on the kind of transactionstarted by the BSC when the OML is down.

IT Communication with the TRE/TRX is established. Gain intelecommunication resource allocation capability on the BTS.

OPR The RSL SBL may cause loss of communication with the FrameUnit. Leads to a reduced telecommunication resource allocationcapability on the BTS.

RSL

FLT The RSL SBL may cause loss of communication with the FrameUnit. Leads to a reduced telecommunication resource allocationcapability on the BTS.

IT The multiplexing on the ATER side is functioning correctly.

FIT The multiplexing on the ATER side is degraded.

FLT/FOS The multiplexing board ASMC (It sub-multiplexes A-trunks at theTranscoder)/ASMB (It sub-multiplexes A-trunks at the BSC) isnot functioning correctly. Complete multiplexing on the Ater sideis not being done.

SM-ADAPT

OPR The multiplexing board ASMC/ASMB are disabled. Completemultiplexing on the Ater is not being done.

IT All links associated with the Switch are IT. All links associated withthe switch can be used.

FLT Causes loss of speech or data connections over this switch. Thisswitch can no longer be used. More than 51% of links associatedto Switch are FLT.

SWITCH

FIT Causes loss of some speech or data connections over this switch.This switch can still be used. Less than 51% of links associatedto Switch are FLT.

3BK 21618 AAAA PCZZA Ed.16 771 / 778



IT The link adaption between the MSC and the Submultiplexer isfunctioning correctly.

FIT The link adaption between the MSC and the Submultiplexer isdegraded.

FLT The link adaption between the MSC and the Submultiplexer is notfunctioning correctly.

TC-ADAPT

OPR The link adaption between the MSC and the Submultiplexer isdisabled. On-going calls are not lost, no new calls can be initiated.

IT Communication with TRE/TRX and/or OMU and/or TSC isestablished. See RSL and/or OML and/or TSL.

FLT/FOS Causes loss of communication with Frame Unit(s) and/or OMUand/or TSC. See RSL and/or OML and/or TSL.

OPR Causes loss of communication with Frame Unit(s) and/or OMUand/or TSC. See RSL and/or OML and/or TSL.

TCU

FIT The processor has reported a high number of DMA problems

IT The A-interface channels managed by the BSC are functioningcorrectly.

FIT The A-interface channels managed by the BSC are degraded.

FLT The A-interface channels managed by the concerned TC-16 SBLare not functioning correctly.

TC-16

OPR The A-interface channels managed by the concerned TC-16 SBLare disabled.

IT Gain of transmission O&M availability from the BSC point of view.TR-OM

FLT Loss of transmission O&M availability from the BSC point of view.

IT The transmission processor controlling transmission O&M isfunctioning correctly.

TSC

FIT The transmission processor controlling transmission O&M isdegraded.

IT Connection between the BSC and a local terminal or OMC-Ris established.

FLT If there is no X.25 redundancy, causes loss of connection betweenthe BSC and a local terminal or OMC-R.

X.25

OPR If there is no X.25 redundancy, causes loss of connection betweenthe BSC and a local terminal or OMC-R.

772 / 778 3BK 21618 AAAA PCZZA Ed.16


37.2 9130 BSC Evolution SBLs


IT The telecom and O&M link between the BSC and the BTS or twoBTSs is functioning correctly.

FIT Degradation in the telecom and O&M link between the BSC andthe BTS or two BTSs.

FLT Loss of telecom and O&M link between the BSC and the BTS ortwo BTSs.

ABIS-HWAY-TP

OPR The alarm reporting on the transmission link is disabled.If relatedto the second Abis, for a second Abis BTS, the TS on the secondAbis are no more used.

IT Gain of a terrestrial traffic channel to the MSC. The channel canbe used for traffic.

ACH

FLT/FOS Causes loss of a terrestrial traffic channel to the MSC. The channelwill no longer be used for traffic.

IT The telecom link between the TC and the MSC is functioningcorrectly.

FIT Degradation in the telecom and O&M link between the TC andthe MSC.

FLT Loss of telecom and O&M link between the TC and the MSC.

A-PCM-TP


IT The link between the two submultiplexers is functioning correctly.

FLT Loss of link between the two submultiplexers.

ATER-HWAY-TP


IT Gain of speech or data connections over this trunk. If the ATR backin service can be used for clock extraction and the BSC is currentlyusing its local clock as the reference, then the BSC tries to switchback to the external clock provided by the ATR.

ATR

FLT/EF Causes loss of speech or data connections over this trunk. If theATR is used for clock extraction, the BSC selects another ATR. Ifno other ATR is available, the BSC uses its local clock. The trunkwill no longer be used for traffic.

3BK 21618 AAAA PCZZA Ed.16 773 / 778



IT The BSC is working correctly.BSC

FIT There is a persistent problem on the N7 links. New calls can notbe established.

IT Gain of telecom availability of all the cells of a BSC from BSCpoint of view.

FLT Loss of telecom availability of all cells of a BSC from the BSCpoint of view.

FIT Degradation of telecom availability of all cells of a BSC from theBSC point of view.

BSS-TEL

OPR Loss of telecom availability of all cells of a BSC from the BSCpoint of view.

The BTS-BIE, which demultiplexes Abis channels from an ABISHWAY-TP at BTS side, is functioning correctly.

FIT There is a degradation in the service provided by BTS-BIE board,which demultiplexes Abis channels from an ABIS HWAY-TP atBTS side.

FLT/FOS The BTS-BIE board, which demultiplexes Abis channels from anABIS HWAY-TP at BTS side, is lost. It cannot be programmed oraccessed.

BTS-ADAPT

OPR This state has no impact on the telecom functions of the board,only on the O&M part.

IT Gain of full O&M availability of the cell from the BSC point of view.

FLT/FOS Loss of O&M availability of the cell from the BSC point of view. Ifparameters must be changed the cell mapped on this BTS becomeout of service.

BTS-OM

OPR Loss of O&M availability of the cell from the BSC point of view. Ifparameters must be changed the cell mapped on this BTS becomeout of service.

BTS-POOL IT Gain of telecom availability of the extra Abis TS

774 / 778 3BK 21618 AAAA PCZZA Ed.16



IT Gain of telecom availability of the cell from the BSC point of view.

FLT Loss of telecom availability of the cell from the BSC point of view.

FIT Degradation of telecom availability of the cell from the BSC pointof view.

BTS-TEL

OPR Loss of telecom availability of the cell from the BSC point of view.

CP-HW IT The board is working correctly.

FLT The board is not working correctly. The standby board will becomeactive and takes over all the functions. In case there is no moreCP-HW operational a part of the cells and a part of interfaces(Abis, Ater) will be lost.

OPR The board is disabled by the operator. The standby board willbecome active and takes over all the functions.

CP-LOG IT The application software works correctly.

FLT The application software does not work correctly. This correspondsto the double fault seen on CP-HW, a part of the cells and a part ofinterfaces (Abis, Ater) would be lost

IT The CPR is working correctly.CPR

FLT All stable calls are not affected. Due to TCH-RM takeover somesignaling messages can be lost which can affect some transactionsin progress (call setup or handovers). Some CMISE exchanges orfile transfers with OMC-R may be interrupted. Anew instance ofthe process takes over all functions.

3BK 21618 AAAA PCZZA Ed.16 775 / 778



Speech or data connections to the MSC or MFS:

IT These connections are re-established. New connections arepossible. Change back of the SCCP connections on the N7handled by the DTCs occurs.

DTC

FLT/FOS These connections on the associated PCM (1/4 of an Atermux) arelost. No new connections are possible.



If the DTC carries N7, the SCCP connections are abortedafter some time. N7 Signaling will be handled by other DTCs

(=changeover). Degradation can happen if the remaining


If DTC carries BSSAP/GPRSAP, all concerned SCCP

connections are lost.



ECU IT Concentration unit for all E1 links collected by MUX board isworking correctly.

FLT Concentration unit for all E1 links collected by MUX board is notworking correctly of the MUX board lost the connection with theOMCP board. The standby board will become active and takesover all the functions.

ETU IT Concentration unit for all E1 links collected by LIU board is workingcorrectly.

FIT One 16 E1 serial link failed.

FLT Concentration unit for all E1 links collected by LIU board is notworking correctly. All E1 connected on the LIU are lost.

FAN IT Fan unit is working correctly.

FLT Fan unit is not working correctly.

GSL IT GPRS signalisation is working correctly.

FLT GPRS signalisation is not working correctly. If there are notenough resources available data transactions can fail due dueto signalling links congestion.

776 / 778 3BK 21618 AAAA PCZZA Ed.16



IT N7 Signaling can now be handled by the N7 link (=changeback).

FLT/EF N7 Signaling will be handled by another N7 link (=changeover). Ifthere are not enough resources available calls can fail due dueto signalling links congestion.

N7

OPR N7 Signaling will be handled by another N7 link (=changeover).

IT Communication with the OMU is re-established. Can have animpact on the BTS_O&M state.

OML

FLT Causes loss of communication with the OMU. Will have an impacton the BTS_O&M state, depending on the kind of transactionstarted by the BSC when the OML is down.

PEM IT The power entry module is working correctly.

FLT The power entry module is not working correctly. There is noimpact on traffic because the power supplies are in parallel.

IT Communication with the TRE/TRX is established. Gain intelecommunication resource allocation capability on the BTS.

OPR The RSL SBL may cause loss of communication with the FrameUnit. Leads to a reduced telecommunication resource allocationcapability on the BTS.

RSL

FLT The RSL SBL may cause loss of communication with the FrameUnit. Leads to a reduced telecommunication resource allocationcapability on the BTS.

SMM IT The SMM board is working correctly.

FLT The SMM board is not working correctly. The standby board willbecome active and takes over all the functions.

OPR The SMM board was disabled by the operator. The standby boardwill become active and takes over all the functions.

SSW-HW IT The SSW board is working correctly.

FLT The SSW board is not working correctly. The standby board willbecome active and takes over all the functions.

OPR The SSW board was disabled by the operator. The standby boardwill become active and takes over all the functions.

If the SSW supports the connection to the external alarm box theconnection is lost and the external alarms will not be supervised.

3BK 21618 AAAA PCZZA Ed.16 777 / 778



IT The link adaption between the MSC and the Submultiplexer isfunctioning correctly.

FIT The link adaption between the MSC and the Submultiplexer isdegraded.

FLT The link adaption between the MSC and the Submultiplexer is notfunctioning correctly.

TC-ADAPT

OPR The link adaption between the MSC and the Submultiplexer isdisabled. On-going calls are not lost, no new calls can be initiated.

IT Communication with TRE/TRX and/or OMU and/or TSC isestablished. See RSL and/or OML and/or TSL.

TCU

FLT All calls carried by TRX managed by the TCU process are lost. Newcalls can be established after a new instance is started.Causesloss of communication with Frame Unit(s) and/or OMU and/or TSC.

IT The A-interface channels managed by the BSC are functioningcorrectly.

FIT The A-interface channels managed by the BSC are degraded.

FLT The A-interface channels managed by the concerned TC-16 SBLare not functioning correctly.

TC-16

OPR The A-interface channels managed by the concerned TC-16 SBLare disabled.

TP-HW IT The TP board is working correctly.

FIT Non fatal alarms are present in TPGSM board or configurationchange due to extension/reduction failed to apply to TPGSM board.

FLT The TP board is not working correctly. The standby board willbecome active and takes over all the functions.

OPR The board is disabled by the operator. The standby board willbecome active and takes over all the functions.

IT Gain of transmission O&M availability from the BSC point of view.TR-OM

FLT Loss of transmission O&M availability from the BSC point of view.

IT The transmission processor controlling transmission O&M isfunctioning correctly.

TSC

FLT All transmission downloading managed by the process is lost.

778 / 778 3BK 21618 AAAA PCZZA Ed.16

bsc & tc alarm dictionary - b11

Documents

communication

communication

communication

wrong ptr

equipment

equipment

communication

communication