Alcatel BSS

EVOLIUM A935 MFS Alarm

Dictionary

O&M Documentation
Reference Guide

3BK 20417 AAAA PCZZA Ed.09

BLANK PAGE BREAK

Status

RELEASED

Short title

MFS Alarm Dictionary

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

2 / 146

3BK 20417 AAAA PCZZA Ed.09

Contents

Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2
A1353-RA AS Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3
IMT Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NECTAR Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1
Communication subsystem failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2
IAN error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3
Version mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4
Software error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5
Software program abnormally terminated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6
Power problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7
I/O device error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.8
Equipment malfunction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.9
Adaptor error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.10
Ventilation system failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11
Heating/ventilation/cooling system problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12
Temperature unacceptable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.13
Storage capacity problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GPU/JBETI Boards Alarm Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1
PCI System Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2
PCI Parity Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3
GPU loss of contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4
Ethernet error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5
HDLC auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6
MT90820 Matrix auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7
MT90823 Matrix auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.8
BGTCGC auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.9
BGRECC auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.10
JGHPI auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.11
JGGPU2 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.12
PLX9080 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.13
PLX9054 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.14
NGISL2 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.15
NGISL3 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.16
BGPLTC auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.17
GT-64161A auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.18
Ethernet auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.19
DSP auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.20
DSP error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.21
Framer auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.22
Time base clock error (SGSN only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.23
Free run mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.24
Applique Presence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCM-TTP Alarm Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1
LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2
LFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3
AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4
CH0EERH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5
RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6
DFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7
CRC4BERH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3BK 20417 AAAA PCZZA Ed.09

11
12
13
15
17
19
20
22
23
25
26
27
29
31
33
34
35
37
39
41
43
46
48
50
51
52
53
54
55
56
57
58
59
60
61
62
63
65
66
67
68
69
71
73
74
76
77
78
79
81
83

3 / 146

Contents

4.8
CRC4BERL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
SUB-RACK Alarm Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
5.1
Board Ethernet error at initialization phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
5.2
Board firmware updated part error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
5.3
Board firmware permanent part error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
5.4
Board DRAM error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
5.5
Board ECC test error during boot phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
5.6
Board target abort during boot phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
5.7
Unlocked board deletion alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
5.8
JBETI slot4 loss of contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
5.9
JBETI slot23 loss of contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.10
No JBETI on subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.11
JBETI address error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
5.12
Fan problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
5.13
Temperature problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.14
48V alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5.15
PRE48 alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5.16
CALVREF alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.17
ACP1 alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
5.18
Hub converter problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.19
CNVR converter alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.20
2.1V alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5.21
JAETI Failure (slot 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.22
JAETI Failure (slot 23) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.23
EALM1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.24
EALM2 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5.25
EALM3 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.26
EALM4 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
5.27
EALM5 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
5.28
EALM6 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
5.29
EALM7 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.30
EALM8 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
MFS Telecommunication Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
6.1
SGSN in user mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
6.2
No response from network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
6.3
No reply from network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
6.4
No reply from SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
6.5
NSEI mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
6.6
NSVCI mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
6.7
Inactive DLCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
6.8
Unknown DLCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
6.9
GSL out (B6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
6.10
GSL out (B7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
6.11
BVCSig is broken on (B7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
6.12
BVC out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
6.13
LapDLink disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
MFS Alarm Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
7.1
MFS Q3 specific problem identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

4 / 146

3BK 20417 AAAA PCZZA Ed.09

Figures

Figures
Figure 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: CH0EERH: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Figure 41: RAI: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 42: DFM: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 43: CRC4BERH: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 44: CRC4BERL: 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 68: EALM2: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Figure 69: EALM3: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Figure 70: EALM4: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 71: EALM5: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 72: EALM6: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Figure 73: EALM7: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Figure 74: EALM8: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
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

Tables
Table 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 structured

method for handling MFS alarm messages.

Audience

This document is aimed at telecommunications operators responsible for

performing O&M fault handling and troubleshooting tasks.
This document contains a list of all A935 MFS alarms, and the actions required
to remove them.
The alarms are displayed at the OMC-R terminal and at the IMT to inform the
operator 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 Overview
This alarm dictionary provides additional information that is not displayed in the
alarm messages sent to the terminals.
The dictionary contains alarm definitions for each alarm type produced
by 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 Information

In the A1353-RA OMC-R, Alarm Surveillance provides an efficient means to
control, supervise and manage equipment problems in the MFS.
Alarms or Alarm notifications consist of messages sent by network resources
that have detected problems or failures in the network. These alarms are
displayed in lists while alarm counters keep track of statistics. By clicking on an
alarm in the list, the operator gets detailed information. AS displays information
as described below.

1.2.1 Object Identification

The Object Identification identifies the resource that raised the alarm.
Object identification gives information about:
The resource type (Object Class)
The resource name (Friendly Name). For a board, the Friendly Name also
shows the boards location by rack, shelf and slot.

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. Table
4gives 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 from

one 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 must
be restored.

Major

a fault condition which requires urgent correction action. Example: severe

degradation in the capability of the managed object and its full capability
must be restored.

Minor

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

Warning

detection of a potential fault condition, before any significant effects have

been felt. Action should be taken to further diagnose (if necessary) and
correct the problem in order to prevent it from becoming a more serious
service 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 alarms
always give the date and time of the alarm. An alarm may also contain optional
information, such as the notification id. Refer to the AS on-line help for more
detailed information on AS.

14 / 146

3BK 20417 AAAA PCZZA Ed.09

1 Introduction

1.3 IMT Alarm Messages

The alarms generated by the A935 MFS equipment are displayed at the IMT in
the GPRS Terminal Window. Whenever A935 MFS equipment generates an
alarm, the alarm lists in the GPRS Terminal Window are updated. The number
of alarms in the appropriate list is incremented by one. Also, if the alarm icon is
not already displayed, it appears next to the impacted list. Optionally a beeper
can be sent to sound every time a new alarm is raised.
The IMT operator uses IMT facilities to identify which equipment is responsible
for the fault. Like the A1353-RA, the IMT also displays alarms grouped
according to severity levels. This makes it easier for the operator to prioritize
handling of the alarms.
Refer to the IMT on-line help for more information on handling alarms with the
IMT. To find a particular alarm definition, use the Advance Search facility in
electronic 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 five
lists based on the severity level of the alarm. Refer to Table 2 for a description
of severity levels.
Detailed information on an alarm is displayed in the Alarm Detailed View
Window. 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 listed
per probable cause.
The impacts are described with regard to the pilot station only, used in
active/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 and
defence unit global state).
Some alarms may no apply for MFS or SGSN, if they dont use the
mentioned DU. For example, there is no router for the MFS, so all router
alarms 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 and
its remote access.
The maintenance commands cannot be executed.

Impact on System

The station availabilityStatus is degraded.

2.1.1 Corrective Actions

Communication
subsystem failure

Station

yes

is

Unlock

locked?

station

no

Onsite
External

no

router link

Replace/repair

operational?

external router link

yes

Onsite
Link terminal
concentrator to station
operational

yes

no

Replace/repair
terminal/station link

Is link

yes

operational?

Alarm
solved

Contact
System Support
no

Contact
System Support

Figure 1: Communication subsystem failure: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

19 / 146

2 NECTAR Alarms

2.2 IAN error

eventType:

Communication

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 station
switchover. 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

2.2.1 Corrective Actions

IAN error

Station
Coupler

yes

of station

Replace
coupler

faulty?

no

Station
Link between

no

Replace/repair

station and LSN Hub

link station to

operational?

LSN Hub

yes

Hub
Hub power

no

Establish

supply

correct Hub

operational?

power supply

yes

Hub
Link &

no

Establish

network

correct link &

operational?

network

yes
Is link
Contact

operational?

yes

Alarm
solved

System Support
no

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 version

on the active station is not found on the standby station.

Impact on System

The control station switchover was at software version change, so there

is 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 not
secured.
The station availabilityStatus is failed.
There is no impact on the telecom service.

2.3.1 Corrective Actions

Version mismatch

Installed
correct software
version?

no
Reinstall

Alarm

correct version

solved

yes

Contact
System Support

Figure 3: Version mismatch: Corrective Actions

22 / 146

3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2.4 Software error

eventType:

ProcessingError

probableCause:

Software error

perceivedSeverity:

Critical

Alarm Description

The station cannot be installed by NECTAR because the station fails

during the initialization or the FLT program cannot be executed.

Impact on System

The control station switchover has been made at software version

change, so no O&M impact (the software is installed on the standby
station).
The standby pilot station is not initialized, so the O&M service is not
secured anymore in case of the pilot station.
The station availabilityStatus is failed.
There is no impact on the telecom service.

3BK 20417 AAAA PCZZA Ed.09

23 / 146

2 NECTAR Alarms

2.4.1 Corrective Actions

Software error

Installed

no

Reinstall correct version of

Alarm

UNIX, NECTAR, application

correct software

solved

version?

yes

Error
occures during
normal

yes
Verify the two hubs/switches

working?

no
Verify that the station has
not been stopped voluntarily
(by a third party)
Contact
System Support

Analyze the Nectar logs and

the application logs

Reinstall the local disk

Software
error
solved?

yes

Alarm
solved

no

Contact
System Support

Figure 4: Software error: Corrective Actions

24 / 146

3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2.5 Software program abnormally terminated

eventType:

ProcessingError

probableCause:

Software program abnormally terminated

perceivedSeverity:

Warning

Alarm Description:

NECTAR has detected the failure of a station. This alarm occurs during
the 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 in
progress.
Station availabilityStatus: OK.
Impact on the telecom service: None.

2.5.1 Corrective Actions

None. The station is down, but the automatic restart is in progress. Check
the 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

perceivedSeverity:

Critical

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.
The data on the shared disks are not secured. Administrative functions
are not impacted by this error.

Impact on System:

Shared disk availabilityStatus: failed.

Impact on the telecom service: None.

2.6.1 Corrective Actions

Power problem

Establish correct
Shared disk

no

shared disk

Alarm

power supply

powered?

solved

(switch power on etc)

yes

Subrack
powered?

no

Establish correct
subrack power supply

Alarm
solved

(switch power on etc)

yes

Contact
System Support

Figure 5: Power problem: Corrective Actions

26 / 146

3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2.7 I/O device error

eventType:

Equipment

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

shared 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 the
administrative 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 is
failed.
There is no Impact on the telecom service.

3BK 20417 AAAA PCZZA Ed.09

27 / 146

2 NECTAR Alarms

2.7.1 Corrective Actions

I/O device error
on:
Terminal
concentrator

Station
Shared
disk

OnSite
Replace local
disk, SCSI bus
or coupler

OnSite

Major

Replace Hub,
ethernet link
Hub/terminal or
terminal

Minor

Alarm
severity?

OnSite
SCSI
alarm
events?

yes

Solve SCSI
alarm

Replace
SCSI bus

no
OnSite

OnSite

Execute
disk_recover
to resynchronize
shared disk

Replace SCSI cables

Replace shared disk,

shareddisk box

I/O
operational?

yes

Alarm
solved

no
Contact
System Support

Figure 6: I/O device error: Corrective Actions

28 / 146

3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2.8 Equipment malfunction

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

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 FLT
result message where the hardware management has replaced the
FRU reference code by its administrative name.

Impact on System:

O&M service is interrupted because of the control station switchover is

not secure anymore.
The Station availabilityStatus is failed.
There is no impact on the telecom service.

3BK 20417 AAAA PCZZA Ed.09

29 / 146

2 NECTAR Alarms

2.8.1 Corrective Actions

Equipment malfunction

Onsite

Replace faulty
FRU given in
additional text:

Onsite

Onsite

Replace faulty
StorageWorks
shelf

OR

Replace faulty

Onsite

OR

power supply

Replace faulty
CPU box

Select
the station

Execute
clear_alarm

Station reboots
autonomously,
After reboot station
should be
" unlocked/ disabled/
initializing"

Router/
Station
operational?

yes

Alarm
solved

no

Contact
System Support

Figure 7: Equipment malfunction: Corrective Actions

30 / 146

3BK 20417 AAAA PCZZA Ed.09

2 NECTAR Alarms

2.9 Adaptor error

eventType:

Equipment

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 in
the shared disk box
On a station:
This alarm is associated associated to access error on shared SCSI
bus.

Impact on System:

On a station: The station is not stopped, but the access to the data on
the shared disks cannot be secured.
Station availabilityStatus: Degraded.
On a shared disk (GEM chip): The whole system is available but the
temperature 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

2.9.1 Corrective Actions

Adaptor error
on:
Shared disk

GEM

Station

no

operational?

Replace

Reboot

GEM chip

chip

the station

yes

SCSI

no

coupler

yes

SCSI
cable
ok?

Alarm
solved

operational?

coupler

operational?

yes

Adaptor

Replace SCSI

no

no

Replace SCSI coupler,

Replace SCSI

SCSI cable or CPU box

cable

as given by FLT result

yes

Contact
System Support

Adaptor
operational?

yes

Alarm
solved

no

Contact
System Support

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.

eventType:

Equipment

probableCause:

Ventilation system failure

perceivedSeverity:

Major

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.

2.10.1 Corrective Actions

Ventilation system
failure

Fan tray

no

establish correct

power supply

fan tray power

operational?

supply

yes

Replace
fan tray

Adaptor
operational?

yes

Alarm
solved

no

Contact
System Support

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

Note:

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

eventType:

Equipment

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 automatically
powered off.
If the problem is on a shared disk: The file management has detected
a fan failure in a fan tray.

Impact on System:

On a station: The station is powered off by the system. The O&M

service is interrupted due to a control station switchover, and it is not
secured anymore.
Station availabilityStatus: Failed.
On a shared disk: The system is available but only one fan in the fan
tray is available.
Impact on the telecom service: None.

2.11.1 Corrective Actions

Heating/ventilation/cooling
system problem on:

Shared disk

Station

Replace

Replace PCI

fan tray

fan or CPU fan

yes
Fan

Alarm

operational?

solved

no

Contact
System Support

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 first

temperature level, the system is available (alarm: Minor). For the
second temperature level, the system is stopped (alarm: Critical).

Impact on System:

If the severity is Critical, the faulty system is stopped. The station

availabilityStatus is failed. Then, on a station: The O&M service
is interrupted due to a control station switchover, it is not secured
anymore.
Then, on a shared disk: Data are not secured anymore.
There is no impact on the telecom service.

3BK 20417 AAAA PCZZA Ed.09

35 / 146

2 NECTAR Alarms

2.12.1 Corrective Actions

Temperature
unacceptable

Room

yes

Reduce room

temperature

temperature

too high?

no

Temperature

no

Replace

sensor

temperature

ok?

sensor

yes
Shared disk

Replace
fan tray

no

Station

Fan tray

PCU/CPUfan

operational?

operational?

yes

no

Replace
PCI fan
or CPU fan

yes

Contact

Contact

System Support

System Support

Temperature
acceptable?

yes

Alarm
solved

no

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 threshold
reached:

Warning

perceivedSeverity if disk full:

Critical

Alarm Description:

This is a warning alarm in a log. It means that a threshold has been

reached.
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&M
service is interrupted during this action. There is no impact on the
telecom service.

Note:

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

2.13.1 Corrective Actions

Storage capacity
problem

Reduce used disk

space (clean disk)

Enough
disk space?

yes

Alarm
solved

no

Contact
System Support

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

3 GPU/JBETI Boards Alarm Class

This chapter contains the MFS platform alarm definitions of the GPU/JBETI
Borad 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

3 GPU/JBETI Boards Alarm Class

Time base clock error (SGSN only)

Free run mode
Applique presence

40 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.1 PCI System Error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

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

Degradation

O&M Capabilities

# (GPU)

# (GPU)

- (JBETI)

Loss

Cells

- (JBETI)

- (GPU)
(JBETI)

# = if no switchover

3.1.1 Corrective Actions

PCI System Error

Onsite

Replace
JBETI

Alarm on
this JBETI
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 13: PCI System Error: Corrective Actions for JBETI

3BK 20417 AAAA PCZZA Ed.09

41 / 146

3 GPU/JBETI Boards Alarm Class

PCI System Error

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 14: PCI System Error: Corrective Actions for GPU

42 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.2 PCI Parity Error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1004098

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.

BSS

Degradation

O&M Capabilities

# (GPU)

# (GPU)

- (JBETI)

Loss

Cells

- (JBETI)

- (GPU)
(JBETI)

# = if no switchover

3BK 20417 AAAA PCZZA Ed.09

43 / 146

3 GPU/JBETI Boards Alarm Class

3.2.1 Corrective Actions

PCI Parity Error

Onsite

Reset all
GPU boards
by pushbotton
or via IMT

Alarm on

yes

GPU

Alarm
solved

cleared?

no

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 15: PCI Parity Error: Corrective Actions for GPU

44 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

PCI Parity Error

Onsite

Reset all
GPU boards
by pushbotton
or via IMT

Alarm on

yes

GPU

Alarm
solved

cleared?

no

Onsite

Replace
JBETI

Alarm on
this JBETI
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 16: PCI Parity Error: Corrective Actions for JBETI

3BK 20417 AAAA PCZZA Ed.09

45 / 146

3 GPU/JBETI Boards Alarm Class

3.3 GPU loss of contact

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1004146

Alarm Description:

The GEM chip has lost the Communication Service with the GPU, but
JBETI 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 software
problem.
All supported GPRS telecom resources will go disabled/failed if the
GPU goes disabled, with no switchover.
CircuitSwitched traffic may be interrupted if it is a hardware problem,
with no switchover.

BSS

Cells

O&M Capabilities

Loss

Degradation

# = if no switchover

46 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.3.1 Corrective Actions

GPU loss of contact

Is

yes

yes

Is

Alarm

GPU

GPU

disabled?

restarted?

solved

no
no

Onsite

Replace
GPU

OMCR
Check
software
versions

OMCR

yes
Alarm
solved

Alarm on
this GPU
cleared?

Reinstall
correct
software
version(s)

no

Contact
System Support

Alarm on

yes

this GPU
cleared?

Alarm
solved

no

Contact
System Support

Figure 17: GPU loss of contact: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

47 / 146

3 GPU/JBETI Boards Alarm Class

3.4 Ethernet error

eventType:

Communication

probableCause:

Ianerror

perceivedSeverity:

Minor

specificProblem (decimal):

1004145

Alarm Description:

One Ethernet link with GPU board is out of service.

Impact on System:

The communication between the control station and the GPU is

degraded.

BSS

Cells

O&M Capabilities

Loss

Degradation

48 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.4.1 Corrective Actions

Ethernet error

Component1
=1 =>
Termination
unit 1

Component1
=2 =>
Termination
unit 2

Onsite
Is

yes
Replugg unit

Ethernet Link 1
unplugged?

no

Onsite
Has
GPU Ethernet

yes
Replace GPU

autotest
alarm?

no

Onsite
Have

yes

all GPUs alarm

Replace Hub

JBETI loss
of contact?

no

Onsite
Have
all GPUs alarms,

yes
Replace BATTU

but no JBETI
alarms?

no

Onsite

Replace GPU

Onsite
Alarm on
this GPU

no
Replace Hub

cleared?

yes
Alarm on
Alarm
solved

this GPU
cleared?

no

Contact
System Support

yes

Alarm
solved

Figure 18: Ethernet error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

49 / 146

3 GPU/JBETI Boards Alarm Class

3.5 HDLC auto-test error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1016464

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.

BSS

Cells

O&M Capabilities
-

Loss
Degradation

3.5.1 Corrective Actions

HDLC autotest error

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 19: HDLC auto-test error: Corrective Actions

50 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.6 MT90820 Matrix auto-test error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1016469

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.
This alarm can occur only on GPU2.

Comments

BSS

Cells

O&M Capabilities
-

Loss
Degradation

3.6.1 Corrective Actions

MT90820 autotest error

Trigger
switchover

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no
Contact
System Support

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

3BK 20417 AAAA PCZZA Ed.09

51 / 146

3 GPU/JBETI Boards Alarm Class

3.7 MT90823 Matrix auto-test error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1016415

Alarm Description:

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

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.
This alarm can occur only on GPU2 variant AC.

Comments

BSS

Cells

O&M Capabilities
-

Loss
Degradation

3.7.1 Corrective Actions

Matrix autotest error

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no

Contact
System Support

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

52 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.8 BGTCGC auto-test error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1016470

Alarm Description:

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

Impact on System:

The GPU cannot start and is disabled.

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

BSS

Cells

O&M Capabilities
-

Loss
Degradation

3.8.1 Corrective Actions

BGTCGC autotest error

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 22: BGTCGC auto-test error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

53 / 146

3 GPU/JBETI Boards Alarm Class

3.9 BGRECC auto-test error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1016471

Alarm Description:

An auto-test discovered a problem on the BGRECC 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.

BSS

Cells

O&M Capabilities
-

Loss
Degradation

3.9.1 Corrective Actions

BGRECC autotest error

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 23: BGRECC auto-test error: Corrective Actions

54 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.10 JGHPI auto-test error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1016472

Alarm Description:

An auto-test discovered a problem on the JGHPI.

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.
This alarm can occur only on GPU2.

Comments

BSS

Cells

O&M Capabilities
-

Loss
Degradation

3.10.1 Corrective Actions

JGHPI autotest error

Trigger
switchover

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no
Contact
System Support

Figure 24: JGHPI auto-test error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

55 / 146

3 GPU/JBETI Boards Alarm Class

3.11 JGGPU2 auto-test error

eventType:

Equipment

probableCause:

equipmentMalfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1016419

Alarm Description:

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

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.
This alarm can occur only on GPU2 variant AC.

Comments

BSS

Cells

O&M Capabilities
-

Loss
Degradation

3.11.1 Corrective Actions

JGGPU2 autotest error

Trigger
switchover

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no
Contact
System Support

Figure 25: JGGPU2 auto-test error: Corrective Actions

56 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.12 PLX9080 auto-test error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1016473

Alarm Description:

An auto-test discovered a problem on the PLX9080.

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.
This alarm can only occur on GPU2.

Comments

BSS

Cells

O&M Capabilities
-

Loss
Degradation

3.12.1 Corrective Actions

PLX9080 autotest error

Trigger
switchover

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no
Contact
System Support

Figure 26: PLX9080 auto-test error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

57 / 146

3 GPU/JBETI Boards Alarm Class

3.13 PLX9054 auto-test error

eventType:

Equipment

probableCause:

equipmentMalfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1016411

Alarm Description:

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

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.
This alarm can only occur on GPU2 variant AC.

Comments

BSS

Cells

O&M Capabilities
-

Loss
Degradation

3.13.1 Corrective Actions

PLX9054 autotest error

Trigger
switchover

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no
Contact
System Support

Figure 27: PLX9054 auto-test error: Corrective Actions

58 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.14 NGISL2 auto-test error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Major

specificProblem (decimal):

1016480

Alarm Description:

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

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.
This alarm can only occur on GPU2.

Comments

BSS

Cells

O&M Capabilities
-

Loss
Degradation

3.14.1 Corrective Actions

NGISL2 autotest error

Trigger
switchover

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no
Contact
System Support

Figure 28: NGISL2 auto-test error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

59 / 146

3 GPU/JBETI Boards Alarm Class

3.15 NGISL3 auto-test error

eventType:

Equipment

probableCause:

equipmentMalfunction

perceivedSeverity:

Major

specificProblem (decimal):

1016425

Alarm Description:

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

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.
This alarm can only occur on GPU2 variant AC.

Comments

BSS

Cells

O&M Capabilities

Loss

Degradation

3.15.1 Corrective Actions

NGISL3 autotest error

Trigger
switchover

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no
Contact
System Support

Figure 29: NGISL3 auto-test error: Corrective Actions

60 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.16 BGPLTC auto-test error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1016481

Alarm Description:

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

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.
This alarm can only occur on GPU2.

Comments

BSS

Cells

O&M Capabilities
-

Loss
Degradation

3.16.1 Corrective Actions

BGPLTC autotest error

Trigger
switchover

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no
Contact
System Support

Figure 30: BGPLTC auto-test error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

61 / 146

3 GPU/JBETI Boards Alarm Class

3.17 GT-64161A auto-test error

eventType:

Equipment

probableCause:

equipmentMalfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1016420

Alarm Description:

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

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.
This alarm can only occur on GPU2 variant AC.

Comments

BSS

Cells

O&M Capabilities
-

Loss
Degradation

3.17.1 Corrective Actions

GT64161A autotest
error

Trigger
switchover

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no
Contact
System Support

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

62 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.18 Ethernet auto-test error

eventType:

Communication

probableCause:

Ianerror

perceivedSeverity:

Minor

specificProblem (decimal):

1016451

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 and
the GPU is degraded, and it is not secure anymore.

BSS

Cells

O&M Capabilities

Loss

Degradation

3BK 20417 AAAA PCZZA Ed.09

63 / 146

3 GPU/JBETI Boards Alarm Class

3.18.1 Corrective Actions

Ethernet autotest error

Component1
=1 =>
Termination
unit 1

Component1
=2 =>
Termination
unit 2

Trigger
switchover

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 32: Ethernet auto-test error: Corrective Actions

64 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.19 DSP auto-test error

eventType:

Equipment

probableCause:

Processor problem

perceivedSeverity:

Minor

specificProblem (decimal):

1016450

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 error
alarm later on, on which the operator has to react.

BSS

Cells

O&M Capabilities

Loss

Degradation

3.19.1 Corrective Actions

None.

3BK 20417 AAAA PCZZA Ed.09

65 / 146

3 GPU/JBETI Boards Alarm Class

3.20 DSP error

eventType:

Equipment

probableCause:

Processor problem

perceivedSeverity:

Major

specificProblem (decimal):

1016385

Alarm Description:

The DSP is offline.

Impact on System:

The GPU goes disabled and there is a switchover to the spare GPU.
The GPRS traffic is interrupted during the GPU switchover.

BSS

Cells

O&M Capabilities

Loss

Degradation

# = if no switchover

3.20.1 Corrective Actions

DSP error

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 33: DSP error: Corrective Actions

66 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.21 Framer auto-test error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Minor

specificProblem (decimal):

1016465

Alarm Description:

An auto-test discovered a problem on the Framer component. Start

goes on.

Impact on System:

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

BSS

Cells

O&M Capabilities

Loss

Degradation

# = due to the PCM failure

3.21.1 Corrective Actions

Framer autotest error

Onsite

Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 34: Framer auto-test error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

67 / 146

3 GPU/JBETI Boards Alarm Class

3.22 Time base clock error (SGSN only)

eventType:

Equipment

probableCause:

not relevant

perceivedSeverity:

Minor

specificProblem (decimal):

1016417

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 synchronizing

GPU.

BSS

Cells

O&M Capabilities

Loss

Degradation

3.22.1 Corrective Actions

None.

68 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.23 Free run mode

eventType:

Equipment

probableCause:

LossOfSynchronisation

perceivedSeverity:

Critical

specificProblem (decimal):

1016418

Alarm Description:

MFS case:
There is no longer a synchronizing PCM on the GPU. The GPU is
automatically 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 all
GPU switch into free run mode, using the local oscillator.
The alarm is on all synchronizing GPUs.

Impact on System:

BSS

The transmission quality on the PCM becomes degraded, as

synchronization is lost on frames.

Cells

Loss
Degradation

O&M Capabilities

3BK 20417 AAAA PCZZA Ed.09

69 / 146

3 GPU/JBETI Boards Alarm Class

3.23.1 Corrective Actions

Free run mode

First check for

& solve other
PCM alarms
(AIS;LOS,..)

At GPU Site
Are TX and RX
or
cables crossed ?
at Peer Entity Side

yes

Alarm
solved

yes

Alarm
solved

yes

Alarm
solved

yes

Alarm
solved

no

Does Sync.
PCM recover?

no

Congigure new
sync. PCM for
GPU

MFS only:
add Gb PCM to
Transcoder or
SGSN

PCM in service?

no

Onsite
Replace
GPU

PCM in service?

no

Contact
System Support

Figure 35: Free run mode: Corrective Actions

70 / 146

3BK 20417 AAAA PCZZA Ed.09

3 GPU/JBETI Boards Alarm Class

3.24 Applique Presence

eventType:

Equipment

probableCause:

BackPlaneFailure

perceivedSeverity:

Critical

specificProblem (decimal):

1016449

Alarm Description:

The JAE1 is not present.

Impact on System:

There is no traffic available for the associated GPU board. PCM

are disabled. The board is still enabled but all its associated radio
resources will go or remain disabled.

BSS

Cells

O&M Capabilities
-

Loss
Degradation

3.24.1 Corrective Actions

Applique presence

Onsite

Insert
JAE1

Alarm on
assoc. GPU
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 36: Applique presence: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

71 / 146

3 GPU/JBETI Boards Alarm Class

72 / 146

3BK 20417 AAAA PCZZA Ed.09

4 PCM-TTP Alarm Class

4 PCM-TTP Alarm Class

This chapter contains the MFS platform alarm definitions of the PCM -TTP
Alarm class
LOS
LFA
AIS
CH0EERH
RAI
DFM
CRC4BERH
CRC4BERL.

3BK 20417 AAAA PCZZA Ed.09

73 / 146

4 PCM-TTP Alarm Class

4.1 LOS
eventType:

Communication

probableCause:

LossOfSignal
RemoteAlarmInterface
AIS
LossOfFrame

perceivedSeverity:

Critical

specificProblem (decimal):

1016401

Alarm Description:

The PCM link between transceiver and receiver is broken.

If several PCM-TTPs of the same GPU are affected by transmission
alarms, 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 service
is degraded (bandwith is reduced).

BSS
Loss
Degradation

74 / 146

Cells

O&M Capabilities

3BK 20417 AAAA PCZZA Ed.09

4 PCM-TTP Alarm Class

4.1.1 Corrective Actions

LOS
At GPU Site
or
at Peer Entity Side
Are TX and RX
cables crossed ?

yes

Alarm
solved

Onsite
Is
PCM Link
unplugged?

yes

Replugg
PCM link

no

At peer site
Is line
in service?

no

Check peer
entities,
repeaters etc.

yes

Onsite
Alarm is on
more than
2 PCMTTP?

yes
Replace JAE

no

Contact
System Support

Alarm on
this GPU
cleared?

yes

Alarm
solved

no
Contact
System Support

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 into
service, automatically.
The alarm is also cleared at GPU extraction or setting the PCM-TTP alarm
filtering (locking the 2MbTTP on Q3 interface).

3BK 20417 AAAA PCZZA Ed.09

75 / 146

4 PCM-TTP Alarm Class

4.2 LFA
eventType:

Communication

probableCause:

LossOfFrame

perceivedSeverity:

Critical

specificProblem (decimal):

1016402

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 is
degraded (bandwith is reduced).

BSS
Loss

Cells

O&M Capabilities

Degradation

4.2.1 Corrective Actions

LFA

At peer site
no
Is line in service?

Check
peer entities,
repeaters etc.

yes

Alarm:
Applique

yes

Solve Alarm

Presence

Applique

on

Presence

GPU?

no
Alarm on
Contact

this GPU

System Support

yes

Alarm

cleared?

solved

no

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 PCM-TTP Alarm Class

4.3 AIS
eventType:

Communication

probableCause:

AIS

perceivedSeverity:

Critical

specificProblem (decimal):

1016403

Alarm Description:

There are two or less ZEROs in each two successive double frame
periods.
The peer entity has emission problems.
The PCM-TTP is disabled (no more traffic).

Impact on System:

If it is an Ater or Gb PCM-TTP, related BSS and cells GPRS service is

degraded (bandwith is reduced).

BSS
Loss

Cells

O&M Capabilities

Degradation

4.3.1 Corrective Actions

AIS

At peer site
Check peer
entities,
repeaters etc.

Alarm is
solved when peer entity
is back in service

Figure 39: AIS: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

77 / 146

4 PCM-TTP Alarm Class

4.4 CH0EERH
eventType:

Communication

probableCause:

ExcessiveBER

perceivedSeverity:

Critical

specificProblem (decimal):

1016405

Alarm Description:

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

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 is
degraded (bandwith is reduced).

BSS
Loss

Cells

O&M Capabilities

Degradation

4.4.1 Corrective Actions

BER 103

At peer site
Check peer
entities,
repeaters etc.

Alarm is
solved when peer entity
is back in service

Figure 40: CH0EERH: Corrective Actions

78 / 146

3BK 20417 AAAA PCZZA Ed.09

4 PCM-TTP Alarm Class

4.5 RAI
eventType:

Communication

probableCause:

RemoteAlarmInterface

perceivedSeverity:

Critical

specificProblem (decimal):

1016406

Alarm Description:

The MFS has received a RAI-remote alarm indication, sent by the peer
entity, signaling an emission problem (remote equipment understands
nothing). This is temporized for 100 ms.

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 is
degraded (bandwith is reduced).

BSS
Loss

Cells

O&M Capabilities

Degradation

3BK 20417 AAAA PCZZA Ed.09

79 / 146

4 PCM-TTP Alarm Class

4.5.1 Corrective Actions

RAI

Other
relating alarms
(DFM etc.)?

yes

Solve
that alarms

no

Force

Resetdata

switchover

GPU

Alarm on
this GPU

yes

Alarm
solved

cleared?

no

Replace GPU

Alarm on
this GPU

yes

Alarm
solved

cleared?

no

Contact
System Support

Figure 41: RAI: Corrective Actions

80 / 146

3BK 20417 AAAA PCZZA Ed.09

4 PCM-TTP Alarm Class

4.6 DFM
eventType:

Communication

probableCause:

TransmitFailure

perceivedSeverity:

Critical

specificProblem (decimal):

1016407

Alarm Description:

There is a problem on JAE1 component or PCM is connected to

ground. 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.
If it is an Ater or Gb PCM-TTP, related BSS and cells GPRS service is
degraded (bandwith is reduced).

BSS
Loss

Cells

O&M Capabilities

Degradation

3BK 20417 AAAA PCZZA Ed.09

81 / 146

4 PCM-TTP Alarm Class

4.6.1 Corrective Actions

DFM

Are TX and RX
cables crossed ?

At GPU Site
or
at Peer Entity Side
yes

Alarm
solved

Onsite
Is
PCM Link
unplugged?

yes

Replugg
PCM link

no

At peer site
Is line
in service?

no

Check
peer entities,
repeaters etc.

yes

Onsite

Replace JAE

Alarm on
this GPU
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 42: DFM: Corrective Actions

Alarm is cleared at problem resolution, when PCM is automatically brought
back 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 PCM-TTP Alarm Class

4.7 CRC4BERH
eventType:

Communication

probableCause:

DegradedSignal

perceivedSeverity:

Major

specificProblem (decimal):

1016408

Alarm Description:

BER 10-4: The excessive error rate is 51 errors in 1 s, only with

CRC4.

Impact on System:

The traffic on PCM is perturbed.

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

BSS
Loss

Cells

O&M Capabilities

Degradation

4.7.1 Corrective Actions

BER 106

At peer site
Check
peer entities,
repeaters etc.

Alarm is solved
when peer entity
is back in service

Figure 43: CRC4BERH: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

83 / 146

4 PCM-TTP Alarm Class

4.8 CRC4BERL
eventType:

Communication

probableCause:

DegradedSignal

perceivedSeverity:

Minor

specificProblem (decimal):

1016409

Alarm Description:

BER 10-6: The excessive error rate is 100 errors in 1 min, only with
CRC4.

Impact on System:

The traffic on PCM is perturbed. If it is an Ater or Gb PCM-TTP, related

BSS and cells GPRS service is degraded (bandwith is reduced).

BSS
Loss

Cells

O&M Capabilities

Degradation

4.8.1 Corrective Actions

BER 106

At peer site
Check
peer entities,
repeaters etc.

Alarm is solved
when peer entity
is back in service

Figure 44: CRC4BERL: Corrective Actions

84 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5 SUB-RACK Alarm Class

This section contains the MFS platform alarm definitions of the SUB -Rack
alarm 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 SUB-RACK Alarm Class

5.1 Board Ethernet error at initialization phase

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1004099

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, there
will be no converter and fan alarms.
If this happens at board plug-in, the GPU/JBETI object is not created
for this board, as it cannot start.
No telecom impact, as board cannot start.

BSS

Cells

O&M Capabilities

Loss

Degradation

5.1.1 Corrective Actions

Board Ethernet error at
initialization phase

Onsite

Replace
JBETI
(given in
Component1)

Alarm on
this JBETI
cleared?

yes

Alarm
solved

no

Contact
System Support

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 that
starts properly is plugged in the same slot.

86 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.2 Board firmware updated part error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1004100

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, there
will be no converter and fan alarms.
If this happens at board plug-in, the GPU/JBETI object is not created
for this board, as it cannot start.
No telecom impact, as board cannot start.

BSS

Cells

O&M Capabilities

Loss

Degradation

5.2.1 Corrective Actions

Board firmware
updated part error

Onsite

Replace
JBETI
(given in
Component1)

Alarm on
this JBETI
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 46: Board firmware updated part error: Corrective Actions

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

3BK 20417 AAAA PCZZA Ed.09

87 / 146

5 SUB-RACK Alarm Class

5.3 Board firmware permanent part error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1004101

Alarm Description:

The checksum test on permanent part of firmware has failed.

Impact on System:

There is no impact except for slot4. If JBETI slot 4 cannot start, there
will be no converter and fan alarms.
If this happens at board plug-in, the GPU/JBETI object is not created
for this board, as it cannot start.
No telecom impact, as board cannot start.

BSS

Cells

O&M Capabilities

Loss

Degradation

5.3.1 Corrective Actions

Board firmware
permanent part error

Onsite

Lock/Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no
Contact
System Support

Figure 47: Board firmware permanent part error: Corrective Actions

88 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.4 Board DRAM error

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1004102

Alarm Description:

The DRAM firmware part test has failed.

Impact on System:

There is no impact except for slot4. If JBETI slot 4 cannot start, there
will be no converter and fan alarms.
If this happens at board plug-in, the GPU/JBETI object is not created
for this board, as it cannot start.
No telecom impact, as board cannot start.

BSS

Cells

O&M Capabilities

Loss

Degradation

3BK 20417 AAAA PCZZA Ed.09

89 / 146

5 SUB-RACK Alarm Class

5.4.1 Corrective Actions

Board DRAM error

Onsite

Reset JBETI
(given in
component1)

Alarm on

yes

this JBETI

Alarm
solved

cleared?

no

Onsite

Replace JBETI

Alarm on
this JBETI
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 48: Board DRAM error: Corrective Actions

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

90 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.5 Board ECC test error during boot phase

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1004103

Alarm Description:

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

Impact on System:

There is no impact except for slot4. If JBETI slot 4 cannot start, there
will be no converter and fan alarms.
If this happens at board plug-in, the GPU/JBETI object is not created
for this board, as it cannot start.
No telecom impact, as board cannot start.

BSS

Cells

O&M Capabilities

Loss

Degradation

5.5.1 Corrective Actions

Board ECC test error
during boot phase

Onsite

Replace
JBETI (given in
component1)

Alarm on
this JBETI
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 49: Board ECC test error during boot phase: Corrective Actions
If this happens at board plug-in, the alarm is cleared when a new board that
starts properly is plugged in the same slot.

3BK 20417 AAAA PCZZA Ed.09

91 / 146

5 SUB-RACK Alarm Class

5.6 Board target abort during boot phase

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1004104

Alarm Description:

The target aborted (MCP) during boot processing.

Impact on System:

There is no impact except for slot4. If JBETI slot 4 cannot start, there
will be no converter and fan alarms.
If this happens at board plug-in, the GPU/JBETI object is not created
for this board, as it cannot start.
No telecom impact, as board cannot start.

BSS

Cells

O&M Capabilities

Loss

Degradation

5.6.1 Corrective Actions

Board target abort
during boot phase

Onsite

Replace
JBETI (given in
component1)

Alarm on
this JEBTI
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 50: Board target abort during boot phase: Corrective Actions
If this happens at board plug-in, the alarm is cleared when a new board that
starts properly is plugged in the same slot.

92 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.7 Unlocked board deletion alarm

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1004105

Alarm Description:

The GPU has been extracted without being locked.

Impact on System:

Telecom traffic (GPRS and Circuit Switched) has been interrupted on

this GPU. All telecom resources that were supported by this board
have now a not-installed availabilityStatus.

BSS

Cells

O&M Capabilities
-

Loss
Degradation

5.7.1 Corrective Actions

Unlocked board
deletion alarm

Onsite

RePlugg/
Replace
GPU

Alarm on
this GPU
cleared?

yes

Alarm
solved

no

Contact
System Support

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 SUB-RACK Alarm Class

5.8 JBETI slot4 loss of contact

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1004161

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

service (subrack supervision) is degraded.

BSS

Cells

O&M Capabilities

Loss

Degradation

5.8.1 Corrective Actions

JBETI slot4
loss of contact

Onsite
JBETI

yes

slot4

RePlugg
JBETI

unplugged?

no

Onsite
JBETI
slot4
faulty?

yes

Replace
JBETI

no

Contact

Alarm on

System Support

this GPU
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 52: JBETI slot4 loss of contact: Corrective Actions

94 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.9 JBETI slot23 loss of contact

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Major

specificProblem (decimal):

1004162

Alarm Description:

The contact with JBETI slot23 is lost.

Impact on System:

There is no impact.

BSS

Cells

O&M Capabilities

Loss

Degradation

5.9.1 Corrective Actions

JBETI slot23
loss of contact

Onsite
JBETI

yes

slot23

RePlugg
JBETI

unplugged?

no

Onsite
JBETI
slot23
faulty?

yes

Replace
JBETI

no

Contact
System Support

Alarm on
this GPU
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 53: JBETI slot23 loss of contact: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

95 / 146

5 SUB-RACK Alarm Class

5.10 No JBETI on subrack

eventType:

Equipment

probableCause:

ReplaceableUnitMissing

perceivedSeverity:

Critical

specificProblem (decimal):

1004163

Alarm Description:

There is no available JBETI on the subrack.

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

Impact on System:

The alarms are cleared; no new alarm is triggered (at least no

equipment alarms reported by JBETI) and boards cannot be reset.

BSS

Cells

O&M Capabilities

Loss

Degradation

96 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.10.1 Corrective Actions

No JEBTI on subrack

Is

yes

No action

transient?

Alarm

required

alarm

solved

no

Onsite
Minimum
no

one

Insert

JBETI

JBETI

in service?

yes

Onsite
Alarm
Loss of Contact
on faulty

yes

Solve alarm
Loss of Contact

JBETI?

no

Onsite

Replace
JBETI

Alarm on
this JBETI
cleared?

yes
Alarm
solved

no

Contact
System Support

Figure 54: No JBETI on subrack: Corrective Actions

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

3BK 20417 AAAA PCZZA Ed.09

97 / 146

5 SUB-RACK Alarm Class

5.11 JBETI address error

eventType:

Equipment

probableCause:

ReplaceableUnitProblem

perceivedSeverity:

Critical

specificProblem (decimal):

1004113

Alarm Description:

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

ADR cabling (ADRIN, ADR1, ADR2, ADR3, ADROUT) on JAETIs (that
chain the racks and subracks) fixing JBETI rack/subrack addresses, is
wrong.

Impact on System:

O&M service is degraded, rack/subrack/slot identifiers in alarms

description may be wrong.
A JBETI with an invalid rack/subRack number is disabled.

BSS

Cells

O&M Capabilities

Loss

Degradation

98 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.11.1 Corrective Actions

JBETI address error

Onsite
Is

no
Redo cabling

ADR cabling
correct?

yes

Onsite
Is

yes

ADR cabling

Replace
ADRx cable(s)

faulty?

no
Alarm on
this JBETI
cleared?

yes
Alarm
solved

Contact
System Support
no

Contact
System Support

Figure 55: JBETI address error: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

99 / 146

5 SUB-RACK Alarm Class

5.12 Fan problem

eventType:

Equipment

probableCause:

CoolingFanFailure

perceivedSeverity:

Major

specificProblem (decimal):

1004114

Alarm Description:

One or more fans problem, or the maintenance key is set, or the

BDAFU is unplugged.

Impact on System:

The subrack temperature may increase, raising the temperature

problem alarm.

BSS

Cells

O&M Capabilities

Loss

Degradation

100 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.12.1 Corrective Actions

Fan problem

Onsite
Is

yes

Unset

maintenance

maintenance

key set?

key

no

Onsite
Is

yes

BDAFU

Replugg
BDAFU

unplugged?

no

Onsite
Is
BDAFU

yes

Replace
faulty Fan

LED
yellow?

no

Alarm on
Contact

this BDAFU

System Support

cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 56: Fan problem: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

101 / 146

5 SUB-RACK Alarm Class

5.13 Temperature problem

eventType:

Equipment

probableCause:

HeatingOrVentilationOrCoolingSystemProblem

perceivedSeverity:

Critical

specificProblem (decimal):

1004115

Alarm Description:

Impact on System:

At least one temperature sensor has detected a temperature over 65

C.

The subrack power may be cut off. If so, BSS, cells and Circuit
Switched traffic are lost on all subRack GPUs.

BSS

Cells

O&M Capabilities

Loss
Degradation

102 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.13.1 Corrective Actions

Temperature problem

Onsite
yes

Alarm

Solve alarm
Fan Problem

Fan Problem?

no

Onsite
Alarm(s)

yes

on related

Solve GPU
problems

GPU(s)?

no

Onsite

Switch subrack
power on

Alarm on

yes

this subrack
cleared?

no

Onsite

Replace
fan tray

Alarm on
this subrack
cleared?

yes
Alarm
solved

no

Contact
System Support

Figure 57: Temperature problem: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

103 / 146

5 SUB-RACK Alarm Class

5.14 48V alarm

Note:

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

eventType:

Equipment

probableCause:

PowerProblem

perceivedSeverity:

Critical

specificProblem (decimal):

1004122

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.

BSS

Cells

O&M Capabilities

Loss

Degradation

104 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.14.1 Corrective Actions

48V alarm

Onsite

Power input

no

establish
correct

correct?

power input

yes

Onsite

yes

Alarm

Solve
PRE48 alarm

PRE48?

no

Onsite

Replace
BE35B2
Alarm(s) on
relating
converter?

yes

Onsite

Replace
BA35B2
no

Contact
System Support
Alarm on
this converter
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 58: 48V alarm: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

105 / 146

5 SUB-RACK Alarm Class

5.15 PRE48 alarm

eventType:

Equipment

probableCause:

Equipment malfunction

perceivedSeverity:

Major

specificProblem (decimal):

1004131

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.

BSS

Cells

O&M Capabilities

Loss

Degradation

5.15.1 Corrective Actions

PRE48 alarm

Onsite
BLTLM cable
TRU/JAETI

yes

Replugg
BLTLM cable

slot4/23
unplugged?

no

Onsite

Rack power

no

Establish
correct rack

supply ok?

power supply

yes

Onsite

Input power
avaliable?

no

Ensure correct
input power

yes

Alarm on
this rack
cleared?

yes

Alarm
solved

Contact
System Support
no

Contact
System Support

Figure 59: PRE48 alarm: Corrective Actions

106 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.16 CALVREF alarm

eventType:

Equipment

probableCause:

PowerProblem

perceivedSeverity:

Critical

specificProblem (decimal):

1004136

Alarm Description:

CALVREF: There is no longer the -48V input reference from the top
of the rack.

Impact on System:

O&M service degraded, as external alarms are no longer visible.

BSS

Cells

O&M Capabilities

Loss

Degradation

3BK 20417 AAAA PCZZA Ed.09

107 / 146

5 SUB-RACK Alarm Class

5.16.1 Corrective Actions

CALVREF alarm

Onsite
yes

Cable(s)
TRU/JAETI slot4/23

Replugg
cable(s)

unplugged?

no

Onsite

no
Rack power

Establish correct

supply ok?

rack power supply

yes

Onsite

Input power
avaliable?

no

Ensure correct
input power

yes

Alarm on
this rack
cleared?

yes

Alarm
solved

Contact
System Support
no

Contact
System Support

Figure 60: CALVREF alarm: Corrective Actions

108 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.17 ACP1 alarm

eventType:

Equipment

probableCause:

PowerProblem

perceivedSeverity:

Major

specificProblem (decimal):

1004135

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 problem

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

BSS

Cells

O&M Capabilities

Loss

Degradation

5.17.1 Corrective Actions

ACP1 alarm

Onsite

TRU circuit
breakers ok?

no

Replace TRU
circuit breakers

yes

Onsite
Replace
precharge
module

Alarm on
this rack
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 61: ACP1 alarm: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

109 / 146

5 SUB-RACK Alarm Class

5.18 Hub converter problem

Note:

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

eventType:

Equipment

probableCause:

PowerProblem

perceivedSeverity:

Major

specificProblem (decimal):

1004137

Alarm Description:

A Hub converter is out of service, or a input of the terminal server is

out of service.

Impact on System:

None.

BSS

Cells

O&M Capabilities

Loss

Degradation

110 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.18.1 Corrective Actions

Hub converter problem

Onsite
JHALA cable(s)

yes

to related converter

Replugg JHALA
cable(s)

unplugged?

no

Onsite

Related power

Establish

no

correct Hub

supply ok?

power supply

yes

Onsite

Related

yes

converter faulty?

Replace related
faulty converter

no

Onsite
Input of terminal

Onsite
Repair & bring

server is out of

back terminal

service.

server in service

Alarm on
this rack
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 62: Hub converter problem: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

111 / 146

5 SUB-RACK Alarm Class

5.19 CNVR converter alarm

eventType:

Equipment

probableCause:

PowerProblem

perceivedSeverity:

Major

specificProblem (decimal):

1004116

Alarm Description:

The CNVR output voltage overloads threshold 1 or 2. There is a

converter disjunction.

Impact on System:

After several CNVR alarms, the subrack power may be cut off.

BSS

Cells

O&M Capabilities

Loss

Degradation

5.19.1 Corrective Actions

CNVR converter alarm

Onsite

Replace related
faulty converter

Alarm on
this rack
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 63: CNVR converter alarm: Corrective Actions

Note:

112 / 146

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

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.20 2.1V alarm

eventType:

Equipment

probableCause:

PowerProblem

perceivedSeverity:

Critical

specificProblem (decimal):

1004130

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 is

degraded. Switchover of GPU to spare board is not available

BSS

Cells

O&M Capabilities

Loss

Degradation

5.20.1 Corrective Actions

2.1V alarm

Onsite

Replace
JAETI

Alarm on
this rack

yes

Alarm
solved

cleared?

no

Contact
System Support

Figure 64: 2.1V alarm: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

113 / 146

5 SUB-RACK Alarm Class

5.21 JAETI Failure (slot 4)

eventType:

Equipment

probableCause:

equipmentMalfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1004153

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 will
not restart with an important outage of services.

5.21.1 Corrective Actions

JAETI Failure
slot 4

Onsite

Replace
JAETI

Onsite

Reset both
JBETIs
with board switch

Alarm
cleared?

yes

Alarm
solved

no

Contact
System Support

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

114 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.22 JAETI Failure (slot 23)

eventType:

Equipment

probableCause:

equipmentMalfunction

perceivedSeverity:

Critical

specificProblem (decimal):

1004154

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 will
not restart with an important outage of services.

5.22.1 Corrective Actions

JAETI Failure
slot 23

Onsite

Replace
JAETI

Onsite

Reset both
JBETIs
with board switch

Alarm
cleared?

yes

Alarm
solved

no

Contact
System Support

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

3BK 20417 AAAA PCZZA Ed.09

115 / 146

5 SUB-RACK Alarm Class

5.23 EALM1
eventType:

Environmental

probableCause:

GsmExternalEquipmentFailure

perceivedSeverity:

Major

specificProblem (decimal):

1006400

Alarm Description:

This is the external alarm n1.

Impact on System:

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

BSS

Cells

O&M Capabilities

Loss

Degradation

116 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.23.1 Corrective Actions

EALM1

yes
Blind alarm?

Onsite
no
Sensor

no

Replugg/
replace sensor

cabling ok?

cabling

Trigger action
according to
Additional_Text

yes

Onsite

no
Sensor ok?

Replace
sensor

yes

External
Contact
System Support

alarm
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 67: EALM1: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

117 / 146

5 SUB-RACK Alarm Class

5.24 EALM2 external alarm

eventType:

Environmental

probableCause:

GsmExternalEquipmentFailure

perceivedSeverity:

Major

specificProblem (decimal):

1006401

Alarm Description:

This is the external alarm n2.

Impact on System:

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

BSS

Cells

O&M Capabilities

Loss

Degradation

5.24.1 Corrective Actions

EALM2

yes
Blind alarm?

Onsite
no
Sensor

no

Replugg/
replace sensor

cabling ok?

cabling

Trigger action
according to
Additional_Text
yes

Onsite

no
Sensor ok?

Replace
sensor

yes
External
Contact

alarm

System Support

cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 68: EALM2: Corrective Actions

118 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.25 EALM3 external alarm

eventType:

Environmental

probableCause:

GsmExternalEquipmentFailure

perceivedSeverity:

Major

specificProblem (decimal):

1006402

Alarm Description:

This is the external alarm n3.

Impact on System:

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

BSS

Cells

O&M Capabilities

Loss

Degradation

5.25.1 Corrective Actions

EALM3

yes
Blind alarm?

Onsite
no
Sensor

no

Replugg/
replace sensor

cabling ok?

cabling

Trigger action
according to
Additional_Text
yes

Onsite

no
Sensor ok?

Replace
sensor

yes

Contact
System Support

External

yes

alarm

no

Contact
System Support

Figure 69: EALM3: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

Alarm
solved

cleared?

119 / 146

5 SUB-RACK Alarm Class

5.26 EALM4 external alarm

eventType:

Environmental

probableCause:

GsmExternalEquipmentFailure

perceivedSeverity:

Major

specificProblem (decimal):

1006403

Alarm Description:

This is the external alarm n4.

Impact on System:

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

BSS

Cells

O&M Capabilities

Loss

Degradation

5.26.1 Corrective Actions

EALM4

yes
Blind alarm?

Onsite
no
Sensor

no

Replugg/
replace sensor

cabling ok?

cabling

Trigger action
according to
Additional_Text
yes

Onsite

no
Sensor ok?

Replace
sensor

yes

External
Contact

alarm

System Support

cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 70: EALM4: Corrective Actions

120 / 146

3BK 20417 AAAA PCZZA Ed.09

5 SUB-RACK Alarm Class

5.27 EALM5 external alarm

eventType:

Environmental

probableCause:

GsmExternalEquipmentFailure

perceivedSeverity:

Major

specificProblem (decimal):

1006404

Alarm Description:

This is the external alarm n5.

Impact on System:

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

BSS

Cells

O&M Capabilities

Loss

Degradation

5.27.1 Corrective Actions

EALM5

yes
Blind alarm?

Onsite
no
Sensor

no

Replugg/
replace sensor

cabling ok?

cabling

Trigger action
according to
Additional_Text
yes

Onsite

no
Sensor ok?

Replace sensor

yes

External
Contact
System Support

yes

alarm

no

Contact
System Support

Figure 71: EALM5: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

Alarm
solved

cleared?

121 / 146

5 SUB-RACK Alarm Class

5.28 EALM6 external alarm

eventType:

Environmental

probableCause:

GsmExternalEquipmentFailure

perceivedSeverity:

Major

specificProblem (decimal):

1006405

Alarm Description:

This is the external alarm n6.

Impact on System:

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

BSS

Cells

O&M Capabilities

Loss

Degradation

5.28.1 Corrective Actions

EALM6

yes
Blind alarm?

Onsite
no
Sensor

no

Replugg/
replace sensor

cabling ok?

cabling

Trigger action
according to
Additional_Text
yes

Onsite

no
Sensor ok?

Replace
sensor

yes

Contact

External

System Support

alarm

yes

cleared?

no

Contact
System Support

Figure 72: EALM6: Corrective Actions

122 / 146

3BK 20417 AAAA PCZZA Ed.09

Alarm
solved

5 SUB-RACK Alarm Class

5.29 EALM7 external alarm

eventType:

Environmental

probableCause:

GsmExternalEquipmentFailure

perceivedSeverity:

Major

specificProblem (decimal):

1006406

Alarm Description:

This is the external alarm n7.

Impact on System:

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

BSS

Cells

O&M Capabilities

Loss

Degradation

5.29.1 Corrective Actions

EALM7

yes
Blind alarm?

Onsite
no
Sensor

no

Replugg/
replace sensor

cabling ok?

cabling

Trigger action
according to
Additional_Text
yes

Onsite

no
Sensor ok?

Replace sensor

yes

External
Contact

yes

alarm

System Support

cleared?

no

Contact
System Support

Figure 73: EALM7: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

Alarm
solved

123 / 146

5 SUB-RACK Alarm Class

5.30 EALM8 external alarm

eventType:

Environmental

probableCause:

GsmExternalEquipmentFailure

perceivedSeverity:

Major

specificProblem (decimal):

1006407

Alarm Description:

This is the external alarm n8.

Impact on System:

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

BSS

Cells

O&M Capabilities

Loss

Degradation

5.30.1 Corrective Actions

EALM8

yes
Blind alarm?

Onsite
no
Sensor

no

Replugg/
replace sensor

cabling ok?

cabling

Trigger action
according to
Additional_Text
yes

Onsite

no
Sensor ok?

Replace
sensor

yes

Contact

External

System Support

alarm
cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 74: EALM8: Corrective Actions

124 / 146

3BK 20417 AAAA PCZZA Ed.09

6 MFS Telecommunication Alarms

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 MFS Telecommunication Alarms

6.1 SGSN in user mode

eventType:

ProcessingError

probableCause:

ConfigurationOrCustomizationError

perceivedSeverity

Major

specificProblem (decimal):

1016641

Alarm Description:

The SGSN sends a status inquiry that indicates that it is also in user
mode.

Impact on System:

The FRBearer is disabled, it cannot start.

There is no impact on Circui tSwitched traffic.

BSS
Loss

Cells

O&M Capabilities

Degradation

6.1.1 Corrective Actions

None.
It is up to the SGSN to change its configuration.
The alarm is cleared when SGSN sends a status inquiry that indicates that it
is in network mode.

126 / 146

3BK 20417 AAAA PCZZA Ed.09

6 MFS Telecommunication Alarms

6.2 No response from network

eventType:

Communication

probableCause:

TransmissionError

perceivedSeverity

Major

specificProblem (decimal):

1016446

Alarm Description:

There is no reply from the network to the status inquiry after a certain
number of requests.

Impact on System:

The FRBearer is disabled, it cannot start.

BSS and cells GPRS service is degraded.
There is no impact on Circuit Switched traffic.

BSS
Loss

Cells

O&M Capabilities

Degradation

6.2.1 Corrective Actions

No response
from network

Onsite

PCM cable(s)

yes

Replugg
PCM cable

unplugged?

no

Onsite
Alarm on
related
PCMTTP?

yes

Solve PCMTTP
alarm first

no

PCM problem must be

PCM Alarm

solved at peer side

cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 75: No response from network: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

127 / 146

6 MFS Telecommunication Alarms

6.3 No reply from network

eventType:

Communication

probableCause:

TransmissionError

perceivedSeverity

Major

specificProblem (decimal):

1016642

Alarm Description:

There is no reply from the network to the status inquiry.

Impact on System:

The FRBearer is disabled, it cannot start.

There is no impact on Circuit Switched traffic.

BSS
Loss

Cells

O&M Capabilities

Degradation

6.3.1 Corrective Actions

No reply
from network

Onsite

PCM cable(s)

yes

Replugg
PCM cable

unplugged?

no

Onsite
Alarm on
related
PCMTTP?

yes

Solve PCMTTP
alarm first

no

PCM problem must be

PCM Alarm

solved at peer side

cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 76: No reply from network: Corrective Actions

128 / 146

3BK 20417 AAAA PCZZA Ed.09

6 MFS Telecommunication Alarms

6.4 No reply from SGSN

eventType:

Communication

probableCause:

TransmissionError

perceivedSeverity

Major

specificProblem (decimal):

1016672

Alarm Description:

The SGSN does not answer an NS-VC procedure.

Impact on System:

The NS-VC is disabled

There is no impact on Circuit Switched traffic.

BSS
Loss

Cells

O&M Capabilities

Degradation

6.4.1 Corrective Actions

No reply from SGSN

Onsite

PCM cable(s)

yes

Replugg PCM
cable

unplugged?

no

Onsite
Alarm on
related
PCMTTP?

yes

Solve PCMTTP
alarm first

no

PCM problem must be

PCM Alarm

solved at peer side

cleared?

yes

Alarm
solved

no

Contact
System Support

Figure 77: No reply from SGSN: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

129 / 146

6 MFS Telecommunication Alarms

6.5 NSEI mismatch

eventType:

ProcessingError

probableCause:

ConfigurationOrCustomizationError

perceivedSeverity

Major

specificProblem (decimal):

1016673

Alarm Description:

This alarm is raised when SGSN sends back a wrong NSEI at NS-reset
ack.

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 share
the same NSEI. Then BSS and cells are lost. (#)
There is no impact on Circuit Switched traffic.

BSS
Loss

Cells

O&M Capabilities

Degradation

6.5.1 Corrective Actions

NSEI mismatch

SGSN side

Reconfigure

MFS side

NSEI

Delete/create
NSEI with new
NSE

SGSN

yes

accepts
NSEI?

Alarm
solved

no

Contact
System Support

Figure 78: NSEI mismatch: Corrective Actions

130 / 146

3BK 20417 AAAA PCZZA Ed.09

6 MFS Telecommunication Alarms

6.6 NSVCI mismatch

eventType:

ProcessingError

probableCause:

ConfigurationOrCustomizationError

perceivedSeverity

Major

specificProblem (decimal):

1016674

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.

BSS
Loss

Cells

O&M Capabilities

Degradation

6.6.1 Corrective Actions

NSVCI mismatch

Reconfigure
NSVC with new
NSVCI

SGSN
accepts
NSVCI?

yes
Alarm
solved

no

Contact
System Support

Figure 79: NSVCI mismatch: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

131 / 146

6 MFS Telecommunication Alarms

6.7 Inactive DLCI

eventType:

Communication

probableCause:

TransmissionError

perceivedSeverity

Major

specificProblem (decimal):

1016688

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.

There is no impact on Circuit Switched traffic.

BSS
Loss

Cells

O&M Capabilities

Degradation

6.7.1 Corrective Actions

None.
The PVC fault must be repaired at peer side. The alarm is cleared when the
fault 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 MFS Telecommunication Alarms

6.8 Unknown DLCI

eventType:

ProcessingError

probableCause:

ConfigurationOrCustomizationError

perceivedSeverity

Major

specificProblem (decimal):

1016689

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.

There is no impact on Circuit Switched traffic.

BSS
Loss

Cells

O&M Capabilities

Degradation

6.8.1 Corrective Actions

None.
The DLCI fault must be repaired at peer side. The alarm is cleared when the
DLCI is active in bearer channel status response.
The alarm is also cleared at GPU extraction or loss.

3BK 20417 AAAA PCZZA Ed.09

133 / 146

6 MFS Telecommunication Alarms

6.9 GSL out (B6)

eventType:

Quality of Service

probableCause:

UnderlyingResourceUnavailable

perceivedSeverity

Critical

specificProblem (decimal) for

Release B6:

1012289

Alarm Description:

The BSS no longer has GSLs.

Impact on System:

Signaling with the BSC is impossible. The BSS and its cells are
disabled.
There is no impact on Circuit Switched traffic.

BSS

Cells

O&M Capabilities
-

Loss
Degradation

6.9.1 Corrective Actions

GSL out

Onsite
yes
LapDLink

Unlock LapdDLink,

locked?

check operational and

administrative State

no

Onsite
Alarm on
related
PCMTTP?

yes

Solve PCMTTP
alarm

no

At least
one LapDLink

Investigate on LapDLink

operational?

yes

Alarm
solved

at BSC side
no

Contact
System Support

Figure 80: GSL out: Corrective Actions (B6)

134 / 146

3BK 20417 AAAA PCZZA Ed.09

6 MFS Telecommunication Alarms

6.10 GSL out (B7)

eventType:

Quality of Service

probableCause:

UnderlyingResourceUnavailable

perceivedSeverity

Critical

specificProblem (decimal) for

Release 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 are
disabled for on GPU, as well as the cells supported by this GPU. BSS
and cells GPRS service is lost for this GPU.
There is no impact on Circuit Switched traffic.

BSS

Cells

O&M Capabilities
-

Loss
Degradation

6.10.1 Corrective Actions

GSL out

Onsite

LapDLink

yes

Unlock LapdDLink,
check operational and

locked?

administrative State

no

Onsite
Alarm on
related
PCMTTP?

no

yes

Solve
PCMTTP alarm

At least
one LapDLink
operational?

yes

Alarm
solved

Investigate on LapDLink
at BSC side
no

Contact
System Support

Figure 81: GSL out (B7): Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

135 / 146

6 MFS Telecommunication Alarms

6.11 BVCSig is broken on (B7)

eventType:

Quality of Service

probableCause:

UnderlyingResourceUnavailable

perceivedSeverity

Critical

specificProblem (decimal) for

Release B7:

1012296

Alarm Description:

The BSS BVCSig is down for one GPU, probably because the NSE
has no transfer capability.

Impact on System:

The BSS and all its cells are disabled for one GPU. BSS and cells
GPRS service is lost for this GPU.
There is no impact on Circuit Switched traffic.

BSS

Cells

O&M Capabilities
-

Loss
Degradation

6.11.1 Corrective Actions

BVCSig out

Onsite

NSVC

yes

Unlock NSVC,
check its operational and

locked?

administrative State

no

Onsite
Alarm on
related
PCMTTP?

yes

Solve
PCMTTP alarm

no

At least
one BSC NSVC
operational?

Investigate on NSVC

yes

Alarm
solved

at SGSN side
no

Contact
System Support

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

136 / 146

3BK 20417 AAAA PCZZA Ed.09

6 MFS Telecommunication Alarms

6.12 BVC out

eventType:

Quality of Service

probableCause:

UnderlyingResourceUnavailable

perceivedSeverity

Major

specificProblem (decimal):

1012305

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 is
lost). The cell GPRS service is lost.
There is no impact on Circuit Switched traffic.

BSS
Loss

Cells

O&M Capabilities
-

Degradation

6.12.1 Corrective Actions

None. Investigate at SGSN side; it may be faulty.
The alarm will be cleared when the fault disappears.
The alarm is also cleared at GPU extraction or loss.

3BK 20417 AAAA PCZZA Ed.09

137 / 146

6 MFS Telecommunication Alarms

6.13 LapDLink disabled

eventType:

Communication

probableCause:

LinkFailure

perceivedSeverity

Major

specificProblem (decimal):

1012321

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. Then
the BSS and the cells GPRS service is degraded ( ).
If it is due to a remote BSC problem, both LapDLinks might be in
alarm. Then, the BSS also has a GSL down alarm. The BSS and
cells packet-switched is lost (#).
There is no impact for CircuitSwitched traffic.

BSS
Loss
Degradation

138 / 146

Cells

O&M Capabilities

3BK 20417 AAAA PCZZA Ed.09

6 MFS Telecommunication Alarms

6.13.1 Corrective Actions

LapDLink disabled

Onsite

LapDLink

yes

Unlock LapdDLink,
check operational and

locked?

administrative State

no

Onsite
Alarm on
related
PCMTTP?

yes

Solve PCMTTP
alarm

no

Investigate on LapDLink
at BSC side

At least

yes

one LapDLink

Alarm
solved

operational?

no

Onsite

Replace LapDLink
of PCMTTP

At least
one LapDLink
operational?

yes

Alarm
solved

no

Contact
System Support

Figure 83: LapDLink disabled: Corrective Actions

3BK 20417 AAAA PCZZA Ed.09

139 / 146

6 MFS Telecommunication Alarms

140 / 146

3BK 20417 AAAA PCZZA Ed.09

7 MFS Alarm Additional Information

7 MFS Alarm Additional Information

3BK 20417 AAAA PCZZA Ed.09

141 / 146

7 MFS Alarm Additional Information

7.1 MFS Q3 specific problem identifier

The MFS Q3 specific problem identifier gives for each identifier of alarmId or
component, found in decimal form in the specific problem field, the label that
the 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/subrack

address

1004114

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

unplugged

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

7 MFS Alarm Additional Information

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

7 MFS Alarm Additional Information

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

2000011

component 11

2000012

component 12

2000013

component 13

144 / 146

3BK 20417 AAAA PCZZA Ed.09

7 MFS Alarm Additional Information

2000014

component 14

2000015

component 15

2000016

component 16

2000017

component 17

2000018

component 18

2000019

component 19

2000020

component 20

2000021

component 21

2000022

component 22

2000023

component 23

2000024

component 24

2000025

component 25

2000026

component 26

2001536

Rack 1 Shelf 0 GPU 6

2001537

Rack 1 Shelf 1 GPU 6

2001792

Rack 1 Shelf 0 GPU 7

2001793

Rack 1 Shelf 1 GPU 7

2002048

Rack 1 Shelf 0 GPU 8

2002049

Rack 1 Shelf 1 GPU 8

2002304

Rack 1 Shelf 0 GPU 9

2002305

Rack 1 Shelf 1 GPU 9

2002560

Rack 1 Shelf 0 GPU 10

2002561

Rack 1 Shelf 1 GPU 10

2002816

Rack 1 Shelf 0 GPU 11

2002817

Rack 1 Shelf 1 GPU 11

2003072

Rack 1 Shelf 0 GPU 12

2003073

Rack 1 Shelf 1 GPU 12

2003584

Rack 1 Shelf 0 GPU 14

2003585

Rack 1 Shelf 1 GPU 14

3BK 20417 AAAA PCZZA Ed.09

145 / 146

7 MFS Alarm Additional Information

2003840

Rack 1 Shelf 0 GPU 15

2003841

Rack 1 Shelf 1 GPU 15

2004096

Rack 1 Shelf 0 GPU 16

2004097

Rack 1 Shelf 1 GPU 16

2004352

Rack 1 Shelf 0 GPU 17

2004353

Rack 1 Shelf 1 GPU 17

2004608

Rack 1 Shelf 0 GPU 18

2004609

Rack 1 Shelf 1 GPU 18

2004864

Rack 1 Shelf 0 GPU 19

2004865

Rack 1 Shelf 1 GPU 19

2005120

Rack 1 Shelf 0 GPU 20

2005121

Rack 1 Shelf 1 GPU 20

2005376

Rack 1 Shelf 0 GPU 21

2005377

Rack 1 Shelf 1 GPU 21

Table 4: MFS Q3 Alarm Identifier

146 / 146

3BK 20417 AAAA PCZZA Ed.09