E-935 Mfs Alarm Dictionary

Alcatel BSS

EVOLIUM A935 MFS AlarmDictionary

O&M Documentation

Reference Guide

3BK 20417 AAAA PCZZA Ed.09

Status RELEASED

Short title MFS Alarm Dictionary

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 / 146 3BK 20417 AAAA PCZZA Ed.09

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2 A1353-RA AS Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.3 IMT Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2 NECTAR Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.1 Communication subsystem failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.2 IAN error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.3 Version mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.4 Software error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.5 Software program abnormally terminated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.6 Power problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.7 I/O device error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.8 Equipment malfunction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.9 Adaptor error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.10 Ventilation system failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332.11 Heating/ventilation/cooling system problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.12 Temperature unacceptable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.13 Storage capacity problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3 GPU/JBETI Boards Alarm Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.1 PCI System Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.2 PCI Parity Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.3 GPU loss of contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.4 Ethernet error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.5 HDLC auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503.6 MT90820 Matrix auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513.7 MT90823 Matrix auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523.8 BGTCGC auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533.9 BGRECC auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543.10 JGHPI auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553.11 JGGPU2 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563.12 PLX9080 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573.13 PLX9054 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583.14 NGISL2 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593.15 NGISL3 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603.16 BGPLTC auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613.17 GT-64161A auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623.18 Ethernet auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633.19 DSP auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653.20 DSP error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.21 Framer auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673.22 Time base clock error (SGSN only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.23 Free run mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693.24 Applique Presence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

4 PCM-TTP Alarm Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734.1 LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744.2 LFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764.3 AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774.4 CH0–EERH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784.5 RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794.6 DFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814.7 CRC4–BERH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

3BK 20417 AAAA PCZZA Ed.09 3 / 146

Contents

4.8 CRC4–BERL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

5 SUB-RACK Alarm Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855.1 Board Ethernet error at initialization phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865.2 Board firmware updated part error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875.3 Board firmware permanent part error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885.4 Board DRAM error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895.5 Board ECC test error during boot phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915.6 Board target abort during boot phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925.7 Unlocked board deletion alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935.8 JBETI slot4 loss of contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945.9 JBETI slot23 loss of contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955.10 No JBETI on subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965.11 JBETI address error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985.12 Fan problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005.13 Temperature problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.14 48V alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045.15 PRE48 alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065.16 CALVREF alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075.17 ACP1 alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1095.18 Hub converter problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1105.19 CNVR converter alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125.20 2.1V alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135.21 JAETI Failure (slot 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145.22 JAETI Failure (slot 23) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155.23 EALM1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165.24 EALM2 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1185.25 EALM3 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1195.26 EALM4 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205.27 EALM5 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215.28 EALM6 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1225.29 EALM7 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235.30 EALM8 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

6 MFS Telecommunication Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1256.1 SGSN in user mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1266.2 No response from network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1276.3 No reply from network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1286.4 No reply from SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1296.5 NSEI mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1306.6 NSVCI mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1316.7 Inactive DLCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1326.8 Unknown DLCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1336.9 GSL out (B6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346.10 GSL out (B7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1356.11 BVCSig is broken on (B7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1366.12 BVC out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1376.13 LapDLink disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

7 MFS Alarm Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1417.1 MFS Q3 specific problem identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

4 / 146 3BK 20417 AAAA PCZZA Ed.09

Figures

FiguresFigure 1: Communication subsystem failure: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Figure 2: IAN error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 3: Version mismatch: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Figure 4: Software error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Figure 5: Power problem: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Figure 6: I/O device error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Figure 7: Equipment malfunction: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Figure 8: Adaptor error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Figure 9: Ventilation system failure: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Figure 10: Heating/ventilation/cooling system problem: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Figure 11: Temperature unacceptable: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Figure 12: Storage capacity problem: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Figure 13: PCI System Error: Corrective Actions for JBETI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Figure 14: PCI System Error: Corrective Actions for GPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Figure 15: PCI Parity Error: Corrective Actions for GPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Figure 16: PCI Parity Error: Corrective Actions for JBETI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Figure 17: GPU loss of contact: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Figure 18: Ethernet error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Figure 19: HDLC auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Figure 20: MT90820 Matrix auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Figure 21: MT90823 Matrix auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Figure 22: BGTCGC auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Figure 23: BGRECC auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Figure 24: JGHPI auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Figure 25: JGGPU2 auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Figure 26: PLX9080 auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Figure 27: PLX9054 auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Figure 28: NGISL2 auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Figure 29: NGISL3 auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Figure 30: BGPLTC auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Figure 31: GT-64161A auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Figure 32: Ethernet auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Figure 33: DSP error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Figure 34: Framer auto-test error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Figure 35: Free run mode: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Figure 36: Applique presence: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Figure 37: LOS: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Figure 38: LFA: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Figure 39: AIS: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

3BK 20417 AAAA PCZZA Ed.09 5 / 146

Figures

Figure 40: CH0–EERH: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Figure 41: RAI: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Figure 42: DFM: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Figure 43: CRC4–BERH: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Figure 44: CRC4–BERL: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Figure 45: Board Ethernet error at initialization phase: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Figure 46: Board firmware updated part error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Figure 47: Board firmware permanent part error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Figure 48: Board DRAM error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Figure 49: Board ECC test error during boot phase: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Figure 50: Board target abort during boot phase: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Figure 51: Unlocked board deletion alarm: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Figure 52: JBETI slot4 loss of contact: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Figure 53: JBETI slot23 loss of contact: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Figure 54: No JBETI on subrack: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Figure 55: JBETI address error: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Figure 56: Fan problem: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Figure 57: Temperature problem: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Figure 58: 48V alarm: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Figure 59: PRE48 alarm: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Figure 60: CALVREF alarm: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Figure 61: ACP1 alarm: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Figure 62: Hub converter problem: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Figure 63: CNVR converter alarm: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Figure 64: 2.1V alarm: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Figure 65: JAETI Failure (slot 4): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Figure 66: JAETI Failure (slot 23): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Figure 67: EALM1: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117








Figure 75: No response from network: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Figure 76: No reply from network: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Figure 77: No reply from SGSN: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Figure 78: NSEI mismatch: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Figure 79: NSVCI mismatch: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

6 / 146 3BK 20417 AAAA PCZZA Ed.09

Figures

Figure 80: GSL out: Corrective Actions (B6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Figure 81: GSL out (B7): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Figure 82: BVCSig is broken on (B7): Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Figure 83: LapDLink disabled: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

3BK 20417 AAAA PCZZA Ed.09 7 / 146

Tables

TablesTable 1: Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Table 2: Alarm Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table 3: MFS Alarm Detailed View Window format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Table 4: MFS Q3 Alarm Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

8 / 146 3BK 20417 AAAA PCZZA Ed.09

Preface

Preface

Purpose The purpose of this document is to provide the operator with a structuredmethod for handling MFS alarm messages.

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

This document contains a list of all A935 MFS alarms, and the actions requiredto remove them.

The alarms are displayed at the OMC-R terminal and at the IMT to inform theoperator of system faults.

Assumed Knowledge The operator must be familiar with the following:

Alcatel O&M concepts for the BSS and MFS

Fault management

Use of OMC-R and IMT terminals

Telecommunications techniques including line transmission and switching.

3BK 20417 AAAA PCZZA Ed.09 9 / 146

Preface

10 / 146 3BK 20417 AAAA PCZZA Ed.09

1 Introduction

1 Introduction

This chapter describes the structure of the A935 MFS alarm messages.

It provides information on:

A1353-RA AS

A935 MFS Alarm definition format

IMT alarm messages

3BK 20417 AAAA PCZZA Ed.09 11 / 146

1 Introduction

1.1 OverviewThis alarm dictionary provides additional information that is not displayed in thealarm messages sent to the terminals.

The dictionary contains alarm definitions for each alarm type producedby the A935 MFS.

Each definition describes the:

Alarm definition

Alarm description

Impacts on System and Telecom

Methods for further fault isolation

Corrective actions.

12 / 146 3BK 20417 AAAA PCZZA Ed.09

1 Introduction

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

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

1.2.1 Object Identification

The Object Identification identifies the resource that raised the alarm.

Object identification gives information about:

The resource type (Object Class)

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

1.2.2 Alarm Type

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

This information is sub-divided into:

eventType (alarm type)

probableCause

perceivedSeverity: gives the severity level of the alarm.

specificProblem: specifies the MFS Q3 specific problem identifier. Table4gives for each identifier (in decimal form) the specific problem field and the

label of the OMC displays.

The following table describes the five eventTypes.

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

3BK 20417 AAAA PCZZA Ed.09 13 / 146

1 Introduction

The following table describes the severity levels.

Severity Level Indicates ...

Critical a serious fault condition which requires immediate corrections. Example:a managed object becomes totally out of service and its capability mustbe restored.

Major a fault condition which requires urgent correction action. Example: severedegradation in the capability of the managed object and its full capabilitymust be restored.

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, before any significant effects havebeen felt. Action should be taken to further diagnose (if necessary) andcorrect the problem in order to prevent it from becoming a more seriousservice affecting fault.

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

Table 2: Alarm Severity Levels

In addition the Object Identification and eventType 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.

14 / 146 3BK 20417 AAAA PCZZA Ed.09

1 Introduction

1.3 IMT Alarm MessagesThe alarms generated by the A935 MFS equipment are displayed at the IMT inthe GPRS Terminal Window. Whenever A935 MFS equipment generates analarm, the alarm lists in the GPRS Terminal Window are updated. The numberof alarms in the appropriate list is incremented by one. Also, if the alarm icon isnot already displayed, it appears next to the impacted list. Optionally a beepercan be sent to sound every time a new alarm is raised.

The IMT operator uses IMT facilities to identify which equipment is responsiblefor the fault. Like the A1353-RA, the IMT also displays alarms groupedaccording to severity levels. This makes it easier for the operator to prioritizehandling of the alarms.

Refer to the IMT on-line help for more information on handling alarms with theIMT. To find a particular alarm definition, use the Advance Search facility inelectronic documentation.

3BK 20417 AAAA PCZZA Ed.09 15 / 146

1 Introduction

Alarm Message Formats The GPRS Terminal Window displays alarms in six lists: the Main list and fivelists based on the severity level of the alarm. Refer to Table 2 for a descriptionof severity levels.

Detailed information on an alarm is displayed in the Alarm Detailed ViewWindow. This Window is described in Table 3.

Refer to Tables 1 and 2 for a description of event types and severity levels.

Field/Button Description

Type The following types are used:

Communication

Processing error

Quality of Service

Environment

Equipment.

Severity The following levels are used:

Critical

Major

Minor

Warning

Indeterminate.

Alarm Label Alarm Description

Additional Text Additional Information

Date Begin Date when alarm was raised

DnCmise DN of source object for alarm

Rack Rack number

Subrack Subrack number

Slot Slot number

Component 1 Additional fault source identifier

Component 2 Additional fault source identifier

Table 3: MFS Alarm Detailed View Window format

16 / 146 3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2 NECTAR Alarms

This chapter contains the NECTAR alarm definitions. The alarms are listedper probable cause.

The impacts are described with regard to the pilot station only, used inactive/standby mode.

The alarm class of all these alarms is NECTAR Circuit Pack.

Communication subsystem failure

IAN error

Version mismatch

Software error

Software program abnormally terminated

Power problem

I/O device error

Equipment malfunction

Adaptor error

Ventilation system failure

Heating/ventilation/cooling system problem

Temperature unacceptable

Storage capacity problem

3BK 20417 AAAA PCZZA Ed.09 17 / 146

2 NECTAR Alarms

Note: For NECTAR alarms :

A defence unit (DU) is a structure of equipment affecting the same functional

service and handled as a unit for fault management (fault confinement anddefence unit global state).

Some alarms may no apply for MFS or SGSN, if they don’t use the

mentioned DU. For example, there is no router for the MFS, so all routeralarms will not occur.

The smallest unit of replacement on-site is the Field Replaceable Unit(FRU). The additional text contains a string with an explanation of the alarm

with, if possible, the list of the accused FRUs with each percentage.

18 / 146 3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2.1 Communication subsystem failure

eventType: Communication

probableCause: Communication subsystem failure

perceivedSeverity: Major

Alarm Description The defence unit associated to this event is a station.

The station cannot be contacted via the terminal concentrator andits remote access.

Impact on System The maintenance commands cannot be executed.

The station availabilityStatus is degraded.

2.1.1 Corrective Actions

Communication

subsystem failure

Is link

operational?

Alarm

solved

Contact

System Support

no

yes

External

router link

operational?

no

yes

Replace/repair

terminal/station link

On−site

Replace/repair

external router link

On−site

Link terminal

concentrator to station

operational

no

yes

Contact

System Support

Station

is

locked?

no

yesUnlock

station

Figure 1: Communication subsystem failure: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 19 / 146

2 NECTAR Alarms

2.2 IAN error


probableCause: IAN error

perceivedSeverity: If the alarm is on a station:Minor

If the alarm is on a LSN:Major

Alarm Description The defence unit associated to this event is a LSN or a station.

If the alarm is on a station:

The station cannot contact all stations (one for MFS) via this Hub.

If the alarm is on a LSN:

At least one station cannot communicate on a LSN link.

Impact on System In case of a station:

O&M service is interrupted because of the control stationswitchover. The O&M service is not secured

the station availabilityStatus is degraded

In case of a LSN its availabiltyStatus is failed

There is no impact on the telecom service.

20 / 146 3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms


IAN error

Is link

operational?

Alarm

solved

Contact

System Support

no

yes

Coupler

of station

faulty?

no

yes

Replace/repair

link station to

LSN Hub

Station

Replace

coupler

Station

Link between

station and LSN Hub

operational?

no

yes

Hub power

supply

operational?

no

yes

Establish

correct Hub

power supply

Hub

Link &

network

operational?

no

yes

Establish

correct link &

network

Hub

Contact

System Support

Figure 2: IAN error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 21 / 146

2 NECTAR Alarms

2.3 Version mismatch

eventType: ProcessingError

probableCause: Version mismatch

perceivedSeverity: Critical

Alarm Description A station cannot be installed by NECTAR because the correct versionon the active station is not found on the standby station.

Impact on System The control station switchover was at software version change, so thereis no O&M impact (the software is installed on the standby station).

The standby pilot station is not started and so the O&M service is notsecured.

The station availabilityStatus is failed.



Version mismatch

Alarm

solved

Contact

System Support

Installed

correct software

version?

no

yes

Re−install

correct version

Figure 3: Version mismatch: Corrective Actions

22 / 146 3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2.4 Software error


probableCause: Software error


Alarm Description The station cannot be installed by NECTAR because the station failsduring the initialization or the FLT program cannot be executed.

Impact on System The control station switchover has been made at software versionchange, so no O&M impact (the software is installed on the standbystation).

The standby pilot station is not initialized, so the O&M service is notsecured anymore in case of the pilot station.

The station availabilityStatus is failed.


3BK 20417 AAAA PCZZA Ed.09 23 / 146

2 NECTAR Alarms


Software error

Alarm

solved

Contact

System Support

Installed

correct software

version?

no

yes

Error

occures during

normal

working?

no

yes

Verify that the station has

not been stopped voluntarily

(by a third party)

Software

error

solved?

Alarm

solved

Contact

System Support

no

yes

Analyze the Nectar logs and

the application logs

Reinstall the local disk

Verify the two hubs/switches

Re−install correct version of

UNIX, NECTAR, application

Figure 4: Software error: Corrective Actions

24 / 146 3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2.5 Software program abnormally terminated


probableCause: Software program abnormally terminated

perceivedSeverity: Warning

Alarm Description: NECTAR has detected the failure of a station. This alarm occurs duringthe station re-initialization.

Impact on System: O&M service was interrupted because of the control station switchover.

This station is temporarily not available. The restart is normally inprogress.

Station availabilityStatus: OK.

Impact on the telecom service: None.


None. The station is down, but the automatic restart is in progress. Checkthe log of the station to know the cause of failure.

3BK 20417 AAAA PCZZA Ed.09 25 / 146

2 NECTAR Alarms

2.6 Power problem

eventType: Equipment

probableCause: Power problem


Alarm Description: The file management has detected a failure of the shared power supply.

The shared disks and the fan trays are powered off.

The station local disk is not ventilated.

Impact on System: The data on the shared disks are not secured. Administrative functionsare not impacted by this error.

Shared disk availabilityStatus: failed.



Power problem

Alarm

solved

Contact

System Support

Shared disk

powered?

no

yes

Establish correct

shared disk

power supply

(switch power on etc)

Subrack

powered?

no

yes

Establish correct

subrack power supply

(switch power on etc)

Alarm

solved

Figure 5: Power problem: Corrective Actions

26 / 146 3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2.7 I/O device error


probableCause: I/O device error

perceivedSeverity: In case of a local disk problem :Major

In case of a shared disk problem:Minor/Major

In case of a terminal server :Minor

Alarm Description: NECTAR has detected a input/output device failure of a local disk , ashared disk, or a terminal server.

Impact on System: In case of a local disk problem:

The station associated to the local disk is stopped. So theadministrative function can be not secured.

The Station availabilityStatus is failed.

In case of a shared disk problem:

The date on the shared disks are not backuped.

The Shared disk availabilityStatus is failed.

In case of a terminal server problem:

Some administrative commands cannot be executed.

If the alarm is on a station, the Terminal Server availabilityStatus isfailed.

There is no Impact on the telecom service.

3BK 20417 AAAA PCZZA Ed.09 27 / 146

2 NECTAR Alarms


I/O device error on:

Alarmsolved

ContactSystem Support

Alarm severity?

MinorMajorReplace local disk, SCSI bus

or coupler

I/O operational?

no

yes

Station

Replace Hub, ethernet link

Hub/terminal or terminal

Terminal concentrator

Replace shared disk, shared−disk box

Replace SCSI bus

Execute disk_recover

to re−synchronize shared disk

Shared disk

SCSIalarm

events?

no

yes Solve SCSI alarm

On−Site

On−Site

On−Site

On−Site

On−Site

Replace SCSI cables

Figure 6: I/O device error: Corrective Actions

28 / 146 3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2.8 Equipment malfunction


probableCause: Equipment malfunction


Alarm Description: This alarm is associated to a return in error of the FLT program.

The Additional_Text contains the FLT error string given in the FLTresult message where the hardware management has replaced theFRU reference code by its administrative name.

Impact on System: O&M service is interrupted because of the control station switchover isnot secure anymore.

The Station availabilityStatus is failed.


3BK 20417 AAAA PCZZA Ed.09 29 / 146

2 NECTAR Alarms


Equipment malfunction

Alarm

solved

Contact

System Support

Replace faulty

FRU given in

additional text:

Router/

Station

operational?

no

yes

On−site

Station reboots

autonomously,

After reboot station

should be

" unlocked/ disabled/

initializing"

Replace faulty

StorageWorks

shelf

Replace faulty

power supply

Replace faulty

CPU box

On−site On−site On−site

OR OR

Select

the station

Execute

clear_alarm

Figure 7: Equipment malfunction: Corrective Actions

30 / 146 3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2.9 Adaptor error


probableCause: Adaptor error

perceivedSeverity: On a shared disk:Minor

On a station:Major

Alarm Description: If the problem is on a shared disk:

This alarm is associated to a non response of gem chip component inthe shared disk box

On a station:

This alarm is associated associated to access error on shared SCSIbus.

Impact on System: On a station: The station is not stopped, but the access to the data onthe shared disks cannot be secured.

Station availabilityStatus: Degraded.

On a shared disk (GEM chip): The whole system is available but thetemperature and the power supply of the shared disks are not checked.

Impact on telecom service: None.

3BK 20417 AAAA PCZZA Ed.09 31 / 146

2 NECTAR Alarms


Adaptor error

on:

Alarm

solved

Contact

System Support

Reboot

the station

Adaptor

operational?

no

yes

Station

Replace

GEM chip

Replace SCSI

coupler

Shared disk

SCSI

coupler

operational?

no

yes

Replace SCSI coupler,

SCSI cable or CPU box

as given by FLT result

GEM

chip

operational?

no

yes

Replace SCSI

cable

SCSI

cable

ok?

no

yes

Contact

System Support

Alarm

solved

Adaptor

operational?

no

yes

Figure 8: Adaptor error: Corrective Actions

32 / 146 3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2.10 Ventilation system failure

Note: For AS 800 only. This alarm is not relevant for the DS10 server.


probableCause: Ventilation system failure


Alarm Description: Two fans of a fan tray are failed.

Impact on System: The system is available but shared disks and local disks are not cooled.


Ventilation system

failure

Alarm

solved

Contact

System Support

Adaptor

operational?

no

yes

establish correct

fan tray power

supply

Replace

fan tray

Fan tray

power supply

operational?

no

yes

Figure 9: Ventilation system failure: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 33 / 146

2 NECTAR Alarms

2.11 Heating/ventilation/cooling system problem



probableCause: Heating/Ventilation/Cooling System problem

perceivedSeverity: On a station:Critical

On a shared disk:Minor

Alarm Description: If the problem is on a station:

The system has detected a fan failure so the station is automaticallypowered off.

If the problem is on a shared disk: The file management has detecteda fan failure in a fan tray.

Impact on System: On a station: The station is powered off by the system. The O&Mservice is interrupted due to a control station switchover, and it is notsecured anymore.

Station availabilityStatus: Failed.

On a shared disk: The system is available but only one fan in the fantray is available.



Heating/ventilation/cooling

system problem on:

Alarm

solved

Contact

System Support

Replace PCI

fan or CPU fan

Fan

operational?

no

yes

Station

Replace

fan tray

Shared disk

Figure 10: Heating/ventilation/cooling system problem: Corrective Actions

34 / 146 3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2.12 Temperature unacceptable

eventType: Environment

probableCause: Temperature unacceptable

perceivedSeverity: Minor/Critical

Alarm Description: NECTAR detects an unacceptable temperature. For the firsttemperature level, the system is available (alarm: Minor). For thesecond temperature level, the system is stopped (alarm: Critical).

Impact on System: If the severity is Critical, the faulty system is stopped. The stationavailabilityStatus is failed. Then, on a station: The O&M serviceis interrupted due to a control station switchover, it is not securedanymore.

Then, on a shared disk: Data are not secured anymore.


3BK 20417 AAAA PCZZA Ed.09 35 / 146

2 NECTAR Alarms


Temperature

unacceptable

Alarm

solved

Contact

System Support

Replace

PCI fan

or CPU fan

Temperature

acceptable?

no

yes

Station

Replace

fan tray

Shared disk

Room

temperature

too high?

no

yesReduce room

temperature

Temperature

sensor

ok?

no

yes

Replace

temperature

sensor

Fan tray

operational?

no

yes

PCU/CPUfan

operational?

no

yes

Contact

System Support

Contact

System Support

Figure 11: Temperature unacceptable: Corrective Actions

36 / 146 3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2.13 Storage capacity problem

eventType: Processing Error

probableCause: Storage capacity problem

perceivedSeverity if thresholdreached:

Warning

perceivedSeverity if disk full: Critical

Alarm Description: This is a warning alarm in a log. It means that a threshold has beenreached.

A Critical alarm in a log means that the disk is full.

Impact on System: If a threshold has been reached: No immediate impact.

If the disk is full: It leads to a control station switchover, so the O&Mservice is interrupted during this action. There is no impact on thetelecom service.

Note: This alarm will not appear because the log is not used on MFS.


Storage capacity

problem

Alarm

solved

Contact

System Support

Enough

disk space?

no

yes

Reduce used disk

space (clean disk)

Figure 12: Storage capacity problem: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 37 / 146

2 NECTAR Alarms

38 / 146 3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class


This chapter contains the MFS platform alarm definitions of the GPU/JBETIBorad Alarm class:

PCI System Error

PCI Parity Error

GPU loss of contact

Ethernet error

HDLC auto-test error

MT90820 Matrix auto-test error

MT90823 Matrix auto-test error

BGTCGC auto-test error

BGRECC auto-test error

JGHPI auto-test error

JGGPU2 auto-test error

PLX9080 auto-test error

PLX9054 auto-test error

NGISL2 auto-test error

NGISL3 auto-test error

BGPLTC auto-test error

GT-64161A auto-test error

Ethernet auto-test error

DSP auto-test error

DSP error

Framer auto-test error

3BK 20417 AAAA PCZZA Ed.09 39 / 146


Time base clock error (SGSN only)

Free run mode

Applique presence

40 / 146 3BK 20417 AAAA PCZZA Ed.09


3.1 PCI System Error




specificProblem (decimal): 1004097

Alarm Description: A system error has been detected on the PCI bus.

Impact on System: The traffic on the failed GPU is interrupted and GPU goes disabled.There is a switchover on the spare GPU.

There is no impact except for JBETI slot4. If JBETI slot 4 is disabled,there are no converter and fan alarms. The JBETI goes disabled.

BSS Cells O&M Capabilities

Loss # (GPU)

- (JBETI)

# (GPU)

- (JBETI)

-

Degradation - - - (GPU)

(JBETI)

# = if no switchover


PCI System Error

Alarm on

this JBETI

cleared?

Alarm

solved

Contact

System Support

no

Replace

JBETI

On−site

yes

Figure 13: PCI System Error: Corrective Actions for JBETI

3BK 20417 AAAA PCZZA Ed.09 41 / 146


PCI System Error

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

no

Replace

GPU

On−site

yes

Figure 14: PCI System Error: Corrective Actions for GPU

42 / 146 3BK 20417 AAAA PCZZA Ed.09


3.2 PCI Parity Error





Alarm Description: A data parity error has been detected on PCI bus.

Impact on System: The traffic on the failed GPU is interrupted and the GPU goes disabled.There is a switchover on the spare GPU.

There is no impact except for JBETI slot4. If JBETI slot 4 is disabled,there are no converter and fan alarms. The JBETI goes disabled.


Loss # (GPU)

- (JBETI)

# (GPU)

- (JBETI)

-

Degradation - - - (GPU)

(JBETI)


3BK 20417 AAAA PCZZA Ed.09 43 / 146



PCI Parity Error

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

no

Replace

GPU

On−site

yes

Reset all

GPU boards

by pushbotton

or via IMT

On−site

Alarm on

GPU

cleared?

no

yes Alarm

solved

Figure 15: PCI Parity Error: Corrective Actions for GPU

44 / 146 3BK 20417 AAAA PCZZA Ed.09


PCI Parity Error

Alarm on

this JBETI

cleared?

Alarm

solved

Contact

System Support

no

Replace

JBETI

On−site

yes

Reset all

GPU boards

by pushbotton

or via IMT

On−site

Alarm on

GPU

cleared?

no

yesAlarm

solved

Figure 16: PCI Parity Error: Corrective Actions for JBETI

3BK 20417 AAAA PCZZA Ed.09 45 / 146


3.3 GPU loss of contact





Alarm Description: The GEM chip has lost the Communication Service with the GPU, butJBETI has not detected a loss of contact. The GPU is still present,but in failure.

Impact on System: If it is a software problem, the GPU is reset-data. If it does not restart,it goes disabled.

If it is a hardware problem, there is a switchover to the redundant GPU,if possible. GPU goes disabled. Otherwise, same as for softwareproblem.

All supported GPRS telecom resources will go disabled/failed if theGPU goes disabled, with no switchover.

CircuitSwitched traffic may be interrupted if it is a hardware problem,with no switchover.


Loss # # -

Degradation - - -


46 / 146 3BK 20417 AAAA PCZZA Ed.09



GPU loss of contact

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

no

Replace

GPU

On−site

yes

Is

GPU

disabled?

no

yes Is

GPU

restarted?

no

yes

Check

software

versions

OMC−R

Re−install

correct

software

version(s)

OMC−R

Alarm on

this GPU

cleared?

no

yes

Contact

System Support

Alarm

solved

Alarm

solved

Figure 17: GPU loss of contact: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 47 / 146


3.4 Ethernet error


probableCause: Ianerror

perceivedSeverity: Minor


Alarm Description: One Ethernet link with GPU board is out of service.

Impact on System: The communication between the control station and the GPU isdegraded.


Loss - - -

Degradation - -

48 / 146 3BK 20417 AAAA PCZZA Ed.09



Have

all GPUs alarms,

but no JBETI

alarms’?

Is

Ethernet Link 1

unplugged?

Ethernet error

Replugg unit

On−site

yes

Alarm on

this GPU

cleared?

yes

Component1

=1 =>

Termination

unit 1

Component1

=2 =>

Termination

unit 2

Has

GPU Ethernet

auto−test

alarm?

Replace GPU

Have

all GPUs alarm

’JBETI loss

of contact’?

Replace Hub

Replace BATTU

Replace GPU

Replace Hub

Alarm

solved

Contact

System Support

Alarm on

this GPU

cleared?

no

yes

yes

On−site

On−site

On−site

On−site

no

no

no

no

yes

yes

no

On−site

Alarm

solved

Figure 18: Ethernet error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 49 / 146


3.5 HDLC auto-test error





Alarm Description: An auto-test discovered a problem on the HDLC component.

Impact on System: The GPU cannot start and is disabled.

The BSS and cell cannot start, their availabilityStatus remains:not-installed.

The CircuitSwitched traffic cannot start.


Loss -

Degradation - - -


HDLC auto−test error

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

no

Replace

GPU

On−site

yes

Figure 19: HDLC auto-test error: Corrective Actions

50 / 146 3BK 20417 AAAA PCZZA Ed.09


3.6 MT90820 Matrix auto-test error





Alarm Description: An auto-test discovered a problem on the matrix MT90820.

Impact on System: The GPU goes disabled and there is a switchover to the spare GPU.

GPRS impact : outage during the switchover.

CircuitSwitched Impact : None.

Comments This alarm can occur only on GPU2.


Loss -

Degradation - - -


MT90820 auto−test error

Alarm on this GPUcleared?

Alarmsolved


no

Replace GPU

On−site

yes

Triggerswitchover

Figure 20: MT90820 Matrix auto-test error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 51 / 146


3.7 MT90823 Matrix auto-test error





Alarm Description: An auto-test discovered a problem on the matrix MT90823 component.




Comments This alarm can occur only on GPU2 variant AC.


Loss -

Degradation - - -


Matrix auto−test error

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

no

Replace

GPU

On−site

yes

Figure 21: MT90823 Matrix auto-test error: Corrective Actions

52 / 146 3BK 20417 AAAA PCZZA Ed.09


3.8 BGTCGC auto-test error





Alarm Description: An auto-test discovered a problem on the BGTCGC component.


The BSS and cell cannot start, their availabilityStatus remain not-installed.



Loss -

Degradation - - -


BGTCGC auto−test error

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

no

Replace

GPU

On−site

yes

Figure 22: BGTCGC auto-test error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 53 / 146


3.9 BGRECC auto-test error





Alarm Description: An auto-test discovered a problem on the BGRECC component.


The BSS and cell cannot start, their availabilityStatus remains not-installed.



Loss -

Degradation - - -


BGRECC auto−test error

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

no

Replace

GPU

On−site

yes

Figure 23: BGRECC auto-test error: Corrective Actions

54 / 146 3BK 20417 AAAA PCZZA Ed.09


3.10 JGHPI auto-test error





Alarm Description: An auto-test discovered a problem on the JGHPI.




Comments This alarm can occur only on GPU2.


Loss -

Degradation - - -


JGHPI auto−test error


Alarmsolved


no

Replace GPU

On−site

yes

Triggerswitchover

Figure 24: JGHPI auto-test error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 55 / 146


3.11 JGGPU2 auto-test error


probableCause: equipmentMalfunction



Alarm Description: An auto-test discovered a problem on the JGGPU2 component.


GPRS impact : outage during the switchover .


Comments This alarm can occur only on GPU2 variant AC.


Loss -

Degradation - - -


JGGPU2 auto−test error


Alarmsolved


no

Replace GPU

On−site

yes

Triggerswitchover

Figure 25: JGGPU2 auto-test error: Corrective Actions

56 / 146 3BK 20417 AAAA PCZZA Ed.09


3.12 PLX9080 auto-test error





Alarm Description: An auto-test discovered a problem on the PLX9080.




Comments This alarm can only occur on GPU2.


Loss -

Degradation - - -


PLX9080 auto−test error


Alarmsolved


no

Replace GPU

On−site

yes

Triggerswitchover

Figure 26: PLX9080 auto-test error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 57 / 146


3.13 PLX9054 auto-test error





Alarm Description: An auto-test discovered a problem on the PLX9054 component.




Comments This alarm can only occur on GPU2 variant AC.


Loss -

Degradation - - -


PLX9054 auto−test error


Alarmsolved


no

Replace GPU

On−site

yes

Triggerswitchover

Figure 27: PLX9054 auto-test error: Corrective Actions

58 / 146 3BK 20417 AAAA PCZZA Ed.09


3.14 NGISL2 auto-test error





Alarm Description: An auto-test discovered a problem on the NGISL2 component.






Loss -

Degradation - - -


NGISL2 auto−test error


Alarmsolved


no

Replace GPU

On−site

yes

Triggerswitchover

Figure 28: NGISL2 auto-test error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 59 / 146


3.15 NGISL3 auto-test error





Alarm Description: An auto-test discovered a problem on the NGISL3 component.


GPRS impact : outage during the switchover .




Loss - - -

Degradation - -


NGISL3 auto−test error


Alarmsolved


no

Replace GPU

On−site

yes

Triggerswitchover

Figure 29: NGISL3 auto-test error: Corrective Actions

60 / 146 3BK 20417 AAAA PCZZA Ed.09


3.16 BGPLTC auto-test error





Alarm Description: An auto-test discovered a problem on the BGPLTC component.






Loss -

Degradation - - -


BGPLTC auto−test error


Alarmsolved


no

Replace GPU

On−site

yes

Triggerswitchover

Figure 30: BGPLTC auto-test error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 61 / 146


3.17 GT-64161A auto-test error





Alarm Description: An auto-test discovered a problem on the GT-64161A component.


GPRS impact: outage during the switchover .




Loss -

Degradation - - -


GT−64161A auto−test error


Alarmsolved


no

Replace GPU

On−site

yes

Triggerswitchover

Figure 31: GT-64161A auto-test error: Corrective Actions

62 / 146 3BK 20417 AAAA PCZZA Ed.09


3.18 Ethernet auto-test error


probableCause: Ianerror



Alarm Description: An auto-test discovered a problem on one GPU Ethernet component.

Impact on System: The GPU can start, but communication between the control station andthe GPU is degraded, and it is not secure anymore.


Loss - - -

Degradation - - -

3BK 20417 AAAA PCZZA Ed.09 63 / 146



Ethernet auto−test error

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

no

Replace

GPU

On−site

yes

Trigger

switchover

Component1

=1 =>

Termination

unit 1

Component1

=2 =>

Termination

unit 2

Figure 32: Ethernet auto-test error: Corrective Actions

64 / 146 3BK 20417 AAAA PCZZA Ed.09


3.19 DSP auto-test error


probableCause: Processor problem



Alarm Description: An auto-test discovered a problem on the DSP.

Impact on System: A GPU start goes on, there is no impact.

If the DSP has a software loaded, there will probably be a DSP erroralarm later on, on which the operator has to react.


Loss - - -

Degradation - - -


None.

3BK 20417 AAAA PCZZA Ed.09 65 / 146


3.20 DSP error


probableCause: Processor problem



Alarm Description: The DSP is offline.


The GPRS traffic is interrupted during the GPU switchover.


Loss # # -

Degradation - - -



DSP error

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

no

Replace

GPU

On−site

yes

Figure 33: DSP error: Corrective Actions

66 / 146 3BK 20417 AAAA PCZZA Ed.09


3.21 Framer auto-test error





Alarm Description: An auto-test discovered a problem on the Framer component. Startgoes on.

Impact on System: A GPU start goes on, but four PCM-TTPs will be disabled.


Loss # # -

Degradation # # -

# = due to the PCM failure


Framer auto−test error

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

no

Replace

GPU

On−site

yes

Figure 34: Framer auto-test error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 67 / 146


3.22 Time base clock error (SGSN only)


probableCause: not relevant



Alarm Description: All synchronizing PCM are lost on SGSN first synchronizing GPU.

Impact on System: There is an automatic switching of all GPUs on another synchronizingGPU.


Loss - - -

Degradation - - -


None.

68 / 146 3BK 20417 AAAA PCZZA Ed.09


3.23 Free run mode


probableCause: LossOfSynchronisation



Alarm Description: MFS case:

There is no longer a synchronizing PCM on the GPU. The GPU isautomatically switched to free run mode, using the local oscillator.

The alarm is per individual GPU.

SGSN case:

All synchronizing GPUs have lost all their synchronizing PCM. So allGPU switch into free run mode, using the local oscillator.

The alarm is on all synchronizing GPUs.

Impact on System: The transmission quality on the PCM becomes degraded, assynchronization is lost on frames.


Loss -

Degradation - -

3BK 20417 AAAA PCZZA Ed.09 69 / 146



Free run mode

Does Sync. PCM recover?

Alarmsolved


Replace GPU

On−site

yes

First check for & solve otherPCM alarms (AIS;LOS,..)

Congigure new sync. PCM for

GPU

MFS only: add Gb PCM to Transcoder or

SGSN

PCM in service?

PCM in service?yes

yes

no

no

no

Alarmsolved

Alarmsolved

Are TX and RX cables crossed ?

yes

no

Alarmsolved

At GPU Siteor

at Peer Entity Side

Figure 35: Free run mode: Corrective Actions

70 / 146 3BK 20417 AAAA PCZZA Ed.09


3.24 Applique Presence


probableCause: BackPlaneFailure



Alarm Description: The JAE1 is not present.

Impact on System: There is no traffic available for the associated GPU board. PCMare disabled. The board is still enabled but all its associated radioresources will go or remain disabled.


Loss -

Degradation - - -


Applique presence

Alarm on

assoc. GPU

cleared?

Alarm

solved

Contact

System Support

no

Insert

JAE1

On−site

yes

Figure 36: Applique presence: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 71 / 146


72 / 146 3BK 20417 AAAA PCZZA Ed.09

4 PCM-TTP Alarm Class


This chapter contains the MFS platform alarm definitions of the PCM -TTPAlarm class

LOS

LFA

AIS

CH0–EERH

RAI

DFM

CRC4–BERH

CRC4–BERL.

3BK 20417 AAAA PCZZA Ed.09 73 / 146


4.1 LOS


probableCause: LossOfSignal

RemoteAlarmInterface

AIS

LossOfFrame



Alarm Description: The PCM link between transceiver and receiver is broken.

If several PCM-TTPs of the same GPU are affected by transmissionalarms, the JAE1 can be faulty.

Impact on System: The PCM-TTP becomes disabled (no more traffic).

If it is an Ater or Gb PCM-TTP, the related BSS and cells GPRS serviceis degraded (bandwith is reduced).


Loss - - -

Degradation -

74 / 146 3BK 20417 AAAA PCZZA Ed.09



LOS


AlarmsolvedContact

System Support

no

yes

IsPCM Link unplugged?

RepluggPCM link

On−site

yes

Is line in service?

Check peer entities,

repeaters etc.

yes

no

no

Alarm is on more than

2 PCM−TTP?Replace JAE

yes

On−site

no

At peer site



yes Alarmsolved

At GPU Siteor

at Peer Entity Side

Figure 37: LOS: Corrective Actions

If the alarm is appearing on 2 or more PCM-TTPs, suspect JAE1 to be faulty.

The alarm is cleared at problem resolution, when PCM-TTP goes back intoservice, automatically.

The alarm is also cleared at GPU extraction or setting the PCM-TTP alarmfiltering (locking the 2MbTTP on Q3 interface).

3BK 20417 AAAA PCZZA Ed.09 75 / 146


4.2 LFA


probableCause: LossOfFrame



Alarm Description: Multiple LFAs have been detected.

Impact on System: The PCM-TTP is disabled (no more traffic).

If it is an Ater or Gb PCM-TTP, related BSS and cells GPRS service isdegraded (bandwith is reduced).


Loss - - -

Degradation -


LFA

Alarm on

this GPU

cleared?

Alarm

solvedContact

System Support

no

yes

Is line in service?

Check

peer entities,

repeaters etc.

yes

no

Alarm:

Applique

Presence

on

GPU?

Solve Alarm

Applique

Presence

yes

no

At peer site

Contact

System Support

Figure 38: LFA: Corrective Actions

The alarm is also cleared at GPU extraction or setting PCM-TTP alarm filtering(locking the 2MbTTP on Q3 interface).

76 / 146 3BK 20417 AAAA PCZZA Ed.09


4.3 AIS


probableCause: AIS



Alarm Description: There are two or less ZEROs in each two successive double frameperiods.

The peer entity has emission problems.




Loss - - -

Degradation -


AIS

Alarm is

solved when peer entity

is back in service

Check peer

entities,

repeaters etc.

At peer site

Figure 39: AIS: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 77 / 146


4.4 CH0–EERH


probableCause: ExcessiveBER



Alarm Description: BER 10-3: The excessive error rate is ≥ 64 errors in 1 s.




Loss - - -

Degradation -


BER 10−3

Alarm is

solved when peer entity

is back in service

Check peer

entities,

repeaters etc.

At peer site

Figure 40: CH0–EERH: Corrective Actions

78 / 146 3BK 20417 AAAA PCZZA Ed.09


4.5 RAI


probableCause: RemoteAlarmInterface



Alarm Description: The MFS has received a RAI-remote alarm indication, sent by the peerentity, signaling an emission problem (remote equipment understandsnothing). This is temporized for 100 ms.




Loss - - -

Degradation -

3BK 20417 AAAA PCZZA Ed.09 79 / 146



RAI

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

yes

Other

relating alarms

(DFM etc.)?

Solve

that alarms

yes

Force

switchover

no

Replace GPU

Reset−data

GPU

no

Alarm on

this GPU

cleared?

yes

no

Alarm

solved

Figure 41: RAI: Corrective Actions

80 / 146 3BK 20417 AAAA PCZZA Ed.09


4.6 DFM


probableCause: TransmitFailure



Alarm Description: There is a problem on JAE1 component or PCM is connected toground. This is equivalent to LOS but on emission.

Impact on System: The emission traffic on PCM is interrupted.

There is also an RAI alarm on this PCM-TTP.

This alarm may be on four PCM-TTP simultaneously.



Loss - - -

Degradation -

3BK 20417 AAAA PCZZA Ed.09 81 / 146



DFM


Alarmsolved


no

yes

IsPCM Link unplugged?

RepluggPCM link

On−site

yes

Is line in service?

Check peer entities, repeaters etc.

yes

no

no

Replace JAE

On−site

At peer site


yes Alarmsolved

At GPU Siteor

at Peer Entity Side

Figure 42: DFM: Corrective Actions

Alarm is cleared at problem resolution, when PCM is automatically broughtback into service.

Alarm is also cleared at GPU extraction or setting PCM-TTP alarm filtering(locking the 2MbTTP on Q3 interface).

82 / 146 3BK 20417 AAAA PCZZA Ed.09


4.7 CRC4–BERH


probableCause: DegradedSignal



Alarm Description: BER 10-4: The excessive error rate is ≥ 51 errors in 1 s, only withCRC4.

Impact on System: The traffic on PCM is perturbed.



Loss - - -

Degradation -


BER 10−6

Alarm is solved

when peer entity

is back in service

Check

peer entities,

repeaters etc.

At peer site

Figure 43: CRC4–BERH: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 83 / 146


4.8 CRC4–BERL


probableCause: DegradedSignal



Alarm Description: BER 10-6: The excessive error rate is ≥ 100 errors in 1 min, only withCRC4.

Impact on System: The traffic on PCM is perturbed. If it is an Ater or Gb PCM-TTP, relatedBSS and cells GPRS service is degraded (bandwith is reduced).


Loss - - -

Degradation -


BER 10−6

Alarm is solved

when peer entity

is back in service

Check

peer entities,

repeaters etc.

At peer site

Figure 44: CRC4–BERL: Corrective Actions

84 / 146 3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class


This section contains the MFS platform alarm definitions of the SUB -Rackalarm class.

Board alarms

JBETI contact alarms

GEM Subrack alarms

Subrack alarms, detected by JBETI:

JBETI address error

Fan problem

Temperature problem

48V alarm

TRU alarms:

PRE48 alarm

CALVREF alarm

ACP1 alarm

Hub converter alarm

CNVR alarm

JAETI 2.1 V alarm

External alarms No. 1 to No. 8.

3BK 20417 AAAA PCZZA Ed.09 85 / 146


5.1 Board Ethernet error at initialization phase





Alarm Description: The Ethernet #1 and #2 internal loopback test has failed in boot phase.Board cannot start.

Impact on System: There is no impact except for slot 4. If JBETI slot 4 cannot start, therewill be no converter and fan alarms.

If this happens at board plug-in, the GPU/JBETI object is not createdfor this board, as it cannot start.

No telecom impact, as board cannot start.


Loss - - -

Degradation - - -


Board Ethernet error at

initialization phase

Alarm on

this JBETI

cleared?

Alarm

solved

Contact

System Support

no

Replace

JBETI

(given in

Component1)

On−site

yes

Figure 45: Board Ethernet error at initialization phase: Corrective Actions

If this happens at board plug-in, the alarm is cleared when a new board thatstarts properly is plugged in the same slot.

86 / 146 3BK 20417 AAAA PCZZA Ed.09


5.2 Board firmware updated part error





Alarm Description: The checksum test on updated part of firmware has failed.

Impact on System: There is no impact except for slot4. If JBETI slot 4 cannot start, therewill be no converter and fan alarms.




Loss - - -

Degradation - - -


Board firmware

updated part error

Alarm on

this JBETI

cleared?

Alarm

solved

Contact

System Support

no

Replace

JBETI

(given in

Component1)

On−site

yes

Figure 46: Board firmware updated part error: Corrective Actions


3BK 20417 AAAA PCZZA Ed.09 87 / 146


5.3 Board firmware permanent part error





Alarm Description: The checksum test on permanent part of firmware has failed.





Loss - - -

Degradation - - -


Board firmware

permanent part error

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

no

Lock/Replace

GPU

On−site

yes

Figure 47: Board firmware permanent part error: Corrective Actions

88 / 146 3BK 20417 AAAA PCZZA Ed.09


5.4 Board DRAM error





Alarm Description: The DRAM firmware part test has failed.





Loss - - -

Degradation - - -

3BK 20417 AAAA PCZZA Ed.09 89 / 146



Board DRAM error

Alarm on

this JBETI

cleared?

Alarm

solved

Contact

System Support

Reset JBETI

(given in

component1)

On−site

yes

Replace JBETI

no

Alarm on

this JBETI

cleared?

yes

no

On−site

Alarm

solved

Figure 48: Board DRAM error: Corrective Actions


90 / 146 3BK 20417 AAAA PCZZA Ed.09


5.5 Board ECC test error during boot phase





Alarm Description: There is an ECC error (MCP) during boot processing.





Loss - - -

Degradation - - -


Alarm on

this JBETI

cleared?

Alarm

solved

Contact

System Support

no

Replace

JBETI (given in

component1)

On−site

yes

Board ECC test error

during boot phase

Figure 49: Board ECC test error during boot phase: Corrective Actions


3BK 20417 AAAA PCZZA Ed.09 91 / 146


5.6 Board target abort during boot phase





Alarm Description: The target aborted (MCP) during boot processing.





Loss - - -

Degradation - - -


Alarm on

this JEBTI

cleared?

Alarm

solved

Contact

System Support

no

Replace

JBETI (given in

component1)

On−site

yes

Board target abort

during boot phase

Figure 50: Board target abort during boot phase: Corrective Actions


92 / 146 3BK 20417 AAAA PCZZA Ed.09


5.7 Unlocked board deletion alarm





Alarm Description: The GPU has been extracted without being locked.

Impact on System: Telecom traffic (GPRS and Circuit Switched) has been interrupted onthis GPU. All telecom resources that were supported by this boardhave now a not-installed availabilityStatus.


Loss -

Degradation - - -


Unlocked board

deletion alarm

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

no

Re−Plugg/

Replace

GPU

On−site

yes

Figure 51: Unlocked board deletion alarm: Corrective Actions

The alarm is cleared when a JBETI that starts properly is plugged in slot 4.

3BK 20417 AAAA PCZZA Ed.09 93 / 146


5.8 JBETI slot4 loss of contact





Alarm Description: The contact with JBETI slot4 is lost.

Impact on System: If unplugged, there is a loss of converter and fan alarms. So O&Mservice (subrack supervision) is degraded.


Loss - - -

Degradation - -


JBETI slot4

loss of contact

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

no

Re−Plugg

JBETI

On−site

yes

JBETI

slot4

unplugged?

no

yes

JBETI

slot4

faulty?

no

yesReplace

JBETI

On−site

Contact

System Support

Figure 52: JBETI slot4 loss of contact: Corrective Actions

94 / 146 3BK 20417 AAAA PCZZA Ed.09


5.9 JBETI slot23 loss of contact





Alarm Description: The contact with JBETI slot23 is lost.

Impact on System: There is no impact.


Loss - - -

Degradation - - -


JBETI slot23

loss of contact

Alarm on

this GPU

cleared?

Alarm

solved

Contact

System Support

no

Re−Plugg

JBETI

On−site

yes

JBETI

slot23

unplugged?

no

yes

JBETI

slot23

faulty?

no

yesReplace

JBETI

On−site

Contact

System Support

Figure 53: JBETI slot23 loss of contact: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 95 / 146


5.10 No JBETI on subrack


probableCause: ReplaceableUnitMissing



Alarm Description: There is no available JBETI on the subrack.

This alarm occurs at system initialization, for all subracks. This alarmalso occurs on a subrack at each JBETI switchover.

Impact on System: The alarms are cleared; no new alarm is triggered (at least noequipment alarms reported by JBETI) and boards cannot be reset.


Loss - - -

Degradation - - -

96 / 146 3BK 20417 AAAA PCZZA Ed.09



No JEBTI on subrack

Alarm on

this JBETI

cleared?

Alarm

solved

Contact

System Support

no

Solve alarm

Loss of Contact

yes

Is

alarm

transient?

no

yes

Minimum

one

JBETI

in service?

no

yes

Insert

JBETI

On−site

No action

required

Alarm

Loss of Contact

on faulty

JBETI?

no

yes

Replace

JBETI

On−site

On−site

Alarm

solved

Figure 54: No JBETI on subrack: Corrective Actions

The alarm is cleared when the subrack has at least one JBETI plugged andin service.

3BK 20417 AAAA PCZZA Ed.09 97 / 146


5.11 JBETI address error


probableCause: ReplaceableUnitProblem



Alarm Description: The JBETIs on a subrack do not have the same rack/subrack address.

ADR cabling (ADRIN, ADR1, ADR2, ADR3, ADROUT) on JAETIs (thatchain the racks and subracks) fixing JBETI rack/subrack addresses, iswrong.

Impact on System: O&M service is degraded, rack/subrack/slot identifiers in alarmsdescription may be wrong.

A JBETI with an invalid rack/subRack number is disabled.


Loss - - -

Degradation - -

98 / 146 3BK 20417 AAAA PCZZA Ed.09



JBETI address error

Alarm on

this JBETI

cleared?

Alarm

solved

Contact

System Support

no

yes

Is

ADR cabling

correct?

no

yes

Replace

ADRx cable(s)

On−site

Re−do cabling

Is

ADR cabling

faulty?

no

yes

On−site

Contact

System Support

Figure 55: JBETI address error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 99 / 146


5.12 Fan problem


probableCause: CoolingFanFailure



Alarm Description: One or more fan’s problem, or the maintenance key is set, or theBDAFU is unplugged.

Impact on System: The subrack temperature may increase, raising the temperatureproblem alarm.


Loss - - -

Degradation - - -

100 / 146 3BK 20417 AAAA PCZZA Ed.09



Fan problem

Alarm on

this BDAFU

cleared?

Alarm

solved

Contact

System Support

no

yes

Is

maintenance

key set?

no

yes

Replugg

BDAFU

On−site

Unset

maintenance

key

Is

BDAFU

unplugged?

no

yes

On−site

Is

BDAFU

LED

yellow?

no

yes Replace

faulty Fan

On−site

Contact

System Support

Figure 56: Fan problem: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 101 / 146


5.13 Temperature problem


probableCause: HeatingOrVentilationOrCoolingSystemProblem



Alarm Description: At least one temperature sensor has detected a temperature over 65�C.

Impact on System: The subrack power may be cut off. If so, BSS, cells and CircuitSwitched traffic are lost on all subRack GPUs.


Loss

Degradation - - -

102 / 146 3BK 20417 AAAA PCZZA Ed.09



Temperature problem

Alarm on

this subrack

cleared?

Alarm

solved

Contact

System Support

no

yes

Alarm

Fan Problem?

no

yes

Solve GPU

problems

On−site

Solve alarm

Fan Problem

Alarm(s)

on related

GPU(s)?

no

yes

On−site

Switch subrack

power on

On−site

Alarm on

this subrack

cleared?

no

yes

Replace

fan tray

On−site

Figure 57: Temperature problem: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 103 / 146


5.14 48V alarm



probableCause: PowerProblem



Alarm Description: There is a 48V problem for at least one converter.

Impact on System: None. Converters are still in service as power supply is redundant.


Loss - - -

Degradation - - -

104 / 146 3BK 20417 AAAA PCZZA Ed.09



48V alarm

Alarm on

this converter

cleared?

Alarm

solved

Contact

System Support

no

yes

Power input

correct?

no

yes

Solve

PRE48 alarm

On−site

establish

correct

power input

Alarm

PRE48?

no

yes

On−site

Alarm(s) on

relating

converter?

no

yes

Replace

BE35B2

On−site

Contact

System Support

Replace

BA35B2

On−site

Figure 58: 48V alarm: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 105 / 146


5.15 PRE48 alarm





Alarm Description: There is a loss of one -48 V TRU reference signal, -48 VA or -48 VB.

Impact on System: O&M service degraded, as external alarms are no longer visible.


Loss - - -

Degradation - -


PRE48 alarm

Alarm on

this rack

cleared?

Alarm

solved

Contact

System Supportno

yes

BLTLM cable

TRU/JAETI

slot4/23

unplugged?

no

yes

no Establish

correct rack

power supply

On−site

Re−plugg

BLTLM cable

Rack power

supply ok?

yes

On−site

Input power

avaliable?

no

yes

Ensure correct

input power

On−site

Contact

System Support

Figure 59: PRE48 alarm: Corrective Actions

106 / 146 3BK 20417 AAAA PCZZA Ed.09


5.16 CALVREF alarm





Alarm Description: CALVREF: There is no longer the -48V input reference from the topof the rack.

Impact on System: O&M service degraded, as external alarms are no longer visible.


Loss - - -

Degradation - -

3BK 20417 AAAA PCZZA Ed.09 107 / 146



CALVREF alarm

Alarm on

this rack

cleared?

Alarm

solved

Contact

System Support

no

yes

Cable(s)

TRU/JAETI slot4/23

unplugged?

no

yes

noEstablish correct

rack power supply

On−site

Re−plugg

cable(s)

Rack power

supply ok?

yes

On−site

Input power

avaliable?

no

yes

Ensure correct

input power

On−site

Contact

System Support

Figure 60: CALVREF alarm: Corrective Actions

108 / 146 3BK 20417 AAAA PCZZA Ed.09


5.17 ACP1 alarm





Alarm Description: The -48 V input voltage of the rack may be perturbed.

Impact on System: The rack alimentation is perturbed. It may involve converter problemalarms.

O&M service may be degraded, with loss of external alarms.


Loss - - -

Degradation - -


ACP1 alarm

Alarm on

this rack

cleared?

Alarm

solved

Contact

System Support

no

yes

TRU circuit

breakers ok?

no

yes

Replace

precharge

module

On−site

Replace TRU

circuit breakers

On−site

Figure 61: ACP1 alarm: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 109 / 146


5.18 Hub converter problem






Alarm Description: A Hub converter is out of service, or a input of the terminal server isout of service.

Impact on System: None.


Loss - - -

Degradation - - -

110 / 146 3BK 20417 AAAA PCZZA Ed.09



Hub converter problem

Alarm on

this rack

cleared?

Alarm

solved

Contact

System Support

no

yes

JHALA cable(s)

to related converter

unplugged?

no

yes

no Establish

correct Hub

power supply

On−site

Re−plugg JHALA

cable(s)

Related power

supply ok?

yes

On−site

Related

converter faulty?

no

yes Replace related

faulty converter

On−site

Input of terminal

server is out of

service.

On−site

Repair & bring

back terminal

server in service

On−site

Figure 62: Hub converter problem: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 111 / 146


5.19 CNVR converter alarm





Alarm Description: The CNVR output voltage overloads threshold 1 or 2. There is aconverter disjunction.

Impact on System: After several CNVR alarms, the subrack power may be cut off.


Loss - - -

Degradation - - -


CNVR converter alarm

Alarm on

this rack

cleared?

Alarm

solved

Contact

System Support

no

yes

Replace related

faulty converter

On−site

Figure 63: CNVR converter alarm: Corrective Actions

Note: If this alarm occurs after a JBETI reset, do the JBETI reset again.

112 / 146 3BK 20417 AAAA PCZZA Ed.09


5.20 2.1V alarm





Alarm Description: 2.1 V power supply of JAETI is out of service.

Impact on System: The ISL/ICL/RAB/RSCB buses cannot work, so O&M service isdegraded. Switchover of GPU to spare board is not available


Loss - - -

Degradation - -


2.1V alarm

Alarm on

this rack

cleared?

Alarm

solved

Contact

System Support

no

yes

Replace

JAETI

On−site

Figure 64: 2.1V alarm: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 113 / 146


5.21 JAETI Failure (slot 4)





Alarm Description: The JAETI is out of service. The safety fuse can be faulty.

Impact on System: There is no immediate impact, but if a GPU resets, it will not restart.

Switch over of GPU on spare boards is available.

If the control station is restarted, all the GPU will be reset and all willnot restart with an important outage of services.


JAETI Failure

slot 4

Alarm

cleared?

Alarm

solved

Contact

System Support

no

yes

Replace

JAETI

On−site

Reset both

JBETIs

with board switch

On−site

Figure 65: JAETI Failure (slot 4): Corrective Actions

114 / 146 3BK 20417 AAAA PCZZA Ed.09


5.22 JAETI Failure (slot 23)





Alarm Description: The JAETI is out of service.

Impact on System: There is no immediate impact, but if a GPU resets, it will not restart.

Switch over of GPU on spare boards is available.

If the control station is restarted, all the GPU will be reset and all willnot restart with an important outage of services.


JAETI Failure

slot 23

Alarm

cleared?

Alarm

solved

Contact

System Support

no

yes

Replace

JAETI

On−site

Reset both

JBETIs

with board switch

On−site

Figure 66: JAETI Failure (slot 23): Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 115 / 146


5.23 EALM1

eventType: Environmental

probableCause: GsmExternalEquipmentFailure



Alarm Description: This is the external alarm n�1.

Impact on System: The impact depends on the associated alarm (fire, door opened, ...).


Loss - - -

Degradation - - -

116 / 146 3BK 20417 AAAA PCZZA Ed.09



EALM1

External

alarm

cleared?

Alarm

solved

Contact

System Support

no

yes

Trigger action

according to

Additional_Text

On−site

Blind alarm?

no

yes

Sensor

cabling ok?

no

yes

Re−plugg/

replace sensor

cabling

Sensor ok?no

yes

Replace

sensor

On−site

Contact

System Support

Figure 67: EALM1: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 117 / 146


5.24 EALM2 external alarm








Loss - - -

Degradation - - -


EALM2

External

alarm

cleared?

Alarm

solved

Contact

System Support

no

yes

Trigger action

according to

Additional_Text

On−site

Blind alarm?

no

yes

Sensor

cabling ok?

no

yes

Re−plugg/

replace sensor

cabling

Sensor ok?no

yes

Replace

sensor

On−site

Contact

System Support


118 / 146 3BK 20417 AAAA PCZZA Ed.09










Loss - - -

Degradation - - -


EALM3

External

alarm

cleared?

Alarm

solved

Contact

System Support

no

yes

Trigger action

according to

Additional_Text

On−site

Blind alarm?

no

yes

Sensor

cabling ok?

no

yes

Re−plugg/

replace sensor

cabling

Sensor ok?no

yes

Replace

sensor

On−site

Contact

System Support


3BK 20417 AAAA PCZZA Ed.09 119 / 146










Loss - - -

Degradation - - -


EALM4

External

alarm

cleared?

Alarm

solvedContact

System Support

no

yes

Trigger action

according to

Additional_Text

On−site

Blind alarm?

no

yes

Sensor

cabling ok?

no

yes

Re−plugg/

replace sensor

cabling

Sensor ok?no

yes

Replace

sensor

On−site

Contact

System Support


120 / 146 3BK 20417 AAAA PCZZA Ed.09










Loss - - -

Degradation - - -


EALM5

External

alarm

cleared?

Alarm

solved

Contact

System Support

no

yes

Trigger action

according to

Additional_Text

On−site

Blind alarm?

no

yes

Sensor

cabling ok?

no

yes

Re−plugg/

replace sensor

cabling

Sensor ok?no

yes

Replace sensor

On−site

Contact

System Support


3BK 20417 AAAA PCZZA Ed.09 121 / 146










Loss - - -

Degradation - - -


EALM6

External

alarm

cleared?

Alarm

solved

Contact

System Support

no

yes

Trigger action

according to

Additional_Text

On−site

Blind alarm?

no

yes

Sensor

cabling ok?

no

yes

Re−plugg/

replace sensor

cabling

Sensor ok?no

yes

Replace

sensor

On−site

Contact

System Support


122 / 146 3BK 20417 AAAA PCZZA Ed.09










Loss - - -

Degradation - - -


EALM7

External

alarm

cleared?

Alarm

solved

Contact

System Support

no

yes

Trigger action

according to

Additional_Text

On−site

Blind alarm?

no

yes

Sensor

cabling ok?

no

yes

Re−plugg/

replace sensor

cabling

Sensor ok?no

yes

Replace sensor

On−site

Contact

System Support


3BK 20417 AAAA PCZZA Ed.09 123 / 146










Loss - - -

Degradation - - -


EALM8

External

alarm

cleared?

Alarm

solved

Contact

System Support

no

yes

Trigger action

according to

Additional_Text

On−site

Blind alarm?

no

yes

Sensor

cabling ok?

no

yes

Re−plugg/

replace sensor

cabling

Sensor ok?no

yes

Replace

sensor

On−site

Contact

System Support


124 / 146 3BK 20417 AAAA PCZZA Ed.09

6 MFS Telecommunication Alarms


This chapter contains the MFS telecommunication alarm definitions.

Frame Relay Bearer (SGSN and network) alarms

NSVCI and NSEI alarms

PVC DLCI alarms

GSL BSS alarm (B6 only)

GSL and BVCsig BSS alarms

CELL BVC alarm

LapDLink alarm.

3BK 20417 AAAA PCZZA Ed.09 125 / 146


6.1 SGSN in user mode


probableCause: ConfigurationOrCustomizationError

perceivedSeverity Major


Alarm Description: The SGSN sends a status inquiry that indicates that it is also in usermode.

Impact on System: The FRBearer is disabled, it cannot start.

There is no impact on Circui tSwitched traffic.


Loss - - -

Degradation -


None.

It is up to the SGSN to change its configuration.

The alarm is cleared when SGSN sends a status inquiry that indicates that itis in network mode.

126 / 146 3BK 20417 AAAA PCZZA Ed.09


6.2 No response from network


probableCause: TransmissionError



Alarm Description: There is no reply from the network to the status inquiry after a certainnumber of requests.


BSS and cells GPRS service is degraded.

There is no impact on Circuit Switched traffic.


Loss - - -

Degradation -


No response

from network

PCM Alarm

cleared?

Alarm

solved

Contact

System Support

no

yes

PCM cable(s)

unplugged?

no

yes

Solve PCM−TTP

alarm first

On−site

Re−plugg

PCM cable

On−site

Alarm on

related

PCM−TTP?

no

yes

PCM problem must be

solved at peer side

Figure 75: No response from network: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 127 / 146


6.3 No reply from network





Alarm Description: There is no reply from the network to the status inquiry.




Loss - - -

Degradation -


No reply

from network

PCM Alarm

cleared?

Alarm

solved

Contact

System Support

no

yes

PCM cable(s)

unplugged?

no

yes

Solve PCM−TTP

alarm first

On−site

Re−plugg

PCM cable

On−site

Alarm on

related

PCM−TTP?

no

yes

PCM problem must be

solved at peer side

Figure 76: No reply from network: Corrective Actions

128 / 146 3BK 20417 AAAA PCZZA Ed.09


6.4 No reply from SGSN





Alarm Description: The SGSN does not answer an NS-VC procedure.

Impact on System: The NS-VC is disabled



Loss - - -

Degradation -


No reply from SGSN

PCM Alarm

cleared?

Alarm

solved

Contact

System Support

no

yes

PCM cable(s)

unplugged?

no

yes

Solve PCM−TTP

alarm first

On−site

Re−plugg PCM

cable

On−site

Alarm on

related

PCM−TTP?

no

yes

PCM problem must be

solved at peer side

Figure 77: No reply from SGSN: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 129 / 146


6.5 NSEI mismatch





Alarm Description: This alarm is raised when SGSN sends back a wrong NSEI at NS-resetack.

Impact on System: The NS-VC is disabled. Then BSS and cells are degraded. ( )

In fact, all NS-VC will probably be in alarm and disabled, as they sharethe same NSEI. Then BSS and cells are lost. (#)



Loss # # -

Degradation -


NSEI mismatch

SGSN

accepts

NSEI?

Alarm

solved

Contact

System Support

no

yes

Re−configure

NSEI

SGSN side

Delete/create

NSEI with new

NSE

MFS side

Figure 78: NSEI mismatch: Corrective Actions

130 / 146 3BK 20417 AAAA PCZZA Ed.09


6.6 NSVCI mismatch





Alarm Description: The SGSN sends back a wrong NSVCI at NS-reset ack.

Impact on System: The NS-VC is disabled. There is no impact on Circuit Switched traffic.


Loss - - -

Degradation -


NSVCI mismatch

SGSN

accepts

NSVCI?

Alarm

solved

Contact

System Support

no

yes

Re−configure

NS−VC with new

NSVCI

Figure 79: NSVCI mismatch: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 131 / 146


6.7 Inactive DLCI





Alarm Description: The DLCI is inactive in bearer channel status response.

Impact on System: The PVC is disabled, as well as the related NS-VC.



Loss - - -

Degradation -


None.

The PVC fault must be repaired at peer side. The alarm is cleared when thefault is repaired and the DLCI is active in bearer channel status response.

The alarm is also cleared at GPU extraction or loss.

132 / 146 3BK 20417 AAAA PCZZA Ed.09


6.8 Unknown DLCI





Alarm Description: The DLCI is declared as unknown in bearer channel status response.

Impact on System: The PVC is disabled, as well as the related NS-VC.



Loss - - -

Degradation -


None.

The DLCI fault must be repaired at peer side. The alarm is cleared when theDLCI is active in bearer channel status response.


3BK 20417 AAAA PCZZA Ed.09 133 / 146


6.9 GSL out (B6)

eventType: Quality of Service

probableCause: UnderlyingResourceUnavailable

perceivedSeverity Critical

specificProblem (decimal) forRelease B6:

1012289

Alarm Description: The BSS no longer has GSLs.

Impact on System: Signaling with the BSC is impossible. The BSS and its cells aredisabled.



Loss -

Degradation - - -


GSL out

At least

one LapDLink

operational?

Alarm

solved

Contact

System Support

no

yes

LapDLink

locked?

no

yes

Solve PCM−TTP

alarm

On−site

Unlock LapdDLink,

check operational and

administrative State

On−site

Alarm on

related

PCM−TTP?

no

yes

Investigate on LapDLink

at BSC side

Figure 80: GSL out: Corrective Actions (B6)

134 / 146 3BK 20417 AAAA PCZZA Ed.09


6.10 GSL out (B7)





1012295

Alarm Description: The BSS has no more GSL for one GPU.

Impact on System: Signaling with the BSC is impossible. The BSS and its cells aredisabled for on GPU, as well as the cells supported by this GPU. BSSand cells GPRS service is lost for this GPU.



Loss -

Degradation - - -


GSL out

At least

one LapDLink

operational?

Alarm

solved

Contact

System Support

no

yes

LapDLink

locked?

no

yes

Solve

PCM−TTP alarm

On−site

Unlock LapdDLink,



On−site

Alarm on

related

PCM−TTP?

no

yes


at BSC side

Figure 81: GSL out (B7): Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 135 / 146


6.11 BVCSig is broken on (B7)





1012296

Alarm Description: The BSS BVCSig is down for one GPU, probably because the NSEhas no transfer capability.

Impact on System: The BSS and all its cells are disabled for one GPU. BSS and cellsGPRS service is lost for this GPU.



Loss -

Degradation - - -


BVCSig out

At least

one BSC NS−VC

operational?

Alarm

solved

Contact

System Support

no

yes

NS−VC

locked?

no

yes

Solve

PCM−TTP alarm

On−site

Unlock NS−VC,

check its operational and


On−site

Alarm on

related

PCM−TTP?

no

yes

Investigate on NS−VC

at SGSN side

Figure 82: BVCSig is broken on (B7): Corrective Actions

136 / 146 3BK 20417 AAAA PCZZA Ed.09


6.12 BVC out





Alarm Description: The Gb BVC of the cell cannot work.

Impact on System: The cell is disabled. The BSS GPRS service is degraded (one cell islost). The cell GPRS service is lost.



Loss - -

Degradation - -


None. Investigate at SGSN side; it may be faulty.

The alarm will be cleared when the fault disappears.


3BK 20417 AAAA PCZZA Ed.09 137 / 146


6.13 LapDLink disabled


probableCause: LinkFailure



Alarm Description: The LapDLink is disabled.

Impact on System: The LapDLink is disabled. It can be due to:

a LapD protocol failure

stopped remote BSC GPRS traffic as the BSS is locked or disabled

a locked LapDlink

a PCM-TTP transmission problem.

The BSS GSL is no longer secured and has a reduced capacity. Thenthe BSS and the cells GPRS service is degraded ( ).

If it is due to a remote BSC problem, both LapDLinks might be inalarm. Then, the BSS also has a GSL down alarm. The BSS andcells packet-switched is lost (#).

There is no impact for CircuitSwitched traffic.


Loss # # -

Degradation -

138 / 146 3BK 20417 AAAA PCZZA Ed.09



LapDLink disabled

At least

one LapDLink

operational?

Alarm

solved

Contact

System Support

yes

LapDLink

locked?

no

yes

Solve PCM−TTP

alarm

On−site

Unlock LapdDLink,



On−site

Alarm on

related

PCM−TTP?

no

yes


at BSC side

Replace LapDLink

of PCM−TTP

On−site

no

At least

one LapDLink

operational?

yes

no

Alarm

solved

Figure 83: LapDLink disabled: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09 139 / 146


140 / 146 3BK 20417 AAAA PCZZA Ed.09

7 MFS Alarm Additional Information


3BK 20417 AAAA PCZZA Ed.09 141 / 146


7.1 MFS Q3 specific problem identifierThe MFS Q3 specific problem identifier gives for each identifier of alarmId orcomponent, found in decimal form in the specific problem field, the label thatthe OMC displays consistent with the MFS IMT.

specificProblem (decimal) Alarm Label

1004097 PCI System Error

1004098 PCI data Parity Error

1004099 Ethernet#1 and #2 internal loopback test failed in boot phase

1004100 Checksum test on updasted part of firmware failed

1004101 Checksum test on permanent part of firmware failed

1004102 DRAM firmware part test failed

1004103 ECC test error (MCP) during boot phase

1004104 Target abort (MCP) during boot phase

1004105 GPU extracted when not locked

1004113 Address error: JBETIs on a subrack have not the same rack/subrackaddress

1004114 At least one fan failure OR maintenance key is set OR BDAFU2 isunplugged

1004115 At least one temperature sensor has detected a T > 65C

1004116 CNVR: disjunction due to output voltage problem on converter

1004122 48V alarm, at least one converter disjuncted

1004130 2.1V alarm, no more redundancy of GPU boards

1004131 PRE48 alarm, external alarms no more visible

1004135 ACP1 alarm

1004136 CALVREF alarm

1004137 Terminal server 48 V not powered or Hub converter is out of service

1004145 GPU Ethernet error

1004146 GPU loss of contact

1004153 Failure of a JAETI applique (slot 4)

1004154 Failure of a JAETI applique (slot 23)

1004161 JBETI slot4 loss of contact

142 / 146 3BK 20417 AAAA PCZZA Ed.09


1004162 JBETI slot23 loss of contact

1004163 No JBETI on subrack

1006400 EALM1

1006401 EALM2

1006402 EALM3

1006403 EALM4

1006404 EALM5

1006405 EALM6

1006406 EALM7

1006407 EALM8

1012289 BSS GSL is broken (B6)

1012295 BSS GSL is broken on (B7)

1012296 BSS BVCSig is broken on (B7)

1012305 Cell BVC is out

1012321 LapDLink disabled

1016385 DSP offline

1016401 LOS, PCM link transceiver to receiver broken

1016402 LFA, header frame lost

1016403 AIS, no more two zero bits into two successive frames

1016405 BER 10-3

1016406 RAI

1016407 DFM

1016408 BER 10-4

1016409 BER 10-6

1016417 Time base block offline

1016418 Free run mode

1016449 Applique not present

1016450 DSP auto-test error

1016451 Ethernet auto-test error

3BK 20417 AAAA PCZZA Ed.09 143 / 146


1016464 HDLC auto-test error

1016465 Framer auto-test error

1016469 Matrix auto-test error

1016470 BGTCGC auto-test error

1016471 BGRECC auto-test error

1016472 JGHPI auto-test error

1016473 PLX9080 auto-test error

1016480 NGISL2 auto-test error

1016481 BGPLTC auto-test error

1016641 SGSN in user mode

1016642 No reply from network

1016672 No reply from SGSN

1016673 NSEI mismatch

1016674 NSVCI mismatch

1016688 Inactive DLCI

1016689 Unknown DLCI

2000001 component 1

2000002 component 2

2000003 component 3

2000004 component 4

2000005 component 5

2000006 component 6

2000007 component 7

2000008 component 8

2000009 component 9

2000010 component 10




144 / 146 3BK 20417 AAAA PCZZA Ed.09















2001536 Rack 1 Shelf 0 GPU 6
















3BK 20417 AAAA PCZZA Ed.09 145 / 146
















Table 4: MFS Q3 Alarm Identifier

146 / 146 3BK 20417 AAAA PCZZA Ed.09

E-935 Mfs Alarm Dictionary

Documents

Transcript of E-935 Mfs Alarm Dictionary