1353NM 74B 03 1

1353NM-E
Element Manager for Optical&Radio Networks
Rel. 7.4B
Version 7.4.4
Operator Handbook
3AL 89099 AAAA
Issue 3
June 2008
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent.
All other trademarks are the property of their respective owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no
responsibility for inaccuracies contained herein.
Copyright 2007 Alcatel-Lucent
3AL 89099 AAAA

Issue 3
Status: RELEASED
All rights reserved.

Passing on and copying of this document,
use and communication of its contents is not permitted
without written authorization from Alcatel-Lucent.
TABLE OF CONTENTS
LIST OF FIGURES .........................................................................................................................
LIST OF TABLES ...........................................................................................................................
19
PREFACE.........................................................................................................................................
Preliminary Information..............................................................................................................
Applicability.................................................................................................................................
Scope ...........................................................................................................................................
History..........................................................................................................................................
Related Documents ....................................................................................................................
Handbook Structure ...................................................................................................................
General on Customer Documentation ......................................................................................
21
21
22
22
23
23
25
27
1 WHAT IS NEW? ...........................................................................................................................

1.1 New GUI application for setting NE address.....................................................................
1.2 4G NE and 2G NE Abort Supervision.................................................................................
1.3 File Transfer Scheduler Editor facilities ............................................................................
31
31
31
31
2 SYSTEM OVERVIEW...................................................................................................................
2.1 System Access.....................................................................................................................
2.1.1 Logging into the System .................................................................................................
2.1.2 Password Expiration .......................................................................................................
2.1.3 Workspace Description ...................................................................................................
2.1.4 Locking the Screen .........................................................................................................
2.1.5 Logging Out ....................................................................................................................
2.2 Main Functionalities ............................................................................................................
2.2.1 Access ............................................................................................................................
2.2.2 The TMNOS..................................................................................................................
2.2.3 Quitting the 1353NM applications ...................................................................................
2.2.4 System stop ....................................................................................................................
2.3 View Description ..................................................................................................................
2.3.1 Equipment View Description ...........................................................................................
2.4 Map Navigation ....................................................................................................................
2.4.1 Root map navigation .......................................................................................................
2.5 Equipment View ...................................................................................................................
2.5.1 Open in Window command.............................................................................................
2.5.2 NE Equipment views.......................................................................................................
2.6 NE Alarms and NE Status....................................................................................................
2.6.1 NE Alarms.......................................................................................................................
2.6.2 NE Status ........................................................................................................................
2.7 On Line Documentation ......................................................................................................
2.7.1 Overview.........................................................................................................................
2.7.2 Help on help....................................................................................................................
2.7.3 Help on context ...............................................................................................................
2.7.4 Glossary..........................................................................................................................
2.7.5 About the help version ....................................................................................................
2.7.6 Tutorial ............................................................................................................................
2.7.7 Navigation Bar ................................................................................................................
33
33
33
34
35
35
36
38
38
39
43
43
44
45
52
52
57
57
57
61
61
63
67
67
68
68
70
71
72
73
3 ALARM MANAGEMENT..............................................................................................................
3.1 AS Overview .........................................................................................................................
3.1.1 Alarm Information ...........................................................................................................
3.1.2 AS Functionalities ...........................................................................................................
75
75
75
76
Operator Handbook
Table of Contents
1353NM-E Rel. 7.4B

3AL 89099 AAAA Issue 3
1/532
3.1.3 Current Alarm Management ...........................................................................................

3.1.4 Historical Alarm Management.........................................................................................
3.1.5 An Iterative Approach for Alarm Description...................................................................
3.2 Alarm Management..............................................................................................................
3.2.1 Access AS ......................................................................................................................
3.2.2 Reserving/Unreserving Alarms .......................................................................................
3.2.3 Acknowledging Alarms ...................................................................................................
3.2.4 Manually Purging an Alarm.............................................................................................
3.2.5 Manually Clearing an Alarm............................................................................................
3.2.6 Exporting and Printing (Output...) an Alarm ....................................................................
3.3 Navigation to/from Alarm Surveillance..............................................................................
3.4 Alarm Debouncing ...............................................................................................................
3.4.1 Alarm Debouncing Management ....................................................................................
76
77
77
79
79
80
82
84
84
84
85
88
89
4 PERFORMANCE MONITORING MANAGEMENT ......................................................................

4.1 Accessing Performance Monitoring ..................................................................................
4.2 Generating Reports .............................................................................................................
4.2.1 Filtering criteria ...............................................................................................................
4.2.2 Selecting Performance Entities.......................................................................................
4.2.3 Search Functions............................................................................................................
4.2.4 Setting Reporting Criteria ...............................................................................................
4.2.5 Setting Report Destination ..............................................................................................
4.2.6 Select Performance Parameters.....................................................................................
4.2.7 Setting Thresholds ..........................................................................................................
4.2.8 Setting Presentation Option ............................................................................................
4.2.9 Setting User Customized Label Options .........................................................................
4.2.10 Manipulating Reports ....................................................................................................
91
92
94
95
96
101
102
105
106
107
108
109
110
5 EVENT AND ALARM LOG BROWSER.......................................................................................

5.1 Application Startup ..............................................................................................................
5.2 ELB Graphical User Interface .............................................................................................
5.2.1 Menu Bar ........................................................................................................................
5.3 Tabbed Panes.......................................................................................................................
5.3.1 Alarm Log Display...........................................................................................................
5.3.2 Event Log Display ...........................................................................................................
5.4 Filter Management ...............................................................................................................
5.4.1 Filtering Criteria ..............................................................................................................
5.4.2 Filter Selection ................................................................................................................
5.4.3 Filter Dialog.....................................................................................................................
113
114
115
117
122
122
129
135
136
137
139
6 TOPOLOGY MANAGEMENT.......................................................................................................
6.1 NEs and Links ......................................................................................................................
6.1.1 Remote NE and Remote Unit .........................................................................................
6.1.2 Management States ........................................................................................................
6.2 Operations on NEs...............................................................................................................
6.2.1 Information about NEs ....................................................................................................
6.2.2 Modifying the Access State of an NE..............................................................................
6.2.3 Switching the NE Access State from Local to OS...........................................................
6.2.4 Management State Consultation.....................................................................................
6.2.5 Managing the NE MIB.....................................................................................................
6.2.6 Managing the NE Time ...................................................................................................
6.2.7 Managing the Administrative State of an NE ..................................................................
6.2.8 Managing the Supervision of an NE ...............................................................................
6.2.9 Resynchronizing Topology Management ........................................................................
6.2.10 Uploading the Remote Inventory ..................................................................................
145
145
145
145
148
149
150
151
157
158
164
168
170
173
173
1353NM-E Rel. 7.4B

2/532
Operator Handbook
Table of Contents
6.2.11 Ping NE .........................................................................................................................

6.3 Inventories and Navigations ...............................................................................................
6.3.1 Accessing the Global NE Inventory ................................................................................
6.3.2 NE Global Inventory Layout............................................................................................
6.3.3 Definition of an Inventory Selection Filter .......................................................................
6.3.4 Population .......................................................................................................................
6.3.5 Navigation towards Other Applications ...........................................................................
6.3.6 Creation/Deletion Monitoring ..........................................................................................
6.4 Window Management ..........................................................................................................
6.4.1 Creating a New Map .......................................................................................................
6.4.2 Setting the Map Parameters ...........................................................................................
6.4.3 Using the Local Persistency ...........................................................................................
6.4.4 Duplicating the Main Window .........................................................................................
6.4.5 Closing the Current Window ...........................................................................................
6.4.6 Opening the Console Window ........................................................................................
6.5 View Management................................................................................................................
6.5.1 Using the View Menu ......................................................................................................
6.5.2 Managing the View Filters...............................................................................................
6.5.3 Filter Editor Window........................................................................................................
6.6 Symbol Management ...........................................................................................................
6.6.1 Creating a Child View .....................................................................................................
6.6.2 Adding a Graphic Symbol ...............................................................................................
6.6.3 Adding a Graphic Link ....................................................................................................
6.6.4 Improving the Layout Display .........................................................................................
6.6.5 Activating/Deactivating the Frozen Mode .......................................................................
6.6.6 Selecting All the Symbols ...............................................................................................
6.6.7 Cutting a Symbol ............................................................................................................
6.6.8 Copying a Symbol...........................................................................................................
6.6.9 Pasting a Symbol............................................................................................................
6.6.10 Deleting a Symbol.........................................................................................................
6.6.11 Deleting All the Symbols from All the Views .................................................................
6.7 Navigation.............................................................................................................................
6.7.1 Navigating by Using the Go Menu ..................................................................................
6.8 Creation/Deletion of NEs or Links......................................................................................
6.8.1 Creation of NEs or Links .................................................................................................
6.9 Deletion of NEs ....................................................................................................................
6.9.1 Deleting an NE................................................................................................................
6.10 Modification of NE or Link Characteristics .....................................................................
6.10.1 Modifying the NE Characteristics..................................................................................
6.10.2 Cloning an NE...............................................................................................................
6.10.3 Declaration of the NE Addresses..................................................................................
6.10.4 Changing an OS Address .............................................................................................
6.11 External Text.......................................................................................................................
174
179
179
180
182
183
184
185
188
188
189
191
193
193
193
195
195
203
203
207
207
209
210
211
211
211
211
211
212
212
212
214
214
215
216
220
220
221
221
222
225
233
235
7 MANAGING A MAP .....................................................................................................................

7.1 Introduction ..........................................................................................................................
7.2 Create the map .....................................................................................................................
7.2.1 Map Background and Layout ..........................................................................................
7.2.2 Creating a child submap .................................................................................................
7.3 Constructing the Manageable Entities...............................................................................
7.3.1 Adding NEs to the Topological representation ................................................................
7.3.2 Population from Inventory ...............................................................................................
7.4 NE Address...........................................................................................................................
7.5 Supervision ..........................................................................................................................
237
237
238
240
243
245
245
249
255
256
Operator Handbook
Table of Contents
1353NM-E Rel. 7.4B

3/532
7.5.1 NE management states ..................................................................................................

7.6 Supervising NEs ..................................................................................................................
7.6.1 Starting supervision of NEs.............................................................................................
7.6.2 Stopping NE supervision.................................................................................................
7.6.3 Abort Supervision ...........................................................................................................
7.6.4 Black icon with question point.........................................................................................
7.7 OS Address for an Equipment............................................................................................
7.7.1 OS Address ....................................................................................................................
7.8 Add Connection ...................................................................................................................
7.9 Diagnose...............................................................................................................................
7.9.1 Remote Inventory on PNM .............................................................................................
7.9.2 Abnormal Condition (AC) Viewer ....................................................................................
7.10 Create ISA board................................................................................................................
7.11 Map Management ...............................................................................................................
7.11.1 Introduction ...................................................................................................................
7.11.2 Submaps and local maps..............................................................................................
7.11.3 DNM Management ........................................................................................................
7.12 View: Display Options .......................................................................................................
7.12.1 NE Time Management ..................................................................................................
256
261
261
263
265
266
267
267
269
272
272
282
289
290
290
290
291
296
296
8 PROCEDURES FOR NM CONFIGURATION ..............................................................................

8.1 Q3 based NE management..................................................................................................
8.1.1 Data storage and recovery procedures...........................................................................
8.1.2 The backup of Q3 NE into 1353NM ................................................................................
8.1.3 The onboard simulator of Q3 NE into 1353NM.............................................................
8.1.4 RM behavior with respect to the MIBless architecture..................................................
8.2 OMSN and ATM board management ..................................................................................
8.2.1 Introduction .....................................................................................................................
8.2.2 OMSNs and ISA board: PNM customization ..................................................................
8.2.3 Create ISA board ............................................................................................................
8.2.4 ISA Address....................................................................................................................
8.2.5 OMSN + ISA: Supervision ..............................................................................................
8.2.6 Rename ISA board .........................................................................................................
8.2.7 Error Recovery: commands for NM administrators.........................................................
8.3 Procedures to handle Transmission Alarms.....................................................................
8.3.1 Introduction .....................................................................................................................
8.3.2 Why Transmission alarms are not shown at subrack view? ...........................................
8.3.3 How to identify transmission alarms starting from NE subrack view...............................
8.3.4 Transmission alarms sublist in AS component. ............................................................
8.4 Alarm Severity Assignment Profile Customization for OMSN.........................................
8.4.1 Introduction .....................................................................................................................
8.4.2 Customizing a new ASAP on NMOS ............................................................................
8.4.3 Customizing a new ASAP on RMOS for PDH ports .....................................................
8.5 Object Assignment Domain ................................................................................................
8.6 File Transfer Scheduler .......................................................................................................
8.6.1 Introduction .....................................................................................................................
8.6.2 Job Planning ...................................................................................................................
8.6.3 FT Scheduler Job Descriptor ..........................................................................................
8.6.4 FTS Job Editor ................................................................................................................
8.6.5 Job editing facilities.........................................................................................................
8.6.6 Save and Open menu options ........................................................................................
8.6.7 FTS Job Status ...............................................................................................................
8.6.8 Window Management .....................................................................................................
8.6.9 View Report ....................................................................................................................
301
301
301
304
310
315
316
316
317
318
320
322
323
324
325
325
325
326
328
329
329
330
334
340
346
346
348
348
349
355
361
363
366
368
1353NM-E Rel. 7.4B

4/532
Operator Handbook
Table of Contents
8.6.10 Software Status............................................................................................................. 370

8.6.11 DCN network example .................................................................................................. 376
9 SYSTEM CONFIGURATION FOR SUPERVISION AREA ..........................................................
9.1 Supervision Area Configuration.........................................................................................
9.1.1 Definition of Real Supervision Area ................................................................................
9.1.2 Definition of virtual Supervision Area for IP over OSI Tunnels .......................................
9.1.3 How to see parameters already configured for Supervision Area...................................
9.1.4 How to safely close 'Configure Supervision Area' dialog box .........................................
9.1.5 How to DeConfigure an existing Supervision Area .......................................................
9.1.6 How to see Supervision Area associated to EMLIM and other components ................
9.2 OSI Stack (RETIX) Configuration........................................................................................
9.2.1 Association of two NECOM components to the same SA ..............................................
9.2.2 How to see parameters already configured for NECOM.................................................
9.3 OSI Tunnel Configuration....................................................................................................
9.4 Q3 EMLIM Configuration ...................................................................................................
9.5 SNMP EMLIM Configuration .............................................................................................
9.6 4G EMLIM Configuration ...................................................................................................
9.7 Example ................................................................................................................................
389
389
390
391
392
392
392
392
392
393
393
393
394
395
396
397
10 IP OVER OSI TUNNELLING ......................................................................................................

10.1 Generalities ........................................................................................................................
10.2 System Configuration for IP over OSI Tunnelling...........................................................
10.2.1 System Configuration ...................................................................................................
10.2.2 Start Configured Process ..............................................................................................
10.3 IP over OSI Tunnelling Setup............................................................................................
10.3.1 Preconditions ................................................................................................................
10.3.2 Operations on OMSN NE .............................................................................................
10.3.3 Operations on 1353NM System....................................................................................
10.3.4 Start Supervision on ISA Board ....................................................................................
10.4 IP over OSI Tunnelling GUI Functions .............................................................................
10.4.1 Remove NE from Tunnel ..............................................................................................
10.4.2 Tunnel Remove.............................................................................................................
399
399
402
402
405
407
407
407
416
422
422
422
423
11 OA512 MANAGEMENT..............................................................................................................
11.1 Generalities.........................................................................................................................
11.1.1 OmniAccess 512 .........................................................................................................
11.1.2 References....................................................................................................................
11.1.3 OA512 Integration in 1353NM.....................................................................................
11.1.4 Preconditions for the Integration of OA512 in 1353NM.............................................
11.2 1353NM activation..............................................................................................................
11.3 OA512 Integration ............................................................................................................
11.3.1 OA512 EML Domain ...................................................................................................
11.3.2 1353NM registration on OA512 System......................................................................
11.3.3 Configuring trap management.......................................................................................
11.3.4 OA152 Network Element Creation ..............................................................................
11.3.5 Security .........................................................................................................................
11.3.6 OA512 Network Element Supervision.........................................................................
11.3.7 Navigation from 1353NM Topology Management to OA512 USM..............................
11.3.8 Ping NE .........................................................................................................................
11.4 Alarm management............................................................................................................
11.4.1 Navigation from AS to OA512 USM ..............................................................................
11.4.2 Navigation from Topology Management to AS USM.....................................................
425
425
425
425
425
426
427
428
428
430
431
433
437
437
439
440
441
445
446
12 1353NMSE MANAGEMENT .................................................................................................... 449
Operator Handbook
Table of Contents
1353NM-E Rel. 7.4B

5/532
12.1 Product overview ...............................................................................................................

12.1.1 SAN Extender 169xSE .................................................................................................
12.1.2 References ...................................................................................................................
12.1.3 SAN Extender 169xSE Integration in 1353NM .............................................................
12.1.4 Preconditions for the Integration of 169xSE in 1353NM .............................................
12.2 Installation of 169xSE Client Application ........................................................................
12.2.1 Installation Requirements .............................................................................................
12.2.2 Installing the Server ......................................................................................................
12.2.3 Installing the Client. ......................................................................................................
12.3 Customizing the NMSE Server .........................................................................................
12.3.1 Registering NMSE in the NM Framework .....................................................................
12.3.2 Defining Users ..............................................................................................................
12.3.3 Registering Network Elements in the NM Framework ..................................................
12.3.4 Registering Network Elements in NMSE ......................................................................
12.3.5 Adding Switches to the Server's List.............................................................................
12.4 Managing the Database .....................................................................................................
12.5 1353NM activation..............................................................................................................
12.6 169xSE Integration.............................................................................................................
12.6.1 Steps sequence to manage 169xSE NEs .....................................................................
12.6.2 169xSE EML Domain Configuration .............................................................................
12.7 169xSE San extender Management..................................................................................
12.7.1 169xSE Network Element Creation ..............................................................................
12.7.2 Security.........................................................................................................................
12.7.3 169xSE Network Element Supervision .........................................................................
12.7.4 Navigation from 1353NM Topology Management to USM............................................
12.7.5 Navigation to SANman application ...............................................................................
12.7.6 Ping NE.........................................................................................................................
12.8 Alarm Management............................................................................................................
12.8.1 Navigation from AS to 169xSE USM ............................................................................
12.8.2 Navigation from Topology Management to AS USM ....................................................
449
449
452
452
452
453
453
454
455
455
455
455
456
456
458
460
461
462
462
463
465
465
469
469
472
474
476
477
480
482
13 1615BCE MANAGEMENT .........................................................................................................

13.1 Product overview ...............................................................................................................
13.1.1 SHDSL SYSTEM ..........................................................................................................
13.1.2 1615BCE ......................................................................................................................
13.1.3 References ...................................................................................................................
13.1.4 1615BCE Integration in 1353NM ..................................................................................
13.1.5 Preconditions for the Integration of 1615BCE in 1353NM ..........................................
13.2 1353NM activation..............................................................................................................
13.3 1615BCE Integration..........................................................................................................
13.3.1 1615BCE EML Domain Configuration ..........................................................................
13.4 1615BCE Management ......................................................................................................
13.4.1 1615BCE Network Element Creation ...........................................................................
13.4.2 Security.........................................................................................................................
13.4.3 1615BCE Network Element Supervision ......................................................................
13.4.4 Navigation from 1353NM Topology Management to USM............................................
13.4.5 Navigation to SANman application ...............................................................................
13.4.6 Ping NE.........................................................................................................................
13.5 Alarm Management............................................................................................................
13.5.1 Navigation from AS to 169xSE USM ............................................................................
13.5.2 Navigation from Topology Management to AS USM ....................................................
485
485
485
486
486
486
487
487
488
488
490
490
494
495
497
499
500
502
505
507
14 GENERIC FUNCTIONS.............................................................................................................. 509

14.1 Configuration for Navigation between NM and BM-PR .................................................. 509
14.2 Navigation from 1353NM to 1354BM-PR.......................................................................... 509
1353NM-E Rel. 7.4B
6/532
Operator Handbook
Table of Contents
14.3 NE Event Archiving Configuration ................................................................................... 512

14.4 NE AutoDiscovery............................................................................................................ 516
ABBREVIATIONS ............................................................................................................................ 517
INDEX ............................................................................................................................................... 527
CUSTOMER DOCUMENTATION FEEDBACK.............................................................................. 529
Operator Handbook
Table of Contents
1353NM-E Rel. 7.4B

7/532
1353NM-E Rel. 7.4B

8/532
Operator Handbook
Table of Contents
LIST OF FIGURES
Figure 1. Login panel view. ...............................................................................................................
Figure 2. First time Password expiration...........................................................................................
Figure 3. Password expiration after a fixed interval time ..................................................................
Figure 4. The 1353NM workspace Front Panel. ...............................................................................
Figure 5. Locking the screen using a manual lock...........................................................................
Figure 6. Screen lock Password: entry box. .....................................................................................
Figure 7. Logging out using the front panel. .....................................................................................
Figure 8. HPCDE Panel ..................................................................................................................
Figure 9. TMNOS manager.............................................................................................................
Figure 10. Accessing the 1353NM functionalities. ............................................................................
Figure 11. Alarm Management view..................................................................................................
Figure 12. 1353NM map. ..................................................................................................................
Figure 13. Q3 NE view example. ......................................................................................................
Figure 14. Control panel alarm icon shapes .....................................................................................
Figure 15. Per domain icon alarms ...................................................................................................
Figure 16. Example of NE view message area.................................................................................
Figure 17. Example of a Q3 NE Board view. ....................................................................................
Figure 18. Example of a detailed port view for Q3 NE. .....................................................................
Figure 19. File: Local Persistency: Restore map ..............................................................................
Figure 20. Question box....................................................................................................................
Figure 21. Local Restore map selection box.....................................................................................
Figure 22. 1353NM Map ...................................................................................................................
Figure 23. NE popup menu.............................................................................................................
Figure 24. NE Supervision popup menu .........................................................................................
Figure 25. Opening a view in a window ............................................................................................
Figure 26. Example of a Board view for a Q3 NE. ............................................................................
Figure 27. Selecting a specific port view of a Q3 NE Board View.....................................................
Figure 28. Example of a Q3 NE Port View. .......................................................................................
Figure 29. Alarm representation in the Equipment views. ................................................................
Figure 30. Obtaining help on help.....................................................................................................
Figure 31. Obtaining context sensitive help. .....................................................................................
Figure 32. Netscape Help Window ...................................................................................................
Figure 33. Obtaining the glossary. ....................................................................................................
Figure 34. Glossary help window......................................................................................................
Figure 35. Obtaining info about the help version ..............................................................................
Figure 36. About the help on version window ...................................................................................
Figure 37. Obtaining help home page...............................................................................................
Figure 38. Tutorial help window ........................................................................................................
Figure 39. Iterative Approach for Alarm Description .........................................................................
Figure 40. AS Activation ...................................................................................................................
Figure 41. AS Counter Summary Window ........................................................................................
Figure 42. Alarm Reservation ...........................................................................................................
Figure 43. Alarm reserved ................................................................................................................
Figure 44. Unreserve Alarms ............................................................................................................
Figure 45. Acknowledging Alarms ....................................................................................................
Figure 46. Ack. Status change ..........................................................................................................
Figure 47. AS Output window ...........................................................................................................
Figure 48. File Chooser dialog box ...................................................................................................
Figure 49. Navigation from Topology Management to AS ................................................................
Figure 50. Alarm Sublist for selected NE ..........................................................................................
Figure 51. Navigation to NE USM.....................................................................................................
Figure 52. NE USM...........................................................................................................................
Operator Handbook
List of Figures
33
34
34
35
36
36
36
38
39
41
42
44
45
47
47
48
49
50
52
52
53
54
55
56
57
58
59
60
62
68
68
69
70
70
71
71
72
72
78
79
80
81
81
82
83
83
84
85
86
87
87
88
1353NM-E Rel. 7.4B

9/532
Figure 53. Alarm Debouncing activation ...........................................................................................

Figure 54. Alarm Debouncing GUI....................................................................................................
Figure 55. Save Confirmation Box ....................................................................................................
Figure 56. Performance Monitoring selection ...................................................................................
Figure 57. Report Request Control Window .....................................................................................
Figure 58. Select filtering criteria ......................................................................................................
Figure 59. Select performance entities using the performance entity tree........................................
Figure 60. Performance Entity Selection Menu ................................................................................
Figure 61. PE Selection window .......................................................................................................
Figure 62. Save PE selection window...............................................................................................
Figure 63. Delete PE selection window ............................................................................................
Figure 64. PE selection detail window ..............................................................................................
Figure 65. Search Functions.............................................................................................................
Figure 66. Search Window: TP Name ..............................................................................................
Figure 67. Set reporting Criteria........................................................................................................
Figure 68. Report destination selection ............................................................................................
Figure 69. Select Performance Parameter for Report ......................................................................
Figure 70. Setting threshold..............................................................................................................
Figure 71. Setting presentation options ............................................................................................
Figure 72. User customized label selection window .........................................................................
Figure 73. View and manipulate PDT report .....................................................................................
Figure 74. One report per PMP in PDT report ..................................................................................
Figure 75. View and manipulate TCT report .....................................................................................
Figure 76. ELB Application ...............................................................................................................
Figure 77. Show equipment activation..............................................................................................
Figure 78. Navigation from EML USM to ELB ..................................................................................
Figure 79. Loading Dialog.................................................................................................................
Figure 80. NAV Message Information Dialog ....................................................................................
Figure 81. Alarm Log Display selected .............................................................................................
Figure 82. Event Log Display selected .............................................................................................
Figure 83. Menu Bar .........................................................................................................................
Figure 84. File Menu .........................................................................................................................
Figure 85. Export Dialog ...................................................................................................................
Figure 86. Export Successful Information Dialog..............................................................................
Figure 87. Directory Error Message..................................................................................................
Figure 88. Save Failed Error Message .............................................................................................
Figure 89. Write protected error message ........................................................................................
Figure 90. Export Failed Error Message ...........................................................................................
Figure 91. Print Dialog ......................................................................................................................
Figure 92. Print Failed Error Message ..............................................................................................
Figure 93. Print Preview Dialog ........................................................................................................
Figure 94. Print Preview Error Message ...........................................................................................
Figure 95. ELB Tabbed Panes ..........................................................................................................
Figure 96. Alarm Log request Start Up .............................................................................................
Figure 97. Progress Dialog ...............................................................................................................
Figure 98. Alarm Log Display............................................................................................................
Figure 99. Column Width ..................................................................................................................
Figure 100. Alarm Log Display Columns ..........................................................................................
Figure 101. Hide/Show Columns ......................................................................................................
Figure 102. Perceived Severity Sort .................................................................................................
Figure 103. Alarm Log Full Details View for Q3 NE ..........................................................................
Figure 104. Alarm Log Full Details View for SNMP NE ....................................................................
Figure 105. Event Log request Start Up............................................................................................
Figure 106. Event Log Display..........................................................................................................
1353NM-E Rel. 7.4B

10/532
89
90
90
92
93
95
96
97
97
98
99
100
101
101
102
105
106
107
108
109
110
111
112
113
114
115
115
115
116
117
117
118
118
119
119
119
119
120
120
120
121
121
122
122
123
124
125
126
126
127
128
128
129
130
Operator Handbook
List of Figures
Figure 107. Event Notification Id Sort ...............................................................................................

Figure 108. Event Log Full Details View for Q3 NE ..........................................................................
Figure 109. Event Log Full Details View for SNMP NE.....................................................................
Figure 110. Full Details View with a long value.................................................................................
Figure 111. Long Message Value......................................................................................................
Figure 112. Event Log Filters Dialog .................................................................................................
Figure 113. Alarm Log Filters Dialog...............................................................................................
Figure 114. Example of Logical Operators in Alarm Log Filters Dialog.............................................
Figure 115. Selected filters for Alarm Filters Dialog ..........................................................................
Figure 116. Selected filters for Event Filters Dialog ..........................................................................
Figure 117. Filter Dialog Buttons.......................................................................................................
Figure 118. Event Type for Alarms and for Events............................................................................
Figure 119. Event Type Filter ............................................................................................................
Figure 120. Event Type Filter Greyed ...............................................................................................
Figure 121. Event Time Filter............................................................................................................
Figure 122. Invalid Date Range Error Message................................................................................
Figure 123. Last n minute Filter Selection ........................................................................................
Figure 124. Perceived Severity Filter................................................................................................
Figure 125. Probable Cause Filter ....................................................................................................
Figure 126. Operations menu ...........................................................................................................
Figure 127. Information dialog box for an NE ...................................................................................
Figure 128. Local AccessSwitch to Local Dialog Box ...................................................................
Figure 129. Local AccessSwitch to OS Dialog Box ........................................................................
Figure 130. Local AccessSwitch to Requested Dialog Box. ...........................................................
Figure 131. Local AccessRequested Monitoring Dialog Box ..........................................................
Figure 132. OS AccessRequested to Local dialog box...................................................................
Figure 133. Local AccessRequested to OS dialog box...................................................................
Figure 134. Current Status Dialog Box for an NE .............................................................................
Figure 135. MIB AlignmentAlign MIB Up Dialog Box ......................................................................
Figure 136. MIB AlignmentAlign MIB Down (Manual) Dialog Box ..................................................
Figure 137. MIB AlignmentAlign MIB Down (Global) Dialog Box....................................................
Figure 138. MIB AlignmentCompare MIBs Dialog Box ...................................................................
Figure 139. MIB AlignmentDump MIB Dialog Box ..........................................................................
Figure 140. Time ManagementGet Time Dialog Box (before command execution) .......................
Figure 141. Time ManagementGet Time Dialog Box (after command execution) ..........................
Figure 142. Time ManagementSet Time Dialog Box (before command execution)........................
Figure 143. Time ManagementSet Time Dialog Box (after command execution)...........................
Figure 144. AdministrationLock Dialog Box ....................................................................................
Figure 145. Administration. Unlock Dialog box .................................................................................
Figure 146. Example of a Supervision Dialog box ............................................................................
Figure 147. SupervisionStop Dialog Box ........................................................................................
Figure 148. Message dialog Box for Topology Management Resynchronization .............................
Figure 149. Upload Remote Inventory Dialog Box............................................................................
Figure 150. Menu Operations: Ping NE ............................................................................................
Figure 151. Ping NE function window ...............................................................................................
Figure 152. Select NEs on a map .....................................................................................................
Figure 153. Ping result for selected NEs ..........................................................................................
Figure 154. Tools Menu ....................................................................................................................
Figure 155. Global NE Inventory.......................................................................................................
Figure 156. NE Global Inventory Layout submenu ...........................................................................
Figure 157. Layout Examples ...........................................................................................................
Figure 158. NE Global Inventory Filter..............................................................................................
Figure 159. Population Window ........................................................................................................
Figure 160. Monitor dialog box (Creation Monitoring Panel) ............................................................
Operator Handbook
List of Figures
131
132
133
133
134
135
136
137
138
138
139
140
140
140
141
141
142
142
143
148
149
150
151
153
154
155
156
157
159
160
161
162
163
164
165
166
167
168
169
171
172
173
174
175
176
177
178
179
180
181
181
182
184
186
1353NM-E Rel. 7.4B

11/532
Figure 161. File Menu .......................................................................................................................

Figure 162. Confirmation Dialog Box for Creating a New Map .........................................................
Figure 163. Map Parameters Dialog Box..........................................................................................
Figure 164. Save Local Map Dialog Box...........................................................................................
Figure 165. Restore Map Dialog Box................................................................................................
Figure 166. Delete Map Dialog Box ..................................................................................................
Figure 167. Console Window............................................................................................................
Figure 168. Screen Button Indicating a New Error ...........................................................................
Figure 169. View Menu .....................................................................................................................
Figure 170. Filter Editor window .......................................................................................................
Figure 171. Command Filter Editor...................................................................................................
Figure 172. Related Views Dialog Box .............................................................................................
Figure 173. Example of a RowColumn Layout ...............................................................................
Figure 174. Example of a Cartesian Layout......................................................................................
Figure 175. View Parameters Dialog Box .........................................................................................
Figure 176. Options Window.............................................................................................................
Figure 177. Filter Editor Window.......................................................................................................
Figure 178. File Menu of the Filter Editor Window............................................................................
Figure 179. Working Area of the Filter Editor Window ......................................................................
Figure 180. Edit Menu.......................................................................................................................
Figure 181. Child View Creation Dialog Box .....................................................................................
Figure 182. Graphic Symbol Creation Dialog Box ............................................................................
Figure 183. Graphic Connection Creation Dialog Box ......................................................................
Figure 184. Go Menu ........................................................................................................................
Figure 185. Declarations Menu.........................................................................................................
Figure 186. NE Creation Dialog Box.................................................................................................
Figure 187. Remote NE Creation Dialog Box ...................................................................................
Figure 188. Deletion Dialog Box .......................................................................................................
Figure 189. Modification Dialog Box for a basic NE..........................................................................
Figure 190. Example of a Clone Dialog Box .....................................................................................
Figure 191. OSI address setting user interface (AFI= 39) ................................................................
Figure 192. OSI address setting user interface (AFI=47) .................................................................
Figure 195. OSI address setting user interface (AFI= free) ..............................................................
Figure 196. IP address setting user interface ...................................................................................
Figure 197. OS Address Dialog Box .................................................................................................
Figure 198. Current Status Dialog Box for NE with External Text Enabled .......................................
Figure 199. Filter Dialog Box (Static Attributes Panel) External Text Enabled ..................................
Figure 200. File: New Map................................................................................................................
Figure 201. Question: Save current map ..........................................................................................
Figure 202. View: View Parameters pulldown and popup menu.....................................................
Figure 203. Background selection ....................................................................................................
Figure 204. Layout selection.............................................................................................................
Figure 205. Root map display with background................................................................................
Figure 206. Edit: Create Child View ..................................................................................................
Figure 207. Child View icon selection ...............................................................................................
Figure 208. Child View icon selection box: Close button ..................................................................
Figure 209. Declarations: Create: NE ...............................................................................................
Figure 210. NE Creation ...................................................................................................................
Figure 211. Tools: NE Inventory: Global ...........................................................................................
Figure 212. Inventory: Population .....................................................................................................
Figure 213. Submap topology selection............................................................................................
Figure 214. Global Inventory population dialog box..........................................................................
1353NM-E Rel. 7.4B

12/532
188
189
189
191
192
193
194
194
195
196
197
199
200
201
201
202
204
204
205
207
208
209
210
214
215
217
219
220
221
223
227
228
229
230
231
232
233
235
236
238
240
240
241
241
242
243
243
244
246
247
249
250
251
252
Operator Handbook
List of Figures
Figure 215. Root map and submap ..................................................................................................

Figure 216. Submap view .................................................................................................................
Figure 217. Declarations: Set Addresses: NE Address ....................................................................
Figure 218. An example of the evolution of the NE management states. .........................................
Figure 219. Operations: Show Statuses ...........................................................................................
Figure 220. Current status dialog box ...............................................................................................
Figure 221. NE: Operations: Supervision: Align Up ..........................................................................
Figure 222. Align Up Supervision .....................................................................................................
Figure 223. Align Up Supervision end ..............................................................................................
Figure 224. Abort supervision ...........................................................................................................
Figure 225. Black icon with question point........................................................................................
Figure 226. Displaying and changing the OS address for an NE. ....................................................
Figure 227. OS Address dialog box ..................................................................................................
Figure 228. Operations: Add Connection..........................................................................................
Figure 229. Add Connection dialog box............................................................................................
Figure 230. Icon selection.................................................................................................................
Figure 231. Add Connection creation: Apply button .........................................................................
Figure 232. The connection is drawn on the map.............................................................................
Figure 233. Diagnose menu options .................................................................................................
Figure 234. Upload Remote Inventory option ...................................................................................
Figure 235. Remote Inventory uploading example ...........................................................................
Figure 236. Show Remote Inventory menu ......................................................................................
Figure 237. Show Remote Inventory window example .....................................................................
Figure 238. Wizard dialog box ..........................................................................................................
Figure 239. Remote Inventory Search dialog box.............................................................................
Figure 240. AC Abnormal Condition Viewer menu ...........................................................................
Figure 241. AC Viewer Window ........................................................................................................
Figure 242. Manual Refresh Command............................................................................................
Figure 243. AC View Icons ...............................................................................................................
Figure 244. Navigation from AC Viewer (PNM) to NE USM .............................................................
Figure 245. Refresh time configuration option ..................................................................................
Figure 246. Set refresh time and confirmation windows ...................................................................
Figure 247. Set default time and confirmation windows ...................................................................
Figure 248. Create ISA board option ................................................................................................
Figure 249. File options. ...................................................................................................................
Figure 250. File: Save Map As..........................................................................................................
Figure 251. Save Map As dialog box ................................................................................................
Figure 252. DNM Message ...............................................................................................................
Figure 253. File: Map management ..................................................................................................
Figure 254. DNM Map Management dialog box ...............................................................................
Figure 255. SECUSM browser: DNMAccessControlDomain ..........................................................
Figure 256. dnmusm admin added to profile Administrator ..............................................................
Figure 257. New DNM Map Management dialog box .......................................................................
Figure 258. GET NE TIME................................................................................................................
Figure 259. Example of GET NE TIME/............................................................................................
Figure 260. Q3 NE NM connection types .........................................................................................
Figure 261. Misalignment (warning alarm) between NE NM MIB and NE configuration ..................
Figure 262. NE Statuses shown window...........................................................................................
Figure 263. Simulator menu Align Up" option..................................................................................
Figure 264. Information window during a MIB Align Up procedure...................................................
Figure 265. NM MIB representation ..................................................................................................
Figure 266. RM connected to NE simulator ......................................................................................
Figure 267. Onboard Simulator monitoring.....................................................................................
Figure 268. OMSN and ISA board ....................................................................................................
Operator Handbook
List of Figures
253
254
255
258
259
260
261
262
263
265
266
267
268
269
270
270
270
271
272
273
273
274
275
278
280
282
283
284
284
285
286
287
288
289
290
291
292
292
293
293
294
295
295
297
298
302
305
306
307
308
309
311
312
317
1353NM-E Rel. 7.4B

13/532
Figure 269. Operations: Create ISA..................................................................................................

Figure 270. Create ISA dialog box....................................................................................................
Figure 271. ISA: Set Address: NE Address ......................................................................................
Figure 272. Set Addresses: IP Address............................................................................................
Figure 273. Start Supervision on OMSN. ..........................................................................................
Figure 274. Operations: Rename ISA...............................................................................................
Figure 275. Alarm indication syntheses ............................................................................................
Figure 276. Alarm Menu ...................................................................................................................
Figure 277. Alarm surveillance window ............................................................................................
Figure 278. AS navigation back to NE EML USM.............................................................................
Figure 279. Relationship between AS and Port View of NE EML USM ............................................
Figure 280. Show Equipment pop up menu......................................................................................
Figure 281. Configuring Alarm Severity Assignment Profile. ............................................................
Figure 282. ASAPs Management dialogue box. ...............................................................................
Figure 283. ASAP Edition dialogue box example. ............................................................................
Figure 284. Example of Management dialogue box with two customized ASAPs............................
Figure 285. ASAP Identifier on ASAP Edition dialogue box .............................................................
Figure 286. Path routing display .......................................................................................................
Figure 287. PDH Disabled alarm ......................................................................................................
Figure 288. RM level ASAP identifier................................................................................................
Figure 289. NM level ASAP list.........................................................................................................
Figure 290. OAD: Object: Create......................................................................................................
Figure 291. new OAD object.............................................................................................................
Figure 292. Elementary OAD: Create ...............................................................................................
Figure 293. Edit Operator profile.......................................................................................................
Figure 294. Elementary OAD and ACD of the Viewer Profile ...........................................................
Figure 295. Create NE ......................................................................................................................
Figure 296. FT Scheduler option ......................................................................................................
Figure 297. Selecting the New Job option from menu ......................................................................
Figure 298. Job type selection ..........................................................................................................
Figure 299. New Job creation ...........................................................................................................
Figure 300. SWDL job: Adding a new Session" example ................................................................
Figure 301. SWDL job: Adding NE equipment..................................................................................
Figure 302. SWDL package assignment example ............................................................................
Figure 303. Backup job window example .........................................................................................
Figure 304. Backup job assignment example ...................................................................................
Figure 305. Ne selection from Network Map.....................................................................................
Figure 306. Ne selection from NE software Table.............................................................................
Figure 307. Select extension with Shift" key....................................................................................
Figure 308. Select extension with Ctrl" key .....................................................................................
Figure 309. Cutting a branch ............................................................................................................
Figure 310. Pasting a branch............................................................................................................
Figure 311. Entering the file name to save .......................................................................................
Figure 312. Opening an existing job .................................................................................................
Figure 313. Closing the job scheduler ..............................................................................................
Figure 314. Job running indication window.......................................................................................
Figure 315. Example of job Status ....................................................................................................
Figure 316. Example of backup job status ........................................................................................
Figure 317. Job status and View Report" command........................................................................
Figure 318. List of the job opened ....................................................................................................
Figure 319. View of multiple job windows .........................................................................................
Figure 320. SWDL report window example ......................................................................................
Figure 321. Backup report window example.....................................................................................
Figure 322. SW Status menu All NEs" option and its tool-tip...........................................................
1353NM-E Rel. 7.4B

14/532
318
319
320
320
322
323
326
326
327
327
328
330
331
331
332
334
336
337
338
339
339
340
341
342
343
344
345
346
349
349
350
351
351
352
353
354
355
356
357
358
359
360
361
361
362
362
363
364
365
366
367
369
369
370
Operator Handbook
List of Figures
Figure 323. NEs SWDL Status..........................................................................................................

Figure 324. Export command............................................................................................................
Figure 325. File export characteristic................................................................................................
Figure 326. SW Status selected by name with a NE list menu .........................................................
Figure 327. NE software status detail ...............................................................................................
Figure 328. Q3NE Software unit detail example .............................................................................
Figure 329. Software management action example .........................................................................
Figure 330. Confirmation box window...............................................................................................
Figure 331. SW Status Selected by NE Type with a NE list menu....................................................
Figure 332. NE by type SW status ....................................................................................................
Figure 333. DCN network example...................................................................................................
Figure 334. Balancing the DCN traffic load.......................................................................................
Figure 335. Optimizing the load traffic for session ............................................................................
Figure 336. Example of DCN traffic increasing the LAN load ...........................................................
Figure 337. Job editor example ........................................................................................................
Figure 338. MIB backup job example ...............................................................................................
Figure 339. Misalignment Flag in the backup job .............................................................................
Figure 340. Job in progress status example .....................................................................................
Figure 341. SWDL job report example..............................................................................................
Figure 342. NEs software status table example................................................................................
Figure 343. Action on NE software package memory banks ............................................................
Figure 344. Supervision Area Selection in System Configuration ....................................................
Figure 345. Configuration of Supervision Area Parameters .............................................................
Figure 346. Confirmation Dialog before Supervision Area is de-configured .....................................
Figure 347. Supervision Area selection in OSI Stack configuration ..................................................
Figure 348. OSI Tunnel Configuration ..............................................................................................
Figure 349. Supervision Area selection during Q3 EMLIM configuration .......................................
Figure 350. Supervision Area selection during SNMP EMLIM configuration ..................................
Figure 351. Supervision Area selection during 4G EMLIM configuration .......................................
Figure 352. Supervision Area selection for coordinator ....................................................................
Figure 353. IP over OSI new components ........................................................................................
Figure 354. Tunnelling Schema ........................................................................................................
Figure 355. Network Setup ...............................................................................................................
Figure 356. System Configuration ....................................................................................................
Figure 357. Osi tunnelling Process Parameter Definition .................................................................
Figure 358. Save inserted data .........................................................................................................
Figure 359. Update Config Selection ................................................................................................
Figure 360. Start IP over OSI Processes ..........................................................................................
Figure 361. netstat command with osi tunnelling process running ...................................................
Figure 362. netstat command with osi tunnelling process stopped...................................................
Figure 363. Show equipment activation............................................................................................
Figure 364. Network Element USM ..................................................................................................
Figure 365. PointtoPoint Address Configuration selection............................................................
Figure 366. IP Address for PtoP Configuration.................................................................................
Figure 367. IP over OSI Selection ....................................................................................................
Figure 368. IP over OSI Tunnelling Configuration ............................................................................
Figure 369. IP Static Routing Configuration Selection ......................................................................
Figure 370. IP Static Routing Configuration......................................................................................
Figure 371. Create ISA board selection............................................................................................
Figure 372. Create ISA window ........................................................................................................
Figure 373. IP over OSI Tunnelling selection....................................................................................
Figure 374. Tunnel Configuration Application ...................................................................................
Figure 375. Create Tunnel window ...................................................................................................
Figure 376. Tunnel configuration list window ....................................................................................
Operator Handbook
List of Figures
370
371
371
372
372
373
374
374
375
375
376
377
378
380
382
383
384
385
386
387
388
390
391
391
393
394
395
395
396
396
399
400
401
402
403
404
404
405
406
406
407
408
409
409
410
411
412
413
414
415
416
417
418
419
1353NM-E Rel. 7.4B

15/532
Figure 377. Add IP NE on selected Tunnel.......................................................................................

Figure 378. Add IP NE on Tunnel .....................................................................................................
Figure 379. Detail Window for a Tunnel............................................................................................
Figure 380. Start Supervision on ISA board......................................................................................
Figure 381. Remove NE from Tunnel ...............................................................................................
Figure 382. IP over OSI Tunnelling Main Window ............................................................................
Figure 383. Delete Operation Confirm Window ................................................................................
Figure 384. Alcatel CDE Front Panel................................................................................................
Figure 385. TMN OS application.......................................................................................................
Figure 386. System Configuration window .......................................................................................
Figure 387. EMLIMSGM Configuration.............................................................................................
Figure 388. OA512 Coonfiguration .................................................................................................
Figure 389. Topology Manager .........................................................................................................
Figure 390. 1353NM Create Network Element .................................................................................
Figure 391. OA152 NE Creation .....................................................................................................
Figure 392. NE Set Address .............................................................................................................
Figure 393. OA512 Set Address .......................................................................................................
Figure 394. NE Supervision ..............................................................................................................
Figure 395. Start Supervision............................................................................................................
Figure 396. NE Show Equipment......................................................................................................
Figure 397. OA512 User Interface ....................................................................................................
Figure 398. Ping NE result................................................................................................................
Figure 399. Main Alarm List ..............................................................................................................
Figure 400. AS Administration Selection ..........................................................................................
Figure 401. Probable Cause List Selection.......................................................................................
Figure 402. AS Administration ..........................................................................................................
Figure 403. Navigation to OA512 USM.............................................................................................
Figure 404. OA512 USM...................................................................................................................
Figure 405. Navigation to AS USM ...................................................................................................
Figure 406. OA512 Alarms Sublist....................................................................................................
Figure 407. NMSE in TMN Architecture..........................................................................................
Figure 408. Remote SAN interconnection ........................................................................................
Figure 409. Install Wizard Mode Selection Screen ...........................................................................
Figure 410. Server Main Window......................................................................................................
Figure 411. The Add Switch Window ................................................................................................
Figure 412. Advanced Options for Adding Switches.........................................................................
Figure 413. Options Window, Statistic Tab........................................................................................
Figure 415. TMN OS application.......................................................................................................
Figure 418. Configuration data confirmation .....................................................................................
Figure 421. 169xSE NE Creation......................................................................................................
Figure 423. 169xSE Set Address......................................................................................................
Figure 427. 169xSE USM .................................................................................................................
Figure 428. Open SANman application from TMNOS selecting icon .............................................
Figure 429. Open SANman application from TMNOS selecting menu Actions ..............................
Figure 430. User Interface ................................................................................................................
1353NM-E Rel. 7.4B

16/532
420
421
421
422
423
424
424
427
427
428
429
430
433
434
435
436
436
437
438
439
439
440
441
442
443
444
445
445
446
447
450
451
454
457
458
459
460
461
461
463
464
464
465
466
467
468
469
470
471
472
473
474
474
475
Operator Handbook
List of Figures

Figure 434. AS Administration Window ............................................................................................
Figure 435. Navigation to SANman application ................................................................................
Figure 436. 1353NMSE Alarms List................................................................................................
Figure 438. 169xSE Alarms Sublist ..................................................................................................
Figure 439. SHDSL System..............................................................................................................
Figure 441. TMNOS Application .....................................................................................................
Figure 444. Configuration data confirmation .....................................................................................
Figure 447. 169xSE NE Creation......................................................................................................
Figure 449. 1615BCE Set Address...................................................................................................
Figure 453. 169xSE USM .................................................................................................................
Figure 454. Open SANman application from TMNOS selecting icon .............................................
Figure 455. Open SANman application from TMNOS selecting menu Actions ..............................
Figure 456. User Interface ................................................................................................................
Figure 460. AS Administration Window ............................................................................................
Figure 461. Navigation to SANman application ................................................................................
Figure 462. 1353NMSE Alarms List................................................................................................
Figure 464. 169xSE Alarms Sublist ..................................................................................................
Figure 465. Network Element on 1353NM map................................................................................
Figure 466. Network Element on BM-PR map ..................................................................................
Figure 467. Navigation from 1353NM to 1354BM-PR ......................................................................
Figure 468. NE view on BM-PR ........................................................................................................
Figure 469. NE Event Archiving Configuration selection ..................................................................
Figure 470. Event Archiving Configuration .......................................................................................
Figure 471. Event Archiving active ...................................................................................................
Figure 472. Event Log Display selection...........................................................................................
Figure 473. Archived Event Log file ..................................................................................................
Figure 474. AS NE Auto-discovery sublist ........................................................................................
Operator Handbook
List of Figures
476
477
478
479
480
481
482
483
485
487
487
488
489
489
490
491
492
493
494
495
496
497
498
499
499
500
501
502
503
504
505
506
507
508
510
511
511
512
513
514
514
515
515
516
1353NM-E Rel. 7.4B

17/532
1353NM-E Rel. 7.4B

18/532
Operator Handbook
List of Figures
LIST OF TABLES
Table 1. Product and release ............................................................................................................
Table 2. History .................................................................................................................................
Table 3. Handbooks related to the specific software application ......................................................
Table 4. Handbooks related to the Network Release........................................................................
Table 5. Handbooks for factory internal use only ..............................................................................
Table 6. Documentation on CDROM...............................................................................................
Table 7. Handbook structure .............................................................................................................
Table 8. Critical NE status .................................................................................................................
Table 9. Major NE status ...................................................................................................................
Table 10. Minor NE status .................................................................................................................
Table 11. Warning NE status .............................................................................................................
Table 12. Restricted NE status..........................................................................................................
Table 13. Disabled NE status............................................................................................................
Table 14. Unknown NE status ...........................................................................................................
Table 15. Normal NE status ..............................................................................................................
Table 16. Alarm severity and colour..................................................................................................
Table 17. Alarm Status Propagation by Default ................................................................................
Table 18. Default Assignment of Service Dependency and Severity on OMSN ...............................
Table 19. Possible customization Assignment of Service Dependency and Severity on OMSN ......
Table 20. Link load of level 1 with LAN load max=4 .........................................................................
Table 28. Handbooks related to Omni Access 512 management .....................................................
Table 29. OA512 Trap management ...............................................................................................
Table 30. Trap Mask Calculation.......................................................................................................
Table 31. Handbooks related to 169xSE management.....................................................................
Table 32. Suggested configuration for the Client PC ........................................................................
Table 33. Handbooks related to 1615BCE management.................................................................
Operator Handbook
List of Tables
22
23
23
24
24
24
25
63
64
64
64
65
65
65
65
123
190
333
333
378
379
379
379
380
381
381
381
425
431
432
452
453
486
1353NM-E Rel. 7.4B

19/532
1353NM-E Rel. 7.4B

20/532
Operator Handbook
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 special, in connection with the furnishing, performance, or use of this material.
NOTICE
The product specification and/or performance levels contained in this document are for information
purposes only and are subject to change without notice. They do not represent any obligation on the
part of ALCATEL.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL and must not be copied, reproduced or disclosed to a third party without written consent.
TECHNICAL SUPPORT
Please contact your Local Alcatel Technical Assistance Center for questions referred to the information contained in this document.
To send your comments about this handbook please follow the indication on Customer Documentation Feedback.
Operator Handbook
Preface
1353NM-E Rel. 7.4B

21/532
Applicability
This handbook applies to following productreleases:
Table 1. Product and release
PRODUCT
Part Number
1353NM
3AL 89052 AAAA
PRODUCT
RELEASE
VERSION (N.B.)
Part Number
1353NM
7.4B
7.4.4
3AL 89090 AEAA
N.B.
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

Handbooks relevant to software applications are not modified unless the new software "version" distributed to Customers implies manmachine interface changes or in case of slight
modifications not affecting the understanding of the explained procedures.
Moreover, should the screen prints included in the handbook contain the productrelease'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 the 1353NM Subsystem functionalities to manage Network Elements on
a topology oriented tool.
This document is intended to 1353NM Operators.
1353NM-E Rel. 7.4B

22/532
Operator Handbook
Preface
History
Table 2. History
EDITION
DATE
DESCRIPTIONS
03
June 2008
02
August 2007
General review
01
March 2007
First edition
Added Navigation configuration for navigating from NM to BM-PR
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
releaseversion is stated in Applicability on page 22 consists of the following handbooks:
Table 3. Handbooks related to the specific software application
REF
HANDBOOK
[1]
1353NM Rel. 7.4B

Administration Guide
3AL 89099 BAAA
[2]
1353NM Rel. 7.4B

Operator's Handbook
3AL 89099 AAAA
[3]
1353NM NR5 Equipment Specific

Operator's Handbook
3AL 89062 AAAA
[4]
1353NM NE LIST Handbook
3AL 89063 AAAA
[5]
PMDS 2.0 User's Guide
3AL 88927 AAAA
[6]
1330AS 6.5
Operator's Handbook
3AL 88876 AAAA
[7]
ELB 2.X
Operator's Handbook
3AL 88877 AAAA
Operator Handbook
Preface
Part Number
Notes
THIS
HANDBOOK
1353NM-E Rel. 7.4B

23/532
Table 4. Handbooks related to the Network Release

REF
HANDBOOK
Part Number
Notes
[8]
1350NM Rel. 8.1 PL1

Installation Guide
8DG 80028 BAAA
[9]
1350NM 7.1 System Management

Operator's Handbook
3AL 88893 AAAA
Table 5. Handbooks for factory internal use only

REF
[10]
HANDBOOK
Part Number
Notes
RFC 1305
Table 6. Documentation on CDROM

REF
Documentation CDROM TITLE

1353NM Rel. 7.4B CDROM DOC EN
Part Number
3AL 89100 AAAA
Contains handbooks REF.[1] to [7] in electronic format

Typically 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
Heatradiating Mechanical Parts

ELECTROMAGNETIC COMPATIBILITY (EMC)
ELECTROSTATIC DISCHARGERS (ESD)
EQUIPMENT LABELS
DISMANTLING & RECYCLING
1353NM-E Rel. 7.4B

24/532
Operator Handbook
Preface
Handbook Structure
This handbook has been edited according to the Alcatel standardized drawingup 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.
Table 7. Handbook structure
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.
What is New?
This section describes the most important new functions of the

described release of the product.
System Overview
This section introduces the 1353NM working environment, to the

users of the system, in terms of getting access to the system, the
environment utilities, the existing 1353NM functionalities and navigation through the system.
Alarm Management
This section describes the main Alarm Surveillance utilities and the
application in the 1353NM environment.
Performance Monitoring
Management
This section describes the main functionalities of PMDS application,

which offers a graphical user interface to generate different types of
reports for SDH, Ethernet and ATM performance monitoring data.
Event and Alarm Log

Browser
This section describes the main functionalities of ELB (Event Log

Browsing) tool, which provides a way to browse Event Log and
Alarm Log for different types of NEs: Q3, SNMP and TL/1 NEs. ELB
displays the events in a clear form, retrieves records from NE using
some filter and has the possibility to export, print and print preview
Log Records.
Topology Management
The Topology Management Application provides the user with:

coherent views of a telecommunication network in an intuitive
graphical format, the integration of different network management
applications in a unique interface. The Telecommunication Network
managed by client applications is represented as follows: topology
objects like views, equipment objects associated to Managed Elements like NEs (switches, adddrop multiplexers, routers) and
topology and logical links between NEs. It is also devoted to the integration of EML (Element Management Layer) subsystems. That is,
it achieves the integrated management of various kinds of Network
Elements (NEs) which are already individually managed by their
own EML subsystem.
Operator Handbook
Preface
1353NM-E Rel. 7.4B

25/532
Managing a Map
This section describes the operations related to the management of

Maps, Submap and symbols within the 1353NM. The actions leading to the creation, edition, deletion, storage and listing of Maps
shall be indicated and the navigation through the necessary
sequences of the Maps needed to create the Telecommunication
Network will be described. Sufficient details on the addition, the
removal and the selection of Network Element symbols are given to
enable an easy characterization of the network.
Procedures for NM Configu- The aim of this document is to describe some procedures clarifying
all the necessary items to achieve specific functionalities and conration
figuration. For the correct understanding of this Procedures Manual
all the commands described in the NM Operators Handbook have
to be considered known.
System Configuration for
Supervision Area
This section describes how instantiate and configure Supervision

Areas and OSI Stack processes (Necom Subsystems).
IP over OSI Tunnelling
This section describes the steps required to manage IP over OSI

tunnelling.
OA512 Management
The aim of this document is to describe the management of OmniAccess 512 integrated in 1353NM Subsystem.
1353NMSE Management
The aim of this document is to describe the management of 169xSE

that interconnects SAN islands using available fiber optic infrastructure such as SONET, DWDM or dedicated fiber.
1615BCE Management
1615BCE is a SHDSL system. The management of this system in

1353NM environment is described.
Generic Functions
This chapter collects some generic functions available on 1353NM

Subsystem.
Abbreviations
The abbreviation list is supplied.
Index
Index references are supplied.
Customer Documentation
Feedback
It contains info regarding customer opinions collection about this

documentation.
1353NM-E Rel. 7.4B

26/532
Operator Handbook
Preface
General on Customer Documentation

Note: when Network Management Operators 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 performance and services for which it is meant.
A "product" evolves through successive "productreleases" which are the real products marketed for
their delivery at a certain "productrelease" availability date.
So, a "productrelease" 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 "productrelease" 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 "productrelease" has its own standard Customer Documentation, composed by one or more handbooks.
A new "version" of a "productrelease" 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 plantindependent.
Plantdependent documentation, if envisaged by the contract, is subjected to commercial criteria as far
as contents, formats and supply conditions are concerned (plantdependent 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 explanation of the manmachine 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 production 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... .
Operator Handbook
Preface
1353NM-E Rel. 7.4B

27/532
Handbook Updating
The handbooks associated to the "productrelease" are listed in Related Documents on page 23.
Each handbook is identified by:
The name of the "productrelease" (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 productrelease (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
editorial 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 23.
In affected chapters, revision bars on the left of the page indicate modifications in text and drawings.
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 editions.
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 manmachine interface changes or in case of slight modifications not
affecting the understanding of the explained procedures.
Moreover, should the screen prints included in the handbook contain the productrelease'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 (supplying erratacorrige 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.
1353NM-E Rel. 7.4B

28/532
Operator Handbook
Preface
Customer documentation on CDROM

In the following by 'CDROM' it is meant 'Customer Documentation on CDROM'
Contents, creation and production of a CDROM
In most cases, a CDROM contains in readonly electronic format copy of the documentation for a specific
productrelease(version) and for a certain language.
In some other cases, the same CDROM can contain the documentation of different productrelease(
version)s for a certain language.
As a general rule:
CDROMs 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.
CDROMs 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 CDROM 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 CDROMs 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 CDROM
is recorded.
Suitable checks are made in order to have a virusfree product.
After a complete functional check, the CDROM image is electronically transferred to the archive of the
Production Department, so that the CDROM can be produced and delivered to Customers.
Use of the CDROM
The CDROM can be used both in PC and Unix WS environments.
The CDROM starts automatically with autorun and hyperlinks from the opened Index" document permit
to visualize the PDF format handbooks.
Other hyperlinks permit to get, from the Technical handbooks, the specific setting documents.
In order to open the .pdf documents Adobe Acrobat Reader Version 5.0 (minimum) must have been
installed on the platform.
The CDROM doesn't contain the Adobe Acrobat Reader program. The Customer is in charge of getting
and installing it.
ReadMe info is present on the CDROM 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.
Operator Handbook
Preface
1353NM-E Rel. 7.4B

29/532
CDROM identification
Each CDROM is identified:
1)
By external identifiers, that are printed on the CDROM upper surface:
The name of the "productrelease(s)" (and "version" if applicable).
A writing indicating the language(s).
The CDROM Part Number.
The CDROM Edition (usually first Edition=01).
2)
By internal identifier: the list of the source handbooks and documents (Part Number and Edition) by whose collection and processing the CDROM itself has been created.
CDROM updating
The list of source handbook/document Part Number and Edition indicated at previous point 2), in association with the CDROM's own Part Number and Edition, is also loaded in the AlcatelInformationSystem 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 AlcatelInformationSystem is made to identify the list of CDROMs 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 CDROM.
Updating of CDROMs always follows, with a certain delay, the updating of the single handbooks composing the collection.
1353NM-E Rel. 7.4B

30/532
Operator Handbook
Preface
1 What is New?
This chapter summarizes the new inserted functions and the most important modifications for the current
release 7.4.4 of 1353NM Subsystems.
1.1 New GUI application for setting NE address

New Graphic User Interface (GUI) application, in respect to previous solution, has the following
advantages:
1)
2)
3)
4)
It is able to determine type and release for a NE by its user label.

According to NE's type and release, GUI automatically fills the transport, presentation and session selectors for OSI and RFC 1006 addresses; it gives NSAP Selector for certain NE types
and releases; it assigns default value of NSAP fields for OSI addresses; it also automatically
fills UDP port for SNMP addresses.
Before setting the new address, it checks that the address is not duplicated created in global
inventory associated to PNM by invoking a method on an external component (FTS IM), which
takes in the new address and returns true or false depending on whether or not the new address
already exist in the network. New address will be compared with Global Inventory by using
FTSIM service via TCPPDU connection.
It is developed with JDK 1.4.2. If there are similar southbound interfaces, this application can
be easily ported to different OS platforms.
The NE address management function is mostly used when the NE is manually created by 1353NM
users. In case NE Automatic Discovery procedure applies, NE address is automatically notified and
1353NM users can skip any manual address setup. (See chapter 6.10.3)
1.2 4G NE and 2G NE Abort Supervision

The behaviour of Abort Supervision is the same as Stop Supervision unless for PM Collection that
is not provided. (See chapter 7.6.3).
1.3 File Transfer Scheduler Editor facilities

FTS gives now the possibility to activate Job Editor window including automatically a set of NEs
selected from the Network Map or from the NE Software Status Table. (See chapter 8.6.5).
Operator Handbook
What is New?
1353NM-E Rel. 7.4B

31/532
1353NM-E Rel. 7.4B

32/532
Operator Handbook
What is New?
2 System Overview
2.1 System Access
2.1.1 Logging into the System
This is the first operation you will have to undertake to access the system. The view that will greet you,
called the Login panel is presented below.
Workstation
name
Login name
Entry box
Password
Entry box
Push buttons
Figure 1. Login panel view.

To correctly access the 1353NM:
Enter your login name.
Enter your password.
N.B.
Your login name is assigned to you by the 1353NM administrator.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

33/532
After a correct login, the login view is replaced by a transition view giving certain software copyright indications. This view is automatically replaced by the normal workspace view containing the Front Panel from
which you will be able to access the 1353NM functionalities.
2.1.2 Password Expiration

This new login management, applied to the current NM network release, forces a new user, who is trying
at first time to login to the 1353NM system, to change the password (see Figure 2.). The previous password is no more valid then clicking on Dismiss" button the Change Password" window opens and the
new password can be applied.
Figure 2. First time Password expiration

After a fixed interval time (expressed in days), depending on the operator profile, the operator password
expires and a new one is required. Thus during a new login session after entering user and password a
new password is required (see Figure 3.)
Figure 3. Password expiration after a fixed interval time

Clicking on Dismiss" button, the Change Password" window opens and the new password can be
applied.
If during the password expiration the master presentation connection is not alive, the new password is not
required. In this case, clicking on Dismiss" button, the login will be accepted. The password modification
procedure requirement will be postponed to a next login, until all workstation are alive.
1353NM-E Rel. 7.4B

34/532
Operator Handbook
System Overview
2.1.3 Workspace Description

Your workspace is described as the functionalities that appear on your workstation screen after login.
The workspace Front Panel is described below.
WS
activity
Clock
Date
Text
Editor
Padlock
Workspaces
Letter
Exit
Terminal
Printer
File
Manager
TMNOS
Manager
Figure 4. The 1353NM workspace Front Panel.

The components of this front panel are distributed across two rows.
Top row of the Front Panel (from left to right):
The Clock icon displays the current time on your workstation.

The Date display indicates the day and the date and enables you to access a calender.
The WS activity icon indicates the internal activity of the workstation.
The Help icon enables you to launch the help application.
The Padlock icon enables you to lock your workstation screen.
The Workspace icons enable you to access different workspaces. There are only two available
workspaces (workspaces One and Two) used in the 1353NM product.
The Printer icon enables you to access the printing facilities. You can drag a file to the printer
icon to print it or simply access printer information.
The Letter icon gives access to the electronic mail service.
The File Manager icon gives you access to the files in your home directory.
The Terminal icon launches a hpterm command shell on your workspace.
The TMNOS System icon gives you access to the functionalities offered by the 1353NM product for the management of the network.
Bottom row of the Front Panel (from left to right):
The ALCATEL logo icon gives access to information about the 1353NM product.
The Workspace naming icon enables you to rename your workspaces.
The Key icon launches the password modification application on your workspace enabling you
to change your password.
The EXIT icon launches the logout procedure.
2.1.4 Locking the Screen

This utility enables you to lock the screen to prevent other users from using your working environment.
Two ways of doing this are described below.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

35/532
2.1.4.1 Manual Lock
Lock
Figure 5. Locking the screen using a manual lock.

To lock the screen simply click on the small Padlock icon situated on the Front Panel described above.
The screen will lock immediately. The following figure will appear on the screen.
Password Entry box
Username
Figure 6. Screen lock Password: entry box.
To resume work type in your password in the Password: entry box.
2.1.4.2 Inactivity Timeout

During a work session, the screen will be automatically locked by the system, if you have not undertaken
any operations on it since a certain time. The parameters of the screen lock can not be configured (e.g.
the timeout period before the screen locks).
2.1.5 Logging Out

Logging out from the workstation will automatically quit all graphical applications that you opened and give
place to the Login panel.
Use the Front Panel.
Click on the EXIT icon on the front panel, using the "Select" mouse button, as shown in the figure below:
EXIT icon
Figure 7. Logging out using the front panel.
1353NM-E Rel. 7.4B

36/532
Operator Handbook
System Overview
A dialogue box opens from which you can confirm or cancel the "Logout" operation.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

37/532
2.2 Main Functionalities

The access to 1353NM functionalities is described in the following paragraph.
2.2.1 Access
The graphical interface is based on:
HP Common Desktop Environment (HPCDE).

OSF Motif applications.
The HPCDE Tool panel (See Figure 8.) has been customized to contain the TMNOS Manager (on the
righthand side).
WS
activity
Clock
Padlock
Date
Text
Editor
Workspaces
Letter
Exit
Printer
Terminal
TMNOS
Manager
File
Manager
Figure 8. HPCDE Panel
Clicking on the Manager icon you can open the TMNOS Management. (See Figure 9.)
1353NM-E Rel. 7.4B

38/532
Operator Handbook
System Overview
2.2.2 The TMNOS

The TMNOSs is the graphical interface of the common platform application dedicated to manage the different System Instances installed on the same hardware machine.
The TMNOSs graphical interface is composed of a common window for managing (Start System, Stop
System, System Configuration, etc.) all the configured System Instances.
The common window contains an application icon for each System Instances and the operator through
the colour of the application icons background can check the status of the related System Instance.
The operator can also execute actions on the selected System Instance through icon bar or through pull
down menu.
Figure 9. TMNOS manager

Clicking on the TMNOS icon a window containing all the OS icons open, i.e. all the systems resident on
the Server or on WS. The colour of each icon depends on the OS process state:
Green
all the processes are running.
Red
at least one process is not running.
Blue
all the processes are stopped.
Yellow
the process state is unknown. It may be due to a isolation condition.
The window contains a pulldown menu bar with following menus:
File
containing the option "Close" to close the window only.
Edit
containing the option Clear Message area only.
View
allows to show/hide OS area or Message area.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

39/532
OS
containing::
Start System. This submenu is present for all NM Subsystems. The Start option is available if the selected OS is in the Stop state.
Stop System. This submenu is present for all NM Subsystems. The Stop option is available if the selected OS is in the running state.
Start/Stop System. Both options are provided if the selected OS is in the Wrong state
(partially stopped).
System Config. This submenu is available for NM Subsystems installed. It allows to configure the system in terms of processes.
Process Monitoring. This submenu is available both for all NM Subsystems. It opens the
Process Monitor window.
System Information. It gives information on the product actually installed.
Actions.(Active only for resident Manager) containing a list of menus that vary depending on
the OS type (RM, NM, etc.) and on its actual status. The relevant OS icon must be selected.
The available submenus are:
1353NM Admin. This submenu permits to launch the System Management applications:
SEC Administration, NE Administration and Data Management.
Alarm Debouncing.
Alarms. This submenu permits to launch the AS application.
SMF. It contains following options.

Operator Administration.
Log Management.
Trace Management.
Failure Management.
Scheduler Management.
Backup Management.
Restore Management.
Cleanup Management.
PMDS DB Administration.
Topology Manager. It permits to launch the map application.
Performance Monitoring. It permits to launch the PMDS display window.
Command Log Viewer. It permits to launch the browser to display logs.
NE Event Archiving Configuration.
NE AutoDiscovery.
Open 1353NMSE Map.
Global Actions.(Active only for resident Manager) It permits to launch the entire system
actions. It contains the following submenus:
Operator. It contains the following options:
1353NM-E Rel. 7.4B

40/532
Operator Handbook
System Overview
Global Operators Administration.

Change Password.
Session management.
Max Operator Logged Administration.
Set Personal Printer.
Synchronize Systems.
Global Process Monitoring.
Alarm Federations.
MySQL user.
The window contains a tool bar (active only for resident Manager) which allows to launch the most frequently used applications. They are:
EXIT
ALARM
SURVEILLANCE
SYSTEM
VERSION
SYSTEM
CONFIG
PERFORMANCE
MONITORING
PROCESS
MONITORING
1353NM
ADMIN
TOPOLOGY
MANAGER
Figure 10. Accessing the 1353NM functionalities.

N.B.
Depending on your access rights, you may or may not have access to some of the management
functions described below. The management functions that you cannot access are represented
as greyed icons or greyed menu options.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

41/532
2.2.2.1 1353NM System Management

N.B.
This management function is reserved to the 1353NM System Administrator.
This submenu permits to launch the System Management applications: SEC Administration; NE Administration and Data Management.
2.2.2.2 Alarm management

This management functionality covers provision of information concerning alarm surveillance, and alarm
management such as displaying alarm lists and acknowledging alarms. The functionality is provided by
the Alarm Surveillance (AS) application.
To access this management functionality, click on the Alarm icon in the scrolling subpanel of Figure 10.
The main view of the alarm manager opens.
An example of the view that opens is shown below.
Figure 11. Alarm Management view.

For details on this management function refer to the Operation Manual Alarm Manager AS.
1353NM-E Rel. 7.4B

42/532
Operator Handbook
System Overview
2.2.2.3 NE Construction Management

Topology Management
This management functionality is accessed from the TMNOS selecting the function Topology Manager.
NE Equipment Management
This management functionality covers configuration and manipulation of the NE using the Operating System. The functionality is provided by the Element Management Layer User Service Manager (EMLUSM)
application.
To access this management functionality, select the NE in the Network Topology view by clicking on it with
the "Select" mouse button. The NE is highlighted. Open the Show Equipment option from the popup
menu (otherwise select View Equipment from Tools menu).
2.2.2.4 PMDS management functionality

The operator can open the PMDS (Performance Monitoring Display) clicking on Performance" icon. The
purpose of the PMDS application is to present the performance data monitored on the TPs (termination
Points). The error counters data collection can be represented with textual reports and graphical format.
2.2.3 Quitting the 1353NM applications

During normal operations, to quit the 1353NM applications you simply have to logout from your workspace
(see para. 2.1.5 ).
If you do not want to log out but simply close the applications, select the File Exit option from the
Network Topology view.
A confirmation dialogue box opens from which you can confirm or cancel the "Exit" operation using the
Yes or No push buttons.
To only quit an equipment view, select the Close option from the Views pull down menu.
2.2.4 System stop

This section deals with what occurs when the 1353NM is stopped on your workstation (WS). The stopping
of the 1353NM applications on your workstations may be decided by the System Administrator following
a system crash.
Before stopping the 1353NM, you will be informed by the 1353NM system Administrator that there is an
ongoing 1353NM shutdown. You will no longer be able to launch operations on the 1353NM but you will
be given the opportunity to cleanly exit all the 1353NM applications before the 1353NM system shuts
down.
When the 1353NM is shutdown you are not logged out. The logout procedure is described into the paragraph
Logging Out.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

43/532
2.3 View Description

Figure which follows shows an example of 1353NM map.
A detailed description about map view can be found into chapter 6.4.
MAP TREE
PULLDOWN MENU
TITLE
TOOL BAR
ZOOMED AREA
GLOBAL AREA
Figure 12. 1353NM map.
1353NM-E Rel. 7.4B

44/532
Operator Handbook
System Overview
2.3.1 Equipment View Description

There are three types of equipment views. The NE views, the board views and the port views.
2.3.1.1 Network Element View

The front side of an NE may be composed of several racks, containing several subracks. Each subrack
is composed of several slots containing boards.
The number of views related to an equipment depends on the NE type. Several types of equipment are
made only of one subrack, the rack view is not available when this equipment is displayed.
An example of NE view is given in the following figure:
Severity alarm panel

Message area
Icon representing the global

board alarm severity
Management
states control panel
Domain alarm panel
Figure 13. Q3 NE view example.
This picture shows an NE subrack in which the different boards are represented.
Boards may be duplicated in an NE for equipment protection reasons, to avoid loss of communications in case
of equipment failure.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

45/532
Some boards contain several ports used for transmission purposes and interconnections between the different boards.
The lock representation which appears over some boards (with the Put in service" command for Q3 NE),
indicates that these boards cannot be removed because they are involved in one of the following processes:
Cross connection.
Equipment protection.
Multiplex section protection.
Synchronization.
NML assigned port.
To be able to remove one of this board (the lock, with the Put out of service" command for Q3 NE), you
must first stop the running process in which it is involved. (Only the unlocked boards can be removed with
the Remove" command for Q3 NE).
The NE view contains an alarm panel, a management states control panel and a message area. They provide you with information needed to manage the network.
Icons in the top left hand corner give information on the number and the severity of the current alarms. Icons
representing the management states are defined in the right side view.
N.B.
a)
Details on NE states and alarms relationship is given in the chapter 2.6. For Transmission Alarm
identification refer to chapter 8.3.
The Severity Alarm Panel.
The 1353NM provides an alarm functionality that informs the operator on the severity of the different
alarms in the NE as well as on the number of current alarms. There are five different alarm severity
levels.
In the 1353NM these different levels are associated with colours:
Red:
Orange:
Yellow:
Cyan:
Blue:
Critical alarm (CRI).

Major alarm (MAJ).
Minor alarm (MIN).
Warning alarm (WNG).
Indeterminate (IND).
Each alarm severity is represented by an alarm icon situated in the top left hand corner of the view.
These alarm icons are constantly represented on the different Equipment views (NE view, Board
view or Port view) so that the operator is always aware of the alarms occurring in the system.
Furthermore the shape of the alarm icons in the alarm panel gives an indication of the occurrence
of alarms.
The figure below describes different examples:
An alarm icon with a circle inside it (and a number at the bottom of the icon) indicates that
alarms of the number and the type defined by the icon are occurring.
An alarm icon with a rectangle inside indicates that no alarms of the type defined by the icon
are occurring.
An alarm icon greyed out indicates that spontaneous incoming alarm notification have been
inhibited.
1353NM-E Rel. 7.4B

46/532
Operator Handbook
System Overview
Rectangular shaped icon indicating a stable state.

Circular shaped alarm icon indicating alarm occurrence.
Greyed icon indicating alarm notification inhibition.

Figure 14. Control panel alarm icon shapes
The Q3 NE view presents three or four other icons in the top right of the window. These icons summarize the alarms per domain: Synchronization (SYNC), External Point (EXTP for ADM only), Equipment (EQP) and Transmission (TRNS).
Figure 15. Per domain icon alarms

N.B.
b)
Since some synchronization alarms are counted as a communication alarm on a synchronization object, it is counted one time in transmission alarm and one time in synchronization alarm. The result is that the sum of the numbers in the domain icons can not
correspond to the sum of the numbers displayed in the severity icons: the severity alarm
total number is always <= to the domain alarm total number.
The Management States Control Panel.

The different management states concerning the NE (see Q3 Generic NE Management manual) are
also represented via icons located in the right side of the equipment views. These icons are:
N.B.
The SUP icon: The Supervision state indicates whether or not the NE is under OS supervision.
The ALI icon: The Alignment state indicates whether or not the NE and OS MIBs are aligned.
The icon with a key symbol: The Local Access state indicates whether the NE is managed by
a craft terminal or by the OS.
The Q3 / COM icon: The Operational state indicates whether or not the communication with the
OS is established.
The CTC icon: The Connected state indicates whether the NE is connected to local Craft terminal.
The NML / MGR icon: The Assignment state indicates whether the NE is assigned to Network
Management tasks.
The NTP icon: The Network Time Protocol indicates whether the NTP communication protocol
is Enable (green frame) or Disable (brown frame).
The SIM icon: The Simulator state indicates whether the Simulator is disabled (green) or
enabled (blue).
The AC icon: The Abnormal Condition state indicates whether some abnormal conditions have
been recognized. The user can visualize them with the menu:
Diagnosis Abnormal condition list command.
Position the cursor over one of the states icons, to display in the message area (see Figure
16.) the management state corresponding to the colour displayed by this icon.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

47/532
A colour is applied to each management states icons. They give an indication of the status of the
NE. These colours may be configured
N.B.
c)
As for the alarm icons, a rectangular management state icon represents the stable state
while a circular icon shape represents an unstable management state.
The Message area.

The information displayed in the message area depends on the mouse cursor location within the
view. It can give two main types of information:
Information on the contents of the view, i.e. board name, port name etc... . This information
depends on the type of view (NE view, Board view or Port view).
Information on the control panel. Displays the visual information provided by the icons in a written form.
In the following figure the mouse cursor is situated on the slot 6. The message area therefore indicates which board is present in slot 6.
ADM_001: 1641sm 2.7
sr1 / STM1_EL_Aggr#6
Message area
Figure 16. Example of NE view message area.
1353NM-E Rel. 7.4B

48/532
Operator Handbook
System Overview
2.3.1.2 Board view

Each board that appears in the NE view has a particular detailed view concerning it. To avoid representing
all the views, only the general layout is described in this section using a 2 Mbit tributary board view for a
Q3 NE.
The following figures represent these board views.
N.B.
The control panel and the message area are identical to those in the NE view and are not
described again in this section.
Port
icons
Board
Administrative State
Indications on the probable causes of the alarms

occurring in the board.
Figure 17. Example of a Q3 NE Board view.
The board view shows:
The icon representation of the ports. There are as many icons as there are different ports. In the
above figure one type of ports is represented: a PDH port for the Q3 NE board.
An alarm probable cause information area which enable you to determine the probable cause of
the alarms occurring in the board. This area uses the alarm severity colour definition described previously to indicate the severity of the alarms occurring.
Small alarm icon on a corner of the port icons that indicate the most critical alarm occurring in the
port. To get details on the alarms occurring in the ports, navigate to the port view.
N.B.
Some Q3NE transmission alarms detected in the port view are not propagated to the board
view.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

49/532
2.3.1.3 Port view

Navigation to the port views is explained in the Navigation Chapter.
The port view is the final view of the NE and shows in the most detail the composition of the ports, in terms
of the TPs that compose them.
To avoid representing all the different port views a STM1 optical port view (Q3 NE) is used to underline
the descriptions given hereafter.
The port view is represented in the following figure:
Port and board
identification
Functional blocks of the board concerning this particular port
Port functional state

information message area
Figure 18. Example of a detailed port view for Q3 NE.
1353NM-E Rel. 7.4B

50/532
Operator Handbook
System Overview
The port views show:
The signal processing functional blocks concerning the port.

These functional blocks are placed in the top part of the view. The acronyms situated on each functional block identifies the specific operations undertaken by the functional block.
The Termination Points (TPs) associated with each type of port.

The TPs are placed under the functional blocks. The acronyms of the TPs identify the type of TP.
This helps to identify the type of signal that transits by the port.
A port functional state information message area.

This message area gives information on the Administrative state, the Protection state, the Laser
shutdown state and the Operational state of the port.
The information in the functional state message area may change from port to port. For example,
electrical ports do not have the Laser shutdown information and PDH ports only have the NML
assignment information.
Small alarm icons placed next to the TP representations, and in the functional blocks, indicate
alarm occurrence. These alarm icons are identified by acronyms indicating the probable cause of
the alarm occurring.
These alarm icons use the alarm severity colour feature to indicate the severity of the alarm. The
operator can therefore determine the type and severity of the alarm occurring in a specific part of
the port.
N.B.
The control panel and the message area are identical to those in the NE view and are not
described again in this section.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

51/532
2.4 Map Navigation

2.4.1 Root map navigation
In order to navigate through the different views follow the steps described below:
a)
From the previously opened map view select pulldown menu item:
File Local Persistency Restore map.
Figure 19. File: Local Persistency: Restore map

b)
A question box asks for saving modification done on the actually opened map.
Figure 20. Question box

1353NM-E Rel. 7.4B
52/532
Operator Handbook
System Overview
c)
If you click on Yes button, your changes will be saved. Subsequently the Local Restore map selection
box opens.
Figure 21. Local Restore map selection box
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

53/532
d)
Select the desired map and click on Restore button. Finally the map opens. See the following figure:
Figure 22. 1353NM Map
1353NM-E Rel. 7.4B

54/532
Operator Handbook
System Overview
e)
Selecting a NE, you can open the popup menu. In particular it is possible to open the NE view via
the Show Equipment menu.
Figure 23. NE popup menu.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

55/532
In addition you may use the Supervision menu to control main NM to NE functions.
Figure 24. NE Supervision popup menu
1353NM-E Rel. 7.4B

56/532
Operator Handbook
System Overview
2.5 Equipment View

2.5.1 Open in Window command
Navigating among different views may be performed either inside the same window, or opening a new window. This is useful if you want to navigate to another view without clearing the current view.
This operation can be carried out from Equipment views.
After selecting the desired element (board, port) from the current equipment view, select the Open In Window
option from the Views pull down menu as shown in the following figure.
Figure 25. Opening a view in a window

The selected view is then displayed in a new window.
N.B.
Only three windows can be opened simultaneously. This option is not available in the Port view.
2.5.2 NE Equipment views

The NE symbols in the Network Topology views allow the user to open a detailed NE view. It is then possible to navigate among the different NE Equipment views and to access other management domains.
There are two types of NE Equipment views:
The views that reflect the equipment structure on different levels namely Room view, Equipment
view with rack and subrack level, Board view and Port view. These views follow an hierarchical
order. From the access point Room view, the user has to navigate through the various levels down
to the destination view. On the other hand it is possible to directly access the various levels via Equipment Overview. For W/OMSN and WDM equipments the USM representation starts from the
Equipment View at rack level.
The views providing specific information according to management domains i.e.: Equipment Overview, Synchronization view and Transmission view. These views are described in the Q3 NE
Management section for Q3 NE equipments. They can be directly accessed via Views menu.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

57/532
2.5.2.1 Navigating to the Board View

The Board view can be opened from the subrack level of the Equipment view. To get there, access the
Room view via Views menu and then navigate through rack level of the Equipment view by doubleclicking on the relevant rack and subrack. Or select the relevant board in the Equipment Overview (for OMSG
only) and directly navigate to the Board view.
There are two ways of opening a Board view from the subrack level of the Equipment view:
Via Views pull down menu.
By doubleclicking on the desired board.
If you use the menu option, click on the board you want to visualize. The contour is highlighted in the view
showing that the board is selected. Select the Open Object or Open In Window option of the Views pull
down menu.
The Board view is then opened.
Port
icons
Board
Administrative State
Indications on the probable causes of the alarms

occurring in the board.
Figure 26. Example of a Board view for a Q3 NE.
1353NM-E Rel. 7.4B

58/532
Operator Handbook
System Overview
2.5.2.2 Navigating to the Port View

The Port view can be opened from the Board view. To get there, access the Room view via Views menu
and then navigate through rack level and subrack level of the Equipment view by doubleclicking on the
relevant rack, subrack and board. Or select the relevant port in the Equipment Overview and directly navigate to the Port view. For W/OMSN and WDM equipments the USM representation starts from the Equipment View at rack level and the board view is opened through the previous to the Board view navigation.
From the Board view you can access a specific Port view by doubleclicking on the desired board.
Selected port
Board functional state

information message area
Figure 27. Selecting a specific port view of a Q3 NE Board View.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

59/532
Identification of the port and board

types
Functional blocks
of the board concerning
this particular port
Figure 28. Example of a Q3 NE Port View.
2.5.2.3 Navigating to Management menu commands

These views are described in the Q3 NE Management section for Q3 NE equipments.
1353NM-E Rel. 7.4B

60/532
Operator Handbook
System Overview
2.6 NE Alarms and NE Status

This section describes the types of alarms defined for 1353NM Subsystem, in terms of severity levels, and
the way they are propagated through the different Equipment views (NE, Board or Port views).
2.6.1 NE Alarms
2.6.1.1 Description
Five different alarm severity levels are provided by the 1353NM:
Critical
(CRI).
Major
(MAJ).
Minor
(MIN).
Warning
(WNG).
Indeterminate (IND).
These levels are represented with different colours. They enable you to know the severity of the current
alarms occurring in the Equipment.
2.6.1.2 Propagation
In all the equipment views, small icons synthetically summarizing the alarms occurring in these different
entities, are represented next to the Board or Port entities themselves. The Transmission" alarms, related
to the received information stream, are recognized on the TP points of the boards but are not signalled
on the synthesis small icon alarm of the Q3 NEs board. To find out the board with the occurred transmission alarm the user can open the AS applicative selecting the menu option in the USM menu commands:
Diagnosis Alarms Transmission Alarms .
Then, after reading the listed physical board indications, come back to the USM, select the board and open
the Port view to check the previous transmission alarms.
These icons have the following characteristics:
Colour: enables you to determine the severity of the alarm occurring (critical, major,...) in the board
or port. This functionality enables a rapid diagnosis and navigation to the views where the source
of the problem lies.
Aspect: inside the icon either a "-" is drawn, in which case no alarm is occurring in the entity, or a
"x" sign is drawn, in which case alarms are occurring in the entity.
Using these two characteristics that are depicted in Figure 29., you can determine the existence of alarms
in the entities you manage.
The figure below shows:
A section of a NE view with some boards defined and the alarm icon below the board representations.
A section of a Board view with a port defined and the alarm icon next to the port representation.
A section of a Port view with the alarm icons drawn next to the subunits composing the port.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

61/532
Icon summarizing the alarms

occurring in the board. The
colour of the icon indicates
the severity of the most critical alarm occurring in the
board.

occurring in the port. The
colour of the icon indicates
the severity of the most critical alarm occurring in the
port.
occurring in the board element named MST.
The colour of the icon indicates the severity of the
alarm.
The name of the icon identifies the alarm.
Figure 29. Alarm representation in the Equipment views.
1353NM-E Rel. 7.4B

62/532
Operator Handbook
System Overview
2.6.2 NE Status
2.6.2.1 Description
In the Network topology views, each NE composing the Telecommunication Network is associated with
a status that is related to its functional state. This section describes the relationship between the different
NE statuses, the NE management states and the alarm severities. Furthermore, the propagation of the
statuses through the hierarchy of views is described.
The status of the NE is displayed on the Network Topology views graphical interface using colours. The
colour of an NE indicates its status.
The different NE statuses are:
Critical.
Major.
Minor.
Warning.
Restricted.
Disabled.
Unknown.
Normal.
The NE status is a function of its alarm severity (listed in paragraph 2.6.1), its alignment state, its operational state and its supervision state. Details on NE states are given in the chapter 6.1.2.
The relationships between the NE statuses and these different states are represented in the tables that
follow:
N.B.
a)
The sign signifies that the value of this state doesnt impact on the final NE status.
Critical NE status.
A NE status is critical if the NE operational state is disabled, or, if it presents a critical alarm status and
no other dysfunctions.
Table 8. Critical NE status
NE
Status
CRITICAL
Operator Handbook
System Overview
Alarm
Status
NE Alignment
state
NE Operational
state
NE Supervision
State
Disabled
Supervised
Critical
In configuration
Enabled
Supervised
Critical
Aligned
Enabled
Supervised
1353NM-E Rel. 7.4B

63/532
b)
Major NE status.
A NE status is major if the OS and NE MIBs are misaligned, or, if the NE presents major alarms and no
other dysfunctions.
Table 9. Major NE status
NE
Status
Alarm
Status
MAJOR
c)
NE Alignment
state
NE Operational
state
NE Supervision
State
Misaligned
Enabled
Supervised
Major
In configuration
Enabled
Supervised
Major
Aligned
Enabled
Supervised
Minor NE status.
A NE status is minor if the NE presents minor alarms and no other dysfunctions.

Table 10. Minor NE status
NE
Status
Alarm
Status
MINOR
d)
NE Alignment
state
NE Operational
state
NE Supervision
State
Minor
In configuration
Enabled
Supervised
Minor
Aligned
Enabled
Supervised
Warning NE status.
A NE status is warning if alarms are either warning, indeterminate or cleared and the alignment state in
configuration, or, if the alarms are warning and no other dysfunctions present.
Table 11. Warning NE status
NE
Status
Alarm
Status
WARNING
NE Alignment
state
NE Supervision
State
Warning,
Indeterminate,
Cleared
In configuration
Enabled
Supervised
Minor
Aligned
Enabled
Supervised
1353NM-E Rel. 7.4B

64/532
NE Operational
state
Operator Handbook
System Overview
e)
Restricted NE status.
A NE status is restricted when it is currently undergoing operations (aligning MIB or activating/deactivating Supervision). This means that no other operations can be carried out on the NEs until the operations are completed.
Table 12. Restricted NE status
NE
Status
RESTRICTED
f)
Alarm
Status
NE Alignment
state
NE Operational
state
NE Supervision
State
Activating/
Deactivating
Aligning
Enabled
Supervised
Disabled NE status.
A NE status is disabled when the NE is just declared.

Table 13. Disabled NE status
NE
Status
DISABLED
g)
Alarm
Status
-
NE Alignment
state
-
NE Operational
state
-
NE Supervision
State
Declared
Unknown NE status.
A NE status is unknown if the alarms are indeterminate (meaning that the OS has not received an update
of the current alarms occurring) and no other dysfunctions are present in the NE.
Table 14. Unknown NE status
NE
Status
UNKNOWN
h)
Alarm
Status
Indeterminate
NE Alignment
state
Aligned
NE Operational
state
Enabled
NE Supervision
State
Supervised
Normal NE status.
This occurs when all the alarms are cleared and the NE is functioning correctly.
Table 15. Normal NE status
NE
Status
NORMAL
Operator Handbook
System Overview
Alarm
Status
Cleared
NE Alignment
state
Aligned
NE Operational
state
Enabled
NE Supervision
State
Supervised
1353NM-E Rel. 7.4B

65/532
To each of these NE statuses a colour is associated. The default colours set are listed below:
Critical:
Major:
Minor:
Warning:
Restricted:
Disabled:
Unknown:
Normal:
Red.
Orange.
Yellow.
Cyan.
Tan.
Dark brown.
Blue.
Green.
The alarm status propagation is described in the chapter 6.4.2 and the modification of the default alarm
severity is described in the chapter 8.4.
1353NM-E Rel. 7.4B

66/532
Operator Handbook
System Overview
2.7 On Line Documentation

2.7.1 Overview
The Help is an important aspect of the 1353NM product. Using this functionality you can get information
on actions you are carrying out or on any particular topic linked to the 1353NM.
The help is based on world wide web technologies. The topics are written in html. Netscape Gold is the
browser used to navigate through the html pages and it is also used to edit the user personal pages. Navigation through the help is also possible using a customized navigation bar permanently displayed in the
left of the help screen (see paragraph Navigation principles).
To know how to use Netscape, access the Netscape online help on the web, by typing the following URL
(Uniform Resource Locator) directly into the location Netsite: text field of Netscape (or using the URL dialog box produced by the File Open Location menu item):
http://home.netscape.com/eng/mozilla/3.0/handbook/index.html
Access to 1353NM help is possible in two different ways: Permanent access and access when using the
1353NM.
Help permanent access:

Any time you need information, you can start Netscape and access the 1353NM help by typing the
correct URL directly into the location Netsite: text field. It is not necessary to have an 1353NM product
running, you just need Netscape and the help location URL.
N.B.
To have the correct URL, ask your system administrator.
Help access when using the 1353NM:

The 1353NM enables to access the help from the help menu, using the help push buttons of the dialog boxes or by pressing the F1 key of the keyboard. This two last options gives you access to contextual help. The help menu gives access to the following parts of the help:
help on help.
help on context.
glossary.
about (on version).
tutorial.
The menu options detailed in the following chapters are in fact entry points to the main help system. Once
you have entered the help system, via one of these menu options, hyperlinks enable you to navigate to
other parts of the help system and to view other help topics.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

67/532
2.7.2 Help on help

Help on help opens the Netscape help system. It helps understand the basics of navigation and also presents facilities that will enable you to quickly find the information you need. Using this option opens the
current online documentation chapter. This help is available from any Help pull down menu option.
To access help on help, select the On Help... option from the Help pull down menu.
Figure 30. Obtaining help on help.
2.7.3 Help on context

To access the on line context sensitive help you can either:
Press on the F1 key placed on top of the keyboard to get help on the active window.
Select the On Context option from the Help pull down menu to get help on the relevant application
window.
Click on the Help push button from any window.
The advantage of the help on context using push buttons is that it directly brings up the help that applies
to the actual context you are in. For example, in a dialogue box concerning the creation of a network element symbol, clicking on the Help push button will open a help window giving information on this action.
Figure 31. Obtaining context sensitive help.

The following Netscape help window opens:
1353NM-E Rel. 7.4B

68/532
Operator Handbook
System Overview
Figure 32. Netscape Help Window

Select the desired menu item.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

69/532
2.7.4 Glossary
This help option enables you to display the 1353NM online glossary.
To access the 1353NM Glossary, select the Glossary option from the Help pull down menu
.
Figure 33. Obtaining the glossary.

A window like the following example is opened:
Figure 34. Glossary help window

1353NM-E Rel. 7.4B
70/532
Operator Handbook
System Overview
2.7.5 About the help version

About the help version displays the version and copyright for the 1353NM Product.
To access the Help on Version, select the About... option from the Help pull down menu.
Figure 35. Obtaining info about the help version

Figure 36. About the help on version window
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

71/532
2.7.6 Tutorial
Tutorial displays the 1353NM help home page. To access the handbook's contents and structure, select
the Tutorial option from the Help pull down menu.
Figure 37. Obtaining help home page

Figure 38. Tutorial help window

1353NM-E Rel. 7.4B
72/532
Operator Handbook
System Overview
2.7.7 Navigation Bar

The navigation bar which is displayed on the left side of the screen allows quick access to the following
help pages:
Home.
The home page offers links to other documentation that is part of the 1353NM Operation Manual
Software.
Contents.
The contents of the currently consulted manual are displayed.
Previous and Next .
Those buttons can be used to navigate within a document.
Glossary.
The glossary pages are displayed.
Help.
This description of the navigation bar is displayed.
What's New.
A versions history list is displayed.
User Pages.
The user pages offer the opportunity to take notes or make commentaries. These user pages are
created automatically during the user account creation and can only be accessed from this user.
Search.
If available, the search function performs a string search within all onlinehelp files supporting the
search function. The output is a list of files containing the search string.
Operator Handbook
System Overview
1353NM-E Rel. 7.4B

73/532
1353NM-E Rel. 7.4B

74/532
Operator Handbook
System Overview
3 Alarm Management
The functionality is provided by the Alarm Surveillance (AS) application. This management functionality
provides efficient mechanism to control, supervise and manage equipment anomalies that may occur in
a Telecommunication Network. It covers provision of information concerning alarm surveillance, and
alarm management such as displaying alarm lists and acknowledging alarms.
3.1 AS Overview
3.1.1 Alarm Information
Alarms consist in messages emitted by network resources that have detected problems or failures in the
network. Information contained in the alarm belongs to two classes:
Resource identification.
Type Identification.
Resource Identification: Identifies the resource which has raised the alarm. The information is:
The resource type.

The resource name which has to be unique (Full Distinguished Name) in order to avoid identification ambiguities.
Type Identification: Identifies the type of the problem the alarm refers to. The kind of problem regroups
three basic elements of information:
The problem type belonging to following list:
Quality of service.
Communications.
Processing error.
Equipment.
Environmental.
The probable cause of the problem, which belongs either to standard probable cause values
(ITUT Recommendation X.733), or locally defined values.
The severity level of the problem (Alarm Perceived Severity) when the alarm is raised. Malfunctions are ranked into five severity levels:
Critical when it is no longer possible to provide the service you have requested.
Major.
Minor.
Warning which means no impact is reported upon the quality of service offered to you.
Indeterminate, if the severity level cannot be defined by the resource which raises the alarm.
Note
A particular severity level (Cleared) is used when the alarm is cleared by the resource
which has raised it before.
Operator Handbook
Alarm Management
1353NM-E Rel. 7.4B

75/532
3.1.2 AS Functionalities
The AS application is dedicated to receive, store, display and manage in real time alarms (current alarms)
raised by different sources, facilitating the overall alarm surveillance of the network, and improving the
reaction time of the network users in case of anomalies in the network. It also provides the possibility to
archive and retrieve the alarms, the called historical alarms, allowing postanalysis of anomalies in the
network.
The alarms, current and historical, can be displayed in lists. By mouse clicking, you can get detailed information, or perform action on the alarm when the alarm is raised.
In the current alarm case, a synthesis of alarm information can be displayed in submap. This alarm information is displayed for each NE present within the submap.
3.1.3 Current Alarm Management

This section describes how to supervise the network activity to interfere with the network in order to take
anomalies into account and solve them.
Raised Alarm:
When an alarm is raised by a faulty resource, it is received by Alarm Surveillance which

stores it. The alarm can be displayed as soon as it is signalled.
Displayed Alarm: The alarm is displayed on the screen, the basic information is immediately available
to the user who can decide:
To get detailed information contained in the alarm.

To reserve the alarm for further exclusive investigation. This action of reservation on the alarm
prevents other users to perform any action on the alarm.
To request the creation of a trouble ticket to be handled by the external product ARS (Action
Remedy System).
To acknowledge the alarm, indicating that the cause of the alarm has been taken into account,
and that repair actions have been launched.
To let other user take it into account.
During the whole period an alarm is considered to be current (alive), its state is permanently realtime
refreshed so that any user who displays this alarms knows the actual state of the alarm.
Cleared Alarm:
The alarm is cleared by the emitting resource as soon as the problem is no longer
present at resource level.
As soon as the alarm is acknowledged by the user, it is no longer considered as a current alarm.
The alarm is removed from the current alarm set and is archived into the set of historical alarms.
The problem the alarm is linked to may not be solved immediately. In such a case the alarm
is repeated until the problem is solved. AS associates a repetition counter to each received
alarm. If the alarm is not cleared by the resource which raised it, then AS offers the possibility
to archive it manually on users request.
Note:
A single anomaly in the network may cause the raising of several alarms; it may also generate
other anomalies or dysfunctions that raise additional alarms. These alarms, called correlated alarms may
be marked as linked to each other.
1353NM-E Rel. 7.4B
Operator Handbook
76/532
Alarm Management
3.1.4 Historical Alarm Management

Once alarms are no longer considered as current alarms, they are archived in the historical Alarm section
of the AS application, where they can be consulted.
A consultation of historical alarms is generally performed in four steps:
Extracting the required alarm list from the repository or from personal files. The user is requested to
specify filtering criteria in order to extract only useful part of the alarms. These alarms are stored in a main
alarm list.
Creating sublists from the main alarm list.
Opening the alarm sublists. The user can get basic information on the alarms including the date of the
archiving and the reason.
Getting detailed information on a particular alarm.
The historical part of the Alarm Surveillance is particularly useful to follow the activity of a network, its
robustness, the recurrence of the problems, or to help the user to dimension the network and detect its
critical points.
3.1.5 An Iterative Approach for Alarm Description

Alarm Surveillance offers three main windows for viewing the alarms:
The Counter Summary window.
The Alarm Sublist window.
The More Alarm Information window.
The Counter Summary Window Main window used to display statistics on alarms. It shows
alarm counters, according to severity levels or statuses of
the alarms.
The Alarm Sublist Window
The sublist is a basic working window. It regroups alarms

according to filtering criteria defined by the user, and allows
to work on a limited subset of alarms.
The more Alarm Information This window displays the complete information contained in
Window
an alarm, which is particularly helpful for locating and diagnosing the problem the alarm is linked to.
Operator Handbook
Alarm Management
1353NM-E Rel. 7.4B

77/532
Figure 39. Iterative Approach for Alarm Description
1353NM-E Rel. 7.4B
Operator Handbook
78/532
Alarm Management
3.2 Alarm Management

3.2.1 Access AS
To access this management functionality, select
Actions Alarms
from the TMNOS menu or click on the Alarm icon in the TMNOS window.
Figure 40. AS Activation

The counter summary window of the alarm manager opens. The window provides the user with all the
available sublists informing the user about the status of the network in terms of alarm, as shown in following figure.
Operator Handbook
Alarm Management
1353NM-E Rel. 7.4B

79/532
Figure 41. AS Counter Summary Window
3.2.2 Reserving/Unreserving Alarms

To ensure to be the only responsible for an alarm (or a group of alarms), the user can perform the reservation action on alarms.
3.2.2.1 Reserving Alarms

To reserve one or several alarms:
Select the alarms.
Use the menu path: Action Reserve.
1353NM-E Rel. 7.4B
Operator Handbook
80/532
Alarm Management
Figure 42. Alarm Reservation

The Reservation Status changes from NRSV to RSV as shown in the figure.
Figure 43. Alarm reserved
Operator Handbook
Alarm Management
1353NM-E Rel. 7.4B

81/532
3.2.2.2 Unreserving Alarms

To unreserve one or several alarms:
Select the alarms.
Use the menu path: Action Unreserve.
Figure 44. Unreserve Alarms

The Reservation Status changes from RSV to NRSV.
3.2.3 Acknowledging Alarms

By acknowledging a single or a group of selected alarms in the Alarm Sublist window, the user notifies
he is taking them into account.
To acknowledge one or several alarm(s):
Select the alarm(s).
Use the menu path: Action Acknowledge.
A confirmation is required.
1353NM-E Rel. 7.4B
Operator Handbook
82/532
Alarm Management
Figure 45. Acknowledging Alarms

The status of the selected alarm(s) changes in the Ack. Status column from NACK (not acknowledged)
to ACK (acknowledged).
Figure 46. Ack. Status change

Acknowledging a cleared alarm is an implicit archiving action. Thus, in this case the acknowledgement
will archive the alarm and cause the disappearance from the list.
Operator Handbook
Alarm Management
1353NM-E Rel. 7.4B

83/532
3.2.4 Manually Purging an Alarm

To manually purge one or several alarm(s) of the Alarm Sublist window:
Select the alarm(s).
Use the menu path: Action Manual Purge...
The purged alarm(s) disappear from the sublist, or main list, and are archived, if matching the archiving
filter.
3.2.5 Manually Clearing an Alarm

When Alarm Clear Event is never received from an alarm agent, an AS operator is authorized to clear
manually this kind of alarm. AS can be informed about this kind of alarm either by the alarm agent or by
AS offline configuration. To manually clear one or several alarm(s) of the Alarm Sublist window:
Select the alarm(s) whose alarm status must be Clearable.
Use the menu path: Action Manual Clear...
A confirmation dialog box opens.
3.2.6 Exporting and Printing (Output...) an Alarm

The content of a sublist can be exported to a file or sent to a printer as well as the content of a single alarm.
In both cases the user will be requested to fill the Output dialog box with the desired parameters.
To export a part or the whole Alarm Sublist:
Select one or several alarm(s).
Use the menu path: Action Output...
The output window is:
Figure 47. AS Output window

The user can change the default options, exporting the alarms to an ASCII file or using a specific print
command. To activate either the Print or the Export field.
1353NM-E Rel. 7.4B
Operator Handbook
84/532
Alarm Management
To activate either the Print or Export field, click on the radio button beside the field. Then fill the field with
data corresponding to the selected type of export (printer or ASCII file).
The user is requested to fill the Print field with a user command:
keep the default command.
develop a print command that handles as a parameter the name of the temporary formatted file generated by AS. This file is not accessible and AS application should execute the
user command.
The Export field should be filled with a file name:
specify in the field the name of the file.
use the Select push button. The File Chooser dialog box opens and allows the user to
browse the existing file. The use can select a file from the list which will be overwritten or
specify a file name.
Figure 48. File Chooser dialog box

The exported information concerns only the attributes displayed in the sublist.
3.3 Navigation to/from Alarm Surveillance

It is possible from other applications to navigate towards AS application.
a)
From Topology Management, selecting a NE and the menu item Show Alarm, the AS USM is displayed listing the alarms for the selected NE.
Operator Handbook
Alarm Management
1353NM-E Rel. 7.4B

85/532
Figure 49. Navigation from Topology Management to AS
1353NM-E Rel. 7.4B
Operator Handbook
86/532
Alarm Management
Figure 50. Alarm Sublist for selected NE

It is possible from AS application to navigate towards the NE USM.
a)
From Alarm Surveillance select

Navigation External Application Related EmlUsm .
In the NE USM is displayed listing the alarms for the selected NE.
Figure 51. Navigation to NE USM

The NE USM is displayed.
Operator Handbook
Alarm Management
1353NM-E Rel. 7.4B

87/532
Figure 52. NE USM
3.4 Alarm Debouncing

SNMP and Q3 NE Management is improved with an alarm filtering in the timescale of several seconds
to minutes (ca. 30 seconds to 45 minutes).
Each filter is identified by a probableCause and its holdPeriod and configured by the Alarm Debouncing
GUI. The Alarm Debouncing GUI produces a filtering configuration file and EMLIM will be alerted, as
soon as the file is updated, to reread the file.
EMLIM (Q3 and SNMP), by using the filtering configuration file, will apply this filtering mechanism to
alarm notifications before sending alarms to Upper Managers:
When a clear notification is received and it falls in a filter criteria (e.g. probableCause of clear
notification has filter enabled), the clear notification is frozen and not forwarded, and a timer is
activated for the holdPeriod.
1353NM-E Rel. 7.4B
Operator Handbook
88/532
Alarm Management
If a raise notification, with the same MOC, MOI, ProbableCause, SpecificProblem, EventType
of clear notification, is received before the holdPeriod is exhausted, the frozen clear notification
is discarded, the timer is removed, and the raise notification is forwarded.
Instead, if no raise notification is received before the holdPeriod is exhausted, on timer expiration the frozen clear notification is forwarded.
The default configuration is no filter activated. The maximum number of filters that can be activate is 1000.
3.4.1 Alarm Debouncing Management

The Alarm Debouncing function is activated selecting from TMNOSs menu
Actions Alarm Debouncing
as shown in following figure
Figure 53. Alarm Debouncing activation

The Alarm Debouncing GUI opens.
Operator Handbook
Alarm Management
1353NM-E Rel. 7.4B

89/532
Figure 54. Alarm Debouncing GUI
Select in the form the probable cause to configure with the filter, the probable cause selected
appears in the box on the top of the form.
Here, selecting the option button on the right, the desired seconds can be inserted. Push the
Apply button to confirm the inserted data.
This operation can be done several times for all the probable cause that should be filtered.
To save the inserted data push the button Save.
If the file already exists, a confirmation box is displayed.
Figure 55. Save Confirmation Box

If you want to save the new inserted values answer yes to the question.
1353NM-E Rel. 7.4B
Operator Handbook
90/532
Alarm Management
4 Performance Monitoring Management

Performance management in the context of PMDS application means the storage of historic performance
data of managed Network Elements, reporting of the stored performance data, and long term trend analysis of the stored performance data.
The PMDS application offers a graphical user interface to generate different types of reports for SDH,
Ethernet and ATM performance monitoring data.
A system administrator can request the PMDS application to perform database management actions like
backup/restore, data purge, DB optimize, DB cleanup and DB size monitor.
PMDS can present the performance data collected by one or more network managers such as the
1353NM, 1354RM and 1354BM.
1353NME provides the following functionalities related to management of performance data collected
by each NE:
Start and Stop PM on a specific TP (Termination Point) through USM. Also CT and other NML
managers may start or stop PM. The following different measurement types may be started:
Digital PM with either 15 minutes or 24 hour granularity.
Ethernet PM with either 1 hour granularity.
Analog PM with either 15 minutes or 24 hour granularity.
Periodical collection of PM data from each NE. The collection is done:
Once a day for 24h PM data.
Once every two (but this value is configurable in EMLIM configuration files) hours for
15min and 1h PM data.
Forced collection of all PM data of a NE through EMLUSM.
Navigation to PMDS for display of PM historical data and graphical reports built on top of them.
PM data collection is triggered by:
Either EMLIM (periodical PM collection).
Or EMLUSM (forced collection).

EMLIM collects the PM data by NE in one of the following two ways:
Either through a file transfer session (in case of 4G NEs).
Or though a set of Q3 or SNMP requests (for all other NEs).

A specific process (Perfstorage) processes the PM config files written by EMLIM and, for each NE, saves:
A file to be used by PMDS for inserting PM collection data inside MySQL database.
A file to be used by IOO or other external products.
Operator Handbook
Performance Monitoring Management
1353NM-E Rel. 7.4B

91/532
4.1 Accessing Performance Monitoring

The Performance Monitoring application is included in 1353NM Subsystem and can be activated from
TMNOS menu
Figure 56. Performance Monitoring selection
or clicking on the icon
The Report Request Control Window opens.
1353NM-E Rel. 7.4B

92/532
Operator Handbook
Figure 57. Report Request Control Window
Operator Handbook
1353NM-E Rel. 7.4B

93/532
4.2 Generating Reports

When the operator wants to do performance analysis with PMDS a report should be generated.
To generate a report following steps are required in Report Request Control Window:
(Optional) Choose a filter combination to filter the Performance Entity tree.
Select Performance Entities in the Performance Entity tree.
(Optional) Use 'search' functions to select Performance Entities in the Performance Entity tree.
Set Reporting Criteria (report period, granularity, report destination, report type).
(Optional) Select Performance Parameters of the selected Performance Entities (all supported
performance parameters are selected by default).
This step should be done after "Performance Entities Selection" and "Report Type
Selection" because that the default selected parameters will be changed according to
the change of selected PEs and selected report type.
(Optional) Set threshold for Performance Entities.
(Optional) Set presentation options for the report that will be generated.
(Optional) Set the user customized label options for the TP label.
Trigger the Report Generation using the 'Apply' button.
The contents of the report that will be generated depending on the current set of Selected Performance Entities and Reporting Criteria.
Manipulate Reports (tabular or graphical report).
N.B.
These settings can already have been set when PMDS is invoked (for instance via Navigation
options).
1353NM-E Rel. 7.4B

94/532
Operator Handbook
4.2.1 Filtering criteria

A filter combination can be optionally chosen to filter the Performance Entity tree as shown in figure below:
Figure 58. Select filtering criteria

The operator can filter by choosing a single filter or a combination of filters.
Basic filters available now are:
No Filtering.
15min Monitoring.
1 hour Monitoring.
24h Monitoring.
Monitored (Any granularity).
In addition, there is one filter that can be coused to do the filtering:
Monitored As Active.
After filtering, the performance entity tree will show only those performance entities that match the filtering
criteria.
Operator Handbook
1353NM-E Rel. 7.4B

95/532
4.2.2 Selecting Performance Entities

Performance Monitoring: The operator wants to select Performance Entities to make a report for the
selected entities.
There are several ways to select one or more Performance Entities:
Using the Network Tree.
Using the Performance Entity Selections.
4.2.2.1 Selecting Performance Entities using the Performance Entity Tree

The operator wants to select Performance Entities to make a report on the selected entities.
Figure 59. Select performance entities using the performance entity tree
One or more Performance Entities may already be selected. The following actions are allowed to manipulate the set of selected Performance Entities:
Open a branch in the selection tree by clicking the [+] sign.
Close a branch in the selection tree by clicking the [-] sign.
Select a single Performance Entity by clicking on the Performance Entity label. All Performance
Entities that were already selected will be deselected.
Select multiple Performance Entities by using the <Ctrl> key (selecting and deselecting a single
Performance Entity) and the <Shift> key (selection of a range of Performance Entities).
1353NM-E Rel. 7.4B

96/532
Operator Handbook
4.2.2.2 Manipulating Performance Entity Selections

The operator wants to select, save or delete selections of performance entities.
The operator can manipulate performance entity selections through the menu:
File Performance Entity Selection
Figure 60. Performance Entity Selection Menu

Select Performance Entity Selection
The operator wants to select one PE from all existing PE selections and highlight all performance entities
contained in this selection on the performance entity tree.
Figure 61. PE Selection window
Operator Handbook
1353NM-E Rel. 7.4B

97/532
The operator can choose one nameitem of the PE selections in the combo box, the corresponding
description and all contained performance entities will be listed in their areas separately.
Meanwhile, the operator can click the [] button to see detail information of all PE selections' name and
description. The operator can select one name item directly in detail window as a short cut.
After selection, the operator can click [Select] button to make all listed performance entities directly
selected on the performance entity tree in RRC window, or click [Cancel] button to close this selection
window without doing any selection operation.
N.B.
The name and description areas in this window are NOT editable.
Save Performance Entity Selection
Figure 62. Save PE selection window

After selecting performance entities on performance entity tree in RRC window, the operator can save this
selection permanently in this window. The operator must give a name and optionally a description for this
selection.
description. Also, the operator can select one name item directly in detail window as a short cut.
After selection, the operator can click [Save] button to make a permanent storage for this PE selection,
or click [Cancel] button to close this selection window without doing any saving operation.
1353NM-E Rel. 7.4B

98/532
Operator Handbook
If the operator chooses to use an existing name and description, a message box will appear to have the
operator make sure that he/she wants to do the replacement.
Delete Performance Entity Selection
The operator wants to delete one or more of the existing PE selections.
Figure 63. Delete PE selection window

The operator can choose one nameitem of the PE selections in the combo box, the corresponding
description and all contained performance entities will be listed in their areas separately.
description. Also, the operator can select one name item directly in detail window as a short cut.
After selection, the operator can click [Delete] button to permanently delete this PE selection, or click
[Cancel] button to close this selection window without doing any deleting operation.
N.B.
The name and description areas in this window are NOT editable.
Operator Handbook
1353NM-E Rel. 7.4B

99/532
View details of PE Selections

The operator wants to view name and description details of the existing PE selections all at a time.
Figure 64. PE selection detail window

The operator can view name and description of all existing performance entity selections. This window
can accelerate operator's selection option without viewing descriptions one by one by changing items in
name combo box.
The operator can select one selection clicking on the corresponding line of the table.
After selection, the operator can click [Select] button to select this PE selection back to select, save or
delete window, or click [Cancel] button to close this selection window without doing any selecting operation.
1353NM-E Rel. 7.4B

100/532
Operator Handbook
4.2.3 Search Functions

The operator can use 'Search' functions to select Performance Entities in the Performance Entity tree as
shown in following picture
Figure 65. Search Functions

If the selection is Search TP Name following window is displayed:
Figure 66. Search Window: TP Name

Operator Handbook
1353NM-E Rel. 7.4B

101/532
This window consists of these areas:

Search Profile area consists of a profile list and a sub area:
Profile List contains all saved profiles for this search.
Operator can select a profile to be searched.
The Search Criteria area presents a search profile's conditions and enables operator to set search conditions.
The Profile Save area consists of two buttons used to save/update/delete search profile.
The Search Control area consists of three buttons used to start/pause/resume/restart search.
The Search Result area consists of result list and four buttons used to display found items, print
found items and navigate to Performance Entity Tree in RRC window.
The Search Status area contains a status bar at the bottom of the search window, which presents search progress information.
4.2.4 Setting Reporting Criteria

The operator wants to specify specific Reporting Criteria (report period, granularity, report destination,
report type) to direct the contents of a report.
Figure 67. Set reporting Criteria

Setting the reporting criteria includes:
The Reporting Period can be specified on four ways:
1353NM-E Rel. 7.4B

102/532
Operator Handbook
1)
User Selection period.

The operator must enter the 'From Date and Time' and the 'To Date and Time' manually.
The From Date starts at the earliest of 1 January 1970, the To Date ends at the latest of 31
December 2037. The preselected periods are grayedout.
2)
The last period.

The operator can choose from the following options:
15min:
hour:
day:
week:
month:
year:
last 15 minutes.
last hour.
yesterday.
last week.
last month.
last year.
The 'From Date and Time' and the 'To Date and Time' are updated automatically according to
the selected period and cannot be modified anymore.
3)
The current period

15min:
hour:
day:
week:
month:
year:
these 15 minutes.
this hour.
today.
this week starting with Monday.
this month.
this year.
The 'From Date and Time' and the 'To Date and Time' are updated automatically according to
the selected period and cannot be modified anymore.
4)
The Last Until period

15min:
hour:
day:
week:
month:
year:
15 minutes.
1 hour.
24 hours.
1 week.
1 month.
1 year.
The field 'To Date and Time' is entered by the operator. The field 'From Date...' is updated automatically and cannot be modified. A Reporting Period cannot be set for Reference Value
Reports. Operator can use the up and down arrow key to roll the selected time fields quickly.
Selecting granularity from a list of selectable Granularities. Granularity cannot be set for Reference
Value Reports.
Specifying the Report Destination:
Screen.
Mail.
File.
Printer.
Operator Handbook
1353NM-E Rel. 7.4B

103/532
Specifying the Report Type:
N.B.
PM Counter - Tabular.
PM Counter - Graphical.
Path State History.
Availability and Quality Trend.
Comparison - Tabular.
Comparison - Graphical.
Reference Value.
Delta Counter - Tabular.
Delta Counter - Graphical.
The Reporting Period is not updated for 'User Selection'.
For EML OS, the report type includes PDT, PDG, CMPT, CMPG, and REF.
For NML OS except RM, the report type includes PDT, PDG, PSH.
DCT and DCG are only for the ETH TPs of NM OS.
1353NM-E Rel. 7.4B

104/532
Operator Handbook
4.2.5 Setting Report Destination

The operator wants to specify the destination to which the report will be generated.
Figure 68. Report destination selection

There are four available destinations:
Screen: the report will be generated on screen.
Printer: the report will be generated and printed directly to printer.
File: the report will be generated into a file.
Mail: the report will be generated and sent as an attachment by mail.
Operator Handbook
1353NM-E Rel. 7.4B

105/532
4.2.6 Select Performance Parameters

The operator can select Performance Parameters of a selected Performance Entity (all supported performance parameters are selected by default) to be used in the report.
This step should be done after "Performance Entities Selection" and "Report Type Selection" because the
selected default parameters will be changed according to the change of selected PEs and selected report
type.
Figure 69. Select Performance Parameter for Report

One or more Performance Parameters may already be selected, and will be shown in the 'Selected' list
(if operator didn't change his Performance Entity selection), other unselected and supported Performance
Parameters will be shown in the 'Available' list. If no Performance Parameters previously selected, then
all supported Performance Parameters of those selected Performance Entities will be selected by default.
The following actions are allowed to manipulate the set of selected Performance Parameters:
Make a Performance Parameter from 'Available' to 'Selected' by single select one available
parameter and click the [>] button.
Make a Performance Parameter from 'Selected to 'Available' by single select one selected
parameter and click the [<] button.
Make all Performance Parameters from 'Available' to 'Selected' by the [>>] button.
Make all Performance Parameter from 'Selected to 'Available' by click the [<<] button.
Filtering 'Raw' or 'Derived' parameters by select/deselect [Raw Param] and [Derived Param]
check boxes.
Click [OK] to apply selections or [Cancel] to discard all selection changes.
1353NM-E Rel. 7.4B

106/532
Operator Handbook
4.2.7 Setting Thresholds

The operator wants to set threshold for a certain TP or all TPs.
Figure 70. Setting threshold

There are only one kind of threshold:
Bind to a parameter of a certain TP under a certain granularity.
Different threshold setting window will be shown according to different database: If submarine database's
tps selected, the threshold setting window will provide a button "Delete Threshold" to delete the corresponding threshold bond to a parameter of a certain TP under a certain granularity; if other database's
tps selected, no "Delete Threshold" button is displayed.
The operator can click one parameter and set its RESET and SET values. In addition, the operator can
set the direction of one threshold (with the default 'Threshold on Max' value).
In "Threshold Setting Window", if the operator click the [Apply to all TPs], then this threshold will apply
to all TPs listed in the combo box; otherwise, this threshold will apply only to the currently selected TP
in combo box by default.
After setting threshold, the operator can click [Save] button to save all settings or click [Cancel] button
to discard all settings.
Operator Handbook
1353NM-E Rel. 7.4B

107/532
4.2.8 Setting Presentation Option

The operator wants to set presentation options before or after report generation.
Figure 71. Setting presentation options

Setting the presentation options includes:
Setting graphical report scale, either linear or logarithmic.
Specify whether one report groups multiple PMPs or a single PMP. Also, specify how many
reports will be show if one report per PMP. The number must be 1, 2 or 3.
Specify whether show chart annotation, threshold or reference value in report. Only submarine
data supports reference value. If Show Threshold Value selected, threshold lines will appear
in PDG report when only one TP and one Parameter selected in Line Chart.
Choose date format in report. For RM and BM, there will be 3 items without second part; for
NM and SN, there will be 6 items, three of them have second part. In this case, in NM and SN,
the timestamp in report can have second part, for example: 2004/04/03 23:23:56.
Choose Report Content; RM, BM default select Full type, NM default uses the Compact type.
1353NM-E Rel. 7.4B

108/532
Operator Handbook
Choose timestamp style, it means the timestamp displayed in report is PM monitor start time
or end time, it's only available for 1353NM.
If the operator chooses to set presentation options before report generation (i.e. in RRC window), the setting will be remembered and be applied on the report that to be generated.
If the operator chooses to set presentation options after report generation (i.e. in Report window), the setting will be applied immediately on the report and the report will be changed accordingly.
N.B.
Currently only PDT and PDG report will accept one report per PMP setting. In RRC window,
the option "One Entity per Table/Chart" is unavailable, but in report window, the option is available.
4.2.9 Setting User Customized Label Options

The operator wants to customize the TP label that he/she preferred.
Figure 72. User customized label selection window

The operator can use the customized TP label by choosing Yes or No option in this window.
After selecting, the RRC window will be refreshed automatically.
N.B.
The function depends on the LET component. After the LET component is installed, the function
is visible, otherwise, it is invisible. It is not included into PMDS component.
Operator Handbook
1353NM-E Rel. 7.4B

109/532
4.2.10 Manipulating Reports

The operator wants to view a report, and manipulate it to format it the way he prefers.
Figure 73. View and manipulate PDT report

The operator performs one or more of the following actions:
Switching Reporting Style between Tabular and Graphical: Select the appropriate item in the
combo box. The desired representation of the report appears.
Switching the display of specific Termination Points on and off. When the selections of termination points are changed, the report is updated according the new selection. When a report
is generated, all termination points are selected by default.
Switching the display of specific Performance Parameters on and off. hen the selections of performance parameters are changed, the report is updated according the new selection. When
a report is generated, all performance parameters are selected by default.
Resizing of the columns in a tabular report. When the mouse is moved to the border of a cell,
the cursor takes a double arrow shape. If the mouse button is clicked and held, the size of the
column can be changed. The user preferred column width is kept persistent even PMDS application is closed and can be retrieved in next session.
Viewing report contents page by page. Click [ ] or [ ] button to view the previous or
next page of the content. Or input a page number in the text field and click [go] button to view
a specified page. If the page number is less than 1 or greater than the largest page number,
report will turn to page 1 or the largest page by default.
1353NM-E Rel. 7.4B

110/532
Operator Handbook
Viewing information of over threshold counters. Click menu:

Info Over Threshold Counter Setting to view over threshold counter settings for the TPs
currently in report. Please note that it's only available for 1353NM.
View Thresholds.
Set Thresholds. Click menu:

View Set Threshold or right click on one counter's column and click the pop menu item
"Set Threshold" to open Threshold Setting Window to set Threshold {see "Set Thresholds"}.
Sort/Statistic.
View Reference Value(Only for submarine data).
Set Reference Value(Only for submarine data).
Regenerate report.
Automatically update report.
Print report.
If the operator choose one report per PMP in presentation options setting (see "Setting presentation
options"), the PDT report will change its presentation style accordingly.
Figure 74. One report per PMP in PDT report
Operator Handbook
1353NM-E Rel. 7.4B

111/532
If the operator chose the menu option

Option Show Threshold Crossing Rows Only, then the PDT report will be turned to TCT report,
which considers only the rows with at least one counter value exceeding thresholds. Choose this menu
item again, and it will be toggled off to return to PDT report.
Figure 75. View and manipulate TCT report
1353NM-E Rel. 7.4B

112/532
Operator Handbook
5 Event and Alarm Log Browser

ELB (Event Log Browsing) tool provides a way to browse Event Log and Alarm Log for different types of
NEs: Q3, SNMP and TL/1 NEs. ELB displays the events in a clear form for the operator, retrieves records
from NE using some filter and has the possibility to export, print and print preview Log Records.
Figure 76. ELB Application
Operator Handbook
Event and Alarm Log Browser
1353NM-E Rel. 7.4B

113/532
5.1 Application Startup

The ELB application can start from the EML USM application. The EML USM is started from Topology
Management as shown in the figure below:
Figure 77. Show equipment activation

Select the NE in the Topology Management map, select Show Equipment from popup menu the corresponding NE USM opens.
1353NM-E Rel. 7.4B

114/532
Operator Handbook
Select:
Diagnosis Log Browsing Alarm Log
for Alarm and
Diagnosis Log Browsing Event Log
for Event in the Diagnosis menu of the EML USM application as show in figure below:
Figure 78. Navigation from EML USM to ELB

ELB starts with a temporary Loading Window, before showing ELB Main View.
Figure 79. Loading Dialog

ELB can process one request a time. If a new NAV message arrives when ELB is already processing a
request, a Message Dialog box appears.
Figure 80. NAV Message Information Dialog
5.2 ELB Graphical User Interface

The ELB GUI displays a window with the following main areas:
Operator Handbook
1353NM-E Rel. 7.4B

115/532
Title Bar.
Menu Bar.
Status Bar.
Tabbed Panes: Alarm Log Display and Event Log Display with tables containing one row per
log item.
The table supports sorting, column reordering and column exclusion.
Alarm log items are colored according to associated severity.
A log item detail panel; this panel displays additional information that could not fit into the basic
tablebased display.
A filter panel. Filtering is possible on the standard fields of the table; it is not possible on the
additional information fields.
The ELB window dimension is set according to the dimension of the screen where the application is running.
The operator can change the dimension of ELB window with the usual mouse actions.
Following pictures show the Log Browsing GUI for Alarm and Event Log display in ELB application.
Figure 81. Alarm Log Display selected
1353NM-E Rel. 7.4B

116/532
Operator Handbook
Figure 82. Event Log Display selected
5.2.1 Menu Bar

The Menu Bar contains five menus and has a platformdependent location along the top of the window.
Every Menu displays a popup menu when activated.
A popup menu is a menu that is invisible until the user makes a platformspecific mouse action, such as
pressing the right mouse button, over a popupenabled component. The popup menu then appears under
the cursor.
Figure 83. Menu Bar
5.2.1.1 File Menu

The File popup menu is composed by a submenu and three menu items.
Operator Handbook
1353NM-E Rel. 7.4B

117/532
Figure 84. File Menu

5.2.1.1.1 Export
ELB provides the possibility to export log items to a file with a specific format.
The export formats are:
CSV: Comma Separated Value (Excel format).
HTML with two different types: text file or table.
PDF.
PS.
XML.
TXT.
After choosing the file format, ELB shows an Export Dialog with a default export file name that depends
on the current Display, Alarm or Event, and on a default repository folder (export in the example), which
is set in a configuration file.
Figure 85. Export Dialog
1353NM-E Rel. 7.4B

118/532
Operator Handbook
If the export operation has succeeded, ELB displays the information about path and name of the exported
file in a dialog box.
Figure 86. Export Successful Information Dialog

If the export operation fails, ELB returns an error message. The message depends on the kind of problem
that occurred.
This error message is displayed if the inserted directory is a null or blank String.
Figure 87. Directory Error Message

This error message appears if ELB can't write a temporary XML file to tmp directory.
Note that this may occur whatever format was
selected, because an XML intermediate file is always
generated.
Figure 88. Save Failed Error Message

This error message is displayed if the inserted directory is not accessible or writeprotected.
Figure 89. Write protected error message
Operator Handbook
1353NM-E Rel. 7.4B

119/532
This error message is displayed if ELB has problem

with an internal library that converts XML file with XSL
style in desired format file.
Figure 90. Export Failed Error Message

5.2.1.1.2 Print
ELB provides the possibility to print log items in PDF format only.
Figure 91. Print Dialog

The Print Dialog allows to choose the Printer and set the Print range and Copies number.
If for any reason print operation fails, ELB displays an error message
Figure 92. Print Failed Error Message
1353NM-E Rel. 7.4B

120/532
Operator Handbook
5.2.1.1.3 Print Preview

ELB provides the possibility to preview log items in PDF format only.
Figure 93. Print Preview Dialog

Print Preview Dialog allows to scroll all log items in PDF format, page by page, to chose Print or Reload
operation and to set the preferred View format.
If print preview operation fails, ELB gives back to operator an error message.
Figure 94. Print Preview Error Message
Operator Handbook
1353NM-E Rel. 7.4B

121/532
5.3 Tabbed Panes

Two ELB components share the same space on screen: Alarm Log Display and Event Log Display. Only
one display is visible at a time. The user chooses which component view by selecting the tab corresponding to the desired Display.
Figure 95. ELB Tabbed Panes
5.3.1 Alarm Log Display

If an USM navigation requires a Log Browsing Alarm Log, the ELB window is activated and displayed, presenting the Filters Dialog for Alarm Log on top of the empty ELB Main View (which by default presents
the empty Event Log Display).
Initially the menu items are disabled: the operator must set the filters configuration to continue.
Figure 96. Alarm Log request Start Up
1353NM-E Rel. 7.4B

122/532
Operator Handbook
After setting the desired filters configuration, the event log application starts uploading Data Items from
the Network Element. A Progress Dialog appears above of the Main View of ELB that initially is empty.
The Progress Dialog shows with a numeric index in the Title Bar and with an animation in the figure, the
collection of Items by ELB.
Figure 97. Progress Dialog

When the Alarm Log collection is completed, all Items are shown in the ELB Main View that has switched
on Alarm Log Display automatically.
Every item assumes a colour according to his Perceived Severity, so the Alarm Log Table results to be
a multicolored table.
Table 16. Alarm severity and colour
Severity Number
Severity String
Severity Colour
CRITICAL
Red
MAJOR
Orange
MINOR
Yellow
WARNING
Cyan
CLEARED
Green
INDETERMINATE
White
An operator can also switch to Alarm Log Display from Event Log Display by clicking on tabbed pane.
Alarm Log Display reports data of last Alarm Log navigation on considered NE.
Alarm Log Display is empty if no navigation required a Log Browsing Alarm Log on this NE yet.
The operator can require a new Alarm Log navigation by selecting Filters Menu.
If an USM navigation requires a Log Browsing Alarm Log for a different NE, ELB clears current Alarm Log
Display (as well as Event Log Display) and prepares to show new Alarm Logs (Event Log Display remains
empty).
Operator Handbook
1353NM-E Rel. 7.4B

123/532
Figure 98. Alarm Log Display

Alarm Log Display has eight columns by default.
The number of rows depends by the number of Alarm Log Items read by ELB from NE: every row is an
Alarm Log Item of the NE.
Event Time and Date: date and time of the alarm occurrence. The format of Data and Time is:
yyyy/mm/dd hh:mm:ss.
Perceived Severity: indication of the severity of the alarm occurrence. The possible severities
are six and every severity is associated to a specific colour. The Perceived Severity of the alarm
occurrence determines the colour of the whole row of the Alarm Log Display.
Event Type: type of the alarm event occurrence defined in the OpticsIM Model.
Notification ID: a unique identifier for the alarm.
Managed Object Class: is the class of the object that emitted the alarm, as defined by the
OpticsIM Model.
Managed Object Instance: is the instance of the managed object class.
Probable Causes: is an attribute of the alarm event occurrence defined in the OpticsIM Model.
Specific Problem: is an attribute of the alarm event occurrence defined in the OpticsIM Model.
1353NM-E Rel. 7.4B

124/532
Operator Handbook
5.3.1.1 Column Width and Position

In general, table columns can have different widths in Alarm Log Display.
The operator can set the column width by dragging with the mouse the border of the column header cell.
So you can read the contents of a column that is partially hidden by default due to the standard dimension
of the Alarm Log Display Columns.
The operator can change the column positions using drag and drop functionality on a header column.
Figure 99. Column Width
Operator Handbook
1353NM-E Rel. 7.4B

125/532
5.3.1.2 Hide and show column

By default, when items are shown, columns that are completely empty (if any) are hidden in the right of
the table.
If even a single item has a nonnull value in Specific Problem column, then the whole column will be
shown.
Figure 100. Alarm Log Display Columns
Figure 101. Hide/Show Columns

To show hidden columns the operator can click on the left arrow until the left arrow becomes greyed.
To gain more space for the visualization, the operator can hide the right-most columns by clicking the right
arrow button.
1353NM-E Rel. 7.4B

126/532
Operator Handbook
5.3.1.3 Column Sort

By default Alarm Log table is ordered by Event Time and Date from the oldest Log to the most recent one.
The operator can sort the Alarm Log table in different ways.
If you click with the mouse on the header of a column the selected column is ordered in alphabetic or
numeric order, according to the type of data contained in the considered column. Consequently the whole
table is ordered.
An arrow appears in the header column to indicate whether the order is ascending or descending.
For example the Perceived Severity column is sorted in ascending or descending alphabetic order.
Figure 102. Perceived Severity Sort
Operator Handbook
1353NM-E Rel. 7.4B

127/532
5.3.1.4 Full Details

Selecting an item of the list displayed in Alarm Log panel, it is possible to view details about the item by
simply doubleclicking on it. This will open the Full Detail Window.
Figure 103. Alarm Log Full Details View for Q3 NE

For Q3 NEs, Full Details View shows the eight principal fields of Alarm Log panel and some other detailed
fields.
The set of detailed fields is not fixed; it depends on the actual contents of the corresponding item of the
Alarm Log. Possible detailed fields for Alarm Log are:
packages.
loggingTime.
nameBinding.
objectClass.
logRecordId.
monitoredAttribute.
For SNMP NEs, Full Details View shows only the eight principal fields of Alarm Log panel.
Figure 104. Alarm Log Full Details View for SNMP NE
1353NM-E Rel. 7.4B

128/532
Operator Handbook
5.3.2 Event Log Display

If an USM navigation requires a Log Browsing Event Log, the ELB window is activated and displayed, presenting the Filters Dialog for Event Log on top of the Main View of ELB that initially is empty.
Initially the menu items are disabled: the operator must set the filters configuration to continue.
Figure 105. Event Log request Start Up

After setting the desired filters configuration, ELB starts to upload Data Items from the Network Element.
The Progress Dialog appears above the empty Event Log Display.
When the Event Log collection is completed, all Items are shown in Event Log Display.
Operator Handbook
1353NM-E Rel. 7.4B

129/532
Figure 106. Event Log Display

The operator can also switch to Event Log Display from Alarm Log Display by clicking on tabbed pane.
Event Log Display reports data of last Event Log navigation on considered NE.
Event Log Display is empty if no navigation requires a Log Browsing Event Log on this NE yet.
The operator can require a new Event Log navigation by selecting Filters Menu.
If an USM navigation requires a Log Browsing Event Log for a different NE, ELB clears current Event Log
Display (as well as Alarm Log Display) and prepares to show new Event Logs (Alarm Log Display remains
empty).
5.3.2.1 Event Log Display Columns

Event Log Display has three columns by default.
The number of rows depends by the number of Event Log Items read from NE: every row is an Event Log
Item of the NE.
Event Time and Date: date and time of the event occurrence. The format of Data and Time is:
yyyy/mm/dd hh:mm:ss.
Notification ID: a unique identifier for the event.
Explanation: sentence built with the event log data to explain what the event represents.
1353NM-E Rel. 7.4B

130/532
Operator Handbook
5.3.2.2 Columns Width and Position

As Alarm Log Display, table columns can have different widths in order to gain more space for the visualization. You can set the column width by dragging with the mouse the border of the column header cell.
The operator can change column position using drag and drop functionality on a header column.
5.3.2.3 Hide/Show Columns

By default, Event Log Display shows all columns because there are none empty.
The operator can hide/show the last column by clicking to the right/left arrow every times.
5.3.2.4 Columns Sort

By default Event Log table is ordered by Event Time and Date from the oldest Log to the most recent one.
The operator can sort the Event Log table clicking with the mouse on the header of a column. That column,
and so all table, is ordered in alphabetic or numeric order, according to the type of data contained in the
considered column.
The Notification Id column is sorted in ascending or descending numeric order and the null or blank values
are put after the greatest values (when in ascending order).
Figure 107. Event Notification Id Sort
Operator Handbook
1353NM-E Rel. 7.4B

131/532
5.3.2.5 Full Details

Selecting an item of the list displayed in Event Log panel, it is possible to view details about the item by
simply doubleclicking on it. This will open the Full Detail Window.
For Q3 NEs, Full Details View brings again the three principal fields of Event Log panel and some other
detailed fields. Full Details View reports all data of considered event item returned by NE, including those
that are not normally shown in the main Log Display.
The set of detailed fields is not fixed; it depends on the actual contents of the corresponding item of the
Event Log. Possible detailed fields for Event Log are:
packages.
loggingTime.
logRecordId.
managedObjectClass.
nameBinding.
objectClass.
eventTypeId.
objectInstance.
attributeList.
protectionStatusParameter.
additionalInformation.
reportedProtectionUnit.
sourceIndicator.
Full Details View reports all data of considered alarm item returned by NE, including those that are not
normally shown in the main Log Display.
Figure 108. Event Log Full Details View for Q3 NE

For SNMP NEs, Full Details View brings the three principal fields of Event Log panel and:
objectInstance.
managedObjectClass.
eventTypeId.
1353NM-E Rel. 7.4B

132/532
Operator Handbook
Figure 109. Event Log Full Details View for SNMP NE

If a Full Details View contains a value longer the cell space, you can read all message value simply doubleclicking on the open Full Details View.
Figure 110. Full Details View with a long value

This operation opens a window, the Long Message Value Dialog that shows all message using scroll bars,
if necessary.
Operator Handbook
1353NM-E Rel. 7.4B

133/532
Figure 111. Long Message Value
1353NM-E Rel. 7.4B

134/532
Operator Handbook
5.4 Filter Management

The retrieval of Events and Alarms Log is managed using filters to make the analysis easier.
The filter selection operation is performed every time that a NAV Message arrives, at application start
up, or by explicitly activating the Filters Menu item.
For Q3 NE events and alarms log, the filter can be applied to log retrieve operation, for SNMP NE this
is not possible due to protocol restrictions. The filtering for SNMP log is performed by ELB application on
the totality of log data retrieved from NE.
For some fields, the user must choose a value from predefined lists, these are:
For alarms:
Probable causes.
Alarm type.
Alarm severity.
For events:
Event type.
Following figure shows the Filter Dialog for event. The dialog allows setting the filters to apply during the
retrieval of event items.
Figure 112. Event Log Filters Dialog

Following figure shows the Filter Dialog for alarms. The dialog allows selecting the filters to apply during
the retrieval of alarm items.
Operator Handbook
1353NM-E Rel. 7.4B

135/532
Figure 113. Alarm Log Filters Dialog

At application startup the Filter Dialog is clear, without any selection.
5.4.1 Filtering Criteria

The applicable filters are displayed in the Filters Dialog. The selected filters can be zero or more of the
possible filters.
The global condition defining the filter is built by applying an AND operator between the elementary conditions defined by groups. When, inside a group, a list offers multiple selections for an attribute, the condition on this attribute results from an OR on different selected values.
For example, Figure 55 shows the logical tree corresponding to the filter selection of Figure 56.
Suppose you are on October 17th 2003 16:27:28 and you want to filter for Alarm Logs with Equipment
or Quality of Service Alarms, that occurred after October 17th 2003 16:21:19 and before November 17th
2003 16:21:19, whose perceived severity is major, minor or cleared, and that have five types of probable
causes, Call Set Up Failure, or Clock Data Recovery Unlock, or Commercial Power Failure, or Common
Loss Alarm, or Communications Protocol Error.
The filter can be expressed as follows:
1353NM-E Rel. 7.4B

136/532
Operator Handbook
Figure 114. Example of Logical Operators in Alarm Log Filters Dialog

To activate or deactivate one of the groups (e.g. Event Type), you have to click the check button of the
zone. If you deactivate one of the groups, his panel becomes greyed.
The following paragraphs detail the operations for the different groups.
5.4.2 Filter Selection

The filter selection window displays all available filters. The last filter selection performed is proposed; this
selection can be confirmed or reset using a dedicated button on the window. The selected combination
of filters is displayed in the ELB application window to be remembered consulting the list.
Following figure shows the Filter Dialog with selected filters for Alarm.
Operator Handbook
1353NM-E Rel. 7.4B

137/532
Figure 115. Selected filters for Alarm Filters Dialog

Following figure shows the Filter Dialog with selected filters for Event.
Figure 116. Selected filters for Event Filters Dialog
1353NM-E Rel. 7.4B

138/532
Operator Handbook
5.4.3 Filter Dialog

The filter is defined through a panel composed of several groups: the Filter Dialog.
Filter Dialog is different for Alarm Log and Event Log.
The filters defined for Alarm Log are:
Event Type for alarm.

Event Time.
Perceived Severity.
Probable Causes.
The filters defined for Event Log are a subset of Alarm Log filters:
Event Type for event.

Event Time.
5.4.3.1 Filter Dialog Button

Filter Dialog has four buttons that have different purpose.
Figure 117. Filter Dialog Buttons

The 'Filter' button starts the log retrieval, activating the selected filters. The current filter configuration is
saved.
The 'No Filter' button starts the log retrieval, without activating the selected filters. The current filter configuration is saved.
The 'Clear All' button resets the currently selected filters, leaving the Filters Dialog open. Log retrieval
is not started.
The 'Cancel' button closes the Filters Dialog. This button doesn't perform any log retrieval action and the
current filter configuration is not saved. To save the filter setup, the operator should first use the button
'Filter'.
5.4.3.2 Event Type

To activate Event Type group, you have to click the check button near the filter name. By default the check
button is set. Then, select the desired fields with the mouse left button.
Event Type List reports all types of event or alarm that a NE can return: five basic categories of alarms
and four basic categories of events are specified. It is a multiselect list, that is, more than one value of
the list can be chosen. Use Ctrl + mouse or Shift + mouse to select multiple items.
Operator Handbook
1353NM-E Rel. 7.4B

139/532
Figure 118. Event Type for Alarms and for Events

If the check button is selected but no value of the list is selected, the effect is like all values of the list panel
were selected.
Figure 119. Event Type Filter

The two selections shown in the figure above yield the same result.
To deactivate Event Type group, you have to uncheck the button near the filter name. Event Type List
becomes greyed with his selection if there is one.
Figure 120. Event Type Filter Greyed
1353NM-E Rel. 7.4B

140/532
Operator Handbook
5.4.3.3 Event Time

ELB application gives the possibility to select retrieve Logs according to the data and time of their raising
event. To do this you must use Event Time Filter.
Figure 121. Event Time Filter

Filtering on date and time can have several variants; date and time filters are the following:
From to: date interval to display the events or alarms, the date to select are the time interval
starting date and the ending date.
To : events or alarms happened before a certain date, the date to select is the ending interval
date.
From : events or alarms happened after a certain date, the date to select is the starting interval date.
Last n minutes: events or alarms happened in the last n minutes interval.
The date and time value inserted should be checked for consistency:
From to : the 'from' date should precede the 'to' date.

To : the date inserted should precede or be equal the current date.
From : the date inserted should precede the current date.
If the date and time interval settings are invalid or inconsistent, an error message appears.
Figure 122. Invalid Date Range Error Message

The filter 'Last n minute' lets the user quickly select the last events/alarms list to see the last events or
alarms. The value n is inserted directly in the filter setting window.
If the Last check button is selected, From and To fields are greyed.
Operator Handbook
1353NM-E Rel. 7.4B

141/532
Figure 123. Last n minute Filter Selection

If the Event Time check button is selected but no other value of the group is selected, the filter operation
returns all items. This is equivalent to a nofilter operation.
5.4.3.4 Perceived Severity

To activate Perceived Severity group, you have to click the check button near the filter name. By default
the check button is set.
Perceived Severity group is composed by six check buttons, one for each alarm severity. It is a multi
select group, that is, more than one button of the group can be chosen.
If the check button is selected but no other value of the group is selected no filter is applied.
Figure 124. Perceived Severity Filter

To deactivate Perceived Severity group, you have to uncheck the button near the filter name. Perceived
Severity group becomes greyed with group selection if there is one.
5.4.3.5 Probable Cause

To activate Probable Causes group, you have to click the check button near the filter name. By default
the check button is set.
Probable Cause List reports all probable causes that Q3 or SNMP NEs could return.
It is multiselect list, that is more than one value of the list can be chosen. It is a very long list, so you can
use Shift button and left button of mouse to select one or plus interval of values or Ctrl button and left button
of mouse to select separated values.
The list is sorted in alphabetical order.
If the check button is selected but no value of the list is selected, the effect is like all values of the list panel
were selected.
1353NM-E Rel. 7.4B

142/532
Operator Handbook
Figure 125. Probable Cause Filter

To deactivate Probable Causes group, you have to uncheck the button near the filter name. Probable
Cause List becomes greyed with his selection if there is one.
Operator Handbook
1353NM-E Rel. 7.4B

143/532
1353NM-E Rel. 7.4B

144/532
Operator Handbook
6 Topology Management
6.1 NEs and Links
The elementary building blocks of any telecommunication network are the Network Elements (NEs). The
connection between two NEs is called a link.
Topology Management can manage following entities:
Several types of NEs:
Basic NEs (that are not remote NEs).
Remote NEs and remote units.
Sub NEs.
6.1.1 Remote NE and Remote Unit

A remote NE is distinguished by its need to be managed by the OS through another NE called master NE.
The remote NE is physically connected to its master NE, which is responsible for the exchange of management information between the OS and the remote NE.
A remote unit is an NE component (a board for example) that is connected to a master NE.
6.1.1.1 Static Link
A static link is used to draw a graphical link only between related NEs. It based on NE attributes which
are not animated. It does not appear in the link.
PNM can manage two types of static links:
'Hierarchical' static links that represent a hierarchical relationship between NEs like for example:
The link between a master NE and a remote NE.
The link between a master NE and a remote unit.
The hierarchical static link management is optional.
'Generic' static links that represent a simple relationship between NEs whatever their type PNM does
not make any control on static links with respect to the topology of the network
6.1.2 Management States

This section presents the different management states of NEs and dynamic links from the OS point of view.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

145/532
Management states are available for any manageable entity, including remote NEs and remote units. In
this section, NE stands for any manageable entity.
The NE and dynamic link management states are as follows:
NE management states: Supervision, Alignment, Communication, Administrative, Usage,

Operational, Local Access, and a single Alarm status.
Dynamic link management states: Supervision, Alignment, Administrative, Operational and a

single Alarm status.
Actions undertaken from Topology Management can influence only the NE management states, not the
link management states.
Management states:
Supervision state: gives information relative to the supervision state of the NE or the dynamic link. There
are four possible values. Operational state and Access state can then be fixed. Possible values are:
Declared: the NE or the dynamic link is just declared to the OS.
Supervised: the NE or the dynamic link is under supervision.
Activating: the NE or the dynamic link is being brought under supervision and no management tasks
can be performed on it.
Deactivating: the supervision process on the NE or the dynamic link is being stopped and no management tasks can be performed on it.
Communication state: reflects the capability of the NE to communicate with the EML. This management
state does not concern dynamic links. Possible values are:
Disabled: the communication between the EML and the NE is interrupted.
Enabled: the EML can communicate with the NE.
Administrative state: reflects the administration of a resource. Possible values are:
Locked: the resource is administratively prohibited from performing services for its users.
Unlocked: the resource is administratively permitted to perform services for its users. this is independent of its inherent operability.
Usage state: reflects the usage of the NE. This management state does not concern dynamic links. Possible values are:
Idle: the resource is not currently in use.
Busy: the resource is in use and it has no spare operating capacity to provide for additional users
simultaneously.
Active: the resource is in use and it has sufficient spare operating capacity to provide for additional
users simultaneously.
Alignment state: indicates whether the NE MIB and its image in the OS are aligned or not. There are five
possible values:
Aligning Up: the system is performing a 'MIB Align Upwards' operation. No operation can be done
on the NE or the dynamic links.
1353NM-E Rel. 7.4B

146/532
Operator Handbook
Topology Management
Aligning Down: the system is performing a 'MIB Align Downwards' operation. No operation can be
done on the NE or the dynamic links.
Aligned: the NE MIB and its image in the OS are identical. In Config: the NE or the dynamic link is
being configured and no alignment has been undertaken yet.
Misaligned: the NE MIB and its image in the OS are not identical and eventually, the NE or the
dynamic link has to be reconfigured.
Auditing: the NE or the dynamic link is under OS supervision and the system is comparing the NE
MIB with its image in the OS.
Local access state: denotes the granting or denial of access for management operations on the NE via
the craft terminal. This management state does not concern dynamic links. There are three possible values:
Granted: the NE can be managed by the local craft terminal.
Requested: the local manager has requested update permission from the remote manager and is
waiting for a reply.
Denied: the NE cannot be managed by the local craft terminal.
Operational state: reflects the capability for the NE or the dynamic link to accept the EML supervision.
There are two possible values:
Disabled: the NE or the dynamic link cannot be supervised. This means the resource is internally
facing a major failure.
Enabled: the NE or the dynamic link can be supervised.
Alarm status: indicates the highest severity alarm currently present on the NE or the dynamic link. There
are six possible values:
Critical: the NE or the dynamic link operational state is disabled, or the NE or the dynamic link presents malfunctions. An immediate corrective operation is required.
Major: the OS and NE or dynamic link MIBs are misaligned, or the NE or the dynamic link presents
dysfunctions. Urgent corrective operation is required.
Minor: the NE or the dynamic link presents dysfunctions. A corrective operation should be taken in
order to prevent more serious fault (for example service affecting).
Warning: it indicates the detection of a potential or impending service affecting fault before any significant effects have been felt. Operation should be taken to further diagnose (if necessary) and correct the problem in order to prevent it from becoming a more serious fault.
Active Pending: the NE or the dynamic link is in a pending state.
Cleared: there is no outstanding alarm within the NE or the dynamic link.
Indeterminate: the OS has not received an update of the current alarms occurring.
A mechanism enables the OS to determine whether it manages the supervised NEs or the supervised
dynamic link. This mechanism enables the OS to detect changes in the NE or in the dynamic link configuration or in the operational state of the NE or the dynamic link. This mechanism is launched automatically after the NE, or the dynamic link, is brought under supervision by the OS. It is stopped if the OS is
shut down or if the NE or the dynamic link is no longer under supervision.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

147/532
Any disruption in the communication link between the OS and the NE or the dynamic link results in an
update of the management states once the OS has detected the communication failure.
6.2 Operations on NEs

This chapter describes the functions offered by the Operations menu.
Figure 126. Operations menu

This menu allows you to:
Get information about an NE or a link.
Modify the access state of an NE.
Consult the management states of an NE or a link.
Manage the NE MIB.
Manage the NE time.
Manage the administrative state of an NE.
Manage the supervision of an NE.
Resynchronize PNM with the EMLs.
1353NM-E Rel. 7.4B

148/532
Operator Handbook
Topology Management
Upload the remote inventory.
Ping one or more NEs.
The Operations menu is configurable.
Information about NEs
6.2.1
This section explains how to display the characteristics of a selected NE.
Select an NE on the Topology Management displayed map.
Use the menu path: Operations Information.
The following dialog box opens:
Figure 127. Information dialog box for an NE

This dialog box is readonly.
To close the dialog box, click on the Close push button.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

149/532
Modifying the Access State of an NE
6.2.2
The NE access state indicates if the NE is managed by the OS or from a craft terminal. This section
describes following actions:
Switch the NE access state from OS to local.
Switch the NE access state from local to OS.
Request a local access from a craft terminal.
Grant the local access for all NEs in requested access state.
Deny the local access for all NEs in requested access state.
6.2.2.1 Switching the NE Access State from OS to Local

This function allows a craft terminal located next to the NE to manage it instead of the OS. This function
is available only from Topology Manager installed in the supervision room. To switch the NE access state
from OS to local, proceed as follows:
Select the NE whose local access state is Denied on the Topology Management map.
Use the menu path: Operations Access State Local
Figure 128. Local AccessSwitch to Local Dialog Box
1353NM-E Rel. 7.4B

150/532
Operator Handbook
Topology Management
The NE local access state changes to Granted

Once the NE is in local access state, the OS cannot manage it anymore. However it continue to provide
some services like:
The reception and processing of alarms.
The switching back to the OS access state.
The access state of a remote NE or a remote unit cannot be modified as it keeps aligned on the access
state of its master NE.
6.2.3
Switching the NE Access State from Local to OS
This function allows the OS to manage an NE that was under control of a craft terminal.
To switch the NE access state from local to OS, proceed as follows:
Select the NE whose local access state is Granted on the Topology Management map.
Use the menu path: Operations Access State OS.
Figure 129. Local AccessSwitch to OS Dialog Box

The NE local access state changes to Denied.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

151/532
The access state of a remote NE or a remote unit cannot be modified as it keeps aligned on the access
state of its master NE.
1353NM-E Rel. 7.4B

152/532
Operator Handbook
Topology Management
6.2.3.1 Requesting a Local Access from a Craft Terminal

This function allows a craft terminal to request a local access to the NE it wants to control.
This function is available only from Topology Management installed in a craft terminal.
To request a local access, proceed as follows:
Select the NE you want to manage by means of the craft terminal on the Topology Management map. Its
local access state must be Denied.
Use the menu path: Operations Access State Requested.
Figure 130. Local AccessSwitch to Requested Dialog Box.

The NE local access state changes to Requested.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

153/532
The following dialog box appears on Topology Management installed in the supervision room:
Figure 131. Local AccessRequested Monitoring Dialog Box

This dialog box warns you (if you are an operator in the supervision room) that the local access state of
an NE is Requested.
As long as you do not answer this request, the New Requested NEs toggle remains red and you cannot
close the dialog box.
So you must grant or deny the local access request by clicking on the Requested to Granted or Requested
to Denied push button.
As soon as you click on one of the two push buttons, the New Requested NEs toggle becomes inactive
and the No New Requested NEs toggle becomes green.
1353NM-E Rel. 7.4B

154/532
Operator Handbook
Topology Management
Request Granted
If you want to grant the request, the following dialog box opens:
Figure 132. OS AccessRequested to Local dialog box

The NE local access state changes to Granted.
Now you can close the Requested Monitoring dialog box.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

155/532
Request Denied
If you want to deny the request, the following dialog box opens:
Figure 133. Local AccessRequested to OS dialog box

The NE local access state changes to Denied.
Now you can close the Requested Monitoring dialog box.
6.2.3.2 Denying the local access for All NEs in Requested Access State
Topology Management allows you in a simple way to deny the local access for all the NEs whose access
state is currently Requested.
To perform this function, use the menu path:
Operations Access State Requested to OS.
The Local AccessRequested to OS dialog box presented in Figure 133. opens.
The Local Access of the concerned NEs changes to Denied.
1353NM-E Rel. 7.4B

156/532
Operator Handbook
Topology Management
Management State Consultation
6.2.4
This section explains how to consult the management states of:
A NE.
A link.
6.2.4.1 Consulting the NE Management States

To consult the management states of an NE, proceed as follows:
Select an NE on the Topology Management map.
Use the menu path: Operations Show Statuses.
Figure 134. Current Status Dialog Box for an NE
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

157/532
The NE user label appears in the title of the dialog box.

This dialog box is readonly.
Unused attributes are greyed.
To close the dialog box, click on Close push button.
Managing the NE MIB
6.2.5
During the construction of the network topology the creation of a new NE in the network is associated with
the description of its configuration in the OS. This NE configuration may be different from the actual physical configuration of the NE, described in the NE MIB (Management Information Base), and an alignment
operation may be necessary to adjust the NE MIB and the OS.
Moreover, during the normal functioning of the network it may be necessary to modify the NE configuration, physically or by using the graphical interface. After that operation an alignment between the NE MIB
and its image in the OS appears to be necessary.
This section explains how to:
Upload the NE MIB into the OS.
Download MIB information from the OS into the NE MIB.
Compare the NE MIB with its image in the OS.
Dump the NE MIB into a file.
The alignment state of dynamic links is not managed by Topology Management application.
1353NM-E Rel. 7.4B

158/532
Operator Handbook
Topology Management
6.2.5.1 Uploading the NE MIB into the OS

This function consists in aligning the OS with the NE MIB.
This operation may be necessary if:
A communication failure between the OS and the NE has occurred.
The NE configuration has been changed during a local management by a craft terminal and the
NE MIB differs from its image in the OS.
To upload the NE MIB into the OS, proceed as follows:

Select the NE on the Topology Management map.
Use the menu path: Operations MIB Align Upwards.
Figure 135. MIB AlignmentAlign MIB Up Dialog Box

The NE configuration contained in the NE MIB is uploaded into the OS. The NE MIB and its image in the
OS are now aligned.
6.2.5.2 Downloading Information from the OS into the NE MIB
This function consists in aligning the NE MIB with the NE configuration coming from the OS.
This operation may be necessary when the OS is launched or if a new configuration is needed for a NE.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

159/532
There are two available possibilities for this operation:
A manual alignment, the NE configuration present in the OS is as much as necessary downloaded into the NE MIB, according to the EML agent decision.
A global alignment, the NE configuration is unconditionally downloaded.
In the first case, the entire NE configuration could be downloaded as well if needed.
To download the NE configuration from the OS into the NE MIB, proceed as follows:
Select the NE on the Topology Management map window.
Use the menu path:

Operations MIB Manual Align Downwards
or
Operations MIB Global Align Downwards
One of the two following dialog boxes opens:
Figure 136. MIB AlignmentAlign MIB Down (Manual) Dialog Box
1353NM-E Rel. 7.4B

160/532
Operator Handbook
Topology Management
Figure 137. MIB AlignmentAlign MIB Down (Global) Dialog Box

The NE configuration contained in the OS is downloaded into the NE MIB. The NE MIB and its image in
the OS are now aligned.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

161/532
6.2.5.3 Compare the NE MIB and Its Image in the OS

This function consists in finding any difference between the NE MIB and its image in the OS.
To compare the NE MIB with its image in the OS, proceed as follows:
On the Topology Management map window, select the NE whose supervision state is Supervised and communication state is enabled.
Use the menu path: Operations MIB Compare.
Figure 138. MIB AlignmentCompare MIBs Dialog Box
1353NM-E Rel. 7.4B

162/532
Operator Handbook
Topology Management
6.2.5.4 Dumping the NE MIB into a File

This function consists in launching a request (dump the NE MIB into a file) that is processed by the EML.
No result is provided by Topology Manager.
The process is carried out even if the NE is not supervised (its supervision state is declared).
This manual operation is intended to give humanreadable information regarding the NE configuration
in the OS.
To dump the NE MIB into a file, proceed as follows:
Select the NE on the Topology Management map window.
Use the menu path: Operations MIB Dump MIB.
Figure 139. MIB AlignmentDump MIB Dialog Box
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

163/532
Managing the NE Time
6.2.6

get the time of an NE
synchronize the NE time with the OS time
6.2.6.1 Getting the Time of an NE
To get the time of an NE, proceed as follows:
On the Topology Management map window, select an NE whose supervision state is Supervised and communication state is enabled.
Use the menu path: Operations Time Get.
Figure 140. Time ManagementGet Time Dialog Box (before command execution)
1353NM-E Rel. 7.4B

164/532
Operator Handbook
Topology Management
The NE time appears in the Command Status, as shown in figure below:
Figure 141. Time ManagementGet Time Dialog Box (after command execution)
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

165/532
6.2.6.2 Synchronizing the NE Time with the OS Time

To synchronize the NE time with the OS time, proceed as follows:
On the Topology Management map, select an NE whose supervision state is Supervised and
communication state is enabled.
Use the menu path: Operations Time Set.
Figure 142. Time ManagementSet Time Dialog Box (before command execution)
1353NM-E Rel. 7.4B

166/532
Operator Handbook
Topology Management
The NE time appears in the Command Status, as shown in figure below. It has changed. It is now the same
as the OS time.
Figure 143. Time ManagementSet Time Dialog Box (after command execution)
NOTE: If the NE is associated with an NTP server, you cannot synchronize its time with the OS time.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

167/532
Managing the Administrative State of an NE
6.2.7
To change the administrative state of an NE, proceed as follows:
On the Topology Management map window, select an NE whose supervision state is Supervised, communication state is enabled and administrative state is unlocked (or locked).
Use the menu path:

Operations Administration Lock
(or Operations Administration Unlock).
One of the two following dialog boxes opens:
Figure 144. AdministrationLock Dialog Box
1353NM-E Rel. 7.4B

168/532
Operator Handbook
Topology Management
Figure 145. Administration. Unlock Dialog box

The NE administrative state changes to Locked (or Unlocked).
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

169/532
Managing the Supervision of an NE
6.2.8
Supervising NEs is an essential aspect of the network management. It enables the gathering of information concerning the behavior of the NE with respect to its functional state.
The supervision of an NE consists in establishing a communication that allows the user to perform EML
operations such as configuration and alarm management.
The NE address must have been declared before starting the supervision of this NE. Otherwise error messages will be displayed.
Start the NE supervision.
Stop the NE supervision.
6.2.8.1 Starting the NE Supervision

You can perform a 'start supervision' using one of the following options:
Default.
Align up.
Align down.
Enhanced align down.
Audit.
No alignment.
NOTE: Since remote NEs or remote units are automatically brought under supervision when the supervision of the corresponding master NE is started, the 'start supervision' operation is not available for such
remote elements.
Default: To perform a 'start supervision' (align up, align down, enhanced align down, audit or no alignment) defined in the Type/Release configuration file, use the menu:
Operations Supervision Default.
Align Up: To align the OS local configuration with the NEs at the end of the 'start supervision', use the
menu:
Operations Supervision Align Up.
Align Down: To align the NE configurations with the OS at the end of the 'start supervision', use the menu:
Operations Supervision Align Down.
Enhanced Align Down: To align the NE configurations with the last OS at the end of the 'start supervision', use the menu:
Operations Supervision Enhanced Align Down.
Audit: To compare the NE MIB with its image in the OS during the 'start supervision', use the menu:
Operations Supervision Audit.
No Alignment: To perform a 'start supervision' without any alignment, use the menu:
Operations Supervision No Alignment.
1353NM-E Rel. 7.4B

170/532
Operator Handbook
Topology Management
Start Supervision Command Dialog Box.

Whatever the 'start supervision' option you have chosen, a command dialog box like the one in figure
below opens:
Figure 146. Example of a Supervision Dialog box

The NE supervision state changes to Supervised.
Once the NE is supervised, an association between the NE and the OS is created. Thus Topology Management application will be able to animate the NE symbol colour according to the changes of the NE
states.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

171/532
6.2.8.2 Stopping the NE Supervision

The supervision of remote NEs or remote units cannot be stopped individually. Rather, it is automatically
stopped when the supervision of the corresponding master NE is stopped.
To stop the supervision of an NE, select it then use the menu path:
Operations Supervision Stop.
Figure 147. SupervisionStop Dialog Box

The NE supervision state changes to Stopped.
6.2.8.3 Abort the NE Supervision
The Abort Supervision immediately close the management session. Differently from Stop Supervision it
does not perform PM data collection.
To Abort the supervision of an NE, select it then use the menu path:
Operations Supervision Abort.
It requires action confirmation.
1353NM-E Rel. 7.4B

172/532
Operator Handbook
Topology Management
Resynchronizing Topology Management
6.2.9
To make sure that the NE and dynamic link states displayed by Topology Management are really up to
date, you can perform a manual resynchronization by proceeding as follows:
Select the NE or dynamic links to be resynchronized.
Use the menu path: Operations Resynchronize.
You can also resynchronize completely Topology Management, but in that case, you must know that this
can take a long time according to the number of NEs and links to be resynchronized.
At the end of the resynchronization, the following message dialog box appears.
Figure 148. Message dialog Box for Topology Management Resynchronization

NOTE: If the resynchronization operation fails, an error message is displayed.
6.2.10
Uploading the Remote Inventory
This function consists in launching the EML process that inventories the components of an NE. No
response is provided by PNM.
To perform this operation, proceed as follows:
Select an NE on the Topology Management map window.
Use the menu path: Operations Upload Remote Inventory.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

173/532
Figure 149. Upload Remote Inventory Dialog Box

N.B.
The uploaded Remote Inventory file can be found under the directory /usr/Systems/1353NM/
data/ri
6.2.11
Ping NE
This function allows to ping one or several NEs to see if they are reachable. The function is activated from
menu 'Operations'. There are two different possibilities to use 'Ping NE'.
a)
No NEs selected on the map.
Select from menu operations function 'Ping NE' as shown in following figure:
1353NM-E Rel. 7.4B

174/532
Operator Handbook
Topology Management
Figure 150. Menu Operations: Ping NE

Selecting 'PIing NE' the function window will be displayed, one or more NEs can be selected to perform
the ping function to test the whether the NE is reachable or not.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

175/532
Figure 151. Ping NE function window

Select the NEs from the list clicking on the arrow on the left, then click on the 'Ping Selected' button to
execute the ping. A window with the ping result for the selected NEs will be displayed.
b)
One or more NEs selected on the map.
Select one or more NEs on the map as shown in following figure:
1353NM-E Rel. 7.4B

176/532
Operator Handbook
Topology Management
Figure 152. Select NEs on a map

Select from 'Operations' menu the function 'Ping NE'. For each selected NE a dialog box is displayed with
the ping operation result as shown in following figure.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

177/532
Figure 153. Ping result for selected NEs
1353NM-E Rel. 7.4B

178/532
Operator Handbook
Topology Management
6.3 Inventories and Navigations

This chapter describes the functions offered by the Tools menu (see below figure)
Figure 154. Tools Menu

N.B.
6.3.1
Access the global NE inventory.
Set an inventory selection filter.
Navigate towards other applications.
Monitor the creation/deletion of an NE or a link.
Associate an NE to an NTP server.

The Show Alarms and Show Equipment items are examples of one and a same generic command. There could be other similar items using this generic command or nothing.
Accessing the Global NE Inventory
The global NE inventory lists all the NEs managed by PNM, including master NEs and remote NEs. To
access the global NE inventory, use the menu path:
Tools NE Inventory Global...
The NE: Global Inventory window that opens is displayed hereafter:
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

179/532
Figure 155. Global NE Inventory

Expandable Node
A [+] (or [-]) symbol preceding a node label means that the node contains a branch that can be expanded
(or shrunk). There are two ways of expanding/shrinking a node: you can either click on the [+] or [-] symbol
or doubleclick on the node label (for example "Milano" in the previous figure).
6.3.2 NE Global Inventory Layout

The NE Global Inventory window layout can be of several types. To setup the desired layout select the
menu path: Inventory Layout.
The available layouts are listed in the submenu as shown in following figure:
1353NM-E Rel. 7.4B

180/532
Operator Handbook
Topology Management
Figure 156. NE Global Inventory Layout submenu
Figure 157. Layout Examples
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

181/532
6.3.3
Definition of an Inventory Selection Filter
This function consists in defining the selection filter criteria for the NEs of an NE Inventory window.
To define the selection filter criteria for the NEs of an NE Inventory window, use the menu path:
Inventory Contents Filter.
The NE Inventory Selection Filter dialog box that opens is:
Figure 158. NE Global Inventory Filter

Configuring the Filter
The filter is divided on two panels: Static Attributes and Dynamic Attributes.
Static Attributes are the NE configuration attributes: NE Type and version, NE label and location, NE
Supervision area and EML domain, ACD and creation date interval.
Dynamic Attributes are all the NE attributes that changes during management: Alarms, Supervision,
Alignment, Communication, Administrative, Access.
The filter can be configured selecting one or more static or dynamic attributes.
Resetting the Filter
In the Static Attributes panel, clicking on the Reset push button deactivate the filter. In that case, all the
NEs are selected.
1353NM-E Rel. 7.4B

182/532
Operator Handbook
Topology Management
In the Dynamic Attributes panel, the Reset push button operates like a global toggle to activate or deactivate all the other ones. In both cases, all the NEs will be selected in the table area of the NE Inventory
window. This just allows you to more quickly eliminate (or keep) some attributes rather than keep (or eliminate) one by one all the other ones.
Applying the Filter

To make the filter active, click on the Apply push button. In the NE Inventory window, the NEs matching
the selection filter criteria are selected.
This action does not deactivate the filter.
6.3.4 Population
This function is used to populate a map selecting the already created NEs.
To display the population panel select the menu path: Inventory Population.
Following window will be displayed:
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

183/532
Figure 159. Population Window

Select the desired options and confirm with Apply button. The map will be populated using the selected
options.
Navigation towards Other Applications
6.3.5
Topology Management application can be integrated with other applications which allows you for example
to:
Manage alarms.
Visualize and configure the NE equipment.
Composite NE
In case of Composite NE (CNE), you also can navigate towards either the composite NE view or the host
NE view.
1353NM-E Rel. 7.4B

184/532
Operator Handbook
Topology Management
6.3.5.1 Alarm Management

Thanks to AS, you can perform operations on the alarms occurring on an NE. To access AS, proceed as
follows:
Select an NE.
Use the menu path: Tools Show Alarms.
The AS Alarm sublist window related to the selected NE opens.

This is an example of integration of Topology Management with AS. We may also decide at integration
time that there will be only one Alarm sublist window for all the currently selected NEs.
Refer to the ALMAP AS User's Guide for more information about the alarm management.
6.3.5.1.1 Visualizing Alarm Information
For each NE symbol present within a submap, the AS application allows the display of the corresponding
alarm synthesis information:
A flashing symbol when the NE is impacted by incoming alarms.
The total and acknowledged active alarm numbers.
The most severe alarms.
Refer to the ALMAP AS User's Guide for more information about the NE symbol management by AS
6.3.5.2 Navigating towards an Equipment View
To navigate towards an equipment (or a CNE) view, proceed as follows:
Select an NE.
Use the menu path: Tools Show Equipment.
The equipment view related to the selected NE opens.

Refer to the external application documentation for more information.
6.3.6
Creation/Deletion Monitoring
This function consists in informing you when an element (NE or link) has been created or removed from
the network since either the beginning of the PNM session or the last purge.
The creation/deletion monitoring function can be activated using following menu path:
Tools Show Monitor.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

185/532
Figure 160. Monitor dialog box (Creation Monitoring Panel)

This dialog box includes two similar panels: one for the created elements, the other one for the removed
elements. For each panel:
The Name list is ordered as follows: the first line is the last created/removed element. The field located
below the list gives the number of concerned elements.
The Purge push button allows you to reset the content of the list.
The Quiet and Popup toggle buttons allow you to choose the way to be informed:
Quiet: the Monitor dialog box is updated on creation/deletion event and you can consult the list when
you want.
Popup: the Monitor dialog box is also updated but is automatically raised on create/deletion event.
Add Selection to Map: some NEs can be selected and added to the map.
1353NM-E Rel. 7.4B

186/532
Operator Handbook
Topology Management
Add all to map: all the NEs are added to the map.
Starting the Monitoring
To start the monitoring, click on the Start push button.
The Start push button becomes a Stop push button.
Stopping the Monitoring
To stop the monitoring, click on the Stop push button.
Closing the Dialog Box
This action does not stop nor purge the monitor.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

187/532
6.4 Window Management

This chapter describes the functions offered by the File menu.
Figure 161. File Menu

6.4.1
Create a new map.
Set the map parameters.
Use the local persistency.
Open a map object.
Duplicate the main window.
Close the current window.
Open the Console window.
Exit from Topology Management.
Creating a New Map
This function consists in opening a new map that replaces the currently displayed one.
To create a new map, use the menu path: File New Map.
1353NM-E Rel. 7.4B

188/532
Operator Handbook
Topology Management
Figure 162. Confirmation Dialog Box for Creating a New Map

The above dialog box appears if a map is already displayed. Click on the <Yes>, if you want to save the
currently displayed map, or <No> push button. A new empty map opens with default parameters.
When you click on the Yes push button, a file chooser dialog box opens allowing you to give a name to
the map to be saved.
As soon as the current map is saved, a new empty map opens with default parameters.
Setting the Map Parameters
6.4.2
This function consists in setting synthesis engine parameters that will be used in the whole map (i.e. in
all the views belonging to the map).
A synthesis engine propagates abnormal operation data through the views of a map. For instance the
alarm status of an NE in the lowest level view of a map can be made visible at the highest level view of
the same map.
To set the map parameters, use the menu path: File Map Parameters.
Figure 163. Map Parameters Dialog Box

This dialog box allows you activate or not following types of synthesis engines:
Operational State Propagates the disabled operational state.
Alarm Status
Communication State
Propagates any alarm status.

Propagates the disabled communication state.
Then for each enabled synthesis engine type, you can choose a synthesis mode.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

189/532
The Default mode propagates the flashing symbol state, the disabled communication state and/or the disabled operational state at the view level as soon as at least one of the symbol contained in the view is
in this state.
For the Alarm Status synthesis engine, three modes are provided:
a)
Default.
The table below gives the way the alarm status is propagated through the views (a symbol is 'normal' when
its alarm status is clear).
Table 17. Alarm Status Propagation by Default
States of the Symbols in the View
Alarm Status of the View
Symbols are neither normal nor abnormal
Indeterminate
All the symbols are normal
Cleared
One symbol is abnormal and all other ones are nor- Warning
mal
More than one symbol is abnormal and more than Minor
one other symbol is normal
One symbol is normal and all other ones are abnor- Major
mal
All the symbols are abnormal
b)
Critical
Threshold value.
The synthesis engine propagates the alarm status according to the percentages given below:
c)
Active pending: 70%.
Indeterminate: 50%.
Warning: 30%.
Minor: 20%.
Major: 10%.
Critical: 5%.
Most critical.
The synthesis engine propagates the most critical alarm status of the symbol belonging to the view.
Adding a Comment.
You can add a comment in the Map Comment field.
Enabling/Disabling a Synthesis Type
To enable/disable a synthesis engine type, click on the corresponding tick box. A tick means the synthesis
engine is enabled.
1353NM-E Rel. 7.4B
190/532
Operator Handbook
Topology Management
Choosing a Synthesis Mode

To choose the synthesis mode of a previously enabled synthesis type, click on the down arrow of the corresponding option button, then select the mode in the list which appears.
Using the Local Persistency
6.4.3
The local persistency allows you to store and retrieve complete maps (and the submaps, objects and
symbols they contain) in map files. Thanks to the local persistency, you can:
Save a map as a local map.
Save a local map.
Restore a local map.
Delete a map file.
Reset the local database.
6.4.3.1 Saving a Map as Local Map

To save for the first time the current map in a map file, use the menu path:
File Local Persistency Save Map As.
A file chooser dialog box opens allowing you to give a name to the map to be saved.
Figure 164. Save Local Map Dialog Box
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

191/532
6.4.3.2 Saving a Local Map

To save a map already declared in a map file, use the menu path:
File Local Persistency Save Map
A file chooser dialog box opens (see Figure 164.) allowing you to end the saving if the map is a new map,
the saving operation is automatic if the map was already saved in a file.
6.4.3.3 Restoring a Local Map
To restore a map from a map file, use the menu path:
File Local Persistency Restore Map.
Two cases may occur:
If you had not modified the currently displayed map, a file chooser dialog box opens allowing
you to select the map to be retrieved.
Figure 165. Restore Map Dialog Box
If you had modified the currently displayed map, the dialog box to confirm the saving of the current map opens:
When you click on the Yes push button, a file chooser dialog box opens allowing you to
give a name to the map to be saved.
As soon as the current map is saved, another file chooser dialog box (see Figure 165.)
opens allowing you to select the map to be retrieved.
6.4.3.4 Deleting a Map File

To delete a map file, use the menu path:
File Local Persistency Delete Map File.
1353NM-E Rel. 7.4B

192/532
Operator Handbook
Topology Management
A file chooser dialog box opens allowing you to select the map file to be removed.
Figure 166. Delete Map Dialog Box
6.4.4
Duplicating the Main Window
This function allows you to display several main windows at the same time. That can be useful, for example, to visualize two different views of the map.
To duplicate the main window, use the menu path: File Duplicate Window.
A new main window opens. Its contents is exactly the same as the other main window.
6.4.5
Closing the Current Window
This function allows you to close the current main window. It is available only when several main windows
are open.
To close the current main window, use the menu path: File Close.
6.4.6
Opening the Console Window
The Console window provides you with information about errors related to TVA.
To open the Console window, use the menu path: File Show Console.
The following window opens:
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

193/532
Figure 167. Console Window

This window is read only. At any time, you can:
remove its contents by clicking on the Clear push button.
close it by clicking on the Close push button.
The error messages can also be displayed on the message area at the bottom of the main window.
6.4.6.1 Using a Shortcut Button to open the Console Window

At the bottom of the Topology Management main window, on the left of the Alcatel logo, a button in form
of screen represents the Console window. When an error occurs, a red "!" sign appears in the screen (see
figure below).
Figure 168. Screen Button Indicating a New Error

By clicking on this button, you can quickly open the Console window.
1353NM-E Rel. 7.4B

194/532
Operator Handbook
Topology Management
6.5 View Management

This chapter describes:
The functions offered by the View menu.
The management of the view filters.
The use of the Filter Editor window.
Using the View Menu
6.5.1
Figure 169. View Menu

Configure a display filter.
Activate/deactivate a display filter.
Configure a command filter.
Activate/deactivate a command filter.
Zoom in/out a view.
Manage the related views.
Set the general parameters of a view.
Set the display parameters of a view.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

195/532
6.5.1.1 Configuring a Display Filter

This function consists in choosing the criteria of a display filter.
A display filter can be used to hide or display symbols in all the views of the current map, according to
their properties.
The configuration and management of the display filters is performed through the Filter Editor window.
To configure a display filter, use the menu path: View Edit Filter.
The Filter Editor window opens:
Figure 170. Filter Editor window

When no filter exists, you can access the Filter Editor window for the display filter by clicking on the corresponding icon in the tool bar.
6.5.1.2 Activating/Deactivating a Display Filter
This function consists in applying or removing the current display filter to all the views of the current map.
To activate/deactivate a display filter, use the menu path: View Activate Filter or click on the corresponding icon in the tool bar (see Figure 152.).
When the display filter is activated:
A tick appears in the small square located just before the menu item.
The current view in the view area of the main window displays only the symbols whose properties match this filter.
The icon corresponding to the display filter in the tool bar is no longer crossed out.
6.5.1.3 Configuring a Command Filter

This function consists in choosing the criteria of a command filter.
1353NM-E Rel. 7.4B

196/532
Operator Handbook
Topology Management
A command filter can be used to apply command only on symbols whose properties match the item
defined in the filter.
The configuration and management of the command filters is performed through the Filter Editor window.
To configure a command filter, use the menu path: View Edit Command Filter.
The Command Filter Editor window opens:
Figure 171. Command Filter Editor

When no filter exists, you can access the Filter Editor window for the command filter by clicking on the
corresponding icon in the tool bar.
6.5.1.4 Activating/Deactivating a Command Filter
This function consists in applying or removing the current command filter to all the views of the current
map.
To activate/deactivate a command filter, use the menu path:
View Activate Command Filter
or click on the corresponding icon in the tool bar (see Figure 152.).
When the command filter is activated:
A tick appears in the small square located just before the menu item.
The action requested by the client application will concern only the symbols whose properties
match this filter.
The icon corresponding to the command filter in the tool bar is no longer crossed out.
The display filter and the command filter are independent. When a display filter is applied, some symbols
may be hidden, but the command filter may involve them even so.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

197/532
6.5.1.5 Zooming in/out a View

This function allows you to zoom in/out the current view in the view area.
There are three main zoom functions:
Enlargement of a zone of the view

Application of an enlargement/reduction percentage
Adaptation to the size of the view area
Zone
To define the view zone to be enlarged use the menu path:
View Zoom Box.
The cursor becomes a cross which allows you to select a zone that will be enlarged.
Percentage
To apply an enlargement/reduction percentage on all the view displayed in the view area use the menu:
View Zoom.
Select a percentage in the submenu that appears.
100% corresponds to the display by default.
Adaptation
To adapt the size of the current view to the size of the view area use the menu path:
View Zoom Fit.
Shortcuts
Topology Management offers shortcuts for performing more quickly the zoom functions:
Type <I> to apply the zoom value by default (100%).
Type <Ctrl>+ U to zoom in.
Type <Ctrl>+ Z to zoom out.
Type <F> to adapt the view to the size of the view area.
6.5.1.6 Managing the Related Views

This function consists in associating a view (called 'related view') to the current one. You can then navigate
at any time from the current view towards the related view.
To manage the related views of the current one, use the menu path:
View Related Views.
1353NM-E Rel. 7.4B

198/532
Operator Handbook
Topology Management
Figure 172. Related Views Dialog Box

This dialog box displays the name of the current view.
The Related Views list presents all the related views that have been associated to the current one.
The Available Views area presents in the form of a tree all the views that can be set as related.
To set a view as related of the current one:
Select it in the Available Views area.
Click on the Add push button.
To remove a related view:
Select it in the Related Views list.
Click on the Remove push button.
To remove all the related view from the Related Views list, click on the Clear push button.
6.5.1.7 Setting the General Parameters of a View
The general parameters of a view are defined as follows:
View name.
Image used as background.
Layout.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

199/532
TVA offers two ways of laying out the symbols in a view:

a)
RowColumn layout (by default).
Figure 173. Example of a RowColumn Layout

Each symbol is centered in a cell whose size is based on the largest and highest symbol size in the view.
All the cells are arranged in rows and columns.
This layout is independent of possible links between symbols.
You can move a symbol by dragging it on an other symbol in the view. This permutes both symbols.
1353NM-E Rel. 7.4B

200/532
Operator Handbook
Topology Management
b)
Cartesian layout
Figure 174. Example of a Cartesian Layout

Each symbol is positioned on the view according to its (x, y) coordinates.
You can move a symbol anywhere in the view.
To set the general parameters of a view use the menu path:
View View Parameters.
Figure 175. View Parameters Dialog Box
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

201/532
In the Name field, enter the view name.

Click on the Background option button, then select a image file in the list that appears. Select None to have
no background.
6.5.1.8 Setting the Display Parameters of a View
This function allows you to choose the way of displaying the symbol properties.
In fact the symbol properties (symbol name, symbol type, different states,...) can be displayed in the symbol itself and/or by means of an information box (also called 'balloon').
For more detailed description about the map view, refer to section 2.3.
To set the display parameters of a view use the menu path:
View Display Options.
Figure 176. Options Window

In the Property Display Customization table, for each line, select the way of displaying the corresponding
property, by ticking:
The In Renderer column so that the property appears in the symbol itself.
The In Balloon column so that the property appears in the information box.
Use the vertical scrollbar to reach the invisible lines.

The display parameters apply to all the views of the current map.
1353NM-E Rel. 7.4B

202/532
Operator Handbook
Topology Management
Managing the View Filters
6.5.2
A filter is a logical "AND" expression of elementary items. Each item is a comparison of a property having
one or several values (like the alarm status property for instance).
TVA offers two kinds of filters:
The display filter.
The command filter.
Display Filter
The display filter is used to hide or display symbols in the current view, according to their properties. For
instance you may want to display in a view only NEs whose alarm status is Critical.
Command Filter
The command filter is used to apply command only on symbols whose properties match the item defined
in the filter.
This kind of filter can be used for applying commands of the client applications. The standard TVA commands (Cut, Copy, Paste,...) are not concerned.
Filter Editor Window
The Filter Editor window allows you to manage and edit the display and command filters.
For more detailed information, refer to section 6.5.1.
Filter Editor Window
6.5.3
The Filter Editor window allows you to:
Manage the display and command filters.
Modify the current display or command filter.
This window is composed of three areas (from top to bottom):
a menu bar including:
The File menu that allows the filter management.
The Help menu whose About Filter Editor item accesses the contextual help on line.
A table showing the items of the current filter.
A working area containing different fields and buttons and allowing you to modify the current filter.
To open the Filter Editor window, use the menu path:

View Edit Filter or Edit Command Filter
or click on the corresponding icon in the tool bar (only when no filter exists).
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

203/532
Figure 177. Filter Editor Window
6.5.3.1 Managing Filters

The filter management is performed by using the File menu of the Filter Editor window.
Figure 178. File Menu of the Filter Editor Window

Apply the filter to all the views of the current map. The icon corresponding to the filter in the
tool bar is no longer crossed out.
Close the Filter Editor window. If the filter currently displayed in the window has not been
applied, a confirmation dialog box opens.
Revert to the currently applied filter.
Create a New filter. This action empties the working area of the Filter Editor window.
Open an existing filter, by means of a file chooser dialog box.
Save the current filter.
Save the current filter As another name, by means of a file chooser dialog box.
Delete a filter, by means of a file chooser dialog box.
1353NM-E Rel. 7.4B

204/532
Operator Handbook
Topology Management
6.5.3.2 Modifying the Current Filter

To modify the current filter, use the working area of the Filter Editor window.
Figure 179. Working Area of the Filter Editor Window

Adding an Item
To add an item:
Click on the option button located below Property, then select a symbol property.
Click on the option button located below Operator, then select the operator to be applied
between the property and an available value.
According to the property and operator previously chosen, the area located below Value may become a
scrollable list, an option button or a text entry field.
Choose or enter a value.
Click on the Add push button.
The item is added at the end of the table.

Modifying an Item
To modify an item:
Select an item in the table.
The selected item appears in the working area.
Modify one or several elements of this item.
Click on the Modify push button.
The modified item replaces the former one in the table.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

205/532
Removing an Item
To remove an item:
Select an item in the table.
Click on the Remove push button.
The removed item disappears from the table.
1353NM-E Rel. 7.4B

206/532
Operator Handbook
Topology Management
6.6 Symbol Management
Figure 180. Edit Menu

6.6.1
Create a child view.
Add a graphic symbol.
Add a graphic link.
Improve the layout display.
Activate/deactivate the frozen mode.
Select all the symbol of a view.
Cut a symbol.
Copy a symbol.
Paste a symbol.
Delete a symbol from a view.
Delete all the symbols from all the views.
Creating a Child View
This function consists in creating an empty child view in the current view.
To create a child view use the menu path: Edit Create Child View.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

207/532
Figure 181. Child View Creation Dialog Box

In the Name field, enter the child view name.
Choose a symbol by clicking on it.
Click on the Apply push button.
NOTE: Several child views may be created in the same parent view.
As soon as the last child view is created, click on the Close push button to close the dialog box.
The position of the child view symbol newly created depends on the layout mode (see chapter 6.5.1.7)
of the parent view:
In RowColumn layout mode, the new symbol is positioned at the last row and column of the
view area.
In Cartesian mode, the symbol is positioned in the center of the view area. If the creation has
been requested from the contextual menu, the symbol is positioned at the location of the cursor.
1353NM-E Rel. 7.4B

208/532
Operator Handbook
Topology Management
Adding a Graphic Symbol
6.6.2
This function consists in adding a graphic symbol in the current view.

A graphic symbol is a TVA object that is not managed by the client application. It is the reason why it cannot
represent an NE and cannot be supervised.
To create a graphic symbol use the menu path: Edit Add Symbol.
Figure 182. Graphic Symbol Creation Dialog Box
N.B.
Click on the Type option button, then select a graphic symbol type.
In the User Label field, enter the graphic symbol name.

Several graphic symbols may be created by using the same dialog box.
As soon as the last graphic symbol is created, click on the Close push button to close the dialog box.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

209/532
Adding a Graphic Link
6.6.3
This function consists in adding a graphic link in the current view.

A graphic link is a TVA object that is not managed by the client application. It is the reason why it cannot
be supervised.
To create a graphic link:
Select both extremities of the link.
Use the menu path: Edit Add Connection.
Figure 183. Graphic Connection Creation Dialog Box

The dialog box indicates the user labels of both connection extremities.
Click on the Type option button, then select a graphic link type.
In the User Label field, enter the graphic link name.
Click on the Close push button to close the dialog box.
1353NM-E Rel. 7.4B

210/532
Operator Handbook
Topology Management
Improving the Layout Display
6.6.4
This function is useful to make the display of the network symbols more understandable (when for example the links are tangled).
To improve the layout display, use the menu path: Edit Layout Network.
When this function is used, the layout is forced to the cartesian mode (see Figure 174.).
Activating/Deactivating the Frozen Mode
6.6.5
The frozen mode prevents you to move the symbols in a view whose layout is in Cartesian mode.
To activate (or deactivate) the frozen mode, use the menu path: Edit Frozen Mode.
When the frozen mode is activated, a tick appears in the small square located just before the menu item.
Selecting All the Symbols
6.6.6
This function allows you to select all the symbols of the current view.
This selects in fact the objects represented by the symbols. All the symbols representing those objects
are selected in all the views where they appear.
To select all the symbols, use the menu path: Edit Select All.
Cutting a Symbol
6.6.7
This function consists in moving the selected symbol in the clipboard so that it can be pasted elsewhere.
NOTE: This does not concern the object represented by the symbol. The selected symbol is
removed only from the current view.
Only symbols that represent MEs and child views can be cut.
When an extremity of a link is removed, the link itself disappears.
To cut a symbol:
Select it.
Use the menu path: Edit Cut.
The selected symbol disappears from the current view, but it remains available to be pasted in another
view.
Several symbols can be selected to be cut at the same time.
6.6.8
Copying a Symbol
This function consists in duplicating the selected symbol in the clipboard so that it can be pasted in the
same view or elsewhere.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

211/532
This does not concern the TVA object represented by the symbol. Only the symbol selected in the current
view is duplicated.
Only symbols that represent MEs and child views can be copied.
To copy a symbol:
Select it.
Use the menu path: Edit Copy.
The selected symbol is duplicated in the clipboard.

Several symbols can be selected to be copied at the same time.
Pasting a Symbol
6.6.9
This function consists in pasting in the current view one or more symbols that have been previously put
in the clipboard at the time of a cut or copy operation.
To paste the contents of the clipboard, use the menu path: Edit Paste.
The contents of the clipboard is moved to the current view.
When pasting a symbol that was a link extremity in a view that contains the other link extremity, the link
is restored, but for a graphic link.
6.6.10
Deleting a Symbol
This function consists in definitely removing a symbol from the current view.
This does not concern the TVA object represented by the symbol. Only the symbol selected in the current
view is removed, except the offpage connector that is removed in both views where it appears.
Any symbol can be deleted.
To delete a symbol:
Select it.
Use the menu path: Edit Delete.
A confirmation dialog box opens. Several symbols can be selected to be deleted at the same time.
6.6.11
Deleting All the Symbols from All the Views
This function consists in definitely removing all the symbols of a TVA object from all the views.
The disappearance of all the symbols of a TVA object leads to the disappearance of the TVA object itself.
Any symbol can be deleted.
1353NM-E Rel. 7.4B

212/532
Operator Handbook
Topology Management
To remove a symbol from all the views, use the menu path: Edit Delete from all views.
A confirmation dialog box opens. Several symbols can be selected to be deleted at the same time.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

213/532
6.7 Navigation
This chapter describes the functions offered by the Go menu that is a way of navigating within the views
of a map (see chapter 6.5).
You can also navigate:
By means of the tree area.
By opening an object.
Navigating by Using the Go Menu
6.7.1
Figure 184. Go Menu

The items of the Go menu are as follows:
Root: to reach the root view.
Backward: to go back to the view that had been displayed before the current one.
Forward: to go back to the view that had been displayed after the current one.
Related Views: to reach one of the related views of the current one.
1353NM-E Rel. 7.4B

214/532
Operator Handbook
Topology Management
6.8 Creation/Deletion of NEs or Links

This chapter describes the functions offered by the Declarations menu.
Figure 185. Declarations Menu

Create an NE or a link.
Delete an NE or a link.
Modify the characteristics of an NE or a link.
Clone an NE.
Set the NE addresses.
Check address.
Create ISA NE.
Rename ISA NE.
The Declarations menu is configurable.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

215/532
6.8.1
Creation of NEs or Links
6.8.1.1 Creating an NE
There are two methods for creating a NE:
either by providing all the necessary NE characteristics (type and release, user label and other optional
parameters) or by copying from the OS the configuration of an existing NE then providing only another
user label.
The second method is called 'NE cloning'.
Remote NE
As the remote NEs are not selfsufficient, they require a particular creation procedure.
After the NE Creation
Except for remote NEs, the creation procedure does not imply specifying all the information needed to
start the NE supervision. The NE address is always specified some time after the NE creation and before
starting the NE supervision.
The EML agent supplies the default OS addresses for the NE during the synchronization phase of the creation process. These values can be overridden later.
Mediation Devices
Certain types of NEs (Q2 NEs) cannot exchange their management information directly with the OS,
therefore they need sending their information via a mediation device. The mediation device need not being
specified at creation time, but rather once the network address has been set.
Creating an NE
To create an NE, use the menu path:
Declarations Create NE.
1353NM-E Rel. 7.4B

216/532
Operator Handbook
Topology Management
Figure 186. NE Creation Dialog Box

Select a Family, a Type and a Release for the NE to be created by using the corresponding option buttons.
NOTE: The NE types you can choose depend on the NE family you just have been selecting. In the same
way, the choice of NE releases depends on the NE type previously selected.
In the User Label field, enter the user friendly name of the NE.
In the Location Name field, enter the location where the NE will be created. This field may be
optional, according to the PNM configuration.
Use the Supervision Area option button to force the allocation of the NE to an EML domain
belonging to this supervision area. PNM will assign the NE creation to the EML agent having
the biggest capacity in terms of NEs among those supporting the required NE type and release
in the supervision area.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

217/532
Use the EML Domain option button to force the assignment of the NE to that EML domain, provided that it supports the required NE type and release. The list of running EMLs depends on
the previously chosen supervision area.
NOTE: If none of the two previous attributes (supervision area and EML domain) are provided,
the NE will be allocated to the least loaded EML domain among all of those supporting the
required NE type and release.
NOTE: Both attributes are compatible. In case of conflict (no EML domain in the specified
supervision area), an error message is displayed.
Use the ACD option button to select the Access Control Domain of the NE.
NOTE: When PNM runs in nonsecured mode, the ACD option button does not exist.
Launching the Creation

To trigger the creation, click on the Apply push button.
Once you click on the Apply push button, the NE symbol appears in the current submap.
Its supervision state is Declared and its characteristics (except the NE address) are defined in the OS.
6.8.1.2 Creating a Remote NE
To create a remote NE, proceed as follows:
Select the master NE to which you want to attach the remote NE on the current submap.
Use the menu path:
Declarations Create Remote NE.
1353NM-E Rel. 7.4B

218/532
Operator Handbook
Topology Management
Figure 187. Remote NE Creation Dialog Box

In this dialog box, you cannot modify the Master NE, Supervision Area and EML Domain fields. In fact
they contain the values corresponding to the selected master NE.
Fill in the rest of the dialog box as for a basic NE. The available types and releases are only the ones
allowed for this kind of master NE.
As the master NE may support several remote NEs connected to it, it is necessary to identify the slot of
the master NE in which the remote NE should be plugged. Enter the remote NE index number in the RNE
Index field. The index value must range from the values given in the PNM resource file.
Launching the Creation
To trigger the creation, click on the Apply push button.
The Remote NE Creation dialog box in viewer mode contains an additional field named Comments. The
remote NE symbol is created in the same submap as the master NE and a static link is automatically added
between them.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

219/532
6.9 Deletion of NEs

This section explains how to delete an NE.
6.9.1
Deleting an NE
Deleting an NE consists in removing its characteristics from the OS. This function is not available on
remote units.
To remove an NE, proceed as follows:
Select an NE on the submap.
Use the menu path: Declarations Delete Generic.
Figure 188. Deletion Dialog Box

The NE disappears from the submap window.
1353NM-E Rel. 7.4B

220/532
Operator Handbook
Topology Management
6.10 Modification of NE or Link Characteristics

modify the NE characteristics.
modify the remote NE characteristics.
This section does not deal with the address change.
6.10.1
Modifying the NE Characteristics
To modify the characteristics of an NE, proceed as follows:
Select an NE on the submap window.
Use the menu path: Declarations Modify.
Figure 189. Modification Dialog Box for a basic NE
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

221/532
The title of the dialog box recalls the user label of the NE to be modified.
You can modify only the User Label, Location Name and Comment fields and choose another ACD.
Applying the Modifications
To validate the modifications, click on the Apply push button.
The NE characteristics are updated in all open windows.
6.10.2
Cloning an NE
This function allows you to duplicate an NE with its configuration. This may be useful to create an NE
whose characteristics are very similar to another one.
The cloning operation is not allowed on the composite NEs.
To clone an NE, proceed as follows:
Select an NE on the current submap in the Topology Management window. The new NE will be placed
on the same submap as the cloned NE.
Use the menu path: Declarations Clone...
A dialog box like in figure below opens:
1353NM-E Rel. 7.4B

222/532
Operator Handbook
Topology Management
Figure 190. Example of a Clone Dialog Box

The title of the dialog box recalls the user label of the NE to be cloned.
You can modify only the same fields as in a Modification dialog box, but you must enter a new User Label.
Launching the Cloning
To trigger the cloning, click on the Apply push button.
The cloned NE appears in the NE: Global Inventory window.
Since neither the supervision area nor the EML domain can be changed, the new NE is always allocated
to the EML agent managing the cloned NE.
Launching the Migration
To trigger the migration, click on the Apply push button.
In the NE: Global Inventory window, the migrated NE disappears as basic NE and a new CNE appears.
The creation of the composite NE brings about the creation of a list of subNEs by default.
The list of the subNEs is available in a hierarchical way in the NE Global Inventory dialog box.
Closing the Dialog Box
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

223/532

PNM in Viewer Mode
When PNM runs in viewer mode, you can migrate an NE to a host NE by selecting them from the current
submap in the viewer window.
During the migration, the symbol of the currently selected NE is transferred to the newly created CNE submap. All the occurrences of this NE that could exist in other sub maps are removed.
Like the NE Creation dialog box presented at the end of paragraph 6.8.1, the Migrate to Host NE CNE
Creation dialog box in viewer mode contains an additional field named Comments.
1353NM-E Rel. 7.4B

224/532
Operator Handbook
Topology Management
6.10.3
Declaration of the NE Addresses
Once the NE has been created in PNM, you have to provide the OS with the address of the real NE that
is in the network.
This feature can also be used to change the NE address later on.
PNM can manage different types of NE addresses: OSI (Q3), RFC1006 (a special case of OSI address)
and free addresses such as TCPIP (SNMP) addresses. That is the reason why the address declaration
is separated from the NE creation and address input forms depend on the NE type.
Moreover some NE types, such as remote NEs, do not embed their own address, as they exchange their
management information with the OS through other NEs. Therefore no address capture is expected for
such NEs.
To set an NE address select an NE in the NE Global Inventory window, then use the menu path:
Declarations Set Addresses NE Address.
The dialog box that opens may be like one of the examples that are shown in the figures below.
In following Graphic User Interface (GUI), all text boxes in group "NE information" are read only. They are
filled by the interface and cannot be edited by user.
If the GUI is opened on a NE on which an address has already been set, then the GUI shows the address
of the NE in the appropriate panels (depending on address type) and with the correctly enabled fields
(depending on value of AFI field).
If the GUI is opened on a NE that has no address yet, GUI retrieves the format of NE address and, for
an OSI NE address, it's up to the user to decide the value of AFI for an OSI address. AFI determines which
other GUI elements in NSAP are enabled. In this case (NE with no address yet), OSI panel is always displayed with only:
The selector fields already filled.

The AFI field visible.
Note: For those N/A fields (e.g.: OrganizationID field in case of AFI=47), GUI still leaves both field label
and input area visible for an orderly layout, but they are disabled so in grey the input area is empty and
noteditable.
Field AFI (Authority and Format Identifier) prescribes the basic format layout for an OSI NE address. GUI
prevents users to give an illegal address by:
Disabling unnecessary input fields for certain AFI.
Any nonhexdigit character is rejected; the uppercase or lowercase form of hexadecimal digit characters "AF" doesn't bring difference.
The length of any nonfree field must conform to OSI rule exactly.
The length of free field must be an even number (because 2 hexadecimal digits form a "byte").
The length of free field is up to the user. Currently it is not practicable for GUI to validate it.
Supported values of AFI are 39, 47, 49, 54 and "free".
OSI addresses can be divided into two parts:
NSAP is a unique address in an OSI network that identifies the network service.
Selectors (TSel, SSel, and PSel) identify services of peer entities. For example, the TSel identifies
the service provided by the transport layer.
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

225/532
After NE creation 1353NM users configure the agent application address NSAP plus upper selectors
through a dedicated form. The NE address definition is mandatory before starting NE supervision.
The length of upper selectors are:
Transport Selector: 2 digits.

Session Selector: 2 digits.
Presentation Selector: 4 digits.
In OSI standard, NSAP consists of 40 digits (short address and RFC 1006 address form are the exception):
AFI: 2 BCD digits.

IDI: 4 digits.
Org. Id: 16 digits.
Area: 4 digits.
System Id: 12 digits.
NSAP Selector: 2 digits (1D for all, except 01 for OMSG).
While NSAP shall be unique in the DCN and it is assigned according to the designed addressing plan,
TSP selectors are always the same for a given family of NEs:
OMSN, MW, WDM: T = 00, S = 00, P = 0002.

ION/OMSG (full OSI and RFC1006): T = 31, S = 31, P = 31.
In case of short address form the NSAP address length can range from 8 to 20 bytes (that is 16 to 40 hex
digits). 1353SH 6.3 supports a dedicated form for editing the short address in a free format; with 1353 NM
7.0 the standard form is used and some fields can be partially populated or missing.
1353NM-E Rel. 7.4B

226/532
Operator Handbook
Topology Management
If AFI= "39" is selected, text boxes "IDI", "Organisation ID", "Area", "System ID", "NSAP Selector"
are enabled:
Figure 191. OSI address setting user interface (AFI= 39)

AFI= 39 (ISODCC): a Q3 NE address is composed of 40 digits:
AFI (2 digits) + IDI (4 digits) + Organization ID (16 digits) + Area Address (4 digits) + System ID (12 digits)
+ NSAP Selector (2 digits).
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

227/532
If AFI= "47" is selected, text boxes "IDI", "System ID", "NSAP Selector" and "Free" are enabled:
Figure 192. OSI address setting user interface (AFI=47)

AFI=47 (ISO 6523ICD): the length of Q3 NE address ranges from 16 digits to 40 digits:
AFI (2 digits) + IDI (4 digits) + free part (0 to 20 digits) + System ID (12 digits) + NSAP Selector (2 digits).
1353NM-E Rel. 7.4B

228/532
Operator Handbook
Topology Management
If AFI= "49" is selected, text boxes "System ID", "NSAP Selector" and "Free" are enabled:

AFI= 49 (Private), the length of Q3 NE address ranges from 16 digits to 40 digits:
AFI (2 digits) + free part (0 to 24 digits) + System ID (12 digits) + NSAP Selector (2 digits).
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

229/532
If AFI= "54" is selected (RFC1006), text boxes "NSAP Selector", "IP address", "Port" and "Protocol"
are enabled; "IDI" and "Organisation ID" are displayed but readonly with fixed values:

AFI= 54 (RFC 1006), the length of RFC 1006 NE address is 14 digits plus length of TCP/IP address (total
18 bytes):
AFI (2 digits) + IDI (4 digits) + Organization ID (6 digits) + NSAP Selector (2 digits) + IP address (12 BCD
digits) + Port number (5 BCD digits; default is 00102) + Protocol Identifier (5 BCD digits; TCP: 1; UDP:
2; default is 00001).
RFC 1006 address is a special case of standard OSI address. IP address information should be given
for it. The values of TSP selectors and all NSAP fields are predetermined, and given in readonly text
boxes just for information of users.
For OSI addresses, a preview of combined full address string is displayed in field "Preview". This field is
always visible and readonly. If an illegal address is given, an alarm is appended to tail of combined
address string.
1353NM-E Rel. 7.4B

230/532
Operator Handbook
Topology Management
If AFI= "free" is selected, only text box "Free" is enabled.
The GUI for setting SNMP NE address is as follows:
Figure 195. OSI address setting user interface (AFI= free)

AFI= "free", the length of Q3 NE address ranges from 0 digit to 40 digits: free part (0 to 40 digits)
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

231/532
TCPIP address setting.
For NE supporting TCPIP address, select the IP address tab.

TCPIP address and port number (usually it is 161) should be given for a SNMP NE address.
The GUI for setting SNMP NE address is as follows:
Figure 196. IP address setting user interface
Validating the NE Address

To validate the modifications in the dialog box, click on the Set push button.
1353NM-E Rel. 7.4B

232/532
Operator Handbook
Topology Management
6.10.4 Changing an OS Address

NEs exchanging their management information directly with the OS need addressing information in order
to be able to communicate with the OS across the network. Such an OS address is conveyed to the NE
by the EML agent during the creation process.
Actually certain types of NEs have two OS addresses at their disposal: the main OS address and a spare
OS address, enabling them to switch from one OS to another. This is intended to support, for instance,
OS resilience or OS migration.
At the beginning, both addresses conveyed to the NE are identical, and they are known by the EML agent
by configuration. The given address relates to the workstation which hosts the EML agent.
Once the NE is created, each OS address may be individually changed (for NEs which support it).
To change an OS address, proceed as follows:
Select an NE whose supervision state is Supervised on the Topology Management map.
Use the menu path:
Declarations Set Addresses OS Address.
Figure 197. OS Address Dialog Box
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

233/532
The title of the dialog box recalls the user label of the NE whose OS addresses are to be changed.
The first time an OS Address dialog box opens, the OS Main Address and OS Spare Address (known by
configuration) are displayed in the corresponding fields.
You can change the main OS presentation (PSAP) address in accordance with the ISO definition (AFI,
IDI, Organization Id., Area, System Id. and Sel. fields).
You can also change the optional spare OS PSAP address by using the same format.
NOTE: The OS main address can only be changed if the NE is supervised (i.e. its supervision state is
Supervised). However the OS Address dialog box can always be displayed whatever the supervision state
is and you can change the OS spare address in all cases.
Validating the OS Addresses

To validate the modifications in the dialog box, click on the Apply push button.
1353NM-E Rel. 7.4B

234/532
Operator Handbook
Topology Management
6.11 External Text

The external text is a piece of information provided by the EML agent.
When PNM is configured to display external texts, this attribute appears in the following dialog boxes:
Current Status for an NE.
NE Inventory Filter (Static Attributes panel).
NE Inventory Selection Filter (Static Attributes panel).
Current Status Dialog Box
Next figure shows how the external text attribute appears in a Current Status dialog box for an NE:
Figure 198. Current Status Dialog Box for NE with External Text Enabled
Operator Handbook
Topology Management
1353NM-E Rel. 7.4B

235/532
Filter Dialog Box

The figure below shows how the external text attribute appears in a filter dialog box.
Figure 199. Filter Dialog Box (Static Attributes Panel) External Text Enabled
The external text attribute also appears in the following dialog boxes:
NE Map Inventory Filter (Static Attributes panel).
NE Map Inventory Selection Filter (Static Attributes panel).
NE Map Complement Inventory Filter (Static Attributes panel).
NE Map Complement Inventory Selection Filter (Static Attributes panel).
NE Map Filter (Static Attributes panel).
The External Text field appears in those dialog boxes like in the example above.
1353NM-E Rel. 7.4B

236/532
Operator Handbook
Topology Management
7 Managing a Map
7.1 Introduction
A map is an abstract entity, that represents a collection of symbols interconnected to represent a network. A map
contains a set of created objects. Some of these objects correspond to entities that can be supervised (Network
Elements) and others are only graphical and are not supervised (network nodes, Local Area Networks (LANs)
sites, regions, connections between the graphical symbols). Maps are built by authorized operators during the
construction phase. A given operator works from a subset of maps, according to his access rights.
In order to allow authorized operators to make changes to the supervised network in a flexible and reversible way,
maps can be created, edited, saved, opened and deleted without modifying the map used by other operators.
Once a construction map is an accurate image of the supervised network, authorized operators can distribute it
to operators in relation with access rights. It is up to the client operator to decide to use the new map.
Two types of maps are available:
A distributed map is the original map created by the administrator or constructor from which a local
map is generated for the user which has the proper access rights to use it. The administrator and
constructor always acts on the original map, each deletion or modification are definitive.
A local map is an operator own version of the distributed map. An operator always acts on its local
map and modifies it as necessary without affecting the original one.
The building blocks of Maps are called submaps.
A submap is a collection of related symbols displayed in a single graphical window. Submaps are organized in a hierarchical way. Each submap may contain symbols that represent other submaps. Navigation
through the different submaps that make up the Map is done by doubleclicking on symbols. This opens
the associated submap in a window on the terminal.
Symbols that generate other submaps are called Parent symbols and the submaps they create are called
Child submaps. The first submap created is called the Root submap. It contains the parent symbols from
which the submap hierarchy will be established.
When a submap is opened, the name of the Root submap is written in the bottom left corner of the submap.
The name of the submap is given in the bottom right corner of the submap. In Figure 200. the submap
is the Root submap.
Depending on the access rights, management operations on submaps may or may not be undertaken.
An Object is a particular entity or resource in a network system environment. In the Network Topology
views that are dealt with in this manual, objects are either Sites, NEs or Connections between these different entities.
A symbol on a submap is the representation of an Object described in the OS MIB.
Two types of symbols can be distinguished:
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

237/532
Managed symbols: represent a supervised entity managed by the system. They generally represent NEs. In this case the network characteristics (name, network address...) are defined in the OS
MIB.
Graphical symbols: not managed by the system but are simply a graphical representation of an
object. They generally represent geographical entities such as connections or sites.
N.B.
There may be multiple representations (symbols) in a map of a given managed object. However the
object is uniquely defined in the OS MIB. This means that no matter how many representations (symbols) of an entity appear in a map, there is only one description of the object in the OS MIB.
7.2 Create the map

SCOPE
The aim of this chapter is to introduce the steps necessary to define the network topology. This is done
step by step, so that the most detailed and correct description of the network construction is given.
As defined in the previous chapter, geographical entities represent sites or connections and are not managed by the system. Therefore, this chapter describes the creation of the site and the connection symbols.
It may be necessary to create a new Map in order to create a new network or to represent differently an
existing network without modifying the original network layout.
SEQUENCE
a)
To create a new Map select the pulldown menu

File New Map.
Figure 200. File: New Map

1353NM-E Rel. 7.4B
238/532
Operator Handbook
Managing a Map
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

239/532
b)
A question box asks if you want to save the current map before opening the new one.
Figure 201. Question: Save current map
7.2.1 Map Background and Layout
Figure 202. View: View Parameters pulldown and popup menu
1353NM-E Rel. 7.4B

240/532
Operator Handbook
Managing a Map
Figure 203. Background selection
Figure 204. Layout selection
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

241/532
Figure 205. Root map display with background
1353NM-E Rel. 7.4B

242/532
Operator Handbook
Managing a Map
7.2.2 Creating a child submap

SCOPE
The scope of this procedure is to create a Child view
SEQUENCE
a)
From the Root map select:

Edit Create Child View.
Figure 206. Edit: Create Child View

b)
From the Child View icon selection dialog box (see below figure) select the icon and click on Apply
button.
Figure 207. Child View icon selection
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

243/532
c)
The icon of the child view is displayed on the map. Click on Close button of the icon selection box
to close the box. (See below figure).
Figure 208. Child View icon selection box: Close button
1353NM-E Rel. 7.4B

244/532
Operator Handbook
Managing a Map
7.3 Constructing the Manageable Entities

The previous chapter dealt with general Map and Submap construction concerning the geographical entities (sites and connections) and the navigation through the different submaps.
This chapter describes the steps involved in the addition of manageable entities to submaps.
The operations that can be undertaken are:
Creating a NE.
MIB cloning.
Adding or removing a NE symbol.
Declaring or changing the NE address.
N.B.
The NE to create has been correctly installed with the right software version.
N.B.
The EMLIM which will manage the NE to create has been correctly installed in 1353NM.
7.3.1 Adding NEs to the Topological representation

There are two methods for creating a NE on a submap:
either by providing all the necessary characteristics of the NE to be created (Type and release,
unique userfriendly name and other optional parameters).
or by copying the OS MIB configuration from an existing NE, providing only (at least) the user
friendly name (user label) of the new NE, for the NEs which support this operation.
The second method is called MIB cloning.

Moreover, certain types of NE requires a particular creation procedure, as they have not their selfsufficiency (not standalone). They are called remote NEs.
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

245/532
7.3.1.1 Creating NEs

The creation of a NE enables you to create a graphical NE symbol on a submap and at the same time create
its corresponding configuration in the OS MIB. To create a NE of a specified type and release, the following
information is required:
a unique user friendly name (User Label).
Other information (such as EML domain, supervision area) may be provided, but is not mandatory.
SEQUENCE
a)
To create a NE, place yourself on the submap on which the NE must be created.
Select thepull down menu as shown in the figure below:
Declarations Create NE
Figure 209. Declarations: Create: NE
1353NM-E Rel. 7.4B

246/532
Operator Handbook
Managing a Map
The following dialogue box opens allowing to enter the NEs characteristics:
Figure 210. NE Creation

b)
In the above dialogue box, the Family criterion provides a way to filter the NE types by categories.
c)
Select a family of NE types from the list. The selected family of NEs is highlighted and the
NE Type list is updated to show all supported NEs in that family.
d)
Select a NE type from the list. The NE type is highlighted to show it has been selected.
At the same time the available releases concerning the selected NE type are listed in the
top right hand corner of the dialogue box.
e)
Select the required NE Release.
f)
Enter the NE user label (friendly name) and the location name in their respectively entry
boxes. In the NM system the maximum character number for the location name has been
fixed to 32. This maximum length has been provided for both Q3 NEs. The existing NEs
with longer location name will be taken over and accepted by the system but if the user
will try to modify it the new one will be accepted if shorter than 32.
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

247/532
The User Label and Location Name are mandatory. The maximum character numbers for the User Label"
is 32.
The maximum character numbers, for User Label" of 1540PO, when the PO is connected to
a Network Terminal (NT), is: max." - 7, where the default max." installation value is 32.
The Location Name field allows to specify the location of the NE being created.
The remaining fields Supervision Area, EML Domain and Comments) are not mandatory but a wrong
Supervision Area" assignment can create a not reachable NE:
The Supervision Area is associated to different management interface (OSI protocol stack) provided by
the NM. Specifying the Supervision Area label forces the NE to be allocated to an EML domain belonging
to this supervision area. Then the Supervision Area" marks the lan type connected to the NE.
Specifying the EML Domain forces the assignment of the NE to that EML domain, provided that it supports
the required NE type and release.
If none of these two attributes are provided, the NE will be allocated to the least loaded EML domain
among all of those supporting the required NE type and release.
If both attributes are provided, they must be compatible. In case of conflict (EML domain not in specified supervision area), an error message will be displayed.
Specifying the Access Control Domain forces the assignment of the NE to that control domain. The
possible control domains are defined in the user profile. If this security is not defined in the user profile, the Security field will be Disabled and the Unknown is specified in the Access Control Domain
list.
N.B.
The Access Control Domain feature is used to limit the number of possible operations on a specific NE. But it can also limit the operations allowed to an operator.
For example, the NE creation can be forbidden to a specific user.
The Comments field allows the operator to enter some comments about the NE being created.
Confirm or cancel the creation operation using the OK or Close push buttons at the bottom of the dialogue box.
The processing of the request is indicated by the cursor changing to a busy (clock) cursor and no further
operation can be performed on the NE until the operation is completed.
The Close push button enables to close the dialogue box.
If you close the dialogue box during the creation process, the NE graphical representation on the submap will
be removed but the creation process will not be cancelled. However, the operator will have to perform a Global
NE Inventory) to see the NE graphical representation on the submap.
d)
After this "Create NE" operation, the NE graphical representation appears on the submap and the
NE characteristics (except for the NE address) are defined in the OS MIB. A NE object is thus created
in the OS MIB.
The creation operation cause the NE supervision state pass to Declared state.
e)
To access the Equipment view, select the NE by clicking on it with the "Select" mouse button. Open
the Supervision pull down menu and choose the Show Equipment option from this menu, as
explained in the Getting Started manual. Note that a declared NE Equipment View", managed by
Q3, can be opened but nothing will be visualized.
In this view, the SUP icon, representing the supervision state of the NE is in the Declared colour.
1353NM-E Rel. 7.4B

248/532
Operator Handbook
Managing a Map
N.B.
If the name given to the NE during this "Create NE" operation is the name of an existing NE
then the system will alert you of this fact by opening a dialogue box.
7.3.2 Population from Inventory

SEQUENCE
a)
From the PNM window select:

Tools NE Inventory Global.
Figure 211. Tools: NE Inventory: Global
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

249/532
b)
From the NE Inventory window select the NE to create and issue the pulldown menu Populate.
Figure 212. Inventory: Population
1353NM-E Rel. 7.4B

250/532
Operator Handbook
Managing a Map
c)
A dialog box is presented, allowing the user to choose the population options:
Figure 213. Submap topology selection
Population Input. Contains the options:
Selected NEs. Only the selected NEs will be placed in the maps.
All NEs. All NEs present in the Inventory list will be placed in the maps.
Population Mode.
OS Topology. The system creates a different submap per each installed EMLIM and places
each NE into its own submap.
Network Topology. The system creates a different submap per each site and places each NE
into its own submap.
Submap Topology. The user selects on the popup sub window (see above figure) the subnetwork where the NE(s) will be placed.
Population Options.
If this option is not activated, all the NEs are treated on the basis defined in the Population Mode area.
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

251/532
No duplication. when activated, this option prevents the NE symbols from being duplicated in
the same submap during population operations.
Hierarchical. when this option is activated, the remote NEs, remote units and subNEs are
managed with the following rule: the remote NEs are located on the same submap as their master NE, the remote units are located in a submap associated to their master NE and the sub
NEs are located in a submap associated to their composite NE.
Figure 214. Global Inventory population dialog box

For more detailed information refer to Section PNM.
1353NM-E Rel. 7.4B

252/532
Operator Handbook
Managing a Map
An example of root map with one submap is displayed in the figure which follows:
Figure 215. Root map and submap
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

253/532
Figure 216. Submap view
1353NM-E Rel. 7.4B

254/532
Operator Handbook
Managing a Map
7.4 NE Address
SCOPE
In order to communicate with a NE, PNM requires the network address of the NE to be configured in the
OS MIB.
Since various addressing mechanisms should be supported, the address declaration is separated from
the NE creation, and address input forms depend on the type of NE.
The NE address management could be handled out of the system in particular cases (for instance, the
EML agent may take care of it).
N.B.
The currently supported NE address formats are IP addressing, Q3 addressing and Q2

addressing.
This operation is only allowed if the NE supervision state is Declared.

CONDITIONS
The local NE address on the equipment must be previously set up via the Craft Terminal.
SEQUENCE
To supply the NE address of an equipment, place yourself on the submap on which the NE is located.
Select the NE for which you want to declare the address.
Select the NE Address... option from the Declarations: Set Addresses pull down menu as shown in the
Figure 217. below:
Figure 217. Declarations: Set Addresses: NE Address

According to the NE type, one of the following dialogue boxes opens allowing you to enter some addressing information (Refer to 6.10.3 for details).
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

255/532
7.5 Supervision
7.5.1 NE management states
7.5.1.1 Introduction
The elementary building blocks of any telecommunication network are the Network Elements (NEs). This
section presents the different management states of an NE from the OS point of view. There are 5 management states and one Alarm status:
Supervision state: gives information relative to the supervision state of the NE. There are 4 states.
Declared: the NE is not being supervised (e.g. it has just been declared to the OS).
Supervised: the NE is under supervision.
Activating: the NE is being brought under supervision and no management tasks can be performed on it.
Deactivating: the supervision process on the NE is being stopped and no management tasks
can be performed on it.
Only an NE in Supervised state can be fully managed by the USM application. Please note the
software downloading operations can be also applied to a Declared NE.
MIB Alignment state: occurs during the NE Supervision state. There are 2 states.
N.B.
Misaligned: this is a transitory state before being able to visualize the NE configuration.
Aligned: the system becomes aligned when all the operations for synchronizing the NM with
the NE are fully completed. For the Q3 / SNMP NEs the synchronization procedure involves
the alarms, the PM and the NE configuration.
The alignment state goes automatically to misaligned state when the operational state
goes to disabled.
Local access state:

relates to the ability for the NE to be managed from the local craft terminal CT. There are 3 states.
Granted: the NE may be managed by the local craft terminal. In this case, the icon is displayed
green on the CT and blue on the OS.
Denied: the NE can not be managed by the local craft terminal. In this case, the icon is displayed blue on the CT and green on the OS.
Requested: the local manager (CT) has requested update permission from the OS and is waiting for a reply (granted or denied) from the remote manager.
This parameter is set from the OS to Granted or Denied. The CT can only request local access or
return access to the OS.
When no OS is logged in, a CT gets a requested local access after a while. When an OS is logged
in, a CT does not get local access. In this case, it is necessary to call the OS operator to set the local
access state to Granted.
If the Local access state is Granted, some USM operations can be disabled (greyed).
As long as local access is granted for CT, the access for NM is denied.
1353NM-E Rel. 7.4B

256/532
Operator Handbook
Managing a Map
Craft Terminal Connected state: The Craft Terminal Connected state on the NMDXC shows if a
CT is logged in on the NE. This means, a Craft Terminal has started supervision on the selected NE
in the PNM view.
CT not connected (green): no CT supervises the NE.
CT connected (blue): CT supervises the NE.
Operational state: relates to the ability for the NE and the OS to communicate together. There are
2 states:
Disabled: the communication link between the OS and the NE is interrupted.

Enabled: the NE is either in the activating, deactivating or supervised supervision state and
communication between the NE and OS is possible.
NML Assignment state: indicates whether an NE is used for Network Management purposes.
There are 3 states:
Free: the NE is not assigned to Network management tasks. Element manager level (1353 NM
can be selected in the manager list).
Observed: Network management tasks may be applied to the NE.
Assigned: the NE is assigned to Network management tasks (superior network manager
selected in the manager list, e.g. 1354 RM). This causes a reduced access on the 1353 NM.
The NML assignment state can be displayed with the Set Manager List dialog.
To supervise the NE, the NMOS establishes a permanent association with the NE.
Any disruption in the communication link between the OS and the NE results in an update of the management states when the OS has detected the communication failure. More details are given on Q3 / QB3
NE Management relevant sections.
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

257/532
7.5.1.2 Consulting the different management states

To understand the way in which the different management states are related, the following representation
may be helpful. The NE states are as follows:
NE_STATE [Operational state, Access state, Supervision state, Alignment state, NML Assignment state]
In the following diagram, depending on the operations undertaken, the management states change. If a
particular management state can take any value, it is represented by the "-" sign in the state representation. For example, at the launching of the 1353NM, the representation is NE_STATE [-, -, -, -, -].
Figure 218. is an example of how the management states can evolve following different operations.
Declare NE
NE_STATE[disabled, granted, declared, -, -]

Start Supervision
Supervision
fail
NE_STATE[-, -, activating, -, -]
Stop Supervision
successful
Supervision
successful
NE_STATE[enabled, denied, supervised, aligned, -]
Compare
MIBs.
Allow
Local_ access
Stop Supervision
NE_STATE[-, -, deactivating, -, free/observed]
NE_STATE[enabled, Granted, supervised, aligned, -]

NE_STATE[enabled, denied, supervised, misaligned, free/observed ]
Download
NE_STATE[enabled, denied, supervised, aligned, - ]
Stop Supervision
Figure 218. An example of the evolution of the NE management states.

The Network Topology views enable you to get access to the current NE status in which the different NE
management states are described.
The Network Topology views enable you to get the status information on:
A Site: in this case all the NE statuses are shown.

One or more NEs: in which case only that (or those) particular NEs management states are shown.
One or more Sites and one or more NEs: this is the most general case.
The above cases are identical in the operations that are undertaken but differ only in the number and type
of the symbols selected. In this section only the most general case is treated.
1353NM-E Rel. 7.4B

258/532
Operator Handbook
Managing a Map
In a Network Topology view, select the sites and the NEs of which you require the NE management states.
Select the Show Statuses... option from the Operations pull down menu as shown in the following figure:
Figure 219. Operations: Show Statuses
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

259/532
The NE Status dialogue boxes of all the NEs concerned by the operation are opened. An example of this
dialogue box is shown in the following figure:
Figure 220. Current status dialog box

The title of the dialogue box indicates the NE that is concerned.
N.B.
The relationships between the NE statuses and the severity alarm are described in the chapter
2.6.
7.5.1.3 Resynchronize NE States in the Network Topology view

An automatic refresh of the Network Topology view is performed regularly. However, to make sure that the NE
states displayed by the Network Topology view are really up to date, it is possible to perform a manual refresh.
From the Network Topology view, select the Resynchronize option from the Operations pull down menu.
1353NM-E Rel. 7.4B

260/532
Operator Handbook
Managing a Map
7.6 Supervising NEs

Supervising NEs is an essential aspect of network management! It enables the gathering of information
concerning the behaviour of the NE with respect to its functional state.
The creation of an NE symbol and the declaration of its characteristics in the OS MIB put the supervision
state of the NE in the Declared state.
You can start the supervision of:
N.B.
A Site: in this case, the operation is performed on all NEs in the site.
One or more NEs: in this case, only a set of NEs is concerned by the operation.
One or more sites and NEs: this is the most general case.
The NE addresses must have been declared before starting supervision of those NEs. Otherwise error messages will be displayed.
7.6.1 Starting supervision of NEs

SEQUENCE
a)
Select the sites and the NEs to supervise in the Network Topology views. They are highlighted.
b)
Select the pull down menu:

Operations Supervision.
The operator can then select supervision either of the options (Align Up..., Align down... or
Audit...) for starting the NE Supervision.
Figure 221. NE: Operations: Supervision: Align Up
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

261/532
Figure 222. Align Up Supervision

The following dialogue box opens from which the operator confirms or cancels the "Start Supervision"
operation using the Ok or Close push buttons.
In this dialogue box, the list of NEs that will undergo the "Start Supervision" operation is given.
To launch the "Start Supervision" operation, use the Apply push button.
Messages concerning the supervision operation appear next to the list of NEs.
N.B.
Selecting the Close push button will exit the dialogue box without launching the supervision
operation.
An Information dialogue box opens indicating that the "Start Supervision" operation is terminated. Click
on the Ok push button of the Information dialogue box to continue.
When the "Start Supervision" operation is over, click on the Close push button to close the dialogue box.
Once the Supervised state is established, an association between the NEs and the OS is created.
This association implies that the OS constantly supervises the NE. This association is released, by the
OS, only when the supervision is stopped. NE or OS failure automatically cancels the association which
is automatically reestablished by the OS once the NE becomes connectable once again (in the event
of NE failure or network failure) or when the OS is restarted (in the event of OS failure).
On a NE which has been created, the first time the command Align up is required. Figure which follows
shows an example of Align Up Supervision end.
1353NM-E Rel. 7.4B

262/532
Operator Handbook
Managing a Map
Figure 223. Align Up Supervision end
7.6.2 Stopping NE supervision

As for the "Start Supervision" operation, the "Stop Supervision" operation can be done from the Network
Topology views: They allow you to stop the supervision of:
A Site: in this case, the operation is performed on all NEs in the site.
One or more NEs: in this case, only a set of NEs is concerned by the operation.
One or more sites and NEs: this is the most general case.
As for the "Start Supervision" operation, the most general case is explained in this section.
From the Network Topology view, select the NEs of which you require to stop the supervision. Select the
Stop option from the Operations: Supervision pull down menu.
The dialogue box that opens is similar to the one displayed for the start supervision operation. This dialogue box gives the list of NEs that will be involved in the "Stop Supervision" operation.
Selecting the Apply push button launches the "Stop Supervision" operation. Messages appear in the dialogue box next to the list of NEs indicating the progress of the "Stop Supervision" operation.
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

263/532
N.B.
Pay attention that the Stop Supervision" will be suspended during the data PM collection. It
may be necessary to complete the PM collection the following waiting time:
10 minutes for OMSN and 5 minutes for OMSG, during the even day hours.
40 minutes for OMSN and 120 minutes for OMSG at the midnight.
7.6.2.1 Different NE subversion of the same NE type (only applicable to W/OMSN)

Since a NE MIB might be not compatible with next version of the same NE Type & Release, subversion
indication (a letter "A", "B" and so on) has been introduced to automatically distinguish the version. The
reason of different subversions is due to features enhancement or bug fixing. Then the solution is an
additional software package for SDH NE object that contains the value of the NE subversion.
In order to manage this subversion of the same NE Type & Release, we have to read this new package
at startup time. USM will subscribe for AVC (Attribute Value Change) of the package of NE subversion.
In this way it is possible to know when the subversion of NE changes.
The following situations can be met:
NE declared and supervised:
When the operator starts the USM, it will retrieve the package from EMLIM which knows the correct sub
version, and then uses it. In additional the USM will subscribe for AVC on NE subversion.
NE declared and not supervised:
In this case the subversion is unknown, so the EMLIM sends back to the USM, the value "undefined"
for the package subversion and for the version the latest acquired.
USM already opened:
If a "Start Supervision" occurred after USM started and the version of NE is different from previous one,
then the AVC of the new version will be notified to the USM. In this case the USM will show the operator
a message box indicating the equipment change and the USM will be closed.
1353NM-E Rel. 7.4B

264/532
Operator Handbook
Managing a Map
7.6.3 Abort Supervision

In addition to the usual Stop Supervision" operation the user can select the Abort Supervision" command. The Stop Supervision" operation allows the operator to perform a smooth closing of the management session with the relevant NE. Therefore, before closing the management session, the NM retrieves
the collected PM data that have not been jet retrieved. If the request for Stop Supervision" is issued in
some critical periods, immediately after every hours (e.g. at 8, 10, 12, etc.) or immediately after midnight,
then the NM waits for the collection of the last period, which can last a while.
The Abort Supervision" operation allows the operator to immediately close the management session
without performing the collection of latest historical PM data. Therefore, this operation is normally faster,
and in some cases much faster, than the normal Stop supervision" operation.
A warning message is displayed and a confirmation is required before the abort supervision command
is executed.
Figure 224. Abort supervision
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

265/532
7.6.4 Black icon with question point
Figure 225. Black icon with question point

PROBLEM
A new 1353NM software package has been installed which does not manage the versions actually resident on the NE.
CORRECTIVE ACTION
Execute an NE sw upgrade via SW download commands.
1353NM-E Rel. 7.4B

266/532
Operator Handbook
Managing a Map
7.7 OS Address for an Equipment

NEs exchanging their management information directly with the OS need addressing information in order
to be able to communicate with the OS across the network.
Actually certain types of NEs have two OS addresses at their disposal: the main OS address and a spare
OS address, thus enabling them to switch from one OS to another. This is intended to support, for
instance, OS resilience or OS migration.
At the beginning, both addresses conveyed to the NE are identical, and they are known by the EML agent
by configuration. The given address relates on the workstation which hosts the EML agent.
Only the spare OS address may be individually changed (for NEs which support it).
N.B.
The OS address of an equipment can only be changed if the NE is supervised. Nevertheless

it can always be displayed.
To change the NE address for an equipment, place yourself on the submap on which the NE is located.
Select the NE for which you want to change the address. It is then highlighted.
7.7.1 OS Address
SEQUENCE
a)
Select Declarations: Set Addresses: OS Address.
Figure 226. Displaying and changing the OS address for an NE.

b)
The OS Address dialog box is displayed.
The title of the dialogue box displays the name of the NE for which the OS addresses are to be changed.
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

267/532
Figure 227. OS Address dialog box

The first time the OS input address dialogue box is opened, the default main and spare OS addresses
(known by configuration) are displayed in the corresponding entry boxes.
c)
You can change the main OS NSAP presentation address, in accordance with the ISO definition
(AFI, ADI, Organization ID, Area, System ID and Sel entry boxes).
You can also change the optional spare OS NSAP presentation address, using the same format.
The SEL" field shall always be put to 1d"
d)
Confirm or cancel the changes to the OS addresses using the OK or Close push buttons at the bottom
of the dialogue box.
1353NM-E Rel. 7.4B

268/532
Operator Handbook
Managing a Map
7.8 Add Connection

The following figures show an example of creation of connection in the NM map.
Notice that connections are only graphical objects, created only to ease the user's tasks.
A detailed description of the Connection management commands can be found in Section Topology Management.
Figure 228. Operations: Add Connection
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

269/532
Figure 229. Add Connection dialog box
Figure 230. Icon selection
Figure 231. Add Connection creation: Apply button
1353NM-E Rel. 7.4B

270/532
Operator Handbook
Managing a Map
Figure 232. The connection is drawn on the map
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

271/532
7.9 Diagnose
All the options reported on Figure 233. are described in the Q3 NE Management manual.
Figure 233. Diagnose menu options
7.9.1 Remote Inventory on PNM

7.9.1.1 Remote Inventory Visualization
The remote inventory are factory information identifying the boards, the final test and eventually other
data. The data are written inside each boards and the operator can only collect the data and read them.
Select a NE in the map and then the Remote Inventory Display option to display the RI data. if the NE is
in supervision state the user with the Upload Remote Inventory option can update the RI data loading the
last available one.
Select a NE and then Operations: Upload Remote Inventory option as in the example of Figure 234.
1353NM-E Rel. 7.4B

272/532
Operator Handbook
Managing a Map
Figure 234. Upload Remote Inventory option

After the OK" confirmation, wait the Success" indication as shown in the example of Figure 235.
Figure 235. Remote Inventory uploading example

Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

273/532
Now the Remote Inventory data, for the selected NE, can be shown with the Display Remote Inventory
command.
Figure 236. Show Remote Inventory menu

Select Operations: Display Remote Inventory to open Figure 237.
1353NM-E Rel. 7.4B

274/532
Operator Handbook
Managing a Map
Figure 237. Show Remote Inventory window example

The Remote Inventory window starts with the beginning data and time of the RI" and the NE name indication. Then the following info are listed:
USER LABEL:
Gives the information related to the NE type and the rack, subrack and slot board indications.
The list is ordered starting from the first rack on the left, the first subrack on the top and the
first board on the left.
LOCATION NAME (if available):
Specifies only the slot where the board is plugged in. The rack and subrack indications could
be fixed.
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

275/532
ELEMENT IDENTIFICATION:
ALCATEL Company.
It indicates the Company's (Alcatel's branch) which designs the unit.
Refer to Alcatel for the abbreviation meaning (four characters).
Unit Type.
Specifies type of board, e.g. Empty Slot, AGG16....
Unit Part Number.

It indicates Alcatel or Factory product Part No. The number indicated is that printed on the labels
or on the units front plates.
Software Part Number.

It indicates the id. of the unit resident software
CLEI Code.
It indicates the CLEI code according to Bellcore specs. TRISD325
MANUFACTURING INFORMATION:
Manufacturing plant.
It indicates the Company's manufacturing plant id. within the company, producing the unit.
Refer to Alcatel for the abbreviation's meaning.
Serial Number.
It indicates the product serial number as specified by the NR130Norm.
Date identifier and Date.

Date identifier indicates the meaning of the date that follows.
It is a twodigit code supplying the following information:
00
01
02
03
04
date of construction at the time of final testing.

production order data.
construction date of the unit lot.
date product has been forwarded to customer.
customer order date.
Date (YYMMDD).
The identification of the date depends on the indications stated in the previous field. When only
the year is displayed, the format must be "YY- - - - ".
OPERATOR INVENTORY DATA (if available):
Operator Data.
It indicates customer's data (name, site...)
Free For System Use.

This is reserved for the registration of modifications at the site. Each modification is identified
by a number. Two numbers can be displayed at a time. After more than two modifications, the
oldest entry is deleted.
1353NM-E Rel. 7.4B

276/532
Operator Handbook
Managing a Map
7.9.1.2 Remote Inventory Wizard

The RI wizard allows to execute a RI uploading operation on multiple selected NEs, to show the RI log
and to display all the RI windows of the chosen NEs.
The RI wizard is an application program designed for Q3 NE protocol interfaces. To open the RI wizard,
in the PNM management window, select option:
Operations Remote Inventory Wizard .
The SEL" and un SEL" buttons, on the left side, display the selected NE list" and not selected NE list"
on the right side of the wizard window. The user can visualize all the available (selected and not selected
NEs) NEs enabling the SEL" and unSEL" buttons as shown in Figure 238. In the right side field there
is the SEL" column with a button which allows to select or not select any NEs. Clicking on it, its colour
change from green to red or vice versa. The highlighted NEs with the green colour are the Selected" ones,
while those with the red colour are the Not Selected" ones. Clicking on the scrolling arrows / bar the user
can pass trough all the selected / not selected NEs and modifies their (selected / not selected) status.
When the selected / not selected NE list has been completed, the user can activate the required operation
on the Selected NE list:
Show Log and Display RI = both disabled

The RI uploading, of any NE belonging to the Selected NE list, is performed but there is no indication
about the RI uploading: which are the NEs successfully uploaded and which are not.
Show Log= enabled and Display RI = disabled

The RI uploading, of any NE belonging to the Selected NE list, is performed. At the end a file log will
be generated which informs the operator about the RI uploading situation.
Show Log= disabled and Display RI = enabled

The RI uploading, of any NE belonging to the Selected NE list, is performed. At the end the RI windows of the successful uploading operation will be opened.
Show Log and Display RI = both enabled.

The RI uploading, of any NE belonging to the Selected NE list, is performed. At the end a file log will
be generated which informs the operator about the RI uploading situation and the RI windows of all
the successful uploading operations will be opened.
In any case, when the Display RI" option is disabled, to open the RI windows, in PNM windows, select
the NE and click on "Show Remote Inventory" option (see Figure 236.).
The selected / not selected NE list can be filtered through the NE Family", the NE Type" and the User
Label" entries.
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

277/532
Figure 238. Wizard dialog box

Depending on the configured NEs in the NMOS system, clicking on the NE family" button, one of the
present family can be selected:
All
ADM
SNMP
WDM
Others
If the selected NE Type" does not belong to the NE Family the NE type indication is modified to all". If
for the same NE type there are many NEs the user can edit the User Label" to drop the required NEs.
The filtering is applied clicking on the filter button.
1353NM-E Rel. 7.4B

278/532
Operator Handbook
Managing a Map
Different operations can be performed clicking on the four buttons in the right bottom field:
push on this button to start the Wizard command on the selected / not selected NE list. The wizard
log window and / or the RI windows (as in Figure 237.) will be opened depending on the status
previously selected (Show Log / Display RI).
push on this button to save the selected / not selected NE list.
push on this button to come back to the last old saved selected / not selected NE list.
push on this button to save the selected / not selected NE list and to exit from the RI wizard application.
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

279/532
7.9.1.3 Remote Inventory Search

With the remote inventory search the operator can search a text, in the remote inventory files, and then
visualize the remote inventory of the wished NE through the NE USM navigation. Click on the Search"
button of the Wizard dialog box to open Figure 239.
Figure 239. Remote Inventory Search dialog box

Two different text search can be performed:
Editing the text in the Text Search" entry box.
Selecting the Family Type" check button, the red bar to open the pull down menu and the family
type component to enter in the text search. (as shown in Figure 239.).
The reset" button can be used to cancel the entry text. The search operation starts clicking on the
Search" button
1353NM-E Rel. 7.4B
280/532
Operator Handbook
Managing a Map
The Search Result" is listed, after a waiting time, at the bottom field. This field is divided into three parts:
Network Element Name = NE name where the text has been found.
Number= number of times for which the test has been found.
Search= processed text.
The last row at the bottom field contains the Total Number" = all times summary.
Pointing the mouse on a command, a tooltip, showing the command meaning, is displayed.
With a double click, on the Network Element Name" of the search result, the user can navigate on the
NE USM. With the NE USM remote inventory commands any remote inventory board details can be easily
visualized.
Click on X" button to exit and leave the application or on help" button to access to help on line facility.
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

281/532
7.9.2 Abnormal Condition (AC) Viewer

The Abnormal Condition (AC) is the status of the NE that informs about the presence of special conditions,
forced by the operator via management commands, which prevent the NE from behaving normally
according to its default configuration. The AC condition status in Q3 and SNMP supervised NEs is displayed on both the GUI (USM) of the NE itself and on the Topology Management application as shown
in Figure 45., but the operator commands generating the AC status are located on the USM only.
N.B.
The submap with an NE in AC status does not display the AC status, that is the AC status,
as all other statuses, is not inherited by the submap including the NE in AC status.
Figure 240. AC Abnormal Condition Viewer menu

General AC for W/OMSN or specific Q3 NE AC conditions (i.e. AC Radio condition on LHR) are described
in the proper NECT Operators Handbook. The SNMP NE AC events are described in its own Operators
Manuals. Each operator acting on the NM system can open his own instance of AC Viewer application.
SEQUENCE
g)
On Topology Management map deselect all NEs to enable the AC Viewer application
and then click on:
Tools Diagnose AC Viewer
to open Figure 46. The AC Viewer window lists all the Q3 and SNMP NEs characterized
by the AC status. The NE list is automatically updated on configured interval time. The
chosen refresh time is shown at the bottom of the AC Viewer window.
h)
The operator can force manually the updating of NE list, without having to wait for the
period of time, clicking on the Refresh button as shown in Figure 47.
1353NM-E Rel. 7.4B

282/532
Operator Handbook
Managing a Map
Figure 241. AC Viewer Window
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

283/532
Figure 242. Manual Refresh Command

If the AC Viewer has been iconized and the AC NE list, at the refresh time, has been modified, the AC
Viewer icon colour changes from blue to red to highlighted that the previous AC NE list has been updated:
if the user opens and iconizes again the AC Viewer, the icon will be displayed again in blue colour.
Figure 243. AC View Icons
1353NM-E Rel. 7.4B

284/532
Operator Handbook
Managing a Map
The AC Viewer is a centralized point for detection of abnormal condition statuses on all supervised NEs.
Looking at this AC Viewer application, the operator can immediately detect which nodes are characterized
by any forcing condition that is causing the AC status. Selecting the NE name from AC NE list, the user,
clicking on the Show Equipment button, navigates directly to the related USM NE and can open, with
the USM commands (Diagnosis > Abnormal Condition List, as shown in Figure 49.), the USM Abnormal
Condition List window. For Q3 NE Abnormal Condition details refer to NR5 Equipment Specific Handbook.
Figure 244. Navigation from AC Viewer (PNM) to NE USM

To configure the automatic refresh time interval, select from the Option menu the set Automatic Refresh
as shown in Figure 50.
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

285/532
Figure 245. Refresh time configuration option

The set refresh window opens. Two different options can be chosen: setting a new time value or default
time value. Select the new time check button at the top of set refresh window (see Figure 51.) and move
the Hour / Minute / Seconds scroll bars to set the new time value (1Min.< accepted value <24Hours).
The Clear button sets the new time to 1Min., but leaves the dialog box open, the Cancel button discards the new entries and closes the dialog box, the as Default button opens the confirmation window
of Figure 51.
On the Confirmation window the OK button inserts the accepted value, displaying the corresponding
seconds between brackets, at the bottom of Figure 50. and closes all dialog boxes, the Cancel button
closes the confirmation box dialog and comes back to the set Refresh window.
1353NM-E Rel. 7.4B

286/532
Operator Handbook
Managing a Map
Figure 246. Set refresh time and confirmation windows

Select the default time check button at the bottom of set refresh window (see Figure 52.) The default
time value is fixed to 15Min. and can not be modified. The Cancel button closes the dialog box, the as
Default button opens the confirmation window of Figure 52.
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

287/532
Figure 247. Set default time and confirmation windows

On the Confirmation window the OK button inserts the 15Min. (900 sec.) value displaying it between
brackets at the bottom of Figure 50. and closes all dialog boxes, the Cancel button closes the confirmation box dialog and comes back to the set Refresh window.
1353NM-E Rel. 7.4B

288/532
Operator Handbook
Managing a Map
7.10 Create ISA board

The ISA board management for OMSN has been described in Section Procedures, OMSN and ATM
board management..."(ref. to chapter 8.2 ). The ISA board management involves both PNM USM / EML
USM commands then this procedure description helps the operator to understand easily all the required
operations.
Figure 248. Create ISA board option
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

289/532
7.11 Map Management

7.11.1 Introduction
Two types of maps are available: the local map and the distributed map. A distributed map is the original
map created by a privileged user from which a local map may be generated by operators having the appropriate access permissions. An operator always works on his own local map and modifies it as necessary
without affecting the original. Only privileged users are allowed to affect the distributed map, each deletion
or modification of distributed maps is irreversible.
A detailed description of the local map management is given at Section TVA. See chapter 3.
The access to these operations is given by the File pull down menu:
Figure 249. File options.
7.11.2 Submaps and local maps

This functions are described in chapter 6 Topology Management that describes the general operations
that the operator may achieve on submaps and local maps.
1353NM-E Rel. 7.4B

290/532
Operator Handbook
Managing a Map
7.11.3 DNM Management

CONDITIONS
The operator admin is actually logged.
SEQUENCE
a)
Save the actual map 'marzia' by selecting File Save Map As...
tk
Figure 250. File: Save Map As
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

291/532
b)
In the Save Map As dialog box enter the map name and click on OK button.
Figure 251. Save Map As dialog box

A DNM Message alerts that the Security profile has been changed.
Figure 252. DNM Message
1353NM-E Rel. 7.4B

292/532
Operator Handbook
Managing a Map
c)
To verify that the map has been saved you may issue File: Map management.
Figure 253. File: Map management

The map which has been just saved is present in the map tree. See following figure.
Figure 254. DNM Map Management dialog box
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

293/532
d)
To verify on SECUSM browser, notice that the object DNM ACD named 'pippo' is now present. See
following figure:
Figure 255. SECUSM browser: DNMAccessControlDomain

And the association dnmusmadmin has been added to profile Administrator.
1353NM-E Rel. 7.4B

294/532
Operator Handbook
Managing a Map
Figure 256. dnmusm admin added to profile Administrator

e)
Exit from USM and reenter with another Administrator profile user. The new saved map is visible.
See following figure:
Figure 257. New DNM Map Management dialog box

Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

295/532
7.12 View: Display Options

This feature is intended to enable the operator to customize the displaying of management states within
his submaps, in term of colour attributes.
The description of this feature is given in Section TVA, paragraph: 6.5.1.8 Setting the Display Parameters of a View.
The involved command is View Display Options
7.12.1 NE Time Management

This management allows the operator to get or to set NE(s) time at the Network Topology view level.
It is implemented at PNM level in the Supervision pull down menu.
However, an operator may have access rights to get the NE time but no access rights to set the NE time.
The operator's profile defines the access rights for the operations.
If the operator does not have the access rights, the corresponding menu is greyed.
Even if the operator has access rights for the two operations, only NEs belonging to the operator access
domain list will be displayed and processed.
7.12.1.1 Get NE Time Action

To get NE(s) time, a GET request is sent to each selected NEs.
Select the NE and issue Operations Time Get
When the user clicks on this option, a window is displayed with all the NEs name related to the selection
(site or NE(s)) as shown in Figure 258.:
1353NM-E Rel. 7.4B

296/532
Operator Handbook
Managing a Map
Figure 258. GET NE TIME

When the operator clicks on the Apply button, a GET request is sent to all the listed NEs. For each
NE, a message is displayed (see Figure 258.):
NE Date and Time: as soon as the NE answer has been received and is correct.
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

297/532
Figure 259. Example of GET NE TIME/
1353NM-E Rel. 7.4B

298/532
Operator Handbook
Managing a Map
7.12.1.2 Set NE Time Action

To set NE time, the OS time is recovered and sent to the NEs by a SET request.
Select the NE and issue: Operations Time Set
Click on Apply. The Command status sting contains date/time sent by EML to NE.
The operator cannot set the NE Time when the NE supports the NTP Protocol or when the NE is managed
by the Craft Terminal (directly connected to the NE).
Operator Handbook
Managing a Map
1353NM-E Rel. 7.4B

299/532
1353NM-E Rel. 7.4B

300/532
Operator Handbook
Managing a Map
8 Procedures for NM Configuration

Q3 Based NE Management explains concepts related to the new Q3 MIB management
OMSN and ATM Board Management for NM Operator explains how to configure and manage the ATM
ISA board.
Procedures to Handle Transmission Alarms explains how to consider the transmission alarm in NM
system.
Alarm Severity Assignment Profile (ASAP) Customization for OMSN explains how to assign a customization ASAP to a PDH path. The procedure must be executed on 1353NM and on 1354RM.
8.1 Q3 based NE management

8.1.1 Data storage and recovery procedures
In NR5, the MIBless architecture has been adopted in NM concerning the management of Q3 NEs. This
implies that 1353NM system does not mirror the NE configuration, and directly uses the NE itself as a reference configuration base.
This has a bunch of consequences in the procedures to be used by the Network Operators in managing
the Network, e.g. backup/restore and configuration alignment procedures.
Moreover, a new entity appears in the scope of the management of Q3 Network Elements, the NE on
board simulator on 1353NM management platform.
This technical description aims at describing the new management architecture, why and how the NE on
board simulator shall be used when managing a Telecommunication Network, and how the management
procedures are impacted from Operator viewpoint.
8.1.1.1 The MIBless architecture of 1353NM

Starting from 1353NM 5.x (hereafter simply referred to as NM") is the Element Management platform that
provides the Network operator with the capabilities to configure and monitor the supported Network Elements (NEs). The 1353NM product allows managing NEs different both in transmission technology (SDH,
WDM, Radio, ATM, IP) and in management interface they provide towards the management system (Q3
and SNMP). In this paper, we will focus on Q3 technology.
With respect to NR3 management structure, 1353NM implements an important architecture change in the
management of Q3 NEs, the socalled MIBless architecture".
Operator Handbook
Procedures for NM Configuration
1353NM-E Rel. 7.4B

301/532
As far as Q3 NEs are concerned, no replication of NE configuration data is kept within NM and the NM
relies on the database stored within the Q3 NEs themselves. This is due to the capability of NM to manage
very big NEs (i.e. DXCs) so that it is not reasonable to duplicate the NE configuration inside NM and to
perform configuration synchronization.
This MIBless architectural choice has some consequences on the Network Management in general, on
management procedures and on Operator perspective. It is worth reminding once more that this new concept applies to the management of Q3 NEs only.
The following list includes the main concepts associated to this new architecture:
1)
The reference database for NM is the NE database itself. The NM operator actually works on
the NE database, and not anymore on a local copy of the NE configuration. Only some administrative NE configuration data are stored within the NM (typically NE name, location, address,
and some other few information). This choice avoids any possible problem of desynchronization of data between EML and NE.
2)
The Data Communication Network (DCN) connecting the NM to the NE assumes a bigger relevance both in terms of reliability and rate. In fact, the faster the network, the faster the
response time of the system in displaying NE configuration data (normal USM views). Moreover, if the NE is isolated, the operator has no possibility (in principle, see later chapter on simulator) to see its actual configuration.
3)
The MIBless architecture implies that there is no need at (re) connection time for the NM to
perform a complete database resynchronization against the actual NE configuration. Only
alarms, the identification of monitored Termination Points and some few other configuration
data have to be synchronized at connection time.
RM DB
RM
optics IM
USM
1
Q3 EML IM
OPTICS IM
Q3 NE
Figure 260. Q3 NE NM connection types
1353NM-E Rel. 7.4B

302/532
Operator Handbook
Despite the fact that NM is not any more the repository of the NE configuration for Q3 NEs, NM product
maintains a central role in the management of the network and in recovery procedures. The following list
includes the main functions (visible or not to the operator) that can be performed only from NM:
1)
The NM is still the unique management system directly connected to the NEs (with the only
exception of 1664SX which can be directly managed by 1354NP for restoration purposes). Any
other management system (RM, SY, BM) which needs to act on the NE has to pass through
the NM.
2)
The NM product is responsible for establishing and maintaining the OSI association with the
managed NEs. It is up to the NM to retry to establish the OSI association after any disconnection
of the management link.
3)
The NM is responsible for the handling of alarms generated by the NE, also with respect to
upper managers so acting as a sort of mediation device.
4)
The NM is responsible for the collection of PM historical data from the NE, independently of the
Manager who started them.
5)
The NM is responsible for the recovery actions to be taken in case of major NE problem (NE
substitution, NE loss of configuration memory).
6)
The NM is responsible for the NEs SW download and NEs MIB backup.
7)
Finally, the NM is responsible for equipment provisioning, synchronization configuration, external point configuration, and for all the functionalities which are not available at NML level.
In few words, the NM is the management platform devoted to all the maintenance activities of the transmission network, and it acts as a central agent between all the network management systems and the
NEs. Nevertheless, it maintains all the capabilities to completely configure and manage the NEs in all their
management domains.
Operator Handbook
1353NM-E Rel. 7.4B

303/532
8.1.2 The backup of Q3 NE into 1353NM

The 1353NM product does not maintain any updated copy of the NE configuration. The NM directly works
on the NE MIB to read and change the current NE configuration.
Nevertheless, in the scope of providing recovery procedures, the NM provides facilities to backup and
restore the database (MIB) of each Q3 NE. The MIB alignup/aligndown procedures are all based on
the same protocol (ISO 802.1e on top of CLNP) used for the SW download.
The MIB file copied into NM is used only as a backup copy of the actual NE configuration, and it is not,
in any case, used during normal network management activities. Therefore, the NE MIB image is not
updated online when the actual NE is being configured (independently on the originator of the configuration changes, either NM operator, or RM / SY systems).
The MIB backup includes all the NE information (i.e. NSAP address, Ethernet, LAPD, ) excepts the
payload structure, crossconnection and PM data.
The MIB backup file size depends on the NEtype. Examples of file sizes are:
1640FOX around 140 KB.
1650SMCaround 170 KB.
1660SM around 630 KB.
1664SM around 90 KB.
1666SR around 30 KB.
1641SX around 40 MB (for a big DXC configuration).
and the time required for backup is in the order of few minutes (5 to 10 for DXC).
It is likely worth noting that the backup of DXC is performed via SMF.
N.B.
Note that backup files for new equipments are compressed, then requiring less memory space
and less transmission time.
Now, the MIB of the NE backed up into NM is actually the exact copy of the memory inside the NE. This
copy is strictly dependent on NE type and release, and it's basically readable by the NE only.
Since RM contains in its internal database all the configuration of the NE as far as the transmission fragments are concerned, it is mandatory for the MIB backedup into the NM to be always synchronized with
the latest changes in the Equipment and Synchronization configuration information.
In other words, the NM operator shall perform an upload of the NE MIB every time either CT or NM
operators performed any change in the Equipment (board provisioning) or Synchronization configuration. In this way, NM and RM systems together contain a global and consistent information of the
actual NE configuration.
1353NM-E Rel. 7.4B

304/532
Operator Handbook
In order to trigger the Operator for such upload, an alarm is generated by the system every time there is
even the doubt that the Synchronization or Equipment configuration changed with respect to the copy
present in the NM system. The alarm (with MIB backup misaligned probable cause and warning severity
see Figure 261.) will be cleared by the system as soon as the MIB upload operation has been successfully
performed on the relevant NE using the Supervision Align Up option.
Figure 261. Misalignment (warning alarm) between NE NM MIB and NE configuration

The MIB upload operation is manual, and not automatic, since the system cannot automatically know
when the sequence of configuration operations done by NM Operator is finished, or if the configuration
operation done by CT Operator is really to be adopted by the centralized management platforms.
The utility of the backup copy is basically associated to the possibility to restore the previous configuration
data into a NE that failed. In this scope, it is mandatory for the management systems to be able to re
create the latest configuration of the NE in order to download it.
The backup and restore of the MIB database can be performed by CT as well, so that the NE MIB will be
transferred onto CT platform.
The MIB operation is completely uncoupled from the existence and usage of NE onboard simulator in
NM. In fact, for example, DXC and WDM NEs do not support the simulator on NM, while they do support
the possibility to backup and restore their MIB.
Operator Handbook
1353NM-E Rel. 7.4B

305/532
The NE simulator, named also onboard simulator", utilizes the same NM NE MIB (NE MIB copy in the
1353NM system) and the different expression is often used to distinguish the environment of NM NE MIB
activation. So the onboard simulator" is activated in read/write configuration when the NE Supervision
has been stopped: the Supervision State is Declared" (see Figure 262.).
Figure 262. NE Statuses shown window
1353NM-E Rel. 7.4B

306/532
Operator Handbook
The MIB alignup.

The alignup option allows the operator to upload the copy of the MIB image from the NE into the area
of the NM simulator. The simulator will use this copy, which is supposed to be the last updated one of the
NE database. When the database is being aligndown, this MIB image will be downloaded into the NE.
The last NE MIB image alignup always overwrites the previously one, even if its contents have been
changed using the NE simulator.
Figure 263. Simulator menu Align Up" option

With the NE Supervision State Supervision", open NE USM application and select the Align Up option,
confirm the align up and wait the end of the operation (see Figure 264.).
Operator Handbook
1353NM-E Rel. 7.4B

307/532
Figure 264. Information window during a MIB Align Up procedure

N.B.
The Activate" option shall performed after an Align Down" to NE command to activate the NM
NE MIB copy into the NE equipment
After pushing the Activate button the related NE shall restart itself therefore the NM operator
has to wait a few minutes until the NE will became aligned with the new MIB previously downloaded. During this transitory period no actions on the NE are possible because the NE is in
Q3 isolation.
1353NM-E Rel. 7.4B

308/532
Operator Handbook
The following picture depicts the NM MIB repository:
NM
Q3 OBS
Q3 USM
NM NE MIB
OPTICS IM
ISO 802.1e
Q3 NE
DB
Figure 265. NM MIB representation
Operator Handbook
1353NM-E Rel. 7.4B

309/532
8.1.3 The onboard simulator of Q3 NE into 1353NM

An important change in NR5 is related to the introduction within the NM of NE onboard simulators (OBS).
The onboard simulator is used to simulate the presence of the actual NE on the NM in order to read (and
write) the MIB copy resident on the NM. The onboard simulator is actually the same SW of the NE, just
ported onto NM platform.
The onboard simulator is a tool that shall be used in the scope of precise procedures, hereafter listed,
and normally it is always switched off. The OBS is not provided for testing or debugging purposes, but it
is an integral part of NM product.
The reasons why the OBS is required on NM are the following:
1)
In case of a DCN failure between the NM and the GNE, the NM operator has lost access to the
NEMIB. He is not anymore able to know the NE configuration. Normally there is no strong reason why the NM operator should be interested in knowing the last known NE configuration, but
if he/she does want to navigate through the NE configuration, he/she can start up the simulator
and read the backup copy of that NE.
2)
When an offline configuration operation is performed. The offline configuration procedure is the
possibility for RM operator to act on the configuration of one Q3 NE even if it is not yet currently
reachable (because not yet installed). This feature can offer to the Network Administrator the
possibility to preconfigure the network, starting creating the network topology and even transmission configuration before the network actually exists. Hence this feature applies only once
in the network lifetime. All the NEs pertaining to the network shall be declared and provisioned,
even if not yet installed in field. In this scope, the NM Operator can use the onboard simulator
to provision each new NE, one at a time. Through this simulator, the 1354RM system can get
aware of ports existing in each NE, so that RM can populate its internal database. From this
moment on, the onboard simulator shall be switched off and RM will work on its own database.
3)
The replacement of an Equipment Controller (EC) is in fact the main reason for the development of the OBS The replacement requires a procedure which synchronizes onsite activities
on the management system to avoid traffic perturbation. The procedure is based on a resynchronization between the data stored into 1354RM system and the NE MIB backup. In this
scope, the simulator is mandatory to allow RM to write onto NE MIB backup in order to realize
the realignment.
Therefore this is an emergency procedure applied when a NE is unreachable or to replace the EC, per
default, only one OBS can be opened at a time.
Hence, it is clear that the simulator shall be used only in very special and delicate network phases, and
that its usage shall be controlled by expert network operators.
The OBS is manageable by NM not by Craft Terminal
A more detailed description of the above procedures are provided in para. 8.1.3.1 and 8.1.3.2.
1353NM-E Rel. 7.4B

310/532
Operator Handbook
RM
DB
OPTICSIM
USM
NM
OPTICS IM
Q3 EML IM
OPTICS IM
NE
Simulator
NEs IDs
STARTED
DB
OPTICSIM
Q3 NE
Figure 266. RM connected to NE simulator

Once understood why and when the NE OBS shall be used, it is clear why the operator can only start the
NE simulator manually. No automatic mechanism to startup the simulator exists in NM. Moreover, the
NE simulator can be started only if the associated NE is not currently read (condition of Q3 isolation).
The NM operator shall startup only one simulator at a time.
As it is manually started, the NE simulator shall be manually stopped. If the simulator of a given NE is
started, and maybe the NE becomes reachable again, the operator keeps on working on the NE simulator
until he manually stops it.
Once started, the NM operator is aware of the fact that he/she is currently working on the simulator, and
not on the actual NE, by the relevant state on the right side of the USM. Moreover an OBS monitoring process is available to detect globally which simulator is active, if any (see Figure 267.).
The onboard simulator can be opened from TMNOS view. On Board Simulator Monitoring. Clicking on
the monitor picture, the box window shows the NE equipment name where the OBS is running. Note that
this window is not automatically updated: push the Refresh" button to know the current onboard simulator status.
Operator Handbook
1353NM-E Rel. 7.4B

311/532
Figure 267. Onboard Simulator monitoring

Assuming that the supervision of that NE was not previously stopped on a given NE, if this latter becomes
again reachable while the NM Operator is working on the simulator, and hence on the local MIB, the operator is aware of this by the clearing of the Q3 isolation" alarm, which is visible on both AS and USM. If,
on the other hand, the supervision was previously stopped for that NE, the operator can check about the
possibility to reach the NE by the OSI ping functionality.
To open the communication test tool window select the Administration" icon, then select the menu:
System Management features Local Data Management Ping NE
The OBS feature is not available at all for DXCs, because the DXC is already redundant with two AUs.
Moreover, OBS is not available for WDM, since not yet managed at NML level.
Finally, it is worth adding a note on the releases of simulators and associated NEs. It could occur that the
release of a given NE simulator is different (lower) than the release of the actual NE. This is possible, and
due to the fact that the NE simulator needs to be aligned with the actual NE as far as the configuration
of the NE is concerned. All the dynamic NE behaviors (e.g. event or alarm reporting, PM collection) are
not relevant for the NE OBS. Therefore, it can happen that during the testing phase, some NE behaviors
related to the dynamic mechanisms of the NE have been corrected, but they did not require a new NE
simulator version.
1353NM-E Rel. 7.4B

312/532
Operator Handbook
8.1.3.1 Equipment boards replacement procedures without affecting the service

The Equipment boards replacement have to be performed following specific procedures written taking in
account the NR and the board type. The operator can refer to the network integration of existing documents.
8.1.3.2 Procedure to perform an offline configuration

The offline configuration procedure applies to RM and NM operators to act on the configuration of one
Q3 NE even if the latter not yet currently reachable (because not yet installed). This feature offers to the
network administrator the possibility to preconfigure the network, starting creating the network topology
and even transmission configuration even before the network actually exists (predeployment phase).
Hence this feature applies only once in the network lifetime.
In order to start the offline configuration, the NM operator shall startup the onboard simulator as soon
as RM has to retrieve ports from that NE. NM operator shall configure the NE in terms of equipment configuration (boards, etc.). Then the RM can upload the ports from the simulator according to the configuration entered by NM operator. Once aware of the NE equipment configuration, RM works locally
configuring the NEs RM MIB in download disable mode. During the network configuration done by RM,
the simulators on NM shall remain stopped. The network population offline procedure is:
1)
Open the NM PNM window and create the NEs on the Map View in the Declared" Supervision
State.
2)
Select, on NM PNM, the NE and open the USM. Select the Start" Simulator option from the
Supervision menu.
3)
Configure the NE equipment and the NE synchronization sources.
4)
On 1354RM, enable the NE NM MIB uploading to upload the NE Simulator ports.
5)
On 1354RM, disable the NE NM MIB uploading. The 1354RM will work with its internal NEs RM
MIB.
6)
Stop the NM onboard simulator and restart from step 2) up to consider all the NEs involved
in the network configuration.
As soon as the actual NE will become reachable, two possible policies are implemented:
a)
The NM operator shall download the NE NM MIB onto the actual NE, in order to instruct it about
equipment configuration, and then the consistency download from RM will be performed directly with
the NE in order to download the RM related configuration information. Once downloaded the image
stored in NM, the configuration can be activated in the NE even if not complete (it does not include
the configuration performed by RM). This operation affects traffic, if the network already carries traffic. Normally it is not a problem since the NE is new and it does not carry any traffic. The procedure is:
1)
On NM, open the PNM window and change the NE Supervision State in Supervision" for all
the reachable NEs.
2)
Open the USM window and select the Align down" option from the Supervision menu. Repeat
the operation for all the NEs involved in the network configuration.
3)
On 1354RM enable the NEs RM MIB downloading mode to manage the NEs transmission network.
Operator Handbook
1353NM-E Rel. 7.4B

313/532
b)
The simulator is activated on NM. RM performs a consistency download, actually working on the on
board simulator, and hence on the NE NM MIB. The NE NM MIB is Aligned down onto the real NE,
which will be then automatically aligned with both NM and RM. The RM is working in disable downloading mode and the NM simulator has been stopped. The following procedure has to be applied
to any NE taken over by NMRM management system.
1)
On NM open the PNM window and change the NE Supervision state in Supervision".
2)
Open the NE USM window and select the Align Up option from themenu:
Supervision Simulator Align Up .
3)
On NM open the PNM window and change the NE Supervision state in Declared".
4)
Open the NE USM window and select the Start option to start up the onboard simulator:
Supervision Simulator Start .
5)
On RM enable the NE NM MIB uploading to upload the SDH and PDH ports.
6)
On RM in disable downloading mode, execute a mark audit and verify that the list of misaligned
objects does not concern the equipment and synchronization configuration.
7)
On NM open the PNM window and change the NE Supervision State in Supervision" to manage the NE configuration.
8)
On RM enable the NE downloading to manage the NE paths.
1353NM-E Rel. 7.4B

314/532
Operator Handbook
8.1.4 RM behavior with respect to the MIBless architecture

1354RM product reflects in its internal behavior the new NR5 MIBless architecture of NM management
platform. Actually, this is rather an internal issue and does not impact the procedures for managing the
network at Network Management Level.
The MIBless architecture of NM does not have any impact on the type and amount of data managed by
RM. RM is the manager of the transmission network, and contains in its internal database all the information related to the transmission network only. RM is not aware of the Equipment configuration of a NE,
and not even of the synchronization or networking configuration of a given NE.
On the other hand, the passthrough role of NM implies that RM system sends commands directly to NEs,
and their availability becomes an important parameter for RM. In case of command to be sent to an
unreachable NE, the RM stores the relevant commands internally, and automatically resends them as
soon as the NE becomes again reachable. But this has no impact on the operator's view of the management. If the NE is not currently reachable, the path cannot be implemented anyway.
Since RM keeps on having its internal database mirroring the Network configuration, there is the need to
maintain the RM database synchronized with the actual Network Element MIB.
RM is now responsible for guaranteeing that there is no misalignment about configuration information. An
efficient mechanism has been setup in order to allow RM to immediately identify whether there could be
misalignment with a given NE. In such a case, the RM operator is informed, and he/she can react by auditing the misalignment and eventually forcing the RM configuration information into the NE.
As for NR3, the RM operator is able to specify whether he wants to really act on the network element configuration (download enabled mode) or just work on the RM database (download disabled mode). If the
download disable mode is entered by RM operator, the RM operator can still work configuring its network,
but configuration commands are not sent to NEs for modification change, but just stored internally for later
appliance or for crosscheck with actual NE configuration.
The RM system enters the downloaddisabled mode status as soon as either of the following events
occurs:
A given NE is not reachable by RM for any reason (DCN failure, NE failure, NM restart, etc.).
Once the NE is reachable again, the RM automatically downloads towards it the locally stored
configuration changes.
The NM operator has granted the access to the CT operator into a given NE. Once the NE is
reachable again, the RM system informs the operator about possible inconsistencies, but no
automatic download is performed towards the involved NE. It is up to the operator to act and
decide whether to perform an audit or just to force the realignment (download from RM).
The RM operator has asked for download disable to a given NE. Once the operator exits the
download disable status, the RM performs an automatic download towards the NE.
Operator Handbook
1353NM-E Rel. 7.4B

315/532
8.2 OMSN and ATM board management

8.2.1 Introduction
This document describes the procedures associated to the management of the ISA board into OMSN
NEs, in particular focusing at board creation and supervision operations performed through EMLUSM
and PNM applications. This is a guideline document oriented to NM Operators involved in management
of ATM boards, starting from release 5.x, the first one offering the management of ISA boards inside
OMSNs.
Basic EML operations, like Create/Remove NE and Start/Stop Supervision, are assumed to be known,
as well as NEspecific operations to be done with the EMLUSM, like Set/Remove Board and IP address
configuration.
Since OMSNs are actually multiservice nodes and the provisioning of different communication services
is achieved via different management entities, from now on the term "entities" will refer to both the OMSN
NEs and the ATM boards.
1353NM-E Rel. 7.4B

316/532
Operator Handbook
8.2.2 OMSNs and ISA board: PNM customization

ISA boards cannot be considered as all the other PDH/SDH boards normally equipped into the NEs, since
they run a SNMP agent interworking with the SNMP EMLIM at NM level, that is supporting parallel management sessions with respect to Q3 connections established between the Q3 EMLIM and the OMSN
ECs.
1353NM
SNMP
EMLIM
ISA
Q3
EMLIM
OMSN
Equipment
Controller
Figure 268. OMSN and ISA board

The peculiar nature of ISA boards and the generic requirement on PNM to support both SDH and ATM
alarm synthesis in the OMSN icon, has lead the design of a PNM customization where all the managed
ISA boards are represented by dedicated icons (in the same way standard NEs are).
In the following, a procedure is described for the configuration of PNM enabling proper ISA management
inside network maps/submaps.
ISA management in PNM needs basically two preliminary operations, to be carried out just once, before
the first ISA board is to be equipped into a given OMSN described into a given Map.
the SDH equipment (one element).

the ATM boards (n elements, as many as the ISA equipped).
As usual, the Operator shall select the NE of interest from the PNM Global Inventory (in this context the
ISA boards are listed into the Global Inventory as standard NEs). The insertion of the SDH OMSN into
the OMSN submap itself is mandatory, otherwise the PNM will not perform a correct behaviour.
Operator Handbook
1353NM-E Rel. 7.4B

317/532
8.2.3 Create ISA board
SEQUENCE
a)
Select the NE which houses the ISA board and issue Operations: Create ISA. See following figure:
Figure 269. Operations: Create ISA
1353NM-E Rel. 7.4B

318/532
Operator Handbook
b)
The Create ISA dialog box is presented as per Figure 270. You can select the board type.
Figure 270. Create ISA dialog box

c)
Enter the suitable selections and click on Apply button to confirm. The ISA board is displayed with
an icon similar to NE icon. The userlabel contains the name of the parent NE and the ISA slot position.
Operator Handbook
1353NM-E Rel. 7.4B

319/532
8.2.4 ISA Address

SEQUENCE
Figure 271. ISA: Set Address: NE Address

a)
Assuming that the IPoverOSI tunnelling is already correctly configured in the OMSN (it is out of
scope of this procedure description), the Operator can set the IP Address of the ISA boards by selecting the menu: Set Addresses: IP Address.
Figure 272. Set Addresses: IP Address

When a new board has to be provisioned into the OMSN, the first step is always settinginservice the
board itself via the EMLUSM. The same applies to ISA boards.
The Operator starts the OMSN EMLUSM, selects the slot of interest and, from the menu:
Euipment Set
chooses the ATM board type: "ATM4x4" in case of a 4x4 ATM matrix, "ATM8x8" in case of a 8x8 ATM
matrix. In the reference case an ATM4x4 is provisioned.
1353NM-E Rel. 7.4B
320/532
Operator Handbook
Now the Operator shall perform a parallel description of the ISA as NE contained within the OMSN domain
(submap) into the PNM, as it is for all the managed NEs at EML level.
Reminding that the submap could in general contain the OMSN itself plus a number of already described
ISA boards, the Operator can create the new ISA instance into the PNM by selecting the OMSN icon and
choosing the menu option
NE Directory Create ISA Board, thus opening a new window into the PNM.
The User Label of the ISA board is automatically generated as derived from the OMSN User Label, once
Rack/Subrack/Slot coordinates of ISA itself are inserted by the Operator. Also ISA IP address shall be
inserted (dotted format). No complete Friendly names shall be chosen by the Operator, as per all other
NEs. If no OMSN (namely 1640FOX, 1650SMC or 1660SM) is selected the menu is greyed out.
It is worth noting that the NM Operator shall insert consistent information about ISA coordinates and IP
address between OMSN EMLUSM and PNM, otherwise the NM will not be able to start the supervision
on ISA and manage the ATM services.
Operator Handbook
1353NM-E Rel. 7.4B

321/532
8.2.5 OMSN + ISA: Supervision

SEQUENCE
a)
Select the ISA board icon from the map and issue Supervision: No Alignment.
Figure 273. Start Supervision on OMSN.
1353NM-E Rel. 7.4B

322/532
Operator Handbook
8.2.6 Rename ISA board

As already highlighted, the ISA User Labels must be aligned to the parent OMSN User Label. As a consequence, each time the OMSN friendly name changes, the user labels of slave ISA Boards shall be modified accordingly.
The supervision shall be stopped on all the NE provided services (Q3 OMSN + all ISAs).
OMSN friendly name is changed according to the normal procedure. Then the Operator shall launch a
new, dedicated tool for ISA label modification, from the menu Operations: Rename ISA.
The Rename ISA Board tool addresses just the OMSNlabel change only, not the change of ISA physical
coordinates (e.g. slot change into the subrack). If an ISA has to be moved from Slot X to Slot Y, the only
available procedure is first removing the ISA and then recreating it as it is a new board to be setup.
The Operator has the responsibility to update the OMSN label according to what already defined when
performed the Change Q3 Ne name procedure, since no doublechecks are implemented to detect operators' errors.
It is worth noting that the new OMSN name shall be inserted just once, and the tool will automatically
upgrade the labels of all the equipped ISA inside the OMSN.
When the tool starts, the list of all managed Metro OMSNs' Friendly Names is shown. Each time a item
in the list is selected, the contained ISA boards are shown in the lower side of the window.
In order to change one of the current OMSN User Labels displayed on the left side of the list, the Operator
shall insert the new user label in the right column (the one displayed in red). Then he can commit the modifications by clicking on the "Apply" button.
The user may change the name of the ISA board via the menu Operations: Rename ISA.
Figure 274. Operations: Rename ISA
Operator Handbook
1353NM-E Rel. 7.4B

323/532
8.2.7 Error Recovery: commands for NM administrators

In case an NM Operator made an error during the ISA Board creation phase (wrong rack and/or subrack
and/or slot position), the NM administrators (axadmin profile) with granted access to the Command Line
will be able to perform a manual renaming of the user label associated to the ISA board.
The command syntax will be provided in the 1353NM Administration Guide.
1353NM-E Rel. 7.4B

324/532
Operator Handbook
8.3 Procedures to handle Transmission Alarms

8.3.1 Introduction
This technical description provides a highlevel description for procedures to be followed by Operators
to deal with Transmission Alarms with 1353NM product, starting from release 5.x, when supervising Q3
CMISEbased NEs.
The basic reason for these guidelines is that, for CMISE based NEs, transmission alarms do not contribute
to the alarm synthesis shown in the subrack view of the Network Element. Therefore, starting from the
subrack view of a given NE, a new procedure is required to identify immediately where transmission
alarms are.
8.3.2 Why Transmission alarms are not shown at subrack view?

This section aims at explaining the rationale behind the choice of preventing transmission alarms to be
part of Alarm Synthesis in the NE subrack view.
The new behavior, applying to 2nd generation NEs, based on CMISE management interface, has been
designed according to the principle that the 1353NM, as a product devoted to the maintenance of the
equipment in the network, is not basically involved in the management of the Transmission services provided by the network, which is a core task of other Network Management Platforms.
Therefore, the 1353NM product shall be designed and optimized in order to help the Operators to identify
immediately the roots of equipment alarms. This will improve the network maintenance process by reducing reaction times, without being flooded by alarms referred to the Transmission Services, which are the
responsibility of other personnel in the Customers' organization.
The subrack view of 2nd generation NEs provides a perboard Alarm Synthesis related to equipment
alarms only. Hence, the Operator can immediately identify which boards currently have some maintenancerelevant alarms.
Nevertheless, the counters on the topleft part of the NE GUI, indicating the total number of active alarms
on the NE, do include the Transmission alarms, in order to provide a global view of the NE alarm status.
Moreover, the new splitting of alarms in alarm domains and associated counters, on the topright part of
the GUI, allows the Operator identifying specifically the number of transmission alarms currently active
on the NE (see Figure 275.).
Operator Handbook
1353NM-E Rel. 7.4B

325/532
Figure 275. Alarm indication syntheses
8.3.3 How to identify transmission alarms starting from NE subrack view

As stated, the transmission alarms do not contribute to the alarm synthesis associated to each board of
the NE subrack view. Therefore, a procedure has been setup to allow the Operator to identify where Transmission alarms are, with no need of an unfocused, timeconsuming navigation activity through all the
Views of the GUI before detecting which transmission object has been affected.
A new set of options is present in Figure 276., under Diagnosis/Alarms menu item.
Figure 276. Alarm Menu
1353NM-E Rel. 7.4B

326/532
Operator Handbook
The Transmission Alarms item allows the operator to open the Alarm Surveillance application (AS), focusing only on the current transmission alarms of that NE, as shown in Figure 277.
Figure 277. Alarm surveillance window

The Operator can now select the current alarm of interest and, exploiting the ASEMLUSM navigation
capability, moving back to the NE EMLUSM application, now addressing the proper View with respect to
the affected resource.
The AS menu of Figure 278. allows performing the required navigation:
Figure 278. AS navigation back to NE EML USM
Operator Handbook
1353NM-E Rel. 7.4B

327/532
In this scope, the Operator does not have to navigate throughout the NE configuration, starting from the
subrack view, in order to identify the Transmission alarm: the right view displaying the resource actually
affected by the alarm of interest is immediately available, so that remote diagnostic tasks from the NOC
could be started with no delays. You can look at the following figure and see that the Operator has selected
a LossOfSignal item in the AS and the navigation back to the EMLUSM has automatically popped
up the Port View associated to the SPI experiencing the LOS.
Figure 279. Relationship between AS and Port View of NE EML USM
8.3.4 Transmission alarms sublist in AS component.

In case the Operator wishes to pay even more attention to Transmission alarms, thus orienting the
1353NM to be a management system pushed beyond the pure equipment maintenance scope, it is possible to customize the system by creating an alarm view devoted to transmission alarms only.
Starting from such view, the Operator can again select an alarm, and navigate onto the GUI associated
to that alarm, and again the GUI will be opened on the View where the alarmed resource is shown.
1353NM-E Rel. 7.4B

328/532
Operator Handbook
8.4 Alarm Severity Assignment Profile Customization for OMSN

8.4.1 Introduction
The procedure described in this document is a shortterm solution is only available from FIX12 of NR5.0C
PL2.
The operator has to follow the procedure having care in avoiding any human error.
The ASAP (alarm severity assignment profile) is a descriptor which associates the proper severity to the
probable cause of each alarm.
This profile is then associated to the relevant resource.
For more detailed explanation please refer to 1354RM Operator's Handbook, Section Maintenance.
8.4.1.1 Scope
The scope of this procedure is to change the severity of some alarms. In particular, PDH functional blocks
concerned are:
PPI, E* (E1 or E3), P* (P12 or P3).
while SDH functional blocks V* (V12 or V3) are not concerned:

In the previous system version releases, 1354RM was associating the standard 'All Alarms' ASAP to the
PDH functional blocks of the SDH paths, while the SDH functional blocks (e.g. VC12) were associated
by 1354RM to the default 'No Remote Alarms' ASAP.
8.4.1.2 Description and Warnings

The procedure must be executed first on 1354NM, then on 1354RM.
It is mandatory to assign the same ASAP identifiers to the whole network, i.e. to each NE, to
each NM, to each RM of the network.
Since the ASAP identifiers are automatically assigned by 1353NM, it is important to execute
the same identical ASAP creation procedure per each 1353NM.
8.4.1.3 Description of the procedure

The procedure is constituted by the following main steps:
a)
The 1353NM operator, per each NE, creates the new customized ASAP, associating the severity to
the Probable Cause for the involved alarm.
b)
The 1354RM operator associates to each type of PDH port involved, the ASAP identifier previously
created by the NM operator.
The detailed procedures are described in the paragraphs which follow.
Operator Handbook
1353NM-E Rel. 7.4B

329/532
8.4.2 Customizing a new ASAP on NMOS

8.4.2.1 Introduction
This section describes the procedures on NM to provide the ASAP customization required from RM.
The freeuse ASAPs are always created cloning an already existing ASAP: hence, also in freeuse
ASAPs all foreseen (for a certain NE) probableCauses will be always present. Removing or adding probableCauses is not allowed.
The maximum number of freeuse ASAPs supported in NMOS is product dependent: the freeuse
ASAPs are 2 for OMSN.
8.4.2.2 ASAP creation Procedure on NM

Select the supervised OMSN NE in the map window view and with Show Equipment command open the
NE EMLUSM window. Then click on Configuration Alarms Severities as shown in Figure 281.
Figure 280. Show Equipment pop up menu
1353NM-E Rel. 7.4B

330/532
Operator Handbook
Figure 281. Configuring Alarm Severity Assignment Profile.

The following window opens:
Figure 282. ASAPs Management dialogue box.
Operator Handbook
1353NM-E Rel. 7.4B

331/532
Select an ASAP in the List of ASAP" field to enable the Clone" button. Obviously the operator should
select the ASAP which most matches the required customization, since the customization procedure is
manual in this NM release. click on the Clone button to create the new freeuse ASAPs identifier with
the default number #10001 (as shown in Figure 283.). It is important not to change the ASAP Id" since
the same shall be used on RM and therefore it is guarantee of coherence among the network.
The user can mark the new ASAP, adding a character string after the identifier (#10001, #10002) as shown
in the following.
Figure 283. ASAP Edition dialogue box example.

The operator can modify the severity associated with each probable cause. Hence, select the Probable
Cause Families: Communication, Equipment,... whose severity level you want to modify. Then select the
Probable Causes Name and click on the option button: Service Affecting (SA), and then Non Service
Affecting (NSA) and then Service Independent (SI). For each one you can choose the severity value
among Critical", Major", Minor", Warning" or Nonalarm". A Nonalarm" probable cause corresponds
to no alarm emitted for this probable cause.
1353NM-E Rel. 7.4B

332/532
Operator Handbook
OMSN do not support the SI severity but the SI severity can be provided selecting, in SA and NSA fields,
the same severity value as indicated in Table 18. and Table 19. case 2 (SI). Usually the NSA default
severity is lower than the SA severity (see Table 18.) but in general any possible severity customization
assignment can be chosen (see Table 19.).
Table 18. Default Assignment of Service Dependency and Severity on OMSN
Case
Service Affecting (SA)
Non Service Affecting (NSA)
Service Independent (SI)
major
minor or warning or non

alarmed
not used
2 (SI)
major, minor, warning
major, minor, warning
not used
Table 19. Possible customization Assignment of Service Dependency and Severity on OMSN
Case
Service Affecting (SA)
Non Service Affecting (NSA)
Service Independent (SI)
critical or major or minor or critical or major or minor or

warning or nonalarmed
warning or nonalarmed
not used
2 (SI)
critical, major, minor, warn- critical, major, minor, warning

ing
not used
When you have configured the ASAP, press the OK button to confirm the settings and close the dialogue
box or the Cancel push button to cancel the new settings and close the dialog box. If necessary, repeat
the previous ASAP creation starting from the ASAP clone of Figure 282.The second new ASAP identifier
will begin with #10002... as shown in Figure 284.
Operator Handbook
1353NM-E Rel. 7.4B

333/532
Figure 284. Example of Management dialogue box with two customized ASAPs
When the procedure has been completed close the selected NE EML USM and start again from the beginning selecting a new NE from the map view window. Therefore to assign to PDH ports of RMOS the customized ASAPs the above same procedure has to be applied to any NE involved in the path
communication circuit.
8.4.3 Customizing a new ASAP on RMOS for PDH ports

8.4.3.1 Customize the new ASAP
In order to associate a new alarm profile, previously created via NM on all PDH ports of all NEs composing
the whole network, the RM operator has to execute the following procedure:
a)
Shutdown the 1354RM system. From 1354RM Process Monitor window select Actions: Shutdown:
System. Wait...
b)
Exit from CDE session.
c)
Execute login as root user.
d)
Edit the following startup script:

/usr/snml/nxnlenv_make
1353NM-E Rel. 7.4B

334/532
Operator Handbook
Within this file it is possible to change the ASAP identifier for PDH Ports.
The relevant variables are:
NL_PdhPort_2Mb_ASAP
for 2 MB Ports.
NL_PdhPort_34Mb_ASAP
for 34 MB Ports.
for 45 MB Ports.
for 140 MB Ports.
The commands to be entered are respectively:

export NL_PdhPort_2Mb_ASAP=<ASAP identifier numeric field for 2 Mb ports>
where <ASAP identifier numeric field for xx Mb ports> is the value previously defined by the NM operator.
The same ASAP id can be associated to several PDH port types.
N.B.
The syntax is case sensitive (Uppercase/Lowercase)
See following figure:
Operator Handbook
1353NM-E Rel. 7.4B

335/532
ASAP IDENTIFIER 5digit numeric field
PDH Port type
Figure 285. ASAP Identifier on ASAP Edition dialogue box

e)
Execute the script "customize_patch":

/usr/snml/etc/customize_patch
Exit from CDE session.

f)
Login as snml user.
g)
From the Process Monitor window execute Actions: Startup: System. The system starts using the
new environment variables previously defined in file:
/usr/snml/nxnlenv_make
N.B.
Notice that after each patch installation, it is mandatory to reenter the customize commands
above mentioned on page 334.
1353NM-E Rel. 7.4B

336/532
Operator Handbook
8.4.3.2 Error analysis

Once the RM operator implements a PDH circuit, he has to specify whether he wants to enable PDH
alarms. In case he does want, the specified ASAP profile will be used.
If the ASAP required for the PDH circuit has not been preconfigured into the terminating NE, then RM
will display a generic error message, indicating that something went wrong in the implementation of the
circuit.
In this case, the Operator has to check the reason of the failure:
1)
To verify on NM if the required cloned ASAP is present on path terminating NEs.
2)
To check on RM using the routing display for the actual implementation of the path (if the error
occurs during the implementation or commissioning of the path).
3)
To check on RM using the NAP view (if the message error appears upon a request for ASAP
change done during circuit lifetime).
EXAMPLE
a)
The routing display of the path shows that the path implementation state is failed to implement and
that NAP consistency state is failed to align. See following figure.
Figure 286. Path routing display
Operator Handbook
1353NM-E Rel. 7.4B

337/532
b)
In case the reason for path implementation state=failed to implement is missing ASAP on terminating NE, the NAP alarm detail will show PDH disabled alarms as cause of misalignment. See figure that follows:
PDH Disabled Alarms
Figure 287. PDH Disabled alarm
1353NM-E Rel. 7.4B

338/532
Operator Handbook
4)
The misalignment is due to the fact that:

a)
at RM level in the /usr/snml/nxnlenv_make file (see below figure) the ASAP identifier for
2 Mb ports is equal to 7
Figure 288. RM level ASAP identifier

b)
at NM level this ASAP identifier is not existent in the NE for that port. See following figure:
Figure 289. NM level ASAP list
Operator Handbook
1353NM-E Rel. 7.4B

339/532
8.5 Object Assignment Domain

SEQUENCE
a)
Click on icon 1353NM Admin. The System Management Tools box is displayed.
b)
From the System Management Tools box select SEC Administration.
c)
Select SEC USM Browser.
d)
Select OAD: Object and click on Create Object button. (see below figure).
e)
Enter name (e.g. ROSSO), family (e.g. Access Control Domain), System Id (string or FDN) and click
on Apply button. The new OAD is now present. See Figure 291.
Create
OA
Object
name
AC
Figure 290. OAD: Object: Create
1353NM-E Rel. 7.4B

340/532
Operator Handbook
NEW OAD
Figure 291. new OAD object
Operator Handbook
1353NM-E Rel. 7.4B

341/532
f)
Point with the mouse to Elementary OAD and issue the popup menu Create new Elementary OAD.
The same menu option is present in the popup menu of an existing Elementary OAD.
Figure 292. Elementary OAD: Create

g)
Enter the Elementary OAD name and move to the right subbox the objects to assign. Click on Apply
button to confirm.
1353NM-E Rel. 7.4B

342/532
Operator Handbook
h)
Select the Operator profile to which you want to assign the Elementary OAD and click on Edit Operator profile. See following figure:
OPTION BUTTONS
LEFT BOX
RIGHT BOX
Figure 293. Edit Operator profile

In the Edit dialog box select option button Elementary OAD (deselecting the other buttons) and from the
left selection box select the Elementary OAD to add and include it (e.g. rossino) by pressing the right
arrow. Click on Apply to confirm.
Now all operators with profile=Viewer contain the Elementary OAD ' rossino'.
Operator Handbook
1353NM-E Rel. 7.4B

343/532
Figure 294. Elementary OAD and ACD of the Viewer Profile
i)
Restart LSS process to render effective the change
1353NM-E Rel. 7.4B

344/532
Operator Handbook
EXAMPLE
An operator with profile=admin and Elementary OAD=rossino and ACD=ROSSO, when creating a new
NE will be able to select ACD=ROSSO to include or not the management of the new NE. See following
figure:
Figure 295. Create NE
Operator Handbook
1353NM-E Rel. 7.4B

345/532
8.6 File Transfer Scheduler

8.6.1 Introduction
The FT Scheduler allows to execute software downloading operations on multiple NEs, defining the
sequence to be followed and the activation time as SWDL (Software Downloading Scheduler).
The FT Scheduler is an application useful to launch multiple file transfer (SW Download, MIB backup)
between the OS and the NEs providing scheduling & periodic services. In addition, to avoid critical network
load, the FTS allows to plan the DCN loading during the file transfer.
The FT Scheduler is an application designed for SNMP and Q3 NE protocol interfaces that allows to execute the SNMP MIB back up and the Q3 MIB align up.
To open the FT Scheduler, in the PNM management window, select Operations FT Scheduler
option (as shown in Figure 296.).
Figure 296. FT Scheduler option

The USM process can be installed on any OS types (Master or Presentation). Only one FT Scheduler USM
can run at the same time on the same OS workstation: if the user tries to open a new FT Scheduler USM,
a warning box will advice that the application is already running.
8.6.1.1 FTS Application

The FTS application can be applied to all NEs independently from the technologies and/or the protocol
type: the application automatically excludes those NEs that do not support SWDL protocol or MIB Backup/
Align Up.
1353NM-E Rel. 7.4B

346/532
Operator Handbook
The application masks operational differences so operativeness and results are uniformed for different
NE protocol type (Q3 or SNMP). Then the same FTS windows and procedures will be applicable for different NE types.
Dynamic Bandwidth Optimization is adopted for data transfer between FTS application and NEs. This
method implements the possibility to modify the bandwidth according to the reliability of the transmission
channel, in order to reach the best transfer data speed allowed.
Impacted functionality are SW download and MIB restore managed according to the protocol ISO 802.1e
CLNP and over TCP/IP.
8.6.1.2 Functionality
The main features offered by the FT Scheduler are:
scheduling of SWDL jobs.
scheduling of MIB backup jobs.
periodic scheduling of MIB backup Jobs.
Job (SWDL or MIB backup) progress monitoring.
NE SW status retrieving in single or multiple form.
NE SW management.
NE SW status data export.
operation and result logging.
SWDL and MIB backup functionality are offered working simultaneously on a set of NEs.
8.6.1.3 Operational scenario

The managed file transfers are:
SW Download (scheduling services).
MIB backup (scheduling and periodic services).
File Transfer operations are based on the application task named Job". A Job is defined by a Descriptor
File, that contains the list of the target NEs and all the parameters related to the action to be scheduled
(SWDL or MIB Backup).
The Job activation time may be immediate or programmed. In addition, MIB Backup Jobs may be periodically reactivated every 24 hours.
The SW management function allows managing SW versions loaded on the NE. The allowed SW Management commands set depends from the NE SW status and from the functionality supported by the target NE. SW management is allowed on a single NE at a time and it's not scheduled, i.e. commands are
immediately sent to the target NE.
The FTS application allows to retrieve the list of the SW version loaded on all the NEs, with the associated
status. The NEs SW version may be retrieved on single NE or on a set of NEs. Some filters are available
to select subset of NEs. When the SW status is retrieved on a set of NEs is possible to save the result
in an exportable file (ASCII format), useful for external analysis.
Operator Handbook
1353NM-E Rel. 7.4B

347/532
N.B.
MIB backup operation may be implemented differently for different NE types: may be MIB align
up or MIB backup. This document and the FTS, use the operation name MIB backup".
8.6.2 Job Planning

The FTS Scheduling function is based on the information contained into the Job" descriptor file. The Job"
is composed by different sessions, each of one containing a set of NEs.
The same job allows having a priority levels approach in the FTS operation. All the NEs pertaining to a
session are Downloaded / Backedup before the NEs of the next session: the job will start from the
first NE of the first session and will go on, respecting the order of sessions and in each session the order
of NEs. This permits to control the DCN traffic in the network, then the global FT phase can be organized
in order to avoid overloading some specific GNEs or DCN links.
In order to have a good balanced DCN traffic load each LAN node divides the network into two links, each
of one will support, in both sides, quite the same NE number. The FTS application emphasizes the possibility to maintain a reduced DCN load dividing the file transfer load time by sessions (See chapter 8.6.11).
The application launches, for each session, the maximum number of simultaneous file transfer allowed
(<=10 for each involved NM LAN: then the maximum simultaneous file transfer, inside a session, is 10
multiply by the number of involved LAN). When one session terminates, the application launches the next
defined session.
The maximum NE number for any session is 90 but there is no limit regarding the maximum session number in a job.
The DCN traffic load affects the NEs and the network branches involved in the OSNE communication
Considering any NE load equivalent to 1", charging any DCN branch with a balanced load, it can be suggested the following job planning rule:
Distribute the DCN traffic dividing the global traffic load of each branch through different sessions trying to reduce the session numbers: in each session the same network branch will be
passed through by the traffic the minimum number of times.
In a real DCN network, each session will contain NEs belonging to different LANs and the optimum traffic
load for branches will take in account the network communication capacity and the file transfer traffic
between NM and tens / hundred of NEs.
We can reduce the session numbers increasing the LAN load value but the traffic load for branches will
be increased too.
8.6.3 FT Scheduler Job Descriptor

The FT scheduling function is based on the information contained into the Job descriptor" file.
The Job" menu allows to create job descriptor files, to open the existing descriptor files, to show the running job status and the job report.
1353NM-E Rel. 7.4B

348/532
Operator Handbook
Figure 297. Selecting the New Job option from menu

The job editor allows to generate a Job" containing a sequence of Sessions" each one composed of a
set of NEs. The policy of providing different sessions within the same job allows having a two levels
approach in the FT operation. All the NEs belonging to a session are Downloaded / Backedup before
the NEs of the next session: the job will start from the first NE of the first session and will go on, respecting
the order of sessions and in each session the order of NEs. This permits to control the DCN traffic in the
network, then the global FT phase can be organized in order to not overload some specific GNEs or interconnecting DCN links. The maximum NE number for any session is 90" but there is no limit regarding
the maximum session number in a job.
8.6.4 FTS Job Editor

Select the New" job to open Figure 299.and then click on the start button
the new Backup or Download job.
to choose (see Figure 298.)
Figure 298. Job type selection

Click on Yes" or on No" to start editing/building the Backup or the SWDL (Software Download) job.
Operator Handbook
1353NM-E Rel. 7.4B

349/532
Figure 299. New Job creation

The editor job window (see Figure 299.) is composed by two parts: left and right sides. The left side is similar to a tree directory. Here the user creates the job tree selecting, with the mouse button or with the arrow
buttons, the different tree branches. To navigate up/down, to add or delete sessions or NEs click, with the
right mouse button, on the branch and select the menu option (see Figure 300.). The right side window
represents the configuration side to fill in with the required indication.
On the right side enter the mandatory job Name" and the optional Info". Select then Now" or At Time".
Choosing At Time", click on the editing boxes and typing the requested values to introduce Data and Time
of the job activation. A red check sign on the left window will point out a correctly configured branch. Then
the user can go on selecting, with the right mouse button, the new entry data.
1353NM-E Rel. 7.4B

350/532
Operator Handbook
Figure 300. SWDL job: Adding a new Session" example

Select the Add Session" to add a new session item. Then click again, with the right mouse button, to open
the Add NE" menu as shown in Figure 301.
Figure 301. SWDL job: Adding NE equipment

Click again on the new created tree branch (similar to a subdirectory indication), to open the configuration
window shown on Figure 302.
Operator Handbook
1353NM-E Rel. 7.4B

351/532
Figure 302. SWDL package assignment example

In the SWDL window, the NE Label can be filtered choosing the Supervision area" and the NE Type".
If many NEs are managed the filters visualize a restricted NE set in the NE Label field making easier the
required selection.
The selected NE label will be also shown at the left window side as name of the tree branch: the NE detail
will be reported in the related NE detail field accordingly. Depending on the selected server and on the
NE type, the list of available software package will be shown. Then select the package version in the list
to complete the NE SWDL package configuration. If the operator wants to select a SWDL package belonging to another NE Type, he can enter the NE type into the Package Filter" and then, clicking on the Apply
Package Filter" button, choose the NE package. The Apply Package Filter" command can be also used
to perform two other operations:
If a ISA board is equipped into a OMSN, the OMSN software package can be selected by Apply
Package Filter" option to show an enhanced OMSN software package: for example to change the
Software package 650SMC" with the 650SMCE" enter it in the Package Filter and click on the
Apply Package Filter" button.
The same Apply Package Filter" option associated to the CTRL" button can be used to force the
software package list updating in the FT Scheduler editor after a new software package installation.
1353NM-E Rel. 7.4B

352/532
Operator Handbook
Repeat the same Add NE" or Add Session" items to complete the job procedure. At the end the user can
select Submit" to start the SWDL job, Save" to save the job into a file name or close, selecting the Exit"
option to close Job Scheduler Editor menu (see Figure 313.). Note that before submitting a job, all
branches have to be correctly updated, the red check sign indication will appear on every completed item.
The same concepts can be applied to a Backup job but the backup job window is slightly different to the
SWDL one. In Figure 303. is shown a Backup window example. The main differences are the periodic job
and the misalignment flag options.
.
Figure 303. Backup job window example

A periodic backup job is automatically rescheduled every 24 hours selecting At Time" and the Periodic
Job" options. A Backup job assignment example is represented in Figure 304.
Operator Handbook
1353NM-E Rel. 7.4B

353/532
Figure 304. Backup job assignment example

If the Misalignment Flag" is selected the Backup operation on the target NE will be executed only if the
MIB NENM misalignment is detected. This option is available only for those NEs supporting it.
1353NM does not manage Backup Misalignment alarm/Flag for 4G NEs.
1353NM-E Rel. 7.4B

354/532
Operator Handbook
8.6.5 Job editing facilities
Ne selection from Network Map
Instead of from FTS USM, Editor application can be opened by a navigation command from the Network
Map view of the OS: in this case all the valid NEs selected on the Map view are automatically added in
a new SWDL Job.
Figure 305. Ne selection from Network Map
Operator Handbook
1353NM-E Rel. 7.4B

355/532
Ne selection from Ne Software Status Table
FTS allows the selection of a set of NEs inside the NE Software Status Table window and the launch of
the FTS Editor window in order to automatically include the selected NEs in a new SWDL/BKUP Job.
NE Software Status Table window offers sorting facility useful for selecting homogeneous sets of NE.
Select desired NE in the list and then right click the mouse to create the desired kind of job.
Figure 306. Ne selection from NE software Table
Shift" and Ctrl" keys
The FTS Editor application can be started from the FTSUSM main menu in order to create a new job
descriptor or to modify an old one.
The FTS Editor allows selecting several NEs in the Editor window at the same time. The required condition
is that all the NEs to be included belong to the same family.
To define the set of NEs belonging to the same family select, in the left job window, the first NE belonging
to the chosen family and then, pushing on the Shift" key, the last one. All the NEs between the ones chosen will be simultaneously selected, excluding other NE types. In the example of Figure 307.the
1664sm31 NE has been selected identifying the NE family, then the 1641sm28 NE (last available NE) has
been selected, but only the first three NEs, of the same type, have been included in the set.
1353NM-E Rel. 7.4B

356/532
Operator Handbook
Figure 307. Select extension with Shift" key

It is also possible to select different NEs, belonging to the same family, through the Ctrl" key. Choose the
first NE type identifying the NE family, and pushing on the Ctrl" key, select all the other NEs.
In the example of Figure 308.the operator has selected the 1664sm31 NE and then, pushing on the Ctrl"
key, the 1664smR3.2B, 1650 smc1.1ve and 1641sm28 but only the first two NEs have been chosen.
Operator Handbook
1353NM-E Rel. 7.4B

357/532
Figure 308. Select extension with Ctrl" key

On the right side of the job window the user has to choose the common NE software package available
among the software package list. (see Figure 307.and Figure 308.)
1353NM-E Rel. 7.4B

358/532
Operator Handbook
Cut & Paste Editing
To cut one or more job tree branches, select tree branch to cut and click on the Cut" option from the Edit
menu as shown in Figure 309.Apply the Paste" command following the same procedure.
In the examples of Figure 309. and Figure 310.the branch of 1641sm2.7 has been cut from the Pluto"
job and has been pasted on another job descriptor.
Figure 309. Cutting a branch
Operator Handbook
1353NM-E Rel. 7.4B

359/532
Figure 310. Pasting a branch
1353NM-E Rel. 7.4B

360/532
Operator Handbook
8.6.6 Save and Open menu options

Before closing a job window the user can save the created file clicking on the Save" option job window
(see Figure 313.). The first time the Save As" window will be opened and the file name has to be typed
into the bottom editing field (see Figure 311.). Following times the file will be saved without displaying the
Save As" window.
Figure 311. Entering the file name to save

To access the available job list, click on the Open" option of the FT Scheduler editor menu. The same
option can be selected from the FT Scheduler Job" menu (see Figure 297.)
Figure 312. Opening an existing job

Choose the job name from the list as shown in Figure 312. and click on OK" to open File Transfer Scheduler editor window.
To delete the selected job descriptor file select the job name, click the Delete file" command of Figure
313. and then confirm operation clicking on the OK" button.
Operator Handbook
1353NM-E Rel. 7.4B

361/532
Figure 313. Closing the job scheduler

If the SWDL / Backup Scheduler has been opened and a Job" is running, a warning message is displayed
on the screen as shown in Figure 314. The user can check the job current status clicking on the Yes" button of the job running indication window. The same Show SWDL / Backup running job" commands are
also available on the Job" menu option (see 8.6.7).
Figure 314. Job running indication window
1353NM-E Rel. 7.4B

362/532
Operator Handbook
8.6.7 FTS Job Status

The "Show SWDL running job" and "Backup running job" commands are available on the Job" menu
option (see Figure 297.).
The job status gives all the session statuses and single NE procedure values for backup and SWDL (see
Figure 315.):
Green colour indicates that the SWDL procedure has been successfully executed.
Red colour indicates a failed procedure.
Grey colour indicates that the procedure has not been started.
Orange colour indicates the procedure is still running.
On the right window side are reported the selected NE SWDL / Backup details.
Figure 315. Example of job Status

Select the Abort" button to interrupt the SWDL in progress job or the Close" button to close the monitoring
window. From the SWDL / Backup monitoring window the user can open the View Report" window (see
Figure 320.) selecting from the Job" menu, the relative command (see Figure 317.)
Operator Handbook
1353NM-E Rel. 7.4B

363/532
Figure 316. Example of backup job status

Note that in Backup job window the Abort" button is not active selecting the single NE branches.
In the status of job / session / SWDLNE or BackupNE, the following colored icons can be found:
Grey:
Waiting start".
Orange: Activated".
Green:
Operation finished with No Error".
Red:
Operation finished with Errors".
Red with a crossed sign: Aborted" operation.
1353NM-E Rel. 7.4B

364/532
Operator Handbook
Figure 317. Job status and View Report" command

The View report" is described in para. 8.6.9 (on page 368).
Operator Handbook
1353NM-E Rel. 7.4B

365/532
8.6.8 Window Management

Window menu.
All the opened jobs, listed in the Window" menu, can be visualized separately on the SWDL Scheduler
Editor window. Choose the job name and click on it to open the relative window.
Figure 318. List of the job opened
1353NM-E Rel. 7.4B

366/532
Operator Handbook
Arrange Window.
To see more jobs simultaneously on the scheduler editor, select the Multiple Document View" option of
the Arrange Window" menu as shown in Figure 319.
To reduce or enlarge the job window use the two little boxes with the up and down arrows in the title bar;
to close the window use the box with the cross in it.
Figure 319. View of multiple job windows
Operator Handbook
1353NM-E Rel. 7.4B

367/532
8.6.9 View Report

Two View Report options are available: the View SWDL Report" and the View Backup Report". These
view report files can be opened with the relevant options from the job" menu (see Figure 297.) or with
the View Report" commands from the SWDL / Backup job" menu (see Figure 317.)
The View report starts with the beginning data and time of the FT Scheduler Job" and the Job name indication.
Then, for each NE lists, the beginning data and time of the SW Download / Backup", NE name, software
name, software version, software type, Server address (alias named EML Area Domain) and the forced/
not forced SWDL type attribute. It follows, for each NE, the end data and time of the SW Download /
Backup", NE name, SWDL / Backup result and, eventually, the Error indication.
The report terminates with the end data and time of the SW Download / Backup Scheduler Job" and the
summary indication of the SWDL successfully executed and the SWDL failed.
The SWDL report example is shown in Figure 320. while the Backup view report is shown in Figure 321.
1353NM-E Rel. 7.4B

368/532
Operator Handbook
Figure 320. SWDL report window example
Figure 321. Backup report window example

The SWDL / Backup View report can be configured in two different ways:
Adding info in the report file at each job start time: all the SWDL / Backup info will be stored in the
report file appending them to the existing.
Writing a new report file at each job start time: the report file is created new and only the last SWDL
/ Backup info will be stored.
To configure the SWDL / Backup View report, access to the directory:

/alcatel/Kernel/SystemInstances/1353NM_<Inst_number>/swdl/swdlsched/conf,
select the file param.cfg and modify the following parameters:
BCKP_LOG_FILE_REWRITE".
SWDS_LOG_FILE_REWRITE.
in following way:
False" = if the job report file must be created new only if it doesn't exist, at job start time, otherwise
it will be appended.
True" = if the job report file must be created new at each job start time, it will be rewritten each time
that a job starts.
The default values are:
SWDS_LOG_FILE_REWRITE= True";.
BCKP_LOG_FILE_REWRITE= False".
Operator Handbook
1353NM-E Rel. 7.4B

369/532
8.6.10 Software Status

The Software Status menu allows visualizing the NE software status on different modalities: for all NEs,
for NE name and for NE type. The info is retrieved from NEs themselves.
To get the SW Status of all NEs, select the SW Status menu and then All NEs" option.
Note that pointing on every single item of the FT Scheduler menu, a tool-tip showing the command meaning is displayed as shown in the example of Figure 322.
Figure 322. SW Status menu All NEs" option and its tool-tip
The All NEs" option lists the SW Status of all the reachable NEs created on the NM system, independently
of the NE Supervision state, excluding the NEs not managed by the tool as mentioned in the previously
paragraph (see Figure 323.).
Figure 323. NEs SWDL Status

1353NM-E Rel. 7.4B
370/532
Operator Handbook
The NE software package banks are distinguished by the different colour: the first bank is green, the second one is yellow. The selected row becomes light blue.
Clicking on the column names (grey) it is possible to sort rows. The up/down arrow visualizes the increasing/decreasing sorting chosen (by name, by version,...). The Export" command creates a file in CSV
(Comma Separated Value) format with assigned name and path. This type of export file is utilizable by
other applications. Clicking on the Export" button Figure 324.opens.
Figure 324. Export command

Clicking on OK" the file name and path are visualized as shown on Figure 325.
Figure 325. File export characteristic

A similar SW status window can be opened selecting the NE by Type. Depending on the NE number,
defined on the NM system, it is possible to have two different Select By Name" menus. The first one,
shown in Figure 326., represents a menu with a NE list while the second one a menu with the Select one
from list" indication, used to help selection on large number of NEs.
Operator Handbook
1353NM-E Rel. 7.4B

371/532
Figure 326. SW Status selected by name with a NE list menu

The Software Status Details are represented on a double panel. The number with grey background represents the visualized panel while the one, with dark grey background, indicates the hidden panel. Click
on the dark grey background panel to pass from a panel to the other. (Figure 327.shows panel number 1")
Figure 327. NE software status detail

Selecting a Q3NE element the Software Unit Status" button will be enabled while the View Descriptor
File" button will be disable (greyed). Clicking on the Software Unit Status" button Figure 328.opens.
1353NM-E Rel. 7.4B

372/532
Operator Handbook
Figure 328. Q3NE Software unit detail example

N.B.
It should be noted that in the Software Unit detail window the ATM SW package types can be
visualized, as shown in the example of Figure 328..
Some Software Management Action" can be accessed via the NE Software Status Detail Dialog box. The
available actions depend on the NE type and loaded SW Package status. A pull up menu shows the available actions (see Figure 329.). The possible actions are:
None: no action.
Activate: serves to activate the selected software package.
Force: force reactivating of active SW package.
Commit: the selected SW package (the active one) will be activated at NE restart.
Delete: the selected package will be deleted on the NE.
Duplicate: the selected package will be duplicated on the NE.
Operator Handbook
1353NM-E Rel. 7.4B

373/532
Figure 329. Software management action example

When the required action has been selected, click on the Apply Action" button: a confirmation dialog box
is shown before starting the action (see Figure 330.)
Figure 330. Confirmation box window

For the Selected By NE Type" option it is possible to have two similar different menus depending on the
number of NE types. The first one represents a menu with a NE list, the second one with the Select one
from list" indication. Selecting, for example in Figure 331.the 1664 SM, Figure 332.opens.
1353NM-E Rel. 7.4B

374/532
Operator Handbook
Figure 331. SW Status Selected by NE Type with a NE list menu
Figure 332. NE by type SW status
Operator Handbook
1353NM-E Rel. 7.4B

375/532
8.6.11 DCN network example

The DCN examples, here below reported, concern elementary networks with a single LAN and a few NEs.
1353NM
LAN nodes
LAN node
Router
1
Router
2
LAN
5
NE 5
NE 1
NE 2
NE 3
NE 6
NE 4
NE 7
Figure 333. DCN network example

The procedures show how to divide the total DCN traffic without exceeding the suggested optimum traffic
load for branches.
Higher is the LAN load, lower will be the session numbers and viceversa.
1353NM-E Rel. 7.4B

376/532
Operator Handbook
Let us assume, in the examples that follow, the optimum DCN traffic load for branch <=1.
1353NM
Level 1=3
Level 2=2
Level 3=1
Figure 334. Balancing the DCN traffic load

In the example of Figure 334. the link connection between NM and each NE types have been represented:
the traffic in the branch NMNE1 has been balanced with the traffic in the branch NMNE4 but these
branches, in each session, are passed through by the traffic two times and the suggested planning rule
has been disappointed.
Operator Handbook
1353NM-E Rel. 7.4B

377/532
1353NM
Level 1 =4
Router
1
1
Level 3 1
Level 2
1
1
Router
2
LAN
NE 3
NE 4
Level 3 1
5
NE 5
NE 1
NE 2
NE 6
NE 7
Level 4
Figure 335. Optimizing the load traffic for session

In the example of Figure 335., following the suggested planning rule, a LAN load <=4 has been considered
and the job has been divided in the following sessions:
First session: GNE1, GNE2, GNE3 and GNE4.

Second session: NE1, NE2, NE4 and NE6.
Third session: GNE5, NE3, NE5 and NE7.
Fourth session: GNE6.
The link load will be:

Table 20. Link load of level 1 with LAN load max=4
Branch
Session 1
link load
Session 2
link load
Session 3
link load
Session 4
link load
Lan load =
1353NM-E Rel. 7.4B

378/532
Operator Handbook

Branch
Session 1
link load
Session 2
link load
Session 3
link load
Session 4
link load
Router 1GNE1=
Router 1GNE2=
Router 1GNE3=
Router 1GNE4=
The traffic load, in any branch of each session, is <=1 (Table 21.) as suggested in the planning rule.
Branch
Session 1
link load
Session 2
link load
Session 3
link load
Session 4
link load
GNE1NE1 =
GNE2NE2 =
GNE3NE4=
GNE4NE6=
GNE1GNE5=
GNE2NE3=
GNE3NE5=
GNE4NE7=

Branch
Session 1
link load
Session 2
link load
Session 3
link load
Session 4
link load
GNE5GNE6 =
As before the traffic load, reported on Table 22.and Table 23., in any branch of each session, is <=1
The traffic load has been represented dividing the DCN network with different network levels. In Figure
335.the DCN has been divided into 4 levels and the load, in any branch of each session, is minimum (<=1).
Operator Handbook
1353NM-E Rel. 7.4B

379/532
With a higher LAN load it is possible to reduce the session numbers but we can not minimize the traffic
load in any branch of each session.
1353NM
Level 1 =7
Router
1
3
1
1
Router
2
LAN
Level 3 1
Level 2
NE 3
NE 4
Level 3 1
5
NE 5
NE 1
NE 2
NE 6
NE 7
Level 4
1
6
Figure 336. Example of DCN traffic increasing the LAN load

Consider the same DCN network of Figure 333. but with a LAN load <=7: the job could be divided in the
following sessions:
First session: GNE1, GNE2, GNE3, GNE4, GNE5 and GNE6.

Second session: NE1, NE2, NE3, NE4, NE5, NE6 and NE7.
The distribution traffic load, at different network levels, has been visualized in Figure 336.
Branch
Session 1
Session 2
Lan load
1353NM-E Rel. 7.4B

380/532
Operator Handbook

Branch
Session 1
Session 2
Router 1GNE1=
Router 1GNE2=
Router 2GNE3=
Router 2GNE4=
The traffic load, in many branches is >1 (Router1GNE1 of Session1 is =3). That could cause an overloading of the DCN traffic.
Branch
Session 1
Session 2
GNE1NE1=
GNE2NE2=
GNE3NE4=
GNE4NE6=
GNE1GNE5=
GNE2NE3=
GNE3NE5=
GNE4NE7
As before the traffic load, reported on Table 26. in branch GNE1GNE5 of Session1, is >1.
Branch
Session 1
Session 2
GNE5GNE6
Therefore this second job planning does not optimize the network traffic load.
Operator Handbook
1353NM-E Rel. 7.4B

381/532
8.6.11.1 Job Editor

The job planning of is built through the job editor of Figure 337.: the generic NEs have been substituted
by the real ones.
Figure 337. Job editor example
1353NM-E Rel. 7.4B

382/532
Operator Handbook
8.6.11.2 Job Scheduling

A defined job may be executed at the submitted time (option Now") or at programmed time (option At
Time"), in addition, only for MIB backup, can be also chosen At Time" with a Periodic Job" parameter
that allows an automatic MIB backup job activation every 24 hours (see Figure 338.).
Figure 338. MIB backup job example
Operator Handbook
1353NM-E Rel. 7.4B

383/532
Figure 339. Misalignment Flag in the backup job

Moreover in the MIB backup Scheduler editor, the user can select, for each NE, the Misalignment flag"
(see Figure 339.). This flag allows to load (or reload) the MIB backup file only when the MIB misalignment alarm has been recognized, avoiding unnecessary MIB backup operation.
1353NM-E Rel. 7.4B

384/532
Operator Handbook
8.6.11.3 Job Monitoring

During the job running the job status can be checked by the job in progress window (see Figure 340.).
Figure 340. Job in progress status example

The colours icons identify the job status:
grey:
Waiting start"
orange: Activated"
green:
Operation finished with "Success"
red:
Operation finished with "Errors"
red with a crossed sign:Aborted" operation
Operator Handbook
1353NM-E Rel. 7.4B

385/532
8.6.11.4 Job Report

Moreover the FTS application allows programming a SWDL / Backup job not obliging the NM operator
to be present (and awake) during the operation (overnight). A log report is provided to verify how the job
operation worked out (see Figure 341.).
Figure 341. SWDL job report example
1353NM-E Rel. 7.4B

386/532
Operator Handbook
8.6.11.5 NE SW Status Visualization

The FTS allows checking the SW releases currently loaded on the NEs, the running one (active) and the
ones stored in the spare bank of the memory. This operation is possible on a single NE (menu option:
Selected by name), or on a predefined set of NEs of a given type (menu option: Select by NE Type), or
globally on all the managed NEs (menu option: All NEs).
Figure 342. NEs software status table example

The information is retrieved directly from the NEs so that it reflects the current status of the network. The
NE SW Status table, used to show SW Status for a set of NEs, allows to export values in a file for the external analysis.
Operator Handbook
1353NM-E Rel. 7.4B

387/532
8.6.11.6 NE SW Management
A new software package downloaded is stored in the NE standby bank: the activation can be performed
in a second time. The same Figure 343.can be opened with a double click on the selected NE of the software status list or selecting the Select By Name" option from SW Status pull down menu.
Figure 343. Action on NE software package memory banks

NE SW Detail window shows the status of the data loaded in each memory bank of the NE and the allowed
SW Management operation (actions).
The SW Management actions that can be performed on the NE are:
None:
no action.
Activate: to activate the selected software package on the NE.
Force:
Commit: to commit the software package activated on the NE.
Delete:
Duplicate:to duplicate the selected software package on the NE.
to force the selected software package activation on the NE.
to delete the selected software package on the NE.
The SW Management Action list shows the allowed operation depending from the NE SW Status.
1353NM-E Rel. 7.4B

388/532
Operator Handbook
9 System Configuration for Supervision Area

The Supervision Areas is instantiated and configured in the System Configuration GUI; a Supervision Area is not necessarily linked to an OSI Stack.
The new configuration scheme managing:
Pure IP networks without OSI traffic.

IP over OSI tunnelling.
Three types of Supervision Area are possible:
OSI
Linked to a lan card (physical device).
Used by an OSI Stack (i.e. referred to by a Necom Subsystem instance).

IP
Linked to a LAN card (physical device).
Not used by any OSI Stack.

Virtual
Linked to a virtual device.
Not directly linked to any OSI Stack but sharing the same OSI Supervision Area LAN card.
Used for IP over OSI tunnelling.
It is possible to manage:
1)
2)
3)
OSI traffic as usual, by configuring:
An OSI Supervision Area X on a lan card.
An OSI Stack (Necom Subsystem) linked to X.
Any EMLIM referring to X.

IP traffic tunnelled on an OSI network (IPoverOSI), by configuring:
An OSI Supervision Area X on a lan card N.
An OSI Stack (Necom Subsystem) linked to X.
A virtual Supervision Area V on the same lan card N.
An OSI tunnelling process referring to V.
SNMP EMLIMs referring to V.

IP traffic on IP networks, by configuring:
An IP Supervision Area X on a lan card.
SNMP EMLIMs referring to X.
9.1 Supervision Area Configuration

Operator Handbook
System Configuration for Supervision Area
1353NM-E Rel. 7.4B

389/532
Define an OSI (real) supervision area for OSI traffic.
Define a virtual supervision area for IP over OSI tunnel.
Check parameters of an already configured supervision area.
Deconfigure an existing supervision area.
See which supervision area is associated to each component.
9.1.1 Definition of Real Supervision Area

The Supervision Area can be instantiated from the left side of the System Configuration GUI.
Figure 344. Supervision Area Selection in System Configuration

Selecting a Supervision Area instance on the right side, another GUI is displayed. This GUI allows
to define:
The related LAN card.
The Supervision Area logical name.
1353NM-E Rel. 7.4B

390/532
Operator Handbook
Figure 345. Configuration of Supervision Area Parameters

In older NM versions, operations described above were done in the NECOM Subsystem configuration window.
Remark: on selection of a Supervision Area instance in the System Configuration GUI, the operator
is required to confirm its removal before applying it.
Figure 346. Confirmation Dialog before Supervision Area is de-configured

If removal is confirmed, the operator is obliged to modify all instances currently linked to the Supervision Area just removed.
9.1.2 Definition of virtual Supervision Area for IP over OSI Tunnels

A second Supervision Area must be associated to a LAN where another OSI (real) Supervision Area
is already configured. The "StackInterface.txt" file is updated with new Supervision Area.
The 'IP over OSI tunnel' configuration window can be opened only if two supervision Areas (one real
and one virtual) exist and the NECOM component is correctly configured on the real SA.
Operator Handbook
1353NM-E Rel. 7.4B

391/532
9.1.3 How to see parameters already configured for Supervision Area

NM operator may see the parameters already configured for Supervision Area by opening 'Configure
Supervision Area' dialog with right mouse button.
9.1.4 How to safely close 'Configure Supervision Area' dialog box

When opening 'Configure Supervision Area' dialog box for display only, it is necessary to close the
dialog with 'Close' button. In this case, some warning dialogs appear, which have no side effects,
provided that operator does not choose to deconfigure the supervision area.
If the 'Configure Supervision Area' is closed with 'Apply and exit' button, then the
associated NECOM is deconfigured.
There is a restriction on dialog management: check commands fail even if processes are down and
some warning dialogs appear when operator refuses to deconfigure the supervision area.
9.1.5 How to DeConfigure an existing Supervision Area

Supervision Area is deconfigured with the standard procedure but this operation triggers deconfiguration of all existing NECOM instances.
No message is currently displayed to warn the operator that all NECOM instances will be deconfigured if the supervision area is deconfigured.
9.1.6 How to see Supervision Area associated to EMLIM and other components
Operator may choose 'Configure <component>' menu (with right mouse button) and then exit from
dialog with 'Apply and exit' menu.
9.2 OSI Stack (RETIX) Configuration

The OSI Stack (NECOM Subsystem) configuration does not change with respect to previous NM versions: all Supervision Areas are listed for selection.
1353NM-E Rel. 7.4B

392/532
Operator Handbook
Figure 347. Supervision Area selection in OSI Stack configuration
9.2.1 Association of two NECOM components to the same SA

It is impossible to associate more than one NECOM to the same supervision area
but there is no error message that informs the operator that the new Supervision Area is not
correctly configured.
The "StackInterface.txt" is updated with new Supervision Area.
NM operator is responsible of making sure that one and no more than one NECOM is associated
to each OSI Supervision Area.
9.2.2 How to see parameters already configured for NECOM

NM operator may see the parameters already configured for NECOM by opening 'Configure
NECOM' dialog with right mouse button.
9.3 OSI Tunnel Configuration

Operator must choose the desired virtual Supervision Area and then configure the remaining parameters. OSI Supervision Area are not listed for selection.
Operator Handbook
1353NM-E Rel. 7.4B

393/532
Figure 348. OSI Tunnel Configuration
9.4 Q3 EMLIM Configuration

Only OSI Supervision Areas are listed for selection when operator needs to configure a new instance
of Q3 EMLIM.
1353NM-E Rel. 7.4B

394/532
Operator Handbook
Figure 349. Supervision Area selection during Q3 EMLIM configuration
9.5 SNMP EMLIM Configuration

All Supervision Areas are listed for selection, because the final choice depends on the network architecture.
Figure 350. Supervision Area selection during SNMP EMLIM configuration
Operator Handbook
1353NM-E Rel. 7.4B

395/532
9.6 4G EMLIM Configuration

Configuration of supervision area for 4G EMLIM is performed in two different steps.
As a first step the operator needs to select the OSI Supervision Area for Q3 traffic on OSI Stack.
In this case, only OSI Supervision Areas are listed for selection.
Figure 351. Supervision Area selection during 4G EMLIM configuration

After this selection has been done, it is necessary to associate the supervision area for the SNMP
protocol adapter, which should use either an OSI or a Virtual Supervision Area depending on the network architecture.
Two cases are possible:
If no virtual Supervision Areas exists, the whole 4G process group (coordinator, Q3 adapter,
SNMP adapter) is automatically linked to the selected OSI Supervision Area. In this case, operator needs not to select any other supervision area.
If at least one virtual Supervision Area exists, a second window is displayed, which lists both
the selected OSI Supervision Area and all the available virtual supervision area. NM operator
needs to choose one of the displayed supervision areas.
Figure 352. Supervision Area selection for coordinator

The selected Supervision Area applies also to the coordinator.
1353NM-E Rel. 7.4B

396/532
Operator Handbook
9.7 Example
An example of configuration steps follows:
OSI Supervision Area & Stack configuration:
Supervision_Area_0 on lan0.
Necom_SubSystem_0 on SupArea_0.
Virtual Supervision Area configuration:
IP Supervision Area configuration:
Other processes configuration:
ositunnelling_0 on Supervision_Area_2 (for IP over OSI).
EMLIMCORBASNMP on Supervision_Area_2 (for IP over OSI).
EMLIMCORBASNMP on Supervision_Area_1 (for IP networks).
EMLIMADMQ3 on Supervision_Area_0 (for OSI traffic).
Operator Handbook
1353NM-E Rel. 7.4B

397/532
1353NM-E Rel. 7.4B

398/532
Operator Handbook
10 IP over OSI Tunnelling

10.1 Generalities
The aim of introducing new processes in 1353NM System is to pass on IP Addresses, managed by SNMP
EMLIM, over the OSI Stack processes. The figure outlines the new components added to support the
IP over OSI tunnelling function.
Figure 353. IP over OSI new components
Operator Handbook
1353NM-E Rel. 7.4B

399/532
The figure outlines the two different treatments of IP addresses, with and without "ositunnelling" process.
In the first case (on the right of the figure), the IP addresses are treated by OSI processes and on the
OMSN Network Element are processed to decide if the address is of type Q3 or IP and then redirected
to the right agent.
Figure 354. Tunnelling Schema

In the sequel of the document the steps required to setup the tunnelling on OMSN Network Elements using
a dedicated GUI are described.
1353NM-E Rel. 7.4B

400/532
Operator Handbook
Figure 355. Network Setup

The IPoverOSI feature introduced at 1353NM level aims at:
Keeping OSI DCN backbones (no OPSFv2 introduction, no router reconfiguration).
Supporting SNMP traffic to/from ISA Boards with a single endtoend tunnel.
One tunnel per OMSN, fully exploitation of OSI DCN resilience.
Operator Handbook
1353NM-E Rel. 7.4B

401/532
10.2 System Configuration for IP over OSI Tunnelling

10.2.1 System Configuration
In order to be able to setup an IP over OSI Tunnelling operation, 1353NM System should be configured
with processes managing this application.
Starting from TMNOS window, select from menu OS SystemConfig.
The System Configuration window is displayed as shown in following figure:
Figure 356. System Configuration

Select the process ositunneling in the left list and, using the arrow, insert it in the right list. Select
the process in the right list; the parameters window will be displayed as shown in following figure.
1353NM-E Rel. 7.4B

402/532
Operator Handbook
Figure 357. Osi tunnelling Process Parameter Definition

Parameters to be inserted are:
SUPERVISION_AREA: select the virtual supervision area.
OSI_TUN_DEVICE: number of tunnel device to be used, an integer number from 0 to 15.
OSI_TUN_ADDRESS: address assigned to create the tunnel, it should be a unique IP address.
OSI_TUN_GATEWAY: IP address of the default Gateway tunnel (ISA Board Address).
OSI_TUN_NETMASK: Net mask for the tunnel.
Operator Handbook
1353NM-E Rel. 7.4B

403/532
Selecting Actions Apply & Exit the data inserted are saved.
Figure 358. Save inserted data

The modified configuration for the system should be saved to become active. Select from System Configuration main window Main Update Config and wait until the operation has finished.
Figure 359. Update Config Selection

Active parameter settings are saved into the file osi_tun_devconfig_<ip_phisical_supervision_area> in
the directory /usr/Systems/1353NM<instance_nbr>/OSITUN/conf.
In order to complete system configuration open the file /etc/hosts and insert, if not already present, the
line: <ip_address> <virtual_supervision_area_name>.
1353NM-E Rel. 7.4B

404/532
Operator Handbook
10.2.2 Start Configured Process

The new configured process should be started using PMC application. Select, from TMNOS menu:
OS Process Monitoring .
The processes to be started are:
"ositunneling_<n>" in the process group "Stack_Services_<n>".

"OsiManager" in the process group "Osi_Manager".
Figure 360. Start IP over OSI Processes

The IP over OSI tunnelling application is now active on the System.
Operator Handbook
1353NM-E Rel. 7.4B

405/532
On a HPUX terminal run the command netstat rn, you can notice that the addresses insert configuring
the processes appear in the routing tables with the interface set as "du0".
Figure 361. netstat command with osi tunnelling process running

If you stop the process ositunneling_n, automatically the process Osi_Manager stops and if you run
again the command you see that the addresses defined for osi tunnelling process are no more present.
Figure 362. netstat command with osi tunnelling process stopped
1353NM-E Rel. 7.4B

406/532
Operator Handbook
10.3 IP over OSI Tunnelling Setup

10.3.1 Preconditions
The precondition to setup correctly the IP over OSI Tunnelling is that the OMSN Network Element has
already been created and is supervised by 1353NM System.
10.3.2 Operations on OMSN NE

This paragraph describes the operations needed on Network Element side to define the IP over OSI tunnel
completely. Starting from TMNOS window, select:
Actions Topology Manager or the corresponding icon.
On the Topology Manager application select the map with the Network Elements on which the tunnel
should be configured.
Select on the map the NE and the item "Show Equipment" on the popup menu, activated with the right
mouse button.
Figure 363. Show equipment activation
Operator Handbook
1353NM-E Rel. 7.4B

407/532
Figure 364. Network Element USM
10.3.2.1 IP Point to Point

As first operation the IP PointtoPoint configuration should be defined.
Select from the menu:
Configuration Comm/Routing IP Configuration IP Address Configuration of Point
toPoint Interfaces
as shown hereafter:
1353NM-E Rel. 7.4B

408/532
Operator Handbook
Select IP Address
Configuration of
Point-to-Point
Interfaces
Figure 365. PointtoPoint Address Configuration selection

The window to insert the required address is displayed. Insert the address used by the board interfaces.
Figure 366. IP Address for PtoP Configuration
10.3.2.2 IP over OSI Tunnelling Definition

The next operation to do on Network Element side is define the IP over OSI tunnel. From the menu
Configuration Comm/Routing Tunnelling IP over OSI
as shown hereafter:
Operator Handbook
1353NM-E Rel. 7.4B

409/532
Select IP over
OSI option
Figure 367. IP over OSI Selection

The configuration window is displayed to insert the required data.
System Id of NM
related Stack
1353NM-E Rel. 7.4B
410/532
Operator Handbook
Figure 368. IP over OSI Tunnelling Configuration
Operator Handbook
1353NM-E Rel. 7.4B

411/532
10.3.2.3 IP Static Routing Configuration

The next operation to be performed to setup the IP over OSI tunnel is the configuration of the IP static
routing. Select from the menu:
Configuration Comm/Routing IP Configuration IP Static Routing Configuration
as shown hereafter:
Select IP Static
Routing
Configuration
Figure 369. IP Static Routing Configuration Selection

The configuration window is displayed to insert the required data.
1353NM-E Rel. 7.4B
412/532
Operator Handbook
Figure 370. IP Static Routing Configuration
Operator Handbook
1353NM-E Rel. 7.4B

413/532
10.3.2.4 Create ISA Board on OMSN NE

The next operation we perform on the OMSN Network Element is the creation of the ISA board. The ISA
boards should be also already created. Select from the menu bar
Declaration Create ISA
as shown in the figure:
Figure 371. Create ISA board selection

The creation window is displayed to insert the required data.
1353NM-E Rel. 7.4B
414/532
Operator Handbook
Figure 372. Create ISA window
Operator Handbook
1353NM-E Rel. 7.4B

415/532
10.3.3 Operations on 1353NM System

The application is a GUI that allows creating, displaying, modifying and deleting IP over OSI tunnels. This
operation should be done before starting the supervision on the OMSN NE. More ISA boards compose
an OMSN NE. A different tunnel is defined for each OMSN Network Element.
The access to the application is from the TMNOS menu
Actions 1353NMAdmin
The 1353NMAdmin menu is displayed.
Figure 373. IP over OSI Tunnelling selection
1353NM-E Rel. 7.4B
416/532
Operator Handbook
The IP over OSI Tunnelling main window is displayed as shown hereafter:
Figure 374. Tunnel Configuration Application
Operator Handbook
1353NM-E Rel. 7.4B

417/532
10.3.3.1 Create a tunnel on 1353NM System

Select the button <Create> on the displayed window; the creation window is displayed to insert the
required data. The NE list can be filtered by type or name or the whole NE list can be displayed.
Select the desired NE from the list and the type of tunnel needed. Selecting the <Confirm> button, the
tunnel is created for the selected NE. In the main window the updated list is displayed.
Figure 375. Create Tunnel window
1353NM-E Rel. 7.4B
418/532
Operator Handbook
the Added Tunnel
Figure 376. Tunnel configuration list window
Operator Handbook
1353NM-E Rel. 7.4B

419/532
10.3.3.2 Add Network Element on Tunnel

The next operation required is adding an IP NE to the tunnel on OMSN NE previously created. To perform
this operation, select the tunnel on which the IP NE should be added and press the button <Add> in the
"NE IP on Tunnel" part of the window.
Figure 377. Add IP NE on selected Tunnel

The list of available IP NEs is displayed. Select the desired NE from the list and <Confirm> with the button.
1353NM-E Rel. 7.4B
420/532
Operator Handbook
Select the previously

created ISA Board
Figure 378. Add IP NE on Tunnel
10.3.3.3 IP NEs on a Tunnel

The list of IP Network Elements inserted in a tunnel on OMSN NE can be shown selecting the button
<Detail> on the "Tunnel" part of the main window.
Figure 379. Detail Window for a Tunnel

The Information displayed in the detail window are name, address and type of the OMSN Network Element, below is the list of the IP NE added to create an IP over OSI tunnel.
Operator Handbook
1353NM-E Rel. 7.4B

421/532
10.3.4 Start Supervision on ISA Board

Once the previous operations are completed the new created ISA should be supervised to setup the created IP over OSI tunnel. Start from Topology Manager Application, select the ISA board on the map and
on the popup menu select the item "Start Supervision".
Figure 380. Start Supervision on ISA board
10.4 IP over OSI Tunnelling GUI Functions

10.4.1 Remove NE from Tunnel
A previously added Network Element can be deleted from the added IP NE. Select the <Remove> button
in the main window in the "NE IP on Tunnel" part of the window. The window shown in the figure below
is displayed, choose the NE to be deleted and confirm with the button.
1353NM-E Rel. 7.4B
422/532
Operator Handbook
Figure 381. Remove NE from Tunnel
10.4.2 Tunnel Remove

The tunnel created can also be removed. The operation is possible on the main window selecting the
<Remove> button on the "Tunnel" part of the window. A dialog box is displayed to confirm the operation.
Operator Handbook
1353NM-E Rel. 7.4B

423/532
Figure 382. IP over OSI Tunnelling Main Window
Figure 383. Delete Operation Confirm Window
1353NM-E Rel. 7.4B
424/532
Operator Handbook
11 OA512 Management
11.1 Generalities
11.1.1 OmniAccess 512
The Omni Access 512 (OA512) family is a group of stackable switches that offers multiservice access
to an enterprise (WAN) backbone. Designed to connect branch offices to the main office Frame Relay network, this switch combines LAN switching, WAN routing and Service Level MAnagement in a single platform.
The OA512 supports up to two widearea uplinks. Userinstallable USP, T1/E1 and ISDN submodules
provide flexibility. Support of frame relay, leased lines and ISDN offers a broad range of solutions for connecting an enterprise branch office.
11.1.2 References
Table 28. Handbooks related to Omni Access 512 management
REF
HANDBOOK
Part No.
OMNI ACCESS 512

User Manual Release 4.3
03070210 Rev.B
11.1.3 OA512 Integration in 1353NM

1353NM integrates OA512, it is managed as a Network Element.
Operations carried out by 1353NM on OA512 are:
Create OA512 NE starting from Topology Management.
Start/Stop Supervision of OA512.
Show Equipment.
Alarm management.
Operator Handbook
OA512 Management
1353NM-E Rel. 7.4B

425/532
11.1.4 Preconditions for the Integration of OA512 in 1353NM

This paragraph lists some conditions to allow the integration of OA512 in 1353NM Subsystem.
If a global installation is performed, OA512 application is automatically installed, but with partial system installation a selection should be done to install OA512 application.
1353NM Subsystem must be registered on OA512 equipment in order to enable proper operations.
The relevant procedure is explained in a dedicated paragraph.
Alarm/Trap Management: configuration description of the managed traps and the operations to
enable the management on 1353NM is explained in a dedicated paragraph.
1353NM-E Rel. 7.4B
426/532
Operator Handbook
OA512 Management
11.2 1353NM activation

TMN OS is the graphical interface of OSKernel 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 384. Alcatel CDE Front Panel
Select TMN OS icon as shown in the previous figure to start TMN OS application. The TMNOS Management Window will be shown in a few seconds, you have to select the 1353NM instance you want to
manage.
Figure 385. TMN OS application
Operator Handbook
OA512 Management
1353NM-E Rel. 7.4B

427/532
11.3 OA512 Integration

This chapter explains the integration steps to be done in order to manage OA512 starting from 1353NM.
These operations should be done before activating any 1353NM function towards OA512.
11.3.1 OA512 EML Domain

OA512 are supervised by 1353NM Subsystem through SGM (SNMP Generic Mapper) component. This
application allows to manage System using SNMP protocol in a generic way. During System Configuration
phase, this application gets an identification number (EMLIM id). To get this information which is useful
for some operations explained in following paragraphs, select
OS SystemConfig
from TMNOS menu. The following window will be displayed:
EMLIMSGM ID
Figure 386. System Configuration window

During System Configuration the UDP port number is assigned to "EMLIMSGM". This port number should
be greater than 1024 and the operator should take care to assign different port number for different configured EML-IMs. Selecting on the right side of the SystemConfig window 'EMLIMSGM_xxx', the following
window will be displayed:
1353NM-E Rel. 7.4B
428/532
Operator Handbook
OA512 Management
Figure 387. EMLIMSGM Configuration
Operator Handbook
OA512 Management
1353NM-E Rel. 7.4B

429/532
11.3.2 1353NM registration on OA512 System

OA512 should know 1353NM Subsystem in order to be managed by it, the identification of NM on OA
512 System is achieved by the IP address. To define the 1353NM IP address on OA512 follow these
steps (only for Administrator's profile):
open an UX terminal on 1353NM Workstation.
execute the command: telnet <OA512 IP address>.
insert OA512 administrator login and password to be logged into the device.
type the command snmpc, the configuration will be displayed as shown in following figure.
Figure 388. OA512 Coonfiguration
in order to set 1353NM IP address, insert a line n=xxx.yyy.zzz.aaa where n is the number following
the last of the list, xxx.yyy.zzz.aaa is 1353NM IP address; for IP addresses the numbers go from
7 to 16.
the next two prompts ask to insert word 0:1 and word 2:3 for trap configuring, the value to insert are
explained in following paragraph.
the last prompt asks for UDP port number, the UDP port configured for receiving trap; this value is
the value assigned during system configuration procedure and should be read from the window
shown in Figure 387.. This information is reachable starting from SystemConfig window.
1353NM-E Rel. 7.4B
430/532
Operator Handbook
OA512 Management
11.3.3 Configuring trap management

As explained in previous paragraph, trap management can be configured to receive only a subset of the
possible traps. The subset managed by 1353NM is shown in the following table.
Table 29. OA512 Trap management
Trap
Object ID
Description
Bit
Position
Hex Value
coldStart
1.3.6.1.2.1.11.0
The sending protocol entity is re (word 0) 0

initializing itself such that the
agent's configuration or the protocol entity implementation may be
altered
(word 0) 1
warmStart
1.3.6.1.2.1.11.1
The sending protocol entity is re (word 0) 1

initializing itself such that neither
the agent's configuration nor the
protocol entity implementation
may be altered
(word 0) 2
tempAlarm
1.3.6.1.4.1.800. The temperature sensor have (word 1) 0

3.1.1.4.0.1
detected a temperature in the
chassis that exceeds the threshold. These sensors are physically
located on the MPM module, but
can detect temperature changes
throughout the chassis.
(word 1) 1
portLinkUpEvent
1.3.6.1.4.1.800. A physical, logical, or virtual port (word 1) 7

3.1.1.4.0.8
was enabled. These ports may be
enabled through the UI or Switch
Manager. Note that if you enable
a physical port, any associated
logical and virtual ports will also
be enabled. And if you enable a
logical port, such as a WAN service, associated virtual ports will
be enabled.
(word 1) 80
portLinkDownEvent 1.3.6.1.4.1.800. A physical, logical, or virtual port (word 1) 8

3.1.1.4.0.9
was disabled. These ports may
be disabled through the UI or
Switch Manager. Note that if you
disable a physical port, any associated logical and virtual ports will
also be disabled. And if you disable a logical port, such as a WAN
service, associated virtual ports
will be disabled.
(word 1) 100
portPartitioned
(word 1) 200
Operator Handbook
OA512 Management
1.3.6.1.4.1.800. The physical port detected jab- (word 1) 9

ber. Jabber may be produced by a
3.1.1.4.0.10
bad port connection, such as a
faulty cable.
1353NM-E Rel. 7.4B

431/532
The trap is configured in four words (128 bits). The first word (Word 0) contains only standard traps as
they are defined within RFC (MIB) documents. Words 1, 2 and 3 contain Alcatelspecific traps. To set
these traps a sum should be made of the values corresponding to the selected traps.
The trap mask to be entered during the configuration on OA512 is to calculate as follows:
The mask value FFFFFFFF:FFFFFFFF indicates that all traps are enabled for words 0 and 1. Pressing
<Enter> this value is accepted. To configure a subset of traps, you have instead to enter the values in the
following table:
Table 30. Trap Mask Calculation
Trap Type
Bit Settings
Word 0
Word 1
coldStart
00 00 00 01 : 00 00 00 00
warmStart
00 00 00 02 : 00 00 00 00
tempAlarm
00 00 00 00 : 00 00 00 01
portLinkUpEvent
00 00 00 00 : 00 00 00 80
portLinkDownEvent
00 00 00 00 : 00 00 01 00
portParitioned
00 00 00 00 : 00 00 02 00
Total =
00 00 00 03 : 00 00 03 81
The value calculated is the value to be inserted as trap mask in configuring trap management operation.
1353NM-E Rel. 7.4B
432/532
Operator Handbook
OA512 Management
11.3.4 OA152 Network Element Creation

In order to manage OA512 System from 1353NM a new Network Element should be created. The creation of the new Network Element starts from Topology Management (PNM) application, to open the application select from TMNOS menu:
Actions Topology Manager
or pressing the icon
Figure 389. Topology Manager

The map management window will be displayed with the last saved map.
OA512 can be created in a new map or in an already existent map. To create the Network Element select
from the menu
Declaration Create NE...
as shown in following figure.
Operator Handbook
OA512 Management
1353NM-E Rel. 7.4B

433/532
Figure 390. 1353NM Create Network Element

The above selection will display the NE Creation window where the new Network Element data should
be inserted.
1353NM-E Rel. 7.4B
434/532
Operator Handbook
OA512 Management
Figure 391. OA152 NE Creation

Network Element data to insert for the OA512 NE creation are:
NE Family: Omni Access.

NE Type: OA512.
NE Release: 1.0.
User Label: User Label for the Network Element.
Location Name: where the NE is positioned.
Supervision Area: select the lan where the NE is connected.
EML domain: select from the list the domain corresponding to the EML-IM managing OA512. The
EML-IM managing OA512 is EMLIMSGM. The information about the domain can be found in the
System Configuration window.
Operator Handbook
OA512 Management
1353NM-E Rel. 7.4B

435/532
Click on the Apply button to confirm the Network Element creation, the click on the Close button to close
this window.
After the NE creation, the OA512 IP address should be assigned to the new Network Element. To set
the NE address select from the Topology Management menu
Declarations Set Addresses NE Address...
as shown in following figure:
Figure 392. NE Set Address

After the selection a dialog box to insert the IP address is displayed, as shown hereafter
Figure 393. OA512 Set Address
1353NM-E Rel. 7.4B
436/532
Operator Handbook
OA512 Management
After this operation, the Network Element creation is completed.
11.3.5 Security
Security is not managed by 1353NM for OA512. This means basically that users of any profile are enabled
to open the OA512 specific application and perform all available operations on the switch.
11.3.6 OA512 Network Element Supervision

After the creation, a Network Element should be supervised by 1353NM Subsystem in order to be managed by the Network Management system. Select from menu
Figure 394. NE Supervision

To start the supervision click on the button Apply and wait for the operation to finish, then click on the button Close to exit.
Operator Handbook
OA512 Management
1353NM-E Rel. 7.4B

437/532
Figure 395. Start Supervision
1353NM-E Rel. 7.4B
438/532
Operator Handbook
OA512 Management
11.3.7 Navigation from 1353NM Topology Management to OA512 USM

Once OA512 is supervised, navigation to the native OA512 management application (XVision) is
allowed selecting from the popup menu the Show Equipment" option.
Figure 396. NE Show Equipment

This operation opens OA512 user interface as shown in following figure.
Figure 397. OA512 User Interface

For details on OA512 see Omni Access 512 User Manual".
Operator Handbook
OA512 Management
1353NM-E Rel. 7.4B

439/532
The contents and set of operations available with XVision are not part of the present manual. Please refer
to [2] for a detailed description of the application.
11.3.8 Ping NE
A useful function to test the OA512 NE availability from 1353NM is the Ping NE" function. Select the
OA512 NE on the map, select from the menu
Operations Ping NE.
The operation's result will be displayed after a few seconds as shown in following figure:
Figure 398. Ping NE result
1353NM-E Rel. 7.4B
440/532
Operator Handbook
OA512 Management
11.4 Alarm management

Alarms are managed by a generic component called AS (Alarm Surveillance) integrated in the common
platform OSKernel and can be activated from TMNOS menu. For OA512 a subsystem of traps is managed and can be see using AS USM. Starting from TMNOS menu the main AS USM window is displayed
as shown in following figure. This list contains all the alarms received.
Figure 399. Main Alarm List

OA512 managed alarms are shown by AS in realtime. To allow realtime management a particular
alarm OA512 New Event" is used which is suggested to be configured for auto-purging from AS administration facilities. The auto-purge action is associated to the OA512 New Event" Probable Cause. The
alarm is not registered in the Current Alarm List, but in the Historical Alarm List.
Operator Handbook
OA512 Management
1353NM-E Rel. 7.4B

441/532
The auto-purge action is configurable with AS component. Selecting from the summary alarm window
Options Administration 1353NM_<Inst_numb>
Figure 400. AS Administration Selection

The administration window is displayed. To activate the autopurge action on the Probable Cause OA512
New Event", select the button near 'Probable Cause' and select the string from the displayed list, as shown
in following figure.
1353NM-E Rel. 7.4B
442/532
Operator Handbook
OA512 Management
Figure 401. Probable Cause List Selection

Select the Probable Cause on the left list and then press the arrow button to take it on the 'Selected Probable Causes' list. Use the 'OK' button to confirm the selection.
Operator Handbook
OA512 Management
1353NM-E Rel. 7.4B

443/532
Figure 402. AS Administration

The selection is stored in the main administration window, to confirm the option press the 'Apply' button.
1353NM-E Rel. 7.4B
444/532
Operator Handbook
OA512 Management
11.4.1 Navigation from AS to OA512 USM

Starting from the main alarm list window it is possible to navigate to OA512 USM selecting
Navigation External Application Related EmlUsm.
Each time a navigation is selected a new OA512 USM window will be opened.
Figure 403. Navigation to OA512 USM

Selecting the above navigation the OA512 USM is displayed.
Figure 404. OA512 USM
Operator Handbook
OA512 Management
1353NM-E Rel. 7.4B

445/532
11.4.2 Navigation from Topology Management to AS USM

On the other side it's possible to navigate from Topology Management, selecting OA512 Network Element, to AS USM displaying the alarm's sublist concerning OA512 alarms.
Figure 405. Navigation to AS USM

Selecting the option 'Show alarms' the list of OA512 alarms will be displayed.
1353NM-E Rel. 7.4B
446/532
Operator Handbook
OA512 Management
Figure 406. OA512 Alarms Sublist
Operator Handbook
OA512 Management
1353NM-E Rel. 7.4B

447/532
1353NM-E Rel. 7.4B
448/532
Operator Handbook
OA512 Management
12 1353NMSE Management
12.1 Product overview
12.1.1 SAN Extender 169xSE
1693SE and 1696SE are high performance gateway that interconnects SAN islands using readily available fiber optic infrastructure such as SONET, DWDM or dedicated fiber.
169xSE" refers to two different products in Alcatel catalogue:
1693SE.
1696SE.
1693 SAN Extender is a switching gateway providing seamless bidirectional integration of Fibre Channel
(FC) and Gigabit Ethernet (GbE) networks over long distances without disruption or technology changes.
1696 SAN Extender enables the extension of Storage Area Networking over distances of up thousands
of kilometers. It is specifically designed for applications that are critically dependent on dedicated and
highly reliable long distance connectivity, such as disaster recovery, remote site backup, and datacenter
to datacenter sharing.
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

449/532
Figure 407. NMSE in TMN Architecture

With the ever increasing volumes of storage, today's enterprise is rapidly adopting the Storage Area Network (SAN) as the foundation for a scalable, high performance storage system.
SANs are typically built on Fibre Channel (FC) which provides a high bandwidth, low latency fabric for
interconnecting servers and storage devices.
Storage System Integrators have to come to rely on this high level of performance within the Data Center.
The challenge is to interconnect multiple Data Centers without sacrificing performance.
1353NM-E Rel. 7.4B
450/532
Operator Handbook
1353NMSE Management
Figure 408. Remote SAN interconnection
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

451/532
12.1.2 References
Table 31. Handbooks related to 169xSE management
REF
[1]
HANDBOOK
Part No.
1353NMSE Network Manager for SAN Extender
12.1.3 SAN Extender 169xSE Integration in 1353NM

1353NM integrates 169xSE, it is managed as a Network Element.
Operations carried out by 1353NM on 169xSE are:
Create 169xSE NE starting from the Topology Viewer.
Start/Stop Supervision of 169xSE NE.
Show Equipment.
Alarm management.
12.1.4 Preconditions for the Integration of 169xSE in 1353NM

This paragraph lists some conditions to allow the integration of 169xSE in 1353NM Subsystem.
If a global installation is performed, 1353NMSE application is installed on 1353NM, but with partial
system installation a selection should be done to install 1353NMSE application.
1353NM Subsystem must be activated by GoGlobal application from a PC where 1353NMSE client application is installed. If this condition isn't verified the 'Show Equipment' command doesn't open
the NE USM.
To achieve a correct installation and integration of 169xSE follow the procedure described in paragraph 12.2 for the Client installation, the Customization of the NMSE Server and setting the parameters for the registration of the traps on 1353NM Subsystem.
1353NM-E Rel. 7.4B
452/532
Operator Handbook
1353NMSE Management
12.2 Installation of 169xSE Client Application

12.2.1 Installation Requirements
The NMSE software has two separate applications: Server and Client. The Server should be installed on
a dedicated Windowscompatible PC. It is recommended to have at least 3 Gigabytes of free disk space
on the Server PC for collecting monitoring data from all switches managed by NMSE.
The NMSE Client application should be installed on a user PC which will also have Alcatel's Go Global
remote terminal application installed. The NMSE Client works in conjunction with Go Global to provide
management and monitoring capabilities for SAN Extender switches. The suggested configuration for the
Client PC is as follows:
Table 32. Suggested configuration for the Client PC
Component
Minimum Requirement
Processor
Pentium III, 850 MHz CPU
RAM
256 MB
Hard Drive
10 Gb
CDROM Drive
24x
Operating System
Windows XP Professional
Monitor
1024 / 768 256 colours, small fonts
Multiple instances of the Client application can be installed in the management network, communicating
with the same NMSE Server application.
Installation of more than one NMSE Server on the same management subnet is not recommended. Multiple servers may cause difficulties in logging, performance monitoring
and time synchronization.
To install the NMSE Server or Client, use the CD supplied with the SAN Extender (1693SE or 1696SE)
or the selfextractable file downloaded from Alcatel's software support directory. Run the setup application, which has several screens. When the Mode Selection screen appears (Figure 409.), choose Client
or Server to be installed, then click Next.
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

453/532
Figure 409. Install Wizard Mode Selection Screen
12.2.2 Installing the Server

On the NMSE Server station, also called the Master Platform, start the setup application as described
above. In the Install Wizard screen, choose the Server application, then click Next.
No further inputs are required. Once the installation process has completed, the NMSE Server application
can be activated in the following ways:
In the final screen of the installation process, check Yes, Launch the program file, then click Finish.
Or
Launch the application as a standard Windows program, from the following menu path:
Start Programs 1353SE
After installation, the Server will need to be customized in order to register it within the Network Manager
framework, restrict access, define network elements, configure encryption, and manage the database.
The customization procedure is described in paragraph "12.3: Customizing the NMSE Server" on page
455.
1353NM-E Rel. 7.4B
454/532
Operator Handbook
1353NMSE Management
12.2.3 Installing the Client.

On the client PC, which has already had Go Global installed, start the setup application as described
above. In the Install Wizard screen, choose the Client application, then click Next.
No further inputs are required. Once the installation process has completed, the NMSE Client application
can be activated in the following ways:
In the final screen of the installation process, check Yes, Launch the program file, then click Finish.
Or
Launch the application as a standard Windows program, from the following menu path:
Start Programs 1353SE
After rebooting the system, the NMSE Client will start automatically.
When the Client application starts up, it activates the SUS (Startup Service). The SUS icon will be placed
into the system tray. The management and monitoring windows of the NMSE Client will be activated later
by actions in the Go Global application.
Detailed operating instructions for the NMSE Client are given in document [1].
12.3 Customizing the NMSE Server

After installation, the NMSE Server must be customized in order to register it within the Network Manager
framework, restrict access, register network elements, configure encryption and manage the database.
12.3.1 Registering NMSE in the NM Framework

The NMSE Server is registered in the NM framework by a root user. The user must edit the NM Server's
/etc/hosts file to add a line of the following format:
<NMSE IP address> <NMSE server name> # SanServer
For example:
151.98.28.33 PCSan # SanServer
Note that "# SanServer" is a required string, not a parameter.
After this addition is made, the NMSE Server station can be recognized and contacted by the NM system.
12.3.2 Defining Users

In order to limit application access to authorized users, the NMSE operator defines a list of users and their
access privilege levels in the "users.ini" file located in the root directory of the 1353NMSE application.
This list works as an additional security level to the regular SNMP community definitions. The access list
must conform to the main 1353NM Server authentication policy.
The two access privilege levels are Read/Write (RW) and Read Only (RO). RW allows full administrator
level access to the managed switches. A user with RW access can configure, upgrade and monitor
switches. RO privilege allows only monitoring of the managed switches.
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

455/532
To add, delete or change users, the operator manually edits the "users.ini" file. The default user is alcatel
(casesensitive) with access level set to RW. (This default user is predefined and is not included in the
"users.ini" file.)
Example. The contents of the "users.ini" file after installation shows one user (SuperUser) defined with
privilege level of RW. Lines beginning with ";" are comments only, showing possible users and privilege
levels that can be defined.
;[ALL]
;Acc=RO
[SuperUser]
Acc=RW
;[User]
;Acc=RO
Example. Two new users are added to the file: Tornado with RW access, and Storm with RO access:
[Tornado]
Acc=RW
[Storm]
Acc=RO
12.3.3 Registering Network Elements in the NM Framework

A network element (NE) is a switch in the network being managed by the 1353NM Framework. SAN
Extenders of the 1693SE and 1696SE families can be created as managed NEs in the 1353NM list so
that they will be considered nodes in the SAN. In the Topology Viewer Application (TVA) window, open
the Declarations menu, then select Create NE. Please refer to paragraph 12.1 in this chapter for more
information.
12.3.4 Registering Network Elements in NMSE

Switches supported by NMSE include all models of the Alcatel 1693SE and 1696SE families of SAN
Extenders. In addition, some models from other vendors can be partially supported, depending on the
SNMP MIBs they have implemented. For example, Brocade's (or OEM Brocade's) Fibre Channel
switches are supported and can be managed using most common commands from the NMSE Client.
Each supported NE (switch) must have at least one management interface configured. Parameters
include IP address, network mask, default gateway IP address, SNMP community, permitted users and
their profiles.
A switch must be registered in the NMSE Server's list of network elements before it can be managed by
the NMSE application. It is recommend that all switches managed by the 1353NM Server also be registered in the NMSE Server's list. Use the NMSE Server Main Window (Figure 410.) to add, change or delete
switches.
1353NM-E Rel. 7.4B
456/532
Operator Handbook
1353NMSE Management
Figure 410. Server Main Window
colourcoded switch icons: the Tree View shows a list of switches in the SAN, with status indicated
by the following icon colours:
Red: switch has been defined in the SAN but is not physically connected.
Green: switch is defined in the SAN, there is a good connection, and the switch is fully under
SNMP control.
Blue: switch has unknown communication status.
Yellow: switch can be seen in the SAN but there is no direct communication (no ping). There
is FC inband communication.
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

457/532
12.3.5 Adding Switches to the Server's List

A switch can be added to the Server's list even if it is not yet physically connected to the network, or if
its status prevents it from communicating.
1)
Right click the SAN (globe) icon in the Workspace Tree. A popup menu appears.
2)
Select Add Switch. The Add Switch window appears (Figure 411.).
Figure 411. The Add Switch Window

3)
Enter the IP Address.
4)
The Switch Name parameter is optional and has the following limitations:
No spaces.
Maximum 31 characters.
First character must be alphabetic.
5)
Set the SNMP Community to the value that has been set for the network element's SNMP agent
community. The SNMP community and "users.ini" file together define the users and privileges
for the particular NE.
6)
Click OK.
7)
Click Advanced in the Add Switch window. The window is displayed.
1353NM-E Rel. 7.4B
458/532
Operator Handbook
1353NMSE Management
Figure 412. Advanced Options for Adding Switches

NOTE: It is recommended not to enter the switch name, in order to avoid switch name conflicts. If the
switch is connected to the network, the NMSE Server will autodetect the switch name and display it after
the other data has been entered.
8)
Enable (check) or disable (uncheck) Polling. If enabled, Polling interval specifies how frequently (in seconds) statistics and status data are collected from the switch. Statistics storage
rate specifies (in minutes) the resolution of data that will be stored in the database.
9)
Enter the Switch Parameters: WWN, Number of ports and Domain ID. These parameters cannot be determined automatically if the switch is not yet physically connected or cannot communicate. (Where zoning is supported, a predefined switch can be used in zoning strategy
once these parameters have been defined).
To delete a switch:
Rightclick on the switch, and select Delete from the popup menu.
To modify the properties of an existing switch:
Rightclick on the switch, and select Properties from the popup menu.
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

459/532
12.4 Managing the Database

The NMSE Server application collects data from all managed network elements and automatically saves
the data to multiple databases located on the NMSE Server PC.
There are three types of databases:
Statistics Database: keeps full statistical information for all managed network elements,
including number of transmitted and received frames and bytes for the whole switch and for
each port; error counters; and other statistics.
Traps Database: keeps history of all alerts generated by all managed network elements.
Logs Database: accumulates operation logs for managed network elements.
To specify the size and location of these databases:

1)
In the NMSE Server Main Window, open the Options menu and select Options. The Options
window appears. Select the Statistic tab (Figure 413.).
Figure 413. Options Window, Statistic Tab

2)
Specify the Size of the database file (in Megabytes). The default is 50. Once a file reaches this
size it will be archived on the local hard drive and a new file will be opened.
3)
Specify the Number of database files. This is the maximum number of files that will be created
for each type of database. The default is 10.
4)
Click OK.
5)
Select the Folders tab. Set the file path for the location of database files on the local hard drive.
6)
Click OK.
1353NM-E Rel. 7.4B
460/532
Operator Handbook
1353NMSE Management

physical machine.
TMN OS Icon
manage.
Figure 415. TMN OS application
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

461/532
12.6 169xSE Integration

This chapter explains the integration steps to be done in order to manage 169xSE starting from 1353NM.
These operations should be done before activating any 1353NM function towards 169xSE.
12.6.1 Steps sequence to manage 169xSE NEs
Installation of 1353NMSE Client application on the Personal Computer from which the operator performs the remote connection to 1353NM platforms via GOGlobal.
1353NMSE Server station shall be known to 1353NM Master platform and reachable via IP
networking. The simplest way to achieve IP connectivity is declaring 1353NMSE Server into
/etc/hosts file. Root user can edit the file and add following line:
<SANman IP address> <SANman server name> #SanServer
N.B.
The comment # SanServer" is not an optional but a mandatory string> It cannot be

omitted. E.g. 151.98.28.33 PCScan #SanServer.
1353NM-E Rel. 7.4B
462/532
Operator Handbook
1353NMSE Management
12.6.2 169xSE EML Domain Configuration

Once the installation steps are completed, System Configuration phase should be started to configure
EMLIM to manage 169xSE NEs.
169xSE are supervised by 1353NM through SGM (SNMP Generic Mapper) component. During System
Configuration phase, this application gets an identification number (EMLIM id).
To configure the application select from TMNOS menu:
OS SystemConfig
The following window will be displayed.
EMLIMSGM ID

During System Configuration the UDP port number is assigned to EMLIMSGM subsystem.
This port number should be greater than 1024 and the operator should take care to assign different port
number for different configured EMLIMs.
Selecting on the right side of the SystemConfig window 'EMLIMSGM_xxx', the following window will be
displayed.
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

463/532
Insert a port number greater than 1024 and select

Actions Apply&Exit
Figure 418. Configuration data confirmation
1353NM-E Rel. 7.4B
464/532
Operator Handbook
1353NMSE Management
12.7 169xSE San extender Management

12.7.1 169xSE Network Element Creation
In order to manage 169xSE from 1353NM a new Network Element should be created. The creation of the
new Network Element starts from Topology Management application, to open the application select from
TMNOS menu
or pressing the icon
.
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

465/532
The map management window will be displayed with the last saved map. 169xSE can be created in a new
map or in an already existent map. To create the Network Element select from the menu |

be inserted.
1353NM-E Rel. 7.4B
466/532
Operator Handbook
1353NMSE Management
Figure 421. 169xSE NE Creation

Network Element data to insert for the NE creation are:
NE Family: SAN family.

NE Type: 169xSE.
NE Release: 1.0.
User Label: User Label for the Network Element. The first symbol of the name must be a letter. The
current implementation of SANman does not allow to include the following characters into NE name:
~ ! @ # $ % ^ & * () _ + = < > ? / , ' ; \ " : \\ [ ] { } and space.
Location Name: where the equipment is installed.
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

467/532
Supervision Area: identifies the LAN card of the 1353NM Master platform (HP server) through which
the management traffic to/from 169xSE shall go through, according to the DCN design. In case
1353NM Master is equipped with one LAN Card for NE management channels, no selection
requested to endusers.
EML domain: it identifies the Manager process instance in charge of direct interworking with the NE
SNMP agent; no user selection let 1353NM automatically choose the proper SNMP Manager
instance according to load balancing criteria. Select from the list the domain corresponding to the
EMLIM managing 169xSE. The EMLIM managing 169xSE is EMLIMSGM. The information about
the domain can be found in the System Configuration window.
ACD: it identifies a given network domain, applicable just in case the global network under 1353NM
supervision is securely partitioned to split the management responsibility to different users.
Click on the Apply button to confirm the Network Element creation, the click on the Close button to close
this window.
Once the 169xSE equipment is created into the 1353NM Global Inventory and is available to be inserted
into the Network Maps.
After the NE creation, the 169xSE IP address should be assigned to the new Network Element. To set
the NE address select from the Topology Management menu as shown in following figure.

After the selection a dialog box to insert the IP address is displayed, as shown hereafter:
1353NM-E Rel. 7.4B
468/532
Operator Handbook
1353NMSE Management
Figure 423. 169xSE Set Address

12.7.2 Security
Security is not managed by 1353NM for 169xSE NE. This means basically that users of any profile are
enabled to open the specific application and perform all available operations on the switch.
12.7.3 169xSE Network Element Supervision

After the creation, a Network Element should be supervised by 1353NM Subsystem in order to be managed by the Network Management system. Select from menu
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

469/532

1353NM-E Rel. 7.4B
470/532
Operator Handbook
1353NMSE Management
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

471/532
12.7.4 Navigation from 1353NM Topology Management to USM

Once 169xSE is supervised, navigation to the SANman management application is allowed selecting from
the popup menu the Show Equipment" option.

This operation opens the user interface as shown in following figure.
1353NM-E Rel. 7.4B
472/532
Operator Handbook
1353NMSE Management
Figure 427. 169xSE USM
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

473/532
12.7.5 Navigation to SANman application

From TMNOS it is possible to activate SANman application selecting the dedicated icon as shown in following figure:
Figure 428. Open SANman application from TMNOS selecting icon
Figure 429. Open SANman application from TMNOS selecting menu Actions
Selecting the highlighted icon in the figure or TMNOS menu
Actions Open 1353NMSE Map
the application main window is displayed where all the managed SAN equipment are displayed in the
resource tree.
1353NM-E Rel. 7.4B
474/532
Operator Handbook
1353NMSE Management
Figure 430. User Interface

The contents and set of operations available with application are not part of the present manual. Please
refer to [1] for a detailed description of the application.
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

475/532
12.7.6 Ping NE
A useful function to test the 169xSE NE availability from 1353NM is the Ping NE" function. Select the
169xSE NE on the map, select from the menu:
Operations Ping NE.
The operation's result will be displayed after a few seconds as shown in following figure.
1353NM-E Rel. 7.4B
476/532
Operator Handbook
1353NMSE Management

platform OSKernel and can be activated from TMNOS menu.
For 169xSE a subsystem of alarms is managed and can be seen using AS USM. Starting from TMNOS
menu the main AS USM window is displayed as shown in following figure.
This list contains all the alarms received.
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

477/532

The administration window is displayed.
1353NM-E Rel. 7.4B
478/532
Operator Handbook
1353NMSE Management
Figure 434. AS Administration Window
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

479/532
12.8.1 Navigation from AS to 169xSE USM

Starting from the main alarm list window it is possible to navigate to SANman USM selecting:
Each time a navigation is selected a new SANman USM window will be opened.
Figure 435. Navigation to SANman application
1353NM-E Rel. 7.4B
480/532
Operator Handbook
1353NMSE Management
Selecting the above navigation the 169xSE USM is displayed.
Figure 436. 1353NMSE Alarms List
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

481/532

1353NM-E Rel. 7.4B
482/532
Operator Handbook
1353NMSE Management
Selecting the option 'Show alarms' the list of 169xSE alarms will be displayed.
Figure 438. 169xSE Alarms Sublist
Operator Handbook
1353NMSE Management
1353NM-E Rel. 7.4B

483/532
1353NM-E Rel. 7.4B
484/532
Operator Handbook
1353NMSE Management
13 1615BCE Management
13.1 Product overview
13.1.1 SHDSL SYSTEM
The SHDSL transmission system allows the transmission of a 2048 Kbit/s data stream over one or two
symmetrical pairs between two units, known as the Line Termination Unit (LTU) and the Network Termination Unit (NTU).
LTU termination is called "Central Office equipment" as usually located in the urban exchanges of the telephone network; NTU is the user termination, also called "Remote Equipment".
Figure 439. SHDSL System

The bidirectional transmission on one line only has been achieved thanks to the echo cancellation.
The transmission capacity of SHDSL line is variable. The payload can generally vary from 192 to 2304
kbit/s (higher bit rate can be available depending on the provided software release). Using an
G.703 E1 network interface, the maximum payload decreases to 2048 kbit/s.
In this case, with the transmission over 2 wires, the transmission capacity of SHDSL line is 2056 kbit/s,
equal to 32 time-slots of payload plus a transmission overhead. In case of transmission over 4 wires, the
time slots present on the G.703 E1 interface are divided on the two SHDSL pairs.
The even time slots are set over a pair (0, 2, 4, ) and the odd time slots on the other pair (1, 3, 5,...)
Higher bit rates (up to 4608 Kbit/s) are reachable connecting two terminals with V.36 interface.
This configuration can be reached through proper software versions.
Operator Handbook
1615BCE Management
1353NM-E Rel. 7.4B

485/532
13.1.2 1615BCE
"1615BCE" is the name assigned to the SHDSL Line Terminal Box. In the SHDSL environment the LT is
the only equipment modelled and considered at TMN level: the SHDSL Network Terminations installed
in Customer premises and connected to the LT through the copper pairs are running SW agents directly
under control of the LT, not directly visible to the EMS. Any information/function related to NTs is reported
or conveyed through the LT (1615BCE in this case) to the 1353NM.
From the management with 1353NM Subsystem perspective, 1615BCE is a node equipped with following
modules/boards:
UAplus" module running the SNMP agent, where the equipment alarm information (APT =
Active Problem Table) are stored. UAplus is in charge to keep the Alarm DB updated with the
status of the different modules supporting locally/remotely services over SHDSL and to properly manage the alarm information towards 1353NM, in terms of spontaneous notifications
(traps) and retrieval/resynchronization methods against the APT.
Uaplus also runs the http daemon offering the WEB pages containing alarm synthesis info and
menu options able to launch telnet sessions against the I/O modules (SNT+/SNTHD) of interest.
"SNT+" module, terminating the copper pairs, supporting the Ethernet services.
SNTHD" module, terminating the copper pairs, supporting the E1 services.
In case of 1615BCE multishelf configuration (up to 4 in daisy chain), there is a UA+ module per subrack,
each one managing its own APT and local HW resources.
This means any subrack is represented and managed as a separate NE in 1353NM.
13.1.3 References
Table 33. Handbooks related to 1615BCE management
REF
HANDBOOK
Part No.
[1]
User Manual SNTPlus
720014000A0LM
[2]
General Technical Description
723014002A0GB
13.1.4 1615BCE Integration in 1353NM

1353NM integrates 1615BCE it is managed as a Network Element.
Operations carried out by 1353NM on 1615BCE are:
Create 1615BCE NE starting from PNM.
Start/Stop Supervision of 1615BCE NE.
Show Equipment.
Alarm management.
1353NM-E Rel. 7.4B
486/532
Operator Handbook
1615BCE Management
13.1.5 Preconditions for the Integration of 1615BCE in 1353NM

This paragraph lists some conditions to allow the integration of 1615BCE in 1353NM Subsystem.
1353NM NTP Server Configuration.
Please refer to the "1350 NR7.1 PL1 INSTALLATION GUIDE" (3AL 88893 BAAA), Chapter 6.2 "Synchronize the Clocks".

physical machine.
TMN OS Icon
manage
Figure 441. TMNOS Application

Operator Handbook
1615BCE Management
1353NM-E Rel. 7.4B

487/532
13.3 1615BCE Integration

This chapter explains the integration steps to be done in order to manage 1615BCE starting from 1353NM.
These operations should be done before activating any 1353NM function towards 1615BCE.
13.3.1 1615BCE EML Domain Configuration

1615BCE are supervised by 1353NM Subsystem through SGM (SNMP Generic Mapper) component.
This application allows managing System using SNMP protocol in a generic way. During System Configuration phase, this application gets an identification number (EMLIM id). To get this information, which
is useful for some operations explained in following paragraphs, select from TMNOS menu:
OS SystemConfig,
The following window will be displayed:
EMLIMSGM ID

During System Configuration the UDP port number is assigned to EMLIMSGM. This port number should
be greater than 1024 and the operator should take care to assign different port number for different configured EML-IMs. Selecting on the right side of the SystemConfig window 'EMLIMSGM_xxx', the following
window will be displayed:
1353NM-E Rel. 7.4B
488/532
Operator Handbook
1615BCE Management

Following parameters should be configured:
SUPERVISION_AREA: associate the EmlimSgm to the right LAN.
UDP_PORT: the UDP_PORT number parameter should be a number greater than 1024.
To confirm the selected parameters pull down the menu "Action" and select "Apply & exit".
Figure 444. Configuration data confirmation
Operator Handbook
1615BCE Management
1353NM-E Rel. 7.4B

489/532
13.4 1615BCE Management

13.4.1 1615BCE Network Element Creation
In order to manage 1615BCE from 1353NM a new Network Element should be created. The creation of
the new Network Element starts from Topology Management application, to open the application select
from TMNOS menu:
or pressing the icon .

The map management window will be displayed with the last saved map. 1615BCE can be created in a
new map or in an already existent map. To create the Network Element select from the menu:
1353NM-E Rel. 7.4B
490/532
Operator Handbook
1615BCE Management

be inserted.
Operator Handbook
1615BCE Management
1353NM-E Rel. 7.4B

491/532
Figure 447. 169xSE NE Creation

Network Element data to insert for the 1615BCE NE creation are:
NE Family: GSDHSL.
NE Type: 1615BCE.
NE Release: 1.0.
User Label: User Label for the Network Element.
Location Name: where the NE is positioned.
Supervision Area: select the LAN where the NE is connected.
EML domain: select from the list the domain corresponding to the EMLIM managing
1615BCE. The EMLIM managing 1615BCE is EMLIMSGM. The information about the domain
can be found in the System Configuration window.
1353NM-E Rel. 7.4B
492/532
Operator Handbook
1615BCE Management
Click on the Apply button to confirm the Network Element creation and then click on the Close button to
close this window.
After the NE creation, the 1615BCE IP address should be assigned to the new Network Element.
To set the NE address, select
from the Topology Management menu as shown in following figure.
Once the 169xSE equipment is created into the 1353NM Global Inventory and is available to be inserted
into the Network Maps.
After the NE creation, the 169xSE IP address should be assigned to the new Network Element.
To set the NE address select
from the Topology Management menu as shown in following figure.

After the selection a dialog box to insert the IP address is displayed, as shown hereafter:
Operator Handbook
1615BCE Management
1353NM-E Rel. 7.4B

493/532
Figure 449. 1615BCE Set Address

13.4.2 Security
Security is not managed by 1353NM for 1615BCE. This means basically that users of any profile are
enabled to open the 1615BCE specific application and perform all available operations on the switch.
The only restriction is a password to enter the application navigating from 1353NM Subsystem.
1353NM-E Rel. 7.4B
494/532
Operator Handbook
1615BCE Management
13.4.3 1615BCE Network Element Supervision

After the creation, a Network Element should be supervised by 1353NM Subsystem in order to be managed by the Network Management system.
Select from menu:

Operator Handbook
1615BCE Management
1353NM-E Rel. 7.4B

495/532
1353NM-E Rel. 7.4B
496/532
Operator Handbook
1615BCE Management
13.4.4 Navigation from 1353NM Topology Management to USM

Once 169xSE is supervised, navigation to the SANman management application is allowed selecting from
the popup menu the Show Equipment" option.
This operation opens the user interface as shown in following figure:
Operator Handbook
1615BCE Management
1353NM-E Rel. 7.4B

497/532
Figure 453. 169xSE USM
1353NM-E Rel. 7.4B
498/532
Operator Handbook
1615BCE Management
13.4.5 Navigation to SANman application

From TMNOS it is possible to activate SANman application selecting the dedicated icon as shown in following figure:
Figure 454. Open SANman application from TMNOS selecting icon
Figure 455. Open SANman application from TMNOS selecting menu Actions
Operator Handbook
1615BCE Management
1353NM-E Rel. 7.4B

499/532
Selecting the highlighted icon in the figure or TMNOS menu:

Actions Open 1353NMSE Map
the application main window is displayed where all the managed SAN equipment are displayed in the
resource tree.
Figure 456. User Interface

The contents and set of operations available with application are not part of the present manual. Please
refer to [1] for a detailed description of the application.
13.4.6 Ping NE
A useful function to test the 169xSE NE availability from 1353NM is the Ping NE" function. Select the
169xSE NE on the map, select from the menu:
Operations Ping NE.
The operation's result will be displayed after a few seconds as shown in following figure.
1353NM-E Rel. 7.4B
500/532
Operator Handbook
1615BCE Management
Operator Handbook
1615BCE Management
1353NM-E Rel. 7.4B

501/532

platform OSKernel and can be activated from TMNOS menu. For 169xSE a subsystem of alarms is
managed and can be seen using AS USM. Starting from TMNOS menu the main AS USM window is displayed as shown in following figure. This list contains all the alarms received.
1353NM-E Rel. 7.4B
502/532
Operator Handbook
1615BCE Management

The administration window is displayed.
Operator Handbook
1615BCE Management
1353NM-E Rel. 7.4B

503/532
Figure 460. AS Administration Window
1353NM-E Rel. 7.4B
504/532
Operator Handbook
1615BCE Management
13.5.1 Navigation from AS to 169xSE USM

Starting from the main alarm list window it is possible to navigate to SANman USM selecting :
Each time a navigation is selected a new SANman USM window will be opened.
Figure 461. Navigation to SANman application

Selecting the above navigation the 169xSE USM is displayed.
Operator Handbook
1615BCE Management
1353NM-E Rel. 7.4B

505/532
Figure 462. 1353NMSE Alarms List
1353NM-E Rel. 7.4B
506/532
Operator Handbook
1615BCE Management


Selecting the option 'Show alarms' the list of 169xSE alarms will be displayed.
Operator Handbook
1615BCE Management
1353NM-E Rel. 7.4B

507/532
Figure 464. 169xSE Alarms Sublist
1353NM-E Rel. 7.4B
508/532
Operator Handbook
1615BCE Management
14 Generic Functions
This chapter collects some generic functions available on 1353NM Subsystem.
14.1 Configuration for Navigation between NM and BM-PR

This paragraph lists some steps to setup correctly NM Subsystem to succeed in navigationg towards BMPR Subsystem.
The 1353NM System and 1354BM-PR System are integreted with following actions:
After the System Config on both systems, run following script as root user (the processes can be running) :
/alcatel/Kernel/bin/CustomNavigations.pl -sys
1354BMPR -iinst <1354BMPR_INST_NUM>
1353NM
-inst
<1353NM_INST_NUM>
-isys
/alcatel/Kernel/bin/CustomNavigations.pl -sys 1354BMPR -inst <1354BMPR_INST_NUM> -isys

1353NM -iinst <1353NM_INST_NUM>
For example :
/alcatel/Kernel/bin/CustomNavigations.pl -sys 1353NM -inst 5-7.4.4 -isys 1354BMPR -iinst 1-8.1.6
/alcatel/Kernel/bin/CustomNavigations.pl -sys 1354BMPR-inst 1-8.1.6 -isys 1353NM -iinst 5-7.4.4
14.2 Navigation from 1353NM to 1354BM-PR

To setup the navigation from 1353NM to 1354BM-PR following conditions are mandatory:
1)
The Network Element label is the same on both system, that is on the topology management
map for 1353NM and on the BM-PR map. The Network Element is created using Topology Management in 1353NM System.
Operator Handbook
Generic Functions
1353NM-E Rel. 7.4B

509/532
Figure 465. Network Element on 1353NM map

The same Network Element is available on BM-PR map.
1353NM-E Rel. 7.4B
510/532
Operator Handbook
Generic Functions
Figure 466. Network Element on BM-PR map

2)
The navigation is supported from 1353NM to 1354BM-PR using the Show Equipment command starting from 1353NM map.
Figure 467. Navigation from 1353NM to 1354BM-PR
Operator Handbook
Generic Functions
1353NM-E Rel. 7.4B

511/532
The Network Element view opens on BM-PR system.
Figure 468. NE view on BM-PR
14.3 NE Event Archiving Configuration

The NE Event Archiving configuration function permits the operator to archive some events present in the
NE log in a text format log file (Comma Separated Values File Format). Indeed the main goal of this application is to store the meaningful event notifications in order not to lose them in case of NE restart.
Event logs are related to object creation/deletion, state change, attribute value change, protection events.
The NE Event to archive can be selected using the Archiving Configuration function.
1353NM-E Rel. 7.4B
512/532
Operator Handbook
Generic Functions
This function is activated selecting from the TMNOS menu:

Actions NE Event Archiving Configuration
Figure 469. NE Event Archiving Configuration selection

The Configuration window is displayed.
Operator Handbook
Generic Functions
1353NM-E Rel. 7.4B

513/532
Figure 470. Event Archiving Configuration

The protocol selection enables the filter on Q3 or SNMP NEs. The event log archived are the one listed
in the window. Selecting the event and clicking the <Enable Filter> button, activate the filter. The selected
events for the selected protocol will be archived for each NE corresponding to these characteristics.
The operation is confirmed by the box:
Figure 471. Event Archiving active

Once the Filter is active and you want to deactivate it, select the button <Disable Filter>.
The event are archived in a file, the file can be displayed from Topology Management window, selecting
an NE on the map and selecting from the menu: Operations Event Log Display
1353NM-E Rel. 7.4B
514/532
Operator Handbook
Generic Functions
Figure 472. Event Log Display selection

The archived file is displayed:
Figure 473. Archived Event Log file
Operator Handbook
Generic Functions
1353NM-E Rel. 7.4B

515/532
14.4 NE AutoDiscovery
The automatic creation of a new equipment is triggered by Craft Terminal. A new message with commissioning information (NE Type & Release, UserLabel, LocationName, NE address) is sent by CT NES to
a dedicated daemon of 1353NM Platform, passing through the Network Element. When NEs will be able
to support this commissioning message, NEs will be in charge to retrigger this notification periodically
(each ten minutes, configurable parameter). Anyway, CT has the full control on discovery message. CT
sends periodically the message until an acknowledge from a 1353NM daemon is received.
On 1353NM, a daemon receives this message and acknowledges it to the sender. Before sending the
acknowledge message to CT, daemon has to check its correctness: duplicated NE address, duplicated
discovery message on the same NE. When acknowledged, daemon sends a special alarm (persisted by
an APT internal to the daemon) to AS containing all the information related to the new NE.
This new alarm is displayed on a specific sublist on AS. 1353NM operator then selects the alarm on AS
and navigate to a Create NE dialog, which displays the parameters of the new NE as they appear in the
AS alarm. The operator may then change some of these parameters and confirm the NE creation, which
is then processed by PNMIM as a normal NE creation. It may then succeed or fail and, in this last case,
the operator may retry it by changing some parameter. Create NE dialog, when NE is created, sends an
action to the daemon in order to clear the alarm. The daemon, at its turn, will send the clear of the alarm
to AS.
Figure 474. AS NE Auto-discovery sublist
1353NM-E Rel. 7.4B
516/532
Operator Handbook
Generic Functions
ABBREVIATIONS
ABBREVIATION
MEANING
2G
2nd Generation wireless tecnology
4G
4th Generation wireless tecnology
AC
Equipment view Abnormal Condition state icon
ACD
Access Control Domain
ACK
ACKnowledged
ADI
NSAP address portion
AFI
Authority and Format Identifier (NSAP address portion)
AGG16
Aggregation board module
ALI
Equipment view Alignment state icon
APT
Active Problem Table
ARS
Action Remedy System
AS
Alarm Surveillance, 1330AS Alcatel product
ASAP
Alarm Severity Assignment Profile
ATM
Asynchronous Transfer Mode
AU
Administrative Unit
AVC
Advanced Video Coding
BCE
SHDSL Line terminal Box,1615BCE Alcatel product
BKUP
Backup
BM
1354BM Alcatel product
BMATM
1354 BMATM Alcatel product
BMETH
1354 BMETH Alcatel product
BMPR
1354 BMPR Alcatel product
CLEI
Telcordia (former Bellcore) NE Identification code
CLNP
ConnectionLess Network Protocol
Operator Handbook
Abbreviations
1353NM-E Rel. 7.4B

517/532
ABBREVIATION
MEANING
CLNS
ConnectionLess Network Service
CM
1352 CM Alcatel product
CMPG
CoMParison Graphic PM report
CMPT
CoMParison Tabular PM report
CNE
Composite NE
COM
Equipment view communication state icon
CPU
Central Processing Unit
CRI
Equipment view CRItical alarm severity icon
CSV
file format
CT
Craft Terminal, 1320CT Alcatel product
CTC
Equipment view CT Connection state icon
DCC
Data Communication Channel
DCG
Delta Counter Graphic PM report
DCN
Data Communication Network
DCT
Delta Counter Tabular PM report
DD
Two digit day number
DNM
Distributed Network Map
DWDM
Dense Wavelength Division Multiplexing
E1
International standard for highspeed voice/data transmission
EC
Equipment Controller
ELB
Event Log Browser
EMC
Electro Magnetic Compatibility
EML
Element Manager Layer
EMLIMSGM
EML IM SGM
EQP
EQuiPment view alarm icon
ESD
ElectroStatic Discharger
EXTP
Equipment view EXternal TP state icon
FC
Fiber Channel
FDN
Full Distinguished Name
FOX
1640FOX Alcatel product
1353NM-E Rel. 7.4B
518/532
Operator Handbook
Abbreviations
ABBREVIATION
MEANING
G.703
ISO standard
GbE
Giga bit Ethernet board
GNE
Gateway Network Element
Hour(s)
HA
1359 HA Alcatel product
HAOSCLS
1359 HAOSCLS Alcatel product
HAOSRES
1359 HAOSRES Alcatel product
hh
Two digit hour value
HP
Hewlett Packard
HPCDE
HP Common Desktop Environment
HPOV
HP OpenView
HPOVW
HP OpenView Windows
hpterm
HP terminal
HPUX
HP Unix
HPVUE
HP Visual User Environment
htm
HyperText Markup language
html
HyperText Markup Language
HW
HardWare
I/O
Input/Output
IAP
1359 IAP Alcatel product
ICD
ATM address format
IDI
Initial Domain Identifier (NSAP address portion)
IEEE
Institute of Electrical and Electronics Engineers
IM
Information Manager
IND
Equipment view INDeterminate alarm severity icon
ION
Intelligent Optical Networking
IOO
1359 IOO Alcatel product
IP
Internet Protocol
ISA
Industry Standard Architecture
ISDN
Integrated Service Digital Network
Operator Handbook
Abbreviations
1353NM-E Rel. 7.4B

519/532
ABBREVIATION
MEANING
ISN
1359 ISN Alcatel product
ISO
International Standard Organization
ITU
International Telecommunications Union
ITUT
ITU Telecommunication standardization sector
JDK
Java Development Kit
KB
1024 bytes
Kbit
1024 bits
Kbit/s
Kilobits per second
LAN
Local Area Network
LAPD
Link Access Procedure on the D channel
LET
PM external component
LOS
Loss OfSignal
LSS
OAD process
LT
Line Termination
LTU
LT Unit
MAJ
Equipment view MAJOR alarm severity icon
Mbit
1048 kilobits.
Mbit/s
Megabits per seconds
MGR
ManaGer role
MIB
Management Information Base
MIN
Equipment view MINor alarm severity icon
min
Minute(s)
mm
Two digit minute value
MM
Two digit month number
MSEML
1350 MSEML Alcatel product
MSHPUX
1350 MSHPUX Alcatel product
MW
Microwave technology
MySQL
Multithreaded SQL database management system
NACK
Not ACKnowledged
NAD
Network Access Domain
1353NM-E Rel. 7.4B
520/532
Operator Handbook
Abbreviations
ABBREVIATION
MEANING
NAP
Network Access Point
NAV
Alcatel product
NE
Network Element
Netscape
Internet Browser
netstat
NETwork STATistic command line tool
NM
Network Manager, 1353NM Alcatel product
NME
1353NM for Ethernet
NML
Network Management Layer
NML/MGR
Equipment view assignment state icon
NMSE
NMSE integration server
NOC
AS component
NP
1354NP Alcatel product
NR
Network Release
NR130Norm
Serial Number format
NRSV
Not ReSerVed alarm
NSA
Non Service Affecting alarm
NSAP
Network Service Access Point
NT
1356NT Alcatel product
NT
Network Termination
NTP
Equipment view Network Time Protocol state icon
NTP
Network Time Protocol
NTU
Network Termination Unit
OA512
Omni Access Alcatel product
OAD
Object Access Domain
OAM&P
Operations, Administration, Maintenance and Provisioning NM

functionalities
OBS
On Board Simulator
OBS
OutofBand Signaling
OmniAccess
Alcatel WLAN platform
OMSG
Optical MultiService Gateway
Operator Handbook
Abbreviations
1353NM-E Rel. 7.4B

521/532
ABBREVIATION
MEANING
OMSN
Optical MultiService Node
OS
Computer Operating System
OS
Network Operation System
OSCONF
Operation System CONFigurator
OSF
Open Source Foundation
OSF
Operation System Function
OSF
Outgoing Signal Fail
OSI
Open System Interconnection
OSK
Operation System Kernel
P/N
Part Number
P2P
Point to point
PDF
Portable Data Files
PDG
Packet Data Gateway
PDG
PM Data counter Graphic
PDH
Plesiochronous Digital Hierarchy
PDT
PM Data counter Tabular
PDU
Protocol Data Unit
PE
PM Performance Entity
PE
Provider Edge
PES
Packetized Elementary Stream
PI
1350 PI Alcatel product
PI
Physical Interface
PL1
Patch Level n
PM
PMC
Process Monitoring Control Alcatel product
PMDS
PM Display System Alcatel product
PMP
Performance Monitoring Point
PMP
PM Point
PNM
Physical Network Manager
PO
1540PO Alcatel product
1353NM-E Rel. 7.4B
522/532
Operator Handbook
Abbreviations
ABBREVIATION
MEANING
PPI
PDH Physical Interface
PS
file format
PS
Packet Switching
PSAP
Public Safety Answering Point
Psel
Presentation SELector
PSH
PM Path State History
PTM
Path Trace Mismatch
PtoP
Point to point
Q2
protocol for network management
Q3
CMIP based protocol for network management
Q3/COM
Equipment view operational state icon
QA
1354 QA Alcatel product
QB3
protocol for network management
REF
PM REFerence Value
RFC
Request for Comments
RFC1006
OSI address special case
RM
Regional Manager, 1354RM Alcatel product
RM
Resource Management
RNE
Remote NE
RO
Read Only access
ROM
Read Only Memory
RRC
Radio Resource Control
RRC
Report Request Control pm component
RS
Regenerator Section
RSV
ReSerVed alarm
RW
Read Write access
SA
Service Affecting alarm
SA
Source Address
SAN
Storage Area Network
SDH
Synchronous Digital Hierarchy
Operator Handbook
Abbreviations
1353NM-E Rel. 7.4B

523/532
ABBREVIATION
MEANING
SE
169xSE Alcatel product family (1353 1693 1696 SE)
SEC
SECurity
SF
Signal Failure
SGM
SNMP Generic Mapper
SH
1353SH former Alcatel product
SHDSL
Symetric High speed Digital SubscriberLine
SI
Service Independent alarm
SI
System Integrator
SIM
Equipment view SIMulator state icon
SKT
SKT
SM
1660 1664SM Alcatel product
SMC
1650SMC Alcatel product
SMF
System Management Feature
SN
Service Node
SNMP
Simple Network Management Protocol
SNT
SHDSL module
SNTHD
SHDSL E1 module
SONET
Synchronous Optical NETwork
SPI
AS Alcatel product component
SQL
Structured Query Language
SR
1666SR Alcatel product
ss
Two digit second value
SSel
S SELector
SSel
Session SELector
STM
Synchronous Trasfer Mode
SUP
Equipment view SUPervision state icon
SUS
Start Up Service for SE
SWDL
SoftWare DownLoad
SX
1664SX Alcatel product
SY
1354 SY Alcatel product
1353NM-E Rel. 7.4B
524/532
Operator Handbook
Abbreviations
ABBREVIATION
MEANING
SY
Alcatel product
SYNC
Equipment view SYNChronization state icon
T1
U.S. standard for highspeed voice/data transmission
TCP
Transmission Control Protocol
TCT
Threshold Cross Table PM report
telnet
TELetype NETwork protocol
TLI
1359 TLI Alcatel product
TMN
Telecommunication Management Network (ITUT generic model

for OAM&P information )
TMN
Topology MaNager
TMN
Transmission Management Network (1300platform;

1312mediation; 13301336/1380application)
TP
Termination Point
TRISD325
Telcordia (former Bellcore) specification
TRNS
Equipment view TRaNSmission state icon
Tsel
Transmission SELector
TSP
Transmission Session Presentation selectors
TVA
Topology Viewer Application
TXT
file format
UA
User Access
UAplus
SHDSL module
UDP
User Datagram Protocol
URL
Uniform Resource Locator
USM
User Service Manager
USP
OA module for E1 T1 ISDN
VC
Virtual Container
VPN
1355 VPN Alcatel product
WLAN
Wireless LAN
WDM
Wavelength Division Multiplexing
WNG
Equipment view WarNinG alarm severity icon
Operator Handbook
Abbreviations
1310/
1353NM-E Rel. 7.4B

525/532
ABBREVIATION
MEANING
WS
Work Station
WWN
NMSE switch parameter
X.733
ITUT Recomendation
XC
CrossConnect
XML
Extensible Markup Language file format
XSL
file format
YY
Two digit year number
YYYY
Four digit year number
1353NM-E Rel. 7.4B
526/532
Operator Handbook
Abbreviations
INDEX
A
Abnormal Condition, 282
Access Control Domain, 218
Profile, 248
Action Remedy System (ARS), 76
Alarm
Log, 113
Alarm Management
Acknowledge, 82
Alarm Severity Assignment Profile, 329
Alarm Surveillance, 75
Clear, 84
Debouncing, 89
Export, 84
Perceived Severity, 75
Print, 84
Probable cause, 75
Purge, 84
Reserve, 80
Severity panel, see Equipment View
Align Up, 307
Authority and Format Identifier, 225
Availability, see Performance Monitoring
B
Board view, 49
C
Command Log, 40
Comparison, see Performance Monitoring
Composite NE, 184, 222, 223, 252
D
Delta Counter, see Performance Monitoring
Distributed map, 237
DWDM, 449
Dynamic Bandwidth Optimization, 347
Dynamic Link, 145
E
Equipment View, 45
Message area, 48
Event log, 512
Event Log Browser, 113
Expiration, see Password
Operator Handbook
Index
External Text, 235
F
File Transfer Scheduler, 346
Front Panel, 35
Full Distinguished Name, 75
G
Global Actions, 40
Granularity, see Performance Monitoring
H
Help, 67
I
ISA board, 316
L
Line Terminal, 486
Line Termination Unit, 485
Local map, 237
Local Persistency, 191
Lock the screen, 35
Logging out, 36
Login panel, 33
M
Management State Control Panel, 47
Map, 237
Message area, see Equipment View
MIBless architecture, 301
N
NE address, 255
NE AutoDiscovery, 516
NE Event Archiving, 512
NE Management states, 146
NE MIB, 158
NE view, 45
Network Element, 145
Network Termination Unit, 485
Non Service Affecting, 332
1353NM-E Rel. 7.4B

527/532
NSAP, 225
Remote NE, 145

Report Request Control, see Performance Monitoring
O
Omni Access, 425
OMSN management, 316
onboard simulator, 310
OS process state, 39
OSKernel, 427, 461, 487
P
Padlock, 35
Password, 33
Change, 34
Expiration, 34
Path State History, see Performance Monitoring
Availability and Quality Trend, 104
Comparison Report, 104
Counter, 104
Delta Counter, 104
Forced collection, 91
Granularity, 91
Path State History, 104
Periodical collection, 91
PM Entity, 96
PM Report, 94
PMDS, 91
Profile, 102
Reference Value, 104
Report Request Control, 98
Start and Stop, 91
Threshold, 107
Perfstorage, 91
Port View, 50
Probale Cause family, 332
Process Monitoring Control (PMC), 405
Processing error, 75
productrelease, 27
Profile, see Access Control Domain
Profile, see Alarm Management
Profile, see Performance Monitoring
S
SAN Extender, 449
Selectors, 225
Service Affecting, 332
Service Independent, 332
SHDSL transmission system, 485
SNMP Generic Mapper, 428, 463, 488
SNT+, 486
SNTHD, 486
Software Download Scheduler, 346
software package, 27, 264, 266, 352
SONET, 449
Start/Stop System, 39
Static Link, 145
Submap, 237
Supervision Area, 248
T
Threshold, see Performance Monitoring
TMNOS, 38
TMNOS Manager, 38
TMNOS System, 35
Transmission Alarm, 325
U
UAplus, 486
W
workspace, 35
workstation, 35
X
XVision, 439
Q
Quality of service, 75
Quality Trend, see Performance Monitoring
1353NM-E Rel. 7.4B
528/532
Operator Handbook
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 understanding 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 CDROM, 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 Assistance Center.
Well take your suggestion in account.

We reserve to modify consequently the handbook according to the corretness and congruence of the suggestion and requests.
Operator Handbook
Customer Documentation Feedback
1353NM-E Rel. 7.4B

529/532
532
CUSTOMER DOCUMENTATION FEEDBACK

Handbook Data
Handbook title, release,version:
Handbook type:
Handbook part number and edition:
General Feedback Evaluation
SUBJECT
5(max)
4
3
Total evaluation
Info quantity
Info quality
Info structure
Consulting facility
Layout
Chapters Feedback Evaluation
HANDBOOK PARTS
5(max)
4
3
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
1 (min)
1(min)
Your Comments (strictly 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:
Email:
Phone:
1353NM-E Rel. 7.4B
530/532
Operator Handbook
Operator Handbook
1353NM-E Rel. 7.4B

531/532
532
1353NM-E Rel. 7.4B
532/532
Operator Handbook
3AL 89099 AAAA

Issue 3
All rights reserved.

Passing on and copying of this document,
use and communication of its contents is not permitted
without written authorization from Alcatel -Lucent.
www.alcatel-lucent.com

1353NM 74B 03 1

Uploaded by

Copyright:

Available Formats

1353NM 74B 03 1

Uploaded by

Document Information

Original Description:

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

1353NM 74B 03 1

Uploaded by

Copyright:

Available Formats

1353NM-E

Element Manager for Optical&Radio Networks

Copyright 2007 Alcatel-Lucent

3AL 89099 AAAA

All rights reserved.

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

1 WHAT IS NEW? ...........................................................................................................................

1353NM-E Rel. 7.4B

3.1.3 Current Alarm Management ...........................................................................................

4 PERFORMANCE MONITORING MANAGEMENT ......................................................................

5 EVENT AND ALARM LOG BROWSER.......................................................................................

1353NM-E Rel. 7.4B

3AL 89099 AAAA Issue 3

6.2.11 Ping NE .........................................................................................................................

7 MANAGING A MAP .....................................................................................................................

1353NM-E Rel. 7.4B

7.5.1 NE management states ..................................................................................................

8 PROCEDURES FOR NM CONFIGURATION ..............................................................................

1353NM-E Rel. 7.4B

3AL 89099 AAAA Issue 3

8.6.10 Software Status............................................................................................................. 370

10 IP OVER OSI TUNNELLING ......................................................................................................

12 1353NMSE MANAGEMENT .................................................................................................... 449

1353NM-E Rel. 7.4B

12.1 Product overview ...............................................................................................................

13 1615BCE MANAGEMENT .........................................................................................................

14 GENERIC FUNCTIONS.............................................................................................................. 509

3AL 89099 AAAA Issue 3

14.3 NE Event Archiving Configuration ................................................................................... 512

1353NM-E Rel. 7.4B

1353NM-E Rel. 7.4B

3AL 89099 AAAA Issue 3

1353NM-E Rel. 7.4B

Figure 53. Alarm Debouncing activation ...........................................................................................

1353NM-E Rel. 7.4B

3AL 89099 AAAA Issue 3

Figure 107. Event Notification Id Sort ...............................................................................................

1353NM-E Rel. 7.4B

Figure 161. File Menu .......................................................................................................................

1353NM-E Rel. 7.4B

3AL 89099 AAAA Issue 3

Figure 215. Root map and submap ..................................................................................................

1353NM-E Rel. 7.4B

Figure 269. Operations: Create ISA..................................................................................................

1353NM-E Rel. 7.4B

3AL 89099 AAAA Issue 3

Figure 323. NEs SWDL Status..........................................................................................................

1353NM-E Rel. 7.4B

Figure 377. Add IP NE on selected Tunnel.......................................................................................

1353NM-E Rel. 7.4B

3AL 89099 AAAA Issue 3

Figure 431. Ping NE result................................................................................................................

1353NM-E Rel. 7.4B

1353NM-E Rel. 7.4B

3AL 89099 AAAA Issue 3

1353NM-E Rel. 7.4B

1353NM-E Rel. 7.4B

3AL 89099 AAAA Issue 3