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
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 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
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20.1 Use/Not use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20.2 Overlapped/Disjointed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
205
207
210
21 ADD LEGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211
22 CONNECTIVITY INVENTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2 Data Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
213
213
214
23 EVENT LOGGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
217
217
24 RM JAVA BROWSER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.1.1 Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.1.2 Available Choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.1.3 Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
221
221
221
223
224
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
230
ED
01
957.130.872 H
3AL 61259 AA AA
230
5 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
FIGURES
Figure 1. HPCDE Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. 1354RM Tool subpanel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. SDH Netview window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Network popup menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Subnetwork popup menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. ET popup menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. Physical connection main items popup menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Node pop up menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. Map pull down menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Available Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. Open View Windows Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. File:New Map dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. Map: Submap pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. Map pull down menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. Map Redo Store dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. List of saved maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Execute map report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Map: Map Redo: Execute: dragging nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. Map:Distribute Maps menu items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Store Map dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. Map :Distribute map: Lock map image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Modify Username dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. Exit warning box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. Edit pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Locate pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. View pull down menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. Example of View: Object Attributes: Long Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. Example of View: Object Attributes: Short Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. Construction pull down menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. Available EMLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Available NEs in a EML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. NE port detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. Construction:Virtual Elements:Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. Create a virtual NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. Virtual tool buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. Create a virtual port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. Create many virtual ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Example of eml deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. Create Dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. Create Ring dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. Create connection dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. Connection just created. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. Ports in Node: Create Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. Create Connection dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. Physical connection: Implement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. Supervision pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 47. Implement Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 48. Audit basic flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 49. Browse pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 50. NAP List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
01
13
14
15
18
20
22
24
27
29
31
31
32
38
41
42
44
45
46
47
48
52
55
56
57
63
67
70
71
73
74
75
76
77
78
79
80
81
83
85
87
88
89
90
91
91
93
94
98
103
104
957.130.872 H
3AL 61259 AA AA
230
6 / 230

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 51. Filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 52. Browser main window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 53. Browser work area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 54. Object filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 55. Define query window for Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 56. Show/Set Attributes dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 57. Actions: Details: Displayed Info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 58. View:Report full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 59. View:Report short . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 60. Options:Deferred Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 61. Options:Default graph refresh rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 63. Physical connection structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 64. Client link connection (view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 65. Paths in trail (view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 66. Port structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 67. Trail Routing display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 68. MSSPRING Protection block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 69. Protection block popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 70. All protection block in MSSPRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 71. 4F Protection blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 72. Actual route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 73. Path Routing ( BidirectionalProtected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 74. Path Routing example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 75. Route report example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 76. Link Connection Routing view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 77. Naps view of a bidirectional path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 78. Node view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 79. PM transport view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 80. PM TP view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 81. Example of Multicolumn window (Path In Topology list) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 82. Graphical window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 83. Statistical Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 84. Ordering items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 85. Sorting items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 86. Highlighte button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 87. Selection box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 88. Locate display ( unprotected path ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 89. Selection dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 90. Locate display ( protected path ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 91. Node list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 92. Highlight button in Browser main. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 93. Highlighted node in Netview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 94. Payload Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 95. Payload Configuration dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 96. Physical connection structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 97. MS trail selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 98. Payload configuration button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 99. Payload Configuration window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 100. Payload selection subwindow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 101. Concatenated payload configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 102. Browser window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 103. Setup Trail icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 104. Setup Trail window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 105. Ring Attribute change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
01
105
117
121
122
123
125
132
133
134
135
136
142
143
144
145
146
147
148
149
150
153
154
155
156
157
158
159
161
163
168
170
170
172
173
177
178
178
179
179
180
181
181
184
185
187
188
189
189
190
190
191
191
192
193
957.130.872 H
3AL 61259 AA AA
230
7 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
194
195
199
201
203
205
208
210
211
212
214
215
217
219
221
222
225
226
227
227
228
228
229
TABLES
Table 1. Items selection in the Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
126
ED
01
957.130.872 H
3AL 61259 AA AA
230
8 / 230

Figure 106. Setup trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 107. Trail view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 108. Path Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 109. Multi path creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 110. Path Create. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 111. Path Constraints dialog box (use/not use constraint for CTPs popup) . . . . . . . . . . . . . .
Figure 112. Use Service Forward/Backward for Dual Node SNCP network . . . . . . . . . . . . . . . . . . . .
Figure 113. Path Constraints dialog box (disjoint/overlap constraint for PATHs popup) . . . . . . . . . .
Figure 114. Path list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 115. Add Leg dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 116. Actions:Get Topologies:all levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 117. Connectivity Inventory : VC4 Trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 118. Event Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 119. Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 120. 1354RM home page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 121. Shrunk menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 122. Expanded menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 123. Operator Manual selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 124. NEs ordered by type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 125. NEs ordered by site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 126. Path by rate and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 127. Path: All filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 128. Routing links completely idle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 INTRODUCTION
1.1 Introduction
This document is a reference handbook describing in detail the graphical interface provided by the
1354RM.
1.2 Target audience

The Introduction Manual is intended for all 1354RM users.
1.3 Document structure

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
ACCESS MODALITY
Access to the Main Functionalities
SDH Netview
MAP VIEW
Map: Submenu
Map: Maps menu
Map: Submap menu
Map: Refresh Map
Map: Redo Map
Map: Distribute Maps
Map: Close Submap
Map: Edit Submenu
Map: Locate Submenu
Map: View Submenu
CONSTRUCTION MENU
Introduction
Construction: Upload
Construction: Create Virtual
Construction: Create Object
Construction: Create Connection
Construction: Link (Line/Radio)
01
957.130.872 H
3AL 61259 AA AA
230
9 / 230
SUPERVISION
Supervision Menu
BROWSE
Browse Menu
TOOLS
Tools Menu
HELP
1AA 00014 0004 (9007) A4 ALICE 04.10
ED

Help on Line
BROWSER
Introduction
Browser Main Window
Object Filtering
Object Attribute
Item Selection
Generic Browser Menu
DRAWING WINDOWS
Drawing Introduction
Physical Connection Structure
Link Connection View
Path in Trail View
Port Structure
Trail Routing Display
2F MS SPRING View
4F NPE Protection View
Routing View
Link Connection View
Naps View
Node View
PM Views
01
957.130.872 H
3AL 61259 AA AA
230
10 / 230
BROWSER LIST

Browser List
LOCATE
Locate
PAYLOAD
Payload
AU4C ( CONCATENATED ) payload
TRAIL
Trail Setup
PATH CREATE
Path Create
Path Create (by Browser)
Path Create (Netview)
Path Create (Browser Naps)
CONSTRAINTS
Constraints
ADD LEGS
Add Legs
CONNECTIVITY MATRIX
Connectivity Matrix
LOGGER
Logger
JAVA BROWSER
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Java browser netscape
01
957.130.872 H
3AL 61259 AA AA
230
11 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
12 / 230

2 ACCESS TO THE MAIN FUNCTIONALITIES

A more detailed description concerning the Regional Manager management domains are given in the
Regional Manager Introduction Manual.
Access to the Regional Manager functionalities is done through the workspace front panel as described
in the following sections.
2.1 Introduction
The 1354RM graphical interface is based on:
HP Common Desktop Environment ( CDE )
HP OpenView Windows (HP-OVw)
OSF Motif applications (Browser, RM Configuration Tools, Monitor tool, System Management
Functions, etc.).
The HP_CDE Tool panel ( See Figure 1. ) has been customized to contain the 1354RM Logo ( righthand
side ).
Clicking on the small arrow above the 1354RM logo you can open the Tool Subpanel. ( See Figure 2. on
page 14)
Clock
WS
activity
Padlock
Date
Text
Editor
Workspaces
Exit
Letter
Printer
Netstation applications
Terminal
File
Manager
Regional
Manager
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 1. HPCDE Panel.
ED
01
957.130.872 H
3AL 61259 AA AA
230
13 / 230
The HP_CDE Tool Subpanel (See Figure 2. ) has been customized to contain the following icons (click
the small arrow above the 1354 RM logo to open the Tool Subpanel):
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 2. 1354RM Tool subpanel
Logo
1354 RM Network Management System. Clicking twice on it, the informa

tion on RM version is displayed.
TMN OSs
This icon, if selected, opens the supervision of the various OSs.
Administration
This icon, if selected, opens the System Management functions

(see SMF doc.)
Alarms
Starts the Alarm Surveillance user interface (see AS doc.).
Browser
Starts the Generic Browser
Network View
Starts the SDH Netview application.
ED
01
957.130.872 H
3AL 61259 AA AA
230
14 / 230

2.1.1 The Tool Subpanel

3 SDH NETVIEW
3.1 Introduction
In figure Figure 3. its displayed a typical SDH netview window; each window is relevant to a submap.
icon bar
Panner
Go to parent
window
submap
Exit Go to root
submap
Go to home
submap
work area
pulldown menu
holding area
window title
items
info area
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 3. SDH Netview window
ED
01
957.130.872 H
3AL 61259 AA AA
230
15 / 230
window title : <parents fdn> # <parents label> (in this case the parent is a meshed ring)
pulldown menu bar. Refer to chapter 3 to 11
icon bar. Refer to paragraph 3.1.1
work area. It contains items (Network, Subnetworks, ET, Nodes, Ports, Connections, ...) related
to the submap. The operations on items (Delete, Cut, Paste, Select, Move, ...) are described
in HPOpenview Windows manuals.
holding area. It contains the items that have not yet been placed in work area.
info area. It contains the map name and the rights on it.
A popup is also available on items (see para 3.1.2)

3.1.1 Icon bar
The icon bar contains the following buttons:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Exit SDH netview. It corresponds to the pulldown command Map: Exit (see para 4.8)
Go to parent submap. It display the parent submap.
Go to root submap. It display the root submap (eg. Network submap).
Panner window. It display the panner window (zoom window); selecting an area in the panner
window a zoom is performed in the submap window.
HP Openview version. It display the HP Openview Version dialog box.
Browser. It corresponds to the pulldown command Browse:Object(s).
Path constraints. It start the Path Constraints application (see chapter 20)
Filtered Paths .... It corresponds to the pulldown command Browse:Paths:In topology:Filtered.
User defined Trail .... It corresponds to the pulldown command Browse:Trails:User defined
HOTrails at all sublevels ....
Payload configuration. It start the Payload Configuration application (see chapter 17)
All Paths. It corresponds to the pulldown command Browse:Paths:all in Phys. connection .....
SH view. Available only for adms, it shows the equipment view on SH (see 1353SH documentation)
Path Creation. It corresponds to the pulldown command Path:Create ....
Add legs. It start the Add legs application (see chapter 21 )
Alarmed objects. It corresponds to the pulldown command Browse:Alarmed objects
Setup Trail. It corresponds to the pulldown command Supervision:Setup trail (see chapter 18 ).
Naps filtered. It corresponds to the pulldown command Browse:NAPS:filtered
HOCtps. It corresponds to the pulldown command Browse:HOCtps .
01
957.130.872 H
3AL 61259 AA AA
230
16 / 230

A window (submap) typically contains:

3.1.2 Popup menus

From the map the popup menu can be opened on each topological object. The actions available per each
object are described in the paragraphs which follow.
In most of the cases the browser is started giving the list or the graphical view invoked by the selected
command. The explanation of the Browser windows can be found at chapter 13 of this section.
3.1.2.1 Network popup menu
The Network popup menu, ( see Figure 4. as an example), contains the following submenus:
Browse object... It corresponds to the pulldown command Browse:Object(s)
Main items:paths in topology. This menu starts a browser instance displaying the list of the paths
belonging to the selected topological object.
Main items:Trails at all sublevels.This menu starts a browser instance displaying the list of all
trails belonging to the selected network.
Main items:User defined HOtrails at all sublevels.This menu starts a browser instance
displaying the list of all the user defined HO trails belonging to the selected network.
Main items: Alarmed objects. This menu starts a browser instance displaying the filtered list of the
following alarmed objects: nap,cap, ctp, msCtpCap, port, ne. The filter can be set by means of the
popup menus Main/All items ( Filtered Query ). The allowed filtering parameters are: alarm status,
consistency status and direction.
Main items: All Rings. This menu starts a browser instance displaying the list of all rings belonging
to the selected topological object.
Main items: All Nodes.This menu starts a browser instance displaying the list of all nodes belonging
to the selected topological object.
Main items: All physical connections in Network. This menu starts a browser instance displaying
the list of the physical connections interconnecting the subnetworks belonging to the selected
network..
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
All items: Physical Connections . Same as above Main items: All physical connections in
Network
All items: Trails at all sublevels. Same as above Main items:Trails at all sublevels.
All items: User defined HOtrails at all sublevels. Same as above Main items:User defined
HOtrails at all sublevels.
All items: HO LCs in the topology. This menu starts a browser instance displaying the list of all the
user defined HO LCs belonging to the selected network.
All items: Routing Links. This menu starts a browser instance displaying the list of all the routing
links belonging to the selected network.
All items: Not consistent tps and connections in topologies. This menu starts a browser
instance displaying the list of Not consistent tps and connections in topology.
All items: Alarmed objects. Same as above Main items: Alarmed objects.
All items: Paths in topology. Same as above Main items:paths in topology.
All items: Paths in topology (with Source/Sink) This menu starts a browser instance displaying
the list of the paths ( with source and sink ), belonging to the selected network.
All items: Subnetworks. This menu starts a browser instance displaying the list of the subnetworks
belonging to the selected network.
All items: All Rings. This menu starts a browser instance displaying the list of the rings belonging
to the selected network.
All items: All Nodes. This menu starts a browser instance displaying the list of the nodes belonging
to the selected network.
01
957.130.872 H
3AL 61259 AA AA
230
17 / 230
All items: All physical connections in Network. This menu starts a browser instance displaying
the list of the physical connections belonging to the selected network.
Main items ( Filtered query ) This menu contains the same options listed above for the Main items
menu. In addition a query filter is provided in order to obtain a filtered list.
All items ( Filtered query ). This menu contains the same options listed above for the All items
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 4. Network popup menu.
ED
01
957.130.872 H
3AL 61259 AA AA
230
18 / 230

3.1.2.2 Subnetwork popup menu
1AA 00014 0004 (9007) A4 ALICE 04.10

The Subnetwork popup menu ( see Figure 5. as an example), contains the following submenus:
Browse object... It corresponds to the pulldown command Browse:Object(s) .
Main items:Paths in topology. This menu starts a browser instance displaying the list of the paths
Main items:Trails at all sublevels.This menu starts a browser instance displaying the list o trails
interconnecting the subnetworks belonging to the selected network.
displaying the list of all the user defined HO trails belonging to the selected topological object.
Main items: All Rings This menu starts a browser instance displaying the list of the rings belonging
to the selected subnetwork.
Main items: All Nodes. This menu starts a browser instance displaying the list of the nodes
belonging to the selected subnetwork.
All items: Physical Connections . Same as above Main items: All physical connections in
Network
All items: HO LCs in the topology. This menu starts a browser instance displaying the list of all the
user defined HO LCs belonging to the selected network.
All items: Routing Links. This menu starts a browser instance displaying the list of all the routing
links belonging to the selected network.
instance displaying the list of Not consistent tps and connections in topology.
All items: Paths in topology. Same as above Main items:paths in topology.
the list of the paths ( with source and sink ), belonging to the selected subnetwork.
All items: All Rings. Same as above Main items: All Rings.
All items: All Nodes. Same as above Main items: All Nodes.
ED
01
957.130.872 H
3AL 61259 AA AA
230
19 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 5. Subnetwork popup menu.
ED
01
957.130.872 H
3AL 61259 AA AA
230
20 / 230

3.1.2.3 Elementary Topology popup menu
1AA 00014 0004 (9007) A4 ALICE 04.10

The Elementary Topology popup menu ( see Figure 6. as an example), contains the following submenus:
Browse object... It corresponds to the pulldown command Browse:Object(s).
Main items: Nodes in topology. This menu starts a browser instance displaying the list of all nodes
Main items:Trails at all sublevels.This menu starts a browser instance displaying the list of the
trails interconnecting the nodes belonging to the selected topology.
displaying the list of all the user defined HO trails belonging to the selected topological object.
Main items: Physical Connections. This menu starts a browser instance displaying the list of the
physical connections interconnecting the the nodes belonging to the selected topology.
Main items: HO LCs in the topology. This menu starts a browser instance displaying the list of all
the user defined HO LCs belonging to the selected network.
Main items: All Protection Blocks in MSSpring. This menu starts a browser instance displaying
the view of the protection blocks in MSSpring.
All items: Nodes in topology. Same as above Main items: Nodes in topology
All items: Physical Connections. Same as above Main items: Physical Connections.
All items: HO LCs in the topology. Same as above Main items: HO LCs in the topology.
All items: Routing Links. This menu starts a browser instance displaying the list of the routing links
belonging to the selected topology.
All items: All Protection Blocks in MSSPRING. Same as above Main items: All Protection
Blocks in MSSpring.
instance displaying the list of Not consistent tps and connections in topologies.
All items: Paths in topology. Same as above Main items:Paths in topology.
ED
01
957.130.872 H
3AL 61259 AA AA
230
21 / 230
the list of the paths ( with source and sink ), belonging to the selected subnetwork.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 6. ET popup menu.
ED
01
957.130.872 H
3AL 61259 AA AA
230
22 / 230

1AA 00014 0004 (9007) A4 ALICE 04.10

3.1.2.4 Physical Connection popup menu

The Physical Connection
submenus:
popup menu, ( see Figure 7. as an example), contains the following
Active Paths. This menu starts a browser instance displaying the list of the active paths in the
Physical Connection.
Main items:Physical Connection structure This menu starts a browser instance displaying the
view of the Physical Connection structure.
Main items: Paths in physical connection. This menu starts a browser instance displaying the list
of the paths in the Physical Connection.
Main items: Paths in physical connection (with Source/Sink). This menu starts a browser
instance displaying the list of the paths (with Source/Sink) in the Physical Connection.
Main items: Alarm profile. This menu starts a browser instance displaying the icon of the alarm
profile actually assigned to the selected physical connection.
All items: Connected Topologies. This menu starts a browser instance displaying the connected
topologies ( physical connections )
All items: Connected Nodes. This menu starts a browser instance displaying the connected nodes.
All items: Paths in physical connection. Same as above Main items: Paths in physical
connection.
All items: MS Trail. This menu starts a browser instance displaying the list of the MS Trails in the
All items: HO Trail. This menu starts a browser instance displaying the list of the HO Trails in the
All items: Active Paths in Physical Connection .Same as above Active Paths.
All items: Physical Connection structure. Same as above Main items:Physical Connection
structure.
All items: Paths in physical connection (with Source/Sink). Same as above Main items: Paths
in physical connection (with Source/Sink).
All items: Active Paths in physical connection (with Source/Sink). Same as above Main items:
Paths in physical connection (with Source/Sink).
All items: Alarm profile. Same as above Main items: Alarm profile.
ED
01
957.130.872 H
3AL 61259 AA AA
230
23 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 7. Physical connection main items popup menu.
ED
01
957.130.872 H
3AL 61259 AA AA
230
24 / 230
3.1.2.5 Node popup menu

The Node popup menu ( see Figure 8. as an example) contains the following submenus:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Add Legs. This menu starts the Add Leg application. See Chapter 21 of this section.
Assigned Ports. This menu starts a browser instance displaying the list of the ports of the selected
node, whose Assignment State is equal to Assigned.
Main items: Node View. This menu starts a browser instance displaying the graphical view of the
selected node.
Main items: Path starting(ending) from(in)node. This menu starts a browser instance displaying
the list of the paths terminated to the selected topological object.
Main items: Ports in node. This menu starts a browser instance displaying the list of the ports of
the selected node.
Main items: All naps. This menu starts a browser instance displaying the list of the naps of the
selected node.
Main items: MSTPs. This menu starts a browser instance displaying the list of the MSTPs of the
selected node.
All Items:Not consistent tps and connections in topologies. This menu starts a browser
instance displaying the list of Not consistent tps and connections in topologies belonging to the
selected node.
All items: Paths in topology. Same as above Main items:Paths in topology.
All items: Paths in topology (with Source/Sink). This menu starts a browser instance displaying
the list of the paths (with Source/Sink) belonging to the selected node.
All items: All Naps. Same as above Main items: All naps.
All items: End Points. It gives the list of all end points belonging to the selected node.
All items: CTPs .It gives the list of all CTPs belonging to the selected node.
All items: Connections in the topology. This menu starts a browser instance displaying the list of
the Connections in the topology.
All items: High Order CTPs. This menu starts a browser instance displaying the list of the High
Order CTPs belonging to the selected node.
All items: Low Order CTPs. This menu starts a browser instance displaying the list of the Low Order
CTPs belonging to the selected node.
All items: MSTPs. This menu starts a browser instance displaying the list of the MSTPs belonging
to the selected node.
All items: MSSPRING Protection Block. This menu starts a browser instance displaying the icon
of the protection block associated to the node.
All items: Path starting(ending) from(in)node. See above Main items:Path starting(ending)
from(in)node
All items: Ports in node. This menu starts a browser instance displaying the list of the ports
belonging to the node.
All items: Network Element. This menu starts a browser instance displaying in the browser window
the Network Element associated to the selected node.
All items: Node view. This menu starts a browser instance displaying the graphical view of the
selected node.
01
957.130.872 H
3AL 61259 AA AA
230
25 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
All items: Path starting(ending) from(in)node(with Source/Sink). This menu starts a browser
instance displaying the list of the paths (with Source/Sink) terminated to the selected node.
All items: Naps (with Path label). This menu starts a browser instance displaying the list of the naps
(with belonging to the node.
Main items: Alarm profile. This menu starts a browser instance displaying the icon of the alarm
profile actually assigned to the selected physical connection.
All items: Connected Topologies. This menu starts a browser instance displaying the connected
topologies ( physical connections )
All items: Connected Nodes. This menu starts a browser instance displaying the connected nodes.
All items: Paths in physical connection. Same as above Main items: Paths in physical
connection.
All items: MS Trail. This menu starts a browser instance displaying the list of the MS Trails in the
All items: HO Trail. This menu starts a browser instance displaying the list of the HO Trails in the
All items: Active Paths in Physical Connection .Same as above Active Paths.
All items: Physical Connection structure. Same as above Main items:Physical Connection
structure.
All items: Paths in physical connection (with Source/Sink). Same as above Main items: Paths
in physical connection (with Source/Sink).
All items: Active Paths in physical connection (with Source/Sink). Same as above Main items:
Paths in physical connection (with Source/Sink).
All items: Alarm profile. Same as above Main items: Alarm profile.
01
957.130.872 H
3AL 61259 AA AA
230
26 / 230

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 8. Node pop up menu.
ED
01
957.130.872 H
3AL 61259 AA AA
230
27 / 230

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
28 / 230

4 SDH NETVIEW : MAP SUBMENU

4.1 Introduction
The Map pulldown menu allows to select one of the following items (see Figure 9. ):
Map: Maps
Map: Submap
Map: Refresh Map
Map: Map Redo
Map: Distribute Maps
Map: Close Submap
Map: Exit
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 9. Map pull down menu

Note: A Map is a logical structure of the network, tree like, which includes: Network, Subnetwork,
ElementaryTopology, Node, EMLs, Network Element, Port.
ED
01
957.130.872 H
3AL 61259 AA AA
230
29 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
Open/List...
New...
Save Map As...
Describe/Modify...
Delete...
ED
01
957.130.872 H
4.2 Map: Maps
This menu allows to further select among:
3AL 61259 AA AA
230
30 / 230
4.2.1 Map: Maps: Open/List ...

SCOPE
Open a map from the list of available maps. Before the chosen map opens, HP OpenView Windows saves
and closes the currently open map. Maps may be open with readonly or readwrite access.
SEQUENCE
1)
Selecting Map: Maps: Open/List... displays the Available Maps dialog box which gives a list
of the available maps. ( see Figure 10. )
Figure 10. Available Maps

2)
To open a map:
a ) Select the name of the map you want to open and click the [Open Map] button.
A confirmation box appears.

b ) Click [OK].
1AA 00014 0004 (9007) A4 ALICE 04.10
OpenView Windows closes all submap windows and dialog boxes of the open map. Then, HP OpenView
Windows opens the selected map.
Figure 11. Open View Windows Warning
ED
01
957.130.872 H
3AL 61259 AA AA
230
31 / 230
4.2.2 Map: Maps: New

SCOPE
Create a new map and configure basic map characteristics.
CONDITIONS
1AA 00014 0004 (9007) A4 ALICE 04.10
Selecting Map: Maps: New... displays the New Map dialog box of Figure 12.
Figure 12. File:New Map dialog box
ED
01
957.130.872 H
3AL 61259 AA AA
230
32 / 230
The New Map... dialog box contains the following fields:

Name. Mandatory, readwrite field

Enter text in this field for the name of the map. This name will be used by Netview to identify the map. Every
map must have a unique name. You can change the name of the map any time the map is opened with
readwrite access.
Layout for Root Submap. Readwrite
Displays the layout of the Root submap. The initial setting is Row/Column. You can choose the layout for
the root submap only during map creation. To change the layout, press the Option button to display the
menu of possible layouts, and choose the desired layout.
You can select among: None, Row/Column, Point to point, Bus, Star, Ring.
It is strongly suggested to set to None in order to displace the objects in the map without any
constraints. In this case objects will appear in the New Object Holding Area. The operator will drag them
to the suitable position.
Compound Status
You can modify the Compound Status scheme for the map open with read/write access.The Compound
Status scheme determines how Netview propagates status from symbols in child submaps to symbols of
the parent object.
The compound status setting applies to the entire map. You may choose one of the three settings using
the radio buttons:
Default
Propagate Most Critical. MANDATORY
Propagate At Threshold Value (0 100%)
Configurable Applications
Configurable Applications lists network and system management applications that are installed on the
OpenView platform. You can configure each application differently for each map.
To configure an application, select an application and click the [Configure For This Map...] button.
Select the application Map Management and click on Configure for This Map... button. The configuration
window is displayed.
Configure For This Map...
1AA 00014 0004 (9007) A4 ALICE 04.10
Displays a Configuration dialog box for the application. The Configuration dialog box contains
configuration settings that are specific to that application.
ED
01
957.130.872 H
3AL 61259 AA AA
230
33 / 230
The following configuration settings are available:

Type of SDH network synchronization enabled for this map . Three popup options are selectable:
Unset. If this option is selected the operator will not be able to perform any operations of
alignment of the local (WS) OVW data base to the SNML_IM data base.
Synchronize complete map (Map and Alarm Synchronization). If this option is selected the
operator will be able to perform operations of alignment of the local (WS) OVW data base to
the SNML_IM data base.
Syncronize Only Alarm on map.( DEFAULT) If this option is selected, the operator will be
able to perform operations of alarrm alignment of the local (WS) OVW data base to the
SNML_IM data base.
SDH network synchronization by site for this map, (DEFAULT=FALSE) if true, means that the
alignment will be executed geographically. If false will be executed logically. This field is effective only
if SDH network synchronization is enabled. Note that on geographical map only view operation can
be performed.
SDH synchronize ports for this map (DEFAULT=TRUE) means alignment of the local OVW data to
SNML_IM data for the data relevant to the ports.
SDH set attribute in creation enabled (DEFAULT=FALSE) means that the application will open the
View/Set attributes for each object added. (Not used)
SDH delete operation enabled on implemented object (DEFAULT=FALSE), if true means that it is
not possible to delete an object implemented. Deletion is only possible in OVwDb.
SDH Show uselabel on Layered map (DEFAULT=FALSE). If set to Enabled, in the layered maps the
user label is displayed with the payload structure, otherwise only the payload is displayed.
SDH Enable Synchronization Log. If true means that the system will provide a report for each
sinchronization occurrance.
SEQUENCE
To create a map:
a)
Select Map:Maps: New
The New Map dialog box appears.

b)
Enter a name for the new map.
c)
Modify map settings, such as the layout of the root submap, or the applications to configure, if
desired.
d)
In the Configuration window select Verify. If the parameters entered are correct, the following
message will appear in the Messages area :
1AA 00014 0004 (9007) A4 ALICE 04.10
All values are OK. The Messages area contains also notes which detail the values set above.
e)
Click [OK]. The Configuration window is closed automatically.
f)
Select OK in the New Map dialog box .
OpenView Windows creates the new map. A warning box is displayed informing the operator that the new
map has been created and giving him the choice of opening it or remaining in the current map.
ED
01
957.130.872 H
3AL 61259 AA AA
230
34 / 230

4.2.3 Map: Maps: Save Map As...

This menu allows you to make a copy of the open map and save it under a new name.
4.2.4 Map: Maps: Describe/Modify Map...
PURPOSE
Display and/or modify characteristics of the open map.
Name of map
Name of Home Submap
Compound Status
Configuration of Applications
Comments
PREREQUISITES
Map must be opened with readwrite access to modify any map characteristics.
CONDITIONS
You can view and/or modify the following characteristics from the open map:
Name
Name assigned to the map. Each map must have a unique name.
Home Submap
Name of the submap that is displayed when the map is open. When a map is first created, the home
submap is the root submap.
Click [Submap List...] to display the Submaps in Map dialog box, which lists the submaps of the open map.
To choose a submap as the home submap, select the desired submap name, and click the [Set As Home]
button.
1AA 00014 0004 (9007) A4 ALICE 04.10
Compound Status
Default
Propagate Most Critical : Mandatory
Propagate At Threshold Value
ED
01
957.130.872 H
3AL 61259 AA AA
230
35 / 230
Configurable Applications lists network and system management applications that are integrated with
OVW. You can configure each application differently for each map.
To configure an application, select an application and click the [Configure For This Map...] button.
The Configuration dialog box for the selected application is displayed. The Configuration dialog box
contains configuration settings that are specific to that application.
Applications may provide help information that is available from the dialog box [Help] button.
The only configurable application is Maps Management.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
The Save Map As... command can be used as follows:

1)
The operator logged on WS1 as snml, working on MAP1 with READ/WRITE access saves this
map by entering the command: Map: Maps: Save Map As... and assignes it the name MAP2.
2)
An other operator logged on WS2 as snml can open MAP2 with READ/WRITE access.
3)
The operator on WS1 creates a new topological object and places it on the map.
4)
The operator on WS2 can display the new object in this new Object Holding Area.
5)
The operator on WS1 issues Supervision: Placement: Store
6)
The operator on WS2 issues Supervision: Placement: Retrieve, thus displaying the new object
in the desired position.
01
957.130.872 H
3AL 61259 AA AA
230
36 / 230

Configurable Applications
4.2.5 Map: Maps: Delete...

SCOPE
Deleting a map deletes all symbols and submaps in the map.
PREREQUISITES
You must have readwrite permission to delete a map.
CONDITIONS
All objects in the map are deleted unless those objects are represented by symbols in another map.
SEQUENCE
To delete a map:
a)
Select Map: Maps: Delete...The Available Maps dialog box appears.
b)
Select the name of the map that you want to delete and click [Delete Map].
A confirmation box appears.

c)
Click [OK].
OpenView Windows deletes the map along with submaps and symbols, in that map.
DELETING THE OPEN MAP
1AA 00014 0004 (9007) A4 ALICE 04.10
When OpenView Windows is running, a map is always open. If you choose to delete the open map, the
following conditions occur:
The open map is closed and deleted. The User Default Map is opened.
If the open map you are deleting is the User Default Map, the map named Default is opened. It
becomes your new User Default Map.
ED
01
957.130.872 H
3AL 61259 AA AA
230
37 / 230
4.3 Map: Submap
Open/List...
New...
Describe/Modify...
Set this Submap As Home Delete...
Delete..
Delete this submap

This menu allows to further select among:
Figure 13. Map: Submap pulldown menu
4.3.1 Map: Submap: Open/List...

Open a submap from the list of available submaps in the open map.
It is not advisable to use this menu.
4.3.2 Map: Submap : New...
Create a new submap of the open map.
4.3.3 Map: Submap: Describe/Modify...
1AA 00014 0004 (9007) A4 ALICE 04.10
View and/or modify basic characteristics about the submap.

This menu gives the description of the main characteristics of the current submap. In particular it can be
used to add a graphical background. See description at Paragraph 5.1 Creating a geographical map
of section OPERATION.
ED
01
957.130.872 H
3AL 61259 AA AA
230
38 / 230
4.3.4 Map: Submap: Set This Submap As Home
1AA 00014 0004 (9007) A4 ALICE 04.10

You can specify the submap that is displayed when the map is opened.
4.3.5 Map: Submap: Delete...
Delete a submap from the list of submaps in the open map.
WARNING
For more detailed information refer to HPOV Users Guide.
4.3.6 Map: Submap: Delete This Submap...
ED
01
957.130.872 H
3AL 61259 AA AA
230
39 / 230
4.4 Map: Refresh Map
Update the topology of a map open with readonly access.

PREREQUISITES
Refresh Map applies only to maps opened with readonly access.
DESCRIPTION
Maps open with readonly access do not automatically receive updates on topological events such as the
addition or deletion of symbols, objects, or submaps, or the relocation of symbols by applications or other
users.
You can update the topology of a map open with readonly access by selecting File:Refresh Map. When
a map is refreshed all dialog boxes and submaps are first closed.
Status
Refresh Map is not required to update status. OpenView Windows automatically updates the status of all
symbols and objects in all submaps of the map.
PROCEDURE
To update the map topology:
a)
Select Map: Maps: Refresh Map. OpenView Windows updates the topology of the open map.
TROUBLESHOOTING
1AA 00014 0004 (9007) A4 ALICE 04.10
The Refresh Map button is greyed in a submap window of a snapshot and a map opened with read/write
access.
ED
01
957.130.872 H
3AL 61259 AA AA
230
40 / 230

PURPOSE
4.5 Map:Map Redo

This menu ( see Figure 14. herebelow ), allows to further select among:
Store: Map
Store: Map (no connections)
Store: Submap
Store: Submap (no connections)
Execute
Figure 14. Map pull down menu.
1AA 00014 0004 (9007) A4 ALICE 04.10
The above menus are detailed in the following.
ED
01
957.130.872 H
3AL 61259 AA AA
230
41 / 230
4.5.1 Map: Map Redo: Store Map
This command allows to store the commands required to create all topological objects contained in the
map on both ovwdb and mibdb.
SEQUENCE
1)
From the map pulldown menu bar select Map: Map Redo: Store: Map. The Map Redo Store
dialog box is presented.
2)
Enter the name of the saved map ( it can be the same or different from the name of the map
being saved) and click on OK button. Subsequent messages are presented to the user, namely:
Insert data and Copy Map <mapname> completed susccessfully . See Figure 15.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 15. Map Redo Store dialog box.
ED
01
957.130.872 H
3AL 61259 AA AA
230
42 / 230

SCOPE
4.5.2 Map: Map Redo: Store Map (no connections)

SCOPE
map on both ovwdb and mibdb. This option does not store any connection.
SEQUENCE
The sequence of the commands is the same as per paragraph 4.5.1 on page 42.
4.5.3 Map: Map Redo: Store Submap
SCOPE
submap on both ovwdb and mibdb.
SEQUENCE
The sequence of the commands is the same as per paragraph 4.5.1
N.B.
The connections terminated outside the current submap are not saved.
4.5.4 Map: Map Redo: Store Submap (no connections)

SCOPE
submap on both ovwdb and mibdb. This option does not store any connection.
SEQUENCE
The sequence of the commands is the same as per paragraph 4.5.1
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
The connections terminated outside the current submap are not saved.
01
957.130.872 H
3AL 61259 AA AA
230
43 / 230
4.5.5 Map: Map Redo: Execute
This command allows to execute all the commands previously stored by issuing the menu Map: Redo:
Store. This command can be applied to execute whichever map or submap, with or without connections.
CONDITIONS
IThe execute of a complete map ( with or without connections ) must be performed on an empty map.
IThe execute of a submap ( with or without connections ) must be performed on the submap window
consistent with the topological tree.
SEQUENCE
1)
From the map pulldown menu bar select Map: Map Redo: Execute. The List of saved maps
is displayed, as per Figure 16. on page 44.
Figure 16. List of saved maps.
1AA 00014 0004 (9007) A4 ALICE 04.10
2)
ED
Select the map to execute from the list and click on Get button. The command file describing
the object contained in the map/submap tp execute is launched and the relevant report is
displayed, as per Figure 17. on page 45. The involved objects are created in the mib data base
and the map/submap is automatically populated.
01
957.130.872 H
3AL 61259 AA AA
230
44 / 230

SCOPE

Figure 17. Execute map report.
1AA 00014 0004 (9007) A4 ALICE 04.10
Notice that the user has to adjust manually the object position in the map by dragging each object from
the new object holding area to the map working area. See Figure 18. on page 46
ED
01
957.130.872 H
3AL 61259 AA AA
230
45 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 18. Map: Map Redo: Execute: dragging nodes
ED
01
957.130.872 H
3AL 61259 AA AA
230
46 / 230
4.6 Map:Distribute Maps

The Map: Distribute Maps menu item allows to execute the following operations on the maps:
Map:Distribute Maps:Store map image
Map:Distribute Maps:Get/List map image
Map:Distribute Maps:Remove map image
Map:Distribute Maps:Lock map image
Map:Distribute Maps:Unlock map image
Map:Distribute Maps: Modify Username List
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 19. Map:Distribute Maps menu items.
ED
01
957.130.872 H
3AL 61259 AA AA
230
47 / 230
4.6.1 Map :Distribute Maps: Store Map Image
The purpose of this procedure is to save a map in the central mapDb repository.
CONDITIONS
The map is codified into an ASCII format.
The Store Map dialog window allows to select:
Map name. Digit the map name.The default name is the current map name.
Username List. It is the list of the users which are allowed to read this map. Default ALL Users.
The items of the list are separated by a comma or a blank.
If the map was previously locked, this command causes its automatic unlock.
SEQUENCE
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
In the Network Window select Map:Distribute Maps:Store map image. The Store Map dialog window
is displayed. ( see Figure 20. )
Figure 20. Store Map dialog box.
ED
01
957.130.872 H
3AL 61259 AA AA
230
48 / 230

PURPOSE
Enter the selection parameters (see above point CONDITIONS)
c)
Selecting OK the Work in progress message is displayed in the message Area.
1AA 00014 0004 (9007) A4 ALICE 04.10

b)
After a few seconds the messages Current Map is stored in SNLMAP DB and Copy Map successful
ly completed. A message is sent to the users included in the Username list.
Selecting Cancel the selection window is closed without any further action.
Selecting Help the description of the relevant menu option is displayed.
ED
01
957.130.872 H
3AL 61259 AA AA
230
49 / 230
4.6.2 Map: Distribute Maps: Get/List Map Images
The purpose of this procedure is to display the list of the available maps, select and create a map on the
local Db. All data are dumped from the central data base.
CONDITIONS
The Get Map operation can be executed only starting from an empty map.
The Get Map dialog window contains the list of all available maps with:
Layout
Creation Time
Comment
PROCEDURE
a)
In the Root window select Map:Distribute Maps:Get/List map images.
The Get Map dialog window containing the list of all the available maps is displayed.
b)
Select the map to get.
c)
Click Get button and the selected image is created in the local data base.
After a few seconds the messages Current Map will be synchronized to selected < map name > is
displayed.
Wait until the message Get Map completed successfully is presented, then...
Selecting Close the selection window is closed without any further action.
1AA 00014 0004 (9007) A4 ALICE 04.10
After a few seconds the requested map is displayed.
ED
01
957.130.872 H
3AL 61259 AA AA
230
50 / 230

PURPOSE
4.6.3 Map:Distribute Maps:Remove Map image

PURPOSE
The purpose of this procedure is to remove a map from the central data base.
CONDITIONS
The Delete Map dialog window contains the list of all available maps with:
Map name
Layout
User list (users which can access it)
Creation Time
Lock (the user actually locking this map)
Comment
PROCEDURE
a)
In the Network window select Map:Distribute Maps:Remove map image.
The Delete Map dialog window containing the list of all available maps is displayed.
b)
Select the map to delete.
c)
Selecting Delete, the Map image is removed.

After a few seconds the requested map is removed and the message Delete map successfully com
pleted is displayed.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
51 / 230
4.6.4 Map :Distribute Maps: Lock map image
The purpose of this procedure is to lock a map image. This could be useful during map changes, to screen
a get operation by another user.
CONDITIONS
This procedure can be executed only by the System Administrator.
PROCEDURE
a)
In the Network window select File:Distribute maps:lock map image.

The Lock Map dialog window containing the list of all the available maps is displayed.
b)
Select the map to lock.
c)
Selecting Lock a dialog box appears, asking for confirmation. If you select OK, the map is locked.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 21. Map :Distribute map: Lock map image
ED
01
957.130.872 H
3AL 61259 AA AA
230
52 / 230

PURPOSE
4.6.5 Map :Distribute Maps: Unlock map image

PURPOSE
The purpose of this procedure is to unlock a map image.
CONDITIONS
This procedure can be executed only by the System Administrator.
PROCEDURE
a)
In the Network window select File:Distribute maps:unlock map image.

The Unlock Map dialog window containing the list of all the available maps is displayed.
b)
Select the map to unlock.
c)
Selecting Unlock a dialog box appears, asking for confirmation. If you select OK, the map is
unlocked.
1AA 00014 0004 (9007) A4 ALICE 04.10
Selecting Help is displayed the description of the relevant menu option .
ED
01
957.130.872 H
3AL 61259 AA AA
230
53 / 230
4.6.6 Map :Distribute Maps: Modify Username List

PURPOSE
The purpose of this procedure is to modify the Username List
CONDITIONS
The dialog window contains the list of all available maps with:
Map name
Layout
User list (users which can access it)
Creation Time
Lock (the user actually locking this map)
Comment
PROCEDURE
a)
In the Network window select File:Distribute Maps:Modify Username List.
The relevant dialog window containing the list of all available maps is displayed.
1AA 00014 0004 (9007) A4 ALICE 04.10
b)
ED
Select the map to modify. Select button Modify. The dialog box Modify Username is displayed.
01
957.130.872 H
3AL 61259 AA AA
230
54 / 230

Figure 22. Modify Username dialog box
c)
Enter the new authorized userlist. Select OK.

1AA 00014 0004 (9007) A4 ALICE 04.10
Selecting Help is displayed the description of the relevant menu option.
ED
01
957.130.872 H
3AL 61259 AA AA
230
55 / 230
4.7 Map: Close Submap
4.8 Map: Exit

PURPOSE
Close all submap windows and dialog boxes of the open map and exit from HP OpenView Windows.
PROCEDURE
To exit HP OpenView Windows:
a)
Select Map: Exit. A confirmation box is displayed asking if you want to exit HP OpenView Windows.
(See Figure 23. )
Figure 23. Exit warning box
1AA 00014 0004 (9007) A4 ALICE 04.10
b)
Click [OK] in the confirmation box.
HP OpenView Windows closes all dialog boxes and submaps of the open map (and the snapshot if it is
open). OpenView Windows exits.
ED
01
957.130.872 H
3AL 61259 AA AA
230
56 / 230

This command closes the submap window and dialog boxes of the open submap.

5 SDH NETVIEW: EDIT SUBMENU

5.1 Introduction
The Edit pulldown menu allows to select the following items (see Figure 24. herebelow):
Edit:Cut: From This Submap
Edit:Paste
Edit:Hide
Edit:Show Hidden Objects
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 24. Edit pulldown menu
ED
01
957.130.872 H
3AL 61259 AA AA
230
57 / 230
5.2 Edit: Cut: From This Submap
This menu item allows to cut the selected symbols and place them into the cut buffer.
The symbol is removed from the submap of the available NEs but it is not removed from MIB
database.
PROCEDURE
To cut the selected symbols from this submap:
a)
Select one or more symbols in the submap.
b)
Select Edit: Cut : From This Submap.
A confirmation box is presented.

c)
Click [OK].
OpenView Windows removes the selected symbols from this submap, and stores them in the cut buffer.
To paste the cut NE(s) onto a submap,
a)
Display the submap on which you want to paste the NE(s).
b)
Select Edit: Paste.
The NE(s) in the cut buffer is pasted in the New Object Holding Area.
NOTE
The Cut and Paste procedure is used in the Network Construction phase.
WARNING
You cannot cut a connection symbol; the only action delete (in MIB) is allowed.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
58 / 230

PURPOSE
5.3 Edit: Paste

PURPOSE
Paste the symbols in the cut buffer ( usually NEs from Available NE submap ) onto a submap in the open
map.
Paste is useful for:
Moving a symbol from submap to submap.
Populating a submap with symbols from other submaps of your own choosing.
CONDITIONS
The paste operation is local to the submap you are pasting.
Paste is the second half of the cut and paste operation. Paste places all the symbols that are stored in the
cut buffer onto the open map.
Symbols in the cut buffer may be from a single submap, or from multiple submaps of the open map. All
symbols are pasted onto a single submap.
Effects of Automatic Layout
OVW pastes symbols in the New Object Holding Area for each submap in which automatic layout is
disabled (or set to no layout).
OVW pastes symbols into the submap layout on submaps in which automatic layout is enabled.
PROCEDURE
To paste a symbol or symbols onto a submap:
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
ED
Select Edit: Paste.

When pasting the NE onto a submap, the Node associated to the NE is created. The implementation
state of the Node is Not Implemented.
01
957.130.872 H
3AL 61259 AA AA
230
59 / 230
5.4 Edit: Delete: From the Map
Delete the symbol of an object from of the open map.

CONDITIONS
The delete operation is the same as the cut operation except that symbols are not placed in the cut buffer.
HP OpenView Windows deletes them.
PROCEDURE
To delete a symbol or symbols from all submaps of the open map:
a)
Select one or more symbols in the submap.
b)
Select Edit: Delete : From All Submaps.
HP OpenView Windows displays a confirmation box.

c)
Click [OK].
All symbols representing the selected objects are deleted.
1AA 00014 0004 (9007) A4 ALICE 04.10
When symbols are deleted only from OVW (using the local delete command) it is normal that no deletion
is performed in RM MIB and, as a consequence, the next time that an upload is performed from the MIB
the objects will appear again. The delete command local to OVW should be used only by the system
administrator in conjunction with an appropriate map synchronization level in order to create maps with
a reduced number of network elements for path operators.
ED
01
957.130.872 H
3AL 61259 AA AA
230
60 / 230

PURPOSE
5.5 Edit : Hide

The Edit:Hide menu item allows to further select the following items (see Figure 24. ):
Edit:Hide:From This Submap
Edit:Hide:From All Submaps
5.5.1 Edit: Hide : From This Submap...
Hide selected symbols from this submap. The hide operation is useful when you no longer want to display
a symbol and an application refuses to allow OVW to delete a symbol, or the symbol reappears after having
been deleted because the object is discovered again.
WARNING
For more detailed information refer to HPOV Users Guide. It is not advisable to use this menu.
5.5.2 Edit: Hide : From All Submaps...
Hide the symbols of selected objects from all submaps of the open map. The hide operation is useful when
you no longer want to display a symbol and an application refuses to allow OVW to delete a symbol.
WARNING
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
61 / 230
5.6 Edit:Show Hidden Objects

WARNING
The Edit:Show Hidden Objects menu item allows to further select the following items:
Edit:Show Hidden Objects:For This Submap
Edit:Show Hidden Objects:For All Submaps
5.6.1 Edit: Show Hidden Objects : For This Submap
Displays all symbols that were hidden in a previous hide operation.
5.6.2 Edit: Show Hidden Objects : For All Submaps
1AA 00014 0004 (9007) A4 ALICE 04.10
Unhide the symbols that have been previously hidden on all submaps of the open map.
ED
01
957.130.872 H
3AL 61259 AA AA
230
62 / 230

6 SDH NETVIEW: LOCATE SUBMENU

6.1 Introduction
The Locate pulldown menu item allows to further select the following items (see Figure 25. ):
Locate:Selected Object List...
Locate: Objects
Locate: Submap List...
Figure 25. Locate pulldown menu
6.2 Locate: Selected Object List...

A list of all selected objects on the open map or open snapshot is presented. The selection list displays
objects by their selection name. You can display or modify the list of selected objects by operations
available in the selection list dialog box.
1AA 00014 0004 (9007) A4 ALICE 04.10
For more detailed information refer to Hp OV Users Guide.
ED
01
957.130.872 H
3AL 61259 AA AA
230
63 / 230
6.3 Locate:objects

The Locate:Objects pulldown menu allows to select one of the following submenus:
Locate:Objects:By Selection Name...
Locate:Objects:By Attribute...
Locate:Objects:By Comment...
Locate:Objects:By Symbol Status...
Locate:Objects:By Symbol Type...
Locate:Objects:By Symbol Label...
6.3.1 Locate: Objects : By Selection Name...
This menu item allows to locate objects by their selection name.
Put the selection names of located objects into the selection list.
Open the submap(s) of located objects.
You can locate objects in:
Maps opened with readwrite access.
Maps opened with readonly access.
Snapshots.
6.3.2 Locate: Objects : By Attribute...
This menu item allows to locate objects in either the open map or a snapshot based on a value of a specific
attribute.
Put the selection names of located objects into the selection list.
Exact Match
Locates only those objects whose attribute value exactly matches the string entered. To switch to the exact
match search, click on the [Exact Match] radio button. You must enter the complete string in this mode.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
64 / 230

6.3.3 Locate: Objects : By Comment...

Locate all objects that have a specific comment or portion of a comment. Search for objects by keywords
assigned by you.
Put the comment string into the Form.


6.3.4 Locate: Objects : By Symbol Status...
This menu item allows to locate objects based on the status of their symbols.
Select a state in the relevant list.

You can perform locate tasks from:

6.3.5 Locate: Objects : By Symbol Type...
This menu item allows to locate objects based on the symbol type.
Select a symbol class and symbol subclass.


6.3.6 Locate: Objects : By Symbol Label...
Enter a symbol label.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
65 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
66 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10

7 SDH NETVIEW: VIEW SUBMENU

7.1 Introduction
The View pulldown menu allows to select one of the following menu items (see Figure 26. ):
View:Highlights
View:Tool Bar
View: Pan and Zoom
View: Overlay Submap
View:Redo Layout
View: EML...
View:SDH Layer...
View:Object Attributes...
View:Clear Alarmed Object
View:Event History..
Figure 26. View pull down menu.
ED
01
957.130.872 H
3AL 61259 AA AA
230
67 / 230
7.1.1 View:Highlights
View:Highlights:Select Highlighted
View:Highlights:Clear Highlighted
7.1.1.1 View: Highlights : Select Highlighted
7.1.1.2 View: Highlights: Clear Highlights
Clear the highlights of all objects in the map.
Clear highlights after objects have been highlighted from a locate operation.
Clear highlighted objects after an application has highlighted objects in the map. ( e.g. Locate ... )
OpenView Windows and applications may select objects in the map. When an object is highlighted, all
symbols representing that object in open submaps are displayed in inverse video.
7.1.1.3 View: Tool Bar
The View:Tool Bar menu item allows the selection of:
View: Tool Bar: Off For All Submaps. If you select this command the Toolbar disappears from all submaps.
View: Tool Bar On For All Submaps. If you select this command the Toolbar is available in all submaps.
7.1.1.4 View: Pan and Zoom
Panner. Displays the Panner. The panner lets you zoom in on details within a submap window and pan
from area to area in the submap window.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
68 / 230

The View:Highlights menu item allows the selection of:
7.1.2 View: Overlay Submap

The View: Overlay Submap menu item allows the selection of:
View:Overlay Submap: On For this Submap
View:Overlay Submap: Off For this Submap
View:Overlay Submap: On For All Submaps
View:Overlay Submap: Off For All Submaps
The above listed menus allow to overlay or not submaps, i.e. to display either only the last opened submap
or all open submaps
7.1.3 View: Redo Layout

Enables you to invoke the layout algorithm for a specific submap.
7.1.4 View: EML...

PURPOSE
The purpose of this procedure is to utilize the RM screen to display a remote 1353SH application running
on the selected EML.
1AA 00014 0004 (9007) A4 ALICE 04.10
PROCEDURE
a)
In the Netview window select a node belonging to the 1353SH you want to display .
b)
Select a node from the map and issue the pulldown menu item View: EML...
The Equipment view of the selected Network Element is displayed.
ED
01
957.130.872 H
3AL 61259 AA AA
230
69 / 230
7.1.5 View: Object Attributes

The View: Object Attributes allows to select among the following submenus:
View: Object Attributes: Long Report
View: Object Attributes: Short Report
View: Object Attributes: OVw Symbol Information
7.1.5.1 View: Object Attributes: Long Report
PURPOSE
The purpose of this procedure is to display a report listing all attributes of the selected object.
PROCEDURE
a)
In the Netview window select the object to display.
b)
Select the pulldown menu item View: Object Attributes: Long Report
The long report is displayed. An example of long report is shown in Figure 27.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 27. Example of View: Object Attributes: Long Report.
ED
01
957.130.872 H
3AL 61259 AA AA
230
70 / 230
7.1.5.2 View: Object Attributes: Short Report

PURPOSE
The purpose of this procedure is to display a report listing the main attributes of the previously selected
object.
SEQUENCE
a)
In the Netview window select the object to display.
b)
Select the pulldown menu item View: Object Attributes: Short Report
The report is displayed. An example of short report is shown in Figure 28.
Figure 28. Example of View: Object Attributes: Short Report

7.1.5.3 View: Object Attributes: OVw Symbol Information
1AA 00014 0004 (9007) A4 ALICE 04.10
For Developer staff only.
ED
01
957.130.872 H
3AL 61259 AA AA
230
71 / 230
7.1.6 View: Clear Alarmed Object (acknowledge)
The scope of this procedure is to acknowledge (clear) the alarm indication of the selected object on the
Netview map.
SEQUENCE
a)
In the Netview window select the object to clear.
b)
Select the pulldown menu item View: Clear Alarmed Object. The alarm indication is cleared only
on the Netview map for the selected object and the symbol is distinguished by an exclamation mark.
A subsequent alarm affecting the same object is displayed on the map only for greater severity.
1AA 00014 0004 (9007) A4 ALICE 04.10
It starts the Event logger application and automatically load into the object instance area all the selected
objects (if any).
ED
01
957.130.872 H
3AL 61259 AA AA
230
72 / 230

SCOPE

8 SDH NETVIEW: CONSTRUCTION SUBMENU

8.1 Introduction
The Construction pulldown menu allows to select one of the following items ( See Figure 29. ):
Construction:Upload EML(s) info...
Create Virtual
Delete Virtual
Create
Delete (in MIB)
Link to a topology
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 29. Construction pull down menu
ED
01
957.130.872 H
3AL 61259 AA AA
230
73 / 230
The Construction:Upload EML(s) info submenu allows to select the following items (See Figure 29. on
page 73):
Construction:Upload EML(s) info:Available EML

Construction:Upload EML(s) info:Available NEs in an EML.
Construction:Upload EML(s) info:Available NE ports
8.2.1 Construction:Upload EML(s) info:Available EMLs

PURPOSE
The purpose of this procedure is to upload the available EMLs.
CONDITIONS
This command retrieves data from the central SNML IM database. The available EMLs are defined in the
database during the installation.
PROCEDURE
a)
In the relevant subnetwork window or ring window select Construction:Upload EML(s) info :
Available EMLs. A dialog box of Work in progress is presented. A message is displayed to the user:
Uploading EMLs from ...... SNMLIM
1AA 00014 0004 (9007) A4 ALICE 04.10
The dialog box automatically closes and the window of the Available EMLs is displayed (See Figure 30. ).
Figure 30. Available EMLs
ED
01
957.130.872 H
3AL 61259 AA AA
230
74 / 230

8.2 Construction:Upload EML(s) info...
8.2.2 Construction:Upload EML(s) info:Available NE

PURPOSE
The purpose of this procedure is to upload the available NE.
CONDITIONS
The relevant EML has been already uploaded and the Available EML window is displayed on the screen.
This command causes to retrieve data from the central SNML IM database.
PROCEDURE
a)
In the Available EML window select (left click) the relevant EML
b)
In the EML select Construction:Upload EML(s) info : Available NEs in a EML.
A dialog box of Work in progress informs the Operator: Uploading NEs from ...... SNMLIM .
The dialog box closes automatically and the window of the Available NEs is displayed (See Figure 31. ).
NOTE
1AA 00014 0004 (9007) A4 ALICE 04.10
The Available EML window is a map independent from the map hierarchy.
Figure 31. Available NEs in a EML
ED
01
957.130.872 H
3AL 61259 AA AA
230
75 / 230
8.2.3 Construction:Upload EML(s) info:Available NE ports

SCOPE
The purpose of this procedure is to upload the information relevant to the available NE ports.
CONDITIONS
The relevant object window must be opened and one or more NE must be selected.
SEQUENCE
a)
In the ring window select Construction:Upload EML(s) info : Available NE ports.
A dialog box of Work in progress is presented.

b)
Click twice on the relevant Network Element (NE)

The NE port detail is displayed (See Figure 32. ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 32. NE port detail
ED
01
957.130.872 H
3AL 61259 AA AA
230
76 / 230

8.3 Construction:Create Virtual

Virtual objects are useful to establish a connection between various 1354RMs or to create a path
terminated to a node non controlled by 1354RM. A path is defined as non terminated if either one of the
NAPs or both are not in the 1354RM domain. A nonterminated path describes a path between a TTP
associated to a PDH port and a real CTP.
The Construction:Create Virtual menu item allows the selection of the following submenus
(See Figure 33. ):
Construction:Create Virtual: Ne...
Construction:Create Virtual: Port...
Construction:Create Virtual: NSDHPort...
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 33. Construction:Virtual Elements:Create
ED
01
957.130.872 H
3AL 61259 AA AA
230
77 / 230
8.3.1 Creating a Virtual EML
a)
cd /usr/snml/bin
b)
nlCreateInDb eml id <n.o>
8.3.1.1 Construction:Create Virtual: NE...

SCOPE
The scope of this procedure is to add a virtual NE.
SEQUENCE
a)
Select EML0 or the Virtual EML where you want to create the virtual NE.
b)
In the OVW map select menu Construction:Create Virtual:NE... A dialog box is presented, asking
for the specification of NE user label and site name. The command confirmation is required.
c)
To verify that the new NE has been successfully created, select the EML and execute the command
Construction:Upload EMLinfo: NEs...: the new NE is present in the submap of the Available NEs.
( See Figure 34. )
Figure 34. Create a virtual NE
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Alternatively thi procedure can be executed fro browser interface by clicking on tool button
Create a Virtual Network Element. See Figure 35.
01
957.130.872 H
3AL 61259 AA AA
230
78 / 230

For more detail refer to the Installation Guide.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 35. Virtual tool buttons.
ED
01
957.130.872 H
3AL 61259 AA AA
230
79 / 230

8.3.2 Construction:Create Virtual: Port...
The scope of this procedure is to add a virtual port.

PROCEDURE
a)
Select the NE where you want to create the virtual port.
b)
In the OVW map select menu Construction:Create Virtual:Port... A dialog box is presented, asking
for the specification of Port user label
c)
Digit the required parameters: Port type ( SDH/PDH) and port bit rate ( STM1/4/16 for SDH or
C3/C4/C12 for PDH). A confirmation is required.
N.B.
Create a Virtual Port. See Figure 35.
Figure 36. Create a virtual port
1AA 00014 0004 (9007) A4 ALICE 04.10
d)
ED
To verify that the port has been successfully created, select the relevant NE and execute the
command Construction:Upload EMLinfo:Ports...: the new port is in the dialog box of the Available
Ports.
01
957.130.872 H
3AL 61259 AA AA
230
80 / 230

SCOPE
8.3.3 Construction:Create Virtual: NSDHPort...

SCOPE
The purpose of this procedure is to add many virtual SDH ports.
SEQUENCE
a)
Select the NE where you want to create the virtual ports.
b)
In the OVW map select menu Construction:Create Virtual: NSDHPort.. A dialog box is presented,
asking for the specification of port quantity, Port prefix, port type, initial port number.
c)
Enter Yes to confirm (See Figure 37. ).
Figure 37. Create many virtual ports
1AA 00014 0004 (9007) A4 ALICE 04.10
d)
ED
To verify that the port has been successfully created, select the relevant NE and execute
Construction: Upload: Available NE PORTS; then click twince on the NE (virtual) icon. The child
submap opens displaying the port which has been just created.
01
957.130.872 H
3AL 61259 AA AA
230
81 / 230
NOTE
Cut and Paste the objects to the Map
Create the Connection
Implement the objects and the connection
Create the Path
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Create N Virtual Ports. See Figure 35.
01
957.130.872 H
3AL 61259 AA AA
230
82 / 230

After creating the virtual objects, you could follow the usual procedures:
8.3.4 Construction:Delete Virtual

SCOPE
The purpose of this procedure is to delete a virtual object .
CONDITIONS
The OVW map is open.
The virtual element to delete has no subordinate objects.
PROCEDURE
a)
In the OVW map select the virtual object to delete.
b)
In the OVW map select menu Construction:Virtual Element:Delete from MIB. The dialog box of
Figure 38. is presented. Execute the command as specified in the dialog box.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 38. Example of eml deletion
ED
01
957.130.872 H
3AL 61259 AA AA
230
83 / 230
8.4 Construction:Create
1AA 00014 0004 (9007) A4 ALICE 04.10
Construction:Network
Construction:Subnetwork
Construction:Ring
Construction:Create Connection
ED
01

The Construction:Create menu item allows the selection of the following submenus:
957.130.872 H
3AL 61259 AA AA
230
84 / 230
8.4.1 Construction:Create:Network

SCOPE
The scope of this procedure is to construct a new network.
CONDITIONS
This command can be executed only in the Root window.
SEQUENCE
a)
In the Root window select Construction:Create: Network.
The Add Object dialog window is displayed (See Figure 39. ).
Figure 39. Create Dialog box

b)
Insert the network name and click on Create button. The Create Network dialog box is closed and
the symbol of the network just created is displayed in the New Object Holding Area.
1AA 00014 0004 (9007) A4 ALICE 04.10
You can point with the middle button of the mouse at the graphical symbol and drag it to the center of the
window working area.
ED
01
957.130.872 H
3AL 61259 AA AA
230
85 / 230
8.4.2 Construction:Create:Subnetwork
The purpose of this procedure is to construct a new subnetwork.

SEQUENCE
The new subnetwork must be constructed in network submap. Open the Network submap if it is still closed.
The Network window can be opened by moving the mouse at the network symbol in the Root submap and
clicking twice on it.
The Root submap is displayed by pressing the Root button on HPOV toolbar of each window.
PROCEDURE
a)
Open the Network window, if it is still closed.
b)
Select Construction:Create:Subnetwork. The Create Subnetworkt dialog box is displayed.
c)
Insert the subnetwork name and click on Create botton. The Create subnetwork dialog box is closed
and the symbol of the subnetwork just created is displayed in the New Object Holding Area. (if map
layout is none).
The Create Object dialog box contains the tool button Close which, if pressed, aborts the subnetwork
construction action .
1AA 00014 0004 (9007) A4 ALICE 04.10
d)
ED
You can point with the middle button of the mouse at the graphical symbol and drag to the center of
the window working area.
01
957.130.872 H
3AL 61259 AA AA
230
86 / 230

SCOPE
8.4.3 Construction:Create:Ring

SCOPE
The purpose of this procedure is to construct a ring .
CONDITIONS
This procedure must be executed in the Subnetwork window.
PROCEDURE
a)
b)
If the Subnetwork submap is still closed, in the Root submap click twice on the symbol of the relevant
Network. The Subnetwork submap is opened.
In the Subnetwork submap select Construction:Create:Ring.
The Create Ring dialog box is displayed. (See Figure 40. )

c ) Insert:
user label
ET tipy (SNCPU/2FMSSpring/Meshed/4FMSSpring
STM type (STM1/STM4/STM16/STM64)
Fiber No. (2/4)
Global Configuration (True/False) and click on CREATE button.

d)
e)
The Create Ring dialog window is closed and the symbol of the ring just created is displayed in the
New Object Holding Area.
By clicking on the tool button Close you clear the create operation.
You can point with the middle button of the mouse at the graphical symbol and drag to the center of
the window working area.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 40. Create Ring dialog box
ED
01
957.130.872 H
3AL 61259 AA AA
230
87 / 230
8.5 Construction:Create Connection
The purpose of this procedure is to create a connection.

CONDITIONS
Only SDH ports can be connected in the map.
The NEs are placed in the correct submap and the ports have been uploaded.
1AA 00014 0004 (9007) A4 ALICE 04.10
SEQUENCE
a)
Select View: Overlay Submap: off for all submap in order to display more submaps at the same time
b)
Open the submaps of the nodes to the connected
c)
Select a couple of ports to be connected (use the Control button of the keyboard to select the second
port), then execute Construction: Create:Connection (alternatively press F12). In the Create
Connection dialog box ( see Figure 41. ) enter the connection name and click on Create button. The
connection is hence created and is displayed in the parent submap(s).
Figure 41. Create connection dialog box.
ED
01
957.130.872 H
3AL 61259 AA AA
230
88 / 230

SCOPE

Having created the connection, an external connection symbol is created in the submaps which
contain the connected objects. The external connection symbol label contains the name of the
object connected at the other end plus the connection name.
The connection is not visible in the Node submap which now contains only the ports not
connected. See Figure 42.
Figure 42. Connection just created.
1AA 00014 0004 (9007) A4 ALICE 04.10
d)
ED
Create all the remaining connections as per above point c )
01
957.130.872 H
3AL 61259 AA AA
230
89 / 230
NOTE 2
Alternatively, only after network implementation, the Create Connection operation can be executed
from browser interface.
CONDITIONS
This procedure can be used for toplogy modifications after the network implementation. Alternatively
the operator can use the Create Connectoin procedure from the Netview map.
SEQUENCE
1)
Select from the browser the nodes to connect and issue the command Display:Related
items:Ports in node. The relevant lists are displayed. See Figure 43.
Figure 43. Ports in Node: Create Connection.
1AA 00014 0004 (9007) A4 ALICE 04.10
2)
ED
As in Figure 43. , select the ports ( asignment state=observed ) to connect and click on Create
Connection button. The Create Connection dialog box is displayed. See Figure 44.
01
957.130.872 H
3AL 61259 AA AA
230
90 / 230

NOTE 1
Notice that each WEST port must be connected to an EAST port on the connected NE, if the NE is
contained in a Ring.

Figure 44. Create Connection dialog box.

3)
The Create Connection dialog box already contains the icons of the ports to connect. Digit the
connecion name and click on Create Connection button. The new connection is created and
the view of the structure is displayed. See Figure 45. The new connection is visible in the maps.
Figure 45. Physical connection: Implement.
1AA 00014 0004 (9007) A4 ALICE 04.10
4)
The new connection is also displayed in netview map.
Detailed descriptions of the browser can be found at chapters 12 to 15 of this section.
ED
01
957.130.872 H
3AL 61259 AA AA
230
91 / 230
8.6 Construction: Link to a topology
Construction: Link to a topology: Add

This command is used in the creation of the line/radio systems. See description at chapter Operation
of this book.
Construction: Link to a topology: Remove
1AA 00014 0004 (9007) A4 ALICE 04.10
This command is used to delete a line/radio link. See description at chapter Network Configuration
of the Handbook Operation.
ED
01
957.130.872 H
3AL 61259 AA AA
230
92 / 230

The Construction: Link to a topology pulldown menu allows to select one of the following options:

9 SDH NETVIEW: SUPERVISION SUBMENU

9.1 Introduction
The Supervision pulldown menu allows to select one of the following menu items (See Figure 46. ):
Supervision:Implement Objects
Supervision:Deimplement Objects
Supervision:Placement
Supervision:Configuration
Supervision::Synchronize
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 46. Supervision pulldown menu
ED
01
957.130.872 H
3AL 61259 AA AA
230
93 / 230
9.2 Supervision: Implement Objects
The purpose of this procedure is to implement the selected object.

CONDITIONS
The color of the objects after the implementation depends on their alarm status.
All objects contained in the object to implement, will be implemented.
In case of Network Implementation, the MSTPs and the MSTrails will be created in the MIB database.
PROCEDURE
a)
Open the window containing the object to implement.
b)
Select the object to implement.
c)
Select the Supervision:Implement Object pulldown menu. An example of dialog box for a Network
Implement action is shown in Figure 47. At the end of the Implement process the object changes
status from Deimplemented ( dark brown ) to Implemented ( green ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 47. Implement Network
ED
01
957.130.872 H
3AL 61259 AA AA
230
94 / 230

SCOPE
9.2.1 Supervision: Deimplement Objects

SCOPE
The purpose of this procedure is to deimplement the selected object .
CONDITIONS
The color of the objects after the deimplementation depends on their alarm status.
All objects contained in the object to deimplement will be automatically deimplemented.
In the MIB database the MSTPs and the MSTrails go to the deimplemented state.
PROCEDURE
a)
Open the window which contains the object to deimplement.
b)
Select the object to deimplement.
c)
Select the Supervision:Deimplement Object pulldown menu.
9.2.2 Supervision: Placement: Store

Supervision: Placement: Store. This command allows to store in MIB data base the coordinates of the
topological objects, for the entire map, for the current submap or for the current submap including the
related child submaps.
9.2.3 Supervision: Placement: Retrieve: Map
Supervision: Placement: Retrieve: Map This command allows to retrieve from MIB data base the
coordinates of all topological objects, for the entire map.
9.2.4 Supervision: Placement: Retrieve Not Placed
1AA 00014 0004 (9007) A4 ALICE 04.10
Supervision: Placement: Retrieve: Not Placed This command allows to retrieve from MIB data base the
coordinates of all topological objects actually displayed in the New Object Holding Area. This could apply
for a user working in ReadOnly modality.
ED
01
957.130.872 H
3AL 61259 AA AA
230
95 / 230
9.2.5 Supervision:Configuration
Supervision:Configuration:Download
Supervision:Configuration:Eml<>Ne Audit
Supervision:Configuration: Synch.equipment Eml<>NML
The Supervision:Configuration:Download menu contains options Enable and Disable, respectively for
Eml or Ne/Node.
9.2.5.1 Supervision:Configuration:Download
For the Supervision:Configuration:Download pulldown menu item two options are available:
Enable
Disable
PURPOSE
EML Configuration Download Enabled/Disabled. ( NOT AVAILABLE FOR TSDIM ). This

functionality provides the operator with the ability to change the Configuration Download mode
of each NE belonging to the EML.
NE Configuration Download Enabled/Disabled. This functionality provides the operator with

the ability to change the Configuration Download mode of the NE.
If the Configuration Download mode is enabled, each request received by the EML and
addressed to the NE is forwarded to the NE.
If the Configuration Download mode is disabled, each request received by the EML and
addressed to the NE is not propagated to the NE.
CONDITIONS
The operation is accepted if:
no audit activity is already in progress for the NE
the NE is not a virtual NE
1AA 00014 0004 (9007) A4 ALICE 04.10
If the operation is accepted, a command is sent to the EML in order to set the Configuration
Download attribute of the NE to the proper value (enabled/disabled).
ED
01
957.130.872 H
3AL 61259 AA AA
230
96 / 230

The Supervision:Configuration pulldown menu allows to select one of the following menu items:

PROCEDURE
a)
Select Construction:Upload EML info.
b)
In the window of the Available EMLs, select the EML and issue the command:
Supervision:Configuration:Download: Enable/Disable:EML
NOTE 1 The above mentioned commands can be also launched from the relevant Browser popup
menus.
NOTE 2
In the Takeover procedure the main steps are:
Disable the download for the EML or NE
Network construction, Network implementation
Payload configuration, Upload NAPs, Setup HO trails , Path definition, allocation,

implementation.
manually
batch utility
Execute Audits and check Processing error alarm list, if any.
Enable the download for the EML or NE
NOTE 3 Using the Browser you can verify the following attributes;
NE
ConfigDownloadStatus
(Enabled/Disabled/Enabling/Disabling/Fail
ToEnable/FailToDisable)
neNotEmlAligned
(Aligned/Misaligned/Auditing/Waitingfortacti
vity/AuditFailed )
Colors are as follows: aligned=green, misaligned=yellow, auditing=brown, waiting for audit=gray, audit
failed=red.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
EML
auditStatus
(AuditInProgress/noAuditInProgress0
downloadStatus
(allNEsAreEnabled/allNEsAreDisabled/some
NEsAreDisabled/downloadIn
ProgressOnSomeNEs)
957.130.872 H
3AL 61259 AA AA
230
97 / 230
ALIGNED
MISALIGNED
AUDIT

A basic flow chart of the audit process is shown in Figure 48. ( for SENIM info model only )
AUDIT
FAILED
AUDIT
AUDIT
WAIT(ING)
FOR
AUDIT
TIMEOUT
YES
EXPIRED
NO
the EML starts running the

AUDITING
YES
auditing
NO (Restart)
AUDIT OK
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 48. Audit basic flowchart
ED
01
957.130.872 H
3AL 61259 AA AA
230
98 / 230
9.2.5.2 Supervision:Configuration:Eml<>Ne Audit ( for SENIM info model only )

PURPOSE
This functionality allows the operator to force the EML to perform the audit activity on the specified NE in
order to check if the EML DB is aligned with the NE one.
CONDITIONS
the Configuration Download towards the involved NE is disabled
no other audit activity is already running for the EML
the EML has not a SENIM version earlier than the V3.2
PROCEDURE
a)
b)
Supervision:Configuration:Eml<>Ne Audit
1AA 00014 0004 (9007) A4 ALICE 04.10
NOTE. The above mentioned command can be also launched from the relevant Browser popup menu.
ED
01
957.130.872 H
3AL 61259 AA AA
230
99 / 230
9.2.6 Supervision:Configuration: Synch.equipment Eml<>NML
This functionality performs the upload of all NEs and related ports for the selected EML.
CONDITIONS
PROCEDURE
a)
b)
Supervision:Configuration:Synch.equipment Eml<>NML
NOTE. The above mentioned commands can be also launched from the relevant Browser popup menus.
9.2.6.1 Rules applied by the Audit software (for SENIM only)
Rules applied by the Audit software can be summarized as follows:
a)
if CC is not equal to snCo, set an alarm in relevant TPs of CC. This alarm is:
event type: errorProcessingAlarm
probable cause: configurationMismatch
perceived severity: major
b)
if snCo exists in the MIB but does not exist in the NE, set the alarm mentioned in a ) in relevant TPs
of snCo
c)
in case of WX, if CC is equal to snCo but has a different crossconnectionid, set the alarm
mentioned in a ) in relevant TPs of snCo. If later, the operator will enter the DownloadEnabled mode
and this mismatch still occurs, WX renames the crossconnectionid in the NE according to its own
rules.
d)
If a payload mismatch is detected, an alarm in the involved higherOrderPathLayerTTP is set.
9.2.6.2 Supervision:Synchronize Alarms on Map

PURPOSE
The purpose of this procedure is to synchronize the alarms of the opened map to the MIB database.
PROCEDURE
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
ED
Select Supervision:Synchronize Alarms on Map.
01
957.130.872 H
3AL 61259 AA AA
230
100 / 230

PURPOSE
9.2.6.3 Supervision:Synchronize Map
1AA 00014 0004 (9007) A4 ALICE 04.10

PURPOSE
The purpose of this procedure is to synchronize the opened map to the MIB database.
CONDITIONS
This operation is required following database changes executed by the user.
PROCEDURE
a)
Select Supervision:Synchronize Map (See Figure 46. ). The list of the Available Networks is
displayed.
b)
Select the Network name and click on button Synchronize. The map synchronization starts and the
Network icon of the synchronizing map is placed in the New Object Holding Area. Wait...
c)
At synchronization end, drag the network icon to the center of the map window.
d)
Open the Network clicking twice on the network icon: the network window is opened. The Subnetwork
icons are displayed in the New Object Holding Area.
e)
Drag the Subnetwork icons to the center of the window.
f)
Click twice on the first Subnetwork. The Subnetwork window is opened.
g)
Drag the topological objects to the center of the window.
h)
Click twice on the ring icon. The ring window is opened with the objects still in the New Object Holding
Area.
i)
Click twice on the first NE icon. The Network Element window is opened.
j)
Drag the objects to the center of the window
k)
Repeat steps f) to k) for each object involved .
ED
01
957.130.872 H
3AL 61259 AA AA
230
101 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
102 / 230

10 SDH NETVIEW: BROWSE SUBMENU

10.1 Introduction
The Browse pulldown menu item allows to select among the following submenus (see Figure 49. ):
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 49. Browse pulldown menu
ED
Browse: Object(s)
Browse: NAPs... : Idle 2 Mb
Browse: NAPs... : Idle140 Mb
Browse: NAPs... : filtered
Browse: HO CTPs
Browse: Paths... : in Topology: 2 Mb
Browse: Paths... : in Topology: filtered
Browse: Paths... : all in Physical Connection
Browse: Paths... : active in Physical Connection
Browse: Paths... : starting (ending) from nodes
Browse: Trails... : at this sublevel
Browse: Trails... : at all sublevels
Browse: Trails... : user defined HO trails at all sublevels
Browse: Trails... : starting (ending) from nodes
Browse: Physical Connection.. : LCs
Browse: Physical Connection.. : Physical Connection structure
Browse: SDH Port payload...
Browse: Protection block
Browse: Performance Monitoring: Measures
Browse: Performance Monitoring: Monitored NEs
Browse: Performance Monitoring: TCA Profiles
Browse: Performance Monitoring: Counter Reports
Browse: Performance Monitoring : Threshold Reports
Browse: Performance Monitoring : Archive Session
Browse: Alarmed Objects
01
957.130.872 H
3AL 61259 AA AA
230
103 / 230
One or more object(s) can be selected in the map. Then enter command Browse: Object(s). This causes
the Browser to start on the selected object(s).
10.3 Browse: NAPs: Idle 2 Mb/ Idle34Mb/ Idle 45Mb/ Idle140Mb/ filtered
One or more node(s) can be selected in the map. Then enter command Browse: NAPs. either specifying
the port rate or the option filtered.
This causes the Browser to start (or popup if already started) on the selected object(s) and display the
relevant multirow window.
SCOPE
The scope of this procedure is to obtain a list of the NAPs on a Node basis.
1AA 00014 0004 (9007) A4 ALICE 04.10
SEQUENCE
a)
In the Netview map select the node of which you want to retrieve naps.
b)
Select pulldown menu Path: NAP List and further select among 2 Mb, 34 Mb, 45 Mb, 140 Mb and
filtered or click on the relative button.
1)
If you select 2 Mb, 34 Mb, 45Mb, 140 Mb, you will get the relevant list of the idle NAPs belonging
to the selected object. (See Figure 50. ). The NAP list is presented in the multicolumn mode on
a separated window.
2)
If you select the option filtered, or click on the relative button, the filter dialog box is presented
(see Figure 51. ), allowing the user to program a filtered list.
Figure 50. NAP List
ED
01
957.130.872 H
3AL 61259 AA AA
230
104 / 230

10.2 Browse: Objects
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 51. Filter dialog box
ED
01
957.130.872 H
3AL 61259 AA AA
230
105 / 230

Select in the map the Nodes and enter the command: Browse: HO CTPs.
The browser starts and the relevant view is presented.
10.5 Browse: Paths... : in Topology... : 2Mb/ 34Mb/ 45Mb /140 Mb / filtered

One topological object can be selected in the map. Then enter command Browse: Paths... : in Topology
either specifying the path rate or the option filtered.
This causes the Browser to start on the selected object(s) and to display the relevant path list (multirow
window).
SCOPE
The scope of this procedure is to obtain a path list related to the selected object, selecting either path rate
or using a standard filter.
PROCEDURE
a)
In the Netview map select the topological object on which you want to retrieve paths.
b)
Select pulldown menu Path: On Selected and further select among 2 Mb, 34 Mb, 140 Mb and filtered
or click on the relative button.
1)
If you select 2 Mb, 34 Mb, 140 Mb, you will get the relevant list of Paths
originated/terminated/crossing the selected object. The Path list is presented in the multicolumn
mode on a separated window. See chapter 14 for details.
2)
If you select the option filtered, or click on the relative button, the filter dialog box is presented,
allowing the user to program a filtered list.
10.6 Browse: Paths... : all in Phys. Connection

One Physical Connection can be selected in the map. Then enter command Browse: Paths... : all in
This causes the Browser to start on the selected Physical Connection and to display the list of the paths
making use of the selected Physical Connection.
10.7 Browse: Paths... : active in Phys. Connection

One Physical Connection can be selected in the map. Then enter command Browse: Paths... : active in
This causes the Browser to start on the selected Physical Connection and to display the list of the paths
actually active (main or spare route) on the selected Physical Connection.
10.8 Browse: Paths... : starting (ending) from nodes
1AA 00014 0004 (9007) A4 ALICE 04.10
You can select the node/nodes in the map, then issuing this command the list of the paths terminated to
these nodes will be displayed.
ED
01
957.130.872 H
3AL 61259 AA AA
230
106 / 230

10.4 HO CTPs

10.9 Browse: Trails...: at this sublevel

If you select the network and you issue this command, you will get the list of the trails interconnecting the
subnetworks belonging to the selected network.
If you select a subnetwork and you issue this command, you will get the list of the trails interconnecting
rings and nodes, belonging to the selected subnetwork.
If you select a ring and you issue this command, you will get the list of the trails interconnecting the nodes
belonging to the selected ring.
10.10 Browse: Trails...: at all sublevels

If you select the network and you issue this command, you will get a trail list constituted by:
the trails interconnecting the subnetworks belonging to the selected network
the trails interconnecting rings and nodes, belonging to the subnetworks contained in the network
the trails interconnecting the nodes belonging to the selected ring
If you select a subnetwork and you issue this command, you will get a trail list constituted by:
the trails interconnecting rings and nodes, belonging to the selected subnetwork
the trails interconnecting the nodes belonging to the rings contained in the subnetwork
If you select a ring and you issue this command, you will get a trail list constituted by:
the trails interconnecting the nodes belonging to the rings contained in the subnetwork
10.11 Browse: Trails...: user defined HO trails at all sublevels

If you select the network,or asubnetwork or a ring you will get a trail list containing all the user defined
HO trails belonging to the selected topological object.
10.12 Browse: Trails starting (ending) from nodes

You can select the node/nodes in the map, then issuing this command the list of the trails terminated to
these nodes will be displayed.
10.13 Browse: Physical Connection.. : LCs
1AA 00014 0004 (9007) A4 ALICE 04.10
Select the Physical Connection in the map. Then enter Browse: Physical Connection: LCs. This causes
the Browser to start on the selected Physical Connection and display the relevant Link Connection list.
ED
01
957.130.872 H
3AL 61259 AA AA
230
107 / 230
Select in the map the Physical Connection to display. Then enter command Browse: Physical Connection:
Payload structure.
This causes the Browser to start on the selected Physical Connection and display the Physical Connection
structure. This includes in the graphical window:
area PHYS:
ports
physical Connection
area MS
MS trail
area HO
link connection
HO trail
area LO
low order structure
protection type
No. of hops
LO link connections
Paths in HO trail
For more detailed information see also paragraph 14.2 .

The popup menu can be opened on all objects, in particular the popup menu selected on LO link
connections and on Paths in HO trail provides the relevant views. See para.14.3. and para.14.4 .
10.15 Browse: SDH Port payload

Select in the map the SDH port and enter the command: Browse: SDH Port payload.
The browser starts and the relevant view is presented. See para.14.5.
10.16 Browse: Protection Block

You can select in the map the MSPRING ring, then you issue the command Browse: Protection block. See
para. 14.7 .
10.17 Browse: Performance Monitoring: Measures

From the root submap you can select the network icon and issue the Browse: Performance Monitoring:
Measures pulldown menu item. The Measure list is displayed.
10.18 Browse: Performance Monitoring: Monitored NEs
1AA 00014 0004 (9007) A4 ALICE 04.10
Monitored NEs pulldown menu item. The Monitored NEs list is displayed.
ED
01
957.130.872 H
3AL 61259 AA AA
230
108 / 230

10.14 Browse: Physical Connection: Physical Connection structure

10.19 Browse: Performance Monitoring: TCA Profiles

TCA Profiles. The TCA Profile list is displayed.
10.20 Browse: Performance Monitoring: Counter Reports

Counter Reports pulldown menu item. The Counter Reports list is displayed.
10.21 Browse: Performance Monitoring: Threshold Reports

From the root submap you can select the network icon and issue the Browse: View Performance
Monitoring: Thresholds Reports pulldown menu item. The Thresholds Reports list is displayed.
10.22 Browse: Performance Monitoring: Archive Session

This command starts an Archive session. See description at section OPERATION, Chapter 4
Performance Monitoring.
10.23 Browse: Alarmed objects
1AA 00014 0004 (9007) A4 ALICE 04.10
Select in the map the Nodes and enter the command: Browse: Alarmed objects.
The browser starts and displays the filtered list of the following alarmed objects: nap,cap, ctp, msCtpCap,
port, ne, belonging to the selected topological object.
ED
01
957.130.872 H
3AL 61259 AA AA
230
109 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
110 / 230

11 SDH NETVIEW: TOOLS SUBMENU

11.1 Introduction
The Tools pulldown menu allows to select one of the following items:
Path: Create
Path: Constraints
Path: Add Leg
Modify Payload
Setup Trail
Upload NAP
Network Connectivity
11.2 Tools: Path: Create

Refer to Chapter Path: Create
11.3 Tools: Path: Contraints

Refer to Chapter Path: Constraints
11.4 Tools: Path: Add Leg

Refer to Chapter Path: Add Leg
11.5 Tools: Modify Payload

Refer to Chapter Payload Configuration
11.6 Tools: Setup Trail
1AA 00014 0004 (9007) A4 ALICE 04.10
Refer to Chapter Setup Trail
ED
01
957.130.872 H
3AL 61259 AA AA
230
111 / 230
11.7 Tools: Upload NAP

SCOPE
The purpose of this procedure is to launch a NAP upload for the selected ring/node.
PROCEDURE
a)
Select in the map the object(s) from which you want to upload the nap(s).
b)
Select command tools: Upload Naps. A dialog box alert that the action is correctly started
11.8 Tools: Network Connectivity
1AA 00014 0004 (9007) A4 ALICE 04.10
Refer to Chapter 21
ED
01
957.130.872 H
3AL 61259 AA AA
230
112 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10

12 SDH NETVIEW: HELP SUBMENU
The description of the 1354RM Help feature is contained in the 1354RM Getting Started Handbook.
ED
01
957.130.872 H
3AL 61259 AA AA
230
113 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
114 / 230

13 BROWSER
13.1 Introduction
The Browser is a Motif based application which provides multiple navigation views. It supports full view
of MIB data objects or tailored views. The commands available in the browser depend on users profile.
The Browser supports:
Single/multiple selection operations
Pulldown menu with generic and/or object specific commands
Popup menus with generic and/or object specific commands
Drag and drop operation for interworking between applications
Help on item (Balloon help). A textstring describing the function is presented if you leave the
mouse more than one second on the functional button/object.
Contextsensitive help. If you select the object and the pulldown menu Help on selected
object, the Worldview application starts and displays automatically the description of the
selected object class.
The Browser is based on the approach to enable navigation into all, a portion or a view of the containment
tree.
Objects are presented with:
An icon related to the class (a bitmap) that can be related to one or more attribute values.
Examples:
class NE with bitmap depending on Type
class ET with bitmap depending on ET type and stm type values
A color relevant to an attribute value (e.g. implementationStatus)
A label related to one or more attribute values
Additional labels/option buttons/texts or multicolor icon (pixmaps) displaying attribute values
An alarm icon that appears only when the object is alarmed, whose color is related to the alarm
status value.
1AA 00014 0004 (9007) A4 ALICE 04.10
Object containment is represented using:
ED
Recursive object grouping into frames
Indentation
01
957.130.872 H
3AL 61259 AA AA
230
115 / 230
The basic operations on objects are:
All related items ...
Align item(s)
Parent
Related items ...
All related items
Unselect all
Details
1AA 00014 0004 (9007) A4 ALICE 04.10
Main related items ...
Select
ED

Display
Show/Set attributes ...
Displayed info ...
Class specific actions (executed as separate processes)
01
957.130.872 H
3AL 61259 AA AA
230
116 / 230
13.2 Browser main window

After launching the Browser application, the Browser window is opened.

This window contains:
Balloon help
icon bar
window title
pulldown menu
counters area
item
area
info
help area
receive events indicator
events flag indicator
1AA 00014 0004 (9007) A4 ALICE 04.10
work area
Figure 52. Browser main window.
ED
01
957.130.872 H
3AL 61259 AA AA
230
117 / 230
window title : 1354RM: Browser
pulldown menu bar.
icon bar. Refer to paragraph 10.2.1
title : 1354 RM Viewer [ drop to view ]

You can drop here an item dragged from browser or other RM applications.
counters area. It contains three counters:
Total. It is the total number of objects actually retrieved by the Browser.
Visible. It is the total number of objects visible in the window.
Selected. It is the total number of objects selected (should be always 1)
work area. It contains the retrieved objects.
info area containing:
logo
help area providing the following information:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED

values of displayed attributes.You get this information moving the mouse to the
involved object in the work area.
function button description. You get this information moving the mouse to the
involved button in the button box.
event row containing:
receive events indicator.
events flag indicator (Create not processed, Delete and Update processed)
Balloon help are present on widgets (buttons, items, attributes, ...).
01
957.130.872 H
3AL 61259 AA AA
230
118 / 230
13.2.1 Icon bar

The first row of icon bar contains the following buttons:
Exit Browser. It corresponds to the pulldown command File: Exit.
Get object from MIB. It corresponds to the pulldown command Actions:Display:Main related items
and/or to the popup command Display:Main related items
Get parent object from MIB. It corresponds to the pulldown command Actions:Display:Parent
and/or to the popup command Display:Parent.
Show/Set item attributes. It corresponds to the pulldown command Actions:Details:Show/Set

Attributes and/or to the popup command Details:Show/Set Attributes.
Synchronize item making an attribute reget. It corresponds to the pulldown command

Actions:Display:Align item(s) and/or to the popup command Display:Align item(s).
Info about selected item. It corresponds to the pulldown command Actions:Details:Displayed info
and/or to the popup command Details:Displayed info
Report of selected item. It corresponds to the pulldown command View:Report:full on selected
Show drop area. If you click on this button a submenu is opened. It contains:
Fdn:: where you can drop/write the fdn (eventually dragged from Report).
Add the dropped/written items fdn in first position.
Close all displayed items and add the dropped/written one.
Hide the drop area.
Show additional information. It provides additional information related to actions not succesfully
terminated (eg. Resources not available to allocate path).
Used info for. It provides the help information of the logged user.
The second row of icon bar contains the following buttons:
ovw. If you click on this button a submenu is opened. It includes the following buttons:
1AA 00014 0004 (9007) A4 ALICE 04.10
go to parent menu
go to home menu
Locate selected item in OpenView
browser. It starts another browser application.
Paths tool. If you click on this button a submenu is opened. It includes the following buttons:
ED
go to parent menu
go to home menu
Create a new path
Add Constraints to a path/trail
Add leg to a path
Show the queued job
01
957.130.872 H
3AL 61259 AA AA
230
119 / 230
Alarms tool. If you click on this button a submenu is opened. It includes the following buttons:
go to parent menu
go to home menu
show the alarm in route
Report of elementary alarm correlation
Show communication alarm
Create a new Alarm profile
Correlate path/trail/physical connection to an Alarm profile
MNG. It shows the administering tools. If you click on this button a submenu is opened. It includes
the following buttons:
go to parent menu
go to home menu
start process monitor
Alcatel icon. It displays the current 1354RM patch level.
CFG. It shows the configuration tools. If you click on this button a submenu is opened. It includes the
following buttons:
go to parent menu
go to home menu
start the Payload configuration
start the trail definition
start the Connectivity application
PM. It shows the performance monitoring tools. If you click on this button a submenu is opened. It
includes the following buttons:
1AA 00014 0004 (9007) A4 ALICE 04.10
go to parent menu
go to home menu
Create a new measure
Correlate path/trail to a measure
Merge measure
Show Performance Monitoring Data
Delete Monitored Data
Archive Performance Monitoring Data
Display Performance Monitoring Archived Data
Retrieve Performance Monitoring Data
Event Log. It starts the Event Log application.
Start the Show Equipment command ( EML ) . Select first the node or the network element. Then,
if you click on this icon ( see Figure 52. on page 117, the Equipment View of the relevant NE opens.
ED
01
957.130.872 H
3AL 61259 AA AA
230
120 / 230


13.2.2 Counters area

In the Total, Visible and Selected field are shown respectively the total number of displayed items, the
number of visible items and the number of selected items.
13.2.3 Work area
Item
Label
Attribute (Working State)
Balloon help
Figure 53. Browser work area.
1AA 00014 0004 (9007) A4 ALICE 04.10
In the Browser main window work area are displayed the retrieved items that are configured to be shown
in that window (eg. Nodes in topology from the ET). Retrieved items can be also displayed in Drawing
Windows and in Multicolumn Windows (eg. All nodes from Network, Network Domain and Root Domain)
and will be detailed in the next paragraphs; in these cases a group icon that refer to the relative window
is displayed in Browser Main Window work area.
ED
01
957.130.872 H
3AL 61259 AA AA
230
121 / 230
Object filtering and scoping is fully supported throught the Display:Main related items and Display:All
related items, in particular:
Scoping is hidden in the selected navigation tree (eg. Nodes in topology from ET or Subnetwork are
performed with scope level 1 and All Nodes from Network is performed with all tree depth level)
Filtering can be performed with:
Conditions entered by the user
User defaults presaved conditions
Class related predefined conditions (e.g. customerName=xyy)
Using the popup Display:Main related items or Display:All related items, or selecting one or more items
and using the icon button Get object from MIB or the pulldown Actions:Display:Main related items or
Actions:Display:All related items a Chooser window of available navigation is shown:
Figure 54. Object filtering.
1AA 00014 0004 (9007) A4 ALICE 04.10
Clicking on the Filter ... button the Define Query For window is shown (see next paragraph)
ED
01
957.130.872 H
3AL 61259 AA AA
230
122 / 230

13.3 Object filtering and scoping

13.3.1 DEFINE QUERY FOR (the selection/filter window)
Figure 55. Define query window for Node

The DEFINE QUERY window is used to display a list of attributes of the selected object. This window has
a standard structure, described in the following:
Window label
The window label is: DEFINE QUERY FOR <object class name >
Selection parameters
The selection parameters are structured in three columns:

attributes, filtercriterion , value.
Control buttons
Three control buttons are provided: Apply, Cancel and Help
The lefthand column contains the list of all the attributes of the selected object
1AA 00014 0004 (9007) A4 ALICE 04.10
The central column (option button) specifies the filter condition. A popup menu can be opened, which
allows to select among the options.
ED
01
957.130.872 H
3AL 61259 AA AA
230
123 / 230
None.
No filtering is specified.
Start with.
This filter condition provides the instances which start with the speci
fied string in the relevant MIB data.
Match exactly.
This filter condition applies an exactly match between the field

specified and the relevant MIB data.
Contains.
This filter condition provides the instances which contain the speci
End with.
This filter condition provides the instances which ends with the speci
Doesnt contain.
This filter condition provides the instances which do not contain the
specified string in the relevant MIB data.
If the attribute is of the type enumerated, the popup menu which can be opened is the following:
None
Equal to
Not Equal to
If the attribute type is date, the popup menu is:
None
Before
Since
Exactly
If the attribute type is integer the popup menu is:
None
Greater equal than
Less equal than
Equal to
Not equal to
The righthand column contains the attribute values. The value can be entered in text field, for the types
integer, date and string. The value can be entered as option for the type enumerated.
The function of the filter is an AND of all the previously specified conditions.
1AA 00014 0004 (9007) A4 ALICE 04.10
In case the selection is handled by pointers instead of containment tree, the filter is disabled.
ED
01
957.130.872 H
3AL 61259 AA AA
230
124 / 230

If attribute is of type string the popup menu which can be opened is the following:

13.4 Show/Set Attribute

The Show attribute operation is startable from popup Details:Show/Set attributes, from the pulldown
Actions:Details:Show/Set attributes and from Show/Set attributes icon and allows to display the
ATTRIBUTE VALUES FOR window that shown the item attributes retrieved by Agents, including:
Simple attributes: text, integer, enumerated, data.
Pointers to other classes/objects.
ASN.1 set of, sequence of and combination (e.g. napList=set of sequence of (napPointer,used
Direction , siteName...)
The ATTRIBUTE VALUES FOR window is quite similar to the DEFINE QUERY window and is used to
display or change value in MIB of the selected objects attributes. This window has a standard structure,
( see Figure 56. ) described in the following:
Window label
The window label is: ATTRIBUTE VALUE FOR <class> <item label>
Parameters
The parameters are structured in three columns:

attributes name, set buttons (set and set to default) present only if the
attribute is modifiable, fields or option buttons.
Control buttons
Three control buttons are provided: Apply, Cancel and Help
set button
1AA 00014 0004 (9007) A4 ALICE 04.10
non modifiable attribute
Figure 56. Show/Set Attributes dialog box.
ED
01
957.130.872 H
3AL 61259 AA AA
230
125 / 230
13.5 Items selection in the Browser
select within a path list already displayed in the browser, all the paths where the configuration state
is allocated and the customer name matches a given value or pattern. After the selection, the
configuration action required can be issued.
The available commands and the behavior result from the following table:
Table 1. Items selection in the Browser
Browser
Main Window
Command
Select All
Not available
Browser
Multi Column Lists
Browser
Graphical Views
All the items in the current Not available

multi column list are selected
Select
All the children of the given Not available
All related items selected object are selected
Unselect All
Not available
All the selected objects All the selected objects All the selected objects
are unselected
are unselected
are unselected
Select
related A mask with the possible Not available
items ....
children classes for the selected object is presented.
From this mask, the user
can select a class and, optionally, the detailed filter
to be applied (see description for multicolumn
view)
Select ....
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Not available
A mask with the possible

classes displayed in the
view is presented.From
this mask, the user can select a class and, optionally,
the detailed filter to be applied (see description for
multicolumn view).
A mask with the attributes Not available

of class displayed in the
list is presented. The user
can define a sequence of
conditions in order to perform the needed selection.
The command Select All allows to select a maximum of 65 lines.
01
957.130.872 H
3AL 61259 AA AA
230
126 / 230

A possible use of this feature is, for example:

13.6 Generic Browser pulldown menu

The 1354RM Browser window presents in the main menu bar the following pulldown menu: File, Actions,
View, Options, Specific, Windows, ExtTools, Help.
The File menu contains the only option Exit.
The Actions menu contains the following selectable items:
Actions: Display: Main Related items... < F2 >

Actions: Display: All Related items...
Actions: Display: Align Item(s)
< F6 >
Actions: Display: Parent
< Shift + F1 >
Actions: Select: Items...

Actions: Select: All Items...
Actions: Select: Unselect all
< Alt + F1 >

< Alt + F2 >
< Alt + F3 >
Actions: Close: Item

Actions: Close: Item by Class
Actions: Close: All Related items...
< F3 >
< Shift + F3 >
< F4 >
Actions: Details: show/set attributes

Actions: Details: Displayed info...
< F5 >
< F9 >
The View menu contains the following selectable items:
View: Displayed Info...
< F8 >
View: Report: Full...

View: Report: Full on selected...
View: Report: Short...
View: Report: Short on selected...
< Shift + F5 >

< Shift + F6 >
< Shift + F7 >
< Shift + F8 >
The Options menu contains the following selectable items:
Options: Filtered presentation

Options: Not Filtered presentation
Options: Immediate operations

Options: Deferred operations
Options: Graph refresh rate
Options: Close window going to parent
Enable AS link
The Specific menu contains items which depend on the selected object.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Windows menu contains the list of opened windows (views and multicolumn lists).
Iconified windows can be deiconified; deiconified windows can be iconified.
ED
01
957.130.872 H
3AL 61259 AA AA
230
127 / 230
The ExtTools menu contains the following selectable items:

from AS
from Others

The Help menu contains the following selectable item.
Help: On Help....
Help: On 1354RM....
Help: On Browser....
Help: On This Window....
Help: About This Version....
Help: On Index
All above mentioned menus are described in the following paragraphs.

In addition, for each object class the popup menu contains object specific commands.
13.6.1 Actions: Display: Main Related items...
The purpose of this procedure is to retrieve from the MIB data base the main information related to the
selected object. The relationship between the selected object and its related items is described in the
object containment tree. In detail, this relationship can be though as a fatherchild relationship or a pointer
relationship.
This operation can be executed either from the Actions pulldown menu, that starts the get operation of
all selected objects (they MUST belong to the same class) or from the object popup menu that starts the
get operation only on that object.
This operation can also be launched by doubleclicking the object or clicking on the Get object from MIB
icon of the icon bar.
SEQUENCE
a)
Select (left click) one or more object to browse and Actions: Display: Main Related items....
The related item selection window is displayed. This window contains the list of child classes of the
selected object.
b)
Select the class to display and the search mode (Filter/No Filter). If you select No Filter the related
objects (children) of the selected object are displayed below the father icon.
If you select Filter the Define Query window is displayed (See Figure 55. ).
The box containing the available related objects is indentated with respect to the symbol of the father.
c)
You can continue displaying related items for an object selecting again Display: Main related items
popup or pulldown menu item, according to the database hierarchical tree.
NOTE
1AA 00014 0004 (9007) A4 ALICE 04.10
The output of the Display Main Related items operation can be in normal format, i.e. displayed indentated
in graphical way, or in multicolumn format or by means of dedicated views, i.e. giving a compacted list
of the browsed objects.
ED
01
957.130.872 H
3AL 61259 AA AA
230
128 / 230

13.6.2 Actions: Display: All Related items...

This command is analog to the command Actions: Display: Main Related items... (see paragraph
13.6.1)The only difference is that all related items are available to be displayed.
13.6.3 Actions: Display: Align item(s)
The purpose of this procedure is to align the data displayed on the screen to MIB data.
This operation can be executed from the object popup menu and the pulldown menu.
SEQUENCE
a)
Select (left click) one / more object/s to be aligned.
b)
Select Actions: Display: Align item(s) or by using the right mouse button, select Display: Align
item(s)
13.6.4 Actions: Display: Parent.

The purpose of this procedure is to retrieve from the MIB data base information related to objects that
contains the selected one. The relationship between the selected object and its parent is described in the
object containment tree. More in detail, this relationship can be though as a fatherchild relationship or
a pointer relationship.
This operation can also be launched by clicking on the Get parent object from MIB icon of the icon bar or
from the object popup menu.
SEQUENCE
a)
b)
Select (left click) one/more object/s to browse or popup.

Select Actions: Display: Parent.
The Parent object is displayed in the Browser window below the icon of the child object.
13.6.5 Actions: Select: Related Items....
This menu, if selected, provides a mask with the possible children classes for the selected object.
From this mask the user can select a class and, optionally, the detailed filter to be applied.
This operation can be executed also from the object popup menu.
13.6.6 Actions: Select: All related Items....
All children of the given selected object are selected.
1AA 00014 0004 (9007) A4 ALICE 04.10
13.6.7 Actions: Select: Unselect All....

All selected objects are unselected.
ED
01
957.130.872 H
3AL 61259 AA AA
230
129 / 230
13.6.8 Actions: Close: Item
SEQUENCE
a)
Select (left click) one or more object/s to close.
b)
Select Close: Item.
The selected object/s is/are removed from the screen.

13.6.9 Actions: Close: Item by Class
The purpose of this procedure is to remove from the window the specific child class of the selected object.
This operation can be executed only from the Actions pulldown menu.
SEQUENCE
a)
Select (left click) one/ more object/s whose child class has to be forgotten.
b)
Make use of the Actions pulldown menu. Select Close: Items by Class.
c)
The child selection window is displayed. One/more child class can be selected (left click).
d)
Pressing the OK button the select classes are removed from the screen.
13.6.10 Actions: Close: All related items

This command removes from the window all displayed children of the selected object.
1AA 00014 0004 (9007) A4 ALICE 04.10
SEQUENCE
a)
Select (left click) one/more object/s whose related items have to be removed.
b)
Select Action: Close: All related items.
ED
01
957.130.872 H
3AL 61259 AA AA
230
130 / 230

The purpose of this procedure is to remove the selected object and its opened children from the window.

13.6.11 Actions: Details: Show/set attributes

This allows to show attributes of an object or modify the value of the simple attributes (Modifiable at UI)
in the MIB data base.
This operation can also be executed by clicking on the Show/Set attributes icon of the icon bar or from
the object popup menu.
SEQUENCE
a)
Select (left click) the object whose attributes have to be set/shown.
b)
Select Show/Set attributes. A dialog box is presented. It contains the objects attributes.
The attribute that cannot be modified is displayed without any
If the user selects the option Set, will enter the new value in the area of the field (string, integer and
date type) or set the new enumeration value.
If the user selects the option Set to default, the attribute will be set to the default value.
c)
After entering the modifications, select Apply. The attribute will be modified.
The Show/Set dialog box also contains the Cancel button, which causes to abort the procedure and
close the window and the button Help providing the relevant Help information.
13.6.12 Actions: Details: Displayed info...

The purpose of this procedure is to display the information relative to the selected object class.
This operation can also be executed by clicking on the Details on the displayed information icon of the icon
bar or from the object popup menu (Details: Displayed info..).
SEQUENCE
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
b)
ED
Select (left click) one/more objects or right mouse...

Select View:Displayed info...
A dialog box is presented. It contains the information relative to class name, color of the icon,
displayed attributes.
01
957.130.872 H
3AL 61259 AA AA
230
131 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 57. Actions: Details: Displayed Info.
ED
01
957.130.872 H
3AL 61259 AA AA
230
132 / 230
13.6.13 View:Displayed info....
1AA 00014 0004 (9007) A4 ALICE 04.10

Same as 13.6.12
13.6.14 View:Report
The View:Report item allows to select one of the following submenus:
Report full...
Report full only selected...
Report short...
Report short only selected...
Figure 58. View:Report full
ED
01
957.130.872 H
3AL 61259 AA AA
230
133 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Report short...(See Figure 59. )
Report short only selected...
Figure 59. View:Report short
01
957.130.872 H
3AL 61259 AA AA
230
134 / 230

13.6.15 Options: Filtered presentation / Not filtered presentation

These options specify if the pulldown Display Related Items action is filtered or not when exists only one
child class.
13.6.15.1 Options:Immediate Operations
The purpose of this procedure is to preset the immediate execution of a subsequent action on a path
(allocate/deallocate/impement/deimplement).
PROCEDURE
a)
Select Options:Immediate Operations. The subsequent action will be immediately executed.
13.6.15.2 Options:Deferred Operations

The purpose of this procedure is to enable the scheduling of the subsequent actions on paths.
PROCEDURE
a)
Select Options:Deferred Actions. Select the action to schedule. A dialog box is displayed (lefthand
side of Figure 60. ).
b)
c)
d)
Click on the scrollbar. A selectable list is displayed (rigthhand side of Figure 60. )
Select the time value and click on OK. The selected value is copied into the lefthand side box.
Selecting OK the action on path will be executed at the specified time.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 60. Options:Deferred Actions
ED
01
957.130.872 H
3AL 61259 AA AA
230
135 / 230
13.6.16 Options:Graph refresh rate

The purpose of this menu is to change the rate to refresh graph (see Figure 61. )
SEQUENCE
a)
Select Options:Default graph refresh rate

A dialog box is shown (see Figure 61. )
Figure 61. Options:Default graph refresh rate
1AA 00014 0004 (9007) A4 ALICE 04.10
You can change the refresh rate for the new counter graph you are going to start (New value). Each
time a new graph is started this value is read, so if you have a counter with some parameter that
change their value very often, you can set the refresh rate to few seconds and then start the graph;
after this if there is a slowly changing parameter counter you can set a new value (eg. 180 sec)
without involve the previously started graph. Remember that this value is run time only. It is resetted
on default value every time you restart the browser.
ED
01
957.130.872 H
3AL 61259 AA AA
230
136 / 230
13.6.17 Options:Close window going to parent

The purpose of this option is enable/disable the selflocking of opened window going to its parent.
13.6.18 Options: Enable AS link
The purpose of this option is to break off the talking between browser and AS application.
13.6.19 Specific
It contains menus which depends on the selected item (typically specific actions).
13.6.20 Windows
It contains the list of opened windows (views and multi column lists). Iconified windows can be deiconified,
deiconified windows can be iconified.
13.6.21 ExtTools
It allows to open views containing items built after AS navigation and navigation from external tools
(eg: setup trail, path creation). The menu has following submenus:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
from AS. It opens a browser instance containing objects navigated from the Alarm Surveillance
application.
from Others. It opens a browser instance containing objects navigated from the Netview application.
01
957.130.872 H
3AL 61259 AA AA
230
137 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
138 / 230

14 BROWSER: DRAWING WINDOWS

The Browser application includes the possibility to display several drawing windows, which are helpful in
managing the controlled network.
14.1 Introduction
Drawing windows support:
Icon Bar generic commands
Dynamic Icon Bar depending on selected class
Popup menus with generic and/or object specific commands
Help on item (Balloon help). A textstring describing the function is presented if you leave the
mouse more than one second on the functional button/object.
selected object class.
1AA 00014 0004 (9007) A4 ALICE 04.10
Drawing windows have the following look (see Figure 62. )
ED
window title : 1354RM: Browser
pulldown menu bar. Refer to paragraph 13.6 .
Icon bar
title : eg. Physical connection structure
work area: It contains the retrieved objects.
info area (Refer to paragraph 13.2 )
01
957.130.872 H
3AL 61259 AA AA
230
139 / 230
14.1.1 Icon bar
Close this window. It forget the window and all its opened ones. This operation can also be executed
from the pulldown menu (File:Close).
Popdown this window. It hides the window. It can be redisplay without any reget. This operation
can also be executed from the pulldown menu (File:Popdown).
Go to the parent window. It goes to window from which this one has been opened. The current
drawing is hidden or not, depending the status of Options:Close window going to parent on browser
main window (see paragraph 13.6.17)
Get object from MIB. It navigates the selected object(s) on browser main window. The children
chooser is automatically proposed (Main related items). This operation can also be executed by
double click on object or from the object popup menu (Display:Main related items)
Show/set attributes. This allows to show attributes of an object or modify the value of the simple
attributes (Modifiable at UI) in the MIB data base. This operation can also be executed from the object
popup menu (Details:show/Set attributes) or from pulldown menu (Actions:Details:show/Set
attributes)
Align items (s). It alignes the data displayed on the screen to MIB data. Almost one object must be
selected. This operation can also be executed from the object popup menu (Display:Align items(s))
or from pulldown menu (Actions:Display:Align item(s))
Refresh this window. It deletes all items and regets all data. Note that all children
views/multicolumns lists are closed.
Used info for. It provides the help information of the logged user.
The second row depends on the specific view. It typically allows to open external application (eg. Setup
trail, Payload configuration, Path/Trail constraints) or views to create particularly instances or to correlate
objects to each others).
The third row depends on selected class. It dynamically shows icons to open view/multicolumn list
associated to selected object.
14.1.2 Work area
1AA 00014 0004 (9007) A4 ALICE 04.10
In the Drawing window, the work area displays the retrieved items typically located on graphic background
to show the relation to each other. Inside the work area are often displayed particularly items (named
group) from which other view/multicolumn lists can be opened).
ED
01
957.130.872 H
3AL 61259 AA AA
230
140 / 230

The Icon bar area is subdivided in three rows. The first one contains the following buttons:
14.2 Payload configuration of a Physical Connection
1AA 00014 0004 (9007) A4 ALICE 04.10

To display it, follow this procedure:

a)
Select in the Browser window the Physical connection to display
b)
Open the popup menu and select item Display: All Related Items
c)
Select option Physical Connection Structure.
As an alternative you may select the physical connection in the map, open the popup menu (right button)
and then select the drawing window icon.
The view can be opened also from all views/multicolumn lists containing involved object.
As can be seen in Figure 63. , the following object are displayed:
the physical connection. Next to object is located the group icon to open view Paths in physical
connection.
the two connected ports. Next to objects is located the group icon to open view Port structure.
the MSTrail
the n (1,4,16) HO link Connections
the HO Trails eventually present on each displayed HOLC (displayed info: icon + payload structure
+ Number of performed hops at HO)
the HO paths eventually present on each displayed HOLC
for each HOTrail, next to objects are present the group icon to open Client link connection (view),
the Path in trail (view) and the Routing display.
ED
01
957.130.872 H
3AL 61259 AA AA
230
141 / 230
group icons
icon bar
window title
title
pulldown menu
info
area
help area
receive events indicator
work area
Figure 63. Physical connection structure
1AA 00014 0004 (9007) A4 ALICE 04.10
From this view you can obtain the following subviews:
Client link connection (view) (see paragraph 14.3 )
Path in trail (view) (see paragraph 14.4 )
Port structure (see paragraph 14.5 )
Routing display (see paragraph 14.6 )
MS trail structure (see Figure 63. )
ED
01
957.130.872 H
3AL 61259 AA AA
230
142 / 230

14.3 Client link connection (view)
Figure 64. Client link connection (view)

All LO Link connection are placed depending to their payload.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
The LO link connections could have the following color:

green, if the lc is used in a path
white, if the lc is idle
01
957.130.872 H
3AL 61259 AA AA
230
143 / 230

14.4 Path in trail (view)
Figure 65. Paths in trail (view)
1AA 00014 0004 (9007) A4 ALICE 04.10
All paths (if any) are located depending on payload position of used link connection. Also trails ends are
displayed.
ED
01
957.130.872 H
3AL 61259 AA AA
230
144 / 230
14.5 Port structure

The view (see Figure 66. ) provides a description of the payload structure of a given SDH port.
The displayed objects are :
SDH port
MSTP (unprotected)
HOCTPs
HOTTPs (if any)
HOTrails using the HOCTPs.
If an HOtrail is not terminated on the NE (but is terminated in another equipment), the related HOTTP
is not displayed.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 66. Port structure
ED
01
957.130.872 H
3AL 61259 AA AA
230
145 / 230
The view provides a description of route of trail. In this case only the main route is shown (the trail is not
protected).
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 67. Trail Routing display
ED
01
957.130.872 H
3AL 61259 AA AA
230
146 / 230

14.6 Trail Routing display
14.7 2F MSSPRING protection block view

To display this view, perform the following steps:

a)
Select in the Browser window the relevant MsSpring
b)
Open the popup menu and select item Display: All related Items
c)
Select option MS Protection blocks
The view opens (see Figure 68. ) and displays:
the MSSPRING
the protection blocks of each Node of the Ring
The icon used for the Protection Block is modified according to the switch status: idle, passthrough,
bridge east/West... . The blue capacity (8 Au4s) represents the protected flow, the red capacity (8
AU4s) represents the protection flow (normally not used); when a fault is detected the protected flow is
crossconnected to the protecting flow at MS level.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 68. MSSPRING Protection block
ED
01
957.130.872 H
3AL 61259 AA AA
230
147 / 230

Figure 69. Protection block popup menu
1AA 00014 0004 (9007) A4 ALICE 04.10
The Protection block popup menu is shown in Figure 69. In particular, the commands under Manage
Switch are:
Synchronize. This command only allows to align the displayed information (got with Show/Set
attributes ) to the MIB data base.
Release. This command cancel the effect of a previously issued command of lockout/forced/manual
Lockout west/east. This command inhibits the automatic switch which would automatically occurr in
the relevant ring section in case of fault.
forced west. This command forces the selected node to execute a bridge & switch east operation.
forced east. This command forces the selected node to execute a bridge & switch west operation.
manual west. This command causes the selected node to execute a bridge & switch east operation,
but an equipment automatic switch can override this operation.
manual east. This command causes the selected node to execute a bridge & switch west operation,
but an equipment automatic switch can override this operation.
Change. This command allows to change the Wait to Restore Time.
From the view related to all protection block, select a node and click on icon button in icon bar area (third
row).
ED
01
957.130.872 H
3AL 61259 AA AA
230
148 / 230

Figure 70. shows an example of single MSSPRING protection block view related to first node. It
represents the MS protection block of a single Node belonging to a MSSpring.
The view is modified according to the state of the protection (idle, passthrough, bridge).
In the view the displayed entities are:
Physical ports
Physical Connections
MSTPs
MSTrails
Protected MSTPs
Protected MSTrails
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 70. All protection block in MSSPRING
ED
01
957.130.872 H
3AL 61259 AA AA
230
149 / 230
14.8 4F NPE protection block view
a)
Select in the Browser window the relevant NPE Ring
b)
c)
Select option Protection blocks in a 4F NPE

The view opens (see Figure 68. ) and displays:
the NPE MSSPRING
the protection blocks of each Node of the Ring
Protection blocks
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 71. 4F Protection blocks.
ED
01
957.130.872 H
3AL 61259 AA AA
230
150 / 230

14.9 Path/Trail Routing view

This view displays the complete path route including the main resources dedicated to the selected path.
Examples of Path Routing views are shown in Figure 73.
From the Path Routing view you can display the route report of the path by entering the command View:
Report: Route full. An example of report is shown in Figure 75.
The Path Routing view wholly represents the connectivity objects belonging to a defined path.
The view (see Figure 73. ) is subdivided into vertical columns (named Main, Spare, Service), each of
which represents a whole route.
Two cases can be distinguished:
in case of an unprotected path the Main route is only available;
if the path is of the SNCP protected type, the Main route and the Spare one are available;
if the path is of the D&C SNCP protected type, all the route graphical representations are present:
Main
Spare (more than one spare route can be present)
different service routes
The number of service and spare connections depends on how the path has been constructed.
Moreover if the path is broadcast, the different legs are separately represented.
The main and spare routes are represented for each leg if the path is of the broadcast and protected type.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
In general the description of the path routing view applies also to the trail routing view
01
957.130.872 H
3AL 61259 AA AA
230
151 / 230
14.9.1 Main Route
on the upper lefthand side the connection in topology icon at network level
From the first row on are listed the connections in topology at subnetwork level and eventually the
first connection in topology at level of Elementary Topology (ET).
Note that for each connection in topology, a continuous vertical line permits to identify the end points.
If one connection in topology is inside one route only, the vertical line directly connects the TPs (TTPs
or CTPs) involved.
On the righthand side of the different connections in topology the first end point (NAP) is depicted, hence
in the column are displayed the CTPs and the link connections connecting the CTPs belonging to different
nodes.
The link connection icon contains the label describing the relevant payload position.
The representation of the Switch connections in topology ( either Switch or Bridge & Switch ) contains
an icon (Resource Type) indicating the actual switch status. It can be:
M
S
Main
Spare
The switch is set at Main

The switch is set at Spare
It is used only for a D&C type switch, i.e. for the service type connections.
It indicates that the switch is set at Service.
The connection in topology of the Switch, B&S, or Service type may also contain the Operation Mode
information (bidirectional arrow) which can be Revertive or not Revertive.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
The Path Routing View permits to display the actual route of the path. For this purpose the
switch Resource Type indications should be analyzed. In the following Figure 72. two examples
are given:
01
957.130.872 H
3AL 61259 AA AA
230
152 / 230

The Main route graphical representation comprises (in the area relevant to the first column):
1AA 00014 0004 (9007) A4 ALICE 04.10

MAIN
ED
01
957.130.872 H
SPARE
M
M
MAIN
M
M
SPARE
Figure 72. Actual route
3AL 61259 AA AA
230
153 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
link conn. routing symbol
Figure 73. Path Routing ( BidirectionalProtected)
ED
01
957.130.872 H
3AL 61259 AA AA
230
154 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
Naps view
Figure 74. Path Routing example
ED
01
957.130.872 H
3AL 61259 AA AA
230
155 / 230


Figure 75. Route report example

Clicking on the group icon Routing display located on the view next to the link connection, it is possible
to display the objects relevant to the Link Connection at higher order (see Figure 76. on page 157).
1AA 00014 0004 (9007) A4 ALICE 04.10
Clicking on Nap view button inside the icon bar (see Figure 74. on page 155) it is possible to open the
view to display all path legs (see Figure 77. on page 158).
ED
01
957.130.872 H
3AL 61259 AA AA
230
156 / 230
14.10 Link Connection routing View
1AA 00014 0004 (9007) A4 ALICE 04.10


a)
b)
c)
Select in the Browser window the relevant link connection

Select option Routing display
Figure 76. Link Connection Routing view
ED
01
957.130.872 H
3AL 61259 AA AA
230
157 / 230
14.11 Naps View
a)
b)
c)


Select in the Browser window the relevant path
Select option Naps view
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 77. Naps view of a bidirectional path
ED
01
957.130.872 H
3AL 61259 AA AA
230
158 / 230
14.12 Node view


a)
b)
Select in the Browser window the relevant node

Open the popup menu and select item Display: Main related Items
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 78. Node view
ED
01
957.130.872 H
3AL 61259 AA AA
230
159 / 230
eml domain main browser displayed info
NE main browser displayed info
Elementary Topology main browser displayed info
node main browser displayed info
The lefthand side of the window contains a box housing the following group icons (from top to bottom):
Low Order Ctp
(multicolumn list)
HO Trail starting(ending) from (in) node
(multicolumn list)
Paylodable HOTTP
(multicolumn list)
High Order CTPs
(multicolumn list)
MS TPs
(multicolumn list)
SDH ports
(multicolumn list)
The node is represented by a triangle containing the following group icons:
Alarmed Objects
(multicolumn list)
Path in topology
(multicolumn list)
Paths starting(ending) from (in) node
(multicolumn list)
The bottom area of window contains:
PDH ports
(multicolumn list)
Naps
(multicolumn list)
The allowed operations in this window are:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
The relevant popup menu can be opened on all icons, in particular the relevant lists can be retrieved
by means of the popup menu.
01
957.130.872 H
3AL 61259 AA AA
230
160 / 230

This view contains in the upper area:
14.13 Performance Monitoring Views

Two views are available to display performance monitoring objects:
PM transport view
PM tp view
14.13.1 PM Transport view display

a)
From the measure list, otained from Browser quality domain, select the measure and issue the menu
Actions: Display: All Related Items: PM Transports
b)
From the PM transport list select the transport and click on functional button PM transport view. The
view is displayed. See Figure 79. herebelow.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 79. PM transport view
ED
01
957.130.872 H
3AL 61259 AA AA
230
161 / 230
Measure icon
PM Transport and Transport icons
PM TPs, TPs and PMNEs icons
On each icon the relevant popup menu can be opened.

14.13.2 PM TP view display
a)
From the measure list, otained from Browser quality domain, select the measure and issue the menu
Actions: Display: All Related Items: PM TPs
b)
From the PM transport list select the TP and click on functional button PM TP view. The view is
displayed. See Figure 80. herebelow.
This view contains:
Measure icon
PM Transport and Transport icons
PM TPs, TPs and PMNEs icons
TCA required and active conditions for the PMTP.
1AA 00014 0004 (9007) A4 ALICE 04.10
On each icon the relevant popup menu can be opened.
ED
01
957.130.872 H
3AL 61259 AA AA
230
162 / 230

This view contains:
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 80. PM TP view.
ED
01
957.130.872 H
3AL 61259 AA AA
230
163 / 230

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
164 / 230

15 BROWSER MULTICOLUMN WINDOWS

The Browser application includes the possibility to display several multicolumn lists, which can be iconified
to the main Browser window.
15.1 Introduction
Multicolumn lists windows support:
Icon Bar generic commands
Dynamic Icon Bar depending on selected class
Help on icons (Balloon help). A textstring describing the function is presented if you leave the
mouse more than one second on the functional button
selected object class
Statistical counters related to displayed attributes
Counters graphs which displays the changes of some attributes value
1AA 00014 0004 (9007) A4 ALICE 04.10
Multicolumn lists windows have the following look (see Figure 81. on page 168 )
ED
window title : it is composed by parent class and name of list
pulldown menu bar
Icon bar
Title area
Counters area
work area: It contains the retrieved objects.
info area (Refer to paragraph 13.2 ).
01
957.130.872 H
3AL 61259 AA AA
230
165 / 230
15.1.1 Pulldown menu

The following pulldown menu item is available:

File
Actions
View
Options
Windows
Help
The menu File allows to further select among:
Save all as. This command saves the lists content on specified file
Save selected as. This command saves the selected items on specified file
Print all. This command print all lists content
Popdown. This command hides the multicolumn list window
Close. This command closes the multicolumn list window. The group icon displayed on Browser
main disappears, the one displayed on drawing window change its colour.
The menu Actions allows to further select among:
a menu common to all lists: (path list, nap list...):
Display
Select
Details
Align item(s)
Align view
Remove from RM
a menu of Actions specific to the object class being retrieved.
1AA 00014 0004 (9007) A4 ALICE 04.10
The menu View allows to further select among:
ED
Columns.This option allows to perform a column reordering. If you select this option, a column
reordering window is presented, containing the fields which allow to move the columns, perform
text string justification and change the column width. After executing the changes you can select
Apply, to apply the changes to the list, OK to apply the changes while closing the column
reordering window or Cancel, to close the window without any change.
Sorting. This option allows to perform a list sorting. If you select this option, the Sorting window
is displayed, containing the fields Priority and Condition.The priority field allows to assign a
sorting priority among the object attributes. The field Condition allows to assign an increasing
or decreasing sorting condition. After executing the changes you can select Apply, to apply the
changes to the list, OK to apply the changes while closing the sorting window or Cancel, to close
the window without any change.
Report. For Path/Trail is available the Report: Route and the command file generator used to
save the list of path/trail that can be reused to rebuild the circuit.
01
957.130.872 H
3AL 61259 AA AA
230
166 / 230
15.1.2 Icon bar

The Icon bar area is subdivided in three rows. The first one contains the following buttons:
Close this window. see description of menu File:Close in paragraph 15.1.1
Popdown this window. see description of menu File:Popdown in paragraph 15.1.3
Go to the parent window. It goes to window from which this one has been opened. The current
multicolumn lists window is hidden or not, depending the status of Options:Close window going to
parent on browser main window (see paragraph 13.6.17)
Save the report of these items to file. A dialog box to specify files name is shown. The file contains
the mirror of displayed rows.This operation can also be executed by pulldown menu (File:Save all
as)
Print the report of these items. Sends the print of displayed items.This operation can also be
executed by pulldown menu (File:Print all)
Displayed related items. It navigates the selected object(s) on browser main window. The children
chooser is automatically proposed (Main related items). This operation can also be executed from
pulldown menu (Actions:Display:Main related items)
Show/set attributes. This allows to show attributes of an object or modify the value of the simple
attributes (Modifiable at UI) in the MIB data base. This operation can also be executed from the
pulldownmenu (Actions:Details:show/Set attributes)
Show/set filtering criteria. This allows to reget the multicolumn list with different filtering criteria.
Align items (s). It alignes the data displayed on the screen to MIB data. Almost one object must be
selected. This operation can also be executed from the pulldown menu (Actions:Align item(s))
Refresh this window. It deletes all items and regets all data. Note that all children
views/multicolumns lists are closed. This operation can also be executed from the pulldown menu
(Actions:Align view)
Ordering items. see description of View:Columns menu in paragraph 15.1.1
Sorting items. see description of View:Sorting menu in paragraph 15.1.1
Hide/Show counters. It hides/shows the counters displayed in counters area.
The second row depends on the specific multicolumn list. It typically allows to open external application
(eg. Setup trail, Payload configuration, Path/Trail constraints) or views to create particularly instances or
to correlate objects to each others).
1AA 00014 0004 (9007) A4 ALICE 04.10
The third row depends on selected class. It dynamically shows icons to open view/multicolumn list
associated to selected object.
ED
01
957.130.872 H
3AL 61259 AA AA
230
167 / 230
It contains icons related to parent class and the displayed class (with their names), the title of list, the total
number of displayed items and the number of selected ones.
15.1.5 Counters area
It contains counters related to most significant attributes with their values. To change displayed attributes
please open Ordering items window.
15.1.6 Work area
In the multicolumn list window, the work area displays the retrieved items in according to selected order
and sorting criteria, and to specified filter criteria (if any).
icon bar area
window title
pulldown menu
title
total items
Hide/Show counters
Sorting items
Ordering items
counters area
help area
work area
graph icon
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 81. Example of Multicolumn window (Path In Topology list)

The associated group icon is displayed under the parent object in the Browser Main window or inside the
drawing windows. On group icon a popupmenu allows to iconify/deiconify/close the associated list. When
lists has been opened from other list, the group icon is not displayed but the related item in Windows menu
is present to iconify/deiconify list.
On the selected object it is also possible to start all the objects specific actions (e.g. for Path:
Allocate/Implement, Protect/ Unprotect, Delete, ect...)
ED
01
957.130.872 H
3AL 61259 AA AA
230
168 / 230

15.1.4 Title area
15.1.7 Counters and graphs on Browser MultiColumn Lists

A dedicated button is available (see Figure 81. on page 168 ).

Clicking on Hide/Show counters, defined counters are displayed. For each displayed attribute a set of
counters is presented, preceeded by the graph icon. Each counter is described by its balloon text (it is
enough to leave 1sec. the mouse pointer on the counter to display it).
Clicking on the graph icon, the corresponding graphical window starts and displays a real time graph (see
Figure 82. on page 170 ) of the above mentioned counters. You can select the menu item View: Statistics
in order to display the corresponding report (see Figure 83. on page 170 )
You can save the counter contents by using the option Save as...
In addition you can scroll the values by simply clicking on the graph lefthand side (backwards) or on the
graph righthand side (forwards).
To get the detailed data of a certain instant you must first select View: Statistics. The relevant window
opens (see Figure 83. on page 170 ). Press and hold the left mouse button and move the mouse to the
instant to show; the corresponding data are displayed in the Statistical Information dialog box.
To customize the counter refresh time, you can select the menu Options: Graph Refresh Rate in the
Browser window. See para 13.6.16 for details.
1AA 00014 0004 (9007) A4 ALICE 04.10
To select the attributes to display you can use the command Order Columns from the Toolbar of the Multiple
row view.
ED
01
957.130.872 H
3AL 61259 AA AA
230
169 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
refresh time
Figure 82. Graphical window
Figure 83. Statistical Information
ED
01
957.130.872 H
3AL 61259 AA AA
230
170 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10

15.1.7.1 Example of usage

a)
Inside list select the Counter and Graphs icon; the counters are displayed in the multiple row
Browser window.
b)
In the Browser main window select Options: Graph Refresh Rate. You can enter a large value, e.g.
to supervise the Configuration State. The max. value is 999 secs.
c)
Now select the Config State graph icon: the graphical window starts with the new (large) value.
d)
In the Browser window select Options: Graph Refresh Rate. Now you can enter a small value, e.g.
to supervise the Alarm State.
e)
Now select the Config State graph icon: the graphical window starts with the new (small) value and
the previous one is being displayed with the greater value.
NOTE: A number of graphs simultaneously displayed is definable during installation phase.
ED
01
957.130.872 H
3AL 61259 AA AA
230
171 / 230
15.1.8 Multicolumn list window configuration

15.1.8.1 Ordering items

Open the relevant view following procedure described in paragraph 15.1.1 or paragraph 15.1.2
Figure 84. Ordering items

The view contains in the upper area an option button that allows to read/save user configuration file (active
after Apply button pressing)
User defaults. Reads saved user configuration file

Save user default. Saves the user configuration file
User default from. Reads the specified user configuration file
Save user default as. Saves the specified user configuration file
The button System default read the system configuration file.

The scale Fixed columns allows to set the number of fixed columns on multicolumn (to have partial
horizontal scrolling)
1AA 00014 0004 (9007) A4 ALICE 04.10
The Multicolumn counters and Browser counters buttons allow to display/hide specified counters on
multicolumn or browser
For each attibute of displayed class, it is possible to define the position (to hide attribute choose Ignore),
the justify and the displayed size of name (width).
To change the list, press OK button (the interface will be closed) or Apply button, to abort press Cancel
ED
01
957.130.872 H
3AL 61259 AA AA
230
172 / 230
15.1.8.2 Sorting items

Open the relevant view following procedure described in paragraph 15.1.1 or paragraph 15.1.2.
Figure 85. Sorting items

The upper area has already been described in paragraph 15.1.8.1.
For each attibute of displayed class, it is possible to define the priority used in sort (Ignore value doesnt
take in account the attribute) and the Condition (Ascending or Descending)
1AA 00014 0004 (9007) A4 ALICE 04.10
To change the list, press OK button (the interface will be closed) or Apply button, to abort press Cancel
ED
01
957.130.872 H
3AL 61259 AA AA
230
173 / 230
All lists have the same look already described. Main differences among list are the dynamic Action menu
(depending on retrieved class) and the specific toolbar (second row inside the icon bar area).
1AA 00014 0004 (9007) A4 ALICE 04.10
Possible getting multicolumn windows are following lists:
All nodes
available from Root Domain (for MultiRM), Network Domain, Network, Subnetwork
Trails at all sublevels

available from Network, Subnetwork, ET
Used defined HOTRAIL at all sublevels

available from Network, Subnetwork, ET
All physical connection in network
Ports
available from ne
SDH Ports
available from ne
PDH Ports
available from ne
Payloadable HOTTP
available from node
CTPs
available from node
High Order CTPs

available from node
Low Order CTPs

available from node
Client Link Connection

available from trail
Measures
available from pm domain
Monitored NEs
TCA profiles
Counter reports
Threshold reports
ED
01
957.130.872 H
3AL 61259 AA AA
230
174 / 230

15.2 Available Lists
1AA 00014 0004 (9007) A4 ALICE 04.10

Archive session
PM Transports
available from measure
Paths in Topology
available from root domain, network domain, network, subnetwork, et, node
Alarmed objects
available from network, subnetwork, et, node
Paths in Topology (with Source/Sink)

available from network, subnetwork, et, node
Paths starting(ending) from (in) node
HO Trail starting(ending) from (in) node
Ports in node
Paths starting(ending) from (in) node (with Source/Sink)
Naps (with Path label)

available from node
monitoring Measures
available from path, trail
Alarms in route
available from path, trail
LCs in routing link

available from routing link.
Paths in physical connection
HO Trail
available from physical connection
Link Connection in physical connection
Active paths in physical connection
Paths in physical connection (with Source/Sink)
Active paths in physical connection (with Source/Sink)
Path in Trail
Path at the same layer

available from link connection
Path at the same layer (with Source/Sink)

available from link connection
ED
01
957.130.872 H
3AL 61259 AA AA
230
175 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
Counter reports
available from measure
Related NE
available from pm NE
Restoration rule
available from restoration Domain
Asap correlated objects

available from restoration Domain
Eml domain
available from network Domain
Related NE
available from Eml Domain
NMLEML misaligned objects

available from Network, Subnetwork, ET, Node.
ED
01

957.130.872 H
3AL 61259 AA AA
230
176 / 230

16 BROWSER: LOCATE ITEMS IN SDH NETVIEW

16.1 Path route on SDH netview
The scope of this procedure is to disply the path/trail route in the Netview maps. The Highlite button is
present in the Path list/ Trail list and in other drawing windows containing the object to show( Naps view,
Routing view, Paths in Trail, Physical connection... und so weiter). The sequence listed herebelow refers
to the locate of a path from the path list.
Notice that the view is not automatically refreshed after a modification of the protection (Add/Remove
protection) ; in this case the sequence of operations must be executed again.
SEQUENCE
a)
From the path list select the path to display and click on Highlight button.
Highlighte
button
Figure 86. Highlighte button.
1AA 00014 0004 (9007) A4 ALICE 04.10
1)
ED
If the transport is not protected the dialog box of Figure 87. is presented. The following options
are available:
01
Main to display the main route ( square flag )
Show Payload on Physical Connection ( AU4#, TUG3#,TUG2#,TU12#)
Show end points ( small blue window icon)
a)
Select the options (multiple selections are allowed) and click on Apply button. The path
is highlighted in the netview maps. See an example in Figure 88.
957.130.872 H
3AL 61259 AA AA
230
177 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 87. Selection box.
Figure 88. Locate display ( unprotected path ).
ED
01
957.130.872 H
3AL 61259 AA AA
230
178 / 230
2)
If the transport is protected the dialog box of Figure 89. is presented. The following options are
available:

Main to display the main route ( square flag )

Spare to display the spare route ( triangular flag )
Service to display the service spare route, for D & C paths only ( triangular flag )
Show Payload on Physical Connection ( AU4#, TUG3#,TUG2#,TU12#)
Show end points ( small blue window icon)
Figure 89. Selection dialog box.
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
Select the options (multiple selections are allowed) and click on Apply button. The path
is highlighted in the netview maps. See an example in Figure 90.
Figure 90. Locate display ( protected path )
ED
01
957.130.872 H
3AL 61259 AA AA
230
179 / 230
It is possible to locate toplogical objects from browser to Netview. In the following an example of locating
a node is given.
a)
From the Node list ( see Figure 91. ) select the node and click on Navigation button. The Node icon
is displayed in the Browser main window. ( already selected ).
Navigation button
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 91. Node list.
ED
01
957.130.872 H
3AL 61259 AA AA
230
180 / 230

16.2 Locate topological objects on Netview

b)
With the node already selected click on button Highlight ( see Figure 92. ). The node is highlighted
in the Netview submaps as in Figure 93.
Highlight
button
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 92. Highlight button in Browser main.
Figure 93. Highlighted node in Netview.
ED
01
957.130.872 H
3AL 61259 AA AA
230
181 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
182 / 230

17 PAYLOAD CONFIGURATION
17.1 Introduction to Payload Configuration
The Payload Configuration procedures include:
Configuring the payload
Payload Configuration monitoring
Payload Configuration supervision
AU4 Concatenation. See next document.
17.1.1 Configuring the payload
PURPOSE
The Payload Configuration is the activity executed to define the payload structure at the corresponding
layer.
CONDITIONS
The Payload Configuration can be executed after Network Implementation.
The Payload Configuration can be executed on the following objects:
Rings
Physical Connections
High Order Link Connections
High Order Trails
After Network implementation, the payload configuration at HO of all the rings and physical connections
automatically starts, i.e. the system creates all HOTPs and the HOLCs.
PROCEDURE (FROM NETVIEW)
a)
Select an ET or a physical connection.
b)
Select menu item Tools: Modify Payload. The payload configuration window is open, with the icon
of the selected object (see Figure 94. ). The type of connection appears in the field STM type (STM1
/ STM4 / STM16).
The Modify Payload dialog box contains 3 fields named VC12, VC3 and VC4 which display the current
amounts of virtual containers. (This value is the actual configuration of the dropped object.). A button is
associated to each box.
1AA 00014 0004 (9007) A4 ALICE 04.10
c)
Select the choice button associated to the VC(s) to configure.
A new dialog box (Dictionary) is displayed (see Figure 95. ) containing a list of the possible choices for
the selected VC.
ED
01
957.130.872 H
3AL 61259 AA AA
230
183 / 230
For a given STMN, where N=1,4,16 is applied the following formula:
d)
Moving the scroll bar of the dialog box Dictionary, a complete list of the possible choices is displayed.
Select the value, and click OK. The value entered is copied in the relevant field of the Modify Payload
dialog box.
This step must be executed as many times as the payload has to be configured.
e)
Click on SETUP. The payload configuration request is sent. Checks are executed (presence of paths,
configuration state implemented of the object to configure, no other actions in progress). If checks
are successful, the Working State of the involved objects changes to Configuring.
If checks are not successful, a dialog box is presented with the relevant error message. Verify with
the Browser the state conditions of the object to configure.
For successfull payload configuration the final Working states of the involved objects is Normal, otherwise
go to Fail to Configure.
f)
Verify with the Browser the entered payload configuration.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 94. Payload Configuration window
ED
01
957.130.872 H
3AL 61259 AA AA
230
184 / 230

no. of VC4 x 63 + no. of VC3 x 21 + no. of VC12 = 63 x N

Figure 95. Payload Configuration dictionaries

NOTE 1
This procedure can be executed in the Browser window; the sequence is analog with the exception that
the operator has to drag the object to configure and drop it into the empty area of the Payload Configuration
window.
NOTE 2
This procedure can be executed also on HOLCs and HOtrails; in this case it is possible to select the
structure of each TUG3.
NOTE 3
The configuration of a physConn,/ HOLC / HOTrail within a Ring can be done only if the attribute
globalCfg of the Ring is set to False.
17.1.1.1 Example of a STM1 fiber Low Order configuration
a)
HOCTPs and HOLCs are created following topology implementation.
b)
The HOCAPs are created in correspondance to the HOCTPs. The HOCAP is a trail termination point
1AA 00014 0004 (9007) A4 ALICE 04.10
which is in a client relationship to the HOCTP.

c)
The HOTRAIL is created between HOCAPs.
d)
The LOCTPs and the connected LCs are created.
ED
01
957.130.872 H
3AL 61259 AA AA
230
185 / 230
When the payload configuration is in progress, the operator can supervise the operations performed by
the process. It mainly means:
a)
Verify in the Browser that the working state of the object (e.g. a ring) changes to Configuring.
b)
If the object to configure is a ring, the working state of all the contained physical connections must
be configuring. To do this enter command: Display:Related items:Physical Connections, starting
from a ring.
c)
If the operator wants to supervise the other objects involved in payload configuration, he can issue
a Display:All Related items command on mstrails, Client Link Connections, HOtrails, Low Order Link
Connections, etc.
At the end of the configuration process the working state of the configured objects must return to normal;
otherwise the working state becomes Fail to Configure.
NOTE
1AA 00014 0004 (9007) A4 ALICE 04.10
To execute a Payload Configuration on a connection inside a ring, it is required to change the

globalConfiguration attribute of the ring to which belongs the connection from true to false.( Show/Set
Attributes dialog box).
ED
01
957.130.872 H
3AL 61259 AA AA
230
186 / 230

17.1.2 Payload Configuration monitoring
17.1.3 Payload Configuration supervision

When the payload configuration is successfully completed, the user can supervise it in the following ways:
a)
From the map select the Physical Connection and use the popup menu Payload Configuration. The
relevant drawing window is opened; the Payload Configuration is represented graphically.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 96. Physical connection structure

b)
From the browser display the ring or the physical connection: both objects have dedicated fields
displaying the actual configuration of the Physical Connection. You can also use the Display: Related
items: Physical Connection Structure option to display the relevant drawing window.
c)
From the browser or from the Physical Connection drawing window you can open the graphical
window on the SDH Port, which displays the payload configuration supported by the port.
ED
01
957.130.872 H
3AL 61259 AA AA
230
187 / 230
17.2 AU4 Concatenation
17.2.1 AU4 Concatenation SETUP

a)
From the browser select the physical connection ( see Figure 97. ) and issue Display: Related Items:
the MS trail to configure and click on Payload Configuration button. See Figure 98. The Payload
Configuration window is presented. See Figure 99.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 97. MS trail selection.
ED
01
957.130.872 H
3AL 61259 AA AA
230
188 / 230

The AU4 Concatenation is a possible payload structure.

PAYLOAD CONFIGURATION
Figure 98. Payload configuration button.

b)
The actual payload structure is displayed in the bottom section of the window.
PAYLOAD
STRUCTURE
first AU4
Figure 99. Payload Configuration window.
1AA 00014 0004 (9007) A4 ALICE 04.10
c)
ED
Click on the AU4 which will be the first AU4 of the concatenated stream. A subwindow is displayed
( see Figure 100. on page 190), which allows to select the payload structure. If the operator selects
AU44C and presses OK, the concatenated configuration is set up in the Payload Configuration
window. See Figure 101.
01
957.130.872 H
3AL 61259 AA AA
230
189 / 230

Figure 100. Payload selection subwindow.
SETUP BUTTON
MSTRAIL
CONCATENATED
PAYLOAD
CONFIGURATION
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 101. Concatenated payload configuration.

d)
ED
Click on SETUP button to confirm. The configuration is sent to the Network Elements and a Report
Log is displayed.
01
957.130.872 H
3AL 61259 AA AA
230
190 / 230
18 TRAIL SETUP

PURPOSE
The Trail Setup function is used to create, allocate, implement and configure an HOTrail within the SDH
Network. An HOTrail is a transport connection between HOTTPs ( HOCAPs) related to SDH ports. An
HO Trail provides LO resources ( LOLCs) to carry LO traffic ( i.e. LO paths ).
PROCEDURE
a)
Select the Node / CTP popup menu (See Figure 102. ) and then the CFG icon. The CFG
(Configuration ) icons are presented (See Figure 103. )
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 102. Browser window
Figure 103. Setup Trail icon
ED
01
957.130.872 H
3AL 61259 AA AA
230
191 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10

b)
ED
Select the Setup Trail icon. The trail configuration window is displayed.
Figure 104. Setup Trail window
01
957.130.872 H
3AL 61259 AA AA
230
192 / 230
If one or more endnodes / ctps are in a globally configured ring, issue a Show/Set Attributes of the
ring (See Figure 105. ) in order to modify the global configuration attribute (global Cfg) to False.

c)
Figure 105. Ring Attribute change

d)
Drag and drop the end nodes/ctps of the new trail. Enter Trail name (user label ), the number of trails
and select the trail payload configuration (See Figure 106. ). Click on SETUP. The Creation Report
is presented (See Figure 107. ) and the new Trail appears in the trail list ( See Figure 107. )
Note that the Number of trails can be specified only for trails between nodes.
The User Label can be:
not specified
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
specified
Configure to
01
it is created according to Rec. M1400. (source sitenamesink site

name VC4Sx where x=progressive no. )
if you create more trails an ordinal number is added to the User Label.
payload configuration selectable from a list ( see Figure 106. )
957.130.872 H
3AL 61259 AA AA
230
193 / 230
The Setup rule can be:
auto
user
endtoend protected
Drop & Continue endtoend protected
when you click on setup, the trail is allocated, implemented,

configured at low order with all LO CTPs and LOLCs.
when you click on setup, the trail is just defined; you can create the
constraints, allocate the trail, implement the trail and finally configure
step by step the payload of the trail.
Setup button
AU4 configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 106. Setup trail
ED
01
957.130.872 H
3AL 61259 AA AA
230
194 / 230

The Protection type can be:
none
In Rings
SNCP
D&C SNCP

Figure 107. Trail view
1AA 00014 0004 (9007) A4 ALICE 04.10
When a trail has been created the Trail view window is automatically displayed on the screen (see
Figure 107. ); if more than one trail are created, the list of defined trails is displayed instead. Starting from
these windows you can performs other actions on created trails (eg. allocate, implement if setup rule is
manual).
Clicking on the relative icon button it is possible to show all defined trails in network.
ED
01
957.130.872 H
3AL 61259 AA AA
230
195 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
196 / 230
19 PATH CREATE

SCOPE
The Path Create function is used to create new paths.
CONDITIONS
The Path creation application can be started from SDH Netview path submenu or from the relative icon
button in the Browser windows.
The Path Create dialog box (see Figure 108. ) contains the following selectable attributes:
UserLabel.
Name of the path.
PathType.
The user can select the type of path among:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Bidirectional
Unidirectional
Broadcast
PathRate.
2 Mb/s
34 Mb/s
140 Mb/s
45 Mb/s
AU44C
ProtType protection type.
None
In Rings
SNCP
D & C SNCP
The user can select the protection type among:
AllocationRule.
Rule of allocation of the resources.The user can select among:
User
Path resource allocation is executed following user command.
Automatic
Path resource allocation is done automatically upon path

creation.
01
957.130.872 H
3AL 61259 AA AA
230
197 / 230
AllocationConstraints.
The user can select between:
notAlarmedResourceOnly
Only link connections with enabled operational state can

be used. The operational state of the link connections is
disabled when one of the following conditions is present:
one/both end ctp/s is/are disabled
the server trail is disabled.
noRestriction
All link connections can be used.
Propagation Rule
Alarm Propagation rule.The user can select between:
When Implemented. Alarms will be propagated to this path at implementation time.
When Commissioned. Alarms will be propagated to this path at commissioning time.
ImplRule
Implementation rule.The user can select between:
Automatic.
The path implementation is done automatically upon path

creation.
User
The path implementation is executed by the user.
MS Protection Usage Profile (for 4F MSSpring only). This attribute can allocate the path on the
protection or working capacity
Path group
String which is associated to all paths belonging to a group.
Automatic Monitoring.
The user can select between False and True. If True is selected,
a measure on this path is automatically created. The measure
name coincides with the path one.
Comment12 :
Descriptive information can be entered to describe the path.
Customer
Descriptive information
NapList symbol
The space under the NAP List symbol is left for NAP or Node dropping. These objects should be dragged
from Browser or NAP/NODES Inventory.
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.
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).
1AA 00014 0004 (9007) A4 ALICE 04.10
In addition, 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.
A dialog box is presented, which allows the enabling rule selection by means of a dictionary.
ED
01
957.130.872 H
3AL 61259 AA AA
230
198 / 230

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 108. Path Creation
ED
01
957.130.872 H
3AL 61259 AA AA
230
199 / 230

a)
Select the Network.
b)
Open the Network popup menu and select Display: Related items.
c)
In the selection box select the option All Nodes and click on Apply.
The Nodes belonging to the selected Network are displayed in the MIB Browser window.
d)
Select the first node involved in the path. Open the popup menu and select Display: Related items:
NAPs
e)
Select the NAP and click on the Path Creation tool button.
f)
Repeat steps d ) and e ) for the other NAPs.
g)
Enter the correct used direction values.
h)
Click on the Create Path button. A dialog box informs: Starting path creation
1AA 00014 0004 (9007) A4 ALICE 04.10
If the path is created the browser window of path and used naps is automatically shown; starting from this
window is it possible to perform all actions on path (eg. allocate, implement, ...). In case of Multiple path
creation (see next paragraph) the list of created paths is automatically shown.
ED
01
957.130.872 H
3AL 61259 AA AA
230
200 / 230

19.1 Path Create by using the Browser

19.2 Path Create by using NETVIEW Browse: Nodes or relative icon

a)
Select the relevant nodes from the map.
b)
Select menu Tools Path: Create. The Path Create dialog box is open. It contains the already selected
nodes.
c)
Click on the Path Creation button. A dialog box informs: Starting Path Creation. The system
chooses the first free NAPs from the selected nodes.
A message will inform whether the operation was successful or not.
19.2.1 Multipath Create

If the Operator selects the Multipath Create button, the window shown in Figure 109. is displayed.
Figure 109. Multi path creation

The following values must be specified:
Number of paths (numerical value)
Starting (numerical value)
Append (radio button)
Replace (radio button)
1AA 00014 0004 (9007) A4 ALICE 04.10
If Append is selected, the path sequential numbering is added as a suffix to the name of the path.
If you want to insert the sequential numbering in the inner of the path name, the userlabel containing the
%nd characters should be written where n corresponds to the numbering field size. In this case you have
to select Replace.
ED
01
957.130.872 H
3AL 61259 AA AA
230
201 / 230
number of paths
>1
starting
any
1AA 00014 0004 (9007) A4 ALICE 04.10
This feature allows to associate as constraint the first created path. The user can carefully setup the
first created path. The remaining ones will have the same route.
ED
01
957.130.872 H
3AL 61259 AA AA
230
202 / 230

The Associate feature is provided (same route) if the following are selected:
1AA 00014 0004 (9007) A4 ALICE 04.10

19.3 Path Create by using NETVIEW Browse: Nap(s)
Figure 110. Path Create.
ED
01
957.130.872 H
3AL 61259 AA AA
230
203 / 230
Select the involved nodes from the map and enter Browse:Nap(s): 2Mb/ 34Mb/ 140Mb / filtered or
click on the Nap list icon (all naps in selected nodes).
1AA 00014 0004 (9007) A4 ALICE 04.10
The NAP lists of both originating and terminating nodes are displayed.
b)
From the NAP list of the originating node select the NAP and press tool button Create Path . The Path
Create dialog box opens, it contains the first selected NAP.
c)
From the NAP list of the terminating nodes select the relevant NAPs and press the tool button Create
Path. The selected NAPs are added to the NAP list of the Path Create dialog box.
d)
Enter the required parameters (user label, rate, ...) and start the path creation or multiple path
creation clicking on hte relative button.
e)
When the path is created the browser window of path and used naps is automatically shown (see
fig. ); starting from this window is it possible to perform all actions on path (eg. allocate, implement,
...). In case of Multiple path creation the list of created paths is automatically shown.
ED
01
957.130.872 H
3AL 61259 AA AA
230
204 / 230

a)
20 PATH/TRAIL CONSTRAINTS
The purpose of this procedure is to set/modify the use or not of specified resources for a path/trail.
CONDITIONS
The action Create/Modify Constraints can be applied on a defined path/trail; if it is applied to an already
allocated path, it will be taken into account at the next allocation.
PROCEDURE
Select a path from the Browser path List or other window (eg. path view, path routing view, ...) and
click on the Add Constraint to a Path icon button.The Path Constraints window is displayed ( see
Figure 111. ). The selected path is dropped into the path drop area.
Path/Trail drop area
a)
1AA 00014 0004 (9007) A4 ALICE 04.10
Constraint drop area

PURPOSE
Figure 111. Path Constraints dialog box (use/not use constraint for CTPs popup)
ED
01
957.130.872 H
3AL 61259 AA AA
230
205 / 230
From the SDH netview it is possible to select Subnetworks, ETs, Nodes, Ports, Connections and click
on the Path Constraint icon.
From the Browser is it possible to select Subnetworks, ETs, Nodes, Ports, Connections, Trail, Ctp,
Routing link, Path and click on the Path Constraint icon.
The selected items are automatically dropped into the Constraint Drop Area.
c)
To delete objects from this list use the popup menu Delete.
The Constraints will be used after a subsequent path allocation.
1AA 00014 0004 (9007) A4 ALICE 04.10
For each constraint specify the usage; two different kind of constraint can be used:
ED
to be used or not (see para 20.1).
to be overlapped or disjointed (see para 20.2).
01
957.130.872 H
3AL 61259 AA AA
230
206 / 230

b)

20.1 Use/Not use

This set of constraints are available for all type of objects dropped in Constraint area.
This constraint type means that the resources must be used (or not) in the proper route (Main, Spare,
Service) of a path/trail. The constraint usage can be (see Figure 111. ):
Use Main
Use Spare
Not Use Main
Not Use Spare
Not Use
Use Service
Not Use Service
Use Main as A
Use Main as Z
Use Spare as A
Use Spare as Z
Use Main&Spare as A
Use Main&Spare as Z
Use Service Forwards
Use Service Backwards
The values Use Service Forwards and Use Service Backwards are significant for paths crossing a
Dual Node SNCP network. See Figure 112.
The user drops as constraint one of the Physical connections between the two D& C nodes, or a link
connection, or a CTP, then must select between Use Service Forwards and Use Service Backwards.
If the user selects Use Service Forwards, the object dropped as constraint will be used as service
route/termination to protect the forward transmission direction (from A to Z or from the left to the right
or the TX)
1AA 00014 0004 (9007) A4 ALICE 04.10
If the user selects Use Service Backwards, the object dropped as constraint will be used as service
route/termination to protect the backward transmission direction (from Z to A or from the right to the
left or the RX)
ED
01
957.130.872 H
3AL 61259 AA AA
230
207 / 230

FORWARD
BACKWARD
THIS PHYSCON IS USED
THIS PHYSCON IS USED
AS CONSTRAINT:
AS CONSTRAINT:
USE SERVICE FORWARD
USE SERVICE BACKWARD
Figure 112. Use Service Forward/Backward for Dual Node SNCP network
1AA 00014 0004 (9007) A4 ALICE 04.10
The Constraints with A or Z are used only in unidirectional or broadcast paths only for dropped CTP; this
constraint specify the direction of paths: A means that the CTP must be used as source of connection in
topology and Z as sink.
The protection type of the dropped object affects the available constraint type parameter as following:
Protection type
Available constraint type
Not protected
Only Main
In ring
Only Main out of ring

Main or Spare in ring
SNCP
Main and Spare
Drop & Continue SNCP
Main, Spare and Service
ED
01
957.130.872 H
3AL 61259 AA AA
230
208 / 230
The Option:Check disabled allow to the operator to use Spare or Service constraint type for an
unprotected dropped path/trail. In this way it is possible to define the constraint before the
protection of the path/trail.
1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.
ED
01
957.130.872 H
3AL 61259 AA AA
230
209 / 230
Constraint drop area
Path/Trail drop area

20.2 Overlapped/Disjointed
Figure 113. Path Constraints dialog box (disjoint/overlap constraint for PATHs popup)
1AA 00014 0004 (9007) A4 ALICE 04.10
This set of constraints are available only for Path and Trail dropped in Constraint area (see Figure 113. ).
A path (or HOTrail) can be used as a constraint of another path (or HOTrail); the constraint type can
be either completely disjointed (not use same route) or overlapped. The overlap can be on the same
server trail (overlapped) or on the same Routing links (route overlapped) .
ED
01
957.130.872 H
3AL 61259 AA AA
230
210 / 230
21 ADD LEGS

The Add leg function consists in adding a sink (or more) termination to a broadcast or unidirectional path.
Select a path from the Path List (see Figure 114. ) or other window (eg. path view, path routing view, ...)
and select the Actions:Broadcast Path modify:Add Leg pulldown menu or click on the corresponding tool
button.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 114. Path list
ED
01
957.130.872 H
3AL 61259 AA AA
230
211 / 230
Choose Node(s) from SDH netview or from Browser or choose Naps from Browser windows (lists or views)
and then click on the Add legs icon button (from Browser it is possible to Drag&Drop by hand) .
Add Leg
Drop area
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 115. Add Leg dialog box
ED
01
957.130.872 H
3AL 61259 AA AA
230
212 / 230

The Add Leg window is opened. (See Figure 115. ).

22 CONNECTIVITY INVENTORY
22.1 General
This application can be launched from the Browser window by selecting the relevant tool button.
The application can also be invoked from the Netview map by means of the pulldown menu Supervision:
Network Connectivity. It is necessary to drag and drop the topology (NTW, SBN, ET) whose connectivity
information is to be analyzed only if started from Browser.
The Connectivity Inventory window which is displayed upon launching the application contains the
following pulldown menus:
File
contains the only option Exit, to close the application.
Actions
contains the following menus:
Get topologies, which allows to further select between first level * and all levels**
Get Connections, to display the connections on the window
Forget Topologies, to delete the topologies actually displayed on the window
Forget Connections, to delete the connections actually displayed on the window
Refresh Connections, to synchronize (actualize) the actually displayed connections
Show Attributes, to display the attributes of the selected connection object
The View pulldown menu only contains the option Displayed info and the Run pulldown menu allows
to start the browser on the selected object.
(*) It performs a get on topologies just one scope level below the dropped topology in the MIB tree, for
example the node contained in the dropped ET.
(**) It asks for which topology below the dropped one you want to perform the get, for example all nodes
contained in the dropped Network
1AA 00014 0004 (9007) A4 ALICE 04.10
Popup menus are also available on the displayed topologies and connections (generic and specific
actions).
ED
01
957.130.872 H
3AL 61259 AA AA
230
213 / 230
22.2 Data Visualization
Execute the following:

a)
In the Connectivity Inventory window select the Actions:Get Topologies pulldown menu.
If you select the first level you will get the topologies just one level below the dropped ONE (E.g. SBN
for NTW, ET for SBN, NODE for ET); if you select all levels you can select among the following
topologies:
subnetwork, ring, node, if you have dragged a network.
ring, node if you dragged a subnetwork
node if you have dragged a ring
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 116. Actions:Get Topologies:all levels
ED
01
957.130.872 H
3AL 61259 AA AA
230
214 / 230

The purpose of this procedure is to get the topologies and connections useful to represent the connectivity.

After the get topologies operation it is possible to enter a Get Connections action. An example is shown
herebelow.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 117. Connectivity Inventory : VC4 Trails
ED
01
957.130.872 H
3AL 61259 AA AA
230
215 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
216 / 230

23 EVENT LOGGER
23.1 Introduction
Displays the current events and the list of the events which have been stored in the log file.
The Event Log window is shown in Figure 118.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 118. Event Logger
ED
01
957.130.872 H
3AL 61259 AA AA
230
217 / 230
Class Type. The operator can choose to display events relative to all classes that manage one or
more event type (eg. nodes, ports, physical connections, paths, trails, measures, ...)
Event Type. The operator can select among the following types:
all types (wildcard)

attribute Value Change
state Change
object Creation
object Deletion
communication alarm
switch status change
quality of service alarm
processing error alarm
operation reporting
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 or SDH netview it is possible to select an item an click on the Event
Logger icon; the items are automatically dropped into the Object Instance 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;
Exit, to quit from the Event Logger application.
Apply, to start the event log process.
Cancel Get, to abort the data retrieval.
Help, to invoke the online help.
ED
01
957.130.872 H
3AL 61259 AA AA
230
218 / 230

This box allows the user to select the following parameters:
EVENT LOG


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.
1AA 00014 0004 (9007) A4 ALICE 04.10
An example of event log is shown in Figure 119.
Figure 119. Event Log
ED
01
957.130.872 H
3AL 61259 AA AA
230
219 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
3AL 61259 AA AA
230
220 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10

24 RM JAVA BROWSER
24.1 Introduction
The 1354RM web browser application is powerful means to naigate in the MIB data base.
The application is bsed on web technologies, merging the use of SQL views with Java screens.
24.1.1 Access
1)
Execute the startup of Netscape navigator.

The Netscape window is displayed.
2)
Enter the work station name. The 1354RM home page is displayed. See Figure 120.
Figure 120. 1354RM home page
ED
01
957.130.872 H
3AL 61259 AA AA
230
221 / 230
The Netscape window contains:

lefthand side region (left subframe):
two functional links: Expand All and Shrink All, to expand or shrink the menu. Figure 121. displays
the shrunk menu. Figure 122. on page 225 shows the expanded menu.
Figure 121. Shrunk menu.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
righthand side region (lright subframe): it is the window working area which displays the retrieved
contents.
01
957.130.872 H
3AL 61259 AA AA
230
222 / 230

24.1.2 Available Choices

The binder Statistics contains the following choices: (see Figure 122. on page 225)
Network Element. This is a directory which contains the following options:
by type. See example in Figure 124. on page 227
by site. See example in Figure 125. on page 227
boundary NEs
Paths. This is a directory which contains the following options:
by rate. See Figure 126. on page 228
by type
by protection
All. The selection of this item presents the filter option. See Figure 127. on page 228. See
description on paragraph 24.1.3 on page 224.
Naps.
The binder Naps contains the only choice by rate.
Physical Connections. This is a directory which contains the following options:
by rate
All
Trails
The binder Trails contains the only choice by payload.
Routing Links. This is a directory which contains the following options:
busy by layer
idle by layer. See Figure 128. on page 229
idle link connections
link connection usage
Pm
1AA 00014 0004 (9007) A4 ALICE 04.10
The binder Trails contains the only choice Measurements
The binder Documentation contains the only choice Operator Manual, which if selected, allows to navigate
through the Operators Handbook. See Figure 123. on page 226.
ED
01
957.130.872 H
3AL 61259 AA AA
230
223 / 230
The Filter view ( see Figure 127. on page 228 ) is used to display a list of attributes of the selected object.
The view structure is as follows:
Selection parameters
attributes, filtercriterion , value.
Control buttons
The selection parameters are
Three control buttons are provided: Reset Filter, add, Go Select
The lefthand column contains the list of all the attributes of the selected object
The central column (option button) specifies the filter condition. A popup menu can be opened, which
allows to select among the options.
If the attribute is of type string the popup menu which can be opened is the following:
Start with.
Match .
Contains.
This filter condition provides the instances which start with the speci
This filter condition applies an exactly match between the field
specified and the relevant MIB data.
This filter condition provides the instances which contain the speci
If the attribute is of the type enumerated, the popup menu which can be opened is the following:
Equal to
Not Equal to
If the attribute type is integer the popup menu is:
Greater than
Less than
Equal to
Not equal to
Greater equal than
Less equal than
The righthand column contains the attribute values. The value can be entered in text field, for the types
integer and string. The value can be entered as option for the type enumerated.
1AA 00014 0004 (9007) A4 ALICE 04.10
The function of the filter is an AND of all the previously specified conditions.
ED
01
957.130.872 H
3AL 61259 AA AA
230
224 / 230

24.1.3 Filter
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 122. Expanded menu
ED
01
957.130.872 H
3AL 61259 AA AA
230
225 / 230

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 123. Operator Manual selection
ED
01
957.130.872 H
3AL 61259 AA AA
230
226 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 124. NEs ordered by type
Figure 125. NEs ordered by site
ED
01
957.130.872 H
3AL 61259 AA AA
230
227 / 230

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.872 H
Figure 126. Path by rate and configuration
Figure 127. Path: All filter
3AL 61259 AA AA
230
228 / 230
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 128. Routing links completely idle
ED
01
957.130.872 H
3AL 61259 AA AA
230
229 / 230

INDEX
Add Connection, 88
Add Object, 84

Multicolumn Windows, 165, 177

Multipath, 201
P
Paste, 59
Path List, 174
Path/Trail Constraints, 205, 211
Payload Configuration, 183
B
Browse PullDown, 103
Browse: Paths....: in Topology, 106
Browser Main, 115
R
C
Refresh Map, 40
Connectivity Inventory, 213
Cut: From This Submap, 58
S
SDH Manager, Main functionalities, 13
Submap, 38
D
Deimplement, 95
Delete: From All Submaps, 60
Distribute Maps, 47
Drawing Windows, 139
T
Trail Setup, 191
Implement, 94
Upload EML, 74
Locate, 64
Virtual Elements, 77
M
Map, 30
1AA 00014 0004 (9007) A4 ALICE 04.10
END OF DOCUMENT
ED
01
957.130.872 H
3AL 61259 AA AA
230
230 / 230

TABLE OF CONTENTS
1AA 00014 0004 (9007) A4 ALICE 04.10
01
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Purpose of the Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 Abbreviations and Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
5
6
6
2 SYSTEM MANAGEMENT FEATURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 USER INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 SMF Windows Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2 Main Level operativity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.3 SMF activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.4 2nd level operativity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
9
9
11
11
12
4 OPERATOR ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 List Current Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 List Successful Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.3 List Unsuccessful Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.4 List Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.5 Add Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.6 Remove Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.7 Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.8 Change Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.9 Detailed Info about Network Access Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.10 New Embedded Rules for PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.11 Customer Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.12 Integration of 1354RM with SEC Security Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.13 Initiator Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.14 Scheduled Rules Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.15 Add Scheduled Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.16 Remove Scheduled Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
13
14
16
17
18
19
21
22
24
28
33
36
37
42
44
44
44
000721
validated
01A 000515
proposal
ED
DATE
CHANGE NOTE
F.CASASOLE ITAVE
E.CORRADINI
F.CASASOLE ITAVE
E.CORRADINI
V.PORRO ITAVE
R.MANCINI
V.PORRO ITAVE
R.MANCINI
APPRAISAL AUTHORITY
ORIGINATOR
1354RM REL.5.2B
OPERATORS HANDBOOK
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
1 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10
45
46
48
5 CONSOLE ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1 Console State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.2 List Operator Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.3 Add Operator Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.4 Remove Operator Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.5 Lock Operator Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.6 Unlock Operator Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.7 System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.8 System Inspect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
49
49
50
51
52
53
54
55
56
6 SYSTEM LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1 List System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.2 Lis Archived System Messagest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.3 List Restored System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
61
61
63
64
7 PERIODIC ACTIONS MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.1 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.2 Set Scheduling Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.3 Show Scheduling Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.4 Cancel Scheduling Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
65
65
65
65
67
68
8 BACKUP/RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1 Subsystems and Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.2 Operation Area on disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.3 Using a Magnetic Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.4 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.5 Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.6 Remotization Enable/Disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
69
69
69
70
70
71
75
82
9 SYSTEM START/STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.1 Launching by command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2 Start System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3 Stop System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.4 Show System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.5 Autostart Enable/Disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.6 Show Autostart Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.7 Process Monitoring Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
83
83
83
84
85
86
87
88
89
10 TRACE ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 Cleaning files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 Purge Trace Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.1 Periodic Action reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4 Dump Log and Trace Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
91
91
91
92
93
94
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
95
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
2 / 96

4.1.17 Maximum Operators Logged . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1.18 Forced Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.19 Set Default Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10


FIGURES
Figure 1. Selection path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. SMF window levels and organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. List Current Login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. List Successful Login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. List Unsuccessful Login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. List Operators window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. Add Operator window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Add Operator:Initiator selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. Remove Operator window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Change Password window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. Change Password subwindow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Change Initiator window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. Add Initiator window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. Add Scheduled Rules window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. Maximum Operators logged window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Forced Logout dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Details of users processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Set Default Printer dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. List Operator Consoles window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Add Operator Console window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. Remove Console window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Lock Operator Consoles window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. Unlock Operator Consoles window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. System Inspect window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Disk and Partition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. Memory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. Current Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. Unix System Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. Logged Users Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. List System Messages window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. List Archived System Messages window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. Set Scheduling Time window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. Show Scheduling Time window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. Cancel Scheduling Time window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. Example of Backup subtree structure on 1354RM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. Backup window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Backup execution subwindow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. Saving on Tape subwindow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. Restore window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. Status subwindow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. Subtypes subwindow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. Load data from Tape subwindow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. Restore execution subwindow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. Remotization Enable/Disable window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. Start System window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 47. Stop System window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 48. Show System status window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 49. Autostart Enable/Disable window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 50. Show Autostart status window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
01
9
10
14
16
17
18
19
20
21
22
23
24
43
44
45
46
47
48
50
51
52
53
54
56
57
57
58
58
59
59
61
63
65
67
68
70
71
72
73
75
77
78
79
80
82
84
85
86
87
88
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
3 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10
92
94
TABLES
Table 1. Access Rules Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2. NAD / FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3. Chars set for the entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4. Procedures for Log and Trace management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
34
66
91
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
4 / 96

Figure 51. Purge Log&Trace Files window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 52. Dump Log and Trace Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

1 INTRODUCTION
1.1 Purpose of the Document
Purpose of this document is to describe to the users the services supplied by the System Management
Features in the 1354RM environment.
1.2 Target audience

The Introduction Manual is intended for all 1354RM users.
1.3 Document structure

ED
Features
User Interface
Login supervision
Operator Management
Initiators
Security on AS
Console Administration
System Log
Periodic Actions
Backup/Restore
System Start/Stop
Trace Administration
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
5 / 96
1.4 Document Conventions
underlined
Single underline is used for argument introduction.
italic
Italic type is used for recurring names, when they are used for the first time.
courier
Courier type is used to indicate output produced by the system, files name and
variables name.
courier
Bold courier type is used to indicate commands typed by the operator.
<data>
Courier type between angle brackets is used to indicate data depending on the
context.
1AA 00014 0004 (9007) A4 ALICE 04.10
1.5 Abbreviations and Terms

EML
Element Management Layer;
FAD
Functional Access Domain;
NML
Network Management Layer;
NN
Acronym for 1354NN product;
RM
Acronym for 1354RM product;
SH
Acronym for 1353SH product;
SMF
System Management Features;
TMN
Telecommunication Management Network ;
WS
Workstation;
product
This term is used to indicate indistinctly the TMN products: 1353SH, 1354RM
and 1354NN;
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
6 / 96

The following conventions are used in this document:
2 SYSTEM MANAGEMENT FEATURES

The following features actually makes up the SMF in NML context of NR5:
1)
2)
3)
4)
5)
6)
7)
Operator Administration;
Console Administration;
System Log;
Periodic Actions;
Backup & Restore;
System Start/Stop;
Log&Trace Administration.
For each feature the following functions are available:
Operator Administration functions:

a)
b)
c)
d)
e)
f)
g)
h)
i)
j)
k)
l)
m)
Console Administration functions:

a)
b)
c)
d)
e)
f)
g)
1AA 00014 0004 (9007) A4 ALICE 04.10
List System Messages,

List Archived System Messages,
List Restored System Messages;
Periodic Actions functions:

a)
b)
c)
ED
List Operator Consoles,

Add Operator Console,
Remove Operator Console,
Lock Operator Console,
Unlock Operator Console;
System Messages
System Inspect
System Log functions:

a)
b)
c)
,List Current Login

List Successful Login,
List Unsuccessful Login;
List Operators
Add Operator
Remove Operator,
Change Password,
Change Initiators
Initiator Management
Scheduled Rules Management
Maximum Operators Logged
Forced Logout
Set Default Printer
01
Show Scheduling Time,

Set Scheduling Time,
Cancel Scheduling Time;
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
7 / 96
Backup & Restore functions:

a)
b)
c)
System Start/Stop functions:

a)
b)
c)
d)
e)
f)
1AA 00014 0004 (9007) A4 ALICE 04.10
Start System,
Stop System,
Show System Status
Autostart Enable/Disable,
Show Autostart Status
Process Monitor Control
Trace Administration functions:

a)
b)
ED
Backup,
Restore;
Remotization Enable/Disable

01
Purge Log&Trace Files.

Dump Log & Trace Files
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
8 / 96

3 USER INTERFACE
3.1 Introduction
This chapter describes the interface through which every feature operates.
3.1.1 SMF Windows Levels
A Main SMF window level is provided, from which the operator chooses and activates functions following
a selection path: Feature Function, as shown in Figure 1.
SMF application
function 1
function 2
............ ..
function i
feature 1
feature 2
.......... ..
.......... ..
function n
feature n
Figure 1. Selection path
1AA 00014 0004 (9007) A4 ALICE 04.10
The control of the actions relevant to a function is provided by means of a 2Level (second level) SMF
window. 2Level windows main characteristic, is that it depends on the activated function.
Figure 2. shows the two levels.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
9 / 96

Main level
Selecting Feature
Main level
Selecting Function
2Level
Managing Function
Header area
Work area
1AA 00014 0004 (9007) A4 ALICE 04.10
Status area
Figure 2. SMF window levels and organization.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
10 / 96
3.1.2 Main Level operativity

3.1.3 SMF activation

In 1354RM the operator can:
a)
b)
c)
display the subpanel of SMF from HPCDE front panel toprow;

click on TMN OSs control;
select a subsystem in TNM OSs window;
3.1.3.1 Selecting the feature

On SMF application activation, the Main window appears. With reference to Figure 2. :
the Header Area presents the application name: System Management Features;
in the Work Area are present:
1 selectable Listbox, whose items are the available features;
1 empty relief Bar, over the Listbox;
3 Confirmation Buttons: OK to confirm, Back disabled, Exit to terminate the

application;
The operator can:

1)
select a feature;
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
ED
confirm feature selection clicking on OK button;
2)
double click on a feature;
3)
close the window and terminate SMF application clicking on Exit button.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
11 / 96
3.1.3.2 Selecting the function
In the Work Area are present:
1 selectable Listbox, whose items are the functions provided for the selected feature;
1 relief Bar, over the functions Listbox, filled with the name of the selected feature;
3 Confirmation Buttons: OK to confirm, Back to come back to the feature selection, Exit
to terminate the application;
The operator can:

1)
select a function;
a)
confirm function selection clicking on OK button;
2)
double click on a function;
3)
come back to the feature selection clicking on Back button.
4)
close the window and terminate SMF application clicking on Exit button.
If the operator confirms the selected function (move 1a or 2), the relevant 2Level window is opened.
3.1.4 2nd level operativity
1AA 00014 0004 (9007) A4 ALICE 04.10
The operativity of 2Level windows will be described in the next chapters, each one contextually to single
feature description.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
12 / 96

After feature selection, a subwindow is presented. With reference to Figure 2. :

4 OPERATOR ADMINISTRATION
4.1 Introduction
The Operator Administration feature provides several functions to manage Operators. They are:
List Current Login
List Successful Login
List Unsuccessful login
List Operators
Add Operators
Remove Operators
Change Password
Change Initiators
Initiator Management
Scheduled Rules Management
Maximum Operators Logged
Forced Logout
Set Default Printer
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
The Print Option is present on all dialog boxes.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
13 / 96
4.1.1 List Current Login
This function allows the operator to view the list of operators currently logged in, on the workstations
belonging to the network configuration.
SEQUENCE
a)
b)
c)
Select the SMF icon from the vertical palette.

Select the feature Operator Admiistration and confirm by pressing OK.
From the Operator Administration window select the option List Current Login and confirm by
pressing OK. The list of Current Login is presented (See Figure 3. ).
Figure 3. List Current Login window
The Header Area presents the function name: List Current Login;
1AA 00014 0004 (9007) A4 ALICE 04.10
The elements to manage the workstations filtering.

1 listbox, unselectable, which contains the list of operators. The list is equipped of an header
indicating the composition of items line:
Workstation
Username
Terminal
Date&Time Profile.
2 buttons: Print to print the operators list on the default printer, Close to close the window
and return to the Main.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
14 / 96

SCOPE
WS FILTERING
1AA 00014 0004 (9007) A4 ALICE 04.10

Two buttons are present in the upper left hand side of the window:
Select WS
All WS
If you click on Select WS, you have to select the WS from the list presented in the upper right hand side
of the window, then you click on button Apply. Finally you will get the current login list on the selected WS.
If you click on All WS, the WS list is no longer selectable and the current login list on all WSs is immediately
presented.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
15 / 96
4.1.2 List Successful Login
This function allows the operator to view the list of successfully terminated attempts to log in, on WSs
belonging to the network configuration.
SEQUENCE
a)
b)
c)

Select the feature Operator Administration and confirm by pressing OK.
From the Operator Administration window select the option List Successful Login and confirm by
pressing OK. The list of successful login is presented (See Figure 4. ).
Figure 4. List Successful Login window
1AA 00014 0004 (9007) A4 ALICE 04.10
The Header Area presents the function name: List Successful Login;
The elements to manage the WSs filtering.
1 listbox, unselectable, containing the list of attempts to log in that have been successfully
terminated. The list is equipped of an header indicating the composition of items line:
Workstation
Username
Terminal
Date&Time Profile.
2 buttons: Print to print the list content on the default printer, Close to close the window
WS FILTERING
For the workstation filtering refer to para. 4.1.1 on page 14
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
16 / 96

SCOPE
4.1.3 List Unsuccessful Login

SCOPE
This function allows the operator to view the list of Operators unsuccessful attempts to log in, on
workstations belonging to the network configuration.
SEQUENCE
a)
b)
c)

From the Operator Administration window select the option List Unsuccessful Login and confirm by
pressing OK. The list of unsuccessful login is presented (See Figure 5. ).
Figure 5. List Unsuccessful Login window
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
The Header Area presents the function name: List Unsuccessful Login;
The elements to manage the WSs filtering.
1 listbox, unselectable, which contains the list of failed login. The list is equipped of an header
indicating the composition of items line:
Workstation
Username
Terminal
Date&Time.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
17 / 96
4.1.4 List Operators
This function allows the operator to examine the list of operators existent on workstations belonging to the
network configuration.
SEQUENCE
a)
b)
c)

From the Operator Administration window select the option List Operators and confirm by pressing
OK. The Operator list is presented (See Figure 6. ).
Figure 6. List Operators window
1AA 00014 0004 (9007) A4 ALICE 04.10
The Header Area presents the function name: List Operators;

1 listbox, unselectable, which contains the list of operators existing on selected ws. The list is
equipped of an header indicating the composition of items line:
Workstation
Username
Profile
Real Name.
Initiator
2 buttons: Print to print the operators list, Close to close the window and return to the
Main.
WS FILTERING
For the workstation filtering refer to para. 4.1.1 on page 14
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
18 / 96

SCOPE
4.1.5 Add Operator

SCOPE
This function allows the Administrator to create one new operator at a time on WSs belonging to the
network configuration.
SEQUENCE
a)
b)
c)
d)

From the Operator Administration window select the option Add Operator and confirm by pressing
OK. The Add Operator dialog window is presented (See Figure 7. ).
After entering all information you can confirm the Operator creation by pressing button Add.
A subsequent confirmation box containing all data relevant to the New Operator being created is
presented. If you press OK the Opertaor is created. This dialog box also contains the button Abort
to abort the procedure.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 7. Add Operator window
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
19 / 96
The Header Area presents the function name: Add Operator;

In the Work Area are present three sections:
WS filtering
1 listbox, selectable, which contains the list of defined WS;
1 couple of radiobuttons, with label: All WS to select all WS on which to add operator, and
Select WS to allow selection from the listbox of WS;
1 button above the WS listbox, with label Apply : it gives effect to WS selection for operator
creation, and filters the users list;
Data entering
1 listbox, unselectable, which contains the list of users existing on selected WS. The list is
Workstation
Username
Profile
Real Name
Initiator
;
2 entries with labels: User name, Real Name;
1 popdown menu for choosing among available profiles, with label Profiles;
1 popdown menu for choosing among available initiators, with label Initiators;
2 entries for password definition: Password, Confirm Password;

Confirmations
2 buttons: Add to create described operator, Close to close the window and return to the
Main.
Figure 8. Add Operator:Initiator selection.

WS FILTERING
1AA 00014 0004 (9007) A4 ALICE 04.10
For the workstation filtering refer to para 4.1.1

N.B.
ED
The operations allowed to the different types of operators are described in this chapter from
page 25 to page 36.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
20 / 96

The Add Operator window contains the following:
4.1.6 Remove Operator

SCOPE
This function allows the Administrator to remove one operator at a time on WSs belonging to the network
configuration.
SEQUENCE
a)
b)
c)

From the Operator Administration Window select the option Remove Operator and confirm by
pressing OK. The Remove Operator dialog window is presented (See Figure 9. ).
Figure 9. Remove Operator window
The Header Area presents the function name: Remove Operator;

1 listbox, selectable, which contains the list of operators existing on selected WSs. The list is
Workstation
Username
Profile
Real Name
Initiator
2 buttons: Remove to remove selected operator, Close to close the window and return to
the Main.
On Remove button pressing, a message box is presented giving a warning about the operation, and
giving the possibility to confirm or to abort the operation.
WS FILTERING
1AA 00014 0004 (9007) A4 ALICE 04.10
For the workstation filtering refer to para. 4.1.1

N.B.
ED
The operations allowed to the different types of operators are described in this chapter from
page 25 to page 36.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
21 / 96
4.1.7 Change Password
This function allows the operator to change password. Operators whose profile allows to change other
operators password (e.g.: Administrator profile) are distinguished. They are referenced as
Administrator.
SEQUENCE
a)
b)
c)
d)

From the Operator Administration Window select the option Change Password and confirm by
pressing OK. The Change Password window is presented (See Figure 10. ).
Select the username and then select Change, the subwindow of Figure 11. is displayed.
Figure 10. Change Password window
1AA 00014 0004 (9007) A4 ALICE 04.10
The Header Area presents the function name: Change Password;

1 listbox, selectable, which contains the list of operators existing on selected ws. The list is
Workstation
Username
Profile
Real Name
Initiator
2 buttons: Change to continue changing the password, Close to close the window and
return to the Main.
When a non Administrator operator selects another operator, if the Change button is pressed, a
message has to be displayed to inform that the permission is denied.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
22 / 96

SCOPE

Figure 11. Change Password subwindow
The window frame name is the <operatorname>;

The Header Area presents the function name: Change Password;
3 entries for password definition: Old, New, Confirm; for nonpriviledged operators
the entry Oldis not present.
2 buttons: Apply to confirm typed password, Back to close the window and return to the
previous.
Subwindow for Administrator differs from described one for Old entry absence.
1AA 00014 0004 (9007) A4 ALICE 04.10
All entries have the property of showing the asterisk (*) instead of each character typed.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
23 / 96
4.1.8 Change Initiator
This function allows the Administrator operator to change the profile of the selected operator.
SEQUENCE
a)
b)
c)

From the Operator Administration Window select the option Change Initiator and confirm by pressing
OK. The Change Initiator window is presented (See Figure 12. ).
Figure 12. Change Initiator window.

N.B.
d)
e)
The available Initiators and the allowed operations for each Initiator are described in the System
Administrator Reference Guide. The tables which summarize the allowed operation for each
Initiator can be found at paragraph herebelow.
Select the Operator.

Select the Initiator from the popup Initiator list and click on Apply Change button.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
The resources cited below have the NAD attribute and can be assigned to a certain NAD
Network Assignment Domain) :
path
lc
trail
nap
The command utilized is Change: NAD.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
24 / 96

SCOPE
1AA 00014 0004 (9007) A4 ALICE 04.10

4.1.8.1 Initiators
A set of Initiators is provided with 1354RM delivery. They represent the most typical operator profiles for
the network management. To each initiator are associated Rules ( set of operations ). The table describing
each rule can be found at paragraph 4.1.8.3.
Initiator Name
Rules
Description
Free Pool
No Rules
Used to define composite rules. Not mapped to any

user.
RM Administrator
SNML
All operations allowed.
Advanced Operator
PAYLOAD PTHADM
PayloadPath Administration
Network Constructor
TOP
PTHADM PAYLOAD
Topology
PayloadPath Administration
Path Watcher
PTHR/O
User profile for readonly operations on path trail.
Path Administrator
PTHADM
Operator for working on path.
Path Allocator
PTHALL
Path create and allocate/deallocate allowed.
1354 NN
VPN
Qnn Agent.
RVPN Operator
RVPN
It is the restricted Virtual Private Operator.
VPN Operator
VPN
It is the Virtual Private Operator.
EVPN Operators
EVPN
It is the enhanced Virtual Private Operator.
Payload Manager
PAYLOAD
Payload
cnm_pathbuilder
VPN
PMVPN
Virtual Private Network

PM Virt. Priv. Netw.
cnm_lookonly
PMVPNR/O
PM Virt. Priv. Netw. Read Only
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
25 / 96
4.1.8.2 Default Mapping between User Profiles and Initiators
The correspondence between User Profiles and Default Initiators is described in the following table.
1AA 00014 0004 (9007) A4 ALICE 04.10
User Interface Profile
Default Initiators
OS Administrator
RM Administrator
Administrator
Network Constructor + System Features
Constructor
Network Constructor
Path builder
Path Administrator or EVPN or VPN or RVPN
Path allocator
Path Allocator
Look Only
Path watcher on whole RM
cnm_pb
cnm_pathbuilder
cnm_lo
cnm_lookonly
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
26 / 96

User Profile related to an operator has impacts on User Interface by hiding or showing some action menus
4.1.8.3 Detailed Access Rules

The available rules are :
AC_R_SNML: RM Administrator.
Its able to perform all the operations without any limit.
It must be assigned very carefully because an Initiator with this capability can modify
operations performed by 1354NN.
It is not usefull to compose this rule with any other one.
N.B.
This rule is mapped by default on the RM Administrator snml. It is

mandatory do not change the snml initiator.
AC_R_PADMIN: Path Administrator.

It can manage paths and releated resources (NAPs and LCs) not explicitely assigned to
VPN domains.
This rule can be composed with AC_R_TOPMAN and/or AC_R_PAYMAN in order to
achieve the needed level of functionality.
the AC_R_PADMIN rule cannot be used for VPN Initiator.
AC_R_PATHALL: Path Allocator.

It can allocate/deallocate paths and manage the resources (NAPs and LCs) not explicitely
assigned to VPN domains.
This rule can be composed with AC_R_TOPMAN and/or AC_R_PAYMAN in order to
the AC_R_PATHALL rule cannot be used for VPN Initiator.
AC_R_PATHRO: Path Watcher.

It can only get paths and NAPs.
the AC_R_PATHRO rule cannot be used for VPN Initiator.
AC_R_TOPMAN: Topology Manager.

It can operate on topologies in order to modify the network.
This rule can be composed with AC_R_PADMIN and/or AC_R_PAYMAN in order to
the AC_R_TOPMAN rule cannot be used for VPN Initiator.
AC_R_PAYMAN: Payload Manager.
1AA 00014 0004 (9007) A4 ALICE 04.10
It can operate on payload configuration.

This rule can be composed with AC_R_PADMIN and/or AC_R_TOPMAN in order to
the AC_R_PAYMAN rule cannot be used for VPN Initiator.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
27 / 96
RVPN: Restricted Virtual Private Network Operator.

Its able to create, view, modify paths only using resources (NAPs & LCs) assigned to his
NAD.
It can be assigned only to VPN Initiator.
VPN: Virtual Private Network Operator.

As RVPN except that the routing can be done also on free LCs (Security Label=0).
This Rule is used also for 1354NN activities.
4.1.9 Detailed Info about Network Access Domains

4.1.9.1 Detailed Access Rules
The list of embedded rules is displayed in Table 1.
1AA 00014 0004 (9007) A4 ALICE 04.10
Legend for ownership :
O:
Owned objects (Security label equal Initiator Id)
OF :
Owned or free objects (Security Label equal Initiator Id or 0 )
N:
Not VPN objects (Security label <=300)
A:
All objects
Gray :
Disabled by default rules
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
28 / 96

1AA 00014 0004 (9007) A4 ALICE 04.10

Table 1. Access Rules Description

C
L
A
S
S
Operation
P
A
T
H
allocate, deallocate,
ED
Notes
RULE
R
V
P
N
V
P
N
E
V
P
N
P
T
H
A
D
M
P
T
H
A
L
L
implement, deimple- O
ment, commission,
decommission, add/
remove protection.....
get
Add / remove leg
Create
Change Owner
Delete
01
S
N
M
L
N
N
O
P
For the add leg, the check

is performed also on the
NAP (see Use in Path)
The initiator ID is taken as

NAD of the created object.
In the redolog, the path
creation is followed by a
change of NAD in order to
be able to replicate the final result in term of NAD.
The check to allow or not a
path creation is made on
the path and on the specified NAPs; the path is
created if the NAPs can be
related to the path (see
NAP class)
O
F
It is the action to change

the NAD. The operation is
registered in the redolog
The check is done on the

path and NOT on the used
NAPs (unset of the pathPtr
attribute)
P
T
H
R
/
O
T
O
P
P
A
Y
L
O
A
D
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
29 / 96
N
A
P
L
C
remove nap
O
F
get
O
F
change owner
O
F
The operation is register
Use in path (create a O

path or add leg)
O
F
The command is not present at the user interface

but is embedded in create
path and add leg. It is defined as set on pathPtr attribute
Change owner
O
F
The command is registered in the redolog.

As a consequence of this
operation the LC is also
moved from the original
Routing Link bundle to the
appropriate one. A new
routing links is created if
needed.
Use in path
O
F
O
F
O
F

but is embedded in path or
trail allocation. It is defined
as set on the belongTrailId
attribute.
The allocation algorithm

during the search only
uses the Routing Links
matching the condition for
LCs
Delete
get
1AA 00014 0004 (9007) A4 ALICE 04.10
Configure Payload
ED
01

but is embedded in the
payload configuration of
physical connections and
HOTrails.
A
Only for HOTrails
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
30 / 96



T
R
A
I
L
Change owner
The command is registered in the redolog
Configure Payload
Create
It is the creation of the HO

Trail
Remove
It is the action to remove

the HOTrail; as a consequence a payload deconfig. is started.
T
R
A
I
L
Set Qnn Info
T
O
P
O
L.
/
P
H
C
O
N
N
Create
It is the operation to activate topologies, Nodes,

physical Connection (action)
Implement
It includes the configuration at HO
Deimplement
Remove
Start Network Activ.
Get
Upload NAPs
Configure Payload
Get
M
S
S
P
R
I
N
G
1AA 00014 0004 (9007) A4 ALICE 04.10
O
F
ED
Operate on protection
blocks
Get
01
A
Operation are : modify the
WTR,
force,
manual,...synchronize
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
31 / 96
C
T
P
/
T
T
P
Change defaults for

UPA propagation
P
D
H
P
O
R
T
Configurate PDH port
It is the action to modify the

configuration of a transmux board
It is the action to loopback

a PDH port for testing. The
action can also be started
on a NAP but only as an
extension at US level.
Configuration Download
It is the action to enable /

disable the configuation
download from RM to NEs.
The check is performed
also for operation started
on single NEs
Start Audit
It is the action to start Auditing differences between

NE and EML view. The
check is performed also on
operations started on
single NEs.
Get
O
T
H
E
R
S
1AA 00014 0004 (9007) A4 ALICE 04.10
Get
Get
Operations
R
V
P
N
ED
Loop Back
Get
E
M
L
01
V
P
N
E
V
P
N
P
T
H
A
D
M
P
T
H
A
L
L
P
T
H
R
/
O
T
O
P
P
A
Y
L
O
A
D
S
N
M
L
Eventually restricted by
FAD at the user Interface
Restricted by FAD implemented at the user interface
N
N
O
P
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
32 / 96


4.1.10 New Embedded Rules for PM.

New rules have ben added to manage Performance Monitoring activities. They are described in the
following paragraphs.
4.1.10.1 AC_R_PMSNML : Performance Monitoring SNML
PMSNML is the rule allowing full capability of managing PM domain objects. This rule allows to operate
on all the PM Domain data regardless from the ownership (NAD) of PM data, paths and trails
4.1.10.2 AC_R_PMVPN : Performance Monitoring Virtual Private Operator
PMVPN is, in the PM domain, the equivalent of the VPN rule in the path management domain. This rule
allows to operate / visualize PM data, put under monitoring path or trail only related to a given NAD.
Note that if an operator is the owner of a measure then he is the owner of the pmTp and the pmTransport
of the measure.
4.1.10.3 AC_R_PMADMIN : Performance Monitoring Administrator
PMADMIN is, in the PM domain, the equivalent of the PADMIN rule in the path domain. This rule allows
to fully operate on PM domain related to non VPN measures, PM transport etc. and visualize all
the PM data even if belonging to VPN domains.
Non VPN domain is the set of all RM objects with nad<300.
4.1.10.4 AC_R_PMRO : Performance Monitoring Read Only
PMREAD is the read only rule on PM domain. This rule allows to visualize all the PM related
information regardless to the ownership.
4.1.10.5 AC_R_PMVPNRO : Performance Monitoring Read Only VPN
PMREAD is the read only rule on a given NAD. This rule allows to visualize the PM related information
related to a given NAD.
4.1.10.6 Rule description table.
1AA 00014 0004 (9007) A4 ALICE 04.10
Legend for ownership :
: Owned objects (Security label equal Initiator Id)
OF : Owned or free objects (Security Label equal Initiator Id or 0 )
: Not VPN objects (Security label <=300)
: All objects
Gray
ED
01
:Disabled by default rules
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
33 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 2. NAD / FAD

Operation
M
E
A
S
U
R
E
Notes
RULE
P
M
V
P
N
P
M
A
D
M
I
N
Create
Delete
Set
Activate, Stop and Consistency
Correlate Transport to Measure
This action correlates a Measure to

a Path or Trail.
The check is performed on the
Path/Trail too.
Correlate Tp to Measure
The check is performed on the Tp

(nap, cap, ctp) too.
Correlate Report to Measure
The check is performed on the report (Counter Report or TCR) too.
C
O
U
N
T
E
R
Create
Delete
Set
R
E
P
O
R
T
Get
ED
P
M
V
P
N
R
O
Get
01
P
M
R
O
P
M
S
N
M
L
This is the first step to start a measure session.
See the note about this action in the

Measure class context.
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
34 / 96

C
L
A
S
S

Table 2. NAD / FAD

T
C
A
Create
Delete
P
r
o
f
i
l
e
Set
Correlate pmTp To TCA
T
C
R
Create
Delete
Set

Measure class context.
Create
This command is not present at the

user interface. It is a consequence
of the Correlation of a Path/Trail to
a Measure.
Delete
Create
Delete
Correlate pmTp To TCA
P
A
T
H
N
A
P
Get
Get
P
M
T
R
A
N
S
P
M
T
P
Get
1AA 00014 0004 (9007) A4 ALICE 04.10
Get
ED
01
A
The check is performed on the
pmTp too.
A
This command is not present at the
user interface. It is a consequence
of the Correlation of a Tp to a Measure
A
TCA class context.
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
35 / 96
T
R
A
I
L
C
T
P
/
T
T
P
OF

Table 2. NAD / FAD
4.1.10.7 Customer Network Management CNM

4.1.11 Customer Rules
A customer Rule is a redefinition of an embedded access rule only in terms of Daily and Weekly
Scheduling.
The customized rules must be defined editing the /usr/snml/ac_info/scheduling.ac.<n> file (where <n>
is the Network Domain Id of the current RM): for each new rule a new line shall be added that contains
the corrispondent embedded rule and the time scheduling.
The information included in the file is :
Name of the Customer Rule

Daily Scheduling: its the validity start & end time of the Rule. Starting and Ending Time has the
format hh.mmhh.mm (hh = hour, mm = minute) and shall be expressed in UTC (Greenwich Time).
An empty value enables the rule in the whole day.
Weekly Scheduling: it contains the days of the week for which the daily scheduling applies. Possible
values are in the range from 0 (Sunday) to 6 (Saturday). An empty value enables the rule in all the
days.
Embedded Rule: it is the name of the embedded rule referred in term of functionalities
An example of the file follows:

#Customer Rule : Daily Scheduling : Weekly Scheduling
AC_R_NEWPADMIN : 08.0019.00
: 1 , 2 , 3, 4 , 5
: Embedded Rule
: AC_R_PADMIN
Customer rules can be inserted in the Initiator definition file .

It can be used only for VPN Initiators
1AA 00014 0004 (9007) A4 ALICE 04.10
EVPN: Enhanced Virtual Private Network Operator.
As VPN except that also free NAPs can be used for path setup.
It can be used only for VPN Initiators
No check is performed to avoid the assignment of a VPN rule to non VPN Initiators and
viceversa.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
36 / 96
4.1.12 Integration of 1354RM with SEC Security Subsystem
1AA 00014 0004 (9007) A4 ALICE 04.10

4.1.12.1 SEC Architecture on 1354RM System

The SEC Subsystem is composed of two permanent processes:
secim process, which is the agent of the Security Subsystem and keep all the informations related
to the users and the system. Secim process is running only on 1354RMIM.
lss process, which is a kind of gate for applications related to user Security profile. One lss process
is instantiated for each workstation/server belonging to the 1354RM system (1 for each presentation
and each IM).
These permanent processes are configured to automatically run after the installation.
The SEC integration on 1354RM, as a first step, is intended only for the integration of Security
Management within AS (Alarm Surveillance). This means that each 1354RM operator using AS is able
to view/manage only alarms coming from Network resources that it can manage.
In order to have inside SEC Subsystem all the informations concerning Security, SEC is also integrated
in SMF, in order to get informations related to new users, user removal, and initiator management .
Moreover the integration of SEC in SMF is also related to the Backup operation. Each time a new Operator
backup is performed also SEC database is backuped.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
37 / 96
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.8:SMF
957.130.872 H
3AL 61259 AA AA
96
38 / 96

4.1.12.2 SEC Administration
4.1.12.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.8:SMF
957.130.872 H
3AL 61259 AA AA
96
39 / 96

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.8:SMF
957.130.872 H
3AL 61259 AA AA
96
40 / 96
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
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
as follows:
System_Profile
:
LookOnly
:
ASHISTUSM_FAD@AsHistoricalUsm : ASCURUSM_ALARM_MANAGER_FAD@AsCurrentUsm
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
41 / 96
4.1.13 Initiator Management
This function allows the Administrator operator either to add or remove an Initiator to / from the list of the
Initiators.
4.1.13.1 Adding an Initiator
SEQUENCE
a)
b)
c)
Select the Administration ( SMF) icon from the vertical palette.

From the Operator Administration Window select the option Add Initiator and confirm by pressing OK.
The Add Initiator window is presented. This window contains:
the current Initiator list
two textlines: RM Initiator and Initiator Name where the Administrator operator can digit the
RM Initiator ( integer ) and the Initiator Name (it must be unique in the file).
The Initiator Identifier must be given according to the following rules:
Non VPN Initiators must have Identifier less than 300
VPN Initiators must have Identifier greater than 300
The identifier 0 (zero) is reserved (it is used to identify free resources).
The Identifier 301 is reserved for 1354NN (when present)
The Initiator Name is added to the possible values of the NAD attribute. The NAD attribute
is used to mark Network Resources (using the change NAD command) and to evaluate
Access Rules.
a selection button called Rule which gives the list of the access rules. These rules can be:
embedded rules ( see description at paragraph 4.1.8.3)
customer rules. They are a redefinition of the embedded rules in terms of scheduling.( see
description at paragraph 4.1.11)
An example of the file follows:

#RM initiator : InitiatorName
50
: Path Administrator
55
: PathWatcher
: Rules
: AC_R_PADMIN
: AC_R_PATHRO
In the example, the Initiator 50 is called Path Administrator and is mapped to the rule AC_R_PADMIN.
This access rule allows all the operations on paths.
1AA 00014 0004 (9007) A4 ALICE 04.10
In the Rules field more than one rule can be specified.

The rules are evaluated sequentially and in case of duplication or inconsistency only the first
one is taken into account.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
42 / 96

SCOPE

Figure 13. Add Initiator window.

d)
Enter the suitable RM Initiator and Initiator Name and select the rules to be associated. Click on
the Rule button. The list of the available rules opens. Each item of the list has a toggle button, i.e.
you can select many rules per each Initiator. Click on the Add button to confirm the creation.
4.1.13.2 Removing an Initiator

SEQUENCE
a)
b)
c)
1AA 00014 0004 (9007) A4 ALICE 04.10
d)
ED

From the Operator Administration Window select the option Add Initiator and confirm by pressing OK.
The Add Initiator window is presented (See Figure 13. ).
Select the Initiator to remove and click on the Remove button.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
43 / 96
4.1.14 Scheduled Rules Management
This function allows the Administrator operator to setup / remove customer rules. They are a redefinition
of the embedded rules in terms of scheduling.( see description at paragraph 4.1.11)
4.1.15 Add Scheduled Rules
SEQUENCE
a)
b)
c)

From the Operator Administration Window select the option Add Scheduled Rules and confirm by
pressing OK. The Add Scheduled Rules window is presented. ( See Figure 14. ).
Figure 14. Add Scheduled Rules window.
4.1.16 Remove Scheduled Rules
1AA 00014 0004 (9007) A4 ALICE 04.10
SEQUENCE
a)
b)
c)
d)
ED

From the Operator Administration Window select the option Add Scheduled Rules and confirm by
pressing OK. The Add Scheduled Rules window is presented. ( See Figure 14. ).
Select the Rule to be removed from the list and click on the Remove button.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
44 / 96

SCOPE
4.1.17 Maximum Operators Logged

SCOPE
This function allows the Administrator operator to setup the maximum number of operators logged.
SEQUENCE
a)
b)
c)
d)

From the Operator Administration Window select the option Maximum Operators logged and confirm
by pressing OK. The Maximum Operators logged window is presented (See Figure 15. ). This
window contains the Maximum Operators logged ( default and current values )
In the textline New you can type the new value. Click on Apply to confirm. The new value is present
in the Current field.
Figure 15. Maximum Operators logged window.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
The check on Maximum Operators logged does not consider OS Administrator operators.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
45 / 96
4.1.18 Forced Logout
This function allows the Administrator operator to close the session of an other operator.
SEQUENCE
a)
b)
c)
d)

From the Operator Administration Window select the option Forced Logout and confirm by pressing
OK. The Forced Logout window is presented (See Figure 16. ).
Select the operator to quit and click on the Logout button.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 16. Forced Logout dialog box.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
46 / 96

SCOPE
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 17. Details of users processes.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
47 / 96

4.1.19 Set Default Printer

SCOPE
This function allows the operator to set the default printer.
SEQUENCE
a)
b)
c)

Select option Set Default Printer. The relevant dialog box is opened. See Figure 18.
Figure 18. Set Default Printer dialog box

d)
e)
The dialog box displays in the center of its working area the list of the installed printers. The current
printer name is displayed below the working area.
The user can select another printer by clicking twice on the printer name and then clicking on Apply
button.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
The change of the default printer is made effective only after a logout operation.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
48 / 96

5 CONSOLE ADMINISTRATION
5.1 Introduction
The operator console is intended as a workstation for the 1353SH, but in NML context could be either a
workstation or an XTerminal.
The Console Administration features are:
List Operator Consoles
Add Operator Console
Remove Operator Console
Lock Operator Console
Unlock Operator Console
System Messages
System Inspect
5.1.1 Console State
1AA 00014 0004 (9007) A4 ALICE 04.10
In NML context, a console can be locked/unlocked in addition to be defined or removed. As a consequence

it is necessary to associate a state to the console which can stay in one of the following:
ED
1)
Unlocked, since console definition time;
2)
Locked;
3)
Working, intermediate state between unlocked and locked.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
49 / 96
5.1.2 List Operator Consoles
This function allows the operator to view the list of the operator consoles belonging to the configuration.
SEQUENCE
a)
b)
c)

Select the Console Administration feature and confirm by pressing OK.
From the Console Administration window select the option List Operator Consoles and confirm by
pressing OK. The list of Operators Consoles is presented (See Figure 19. ).
Figure 19. List Operator Consoles window
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
The Header Area presents the function name: List Operator Consoles;
1 listbox, unselectable, which contains the list of configured operator consoles. The list is
Type
Console
State.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
50 / 96

SCOPE
5.1.3 Add Operator Console

SCOPE
This function allows the Administrator to define a new operator console in the network configuration.
SEQUENCE
a)
b)
c)

From the Console Administration window select the option Add Operator Console and confirm by
pressing OK. The Add Operator Console dialog box is presented (See Figure 20. ).
Figure 20. Add Operator Console window
The Header Area presents the function name: Add Operator Console;
1 Entry, with label: Console;
2 Radiobuttons: Workstation and XTerminal;
2 Buttons: Add to add the defined console, Close to close the window and return to the
Main.
The window appears with the radiobutton Workstation selected by default.

If the operator gives a console name which is unknown to the /etc/.rhosts the procedure completes
the assignment operation, and gives a warning message.
1AA 00014 0004 (9007) A4 ALICE 04.10
Twice assignment prevention

If the operator gives a console name, whether an hostname or an IP address, which was just defined into
the $OSWS_FILE, the procedure gives an info message and exits on operator acknowledgment.
When the operator specify an IP address as console name, not defined into the $OSWS_FILE, the
procedure extracts relative hostname from the /etc/hosts and repeats the check in the $OSWS_FILE
using the hostname.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
51 / 96
5.1.4 Remove Operator Console
This function allows the Administrator to remove a defined operator console from the network
configuration.
SEQUENCE
a)
b)
c)

From the Console Administration window select the option Remove Operator Console and confirm
by pressing OK. The list of consoles is presented (See Figure 21. ).
Figure 21. Remove Console window
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
The Header Area presents the function name: Remove Operator Console;
1 listbox, selectable, which contains the list of configured operator consoles. The list is
Type
Console
State.
2 Buttons: Remove to remove the selected console, Close to close the window and return
to the Main.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
52 / 96

SCOPE
5.1.5 Lock Operator Console

SCOPE
This function allows the operator to lock operator consoles belonging to the network configuration.
SEQUENCE
a)
b)
c)

From the Console Administration window select the option Lock Operator Console and confirm by
pressing OK. The Lock Operator Console dialog box is presented (See Figure 22. ).
Figure 22. Lock Operator Consoles window
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
The Header Area presents the function name: Lock Operator Consoles;
1 listbox, selectable, which contains the list of configured operator consoles. The list is equipped
of an header indicating the composition of items line:
Type
Console
State.
2 buttons: Lock to lock the selected console and Close to close the window and return to
the Main.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
53 / 96
5.1.6 Unlock Operator Console
This function allows the operator to unlock the currently locked consoles.
SEQUENCE
a)
b)
c)

From the Console Administration window select the option Unlock Operator Console and confirm by
pressing OK. The Unlock Operator Console dialog box is presented (See Figure 23. ).
Figure 23. Unlock Operator Consoles window
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
The Header Area presents the function name: Unlock Operator Consoles;
1 listbox, selectable, which contains the list of configured operator consoles. The list is equipped
of an header indicating the composition of items line:
Type
Console
State.
2 buttons: Unlock to lock the selected console and Close to close the window and return
to the Main.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
54 / 96

SCOPE
5.1.7 System Messages
1AA 00014 0004 (9007) A4 ALICE 04.10

SCOPE
This function allows an operator to send a broadcast message to all workstations and Xterminals.
SEQUENCE
a)
b)
c)
From the Console Administration window select the option System Messages. The System
Messages window is displayed.
d)
You can digit in the textline the text you want to broadcast.
e)
Press the button Send. The message is then broadcasted.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
55 / 96
5.1.8 System Inspect
This function allows an operator to inspect the system parameters of the selected workstation
SEQUENCE
a)
b)
c)

From the Console Administration window select the option System Inspect. The System Inspect
window is displayed. ( See Figure 24. ). The possible popup options are:
Disk and Partition

Memory Information
Current Processes
Unix System Log Files
Logged Users Information
System Information
The following figures show the information which are displayed per each option.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 24. System Inspect window.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
56 / 96

SCOPE
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 25. Disk and Partition.
Figure 26. Memory Information
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
57 / 96

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 27. Current Processes
Figure 28. Unix System Log Files
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
58 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 29. Logged Users Information
Figure 30. System Information
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
59 / 96

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
60 / 96

6 SYSTEM LOG
6.1 Introduction
This feature allows the operator to view the messages generated by the different SMF functions.
6.1.1 List System Messages

SCOPE
This function allows the operator to view the System Log file.
SEQUENCE
a)
b)
c)

From the System Log features window select the option List System Messages and confirm by
pressing OK. The System Log window is presented (See Figure 31. ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 31. List System Messages window
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
61 / 96
The Header Area presents the function name: List System Messages;
1 couple of Radiobuttons, with label: All to view all messages from the log files, and
Filter to allow messages filtering.
4 checkbuttons for filter criterion: Day, Month, Function, Workstation,

Operator to determine the filter to apply to the list.
1 listbox, containing parameters available for each filter criterion.
1 button above the parameters listbox, with label Apply : it gives effect to the filter application
updating the list of messages.
1 listbox, which contains the list of messages. The list is equipped of an header indicating the
composition of items line:
YYYY MM DD HH:MM:SS
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Workstation
Product/Function: Username Message.
3 buttons: Print to print the list content, Info to display informations about log file in view,
Close to close the window and return to the Main.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
62 / 96

6.1.2 Lis Archived System Messagest

SCOPE
This function allows the operator to view the messages from archived system log files.
SEQUENCE
a)
b)
c)

From the System Log features window select the option List Archived System Messages. The
relevant window of Figure 32. is displayed.
Figure 32. List Archived System Messages window
1AA 00014 0004 (9007) A4 ALICE 04.10
The window appearance and behaviour is near the same of List System Messages, with the exception
that it gives the list of archived files among which the operator has to select.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
63 / 96
6.1.3 List Restored System Messages
1AA 00014 0004 (9007) A4 ALICE 04.10
This functionality is the same of List Archived Messages, the only difference is that the listed messages
are taken from the previously restored log files .
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
64 / 96

SCOPE

7 PERIODIC ACTIONS MANAGEMENT

7.1 Introduction
7.1.1 Definition
Periodic actions are defined as actions that can be modified by the Administrator during the system
activity; such actions are submitted to cron daemon at product installation time if scheduled, otherwise
at first schedulation by the administrator.
E.g.: daily backup for network data.
7.1.2 Set Scheduling Time

SCOPE
This function allows the operator to set the scheduled time for the selected actions.
SEQUENCE
a)
b)
Select the Periodic Actions option and confirm by pressing OK.

From the Periodic Actions window select the Set Scheduling Time option and confirm by pressing
OK. The Set Sheduling Time window opens (See Figure 33. ).
Apply
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 33. Set Scheduling Time window.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
65 / 96
The Header Area presents the function name: Set Scheduling Time;
The Work Area contains:
1 listbox for actions. The list is equipped of an header indicating the composition of items line:
Action
Time:mm hh ddW ddM;
4 entries, with respective labels: Minutes, Hours, Day of week, Day of

month ;
4 radiobuttons, to activate current entry;
1 listbox bound to the entries, containing the list of possible values for the current entry in
editing;
2 Buttons: < to put an item selected from the bound listbox into the current entry field, > to
remove an item selected from the entry;
3 Buttons: Close to close the window and return to the Main, Confirm to apply defined
scheduled time to the list, Set to save modifications activating new crontab file.
From the actions listbox the operator can choose the item to set. On selection automatically the listbox
is bound to the entry of minutes.
The set of characters to make up the values, are presented by the bound listbox on entry selection.
Table 3. Chars set for the entries.
Entry
set of characters
minutes
0..59, *.
hours
0..23, *.
days of week
0..6, *. (0=Sunday).
days of month
1..31, *.
As provided by the syntax of Unix cron, a set of values from a range can be selected by the operator: in
this case the application puts automatically a comma between one value and the next.
When the operator has filled all the entries, he can set the time confirming with the Confirm button.
1AA 00014 0004 (9007) A4 ALICE 04.10
If the operator press Close button and there is a scheduled time which was confirmed but not set, a
warning message asks for a confirmation on closing the functionality.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
66 / 96

7.1.3 Show Scheduling Time

SCOPE
This function allows the operator to examine the scheduled time for the selected action.
SEQUENCE
a)
b)

From the Periodic Actions window select the Show Scheduling Time option and confirm by pressing
OK. The Show Scheduling Time window opens (See Figure 34. ).
In the 2Level SMF window is presented a listbox which contains one line for each action of the provided
set. For each not scheduled action, if it isnt scheduled, the line contains:
<actionname>;
while for each scheduled action the line contains:
<actionname> <scheduledtime>.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 34. Show Scheduling Time window.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
67 / 96
7.1.4 Cancel Scheduling Time
This function allows the operator to cancel the time scheduled for the selected action.
SEQUENCE
a)
b)

From the Periodic Actions window select the Cancel Scheduling Time option and confirm by pressing
OK. The Cancel Scheduling Time window opens (See Figure 35. ).
In the 2Level SMF window is presented a listbox, which:
if there is not any scheduled action, contains the message:

No Periodic Actions scheduled;
if there are scheduled actions, contains a line for each one, indicating
<actionname> <schedulingtime>.:
Figure 35. Cancel Scheduling Time window
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
The Header Area presents the function name: Cancel Scheduling Time;
1 listbox for actions. The list is equipped of an header indicating the composition of items line:
Action
Time:mm hh ddW ddM;
2 Buttons: Unset to remove the scheduled time for the selected action, Close to close the
window and return to the Main.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
68 / 96

SCOPE
8 BACKUP/RESTORE

It is recommended to perform a backup everytime a topology is modified.
8.1 Introduction
8.1.1 Subsystems and Data Types
Entities belonging to management layers which needs to be backed up are called subsystems, e.g.:
from the eml point of view, each workstation belonging to a 1353SH installation, is a subsystem;
from the snml point of view, each workstation belonging to a 1353SH installation, is a subsystem;
from the snml point of view, its own databases subtree is a subsystem;
from the nnml point of view, its own databases subtree is a subsystem;
Backup and restore procedures operate on a set of subsystems; however, if required, they can operate
on a subset.
Several data types make up a complete subsystem backup/restore. Recommended set of data type is:
a)
b)
c)
d)
e)
f)
Network:
OSconfig:
PM:
Operator:
Alarms:
Log:
network;
operating system data relative to application sphere;
performance monitoring;
operators;
alarms;
applications activity messages.
The SMF function interface gives the possibility to select all or a subset of data types (max. 10), for each
subsystem to backup/restore.
In restore configuration phase, the functionality is able to read the data type set from the data to restore
contents and to give the possibility to restore subtypes for each data type (max.10 different subtypes for
each data type).
1AA 00014 0004 (9007) A4 ALICE 04.10
Subsystem and data type concepts can be briefly summarized:

a)
the smallest entity which can be backed up has the format:

<subsystem><datatype>;
b)
the smallest entity which can be restored has the format:

<subsystem><datatype>[<subtype>];
c)
the operator starts procedures after a phase in which determines a backup or restore configuration,
selecting subsystems on which to operate and the subset of data types for each subsystem.
The following list is an example of backup (or restore) configuration:
snmlNetwork
snmlPM
snmlAlarms
snmlUS1Network
snmlUS1PM
snmlUS1Alarms
eml1MasterOSconfig
eml1MasterOperators
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
69 / 96
The directory /backup is fixed as root of the directory structure designed for backup and restore
operations.
It has a dynamic structure, which is removed and created at each backup/restore procedure start. The
structure depends on the backup/restore configuration.
The following figure shows the /backup subtree structure on a 1354RM after a backup procedure based
on backup configuration given as example in par.8.1.1.
/backup
snml
Ntwk
PM
snmlUS1
Ntwk
Alarms
PM
eml1Master
Alarms
OScfg
<Ntwk>.tar
Oper
<Ntwk>.tar
<PM>.tar
<Oper>.tar
<PM>.tar
INFO
<Alarms>.tar
<Alarms>.tar
<OScfg>.tar
INFO
Figure 36. Example of Backup subtree structure on 1354RM.
8.1.3 Using a Magnetic Tape

Backup/Restore procedure write/read data to/from a magnetic tape. The following has to be taken into
account:
a)
only one backup file for each magnetic tape is expected;
b)
an environment variable which specifies the host to which the tape is connected, is defined at product
installation time as
TAPE_SERVER;
c)
the device used is: /dev/rmt/0m;
d)
when executing operations on tape, both backup and restore use a timeout in order to manage
device detection. The procedures evaluate the timeout value taking into account the following va
riables:
TAPE_TRANSFER_RATE: default value is fixed to 300 Kbytes/sec.;
1AA 00014 0004 (9007) A4 ALICE 04.10
TAPE_ACCESS_TIME: the device location has to be taken into account and the possible delay
might be due to the network usage.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
70 / 96

8.1.2 Operation Area on disk
8.1.4 Backup

SCOPE
This function allows the operator to execute the backup of a set of <subsystem><datatype> items
configured by the operator.
SEQUENCE
a)
b)
Select the Backup & Restore option and confirm by pressing OK.
Select the Backup option and confirm by pressing OK.
The Backup selection window opens.
TapeCopy
Figure 37. Backup window
1AA 00014 0004 (9007) A4 ALICE 04.10
The Header Area presents the function name: Backup;

1 listbox for product available subsystems set;
1 listbox for <subsystem><datatype> items to backup;
5 checkbuttons: one for each data type;
1 button: Supported data types . It is enabled only if a single subsystem is selected from
the available list, and automatically put on/off the checkbuttons depending on backup
procedures availability for that subsystem;
2 buttons: right and left angle brackets to put/take away items into/from to backup list;
2 buttons: Add All to put directly items relative to all subsystems in the list into to backup
list depending on data types put on checkbuttons; Remove All to clear the to backup list;
1 switchbutton: Disk/Disk&Tape to establish backup destination;
2 buttons: Close to close the functionality and Start to launch procedures.
To enable Start button the operator has to put at least one item into To Backup list.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
71 / 96
c)
d)
into the list of To Backup are put only the available items <subsystem><datatype>;
a diagnostic window is displayed, giving a warning message for each not provided item.The
possibility that a lot of messages have to be given is very high: so it would be better to maintain the
list of requested but excluded items until the operator exits from backup functionality or builds a new
backup configuration or forces the closure using the Motif frame menu of the diagnostic window.
Select the OSs to be backed up and the Backup option (Network, Operator, .....) and confirm by
pressing Start. A System Message alerts: Network backup started, configuration functions not
available. The Backup monitoring window is presented (See Figure 38. ).
On start request a subwindow, shown in the following figure, is opened. By this window the operator
is able to monitor backup procedure progress and execute an abort operation, if necessary.
Figure 38. Backup execution subwindow
The Header Area presents the function name: Backup execution;

1 progress bar;
2 labels: Estimated Time and Elapsed Time with relative values;
1 button: Abort to stop execution.
An area sideways to the label Estimated time indicates to the user a fixed time estimated for the complete
backup to be performed.
An area sideways to the label Elapsed time indicates the time elapsed from the beginning of the backup,
updating the value second by second.
1AA 00014 0004 (9007) A4 ALICE 04.10
e)
At the end of the backup phase from subsystems to the disk area, an information window is opened
to inform the operator on procedure completion and its result. After operator acknowledgment, the
information window and the subwindow are simultaneously closed.
If the Disk&Tape option was selected, the procedure continues performing the saving backup data on
tape action, as described forward in this chapter.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
72 / 96

Configuring a backup can cause the following: the operator switches on a set of data types, then selects
a set of subsystems from the Available list and puts into To Backup, but some subsystems do not provide
one or more of the selected data types.
In this case the following behaviours are expected:
8.1.4.1 Handling Backup Execution Failure

The following cases are managed:

a)
if m<n commands fail, for each one of the m items, at the end of the parallel procedure a warning
window is opened indicating the item and its procedure result: the operator has to acknowledge to
close the window by means of a confirmation button. After operator acknowledgment of the last
warning window, this one and the subwindow are simultaneously closed.
b)
if all of n commands fail, the Backup procedure is interrupted and an information window is opened
to inform the operator that the configured backup execution is totally failed. After operator
acknowledgment, the information window and the subwindow are simultaneously closed.
8.1.4.2 Saving on Tape subwindow

After the Backup execution, if Disk&Tape option was selected, the subwindow shown in the following
figure is opened.
Figure 39. Saving on Tape subwindow

The subwindow appearance and behaviour is the same as that described for the Backup execution
subwindow, with only one exception in the label for Header Area, that is:
the Header Area presents the function name: Saving data on Tape;
1AA 00014 0004 (9007) A4 ALICE 04.10
At the end of the saving phase from disk area to tape, an information window is opened to inform the
operator on procedure completion and its result. After operator acknowledgment, the information window
and the subwindow are simultaneously closed.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
73 / 96
During saving on tape backup data procedure, if errors occur using tape, a warning window gives the
operator a message and the possibility to retry or abandon the operation. If the operator choses to
abandon, the information window and the subwindow are simultaneously closed.
8.1.4.4 Timeout
An environment variable is defined. It gives, in seconds, the timeout value for backup operations:
BCK_RES_TIMEOUT.
If the variable is not assigned, is adopted a default value fixed to 7200 seconds.
8.1.4.5 Periodic Action reference
In NML products a backup procedure is provided. It is called periodic action. It differs from the Backup
described in this chapter, since it backups Network data type only, related to subsystem of IM WS
installation.
1AA 00014 0004 (9007) A4 ALICE 04.10
An implementation requirement is to achieve a unique Backup procedure which is possible to launch

whether as graphical SMF or as periodic action in background without display.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
74 / 96

8.1.4.3 Handling Save on tape Failure
8.1.5 Restore

SCOPE
This function allows the operator to restore a set of <subsystem><datatype> items available from a given
backup file.
SEQUENCE
a)
b)
c)
d)
e)
f)
Select the Restore option and confirm by pressing OK.
Shutdown the 1354RM and 1353SH processes involved.
Select the Restore option and confirm by pressing OK. The Restore window is presented (See
Figure 40. ).
Start the Restore procedure. The Monitoring window appears. A message indicating that the Backup
is being started is presented on the 1353SH screens.
When the Backup is terminated a message indicating Restore procedure successfully completed
is displayed.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 40. Restore window
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
75 / 96
The Header Area presents the function name: Restore;
1 listbox for available <subsystem><datatype> items;

1 listbox for <subsystem><datatype> items to restore;
1 button: Show Info . It is enabled only if a single item is selected from the available list and
if exist an information file for that item; it visualize, on request, the content of the file; when the
file is not provided, the button becomes disabled.
2 buttons: right and left angle brackets to put/take away items into/from to Restore list;
2 buttons: Add All to put directly all available items into to Restore list; Remove All to
clear the to Restore list;
1 switchbutton: Disk/Tape to establish where are located data to restore;
1 button: Show Status to visualize detailed informations about data to Restore contents;
1 button: Load to copy backup data from tape to disk;
2 buttons: Close, to close functionality, and Start to activate the parallel restore
procedure;
As default, on window opening, the option Tape is switched on, the Load button is enabled, the Show
Status button is enabled and the Start button is disabled; the operator can control data to
Restore status pressing the relative button, and/or enable the Start executing two steps:
a)
b)
switching on Disk or executing the loading action,

and putting at least one item into To Restore list.
8.1.5.1 Redo Log

1)
From the File Manager position on the directory Mirror. The last redo file is 1354RM.redo.
2)
Execute:
File: Copy with extension . rmCmd
and then click on OK.
A new icon, distinguished by the acronym RM is presented.
3)
Select this icon and then select the popup menu RM exec
A COMMAND MODE INTERPRETER dialog window is displayed.
Select YES. Redo is performed as regards the paths, trails and the payload changes that have
been made following the last backup operation.
8.1.5.2 Exclusive procedures management
1AA 00014 0004 (9007) A4 ALICE 04.10
Some data types cannot be restored in parallel with other data types. Restore procedures relative to such
data types are considered exclusive; i.e. they have to be managed individually.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
76 / 96

The following is a description of the Restore window.

8.1.5.3 Status subwindow

It shows data to Restore status related whether to tape or to disk area, depending on switch button state.
Only one backup file for each magnetic tape is expected.
Figure 41. Status subwindow
The subwindow is organized to give relevant information about data to Restore, that is
a)
b)
c)
date & time creation of the Backup file;

data to Restore composition, that is <subsystem><datatype> item list;
for each item, the status at backup procedure completion.
The Header Area presents the function name: Restore data Status;
1 label, giving the date and time of backup file creation;
1 listbox, unselectable, which contains the list of <subsystem><datatype> items which

compose backup data. The list is equipped of an header indicating the line contents:
Subsystem
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Data Type
status
1 button: Back to come back to previous level.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
77 / 96
When selected a <subsystem><datatype> item from Available list, if subtypes are provided for it , at put
action time (operator push >), a subwindow is displayed for subtypes configuration. As default, all
subtypes are selected (check buttons ON): the operator can deselect subtypes in order to restore a subset
of the <subsystem><datatype> data. Following figure shows the subtypes subwindows.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 42. Subtypes subwindow
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
78 / 96

8.1.5.4 Subtypes Selection subwindow

8.1.5.5 Loading from Tape subwindow

On load request a subwindow, shown in the following figure, is opened. By this window the operator is able
to monitor loading procedure progress and execute an abort operation if necessary.
Figure 43. Load data from Tape subwindow
The Header Area presents the function name: Loading data from Tape;
1 progress bar;
An area sideways to the label Estimated time indicates to the user a fixed time estimated for the complete
load to be performed.
An area sideways to the label Elapsed time indicates the time elapsed from the beginning of the load,
At the end of the load phase from tape to disk area, an information window is opened to inform about
operation completion and its result: after operator acknowledgment the information window and the
subwindow are simultaneously closed.
8.1.5.6 Handling Load from Tape Failure
1AA 00014 0004 (9007) A4 ALICE 04.10
During loading from tape procedure, if errors occur using tape a warning window give to the operator a
message and the possibility to retry or abandon the operation. If the operator choses to abandon, the
warning window and the subwindow are simultaneously closed.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
79 / 96
On start request a subwindow, shown in the following figure, is opened. By this window the operator is able
to monitor restore procedure progress and execute an abort operation if necessary.
Figure 44. Restore execution subwindow

Follows a description of the subwindow appearance and behaviour.
The Header Area presents the function name: Restoring data from disk;
1 progress bar;
An area sideways to the label Estimated time indicates to the user a static time value estimated for the
complete Restore to be performed.
An area sideways to the label Elapsed time indicates the time elapsed from the Restore beginning,
1AA 00014 0004 (9007) A4 ALICE 04.10
At the end of the Restore procedure, an information window is opened to inform about operation
completion and its result: after operator acknowledgment the information window and the subwindow are
simultaneously closed.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
80 / 96

8.1.5.7 Restore subwindow
8.1.5.8 Handling Restore Commands Failure
1AA 00014 0004 (9007) A4 ALICE 04.10

During Restore procedure phase, parallel restore commands are executed (lets suppose n):
a)
if m<n commands fail, for each one of the m items, at the end of parallel procedure, a warning window
is opened indicating the item and its procedure result: the operator has to acknowledge by means
of a confirmation button to close the window. After operator acknowledgment of the last warning
window, this one and the subwindow are simultaneously closed.
b)
if all of n commands fail, the Restore procedure is interrupted and a warning window is opened to
inform the operator that the configured Restore execution is totally failed. After operator
acknowledgment, the warning window and the subwindow are simultaneously closed.
8.1.5.9 Timeout
The same environment variable specified in par.8.1.4.4 is used to give, in seconds, the timeout value for
restore operations.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
81 / 96
8.1.6 Remotization Enable/Disable

SCOPE
This function allows to enable or disable the copy of the backup data to the remote server.
SEQUENCE
a)
b)
c)

Select the Remotization Enable/Disable option. A dialog window is presented. See Figure 45.
Figure 45. Remotization Enable/Disable window.

If Remotization Actual state is Enabled, the allowed option is Disable ( lefthand side of the dialog box )
1AA 00014 0004 (9007) A4 ALICE 04.10
If Remotization Actual state is Disabled, the allowed option is Enable.
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
82 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10

9 SYSTEM START/STOP
9.1 Introduction
This feature provides some functions for product activity management, local to the SMF application
running machine.
9.1.1 Launching by command line
It is also possible to start or stop the system, launching the command on line using the following command
and syntax:
StartStop {START|STOP} [{sys|subsys}{system_name}]
E.g.:
StartStop Start
StartStop Stop sys
StartStop Start subsys system_name
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
83 / 96
9.1.2 Start System
This function allows the Administrator to start the 1354RM system.

SEQUENCE
a)
Select the SMF icon from the vertical palette
b)
Select the System Start/Stop option and confirm by pressing OK.
c)
The System Start/Stop window is presented.
d)
Select the Start System option and confirm by clicking on OK.

The system starts running and the Startup procedure presents a dialog box (See Figure 46. ).
Figure 46. Start System window
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
The Header Area presents the function name: Start System;

1 scrollable text area to display starting operation messages;
2 Buttons: Start to start the system, Close to close the window and return to the Main.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
84 / 96

SCOPE
9.1.3 Stop System

SCOPE
This function allows the Administrator to stop the 1354RM system.
SEQUENCE
a)
b)
c)

Select the Stop System option.
The system starts running the shutdown procedure and presents the window of Figure 47.
Figure 47. Stop System window
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
The Header Area presents the function name: Stop System;

1 scrollable text area to display stopping operation messages;
2 Buttons: Stop to stop the system, Close to close the window and return to the Main.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
85 / 96
9.1.4 Show System Status

SCOPE
This function allows the Administrator to view the current system state.
SEQUENCE
a)
b)
c)

Select the Show System Status option.
The dialog box of Figure 48. is presented.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 48. Show System status window
The Header Area presents the function name: Show System Status;
ED
1 label, indicating the current state: Current state: Disabled/Enabled;
1 Button: Close to close the window and return to the Main.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
86 / 96
9.1.5 Autostart Enable/Disable

SCOPE
This function allows the Administrator to put On/Off the system Autostart as startup option.
SEQUENCE
a)
b)
c)

Select option Autostart Enable/Disable. The dialog box of Figure 49. is presented.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 49. Autostart Enable/Disable window
The Header Area presents the function name: Autostart Enable/Disable;
ED
1 label, indicating the current state: Current state: Disabled/Enabled;
2 Buttons: Enable/Disable to put Autostart on/off, Close to close the window and return
to the Main.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
87 / 96
9.1.6 Show Autostart Status

SCOPE
This function allows the Administrator to view the current system Autostart state.
SEQUENCE
a)
b)
c)

The System Start/Stop window is presented.
Select option Show Autostart status. The dialog box of Figure 50. is presented.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 50. Show Autostart status window
The Header Area presents the function name: Show Autostart Status;
ED
1 label, indicating the current state: Actual state: Disabled/Enabled;
1 Button: Close to close the window and return to the Main.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
88 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10

9.1.7 Process Monitoring Control
Refer to Chapter Process Monitor of the Handbook Maintenance
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
89 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
90 / 96

10 TRACE ADMINISTRATION
10.1 Introduction
The following files are generated by the 1354RM products:
a)
b)
c)
d)
e)
f)
g)
Oracle Archive files, referenced as DB (data base);

HPOV event log file, referenced as Event;
AS 1330 log file, referenced as AS;
1354RM/1354NN agents log files, referenced as AgL (Agent Logs);
1354RM/1354NN agents trace files, referenced as AgT (Agent Traces);
System Management functionalities Log file, referenced as SML;
OS log files (of succ./unsucc. login activity), referenced as OS.
The action on empty files is called Clean files.

The procedures which perform clean actions execute a file saving before any operation; this is called Save
files.
Oracle Archive files are saved during data base automaticbackup phase. In this case only a clean action
is provided.
10.2 Cleaning files

The 1354RM provides the possibility to clean files by means of:
1)
2)
periodic action procedures

SMF graphical function.
The following table explains which files are treated by periodic action (P.A.) procedures and which by SMF.
Table 4. Procedures for Log and Trace management
Function/Procedure Name
Run as
SMF
1AA 00014 0004 (9007) A4 ALICE 04.10
Purge Trace Files
P.A.
Save and Clean Event Log
Clean Data Base Archives
01
DB
Event
Save and Clean Log&Trace Files
ED
Files Treated
AS
AgL
AgT
SML
OS
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
91 / 96
10.3 Purge Trace Files
This function allows the operator to clean some relevant log and trace files produced during the product
activity. Files treated are shown in para 10.2 Table 4.
SEQUENCE
a)
b)
c)
Select the SMF icon from the vertical palette confirm by pressing OK.
Select option Trace Administration and confirm by selecting OK.
Select option Purge Trace Files and confirm by selecting OK. The dialog box of Figure 51. is
presented.
Figure 51. Purge Log&Trace Files window
The Header Area presents the function name: Purge Log&Trace Files;
1 Slide, with label: Max Size KB; it give the possibility to establish the maximum size
threshold into a range since 10 up to 1000 KB;
4 Checkbuttons, one for each file subset, with the following labels:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Agent Logs, for Log files of product s Agents;

Agent Traces, for Trace files of product s Agents;
Alarms Log, for Log file of AS 1330 application;
System Log, for System Management and OS Log files.
the Button: Apply to execute the clean, Close to close the window and return to the Main.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
92 / 96

SCOPE
1AA 00014 0004 (9007) A4 ALICE 04.10

10.3.1 Periodic Action reference

It is provided a procedure, Save and Clean Log&Trace files, which is called as periodic action (par7). It
is different from the one specified in this chapter, because of following characteristics:
a)
b)
ED
it works on *.log/*.trc files, related to Agents only;

maximum size threshold, fixed to 1000 blocks (512 Kbyte), is not configurable.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
93 / 96
10.4 Dump Log and Trace Files
This function allows execute a dump to tape operation of the Log and Trace Files.
SEQUENCE
a)
b)
c)
d)
Select the SMF icon from the vertical palette confirm by pressing OK.
Select option Trace Administration and confirm by selecting OK.
Select option Dump Log and Trace Files and confirm by selecting OK. The relevant dialog box of
is presented. ( See Figure 52. )
If you click on button Copy , the dump operation will start. The monitoring of the inprogress transfer
is available on a separate window.
Figure 52. Dump Log and Trace Files.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
The tape address is contained in the environment variable tape_server.
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
94 / 96

SCOPE
INDEX

SPACES
Archived System Messages, 63
O
Operators, 13
Access Rules, 27
Add Operator, 19
Autostart, 87
PERIODIC ACTIONS, 65
R
Remove Operator, 21
B
BACKUP/RESTORE, 69
C
Change Initiator, 24
Change Password, 22
E
Embedded Rules, 33
S
Scheduling Time, 65
Show Autostart, 88
Start System, 84
Stop System, 85
SYSTEM LOG, 61
System Management Features, 7
System Messages, 61
System Status, 86
User Profiles, 26
Initiators, 25
1AA 00014 0004 (9007) A4 ALICE 04.10
NAD, 24
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
95 / 96
1AA 00014 0004 (9007) A4 ALICE 04.10
END OF DOCUMENT
ED
01
SC.8:SMF
957.130.872 H
3AL 61259 AA AA
96
96 / 96

1354rm52b Manual Del Operador Vol 2

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

1354rm52b Manual Del Operador Vol 2

Enviado por

Direitos autorais:

Formatos disponíveis

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

All rights reserved. Passing on and copying of this