b9 a1353-ra omc-r alarm dictionary ed01.pdf

Alcatel BSS

A1353-RA OMC-R Alarm

Dictionary

OMC Document

Reference Guide

Release B9

3BK 20905 AAAA PCZZA Ed.01

Status RELEASED

Short title A1353-RA 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 / 26 3BK 20905 AAAA PCZZA Ed.01

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2 Alarm Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.2.1 Alarm Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2.2 Alarm Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2.3 Impact on System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2.4 Corrective Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Communications Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1 Internal Link Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2 OMC-BSC Link Failure: BSC Unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3 OMC-BSC Link Failure: First Link Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.4 OMC-BSC Link Failure: Second Link Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.5 External Communication Link Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3 O&M Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.1 Hardware Audit Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.2 Alarm/State Audit Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.3 DLS Backup Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3BK 20905 AAAA PCZZA Ed.01 3 / 26

Figures

FiguresFigure 1: Internal Link Failure: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Figure 2: OMC-BSC Link Failure: BSC Unreachable Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Figure 3: OMC-BSC Link Failure: First Link Down Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Figure 4: OMC-BSC Link Failure: Second Link Down Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Figure 5: External Communication Link Failure: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Figure 6: Hardware Audit Failed: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Figure 7: Alarm/State Audit Failed: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Figure 8: DLS Backup Failed: Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4 / 26 3BK 20905 AAAA PCZZA Ed.01

Preface

Preface

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

This document contains a list of all A1353-RA alarms, and the actions requiredto remove them.

It is not intended to describe all alarms generated by other subsystem such asBTS, MFS, BSC etc. components.

What’s New In Edition 01The new alarm OMC-BSC Link Failure: Second Link Down (Section 2.4)was added.Alarm OMC-BSC Link Failure: BSC Unreachable (Section 2.2) was updated.Alarm OMC-BSC Link Failure: First Link Down (Section 2.3) was updated.The new alarm DLS Backup Failed (Section 3.3) was added.Description improvement for OMC-BSC Link Failure: BSC Unreachable(Section 2.2) and OMC-BSC Link Failure: First Link Down (Section 2.3)alarms due to refinement of X25 alarms (discrimination between network andapplicative alarms).

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

Assumed Knowledge The operator must be familiar with the following:

Alcatel O&M concept

Use of OMC-R terminals.

3BK 20905 AAAA PCZZA Ed.01 5 / 26

Preface

6 / 26 3BK 20905 AAAA PCZZA Ed.01

1 Introduction

1 Introduction

This section describes the structure of alarm messages.

3BK 20905 AAAA PCZZA Ed.01 7 / 26

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 A1353-RA:

Communication alarms

O&M alarms.

1.2 Alarm DefinitionEach alarm definition describes the:

Alarm type

Alarm description

Impact on System

Corrective actions.

1.2.1 Alarm Type

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

This information is sub-divided into:

eventTypeidentifies the basic type of the alarm. Table 1 gives the possible valuesfor eventType.

probableCause

perceivedSeveritygives the severity level of the alarm. Table 2 gives the possible values forperceivedSeverity.

evenType Indicates....

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

Processing Error A software or processing fault.

Table 1: Event Types

8 / 26 3BK 20905 AAAA PCZZA Ed.01

1 Introduction

Severity Level Indicates...

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

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

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

Warning Detection of a potential fault condition. Action should be taken to diagnose andcorrect the problem to avoid a more serious fault condition.

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

Table 2: Alarm Severity Levels

All alarms always give the date and time of the alarm. An alarm may alsocontain optional information, such as the notification id.

1.2.2 Alarm Description

It gives a short description of the problem indicated by this alarm.

1.2.3 Impact on System

It gives a short description of the impact on the system due to the problemindicated by this alarm.

1.2.4 Corrective Action

To solve the current alarm a graphical workflow chart is used. It shows therequired procedures by checks, tests and actions to determine the fault andfinally to solve the alarm.

By clicking on a dedicated action field, a link to the detailed description of thetask will be opened when available.

3BK 20905 AAAA PCZZA Ed.01 9 / 26

1 Introduction

10 / 26 3BK 20905 AAAA PCZZA Ed.01

2 Communications Alarms


This section describes the meaning and corrective actions for each alarmraised on the communication with the supervised equipment (BTS, BSC, MFS).

3BK 20905 AAAA PCZZA Ed.01 11 / 26


2.1 Internal Link Failure

eventType Communications

probableCause CommunicationSubsystemFailure

Alarm Number 500000

perceivedSeverity Major

Alarm Description Due to a failure in OMC-R internal processes, the OMC-R is not able tocommunicate with a BSC equipment.

Impact on System The BSC and all BTS related equipment is no more supervised.

The following flowchart describes the associated corrective actions for thisalarm.

Internal Link Failure

Processesmarked

red?

Restartstopped

process(es)

OMC−R

Yes

Re−checkprocess(es).Wait 30 min

to start RNUSM if RNIM was

stopped

OMC−R

Do restartedProcess(es)stop again?

Alarmsolved

ContactSystem Support

No

No

CheckOMC

process(es)

OMC−R


Yes

Figure 1: Internal Link Failure: Corrective Actions

12 / 26 3BK 20905 AAAA PCZZA Ed.01


2.2 OMC-BSC Link Failure: BSC Unreachable



Alarm Number 500001

perceivedSeverity Critical

Alarm Description Due to a wrong configuration or OMC hardware failure or network erroror BSC response time-out, the OMC is not able to communicate withthe BSC equipment. The alarm is raised when the BSC cannot bereached: both links are not usable (in case of BSC redundancy) or linknot usable (if no BSC redundancy).

Impact on System The BSC and all BTS related equipment are no more supervised.

3BK 20905 AAAA PCZZA Ed.01 13 / 26



OMC−BSC Link Failure: BSC Unreachable

X.25 configuration correct?

Check X.25 configuration with X.25 tool

OMC−R

Yes

X.25 linkin service?

Alarmsolved


No

Yes

Re−checkX.25 link

OMC−R

No

X.25 network ok?

No Fix X.25 network problems

Yes

OMC−R X.25 boards ok?

No

Yes

Check OMC−R X.25 boards

Correct X.25 configuration if

required

OMC−R

On−site

BSC equipment ok?

Fix BSC equipmentproblems

No

Yes

Figure 2: OMC-BSC Link Failure: BSC Unreachable Corrective Actions

14 / 26 3BK 20905 AAAA PCZZA Ed.01


2.3 OMC-BSC Link Failure: First Link Down



Alarm Number 500002

perceivedSeverity Minor

Alarm Description Due to a wrong configuration or OMC hardware failure or networkerror or BSC response time-out, the OMC is not able to communicatewith the BSC equipment through the first of the two X25 links in caseof BSC redundancy. The BSC and all related BTS equipments aresupervised. The alarm is raised in order to warn the operator that thefirst link is down and must be repaired.

Impact on System First link is down between OMC and BSC in case of BSC redundancy.

If there is no X.25 redundancy, the BSC and all BTS related equipmentis no more supervised.

With X.25 redundancy there is no impact.


3BK 20905 AAAA PCZZA Ed.01 15 / 26


OMC−BSC Link Failure: First Link

Down



OMC−R

Yes


Alarmsolved


No

Yes

Re−checkX.25 link

OMC−R

No

X.25 network ok?


Yes


No

Yes



required

OMC−R

On−site

BSC equipment ok?


No

Yes

Figure 3: OMC-BSC Link Failure: First Link Down Corrective Actions

16 / 26 3BK 20905 AAAA PCZZA Ed.01


2.4 OMC-BSC Link Failure: Second Link Down



Alarm Number 500003

perceivedSeverity Minor

Alarm Description Due to a wrong configuration or OMC hardware failure or network erroror BSC response time-out, the OMC is not able to communicate withthe BSC equipment through the second of the two X25 links in caseof BSC redundancy. The BSC and all related BTS equipments aresupervised. The alarm is raised in order to warn the operator that thesecond link is down and must be repaired.

Impact on System Second link is down between OMC and BSC in case of BSCredundancy.

If there is no X.25 redundancy, the BSC and all BTS related equipmentis no more supervised.

With X.25 redundancy there is no impact.

3BK 20905 AAAA PCZZA Ed.01 17 / 26



OMC−BSC Link Failure: Second Link

Down



OMC−R

Yes


Alarmsolved


No

Yes

Re−checkX.25 link

OMC−R

No

X.25 network ok?


Yes


No

Yes



required

OMC−R

On−site

BSC equipment ok?


No

Yes

Figure 4: OMC-BSC Link Failure: Second Link Down Corrective Actions

18 / 26 3BK 20905 AAAA PCZZA Ed.01


2.5 External Communication Link Failure



Alarm Number 5000001


Alarm Description Due to:

a wrong configuration or

an OMC-R hardware failure or

a network error or

an MFS response timeout.

The OMC-R is not able to communicate with the MFS equipment.

Impact on System The MFS related equipment is no more supervised.

3BK 20905 AAAA PCZZA Ed.01 19 / 26



Ext. Comm. Link Failure

X.25 OMC link

address at MFS correct?

CorrectX.25 OMC

link address

OMC−R

Trigger HSI boards

replacement by OMC−R service

OMC−R


Alarmsolved


HSI boardsin service?

no

IP networkof MFS router

in service?

no

yes

Trigger network/ router

repair action

OMC−R

yes

X.25 network between

OMC and MFSin service?

no

OMC−R

no

Alarms onMFS

equipment?

no

Solve MFS alarm(s)

OMC−R

yes

Re−checkX.25link

yes

yes

Trigger repairaction from

network provider

no


no

Figure 5: External Communication Link Failure: Corrective Actions

20 / 26 3BK 20905 AAAA PCZZA Ed.01

3 O&M Alarms

3 O&M Alarms

This section describes the meaning and corrective actions for each alarmraised on the O&M with the supervised equipment (BTS, BSC, MFS).

3BK 20905 AAAA PCZZA Ed.01 21 / 26

3 O&M Alarms

3.1 Hardware Audit Failed

eventType ProcessingError

probableCause SoftwareProgramAbnormallyTerminate

Alarm Number 500010


Alarm Description Due to a failure during hardware audit, the hardware configurationis not correctly uploaded.

Impact on System The hardware audit of equipment fails. The configuration of the OMC-Rand the faulty equipment are not aligned.

22 / 26 3BK 20905 AAAA PCZZA Ed.01

3 O&M Alarms


Hardware Audit Failed

BTS:SBL OMLenabled/

unlocked?

Analyze/solveOML problem

OMC−R

Alarmsolved


no

Trigger newHardware

audit

yes

OMC−R

AuditOK?

Triggerrepairaction

OMC−R

RelatingBSC/BTSalarms?

Trigger newHardware

audit

OMC−R

AuditOK?

StartO−CPRtakeover

OMC−R

no

AuditOK?

Trigger newHardware

audit

OMC−R

yes

no

no

no

yes

yes

Alarmsolved

yes

Alarmsolved

Figure 6: Hardware Audit Failed: Corrective Actions

To isolate the fault: Check the transmission settings in BTS. Check thesector/TRE configuration versus equipped hardware (e.g. 2+2+2 TREsconfigured, but 4+4+4 TREs equipped in cabinet).

3BK 20905 AAAA PCZZA Ed.01 23 / 26

3 O&M Alarms

3.2 Alarm/State Audit Failed



Alarm Number 500011


Alarm Description Due to a failure during alarm/state audit, the equipment states andalarms are not correctly uploaded.

Impact on System The alarm and state audit of equipment fails. The OMC-R and thefaulty equipment are not aligned.

24 / 26 3BK 20905 AAAA PCZZA Ed.01

3 O&M Alarms


Alarm/State Audit Failed

BTS:SBL OMLenabled/

unlocked?

Analyze/solveOML problem

OMC−R

Alarmsolved


no

Trigger newalarm/state

audit

yes

OMC−R

AuditOK?

Triggerrepairaction

OMC−R

RelatingBSC/BTSalarms?


audit

OMC−R

AuditOK?

StartO−CPRtakeover

OMC−R

no

AuditOK?


audit

OMC−R

yes

yes

no

no

no

yes

yes Alarmsolved

Alarmsolved

Figure 7: Alarm/State Audit Failed: Corrective Actions

3BK 20905 AAAA PCZZA Ed.01 25 / 26

3 O&M Alarms

3.3 DLS Backup Failed



Alarm Number 500012


Alarm Description The running DLS backup can not be performed.

Impact on System The DLS backup fails. The running DLS is not stored in the OMC-Rdatabase.


DLS Backup Failed

Manual backup is ok?

OMC−R

Alarmsolved

yes

Perform a manual backup

OMC−R

Restart S−CPR

OMC−R

no

Perform a manual backup

Manual backup is ok?

Alarmsolved

yes


no

Figure 8: DLS Backup Failed: Corrective Actions

26 / 26 3BK 20905 AAAA PCZZA Ed.01

b9 a1353-ra omc-r alarm dictionary ed01.pdf

Documents

new alarm omcbsc link

internal link failure

link down172

alarm typethe alarm

alarm definitions

alarm description91

bsc unreachablesection

bsc unreachable section