asmanualed02

7/29/2019 ASManualEd02

1/130

Allrightsreserved.

Passingonandcopyingofthis

document,useandcommunicationofit

scontents

notpermittedwithoutwrittenauthorization

fromA

lcatel.

ED

1AA000140004(9007)A4

ALICE

04

.10

Y 1

02

957.130.722 TQZZA

RELEASED

/3AL 71109 AAAA TQZZA

4

4

QUESTA PAGINA NON VA INSERITA NEL MANUALETHIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

COD.MANUALEHDBK P/N: 957.130.722 A Ed.02 3AL 71109 AAAA Ed.021300NM

1330AS Rel. 5.1Version 5.1.1 OPERATORS HANDBOOK

ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)

No PAGINE TOTALI PER ARCHIVIAZIONE: 130

DIMENSIONE BINDER SORGENTE (du ks): 72.499 kBytes

INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS

STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING

COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

HANDBOOK COMPOSITION AND ASSEMBLY:

No pagine

(facciate)

numerate

numbered(facciate)

No pages da from ato

TARGHETTE - LABELS

957.130.722 A Ed.02

frontespizio

front2

957.130.722 A Ed.02

3AL 71109 AAAA Ed.02 manualemanual

124 1/124 124/124

TOTALE PAGINE A4 (FACCIATE)TOTAL A4 PAGES: 126

TOTALE FOGLI A4TOTAL A4 SHEETS: 63

WARNING FOR A-UNITS OTHER THAN A-ITALY

Labels are done according to A-Italy binder format.


2/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

Y 2

02

957.130.722 TQZZA

RELEASED


4

4

ALCATEL OPTICS GROUPSite

Originators

MARCOUSSIS

:

Domain

1330AS REL.5.1

Division

VERSION 5.1.1

Rubric

OPERATORS HANDBOOK

TypeDistribution Codes Internal External

::::

TNDNMALMAPALARM SURVEILLANCE1330AS REL.5.1 OPERATORS HANDBOOK

:

C.Mandroux

Approvals

NameApp.

App.Name

O.Frelot

INFORMAZIONI EDITORIALI

ORIGINALE SU FILE: ALICE 6.10

sistemazione figlist

957.130.722 A

3AL 71109 AAAA

Ed.02

1300NM

1330AS Rel. 5.1

Version 5.1.1

Alarm Surveillance

Version 5.1.1 on

OPERATORS HANDBOOK


3/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

Y 3

02

957.130.722 TQZZA

RELEASED


4

4

1300NM1330AS Rel. 5.1

Alarm Surveillance

Version 5.1.1 on

OPERATORS HANDBOOK

957.130.722 A Ed.02 3AL 71109 AAAA Ed.02

VOL.1/1

1300NM

1330AS Rel. 5.1Alarm Surveillance

Version 5.1.1 on

OPERATORS HANDBOOK

957.130.722 A Ed.02 3AL 71109 AAAA Ed.02

VOL.1/1

1300NM1330AS Rel. 5.1

Alarm Surveillance

957.130.722 A Ed.02 3AL 71109 AAAA Ed.02 OPERATORS HANDBOOK VOL.1/1

1300NM1330AS Rel. 5.1 Alarm Surveillance


1300NM1330AS Rel. 5.1

Alarm Surveillance

Version 5.1.1 on



4/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

Y 4

02

957.130.722 TQZZA

RELEASED


4

4

FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT


5/130957.130.722 A Ed.02 3AL 71109 AAAA Ed.02

Operators Handbook

Alcatel 1300NMNetwork Management

1330AS Rel.5.1Alarm Surveillance

Version 5.1.1 on


6/130957.130.722 A Ed.02 3AL 71109 AAAA Ed.02

APPLICABILITY

This handbook applies to all ALCATEL Network Management product-releases of which 1330AS Rel.5.1

is a SW component.


7/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

1

02

957.130.722 A

/3AL 71109 AAAA

124

124

1300AS REL.5.1 OPERATORS HANDBOOK

TABLE OF CONTENTS

LIST OF FIGURES AND TABLES 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HISTORY 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 INTRODUCTION 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 Scope. 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Target audience. 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 Document description. 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 ALARM SURVEILLANCE PRINCIPLES 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 Alarm Surveillance Context 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.1 Telecommunication Network operation 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.2 Alarm information 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2 Alarm Surveillance Functionalities 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2.1 An iterative approach for alarm description 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2.2 Current Alarms Management 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2.3 Historical Alarms Management 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2.4 Advanced Features 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 HMI Overview 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1 General conventions and kinds of widgets. 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.2 Main windows. 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.3 Dialogue boxes. 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.4 Errors, confirmations and messages. 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.3.5 Online Help. 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 MANAGING CURRENT ALARMS 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 Current alarms management startup 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 Creating a sublist 29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Modifying a sublist 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.1 Modifying the sublist display parameters 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.2 Modifying the sublist filter 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.3 Modifying the sorting rules of a sublist 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.4 Setting tone emission and scripts triggering 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4 Visualizing (opening) a sublist 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.5 Deleting a sublist 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.6 Selecting alarms within a sublist window 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

01 991209 O. Frelot F. Clenet

02 001219 SC 00121901 O. Frelot C. Mandroux

1300AS REL.5.1

VERSION 5.1.1 ONOPERATORS HANDBOOK


8/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

2

02

957.130.722 A

/3AL 71109 AAAA

124

124

3.6.1 Selecting a single or a group of alarms 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.6.2 Selecting all alarms 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.6.3 Deselecting all alarms 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.7 Exporting contents of a sublist 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.8 Visualizing full alarm information 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.9 Performing actions on selected alarms 60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.9.1 Acknowledging alarms 60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.9.2 Reserving or unreserving alarms 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.9.3 Creating trouble tickets 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.9.4 Manual purging 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.9.5 Getting correlated alarms information 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.10 Getting reports on performed actions 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.10.1 Visualizing the actions report 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.10.2 Clearing the whole report list 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.10.3 Deleting reports for some selected actions 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.10.4 Configuring the Report window 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.11 NE Symbols management 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.11.1 Alarm information 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.11.2 Most severe/Most recent Non cleared alarms management 73. . . . . . . . . . . . . . . . . . . . . .

4 ADMINISTERING ALARM SURVEILLANCE 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Overview 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2 Administering the C.A.L. 78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.1 C.A.L Size Control Settings 78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.2 Setting the Overflow parameters 79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.3 Setting the Purging Sort Criteria 80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.4 The Statistics Zone 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3 Customizing the Archiving Filter 82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4 Purging alarms automatically 84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.5 Autocreating trouble tickets 85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.6 Autoacknowledging alarms 85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.7 Resynchronizing AS 86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 MANAGING HISTORICAL ALARMS 89. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1 Introduction and capabilities 89. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2 Historical alarms management start up 91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.3 Retrieving archived alarms 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.4 Filtering archived alarms 97. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.4.1 Accessing the Filter panel 97. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.4.2 Using the different groups of the panel 98. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.5 Managing User Files 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.5.1 Saving a set of alarms to an user file 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.5.2 Retrieving alarms from a set of user files 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.5.3 Deleting a set of user files 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 NAVIGATION FEATURES 113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1 Navigating within the AS application 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1.1 Navigating through the sublists 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1.2 Navigating between the C.A.L. and the H.A.L. 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1.3 Navigating to the Counter Summary 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2 Navigating toward external applications 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2.1 Navigating to the PNM application 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2.2 Navigating to the ELM application 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2.3 Sending alarm information to an external application 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . .


9/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

3

02

957.130.722 A

/3AL 71109 AAAA

124

124

7 ABBREVIATIONS 119. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8 GLOSSARY OF TERMS 121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INDEX 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


10/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

4

02

957.130.722 A

/3AL 71109 AAAA

124

124

LIST OF FIGURES AND TABLES

Figure 1. Telecommunication network and alarm emission 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2. Current and Historical Functions of the Alarm Surveillance 11. . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3. An iterative approach for alarm description 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4. Advanced features mechanisms and alarm flow 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5. Main window Organization 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6. Mouse Action on Counter Summary working area 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Figure 7. Mouse Actions on Current Alarm Sublist 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 8. Additional window Organization 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 9. Dialog window Organization 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 10. Current Alarms Counter Summary window. 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 11. Creating a sublist 29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12. Just created sublist. 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13. Modifying a sublist 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 14. Sublist modificationDisplay panel 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 15. Sublist modificationColour definition 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 16. Colour selectionThe different methods. 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 17. Sublist modificationDisplayed attributes: adding MO Instance . 35. . . . . . . . . . . . . . . . .Figure 18. Sublist PropertiesFilter Panel (Current Alarms case) 36. . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 19. Sublist filterEvent Date & Time group. 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 20. Sublist filterEdition of the list of time intervals. 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 21. Sublist filterStatus group. 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 22. Sublist filterSeverity level and AlarmType groups. 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 23. Sublist filterProbable cause group. 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 24. Sublist filterSelection of probable causes. 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 25. Sublist filterCorrelation group 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 26. Instance Filter groupMO instance 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 27. Instance filter groupFriendly Name 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 28. MO Class filter group 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 29. More Info window: Retrieval of MO Class, Instance and Friendly Name. 44. . . . . . . . . . .

Figure 30. Extended Filter page 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 31. Sublist PropertiesSort Panel (Current Alarms case). 47. . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 32. Addition of a dictionnary entryError message. 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 33. trigger page of the Sublist Properties My_Sublist 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 34. 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 35. Opening a sublist 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 36. Sublist contents window (Current Alarms case) 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 37. Deleting a sublist 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 38. Deletion of a sublistConfirmation 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 39. Selecting all alarms within the Alarm Sublist window 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 40. Exporting selected alarms of a sublist. 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Figure 41. Output windowDefault aspect 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 42. Output windowExporting alarms to a file 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 43. File Chooser window. 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 44. Getting full information about an alarm. 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 45. More Alarm Information windowIdentity panel 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 46. More Alarm Information windowCorrelation panel. 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 47. Acknowledging a group of alarms 60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 48. Reserving selected alarms 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 49. Unreserving some alarms 62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 50. Sending trouble tickets concerning selected alarms 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 51. Manually purging selected alarms 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 52. Correlated Notification Flag Attribute. 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


11/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

5

02

957.130.722 A

/3AL 71109 AAAA

124

124

Figure 53. Visualizing report information 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 54. Report windowAn abort case 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 55. Clearing the whole report window 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 56. Deleting the report of a selected action 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 57. Display options for Report window 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 58. Submap window example. 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 59. Alert Symbol view. 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 60. Administration window for alarm surveillance configuration 75. . . . . . . . . . . . . . . . . . . . . . . .Figure 61. Failure report 76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 62. C.A.L. AdministrationOverflow Parameter zone 79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 63. C.A.L. AdministrationPurging Criteria zone 80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 64. C.A.L. AdministrationStatistics zone 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 65. AdministrationArchiving filter Panel 82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 66. Resynchronizing the AS 86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 67. Confirmation box. 86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 68. Message box. 87. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 69. The different alarm archives 90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 70. AS historical part start up : Counter Summary window 91. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 71. historical Sublist pull down menu 92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Figure 72. Selecting a source of archived alarms 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 73. Retrieval operationAppending or overwriting 94. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 74. Retrieval operationConfirming the reinitialization of sublists. 94. . . . . . . . . . . . . . . . . . . . .

Figure 75. Retrieval operationProgress window 95. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 76. Interrupting the historical alarm retrieval 95. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 77. Error message box. 95. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 78. Sublist PropertiesFilter Panel (Historical Alarms case) 97. . . . . . . . . . . . . . . . . . . . . . . . .

Figure 79. Sublist filterEvent Date & Time group. 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 80. Sublist filterEdition of the list of time intervals. 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 81. Sublist filterSeverity level and Alarm Type groups. 100. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 82. Sublist filterProbable cause group. 101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 83. Sublist filterSelection of probable causes. 101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 84. Sublist filterInsertion Cause group 102. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 85. Sublist filterSource filter page 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 86. More Info window: Retrieval of MO Class, Instance and Friendly Name. 104. . . . . . . . . . .

Figure 87. Extended filter page 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 88. Saving historical alarms to an user file 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 89. Historical user fileSpecification of the file name 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 90. Historical user fileStorage progress window 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 91. Historical user filesSelection of files 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 92. Deleting archive user files. 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 93. Navigation pull down menu 113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 94. Navigating to a opened sublist named NE_Nantes 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Figure 95. Accessing the Historical Counter Summary from the Current Counter Summary

window 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 96. Accessing PNM submap from a Current Alarms sublist 116. . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 97. Calling the ELM application for HPLog configuration 117. . . . . . . . . . . . . . . . . . . . . . . . . . . .


12/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

6

02

957.130.722 A

/3AL 71109 AAAA

124

124

HISTORYAS INTERNAL DOCUMENT 3BP 21600 0010 TCZZA

Edition Authors Date Page /

Paragraph

Observations

2.0 F. Clenet 990113 All Modifications and updating.

3.0 C. Mandroux 000517 All Modifications and updating.

AS HANDBOOK P/N 3AL 71109 AAAA (factory P/N 957.130.722 A)

Ed.01 created on December 9, 1999 corresponding to ED.2.0 of internal document

Ed.02 created on December 19, 2000 corresponding to ED.3.0 of internal document

Edition Date Corresponding to internal document edition

01 991209 ED.2.0

02 001219 ED.3.0

Applicable documents (for Alcatel internal use only)

[1] DOCUMENT MANAGEMENT PROCEDURE

Ed03, NMU/C/RT/95/034

[2] AAR, ALMAPPlatform and Generic Components PLCProduct Life Cycle

Ed02, NMU/C/96/0045

[3] NMU, ALMAP PLC Amendment

Ed01, 3BP 216130007 ASZZA

Reference Documents (for Alcatel internal use only)

[4] NMU, ALMAPFeature Description

Ed02, NMU/C/96/0056

[5] NMU, ALMAPAS Feature Description

Ed04, NMU/C/96/0036

[6] AAR, ALMAPAS5.0 Technical Specification

Ed02, 3BP 21600 0001 DSZZA

[7] AAR, ALMAPAS5.0 User Interface Overview

Ed01, 3BP 21600 0002 DSZZA

[8] X.733 Alarm Reporting Function

ITUT (CCITT)Feb. 1992

[9] X.734 Event Report Management Function

ITUT (CCITT)1993

[10] NMU, ALMAPPNM320 Users Guide

Ed01, 3BP21619 0004 TCZZA


13/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

7

02

957.130.722 A

/3AL 71109 AAAA

124

124

1 INTRODUCTION

1.1 Scope.

This document contains the Operators Manual of the ALMAP AS Generic Component. It applies to AS

5.1.0 application. A prerequisite to the reading of this document is to be aware of TMN Standards.

1.2 Target audience.

This document is intended for all the Operators using the Alarm Surveillance subsystem in their applica-

tion.

1.3 Document description.

This document is composed of the following chapters:

Chapter 2: Alarm Surveillance Principles, is a presentation of the AS application, from its functional-

ities and GUI point of view, together with the context it takes place into:

Alarm Surveillance Context.

Alarm Surveillance Functionalities.

HMI Overview.

Chapter 3: Managing current alarms, describes all the aspects concerning the management of cur-

rent alarms. Most of the first sections are devoted to general operations on sublists and on alarms

within these sublists. The interface described there is shared with the historical alarms management

subset. On the opposite, the final sections of the chapter deal with specific aspects of current alarms

management.

Current alarms management startup.

Creating a new sublist.

Modifying a sublist.

Visualizing (opening) a sublist.

Deleting a sublist.

Selecting alarms within a sublist window.

Exporting contents from a sublist.

Vizualizing full alarm information.

Performing actions on selected alarms (specific to current alarms management):

acknowledging alarms,

reserving or unreserving alarms,

creating a trouble ticket, manually purging alarms,

visualizing correlated alarms.

Getting reports on performed actions.

NE Management.

Chapter 4: Administering Alarm surveillance, explains how to administer the Alarm Surveillance of

AS :

Administering the C.A.L..

Customizing the Archiving Filter.

Purging alarms automatically.

Autocreating trouble tickets.


14/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

8

02

957.130.722 A

/3AL 71109 AAAA

124

124

Autoacknowledging.

Resynchronizing the AS.

Chapter 5: Managing historical alarms, explains how to work with the AS historical branch. This chapter

focuses on specific aspects of historical management. References are provided to Chapter 3 concerning

general operations managed in the same way as for current alarms.

Introduction and capabilities. Historical alarms management startup.

Retrieving archived alarms.

Filtering archived alarms.

Managing User Files.

Chapter 6: Navigation Features, describes navigation options, within the AS application and toward

external applications, such as PNM and ELM :

Navigating within the AS application.

Navigating toward external applications.

Chapter 7: Acronyms, gives the definition of the acronyms used in this document.

Chapter 8: Glossary, gives definitions of terms used in this document.


15/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

9

02

957.130.722 A

/3AL 71109 AAAA

124

124

2 ALARM SURVEILLANCE PRINCIPLES

The Alarm Surveillance (AS) is a generic component of the ALMAP product. It provides efficient mecha-

nisms to control, supervise and manage equipment anomalies that may occur in a Telecommunication

Network.

2.1 Alarm Surveillance Context

2.1.1 Telecommunication Network operation

Telecommunication Networks are usually composed of thousands of heterogeneous resources (access,

transmission, switch, ...) which are linked to each other in order to communicate and achieve highlevel

services to the network users like dispatching a TV program or an usual phone call.

Because some elements in the network may happen to break down, several mechanisms have been pro-

vided to the operators in charge of supervising the network, whenever such a failure occurs. One of these

mechanisms allows the resources which are trying to use another disabled one to send a warning mes-

sage into the network. In such a case, the warning message is called an alarm, and the mechanism iscalled alarm raising. These alarms messages are collected and displayed on a supervision console.

Therefore, the network operators are able to engage whatever action is necessary to solve the raised prob-

lem. Once the disabled resource is repaired, other resources may use it again. If the operation is success-

fully achieved, all the resources send another message to warn that the failure has been repaired. The

message is still called an alarm, but the mechanism here is called the alarm clearing.

The alarms that are sent into a Telecommunication Network are potentially all the more numerous since

the number of elements that compose the network is large. The operators supervising the network need

efficient tools to detect, locate and take into account dysfunctions in the network, and finally resume opera-

tion. The Alarm Surveillance product is dedicated to this purpose.

NETWORK

Network Operator

Network Operator

availableresource

faulty re-source

resourceemittingalarms

Figure 1. Telecommunication network and alarm emission


16/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

10

02

957.130.722 A

/3AL 71109 AAAA

124

124

2.1.2 Alarm information

Alarms or Alarm notificationsconsist in messages emitted by network resources that have detected prob-

lems or failures in the network. Information contained in the alarm belongs to two classes:

a ) information that identifies the resource (Object Instance) which has raised the alarm. Basically these

pieces of information are:

the resource type (Object Class),

the resource name which has to be unique (Full Distinguished Name) in order to avoid identifi-

cation ambiguities. However, because the manipulation of such unique ids is often heavy, the

resource usually happens to be also designed by a userfriendly name which is locally unique

(Friendly Name).

b ) information that identifies the type of the problem the alarm refers to. The kind of problem regroups

three basic elements of information :

the problem type (Event Type) taken out of the five following ones :

Quality of Service, Communications,

Processing Error,

Equipment,

Environmental.

the probable cause of the problem, which is taken out of either standard probable cause values

(cf. ITUT Recommendation X.733), or locally defined values.

the severity level of the problem (Perceived Severity) when the alarm is raised. Malfunctions

are ranked into five severity levels:

Critical, when it is no longer possible to provide the service requested by the user, Major,

Minor,

Warning, which means no impact is reported upon the quality of service offered to the user,

Indeterminate, if the severity level cannot be defined by the resource which raises the

alarm.

Note that a particular severity level (Cleared) is used when the alarm is cleared by the resource

which has raised it before.

Note that these pieces of information are mandatory in any alarm notification, as well as the date and time

the alarm has been raised by the resource. Other optional information such as the specific problems the

alarm is linked to, the notification identifier, ... may also be present to help the operator in the alarm man-agement process.


17/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

11

02

957.130.722 A

/3AL 71109 AAAA

124

124

2.2 Alarm Surveillance Functionalities

The Alarm Surveillance application is dedicated to receive, store, display and manage in real time alarms

raised by different sources, here called current alarms, facilitating the overall alarm surveillance of the mul-

tivendor and multitechnology network, and improving the reaction time of the network operators in case

of anomalies in the network. It also provides the possibility to archive and retrieve the alarms, then called

historical alarms, allowing postanalysis of anomalies in the network.

Figure 2. illustrates the use of the different branches of the Alarm Surveillance application.

Export Files

display

CURRENTALARMS

ARCHIVEDALARMS

AS Operator

Export Files

archivealarms

raise & clearalarms

alarmsdisplayalarms

Alarm Surveillance

PrinterPrinter

print/exportalarms

print/exportalarms

AS Operator

managealarms

Static AnalysisRealTime Management

NETWORK RE-SOURCES

Figure 2. Current and Historical Functions of the Alarm Surveillance

Current and historical alarms are managed through an userfriendly and powerful query interface. The

way alarms are handled is similar in both current and historical parts of the Alarm Surveillance, so that the

operator can go through realtime treatment or long term analysis of the network problems without having

to learn a new interface.

These alarms can be displayed in lists while alarm counters keep track of statistics. By mouse clicking,

the operator can get detailed alarm information, or perform action on the alarm when the alarm is raised.

In both cases, the operator is offered the possibility to export the displayed alarms to either a printer or

an ASCII file that may be used by another application for dedicated analysis.


18/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

12

02

957.130.722 A

/3AL 71109 AAAA

124

124

In the current alarm case, a synthesis of alarm information can be displayed in submap. This option de-

pends on a configuration file (see section 3.11). This alarm information is displayed for each NE present

within the submap.

2.2.1 An iterative approach for alarm description

Taken in account the number of alarms that are usually emitted in a network, the Alarm Surveillance offers

the operator a stepbystep approach for alarm visualization.

a ) The Counter Summarywindow: This is a main window used to display statistics on alarms. It shows

alarm counters, according to severity levels or statuses of the alarms (critical, major, minor, warning,

indeterminate, cleared, acknowledged, incoming). In the counter summary, alarms may be grouped

according to filtering criteria in several sublists. For each sublist, each of the counters may be shown

or not.

b ) The Alarm Sublistwindow: The sublist is a basic working window. It regroups alarms according to

filtering criteria defined by the operator, and allows to work on a limited subset of alarms. The sublist

can also be sorted according to criteria defined by the operator. It makes easier the management of

current alarms, and allows information classification before a possible export to a file or a printer.

c ) The More Informationwindow: This window gives the operator the complete information contained

in an alarm, which is particularly helpful for locating and diagnosing the problem the alarm is linked

to.

Figure 3. illustrates the principle of this iterative approach.

AlarmsCounter Summary

Alarm SublistM o r e I n f or m a ti o n

increasing precision

1 sublist ,

n a la rm s

1 summary,

n s ub l is t s

1 alarm

filter

sort

global vision local vision detailed visionactual network

Figure 3. An iterative approach for alarm description

Next section 2.2.2 details the actions and operations that can be performed on current alarms, while sec-

tion 2.2.3 Historical Alarms Managementdeals with manipulation of historical alarms. Section 2.2.4 Ad-

vanced Featuresgives additional features provided to the operator for a more efficient alarm surveillance.


19/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

13

02

957.130.722 A

/3AL 71109 AAAA

124

124

2.2.2 Current Alarms Management

A part of the Alarm Surveillance product is dedicated to the realtime treatment of current alarms, i.e. the

alarms which have just been raised by a resource. This section will describe how the operator who follows

the network activity may interfere with the network in order to take anomalies into account and solve them.

a ) when an alarm is raised by a faulty resource (or by a neighboring one), it is received by the Alarm

Surveillance which stores it and warns the operator by a tone emission or by the appearance of aspecific icon on the screen. The alarm may be displayed as soon at it is signalled according to the

operator needs.

b ) the alarm is displayed on the screen by the operator: basic information (described in section 2.1.2

Alarm information) is immediately available to the operator who can decide:

to get detailed information contained in the alarm,

to reserve the alarm for further exclusive investigation. This action of reservation on the alarm

prevents other operators to perform any action on the alarm. It is reversible: an operator can

unreserve a formerlyreserved alarm without damaging it,

to request the creation of a trouble ticket to be handled by the external product ARS,

to acknowledge the alarm, indicating that the problem the alarm is linked to has been taken into

account, and that repair actions have been launched,

to let other operators take it into account.

During the whole period an alarm is considered to be current (alive), its state is permanently real

time refreshed so that any operator who displays the alarm is able to know if it has been reserved

or not, if it has been acknowledged or not, if a trouble ticket has been requested for this alarm or not,

... Other elements of information such as the date and time these actions have been performed, or

the name of the operator that performed each of them are also available on operators request. Fur-

thermore, the operator can attach a free text note to any of the current alarms.

c ) the alarm is cleared by the emitting resource as soon as the problem is no longer present at the re-

source level. Then the alarm will no longer be considered as a current alarm as soon as it will be

acknowledged by the operator, and thus it will disappear from the current alarm set and will be ar-

chived into the set of historical alarms.

The problem the alarm is linked to may not be solved immediately. In such a case the alarm is re-

peated after a while until the problem is solved. Alarm Surveillance associates a repetition counter

to each received alarm. Furthermore, if the alarm is not cleared, for any reason, by the resource which

raised it before, then the Alarm Surveillance offers the possibility to archive it manually on the opera-

tors request.

Note that a single anomaly in the network may cause the raising of several alarms ; it may also generate

other anomalies or dysfunctionments that raise additional alarms. These alarms, called correlated alarms,

may be marked as linked each other. So, the operator can know if an alarm has correlated alarms or not.


20/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

14

02

957.130.722 A

/3AL 71109 AAAA

124

124

2.2.3 Historical Alarms Management

Once alarms are no longer considered as current ones by the Alarm Surveillance application, they are

archived in a repository for further consultation. It is up to the historical part of the Alarm Surveillance to

allow these further consultations.

A consultation of historical alarms is generally performed in 4 steps:

a ) extracting the required alarm list from the repository or from personal files (see below). Because all

alarms present in the repository may not be relevant for the operator analysis, the operator is re-

quested to specify filtering criteria in order to extract only the useful part of the alarms. These alarms

are stored in a main alarm list. The main alarm list is the base on which the operator will work later

on.

b ) creating sublists from the main alarm list. This operation automatically generates counters based on

the severity level, or on the clearing or acknowledgement statuses of the alarms contained in the sub-

list.

c ) opening the alarm sublists. The operator can then get basic information on the alarms of the sublist,

including the date and time the alarms have been archived and the reason of their archiving.

d ) getting detailed information on a particular alarm.

The operator can store a collection of selected alarms into an user file. The operator will then be allowed

to access later again these alarms from this file to pursue the analysis.

The historical part of the Alarm Surveillance is particularly useful to follow the activity of a network, its ro-

bustness, the recurrence of problems, or to help the operator to dimension the network, detect its critical

points, ...


21/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

15

02

957.130.722 A

/3AL 71109 AAAA

124

124

2.2.4 Advanced Features

Because the Current Alarms List (C.A.L.) has a limited size, the operator is provided with several ad-

vanced features in order to solve capacity overflow problems:

a ) the operator can adjust the C.A.L. size, and indicates the filling percentage starting from which a

warning is emitted (see section 4.1 Administering the C.A.L). The maximum size value being itself

limited to a maximum value of 10000 current alarms. The operator can also specify the behaviourof the C.A.L. when the overflow occurs (wrap/halt). In wrap mode, a mechanism of purge will be auto-

matically involved. The operator specifies the size of the purge (number of alarms) and the criteria

to select the alarms to be eliminated (these alarms are archived in the historical list).

b ) an automatic purge mechanism: according to filtering criteria, some incoming alarms may be immedi-

ately archived, without going through the current state, that is without being displayed in the current

alarms part of the Alarm Surveillance (see section 4.4 Purging alarms automatically).

Other features are provided:

c ) an automatic acknowledgement mechanism: according to filtering criteria, the operator may decide

to automatically acknowledge some alarms when they enter the C.A.L. (see section 4.6 Autoac-knowledging alarms).

d ) an automatic trouble ticket creation mechanism: according to filtering criteria, the operator is pro-

vided the way to automatically request the creation of trouble tickets to an external ARS application

when the alarms appear in the C.A.L..

e ) a selective archiving mechanism: according to filtering criteria, the operator can prevent some alarms

from being archived in the historical list. By default, all the alarms are foreseen to be archived. If this

filter is changed, alarms which are not archived are lost.

f ) a synchronization mechanism: because the C.A.L., for any reason, may happen to become inconsis-

tent with the alarms situation of the network, the operator can provoke a synchronization mechanism

which performs a global refreshment of the C.A.L. checking all the resources involved.

g ) an automatic tone emission mechanism: according to the severity level of the incoming alarm, a tone

may be automatically emitted. This configuration can be customized by each operator.

h ) a navigation mechanism: the operator is provided with an interface to another external application

after selecting an alarm to allow specific treatment on its data (see section 6. Navigation features).

Figure 4. illustrates the advanced features mechanisms.


22/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

16

02

957.130.722 A

/3AL 71109 AAAA

124

124

NETWORKRESOURCES

AS Operator

CURRENT ALARMS ARCHIVED ALARMS

autoacknowledgement filter

autotroubleticket creation

autopurge filter

ARS

autobeepingarchivingfilter

overflow purge

AS Operator

alarm retrieving

sublistordering andfi ltering

Alarm flow

Alarm ordering

Alarm filtering

Static AnalysisRealTime Management

EXTERNALAPPLICATION

navigation

navigation

sublistordering andfiltering

navigation

Figure 4. Advanced features mechanisms and alarm flow


23/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

17

02

957.130.722 A

/3AL 71109 AAAA

124

124

2.3 HMI Overview

This section gives some general rules concerning the whole AS User interface. It includes a general de-

scription of the different kinds of windows that can be encountered through the application.

Current and Historical part of the Alarm Surveillance follow the same design rules. This allows the operator

to use indifferently both parts without any additional formation. These design rules aim to get:

a ) a simpleinterface: all operation may be realized with a left button mouse click. Some operations are

accelerated by mouse doubleclick and drag and drop. Operations may be disabled according to

selections, ... their corresponding items then are greyed.

b ) an interactiveinterface: dialogs are popped up before performing any unreversible operations. Mes-

sages are systematically displayed on the screen to inform the operator of the state of the Alarm Sur-

veillance. A contextual help offers from any window a support to the operator.

c ) a personalinterface: the operator can easily customize colors, fonts and general layout of the inter-

face. This customization is saved while exiting the interface. It is automatically retrieved while starting

it again.


24/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

18

02

957.130.722 A

/3AL 71109 AAAA

124

124

2.3.1 General conventions and kinds of widgets.

Menus and buttons in AS follow usual common rules:

The menu bar, when it exists, is located at the top of the window, just below the title.

A right arrow, when appearing at the right of a menu item, indicates the presence of a popup

submenu.

The ... mention, at the right of a menu item or of a button label (for example Create...), means thatadditional information is needed to perform the operation. This information will be provided through

a dialogue box.

When a character appears underlined inside a menu item or a button label, the combination of the

Altkey and of the character key provides a shortcut for executing the same command.

A grayed item means that the corresponding command is not available, either because of a restriction

of access rights, or because the operation needs an operand, which has not yet been selected.

Concerning the mouse usage in AS , the following rules apply:

All actions are performed with the left button.

Quite generally, these actions are limited to simple click. They sometimes include doubleclick. Drag

and drop operations are not used, except for moving columns in tables. Combination of key pressing and mouse action is used in lists with multiple selection. Shift+ click

allows to select a range of items, Ctrl+ click allows to add an item to an existing selection (or to re-

move it). In this same context, selecting a range of items can also be obtained by holding down the

mouse button after pointing the first item, moving toward the last one and releasing the button on this

element.

The different kinds of widgets which may be encountered in this application are (with the denominationsused through out this manual):

The push button, or more simply the button, used to cause the execution of an action.

The check button, or checkbox, sometimes used in a group, individually describing a boolean state.

The radio buttons, always used in a group, to figure exclusive choices.

The option button, or popup list, describing also a choice among a list of generally predefined items.

The list box, or more simply the list, used to display sets of generally nonpredefined items and to

select the item (simple selection list ) or the items (multiple selection list) on which an action will be

performed.

The Twin boxes, used to select and move one or several attributes from a source list to a destination

list :


25/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

19

02

957.130.722 A

/3AL 71109 AAAA

124

124

You can move one or several attributes from a source list (e.g. Hidden Attributes list) to the destination

list (e.g. Displayed Attributes) by selecting the desired items and then using the arrow buttons (left

and right).

In each list, multiple selection is available. To add a new attribute to the selection, press the Ctrl key

simultaneously to the mouse click. To unselect an already selected attribute, use again in the same

way this Ctrlkey. To add a whole block of attributes, including all items between the end of the current

selection and the designated item, press the Shift key together with the mouse button, or hold the

button across the desired block.

To control the position of insertion in the destination list, after the selection of the desired item in the

source list, operate at follows :

to add at the end of the list, check there is no current selection in this destination list (Displayed

Attributes). If there is one, click again on the selected item, while pressing simultaneously the

Ctrl key. Click afterwards on the right arrow button.

to insert at the beginning or before an existing item of the destination list (e.g. Displayed Attrib-

utes), i.e. to take the ordinal position of an existing item, select first this item in the destination

list and then click the right arrow. If, when pressing the arrow, there is a multiple selection in the

destination list, only the first item is used as position reference.

The entry box, used to enter textual or alphanumeric data. Also called text box, especially when it

can accept multiline display or input.

The entry box may be in some cases (when it contains numeric or date/time values) be accompanied

on its right by spin buttons, two small down and up arrows which allow to decrease or increase the

value or a subfield of this value in the box.

The combo box, which combines an option button and an entry box, used here to manage dictio-

naries entries.


26/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

20

02

957.130.722 A

/3AL 71109 AAAA

124

124

2.3.2 Main windows.

Main windows are primary windows. The operator does not need to close them before performing any oth-

er action. A possible presentation of main windows is shown in Figure 5.

MENU BAR

WORKING AREA

INFORMATION BOX

WINDOW TITLE

Figure 5. Main window Organization

The Counter Summaryand the Alarm Sublistwindows belong to this window category, and their functional-

ities are described in detail later on.

Menus can only be encountered within these workspaces.

Such a window is made of:

a menu bar, which allows the operator to perform commands.

a working area, which contains a table of elements (sublists or alarms).

You can select with the mouse or the keyboard arrows one or several elements in this table.

When needed, because of a limited size or of a large number of elements, a scroll bar on the right

allows to walk through the complete list. Similarly, a scroll bar may appear at the bottom of the table

to make possible the visualization of the complete set of columns.

The order of the attributes columns can be modified. To move such a column, click the corresponding

cell on the header line and hold down. The contents of the column are displayed with inverse video.

Move the cursor toward the desired position without leaving the header bar. The column follows the

movement and other columns are moved. When on the right position, release the button.

The width of the columns can also be modified to adapt to their contents or to allow a better visualiza-

tion. To do so, move the mouse cursor to the header line, at the right border of the column you want

to widen or to narrow. The aspect of the cursor changes to a horizontal double arrow. Click, hold

down. A thin vertical line appears. Move right or left until you reach the desired width and release.

The table display is then updated.

an information box, which gives you general realtime refreshed information or error messages, and,

in the bottomright corner, the number of elements of the table. You cannot perform any action on

the Information Box.


27/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

21

02

957.130.722 A

/3AL 71109 AAAA

124

124

The Figure 6. and Figure 7. respectively synthetisizes the graphical capabilities of the Counter Summary

and Alarm Sublistworking areas :

Location \ Action Click Double Click Drag & Drop

Column Title

hide column move column (1)(2)

Sublist Line

Unselected select sublistopen the SINGLE

Single selection unselect sublist

open the SINGLE

pointed sublistmove sublist line (3)

Multiple selection (0)

(0) MultipleselectionisnotallowedintheCounterSummary.

(1) Drag&Dropontheleftorrightedgeofcolumntitleresizesthewidthoftherow.

(2)

Drag&Dropon

the

bottom

edge

of

acolumn

title

resizes

the

height

of

the

row.

(3) Drag&Droponthebottomorhighedgeofthe1.stcolumnofanyrowsresizestheheightofallrows.

Figure 6. Mouse Action on Counter Summary working area

Location \ Action Click Double Click Drag & Drop

Column Titles

hide column move column (1)

Alarms

Unselected

Single selection select alarmshow more info on

(2)

Multiple selection

THE pointed alarm

(1) Drag&Droponthebottomedgeofacolumntitleresizestheheightoftherow.

(2) Drag&Droponthebottomorhighedgeofthe1.stcolumnofanyrowsresizestheheightofallrows.

Figure 7. Mouse Actions on Current Alarm Sublist


28/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

22

02

957.130.722 A

/3AL 71109 AAAA

124

124

2.3.3 Dialogue boxes.

Selecting a command from a menu generally causes the opening of a dialogue box.

These additional windows are also primary windows. The operator does not need to close them before

performing any other action. They are used for displaying general information on alarms and sublist prop-

erties. Their content is refreshed according to operators selection. A possible presentation of additional

windows is shown in Figure 8.

WORKING AREA(S)

Apply

WINDOW TITLE

FOLDER

Reset Close Help

BUTTON AREA

Figure 8. Additional window Organization

Property, Administrationand More Infowindows belong to this category of windows. Their functionalities

are described in detail later on.

Such a window is frequently composed of several panels. Each of them can be accessed by clicking onthe corresponding tab at the top of the window.

The central zone is occupied by the widgets belonging to the current panel. These widgets vary with the

panel and some of them may be grayed in specific contexts.

The button area, at the bottom of the dialogue box, is shared between the different panels.

Apply: The modifications, operated in all the panels, are saved. The window is not closed and the

Close: The window is closed without any storing. Any modifications, operated in any panel, and not

saved through the previous usage of Applyare lost.

Reset: The window is not closed, but the modifications operated in the current panel are lost. The

initial state of this panel is restored. Other panels are left unchanged.

Helpcauses the display an Online Help window.

In some other dialogue boxes, especially those with only one panel, Closemay be replaced by Cancel,with a similar operation. However, in thoses cases, Applycauses the window to close after saving the userinput.


29/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

23

02

957.130.722 A

/3AL 71109 AAAA

124

124

2.3.4 Errors, confirmations and messages.

To display some messages, especially errors, or to ask for confirmation before performing some actionssuch as deletions, the system uses small modal windows. You must take the dialogue into account andclose the window before any other action on the application.

A possible presentation of such a window is shown in Figure 9.

DIALOG AREA

WINDOW TITLE

Ok Cancel Help

BUTTON AREA

Figure 9. Dialog window Organization

The central area is readonly. You cannot perform any action on it.

For a simple information or error message, the button bar will only include a Okbutton to acknowledgethe message.

For a confirmation, the buttons will include Okand Cancel, and sometimes Help.

Output, Tone Configurationand basic dialog windows belong to this category of windows. Their functional-

ities are described in detail later on.

2.3.5 Online Help.

An online help is provided by the application. You can access this help:

by opening the Helppopup menu from the menu bar in any workspace window, and then selectingone of the following options:

On Version: the current AS version and related information are displayed.

On Help: a window opens, which describes the help facilities and the methods of navigation

within the help contents.

On Window: a window opens, providing an explanation about the current window.

On Index: a window opens, which presents an introduction page, and then proposes links to-

ward the various parts of the help.

Glossary: a window opens, which presents a list of important terms together with the related

definitions.

by pushing the Helpbutton available in most dialogue boxes. This method gives access to same con-

tents that the On Windowmenu option presented above. In that case, the help window is opened

on a page which directly relates to the current dialog box function and way of operation.


30/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

24

02

957.130.722 A

/3AL 71109 AAAA

124

124


31/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

25

02

957.130.722 A

/3AL 71109 AAAA

124

124

3 MANAGING CURRENT ALARMS

When working with current alarms the user interface is primarily organized around :

the Counter Summarywindow, which provides the global level of information,

one or several sublist windows, each of them providing a second level of information on a parame-

trized subset of alarms, together with a set of possible commands on these alarms.

a Submapwindow, which allows to display a synthesis of alarm information for each NE (see section3.11). The existence of this submap is optional and depends on a configuration file.

a Most Severe Alarmssublist, which is automatically created if a submap is displayed (see section

3.12).

The application is installed with a configuration including some default sublists. The operator is expected

to create new alarm sublists according to his/her surveillance or analysis needs (see section 3.2). The cre-

ation of a new sublist is characterized by the definition of its filter and by the setup of its sorting and display

characteristics.

The application allows to receive alarms raising from one or several alarm agents.

The filter conditions the content of the sublist. For example, a filter may be used to monitor alarms of agiven resource or to restrict the number of alarms to be looked at when analyzing a problem. It is a logical

expression that describes conditions on the presence of alarm attributes or on their values. An alarm

passes the filter if all conditions expressed by the filter are fulfilled by the attributes of the alarm. In that

case, the alarm is added to the sublist. Since an alarm may pass different filters, an alarm may belong to

several sublists.

The display and sort criteria do not involve the content of the sublist but its visualization. For each sublist,

the attributes of the alarms to be displayed may be configured. In addition, alarms may be listed according

to a userdefined order. A sublist is also given a name and is assigned an userdefined color.

When working with historical (archived) alarms, the user interface is organized as with current alarm, ex-

cept for the submap window which is here not present.


32/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

26

02

957.130.722 A

/3AL 71109 AAAA

124

124

3.1 Current alarms management startup

The Counter Summarywindow is a startup windows for current alarms management. This window mayappear as shown in Figure 10. . It provides a first view on the set of available sublists and on the situationof the network.

The window is actualized according to the flow of incoming alarms. When a new alarm arrives, filter match-ing is tried for each sublist. If the test is successful for a given sublist, the alarm is added to this sublist,according to its displaying and sort criteria.

Available global information is displayed by counters that show either the number of alarms of a single

severity level, or the total number of alarms in the sublist, or the number of non acknowledged and cleared

alarms. These counters may be realtime refreshed (when the sublist is active) or not (when the sublist

is inactive) according to the operators needs (see section 3.1 Current alarms management startup).

N.B. The NACK counter owns its proper status color, contrarily to the ACK counter. The status color

of the ACK counter is identical to those assigned to the NACK counter. Moreover, the displayed

ACK alarms number is equal to the displayed NACK alarms number.

The figure presents the standard aspect of this window, as it appears when running the application after

its installation on the user platform, without customization.

The default set of sublists managed by the AS application for current alarms is composed of:

The Main Alarm Sublist contains all the available alarms.

The Critical (resp. Major, Minor, Warning, Indeterminate) sublist contains the subset of alarms whose

severity is critical (resp. major, minor, warning, indeterminate).

The Cleared Alarm sublist contains the subset of alarms which have been cleared.

The Default Alarm Sublist plays a specific role for creating new sublists and its management will

be presented later on.

In this Current Alarms case, the active sublists are immediately initialized according to the network situa-

tion.


33/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

27

02

957.130.722 A

/3AL 71109 AAAA

124

124

Information

box

Name of the AS IM +CAL status color

Total

CountersSeverity

Counters

Alarmsincomingflag

Status

Counters

InactiveSublists

SysIM0

Figure 10. Current Alarms Counter Summary window.

N.B. Because of the importance of its contents, this window may be configured so as to be alwaysput in foreground (whatever your environment) on alarms incomings. Use the Autoraiseop-

tion from the Displaypull down menu. Furthermore, navigation features described in the chap-

ter 6. Navigation Featuresallow to quickly bring it to the front.

The flag, before the sublist name, informs you that new alarms have arrived in the concerned sublist.

If you select (i.e. single click) or open (i.e. double click) the sublist, then this flag disappears (if there areno new incoming alarms).

Inactive sublists have all their counters set to.

The . character means there is no alarm in the corresponding field.

At the bottomright corner of the window, an indicator displays the corresponding AS IM name and thecolor of the C.A.L Status. This color is realtime updated. Overflow parameters are set by the operator(see section 4.1.1 Setting the Overflow parameters)

Once the Counter Summarywindow is displayed, you can begin to manage current alarms. To do so,you are expected to create sublists of the C.A.L. and to modify them by customizing their characteristics.

For these creation or modification operations, refer to the next sections 3.2 Creating a sublist, and 3.3 Mod-ifying a sublist.

Once these sublists have been opened, actions on alarms are available using the Actionpull down menu.These actions are detailed in section 3.9 Actions on selected alarms.


34/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

28

02

957.130.722 A

/3AL 71109 AAAA

124

124

If using the Saveoption from the Exitpull down menu, any sublist creation or any modification you performon sublists parameters are saved during exit process, and restored at the beginning of AS next sessions(persistency).


35/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.

ED

1AA000140004(9007)A4

ALICE04

.10

29

02

957.130.722 A

/3AL 71109 AAAA

124

124

3.2 Creating a sublist

To set up a new sublist, you will have to define its characteristics, i.e. its filter, the list of attributes to display

for the matching alarms, the sort criteria to be applied, the color to be assigned. To ease this process, the

creation of a sublist follows a cloning mechanism, that allows you to start from an existing definition and

then to adapt the parameters. You can choose to:

duplicate the characteristics of an existing sublist, use those of a special sublist, the Default Alarm Sublist, whose goal is to store a common initial defini-

tion corresponding to user preferences.

To create a new sublist using the first method, within the Counter Summarywindow, select the source sub-list in the table by clicking on its line, and then choose the Createoption from the Sublistpull down menuof the menu bar. To use the second method, do not select first a line in the table (or select the Default AlarmSublist line). Then run the menu option in the same way.

SysIM0

Figure 11. Creating a sublist

The following dialog box opens :

Ok


36/130

Allrig

htsreserve

d.

Pass

ingonan

dcopy

ingo

fthis

documen

t,usean

dcommun

ica

tiono

fitscon

ten

ts

no

tperm

ittedw

ithou

twri

ttenau

thoriza

tion

from

Alca

tel.