1353sh Administracion

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.932
V Ed.01 3AL 71807 AAAA Ed.01
1300NM
1353SH Rel.5.3
ADMINISTRATION GUIDE
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)
No PAGINE TOTALI PER ARCHIVIAZIONE: 360

DIMENSIONE BINDER SORGENTE (du ks): 179.153 kBytes
INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS
STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING
COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

HANDBOOK COMPOSITION AND ASSEMBLY:
No pagine
(facciate)
No pages
numerate
numbered
da from
a to
1/354
354/354
TARGHETTE - LABELS
957.130.932 V Ed.01
3AL 71807 AAAA Ed.01
frontespizio
front
manuale
manual
354
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES:
356
TOTALE FOGLI A4 TOTAL A4 SHEETS:
178
WARNING FOR A-UNITS OTHER THAN A-ITALY
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Labels are done according to A-Italy binder format.

Source files: ALICE 6.10 ARCHIVED BY GAPI 3.9.1
01
RELEASED
957.130.932 V
3AL 71807 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
Originators
L.Pilotti
1353SH 5.3
Domain
Division
Rubric
Type
Distribution Codes
:
:
:
:
TND
1353SH 5.3 ADMINISTRATION GUIDE

Internal :
External
Approvals
Name
App.
V.Scortecci
F.PASTENA
Name
App.
INFORMAZIONI EDITORIALI
ORIGINALE SU FILE: ALICE 6.10
sistemazione figlist
957.130.932 V
3AL 71807 AAAA
Ed.01
1300NM
1353SH Rel.5.3
1AA 00014 0004 (9007) A4 ALICE 04.10
Element Manager for SDH and Optical Networks

ED
01
RELEASED
957.130.932 V

4
2/ 4

1300NM
1353SH Rel.5.3
957.130.932 V Ed.01
VOL.1/1
1300NM
1353SH Rel.5.3
957.130.932 V Ed.01
VOL.1/1
1300NM
1353SH Rel.5.3
957.130.932 V Ed.01
957.130.932 V Ed.01

VOL.1/1
1300NM 1353SH Rel.5.3

VOL.1/1
1300NM
1353SH Rel.5.3
1AA 00014 0004 (9007) A4 ALICE 04.10
957.130.932 V Ed.01
ED
01
VOL.1/1
RELEASED
957.130.932 V

4
3/ 4
1AA 00014 0004 (9007) A4 ALICE 04.10
FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT
ED
01
RELEASED
957.130.932 V
4/ 4
Administration Guide
Alcatel 1300NM
Network Management
1353SH Rel.5.3
957.130.932 V Ed.01
957.130.932 V Ed.01
1AA 00014 0004 (9007) A4 ALICE 04.10

1353 SH REL.5.3 ADMINISTRATION GUIDE
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
REFERENCED DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
GLOSSARY / TERMINOLOGY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
PREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Product-release handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1 Handbooks related to the specific software application 1353SH Rel.5.3 Version 5.3.0
1.3.2 NR 5.0B related handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.3 Handbooks related to the products hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Purpose of the Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6 Document Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
17
17
18
18
19
19
20
20
20
2 GENERALITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Role of the Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 System Management Notions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 General Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2 Presentation Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Defence Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1 General Processes Defence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2 Third Party Product Process failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25
25
26
27
27
29
29
31
34
3 RELEASE IDENTIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
4 WORKSTATION SHUTDOWN OR POWERUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43
5 MAINTENANCE GENERALITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
01
001120
ED
DATE
CHANGE NOTE
F.Pastena
V.Scortecci
L.Pilotti
APPRAISAL AUTHORITY
ORIGINATOR
1353 SH Rel.5.3
ED
01
957.130.932 V

0
1 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

6 DISKS FULL BACKUP AND FULL RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
7 OPERATOR MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 SEC Administration Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.1 The access control model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.2 Object Access Domains (OADs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.3 Functional Access Domains (FADs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.4 Define a new User Profile using ACA graphical tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5 Create a new Access Control Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.6 General SEC behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.7 EmlUsm Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.8 Q3 FADs configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.9 QB3* FADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.10 RM constraints FADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3 Forced Logout Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4 List Current Login Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5 List Unsuccessful Login Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.6 List Successful Login Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.7 List Operators Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.8 Add Operator Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.9 Remove Operator Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.10 Change Password Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.11 Set Max Operators Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.12 Set Personal Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
50
51
51
53
53
54
60
60
63
65
81
86
87
89
90
91
92
93
95
96
97
98
8 SYSTEM TRACE & LOG MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1 SMF/Command/Event Logs Management/Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.2 Management of log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.3 Access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.4 Log Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.5 SMF/Command/Event Logs Management (User Interface) . . . . . . . . . . . . . . . . . . . . . . . .
8.1.6 SMF/Command/Event Logs Visualization (User Interface) . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Failure Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.2 Fault Report Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.3 Sequence of events when a process exits abnormally . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.4 Failure Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2.5 Failure Management (User Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3 Trace Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.1 Traces Management tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.2 Trace Management (User Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.3 Traces visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.4 Traces saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4 Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.2 Cleanup tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.3 Cleanup (User Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.4 Cron actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5 Dump Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5.1 Open option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5.2 Capture option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5.3 Quit option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
99
99
99
99
101
101
102
109
110
110
110
110
111
111
114
114
114
118
121
122
122
122
122
124
125
125
126
127
ED
01
957.130.932 V

0
2 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

9 BACKUP/RESTORE FEATURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2 Workstation distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3 Destination selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.4 Backup tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 Backup/Restore (User interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.1 Access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3 Backup Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4 Restore Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.1 Main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.2 PM data type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.3 Exclusive option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.4 Restore in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.5 PostOperations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5 Remotization Enable/Disable Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
129
129
129
129
131
131
133
133
133
135
138
138
140
141
141
142
144
10 SYSTEM MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1 Stack Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.1 System Management Stack Configuration Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.2 MultiStack configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.3 Using multiple Lan interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 Process Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.1 Main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.2 Processes menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.3 Eml processes creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.4 Workstations configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 Process Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.1 Access to the commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.2 Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.3 Console & New Term . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.4 Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.5 System Defence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.6 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4 System Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5 On Board Simulator Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.6 Broadcast message to users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.7 HPOV Failure on a workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
145
147
147
151
154
156
157
158
159
159
161
161
164
167
168
171
175
176
178
180
181
11 LOCAL DATA MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.1 Access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.2 Choosing a NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.3 Interactions with the OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.4 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.5 User Interface parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 Diagnosis of audit of the MIB Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.4 Display SEN MIB Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5 NECTAS Decoding Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6 NECTAS Comparison Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7 Upload Failure Diagnosis Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.8 Enable RPS Switch Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
183
183
185
185
185
185
186
186
187
190
191
194
197
198
ED
01
957.130.932 V

0
3 / 354
221
223
224
224
226
230
235
236
237
12 PERIODIC ACTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.1 Access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2 Add a scheduled action Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3 View scheduled actions Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.4 Remove a scheduled action Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
239
239
239
240
244
245
13 1641SX MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.1 NE/AU Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.1.1 Access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.1.2 NE/AU Selection dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2 AU Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2.1 AU Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2.2 View files on AU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2.3 Protocol Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3 Trasmission Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.1 Matrix Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.2 Configuration Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.3 List of all timescheduled connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4 Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5 Data Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5.1 Export PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5.2 Export FMCAT Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5.3 Export RI Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6 Software DownLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.7 AckStationAlarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
247
247
247
248
250
251
253
255
256
257
259
260
261
262
263
265
265
266
267
14 REMOTE MAINTENANCE IN SH5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.1 Introduction to GoGlobal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.2 GOGlobal Connections creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
269
269
270
1AA 00014 0004 (9007) A4 ALICE 04.10

11.9 Software download manager configuration Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.10 Software download server configuration Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.10.1 Install a new package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.10.2 Delete a package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.10.3 Display SWP Descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.10.4 Check SWP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.11 Save TP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.12 Restart Perf Collect Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.13 Overhead byte Configuration Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.14 LAPD Configuration Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.15 Change ASAP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.16 Sync Source Selection Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.17 Address Configuration Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.18 Change Assigned To Observed and Change Free or Observed To Assigned
Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.19 Switch Old/New Practice Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.20 Set offline board and set offline signal label option . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.20.1 Set offline board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.20.2 Set offline Signal label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.21 Ping NE Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.22 List Gateway NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.23 DXC TCPIP Address Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.24 Change User Label Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
199
201
201
202
203
205
206
207
208
211
214
216
218
01
957.130.932 V

0
4 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

14.2.1 Creating a new generic connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.2.2 Completing the connection with log in phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.2.3 Creating a new connection with automatic login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3 GOGlobal connection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3.1 Opening a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3.2 Editing a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3.3 Exiting a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
270
271
272
274
274
275
277
15 NETWORK TIME PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.1 NTP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.1 NTP implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.2 NTP daemon and configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.3 The driftfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.4 Other options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.5 Synchronization schemes and reference principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.2 NTP configuration procedure in 1353 SH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.2.1 1353 SH (HPUX Rel. 10.20) NTP configuration files. . . . . . . . . . . . . . . . . . . . . . . . . . .
15.2.2 DXC (System V Unix version 3) NTP configuration files. . . . . . . . . . . . . . . . . . . . . . . . . .
15.2.3 1353 SH System Administration script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
279
279
279
280
281
281
282
284
284
284
285
16 ALCATEL NETWORK TIME PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.1.1 ANTP behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.1.2 RTC distribution system architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2 ANTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
287
287
287
287
289
17 PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1 Preventive Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2 Corrective Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.3 Failure management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.4 Maintenance operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.5 Upload failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.6 Advanced network management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
291
291
295
303
305
309
313
320
APPENDIX A : EXAMPLE OF AN AXCONFIG FILE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
333
APPENDIX B : EXAMPLE OF A PARAM.CFG FILE FOR AN EMLIM. . . . . . . . . . . . . . . . . . . . . . .
337
APPENDIX C : EXAMPLE OF A PARAM.CFG FILE FOR PERFSTORAGE. . . . . . . . . . . . . . . . . .
341
APPENDIX D : EXAMPLE OF A FAILURE_HANDLER.CFG FILE. . . . . . . . . . . . . . . . . . . . . . . . . .
343
APPENDIX E : EXAMPLE OF A TRACE.CFG FILE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
345
APPENDIX F : EXAMPLE OF AN CLEANUP.CFG FILE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
347
APPENDIX G : NTP CONFIGURATION EXAMPLES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
349
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
353
ED
01
957.130.932 V

0
5 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

LIST OF FIGURES AND TABLES

FIGURES
Figure 1. Process failure (example 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. Process failure (example 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. General process automatic restart diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Automatic restart after HP OV failure diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Example of typed unix shell commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. Example of the system response to the command date. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. Access to the 1353SH System Management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Starting the SMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. Successive menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Examples of error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. SMF main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. 1353SH version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. Release folder of the Administration toolbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. Operators Administration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. ACA interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Object Access Domain creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Elementary Object creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Object Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. Default Function Access Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Create/Modify a new Function Access Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. OADFAD Combination creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Modify the NE ACD value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. Relation between the User Name and the EmlUsmSH5 profile . . . . . . . . . . . . . . . . . . . . .
Figure 24. Forced Logout Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Details of user processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. List Current Login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. List Unsuccessful Login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. Successful logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. List the users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. Create user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Remove an user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. Change of users password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. Set max operators number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. Set Default Printer window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. Logs states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. Logs Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. System Logs visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Event/Command Logs visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. View Logs Show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. View Logs 1000 records excedeed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. View Logs Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. View Logs Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. View Logs Save As . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. View Logs Analyzed fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. Move log to save area option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. Delete logs option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 47. Failure Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 48. Failure Management Capture Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 49. Failure Management Manage Failure Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 50. Trace Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 51. Trace Management Change Trace Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 52. Trace Management Change Trace Level Confirmation . . . . . . . . . . . . . . . . . . . . . . . .
ED
27
28
30
32
34
34
35
35
36
36
37
39
40
49
51
54
55
56
57
58
59
61
63
87
88
89
90
91
92
94
95
96
97
98
100
102
103
103
104
105
105
106
107
107
108
109
111
112
113
114
116
117
01
957.130.932 V

355
6 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 53. Trace Management Reset Cyclic Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 54. Trace Management Reset Cyclic Traces Confirmation . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 55. Trace visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 56. Trace visualization Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 57. Search in Trace file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 58. View of the trace file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 59. Software download trace file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 60. Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 61. Cleanup Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 62. Cleanup Clean Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 63. Cleanup Clean Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 64. Dump Screen window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 65. Dump Screen window Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 66. Dump Screen window Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 67. Dump Screen window Select Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 68. Backup operation on distributed workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 69. Restore operation on distributed workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 70. Destination selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 71. Backup tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 72. Backup/Restore window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 73. Backup operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 74. Backup in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 75. Backup completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 76. Restore window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 77. Show status pushbutton . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 78. Show info pushbutton . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 79. PM data subtypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 80. Warning window for exclusive data type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 81. Starting restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 82. Restore in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 83. Restore operation completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 84. Restore Compare MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 85. Remotization Enable/Disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 86. System Management Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 87. Stack Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 88. Retix Stack Configuration Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 89. Retix Stack Configuration Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 90. Multistack first window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 91. IP address configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 92. Add address alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 93. Process configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 94. Main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 95. Set XCC Hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 96. Processes menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 97. Update configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 98. Workstations icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 99. WS and Processes, list and status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 100. Sub menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 101. Startup in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 102. SH Console Startup in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 103. 1353SH startup on a WS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 104. New SDH Manager window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 105. Console window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 106. Stop in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 107. SH Console Stop in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 108. SDH Manager Stopping a workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
117
117
118
119
119
120
121
123
123
124
124
125
125
126
127
130
130
131
132
133
135
136
137
138
139
140
140
141
141
142
142
143
144
145
147
148
149
152
153
154
156
158
158
159
160
161
162
163
164
165
166
167
167
168
169
170
01
957.130.932 V

355
7 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 109. SDH Manager General process stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 110. Process Monitoring 1353SH menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 111. Defence mode change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 112. Handling process failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 113. General process restart procedure. Console information. . . . . . . . . . . . . . . . . . . . . . . . .
Figure 114. 1353SH status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 115. System Shutdown window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 116. On Board Simulator Monitoring window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 119. Message Broadcast dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 120. Workstation failure SH processes failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 121. Workstation failure Fault configurations Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 122. Workstation failure Fault configurations Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 123. Menu of Local Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 124. Choosing a NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 125. System stop confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 126. Diagnosis of audit of the MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 127. MIBs differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 128. Pulldown menus of the MIBs differences window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 129. Find dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 130. Searching occurences in the MIBs differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 131. Display SEN MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 132. SEN MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 133. NECTAS Decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 134. NECTAS Decoding Show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 135. NECTAS Decoding Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 136. Encode operation confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 137. Encode System stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 138. NECTAS Comparison (first NE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 139. NECTAS Comparison (second NE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 140. NECTAS Comparison Result (no differences) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 141. NECTAS Comparison Differences displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 142. NECTAS Comparison File saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 143. Upload Diagnosis Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 144. Upload Diagnosis Failure Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 145. Enable RPS Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 146. Enable RPS Switch Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 147. Software Download Manager Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 148. Add new version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 149. Software download server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 150. Package installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 151. Selection of the package to delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 152. Package deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 153. Selection of the descriptor to display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 154. Display of descriptor file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 155. Selection of the package to display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 156. SWP check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 157. Save TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 158. Restart Perf Collect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 159. Restart Perf Collect Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 160. Overhead byte configuration option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 161. Overhead byte configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 162. LAPD configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 163. LAPD configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 164. Change ASAP window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
170
171
171
172
174
175
176
178
178
179
180
181
182
182
183
185
186
187
188
188
188
189
190
190
191
192
192
193
193
194
194
195
195
196
197
197
198
198
199
200
201
201
203
203
204
204
205
205
206
207
207
208
209
211
212
214
01
957.130.932 V

355
8 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 165. Change ASAP window NE source selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 166. Change ASAP window Getting ASAP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 167. Change ASAP window Work in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 168. Sync Source Selection Choosing a NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 169. Sync Source Selection Selecting the synchronization source . . . . . . . . . . . . . . . . . . .
Figure 170. Sync Source Selection Choosing the SSU quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 171. Address Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 172. Address Configuration NE source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 173. Address Configuration Initialisation on going . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 174. Address Configuration Addresses setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 175. Change assigned to observed window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 176. Change state operation running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 177. Switch Old/New Practice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 178. Switch Old/New Practice confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 179. Set Offline Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 180. Ne Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 181. Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 182. Ne selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 183. Current setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 184. New setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 185. Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 186. Ping NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 187. Ping NE Add by supervision area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 188. Ping NE Add by supervision area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 189. Ping NE Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 190. List Gateway NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 191. 1641SX TCPIP Address Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 192. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 194. Periodic Actions Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 195. Set Scheduling Time Window (step 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 198. Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 199. Show Scheduling Time Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 200. Cancel Scheduling Time Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 201. Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 202. 1441SX main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 203. 1641SX Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 204. 1641SX Maintenance Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 205. 1641SX AU services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 206. 1641SX View files on AU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 207. 1641SX Protocol Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 208. 1641SX Trasmission Maintenance Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 209. 1641SX Matrix Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 210. 1641SX Configuration Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 211. 1641SX scheduled connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 212. 1641SX Backup&Restore Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 213. 1641SX Data Export Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 214. 1641SX Export PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 215. 1641SX Export RI Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 216. 1641SX Sw Download Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 217. AckStationAlarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 218. Connection Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 219. Host Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 220. Log in Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
215
215
215
216
216
217
218
219
219
220
221
222
223
223
224
225
226
226
227
228
229
231
232
233
234
235
236
237
237
239
240
241
242
242
244
245
245
248
249
250
251
253
255
256
257
259
260
261
262
263
265
266
267
270
271
272
01
957.130.932 V

355
9 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 221. Automatic connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 222. List of connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 223. Copy and paste options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 224. ANTP system architecture with colocated ANTP servers . . . . . . . . . . . . . . . . . . . . . . . .
Figure 225. ANTP system architecture with not colocated ANTP servers . . . . . . . . . . . . . . . . . . . .
Figure 226. No external reference clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 227. No external clock source in Resilient configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 228. Cohosted resilient RM/SH No external reference clock source available . . . . . . . . . .
273
274
276
288
288
350
351
352
TABLES
Table 1. Operator Management: Access rights for different User Profiles . . . . . . . . . . . . . . . . . . . . . .
Table 2. Operators management tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3. Default operators in 1353SH5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4. Login as
axadmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5. Login as
userXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6. Login as
userYY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 7. Cross connection Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 8. View Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9. Trasmission Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 10. Supervision Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 11. Port Management Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 12. Performance Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13. Equipment Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 14. External Point Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 15. EPS Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 16. Download Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 17. Diagnosis Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 18. Configuration Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 19. Board Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 20. MS Spring Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 21. Ok Buttons Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 22. Ok Sub Segment Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 23. Alarm Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 24. Mib Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 25. Timing Source Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 26. Generic Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 27. Trace & Log Management: Access rights for different User Profiles . . . . . . . . . . . . . . . . . .
Table 28. Trace & Log Management Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 29. Trace Management: tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 30. Trace Management: trace configuration pathnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 31. Trace Management: Trace levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 32. Backup&Restore: Access rights for different User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 33. Backup&Restore: Tools description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 34. System Management: Access rights for different User Profiles . . . . . . . . . . . . . . . . . . . . . .
Table 35. Stack configuration: NSAP in ISODCC format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 36. Process Monitoring command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 37. Local data management: acess right for different User Profiles . . . . . . . . . . . . . . . . . . . . .
Table 38. Periodic Options: Access rights for different User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 39. 1641SX Maintenance: Access rights for different User Profiles . . . . . . . . . . . . . . . . . . . . .
49
50
53
62
62
62
65
66
69
71
73
74
75
76
77
78
79
80
80
81
83
84
84
84
85
86
101
101
114
115
116
133
134
146
148
161
184
239
247
ED
01
957.130.932 V

355
10 / 354
HISTORY

As internal document 3AL 70805 AAAA TCZZA

Edition
Date
SH delivery
Authors
State
1.0
May 25th 1999
Created by SH3.1 A.Latini, P.A.Sardo

for: SH5.1.0.x
RELEASED
2.0
July 30th 1999
Updated for:
SH5.1.1.x
A.Latini, P.A.Sardo
RELEASED
3.0
Sept 30th 1999
Updated for:
SH5.2.0.x
P.A.Sardo
RELEASED
4.0
Dec 17th 1999
Updated for:
SH5.2.1.x
P.A.Sardo
RELEASED
5.0
Jan 28th 2000
Updated for:
SH5.2.1.2
P.A.Sardo
RELEASED
6.0
Sept 26th 2000
Updated for:
SH5.3
L.Pilotti, F.Pastena
PROPOSAL
6.0
Oct 26th 2000
Updated for:
SH5.3
L.Pilotti, F.Pastena
RELEASED
1AA 00014 0004 (9007) A4 ALICE 04.10
As handbook P/N 3AL 71807 AAAA
ED
ED
DATE
CORRESPONDING TO INTERNAL DOCUMENT ED.
01
001120
6.0
01
957.130.932 V

354
11 / 354
REFERENCED DOCUMENTS
[1]
NR3 SMF specification,

3AL 36740 0001 DSZZA, Ed. 03
[2]
1353SH5 Quality Assurance Plan

3AL 69901 AAAA QMZZA,Ed. 1
[3]
Alcatel/NMU 1353SH3.0, Software Specific Development Process

NMU/GT/96/020, Ed. 1.2
[4]
Alcatel/NMU SMF GUI Style Guide

NMU/GT/97/0190, Ed. 1
[5]
Alcatel/NMU OSF/Motif Style Guide

ISBN 0136431232, Ed. 1.2
[6]
1353SH Element Manager Release 5.3: Feature List

3AL 70805 ADAA FLZZA, Ed. 3
[7]
Alcatel/NMU, NMU Documentation Management Procedure

NMU/RT/95/0034, Ed. 03

Applicable documents (for Alcatel internal use only)
Reference documents (for Alcatel internal use only

[8]
1353 SH 3.1 SMF Specification,

NMU/C/98/0094, Ed. 01
[9]
EML Core 98 System Architecture Description Application, part 1 and part 2

3BP 22100 0001 EBZZA and 3BP 22100 0002 EBZZA, Ed. 1
[10] EML Core 98 System Architecture Description Defence

3PB 22100 0019 EBZZA, Ed1
[11] 1353SH5 User Interface Specification QB3*,
3AL 71310 001 PBZZA, Ed1
[12] Alcatel/NMU, ALMAP Security Management 5.0 Users Guide,
3BP 21607 0012 TCZZA, Ed1
[13] Operators Handbook Rel 5.3: Introduction Manual
[14] Operators Handbook Rel 5.3: Getting Started Manual
[15] 1641SX Maintenance System Maintenance Features
3AL 69396 AAAA PCZZA, Draft
1AA 00014 0004 (9007) A4 ALICE 04.10
[16] Installation Guide1353SH Rel 5.3.....

3AL 70805 AAAA RJZZA Ed 12
[17] 1353SH52 Delivery Notes: 1353SH5.3.0.3
3AL 71572 0001 FMZZA, Ed.07 000914
ED
01
957.130.932 V

354
12 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

[18] Alcatel Network Time Protocol Functional Specification

3AL 36711 0001 DSZZA Ed 02 DRAFT, 960911
[19] RFC 1305
Network Time Protocol March 1992
[20] 1353SH Operators Handbook Rel 5.3
ED
01
957.130.932 V

354
13 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
GLOSSARY / TERMINOLOGY
ED
Add and Drop Multiplexer

Alarm Indication Signal
Automatic Laser Shutdown
Automatic Protection Switching
Alarm Severity Assignment Profile
Administrative Unit
Administrative Unit Pointer Justification Counter
Bit Error Rate
Compact Disc Read Only Memory
Telegraph and Telephone International Consultative Committee
ConnectionLess Network Service
ConnectionLess Network Protocol
Craft Terminal
Data Communication Channel
Data Communications Network
Degraded Signal
Embedded Communication Channels
Element Management Layer
Equipment Protection Switching
Functional Access Domain
Far End Received Failure
Frame Loss Second
Gigabits per second
Gateway Network Element
Human Machine Interface
High Order Assembler
High Order Matrix
High Order Path Adaptation
High Order Path Connection
High Order Path Termination
Hewlett Packard
Hewlett Packard OpenView
Hewlett Packard OpenView Windows
Hewlett Packard Unix
Hewlett Packard Visual User Environment
Higher Order Virtual Container
Institute of Electrical and Electronics Engineers
Information Manager
Kilobits per second
Local Area Network
Link Access Procedures Direct (protocol)
Loss Of Frame
Low Order Matrix
Loss Of Pointer
Loss Of Signal
Loss Of Tributary
Lower Order Path Adaptation
Lower Order Path Connection
Lower Order Path Termination
Lower Order Virtual Container
Media Access Control
Megabits per seconds

ADM:
AIS:
ALS:
APS:
ASAP:
AU:
AU PJC
BER:
CDROM:
CCITT:
CLNS:
CLNP:
CT:
DCC:
DCN:
DS:
ECC:
EML:
EPS:
FAD:
FERF:
FLS:
Gbit/s:
GNE:
HMI:
HOA:
HO Matrix:
HPA:
HPC:
HPT:
HP:
HPOV:
HPOVW:
HPUX:
HPVUE:
HVC:
IEEE:
IM:
Kbit/s:
LAN:
LAPD:
LOF:
LO Matrix:
LOP:
LOS:
LOT:
LPA:
LPC:
LPT:
LVC:
MAC:
Mbit/s:
01
957.130.932 V

354
14 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

MIB:
MS:
MSP:
MST:
NAD:
NAP:
NE:
NML:
NSAP:
NTP:
OFS:
OS:
PDH:
PI:
PPI:
PTM:
RS:
RST:
SA:
SCSI:
SDH:
SF:
SPI:
STMN:
TF:
TMN:
TN:
TP:
TU:
TU PJC:
USM:
VC:
XC:
ED
Management Information Base

Multiplex Section
Multiplex Section Protection
Multiplex Section Termination
Network Access Domain
Network Access Point
Network Element
Network Management Layer
Network Service Access Point
NetworkTime Protocol
Out of Frame Seconds
Operation System
Plesiochronous Digital Hierarchy
Physical Interface
PDH Physical Interface
Path Trace Mismatch
Regenerator Section
Regenerator Section Termination
Section Adaptation
Small Computer Serial Interface
Synchronous Digital Hierarchy
Signal Failure
SDH Physical Interface
Synchronous Transport Module level N (N is an integer = 1,4 or 16)
Transmit Fail
Telecommunications Management Network
Telecommunications Network
Termination Point
Tributary Unit
Tributary Unit Pointer Justification Counter
User Service Manager
Virtual Container
CrossConnect
01
957.130.932 V

354
15 / 354
PREFACE
SH5.3.x version packages

The SH5.3 package deliveries can support the whole set of QB3* and Q3 NEs listed in the Installation
Guide and Release Notes Documents (see [16] and [17]).
1AA 00014 0004 (9007) A4 ALICE 04.10
More important upgrades in respect of last edition regard the features:
Configure processes to use different Lan interfaces, see section 10.1.3: configure FT services and
ANTP server;
Installation of a new software package from CD ROM (only some adjustments in section 11.10.1);
Introduction to Go_Global (only some adjustments in section 14);
Add the procedure to execute the change NE name to NEs NML assigned, in section 17.6.
and they are marked with revision bar.
ED
01
957.130.932 V

354
16 / 354

This edition is applicable to:

1 INTRODUCTION
1.1 General information
WARNING
ALCATEL makes no warranty of any kind with regards to this manual, and specifically disclaims the
implied warranties of merchantability and fitness for a particular purpose. ALCATEL will not be liable
for errors contained herein or for damages, whether direct, indirect, consequential, incidental, or
special, in connection with the furnishing, performance, or use of this material.
NOTICE
The product specification and/or performance levels contained in this document are for information
purposes only and are subject to change without notice. They do not represent any obligation on the
part of ALCATEL.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL and must not be copied,
reproduced or disclosed to a third party without written consent.
1.2 Handbook applicability

This handbook applies to the following product-releases:
1AA 00014 0004 (9007) A4 ALICE 04.10
ANV P/N
Factory P/N
1353SH
3AL 69901 AAAA
521.201.600
PRODUCT
RELEASE
VERSION (N.B.)
ANV P/N
Factory P/N
1353SH
5.3
5.3.0
3AL 70805 ADAA
521.560.720
N.B.
ED
PRODUCT
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

Handbooks relevant to software applications (typically the Operators Handbooks) are not
modified unless the new software version distributed to Customers implies manmachine
interface changes or in case of slight modifications not affecting the understanding of the
explained procedures.
Moreover, should the screen prints included in the handbook contain the product-releases
version marking, they are not replaced in the handbooks related to a subsequent version, if
the screen contents are unchanged.
01
957.130.932 V

354
17 / 354
The list of handbooks given here below is valid on the issue date of this Handbook and
can be changed without any obligation for ALCATEL to update it in this Handbook.
Some of the handbooks listed here below may not be available on the issue date of this
Handbook.
The standard Customer Documentation in the English language for the equipment whose
product-release-version is stated in para.1.2 on page 17 consists of the following handbooks:
1AA 00014 0004 (9007) A4 ALICE 04.10
1.3.1 Handbooks related to the specific software application 1353SH Rel.5.3 Version 5.3.0
HANDBOOK
ANV Part No.
FACTORY
Part No.
1353SH Rel.5.3 Version 5.3.0 Installation

Guide
3AL 71808 AAAA
957.130.942 F
1353SH Rel.5.3 Administration Guide
3AL 71807 AAAA
957.130.932 V
1353SH Rel.5.3 Version 5.3.0 Operators

Handbook
3AL 71806 AAAA
957.130.922 T
ED
THIS
HANDBOOK
or note
01
957.130.932 V

354
18 / 354

1.3 Product-release handbooks
1.3.2 NR 5.0B related handbooks
ANV Part No.
FACTORY
Part No.
1330AS Rel.5.1 Operators Handbook
3AL 71109 AAAA
957.130.722 A
DNM Rel.5.0 Operators Handbook
3AL 71110 AAAA
957.130.732 C
ELM Rel.5.0 Operators Handbook
3AL 71081 AAAA
957.130.462 E
PNM Rel.3.2 Operators Handbook
3AL 71112 AAAA
957.130.752 Q
SEC Rel.5.0 Operators Handbook
3AL 71080 AAAA
957.130.452 C
Generic OSOS Interface REL.4.2

Installation & User Guide
3AL 71184 AAAA
957.140.112 H

HANDBOOK
THIS
HANDBOOK
or note
1.3.3 Handbooks related to the products hardware

Refer to WS supplier handbooks.
In particular refer to such handbooks to obtain the following information (where applicable):
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
COMPLIANCE WITH EUROPEAN NORMS

SAFETY RULES
General rules
Harmful optical signals
Risk of explosion
Moving mechanical parts
Heatradiating Mechanical Parts

ELECTROMAGNETIC COMPATIBILITY
ELECTROSTATIC DISCHARGERS (ESD)
EQUIPMENT LABELS
01
957.130.932 V

354
19 / 354
The purpose of this document is to describe necessary operations to be done by the 1353SH System
Administrator, in order to manage and monitor the SH processes.
1.5 Target Audience

This document is intended to 1353SH Administrators.
The documents that should be read before starting this document are:
Introduction Manual, see [13],

Getting Started Manual, see [14].
It is recommended having some knowledge of SH underlying principles.

This document does not replace a training on 1353SH administration.
1.6 Document Description

This document is divided into two parts:
Part 1: Services provided to the operator by the SMF Interface.
Chapter 2: Generalities. The 1353SH processes are described briefly and management services that
are offered to the system administrator, are listed here.
Role of the administrator.

System Management Notions.
Defence Management.
Document Conventions.
Chapter 3: Release Identification.

The operations necessary for the launching and the stopping of the 1353SH product are described
here.
Chapter 4: Workstation Shutdown Or Powerup.

The operations necessary for the stopping and restarting workstations are described here.
Chapter 5: Maintenance Generalities.

Maintenance activity covers Data saving/restoring, Failure management, Cleanup operations,
Traces management, Logs management.
Chapter 6: Full Backup Disks And Full Restore disks. The operations necessary to backup and
restore the complete disks of workstation are described here.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Short Bootable Tape.

Full Backup Disks.
Full Restore Disks.
01
957.130.932 V

354
20 / 354

1.4 Purpose of the Document

Chapter 7: Operator Management. The operations necessary for the managing of users are
described here.
Tools.
SEC Administration Option for Q3 and Qb3* NEs and ACA management.
Forced Logout Option.
List Current Login Option.
List Unsuccesful Login Option.
List Succesful Login Option.
List Operators Option.
Add Operator Option.
Remove Operator Option.
Change Password Option.
Set Max Operator Number Option.
Set Personal Printer Option.
Chapter 8: System Trace & Log Management. Tools to control logs, to track failure and to control
traces.
SMF/Command/Event Logs Management/Visualization.

Failure Management.
Trace Management.
Cleanup.
Dump Screen.
Chapter 9: Backup/Restore Feature. The operations necessary to backup and restore the1353SH
data are described here.
Overview.
Backup/Restore (User Interface).
Backup Operations.
Restore Operations.
Remotization Enable/Disable Option.
Chapter 10: System Management. The operations necessary for the configuring , launching and
stopping of the 1353SH product are described here.
1AA 00014 0004 (9007) A4 ALICE 04.10
Stack Configuration.
Process Configuration.
Process Monitoring.
System Shutdown.
On Board Simulator Monitoring.
Broadcast message to users.
HPOV Failure on a Workstation.
Chapter 11: Local Data Management. Tools for data maintenance.
ED
Access Rights.
Overview.
Diagnosis of audit of the MIB option (Qb3* NEs only).
Display SEN MIB Option (Qb3* NEs only).
NECTAS Decoding Option (Qb3* NEs only).
NECTAS Comparison Option (Qb3* NEs only).
Upload Failure Diagnosis Option (Qb3* NEs only).
Enable RPS Switch Option (Qb3* NEs only).
01
957.130.932 V

354
21 / 354
Software download manager configuration Option (Qb3* NEs only).

Software download server configuration Option.
Save TP Option (Qb3* NEs only).
Restart Perf Collect Option (Qb3* NEs only).
Overhead byte Configuration Option (Qb3* NEs only).
LAPD Configuration Option (Qb3* NEs only).
Change ASAP Option (Qb3* NEs only).
Sync Source Selection Option (Qb3* NEs only).
Address Configuration Option (Qb3* NEs only).
Change Assigned To Observed and Change Free or Observed To Assigned Options (Qb3* NEs
only).
Switch Old/New Practice Option (Qb3* NEs only).
Set offline Board Option.
Set offline SignalLabel Option.
Ping NE Option.
List Gateway NEs Option (Qb3* NEs only).
DXC TCP/IP address configuration Option.
Change User Label format Option (Q3 NEs only).
Chapter 12: Periodic Actions. The operations necessary for the managing of the periodic actions are
described here.
Overview.
Add a scheduled action Option.
View scheduled actions Option.
Remove a scheduled action Option.
Chapter 13: 1641/1664SX Maintenance. The operations necessary for the managing of
1641/1664SX DXC.
AU maintenance.
Trasmission maintenance.
Backup and Restore.
Data Export.
Software Download.
AcknoledgeStationAlarms.
Chapter 14: Remote Maintenance with GoGlobal. The operations necessary to create and manage
a G_Global connection between a PC and a SH workstation.
Introduction.
Create a GOGlobal connection.
Manage a GOGlobal connection.
Chapter 15: Network Time protocol. The operations necessary to create or modify the NTP daemon
configuration files.
1AA 00014 0004 (9007) A4 ALICE 04.10
Overview.
NTP configuration.
Chapter 16: Alcatel Network Time protocol. The operations necessary to configure ANTP features.
Overview.
ANTP configuration.
Part 2: Procedure sheets.
ED
01
957.130.932 V

354
22 / 354

1AA 00014 0004 (9007) A4 ALICE 04.10

Chapter 17: Procedures.
Preventive maintenance.
Corrective maintenance.
Failure management.
Maintenance operations.
Upload failure.
Advanced network management.
Troubleshooting.
Appendix:
ED
Appendix A: Example of an axconfig file.

Appendix B: Example of a param.cfg file for an EMLIM.
Appendix C: Example of a param.cfg file for perfstorage.
Appendix D: Example of a failure_handler.cfg file.
Appendix E: Example of a trace.cfg file.
Appendix F: Example of an cleanup.cfg file.
Appendix G: Example of NTP configuration files.
01
957.130.932 V

354
23 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V
354
24 / 354

2 GENERALITIES
2.1 Role of the Administrator
The role of the administrator is to:
manage the system and keep the OS up and running:
process monitoring and configuration,

logs management,
trace management,
backup/restore operations,
NE maintenance (software download, save TPs),
reconfigurations (stack, processes).
perform preventive maintenance operations:
to minimize the failures consequences and to be able to start up the system as quickly as
possible in case of power supply failure for example,
to avoid file system full occurence or hardware failures.
perform corrective maintenance operations in case of:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
power supply failure,

file system full,
hardware failures (disk crash, SCSI errors),
software failures (Panic UNIX, HPOV failure, application bug).
01
957.130.932 V

354
25 / 354
2.2 System Management Notions
start/stop the 1353SH system,

get the process startup results from the workstations composing the system,
start/stop processes on workstations,
get process status results for a workstation or for the 1353SH system,
perform backup/restore operations of data,
get troubleshooting information.
Each of the processes that constitute the 1353SH system treats a particular functionality of the system.
Three types of processes can be identified:
General Processes:
They are the functional part of the application. They control the data processing and the data
persistency. Some of these processes are started automatically on launching the system. General
processes can be vital or non vital, they can also be grouped or not grouped.
Presentation Processes:
They control the presentation data or the Human Machine Interface (HMI) of an application. The
Presentation Processes are started at user login, on explicit request by the user or as a result of
navigation between different functionalities of the system. The processes that can be started by a
user depend on his access rights.
Monitoring Processes:
They are the processes that monitor the General Processes composing the 1353SH product. They
detect the failed processes and report the failure to the 1353SH system administrator in a console
shell of the Master workstation. They are non vital.
The allocation of the general processes on the workstations is recorded in a configuration file called the
axconfig file which can be edited. This file contains information on the different processes. It is not
recommended to modify this file. An example of such a file is given in APPENDIX.
The different processes are protected against failure by a defence mode that manages the restarting of the
failed processes. The defence restarting mode is either automatic or manual.
1AA 00014 0004 (9007) A4 ALICE 04.10
The 1353SH workstations are classified in the following way:
Master Station (either Workstation or Server)

There is an unique Master workstation in the 1353SH system. On this workstation is installed the
Application Manager. This process is used to manage and monitor the 1353SH system processes.
All the management and monitoring of the 1353SH is undertaken from this workstation.
As there is only one Master workstation, all other workstations are considered as slaves.
Presentation Workstations
These workstations only run application processes (USMs) whose lifespan is bounded to user
session. They are not subject to any system management operations.
Presentation workstations can be added to the system dynamically (online).
The 1354RM workstation is also declared as a Presentation station for 1353SH application.
EML Workstations (Agent)

These are workstations on which information managers (IMs) run. They are subject to all
management operations. They may run USMs as well but this affects performance of the workstation.
The management of the system processes is done using specific 1353SH commands available in SMF.
They can be used from any station by the administrator but only if the Master station is running.
A very few number of commands can be only accessed via a normal Unix command shell:
ED
01
957.130.932 V

354
26 / 354

The following list specifies the System management services offered to the system administrator to:

A normal Unix command shell (called command shell in this document), where commands are typed.
A readonly console shell (called console) generated by the system after an axstart admax or an
axnewterm, where system responses to commands are displayed.
All messages forwarded to the console are saved in log files. They can be visualized by the administrator,
using the usual Unix text editor.
2.2.1 General Processes
These processes run independently of the user session and are controlled through HP OV process
management features (Local Registration Files) and by the 1353SH Application Manager (APMAN).
There are two types of general processes, vital or non vital. This information is stored in the axconfig file
(see APPENDIX A in this document):
Vital Processes: Important processes without which the 1353SH system cannot run. Certain
general processes such as communication processes are Vital Processes.
Non Vital Processes: Processes that do not cause a crash of the 1353SH system if they fail. The
1353SH continues to run in a degraded mode. As an example, the performance counters temporary
storage module called Performance storage is a Non Vital general process.
General processes can be either single processes or process groups. As for general process type, this
information is stored in the axconfig file. A process group is a set of processes that are interdependent.
If a process of the group is launched then all the group processes are launched, if it is stopped then the group
stops. The processes of the group are always started in the order of their appearance in the axconfig file,
and in reverse order if they are stopped.
If at least one groups process is vital, then the group itself becomes vital, regardless of the other groups
process type.
2.2.2 Presentation Processes
These processes have a lifespan contained in an user session.
The failure of any presentation process is reported to the operators using that particular presentation
process. Generally, the failure of a presentation process results in the disappearance of the graphical user
interface associated to it.
N.B.
The messages that appear on the operators workspace are of two types:
For Equipment Views:
Figure 1. Process failure (example 1)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
For Network Topology Views:
01
957.130.932 V

354
27 / 354

Figure 2. Process failure (example 2)
1AA 00014 0004 (9007) A4 ALICE 04.10
No defence mode is activated for these presentation processes and they have to be restarted, from the
specified workstation(s) on which they failed, by the operator(s) using them.
ED
01
957.130.932 V

354
28 / 354

2.3 Defence Management

If a General Process fails on any workstation, the operator is made aware of the problem by means of a
message in the SH console of the Master Workstation.
2.3.1 General Processes Defence
General Processes have two defence mechanisms: Manual or Automatic restart defence mode.
Manual restart defence mode
In manual restart defence mode, the process must be restarted manually from the Master workstation.
If the process fails again after relaunching without delay and the process is vital, it should be stopped.
Then, the workstation should be restarted.
If the process is non vital, the system can be let working in degraded mode for a certain amount of time,
waiting for the right moment to stop and restart the workstation.
If the restart is still unsuccessful then the administrator can undertake a shutdown of the workstation as
described in chapter MAINTENANCE WS MANAGEMENT. The shutdown should only be done when
the 1353SH processes are cleanly stopped.
Automatic restart defence mode
1AA 00014 0004 (9007) A4 ALICE 04.10
The following figure represents the automatic restart process:
ED
01
957.130.932 V

354
29 / 354

Process Crash
Time counter* => Reset Period

then Crash_ Nb = reset
Process_Crash_Number <
Process critical crash number
Yes
Process_Crash_ Nb+1
Processes
running
Restart Process
No
Vital
No
Yes
Process not
restarted:
Degraded
mode
Workstation
stopped
WS_Crash_Number <
WS critical crash number
Workstation_Crash_ Nb+1
Yes
No
Restart WS Processes
*Time counter: elapsed time between the last

auto. restart and the current auto. restart.
The WS will be restarted by the

administrator after switching the
defence mode to manual.
Figure 3. General process automatic restart diagram

The automatic restart defence mode can be decomposed into three parts:
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
If a General Process fails on any workstation, then the system attempts automatically to restart the
process. If the process fails in the same way, the system tries to relaunch it as long as the number of
restarts does not exceed a critical crash number defined in the axconfig file (MAX_RESTART_NB). If
it does, the process is considered as instable and the procedures to follow depend on the type of process
(vital or non vital).
N.B.
ED
If the failed process is part of a process group, then the same procedure is applied to all
the processes in that group. They are all stopped and restarted but only the number of
restarts of the process which has effectively failed is incremented.
01
957.130.932 V

354
30 / 354

The process number of restarts can be reset, if the failure rate is not too frequent. Each process has
a time counter which evaluates the time elapsed between the last automatic restart and the current
automatic restart. Each time a process fails, the duration recorded by the time counter is compared
to a successive crash period defined in the axconfig file (RESET_PERIOD). If this duration is greater
than the crash period then the process number of restarts is reset. The time counter is however
always reset after this test. This Time Counter enables the operator to differentiate between the real
instable processes and the ones which fail accidentally.
b)
The general process failed too many times, it has exceeded the critical crash number. It is therefore
considered as instable. Depending on the process type, two actions may be performed by the system:
Non vital process: The process is not restarted, the system continues to work even if some nonvital
process are stopped. The system is said to work in degraded mode.
ADVICE:
If the system works in degraded mode, the administrator may choose to toggle the defence mode
to manual, check the processes, restart the failed processes manually and if necessary stop and
restart all General Processes on the workstation.
c)
Vital process: All General Processes on the workstation where the processes failed are stopped
and restarted.
The system will stop all the 1353SH general processes on the workstation and relaunch all of them again.
As for processes, a maximum number of restarts can be defined in the axconfig file (with the tag
MAX_WS_LIVES_NB) for each workstation. If this workstation critical crash number is exceeded then
the workstation stands by with all its processes stopped.
ADVICE:
If the workstation is in stand by, the administrator may choose to toggle the defence mode to manual
and carry out a shutdown of the workstation as described in chapter MAINTENANCE WS
MANAGEMENT. The shutdown should be done only when the 1353SH processes are cleanly
stopped.
Contrary to the process number of restarts, the Workstation number of restarts is never reset except
on workstation manual shutdown and reboot.
A message in the console of the Master Workstation informs about the automatic restart procedure.
2.3.2 Third Party Product Process failure

The 1353SH product uses HP OV and MySql. If either one of these have processes that fail, the following
procedure is undertaken.
MySql failure
MySql processes have no special status and are not managed. Generally the failure will cause the failure
of application.
1AA 00014 0004 (9007) A4 ALICE 04.10
When the workstation is restarted execute the following procedure to restart MySql processes:
from axadmin open a terminal;
launch axstartdb
N.B.
ED
If defence mode is active and the perfstorage process was configurated this action returns
that the process is already running
HP OV software failure
01
957.130.932 V

354
31 / 354
The manual restart mode implies stopping all the general processes on the workstation and stopping
cleanly all the HPOV processes. This should be done by Unix system administrators only.
The following figure represents the automatic restart process:
HP OV failure
Workstation_Crash_ Nb+1
Stop 1353SH Processes
on Workstation
Stop HPOV Processes
on Workstation
Workstation shutdown
Workstation reboot
Processes
running
Start HPOV Processes

on Workstation
WS_Crash_Number <
WS Critical crash number
Yes
Restart WS Processes
No
The WS will be restarted by the

administrator after switching the
defence mode to manual.
Figure 4. Automatic restart after HP OV failure diagram
1AA 00014 0004 (9007) A4 ALICE 04.10
The system will stop all the running 1353SH general processes and monitoring processes and reboot the
workstation, after having done any house keeping tasks required related with opened databases.
If the workstation number of restarts exceeds the critical crash number defined in the axconfig file
(MAX_WS_LIVES_NB) then the workstation wont be rebooted and will remain in stand by with all its
processes stopped.
ED
01
957.130.932 V

354
32 / 354

Following the failure of the HP OV software a message appears in the console to alert you of the problem.
1AA 00014 0004 (9007) A4 ALICE 04.10

ADVICE:
If the workstation is in stand by, the administrator may choose to toggle the defence mode to manual and
reboot the workstation. The shutdown should be done only when the 1353SH processes are cleanly stopped.
When the system has rebooted, restart the 1353SH general processes on the failed workstation ).
At the end of the workstation reboot the system automatically restarts all the 1353SH general processes
and monitoring processes that run on that workstation.
However, due to the reboot, the operator will have to login again in order to pursue his work.
ED
01
957.130.932 V

354
33 / 354
This manual sometimes indicates the commands that have to be typed out by the SDH Manager System
Administrator in a UNIX command shell. To avoid any ambiguity, the following conventions are used:
The UNIX prompt is chosen as the > sign.

Commands that are typed out by the system administrator will be in the bold courier
font preceded by the UNIX prompt.
Variable names will be in the courier italic font. They will usually represent workstation
hostnames or process names.
For example, the UNIX command date is written > date .

The sign indicates that the Return key is pressed on the keyboard.
> date
Figure 5. Example of typed unix shell commands.

The system responses in general will be displayed as a window hardcopy as shown in the following figure.
Figure 6. Example of the system response to the command date.
1AA 00014 0004 (9007) A4 ALICE 04.10
The commands provided to the SDH Manager administrator are available into the Administration toolbox
available in the desktop. Most of them can also be accessed through a shell command (for users of
sysadmin group).
ED
01
957.130.932 V

354
34 / 354

2.4 Document Conventions

The following figure shows the subpanel giving access to these toolboxes, after clicking the 1353SH button
on the administrators desktop:
Figure 7. Access to the 1353SH System Management functions

For the Administration toolbox, the graphic interface SMF System Management Features is used as
presentation interface.
Most part of the functions requires to be run from the SH Master station, so , when the administrator is
logged on a SH slave station, starting the Administration toolbox offers him the choice for location:
on the Master: presents all the tools. Actions are executed remotely on the Master station,
locally: presents only a reduced list of tools launchable from a slave station.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 8. Starting the SMF

The action is launched after selecting the option and giving all necessary parameters by means of
succesive menus with at least 2 levels:
1st level: Select the feature (family of functions)
ED
01
957.130.932 V

354
35 / 354
2nd level: Select the function

lower levels: Select the action , choose options and parameters...
Figure 9. Successive menus
1AA 00014 0004 (9007) A4 ALICE 04.10
When an action can not be executed the system opens an error window (red background).To print a clear
message for the operator, it opens an info window (blue background).
Figure 10. Examples of error messages
ED
01
957.130.932 V

354
36 / 354

The actions may also be launched using a command script in a command shell. The scripts are gathered
into the $DIR1353SH/script directory.
The following figure shows the SMF main menu. Each chapter from 7 to 13 in this document, is dedicated
to one of the following items.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 11. SMF main menu
ED
01
957.130.932 V

354
37 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V
354
38 / 354

3 RELEASE IDENTIFICATION
This command gives the identification of all the 1353SH products and filesets installed on the target
workstation. It can be accessed by all the users.
Figure 12. 1353SH version

Click on the 1353SH Network Management System banner in the toolbox of the 1353SH users desktop
to open a new window displaying the result of the command.
1AA 00014 0004 (9007) A4 ALICE 04.10
All the applicative products are displayed, as well as the filesets. The 1353SH_IDENT shows the SH
delivery current version.
ED
01
957.130.932 V

354
39 / 354

Figure 13. Release folder of the Administration toolbox
Bootable medium
1AA 00014 0004 (9007) A4 ALICE 04.10
Identifies the bootable medium, the date of creation of the reference. It is not dependent of the 1353SH
release.
ED
01
957.130.932 V

354
40 / 354
Sub products of 1353SH
1AA 00014 0004 (9007) A4 ALICE 04.10

The sub products main components of the 1353SH 5.x product are given with subproduct_name + version,
Example: PNM 5.x.
The standard sub products are: AS, PNM, DNM, OSCORE_KERNEL, all the 1353SH5_EMLIM,
1353SH5_KERNEL.
The EMLIMs are optional. When an EML is installed for the OS 1353SH5, it may be loaded on some
stations and not on other stations (refer to Installation Guide).
Filesets
The detailed content of each sub product is given with a list of subproduct.fileset
Click on the Dismiss button to close this window .
ED
01
957.130.932 V

354
41 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V
354
42 / 354

4 WORKSTATION SHUTDOWN OR POWERUP

The shutting down or the powerup of a workstation may be necessary if the attempt to relaunch some
processes fails.
The consequence of a workstation shutdown is that the administrator will have to powerup the workstation
before next login.
a)
Workstation shutdown.
Workstation shutdown can be undertaken in two ways :
A graceful shutdown undertaken by the administrator.

In this case all the processes running on the workstation at the time of the shutdown are
stopped.
> shutdown h
The r option will cause the reboot of the station
The h option will cause the halt of the station
b)
A workstation shutdown undertaken by the system in the automatic restart mode.

This can only occur when a third party product software fails and the automatic restart mode
is set for the system. The system automatically reboots the workstation.
All the 1353SH processes (except the presentation processes, started on demand) that were
running at the time of shutdown are restarted along with HP OV.
Operators that were logged on the workstation are logged out and have to log in again.
Workstation powerup.
Workstation powerup is undertaken in three possible cases :
Following a graceful shutdown by the administrator.

The workstation is powered up by the Unix System Administrator using the appropriate unix
commands.
If a workstation is rebooted in the automatic restart mode

This is the case following third party software failure .
Following a workstation crash

A workstation crash can occur due to :
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
A power supply failure,

A unix panic,
A disk crash.
Warning : After a crash pay attention to messages indicating a disks corruption . If fsck is
required that means the integrity of the 1353SH application can not be assumed any
longer. In such a case it is recommended to make a full system restore (see chapter 11).
In all these cases, after a workstation reboot, the third party software products are restarted
automatically.
The 1353SH processes restart depends on the defence mode that was set before the workstation
crashed .
ED
01
957.130.932 V

354
43 / 354
If the automatic mode was set.

The 1353SH general processes are relaunched automatically. Operators can now log in.
If the manual mode was set.

The 1353SH general processes have to be relaunched manually using the Process
Monitoring function .
1AA 00014 0004 (9007) A4 ALICE 04.10
All the stages in the relaunching of the workstation processes are displayed in trace files that store all the
events occurring in the process of the workstation.
ED
01
957.130.932 V

354
44 / 354

5 MAINTENANCE GENERALITIES

Several tools are provided with the 1353SH to handle common maintenance tasks.
Maintenance Directory Location and Content
The Maintenance directory can be located under the 1353sh/ root directory ($DIR1353SH/maintenance).
This directory is dedicated to the collect and the record of all data concerning the system maintenance.
The data is distributed in various subdirectories located under the main maintenance directory:
1353sh
backup
backup core
backup
maintenance/core
maintenance/trace
maintenance/log
maintenance/failure
maintenance/stat
maintenance
log
failure
stat
trace
on the slave workstation this directory will be empty. On the Master workstation,
this directory will contain the failure backup data which is tared and
compressed.
the UNIX core files are saved in this sub directory.
current trace and dataflow files.
log files.
saving (of traces, of core...) when a process fails .The name of the
files(directories) located in this subdirectory are conform to the format
date_time (eg. 199802101455), for the date and time of the anomaly.
global statistics on the system quality.
1AA 00014 0004 (9007) A4 ALICE 04.10
For each rubric , except stat ,the tools management provided by SMF allow visualizing , saving , deleting
the corresponding files or directories . See chapters to 10 to 16.
ED
01
957.130.932 V

354
45 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V
354
46 / 354
6 DISKS FULL BACKUP AND FULL RESTORE
1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.
These operations are different from the backup/restore feature described in the chapter 10.
Presentation
The disks Full Backup and Full Restore facilities allow to keep a complete disk(s) copy (dump) for the
station where the operation is performed.
The convenience of this copy is it allows to retrieve in a fast and safety way an exact image of installation
including the configuration and data. The inconvenience is that making an OS backup requires to do a
backup on each station and to stop each one for at least 1h30.
The complete description is reported in the Installation Guide. Refer to [16]
ED
01
957.130.932 V

354
47 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V
354
48 / 354
7 OPERATOR MANAGEMENT

When clicking on the Operators Administration option, the following window is displayed:
Figure 14. Operators Administration Menu

From this window the system administrator can manage operators and define their permissions.
Access Rights
The following table shows the access rights for the different User Profiles. The chapter 7.8
corrispondence between User Profile and User Name.
SMF Command
lists the
Access rights
Change password
all user
Set Personal Printer
all user
The other ones
admin
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 1. Operator Management: Access rights for different User Profiles
ED
01
957.130.932 V

354
49 / 354
7.1 Tools
Command
Script
Description
SEC Administration
Command used to activate a new Access Control

Domain.
Forced Logout
Command used to force the logout of a specifc user.
List Current Login
Command used to list the current logins.
List Unsuccessful Login
Command used to list the unsuccessful logins.
List Successful
Command used to list the successful logins.
Login
List Operators
Command to list user accounts and profiles.
Add Operator (*)
axadduser
Command used to create a new user account and

assign a profile.
Remove Operator (*)
axdeluser
Command to delete an user account.
Change Password (*)
axpasswd
Command to change any users password.
Set Max Operator Number
Command to set max dtsessions number.
Set Personal Printer
Command to set users print command and destination.
Table 2. Operators management tasks

(*)
These commands can not be launched simultaneously.
The Operators Management functions require the administrator rights, i.e any user of gadmin group, and
may be run only on the Master station, except the Change Password and Set Personal Printer options
which are authorized to all the users on all the stations.
The graphic interface is globally the same for all the functions and it differs slightly only:
for fields used to set specific parameters for the function,

for the usage of the Select WS button which may be inhibited, meaning the function applies to all
workstations.
By scanning with the mouse, for each parameter field, the main rules usage will be displayed in the
information field. Rejected parameters will be mentioned in an error window once the command is started.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Print pushbutton edits a file containing the information displayed by the graphical interface.
ED
01
957.130.932 V

354
50 / 354

The following table gives the list of functions and commands dedicated to operators management tasks.

7.2 SEC Administration Option

7.2.1 The access control model
SEC is the generic component of the ALMAP platform which implements access control in conjuction with
the applications for which access control is activated (EMLUSMs, DNM, PNM, ..).
The access control is a set of methods and related data aiming at deciding, in quite general terms, whether
someone can do something.
In the framework of the Network Management system
someone means an operator of one of the Network Management applications;
do something means performing a given operation, such as for example, invoking a specific com
mand of the considered application.
An operator working at his/her station is called an initiator. The operation to be performed is called a
target. The definition of the access control policy consists in declaring initiators and targets, and then
associating targets to initiators.
Clicking on SEC Administration option from Operators Administration window the Access Control
Administration tool (ACA) opens (see Figure 15. ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 15. ACA interface

Using ACA the SEC administrator can grant/denie access rights to the various operators.
ED
01
957.130.932 V

354
51 / 354
Objects
Access control is based on objects on which the functions operate. In the SEC context, an object is an
atomic nonfunctional resource of the NM system, accessible by the operator through the NM Application
user interface (pnmusm, emlusm, ..). Objects are classified by family.
1353SH5 SEC environment provides two object families:
AccessControlDomainFamily: concerns network elements and communication ports management;

an object belonging to this family is called Access Control Domain (ACD) and its usage is described
in the following sections;
DnmAccessControlDomainFamily: concerns distributed maps management. Security policy in maps

distributing is decribed in [20].
The list of functions and object families is determined at application design time. The set of objects may
vary along the use of the Network Management system. A set of predefined objects may be created at
configuration or installation time (e.g. the Unknown object). Creation of some other objects will result from
the direct operation of a SEC administrator, through the ACA tool (e.g. ACDs). Other ones will be created
by applications on the direct initiative of an operator (e.g. distributed maps, new operators). Anyway, the
creation of a new object in the Access Control Information database is always notified to a user of the ACA
tool.
Functions
A function may directly map to an atomic feature of an application, such as a specific command
corresponding to a menu item or a dialog box button. It may also correspond to a group of such basic
features, when it appears impossible or difficult to distinguish them from an access control point of view.
Symmetrical features, for example, such as start_supervision and stop_supervision in a PNM menu, will
generally be grouped in the same function, as one of these features may hardly be granted, while the other
is denied.
The definition of these functions is not under control of the SEC administrator. The list of functions of an
application is determined when designing this application. The SEC administrator will access this
functions list and, starting from it, will associate access rights to the initiators. Note also that some
commands or operations of an application may not be mapped to a function. The list of functions may
represent only a subset of the application features. For example, if a command is designed to be always
available to any operator, there will not be a corresponding function in the list.
1AA 00014 0004 (9007) A4 ALICE 04.10
ObjectFunctions Combinations
A combination is the association of an object and a list of functions applying to this object. Using
combinations can make easier the definition of policies where, for a given object, the list of operations that
can be performed on this object varies with the operator. Though they are actual components of the profiles
(see later), objectfunctions combinations are not visible, in the ACA context, at this elementary level.
Actually, they are implicitly defined by the combination of an OAD (which groups objects) with a FAD (which
groups functions). These notions are introduced in the following sections.
Operators and profiles
The first step to introduce access control in a 1353SH system is to declare users as operators. Declaring
operators must be done via the Add Operator function described in chapter7.8; operators must not be
added, modified or removed by the ACA tool.
Several operators may be given the same privileges. On the other hand, an operator may play several
parts implying the union of several sets of access rights (e.g. profiles).
The notion of operators group is introduced to simplify the definition of access rights. A group is
characterized by a list of operators. An operator does not necessarily belong to any group. On the other
hand, he/she may belong to several groups.Two operators belonging to the same group will share at least
the access rights defined for this group, but each of them may also own additional rights, declared either
at individual level or coming from other groups of membership. Operator groups can be created by ACA.
ED
01
957.130.932 V

354
52 / 354

The access control model of SEC is based on the notions of object, function, and objectfunction
combination.

Operators and operator groups are called initiators in the SEC environment. The objects, the functions
and the objectfunction combinations are called targets. The access control policy consists in associating
targets to initiators. For each initiator, the list of authorized targets constitutes his/her profile.
1353SH5 provides a default set of operators with predefined profiles, as shown in Table 3. :
Group
Operators
Profile
admin
axadmin
OSadmin
admin
axemladm
admin
constructor
axemlcst
constructor
operator
axemlope
operator
viewer
axviewer
viewer
viewer
axrmaint
admin
Table 3. Default operators in 1353SH5

On creating a new operator through the Add Operator function, you are required to select one of the
predefined profiles shown above; predefined names and predefined profiles cannot be reconfigured.
However, the SEC administrator can modify the initial profile of each operator changing his targets by the
ACA tool.
7.2.2 Object Access Domains (OADs)
SEC introduces the notion of Object Access Domain (OAD) to group objects. An Elementary OAD groups
objects. A Top Level OAD can group Elementary OADs. The objects may belong to several Elementary
OADs. Elementary OADs may belong to several Top level OADs. Moreover, any Elementary OAD may
be included in any Top Level OAD.
When a new operator is added, an empty Elementary OAD having the same name is automatically
created. Such an OAD can be handled by the SEC administrator exactly like any other OAD; afterwards,
such an OAD may be populated with available objects (e.g. distributed maps, ACDs). On its creation, this
Elementary OAD automatically becomes a target of the new operator (that is, it is put in the operators
profile).
The meaning of group/operator profile can be now reassumed as follows:
a list of OADs. The union of these OADs results in a list of objects. The Elementary OAD created on
the declaration of a new operator (with the same name) is automatically inserted in this list, but can
be removed.
a list of FADs. The union of these FADs results in a list of authorized functions.
a list of OADFAD combinations resulting in a list of objectfunction combinations.
1AA 00014 0004 (9007) A4 ALICE 04.10
7.2.3 Functional Access Domains (FADs)

Defining the access rights (e.g. profiles) of an initiator considering each function on an individual basis,
while possible, would be a tedious task. The ACA tool allows to define groups of functions, called
Functional Access Domains (FADs), to ease the definition of rights.
ED
01
957.130.932 V

354
53 / 354
For further details please refer to the ALMAP Security Management 5.0 Users Guide [12] available also
as HelpOnLine through the Help pushbutton.
N.B.
In order to activate changes to targets configuration, like adding new FADOADs or elementary
FADs to an operator, it is not enough restarting the application or relogin. You have to kill the
lss process on all SH workstations (via kill Unix command). The LSS automatically restarts.
N.B.
The usage of ACA on a 1353SH5 plugged in a 1354RM workstation has some restrictions: they
are described in delivery notes [17] or installation guide [16] documents.
7.2.4 Define a new User Profile using ACA graphical tool

It is possible to assign the following types of target:
Using the item OAD... from the Configuration menu it is possible to define the Elementary OAD (
Object Access Domain ); this kind of information defines an object type ( i.e. new Access Control
Domain type ). A generic OAD can be assigned to a resource. After this operation only the group
users with this OAD in the ACA profile can manage this resource. The first step is to create a new
Object ( see Figure 16. ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 16. Object Access Domain creation

To define a new OAD it is necessary to specify mandatory information ( Name, Family, Creator and
System Id ). It is also possible to set optional information ( type and additional information ). The Name
is used by ACA to manage the object, the Family to set the type of the OAD ( i.e. only
AccessControlDomainFamily can be used by EMLUSM ), the Creator information defines the Group
User which can see in any case the resource ( i.e. NE in the Network Map ) with the new OAD ( see
para. 7.2.6 ).
ED
01
957.130.932 V

354
54 / 354

To allow interapplication function grouping, the notion of System FAD is introduced. A System FAD can
refer to any number of Application FADs.
Then you have to create a new Elementary Object ( see Figure 17. )

To define or modify an Elementary OAD it is necessary to specify all the Objects which are included
in the object scope. In the example of Figure 17. the new elementary object EleOadXX included the
OAD Access Control Domain Family XXoadobj but not the Unknown object. The default ACD domain
is unknown. All the operators can manage resources with this default domain.
Figure 17. Elementary Object creation.
1AA 00014 0004 (9007) A4 ALICE 04.10
or modify an old one ( see Figure 18. ). An example of resource is a Network Element ( NE ) . Actually,
when a NE is created the Operator can decide which OAD domain is assigned to the NE itself.
ED
01
957.130.932 V

354
55 / 354

Figure 18. Object Configuration

Using this ACA interface it is possible to add and modify an OAD ( generic or elementary ).
Using the item FAD... from the Configuration menu it is possible to define the FADs ( Function Access
Domain ); it describes the functions available for each kind of application which supports SEC ( es.
the application FAD AsCurAdmin includes the function Reserve Alarm but does not support the
Inhibit Security ). Each application supplies a set of FAD for each default user profile ( Admin,
Operator and Viewer ) ( see the application list for pnmusm in Figure 19. ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Each application that is integrated with SEC provides a set of default FAD for each group of operator
( Administrator, Operator and Viewer ). In the example of Figure 19. the PnmUsm defines the
following default profiles: PnmUsmAdmin, PnmUsmOpera, PnmUsmViewer and pnmInhibit.
ED
01
957.130.932 V

354
56 / 354

Figure 19. Default Function Access Domain

It is possible to create a new FAD profile for each application ( see Figure 20. ).
1AA 00014 0004 (9007) A4 ALICE 04.10
It is possible to customize each FAD selecting the functions to be supported by the specific FAD.
In the example of Figure 20. the left box contains the functions that are not assigned to the profile
<EmlUsmSH5Opera>. This means, for example, that an operator belonging to the group
<EmlUsmSH5Opera> cannot perform an EquipmentRackRemoteInventory ( FAD in the left column
).
ED
01
957.130.932 V

354
57 / 354

Figure 20. Create/Modify a new Function Access Domain

In SH Version 5.3 the applications set includes the following:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
As Current Usm
As Historical Usm
DNM Usm
Elm Browsing Usm
Eml Usm SH5 ADM
Eml Usm SH5 DXC
SH5MW
Eml Usm SH5 WDM
SH30QB3S
SH31QB3S
SH5QB3S
PNM Usm
SMF Emlcore
SMF SH
Using the item OADFAD... from the Configuration menu it is possible to define the OADFAD
combination ( see Figure 21. ), this information describes which kind of function ( FAD ) is possible
to perform on a specific object ( OAD ) ( i.e. OADFAD adminunknown based on EleOad unknown
and SysFad administration )
01
957.130.932 V

354
58 / 354

Figure 21. OADFAD Combination creation

Using this ACA interface it is possible to associate a set of FADs to an elementary object. In the
example of Figure 21. the new OadFadXX map the System Fad of the administrator on the
EleOadXX elementary object.
So it is possible to create a new user that can perform only specific action ( FAD ) on specific object ( OAD
). For example it is possible to define a user who can do only cross connection operation or only
performance management.
1AA 00014 0004 (9007) A4 ALICE 04.10
The default environment gives the following group profile:
Admin, this user is influenced by the ACD but he/she can modify the profile to manage all the
functions.
Operator, this user can manage the visible NE but he/she cannot manager the Manager List and the
Board Domain. This kind of user cannot modify the SEC profile.
Viewer, this user cannot configure anything on the visible NE but only explore and navigate. This kind
of user cannot modify the SEC profile.
To activate the new configuration it is necessary to stop ( i.e. kill 9 ) the lss process. This process is
automatically started.
ED
01
957.130.932 V

354
59 / 354
7.2.5 Create a new Access Control Domain
Using the item OAD... from the Configuration menu it is possible to display the OAD configuration
dialog. Select the object button to create with ACA ( OAD Configuration, Object ) an OAD Object,
for example ( see Figure 16. ):
Name
= XXoadobj
Family
= AccessControlDomain
Creator
= userXX
SysId
= acdXX
From the same dialog select the elementary button to create with ACA ( OAD Configuration,
Elementary ) an Elementary Object ( see Figure 17. ) that contain the new OAD Object ( i.e.
EleOADXX includes XXoadobj )
Using the item OADFAD... from the Configuration menu it is possible to define with ACA (
OADFAD Combination Configuration ) an OADFAD combination ( see Figure 21. ) that link the
new Elementary Object with a specific set of FAD ( i.e. OadFadXX composed of EleOadXX and
System Fad of Administrator )
Using the item Initiator... from the Configuration menu it is possible to add with ACA ( Access Rights
Definition ) ( see Figure 15. ) the new OADFAD combination to the set of initiator that you want to
improve with the new ACD type:
Using this ACA interface it is possible to specify for each group of operator the set of target ( i.e. FAD, OAD,
Elementary OAD and OADFAD ) that can be used.
7.2.6 General SEC behavior
These are the following basic rules to manage the access to the NE:
If the operator has the NE OADFAD of the new ACD in the ACA profile, he/she can manage the NE
If the operator has not the NE OADFAD of the new ACD in the ACA profile but he/she is the ACD
creator he/she can see the NE in the network map but he/she cannot manage the NE
If the operator has not the NE OADFAD of the new ACD in the ACA profile and he/she is not the
ACD creator he/she cannot see the NE in the network map
The default ACD domain is unknown. All the operators can manage resources with this default
domain.
1AA 00014 0004 (9007) A4 ALICE 04.10
Let us suppose that you create the following Access Control Domain :
AcdXX
Family
Creator
SysId
=
=
=
AccessControlDomain
userXX
acdXX
AcdYY
Family
Creator
SysId
=
=
=
AccessControlDomain
axadmin
acdYY
ED
01
957.130.932 V

354
60 / 354

The following operations are necessary to define a new Access Control Domain ( ACD ):

A generic user can manage only NEs with its own ACD. By the way it is necessary that the user contain
as target the OADFAD combination of the NE ACD ( see paragraph 1.2 ). Moreover the operator will see
in the PNM map all the NEs having an ACD created by the operator himself.
It is possible to modify the NE ACD value by the PNM using the NeInfo menu ( see Figure 22. )
Figure 22. Modify the NE ACD value

Example 1
1AA 00014 0004 (9007) A4 ALICE 04.10
Using the axadmin login you can manage only the unknown ACD type, but you are able to see in the map
also the NE3 with AcdYY because the axadmin is the creator of the AcdYY ACD type.
ED
01
957.130.932 V

354
61 / 354
NE1
ACD = unknown
NE2
ACD = AcdXX
NE3
ACD = AcdYY
NE Creation
OK
Not Possible
OK
Visibility of NE
OK
Not Possible
OK
Managing of NE
OK
Not Possible
Not Possible
Example 2
Using the userXX login you can see and manage the NE1 and only see the NE2. If the userXX wants to
manage the NE2, it is necessary to add the AcdXX type inside the userXX ACA profile.
Table 5. Login as
userXX
NE1
ACD = unknown
NE2
ACD = AcdXX
NE3
ACD = AcdYY
NE Creation
OK
OK
Not Possible
Visibility of NE
OK
OK
Not Possible
Managing of NE
OK
If userXX contains the Not Possible

AcdXX target
Example 3
Using the userYY login you can see and manage the NE1 and only see the NE3. If the userYY wants to
manage the NE3, it is necessary to add the AcdYY type inside the userYY ACA profile.
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 6. Login as
userYY
NE1
ACD = unknown
NE2
ACD = AcdXX
NE3
ACD = AcdYY
NE Creation
OK
Not Possible
OK
Visibility of NE
OK
Not Possible
OK
Managing of NE
OK
Not Possible
If userYY contains the

AcdYY target
ED
01
957.130.932 V

354
62 / 354

Table 4. Login as
axadmin
7.2.7 EmlUsm Profiles

For each EML USM a Fad is defined and for each of this three profiles are defined.
The user profiles provided for example by the SH5 Q3 EMLUSMADM are:
EmlUsmSH5Admin
EmlUsmSH5Opera
EmlUsmSH5Viewer
When an EmlUsm application is installed, the corresponding user profiles are inserted in the SEC.
Now, it is possible to assign the EmlUsm user profile to the user name. By default, there is no
assignment.
User Name
axadmin
axrmaint
axemladm
axemlcst
axemlope
axviewer
Figure 23. Relation between the User Name and the EmlUsmSH5 profile
1AA 00014 0004 (9007) A4 ALICE 04.10
The EmlUsmSH5 profiles are a subset of the EmlUsmSH5 FADs. Normally, the EmlUsmSH5Admin has
all the permissions enabled. The EmlUsmSH5Opera has the permissions enabled according to the
operator activities and the server configuration. The EmlUsmSH5Viewer has only the display permissions
enabled.
The Standard User Names (axadmin, axrmaint, axemladm, axemlcst, axemlope, axviewer) have the
permissions enabled according a miscellaneous of every application profile.
ED
01
957.130.932 V

354
63 / 354
For example, the axemladm could be enabled to every permission of EmlUsmSH5Admin and to the
permissions of PnmUsmViewer, because the target of axemladm is to manage the Eml, not the PNM.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED

In the following chapters are described all the application domain.
01
957.130.932 V

354
64 / 354
7.2.8 Q3 FADs configuration

CrossConnection FAD configuration

The following functions are related to the Cross Connection; in particular way, it is possible to:
Protect the existing cross connection(s)
Modify the existing cross connection(s)
Delete the cross connection(s)
Activate/Deactivate the cross connection(s)
Create the cross connection(s).

Application FAD
EmlUsmSH5Admin
EmlUsmSH5Opera
EmlUsmSH5Viewer
XcProtProtectedCC
Forbidden
XcModifyCC
Forbidden
XcMgmtDeleteCC
Forbidden
XcMgmtDeActivateCC
Forbidden
XcMgmtActivateCC
Forbidden
XcCreateCC
Forbidden
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 7. Cross connection Application FAD
ED
01
957.130.932 V

354
65 / 354
The view is a photorealistic and zoomable view of the front side of a physical equipment or an NE. Several
equipment can be displayed in the container, with their equipment type dependent snapshot image.
In the container, only the directly contained equipments are displayed.
In particular, in the Views menu, it is possible to handle:
External Points: open the external point view
Synchronization: open the Synchronization view
Open Objects: it allows to navigate and show the contents of the selected object (the current view
change). It is equivalent to a doubleclick on the selected element in the view area.
Application FAD
EmlUsmSH5
Admin
EmlUsmSH5
Opera
EmlUsmSH5
Viewer
ViewsSynchronisation
ViewsOpenObject
ViewsOpenInWindow
ViewsLOTransmission
ViewsHOTransmission
ViewsExternalPoints
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 8. View Application FAD
ED
01
957.130.932 V

354
66 / 354

View FAD configuration

Transmission FAD configuration

The transmission domain covers the management of transmission resources. Moreover the test domain
is referenced, which includes the loopback management functionality. The views of the transmission
domain also refer to the alarm and performance domain. The features of both domains are provided by
the port views and the transmission view and several secondary dialogs. The transmission domain
includes:
Management of SDH Transmission (TransSDH*)
Management of PDH Path Layer (TransPDH*)
Management of PDH Transmission Media Layer (TransPDH*)
Management of transmission alarms (TransStructureTPs*)
Management of performance monitoring on transmission resources (TransPerformance*)
Navigation to supporting equipment (TransNavigateToPortView)
Management of the Cross Connection (TransCrossConnection*)
N.B.
The FAD in italics means the start of a subgroup related to the same functionality.
1AA 00014 0004 (9007) A4 ALICE 04.10
Application FAD
EmlUsmSH5Admin
EmlUsmSH5Opera
EmlUsmSH5Viewer
TransTpConf
Forbidden
TransTermTp
Forbidden
TransStructureTPs
VC3_4
Forbidden
TransStructureTPs
VC12
Forbidden
TransStructureTPsTU3
Forbidden
TransStructureTPsTU2
Forbidden
TransStructureTPs
TU12
Forbidden
TransStructureTPs
Menu
Forbidden
TransShowSupportedBoard
Forbidden
TransSDHTxQualityConfiguration
Forbidden
TransSDHSingleFiberConfiguration
Forbidden
TransSDHShowOpticalConfiguration
Forbidden
ED
01
957.130.932 V

354
67 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
EmlUsmSH5Admin
EmlUsmSH5Opera
EmlUsmSH5Viewer
TransSDHRegenerator
SectionManagment
Forbidden
TransSDHPort
Loopback
Forbidden
TransSDHNEMSP
Synthesis
Forbidden
TransSDHMenu
Forbidden
TransSDHMSP
Managment
Forbidden
TransSDHMSP
Commands
Forbidden
TransSDHMS
Configuration
Forbidden
TransSDHLoopback
Forbidden
TransSDHExtraTraffic
Forbidden
TransSDHAls
Managment
Forbidden
TransPerformance
Menu
Forbidden
TransPerformance
HistoryData
Forbidden
TransPerformance
CurrentData
Forbidden
TransPerformance
ConfigureMonitoring
Forbidden
TransPDHTpConf
Forbidden
TransPDHPort
LoopbackConfiguration
Forbidden
TransPDHMenu
Forbidden
TransPDHLineLengthConfiguration
Forbidden
TransNavigToPortView
Forbidden
TransMenu
Forbidden
TransHideUpperTPs
Forbidden
TransHideSelectedTPs
Forbidden
TransHideMenu
Forbidden
ED

Application FAD
01
957.130.932 V

354
68 / 354

Application FAD
EmlUsmSH5Admin
EmlUsmSH5Opera
EmlUsmSH5Viewer
TransHideLowerTPs
Forbidden
TransExpandWholeUp
Forbidden
TransExpandWholeDown
Forbidden
TransExpandNext
LevelUp
Forbidden
TransExpandNext
LevelDown
Forbidden
TransExpandMenu
Forbidden
TransCrossConnectionShowCCTps
Forbidden
TransCrossConnectionModify
Forbidden
TransCrossConnectionMenu
Forbidden
TransCrossConnectionCreate
Forbidden
TransAddTp
Forbidden
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 9. Trasmission Application FAD
ED
01
957.130.932 V

354
69 / 354
The following functions are related to the Supervision menu. The menu allows to handle the NE
supervision. The available entries are the following:
NE Reset (SupervisionNEReset)
NE Info (SupervisionNEInfo)
Resynchronize alarms (SupervisionAlarmsResynchronize)
Access State (SupervisionAccessStase*)
1AA 00014 0004 (9007) A4 ALICE 04.10
Application FAD
EmlUsmSH5
Admin
EmlUsmSH5
Opera
EmlUsmSH5
Viewer
SupervisionUploadRemoteInventory
Forbidden
SupervisionUploadAnalogMeasures
Forbidden
SupervisionStop
Forbidden
SupervisionStartMenu
Forbidden
SupervisionStartAlignWithAudit
Forbidden
SupervisionStartAlignUp
Forbidden
SupervisionStartAlignEnhanced
Forbidden
SupervisionStartAlignDown
Forbidden
SupervisionSimulatorStart
Forbidden
SupervisionSimulatorMenu
Forbidden
SupervisionNESupporting
Forbidden
SupervisionNESupported
Forbidden
SupervisionNEReset
Forbidden
SupervisionNEMenu
Forbidden
SupervisionNEInfo
Forbidden
SupervisionMenu
Forbidden
SupervisionMaintenanceMemory
Upload
Forbidden
SupervisionMaintenanceMemory
Menu
Forbidden
SupervisionMaintenanceMemoryClear
Forbidden
SupervisionDumpMIB
Forbidden
SupervisionAlarmsResynchronize
Forbidden
ED
01
957.130.932 V

354
70 / 354

Supervision FAD configuration
1AA 00014 0004 (9007) A4 ALICE 04.10

Application FAD
EmlUsmSH5
Admin
EmlUsmSH5
Opera
EmlUsmSH5
Viewer
SupervisionAlarmsReset
Forbidden
SupervisionAlarmsMenu
Forbidden
SupervisionAlarmsInhibitNotifs
Forbidden
SupervisionAlarmsAllowNotifs
Forbidden
SupervisionAccesStateOS
Forbidden
SupervisionAccesStateMenu
Forbidden
SupervisionAccesStateLocal
Forbidden
Table 10. Supervision Application FAD
ED
01
957.130.932 V

354
71 / 354
The purpose of port view subsystem is to allow configuration, detailed alarm reporting and states condition
for both physical ports (SDHn, PDH) and HOA port. All the port views show:
active alarms and operational state of the port
NML assignment state of the port
the type of the port
the functional blocks contained in the port
In relation to the STMn port view specific menu, there are the following items:
Physical Media (PortPhysicalMedia*)
Performance (PortPerformance*)
Cross Connection (PortCrossConnection*)
1AA 00014 0004 (9007) A4 ALICE 04.10
Application FAD
EmlUsmSH5
Admin
EmlUsmSH5
Opera
EmlUsmSH5
Viewer
PortTPCfg
Forbidden
PortShowSupportingBoard
Forbidden
PortPhysicalMediaTxSsmQualityCfg
Forbidden
PortPhysicalMediaTxQuality
ConfigurationModifiable
Forbidden
PortPhysicalMediaSingleFiberCfg
Forbidden
PortPhysicalMediaPortShowOptical
LaserCfg
Forbidden
PortPhysicalMediaPortAlsMng
Forbidden
PortPhysicalMediaPdhLineLengthCfg
Forbidden
PortPhysicalMediaMspManagement
Forbidden
PortPhysicalMediaMspCommands
Forbidden
PortPhysicalMediaMsBerCfg
Forbidden
PortPhysicalMediaMenu
Forbidden
PortPhysicalMediaLoopMng
Forbidden
PortPhysicalMediaLoopCfg
Forbidden
PortPerformanceMenu
Forbidden
PortPerformanceDisplayHistData
Forbidden
PortPerformanceDisplayCurrData
Forbidden
ED
01
957.130.932 V

354
72 / 354

Port Management FAD configuration

Application FAD
EmlUsmSH5
Admin
EmlUsmSH5
Opera
EmlUsmSH5
Viewer
PortPerformanceConfigure
Forbidden
PortPdhTPCfg
Forbidden
PortNavigToTransView
Forbidden
PortMenu
Forbidden
PortLowOrderTpConfiguration
Modifiable
Forbidden
PortHighOrderTpConfiguration
Modifiable
Forbidden
PortCrossConnectionModifyShowTP
Forbidden
PortCrossConnectionModify
Forbidden
PortCrossConnectionMenu
Forbidden
PortCrossConnectionCreate
Forbidden
PortCrossConnectionBrowse
Forbidden
PortAlarmsMenu
Forbidden
PortAlarmsDisableRep
Forbidden
PortAlarmsConfigureRep
Forbidden
PortAlarmsCompleteInfo
Forbidden
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 11. Port Management Application FAD
ED
01
957.130.932 V

354
73 / 354
The Performance Monitoring domain covers the monitoring of gauge and counter values for trail
termination points, supervisory connection termination points, connection termination points and the
monitoring of protection switch events for a protection unit.
The threshold table selection dialog pops up if either a global configuration menu item has been selected
or if a threshold table is requested by the PM configuration main dialog. It serves as a display of the list
of existing threshold tables in the NE. The threshold tables are shown with name and granularity. With a
display filter the number of shown threshold tables can be decreased (PerfThreshold*).
EmlUsmSH5
Admin
EmlUsmSH5
Opera
EmlUsmSH5
Viewer
PerfThresholdSelectModifyCmd
Forbidden
PerfThresholdSelectDeleteCmd
Forbidden
PerfThresholdSelectCreateCmd
Forbidden
PerfThresholdSelectAttachCmd
Forbidden
PerfThresholdCreateModifiable
Forbidden
PerfPMConfigRemoveCmd
Forbidden
PerfPMConfigModifiable
Forbidden
PerfPMConfigAttachCmd
Forbidden
PerfCurrentDataModifiable
Forbidden
Application FAD
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 12. Performance Application FAD
ED
01
957.130.932 V

354
74 / 354

Performance FAD configuration

Equipment FAD configuration

The equipment domain deals with the management of the NE as a whole, its physical components,
equipment protection, power supply and External Points (Equipment*)
The Equipment FADs (Equipment*) are equivalent to the Equipment Overview FADs (EqpOv*); the
difference is in the Equipment display: with the graphical symbols for the Equipment FADs, without the
graphical symbols for the Equipment Overview FADs (but in a fast way).
EmlUsmSH5
Admin
EmlUsmSH5
Opera
EmlUsmSH5
Viewer
EquipmentSoftwareDescription
Forbidden
EquipmentShowSupportingEqp
Forbidden
EquipmentSetOutService
Forbidden
EquipmentSetModifiable
Forbidden
EquipmentSetInService
Forbidden
EquipmentSet
Forbidden
EquipmentRemove
Forbidden
EquipmentMenu
Forbidden
EquipmentBoardRemoteInventory
Forbidden
EquipmentRemoteInventory
Forbidden
EquipmentCableListConfiguration
Forbidden
EquipmentModify
Forbidden
EquipmentReset
Forbidden
EquipmentSubrackRemoteInventory
Forbidden
EquipmentUpgradeNE
Forbidden
Application FAD
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 13. Equipment Application FAD
ED
01
957.130.932 V

354
75 / 354
The External Points View is part of the Equipment domain. With the following functions, it is possible to
enable or disable the use of this view (ExternalPoints*).
Application FAD
EmlUsmSH5
Admin
EmlUsmSH5
Opera
EmlUsmSH5
Viewer
ExternalPointsMenu
Forbidden
ExternalPointsDisplayShowOutput
Forbidden
ExternalPointsDisplayShowInput
Forbidden
ExternalPointsDisplayShowAll
Forbidden
ExternalPointsDisplayMenu
Forbidden
ExternalPointsConfig
Forbidden
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 14. External Point Application FAD
ED
01
957.130.932 V

354
76 / 354

External Point FAD configuration

EPS FAD configuration

In the PDH Port View, the EPS Switches occur. In this case, there is no change in the visualized objects
and states. What is changed is the the name of the window that contains the view, which indicates the new
supporting board (EPS*)
EmlUsmSH5Admin
EmlUsmSH5Opera
EmlUsmSH5Viewer
EPSSwitchModifiable
Forbidden
EPSSwitch
Forbidden
EPSMenu
Forbidden
EPSCreationDeletionModifiable
Forbidden
EPSCreationDeletionDeleteAction
Forbidden
EPSCreationDeletion
Forbidden
EPSConfigure
Forbidden
EPSConfigurationModifiable
Forbidden
Application FAD
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 15. EPS Application FAD
ED
01
957.130.932 V

354
77 / 354
The following functions allows to handle the window and menu item of the Software Download view
(Download*)
Application FAD
EmlUsmSH5
Admin
EmlUsmSH5
Opera
EmlUsmSH5
Viewer
DownloadUnitsInfo
Forbidden
DownloadSimuManagement
Forbidden
DownloadSimuAlignUp
Forbidden
DownloadSimuAlignDown
Forbidden
DownloadSimuActivate
Forbidden
DownloadServersManagement
Forbidden
DownloadRestartNe
Forbidden
DownloadMibManagement
Forbidden
DownloadMenu
Forbidden
DownloadInit
Forbidden
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 16. Download Application FAD
ED
01
957.130.932 V

354
78 / 354

Download FAD configuration

Diagnosis FAD configuration

The following functions allows to handle the Diagnosis menu items. The Diagnosis menu allows to make
some diagnosis about the global NE state (Diagnosis*).
Application FAD
EmlUsmSH5
Admin
EmlUsmSH5
Opera
EmlUsmSH5
Viewer
DiagnosisViewRemoteInventory
DiagnosisViewMibDump
DiagnosisViewMenu
DiagnosisViewMaintenanceMemory
DiagnosisViewAnalogMeasures
DiagnosisShowPerformanceData
Menu
DiagnosisShowPerformance
Data24Hours
DiagnosisShowPerformance
Data15Minutes
DiagnosisShowAlarmsSubtree
DiagnosisShowAlarmsObject
DiagnosisShowAlarmsNEDomain
DiagnosisShowAlarmsNE
DiagnosisShowAlarmsMenu
DiagnosisShowAlarmsEquipment
Domain
DiagnosisMenu
DiagnosisListOfUnequippedPorts
DiagnosisListOfPerfPoints
DiagnosisListOfMenu
DiagnosisListOfLoopbacks
DiagnosisCompare
DiagnosisBrowseLogMenu
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 17. Diagnosis Application FAD
ED
01
957.130.932 V

354
79 / 354
Configuration FAD configuration
Application FAD
EmlUsmSH5
Admin
EmlUsmSH5
Opera
EmlUsmSH5
Viewer
ConfigurationPerformance
ThresholdsCrossingAlarms
Forbidden
ConfigurationPerformance
PerformanceThresholds
Forbidden
ConfigurationPerformanceMenu
Forbidden
ConfigurationPerformanceForced
PerformanceCollection
Forbidden
ConfigurationNETime
Forbidden
ConfigurationMenu
Forbidden
ConfigurationAlarmsSeveritiesSet
Forbidden
ConfigurationAlarmsSeveritiesMgt
Forbidden
ConfigurationThresholdTables
Forbidden

The following functions allow to handle the Configuration view (Configuration*).
Table 18. Configuration Application FAD
Board FAD configuration

The following functions allow to handle the Board view (Board*).
Application FAD
EmlUsmSH5
Admin
EmlUsmSH5
Opera
EmlUsmSH5
Viewer
BoardToPortAccess
Forbidden
BoardMenu
Forbidden
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 19. Board Application FAD
ED
01
957.130.932 V

354
80 / 354
7.2.9 QB3* FADs

The following list contains the FADs used for the QB3S network elements.
MS Spring FAD
The following list contains the FAD used for the MS Spring functionalities. MSSPRING (Muliplex Section
Shared Protection Ring) is a form of MS protection that is applicable in ring topologies and that has
efficiency benefits over subnetwork connection protection. The MSSPRING switch type can take the
following values:
bridge East
bridge West
bridge and Switch East
bridge and Switch West
idle.
Application FAD
MSSpring_switch
EmlUsm
SH5Admin
EmlUsm
SH5Opera
EmlUsm
SH5Viewer
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 20. MS Spring Application FAD
ED
01
957.130.932 V

354
81 / 354
The following list contains the FADs used for the OK buttons functionalities. In this way, it is possible
enable/disable the functionalities, allowing to the user to display the current values. The FADs allow to
handle the functionalities related to:
Measurements thresholds
Automatic Laser Shuttdown
Forward Error Correcting code
Fox equipment
Radio Protection Switch
Optical TP Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
Application FAD
EmlUsm
SH5Admin
EmlUsm
SH5Opera
EmlUsm
SH5Viewer
OK_EOWStatus
OK_MeasThresholds
OK_alsMgt
OK_apsConfig
OK_asapMgt
OK_eps
OK_extpConfig
OK_faultReportInhibit
OK_fecErrorMgt
OK_foxLink
OK_mpxSection
OK_opticalConfig
OK_perfThreshold
OK_probableCauseConfig
OK_repeaterBox
OK_rpsConfig
OK_showPerfPoint
OK_singleFecErrorMgt
OK_syncSourceConfig
ED
01
957.130.932 V

354
82 / 354

OK buttons FADs

Application FAD
EmlUsm
SH5Admin
EmlUsm
SH5Opera
EmlUsm
SH5Viewer
OK_t4Squelch
OK_tcaAllowed
OK_timeMgt
OK_timingSourceList
OK_tribStatus
OK_txSSMQuality
OK_vc4PayLoad
OK_videoCodecConfig
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 21. Ok Buttons Application FAD
ED
01
957.130.932 V

354
83 / 354
OK Sub Segment FADs
Application FAD
EmlUsmSH5Admin
EmlUsm
SH5Opera
EmlUsmSH5Viewer
OK_subSegmentMultiRepAdj
OK_subSegmentMultiRepMeas
OK_subSegmentParam
EmlUsm
SH5Admin
EmlUsm
SH5Opera
EmlUsm
SH5Viewer
alarms_AllowInhibit
alarms_Reset
EmlUsmSH5Admin
EmlUsm
SH5Opera
EmlUsmSH5Viewer
mibAlign
mibAlign_Down
mibAlign_GlobalDown
mibAlign_Up
mibCompare
Table 22. Ok Sub Segment Application FAD
Alarms FADs
The following list contains the FADs used for the Alarms functionalities.
Application FAD
Table 23. Alarm Application FAD
Mib FADs
The following list contains the FADs used for the MIB functionalities.
1AA 00014 0004 (9007) A4 ALICE 04.10
Application FAD
Table 24. Mib Application FAD
ED
01
957.130.932 V

354
84 / 354

The following FADs allow to handle the functionalities related to the Submarine Segment.
Timing Source FADs

The following list contains the FADs used for the Timing Source functionalities.
Application FAD
EmlUsm
SH5Admin
EmlUsm
SH5Opera
EmlUsm
SH5Viewer
timingSource_AddRm
timingSource_Select
Table 25. Timing Source Application FAD
Generic FADs
The following list contains the FADs used for the functionalities related to:
Multiplex Section Protection
Cross Connect Panel.
1AA 00014 0004 (9007) A4 ALICE 04.10
Application FAD
EmlUsm
SH5Admin
EmlUsm
SH5Opera
EmlUsm
SH5Viewer
accessState
amsInsertion
autoPreEmphasis
changeBoard
channelPower
equipUnequipPort
forceT4Squelch
loopback
memoryAccess_clear
msp_Switch
performance_forceCollect
resyncAlarms
rps_Switch
secondaryAlarms
ssmAlgorithm
ED
01
957.130.932 V

354
85 / 354
EmlUsm
SH5Admin
EmlUsm
SH5Opera
EmlUsm
SH5Viewer
ssuManagement
subrack
xcPanel
Table 26. Generic Application FAD
7.2.10 RM constraints FADs

In the presenece of RM, the operator has some additional constraints. If RM makes a supervision, the
normal operator is disabled for a lot of operations (connection creation, ports modifications, etc.). The FAD
IgnoreNMLassignment could be added only for the superoperators enable to work during the RM
supervision.
1AA 00014 0004 (9007) A4 ALICE 04.10
Application FAD
EmlUsm
SH5Admin
EmlUsm
SH5Opera
EmlUsm
SH5Viewer
IgnoreNMLassignment
Forbidden
Forbidden
SetDomainModifiable
Forbidden
Forbidden
SetDomainNmlAssignmentModifiable
Forbidden
Forbidden
ED
01
957.130.932 V

354
86 / 354

Application FAD
7.3 Forced Logout Option

It Forces the logout of users. May be filtered by station using the Select WS button.
When clicking on the option, the following window is displayed:
Figure 24. Forced Logout Window

To logout a user:
Select the user in the list.
Click on the Logout pushbutton.
1AA 00014 0004 (9007) A4 ALICE 04.10
The details of the processes associated to an user can be displayed:
Select the user in the list.
Click on the Details pushbutton: the following window is displayed.
ED
01
957.130.932 V

354
87 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 25. Details of user processes
ED
01
957.130.932 V
354
88 / 354
7.4 List Current Login Option

List the current logins. May be sorted by station using the Select WS button.
Indications displayed are the name and profile of the users logged, the source and the date/time of the
loggin, where they are logged .
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 26. List Current Login window
ED
01
957.130.932 V

354
89 / 354
7.5 List Unsuccessful Login Option

List the history of unsuccessfull login attempts. May be sorted by station using the Select WS button.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 27. List Unsuccessful Login window
ED
01
957.130.932 V

354
90 / 354
7.6 List Successful Login Option

List the history of logins. May be sorted by station using the Select WS button.
Same indications are given as for current logins, plus duration and the date/time of log out. The current
login is also displayed (still logged on).
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 28. Successful logs
ED
01
957.130.932 V

354
91 / 354
7.7 List Operators Option

The function is global for all the WS, the Select WS button is not available.
This function lists all the user accounts with their assigned profile and group.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 29. List the users
ED
01
957.130.932 V

354
92 / 354

7.8 Add Operator Option

The function may be invoked only from the Master WS. It is global for all the WS, the Select WS button
is not available.
In order to add a new operator and its User Profile it is necessary define or specify:
the
user informations:
User Name,
Password,
Real Name,
Profile as shown in next figure;
the include target of the new user using the Access Right Definition of the ACA graphical tool (see
7.2.4).
New 1353SH user accounts can be created and assigned a profile by the administrator. By default, one
default user account is created for each predefined profile. The following list gives for each profile the
corresponding abbreviation used as security level in the command syntax to assign a specific profile to
an user account:
Profile
User profile
UNIX group
User Name
OS administrator
SH and EML administrator
EML constructor
EML operator
Look only operator
osadmin
admin
emlconst
emlopera
viewer
gadmin
gadmin
gemlcst
gemlope
gviewer
axadmin
axrmaint , axemladm
axemlcst
axemlope
axviewer
By default, profile is equal to viewer, but must absolutely be changed.

All the SH operators can log on any SH slave station (EML and PRES type) .
The main syntax constraints are:
rules for user name: 3 to 8 characters, 1st character must be a letter. If the length is greater than 8
characters it will be truncated to 8.
rules for password: any character,6 to 8 characters (blank not allowed). If the length is greater than
8 characters it will be truncated to 8.
rules for real name: 30 characters max length, alphanumeric characters only. If the length is greater
than 30 characters it will be truncated to 30.
The user name will also be used for the home directory of the user found under the /users directory.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V

354
93 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 30. Create user
ED
01
957.130.932 V
354
94 / 354
7.9 Remove Operator Option

The administrator is able to remove any created user account, not the predefined users.
The user to delete must be not logged on.
All the stations must be reachable, if not the command will have to be run again when they are.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 31. Remove an user
ED
01
957.130.932 V

354
95 / 354
7.10 Change Password Option
The administrator can change any users password. The new password will be effective on all the stations.
The rules for this password are: any character,6 to 8 characters. If the length is greater than 8 characters
it will be truncated to 8.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 32. Change of users password
ED
01
957.130.932 V

354
96 / 354


7.11 Set Max Operators Number

The following function allows to define the maximum number of simultaneous dtsessions (WS and
GOGlobal sessions).
Figure 33. Set max operators number

When an operator (not administrator) is logging to SH5 the system executes the Max Operator Number
Control. If the limit found exceeds the Current Value (in this figure is 100) the login will be not allowed
with the warning:
There are too many users on system. Try later.
1AA 00014 0004 (9007) A4 ALICE 04.10
The administrator clicking on the Apply button sends the new value to the Master and to all the slave
workstations.
ED
01
957.130.932 V

354
97 / 354
The Set Personal Printer function is local for a workstation and for a user: each user can set its printer
command or double click on a printer to select it.
The option dialog, shown in the figure below, allows the users to Apply their selections or Close the window.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 34. Set Default Printer window
ED
01
957.130.932 V

354
98 / 354

7.12 Set Personal Printer

8 SYSTEM TRACE & LOG MANAGEMENT

8.1 SMF/Command/Event Logs Management/Visualization
8.1.1 General
The Log files are written by administration script in order to archive meaningful operations in the story of
the SDH Manager system. They are not to be confused with trace files which are cyclic files written by
application programs for debug purposes.The SDH Manager administration log is based upon UNIX
syslog.
There are 4 types of log :
Event logs: generated by the NE via the EMLIM.

Command logs: generated by operators via PNMUSM and EMLUSM.
System logs (or SMF Logs): generated by SMF functions and apman.
The different kind of SMF log files are: SMF and StartStop as log of operator commands, ApmanIM
and lpc (local process controler) as log of system commands, and for each one the Overflow as
extension log file if necessary.
Unix logs : other logs produced by Unix processes , ftp , mail ...
The System logs are centralized on the Master WS, while the other log files are located on the WS where
they have been generated.
8.1.2 Management of log files
a)
Log line format
YYYY MMM DD HH:MM:SS hostname 1353SH/subsystem username text
Error levels
The error levels used in the SDH Manager are the following:
err: Error. The operation has not been completed.

warning: Warning messages. There is a warning but the operation has been completed.
notice: conditions that are not error conditions, but should possibly be handled specially.
Beginning and end of operation.
N.B.
The error level (err, warning,notice) is not reported in the log.
Subsystems
1AA 00014 0004 (9007) A4 ALICE 04.10
The following subsystems are used :
b)
ED
user
log
agent
backup restore
operation
tnm
configuration
start stop
maintenance
plugin
Files state
01
957.130.932 V

354
99 / 354
Current log (file name file.log)

Overflow log (file name file.log.old)
This file is automatically created by the log daemon (axSyslogd). When a log file exceeds a
predefined size, the log file is renamed with the .old extension.
axadmin is notified by mail when file is created. The message is xxx.old log file created, please
archive log.
Saved log (file name name.gz). There can be several saved log files saved at different dates. Saved
log files are compressed by gzip. The file name (name) is choosen by the user.
Temporary log (file name /tmp/axtmp.name.date). It corresponds to saved log files decompressed
for visualization. They are removed after usage.
Axsyslog daemon (mv)

current log
overflow log
saving (mv)
saving (mv)
saved log
removing (mv)
visualization from
slave station (cp)
visualization from
slave station (cp)
visualization (cp)
temporary log
automatic destruction
Figure 35. Logs states

As a result, the original file may be mv removed , or cp duplicated
Current and overflow log files are stored into $DIR1353SH/maintenance/log/process_file.
Saved log files are stored on the master station into $DIR1353SH/maintenance/log/saved/ws_name/logs.
c)
Log Handler Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
The Log handler tool can be configured by the OS administrator. The configuration file is called
axsyslog.cfg and is located under $DIR1353SH/conf/. The format is of the form tags:value:
ED
max_size: maximum size of log file before it is renamed in .old,

smf_log_file: name of the log file,
fifo: name of the fifo file used to communicate with syslogd,
facility_smf: facility used by SMF error logging function,
facility_super: facility used by super.
01
957.130.932 V

354
100 / 354

Several logs files exist (smf log, apman log,...), they can be in the 4 different states (see Figure 35. ):
8.1.3 Access rights

SMF Command
Access rights
SMF logs management
admin , on Master station
SMF logs visualization
Command logs management
Command logs visualization
all users
Event logs management
Event logs visualization
all users
Table 27. Trace & Log Management: Access rights for different User Profiles
8.1.4 Log Tools

Logs Management functions can be accessed through System Trace & Log Management option.
Listed below are the tool names and a brief description.
1AA 00014 0004 (9007) A4 ALICE 04.10
Command
Description
View Current
logs
To list the current&overflow log records.
Info
To give info on the log files.
Filter
To apply criterium selection on the current log records.
Show
To display with criterium selection the current log records.
Save
To save in new file the displayed current log records.
Print
To print the displayed current log records.
Mv log to save area
To save the current log files.
View saved logs
To list and view the content of the saved log files.
Info
To give info on the log files.
Filter
To apply criterium selection on the saved log records.
Show
To display with criterium selection the saved log records.
Save
To save in new file the displayed saved log records.
Delete logs
To remove a saved log file.
Table 28. Trace & Log Management Options
ED
01
957.130.932 V

354
101 / 354
For each type of log, a common graphic user interface offers to view records (with filter) from the log files
and to create, to view or to remove archive files.
When clicking on one of the following options, the window given in Figure 36. is displayed:
SMF Logs Management,

Command Logs Management,
Event Logs Management.
Figure 36. Logs Management

N.B.
a)
The window is identical for the three options except the status bar.
View Current Logs option
The current & overflow log files are concerned.

Visualization of these logs may be also accessed using the direct SMF command logs visualization: SMF
logs visualization, Command logs visualization or Event logs visualization.
When clicking on this option, two types of windows can be displayed depending on the log types.
1AA 00014 0004 (9007) A4 ALICE 04.10
For the System Logs, the following window is displayed:
ED
01
957.130.932 V

354
102 / 354

8.1.5 SMF/Command/Event Logs Management (User Interface)

Figure 37. System Logs visualization
1AA 00014 0004 (9007) A4 ALICE 04.10
For the Command and Event Logs, the following window is displayed:
Figure 38. Event/Command Logs visualization

The upper field lists all the files which can be visualized.
ED
01
957.130.932 V

354
103 / 354
For System logs: date, ws, subsytem, operator, text and Newst record first,
For Command and Event logs: Display details and Newest record first.
Show pushbutton: to display the content of the selected file(s). The operator can select the file(s) to
visualize. When several files are selected, all the records of these files are listed togheter (as the same
records of an unique file) and are sorted by date.
Figure 39. View Logs Show
1AA 00014 0004 (9007) A4 ALICE 04.10
The Log Visualization is limited to the first 1000 records, if the real size exceeds a message warns the
operator. Click on Stop to continue.
ED
01
957.130.932 V

354
104 / 354

The check buttons are used to limit the number of information displayed and are the following:

Figure 40. View Logs 1000 records excedeed

The log visualization window includes pushbuttons:
Info pushbutton: gives information on size and location of the selected files.
Figure 41. View Logs Info

N.B.
If no files are selected, the information displayed concern all log files.
1AA 00014 0004 (9007) A4 ALICE 04.10
Filters pushbutton: It is possible to define a multicriteria sorting filter. The number of criteria is not
limited. The logical result is a AND operation between the different criteria. The possible criteria are:
ED
01
957.130.932 V

354
105 / 354
logs :
Date
Operator
Subsystem
Text search
Workstation
For Command logs :
Date
Operator
USM
User label
Ne Directory
Equipment Id
NE element
NE group Id
SDH NE Id
Perf coordinator Id
For
Event logs :
Date
Emlim name
Event type
User label
Text search
NE supervision coordinator Id
Command name
Status
Text search
Process Id
When a filter is selected, it is added in the current window. A field is associated to the filter in which
a value may be entered.
After confirmation for rescanning, the sorting may be displayed by clicking on Ok.
Figure 42. View Logs Filters

Save pushbutton: the result of the display, with filtering options, may be saved as a file, which can
be accessed only with unix command (vi ...) . The Save as window displays the already existing files
previously saved.
1AA 00014 0004 (9007) A4 ALICE 04.10
Choose the path and enter the name for the new file.
ED
01
957.130.932 V

354
106 / 354

For SMF

Figure 43. View Logs Save As

Print pushbutton: to print the result of the display, with filtering options.
Quit pushbutton: to quit.
When selecting a file in the list box of the visualization window (see Figure 37. or Figure 38. ), a menu
can be opened by clicking on the right button of the mouse. Two options are available:
Analysed fields option to display the value of all fields,
Figure 44. View Logs Analyzed fields
b)
Expand/Shrink option to limit the display to the main characteristics of the log file (first line).
View saved logs option
1AA 00014 0004 (9007) A4 ALICE 04.10
The user can list the saved log files with criteria selection. Only the files saved using the command Move
log to save area option can be visualized, not the files saved with the Save pushbutton of the Log
visualization window.
The user can select the saved log files to visualize.
The display is the same as the one for the current logs visualization, and the options have the same effect
as for the current logs visualization.
ED
01
957.130.932 V

354
107 / 354
The visualization of saved files requires the creation of temporary uncompressed files use the Info
button.
Temporary files are also created for viewing log files located on a remote WS.
At the end, temporary files are automatically removed.
c)
Move log to save area option
When clicking on this option, the following window is displayed.
Figure 45. Move log to save area option

The list of files in the states normal and overflow is shown to the user. The user selects the file to save
and gives it a name.
1AA 00014 0004 (9007) A4 ALICE 04.10
Selected files are compressed (gzip) and moved in $LOG_DIR_SAVED on the master station, they dont
appear any longer in the window Move log to save area.
ED
01
957.130.932 V

354
108 / 354

d)
Delete logs option
Saved log files can be destroyed: select the file(s) and click the Delete button. The files deleted can not
be recovered, but the backup facilities may be used to keep logs file(s) on disk or tape (see
Backup/Restore SMF feature).
Figure 46. Delete logs option

e)
Quit Logs Management option
This option closes the Log Management window.

8.1.6 SMF/Command/Event Logs Visualization (User Interface)
1AA 00014 0004 (9007) A4 ALICE 04.10
The window displayed when clicking on these options are identical to the ones described in paragraph
8.1.5 c).
ED
01
957.130.932 V

354
109 / 354
8.2 Failure Management
8.2.1 General
For some maintenance needs, analysis of possible corrections, the SDH Manager product is equipped
with an error detection software which enables to catch the error detected by the system and the context
in which the error has appeared. The backup of these errors is entirely automatic, it is used for errors of
medium and major (crash) severities. Quality is not only linked to detection and correction of this errors,
it is also the result of minor errors detection which dont cause the service to stop. This is in that case
frequently ergonomic type abnormalities or functional malfunctioning. For this kind of abnormality, the
SDH Manager gives the administrator the ability to edit system fault reports.
8.2.2 Fault Report Content
For each (automatic or manual) data capture, a header file is generated detailing information about the
captured data. The structure of the header file is as follows:
Date/Time:
date and time of the anomaly.
Submitter:
application Manager or the SDH Manager system administrator username.
Headline:
name of rogue process if called by the Application Manager or user comment.
SH_Version: result of calling axversion.
Copied Files: the list of files copied together, after capture, with the date, time, size and file access
permissions ( ll unix command).
There are three failure subdirectories maintained under the maintenance/failure directory.
The delay between successive invocation of the failure capture process, manual or automatic, is 5
minutes.
8.2.3 Sequence of events when a process exits abnormally
When a process terminates abnormally, the Application Manager (APMAN) identifies the failed process
and invokes the capture failure script together with the identity of the failed process automatically.
The script will first determine the caller (i.e. APMAN or system administrator).
The name of the new directory will reflect the current date and time, so for example if the process failure
occurred on the 18th March 1997 at 11:05 then the name of the new directory will be 199718031105.
core file : is only captured when APMAN invokes the data capture process, it moves the file from
core/processname/core to the new directory
trace, dataflow, error and output files : are captured from the trace/ directory, each file is first copied from
the trace directory to the new directory.
log files : are captured from the log/ directory, each file is first copied from the log directory to the new
directory.
1AA 00014 0004 (9007) A4 ALICE 04.10
persistent files : are captured from the eml/nefamily/netype/data/*.cfg and pnm/data/NE.db.

The script will then create a header file which contains information about the date and time the capture
process was invoked (i.e. time of failure), the caller (i.e. APMAN or system administrator), a headline
indicating the rogue process if present, the version of the SH as a result if executing axversion and a list
of all the files captured.
ED
01
957.130.932 V

354
110 / 354

All the users can access this function, via the SMF, from any station.

8.2.4 Failure Tools

Failure Management functions can be accessed through System Trace & Log Management feature.
Listed below are the tool names and a brief description.
SMF Command
Capture Data
Tool Description
Failure capture process captures the core (only when activated by APMAN), trace and dataflow files.
Manage
Failure Displays the current list of failures on the specified machines.
Directory
Lock
Allows specific failure directory to be locked (prevent deletion

from new failure).
Unlock
Allows specific failure directory to be unlocked .
Backup
Allows selective backup of failure from specified machine to

master workstation.
Remove
Allows selective removal of failure directory.
Manage Backup List of backup failure data on the master workstation.

Failure Directory
Remove
Allows selective removal of the backup failure data on the

master workstation .
Save
Allows selective backup failure data files to be stored on to

tape media .
8.2.5 Failure Management (User Interface)
1AA 00014 0004 (9007) A4 ALICE 04.10
When clicking on the Failure Managemernt option, the following window is displayed:
Figure 47. Failure Management
ED
01
957.130.932 V

354
111 / 354
Capture Data option
The capture process may be invoked either automatically via APMAN or manually by the OS system
administrator.
Figure 48. Failure Management Capture Data

Select the station(s) and click on the Capture Data pushbutton.
Quit with the Main Menu pushbutton.
N.B.
Invoking the capture process manually will NOT capture any process core files.
This tool will perform the following operations:
Examine the MAX_FAILURE parameter in the failure_handler.cfg file. If this parameter is set to zero,
the script will terminate else if the parameter is greater than zero the script will continue.
Get the current date and time and compare it with the most recent data capture. If the time difference
is greater than a specified delay, the script will continue. Otherwise the request is denied and the
script will terminate.
Store the date and time information.
Create a new directory under $DIR1353SH/maintenance/failure/yyyymmddhhmm.
Copy into the yyyymmddhhmm directory all the necessary files.
Create the header file.
Write to the header file.
If the number of present directories is greater than the maximum number specified , then a cleanup
script is initiated, removing directories in chronological order until the directories number equals the
maximum number specified.
1AA 00014 0004 (9007) A4 ALICE 04.10
Contrary to the automatic catch, the manual catch will only perform a partial capture.
b)
Manage Failure Directory option
To access the failures captured on the stations.
ED
01
957.130.932 V

354
112 / 354

a)

View Failure directories on any Workstation
To view the failures captured on all the stations or on the local workstation only. For local station only, select
the station.
Figure 49. Failure Management Manage Failure Directory

Some actions may be launched on the directory: select first the directory, then pop up the menu of actions
using the right button of the mouse and select an action.
Lock / Unlock of Failure directory
To lock or unlock the failures captured on any workstation. Locking a directory prevents from removing.
The locked directories are highlighted.
Remove Failure directory
To remove a failure directory on any workstation. The directory must be unlocked.
Save on tape the Failure Directory Backup
To save the backup data from the master workstation on to a tape .Format is a tar compressed with gzip.
c)
Quit Failure Management option
1AA 00014 0004 (9007) A4 ALICE 04.10
This option closes the Failure Management window.
ED
01
957.130.932 V

354
113 / 354
8.3 Trace Management

All the users can access to this function, via the SMF, from any station.
8.3.1 Traces Management tools
The following table summarizes the tools provided to manage traces:
SMF Command
Tool Description
Change Trace Level
To set the trace level of each apman process
Reset Cyclic Traces
This tool allows to empty all circular trace files
Table 29. Trace Management: tools
8.3.2 Trace Management (User Interface)

When clicking on the Trace Managemernt option, the following window is displayed:
Figure 50. Trace Management
The administrator is allowed to modify the level of traces to ease the diagnostic of problems under special
circumstances. On each station, each component has its own trace configuration file, named trace.cfg,
under a specific directory.The following table gives the location of the trace configuration files:
1AA 00014 0004 (9007) A4 ALICE 04.10
Component
File location
emlim : netype of nefamily
1353sh/eml/nefamily/netype/conf/
emlusmsh: type_version
1353sh/eml/usmshtype/conf/
system_monitoring
1353sh/apman/conf/
xcc
1353sh/necom/conf/
pnmim
1353sh/pnm/conf/pnmim/
pnmusm
1353sh/pnm/conf/pnmusm/
ED
01
957.130.932 V

354
114 / 354

Component
File location
dnmim
1353sh/dnm/conf/dnmim/
dnmusm
1353sh/dnm/conf/dnmusm/
secim
1353sh/sec/data/secim/
lss
1353sh/sec/data/lss
ascurim
1353sh/as/data/ascurim/
ascurusm
1353sh/as/data/ascurusm/
ashistim
1353sh/as/data/ashistim/
ashistusm
1353sh/as/data/ashistusm
perfstorage
1353sh/eml/perf/conf/
ashistim
1353sh/as/data/ashistim/
ashistusm
1353sh/as/data/ashistusm
simcon
1353sh/simulator/simcon/data
elm_browsing
1353sh/elm/data/config/browsing
elm_management
1353sh/elm/data/config/management
Table 30. Trace Management: trace configuration pathnames

N.B.
In the above table the OSOS interface components are not reported
The default setting for trace level is the following:

TRACE_FILTERS
{
ALL
{
ALL 1 2 5
}
}
1AA 00014 0004 (9007) A4 ALICE 04.10
Maximum level for traces is obtained with the following setting:

TRACE_FILTERS
{
ALL
{
ALL 1 2 3 4 5 6 7
}
}
N.B.
ALL 1+ is equivalent to ALL 1 2 3 4 5 6 7 in previous setting.
The following table gives the information traced according to the trace level specified:
ED
01
957.130.932 V

354
115 / 354
Information
error statuses (raising, ignoring, clearing)
process events (init, shutdown, I/O)
process I/O dataflow
method calls and results
platform calls and results (system, HPOV, SGBD, ...)
debugging
specific
Table 31. Trace Management: Trace levels

When enabled, dataflow tracing (level 3), is issued, along with process events (level 2) in dedicated trace
files with extension .dataflow .
a)
Change Trace Level option
The trace level may be chosen for any agent(s) of any station(s):
Figure 51. Trace Management Change Trace Level

Select the station, the process, and the levels.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on Main Menu to quit, or

Click on Change Trace Level to apply
The result of action is shown in a new Change Trace Level window:
ED
01
957.130.932 V

354
116 / 354

Level

Figure 52. Trace Management Change Trace Level Confirmation

b)
Reset Cyclic Traces option
This tool allows to clear all the circular traces located under 1353sh/maintenance/trace.
To save traces use the axcaptureData command (see Failure tools paragraph) before resetting.
This command is useful to get a clean situation, for instance in order to make easier the analysis of
information given in traces for a next problem.
Figure 53. Trace Management Reset Cyclic Traces

Clicking on the Reset Cyclic Trace pushbutton reset on all the stations all the circular trace files with
extension .trace, .dataflow, .err, .out .
A new window opens displaying as result of action all the resetted files:
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 54. Trace Management Reset Cyclic Traces Confirmation

c)
Quit Trace Management option
This option closes the Trace Management window.
ED
01
957.130.932 V

354
117 / 354
8.3.3 Traces visualization
The tool allows to visualize the trace file selected either dynamically (all the events from the moment when
the command was launched) or statically (all the events up to the moment when the command was
launched). A multi selection will open several windows.
Figure 55. Trace visualization

The processes which can be visualized are: pnmim, all pnmusm, all emlusm, all xcc, all emlim.
1AA 00014 0004 (9007) A4 ALICE 04.10
Example: dynamic view of pnmusm.trace on station claudia
ED
01
957.130.932 V

354
118 / 354

All the cyclic trace, .trace files, for all the stations are offered.

Figure 56. Trace visualization Example

The static view of trace file proposes also to the operator a Search menu with options:
Find: to locate a string, highlight in red colour all the occurences of the string in the displayed window.
Clear: to cancel the result of the previous Find.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 57. Search in Trace file

It is also possible to visualize the trace file about the software download operation as displayed in the
Figure 58.
ED
01
957.130.932 V

354
119 / 354

Figure 58. View of the trace file
1AA 00014 0004 (9007) A4 ALICE 04.10
By clicking on the Show button, the operator views the software download trace file containing log
information, as displayed in the next Figure.
ED
01
957.130.932 V

354
120 / 354

Figure 59. Software download trace file

Note: The operator can not set the trace levels for all software download file log.
8.3.4 Traces saving
There is no specific tool to save traces, this must be done using the Failure tools of SMF and proceeding
as follow :
Capture data to get an image of the trace, indeed performs a complete capture of all the trace files
: traces, logs ... ,
Manage Failure Directory to make to make a Save on tape
1AA 00014 0004 (9007) A4 ALICE 04.10
For more informations, refer to the Failure Management chapter.
ED
01
957.130.932 V

354
121 / 354
The cleanup facilities are accessible to the administrator via the SMF command, from the Master station
only.
Moreover periodic system actions (cron) may be also run to avoid excessive increase of data collected
by the system or the operators.
8.4.1 General
The safety of 1353SH system needs to limit the number and size of files created for management purpose.
The size of some current operating files is limited such as logs and traces , as well as their number since
it is associated to the number of processes. For some others, there is no control, for example the core
files.The OS administrator is also able to create some files or directories which size can not be controlled
easily. So the cleanup tool allows the administrator to look at these extra files and delete them from time
to time.
The cleanup task concerns also the databases for alarm, maps, perfs.
8.4.2 Cleanup tool
The files to clean are classified in domains. The operator gets an overview on the OS looking globally at
all the unwanted files and he can decide a cleanup action. Such an action is performed globally on all the
files of a domain for a station.
Backup
Directories created for backup and restore operations, located on the master station only under
/usr/1353sh/backup, /usr/1353sh/restore, /tmp/restorediff, /usr/1353sh/maintenance/backup.
Log
Concerns the PMlogfile, the.old log files, and all the.log files under save, located in
/usr/1353sh/maintenance/log on a station.
Failure
Concerns the directories located on /usr/1353sh/maintenance/failure on a station.
Install
Concerns all the files, except the axinstallGui, located in /alcatel/DEPOT on a station.
Trace
Concerns all the files.trace,.err and.dataflow in the 1353sh run time tree of a station.
Core
Concerns all the core files on a station : core of SH processes within 1353sh/maintenance/core,
and core resulting of panic unix error within /var/adm/crash.
SEN performance
Concerns all the files /usr/1353sh/rmplug/pm/data/emlDom_on a station.
1AA 00014 0004 (9007) A4 ALICE 04.10
8.4.3 Cleanup (User Interface)

When clicking on the Cleanup option, the following window is displayed:
ED
01
957.130.932 V

354
122 / 354

8.4 Cleanup

Figure 60. Cleanup

a)
Cleanup pushbutton
Before starting a cleanup action, the operator can get more informations about the files to delete:
Select the domain(s), select eventually the station(s), and click on Details to get the complete list of files
for the stations.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
To select workstations, use the All and Clear pushbuttons to select or deselect all workstations
(respectively).
Figure 61. Cleanup Details
ED
01
957.130.932 V

354
123 / 354
b)
Clean pushbutton
To perform the cleanup action, select the domain(s), select one station, and click on Clean.
N.B.
If no domain and/or no station is selected, a dialogue box is displayed to remind the operator
what to select.
Figure 62. Cleanup Clean Confirmation

Click on Yes to confirm: starts the action.
Figure 63. Cleanup Clean Completed

Click on Dismiss to close the window and quit.
8.4.4 Cron actions
Periodic tasks are defined into the configuration file /usr/1353sh/tools/cleanup/conf/cleanup.cfg. It
uses the crontab command and can be changed only by an administrator with unix command.
The default configuration is:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
removing of SEN performance files : files older than 3 days (for 15mn counter) and than 7 days (24h
counter) are removed
removing of Failure directory older than 1 month.
01
957.130.932 V

354
124 / 354

Click on Dismiss to close and return to main window.
8.5 Dump Screen

This tool allows the operator to create and manage screen shots.
The main menu is as follows:
Figure 64. Dump Screen window
8.5.1 Open option

This option is used to manage already existing screen shots.
1AA 00014 0004 (9007) A4 ALICE 04.10
When clicking on this option, the following window is displayed:
Figure 65. Dump Screen window Open
ED
01
957.130.932 V

354
125 / 354
The following options are available:

Open option: opens the screenshot selected in the list,
Print option: print the screenshot selected in the list,
Delete option: deletes the screenshot selected in the list.

8.5.2 Capture option
Figure 66. Dump Screen window Capture

The following options are available:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Pick window option: used to manually create screen shot of a window.
Enter the name of the screen shot in the Name : field.
Select the Pick Window option: the cursor becomes a cross.
Click on the window to capture.
Get Screen option: to create a screen shot of the whole screen.
Enter the name of the screen shot in the Name : field.
Select the Get Screen option: the capture is immediate.
Select Window option: displays the list of active windows from which the operator can create screen
shots.
01
957.130.932 V

354
126 / 354

Figure 67. Dump Screen window Select Window

The list displays the windows currently active.
From the windows name displayed in the list, the operator can:
rescan the windows list (Rescan pushbutton),

close the Capture window (Close pushbutton),
print a window (Print pushbutton),
create a screen shot of a window (Get pushbutton): enter first a screen shot name in the Name field.
8.5.3 Quit option
1AA 00014 0004 (9007) A4 ALICE 04.10
This option closes the emlCore Capture window (see Figure 64. ).
ED
01
957.130.932 V

354
127 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V
354
128 / 354

9 BACKUP/RESTORE FEATURE
9.1 Overview
9.1.1 General
The backup/restore feature allows to save the applicative data of the 1353SH. This feature is not to be
confused with the full backup disks1353SH feature.
The backup/restore unit is defined by a couple (workstation, data type), each data type can include several
subsets of data types.
The data types are the following:
Network data (called Network):
DNM data (saved Maps),

NE configuration data (EMLIMs persistent data).
Performance monitoring (called PM):
PMV database (PM_Main),

SEN_IM Performance files (PM_SEN). These files contain performance counters for RM. In SH
standalone SEN_IM Performance files are not managed.
SEC database files (called SECdb),

SWDL Software Dowload Manager and Server data (called Swdl),
Operating system (called Unix):
Network (UNIX) data: Users, network configuration, Xterminal configuration, printer

configuration, startup/shutdown/periodic actions configuration, licenses configuration,
configuration of products for remote maintenance service, remote display service
configuration.
Operators (Users) (called Operator): home directory of the created and predefined 1353SH users.
Logs (called Log),
1353Sh configuration (called Sh).
Some functional domains are only pertinent for the 1353SH master workstation.
The backup/restore feature copies tar files to or from the backup tree of the SMF master workstation.
9.1.2 Workstation distribution
1AA 00014 0004 (9007) A4 ALICE 04.10
The backup in the 1353SH is made for a workstation and for a functional domain. The backedup data
are collected on the backedup workstation and then copied to the master workstation of the 1353SH.
ED
01
957.130.932 V

354
129 / 354
database


Figure 68. Backup operation on distributed workstation

The master workstation is the target of the backup operation and the source for the restore operation. A
particular case is when the master workstation is the backuped or restored workstation.

database

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 69. Restore operation on distributed workstation
ED
01
957.130.932 V

354
130 / 354

9.1.3 Destination selection
axrestore tape
Ws 3
LoadRestore
Tape
Restore tree
(on master
WS)
SaveBackup Backup tree

(on master
WS)
Ws 2
axbackup
axrestore
Ws 1
axbackup tape
Figure 70. Destination selection

The graphical interface provides an access to the commands axbackup, axbackup tape, axrestore,
axrestore tape.
The tape device on which are stored the backuped data is defined with the file TAPE_SERVER located
under $DIR1353SH/conf/. The default value is the tape device connected to the Master station.
The environment variable TAPE_SERVER is set to the contents of the configuration file
$DIR1353SH/conf/TAPE_SERVER. By default, the contents of this file is localhost ( i.e the tape drive is
located on the SH master workstation ).
It is suggested in OSresilience configuration to define as tape server one of presentation
workstations.
9.1.4 Backup tree
1AA 00014 0004 (9007) A4 ALICE 04.10
A specific file tree (see Figure 71. ) rooted on $DIR1353SH/backup on the master workstation is defined
to receive backuped data from the backuped workstation and to receive data to restore from a media.
ED
01
957.130.932 V

354
131 / 354
<workstation 1>
Ntwk Unix
<workstation 2>
Log
Op
Sec

$DIR1353SH/backup/.smftkbackup/
<workstation n>
Sh
Swdl
PM
Al
<Al_backup>.tar
INFO file
<Ntwk_backup>.tar
<PM_backup>.tar
INFO file
INFO file
<Unix_backup>.tar
<Swdl_backup>.tar
INFO file
INFO file
<Log_backup>.tar
<Sh_backup>.tar
INFO file
INFO file
<Op_backup>.tar
INFO file
<Sec_backup>.tar
INFO file
Figure 71. Backup tree

N.B.
Several tar files can exist in the directories (Unix directory for example).
1AA 00014 0004 (9007) A4 ALICE 04.10
When the data are in the backup tree, it is possible to save them on a tape. At the opposite, it is also
possible to read data on a tape to initialize the backup tree.
ED
01
957.130.932 V

354
132 / 354

9.2 Backup/Restore (User interface)

9.2.1 Access rights
Only the administrators (group admin) can access to these tools, from the Master station.
SMF Command
Access rights
Backup
Restore
Remotization Enable/Disable
Table 32. Backup&Restore: Access rights for different User Profiles
9.2.2 User Interface

If the operator is on a distributed workstation and the SMF runs locally, the backup/restore feature is not
available (the option is not present in the MAIN SMF menu). When the SMF is started, a window is
displayed asking if the SMF must run locally (for a distributed workstation) or on the master workstation.
To have access, to the backup/restore operation, the option on the Master must be selected.
1AA 00014 0004 (9007) A4 ALICE 04.10
When clicking on the option, the following window is displayed.
Figure 72. Backup/Restore window
ED
01
957.130.932 V

354
133 / 354
Tool Description
Backup
To backup the data for OS,1353SH application
Restore
To restore the data for OS,1353SH application

SMF Command
Remotization Enable/ To allow backup remotization (refer to section Remotization

Disable
Enable/Disable Option in this chapter)
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 33. Backup&Restore: Tools description
ED
01
957.130.932 V

354
134 / 354
9.3 Backup Operations

Prerequisite:
the backuped workstation is reachable,

the state that will be backuped is a stable one, for PM and NTWK.
The backup concerns the last version of the files saved on disk. Any information stored in memory which
has not been saved on disk, will not be saved on tape.
As a prerequisite to backup the subset DNM of Network data , Maps to be backed up must be first saved
with DNM.
To avoid any backup errors, the data which are going to be remotely copied must not be modified during
the backup operation. The administrator is responsible for informing the users of the beginning and of the
end of this remote copy, in order to prevent them from any action which may modify the data.
The type of data to backup, as well as the workstation(s) from which these data must be retrieved, must
be selected.
All workstations data are retrieved and saved on the disk of the Master Workstation.The information
displayed in the console after launching the remote copy is shown below.
When clicking on the Backup option, the following window is displayed.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 73. Backup operation

Characteristics of the Backup window :
ED
Available list box: lists all the workstations,

01
957.130.932 V

354
135 / 354
To Backup list box: lists the data types that wil be backed up when clicking on the Start pushbutton.
Supported data types: to select all possible components for one selected workstation.
Storage device pushbutton: to choose the destination of the backup , Disk only or Disk & Tape.
Add All pushbutton: to allow all the selected components for all the workstations to be backed up
(they are added in the To backup list box).
Remove all pushbutton: to delete all the allowed components for all workstations (components are
deleted from the To Backup list box).
> pushbutton: to select all selected components for one selected workstation (components are
added in the To Backup list box).
< pushbutton: to delete one selected component (components are deleted from the To Backup
list box).
Start pushbutton: to start backup for the components present in the To Backup list box.
Tape Copy pushbutton: to copy the backup from the disk to the tape.
Close pushbutton: to close the window.
The data types to backup have to be selected first before transferring information in the To Backup list
box.
While the backup action is running, the following window appear, describing the process working. The
Abort pushbutton allows to interrupt the backup at any time but the coherence of the different backed
up data are not warranted.
Figure 74. Backup in progress
1AA 00014 0004 (9007) A4 ALICE 04.10
After completion of the backup operation, a new Backup window opens to indicate the result.
ED
01
957.130.932 V

354
136 / 354

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 75. Backup completed
ED
01
957.130.932 V
354
137 / 354
9.4 Restore Operations
N.B.
Stop the SH before restore Operation: to stop the system start the Administration SMF and
click on the 1353SH / Stop option in the Process Monitoring window (this is the only way to
guarantee the correct result of the operation).
This operation may be necessary after reinstallation of workstation(s) failure of the system (due to
hardware or software) and after a full restore disks, or upgrade.
The data to be restored on the workstation(s) may be present on the master workstation under
$DIR1353SH/backup: it is a restore from disk.
The data may also be retrieved from tape. They are first copied on the master station
$DIR1353SH/restore before being copied on the backep up station, in the same operation.
under
As a prerequisite, the administrator must make sure to exit from any Presentation station .The current map
database must be cleaned up by selecting local map in the Cleanup window (see paragraph System
trace & Log management / Cleanup) if Network data are going to be restored.
Note: to perform a restore operation of the local MAP (after a backup operation) it is necessary to save
the MAP itself as distribuited MAP
9.4.1 Main window
1AA 00014 0004 (9007) A4 ALICE 04.10
When clicking on the Restore option, the following window is displayed.
Figure 76. Restore window
ED
01
957.130.932 V

354
138 / 354

Prerequisite: The SH must not run to restore Ntwk and Sh data.
N.B.
For the exclusive option, refer to paragraph 9.4.3.

CAUTION: The restore conditions are:
Unix can not be restored. Only a diff operation is possible,

Restore of PM or Ntwk can not be executed while the SH is running (Stop 1353SH with Process
monitoring option in the System Management features).
Characteristics of Restore window :
Available list box: lists all the available datatypes,

To Restore list box: lists the data types that wil be restored when clicking on the Start pushbutton.
Load from tape pushbutton: to load all the components from the tape.
Add All pushbutton: to add all present components in the To Restore list box.
Remove All pushbutton: to delete all components from the To Restore list box.
> pushbutton: to add a selected component in the To Restore list box.
< pushbutton: to delete a selected component from the To Restore list box.
Close pushbutton: to quit window.
Show status pushbutton: to show the components backup status (see Figure 77. ).
Figure 77. Show status pushbutton
1AA 00014 0004 (9007) A4 ALICE 04.10
Show info: displays information about the corresponding backup disk operation (see Figure 78. ).
This feature is not available for data restored from Tape and for the following data types:
ED
Network,
SECdb,
Operator.
01
957.130.932 V

354
139 / 354

Figure 78. Show info pushbutton
9.4.2 PM data type

A window is displayed to select the data subtype(s) (see Figure 79. ).
Figure 79. PM data subtypes
1AA 00014 0004 (9007) A4 ALICE 04.10
Select the data subtypes and click on Ok.

Warning: If the SH is running during the restore operation, PM_Main data are not restored (an error
message is displayed).
ED
01
957.130.932 V

354
140 / 354

9.4.3 Exclusive option

The exclusive option that may appear with the data types in the Available list box means that the data
with and without this option can not be restored in the same Restore operation. They have to be restored
separately. If both data types are associated to this option, they also have to be restored separately.
If the Add All pushbutton is clicked, all the nonexclusive data types will be added in the To Restore
listbox and for each exclusive data type, a window (see Figure 80. ) is displayed to warn the operator that
the data type is exclusive.
Figure 80. Warning window for exclusive data type

Warning: Unix data type can not be restored.
9.4.4 Restore in progress
When the restore operation is started, a message in red coloured background is displayed on all the
stations.
Figure 81. Starting restore
1AA 00014 0004 (9007) A4 ALICE 04.10
The Abort button allows to interrupt the restore at any time, but, despite the principle of saving old data
into a directory.save, the coherence of the different restored up data are not warranted because of the use
of several directories. In such a case, it is advised to start a new and complete restore operation.
While the restore action is running, the following window appear, describing the process working. The
Abort pushbutton allows to interrupt the restore at any time but the coherence of the restored data are
not warranted.
ED
01
957.130.932 V

354
141 / 354

Figure 82. Restore in progress

N.B.
During the restore operation, windows may be displayed according to the constraints given
paragraph 9.4.5.
After completion of the restore operation, a new Restore window opens to indicate the result.
Figure 83. Restore operation completed
9.4.5 PostOperations
1AA 00014 0004 (9007) A4 ALICE 04.10
When restoring the sh data, a message is displayed to warn the operator that:
the configuration has to be updated using the Update Config option in the System Management
/ Process configuration menu.
the HPOV registration has to be forced using the Force HPOV Registration option in the System
Management / Process configuration menu.
N.B.
ED
Only applicable for Q3B* NEs: for Ntwk data, a window (see Figure 84. ) is displayed after the
restore operation to warn the operator that a Compare MIB operation has to be performed on
all NEs.
01
957.130.932 V

354
142 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 84. Restore Compare MIB
ED
01
957.130.932 V
354
143 / 354
This remotization function allows the administrator to perform a backup, but the tar files are copied on a
remote station (i.e. not on the master station). This remote station is defined in the configuration file .
The remote server is defined with the file REMOTE_SERVER located under $DIR1353SH/conf/. The
default value is none.
N.B.
This function is applies only for a periodic backup (refer to chapter 12 Periodic Actions).
When clicking on the Remotization Enable/Disable option, the following window is displayed (in the
example below the actual remotization function state is enabled).
Figure 85. Remotization Enable/Disable
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on the Disable push button to disable the remotization function.
ED
01
957.130.932 V

354
144 / 354

9.5 Remotization Enable/Disable Option
10 SYSTEM MANAGEMENT

System management tasks have been split in the following way (see Figure 86. ):
Stack configuration to set the OSI routing data,
Process configuration to declare and assign the 1353SH agents,
Process monitoring to manage the SH agents,
On board simulator monitoring to view the process that are running,
System Shutdown,
Broadcast messages to users.
Figure 86. System Management Menu

Access rights
1AA 00014 0004 (9007) A4 ALICE 04.10
SMF Command
Access rights
Stack Configuration
Process Configuration
Process Monitoring
ED
01
957.130.932 V

354
145 / 354
Access rights
On board simulator monitoring
all, on Master station
System Shutdown
Broadcast message to users

SMF Command
Table 34. System Management: Access rights for different User Profiles
1AA 00014 0004 (9007) A4 ALICE 04.10
To open the window corresponding to one of the four options (see Figure 86. ):
Select the option.
Click on Ok to open the associated window.
ED
01
957.130.932 V

354
146 / 354

10.1 Stack Configuration

10.1.1 System Management Stack Configuration Feature
This tool allows to configure the OSI routing data for the network environment of the OS.
Figure 87. Stack Configuration
In the Workstation list box, select the workstation for which the stack configuration has to be
performed.
LAN configuration for OSI :
If the station is equipped with 2 ethernet ports ,TCP/IP is on LAN0 ethernet port, while OSI will be
configured on LAN1.
2 LANs (recommended) > Device OSI interface = on LAN1 > select the LAN 1
1 LAN
> Device OSI interface = on LAN0 > select the LAN 0
To copy the current configuration to another workstation:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Click on the Copy ... pushbutton: the following window is displayed.
01
957.130.932 V

354
147 / 354

Figure 88. Retix Stack Configuration Copy
Click on the radio button corresponding to the workstation on which the current configuration
has to be copied.
Click on the radio button(s) corresponding on the parameters to copy.

N.B.
Multiselection is allowed.
Click on Ok or Cancel to validate or cancel the choices.
NSAP address
The Network Service Access Point (NSAP) is the characteristic address of the OS within the OSI domain
of the network.
The format used for ALCATEL equipments (Network Element, Element Manager, Network Manager ...)
is the ISODCC format.
NSAP
IDP
DSP
AFI
IDI
VER
AUTH
ns
Domain
1 byte 2 bytes 1 byte 3 bytes 2 bytes 2 bytes

39
xxxx
80
xxxxxx
0000
xxxx
Area
System ID
2 bytes
6 bytes
xxxx
IP address in
hexa + System ID
SEL
1 byte
1D
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 35. Stack configuration: NSAP in ISODCC format

The ISODCC format is composed by:
ED
AFI:
Authority Format Identifier, is 39 (also 47 is supported).
01
957.130.932 V

354
148 / 354

IDI:
Initial Domain Identifier, is the country code for AFI 39, form xxxF.
Examples :
France 250F
Italy
380F
Ireland 372F
RSA
710F
UK
826F
Argentina 032F
N.B.
VER:
Version, is 80 for GOSIP V2 format of DSP.
AUTH:
Authority , administrative authority identifier for the network.
Domain:
identifies the routing domain in the network.
Area:
subdivision of the routing domain.
System ID:
IP address + NM_ID (NM=Network Management) of the related LAN interface.
N.B.
Se ISO 3166 Standard Documentation.
System ID must be defined in accordance with the custom addressing plan; anyway,
it is the same value configured as Address of Main OS on NEs by Craft Terminal.
SEL:
Selector, internal address of the upper transport layer.
N.B.
The SEL selector is a value requested to set a OSI NE address.
NSAP short format address
This address defines a NSAP shorter than full NSAP address (40 character) and its minimal configuration
includes the fields AFI, SystemID and NSEL (16 character ).
To retrieve the default configuration:
Click on the Default ... pushbutton: the following window is displayed.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 89. Retix Stack Configuration Default
ED
Click on the radio button corresponding to the workstation for which the default configuration
has to be retrieved.
01
957.130.932 V

354
149 / 354
Click on the radio button(s) corresponding on the parameters to retrieve.
Click on Ok or Cancel to validate or cancel the choices.
IS level
To define the IS level of the OS:
Level 1: routing intra area only,

Level 2 (in fact L1 +L2): routing intra and extra area,
Level 2 only , routing between area.
Manual End System Adjacencies
To declare Network Elements not supporting ESIS protocol. Such NEs belong to the same area as the
OS and are identified only with their own System ID ; they will be accessed on the LAN interface with their
own mac address.
Reachable Address Prefixes
To declare areas without Network Elements supporting ISIS protocol. Such area will be identified with
their own NSAP address ; they will be accessed on the LAN interface with their own mac address.
1AA 00014 0004 (9007) A4 ALICE 04.10
Validate the data clicking on Apply and close with Close.
ED
01
957.130.932 V

354
150 / 354

N.B.

10.1.2 MultiStack configuration

The multistack configuration allow you to activate different instances of the OSI Retix stack on different
network interface cards and then distribute SH processes on different network interfaces. Before the
activation of the multistack configuration is necessary to define the network interface card IP address and
the associated alias name. These values are used to identify the stack during next steps of SH
configuration.
The tool axmultistack permits to configure a Network Interface card, automatically excluding the first card
(lan0) that is already configured. To install a new Network Interface card refer to the Installation Procedure
manual (see [16]). This card is given with an internet address amongst the ones that exist in your network
map.
This procedure is not applicable with a unique Network Interface card otherwise the system displays the
following warning message:
Only one lan available, nothing to do.
Log in as root on the Master station and ELM station that supports this facility. Please observe that
superuser privileges are needed. The axmultistack procedure can be localized under /usr/local/etc.
If you configure more than one stack at installation time you must activate the procedure after the 1353SH
installation and before OS configuration (stack configuration, process configuration). Otherwise if you add
a further Network Interface card (after 1353SH has been completely installed and configured) it will
necessary stop 1353SH, activate the configuration procedure and then repeat the stack and process
configuration steps.
1AA 00014 0004 (9007) A4 ALICE 04.10
You have to follow the following procedure to configure the additional Network Interface card. Before to
start, control that the cards are connected to a network:
As root launch: axmultistack;
Select the Network Interface card;
Choose the menu Action/Configure. The system displays the dialog below;
ED
01
957.130.932 V

354
151 / 354

Figure 90. Multistack first window
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Give an IP address for the new Network Interface card as shown in the next figure. The IP address
must be assigned in conformance with your address planning. In any case network interface card
must to have an exclusive IP address number.
01
957.130.932 V

354
152 / 354

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 91. IP address configuration
Chose Modify aliases button to assign a new alias to the IP address. This alias name will be used
in process configuration step (see 10.2.2). As example see the next figure. Insert the new name and
push the Add button.
In addition you can optionally modify the subnet mask. The showed one (255.255.255.0) is the
default one.
ED
01
957.130.932 V

354
153 / 354

Figure 92. Add address alias
As last step, you can confirm configuration of the Network Interface card by clicking on OK button.
A warning message will appears, but not significant in this context.
Then you have to perform the stack configuration of System Management/Stack Configuration sub menu
of SMF (the new Network Interface card is automatically also configured).
As you can see in the chapter 10.2.2, from the Process Configuration dialog the operator is allowed to
select an element manager to configure. From the pulldown Process clicking on the Configure button,
the operator can select the process allowed to use a defined OSI Retix stack (associated with a specific
Network Interface card) specifying its alias address.
10.1.3 Using multiple Lan interfaces
Introducing multistack capability it is necessary execute procedure to configure some process (e.g.
FTservices or AND server) in order to use the stack active on a LAN interface different than the default
lan0.
1AA 00014 0004 (9007) A4 ALICE 04.10
FTservices configuration
The procedure below define the way to configure FTclient and FTserver processes (the appropriate
startup scripts) to connect them to the stack active on a LAN interface. Execute the following steps:
ED
Login to the system as administrator: axadmin

01
957.130.932 V

354
154 / 354

ANTP server configuration

The procedure below define the way to configure ANTP server (the appropriate startup scripts) process
to connect the stack active on a LAN interface. Execute the following step:
1AA 00014 0004 (9007) A4 ALICE 04.10
Execute:
cd $OSCOREDIR/script
Verify that the file switchSWSRV.pl is executable. Otherwise launch the command:
chmod ug+x $OSCOREDIR/script/switchSWSRV.pl

With SMF Process Monitoring function, stop the FT_server (swdlserver) and FT_client (ftclient)
processes.
Execute the command with the lan card identifier as parameter (example is using lan1):
switchSWSRV.pl lan1
Note that lan1 (or others) card must be previously configured as required by the multistack procedure
Restart the FT_Server and FTClient processes.
ED
Login to the system as administrator: axadmin

Execute:
cd $OSCOREDIR/script
Verify that the file switchANTP.pl is executable. Otherwise launch the command:
chmod ug+x $OSCOREDIR/script/switchANTP.pl

With SMF Process Monitoring function, stop the ANTP server (antpserver);
Execute the command with the lan card identifier as parameter (example is using lan1):
switchANTP.pl lan1
Note that lan1 (or others) card must be previously configured as required by the multistack procedure
Restart the ANTP server.
01
957.130.932 V

354
155 / 354
This tool allows an administrator to create 1353SH processes (emlim) for NEs and to allocate them to the
workstations of the OS.
It may be launched while the 1353SH is running, that allows to create dynamically new processes. The
lrf (Local Register Files) and the axconfig file are updated on each station.
Figure 93. Process configuration window
Elements Managers list box: contains the list of all the types of NE the OS is able to manage.
Processes list box: the new EML processes created from the existing Element Managers will appear
in this box.
1AA 00014 0004 (9007) A4 ALICE 04.10
Some processes are already existing, they also have to be assigned to workstation(s):
necomretix : OSI stack (Retix implementation), one is allocated for each station supporting
EML, ANTP or software download functionality.
pnmim : the PNM process. One for the whole OS, it is assigned to the Master station.
ED
01
957.130.932 V

354
156 / 354

10.2 Process Configuration

alarm : the ALARM process. One for the whole OS, it is assigned to the Master station.
perfstorage: this process performs the saving of performance collection for the station. One
perfstorage process must be configured on any station supporting EMLIM .
swdlserver: software download server application.
Workstations list box: contains the list of all the workstations of the OS.
Empty list box: display list box for report messages.
10.2.1 Main menu

Some options may be set [red square means the option is set on]:
Display box: error and warning messages will cause the opening of a window if Display box is set
on. The messages will be displayed in the lower area of the main window if is set off.
Bell: if set on, the bell rings when an error or warning message appears.
Verify state: if set on, removing a process will be refused if it is not stopped.
Verify properties: if set on, adding/removing a process not conform with the 1353SH rules will cause
an error or warning info message and the action is not executed. When set off there is no control and
the action is executed.
Quantity: usage rules about quantity of process of the same type.

Include/Exclude: creates automatically associated process, for instance to assign a first
emlim to a station creates and assigns an xcc retix process to the station.
Allow on: usage rules about allocation on type of workstation.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Update Config: update the configuration. The added / removed processes are registered /
unregistered in the HP OV tables.
Force HPOV Registration: for all the processes (new or already existing) the registration is forced.
ered. This operation could repair same situations but increases the registration time comparing to
the Update Config option.
Quit: to quit without update.
01
957.130.932 V

354
157 / 354

Figure 94. Main menu
10.2.2 Processes menu
Configure: reconfigure an emlim process assigned to a workstation. It is possible:
to change the NE group ID inside the range allocated to the OS,

to change the XCC_HOSTNAME , that means to force the emlim to use a defined XCC OSI
Retix stack. This operation allows the emlim, for instance, to use another workstation as a proxy
station to connect a secondary NEs network or to use a different OSI Retix stack instance (i.e.
the one identified by the alias as defined in the multistack procedure shown in 10.1.2):
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 95. Set XCC Hostname

N.B.
ED
The operator has to assign the process to the station by filling the XCC_HOSTNAME
fieldmanually.
Remove: to remove an emlim process not assigned to a workstation.

01
957.130.932 V

354
158 / 354

Figure 96. Processes menu
10.2.3 Eml processes creation
Select the Element Manager in Elements Managers list box.
Click on the black arrow between the Elements Managers list box and the Processes list box: the
new process is named with the name of the Element Manager plus a number group as suffix, for
instance adm150nr3_n. This number group is known as EML domain.
10.2.4 Workstations configuration
Select the station to configure.
Click on each process to assign to the station.
For the master station, pnmim process is automatically assigned if the option Verify Properties/Allow on
is set on. The alarm process also must be assigned to the Master.
Allocating an emlim automatically assigns a necomretix process.
After configuration of all the stations, save using the Update Config option in the Main menu: this
operation should always be done before exiting to update the configuration of the selected workstations.
1AA 00014 0004 (9007) A4 ALICE 04.10
The operator has to consult the report list box where error and warning messages are displayed.
ED
01
957.130.932 V

354
159 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 97. Update configuration
ED
01
957.130.932 V
354
160 / 354

10.3 Process Monitoring

The following table summarizes the commands provided with the 1353SH for System Management by
Apman.
Command
Description
Start
Command used to start the whole 1353SH application on all the WS or part of
it on specified WS.
Stop
Command used to stop the whole 1353SH application on all the WS or part of
it on specified WS.
Status
Command used to get the status of the whole 1353SH application or part of it.
New term
Command used to restore the monitoring console or create new console if not
present.
Console
As above, old messages are also displayed
Defense
Command used to get the current value of the defence mode of the 1353SH
application.
Command used to set the value of the defence mode of the 1353SH application.
Reset Lives
Command used to reset the lives for 1353SH application, or WS, or process(es).
Table 36. Process Monitoring command.
10.3.1 Access to the commands

When the Process Monitoring option is selected, the following window appears:
Figure 98. Workstations icons
1AA 00014 0004 (9007) A4 ALICE 04.10
Clicking on a WS icon makes appear the list of all the SH processes assigned to this WS as well as their
status (see Figure 99. ).
ED
01
957.130.932 V

354
161 / 354

Figure 99. WS and Processes, list and status

The Start / Stop / Status pushbuttons, directly available for WS and processes, they apply to all the
selected element(s) located into the corresponding left or right half window.
Other commands may be accessed by the cascading menu at the top of the window when clicking on one
of the Main / 1353SH / Workstations / Processes menus.
The meaning of the symbols is the following:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Black screen on WS: the WS is stopped.

Green coloured up arrow: the WS or process is started.
Red coloured down arrow: The process has failed or the WS was started but at least one process
failed on this station.
Blue coloured cross: the process is stopped.
Yellow coloured bent arrow: the process is starting: intermediate state.
Yellow coloured question mark: the Apman manager tries to connect to the process or WS:
intermediate state.
01
957.130.932 V

354
162 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 100. Sub menu commands
ED
01
957.130.932 V
354
163 / 354

Main commands
Rescan states: rescan states of processes.

Confirm: click to activate the procedure that opens a request confirm window (asking the
operator to confirm) when he executes a command;
Select: allows the operator to select several processes.
Deselect after: the selected fields are unselected after the action was performed.
Console: opens an SH console containing all the past changes of status. Deselecting Console
close the SH console.
Quit: close the Process Monitoring window.
1353SH commands
Start / Stop / Status: action is run for the whole 1353SH (all processes of all WS).
Reset Lives: reinitializes the number of lives to the max number, 1 life=1 automatic restart
allowed .
New Term: opens the SDH Manager window if it is not already opened.
Defense: defines the defense mode: automatic (Auto) or manual (Manual). See chapter 2.3.1
in this document.
Workstations commands
Start / Stop / Status: action is run for the whole station (all processes).
allowed (See 2.2 for the Defence Management concepts).
Processes commands
Start / Stop / Status: action is launched for all the selected processes.
allowed , for the selected station.
Select All / Deselect All: quick selection for all the processes corresponding to the already
selected station.
10.3.2 Startup
1AA 00014 0004 (9007) A4 ALICE 04.10
Just when Starting is launched a message Starting 1353SH Application (on green background) is
automatically displayed on all the stations. The Ok button allows to acknowledge the single message,
whereas the Discard All button allows to acknowledge all the messages of this type.
Figure 101. Startup in progress
ED
01
957.130.932 V

354
164 / 354

To set the behaviour of the Apman application.

System Startup
Once the different processes (1353SH processes and third party products) have been installed and the
Master workstation defined, the system can be started using the start command from the 1353SH sub
menu.
An SDH Manager window is generated by the system in which the result of the successive changes of state
resulting from the progress are displayed. This console will remain active until a system stop.
The structure of the console messages is always the same. Each message displays the execution date
and time, the name of the workstation on which the action has been performed (MASTER for the Master
workstation), and finally the action specific message.
N.B.
In the messages displayed by the console, two names are used for the messages of the Master
workstation; MASTER and the real Master workstation name (e.g. lin3). Indeed, the messages
may be sent either by the Application Manager (called MASTER) or the master workstation
considered as a common external workstation.
N.B.
Because a timeout is applied to each process execution, the console messages may be
displayed asynchronously.
An example of the information displayed in the console after the launching of the 1353SH is shown below.
Figure 102. SH Console Startup in progress

All the general processes on the different workstations, that are described in the axconfig file, are
launched. The ones already started are signaled but not relaunched.
The workstations are started in the order of their definition in the axconfig file.
1AA 00014 0004 (9007) A4 ALICE 04.10
Operators can now login, start the presentation processes, and start the management of the NEs that
make up the telecommunication network.
Startup of the 1353SH Application on a Workstation
This operation is undertaken either:
ED
to launch the 1353SH general processes for the first time, on a specified workstation,
01
957.130.932 V

354
165 / 354
in case of process(es) failure to relaunch the process(es).

It also starts HPOV if it is stopped.

As an example the console display resulting from a workstation startup is shown below.
Figure 103. 1353SH startup on a WS

All the 1353SH general processes on the specified workstation, described in the axconfig file, are started.
The processes on a workstation are started in a specific order, the one defined in the axconfig file.
When the apmanGui window is opened, the graphical view of WS and Processes status is refreshed.
General Process Startup
These processes are launched either:
during a global startup of the system,

during a workstation startup,
during a single process startup.
The response of the system will be displayed in the console and the visualization into the Process
Monitoring window is refreshed to reflect the current state.
Presentation Process Startup
1AA 00014 0004 (9007) A4 ALICE 04.10
Presentation processes are launched on explicit request of an operator either by:
ED
Clicking on an icon in the front panel.

The access to the 1353SH functionalities through the front panel is described in the SDH Manager
Getting Started Operator Manual.
01
957.130.932 V

354
166 / 354

As a result of navigation between different 1353SH application functionalities.

The navigation between the different management domains of the 1353SH product is described in
detail in the SDH Manager Getting Started Operator Manual.
10.3.3 Console & New Term

Performing a global 1353SH startup opens an SDH Manager new term window, in which will be displayed
the APMAN events as they come.
If at any time, the existing SDH Manager is closed or if it disappears as a result of a 1353SH stop or a system
malfunction, a new term can easily be regenerated with the New Term option in the 1353SH sub menu.
Figure 104. New SDH Manager window

Independently may be opened a console containing all the apman logs already created from the beginning
of the current session. It is opened using the Console option in the Main sub menu.
As the SDH Manager window does, this console log window displays also the apman events as they occur.
Figure 105. Console window
1AA 00014 0004 (9007) A4 ALICE 04.10
The structure of the console messages is always the same. Each message displays the execution date
and time, the name of the workstation on which the action has been performed (MASTER for the Master
workstation), and finally the action specific message.
ED
01
957.130.932 V

354
167 / 354
Because there is no grace delay the administrator must warn users (by Mail) before launching any stop
of the 1353SH, to prevent them from any loss of data.
Just when Stopping is launched a message Stopping 1353SH Application (on red background)
automatically sent to all the stations. TheDiscard All button allows to acknowledge all the messages
of this type.
Figure 106. Stop in progress

N.B.
Stopping 1353SH, global or workstation or process, is not allowed in Automatic Mode (see
SYSTEM DEFENCE ).
System Stop
The shutting down of the system consists in stopping all 1353SH processes. This operation does not
concern the third party product software (HP OV, Oracle) that can only be stopped by the Unix System
Administrator.
Workstations and all their general processes are stopped in the reverse order of their definition in the
axconfig file.
The SDH Manager window on the Master workstation is closed when the system stop has ended.
1AA 00014 0004 (9007) A4 ALICE 04.10
An example of the information displayed in the console is shown below.
ED
01
957.130.932 V

354
168 / 354

10.3.4 Stop

Figure 107. SH Console Stop in progress
Stopping of Workstation
Stopping the 1353SH general processes on a workstation may be necessary for workstation maintenance
purposes.
All the 1353SH general processes on the specified workstation, described in the axconfig file, are stopped
in the reverse order of the one defined in the axconfig file.
As an example, the console display resulting from a workstation stop is shown in the following figure.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Operators should close their presentation processes, wait for the 1353SH processes on the
specified workstation to be restarted or make a clean logout.
01
957.130.932 V

354
169 / 354

Figure 108. SDH Manager Stopping a workstation
General Process Stopping
Each process can also be stopped.
Figure 109. SDH Manager General process stopping

N.B.
It must be noted that system management commands are asynchronous and return
immediately, even if they are not actually completed. Subsequently, the completion of any
command must be checked on the console and if, for instance, you perform a stop just after a
start, the stopping command will take effect only once every process of the system has been
started. By the way, this is not a way to abort a system startup.
Stopping of Presentation Process
1AA 00014 0004 (9007) A4 ALICE 04.10
Operators wishing to stop a presentation process must select the Exit option from the menu bar of the
required application.
ED
01
957.130.932 V

354
170 / 354

10.3.5 System Defence

The 1353SH offers the administrator two possibilities in case of defect. He can either rely on the system
to automatically restart the processes on a workstation, or he can do it manually by launching the action
himself.
In the first case the defence restarting mode is said to be automatic and in the second case, it is manual.
The automatic restart mode has two phases:
If part of the 1353SH processes on a given workstation fails, during the first phase, the system only
tries to restart the part of the processes that has crashed. The system checks the time lapse between
the current automatic startup and the last automatic startup. If it exceeds a successive crash period
(called reset period), the crash counter value is reset.
If the restarts are unsuccessful and the crash counter value exceeds the maximum number of restart,
then the whole processes running on the workstation is stopped before being relaunched. This is the
second phase. As in the first phase, the successive crash period and the number of restart attempts
are limited and can be configured by the administrator. If the second phase fails, the restart mode
is set to manual and the administrator is given the hand.
When in the automatic mode, only the status and defense commands can be launched. In order to launch
other commands, first revert to manual defense mode.
In this section the operations necessary to determine and configure the defence mode are described.
N.B.
The default value of the defence mode at the start of the 1353SH is the manual mode.
Configuration of the defence mode
The defence mode is set, for the whole system, with the option Defense in the 1353SH sub menu.
There are two possible choices: manual or automatic. Opening the Defense sub menu shows the current
mode, the square is blue coloured.
Figure 110. Process Monitoring 1353SH menu
1AA 00014 0004 (9007) A4 ALICE 04.10
Click to change and confirm:
Figure 111. Defence mode change
ED
01
957.130.932 V

354
171 / 354
Handling process failure
If a General Process fails on any workstation, you are made aware of the problem by means of a message
in the console of the Master Workstation:
Console
Nov 09 11:39:10:tcmh853: Process emlim1641sm_22_2 failed
Figure 112. Handling process failure
In Manual Restart Defence Mode
In manual defence mode, the process should be restarted manually from the Master workstation using the Start
command
If the process fails again after relaunching without delay and the process is vital, you should stop it and
restart the workstation.
If the process is non vital, you can let the system work in degraded mode for a certain amount of time,
waiting for the right moment to stop and restart the workstation.
If the restart is still unsuccessful then the administrator can undertake a shutdown of the workstation as
described in chapter MAINTENANCEWS MANAGEMENT. The shutdown should only be done when the
1353SH processes are cleanly stopped.
In case of failure of one of the HPOV processes, a specific procedure should be undertaken from the
Master workstation:
Stop all the general processes on the workstation.

Check that the processes are effectively stopped.
Cleanly stop all the HP OV processes on the failed workstation (this can only be done by the unix
system administrator).
Restart the HP OV processes on the failed workstation (this can only be done by the unix system
administrator).
Restart the 1353SH general processes on the failed workstation.
In Automatic Restart Defence Mode
The following advices should be taken into account when handling process failure in automatic defence
mode:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
If the workstation is on stand by, the administrator may choose to toggle the defence mode to manual
and carry out a shutdown of the workstation as described in chapter MAINTENANCEWS
MANAGEMENT. The shutdown should be done only when the 1353SH processes are cleanly
stopped.
01
957.130.932 V

354
172 / 354

1AA 00014 0004 (9007) A4 ALICE 04.10

Contrary to the process number of restarts, the Workstation number of restarts is never reset except
on workstation manual shutdown and reboot.
You are informed about the automatic restart procedure by a message in the console of the Master
Workstation. An example of a vital single process called emlim1641sm_22_2 which fails several
times is shown in the following figure. In this example, the emlim1641sm_22_2 process has 3 lives.
The number of lives represents the number of restarts allowed for the process. When the process
has no remaining lives, it is considered as instable. Because emlim1641sm_22_2 is a vital process,
all general processes on the workstation are stopped. A workstation also has a number of lives, when
this number is exceeded then the workstation stands by with all its processes stopped.
ED
01
957.130.932 V

354
173 / 354
Console
1AA 00014 0004 (9007) A4 ALICE 04.10


Nov 09 11:40:05:tcmh853: Process emlim1641sm_22_2 has 2
remaining lives
Nov 09 11:40:05:tcmh853: Process emlim1641sm_22_2 start
in progress...
Nov 09 11:40:19:tcmh853: Process emlim1641sm_22_2 started
remaining lives
in progress...
remaining lives
Nov 09 11:41:18:tcmh853: Process emlim1641sm_22_2 instable
Nov 09 11:41:18:tcmh853: WS stop provoked (2 lives
remaining)
Nov 09 11:41:18:tcmh853: Process emlim1641sm_22_2 stop
impossible : not running
Nov 09 11:41:18:tcmh853: Process emlim1651sm_20_1 stop in progress...
Nov 09 11:41:18:tcmh853: Process emlim1651sm_20_1 stopped
Nov 09 11:41:18:tcmh853: Process xcc stop in progress...
Nov 09 11:41:18:tcmh853: Process xcc stopped
Nov 09 11:41:19:tcmh853: Process qb3s stop in progress...
Nov 09 11:41:19:tcmh853: Process qb3s stopped
Nov 09 11:41:20:tcmh853: WS stopped
Nov 09 11:41:49:MASTER: WS tcmh853 no connection
Nov 09 11:41:51:MASTER: WS tcmh853 automatic restart
Nov 09 11:41:51:MASTER: WS tcmh853 start in progress...
Nov 09 11:42:09:tcmh853: WS started
Nov 09 11:42:09:tcmh853: Process qb3s start in progress...
Nov 09 11:42:19:tcmh853: Process qb3s started
Nov 09 11:42:19:tcmh853: Process xcc start in progress...
Nov 09 11:42:29:tcmh853: Process xcc started
in progress...
in progress...
Nov 09 11:42:58:tcmh853: WS initialisation complete
Figure 113. General process restart procedure. Console information.
ED
01
957.130.932 V

354
174 / 354
10.3.6 Status

1353SH Status
A new window pops up displaying the result of the command, the action may be interrupted by clicking
on the Stop button.
As result the status is given for all the processes of all the stations.
Close this window when finished by clicking on Dismiss.
Figure 114. 1353SH status

The 1353SH general processes are also monitored periodically by the system. The supervision period is
set offline and the default value is 10 seconds.
Status of Workstation
The status is given for all the processes of the selected station.
Status of Process
The status is given for all the selected processes for one station.
1AA 00014 0004 (9007) A4 ALICE 04.10
Presentation Process Status
These processes are NOT monitored by the monitoring processes of the 1353SH product.
The monitoring of these processes may be done using usual unix commands. For example the command
$ ps ef | grep processname
can be used. Refer to the unix system administrator for more information on the ps command.
ED
01
957.130.932 V

354
175 / 354
10.4 System Shutdown

Figure 115. System Shutdown window.

This option is used when a workstation has to be shutdown.
Perform the following operations:
Select the workstation(s) name in the upper area.
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on the Select All pushbutton to select all the listed workstations. Multiselection is
allowed.
Choose the type of shutdown to perform on the selected workstation(s):
Click on the shutdown and halt radio button to stop the workstation.
Click on the shutdown and reboot radio button to reboot the workstation.
Choose when the shutdown is effective:
ED
Click on the do not wait radio button if the shutdown has to be immediate after acknowledging
the action (clicking on the Ok pushbutton).
01
957.130.932 V

354
176 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
Click on the wait before shutdown radio button if a delay is needed. In that case, enter a value
(in seconds) in the Delay field.
Click on the Ok or Cancel pushbuttons to validate or cancel the choices.
01
957.130.932 V

354
177 / 354
This function allows the operator to known how many on board simulator processes are activated at a
certain moment on the master and/or emlim workstations.
From the System Management menu, after clicking on the On Board Simulator Monitoring item the
following window will appear (see Figure 116. ):
Figure 116. On Board Simulator Monitoring window

The first time, Figure 116. shows a black icon indicating that no on board simulator are activated in all the
workstations (master and/or emlim).
After activating one on board simulator processe on a emlim workstation, the operator can click on the
Refresh button in the Figure 116. Then Figure 117. will be displayed.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V

354
178 / 354

10.5 On Board Simulator Monitoring

Finally, by clicking on the green icon other information are displayed.

The information displayed are:
name of every workstations where all the on board simulator processes are running;
NE s names simulated;
type, number and group of the emlim;
SH neId.
To exit from the on board simulator monitoring window chick on the Exit button (see Figure 118. ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Note: This operation must be performed manually by the operator, in fact no automatic mechanism to
Refresh the on board simulator monitoring window exists.
ED
01
957.130.932 V

354
179 / 354
10.6 Broadcast message to users

This option is used when a message has to be sent to all the workstations.
Figure 119. Message Broadcast dialogue box.

Perform the following operations:
Enter the message in the upper area.
Choose the importance level of the message:
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on the info radio button so that the message is displayed in a green window.
Click on the urgent radio button so that the message is displayed in a red window.
Enter the time during which the message remains displayed
Click on the Ok or Cancel pushbutton to validate or cancel the choices.
ED
01
957.130.932 V

354
180 / 354

10.7 HPOV Failure on a workstation

It may happen HPOV fails on a workstation. In that case, a clear message appears in the SDH Manager
window. In manual mode defence, HPOV failure will cause SH processes fall on the station, as it is shown
in the following example.
Figure 120. Workstation failure SH processes failed
1AA 00014 0004 (9007) A4 ALICE 04.10
On the above example, HPOV failure consists in pmd process failure, other fault configurations may occur:
ED
01
957.130.932 V

354
181 / 354

Figure 121. Workstation failure Fault configurations Example 1
Figure 122. Workstation failure Fault configurations Example 2
1AA 00014 0004 (9007) A4 ALICE 04.10
To retrieve a safe state the administrator must stop the whole station then start it again using the
Process Monitoring functionalities.
ED
01
957.130.932 V

354
182 / 354
11 LOCAL DATA MANAGEMENT

These tools were developed to give the operator the facilities for NE management.
Figure 123. Menu of Local Data Management
11.1 Access rights

The following table shows the access rights for the different User Profiles. As you can see a viewer User
Profile (user axviewer) cannot use the SMF Local Data Management functionalities. The chapter 7.8 lists
the corrispondence between User Profile and User Name.
1AA 00014 0004 (9007) A4 ALICE 04.10
SMF Command
Access rights
Diagnostic of audit of the MIB
admin, constructor and operator
Display SEN MIB
NECTAS Decoding
admin
NECTAS Comparison
Upload failure Diagnosis
ED
01
957.130.932 V

354
183 / 354
Access rights
Enable RPS Switch
Software download manager configuration
admin
Software download server configuration
admin
Save TP
admin and constructor
Restart Perf Collect
Overhead byte Configuration
admin
LAPD Configuration
admin
Change ASAP
admin
Sync Source Selection
admin
Address Configuration
admin
Change Assigned To Observed
Change Free or Observed To Assigned
Switch Old/New Practice
Set Offline Board
Set Offline SignalLabel
Ping NE
List Gateway NE
DXC TCPIP Address Configurations
admin
Change user label format
admin

SMF Command
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 37. Local data management: acess right for different User Profiles
ED
01
957.130.932 V

354
184 / 354

11.2 Overview
11.2.1 Interface
In order to give an ergonomic access to the tools, their interface has been developed thanks to a shell
providing a graphical user interface (TCL/TK or Perl/TK).
When clicking on any of the options (except for the two Software download options and for the Ping NE
option), a specific window is displayed for the operator to choose a NE (see Figure 124. ). Only the title
of the window will change depending on the option chosen.
Figure 124. Choosing a NE

Usage of buttons :
Ne Family button: chooses the family of NEs , ADM , microwaves , Line System ....
Ne Type button: chooses one type of NEs.
User Label field: defines a string permitting to select NEs which user label contains the string.
Filter button: applies the search criterium to sort all the corresponding NEs.
Click on the NE to select it.
Click on Quit to exit.
An Ok button for action will appear after the selection.
11.2.2 Choosing a NE
When the window to choose a NE (see Figure 124. ) is displayed:
the list box (just below the Choose an NE string) is empty,

the Ne Family button is set to All,
the Ne Type button is set to All.
In this configuration, click on Filter to display all the possible NEs in the listbox.
If necessary, change the filtering parameters (Ne Family, Ne Type, User Label) to decrease the number
of NEs displayed.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on the NE name then on Ok to select the NE.

11.2.3 Interactions with the OS
As input, the tools use :
ED
01
957.130.932 V

354
185 / 354
the persistency file of PNM using the script axdbRead,

the file of configuration used by APMAN axconfig,
the trace files generated by the EMLIM processes
<nameOfProcess>.err),
the NECTAS file of the NEs (*.cfg),
(<nameOfProcess>.trace
As output, the tools may modify the NECTAS file of the NEs (*.cfg).
11.2.4 Constraints
As some tools work on the file where Nectas tables are saved, the usage of some of these tools needs
to stop the system (or only the EMLIM process managing the concerned NE if the operator knows it).
After the running of the tool, the restart of the system (or of the EMLIM process) will take into account
the modification of the NE, except if a particular action is required .
Once the tool runs, the first window displayed warns the operator to stop the system.
Figure 125. System stop confirmation
Click on OK to go on the program.
Click on Cancel to stop the program.
11.2.5 User Interface parameters

The colors and fonts used by the user interface are defined in a specific file called preferences.wish under
1353sh/conf.
1AA 00014 0004 (9007) A4 ALICE 04.10
They can be updated only with Unix commands.
ED
01
957.130.932 V

354
186 / 354


11.3 Diagnosis of audit of the MIB Option

After MIB Audit on one NE, this tool allows to show the differences between the MIB loaded in the OS and
the MIB in the equipment itself.
N.B.
During a MIB Audit operation, the local tables are automatically uploaded.
This tool has to be used after a takeover to diagnose misalignment.

The differences between the MIB of the NE and the MIB of the OS are written in a file.
N.B.
There is no exchange between the tool and the equipment. This tool supposes that an audit has
been done. It only looks at the trace files to determinate where are the differences.
Figure 126. Diagnosis of audit of the MIB

Select the NE to diagnose the audit (see paragraph 11.2). Only one selection is possible.
Click on the Diagnosis push button to run the action on the selected NE.
1AA 00014 0004 (9007) A4 ALICE 04.10
If there are some differences between the MIBs, a window showing them is displayed. For each difference
detected, the displayed file gives the Application, the Table and the Element . The value of all the bytes
of this element are displayed for the NE and for the OS, as shown in the following figure.
ED
01
957.130.932 V

354
187 / 354

Figure 127. MIBs differences

The following pulldown menus are available on the top left of the window.
File
Search
Print
Quit
Find...
Clear
Figure 128. Pulldown menus of the MIBs differences window
Click on the Print option of the File pulldown menu to print the file.
Click on the Quit option of the File pulldown menu to close the window.
Click on the Find... option of the Search pulldown menu to search an occurence.
The following dialogue box opens:
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 129. Find dialogue box
ED
Enter the required occurence in the Find field.

Click on the Ignore case radio button to not take into account the capital or small letters of the
occurence (when the square is red).
01
957.130.932 V

354
188 / 354

Click on the Find push button.

The found occurences appears in red colour with a highlighted square on the first one (see
figure below).
Figure 130. Searching occurences in the MIBs differences
Click again on the Find push button to go to the next occurence.
Click on the Clear option of the Search pulldown menu to reset the search.
An error may occur when the tool is running. In this case, an error window is displayed to the operator
showing the cause of failure.
Main possible causes of failure are :
File of traces not found: Impossible to find the trace file corresponding to the EMLIM process
managing this NE
No audit was processed on this NE: the tool was unable to find the traces corresponding to
an audit for this NE. From EMLUSM, perform a Diagnosis/Compare operation to create the
file.
1AA 00014 0004 (9007) A4 ALICE 04.10
Restrictions : If several audits have been processed on one NE, only the later one will be taken into
account by the tool .
ED
01
957.130.932 V

354
189 / 354
11.4 Display SEN MIB Option

This chapter is applicable to QB3* NEs only.
The SEN MIB contains the data (connections, ports, etc...) for each Qb3* NE managed by RM system.
The data are mapped from SHIM MIB to SEN MIB when the NE becomes NML assigned.
The tool allows to edit the SEN MIB of NE. Such a MIB exists only when the NE is NML assigned. The action
creates a file *.sen.mib under 1353sh/shared_data/mib. This tool has to be used after a takeover also
to diagnose misalignment.
Figure 131. Display SEN MIB

The information displayed concern the MIB part of connections. Some domains may be skipped if the
corresponding data dont exist for the NE type, or in case of incoherence. All domains are skipped if the
NE is not NML assigned .
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 132. SEN MIB

The possible operations by using the pulldown menus on the top left of the window are the same as for
the previous paragraph.
ED
01
957.130.932 V

354
190 / 354

N.B.
11.5 NECTAS Decoding Option

N.B.
This tool allows to manipulate the NECTAS file (i.e. the persistency file) loaded in the OS. It is possible
to see the value of all the tables (including application 255), to change these values and to replace the old
NECTAS file by the new edited one.
Caution : When replacing a NECTAS file (functionality Encode), take a great care of the
modifications performed, because, as there is no control on the coherence of the tables, an
inconsistency may occur when the EMLIM try to build the NE again and it may result in a crash. This
operation should be done only by Alcatel personnel.
The tool is run by typing the command in a command shell or with a doubleclick on its icon .The first
window displayed allows the operator to select the user label of the NE. Only one selection is possible.
Figure 133. NECTAS Decoding

Select the NE as given in paragraph 11.2.
Click on Show to allow reading the NECTAS file.

Click on Edit to allow editing (mode read/write) the NECTAS file (but the file can not be yet taken
into by the EMLIM process).
Show pushbutton: The correct result of this functionality is to display a window showing the decoded
NECTAS files
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
The button GoTo Table allows to link directly to the wanted table.
The button Quit closes the window.
01
957.130.932 V

354
191 / 354

Figure 134. NECTAS Decoding Show
1AA 00014 0004 (9007) A4 ALICE 04.10
Edit : The correct result of this functionality is to display a window showing the decoded NECTAS files
Figure 135. NECTAS Decoding Edit
ED
The button Save rewrites the file even if no modification has been done.
01
957.130.932 V

354
192 / 354

N.B.
This update does not affect the file used by the EMLIM process, but only the working file of the
tool.
The button Quit closes the window.
Encode: The correct result of this functionality is to apply the previously saved modifications of the
decoded NECTAS files on the file used by the EMLIM process.
Figure 136. Encode operation confirmation
Click on Yes to allow loading the new NECTAS file to the working directory of the EMLIM
process.
The button OK closes the window.
Figure 137. Encode System stop

The EMLIM process must be stopped by the Operator.
An error may occur when the tool is running. In this case, an error window is displayed to the operator
The possible causes of failure are :
Master workstation not found: Impossible to find, in the APMAN configuration file, the hostname
of the MASTER workstation of the OS.
Bad User Label: Impossible to find the user label of the NE inside the file of persistency of PNM.
Hostname not found: Impossible to find, in the APMAN configuration file, the hostname where the
EMLIM is running.
For the Encode functionnality, the following message may be displayed :
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Decoded file does not exist : this means that the tool does not find any NECTAS file to encode, in
its working directory, for the selected NE.
Another message giving an information from PersBrowser in case of failure during the encoding
operation.
01
957.130.932 V

354
193 / 354
11.6 NECTAS Comparison Option

This tool allows to compare the NECTAS table loaded in the OS for 2 NEs. These tables are only read and
no action is done on them.The tool displays the differences between the 2 NEs.
Caution: The tool works on files *.cfg (only in read mode).

The first window allows the operator to select the user labels of the NE to compare.
Figure 138. NECTAS Comparison (first NE)
Click on OK to select the first NE.
Figure 139. NECTAS Comparison (second NE)
Click on OK to select the second NE.
1AA 00014 0004 (9007) A4 ALICE 04.10
If the tool has correctly run, 2 cases may occur:

a)
ED
There are no differences between the NECTAS tables of the 2 NEs.
01
957.130.932 V

354
194 / 354

N.B.

Figure 140. NECTAS Comparison Result (no differences)

b)
There are some differences between the NECTAS tables of the 2 NEs, a window showing these
differences is displayed. For each table in which a difference has been detected, the displayed file
shows the element and the byte different as well as the value of this byte for both NEs.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 141. NECTAS Comparison Differences displayed
ED
The button Print allows to print this file. A dialog box displays the printer status.
The button Save allows to save this file. A dialog box is displayed to get the name of the file in
which the result will be saved.This box is shown hereafter:
01
957.130.932 V

354
195 / 354
The operator has to enter the whole pathname of the file in which the result is saved.
Click on Quit to stop the tool .
An error may occur while the tool is running. In that case, an error window is displayed to the operator
Restrictions: The differences between the NECTAS tables are detected only for the application 55..60.
1AA 00014 0004 (9007) A4 ALICE 04.10
So some applications as 254 , 255 , also called demy tables and relative to OS attributes , are not taken
into account.
ED
01
957.130.932 V

354
196 / 354

Figure 142. NECTAS Comparison File saving
11.7 Upload Failure Diagnosis Option

N.B.
This tool shows the incoherencies detected in Nectas data (e.g. connections using same TPs, connections
using ports not existent, etc... ) while uploading the tables after a Start supervision . It uses an *.invalid.cfg
relative to the NE , under 1353sh/eml/NE_type/data, which still remains present after the incoherency
has been fixed, so it is not representative of the current NE state.
Figure 143. Upload Diagnosis Failure

1AA 00014 0004 (9007) A4 ALICE 04.10
The incoherencies are displayed in red colour to be easily visualized.
Figure 144. Upload Diagnosis Failure Diagnosis
ED
01
957.130.932 V

354
197 / 354
11.8 Enable RPS Switch Option

The Radio Protection Switching applies to microwave NEs. It enables alarms related to RPS status in
alarm criterion tables of the NE.
Figure 145. Enable RPS Switch

Select the NE (see paragraph 11.2) and click on Enable.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 146. Enable RPS Switch Result
ED
01
957.130.932 V

354
198 / 354

N.B.
11.9 Software download manager configuration Option

N.B.
This chapter is applicable to QB3* NEs only. For Q3 NEs the feature is available from the
Download menu in the EML USM program.
This tool allows to create directories for software releases, to be used by the software download server
tool, in order to execute the download procedure.
The software download packages must be identified by the Software download Manager, and they may
be local (installed on the 1353SH OS) or external (installed on PC , SUN stations ...).
Figure 147. Software Download Manager Configuration

When clicking on the NE Type option button, the tool displays all the declared versions for each type of
NE. These informations are under the responsibility of the operator, there is no control with the real
availability of the corresponding software package on any server. If the server must be a local server, the
administrator has to update the server using the Software download server configuration tool.
1AA 00014 0004 (9007) A4 ALICE 04.10
To declare a new version, select an NE type then fill the New Version field and click on the Add
pushbutton.
To remove an old version, select an NE type then select the version in the Version list box and click on
the Remove pushbutton.
In both cases a new window opens then requiring to confirm the request.
ED
01
957.130.932 V

354
199 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 148. Add new version
Click on Ok to create or remove the software version.
Click on Cancel to cancel the request.
ED
01
957.130.932 V
354
200 / 354
11.10 Software download server configuration Option

This tool allows to manage the local software download server:
to get information about packages,

to load a new package,
to delete an old one.
When clicking on this option, the following window is displayed:
Figure 149. Software download server configuration
11.10.1 Install a new package

Installing from floppy disk
The source path field must be filled up by the operator according to the device path. The default path is
shown in the figure below:
Figure 150. Package installation
1AA 00014 0004 (9007) A4 ALICE 04.10
Installing from CD ROM

A default CDROM device path name must be defined in order to install software package from a default
CD_ROM driver. In addition the dialog box shown in Figure 150. allows the operator to define a different
SW package source, modifying the source path input field. The rules are:
ED
Source Path = <device_path><:>. Where device_path is a floppy driver. The final : (colon)
character indicates units in DOS format;
01
957.130.932 V

354
201 / 354
source path = CDROM. The keyword CDROM (or cdrom) indicated that the SW Package source is
a CDROM. The physical device path is that defined as default by environment variable;
source path = <device_path>. The SW Package source is the CDROM device driver indicated;
source path = <hostname>:<device_path>. The SW Package source will be a remote CDROM
device driver. The remote host must exports the mounted CDROM directory;
source path = CDROM#<NeType> or source path = <device_path>#<NeType> or source path =
<hostname>:<device_path>#<NeType>. The indication of the <NeType> allows to install the
related NE type SW package if more than one SW Package is stored on the CDROM. The #
character is used as separator.
To manage installation from CDROM some parameters must be defined. As others parameters in Server
Administration application also these ones are defined as environment variables. The value of all
environment variables is defined in the application startup command script file
(/usr/1353sh/swdl/swdlserv/script/srsa). In the following there is the list of all new parameters and the
related environment variable name:
SRSA_CD_DEV_NAME: is the default CDROM device path name. May include a remote host
name;
SRSA_CD_MOU_ROOT: is the CDROM mount directory path name;
SRSA_CD_ROOT: is the NE SW Package root directory name on CDROM;
SRSA_CD_MOU_CMD: SRSA_CD_UMOU_CMD
these variables define the mount and umount command script file name, as registered in the
super command table;
SRSA_CD_CUPP_CMD: this variable defines the uppercase conversion script file name, located in
the script directory of the application;
SRSA_FORCE_NETYPE_CASE: this variable defines if a forced upper/lowercase conversion is
requested for the optional NeType indication ( UP | LOW)
See [16] for installation notes details about the default CDROM device path name.
N.B.
Remote Access: CDROM drivers are accessible also when installed on a remote host. This
way to operate will be useful in case of SH distributed architecture, for example when only one
workstation is equipped with the CDROM driver (ex. HP KServer). The Server Administration
application allows to select as SW Package source a CDROM mounted and exported from a
remote host . In addition also remote copy of the installed SW Package on a remote host is still
allowed.
N.B.
File location: In currents distribution on CDROM the location of NE SW Package file is

/ECT/SWDW. In any case this root directory definition may be got by the application as
parameter (useful to change it in uppercase or lowercas letters).
N.B.
File format: The use of uppercase only characters for the CDROM production (ISO 9660
character set), as required also in [1], will be recommendable. This rule would have to be worth
for file naming (descriptor file and executables files) and for descriptor file contents. In any case
a forced conversion will be applied. This is done to avoid problems due to differences in file
naming during download operations.
11.10.2 Delete a package
1AA 00014 0004 (9007) A4 ALICE 04.10
When clicking on the Delete SWP option, the following window is displayed.
ED
01
957.130.932 V

354
202 / 354


Figure 151. Selection of the package to delete

The deletion of package may be run without control on the current actions, so an info message warns the
operator.
Figure 152. Package deletion
11.10.3 Display SWP Descriptor
1AA 00014 0004 (9007) A4 ALICE 04.10
When clicking on the Display SWP Descriptor option, the following window is displayed.
ED
01
957.130.932 V

354
203 / 354

Figure 153. Selection of the descriptor to display
1AA 00014 0004 (9007) A4 ALICE 04.10
The Display SWP Descriptor command displays the descriptor file relative to the package.
Figure 154. Display of descriptor file
ED
01
957.130.932 V

354
204 / 354
11.10.4 Check SWP

When clicking on the Check SWP option, the following window is displayed.
Figure 155. Selection of the package to display

As shown in previous chapter the Software Package descriptor contains the description, pathnames and
versions of the files included in tha package. The Check SWP action checks the coherence between the
descriptor and the package files of the software package installed locally.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 156. SWP check
ED
01
957.130.932 V

354
205 / 354
N.B.
This chapter is applicable to QB3* NEs only. In Q3 NE management the EMLIM process
manage a persistency file of its local MIB which includes the list of current started TPs in Perf
in NE.
Save in OS the list of current started TPs in Perf in NE. It creates a new file restart_NE_Type_TP.dat
under 1353sh/shared_data. It should be used before any operation which may result in a loss of started
TPs, such as replacement of ESCT or SMEC2 board on ADM, or before stopping it to be able to restart
it at any time.
Figure 157. Save TP
1AA 00014 0004 (9007) A4 ALICE 04.10
Select the NE (see paragraph 11.2) and click on Save.
ED
01
957.130.932 V

354
206 / 354

11.11 Save TP Option
11.12 Restart Perf Collect Option

N.B.
The tool allows to restart the Perf on NE. The list of TPs must have been saved previously using the Save
TP option.The Restart action is sent to EMLIM which forwards the request to the NE if the TP was stopped.
Figure 158. Restart Perf Collect

Select the NE (see paragraph 11.2) and click on Restart.
The list of TPs currently started is recalled.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 159. Restart Perf Collect Result
ED
01
957.130.932 V

354
207 / 354
N.B.
This chapter is applicable to QB3* NEs only. For Q3 NES the feature is managed by the EML
USM process. See the 1353SH operators Handbook for details.
The overhead bytes are unused bytes in the SDH frame that can be used to transmit data for the operator.
This option allows the configuration of overhead bytes.
Figure 160. Overhead byte configuration option

Select the NE as given in paragraph 11.2 to choose the NE on which the Overhead byte is to be configured
and click on Ok.
1AA 00014 0004 (9007) A4 ALICE 04.10
The following window is then displayed to configure the overhead bytes for the chosen NE.
ED
01
957.130.932 V

354
208 / 354

11.13 Overhead byte Configuration Option
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 161. Overhead byte configuration
ED
01
957.130.932 V
354
209 / 354

The window is divided into four parts:
the Termination Channels part: for each V11 or G703 link, select the Card and the OH Byte,
this part allows to select, if necessary, the options EOX extention enable and MSOH
PassThrough option.
the PassThrough Channel part: configuration of the SOH nine passthrough channels,
the Voice part: configuration of the orderwire channels (voice channels).
The phone number associated to the orderwire channels can also be configured by sliding the cursor.
The possible values are 1 to 99.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on OK to validate the configuration.
ED
01
957.130.932 V

354
210 / 354

The user can select the Card and OH Byte (in the RSOH or MSOH) used for each functionnality to
configure. The possible value for the Card and OH Byte depend on the type of NE managed and on the
channel. The OH Byte values are couples of values which define the byte in the RSOH or MSOH.
11.14 LAPD Configuration Option

N.B.
This chapter is applicable to QB3* NEs only. For Q3 NES the feature is managed by the EML
USM process. See the 1353SH operators Handbook for details.
This option allows the configuration of the Link Access Procedure (LAP) for a D Channel (LAPD).
Figure 162. LAPD configuration window

Select the NE as given in paragraph 11.2 to choose the NE on which the LAPD is to be configured.
1AA 00014 0004 (9007) A4 ALICE 04.10
The following window is then displayed to configure the LAPD for the chosen NE.
ED
01
957.130.932 V

354
211 / 354

Figure 163. LAPD configuration

For each STMn aggregate or STMn tributary boards of the NE, select:
1AA 00014 0004 (9007) A4 ALICE 04.10
the LAPD interface: select Yes or No to use the DCC as communication channel to support the TMN,
the LAPD role: select User or Network to design the link between two adjacent SDH NEs.
NETWORKNETWORK or USERUSER are not authorized.
Select the ethernet link between the OS and the NE. If the NE isnt the GNE (Gateway Network Element),
the ethernet interface should be set to NO. This means that the NE is accessible only through the DCC
via the GNE. The default value is NO.
ED
01
957.130.932 V

354
212 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

The L2 only parameter option can be set to True or False. It shall be set when SH has to communicate
only to NEs pertaining to different areas with respect to the area of the SH itself.
If True is selected, no other machines of the same area address of the OS shall exist in the network.
False is the default.
Click on OK to validate the configuration.
ED
01
957.130.932 V

354
213 / 354
11.15 Change ASAP Option

N.B.
This option allows the copy of the ASAP from one NE to another.
Figure 164. Change ASAP window
Select the Ne Family and NE Type then click on the Filter pushbutton.
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
To have the complete list of NEs, click on the Filter pushbutton.
Select the NE source in the displayed list (see Figure 165. ).
01
957.130.932 V

354
214 / 354

Figure 165. Change ASAP window NE source selection
Click on the Ok pushbutton: the following window is displayed showing that the ASAP table of the
selected NE (source) is retrieved.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 166. Change ASAP window Getting ASAP tables
As for the NE source, select the NE destination.
Click on the Ok pushbutton: a window (see Figure 167. ) is displayed showing that the Change
ASAP operation is running.
N.B.
If the NE source and destination are identical, an error message is displayed.
N.B.
The EMLIM process associated to the selected NEs must be stopped, otherwise an error
message is displayed.
Figure 167. Change ASAP window Work in progress
ED
01
957.130.932 V

354
215 / 354
11.16 Sync Source Selection Option

This tool allows to choose the synchronization source for an NE (only for ADMs and MWs).
The usage of the tool needs to stop the system (or only the EMLIM process(es) managing the concerned
NEs if the operator knows it). After the running of the tool, the restart of the system (or of the EMLIM
process(es)) will take into account the modification and the NE(s) will appear under the assignment state
Observed.
Figure 168. Sync Source Selection Choosing a NE

Click on the Filter push button to display the NEs in the right part of the window.
Select the NE and click on Ok.
1AA 00014 0004 (9007) A4 ALICE 04.10
The following window opens (if the NE is a MW for example).
Figure 169. Sync Source Selection Selecting the synchronization source
ED
01
957.130.932 V

354
216 / 354

N.B.

Click on the Equipment Type option button then select an option. If the selected option concerns the SSU
feature, the windows becomes as follows (SSU Quality option button enabled).
Figure 170. Sync Source Selection Choosing the SSU quality

Click on the SSU Quality option button then select an option.
Click on the Ok push button to allow the change of the synchronization source.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on the Cancel push button to close the window without change.
ED
01
957.130.932 V

354
217 / 354
11.17 Address Configuration Option

N.B.
Figure 171. Address Configuration
Select the Ne Family and NE Type then click on the Filter pushbutton.
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
To have the complete list of NEs, click on the Filter pushbutton.
Select the NE source in the displayed list (see Figure 172. ).
01
957.130.932 V

354
218 / 354

Figure 172. Address Configuration NE source
While running, an intermediate window is displayed.
Figure 173. Address Configuration Initialisation on going
1AA 00014 0004 (9007) A4 ALICE 04.10
Then the Address window is displayed.
ED
01
957.130.932 V

354
219 / 354

Figure 174. Address Configuration Addresses setting
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
The following parameters can be modified:
NE address: Area Address and System ID fields,
IS level: L1 or L2,
OS address main: Area Address and System ID fields,
OS address spare: Area Address and System ID fields,
Auto Switchover: Yes or No. It allows (if set to Yes) an automatic switching from the OS main
address to the OS spare address.
Auto Switchback: Yes or No. It allows (if set to Yes) an automatic switching from the OS spare
address to the OS main address.
Click on Ok or Exit to validate or cancel the modifications.
01
957.130.932 V

354
220 / 354

11.18 Change Assigned To Observed and Change Free or Observed To

Assigned Option
N.B.
This tool allows to change the assignment state of one or several NE.
All the assignment states will be updated (i.e. both for the PDH/SDH ports and for the NE itself).
Observed.
N.B.
There is no change for all the modifications of the configuration which had made the
assignment state turn to Assigned (such as a modification of payload or a NAP upload).
N.B.
The current description is done for a Assigned to observed change. The operations are the
same for the Free or observed to assigned change.
Figure 175. Change assigned to observed window

N.B.
The complete list of NEs (shown above) is displayed only after clicking on Filter.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
Multiple selection is allowed.
If the relative process has not been stopped, a window may be displayed to warn the operator that the
operation can only be performed if the process is stopped.
During the Change state operation, information are displayed in the list box (see Figure 176. ).
ED
01
957.130.932 V

354
221 / 354
The NEs on which the change of assignment state has succeeded are followed by .....OBSERVED.
An error may occur when the tool is running. In this case, the name of the NE concerned by the error is
followed by Failure : <cause of the failure>.
The possible causes of failure are :
Master workstation not found : Impossible to find, in the APMAN configuration file, the hostname
of the MASTER workstation of the OS
Bad User Label : Impossible to find the user label of the NE inside the file of persistency of PNM
Hostname not found : Impossible to find, in the APMAN configuration file, the hostname where the
EMLIM is running
Nectas File not found : Impossible to find the nectas file corresponding to this NE
If another message is displayed, it will contain the error found by the shell script itself.
1AA 00014 0004 (9007) A4 ALICE 04.10
Restrictions : Available for ADM only.
ED
01
957.130.932 V

354
222 / 354

Figure 176. Change state operation running
11.19 Switch Old/New Practice Option

N.B.
This option allows the operator to change the name of the emlim persistency file during a migration phase.
Observed.
Figure 177. Switch Old/New Practice

Select the NE as given in paragraph 11.2 to choose the NE on which the switch old/new practice operation
is to be done.
1AA 00014 0004 (9007) A4 ALICE 04.10
The following confirmation window is then displayed:.
Figure 178. Switch Old/New Practice confirmation window

Click on the Yes or No push button to confirm or cancel the switching.
ED
01
957.130.932 V

354
223 / 354
11.20 Set offline board and set offline signal label option
a)
b)
This chapter is applicable to some QB3* NEs.

N.B.
set offline board is applicable for:

1)
1651sm/smop 2.4 and 2.5
2)
1661smc/smcop 1.4 and 1.5
3)
1664sm 2.1
set offline Signal LAbel is applicable for:

1)
1641sm/smop 2.7
2)
1651sm/smop 2.5
3)
1661smc/smcop 1.5
These tools allow to apply the action on a group of resources in one shot.
The usage of the tool needs to stop the EMLIM process managing the concerned selected NE. After the
running of the tool, the restart of the EMLIM process will take into account the modification and the NE.
11.20.1 Set offline board
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 179. Set Offline Board

N.B.
ED
The complete list of NEs (shown above) is displayed only after clicking on Filter.
01
957.130.932 V

354
224 / 354


When the selection is made a new window is displayed and the user has to select Apply to continue or
Quit to cancel.
Figure 180. Ne Label
1AA 00014 0004 (9007) A4 ALICE 04.10
If Apply button was pressed a new window for confirmation is shown.
ED
01
957.130.932 V

354
225 / 354

Figure 181. Confirmation

followed by Failure : <cause of the failure>
11.20.2 Set offline Signal label
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 182. Ne selection
ED
01
957.130.932 V

354
226 / 354
N.B.
The complete list of NEs is displayed only after clicking on Filter.


When the selection is made a new window is displayed showing the current configuration
Figure 183. Current setup
1AA 00014 0004 (9007) A4 ALICE 04.10
modify the current setup, see below, and press apply to change it.
ED
01
957.130.932 V

354
227 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 184. New setup
When apply is pressed the confirmation box is presented to the user.
ED
01
957.130.932 V
354
228 / 354

Figure 185. Confirmation
1AA 00014 0004 (9007) A4 ALICE 04.10
followed by Failure : <cause of the failure>
ED
01
957.130.932 V

354
229 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
957.130.932 V
11.21 Ping NE Option
This option is used to test the reachability of NEs.
01
354
230 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 186. Ping NE
ED
01
957.130.932 V
354
231 / 354

In the Ping From: area, click on the radio button associated to the supervision Area from which the
Ping action is going to be performed.
N.B.
The NEs are displayed indipendently from the supervision area.
There are four ways to add NEs in the list:

N.B.
1)
The NEs listed are the NEs that are going to be tested.
NE User label
2)
Enter the user label of the NE in the NE user label field.
Click on the associated Add pushbutton: the corresponding NE is added in the list.
NSAP address
3)
Enter the NSAP address of the NE in the NSAP field.
Click on the associated Add pushbutton: the corresponding NE is added in the list.
Add by supervision area
Click on the Add by supervision area ... pushbutton: the following window is displayed.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 187. Ping NE Add by supervision area
4)
Choose a supervision area by clicking on the associated radio button.
Enter the user label in the NE user label field.
Click on the Add pushbutton: the corresponding NE is added in the list.
Add by location name
ED
Click on the Add by location name ... pushbutton: the following window is displayed.
01
957.130.932 V

354
232 / 354


Figure 188. Ping NE Add by supervision area
Choose a location name by clicking on the associated radio button.
Enter the user label in the NE user label field.
Click on the Add pushbutton: the corresponding NE is added in the list.
To remove one or several selected NE(s) from the list:

N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
Select the NE in the list.
Click on the Remove pushbutton.
To remove all NEs from the list, click on the Remove all pushbutton.
To perform the Ping action, more than one possibility exists:
To ping one or several NEs, select the requested NE(s) in the list and click on the Ping
pushbutton.
To ping all NEs, click directly on the Ping all pushbutton.
The results of the reachability test is displayed in the Reachable Element and Unreachable Element
areas (see Figure 189. ).
ED
01
957.130.932 V

354
233 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 189. Ping NE Results
ED
01
957.130.932 V
354
234 / 354
11.22 List Gateway NE

This tool allows the administrator to:
edit a text list of NE names which are working as a gateway NEs inside a DCN structure;
view the list.
The system will not actually do any check whether the information contained in the list are really consistent
with the DCN building.
The operator can filter on all the NEs families defined and the QB3* NEs type:
ALL
each of the type managed.

The List Gateway NE dialog is shown in the figure:
Figure 190. List Gateway NEs

As default, the system adds a specific NE (if included in the NE Global Inventory list) in the set of Gateway
NEs if in the Application Local Configuration (in persistency files on EMLIM QB3* NEs type&release) the
ETHERNET value is set to YES.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Is planned (in SH5.3.x) a new delivery of this feature in which it will be possible to modify this
information using the same interface.
01
957.130.932 V

354
235 / 354
This option is used to configure in the local network the name and IP address of the Lower and Upper AU.
The operator must configure the AUs addresses before use the 1641SX Maintenance menu dialog.
Figure 191. 1641SX TCPIP Address Configuration

The results of adding a Lower and Upper Au IP address is to update the /etc/hosts of the master
workstation with a conventional name and address added in this window for each AU.
1AA 00014 0004 (9007) A4 ALICE 04.10
Only for instance, the /etc/hosts dummy items as result of the previous configuration address fields should
be the following:
121.121.213.21 lowerAUNE102_004
and
32.122.3.34 upperAUNE102_004
ED
01
957.130.932 V

354
236 / 354

11.23 DXC TCPIP Address Configuration
11.24 Change User Label Format

This feature allows the operator to select the type of User Label Format between:
TSD format
TSD compact Format
for the Q3 NEs, as shown in the figure:
Figure 192.
It is strongly suggested to decide the format at installation time.
This function is available when the SH system is stopped (otherwise the Update File button remains
greyed). The operator executes the choice, clicks on Update File button to confirm or Exit without change
a new format.
The following warning will be displayed to confirm the TSD format change:
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 193.
Then, the operator can restart the system: the TSD format changes will be visible on all the different
EMLUSM views, Alarms, PMV etc..., anywhere User labels are displayed. For example for the 1650SMC
1.1, the following User Labels in TSD normal format (navigating from the main view to a board view):
RACK
rack#01
SR50C r01/Subrack#1
CONGI r01sr1/board#04
will be displayed in TSD compact format as:
RACK
01
ED
01
957.130.932 V

354
237 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
SR50C
CONGI
011
01104
01
957.130.932 V
354
238 / 354

12 PERIODIC ACTIONS
12.1 Overview
This functionality allows the administrator to manage peiodic actions.
When clicking on the Periodic Actions option, the following window is displayed:
Figure 194. Periodic Actions Menu
12.1.1 Access rights

1AA 00014 0004 (9007) A4 ALICE 04.10
SMF Command
Access rights
Add a scheduled action
View a scheduled action
Remove a scheduled action
Table 38. Periodic Options: Access rights for different User Profiles
ED
01
957.130.932 V

354
239 / 354
12.2 Add a scheduled action Option

Figure 195. Set Scheduling Time Window (step 1)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Select an action in the Action list. The selected action appears in the Setting field and the Minutes,
Hours, Day of week and Day of month push buttons become active as shown in the following figure.
01
957.130.932 V

354
240 / 354

Click on the Minutes pushbutton.

Select a value in the list that appears in the right part of the window, then click on the righttoleft
arrow in order to transfer the selected value in the Minutes field.
Repeat the same operations for the hour, the day of week and the day of month. The following table
gives some examples of periodicity.
Periodicity of action
Minutes
Hours
Day of week
Day of month
every day, every hour, at 0 and 30 minutes
0,30
on Mondays, at 9:35
35
on the 1st of the month, at 9:35
30
23
15,30
1AA 00014 0004 (9007) A4 ALICE 04.10
at 23:00 on the 15th and 30th of the month 0

and on Fridays
N.B.
ED
In order to modify the values in these fields, the operator has to select the value to change
by selecting it with the mouse, then by clicking on the lefttoright arrow, then by repeating
the operation above.
01
957.130.932 V

354
241 / 354
Click on the Check & Update push button. If the chosen values are correct, they appear next to the
selected action of the Action list, as shown in the following figure.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on the Apply push button to validate the modifications. The following information window
appears.
Figure 198. Information Window
ED
01
957.130.932 V

354
242 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
Click on the Ok push button.

Click on the Close push button of the Set Scheduling Time window.
01
957.130.932 V
354
243 / 354
12.3 View scheduled actions Option

Figure 199. Show Scheduling Time Window
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Click on the Print or Close push button to print the content of the window or to close the window.
01
957.130.932 V

354
244 / 354
12.4 Remove a scheduled action Option

Figure 200. Cancel Scheduling Time Window
1AA 00014 0004 (9007) A4 ALICE 04.10
Select in the Action list the action to remove. The Cancel push buttons becomes active.
Click either on the Close push button to close the window without change or on the Cancel push
button to remove the selected action. In the second case, the following confirmation window is
displayed.
Figure 201. Confirmation Window
ED
01
957.130.932 V

354
245 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Click on the Yes or No pushbutton to confirm or cancel the current action.

If the operator clicks on Yes, the selected action disappears from the Cancel Scheduling Time
window.
Click on the Close push button to close this window.
01
957.130.932 V

354
246 / 354


13 1641SX MAINTENANCE
13.1 NE/AU Selection
13.1.1 Access rights
The item 1641SX Maintenance is displayed on the SMF main menu for the users (see chapter 7.8):
administrator (group admin for the user axadmin and axemladm);
operator (user axemlope);
constructor (user axemlcst);
They are allowed to use this menu, but only the administrator can select the AU/NE selection dialog (as
shown in next figure). The other user can select also tape and floppy management functions:
copy files from /alcatel/export directory to floppy or tape;
copy remote inventory to floppy or tape;
list the content of floppy or tape.

These functions alway check if the device is available.
To summarize:
SMF Command
Access rights
All SMF 1641 SX Maintenance functions
admin
copy files from /alcatel/export to floppy
admin, axemlope, axemlcst
copy remote inventory files to floppy
copy files from /alcatel/export to tape
copy remote inventory files to tape
list content of tape
list content of floppy
viewer
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 39. 1641SX Maintenance: Access rights for different User Profiles
ED
01
957.130.932 V

354
247 / 354
13.1.2 NE/AU Selection dialog

This dialog is displayed for the user axadmin:
Figure 202. 1441SX main menu
1AA 00014 0004 (9007) A4 ALICE 04.10
To operate the SMF menu, the user has to choose in the first step one of the maximum up to 32 NEs and
then, in the second step, one of the 2 possible AUs of the two selection points: upper or lower. On the
SH the state of the AU (active or passive) are ascertained via SHscript. If the upper AU is in active state,
the lower AU can only be in passive state and vice versa.
ED
01
957.130.932 V

354
248 / 354

Figure 203. 1641SX Maintenance

Selecting one of the available NEs (and if needed a possible AUs) the operator can activate the following
dialog box:
AUMaintenance: to manage the AUs states, to view the files on the AUs and to maintenance the
NTProtocol and configure the OSI address;
Trasmission Maintenance: to aid the operator to manage and configure the cross connections and
the trasmission processes;
Backup and Restore: to manage the AUs backup and Restore onto the local SH tape device;
Data Export: to manage export of the PM data, FMCAT data and other persistency files from AU to
SH;
Software Download: to mount/unmount the CDROM device and manage the software download
to upper and lower AU;
AckStation_Alarms: to acknowledge all the station alarms on the selected AU.
N.B.
The AU Maintenance tool must not be installed on a Presentation workstation in SH5.1.1.x

delivery package.
The operator can also click on the following buttons:
Close: to leave the 1641SX Maintenance Screen;
Help: to display a on line Help.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
For detailed information see [15], chapter 1.
01
957.130.932 V

354
249 / 354
13.2 AU Maintenance
AU services: the operator will be allowed to manage the reboot of the AU, switchover the AUs, recover and
save the AU from/to save areas;
View files on AU: the dialog will show the files in the /home and /tmp directories of the AU.
Protocol Maintenance: the dialog will show the Network Time Protocol and the Configuration of OSI
Addresses;
Figure 204. 1641SX Maintenance Menu

From the menu, the operator is also allowed to select:
Help: to display a on line help;
Return: to go back to previous menu;
Exit: to leave the functionality and return to the 1664SX Maintenance Screen.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
For detailed information see [15], chapter 1.1.
01
957.130.932 V

354
250 / 354

The following functionalities are available:
13.2.1 AU Services

Selecting the option 1 in the previous user dialog the system displays the AUservices submenu:
Figure 205. 1641SX AU services

The operator can select the items:
Reboot AU: selecting this option causes the state of the AUs to be displayed (the system executes
the AU states checking). The user must then establish if an AU reboot is appropriate and safe, given
the states of the AUs at the time.
Rebooting the active AU on the redundant system will cause an implicit switchover (ie. the passive
AU will become active).
The user is given the chance to confirm or cancel the operation. If yes the system starts the reboot
procedure of the lower or upper AU (the AU selected in the 1641 Maintenance Screen). The user is
also given the chance to wait for the AU to come back before proceeding. and ;
AU switchover: the system executes the checking of AU states and identificate the passive and
active AUs in fact this function forces a switch between active and passive AUs.
1AA 00014 0004 (9007) A4 ALICE 04.10
The user is given the chance to confirm or cancel the operation. If yes the system activates the
switchover procedure: at the end the AUs switch roles: the currently active AU will become passive
and vice versa.
To maintain some level of system integrity, serializes switchovers are not allowed. The AU will reject
a switchover if a switchover has recently taken place. In this case you should wait for a while (15
minutes) and try again.
ED
Recover from save area: selecting this option allows the user to restore configuration data from a
dedicated save area on the AUs hard disk. Note that this operation can only done on a passive AU.
01
957.130.932 V

354
251 / 354
Save Complete AU: selecting this option allows the user to save vital configuration data to a
dedicated save area (normally not used) on the AUs hard disk. Note that this operation can only
done on a passive AU.
the system executes the AU states checking then displays a confirm dialog to the operator and starts
the save procedure of the lower or upper AU selected; if the operator chooses the n option the
operation will be cancelled;
AU synchronization states: selecting this option causes the current states of synchronization
between the AUs to be displayed. This may be useful to establish before and after maintenance
activity.
Note that following a backup or a reboot, the AUs take some time to resynchronize. In such
circumstances the synchronization check may fail. Please allow 5 minutes to elapse before checking
again.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V

354
252 / 354

The system executes the AU states checking then displays a confirm dialog to the operator and starts
the recover procedure of the lower or upper AU selected; if the operator choice the n option the
operation will be cancelled;
13.2.2 View files on AU

Figure 206. 1641SX View files on AU

The operator can select only the item:
1AA 00014 0004 (9007) A4 ALICE 04.10
View Files on AU: the system establishes the AU type of the AU selected in the 1641 Maintenance
Screen then activates a file viewer to show the AU files in the /home and /tmp directories of the AU.
The most common Vi command are summarized:
h
help
q or Q
quit
<blank> or \n next page
l
next line
d or ^D display half a page more
. or ^L
redisplay current page
f
skip the next page forward
n
next file
p
previous file
$
last page
w or z
set window size and display next page
s savefile save current file in savefile
/pattern/ search forward for pattern
?pattern? or ^pattern^
search backward for pattern
!command execute command. Most commands can be preceded by a number, as in:
+1\n (next page);
1\n (previous page);
1\n (page 1).

See the manual page for more detail.
ED
01
957.130.932 V

354
253 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED

01
957.130.932 V

354
254 / 354
13.2.3 Protocol Maintenance

Figure 207. 1641SX Protocol Maintenance

The operator can select the items:
NTProtocol: the system verifies the active or passive state of the selected AU then shows a menu
in which the user is allowed to:
display the NTP status and configurations on AU;
restart the selected AU;
set the DCF time on the AU.
Configuration of OSI address: the system shows a dialog box to configure and change the OSI
addresses by editing the OSIaetable.cfg.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
For detailed information see [15].
01
957.130.932 V

354
255 / 354
13.3 Trasmission Maintenance
Matrixmaintenance: allows the user to activate, force or enable the cross connections:
activate: asks for arguments and calls mxquery.sh script on the AU;
force: asks for arguments and calls mxforce.sh script on the AU;
enable: asks for arguments and calls mxautomode.sh script on the AU;
Configuration maintenance: allows the user to:
reset board (UBPE/SP);
change alarm persistency time for TPalarm;
restart the VHMprocess (SX1641);
edit the IVME.cfgfile and restarted the MIBprocess.
List of all the timescheduled connection: allows the user to list up all timescheduled connection on the
AU.
Figure 208. 1641SX Trasmission Maintenance Menu

1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
01
957.130.932 V

354
256 / 354

The following items are available:

13.3.1 Matrix Maintenance

Selecting the option 1 in the previous menu the system displays the submenu as shown in the figure, that
allows to do different operation on the matrix system maintenance:
Figure 209. 1641SX Matrix Maintenance

The user can choose:
mxquery [ w | f | <board> | h ]
help on line TBC
w
trigger copy supervision for the (w)hole system
f
trigger supervision for copy with (f)ailures
<board> trigger copy supervision for single IOB45/STM1/ETB
Syntax: Rack#.Subrack#.Board# eg 1.1.10
h: print help
This tool provides information for every cross connection.
This command requires the auto mode command for the whole system. f one IOB is in a forcedmode or it is
an optical protection board, it answers with INVALID.
mxforce [ a | b | h ]
a
force matrix copy **a** for all IOB45/STM1/ETB of the system
b
force matrix copy **b** for all IOB45/STM1/ETB of the system
h: print help
1AA 00014 0004 (9007) A4 ALICE 04.10
his tool forces the matrix copy (a or b) for all boards.

Remark: In case of an active equipmentprotection all of these commands will be executed for the protection
board! Avoid to change the equipmentprotection state during use of the MMT.
The forced state of an IOB gets lost by any protection action.
ED
01
957.130.932 V

354
257 / 354
mxautmode

This tool returns all boards to automode.

This is the default mode of the system.
The matrix copy selector selects the matrix copy with a better quality.
1AA 00014 0004 (9007) A4 ALICE 04.10
From the menu, the operator is allowed to select:
ED
01
957.130.932 V

354
258 / 354
13.3.2 Configuration Maintenance

Selecting the option 2 in the previous menu the system displays the submenu as shown in the figure:
Figure 210. 1641SX Configuration Maintenance

The user can choose:
Reset Board: selecting this option the user can reset the UBPE/SP board using the function:
reset <board_name> [S]
which is used by VCS. Observe that the option S indicate if the start is warmstart or coldstart.
The complete list of boar names could be found, for instance, in the Reset Board Submenu.
Change TP alarm: allows to change the alarm persistency time for TP alarm;
Restart MIB process: allows the user to edit the IVMO.cfg file and restart the MIB process.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V

354
259 / 354
13.3.3 List of all timescheduled connections

Selecting the option 3 in the previous menu the system displays the submenu as shown in the figure:
Figure 211. 1641SX scheduled connections

The user can choose only the item:
List all time scheduled conn: to list all the time scheduled cross connections stored in the Cross
Connection List Configuration File. The user can find a copy of this file in /tmp/PersDump.TCC.
There is a restriction for this function: the selected AU must be in active state.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V

354
260 / 354
13.4 Backup and Restore

Backup: the backup maintenance allows the user to make a complete AU backup onto the local SH tape
device.
There are the restrictions:
One backup per tape is possible.
In the X.25 remoteconnections backup is not supported.
Restore: The restore maintenance allows the user to select a backup, restore it on AU and restart the application
and reload system configuration or powerdown the system.
There are the restrictions:
One backup per tape is possible.
it is not possible to reload the system configuration on passive AU.
Show Contents: The show contents Menu allows the user to select a backup and show the contents of it.
Figure 212. 1641SX Backup&Restore Menu

1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
01
957.130.932 V

354
261 / 354
13.5 Data Export
The data_export maintenance allows the user to:
Export PMdata and FMCATdata: as UNIXASCIIfile from AU to the SH;
Export the FMCAT Data: as UNIXASCIIfile from AU to the SH and (fault management
concatenates data) in compressed (fzip) size from AU to the SH;
Export RI Data: read the contents of the FM persistency file and write them in a formatted way to the
stdout;
Figure 213. 1641SX Data Export Menu

1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
01
957.130.932 V

354
262 / 354

13.5.1 Export PM Data

Selecting the option 1 in the Data Export Maintenance Menu the system displays this second menu dialog:
Figure 214. 1641SX Export PM Data

The operator is allowed to select:
1AA 00014 0004 (9007) A4 ALICE 04.10
Make PM data backup: selecting this choice the system displays the options to backup the PM data
to local hard disk or tape drive (if exists):
Write PM backup to SH hard disk: selecting this option the system displays a menu to choose
the period of time:
15 minutes;
24 hours;
Now it checks the AUs states and start the selected backup procedure.
Write PM backup to SH tape drive: selecting this option the system displays a menu to choose
the period of time:
15 minutes;
24 hours;
Now it checks the SH tape drive and start the selected backup procedure.
Write PM backup to SH hard disk and tape drive: selecting this option the system displays
a menu to choose the period of time:
15 minutes;
24 hours;
Now it checks the AUs states and the SH tape drive and start the selected backup procedure.
Display Contents of PM data backup tape: selecting this choice the system checks the SH tape
drive in order to display its PM data;
Display PM data of the SH Hard Disk: this option displays a menu to choice the period of time:
15 minutes;
24 hours;
Now it find the PM data on hard disk and displays them.
ED
01
957.130.932 V

354
263 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED

01
957.130.932 V

354
264 / 354

13.5.2 Export FMCAT Data

Selecting the option 2 in the Data Export Maintenance Menu the system allows the user to export the
FMCAT (fault management) data form the selected AU to the CT reading the contents of the FM
persistency file and write it formatted to a log file.
13.5.3 Export RI Data

Selecting the option 3 in the Data Export Maintenance Menu the system displays this second menu dialog:
Figure 215. 1641SX Export RI Data

The operator is allowed to select:
Make RI data export: selecting this choice the system creates a text file on the SH which details the
remote inventory (RI) data know to the NE.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V

354
265 / 354
13.6 Software DownLoad

SW download to upper AU;
SW download to lowerAU;
the mount of the CDROMDevice for SW download;
unmount of the CDROMDevice for SW download.
Figure 216. 1641SX Sw Download Menu

Sw Download: selecting this option the system checks the state of the selected AU (upper or lower)
and then start the download procedure;
Mount the CDROM device: selecting this option the system checks for the device
/dev/dsk/device_name on /SD_CDROM (the user must insert the CDROM before mounting) and
then, if there are not problems, display the operation result;
Unmount the CDROM device: selecting this option the system displays a message box with
status/result of the operation. If the umount is executed successfully there are no other messages.
In case of unmount problems, the SH5 host system can be in bad shape and must be rebooted
(shutdown, switch off and switch on again).
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
01
957.130.932 V

354
266 / 354
13.7 AckStationAlarm


AcknoledgeStationAlarms: the operator is allowed to acknowledge all the station alarms on the selected
AU.
The system checks if the AU is in active state: otherwiese displays a warning message.
Figure 217. AckStationAlarms

1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
01
957.130.932 V

354
267 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V
354
268 / 354

14 REMOTE MAINTENANCE IN SH5

14.1 Introduction to GoGlobal
GOGlobal Version 1.6.5.1 is a PC X server application package that provides access to X applications
running on UNIX host computers from PC display devices.
GOGlobal is comprised of two pieces of software: GlobalPC residing on the desktop device and
GlobalHost on the UNIX host machine:
the Unix software product is available starting from bootable media.
to install GOGlobal on PC:
download the executable file:
gpc_165.61.exe included in the bootable 17a version (in /usr/G11R6.1/pc directory)
execute it (doubleclick on the file or selecting the Run option from the Start menu)
launch the interactive setup (setup.exe).
For an explanation about the GOGlobal Installation on PC and Host see the SH5 Installation Guide [16].
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
This chapter is applicable to the new GOGlobal PC X server Versions 1.6.5.1
01
957.130.932 V

354
269 / 354
14.2.1 Creating a new generic connection

Start GOGlobal. In order to create a connection you have to choose the icon New from the Connection
Manager or the menu Connection/New.
First, assign a name to your connection. You may find it useful to provide a descriptive name for the
connection (connection names may contain spaces).
Figure 218. Connection Name

The name is used in the Connection Manager to identify it from the other connections, and does not
determine the type of connection or its attributes. When youre defining a new connection you can decide
to create it completely new or copying settings from a previously defined connection.
N.B.
The figures in this chapter are related to GOGlobal version 1.5 but the new version 1.62 and
1.63 are functionally equivalent (dont take into account the version number).
The Connection Manager contains a list of all the connections currently in GOGlobal. For this example,
type tlvhac_login in the Connection name field. Click Next to continue.
In the next dialog, there are two connection types to choose.
1AA 00014 0004 (9007) A4 ALICE 04.10
Choose Network connection and check that radio buttons below are not selected. In order to complete
a network connection, the following information is needed:
The UNIX host name you are connecting to; this has to be inserted in one of the following forms:
an individual host name;
an IP address in numeric form.
The connection port type to be chosen in the port field after clicking on Details button: be sure that
the one selected is telnet. Then click Ok.
ED
01
957.130.932 V

354
270 / 354

14.2 GOGlobal Connections creation

Figure 219. Host Name

Click Next to continue.
14.2.2 Completing the connection with log in phase
Click Script Editor to configure your log in.
Now you have to insert the correct commands in order to perform a correct log in. Respect the example
and fill the two commands:
I command:
Type in the Wait for: field >
Type in the Transmit: field cd /usr/G11R6.1/bin

with the Enter radio button selected then click Insert.
II command:
Type in the Transmit: field ./goglobal

1AA 00014 0004 (9007) A4 ALICE 04.10
Click Ok.
ED
01
957.130.932 V

354
271 / 354

Figure 220. Log in Connections

Click Finish to complete your first connection.
It is possible introduce only a command. In the example:
Type in the Transmit: field /usr/G11R6.1/bin/goglobal

Click Ok and then Finish to complete the connection.
14.2.3 Creating a new connection with automatic login
The user has to execute the following steps:
Create a new connection.
Insert the related name.
Click Next to continue.

When you are in the Connection type window, choose Network connection, insert the host name in the
Host field and check the follow radio button: Connect directly to the X server, bypassing login shell. In the
same window click Details button and select gologin port in the Port field.
Click Ok. Click Next to continue.
1AA 00014 0004 (9007) A4 ALICE 04.10
When you are in the AutoLogin window, insert your login ID and password.
ED
01
957.130.932 V

354
272 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 221. Automatic connection
Click Finish to complete your connection.
ED
01
957.130.932 V
354
273 / 354

14.3.1 Opening a connection

To open a connection, it must first be selected by clicking on the name in the Connection Manager as
shown in the figure:
Figure 222. List of connections

N.B.
The figures in this chapter are related to GOGlobal version 1.5 but the new version 1.62 and
1.63 are functionally equivalent (dont take into account the version number).
After selecting the connection, open it in one of the following ways:
Click on the Toolbar (Connect icon).

Select Connect! in the Connection menu.
Right click on the connection and select Connect!
Press the Enter key.
Double click on the connection.
If a generic connection is chosen, a telnet window will appear where you have to insert login ID and
password; no actions have to be performed if an automatic log in connection is opened.
GOGlobal can be connected to one host or multiple hosts. Managing these connections is done through
the Connection Manager which maintains a connection list showing one name per connection. Each
connection maintains its own attributes, such as text window size and text color. Though unique attributes
are maintained for each connection, you can apply any attribute changes or updates to all the connections
(such as font size) with one operation.
1AA 00014 0004 (9007) A4 ALICE 04.10
Connections can be created, edited, or deleted, as well as moved up and down in the connection list. As
with other functions in GOGlobal, these operations can be initiated in several ways:
ED
Click Toolbar buttons.

Select from menus.
Right click on the desired connection and make selections.
Use hot keys shown on the right side of menus.
01
957.130.932 V

354
274 / 354

14.3 GOGlobal connection management
1AA 00014 0004 (9007) A4 ALICE 04.10

14.3.2 Editing a connection

Any connection parameters may be changed. If the connection is open when you change the parameters,
the new setting will not take effect until the connection is reopened. As with creating a connection, there
are several ways a connection can be edited. First, you select the connection to be edited by clicking on
it. Editing a connection is initiated in one of the following ways:
Click on the Toolbar.
Select QuickEdit... in the Connection menu.
Right click on the desired connection and select QuickEdit....
Simultaneously press the Alt and Q keys.

Note: The editing process is identical to creating a new connection when using the Connection Wizard.
Note: It is not possible convert a login connection to an autologin connection.
It is important that modifying the paramaters for the connection to 1353SH system, the
Autocopy from host selection to Clipboard and Autocopy from Clipboard to host selection
options remain unselected as shown in the Figure 223.
ED
01
957.130.932 V

354
275 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 223. Copy and paste options
ED
01
957.130.932 V
354
276 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

14.3.3 Exiting a connection

When you are connected with GOlogin port (automatic log in connection) its enough to exit the
application (1353SH or 1354RM) and all windows related with the current connection will be closed.
If your connection is telnet type you have to exit the application and close the telnet window.
ED
01
957.130.932 V

354
277 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V
354
278 / 354

15 NETWORK TIME PROTOCOL

15.1 NTP Overview
15.1.1 NTP implementation
The Network Time Protocol (NTP) defines a set of procedures for synchronizing clocks on hosts connected
to a network with access to the Internet. NTP goes beyond simple routines that occasionally query a time
server and adjust a local clock to a time value received from the server.
NTP has the ability to continually keep a server or workstations time in sync with Coordinated Universal
Time (UTC).
NTP is a tiered time distribution system with redundancy capability. NTP measures delays within the
network and within the algorithms on the machine on which it is running. Using these tools and techniques,
it is able to synchronize clocks to within milliseconds of each other when connected on a Local Area
Network and within hundreds of milliseconds of each other when connected to a Wide Area Network.
The tiered nature of the NTP time distribution tree enables a user to choose the accuracy needed by
selecting a level (stratum) within the tree for machine placement. A time server placed higher in the tree
(lower stratum number), provides a higher likelihood of agreement with the UTC time standard.
Some of the hosts act as time servers, that is, they provide what they believe is the correct time to other
hosts. Other hosts act as clients, that is, they find out what time it is by querying a time server. Some hosts
act as both clients and time servers, because these hosts are links in a chain over which the correct time
is forwarded from one host to the next. As part of this chain, a host acts first as a client to get the correct
time from another host that is a time server. It then turns around and functions as a time server when other
hosts, acting as clients, send requests to it for the correct time.
Should the time server from which NTP is synchronizing fail, NTP retains the ability to maintain an accurate
clock.
The network time daemon, xntpd is the program running on each of the hosts in the network that, following
the conventions defined in the protocol, attempts to establish the correct time. It does this by using the best
available source of time to synchronize the host clock with the time at zero longitude, known as
Coordinated Universal Time or UTC.
1AA 00014 0004 (9007) A4 ALICE 04.10
There are some guidelines for implementing NTP depending of the network size:
If the network is small, consisting of around a dozen hosts, you need only a single NTP time server
on your network. Locate three time servers elsewhere on the Internet from which your time server
can get the correct time. If possible, pick two stratum 2 servers and one stratum 3 server. Ideally, you
should choose to get the time from servers that are closest to your host in terms of roundtrip delay.
In other words, you should prefer servers for which the amount of time it takes to send a request for
the current time and the time it takes to receive a response is smallest. However, there is no great
harm if you select servers for which you do not know the roundtrip delay.
If, however, the network is large, consisting of dozens or hundreds of hosts, you should set up a larger
number of time servers. A good rule of thumb is to have one time server for every dozen hosts. In
this case, you first establish a few stratum 2 time servers, then you establish the remaining time
servers as stratum 3 time servers. Finally, all of the remaining hosts, which constitute the vast majority
of the hosts on the network, become stratum 4 hosts.
ED
01
957.130.932 V

354
279 / 354
The xntpd program is a daemon which maintains a UNIX systems timeofday in agreement with Internet
standard time servers. xntpd is a complete implementation of the Network Time Protocol (NTP) version
3 standard as defined by RFC 1305 and also retains compatibility with version 2 servers as defined by
RFC 1119 and version 1 servers as defined by RFC 1059.
The computations done in the protocol and clock adjustment code are carried out with high precision to
try to maintain an accuracy suitable for synchronizing with even the most precise external time source.
Ordinarily, xntpd reads its configuration from a file at startup time. The default configuration file is:
ntp.conf, though this may be overridden from the command line. It is also possible to specify a working,
though limited, xntpd configuration entirely on the command line, obviating the need for a configuration
file. This may be particularly appropriate when xntpd is to be configured as a broadcast client, with all
peers being determined by listening to broadcasts at run time.
In the ntp.conf file is possible define three different modes in which hosts can be directly configured to
operate with respect to synchronization with other hosts:
client mode using the statement server;

In client mode, a host polls other hosts to get the current time. From among all of the hosts
polled, the local host selects one with which to synchronize. To configure your host this way,
include a server statement in your hosts configuration file. The name or IP address of each time
server to be polled must be specified in the server statement.
symmetric active mode using the statement peer;

In symmetric active mode, a host polls other hosts and responds to polls from those hosts. In
addition, hosts retain timerelated information about the hosts with which they are
communicating. To configure your host this way, include a peer statement in your hosts
configuration file. The name or IP address of each time server must be specified in the peer
statement.
multicast (or broadcast client) mode using the statement broadcast.

In this mode, a host does no polling at all. Rather, it listens for NTP packets broadcast or
multicast over the network. From among all of the broadcasting or multicasting hosts, the local
host selects one with which to synchronize. To configure your host this way, include a broadcast
client yes statement or a multicast client yes statement in your hosts configuration file. For this
mode to function, the local time servers must be configured in broadcast mode with the
broadcast configuration statement or in multicast mode with the multicast configuration
statement.
For each host address specified is also possible define the following options:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Key: indicates that all packets sent to the address are to include authentication fields encrypted using
the specified key number (the range of which is that of an unsigned 32 bit integer). The default is
to not include an encryption field.
version: option allows one to specify the version number to be used for outgoing NTP packets.
Versions 1, 2, and 3 are the choices, version 3 is the default.
minpoll: It specifies the polling interval. The valid value for interval should be between 610
inclusive, which specifies that the minimum polling interval is 2** interval seconds minimum even
when the local daemon isnt using the remote servers data for synchronization. The default minpoll
interval value is 6 (64 seconds).
01
957.130.932 V

354
280 / 354

15.1.2 NTP daemon and configuration file

prefer: option marks the host as a preferred host. Preferred hosts determined the validity of the PPS
signal and are the primary selection for synchronization when found in the set of suitable
synchronization sources.
A general guideline is to configure all hosts, except those at the highest strata of the synchronization
subnet (those furthest away from stratum 1 servers), to operate in symmetric active mode. For those hosts
that are at the highest strata, you have a choice: configure them to operate either in client mode or in
broadcast client mode. You should consider opting for broadcast client mode if your hosts are on a
highspeed LAN that supports broadcasts efficiently, especially if the hosts number more than twenty or
so. If you do opt for broadcast client mode on those hosts, you must configure the time servers on the
local network to be both in broadcast mode (to send broadcast NTP packets on the local network) and in
symmetric active mode (to poll hosts at lower strata).
Take this large introduction as a general explanation on NTP. In fact in SH5 all hosts simply operate in client
mode. As shown in next chapter, in some configuration there is the possibility to declare two servers a
different stratum (priority level). The secondary server will be able to become the primary server in case
of unreachability of the first one.
15.1.3 The driftfile
In the ntp.conf file is usually specified the driftfile entry. It tells xntpd daemon process the name of the file
where it can find and store the clock drift, also known as frequency error, of the system clock. If the file
exists at startup, it is read and the value is used to initialize xntpd internal value of the frequency error.
The file is updated once every hour by xntpd. It usually takes a day or so after the daemon is started to
compute a good estimate of the clock drift. Once the initial value is computed, it will change only by
relatively small amounts during the course of continued operation. Because xntpd needs a good estimate
to synchronize closely to its server, there should always be a driftfile entry.
15.1.4 Other options
1AA 00014 0004 (9007) A4 ALICE 04.10
There are other options less used or used by default values. The most important are:
Precision: Indicates the precision of local timekeeping. The value is an integer which is
approximately the base 2 logarithm of the local timekeeping precision in seconds. By default this
value is set to 6.
broadcastclient yes/no: This indicates whether the local server should listen for, and attempt
to synchronize to, broadcast NTP. The default is no.
broadcast delay: Specifies the default round trip delay to the host whose broadcasts are being
synchronized to. The value is specified in seconds and is typically (for ethernet) a number between
0.007 and 0.015 seconds.
authenticate yes/no: Indicates whether the local server should operate in authenticate mode or not.
If yes, only peers which include an authentication field encrypted with one of our trusted keys (see
below) will be considered as candidates for synchronizing to. The default is no.
authdelay: Indicates the amount of time it takes to encrypt an NTP authentication field on the local
computer. This value is used to correct transmit timestamps when the authentication is used on
outgoing packets. The value usually lies somewhere in the range 0.0001 seconds to 0.003 seconds,
though it is very dependent on the CPU speed of the host computer.
ED
01
957.130.932 V

354
281 / 354
key filename and trusted key: Specifies the name of a file which contains the encryption keys which
are to be used by xntpd. The trustedkey allows the specification of the encryption key numbers which
are trusted for the purposes of determining peers suitable for time synchronization, when
authentication is enabled. Only peers using one of these keys for encryption of the authentication
field, and whose authenticity can be verified by successful decryption, will be considered as
synchronization candidates. The arguments are 32 bit unsigned integers. Note, however, that NTP
key 0 is fixed and globally known. If meaningful authentication is to be performed the 0 key should
not be trusted.
restrict: xntpd implements a general purpose addressandmask based restriction list. The list is
sorted by address and by mask, and the list is searched in this order for matches, with the last match
found defining the restriction flags associated with the incoming packets. The source address of
incoming packets is used for the match, with the 32 bit address being anded with the mask associated
with the restriction entry and then compared with the entrys address (which has also been anded
with the mask) to look for a match. The mask argument defaults to 255.255.255.255, meaning that
the address is treated as the address of an individual host. A default entry (address 0.0.0.0, mask
0.0.0.0) is always included and, given the sort algorithm, is always the first entry in the list.
statistics: enable writing statistic records.
15.1.5 Synchronization schemes and reference principles

Stated that any of the above mentioned approaches could apply in a TMN, the suggested architecture for
implementing time synchronization in 1300NM is based on the client mode (ref. section 15.1.2.)
According to the client mode, each host selects as Time Server a specific node among the lowest stratum
servers it has access to, in order to adjust its own time to the received Time reference. It is worth reminding
that it is mandatory to set the hosts date before starting the NTP daemon, because if the delta time
between the NTP client and server is greater then 1000 sec, the NTP daemon dies and no retries are
performed.
The suggested architecture consists in deducing the NTP hierarchy from the TMN hierarchy: thus the RM
layer should give the reference time to the SH layer, which in turn should give the reference time to the
NEs. USMs will then be synchronized by their relevant IMs.
1AA 00014 0004 (9007) A4 ALICE 04.10
In details:
Master RM will be the NTP server for the Spare RM (in a resilient configuration) and for RMUSMs;
Master RM will be the NTP server for the controlled Master SHs;
Master SH will be the NTP server for the other EML nodes (in a distributed configuration), for the
Spare SH (in a resilient configuration) and for SHUSMs;
SH will be the time server for its controlled NE, using ANTP;
An external NTP server (e.g. a GPS reference clock source) will play the same role as a Master Node
in the highest TMN layer.
ED
01
957.130.932 V

354
282 / 354

1AA 00014 0004 (9007) A4 ALICE 04.10

Appendix G of this document includes some examples relevant to the configuration of NTP in SH, to be
performed:
1)
on SH installation
2)
on modifing the NTP clientserver architecture (e.g. when a Master RM is installed and the
actual NTP configuration on SHs shall be updated with the link to the new time server)
Please refer to SH installation manual and to the plugin manual for the detailed description of actions to
be performed to setup NTP environment.
ED
01
957.130.932 V

354
283 / 354
15.2.1 1353 SH (HPUX Rel. 10.20) NTP configuration files.

The installation of the 1353 SH allow the user to load the system on each workstation of the Network; after
the installation phase, the configuration phase is needed. This is executed by mean of tools script included
in the 1353 SH software package and launched on the SH Master Workstation. The configuration on other
workstations is always done form the Master and, of course, these machines must be connected,
reachable and running.
The operator, in this phase, runs configuration scripts as axinitwsGui in order to specify the IP Address,
Host Name and Type (SH Master or SH EML or SH presentation) of the workstation (see the 1353SH
Installation Guide, chapter 6).
For NTP specification schema, the system must know (see the /etc/hosts) the host names and IP address
and the rule of server (for the SH Master Workstation) and client (for the SH EML and SH Presentation
workstation).
The synchronization time on all the network machines is managed in SH (HPUX) by the axxntpconf.pl
script file which configure the xntp protocol according with the NTP standard RFC 1305 specification
document.
The axxntconf procedure has to be launched at installation time; runs on the SH Master and executes
automatically the following step on the master and also on each clients:
Creates the xntpd configuration files in /etc/ntp.conf

On the master the file is copied by /usr/local/data/ntp.conf.server. On each client the file is
obtained by /usr/local/data/ntp.conf.server replacing the tag _HOST_ with the server IP
address.
Modifies the /etc/rc.config.d/netdaemons files.

On the master and each client the NTPDATE_SERVER keyword must be set to the master host
name and XNTPD must be set to 1 (to start xntpd).
kills the xntpd daemons (if active) and restart them.

See the 1353SH configuration examples in the Appendix G of this document.
15.2.2 DXC (System V Unix version 3) NTP configuration files.
The equipment controllers (UpperAU and LowerAU) of the 1641 SX are System V Motorola Unix
Release 32 Version 3.
The synchronization time on these two machines is managed with xntpd daemon according with the NTP
standard RFC 1305 specification document.
The configuration file path names differs from HPUX files. For each machine we have in the directory
folder /home/alina/process/STARTUP/ the two files:
1AA 00014 0004 (9007) A4 ALICE 04.10
actntp.conf (for the active machine or main machine);

pasntp.conf (for the spare machine or secondary).
ED
01
957.130.932 V

354
284 / 354

15.2 NTP configuration procedure in 1353 SH

On the DXC Craft Terminal is available, from SMF screen selection menu, the ntp.sh (and its
subprocess ntp_au_sub.sh) script file to configure the NTP file in the specified AU Upper and Lower and
execute some maintenance operation. The script displays a menu in which is possible:
1) show the NTP status on the specified AU;
2) allow the user to configure NTP on the specified AU (open a editor session on its NTP configuraton
file /home/alina/process/STARTUP/actntp.conf);
3) restart NTP on the specified AU;
4) allow the user to set the DCF time on the specified active AU;
H) display the Help file;
R) return to the preceding menu;
X) exit and do back to SMF screen.

See the two DXC configuration examples in the Appendix G of this document.
15.2.3 1353 SH System Administration script

Data and time.
If the date or time must be changed on a multi stations OS, it is recommended to use axhpuxconf (see
the 1353SH installation guide). In this case the perl script axxntpconf, seen in previous chapters must be
used to synchronize the time on all the workstation.
Add a client workstation.
1AA 00014 0004 (9007) A4 ALICE 04.10
If the user has to modify the configuration of the network, for instance to add a Presentation or a Element
Manager workstation, the operation must be executed on the Master workstation. All the workstation must
be connected and reachable from the master. At the end of a network reconfiguration the user have to
synchronize the time between the Master and the other workstation (EML o presentation). For this he must
use the perl script axxntpconf.
ED
01
957.130.932 V

354
285 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V
354
286 / 354

16 ALCATEL NETWORK TIME PROTOCOL

16.1 Overview
This section provides a brief explanation of ANTP (Alcatel Network Time Protocol) that is a protocol used
to synchronize timekeeping among a set of distributed time servers and clients.
16.1.1 ANTP behavior
ANTP is an Alcatel proprietary protocol which allows to have a very precise real time clock alignment
between the NEs and a reference source (ANTP server). It is bases on the algorithm implemented by NTP
(see [19]) used in the Unix environment.
The difference with respect to NTP is related to the fact than NTP works in TCP/IP environment while
ANTP protocol is based on OSI layer 3 (CLNP) communication services. As a consequence, modifications
have been performed in the interface and packet format of standard NTP product in order to be plugged
on top of CLNP.
The protocol ANTP is based on a clientserver paradigm. The NE plays the role of the client while the
server is normally located on SH. The behavior is very simple and is based on a periodic enquiry by the
client (NE) in order to discover the current time and date on the server (SH). This mechanism allows to
calculate round trips delays and average statistical values to obtain the best real time alignment between
client and server.
16.1.2 RTC distribution system architecture
The unique goal of ANTP is to keep synchronized the NEs with the reference clock servers, independently
of the accuracy of the reference source. This mechanism guarantees the alignment of the OS and NE
clocks.
Nevertheless the proposed global solution is to have a network synchronized not only internally but also
with external time reference systems (e.g. GPS). In this scenario, ANTP protocol is in charge of distributing
the clock to the Network Elements, getting this clock from a UNIX based Workstation. Its then up to native
NTP protocol to distribute the clock within the Operation Systems, getting the RTC from a GPS external
device (see Figure 224. ). In conclusion, the clock is distributed by one WS (likely the OS itself) to the NEs
using ANTP protocol. In the OS world, RTC can be distributed using native NTP protocol by a GPS device.
In order to be resilient against DCN or WS failures, two ANTP servers are present in the management
network, one of them having higher priority. In case one of them fails, the NE shall automatically refer to
the other one. Only a double ANTP servers failure, or a failure in the related DCN, will let the NEs to work
in RTC freerunning. In general, the two ANTP servers do not have to be located in the same station, even
if they can. The following pictures depict the system architecture with colocated ANTP servers
(Figure 224. ) and with not colocated ANTP servers (Figure 225. ). The latter solution allows higher
resilience against any failure.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Refer to ANTP Functional Specification, see [18], for protocol details: protocol architecture and
ANTP message format.
01
957.130.932 V

354
287 / 354
OS1
GPS
clock source
NTP protocol

OS2
OS3
OS4

ANTP protocol
NE
NE
NE
NE
NE
NE
NE
NE
Figure 224. ANTP system architecture with colocated ANTP servers

OS1
GPS
clock source
NTP protocol

OS2
OS3
OS4
ANTP protocol
NE
NE
NE
NE
NE
NE
NE
NE
GPS
clock source

OS5
ANTP protocol
1AA 00014 0004 (9007) A4 ALICE 04.10
NTP protocol
Figure 225. ANTP system architecture with not colocated ANTP servers
ED
01
957.130.932 V

354
288 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

16.2 ANTP Configuration

In 1353SH5.2.0 the ANTP server is working on LAN0 interface only. Even in multistack configuration
ANTP protocol does not need to be configured inside 1353SH.
ED
01
957.130.932 V

354
289 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V
354
290 / 354
17 PROCEDURES
1AA 00014 0004 (9007) A4 ALICE 04.10

The procedure sheets are divided as follow:
Preventive maintenance
Corrective maintenance
Failure management
Maintenance operations
Upload failure
Advanced network management
Troubleshooting
17.1 Preventive Maintenance

The Preventive Maintenance sheets are the following:
ED
Power supply failure

File system full
Hardware failures
01
957.130.932 V

354
291 / 354
Prevention operations
Protect workstations with UPS if possible.
Have a full backup tape (refer to Full Backup Disks and Full Restore Disks chapter).
The full backup tape has to be created once installation has been checked and can be done anytime
for safety.
Perform applicative backups (refer to Backup/Restore Feature chapter).

Backup network data regularly (daily if possible).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Keep track of changes.
01
957.130.932 V

354
292 / 354

POWER SUPPLY FAILURE
1AA 00014 0004 (9007) A4 ALICE 04.10

FILE SYSTEM FULL
The main actions that can be performed depending on the system configuration are the following:
Disk partitioning to contain glutton processes.
Monitor the disk usage using APMAN.
Use of the Cleanup tool (refer to System Trace & Log Management chapter).
N.B.
Possibility of automatic cleanup of files (/usr/1353sh/conf/axpurge.cfg).
Watch APMAN warnings.
N.B.
ED
The cleaning up has to be performed as often as possible without delay.
For any doubt, contact the ALCATEL support.
01
957.130.932 V

354
293 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
Against disk crash, avoid shocks and power supply failures.
Against SCSI errors, especially for an external disk, never unplug a SCSI cable while SH is running.
ED
01
957.130.932 V

354
294 / 354

HARDWARE FAILURE
17.2 Corrective Maintenance
1AA 00014 0004 (9007) A4 ALICE 04.10

The Corrective Maintenance sheets are the following:
ED
Power supply failure

File system full
Hardware failure Disk crash
Hardware failure SCSI error
Software failure Panic Unix
Software failure HPOV failure
Software failure Application bug
01
957.130.932 V

354
295 / 354
POWER SUPPLY FAILURE

Risks and symptoms

SH does not work properly.
The hardware is not fault tolerant.
Failure consequences
Data corruption is possible.

Disk crash.
Recovering operations
Reboot the system.
If the problem persists, the system will require a fsck (File System Check) operation.
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
It means that data may be corrupted and/or are not recoverable.
If damages are too important:
restore the system entirely (Full Restore operation),
restore the network data,
perform a consistency check.
01
957.130.932 V

354
296 / 354
FILE SYSTEM FULL

Risks and symptoms
System may stop.

System behaves erratically.
Data corruption is possible.

Messages related to file system full are displayed in the SH system console.
As soon as the failure is detected, stop the SH.
Perform cleanup operations in SMF:
In the System Trace & Log Management menu, select the Failure Management option.
Select the worstations and the domain for which the cleanup is necessary.
The directories likely to grow are the following:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
/var/adm/crash/core.*
/usr/1353sh/maintenance/trace
/usr/1353sh/maintenance/failure
/usr/1353sh/data/perf/save
/usr/1353sh/as/data/ascurim/histDB
/var/opt/OV/share/log/ovelog/AS30historic
If the damages are too important:
restore the system entirely (Full Restore operation),
restore the network data,
perform a consistency check.
01
957.130.932 V

354
297 / 354
HARDWARE FAILURE Disk crash

Risks and symptoms

Fatal to the system.
1AA 00014 0004 (9007) A4 ALICE 04.10
Wait for the diagnosis of the HP support.
Replace the crashed disk with identical disk.
Restore the system entirely (Full Restore operation).
Restore the network data.
Perform a consistency check.
ED
01
957.130.932 V

354
298 / 354
HARDWARE FAILURE SCSI errors
1AA 00014 0004 (9007) A4 ALICE 04.10

Risks and symptoms
The system is completely stalled.

Explicit messages are displayed with dmseg command or in /var/adm/... file.
Try to switch off the workstation.
If the operation is unsuccesful, unplug physically the workstation.
Reboot the workstation.
If error messages are displayed:
ED
Restore the system entirely (Full Restore operation).
Restore the network data.
Perform a consistency check.
01
957.130.932 V

354
299 / 354
SOFTWARE FAILURE Panic UNIX

Risks and symptoms

The workstation usually restarts.
Too many core files may cause a file system full.
UNIX kernel failure.

A core file is created in /var/adm/crash as core.n.
A reboot message is created in /var/adm/shutdownlog directory.
1AA 00014 0004 (9007) A4 ALICE 04.10
Send the core file to the ALCATEL/HP support.
Remove it with the SMF cleanup function.
ED
01
957.130.932 V

354
300 / 354
SOFTWARE FAILURE HPOV failure
1AA 00014 0004 (9007) A4 ALICE 04.10

Risks and symptoms
AS and PNM USMs are not refreshed but EML USM is.
System can not work properly.
Messages related to HPOV processes are displayed in the SH system console. The processes
concerned are: pmd, ovead, orsd (OVORS_M) and ovlad.
In automatic mode APMAN tries to reboot ????? if reboot mode enabled.
Manually, the operations have to be performed on the failed workstation and are the following:
ED
Collect traces in the /var/opt/OV/share/log directory and the /var/adm/nettI.LOGxx file.
Check possible core file in the /usr/1353sh/maintenance/core directory.
Stop all SH processes with APMAN.
Stop all HPOV processes by entering the following command: /opt/OV/bin/ovstop
Restart all HPOV processes: /opt/OV/bin/ovstart.
Restart the SH processes.
01
957.130.932 V

354
301 / 354
SOFTWARE FAILURE Application bug
An SH process managed by APMAN does not run.

SH process crash is automatically detected by APMAN.
Traces and core files are automatically collected and saved in a /usr/1353sh/maintenancefailure
directory.
Lock the failure directory.
Backup it to disk (compressed tar).
Save it on a tape.
Send tape to ALCATEL support.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
The compressed tar may be also transferred by ftp to Alcatel support.
01
957.130.932 V

354
302 / 354

Risks and symptoms
1AA 00014 0004 (9007) A4 ALICE 04.10

17.3 Failure management
The Failure Management sheet is the following:
ED
Failure management Step by step procedure
01
957.130.932 V
354
303 / 354
Operations
The operator can use:
SMF:
In the System Trace & Log Management menu, select the Failure Management option.
In the Main Menu of the Failure Management window, select the Manage Failure Directory
option.
Click on Backup, then on Main Menu to come back in the Failure Management window.
Select the Manage Backup Failure Directory option.
Select the last directory in the list and click on Save on tape.
the remote maintenance
UNIX:
The failures are on each machine in /usr/1353sh/maintenance/failure.
1AA 00014 0004 (9007) A4 ALICE 04.10
For example, a failure happened on September 2nd, 1998 at 10:16 am is in the following file:
/usr/1353sh/maintenance/failure/199809021016.
ED
01
957.130.932 V

354
304 / 354

FAILURE MANAGEMENT Step by step procedure
17.4 Maintenance operations
1AA 00014 0004 (9007) A4 ALICE 04.10

The Maintenance Operations sheets are the following:
ED
Power off the whole OS

Power off one machine
Change network area of a workstation
01
957.130.932 V

354
305 / 354
Operations
Warn the users.
Stop the complete SH manager.
Shutdown all machines (the Master must be the last one):
with SMF:
In the System Management menu, select the System Shutdown option.
Select the machines in the List of workstations.
Click either on the shutdown and halt radio button to halt the machines and then power
off it or on the shutdown and reboot radio button to reboot immediately after.
with UNIX:
see paragraph Workstation shutdown or powerup
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Power off the machines.
01
957.130.932 V

354
306 / 354

POWER OFF THE WHOLE OS

POWER OFF ONE MACHINE
Operations
Warn the users.
Stop all processes of the machine.
Shutdown the machine:
with SMF:
In the System Management menu, select the System Shutdown option.
Select the machine in the List of workstations.
Click either on the shutdown and halt radio button to halt the machine and then power
of it or on the shutdown and reboot radio button to reboot immediately after.
with UNIX:
see paragraph Workstation shutdown or powerup
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Power off the machine.
01
957.130.932 V

354
307 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
Operations
Stop the supervision of managed NEs.
Stop the SH manager.
Run Stack Configuration with the System management option in SMF.
Change the network area of the worstation (see paragraph System management / Stack
configuration).
Run Process Configuration with the Process configuration option in SMF, then select the Update
Config option in the Processes pull down menu.
Change the OS address (area) of previously managed NEs:
either with the Craft Terminal.
or with the Address Configuration option of the Local Data Management menu in SMF.
N.B.
In this case the OS address must be changed in the beginning.
N.B.
The OS address main and the OS address spare must not be changed in the same
time.
Reset these NEs.
Restart the SH manager.
Supervise and audit NEs.
ED
01
957.130.932 V

354
308 / 354

CHANGE NETWORK AREA OF A WORKSTATION
17.5 Upload failures
1AA 00014 0004 (9007) A4 ALICE 04.10

The Upload Failures sheets are the following:
ED
Minor inconsistencies
Major inconsistencies On NE side
Major inconsistencies From OS side
01
957.130.932 V

354
309 / 354
MINOR INCONSISTENCIES

Symptoms
NE is supervised.
Warning message says Updated Tables.
1AA 00014 0004 (9007) A4 ALICE 04.10
Operations
Perform a MIB Compare to get differences.
Check SH updates.
Perform more changes if needed.
Align down.
ED
01
957.130.932 V

354
310 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

MAJOR INCONSISTENCIES RECOVERY On NE side
Operations
Preparation:
Increase EMLIM trace size to 500000.
Enable all trace levels for EMLIM.
Reset cyclic traces (see paragraph System trace & log management / Trace management).
Try again to align up the NE.
Alternatives for analysis:
Use the Upload Failure Diagnosis option of the Local Data Management menu in SMF (see
paragraph Local data management / Upload Failure Diagnosis option).
Display EMLIM traces.
Use *.invalid.cfg file:
Find the NE neId and the NE emlDomain.
Stop the EMLIM
Swap the persistency files:
Save the persistency files with .save extension.
Replace it with *.invalid.cfg.
Restart the EMLIM
When it falls at the first inconsistency, find it by analysing EMLIM trace file.
Stop the EMLIM if needed.
Restore .save persistency file.
Fix inconsistencies with ECT.
Try again to supervise with align up.
Repeat the procedure until all inconsistencies are fixed.
Fix inconsistencies with ECT.
Try again to supervise with align up.
ED
01
957.130.932 V

354
311 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
Operations
Perform a MIB audit.
Use the Diagnostic of audit of the MIB option in SMF (see paragraph Local data management /
Diagnostic of audit of the MIB option).
Using the list of differences:
Change the SH configuration to mimic NE one.
Start with Appli 60 then with 56 (or 58 on ADM150).
Audit the MIB again and change the configuration until all differences are fixed.
Supervise with align down.
In the last resort: capture traces and send it to Alcatel support.
ED
01
957.130.932 V

354
312 / 354

MAJOR INCONSISTENCIES RECOVERY From OS side
17.6 Advanced network management
1AA 00014 0004 (9007) A4 ALICE 04.10

The Advanced Network Management sheets are the following:
ED
Testing reachability
Default configuration recovery
Change assigned to observed
Miscellaneous configurations
QB3* NEs NML assigned: change NEs name
Q3 NEs NML assigned: change NEs name
01
957.130.932 V

354
313 / 354
Operations
Link layer
Perform /etc/linkloop MACaddress to check if no lousy cable.
Network layer
Perform /etc/ping IPaddress (or hostname) or select HPUX then IP ping from remote
maintenance.
Transport layer
Perform an OSI ping to check any OSI transport connection:
In SMF:
From remote maintenance:
1AA 00014 0004 (9007) A4 ALICE 04.10
Run the script: /usr/1353sh/necom/axNEdiag.ptk.
Advanced Diagnosis
ED
Select 1353SH then OSI ping.
by UNIX:
Perform the Ping NE option of the Local Data Management menu (see paragraph
Local data management / Ping NE option).
nettl wrapper to analyse network packets (run_capture).
01
957.130.932 V

354
314 / 354

TESTING REACHABILITY
1AA 00014 0004 (9007) A4 ALICE 04.10

DEFAULT CONFIGURATION RECOVERY
Operations
Perform a MIB align down to download all managed tables.
Perform a MIB Compare to upload the local tables.
Perform a global align down:
ED
Wait for Aligning Down status to be cleared.
If the status remains Aligned and the DEF status is not cleared:
Perform an Access state / Local...
Perform an Access state / OS... to force a slow poll.
repeat three times if needed.
If not OK, check the DIP switches on the ECT board of the NE.
01
957.130.932 V

354
315 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
Operations
Stop the EMLIM managing the NE.
Save the persistency file.
Perform the Change Assigned To Observed option of the Local Data Management menu in the
SMF (see paragraph Local data management / Change Assigned to Observed option).
restart the EMLIM.
ED
01
957.130.932 V

354
316 / 354

CHANGE ASSIGNED TO OBSERVED

MISCELLANEOUS CONFIGURATIONS
Operations
From SMF, in the Local Data Management menu, the following options are available:
Enable RPS Switch option to enable RPS related alarms in radio NEs,
Overhead byte Configuration option,
LAPD Configuration option,
Change ASAP option to change Alarm Severity Assignment Profile of one NE,
Sync Source Selection option,
Address Configuration option to configure OS main and spare addresses and switchover
bytes.
From Unix:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
NE batch creation.
01
957.130.932 V

354
317 / 354
Operations
In order to change the NE name of a QB3* NE in a NML assigned state the following step must be
performed:
From SMF, in the Process Monitoring dialog menu:
stop related Qb3* EmlIm process (see managed NEs section in delivery notes document [17])
From SMF, in the Local Data Management dialog menu:
change the assignment state from assigned to observed;
start related Qb3* EmlIm process;
From PNM USM interface, in the Supervision menu, selecting the Stop Supervision user dialog:
stop supervision of NE (that you want to change NE name);
From PNM USM interface, in the NE directory menu, selecting the NE Info user dialog:
change the NE user label and confirm;
stop related Qb3* EmlIm process;
From SMF, in the Local Data Management dialog menu:
change the assignment state from observed to assigned;
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
start related Qb3* EmlIm process.
The NE will return in supervisioned state.
01
957.130.932 V

354
318 / 354

QB3* NEs NML assigned: Change NE name
1AA 00014 0004 (9007) A4 ALICE 04.10

Q3 NEs NML assigned: Change NE name
Operations
In order to change the NE name of a Q3 NE in a NML assigned state the following step must be performed:
From PNM USM interface, in the Supervision menu, selecting the Stop Supervision user dialog:
stop supervision of NE (that you want to change NE name); the NE must be in declared state.
From PNM USM interface, in the NE directory menu, selecting the NE Info user dialog:
change the NE user label and confirm;
From PNM USM interface, in the Supervision menu, selecting the Start Supervision user dialog:
ED
start supervision of specific NE;
01
957.130.932 V

354
319 / 354
17.7 Troubleshooting
1AA 00014 0004 (9007) A4 ALICE 04.10
ED

The Troubleshooting sheets are the following:

Alarms not coming up
NE cant be managed
Performance not displayed
OS isolation
Reproducing an applicative problem
Not enough colours
HPOV problem suspected
Customer site information
Reporting an HPOV problem
Reporting an SH problem
01
957.130.932 V

354
320 / 354

ALARMS NOT COMING UP
Study the EMLUSM working:
If EMLUSM displays the alarm, EMLIM is OK.
If EMLUSM does not display the alarm:
Restart EMLUSM:
If it is OK, it was a temporary congestion.
Perform a Supervision / Alarms / Resynchronize...:
If it is OK, it was a communication problem.
If the NE is actually in OS Isolation, it is a connectivity problem.
Stop/start EMLIM to resynchronize it with the NE:
N.B.
WARNING: all NE managed by this EMLIM are not managed during this time.
If it is OK, it may be a bug.
If the resynchronization does not display the alarm, the NE did not send it.
Study the PNMUSM working:
If PNMUSM displays the alarm, HPOV is OK.
If PNMUSM does not display the alarm:
Perform a Supervision / Refresh NE states...:
Restart PNMUSM to synchronize it with PNMIM:
Restart PNMIM to synchronize it with EMLIM:
1AA 00014 0004 (9007) A4 ALICE 04.10
If it is OK, it was a HPOV congestion.
If PNMUSM displays the alarm on another machine, it is a CPU congestion.
If PNMUSM does not display a new alarm, it is an event routing problem (the resynchronization
updates the views but not the new alarms).
If PNMUSM displays a broken red icon, the NE is in OS Isolation.
If PNMUSM displays a broken blue icon, it cant see EMLIM:
ED
Check processes are running.
Check HPOV on EMLIM and PNMIM machines.
01
957.130.932 V

354
321 / 354
ALARMS NOT COMING UP (Contd)
If ASUSM displays the alarm, no problem.
If ASUSM does not display the alarm:
Check the presence of the alarm in the historical database.
Restart ASUSM:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
If the new alarms are correctly displayed, it was a CPU congestion.
If they are not displayed, it is an event routing problem.

Study the ASUSM working:
Restart ASIM to resynchronize it with EMLIM:
If the new alarms are correctly displayed, it was a HPOV congestion.
If they are not displayed, it is an event routing problem.
01
957.130.932 V

354
322 / 354

NE CANT BE MANAGED
In case of Duplicate address error detected by PNMIM:
Check the NE address and the NE logical number.
In case of Internal Service Error within the OS:
EMLIM or stacks may be down.
In case of External Protocol Error between the OS and the NE:
If the message immediately occurs:
The NE rejects the supervision. The NE has probably a wrong OS address.
If the message occurs after some time (time out has occured). There is probably a DCN problem:
Check the DCN configuration especially areas.
Check the reachability of the NE with the Ping NE option of the Local Data Management menu
in SMF (see paragraph Local Data Management / Ping NE option).
In case of misalignment or upload rejection:
Use the Upload Failure Diagnosis option of the Local Data Management menu in SMF (see
paragraph Local Data Management / Upload Failure Diagnosis option).
In last resort:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Send XCC and EMLIM traces to Alcatel support:
Reset traces and reproduce to get relevant traces.
Check it is the right EML machine.
01
957.130.932 V

354
323 / 354
PERFORMANCES NOT DISPLAYED

In case of time out:

It may be:
Too many TPs to store.
Perfstorage times out.
Switches to offline mode.
Oracle database is down.
Check the presence of files in /usr/1353sh/data/perf/save.
Increase the PERF_PROCESS_LIFETIME in /usr/1353sh/eml/perf/conf/param.cfg:
The default time out value is 10 mn.
Keep it under collection time.
In another cases:
They may be:
Perfstorage crash.
No TP started.
Database problem.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
In order to know what is happened, open /usr/1353sh/maintenance/log/PMlogfile

which logs all actions with the Oracle database.
NE bug...
01
957.130.932 V

354
324 / 354
OS ISOLATION

Symptoms
Broken red icon on PNMUSM.

Red Q3 status on EMLUSM.
Ressource Isolation alarm in ASUSM.
Failure consequence
OS can no longer talk to NE.
Probable causes:
Rarely an OS problem.
Connectivity (hubs, routers,...) problem.
black hole effect if LAN reconnection occurs more after 30 mn.
OS polling:
The OS polling starts once OS isolation is detected. It runs every 2 mn in the first 20 mn, then every
30 mn.
LAN reconnection after more than 30 mn:
OS is not notified.
The alarm is not cleared immediately and you may have to wait up to 30 mn to see the NE icon
change.
1AA 00014 0004 (9007) A4 ALICE 04.10
Workaround: stop/start the supervision to update the icon.
ED
01
957.130.932 V

354
325 / 354
Operations:
Reset cyclic traces (see paragraph System trace & log management / Trace management).
Increase the trace level if needed (see paragraph System trace & log management / Trace
management).
Display the trace dynamically (see paragraph System trace & log management / Trace
management).
Reproduce the problem.
Dump screens if significant (see paragraph System trace & log management / Dump Screen).
Check the trace relevancy:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Traces output during the operation.
Traces not wrapped up.
If the trace size is too short, increase it and start again.
Capture data (see paragraph System trace & log management / Failure management ):
Refer to FAILURE MANAGEMENT Step by step procedure sheet.
Add the screendumps on the tape, by using tar rvf /dev/rmt/0m <Name_of_screendump>
Send the tape to Alcatel support.
01
957.130.932 V

354
326 / 354

REPRODUCING AN APPLICATIVE PROBLEM
1AA 00014 0004 (9007) A4 ALICE 04.10

NOT ENOUGH COLOURS
Probable causes:
Normally there is enough colours to operate SH, excepted maybe if:
SH applications run from remote machines (navigation).
Fancy background images are used.
Netscape runs without install option.
Operations:
Close most colourful applications and try again.
Try opening the applications in a different order.
Remove the colourful images if any.
Logout and login again.
ED
01
957.130.932 V

354
327 / 354
HPOV PROBLEM SUSPECTED

Operations:
Check the error messages in the trace files:
Look under /var/opt/OV/share/log.
Check for keywords: OVERFLOW, TIMEOUT, ABORT,...
Check the database synchronization:
Type:
for i in machine1 machine2 machine3
do
echo Comparing machine $i
remsh $i cd /opt/OV/bin; ovorsutil d > /tmp/$i
diff w /tmp/machine1 /tmp/$i
done
If something outputs (other than Comparing machine...), there is desynchronization.
Check the database connectivity:
Use OSI Ping.
/opt/OV/bin/ovorsutil t PSAPofOtherMachine
(PSAP is in /etc/opt/OV/share/conf/local_p_addr)
Check from remote maintenance:
Third parties then HPOV:
Status gives the stopped or failed processes.
ORS config checks the database consistency.
Start/Stop restarts HPOV (expert profile only).
1353SH then Log Management:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Gives the HPOV logs.
Try to resynchronize the database:
after reconfigurations (new EMLIM, plugin...).
/opt/OV/bin/ovorsutil r on all machines except the Master.
Try to restart HPOV:
Stop all SH processes with APMAN.
Stop all HPOV processes on all SH workstations with /opt/OV/bin/ovstop
Wait for a few minutes.
01
957.130.932 V

354
328 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

HPOV PROBLEM SUSPECTED (Contd)
ED
Restart all HPOV processes on all workstations with /opt/OV/bin/ovstart
Restart the SH processes.
01
957.130.932 V
354
329 / 354
CUSTOMER SITE INFORMATION
1AA 00014 0004 (9007) A4 ALICE 04.10
ED

Informations to provide to Alcatel support:

OS configuration:
Hardware.
Bootable tape version.
SH version.
Number and type of machines (M, E, P, ...).
EML Domain allocation.
Network configuration:
Number, type and versions of NEs.
NSAP address plan, GNEs...
Layout.
DCN layout.
01
957.130.932 V

354
330 / 354

REPORTING AN HPOV PROBLEM
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
HPOV version:
Bootable tape version is enough.
Output of what pmd.
nettl traces:
In /var/adm/nettl.LOG*
netfmt f filename | more to read them.
HPOV traces:
In /var/opt/OV/share/log
All of them, especially pmd.log*
Core file:
Found as /usr/1353sh/maintenance/core
Checked with file core
01
957.130.932 V

354
331 / 354
REPORTING AN SH PROBLEM
SH version:
Output of axversion.
OS configuration:
Number and type of worstations.
Contained in axconfig file.
Type and version of NEs managed:
1AA 00014 0004 (9007) A4 ALICE 04.10
Output of axdbread.
Compressed tar of failure or simply relevant trace files.
Screendumps.
ED

01
957.130.932 V

354
332 / 354

APPENDIX A : EXAMPLE OF AN AXCONFIG FILE.

/********************************************************************************************************************/
/*
An example of the 1353SH process configuration file
*/
/********************************************************************************************************************/
/******************************************************************************/
/******************************Master workstation *********************************/
WS_NUMBER:2;
/******************************************************************************/
/******************************Master workstation *********************************/
/***********************/
WS_1:
HOSTNAME:tcmh8u;
MASTER;
PR_NUMBER:14;
PR_GROUP_NUMBER:4;
{Indicates the number of the Workstation.}

{Identification name of the workstation.}
{Indicates that this WS is the Master WS.}
{Specifies the number of processes on the workstation.}
/******** Description of the processes *********/

PR_1:
PR_NAME:qb3s_ll_retix;
LRF:/usr/1353sh/necom/conf/qb3s_ll_retix.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_1;
{Indicates the number of the process.}

{Indicates the name of the process.}
{Indicates the PATH of the process.}
{Indicates the number of process restarts in
the automatic defense mode.}
{Indicates the period (in seconds) during
which the process must not fail to reset its
max_restart_nb.}
{End of the number 1 process description.}
PR_2:
PR_NAME:qb3s_ul_retix;
LRF:/usr/1353sh/necom/conf/qb3s_ul_retix.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_2;
1AA 00014 0004 (9007) A4 ALICE 04.10
PR_3:
PR_NAME:xcc_retix;
LRF:/usr/1353sh/necom/conf/xcc_retix.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_3;
PR_4:
PR_NAME:emlimadmnr31_100;
LRF:/usr/1353sh/apman/data/emlimadmnr31_100.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
CPU_STAB=20;
XCC_HOSTNAME:tcmh8u;
END_PR_4;
ED
01
957.130.932 V

354
333 / 354

PR_5:
PR_NAME:pnmim;
LRF:/usr/1353sh/apman/data/pnmim.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_5;
PR_6:
PR_NAME:ned_cpa;
LRF:/users/axadmin/1353sh/genos/data/lrf/ned_cpa.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
PR_7:
PR_NAME:ned_ih;
LRF:/users/axadmin/1353sh/genos/data/lrf/ned_ih.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_7;
PR_8:
PR_NAME:perfstorage;
LRF:/usr/1353sh/eml/perf/conf/perfstorage.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_8;
PR_9:
PR_NAME:ascurim;
LRF:/usr/1353sh/apman/data/ascurim.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_9;
PR_10:
PR_NAME:alm_cpa;
LRF:/users/axadmin/1353sh/genos/data/lrf/alm_cpa.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_10;
1AA 00014 0004 (9007) A4 ALICE 04.10
PR_11:
PR_NAME:alm_ih;
LRF:/users/axadmin/1353sh/genos/data/lrf/alm_ih.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_11;
PR_12:
PR_NAME:pmd_cpa;
LRF:/users/axadmin/1353sh/genos/data/lrf/pmd_cpa.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_12;
ED
01
957.130.932 V

354
334 / 354

PR_13:
PR_NAME:pmd_ih;
LRF:/users/axadmin/1353sh/genos/data/lrf/pmd_ih.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_13;
PR_14:
PR_NAME:swdlserver;
LRF:/usr/1353sh/swdl/swdlserv/conf/swdlserver.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_14;
PR_GROUP_1: qb3s_ll_retix qb3s_ul_retix xcc_retix;
PR_GROUP_2: pnmim ned_cpa ned_ih;
PR_GROUP_3: ascurim alm_cpa alm_ih;
PR_GROUP_4: pmd_cpa pmd_ih;
END_WS_1;
/***********************/
{End of the WS number 1 description.}
/******************************************************************************/
/******************************Second workstation*********************************/
WS_2:
HOSTNAME:tcmh8y;
PR_NUMBER:5;
PR_GROUP_NUMBER:1;
/********* WS number 2 processes description ******/
PR_1:
PR_NAME:qb3s_ll_retix;
LRF:/usr/1353sh/necom/conf/qb3s_ll_retix.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_1;
PR_2:
PR_NAME:qb3s_ul_retix;
LRF:/usr/1353sh/necom/conf/qb3s_ul_retix.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_2;
1AA 00014 0004 (9007) A4 ALICE 04.10
PR_3:
PR_NAME:xcc_retix;
LRF:/usr/1353sh/necom/conf/xcc_retix.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_3;
ED
01
957.130.932 V

354
335 / 354

PR_4:
PR_NAME:emlimadmnr31_101;
LRF:/usr/1353sh/apman/data/emlimadmnr31_101.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
CPU_STAB=20;
XCC_HOSTNAME:tcmh8y;
END_PR_4;
PR_5:
PR_NAME:perfstorage;
LRF:/usr/1353sh/eml/perf/conf/perfstorage.lrf;
MAX_RESTART_NB=3;
RESET_PERIOD=3600;
END_PR_5;
PR_GROUP_1: qb3s_ll_retix qb3s_ul_retix xcc_retix;
END_WS_2;
1AA 00014 0004 (9007) A4 ALICE 04.10
/********************** End of the Configuration file ********************/
ED
01
957.130.932 V

354
336 / 354
APPENDIX B : EXAMPLE OF A PARAM.CFG FILE FOR AN EMLIM.

COMMON {
# parameters common to one of more subsystems
traceConfiguration /usr/1353sh/eml/wdmt/wdmtnr31/conf/trace.cfg
maxTrace 1000000
#time between 2 reread of the traceConfiguration file
traceUpdatePeriod 300 #in seconds
}
HIDDEN {
# parameters that should be hidden to the customer
# will be crypted in the final product
}
EXECUTABLE ( emlim ) {
# Hosts where xcc process is running (XCC_HOSTNAME)
XCC_HOSTNAME_102 volvic
XCC_HOSTNSAP_102 39250F80000000000000010001C0C8FA5E00041D process

XCC_HOSTNAME
volvic
configuration
# parameters that are specific to one executable
# For multiple instances of the emlim process we need multiple trace files
# NOTE: there must be a %i in the file pattern this is substituted
# with the group number of the emlim.
MULTI_EMLIM_TRACE_FILE_PATTERN
/usr/1353sh/maintenance/trace/emlimwdmtnr31_%i.trace
MULTI_EMLIM_DATA_FILE_PATTERN
/usr/1353sh/maintenance/trace/emlimwdmtnr31_%i.dataflow
# For senim purpose: SEN MIB instanciation control

AVOID_SEN_USAGE True #The possible values are True or False
# Pass the article to the MO without checking bits

PASS_THRU_ARTICLE False #The possible values are True or False
# Host where XCC process is running

# Port Number to which the XCC process is listening
XCC_PORTNUMBER 10001 # default value is 10001
XCC_SPARE_OS_NSAP
# path of the config files
NAPP_CONFIG_PATH /usr/1353sh/eml/wdmt/wdmtnr31/data
# path of the perf files
NAPP_PERF_PATH /usr/1353sh/eml/perf/data
SENIM
configuration
# path of the mmem files

NAPP_MMEM_IN_PATH /usr/1353sh/eml/wdmt/wdmtnr31/data
NAPP_MMEM_REF_PATH /usr/1353sh/eml/wdmt/wdmtnr31/data
NAPP_MMEM_OUT_PATH /usr/1353sh/data/mm
NAPP_MMEM_CONVERTER /usr/1353sh/eml/em/mmconverter
1AA 00014 0004 (9007) A4 ALICE 04.10
# For senim purpose : default value for the inhibitNotifications attibute

INHIBIT_NOTIF True #The possible values are True or False
ED
01
957.130.932 V

354
337 / 354
# Forced Collect at start

PERF_FORCED_COLLECT_AT_START True
# path of the remote inventory file.
NAPP_RI_PATH /usr/1353sh/data/ri
# extension of the remote inventory file.
NAPP_RI_EXT .ri
path and file extension definition for RI
# path of the dumpNEMib file

DUMPNEMIB_PATH /usr/1353sh/data/mib
# extension of the dumpNEMib file
DUMPNEMIB_EXT .sh_mib
#extension for Config File
NAPP_CONFIG_EXT .cfg
#extension for Config Index File
NAPP_CONFIG_INDEX_EXT .idx
#extension for 15 Mn Perf Collect File
NAPP_PERF_COLL_15_MN_EXT .15Min
#extension for 1 Day Perf Collect File
NAPP_PERF_COLL_1_DAY_EXT .1Day
# extension for Perf Conf File
NAPP_PERF_CONF_EXT .cfg
file extensions definition
# path of the meas files

NAPP_MEAS_IN_PATH /usr/1353sh/eml/wdmt/wdmtnr31/data
NAPP_MEAS_REF_PATH /usr/1353sh/eml/wdmt/wdmtnr31/data
NAPP_MEAS_OUT_PATH /usr/1353sh/data/mea
NAPP_MEAS_CONVERTER /usr/1353sh/eml/em/measconverter
path and file

extension
definition for
WDMter
measurement
# extension of meas files

NAPP_MEAS_IN_EXT .measbin
NAPP_MEAS_REF_EXT .mea
NAPP_MEAS_OUT_EXT .meastxt
# Nb of Article in Job
NAPP_NB_ART_JOB 3
# Nb of SlowPoll to send to get Bit B2 after download
NAPP_NB_SLOW_POLL 30
# At valid download, time between SlowPoll
NAPP_CONFIG_TIMEOUT 5 # in seconds
1AA 00014 0004 (9007) A4 ALICE 04.10
# Number of 15 mn intervals between collection

NAPP_G784_PERF_INTERVAL_15_MIN 8
NAPP_G784_PERF_INTERVAL_1_DAY 1
# Number of 15 mn intervals between collection
# NAPP_G784_PERF_COLLECT_PERIOD 1
# Delay to perform after the end of collect
ED
performance
configuration
01
957.130.932 V

354
338 / 354

# extension of mmem files

NAPP_MMEM_IN_EXT .mmbin
NAPP_MMEM_REF_EXT .mnt
NAPP_MMEM_OUT_EXT .mm

NAPP_G784_PERF_COLLECT_DELAY 120 # in seconds

# Guard time to stop collect before next interval
NAPP_G784_PERF_COLLECT_GUARD 30 # in seconds
# Workstation name where perf monitoring
NAPP_PERF_WORKSTATION localhost
# port number of the perf storage process
NAPP_PERF_PORTNUMBER 11111
# NE transmission Timeout
NAPP_TRANS_MSG_TIMEOUT 1 # in seconds
# Slow polling Period
NAPP_SLOW_POLLING_PERIOD 12 # in 10 seconds
# Max Number of attempt in case of Response In Progress
NAPP_RESP_PROGRESS_NUM 2
# Response in Progress attempt period in seconds
NAPP_RESP_PROGRESS_PERIOD 30
# Number of restart in first phase
NAPP_FIRST_RESTART_NUM 8
# Restart period in first phase
NAPP_FIRST_RESTART_PERIOD 2 # in minutes
# Restart period in second phase
NAPP_THEN_RESTART_PERIOD 5 # in minutes
#auto time setup time
NAPP_AUTO_TIME_SETUP_TIMEOUT 2 # in hours
# Communication type (0:CMISE via HPOV , 1:CMISE via Socket)

USE_TCP_CHANNEL 1
CMIS_USENAMEFILE TRUE
NSERVERFILE /usr/1353sh/conf/NameServerFile
NAPP_UFDFILE_PATH /usr/1353sh/data/ufd
NE name
USER_LABEL_LENGTH 32
SH_SYNCHRO_TIMER_DURATION 10
# path of the MibAuditDiagnosis file
MAD_PATH /usr/1353sh/data/mad
# extension of the MibAuditDiagnosis file
MAD_EXT .mad
# UserLabel_maxLength
LOCATION_NAME_LENGTH
#Access Control Domain
SEC_ACD_ACTIVATE True
NE location name
32
Access Control Domain validation
RESYNCHRO_AFTER_RESTART_FROM_CRASH
True
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V

354
339 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V
354
340 / 354

APPENDIX C : EXAMPLE OF A PARAM.CFG FILE FOR PERFSTORAGE.

EXECUTABLE ( perfstorage ) {
traceConfiguration
/usr/1353sh/eml/perf/conf/trace.cfg
maxTrace 2000000
} maximal size of the <filename>.trace
traceUpdatePeriod 300 #in seconds
# extension for config files
PERF_CONFIG_EXT .pmcfg
} one file / NE
# port number for perf storage

PERF_PORTNUMBER 11111
} TCP port identification
# path for the Perf files

PERF_PATH /usr/1353sh/data/perf
# history lines for perf config file the tabs are mandatory!
} data preservation time
PERF_HISTORY HI:\t15 minutes\t1\thour\t24\nHI:\tday\t1\tmonth\t1
#allow the perf collect after restart by default
PERF_FORCED_COLLECT_AT_START True
# location of scripts to process the files
PERF_PM_CONFIG
/usr/1353sh/pm/perfvisu/lib/pm_config pm pmpmpm # + config file
PERF_PM_STORE
/usr/1353sh/pm/perfvisu/lib/pm_store pm pmpmpm # + data file
OFFLINE_PERF_PATH /usr/1353sh/data/perf/save
# child process lifetime (in case of pb with Oracle, for instance)
PERF_PROCESS_LIFETIME 2
# in minutes
PERF_SCRIPTS_PATH
AX_SEND_MSG
/usr/1353sh/eml/perf/script
/usr/1353sh/script/axSendMsg
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V

354
341 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V
354
342 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10

APPENDIX D : EXAMPLE OF A FAILURE_HANDLER.CFG FILE.

MAX_FAILURE: 3
CAPTURE_DELAY: 20
PNMUSM_CORE: YES
EMLUSM_CORE: YES
TRACE_FILES: YES
DATAFLOW_FILES: YES
PERSISTANT_FILES: YES
LOG_FILES: YES
ERR_FILES: YES
OUT_FILES: YES
PROCESSES: YES
to retrieve these file types or not
LOCATION: NMU
CUSTOMER_REF: xxxx
ORGANISATION: Alcatel Telecom
used for the header file
ED
01
957.130.932 V

354
343 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V
354
344 / 354

APPENDIX E : EXAMPLE OF A TRACE.CFG FILE.

SYSTEMLOG_OUTPUT
{
ALL
/usr/1353sh/maintenance/log/emlusmsh31.log
}
TRACE_OUTPUT
{
ALL
}
/usr/1353sh/maintenance/trace/emlusmsh31.trace
} destination of .log files
} destination of .trace files
DATAFLOW_OUTPUT
{
ALL
/usr/1353sh/maintenance/trace/emlusmsh31.dataflow } destination of .dataflow files
}
TRACE_FILTERS
{
ALL
{
ALL 1 2 5
} trace level selection
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V

354
345 / 354
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
957.130.932 V
354
346 / 354

APPENDIX F : EXAMPLE OF AN CLEANUP.CFG FILE.

#
#
cleanup.cfg
#
# configuration file for axcleanup
The file contains some records, in each record a name, a title ...etc. are listed. See an example below.
{name_
=> SenPerf,
title_
=> sen_performance_files,
impl_
=> CleanupSenPerf,
guiAccessible_ => 1,
fileGlob_ => $axcommon::OSCOREDIR/shared_data/***_*,
cronPeriod_ => 0 0 * * *,
cronCommand_ => /usr/1353sh/script/axcleanup oldonly local dt SenPerf,
parameters_ => {SenPerfMaxDay15m => 3,
SenPerfMaxDay24h => 7
}
In particular the info for the cleanup of SEN performance file as reported in the example are:
a)
periodicity of the cron
where cronPeriod parameter are:
b)
command
c)
minute hour monthday month weekday
cronCommand_ => /usr/1353sh/script/axcleanup oldonly local dt SenPerf,
parameters
parameters_ => {SenPerfMaxDay15m => 3,

SenPerfMaxDay24h => 7
where SenPerfMaxDay15m => 3 defines the max duration of a SEN perf file (15 minute) and
SenPerfMaxDay15m => 3 defines the max duration of a SEN perf file (24 hours)
1AA 00014 0004 (9007) A4 ALICE 04.10
In this file is described also the behaviour for the cleanup of Failure directory which record could be the
following:
ED
01
957.130.932 V

354
347 / 354

{name_
=> Failure,
title_
=> failure_directories,
impl_
=> CleanupFailure,
guiAccessible_ => 1,
fileGlob_ => $axcommon::OSCOREDIR/maintenance/failure/*/*,
cronCommand_ => /usr/1353sh/script/axcleanup oldonly local dt Failure,
parameters => {FailureMaxDay => 30}
1AA 00014 0004 (9007) A4 ALICE 04.10
},
ED
01
957.130.932 V

354
348 / 354

APPENDIX G : NTP CONFIGURATION EXAMPLES.

The cases hereafter included refer to the following network configurations:
a)
SH No external reference clock source available
b)
SH External reference clock source available
c)
Resilient SH No external reference clock source available
d)
Resilient SH External reference clock source available
e)
Cohosted resilient RM/SH No external reference clock source available
f)
Cohosted resilient RM/SH External reference clock source available
The attached figures highligth the content of the /etc/ntp.conf file, as for the server statement. For a
complete description of NTP parameters, please refer to the Network Time Protocol chapter in the present
guide.
As a general recommendation, the NTP configuration for the hosts acting as spare timeservers shall
include at least two NTP servers at the higher level which these hosts shall refer to. It is common practice
to declare the local clock as the secondary NTP source for the host itself, in order to allow the relevant
NTP clients to be synchronized by that host (Spare NTP server at that hierarchical level) when they can
not get the reference time from the designated Master NTP server according to the network architecture.In
particular, that should be the practise for both SH and RM/SH resilient architectures
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
ED
SH No external reference clock source available
01
957.130.932 V

354
349 / 354

Figure 226. No external reference clock

b)
SH External reference clock source available
1AA 00014 0004 (9007) A4 ALICE 04.10
With respect to the case a), the NTP configuration of the Master SH shall replace in the server statement
the IP address of the Master RM with the IP address of the external reference clock source.
ED
01
957.130.932 V

354
350 / 354
Resilient SH No external reference clock source available

c)
Figure 227. No external clock source in Resilient configuration

d)
Resilient SH External reference clock source available
With respect to the case c), the NTP configuration of the Master SH shall replace in the server statement
the IP address of the Master RM with the IP address of the external reference clock source.
1AA 00014 0004 (9007) A4 ALICE 04.10
e)
ED
Cohosted resilient RM/SH No external reference clock source available
01
957.130.932 V

354
351 / 354

Figure 228. Cohosted resilient RM/SH No external reference clock source available
f)
Cohosted resilient RM/SH External reference clock source available
1AA 00014 0004 (9007) A4 ALICE 04.10
With respect to the case e), the NTP configuration of the Master RM/SH shall include a new server
statement referring to the IP address of the external reference clock source (higher priority). The local
clock shall then be the spare NTP server (lower priority).
ED
01
957.130.932 V

354
352 / 354
INDEX

A
Add Operator, 93
Address Configuration, 218
Administrator, Services offered, 26
ANTP, 287
Application startup, Workstations, 165
Application stop, Workstations, 169
AxConfig file example, 333, 337, 341, 343, 345,
347, 349
B
Backup Operations, 135
Backup software, 45, 47, 129
Backup Tree, 131
C
Change ASAP, 214
Change Assigned To Observed, 221
Change Password, 96
Cleanup, 122
Configuration file, 26
D
Diagnostic of audit of the MIB, 187
Display SEN MIB, 190
E
Enable RPS Switch, 198
F
Forced Logout, 87, 240, 244, 245
1AA 00014 0004 (9007) A4 ALICE 04.10
General Process
Failure of, 172
Monitoring of, 175
GPS, 287
ED
H
HPOV Failure, 181
L
LAPD Configuration, 211, 223
List Current Login, 89
List Operators, 92
List Successful Login, 91
List Unsuccessful Login, 90
Local Data Management, 183
M
Maintenance, 291
Corrective, 295, 303, 305, 309, 313, 320
Preventive, 291
Management, Of workstations, 145
Monitoring
the General processes, 175
the Presentation processes, 175
the System, 175
the Workstation applications, 175
N
NECTAS comparison, 194
NECTAS Decoding, 191
Network Interface card, 151
Non Vital Process, 27
O
Overhead Byte Configuration, 208
P
Periodic Actions , 239
Ping NE, 230
PostOperations, 142
Powerup, Workstation, 43
Presentation Process, Monitoring of, 175
Process Configuration, 156
01
957.130.932 V

354
353 / 354
Process Monitoring, 161

Processes
General process, 26
Monitoring process, 26
Non Vital, 27
Presentation process, 26
Vital, 27
Presentation processes, 166

System, 165
Workstation applications, 165
Stop
General processes, 170
Presentation process, 170
System, 168
Workstation applications, 169
System
StartUp, 165
Stop, 168
System Management, 145
R
Remove Operator, 95
Restart Perf Collect, 207, 216
Restore Operations, 138
Restore software, 129
U
Upload Failure Diagnosis, 197
User Profile, 93
S
Save TP, 206
SDH Manager, AxConfig file example, 333, 337,
341, 343, 345, 347, 349
Shutdown, Workstation, 43
SMF/Command/Event Logs Management/Visualization, 99
Software
Backup, 45, 47, 129
Restore, 129
Software Download Manager Configuration, 199
Software Download Server Configuration, 201
Stack Configuration, 147
StartUp
General processes, 166
V
Vital Process, 27
W
Workstation
Application Startup, 165
Application Stop, 169
Powerup, 43
Shutdown, 43
Workstation Distribution, 129
1AA 00014 0004 (9007) A4 ALICE 04.10
END OF DOCUMENT
ED
01
957.130.932 V

354
354 / 354

1353sh Administracion

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

1353sh Administracion

Загружено:

Авторское право:

Доступные форматы

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

V Ed.01 3AL 71807 AAAA Ed.01

No PAGINE TOTALI PER ARCHIVIAZIONE: 360

INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS

STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING

COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES:

TOTALE FOGLI A4 TOTAL A4 SHEETS:

WARNING FOR A-UNITS OTHER THAN A-ITALY

1AA 00014 0004 (9007) A4 ALICE 04.10

Labels are done according to A-Italy binder format.

3AL 71807 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

1353SH 5.3 ADMINISTRATION GUIDE

ORIGINALE SU FILE: ALICE 6.10

1AA 00014 0004 (9007) A4 ALICE 04.10

Element Manager for SDH and Optical Networks

3AL 71807 AAAA TQZZA

All rights reserved. Passing on and copying of this

3AL 71807 AAAA Ed.01

3AL 71807 AAAA Ed.01

3AL 71807 AAAA Ed.01

Element Manager for SDH and Optical Networks

1300NM 1353SH Rel.5.3

1AA 00014 0004 (9007) A4 ALICE 04.10

3AL 71807 AAAA Ed.01

3AL 71807 AAAA TQZZA

1AA 00014 0004 (9007) A4 ALICE 04.10

FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT

3AL 71807 AAAA TQZZA

3AL 71807 AAAA Ed.01

3AL 71807 AAAA Ed.01

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

1353 SH REL.5.3 ADMINISTRATION GUIDE

4 WORKSTATION SHUTDOWN OR POWERUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3AL 71807 AAAA TQZZA

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

6 DISKS FULL BACKUP AND FULL RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8 SYSTEM TRACE & LOG MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3AL 71807 AAAA TQZZA

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

11 LOCAL DATA MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3AL 71807 AAAA TQZZA

14 REMOTE MAINTENANCE IN SH5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

11.9 Software download manager configuration Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3AL 71807 AAAA TQZZA

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

14.2.1 Creating a new generic connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15 NETWORK TIME PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16 ALCATEL NETWORK TIME PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX A : EXAMPLE OF AN AXCONFIG FILE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX B : EXAMPLE OF A PARAM.CFG FILE FOR AN EMLIM. . . . . . . . . . . . . . . . . . . . . . .