1353nm73 Ag Ed01 1

Alcatel 1350
Management Suite
1353NM
Rel. 7.3
7.3.6P9
Element manager for Alcatel optical & radio networks
Administration Guide
3AL 89082 BAAA Edition 01

Status: RELEASED
22 September 2006
All rights reserved.

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

TABLE OF CONTENTS
LIST OF FIGURES ........................................................................................................................... 5
LIST OF TABLES ............................................................................................................................. 9
PREFACE......................................................................................................................................... 11
Preliminary Information.............................................................................................................. 11
Applicability................................................................................................................................. 12
Scope ........................................................................................................................................... 12
History.......................................................................................................................................... 13
Related Documents .................................................................................................................... 13
Handbook Structure ................................................................................................................... 15
General on Customer Documentation ...................................................................................... 16
1 GENERALITIES ........................................................................................................................... 21
1.1 1353NM 7.3 news Overview ................................................................................................ 21
1.2 1353NM activation................................................................................................................ 22
1.3 Role of the Administrator.................................................................................................... 23
1.4 Document Conventions....................................................................................................... 24
2 RELEASE IDENTIFICATION ....................................................................................................... 25
3 CONFIGURATION........................................................................................................................ 29
3.1 Preparing 1353NM Configuration ....................................................................................... 29
3.2 Configure the Patch STYL on 1353NM............................................................................... 30
3.2.1 Patch STYL Procedure ................................................................................................... 30
3.2.2 System Configuration ..................................................................................................... 31
3.3 Change the IP configuration ............................................................................................... 32
3.4 1353NM IP Configuration .................................................................................................... 33
3.4.1 Routing Configuration ..................................................................................................... 33
3.4.2 Multi-Lan configuration ................................................................................................... 42
3.5 1353NM Configuration......................................................................................................... 44
3.5.1 System Tuning ................................................................................................................ 45
3.5.2 Configure specific NMAs ................................................................................................ 49
3.5.3 Configuring 1353NM Element Manager Layers of type SGM and MELOSNMP ............ 53
3.5.4 Configuring OSI GATEWAY ............................................................................................ 54
3.5.5 Execute the configuration ............................................................................................... 57
3.5.6 WA after System Configuration for MDR 8000 Rel.2.0 NEs Management ..................... 59
3.5.7 Removing a previously configured process from the Subsystem configuration ............. 59
3.6 1353NM Master and Client Integration............................................................................... 60
3.7 Process Monitoring ............................................................................................................. 61
3.7.1 Groups of Processes ...................................................................................................... 62
3.7.2 Run Levels...................................................................................................................... 65
4 USER MANAGEMENT................................................................................................................. 67
4.1 User Profiles Description .................................................................................................... 67
4.1.1 The Access control model .............................................................................................. 67
4.1.2 OADs and FADs ............................................................................................................. 71
4.1.3 Administrator, Operator, Viewer profiles configuration.................................................... 72
4.1.4 Constructor profile configuration ..................................................................................... 73
4.1.5 Default User Profiles ....................................................................................................... 74
4.1.6 Customizing User Profiles .............................................................................................. 75
4.1.7 An example of management of OAD, FAD, and OAD-FAD ............................................ 81
4.1.8 Creating new Profiles...................................................................................................... 89
4.2 Macro functionalities related to user profiles ................................................................... 91
Administration Guide 1353NM Rel. 7.3

Table of Contents 3AL 89082 BAAA Edition 01 1/270
5 BACKUP RESTORE FEATURE .................................................................................................. 101
5.1 Overview ............................................................................................................................... 101
5.1.1 Disks Full Backup and Full Restore ................................................................................ 101
5.1.2 General ........................................................................................................................... 101
5.1.3 Backup Performing Time ................................................................................................ 102
6 PERIODIC ACTIONS (SMF SCHEDULER) ................................................................................. 103

6.1 Overview ............................................................................................................................... 103
6.1.1 Access rights .................................................................................................................. 104
6.2 Scheduled actions ............................................................................................................... 104
6.3 Optional scheduled actions ................................................................................................ 104
7 SYSTEM LOG MANAGEMENT ................................................................................................... 105

7.1 SMF/Command/Event Logs Management/Visualization .................................................. 105
7.1.1 General ........................................................................................................................... 106
7.1.2 Management of log files.................................................................................................. 106
7.1.3 Access rights .................................................................................................................. 108
7.1.4 Log Tools ........................................................................................................................ 109
7.1.5 Log Management Files ................................................................................................... 110
7.2 Failure Management ............................................................................................................ 111
7.2.1 General ........................................................................................................................... 111
7.2.2 Fault Report Content ...................................................................................................... 111
7.2.3 Sequence of events when a process exits abnormally ................................................... 111
7.2.4 Failure Tools ................................................................................................................... 112
7.3 Trace Management............................................................................................................... 114
7.3.1 Traces Management tools .............................................................................................. 114
7.3.2 Traces Management files................................................................................................ 114
7.3.3 Trace Management (User Interface)............................................................................... 115
7.4 Command Log Viewer ......................................................................................................... 118
7.4.1 Parse Command Log ...................................................................................................... 118
7.4.2 Printing the selected record ............................................................................................ 132
7.5 Cleanup................................................................................................................................. 137
7.5.1 General ........................................................................................................................... 137
7.5.2 Cleanup tool.................................................................................................................... 137
7.5.3 Cleanup (User Interface) ................................................................................................ 138
7.5.4 Cron actions.................................................................................................................... 142
8 SYSTEM DATA MANAGEMENT ................................................................................................. 143

8.1 Access rights ....................................................................................................................... 144
8.2 Overview ............................................................................................................................... 145
8.2.1 Interface.......................................................................................................................... 145
8.2.2 Constraints...................................................................................................................... 145
8.2.3 User Interface parameters .............................................................................................. 145
8.3 Data Mangement - Configuration ....................................................................................... 146
8.3.1 Diagnosis of audit of the MIB .......................................................................................... 147
8.3.2 Display SEN MIB ............................................................................................................ 150
8.3.3 Upload Failure Diagnosis................................................................................................ 151
8.3.4 Enable RPS Switch......................................................................................................... 152
8.3.5 Overhead byte Configuration .......................................................................................... 153
8.3.6 LAPD Configuration ........................................................................................................ 156
8.3.7 Change ASAP................................................................................................................. 159
8.3.8 Sync Source Selection.................................................................................................... 161
8.3.9 Address Configuration .................................................................................................... 163
8.3.10 Change assignment state for QB3* NEs....................................................................... 166
8.3.11 Switch Old/New Practice............................................................................................... 168
1353NM Rel. 7.3 Administration Guide

2/270 3AL 89082 BAAA Edition 01 Table of Contents
8.4 Performance Operations ..................................................................................................... 169
8.4.1 Save TP .......................................................................................................................... 170
8.4.2 Restart Perf Collect......................................................................................................... 171
8.5 NECTAS ................................................................................................................................ 172
8.5.1 NECTAS Decoding ......................................................................................................... 172
8.5.2 NECTAS Comparison ..................................................................................................... 174
8.6 Equipment ............................................................................................................................ 178
8.6.1 Set offline board.............................................................................................................. 179
8.6.2 Upgrade Offline Board .................................................................................................... 180
8.6.3 Set offline signal label ..................................................................................................... 181
8.7 NE Administration................................................................................................................ 182
8.7.1 1615BCE Configuration .................................................................................................. 182
8.7.2 FT Scheduler .................................................................................................................. 182
8.7.3 SW Package Administration ........................................................................................... 182
8.7.4 List Gateway NE ............................................................................................................. 186
8.7.5 Ping NE........................................................................................................................... 187
8.7.6 AC Viewer ....................................................................................................................... 188
8.7.7 OSI over IP Tunneling..................................................................................................... 189
8.7.8 On Board Simulator Monitoring ...................................................................................... 195
8.7.9 Command Log Viewer .................................................................................................... 196
8.7.10 IP over OSI Tunneling................................................................................................... 196
9 SMF FOR OMSG.......................................................................................................................... 197
10 ALCATEL NETWORK TIME PROTOCOL................................................................................. 199

10.1 Overview ............................................................................................................................. 199
10.1.1 ANTP behaviour ........................................................................................................... 199
10.1.2 RTC distribution system architecture ............................................................................ 200
11 MAINTENANCE.......................................................................................................................... 203
11.1 Generalities......................................................................................................................... 204
11.2 Preventive Maintenance .................................................................................................... 205
11.3 Corrective Maintenance..................................................................................................... 209
11.4 Maintenance operations .................................................................................................... 216
12 TROUBLESHOOTING................................................................................................................ 225
13 PROCEDURES........................................................................................................................... 241
13.1 Failure management .......................................................................................................... 241
13.2 Upload failure ..................................................................................................................... 243
13.3 Advanced network management...................................................................................... 247
ABBREVIATIONS ............................................................................................................................ 263
INDEX ............................................................................................................................................... 267
CUSTOMER DOCUMENTATION FEEDBACK.............................................................................. 269

Table of Contents 3AL 89082 BAAA Edition 01 3/270
4/270 3AL 89082 BAAA Edition 01 Table of Contents
LIST OF FIGURES
Figure 1. Alcatel CDE Front Panel.................................................................................................... 22

Figure 2. TMN OS application........................................................................................................... 22
Figure 3. Example of typed unix shell commands. ........................................................................... 24
Figure 4. Example of the system response to the command date.................................................... 24
Figure 5. Subsystem Information ...................................................................................................... 25
Figure 6. 1353NM Subsystem Information ....................................................................................... 26
Figure 7. Sh_SubSystem Parameter Configuration window............................................................. 31
Figure 8. Example of network with ISA board................................................................................... 35
Figure 9. Systems without sharing LAN (case 1).............................................................................. 39
Figure 10. Systems without sharing LAN (case 2)............................................................................ 40
Figure 11. Systems without sharing LAN (case 3) ............................................................................ 41
Figure 12. 1353NM Warning Security Box........................................................................................ 44
Figure 13. Alcatel CDE Front Panel.................................................................................................. 44
Figure 14. TMN-OS Management Window....................................................................................... 44
Figure 15. 1353NM System configuration window............................................................................ 45
Figure 16. 1353NM Parameter Definition - Sh_SubSystem ............................................................. 47
Figure 17. 1353NM Parameter Definition - System_Tuning ............................................................. 47
Figure 18. 1353NM PMDS_DB_SubSystem .................................................................................... 47
Figure 19. 1353NM Parameter Definition -Q B3S_Simulator Set-up................................................ 48
Figure 20. Entity “System_Mgt_Functions" selection........................................................................ 48
Figure 21. 1353NM Necom SubSytem Configuration 1.................................................................... 49
Figure 22. 1353NM Necom SubSystem 2 ........................................................................................ 50
Figure 23. 1353NM Necom SubSystem 3 ........................................................................................ 50
Figure 24. 1353NM Antp................................................................................................................... 51
Figure 25. 1353NM FTServer and FTclient....................................................................................... 51
Figure 26. 1353NM Wrong Element manager identifier.................................................................... 52
Figure 27. 1353NM Element Manager - Retix Stack assignment ..................................................... 52
Figure 28. Configuring EMLIMSGM and EMLIMMELOSNMP.......................................................... 53
Figure 29. OSI Gateway Parameters definition ................................................................................ 54
Figure 30. OSI Gateway Parameters definition (cont.) ..................................................................... 55
Figure 31. 1353NM Configuration Warnings Window ....................................................................... 57
Figure 32. 1353NM Configuration Error and Warnings window........................................................ 58
Figure 33. 1353NM Configuration quit. ............................................................................................. 58
Figure 34. Process Monitoring Control Main Window....................................................................... 61
Figure 35. TMN OS SEC Administration activation .......................................................................... 68
Figure 36. System Mangement Menu to access SEC Administration .............................................. 68
Figure 37. System Mangement Menu to access SEC Browser ........................................................ 69
Figure 38. SEC USM Browser .......................................................................................................... 69
Figure 39. Application FAD relation .................................................................................................. 72
Figure 40. Pure constructor profile.................................................................................................... 73
Figure 41. Operator-constructor profile............................................................................................. 74
Figure 42. Object creation................................................................................................................. 75
Figure 43. Elementary OAD creation. ............................................................................................... 76
Figure 44. Create/Modify a new Application FAD ............................................................................. 77
Figure 45. Application FAD for user viewer....................................................................................... 78
Figure 46. OAD-FAD Combination creation...................................................................................... 80
Figure 47. Default Access Rights Definition for operator axadmin ................................................... 82
Figure 48. Modify the NE ACD value ................................................................................................ 83
Figure 49. Access Rights Definition of test with the OAD-FAD test_oadfad ..................................... 84
Figure 50. ACD creation ................................................................................................................... 85
Figure 51. Create a new Function Access Domain........................................................................... 86
Figure 52. Create a new SysFad ...................................................................................................... 87

List of Figures 3AL 89082 BAAA Edition 01 5/270
Figure 53. Create a new OAD-FAD .................................................................................................. 88
Figure 54. Create a new profile......................................................................................................... 89
Figure 55. Profiles in SMF-Create User............................................................................................ 90
Figure 56. SMF Scheduler ................................................................................................................ 103
Figure 57. System Log Management activation................................................................................ 105
Figure 58. Logs states ...................................................................................................................... 107
Figure 59. Snapshot Options ............................................................................................................ 113
Figure 60. System Trace Management selection.............................................................................. 115
Figure 61. Trace Management: Trace levels .................................................................................... 116
Figure 62. Trace Management: Trace levels setting ......................................................................... 116
Figure 63. Starting CLV ..................................................................................................................... 118
Figure 64. Starting CLV ..................................................................................................................... 118
Figure 65. Select Target Log File ...................................................................................................... 119
Figure 66. Simple Filter..................................................................................................................... 120
Figure 67. Advanced Filter................................................................................................................ 122
Figure 68. Selecting the subject........................................................................................................ 122
Figure 69. Selecting the relational operator ...................................................................................... 123
Figure 70. Selecting a value of comparison ...................................................................................... 123
Figure 71. Combining Logical Conditions ......................................................................................... 124
Figure 72. Temporary Filter............................................................................................................... 125
Figure 73. Selected Saved Filter....................................................................................................... 126
Figure 74. Extraction result ............................................................................................................... 127
Figure 75. Extraction result list.......................................................................................................... 128
Figure 76. Extraction result list's statistic information ....................................................................... 130
Figure 77. Detail information ............................................................................................................. 131
Figure 78. Print dialog....................................................................................................................... 132
Figure 79. Print preview window ....................................................................................................... 133
Figure 80. Export the selected command result list to text file.......................................................... 134
Figure 81. Export of the selected command record detailed info to text ........................................... 135
Figure 82. Display online help........................................................................................................... 135
Figure 83. Exit CLV confirmation dialog ............................................................................................ 136
Figure 84. Navigation to the Cleanup tool......................................................................................... 137
Figure 85. Cleanup ........................................................................................................................... 139
Figure 86. Cleanup - Details ............................................................................................................. 140
Figure 87. Cleanup - Clean - Error: No Selection ............................................................................. 141
Figure 88. Cleanup - Clean - Confirmation ....................................................................................... 141
Figure 89. System Management Menu............................................................................................. 143
Figure 90. Common interface ........................................................................................................... 145
Figure 91. System Management selection........................................................................................ 146
Figure 92. System Management Tools selection .............................................................................. 146
Figure 93. Diagnosis of audit of the MIB........................................................................................... 147
Figure 94. MIBs differences .............................................................................................................. 148
Figure 95. Pull-down menus of the MIBs differences window .......................................................... 148
Figure 96. Find dialogue box ............................................................................................................ 148
Figure 97. Searching occurences in the MIBs differences................................................................ 149
Figure 98. Display SEN MIB ............................................................................................................. 150
Figure 99. SEN MIB .......................................................................................................................... 150
Figure 100. Upload Diagnosis Failure............................................................................................... 151
Figure 101. Upload Diagnosis Failure - Diagnosis............................................................................ 151
Figure 102. Enable RPS Switch........................................................................................................ 152
Figure 103. Enable RPS Switch - Result .......................................................................................... 152
Figure 104. Overhead byte configuration option............................................................................... 153
Figure 105. Overhead byte configuration.......................................................................................... 154
Figure 106. LAPD configuration window........................................................................................... 156

6/270 3AL 89082 BAAA Edition 01 List of Figures
Figure 107. LAPD configuration........................................................................................................ 157
Figure 108. Change ASAP window................................................................................................... 159
Figure 109. Change ASAP window - NE source selection ............................................................... 160
Figure 110. Change ASAP window - Getting ASAP tables ............................................................... 160
Figure 111. Sync Source Selection - Choosing a NE........................................................................ 161
Figure 112. Sync Source Selection - Selecting the synchronization source ..................................... 161
Figure 113. Sync Source Selection - Choosing the SSU quality....................................................... 162
Figure 114. Address Configuration ................................................................................................... 163
Figure 115. Address Configuration - NE source ............................................................................... 164
Figure 116. Address Configuration - Initialisation on going............................................................... 164
Figure 117. Address Configuration - Addresses setting.................................................................... 165
Figure 118. Change assigned to observed window .......................................................................... 166
Figure 119. Change state operation running..................................................................................... 167
Figure 120. Switch Old/New Practice ............................................................................................... 168
Figure 121. Switch Old/New Practice confirmation window .............................................................. 168
Figure 122. Performance operations selection ................................................................................. 169
Figure 123. Save TP ......................................................................................................................... 170
Figure 124. Restart Perf Collect........................................................................................................ 171
Figure 125. Restart Perf Collect - Result .......................................................................................... 171
Figure 126. NECTAS functions selection .......................................................................................... 172
Figure 127. NECTAS Decoding ........................................................................................................ 172
Figure 128. NECTAS Decoding - Show ............................................................................................ 173
Figure 129. NECTAS Decoding - Edit ............................................................................................... 174
Figure 130. NECTAS Comparison (first NE) ..................................................................................... 175
Figure 131. NECTAS Comparison (second NE) ............................................................................... 175
Figure 132. NECTAS Comparison - Result (no differences)............................................................. 176
Figure 133. NECTAS Comparison - Differences displayed............................................................... 176
Figure 134. NECTAS Comparison - File saving................................................................................ 177
Figure 135. System Management - Equipment ................................................................................ 178
Figure 136. Set Offline Board ........................................................................................................... 179
Figure 137. Upgrade Offline Board ................................................................................................... 180
Figure 138. Set Offline Signal Label ................................................................................................. 181
Figure 139. System Management - NE Administration ..................................................................... 182
Figure 140. SDH software package panel ........................................................................................ 183
Figure 141. SERV. SPEC. panel ....................................................................................................... 184
Figure 142. Successful creation OMSN package window ................................................................ 184
Figure 143. OMSN package panel.................................................................................................... 185
Figure 144. List Gateway NE Wizard................................................................................................ 186
Figure 145. Ping NE.......................................................................................................................... 187
Figure 146. Ping NE result................................................................................................................ 188
Figure 147. IP Tunnel Configuration Application window.................................................................. 190
Figure 148. Create IP Tunnel window............................................................................................... 191
Figure 149. IP tunnel successful creation message ......................................................................... 191
Figure 150. IP Tunnel List window .................................................................................................... 192
Figure 151. IP Tunnel Detail window ................................................................................................ 193
Figure 152. Delete IP Tunnel window ............................................................................................... 194
Figure 153. On Board Simulator Monitoring window ........................................................................ 195
Figure 154. SMF functions for OMSG administration ....................................................................... 197
Figure 155. ANTP system architecture with co-located ANTP servers............................................. 201
Figure 156. ANTP system architecture with not co-located ANTP servers....................................... 202
Figure 157. PM DB Administration.................................................................................................... 219
Figure 158. PM Manual Purge Selection .......................................................................................... 220
Figure 159. Manual Purge on ATM database ................................................................................... 221
Figure 160. PM databases statistics ................................................................................................. 222

List of Figures 3AL 89082 BAAA Edition 01 7/270
Figure 161. Optimize operation on PM database ............................................................................. 223
Figure 162. Set Threshold for PM databases ................................................................................... 224

8/270 3AL 89082 BAAA Edition 01 List of Figures
LIST OF TABLES
Table 1. Handbooks related to the specific software application ...................................................... 13

Table 2. Handbooks related to the Network Release........................................................................ 14
Table 3. Handbooks for factory internal use only .............................................................................. 14
Table 4. Documentation on CD-ROM ............................................................................................... 14
Table 5. Groups of processes ........................................................................................................... 62
Table 6. Run levels............................................................................................................................ 65
Table 7. Periodic Options: Access rights........................................................................................... 104
Table 8. Log Management: Access rights for different User Profiles ................................................ 108
Table 9. Log Management Options ................................................................................................... 109
Table 10. Trace Management: tools.................................................................................................. 114
Table 11. Local data management: access right for different User Profiles ..................................... 144

List of Tables 3AL 89082 BAAA Edition 01 9/270
10/270 3AL 89082 BAAA Edition 01 List of Tables
PREFACE
Preliminary 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.
TECHNICAL SUPPORT
Please contact your Local Alcatel Technical Assistance Center for questions reffered to the infor-
mation contained in this document.
To send your comments about this handbook please follow the indication on Customer Documentatio
Feedback on page 269.

Preface 3AL 89082 BAAA Edition 01 11/270
Applicability
This handbook applies to following product–releases:
PRODUCT Part Number
1353NM 3AL 89052 AAAA
PRODUCT RELEASE VERSION (N.B.) Part Number
1353NM 7.3 7.3 3AL 89053 ACAA
N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

Handbooks relevant to software applications are not modified unless the new software "ver-
sion" distributed to Customers implies man-machine interface changes or in case of slight mod-
ifications not affecting the understanding of the explained procedures.
Moreover, should the screen prints included in the handbook contain the product–release's
"version" marking, they are not replaced in the handbooks related to a subsequent version, if
the screen contents are unchanged.
Scope
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.
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.

12/270 3AL 89082 BAAA Edition 01 Preface
History
EDITION DATE DESCRIPTIONS
01 September 2006 First validated and officially released issue of this Handbook
Related Documents
The list of handbooks given here below is valid on the issue date of this
Handbook and can be changed without any obligation for ALCATEL to
update it in this Handbook.
Some of the handbooks listed here below may not be available on the
issue date of this Handbook.
The standard Customer Documentation in the English language for the equipment whose product–
release–version is stated in “Applicability” on page 12 consists of the following handbooks:
Table 1. Handbooks related to the specific software application
REF HANDBOOK Part Number Notes
[1] 1353NM Rel.7.3

3AL 89082 AAAA
Operator's Handbook
[2] 1353NM Rel.7.3 THIS

3AL 89082 BAAA
Administration Guide HANDBOOK
[3] 1353NM NR5 Equipment Specific

3AL 89062 AAAA
Operator's Handbook
[4] 1353NM NE LIST Handbook 3AL 89063 AAAA
[5] PMDS 1.1 User's Guide 3AL 88875 AAAA
[6] 1330AS 6.5

3AL 88876 AAAA
Operator's Handbook
[7] ELB 2.X

3AL 88877 AAAA
Operator's Handbook
[8] CT/SH-DXC Operation Manuals set 3AL 74553 ADAA

(Administration) ....

Table 2. Handbooks related to the Network Release
[9] 1350 Rel.7.3

3AL 88915 BAAA
Installation Guide
[10] 1350 7.1 System Management

3AL 88874 AAAA
Operator's Handbook
Table 3. Handbooks for factory internal use only
[11] RFC 1305
Table 4. Documentation on CD-ROM
REF Documentation CD-ROM TITLE Part Number
1353NM Rel.7.3 CD-ROM-DOC EN 3AL 89084 AAAA
Contains handbooks REF.[1] to [7] in electronic format.

Tipically envisaged after the release of the handbooks.
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 (EMC)
– ELECTROSTATIC DISCHARGERS (ESD)
– EQUIPMENT LABELS
– DISMANTLING & RECYCLING

Handbook Structure
This handbook has been edited according to the Alcatel standardized “drawing-up guides" complying with
such suggestion.
This handbook is divided into the main topics described in the table of contents:
The technical contents of the document is mainly divided into two parts.
PREFACE: It contains general information as preliminary information, safety

recommendation, handbook scope, history, related documents.
Furthermore, it describes the handbook structure and the customer
documentation.
FIRST TECHNICAL PART
Services provided to the operator to manage the correct behaviuor of the customized subsystem
Generalities The 1353NM processes are briefly described and management ser-
vices offered to the system administrator are listed here (Role of the
administrator, System Management Notions, Defence Manage-
ment, Document Conventions)
Release Identification The information about the releases of components and applications
composing 1353NM subsystem are described here
Configuration The operations requested for configuring , launching and stopping
the 1353NM product are described here (System Configuration,
Process Monitoring)
User MANAGEMENT All facilities available for the system users management are
described here (User Profiles Description, Macro functionalities
related to user profiles)
BACKUP/RESTORE FEA- The operations necessary to backup and restore the 1353NM data
TURE are described here
Periodic Actions How to manage periodic scheduled actions is described in this sec-
tion
System Log MANAGEMENT Tools to control logs, to track failure and to control traces are
described in this section
System Data Management Tools for NEs management are described.
SMF for OMSG SMF for OMSG NEs management
Alcatel Network Time Proto- It describes how to configure ANTP features.
col
SECOND TECHNICAL PART
Maintenace
Maintenance Generalities General introduction about Preventive maintenance, Corrective
maintenance and Maintenance activity
TROUBLESHOOTING Detailed troubleshooting activities are defined
PROCEDURES It contains detailed procedures about Failure management, Upload
failure, Advanced network management
ABBREVIATIONS: The abbreviation list is supplied.
INDEX Index references are inserted
CUSTOMER DOCUMENTA- It contains info regarding customer opinions collection about this
TION FEEDBACK documentation.

General on Customer Documentation
Note: when Network Management Operator’s Handbook is made, other handbooks can refer to it.
A "product" is defined by the network hierarchical level where it can be inserted and by the whole of per-
formance and services for which it is meant.
A "product" evolves through successive "product–releases" which are the real products marketed for
their delivery at a certain "product–release" availability date.
So, a "product-release" defines a set of hardware components and a software package which, as a whole,
identify the possible network applications and the equipment performance which the specific "product–
release" has been designed, engineered and marketed for.
In some cases a "product–release" has further development steps, named "versions", that are born to
improve or add some performance (mainly software) with respect to the previous version, or for bug fixing
purposes.
A "product–release" has its own standard Customer Documentation, composed by one or more hand-
books.
A new "version" of a "product–release" may or may not produce a change in the status of the Customer
Documentation set, as described in “Handbook Updating” following part.
Handbook supply to Customers
Handbooks are not automatically delivered together with the equipment they refer to.
The number of handbooks per type to be supplied must be decided at contract level.
Aims of standard Customer Documentation
Standard Customer Documentation, referred to hereafter, must be always meant as plant–independent.

Plant–dependent documentation, if envisaged by the contract, is subjected to commercial criteria as far
as contents, formats and supply conditions are concerned (plant–dependent documentation is not
described here).
Standard hardware and software documentation is meant to give the Customer personnel the possibility
and the information necessary for installing, commissioning, operating and maintaining the equipment
according to Alcatel Laboratory design choices.
In particular: the contents of the handbooks associated to the software applications focus on the expla-
nation of the man–machine interface and of the operating procedures allowed by it; maintenance is
described down to faulty PCB location and replacement.
Consequently, no supply to the Customers of design documentation (like PCB hardware design and pro-
duction documents and files, software source programs, programming tools, etc.) is envisaged.
The handbooks concerning hardware (usually the "Technical Handbook") and software (usually the
"Operator's Handbook") are kept separate in that any product changes do not necessarily concern their
contents.
For example, only the Technical Handbook might be revised because of hardware configuration
changes (e.g., replacing a unit with one having different P/N but the same function).
On the other hand, the Operator's Handbook is updated because of a new software version but which
does not concern the Technical Handbook as long as it does not imply hardware modifications.
However, both types of handbooks can be updated to improve contents, correct mistakes, etc..

Handbook Updating
The handbooks associated to the "product-release" are listed in “Related Documents” on page 13.
Each handbook is identified by:

– the name of the "product–release" (and "version" when the handbook is applicable to the versions
starting from it, but not to the previous ones),
– the handbook name,
– the handbook Part Number,
– the handbook edition (usually first edition=01),
– the handbook issue date. The date on the handbook does not refer to the date of print but to the date
on which the handbook source file has been completed and released for the production.
Changes introduced in the same product–release (same handbook P/N)
The edition and date of issue might change on future handbook versions for the following reasons:
– only the date changes (pointed out in the Table of Contents) when modifications are made to the edi-
torial system not changing the technical contents of the handbook.
– the edition, hence the date, is changed because modifications made concern technical contents. In
this case:
• the changes with respect to the previous edition are listed in History on page 13.;
• in affected chapters, revision bars on the left of the page indicate modifications in text and draw-
ings.
Changes concerning the technical contents of the handbook cause the edition number increase (e.g. from
Ed.01 to Ed.02). Slight changes (e.g. for corrections) maintain the same edition but with the addition of
a version character (e.g. from Ed.02 to Ed.02A). Version character can be used for draft or proposal edi-
tions.
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

Handbooks relevant to software applications (typically the Operator's Handbooks)
are not modified 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 procedures.
Moreover, should the screen prints included in the handbook contain the product–release's
"version" marking, they are not replaced in the handbooks related to a subsequent version, if
the screen contents are unchanged.
Supplying updated handbooks to Customers
Supplying updated handbooks to Customers who have already received previous issues is submitted to
commercial criteria.
By updated handbook delivery it is meant the supply of a complete copy of the handbook new issue (sup-
plying errata-corrige sheets is not envisaged).
Changes due to new product version
A new product version changes the handbook P/N and the edition starts from 01.
In this case the modified parts of the handbook are not listed.

Customer documentation on CD-ROM
In the following by 'CD-ROM' it is meant 'Customer Documentation on CD-ROM'
Contents, creation and production of a CD-ROM
In most cases, a CD-ROM contains in read-only eletronic format the documentation of one product-
release(-version) and for a certain language.
In some other cases, the same CD-ROM can contain the documentation of different product-release(-ver-
sion)s for a certain language.
As a general rule:
– CD-ROMs for Network Management products do not contain:
• the Installation Guides
• the documentation of system optional features that Customers could not buy from Alcatel
together with the main applicative SW.
– CD-ROMs for Network Elements products do not contain:
• the documentation of system optional features (e.g. System Installation Handbooks related to
racks that Customers could not buy from Alcatel together with the main equipment).
A CD-ROM is obtained collecting various handbooks and documents in .pdf format. Bookmarks and
hyperlinks make the navigation easier. No additional information is added to each handbook, so that the
documentation present in the CD-ROMs is exactly the same the Customer would receive on paper.
The files processed in this way are added to files/images for managing purpose and a master CD-ROM
is recorded.
Suitable checks are made in order to have a virus-free product.
After a complete functional check, the CD-ROM image is electronically transferred to the archive of the
Production Department, so that the CD-ROM can be produced and delivered to Customers.
Use of the CD-ROM
The CD-ROM can be used both in PC and Unix WS environments.
The CD-ROM starts automatically with autorun and hyperlinks from the opened “Index" document permit
to visualize the .pdf handbooks
Other hyperlinks permit to get, from the Technical handbooks, the specific .pdf setting documents.
In order to open the .pdf documents Adobe Acrobat Reader Version 4.0 (minimum) must have been
installed on the platform.
The CD-ROM doesn't contain the Adobe Acrobat Reader program. The Customer is in charge of getting
and installing it.
ReadMe info is present on the CD-ROM to this purpose.
Then the Customer is allowed to read the handbooks on the PC/WS screen, using the navigation and
zooming tools included in the tool, and to print selected parts of the documentation through a local printer.

CD-ROM identification
Each CD-ROM is identified:
1) by external identifiers, that are printed on the CD-ROM upper surface:

– the name of the "product-release(s)" (and "version" if applicable)
– a writing indicating the language(s),
– the CD-ROM Part Number),
– the CD-ROM edition (usually first edition=01)
2) and, internally, by the list of the source handbooks and documents (P/Ns and editions) by
whose collection and processing the CD-ROM itself has been created.
CD-ROM updating
The list of source handbook/document P/Ns-editions indicated in previous para. point 2) , in association
with the CD-ROM's own P/N-edition, is also loaded in the Alcatel-Information-System as a structured list.
Whenever a new edition of any of such handbooks/documents is released in the Alcatel archive system,
a check in the Alcatel-Information-System is made to identify the list of CD-ROMs that must be updated
to include the new editions of these handbooks/documents.
This causes the planning and creation of a new edition of the CD-ROM.
Updating of CD-ROMs always follows, with a certain delay, the updating of the single handbooks com-
posing the collection.

1 GENERALITIES
1.1 1353NM 7.3 news Overview

1353NM 7.3 is a version that signs a turning point in the system architecture. A common platform for NM
Subsystems 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 Subsystems at the same time.
Another incentive to the development of the OS-Kernel comes from observing the growing size of the serv-
ers 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 appli-
cations, 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
• Subsystem Configuration
• Installation/Integration & Customization
• System Management Function

Generalities 3AL 89082 BAAA Edition 01 21/270
1.2 1353NM activation
TMN OS is the graphical interface of OS-Kernel application dedicated to manage the different Subsystem
Instances built on the same hardware machine.
TMN OS application is the box containing and managing all the NM Subsystems customized on a single
physical 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 Man-
agement Window will be shown in a few seconds, you have to select the 1353NM instance you want to
manage.
Figure 2. TMN OS application

22/270 3AL 89082 BAAA Edition 01 Generalities
1.3 Role of the Administrator
The role of the administrator can be summarized in:
– 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).

1.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 preceded 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).

2 RELEASE IDENTIFICATION
The Subsystem general information and Subsystem composition for 1353NM products is displayed
selecting from TMN-OS menu OS | --> System Information or pressing the icon on the menu bar.
Figure 5. Subsystem Information
The following window will be displayed with all information about the selected Subsystem Instance.

Release identification 3AL 89082 BAAA Edition 01 25/270
Figure 6. 1353NM Subsystem Information
Displayed Informations are :
• System : 1353NM OS Subsystem 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
• LOCAL OSK-ENGINE Interface Version: Version of the component OSK-ENGINE on the
local machine.
• Master Kernel Type: Master machin Kernel Type.
• Master OSK-ENGINE Interface Version: Version of the component OSK-ENGINE on the
master machine for interface.

26/270 3AL 89082 BAAA Edition 01 Release identification
• Composition : lists all the components and applications belonging to the Subsystem with cor-
responding versions.
Click on the Dismiss button to close this window.

Release identification 3AL 89082 BAAA Edition 01 27/270
28/270 3AL 89082 BAAA Edition 01 Release identification
3 CONFIGURATION
The installed Alcatel TMN System applications need to be configured in order to run properly. The con-
figuration consists in creating configuration files and databases. It is important to notice that the config-
uration should be performed only on Master instances, the configuration is not required on client
instances.
Following paragraphs describe how to configure the Master instance of 1353NM Subsystem.
3.1 Preparing 1353NM Configuration

Before starting 1353NM Configuration you have to configure all the LAN interface planned to be used by
Retix 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 Con-
figuration, 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 sug-
gested name is: osilan<lan number>, where <lan numer> should be substituted
with the lan logical number. This method allows also to easy identify the lan card with
Retix Stack configured.
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.21hosta osilan1
You have to change it by removing the reference to hosta:

192.200.200.21osilan1
Then save the modified /etc/hosts file.

Configuration 3AL 89082 BAAA Edition 01 29/270
3.2 Configure the Patch STYL on 1353NM
The procedure described in this paragraph configures the patch STYL.
Important : If the patch STYL should be configured you have to apply the Workaround
described in following paragraph before customizing 1353NM Subsystem (paragraph
3.5.2.7 on document “1350NM Management Suite NR7.1 Installation Guide” Ref.[3]).
Refer to ”Patch styl procedure” section.
The so–called Patch STYL is present in order to manage some QB3* equipment (1651,1661). Normally
this is the case of previously migrated (from NR3.1B, for example) networks containing QB3* equipment.
This patch is associated with emlimadmnr31. Otherwise emlimadmnr5qb3 is present to manage QB3*
1651 and 1661 equipment and, eventually the emlimadmnr31 for the others QB3* equipment.
Important! This configuration forces the old emlimadmnr31 to manage 1651SM and 1661SMC instead of
the new emlimadmnr5qb3–process, and thus it will not be possible to use the features supported by this
process.
3.2.1 Patch STYL Procedure
In this section the patch STYL will be configured on 1353NM NR7.4 machine.
Following steps are required:
1 ) Login on 1353NM machine as user root
2 ) Change to the directory /alcatel/NMA/EMLUSM31QB3S/7.3/conf/Kernel/
sys,root > cd /alcatel/NMA/EMLUSM31QB3S/7.3/conf/Kernel
3 ) Execute following commands :
sys,root > cp –p PNM.cfg PNM.cfg.orig
sys,root > cp PNM.cfg.style PNM.cfg
sys,root > cp –p Navigations.cfg Navigations.cfg.orig
sys,root > cp Navigations.cfg.style Navigations.cfg
4 ) Change to the directory /alcatel/NMA/EMLUSM5QB3S/7.3/conf/Kernel
sys,root > cd /alcatel/NMA/EMLUSM5QB3S/7.3/conf/Kernel
Execute following commands
sys,root > cp –p PNM.cfg PNM.cfg.orig
sys,root > cp PNM.cfg.style PNM.cfg
sys,root > cp –p Navigations.cfg Navigations.cfg.orig
sys,root > cp Navigations.cfg.style Navigations.cfg

30/270 3AL 89082 BAAA Edition 01 Configuration
3.2.2 System Configuration
The patch STYL configuration will be completed by the correct setting in the System Configuration phase.
During System Configuration the Sh_Subsytem component should be selected in order to set the param-
eter PATCH_STYL to the value TRUE as shown in following figure
Figure 7. Sh_SubSystem Parameter Configuration window

3.3 Change the IP configuration
The described IP parameter change is meaningful for all 1353NM Systems with any NE managed via
SNMP.
HP-UX default IP protocol configuration has to be changed to allow the correct communication between
1353NM and NE via SNMP, in the following of this paragraph is described how to change it permanently.
In order to change permanently the IP parameter “ip_pmtu_strategy" you have to login the HP-UX as root
user. The parameter “ip_pmtu_strategy" should be forced to value “0" (zero), you have to proceed as
described below:
a) Check how many uncommented “TRANSPORT_NAME" are defined by entering:
...,sys,root # grep TRANS /etc/rc.config.d/nddconf [Enter]
b) Usually only “TRANSPORT_NAME[0]=tcp" is defined, in this case add the following three lines to
the file “/etc/rc.config.d/nddconf" , otherwise if there is no TRANSPORT_NAME defined replace
value 1 between square brackets with value 0, if there are more than one “TRANSPORT_NAME"
lines defined replace value 1 between square brackets with a value greater than the higher value
defined:
..,sys,root # vi /etc/rc.config.d/nddconf [Enter]
Type G and insert the following lines:
TRANSPORT_NAME[1]=ip
NDD_NAME[1]=ip_pmtu_strategy
NDD_VALUE[1]=0
Save and exit from the file typing :x! and press [Enter].
The new value will be assigned to the parameter after the next reboot. It is advisable to verify the
“ip_pmtu_strategy" value after the next reboot by entering the command:
...,sys,root # ndd -get /dev/ip ip_pmtu_strategy [Enter]
The output of the command should be “0" (zero), if it is still “1" review the contents of “/etc/rc.config.d/
nddconf" file.
If the next reboot is not planned in a short time, and you have to change the “ip_pmtu_strategy" parameter
immediately, you can do it entering the following command:
...,sys,root # ndd -set /dev/ip ip_pmtu_strategy 0 [Enter]

3.4 1353NM IP Configuration
3.4.1 Routing Configuration
Within the current network release there are two cases in which the IP routing is necessary to guarantee
the correct behavior of 1353NM:
1) The ISA boards on ADMs.
2) An external client application (i.e.USM).
N.B. If any system is MC/Service Guard protected via 1359HA_OSCluster, the routing configuration must
be done also on the spare node.
3.4.1.1 Routing Configuration for ISA board
To be able to reach the ISA boards from both Element manager and USM the correct IP routing has to
be configured, in fact the ISA boards are always in a different subnetwork, that means it is necessary to
specify in a configuration file how to reach the destination.
The configuration file depends on the routing you have to use. There are two different type of routing:
1) Static routing
2) Dynamic routing
The static routing is easy to configure, and has no impact on the TCP/IP networking, but in case of failure
of the gateway the destinations will became unreachable. Vice versa, using the dynamic routing, with an
appropriate configuration it is possible to guarantee the service also in case of single failure.
FOR BOTH ROUTING METHOD IT IS MANDATORY THAT THE NETWORK MASK (NETMASK) IS
THE SAME FOR ALL INTERFACES BELONGING TO THE SAME SUB-NETWORK.
If different values of the netmask are set on the interfaces the communication are not guarantee
and the DYNAMIC ROUTING CANNOT BE ABLE TO OPERATE.
3.4.1.1.1 Configuration of Static Routing for ISA board
To allow the communication between 1353NM systems and the ISA boards with static routing you have
to declare with route command the gateway to get to the destination. The information that have to be
identified are: the network that has to be reached and the gateway.
The network is defined by an IP address ISA Board and a netmask. This information has to be defined
by the Network Addressing Plan. In our case we are interested to identify the network containing ISA
Boards that have to be managed by our Network Management system.
The gateway is a machine that allows getting to the destination ISA Board; it can depend on the network
topology.
For configuring the static routing the route command is used, it allows declaring the network where the
ISA boards are located and the relationship with the gateway. Following command drives the system to
choose the way to the destination:
...,sys,root # route add net <network> netmask <mask> <gateway> 1 [Enter]
Where:

<network> is the IP network address (Logical AND IP address of node and netmask) which
the ISA board IP belongs to (for example: an ISA with IP address 10.6.4.33 and net-
mask 255.255.0.0 belongs to the network 10.6.0.0)
<mask> is the mask where the bit set to 1 identifies the part of address related to the net-
work, and the bit set to 0 identifies the host in the address.
<gateway> is the IP address of the router or ADM GNE that allow to get to ISA Board.
When the right configuration is reached, in order to save it after system reboot, you have to add following
lines to the file "/etc/rc.config.d/netconf":
..,sys,root # vi /etc/rc.config.d/netconf [Enter]
ROUTE_DESTINATION [<x>]="net <network>"
ROUTE_MASK[<x>]=<netmask>
ROUTE_GATEWAY[<x>]=<gateway>
ROUTE_COUNT[<x>]=1
ROUTE_ARGS[<x>]=""
Where:
<x> is the last defined "ROUTE_DESTINATION" number plus one, or 0 (zero) if the is no
route destination defined yet.
<mask> is the mask where the bit set to 1 identifies the part of address related to the network,
and the bit set to 0 identifies the host in the address.
<network> is the IP network address (Logical AND IP address of node and netmask)
Add a new routing destination to the routing table (editing the /etc/rc.config.d/netconf file) for
each new network defined for ISA Board.

3.4.1.1.2 Static Configuration Example
The example in Figure 8. shows how to configure 1353NM machines with a typical configuration, where
you have the 1353NM Master and the NM Client Function that can be performed by 1353NM Client sys-
tems, but also by 1354RM Master and/or Presentation ones.
Figure 8. Example of network with ISA board
3.4.1.1.3 Configuration of Static Routing on NM Master
To configure the NM Master (lan0 IP 10.2.1.7 , lan1 IP 10.3.7.5) to be able to reach the ISA Board it is
necessary to define the gateway to reach the network where the ISA board is located. In the example the
ISA board is reached via a Gateway Network Element (GNE) , that means the IP address of the GNE will
be used as gateway (in other configuration the gateway can be a router).
The ISA board network can be identified by executing the logical AND between the IP address of the board
and its netmask:
IP address 10 61 4 33
logical AND
Netmask 255 255 0 0
----------------------------------
network 10 61 0 0

In this example the configuration is done defining one of the two GNE IP address as gateway to reach
the ISA Board, with following command:
..,sys,root # route add network 10.61.0.0 netmask 255.255.0.0 10.3.7.6 1 [Enter]
Check the network connectivity by executing a ping command from NM Master to ISA Board:
..,sys,root # ping 10.61.4.33 64 10 [Enter]
You can use the command netstat -r to verify the routing table contents.
When the right configuration is reached, you have to add the configuration lines shown in the paragraph
1.2.1.1 at page 8 to the file "/etc/rc.config.d/netconf".
This configuration has a disadvantage, when the gateway GNE fails, the ISA board becomes unreach-
able. To recover the failure it is necessary to modify the routing table removing the route via failed GNE
(IP address 10.3.7.6) and set up a new one via the alternative GNE (IP address 10.3.7.7).
3.4.1.1.4 Configuration of Static Routing on NM Client
NM Client function comprises all the machines that run 1353NM USM, including 1354RM and 1354SY.
The NM Client Function (IP 10.2.1.7) should be able to reach the ISA board (IP 10.61.4.33) to correctly
perform its job. In the example this occurs via NM Master and GNE. In other configuration you can find
NM Client Function machine sharing the same LAN with the GNE or with a router, in any case it is nec-
essary to identify the gateway for the next LAN segment, it will have the task to send the packet forward
to the destination system.
In the example the configuration have to be done defining the lan0 of NM Master as gateway. To obtain
this behavior you have to enter following command on the NM Client Function system:
..,sys,root # route add 10.61.0.0 netmask 255.255.0.0 10.2.1.6 1 [Enter]
Check the network connectivity by executing a ping command from NM Client to ISA Board:
..,sys,root # ping 10.61.4.33 64 10 [Enter]
Be careful: The ping can fail because NM Master is not yet configured to forward the packages.
When the right configuration is reached, you have to add the following configuration lines to the file "/etc/
rc.config.d/netconf".
ROUTE_DESTINATION [<x>]="net <network>"
ROUTE_COUNT[<x>]=1
ROUTE_ARGS[<x>]=""
Where:

<x> is the last defined "ROUTE_DESTINATION" number plus one, or 0 (zero) if the
is no route destination defined yet.
<mask> is the mask where the bit set to 1 identifies the part of address related to the net-
work, and the bit set to 0 identifies the host in the address.
<network> is the IP network address (Logical AND IP address of node and netmask)
3.4.1.1.5 Configuration of Static Routing on NM Master with OS-Cluster
When the 1353NM is configured with OS-Cluster (MC/Service Guard) it is necessary to configure also the
spare server, in order to allow the correct routing when the switchover occurs. All the network added to
the routing table of the 1353NM main instance MUST be added also to the spare machine.
For example, if you have an OS-Cluster with two 1353NM and a spare system, and in the network con-
figuration file (/etc/rc.config.d/netconf) of the two 1353NM you have:
N.B. In the example the default gateway it is not mentioned, so the route descriptions are shown
starting from 1.
The first 1353NM have to manage Network Elements in the subnetworks 10.61.0.0 through the router
10.3.7.6 and 10.62.0.0 through the router 10.3.7.7.
ROUTE_DESTINATION[1]="net 10.61.0.0"
ROUTE_MASK[1]=255.255.0.0
ROUTE_GATEWAY[1]=10.3.7.6
ROUTE_COUNT[1]=1
ROUTE_ARGS[1]=
ROUTE_MASK[2]=255.255.0.0
ROUTE_COUNT[2]=1
ROUTE_ARGS[2]=
The second 1353NM have to manage Network Elements in the subnetworks 10.63.0.0 through the router
10.3.7.6:
ROUTE_MASK[1]=255.255.0.0
ROUTE_COUNT[1]=1

ROUTE_ARGS[1]=
The spare system will have a description that have to include all of destinations:
ROUTE_MASK[1]=255.255.0.0
ROUTE_COUNT[1]=1
ROUTE_ARGS[1]=
ROUTE_MASK[2]=255.255.0.0
ROUTE_COUNT[2]=1
ROUTE_ARGS[2]=
ROUTE_MASK[3]=255.255.0.0
ROUTE_COUNT[3]=1
ROUTE_ARGS[3]=
3.4.1.2 Configuration of Routing for Client Applications
Using 1353NM with multistack option require some more configuration actions to allow the correct com-
munication between Client and Master applications. In fact they have to communicate each other within
an environment where the Retix Stacks can be installed on the 1353NM Master system, and they can be
instanced for each LAN card equipped on the system. The Client application can be installed on 1353NM
Master and Presentation and also on 1354RM IM and US. To allow the correct behavior of all the installed
applications in the configuration you have to configure the communication among all the LAN cards
involved.
For Retix Stacks instances on lan0 card no additional configuration action are required, because the con-
nectivity and/or the routing have to be guarantee to allow other communications.
For Retix Stacks instances on LAN different than lan0 the connectivity have to be created and verified.
The most common 1353NM configuration with multistack foresees two or more LAN cards each one con-
nected to a different LAN segment. This approach allows to share the traffic on different segments, and
some times is used to avoid mixing IP and OSI traffic.
When the Retix Stacks is configured on LAN board different than lan0, it is necessary to configure some
the routing table on 1353NM Client machine.
In this document are shown three scenarios:
1) Systems in the same site partially sharing the same LAN segment

2) Systems in different sites with full router connection
3) Systems in different sites without full router connection
3.4.1.2.1 Systems in the same site partailly sharing the same LAN segment
This scenario is related to machine sharing the same LAN segment with lan0, but LAN different than lan0
are not connected with. In this scenario, using the internal routing of HP–UX system can set up the com-
munication that means the packets from lan0 of the NM Client will reach the lan1 of the NM Master passing
through lan0 of NM MAster itself.
Figure 9. Systems without sharing LAN (case 1)
To obtain this behavior you have to enter the following command on the NM Client system:
..,sys,root # route add <IP address lan1 SHM> <IP address lan0 SHM> 1 [Enter]
It is recommended to verify the correct data entry entering the command:
..,sys,root # ping <IP address lan1 SHM> [Enter]
on the NM Client system.
When the right configuration is reached, in order to save it after system reboot, you have to login the HP–
UX as root user, then you have to add the following three lines to the file "/etc/rc.config.d/netconf":
ROUTE_DESTINATION[<x>]=<IP address lanx NM Master>

ROUTE_GATEWAY[<x>]=<IP address lan0 NM Master>
ROUTE_COUNT[<x>]=1
Where:
x is the next available value. Check the already existing

ROUTE_GATEWAY in the file.
IP address lanx NM Master is the IP address of the lan different than lan0 that have to reached
passing through lan0.
IP address lan0 NM Master is the IP address of lan0 of the 1353NM Master system
N.B. Before proceed with modifying the /etc/rc.config.d/netconf it is advisable to make a copy of the
original file, by entering (as root): cp /etc/rc.config.d/netconf /etc/rc.config.d/netconf.orig
3.4.1.2.2 Systems in different sites with full router connection
In this configuration all the involved router have to be configured to route IP protocol and allow the com-
munication among all the lan cards.

3.4.1.3 Systems in different sites without full router connection
The last scenario is related to machine connected to different LAN segments, where only the lan0 of these
segments are connected via IP routers. In this scenario it is necessary to use the internal routing of HP-
UX system to be able to set up the communication. Be careful that on the router connected with NM master
lan0 (Router 2 in the picture) you have to configure the NM Master system as next hop to reach the lan1.

3.4.2 Multi-Lan configuration
When 1353NM Subsystem is installed with HP-UX 11.11 all the lan present in config-
uration MUST BE CONFIGURED with an IP address, also if they will not be used. This
rule applies to Master and Presentation systems.
Starting from 1353SH 6 it is possible to use Retix stack on more than one lan board, every lan board used
have to be configured with an appropriate TCP/IP address. Usually the lan0 is automatically configured
by HP-UX Operating System in the installation phases, but other lan have to be configured as well.
3.4.2.1 Lan configuration rules
To configure the lan board it is necessary to follow these rules:
1) No other machine connected to the Local Area Network has the same IP address .
2) There is no board already configured on the same machine with an IP address belonging to the
same subnetwork.
3) The first and the last address of each subnetwork is reserved.
4) The network 127.0.0.0 is forbidden.
The first rule means that all the used IP address have to be defined in a specific addressing plan, usu-
allyprovided by the customer.
The second rule is due to the Unix routing mechanism, if there are two lan board belonging to the same
subnetwork on the same system, the routing process is not able to define which is the way to send out
the messages, and the communications will be stopped.
To identify the subnetwork of an IP address you have to perform the local AND between the IP address
and the netmask.
Example:
This example shows two addresses that look similar but belong to different networks.
IP address 192.1.1.1 with netmask 255.255.255.0 -> Subnet 192.1.1.0
This example shows two addresses that look different but belog to the same network.
The best way to check the relationship between IP Address and netmask is to enter the command “ifcon-
fig" for each lan board and check the value of broadcast. The values have to be different.
Example:
..,sys,root # ifconfig lan1

lan1: flags=963<UP,BROADCAST,NOTRAILERS,RUNNING,PROMISC,MULTICAST>
inet 192.1.1.1 netmask ffffff00 broadcast 192.1.1.255
..,sys,root # ifconfig lan2
lan2: flags=963<UP,BROADCAST,NOTRAILERS,RUNNING,PROMISC,MULTICAST>
inet 192.1.2.1 netmask ffffff00 broadcast 192.1.2.255
which the ISA board IP belongs to (for example: an ISA with IP address 10.6.4.33
where the netmask is 255.255.0.0 belongs to the network 10.6.0.0)
<mask> the mask where the bit set to 1 identifies the part of address related to the network,
and the bit set to 0 identifies the host in the address.
<gateway>router or ADM GNE IP address that allow to get to ISA Board.

When the right configuration is reached, in order to save the configuration also after system reboot, you
have to add following lines to the file “/etc/rc.config.d/netconf":
Type G and insert following lines:

ROUTE_DESTINATION[<x>]="net <network>"
ROUTE_COUNT[<x>]=1
ROUTE_ARGS[<x>]=""
Where:
<x> is the last defined “ROUTE_DESTINATION number plus one, or 0 (zero) if

there is no route destination defined yet.
<mask> the mask where the bit set to 1 identifies the part of address related to the
network, and the bit set to 0 identifies the host in the address.
<network> IP network address (Logical AND IP address of node and netmask)
<gateway> IP address of the router or ADM GNE that allows getting to ISA Board.
A new routing destination have to be added to the routing table (editing the/etc/rc.config.d/netconf
file) for each new network defined for ISA Board.

3.5 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.
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 12. 1353NM Warning Security Box

Please ignore the “Security not activated" warning message, it will disappear after the configuration
explained in this chapter.
TMN OS Icon
Figure 13. 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 14.) selecting “System Config".
Figure 14. TMN-OS Management Window

3.5.1 System Tuning
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 15. 1353NM System configuration window
Don't select QB3S_Simulator item (see paragraph 3.5.1.1 at page 48 for more informa-
tions):
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) con-
figuration 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;
• 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.
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.

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 16. 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 17. 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 18. 1353NM PMDS_DB_SubSystem

3.5.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 19. 1353NM Parameter Definition -Q B3S_Simulator Set-up
3.5.1.2 Configure System Management Functions
The entity System_Mgt_Functions is listed in the component list and represents the well known SMF
(System Management Functions). Its selection is manadatory.
Select the entity System_Mgt_Functions to get it in the Subsystem List.
Figure 20. Entity “System_Mgt_Functions" selection

3.5.2 Configure specific NMAs
3.5.2.1 Retix Stack Configuration
Each lan interface that is configured to be used as retix Retix 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 15.at page 45).
c) Click on “Arrow Button" in the center of the window to create the new item.
Figure 21. 1353NM Necom SubSytem 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.

Figure 22. 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.
Figure 23. 1353NM Necom SubSystem 3
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".
The stack should be configured on all defined lans, also in case only snmp emlin will be configured
on a specific lan. The configured stack identifies the supervision area where emlims are allocated.
This supervision area is used during creaztion of NEs in PNM application.
3.5.2.2 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
DEFINED FOR THE RELATED RETIX STACK.
Figure 24. 1353NM Antp
Then pull down the “Action" menu and select “Apply & exit".
3.5.2.3 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
RETIX STACK.
Figure 25. 1353NM FTServer and FTclient
Then pull down the “Action" menu and select “Apply & exit" from each one of them.

3.5.2.4 Configuring the 1353NM Element Manager Layers
When all the foreseen Retix 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 Con-
figuration" window left column (Figure 15. at page 45), 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.
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 value must be
between 200 and 299. The 1354NM Instance Identifier is the value entered predisposing and cus-
tomizing 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 26. 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 27. 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.

3.5.3 Configuring 1353NM Element Manager Layers of type SGM and MELOSNMP
The emlims managing this type of NEs has a different configuration, not only the “SUPERVISION_AREA"
parameter should be configured, but also the parameter UDP_PORT as shown in the following figure :
Figure 28. Configuring EMLIMSGM and EMLIMMELOSNMP
The UDP_PORT number parameter should be a number greater than 1024 because the previous port
number are reserved for 'root' user, the only other rule to follow is to assign different port numbers to dif-
ferent emlims.

3.5.4 Configuring OSI GATEWAY
The configuration of the OSI Gateway inside 1353NM R7.x is described in this paragraph.
Selecting OSI_GATEWAY in the System_Sublist on the left of the System Configuration window, the win-
dow used to configure the OSI Gateway specific parameters will be displayed.
Figure 29. OSI Gateway Parameters definition

Figure 30. OSI Gateway Parameters definition (cont.)
The external managers use these parameters to open the association with the OSI Gateway inside the
1353NM Subsystem. The definition of the above parameters is the following:
• SUPERVISION AREA: is necessary to associate the OSI Gateway to the right Lan.
• EMLENTITYPSAP: Presentation Selector (Default value 0x5058)
• EMLENTITYSSAP: Session Selector (default value 5345)
• EMLENTITYTSAP: Transport Selector (default value 4152)
• EMLENTITYNSAP: Network Address associated to the OSI Gateway: this parameter must be
inserted in RFC1006 format (the right mode to insert this format is shown in the Appendix).
• MGR_CONNECT_TYPE: this parameter defines the connection type of OSI Gateway Manager
and must be set = SOCKET.
• AGT_CONNECT_TYPE: this parameter defines the connection type of OSI Gateway Agent
and must be set = RETIX.
• STACK: this parameter defines the type of stack for OSI Gateway and must be set = RFC1006.
• MGR_AETITLE: this parameter defines the OSI Gateway AETITLE and must be set = "default
value" 2.9.3.2.7.5 .
When all parameters are inserted choose Apply from the Actions menu.

3.5.4.1 RFC1006 format
Two parts compose RFC1006 format:
• The first part is fix and is equal to 540072872203
• The second part depends from IP address.
For example with an IP address = 121.2.3.23; OSI address will be:
0x540072872203121002003023
where:
0x540072872203 is the header
0x121002003023 is the IP address
3.5.4.2 Manager configuration with RFC1006 and Multistack Retix
If the configuration of the device used by OSI Gateway is a Multistack Retix configuration, it is necessary
"to inform" the Manager that it will lock the OSI Gateway by a Retix instance waiting on a different port
from the standard one (102). Therefore, the RFC1006 address to utilise will be always that configured in
preceeding paragraph; however, the information on the port to be used must be added: with an IP address
= 121.2.3.23, the corresponding OSI RFC1006 address will be: 0x540072872203121002003023 with
Retix instance operating on 1033 port, the OSI address by which the Manager identifies the OSI Gateway
will be as follows:
0x540072872203121002003023010330001
where:
0x01033 two bytes and a half representing the port
0x00001 two bytes and a half representing the TCP protocol
Entity PSAP, Entity SSAP, Entity TSAP selectors will not change and they will be however inserted, as
described in the previous paragraph.

3.5.5 Execute the configuration
When all the Element Managers and Services are assigned to the Retix Stack(s), the System Configu-
ration 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 following windows:
Figure 31. 1353NM Configuration Warnings Window

Figure 32. 1353NM Configuration Error and Warnings window
At the end of System Configuration execution the “Dismiss" button in the lower part of window will be
enabled. Look for any error and warning ignoring the shown once. If everything look correct pull down
again the “Main" menu and select “Quit".
Figure 33. 1353NM Configuration quit.
Press “Yes" button to terminate.

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]
3.5.6 WA after System Configuration for MDR 8000 Rel.2.0 NEs Management
If 1353NM Subsystem manages NEs of type MDR 8000 Rel.2.0 following operations should be done after
System Configuration, to be able to start NE Supervision.
A line must be changed in file param.cfg, the file corresponding to snmp emlim.
Perform following operations from a terminal with UNIX prompt :
.., $ cd /usr/Systems/1353NM_<instance_id>/eml/snmp/csnmp/conf/ \ [Enter]

vi param.cfg \ [Enter]
find in the file the parameter named CSNMP_CHECK_TYPE_AND_RELEASE and change the value
from TRUE to FALSE. Save and exit. Now the NM Subsystem can start.
3.5.7 Removing a previously configured process from the Subsystem configuration
The procedure described in this section is clearly an exception, but nevertheless we describe it to warn
from a different behavior. If a process correctly configured and running for the 1353NM Subsystem should
be for any reason removed from the configuration, this process must be previously stopped using PMC
application.
The sequence of operations to be performed is the following :
• from TMN OS menu select OS --> Process Monitoring
• PMC windows appear, select the process to remove and from PMC menu select Actions -->
Stop --> Selected Item
• when the process appeared as stopped, go back to TMN OS menu and select OS --> System
Config
• select the process to remove in the process list on the right (the process change the color from
blu to grey, now select from menu Main --> Update Config

3.6 1353NM Master and Client Integration
If you have any 1353NM Client Subsystem, and you do not plan to install the 1354RM, you have now to
integrate 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.

3.7 Process Monitoring
The Process Monitoring & Control ( PMC ) tool is a graphic interface of the OS-Kernel application and
is explained in document [4].
When the Process Monitoring option is selected on TMN OS window, the following window appears:
Figure 34. Process Monitoring Control Main Window

3.7.1 Groups of Processes
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.
Table 5. Groups of processes

Process Group Process Description
Retix_Stack_0 Retix_ll_<lan_0>_0 Communication stack process for

lan 0
Retix_ul_<lan_0>_0 Communication stack process for

lan 0
Xcc_<lan_0>_0 Communication stack process for

lan 0
Emlims EMLIMADM31 For each NE type a different

EMLIMADMQB3 emlim is configured to manage
EMLIMADMQ3 NE.
EMLIMWDM31 Emlims are instantiable pro-
EMLIMWDMSUBNR7 cesses, more instances can be
EMLIMDXCQ3 instanced to manage different
EMLIMMELO NEs.
EMLIMMELOSNMP
EMLIMCORBASNMP
EMLIMMW
EMLIMMW30
EMLIMSGM
Topology Manager Topology_Manager_IM Information Manager component

of the PNM subsystem. As such,
it is an agent application respon-
sible for the integrity and consis-
tency of the data that it handles. It
is also a manager application with
respect to EML-IM(s).
Map_Distributor_IM Map management process

Alarms AS_Current_IM As an Alarm Agent manager, AS

current IM role is to:
- manage the interface with the
Alarm Agents and to implement
for this purpose a filtering mech-
anismwith regards to Alarm
Agents configured to this AS
instance.
- perform a synchronization of
alarm information present in the
CAL with active reportable alarms
presentin the Alarm Agents.
- filter alarm information received
from Alarm Agent with regards to
an AS IM instance Filter specified
inoff-line configuration of AS.
AS_Historic_IM The historical alarm information is

stored in the Public Archive by the
AS Current IM.
SQL_database Database_sql_daemon process for SQL database man-

agement
Performances Perfstorage This application is scheduled to

collect the measurement data
and store them into a dedicated
database. There are system
applications, which use other
ways to store data for PMDS;
Perfstorage is not the only gate to
access PMDS data.
Perfcollector Intermediate application between

Perfmonitor the EMLIM, which is in charge to
collect PM data, and Perfstorage.
These applications process the
performance monitor data files
and other interfaces to be ready in
the right directory for Perfstorage
application.
PMDS_db_submarine_storage_ Process acting for submarine

daemon store module.
PMDS_db_TCA_alarms Gives warning message when

the size of terrestrial/submarine
databases exceeds the setting.

PMDS_db_dbadmin_server To identity the database, the data-

base name uses the following for-
mat "Site_Server_Database".
There are 5 keys for each data-
base: Address, Port, DB_Name,
User_ID and Password.
On_Board_Simulator Simcon Process for running on board sim-

ulator.
StackServices_0 Antp_<lan_0>_0 Ntp application for NE network

synchronization.
ositunneling_0 IPoverOSI tunneling
neadnmsrv_<lan_0>_0 NE AutoDiscovery
FTServices_0 FTclient_<lan_0>_0 FT client process for lan 0
FTserver_<lan_0>_0 FT server process for lan 0
FTScheduler FTSSNMP FT Server for SNMP protocol
FTSQ3 FT Server for Q3 protocol
FTSQB3S FT Server for QB3* protocol
FTSSIM FT Server for Simulator
OSIGATEWAY EvtAgent Agent for event handling
OsiGateway Process used in OSS system

communication via RETIX Stack
with full OSI or RFC-1006

3.7.2 Run Levels
NMS Run Level is a Unix Run-Level similar concept, that lets consider the system to be in a run level at
any given time. A run level can be viewed as a software configuration of the subsystem, where each con-
figuration allows only a selected group of processes to exist.
Table 6. Run levels

Run Level Name Description
Number
0 FullFunctionality Subsystem runs with all configured functionalities
1 BackupMode Subsystem runs to allow a backup job running without conflicting

problems. Only processes configured for this run level should run.
2 RestoreMode Subsystem runs to allow a restore job running without conflicting

problems. Only processes configured for this run level should run.
3 DB_only Subsystem runs to allow a databese job running. Only processes

configured for this run level should run.

4 USER MANAGEMENT
4.1 User Profiles Description
4.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
command 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 asso-
ciating targets to initiators.
Clicking on TMN OS menu Actions --> 1353NMAdmin the System Management menu will be displayed
(see Figure 35.).

User Management 3AL 89082 BAAA Edition 01 67/270
Figure 35. TMN OS SEC Administration activation
This action displays the System Management selection window as shown in the following figure :
Figure 36. System Mangement Menu to access SEC Administration

68/270 3AL 89082 BAAA Edition 01 User Management
Select SEC Administration to access the following menu :
Figure 37. 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.
Figure 38. SEC USM Browser
The access control model of SEC is based on the notions of object, function, and object-function com-
bination.

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

ment; 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. Symmet-
rical 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 combi-
nations 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 the 1350NM System Management Operator's Hand-
book.
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 char-
acterized 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
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.
Introducing OS-Kernel common platform has changed also the users profile management.
Functional Access Domain and consequently the users profile management for OS-Kernel based sys-
tems is based on two level of configuration.
• First level : classification of each Generic Component function in one or more application FAD.
• Second level : Specific NMS association of these elementary application FADs to an Operator
Profile.
The caracteristics of each profile are:
• administator: NM administrator; he/she can do everything on NM Subsystem;
• 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 pre-
defined profiles shown above; predefined names and predefined profiles cannot be reconfigured.
4.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.
The elementary application FAD are named:
• Admin
• Operator
• Constructor
• Viewer
They have the following properties:
• They are designed to include, for each Generic Component, all functions needed for a coherent
use of Generic Component itself.
• They are common to all Generic Component (i.e., although each NMC can define its own dif-
ferent application FAD, the defined FAD are currently used in each SEC.cfg of various
NMC_INT), so that operation crossing more GC functions, are already in the same application
FAD.

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 Func-
tional 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 the handbook listed in Table 2. at point
[10].
Whole functions
admin
operator
constructor viewer
Figure 39. Application FAD relation
4.1.3 Administrator, Operator, Viewer profiles configuration
The Application FAD relation, shown in Figure 39. , is designed in such way to permit, for the Adminis-
trator, Operator and Viewer Operator Profiles, an immediate configuration, according to the following sim-
ple correspondence in NMS Profile.cfg:
Operator profile Application FADs
Administrator Admin
Operator (i.e. former PathBuilder) Operator
Viewer (i.e. former LookOnly) Viewer

4.1.4 Constructor profile configuration
Regarding Constructor Operator Profile, it can be noted that the constructor application FAD is not con-
centric.
That means that constructor application FAD (specified only for meaningful component) is not suitable to
build, used alone, the correspondent profile (as for admin, operator, viewer). On the other hand, this con-
structor application FAD doesn't oblige NMS to permit the Constructor to execute all the Operator duties.
It is therefore up to NMS to properly configure, in its own Profiles.cfg, the Constructor profile in one of these
ways:
– A pure constructor Profile, having, for other components, only viewer permission
operator profile Application FADs
Constructor constructor, viewer
Figure 40. Pure constructor profile
– An operator-constructor Profile, having, for other components, the operator permission
operator profile Application FADs
Constructor constructor, operator

Figure 41. Operator-constructor profile
4.1.5 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>-
Unknown. 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 manage 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.

4.1.6 Customizing User Profiles
4.1.6.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 42.).
Figure 42. 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 AccessCon-
trolDomainFamily 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.

– The second step is to manage the Elementary OAD ( see Figure 43.) and associate the created ACD
to the Elementary OAD.
In the example of Figure 43.obtained selecting OAD->Elementary OAD select the tabbed panel Cre-
ate 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 4.1.5 ).
Figure 43. Elementary OAD creation.

4.1.6.2 FAD definition
The System Fad in the Included targets is fondamental for the PNM Menu. By default
an operator inherits 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.
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 Fig-
ure 44.) .
Figure 44. 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.

Figure 45. Application FAD for user viewer

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.

4.1.6.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 4.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 46.), this information describes which kind of functions ( FAD
) is possible to perform on a specific object ( OAD )
Figure 46. 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.

4.1.7 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 are given of
what it is possible to do with this objects and their relations.
A very important feature of Sec is the management of ACD, it is used to enable some oper-
ators to see some NEs on some ADC and to disable other to see them.
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.
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....

Some examples follow.
First example: the operator axadmin can only see an ACD;
as first step create an ACD test_acd ( see Figure 47.).
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 selected, containing the ACD test_acd in the Included Objects.
Figure 47. Default Access Rights Definition for operator axadmin

Figure 48. 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 48.).
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.

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 49.) (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 49. Access Rights Definition of test with the OAD-FAD test_oadfad
In this case test can manage the NEs on the ACD test_acd.
If the ACD is changed from unknown to test_acd every Action admitted for the System
Fad Administrator is enabled.

Third example: a new operator belonging to the admin group that can manage a new ACD (with the func-
tions allowed for admin group):
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 50. 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.

Fourth example: it is like the third one but the set of allowed functions is smaller (it has been cut the pos-
sibility 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 51. Create a new Function Access Domain

• The new System FAD is added in the smf Application, it is SmallAdmin instead of smfSHadmin
that has every Administrator.
Figure 52. Create a new SysFad

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

4.1.8 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 54. Create a new profile

Figure 55. Profiles in SMF-Create User

4.2 Macro functionalities related to user profiles
The following tables summarize the permissions for the default user profiles towards 1353NM Subsystem
functions. The tables are subdiveded following TMN OS menu .
TMN-OS
OS Administrator Constructor Operator Viewer
Exit Allowed Allowed allowed allowed
Start System Allowed
Stop System Allowed
System Config Allowed
Process Monitoring & Control (*) Allowed Allowed (*) Allowed (*) Allowed (*)
System Information Allowed Allowed Allowed Allowed
(*) Process Monitoring can be accessed from these profiles on the TMN-OS menu but the man-
agement is then denied for some functions. The functions are not disabled, but if a user with Oper-
ator, Constructor or Viewer profile tries to run them an error message is displayed.

PMC Administrator Constructor Operator Viewer
Actions
Exit Allowed Allowed Allowed Allowed
Start selected item Allowed
Stop selected item Allowed
Control Allowed
Set Run Level Allowed
Synchronize Allowed
View
Info Allowed Allowed Allowed Allowed
Selected agent trace Allowed Allowed Allowed Allowed
PMC2 Log Allowed Allowed Allowed Allowed
Local Configuration File Allowed Allowed Allowed Allowed
Agent Configuration File Allowed Allowed Allowed Allowed
Configuration
Set Threshold Allowed
Global Actions Administrator Constructor Operator Viewer
Global Operator Administration allowed
Change Password allowed Allowed allowed allowed
Session Management allowed
Max Operator Logged Administr. allowed
Set Personal Printer allowed Allowed allowed allowed
Synchronize Systems allowed Allowed allowed allowed

SESSION MAN- Administrator Constructor Operator Viewer
AGEMENT
workstation Broadcast message Allowed Allowed Allowed
Show good logins Allowed
Show bad logins Allowed
Logout all users Allowed
Lock Allowed
Users Force logout Allowed
AS Administrator Constructor Operator Viewer
Alarms allowed Allowed allowed allowed
Alarm Federation allowed allowed allowed allowed
PMDS Administrator Constructor Operator Viewer
Performance Monitoring Allowed allowed Allowed Allowed

Alarm Surveillance
Current Alarms Administrator Constructor Operator Viewer
Modify Filters Allowed allowed allowed
Administration Allowed
Synchronization Allowed allowed allowed
Reserve Alarm Allowed allowed
Acknowledge Alarm Allowed allowed
Archive Alarm Manually Allowed allowed
Request TroubleTicket Creation Allowed
Export Alarm Information Allowed allowed allowed
Get More Alarm Information Allowed allowed allowed
Navigation->Historical Alarm Usm Allowed allowed allowed
Navigation -> Topology Manager Allowed allowed allowed
Navigation -> External Application Allowed allowed allowed
Historical Alarms Administrator Constructor Operator Viewer
Export Alarm Information Allowed allowed allowed
Get More Alarm Information Allowed allowed allowed
Retrieve Public Archive Allowed Allowed allowed
Navigation -> Current Usm Allowed allowed allowed
Navigation -> Topology Manager Allowed allowed allowed
Navigation -> External Application Allowed allowed allowed

Topology Management
Administrator Constructor Operator Viewer
New Map Allowed Allowed Allowed
Map Parameters Allowed Allowed Allowed
Local Persistency Allowed Allowed Allowed
Save Map Allowed Allowed Allowed
Save Map As Allowed Allowed Allowed
Restore Map Allowed Allowed Allowed
Delete Map File Allowed Allowed Allowed
Map Management (*) Allowed Allowed Allowed
Save Map As Allowed Allowed
Save Map Allowed
View
Edit Filters Allowed Allowed Allowed Allowed
Activate Filter Allowed Allowed Allowed Allowed
Edit Command Filter Allowed Allowed Allowed
Activate Command Filter Allowed Allowed Allowed
Related Views Allowed Allowed Allowed Allowed
View Parameters Allowed Allowed Allowed Allowed
Display Options Allowed Allowed Allowed Allowed
Edit
Create Child View Allowed Allowed Allowed
Add Connection Allowed Allowed Allowed
Add Symbol Allowed Allowed Allowed
Network Layout Allowed Allowed Allowed
Frozen Mode Allowed Allowed allowed
Select All Allowed Allowed Allowed
Delete From All Views Allowed Allowed allowed
Operations
Information Allowed Allowed Allowed Allowed

Access State Allowed Allowed Allowed
Show Statuses allowed Allowed Allowed Allowed
Mib allowed Allowed Allowed
Time -> Get … allowed Allowed Allowed Allowed
Time -> Set … Allowed Allowed Allowed
Administration -> Lock Allowed
Administration -> Unlock Allowed
Supervision Allowed Allowed Allowed
Set ACD Allowed Allowed
Resynchronize Allowed Allowed Allowed Allowed
Change Supervised NE Address Allowed
Upload Remote Inventory Allowed
Display Remote Inventory Allowed
Ping NE Allowed
Remote Inventory Wizard Allowed
Tools
Global NE Inventory Allowed Allowed Allowed Allowed
NE Population Allowed Allowed Allowed Allowed
Map Filter Allowed Allowed Allowed Allowed
Navigation To Alarms Allowed Allowed Allowed Allowed
Navigation To Equipments Allowed Allowed Allowed Allowed
Monitoring Allowed Allowed Allowed Allowed
Diagnose Allowed
(*)
Administrator Constructor Operator Viewer
Map Management (*) allowed allowed allowed allowed
Map Retrieve allowed allowed allowed allowed
Map Modification allowed allowed
Map Deletion allowed allowed
Map Unlock allowed allowed

SEC Management
The Security Database management is allowed only for an Administrator profile.
SMF
SMF Administrator Constructor Operator Viewer
Operators Administra- Allowed

tion
user
Create Allowed
Update Allowed
Delete Allowed
Log Management Allowed Allowed Allowed
Log file
Log file info Allowed Allowed Allowed
Log record print Allowed Allowed Allowed
Log file archive Allowed Allowed Allowed
Log file delete Allowed Allowed Allowed
Log record
Log record filter Allowed Allowed Allowed
Log record update Allowed Allowed Allowed
Log record info Allowed Allowed Allowed
Trace Management Allowed Allowed Allowed
processes
Edit trace level Allowed Allowed Allowed
Trace file
Static view Allowed Allowed Allowed Allowed
Dynamic view Allowed Allowed Allowed Allowed
Reset view Allowed Allowed Allowed Allowed

Failure Management Allowed Allowed Allowed
Workstation
Do a Snapshot Allowed Allowed Allowed
Os Snapshot
Save Tape Allowed Allowed Allowed
Lock Allowed Allowed Allowed
Unlock Allowed Allowed Allowed
Delete Allowed Allowed Allowed
Options
Set Max Nr of Allowed Allowed Allowed

Snapshot
Scheduler Management allowed
plan
New allowed
Edit allowed
Validate allowed
Stop allowed
Delete allowed
Backup Management
job
New allowed
Edit allowed
Delete allowed
Run allowed
Restore Management allowed
load
All allowed allowed allowed Allowed
Disk allowed allowed allowed Allowed
Tape allowed allowed allowed Allowed
Backup

Status allowed allowed allowed Allowed
Restore allowed
Delete backup allowed
Cleanup Management Allowed Allowed allowed
Cleanup
Details allowed Allowed allowed
Clean allowed allowed allowed
Max Operator Logged Allowed

5 BACKUP RESTORE FEATURE
5.1 Overview
5.1.1 Disks Full Backup and Full Restore
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. Such an operation is recommended before doing
a new installation starting from scratch to keep a copy of the 'running' System and after the new installation
to keep a copy of the 'starting' System without the final configuration.
The complete description is reported in the Installation Guide.
5.1.2 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 disks 1353NM feature described in prevoius section.
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.
Backup of one functional domain doesn't remove existent backup of other differents functional
domains.

Backup Restore Feature 3AL 89082 BAAA Edition 01 101/270
5.1.3 Backup Performing Time
This section will suggest the backup performing time, that is when backup should be scheduled to have
the less loss of date in case of problems. The backup operations can be scheduled to be run periodically,
as explained in next chapter.
– Network backup should run every day;
– Alarms files and Performance Monitoring data backup should run every week:
– Operators (Users) backup should run every month or alternatively when modifications are made
on the defined users.

102/270 3AL 89082 BAAA Edition 01 Backup Restore Feature
6 PERIODIC ACTIONS (SMF SCHEDULER)
6.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
displayed to manage the scheduling jobs. From the Scheduler window a new plan can be created or an
existing plan can be modified, validate or deleted.
Figure 56. SMF Scheduler

Periodic actions (SMF scheduler) 3AL 89082 BAAA Edition 01 103/270
6.1.1 Access rights
Only the administrators (admin group) can access to these tools, from the Master station.
Table 7. Periodic Options: Access rights
SMF Command Access rights
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
6.2 Scheduled actions

This function allows to run backups and purge operations periodically to have the job done at the planned
time. Scheduler plan can be created to perform standard operations that should be repeated.
– Possible commands that can be scheduled in a plan are :
1) Periodic Action Tester

2) Backup ALL job : a full backup
3) Backup Network job : Network data backup
4) Backup AS job : Alarms data backup
5) Backup PM job : Performance Monitoring data backup
6) Backup Software Download job :
7) Backup Log Management job : Log data backup
8) Backup System Configuration job : System configuration data backup
9) Backup Operator job : user data backup
10) PurgeHistAS : purge of Historical Alarms
11) CleanPerfDataFiles : clean archived old PM Data files
12) Cleanup of Core/Trace/Log Domain : clean all Core/Trace/Log domain files
13) PMDATAARCHIVE
6.3 Optional scheduled actions

Backup actions in order to keep a reasonable amount of space free can be scheduled to transfer back-
upped data on tapes or CDs and purge the older data to free the disks.

104/270 3AL 89082 BAAA Edition 01 Periodic actions (SMF scheduler)
7 SYSTEM LOG MANAGEMENT
7.1 SMF/Command/Event Logs Management/Visualization

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

System Log Management 3AL 89082 BAAA Edition 01 105/270
7.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
syslog.
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 7.4.
• 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.
7.1.2 Management of log files
7.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

106/270 3AL 89082 BAAA Edition 01 System Log Management
7.1.2.2 Files state
Several logs files exist, they can be in the 4 different states (see Figure 58.):
– 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 pre-
defined size, the log file is renamed with the .old extension.
axadmin is notified by mail when file is created. The message is "xxx.old log file created, please
archive log".
– Saved log (file name "name.gz"). There can be several saved log files saved at different dates. Saved
log files are compressed by gzip. The file name (name) is choosen by the user.
– Temporary log (file name "/tmp/axtmp.name.date"). It corresponds to saved log files decompressed
for visualization. They are removed after usage.
automatic
current log overflow log
automatic
manual or sched- manual or scheduled
uled
archived log deleted overflow log
manual
deleted archived log
Figure 58. 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 con-
tinues 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.

7.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.
7.1.3 Access rights
Table 8. Log Management: Access rights for different User Profiles
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

7.1.4 Log Tools
Logs Management functions can be accessed through Actions |--> SMF |--> System Log Management
option.
Listed below are the tool names and a short description.
Table 9. Log Management Options
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.

7.1.5 Log Management Files
File Location File Name Description
/usr/Systems/1353NM_<Inst- EPIM_Watchdog_1353NM_3- EPIM Watchdog log file

Numb>/maintenance/log/ 7.0_.log
/usr/Systems/1353NM_<Inst- acdbm.log Access Control Database Admin-

Numb>/maintenance/log istration log file (Security Log)
/usr/Systems/1353NM_<Inst- acsi.log Access Control System Informa-

Numb>/maintenance/log tion Log (Security Log)
/usr/Systems/1353NM_<Inst- ascurusm.log AS log file (Other Log)

Numb>/maintenance/log
/usr/Systems/1353NM_<Inst- jacorb.log Jacorb application log file

/usr/Systems/1353NM_<Inst- lss.log Local security log file

Numb>/maintenance/log (Security Log)
/usr/Systems/1353NM_<Inst- pmc2.log PMC log file

Numb>/maintenance/log (System Log)
/usr/Systems/1353NM_<Inst- pmds_db.log PMDS database management

Numb>/maintenance/log log file
/usr/Systems/1353NM_<Inst- pnmusm.syslog PNM Log file (Command log)

/usr/Systems/1353NM_<Inst- retix_ul_1353NM_3- Retix_ul log file

Numb>/maintenance/log 7.0_lan_0_0.log
/usr/Systems/1353NM_<Inst- smf.log SMF log file

/usr/Systems/1353NM_<Inst- swdl Software Download log file


7.2 Failure Management
All the users can access this function, via the SMF, from any station.
7.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.
7.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.
7.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
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.

7.2.4 Failure Tools
Failure Management functions can be accessed through Action |--> SMF |--> Failure Management fea-
ture.
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.
7.2.4.1 Files saved with snapshot operation
A snapshot is created on the master workstation, it contains a compressed tar file for the master work-
station and one for the client (if the command was run for both) that contains the following “.tar.gz" files.
The files are located in the directory
/usr/Systems/1353nm_<Inst_numb>/maintenance/failure/local/
while in the directory
/usr/Systems/1353nm_<Inst_numb>/maintenance/failure/global/
a tar file with a name of type yyyymmddhhmm is saved.
– Os-Kernel_log.tar.gz : compressed tar file of the area /alcatel/Kernel/maintenace/log; log files con-
cerning Kernel operations are stored in this area (Customizatin procedure, Configuration, User Cre-
ation, also error are reported here);
– Os-Kernel_trace.tar.gz : compressed tar file of the area /alcatel/Kernel/maintenace/trace; trace

files concerning OS-Kernel processes are stored in this area;
– System_log.tar.gz : compressed tar file of the area /usr/Systems/1353NM_<IN>/maintenace/log;

this area contains log files concerning the applications running on the configured Subsystem
(1353NM_x), i.e. SMF, PMC, SEC, PNM, ...
– System_trace.tar.gz: compressed tar file of the area /usr/Systems/1353NM_<IN>/maintenace/

trace; this area contains trace files written by the applications running on the configured Subsystem
(1353NM_x), i.e. SMF, PMC, SEC, PNM, ...
– SEC-failure.tar.gz : compressed tar file of the area /usr/Systems/1353NM_<IN>/SEC/repository;

7.2.4.2 Options
Selecting the menu item Options |----> Set Maximum the following window will be displayed to set the
maximum number of snapshot saved on the server. The “OK" button confirms the changes
Figure 59. 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/
yyyymmddhhmm.
– Copy into the yyyymmddhhmm directory all the necessary files.
– Create the header file.
– Write to the header file.
– If the number of present directories is greater than the maximum number specified , then a clean-
up script is initiated, removing directories in chronological order until the directories number equals
the maximum number specified.

7.3 Trace Management
All the users can access to this function, via the SMF, from any station.
7.3.1 Traces Management tools
The following table summarizes the tools provided to manage traces:
Table 10. Trace Management: tools
SMF Command Tool Description
Change Trace Level To set the trace level of each apman process
Reset Cyclic Traces This tool allows to empty all circular trace files
7.3.2 Traces Management files
Trace management files are located in the directory
/usr/Systems/1353NM_<Inst_Numb>/maintenance/trace/.
Trace files have several extensions posssible : .data, .trace, .err, .out, .dataflow.
Applications that writes trace files are :
– emlims
– PNM (IM and USM)
– PMC2 : Process Monitoring
– AMV
– Simcon
– FWK processes
– PMDS
– Software Download
– USM
– lss
– Retix
– Xcc
– SMF

7.3.3 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 60. System Trace Management selection

7.3.3.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
Figure 61. Trace Management: Trace levels
Figure 62. Trace Management: Trace levels setting

The default setting for trace level in trace.cfg 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 .

7.4 Command Log Viewer
Selecting a System Instance icon on the TMN-OSs menu and selecting the menu function Actions |-->
Command Log Viewer as shown in the figure below, the Command Log Viewer interface will be dis-
played.
Figure 63. Starting CLV
Figure 64. Starting CLV
7.4.1 Parse Command Log
Generally, after CLV is started, following figure is shown (see Figure 65.). In Log Files Panel, all the avail-
able command log file(s) are listed.
CLV can parse command log file(s) on the master or client workstation. The location of the command 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 65.).

Figure 65. Select Target Log File
The operator can click the Parse button to parse the target log file. During the parsing period, the Parse
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.
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 in following
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).
7.4.1.1 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 it next time.
7.4.1.2 Simple Filter
Simple filter is simple but more convenient and intuitive (see Figure 66.).

Figure 66. Simple Filter
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 operator among the
filter items is the AND operator.
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,
Machine is NM70 and Command is “Access State Cmd", at the same time, the filter has been con-
structed. (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
extraction 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 in fol-
lowing two ways:

a) Press the Ctrl key on the keyboard while use mouse click the target items in the item list
(continuous items or discontinuous items).
b) Press the Shift key on the keyboard while use mouse click the target items in the item list
(continuous items).

7.4.1.3 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 67.).
Figure 67. 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.
7.4.1.4 Variable
By clicking on a 'Variable' cell, a combo-box is shown with all possible subjects (see Figure 68.):
Figure 68. Selecting the subject

7.4.1.5 Relational Operators
By clicking on a 'Compare to' cell, a combo-box is shown with all possible relational operators (see Figure
58):
Figure 69. Selecting the relational operator
7.4.1.6 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 70. Selecting a value of comparison
7.4.1.7 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.

7.4.1.8 Operators
By clicking on an 'Operator' cell, a combo-box is shown with AND/OR/Stop operators (see figure 60):
Figure 71. 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.

7.4.1.9 Temporary filter
Before the filter is saved manually, it's only a temporary filter (See Figure 61).
Figure 72. Temporary Filter
Operator can click the Save button to save the temporary filter. After the temporary filter is saved, the tem-
porary 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.

7.4.1.10 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 73. Selected Saved Filter
Operator can construct the temporary filter based 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 from the log used to construct the persistent filter,
the persistent filter may be not applicable for the selected target log file. But CLV will not check
that.
7.4.1.11 Display and ouput result
The filter result can be displayed and output in two different ways : displayed with Browser or displayed
in a table.

7.4.1.12 Display result with Browser
If the user selects Output to HTML button, the extraction result will be displayed in the Browser (see
Figure 63).
Figure 74. Extraction result

7.4.1.13 Display result with table
There are the 4 parts in the Command Result List window (see Figure 64).
Top part is menu of the window
Part 2 is the result statistics information
Part 3 is the extraction result list
Bottom part is the selected record information.
Figure 75. Extraction result list

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

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

7.4.1.16 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 77. Detail information
7.4.1.17 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.

7.4.1.18 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.
7.4.1.19 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.
7.4.2 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 78. Print dialog
N.B. User has to input the target printer name when user needs to print the file to printer.

7.4.2.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 a dif-
ferent display scale from 10% to 400%.
Figure 79. 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.
The button is useless at present.
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.
7.4.2.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-
>Export…in Detail Info window or Action ->Export… in Command Result List window).
7.4.2.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 80. Export the selected command result list to text file

7.4.2.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 81. Export of the selected command record detailed info to text
7.4.2.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 82. Display online help

7.4.2.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 83. Exit CLV confirmation dialog

7.5 Cleanup
The cleanup facilities are accessible to the administrator via the SMF command, from the Master station
only.
Figure 84. Navigation to the Cleanup tool
Moreover periodic system actions (cron) may be also run to avoid excessive increase of data collected
by the system or the operators.
7.5.1 General
The safety of 1353NM system needs to limit the number and size of files created for management pur-
pose. 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 con-
trolled 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.
7.5.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/Systems/1353NM_<Instance_Number>/restore,
/usr/Systems/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/Systems/
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_Number>/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/Systems/
1353NM_<Instance_Number>/maintenance/core, and core resulting of panic unix error within /
var/adm/crash.
– EFD
Concerns all the files for EFD domain.
– Temp Files
7.5.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 85. Cleanup
Before starting a cleanup action, the operator can get more informations about the files to delete:
7.5.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 86. Cleanup - Details
Click on Close button to close and return to main window.

7.5.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 87. Cleanup - Clean - Error: No Selection
Figure 88. Cleanup - Clean - Confirmation

Click on Yes to confirm: starts the action.
Messages are displayed in the 'Message Area'.

7.5.4 Cron actions
Periodic tasks are defined into the configuration file /usr/Systems/1353NM_x/SMF/tools/cleanup/conf/

cleanup.cfg. It uses the crontab command and can be changed only by an administrator with unix com-
mand.
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
– removing of Failure directory older than 1 month.
– removing of Historical alarms older than 90 days.

8 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 displayed
as shown hereafter:
Figure 89. System Management Menu

System Data Management 3AL 89082 BAAA Edition 01 143/270
8.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 Data Management functionalities.
Table 11. Local data management: access right for different User Profiles
SMF Command Access rights Function in smfSH application

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 config- admin SwdServCfg
uration
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 admin and constructor ChgFreeObsAssign
Assigned
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 Configura- admin wx_ipconf
tions
Change user label format admin ulformat

144/270 3AL 89082 BAAA Edition 01 System Data Management
8.2 Overview
8.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 90.); only
the window title and the action button differ depending on the required function.
Figure 90. 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.
8.2.2 Constraints
Some functions needs to stop and restart the whole system or the EMLIM process managing the con-
cerned NE.
8.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.

8.3 Data Mangement - Configuration
The following described functions are actived from TMN OS Actions --> 1353NMAdmin --> Data Man-
agement --> Configuration.
Figure 91. System Management selection
The following window will be displayed :
Figure 92. System Management Tools selection

8.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.
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.
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.
When clicking on the option, the following window is displayed:
Figure 93. Diagnosis of audit of the MIB
Select the NE to diagnose the audit (see paragraph 8.3.1). 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.

Figure 94. MIBs differences
The following pull-down menus are available on the top left of the window.
File Search
Print Find...
Quit Clear
Figure 95. 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 96. Find dialogue box
• 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).
• 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 97. 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 .

8.3.2 Display SEN MIB
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 98. 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 99. SEN MIB
The possible operations by using the pull-down menus on the top left of the window are the same as for
the previous paragraph.

8.3.3 Upload Failure Diagnosis
This tool shows the incoherencies detected in Nectas data (e.g. connections using same TPs, connec-
tions 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 100. Upload Diagnosis Failure
Select the NE as given in paragraph 8.3.1.
The incoherencies are displayed in red colour to be easily visualized.
Figure 101. Upload Diagnosis Failure - Diagnosis

8.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 102. Enable RPS Switch
Select the NE (see paragraph 8.3.1) and click on Enable.
Figure 103. Enable RPS Switch - Result

8.3.5 Overhead byte Configuration
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 104. Overhead byte configuration option
Select the NE as given in paragraph 8.6 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.

Figure 105. Overhead byte configuration

The user can select the Card and OH Byte (in the RSOH or MSOH) used for each functionnality to con-
figure. The possible value for the Card and OH Byte depend on the type of NE managed and on the chan-
nel. 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.

8.3.6 LAPD Configuration
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 106. LAPD configuration window
Select the NE as given in paragraph 8.3.1 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.

Figure 107. LAPD configuration

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.

8.3.7 Change ASAP
This option allows the copy of the ASAP from one NE to another.
When clicking on the option Change ASAP, the following window is displayed:
Figure 108. Change ASAP window
– Select the Ne Family and NE Type then click on the Filter push-button.
To have the complete list of NEs, click on the Filter push-button.
– Select the NE source in the displayed list (see Figure 109.).

Figure 109. Change ASAP window - NE source selection
– Click on the Ok push-button: the following window is displayed showing that the ASAP table of the
selected NE (source) is retrieved.
Figure 110. 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 110.) is displayed showing that the Change ASAP
operation is running.
If the NE source and destination are identical, an error message is displayed.
The EMLIM process associated to the selected NEs must be stopped, otherwise an error message
is displayed.

8.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 111. 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 112. Sync Source Selection - Selecting the synchronization source
Click on the Equipment Type option button then select an option. If the selected option concerns the SSU
feature, the windows becomes as follows (SSU Quality option button enabled).

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

8.3.9 Address Configuration
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 114. Address Configuration
– Select the Ne Family and NE Type then click on the Filter push-button.
To have the complete list of NEs, click on the Filter push-button.
– Select the NE source in the displayed list (see Figure 114.).

Figure 115. Address Configuration - NE source
– While running, an intermediate window is displayed.
Figure 116. Address Configuration - Initialisation on going
Then the Address window is displayed.

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

8.3.10 Change assignment state for QB3* NEs
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).
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.
There is no change for all the modifications of the configuration which had made the assignment
state turn to "Assigned" (such as a modification of payload or a NAP upload).
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 118. Change assigned to observed window
The complete list of NEs (shown above) is displayed only after clicking on "Filter".
Multiple selection is allowed.
If the relative process has not been stopped, a window may be displayed to warn the operator that the
operation can only be performed if the process is stopped.
During the Change state operation, information are displayed in the list box.

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

8.3.11 Switch Old/New Practice
This option allows the operator to change the name of the emlim persistency file during a migration phase.
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 120. Switch Old/New Practice
Select the NE as given in paragraph 8.3.1 to choose the NE on which the switch old/new practice operation
is to be done.
The following confirmation window is then displayed:.
Figure 121. Switch Old/New Practice confirmation window

Click on the Yes or No push button to confirm or cancel the switching.

8.4 Performance Operations
These Performance operations are activated from the menu Performance from Data Management as
shown in the figure below :
Figure 122. Performance operations selection

8.4.1 Save TP
This chapter is applicable to QB3* NEs only. In Q3 NE management the EMLIM process
manage a persistency file of its local MIB which includes the list of current started TPs in
Perf in NE
Save in OS the list of current started TPs in Perf in NE. It creates a new file restart_NE_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 123. Save TP
Select the NE (see paragraph 8.3.1) and click on Save.
restart_NE_label_TP.dat files are backupped when a Network Backup is required.

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

8.5 NECTAS
The NECTAS functions can be reached from TMN OS --> 1353NMAdmin as shown in following figure
Figure 126. NECTAS functions selection
8.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
modifications performed, because, as there is no control on the coherence of the tables,
an inconsistency may occur when the EMLIM try to build the NE again and it may result in a
crash. This operation should be done only by Alcatel personnel.
The tool is run by typing the command in a command shell or with a 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.
Figure 127. 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.
Figure 128. NECTAS Decoding - Show
Edit : The correct result of this functionality is to display a window showing the decoded NECTAS files

Figure 129. NECTAS Decoding - Edit
– The button Save re-writes the file even if no modification has been done.
This update does not affect the file used by the EMLIM process, but only the working file of the tool.
– The button Quit closes the window.
Encode: The correct result of this functionality is to apply the previously saved modifications of the
decoded NECTAS files on the file used by the EMLIM process.
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 its working directory, for the selected NE.
– Another message giving an information from PersBrowser in case of failure during the encoding
operation.
8.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 130. NECTAS Comparison (first NE)
– Click on OK to select the first NE.
Figure 131. NECTAS Comparison (second NE)
– Click on OK to select the second NE.

If the tool has correctly run, 2 cases may occur:
a) There are no differences between the NECTAS tables of the 2 NEs.
Figure 132. 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 133. 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:

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

8.6 Equipment
This function accesses some actions on equipments. Starting from TMN OS -->
1353NMAdmin the following steps leed to the desired function
Figure 135. System Management - Equipment

8.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 136. Set Offline Board

8.6.2 Upgrade Offline Board
after restart, the changes are taken into account. This function applies to 1664sm 2.1 only, allowing to
update a tributary board to its UP version.
Figure 137. Upgrade Offline Board

8.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 138. Set Offline Signal Label

8.7 NE Administration
This group of functions can be reached starting from TMN OS --> 1353NMAdmin as shown in following
figure :
Figure 139. System Management - NE Administration
8.7.1 1615BCE Configuration
Please refer to the chapter ‘1615BCE Management’ in the document [1]
8.7.2 FT Scheduler
Please refer to the chapter ‘File Transfer Scheduler’ in the document [1]
8.7.3 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, PREA, ...) obtaining a compound software package (SDH+Specific-Services) called OMSN
package.
The software package built by this tool can be used by the Software Download procedure to load a OMSN
NE. The data are saved on the master workstation in the directory :
• /usr/Systems/1353NM_<IN>/swdl/swdlserv/data
After the installation, the software package is ready to be downloaded on the NE (from NE USM or from
the scheduler) : in case of Add on, the package to be selected ends with an E (extended).
To install the NE SW package in 1353NM the CD containing the SW should be inserted in the CDROM
drive.

8.7.3.1 Creation of an OMSN package
The SDH panel lists all the SDH packages installed on NM by the SRVADMIN tool:
Figure 140. SDH software package panel
The SERV. SPEC. panel lists all available Specific-Service packages installed by SRVADMIN tool:

Figure 141. SERV. SPEC. panel
In order to build a new OMSN package the following steps have to be done.
In the SDH panel (Figure 141.), 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 142. 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 143. OMSN package panel
If a compatible add-on is declared ‘NOT installed’, the “Add" button is enabled. Press the “Add" button to
plug the selected Service-Specific software package into the OMSN package. After the operation is com-
pleted, the Service-Specific package is reported as "Installed" (in the OMSN package) in the right-side list.
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.
Note that all packages (SDH, Specific-Service and OMSN) can be discarded by entering the appropriate
panel, selecting the desired item, and pressing on "Discard" button. A confirm request is always displayed
before proceeding.

8.7.4 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.3 is built. To have
an exhaustive description of the function see document “1350 System Rel. 7.3 Administration Guide".
Figure 144. List Gateway NE Wizard

8.7.5 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.3 is built.
Selecting Ping NE from the NE Administration menu, the following window will be displayed:
Figure 145. Ping NE
The area shown in the figure lists the created NEs and the relevant NSAP address. New NEs can be add
manually specifying User label and NE address. Select the NEs to ping in the list and the command button
<Ping Selected>. The following window will appear displaying the ping result :

Figure 146. Ping NE result
8.7.6 AC Viewer
Please refer to the relevant chapter ‘AC Viewer’ in the document [1]

8.7.7 OSI over IP Tunneling
8.7.7.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 example,
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.
8.7.7.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.

8.7.7.3 Main window
Selecting System Management -> NE Administration -> IP tunneling , the IP Tunnel Configuration Appli-
cation window is opened:
Figure 147. 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 8.7.7.6 ) is dis-
played.
– the Actions section has 5 buttons:

• Create to create an IP tunnel
• Delete to delete an IP tunnel
• Show Listto 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.

8.7.7.4 Creating an IP tunnel
Pressing the Create button in the main window, the Create IP Tunnel window is displayed:
Figure 148. 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:
Figure 149. IP tunnel successful creation message

8.7.7.5 Listing IP tunnels
Pressing the Show List button in the main window, the IP Tunnel List window is displayed:
Figure 150. 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.

8.7.7.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 151. IP Tunnel Detail window
The following data are showed:

– channel startpoint : Supervision Area, IP Tunnel identifier
– channel endpoint : GNE Label Name (if declared as GNE), IP address anyway
– channel status : active / progress / undefined.
8.7.7.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 152. 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.
8.7.7.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.

8.7.8 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/Systems/
1353NM_x/simulator/simcon/data/param.cfg; the parameter value must be suitably set according to
the system resources;
– stop/start simcon process.
Selecting On Board Simulator Monitoring on the System Management menu, the following window will
appear:
Figure 153. On Board Simulator Monitoring window
The figure above shows that 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 shown on the figure above.
If there are OBS processes active (green arrow), for each simulated NE the following information is dis-
played :
– NE name, type & release
– emlim name
– NE group & Id
Click on the Exit button to exit from the On Board Simulator monitoring window.

8.7.9 Command Log Viewer
Please refer to chapter 7.4 ‘Command Log Viewer’ of this document.
8.7.10 IP over OSI Tunneling
Please refer to the relevant chapter ‘IP over OSI Tunneling’ in the document [1]

9 SMF FOR OMSG
SMF functions are available on 1353NM for the management of 1641SX 6.x /1664SX 2.x and 1674 Lamb-
daGate; they are not needed for 1678MCC.
SMF functions for OMSG can be accessed starting from TMN OS menu Actions |--> 1353NMAdmin :
Figure 154. SMF functions for OMSG administration
As for their description, please refer to the set [8] of documents.

SMF for OMSG 3AL 89082 BAAA Edition 01 197/270
198/270 3AL 89082 BAAA Edition 01 SMF for OMSG
10 ALCATEL NETWORK TIME PROTOCOL
10.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.
10.1.1 ANTP behaviour
ANTP is an Alcatel proprietary protocol which allows to have a very precise real time clock alignment
between the NEs and a reference source (ANTP server). It is bases on the algorithm implemented by NTP
(see [11]) 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
server 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.

Alcatel Network Time Protocol 3AL 89082 BAAA Edition 01 199/270
10.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 distrib-
uting 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 155.). 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
155.) and with not co-located ANTP servers (Figure 156.). The latter solution allows higher resilience
against any failure.
Refer to ANTP Functional Specification for protocol details: protocol architecture and ANTP
message format.

200/270 3AL 89082 BAAA Edition 01 Alcatel Network Time Protocol
OS OS OS OS
GP
clock source
NTP protocol
ANTP protocol
Figure 155. ANTP system architecture with co-located ANTP servers

Alcatel Network Time Protocol 3AL 89082 BAAA Edition 01 201/270
OS OS OS OS
GP
clock source
NTP protocol
ANTP protocol
OS
GP
clock source
ANTP protocol
NTP protocol
Figure 156. ANTP system architecture with not co-located ANTP servers

202/270 3AL 89082 BAAA Edition 01 Alcatel Network Time Protocol
11 MAINTENANCE
The procedure sheets are divided as follow:
• Preventive maintenance
• Corrective maintenance
• Failure management
• Maintenance operations
• Upload failure
• Advanced network management
• Troubleshooting

Maintenance 3AL 89082 BAAA Edition 01 203/270
11.1 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
located 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(direc-
tories) 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.

204/270 3AL 89082 BAAA Edition 01 Maintenance
11.2 Preventive Maintenance
The Preventive Maintenance sheets are the following:
• Power supply failure
• File system full
• Hardware failures

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 in the 'Installation
Guide').
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.

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 LOG MANAGEMENT chapter, section
Cleanup).
The cleaning up has to be performed as often as possible without delay.
For any doubt, contact the ALCATEL support.

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.

11.3 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

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.

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.

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.

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.

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.

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.

11.4 Maintenance operations
The Maintenance Operations sheets are the following:
– Power off the whole OS
– Power off one machine
– Change network area of a workstation
– Performance Monitoring database administration

POWER OFF ONE MACHINE
Operations
– Warn the users.
– Stop all processes of the machine.
– Shutdown the machine as explained in the Installation Guide
– Power off the machine.

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.
In this case the OS address must be changed in the beginning.
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.

PM PURGE
All the operations on the PM database are now possible using a graphic tool. This tool is activated starting
from TMN OS menu follwing Actions --> SMF --> PMDS DB Administration
Prerequisites
– MySQL process running
Manual purge
The manual purge operation on PM data can be performed activating the PMDS DB Administration win-
dow. The following window will be displayed :
Figure 157. PM DB Administration

Selecting the option ManualPurge a window will be displayed as shown in the next figure where the mea-
surement to purge can be selected.
Figure 158. PM Manual Purge Selection
On this window three selection can be made to purge the data :
– the database to be purged (ATM, ETH, SDH)
– the Measurement Category to purge (All, 15min, hour, day)
– From <date> to <date>, the interval of date to purge
The <Execute> button runs the purge command.
The following figure shows a more detailed selection for this command:

Figure 159. Manual Purge on ATM database

Statistics
This command will show statistics data about the selected databases. The statistics includes: Allocate
Space; Used Space; Ratio and rows of records in important tables. The window displayed reports the sta-
tistic data. The selection 'All sites' display statistics about all PM databases (ATM, ETH, SDH), while the
selection of a single database displays the data for the selection.
Figure 160. PM databases statistics

Optimize
The Optimize operation on PM data can be performed also activating the PMDS DB Administration win-
dow. The window below will be displayed. Selecting the optimize option a defragmentation is carried out
on the selected database.
Figure 161. Optimize operation on PM database

Threshold_EM
This command can be used to set the threshold of the DBSizeAlarm function for all PM databases.
The low value threshold is the value of threshold to show WARNING. The unit is KByte
The exhaust valuethreshold is the exhaust value to show ALARM. The unit is KByte
The window to modify these values is shown in the figure below
Figure 162. Set Threshold for PM databases

12 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.
– 1692 Software Download procedure
– Supervision not started for MDR 8000 Rel.2.0 NE

Troubleshooting 3AL 89082 BAAA Edition 01 225/270
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.

226/270 3AL 89082 BAAA Edition 01 Troubleshooting
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.

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

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_number>/

maintenance/log/PM-logfile which logs all actions with the Oracle database.
• NE bug...

OS ISOLATION
Symptoms
- Broken red icon on PNMUSM.

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

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 man-
agement).
– 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.

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.

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.

REPORTING AN NM PROBLEM
Informations to provide to Alcatel support:
– NM version:
• Output of TMN OS menu OS|--> System Information.
– 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.

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

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

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.

1692MSE 1.0 Software Download procedure
This workaround is described to allow solving the problem that SWDL procedure doesn't work for NE
1692MSE 1.0.
The following workaround procedure was tested on 1353NM 7.0.x with a NE 1692MSE running SW ver-
sion 1.0.22, on which has been downloaded the SW package V. 1.2.5.
To allow SWDL procedure to work execute following steps :
1) On 1353NM the SW package (ex: 1_2_5) must be correctly installed in :
/usr/Systems/1353NM_xx/swdl/swdlserv/data/1692MS/
2) Create a new user named swd with password swd, using HP-UX SAM application (that
allows definition of a short password);
3) In the user home directory: /home/swd/ create a link named1692MS to /usr/Systems/

1353NM_xx/swdl/swdlserv/data/1692MS : Please note that the directory must have read and
execute rights for everyone.
4) The directory should be listed as follows :
lrwxr-xr-x 1 swd users 48 Dec 17 11:34 1692MS -> /usr/Systems/1353NM_XX/swdl/

swdlserv/data/1692MS
5) From 1692mse1.0 NE Equipment view access Menu item : Download Server Access Config-
uration
- insert user: swd
- insert psw : swd
- insert your 1353NM IP address : xxx.xxx.xxx.xxx
- insert port: 21
- insert path : 1692MS/1_2_5
and confirm.
6) From 1692mse1.0 NE Equipment view access Menu item : Init Software Download
- Select release 1_2_5
- check "force download" box
- confirm with "Init download" button

Additional note:
At this point the SoftWare download session starts and will proceed without errors. After the end of down-
load phase, the new Software version may be Activated from SoftWare status dialog box, as usual. Just
after the activation is suggested to close the current 1692mse1.0 NE Equipment view and wait the equip-
ment restart and realignment.
The EMLIM will automatically detect the updated version of the equipment (check this information into
NE Info dialog box).

Supervision not started for MDR 8000 Rel.2.0 Network Element
This workaround should be already done before starting the Subsystem after System Configuration
phase. If for any reason the operation isn't carried out, follow this steps :
1) Start Process Monitoring application,
2) Stop the corresponding Snmp emlim,
3) Carry out the operations described in paragraph 3.5.6 on page 59.
4) Restart the snmp emlim.

13 PROCEDURES
13.1 Failure management

The Failure Management sheet is the following:
– Failure management - Step by step procedure

Procedures 3AL 89082 BAAA Edition 01 241/270
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.

242/270 3AL 89082 BAAA Edition 01 Procedures
13.2 Upload failure
The Upload Failures sheets are the following:
– Minor inconsistencies
– Major inconsistencies - On NE side
– Major inconsistencies - From OS side

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.

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.

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.

13.3 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

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 main-
tenance.
– Transport layer
• Perform an OSI ping to check any OSI transport connection:
– from TMN OS:
• Perform the Ping NE option of Actions --> 1353NMAdmin --> NE Administration

menu in TMN OS menu.
– by UNIX:
• Run the script: /alcatel/<OSK_vers>/NMC/NECOM/<NMC_vers>/script/

axNEdiag.ptk where <OSK_vers> is OSK version, <NMC_vers> is NECOM ver-
sion.
– Advanced Diagnosis
• nettl wrapper to analyse network packets (run_capture).

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.

CHANGE ASSIGNED TO OBSERVED
Operations
– Stop the EMLIM managing the NE.
– Save the persistency file.
– Perform the Change Assigned To Observed option of the Actions --> 1353NMAdmin --> Data
Management --> Configuration menu in TMN OS (see paragraph System data management /
Change Assigned to Observed option).
– restart the EMLIM.

MISCELLANEOUS CONFIGURATIONS
Operations
– From Actions --> 1353NMAdmin --> Data Management --> Configuration menu, the following
options are available:
• Enable RPS Switch option to enable RPS related alarms in radio NEs,
• Overhead byte Configuration option,
• LAPD Configuration option,
• Change ASAP option to change Alarm Severity Assignment Profile of one NE,
• Sync Source Selection option,
• Address Configuration option to configure OS main and spare addresses and switchover
bytes.
– From Unix:
• NE batch creation.

Change check on NE Address unicity default
Starting from 1353NM Rel.7.0.14 P1 a check on NE Address unicity default is introduced in ’Set NE
Address’ operation with Topology Management application. To change this default setting, it is necessary
to perform following steps. The possibility is to force the check on NE Address at ’Start Supervision’ oper-
ation.
• Change directory to /usr/Systems/1353NM_<Instance_Number>/PNM/conf/pnmim/
• Edit the file param.cfg
• Search the parameter ACTION_CONTROL, the default value is FALSE. To force the check on
’Start Supervision’ set this value to TRUE.
• Search the parameter ADDRESS_UNICITY, the default value is TRUE. If it is not TRUE, set
it to this value.
• Check in the file for the existence of following line, this line should be present for the correct
run of the check mechanism
• TYPERELEASE_FILE “/usr/Systems/1353NM_<Instance_Number>/PNM/conf/pnmusm/Typ-
eReleaseDefinition”
• Save the modified param.cfg file.
• This operation can be done before starting 1353NM Subsystem or if already started, start Pro-
cess Monitoring apllication and stop PNMIM process and restart it again.

Migrated SH31 NEs : “Change NE name"
Introduction
This section describes the actions to be executed when performing the Change NE name procedure for
the NE's managed by emlimadmnr31 application. A specific tool is required in order to successfully
change the NE name of the NE's managed by this process. The installation steps and usage of this tool
are explained below.
Pre-Condition
This section is describing how to change a NE-name for a QB3*-equipment but managed by an emlim-
process of NR3.1, running on SH5 in backward compatibility mode. Execute this procedure only if your
equipment and emlim-process correspond to this description.
Installation
Once the tool is downloaded, it must be installed only on NM. It is not necessary to install it on RM. Follow
the steps below.
1) Copy the file 1353sh31_chname1.0.0.sdpkg in the directory /alcatel/DEPOT
2) Install the package (as user root) by the command:
.,root# swinstall -s /alcatel/DEPOT/1353sh31_chname1.0.0.sdpkg '*'
3) Wait for the installation to finish successfully, after which you will return to the command line
prompt. This could take a few minutes.
Create migration file
Now it is necessary to create a file, which contains the old NE names, and the names by which they will
be replaced. Please note that you can change several names at a time. This file will be used as a reference
for creating the NE inventory later. Note that the name must be correctly entered in the document.
Create a correspondence file migr.map (logged as axadmin or alcatel) :
...,axadmin# vi /tmp/migr.map
Example of file 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. This file will be used during
the migration.
Create NE Inventory
Before running the migration tool, we need to create an inventory file of all the NE's for which the names
will be changed.
1) Change directory:

...,axadmin# cd /alcatel/NMA/NAT/<version>/1353sh/tools/migration/script
or
...,axadmin# cd /alcatel/7.1/NMA/NAT/<version>/1353sh/tools/migration/script
Note: Starting from NR7.1 (1353NM rel. 7.0.10 P1 P2 P3) the directory is the second listed.
Make an inventory of NEs to migrate:
...,axadmin# ./migrUserlabel.pl inventory mapping /tmp/migr.map > /tmp/migr.inventory
Backup persistency files
The next step illustrates how to backup the persistency files, where the emlim groupid number is the id
number of the process, which manages the NE. Accessing the NE Directory ? NE info menu item in the
NM map display this value will be seen.
1) Make a backup of persistency files:
...,axadmin# ./migrUserlabel.pl -backup -group <emlim groupid number>
2) Repeat step1 for all emlimadmnr31_<groupid number> processes
Change NE Name
The change NE name action can now proceed.
1) Stop all the related emlimadmnr31 processes created via Process Monitoring: OS ? Process
Monitoring
Select the Process emlimadmnr31_<groupid number> and stop it.
2) Migrate the persistency file:
...,axadmin# ./migrUserlabel.pl -migrate -persistency -mapping /tmp/migr.map -group

<emlim groupid number>
3) Repeat step2 for all involved emlimadmnr31 processes.
Update 1353NM
1) Start all emlimadmnr31 processes that where previously stopped, via Process Monitoring : OS
--> Process Monitoring
Select the Process emlimadmnr31_<groupid number> and start it
2) Close all maps on PNM
3) Stop the Topology Manager process using Process Monitoring
OS --> Process Monitoring --> Topology Manger
Select the Process Topology Manager and stop it
4) Remove NE.db file:
...,axadmin# rm /usr/Systems/1353NM_<Inst_number>/PNM/data/NE.db
5) Start the Topology Manager process using Process Monitoring

OS --> Process Monitoring --> Topology Manger
Select the Process Topology Manager and start it
6) Migrate the thirdfiles (these are files containing the NE names that were changed):
...,axadmin# ./migrUserlabel.pl -migrate -thirdfiles -mapping /tmp/migr.map -group

<emlim groupid number>
Launch the command for all involved emlims.
7) Open the maps on PNM and check that the NE names have changed.

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.

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.

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.

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.

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
Password Expiration

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>

ABBREVIATIONS
ABBREVIATION MEANING
ACA Access Control Administration tool
ACD Access Control Domain
ALS Automatic Laser Shutdown
APS Automatic Protection Switching
AS Alarm Surveillance
ASAP: Alarm Severity Assignment Profile
ALMAP ALcatel MAnagement Platform
BER Bit Error Rate
CCLNP ConnectionLess Network Protocol
CDCC Data Communication Channel
CD-ROM Compact Disc Read Only Memory
CLNS ConnectionLess Network Service
CT Craft Terminal
DCN Data Communications Network
DS Degraded Signal
DWDM Dense Wavelength Division Multiplexing
ECC Embedded Communication Channels
EML Element Management Layer
EPS Equipment Protection Switching
FAD Functional Access Domain
FLS Frame Loss Second
Gbit/s Gigabits per second
GIF Graphics Interchange Format

Abbreviations 3AL 89082 BAAA Edition 01 263/270
GNE Gateway Network Element
HP-OV Hewlett Packard OpenView
HP-OVW Hewlett Packard OpenView Windows
HP-UX Hewlett Packard Unix
HP-VUE Hewlett Packard Visual User Environment
HTML Hyper Text Markup Language
IEEE Institute of Electrical and Electronics Engineers
IM Information Manager
Kbit/s Kilobits per second
LAN Local Area Network
LOS Loss Of Signal
Mbit/s Megabits per seconds
MIB Management Information Base
NAD Network Access Domain
NAP Network Access Point
NE Network Element
NML Network Management Layer
NTP NetworkTime Protocol
OAD Object Access Domain
OFS Out of Frame Seconds
PI Physical Interface
PPI PDH Physical Interface
PTM Path Trace Mismatch
RS Regenerator Section
SDH Synchronous Digital Hierarchy
SF Signal Failure
TMN Telecommunications Management Network
TN Telecommunications Network
USM User Service Manager

264/270 3AL 89082 BAAA Edition 01 Abbreviations
VC Virtual Container
XC Cross-Connect

Abbreviations 3AL 89082 BAAA Edition 01 265/270
266/270 3AL 89082 BAAA Edition 01 Abbreviations
INDEX
A N
ACD, 70 NECTAS Decoding, 172
ACD creation, 75
administator, 71
O
object, 69
C operator, 71
Change ASAP, 159 OS-Kernel, 61
constructor, 71
P
D patch STYL, 30
Diagnostic of audit of the MIB, 147 PM PURGE, 219
Display SEN MIB, 150 Process Monitoring, 61
profile, 71
E
Elementary OAD, 71 R
Enable RPS Switch, 152 Restart Perf Collect, 171
routing table, 36, 37
F
FAD definition, 77 S
function, 69 Save TP, 170
System FAD, 72
I
initiator, 67 T
IP routing, 33 target, 67
IP tunneling, 189
U
L users, 70
Local Data Management, 143
V
M viewer, 71
Maintenance
Corrective, 209, 247

Index 3AL 89082 BAAA Edition 01 267/270
268/270 3AL 89082 BAAA Edition 01 Index
CUSTOMER DOCUMENTATION FEEDBACK
The meaning of this section is to collect customer feedback about this handbook.
Scope of this activity is the improvement and innovation of customer documentation through the under-
standing of customer needs.
Your comments are welcome.
Please send your comment also if you appreciate the handbook.
You can send them to your Local Alcatel Technical Assistance Center.
They will be addressed to the team in charge of the relevant manual.
The following form supplies an example only of useful info, as a guide of the type of expected feedback.
It is possible fill part of the form, add other data and so on.
How to send feedback:
• copying the example form, filling it and sending it to your Local Alcatel Technical Assistance
Center. In this case handbook data are already available at the page bottom.
• using the same form available as a file in the relevant documentation CD-ROM, saving, filling
and sending it by e-mail to your Local Alcatel Technical Assistance Center.
• creating a dedicated form on paper or file and sending it to your Local Alcatel Technical Assis-
tance Center.
We’ll take your suggestion in account.
We reserve to modify consequently the handbook according to the corretness and congruence of the sug-
gestion and requests.

Customer Documentation Feedback 3AL 89082 BAAA Edition 01 269/270
CUSTOMER DOCUMENTATION FEEDBACK
Handbook Data
Handbook title, release,version:
Handbook type:
Handbook part number and edition:
General Feedback Evaluation
SUBJECT 5(max) 4 3 2 1 (min)
Total evaluation
Info quantity
Info quality
Info structure
Consulting facility
Layout
Chapters Feedback Evaluation
HANDBOOK PARTS 5(max) 4 3 2 1(min)
PREFACE
CHAPTER 1
CHAPTER 2
CHAPTER 3
CHAPTER 4
CHAPTER 5
CHAPTER 6
CHAPTER 7
CHAPTER 8
CHAPTER 9
CHAPTER 10
CHAPTER 11
CHAPTER 12
CHAPTER 13
Your Comments (stricltly necessary when value is less than 3):
Suggestion for Improvement

Which subject to deepen:
How to deepen:
Subject to eliminate or reduce
Other comments/suggestions
Errors Identified
Reader Info
Name:
Company:
Address:
E-mail:
Phone:
270 1353NM Rel. 7.3 Administration Guide

270/270 3AL 89082 BAAA Edition 01 Customer Documentation Feedback
All rights reserved.
Passing on and copying of this document,
use and communication of its contents is not permitted
without written authorization from Alcatel.
THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
ASSEMBLY INSTRUCTIONS
Total Pages: 270 + 6
NOTES: ---
COVER LABELS
(according to Alcatel Italy binder format)
Alcatel 1350 Management Suite
1353NM
Rel. 7.3
7.3.6P9
3AL 89082 BAAA - Ed. 01

1353NM
Rel. 7.3 7.3.6P9
Administration Guide - 3AL 89082 BAAA - Ed. 01

1353NM - Rel. 7.3 7.3.6P9
1353NM
Rel. 7.3 7.3.6P9

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
HANDBOOK EDITORIAL INFORMATION

1353NM Rel. 7.3 7.3.6P9
3AL 89082 BAAA Ed. 01 RELEASED Change Note: not applicable
Unit: FCG OND NM Vimercate 22 September 2006
Author: L.Pilotti
Appraisal: A. Cortese

1353nm73 Ag Ed01 1

Uploaded by

Copyright:

Available Formats

1353nm73 Ag Ed01 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1353nm73 Ag Ed01 1

Uploaded by

Copyright:

Available Formats

Alcatel 1350

3AL 89082 BAAA Edition 01

All rights reserved.

3AL 89082 BAAA Edition 01

LIST OF FIGURES ........................................................................................................................... 5

LIST OF TABLES ............................................................................................................................. 9

2 RELEASE IDENTIFICATION ....................................................................................................... 25

Administration Guide 1353NM Rel. 7.3

6 PERIODIC ACTIONS (SMF SCHEDULER) ................................................................................. 103

7 SYSTEM LOG MANAGEMENT ................................................................................................... 105

8 SYSTEM DATA MANAGEMENT ................................................................................................. 143

1353NM Rel. 7.3 Administration Guide

9 SMF FOR OMSG.......................................................................................................................... 197

10 ALCATEL NETWORK TIME PROTOCOL................................................................................. 199

ABBREVIATIONS ............................................................................................................................ 263

INDEX ............................................................................................................................................... 267

CUSTOMER DOCUMENTATION FEEDBACK.............................................................................. 269

Administration Guide 1353NM Rel. 7.3

Figure 1. Alcatel CDE Front Panel.................................................................................................... 22

Administration Guide 1353NM Rel. 7.3

1353NM Rel. 7.3 Administration Guide

Administration Guide 1353NM Rel. 7.3

1353NM Rel. 7.3 Administration Guide

Table 1. Handbooks related to the specific software application ...................................................... 13

Administration Guide 1353NM Rel. 7.3

Administration Guide 1353NM Rel. 7.3

PRODUCT Part Number

1353NM 3AL 89052 AAAA

PRODUCT RELEASE VERSION (N.B.) Part Number

1353NM 7.3 7.3 3AL 89053 ACAA

N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

This document is intended to 1353NM Administrators.

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

1353NM Rel. 7.3 Administration Guide

EDITION DATE DESCRIPTIONS

Table 1. Handbooks related to the specific software application

REF HANDBOOK Part Number Notes

[1] 1353NM Rel.7.3

[2] 1353NM Rel.7.3 THIS

[3] 1353NM NR5 Equipment Specific

[4] 1353NM NE LIST Handbook 3AL 89063 AAAA

[5] PMDS 1.1 User's Guide 3AL 88875 AAAA

[6] 1330AS 6.5

[7] ELB 2.X

[8] CT/SH-DXC Operation Manuals set 3AL 74553 ADAA

Administration Guide 1353NM Rel. 7.3

REF HANDBOOK Part Number Notes

[9] 1350 Rel.7.3

[10] 1350 7.1 System Management

Table 3. Handbooks for factory internal use only

REF HANDBOOK Part Number Notes

[11] RFC 1305

Table 4. Documentation on CD-ROM

REF Documentation CD-ROM TITLE Part Number

1353NM Rel.7.3 CD-ROM-DOC EN 3AL 89084 AAAA

Contains handbooks REF.[1] to [7] in electronic format.

HANDBOOKS RELATED TO THE PRODUCT'S HARDWARE