1354rm52b Manual Del Operador Vol 2

QUESTA PAGINA NON VA INSERITA NEL MANUALE
All rights reserved. Passing on and copying of this

document, use and communication of its contents
not permitted without written authorization from Alcatel.
THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

COD.MANUALE HDBK P/N: 957.130.872
1300NM
1354RM Rel.5.2B
OPERATORS HANDBOOK
H Ed.01 3AL 61259 AAAA Ed.01
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
(facciate)
No pages
1AA 00014 0004 (9007) A4 ALICE 04.10
fase
step
numerate
numbered
da from
a to
182
1/182
182/182
230
1/230
230/230
1/96
96/96
ASSEMBLARE VOL.1/2 ASSEMBLE VOL.1/2
TARGHETTE - LABELS
FRONTESPIZIO - FRONT
INSERIRE SEPARATORE 6 - INSERT REGISTER 6
SC.6: MAINTENANCE
SC.7: GRAPHICAL INTERFACE
SC.8: SMF
96
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES:
510
TOTALE FOGLI A4 TOTAL A4 SHEETS:
255
WARNING FOR A-UNITS OTHER THAN A-ITALY
ED
Labels are done according to A-Italy binder format.

Source file: ALICE 6.10
01
VOL.2/2 RELEASED
957.130.872 TQZZA
3AL 61259 AAAA TQZZA

4
1/ 4
QUESTA PAGINA NON VA INSERITA NEL MANUALE
Site
VIMERCATE

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
ALCATEL OPTICS GROUP TND
Originators
V.PORRO
ERBA,CRIPPA
FERRARI,MANCINI
1354RM REL.5.2B
OPERATORS HANDBOOK
Domain
Division
Rubric
Type
Distribution Codes
:
:
:
:
NETWORK MANAGEMENT
1354RM REGIONAL MANAGER
REL.5.2B
1354RM REL.5.2B OPERATORS HANDBOOK
Internal :
External
:
Approvals
Name
App.
M.RAGNI
E.CORRADINI
F.CASASOLE
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Regional Network Manager for SDH and Optical Networks

OPERATORS HANDBOOK
ED
01
VOL.2/2 RELEASED
957.130.872 TQZZA

4
2/ 4

1300NM
1354RM Rel.5.2B
OPERATORS HANDBOOK
957.130.872 H Ed.01
3AL 61259 AAAA Ed.01
VOL.2/2
1300NM
1354RM Rel.5.2B
OPERATORS HANDBOOK
957.130.872 H Ed.01
VOL.2/2
1300NM
1354RM Rel.5.2B
957.130.872 H Ed.01
OPERATORS HANDBOOK
VOL.2/2
1300NM
1354RM Rel.5.2B
957.130.872 H Ed.01
OPERATORS HANDBOOK
VOL.2/2
1300NM
1354RM Rel.5.2B
1AA 00014 0004 (9007) A4 ALICE 04.10

957.130.872 H Ed.01
ED
01
OPERATORS HANDBOOK
VOL.2/2
VOL.2/2 RELEASED
957.130.872 TQZZA

4
3/ 4
1AA 00014 0004 (9007) A4 ALICE 04.10
FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT
ED
01
VOL.2/2 RELEASED
957.130.872 TQZZA
4/ 4
Operators Handbook
Alcatel 1300NM
Network Management
1354RM Rel.5.2B
Volume 2/2:
sections 68
957.130.872 H Ed.01
957.130.872 H Ed.01

TABLE OF CONTENTS
1AA 00014 0004 (9007) A4 ALICE 04.10
01
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Purpose of the document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audiance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
7
7
7
2 FAULT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Elementary Alarms and RM Probable Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Alarm Enabling/Disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 Q3 Alarm Enabling/Disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2 QB3* Enabling UPA on specific CTP/CAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.3 Enable / Disable frame supervision alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Alarm Severity Assignment Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1 ASAP list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2 ASAP create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.3 ASAP correlate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.4 ASAP modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Object Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.1 NE Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.2 Port Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.3 MSTP Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.4 MSSpring Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.5 Ne Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.6 HOTTP Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.7 LOTTP Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.8 CTP Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
10
12
12
14
16
17
17
18
19
22
23
23
23
24
24
24
25
26
27
3 INTEGRATION OF 1354RM WITH SEC SECURITY SUBSYSTEM . . . . . . . . . . . . . . . . . . . . . . . .

3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 SEC Architecture on 1354RM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2 SEC Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.3 Alarm Access Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 1330AS customization on 1354RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 Preliminary customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
29
29
30
31
34
35
000721
validated
01A 000515
proposal
ED
DATE
CHANGE NOTE
M.RAGNI ITAVE
E.CORRADINI
M.RAGNI ITAVE
E.CORRADINI
V.PORRO ITAVE
APPRAISAL AUTHORITY
ORIGINATOR
V.PORRO ITAVE
1354RM REL.5.2B
OPERATORS HANDBOOK
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
1 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10
38
48
48
49
52
55
4 INTRODUCTION TO MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Alarm navigation and fault localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Physical connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 MStrail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.3 HOtrail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.4 Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.5 Alarm processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Diagnostic of the main objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Diagnostic of the path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Diagnostic of the trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3 EML Domain Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4 NE Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.5 NE: Consistency Status=Not aligned ( TSDIM ONLY ) . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.6 NE: Consistency Status=Failed to Align ( TSDIM ONLY ) . . . . . . . . . . . . . . . . . . . . . . . .
4.2.7 NE: Consistency Status=Consistency Mismatch ( TSDIM ONLY ) . . . . . . . . . . . . . . . .
4.2.8 NE: NE Communication Problems: NE unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.9 NE Config. Download Status = fail to Disable / Enable . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.10 NE: NEnot EML Aligned_auditfailed / misaligned ( for SENIM ONLY ) . . . . . . . . . . . .
4.2.11 Physical connection diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.12 SDH Port Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.13 SDH port Consistency status ( for SENIM ONLY)=Not found . . . . . . . . . . . . . . . . . . . .
4.2.14 SDH port Consistency status ( for SENIM ONLY)=Unknown . . . . . . . . . . . . . . . . . . . .
4.2.15 SDH port Upload status ( for TSDIM ONLY)=Not found . . . . . . . . . . . . . . . . . . . . . . . .
4.2.16 SDH port Upload status ( for TSDIM ONLY)=Wrong . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.17 Routing link diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.18 Subnetwork diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.19 Ring diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.20 Node diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.21 Payload Configuration Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
62
64
66
68
71
73
74
75
79
83
85
86
86
86
86
86
87
88
90
90
90
90
91
91
92
93
95
97
5 PATH/TRAIL ALLOCATION FAILURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Allocation failure diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1 Show Failure information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.2 Obstacles and Unsatisfied Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.3 Other errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
99
99
100
100
101
114
6 DIAGNOSTIC OF THE NPE RING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1 User Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1 MidProtocol Role ( NODE CONDITION ) attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.2 MidProtocol Role ( NODE CONDITION) attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.3 Allowed combinations of East, West, and MidProtocolRole . . . . . . . . . . . . . . . . . . . . .
6.1.4 Ring Active Condition attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.5 Span Active Condition attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.6 Ring Pending Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.7 Span Pending Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.8 Lockout Working Ring attributes ( not implemented in this release ) . . . . . . . . . . . . . . . .
115
115
117
120
122
125
126
127
128
129
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
2 / 182

3.2.2 Counter customisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Spurious alarm management on 1354RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1 New ASAP definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2 Path Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.3 HOTrail Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.4 Physical Link/MSTrail Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

6.1.9 Lockout Working Span attributes ( not implemented in this version release ) . . . . . . . .
6.1.10 Inhibition chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.11 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
130
131
132
7 LOGGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
145
8 NMLEML CONSISTENCY CHECKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

LIST OF FIGURES AND TABLES
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 51. Example of display of a protected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

TABLES
Table 1. Elementary alarm mnemonics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2. Probable Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3. ConfigurationState, node conditions, and RM display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4. Values of Consistency Status attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5. Starting and final Consistency status given the consistency results for consistency audit
in Mark Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6. Initial and final Consistency status given the consistency results for consistency audit in
Notify Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 INTRODUCTION
1.1 Purpose of the document
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
1AA 00014 0004 (9007) A4 ALICE 04.10
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
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
7 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
8 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10

2 FAULT MANAGEMENT
Alarm messages on elementary objects (nap, cap, ctp, port, mstp) are received from EML, processed and
propagated to the affected objects.
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
9 / 182
Elementary Alarms are described in the documentation of the Network Elements and in the documentation
of the EML OS.
RM Probable Causes are listed in Table 2.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
N.B.
ED
The Elementary alarms reISO. SSF, SSF_In, SSF_Eg apply to TSDIM only.
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
10 / 182

2.1 Elementary Alarms and RM Probable Causes
Table 2. Probable Causes

Probable Cause
Event Type
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Meaning
ED
The Probable Cause reISO applies to TSDIM only.
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
11 / 182
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.
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:
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
12 / 182

2.2 Alarm Enabling/Disabling
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 1. Path: Show/Set Attributes: alarm enabling
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
13 / 182

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
and UPA on CTPs are never received by RM and this prevent a correct alarm from being propagated on
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 2. CAP Alarm Enabling.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
14 / 182

2.2.2 QB3* Enabling UPA on specific CTP/CAP
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 3. CAP: Show/Set Attributes
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
15 / 182


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.
1AA 00014 0004 (9007) A4 ALICE 04.10
By default the frame supervision alarm and the consequent action (AIS) are disabled.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
16 / 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) .
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
A default ASAP is available; when a path, a trail or a physical connection is created, the default
ASAP is assigned.
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
17 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10
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:
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
18 / 182

2.3.2 ASAP create
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
possible sequences is as follows:
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 )
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 7. Correlating paths
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
19 / 182

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).
1AA 00014 0004 (9007) A4 ALICE 04.10
3)
ED
Select the involved profile and click on button Correlate path/trail/physicalConnection to an

Alarm profile.
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
20 / 182

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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 10. The selected Alarm Profile.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
21 / 182
2.3.4 ASAP modify

The user can modify a profile simply issuing a Show/Set Attributes of the profile. See Figure 11.
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
1AA 00014 0004 (9007) A4 ALICE 04.10
remSDHFailure alarm activation

By default this alarm is deactivated since the default ASAP sets it to notAlarmed.
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
182
22 / 182

2.4 Object Alarm Propagation

2.4.1 NE Alarm Propagation
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
SDH Port
Elementary
alarm
RM Object
impacted
RM Object
Severity
Operational
State
RM Probable
LOS / LOF
URU /TrD / TrF
rxF txF
Physical Conn
MSTrail
HOLink Conn
Major
Disabled

MediaEqFail
lowReliability
Physical Conn
note1
Warning
Unchanged
UnderProtDeg
cause
note1: for nonprotected MSTrail the supported HOLCs are set to disabled.
URU
1AA 00014 0004 (9007) A4 ALICE 04.10
PDH Port
Path
Major
Disabled
SDH Failure
LOS LOF
ExBER SD
FERF RAI AIS
Path
Warning
Unchanged
PDH Failure
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
23 / 182
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
( RM Object Impacted ). RM provides for the impacted object the Alarm Severity, the Operational State
and the Probable Cause.
Object
MSTP
unreliable
MSTP
reliable
Elementary
alarm
RM Object
impacted
RM Object
Severity
Operational
State
RM Probable
ExBER
msFERF
msAIS
MSTrail
Major

Disabled

ExBer
RS Failure
HOLink Conn
note1
cause
msSD
lowReliability
MSTrail
Warning

Unchanged

DegSig
UnderProtDeg
Conf. Mismatch
MSTrail
Major
Unchanged
mSconfMismatch
Conf. Mismatch
MSTrail
Major
Unchanged
mSconfMismatch
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
MS
Spring
Elementary
alarm
RM Object
impacted
RM Object
Severity
Operational
State
RM Probable
K1K2PM
Node
Major
Unchanged
Elementary
alarm
RM Object
impacted
RM Object
Severity
Operational
State
RM Probable
neNRreISO
Node
Major
Disabled
cause
2.4.5 Ne Alarm Propagation

Object
1AA 00014 0004 (9007) A4 ALICE 04.10
NE
ED
01
cause
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
24 / 182

2.4.3 MSTP Alarm Propagation

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
ports. If the HOTTP is further structured, it is called HOCAP ( Connection Access Point ).
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
HOTTP
( NAP )
HOTTP
( CAP )
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Elementary
alarm
RM Object
impacted
RM Object
Severity
Operational
State
RM Probable
HPUNEQ
HPSLM/HPPLM
HPUPA/SSF
Path
Major
Disabled
SDH Failure
Threshold15m
Threshold24h
Path
Minor
Unchanged
QualityTC15m
QualityTC24h
Conf. Mismatch
Path
Major
Unchanged
ConfMismatch
HOTrail
Major
Disabled
SDH Failure
LOLink Conn
HPLOM
LOLink Conn.
(TU12 only)
Disabled
Threshold15m
Threshold24h
Conf. Mismatch
HOTrail
Minor
Unchanged
HPUNEQ/Ex
BER
HPSLM/HPPLM
HPUPA/SSF
cause
QualityTC15m
QualityTC24h
Conf. Mismatch
The Elementary Alarm Configuration Mismatch refers to EMLNML misalignment.
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
25 / 182
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
PDH ports.
Object
1AA 00014 0004 (9007) A4 ALICE 04.10
LO
TTP(NAP)
Elementary
alarm
RM Object
impacted
RM Object
Severity
Operational
State
RM Probable
LPUNEQ
LPSLM/LPPTM
LPUPA/ SSF
Path
Major
Disabled
SDH Failure
Threshold15m
Threshold24h
Path
Minor
Unchanged
QualityTC15m
QualityTC24
Conf. Mismatch
Path
Major
Unchanged
ConfMismatch
cause
N.B.
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
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
26 / 182

2.4.7 LOTTP Alarm Propagation

2.4.8 CTP Alarm Propagation

The table lsted below summarizes the alarm propagation for the object CTP ( Connection Termination
Point ).
Boundary CTPs are the CTPs on the boundary of the Network Domain.
Object
HOCTP
HOCTP
Boundary
LOCTP
Elementary
alarm
RM Object
impacted
RM Object
Severity
Operational
State
RM Probable
AULOP
ExBER
HOLink Conn
Disabled
Threshold15m
Threshold24h
Conf. Mismatch
Path or
HOTrail
Minor
Unchanged
QualityTC15m
QualityTC24h
Conf. Mismatch
AULOP
Path / HO Trail
HOLink Conn
LOLink Conn
Major
Disabled
SDH Failure
AUUPA/
SSF_Eg
Path / HOTrail
LOLink Conn
Major
Disabled
SDH Failure
SSF_In /
UNEQ_In /
FERF_In / RDI
Path / HOTrail
N.A.
Unchanged
remSDH Failure
ExBER
Path / HOTrail
Major
Disabled
ExBER
Threshold15m
Threshold24h
Conf. Mismatch
Path/HOTrail
Major
Unchanged
QualityTC15m
QualityTC24h
ConfMismatch
tuLOP/
tuLOM
LOLink Conn
Major
Disabled
Path
N.A.
Unchanged
remSDH Failure
tuUPA/
SSF_Eg
Path
Major
Disabled
SDH Failure
TULOP
TULOM
Path
LOLink Conn
Major
Disabled
SDH Failure
Threshold15m
Threshold24h
Conf. Mismatch
Path
Minor
Unchanged
QualityTC15m
QualityTC24h
ConfMismatch
SSF_In /
UNEQ_In /
FERF_In / RDI
1AA 00014 0004 (9007) A4 ALICE 04.10
LOCTP
Boundary
ED
01
cause
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
27 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10
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
Pointer; LOM=Loss of Multiframe ( Vx bytes ) ; ExBER=Excessive BER ; SSF_Eg=Server
Signal Failure Egressing
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
28 / 182

N.B.

3 INTEGRATION OF 1354RM WITH SEC SECURITY SUBSYSTEM

3.1 Introduction
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
29 / 182
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.
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
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
30 / 182

3.1.2 SEC Administration
3.1.3 Alarm Access Configuration

Depending on 1354RM user definitions the following AS Access Rights are granted:
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:
1AA 00014 0004 (9007) A4 ALICE 04.10
MGT: Users that have this capability, if allowed by the NAD Rule (see below), can manage accessible
alarms ( acknowledgement)
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
31 / 182

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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
32 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10

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
ASHISTUSM_FAD@AsHistoricalUsm :
ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,
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
ASHISTUSM_FAD@AsHistoricalUsm :
as follows:
System_Profile
:
LookOnly
:
ASHISTUSM_FAD@AsHistoricalUsm : ASCURUSM_ALARM_MANAGER_FAD@AsCurrentUsm
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
33 / 182
3.2 1330AS customization on 1354RM
Deactivate the 1330AS standard counters.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Procedures which follow are automatically executed during the installation.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
34 / 182

The main steps of the 1330AS customization on 1354RM are:
3.2.1 Preliminary customization
1AA 00014 0004 (9007) A4 ALICE 04.10

All these customizations are executed per each 1354RMIM .

3.2.1.1 AutoPurging Filter
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
35 / 182
3.2.1.2 Archiving Filter
a)
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
configurationMismatch
Alarm Misaligned
EML not reachable
1AA 00014 0004 (9007) A4 ALICE 04.10
c)
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)
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
36 / 182

3.2.1.3 Auto Acknowledge Filter
1AA 00014 0004 (9007) A4 ALICE 04.10

This procedure is optional.

a)
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)
f)
Click on the Apply button.
g)
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
37 / 182
3.2.2 Counter customisation
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
c)
ED
Select Exit>Save... to save the performed customisation.
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
38 / 182

3.2.2.3 Physical Link Counter


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:
1AA 00014 0004 (9007) A4 ALICE 04.10
p)
ED
Event Date & Time

Friendly Name
EventType
Probable Cause
Perceived Severity
Clearing Status
Ack Status
Reservation Status
Repetition Counter
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
39 / 182
3.2.2.4 MS Trail Counter
a)
b)
c)
d)
Change the name from <new sublist> to MS TRAIL
e)
f)
Arrange Display Attributes in order to provide Event Date & Time (in first position), Friendly Name,
Perceived Severity.
g)
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)
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
1AA 00014 0004 (9007) A4 ALICE 04.10
m ) Press Save... button.

n)
Press Apply button.
o)
Press Close button.
p)
q)
ED
Event Date & Time
Friendly Name
EventType
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
40 / 182

1AA 00014 0004 (9007) A4 ALICE 04.10

Probable Cause
Perceived Severity
Clearing Status
Ack Status
Reservation Status
Repetition Counter
18. Select Exit: Save... to save the performed customisation.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
41 / 182
3.2.2.5 HO Trail Counter
a)
b)
c)
d)
Change the name from <new sublist> to HO TRAIL
e)
f)
Perceived Severity.
g)
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)
k)
causes is provided.
l)
sdhFailure
1AA 00014 0004 (9007) A4 ALICE 04.10

n)
Press Apply button.
o)
Press Close button.
p)
q)
ED
Event Date & Time
Friendly Name
EventType
Probable Cause
Perceived Severity
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
42 / 182

1AA 00014 0004 (9007) A4 ALICE 04.10

r)
ED
Clearing Status
Ack Status
Reservation Status
Repetition Counter
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
43 / 182
3.2.2.6 Path Counter
a)
b)
c)
d)
Change the name from <new sublist> to PATH
e)
f)
Perceived Severity.
g)
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)
k)
causes is provided.
l)
sdhFailure
pdhFailure
1AA 00014 0004 (9007) A4 ALICE 04.10

n)
Press Apply button.
o)
Press Close button.
p)
q)
ED
Event Date & Time
Friendly Name
EventType
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
44 / 182

1AA 00014 0004 (9007) A4 ALICE 04.10

r)
ED
Probable Cause
Perceived Severity
Clearing Status
Ack Status
Reservation Status
Repetition Counter
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
45 / 182
3.2.2.7 Processing Counter
a)
Select the command Sublist>Create.
b)
Select the command Sublist>Modify; a new window is open.
c)
d)
Change the name from <new sublist> to PROCESSING.
e)
f)
Perceived Severity.
g)
h)
Enter the filter name as RM_Processing.
i)
causes is provided.
j)
Alarm Misaligned
EML not reachable
k)
Press Save... button.
l)
Press Apply button.
1AA 00014 0004 (9007) A4 ALICE 04.10
m ) Press Close button.

n)
Select the command Sublist>Activate.
o)
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:
ED
Event Date & Time
Friendly Name
EventType
Probable Cause
Perceived Severity
Clearing Status
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
46 / 182

1AA 00014 0004 (9007) A4 ALICE 04.10
ED

Ack Status
Reservation Status
Repetition Counter
16. Select Exit: Save... to save the performed customisation.
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
47 / 182
3.3 Spurious alarm management on 1354RM
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
48 / 182

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

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.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
49 / 182
Report of elementary alarm correlation

Show Communication alarm

Show the path alarms in route
Create a new alarm profile

Correlate path to an alarm profile
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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
182
50 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10

3.3.2.2 Path commissioning

a)
From the Path List window select the relevant path(s).
b)
Click on Alarm icon in order to make available all the icons relevant for alarm management. Click on
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)
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)
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
51 / 182
3.3.3 HOTrail Management
a)

3.3.3.1 Trail creation

Setup the trail setting Setup Rule = User (N.B. Default value is Automatic).
1AA 00014 0004 (9007) A4 ALICE 04.10
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).
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
52 / 182

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 16. HO Trail ASAP Correlation

d)
If the Indet_Alarm_Profile is already present within the correlation window go to step g).
e)
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)
before). At this point the trail is correlated to the relevant ASAP .
h)
Allocate the trail.
i)
Implement the trail.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
53 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
There is no explicit commissioning on HOTrail. The scope of this phase is to cause the trail to report
alarms to 1330AS.
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)
g)
Profile (the same icon as before). The ASAP icon is inserted into the correlation window.
h)
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
54 / 182

3.3.3.2 Trail commissioning
3.3.4 Physical Link/MSTrail Management
1AA 00014 0004 (9007) A4 ALICE 04.10

3.3.4.1 Physical Link/MSTrail creation

a)
Activate the Physical Connection; this action causes that alarms possibly present on it are
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

The Physical connection implementation creates the MSTrail(s)
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
55 / 182
From the popup menu associated to the Physical Connection select the command Display: All
Related Item.
d)
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 18. Display of associated MSTrail

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).
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
56 / 182

1AA 00014 0004 (9007) A4 ALICE 04.10
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

Alarm>CorrelateAlarmProfile; the MSTrail is added to the correlation window.
ED
01
command
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
57 / 182

Figure 20. Associate ASAP to MSTrail
1AA 00014 0004 (9007) A4 ALICE 04.10
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).
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
58 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10

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

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)
g)
Profile. The ASAP icon is inserted into the correlation window.
h)
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.
ED
01
the
command
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
59 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
60 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10

4 INTRODUCTION TO MAINTENANCE
Maintenance operations consist of several functions that have to be executed following failures on the
network.
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
61 / 182
4.1 Alarm navigation and fault localization
The paths affected by a failure are automatically rerouted on the available route (spare or main).
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
62 / 182

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

The relevant Alarm sublist is presented. Figure 22. shows an example of Physical Connection Alarm
sublist.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 23. Navigation: External Application: 1354RM.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
63 / 182
4.1.1 Physical connection
1AA 00014 0004 (9007) A4 ALICE 04.10

For the Physical connection object the physical connection structure window is presented:
Figure 24. Physical connection structure window
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
64 / 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 25. Alarm details window.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
65 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10

4.1.2 MStrail
The MStrail alarm sublist is shown in Figure 26.
Figure 26. MS Trail alarm sublist.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
66 / 182

For the MStrail object the physical connection structure and relative navigation window is presented:
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 28. Alarm details.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
67 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10

4.1.3 HOtrail
The HOtrail alarm sublist is shown in Figure 29.
Figure 29. HOtrail alarm sublist
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
68 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10

For the HOtrail object the path in trail window and the relevant navigation window is presented:
Figure 30. Paths in trail window
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
69 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 31. Alarm details
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
70 / 182
4.1.4 Path

The Path alarm sublist is shown in Figure 32.
Figure 32. Path alarm sublist
1AA 00014 0004 (9007) A4 ALICE 04.10
For the Path object the Nap view window and relative navigation window is presented:
Figure 33. Path Naps view
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
71 / 182
The severity can be no alarm if the alarm must not be emitted.

An example of Alarms details is shown in Figure 34.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 34. Path Alarm details
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
72 / 182
4.1.5 Alarm processing

In the following is presented the Alarm processing sublist:
Figure 35. Alarm processing sublist
1AA 00014 0004 (9007) A4 ALICE 04.10
For Alarm processing (EML object), only the navigated object is presented in the browser window.
Figure 36. Alarm processing navigation
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
73 / 182
This paragraph describes the diagnostic procedures to be executed for the main RM objects in case of
malfunction.
1AA 00014 0004 (9007) A4 ALICE 04.10
The objects are:
path
trail
EML Domain
NE
Physical Connection
SDH Port
Subnetwork
Ring
Node
Payload
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
74 / 182

4.2 Diagnostic of the main objects
4.2.1 Diagnostic of the path
1AA 00014 0004 (9007) A4 ALICE 04.10

The path diagnostic concerns the following attributes:
Path Alarm status
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
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
75 / 182
CONDITIONS
The path involved is of the broadcast type. The Operator entered an Add Leg
command on the Path involved.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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:
ACTIONS
ED
01
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.
In the second case above described, inspect the EML and NE layers.
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
76 / 182

4.2.1.3 Path: Failed to Add Leg

4.2.1.8 Path: Failed to Allocate

CONDITIONS
The user enters a path 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.1.9 Path: Failed to Deallocate
CONDITIONS
The user entered a Path: Deallocation command.
CAUSES
Software latent errors.
ACTIONS
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
ACTIONS
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
ACTIONS
level.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ACTIONS
1)
2)
ED
01
Identify the protected connection that has failed.

In the Browser navigate up to the EML level.
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
77 / 182
CONDITIONS
The Operator has requested an SNCP management (Forced Switch

Main/Spare/Lockout.
CAUSES
ACTIONS
level.
4.2.1.15 Path: Failed to connect/disconnect
1AA 00014 0004 (9007) A4 ALICE 04.10
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
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
78 / 182

4.2.1.14 Path: Failed to manage SNCPs
4.2.2 Diagnostic of the trail
1AA 00014 0004 (9007) A4 ALICE 04.10

The trail diagnostic concerns the following attributes:
Alarm status
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.
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
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
79 / 182
CONDITIONS
The trail 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.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
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:
ACTIONS
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.
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
1AA 00014 0004 (9007) A4 ALICE 04.10
4.2.2.7 Trail: Failed to Deallocate

CONDITIONS
The user entered a Path: Deallocation command.
CAUSES
Software latent errors.
ACTIONS
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
80 / 182

4.2.2.3 Trail: Failed to Add Protection

4.2.2.8 Trail: Failed to Implement

CONDITIONS
The user entered a Path Implementation command.
CAUSES
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
ACTIONS
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
ACTIONS
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)
2)
Identify the protected connection that has failed.

In the Browser navigate up to the EML level.
1AA 00014 0004 (9007) A4 ALICE 04.10
4.2.2.12 Trail: Failed to manage SNCPs

CONDITIONS
The Operator has requested an SNCP management (Forced Switch

Main/Spare/Lockout.
CAUSES
ACTIONS
level.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
81 / 182
4.2.2.13 Trail: Failed to configure

The working state is Fail to Configure.
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).
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.
ACTIONS
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
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
1AA 00014 0004 (9007) A4 ALICE 04.10
level.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
82 / 182

CONDITIONS
4.2.3 EML Domain Diagnostic

4.2.3.1 EML Alarm status

Regardless the EML alarm status, navigate EML from the Alarm Counter Summary as described at
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
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
ACTIONS
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
83 / 182
CONDITIONS
From Browser the attribute EML Alarms Aligned is false / the attribute EML
Alarms Alignment is Failed / the attribute EML Domain Alignment is Failed.
CAUSES
The possible causes are indicated in the Event Logger.
1AA 00014 0004 (9007) A4 ALICE 04.10
ACTIONS
ED
01
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.
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
84 / 182

4.2.3.3 Alignment False/ Failed
4.2.4 NE Diagnostic

The NE attributes displayed in the browser window are:
Alarm status
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.

NE unreachable.
Configuration Download state

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

neNotEmlAligned_auditfailed
neNotEmlAligned_misaligned
Upload status. for TSDIM ONLY.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Not found=the NE is misaligned about physical objects, such as ports....
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
85 / 182
CONDITIONS
From Browser it is displayed as an icon
CAUSES
The consistency download is probably disabled
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
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
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
ACTIONS
Verify the EML layer
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
86 / 182

4.2.5 NE: Consistency Status=Not aligned ( TSDIM ONLY )
4.2.10 NE: NEnot EML Aligned_auditfailed / misaligned ( for SENIM ONLY )
1AA 00014 0004 (9007) A4 ALICE 04.10

CONDITIONS
From Browser it is displayed as a title
CAUSES
1)
EML/NE erroneously registered
2)
3)
TCPIP problems
1)
Verify EML id/NE address
2)
Restart EML
3)
Verify the workstation physical connections
ACTIONS
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
87 / 182
4.2.11 Physical connection diagnostic
A physical connection failure is denoted by a color variation on the map.

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).
1)
2)
3)

1AA 00014 0004 (9007) A4 ALICE 04.10
ACTIONS
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
88 / 182

4.2.11.1 PhysCon Alarm status
4.2.11.4 PhysCon Failed to Implement

CONDITIONS
The user has previously launched the Physical Connection Implementation

operation.
CAUSES
1)
Negative answer from EML: connectivity object implementation failed.
2)
Communication error
1)
2)
Verify that EML is running and launch again the Physical Connection
Implementation operation.
ACTIONS
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
1)
2)
Verify that EML is running and launch again the Remove operation.
1AA 00014 0004 (9007) A4 ALICE 04.10
ACTIONS
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
89 / 182
The SDH ports are displayed from Browser by utilizing command NE: Display Related Items: SDH Ports.
The attribute involved are
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
CAUSES
Communication problems at OS level.
ACTIONS
Verify the communication between OS. Refer to EML diagnostic.
1AA 00014 0004 (9007) A4 ALICE 04.10
4.2.15 SDH port Upload status ( for TSDIM ONLY)=Not found

CONDITIONS
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
90 / 182

4.2.12 SDH Port Diagnostic
1AA 00014 0004 (9007) A4 ALICE 04.10

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

CONDITIONS
CAUSES
Communication problems at OS level.
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
91 / 182
4.2.18 Subnetwork diagnostic
failed to Implement
failed to Remove
4.2.18.1 Subnetwork: Failed to Implement

CONDITIONS
The user entered a Subnetwork Implementation command.
CAUSES
ACTIONS
After having entered the command perform an inspection at EML and NE layer
level.
1AA 00014 0004 (9007) A4 ALICE 04.10
4.2.18.2 Subnetwork: Failed to Remove

CONDITIONS
The user entered a Subnetwork Delete from MIB command.
CAUSES
ACTIONS
After having entered the command perform an inspection at EML and NE layer
level.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
92 / 182

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

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:
Failed to Configure
Failed to Implement
Failed to Remove
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).
1)
2)
3)

ACTIONS
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.
1)
2)
Verify that EML is running and launch again the Implementation operation.
1AA 00014 0004 (9007) A4 ALICE 04.10
ACTIONS
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
93 / 182
4.2.19.3 Ring Failed to Remove

The user has previously launched a Delete command from MIB.
CAUSES
1)
2)
1)
Inspect the SH side in order to detect a possible SHRM disalignment.
2)
1AA 00014 0004 (9007) A4 ALICE 04.10
ACTIONS
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
94 / 182

CONDITIONS

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:
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)
2)
1)
2)
ACTIONS
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)
1)
2)
1AA 00014 0004 (9007) A4 ALICE 04.10
ACTIONS
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
95 / 182
4.2.20.3 Node Failed to Activate MS spring

The user has launched a Ring Implementation command.
CAUSES
1)
Negative answer from EML: connectivity object implementation failed.
2)
1)
2)
ACTIONS
4.2.20.4 Node Reachable/Not reachable

CONDITIONS
blue NODE in the map= not reachable
CAUSES
1)
NE address erroneously registered
2)
3)
TCPIP problems
1)
Verify the NE addresses
2)
Restart EML
3)
Verify the workstation physical connections
1AA 00014 0004 (9007) A4 ALICE 04.10
ACTIONS
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
96 / 182

CONDITIONS
4.2.21 Payload Configuration Diagnostic
1AA 00014 0004 (9007) A4 ALICE 04.10

4.2.21.1 Payload working status

The user issued a payload modify command. The payload modify command can be executed on:
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
ACTIONS
Inspect the browser Show additional information to display the cause of the
problem and execute one of the following actions:
ED
01
1)
Execute again the payload modify command.
2)
In case of data misalignment perform the consistency download on the

affected objects.
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
97 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
98 / 182

5 PATH/TRAIL ALLOCATION FAILURES

5.1 Introduction
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
ERRORS
OBSTACLES AND
UNSATISFIED CONSTRAINTS
UNSATISFIED
1AA 00014 0004 (9007) A4 ALICE 04.10
OBSTACLES
CONSTRAINTS
OBSTACLES
&
UNSATISFIED
CONSTRAINTS
Figure 37. Allocation failure management
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
99 / 182
5.2.1 Show Failure information

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
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 38. Path List
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
100 / 182

5.2 Allocation failure diagnostic
5.2.2 Obstacles and Unsatisfied Constraints

In case of Obstacles and Unsatisfied Constraints, the complete netscape view is provided.
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 Figure 39. herebelow.
PROBLEM
WINDOW TITLE
SUMMARY
FAILED OBJECT
FRAME
FRAME
1AA 00014 0004 (9007) A4 ALICE 04.10
PROBLEM DETAIL FRAME
Figure 39. Netscape Path/Trail allocation failure.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
101 / 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.

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)
1AA 00014 0004 (9007) A4 ALICE 04.10
PROBLEM TYPE, reference to the html Problem Detail frame. The following cases
are possible:
ED
01
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

constraints cannot be satisfied
OBSTACLE AND CONSTRAINTS PROBLEMS. Both obstacle and constraints

problems are present.
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
102 / 182

Two columns are displayable: MAIN (problems on the main route) and SPARE (problems
on the spare route, only for protected paths/trail)
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
1AA 00014 0004 (9007) A4 ALICE 04.10
ROUTE: End1 (node+port) and End2 (node+port)

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
182
103 / 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.
Figure 43. Route display components.
1AA 00014 0004 (9007) A4 ALICE 04.10
END 1 name and END 2 name. See Figure 44. on page 104.
Figure 44. END 1 / END 2 termination point names.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
104 / 182

Problem Type ( yellow string which is the html reference to the Path/Trail allocation
failure description window of Figure 46. on page 106.
Figure 45. Problem Detail frame.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
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.
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
105 / 182

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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
106 / 182

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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Infinite Cost
Explanation: The routing algorithm has found a route which uses a routing link with infinite cost
Hints: Change the cost of the related physical connection
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
107 / 182
No Free Link Connections
Hints: Deallocate some paths/trails which use the same routing link or change the payload
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 51. and Figure 52. herebelow display an example of protected path allocation failure.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
108 / 182

Explanation: The system tried to use a routing link without free link connections
1AA 00014 0004 (9007) A4 ALICE 04.10

MAIN ROUTE
SPARE ROUTE
Figure 51. Example of display of a protected path
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
109 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10

SPARE
Figure 52. Example of display of a protected path
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
110 / 182
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.

2)
Figure 53. Constraint List
1AA 00014 0004 (9007) A4 ALICE 04.10
An example of Constraint List is shown in Figure 54. on page 112.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
111 / 182

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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
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
182
112 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 55. Examples of interpretation of the Constraint list rows.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
113 / 182

OTHER ERRORS are not described in detail. They indicate errors for which no other information is
provided.
An example of other error display is shown in Figure 56. herebelow.
OTHER ERROR
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 56. Example of OTHER ERRROR display
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
114 / 182

5.2.3 Other errors

6 DIAGNOSTIC OF THE NPE RING

6.1 User Presentation
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
The window can display up to 16 node icons (see Figure 57. )
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
115 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 57. 4 fibre MS SP reporting screen
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
116 / 182

6.1.1 MidProtocol Role ( NODE CONDITION ) attribute

Two node icons are associated to the values of the ConfigurationState attribute od the
MSSPRingProtectionBlock MOC:
ConfigurationState = virtual, icon
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
117 / 182

virtual
topology implementation
topology deimplementation
MSSPRING activation
enabled
active
MSSPRING deactivation
Figure 59. ConfigurationState diagram
1AA 00014 0004 (9007) A4 ALICE 04.10
The following table describes the rationale that drives the displayof the various icons according to the
ConfigurationState state diagram (see Figure 59. ).
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
118 / 182

Table 3. ConfigurationState, node conditions, and RM display.
ConfigurationState
node condition
displayed icons
operation
virtual
MSSPRING not configured
virtual node icon
topology implementation failure (TFEP

stalled)
active
MSSPRING not configured
virtual node icon
topology implementation failure (TSDIM establish failed)
active
node icon +MidProtocolRole = unknown

icon on top
node unreachable
enabled
enabled
node icon +MidProtocolRole = standby

icon on top
MSSPRING deactivation successful
enabled
active
node icon + other icons

on top to show protocol
role and stored commands +
not aligned indication
MSSPRING deactivation failure
active
active
node icon +
other icons on top to
show protocol role and
stored commands
topology implementation successful or MS

SPRING activation successful
active
enabled
node icon +
MidProtocolRole =
standby icon on top +
not aligned indication
topology implementation failure (TSDIM

populate failed) or
MSSPRING activation
failure
1AA 00014 0004 (9007) A4 ALICE 04.10
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;
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
182
119 / 182
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. ).
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 60. ConfigurationState = enabled/active icon
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
120 / 182

6.1.2 MidProtocol Role ( NODE CONDITION) attribute

idle
unknown
intemediate
standby
no icon
Figure 61. MidProtocolRole ( NODE CONDITION ) icons

6.1.2.1 West and EastProtocolRole attributes
null
tailHeadRing
(interruption Ring)
tailHeadSpan
(interruption Span)
protUnav
(EXT)thRingProtUnav
no icon
Figure 62. WestProtocolRole possible icons.
tailHeadRing
null
tailHeadSpan
protUnav
thRingProtUnav
no icon
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 63. EastProtocolRole possible icons.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
121 / 182
The allowed combinations of values for the WestProtocolRole, MidProtocolRole, and EastProtocolRole
are the following:
the node received no external command and detected no failure/degrade:

null
1AA 00014 0004 (9007) A4 ALICE 04.10
null
tailHead Ring
null
tailHeadSpan
intermediate
null
the node either received a commandspan or detected a failure/degradespan on both sides and
served both:
tailHeadSpan
ED
null
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
null
the node is serving an external commandspan or failure/degradespan that involves its East side:
null
null
the node is serving an external commandring or failure/degradering that involves its East side:
null
null
the node is serving an external commandspan or failure/degradespan that involves its West side:
tailHead Span
null
the node is serving an external commandring or failure/degradering that involves its West side:
tailHeadRing
tailHead Ring
null
01
null
tailHeadSpan
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
122 / 182

6.1.3 Allowed combinations of East, West, and MidProtocolRole
the protection MS on the West side of the node is unavailable or locked out:

protUnav
1AA 00014 0004 (9007) A4 ALICE 04.10
null
null
null
protUnav
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
ED
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
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
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
the protection MS on both sides of the node is unavailable or locked out:

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

null
null
01
null
tailHead Span
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
123 / 182
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
incoming K bytes on a given side, the relevant icon is displayed.
null
defaultKBytes
no icon
Figure 64. East failure Of Protocol
null
defaultKBytes
no icon
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 65. West failure Of Protocol
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
124 / 182

6.1.3.1 Protocol Failure attribute

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
addressed. Each value other than null indicated either a command (forced, manual) given by the manager
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
wtr ring
null
no icon
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 67. West ring active condition
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
125 / 182
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,
manual, lockoutProtection) given by the manager 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 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
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 69. West span active condition
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
126 / 182

6.1.5 Span Active Condition attributes

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
can be removed by the manager by the appropriate release command.
manual switch ring
forced switch ring
null
no icon
Figure 70. East ring pending command
manual switch ring
forced switch ring
null
no icon
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 71. West ring pending command
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
127 / 182
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
value other than null indicates a command given by the manager and that can be removed by the manager
by the appropriate release command.
manual switch span
forced switch span
null
no icon
Figure 72. East span pending command
manual switch span
forced switch span
null
no icon
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 73. West span pending command
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
128 / 182

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

null
Lockout working ring
no icon
Figure 74. East Lockout Working Ring
null
Lockout working ring
no icon
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 75. West Lockout Working ring
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
129 / 182
6.1.9 Lockout Working Span attributes ( not implemented in this version release )
Lockout working span

null
no icon
Figure 76. East Lockout Working Span
null
Lockout working span
no icon
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 77. West Lockout Working Span
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
130 / 182
6.1.10 Inhibition chain

The possible requests are listed herebelow in decreasing priority.
LPS (Lockout Protection Span), SFP (Signal Fail Protection), LOWR (Lockout Working Ring),
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
1AA 00014 0004 (9007) A4 ALICE 04.10
EXCEPTIONS
Two MSS (Manual Switch Span): no action
SFR and FSR : no action
Two SDR : no action
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
131 / 182
6.1.11 Scenarios
6.1.11.1 Bidirectional Signal Fail / Ring Scenario

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)
b)
Click on the alarm icon displayed on the main span. The alarm detail window is presented, giving
the information needed to repair the span.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
The scenario after the repair of the affected spans is described at paragraph 6.1.11.2.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
132 / 182

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

Alarm icon
Ring Interruption (tailHeadRing)
Node Condition=intermediate
(not directly affected by the fault)
Node Condition=Idle
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 78. Bidirectional Signal Fail / Ring
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
133 / 182
6.1.11.2 Bidirectional Signal Fail / Ring cleared .WTR
The bidirectional Signal Fail / Ring on AB span is cleared as a consequence of a repair action. The last
node detecting the signal failure clear starts the WTR ( wait to restore time )
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 79. Bidirectional Signal Fail / Ring cleared .WTR
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
134 / 182

DESCRIPTION
6.1.11.3 Double Bidirectional Signal Fail / Ring

DESCRIPTION
Bidirectional Signal Fail / Ring on AB span.
Bidirectional Signal Fail / Ring on DE span.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
It is suggested the repair of the main span first.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
135 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
B

Alarm icon
C
D
Ring Interruption (tailHeadRing)
Node Condition=Idle
Figure 80. Double Bidirectional Signal Fail / Ring
SC.6:MAINTENANCE
3AL 61259 AA AA
182
136 / 182
6.1.11.4 Forced Switch Ring

DESCRIPTION
A Forced Switch / Ring command is entered to A/East for AB span.
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).
REPAIR ACTION
This command is used in the Add/Remove Node procedures.
B
Forced Switch Ring East
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 81. Forced Switch / Ring
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
137 / 182
6.1.11.5 Double Forced Switch / Ring to different nodes, node isolated
Forced Switch / Ring command given to A/East for AB span and Forced Switch / Ring command given
to C/West for BC span.
This scenario can be established to put node B in local maintenance condition.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Forced Switch Ring East
C
Forced Switch Ring West
Figure 82. Double Forced Switch / Ring to different nodes, node isolated
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
138 / 182

DESCRIPTION
6.1.11.6 Double signal Fail / ring, node isolated

DESCRIPTION
Bidirectional Signal Fail / Ring on BC span.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 83. Double signal Fail / ring, node isolated

It is suggested the repair of the main span first.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
139 / 182
6.1.11.7 Forced Switch / Span
A Forced Switch / Span command is entered to B/West for AB span.

This command is used when the AB main span requires a local maintenance.
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.
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 84. Forced Switch / Span
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
140 / 182

DESCRIPTION
6.1.11.8 Double Manual Switch / Ring pending

DESCRIPTION
Manual Switch / Ring command given to D/West for DE span
Manual Switch / Ring command given to B/West for BA span.
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 85. Double Manual Switch / Ring pending
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
141 / 182

Forced Switch / Ring command given to D/West for DE span.
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 86. Signal Fail / Ring pending, Forced Switch / Ring pending
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
142 / 182

DESCRIPTION

DESCRIPTION
Bidirectional Signal Fail on Protection on BA span.
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)
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 87. Signal Fail Span, Signal Fail / Ring pending
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
143 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
144 / 182

7 LOGGER
The event logger displays the current events and the list of the events which have been stored in the log
file.
The Event Log dialog box is shown in Figure 88.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 88. Event Log filter
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
145 / 182
This box allows the user to select the following parameters:

Class Type. The operator can choose to display events relative to:
all classes (wildcard)

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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
146 / 182
EVENT LOG

The Event Log dialog box is shown in Figure 89.

The pulldown menu line contains items File and Actions.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 89. Event Log
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
147 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
148 / 182

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.
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 ).
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
149 / 182
The Consistency Download activity verifies the misalignments between EML and NML and performs
corrective actions in that the NML database is the reference.
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 ).
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
150 / 182

8.1.2 Consistency download ( SENIM )

8.2 NMLEML Consistency Checks ( TSDIM )

With TSDIM, RM interacts directly with the NEs and directly manages alignment, consistency, isolation
and download enable / disable.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
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
182
151 / 182
8.2.3 Consistency download management (
TSDIM )
The operation is available for TSDIM NEs while1354RM is in normal online runlevel.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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).
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
152 / 182

The objective of this feature is to align the NE with RM Mib being RM the reference.
8.2.4 Consistency Status (
TSDIM )

The following table gives an overall mapping of the values of consistency status and consistency activity.
Table 4. Values of Consistency Status attribute.
Consistency
Status
Semantic
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 Isolated.
If the Node is moved to the appropriate state (i.e. download enabled and NE reachable), 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
1AA 00014 0004 (9007) A4 ALICE 04.10
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 performed 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 executed.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
153 / 182
8.2.5 Consistency audit management
The operation is available for TSDIM NEs while the RM system is in normal online runlevel.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
The transport entities affected by a consistency audit are locked with a specific attribute of the working
state (auditing).
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
154 / 182

The objective of this feature is to verify the alignment between NE and RM Mib.
8.2.5.1 Consistency audit on objects

Objects impacted by the consistency audit are single TPs, subnetwork connections, NE / Node, PMTP.
In the following table the releationship between the initial value of the consistency Status and the result
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
Consistency
Status
Object Found and consistent
Object not found or not consistent
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 :
1AA 00014 0004 (9007) A4 ALICE 04.10
Initial
Consistency
Status
Object Found and consistent
Object not found or not consistent
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
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
155 / 182
8.2.5.2 Consistency download on objects
During the consistency download on the Node, all the incoming requests are rejected.
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).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
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
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
156 / 182

This operation can be executed on single TPs, subnetwork connections, NE / Node.
8.2.6 Reporting during consistency ( TSDIM )

This feature allows to present the list of RM objects not consistent with the NE ones.
An object can be not consistent due to the misalignment of one or more attributes. For each attribute the
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)
1AA 00014 0004 (9007) A4 ALICE 04.10
The allAttributes value is used when it is not possible to determinate the attribute that caused the
inconsistency.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
157 / 182
8.2.7 Consistency Status Diagnostic ( TSDIM )
1AA 00014 0004 (9007) A4 ALICE 04.10
Not aligned. This is due to:
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
158 / 182

The Consistency Statuses relevant to Diagnostic are:
1AA 00014 0004 (9007) A4 ALICE 04.10

9 1354RM PROCESS CONTROL

9.1 Introduction to process control
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
159 / 182

Figure 90. Process control window

The pulldown menu bar contains three menus:
File
Actions
View
1AA 00014 0004 (9007) A4 ALICE 04.10
The menu File contains the only option Exit, which allows to close the window.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
160 / 182

The menu Actions contains the following selectable options (See Figure 91. ):
Startup
Shutdown
Control
Set Run Level
on Agent
Synchronize
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 91. Process Control window:Actions:Startup pulldown menu
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
161 / 182
Selected agent
System
Database

The options Startup and Shutdown allow to select one of the following items:
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
1AA 00014 0004 (9007) A4 ALICE 04.10
The options Set Run Level allows to select the following items:
0:Full functionality
1:Network Configuration
2:Network Maintenance
3:Network Consistency
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
162 / 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.
NOTE
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
1AA 00014 0004 (9007) A4 ALICE 04.10
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
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
163 / 182
The Actions:Startup pulldown menu allows to select one of the following submenus
(See Figure 91. on page 161):
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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 .
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
164 / 182

9.1.1 Actions:Startup pulldown menu
9.1.1.3 Actions:Startup:Database
1AA 00014 0004 (9007) A4 ALICE 04.10

PURPOSE
The purpose of this procedure is to cause a startup of the Database.
CONDITIONS
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 .
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
165 / 182
9.1.2 Actions:Shutdown pulldown menu
Selected agent
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
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
166 / 182

The Actions:Shutdown pulldown menu allows to select one of the following submenus:
9.1.2.3 Actions:Shutdown:Database
1AA 00014 0004 (9007) A4 ALICE 04.10

PURPOSE
The purpose of this procedure is to cause a shutdown of the Database.
CONDITIONS
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
167 / 182
The Actions:Startup pulldown menu allows to select one of the following submenus:
Start process
Stop process
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
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
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
168 / 182

9.1.3 Actions:Control pulldown menu
9.1.3.3 Actions:Set Run Level

PURPOSE
The purpose of this procedure is to set the run level of the selected agent. This means that you are
changing the group of actually running processes.
CONDITIONS
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
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
169 / 182
9.1.3.4 Actions: Agents: Change Trace level
The purpose of this procedure is to change the trace level of the selected agent.
CONDITIONS
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
170 / 182

PURPOSE
9.1.3.5 Actions:Synchronize
1AA 00014 0004 (9007) A4 ALICE 04.10

PURPOSE
The purpose of this procedure is to synchronize the monitor window to the actual state of the vprocesses.
CONDITIONS
PROCEDURE
a)
ED
In the menu bar select Actions:Synchronize. The PMC window is aligned to the actual status of the
processes.
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
171 / 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):
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
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. )
1AA 00014 0004 (9007) A4 ALICE 04.10
In this window you can find messages about operations performed on agents or crashes of child
agents automatically recovered by the parent.
Figure 93. Process Control window:View : History: Local
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
172 / 182
9.1.4.2 View:History:Control

PURPOSE
The purpose of this procedure is to display the historical file of system messages relevant to the Control
function.
CONDITIONS
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 94. Process Control window:View : History: Control
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
173 / 182
9.1.4.3 Views:Agent processes
The purpose of this procedure is to show the monitored processes.

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:
1AA 00014 0004 (9007) A4 ALICE 04.10
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
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
174 / 182

PURPOSE
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 95. Process Control window:View : Agent processes
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
175 / 182

9.1.4.4 Views:Database process
The purpose of this procedure is to view the Database process .

CONDITIONS
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
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 96. Database process view
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
176 / 182

PURPOSE
9.1.4.5 Views:Configuration

PURPOSE
The purpose of this procedure is to view the PMC configuration file.
CONDITIONS
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 97. View:Configuration file
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
177 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
agent_name : name of controlled agent
agent_type : it specifies the agent handling type. It can be set either as general (for process
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.
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
178 / 182

For each controlled agent the following information is provided:
9.1.4.6 View: Agent trace

PURPOSE
The purpose is to view the selected agent trace.
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. ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 98. Agent trace selection box
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
179 / 182
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 99. shows an example of Agent trace.
Figure 99. Example of agent trace
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
180 / 182
INDEX

AIS, 10
Alarm processing, 73
Alarm Propagation, 23
Alarms, 9
AlrfloodingHP, 11
AlrfloodingLP, 11
ASAP, 17
LOTTP Alarm Propagation, 26

Lockout , 130
LOF, 10
Logger, 145
LOP, 10
LOS, 10
M
C
ConfMismatch, 11
CONSISTENCY, 149
Consistency audit, 149
Consistency download, 150
Control, 168
CTP Alarm Propagation, 27
MAINTENANCE, 61
Manual Switch / Ring pending, 141
MediaEqFail, 11
MSSpring Alarm Propagation, 24
MSTP Alarm Propagation, 24
MStrail, 66
mSConfMismatch, 11
DegSig, 11
NE, 85
NenotReachable, 11
neNR, 10
Node, 95
NODE CONDITION, 120
NPE Ring, 115
E
EML, 83
ExBER, 10
ExBer, 11
P
F
fault localization, 62
FERF, 10
Forced Switch / Span, 140
Forced Switch Ring, 137
H
HOtrail, 68
HOTTP Alarm Propagation, 25
Path, 71, 75
PDHFailure, 11
Physical Connection, 88
Physical connection, 64
PLM, 10
Port Alarm Propagation, 23
Probable Causes, 10
Process, 159
PTM, 10
Q
QualityTC15m, 11
QualityTC24h, 11
1AA 00014 0004 (9007) A4 ALICE 04.10
Inhibition chain, 131
R
K
RAI, 10
reISO, 10, 11
K1K2PM, 10
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
181 / 182
Startup, 164
Subnetwork, 92
remSDHFailure, 11
RS Failure, 11
RU, 10
rxF, 10
T
TrF, 10
txF, 10
S
Scenarios, 132
SDHFailure, 11
Shutdown, 166
signal Fail, 139
SLM, 10
SSF, 10
SSF_Eg, 10
SSF_In, 10
U
UnderProtDeg, 11
UNEQ, 10
UPA, 10
1AA 00014 0004 (9007) A4 ALICE 04.10
END OF DOCUMENT
ED
01
SC.6:MAINTENANCE
957.130.872 H
3AL 61259 AA AA
182
182 / 182

TABLE OF CONTENTS
1AA 00014 0004 (9007) A4 ALICE 04.10
01
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
9
9
9
2 ACCESS TO THE MAIN FUNCTIONALITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 The Tool Subpanel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
13
14
3 SDH NETVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 Icon bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2 Popup menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
15
16
17
4 SDH NETVIEW : MAP SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Map: Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Map: Maps: Open/List ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Map: Maps: New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3 Map: Maps: Save Map As... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4 Map: Maps: Describe/Modify Map... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.5 Map: Maps: Delete... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 Map: Submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1 Map: Submap: Open/List... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2 Map: Submap : New... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3 Map: Submap: Describe/Modify... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4 Map: Submap: Set This Submap As Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.5 Map: Submap: Delete... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.6 Map: Submap: Delete This Submap... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 Map: Refresh Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5 Map:Map Redo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.1 Map: Map Redo: Store Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.2 Map: Map Redo: Store Map (no connections) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.3 Map: Map Redo: Store Submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
29
30
31
32
35
35
37
38
38
38
38
39
39
39
40
41
42
43
43
000721
validated
01A 000515
proposal
ED
DATE
CHANGE NOTE
M.RAGNI ITAVE
E.CORRADINI
M.RAGNI ITAVE
E.CORRADINI
V.PORRO ITAVE
F.FERRARID.ERBA
V.PORRO ITAVE
F.FERRARID.ERBA
APPRAISAL AUTHORITY
ORIGINATOR
1354RM REL.5.2B
OPERATORS HANDBOOK
ED
01
SC.7:GRAPHICAL INTERFACE
957.130.872 H
3AL 61259 AA AA
230
1 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
43
44
47
48
50
51
52
53
54
56
56
5 SDH NETVIEW: EDIT SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Edit: Cut: From This Submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Edit: Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 Edit: Delete: From the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Edit : Hide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.1 Edit: Hide : From This Submap... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.2 Edit: Hide : From All Submaps... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6 Edit:Show Hidden Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.1 Edit: Show Hidden Objects : For This Submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.2 Edit: Show Hidden Objects : For All Submaps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
57
57
58
59
60
61
61
61
62
62
62
6 SDH NETVIEW: LOCATE SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Locate: Selected Object List... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Locate:objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1 Locate: Objects : By Selection Name... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.2 Locate: Objects : By Attribute... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.3 Locate: Objects : By Comment... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.4 Locate: Objects : By Symbol Status... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.5 Locate: Objects : By Symbol Type... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.6 Locate: Objects : By Symbol Label... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
63
63
64
64
64
65
65
65
65
7 SDH NETVIEW: VIEW SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.1 View:Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.2 View: Overlay Submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.3 View: Redo Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.4 View: EML... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.5 View: Object Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.6 View: Clear Alarmed Object (acknowledge) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
67
67
68
69
69
69
70
72
8 SDH NETVIEW: CONSTRUCTION SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Construction:Upload EML(s) info... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.1 Construction:Upload EML(s) info:Available EMLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.2 Construction:Upload EML(s) info:Available NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.3 Construction:Upload EML(s) info:Available NE ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3 Construction:Create Virtual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.1 Creating a Virtual EML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.2 Construction:Create Virtual: Port... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.3 Construction:Create Virtual: NSDHPort... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.4 Construction:Delete Virtual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
73
74
74
75
76
77
78
80
81
83
ED
01
957.130.872 H
3AL 61259 AA AA
230
2 / 230

4.5.4 Map: Map Redo: Store Submap (no connections) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.5.5 Map: Map Redo: Execute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6 Map:Distribute Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1 Map :Distribute Maps: Store Map Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2 Map: Distribute Maps: Get/List Map Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3 Map:Distribute Maps:Remove Map image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.4 Map :Distribute Maps: Lock map image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.5 Map :Distribute Maps: Unlock map image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.6 Map :Distribute Maps: Modify Username List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7 Map: Close Submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.8 Map: Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

8.4 Construction:Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.1 Construction:Create:Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.2 Construction:Create:Subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.3 Construction:Create:Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5 Construction:Create Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6 Construction: Link to a topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
84
85
86
87
88
92
9 SDH NETVIEW: SUPERVISION SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 Supervision: Implement Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.1 Supervision: Deimplement Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.2 Supervision: Placement: Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.3 Supervision: Placement: Retrieve: Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.4 Supervision: Placement: Retrieve Not Placed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.5 Supervision:Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.6 Supervision:Configuration: Synch.equipment Eml<>NML . . . . . . . . . . . . . . . . . . . . . . . .
93
93
94
95
95
95
95
96
100
10 SDH NETVIEW: BROWSE SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 Browse: Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 Browse: NAPs: Idle 2 Mb/ Idle34Mb/ Idle 45Mb/ Idle140Mb/ filtered . . . . . . . . . . . . . . . .
10.4 HO CTPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5 Browse: Paths... : in Topology... : 2Mb/ 34Mb/ 45Mb /140 Mb / filtered . . . . . . . . . . . . .
10.6 Browse: Paths... : all in Phys. Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.7 Browse: Paths... : active in Phys. Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.8 Browse: Paths... : starting (ending) from nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.9 Browse: Trails...: at this sublevel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10 Browse: Trails...: at all sublevels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.11 Browse: Trails...: user defined HO trails at all sublevels . . . . . . . . . . . . . . . . . . . . . . .
10.12 Browse: Trails starting (ending) from nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13 Browse: Physical Connection.. : LCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.14 Browse: Physical Connection: Physical Connection structure . . . . . . . . . . . . . . . . . .
10.15 Browse: SDH Port payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.16 Browse: Protection Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.17 Browse: Performance Monitoring: Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.18 Browse: Performance Monitoring: Monitored NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.19 Browse: Performance Monitoring: TCA Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20 Browse: Performance Monitoring: Counter Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.21 Browse: Performance Monitoring: Threshold Reports . . . . . . . . . . . . . . . . . . . . . . . . . .
10.22 Browse: Performance Monitoring: Archive Session . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.23 Browse: Alarmed objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
103
103
104
104
106
106
106
106
106
107
107
107
107
107
108
108
108
108
108
109
109
109
109
109
11 SDH NETVIEW: TOOLS SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 Tools: Path: Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 Tools: Path: Contraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.4 Tools: Path: Add Leg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5 Tools: Modify Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6 Tools: Setup Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7 Tools: Upload NAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.8 Tools: Network Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
111
111
111
111
111
111
111
112
112
12 SDH NETVIEW: HELP SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
113
13 BROWSER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
115
ED
01
957.130.872 H
3AL 61259 AA AA
230
3 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
115
117
119
121
121
122
123
125
126
127
128
129
129
129
129
129
129
130
130
130
131
131
133
133
135
136
137
137
137
137
137
14 BROWSER: DRAWING WINDOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1.1 Icon bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1.2 Work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.2 Payload configuration of a Physical Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3 Client link connection (view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.4 Path in trail (view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.5 Port structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.6 Trail Routing display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.7 2F MSSPRING protection block view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.8 4F NPE protection block view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.9 Path/Trail Routing view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.9.1 Main Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.10 Link Connection routing View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.11 Naps View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.12 Node view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.13 Performance Monitoring Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.13.1 PM Transport view display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.13.2 PM TP view display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
139
139
140
140
141
143
144
145
146
147
150
151
152
157
158
159
161
161
162
15 BROWSER MULTICOLUMN WINDOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
165
165
ED
01
957.130.872 H
3AL 61259 AA AA
230
4 / 230

13.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2 Browser main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2.1 Icon bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2.2 Counters area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2.3 Work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3 Object filtering and scoping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.1 DEFINE QUERY FOR (the selection/filter window) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4 Show/Set Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5 Items selection in the Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6 Generic Browser pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.1 Actions: Display: Main Related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.2 Actions: Display: All Related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.3 Actions: Display: Align item(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.4 Actions: Display: Parent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.5 Actions: Select: Related Items.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.6 Actions: Select: All related Items.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.7 Actions: Select: Unselect All.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.8 Actions: Close: Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.9 Actions: Close: Item by Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.10 Actions: Close: All related items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.11 Actions: Details: Show/set attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.12 Actions: Details: Displayed info... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.13 View:Displayed info.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.14 View:Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.15 Options: Filtered presentation / Not filtered presentation . . . . . . . . . . . . . . . . . . . . . . .
13.6.16 Options:Graph refresh rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.17 Options:Close window going to parent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.18 Options: Enable AS link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.19 Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.20 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6.21 ExtTools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

15.1.1 Pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.1.2 Icon bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.4 Title area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.5 Counters area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.6 Work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.7 Counters and graphs on Browser MultiColumn Lists . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.8 Multicolumn list window configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.2 Available Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
166
167
168
168
168
169
172
174
16 BROWSER: LOCATE ITEMS IN SDH NETVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16.1 Path route on SDH netview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2 Locate topological objects on Netview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
177
177
180
17 PAYLOAD CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1 Introduction to Payload Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1.1 Configuring the payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1.2 Payload Configuration monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1.3 Payload Configuration supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2 AU4 Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2.1 AU4 Concatenation SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
183
183
183
186
187
188
188
18 TRAIL SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
191
19 PATH CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.1 Path Create by using the Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.2 Path Create by using NETVIEW Browse: Nodes or relative icon . . . . . . . . . . . . . . . . . .
19.3 Path Create by using NETVIEW Browse: Nap(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
197
200
201
203
20 PATH/TRAIL CONSTRAINTS . . . . . . . . . . . . . . . . . .

Lingua

1354rm52b Manual Del Operador Vol 2

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

1354rm52b Manual Del Operador Vol 2

Caricato da

Copyright:

Formati disponibili

QUESTA PAGINA NON VA INSERITA NEL MANUALE

All rights reserved. Passing on and copying of this

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

H Ed.01 3AL 61259 AAAA Ed.01

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

No PAGINE TOTALI PER ARCHIVIAZIONE: 4 + 510 = 514

STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING

COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

1AA 00014 0004 (9007) A4 ALICE 04.10

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

INSERIRE SEPARATORE 6 - INSERT REGISTER 6

INSERIRE SEPARATORE 7 - INSERT REGISTER 7

SC.7: GRAPHICAL INTERFACE

INSERIRE SEPARATORE 8 - INSERT REGISTER 8

TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES:

TOTALE FOGLI A4 TOTAL A4 SHEETS:

WARNING FOR A-UNITS OTHER THAN A-ITALY

Labels are done according to A-Italy binder format.

3AL 61259 AAAA TQZZA

QUESTA PAGINA NON VA INSERITA NEL MANUALE

All rights reserved. Passing on and copying of this

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

ALCATEL OPTICS GROUP TND

ORIGINALE SU FILE: ALICE 6.10

1AA 00014 0004 (9007) A4 ALICE 04.10

Regional Network Manager for SDH and Optical Networks

3AL 61259 AAAA TQZZA

All rights reserved. Passing on and copying of this

3AL 61259 AAAA Ed.01

3AL 61259 AAAA Ed.01

3AL 61259 AAAA Ed.01

3AL 61259 AAAA Ed.01

1AA 00014 0004 (9007) A4 ALICE 04.10

Regional Network Manager for SDH and Optical Networks

3AL 61259 AAAA Ed.01

3AL 61259 AAAA TQZZA

1AA 00014 0004 (9007) A4 ALICE 04.10

FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT

3AL 61259 AAAA TQZZA

3AL 61259 AAAA Ed.01

3AL 61259 AAAA Ed.01

All rights reserved. Passing on and copying of this

1354RM REL.5.2B OPERATORS HANDBOOK

1AA 00014 0004 (9007) A4 ALICE 04.10

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

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

1AA 00014 0004 (9007) A4 ALICE 04.10

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

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

All rights reserved. Passing on and copying of this

3.2.2 Counter customisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

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

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

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

LIST OF FIGURES AND TABLES

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

Figure 51. Example of display of a protected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this