Sei sulla pagina 1di 514

QUESTA PAGINA NON VA INSERITA NEL MANUALE

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK


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

COD.MANUALE HDBK P/N: 957.130.872 H Ed.01 3AL 61259 AAAA Ed.01


1300NM
1354RM Rel.5.2B
OPERATORS HANDBOOK VOL.2/2
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)

INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS


No PAGINE TOTALI PER ARCHIVIAZIONE: 4 + 510 = 514
DIMENSIONE BINDER SORGENTE (du ks): 236.302

AVVERTENZA WARNING
IL MANUALE COMPLETO COSTITUITO DA DUE VOLUMI QUESTO IL VOL.2/2
THE COMPLETE HANDBOOK IS COMPOSED BY TWO VOLUMES THIS IS VOL.2/2

STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING

COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:


HANDBOOK COMPOSITION AND ASSEMBLY:

No pagine numerate
fase
(facciate) numbered
step
No pages da from a to

1 ASSEMBLARE VOL.1/2 ASSEMBLE VOL.1/2

2 TARGHETTE - LABELS

3 FRONTESPIZIO - FRONT 2

4 INSERIRE SEPARATORE 6 - INSERT REGISTER 6

5 SC.6: MAINTENANCE 182 1/182 182/182

6 INSERIRE SEPARATORE 7 - INSERT REGISTER 7

7 SC.7: GRAPHICAL INTERFACE 230 1/230 230/230

8 INSERIRE SEPARATORE 8 - INSERT REGISTER 8

9 SC.8: SMF 96 1/96 96/96

TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: 510

TOTALE FOGLI A4 TOTAL A4 SHEETS: 255

WARNING FOR A-UNITS OTHER THAN A-ITALY


1AA 00014 0004 (9007) A4 ALICE 04.10

Labels are done according to A-Italy binder format.


Source file: ALICE 6.10

ED 01 VOL.2/2 RELEASED

957.130.872 TQZZA 3AL 61259 AAAA TQZZA Y 1/ 4

4
QUESTA PAGINA NON VA INSERITA NEL MANUALE
THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
Site
VIMERCATE ALCATEL OPTICS GROUP TND

Originators 1354RM REL.5.2B


V.PORRO
ERBA,CRIPPA
FERRARI,MANCINI
OPERATORS HANDBOOK

Domain : NETWORK MANAGEMENT


Division : 1354RM REGIONAL MANAGER
Rubric : REL.5.2B
Type : 1354RM REL.5.2B OPERATORS HANDBOOK
Distribution Codes Internal : External :

Approvals

Name M.RAGNI E.CORRADINI F.CASASOLE


App.

Name
App.

INFORMAZIONI EDITORIALI

ORIGINALE SU FILE: ALICE 6.10


sistemazione figlist
957.130.872 H
3AL 61259 AAAA
Ed.01
1300NM
1354RM Rel.5.2B

Regional Network Manager for SDH and Optical Networks


OPERATORS HANDBOOK
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 VOL.2/2 RELEASED

957.130.872 TQZZA 3AL 61259 AAAA TQZZA Y 2/ 4

4
1300NM
1354RM Rel.5.2B
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Regional Network Manager for SDH and Optical Networks

OPERATORS HANDBOOK

957.130.872 H Ed.01 3AL 61259 AAAA Ed.01

VOL.2/2

1300NM
1354RM Rel.5.2B
Regional Network Manager for SDH and Optical Networks
OPERATORS HANDBOOK

957.130.872 H Ed.01 3AL 61259 AAAA Ed.01

VOL.2/2
1300NM
1354RM Rel.5.2B
Regional Network Manager for SDH and Optical Networks

957.130.872 H Ed.01 3AL 61259 AAAA Ed.01 OPERATORS HANDBOOK VOL.2/2

1300NM
1354RM Rel.5.2B
Regional Network Manager for SDH and Optical Networks
957.130.872 H Ed.01 3AL 61259 AAAA Ed.01 OPERATORS HANDBOOK VOL.2/2

1300NM
1354RM Rel.5.2B
Regional Network Manager for SDH and Optical Networks

957.130.872 H Ed.01 3AL 61259 AAAA Ed.01 OPERATORS HANDBOOK VOL.2/2


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 VOL.2/2 RELEASED

957.130.872 TQZZA 3AL 61259 AAAA TQZZA Y 3/ 4

4
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 TQZZA
VOL.2/2 RELEASED

4
3AL 61259 AAAA TQZZA
Y
FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT

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

Alcatel 1300NM
Network Management

1354RM Rel.5.2B
Regional Network Manager for SDH and Optical Networks

Volume 2/2:

sections 68

957.130.872 H Ed.01 3AL 61259 AAAA Ed.01


957.130.872 H Ed.01 3AL 61259 AAAA Ed.01
1354RM REL.5.2B OPERATORS HANDBOOK
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

TABLE OF CONTENTS

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

1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 Purpose of the document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Target audiance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3 Document description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 FAULT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 Elementary Alarms and RM Probable Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Alarm Enabling/Disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.1 Q3 Alarm Enabling/Disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.2 QB3* Enabling UPA on specific CTP/CAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2.3 Enable / Disable frame supervision alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3 Alarm Severity Assignment Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.1 ASAP list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.2 ASAP create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3.3 ASAP correlate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.3.4 ASAP modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.4 Object Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.1 NE Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.2 Port Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.3 MSTP Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4.4 MSSpring Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4.5 Ne Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4.6 HOTTP Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.4.7 LOTTP Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4.8 CTP Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3 INTEGRATION OF 1354RM WITH SEC SECURITY SUBSYSTEM . . . . . . . . . . . . . . . . . . . . . . . . 29


3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.1.1 SEC Architecture on 1354RM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.1.2 SEC Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.1.3 Alarm Access Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.2 1330AS customization on 1354RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.2.1 Preliminary customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

01 000721 validated M.RAGNI ITAVE V.PORRO ITAVE


E.CORRADINI
01A 000515 proposal M.RAGNI ITAVE V.PORRO ITAVE
E.CORRADINI
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
1AA 00014 0004 (9007) A4 ALICE 04.10

1354RM REL.5.2B

OPERATORS HANDBOOK

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 1 / 182

182
3.2.2 Counter customisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.3 Spurious alarm management on 1354RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.3.1 New ASAP definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.3.2 Path Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

not permitted without written authorization from Alcatel.


3.3.3 HOTrail Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

All rights reserved. Passing on and copying of this


document, use and communication of its contents
3.3.4 Physical Link/MSTrail Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

4 INTRODUCTION TO MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.1 Alarm navigation and fault localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.1.1 Physical connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.1.2 MStrail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.1.3 HOtrail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.1.4 Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.1.5 Alarm processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.2 Diagnostic of the main objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4.2.1 Diagnostic of the path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.2.2 Diagnostic of the trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.2.3 EML Domain Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.2.4 NE Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.2.5 NE: Consistency Status=Not aligned ( TSDIM ONLY ) . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.2.6 NE: Consistency Status=Failed to Align ( TSDIM ONLY ) . . . . . . . . . . . . . . . . . . . . . . . . 86
4.2.7 NE: Consistency Status=Consistency Mismatch ( TSDIM ONLY ) . . . . . . . . . . . . . . . . 86
4.2.8 NE: NE Communication Problems: NE unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.2.9 NE Config. Download Status = fail to Disable / Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.2.10 NE: NEnot EML Aligned_auditfailed / misaligned ( for SENIM ONLY ) . . . . . . . . . . . . 87
4.2.11 Physical connection diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.2.12 SDH Port Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.2.13 SDH port Consistency status ( for SENIM ONLY)=Not found . . . . . . . . . . . . . . . . . . . . 90
4.2.14 SDH port Consistency status ( for SENIM ONLY)=Unknown . . . . . . . . . . . . . . . . . . . . 90
4.2.15 SDH port Upload status ( for TSDIM ONLY)=Not found . . . . . . . . . . . . . . . . . . . . . . . . 90
4.2.16 SDH port Upload status ( for TSDIM ONLY)=Wrong . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.2.17 Routing link diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.2.18 Subnetwork diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.2.19 Ring diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.2.20 Node diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4.2.21 Payload Configuration Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

5 PATH/TRAIL ALLOCATION FAILURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99


5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5.2 Allocation failure diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
5.2.1 Show Failure information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
5.2.2 Obstacles and Unsatisfied Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5.2.3 Other errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

6 DIAGNOSTIC OF THE NPE RING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115


6.1 User Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
6.1.1 MidProtocol Role ( NODE CONDITION ) attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
6.1.2 MidProtocol Role ( NODE CONDITION) attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
6.1.3 Allowed combinations of East, West, and MidProtocolRole . . . . . . . . . . . . . . . . . . . . . 122
6.1.4 Ring Active Condition attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
6.1.5 Span Active Condition attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
1AA 00014 0004 (9007) A4 ALICE 04.10

6.1.6 Ring Pending Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127


6.1.7 Span Pending Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
6.1.8 Lockout Working Ring attributes ( not implemented in this release ) . . . . . . . . . . . . . . . . 129

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 2 / 182

182
6.1.9 Lockout Working Span attributes ( not implemented in this version release ) . . . . . . . . 130
6.1.10 Inhibition chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
6.1.11 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
not permitted without written authorization from Alcatel.

7 LOGGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
All rights reserved. Passing on and copying of this
document, use and communication of its contents

8 NMLEML CONSISTENCY CHECKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149


8.1 NMLEML Consistency Checks ( SENIM ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
8.1.1 Consistency audit ( SENIM ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
8.1.2 Consistency download ( SENIM ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
8.2 NMLEML Consistency Checks ( TSDIM ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
8.2.1 Download disable management ( TSDIM ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
8.2.2 Ne isolation detection and recovery ( TSDIM ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
8.2.3 Consistency download management ( TSDIM ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
8.2.4 Consistency Status ( TSDIM ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
8.2.5 Consistency audit management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
8.2.6 Reporting during consistency ( TSDIM ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
8.2.7 Consistency Status Diagnostic ( TSDIM ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

9 1354RM PROCESS CONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159


9.1 Introduction to process control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
9.1.1 Actions:Startup pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
9.1.2 Actions:Shutdown pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
9.1.3 Actions:Control pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
9.1.4 View pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 3 / 182

182
LIST OF FIGURES AND TABLES

FIGURES

not permitted without written authorization from Alcatel.


Figure 1. Path: Show/Set Attributes: alarm enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

All rights reserved. Passing on and copying of this


document, use and communication of its contents
Figure 2. CAP Alarm Enabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 3. CAP: Show/Set Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 4. CAP: Show/Set Attributes: alarm enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 5. Alarm Profile List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 6. ASAP Creation dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 7. Correlating paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 8. Object correlation to an alarm profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 9. Alarm profile list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 10. The selected Alarm Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 11. ASAP Profile atributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 12. Select Command to Create an ASAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 13. NAPS View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 14. Alarm Management Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 15. HO Trail Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 16. HO Trail ASAP Correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 17. MSTrail Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 18. Display of associated MSTrail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 19. Associate ASAP to Physical Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 20. Associate ASAP to MSTrail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 21. Counter summary window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 22. Physical Connection Alarm sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 23. Navigation: External Application: 1354RM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 24. Physical connection structure window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Figure 25. Alarm details window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 26. MS Trail alarm sublist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 27. MStrail structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 28. Alarm details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 29. HOtrail alarm sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 30. Paths in trail window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 31. Alarm details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 32. Path alarm sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 33. Path Naps view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 34. Path Alarm details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 35. Alarm processing sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 36. Alarm processing navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 37. Allocation failure management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 38. Path List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Figure 39. Netscape Path/Trail allocation failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Figure 40. Failed Object frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 41. Netscape Path Trail allocation failure: problem summary frame. . . . . . . . . . . . . . . . . . . . 103
Figure 42. ProblemType and Constraint list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 43. Route display components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 44. END 1 / END 2 termination point names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 45. Problem Detail frame. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 46. Netscape Path/Trail allocation failure description window. . . . . . . . . . . . . . . . . . . . . . . . . . 106
Figure 47. Generic Help on allocation failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 48. Generic Help on allocation failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107


Figure 49. Example of problem description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Figure 50. Problem menu list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 4 / 182

182
Figure 51. Example of display of a protected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 52. Example of display of a protected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Figure 53. Constraint List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Figure 54. Processed Constraint List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
not permitted without written authorization from Alcatel.

Figure 55. Examples of interpretation of the Constraint list rows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Figure 56. Example of OTHER ERRROR display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114


Figure 57. 4 fibre MS SP reporting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Figure 58. ConfigurationState = virtual icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Figure 59. ConfigurationState diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Figure 60. ConfigurationState = enabled/active icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 61. MidProtocolRole ( NODE CONDITION ) icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 62. WestProtocolRole possible icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 63. EastProtocolRole possible icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 64. East failure Of Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Figure 65. West failure Of Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Figure 66. East ring active condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 67. West ring active condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 68. East span active condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Figure 69. West span active condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Figure 70. East ring pending command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 71. West ring pending command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 72. East span pending command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 73. West span pending command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 74. East Lockout Working Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 75. West Lockout Working ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 76. East Lockout Working Span . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 77. West Lockout Working Span . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 78. Bidirectional Signal Fail / Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 79. Bidirectional Signal Fail / Ring cleared .WTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Figure 80. Double Bidirectional Signal Fail / Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Figure 81. Forced Switch / Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Figure 82. Double Forced Switch / Ring to different nodes, node isolated . . . . . . . . . . . . . . . . . . . . . 138
Figure 83. Double signal Fail / ring, node isolated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 84. Forced Switch / Span . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Figure 85. Double Manual Switch / Ring pending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Figure 86. Signal Fail / Ring pending, Forced Switch / Ring pending . . . . . . . . . . . . . . . . . . . . . . . . . 142
Figure 87. Signal Fail Span, Signal Fail / Ring pending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Figure 88. Event Log filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Figure 89. Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Figure 90. Process control window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Figure 91. Process Control window:Actions:Startup pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 92. Process Control window:View pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Figure 93. Process Control window:View : History: Local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Figure 94. Process Control window:View : History: Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Figure 95. Process Control window:View : Agent processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Figure 96. Database process view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Figure 97. View:Configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Figure 98. Agent trace selection box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Figure 99. Example of agent trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 5 / 182

182
TABLES
Table 1. Elementary alarm mnemonics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Table 2. Probable Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 3. ConfigurationState, node conditions, and RM display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

not permitted without written authorization from Alcatel.


Table 4. Values of Consistency Status attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

All rights reserved. Passing on and copying of this


document, use and communication of its contents
Table 5. Starting and final Consistency status given the consistency results for consistency audit
in Mark Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Table 6. Initial and final Consistency status given the consistency results for consistency audit in
Notify Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 6 / 182

182
1 INTRODUCTION

1.1 Purpose of the document


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

The aim of this document is to describe the operations related to the maintenance of the protection network
controlled by the 1354RM.

1.2 Target audiance

This document is intended for people who are in charge of the maintenance of the network.

Before starting this document, it is recommended reading the following handbook:

1330AS Operators Handbook,

1353SH Operators Handbook,

the Operators Handbooks of the supervised Network Elements

1.3 Document description

This section covers the following topics:

Elementary Alarms and Probable Causes

Alarm Enabling/Disabling

ASAP

Object Propagation

1330AS SECNAD CUSTOMIZATION

1330AS Customization

Spurious alarm Management

Alarm Navigation

Diagnostic

PATH/TRAIL fail to allocate

NPE Diagnostic

Logger

NMLEML Consistency QB3*

NMLEML Consistency TSDIM

Process Monitor
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 7 / 182

182
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 H
SC.6:MAINTENANCE

182
3AL 61259 AA AA
8 / 182
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
2 FAULT MANAGEMENT

Alarm messages on elementary objects (nap, cap, ctp, port, mstp) are received from EML, processed and
propagated to the affected objects.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

These alarms are propagated to the following objects:

a) Transport entities (link connection, trail, path)

b) Topological object (node, ring, subnetwork, network)

Alarms are generated on paths, Physical Connections, Trails (both HO and MS).

The communication EMLNML is described by SENIM protocol, then these resources are said SENIM
objects. Elementary Alarms are received from EML layer and processed by RM in order to determine the
RM object to be marked as faulty ( RM Object Impacted ). RM provides for the impacted object the Alarm
Severity, the Operational State and the Probable Cause.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 9 / 182

182
2.1 Elementary Alarms and RM Probable Causes

Elementary Alarms are described in the documentation of the Network Elements and in the documentation
of the EML OS.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
RM Probable Causes are listed in Table 2.

Table 1. Elementary alarm mnemonics

AIS Alarm Indication Signal

ExBER Excessive Bit Error Rate

FERF FarEnd Receive Failure

FERF_In FarEnd Receive Failure Ingressing

K1K2PM K1_K2_ProtocolMismatch

LOF Loss of Frame

LOP Loss of Pointer

LOS Loss of Signal

PLM Path Label Mismatch

PTM Path Trace Mismatch

RAI Remote Alarm Interface

RDI Remote Defect Indication

neNR NE not Reachable

reISO Resource Isolation

SD Signal Degrade

SSF Server Signal Failure

SLM Signal Label Mismatch

SSF_In Server Signal Failure Ingressing

SSF_Eg Server Signal Failure Egressing

TrF TransmitterFailure

rxF Rx Failure

txD Transmitter Degraded

txF Tx Failure

UNEQ Unequipped

UPA Unavailable Path Alarm

URU Underlying Resource Unavailable


1AA 00014 0004 (9007) A4 ALICE 04.10

N.B. The Elementary alarms reISO. SSF, SSF_In, SSF_Eg apply to TSDIM only.

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 10 / 182

182
Table 2. Probable Causes

Probable Cause Meaning Event Type


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

PDHFailure PDH Port Failure Comunication Alarm

RS Failure Regenerator Failure Comunication Alarm

DegSig Degraded Signal Comunication Alarm

MediaEqFail Media or Equipment Failure Comunication Alarm

SDHFailure SDH Port Failure Comunication Alarm

remSDHFailure RemoteSDH Port Failure Comunication Alarm

UnderProtDeg Underlying Protection Degraded Comunication Alarm

ExBer Excessive Ber Comunication Alarm

ConfMismatch Configuration Mismatch Processing Error Alarm

mSConfMismatch MSTrail Configuration Mismatch Processing Error Alarm

QualityTC15m Quality Threshold Crossed 15m Quality of Service Alarm

QualityTC24h Quality Threshold Crossed 24h Quality of Service Alarm

AlrfloodingHP High Priority Alarm Flooding Comunication Alarm

AlrfloodingLP Low Priority Alarm Flooding Comunication Alarm

NenotReachable Ne not Reachable Processing Error Alarm (SENIM only)

reISO Resource Isolation Equipment Alarm (TSDIM only)

N.B. The Probable Cause reISO applies to TSDIM only.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 11 / 182

182
2.2 Alarm Enabling/Disabling

Alarms can be enabled or disabled only for TSDIM Network Elements. For QB3* Network Elements only
the propagation of the selected alarms can be enabled / disabled at RM level.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
2.2.1 Q3 Alarm Enabling/Disabling

Q3 alarms can be enabled/disabled on the involved Network Element for a certain path.

SEQUENCE

a) On path creation

1) On path creation. The user can modify the following attributes:

Q3 PDH Alarm Enabling Rule ( On Implementation/On Commissioning/Manual ). For TSDIM


equipments.

Q3 SDH Alarm Enabling Rule ( On Implementation/On Commissioning/Manual ) . For TSDIM


equipments.

2) If the user, when creating the path, selects Alarm Enabling Rule: Manual, for this Path it will be
possible to enable / disable the involved alarms ( from the Path List: menu Actions: SDH/PDH
Alarms enable/disable.

b) After path creation, from the Path List the user can modify the PDH/SDH alarm enabling rule by
selecting the menu Actions: SDH/PDH Alarms: Set enabling rule, as in the case of path creation.

c) A dialog box is presented, which allows the enabling rule selection by means of a dictionary.

Alarms on PDH ports, NAPs, boundary CTPs are enabled if Q3 Alarm Enabling rule= on
Implementation.

d) To verify the successful change of this values the user can issue a Show/Set Attributes on the
selected path. See Figure 1.

N.B. Q3 Alarms enabled means AIS, SSF and FERF enabled.

Q3 Alarms disabled means AIS, SSF and FERF disabled.

Q3 Alarms partially enabled means AIS and FERF enabled.

N.B. Q3 Alarm Enabling/Disabling is also available for trails:

rom the Trail List the user can modify the PDH/SDH alarm enabling rule by selecting the menu
Actions: SDH/PDH Alarms: Set enabling rule.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 12 / 182

182
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
01

957.130.872 H
SC.6:MAINTENANCE
Figure 1. Path: Show/Set Attributes: alarm enabling

182
3AL 61259 AA AA
13 / 182
2.2.2 QB3* Enabling UPA on specific CTP/CAP

This includes the ability of RM to setup alarm propagation rules other than the default ones defined for
physical connections related to virtual elements or based on Line Systems / Radio Links. By default AIS

not permitted without written authorization from Alcatel.


and UPA on CTPs are never received by RM and this prevent a correct alarm from being propagated on

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not terminated paths.

To enable the UPA alarm you can enter the Alarm enabling: LOP,EXBER,UPA command on the selected
CAP. See Figure 2.

Figure 2. CAP Alarm Enabling.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 14 / 182

182
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
01

957.130.872 H
SC.6:MAINTENANCE
Figure 3. CAP: Show/Set Attributes

182
3AL 61259 AA AA
15 / 182
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Figure 4. CAP: Show/Set Attributes: alarm enabling

2.2.3 Enable / Disable frame supervision alarm

This feature allows enabling and disabling frame supervision on bulk or structured PDH flows.

The operator can select a PDH port and execute the command to enable or disable the frame supervision.

The command is available on 1641SX (managed by WX 1.7.1) on configurable 140, 34, 2 Mbit/s PDH
ports.

By default the frame supervision alarm and the consequent action (AIS) are disabled.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 16 / 182

182
2.3 Alarm Severity Assignment Profile

RM Object Severity is the RM Object ALARMSTATUS field value, which depends on the correlated ASAP
(Alarm Severity Assignement Profile) .
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

ASAP is managed for Physical Connections, MSTrails, HOTrails, paths.

The main operations relevant to ASAP are LIST, CREATE, CORRELATE and MODIFY.

2.3.1 ASAP list

The ASAP class is inserted under the Network Domain. From the browser the operator points with the
mouse to the Network Domain, issuing Display: Related Items: Alarm Profiles . The list of the current
profiles is displayed. See Figure 5. as an example.

Figure 5. Alarm Profile List.

The severity can be no alarm if the alarm must not be emitted.

N.B. A default ASAP is available; when a path, a trail or a physical connection is created, the default
ASAP is assigned.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 17 / 182

182
2.3.2 ASAP create

The user can create new ASAPs. The command is also available at the user interface from the path,
trail or physical connection views. The sequence is as follows:

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
1) From the browser point with the mouse to the Network Domain and issue the command Alarm:
Create Alarm Profile. The ASAP Creation dialog box is displayed. See Figure 6.

2) Enter via the keyboard the ASAP userlabel and assign the suitable severity to the relevant
probable cause/s. Click on button Create to confirm the creation.

Figure 6. ASAP Creation dialog box.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 18 / 182

182
2.3.3 ASAP correlate

A correlation action is available in order to assign a new ASAP to relevant objects. The command
is also available at the user interface from the path, trail or physical connection views. One of the
not permitted without written authorization from Alcatel.

possible sequences is as follows:


All rights reserved. Passing on and copying of this
document, use and communication of its contents

1) Select the path/paths from path list and click on button Correlate paths to an Alarm profile as
indicated in the window shown in Figure 7. The object correlation to an alarm profile dialog box
is displayed ( See Figure 8. on page 20 )

Figure 7. Correlating paths


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 19 / 182

182
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Figure 8. Object correlation to an alarm profile

2) Select the Alarm profile button as can be seen from Figure 8.

The Alarm profile list window is presented ( see Figure 9. on page 21).

3) Select the involved profile and click on button Correlate path/trail/physicalConnection to an


Alarm profile.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 20 / 182

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

Figure 9. Alarm profile list

The Alarm Profile Correlation window now contains in the Object Correlation area the
requested profile as you can see in Figure 10.

4) Select the Correlate button.

Figure 10. The selected Alarm Profile.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 21 / 182

182
2.3.4 ASAP modify

The user can modify a profile simply issuing a Show/Set Attributes of the profile. See Figure 11.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Figure 11. ASAP Profile atributes.

When a new ASAP is assigned to an object or the associated one is modified, the severity of alarms
present on the object is revalueted clearing the alarm and then generating the alarm with the new
severity if different from no alarm

remSDHFailure alarm activation

By default this alarm is deactivated since the default ASAP sets it to notAlarmed.
1AA 00014 0004 (9007) A4 ALICE 04.10

To activate it, a new ASAP has to be created and correlated to the involved path.

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 22 / 182

182
2.4 Object Alarm Propagation

2.4.1 NE Alarm Propagation


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

The Elementary Alarm neNR ( NE not reachable ) is received through EML layer in case of SENIM
equipments. The RM impacted object is the Node , the Alarm Severity is Major and the Operational State
is Disabled.

The Elementary Alarm reISO ( resource isolation ) is received through EML layer in case of TSDIM
equipments. The RM impacted object is the Node , the Alarm Severity is Major and the Operational State
is Disabled.

2.4.2 Port Alarm Propagation

The table listed below summarizes the alarm propagation for the object Port. Elementary Alarms are
received from EML layer and processed by RM in order to determine the RM object to be marked as faulty
( RM Object Impacted ). RM provides for the impacted object the Alarm Severity, the Operational State
and the Probable Cause.

Object Elementary RM Object RM Object Operational RM Probable


alarm impacted Severity State cause

LOS / LOF Physical Conn Major Disabled MediaEqFail


URU /TrD / TrF MSTrail
SDH Port rxF txF HOLink Conn

lowReliability Physical Conn Warning Unchanged UnderProtDeg


note1

note1: for nonprotected MSTrail the supported HOLCs are set to disabled.

URU Path Major Disabled SDH Failure

LOS LOF
PDH Port ExBER SD Path Warning Unchanged PDH Failure
FERF RAI AIS

lowReliability Path Warning Unchanged UnderProtDeg

N.B. The Elementary Alarm lowReliability for SDH Port refers to SDH Ports protected by the line
protection MSP ( also called APS) mechanism.

N.B. The Elementary Alarm lowReliability for PDH Port refers to PDH Ports protected by the
equipment protection EPS mechanism.

N.B. In the Sink ports only URU and Low Reliability alarms are taken into account. The remaining
alarms are not propagated since they are not significant for the unidirectional path.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 23 / 182

182
2.4.3 MSTP Alarm Propagation

The table lsted below summarizes the alarm propagation for the object MSTP. Elementary Alarms are
received from EML layer and processed by RM in order to determine the RM object to be marked as faulty

not permitted without written authorization from Alcatel.


( RM Object Impacted ). RM provides for the impacted object the Alarm Severity, the Operational State

All rights reserved. Passing on and copying of this


document, use and communication of its contents
and the Probable Cause.

Object Elementary RM Object RM Object Operational RM Probable


alarm impacted Severity State cause

ExBER MSTrail Major Disabled ExBer


msFERF RS Failure
msAIS HOLink Conn
MSTP note1
unreliable
msSD MSTrail Warning Unchanged DegSig
lowReliability UnderProtDeg

Conf. Mismatch MSTrail Major Unchanged mSconfMismatch

MSTP Conf. Mismatch MSTrail Major Unchanged mSconfMismatch


reliable

note1: for nonprotected MSTrail the supported HOLCs are set to disabled.

N.B. The Elementary Alarm MSSD ( Multiplex SectionSignal Degrade ) for MSTP refers to a
degraded signal on the involved Multiplex Section ( B2 byte )

N.B. The Elementary Alarm lowReliability refers to Ports protected by the line protection MSP
( also called APS) mechanism.

N.B. The Elementary Alarm Configuration Mismatch for MSTP refers to EMLNML
misalignment.

2.4.4 MSSpring Alarm Propagation

Object Elementary RM Object RM Object Operational RM Probable


alarm impacted Severity State cause

MS K1K2PM Node Major Unchanged


Spring

2.4.5 Ne Alarm Propagation

Object Elementary RM Object RM Object Operational RM Probable


alarm impacted Severity State cause

NE neNRreISO Node Major Disabled


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 24 / 182

182
2.4.6 HOTTP Alarm Propagation

The table lsted below summarizes the alarm propagation for the object HOTTP ( Higher Order Trail
Termination Point ). HOTTPs are said NAPs ( Network Access Points ) if they are connected to 140 Mb
not permitted without written authorization from Alcatel.

ports. If the HOTTP is further structured, it is called HOCAP ( Connection Access Point ).
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Elementary Alarms are received from EML layer and processed by RM in order to determine the RM object
to be marked as faulty ( RM Object Impacted ). RM provides for the impacted object the Alarm Severity,
the Operational State and the Probable Cause.

Object
Elementary RM Object RM Object Operational RM Probable
alarm impacted Severity State cause

HPUNEQ
HPSLM/HPPLM Path Major Disabled SDH Failure
HOTTP HPUPA/SSF
( NAP )
Threshold15m QualityTC15m
Path Minor Unchanged
Threshold24h QualityTC24h

Conf. Mismatch Path Major Unchanged ConfMismatch

HPUNEQ/Ex
HOTrail Major Disabled SDH Failure
BER
HPSLM/HPPLM
LOLink Conn
HPUPA/SSF
HOTTP
( CAP ) LOLink Conn.
HPLOM Disabled
(TU12 only)

Threshold15m QualityTC15m
Threshold24h HOTrail Minor Unchanged QualityTC24h
Conf. Mismatch Conf. Mismatch

N.B. The Elementary Alarm Configuration Mismatch refers to EMLNML misalignment.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 25 / 182

182
2.4.7 LOTTP Alarm Propagation

The table lsted below summarizes the alarm propagation for the object LOTTP ( Lower Order Trail
Termination Point ). LOTTPs are said NAPs ( Network Access Points ) and are connected to lower order

not permitted without written authorization from Alcatel.


PDH ports.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
Elementary Alarms are received from EML layer and processed by RM in order to determine the RM object
to be marked as faulty ( RM Object Impacted ). RM provides for the impacted object the Alarm Severity,
the Operational State and the Probable Cause.

Object
Elementary RM Object RM Object Operational RM Probable
alarm impacted Severity State cause

LPUNEQ
LPSLM/LPPTM Path Major Disabled SDH Failure
LPUPA/ SSF
LO
TTP(NAP) Threshold15m QualityTC15m
Path Minor Unchanged
Threshold24h QualityTC24

Conf. Mismatch Path Major Unchanged ConfMismatch

N.B. The Elementary Alarm Configuration Mismatch refers to EMLNML misalignment.

N.B. LP=Lower Order Path ; UNEQ=Signal Label Unequipped ; SLM=Signal Label Mismatch ;
UPA=Unavailable Path Alarm; PTM= Path Trace Mismatch; SSF=Server Signal Failure
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 26 / 182

182
2.4.8 CTP Alarm Propagation

The table lsted below summarizes the alarm propagation for the object CTP ( Connection Termination
Point ).
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Boundary CTPs are the CTPs on the boundary of the Network Domain.

Elementary Alarms are received from EML layer and processed by RM in order to determine the RM object
to be marked as faulty ( RM Object Impacted ). RM provides for the impacted object the Alarm Severity,
the Operational State and the Probable Cause.

Object
Elementary RM Object RM Object Operational RM Probable
alarm impacted Severity State cause

AULOP
HOLink Conn Disabled
ExBER
HOCTP Threshold15m QualityTC15m
Path or
Threshold24h Minor Unchanged QualityTC24h
HOTrail
Conf. Mismatch Conf. Mismatch

Path / HO Trail Major Disabled SDH Failure


AULOP HOLink Conn
LOLink Conn

AUUPA/ Path / HOTrail Major Disabled SDH Failure


SSF_Eg LOLink Conn

HOCTP SSF_In /
Boundary UNEQ_In / Path / HOTrail N.A. Unchanged remSDH Failure
FERF_In / RDI

ExBER Path / HOTrail Major Disabled ExBER

Threshold15m QualityTC15m
Threshold24h Path/HOTrail Major Unchanged QualityTC24h
Conf. Mismatch ConfMismatch

tuLOP/
LOCTP LOLink Conn Major Disabled
tuLOM

SSF_In /
UNEQ_In /
Path N.A. Unchanged remSDH Failure
FERF_In / RDI

tuUPA/
Path Major Disabled SDH Failure
LOCTP SSF_Eg
Boundary TULOP Path Major Disabled SDH Failure
TULOM LOLink Conn

Threshold15m QualityTC15m
1AA 00014 0004 (9007) A4 ALICE 04.10

Threshold24h Path Minor Unchanged QualityTC24h


Conf. Mismatch ConfMismatch

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 27 / 182

182
N.B. The Elementary Alarm Configuration Mismatch refers to EMLNML misalignment.

N.B. AU=Administrative Unit; TU=Tributary Unit; LP=Lower Order Path ; UNEQ=Signal Label
Unequipped ; SLM=Signal Label Mismatch ; UPA=Unavailable Path Alarm ; LOP=Loss of

not permitted without written authorization from Alcatel.


Pointer; LOM=Loss of Multiframe ( Vx bytes ) ; ExBER=Excessive BER ; SSF_Eg=Server

All rights reserved. Passing on and copying of this


document, use and communication of its contents
Signal Failure Egressing
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 28 / 182

182
3 INTEGRATION OF 1354RM WITH SEC SECURITY SUBSYSTEM

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

This Chapter deals about the following subjects:

SEC Architecture on 1354RM System

SEC Administration

Alarm Access Configuration

3.1.1 SEC Architecture on 1354RM System

The SEC Subsystem is composed of two permanent processes:

secim process, which is the agent of the Security Subsystem and keep all the informations related
to the users and the system. Secim process is running only on 1354RMIM.

lss process, which is a kind of gate for applications related to user Security profile. One lss process
is instantiated for each workstation/server belonging to the 1354RM system (1 for each presentation
and each IM).

These permanent processes are configured to automatically run after the installation.

The SEC integration on 1354RM, as a first step, is intended only for the integration of Security
Management within AS (Alarm Surveillance). This means that each 1354RM operator using AS is able
to view/manage only alarms coming from Network resources that it can manage.

In order to have inside SEC Subsystem all the informations concerning Security, SEC is also integrated
in SMF, in order to get informations related to new users, user removal, and initiator management .
Moreover the integration of SEC in SMF is also related to the Backup operation. Each time a new Operator
backup is performed also SEC database is backuped.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 29 / 182

182
3.1.2 SEC Administration

SEC Subsystem is provided with a default customization for which on an RM is automatically configured
to run secim process if RMIM and lss process for each kind of RM (IM|US.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
The default configurations are put in the directory /usr/sec/1354RM_<NTWDOMAIN>.

In order to distinguish 1354RM SEC processes from the 1353SH ones the RM processes are called
<process_name>_1354RM_<NTWDOMAIN>.

The SEC configuration is also related to the automatic start of SEC process: in the /etc/inittab file is inserted
1 line for each permanent SEC process. This line invokes the script
run_SECIM|LSS_1354RM_<NTWDOMAIN> that checks for SEC abilitation to run and launch the
secim|lss_1354RM_<NTWDOMAIN> process. The automatic start of SEC processes is set on runlevel
4 that is the 1354RM runlevel default. No checks are performed on the 1354RM effective runlevel (it
is supposed to be 4).

During Operator Backup and Restore the SEC subsystem is stopped in order to add to the Operator
Informations also Informations related to SEC. The actions related to SEC start and stop are automatically
launched by SMF.

If some problem occurs during SMF>Operator Administration and SEC DB is not updated by the changes
done on RM through the SMF, it is possible to launch the script as snml user :

/usr/sec/integration/script/alignsecdb

This procedure starts from the last successful SEC command and alignes the SEC DB to the actual RM
Security definitions.

If at login time the user is alerted by the Message Box:

Security for 1354RM_<NTWDOMAIN> is not activated. Please contact your System


Administrator, the problem is that the user is not defined in the SEC DB, or the SEC Subsystem has been
stopped (Restore proc.) or internal error.

N.B.: If the Message doesnt say 1354RM it is belonging to the SEC installed for SH

RESTRICTIONS

SEC 5.0 doesnt manage the scheduling time. This means that if an user has a scheduled rule this rule
is applied everytime. This limitation is not due to the integration level but to the fact that SEC 5.0 doesnt
support it.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 30 / 182

182
3.1.3 Alarm Access Configuration

Depending on 1354RM user definitions the following AS Access Rights are granted:
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Where:

AS Access Rights means the AS accessability in terms of AS Administration:

ADMIN: Users can invoke AS Administration and Synchronization

VIEW: User cannot interact with AS Administration functionalities

Alarm Access Rights shows the Alarm accessability rules that are allowed to user:

MGT: Users that have this capability, if allowed by the NAD Rule (see below), can manage accessible
alarms ( acknowledgement)
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 31 / 182

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

Alarm AccessType shows the alarm accessibility

MGT means that user have the possibility to Acknowledge alarms (ManaGemenT)

RO means that user can only access alarms in a view mode (ReadOnly)

The MGT Alarm Accessability is granted if allowed by the System Profile (previous table) otherwise (for
LookOnly users) is set to RO.

X show which alarm types that can be accessed by user with the corresponding NAD Rule associated

X* show alarm types (only marked with user NAD) that can be accessed by user with the corresponding
NAD Rule associated

In order to provide a flexible way to configure AS Access on Alarm the configuration file
/usr/snml/conf/sec/1354RM_Ruler is provided.

This file drives the user Access Rights definition in the SECDB and have to be changed before the SEC
installation in order to keep coherent user creations.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 32 / 182

182
In particular in order to give to LookOnly users the possibility to manage all the Alarms without keeping
into account the RM Rule change the line:

System_Profile : LookOnly : ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,


not permitted without written authorization from Alcatel.

ASHISTUSM_FAD@AsHistoricalUsm :
All rights reserved. Passing on and copying of this
document, use and communication of its contents

as follows:

System_Profile : LookOnly :ASCURUSM_ALARM_MANAGER_FAD@AsCurrentUsm,


ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm, ASHISTUSM_FAD@AsHistoricalUsm

On the other side, if the LookOnly users Accessability have to be extended to manage alarms depending
on 1354RM Access Rules (second table), change the line:

System_Profile : LookOnly : ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,


ASHISTUSM_FAD@AsHistoricalUsm :

as follows:

System_Profile : LookOnly : ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,


ASHISTUSM_FAD@AsHistoricalUsm : ASCURUSM_ALARM_MANAGER_FAD@AsCurrentUsm
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 33 / 182

182
3.2 1330AS customization on 1354RM

The main steps of the 1330AS customization on 1354RM are:

not permitted without written authorization from Alcatel.


Deactivate the 1330AS standard counters.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
Define and activate the following five counters:

Processing: this counter will report all the alarms of processing type.

Physical Link: this counter will report all the alarms related to physical links with severity different
than Indeterminate.

MSTrail: this counter will report all the alarms related to MSTrails with severity different that
Indeterminate.

Path: this counter will report all the alarms related to paths with severity different than
Indeterminate.

HOTrail: this counter will report all the alarms related to HOTrails with severity different than
Indeterminate.

Procedures which follow are automatically executed during the installation.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 34 / 182

182
3.2.1 Preliminary customization

All these customizations are executed per each 1354RMIM .


not permitted without written authorization from Alcatel.

3.2.1.1 AutoPurging Filter


All rights reserved. Passing on and copying of this
document, use and communication of its contents

The following procedure is automatically executed during the installation.

a) Select the command Option: Administration.

b) Select the folder AutoPurge.

c) Insert the filter name as RM_Purge.

d) Select the button Severity, then select the severity Indeterminate. The alarm type button must be
deselected.

e) Click on the Save... button.

f) Click on the Apply button.

g) Click on the Close button.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 35 / 182

182
3.2.1.2 Archiving Filter

The following procedure is automatically executed during the installation.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
a) Select the command Option: Administration.

b) Select the folder Archiving Filter.

Insert the filter name as RM_Archive

Select the Severity button and then select CRITICAL, MAJOR, MINOR and WARNING severities
only.

Select the Probable Causes:

mediaOrEquipmentFailure
underlayingProtectionDegraded
regeneratorFailure
excessiveBer
degradedSignal
mSConfigurationMismatch
sdhFailure
pdhFailure
qualityThresholdCrossed15
qualityThresholdCrossed24
configurationMismatch
High Priority Alarm Flooding
Low Priority Alarm Flooding
Alarm Misaligned
EML not reachable

c) Click on the Save... button.

d) Click on the Apply button; you are warned that not all alarms will be archived, this is OK so click on
OK button.

e) Click on the Close button.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 36 / 182

182
3.2.1.3 Auto Acknowledge Filter

This procedure is optional.


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

a) Select the command Option: Administration.

b) Select the folder AutoAck.

c) Insert the filter name as RM_Acknowledge

d) Select the Severity button and then select INDETERMINATE severity only.

Be careful that the button Alarm Type is deselected (button up); in the initial setting of this filter it is
selected (botton down).

e) Click on the Save... button.

f) Click on the Apply button.

g) Click on the Close button.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 37 / 182

182
3.2.2 Counter customisation

The following procedure is automatically executed during the installation.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
All the following customisations are executed for each 1330AS USM related to 1354RM.

3.2.2.1 Display Customization

a) Select Display: Inactive Sublist in order to disable display of inactive sublist (bottom up).

b) Select Display: Severity Counter in order to enable the display of the severity counters (button down).

c) Select Display: AutoRaise in order to enable auto raising of the window in case of new alarms
(button down).

d) Select Exit: Save... to save the performed customisation.

3.2.2.2 Deactivation of standard counters

a) Select the counter MAIN ALARM LIST by clicking on it.

b) Select the command Sublist>Deactivate

Repeat point a) and b) for the counters DEFAULT ALARM SUBLIST, CRITICAL, MAJOR, MINOR,
WARNING, INDETERMINATE and CLEARED.

c) Select Exit>Save... to save the performed customisation.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 38 / 182

182
3.2.2.3 Physical Link Counter

The following procedure is automatically executed during the installation.


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

a) Select the command Sublist: Create.

b) Select the command Sublist: Modify; a new window is open.

c) Select the folder Display.

d) Change the name from <new sublist> to PHYSICAL LINK

e) Click on the colour; a new box is open, set all RGB index to 255 (white colour) and press Apply.

f) Arrange Displayed Attributes in order to provide Event Date & Time (in first position), Friendly Name,
EventType, Reservation Status, Clearing Status, Ack Status, Repetition Counter, Probable Cause,
Perceived Severity.

g) Select folder Filter.

h) Enter the filter name as RM_PhysicalLink

i) Select MO Class button and then insert the class 1.3.6.1.4.1.12.2.1.27.

j) Select the Severity button and then select all the severities unless INDETERMINATE.

k) Press Save... button.

l) Press Apply button.

m ) Press Close button.

n) Select the command Sublist: Activate.

o) Open the alarm list by double clicking on the counter and order the columns by dragging the relevant
headers. The order can be chosen by the customer according to his preferences, but be sure that
the same order is used for all the counters. Recommended order is:

Event Date & Time


Friendly Name
EventType
Probable Cause
Perceived Severity
Clearing Status
Ack Status
Reservation Status
Repetition Counter

p) Select Exit: Save... to save the performed customisation.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 39 / 182

182
3.2.2.4 MS Trail Counter

The following procedure is automatically executed during the installation.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
a) Select the command Sublist: Create.

b) Select the command Sublist: Modify; a new window is open.

c) Select the folder Display.

d) Change the name from <new sublist> to MS TRAIL

e) Click on the colour; a new box is open, set all RGB index to 255 (white colour) and press Apply.

f) Arrange Display Attributes in order to provide Event Date & Time (in first position), Friendly Name,
EventType, Reservation Status, Clearing Status, Ack Status, Repetition Counter, Probable Cause,
Perceived Severity.

g) Select folder Filter.

h) Enter the filter name as RM_MSTrail

i) Select the MO Class button and then insert the class 1.3.6.1.4.1.12.2.1.24

j) Select the Severity button and then select all the severities unless INDETERMINATE.

k) Select the Probable Cause button and then click on Select... button; the list of all available probable
causes is provided.

l) Select the probable causes:

regeneratorFailure

excessiveBer

degradedSignal

underlayingProtectionDegraded

mSConfigurationMismatch

m ) Press Save... button.

n) Press Apply button.

o) Press Close button.

p) Select the command Sublist: Activate.

q) Open the alarm list by double clicking on the counter and order the columns by dragging the relevant
headers. The order can be chosen by the customer according to his preferences, but be sure that
the same order is used for all the counters. Recommended order is:

Event Date & Time


1AA 00014 0004 (9007) A4 ALICE 04.10

Friendly Name

EventType

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 40 / 182

182
Probable Cause

Perceived Severity
not permitted without written authorization from Alcatel.

Clearing Status
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Ack Status

Reservation Status

Repetition Counter

18. Select Exit: Save... to save the performed customisation.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 41 / 182

182
3.2.2.5 HO Trail Counter

The following procedure is automatically executed during the installation.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
a) Select the command Sublist: Create.

b) Select the command Sublist: Modify; a new window is open.

c) Select the folder Display.

d) Change the name from <new sublist> to HO TRAIL

e) Click on the colour; a new box is open, set all RGB index to 255 (white colour) and press Apply.

f) Arrange Display Attributes in order to provide Event Date & Time (in first position), Friendly Name,
EventType, Reservation Status, Clearing Status, Ack Status, Repetition Counter, Probable Cause,
Perceived Severity.

g) Select folder Filter.

h) Enter the filter name as RM_HOTrail

i) Select the MO Class button and then insert the class 1.3.6.1.4.1.12.2.1.24 (N.B. the same as for MS
Trail).

j) Select the Severity button and then select all the severities unless INDETERMINATE.

k) Select the Probable Cause button and then click on Select... button; the list of all available probable
causes is provided.

l) Select the probable causes:

sdhFailure
qualityThresholdCrossed15
qualityThresholdCrossed24
configurationMismatch

m ) Press Save... button.

n) Press Apply button.

o) Press Close button.

p) Select the command Sublist: Activate.

q) Open the alarm list by double clicking on the counter and order the columns by dragging the relevant
headers. The order can be chosen by the customer according to his preferences, but be sure that
the same order is used for all the counters. Recommended order is:

Event Date & Time

Friendly Name

EventType
1AA 00014 0004 (9007) A4 ALICE 04.10

Probable Cause

Perceived Severity

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 42 / 182

182
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
r)



01
Ack Status

957.130.872 H
Clearing Status

Repetition Counter
Reservation Status

SC.6:MAINTENANCE
Select Exit: Save... to save the performed customisation.

182
3AL 61259 AA AA
43 / 182
3.2.2.6 Path Counter

The following procedure is automatically executed during the installation.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
a) Select the command Sublist: Create.

b) Select the command Sublist: Modify; a new window is open.

c) Select the folder Display.

d) Change the name from <new sublist> to PATH

e) Click on the colour; a new box is open, set all RGB index to 255 (white colour) and press Apply.

f) Arrange Display Attributes in order to provide Event Date & Time (in first position), Friendly Name,
EventType, Reservation Status, Clearing Status, Ack Status, Repetition Counter, Probable Cause,
Perceived Severity.

g) Select folder Filter.

h) Enter the filter name as RM_Path

i) Select the MO Class button and then insert the class 1.3.6.1.4.1.12.2.1.2

j) Select the Severity button and then select all the severities unless INDETERMINATE.

k) Select the Probable Cause button and then click on Select... button; the list of all available probable
causes is provided.

l) Select the probable causes:

sdhFailure

pdhFailure

qualityThresholdCrossed15

qualityThresholdCrossed24

configurationMismatch

m ) Press Save... button.

n) Press Apply button.

o) Press Close button.

p) Select the command Sublist: Activate.

q) Open the alarm list by double clicking on the counter and order the columns by dragging the relevant
headers. The order can be chosen by the customer according to his preferences, but be sure that
the same order is used for all the counters. Recommended order is:

Event Date & Time


1AA 00014 0004 (9007) A4 ALICE 04.10

Friendly Name

EventType

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 44 / 182

182
Probable Cause

Perceived Severity
not permitted without written authorization from Alcatel.

Clearing Status
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Ack Status

Reservation Status

Repetition Counter

r) Select Exit: Save... to save the performed customisation.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 45 / 182

182
3.2.2.7 Processing Counter

The following procedure is automatically executed during the installation.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
a) Select the command Sublist>Create.

b) Select the command Sublist>Modify; a new window is open.

c) Select the folder Display.

d) Change the name from <new sublist> to PROCESSING.

e) Click on the colour; a new box is open, set all RGB index to 255 (white colour) and press Apply.

f) Arrange Display Attributes in order to provide Event Date & Time (in first position), Friendly Name,
EventType, Reservation Status, Clearing Status, Ack Status, Repetition Counter, Probable Cause,
Perceived Severity.

g) Select folder Filter.

h) Enter the filter name as RM_Processing.

i) Select the Probable Cause button and then click on Select... button; the list of all available probable
causes is provided.

j) Select the probable causes:

Alarm Misaligned

High Priority Alarm Flooding

Low Priority Alarm Flooding

EML not reachable

k) Press Save... button.

l) Press Apply button.

m ) Press Close button.

n) Select the command Sublist>Activate.

o) Open the alarm list by double clicking on the counter and order the columns by dragging the relevant
headers. Th order can chosen by the customer according to his preferences, but be sure that the
same order is used for all the counters. Recommended order is:

Event Date & Time

Friendly Name

EventType

Probable Cause
1AA 00014 0004 (9007) A4 ALICE 04.10

Perceived Severity

Clearing Status

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 46 / 182

182
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


01
Ack Status

957.130.872 H
Repetition Counter
Reservation Status

SC.6:MAINTENANCE
16. Select Exit: Save... to save the performed customisation.

182
3AL 61259 AA AA
47 / 182
3.3 Spurious alarm management on 1354RM

It is possible to avoid alarm generation for objects under testing.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
3.3.1 New ASAP definition

Define a new ASAP setting the severity of all probable causes to Indeterminate. To do this perform the
following steps:

a) Start the browser.

b) Select the 1354RM icon.

c) Select the command Specific:Alarm:CreateAlarmProfile; a new window is open. As an alternative,


point with the mouse at the Network Domain and issue the command Alarm: Create Alarm Profile.

Figure 12. Select Command to Create an ASAP

d) Fill User Label field with Indet_Alarm_Profile

e) Change to Indeterminate the severity associated to all the proposed probable causes.

f) Click on Create button.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 48 / 182

182
3.3.2 Path Alarm Management

The following procedures describe how to manage paths in order to avoid that alarms on them are reported
to 1330AS while they are under test.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

3.3.2.1 Naps view after path creation

a) The path has been created with Implementation Rule = User (default) and Propagation Rule = When
Implemented (default).

b) As soon as the path is created a new window is opened reporting the path icon with its Naps (Naps
View). Click on Alarm icon making available all the icons relevant for alarm management.

Figure 13. NAPS View

c) Select the path icon.

d) Click on the icon Correlate paths to alarm profile (the last icon on the right); the correlation window
is opened.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 49 / 182

182
Report of elementary alarm correlation

Show the path alarms in route Show Communication alarm

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
Create a new alarm profile

Correlate path to an alarm profile

Figure 14. Alarm Management Icons

e) If in the ASAP space the Indet_Alarm_Profile is already present go to step h). (N.B. the ASAP
possibly provided is not the ASAP currently associated to the path, but it is the last referred ASAP).

f) Click on Alarm Profile icon; the list of the available ASAP is provided.

g) Select the Indet_Alarm_Profile ASAP.

h) Click on the icon Correlate path/trail/physical connection to an Alarm Profile (the same icon as
before). The ASAP icon is inserted into the correlation window.

i) On the correlation window click on the icon Start correlating all the specified objects (the same as
before). At this point the path is correlated to the relevant ASAP.

j) Implement the path.

From this point in time on alarms are reported to the path and visible by means of 1354RM USM, but no
1AA 00014 0004 (9007) A4 ALICE 04.10

alarm on this path is reported to 1330AS. Tests can be performed on the path without affecting
maintenance people.

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 50 / 182

182
3.3.2.2 Path commissioning

a) From the Path List window select the relevant path(s).


not permitted without written authorization from Alcatel.

b) Click on Alarm icon in order to make available all the icons relevant for alarm management. Click on
All rights reserved. Passing on and copying of this
document, use and communication of its contents

the icon Correlate Path to an Alarm Profile.

c) Click on the icon Correlate Path to an Alarm Profile; a new window is open (correlation window).

d) If in the ASAP space the default ASAP is already present go to step g.

e) Click on Alarm Profile icon; the list of the available ASAP is provided.

f) Select the default ASAP and click on the icon Correlate path/trail/physical connection to an Alarm
Profile (the same icon as before). The ASAP icon is inserted into the correlation window.

g) On the correlation window click on the icon Start correlating all the specified objects (the same as
before). At this point the path(s) is(are) correlated to the default ASAP. Since this point in time alarm
on the path(s) are reported also to 1330AS.

h) Commission the path.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 51 / 182

182
3.3.3 HOTrail Management

3.3.3.1 Trail creation

not permitted without written authorization from Alcatel.


a) Setup the trail setting Setup Rule = User (N.B. Default value is Automatic).

All rights reserved. Passing on and copying of this


document, use and communication of its contents

Figure 15. HO Trail Setup

b) As soon as the trail is defined a new window is open (Paths in Trail View).

c) Open the popup menu on the trail icon (pressing right button of the mouse) and select the command
Alarm>CorrelateAlarmProfile; a new window is open (correlation window).
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 52 / 182

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

Figure 16. HO Trail ASAP Correlation

d) If the Indet_Alarm_Profile is already present within the correlation window go to step g).

e) Click on Alarm Profile icon; the list of the available ASAP is provided.

f) Select the Indet_Alarm_Profile ASAP. Click on the icon Correlate path/trail/physical connection to
an Alarm Profile. The ASAP icon is inserted into the correlation window (see fig 6).

g) On the correlation window click on the icon Start correlating all the specified objects (the same as
before). At this point the trail is correlated to the relevant ASAP .
1AA 00014 0004 (9007) A4 ALICE 04.10

h) Allocate the trail.

i) Implement the trail.

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 53 / 182

182
3.3.3.2 Trail commissioning

a) There is no explicit commissioning on HOTrail. The scope of this phase is to cause the trail to report
alarms to 1330AS.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
b) On the Tail list window (possibly filtered on HOTrail) select the relevant trail(s).

c) Select the command Action>Alarms>CorrelateAlarmProfile.

d) Click on the icon Correlate Path to an Alarm Profile; ); a new window is open (correlation window).

e) If in the ASAP space the default ASAP is already present go to step h).

f) Click on Alarm Profile icon; the list of the available ASAP is provided.

g) Select the default ASAP and click on the icon Correlate path/trail/physical connection to an Alarm
Profile (the same icon as before). The ASAP icon is inserted into the correlation window.

h) On the correlation window click on the icon Start correlating all the specified objects (the same as
before). At this point the trail(s) is(are) correlated to the default ASAP. From this point in time on
alarms on trail(s) are reported also to 1330AS.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 54 / 182

182
3.3.4 Physical Link/MSTrail Management

3.3.4.1 Physical Link/MSTrail creation


not permitted without written authorization from Alcatel.

a) Activate the Physical Connection; this action causes that alarms possibly present on it are
All rights reserved. Passing on and copying of this
document, use and communication of its contents

immediately reported to 1330AS too.

b) Navigate from Browser to the Physical Connection.

c) From the popup menu associated to the Physical Connection (on browser) select the command
Configuration: Implement to create the associated MSTrail; this action causes that alarms possibly
present on the MSTrail are immediately reported to 1330AS too.

Figure 17. MSTrail Creation


1AA 00014 0004 (9007) A4 ALICE 04.10

The Physical connection implementation creates the MSTrail(s)

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 55 / 182

182
d) From the popup menu associated to the Physical Connection select the command Display: All
Related Item.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
Figure 18. Display of associated MSTrail document, use and communication of its contents

e) Select MSTrail within the box that is open.

f) Press No filter button; the associated MSTrail is provided below the Physical connection.

g) From the popup menu associated to the Physical connection select the command Alarm:
CorrelateAlarmProfile; a new window is open (correlation window).
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 56 / 182

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

Figure 19. Associate ASAP to Physical Connection

h) If in the ASAP space the Indet_Alarm_Profile is already present go to step m).

i) Click on Alarm Profile icon; the list of the available ASAP is provided )

j) Select the Indet_Alarm_Profile ASAP and click on the icon Correlate path/trail/physical connection
to an Alarm Profile. The ASAP icon is inserted into the correlation window

k) On the correlation window click on the icon Start correlating all the specified objects . At this point
both the Physical Connection and the MSTrail are correlated to the relevant ASAP. Alarm possibly
sent to 1330AS are automatically cleared (but must be acknowledged by operator to make them
disappear).

l) From the popup menu associated to the MSTrail select the command
Alarm>CorrelateAlarmProfile; the MSTrail is added to the correlation window.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 57 / 182

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

Figure 20. Associate ASAP to MSTrail

m ) On the correlation window click on the icon Start correlating all the specified objects . At this point
both the Physical Connection and the MSTrail are correlated to the relevant ASAP. Alarm possibly
sent to 1330AS are automatically cleared (but must be acknowledged by operator to make them
disappear).
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 58 / 182

182
3.3.4.2 Physical Link/MSTrail commissioning

There is no explicit commissioning of these entities. The mean of this phase is to cause both Physical Link
and MSTrail to report alarms to 1330AS.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

a) Put on the browser the relevant Physical Connection.

b) From the popup menu associated to the Physical Connection select the command Display>All
Related Item; select MSTrail within the box that is opened and then No filter button; the associated
MSTrail is provided below the Physical connection.

c) From the popup menu associated to the Physical connection select the command Alarm:
CorrelateAlarmProfile; a new window is open (correlation window).

d) From the popup menu associated to the MSTrail select the command
Alarm:CorrelateAlarmProfile; the MSTrail is added to the correlation window.

e) f in the ASAP space the default ASAP is already present go to step h)

f) Click on Alarm Profile icon; the list of the available ASAP is provided.

g) Select the default ASAP and click on the icon Correlate path/trail/physical connection to an Alarm
Profile. The ASAP icon is inserted into the correlation window.

h) On the correlation window click on the icon Start correlating all the specified objects (the same as
before). At this point both the Physical Connection and the MSTrail are correlated to the default
ASAP. Alarm relevant for these entities are sent again to 1330AS.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 59 / 182

182
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 H
SC.6:MAINTENANCE

182
3AL 61259 AA AA
60 / 182
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
4 INTRODUCTION TO MAINTENANCE

Maintenance operations consist of several functions that have to be executed following failures on the
network.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Note that the protection network comprises:

Telecommunication network (Network Elements and physical connections)

Control network consisting of 1354RM and 1353SH

Data Communication Equipment (Routers and Bridges)

The maintenance operations inherent to the Routers and Bridges are described in the documentation of
the Routers and Bridges.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 61 / 182

182
4.1 Alarm navigation and fault localization

The telecommunication network can bear various failures depending on the size of the resources.

not permitted without written authorization from Alcatel.


The paths affected by a failure are automatically rerouted on the available route (spare or main).

All rights reserved. Passing on and copying of this


document, use and communication of its contents
Should a Network Element fully breakdown, the system will attempt to reroute all paths crossing it.

Therefore, should one NE breakdown, only local drop traffic would be lost.

The RM Operators control the network on the Workstation through the graphical interface.

The operator is informed on the telecommunication network alarms through:

A1330AS application.

Notice that from 1354RM Rel.5.2.B on, alarms reported at 1330AS application are ONLY those
affecting the resources managed by the actually logged operator. This mainly applies to VPN
operators.

the map displaying objects in different colours identifying the status

the browser

The navigation from the Counter summary window is the first level maintenance procedure.

This procedure which is described in the following, applies to each row of the Counter summary window.

a) From the Counter summary window open the Alarm sublist clicking twice on the relevant row of the
Counter summary window ( PHYSICAL CONNECTION, MS TRAIL, HO TRAIL, PATH,
PROCESSING). As an alternative select the row and issue the Sublist: Open pulldown menu item.
See Figure 21.

Figure 21. Counter summary window


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 62 / 182

182
The relevant Alarm sublist is presented. Figure 22. shows an example of Physical Connection Alarm
sublist.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Figure 22. Physical Connection Alarm sublist

b) Select the alarm from the sublist and navigate it by selecting the Navigation: External Application:
1354RM pulldown menu item.( See Figure 23. ). A confirmation dialog box appears. Click on OK
to confirm.

Figure 23. Navigation: External Application: 1354RM.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 63 / 182

182
4.1.1 Physical connection

For the Physical connection object the physical connection structure window is presented:

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Figure 24. Physical connection structure window


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 64 / 182

182
Alarmed objects are marked by an alarm icon. By clicking on this icon a window is presented, which
gives details on the selected alarm. See Figure 25.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Figure 25. Alarm details window.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 65 / 182

182
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01
4.1.2 MStrail

957.130.872 H
SC.6:MAINTENANCE
The MStrail alarm sublist is shown in Figure 26.

Figure 26. MS Trail alarm sublist.

182
3AL 61259 AA AA
66 / 182
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
For the MStrail object the physical connection structure and relative navigation window is presented:
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Figure 27. MStrail structure

Alarmed objects are marked by an alarm icon. By clicking on this icon, the Alarms details window is
displayed. See Figure 28.

Figure 28. Alarm details.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 67 / 182

182
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01
4.1.3 HOtrail

957.130.872 H
SC.6:MAINTENANCE
The HOtrail alarm sublist is shown in Figure 29.

Figure 29. HOtrail alarm sublist

182
3AL 61259 AA AA
68 / 182
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.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 H
SC.6:MAINTENANCE
Figure 30. Paths in trail window

182
3AL 61259 AA AA
For the HOtrail object the path in trail window and the relevant navigation window is presented:

69 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 H
SC.6:MAINTENANCE
Figure 31. Alarm details

182
3AL 61259 AA AA
70 / 182
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
4.1.4 Path

The Path alarm sublist is shown in Figure 32.


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

Figure 32. Path alarm sublist

For the Path object the Nap view window and relative navigation window is presented:
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 33. Path Naps view

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 71 / 182

182
The severity can be no alarm if the alarm must not be emitted.

An example of Alarms details is shown in Figure 34.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
Figure 34. Path Alarm details
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 72 / 182

182
4.1.5 Alarm processing

In the following is presented the Alarm processing sublist:


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

Figure 35. Alarm processing sublist

For Alarm processing (EML object), only the navigated object is presented in the browser window.

Figure 36. Alarm processing navigation


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 73 / 182

182
4.2 Diagnostic of the main objects

This paragraph describes the diagnostic procedures to be executed for the main RM objects in case of
malfunction.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
The objects are:

path

trail

EML Domain

NE

Physical Connection

SDH Port

Subnetwork

Ring

Node

Payload
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 74 / 182

182
4.2.1 Diagnostic of the path

The path diagnostic concerns the following attributes:


not permitted without written authorization from Alcatel.

Path Alarm status


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Path working status

4.2.1.1 Path Alarm status

Regardless the path alarm status, navigate the path from the Alarm Counter Summary

N.B. The Path Alarm Status is Cleared if the path operational status is Enabled ( InService ), this
implies that a path using its spare route is not alarmed.

4.2.1.2 Path working status

The Path working status can be visualized on the Path List.


All the statuses whose description contains the ing suffix are of the workinprogress type. Hence the
path is in this status only for a certain period of time; the path should assume the Normal condition when
a certain timeout has expired. This condition does not require the Operators intervention. He must
intervene if one of the following conditions occurs:

failed to Add Leg

failed to Add Protection

failed to Release Resources

failed to Remove Leg

failed to Remove Protection

failed to Alllocate

failed to Deallocate

failed to Implement

failed to Deimplement

failed to Align SNCPs

failed to manage SNCPs

failed to change SNCP Mode

failed to connect

failed to disconnect
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 75 / 182

182
4.2.1.3 Path: Failed to Add Leg

CONDITIONS The path involved is of the broadcast type. The Operator entered an Add Leg
command on the Path involved.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
CAUSES Lack of resources

ACTIONS Verify the resources (physical connections and payload structure).


Should the path be protected, the protection can be removed and command
Add Leg can be entered again.

4.2.1.4 Path: Failed to Add Protection

CONDITIONS The path involved is of the unprotected type. The Operator entered command
Add Protection.

CAUSES Lack of resources, i.e. the spare resource corresponding to the main one is
not available.

ACTIONS Verify the resources (payload structure).

4.2.1.5 Path: Failed to Release Resources

CONDITIONS The Operator has entered an Add Protection or Remove Protection command
on the path.

CAUSES The cause is due to software latent errors.

ACTIONS Contact Alcatel Technical Assistance Center.

4.2.1.6 Path: Failed to Remove Leg

CONDITIONS The Operator has entered a Remove Leg command on a broadcast path.

CAUSES The cause may be due to the fact that the path section deimplementation has
failed (leg to be removed).

ACTIONS After having entered the command, perform an inspection at EML and NE layer
level.

4.2.1.7 Path: Failed to Remove Protection

CONDITIONS The Operator has entered a Remove Protection command on the path.

CAUSES The two possible causes are:

1) if the command has been entered through the With check option, the
failed attempt to remove the protection may be due to the fact that the path
is utilizing the spare route.

2) if the command has been entered through the No check option, the failed
attempt to remove the protection is due to the unsuccessful spare route
deimplementation.

ACTIONS In the second case above described, inspect the EML and NE layers.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 76 / 182

182
4.2.1.8 Path: Failed to Allocate

CONDITIONS The user enters a path allocation command.


not permitted without written authorization from Alcatel.

CAUSES Lack of resources.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

ACTIONS Execute a provisioning of the suitable resources.

NOTE For more detailed information refer to Chapter 5 PATH/TRAIL


ALLOCATION FAILURES
4.2.1.9 Path: Failed to Deallocate

CONDITIONS The user entered a Path: Deallocation command.

CAUSES Software latent errors.

ACTIONS Contact Alcatel Technical Assistance Center.

4.2.1.10 Path: Failed to Implement

CONDITIONS The user entered a Path Implementation command.

CAUSES The subordinate EML/NEs.

ACTIONS After having entered the command, inspect at EML and NE layer level.

4.2.1.11 Path: Failed to Deimplement

CONDITIONS The user entered a Path Deimplementation command.

CAUSES The subordinate EML/NEs.

ACTIONS After having entered the command, perform an inspection at EML and NE layer
level.

4.2.1.12 Path: Failed to Change SNCP Mode

CONDITIONS The Operator has previously entered a Set revertive/Set not revertive command
on the SNCP Operation mode attribute.

CAUSES The subordinate EML/NEs.

ACTIONS After having entered the command, perform an inspection at EML and NE layer
level.

4.2.1.13 Path: Failed to Align SNCPs

CONDITIONS The operation has been automatically launched by the system which aligns the
paths and trails whose attribute is SNCP status=unknown. It can be launched
in a manual mode by the Operator via command Synchronize Switch on
logically protected Path/trail/connInTopol.

CAUSES The problem is mainly at EML level or is a RMEML communication problem.


1AA 00014 0004 (9007) A4 ALICE 04.10

ACTIONS

1) Identify the protected connection that has failed.


2) In the Browser navigate up to the EML level.

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 77 / 182

182
4.2.1.14 Path: Failed to manage SNCPs

CONDITIONS The Operator has requested an SNCP management (Forced Switch


Main/Spare/Lockout.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
CAUSES The subordinate EML/NEs.

ACTIONS After having entered the command, perform an inspection at EML and NE layer
level.

4.2.1.15 Path: Failed to connect/disconnect

CONDITIONS The Operator has requested one of the following operations:

HO trail join

HO trail split

HO trail connect/disconnect

path connect/disconnect

CAUSES Data base misaligned

ACTIONS Contact Alcatel Technical Assistance Center.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 78 / 182

182
4.2.2 Diagnostic of the trail

The trail diagnostic concerns the following attributes:


not permitted without written authorization from Alcatel.

Alarm status
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Working status

4.2.2.1 Trail Alarm status

Regardless the trail alarm status, navigate the trail from the Alarm Counter Summary. See Paragr. 4.1

4.2.2.2 Trail working status

The Trail working status can be visualized on the Trail List.


All the statuses whose description contains the ing suffix are of the workinprogress type. Hence the
trail is in this status only for a certain period of time; the trail should assume the Normal condition when
a certain timeout has expired. This condition does not require the Operators intervention. He must
intervene if one of the following conditions occurs:

failed to Add Protection

failed to Release Resources

failed to Remove Protection

failed to Alllocate

failed to Deallocate

failed to Implement

failed to Deimplement

failed to configure

failed to Remove

failed to Align SNCPs

failed to manage SNCPs

failed to change SNCP Mode

failed to connect

failed to disconnect

failed to split

failed to join
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 79 / 182

182
4.2.2.3 Trail: Failed to Add Protection

CONDITIONS The trail involved is of the unprotected type. The Operator entered command
Add Protection.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
CAUSES Lack of resources, i.e. the spare resource corresponding to the main one is
not available.

ACTIONS Verify the resources (payload structure).

4.2.2.4 Trail: Failed to Release Resources

CONDITIONS The Operator has entered an Add Protection or Remove Protection command
on the trail.

CAUSES The cause is due to software latent errors.

ACTIONS Contact Alcatel Technical Assistance Center.

4.2.2.5 Trail: Failed to Remove Protection

CONDITIONS The Operator has entered a Remove Protection command on the path.

CAUSES The two possible causes are:

1) if the command has been entered through the With check option, the
failed attempt to remove the protection may be due to the fact that the trail
is utilizing the spare route.

2) if the command has been entered through the No check option, the failed
attempt to remove the protection is due to the unsuccessful spare route
deimplementation.

ACTIONS In the second case above described, inspect the EML and NE layers.

4.2.2.6 Trail: Failed to Allocate

CONDITIONS The user enters a trail allocation command.

CAUSES Lack of resources.

ACTIONS Execute a provisioning of the suitable resources.

NOTE For more detailed information refer to Chapter 5 PATH/TRAIL


ALLOCATION FAILURES

4.2.2.7 Trail: Failed to Deallocate

CONDITIONS The user entered a Path: Deallocation command.

CAUSES Software latent errors.


1AA 00014 0004 (9007) A4 ALICE 04.10

ACTIONS Contact Alcatel Technical Assistance Center.

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 80 / 182

182
4.2.2.8 Trail: Failed to Implement

CONDITIONS The user entered a Path Implementation command.


not permitted without written authorization from Alcatel.

CAUSES The subordinate EML/NEs.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

ACTIONS After having entered the command, inspect at EML and NE layer level.

4.2.2.9 Trail: Failed to Deimplement

CONDITIONS The user entered a Path Deimplementation command.

CAUSES The subordinate EML/NEs.

ACTIONS After having entered the command, perform an inspection at EML and NE layer
level.

4.2.2.10 Trail: Failed to Change SNCP Mode

CONDITIONS The Operator has previously entered a Set revertive/Set not revertive command
on the SNCP Operation mode attribute.

CAUSES The subordinate EML/NEs.

ACTIONS After having entered the command, perform an inspection at EML and NE layer
level.

4.2.2.11 Trail; Failed to Align SNCPs

CONDITIONS The operation has been automatically launched by the system which aligns the
paths and trails whose attribute is SNCP status=unknown. It can be launched
in a manual mode by the Operator via command Synchronize Switch on
logically protected Path/trail/connInTopol.

CAUSES The problem is mainly at EML level or is a RMEML communication problem.

ACTIONS

1) Identify the protected connection that has failed.


2) In the Browser navigate up to the EML level.

4.2.2.12 Trail: Failed to manage SNCPs

CONDITIONS The Operator has requested an SNCP management (Forced Switch


Main/Spare/Lockout.

CAUSES The subordinate EML/NEs.

ACTIONS After having entered the command, perform an inspection at EML and NE layer
level.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 81 / 182

182
4.2.2.13 Trail: Failed to configure

CONDITIONS The working state is Fail to Configure.

not permitted without written authorization from Alcatel.


CAUSES

All rights reserved. Passing on and copying of this


document, use and communication of its contents
1) Negative answer from EML: failed creation / connectivity object removal

2) Communication error received from EML. It may be due to a crash of EML.

3) Violation of the contraints on nodes (sometimes).

ACTIONS

1) Inspect the SH side in order to detect a possible SHRM disalignment

2) Verify that EML is running and reexecute the payload configuration

3) Perform again payload configuration. Consult Event Logger and


Additional Info. It may be necessary to launch the Consistency Download
operation on the EML involved.

4.2.2.14 Trail: Failed to connect/disconnect

CONDITIONS The trail working status is Failed to connect/disconnect.

CAUSES One or more of the paths belonging to this trail is in the Fail to
connect/disconnect status. This is due to data base misalignment.

ACTIONS Contact Alcatel Technical Assistance Center.

4.2.2.15 Trail: Failed to join/split

CONDITIONS The user launched the trail join/split operation.

CAUSES From the multiple reply of the Event Logger it is possible to determine:

1) The operation was interrupted during a connect/disconnect phase.

2) The operation was interrupted during a configuration phase.

ACTIONS

After having entered the command, perform an inspection at EML and NE layer
level.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 82 / 182

182
4.2.3 EML Domain Diagnostic

4.2.3.1 EML Alarm status


not permitted without written authorization from Alcatel.

Regardless the EML alarm status, navigate EML from the Alarm Counter Summary as described at
All rights reserved. Passing on and copying of this
document, use and communication of its contents

paragraph 4.1 .

As an alternative, from the Browser you can select the 1354RM icon and issue the command Actions:
Display Main Related items: EML Domain.

The displayed object is blue if cannot be reached; otherwise it is green colored.

Furthermore the following attributes are presented:

Alarms Aligned

Alarms alignment. It can be: Normal, Failed, In progress. This attribute reflects the consequences
of the Synchronize command launched by the Operator.

EML Domain Alignment

The conditions cited herebelow:

EML not reachable

EML Alarms Aligned false

EML Alarms Alignment Failed

EML Domain Alignment Failed

are described in the following.

4.2.3.2 EML Not Reachable

CONDITIONS blue EML= Not reachable

CAUSES

1) EML erroneously registered on the local registration file

2) EML processes not running

3) TCPIP problems

ACTIONS

1) Verify the EML id on RM and SH.

2) Restart EML

3) Check the workstation physical connections. The last possible choice is


rebooting the workstations.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 83 / 182

182
4.2.3.3 Alignment False/ Failed

CONDITIONS From Browser the attribute EML Alarms Aligned is false / the attribute EML
Alarms Alignment is Failed / the attribute EML Domain Alignment is Failed.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
CAUSES The possible causes are indicated in the Event Logger.

ACTIONS

1) From Browser enter command EML Domain: Synchronize / Synchronize


Alarms.

2) If the Synchronize Operation fails, display the events associated to the


EML Domain object from the Event Logger.
The affected object inspection involves the NEs/ports whose attribute is
Consistency status= normal. Moreover compare the same attributes
considering the values displayed on RM and those presented on SH/NE.
The Operator can now try to solve the problem at NE level utilizing the CT
(Craft Terminal) or the corresponding SH.
If the problem is not solved, launch Consistency Download on the NE
involved.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 84 / 182

182
4.2.4 NE Diagnostic

The NE attributes displayed in the browser window are:


not permitted without written authorization from Alcatel.

Alarm status
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Consistency status. for TSDIM ONLY.

The values to consider for diagnostic are:

Not aligned.

Failed to align

Consistency Mismatch

NE communication problems. for TSDIM ONLY.

The values to consider for diagnostic are:

NE unreachable.

Configuration Download state

The values to consider for diagnostic are:

Fail to Disable

Fail to Enable

EMLreachable. Refer to EML diagnostic.

NE DB modified by CT. ( for TSDIM ONLY). The CT has been automatically enabled because of
isolation problem and some modifications have been made by the CT operator.

Craft Terminal Access State. The possible values are:

CT access granted=CT enabled+CTconnected

CT access required=CT disabled+CTconnected

CT not connected enabled

CT access denied=CT disabled+CT not connected

NE not EML aligned. for SENIM ONLY

The values to consider for diagnostic are:

neNotEmlAligned_auditfailed

neNotEmlAligned_misaligned

Upload status. for TSDIM ONLY.

The values to consider for diagnostic are:


1AA 00014 0004 (9007) A4 ALICE 04.10

Not found=the NE is misaligned about physical objects, such as ports....

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 85 / 182

182
4.2.5 NE: Consistency Status=Not aligned ( TSDIM ONLY )

CONDITIONS From Browser it is displayed as an icon

not permitted without written authorization from Alcatel.


CAUSES The consistency download is probably disabled

All rights reserved. Passing on and copying of this


document, use and communication of its contents
ACTIONS Verify that the Consistency download is enabled. Then execute a consistency
download: ( i.e. global) toward the NE.

NOTICE THAT FOR TSD_IM NE THE RUN LEVEL CHANGE TO EXECUTE THE
CONSISTENCY DOWNLOAD IS NOT REQUIRED .

4.2.6 NE: Consistency Status=Failed to Align ( TSDIM ONLY )

CONDITIONS From Browser it is displayed as an icon

CAUSES Following an Audit operation a/some mismatches

ACTIONS Inspect the browser Error Log.

4.2.7 NE: Consistency Status=Consistency Mismatch ( TSDIM ONLY )

CONDITIONS From Browser it is displayed as an icon

CAUSES The NE is probably unreachable.

ACTIONS Inspect the browser Error Log and eventually execute a consistency download:
( i.e. global) toward the NE

NOTICE THAT FOR TSD_IM NE THE RUN LEVEL CHANGE TO EXECUTE THE
CONSISTENCY DOWNLOAD IS NOT REQUIRED .

4.2.8 NE: NE Communication Problems: NE unreachable

CONDITIONS From Browser it is displayed as an icon.

CAUSES The NE did not answer following a certain operation executed by RM. ( E.g. an
operation on a path, trail,...). The polling toward the NE is automatically started
and an automatic download is then executed.

ACTIONS Verify, by means of the Error Log the last operation executed on the involved
connectivity object of the NE.

4.2.9 NE Config. Download Status = fail to Disable / Enable

CONDITIONS From Browser it is displayed as a title

CAUSES Wrong answer from EML


1AA 00014 0004 (9007) A4 ALICE 04.10

ACTIONS Verify the EML layer

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 86 / 182

182
4.2.10 NE: NEnot EML Aligned_auditfailed / misaligned ( for SENIM ONLY )

CONDITIONS From Browser it is displayed as a title


not permitted without written authorization from Alcatel.

CAUSES
All rights reserved. Passing on and copying of this
document, use and communication of its contents

1) EML/NE erroneously registered

2) EML processes not running

3) TCPIP problems

ACTIONS

1) Verify EML id/NE address

2) Restart EML

3) Verify the workstation physical connections


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 87 / 182

182
4.2.11 Physical connection diagnostic

4.2.11.1 PhysCon Alarm status

not permitted without written authorization from Alcatel.


A physical connection failure is denoted by a color variation on the map.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
Regardless the physical connection alarm status, navigate the path from the Alarm Counter Summary as
described at paragraph 4.1 .

4.2.11.2 PhysCon Working status

The Physical Connection working status can be visualized on the Browser.

From Brower the diagnostic relevant attribute is Working State if it assumes the following values:

Failed to Configure

Failed to Implement

Failed to Remove

All the object statuses, the description of which contains suffix ing are of the workinprogress type and
as a consequence are temporary.

4.2.11.3 PhysCon Failed to Configure

CONDITIONS The working state is Fail to Configure. The user has previously started to modify
the payload.

CAUSES

1) Negative answer from EML: failed creation / connectivity object removal

2) Communication error received from EML. It may be due to a crash of EML.

3) Violation of the contraints on nodes (sometimes).

ACTIONS

1) Inspect the SH side in order to detect a possible SHRM disalignment

2) Verify that EML is running and reexecute the payload configuration

3) Perform again payload configuration. Consult Event Logger and


Additional Info. It may be necessary to launch the Consistency Download
operation on the EML involved.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 88 / 182

182
4.2.11.4 PhysCon Failed to Implement

CONDITIONS The user has previously launched the Physical Connection Implementation
operation.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

CAUSES

1) Negative answer from EML: connectivity object implementation failed.

2) Communication error

ACTIONS

1) Inspect the SH side in order to detect a possible SHRM disalignment

2) Verify that EML is running and launch again the Physical Connection
Implementation operation.

4.2.11.5 PhysCon Failed to Remove

CONDITIONS The user has entered a Delete command from MIB

CAUSES

1) Negative answer from EML: object removal failed.

2) Communication error

ACTIONS

1) Inspect the SH side in order to detect a possible SHRM disalignment

2) Verify that EML is running and launch again the Remove operation.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 89 / 182

182
4.2.12 SDH Port Diagnostic

The SDH ports are displayed from Browser by utilizing command NE: Display Related Items: SDH Ports.
The attribute involved are

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
Operational Status= disabled

Consistency status ( for SENIM ONLY). The values relevant to diagnostic are:

Not found. The board has been extracted. Objects assigned to RM belong to this board. Verify
alarms on related objects at RM and SH level.

Unknown. Communication problems at OS level.

Upload status ( for TSDIM ONLY). The values relevant to diagnostic are:

Not found. The board has been extracted. Objects assigned to RM belong to this board. Verify
alarms on related objects at RM and SH level.

Wrong Communication problems at OS level.

4.2.12.1 SDH port disabled

CONDITIONS The icon displayed from the browser is distinguished by a bar and there is an
alarm icon near it.

CAUSES Hardware or connected signals

ACTIONS Inspect the port at hardware level.

4.2.13 SDH port Consistency status ( for SENIM ONLY)=Not found

CONDITIONS This attribute is displayed by an icon in the browser

CAUSES The board has been extracted. Objects assigned to RM belong to this board.

ACTIONS IVerify alarms on related objects at RM and SH level.

4.2.14 SDH port Consistency status ( for SENIM ONLY)=Unknown

CONDITIONS This attribute is displayed by an icon in the browser

CAUSES Communication problems at OS level.

ACTIONS Verify the communication between OS. Refer to EML diagnostic.

4.2.15 SDH port Upload status ( for TSDIM ONLY)=Not found

CONDITIONS This attribute is displayed by an icon in the browser

CAUSES The board has been extracted. Objects assigned to RM belong to this board.

ACTIONS Verify alarms on related objects at RM and SH level.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 90 / 182

182
4.2.16 SDH port Upload status ( for TSDIM ONLY)=Wrong

CONDITIONS This attribute is displayed by an icon in the browser


not permitted without written authorization from Alcatel.

CAUSES Communication problems at OS level.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

ACTIONS Verify the communication between OS. Refer to EML diagnostic.

4.2.17 Routing link diagnostics

The routing link diagnostic is intended as a verification of the values of counters displayed from Browser
and listed herebelow:

Idle disabled. It informs on the idle, disabled link connections

Busy disabled. It informs on the busy, disabled link connections.

The actions required are:

display the disabled link connections

continue the link connection diagnostic procedure.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 91 / 182

182
4.2.18 Subnetwork diagnostic

The Subnetwork diagnostic concerns the Working status attribute when assumes the following values:

not permitted without written authorization from Alcatel.


failed to Implement

All rights reserved. Passing on and copying of this


document, use and communication of its contents
failed to Remove

4.2.18.1 Subnetwork: Failed to Implement

CONDITIONS The user entered a Subnetwork Implementation command.

CAUSES The subordinate EML/NEs.

ACTIONS After having entered the command perform an inspection at EML and NE layer
level.

4.2.18.2 Subnetwork: Failed to Remove

CONDITIONS The user entered a Subnetwork Delete from MIB command.

CAUSES The subordinate EML/NEs.

ACTIONS After having entered the command perform an inspection at EML and NE layer
level.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 92 / 182

182
4.2.19 Ring diagnostic

A failure along the ring is denoted by a color variation in the map. In the Browser the attribute taken into
consideration for diagnostic is Working State if it assumes the following values:
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Failed to Configure

Failed to Implement

Failed to Remove

All the statuses whose description contains the ing suffix are of the workinprogress type. Hence the
object is in this status only for a certain period of time.

4.2.19.1 Ring Failed to Configure

CONDITIONS The Working state is Failed to configure. The user has previously launched
the Payload Modify operation.

CAUSES

1) Negative answer from the NE: connectivity object creation/removal failed.

2) Communication error received from EML. It may be due to an EML crash.

3) Constraints violation on the nodes (in some cases).

ACTIONS

1) Inspect the SH side in order to detect a possible SHRM disalignment

2) Verify that EML is running and reexecute the payload configuration

3) Perform again payload configuration. Consult Event Logger and


Additional Info. It may be necessary to launch the Consistency Download
operation on the EML involved.

4.2.19.2 Ring Failed to Implement

CONDITIONS The user has previously launched the Ring Implementation operation.

CAUSES

1) Negative answer from the NE: connectivity object implementation failed.

2) Communication error.

ACTIONS

1) Inspect the SH side in order to detect a possible SHRM disalignment

2) Verify that EML is running and launch again the Implementation operation.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 93 / 182

182
4.2.19.3 Ring Failed to Remove

CONDITIONS The user has previously launched a Delete command from MIB.

not permitted without written authorization from Alcatel.


CAUSES

All rights reserved. Passing on and copying of this


document, use and communication of its contents
1) Negative answer from EML: object removal failed.

2) Communication error.

ACTIONS

1) Inspect the SH side in order to detect a possible SHRM disalignment.

2) Verify that EML is running and launch again the Remove operation.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 94 / 182

182
4.2.20 Node diagnostic

A node failure is denoted by a color variation in the map. In the Browser the attributes considered for
diagnostic are:
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

CT access status:

Working status:

Failed to Remove

Failed to Reset

Failed to Activate MS Spring

Reachable/Not reachable

4.2.20.1 Node Failed to Remove

CONDITIONS The user has previously launched a Delete Command from MIB.

CAUSES

1) Negative answer from EML: object removal failed.

2) Communication error.

ACTIONS

1) Inspect the SH side in order to detect a possible SHRM disalignment.

2) Verify that EML is running and launch again the Remove operation.

4.2.20.2 Node Failed to Reset

CONDITIONS The user has launched an Implementation command on the topology.


The command has been unsuccessful in that the NEs have not been reset.

CAUSES

1) Negative answer from EML.

2) Communication error.

ACTIONS

1) Inspect the SH side in order to detect a possible SHRM disalignment.

2) Verify that EML is running and launch again the Implementation operation.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 95 / 182

182
4.2.20.3 Node Failed to Activate MS spring

CONDITIONS The user has launched a Ring Implementation command.

not permitted without written authorization from Alcatel.


CAUSES

All rights reserved. Passing on and copying of this


document, use and communication of its contents
1) Negative answer from EML: connectivity object implementation failed.

2) Communication error.

ACTIONS

1) Inspect the SH side in order to detect a possible SHRM disalignment.

2) Verify that EML is running and launch again the Implementation operation.

4.2.20.4 Node Reachable/Not reachable

CONDITIONS blue NODE in the map= not reachable

CAUSES

1) NE address erroneously registered

2) EML processes not running

3) TCPIP problems

ACTIONS

1) Verify the NE addresses

2) Restart EML

3) Verify the workstation physical connections


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 96 / 182

182
4.2.21 Payload Configuration Diagnostic

4.2.21.1 Payload working status


not permitted without written authorization from Alcatel.

The user issued a payload modify command. The payload modify command can be executed on:
All rights reserved. Passing on and copying of this
document, use and communication of its contents

ET ( global configuration attribute=true )


PhysConn
HOlc
HOtrail

The working state of the above listed objects is Normal after the successful completion of the
configuration. The working state can be Fail to Configure for unsuccessful completion.

4.2.21.2 Fail to Configure

CONDITIONS One of the objects is Fail to Configure; this condition is propagated to its
superordinate object ( e.g. the ET is the superordinate and the PhysConn is the
subordinate ).

CAUSES The subordinate EML/NEs.

ACTIONS Inspect the browser Show additional information to display the cause of the
problem and execute one of the following actions:

1) Execute again the payload modify command.

2) In case of data misalignment perform the consistency download on the


affected objects.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 97 / 182

182
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 H
SC.6:MAINTENANCE

182
3AL 61259 AA AA
98 / 182
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
5 PATH/TRAIL ALLOCATION FAILURES

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

Path/Trail allocation failures are localized in the browser Path/Trail list. Selecting the involved path/trail and
clicking on the Show Failure Information Tool button, the Netscape browser application starts and
displays all information relevant to the failure.
The failure identification tool is based on Internet technologies, such as HTML, Java programming
language and HTTP protocol.
The allocation failure of a path or trail is detected by the user by looking at the transport to allocate, whose
configuration state goes to Failed to allocate. This state is displayed in the path or trail list.

The information provided in case of allocation failure are summarized in Figure 37. on page 99, namely:

OBSTACLES AND UNSATISFIED CONSTRAINTS are managed with the following structure:
OBSTACLES. This problem type is described by a problem description which helps in solving
the problem.
UNSATISFIED CONSTRAINTS. A Constraint List is provided, indicating the failed constraint(s)
OBSTACLES AND UNSATISFIED CONSTRAINTS. Both Problem description and Constraint
List are provided.
OTHER ERRORS are not described in detail. They indicate errors for which no further information
is provided.

For OBSTACLES AND UNSATISFIED CONSTRAINTS Problem description and Constraint List are
presented with the support of a simple graphical representation of the path/trail routing.
The tool usage is described in the following paragraphs.

ALLOCATION FAILURE

OTHER
OBSTACLES AND
ERRORS
UNSATISFIED CONSTRAINTS

OBSTACLES
UNSATISFIED &
OBSTACLES UNSATISFIED
CONSTRAINTS
CONSTRAINTS
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 37. Allocation failure management

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 99 / 182

182
5.2 Allocation failure diagnostic

5.2.1 Show Failure information

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
SEQUENCE

a) Select the involved path/trail and click on the Show Failure Information Tool button. This button
is also present in the path/trail routing view. The Netscape browser application starts and displays
the Netscape Path/Trail allocation failure window. See paragraph 5.2.3

SHOW FAILURE INFORMATION WORKING STATE=FAILED TO ALLOCATE

Figure 38. Path List


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 100 / 182

182
5.2.2 Obstacles and Unsatisfied Constraints

In case of Obstacles and Unsatisfied Constraints, the complete netscape view is provided.
not permitted without written authorization from Alcatel.

SEQUENCE
All rights reserved. Passing on and copying of this
document, use and communication of its contents

a) Select the involved path/trail and click on the Show Failure Information Tool button. This button is
also present in the path/trail routing view. The Netscape browser application starts and displays the
Netscape Path/Trail allocation failure window. See Figure 39. herebelow.

PROBLEM
WINDOW TITLE SUMMARY
FAILED OBJECT FRAME
FRAME

PROBLEM DETAIL FRAME


1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 39. Netscape Path/Trail allocation failure.

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 101 / 182

182
The Netscape Path/Trail allocation failure window shown in detail in Figure 41. on page 103 .
contains the following frames:

Window title: Netscape Path/Trail allocation failure.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
Failed object frame. It contains:

path/trail userlabel (name)

type ( point to point or broadcast )

failure date
failure time
no. of failed legs ( for broadcast paths only )

Figure 40. Failed Object frame

Problem Summary frame. See Figure 41. It contains:

frame title: PATH: path type or TRAIL

one row per each failed leg. The relevant leg number is shown in the lefthand column.

Each leg is described as:

End1 label (node+port) and End2 label (node+port)

PROBLEM TYPE, reference to the html Problem Detail frame. The following cases
are possible:

NO PROBLEMS. This string can be present only in correspondance to the Main


route when PROBLEMS are present on the Spare route

OBSTACLE PROBLEMS. The route cannot be completed because of a lack of


resources

CONSTRAINTS PROBLEMS. The route cannot be completed because some


1AA 00014 0004 (9007) A4 ALICE 04.10

constraints cannot be satisfied

OBSTACLE AND CONSTRAINTS PROBLEMS. Both obstacle and constraints


problems are present.

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 102 / 182

182
Two columns are displayable: MAIN (problems on the main route) and SPARE (problems
on the spare route, only for protected paths/trail)
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Figure 41. Netscape Path Trail allocation failure: problem summary frame.

b) At this point you can select the problem type, or in case of unsatisfied constraints you can select the
constraint list. See Figure 42. herebelow.

Figure 42. ProblemType and Constraint list

1) If you click on the Problem Type, reference to the html Problem Detail frame ( named
OBSTACLES and CONSTRAINTS PROBLEMS), the Problem Detail frame view will display the
selected leg. See Figure 45. on page 105.

The Problem Detail frame contains:

header ( upper lefthand side), constituted by:

Leg no. ,i.e. the selected leg number. This field is not present for point to point paths

ROUTE: End1 (node+port) and End2 (node+port)


1AA 00014 0004 (9007) A4 ALICE 04.10

route type: Main or Spare, followed by the PROBLEM TYPE

Failed routing display (lefthand side). It shows, per each row:

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 103 / 182

182
node icon (green triangle) with node name or link connection icon (yellow icon)
with link connection name: node A name node B name AU/TU pointer No.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
Figure 43. Route display components.

END 1 name and END 2 name. See Figure 44. on page 104.
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 44. END 1 / END 2 termination point names.

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 104 / 182

182
Problem Type ( yellow string which is the html reference to the Path/Trail allocation
failure description window of Figure 46. on page 106.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Figure 45. Problem Detail frame.

From the Problem Detail frame of Figure 45. select the problem type. The Path/Trail allocation failure
description window is displayed. See Figure 46. on page 106.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 105 / 182

182
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Figure 46. Netscape Path/Trail allocation failure description window.

The Path/Trail allocation failure description window contains:

Window title: Netscape Path/Trail allocation failure.

Failed object frame above described.

Problem Summary frame above described.

Generic Help on Allocation Failure. See Figure 47. on page 107. It contains a generic
description of the allocation failure.
A Main wiindow reload button is present in this frame,allowing the operator to display the main
window.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 106 / 182

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

Figure 47. Generic Help on allocation failure.

Problem description. See example in Figure 49. herebelow. It contains the detailed problem
description (Title and Explanation) of the problem and suggestions ( Hints ) how to solve the
problem.

Figure 48. Generic Help on allocation failure.

Figure 49. Example of problem description

The different problem types are:

NE Connection Problems

Explanation: The path/trail could not use a NE because it could not support a connection as
the one required.

Hints: If a constraint to use that NE has been set, try to remove it.

Infinite Cost

Explanation: The routing algorithm has found a route which uses a routing link with infinite cost
1AA 00014 0004 (9007) A4 ALICE 04.10

Hints: Change the cost of the related physical connection

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 107 / 182

182
No Free Link Connections

Explanation: The system tried to use a routing link without free link connections

not permitted without written authorization from Alcatel.


Hints: Deallocate some paths/trails which use the same routing link or change the payload

All rights reserved. Passing on and copying of this


document, use and communication of its contents
configuration in order to create new link connections at the proper rate.

Improper Payload Configuration

Explanation: No one hop routing link exists related to a physical connection. This can be due
to an improper payload configuration or to the presence of a user defined HO trail

Hints: Try to change the payload configuration or split the HO trail.

Unsatisfied Constraints

Explanation: One or more of the constraints given to the path/trail cannot be satisfied

Hints: The only way to allocate the path/trail is to remove/modify some constraints

The left hand side frame contains the Problem menu list. Each menu item, if selected, will display its
problem explanation and some hints to solve it.

Figure 50. Problem menu list

Figure 51. and Figure 52. herebelow display an example of protected path allocation failure.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 108 / 182

182
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
01

957.130.872 H
MAIN ROUTE

SC.6:MAINTENANCE
SPARE ROUTE

Figure 51. Example of display of a protected path

182
3AL 61259 AA AA
109 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 H
SC.6:MAINTENANCE
SPARE

Figure 52. Example of display of a protected path

182
3AL 61259 AA AA
110 / 182
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
2) If you click on the Constraint List icon, as per Figure 42. on page 103, the Constrain List is
presented. See Figure 53. on page 111. Per each leg its Constraint List can be displayed in case
of Unsatisfied Constraints.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Figure 53. Constraint List

An example of Constraint List is shown in Figure 54. on page 112.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 111 / 182

182
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Figure 54. Processed Constraint List.

This graphical table contains one row per each constraint. The table is constituted by : (see Figure 54. )

title: PROCESSED CONSTRAINTS LIST ( route ), where route is equal to Main or Spare

four columns, namely:

satisfied/unsatisfied constraint. The green semaphore icon means that the constraint is
satisfied. The red semaphore icon means that the constraint is not satisfied. In the latter case
the deletion of this constraint will probably solve the allocation problem.

constraint usage in the main route. The oneway icon means USE while the no entry icon
means NOT USE.

constraint usage in the spare route. The oneway icon means USE while the no entry icon
means NOT USE.
1AA 00014 0004 (9007) A4 ALICE 04.10

topology used as constraint. It includes the icon and the userlabel of the topological object

An example of interpretation of some rows is given in Figure 55. on page 113

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 112 / 182

182
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
01

957.130.872 H
SC.6:MAINTENANCE

182
3AL 61259 AA AA
Figure 55. Examples of interpretation of the Constraint list rows.

113 / 182
5.2.3 Other errors

OTHER ERRORS are not described in detail. They indicate errors for which no other information is
provided.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
An example of other error display is shown in Figure 56. herebelow.

OTHER ERROR

Figure 56. Example of OTHER ERRROR display


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 114 / 182

182
6 DIAGNOSTIC OF THE NPE RING

6.1 User Presentation


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

The protection status reporting window displays the current status of the MS SPring, in terms of:
triggers =external commands and/or failure/degrade conditions. The nodes whose triggers are being
served are named served nodes. A served node has at least one trigger served and may have some
pending triggers.
the reaction of the ring to those triggers, namely what triggers are being served, and which ones are
pending. (waiting to be served, either because they are at lower priority, or there are specific protocol
rules). The nodes that have no triggers or only pending ones are called intermediate nodes.

N.B. The protection status reporting screen is neither intended to display the status of the K1K2
signaling, nor the status of the physical switches. With the 2F MS SP ring application, the
bridge&switch at multiplex section level always occurs at served nodes, whereas protection
channels passthrough is made by intermediate nodes. With the 4F MS SP ring application,
bridge&switch at AU4 level may take place at whatsoever node, depending on the distribution
of traffic.

It should be noted that according to the MS SP ring protocol rules any of the following scenarios may occur:

no trigger is present, no protocol request (namely, K1K2 code other than noRequest) is signaled on
the ring;

1 trigger is present, 1 protocol request is signaled and served;

N (>1) triggers are present, N protocol requests are signaled, only 1 is served (higher priority);

N triggers are present, N protocol requests are signaled and served (same priority);

N triggers are present, N protocol requests are signaled, none is served (same priority, but not
allowed to coexist).

1 trigger is present and served, no protocol request is signaled (1);

M (>1) triggers are present, N (<M) protocol requests are signaled, only 1 is served (higher priority);

M triggers are present, N (<M) protocol requests are signaled and served (same priority);

M triggers are present, N (<M) protocol requests are signaled, none is served (same priority, but not
allowed to coexist).
(1) The Lockout of Working channels commands make the scenario even more complicated, as those

commands are not signaled but are actually served, in the sense that they influence the behavior of
the node to which they are addressed.

The window can display up to 16 node icons (see Figure 57. )


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 115 / 182

182
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 H
SC.6:MAINTENANCE
Figure 57. 4 fibre MS SP reporting screen

182
3AL 61259 AA AA
116 / 182
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.1 MidProtocol Role ( NODE CONDITION ) attribute

Two node icons are associated to the values of the ConfigurationState attribute od the
MSSPRingProtectionBlock MOC:
not permitted without written authorization from Alcatel.

ConfigurationState = virtual, icon


All rights reserved. Passing on and copying of this
document, use and communication of its contents

ConfigurationState = enabled, icon


ConfigurationState = active, icon

When the ConfigurationState is virtual for a node (because the relevant TFEP fails) an allgrey icon
(the virtual node icon) is displayed as a placeholder for that node, but no additional information can be
displayed on top of that icon about that node (see Figure 58. ).

Figure 58. ConfigurationState = virtual icon

The virtual node icon being displayed means that the MSSPRING is not configured at the node.

When the ConfigurationState is either enabled or active for a node, the node icon shown in
Figure 60. is displayed. Such an icon then acts as a background for all the icons associated to the
attributes of the MSSPRingProtectionBlock MOC.

The node icon always reports the actual condition of the node in terms of the protocol role the node
is playing to react to the MSSPRING triggers, and the external commands being stored to the
node. If the condition required by the RM and the actual node condition do not match, the not
aligned indication is displayed along with the node icon.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 117 / 182

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

topology implementation
topology deimplementation

MSSPRING activation
enabled active

MSSPRING deactivation

Figure 59. ConfigurationState diagram

The following table describes the rationale that drives the displayof the various icons according to the
ConfigurationState state diagram (see Figure 59. ).
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 118 / 182

182
Table 3. ConfigurationState, node conditions, and RM display.

ConfigurationState node condition displayed icons operation


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

virtual MSSPRING not con- virtual node icon topology implementa-


figured tion failure (TFEP
stalled)
active MSSPRING not con- virtual node icon topology implementa-
figured tion failure (TSDIM es-
tablish failed)
active ? node icon +MidProto- node unreachable
colRole = unknown
icon on top
enabled enabled node icon +MidProto- MSSPRING deactiva-
colRole = standby tion successful
icon on top
enabled active node icon + other icons MSSPRING deactiva-
on top to show protocol tion failure
role and stored com-
mands +
not aligned indication
active active node icon + topology implementa-
other icons on top to tion successful or MS
show protocol role and SPRING activation suc-
stored commands cessful
active enabled node icon + topology implementa-
MidProtocolRole = tion failure (TSDIM
standby icon on top + populate failed) or
not aligned indication MSSPRING activation
failure

The node icon is a rectangle plus arrows that represent the fiber optics to connect the nodes to each other.

Plus, the node icon features a number of rectangles (see Figure 60. ) to hold icons associated to all the
attributes of the MSSPRingProtectionBlock MOC:
the icon for the MidProtocolRole attribute;
the icon for the WestProtocolRole attribute;
the icon for the EastProtectionRole attribute;
the set of six icons for the WestRingActiveCondition, WestSpanActiveCondition,
WestRingPendingCommand, WestSpanPendingCommand, WestLockoutWorkingRing, and
WestLockoutWorkingSpan on the West side of the node icon;
the set of six icons for the EastRingActiveCondition, EastSpanActiveCondition,
EastRingPendingCommand, EastSpanPendingCommand, EastLockoutWorkingRing, and
EastLockoutWorkingSpan on the East side of the node icon;
the icon for the FailureOfProtocol to be placed outside the node icon next the bottom left and
righthand corner;
1AA 00014 0004 (9007) A4 ALICE 04.10

The reason for providing each node icon with 6 icons for the local commands comes from the combinations
of active and pending commands that are allowed to coexist at each node.

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 119 / 182

182
6.1.2 MidProtocol Role ( NODE CONDITION) attribute

The central rectangle with a black triangle in it representing the NE is the place where the values of
the MidProtocolRole are displayed (see Figure 61. ).

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
When MidProtocolRole = idle and all other attributes are = null, no additional icon is placed on top of
the node icon, so that all commandrelated rectangles still look gray to show that no external command
is stored to the node, namely either active or pending and the rectangles on the side of the central triangle
both looking green, to mean that both the East and WestProtocolRole are in an idle condition, namely
the node is neither serving any trigger nor acknowledging a trigger to be served by some other node on
the ring.

Whenever the MidProtocolRole attribute changes from idle to another value, the icon associated to that
new value is displayed on top of the central rectangle with the black triangle in it.

Whenever either the East and WestProtocolRole, or both, change to a value different from null, the icon
associated to the new value (see Figure 62. and Figure 63. ) are displayed on top of the designated green
rectangle.

Whenever any of the external commands is given to and stored by a node to go either active or pending,
the icon associated to the new value (see Figure 67. through Figure 73. ) are displayed on top of the
designated gray rectangle.

west ring pending command east ring pending command


east span pending command
west span pending command

working fibers
east protocol role
east ring active condition
east span active condition
east Lockout W ring status
protection fibers
east Lockout W span status

west protocol role

west span active condition


west ring active condition
west Lockout W span status
east failure ofprotocol
west Lockout W ring status

Figure 60. ConfigurationState = enabled/active icon


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 120 / 182

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

no icon

Figure 61. MidProtocolRole ( NODE CONDITION ) icons

6.1.2.1 West and EastProtocolRole attributes

null tailHeadRing tailHeadSpan protUnav (EXT)thRingProtUnav


(interruption Ring) (interruption Span)

no icon

Figure 62. WestProtocolRole possible icons.

null tailHeadRing tailHeadSpan protUnav thRingProtUnav

no icon

Figure 63. EastProtocolRole possible icons.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 121 / 182

182
6.1.3 Allowed combinations of East, West, and MidProtocolRole

The allowed combinations of values for the WestProtocolRole, MidProtocolRole, and EastProtocolRole
are the following:

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
the node received no external command and detected no failure/degrade:

null null null

the node is serving an external commandring or failure/degradering that involves its West side:
tailHeadRing

tailHead Ring null null

the node is serving an external commandspan or failure/degradespan that involves its West side:

tailHead Span null null

the node is serving an external commandring or failure/degradering that involves its East side:

null null tailHead Ring

the node is serving an external commandspan or failure/degradespan that involves its East side:

null null tailHeadSpan

either the node received/detected nothing and some other node is serving an external command or
the node received/detected a trigger but some other node is serving another trigger of higher priority:

null intermediate null

the node either received a commandspan or detected a failure/degradespan on both sides and
served both:

tailHeadSpan null tailHeadSpan


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 122 / 182

182
the protection MS on the West side of the node is unavailable or locked out:

protUnav null null


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

the protection MS on the East side of the node is unavailable:

null null protUnav

the protection MS on both sides of the node is unavailable or locked out:

protUnav null protUnav

the node is serving an external commandring or failure/degradering that involves its West side,
protection MS on the West side is unavailable or locked out:

tailHeadRingProtUnav null null

the node is serving an external commandspan or failure/degradespan that involves its West side,
protection MS on the East side is unavailable or locked out:

tailHeadSpan null protUnav

the node is serving an external commandring or failure/degradering that involves its East side,
protection MS on the East side is unavailable or locked out:

null null tailHeadRingProtUnav

the node is serving an external commandspan or failure/degradespan that involves its East side,
protection MS on the West side is unavailable or locked out:

protUnav null tailHead Span


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 123 / 182

182
6.1.3.1 Protocol Failure attribute

This attribute has icons (see Figure 64. and Figure 65. ) associated to each of its values to represent the
various failure conditions that may affect the K protocol. When a node detects a protocol failure in the

not permitted without written authorization from Alcatel.


incoming K bytes on a given side, the relevant icon is displayed.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
null defaultKBytes

no icon

Figure 64. East failure Of Protocol

null defaultKBytes

no icon

Figure 65. West failure Of Protocol


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 124 / 182

182
6.1.4 Ring Active Condition attributes

Each of these values is represented on the screen by an icon (see Figure 66. and Figure 67. ) located at
the designated position for this attribute, and pointing at the side of the node to which the command is
not permitted without written authorization from Alcatel.

addressed. Each value other than null indicated either a command (forced, manual) given by the manager
All rights reserved. Passing on and copying of this
document, use and communication of its contents

or a condition (wtrRunning) automatically forced by the NE: each of those can be removed by the manager
by the appropriate release command. Specifically, a release WTR command forces the WTR counter
inside the NE to immediate expiration.

Manual and Forced switch are represented by same symbol on different color, yellow and red respectively.

manual switch ring forced switch ring null wtr ring

no icon

Figure 66. East ring active condition

manual switch ring forced switch ring null wtr ring

no icon

Figure 67. West ring active condition


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 125 / 182

182
6.1.5 Span Active Condition attributes

Each of these values is represented on the screen by an icon (see Figure 68. and Figure 69. ) located at
the designated position for this attribute. Each value other than null indicated either a command (forced,

not permitted without written authorization from Alcatel.


manual, lockoutProtection) given by the manager or a condition (wtrRunning) automatically forced by the

All rights reserved. Passing on and copying of this


document, use and communication of its contents
NE: each of those can be removed by the manager by the appropriate release command. Specifically, a
release WTR command forces the WTR counter inside the NE to immediate expiration.

Manual and Forced switch are represented by same symbol on different color, yellow and red respectively.

manual switch span forced switch span null wtr span

no icon

Figure 68. East span active condition

manual switch span forced switch span null wtr span

no icon

Figure 69. West span active condition


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 126 / 182

182
6.1.6 Ring Pending Command

Each of these values is represented on the screen by an icon (see figure below) located at the designated
position for this attribute. Each value other than null indicates a command given by the manager and that
not permitted without written authorization from Alcatel.

can be removed by the manager by the appropriate release command.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Manual and Forced switch are represented by same symbol on different color, yellow and red respectively.

manual switch ring forced switch ring null

no icon

Figure 70. East ring pending command

manual switch ring forced switch ring null

no icon

Figure 71. West ring pending command


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 127 / 182

182
6.1.7 Span Pending Command

Each of these values is represented on the screen by an icon (see figure below) located at the designated
position for this attribute, and pointing at the side of the node to which the command is addressed. Each

not permitted without written authorization from Alcatel.


value other than null indicates a command given by the manager and that can be removed by the manager

All rights reserved. Passing on and copying of this


document, use and communication of its contents
by the appropriate release command.

Manual and Forced switch are represented by same symbol on different color, yellow and red respectively.

manual switch span forced switch span null

no icon

Figure 72. East span pending command

manual switch span forced switch span null

no icon

Figure 73. West span pending command


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 128 / 182

182
6.1.8 Lockout Working Ring attributes ( not implemented in this release )

null Lockout working ring


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

no icon

Figure 74. East Lockout Working Ring

null Lockout working ring

no icon

Figure 75. West Lockout Working ring


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 129 / 182

182
6.1.9 Lockout Working Span attributes ( not implemented in this version release )

null Lockout working span

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
no icon

Figure 76. East Lockout Working Span

null Lockout working span

no icon

Figure 77. West Lockout Working Span


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 130 / 182

182
6.1.10 Inhibition chain

The possible requests are listed herebelow in decreasing priority.


not permitted without written authorization from Alcatel.

LPS (Lockout Protection Span), SFP (Signal Fail Protection), LOWR (Lockout Working Ring),
All rights reserved. Passing on and copying of this
document, use and communication of its contents

LOWS (Lockout Working Span); LOWR, LOWS LPS are not implemented.

FSS (Forced Switch Span)

FSR (Forced Switch Ring)

SFS (Signal Fail Span)

SFR (Signal Fail Ring)

SDP (Signal Degrade Protection)

SDS (Signal Degrade Span)

SDR (Signal Degrade Ring)

MSS (Manual Switch Span)

MSR (Manual Switch Ring)

WTR (Wait to Restore Time)

EXER not implemented

EXCEPTIONS

Two MSS (Manual Switch Span): no action

SFR and FSR : no action

Two SDR : no action


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 131 / 182

182
6.1.11 Scenarios

This paragraph describes various ring scenarios , as shown in the graphical interface.

not permitted without written authorization from Alcatel.


6.1.11.1 Bidirectional Signal Fail / Ring Scenario

All rights reserved. Passing on and copying of this


document, use and communication of its contents
DESCRIPTION

A Bidirectional Signal Fail / Ring is present on AB span. The relevant aggregate boards are affected
by LOS alarm.

SERVED REQUESTS DISPLAY

Bidirectional Signal Fail / Ring on AB span (indicated by RING INTERRUPTION (tailHeadRing) icons
on AB span)

OPERATION

The traffic affected by the failure is recovered on protection channels away from the failure. All LP traffic
paths whose channels are needed to recover HP traffic are preempted.

HP traffic is maintained. LP traffic paths whose channels are needed to recover HP traffic is lost.

REPAIR ACTION

Two alternatives are possible:

a) First execute the repair of the main span. HP traffic reverts to the main span while LP traffic still is
lost.

1) Click on the alarm icon displayed on the main span. The alarm detail window is presented, giving
the information needed to repair the span.

b) First execute the repair of the spare span, so moving to the Span switch scenario.The LP traffic not
overlapping HP traffic is restored.

1) Click on the alarm icon displayed on the spare span. The alarm detail window is presented,
giving the information needed to repair the span.

The scenario after the repair of the affected spans is described at paragraph 6.1.11.2.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 132 / 182

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

Alarm icon

A B

Ring Interruption (tailHeadRing)

Node Condition=intermediate
(not directly affected by the fault)

Node Condition=Idle

Figure 78. Bidirectional Signal Fail / Ring


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 133 / 182

182
6.1.11.2 Bidirectional Signal Fail / Ring cleared .WTR

DESCRIPTION

not permitted without written authorization from Alcatel.


The bidirectional Signal Fail / Ring on AB span is cleared as a consequence of a repair action. The last

All rights reserved. Passing on and copying of this


document, use and communication of its contents
node detecting the signal failure clear starts the WTR ( wait to restore time )

SERVED REQUESTS DISPLAY

Bidirectional Signal Fail / Ring on AB span (indicated by RING INTERRUPTION (tailHeadRing) icons
on AB span) is still displayed.

The east ring active condition icon reports WTRrunning.

OPERATION

All nodes dropping/inserting HP traffic that was affected by the failure still recover it on protection channels
away from the failure.

All LPtraffic paths whose channels are needed to recover HP traffic are still preempted.

Node A (the last detecting the signal failure clear) is running

REPAIR ACTION

The WTR timer may be forced to expiration by RM via Clear WTR command. ( not implemented in this
version )

WTR

Figure 79. Bidirectional Signal Fail / Ring cleared .WTR


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 134 / 182

182
6.1.11.3 Double Bidirectional Signal Fail / Ring

DESCRIPTION
not permitted without written authorization from Alcatel.

Bidirectional Signal Fail / Ring on AB span.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Bidirectional Signal Fail / Ring on DE span.

SERVED REQUESTS DISPLAY

Bidirectional Signal Fail / Ring on AB span (indicated by RING INTERRUPTION (tailHeadRing) icons

Bidirectional Signal Fail / Ring on DE span (indicated by RING INTERRUPTION (tailHeadRing) icons

OPERATION

All nodes dropping/inserting HP traffic that was affected by the failure still recover it on protection channels
away from the failure.

HP traffic that was affected by either failure is not recovered

All LPtraffic paths whose channels are needed to recover HP traffic are preempted.

REPAIR ACTION

The scenario after the repair of one of the two faults is described at paragraph 6.1.11.1.

It is suggested the repair of the main span first.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 135 / 182

182
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01
A

957.130.872 H
SC.6:MAINTENANCE
B

Ring Interruption (tailHeadRing)


Alarm icon

Node Condition=Idle
C

Figure 80. Double Bidirectional Signal Fail / Ring

182
3AL 61259 AA AA
D

136 / 182
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.11.4 Forced Switch Ring

DESCRIPTION
not permitted without written authorization from Alcatel.

A Forced Switch / Ring command is entered to A/East for AB span.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

SERVED REQUESTS DISPLAY

Forced Switch / Ring command (indicated by tailHeadRing (RING INTERRUPTION) icons facing the AB
span, and the FS/R icon pointing to the relevant node and side. This FS/R icon means that a command
is being served and may be removed).

OPERATION

All nodes dropping/inserting HP traffic that is traversing the addressed span is recovered on protection
channels away from that span (just like an SF/R affecting the same span).

All LPtraffic paths whose channels are needed to recover HP traffic are preempted.

REPAIR ACTION

This command is used in the Add/Remove Node procedures.

B
A
Forced Switch Ring East

Figure 81. Forced Switch / Ring


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 137 / 182

182
6.1.11.5 Double Forced Switch / Ring to different nodes, node isolated

DESCRIPTION

not permitted without written authorization from Alcatel.


Forced Switch / Ring command given to A/East for AB span and Forced Switch / Ring command given

All rights reserved. Passing on and copying of this


document, use and communication of its contents
to C/West for BC span.
This scenario can be established to put node B in local maintenance condition.

SERVED REQUESTS DISPLAY

Forced Switch / Ring command given to A/East (indicated by tailHeadRing icon facing the AB span, and
the FS/R icon . FS/R icon means that a command is being served and may be removed).

Forced Switch / Ring command given to C/West (indicated by tailHeadRing icon facing the BC span, and
the FS/R icon . FS/R icon means that a command is being served and may be removed).

OPERATION

Node B is isolated, as the two Force Ring commands partition the ring into two segment, [B] alone and
[C, D, A].

HP traffic that is traversing both the involved spans is recovered on protection channels away from those
spans.

HP traffic that is traversing one of the involved spans is not recovered.

All LP paths whose channels are needed to recover HP traffic are preempted.

REPAIR ACTION

After the completion of the local maintenance condition of node B, enter the Release Forced Switch / Ring
on nodes A and C.

A B D
C
Forced Switch Ring East Forced Switch Ring West
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 82. Double Forced Switch / Ring to different nodes, node isolated

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 138 / 182

182
6.1.11.6 Double signal Fail / ring, node isolated

DESCRIPTION
not permitted without written authorization from Alcatel.

Bidirectional Signal Fail / Ring on AB span.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Bidirectional Signal Fail / Ring on BC span.

SERVED REQUESTS DISPLAY

Bidirectional Signal Fail / Ring on AB span (indicated by tailHeadRing icons facing both the AB span).

Bidirectional Signal Fail / Ring on BC span (indicated by tailHeadRing icons facing both the BC span).

OPERATION

Node B is isolated, as the two Force Ring commands partition the ring into two segment, [B] alone and
[C, D, A].

HP traffic that is traversing both the involved spans is recovered on protection channels away from those
spans.

HP traffic that is traversing one of the involved spans is not recovered.

All LP paths whose channels are needed to recover HP traffic are preempted.

REPAIR ACTION

a) Execute the repair of the main span. HP traffic reverts to the main span while LP traffic still is lost.

1) Click on the alarm icon displayed on the main span. The alarm detail window is presented, giving
the information needed to repair the span.

Figure 83. Double signal Fail / ring, node isolated

It is suggested the repair of the main span first.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 139 / 182

182
6.1.11.7 Forced Switch / Span

DESCRIPTION

not permitted without written authorization from Alcatel.


A Forced Switch / Span command is entered to B/West for AB span.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
This command is used when the AB main span requires a local maintenance.

SERVED REQUESTS DISPLAY

Forced Switch / Span command (indicated by tailHeadSpan icons facing the AB span, and the FS/S
icon pointing to the relevant node and side).

OPERATION

Nodes A and B recover on the protection channels the traffic traversing the involved span (just like an SF/S
affecting the same span). The only channels that are bridged and switched by A and B are those that
actually carry traffic over AB.

All LPtraffic paths whose channels are needed to recover HP traffic are preempted.

REPAIR ACTION

After the completion of AB main span local maintenance the Release Switch Span West can be entered.

Span Switch
Force Switch Span West

Figure 84. Forced Switch / Span


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 140 / 182

182
6.1.11.8 Double Manual Switch / Ring pending

DESCRIPTION
not permitted without written authorization from Alcatel.

Manual Switch / Ring command given to D/West for DE span


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Manual Switch / Ring command given to B/West for BA span.

SERVED REQUESTS DISPLAY

Manual Switch Ring icons.

OPERATION

No action. Manual Switch / ring commands preempt each other. Nevertheless, they are stored to B and
D and need to be explicitly cleared by the manager. As one is cleared, the other becomes active.

REPAIR ACTION

Release Manual Switch Ring.

Manual Switch Ring

Figure 85. Double Manual Switch / Ring pending


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 141 / 182

182
6.1.11.9 Double Manual Switch / Ring pending

DESCRIPTION

not permitted without written authorization from Alcatel.


Bidirectional Signal Fail / Ring on AB span.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
Forced Switch / Ring command given to D/West for DE span.

SERVED REQUESTS DISPLAY

Forced Switch Ring pending icon on D node.

OPERATION

Forced Switch / Ring command is pending (actually it is higher priority than the SF/R, but it cannot be
served because the protocol fails to complete on the long path).

REPAIR ACTION

Release Forced Switch Ring.

Forced Switch Ring pending

Figure 86. Signal Fail / Ring pending, Forced Switch / Ring pending
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 142 / 182

182
6.1.11.10 Double Manual Switch / Ring pending

DESCRIPTION
not permitted without written authorization from Alcatel.

Bidirectional Signal Fail on Protection on BA span.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Bidirectional Signal Fail / Ring on DE span.

It is a double fault service affecting. The fault between A and B nodes ( SFP ) has priority greater than
the fault between E and D nodes ( SFR)

SERVED REQUESTS DISPLAY

Bidirectional Signal Fail on Protection (indicated by protection unavailable icons facing the AB span)

OPERATION

Bidirectional Signal Fail / Ring is pending (it is lower priority than the Signal Fail /Span), affected traffic
is not recovered, all LPtraffic remains.

Bidirectional Signal Fail on Protection prevents the use of the protection channels on the AB span.

Protection Unavailable

Figure 87. Signal Fail Span, Signal Fail / Ring pending


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 143 / 182

182
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 H
SC.6:MAINTENANCE

182
3AL 61259 AA AA
144 / 182
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
7 LOGGER

The event logger displays the current events and the list of the events which have been stored in the log
file.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

The Event Log dialog box is shown in Figure 88.

Figure 88. Event Log filter


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 145 / 182

182
This box allows the user to select the following parameters:

Class Type. The operator can choose to display events relative to:

not permitted without written authorization from Alcatel.


all classes (wildcard)

All rights reserved. Passing on and copying of this


document, use and communication of its contents
path
emlDomain
ne
port
physicalConn
ntw
sbn
et
node
lc
trail
connInTopol
nap

Event Type. The operator can select among the following types:

all types (wildcard)


attributeValueChange
stateChange
objectCreation
objectDeletion

Log Type. Two options are available:

Immediate. The report window will work as a virtual printer ( FIFO ), displaying messages in real
time.
From Log File. The Report will contain data extracted from the historical event log file of HPOV.

Start Time/End Time, to be specified for searching from Log File.

Object_Instance. From Browser drag the object(s) whose event log is required and drop into this
area. A wrongly dropped object should be deleted by means of the Delete popup option. The
presence of objects in this area automatically makes not meaningfull the content of the above
described ClassType box.

The window contains four toolbuttons;

Cancel, to cancel the operation and close the window.

Apply, to start the event log process.

Cancel Get, to abort the data retrieval.

Users info
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 146 / 182

182
EVENT LOG

The Event Log dialog box is shown in Figure 89.


not permitted without written authorization from Alcatel.

The pulldown menu line contains items File and Actions.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Item File contains the following options:

Open, to start a read operation on an ASCII file. This file is selected by the user by means of
a file filter.

Save as... to save on file the content of the Event Log.

Print all to print the Event Log content on the default printer.

Print Selected to print part of the Event Log content on the default printer.

Item Actions contains the only option Font.

still closed.

An example of event log is shown in Figure 89.

Figure 89. Event Log


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 147 / 182

182
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 H
SC.6:MAINTENANCE

182
3AL 61259 AA AA
148 / 182
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
8 NMLEML CONSISTENCY CHECKS

In the following are described the consistency audit and consistency download activities that can be
executed either on a single Node or the whole EML DOMAIN.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

8.1 NMLEML Consistency Checks ( SENIM )

8.1.1 Consistency audit ( SENIM )

The Consistency Audit activity verifies the misalignments between the EML and the NML. This
activity does not perform any corrective actions.

It is suggested to always execute the Download Disable command before entering command Audit
and in all the following suspected cases:

1) SH rejects a operation (implementation, payload configuration, ...) on an object that is unknown


to SH. This problem is solved through an Event Logger examination.

2) The Communication Infrastructure timeout (C.I.) triggers.

3) The RM database has been restored.

4) SH has been restarted.

5) During an RM operation (ex. Payload Configuration), a shutdown of the agent involved has
occurred.

Perform the following operations:

a) From the Browser execute Configure Download:Disable on the involved EML/NE.

b) Activate the Network Consistency Agent.

c) On the involved EML/NE execute the Consistency Audit popup menu.

The available options are:

1) Global

2) PDHPort NAP

3) SDHPort MStp

4) at HO/LO level

The option Global causes the execution of all the remaining checks 2 ) thru 4 ).

The reporting of the operations is performed using multiple messages in order to display the current state
of the ongoing operations (number of not aligned objects, etc... Otherwise from the Browser can be
displayed the misaligned objects (tps) by selecting the Node and executing a Get related items: Not
consistent tps and connections in topology command.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 149 / 182

182
8.1.2 Consistency download ( SENIM )

The Consistency Download activity verifies the misalignments between EML and NML and performs
corrective actions in that the NML database is the reference.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
a) Execute a Download Disable command

b) Activate the Network Consistency Agent ( Run Level=Consistency )

c) On the involved EML/NE execute the Consistency Download popup menu.

The available options are:

1) Global

2) PDHPort NAP

3) SDHPort MStp

4) at HO/LO level

5) Performance Monitoring (Only for Download)

The option Global causes the execution of all the remaining checks 2 ) thru 4 ).

The reporting of the operations is performed using multiple messages in order to display the current state
of the ongoing operations (number of not aligned objects, etc... Otherwise from the Browser can be
displayed the misaligned objects (tps).

d) Set Run Level=Full Functionality

e) Set Configure Download: Enable on all the NEs/EMLs.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 150 / 182

182
8.2 NMLEML Consistency Checks ( TSDIM )

With TSDIM, RM interacts directly with the NEs and directly manages alignment, consistency, isolation
and download enable / disable.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

8.2.1 Download disable management ( TSDIM )


The operator is able to specify for TSDIM NEs the download disabled / enabled mode (download enabled
mode is the default condition)

When a NE is in download disabled mode, no information exchange is performed between RM and


the NE and all changes are buffered in the RM MIB.

Objects in the RM MIB that, as a consequence of the download disable mode, are not aligned with the NE,
are marked with the value of the consistency status attribute (not aligned).

Nodes that have at least one not aligned object are put in a not aligned state.

When the download disabled mode is removed and the NE is reachable, RM data are downloaded to NEs.

If the download disabled mode is removed and the NE is not reachable, the operation is rejected.
If problems are detected during the download, the NE is put in isolation mode.

During the downloading activity on a given NE, all concurrent operations requested by RM operator and
involving the same NE, will wait for download completion.

The maximum time to wait is configured as a global RM value.


When the timeout condition is detected before download completion, the operator requested operation
fails and a retry must be executed.

8.2.2 Ne isolation detection and recovery ( TSDIM )


RM is able to detect not reachable NEs as a consequence both of problems in the EML, in the DCN or
in the NE.

When a NE is in download enabled mode and is not reachable, RM behavior is similar to the one
described for the download disable mode.

Elementary alarms are correlated to the impacted transport entity allowing a better identification of the
transport entity impacted by the isolation problem.

The isolation is detected as a consequence of a failure of an operation addressed to the NE.

The recovery from the isolation is detected by means of a slow polling performed by RM on the isolated
NE.

When an isolated NE is detected as reachable, the download is automatically started.

During downloading activity, the same considerations made for download disable to download enable
transition are applicable.

The OS isolation alarm received by SH and the SH isolation alarm detected by mean of a slow polling
1AA 00014 0004 (9007) A4 ALICE 04.10

performed by RM are reported as alarms at the RM user interface.

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 151 / 182

182
8.2.3 Consistency download management ( TSDIM )
The objective of this feature is to align the NE with RM Mib being RM the reference.

not permitted without written authorization from Alcatel.


The operation is available for TSDIM NEs while1354RM is in normal online runlevel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
For QB3* NEs (SENIM managed) the consistency download policy remains unchanged.

The operation is available when the NE is not isolated and in download enabled mode. If the
communication is lost during the download, the operator is informed at user interface and the NE is left
in the download enabled mode; when the communication is resumed no automatic restart of the
consistency download is performed.

When a Ne is in the consistency download phase, all the configuration changes on the specific NE are
refused if impacting on the real NE configuration (i.e. the implementation of a subnetwork connection is
refused but not the creation since an allocated connection doesnt have any image in the NE).
As a consequence of this limitation, an activity on a transport entity (e.g. the path implementation) or on
a topology that has impact on a NE where the consistency download phase is ongoing, will fail (e.g. the
path implementation will fail but the path allocation will not).
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 152 / 182

182
8.2.4 Consistency Status ( TSDIM )
The following table gives an overall mapping of the values of consistency status and consistency activity.
not permitted without written authorization from Alcatel.

Table 4. Values of Consistency Status attribute.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Consistency Semantic
Status
Normal The object in the RM MIB is fully aligned with the equivalent object(s) in the NE MIB.
Planned The object exists only in the RM MIB in a planned state.
This is the case for example of allocated subnetwork connections, virtual CAPs etc.
Not aligned RM MIB and NE MIB are different because the RM operator has requested a change
in RM MIB causing a nonalignment.
This is a semi permanent state when the Node is in Download disabled Mode or Iso-
lated.
If the Node is moved to the appropriate state (i.e. download enabled and NE reach-
able), the system forces a download (automatic download).
If the Node is Reachable and in Download enabled the object is in the aligning state
The RM MIB and the NE MIB are not in line because an audit activity detects a non
alignment in download disable mode.
As in previous state, objects in this state are automatically downloaded when the NE
is reachable and in download enabled.

If the consistency audit is executed on transport entities and in download enabled


mode, the consistency status is set to config. mismatch

N.B. The NE comes out of the isolation state and during the isolation the object
has been modified inside the NE. RM using the NE event logger detects
the problem and marks the objects in order to avoid a global consistency
audit.
Failed to align The object in the RM MIB is not aligned with the equivalent objects in the NE MIB
as a result of a failure in the downloading performed from the Not aligned state.
Objects in this state are not automatically downloaded unless a new change is per-
formed on the object or during a consistency download.
Config Mismatch The object has been found not consistent during a consistency audit performed on
transport entities while in download enabled.
Aligning This is a temporary value that is present only when forcing of attributes on NE is exe-
cuted.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 153 / 182

182
8.2.5 Consistency audit management

The objective of this feature is to verify the alignment between NE and RM Mib.

not permitted without written authorization from Alcatel.


The operation is available for TSDIM NEs while the RM system is in normal online runlevel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
This is an improvement respect to previous versions where the operation was only possible with RM set
to consistency run level (i.e. read/only mode).

Two types of consistency audit are available:

Mark :
differencies are marked. These differencies will be taken into account and downloaded during the
operations of enabling the download and isolation recovery.

Notify:
differences are marked and wil be not taken into account during the operations of enabling
download or isolation recovery.

The consistency audit is available on the Node and on the NE, only if the NE is not isolated and the
1354RM is in Download Disable mode.

Consistency audit on transport / topology entities

The consistency audit on transport entities is available in download enabled mode.

The consistency audit on transport entities is executed only in the notify mode.

The not aligned objects are marked with a particular value of the consistency status :Config. mismatch.
Objects with this value of the attribute are not automatically downloaded when the NE becomes reachable
or when the download state becomes enabled.

The transport entities affected by a consistency audit are locked with a specific attribute of the working
state (auditing).
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 154 / 182

182
8.2.5.1 Consistency audit on objects

Objects impacted by the consistency audit are single TPs, subnetwork connections, NE / Node, PMTP.
not permitted without written authorization from Alcatel.

In the following table the releationship between the initial value of the consistency Status and the result
All rights reserved. Passing on and copying of this
document, use and communication of its contents

of the consistency is reported both for Mark and Notify mode.

Table 5. Starting and final Consistency status given the consistency results for consistency audit in
Mark Mode.

Mark Mode :

Initial Object Found and consistent Object not found or not consistent
Consistency
Status

normal Normal not aligned

not aligned Normal not aligned

failed to align Normal failed to align

config mismatch Normal not aligned

aligning Not valid as initial state

planned Not to be taken into account

Table 6. Initial and final Consistency status given the consistency results for consistency audit in Notify
Mode

Notify Mode :

Initial Object Found and consistent Object not found or not consistent
Consistency
Status
normal Normal Config Mismatch
not aligned Normal not aligned
failed to align Normal failed to align
config mismatch Normal Config Mismatch
aligning Not valid as initial state
planned Not to be taken into account
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 155 / 182

182
8.2.5.2 Consistency download on objects

This operation can be executed on single TPs, subnetwork connections, NE / Node.

not permitted without written authorization from Alcatel.


During the consistency download on the Node, all the incoming requests are rejected.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
8.2.5.2.1 NE is again reachable

All operations queued before the event of NE again reachable are executed first.

Only not aligned objects are taken into account.

8.2.5.3 Download disabled to enabled transition

All current operations on the NE must be completed before serving the transition.

8.2.5.4 Startup / Restart scenario

RM elementary objects are taken into account by layers in a server to client order: physical ports, NAPs,
MSTPs, HOCTPs, HO connections, HOTTPs, LOCTPs, LO connections.

8.2.5.5 Ne reachable to unreachable transition

All the current operations on the NE must be completed considering the NE unreachable even if the state
changes again before the end of the current operations.

8.2.5.6 Download enabled to disabled transistion

All the current operations on the NE must be completed before serving the transition. For these operations
the NE has to be considered as still in download enabled.

8.2.5.6.1 Reporting

A specific alignment information table is used to improve reporting during alignment phase.

Contained information

This table contains the following Information for each object with a consistency status
different from normal:
phase where the problem was detected: Consistency audit (Mark or Notify),
Consistency download, Change attribute, Isolation recovery, download enabling.....
[ time stamp ]
problem or info
problem parameter (i.e. the RM attribute qualifying the problem or information).

Example :
Change attribute: (Infocode) The attribute <xy> has not been update in the NE due to
consistency download disabled (or Ne isolation .....)
Cons.AuditNotify: (infocode) The TP or connection does not exist in the NE
Change attribute: (errorcode) Failure in alligning the attribute <xyz>
Change attribute: (errorcode) Failure in alligning one or more client objects
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 156 / 182

182
8.2.6 Reporting during consistency ( TSDIM )

This feature allows to present the list of RM objects not consistent with the NE ones.
not permitted without written authorization from Alcatel.

An object can be not consistent due to the misalignment of one or more attributes. For each attribute the
All rights reserved. Passing on and copying of this
document, use and communication of its contents

following information are presented :

object class
user label
attribute: attribute of the object that causes the not consistency
error type: reason of the inconsistency
date

The user label field contains the user label of the object with the following exceptions:

msProtBlock4f = user label of the node


ctp (ho) = user label of the port payload position
nap = user label of the port
au4RTM = user label of the node au4
ctp (lo) = user label of the port payload position
connInTopol = user label of the path

The user can choose, using two different commands, to display a global or a restricted list of the objects.

The global list comprises:

ne
port (sdh)
msCtpCap
msProtBlock4f
ctpho
port (pdh)
nap
au4RTM
cap
ctplo
connInTopol
pmTp

The restricted list comprises only traffic affecting attributes:

ne (only if it is not reachable)


msCtpCap (au4Structure, removeFromProtSchema, allAttributes)
msProtBlock4f (msProtConfState, allAttributes)
ctpho (disconnectOnNe, allAttributes)
nap (disconnectOnNe, allAttributes)
au4RTM (consistSt, allAttributes)
cap (virtual, tug1Cfg, tug2Cfg, tug3Cfg, allAttributes)
ctplo (disconnectOnNe, allAttributes)

The allAttributes value is used when it is not possible to determinate the attribute that caused the
inconsistency.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 157 / 182

182
8.2.7 Consistency Status Diagnostic ( TSDIM )

The Consistency Statuses relevant to Diagnostic are:

not permitted without written authorization from Alcatel.


Not aligned. This is due to:

All rights reserved. Passing on and copying of this


document, use and communication of its contents
NE unreachable. Note that the NE polling time is 3

NE in download disable mode

Fail to align. The 1354RM tried to execute a data download. The operator can click on the
Consistency Status icon, thus displaying the report identifying the RM failed operation, i.e. the not
aligned attributes and the causes of the failure.

Consistency Mismatch. A Consistency Audit: Notify has been executed. The operator will issue on
the involved NE the command Display: Misaligned Objects.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 158 / 182

182
9 1354RM PROCESS CONTROL

9.1 Introduction to process control


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

The 1354RM Process Monitor & Control (PMC) allows the user an overall control of the IM subsystem.
By means of PMC the user can execute the following operations:

Start / Stop database

Start / Stop system

Start / Stop single Agent

Start / Stop Control process

Change system Run Level

To launch the 1354RM process control, click on icon Monitor in the 1354RM panel or in the Application
Selection box. The 1354RM process control window is displayed (See Figure 90. ). The upper portion of
the window contains the following alarm indicators:

Database (On / Off / Wrong) which displays the alarm status of the database instance associated to
the 1354RM. It is Wrong if at least one process is stopped.

Control (On / Off) which allows to display whether the agents are being controlled or not.

System (On/Off/Wrong). This indicator is On if all agents belonging to the current run level and all
their children are Running; it is Off if all Agents are stopped; it is Wrong if at least one Agent or
one child process is stopped.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 159 / 182

182
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Figure 90. Process control window

The pulldown menu bar contains three menus:

File

Actions

View

The menu File contains the only option Exit, which allows to close the window.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 160 / 182

182
The menu Actions contains the following selectable options (See Figure 91. ):

Startup
not permitted without written authorization from Alcatel.

Shutdown
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Control

Set Run Level

on Agent

Synchronize

Figure 91. Process Control window:Actions:Startup pulldown menu


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 161 / 182

182
The options Startup and Shutdown allow to select one of the following items:

Selected agent

not permitted without written authorization from Alcatel.


System

All rights reserved. Passing on and copying of this


document, use and communication of its contents
Database

These functions are detailed in the following.

The option Control allows to select one of the following items:

Start process. This menu, if selected, executes one of the following:

restart of a stopped process(es) belonging to the current run level

restart of process(es) overlapping the maximum configured size of dynamic memory

restart of stopped data base process(es)

Stop process

The options Set Run Level allows to select the following items:

0:Full functionality

1:Network Configuration

2:Network Maintenance

3:Network Consistency
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 162 / 182

182
EXAMPLE OF SET RUN LEVEL

If you enter Actions:Set Run Level:3Network Consistency, this will stop all Agents which do not include
Run Level 3 configured and starts the remaining.
not permitted without written authorization from Alcatel.

NOTE
All rights reserved. Passing on and copying of this
document, use and communication of its contents

The Run Level attributes are set during installation. You can display these attributes by entering the
command View:Agent Processes.

The menu View contains the following selectable options (See Figure 92. ):

History
Agent processes
Database process
Configuration
Agent trace

Figure 92. Process Control window:View pulldown menu

The option History allows to select one of the following items:


Local, to display actions/events relevant to Process Monitor.
Control, to display actions/events relevant to Process Control
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 163 / 182

182
9.1.1 Actions:Startup pulldown menu

The Actions:Startup pulldown menu allows to select one of the following submenus
(See Figure 91. on page 161):

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
Selected agent
System
Database

9.1.1.1 Actions:Startup:Selected agent

PURPOSE

The purpose of this procedure is to start the selected agent.

CONDITIONS

The process control window is opened and the View: Agent process has been successfully entered. This
operation can be applied only to parent processes (i.e. the process displayed on the lefthand side of the
window.

PROCEDURE

a) In the list 1354RM processes select the process to start (double click).

b) In the menu bar select Actions:Startup:Selected agent. (See Figure 91. ). A dialog box alerts the
user: <agentname> Startup in progress

c) After a few seconds, in the list 1354RM processes verify if the status of the selected agent changed
to RUN.

9.1.1.2 Actions:Startup:System

PURPOSE

The purpose of this procedure is to cause a startup of the system

CONDITIONS

The process control window is opened.

PROCEDURE

a) In the menu bar select Actions:Startup:System. (See Figure 91. ). A dialog box alerts the user:
System Startup in progress

b) After a few seconds verify if the System indicator turned to ON .


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 164 / 182

182
9.1.1.3 Actions:Startup:Database

PURPOSE
not permitted without written authorization from Alcatel.

The purpose of this procedure is to cause a startup of the Database.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

CONDITIONS

The process control window is opened.

PROCEDURE

a) In the menu bar select Actions:Startup:Database (See Figure 91. ). A dialog box alerts the user:
Database Startup in progress

b) After a few seconds verify if the Database indicator turned to ON .


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 165 / 182

182
9.1.2 Actions:Shutdown pulldown menu

The Actions:Shutdown pulldown menu allows to select one of the following submenus:

not permitted without written authorization from Alcatel.


Selected agent

All rights reserved. Passing on and copying of this


document, use and communication of its contents
System
Database

9.1.2.1 Actions:Shutdown:Selected agent

PURPOSE

The purpose of this procedure is to cause a shutdown of the selected agent.

CONDITIONS

The process control window is opened and the View: Agent process has been successfully entered. This
operation can be applied only to parent processes (i.e. the process displayed on the lefthand side of the
window).

PROCEDURE

a) In the list 1354RM process select the process to shutdown (Double click on the process name).

b) In the menu bar select Actions:Shutdown:Selected agent. A dialog box alerts the user:
<agentname> Shutdown in progress

c) After a few seconds, verify if the status of the selected agent changed to STOP in the list 1354RM
process.

9.1.2.2 Actions:Shutdown:System

PURPOSE

The purpose of this procedure is to cause a shutdown of the system.

CONDITIONS

The process control window is opened.

PROCEDURE

a) In the menu bar select Actions:Shutdown:System. A dialog box alerts the user: System Shutdown
in progress

b) After a few seconds verify if the System indicator turned to OFF.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 166 / 182

182
9.1.2.3 Actions:Shutdown:Database

PURPOSE
not permitted without written authorization from Alcatel.

The purpose of this procedure is to cause a shutdown of the Database.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

CONDITIONS

The process control window is opened.

PROCEDURE

a) In the menu bar select Actions:Shutdown:Database. A dialog box alerts the user: Database
Shutdown in progress

b) After a few seconds verify if the Database indicator turned to OFF.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 167 / 182

182
9.1.3 Actions:Control pulldown menu

The Actions:Startup pulldown menu allows to select one of the following submenus:
Start process

not permitted without written authorization from Alcatel.


Stop process

All rights reserved. Passing on and copying of this


document, use and communication of its contents
9.1.3.1 Actions:Control:Start process

PURPOSE

The purpose of this procedure is to enable the control on all agents. This means to start a process which
continuously verifies the status of all processes and puts again active a process which went down.

CONDITIONS

The process control window is opened.

PROCEDURE

a) In the menu bar select Actions:Control:Start process. A dialog box alerts the user: Control enable
in progress

b) After a few seconds verify if the Control indicator is ON .

9.1.3.2 Actions:Control:Stop process

PURPOSE

The purpose of this procedure is to disable the control on all agents.

CONDITIONS

The process control window is opened.

PROCEDURE

a) In the menu bar select Actions:Control:Stop process. A dialog box alerts the user: Control disable
in progress

b) After a few seconds verify if the alarm indicator Control turned to OFF.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 168 / 182

182
9.1.3.3 Actions:Set Run Level

PURPOSE
not permitted without written authorization from Alcatel.

The purpose of this procedure is to set the run level of the selected agent. This means that you are
All rights reserved. Passing on and copying of this
document, use and communication of its contents

changing the group of actually running processes.

CONDITIONS

The process control window is opened.

PROCEDURE

a) In the menu bar select Actions:Set Run Level. You can select among the following:

0 : Full functionality

1 : Network Configuration

2 : Network Maintenance

3: Network Consistency

EXAMPLE OF SET RUN LEVEL

If you enter Actions:Set Run Level:3Network Consistency, this will stop all Agents which do not include
Run Level 3 configured and starts the remaining.
NOTE
The Run Level attributes are set during installation. You can display these attributes by entering the
command View:Agent Processes.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 169 / 182

182
9.1.3.4 Actions: Agents: Change Trace level

PURPOSE

not permitted without written authorization from Alcatel.


The purpose of this procedure is to change the trace level of the selected agent.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
CONDITIONS

The process control window is opened.

PROCEDURE

a) Select the Agent (double click on the name).

b) Select menu Actions:Agents: Change trace level.

c) Change the trace level according to the values indicated in the Agent trace level file. See 1354RM
R2.3 Installation Guide and Syst. Adm. Ref.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 170 / 182

182
9.1.3.5 Actions:Synchronize

PURPOSE
not permitted without written authorization from Alcatel.

The purpose of this procedure is to synchronize the monitor window to the actual state of the vprocesses.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

CONDITIONS

The process control window is opened.

PROCEDURE

a) In the menu bar select Actions:Synchronize. The PMC window is aligned to the actual status of the
processes.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 171 / 182

182
9.1.4 View pulldown menu

The Actions:View pulldown menu allows to select one of the following submenus
(See Figure 92. on page 163):

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
History
Agent processes
Database processes
Configuration
Agent trace

9.1.4.1 View:History:Local

PURPOSE

The purpose of this procedure is to display the historical file of system messages.

CONDITIONS

The process control window is opened.

PROCEDURE

a) Select Views:History:Local. The message file is displayed in the lower portion of the screen. Each
message is described with date, time, message type, <message>. (See Figure 93. )

In this window you can find messages about operations performed on agents or crashes of child
agents automatically recovered by the parent.
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 93. Process Control window:View : History: Local

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 172 / 182

182
9.1.4.2 View:History:Control

PURPOSE
not permitted without written authorization from Alcatel.

The purpose of this procedure is to display the historical file of system messages relevant to the Control
All rights reserved. Passing on and copying of this
document, use and communication of its contents

function.

CONDITIONS

The process control window is opened.

PROCEDURE

a) Select Views:History:Control. The message file is displayed in the lower portion of the screen. Each
message is described with date, time, message type , <message>. (See Figure 94. )

In this window you can find messages about operations performed on agents or crashes of child
agents automatically recovered by the control.

Figure 94. Process Control window:View : History: Control


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 173 / 182

182
9.1.4.3 Views:Agent processes

PURPOSE

not permitted without written authorization from Alcatel.


The purpose of this procedure is to show the monitored processes.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
CONDITIONS

This is the default view.

PROCEDURE

a) Select Views:Agent processes. The Agent processes are displayed in the lower portion of the screen
with name, Run Levels, type, status, size (dynamic memory), pid, child (if any) where:

Name=Agent name

Run Level=run level set specified for the process

Type. It can be UX(Unix) or OV(HPOVw)

Status. It can be:

RUN. The Agent and its children are active.


STOPPED. The Agent and its children are stopped.
WRONG. At least the Agent or one of its children is stopped

Size. Dynamic memory actually allocated for the process (Kb). The allowed maximum size is shown
in the View:Configuration dialog box.

PID. process identifier

Child. Name/s of the Child/ren Process


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 174 / 182

182
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
01

957.130.872 H
SC.6:MAINTENANCE

182
3AL 61259 AA AA
Figure 95. Process Control window:View : Agent processes

175 / 182
9.1.4.4 Views:Database process

PURPOSE

not permitted without written authorization from Alcatel.


The purpose of this procedure is to view the Database process .

All rights reserved. Passing on and copying of this


document, use and communication of its contents
CONDITIONS

The process control window is opened.

PROCEDURE

a) Select Views:Database process. The Database process is displayed in the lower portion of the
screen with PPID, PID, TIME, NAME (See Figure 96. ).

where:

PPID=Parent Process Identifier

PID=Process Identifier

TIME=CPU time elapsed by the processes

NAME=Database Process Name

Figure 96. Database process view


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 176 / 182

182
9.1.4.5 Views:Configuration

PURPOSE
not permitted without written authorization from Alcatel.

The purpose of this procedure is to view the PMC configuration file.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

CONDITIONS

The process control window is opened.

The process control process makes use of the following environment variables:

PROCEDURE

a) Select Views:Configuration. The configuration file is displayed (See Figure 97. ).

The configuration file describes all agents that must be monitored by PMC, Db processes and
associated Run Levels.

Figure 97. View:Configuration file


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 177 / 182

182
For each controlled agent the following information is provided:

agent_name : name of controlled agent

not permitted without written authorization from Alcatel.


agent_type : it specifies the agent handling type. It can be set either as general (for process

All rights reserved. Passing on and copying of this


document, use and communication of its contents
managed as normal Unix processes) or hpov (for process managed by means of ovstart and
ovstop HPOV function).

agent_image : (this entry is meaningful only for agent with agent_type = general)
absolute path name of the executable agent image. It is also possible to indicate script file that
starts the executable image inside if it uses exec Unix command.

agent_params : (this entry is meaningful only for agent with agent_type = general)
agent parameters used by the executable image, or script, in the startup phase. In the
parameters description the spaces are replaced by commas.

agent_child (n lines) : child process names, number of its instances that are controlled by PMC
and max. memory size for each instance (this has the same meaning of the agent_max_size)
parameter. A new line exists for each agent child process.

agent_start_wait : (this entry is meaningful only for agent with agent_type = general)
timeout (number of seconds) to wait before PMC can check the correct agent initialization after
its startup.

agent_shut_wait : (this entry is meaningful only for agent with agent_type = general)
timeout (number of seconds) to wait before PMC can check the correct agent termination after
its shutdown.

agent_mon_interval : number of seconds between two consecutive polling operations on the


agent.

agent_max_size : maximum memory size (in Kb) occupied by the agent. If this value is reached
and the monitoring function is enabled, an automatic agent shutdown and restart will be
executed. If the monitoring function is disabled, no restart is performed and the agent is
displayed with the WRONG status.

agent_trace_location : directory or file containing the trace information associated to the


process.

agent_trace_default : it specifies the default trace file to be visualized, between the ones
displayed to the operator. Typically this multiple trace files selection is between the agent trace
file and its child process trace files.

agent_run_level : it specifies all run levels the controlled agent belongs to.

agent_ps_info : name of controlled agent to use searching it into a ps ef list. This option has
to be specified only if this name differs from the one indicated.

agent_actions_name : Ordering number and actions name for controlled Agent.

agent_actions_command : Ordering number and command for controlled Agent. In the


command description spaces are replaced by commas.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 178 / 182

182
9.1.4.6 View: Agent trace

PURPOSE
not permitted without written authorization from Alcatel.

The purpose is to view the selected agent trace.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

CONDITIONS

The process control window is opened, on Agent process view.

PROCEDURE

a) Select the Agent (double click)

b) Select Views:Agent Trace. If the agent has no children, the Agent Trace window is presented.
For parent Agents is displayed a list of possible traces (see Figure 98. ).

Figure 98. Agent trace selection box


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 179 / 182

182
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 H
SC.6:MAINTENANCE
Figure 99. shows an example of Agent trace.

Figure 99. Example of agent trace

182
3AL 61259 AA AA
180 / 182
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
INDEX

A L
not permitted without written authorization from Alcatel.

AIS, 10 LOTTP Alarm Propagation, 26


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Alarm processing, 73 Lockout , 130


Alarm Propagation, 23 LOF, 10
Alarms, 9 Logger, 145
AlrfloodingHP, 11 LOP, 10
AlrfloodingLP, 11 LOS, 10
ASAP, 17

M
C
MAINTENANCE, 61
ConfMismatch, 11 Manual Switch / Ring pending, 141
CONSISTENCY, 149 MediaEqFail, 11
Consistency audit, 149 MSSpring Alarm Propagation, 24
Consistency download, 150 MSTP Alarm Propagation, 24
Control, 168 MStrail, 66
CTP Alarm Propagation, 27 mSConfMismatch, 11

D N

DegSig, 11 NE, 85
NenotReachable, 11
neNR, 10
E Node, 95
NODE CONDITION, 120
EML, 83
NPE Ring, 115
ExBER, 10
ExBer, 11
P
F Path, 71, 75
PDHFailure, 11
fault localization, 62
Physical Connection, 88
FERF, 10
Physical connection, 64
Forced Switch / Span, 140
PLM, 10
Forced Switch Ring, 137
Port Alarm Propagation, 23
Probable Causes, 10
H Process, 159
PTM, 10
HOtrail, 68
HOTTP Alarm Propagation, 25
Q

I QualityTC15m, 11
QualityTC24h, 11
Inhibition chain, 131

R
1AA 00014 0004 (9007) A4 ALICE 04.10

K
RAI, 10
K1K2PM, 10 reISO, 10, 11

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 181 / 182

182
remSDHFailure, 11 Startup, 164
RS Failure, 11 Subnetwork, 92
RU, 10
rxF, 10

not permitted without written authorization from Alcatel.


T

All rights reserved. Passing on and copying of this


document, use and communication of its contents
S TrF, 10
txF, 10
Scenarios, 132
SDHFailure, 11
Shutdown, 166 U
signal Fail, 139
UnderProtDeg, 11
SLM, 10
UNEQ, 10
SSF, 10
UPA, 10
SSF_Eg, 10
SSF_In, 10

END OF DOCUMENT
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.6:MAINTENANCE

957.130.872 H 3AL 61259 AA AA 182 / 182

182
1354RM REL.5.2B OPERATORS HANDBOOK
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

TABLE OF CONTENTS

LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 ACCESS TO THE MAIN FUNCTIONALITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13


2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1.1 The Tool Subpanel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3 SDH NETVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1.1 Icon bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.1.2 Popup menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4 SDH NETVIEW : MAP SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29


4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.2 Map: Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.2.1 Map: Maps: Open/List ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.2.2 Map: Maps: New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.2.3 Map: Maps: Save Map As... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2.4 Map: Maps: Describe/Modify Map... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2.5 Map: Maps: Delete... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3 Map: Submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3.1 Map: Submap: Open/List... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3.2 Map: Submap : New... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3.3 Map: Submap: Describe/Modify... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3.4 Map: Submap: Set This Submap As Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.3.5 Map: Submap: Delete... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.3.6 Map: Submap: Delete This Submap... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.4 Map: Refresh Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.5 Map:Map Redo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.5.1 Map: Map Redo: Store Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.5.2 Map: Map Redo: Store Map (no connections) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.5.3 Map: Map Redo: Store Submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

01 000721 validated M.RAGNI ITAVE V.PORRO ITAVE


E.CORRADINI F.FERRARID.ERBA
01A 000515 proposal M.RAGNI ITAVE V.PORRO ITAVE
E.CORRADINI F.FERRARID.ERBA
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
1AA 00014 0004 (9007) A4 ALICE 04.10

1354RM REL.5.2B

OPERATORS HANDBOOK

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 1 / 230

230
4.5.4 Map: Map Redo: Store Submap (no connections) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.5.5 Map: Map Redo: Execute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.6 Map:Distribute Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.6.1 Map :Distribute Maps: Store Map Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

not permitted without written authorization from Alcatel.


4.6.2 Map: Distribute Maps: Get/List Map Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

All rights reserved. Passing on and copying of this


document, use and communication of its contents
4.6.3 Map:Distribute Maps:Remove Map image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.6.4 Map :Distribute Maps: Lock map image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.6.5 Map :Distribute Maps: Unlock map image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.6.6 Map :Distribute Maps: Modify Username List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.7 Map: Close Submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.8 Map: Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5 SDH NETVIEW: EDIT SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57


5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.2 Edit: Cut: From This Submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.3 Edit: Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.4 Edit: Delete: From the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.5 Edit : Hide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.5.1 Edit: Hide : From This Submap... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.5.2 Edit: Hide : From All Submaps... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.6 Edit:Show Hidden Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
5.6.1 Edit: Show Hidden Objects : For This Submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
5.6.2 Edit: Show Hidden Objects : For All Submaps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

6 SDH NETVIEW: LOCATE SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63


6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6.2 Locate: Selected Object List... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6.3 Locate:objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.3.1 Locate: Objects : By Selection Name... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.3.2 Locate: Objects : By Attribute... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.3.3 Locate: Objects : By Comment... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.3.4 Locate: Objects : By Symbol Status... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.3.5 Locate: Objects : By Symbol Type... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.3.6 Locate: Objects : By Symbol Label... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

7 SDH NETVIEW: VIEW SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67


7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
7.1.1 View:Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
7.1.2 View: Overlay Submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.1.3 View: Redo Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.1.4 View: EML... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.1.5 View: Object Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
7.1.6 View: Clear Alarmed Object (acknowledge) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

8 SDH NETVIEW: CONSTRUCTION SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73


8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
8.2 Construction:Upload EML(s) info... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
8.2.1 Construction:Upload EML(s) info:Available EMLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
8.2.2 Construction:Upload EML(s) info:Available NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
8.2.3 Construction:Upload EML(s) info:Available NE ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
8.3 Construction:Create Virtual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
1AA 00014 0004 (9007) A4 ALICE 04.10

8.3.1 Creating a Virtual EML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78


8.3.2 Construction:Create Virtual: Port... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
8.3.3 Construction:Create Virtual: NSDHPort... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
8.3.4 Construction:Delete Virtual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 2 / 230

230
8.4 Construction:Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
8.4.1 Construction:Create:Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
8.4.2 Construction:Create:Subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
8.4.3 Construction:Create:Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
not permitted without written authorization from Alcatel.

8.5 Construction:Create Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88


All rights reserved. Passing on and copying of this
document, use and communication of its contents

8.6 Construction: Link to a topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

9 SDH NETVIEW: SUPERVISION SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93


9.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
9.2 Supervision: Implement Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
9.2.1 Supervision: Deimplement Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
9.2.2 Supervision: Placement: Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
9.2.3 Supervision: Placement: Retrieve: Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
9.2.4 Supervision: Placement: Retrieve Not Placed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
9.2.5 Supervision:Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
9.2.6 Supervision:Configuration: Synch.equipment Eml<>NML . . . . . . . . . . . . . . . . . . . . . . . . 100

10 SDH NETVIEW: BROWSE SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103


10.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
10.2 Browse: Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
10.3 Browse: NAPs: Idle 2 Mb/ Idle34Mb/ Idle 45Mb/ Idle140Mb/ filtered . . . . . . . . . . . . . . . . 104
10.4 HO CTPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
10.5 Browse: Paths... : in Topology... : 2Mb/ 34Mb/ 45Mb /140 Mb / filtered . . . . . . . . . . . . . 106
10.6 Browse: Paths... : all in Phys. Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
10.7 Browse: Paths... : active in Phys. Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
10.8 Browse: Paths... : starting (ending) from nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
10.9 Browse: Trails...: at this sublevel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
10.10 Browse: Trails...: at all sublevels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
10.11 Browse: Trails...: user defined HO trails at all sublevels . . . . . . . . . . . . . . . . . . . . . . . 107
10.12 Browse: Trails starting (ending) from nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
10.13 Browse: Physical Connection.. : LCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
10.14 Browse: Physical Connection: Physical Connection structure . . . . . . . . . . . . . . . . . . 108
10.15 Browse: SDH Port payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
10.16 Browse: Protection Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
10.17 Browse: Performance Monitoring: Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
10.18 Browse: Performance Monitoring: Monitored NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
10.19 Browse: Performance Monitoring: TCA Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
10.20 Browse: Performance Monitoring: Counter Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
10.21 Browse: Performance Monitoring: Threshold Reports . . . . . . . . . . . . . . . . . . . . . . . . . . 109
10.22 Browse: Performance Monitoring: Archive Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
10.23 Browse: Alarmed objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

11 SDH NETVIEW: TOOLS SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111


11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
11.2 Tools: Path: Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
11.3 Tools: Path: Contraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
11.4 Tools: Path: Add Leg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
11.5 Tools: Modify Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
11.6 Tools: Setup Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
11.7 Tools: Upload NAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
11.8 Tools: Network Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
1AA 00014 0004 (9007) A4 ALICE 04.10

12 SDH NETVIEW: HELP SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

13 BROWSER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 3 / 230

230
13.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
13.2 Browser main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
13.2.1 Icon bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
13.2.2 Counters area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

not permitted without written authorization from Alcatel.


13.2.3 Work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

All rights reserved. Passing on and copying of this


document, use and communication of its contents
13.3 Object filtering and scoping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
13.3.1 DEFINE QUERY FOR (the selection/filter window) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
13.4 Show/Set Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
13.5 Items selection in the Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
13.6 Generic Browser pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
13.6.1 Actions: Display: Main Related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
13.6.2 Actions: Display: All Related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
13.6.3 Actions: Display: Align item(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
13.6.4 Actions: Display: Parent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
13.6.5 Actions: Select: Related Items.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
13.6.6 Actions: Select: All related Items.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
13.6.7 Actions: Select: Unselect All.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
13.6.8 Actions: Close: Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
13.6.9 Actions: Close: Item by Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
13.6.10 Actions: Close: All related items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
13.6.11 Actions: Details: Show/set attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
13.6.12 Actions: Details: Displayed info... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
13.6.13 View:Displayed info.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
13.6.14 View:Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
13.6.15 Options: Filtered presentation / Not filtered presentation . . . . . . . . . . . . . . . . . . . . . . . 135
13.6.16 Options:Graph refresh rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
13.6.17 Options:Close window going to parent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
13.6.18 Options: Enable AS link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
13.6.19 Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
13.6.20 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
13.6.21 ExtTools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

14 BROWSER: DRAWING WINDOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139


14.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
14.1.1 Icon bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
14.1.2 Work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
14.2 Payload configuration of a Physical Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
14.3 Client link connection (view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
14.4 Path in trail (view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
14.5 Port structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
14.6 Trail Routing display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
14.7 2F MSSPRING protection block view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
14.8 4F NPE protection block view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
14.9 Path/Trail Routing view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
14.9.1 Main Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
14.10 Link Connection routing View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
14.11 Naps View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
14.12 Node view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
14.13 Performance Monitoring Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
14.13.1 PM Transport view display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
14.13.2 PM TP view display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
1AA 00014 0004 (9007) A4 ALICE 04.10

15 BROWSER MULTICOLUMN WINDOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165


15.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 4 / 230

230
15.1.1 Pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
15.1.2 Icon bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
15.1.4 Title area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
15.1.5 Counters area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
not permitted without written authorization from Alcatel.

15.1.6 Work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168


All rights reserved. Passing on and copying of this
document, use and communication of its contents

15.1.7 Counters and graphs on Browser MultiColumn Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . 169


15.1.8 Multicolumn list window configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
15.2 Available Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

16 BROWSER: LOCATE ITEMS IN SDH NETVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177


16.1 Path route on SDH netview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
16.2 Locate topological objects on Netview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

17 PAYLOAD CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183


17.1 Introduction to Payload Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
17.1.1 Configuring the payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
17.1.2 Payload Configuration monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
17.1.3 Payload Configuration supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
17.2 AU4 Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
17.2.1 AU4 Concatenation SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

18 TRAIL SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

19 PATH CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197


19.1 Path Create by using the Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
19.2 Path Create by using NETVIEW Browse: Nodes or relative icon . . . . . . . . . . . . . . . . . . 201
19.3 Path Create by using NETVIEW Browse: Nap(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

20 PATH/TRAIL CONSTRAINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205


20.1 Use/Not use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
20.2 Overlapped/Disjointed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

21 ADD LEGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

22 CONNECTIVITY INVENTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213


22.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
22.2 Data Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

23 EVENT LOGGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217


23.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

24 RM JAVA BROWSER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221


24.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
24.1.1 Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
24.1.2 Available Choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
24.1.3 Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 5 / 230

230
LIST OF FIGURES AND TABLES

FIGURES

not permitted without written authorization from Alcatel.


Figure 1. HPCDE Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

All rights reserved. Passing on and copying of this


document, use and communication of its contents
Figure 2. 1354RM Tool subpanel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 3. SDH Netview window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 4. Network popup menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 5. Subnetwork popup menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 6. ET popup menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 7. Physical connection main items popup menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 8. Node pop up menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 9. Map pull down menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 10. Available Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 11. Open View Windows Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 12. File:New Map dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 13. Map: Submap pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 14. Map pull down menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 15. Map Redo Store dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 16. List of saved maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 17. Execute map report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 18. Map: Map Redo: Execute: dragging nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 19. Map:Distribute Maps menu items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 20. Store Map dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 21. Map :Distribute map: Lock map image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 22. Modify Username dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 23. Exit warning box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 24. Edit pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 25. Locate pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 26. View pull down menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 27. Example of View: Object Attributes: Long Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 28. Example of View: Object Attributes: Short Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 29. Construction pull down menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 30. Available EMLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Figure 31. Available NEs in a EML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 32. NE port detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 33. Construction:Virtual Elements:Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 34. Create a virtual NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 35. Virtual tool buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 36. Create a virtual port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 37. Create many virtual ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 38. Example of eml deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 39. Create Dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 40. Create Ring dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 41. Create connection dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 42. Connection just created. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Figure 43. Ports in Node: Create Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 44. Create Connection dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 45. Physical connection: Implement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 46. Supervision pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 47. Implement Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 48. Audit basic flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98


Figure 49. Browse pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 50. NAP List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 6 / 230

230
Figure 51. Filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 52. Browser main window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Figure 53. Browser work area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 54. Object filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
not permitted without written authorization from Alcatel.

Figure 55. Define query window for Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Figure 56. Show/Set Attributes dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125


Figure 57. Actions: Details: Displayed Info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 58. View:Report full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 59. View:Report short . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Figure 60. Options:Deferred Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Figure 61. Options:Default graph refresh rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Figure 63. Physical connection structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Figure 64. Client link connection (view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Figure 65. Paths in trail (view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Figure 66. Port structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Figure 67. Trail Routing display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Figure 68. MSSPRING Protection block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Figure 69. Protection block popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 70. All protection block in MSSPRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Figure 71. 4F Protection blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Figure 72. Actual route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Figure 73. Path Routing ( BidirectionalProtected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 74. Path Routing example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 75. Route report example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 76. Link Connection Routing view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 77. Naps view of a bidirectional path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Figure 78. Node view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Figure 79. PM transport view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 80. PM TP view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Figure 81. Example of Multicolumn window (Path In Topology list) . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Figure 82. Graphical window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 83. Statistical Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 84. Ordering items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Figure 85. Sorting items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Figure 86. Highlighte button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Figure 87. Selection box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Figure 88. Locate display ( unprotected path ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Figure 89. Selection dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Figure 90. Locate display ( protected path ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Figure 91. Node list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Figure 92. Highlight button in Browser main. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Figure 93. Highlighted node in Netview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Figure 94. Payload Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Figure 95. Payload Configuration dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Figure 96. Physical connection structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Figure 97. MS trail selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Figure 98. Payload configuration button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Figure 99. Payload Configuration window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Figure 100. Payload selection subwindow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Figure 101. Concatenated payload configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 102. Browser window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191


Figure 103. Setup Trail icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Figure 104. Setup Trail window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Figure 105. Ring Attribute change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 7 / 230

230
Figure 106. Setup trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Figure 107. Trail view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Figure 108. Path Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Figure 109. Multi path creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

not permitted without written authorization from Alcatel.


Figure 110. Path Create. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

All rights reserved. Passing on and copying of this


document, use and communication of its contents
Figure 111. Path Constraints dialog box (use/not use constraint for CTPs popup) . . . . . . . . . . . . . . 205
Figure 112. Use Service Forward/Backward for Dual Node SNCP network . . . . . . . . . . . . . . . . . . . . 208
Figure 113. Path Constraints dialog box (disjoint/overlap constraint for PATHs popup) . . . . . . . . . . 210
Figure 114. Path list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Figure 115. Add Leg dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Figure 116. Actions:Get Topologies:all levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Figure 117. Connectivity Inventory : VC4 Trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Figure 118. Event Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Figure 119. Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Figure 120. 1354RM home page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Figure 121. Shrunk menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Figure 122. Expanded menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Figure 123. Operator Manual selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Figure 124. NEs ordered by type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Figure 125. NEs ordered by site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Figure 126. Path by rate and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Figure 127. Path: All filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Figure 128. Routing links completely idle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

TABLES
Table 1. Items selection in the Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 8 / 230

230
1 INTRODUCTION

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

This document is a reference handbook describing in detail the graphical interface provided by the
1354RM.

1.2 Target audience

The Introduction Manual is intended for all 1354RM users.

1.3 Document structure

This section covers the following topics:

ACCESS MODALITY

Access to the Main Functionalities

SDH Netview

MAP VIEW

Map: Submenu

Map: Maps menu

Map: Submap menu

Map: Refresh Map

Map: Redo Map

Map: Distribute Maps

Map: Close Submap

Map: Edit Submenu

Map: Locate Submenu

Map: View Submenu

CONSTRUCTION MENU

Introduction

Construction: Upload

Construction: Create Virtual

Construction: Create Object


1AA 00014 0004 (9007) A4 ALICE 04.10

Construction: Create Connection

Construction: Link (Line/Radio)

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 9 / 230

230
SUPERVISION

Supervision Menu

not permitted without written authorization from Alcatel.


BROWSE

All rights reserved. Passing on and copying of this


document, use and communication of its contents
Browse Menu

TOOLS

Tools Menu

HELP

Help on Line

BROWSER

Introduction

Browser Main Window

Object Filtering

Object Attribute

Item Selection

Generic Browser Menu

DRAWING WINDOWS

Drawing Introduction

Physical Connection Structure

Link Connection View

Path in Trail View

Port Structure

Trail Routing Display

2F MS SPRING View

4F NPE Protection View

Routing View

Link Connection View

Naps View

Node View


1AA 00014 0004 (9007) A4 ALICE 04.10

PM Views

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 10 / 230

230
BROWSER LIST

Browser List
not permitted without written authorization from Alcatel.

LOCATE
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Locate

PAYLOAD

Payload

AU4C ( CONCATENATED ) payload

TRAIL

Trail Setup

PATH CREATE

Path Create

Path Create (by Browser)

Path Create (Netview)

Path Create (Browser Naps)

CONSTRAINTS

Constraints

ADD LEGS

Add Legs

CONNECTIVITY MATRIX

Connectivity Matrix

LOGGER

Logger

JAVA BROWSER

Java browser netscape


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 11 / 230

230
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 H
SC.7:GRAPHICAL INTERFACE

230
3AL 61259 AA AA
12 / 230
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
2 ACCESS TO THE MAIN FUNCTIONALITIES

A more detailed description concerning the Regional Manager management domains are given in the
Regional Manager Introduction Manual.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Access to the Regional Manager functionalities is done through the workspace front panel as described
in the following sections.

2.1 Introduction

The 1354RM graphical interface is based on:

HP Common Desktop Environment ( CDE )

HP OpenView Windows (HP-OVw)

OSF Motif applications (Browser, RM Configuration Tools, Monitor tool, System Management
Functions, etc.).

The HP_CDE Tool panel ( See Figure 1. ) has been customized to contain the 1354RM Logo ( righthand
side ).

Clicking on the small arrow above the 1354RM logo you can open the Tool Subpanel. ( See Figure 2. on
page 14)

WS
Clock activity Text
Padlock Workspaces Editor
Date

Exit Letter
Printer Terminal
Netstation applications
File Regional
Manager Manager

Figure 1. HPCDE Panel.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 13 / 230

230
2.1.1 The Tool Subpanel

The HP_CDE Tool Subpanel (See Figure 2. ) has been customized to contain the following icons (click
the small arrow above the 1354 RM logo to open the Tool Subpanel):

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
Figure 2. 1354RM Tool subpanel

Logo 1354 RM Network Management System. Clicking twice on it, the informa
tion on RM version is displayed.

TMN OSs This icon, if selected, opens the supervision of the various OSs.

Administration This icon, if selected, opens the System Management functions


(see SMF doc.)

Alarms Starts the Alarm Surveillance user interface (see AS doc.).

Browser Starts the Generic Browser

Network View Starts the SDH Netview application.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 14 / 230

230
3 SDH NETVIEW

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

In figure Figure 3. its displayed a typical SDH netview window; each window is relevant to a submap.

icon bar pulldown menu window title items


Go to parent Panner
submap window
Exit Go to root
submap
Go to home
submap

work area holding area info area

Figure 3. SDH Netview window


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 15 / 230

230
A window (submap) typically contains:

window title : <parents fdn> # <parents label> (in this case the parent is a meshed ring)
pulldown menu bar. Refer to chapter 3 to 11

not permitted without written authorization from Alcatel.


icon bar. Refer to paragraph 3.1.1

All rights reserved. Passing on and copying of this


document, use and communication of its contents
work area. It contains items (Network, Subnetworks, ET, Nodes, Ports, Connections, ...) related
to the submap. The operations on items (Delete, Cut, Paste, Select, Move, ...) are described
in HPOpenview Windows manuals.
holding area. It contains the items that have not yet been placed in work area.
info area. It contains the map name and the rights on it.

A popup is also available on items (see para 3.1.2)

3.1.1 Icon bar

The icon bar contains the following buttons:

Exit SDH netview. It corresponds to the pulldown command Map: Exit (see para 4.8)
Go to parent submap. It display the parent submap.
Go to root submap. It display the root submap (eg. Network submap).
Panner window. It display the panner window (zoom window); selecting an area in the panner
window a zoom is performed in the submap window.
HP Openview version. It display the HP Openview Version dialog box.
Browser. It corresponds to the pulldown command Browse:Object(s).
Path constraints. It start the Path Constraints application (see chapter 20)
Filtered Paths .... It corresponds to the pulldown command Browse:Paths:In topology:Filtered.
User defined Trail .... It corresponds to the pulldown command Browse:Trails:User defined
HOTrails at all sublevels ....
Payload configuration. It start the Payload Configuration application (see chapter 17)
All Paths. It corresponds to the pulldown command Browse:Paths:all in Phys. connection .....
SH view. Available only for adms, it shows the equipment view on SH (see 1353SH documentation)
Path Creation. It corresponds to the pulldown command Path:Create ....
Add legs. It start the Add legs application (see chapter 21 )
Alarmed objects. It corresponds to the pulldown command Browse:Alarmed objects
Setup Trail. It corresponds to the pulldown command Supervision:Setup trail (see chapter 18 ).
Naps filtered. It corresponds to the pulldown command Browse:NAPS:filtered
HOCtps. It corresponds to the pulldown command Browse:HOCtps .
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 16 / 230

230
3.1.2 Popup menus

From the map the popup menu can be opened on each topological object. The actions available per each
object are described in the paragraphs which follow.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

In most of the cases the browser is started giving the list or the graphical view invoked by the selected
command. The explanation of the Browser windows can be found at chapter 13 of this section.

3.1.2.1 Network popup menu

The Network popup menu, ( see Figure 4. as an example), contains the following submenus:

Browse object... It corresponds to the pulldown command Browse:Object(s)

Main items:paths in topology. This menu starts a browser instance displaying the list of the paths
belonging to the selected topological object.
Main items:Trails at all sublevels.This menu starts a browser instance displaying the list of all
trails belonging to the selected network.
Main items:User defined HOtrails at all sublevels.This menu starts a browser instance
displaying the list of all the user defined HO trails belonging to the selected network.
Main items: Alarmed objects. This menu starts a browser instance displaying the filtered list of the
following alarmed objects: nap,cap, ctp, msCtpCap, port, ne. The filter can be set by means of the
popup menus Main/All items ( Filtered Query ). The allowed filtering parameters are: alarm status,
consistency status and direction.
Main items: All Rings. This menu starts a browser instance displaying the list of all rings belonging
to the selected topological object.
Main items: All Nodes.This menu starts a browser instance displaying the list of all nodes belonging
to the selected topological object.
Main items: All physical connections in Network. This menu starts a browser instance displaying
the list of the physical connections interconnecting the subnetworks belonging to the selected
network..

All items: Physical Connections . Same as above Main items: All physical connections in
Network
All items: Trails at all sublevels. Same as above Main items:Trails at all sublevels.
All items: User defined HOtrails at all sublevels. Same as above Main items:User defined
HOtrails at all sublevels.
All items: HO LCs in the topology. This menu starts a browser instance displaying the list of all the
user defined HO LCs belonging to the selected network.
All items: Routing Links. This menu starts a browser instance displaying the list of all the routing
links belonging to the selected network.
All items: Not consistent tps and connections in topologies. This menu starts a browser
instance displaying the list of Not consistent tps and connections in topology.
All items: Alarmed objects. Same as above Main items: Alarmed objects.
All items: Paths in topology. Same as above Main items:paths in topology.
All items: Paths in topology (with Source/Sink) This menu starts a browser instance displaying
the list of the paths ( with source and sink ), belonging to the selected network.
All items: Subnetworks. This menu starts a browser instance displaying the list of the subnetworks
belonging to the selected network.
All items: All Rings. This menu starts a browser instance displaying the list of the rings belonging
to the selected network.
1AA 00014 0004 (9007) A4 ALICE 04.10

All items: All Nodes. This menu starts a browser instance displaying the list of the nodes belonging
to the selected network.

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 17 / 230

230
All items: All physical connections in Network. This menu starts a browser instance displaying
the list of the physical connections belonging to the selected network.

not permitted without written authorization from Alcatel.


Main items ( Filtered query ) This menu contains the same options listed above for the Main items

All rights reserved. Passing on and copying of this


document, use and communication of its contents
menu. In addition a query filter is provided in order to obtain a filtered list.
All items ( Filtered query ). This menu contains the same options listed above for the All items
menu. In addition a query filter is provided in order to obtain a filtered list.

Figure 4. Network popup menu.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 18 / 230

230
3.1.2.2 Subnetwork popup menu

The Subnetwork popup menu ( see Figure 5. as an example), contains the following submenus:
not permitted without written authorization from Alcatel.

Browse object... It corresponds to the pulldown command Browse:Object(s) .


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Main items:Paths in topology. This menu starts a browser instance displaying the list of the paths
belonging to the selected topological object.

Main items:Trails at all sublevels.This menu starts a browser instance displaying the list o trails
interconnecting the subnetworks belonging to the selected network.

Main items:User defined HOtrails at all sublevels.This menu starts a browser instance
displaying the list of all the user defined HO trails belonging to the selected topological object.

Main items: Alarmed objects. This menu starts a browser instance displaying the filtered list of the
following alarmed objects: nap,cap, ctp, msCtpCap, port, ne. The filter can be set by means of the
popup menus Main/All items ( Filtered Query ). The allowed filtering parameters are: alarm status,
consistency status and direction.

Main items: All Rings This menu starts a browser instance displaying the list of the rings belonging
to the selected subnetwork.

Main items: All Nodes. This menu starts a browser instance displaying the list of the nodes
belonging to the selected subnetwork.

All items: Physical Connections . Same as above Main items: All physical connections in
Network

All items: Trails at all sublevels. Same as above Main items:Trails at all sublevels.

All items: User defined HOtrails at all sublevels. Same as above Main items:User defined
HOtrails at all sublevels.

All items: HO LCs in the topology. This menu starts a browser instance displaying the list of all the
user defined HO LCs belonging to the selected network.

All items: Routing Links. This menu starts a browser instance displaying the list of all the routing
links belonging to the selected network.

All items: Not consistent tps and connections in topologies. This menu starts a browser
instance displaying the list of Not consistent tps and connections in topology.

All items: Alarmed objects. Same as above Main items: Alarmed objects.

All items: Paths in topology. Same as above Main items:paths in topology.

All items: Paths in topology (with Source/Sink) This menu starts a browser instance displaying
the list of the paths ( with source and sink ), belonging to the selected subnetwork.

All items: All Rings. Same as above Main items: All Rings.

All items: All Nodes. Same as above Main items: All Nodes.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 19 / 230

230
Main items ( Filtered query ) This menu contains the same options listed above for the Main items
menu. In addition a query filter is provided in order to obtain a filtered list.

All items ( Filtered query ). This menu contains the same options listed above for the All items

not permitted without written authorization from Alcatel.


menu. In addition a query filter is provided in order to obtain a filtered list.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
Figure 5. Subnetwork popup menu.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 20 / 230

230
3.1.2.3 Elementary Topology popup menu

The Elementary Topology popup menu ( see Figure 6. as an example), contains the following submenus:
not permitted without written authorization from Alcatel.

Browse object... It corresponds to the pulldown command Browse:Object(s).


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Main items:Paths in topology. This menu starts a browser instance displaying the list of the paths
belonging to the selected topological object.

Main items: Nodes in topology. This menu starts a browser instance displaying the list of all nodes
belonging to the selected topological object.

Main items:Trails at all sublevels.This menu starts a browser instance displaying the list of the
trails interconnecting the nodes belonging to the selected topology.

Main items:User defined HOtrails at all sublevels.This menu starts a browser instance
displaying the list of all the user defined HO trails belonging to the selected topological object.

Main items: Physical Connections. This menu starts a browser instance displaying the list of the
physical connections interconnecting the the nodes belonging to the selected topology.

Main items: HO LCs in the topology. This menu starts a browser instance displaying the list of all
the user defined HO LCs belonging to the selected network.

Main items: All Protection Blocks in MSSpring. This menu starts a browser instance displaying
the view of the protection blocks in MSSpring.

Main items: Alarmed objects. This menu starts a browser instance displaying the filtered list of the
following alarmed objects: nap,cap, ctp, msCtpCap, port, ne. The filter can be set by means of the
popup menus Main/All items ( Filtered Query ). The allowed filtering parameters are: alarm status,
consistency status and direction.

All items: Nodes in topology. Same as above Main items: Nodes in topology

All items: Physical Connections. Same as above Main items: Physical Connections.

All items: Trails at all sublevels. Same as above Main items:Trails at all sublevels.

All items: User defined HOtrails at all sublevels. Same as above Main items:User defined
HOtrails at all sublevels.

All items: HO LCs in the topology. Same as above Main items: HO LCs in the topology.

All items: Routing Links. This menu starts a browser instance displaying the list of the routing links
belonging to the selected topology.

All items: All Protection Blocks in MSSPRING. Same as above Main items: All Protection
Blocks in MSSpring.

All items: Not consistent tps and connections in topologies. This menu starts a browser
instance displaying the list of Not consistent tps and connections in topologies.

All items: Alarmed objects. Same as above Main items: Alarmed objects.

All items: Paths in topology. Same as above Main items:Paths in topology.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 21 / 230

230
All items: Paths in topology (with Source/Sink) This menu starts a browser instance displaying
the list of the paths ( with source and sink ), belonging to the selected subnetwork.

Main items ( Filtered query ) This menu contains the same options listed above for the Main items

not permitted without written authorization from Alcatel.


menu. In addition a query filter is provided in order to obtain a filtered list.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
All items ( Filtered query ). This menu contains the same options listed above for the All items
menu. In addition a query filter is provided in order to obtain a filtered list.

Figure 6. ET popup menu.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 22 / 230

230
3.1.2.4 Physical Connection popup menu

The Physical Connection popup menu, ( see Figure 7. as an example), contains the following
submenus:
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Browse object... It corresponds to the pulldown command Browse:Object(s).

Active Paths. This menu starts a browser instance displaying the list of the active paths in the
Physical Connection.

Main items:Physical Connection structure This menu starts a browser instance displaying the
view of the Physical Connection structure.

Main items: Paths in physical connection. This menu starts a browser instance displaying the list
of the paths in the Physical Connection.

Main items: Paths in physical connection (with Source/Sink). This menu starts a browser
instance displaying the list of the paths (with Source/Sink) in the Physical Connection.

Main items: Alarm profile. This menu starts a browser instance displaying the icon of the alarm
profile actually assigned to the selected physical connection.

All items: Connected Topologies. This menu starts a browser instance displaying the connected
topologies ( physical connections )

All items: Connected Nodes. This menu starts a browser instance displaying the connected nodes.

All items: Paths in physical connection. Same as above Main items: Paths in physical
connection.

All items: MS Trail. This menu starts a browser instance displaying the list of the MS Trails in the
Physical Connection.

All items: HO Trail. This menu starts a browser instance displaying the list of the HO Trails in the
Physical Connection.

All items: Active Paths in Physical Connection .Same as above Active Paths.

All items: Physical Connection structure. Same as above Main items:Physical Connection
structure.

All items: Paths in physical connection (with Source/Sink). Same as above Main items: Paths
in physical connection (with Source/Sink).

All items: Active Paths in physical connection (with Source/Sink). Same as above Main items:
Paths in physical connection (with Source/Sink).

All items: Alarm profile. Same as above Main items: Alarm profile.

Main items ( Filtered query ) This menu contains the same options listed above for the Main items
menu. In addition a query filter is provided in order to obtain a filtered list.

All items ( Filtered query ). This menu contains the same options listed above for the All items
menu. In addition a query filter is provided in order to obtain a filtered list.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 23 / 230

230
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 H
SC.7:GRAPHICAL INTERFACE

230
3AL 61259 AA AA
Figure 7. Physical connection main items popup menu.

24 / 230
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
3.1.2.5 Node popup menu

The Node popup menu ( see Figure 8. as an example) contains the following submenus:
not permitted without written authorization from Alcatel.

Add Legs. This menu starts the Add Leg application. See Chapter 21 of this section.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Browse object... It corresponds to the pulldown command Browse:Object(s).


Assigned Ports. This menu starts a browser instance displaying the list of the ports of the selected
node, whose Assignment State is equal to Assigned.
Main items:Paths in topology. This menu starts a browser instance displaying the list of the paths
belonging to the selected topological object.
Main items: Alarmed objects. This menu starts a browser instance displaying the filtered list of the
following alarmed objects: nap,cap, ctp, msCtpCap, port, ne. The filter can be set by means of the
popup menus Main/All items ( Filtered Query ). The allowed filtering parameters are: alarm status,
consistency status and direction.
Main items: Node View. This menu starts a browser instance displaying the graphical view of the
selected node.
Main items: Path starting(ending) from(in)node. This menu starts a browser instance displaying
the list of the paths terminated to the selected topological object.
Main items: Ports in node. This menu starts a browser instance displaying the list of the ports of
the selected node.
Main items: All naps. This menu starts a browser instance displaying the list of the naps of the
selected node.
Main items: MSTPs. This menu starts a browser instance displaying the list of the MSTPs of the
selected node.

All Items:Not consistent tps and connections in topologies. This menu starts a browser
instance displaying the list of Not consistent tps and connections in topologies belonging to the
selected node.
All items: Alarmed objects. Same as above Main items: Alarmed objects.
All items: Paths in topology. Same as above Main items:Paths in topology.
All items: Paths in topology (with Source/Sink). This menu starts a browser instance displaying
the list of the paths (with Source/Sink) belonging to the selected node.
All items: All Naps. Same as above Main items: All naps.
All items: End Points. It gives the list of all end points belonging to the selected node.
All items: CTPs .It gives the list of all CTPs belonging to the selected node.
All items: Connections in the topology. This menu starts a browser instance displaying the list of
the Connections in the topology.
All items: High Order CTPs. This menu starts a browser instance displaying the list of the High
Order CTPs belonging to the selected node.
All items: Low Order CTPs. This menu starts a browser instance displaying the list of the Low Order
CTPs belonging to the selected node.
All items: MSTPs. This menu starts a browser instance displaying the list of the MSTPs belonging
to the selected node.
All items: MSSPRING Protection Block. This menu starts a browser instance displaying the icon
of the protection block associated to the node.
All items: Path starting(ending) from(in)node. See above Main items:Path starting(ending)
from(in)node
All items: Ports in node. This menu starts a browser instance displaying the list of the ports
belonging to the node.
All items: Network Element. This menu starts a browser instance displaying in the browser window
the Network Element associated to the selected node.
1AA 00014 0004 (9007) A4 ALICE 04.10

All items: Node view. This menu starts a browser instance displaying the graphical view of the
selected node.

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 25 / 230

230
All items: Path starting(ending) from(in)node(with Source/Sink). This menu starts a browser
instance displaying the list of the paths (with Source/Sink) terminated to the selected node.
All items: Naps (with Path label). This menu starts a browser instance displaying the list of the naps
(with belonging to the node.

not permitted without written authorization from Alcatel.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
Main items ( Filtered query ) This menu contains the same options listed above for the Main items
menu. In addition a query filter is provided in order to obtain a filtered list.
All items ( Filtered query ). This menu contains the same options listed above for the All items
menu. In addition a query filter is provided in order to obtain a filtered list.
Main items: Alarm profile. This menu starts a browser instance displaying the icon of the alarm
profile actually assigned to the selected physical connection.

All items: Connected Topologies. This menu starts a browser instance displaying the connected
topologies ( physical connections )
All items: Connected Nodes. This menu starts a browser instance displaying the connected nodes.
All items: Paths in physical connection. Same as above Main items: Paths in physical
connection.
All items: MS Trail. This menu starts a browser instance displaying the list of the MS Trails in the
Physical Connection.
All items: HO Trail. This menu starts a browser instance displaying the list of the HO Trails in the
Physical Connection.
All items: Active Paths in Physical Connection .Same as above Active Paths.
All items: Physical Connection structure. Same as above Main items:Physical Connection
structure.
All items: Paths in physical connection (with Source/Sink). Same as above Main items: Paths
in physical connection (with Source/Sink).
All items: Active Paths in physical connection (with Source/Sink). Same as above Main items:
Paths in physical connection (with Source/Sink).
All items: Alarm profile. Same as above Main items: Alarm profile.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 26 / 230

230
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
01

957.130.872 H
SC.7:GRAPHICAL INTERFACE
Figure 8. Node pop up menu.

230
3AL 61259 AA AA
27 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 H
SC.7:GRAPHICAL INTERFACE

230
3AL 61259 AA AA
28 / 230
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
4 SDH NETVIEW : MAP SUBMENU

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

The Map pulldown menu allows to select one of the following items (see Figure 9. ):

Map: Maps

Map: Submap

Map: Refresh Map

Map: Map Redo

Map: Distribute Maps

Map: Close Submap

Map: Exit

Figure 9. Map pull down menu


1AA 00014 0004 (9007) A4 ALICE 04.10

Note: A Map is a logical structure of the network, tree like, which includes: Network, Subnetwork,
ElementaryTopology, Node, EMLs, Network Element, Port.

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 29 / 230

230
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01
New...

Delete...
Open/List...
4.2 Map: Maps

Save Map As...

Describe/Modify...

957.130.872 H
This menu allows to further select among:

SC.7:GRAPHICAL INTERFACE

230
3AL 61259 AA AA
30 / 230
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.1 Map: Maps: Open/List ...

SCOPE
not permitted without written authorization from Alcatel.

Open a map from the list of available maps. Before the chosen map opens, HP OpenView Windows saves
All rights reserved. Passing on and copying of this
document, use and communication of its contents

and closes the currently open map. Maps may be open with readonly or readwrite access.

SEQUENCE

1) Selecting Map: Maps: Open/List... displays the Available Maps dialog box which gives a list
of the available maps. ( see Figure 10. )

Figure 10. Available Maps

2) To open a map:
a ) Select the name of the map you want to open and click the [Open Map] button.

A confirmation box appears.


b ) Click [OK].

OpenView Windows closes all submap windows and dialog boxes of the open map. Then, HP OpenView
Windows opens the selected map.
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 11. Open View Windows Warning

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 31 / 230

230
4.2.2 Map: Maps: New

SCOPE

not permitted without written authorization from Alcatel.


Create a new map and configure basic map characteristics.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
CONDITIONS

Selecting Map: Maps: New... displays the New Map dialog box of Figure 12.
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 12. File:New Map dialog box

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 32 / 230

230
The New Map... dialog box contains the following fields:

Name. Mandatory, readwrite field


not permitted without written authorization from Alcatel.

Enter text in this field for the name of the map. This name will be used by Netview to identify the map. Every
All rights reserved. Passing on and copying of this
document, use and communication of its contents

map must have a unique name. You can change the name of the map any time the map is opened with
readwrite access.

Layout for Root Submap. Readwrite

Displays the layout of the Root submap. The initial setting is Row/Column. You can choose the layout for
the root submap only during map creation. To change the layout, press the Option button to display the
menu of possible layouts, and choose the desired layout.

You can select among: None, Row/Column, Point to point, Bus, Star, Ring.

It is strongly suggested to set to None in order to displace the objects in the map without any
constraints. In this case objects will appear in the New Object Holding Area. The operator will drag them
to the suitable position.

Compound Status

You can modify the Compound Status scheme for the map open with read/write access.The Compound
Status scheme determines how Netview propagates status from symbols in child submaps to symbols of
the parent object.

The compound status setting applies to the entire map. You may choose one of the three settings using
the radio buttons:

Default

Propagate Most Critical. MANDATORY

Propagate At Threshold Value (0 100%)

Configurable Applications

Configurable Applications lists network and system management applications that are installed on the
OpenView platform. You can configure each application differently for each map.

To configure an application, select an application and click the [Configure For This Map...] button.

Select the application Map Management and click on Configure for This Map... button. The configuration
window is displayed.

Configure For This Map...

Displays a Configuration dialog box for the application. The Configuration dialog box contains
configuration settings that are specific to that application.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 33 / 230

230
The following configuration settings are available:

Type of SDH network synchronization enabled for this map . Three popup options are selectable:

not permitted without written authorization from Alcatel.


Unset. If this option is selected the operator will not be able to perform any operations of

All rights reserved. Passing on and copying of this


document, use and communication of its contents
alignment of the local (WS) OVW data base to the SNML_IM data base.
Synchronize complete map (Map and Alarm Synchronization). If this option is selected the
operator will be able to perform operations of alignment of the local (WS) OVW data base to
the SNML_IM data base.
Syncronize Only Alarm on map.( DEFAULT) If this option is selected, the operator will be
able to perform operations of alarrm alignment of the local (WS) OVW data base to the
SNML_IM data base.

SDH network synchronization by site for this map, (DEFAULT=FALSE) if true, means that the
alignment will be executed geographically. If false will be executed logically. This field is effective only
if SDH network synchronization is enabled. Note that on geographical map only view operation can
be performed.

SDH synchronize ports for this map (DEFAULT=TRUE) means alignment of the local OVW data to
SNML_IM data for the data relevant to the ports.

SDH set attribute in creation enabled (DEFAULT=FALSE) means that the application will open the
View/Set attributes for each object added. (Not used)

SDH delete operation enabled on implemented object (DEFAULT=FALSE), if true means that it is
not possible to delete an object implemented. Deletion is only possible in OVwDb.

SDH Show uselabel on Layered map (DEFAULT=FALSE). If set to Enabled, in the layered maps the
user label is displayed with the payload structure, otherwise only the payload is displayed.

SDH Enable Synchronization Log. If true means that the system will provide a report for each
sinchronization occurrance.

SEQUENCE

To create a map:

a) Select Map:Maps: New

The New Map dialog box appears.

b) Enter a name for the new map.

c) Modify map settings, such as the layout of the root submap, or the applications to configure, if
desired.

d) In the Configuration window select Verify. If the parameters entered are correct, the following
message will appear in the Messages area :

All values are OK. The Messages area contains also notes which detail the values set above.

e) Click [OK]. The Configuration window is closed automatically.

f) Select OK in the New Map dialog box .


1AA 00014 0004 (9007) A4 ALICE 04.10

OpenView Windows creates the new map. A warning box is displayed informing the operator that the new
map has been created and giving him the choice of opening it or remaining in the current map.

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 34 / 230

230
4.2.3 Map: Maps: Save Map As...

This menu allows you to make a copy of the open map and save it under a new name.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents

4.2.4 Map: Maps: Describe/Modify Map...

PURPOSE

Display and/or modify characteristics of the open map.

Name of map

Name of Home Submap

Compound Status

Configuration of Applications

Comments

PREREQUISITES

Map must be opened with readwrite access to modify any map characteristics.

CONDITIONS

You can view and/or modify the following characteristics from the open map:

Name

Name assigned to the map. Each map must have a unique name.

Home Submap

Name of the submap that is displayed when the map is open. When a map is first created, the home
submap is the root submap.

Click [Submap List...] to display the Submaps in Map dialog box, which lists the submaps of the open map.
To choose a submap as the home submap, select the desired submap name, and click the [Set As Home]
button.

Compound Status

Default

Propagate Most Critical : Mandatory

Propagate At Threshold Value


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 35 / 230

230
Configurable Applications

Configurable Applications lists network and system management applications that are integrated with
OVW. You can configure each application differently for each map.

not permitted without written authorization from Alcatel.


To configure an application, select an application and click the [Configure For This Map...] button.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
The Configuration dialog box for the selected application is displayed. The Configuration dialog box
contains configuration settings that are specific to that application.
Applications may provide help information that is available from the dialog box [Help] button.
The only configurable application is Maps Management.

N.B. The Save Map As... command can be used as follows:

1) The operator logged on WS1 as snml, working on MAP1 with READ/WRITE access saves this
map by entering the command: Map: Maps: Save Map As... and assignes it the name MAP2.

2) An other operator logged on WS2 as snml can open MAP2 with READ/WRITE access.

3) The operator on WS1 creates a new topological object and places it on the map.

4) The operator on WS2 can display the new object in this new Object Holding Area.

5) The operator on WS1 issues Supervision: Placement: Store

6) The operator on WS2 issues Supervision: Placement: Retrieve, thus displaying the new object
in the desired position.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 36 / 230

230
4.2.5 Map: Maps: Delete...

SCOPE
not permitted without written authorization from Alcatel.

Deleting a map deletes all symbols and submaps in the map.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

PREREQUISITES

You must have readwrite permission to delete a map.

CONDITIONS

All objects in the map are deleted unless those objects are represented by symbols in another map.

SEQUENCE

To delete a map:

a) Select Map: Maps: Delete...The Available Maps dialog box appears.

b) Select the name of the map that you want to delete and click [Delete Map].

A confirmation box appears.

c) Click [OK].

OpenView Windows deletes the map along with submaps and symbols, in that map.

DELETING THE OPEN MAP

When OpenView Windows is running, a map is always open. If you choose to delete the open map, the
following conditions occur:

The open map is closed and deleted. The User Default Map is opened.

If the open map you are deleting is the User Default Map, the map named Default is opened. It
becomes your new User Default Map.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 37 / 230

230
4.3 Map: Submap

This menu allows to further select among:

not permitted without written authorization from Alcatel.


Open/List...

All rights reserved. Passing on and copying of this


document, use and communication of its contents
New...

Describe/Modify...

Set this Submap As Home Delete...

Delete..

Delete this submap

Figure 13. Map: Submap pulldown menu

4.3.1 Map: Submap: Open/List...

Open a submap from the list of available submaps in the open map.

It is not advisable to use this menu.

4.3.2 Map: Submap : New...

Create a new submap of the open map.

It is not advisable to use this menu.

4.3.3 Map: Submap: Describe/Modify...

View and/or modify basic characteristics about the submap.

This menu gives the description of the main characteristics of the current submap. In particular it can be
used to add a graphical background. See description at Paragraph 5.1 Creating a geographical map
1AA 00014 0004 (9007) A4 ALICE 04.10

of section OPERATION.

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 38 / 230

230
4.3.4 Map: Submap: Set This Submap As Home

You can specify the submap that is displayed when the map is opened.
not permitted without written authorization from Alcatel.

It is not advisable to use this menu.


All rights reserved. Passing on and copying of this
document, use and communication of its contents

4.3.5 Map: Submap: Delete...

Delete a submap from the list of submaps in the open map.

WARNING

For more detailed information refer to HPOV Users Guide.

4.3.6 Map: Submap: Delete This Submap...

It is not advisable to use this menu.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 39 / 230

230
4.4 Map: Refresh Map

PURPOSE

not permitted without written authorization from Alcatel.


Update the topology of a map open with readonly access.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
PREREQUISITES

Refresh Map applies only to maps opened with readonly access.

DESCRIPTION

Maps open with readonly access do not automatically receive updates on topological events such as the
addition or deletion of symbols, objects, or submaps, or the relocation of symbols by applications or other
users.

You can update the topology of a map open with readonly access by selecting File:Refresh Map. When
a map is refreshed all dialog boxes and submaps are first closed.

Status

Refresh Map is not required to update status. OpenView Windows automatically updates the status of all
symbols and objects in all submaps of the map.

PROCEDURE

To update the map topology:

a) Select Map: Maps: Refresh Map. OpenView Windows updates the topology of the open map.

TROUBLESHOOTING

The Refresh Map button is greyed in a submap window of a snapshot and a map opened with read/write
access.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 40 / 230

230
4.5 Map:Map Redo

This menu ( see Figure 14. herebelow ), allows to further select among:
not permitted without written authorization from Alcatel.

Store: Map
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Store: Map (no connections)

Store: Submap

Store: Submap (no connections)

Execute

Figure 14. Map pull down menu.

The above menus are detailed in the following.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 41 / 230

230
4.5.1 Map: Map Redo: Store Map

SCOPE

not permitted without written authorization from Alcatel.


This command allows to store the commands required to create all topological objects contained in the

All rights reserved. Passing on and copying of this


document, use and communication of its contents
map on both ovwdb and mibdb.

SEQUENCE

1) From the map pulldown menu bar select Map: Map Redo: Store: Map. The Map Redo Store
dialog box is presented.

2) Enter the name of the saved map ( it can be the same or different from the name of the map
being saved) and click on OK button. Subsequent messages are presented to the user, namely:

Insert data and Copy Map <mapname> completed susccessfully . See Figure 15.

Figure 15. Map Redo Store dialog box.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 42 / 230

230
4.5.2 Map: Map Redo: Store Map (no connections)

SCOPE
not permitted without written authorization from Alcatel.

This command allows to store the commands required to create all topological objects contained in the
All rights reserved. Passing on and copying of this
document, use and communication of its contents

map on both ovwdb and mibdb. This option does not store any connection.

SEQUENCE

The sequence of the commands is the same as per paragraph 4.5.1 on page 42.

4.5.3 Map: Map Redo: Store Submap

SCOPE

This command allows to store the commands required to create all topological objects contained in the
submap on both ovwdb and mibdb.

SEQUENCE

The sequence of the commands is the same as per paragraph 4.5.1

N.B. The connections terminated outside the current submap are not saved.

4.5.4 Map: Map Redo: Store Submap (no connections)

SCOPE

This command allows to store the commands required to create all topological objects contained in the
submap on both ovwdb and mibdb. This option does not store any connection.

SEQUENCE

The sequence of the commands is the same as per paragraph 4.5.1

N.B. The connections terminated outside the current submap are not saved.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 43 / 230

230
4.5.5 Map: Map Redo: Execute

SCOPE

not permitted without written authorization from Alcatel.


This command allows to execute all the commands previously stored by issuing the menu Map: Redo:

All rights reserved. Passing on and copying of this


document, use and communication of its contents
Store. This command can be applied to execute whichever map or submap, with or without connections.

CONDITIONS

IThe execute of a complete map ( with or without connections ) must be performed on an empty map.

IThe execute of a submap ( with or without connections ) must be performed on the submap window
consistent with the topological tree.

SEQUENCE

1) From the map pulldown menu bar select Map: Map Redo: Execute. The List of saved maps
is displayed, as per Figure 16. on page 44.

Figure 16. List of saved maps.

2) Select the map to execute from the list and click on Get button. The command file describing
the object contained in the map/submap tp execute is launched and the relevant report is
displayed, as per Figure 17. on page 45. The involved objects are created in the mib data base
and the map/submap is automatically populated.
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 44 / 230

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

Figure 17. Execute map report.

Notice that the user has to adjust manually the object position in the map by dragging each object from
the new object holding area to the map working area. See Figure 18. on page 46
1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 45 / 230

230
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01

957.130.872 H
SC.7:GRAPHICAL INTERFACE
Figure 18. Map: Map Redo: Execute: dragging nodes

230
3AL 61259 AA AA
46 / 230
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 Map:Distribute Maps

The Map: Distribute Maps menu item allows to execute the following operations on the maps:
not permitted without written authorization from Alcatel.

Map:Distribute Maps:Store map image


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Map:Distribute Maps:Get/List map image

Map:Distribute Maps:Remove map image

Map:Distribute Maps:Lock map image

Map:Distribute Maps:Unlock map image

Map:Distribute Maps: Modify Username List

Figure 19. Map:Distribute Maps menu items.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 47 / 230

230
4.6.1 Map :Distribute Maps: Store Map Image

PURPOSE

not permitted without written authorization from Alcatel.


The purpose of this procedure is to save a map in the central mapDb repository.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
CONDITIONS

The map is codified into an ASCII format.

The Store Map dialog window allows to select:

Map name. Digit the map name.The default name is the current map name.

Username List. It is the list of the users which are allowed to read this map. Default ALL Users.
The items of the list are separated by a comma or a blank.
If the map was previously locked, this command causes its automatic unlock.

SEQUENCE

a) In the Network Window select Map:Distribute Maps:Store map image. The Store Map dialog window
is displayed. ( see Figure 20. )

Figure 20. Store Map dialog box.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 48 / 230

230
b) Enter the selection parameters (see above point CONDITIONS)

c) Selecting OK the Work in progress message is displayed in the message Area.


not permitted without written authorization from Alcatel.

After a few seconds the messages Current Map is stored in SNLMAP DB and Copy Map successful
All rights reserved. Passing on and copying of this
document, use and communication of its contents

ly completed. A message is sent to the users included in the Username list.

Selecting Cancel the selection window is closed without any further action.

Selecting Help the description of the relevant menu option is displayed.


1AA 00014 0004 (9007) A4 ALICE 04.10

ED 01 SC.7:GRAPHICAL INTERFACE

957.130.872 H 3AL 61259 AA AA 49 / 230