1353NM Rel.7.0 Administration Guide PDF

Administration Guide
Alcatel 1350NM
Network Management
1353NM Rel.7.0
Element Management application for Alcatel Optical and
Radio transport networks
Version 7.0
3AL 89061 BAAA Ed.01

1353NM REL.7.0 ADMINISTRATION GUIDE
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
REFERENCED DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
GLOSSARY / TERMINOLOGY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2 Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.3 Product-release handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.3.1 Handbooks related to the specific software application . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.3.2 Handbooks related to the Network Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.3.3 Documentation on CD–ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3.4 Handbooks related to the product’s hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.4 Purpose of the Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.5 Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.6 Document Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2 GENERALITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.1 1353NM 7.0 news Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.2 1353NM activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.3 Role of the Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3 RELEASE IDENTIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4 WORKSTATION SHUTDOWN OR POWERUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5 CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.1 Preparing 1353NM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.2 1353NM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.2.1 Configure the 1353NM SubSystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.2.2 Retixt Stack Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.2.3 Configuring the 1353NM Element Manager Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
01 040416 M.BERTONI M.ARMANINI
01A 040128 M.BERTONI M.ARMANINI
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

1AA 00014 0004 (9007) A4 – ALICE 04.10
1353NM REL.7.0
ADMINISTRATION GUIDE
ED 01
3AL 89061 BA AA 1 / 280
280
5.2.4 Execute the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.3 1353NM Master and Client Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.4 Process Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.4.1 Group Level concept applied in PMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.4.2 Functional States defined in PMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.4.3 Colour usage in PMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.4.4 Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.4.5 Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.4.6 System Defence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.4.7 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6 MAINTENANCE GENERALITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7 DISKS FULL BACKUP AND FULL RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8 USER MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.1 SEC Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.1.1 The access control model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.1.2 OADs and FADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
8.1.3 Default User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.1.4 Customizing User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8.1.5 An example of management of OAD, FAD, and OAD–FAD . . . . . . . . . . . . . . . . . . . . . . . 65
8.1.6 Creating new Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
8.2 Session Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
8.3 Broadcast Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
8.4 Show Good Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
8.5 Show Bad Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
8.6 Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
8.7 Unlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
8.8 Forced Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
8.9 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
8.9.1 Global Operators Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
8.9.2 Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
8.9.3 Set Max Users Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
8.9.4 SMF Operators Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
8.10 Set Personal Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
9 SYSTEM LOG MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

9.1 SMF/Command/Event Logs Management/Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
9.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
9.1.2 Management of log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
9.1.3 Access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
9.1.4 Log Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
9.1.5 SMF Logs Management (User Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
9.1.6 Command Log Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
9.1.7 Printing the selected record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
9.2 Failure Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
9.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
9.2.2 Fault Report Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
9.2.3 Sequence of events when a process exits abnormally . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
9.2.4 Failure Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
1AA 00014 0004 (9007) A4 – ALICE 04.10
9.2.5 Failure Management (User Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

9.3 Trace Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9.3.1 Traces Management tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9.3.2 Trace Management (User Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
ED 01
3AL 89061 BA AA 2 / 280
280
9.3.3 PMC Trace and Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
9.4 Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.4.2 Cleanup tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.4.3 Cleanup (User Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

9.4.4 Cron actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
10 BACKUP/RESTORE FEATURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

10.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
10.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
10.2 Backup/Restore (User interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
10.2.1 Access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
10.2.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
10.3 Backup Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
10.3.1 Backup job creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
10.4 Restore Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
10.4.1 Load Backup to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
10.4.2 Selected backup Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
11 SYSTEM DATA MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

11.1 Access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
11.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
11.2.1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
11.2.2 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
11.2.3 User Interface parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
11.3 Data Mangement – Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
11.3.1 Diagnosis of audit of the MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
11.3.2 Display SEN MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
11.3.3 Upload Failure Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
11.3.4 Enable RPS Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
11.3.5 Overhead byte Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
11.3.6 LAPD Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
11.3.7 Change ASAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
11.3.8 Sync Source Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
11.3.9 Address Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
11.3.10 Change Assigned To Observed and Change Free or Observed To Assigned . . . . . 176
11.3.11 Switch Old/New Practice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
11.4 Performance Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
11.4.1 Save TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
11.4.2 Restart Perf Collect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
11.5 NECTAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
11.5.1 NECTAS Decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
11.5.2 NECTAS Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
11.6 EQUIPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
11.6.1 Set offline board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
11.6.2 Upgrade Offline Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
11.6.3 Set offline signal label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
11.7 NE Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
11.7.1 SW Package Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
11.7.2 List Gateway NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
11.8 Ping NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
1AA 00014 0004 (9007) A4 – ALICE 04.10
11.8.1 IP Tunneling configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

11.8.2 On Board Simulator Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
11.9 DXC TCP–IP Address Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
ED 01
3AL 89061 BA AA 3 / 280
280
12 PERIODIC ACTIONS (SMF SCHEDULER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
12.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
12.1.1 Access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
12.2 Scheduler plan creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

12.3 Scheduler plan edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

12.4 Scheduler plan validate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
12.5 Scheduler plan stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
12.6 Scheduler plan delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
13 SMF FOR DXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
14 NETWORK TIME PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

14.1 NTP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
14.1.1 NTP implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
14.1.2 Stratum Level and Time Server Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
14.1.3 NTP daemon and configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
14.1.4 The driftfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
14.1.5 Other options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
14.1.6 Synchronization schemes and reference principles in OS Configuration . . . . . . . . . . . 219
14.2 Synchronize the clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
14.2.1 Configure host_b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
14.2.2 Configure host_a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
14.2.3 Initial Clock Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
15 ALCATEL NETWORK TIME PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

15.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
15.1.1 ANTP behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
15.1.2 RTC distribution system architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
16 PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
16.1 Preventive Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
16.2 Corrective Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
16.3 Failure management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
16.4 Maintenance operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
16.5 Upload failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
16.6 Advanced network management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
16.7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 4 / 280
280
LIST OF FIGURES AND TABLES
FIGURES
Figure 1. Alcatel CDE Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Figure 2. TMN OS application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Figure 3. Example of typed unix shell commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 4. Example of the system response to the command date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 5. System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 6. 1353NM System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 7. 1353NM Warning Security Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 8. Alcatel CDE Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 9. TMN–OS Management Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 10. 1353NM System configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 11. 1353NM Parameter Definition – Sh_SubSystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 12. 1353NM Parameter Definition – System_Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 13. 1353NM PMDS_DB_SubSystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 14. 1353NM Parameter Definition –Q B3S_Simulator Set–up . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 15. 1353NM Necom SubSsytem Configuration 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 16. 1353NM Necom SubSystem 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 17. 1353NM Necom SubSystem 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 18. 1353NM Antp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 19. 1353NM FTServer and FTclient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 20. 1353NM Wrong Element manager identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 21. 1353NM Element Manager – Retix Stack assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 22. 1353NM Configuration Warnings Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 23. 1353NM Configuration Error and Warnings window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 24. 1353NM Configuration quit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 25. Process Monitoring Control Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 26. NM Instance selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 27. PMC : Stop selected item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 28. PMC : Activate Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 29. TMN OS SEC Administration activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 30. System Mangement Menu to access SEC Administration . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 31. System Mangement Menu to access SEC Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 32. SEC USM Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 33. Object creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 34. Elementary OAD creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Figure 35. Create/Modify a new Application FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 36. Application FAD for user viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 37. OAD–FAD Combination creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Figure 38. Default Access Rights Definition for operator axadmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 39. Modify the NE ACD value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 40. Access Rights Definition of test with the OAD–FAD test_oadfad . . . . . . . . . . . . . . . . . . . . 68
Figure 41. ACD creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 42. Create a new Function Access Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 43. Create a new SysFad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 44. Create a new OAD–FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 45. Create a new profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 46. Profiles in SMF–Create User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Figure 47. Session Management activation from TMN OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 48. Session Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Figure 49. Broadcast Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 50. Show Good Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
ED 01
3AL 89061 BA AA 5 / 280
280
Figure 51. Show Bad Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 52. Lock a workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 53. Unlock a workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 54. Forced Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Figure 55. Activating User Management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Figure 56. Global Operators Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 57. Create user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 58. Delete User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 59. Change password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 60. Set max users number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 61. Activating SMF User Management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Figure 62. SMF Operators Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 63. SMF Create user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 64. SMF Delete User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 65. Set Default Printer window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 66. System Log Management activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Figure 67. Logs states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Figure 68. Logs Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Figure 69. Log Management : Log File Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Figure 70. SMF Log Management : Log File Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 71. SMF Log Management : Delete Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 72. Log record filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 73. Starting CLV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 74. Starting CLV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Figure 75. Select Target Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Figure 76. Simple Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Figure 77. Advanced Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 78. Selecting the subject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 79. Selecting the relational operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Figure 80. Selecting a value of comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Figure 81. Combining Logical Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Figure 82. Temporary Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Figure 83. Selected Saved Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Figure 84. Extraction result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Figure 85. Extraction result list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Figure 86. Extraction result list’s statistic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Figure 87. Detail information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Figure 88. Print dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Figure 89. Print preview window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 90. Export the selected command result list to text file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 91. Export of the selected command record detailed info to text . . . . . . . . . . . . . . . . . . . . . . . 122
Figure 92. Display online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Figure 93. Exit CLV confirmation dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Figure 94. Failure Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Figure 95. Snapshot Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 96. System Trace Management selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 97. SMF Trace File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Figure 98. SMF Edit Trace Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 99. Trace and Log files selection from PMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Figure 100. Agent Trace and Log files list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 101. Trace file from PMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Figure 102. Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Figure 103. Cleanup – Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 104. Cleanup – Clean – Error: No Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
ED 01
3AL 89061 BA AA 6 / 280
280
Figure 105. Cleanup – Clean – Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Figure 106. Backup/Restore window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Figure 107. Backup job creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Figure 108. Restore window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 109. Load Backups Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Figure 110. Warning window for exclusive data type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Figure 111. System Management Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Figure 112. Common interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Figure 113. System Management selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 114. System Management Tools selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 115. Diagnosis of audit of the MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 116. MIBs differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 117. Pull–down menus of the MIBs differences window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 118. Find dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 119. Searching occurences in the MIBs differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Figure 120. Display SEN MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Figure 121. SEN MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Figure 122. Upload Diagnosis Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Figure 123. Upload Diagnosis Failure – Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Figure 124. Enable RPS Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 125. Enable RPS Switch – Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 126. Overhead byte configuration option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 127. Overhead byte configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Figure 128. LAPD configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Figure 129. LAPD configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Figure 130. System Management Tools selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Figure 131. Change ASAP window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 132. Change ASAP window – NE source selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 133. Change ASAP window – Getting ASAP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 134. Change ASAP window – Work in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 135. Sync Source Selection – Choosing a NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Figure 136. Sync Source Selection – Selecting the synchronization source . . . . . . . . . . . . . . . . . . . 171
Figure 137. Sync Source Selection – Choosing the SSU quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Figure 138. Address Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Figure 139. Address Configuration – NE source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Figure 140. Address Configuration – Initialisation on going . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Figure 141. Address Configuration – Addresses setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Figure 142. Change assigned to observed window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Figure 143. Change state operation running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Figure 144. Switch Old/New Practice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Figure 145. Switch Old/New Practice confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Figure 146. Save TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Figure 147. Restart Perf Collect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Figure 148. Restart Perf Collect – Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Figure 149. NECTAS functions selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Figure 150. NECTAS Decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Figure 151. NECTAS Decoding – Show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Figure 152. NECTAS Decoding – Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Figure 153. NECTAS Comparison (first NE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Figure 154. NECTAS Comparison (second NE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 155. NECTAS Comparison – Result (no differences) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Figure 156. NECTAS Comparison – Differences displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Figure 157. NECTAS Comparison – File saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Figure 158. System Management – Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
ED 01
3AL 89061 BA AA 7 / 280
280
Figure 159. Set Offline Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Figure 160. Upgrade Offline Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Figure 161. Set Offline Signal Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Figure 162. System Management – NE Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Figure 163. SDH software package panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Figure 164. SERV. SPEC. panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Figure 165. Successful creation OMSN package window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Figure 166. OMSN package panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Figure 167. OMSN package panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Figure 168. Remove Service–Specific package panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Figure 169. Discard package panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Figure 170. List Gateway NE Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Figure 171. NE Administration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Figure 172. Ping NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Figure 173. IP Tunneling function selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Figure 174. IP Tunnel Configuration Application window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Figure 175. Create IP Tunnel window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Figure 176. IP tunnel successful creation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Figure 177. IP Tunnel List window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Figure 178. IP Tunnel Detail window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Figure 179. Delete IP Tunnel window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Figure 180. On Board Simulator Monitoring window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 183. 1641SX TCP–IP Address Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Figure 184. SMF Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Figure 185. SMF Scheduler : Create New Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Figure 186. NTP synchronization network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Figure 187. NTP Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Figure 188. ANTP system architecture with co–located ANTP servers . . . . . . . . . . . . . . . . . . . . . . . . 230
Figure 189. ANTP system architecture with not co–located ANTP servers . . . . . . . . . . . . . . . . . . . . 230
TABLES
Table 1. Default operators in 1353SH5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 2. Log Management: Access rights for different User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Table 3. Log Management Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Table 4. Trace Management: tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Table 5. Trace Management: Trace levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Table 6. Backup&Restore: Access rights for different User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Table 7. Backup&Restore: Tools description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Table 8. Local data management: access right for different User Profiles . . . . . . . . . . . . . . . . . . . . . 152
Table 9. Periodic Options: Access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 8 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
ED
01A
01
HISTORY
DATE
Feb 2004
April 2004
Creation and released version
First archived version of the handbook

DESCRIPTION
280
3AL 89061 BA AA
9 / 280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
[2]
[1]
01
RFC 1305
For internal use only.
3AL 89061 AAAA

Operator’s Handbook Rel 7.0:
REFERENCED DOCUMENTS
Network Time Protocol March 1992
280
3AL 89061 BA AA
10 / 280
GLOSSARY / TERMINOLOGY
ACA: Access Control Administration tool

ACD: Access Control Domain
ADM: Add and Drop Multiplexer

AIS: Alarm Indication Signal

ALMAP: Alcatel Management Application Platform
ALS: Automatic Laser Shutdown
APS: Automatic Protection Switching
ASAP: Alarm Severity Assignment Profile
AU: Administrative Unit
AU PJC Administrative Unit Pointer Justification Counter
BER: Bit Error Rate
CD–ROM: Compact Disc Read Only Memory
CCITT: Telegraph and Telephone International Consultative Committee
CLNS: ConnectionLess Network Service
CLNP: ConnectionLess Network Protocol
CT: Craft Terminal
DCC: Data Communication Channel
DCN: Data Communications Network
DWDM: Dense Wavelenght Division Multiplexing
DS: Degraded Signal
ECC: Embedded Communication Channels
EML: Element Management Layer
EPS: Equipment Protection Switching
FAD: Functional Access Domain
FERF: Far End Received Failure
FLS: Frame Loss Second
Gbit/s: Gigabits per second
GNE: Gateway Network Element
HMI: Human Machine Interface
HOA: High Order Assembler
HO Matrix: High Order Matrix
HPA: High Order Path Adaptation
HPC: High Order Path Connection
HPT: High Order Path Termination
HP: Hewlett Packard
HP–OV: Hewlett Packard OpenView
HP–OVW: Hewlett Packard OpenView Windows
HP–UX: Hewlett Packard Unix
HP–VUE: Hewlett Packard Visual User Environment
HVC: Higher Order Virtual Container
IEEE: Institute of Electrical and Electronics Engineers
IM: Information Manager
Kbit/s: Kilobits per second
LAN: Local Area Network
LAPD: Link Access Procedures Direct (protocol)
LOF: Loss Of Frame
LO Matrix: Low Order Matrix
LOP: Loss Of Pointer
1AA 00014 0004 (9007) A4 – ALICE 04.10
LOS: Loss Of Signal

LOT: Loss Of Tributary
LPA: Lower Order Path Adaptation
LPC: Lower Order Path Connection
ED 01
3AL 89061 BA AA 11 / 280
280
LPT: Lower Order Path Termination
LVC: Lower Order Virtual Container
MAC: Media Access Control
Mbit/s: Megabits per seconds

MIB: Management Information Base

MS: Multiplex Section
MSP: Multiplex Section Protection
MST: Multiplex Section Termination
NAD: Network Access Domain
NAP: Network Access Point
NE: Network Element
NML: Network Management Layer
NSAP: Network Service Access Point
NTP: NetworkTime Protocol
OAD: Object Access Domain
OFS: Out of Frame Seconds
OMSG: Optical Multiservices Gate
OMSG: Optical Multiservices Node
OS: Operation System
PDH: Plesiochronous Digital Hierarchy
PI: Physical Interface
PPI: PDH Physical Interface
PTM: Path Trace Mismatch
RS: Regenerator Section
RST: Regenerator Section Termination
SA: Section Adaptation
SCSI: Small Computer Serial Interface
SDH: Synchronous Digital Hierarchy
SF: Signal Failure
SPI: SDH Physical Interface
STM–N: Synchronous Transport Module level N (N is an integer = 1,4 or 16)
TF: Transmit Fail
TMN: Telecommunications Management Network
TN: Telecommunications Network
TP: Termination Point
TU: Tributary Unit
TU PJC: Tributary Unit Pointer Justification Counter
USM: User Service Manager
VC: Virtual Container
XC: Cross–Connect
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 12 / 280
280
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 spe-
cial, 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, repro-
duced or disclosed to a third party without written consent.
1.2 Handbook applicability
This handbook applies to the following product-releases:
PRODUCT ANV P/N

1353NM 3AL 89052 AAAA
PRODUCT RELEASE VERSION (N.B.) ANV P/N

1353NM 7.0 7.0 3AL 89053 AAAA
N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

Handbooks relevant to software applications (typically the Operator’s Handbooks) are not mod-
ified unless the new software ”version” distributed to Customers implies man–machine interface
changes or in case of slight modifications not affecting the understanding of the explained pro-
cedures.
Moreover, should the screen prints included in the handbook contain the product-release’s ”ver-
sion” marking, they are not replaced in the handbooks related to a subsequent version, if the
screen contents are unchanged.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 13 / 280
280
1.3 Product-release handbooks
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-re-
lease-version is stated in para.1.2 on page 13 consists of the following handbooks:
1.3.1 Handbooks related to the specific software application
THIS
REF HANDBOOK ANV Part No.
HANDBOOK
1353NM Rel.7.0
[1] 3AL 89061 AAAA
Operator’s Handbook
1353NM Rel.7.0
[2] 3AL 89061 BAAA
Administration Guide
1.3.2 Handbooks related to the Network Release
THIS
REF HANDBOOK ANV Part No.
HANDBOOK
1350NMRel.7.0
[3] 3AL 88888 AAAA
Installation Guide
1350NM 7.0 System Management

[4] 3AL 88874 AAAA
[5] PMDS 1.1 User’s Guide 3AL 88875 AAAA
1330AS 6.5
[6] 3AL 88876 AAAA
ELB 2.X
[7] 3AL 88877 AAAA
[8] 1353NM NE LIST Handbook 3AL 89063 AAAA
1353NM NR5 Equipment Specific

[9] 3AL 89062 AAAA
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 14 / 280
280
1.3.3 Documentation on CD–ROM
REF CD–ROM TITLE ANV Part No.

1353NM Rel.7.0 CD–ROM–DOC EN 3AL 89059 AAAA

[10]
Contains, in electronic format, the following handbooks: REF.[1], REF.[2] and REF.[4] to [9].
Envisaged after the release of the handbooks.
1.3.4 Handbooks related to the product’s hardware
Refer to WS supplier handbooks.
In particular refer to such handbooks to obtain the following information (where applicable):
– COMPLIANCE WITH EUROPEAN NORMS

– SAFETY RULES
• General rules
• Harmful optical signals
• Risk of explosion
• Moving mechanical parts
• Heat–radiating Mechanical Parts
– ELECTROMAGNETIC COMPATIBILITY
– ELECTROSTATIC DISCHARGERS (ESD)
– EQUIPMENT LABELS
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 15 / 280
280
1.4 Purpose of the Document
This document aims to describe all tools and procedures the System Administrator is provided with in order
to manage the resources of the 1353NM system itself.

1.5 Target Audience
This document is intended to 1353NM Administrators.
The documents that should be read before starting this document is:
– Getting Started Manual, see [1].
It is recommended to have some knowledge of NM underlying principles.
This document does not replace a training on 1353NM administration.
1.6 Document Description
This document is divided into two parts:
Part 1: Services provided to the operator by the SMF (System Management Features) Interface.
– Chapter 2: Generalities. The 1353NM processes are briefly described and management services
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 launching/stopping the 1353NM product are described here.
– Chapter 4: Workstation Shutdown Or Powerup.
The operations necessary for stopping/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: Disks Full Backup And Restore. The operations needed to backup and restore all disks
of a workstation are described here (through a reference to the 1353NM Installation Guide).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 16 / 280
280
– Chapter 7: Operators Administration. All facilities available for the system users management are
described here.
• SEC Administration by ACA

• Restart Security Services

• Forced Logout
• List Current Login
• List Unsuccesful Login
• List Succesful Login
• List Operators
• Add Operator
• Remove Operator
• Change Password
• Set Max Operator Number
• Set Personal Printer.
– Chapter 8: System Trace & Log Management. Tools to control logs, to track failure and to control
traces are described.
• SMF/Command/Event Logs Management/Visualization

• Failure Management
• Trace Management/Visualization
• Cleanup
– Chapter 9: Backup/Restore Feature. The operations necessary to backup and restore the1353NM
data are described here.
• Backup Operations
• Restore Operations
– Chapter 10: System Management. The operations requested for configuring , launching and stop-
ping the 1353NM product are described here.
• System Configuration
• Process Monitoring
– Chapter 11: Local Data Management. Tools for NEs management are described.
• Diagnosis of audit of the MIB (Qb3* NEs only).

• Display SEN MIB (Qb3* NEs only)
• NECTAS Decoding (Qb3* NEs only)
• NECTAS Comparison (Qb3* NEs only)
• Upload Failure Diagnosis (Qb3* NEs only)
• Enable RPS Switch (Qb3* NEs only)
• Software download manager configuration (Qb3* NEs only)
• Software download server configuration
• OMSN SWP Merging Tool
• Save TP (Qb3* NEs only)
• Restart Perf Collect (Qb3* NEs only)
• Overhead byte Configuration (Qb3* NEs only)
• LAPD Configuration (Qb3* NEs only)
• Change ASAP (Qb3* NEs only)
1AA 00014 0004 (9007) A4 – ALICE 04.10
• Sync Source Selection (Qb3* NEs only)

• Address Configuration (Qb3* NEs only)
• Change Assigned To Observed and Change Free or Observed To Assigned (Qb3* NEs only)
ED 01
3AL 89061 BA AA 17 / 280
280
• Switch Old/New Practice (Qb3* NEs only)
• Set offline Board
• Upgrade Offline Board
• Set offline SignalLabel

•

Ping NE

• List Gateway NEs
• DXC TCP/IP address configuration
• Change User Label format (Q3 NEs only).
– Chapter 12: Periodic Actions. Here is described how to manage periodic actions.
• Add a scheduled action

• View scheduled actions
• Remove a scheduled action.
– Chapter 13: SMF for DXC NEs management.
– Chapter 14: Network Time protocol. How to create or modify the NTP daemon configuration files is
described.
• NTP configuration.
– Chapter 15: Alcatel Network Time protocol. It describes how to configure ANTP features.
• ANTP configuration.
Part 2: Procedure sheets.
– Chapter 16: Procedures.
• Preventive maintenance
• Corrective maintenance
• Failure management
• Maintenance operations
• Upload failure
• Advanced network management
• Troubleshooting.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 18 / 280
280
2 GENERALITIES
2.1 1353NM 7.0 news Overview

1353NM 7.0 is a version that signs a turning point in the system architecture. A common platform for NM
Systems has been identified that collects common components and applications. OS–Kernel, this is the
name of the common platform, idea derives from the observation that so far each NM Product needs to
be installed on a dedicated physical machine. This constraint brings to a waste of disk space and machine
resources and may result in an uncomfortable working environment for operators that has to operate on
different NM Systems at the same time.
Another incentive to the development of the OS–Kernel comes from observing the growing size of the
servers and workstations. The machines become very big and consequently expensive, so it is necessary
to optimize their utilization in order to obtain a good ratio between the hardware bought and the systems
installed.
The aim of the OS–Kernel is to provide a common building block of the Network Management architecture.
On the other side the NM Products (1353SH, 1354RM, 1353SN, ...) will be split in components and applica-
tions, so the final result is that a product is a collection of components and applications. On this common
block the NM Products will be assembled fitting the applications and components needed on the OS–Ker-
nel platform.
Up till now difficulties must be faced when installing different product instances (typically NM OS) on the
same workstation (co–hosting).
Common resources used by OS applications are duplicated , conflicts may rise due to different require-
ments for the application customization, etc.
The modularity offered by OS–Kernel permits to install on a hardware platform a single product or several
different products, as well as different instances of the same product.
OS–Kernel offers a set of functionalities about:

– ·Process Management
– ·System Configuration
– ·Installation/Integration & Customization
– ·System Management Function
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 19 / 280
280
2.2 1353NM activation
TMN OS is the graphical interface of OS–Kernel application dedicated to manage the different System
Instances built on the same hardware machine.

TMN OS application is the box containing and managing all the NM Systems customized on a single physi-
cal machine.
TMN OS Icon
Figure 1. Alcatel CDE Front Panel
Select TMN OS icon as shown in the previous figure to start TMN OS application. The TMN–OS Manage-
ment Window will be shown in a few seconds, you have to select the 1353NM instance you want to man-
age.
Figure 2. TMN OS application

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 20 / 280
280
2.3 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 pos-
sible in case of power supply failure for example,
• to avoid file system full occurence or hardware failures.
– perform corrective maintenance operations in case of:
• power supply failure,

• file system full,
• hardware failures (disk crash, SCSI errors),
• software failures (Panic UNIX, application bug).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 21 / 280
280
2.4 Document Conventions
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 pre-
ceded by the UNIX prompt.
– Variable names will be in the courier italic font. They will usually represent workstation host-
names 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 3. 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 4. Example of the system response to the command date.
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 sysad-
min group).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 22 / 280
280
3 RELEASE IDENTIFICATION
The System general information and System composition for 1353NM products is displayed selecting from
TMN–OS menu OS | ––> System Information or pressing the icon on the menu bar.
Figure 5. System Information
The following window will be displayed with all information about the selected System Instance.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 23 / 280
280
Figure 6. 1353NM System Information
Displayed Informations are :
– System : 1353NM OS System name

– Version : 1353NM OS Version
– Instance : Number of the OS Customized Instance
– Role : Role assigned to the OS Customized Instance (Master or Client)
– Master Ws : name of the master workstation
– Composition : lists all the components and applications belonging to the System with corresponding
versions.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Click on the Dismiss button to close this window.
ED 01
3AL 89061 BA AA 24 / 280
280
4 WORKSTATION SHUTDOWN OR POWERUP
The shutting down or the powerup of a workstation may be necessary if the attempt to relaunch some pro-
cesses failed.
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
• 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.
Operators that were logged on the workstation are logged out and have to log in again.
b) 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 :
– A power supply failure,

– A unix panic,
– A disk crash.
N.B. Warning : After a crash pay attention to messages indicating a disks corruption . If fsck is
required that means the integrity of the 1353NM application can not be assumed any lon-
ger. In such a case it is recommended to make a full system restore (see chapter 11).
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 25 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
280
3AL 89061 BA AA
26 / 280
5 CONFIGURATION
The installed Alcatel TMN System applications need to be configured in order to run properly. The configu-
ration consists in creating configuration files and databases. It is important to notice that the configuration
should be performed only on Master instances, the configuration is not required on client instances.
The following paragraphs describe how to configure the Master instance of 1353NM System.
5.1 Preparing 1353NM Configuration
Before starting 1353NM Configuration you have to configure all the LAN interface planned to be used by
Retixt Stack using HP “System Administration Manager” (SAM). For each LAN interface (including lan0)
you have to define an alias name that will be provided as “SUPERVISION_AREA” during 1353NM Confi-
guration, this information will be used to define the relationship between the Retixt Stack and the LAN
interface.
The alias name of the interface MUST BE different from the hostname. The suggested
name is: osilan<lan number>, where <lan numer> should be substituted with the lan log-
ical number. This method allows also to easy identify the lan card with Retixt Stack config-
ured.
When the lan interfaces have been configured by SAM application, you have to remove the unnecessary
reference to hostname added by SAM into the /etc/hosts (excluding the lan0) for new IP Address definition
line.
For example, if you configure the lan1 of hosta to address 192.200.200.21 with alias osilan1, SAM will add
the following new line in /etc/hosts:
192.200.200.21 hosta osilan1
You have to change it by removing the reference to hosta:

192.200.200.21 osilan1
Then save the modified /etc/hosts.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 27 / 280
280
5.2 1353NM Configuration
To be able to configure the 1353NM you have to login as a 1353NM OS Administrator, this authority is
predefined at customization time to “alcatel” user. So you have to login as “alcatel” user with CDE GUI,

and click on TMN–OS icon of the CDE Front Panel.

N.B. It is strongly raccomended avoiding the use of “axadmin” user to startup 1353NM sessions. The
OS Default Administrator to be used is “alcatel”, if needed, additional operators can be defined
by using SMF.
Figure 7. 1353NM Warning Security Box
Please ignore the “Security not activated” warning message, it will disappear after the configuration ex-
plained in this chapter.
TMN OS Icon
Figure 8. Alcatel CDE Front Panel
The TMN–OS Management Window will be shown in few seconds, you have to click on the 1353NM
instance you want to configure, highlighting it. To activate the System Configuration application use the
pulldown OS menu‘ (as shown in Figure 9. ) selecting “System Config”.
Figure 9. TMN–OS Management Window

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 28 / 280
280
5.2.1 Configure the 1353NM SubSystems
The 1353NM “System Configuration” window will be built and shown on the screen. Clicking on all the right
column items to include them in the configuration:
Arrow Button
Identifier Input Field
Figure 10. 1353NM System configuration window
N.B. Don’t select QB3S_Simulator item (see paragraph 5.2.1.1 at page 32 for more informations):
System Configuration is the generic way to configure processes in a System instance. The processes are
configured into groups. A group of processes is called entity. This grouping is meant to configure in a single
step processes that have the same configuration properties. The group definition is a System (NMS) confi-
guration property. Each NMA has a specific configuration file to configure its processes; this configuration
file contains specific data and parameters.
Process Configuration should allow configuring processes in the following way :
– Define a static list of processes that can belong to the System Instance;
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Define a variable list of processes that can have multiple instances inside the System Instance;
A configuration file can define the id category of the multiple instances off–line.
ED 01
3AL 89061 BA AA 29 / 280
280
The list of processes on the left contains the system processes that can have multiple instances. Pressing
the arrow button the process is put in the static list of processes on the right adding an instance number
to the process.

The static list on the right contains the processes that can’t have multiple instances and the processes

chosen from the list on the left and instanced.
The selected processes listed in the static list of processes will be system instance processes.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 30 / 280
280
Selecting “Sh_SubSystem” item the following window will be shown, select the correct value, then pull
down the “Action” menu and select “Apply & exit”.
Figure 11. 1353NM Parameter Definition – Sh_SubSystem
Selecting “System_Tuning” item the following window will be shown, leave the default values (100 and
30) then pull down the “Action” menu and select “Apply & exit”.
Figure 12. 1353NM Parameter Definition – System_Tuning
Selecting the “PMDS_DB_SubSystem” a communication window is open asking you to specify if you
want to create a new database or keep the old one. If you are installing for the first time choose “NEW”.
Figure 13. 1353NM PMDS_DB_SubSystem

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 31 / 280
280
5.2.1.1 Configure QB3S_Simulator SubSystem
You must execute this step only under Alcatel development supervision.

Selecting “QB3S_Simulator” item the following window will be shown, leave the default value (simulator)
then pull down the “Action” menu and select “Apply & exit”.
Figure 14. 1353NM Parameter Definition –Q B3S_Simulator Set–up

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 32 / 280
280
5.2.2 Retixt Stack Configuration
Each lan interface that is configured to be used as retix Retixt Stack has to be configured following this
paragraph instruction. First of all you have to create the four new items for the stack instance in the Sub-
System List column.

a) Select “Necom_SubSystem” on the “Instantiable SubSystem” Column.
b) Write the lan interface identification number in the “Identifier Input Field” (see Figure 10. at page 29).
c) Click on “Arrow Button” in the center of the window to create the new item.
Figure 15. 1353NM Necom SubSsytem Configuration 1
Then repeat the procedure for “Antp”, FTclient, and FTserver.

Click on the just created item “Necom_SubSystem_n”, the item color will change from gray to blue and
the following window will be displayed to allow the configuration of the Retix Stack parameters.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 33 / 280
280
Figure 16. 1353NM Necom SubSystem 2
Entering the data for the Retix you have to specify the LAN card identity in the “LAN_ID” selector menu,
by selecting the first LAN card you want to devote to Retix stack. NOTE: The specified lan MUST BE
CONFIGURED with an IP Address and described in the /etc/hosts file.
Then you have to specify the “SUPERVISION_AREA” by entering a symbolic name, this name will be used
as host alias that means it has to follow the host alias naming rules:
– No space and/or special character are allowed, except “_” .
– No more than eight character.
Enter in the “SYSTEM_ID”, “AFI”, “IDI”, “ORGANIZATION_ID”, “AREA”, “SEL” in agreement with the
Customer Addressing Plan.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 17. 1353NM Necom SubSystem 3
ED 01
3AL 89061 BA AA 34 / 280
280
N.B. The window is shown in two parts because there is no way to show all its contents in one shot.
Then pull down the “Action” menu and select “Apply & exit”.
5.2.2.1 Configure Antp

Configure the Equipment Time synchronization you have to add the “Antp_n” process. The following win-
dow will be shown to allow the “SUPERVISION_AREA” set–up for the Antp, IT MUST BE THE SAME DE-
FINED FOR THE RELATED RETIX STACK.
Figure 18. 1353NM Antp
Then pull down the “Action” menu and select “Apply & exit”.
5.2.2.2 Configure FT Server and Client
Configure the File Transfer by click on both item “FTserver_n” and“FTclient_n”. Their configuration is like
the “Anpt” one, for each one of them, you have to enter the number of the related “Necom_SubSsystem”
by setting up the “SUPERVISION_AREA”, IT MUST BE THE SAME DEFINED FOR THE RELATED RE-
TIX STACK.
Figure 19. 1353NM FTServer and FTclient
Then pull down the “Action” menu and select “Apply & exit” from each one of them.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 35 / 280
280
5.2.3 Configuring the 1353NM Element Manager Layers
When all the foreseen Retixt Stack instances have been predisposed for configuration, you can choose
which Network Element Managers (EM) you want to configure choosing one item shown in “System Confi-

guration” window left column (Figure 10. at page 29), select it by making a click with the mouse selection

button (the Item color will be changed from grey to blue in order to highlight it), then select the “Identifier
Input Field” and enter the EM identifier by keyboard.
N.B. The EM identifier value MUST be a value between <1354NM Instance Identifier>*100 and
<1354NM Instance Identifier>*100+99. If 1354NM Instance Identifier has been set to 2 the val-
ue must be between 200 and 299. The 1354NM Instance Identifier is the value entered predis-
posing and customizing the instance iduring installation phase.
Then click on the “Arrow Button”. If you enter an out of range value one of the following window will be
displayed, and the request rejected.
Figure 20. 1353NM Wrong Element manager identifier
If the request is accepted a new item will be shown in the right column, with the EM name followed by “_”
and identifier number. To include the created item in the configuration click on it, and the following window
will be shown:
Figure 21. 1353NM Element Manager – Retix Stack assignment
The window allows to assign the Element Manager to a specific Retix Stack instance. Clicking on button
under label “SUPERVISION_AREA” the possible Retix Stack instance will be shown, select your choice
and apply it by pulling down the menu “Action” and selecting “Apply & exit”.
For each Retix stack it is also possible to configure also same additional services, such as:
– Equipment Time synchronization.
– File Transfer to/from Equipments.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 36 / 280
280
5.2.4 Execute the configuration
When all the Element Managers and Services are assigned to the Retix Stack(s), the System Configura-
tion can be executed pulling down the “Main” menu and selecting “Update Config” item.
The configuration script start issuing a window with the execution traces. please ignore the warning and
error messages shown in the following windows:
Figure 22. 1353NM Configuration Warnings Window

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 37 / 280
280
Figure 23. 1353NM Configuration Error and Warnings window
At the end of System Configuration execution the “Dismiss” button in the lower part of window will be en-
abled. Look for any error and warning ignoring the shown once. If everything look correct pull down again
the “Main” menu and select “Quit”.
Figure 24. 1353NM Configuration quit.
Press “Yes” button to terminate.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 38 / 280
280
After the System Configuration, the following workaround must be executed:
.., $ /usr/Systems/1353NM_<instance_id>/script/createProcessConfig.pl \ [Enter]

1353NM <instance_id> \ [Enter]
/usr/Systems/1353NM_<instance_id>/Kernel/data/ProcessList.cfg [Enter]
Reading /usr/Systems/1353NM_1/Kernel/data/ProcessList.cfg
Reading /usr/Systems/1353NM_1/PMC2/conf/pmc2im.cfg
Writing /usr/Systems/1353NM_1/tools/process/conf/processconfig.cfg
Using /alcatel/Kernel/lib/lib_perl5.6.1/blib
At the end of procedure, copy (by ftp) on each Client instance (if any) the following file:
.., $ /usr/Systems/1353NM_<instance_id>/tools/process/conf/processconfig.cfg [Enter]

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 39 / 280
280
5.3 1353NM Master and Client Integration
If you have any 1353NM Client system, and you do not plan to install the 1354RM, you have now to inte-
grate all the 1353NM Clients with their 1354NM Master, by executing the following procedure on each one

of them:

1) Login as root user.
2) Start the global integration script by entering:

...,sys,root # /alcatel/Kernel/script/UpdateNeworkConnection.pl [Enter]
This procedure is explained in detail in Installation Guide.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 40 / 280
280
5.4 Process Monitoring
1353NM System is based starting from release 7.0 on OS–Kernel application, therefore , functions belong-
ing in previous releases to the System are now centralized and only customized for the single System on
top of OS–Kernel application.

The Process Monitoring & Control ( PMC ) tool is a graphic interface of the OS–Kernel application and
is one of this functions.
The PMC graphic interface is composed of a common window dedicated to display information and to exe–
cute commands for the management of all the processes (agents) of the selected System Instance.
The processes are collected in groups (i.e. Database processes, Alarms processes,..) and each group
is represented in the PMC window through an icon which colour informs the user about the group function–
al state.
The group icon gives the summarized information of the functional state of all the processes included in
the group and of all the childs of these processes.
Using the PMC window, the user can also execute different commands to interact with the Machine of the
selected System Instance.
The main executable operations are:
– Start / Stop System Instance.
– Start / Stop single/multiple group/s.
– Start / Stop single/multiple agent/s.
– Start / Stop Control function.
When function Control is enabled it verifies automatically the status of all the processes and restarts pro-
cesses which crashes.
When the Process Monitoring option is selected on TMN OS window, the following window appears:
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 41 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 25. Process Monitoring Control Main Window
280
3AL 89061 BA AA
42 / 280
5.4.1 Group Level concept applied in PMC
PMC component divides the managed processes in functional groups and the user can start or stop the
functional groups independently. The sequence of start and stop operations is conditioned by a depen-
dence implemented by the PMC between the functional groups.

When a functional group with a defined dependence level must be started, the PMC starts the functional
groups with lower dependence level if not already running before.
When a functional group with a defined dependence level must be stopped, PMC application stops the
functional groups with higher dependence level that are already running before.
Information about the group dependence level is available in the Info Area of the PMC Main Window only
if requested by the user (selecting the group icon).
5.4.2 Functional States defined in PMC
The PMC identifies the following functional states for the managed elements:
– Run : functional state assigned to elements that are correctly running.

– Stop : functional state assigned to elements that are stopped.
– Wrong : functional state assigned to the element that manages other elements; when one or more
of the managed elements should be running, but it/they is/are still stopped.
– Unknown : functional state assigned to the element when no data are available from the server for
this element.
– Working : functional state assigned to the element when an action is in progress for this element.
– On/Off : These are the functional states assigned to the element that can be enabled (On) or disabled
(Off) by the user (i.e. Control, Auto Start Control).
5.4.3 Colour usage in PMC
The icons representing the managed elements of the PMC can assume different colours and each colour
identifies a different functional state:
– Green is the colour associated to the Run functional state.
– Blue is the colour associated to the Stop functional state.
– Red is the colour associated to the Wrong functional state.
– Yellow is the colour associated to the Unknown functional state.
– Clear blue is the colour associated to the Working functional state

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 43 / 280
280
5.4.4 Startup
Using the Select mouse button, click the collapse/expand button in the PMC view containing the Node item
only to display the System Instance item (See following figure).

Figure 26. NM Instance selection
To start the NM Instance select Actions | ––> Start from menu.

1AA 00014 0004 (9007) A4 – ALICE 04.10
The purpose of this procedure is to start the single selected item or a group of selected items. The Start
action is allowed in the following items: System Instance, Groups and Agents. The Start action is not al-
lowed in the Node item and in the Child items.
ED 01
3AL 89061 BA AA 44 / 280
280
5.4.5 Stop
The purpose of this procedure is to stop the single selected item or a group of selected items. The Stop
action is allowed in the following items: System Instance, Groups and Agents. The Stop action is not al-
lowed in the Node and in the Child items.

To stop the NM Instance select Actions | ––> Stop |––> Selected Item from menu.
Figure 27. PMC : Stop selected item

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 45 / 280
280
5.4.6 System Defence
The purpose of this procedure is to enable the control on the System Instance. This procedure enables
a functionality (the Control) which verifies continuously the status of all the processes and restarts a pro-

cess which crashed. When a process doesn’t start, Control function repeats the start action on this process

only two consecutive times, afterwards if the process doesn’t restart it doesn’t try anymore. In this case
the process may be started manually. This condition may be verified through the Enabled or Disabled state
of the Control activity field in the Info Area of the selected agent. The Control functionality can be activate
and deactivate.
To enable the Control process, select in the menu bar Actions: Control: Activate . A confirmation box is
displayed.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 28. PMC : Activate Control
ED 01
3AL 89061 BA AA 46 / 280
280
• In Manual Restart Defence Mode
In manual defence mode, the process should be restarted manually from PMC menu using the Start action
If the process fails again after relaunching without delay and the process is vital, you should stop it and
restart the whole System Instance.
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 System Instance.
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
1353NM processes are cleanly stopped.
• In Automatic Restart Defence Mode
The following advices should be taken into account when handling process failure in automatic defence
mode:
– 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 MAINTENANCE–WS MANAGE-
MENT. The shutdown should be done only when the 1353NM 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.
– You are informed about the automatic restart procedure by a message in the console of the Master
Workstation. 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. A workstation also has a number of
lives, when this number is exceeded then the workstation stands by with all its processes stopped.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 47 / 280
280
5.4.7 Status
– 1353NM Status

The 1353NM Instance status can be seen in the PMC window according to the colours described in pre-

vious section.
– 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.
– Presentation Process Status
These processes are NOT monitored by the monitoring processes of the 1353NM 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 48 / 280
280
6 MAINTENANCE GENERALITIES
Several tools are provided with the 1353NM to handle common maintenance tasks.
Maintenance Directory Location and Content

The Maintenance directory ( /usr/Systems/1353NM_<Instance_Number>/maintenance/ :

<Instance_Number> is the number of the customized 1353NM instance (1 or 2 or...)) is dedicated to col-
lecting all data concerning the system maintenance. The data is distributed in various sub–directories lo-
cated under the main maintenance directory:
../1353NM_<Inst_Numb>
backup maintenance
backup core log failure stat trace
backup 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 com-
pressed.
maintenance/core the UNIX core files are saved in this sub directory.
maintenance/trace current instance trace and dataflow files.
maintenance/log log files.
maintenance/failure saving (of traces, of core...) when a process fails .The name of the files(directo-
ries) located in this sub–directory are conform to the format date_time (eg.
199802101455), for the date and time of the anomaly.
maintenance/stat global statistics on the system quality.
For each rubric , except stat ,the management tools provided by SMF allow visualizing , saving , deleting
the corresponding files or directories.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 49 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
280
3AL 89061 BA AA
50 / 280
7 DISKS FULL BACKUP AND FULL RESTORE
N.B. These operations are different from the backup/restore feature described in the chapter 10.
The disks Full Backup and Full Restore facilities allow to keep a complete disk(s) copy (dump) for the sta-
tion where the operation is performed.
The convenience of this copy is that it allows to recover in a fast and safety way the exact image of data
and software configuration. The inconvenience is that making an OS backup requires to do a backup on
each station and to stop each machine for a long time.
The complete description is reported in the Installation Guide.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 51 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
280
3AL 89061 BA AA
52 / 280
8 USER MANAGEMENT
8.1 SEC Administration

8.1.1 The access control model
SEC is the generic component integrated on OS–Kernel platform which implements access control in con-
juction with the applications for which access control is activated (EMLUSM, DNM, PNM, AS, SMF).
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 tar-
get. The definition of the access control policy consists in declaring initiators and targets, and then associ-
ating targets to initiators.
Clicking on TMN OS menu Actions ––> 1353NMAdmin the System Management menu will be displayed
(see Figure 30. ).
Figure 29. TMN OS SEC Administration activation

1AA 00014 0004 (9007) A4 – ALICE 04.10
This action displays the System Management selection window as shown in the following figure :
ED 01
3AL 89061 BA AA 53 / 280
280
Figure 30. System Mangement Menu to access SEC Administration
Select SEC Administration to access the following menu :
Figure 31. System Mangement Menu to access SEC Browser
This window allows to access SEC Administration. Selecting the corresponding row, SEC USM Browser
is displayed as shown in the follwing figure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 54 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
bination.
01
Figure 32. SEC USM Browser
280
3AL 89061 BA AA
The access control model of SEC is based on the notions of object, function, and object–function com-
55 / 280
Objects
Access control is based on objects on which the functions operate. In SEC context, an object is an atomic
non–functional resource of the NM system, accessible by the operator through the NM Application user
interface (pnmusm, emlusm, ..). Objects are classified by family.

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.
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 corre-
sponding 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. Symmetri-
cal 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 func–
tions 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.
Object–Functions Combinations
A combination is the association of an object and a list of functions applying to this object. Using combina-
tions can make the definition of policies easier 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), object–functions 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 1353NM system is to declare users. Declaring users must
be done via the Create User function described in chapter 8.9.4.1 on page 91.
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 charac-
terized 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.
Operators and operator groups are called initiators in the SEC environment. The objects, the functions
1AA 00014 0004 (9007) A4 – ALICE 04.10
and the object–function 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.
ED 01
3AL 89061 BA AA 56 / 280
280
1353NM provides a default set of operators with predefined profiles, as shown in Table 1. :
Group Operators Profile

admin axemladm administrator
constructor axemlcst constructor
operator axemlope operator
viewer axviewer viewer
viewer axrmaint admin
Table 1. Default operators in 1353NM
The caracteristics of each profile are:

– administator: NM administrator; he/she can do everything on NM but it has the xterm disabled;
– constructor: can do everything on maps and NEs but he/she has disabled some administration
functions: for example he/she can’t add or remove operators, he/she can’t do backup
and restore;
– operator: he/she can create local maps and import saved maps; can manage NEs (Start/Stop
Supervision) but can’t create NEs and can’t manage the global inventory; he/she
can’t add or remove operators, can’t do backup and restore;
– viewer: can view the maps and create local maps , and has very few functions.
On creating a new operator through the Create User function, you are required to select one of the prede-
fined profiles shown above; predefined names and predefined profiles cannot be reconfigured.
8.1.2 OADs and FADs
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.
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 Function-
al Access Domains (FADs), to ease the definition of rights.To allow inter–application function grouping,
the notion of System FAD is introduced. A System FAD can refer to any number of Application FADs.For
further details please refer to the Security Management included in 1350 SM REL.7.0 User’s Guide.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 57 / 280
280
8.1.3 Default User Profiles
The meaning of group/operator profile can be now summarized 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.

– a list of FADs. The union of these FADs results in a list of authorized functions.
– a list of OAD–FAD combinations resulting in a list of object–function combinations.
A generic OAD can be assigned to a resource. An example of resource is a Network Element (NE); when
a NE is created the Operator can decide which ACD is assigned to the NE itself.
The Access Control Domain feature is used to control the access to NEs, enabling or disabling some
management functions.
By default only ACD Unknown exists; each default group (i.e. admin, constructor, operator, viewer) has
in his own Included targets the EleOad Unknown and the corresponding OAD–FAD <groupname>–Un-
known. Each initiator can manage NEs having ACD Unknown according to the default OAD–FAD of the
group of ownership.
For each application the system gives a set of default FADs. For example:
– PnmUsmAdmininstrator
– PnmUsmOperator
– PnmUsmViewer
The default Application FADs are the following :
– Administrator, 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 58 / 280
280
8.1.4 Customizing User Profiles
8.1.4.1 New ACD creation

– In this section it is shown how to create and to manage new ACDs.

– To create a new ACD, select on the left side of the SEC Browser OAD –> Object –> Create Object.
( see Figure 33. ).
Figure 33. Object creation
To define a new Object it’s necessary to specify mandatory information ( Name, Family 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 AccessControlDomain-
Family can be used by EMLUSM ), the OAD information defines the Elementary OAD which can see
in any case the resource ( i.e. NE in the Network Map ) with the new OAD.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 59 / 280
280
– The second step is to manage the Elementary OAD ( see Figure 34. ) and associate the created ACD
to the Elementary OAD.
In the example of Figure 34. obtained selecting OAD–>Elementary OAD select the tabbed panel

Create Elementary OAD, ACD test_acd has been created by the operator “alcatel”.

The ACD Unknown is always in the Excluded Objects for each initiator, because it’s in the Included
Object for each default group ( see 8.1.3 ).
Figure 34. Elementary OAD creation.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 60 / 280
280
8.1.4.2 FAD definition
N.B. The System Fad in the Included targets is fondamental for the PNM Menu. By default an opera-
tor inherits the SysFad of the group to which he/she belongs, and so the PNM Menu that is dis-
played corresponding to the functions enabled for this SysFad, but if you want that an operator
belonging to viewer group has the PNM Menu of an admin you’ve to put the SysFad Administra-
tor in the Included targets of the operator.
From the function tree on the left of the window select FAD –> Application FAD, selecting the
tabbed panel Create Application FAD it is possible to define the FAD ( Function Access Domain
); it describes the functions available for each kind of application which SEC supports.
– It’s possible to create a new set of FAD ( for example in the application list for ASCurrentUsm in
Figure 35. ) .
Figure 35. Create/Modify a new Application FAD
It is possible to customize each FAD selecting the functions to be supported by the specific FAD. In
the example the left box contains the functions that are not assigned to the profile . This means, for
example, that if an operator has in the Access Rights the Sys FAD “Viewer” he/she can export alarm
information but can’t apply other functions like Acknowledge Alarm.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 61 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 36. Application FAD for user viewer
280
3AL 89061 BA AA
62 / 280
1353NM provides the following applications:
• AsCurrentUsm
• AsHistoricalUsm
• EmlUsmATM
• EmlUsmATMV2
• EmlUsmATMV3
• EmlUsmPREAV1
• EmlUsmPREAV2
• EmlUsmDXC
• EmlUsmSH5ADM
• EmlUsmSH5DXC
• EmlUsmSH5MW
• EmlUsmSH5MWV2
• EmlUsmSH5MWV3
• EmlUsmSH5WDM
• EmlusmVC
• dnmusm
• emlusmmelosnmp
• EmlUsmSH30 qb3s
• EmlUsmSH31 qb3s
• EmlUsmSH5 qb3s
• pnmusm
It is possible to create a new System FAD; for example in this case Supervisor that contains only one
Application FAD in the Included Application FADs that is PnmUsmSupervisor.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 63 / 280
280
8.1.4.3 OAD–FAD definition
The next step is to manage the new FAD profile ( PnmUsmSupervisor ) that has been created. It is
necessary to refer to the OAD–FAD concept (see 8.1.1).

– Selecting OAD–FAD combination on the left side of the SEC Browser window it is possible to define
the OAD–FAD combination ( see Figure 37. ), this information describes which kind of functions (
FAD ) is possible to perform on a specific object ( OAD )
Figure 37. OAD–FAD Combination creation
Using this interface it is possible to associate a set of FADs to an Elementary OAD, i.e. to define which
FADs are enabled to which OAD. If an operator has in his/her Access Rights this OAD–FAD he/she
can apply allowed functions for “admin” in the Included Objects of the Elementary OAD “viewet”.
So it is possible to create a new user that can perform only specific actions (FAD) on specific objects
(OAD).
In order to activate changes, like adding new OAD–FADs or elementary FADs to an operator, it is not
enough restarting the application or re–login. It’s necessary to kill the lss process on all NM workstations
(via kill Unix command), the lss process automatically restarts.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 64 / 280
280
8.1.5 An example of management of OAD, FAD, and OAD–FAD
In this chapter it is shown how to manage OAD, FAD and OAD–FAD, and some examples of what it is
possible to do with them are given.
N.B. A very important feature of Sec is the management of ACD, it is used to enable some operators
to see some NEs on some ADC and to disable other to see them.
N.B. The System Fad in the Included targets is fondamental for the PNM menu.
By default an operator inherited the SysFad of the group to which he/she belongs, and so the
PNM Menu that is displayed corresponding to the functions enabled for this SysFad, but if you
want that an operator belonging to viewer group has the PNM Menu of an admin you’ve to put
the SysFad Administrator in the Included targets of the operator.
On the other hand if you want that an operator belonging to admin group has the PNM menu
of a constructor you’ve to put the SysFad Constructor in the Included targets of the operator.
N.B. It is very important to note that it is necessary to remove the SysFad that includes the
greather number of functions, for example in the previous SysFad Administrator has to be
removed and then to put SysFad Constructor, because domains the SysFad with more
functions allowed.
First of all it is important to underline that there is a difference between see an ACD and manage it.
– See an ACD means that in the PNM it is possible to see the NEs created on this ACD; and selecting
“NE info..” it is possible to see in the Access Control Domain area the name of this ACD. But it is not
possible to do operations on this ACD.
– Manage an ACD means that on the NEs created on this ACD it is possible to do for example “Start
and Stop Supervision“, or to set “NE Address”, etc....
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 65 / 280
280
Some examples follow.
First example: the operator axadmin can only see an ACD;

as first step create an ACD test_acd ( see Figure 33. ).

N.B. When an ACD is created, an “ElementaryOAD” can be associated to the ACD selecting the OAD
from the list displayed in the box OAD; in this case the ACD is associated to the EleOad selec-
ted, containing the ACD test_acd in the Included Objects.
Figure 38. Default Access Rights Definition for operator axadmin

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 66 / 280
280
Figure 39. Modify the NE ACD value
In this case the operator axadmin can see on the PNM map all the NEs created with ACD adm_dom, and
he/she can modify its ACD value by selecting the NeInfo Menu from PNM( see Figure 39. ).
N.B. If the ACD is changed from unknown to test_acd it is impossible to do anything; every Action
is forbidden because in the ACD test_acd the operator has no functionality.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 67 / 280
280
Second example: axadmin can manage an ACD:
• It is necessary to add the OAD–FAD test_oadfad in the Acces Rights of the operator test so that
the operator test is an administrator in the ACD test_acd. (see Figure 40. ) (in this way the oper-

ator can have the Included Functions of the System Fad Administrator for the Included Object

of the EleOad axadmin ).
Figure 40. Access Rights Definition of test with the OAD–FAD test_oadfad
In this case test can manage the NEs on the ACD test_acd.
N.B. If the ACD is changed from unknown to test_acd every Action admitted for the System Fad
Administrator is enabled.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 68 / 280
280
Third example: a new operator belonging to the admin group that can manage a new ACD (with the func-
tions allowed for admin group):
N.B. By default an operator belonging to a group has a FAD defined for the unknown domain. For
each new ACD it is necessary to define the set of functions allowed on the ACD.
• A new operator testadm belonging to admin group is created by smf tools “Add Operator”.
• A new ACD is created by the operator testadm:
Figure 41. ACD creation
• By default the operator testadm has defined a FAD for the Unknown ACD.
• To allow testadm to manage the new ACD test_dom (with the functions allowed for admin
group) it is necessary to define a set of function allowed on this ACD.
• It is necessary to define an OAD–FAD where OAD is the new EleOad and the FAD is a SysFad
(in a reverse order) ; so the new OAD–FAD is admin–testadm.
• Then this new OAD–FAD has to be put in the Included targets of testadm.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 69 / 280
280
Fourth example: it is like the third one but the set of allowed functions is smaller (it has been cut the possi-
bility of managing the stack retix).
• The conditions are the same of the example 3 but now the combination OAD–FAD is different.

• It is necessary create a new ApplicationFAD (in which there is not the possibility of managing
stack retix) and a new SysFad.
• The new ApplicationFAD is added in the smf Application, it is smfSHSmallAdmin that has all
functions of Administrator minus “StackCfg” that manage the Stack Retix:
Figure 42. Create a new Function Access Domain

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 70 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
•
01
that has every Administrator.
Figure 43. Create a new SysFad
280
3AL 89061 BA AA
The new System FAD is added in the smf Application, it is SmallAdmin instead of smfSHadmin
71 / 280
• Now it is necessary to create a new OAD–FAD smallAdmin–testadm to add in the Included tar-
gets of the Access Rights of the operator testadm:

Figure 44. Create a new OAD–FAD
• In this way it has been created a new operator that belongs to the admin group but that cannot
manage the stack retix.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 72 / 280
280
8.1.6 Creating new Profiles
From SEC USM Browser is possible to create Operator profiles. A new profile can be composed using
OAD–FAD combinations, System FAD, Elementary OAD and Apllication FAD.
The defined profiles can be used from SMF when creating a new user.
The following window shows the SEC USM Browser for creating a new profile.
Figure 45. Create a new profile

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 73 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 46. Profiles in SMF–Create User
280
3AL 89061 BA AA
74 / 280
8.2 Session Management
To activate the function acted to manage the session on a workstation start from TMN OS menu Global
Actions |––> Operator |––> Session Management as shown in following figure :
Figure 47. Session Management activation from TMN OS
When clicking on the option, the following window is displayed:

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 75 / 280
280
Figure 48. Session Management
This function allows to manage the session connected on the workstation. The possible actions to be per-
formed are :
– Broadcast Message
– Show good logins
– Show bad logins
– Lock
– Unlock
– Forced Logout
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 76 / 280
280
8.3 Broadcast Message
This function allows to broadcast a message to all workstations listed in Session Management window.
When clicking on the option or using the menu icon , the following window is displayed:
Figure 49. Broadcast Message
For broadcast a message write the text in the displayed window and send confirming with <OK> button.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 77 / 280
280
8.4 Show Good Logins
List the history of good logins. 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).

When clicking on the option or using the menu icon , the following window is displayed:
Figure 50. Show Good Logins

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 78 / 280
280
8.5 Show Bad Logins
This function shows the history of bad logins.

When clicking on the option or using the menu icon, the following window is displayed:
Figure 51. Show Bad Logins

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 79 / 280
280
8.6 Lock
This function allows to lock a workstation selected in the session management display window.


Figure 52. Lock a workstation
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 80 / 280
280
8.7 Unlock
This function allows to unlock a workstation that was previously locked, selected in the session manage-
ment display window.
Figure 53. Unlock a workstation

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 81 / 280
280
8.8 Forced Logout
This function allows to logout a user from the selected workstation. Select the menu function from User
menu.

Figure 54. Forced Logout
To logout a user:
– Select the user in the list.
– Click on the Force Logout push–button under the menu Users.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 82 / 280
280
8.9 User Management
8.9.1 Global Operators Administration

As said in previous sections of this document this Network Release of Network Management products has
signed a turning point, now more different Network Management products can be integrated in a common
environment. This new configuration has brought to a ’Global Operators Administration’ as explained in
the following of this paragraph, this centralized function allows to define operators for the Network Mana-
gement environment defined on a group of workstations.
The application to manage system users is started from TMN OS menu Global Actions |––> Operator
|––> Global Operators Administration as shown in following figure :
Figure 55. Activating User Management functions
The following window will be displayed :

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 83 / 280
280
Figure 56. Global Operators Administration
A list of profiles is proposed to used to define a new user to the System. The default defined profiles are
:
– ALL–Administrator: this profile has access to all system functions on all Network Management Sys-
tems (1353NM, 1354RM, ...)
– ALL–Operator: this profile has access to the functions on all Network Management Systems
(1353NM, 1354RM, ...) defined for the Operator profile
– ALL–Viewer: this profile has access to the system functions on all Network Management Systems
(1353NM, 1354RM, ...) defined for the Viewer profile
– ALL–Constructor: this profile has access to the system functions on all Network Management Sys-
tems (1353NM, 1354RM, ...) defined for the Constructor profile
– <NM Product>_<Instance_Number>–Administrator: this profile has access to all the system

functions on <NM Product> System (1353NM or 1354RM or ...)
– <NM Product>_<Instance_Number>–Operator: this profile has access to the functions on <NM

Product> System (1353NM or 1354RM or ...) defined for the Operator profile
1AA 00014 0004 (9007) A4 – ALICE 04.10
– <NM Product>_<Instance_Number>–Viewer: this profile has access to the system functions on

<NM Product> System (1353NM or 1354RM or ...) defined for the Viewer profile
ED 01
3AL 89061 BA AA 84 / 280
280
– <NM Product>_<Instance_Number>–Constructor: this profile has access to the system functions
on <NM Product> System (1353NM or 1354RM or ...) defined for the Constructor profile
8.9.1.1 User Creation

Selecting the function User |––> Create from the User Management menu the window for the user defini-
tion will be displayed.
Figure 57. Create user
The data to specify inserting a new user are the following :
– User Login : is the identification of the user, inserted when login on the System;
– Description : a short description of the user to create;
– New Password : a password that will be asked when the user logs into the System (at least 6 charac-
ters);
– Confirm : the password inserted should be confirmed to be valid.
– Profile Management : selection of the profile for the user to be created; a combination of several pro-
file can be inserted to define the desired user.
– Login Localization : selection of the workstations where the login is allowed.
The button <Apply> confirms the creation of the new user, while the button <Cancel> exit without modifica-
tions, that is the new defined user is not created.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 85 / 280
280
8.9.1.2 Update User
Selecting the function User |––> Update from the User Management menu the window for updating the
user data will be displayed, the user data can be modified and confirmed with the <Apply> button. The

window is the same window described in the previous section for user creation, the only difference is that

the user to be modified should be selected in the user list.
8.9.1.3 Delete User
Selecting the function User |––> Delete from the User Management menu the window displaying the selec-
ted user data is shown; to delete the selected user select the button <Ok>.
Figure 58. Delete User

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 86 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
tions.
01
8.9.2 Change Password
Figure 59. Change password
280
3AL 89061 BA AA
The administrator can change any user’s password. The new password will be effective on all worksta-
87 / 280
8.9.3 Set Max Users Number
The function allows to define the maximum number of simultaneous users connected to the Workstation.
The following figure represents the window to introduce this data.

Current Value : is the value actually set for maximum users value;
New Value : allows to insert a new value for the maximum value;
Default : is the defined default value for the maximum value.
The Apply Button defines the current value;
the Default Button applies the default value as current value;
the Close Button closes the window.
Figure 60. Set max users number

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 88 / 280
280
8.9.4 SMF Operators Administration
’SMF Operators Administration’ allows to create, update, delete users on the selected Network Manage-
ment System in TMN OS window.
The application to manage system users with SMF local on the selected system on TMN OS starts from-
menu Actions |––>SMF |––> Operators Administration as shown in following figure :
Figure 61. Activating SMF User Management functions

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 89 / 280
280
Figure 62. SMF Operators Administration
A list of profiles is proposed to used to define a new user to the System. The default defined profiles are:
– Administrator: this profile has access to all system functions on the selected Network Management
System (1353NM in our case)
– Operator: this profile has access to the functions on 1353NM Network Management System defined
for the Operator profile
– Viewer: this profile has access to the system functions on 1353NM Network Management System
defined for the Viewer profile
– Constructor: this profile has access to the system functions on 1353NM Network Management Sy-
stem defined for the Constructor profile
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 90 / 280
280
8.9.4.1 User Creation
Selecting the function User |––> Create from the User Management menu the window for the user defini-
tion will be displayed.
Figure 63. SMF Create user
The data to specify inserting a new user are the following :
– User Login : is the identification of the user, inserted when login on the System;
– Description : a short description of the user to create;
– New Password : a password that will be asked when the user logs into the System (at least 6 charac-
ters);
– Confirm : the password inserted should be confirmed to be valid.
– Profile Management : selection of the profile for the user to be created;
– Login Localization : selection of the workstations where the login is allowed.
The button <Apply> confirms the creation of the new user, while the button <Cancel> exit without modifica-
tions, that is the new defined user is not created.
8.9.4.2 Update User
Selecting the function User |––> Update from the User Management menu the window for updating the
user data will be displayed, the user data can be modified and confirmed with the <Apply> button. The
window is the same window described in the previous section for user creation, the only difference is that
1AA 00014 0004 (9007) A4 – ALICE 04.10
the user to be modified should be selected in the user list.
ED 01
3AL 89061 BA AA 91 / 280
280
8.9.4.3 Delete User
Selecting the function User |––> Delete from the User Management menu the window displaying the selec-
ted user data is shown; to delete the selected user select the button <Ok>.

Figure 64. SMF Delete User

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 92 / 280
280
8.10 Set Personal Printer
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.
Figure 65. Set Default Printer window

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 93 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
280
3AL 89061 BA AA
94 / 280
9 SYSTEM LOG MANAGEMENT
9.1 SMF/Command/Event Logs Management/Visualization

The follwing windows shows the activation of SMF Log Management function :
Figure 66. System Log Management activation

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 95 / 280
280
9.1.1 General
The Log files are written by administration scripts in order to archive meaningful operations in the history
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 sys-

log.
There are 4 types of log :
– Security logs: generated by the SEC application.

– Command logs: generated by operators via PNMUSM and EMLUSM.
For Command Logs management a Java interface is available too; it is described in chapter 9.1.6.
– System logs (or SMF Logs): generated by SMF functions.
– 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.
The log file formats are defined in OSKernel platform configuration files. The log files formats that can be
used are : SYSTEM, COMMAND and EVENT.
9.1.2 Management of log files
9.1.2.1 Log line format
’YYYY MMM DD HH:MM:SS’ ’hostname’ ’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 operations.
N.B. The error level (err, warning,notice) is not reported in the log.
– Subsystems
The following subsystems are used :
• user • tnm
• log • configuration
• agent • start stop
• backup restore • maintenance
• operation • plugin
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 96 / 280
280
9.1.2.2 Files state
Several logs files exist, they can be in the 4 different states (see Figure 67. ):
– 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 prede-
fined 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 ar-
chive 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.
automatic
current log overflow log
automatic
manual or manual or sched-
scheduled uled
archived log deleted overflow log
manual
deleted archived log
Figure 67. Logs states
– The IM and USM create current log files. Each log file has a predefined size.
– When a log file exceeds its predefined size, it is renamed with the .old extension. It is now an overflow
log file. The administrator is notified by mail when the overflow log file is created. The logging contin-
ues with the current log file.
– When the administrator is informed an overflow log file has been created, he/she has to move this
file in an area on the master workstation. The overflow log file becomes an archived log file. Archived
log files are compressed by using gzip.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 97 / 280
280
9.1.2.3 Log Handler Configuration
The Log handler tool can be configured by the OS administrator. The configuration file is called axsys-
log.cfg and is located under $DIR1353NM_<Instance_number>/conf/. The format is of the form

tags:value:

– 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 between syslogd and axsyslogd
– facility_smf: facility used by SMF error logging function
– facility_super: facility used by superuser.
9.1.3 Access rights
SMF Command Access rights
SMF logs management admin , on Master station
SMF logs visualization all users
Command logs management admin , on Master station
Command logs visualization all users
Event logs management admin , on Master station
Event logs visualization all users
Java Command logs visualization all users
Java Command logs management admin , on Master station
Table 2. Log Management: Access rights for different User Profiles

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 98 / 280
280
9.1.4 Log Tools
Logs Management functions can be accessed through Actions |––> SMF |––> System Log Manage-
ment option.
Listed below are the tool names and a short description.

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 & overflow 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.
Print To print the displayed current log records.
Delete logs To remove a saved log file.
Table 3. Log Management Options

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 99 / 280
280
9.1.5 SMF Logs Management (User Interface)
For each type of log, a common graphic user interface offers the possibility to view records (with filter) from
the log files and to create, to view or to remove archive files.

Selecting a System Instance icon on the TMN–OSs menu from the menu function Actions |––> SMF |––>
Log Management the Log Management window will be displayed.
Figure 68. Logs Management
N.B. The window is identical for the three options except the status bar.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 100 / 280
280
9.1.5.1 Operations on Log Files
The menu Log Files manages operations on the different log files as explained in following sections.
9.1.5.1.1 View Current Logs option

From the Log Management window it is possible to display the selected log file info in two different ways:
– From the menu Log File |––> Info
– Pressing the left button on the icon bar
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.
Figure 69. Log Management : Log File Info

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 101 / 280
280
9.1.5.1.2 Archive Log File
From the Log Management window it is possible to archive the log files in a compressed format. Select
a log file from the log files list, then it is possible to archive it following two different ways :

– From the menu Log File |––> Archive
– Pressing the middle button on the icon bar
Figure 70. SMF Log Management : Log File Archive
A valid name for the archive file should be inserted and confirmed with <OK> button.
9.1.5.1.3 Delete Log Files
From the Log Management window it is possible to delete a log file selected in the log files list selecting
from the menu Log File |––> Delete. A confirmation window will be displayed.
Figure 71. SMF Log Management : Delete Log Files

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 102 / 280
280
9.1.5.2 Operations on Log Records
The menu Log Record manages operations on the log records belonging to the different files as explained
in following sections.
9.1.5.2.1 Log Record Update
From the Log Management window it is possible to update the display of the selected log file selecting from
the menu Log Record |––> Update. An update operation is done on the selected log file.
9.1.5.2.2 Log Record Filter
From the Log Management window it is possible to filter the records of the selected log file selecting from
the menu Log Record |––> Filter. A window will be displayed as shown in following figure :
Figure 72. Log record filter

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 103 / 280
280
Two type of filters are possible :
• Date & Time Filter : a time interval can be inserted to filter the records in the log file. ’After’ can
display all the records stored after the inserted date, ’Before’ can display all the records stored

before the inserted date; if both dates are inserted the records in the interval between the two

dates are displayed.
• Attribute Filter : allows to define a list of criteria from the records attributes. This area contains
three sub–areas :
– the first sub–area is a three part line :
• click on the Attribute option to select an attribute among the list: the attributes should
be related to the selected log file to provide appropriate filter result.
• click on the Operator option button to select the kind of comparison which is going
to be performed between the previously selected attribute and a value.
• the Value part allows the user to choose a value among a list (if there is an option
button) or to enter a value (if there is only an entry field).
– the Filter Items sub area displays all the attribute filter criteria just bbeing defined by the
user,
– the third sub area contains two push buttons and two radio buttons :
• click on Add push button to add an item just after defining an attribute criterion
• click on Remove push button to delete an item from the Filter Items list
• click on AND radio button if all the items of the Filter Items list must be verified to re-
trieve a log record
• click on OR radio button if at least one of the items of the Filter Items list must be veri-
fied to retrieve a log record
The <Apply> button confirms and applies the selected filter.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 104 / 280
280
9.1.6 Command Log Viewer
The operator can click the Command Log Viewer item in System Management – NE Administration
area to start the CLV (see ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 73. Starting CLV
ED 01
3AL 89061 BA AA 105 / 280
280
Figure 74. Starting CLV
9.1.6.1 Parse Command Log
Generally, after CLV is started, the following figure would be shown (see Figure 75. ). In Log Files Panel,
all the available command log file(s) are listed.
CLV can parse command log file(s) on the master or presentation workstation. The location of the com-
mand log files is masked by CLV. If the selected command log file locates in the same host with CLV, CLV
opens it directly. Otherwise, CLV opens it through a background process automatically.
After the operator selects the target file(s), the Parse button is active (see Figure 75. ).
Figure 75. Select Target Log File
The operator can click the Parse button to parse the target log file. During the parsing period, the Parse
1AA 00014 0004 (9007) A4 – ALICE 04.10
button is presented as a Stop button; operator can click it to cancel the parsing action.
When an operator needs help, he (or she) can click the Help button and start the Online Help to get how
to manipulate the relevant function.
ED 01
3AL 89061 BA AA 106 / 280
280
Click the Refresh button; the log file list can be refreshed manually.
N.B. If an operator wants to select several log files at the same time, operator can do it with the follow-
ing two ways:
– A: Press the Ctrl key on the keyboard while use mouse click the target log files in the file
list (continuous items or discontinuous items).
– B: Press the Shift key on the keyboard while use mouse click the target log files in the file
list (continuous items).
9.1.6.2 Extract Command Log
After the target log files are parsed, operator can extract log record in the target log file with filters. There
are two kinds of filters in CLV, the simple filter and the advanced filter.
If a filter is not saved, we call it a temporary filter, which is only applicable in the current CLV application
instance. If you save a temporary filter with a specific name, it becomes a persistent filter and you can use
them next time.
9.1.6.3 Simple Filter
Simple filter is simple but more convenient and intuitive (see Figure 76. ).
Figure 76. Simple Filter

1AA 00014 0004 (9007) A4 – ALICE 04.10
There are 5 filter items in simple filter, Operator, Machine, Entity, Date and Command. These entire filter
items are used as conditions to filter the output of the command log files. The logic among the filter items
are AND.
ED 01
3AL 89061 BA AA 107 / 280
280
User can click the checkbox to activate a filter Item, and assigns a specific value to it.
For example, user activates the Operator, Machine and Command, then selects operator is alcatel, Ma-
chine is NM70 and Command is “Access State Cmd”, at the same time, the filter has been constructed.

(See Figure 55)

The operator clicks the Apply button to extract the target log with the selected filter items.
During this period, the Apply button is presented as a Stop button; operator can click it to cancel the ex-
traction action.
Operator can click the Help button to get the online help.
The operator clicks the Output to HTML button to output the extracted result to browser.
N.B.:
If operator needs to select an item in the filter item field, operator can click the item in the item field, e.g.
command item field.
If operator wants to select several items in the filter item field at the same time, operator can do it with the
following two ways:
A: Press the Ctrl key on the keyboard while use mouse click the target items in the item list (continu-
ous items or discontinuous items).
B: Press the Shift key on the keyboard while use mouse click the target items in the item list (continu-
ous items).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 108 / 280
280
9.1.6.4 Advanced filter
When CLV user wants to create a very complex filter, he/she can use the advanced filter to construct the
filter (see Figure 77. ).
Figure 77. Advanced Filter
Each row of the table represents a single logical condition made up by a subject (Variable), a relational
operator, and a value of comparison (Value). Several logical conditions can be set by Boolean operators
and grouped by round brackets.
9.1.6.5 Variable
By clicking on a ’Variable’ cell, a combo–box is shown with all possible subjects (see Figure 78. ):
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 78. Selecting the subject
ED 01
3AL 89061 BA AA 109 / 280
280
9.1.6.6 Relational Operators
By clicking on a ’Compare to’ cell, a combo–box is shown with all possible relational operators (see Figure
58):

Figure 79. Selecting the relational operator
9.1.6.7 Value
By clicking on a ’Value’ cell, the user is allowed to set the term of comparison; the inserted value has to
be consistent with the related subject (Variable)(see figure 59).
Figure 80. Selecting a value of comparison
9.1.6.8 Brackets
By clicking once on a left/right ’+’ cell, a left/right round bracket is added;
By clicking once on a left/right ’–’ cell, a left/right round bracket is deleted.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 110 / 280
280
9.1.6.9 Operators
By clicking on an ’Operator’ cell, a combo–box is shown with AND/OR/Stop operators (see figure 60):
Figure 81. Combining Logical Conditions
Selecting one of AND/OR on the last row of the table, a new row is added.
Selecting Stop operator stops constructing the filter or deletes the behind row.
N.B.: Only the CLV user with administrator or constructor permission can use the advanced filter.
In most cases, the simple filter is enough.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 111 / 280
280
9.1.6.10 Temporary filter
Before the filter is saved manually, it’s only a temporary filter (See Figure 61).

Figure 82. Temporary Filter
Operator can click the Save button save the temporary filter. After the temporary filter is saved, the tempo-
rary filter will be the persistent filter.
N.B. The persistent filter name should be a valid Java identifier. The filter name must start with a Uni-
code letter, underscore, or dollar sign ($). The other characters, if any, can be a Unicode letter,
underscore, dollar sign, or digit.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 112 / 280
280
9.1.6.11 Persistent filter
After the filter is saved manually, it’s a persistent filter.

When the operator want to use the persistent filter to extract the target log file. Operator can click the filter
name list, and select the needed filter. The persistent filter will append the filter value to Filter field (see
Figure 62).
Figure 83. Selected Saved Filter
Operator can construct the temporary filter that bases on the persistent filter to extract the target log file(s).
The operation is the same as the temporary filter.
Operator can modify or delete the persistent filter.
N.B. When the selected target log file is different with the log that constructs the persistent filter, the
persistent filter may be not applicable for the selected target log file. But CLV will not check that.
9.1.6.12 Display and ouput result
The filter result can be displayed and outputted with two ways. One is displayed with Browser; the other
can be displayed with table.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 113 / 280
280
9.1.6.13 Display result with Browser
If the user press Output to HTML button, the extraction result will be displayed in the Browser (see Fig-
ure 63).

Figure 84. Extraction result

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 114 / 280
280
9.1.6.14 Display result with table
There are the 4 parts in the Command Result List window (see Figure 64).
a. Top part is menu of the window

b. Part 2 is the result statistics information
c. Part 3 is the extraction result list
d. Bottom part is the selected record information.
Figure 85. Extraction result list

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 115 / 280
280
9.1.6.15 The menu of the window
The menu items of the window are:

List Menu:

a. List–>Print…
Print the selected record.
b. List–>Print Preview
Display the Print Preview window.
c. List–>Export…
Export the selected record to /tmp/CLVTableOutput.txt file.
d. List–>Close
Clicking the menu item to close the window.
Action Menu:
a Action–>Select–>All
Select the all records in the table.
b Action–>Select–>None
Clear the record selected status in the table.
Display Menu:
a. Display–>Detail Info
Clicking the menu item to display the selected record detail information window (see figure 65).
Help Menu:
a. Help–>Command Result List
Clicking the menu item to display the help information.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 116 / 280
280
9.1.6.16 The statistics of the extraction result list
The statistics information part includes the following main content (see Figure 65):
a. The number of the different type command record in the extraction result list.
b. The total number of the different type command record in the extraction result list.
Figure 86. Extraction result list’s statistic information
The figure indicates the number of the Error type command record in the extraction result list
is 2.
The figure indicates the number of the Cmd type command record in the extraction result list
is 4.
The figure indicates the number of the Confirm type command record in the extraction result
list is 2.
The figure indicates the number of the Unknown type command record in the extraction result
list is 0.
The figure indicates the number of the all type command record in the extraction result
list is 8.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 117 / 280
280
9.1.6.17 Display detail information of the command
User can see the detail information of the selected record when user double–click the selected record in
the extraction result list (see Figure 66).

Figure 87. Detail information
9.1.6.18 The menu of the window
The menu items of the window are:
Action Menu:
a. Action–>Print…
Print the selected record.
b. Action –>Print Preview
Display the Print Preview window.
c. Action –>Export…
Export the selected record to /tmp/CLVDetailOutput.txt file.
d. Action –>Close
Clicking the menu item to close the window.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 118 / 280
280
9.1.6.19 The detail information of the extraction record
The detail information in the window is:

Date: indicates the date of the command record.

Machine: indicates the machine name of the command record.
Operator: indicates the operator name of the command record.
Process: indicates the process name of the command record.
Process ID: indicates the process ID of the command record.
Command: indicates the command name of the command record.
Command Body: indicates the command body of the command record.
9.1.6.20 Print and print preview
The Print and Print Preview function is provided in CLV1.4. User can use the print function to print and Print
Preview the selected record and its detail information.
The underlying is the detail introduction.
9.1.7 Printing the selected record
When user clicks the print menu Item (e.g. List–>Print … or Action–>Print…). A printer print dialog will
appear (see figure 67).
Figure 88. Print dialog

1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. User has to input the target printer name when user needs to print the file to printer.
ED 01
3AL 89061 BA AA 119 / 280
280
9.1.7.1 Print preview of the selected record(s)
When user clicks the Print Preview menu Item (e.g. List–>Print Preview or Action–>Print Preview), the
Print Preview window will appear (see Figure 68). The default display scale is 75%. User can select the

different display scale from 10% to 400%.

Figure 89. Print preview window
To click the button, preview the first page of the previewed page(s).
To click the button, preview the previous page of the current page.
To click the button, preview the next page of the current page.
To click the button, preview the last page of the previewed page(s).
To click the button, set the printer print format.
To click the button, print the result.

1AA 00014 0004 (9007) A4 – ALICE 04.10
The button is useless at present.
ED 01
3AL 89061 BA AA 120 / 280
280
To click the scale combo box , set the scale of the
preview page from 10% to 400%.
To click the close button, close the window.
9.1.7.2 Export the result to text file
If user needs to export the display result to text file, he (she) can click the Export… menu item (List–>Ex-
port…in Detail Info window or Action –>Export… in Command Result List window).
9.1.7.3 Export the selected command result to text file
User clicks List–>Export…in the Command Result List window, a Save window will appear (see Figure
69). The default export file is CLVTableOutput.txt.
Figure 90. Export the selected command result list to text file
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 121 / 280
280
9.1.7.4 Export the detail information of the selected command record to text file
User clicks Action–>Export…in the Detail Info window, a Save window will appear (see Figure 70).
The default export file is CLVDetailOutput.txt.

Figure 91. Export of the selected command record detailed info to text
9.1.7.5 Display Online Help
The CLV Online Help has the same format as 1353NM. When the user clicks the Menu item:
Help –> User Manual to start the CLV Online Help (see Figure 71).
Figure 92. Display online help

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 122 / 280
280
9.1.7.6 Exit CLV
Select File–>Exit menu item, a confirmation dialog is displayed (see Figure 72). User can confirm whether
delete the extraction result folders automatically when user clicks the Ok button on the confirmation dialog
to exit the CLV application.

As default, the all extraction result output folder will be selected when user select File–>Exit menu item
(see Figure 72).
Figure 93. Exit CLV confirmation dialog

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 123 / 280
280
9.2 Failure Management
All the users can access this function, via the SMF, from any station.

9.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 don’t cause the service to stop. This is in that case fre-
quently ergonomic type abnormalities or functional malfunctioning. For this kind of abnormality, the SDH
Manager gives the administrator the ability to edit system fault reports.
9.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.
– NM_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 sub–directories maintained under the maintenance/failure directory.
The delay between successive invocation of the failure capture process, manual or automatic, is 5 min-
utes.
9.2.3 Sequence of events when a process exits abnormally
When a process terminates abnormally, the Application Manager 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.
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 system management 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.
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
1AA 00014 0004 (9007) A4 – ALICE 04.10
process was invoked (i.e. time of failure), the caller , a headline indicating the rogue process if present,
the version of the NM as a result if executing axversion and a list of all the files captured.
ED 01
3AL 89061 BA AA 124 / 280
280
9.2.4 Failure Tools
Failure Management functions can be accessed through Action |––> SMF |––> Failure Management
feature.
Listed below are the tool names and a brief description.

SMF Command Tool Description
Capture Data Failure capture process – captures the core (only when acti-
vated 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 .
Save on Tape Allows selective backup of failure from specified machine to

master workstation.
Remove Allows selective removal of failure directory.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 125 / 280
280
9.2.5 Failure Management (User Interface)
This function permits to collect data that are transferred to a server in order to have a snapshot of the sy-
stem instance in case of failure. This snapshot can be used to restart the system without a great loss of

data.

When clicking on the TMN OS window Action|––> SMF|––> Failure Managemernt option, the following
window is displayed:
Figure 94. Failure Management
9.2.5.1 Doing a snapshot
Selecting the menu item Workstation |––> Do a SnapShot the procedure starts and executes the snapshot
of the selected workstation. The same function can be activated using the button of the icon bar .
9.2.5.2 Save a snapshot on tape
The snapshot created with the precedent function can be saved on a tape to be used afterwards when
needed. Selecting the menu item OS–Snapshot |à Save on Tape the procedure starts and saves the snap-
shot of the workstation tape device. The same function can be activated using the button of the icon bar
. A check on the existence of a tape device is done before the copy operation, if the tape device
doesn’t exist, a message is displayed.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 126 / 280
280
9.2.5.3 Delete a snapshot
The snapshot created with the precedent function can be deleted when it is no more useful. Selecting the
menu item OS–Snapshot |à Delete the procedure deletes the snapshot on the server. The same function
can be activated using the button of the icon bar . A confirmation window will be displayed before
the snapshot is deleted.
9.2.5.4 Lock and unlock a snapshot
The snapshot created with the precedent function can be locked or unlocked on the server. Selecting the
menu item OS–Snapshot |à Lock or OS–Snapshot |à Unlock the procedure starts and locks or unlocks
the snapshot on the workstation server. The same function can be activated using the button of the icon
bar (lock) or (unlock).

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 127 / 280
280
9.2.5.5 Options
Selecting the menu item Options |à Set Maximum the following window will be displayed to set the maxi-
mum number of snapshot saved on the server. The “OK” button confirms the changes.

Figure 95. Snapshot Options
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 $DIR1353NM_<Instance_Number>/maintenance/failure/global/yyy-
ymmddhhmm.
– 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 clean–up
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
ED 01
3AL 89061 BA AA 128 / 280
280
9.3 Trace Management
All the users can access to this function, via the SMF, from any station.
9.3.1 Traces Management tools
The following table summarizes the tools provided to manage traces:
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 4. Trace Management: tools

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 129 / 280
280
9.3.2 Trace Management (User Interface)
Selecting a System Instance icon on the TMN–OSs menu and selecting the menu function Actions |––>
SMF Trace Management as shown in the following figure, the Trace File Management window will be dis-

played.

Figure 96. System Trace Management selection
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 130 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 97. SMF Trace File Management
280
3AL 89061 BA AA
131 / 280
9.3.2.1 Edit Trace Levels
From the Trace File Management window it is possible to edit the trace files’ levels selecting from the menu
Processes |––> Edit Trace Levels. For each trace file it is possible to select the appropriate trace level.

The following table gives the information traced according to the trace level specified:
Level Information
1 error statuses (raising, ignoring, clearing)
2 process events (init, shutdown, I/O)
3 process I/O dataflow
4 method calls and results
5 platform calls and results (system, SGBD, ...)
6 debugging
7 specific
Table 5. Trace Management: Trace levels

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 98. SMF Edit Trace Levels
ED 01
3AL 89061 BA AA 132 / 280
280
The default setting for trace level is the following:
TRACE_FILTERS
{
ALL
{
ALL 1 2 5
}
}
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.
When enabled, dataflow tracing (level 3), is issued, along with process events (level 2) in dedicated trace
files with extension .dataflow .
9.3.2.2 Trace Files static view
From the Trace File Management window it is possible to view the selected trace file selecting from the
menu Trace File |––> Static View. This view displays the actual content of the selected trace file.
9.3.2.3 Trace files dynamic view
From the Trace File Management window it is possible to view the selected trace file dynamically selecting
from the menu Trace File |––> Dynamic View. This view displays the content of the selected trace file,
changing due to system’s activity.
9.3.2.4 Reset Traces
From the Trace File Management window it is possible to reset the selected trace file selecting from the
menu Trace File |––> Reset Traces. This selection clears the selected trace file.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 133 / 280
280
9.3.3 PMC Trace and Log Management
The trace and log files can be displayed also starting from PMC (Process Monitoring and Control) menu.
The agent should be selected before selecting the view function to activate the list of trace and log files.

This operation is possible only as administrator.

Figure 99. Trace and Log files selection from PMC

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 134 / 280
280
The list of trace and log files is displayed.
Figure 100. Agent Trace and Log files list
Confirming the selection with <OK> button will display the selected file in dynamic way that is the file dis-
played is dynamically updated.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 101. Trace file from PMC
ED 01
3AL 89061 BA AA 135 / 280
280
<Total> button allows reloading the trace file selected in static view.
<Start> button allows the start of the trace on the selected file.

<Stop> button allows to stop this operation.

<Close> button closes this window.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 136 / 280
280
9.4 Cleanup
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.
9.4.1 General
The safety of 1353NM 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.
N.B. The cleanup task concerns also the databases for alarm, maps, perfs.
9.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/Systems/1353NM_<Instance_Number>/backup, /usr/Sys-
tems/1353NM_<Instance_Number>/restore, /tmp/restorediff, /usr/Sys-
tems/1353NM_<Instance_Number>/maintenance/backup.
– Log files
Concerns the PM–logfile, the.old log files, and all the.log files under save, located in /usr/Sys-
tems/1353NM_<Instance_Number>/maintenance/log on a station.
– System log files

Concerns the directories located on /usr/Systems/1353NM_<Instance_Number>/maintenance/
failure on a station.
– Ossnapshot
Concerns all the files, except the axinstallGui, located in /usr/Systems/1353NM_<Instance_Num-
ber>/maintenance/failure/global on a station.
– Trace
Concerns all the files.trace,.err and.dataflow in the 1353NM run time tree of a station.
– Other Trace
– Core
Concerns all the core files on a station : core of NM processes within /usr/Sys-
tems/1353NM_<Instance_Number>/maintenance/core, and core resulting of panic unix error
within /var/adm/crash.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– EFD
Concerns all the files for EFD domain.
ED 01
3AL 89061 BA AA 137 / 280
280
– Temp Files
9.4.3 Cleanup (User Interface)

Cleanup function is an SMF function and is reached from TMN OS menu following Actions ––> SMF click-
ing on the Cleanup Management option, the following window is displayed:
Figure 102. Cleanup

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 138 / 280
280
Before starting a cleanup action, the operator can get more informations about the files to delete:
9.4.3.1 Cleanup – Details

Select the domain(s), select eventually the station(s), and select from menu bar Cleanup ––> Details or
select the icon
to get the complete list of files for the stations.
N.B. To select workstations, use the All and Clear push–buttons to select or deselect all domains
(respectively).
Figure 103. Cleanup – Details
Click on Close button to close and return to main window.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 139 / 280
280
9.4.3.2 Cleanup – Clean
To perform the cleanup action, select the domain(s), select one station, and select from menu bar Cleanup
––> Clean or select the icon.

N.B. If no domain and/or no station is selected, a dialogue box is displayed to remind the operator
what to select.
Figure 104. Cleanup – Clean – Error: No Selection
Figure 105. Cleanup – Clean – Confirmation
Click on Yes to confirm: starts the action.
Messages are displayed in the ’Message Area’.
9.4.4 Cron actions
Periodic tasks are defined into the configuration file /

usr/Systems/1353NM_x/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:
– removing of SEN performance files : files older than 3 days (for 15mn counter) and than 7 days (24h
counter) are removed
1AA 00014 0004 (9007) A4 – ALICE 04.10
– removing of Failure directory older than 1 month.

– removing of Historical alarms older than 90 days.
ED 01
3AL 89061 BA AA 140 / 280
280
10 BACKUP/RESTORE FEATURE
10.1 Overview
10.1.1 General
The backup/restore feature allows to save the applicative data of the 1353NM. This feature is not to be
confused with the full backup disks1353NM feature.
The backup/restore unit is defined by a couple (workstation, functional domains), each functional domains
can include several subsets of data types.
The functional domains are the following:
– Network (called Network):
• DNM data (saved Maps),

• NE configuration data (EMLIMs persistent data).
– Alarms files ,
– Operators (Users) (called Operator): home directory of the created and predefined 1353NM users.
– Logs (called Log),
– Performance Monitoring : the PM collection files,
– Software Download : Network Elements Software data files.
Some functional domains are only pertinent for the 1353NM master workstation.
The backup/restore feature copies tar files to or from the backup tree of the SMF master workstation.
N.B. Backup of one functional domain doesn’t remove existent backup of other differents functional
domains.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 141 / 280
280
10.2 Backup/Restore (User interface)
10.2.1 Access rights

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

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 142 / 280
280
10.2.2 User Interface
Selecting the 1353NM System Instance on the TMN OS window, selecting Actions |––> SMF Backup the
following window will be displayed to manage the backup jobs.
When clicking on the option, the following window is displayed.
Figure 106. Backup/Restore window
Backup To backup the data for OS,1353NM application
Restore To restore the data for OS,1353NM application
Table 7. Backup&Restore: Tools description

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 143 / 280
280
10.3 Backup Operations
Prerequisite:

– the backed up workstation is reachable,

– the state that will be backed up 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
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 144 / 280
280
10.3.1 Backup job creation
This function allows to create a new backup job, to activate the function select from the menu Job |––>
br_menu_new or the left button in the icon toolbar.
The backup job created can include all the files’ types or a subset. The possible subsets are :
– Alarms : hystorical data files,
– Log Files : system, commands and security log files,
– Network : persistency data files,
– Operators : operators definitions and configuration data files,
– Performance Monitoring : PM database,
– Software Download : Network Elements Software data files,
– System Configuration : process configuration data files.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 145 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 107. Backup job creation
280
3AL 89061 BA AA
146 / 280
Data to be inserted in the Backup window :
– Job Name : name to be assigned to the backup job,

– Subsystems/Domains/Subdomains select–button: selection of the data to be inserted in the bac-
kup job.
– Destination select–button : to choose the destination of the backup , Disk only or Disk & Tape.
– Server Name : server name for backup data.
– Comment : allows to add a comment to the created backup job.
– Compression select–button: to select the compression option.
– Apply push–button: to create the configured backup job.
– Close push–button: to close the window.
The functional domains to be included in the new backup job have to be selected first before transferring
information in the ”To Backup” list box.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 147 / 280
280
10.4 Restore Operations
Selecting the System Instance on the TMNOSs window, selecting Actions | ––> SMF Restore the following
window will be displayed to manage the restore jobs.

Figure 108. Restore window
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 148 / 280
280
10.4.1 Load Backup to Restore
In the Restore window, the Load Backups menu (see figure Figure 109. ) allows the administrator to visu-
alize the backups stored on the disk of the Backup/Restore server and/or on the tape connected to this
server.
Load Backups
All
From Disk
From Tape
Figure 109. Load Backups Menu
By using this menu the administrator can display the list of the backups stored:
– All or icon bar button
– From disk or icon bar button
– From tape or icon bar button
The result of the request is displayed in the Backup List of the Restore window.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 149 / 280
280
10.4.2 Selected backup Management
Selecting a backup set from the displayed list, the following actions can be performed :

– Status : displays a window with the backup set status, can be activated from the menu Backup |––>

Status or by the icon bar button
– Restore : displays a window on which the backup set components are listed, the components to be
restored can be selected; can be activated from the menu Backup |––> Restore or by the icon bar
button
– Delete : deletes the selected backup set; can be activated from the menu Backup |––> Delete or by
the icon bar button
Figure 110. Warning window for exclusive data type
Warning: Unix functional domain can not be restored.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 150 / 280
280
11 SYSTEM DATA MANAGEMENT
These tools were developed to give the operator the facilities for NE management. The access to this tool
is starting from TMN OS menu Actions |––> 1353NMAdmin, the selection window will be dispalyed as
shown hereafter :
Figure 111. System Management Menu
11.1 Access rights
The following table shows the access rights for the different User Profiles. As you can see, a viewer user
is not allowed to use the SMF Local Data Management functionalities.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 151 / 280
280
SMF Command Access rights Function in smfSH applica-
tion FAD
Diagnostic of audit of the MIB admin, constructor and operator DiagMib

Display SEN MIB admin, constructor and operator SENMIBView
NECTAS Decoding admin NECTASDec
NECTAS Comparison admin, constructor and operator NECTASCmp
Upload failure Diagnosis admin, constructor and operator UPFailDiag
Enable RPS Switch admin, constructor and operator RPSSwitch
Software download manager admin SwdManCfg

configuration
Software download server confi- admin SwdServCfg

guration
OMSN SWP Marging Tool admin SwdSwpMT
Save TP admin and constructor SaveTP
Restart Perf Collect admin and constructor RestartPerf
Overhead byte Configuration admin OverByteCfg
LAPD Configuration admin LAPDCfg
Change ASAP admin ChgASAP
Sync Source Selection admin SyncSrcSel
Address Configuration admin AddrCfg
Change Assigned To Observed admin and constructor ChgAssignObs
Change Free or Observed To As- admin and constructor ChgFreeObsAssign

signed
Switch Old/New Practice admin and constructor SwOldNewPract
Set Offline Board admin and constructor SetBoardOffline
Upgrade Offline Board admin and constructor UpgradeBoardOffLine
Set Offline SignalLabel admin and constructor SetSignalLabelOffLine
Ping NE admin, constructor and operator PingNE
List Gateway NE admin, constructor and operator ListGNE
DXC TCP–IP Address Configu- admin wx_ipconf

rations
1AA 00014 0004 (9007) A4 – ALICE 04.10
Change user label format admin ulformat
Table 8. Local data management: access right for different User Profiles
ED 01
3AL 89061 BA AA 152 / 280
280
11.2 Overview
11.2.1 Interface
In order to give an ergonomic access to the tools, for most of them a common user interface has been
developed : it allows the operator to choose a particular NE among all the QB3* ones (Figure 112. ); only
the window title and the action button differ depending on the required function.
Figure 112. Common interface
The following components are available in order to display a filtered NE list:
– Ne Family: set filter on the NE family: adm, sub, sgm, mw, ...
only the families of the created NEs are shown in the family list; dafault: all families.
– Ne Type button: set filter on the NE type
only the types of the created NEs are shown in the type list; default: all types.
– User Label text field: allows to define a string that has to be a substring of the User Label.
– Filter button: applies the filter criterium.
Once displayed the filtered list, you can select a particular NE clicking on it.
Click on Quit (or Cancel) to exit.
Click on the action button (or OK) to apply the required function.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 153 / 280
280
11.2.2 Constraints
Some functions needs to stop and restart the whole system or the EMLIM process managing the con-
cerned NE.

11.2.3 User Interface parameters
The colors and fonts used by the user interface are defined in a specific file called preferences.wish under
1353NM/conf.
They can be updated only with Unix commands.
11.3 Data Mangement – Configuration
The following described functions are actived from TMN OS Actions ––> 1353NMAdmin ––> Data Mana-
gement ––> Configuration.
Figure 113. System Management selection

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 154 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 114. System Management Tools selection
280
3AL 89061 BA AA
155 / 280
11.3.1 Diagnosis of audit of the MIB
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 115. 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.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 156 / 280
280
Figure 116. MIBs differences
The following pull–down menus are available on the top left of the window.
File Search
Print Find...
Quit Clear
Figure 117. Pull–down menus of the MIBs differences window
– Click on the Print option of the File pull–down menu to print the file.
– Click on the Quit option of the File pull–down menu to close the window.
– Click on the Find... option of the Search pull–down menu to search an occurence.
• The following dialogue box opens:
Figure 118. Find dialogue box

1AA 00014 0004 (9007) A4 – ALICE 04.10
• 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).
ED 01
3AL 89061 BA AA 157 / 280
280
• Click on the Find push button.
• The found occurences appears in red colour with a highlighted square on the first one (see fig-
ure below).

Figure 119. 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 pull–down 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.
Restrictions : If several audits have been processed on one NE, only the later one will be taken into
account by the tool .
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 158 / 280
280
11.3.2 Display SEN MIB
N.B. 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 NM–IM 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 /usr/Systems/1353NM_<Instance_Number>/shared_data/mib. This
tool has to be used after a takeover also to diagnose misalignment.
Figure 120. Display SEN MIB
The information displayed concern the MIB part of connections. Some domains may be ’skipped’ if the
corresponding data don’t exist for the NE type, or in case of incoherence. All domains are skipped if the
NE is not NML assigned .
Figure 121. SEN MIB

1AA 00014 0004 (9007) A4 – ALICE 04.10
The possible operations by using the pull–down menus on the top left of the window are the same as for
the previous paragraph.
ED 01
3AL 89061 BA AA 159 / 280
280
11.3.3 Upload Failure Diagnosis

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 1353NM_<Instance_Number>/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 122. Upload Diagnosis Failure
Select the NE as given in paragraph 11.2.
The incoherencies are displayed in red colour to be easily visualized.
Figure 123. Upload Diagnosis Failure – Diagnosis

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 160 / 280
280
11.3.4 Enable RPS Switch
The Radio Protection Switching applies to microwave NEs. It enables alarms related to RPS status in
alarm criterion tables of the NE.
Figure 124. Enable RPS Switch
Select the NE (see paragraph 11.2) and click on Enable.
Figure 125. Enable RPS Switch – Result

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 161 / 280
280
11.3.5 Overhead byte Configuration
N.B. This chapter is applicable to QB3* NEs only. For Q3 NES the feature is managed by the EML
USM process. See the 1353NM 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 126. 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.
The following window is then displayed to configure the overhead bytes for the chosen NE.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 162 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 127. Overhead byte configuration
280
3AL 89061 BA AA
163 / 280
The user can select the Card and OH Byte (in the RSOH or MSOH) used for each functionnality to config-
ure. 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.

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 Pass–
Through option.
– the Pass–Through Channel part: configuration of the SOH nine pass–through channels,
– the Voice part: configuration of the order–wire channels (voice channels).
The phone number associated to the order–wire channels can also be configured by sliding the cursor.
The possible values are 1 to 99.
Click on OK to validate the configuration.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 164 / 280
280
11.3.6 LAPD Configuration
N.B. This chapter is applicable to QB3* NEs only. For Q3 NES the feature is managed by the EML
USM process. See the 1353NM operators Handbook for details.
This option allows the configuration of the Link Access Procedure (LAP) for a D Channel (LAPD).
Figure 128. LAPD configuration window
Select the NE as given in paragraph 11.2 to choose the NE on which the LAPD is to be configured.
The following window is then displayed to configure the LAPD for the chosen NE.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 165 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 129. LAPD configuration
280
3AL 89061 BA AA
166 / 280
For each STM–n aggregate or STM–n tributary boards of the NE, select:
– 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. NET-
WORK–NETWORK or USER–USER are not authorized.

Select the ethernet link between the OS and the NE. If the NE isn’t 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.
The ”L2 only parameter” option can be set to True or False. It shall be set when NM has to communicate
only to NEs pertaining to different areas with respect to the area of the NM 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.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 167 / 280
280
11.3.7 Change ASAP

This option allows the copy of the ASAP from one NE to another.

This function is actived from TMN OS Actions ––> 1353NMAdmin ––> Data Management ––> Configura-
tion. The following window will be displayed
Figure 130. System Management Tools selection

1AA 00014 0004 (9007) A4 – ALICE 04.10
When clicking on the option Change ASAP, the following window is displayed:
ED 01
3AL 89061 BA AA 168 / 280
280
Figure 131. Change ASAP window
– Select the Ne Family and NE Type then click on the Filter push–button.
N.B. To have the complete list of NEs, click on the Filter push–button.
– Select the NE source in the displayed list (see Figure 132. ).
Figure 132. Change ASAP window – NE source selection

1AA 00014 0004 (9007) A4 – ALICE 04.10
– Click on the Ok push–button: the following window is displayed showing that the ASAP table of the
selected NE (source) is retrieved.
ED 01
3AL 89061 BA AA 169 / 280
280
Figure 133. Change ASAP window – Getting ASAP tables
– As for the NE source, select the NE destination.
– Click on the Ok push–button: a window (see Figure 134. ) 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 134. Change ASAP window – Work in progress

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 170 / 280
280
11.3.8 Sync Source Selection
This tool allows to choose the synchronization source for an NE (only for ADMs and MWs).
The action can be applied on a particular NE only if its emlim has been previously stopped; after
restart, the changes are taken into account.
Figure 135. 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.
The following window opens (if the NE is a MW for example).
Figure 136. Sync Source Selection – Selecting the synchronization source

1AA 00014 0004 (9007) A4 – ALICE 04.10
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).
ED 01
3AL 89061 BA AA 171 / 280
280
Figure 137. 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.
Click on the Cancel push button to close the window without change.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 172 / 280
280
11.3.9 Address Configuration
Figure 138. Address Configuration
– Select the Ne Family and NE Type then click on the Filter push–button.
N.B. To have the complete list of NEs, click on the Filter push–button.
– Select the NE source in the displayed list (see Figure 139. ).

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 173 / 280
280
Figure 139. Address Configuration – NE source
– While running, an intermediate window is displayed.
Figure 140. Address Configuration – Initialisation on going
Then the Address window is displayed.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 174 / 280
280
Figure 141. Address Configuration – Addresses setting
– 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 Switch–over: Yes or No. It allows (if set to Yes) an automatic switching from the OS main
address to the OS spare address.
• Auto Switch–back: 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.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 175 / 280
280
Change Assigned To Observed and Change Free or Observed To As-
11.3.10
signed

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).
N.B. There is no change for all the modifications of the configuration which had made the assign-
ment 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 142. Change assigned to observed window
N.B. The complete list of NEs (shown above) is displayed only after clicking on ”Filter”.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
During the Change state operation, information are displayed in the list box (see Figure 143. ).
ED 01
3AL 89061 BA AA 176 / 280
280
Figure 143. Change state operation running
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.
Restrictions : Available for ADM only.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 177 / 280
280
11.3.11 Switch Old/New Practice

This option allows the operator to change the name of the emlim persistency file during a migration phase.

Figure 144. 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.
The following confirmation window is then displayed:.
Figure 145. Switch Old/New Practice confirmation window

1AA 00014 0004 (9007) A4 – ALICE 04.10
Click on the Yes or No push button to confirm or cancel the switching.
ED 01
3AL 89061 BA AA 178 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
shown in the figure below :
11.4 Performance Operations
280
3AL 89061 BA AA
These Performance operations are activated from the menu Performance from Data Management as
179 / 280
11.4.1 Save TP
N.B. This chapter is applicable to QB3* NEs only. In Q3 NE management the EMLIM process man-
age 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_label_TP.dat in
the directory /usr/Systems/1353NM_<Instance_Number>/data (Instance_Number is the number of
the customization of 1353NM System). 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 146. Save TP
Select the NE (see paragraph 11.2) and click on Save.
N.B. restart_NE_label_TP.dat files are backupped when a Network Backup is required.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 180 / 280
280
11.4.2 Restart Perf Collect

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 147. Restart Perf Collect
Select the NE (see paragraph 11.2) and click on Restart.
The list of TPs currently started is recalled.
Figure 148. Restart Perf Collect – Result

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 181 / 280
280
11.5 NECTAS
The NECTAS functions can be reached from TMN OS ––> 1353NMAdmin as shown in following figure

Figure 149. NECTAS functions selection
11.5.1 NECTAS Decoding
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 modifica-
tions 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 double–click on its icon .The first win-
dow displayed allows the operator to select the user label of the NE. Only one selection is possible.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 182 / 280
280
Figure 150. NECTAS Decoding
– 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 push–button: The correct result of this functionality is to display a window showing the decoded
NECTAS files
– The button GoTo Table allows to link directly to the wanted table.
– The button Quit closes the window.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 151. NECTAS Decoding – Show
ED 01
3AL 89061 BA AA 183 / 280
280
Edit : The correct result of this functionality is to display a window showing the decoded NECTAS files

Figure 152. NECTAS Decoding – Edit
– The button Save re–writes the file even if no modification has been done.
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 de-
coded NECTAS files on the file used by the EMLIM process.
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 :
– Decoded file does not exist : this means that the tool does not find any NECTAS file to encode, in
1AA 00014 0004 (9007) A4 – ALICE 04.10
its working directory, for the selected NE.

– Another message giving an information from PersBrowser in case of failure during the encoding op-
eration.
ED 01
3AL 89061 BA AA 184 / 280
280
11.5.2 NECTAS Comparison

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 153. NECTAS Comparison (first NE)
– Click on OK to select the first NE.
Figure 154. NECTAS Comparison (second NE)
– Click on OK to select the second NE.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 185 / 280
280
If the tool has correctly run, 2 cases may occur:
a) There are no differences between the NECTAS tables of the 2 NEs.

Figure 155. NECTAS Comparison – Result (no differences)
b) There are some differences between the NECTAS tables of the 2 NEs, a window showing these dif-
ferences 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.
Figure 156. NECTAS Comparison – Differences displayed
• 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:
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 186 / 280
280
Figure 157. NECTAS Comparison – File saving
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.
So some applications as 254 , 255 , also called demy tables and relative to OS attributes , are not taken
into account.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 187 / 280
280
11.6 EQUIPMENT
This function accesses some actions on equipments. Starting from TMN OS ––> 1353NMAdmin the fol-
lowing steps leed to the desired function

Figure 158. System Management – Equipment
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 188 / 280
280
11.6.1 Set offline board
This option runs an offline tool which modifies the NE persistency file without involving the related emlim
process; the action can be applied on a particular NE only if its emlim has been previously stopped;
after restart, the changes are taken into account. This tool allows to substitute an aggregate board without
de–assign ports from 1354RM; it is applicable to:
• 1651sm / smop 2.4 / 2.5

• 1661smc / smcop 1.4 / 1.5
• 1664sm 2.1
Figure 159. Set Offline Board

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 189 / 280
280
11.6.2 Upgrade Offline Board

after restart, the changes are taken into account. This function applies to 1664sm 2.1 only, allowing to up-

date a tributary board to its UP version.
Figure 160. Upgrade Offline Board

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 190 / 280
280
11.6.3 Set offline signal label
after restart, the changes are taken into account. This function applies to:
• 1641sm/smop 2.7
• 1651sm/smop 2.5
• 1661smc/smcop 1.5
Figure 161. Set Offline Signal Label

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 191 / 280
280
11.7 NE Administration
This group of functions can be reached startin from TMN OS ––> 1353NMAdmin as shown in following
figure

Figure 162. System Management – NE Administration

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 192 / 280
280
11.7.1 SW Package Administration
This tool allows to select a valid SDH NE software package and to merge it with a Specific–Service pack-
age (ATM, IP, ...) obtaining a compound software package (SDH+Specific–Services) called OMSN pack-
age. The software package built by this tool can be used by the Software Download procedure to load a
OMSN NE.
11.7.1.1 Creation of an OMSN package
The SDH panel lists all the SDH packages installed on NM by the SRVADMIN tool:
Figure 163. SDH software package panel
The SERV. SPEC. panel lists all available Specific–Service packages installed by SRVADMIN tool:
Figure 164. SERV. SPEC. panel

1AA 00014 0004 (9007) A4 – ALICE 04.10
In order to build a new OMSN package the following steps have to be done.
ED 01
3AL 89061 BA AA 193 / 280
280
In the SDH panel (Figure 163. ), select one SDH package and then press ”Create OMSN”. A full copy of
the SDH package is prepared. When the copy operation is over, a question dialog pops up:

Figure 165. Successful creation OMSN package window
Clicking on “YES” button the OMSN panel appears. Otherwise pressing “NO” button you will be left in the
SDH panel, and you will have to switch to OMSN panel manually. Opening OMSN panel the cloned OMSN
package is displayed on the left. Selecting the OMSN package the compatible add–ons are shown on the
right.
Figure 166. OMSN package panel
Selecting the desired compatible add–on the “Add” button is enabled. Press the “Add” button to plug the
selected Service–Specific software package in the OMSN package. After the operation is completed, the
Service–Specific package is reported as ”Installed” (in the OMSN package) in the right–side list.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 194 / 280
280
Figure 167. OMSN package panel
If an installed software package is selected in the right–side list, the “Remove” button is enabled, making
it possible to unplug it from the OMSN package. Clicking on “Remove” button the following window pops
up:
Figure 168. Remove Service–Specific package panel
Clicking on “Yes” button the Specific–Service package is removed.
Note that all packages (SDH, Specific–Service and OMSN), can all be discarded by entering the appropri-
ate panel, selecting the desired item, and pressing on ”Discard” button. The screenshot below refers to
a discard operation on a software package. A confirm request is always displayed before proceeding.
Figure 169. Discard package panel

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 195 / 280
280
11.7.2 List Gateway NE
This tool allows the administrator to make a note of which NEs are working as gateways inside a DCN
structure.

This function is managed by OS–Kernel application, the platform on which 1353NM 7.0 is built. To have

an exhaustive description of the function see document “1350 System Rel. 7.0 Administration Guide”.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 170. List Gateway NE Wizard
ED 01
3AL 89061 BA AA 196 / 280
280
11.8 Ping NE
This option is used to test the reachability of NEs. This function is managed by OS–Kernel application, the
platform on which 1353NM 7.0 is built. To have an exhaustive description of the function see document
“1350 System Rel. 7.0 Administration Guide”.

The function can be accessed from the menu represented in the figure below :
Figure 171. NE Administration menu
Selecting Ping NE the following window will be displayed

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 197 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 172. Ping NE
280
3AL 89061 BA AA
198 / 280
11.8.1 IP Tunneling configuration
11.8.1.1 Introduction
An IP tunnel for OSi traffic is a point–to–point IP channel used to carry OSI data.
OSI–over–IP tunnels are used to allow the communication between NM and NEs using an IP network,
despite the fact that an OSI networking would be normally required to manage Alcatel equipment.
The same applies to NEs supporting such feature.
The concept of OSI–over–IP tunnels is specular with respect to IP–over–OSI tunnels by which, for exam-
ple, the ISA boards, SNMP/UPD/IP protocol based and hosted by OMSNs, can be managed through the
OSI network.
In OSI–over–IP tunnels, OSI packets are encapsulated into IP packets in order to be able to be carried
and routed to destination through a pure IP network. An OSI–over–IP tunnel provides a point–to–point link
between two OSI stations using a virtual IP pipe.
In a network context OSI–over–IP tunnels can be used to:
– interconnect the NM to a Gateway NE through an IP network. In this case the connectivity is provided
also with all the NEs reachable from this GNE (using OSI protocol)
– interconnect two NEs each other, e.g one of them being located at customer premises and not being
reachable via DCCs
– interconnect the NM to a Router through an IP network. In this case NM will be able to manage all
the NEs reachable via that router using OSI protocol
– interconnect the GNE to a Router through an IP network. In this case taht router will have networking
visibility of all the NEs reachable via that GNE using OSI protocol.
– protect an existing OSI DCN via an axisting IP network.
On the NM you can define up to 32 OSI–over–IP tunnels per Ethernet interface.
A NE supporting OSI–over–IP is configurable via EMLUSM in order to define up to 6 OSI–over–IP tunnels,

sharing the same IP address of its Ethernet interface.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 199 / 280
280
11.8.1.2 The IP Tunnel Configuration Tool
The IP Tunnel Configuration tool, available on the master workstation from TMN OS menu Actions
|––>1353NMAdmin interface, allows the system administrator to define IP tunnels between 1353NM and

several tunnel endpoints on the network.

Figure 173. IP Tunneling function selection
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 200 / 280
280
11.8.1.3 Main window
Selecting System Management –> NE Administration –> IP tunneling , the IP Tunnel Configuration Ap-
plication window is opened:
Figure 174. IP Tunnel Configuration Application window
The main window can be divided into two sections:
– the Status section contains a sequence of 32 buttons per Supervision Area (i.e. 32 buttons for each
Ethernet interface); each button represents an IP channel; the colour of a channel button is
• grey if the relative IP channel is not allocated
• orange if the channel endpoint is being connected
• green if the channel endpoint is successfully connected
Clicking on a channel button the relevant ’IP Tunnel Detail’ window (described in 11.8.1.6 ) is dis-
played.
– the Actions section has 5 buttons:

• Create to create an IP tunnel
• Delete to delete an IP tunnel
• Show List to list the whole channel list
• Export to create a a data for off–line management
• List GNE to open the GNE Wizard tool
• Quit to exit the tool.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 201 / 280
280
11.8.1.4 Creating an IP tunnel
Pressing the Create button in the main window, the Create IP Tunnel window is displayed:

Figure 175. Create IP Tunnel window
– in the From section you select the channel startpoint among the Ethernet cards configured on the
NM (i.e. the relevant Supervision Area);
– in the To section you have to define the channel endpoint; two choices are given:
• choosing a GNE by its label;

only GNEs defined via the List Gateway NE tool along with their IP address are listed
• specifying the IP address directly.
Press the Create button to start the creation procedure of the channel; the colour of the channel button
in the main window changes as the state of the communication evolves; if the endpoint is reached, the
following message is displayed:
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 176. IP tunnel successful creation message
ED 01
3AL 89061 BA AA 202 / 280
280
11.8.1.5 Listing IP tunnels
Pressing the Show List button in the main window, the IP Tunnel List window is displayed:
Figure 177. IP Tunnel List window
For each channel of each Supervision Area, the window gives :

– status :
• active if connected
• progress if being connected
• undefined if not allocated (i.e. not created)
– GNE label (if the channel endpoint is chosen among GNEs)
– IP address.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 203 / 280
280
11.8.1.6 Showing IP tunnel details
Pressing a channel button in the main window or in the IP Tunnel List window, the IP Tunnel Detail window
is opened:

Figure 178. IP Tunnel Detail window
The following data are showed:

1AA 00014 0004 (9007) A4 – ALICE 04.10
– channel startpoint : Supervision Area, IP Tunnel identifier

– channel endpoint : GNE Label Name (if declared as GNE), IP address anyway
– channel status : active / progress / undefined.
ED 01
3AL 89061 BA AA 204 / 280
280
11.8.1.7 Deleting an IP tunnel
There are two ways of deleting an IP channel :

– press the Delete button in the relevant IP Tunnel Detail window

or
– press the Delete button in the main window to open the Delete IP Tunnel window
Figure 179. Delete IP Tunnel window
– select the channel to be deleted (only created channel are listed)

– press the Delete button in the Delete IP Tunnel window.
11.8.1.8 Exporting IP tunneling data
The IP Tunneling application may exports data for off–line management. Data are exported by means of
a file in CSV (Comma Separated Values) format.
The export file (/usr/Systems/1353NM_<Instance_number>/necom/tunneling/data/itc.csv) is created on

pressing the Export button in the main window.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 205 / 280
280
11.8.2 On Board Simulator Monitoring
This function allows the operator to know which On Board Simulator (OBS) processes are currently run-
ning on the master workstations.

By default, only one OBS process can be launched at a time; if you want to increase the number of OBS
processes running simultaneously, you have to:
– modify the MAX_NUMBER_OF_INSTANCIABLE_SIMULATORS parameter in /usr/Sys-
tems/1353NM_x/simulator/simcon/data/param.cfg; the parameter value must be suitably set ac-
cording to the system resources;
– stop/start simcon process.
Selecting On Board Simulator Monitoring on the System Management menu, the following window will
appear:
Figure 180. On Board Simulator Monitoring window
The figure above shows that no OBS process is currently running on the master WS.
If one or more OBS processes are started when the OBS Monitoring window is already displayed, the win-
dow is not automatically updated; it is necessary to click on the Refresh button (Figure 181. ).
If there are OBS processes active (green arrow), clicking on the WS icon, for each simulated NE the follow-
ing information is displayed (Figure 182. ):
– NE name, type & release
1AA 00014 0004 (9007) A4 – ALICE 04.10
– emlim name
– NE group & Id
ED 01
3AL 89061 BA AA 206 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
280
3AL 89061 BA AA
Click on the Exit button to exit from the On Board Simulator monitoring window.
207 / 280
11.9 DXC TCP–IP Address Configuration
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 183. 1641SX TCP–IP Address Configuration
The results of adding a Lower and Upper Au IP address is to update the /etc/hosts of the master worksta-
tion with a conventional name and address added in this window for each AU.
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
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 208 / 280
280
12 PERIODIC ACTIONS (SMF SCHEDULER)
12.1 Overview
This functionality allows the administrator to manage periodic actions or run a script or procedure.
Selecting from the menu bar Actions |––> SMF Scheduler Management the following window will be dis-
played to manage the scheduling jobs. From the Scheduler window a new plan can be created or an exist-
ing plan can be modified, validate or deleted.
Figure 184. SMF Scheduler

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 209 / 280
280
12.1.1 Access rights
Only the administrators (admin group) can access to these tools, from the Master station.

Create a scheduled plan admin , on Master station
Edit scheduled plan admin , on Master station
Stop a scheduled plan admin , on Master station
Remove a scheduled plan admin , on Master station
Table 9. Periodic Options: Access rights

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 210 / 280
280
12.2 Scheduler plan creation
This function allows to create a new scheduler plan, to activate it select from the menu Plan |––> New plan
or the left button in the icon toolbar. The following window is displayed :
Figure 185. SMF Scheduler : Create New Plan

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 211 / 280
280
– Assign a name to the new scheduler plan.
– Select a command in the Command list; possible commands are :

1) Periodic Action Tester

2) Backup ALL job
3) Backup Network job
4) Backup AS job
5) Backup PM job
6) Backup Software Download job
7) Backup Log Management job
8) Backup System Configuration job
9) Backup Operator job
10 ) Purge Database
– Insert start date and start time.
– Insert stop date and stop time.
– Select the Repeat delay, if desired; then insert the periodicity interval.
– Click on the Apply push button if the inserted values are correct.
– Click on the Close push button to exit.
12.3 Scheduler plan edit
This function allows to modify an already existing scheduler plan. The window is the same used for the
plan creation. To activate the edit function select from the menu Plan |––> Edit plan or the second button
on the icon toolbar.
12.4 Scheduler plan validate
To validate the selected plan select from the menu Plan |––> Valid plan or the third button in the icon tool-
bar.
12.5 Scheduler plan stop
A scheduler plan can be stopped. To activate the stop function select from the menu Plan |––> Stop plan
or the fourth button in the icon toolbar.
12.6 Scheduler plan delete
A scheduler plan can be deleted. To activate the delete function select from the menu Plan |––> Delete
plan or the right button in the icon toolbar. A confirmation window appears before running the command.
– Click on the Ok push button to confirm the deletion.

– Click on the Close push button to exit.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 212 / 280
280
13 SMF FOR DXC
This chapter should provide the description of System Management Functions for OMSG NEs (cross–on-
nects) and will be added in next version of this document.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 213 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
280
3AL 89061 BA AA
214 / 280
14 NETWORK TIME PROTOCOL
14.1 NTP Overview

The Network Time Protocol (NTP) is a family of programs used to adjust the system clock on a computer
and keep it synchronized with external sources of time.
There are several time distribution mechanisms available :
a) Public time server (phone or modem) via the internet
b) Local clock impersonators
c) Radio receiver terrestrial and satellite broadcast
A good tip is to select a time server that is physically nearby, because the synchronization will otherwise
take too much time to be achieved. A possibility is also to have a node belonging to the local network that
is itself the time source for the other network nodes. This configuration is not so recommended because
it is possible that the synchronization would not be precise coming from an internal machine.
14.1.1 NTP implementation
NTP has the ability to continually keep a server or workstation’s time in sync with Coordinated Universal
Time (UTC).
NTP is a tiered time distribution system with redundancy capability. NTP measures delays within the net-
work 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 Net-
work 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 select-
ing 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 215 / 280
280
14.1.2 Stratum Level and Time Server Hierarchy
The NTP synchronization subnet is a network of timekeeping systems, called time servers. Each time ser-
ver synchronizes to Universal Coordinated Time (UTC). The servers are automatically assigned stratum

values, which indicates how close the time server is to the time source.

a) Stratum–1 Time Server : directly connected to an external time source;
b) Stratum–2 and Stratum–3 Time Servers : Stratum–2 Time Server uses Stratum–1 servers as their
source. Likewise, stratum–3 servers use stratum–2 server as their sources.
The maximum stratum level allowed is 15.

NTP Time Server can assume different roles in its relationship with other time servers in the synchroniza-
tion subnet:
a) Server : provides time to clients when requested (time servers at various strata can assume the role).
b) Peer : obtains time from a specified server and provides time to that server, if requested (Stratum–1
and Stratum–2 servers).
c) Client : obtains time from a specified server but does not provide time to that server.
d) Broadcast : provides time to the specified remote host.
e) Broadcast Client : listen for and synchronizes to broadcast time.
Every NTP hierarchy has at least one stratum–1 server.
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 serv-
ers 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 216 / 280
280
14.1.3 NTP daemon and configuration file
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 Coordi-
nated Universal Time or UTC.

The xntpd program is a daemon which maintains a UNIX system’s time–of–day 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 oper-
ate 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 host’s 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 time–related information about the hosts with which they are communicat-
ing. To configure your host this way, include a peer statement in your host’s 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 multi-
cast 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 cli-
ent yes statement or a multicast client yes statement in your host’s configuration file. For this
mode to function, the local time servers must be configured in broadcast mode with the broad-
cast configuration statement or in multicast mode with the multicast configuration statement.
A general guideline is to configure all hosts, except those at the highest strata of the synchronization sub-
net (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 broad-
cast client mode. You should consider opting for broadcast client mode if your hosts are on a high–speed
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 ac-
1AA 00014 0004 (9007) A4 – ALICE 04.10
tive mode (to poll hosts at lower strata).

Take this large introduction as a general explanation on NTP. The next chapter shows how a configuration
should be done in details.
ED 01
3AL 89061 BA AA 217 / 280
280
14.1.4 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 relative-
ly small amounts during the course of continued operation. Because xntpd needs a good estimate to syn-
chronize closely to its server, there should always be a driftfile entry.
14.1.5 Other options
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 approxi-
mately 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 syn-
chronized 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 out-
going 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.
– 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 authentica-
tion 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 address–and–mask 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 in-
coming 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 entry’s 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– statistics: enable writing statistic records.
ED 01
3AL 89061 BA AA 218 / 280
280
14.1.6 Synchronization schemes and reference principles in OS Configuration
Stated that any of the above mentioned approaches could apply in a TMN, the suggested architecture for
implementing time synchronization in 1300NM is explained hereafter.
The idea is to provide two possible time sources, a primary and a secondary. The nodes belonging to the
network managing the network management system could optionally be connected to the external time
source.
For the synchronization operation the following parameters are requested :
a) · Primary node
b) · Secondary node (optional)
c) · Access key
The access key is required for security problems. The access from external time server is regularized with
access keys to avoid access from unauthorized machines.
These data are stored in the NTP configuration file.
NTP has at its disposal an authentication mechanism. This mechanism helps protect against unauthorized
accesses to time servers. Once enabled on a system, authentication applies to all NTP relationships con-
figured on the system.
As the load on the hosts supporting NTP primary (stratum 1) time service is heavy and always increasing,
clients should avoid using the primary servers whenever possible. The NTP configuration should provide
a Stratum–1 server that is connected to the external time source; the other nodes are connected as Stra-
tum–2 and Stratum–3 servers.
The synchronization time is long, so change should be reduced to the necessary operations.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 219 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 186. NTP synchronization network
280
3AL 89061 BA AA
220 / 280
14.2 Synchronize the clocks
The clock synchronization is mandatory for system working together with Kerberos authentica-
tion tool, to do it the Network Timing Protocol (NTP) specified by RFC 1305.
Before proceeding with the NTP configuration you must have a clear picture of the configuration among
the involved machines, it is advisable prepare a ”time distribution plan” taking in account the following
rules:
a) The primary time sources have to be reliable ones, such as a Global Position System (GPS) receiver
time source.
b) Define two or three time–server machines. Each time–server should be a peer with of the other time–
servers.
c) Do not synchronize multiple time–servers to the same outside source. If it possible
For example in a network with two GPS receivers and five nodes, with the following rules:
– host _b and host_d configured with: 1353NM and 1354RM co–hosted with 1359HA OS–Resilience.
– host_a, host_c and host_e preform the presentation function for the resilient servers.
The resilient hosts plus a presentation (host_c) can be configured to receive the time from the GPS re-
ceives, and swap the time among themselves. All the other servers in the network (host_a and host_e)
have to be configured to receive the time from the host_b, host_c e host_d.
GPS
GPS Receiver 1 GPS Receiver 2

IP 192.202.21.51 IP 192.202.22.20
WAN WAN
host_a host_c
IP 192.200.49.1 host_b IP 192.202.21.8 host_d host_e
IP 192.202.21.7 IP 192.202.22.4 IP 192.202.22.5
Figure 187. NTP Configuration Example

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 221 / 280
280
To obtain such configuration the three servers host_b, host_c and host_d have to declare the two GSP
Receivers as NTP servers, moreover that can declare the other ones as peers, the resulting configuration
will be:

host_b

server GSPReceiver1 prefer
server GSPReceiver2
peer host_c
peer host_d
host_c
server GSPReceiver2
peer host_b
peer host_d
host_d
server GSPReceiver1
peer host_b
peer host_c
The “prefer” attribute distinguish the preferred source, this source it is usually the most reliable and also
the nearest one.
The remaining servers can retrieve the time from the other ones, here after the configuration:
host_a
server host_b prefer
server host_c
server host_d
host_e
server host_b
server host_c
server host_d prefer
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 222 / 280
280
To get the NTP configuration easier the “scxntp” script is provided.
To start “scxntp” script, log into the system as root user and enter: scxntp [Enter]
========================================================================
OS–Conf xntp Protocol Configuration

========================================================================
1 – Add new NTP server
2 – Add new NTP peer
3 – Remove NTP server
4 – Remove NTP peer
5 – Configure NTP on local clock
6 – Show NTP configuration
7 – Show NTP status
8 – Start/Stop NTP server
9 – Align the time to server
e or q – for exit
Insert choice and press [Enter]:
To simplify the explanation, the procedure shows how to configure the server host_b and host_a of
Figure 187. at page 221. Note, the configuration order is revival for the system behavior, it is better to start
configuring the nodes more close to the Timeservers.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 223 / 280
280
14.2.1 Configure host_b
This is the procedure using scxntp script to configure the host_b of Figure 187. at page 221.

a) Login host_b as root user.

b) Start the scxntp script by entering: scxntp [Enter]
c) Define the preferred timeserver:

Insert choice and press [Enter]: 1
Enter server hostname or IP address or q for Quit : 192.202.21.51
NOTE: Checking the configuration ...
Would you like to set 192.202.21.51 as preferred (y/n) ? y
NOTE: Updating /etc/ntp.conf adding server 192.202.21.51 ...
NOTE: Setting 192.202.21.51 timeserver for synchronize at boot
time
Press return to continue ...
d) Define the secondary timeserver:

Would you like to set 192.202.22.20 as preferred (y/n) ? n
e) For each peer hosts enter:

NOTE: Updating /etc/ntp.conf adding peer 192.202.21.8 ...
f) Check the NTP configuration:

Insert choice and press [Enter]: 6Configure host
NTP configuration
server 192.202.21.51 version 3 prefer

server 192.202.22.20 version 3
peer 192.202.21.8 version 3
peer 192.202.22.4 version 3
g) Start the NTP Daemon, set–up the daemon automatic start at system startup, and synchronize the
host_b clock with the preferred server in one shot:
WARNING: The xntpd daemons it is not configure to start automati-
cally
Would you like to start xntpd automatically at reboot (y/n) ? y
NTP server is stop
1AA 00014 0004 (9007) A4 – ALICE 04.10
Would you like to start it (y/n) ?
ED 01
3AL 89061 BA AA 224 / 280
280
NOTE: Temporary setup xntpd autostart...
NOTE: Starting xntpd ...
4 Sep 18:33:01 ntpdate[14482]: step time server 151.98.45.29 off-
set –0.026898 sec
xntpd NOTE: Reset the setup xntpd autostart...

h) Leave script by entering “e” or “q”.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 225 / 280
280
14.2.2 Configure host_a
This is the procedure using scxntp script to configure the host_a of Figure 187. at page 221.

a) Login host_a as root user.

b) Start the scxntp script by entering: scxntp [Enter]
c) Define the preferred timeserver:

Would you like to set 192.202.21.51 as preferred (y/n) ? y
NOTE: Setting 192.202.21.51 timeserver for synchronize at boot
time
d) Define the other two timeserver:

e) Check the NTP configuration:

NTP configuration
server 192.202.21.7 version 3 prefer

f) Start the NTP Daemon, set–up the daemon automatic start at system startup, and synchronize the
host_a clock with the preferred server in one shot:
WARNING: The xntpd daemons it is not configure to start automati-
cally
Would you like to start xntpd automatically at reboot (y/n) ? y
NTP server is stop
Would you like to start it (y/n) ?y
NOTE: Temporary setup xntpd autostart...
NOTE: Starting xntpd ...
4 Sep 18:33:01 ntpdate[14482]: step time server 151.98.45.29 off-
set –0.026898 sec
xntpd NOTE: Reset the setup xntpd autostart...
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 226 / 280
280
g) Leave script by entering “e” or “q”.
The script allows to manage the NTP configuration easy, you can add or/and delete servers and/or peers,
show the configuration, stop and start the NTP daemon, or align in one shot your system time to a specific
server.
Defining a NTP server the management script allows to specify the preferred one, it is discourage to define
more than one preferred server.
The NTP mechanism takes a long time to synchronize the machine with server.
The NTP daemon have to be stopped and started each time the configuration changes.
Usually the NTP daemon it is not running.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 227 / 280
280
14.2.3 Initial Clock Alignment
When a machine is installed for the first time, the clock it is not synchronized with any reference, the easiest
way to synchronize it with the other is by running “scxntp” script selecting the option N.9 “Align the time

to server”.

N.B. The time alignment is forbidden when NTP daemon is running.
To align the time you have to login the system as root user and start the script “scxntp” by entering:
...,sys,root# scxntp[Enter]
========================================================================
OS–Conf xntp Protocol Configuration
========================================================================
1 – Add new NTP server
2 – Add new NTP peer
3 – Remove NTP server
4 – Remove NTP peer
5 – Configure NTP on local clock
6 – Show NTP configuration
7 – Show NTP status
8 – Start/Stop NTP server
9 – Align the time to server
e or q – for exit
Insert choice and press [Enter]:
At the prompt enter “9[Enter]”
Enter server hostname or IP address or q for Quit :
The procedure will ask you to enter the IP address or Hostname of the timeserver, enter it and press [Enter]
key. The time will be aligned and shown.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 228 / 280
280
15 ALCATEL NETWORK TIME PROTOCOL
15.1 Overview
This section provides a brief explanation of ANTP (Alcatel Network Time Protocol) that is a protocol used
to synchronize time–keeping among a set of distributed time servers and clients.
15.1.1 ANTP behavior
ANTP is an Alcatel proprietary protocol which allows to have a very precise real time clock alignment be-
tween the NEs and a reference source (ANTP server). It is bases on the algorithm implemented by NTP
(see [2]) 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 client–server paradigm. The NE plays the role of the client while the ser-
ver is normally located on NM. 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 (NM). This mechanism allows to calculate
round trips delays and average statistical values to obtain the best real time alignment between client and
server.
15.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. It’s then up to native
NTP protocol to distribute the clock within the Operation Systems, getting the RTC from a GPS external
device (see Figure 188. ). 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 free–running. 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 co–located ANTP servers
(Figure 188. ) and with not co–located ANTP servers (Figure 189. ). The latter solution allows higher resil-
ience against any failure.
N.B. Refer to ANTP Functional Specification for protocol details: protocol architecture and ANTP
message format.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 229 / 280
280
ÎÎÎÎ
Î
ÎÎÎÎ
Î
OS1
ÎÎÎ
Î
Î ÎÎÎÎ
ÎÎÎ Î
OS2
ÎÎÎÎ
Î
OS3
Î
ÎÎÎ
ÎÎÎ
Î
OS4
ÎÎÎÎ ÎÎÎ ÎÎÎÎ ÎÎÎ

GPS
ÎÎ
ÎÎÎÎ
ÎÎ Î ÎÎÎ
Î
ÎÎÎÎ
ÎÎÎÎÎÎÎ
ÎÎ
ÎÎ Î ÎÎÎ
ÎÎÎ

clock source
NTP protocol
ANTP protocol
NE NE
NE NE
NE NE
NE NE
Figure 188. ANTP system architecture with co–located ANTP servers
ÎÎÎÎ
Î
ÎÎÎÎ
OS1
ÎÎÎ
Î
ÎÎÎ
Î ÎÎÎÎ
Î
OS2
ÎÎÎÎ
Î
OS3
Î
ÎÎÎ
ÎÎÎ
Î
OS4
GPS
ÎÎÎÎ ÎÎÎ ÎÎÎÎ ÎÎÎ
ÎÎ
ÎÎÎÎ
ÎÎ Î ÎÎÎÎÎÎÎÎ
ÎÎÎÎ ÎÎ
ÎÎ Î ÎÎÎ
ÎÎÎ
clock source
NTP protocol
ANTP protocol
NE NE
NE NE
NE NE
NE NE
ÎÎÎÎ
Î
OS5
ÎÎÎÎ
ÎÎ
ÎÎÎÎ
ÎÎ Î
GPS
clock source
ANTP protocol
NTP protocol
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 189. ANTP system architecture with not co–located ANTP servers
ED 01
3AL 89061 BA AA 230 / 280
280
16 PROCEDURES
The procedure sheets are divided as follow:

– Preventive maintenance
– Corrective maintenance
– Failure management
– Maintenance operations
– Upload failure
– Advanced network management
– Troubleshooting
16.1 Preventive Maintenance
The Preventive Maintenance sheets are the following:
– Power supply failure

– File system full
– Hardware failures
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 231 / 280
280
POWER SUPPLY FAILURE
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).
– Keep track of changes.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 232 / 280
280
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 PMC tool.
• Use of the Cleanup tool (refer to System Trace & Log Management chapter).
N.B. The cleaning up has to be performed as often as possible without delay.
N.B. For any doubt, contact the ALCATEL support.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 233 / 280
280
HARDWARE FAILURE

– Against disk crash, avoid shocks and power supply failures.
– Against SCSI errors, especially for an external disk, never unplug a SCSI cable while NM is running.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 234 / 280
280
16.2 Corrective Maintenance
The Corrective Maintenance sheets are the following:

– Power supply failure

– File system full

– Hardware failure – Disk crash
– Hardware failure – SCSI error
– Software failure – Panic Unix
– Software failure – Application bug
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 235 / 280
280
POWER SUPPLY FAILURE
Risks and symptoms

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

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 236 / 280
280
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 NM system console.
– As soon as the failure is detected, stop the NM Instance.
– Perform cleanup operations in SMF:
• In Actions ––> SMF menu, select the Cleanup Management option.
• Select the worstations and the domain for which the cleanup is necessary.
• The directories likely to grow are the following:

– /usr/Systems/1353NM_<Instance_Number>/maintenance/trace
– /usr/Systems/1353NM_<Instance_Number>/maintenance/failure/global
– /usr/Systems/1353NM_<Instance_Number>/data/perf/save
– /usr/Systems/1353NM_<Instance_Number>/as/data/ascurim/histDB
– If the damages are too important:
• restore the system entirely (Full Restore operation),
• restore the network data,
• perform a consistency check.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 237 / 280
280
HARDWARE FAILURE – Disk crash
Risks and symptoms

– Fatal to the system.
– 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.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 238 / 280
280
HARDWARE FAILURE – SCSI errors
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:
• Restore the system entirely (Full Restore operation).
• Restore the network data.
• Perform a consistency check.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 239 / 280
280
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.
– Send the core file to the ALCATEL/HP support.
– Remove it with the SMF cleanup function.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 240 / 280
280
SOFTWARE FAILURE – Application bug
Risks and symptoms

An NM process managed by PMC tool does not run.
– NM process crash is automatically detected by PMC tool.

– Traces and core files are automatically collected and saved in a
/usr/Systems/1353NM_<Instance_Number>/maintenance/failure directory
(where <Instance_Number> is the instance number of the customized 1353NM System) .
– Lock the failure directory.
– Backup it to disk (compressed tar).
– Save it on a tape.
– Send tape to ALCATEL support.
N.B. The compressed tar may be also transferred by ftp to Alcatel support.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 241 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
16.3 Failure management
The Failure Management sheet is the following:
Failure management – Step by step procedure
280
3AL 89061 BA AA
242 / 280
FAILURE MANAGEMENT – Step by step procedure
Operations
The operator can use:
– SMF:
• Select the Failure Management option.
• In the Main Menu of the Failure Management window, select the Manage Failure Directory
option.
• Click on Workstation ––> Do a Snapshot .
• Select the last snapshot in the list and click on menu OS–Snapshot ––> Save on tape.
– the remote maintenance
– UNIX:
• The failures are on each machine in /usr/Systems/1353NM_<Instance_Number>/mainte-

nance/failure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 243 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
–
–
–
ED
01
Power off one machine
Power off the whole OS
16.4 Maintenance operations
Change network area of a workstation

The Maintenance Operations sheets are the following:
280
3AL 89061 BA AA
244 / 280
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.
– Click on the Ok push button.
• with UNIX:
see paragraph Workstation shutdown or powerup
– Power off the machine.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 245 / 280
280
CHANGE NETWORK AREA OF A WORKSTATION
Operations

– Stop the supervision of managed NEs.
– Stop the NM manager.
– Run from TMN OS menu OS ––> SystemConfig option.
– Change the network area of the worstation (see paragraph System Configuration /Retixt Stack Con-
figuration).
– Select the Update Config option in the Main pull down menu.
– Change the OS address (area) of previously managed NEs:
• either with the Craft Terminal.
• or with the Address Configuration option of Actions ––> 1353NMAdmin ––> Data Manage-
ment ––> Configuration menu in TMN OS.
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 NM manager.
– Supervise and audit NEs.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 246 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
–
–
–
ED
01
16.5 Upload failures
Minor inconsistencies
Major inconsistencies – On NE side
Major inconsistencies – From OS side
The Upload Failures sheets are the following:
280
3AL 89061 BA AA
247 / 280
MINOR INCONSISTENCIES
Symptoms

– NE is supervised.
– Warning message says ”Updated Tables”.
Operations
– Perform a MIB Compare to get differences.
– Check NM updates.
– Perform more changes if needed.
– Align down.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 248 / 280
280
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 Actions ––> 1353NMAdmin ––> Data Manage-
ment ––> Configuration menu in TMN OS (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.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 249 / 280
280
MAJOR INCONSISTENCIES RECOVERY – From OS side
Operations

– Perform a MIB audit.
– Use the Diagnostic of audit of the MIB option in SMF (see paragraph Local data management / Diag-
nostic of audit of the MIB option).
– Using the list of differences:
• Change the NM 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.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 250 / 280
280
16.6 Advanced network management
The Advanced Network Management sheets are the following:

– Testing reachability
– Default configuration recovery

– Change assigned to observed
– Miscellaneous configurations
Migrated SH31 NEs : change NE name
– QB3* NEs NML assigned: change NEs name
– Q3 NEs NML assigned: change NEs name
– PM purge
– Changing from 256 to 16 millions colors for HP–B2000
– Q3 NE names with more than 32 characters
– OMSG NEs managed by 1354NP
– First Login Password Change & Enable/Disable Password Expiration mechanism
– ISA board rename after error
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 251 / 280
280
TESTING REACHABILITY
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 mainte-
nance.
– Transport layer
• Perform an OSI ping to check any OSI transport connection:
– In SMF:
• Perform the Ping NE option of Actions ––> 1353NMAdmin ––> NE Administra-

tion menu in TMN OS menu.
– by UNIX:
• Run the script: /usr/Systems/1353NM_<Instance_number>/necom/axNE-

diag.ptk.
– Advanced Diagnosis
• nettl wrapper to analyse network packets (run_capture).

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 252 / 280
280
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:
• 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 253 / 280
280
CHANGE ASSIGNED TO OBSERVED
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.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 254 / 280
280
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 by-
tes.
– From Unix:
• NE batch creation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 255 / 280
280
Migrated SH31 NEs : “Change NE name”
The NE label migration tool can be used on SH5 platforms for changing the user label of NEs migrated

from SH31 platforms.
Installation
1) Copy the file 1353SH5_SH31CHNAME.sdpkg on the directory /alcatel/DEPOT
2) Login as root and install the package by the command:
...,root# swinstall –s /alcatel/DEPOT/1353SH5_SH31CHNAME.sdpkg ’*’
Operations
3) Login as axadmin and create a corrispondence file (migr.map):
...,axadmin# vi /tmp/migr.map
Example of migr.map:
––––––––––––––––––––
OLD_NAME_ADM1 NEW_NAME_ADM1
OLD_NAME_ADM2 NEW_NAME_ADM2
............. .............
N.B. One blank character must separate the old NE name from the new one
4) Change directory:
...,axadmin# cd /alcatel/1353NM/tools/migration/userlabel
5) Make an inventory of NEs to migrate:
...,axadmin# ./migrUserlabel.pl –inventory –mapping /tmp/migr.map > /tmp/migr.inventory
5) Make a backup of persistency files:
...,axadmin# ./migrUserlabel.pl –backup –group <emlim groupid number>
6) Repeat the step 5) for all emlimadmnr31_<groupid number>
7) Stop all the emlimadmnr31 processes created via SMF:
Administration –> System Management –> Process monitoring
8) Migrate the persistency file:
...,axadmin# ./migrUserlabel.pl –migrate –persistency –mapping /tmp/migr.map –group <emlim groupid

number>
9) Repeat the step 8) for all emlimadmnr31 processes

1AA 00014 0004 (9007) A4 – ALICE 04.10
10) Start all the emlimadmnr31 processes created via SMF:
ED 01
3AL 89061 BA AA 256 / 280
280
11) Close all maps on PNM
12) Stop the PNMIM process via SMF:


13) Remove the NE.db file:
...,axadmin# rm /alcatel/1353NM/pnm/data/NE.db
14) Start the PNMIM process via SMF:
15) Migrate the thirdfiles:
...,axadmin# ./migrUserlabel.pl –migrate –thirdfiles –mapping /tmp/migr.map –group <emlim’s groupid

number>
16) Open the maps on PNM and check that NE names changed according to the step 3).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 257 / 280
280
QB3* NEs NML assigned: “Change NE name”
Operations

In order to change the NE name of a QB3* NE in a NML assigned state the following steps must be per-
formed:
– From SMF, in the Process Monitoring dialog menu:
• stop related Qb3* Emlim process (see managed NEs section in delivery notes document )
– 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
• select the NE
• select stop supervision in the Supervision menu
– 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;
• start related Qb3* Emlim process;
– From PNM USM interface:
• select the NE
• select start supervision in the Supervision menu;
– The NE will return in supervisioned state.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 258 / 280
280
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:
• start supervision of the specific NE.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 259 / 280
280
PM PURGE
Prerequisites

– MySQL process running
Manual purge
It is possible to discard consecutive records (15 min or 1 day) within a specified time interval as follows:
• login as alcatel
• cd /usr/Systems/1353NM_<Instance_number>/pm/pmv/script/
• ./pm_purge “<Starting_Time>” “<Ending_Time>” 15min
or
• ./pm_purge “<Starting_Time>” “<Ending_Time>” 1day
having <Starting_Time> and <Ending_Time> the format YYYY/MM/DD hh:mm:ss (Year/Month/

Day hour:minute:second).
The command pm_purge “<Starting_Time>” “<Ending_Time>” 1day deletes all the PM 1day records
whose midnight Mj falls into the specified interval as follows:
• Starting_Time <= Mj < Ending_Time
Examples:
./pm_purge “2001/10/11 05:00:00” “2001/10/11 10:30:00” 15min
./pm_purge “2001/10/11 00:00:00” “2001/10/27 00:30:00” 1day
The Starting_Time and the Ending_Time must be converted to GMT.
Therefore, if the current local time is (GMT + GMT_local_offset) then the values
<Starting_Time> = Starting_local_Time – GMT_ local_offset
and
<Ending_Time> = Ending_local_Time – GMT_local_offset
must be used.
Automatic purge
– It is possible to discard automatically and periodically all PM data older than a specific time interval:
• edit the file /usr/Systems/1353NM_<Instance_number>/pm/pmv/script/set_variable and set

the time interval:
Example:
[15 minutes]
Sec 00 [00..60]
Min 00 [00..60]
1AA 00014 0004 (9007) A4 – ALICE 04.10
Hour 00 [00..24]
Day 2 [0..31] ==> Older than 2 day
Month 0 [0..12]
ED 01
3AL 89061 BA AA 260 / 280
280
Year 0 [0..15]
[1 day]
Sec 00 [00..60]
Min 00 [00..60]
Hour 00 [00..24]
Day 0 [0..31]
Month 3 [0..12] ==> Older than 3 months
Year 0 [0..15]
• Login as root and add in the crontab file the line which defines the purge frequency (you can
digit man crontab for help about usage):
...,root#crontab –e root
Example:
0 1 * * * /usr/Systems/1353NM_x/script/axcleanup –oldonly –local –dt Failure

0 0 * * * /usr/Systems/1353NM_x/script/axcleanup –oldonly –local –dt SenPerf
0 2 * * * /usr/Systems/1353NM_x/script/axcleanup –oldonly –local –dt HistDB
45 22 * * 1 /usr/Systems/1353NM_x/pm/pmv/script/axpurge
• Verify the crontab file:
...,root# crontab –l
PM database Reset
By one of the following procedures, all PM data are deleted.
Procedure 1
• Login as axadmin
• ...,axadmin# stop process perfstorage
• ...,axadmin# stop process pm_database
• ...,axadmin# rm –rf /usr/Systems/1353NM_<Instance_number>/pm/pmdb/data
• ...,axadmin# restart process perfstorage
• ...,axadmin# restart process pm_database

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 261 / 280
280
CHANGING FROM 256 TO 16 MILLIONS COLORS FOR HP–B2000
Operations

– Log in as root and change the rights to X0screens file:
• ...,root# chmod u+w /etc/X11/X0screens
– Edit the X0screens file adding at the end the following row:
• DefaultVisual Class TrueColor Depth 24 Layer Image
– Search the X process path:
• ...,root# which X
– Use the output of previous command to kill the X process:
• ...,root# fuser –k <full X process path>
– Log in again.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 262 / 280
280
Q3 NE NAME with MORE THAN 32 CHARACTERS
Q3 NE name has a default maximum length of 32 characters. If you need to increase this value, for any
reason, following procedure comes in handy:
Operations
On NM master :
– stop all Q3 emlims
– in /usr/Systems/1353NM_<Instance_number>/eml/adm/admq3nr5/conf/param.cfg
and in
– in /usr/Systems/1353NM_<Instance_number>/eml/dxc/dxcq3nr5/conf/param.cfg
modify as follows
USER_LABEL_LENGTH <new value> (e.g. 50 instead of 32)
– restart all Q3 emlims
On all ws (SH/RM, master/presentation) :
– exit PNM USM
– in /usr/Systems/1353NM_<Instance_number>/PNM/data/pnmusm/english/param.dbm
modify as follows
...
”&UserLabel_maxLength” 1
”english” ”<new value>” <–– change
...
– reopen PNM emlusm.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 263 / 280
280
First Login Password Change & Enable/Disable Password Expiration mechanism
By default the First Login Password Change and Expiration mechanism are not active.

You can make them active by modifying the file /usr/local/data/pwdExpiryAge.
By default pwdExpiryAge file contains 0 (no first login change request and no expiration date).
If you want to enable the expiration mechanism, the following procedure has to be applied :
– login as root
– cd /usr/local/data/
– modify pwdExpiryAge replacing the value 0 by the value <n> (greather than zero)
n being the expiry age in days.
Example:
the root modify the pwdExpiryAge file content with 30; the users, at first login or 30 days after latest
password change, are prompted with a message forcing password change:
“Expired Password – You must change it !”
The rules to follow to change passwords are described in Operator Handbook vol.1, chapter 6.2 Pas-
sword Expiration
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 264 / 280
280
ISA board rename after error
If the operator has made any error during the ISA board creation phase (wrong rack and/or subrack /and/or
slot position), by command line it is possible to rename manually the user label associated to the ISA
board.
This operation recovers from errors and, therefore, it shall not be used in the normal product life.
From the directory
/usr/Systems/1353NM_<Instance_number>/tools/operation/script/
launch the script
ATMmanager.pl –NERENAME <old name> <new name>

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 265 / 280
280
16.7 Troubleshooting
The Troubleshooting sheets are the following:

– Alarms not coming up

– NE can’t be managed
– Performance not displayed
– OS isolation
– Reproducing an applicative problem
– Not enough colours
– Customer site information
– Reporting an NM problem
– Using lan0 for managing nodes using RFC1006 feature
– RM/NM cohosted, create neGroup object first on RM and then on NM; create Tfep and then emlim.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 266 / 280
280
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 does not display the alarm:
• Perform a Supervision / Refresh NE states...:
• Restart PNMUSM to synchronize it with PNMIM:
• 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 can’t see EMLIM:
• Check processes are running.
• Check HPOV on EMLIM and PNMIM machines.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 267 / 280
280
ALARMS NOT COMING UP (Cont’d)
Study the ASUSM working:

– 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:
– If the new alarms are correctly displayed, it was a CPU congestion.
– If they are not displayed, it is an event routing problem.
• Restart ASIM to resynchronize it with EMLIM:
– If they are not displayed, it is an event routing problem.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 268 / 280
280
NE CAN’T 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 Topology Manager |––> Opera-
tions | Ping NE .
In case of misalignment or upload rejection:
– Use the Upload Failure Diagnosis option of the Local Data Management menu in SMF (see para-
graph Local Data Management / Upload Failure Diagnosis option).
In last resort:
– Send XCC and EMLIM traces to Alcatel support:
• Reset traces and reproduce to get relevant traces.
• Check it is the right EML machine.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 269 / 280
280
PERFORMANCES NOT DISPLAYED
In case of time out:

– It may be:
• Too many TPs to store.
• Perfstorage times out.
• Switches to off–line mode.
• Oracle database is down.
– Check the presence of files in /usr/Systems/1353NM_<Instance_number>/data/perf/save.
– Increase the PERF_PROCESS_LIFETIME in /usr/Systems/1353NM_<Instance_number>/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.
– In order to know what is happened, open /usr/Systems/1353NM_<Instance_num-

ber>/maintenance/log/PM–logfile which logs all actions with the Oracle database.
• NE bug...
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 270 / 280
280
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 chan-
ge.
Workaround: stop/start the supervision to update the icon.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 271 / 280
280
REPRODUCING AN APPLICATIVE PROBLEM
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 manage-
ment).
– Display the trace dynamically (see paragraph System trace & log management / Trace manage-
ment).
– Reproduce the problem.
– Dump screens if significant (see paragraph System trace & log management / Dump Screen).
– Check the trace relevancy:
• 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.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 272 / 280
280
NOT ENOUGH COLOURS
Probable causes:
Normally there is enough colours to operate NM, excepted maybe if:
– NM 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.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 273 / 280
280
CUSTOMER SITE INFORMATION
Informations to provide to Alcatel support:

– OS configuration:
• Hardware.
• Bootable tape version.
• NM 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 274 / 280
280
REPORTING AN NM PROBLEM
Informations to provide to Alcatel support:

– NM version:
• Output of axversion.
– OS configuration:
• Number and type of worstations.
• Contained in axconfig file.
– Type and version of NEs managed:
• Output of axdbread.
– Compressed tar of failure or simply relevant trace files.
– Screendumps.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 275 / 280
280
USE lan0 for managing nodes using RFC1006 feature
A WorkAround is described hereafter to allow stack running on lan0 IP Address different from 127.0.0.1.

The following describes how to modify some script files to allow stack running on lan0 IP address (different
than 127.0.0.1)
Files to modify ( some lines commented with ”#”) are:
– /alcatel/<OSK_version>/NMA/EMLIMADMQ3/<NMA_version>/templates/getRetixTag.pl (used to
start Q3 EMLIM)
– /alcatel/<OSK_version>/NMC/NECOM/<NMC_version>/script/retix_qb3s_lower_layer
– /alcatel/<OSK_version>/NMC/NECOM/<NMC_version>/script/retix_qb3s_upper_layer (used to
start Retix LL and Retix QB3* UL)
– /alcatel/<OSK_version>/NMC/NECOM/<NMC_version>/script/run_antpserver
– /alcatel/<OSK_version>/NMC/NECOM/<NMC_version>/script/run_ftclient
– /alcatel/<OSK_version>/NMC/NECOM/<NMC_version>/script/run_swdlserv (used to start FTser-

vices and ANTP server)
where :
<OSK_version> : is the OS–Kernel version
<NMC_version> : is the generic component version (e.g. NECOM)
<NMA_version> : is the application version (e.g.EMLIMADMQ3)
Please make a copy of the original files.
Modification are described as UNIX ”diff” command output:
a) diff getRetixTag.pl getRetixTag.pl.REF34c34
< #( $lan0addr eq $IPADDR ) && ($IPADDR=”127.0.0.1”);
–––
> ( $lan0addr eq $IPADDR ) && ($IPADDR=”127.0.0.1”);
b) diff retix_qb3s_lower_layer retix_qb3s_lower_layer.REF37,39c37,39
< # lan0addr=‘/etc/ifconfig lan0 | sed –n ’s/.*inet $[^ ]*$ .*/\1/p’‘
< # [ $2 = $lan0addr ] && multipleStack=””
< # [ $2 = $lan0addr ] && cp $OSCOREDIR/necom/conf/config_nmid_$1.txt
$OSCOREDIR/necom/conf/config.txt
1AA 00014 0004 (9007) A4 – ALICE 04.10
–––
> lan0addr=‘/etc/ifconfig lan0 | sed –n ’s/.*inet $[^ ]*$ .*/\1/p’‘
ED 01
3AL 89061 BA AA 276 / 280
280
> [ $2 = $lan0addr ] && multipleStack=””
> [ $2 = $lan0addr ] && cp $OSCOREDIR/necom/conf/config_nmid_$1.txt

$OSCOREDIR/necom/conf/config.txt
c) diff retix_qb3s_upper_layer retix_qb3s_upper_layer.REF51,52c51,52
< # lan0addr=‘/etc/ifconfig lan0 | sed –n ’s/.*inet $[^ ]*$ .*/\1/p’‘
< # [ $1 = $lan0addr ] && multipleStack=””
–––
d) diff run_antpserver run_antpserver.REF27,28c27,28
< #lan0addr=‘/etc/ifconfig lan0 | sed –n ’s/.*inet $[^ ]*$ .*/\1/p’‘
< #[ $1 = $lan0addr ] && multipleStack=””
–––
e) diff run_ftclient run_ftclient.REF18,19c18,19
–––
f) diff run_swdlserv run_swdlserv.REF19,20c19,20
–––
To apply modifications stop&restart stack, FTservices, ANTP server and emlims.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 277 / 280
280
RM/NM cohosted, create neGroup object first on RM and then on NM
A WorkAround is described hereafter to allow the correct behaviour of EMLIM Q3 for DXC (COMET

2.1.8.1) when NM System runs integrated with RM System.
In NR7 HP–OV has been substituted by EPIM. This application is in charge to send alarms from NM to
RM. When EMLIM starts on NM System, it creates EFD (object for managing events) to be managed by
EPIM.
EFD doesn‘t distinguish if the notification sent is for Q3 or QB3* neGroup objects, therefore sends two
notifications. If on RM the object is not yet created, then RM doesn‘t know the notification correspondance.
Having this restriction the following rule should be followed in case of integration of NM with RM :
– The object neGroup should be created on RM System first, then on NM System
– TFEP should be created before emlims.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
3AL 89061 BA AA 278 / 280
280
INDEX
A the General processes, 48

the Presentation processes, 48
ANTP, 229 the System, 48

the Workstation applications, 48
B
N
Backup Operations, 144
Backup software, 49, 51, 141 NECTAS Decoding, 182
C O
Change ASAP, 168 OMSN SWP Merging Tool, 193
Cleanup, 137
P
D
Ping NE, 197
Diagnostic of audit of the MIB, 156 PM PURGE, 260
Display SEN MIB, 159 Powerup, Workstation, 25
Presentation Process, Monitoring of, 48
Process Monitoring, 41
E
Enable RPS Switch, 161 R
Restart Perf Collect, 181

F Restore Operations, 148
Restore software, 141
Forced Logout, 211
S
G
Save TP, 180
General Process, Monitoring of, 48
Set offline board, 189
GPS, 229
Set offline signal label, 191
Shutdown, Workstation, 25
I SMF/Command/Event Logs Management/Visu-
alization, 95
IP tunneling, 199 Software
Backup, 49, 51, 141
Restore, 141
L
List Successful Login, 77, 78, 79 U

Local Data Management, 151
Upgrade Offline Board, 190
M
W
Maintenance, 231
1AA 00014 0004 (9007) A4 – ALICE 04.10
Corrective, 235, 242, 244, 247, 251, 266 Workstation

Preventive, 231 Powerup, 25
Monitoring Shutdown, 25
ED 01
3AL 89061 BA AA 279 / 280
280
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
END OF DOCUMENT
280
3AL 89061 BA AA
280 / 280
LABELS AND ASSEMBLY INSTRUCTIONS
TARGHETTE E INFORMAZIONI PER IL CENTRO STAMPA
QUESTA PAGINA NON VA INSERITA NEL MANUALE

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
COD.MANUALE HDBK P/N: 3AL 89061 BAAA Ed.01
1350NM
1353NM Rel.7.0
Version 7.0 ADMINISTRATION GUIDE
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)
– No PAGINE TOTALI PER ARCHIVIAZIONE: 282+4=286
– DIMENSIONE BINDER SORGENTE (du –ks):176.570 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 numerate
(facciate) numbered
No pages da from a to
TARGHETTE - LABELS
frontespizio
2
front
manuale
280 1/280 280/280
manual
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: 282
TOTALE FOGLI A4 TOTAL A4 SHEETS: 141
WARNING FOR A-UNITS OTHER THAN A-ITALY
• Labels are done according to A-Italy binder format.

• Source files: ALICE 6.10 ARCHIVED BY GAPI 4.1
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 RELEASED
3AL 89061 BAAA TQZZA Y 1/ 4
4
QUESTA PAGINA NON VA INSERITA NEL MANUALE
THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

Site
FCG
Originators 1353NM REL. 7.0

M.Armanini
VERSION 7.0
Domain : OND
Division : NM
Rubric : 1353NM
Type : 1353NM REL.7.0 ADMINISTRATION GUIDE
Distribution Codes Internal : External :
Approvals
Name V.Scortecci L.Foresta

App.
Name
App.
INFORMAZIONI EDITORIALI
– ORIGINALE SU FILE: ALICE 6.10

• sistemazione ’figlist’
3AL 89061 BAAA

Ed.01
1350NM
1353NM Rel.7.0
Version 7.0
Element mngt for Alcatel Optical / Radio transport networks

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 RELEASED
4
1350NM
1353NM Rel.7.0

VOL.1/1
1350NM
1353NM Rel.7.0
VOL.1/1
1350NM
1353NM Rel.7.0
3AL 89061 BAAA Ed.01 ADMINISTRATION GUIDE VOL.1/1
1350NM 1353NM Rel.7.0

1350NM
1353NM Rel.7.0

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 RELEASED
4
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
RELEASED
4
3AL 89061 BAAA TQZZA
Y
FINE DEL DOCUMENTO INTERNO – END OF INTERNAL DOCUMENT
4/ 4

1353NM Rel.7.0 Administration Guide PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

1353NM Rel.7.0 Administration Guide PDF

Caricato da

Copyright:

Formati disponibili

Administration Guide

3AL 89061 BAAA Ed.01

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

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

01 040416 M.BERTONI M.ARMANINI

01A 040128 M.BERTONI M.ARMANINI

ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

3AL 89061 BA AA 1 / 280

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

7 DISKS FULL BACKUP AND FULL RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

9 SYSTEM LOG MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

9.2.5 Failure Management (User Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

3AL 89061 BA AA 2 / 280

9.4.3 Cleanup (User Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

9.4.4 Cron actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

10 BACKUP/RESTORE FEATURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

11 SYSTEM DATA MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

11.8.1 IP Tunneling configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

3AL 89061 BA AA 3 / 280

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

13 SMF FOR DXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

14 NETWORK TIME PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

15 ALCATEL NETWORK TIME PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

3AL 89061 BA AA 4 / 280

Figure 1. Alcatel CDE Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Figure 2. TMN OS application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Figure 48. Session Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

3AL 89061 BA AA 5 / 280

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

Figure 101. Trace file from PMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

3AL 89061 BA AA 6 / 280

Figure 109. Load Backups Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Figure 110. Warning window for exclusive data type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Figure 155. NECTAS Comparison – Result (no differences) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

3AL 89061 BA AA 7 / 280

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

3AL 89061 BA AA 8 / 280

First archived version of the handbook

3AL 89061 AAAA

Network Time Protocol March 1992

ACA: Access Control Administration tool

ADM: Add and Drop Multiplexer

AIS: Alarm Indication Signal

LOS: Loss Of Signal

3AL 89061 BA AA 11 / 280

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

3AL 89061 BA AA 12 / 280

1.1 General information

1.2 Handbook applicability

This handbook applies to the following product-releases:

PRODUCT ANV P/N

PRODUCT RELEASE VERSION (N.B.) ANV P/N

N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

3AL 89061 BA AA 13 / 280

not permitted without written authorization from Alcatel.

1.3.1 Handbooks related to the specific software application

1.3.2 Handbooks related to the Network Release

1350NM 7.0 System Management