QUESTA PAGINA NON VA INSERITA NEL MANUALE

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

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

COD.MANUALE HDBK P/N: 957.130.722

A Ed.02 3AL 71109 AAAA Ed.02

1300NM 1330AS Rel. 5.1 Version 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) No pages TARGHETTE - LABELS frontespizio front manuale manual 2 numerate numbered da from a to

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

124 126 63

1/124

124/124

TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: TOTALE FOGLI A4 TOTAL A4 SHEETS: WARNING FOR A-UNITS OTHER THAN A-ITALY Labels are done according to A-Italy binder format.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02

RELEASED 3AL 71109 AAAA TQZZA 4 Y 1/ 4

957.130.722 TQZZA

Originators C.Mandroux

1330AS REL.5.1 VERSION 5.1.1 OPERATORS HANDBOOK

Domain Division Rubric Type Distribution Codes

: : : :

TND NM ALMAP ALARM SURVEILLANCE 1330AS REL.5.1 OPERATORS HANDBOOK Internal : External :

Approvals Name App. O.Frelot

Name App.

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

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02

RELEASED 3AL 71109 AAAA TQZZA 4 Y 2/ 4

957.130.722 TQZZA

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

Site MARCOUSSIS

ALCATEL OPTICS GROUP

1300NM 1330AS Rel. 5.1

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

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.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.1
Alarm Surveillance 957.130.722 A Ed.02 3AL 71109 AAAA Ed.02 OPERATORS HANDBOOK VOL.1/1

1300NM 1330AS Rel. 5.1 Alarm Surveillance

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

1300NM 1330AS Rel. 5.1

Alarm Surveillance Version 5.1.1 on
957.130.722 A Ed.02
1AA 00014 0004 (9007) A4 ALICE 04.10

3AL 71109 AAAA Ed.02

OPERATORS HANDBOOK

VOL.1/1

ED

02

RELEASED 3AL 71109 AAAA TQZZA 4 Y 3/ 4

957.130.722 TQZZA

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02

RELEASED

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

FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT

3AL 71109 AAAA TQZZA

4/ 4

Operator s Handbook

Alcatel 1300NM
Network Management

1330AS Rel.5.1
Alarm Surveillance

Version 5.1.1 on

957.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.

957.130.722 A Ed.02

3AL 71109 AAAA Ed.02

1300AS REL.5.1 OPERATORS HANDBOOK

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

TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Target audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Document description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 ALARM SURVEILLANCE PRINCIPLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Alarm Surveillance Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.1 Telecommunication Network operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.2 Alarm information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Alarm Surveillance Functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 An iterative approach for alarm description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.2 Current Alarms Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.3 Historical Alarms Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.4 Advanced Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 HMI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.1 General conventions and kinds of widgets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.2 Main windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.3 Dialogue boxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.4 Errors, confirmations and messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.5 Online Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 MANAGING CURRENT ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 Current alarms management startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Creating a sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 Modifying a sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.1 Modifying the sublist display parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.2 Modifying the sublist filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.3 Modifying the sorting rules of a sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4 Setting tone emission and scripts triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Visualizing (opening) a sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5 Deleting a sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6 Selecting alarms within a sublist window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 6 7 7 7 7 9 9 9 10 11 12 13 14 15 17 18 20 22 23 23 25 26 29 31 33 36 47 49 51 53 54

02 01
1AA 00014 0004 (9007) A4 ALICE 04.10

001219 991209 DATE

SC 00121901

O. Frelot O. Frelot

C. Mandroux F. Clenet ORIGINATOR

ED

CHANGE NOTE

APPRAISAL AUTHORITY

1300AS REL.5.1 VERSION 5.1.1 ON OPERATORS HANDBOOK

ED

02 957.130.722 A 3AL 71109 AAAA 124 1 / 124

3.6.1 Selecting a single or a group of alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.2 Selecting all alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.3 Deselecting all alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7 Exporting contents of a sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8 Visualizing full alarm information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9 Performing actions on selected alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9.1 Acknowledging alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9.2 Reserving or unreserving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9.3 Creating trouble tickets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9.4 Manual purging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9.5 Getting correlated alarms information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10 Getting reports on performed actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10.1 Visualizing the actions report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10.2 Clearing the whole report list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10.3 Deleting reports for some selected actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10.4 Configuring the Report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11 NE Symbols management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11.1 Alarm information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11.2 Most severe/Most recent Non cleared alarms management . . . . . . . . . . . . . . . . . . . . . . 4 ADMINISTERING ALARM SURVEILLANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Administering the C.A.L. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.1 C.A.L Size Control Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2 Setting the Overflow parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.3 Setting the Purging Sort Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.4 The Statistics Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 Customizing the Archiving Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4 Purging alarms automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5 Autocreating trouble tickets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6 Autoacknowledging alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7 Resynchronizing AS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 MANAGING HISTORICAL ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Introduction and capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 Historical alarms management start up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 Retrieving archived alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 Filtering archived alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1 Accessing the Filter panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.2 Using the different groups of the panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5 Managing User Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.1 Saving a set of alarms to an user file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.2 Retrieving alarms from a set of user files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.3 Deleting a set of user files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 NAVIGATION FEATURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 Navigating within the AS application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.1 Navigating through the sublists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.2 Navigating between the C.A.L. and the H.A.L. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.3 Navigating to the Counter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 Navigating toward external applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.1 Navigating to the PNM application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.2 Navigating to the ELM application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.3 Sending alarm information to an external application . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

54 54 54 55 58 60 60 61 63 64 65 66 66 68 69 69 70 71 73 75 75 78 78 79 80 81 82 84 85 85 86 89 89 91 93 97 97 98 108 108 110 111 113 114 114 115 115 116 116 117 117

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 2 / 124

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

7 ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 GLOSSARY OF TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

119 121 124

INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 3 / 124

LIST OF FIGURES AND TABLES

Figure 1. Telecommunication network and alarm emission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2. Current and Historical Functions of the Alarm Surveillance . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3. An iterative approach for alarm description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4. Advanced features mechanisms and alarm flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 5. Main window Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6. Mouse Action on Counter Summary working area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7. Mouse Actions on Current Alarm Sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 8. Additional window Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 9. Dialog window Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 10. Current Alarms Counter Summary window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 11. Creating a sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 12. Just created sublist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 13. Modifying a sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 14. Sublist modification Display panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 15. Sublist modification Colour definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 16. Colour selection The different methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 17. Sublist modification Displayed attributes: adding MO Instance . . . . . . . . . . . . . . . . . . Figure 18. Sublist Properties Filter Panel (Current Alarms case) . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 19. Sublist filter Event Date & Time group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 20. Sublist filter Edition of the list of time intervals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 21. Sublist filter Status group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 22. Sublist filter Severity level and AlarmType groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 23. Sublist filter Probable cause group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 24. Sublist filter Selection of probable causes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 25. Sublist filter Correlation group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 26. Instance Filter group MO instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 27. Instance filter group Friendly Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 28. MO Class filter group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 29. More Info window: Retrieval of MO Class, Instance and Friendly Name. . . . . . . . . . . . Figure 30. Extended Filter page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 31. Sublist Properties Sort Panel (Current Alarms case). . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 32. Addition of a dictionnary entry Error message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 33. trigger page of the Sublist Properties My_Sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 35. Opening a sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 36. Sublist contents window (Current Alarms case) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 37. Deleting a sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 38. Deletion of a sublist Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 39. Selecting all alarms within the Alarm Sublist window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 40. Exporting selected alarms of a sublist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 41. Output window Default aspect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 42. Output window Exporting alarms to a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 43. File Chooser window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 44. Getting full information about an alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 45. More Alarm Information window Identity panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 46. More Alarm Information window Correlation panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 47. Acknowledging a group of alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 48. Reserving selected alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 49. Unreserving some alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 50. Sending trouble tickets concerning selected alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 51. Manually purging selected alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 52. Correlated Notification Flag Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 11 12 16 20 21 21 22 23 27 29 30 31 32 33 34 35 36 38 38 39 40 40 41 41 42 43 43 44 45 47 48 49 50 51 52 53 53 54 55 56 56 57 58 58 59 60 61 62 63 64 65

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 4 / 124

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

Figure 53. Visualizing report information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 54. Report window An abort case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 55. Clearing the whole report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 56. Deleting the report of a selected action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 57. Display options for Report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 58. Submap window example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 59. Alert Symbol view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 60. Administration window for alarm surveillance configuration . . . . . . . . . . . . . . . . . . . . . . . . Figure 61. Failure report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 62. C.A.L. Administration Overflow Parameter zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 63. C.A.L. Administration Purging Criteria zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 64. C.A.L. Administration Statistics zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 65. Administration Archiving filter Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 66. Resynchronizing the AS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 67. Confirmation box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 68. Message box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 69. The different alarm archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 70. AS historical part start up : Counter Summary window . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 71. historical Sublist pull down menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 72. Selecting a source of archived alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 73. Retrieval operation Appending or overwriting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 74. Retrieval operation Confirming the reinitialization of sublists. . . . . . . . . . . . . . . . . . . . . . Figure 75. Retrieval operation Progress window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 76. Interrupting the historical alarm retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 77. Error message box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 78. Sublist Properties Filter Panel (Historical Alarms case) . . . . . . . . . . . . . . . . . . . . . . . . . Figure 79. Sublist filter Event Date & Time group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 80. Sublist filter Edition of the list of time intervals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 81. Sublist filter Severity level and Alarm Type groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 82. Sublist filter Probable cause group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 83. Sublist filter Selection of probable causes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 84. Sublist filter Insertion Cause group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 85. Sublist filter Source filter page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 86. More Info window: Retrieval of MO Class, Instance and Friendly Name. . . . . . . . . . . . Figure 87. Extended filter page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 88. Saving historical alarms to an user file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 89. Historical user file Specification of the file name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 90. Historical user file Storage progress window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 91. Historical user files Selection of files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 92. Deleting archive user files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 93. Navigation pull down menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 94. Navigating to a opened sublist named NE_Nantes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 95. Accessing the Historical Counter Summary from the Current Counter Summary window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 96. Accessing PNM submap from a Current Alarms sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 97. Calling the ELM application for HPLog configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . .

66 66 68 69 69 70 71 75 76 79 80 81 82 86 86 87 90 91 92 93 94 94 95 95 95 97 99 99 100 101 101 102 103 104 106 108 109 109 110 111 113 114 115 116 117

1AA 00014 0004 (9007) A4 ALICE 04.10

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

ED

02 957.130.722 A 3AL 71109 AAAA 124 5 / 124

HISTORY
AS INTERNAL DOCUMENT 3BP 21600 0010 TCZZA Edition Authors Date Page / Paragraph All All Observations
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

2.0 3.0

F. Clenet C. Mandroux

990113 000517

Modifications and updating. Modifications and updating.

AS HANDBOOK P/N 3AL 71109 AAAA (factory P/N 957.130.722 A) Ed.01 created on December 9, 1999 Ed.02 created on December 19, 2000 Edition 01 02 Date 991209 001219 corresponding to ED.2.0 of internal document corresponding to ED.3.0 of internal document Corresponding to internal document edition ED.2.0 ED.3.0

Applicable documents (for Alcatel internal use only) [1] DOCUMENT MANAGEMENT PROCEDURE Ed03, NMU/C/RT/95/034 AAR, ALMAP Platform and Generic Components PLC Product Life Cycle Ed02, NMU/C/96/0045 NMU, ALMAP PLC Amendment Ed01, 3BP 216130007 ASZZA

[2]

[3]

Reference Documents (for Alcatel internal use only) [4] NMU, ALMAP Feature Description Ed02, NMU/C/96/0056 NMU, ALMAP AS Feature Description Ed04, NMU/C/96/0036 AAR, ALMAP AS5.0 Technical Specification Ed02, 3BP 21600 0001 DSZZA AAR, ALMAP AS5.0 User Interface Overview Ed01, 3BP 21600 0002 DSZZA X.733 Alarm Reporting Function ITUT (CCITT) Feb. 1992 X.734 Event Report Management Function ITUT (CCITT) 1993

[5]

[6]

[7]

[8]

[9]
1AA 00014 0004 (9007) A4 ALICE 04.10

[10] NMU, ALMAP PNM320 User s Guide Ed01, 3BP21619 0004 TCZZA

ED

02 957.130.722 A 3AL 71109 AAAA 124 6 / 124

1 INTRODUCTION 1.1 Scope.

This document contains the Operator s 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.

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

1.2 Target audience.

This document is intended for all the Operators using the Alarm Surveillance subsystem in their application.

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 functionalities 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 current 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. 02 957.130.722 A 3AL 71109 AAAA 124 7 / 124

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

Autoacknowledging. Resynchronizing the AS.

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

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.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 8 / 124

2 ALARM SURVEILLANCE PRINCIPLES

The Alarm Surveillance (AS) is a generic component of the ALMAP product. It provides efficient mechanisms to control, supervise and manage equipment anomalies that may occur in a Telecommunication Network.

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

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 provided 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 message into the network. In such a case, the warning message is called an alarm, and the mechanism is called 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 problem. Once the disabled resource is repaired, other resources may use it again. If the operation is successfully 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 operation. The Alarm Surveillance product is dedicated to this purpose.

NETWORK Network Operator

Network Operator

1AA 00014 0004 (9007) A4 ALICE 04.10

available resource

faulty resource

resource emitting alarms

Figure 1. Telecommunication network and alarm emission

ED

02 957.130.722 A 3AL 71109 AAAA 124 9 / 124

2.1.2 Alarm information Alarms or Alarm notifications consist in messages emitted by network resources that have detected problems 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 identification 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 management process.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 10 / 124

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

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 multivendor 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.

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

RealTime Management AS Operator print/export alarms AS Operator

Static Analysis

print/export alarms

Printer Export Files display alarms manage alarms display alarms

Printer Export Files

CURRENT ALARMS

archive alarms

ARCHIVED ALARMS

Alarm Surveillance raise & clear alarms

NETWORK RESOURCES

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.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 11 / 124

In the current alarm case, a synthesis of alarm information can be displayed in submap. This option depends 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 Summary window: 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. The Alarm Sublist window: 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. The More Information window: 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.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

b)

c)

Figure 3. illustrates the principle of this iterative approach.

Alarms

Counter Summary
sort

Alarm Sublist

More Information

filter
increasing precision

actual network

global vision 1 summary, n sublists

local vision 1 sublist, n alarms

detailed vision 1 alarm

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 section 2.2.3 Historical Alarms Management deals with manipulation of historical alarms. Section 2.2.4 Advanced Features gives additional features provided to the operator for a more efficient alarm surveillance.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 12 / 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 a specific icon on the screen. The alarm may be displayed as soon at it is signalled according to the operator needs. 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.

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

b)

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 operator s request. Furthermore, 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 resource 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 archived 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 repeated 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 operator s 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.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 13 / 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 requested 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. 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 sublist. 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. getting detailed information on a particular alarm.

b)

c)

d)

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 robustness, the recurrence of problems, or to help the operator to dimension the network, detect its critical points, ...

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 14 / 124

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

2.2.4 Advanced Features Because the Current Alarms List (C.A.L.) has a limited size, the operator is provided with several advanced 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 behaviour of the C.A.L. when the overflow occurs (wrap/halt). In wrap mode, a mechanism of purge will be automatically 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). an automatic purge mechanism: according to filtering criteria, some incoming alarms may be immediately 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).

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

b)

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 Autoacknowledging alarms). an automatic trouble ticket creation mechanism: according to filtering criteria, the operator is provided the way to automatically request the creation of trouble tickets to an external ARS application when the alarms appear in the C.A.L.. 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. a synchronization mechanism: because the C.A.L., for any reason, may happen to become inconsistent 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. 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. 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).

d)

e)

f)

g)

h)

Figure 4. illustrates the advanced features mechanisms.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 15 / 124

RealTime Management
navigation

Static Analysis AS Operator

navigation

AS Operator EXTERNAL APPLICATION

navigation

sublist ordering and filtering autobeeping archiving filter auto trouble ticket creation overflow purge

sublist ordering and fi ltering

alarm retrieving

ARS

CURRENT ALARMS

ARCHIVED ALARMS

autoacknowledgement filter

autopurge filter

Alarm flow Alarm ordering Alarm filtering NETWORK RESOURCES

Figure 4. Advanced features mechanisms and alarm flow

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 16 / 124

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

2.3 HMI Overview

This section gives some general rules concerning the whole AS User interface. It includes a general description 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 simple interface: 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. an interactive interface: dialogs are popped up before performing any unreversible operations. Messages are systematically displayed on the screen to inform the operator of the state of the Alarm Surveillance. A contextual help offers from any window a support to the operator. a personal interface: the operator can easily customize colors, fonts and general layout of the interface. This customization is saved while exiting the interface. It is automatically retrieved while starting it again.

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

b)

c)

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 17 / 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 that additional 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 Alt key 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.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

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 remove 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 denominations used 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 :

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 18 / 124

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

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 Ctrl key. 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 Attributes), 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.

1AA 00014 0004 (9007) A4 ALICE 04.10

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 dictionaries entries.

ED

02 957.130.722 A 3AL 71109 AAAA 124 19 / 124

Main windows are primary windows. The operator does not need to close them before performing any other action. A possible presentation of main windows is shown in Figure 5.
WINDOW TITLE MENU BAR

WORKING AREA

INFORMATION BOX

Figure 5. Main window Organization The Counter Summary and the Alarm Sublist windows belong to this window category, and their functionalities 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 visualization. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10

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.

ED

02 957.130.722 A 3AL 71109 AAAA 124 20 / 124

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

2.3.2 Main windows.

The Figure 6. and Figure 7. respectively synthetisizes the graphical capabilities of the Counter Summary and Alarm Sublist working areas :
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Location \ Action Column Title

Click

Double Click

Drag & Drop

Sublist Line Unselected Single selection Multiple selection (0) select sublist unselect sublist

hide column

move column (1) (2)

open the SINGLE pointed sublist

move sublist line (3)

(0) Multiple selection is not allowed in the Counter Summary. (1) Drag&Drop on the left or right edge of column title resizes the width of the row. (2) Drag&Drop on the bottom edge of a column title resizes the height of the row. (3) Drag&Drop on the bottom or high edge of the 1.st column of any rows resizes the height of all rows.

Figure 6. Mouse Action on Counter Summary working area

Location \ Action Column Titles

Click

Double Click

Drag & Drop

Alarms Unselected Single selection Multiple selection select alarm

hide column

move column (1)

show more info on THE pointed alarm

(2)

(1) Drag&Drop on the bottom edge of a column title resizes the height of the row. (2) Drag&Drop on the bottom or high edge of the 1.st column of any rows resizes the height of all rows.

Figure 7. Mouse Actions on Current Alarm Sublist

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 21 / 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 properties. Their content is refreshed according to operator s selection. A possible presentation of additional windows is shown in Figure 8.
WINDOW TITLE FOLDER All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

WORKING AREA(S)

BUTTON AREA Apply Reset Close Help

Figure 8. Additional window Organization Property, Administration and More Info windows 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 on the 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 Apply are 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. Help causes the display an Online Help window.

In some other dialogue boxes, especially those with only one panel, Close may be replaced by Cancel, with a similar operation. However, in thoses cases, Apply causes the window to close after saving the user input.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 22 / 124

2.3.4 Errors, confirmations and messages. To display some messages, especially errors, or to ask for confirmation before performing some actions such as deletions, the system uses small modal windows. You must take the dialogue into account and close the window before any other action on the application. A possible presentation of such a window is shown in Figure 9.
WINDOW TITLE DIALOG AREA BUTTON AREA Ok Cancel Help

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

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 Ok button to acknowledge the message. For a confirmation, the buttons will include Ok and Cancel, and sometimes Help. Output, Tone Configuration and basic dialog windows belong to this category of windows. Their functionalities 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 Help popup menu from the menu bar in any workspace window, and then selecting one 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 toward 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 Help button available in most dialogue boxes. This method gives access to same contents that the On Window menu 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.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 23 / 124

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02

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

3AL 71109 AAAA

124

24 / 124

3 MANAGING CURRENT ALARMS

When working with current alarms the user interface is primarily organized around :
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

the Counter Summary window, which provides the global level of information, one or several sublist windows, each of them providing a second level of information on a parametrized subset of alarms, together with a set of possible commands on these alarms. a Submap window, which allows to display a synthesis of alarm information for each NE (see section 3.11). The existence of this submap is optional and depends on a configuration file. a Most Severe Alarms sublist, 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 creation 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 a given 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, except for the submap window which is here not present.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 25 / 124

3.1 Current alarms management startup

The Counter Summary window is a startup windows for current alarms management. This window may appear as shown in Figure 10. . It provides a first view on the set of available sublists and on the situation of the network. The window is actualized according to the flow of incoming alarms. When a new alarm arrives, filter matching 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 operator s 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 situation.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 26 / 124

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

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

Alarms incoming flag

Total Counters

Severity Counters

Status Counters

Inactive Sublists

Information box SysIM0

Name of the AS IM + CAL status color 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 always put in foreground (whatever your environment) on alarms incomings. Use the Autoraise option from the Display pull down menu. Furthermore, navigation features described in the chapter 6. Navigation Features allow 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 are no 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 the color 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 Summary window 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 Modifying a sublist.
1AA 00014 0004 (9007) A4 ALICE 04.10

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

ED

02 957.130.722 A 3AL 71109 AAAA 124 27 / 124

If using the Save option from the Exit pull down menu, any sublist creation or any modification you perform on sublists parameters are saved during exit process, and restored at the beginning of AS next sessions (persistency).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 28 / 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 definition corresponding to user preferences.

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

To create a new sublist using the first method, within the Counter Summary window, select the source sublist in the table by clicking on its line, and then choose the Create option from the Sublist pull down menu of the menu bar. To use the second method, do not select first a line in the table (or select the Default Alarm Sublist line). Then run the menu option in the same way.

SysIM0

Figure 11. Creating a sublist The following dialog box opens :

1AA 00014 0004 (9007) A4 ALICE 04.10

Ok

ED

02 957.130.722 A 3AL 71109 AAAA 124 29 / 124

If a sublist is selected, the entry box contains the corresponding name (which is selected), so the user can modify easily the name. If no sublist is selected, the entry box is empty, and the user should write the sublist name. Click on Ok to confirm the creation operation, otherwise press Cancel. If the written name is empty, an error box is displayed. If the written name already exits, a warning box is displayed, then the sublist is created. The Counter Summary window is updated and a new sublist is displayed (e.g. ne sublist). At this moment, the new sublist has exactly the same characteristics as its source. As a consequence, the new sublist would have exactly the same content as the original one. So, the next operation is generally the modification of this new sublist to adjust its parameters. Refer to next section (3.3 Modifying a sublist) for commands and user interface.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

SysIM0

Figure 12. Just created sublist.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 30 / 124

3.3 Modifying a sublist

Modifying a sublist consists in modifying one or several of its characteristics:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

its name, the assigned colour, the level of information to be displayed for each alarm, through a list of attributes, the filter which specifies the content of the sublist (matching alarms), the sort criteria used to determine the order in which alarms will be displayed. the tone emission on incoming alarms, the scripts triggered when the number of alarms becomes greater or smaller than customizable values.

To modify a sublist, first select it by clicking on the corresponding line in the Counter Summary window, and then select the Modify option from the Sublist pull down menu (see Figure 13. ).

SysIM0

Figure 13. Modifying a sublist The following Sublist Properties window is then displayed:

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 31 / 124

Mouse Clicking Areas

Figure 14. Sublist modification Display panel This window is made up of three pages that can be accessed by clicking on the areas shown on Figure 14. . Each page is dedicated to a specific group of properties of the sublist. Operate the modifications in the different panels as described in the next paragraphs and press Apply to save your definitions. Then close the dialogue box pressing Close. N.B. Modifying an opened sublist (i.e. a sublist whose content is displayed by a window of the Figure 36. type) and clicking on the Apply button will cause this window to be immediately actualized, according to the changes performed.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 32 / 124

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

3.3.1 Modifying the sublist display parameters Modifying the sublist display consists in modifying three parameters :
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

the sublist name, the sublist counter colour, the displayed attributes.

These criteria do not modify the content of the sublist but change the display according to your preferences. 3.3.1.1 Modifing the sublist name To modify the sublist name, click on the Sublist Name edit zone and replace the existing name. Authorized names are names composed of alphanumeric characters plus the _, ,. ones. The size must also be less that or equal to 32 characters. 3.3.1.2 Modifying the colour The Counter Colour of a sublist is the color used to display the sublist line within the Counter Summary window table. For example, by default, critical alarm sublist appears in red colour. To change this colour, press the large button labeled with the sublist name. The following window opens up :

Ok

Cancel

Figure 15. Sublist modification Colour definition Two colour models are provided: RGB (Red, Green and Blue) which is based on proportions of primary colours, HSV (HueSaturationValue).

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 33 / 124

Moreover, you are given the possibility to choose the colour from a list of colour names or to select it from a palette (see Figure 16. ).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Select the mode you want to use by opening if necessary one of the option buttons at the top of the window and choosing the relevant option. In RGB and HSV modes, adjust the cursor for each slider bar. The corresponding numeric value is displayed at the bottom. In Color Disk mode, the colour is defined by two complementary data: a point on the disk, the position of the curson on the horizontal bar.

Define these two parameters by clicking on these two elements at the desired position. As in HSV or RGB mode, you can also drag the mouse to progressively find the right colour. In Color Names mode, simply select the desired option in the list. In every mode, the current definition is shown in the rectangular area at the right bottom of the window. Press Ok when you have finished.

Ok

Cancel

Ok

Cancel

Figure 16. Colour selection The different methods.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 34 / 124

3.3.1.3 Modifying the list of displayed attributes Displayed attributes are the alarm attributes that appear when the sublist is opened (see section 3.4 Visualizing a sublist).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

This panel (see Figure 17. ) includes two lists: one for the hidden attributes, not to be displayed in the table, one for the displayed attributes.

You can move one or several attributes from a list to the other one by selecting the desired items and then using the arrow buttons (left and right). Refer to section 2.3.1 General conventions and kind of widgets.

Figure 17. Sublist modification Displayed attributes: adding MO Instance . The set of possible attributes depends on the context. The lists are different in Current Alarms and Historical Alarms cases, but the user interaction is identical. In the second list (Displayed Attributes), the order of items also represents the order of the corresponding columns in the sublist table.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 35 / 124

3.3.2 Modifying the sublist filter The filter of a sublist is the criterion that determines the content of the sublist. In this regard, it is basically different from the display and sort criteria, that do not affect this content. In Current Alarms case, the Filter page of the Sublist Properties window has the following aspect :

Figure 18. Sublist Properties Filter Panel (Current Alarms case) The filter allows to store in a given sublist, alarms with common properties (values of attribute), matching some user defined criterions. Filters may be created for a session only. They can be also saved for a coming use.The filter is defined through a panel composed of several groups, each of them, at the exception of the dictionary group at the top, corresponding to a specific attribute or group of attributes and being enclosed in a specific page. The global condition defining the filter is built by applying an AND operator between the elementary conditions defined by the groups. When, inside a group, a list offers multiple selection for an attribute, the condition on this attribute results from an OR on the different selected values.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 36 / 124

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

To activate or deactivate one of the groups (e.g. Severity or Alarm Type), you have to click the check button of the zone (black color means that the area has been activated). The following paragraphs detail the operations for the different groups.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

3.3.2.1 Using the Filters Dictionary The filters dictionary group is placed in the upper zone of the Filter panel :

Matching status of the filter

The dictionary provides a list of filters previously prepared and available to ease your work. In this dictionary, filters can be created, modified or removed according to your choice. Clicking on the button shows the drop down list containing the existing filter names. Clicking on one of them selects it and loads the various elementary criterions in the different other fields of the panel.. The matching status zone indicates if alarms could match this filter. One of the following three statuses may appear : Match none : no alarm could match the filter. In this case, there may be conflicting options specified in the filter. Match some : alarms may match the filter. Match all : all alarms will match the filter. This means in particular that a sublist characterized by this type of filter will extract all alarms of the main list (in the current and historical case).

To create a new filter in the dictionary, fill the edit zone with any authorized name. Authorized names are names containing letters (case independent), numbers, and the three , _, and . characters. Size of a name should not exceed 32 characters. Clicking on the Save button will take into account every element of the Filter Panel. So this must be done after having performed the modifications on the other elements of the page.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 37 / 124

3.3.2.2 Selecting alarms according to a Date and Time (basic filter page) The AS application gives the possibility to select alarms according to the date and time of their raising event. To do this, select first the Basic page by clicking on the corresponding tab. You can specify a list of intervals for date and time. An alarm will be selected if the raising event took place in one of the intervals. In the filter panel, the Event Date & Time Ranges zone presents in a readonly box the list of the intervals already defined.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Figure 19. Sublist filter Event Date & Time group.

Figure 20. Sublist filter Edition of the list of time intervals. To add some intervals or to adapt this list, press the Select... button. Another dialogue box opens, presented in Figure 20. As in all other relevant places of the application, times have to be expressed using local definition, not GMT.
1AA 00014 0004 (9007) A4 ALICE 04.10

Specify a interval (beginning and end) with the text boxes, respecting the proposed format, or adapt it with the spin buttons, after selecting the desired subpart (month, day, year, hours, minutes, seconds) by clicking on the right position inside a box (see section 2.3.1 General conventions and kinds of widgets).

ED

02 957.130.722 A 3AL 71109 AAAA 124 38 / 124

Add it to the list of intervals, displayed on the right part of the dialogue box, by pressing the rightarrow button. Reciprocally, you can suppress an existing time interval from this list by selecting it and then pressing the leftarrow button.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

N.B.

The validation of a date depends on your operating way : A date that is specified by typing in the entry box is only validated when you press the right arrow. A date that is specified by using the spin buttons can not be false, so it is automatically validated.

To modify an interval, proceed in two steps (deletion and addition): Select it in the right list and press the leftarrow button. It disappears from the list (deletion), but its definition is moved to the edition area on the left. Adapt this definition according to your needs and press the rightarrow button. The new interval is inserted in the list.

Press Apply to come back to the Sublist Properties (Filter panel) window. 3.3.2.3 Selecting alarms according to their status (basic filter page) In Current Alarms management context, alarms can be selected according to their statuses. You can manage separately the statuses corresponding to: N.B. Reservation, Acknowledgement, Clearing. Each of these statuses are described in section 8 Glossary of Terms.

For each of these statuses, you can insert a condition in the filter and specify the desired state (set or not). To do so, select first the Basic page by clicking on the corresponding tab, then check the relevant check button and select the wanted option by opening the option list on the right. For example, to include in the list the acknowledged alarms, check on Acknowledgement button and select ACK from the option list.

Figure 21. Sublist filter Status group.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 39 / 124

3.3.2.4 Selecting alarms according to their severity level or type (basic filter page) In both contexts (current and historical alarms management), alarms can also be filtered according to their severity level or their alarm type.

Figure 22. Sublist filter Severity level and AlarmType groups. For each group, the test can be operated against several values, offering an OR boolean operator through multiple selection in the list. Select first the Basic page by clicking on the corresponding tab and then click on the check buttons Severity or Alarm Type to activate the respective zones if they are not activated. Then, select the desired fields with the left mouse button. Reciprocally, click also on the check buttons to deactivate the zones if they are already activated and you want to remove the corresponding condition from the filter. 3.3.2.5 Selecting alarms according to their probable cause (basic filter page) Another attribute that may be used for filtering is the probable cause of the alarm. Exactly as for severity or type, several values can be selected to define an OR combination. However, the dialogue is different. The list presented at this panel level is readonly and displays the causes already selected (in previous operations). It is initially empty. The set of Probable Causes is defined in a repository file. Probables Causes are predefined when AS application is launched. They are loaded from a configuration file that gives the translation between attribute identifier (oid/Integer) and displayed associated text.

Figure 23. Sublist filter Probable cause group.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 40 / 124

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

To select alarms according to their probable cause, select first the Basic page by clicking on the corresponding tab, then click on the check button to activate the zone and press the Select... button. A new window opens up in which the operator can adapt the list of selected probable causes.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Figure 24. Sublist filter Selection of probable causes. The window includes two lists: one for the causes to be no selected, one for the causes to be taken into account.

You can move one or several elements from a list to the other one by selecting the desired items and then using the arrow buttons (left and right). Refer to section 2.3.1 General conventions and kinds of widgets. At the end of the operation, press Ok. This window closes and the list at the panel level is updated. 3.3.2.6 Selecting alarms according to their correlation status (basic filter page) In Current Alarms case, you can select alarms according to their correlation status. To do this, select first the Basic page by clicking on the corresponding tab, then select the kind of desired alarms using the Correlation option button.

Figure 25. Sublist filter Correlation group Click on the check button to activate the zone if necessary. Then click on the list zone to drop it down and select an item. N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10

A Primary alarm has no correlated alarms while a Correlated alarm has a list of correlated alarms displayed in the Correlated tab of the More Alarm Information window.

Selecting Primary Alarms will add in the filter a condition specifying that the correlation status must be false, excluding all the correlated alarms. Selecting Correlated alarms will add a condition specifying that this status must be true.

ED

02 957.130.722 A 3AL 71109 AAAA 124 41 / 124

3.3.2.7 Selecting alarms according to their attribute type (source filter page) You are also given the possibility to extract alarms considering their MO class (see section 3.3.2.7 Selecting alarms according to their MO Class), MO Instance or Friendly Name (NE). To add a test on such an attribute, select first the Source filter panel by clicking on the relevant tab. The Source filter panel contains two attributes (Object Instance and Object Class). For each attribute type, the application offers a friendly display with gadgets sets. All the gadget sets have a check button with a name. This name is the name given in a configuration file. The check button selection allows the operator to use or not this attribute in the filter. If it is selected, this attribute is used in the filter, otherwise it is not used in the filter. If the two attributes are used, the filter will consist in an AND condition on the used attributes. The two types of attributes, which may be used, are described below : a) The Object Instance type :
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

A selector allows to choose how does the instance will be managed (as a friendly name or as a MO Instance) If MO Instance is selected (see Figure 26. ), you can specify the kind of test to be performed using the option button on the left, which presents the following options : Base : to only consider the object specified by the instance, Subtree : to also include in the search all the objects contained in the specified object.

Figure 26. Instance Filter group MO instance If Friendly Name is selected, you can also specify the nature of the test using the same option button as above, which now presents a modified list of options : Equal : selfunderstanding, Substring : the actual friendly name must contain the specified string, Begin with: the actual friendly name must begin by the specified string, End with: the actual friendly name must end by the specified string.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 42 / 124

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

Figure 27. Instance filter group Friendly Name Enter the desired value in the lower edit field and then click on the Add button. Your value appears now in the right readonly zone. If you want to modify an existing value appearing in this readonly list, select it first by clicking on it with the left mouse button. This causes the left zone to be put in conformity with the selected element (this means that one of the Friendly Name or MO Instance check buttons is checked, the option button points to the option in accordance with the selected element and the edit field is also updated). Bring any modifications you want in this zone and valid them by clicking on the Modify push button (note that this button remains disabled as long as no element or more than one have been selected in the right list box). Multiple selection is available in the right list box to allow removing action (using the Remove button). To do this, select one or more elements in the right list box and click on the initially disabled Remove button. b) The Object Class type :

In AS, you are given the possiblity to extract alarms with respect to multiple MO Classes attribute values.

Figure 28. MO Class filter group

1AA 00014 0004 (9007) A4 ALICE 04.10

This zone includes two lists : one (Unselected MO Class) for the MO Classes which will not be involved in the extraction process, one (Selected MO Class) for the MO Classes participating to this process, 02 957.130.722 A 3AL 71109 AAAA 124 43 / 124

ED

You can move one or several elements from a list to the other one by selecting the desired items and then using the arrows buttons (left and right). Refer to section 2.3.1 General conventions and kinds of widgets.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

To retrieve valid values for MO Class, MO Instance and Friendly Name, you can make use of the More Info window. This window can be called from any opened sublist window after selection of an alarm in the table. The three attributes are displayed in the Identity panel.

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

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 44 / 124

3.3.2.8 Selecting alarms according to their additional info (extended filter page) In AS, you are given the possiblity to extract alarms considering their additional info attribute values. To do this, select first the Extended filter page by clicking on the relevant tab (see Figure 30. ). Check the Additional Info check button to activate the zone if necessary.

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

Figure 30. Extended Filter page The availability of the Extended panel depends on the Additional Info repository : it may be insensitive if Additional Info repository is empty. The Extended filter is defined through a zone composed of numerotated Additional Info check buttons, each of them being associated with an option button, wich specifies the nature of the test, and an edit field. The push buttons and edit fields are activated once the relevant Additional Info check button has been checked. A test is defined by an operator AND applied between the conditions specified at the level of each activated Additional Info check button. Fill the desired fields.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 45 / 124

N.B.

When an alarm does not contain a value for the additional info attribute, this alarm will not match the condition different on a value of this attribute.

If you want to modify an existing test (i.e. appearing in the readonly zone), select it first in this zone by clicking on it. The upper zone of the page is updated according to the content of the test. Modify your test and then click on the Modify button. The test is now updated. In a same way, removing an existing test is done by first selecting the test and then clicking on the Remove button. The removed test disappears from the list. Note that multiple selection is available in the existing tests list. In this case, the additional info check boxes zone relates to the last selected test, but the Modify button is not active.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 46 / 124

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

Then, to add your test involving additional info attributes to the existing ones (if any), click on the Add button situated below this zone. As a result of this, the test appears (in an explicit form showing the elementary expressions and the logical operator AND applied between them) in the readonly zone located at the bottom of the page. The extended filter results in an OR operator applied between the different existing tests.

3.3.3 Modifying the sorting rules of a sublist The sorting page of the Sublist Properties window presents the following aspect :
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Figure 31. Sublist Properties Sort Panel (Current Alarms case). This panel includes two lists: one (Unselected Sort Criteria) for the attributes which will not be involved in the sort process, one (Selected Sort Criteria) for the attributes participating to this process.

You can move one or several attributes from a list to the other one by selecting the desired items and then using the arrow buttons (left and right). Refer to section 2.3.1 General conventions and kinds of widgets. The set of possible attributes depends on the context. The lists are different in Current Alarms and Historical Alarms cases, but the user interaction is identical. In the second list (Selected Sort Criteria), the order of items also represents the priority order for the sort process. For each attribute of the right list, you can also specify the order the values taken by this attribute are considered (ascending or descending order). The current direction is indicated by the option button on the right of the attribute name. To invert this order, click on this button. Its label then changes (Incr or Decr).
1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

For boolean attributes such as Reserve Status, the set value (e.g. Reserved) is assimilated to 1, the unset value (e.g. Unreserved) to 0, which allows defining an ascending or descending order.

ED

02 957.130.722 A 3AL 71109 AAAA 124 47 / 124

As in several other contexts, you can benefit of a dictionary of sorting configurations to ease your work. The corresponding group (Sort Name) is located at the top of the panel. You can choose among available entries, add another one from your definition, or remove an existing entry button and then that will not be useful anymore. Loading a configuration is done by first clicking on the selecting the desired entry through its name. When creating a new entry by pressing the Save button, authorized names are names containing letters (case independent), numbers, and the three ,_,. characters. The size of the name should not exceed 32 characters. If the specified name is incorrect, then the following message appears:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Figure 32. Addition of a dictionnary entry Error message.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 48 / 124

3.3.4 Setting tone emission and scripts triggering In AS, you are given the possibility to set tone emission on incoming alarms in the sublist (whatever the severity level).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

You are also given the possibility to trigger scripts execution as the number of alarms contained in the sublist becomes lower or greater than customizable values. To do this, select first the Trigger page by clicking on the relevant tab. The trigger page of the Sublist Properties window presents the following aspect :

Figure 33. trigger page of the Sublist Properties My_Sublist To activate tone emission on alarms incomings, check the Tone On/Off button of the upper page zone. In this case, AS will trigger a tone emission each time a new alarm is incoming in the concerned sublist, that is matches the filter defined for this sublist (you may for example set tone emission for the predefined critical sublist and be this way warned if critical alarms are sent to the AS).

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 49 / 124

N.B.

In case of incoming alarms package (one or several alarms) or incoming alarms in several displayed sublists, the AS application triggers a single tone emission (due to physical limitation).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

To deactivate Tone emission, uncheck the button. To extend the trigger features, AS gives you the possibility to execute any command line according to the number of alarms contained in the sublist (this would allow you for example to load some particular process as soon as the number of critical alarms exceeds a certain value). Two distinct command execution criteria can be defined : when the number of alarms becomes greater than a specified value. when the number of alarms becomes smaller than a specified value.

To define the first criterion, check the Execute check button to activate the upper zone of the Trigger frame (see Figure 33. ). Then fill the edit zone with the command or the full path of the executable file. To do this, you can use the File Chooser window which can be accessed using the Select... button (see Figure 34. ).

Figure 34. Fill the edition field with the number over which the execution must be started. The second criterion definition follows the same steps except that the lower zone of the Trigger frame is involved in this case.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 50 / 124

3.4 Visualizing (opening) a sublist

Once a sublist has been created and its parameters defined (see previous section), you may want its content to be displayed. Counter Summary only displays global information (the number of alarms of each severity level). To get more information, i.e. the list of alarms contained in the sublist, you must open this sublist. To open a sublist, select the corresponding line in the Counter Summary table. Then, select the Open option from the Sublist pull down menu.

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

SysIM0

Figure 35. Opening a sublist The figure above points out how to open the activated sublist named My_Sublist. A specific window dedicated to this sublist appears (Figure 36. ). As an alternate method, you can simply doubleclick on the line in the table. The window also opens.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 51 / 124

Actions and Displaying instructions on alarms are available

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

Figure 36. Sublist contents window (Current Alarms case) This window presents a table of the alarms matching the sublist filter. The columns of the table correspond to the displayed subset of alarm attributes, which has been defined as one of the sublist parameters. Above the table, the global information already available in the Counter Summary window is repeated. The window also contains an enriched menu bar which allows to perform actions on selected alarms, such as acknowledging or purging them or displaying more info about them. In Current Alarms case, sublist windows content is permanently refreshed according to alarm incomings and sublist characteristics (filter, sort, ...) (except for windows issued from the Correlated Alarms command). From the Current Alarms sublist window, the operator may perform actions on each alarm of the sublist. Any Current Alarms sublist window can be closed by the operator.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 52 / 124

3.5 Deleting a sublist

Any sublist, excepting the Main Alarm List and the Default Alarm Sublist, can be deleted.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

To delete a sublist, select it first from the Counter Summary table by clicking on the corresponding line with the left mouse button. Then, select the Delete... option from the Sublist pull down menu as shown on Figure 37. .

SysIM0

Figure 37. Deleting a sublist Before the actual deletion, you are asked for a confirmation.

Yes

No

Figure 38. Deletion of a sublist Confirmation In case of confirmation, the sublist disappears from the Counter Summary table.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 53 / 124

3.6 Selecting alarms within a sublist window

Once a sublist has been opened, one or more alarms can be selected using the mouse. Selecting or deselecting all alarms can be done via the menu bar of this window. 3.6.1 Selecting a single or a group of alarms To select a single or a group of alarms, click on the desired alarm or drag the mouse along the alarms you want to select. You can also use some combinations of mouse and keystrokes: Once an alarm has been selected in the list, the <Shift> + left button click action selects all the alarms appearing between the first selected alarm and the clicked alarm. The <Ctrl> + left button click action selects an alarm outside a given existing selection without removing this selection (this allows to select alarms which are not consecutive in a list). This same combination also allows to unselect a previouslyselected alarm.

3.6.2 Selecting all alarms To select all alarms within the Alarm Sublist window, select the All option of the Select cascading menu from the Action pull down menu (Figure 39. ).

Figure 39. Selecting all alarms within the Alarm Sublist window

3.6.3 Deselecting all alarms To deselect all alarms, select the None option of the Select cascading menu from the Action pull down menu.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 54 / 124

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

3.7 Exporting contents of a sublist

The content of a sublist can be exported to a file or sent to a printer as well as the content of a single alarm (for this last part, see the section 3.8 Visualizing full alarm information). In both cases, you will be requested to fill the Output window with the desired parameters. Exporting a whole sublist or part of it (i.e. a selected group of alarms belonging to this sublist) can be done from both Current or Historical Alarm Sublist windows. It means notably that you are requested to first open the sublists you want to export. To export a part of or the whole sublist, select first the alarms you want to incorporate. If necessary, refer to section 3.6 Selecting alarms within a sublist window. Then, choose the Output... item from the Action pull down menu, as shown on the figure below.

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

SysIM0

Selected Alarms

Figure 40. Exporting selected alarms of a sublist.

1AA 00014 0004 (9007) A4 ALICE 04.10

The Output window, that opens up, has the following aspect (by default, the Print zone is greyed and Export zone is enabled. A default print command and a default filename are specified) :

ED

02 957.130.722 A 3AL 71109 AAAA 124 55 / 124

Ok

Figure 41. Output window Default aspect You have the possibility to change the default options, exporting the alarms to an ASCII file of your choice, or using a specific print command. To activate either the Print zone or the Export zone, click on the radio button in front of the zone. Then, fill the edit zone corresponding to the type of export you have chosen (printer or ASCII file) (Figure 42. ).

Ok

Figure 42. Output window Exporting alarms to a file You are requested to fill the Print edit zone with a print command (there is a default one). Two possibilities actually exist: keeping the default command, developing your own print command that handles as a parameter the name of the temporary formatted file generated by the AS5.0 ; this file is not accessible and it is up to the AS5.0 application to take and execute the user command.

The Export edit zone is to be filled with a file name. There are two possibilities: specifying directly in the edit zone either the absolute path name of the file or a relative one if you want this file to be placed in a particular directory different from your current working directory. using the Select... push button. The following File Chooser window opens up, which allows to browse through the directories. You can select an existing file (in this case, this file will be overwritten), or specify a new name. Press Ok to come back to the Output window.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 56 / 124

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

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

Figure 43. File Chooser window. To actually launch the exportation or printing operation, click on the Ok push button (in the Ouput window). During the operation, a progress window is displayed. N.B. The exported information concerns all the attributes of the selected alarms, outside any considerations about the displayed or hidden attributes of the sublist. Thus, it may appear in the ASCII file more attributes than those visualized (but it will never include additional information such as correlation lists). On the contrary, information exported from the More Alarm Information window only concerns a single alarm. Its content corresponds to this More Alarm Information window (see section 3.8 Visualizing full alarm information).

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 57 / 124

3.8 Visualizing full alarm information

Once a sublist has been opened and its alarms displayed, you can get the full information about each of these alarms. This information is collected within the More Alarm Information window and presented through a folder of panels. To visualize all information relating to a specific alarm of a sublist, select first this alarm in the table and then choose the More Info... option from the Display pull down menu, as shown on the Figure 44. :

Figure 44. Getting full information about an alarm. An alternate method is to doubleclick on the alarm line in the table. The More Alarm Information window opens up :

Figure 45. More Alarm Information window Identity panel The More Alarm Info window of the Figure 45. presents several pages. Some may be activated and some others deactivated. Each of them regroups pieces of information of the same kind. All the fields, except the User Note on the Identity panel, have only display purpose and are therefore readonly.
1AA 00014 0004 (9007) A4 ALICE 04.10

The User Note zone is an edit zone limited to 500 characters that offers you the possibility to enter textual information, such as comments, which can be useful to some other operators. Click within this zone and enter your text. Press Apply to store it.

ED

02 957.130.722 A 3AL 71109 AAAA 124 58 / 124

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

When the More Alarm Information window is open, you can still access the Alarm Sublist window and select another alarm of the list. In this case, the More Alarm Information and its current panel comes back at the front and displayed information is actualized according to the new selected alarm.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Information contained in the More Alarm Information window (and relative to a single alarm) can be exported using the Output... button. To use the Output window that then opens up, please refer to section 3.7 Exporting contents from a sublist. Note that, if the user interface is similar, the exported information is different. Here, it is the full content of a single alarm (taking into account all the panels of the More Alarm Information window, except those which are greyed). There, it includes the set of attributes (whether they are displayed or not in the Alarm Sublist window), but not additional data such as the correlation list, for the group of selected alarms. N.B. Panels of the More Alarm Information window which do not concern the considered alarm are greyed. On the previous figure, the Correlation panel was greyed because the considered alarm has no correlated alarms. The Correlation panel of a correlated alarm has the following aspect:

Figure 46. More Alarm Information window Correlation panel. The lists of numbers correspond to the lists of alarm Notification IDs (see Figure 45. ). Refer to Technical Specification [5] for additional information.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 59 / 124

3.9 Performing actions on selected alarms

You can perform actions on selected alarms (such as reserving, acknowledging or purging them) from the sublist window. The different ways of selecting alarms have been detailed in the section 3.6 Selecting alarms within a sublist window. The actions described in this chapter only concern Current Alarms management. They are not available in historical context. 3.9.1 Acknowledging alarms By acknowledging a single or a group of selected alarms, you notify you are taking it or them into account. To acknowledge alarms, after having selected them, select the Acknowledge option from the Action pull down menu. Acknowledgement Status column

SysIM0

Figure 47. Acknowledging a group of alarms You are then asked a confirmation. Cancel the operation if desired.
1AA 00014 0004 (9007) A4 ALICE 04.10

Statuses of the selected alarms change, passing from NACK (non acknowledged) to ACK (acknowledged). N.B. Acknowledging a cleared alarm is an implicit archiving action. Thus, on the example above, the acknowledgement will actually archive the alarms and cause their disapperance from the list. 02 957.130.722 A 3AL 71109 AAAA 124 60 / 124

ED

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

3.9.2 Reserving or unreserving alarms To ensure to be the only responsible for an alarm, you can perform the reservation action on a current alarm.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

To reserve an alarm (or a group of alarms), select first the concerned alarm(s) and then select the Reserve option from the Action pull down menu, as shown on the Figure 48. Note that an alarm can only be reserved if it hasnt been reserved before by another operator (i.e. an alarm must have a Reservation Status set to NRSV). Reserve Status column

SysIM0

Figure 48. Reserving selected alarms Reservation statuses of the selected alarms change, passing form NRSV (non reserved) to RSV (reserved). To unreserve an alarm (or a group), select the Unreserve option from the Action pull down menu, as shown on the following figure:

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 61 / 124

SysIM0

Figure 49. Unreserving some alarms Reservation statuses of the selected alarms change, passing from RSV (reserved) to NRSV (non reserved). N.B. The only operator who can perform this unreserving action (for a given alarm) is the one who did the reservation action before. Even after an alarm has been unreserved, the Reservation User Name column keeps the name of the last user who reserved the alarm.

N.B.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 62 / 124

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

3.9.3 Creating trouble tickets A trouble ticket is a collection of all kind of information about a specific problem. Thus, it contains at least the information related to an alarm, but can also include information relative to the actions performed to solve this problem. AS can be customized to interface with the thirdparty Trouble Ticket managing product ARS (edited by Remedy Corporation). N.B. The availability of ARS is checked only when the user wants to access it. So the ARS configuration does not impact the Action menu.

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

To create trouble ticket(s) about a single or a group of alarms, first select them and then select the Trouble Ticket... option from the Action pull down menu, as shown on the following figure: Trouble Ticket Creation Flag column

SysIM0

Figure 50. Sending trouble tickets concerning selected alarms You are then asked a confirmation before effectively sending the request. After confirmation, the corresponding indicator in the table changes to YES.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 63 / 124

3.9.4 Manual purging You can manually purge alarms. To do so, select a single or a group of alarms, and then, select the Manual Purge... option from the Action pull down menu, as shown on the following figure:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

SysIM0

Figure 51. Manually purging selected alarms The purged alarms disappear from the sublist (or Main List) and are now archived, if matching the archiving filter.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 64 / 124

3.9.5 Getting correlated alarms information The Correlated Notification Flag of an alarm is an optional attribute (not required by X.733 standard) indicating a link of this alarm with a set of other alarms identified by a Notification Identifier and their relative Object instance. When the Correlated Notification Flag of an alarm is set to YES, the alarm is said to be correlated. You can see if alarms of an opened sublist are correlated or not, looking at this Correlated Notification Flag column (see Figure 52. ). N.B. If the Correlated Notification Flag Attribute doesnt appear in an opened sublist, it may have been removed. To recover it, select the Hidden Columns option from the Display pull down menu. All the attributes will then be displayed. NE100 NE100 NE100

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

Correlated Notification Flag column Figure 52. Correlated Notification Flag Attribute. For a correlated alarm, you can visualize the list of alarms which this alarm is linked with. To do so, select the Correlated Alarms... option from the Display pull down menu. A Sublist window dedicated to the correlated alarms opens up. Contrarily to other sublist windows (corresponding to actual sublists listed in the Counter Summary window), the content of this window will not be realtime refreshed at the arrival of new alarms. Trying to visualize correlated alarms of an alarm whose Correlated Notification Flag is set to NO causes the action to abort, as displayed on the Report window that pops up in this case. N.B. Note that when a duplicate alarm (see the Glossary for definition) raising notification is received, alarms attributes that have changed are updated with their most recent received value and the repetition counter which is displayed in the Identity page of the More Alarm Info window of the alarm is incremented.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 65 / 124

3.10 Getting reports on performed actions

After an action has been launched on your request, it may be useful to visualize a report offering detailed information about the progress or achievement (successful or not) of this action. For example, you may try to manually purge alarms whereas some of these alarms have been previously reserved by another operator. The operation will succeed for some alarms and fail for others. This kind of cases is reported by the AS. 3.10.1 Visualizing the actions report To get the report about an action, select the Report... option from the Option pull down menu in the Counter Summary window, as shown on Figure 53.

Figure 53. Visualizing report information A window opens up, displaying the list of successive actions and their status report (Figure 54. ). Let us consider an illustrative example. If you try to acknowledge alarms while some of them are being manually purged by another operator working on another USM and some else have been previously reserved by another operator, the report window will offer you the following information (see Figure 54. ). In a same way, several explicit Report Detail messages have been predefined to explain request failures or half successes. Status Column

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 54. Report window An abort case

ED

02 957.130.722 A 3AL 71109 AAAA 124 66 / 124

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

The first column of the Report List displays the date and time the action was sent. The second one displays the type of action that is reported. The different types are as follows :
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Get Alarm List Attributes Get All Alarms Get More Alarm Info Get Correlated Alarms Set Alarm List Attributes Set User Note Reserve Alarms Unreserve Alarms Acknowledge Alarms Create Trouble Ticket Manually Purge Alarms Synchronize Application

The last one displays the status of the operation. Five different statuses are managed. They are mapped to the colours of the default severity levels: In Progress (Indeterminate severity level colour) : request is ongoing. Aborted (Minor severity level colour) : request hasnt been sent. Failure (Critical severity level colour) : request failed. Success (Cleared severity level colour) : request succeeded. Half Success (Major severity level colour) : request partially succeeded. In this case, read the report details in order to find out what failed in the request.

In the lower part of the window, a Report Detail zone may provide additional information on the action selected in the list. In the figure above, an abort case is presented : trying to visualize correlated alarms of a decorrelated alarm has caused the action to abort. N.B. The Report window is actualized each time an action is initiated. The new action is inserted at the top of the list. The Report window automatically opens up each time an action request result is Aborted or Failure in order to allow you to get details on the failed action.

N.B.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 67 / 124

3.10.2 Clearing the whole report list You can clear the whole report list, reinitializing it in the mean time. Clearing the report list will cause all terminated actions displayed in the Report List to disappear, keeping the actions in progress. To clear the Report List, select the Clear option from the Report menu bar of the Report window, as shown on the following figure:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Figure 55. Clearing the whole report window

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 68 / 124

3.10.3 Deleting reports for some selected actions Clearing the whole report window, as presented in the previous section, may be sometimes an inadequate solution. You can also delete a single or some report items after having selected them. The reports must correspond to terminated actions. To delete some report items, select first the corresponding lines with the left mouse button. Then select the Delete... option from the Report pull down menu of the Report window, as shown on the following figure :

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

Figure 56. Deleting the report of a selected action

3.10.4 Configuring the Report window The Report window offers some different display options available from the Display pull down menu (see Figure 57. ) .

Figure 57. Display options for Report window The All Attributes option recovers the attributes columns you may have previously removed by double clicking on their titles. The Report window may be configured so as to be systematically brought on top when an action is performed. You can thus control the progress and the result of this action. To do so, check on the AutoRaise option.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 69 / 124

3.11 NE Symbols management

The alarm sublist displays global alarm information related to NEs. Depending on a configuration file, the application enables the operator to visualize a synthesis of alarm information for each NE : A submap, which contains NEs symbols, is created automatically as a start up window for current alarms management. The submap creation is optional and depends on a configuration file. For each NE symbol, the application allows to display the corresponding alarm synthesis information. Basically, the submap window creation is allowed by integrating the PNM application with the AS one, throught H.P Open View Window.

An example of a submap containing NE symbols and their related alarm synthesis information, is displayed in Figure 58. .

Figure 58. Submap window example. NEs symbols in the submap can either be explodable or executable. Explodable symbols : they are parent symbols. They generate child submaps containing other symbols when you double click on them. Executable symbols : they are associated to actions which can be performed on the symbols.

All the submap functionalities are available from PNM application, and are described into the document [10]

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 70 / 124

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

3.11.1 Alarm information For each NE symbol present within an opened submap, the application allows to display the corresponding alarm synthesis information : a flashing symbol when NE resources are impacted by incoming alarms, the total and unacknowledged active alarm counters, the most severe alarms.

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

The management of the alarm information follows the following principles : The display of Alarm Counter information related to each Symbol contained in a displayed Submap is ensured by the Alert symbol (see Figure 59. ). The flashing of displayed NE Symbol impacted by incoming alarm(s) present in one or several sublists defined by operators.

3.11.1.1 Alert Symbol management The Alert Symbol is calculated for Symbols associated with a single object of type NE which has one FDN. An example of Alert symbol, associated with a NE symbol, is displayed in Figure 59. .

Highest severity Number

Lower severity existence character Total number of alarms [ Number of Unack. Active Alarms]

Figure 59. Alert Symbol view. N.B. A NE symbol can not be deleted or moved to another submap, by an Ovw operation, while it supports an Alert Symbol. On the other hand the PNM action Remove ME is possible.

The Alert Symbol indicates the total number of alarms, the number of unacknowledged active alarms and also the highest severity among total and unacknowledged active alarms indicated by a character (see Figure 59. ). Available character are : C : critical, M : major, m : minor, W : warning, I: indeterminate.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 71 / 124

The + character, that is located next to the highest severity character (see Figure 59. ), means it exists others alarms of lower severity for this NE.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

This displayed information is updated automatically on reception of incoming alarms. Alarm counters and maximum severity are computed independently for each NE. The Alert Symbol management can be enabled/disabled by offline configuration of AS. N.B. The AS does not impact the Alarm Status information related to each NE managed by PNM.

3.11.1.2 Flashing symbol management. For each alarm present in the C.A.L., the AS application is capable to check whether a displayed Symbol is impacted by this alarm. If this is the case, AS triggers the flashing of this Symbol. the Symbol flashing functionality is supported for Symbols representing NEs. The Symbol flashing is disabled once no unacknowledged active alarm present in configured Sublists impacts the object resource(s) represented by the Symbol. The flashing state of the NEs is transmitted through submap navigation. The operator can request to stop the flashing of Symbol by just selecting them. The Flashing Symbol functionality can be enabled/disabled by offline configuration of AS.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 72 / 124

3.11.2 Most severe/Most recent Non cleared alarms management The application allows the management of a Most severe/Most recent Non cleared alarms sublist. When submaps feature is enabled, each opened submap has an associated Most severe/Most recent Non cleared sublist. This sublist type includes the common Sublist characteristics (see section 3.3 ). When the submap is closed, the corresponding Most severe/Most recent Non cleared alarms sublist is closed automatically. This feature is also accessible from a list of source, by AS navigation (see section 6. ). N.B. when you modify the predefined name of a Most severe/Most recent Non cleared alarms sublist, this one is deconnected from the PNM application. To again connect to PNM application, the operator has to close the current submap, then to open a new one.

1AA 00014 0004 (9007) A4 ALICE 04.10

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

ED

02 957.130.722 A 3AL 71109 AAAA 124 73 / 124

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02

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

3AL 71109 AAAA

124

74 / 124

4 ADMINISTERING ALARM SURVEILLANCE 4.1 Overview

The operator may customize the alarm surveillance performed by the application. To do so, select the Administration... option from the Option pull down menu (in the Counter Summary window), then select the IM that is source of the alarms. The following window opens.

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

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 60. Administration window for alarm surveillance configuration As shown on the Figure 60. , Administration window presents five different pages (panels), each one offering some parameters. The different pages are :

ED

02 957.130.722 A 3AL 71109 AAAA 124 75 / 124

Figure 61. Failure report Archiving Filter : Alarms which are removed from the C.A.L. (whatever the reason) are tested against this filter. If matching it, they are archived in the Historical Alarms List (H.A.L.) and they can be retrieved from it using the AS historical part commands and operations. N.B. The default configuration of this filter is match all. That causes every alarm removed from the C.A.L. to be effectively archived (i.e. placed in the H.A.L.).

AutoPurge : Automatic purging allows to automatically redirect some incoming alarms to the H.A.L. Thus, such alarms will never appear in the C.A.L, avoiding by this mean their creation in the C.A.L. N.B. The default configuration of this filter is match none. That causes every incoming alarm to enter the C.A.L., without any bypassing.

1AA 00014 0004 (9007) A4 ALICE 04.10

AutoTT : Similarly to automatic purging, trouble ticket requests can be automatically generated for some alarms and sent to the third party product ARS. N.B. The default configuration of this filter is match none. That means that an incoming alarm never triggers the automatic creation of a trouble ticket.

ED

02 957.130.722 A 3AL 71109 AAAA 124 76 / 124

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

C.A.L. Administration : You can set the size of the Current Alarms List (C.A.L.), customize parameters relating to an overflow case, visualize the current filling status of the C.A.L.. Note that the maximum C.A.L. size should not exceed 10000 alarms. If you try to specify a maximum C.A.L. size greater than this value, a report window opens up pointing out the request failure and giving you some useful indications (see Figure 61. ).

AutoAck : Automatic acknowledgement is useful when the AS Operator wants to avoid manual acknowledgement of some incoming alarms. N.B. The default configuration of this filter is match none, which means that an incoming alarm is never automatically acknowledged.

1AA 00014 0004 (9007) A4 ALICE 04.10

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

ED

02 957.130.722 A 3AL 71109 AAAA 124 77 / 124

4.2 Administering the C.A.L.

4.2.1 C.A.L Size Control Settings The Current Alarm List (and as a consequence, every sublist) can only contain a limited number of alarm instances. You can define this maximum size, this configuration value being itself limited to a maximum value of 10000 current alarms. A Warning Filling Percentage of the list is also defined. It corresponds to a percentage ratio between the present size (number of alarms) and the maximum size. A CAL status is computed from those parameters : From emptyness (0 alarm) to the Warning Filling Percentage, the status of the list is valued to normal. From the Warning Filling Percentage to the maximum size, the status is valued to warning. When the number of alarms reaches the maximum value, the status is valued to overflow.

Operators are instantaneously informed of changes of the C.A.L. status, through the realtime update of the information in the bottomright corner of the Counter Summary window. Operators can select the C.A.L. Overflow Action Mode through a drop down list. This parameter is activated once the C.A.L. Maximum Size is reached (and only then). Two modes exist. They are : Wrap : on an alarm creation request, a certain number of alarms, defined by the Overflow Purge Size parameter, are purged (selection is operated according to the Purging Sort criteria mentioned below) to allow the insertion of the new alarm into the list. This is the default mode. Halt : the request concerning the creation of a new alarm is discarded (consequently, the alarm is not created in the C.A.L.). In this case, no overflow purge occurs.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 78 / 124

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

4.2.2 Setting the Overflow parameters The Overflow parameter zone is shown on the Figure 62. :
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Figure 62. C.A.L. Administration Overflow Parameter zone To set the maximum number of alarms of the C.A.L., click on the edit field of the C.A.L. Maximum Size item and fill it with the desired value. Operate in the same way for the Warning Filling Percentage and for Overflow Purge Size. To set the Overflow Action Mode (see above for definition), select the desired mode after having dropped down the list.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 79 / 124

4.2.3 Setting the Purging Sort Criteria Alarms to be removed from the Current Alarm List as overflow occurs (in Wrap mode) can be selected according to specified criteria. For example, you may want alarms of the less high severity levels to be removed first. This can be done configuring the Purging Sort Criteria zone :

Figure 63. C.A.L. Administration Purging Criteria zone This zone includes two lists: one for the attributes which do not play a part in the selection process, one for the attributes which play such a role.

You can move one or several attributes from a list to the other one by selecting the desired items and then using the arrow buttons (right and left). Refer to 2.3.1 General conventions and kinds of widgets. In the second list (Selected criteria), the order of items represents the order the corresponding attributes are considered in the determination of the alarms to be kept or removed. Note that the alarms to be removed are not the first but the last appearing in the built list. You can check the effects of the sort by applying exactly the same criterions for displaying the contents of the Main Alarm List. The candidates to the purge appear at the bottom of the table. For each attribute of the right list, you can also specify the order the values taken by this attribute are considered (ascending or descending order). The current direction is indicated by the option button on the right of the attribute name. To invert this order, click on this button. Its label then changes (Incr or Decr). N.B. For boolean attributes such as Reserve Status, the set value (e.g. Reserved) is assimilated to 1, the unset value (e.g. Unreserved) to 0, which allows defining an ascending or descending order.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 80 / 124

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

4.2.4 The Statistics Zone This zone is a readonly zone, which informs you of the current state of the C.A.L. :
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Figure 64. C.A.L. Administration Statistics zone Four pieces of information are given. Three of them evolve on a regular basis. These are : The C.A.L. Size which gives the current number of alarms contained in the C.A.L.. It corresponds to the displayed total number of alarms in the Main Alarm List in the Counter Summary window. The C.A.L. Filling Percentage which gives the present filling state of the C.A.L. with respect to the C.A.L. Maximum Size. The C.A.L. Status which is related to the C.A.L. Filling Percentage (see the beginning of this chapter 4.2 Administering the C.A.L.).

Note the presence in this zone of the ARS Connection Status field (ARS being the third party application for trouble ticket management) to indicate whether this application is interfaced or not with AS.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 81 / 124

4.3 Customizing the Archiving Filter

When alarms are removed from the C.A.L. (whatever the mean), they are tested against the archiving filter. If matching this filter, alarms are put in the H.A.L.. They may then be retrieved from there using the AS historical part. Alarms leaving the C.A.L. and not matching the archiving are discarded. In particular, this means that setting a match none archiving filter (i.e. a filter that no alarm could match) would cause purged alarms to be irremediably lost. refer to section 4.1 Overview. The default configuration of this filter is match all. That causes every alarm removed from the C.A.L. to be effectively archived (i.e. placed in the H.A.L.). The archiving filter is defined through a panel composed of several groups, each of them, at the exception of the dictionary group at the top, corresponding to a specific attribute or group of attributes. The global condition defining the filter is built by applying an AND operator between the elementary conditions defined by the groups. When, inside a group, a list offers multiple selection for an attribute, the condition on this attribute results from an OR on the different selected values.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 65. Administration Archiving filter Panel

ED

02 957.130.722 A 3AL 71109 AAAA 124 82 / 124

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

The way of operation within this panel is exactly the same as in the Filter panel for the definition or modification of a Current Alarms sublist. Refer to section 3.3.2 Modifying a sublist Modifying the sublist filter for a detailed presentation of the management of each group within the panel.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 83 / 124

4.4 Purging alarms automatically

Automatic purging allows to automatically redirect some incoming alarms to the H.A.L. (see section 4.1 Overview), avoiding by this mean their creation in the C.A.L. The default configuration of this filter is match none. That causes every incoming alarm to enter the C.A.L., without any bypassing. As for the Archiving Filter, the way of operation within this panel is exactly the same as in the Filter panel for the definition or modification of a Current Alarms sublist. Refer to section 3.3.2 Modifying a sublist Modifying the sublist filter for a detailed presentation of the management of each group within the panel. However, in this AutoPurge filter panel (and also in the two other analogous panels, for AutoTrouble Ticket and AutoAcknowledgement filtering), the Status zone is greyed, and so its elements cannot be accessed. AS does not support automatic operations on alarms according to these statuses. N.B. As already pointed, all alarms removed from the C.A.L. are submitted to the archiving filter before being put in the H.A.L..

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 84 / 124

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

4.5 Autocreating trouble tickets

The access to this panel is enabled although the AS application is not interfaced with the third party product ARS. But in such a case its configuration is not operational. If the interface is installed, trouble ticket requests can be automatically generated for some alarms and sent to ARS. The default configuration of this filter is match none. That means that an incoming alarm never triggers the automatic creation of a trouble ticket. As for the Archiving Filter, the way of operation within this panel is exactly the same as in the Filter panel for the definition or modification of a Current Alarms sublist. Refer to section 3.3.2 Modifying a sublist Modifying the sublist filter for a detailed presentation of the management of each group within the panel.

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

4.6 Autoacknowledging alarms

Automatic acknowledgment is useful when you want systematic acknowlegement of some alarms, on their incoming, but you prefer to avoid manual acknowledgement . The default configuration of this filter is match none, which means that an incoming alarm is never automatically acknowledged. As for the Archiving Filter, the way of operation within this panel is exactly the same as in the Filter panel for the definition or modification of a Current Alarms sublist. Refer to section 3.3.2 Modifying a sublist Modifying the sublist filter for a detailed presentation of the management of each group within the panel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 85 / 124

4.7 Resynchronizing AS
The Current Alarms Main List displays the alarms emitted within the system. It is real time refreshed. Except the case of automatic purging, an alarm received by the AS is immediately displayed on your screen. Furthermore, because the C.A.L. may happen to become inconsistent with the actual situation of the network, you can explicitely initiate the resynchronization of information concerning current alarms. The application enables the operator to request synchronization with local or external agents, depending on the configuration file. To do so, select the Synchronization... option from the Option pull down menu in the Counter Summary window. Then, select the chosen agent (local or external) from the cascading menu, as shown on the following figure :

Figure 66. Resynchronizing the AS The following confirmation box appears :

Figure 67. Confirmation box.

Press Yes to perform the synchronisation, press No otherwise. During synchronization phase, the following information box opens :

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 86 / 124

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

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

Figure 68. Message box.

Alarms which were present in the C.A.L., and which are not confirmed by the synchronization (i.e. that do not exist anymore from the AS point of view) are automatically cleared by the AS application. Thus, alarms that were previously acknowledged are forwarded to the H.A.L. if matching the archiving filter.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 87 / 124

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02

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

3AL 71109 AAAA

124

88 / 124

5 MANAGING HISTORICAL ALARMS 5.1 Introduction and capabilities

AS historical part allows to display archived alarms and to perform actions on them. AS internally manages an archiving space called the Historical Alarm List containing former current alarms that have been archived through one of the following processes (at the additional condition they were matching the archiving filter): autopurging : such alarms have never been raised up to the C.A.L. manual purging : an AS operator has manually removed one or more selected alarms from the C.A.L.. overflow : an AS operator can set overflow configuration (i.e. a maximum size of the C.A.L., an overflow mode, an Overflow Purge Size and Purging Sort Criteria). Refer to section 4.2 Administering the C.A.L. for additional detail. acknowledging cleared alarms or clearing acknowledged alarms : when normal synchronisation occurs, all alarms which were acknowledged and which are not confirmed in the synchronisation. synchronization : alarms that are not confirmed on a synchronization command are automatically cleared by the application. Among them, those which were previously acknowledged are forwarded to the H.A.L. . AS IM modification : at start up, when an agent is no longer in the agents list, all alarms from this agent. Invalidation : alarms matching FDN, scope and class in case of invalidateAlarmList.

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

Specifying filters, you can extract alarms from this archiving space to visualize and process them. The H.A.L. is stored using a specific adhoc format, referenced below as the Public Archive format. This repository receives all alarms matching through the Archiving filter. In addition, in standard configuration, these alarms are stored in parallel using HP OpenView facilities, in a HPLog repository. The contents of these repositories, as a list of alarms, are usually identical over a short time period. The two repositories can be seen as a redundancy method to improve the disponibility of the archiving and retrieval functions of the AS application. However, the HPLog can be configured (using navigation to the EFD and Log Management application ELM ) [5]. Its characteristics, such as its size, its overflow mode, its input filter, can then be modified. In that case, the content of the HPLOG may be only a subset of the content of the Public Archive. You can retrieve archived alarms from both repositories. Moreover, the application allows to retrieve archived alarms from several Public Archive (local and external). Using a filter, called the Main (historical) Filter, you build a list of alarms corresponding to the subset of archived alarms you are interested in. This subset constitutes the Main (historical) Alarm List. In addition, you can store a set of alarms (built by selection in the Main List or in any sublist) into an user defined file. You will then be able to retrieve alarms from such a file instead of the HPLog or Public Archive, or in conjunction with this source. As for current alarms, sublists can be created to provide limited views on this Main List by defining secondary filters. Thus, when you initiate a retrieval, all existing sublists are affected. Their definition itself (as a combination of conditions) is kept, but their content (as a list of alarms) is removed and will be totally regenerated. For this reason, a confirmation is asked before proceeding.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 89 / 124

Handling of sublists and general management of alarms within the sublists (or within the Main List) are performed according to the same methods as in the Current Alarms Case. Specific actions on current alarms such as reservation, clearing... are not available because they are meaningless in historical case, but obtention of detailed information or exportation are operated exactly in the same way. Figure 69. presents these different retrieval and storage capabilities.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Figure 69. The different alarm archives

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 90 / 124

5.2 Historical alarms management start up

On start up of AS historical part, the Counter Summary window opens up :
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Figure 70. AS historical part start up : Counter Summary window The Counter Summary window, as in the C.A.L. case, presents global information made up of severity level counters about the different existing sublists. Before any action, this window only displays two empty lists, the main and the default one. To initiate your work session, you have to: build a Main (historical) Alarm List by specifying one or several (by successive elementary operations) archive sources and configuring the filter to be applied for retrieval, create or adapt sublists according to your needs.

The retrieval operations are described in next section (5.3 Retrieving archived alarms). The configuration of filters is presented in section 5.4 Filtering archived alarms. The creation and modification of sublists are operated as in the Current Alarms case. Refer to the relevant sections (especially 3.2 Creating a sublist, 3.3 Modifying a sublist, 3.4 Visualizing (opening) a sublist, 3.5 Deleting a sublist) for additional information. However, note that slight differences exist concerning the activating/deactivating features of the Current Alarms sublists. As historical sublists are made of statical retrieved information (where as current sublists contain realtime updated information), the terms of activating or deactivating have no meaning. Consequently, they are replaced in the Sublist pull down menu in the Historical Alarms case by the enable/disable terms. The following figure represents the Sublist pull down menu of the Historical Counter Summary window :

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 91 / 124

Figure 71. historical Sublist pull down menu From a strictly visual point of view, enabling or disabling the counter of a historical sublist respectively has the same effect as activating or deactivating a current sublist (that is the counter of a disabled historical sublist appears as x). Moreover, since filters for archived alarms are slightly different from filters concerning current alarms, when considering to adapt the filter of a historical sublist, you can directly refer to the abovementioned section 5.4 Filtering archived alarms. Secondary historical filters present exactly the same characteristics as the Main Filter used for retrieval from the archive. Concerning general operations on alarms within sublists, which are also performed by the same methods as in the Current Alarms case, refer if necessary to 3.6 Selecting alarms within a sublist window, 3.7 Exporting contents from a sublist, 3.8 Visualizing full alarm information.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 92 / 124

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

5.3 Retrieving archived alarms

You can retrieve alarms either from the HPLog, from a set of user files, or from one or several Public Archives (local and externals). Public Archive is a storage database containing a set of alarm information, and is managed by the AS Current IM. You can also build a Main (historical) Alarm list from a combination of these different sources. A retrieval operation can be analyzed as the succession of several phases: selecting a single source among the three possibilities offered. In the Public Archive case, the operator may select the local one (the Alarm Source attribute displays the archive file in which the alarm has been retrieved) or one of the external ones (the Alarm Source attributes displays the name of the IM that is the alarm source), depending on the configuration file, defining the filter to be applied to this source, deciding whether the set of alarms resulting from the retrieval will overwrite the current content of the Main List or will be appended to it, retrieving the alarms from the source, with the possibility to stop the process at any moment.

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

By performing several successive retrieval operations and using the append option, you can build a Main List containing alarms of various origins. Duplicated alarms (i.e. alarms retrieved from a source but already loaded from another) are discarded to keep a single instance. Note also that you can apply different types of filters or variants on the different sources. To choose the archive source, open the Archive pull down menu in the Counter Summary window (figure below).

Figure 72. Selecting a source of archived alarms When selecting Retrieve from Log..., the Main Filter window immediately opens. When selecting Retrieve from Public Archive..., a cascading menu appears, displaying all the Public Archive you may access (local and externals). Select one Public Archive, the Main Filter window then opens.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 93 / 124

In this Main Filter panel, define the conditions you want to apply. A full description of the panel organization and of the operation in the various groups takes place in the next section (5.4 Filtering archived alarms). Refer to it if necessary. Clicking on the Apply button of the Main Filter panel allows to enter the next step of the process. Now, decide if you want to overwrite the current content of the Main List or to keep it and append the alarms to be retrieved. To append the retrieved alarms to the Main List, press Yes in the window which has opened (Figure 73. ). To overwrite its contents, press No. To give up the retrieval operation, press Cancel.

Figure 73. Retrieval operation Appending or overwriting Whatever your choice in this window (excepting Cancel), another confirmation window opens (Figure 74. corresponds to the overwrite case. The message differs in the append case). Performing the retrieval causes a global change of the contents of all the sublists, since the sublists correspond to limited views of the Main List, whose content is to be revised. Press OK to go on. The sublists are closed if previously opened, and made empty, but their characteristics (especially the related filter) are kept. To regenerate their content, you will simply have to open them again. Otherwise, press Cancel to give up the retrieval operation and keep the Main List and the sublists unchanged.

Figure 74. Retrieval operation Confirming the reinitialization of sublists. Confirming by pressing OK initiates the retrieval from the selected source. You will continuously be informed of the progress of the retrieval operation by the updated counters of the Counter Summary window and by the following Filling Percentage window :

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 94 / 124

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

When selecting Retrieve from User Files..., another window opens first, allowing you to define a subset of the user files to be used for the retrieval operation. For additional information, this window is described in section 5.5.2 Retrieving alarms from a set of user files. When you have chosen this set of files, press Apply in this window. The Main Filter window then opens.

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

Figure 75. Retrieval operation Progress window If desired, the retrieval operation can be stopped at any moment by clicking on the Stop button. The following confirmation window pops up :

Figure 76. Interrupting the historical alarm retrieval In case of confirmation, the actual stopping may take some time. In any case, the alarms already retrieved are displayed in the list. The retrieval operation may failed (time out exceeded). The following window then pops up :

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 77. Error message box.

ED

02 957.130.722 A 3AL 71109 AAAA 124 95 / 124

Two messages may be displayed depending on the error source : The first message means the Log Agent (ovlad) is not reachable. The second one means no response has been reported since a lapse of time, defined in the configuration file (parameter GET_TIMEOUT from param.cfg file).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 96 / 124

5.4 Filtering archived alarms

5.4.1 Accessing the Filter panel For Historical Alarms Management, the Filter page of the Sublist Properties window has the following aspect :

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

Figure 78. Sublist Properties Filter Panel (Historical Alarms case) In addition to its usage for the definition of the filters associated to sublists, this panel is also used to define the Main Filter applied during a retrieval operation. In that case, it is loaded after the selection of the source.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 97 / 124

5.4.2 Using the different groups of the panel The filter is defined through a panel composed of several groups, each of them, at the exception of the dictionary group at the top, corresponding to a specific attribute or group of attributes and being enclosed in a specific page (Basic, Source or Extended filter page). The global condition defining the filter is built by applying an AND operator between the elementary conditions defined by the groups. When, inside a group, a list offers multiple selection for an attribute, the condition on this attribute results from an OR on the different selected values. To activate or deactivate one of the groups (e.g. Severity or Alarm Type), you have to click the check button of the zone (black color means that the area has been activated). The following paragraphs detail the operations for the different groups. 5.4.2.1 Using the Filters Dictionary The filters dictionary group is placed in the upper zone of the Filter panel :

Matching status of the filter

The dictionary provides a list of filters previously prepared and available to ease your work. In this dictionary, filters can be created, modified or removed according to your choice. Clicking on the button shows the drop down list containing the existing filter names. Clicking on one of them selects it and loads the various elementary criterions in the different other fields of the panel.. The matching status zone indicates if alarms could match this filter. One of the following three statuses may appear : Match none : no alarm could match the filter. In this case, there may be conflicting options specified in the filter. Match some : alarms may match the filter. Match all : all alarms will match the filter. This means in particular that a sublist characterized by this type of filter will extract all alarms of the main list (in the current and historical case).

To create a new filter in the dictionary, fill the edit zone with any authorized name. Authorized names are names containing letters (case independent), numbers, and the three , _, and . characters. Size of a name should not exceed 32 characters. Clicking on the Save button will take into account every element of the Filter Panel. So this must be done after having performed the modifications on the other elements of the page.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 98 / 124

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

5.4.2.2 Selecting alarms according to a Date and Time (basic filter page) The AS application gives the possibility to select alarms according to the date and time of their raising event. To do this, select first the Basic page by clicking on the corresponding tab.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

You can specify a list of intervals for date and time. An alarm will be selected if the raising event took place in one of the intervals. In the filter panel, the Event Date & Time Ranges zone presents in a readonly box the list of the intervals already defined.

Figure 79. Sublist filter Event Date & Time group. To add some intervals or to adapt this list, press the Select... button. Another dialogue box opens, presented in Figure 80.

Figure 80. Sublist filter Edition of the list of time intervals. As in all other relevant places of the application, times have to be expressed using local definition, not GMT. Specify an interval (beginning and end) with the text boxes, respecting the proposed format, or adapt it with the spin buttons, after selecting the desired subpart (month, day, year, hours, minutes, seconds) by clicking on the right position inside a box.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 99 / 124

Add it to the list of intervals, displayed on the right part of the dialogue box, by pressing the rightarrow button. Reciprocally, you can suppress an existing time interval from this list by selecting it and then pressing the leftarrow button. To modify an interval, proceed in two steps (deletion and addition): Select it in the right list and press the leftarrow button. It disappears from the list (deletion), but its definition is moved to the edition area on the left. Adapt this definition according to your needs and press the rightarrow button. The new interval is inserted in the list.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Press Ok to come back to the Sublist Properties (Filter panel) window. In historical case, alarms can also be filtered according to their Archiving Date and Time, i.e. the moment they have entered the archive. This time can be significantly different from the raising event time and, for this reason, is available as a separate data. The way of operation is exactly similar. The corresponding group is placed at the right of the previous one within the panel. 5.4.2.3 Selecting alarms according to their severity level or type (basic filter page) Alarms can also be filtered according to their severity level or their alarm type.

Figure 81. Sublist filter Severity level and Alarm Type groups. For each group, the test can be operated against several values, offering an OR boolean operator through multple selection in the list. Select first the Basic page by clicking on the corresponding tab and then click on the check buttons Severity or Alarm Type to activate the respective zones if necessary. Then, select the desired fields with the mouse left button. Reciprocally, click also on the check buttons to deactivate the zones if they are already activated and you want to remove the corresponding condition from the filter.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 100 / 124

5.4.2.4 Selecting alarms according to their probable cause (basic filter page) Another attribute that may be used for filtering is the probable cause of the alarm. Exactly as for severity or type, several values can be selected to define an OR combination. However, the dialogue is different.

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

Figure 82. Sublist filter Probable cause group. The list presented at this panel level is readonly and displays the causes already selected (in previous operations). It is initially empty. Refer to section 3.3.2.5 Selecting alarms according to their probable cause (basic filter page). To select alarms according to their probable cause, select first the Basic page by clicking on the corresponding tab, then click on the check button to activate the zone and press the Select... button. A new window opens up in which the operator can adapt the list of selected probable causes.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 83. Sublist filter Selection of probable causes.

ED

02 957.130.722 A 3AL 71109 AAAA 124 101 / 124

The window includes two lists: one for the causes to be rejected, one for the causes to be taken into account.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

You can move one or several elements from a list to the other one by selecting the desired items and then using the arrow buttons (left and right). Refer to 2.3.1 General conventions and kinds of widgets. At the end of the operation, press Ok. This window closes and the list at the panel level is updated. 5.4.2.5 Selecting alarms according to their insertion cause (basic filter page) In the Historical Alarms case, you can extract alarms from the Main Alarm List according to their insertion cause, i.e. the way the alarm has entered the historical list.

Figure 84. Sublist filter Insertion Cause group This can be done by selecting the desired option in the Insertion Cause zone. To select the desired alarms, select first the Basic page by clicking on the corresponding tab, then click with the left mouse button on the radio button to activate the zone if it is not. Then click on the list zone in order to drop it down and select the alarm kind to be extracted. The list contains the five following items : autopurging : such alarms have never been raised up to the C.A.L. manual purging : an AS operator has manually removed one or more selected alarms from the C.A.L.. overflow : an AS operator can set overflow configuration (i.e. a maximum size of the C.A.L., an overflow mode, an Overflow Purge Size and Purging Sort Criteria). Refer to section 4.2 Administering the C.A.L. for additional detail. acknowledging cleared alarms or clearing acknowledged alarms : when normal synchronisation occurs, all alarms which were acknowledged and which are not confirmed in the synchronisation. synchronization : alarms that are not confirmed on a synchronization command are automatically cleared by the application. Among them, those which were previously acknowledged are forwarded to the H.A.L. . AS IM modification : at start up, when an agent is no longer in the agents list, all alarms from this agent. Invalidation : alarms matching FDN, scope and class in case of invalidateAlarmList.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 102 / 124

5.4.2.6 Selecting alarms according to their Object and Scope Attribute (source filter page) You are also given the possibility to extract alarms considering their MO class, MO Instance or Friendly Name (NE).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

To add a test on such an attribute, select first the Source filter page by clicking on the relevant tab. Click if necessary on the Instance check button to activate the zone.

Figure 85. Sublist filter Source filter page Concerning MO Instance, you can specify the kind of test to be performed using the option button on the left, which presents the following options : Base : to only consider the object specified by the instance, Subtree : to also include in the search all the objects contained in the specified object.

Similarly, concerning Friendly Name, you can also specify the nature of the test using the same option button, which presents a modified list of options once you have clicked on the Friendly Name check button : Equal : sefunderstanding, Substring : the actual friendly name must contain the specified string, Begin with: the actual friendly name must begin by the specified string, End with: the actual friendly name must end by the specified string.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 103 / 124

Enter the desired value in the lower edit field and then click on the Add button. Your value should appear now in the right readonly zone.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

If you want to modify an existing value appearing in this readonly list, select it first by clicking on with the left mouse button. This causes the left zone to be put in conformity with the selected element (that is, one of the Friendly Name or MO Instance check buttons is checked, the option button points to the option in accordance with the selected element and the edit field is also updated). Bring any modifications you want in this zone and valid them by clicking on the Modify push button (note that this button remains disabled as long as no element or more than one have been selected in the right list box). Multiple selection is available in the right list box to allow removing action (using the Remove button). To do this, select one or more elements in the right list box and click on the initially disabled Remove button. To retrieve valid values for MO Class, MO Instance and Friendly Name, you can make use of the More Info window. This window can be called from any opened sublist window after selection of an alarm in the table. The three attributes are displayed in the Identity panel.

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

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 104 / 124

5.4.2.7 Selecting alarms according to their MO Class (source filter page) To add such tests, select first the Source filter page by clicking on the relevant tab. Click if necessary on the MO Class check button to activate the zone (see Figure 85. ). This zone includes two lists: one (Unselected MO Class) for the MO Classes which will not be involved in the extraction process, one (Selected MO Class) for the MO Classes participating to this process.

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

You can move one or several elements from a list to the other one 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 element to the selection, press the Ctrl key simultaneously with the mouse click. To unselect an already selected element, use again in the same way this Ctrl key. 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.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 105 / 124

5.4.2.8 Selecting alarms according to their additional info (extended filter page) In AS you are given the possibility to extract alarms considering their additional info attribute values. To do this, select first the Extended filter page by clicking on the relevant tab (see Figure 87. ). Check the Additional Info check button to activate the zone if necessary.

Figure 87. Extended filter page The Extended filter is defined through a zone composed of numerotated Additional Info check button, each of them being associated with an option button, which specifies the nature of the test, and an edit field. The option buttons and edit fields are activated once the relevant Additional Info check button has been checked. One test is defined by an operator AND applied between the conditions specified at the level of each activated Additional Info check button. Fill the desired fields.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 106 / 124

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

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

Then, to add your test involving additional info attributes to the existing ones (if any), click on the Add button situated below this zone. As a result of this, the test appears (in an explicit form showing the elementary expressions and the logical operator AND applied between them) in the readonly zone situated at the bottom of the page. The extended filter results in an OR operator applied between the different existing tests. If you want to modify an existing test (i.e. appearing in the readonly zone), select it first in this zone by clicking on it. The upper zone of the page is updated according to the content of the test. Modify your test and then click on the Modify button. The test is updated. In a same way, removing an exising test is done by first selecting the test and then clicking on the Remove button. the removed test disappears from the list. Note that multiple selection is available in the existing tests list. In this case, the additional info check boxes zone relates to the last selected test, but the Modify button is not active.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 107 / 124

5.5 Managing User Files

5.5.1 Saving a set of alarms to an user file You can store into an user file a set of alarms displayed in any of the sublists (or in the Main List). To do so, from such a sublist window, select first the desired alarms. Then select the Save As... option from the Action pull down menu.

Figure 88. Saving historical alarms to an user file A window then opens (Figure 89. ), which allows to specify a file name.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 108 / 124

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

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

Ok

Figure 89. Historical user file Specification of the file name The directory where the file will be stored has been configured by the administrator. According to this configuration, it may be common to the different operators, to some of them, or specific to each of them. As a result, you cannot control this directory location. Simply select from the list one of the existing files to overwrite it, or type a new name in the entry box at the bottom to create a new file. Authorized names are names containing letters (case independent), numbers, and the three , _, and . characters. Size of a name should not exceed 32 characters. Press Ok. During the storage process, a progress window is displayed.

Stop

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 90. Historical user file Storage progress window

ED

02 957.130.722 A 3AL 71109 AAAA 124 109 / 124

At any moment, you can interrupt the process by pressing the Stop button. Already treated alarms are kept in the file, but remaining ones are ignored. 5.5.2 Retrieving alarms from a set of user files From the Counter Summary window, select the Retrieve from User Files... option from the Archive pull down menu. The following window opens:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Ok

Figure 91. Historical user files Selection of files The window includes two lists: one for the excluded files, not to be used for retrieval, one for the included files, to be used for the retrieval.

You can move one or several attributes from a list to the other one by selecting the desired items and then using the arrow buttons (left and right). Refer to section 2.3.1 General conventions and kind of widgets. Press then Ok. You enter the retrieval process itself, as described in section 5.3 Retrieving archived alarms, with first the definition of the filter to be used.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 110 / 124

5.5.3 Deleting a set of user files From the Counter Summary window, select the Remove User Files... option from the Archive pull down menu.

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

Figure 92. Deleting archive user files. The same file selection window as above opens (see Figure 91.). Operate in the same way. Press Ok to actually delete the chosen files.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 111 / 124

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02

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

3AL 71109 AAAA

124

112 / 124

6 NAVIGATION FEATURES
AS provides some navigation features in order to improve the handling of the application.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Navigation options can be accessed via the Navigation pull down menu, which is present either in the Counter Summary window or in any sublist window.

Figure 93. Navigation pull down menu

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 113 / 124

6.1 Navigating within the AS application

6.1.1 Navigating through the sublists Once several sublists have been opened, it may be useful to navigate through the different windows. To navigate to a particular opened sublist, select the Sublists cascading menu from this Navigation pull down menu. Then select the sublist name among the proposed items (Figure 93. ) Note that only currentlyopened sublists (for the considered subset Current or Historical alarms of the application) are presented in this dynamic menu, and not the whole set of existing sublists. This menu also does not include (in Current Alarms management case) the windows obtained through the Correlated Alarms command.

Figure 94. Navigating to a opened sublist named NE_Nantes N.B. To access sublist that are not currently opened, select the Open option from the Sublist pull down menu.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 114 / 124

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

6.1.2 Navigating between the C.A.L. and the H.A.L. AS offers to navigate between the two Counter Summary windows (Current and Historical) using respectively the Archive... or Current... option of each Navigation pull down menu.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

As an example, from the Current Counter Summary window, access to the Historical Counter Summary window can be obtained as shown in the following figure :

Archive...

Figure 95. Accessing the Historical Counter Summary from the Current Counter Summary window N.B. In the previous example, if AS historical part is not running, the result of the request is the starting up of this part. If it is running, it is brought on top.

6.1.3 Navigating to the Counter Summary From an opened sublist window, either in current or historical case, you can return to the relevant Counter Summary window using the Summary option of the Navigation pull down menu.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 115 / 124

6.2 Navigating toward external applications

6.2.1 Navigating to the PNM application In Current Alarms Management context, if the Physical Network Management (PNM) application is installed on your workstation, you can benefit from its capabilities. You can visualize the Network Element which has emitted an alarm. To do so, from a sublist window (but not from the Counter Summary window) : select an alarm in the table, select the PNM option from the Navigation pull down menu.

A PNM window opens, displaying the submap the Network Element belongs to, and highlighting this Network Element within this submap. Reciprocally, when using the PNM application and selecting a Network Element, you can access the AS application to open a sublist containing the alarms emitted by this Network Element.

PNM...

Figure 96. Accessing PNM submap from a Current Alarms sublist

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 116 / 124

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

6.2.2 Navigating to the ELM application In Historical Alarms Management context, if the EFD and Log Management (ELM) application is installed on your workstation, you can benefit from its capabilities. You can thus configure the characteristics of the HPLog repository. To do so, from the (historical) Counter Summary window, select the ELM option from the Navigation pull down menu.

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

Figure 97. Calling the ELM application for HPLog configuration An ELM window opens, allowing the modification of the HPLog attributes. You can especially change the size of the log and its overflow mode, getting thus similar capabilities than those presented for Current Alarms List (C.A.L.) Administration. Refer to the ELM Users Guide if necessary. 6.2.3 Sending alarm information to an external application You may also be offered to navigate to an external application, according to your choice. This navigation feature has to be configured during the installation phase. To navigate to a particular external application, select the External Application cascading menu from the Navigation pull down menu. Then select an external application name among the proposed items. This operation allows to export information related to a single alarm and to treat this information in this external application (this treatment may be of any kind, but a spreadsheet application can be a typical example). Applying to a single selected alarm, this operation is not available from the Counter Summary window, but from any sublist window. In such a window, select first the alarm in the table and then select the option from the menu. N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10

In case of multiple alarms selection, only the first alarm is sent to the external application.

ED

02 957.130.722 A 3AL 71109 AAAA 124 117 / 124

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02

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

3AL 71109 AAAA

124

118 / 124

7 ABBREVIATIONS
ALMAP : Alcatel Management Platform
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

AS : Alarm Surveillance ARS : Action Request System (Trouble Ticket third party Product of Remedy) CAL : Current Alarm List ELM : EFD and Log Management GUI : Graphical User Interface HAL : Historical Alarm List HMI : Human Machine Interface MOC : Managed Object Class MOI : Managed Object Instance NE: Network Element PNM : Physical Network Management TMN: Telecommunications Management Network TN: Telecommunications Network TT : Trouble Ticket

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 119 / 124

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02

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

3AL 71109 AAAA

124

120 / 124

8 GLOSSARY OF TERMS
Acknowledgement : When an alarm is taken into account by the application, the operator has to acknowledge it to point out that he has seen it and that he will react in the right way. Acknowledgement Status : This attribute indicates whether the reported alarm has been acknowledged or not. Additional Information : optional attribute of an alarm wich consist in structured information that is used to define sublists characteristics. Additional text : This optional information allows a free form text description to be reported. Alarm : An alerting indication to a condition that may have an immediate or potentially negative impact on the state of a communication resource. An alarm is characterized by an alarm begin and an alarm end. Archiving Filter : Alarms which are removed from the C.A.L. (whatever the reason) are tested against this filter. If matching it, they are archived in the Historical Alarms List (H.A.L.) and they can be retrieved from it using the AS historical part commands and operations. Correlated Notification : This optional attribute indicates a link of an alarm to a set of other alarms identified by a Notification Identifier and their relative Object instance. Correlated Notification Flag (in the C.A.L. only) : This attribute is set to YES when a Correlated Notification is sent together with the reported alarm. Clearing Status : This attribute indicates whether the reported alarm has been cleared or not. Event Date & Time : This parameter gives the local date and time when the event alarm is the notification of has been detected. Event Type : This parameter categories the alarm. Five basic categories of alarm are specified. These are reported in the Alarms section. Filter : They are related to the alarms or events generated on an NE. They can be configured by an operator to reject specified types of notifications and limit the processing that is applied to them. Friendly name : Name of a managed entity. Human Machine Interface : It is the graphical user interface application through which the operators interact with the system.

1AA 00014 0004 (9007) A4 ALICE 04.10

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

ED

02 957.130.722 A 3AL 71109 AAAA 124 121 / 124

Logging Time (in the H.A.L. only) : This parameter gives the local time when the alarm was put in the H.A.L.. Managed Object Class : This attribute specifies the class of the managed object in which the event emitted by the agent occurred. Managed Object Instance : This attribute specifies the instance of the managed object in which the event emitted by the agent occurred. Monitored attributes : These attributes are monitored by AS and can contain one or more attributes belonging to the following set : alarm status: This attribute can have one of the following values: cleared, activeReportableindeterminate, activeReportableWarning, activeReportableMinor, activeReportableMajor, activeReportableCritical, activePending. availability status: This attribute can have zero or more of the following values: In test, Failed, Power off, Off line, Off duty, Dependency, Degraded, Not installed, Log full. administrative state: This attribute can have 3 different values: locked, unlocked and shutting down. location Name : this attribute identifies a location. operational state : This attribute indicates whether or not the resource associated to the managed object is physically installed and working. usage state : This attribute indicates the usage of the resource associated to the managed object with regards to 3 possible values: Idle, Active and Busy. user label : This optional attribute contains the Friendly Name information. The Friendly Name is used to give meaningful user friendly information on the alarm origin. vendorName : this attribute identifies the vendor of the associated managed object. version : this attribute identifies the version of the associated managed object. Access Control Domain: This optional attribute identifies the domain to which the alarm belongs. Network Element (NE) : Either a telecommunication equipment or groups parts of a Telecommunication Network. Have characteristics compliant with ITUT recommendations. Notification : Spontaneous data received by the system concerning an NE. Notification Identifier: This parameter, when present, provides an identifier for the notification, which may be carried in the Correlated notifications parameter of future notifications. Overflow : the C.A.L. can only contain a limited number of alarm instances, that you can defined. Once this number is reached, overflow purge occurs that you can customize. See the Setting the Overflow parameters section.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 122 / 124

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

Insertion Cause (in the H.A.L. only) : This parameter indicates which processing causes the alarm to be archived. It can be one of the following: Overflow purge. Manual purge. Automatic purge. Acknowledging a cleared alarm (or the inverse). Synchronization. AS IM Modification. Invalidation. See the beginning of the chapter Managing historical alarms.

Perceived Severity : This parameter defines six severity levels, which provide an indication of how it is perceived that the capability of the managed object has been affected. See the Alarm information section.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

Probable Cause : This parameter defines further qualification as to the probable cause of the alarm. Proposed Repair Actions : This optional attribute consists of a set of elements, each indicating a possible solution for solving the present alarm. Repetition Counter : This parameter indicates the number of times an alarm was sent by an agent. Reservation Status : This attribute indicates whether the alarm has been reserved by an operator or not. Severity : see Perceived Severity. Specific Problems : This optional attribute consists of a set of possible values complementary to the Probable Cause. State change definition : This optional attribute is used to indicate a state transition associated with the alarm. Telecommunication Network : Describes the network to be managed. Provides the transmission, the transport and the switching supports to the interconnected Network Elements. Threshold information : This optional attribute indicates information relative to the crossing of a threshold that implied the emission of the alarm. Trend indication : This optional information specifies the current severity trend of the managed object. The following values can be taken by this attribute: more severe: With regards to alarms notified previously, this alarm has a higher perceived severity. no change: With regards to alarms notified previously, the perceived severity of this alarm is equal to the highest severity of alarms notified previously. less severe: This alarm has not the highest severity of the set of alarm impacting the same object instance. Wrapping : Wrapping is the technique that enables the most recent entries in a file to replace the oldest when a file is full (overflow wrap action mode, see the Administering the C.A.L. section).

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 123 / 124

INDEX A
Alarms, selecting, 54 Modifying the filter criterion of a sublist, 36 the sorting criterion of a sublist, 47 the sublist display, 33 Mouse, general usage in the application, 18

C
Confirmations, confirmation windows, 23

S
Sublists deleting, 53 modifying, 31, 97 opening, 51 visualizing, 51

D
Deleting, a sublist, 53 Dialogue boxes, layout and organization, 22

H
Help, help functions, 23

W
Widgets, kinds of widgets used in the application, 18 Workspace, layout and organization, 20

M
Messages, message windows, 23

END OF DOCUMENT

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

02 957.130.722 A 3AL 71109 AAAA 124 124 / 124

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