B9 MFS Alarm Dictionary ed04.pdf

Alcatel BSS

MFS Alarm Dictionary

MFS Document

Reference Guide

Release B9

3BK 20931 AAAA PCZZA Ed.04

Status RELEASED

Short title MFS Alarm Dictionary

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

BLANK PAGE BREAK

2 / 267 3BK 20931 AAAA PCZZA Ed.04

Contents

ContentsPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.2 A1353-RA AS Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.3 IMT Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2 GPU/ JBETI Alarm Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.1 PCI system error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.2 PCI data parity error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.3 Ethernet error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.4 GPU loss of contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.5 16E1 serial link failure on GP board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.6 NE1OE supervision error on GP board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.7 GP NE1OE contact error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.8 Voltage out of range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.9 Temperature reaches minor threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.10 Temperature reaches major threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.11 Temperature reaches critical threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.12 DSP error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.13 PLX9054 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402.14 MT90823 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412.15 Time base clock error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422.16 Free run mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442.17 JGGPU2 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472.18 GT-64161A auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482.19 NGISL3 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492.20 IPMC problem on GP board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.21 Applique not present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522.22 DSP Auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532.23 Ethernet Auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542.24 GP Autotest error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562.25 HDLC auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572.26 Framer Auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582.27 MT90820 Matrix auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592.28 BGTCGC auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602.29 BGRECC auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612.30 JGHPI auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622.31 PLX9080 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632.32 NGISL2 auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.33 BGPLTC auto-test error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

3 Irrelevant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673.1 I/O Device Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.2 Ventilation System Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.3 Communications Subsystem Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.4 LAN Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.5 LAN Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.6 Version Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.7 Software Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.8 Software Program Abnormally Terminated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.9 I/O Device Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.10 I/O Device Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.11 I/O Device Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.12 Software Program Abnormally Terminated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883.13 Equipment Malfunction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

3BK 20931 AAAA PCZZA Ed.04 3 / 267

Contents

3.14 Power Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913.15 Adaptor Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933.16 Adaptor Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953.17 Heating/ Ventilation/ Cooling System Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.18 Heating/ Ventilation/ Cooling System Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993.19 Temperature Unacceptable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013.20 Temperature Unacceptable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033.21 Temperature Unacceptable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053.22 Temperature Unacceptable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

4 MFS Telecommunication Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094.1 Remote BSC out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104.2 GSL out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124.3 BVCSig out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144.4 LapDLink is disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164.5 Sleeping Cell Detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184.6 No response from network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204.7 Loss of Gprs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224.8 One BVCsig is out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244.9 All BVCsig are out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264.10 SGSN in user mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284.11 No reply from SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1294.12 NSEI mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314.13 NSVCI mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334.14 Inactive DLCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354.15 Unknown DLCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1364.16 A-GPS server not reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

5 Network Element Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1395.1 Hardware Configuration error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1405.2 Temperature warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1425.3 Temperature alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1445.4 Temperature major alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1465.5 Failure of a Chassis fan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1485.6 Failure of all chassis fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1495.7 Failure of a chassis power unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1505.8 Failure of all power units of a chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1525.9 Card voltage out of range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1545.10 ICMB Access Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1565.11 Station unreachable through LSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1585.12 Loss of contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1605.13 Software configuration error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1625.14 Fatal software error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1645.15 Local Disk I/O error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1665.16 Fatal Hardware Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1675.17 PMC Access Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1695.18 Card failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1715.19 Fatal Ethernet switch error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1735.20 Router communication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1755.21 Non Fatal Router Path failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1775.22 Fatal Router Path failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1795.23 Shared disks error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1815.24 A-GPS router not reachable through LSN 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1825.25 A-GPS router not reachable through LSN 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

6 PCM-TTP Alarm Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1876.1 LOS (Loss Of Signal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1886.2 LFA (Loss Of Frame) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1906.3 AIS (Alarm Indication System) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

4 / 267 3BK 20931 AAAA PCZZA Ed.04

Contents

6.4 CH0-EERH (Excessive Error Rate 10-3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1936.5 RAI (Remote Alarm Indication) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1946.6 DFM (Driver Failure Monitor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1966.7 CRC4-BERH (Excessive Error Rate 10-4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1986.8 CRC4-BERL (Excessive Error Rate 10-6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

7 SUB-RACK Alarm Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2017.1 Board Ethernet error at initialization phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2027.2 Board firmware updated part error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2047.3 Board firmware permanent part error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2067.4 Board DRAM error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2087.5 Board ECC test error during boot phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2107.6 Board target abort during boot phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2127.7 Unlocked board deletion alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2147.8 JBETI address error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2157.9 Fan problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2177.10 Temperature problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2197.11 CNVR converter alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2217.12 48V alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2227.13 2.1V alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2247.14 PRE48 alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2257.15 ACP1 alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2277.16 CALVREF (Cutted Alarm Voltage Reference) alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2297.17 Hub converter problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2317.18 JAETI Failure (slot 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2337.19 JAETI Failure (slot 23) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2357.20 JBETI slot 4 Loss of contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2377.21 JBETI slot 23 Loss of contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2397.22 No JBETI on subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2417.23 MUX supervision error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2437.24 MUX contact error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2457.25 PEM in LIU shelf not operational . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2477.26 LIU board not operational . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2487.27 16E1 serial link failure on MUX board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2497.28 Loss of 48V redundancy for a PEM LIU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2507.29 EALM1 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2527.30 EALM2 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2547.31 EALM3 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2567.32 EALM4 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2587.33 EALM5 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2607.34 EALM6 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2627.35 EALM7 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2647.36 EALM8 external alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

3BK 20931 AAAA PCZZA Ed.04 5 / 267

Tables

TablesTable 1: AS800 Field Replaceable Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Table 2: DS10 Field Replaceable Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Table 3: Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Table 4: Alarm Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Table 5: MFS Alarm Detailed View Window format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

6 / 267 3BK 20931 AAAA PCZZA Ed.04

Preface

PrefacePurpose The purpose of this document is to provide the operator with a structured

method for handling MFS alarm messages.

Whats New In Edition 04Alarms for A9130 MFS Evolution were added.

In Edition 03Severity for alarm Loss of Gprs (Section 4.7) was changed to major.

In Edition 02The new alarm Loss of Gprs (Section 4.7) was added for visibility of GPRSproblems.Corrective action update for alarm Shared disks error (Section 5.23).

In Edition 01The new alarm Shared disks error (Section 5.23) was added for supervisionof CPU, memory and disks of MFS from OMC-R.The new alarm Remote BSC out (Section 4.1) was added.

Audience This document is aimed at telecommunications operators responsible forperforming O&M fault handling and troubleshooting tasks.This document contains a list of all A9135 MFS alarms, and the actionsrequired to remove them.The alarms are displayed at the OMC-R terminal and at the IMT to inform theoperator of system faults.

Assumed Knowledge The operator must be familiar with the following:

Alcatel O&M concepts for the BSS and MFS

Fault management

Use of OMC-R and IMT terminals

Telecommunications techniques including line transmission and switching.

3BK 20931 AAAA PCZZA Ed.04 7 / 267

Preface

8 / 267 3BK 20931 AAAA PCZZA Ed.04

1 Introduction

1 Introduction

This section describes the structure of the A9135 MFS alarm messages.It provides information on:

A1353-RA AS

A9135 MFS Alarm definition format

IMT alarm messages.

3BK 20931 AAAA PCZZA Ed.04 9 / 267

1 Introduction

1.1 OverviewThis alarm dictionary provides additional information that is not displayed in thealarm messages sent to the terminals.The dictionary contains alarm definitions for each alarm type producedby the A9135 MFS.Each definition describes the:

Alarm definition

Alarm description

Impacts on System and Telecom

Methods for further fault isolation

Corrective actions.

1.2 A1353-RA AS Alarm InformationIn the A1353-RA OMC-R, Alarm Surveillance provides an efficient means tocontrol, supervise and manage equipment problems in the MFS.Alarms or Alarm notifications consist of messages sent by network resourcesthat have detected problems or failures in the network. These alarms aredisplayed in lists while alarm counters keep track of statistics. By clicking on analarm in the list, the operator gets detailed information. AS displays informationas described below.

1.2.1 Object IdentificationThe Object Identification identifies the resource that raised the alarm.Object identification gives information about:

The resource type (Object Class)The resource name (Friendly Name). For a board, the Friendly Name alsoshows the boards location by rack, shelf and slot.

The table below lists the different Defense Units with their Instance Friendlyname and the corresponding list of equipment affecting them.

10 / 267 3BK 20931 AAAA PCZZA Ed.04

1 Introduction

1.2.1.1 AS800 Platform

Instance Friendly Name Defense Unit (DU) Field Replaceable Unit

CPU Box A

Local Disk (9GB) Arack1 sb3 aspA A Station A

Pci Board Fan A

CPU Box B

Local Disk (9GB) Brack1 sb3 aspB B Station B

Pci Board Fan B

Shared Hard Disk (9GB) APower Supply Unit (90PS) A

Shared Fan tray

rack1 sb3 aspA dusdisk1A Shared-Disk A

Shared Disk Box

Shared Disk Box

Shared Fan tray

Power Supply Unit (90PS) B

rack1 sb3 aspB dusdisk1B Shared-Disk B

Shared Hard Disk (9GB) Brack1 srLSN1 dulsn1 Hub (1) Hub 500 (1)rack1 srLSN2 dulsn2 Hub (2) Hub 500 (2)

rack1 srTS dutserv Terminal Server IOLAN

Table 1: AS800 Field Replaceable Units

3BK 20931 AAAA PCZZA Ed.04 11 / 267

1 Introduction

1.2.1.2 DS10 Platform

Instance Friendly Name Defense Unit (DU) Field Replaceable Unit

rack1 srSTA1 A Station A CPU Box A

rack1 srSTA2 B Station B CPU Box B

Shared Hard Disk (9GB) Arack1 srSTW1 dusdisk1Bus2 Shared-Disk A *

Storage Works Shelf A

Shared Hard Disk (9GB) Brack1 srSTW2 dusdisk1Bus3 Shared-Disk B *Storage Works Shelf B

rack1 srLSN1 dulsn1 Hub (1) Hub 500 (1)rack1 srLSN2 dulsn2 Hub (2) Hub 500 (2)rack1 srTS dutserv Terminal Server IOLAN

* : For the New DS10/RC40 MFS platform , this defense unit (and then the associated FRU) does not exist.Table 2: DS10 Field Replaceable Units

12 / 267 3BK 20931 AAAA PCZZA Ed.04

1 Introduction

1.2.2 Alarm TypeThe 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

specificProblems: specifies the MFS Q3 specific problem identifier. Tablegives for each identifier (in decimal form) the specific problem field and thelabel of the OMC displays.

The following table describes the five eventTypes.

Event Type Indicates ...

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

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

Processing Error A software or processing fault.

Equipment An equipment fault.

Environmental A problem in the enclosure containing the equipment.

Table 3: Event Types

3BK 20931 AAAA PCZZA Ed.04 13 / 267

1 Introduction

The following table describes the severity levels.

Severity Level Indicates ...

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

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

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

Warning Detection of a potential fault condition, before any significant effects havebeen felt. Action should be taken to further diagnose (if necessary) andcorrect the problem in order to prevent it from becoming a more seriousservice affecting fault.

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

Table 4: Alarm Severity Levels

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

14 / 267 3BK 20931 AAAA PCZZA Ed.04

1 Introduction

1.3 IMT Alarm MessagesThe alarms generated by the A9135 MFS equipment are displayed at the IMTin the GPRS Terminal Window. Whenever A9135 MFS equipment generates analarm, the alarm lists in the GPRS Terminal Window are updated. The numberof alarms in the appropriate list is incremented by one. Also, if the alarm icon isnot already displayed, it appears next to the impacted list. Optionally a beepercan be sent to sound every time a new alarm is raised.The IMT operator uses IMT facilities to identify which equipment is responsiblefor the fault. Like the A1353-RA, the IMT also displays alarms groupedaccording to severity levels. This makes it easier for the operator to prioritizehandling of the alarms.Refer to the IMT on-line help for more information on handling alarms with theIMT. To find a particular alarm definition, use the Advance Search facility inelectronic documentation.

3BK 20931 AAAA PCZZA Ed.04 15 / 267

1 Introduction

1.3.1 Alarm Message FormatsThe GPRS Terminal Window displays alarms in six lists: the Main list and fivelists based on the severity level of the alarm. Refer to Table 4 for a descriptionof severity levels.Detailed information on an alarm is displayed in the Alarm Detailed ViewWindow. This Window is described in table 5.Refer to Tables 3 and 4 for a description of event types and severity levels.

Field/Button Description

Type The following types are used:

Communications

Processing error

Quality of Service

Environment

Equipment.

Severity The following levels are used:

Critical

MajorMinor

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 5: MFS Alarm Detailed View Window format

16 / 267 3BK 20931 AAAA PCZZA Ed.04

2 GPU/ JBETI Alarm Class


This section contains the GPU/ JBETI Alarm Class definitions. The alarms arelisted per specific problems.

3BK 20931 AAAA PCZZA Ed.04 17 / 267


2.1 PCI system error

Q3 Class circuitPack

Alarm Label PCI system error

Alarm Type equipmentAlarm

Probable Cause equipmentMalfunction

Perceived Severity CRITICAL

Specific Problems 1004097

Alarm Description A system error has been detected on PCI bus

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.

BSS Loss Cells O&M Capabilities

Loss - (JBETI)# (GPU)

- (JBETI)# (GPU)

-

Degradation - - X (JBETI)- (GPU)

if no switchover

18 / 267 3BK 20931 AAAA PCZZA Ed.04


2.1.1 Corrective Action

PCI System Error

Alarm on this GPU/JBETI

cleared?

Alarmsolved

ContactSystem Support

no

Replace GPU

Onsite

yes

ReplaceJBETI

Onsite

Or

Figure 1: PCI System Error: Corrective Actions for JBETI

3BK 20931 AAAA PCZZA Ed.04 19 / 267


2.2 PCI data parity error


Alarm Label PCI data parity error





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




Loss - (JBETI)# (GPU)

- (JBETI)# (GPU)

-

Degradation - - X (JBETI)- (GPU)

if no switchover

20 / 267 3BK 20931 AAAA PCZZA Ed.04



PCI Parity Error

Alarm on this GPUcleared?

Alarmsolved


no

Replace GPU

Onsite

yes

Reset allGPU boards by pushbotton

or via IMT

Onsite

Alarm on GPU

cleared?

no

yes Alarmsolved

Alarm on this JBETIcleared?

no

Replace JBETI

Onsite

yes

Reset allJBETI boards by pushbotton

or via IMT

Onsite

Alarm on JBETI

cleared?

no

yes

Alarm on GPU Alarm on JBETI

Figure 2: PCI Parity Error: Corrective Actions for GPU

3BK 20931 AAAA PCZZA Ed.04 21 / 267


2.3 Ethernet error


Alarm Label GPU board has lost ethernet link

Alarm Type communicationsAlarm

Probable Cause lANError

Perceived Severity MINOR


Alarm Description One ethernet link with GPU board is out of service

Impact on System Communication between control station and GPU is degraded.GPRS impact : outage if board replacement .CircuitSwitched Impact : outage if board replacement.


Loss - - -

Degradation - - X

if no switchover

22 / 267 3BK 20931 AAAA PCZZA Ed.04



Haveall GPUs alarms,

but no JBETI alarms?

IsEthernet Link 1

unplugged?

Ethernet error

Replugg unit

Onsite

yes


yes

Component1=1 =>

Termination unit 1

Component1=2 =>

Termination unit 2

HasGPU Ethernet

autotest alarm?

Replace GPU

Haveall GPUs alarm

JBETI lossof contact?

Replace Hub

Replace BATTU

Replace GPU

Replace Hub

Alarmsolved



no

yes

yes

Onsite

Onsite

Onsite

Onsite

no

no

no

no

yes

yes no

Onsite

Alarmsolved

Figure 3: Ethernet error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 23 / 267


2.4 GPU loss of contact


Alarm Label Loss of contact with GPU





Alarm Description The Control Station has lost the Communication Service with theGPU, but JBETI has not detected a loss of contact. The GPU is stillpresent, but in failure.

Impact on System If it is a software problem, the GPU performs a reset-data.

If it is a hardware problem, there is a switchover to the spare GPU.

GPRS impact : outage .CircuitSwitched Impact : None.


Loss # # -

Degradation - - -

if no switchover

24 / 267 3BK 20931 AAAA PCZZA Ed.04



GPU loss of contact


Alarmsolved


no

Replace GPU

Onsite

yes

IsGPU

disabled?

no

yes IsGPU

restarted?

no

yes

Checksoftwareversions

OMCR

Reinstallcorrect

softwareversion(s)

OMCR


no

yes


Alarmsolved

Alarmsolved

Figure 4: GPU loss of contact: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 25 / 267


2.5 16E1 serial link failure on GP board


Alarm Label 16E1 serial link failure on GPU board





Alarm Description The 16E1 serial link chip of the GP board is out of service

Impact on System A GP switchover is triggered by the system that should lead to a shortGPRS outage.


Loss

Degradation

if no switchover

26 / 267 3BK 20931 AAAA PCZZA Ed.04


2.5.1 Corrective Actions16E1 serial link failure

on GP board


Alarmsolved


no

Replace GPU

Onsite

yes

Navigate from AS to MFSUSM to identify the

faulty GPU

Figure 5: 16E1 serial link failure on GP board: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 27 / 267


2.6 NE1OE supervision error on GP board


Alarm Label NE1OE supervision error on GPU board





Alarm Description No NE1OE supervision frames received by the GP board.

Impact on System The system will trigger a GP switch-over that leads to a short GPRSoutage.Otherwise if standby GP, then the system will trigger a reset of the GPwith no impact on system.


Loss

Degradation

if no switchover

28 / 267 3BK 20931 AAAA PCZZA Ed.04


2.6.1 Corrective ActionsNE1OE supervision error on GP board


Alarmsolved


no

Replace GPU

Onsite

yes

Switchover GPU


yes

no


Reset GPU

yes

no


faulty GPU

Figure 6: NE1OE supervision error on GP board: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 29 / 267


2.7 GP NE1OE contact error


Alarm Label GPU NE1OE contact error

Alarm Type processingErrorAlarm

Probable Cause configurationOrCustomizationError

Perceived Severity MAJOR


Alarm Description The OMCP has lost the contact with the NE1OE processor of the GPboard and cant supervise it anymore.

Impact on System If the failure occurred on a active GP, a switchover of GP board istriggered by the system and it will lead to a short GPRS outage.

If the failure occurred on the standby GP, no impact on traffic.


Loss

Degradation

if no switchover

30 / 267 3BK 20931 AAAA PCZZA Ed.04


2.7.1 Corrective Actions

GP NE1OE contact error


Alarmsolved


no

Reset GPU manually

Onsite

yes

IP configuration ok? Correct IP configuration


no

no

yes

yes

Figure 7: GP NE1OE contact error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 31 / 267


2.8 Voltage out of range


Alarm Label Voltage out of range


Probable Cause powerProblem



Alarm Description IPMC detects that the board voltage is not compatible with ATCA shelf.The board will not start.

Impact on System No GPRS nor Circuit Switched on all the E1s carried to this XPU.


Loss

Degradation

if no switchover

32 / 267 3BK 20931 AAAA PCZZA Ed.04



Voltage out of range


Alarmsolved


no

Replace GPU

Onsite

yes


faulty GPU

Figure 8: Voltage out of range: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 33 / 267


2.9 Temperature reaches minor threshold


Alarm Label Temperature reaches minor threshold

Alarm Type environmentalAlarm

Probable Cause temperatureUnacceptable



Alarm Description HPI detects that the temperature of the board has reached a minorthreshold.

Impact on System No impact.


Loss

Degradation

if no switchover

2.9.1 Corrective ActionsTemperature reaches

minor threshold


Alarmsolved


no

Check fans and room

temperature

Onsite

yes

Figure 9: Temperature reaches minor threshold: Corrective Actions

34 / 267 3BK 20931 AAAA PCZZA Ed.04


2.10 Temperature reaches major thresholdQ3 Class circuitPack

Alarm Label Temperature reaches major threshold





Alarm Description HPI detects that the temperature of the board has reached a majorthreshold.

Impact on System No impact.


Loss

Degradation

if no switchover

3BK 20931 AAAA PCZZA Ed.04 35 / 267



major threshold


Alarmsolved


no

Replace GPU

Onsite

yes

Replace fanFans ok?

Room temperature ok?



Correct room temperature

yes

yes

yes

yes

no

no

no

no


faulty GPU

Figure 10: Temperature reaches major threshold: Corrective Actions

36 / 267 3BK 20931 AAAA PCZZA Ed.04


2.11 Temperature reaches critical threshold


Alarm Label Temperature reaches critical threshold





Alarm Description IPMC chip detects that the temperature of the board has reached acritical threshold and the board has been powered off.

Impact on System As soon as the board is powered off, a switch-over is triggered by thesystem with no CS outage and a short GPRS outage.If it is the spare board, the board is just powered off with no telecomimpacts.


Loss

Degradation

if no switchover

3BK 20931 AAAA PCZZA Ed.04 37 / 267



critical threshold


Alarmsolved


no

Replace GPU

Onsite

yes

Replace fanFans ok?

Room temperature ok?



Correct room temperature

yes

yes

yes

yes

no

no

no

no


faulty GPU

Figure 11: Temperature reaches critical threshold: Corrective Actions

38 / 267 3BK 20931 AAAA PCZZA Ed.04


2.12 DSP error


Alarm Label DSP offline


Probable Cause processorProblem



Alarm Description DSP is faulty


The GPRS traffic is interrupted during the GPU switchover.


Loss # # -

Degradation - - -

if no switchover


DSP error


Alarmsolved


no

Replace GPU

Onsite

yes

Figure 12: DSP error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 39 / 267


2.13 PLX9054 auto-test error


Alarm Label PLX9054 auto-test error





Alarm Description Auto-test discovered a problem on the PLX9054 component




Loss X X -

Degradation - - -

if no switchover


PLX9054 autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

Figure 13: PLX9054 auto-test error: Corrective Actions

40 / 267 3BK 20931 AAAA PCZZA Ed.04


2.14 MT90823 auto-test error


Alarm Label MT90823 auto-test error





Alarm Description Auto-test discovered a problem on the MT90823 Matrix component




Loss X X -

Degradation - - -

if no switchover


MT90823 autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

Figure 14: MT90823 auto-test error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 41 / 267


2.15 Time base clock error


Alarm Label Time base clock offline


Probable Cause gsmLossOfSynchronisation



Alarm Description The MFS is in centralized synchronization mode.

All synchronizing PCM are lost on first synchronizing GPU.Automatic switching of the GPU on the other synchronising GPU.

Impact on System Synchronising clock of all the PCM of the sub-rack are no morebackuped


Loss - - -

Degradation - - -

if no switchover

42 / 267 3BK 20931 AAAA PCZZA Ed.04



Time base clock offline

Does Sync. PCM recover?

Alarmsolved


Replace GPU

Onsite

yes

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

Congigure new sync. PCM for

GPU

MFS only: add Gb PCM to Transcoder or

SGSN

PCM in service?

PCM in service?yes

yes

no

no

no

Alarmsolved

Alarmsolved

Figure 15: Time base clock offline: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 43 / 267


2.16 Free run mode


Alarm Label On free run mode


Probable Cause gsmLossOfSynchronisation



Alarm Description The MFS is in autonomous synchronization mode.

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

The alarm is per individual GPU.

Impact on System The transmission quality on the PCM is not sufficient to provide acorrect synchronization. Telcom traffic is lost.

GPRS impact : Outage .CircuitSwitched Impact : Outage.LCS Impact : Loss of service.


Loss X X -

Degradation - - X

if no switchover

44 / 267 3BK 20931 AAAA PCZZA Ed.04



Free run mode

Does Sync. PCM recover?

Alarmsolved


Replace GPU

Onsite

yes

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

Congigure new sync. PCM for

GPU

MFS only: add Gb PCM to Transcoder or

SGSN

PCM in service?

PCM in service?yes

yes

no

no

no

Alarmsolved

Alarmsolved

Are TX and RX cables crossed ?

yes

no

Alarmsolved

At GPU Siteor

at Peer Entity Side

Figure 16: Free run mode: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 45 / 267


46 / 267 3BK 20931 AAAA PCZZA Ed.04


2.17 JGGPU2 auto-test error


Alarm Label JGGPU2 auto-test error





Alarm Description Auto-test discovered a problem on the JGGPU2 component




Loss X X -

Degradation - - -

if no switchover


JGGPU2 autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

Figure 17: JGGPU2 auto-test error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 47 / 267


2.18 GT-64161A auto-test error


Alarm Label GT-64161A auto-test error





Alarm Description Auto-test discovered a problem on the GT-64161A component




Loss X X -

Degradation - - -

if no switchover


GT64161A autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

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

48 / 267 3BK 20931 AAAA PCZZA Ed.04


2.19 NGISL3 auto-test error


Alarm Label NGISL3 auto-test error





Alarm Description Auto-test discovered a problem on the NGISL3 component

Impact on System GPU start goes on, but O&M service is degraded for GPU supervision(no JBETI alarms).

GPRS impact : None.CircuitSwitched Impact : None.


Loss - - -

Degradation - - X

if no switchover


NGISL3 autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

Figure 19: NGISL3 auto-test error: Corrective Action (GPU2 only)

3BK 20931 AAAA PCZZA Ed.04 49 / 267


2.20 IPMC problem on GP board


Alarm Label IPMC problem on GPU board





Alarm Description The system has detected an IPMC failure on the GP board

Impact on System GPRS impact : outage during the switchover .CircuitSwitched Impact : None.


Loss

Degradation

if no switchover

50 / 267 3BK 20931 AAAA PCZZA Ed.04


2.20.1 Corrective ActionsIPMC problem on GP board


Alarmsolved


no

Replace GPU

Onsite

yes

Switchover GP


yes

no


faulty GPU

Figure 20: IPMC problem on GP board: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 51 / 267


2.21 Applique not present


Alarm Label Applique not present


Probable Cause backplaneFailure



Alarm Description Applique JAE1 not present

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

GPRS impact : outage .CircuitSwitched Impact : outage.


Loss X X -

Degradation - - -

if no switchover


Applique presence

Alarm on assoc. GPU

cleared?

Alarmsolved


no

InsertJAE1

Onsite

yes

Figure 21: Applique presence: Corrective Actions

52 / 267 3BK 20931 AAAA PCZZA Ed.04


2.22 DSP Auto-test error


Alarm Label DSP auto-test error


Probable Cause processorProblem



Alarm Description Auto-test discovered a problem on the DSP




Loss - - -

Degradation - - -

if no switchover

2.22.1 Corrective ActionNone.

3BK 20931 AAAA PCZZA Ed.04 53 / 267


2.23 Ethernet Auto-test error


Alarm Label Ethernet Link auto-test error





Alarm Description Auto-test discovered a problem on one GPU ethernet component

Impact on System GPRS impact :None.CircuitSwitched Impact : None.


Loss - - -

Degradation - - -

if no switchover

54 / 267 3BK 20931 AAAA PCZZA Ed.04



Ethernet autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

Triggerswitchover

Component1=1 =>

Termination unit 1

Component1=2 =>

Termination unit 2

Figure 22: Ethernet auto-test error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 55 / 267


2.24 GP Autotest error


Alarm Label GPU Autotest error





Alarm Description Autotest discovered a problem on a GP component

Impact on System The GP board goes disabled and there is a switchover to a spare GP.


Loss X X -

Degradation - - -

if no switchover


MXGP Autotest error


Alarmsolved


no

Replace GPU

Onsite

yes


faulty GPU

Figure 23: MX-GP Autotest error: Corrective Action

56 / 267 3BK 20931 AAAA PCZZA Ed.04


2.25 HDLC auto-test error


Alarm Label HDLC auto-test error





Alarm Description Auto-test discovered a problem on the HDLC component




Loss X X -

Degradation - - -

if no switchover


HDLC autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

Figure 24: HDLC auto-test error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 57 / 267


2.26 Framer Auto-test error


Alarm Label Framer auto-test error





Alarm Description Auto-test discovered a problem on the Framer component.




Loss # # -

Degradation # # -

if no switchover


Framer autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

Figure 25: Framer auto-test error: Corrective Actions

58 / 267 3BK 20931 AAAA PCZZA Ed.04


2.27 MT90820 Matrix auto-test error


Alarm Label MT90820 matrix auto-test error





Alarm Description Auto-test discovered a problem on the MT90820 Matrix component




Loss X X -

Degradation - - -

if no switchover


Matrix autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

Figure 26: Matrix auto-test error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 59 / 267


2.28 BGTCGC auto-test error


Alarm Label BGTCGC auto-test error





Alarm Description Auto-test discovered a problem on the BGTCGC component




Loss X X -

Degradation - - -

if no switchover


BGTCGC autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

Figure 27: BGTCGC auto-test error: Corrective Actions

60 / 267 3BK 20931 AAAA PCZZA Ed.04


2.29 BGRECC auto-test error


Alarm Label BGRECC auto-test error





Alarm Description Auto-test discovered a problem on the BGRECC component




Loss X X -

Degradation - - -

if no switchover


BGRECC autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

Figure 28: BGRECC auto-test error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 61 / 267


2.30 JGHPI auto-test error


Alarm Label JGHPI auto-test error





Alarm Description Auto-test discovered a problem on the JGHPI component




Loss X X -

Degradation - - -

if no switchover


JGHPI autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

Figure 29: JGHPI auto-test error: Corrective Actions

62 / 267 3BK 20931 AAAA PCZZA Ed.04


2.31 PLX9080 auto-test error


Alarm Label PLX9080 auto-test error





Alarm Description Auto-test discovered a problem on the PLX9080 component




Loss X X -

Degradation - - -

if no switchover


PLX9080 autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

Figure 30: PLX9080 auto-test error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 63 / 267


2.32 NGISL2 auto-test error


Alarm Label NGISL2 auto-test error





Alarm Description Auto-test discovered a problem on the NGISL2 component

Impact on System GPU start goes on, but O&M service is degraded for GPU supervision(no JBETI alarms).

GPRS impact : None.CircuitSwitched Impact : None.


Loss - - -

Degradation - - X

if no switchover

64 / 267 3BK 20931 AAAA PCZZA Ed.04



NGISL2 autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

Triggerswitchover

3BK 20931 AAAA PCZZA Ed.04 65 / 267


2.33 BGPLTC auto-test error


Alarm Label BGPLTC auto-test error





Alarm Description Auto-test discovered a problem on the BGPLTC component




Loss X X -

Degradation - - -

if no switchover


BGPLTC autotest error


Alarmsolved


no

Replace GPU

Onsite

yes

Figure 31: BGPLTC auto-test error: Corrective Actions

66 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3 Irrelevant

This section contains the Irrelevant definitions. The alarms are listed perspecific problems.

3BK 20931 AAAA PCZZA Ed.04 67 / 267

3 Irrelevant

3.1 I/O Device Error

Q3 Class NectarCircuitPack

Alarm Label I/O Device Error


Probable Cause inputOutputDeviceError



Alarm Description TOMAS has detected an input/output device failure of the terminalserver.

Impact on System Some administrative commands cannot be executed.The terminal Server availabilityStatus is failed.There is no Impact on the telecom service.


Loss

Degradation

if no switchover

68 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3.1.1 Corrective ActionI/O device error

on:

Alarmsolved


Alarm severity?

MinorMajorReplace local disk, SCSI bus

or coupler

I/O operational?

no

yes

Station

Replace Hub, ethernet link

Hub/terminal or terminal

Terminal concentrator

Replace shared disk, shareddisk box

Replace SCSI bus

Execute disk_recover

to resynchronize shared disk

Shared disk

SCSIalarm

events?

no

yes Solve SCSI alarm

OnSite

OnSite

OnSite

OnSite

OnSite

Replace SCSI cables

Figure 32: I/O device error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 69 / 267

3 Irrelevant

3.2 Ventilation System Failure


Alarm Label Ventilation System Failure

Alarm Type

Probable Cause ventilationsSystemFailure



Alarm Description The two fans of a fan tray are failed

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


Loss

Degradation

if no switchover

70 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3.2.1 Corrective ActionVentilation system

failure

Alarmsolved


Adaptoroperational?

no

yes

establish correct fan tray power supply

Replace fan tray

Fan tray power supply operational?

no

yes

Figure 33: Ventilation system failure: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 71 / 267

3 Irrelevant

3.3 Communications Subsystem Failure


Alarm Label Communications Subsystem Failure


Probable Cause communicationsSubsystemFailure



Alarm Description The station cannot be contacted via the terminal server and its remoteaccess.

Impact on System The station availabilityStatus is degraded.

No O&M ImpactNo telecom Impact


Loss

Degradation

if no switchover

72 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3.3.1 Corrective ActionCommunication

subsystem failure

Is link operational?

Alarmsolved


no

yes

External router link

operational?

no

yes

Replace/repair terminal/station link

Onsite

Replace/repair external router link

Onsite

Link terminal concentrator to station

operational

no

yes


Stationis

locked?

no

yes Unlockstation

3BK 20931 AAAA PCZZA Ed.04 73 / 267

3 Irrelevant

3.4 LAN Error


Alarm Label LAN Error





Alarm Description The active station cannot contact the standby station via this Hub.

Impact on System The station availabilityStatus is degraded.

No O&M ImpactNo telecom Impact


Loss

Degradation

if no switchover

74 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3.4.1 Corrective ActionIAN error


Alarmsolved


no

yes

Coupler of station

faulty?

no

yes

Replace/repair link station to

LSN Hub

Station

Replace coupler

Station

Link between station and LSN Hub

operational?

no

yes

Hub power supply

operational?

no

yes

Establish correct Hub power supply

Hub

Link & network

operational?

no

yes

Establish correct link &

network

Hub


Figure 34: IAN error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 75 / 267

3 Irrelevant

3.5 LAN Error


Alarm Label LAN Error





Alarm Description At least one station cannot communicate on a LSN link.

Impact on System LSN availabiltyStatus is failed.There is no impact on telecom service.


Loss

Degradation

if no switchover

76 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3.5.1 Corrective ActionIAN error


Alarmsolved


no

yes

Coupler of station

faulty?

no

yes

Replace/repair link station to

LSN Hub

Station

Replace coupler

Station

Link between station and LSN Hub

operational?

no

yes

Hub power supply

operational?

no

yes

Establish correct Hub power supply

Hub

Link & network

operational?

no

yes

Establish correct link &

network

Hub


Figure 35: IAN error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 77 / 267

3 Irrelevant

3.6 Version Mismatch


Alarm Label Version Mismatch


Probable Cause versionMismatch



Alarm Description A station cannot be installed by TOMAS because the version on theactive station is not the same that in the standby station.

Impact on System The station availabilityStatus is failed.

O&M service is not securedNo telecom Impact


Loss

Degradation

if no switchover

3.6.1 Corrective ActionVersion mismatch

Alarmsolved


Installed correct software

version?

no

yes

Reinstall correct version

Figure 36: Version mismatch: Corrective Actions

78 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3.7 Software Error


Alarm Label Software Error


Probable Cause softwareError



Alarm Description The station cannot be installed by TOMAS because the station failsduring the initialization .




Loss

Degradation

if no switchover

3BK 20931 AAAA PCZZA Ed.04 79 / 267

3 Irrelevant


Software error

Alarmsolved


Installed correct software

version?

no

yes

Error occures during

normalworking?

no

yes

Verify that the station has not been stopped voluntarily

(by a third party)

Software error

solved?

Alarmsolved


no

yes

Analyze the Nectar logs and the application logs

Reinstall the local disk

Verify the two hubs/switches

Reinstall correct version of UNIX, NECTAR, application

Figure 37: Software error: Corrective Actions

80 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3.8 Software Program Abnormally Terminated


Alarm Label Software Program Abnormally Terminated


Probable Cause softwareProgramAbnormallyTerminated



Alarm Description TOMAS has detected a SW failure on a station. This alarm occursduring the station initialization.

Impact on System The station is temporarily not available.The station availabilityStatus is OK.

O&M service is interrupted because of the control station switchover.Restart is normally in progress.No telecom Impact


Loss

Degradation

if no switchover

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

3BK 20931 AAAA PCZZA Ed.04 81 / 267

3 Irrelevant








Alarm Description TOMAS has detected an input/output device failure of a local disk.

Impact on System The station associated to the local disk is stopped.The station availabilityStatus is failed.



Loss

Degradation

if no switchover

82 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3.9.1 Corrective ActionI/O device error

on:

Alarmsolved


Alarm severity?

MinorMajorReplace local disk, SCSI bus

or coupler

I/O operational?

no

yes

Station

Replace Hub, ethernet link

Hub/terminal or terminal

Terminal concentrator

Replace shared disk, shareddisk box

Replace SCSI bus



Shared disk

SCSIalarm

events?

no


OnSite

OnSite

OnSite

OnSite

OnSite

Replace SCSI cables

Figure 38: I/O device error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 83 / 267

3 Irrelevant








Alarm Description TOMAS has detected an input/output device failure of a shared disk.

Impact on System The data on the shared disks are not backuped.The Shared disk availabilityStatus is failed.There is no Impact on the telecom service.


Loss

Degradation

if no switchover

84 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant


I/O device error

Alarmsolved


I/O operational?

no

yes

Replace shared disk, shareddisk box or SCSI cables

SCSIalarm

events?

no


OnSite

Figure 39: I/O Device Error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 85 / 267

3 Irrelevant








Alarm Description TOMAS has detected an input/output device failure of a shared disk.

Impact on System The data on the shared disks are not backuped.The Shared disk availabilityStatus is failed.There is no Impact on the telecom service.


Loss

Degradation

if no switchover

86 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant


I/O device error

Alarmsolved


I/O operational?

no

yes

Replace SCSI bus



OnSite

OnSite

Figure 40: I/O Device Error: Corrective Actions

3BK 20931 AAAA PCZZA Ed.04 87 / 267

3 Irrelevant

3.12 Software Program Abnormally Terminated


Alarm Label Software Program Abnormally Terminated


Probable Cause softwareProgramAbnormallyTerminated



Alarm Description TOMAS has detected a SW failure on a station. This alarm occursduring the station initialization.

Impact on System The station is temporarily not available.The station availabilityStatus is OK.

O&M service is interrupted because of the control station switchover.Restart is normally in progress.No telecom Impact


Loss

Degradation

if no switchover

3.12.1 Corrective ActionsNone.The station is down. The automatic restart is in progress.Check the log of the station to be informed of the failure reason.

88 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3.13 Equipment Malfunction


Alarm Label Equipment Malfunction





Alarm Description This alarm is associated to the object associated to the FLT program.


O&M service is not securedNo Telecom Impact


Loss

Degradation

if no switchover

3BK 20931 AAAA PCZZA Ed.04 89 / 267

3 Irrelevant


Equipment malfunction

Alarmsolved


Replace faulty FRU given in additional text:

Router/Station

operational?

no

yes

Onsite

Station reboots autonomously,

After reboot station should be

" unlocked/ disabled/ initializing"

Replace faulty StorageWorks

shelf

Replace faulty power supply

Replace faulty CPU box

Onsite Onsite Onsite

OR OR

Select the station

Execute clear_alarm

Figure 41: Equipment malfunction: Corrective Actions

90 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3.14 Power Problem


Alarm Label Power Problem


Probable Cause powerProblem



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 local station is not ventilated.

Impact on System The data on the shared disks are not secured.The shared disk availabilityStatus is failed.

No Telecom Impact


Loss

Degradation

if no switchover

3BK 20931 AAAA PCZZA Ed.04 91 / 267

3 Irrelevant


Power problem

Alarmsolved


Shared disk powered?

no

yes

Establish correct shared disk power supply

(switch power on etc)

Subrack powered?

no

yes

Establish correct subrack power supply(switch power on etc)

Alarmsolved

Figure 42: Power problem: Corrective Actions

92 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3.15 Adaptor Error


Alarm Label Adaptor Error


Probable Cause adapterError



Alarm Description This alarm is associated to an access error on shared SCSI bus.

Impact on System The data on the shared disks are not secured.The shared disk availabilityStatus is failed.

No telecom Impact


Loss

Degradation

if no switchover

3BK 20931 AAAA PCZZA Ed.04 93 / 267

3 Irrelevant


Adaptor erroron:

Alarmsolved


Reboot the station

Adaptoroperational?

no

yes

Replace SCSI coupler, SCSI cable or CPU box as given by FLT result

Alarmsolved

Adaptoroperational?

no

yes

Figure 43: Adaptor Error: Corrective Actions

94 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3.16 Adaptor Error


Alarm Label Adaptor Error


Probable Cause adapterError



Alarm Description This alarm is associated to a component error in the shared disk box

Impact on System The whole system is available but the temperature and the powersupply of the shared disks are no more monitored.

There is no Impact on the telecom service.


Loss

Degradation

if no switchover

3BK 20931 AAAA PCZZA Ed.04 95 / 267

3 Irrelevant

3.16.1 Corrective ActionAdaptor error

on:

Alarmsolved


Reboot the station

Adaptoroperational?

no

yes

Station

Replace GEM chip

Replace SCSI coupler

Shared disk

SCSI coupler

operational?

no

yes

Replace SCSI coupler, SCSI cable or CPU box as given by FLT result

GEM chip

operational?

no

yes

Replace SCSI cable

SCSI cableok?

no

yes


Alarmsolved

Adaptoroperational?

no

yes

Figure 44: Adaptor error: Corrective Actions

96 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3.17 Heating/ Ventilation/ Cooling System Problem


Alarm Label Cooling System Problem


Probable Cause heatingOrVentilationOrCoolingSystemProblem



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

Impact on System The station is powered off by the system.The station availabilityStatus is failed.

O&M service is not securedNo Telecom Impact


Loss

Degradation

if no switchover

3BK 20931 AAAA PCZZA Ed.04 97 / 267

3 Irrelevant

3.17.1 Corrective ActionHeating/ventilation/cooling

system problem on:

Alarmsolved


Replace PCI fan or CPU fan

Fanoperational?

no

yes

Station

Replace fan tray

Shared disk

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

98 / 267 3BK 20931 AAAA PCZZA Ed.04

3 Irrelevant

3.18 Heating/ Ventilation/ Cooling System Problem


Alarm Label Cooling System Problem


Probable Cause heatingOrVentilationOrCoolingSystemProblem



Alarm Description The file management has detected the failure of one fan of a fan tray.

Impact on System The system is available but only one fan in the fan tray is available.

There is no impact on the telecom service.


Loss

Degradation

if no switchover

3BK 20931 AAAA PCZZA Ed.04 99 / 267

3 Irrelevant

3.18.1 Corrective ActionHeating/ventilation/cooling

system problem on:

Alarmsolved


Replace

Date post:	14-Nov-2015
Category:	Documents
Upload:	vu-anh-tuan
View:	20 times
Download:	11 times

B9 MFS Alarm Dictionary ed04.pdf

Documents