1354rm74f Oh v1 I4 PDF

1354RM
Regional Network Manager for SDH and Optical Networks

VOL I Basic Network Management
Rel.7.4F
Version 7.5.0
User Guide
3AL 61269 AAAA
Issue 4
May 2009
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 61269 AAAA

Issue 4
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 ......................................................................................................................... 7
LIST OF TABLES ........................................................................................................................... 25
PREFACE......................................................................................................................................... 27
Preliminary Information.............................................................................................................. 27
Applicability................................................................................................................................. 28
Scope ........................................................................................................................................... 28
History.......................................................................................................................................... 29
Related Documents .................................................................................................................... 30
Handbook Structure ................................................................................................................... 31
General on Customer Documentation ...................................................................................... 32
1 GETTING STARTED .................................................................................................................... 37

1.1 Introduction .......................................................................................................................... 37
1.2 Overview ............................................................................................................................... 37
1.2.1 The Regional Manager in the controlled network ........................................................... 37
1.2.2 Topological Components ................................................................................................ 37
1.2.3 Transport Entities............................................................................................................ 38
1.2.4 1330AS ........................................................................................................................... 40
1.2.5 System Management Features....................................................................................... 40
1.2.6 Fault Management.......................................................................................................... 41
1.2.7 Performance Monitoring Management ........................................................................... 43
1.3 REGIONAL Manager graphical user interface principles................................................. 44
1.3.1 Generalities..................................................................................................................... 44
1.3.2 Windows ......................................................................................................................... 45
1.4 PRELIMINARY OPERATIONS.............................................................................................. 48
1.4.1 Logging in to the System ................................................................................................ 48
1.4.2 Locking the screen.......................................................................................................... 49
1.4.3 Logging Out .................................................................................................................... 49
1.5 Access to the main functionalities..................................................................................... 51
1.5.1 Introduction ..................................................................................................................... 51
1.5.2 The TMN-OS .................................................................................................................. 52
1.5.3 Alarm management ........................................................................................................ 54
1.5.4 Task Subpanel ................................................................................................................ 56
1.5.5 Active task subpanel ....................................................................................................... 57
1.6 Views Description ................................................................................................................ 69
1.6.1 Overview......................................................................................................................... 69
1.6.2 Management Tools windows........................................................................................... 70
1.7 SDH Netview : map navigation ........................................................................................... 72
1.7.1 Introduction ..................................................................................................................... 72
1.8 Layered maps....................................................................................................................... 78
1.9 Browser................................................................................................................................. 80
1.9.1 Introduction ..................................................................................................................... 80
1.9.2 Work area ....................................................................................................................... 84
1.9.3 Navigations ..................................................................................................................... 96
1.9.4 Active Counters .............................................................................................................. 96
1.9.5 Counters ......................................................................................................................... 98
1.9.6 User Interface ................................................................................................................. 100
1.9.7 Definition and Activation ................................................................................................. 103
1.10 Browser: Drawing Windows ............................................................................................. 112
1.10.1 Introduction ................................................................................................................... 112
1.10.2 Icon bar ......................................................................................................................... 113
User Guide 1354RM Rel.7.4F

Table of Contents 3AL 61269 AAAA Issue 4 1/854
1.10.3 Work area ..................................................................................................................... 113
1.11 BROWSER: LOCATE ITEMS IN NETVIEW........................................................................ 114
1.11.1 Locate topological objects on Map................................................................................ 114
1.12 On-line documentation...................................................................................................... 116
1.12.1 Overview....................................................................................................................... 116
2 OPERATION................................................................................................................................. 117
2.1 Introduction .......................................................................................................................... 117
2.2 Network configuration......................................................................................................... 117
2.2.1 Network Construction ..................................................................................................... 117
2.2.2 Start the Netview application .......................................................................................... 118
2.2.3 Create the network objects ............................................................................................. 119
2.2.4 External Network Reference........................................................................................... 128
2.2.5 Create Connection.......................................................................................................... 132
2.2.6 Introduction to NPA ......................................................................................................... 143
2.2.7 Create a 4-F STM-16 NPE Ring with 1664SM ............................................................... 156
2.2.8 Takeover procedure ........................................................................................................ 157
2.2.9 Create a 4-Fibre STM-64 NPE Ring with 1670SM ......................................................... 157
2.2.10 Takeover procedure ...................................................................................................... 159
2.2.11 Upload Tools ................................................................................................................. 159
2.2.12 2Mb/s retiming management ........................................................................................ 165
2.2.13 Network implementation ............................................................................................... 168
2.2.14 Payload structure modification:Ho/Lo ........................................................................... 169
2.2.15 Trail Creation Wizard .................................................................................................... 170
2.2.16 Improved path/trail management .................................................................................. 174
2.2.17 Upload NAPs ................................................................................................................ 177
2.2.18 Take-over of retiming .................................................................................................... 178
2.3 Transport Management ....................................................................................................... 180
2.3.1 Path Provisioning............................................................................................................ 180
2.3.2 Path Create management............................................................................................... 182
2.3.3 Non terminated path ....................................................................................................... 199
2.3.4 Path ends modification ................................................................................................... 199
2.3.5 Gigabit Ethernet path ..................................................................................................... 202
2.3.6 LCAS Management ........................................................................................................ 210
2.3.7 Compatibility tables......................................................................................................... 215
2.3.8 Gigab broadcast 1 source............................................................................................... 229
2.3.9 Gigab broadcast 2 sources............................................................................................. 235
2.3.10 2 MB broadcast 2 sources ............................................................................................ 241
2.3.11 AU3 path ....................................................................................................................... 244
2.3.12 User's Default ............................................................................................................... 246
2.3.13 AU3-NV path................................................................................................................. 247
2.3.14 Digital Video Broadcasting path (not protected) ........................................................... 252
2.3.15 Digital Video Broadcasting path (route protected) ........................................................ 261
2.3.16 DVB path route (SNCP) and source protected ............................................................. 266
2.3.17 10 GBE EPL point to point path .................................................................................... 274
2.3.18 10 GBE EVPL point to multipoint path .......................................................................... 284
2.3.19 EVPL mixed 10GbE-1GbE path flow control management .......................................... 290
2.3.20 LCAS hold off time management on 1678MCC-1GBE path ......................................... 294
2.3.21 Ethernet auto-negotiation on single port of a path ........................................................ 299
2.3.22 Ethernet path consequent actions configuration for 1678MCC R4.3............................ 300
2.3.23 ............................................................................................ Management of ISA ES64 302
2.3.24 Path Allocate, implicit payload ...................................................................................... 308
2.3.25 Lock of BM path ............................................................................................................ 308
2.3.26 Saturation and fragmentation profiles ........................................................................... 319
1354RM Rel.7.4F User Guide

2/854 3AL 61269 AAAA Issue 4 Table of Contents
2.3.27 Allocation algorithm: defragmentation........................................................................... 320
2.3.28 Path Implement............................................................................................................. 325
2.3.29 Service state modification ............................................................................................. 331
2.3.30 Constraint management ............................................................................................... 332
2.3.31 Add Constraints procedure ........................................................................................... 339
2.3.32 Potential time slot ......................................................................................................... 345
2.3.33 Copy and Paste of Constraints set ............................................................................... 348
2.3.34 Adding /Removing a leg to a path................................................................................. 349
2.3.35 Path in NPE ring ........................................................................................................... 352
2.3.36 Drop and Continue path................................................................................................ 356
2.3.37 Z & C - 4 Nodes interconnection................................................................................... 372
2.3.38 D&C for dual node interconnection on single physical connection (only add service).. 373
2.3.39 Single timeslot across the ring...................................................................................... 373
2.3.40 NAPs with Path information .......................................................................................... 377
2.3.41 Path/Trail Modification Tool........................................................................................... 378
2.3.42 OS driven restoration for HO paths & trails................................................................... 393
2.3.43 Join/Split Path ............................................................................................................... 398
2.3.44 Join-Split Trail ............................................................................................................... 411
2.3.45 Join-Split Physical Connection...................................................................................... 416
2.3.46 ISDN primary access management .............................................................................. 426
2.3.47 4 x ANY......................................................................................................................... 430
2.3.48 Take-over of paths and trails (point-to-point + SNCP) .................................................. 433
2.3.49 Reroute paths from physcon......................................................................................... 437
2.3.50 Force path switch from physcon ................................................................................... 438
2.3.51 End to end path reroute (broadcast incl.)...................................................................... 440
2.3.52 Reuse of Physical Connection on different VC for the same path ................................ 449
2.3.53 Save and recall of nominal route with constraint set .................................................... 449
2.3.54 Save and recall of nominal route as constraint set ....................................................... 450
2.3.55 Planned Activities for path, trails and Nodes operations............................................... 455
2.4 Network Modifications......................................................................................................... 468
2.4.1 Introduction ..................................................................................................................... 468
2.4.2 Remove Tributary Board................................................................................................. 474
2.4.3 Configuration of a Transmux board ................................................................................ 475
2.5 Export of resources on ISN interface for 1355VPN .......................................................... 476
2.5.1 Introduction ..................................................................................................................... 476
2.6 Statistics Tables ................................................................................................................... 479
2.6.1 Statistics Tables from Ntw, Sbn, Node ............................................................................ 480
2.7 Topology structure change utilities ................................................................................... 486
2.7.1 Move node from/to RM topologies .................................................................................. 486
2.7.2 SPLIT OF VIRTUAL NE.................................................................................................. 492
2.7.3 Move Ports of a Virtual Node .......................................................................................... 515
2.7.4 Move Ports (Real Node) ................................................................................................. 521
2.7.5 Conversion planned/real ports ........................................................................................ 532
2.8 SDH Network Take Over ...................................................................................................... 537
2.8.1 SDH Network Take Over Description.............................................................................. 537
2.8.2 Linear MSP Take Over.................................................................................................... 539
2.8.3 2f MS-SPRings Take Over .............................................................................................. 540
2.8.4 Paths and Trails Take Over............................................................................................. 541
2.8.5 Overview on the operational procedures for take over ................................................... 542
2.8.6 Complete SDH Network take over .................................................................................. 542
2.8.7 Take over of specific SDH Paths/Trails........................................................................... 545
2.8.8 Resources managed by 1354RM ................................................................................... 545
2.9 Protection Analyzer Tool..................................................................................................... 547
2.9.1 Tool Description .............................................................................................................. 547

2.9.2 How to run the tool.......................................................................................................... 547
2.9.3 Analyze a single path...................................................................................................... 548
2.9.4 Analyze the entire network ............................................................................................. 549
2.9.5 Analyze a subset of paths/trails ...................................................................................... 549
2.9.6 Filtering results ............................................................................................................... 550
2.9.7 Export entire network analysis to Excel .......................................................................... 552
3 MAINTENANCE ........................................................................................................................... 555

3.1 Introduction .......................................................................................................................... 555
3.2 Fault Management ............................................................................................................... 555
3.2.1 Elementary Alarms and RM Probable Causes ............................................................... 555
3.2.2 Alarm auto-Synchro after Flooding ................................................................................. 556
3.2.3 Alarm Enabling/Disabling................................................................................................ 556
3.2.4 Alarm Severity Assignment Profile ................................................................................. 560
3.2.5 Object Alarm Propagation............................................................................................... 568
3.3 Integration of 1354RM with SEC Security Subsystem ..................................................... 583
3.3.1 Introduction ..................................................................................................................... 583
3.3.2 Spurious alarm management on 1354RM ...................................................................... 586
3.4 INTRODUCTION TO MAINTENANCE.................................................................................. 590
3.4.1 Alarm navigation and fault localization ........................................................................... 590
3.4.2 Navigation of alarmed transport objects at server layer.................................................. 602
3.4.3 Diagnostic of the main objects ........................................................................................ 606
3.5 Path/Trail Allocation Failures.............................................................................................. 624
3.5.1 Introduction ..................................................................................................................... 624
3.5.2 Allocation failure diagnostic ............................................................................................ 625
3.6 Join / Split Trail Failure........................................................................................................ 639
3.6.1 Joint / Split HO-Trails ...................................................................................................... 639
3.7 Diagnostic of the NPE Ring ................................................................................................ 644
3.7.1 The 4-F MS Spring RM side ........................................................................................... 644
3.7.2 User Presentation ........................................................................................................... 654
3.8 NML-EML CONSISTENCY CHECKS ................................................................................... 676
3.8.1 NML-EML Consistency Checks (SEN-IM) ...................................................................... 676
3.8.2 SEN-IM NM misaligned .................................................................................................. 680
3.8.3 NML-EML Consistency Checks (Q3) .............................................................................. 683
3.9 Maintenance Tracing ........................................................................................................... 687
3.9.1 J0 Section Trace Identifier Set / Modify .......................................................................... 687
3.9.2 J1/J2 Trace Identifier ...................................................................................................... 693
3.9.3 Path Trace ...................................................................................................................... 695
3.9.4 Tandem Connection........................................................................................................ 698
3.9.5 TCT/TCM global automatic deimplementation ( upon path/trail deimplement ).............. 710
3.9.6 Manual remove of TCTs and TCMs ................................................................................ 710
3.9.7 Monitoring function (POM) on intermediate points.......................................................... 711
3.9.8 Loopback on PDH port / NAP ......................................................................................... 715
3.9.9 Loopback commands on CTP ........................................................................................ 718
3.9.10 Craft Terminal Supervision............................................................................................ 719
3.10 Protection management .................................................................................................... 719
3.10.1 SNCP path layer switch management .......................................................................... 719
3.10.2 Multiplex Section Layer switch management................................................................ 725
3.10.3 Management of switches at RM interface..................................................................... 737
3.11 Performance Monitoring.................................................................................................... 740
3.11.1 Introduction ................................................................................................................... 740
3.11.2 Creating the Measure.................................................................................................... 741
3.11.3 Transport object Correlation to the Measure................................................................. 745
3.11.4 Tp's correlation to the Measure..................................................................................... 748

3.11.5 PM on Multiplex Section................................................................................................ 752
3.11.6 Force Collection ............................................................................................................ 755
3.11.7 PMTP Attributes ............................................................................................................ 757
3.11.8 Counter Report Profile Creation.................................................................................... 760
3.11.9 Threshold Report Profiles Creation............................................................................... 763
3.11.10 Report Profile Correlation............................................................................................ 765
3.11.11 Measure Activation, Stop and Consistency ................................................................. 767
3.11.12 Threshold Crossing Alarm (TCA) Profile creation ....................................................... 769
3.11.13 Threshold Crossing Alarm (TCA) Profile Correlation to the PMTP ............................. 771
3.11.14 Merging of several Measures...................................................................................... 772
3.11.15 Displaying PM data ..................................................................................................... 773
3.11.16 The pmNE ................................................................................................................... 773
3.11.17 Archive Session .......................................................................................................... 777
3.11.18 Uncorrelate the transport from planned measures...................................................... 778
3.11.19 Uncorrelate the tp from planned measures................................................................. 778
3.11.20 Remove from RM menu .............................................................................................. 779
3.11.21 Uncorrelate the counter/threshold report profile from the measure ............................ 780
3.12 Test Ports............................................................................................................................ 781
3.12.1 SDH Test Port setup: Forward connection addition (A to B) ......................................... 781
3.12.2 SDH Test Port setup: backward connection addition (B to A)...................................... 789
3.12.3 Test Port Remove ......................................................................................................... 792
3.12.4 Multiple test port remove .............................................................................................. 793
3.12.5 Multiple Test port Addition............................................................................................. 794
3.12.6 PDH Test Ports ............................................................................................................. 796
3.13 LOGGER ............................................................................................................................. 801
4 TECHNICAL ANNEXES ............................................................................................................... 803

4.1 Introduction .......................................................................................................................... 803
4.2 Functionalities...................................................................................................................... 804
4.2.1 Supported EMLs ............................................................................................................. 804
4.2.2 Supported NEs ............................................................................................................... 804
4.3 ROUTING Algorithm ............................................................................................................ 805
4.3.1 Routing Algorithm General ............................................................................................. 805
4.3.2 Point to point paths ......................................................................................................... 805
4.3.3 Protection in Rings.......................................................................................................... 806
4.3.4 Broadcast path................................................................................................................ 807
4.3.5 Routing inside rings ........................................................................................................ 807
4.3.6 Service route in D&C paths............................................................................................. 811
4.4 ALLOCATION........................................................................................................................ 816
4.4.1 Allocation and Defragmentation...................................................................................... 816
4.4.2 De-saturation in routing .................................................................................................. 819
4.4.3 Saturation profile management....................................................................................... 820
4.4.4 ASON GBE restoration type, priority, reversion type management on path level........... 822
4.4.5 AU3 SPC's ...................................................................................................................... 823
4.4.6 LO Matrix TTP's as SPC end points .............................................................................. 823
4.4.7 GBE@AU3 in ASON....................................................................................................... 823
4.4.8 SC support in AU3 based networks (AU3, AU4, AU4-nC).............................................. 823
4.4.9 Management of GMRE setUpPriority ............................................................................. 824
4.5 NE CONSTRAINTS ............................................................................................................... 826
4.6 RM objects............................................................................................................................ 826
4.6.1 OTN WDM model ........................................................................................................... 830
4.6.2 Integrated approach........................................................................................................ 834
4.6.3 Functions ........................................................................................................................ 834
4.7 Object Names ....................................................................................................................... 835

ABBREVIATIONS AND GLOSSARY .............................................................................................. 837
INDEX ............................................................................................................................................... 851
CUSTOMER DOCUMENTATION FEEDBACK.............................................................................. 853

LIST OF FIGURES
Figure 1. Path configuration status states......................................................................................... 39
Figure 2. Alarm navigation ................................................................................................................ 42
Figure 3. Login panel view ................................................................................................................ 48
Figure 4. The SDH Manager workspace Front Panel. ...................................................................... 48
Figure 5. Locking the screen using a manual lock............................................................................ 49
Figure 6. Screen lock Password: entry box ...................................................................................... 49
Figure 7. Logging out using the front panel ...................................................................................... 50
Figure 8. HP-CDE Panel................................................................................................................... 51
Figure 9. TMN-OS manager ............................................................................................................. 52
Figure 10. Self-hiding vertical palette................................................................................................ 56
Figure 11. Active task subpanel ........................................................................................................ 57
Figure 12. System Menus started from the logo icon ....................................................................... 58
Figure 13. Pop-up menu ................................................................................................................... 58
Figure 14. Panel Close confirmation window. ................................................................................... 58
Figure 15. System menu................................................................................................................... 59
Figure 16. System Menus: Path Provisioning menu ......................................................................... 59
Figure 17. System Menus: Network Configuration menu ................................................................. 59
Figure 18. System Menus: Maintenance .......................................................................................... 60
Figure 19. System Menus: OS Supervision ...................................................................................... 60
Figure 20. Create New Panel submenu............................................................................................ 60
Figure 21. Create: New Corner Panel............................................................................................... 61
Figure 22. Create: New Edge Panel ................................................................................................. 61
Figure 23. Task bar pop-up menu .................................................................................................... 61
Figure 24. Panel Properties: Edge Panel.......................................................................................... 62
Figure 25. Panel Properties: Background ......................................................................................... 62
Figure 26. Global Panel Configuration: Animation............................................................................ 63
Figure 27. Global Panel Configuration: Miscellaneous ..................................................................... 64
Figure 28. Utility pop-up menu on each system menu item.............................................................. 65
Figure 29. Utility buttons ................................................................................................................... 66
Figure 30. Customized user menu.................................................................................................... 67
Figure 31. System menus: Path Provisioning: Path Creation Wizard: Add this to launcher panel ... 67
Figure 32. Window icon pop-up menu .............................................................................................. 68
Figure 33. Map window: Pull-down menu and tool buttons .............................................................. 72
Figure 34. Zoom tool interface .......................................................................................................... 73
Figure 35. RM domain map .............................................................................................................. 73
Figure 36. Available Layers .............................................................................................................. 74
Figure 37. Domain submap............................................................................................................... 74
Figure 38. Objects belonging to a subnetwork.................................................................................. 75
Figure 39. Objects belonging to a 2nd level Subnetw....................................................................... 75
Figure 40. Physical Connection list................................................................................................... 76
Figure 41. Physical Connection structure ......................................................................................... 76
Figure 42. Pop-up menu ................................................................................................................... 77
Figure 43. Example of selection of layer TU-12................................................................................ 78
Figure 44. Example of layer TU-12 ................................................................................................... 79
Figure 45. Example of layer AU4-16C .............................................................................................. 79
Figure 46. Browser main window. ..................................................................................................... 81
Figure 47. Browser work area........................................................................................................... 84
Figure 48. Object filtering.................................................................................................................. 85
Figure 49. Define query window for Node......................................................................................... 86
Figure 50. Show/Set Attributes dialog box........................................................................................ 88
Figure 51. Edit: Copy Attributes ........................................................................................................ 88
Figure 52. Attribute selection ............................................................................................................ 89

List of Figures 3AL 61269 AAAA Issue 4 7/854
Figure 53. Actions: Details: Displayed Info. ...................................................................................... 93
Figure 54. View:Report full................................................................................................................ 94
Figure 55. View:Report short ............................................................................................................ 95
Figure 56. Active Counters tool......................................................................................................... 96
Figure 57. Browser: Tools: Active Counters...................................................................................... 101
Figure 58. Status window.................................................................................................................. 101
Figure 59. Status window menus ...................................................................................................... 102
Figure 60. Active Counter Creation window...................................................................................... 103
Figure 61. Entering data in Active Counter Creation window ........................................................... 104
Figure 62. Monitored Class selection................................................................................................ 105
Figure 63. Condition Modification dialog box .................................................................................... 105
Figure 64. Condition Modification: Attribute selection....................................................................... 106
Figure 65. Condition Modification: attribute (enumerated) ................................................................ 106
Figure 66. Condition Modification: attribute modification (label) ....................................................... 107
Figure 67. Split button enabled ......................................................................................................... 108
Figure 68. Counter: Modify pop-up menu item ................................................................................. 109
Figure 69. Active Counter: Modify..................................................................................................... 110
Figure 70. Condition Visualization ( Show) ....................................................................................... 111
Figure 71. Node list........................................................................................................................... 114
Figure 72. Highlighted node in Netview. ........................................................................................... 115
Figure 73. Netview domain submap ................................................................................................. 118
Figure 74. Add background............................................................................................................... 118
Figure 75. Create Network dialog box. ............................................................................................. 119
Figure 76. Create: Network pop-up menu......................................................................................... 120
Figure 77. Network Domain submap ................................................................................................ 120
Figure 78. Create: Subnetwork. ........................................................................................................ 121
Figure 79. Create 1st lev. Subnetwork dialog box. ........................................................................... 121
Figure 80. Network map.................................................................................................................... 122
Figure 81. Subnetwork: Create: 2nd level Subnetwork pop-up menu .............................................. 122
Figure 82. Create 2nd level Subnetwork dialog box. ........................................................................ 123
Figure 83. New Object Holding Area ................................................................................................ 123
Figure 84. Objects belonging to a subnetwork.................................................................................. 124
Figure 85. Subnetwork: Actions: Create: Node................................................................................. 125
Figure 86. Node creation wizard: step 1 ........................................................................................... 126
Figure 87. Node creation wizard: step 1: NE selection. .................................................................... 127
Figure 88. Node just created............................................................................................................. 127
Figure 89. Node drag to the working area. ....................................................................................... 128
Figure 90. External Network Creation wizard. .................................................................................. 129
Figure 91. Create Connection step 1. ............................................................................................... 130
Figure 92. Create Connection step2 ................................................................................................. 130
Figure 93. Physical Connection: Implement ..................................................................................... 131
Figure 94. Actions: Create: Physical Connection.............................................................................. 132
Figure 95. Create Connection-step 1-Type SDH .............................................................................. 133
Figure 96. Create Connection-step 1-Type WDM............................................................................. 134
Figure 97. Create Connection-step 1-Type SDH-CBR/WDM interworking ....................................... 135
Figure 98. Create Connection-step 1-Type Generic Digital Client/WDM interworking...................... 136
Figure 99. Create Connection-step 2................................................................................................ 137
Figure 100. Port selection. ................................................................................................................ 138
Figure 101. Saturation Profile list...................................................................................................... 139
Figure 102. Fragmentation Profile list ............................................................................................... 140
Figure 103. Physical Connection Structure....................................................................................... 140
Figure 104. Physical Connection: Configuration: Implement ............................................................ 141
Figure 105. Physical connection structure implemented. ................................................................. 141
Figure 106. Saturation/Fragmentation Profile create button ............................................................. 142

8/854 3AL 61269 AAAA Issue 4 List of Figures
Figure 107. Saturation Profile create ................................................................................................ 142
Figure 108. Fragmentation profile create .......................................................................................... 142
Figure 109. Actions: Create: Npa...................................................................................................... 144
Figure 110. Create: Npa: Step 1: SNCP-U........................................................................................ 146
Figure 111. Create: Npa: Step 1: 1 + 1 protection ............................................................................. 147
Figure 112. Create: Npa: Step 1: 1 to N protection ........................................................................... 147
Figure 113. Create: Npa: Step 1: ASON protection........................................................................... 148
Figure 114. Create: Npa: Step 1: NPOS protection........................................................................... 148
Figure 115. Selection of the Physical connections............................................................................ 149
Figure 116. 1 to N NPA: physical connection selection..................................................................... 150
Figure 117. Action creation report ..................................................................................................... 150
Figure 118. NPA highlight.................................................................................................................. 151
Figure 119. NPA: Actions: Configuration: Modify NPA ...................................................................... 152
Figure 120. NPA: Modify: step 1 ....................................................................................................... 153
Figure 121. NPA: Modify: step 2 ....................................................................................................... 153
Figure 122. NPA: Actions: Configuration: Implement........................................................................ 154
Figure 123. NPA: Specify ring map: step 1 ....................................................................................... 155
Figure 124. NPA: Specify ring map: step 2 ....................................................................................... 155
Figure 125. Physical view of the aggregates of 1664SM-NPE (from 1353NM) ................................ 156
Figure 126. Example of NPE ring with 1670SM................................................................................ 158
Figure 127. 1670SM equipment view ............................................................................................... 158
Figure 128. 4-Fibre NPE ring 1353NM main dialog box ................................................................... 159
Figure 129. Sbn: Configuration: Upload Tools .................................................................................. 160
Figure 130. Upload Tools: Automatic generation of Trace Identifier ................................................. 161
Figure 131. Upload Tools. Select option Upload Physical Connectivity ............................................ 162
Figure 132. Upload Tools: Upload of Protection Schema ................................................................. 163
Figure 133. Discovered NPAs ........................................................................................................... 164
Figure 134. Path: Configuration: 2Mbit/s Retiming management ..................................................... 166
Figure 135. Path Retiming; step 1 .................................................................................................... 166
Figure 136. Path: retiming: port selection-step 2 .............................................................................. 167
Figure 137. Port: Retiming state=enabled ........................................................................................ 168
Figure 138. Payload structure modification: Ho-Cfg ......................................................................... 169
Figure 139. Payload structure modification: Lo-Cfg.......................................................................... 170
Figure 140. Create trail wizard step1:configuration .......................................................................... 171
Figure 141. Create trail wizard step1: protection .............................................................................. 172
Figure 142. Create trail wizard step1: protection .............................................................................. 172
Figure 143. Create trail wizard step1: PM......................................................................................... 173
Figure 144. Create trail wizard step1: routing ................................................................................... 173
Figure 145. Create trail wizard step1: CP restoration ....................................................................... 174
Figure 146. Highlight of the path ....................................................................................................... 175
Figure 147. Highlight of the path including the crossed trails ........................................................... 175
Figure 148. Trail setup between external networks .......................................................................... 176
Figure 149. Trail setup between an external network and a real NE ................................................ 177
Figure 150. Topological object: Configuration: Upload NAPs. .......................................................... 178
Figure 151. Actions: Create: Path pull-down menu .......................................................................... 181
Figure 152. Node: Create: Path pop-up menu.................................................................................. 181
Figure 153. Path Create step1.......................................................................................................... 183
Figure 154. Service type PDH: Service rate selection ...................................................................... 184
Figure 155. Service type ATM: Service rate selection ...................................................................... 184
Figure 156. Service type Ethernet: Service rate selection ................................................................ 184
Figure 157. Service type DATA: Service rate selection..................................................................... 185
Figure 158. Service type SDH: Service rate selection ...................................................................... 185
Figure 159. Path type selection ........................................................................................................ 185
Figure 160. Path SNCP type............................................................................................................. 186

Figure 161. Protection selection ....................................................................................................... 186
Figure 162. MS Protection Usage Profile.......................................................................................... 187
Figure 163. Step 2: End Points selection: Node selection: example of path..................................... 188
Figure 164. Path Create: step 3........................................................................................................ 191
Figure 165. Path just created............................................................................................................ 193
Figure 166. Fast Ethernet board ....................................................................................................... 194
Figure 167. Fast Ethernet board view............................................................................................... 195
Figure 168. Fast Ethernet board: Port view ...................................................................................... 195
Figure 169. Objects on browser. ....................................................................................................... 195
Figure 170. Multiple path creation button.......................................................................................... 196
Figure 171. Multi path creation ......................................................................................................... 196
Figure 172. Path ends modification: Add Backup End Points........................................................... 199
Figure 173. Backup ends specification ............................................................................................. 200
Figure 174. Modified path routing display ......................................................................................... 201
Figure 175. Path ends modification: Remove End Points................................................................. 201
Figure 176. 1 Gigabit connection structure ....................................................................................... 202
Figure 177. GB Eth path create step1 .............................................................................................. 203
Figure 178. Path create step 2.......................................................................................................... 204
Figure 179. Display: Server Trails..................................................................................................... 205
Figure 180. Server Trail list ............................................................................................................... 205
Figure 181. 1 Gigabit path routing display ........................................................................................ 206
Figure 182. Trail list........................................................................................................................... 206
Figure 183. Path: Modify Constraints................................................................................................ 207
Figure 184. 1 Gbit/s Ethernet Rate Adaptive path attributes ............................................................ 208
Figure 185. 1 Gbit/s Ethernet Rate Adaptive path routing display .................................................... 208
Figure 186. 1 Gbit/s Ethernet Rate Adaptive path trail list ................................................................ 209
Figure 187. Server trail routing modification ..................................................................................... 212
Figure 188. Path create:eth-adapt:es:step 3: LCAS ......................................................................... 214
Figure 189. Path: Modification: Lcas control menu........................................................................... 214
Figure 190. Path: Modification: Lcas control dialog box ................................................................... 214
Figure 191. Modification: Bandwidth: Increase bandwidth................................................................ 223
Figure 192. Action report: Increase bandwidth ................................................................................. 224
Figure 193. Display server trails button. ........................................................................................... 224
Figure 194. Server trail list ................................................................................................................ 225
Figure 195. Modification: Bandwidth: Activate Trails ........................................................................ 226
Figure 196. Modification: Bandwidth: Deactivate Trails .................................................................... 227
Figure 197. GFP Protocol Modification wizard.................................................................................. 228
Figure 198. Gigab broadcast 1 source: create step 1....................................................................... 229
Figure 199. Gigab broadcast 1 source: source selection.................................................................. 230
Figure 200. Gigab broadcast 1 source: 1st sink selection ................................................................ 230
Figure 201. Gigab broadcast 1 source: 2nd sink selection ............................................................... 231
Figure 202. Gigab broadcast 1 source: configuration ....................................................................... 232
Figure 203. Gigab broadcast 1 source defined view......................................................................... 232
Figure 204. Gigab broadcast 1 source allocation ............................................................................. 233
Figure 205. Gigab broadcast 1 source allocated view ...................................................................... 233
Figure 207. Trail routing view............................................................................................................ 234
Figure 208. Broadcast path highlight ................................................................................................ 235
Figure 209. Gigab broadcast 2 sources: create step 1 ..................................................................... 236
Figure 210. Gigab broadcast 2 sources: 1st source selection .......................................................... 237
Figure 211. Gigab broadcast 2 sources: 2nd source selection ......................................................... 237
Figure 212. Gigab broadcast 2 sources: sink selection .................................................................... 238
Figure 213. Gigab broadcast 2 sources-3 sinks defined view .......................................................... 238
Figure 214. Gigab broadcast 2 sources-3 sinks allocated view........................................................ 239

Figure 216. Trail view........................................................................................................................ 240
Figure 217. 2 Mb BROAD 2sources create step 1............................................................................ 241
Figure 218. 2 Mb BROAD 2sources: 1st source selection................................................................ 242
Figure 219. 2 Mb BROAD 2sources: sink selection.......................................................................... 242
Figure 220. 2 Mb BROAD 2sources view ......................................................................................... 243
Figure 221. 2 Mb BROAD 2sources highlight ................................................................................... 243
Figure 222. AU3 path create step 1 .................................................................................................. 244
Figure 223. AU3 path create step 2: end point selection .................................................................. 245
Figure 224. AU3 path allocated view ................................................................................................ 245
Figure 225. AU3 path implemented view .......................................................................................... 246
Figure 226. Save user defaults ......................................................................................................... 246
Figure 227. AU3-NV path create....................................................................................................... 247
Figure 228. AU3-NV path create step1 ............................................................................................. 248
Figure 229. End points selection....................................................................................................... 248
Figure 230. Detailed parameters selection example......................................................................... 249
Figure 231. Allocate the path ............................................................................................................ 249
Figure 232. Routing view of the allocated path ................................................................................. 250
Figure 234. Search: All related Items: Server Physical Connection ................................................. 251
Figure 235. Search: All related Items: Physical Connection Structure.............................................. 251
Figure 236. Physical Connection Structure....................................................................................... 252
Figure 237. DVB Reference Network................................................................................................ 253
Figure 238. Port list........................................................................................................................... 253
Figure 239. NAP list .......................................................................................................................... 254
Figure 240. Create: Path pop-up menu ............................................................................................ 254
Figure 241. DVB Path create box (step 1) ........................................................................................ 255
Figure 242. Source node selection ................................................................................................... 256
Figure 243. Source NAP selection.................................................................................................... 256
Figure 244. Additional Info box ......................................................................................................... 257
Figure 245. DVB defined path routing display .................................................................................. 258
Figure 246. Path: allocate pop-up menu........................................................................................... 258
Figure 247. DVB allocated path routing display ................................................................................ 259
Figure 248. Path: Implement pop-up menu ...................................................................................... 259
Figure 249. DVB implemented path routing display.......................................................................... 260
Figure 250. DVB path highlight ......................................................................................................... 260
Figure 252. Create: Path pop-up menu ............................................................................................ 262
Figure 253. DVB Path route prot. create box (step 1)....................................................................... 262
Figure 254. Source node selection ................................................................................................... 263
Figure 255. Sink1 NAP selection ...................................................................................................... 263
Figure 256. Sink2 selection............................................................................................................... 264
Figure 257. Additional Information box ............................................................................................. 264
Figure 258. Routing display .............................................................................................................. 265
Figure 259. DVB path route prot. Highlight ....................................................................................... 265
Figure 260. DVB path route prot. routing display .............................................................................. 266
Figure 261. VC-AIS insertion attribute .............................................................................................. 267
Figure 262. DVB Path route-source prot. create box (step 1)........................................................... 268
Figure 263. Selection of the Primary source..................................................................................... 269
Figure 264. Backup source node selection....................................................................................... 269
Figure 265. Source backup NAP node selection .............................................................................. 270
Figure 266. Source backup NAP selection ....................................................................................... 270
Figure 267. Source backup NAP selected ........................................................................................ 271
Figure 268. Primary source NAP selected........................................................................................ 271

Figure 269. Selection of the first sink................................................................................................ 272
Figure 270. Selection of the second sink .......................................................................................... 272
Figure 271. Routing display .............................................................................................................. 273
Figure 272. Highlight......................................................................................................................... 273
Figure 273. 10 GBE EPL node ......................................................................................................... 274
Figure 274. Create path pop-up menu .............................................................................................. 275
Figure 275. 10 GBE EPL path create-step1 ..................................................................................... 276
Figure 276. 10 GBE EPL path end-point selection ........................................................................... 277
Figure 277. 10 GBE EPL path: Additional Infos ................................................................................ 277
Figure 278. Path list: EPL and compounds....................................................................................... 278
Figure 279. 10 GBE EPL path routing view ...................................................................................... 278
Figure 280. EPL path: Allocate ......................................................................................................... 279
Figure 281. EPL path: Implement ..................................................................................................... 279
Figure 282. EPL path: Implementation log........................................................................................ 280
Figure 283. EPL path: trail activation log .......................................................................................... 280
Figure 284. EPL path: routing view selection.................................................................................... 281
Figure 285. EPL link conn: Server trail selection .............................................................................. 281
Figure 286. EPL link conn: Server trail list ........................................................................................ 282
Figure 287. EPL path: trail list and routing display............................................................................ 282
Figure 288. Trail end points on EML (1)............................................................................................ 283
Figure 289. Trail end points on EML (2)............................................................................................ 283
Figure 290. Port selection ................................................................................................................. 284
Figure 291. Create EVPL path step 1 ............................................................................................... 285
Figure 292. Create EVPL path step 2 ............................................................................................... 285
Figure 293. Create EVPL path:Additional Information ...................................................................... 286
Figure 294. Path list including path evpl ........................................................................................... 286
Figure 295. Routing display of path evpl........................................................................................... 286
Figure 296. Create second EVPL path ............................................................................................. 287
Figure 297. Path list including evpl and evpl_1................................................................................. 288
Figure 298. Trail list........................................................................................................................... 288
Figure 299. Trail routing display........................................................................................................ 289
Figure 300. Path list including the mixed path .................................................................................. 290
Figure 301. Mixed path routing display ............................................................................................. 290
Figure 302. Flow control disabled on NM ......................................................................................... 291
Figure 303. NAP display ................................................................................................................... 291
Figure 304. NAP list .......................................................................................................................... 292
Figure 305. NM:Transmission:Physical Media:Ethernet Port Configuration ..................................... 292
Figure 306. RM: Flow control set to Enabled.................................................................................... 293
Figure 307. RM:Report:Flow control set to Enabled ......................................................................... 293
Figure 308. Flow control enabled on NM .......................................................................................... 294
Figure 309. Path create 1 GbE step1 ............................................................................................... 294
Figure 310. Path create 1 GbE step2 ............................................................................................... 295
Figure 311. Path create 1 GbE step3:LCAS control=Enabled .......................................................... 295
Figure 312. Allocate and Implement path report............................................................................... 296
Figure 313. Path list: the path is implemented .................................................................................. 296
Figure 314. Show/Set attributes. LCAS control=enabled.................................................................. 296
Figure 315. NM: ISA port configuration:LCAS control=enabled........................................................ 297
Figure 316. Path: Ethernet: LCAS Hold Off Time ............................................................................. 297
Figure 317. Dictionary and LCAS set hold off time ........................................................................... 298
Figure 318. LCAS setting Hold Off time report ................................................................................. 298
Figure 319. NM: ISA port configuration............................................................................................. 299
Figure 320. NM: ISA port configuration:Hold Off time=400............................................................... 299
Figure 321. Scenario 1: client failure on bidirectional path ............................................................... 300
Figure 322. Scenario 2: SDH failure on bidirectional path ................................................................ 301

Figure 323. Scenario 3: client failure on unidirectional path ............................................................. 301
Figure 324. Scenario 4: SDH failure on unidirectional path .............................................................. 302
Figure 325. Path between two different ES64 boards ...................................................................... 303
Figure 326. Path between a ES64 and an External Node ................................................................ 303
Figure 327. Path between a ES64 and a 10Gb port on the same node ........................................... 304
Figure 328. Paths created via RM .................................................................................................... 304
Figure 329. Cross-connection scheme ............................................................................................. 305
Figure 330. Create path betw ES64 boards step1 ............................................................................ 306
Figure 331. Create path betw ES64 boards step2 ............................................................................ 306
Figure 332. Create path ES64 to 10Gb port same node step1........................................................ 307
Figure 333. Create path ES64 to 10Gb port same node step2........................................................ 307
Figure 334. BM lock attributes .......................................................................................................... 309
Figure 335. Reference network......................................................................................................... 309
Figure 336. Payload not structured on the physcon ......................................................................... 310
Figure 337. Create path .................................................................................................................... 310
Figure 338. AU4 4-C create path step1 ............................................................................................ 311
Figure 339. AU4 4-C create path step 2 ........................................................................................... 311
Figure 340. AU4 4-C create path step3 ............................................................................................ 312
Figure 341. AU4 4-C create path path report.................................................................................... 312
Figure 342. AU4-4C path:configuration: Modify: Allocate ................................................................. 313
Figure 343. AU4-4C path allocation in progress ............................................................................... 313
Figure 344. AU4-4C path allocation in progress: refresh routing view.............................................. 314
Figure 345. AU4-4C path allocation report ....................................................................................... 314
Figure 346. AU4-4C allocated path routing display .......................................................................... 315
Figure 347. Link conn show: path rate=AU4-4C ............................................................................... 316
Figure 348. Physcon structure: it is not updated............................................................................... 316
Figure 349. AU4-4C path:configuration: Modify: Implement ............................................................. 317
Figure 350. Trail configuration in progress........................................................................................ 318
Figure 351. The trail is configured on path implementation .............................................................. 318
Figure 352. Actual payload structure ................................................................................................ 321
Figure 353. Creation of path 'civetta' with constraint to trail 2........................................................... 322
Figure 354. Path civetta position in trail 2 ......................................................................................... 323
Figure 355. New path create step 1.................................................................................................. 323
Figure 356. New path create step 2.................................................................................................. 324
Figure 357. New path allocated to trail 2, due to defragmentation algorithm.................................... 324
Figure 358. Route report example .................................................................................................... 325
Figure 359. Actual route.................................................................................................................... 327
Figure 360. Path Routing example ................................................................................................... 327
Figure 361. Highlight button.............................................................................................................. 328
Figure 362. Symbols used by Hyghlight feature ............................................................................... 329
Figure 363. Path Locate button......................................................................................................... 329
Figure 364. Example of Path locate on subnetwork map ................................................................. 330
Figure 365. Example of protected Path locate.................................................................................. 330
Figure 366. Locate path: protected on the same link group.............................................................. 331
Figure 367. Service State Modification box and dictionary ............................................................... 332
Figure 368. Mapping between old constraint type and new constraint type ..................................... 335
Figure 369. CTP as constraint. ......................................................................................................... 337
Figure 370. Use Service Forward/Backward for Dual Node SNCP network..................................... 338
Figure 371. Add Constraints button .................................................................................................. 339
Figure 372. Add Constraints start dialog box (step 1)....................................................................... 340
Figure 373. Add Constraints step 2 dialog box ................................................................................. 340
Figure 374. Routing Constraints section........................................................................................... 341
Figure 375. Routing Constraints type ............................................................................................... 342
Figure 376. Add Set button ............................................................................................................... 342

Figure 377. Enter the new constraint name ...................................................................................... 343
Figure 378. Time slot position entry .................................................................................................. 343
Figure 379. Constraint set list ........................................................................................................... 344
Figure 380. The constraint set is executed ....................................................................................... 344
Figure 381. Trail structure (2nd LC at TU3) ...................................................................................... 345
Figure 382. AU4 structure (TU3)....................................................................................................... 345
Figure 383. Path 2Mb: constraint trail wrongly structured................................................................. 346
Figure 384. Setting the position ........................................................................................................ 346
Figure 385. AU4 structure (TU3)after 2Mb path allocation ............................................................... 347
Figure 386. AU4 structure (TU3)after 2Mb path implementation ...................................................... 347
Figure 387. Path: Constraints menu ................................................................................................. 348
Figure 388. Paste Constraints to many paths ................................................................................... 349
Figure 389. Add Leg menu item........................................................................................................ 350
Figure 390. Add Leg dialog box. ....................................................................................................... 350
Figure 391. Drag from browser ......................................................................................................... 351
Figure 392. Add Leg button. ............................................................................................................. 351
Figure 393. Routing display of a broadcast path. ............................................................................. 352
Figure 394. Bidir. Path, 1664SM, RIP ............................................................................................... 354
Figure 395. Bidir path, 1670SM, RIW. .............................................................................................. 355
Figure 396. Drop and Continue D/C W INS W.................................................................................. 357
Figure 397. Drop and Continue......................................................................................................... 358
Figure 398. Drop and Continue - 1st failure...................................................................................... 359
Figure 399. Drop and Continue - 2nd failure..................................................................................... 359
Figure 400. Submaps of 2nd level subnetworks (ET-1 , ET-2, ET-3) for 2 ND&C ............................ 360
Figure 401. Example Network........................................................................................................... 361
Figure 402. Routing view for 2-N D & C path.................................................................................... 362
Figure 403. Status switch subwindows for 2-N D & C....................................................................... 363
Figure 404. Main route connection view detail.................................................................................. 363
Figure 405. CTP name detail. ........................................................................................................... 364
Figure 406. Use Service Forward/Backward for Dual Node SNCP network..................................... 365
Figure 407. Double failure for a SNCP path (w/o enhanced)............................................................ 366
Figure 408. Path routing view (one node D & C) .............................................................................. 367
Figure 409. Enhanced SNCP-one node connection detail. .............................................................. 368
Figure 410. Highlight of a 2 Mb path................................................................................................. 370
Figure 411. Path: Modify: Path Modification Tool .............................................................................. 370
Figure 412. Add Service: Dual Node D & C...................................................................................... 371
Figure 413. Selection of the second termination............................................................................... 371
Figure 414. Terminations selected .................................................................................................... 372
Figure 415. D&C for dual node interconnection on single physical connection ................................ 373
Figure 416. Timeslot interchange ex 1.............................................................................................. 375
Figure 417. Timeslot interchange ex 2.............................................................................................. 375
Figure 418. Time slot interchange mode choice in NPA creation ..................................................... 376
Figure 419. Timeslot interchange attribute........................................................................................ 376
Figure 420. Search from Node: NAPs (with Path information) ......................................................... 377
Figure 421. NAP list .......................................................................................................................... 377
Figure 422. Path/Trail Modification Tool............................................................................................ 378
Figure 423. Path/Trail Modification Tool: add service ....................................................................... 381
Figure 424. Selection of the NPA ...................................................................................................... 383
Figure 425. Dual node drop & continue ............................................................................................ 384
Figure 426. Selection of the connections in topology ....................................................................... 385
Figure 427. 2-node D & C path ......................................................................................................... 386
Figure 428. Main route connection view detail.................................................................................. 387
Figure 429. Add service: single node D & C ..................................................................................... 388
Figure 430. Single node D & C. Switch selection. ............................................................................ 389

Figure 431. Step 2. Selected switches.............................................................................................. 390
Figure 432. Transport reroute step 2 dialog box ............................................................................... 392
Figure 433. Restoration:Create Restoration Rule............................................................................. 393
Figure 434. Create: Restoration Rule. .............................................................................................. 394
Figure 435. Browser: restoration domain.......................................................................................... 395
Figure 436. Restoration Rule list....................................................................................................... 396
Figure 437. Restoration Rule attributes. ........................................................................................... 397
Figure 438. Submaps of SUBN1 and SUBN2................................................................................... 398
Figure 439. Path List containing paths P1 and P2 ............................................................................ 399
Figure 440. Create connection-step 1............................................................................................... 400
Figure 441. Create connection-step 2............................................................................................... 401
Figure 442. Connection between the virtual nodes........................................................................... 402
Figure 443. Payload configuration of the virtual physical connection ............................................... 403
Figure 444. Path Create between external network references........................................................ 404
Figure 445. P1+PV Join path pull-down menu.................................................................................. 405
Figure 446. Join path dialog box (P1+PV=P3).................................................................................. 406
Figure 447. Path list: paths P2+P3 ................................................................................................... 406
Figure 448. Actions: Modification: Join ............................................................................................. 407
Figure 449. Path list after join operation. .......................................................................................... 407
Figure 450. Path P highlighted.......................................................................................................... 408
Figure 451. Actions: Manage path: Split path ................................................................................... 409
Figure 452. Split path dialog box....................................................................................................... 410
Figure 453. Node selection. .............................................................................................................. 410
Figure 454. Trail: Modification: Split .................................................................................................. 411
Figure 455. Split trail dialog box........................................................................................................ 412
Figure 456. Common node selection. ............................................................................................... 412
Figure 457. Split trail report............................................................................................................... 413
Figure 458. Actions: Modifications: Join. .......................................................................................... 415
Figure 459. Trail: Modification: Join dialog box................................................................................. 416
Figure 460. Topology Management pop-up menu. ........................................................................... 417
Figure 461. Split wizard: step1.......................................................................................................... 418
Figure 462. Node list......................................................................................................................... 419
Figure 463. Node inserted. ............................................................................................................... 419
Figure 464. Step 2. First port to use.................................................................................................. 420
Figure 465. Port list........................................................................................................................... 421
Figure 466. Step 2. First port to use.................................................................................................. 421
Figure 467. Split connection summary dialog box. ........................................................................... 423
Figure 468. Restriction on Join physical connections ....................................................................... 424
Figure 469. Join Physical Connections dialog box. .......................................................................... 425
Figure 470. Join Physical Connection report .................................................................................... 426
Figure 471. Path: Alarms: Operations: On Clients: PDH framing ..................................................... 427
Figure 472. ISDN-PRA step 1 dialog box (alarm monitoring type) ................................................... 428
Figure 473. ISDN-PRA step 2 dialog box (Port role assignment) ..................................................... 429
Figure 474. ISDN-PRA: NT Ports selection. ..................................................................................... 430
Figure 475. Ports in node.................................................................................................................. 433
Figure 476. Nap: Path/Trail take-over ............................................................................................... 434
Figure 477. Path/trail take over wizard step 1................................................................................... 435
Figure 480. Path list: uploaded path ................................................................................................. 437
Figure 481. Physical connection:Reroute paths ............................................................................... 437
Figure 482. Reroute paths crossing a physical connection .............................................................. 438
Figure 483. Force path switch (Physcon:Maintenance:Generic) ...................................................... 439
Figure 484. Maintenance wizard....................................................................................................... 440

Figure 485. Path: Modification: Reroute ........................................................................................... 441
Figure 486. Broadcast path to reroute ............................................................................................. 442
Figure 487. Modification: Reroute:Allow traffic impacts .................................................................... 442
Figure 488. Broadcast path has been rerouted ................................................................................ 443
Figure 489. Highlight broad path: physcons list (first level) .............................................................. 443
Figure 490. Highlight 3rd physcon: Reroute paths............................................................................ 444
Figure 491. Reroute Physcon wizard................................................................................................ 444
Figure 492. Select the reroute operation type................................................................................... 445
Figure 493. Destination physcon selection ....................................................................................... 445
Figure 494. Reroute physcon end of selection ................................................................................. 446
Figure 495. List of used physcons (first level) after physcon reroute................................................ 446
Figure 496. Constraint set=last route................................................................................................ 447
Figure 497. Constraint set modification ............................................................................................ 448
Figure 498. Path highlight (application of the constraints) ............................................................... 448
Figure 499. Other:Save and Recall: Recall last saved route ............................................................ 449
Figure 500. Highlight of the recalled route ........................................................................................ 449
Figure 501. Other: Save and Recall: Save Route as Constraint set................................................. 450
Figure 502. Save Route as Constraint set confirmation ................................................................... 451
Figure 503. Save Route as Constraint command log ....................................................................... 451
Figure 504. Constraints wizard ......................................................................................................... 451
Figure 505. Constraint set selection ................................................................................................. 452
Figure 506. Last (saved) route display.............................................................................................. 452
Figure 507. Path: Other: Save and Recall: Recall last saved route.................................................. 453
Figure 508. Warning: traffic hit for not protected path....................................................................... 453
Figure 509. Unsuccessful reroute on the last save route.................................................................. 454
Figure 510. Scheduled action: one shot. .......................................................................................... 455
Figure 511. Scheduled action: periodic task ..................................................................................... 455
Figure 512. Max execution delay: agent state scenario.................................................................... 456
Figure 513. Network Domain: Search: Related Objects: Planned Activities ..................................... 457
Figure 514. Planned Activities list ..................................................................................................... 457
Figure 515. Planned Activities wizard button .................................................................................... 458
Figure 516. Planned Activities wizard: Start...................................................................................... 459
Figure 517. Planned Activities wizard: Select wizard........................................................................ 459
Figure 518. Planned Activities wizard: Select Object step 1............................................................. 460
Figure 519. Planned Activities wizard: selection of the command .................................................... 461
Figure 520. Planned Activities wizard: Select Parameters 1 ............................................................ 462
Figure 521. Planned Activities wizard: Select Parameters 2 ............................................................ 463
Figure 522. Planned Activities wizard: Logger messages ................................................................ 464
Figure 523. Modify schedule wizard ................................................................................................. 465
Figure 524. Adding a new Network Element to a SNCP ring............................................................ 469
Figure 525. Network: Display Related Items..................................................................................... 480
Figure 526. Subnetwork: Display Related Items............................................................................... 481
Figure 527. Node: Display Related Items ......................................................................................... 482
Figure 528. SDH CTP Statistics........................................................................................................ 483
Figure 529. SDH PATHs statistics..................................................................................................... 484
Figure 530. NAPs statistics ............................................................................................................... 484
Figure 531. NODEs statistics ............................................................................................................ 485
Figure 532. Node: Modification: Move Node..................................................................................... 486
Figure 533. Move dialog box............................................................................................................. 487
Figure 534. Network Domain map opened in selection modality...................................................... 487
Figure 535. Network map opened in selection modality ................................................................... 488
Figure 536. 2nd level subnetwork map ............................................................................................. 488
Figure 537. Selection of the Destination topology ............................................................................ 489
Figure 538. Move dialog box: command launch ............................................................................... 489

Figure 539. Moved node in the New Object holding area................................................................. 490
Figure 540. Destination submap after the move operation ............................................................... 490
Figure 541. Multiple move operation................................................................................................. 491
Figure 542. Simplified example of actual network view .................................................................... 493
Figure 543. Network view after the split............................................................................................ 494
Figure 544. Example of wrongly represented path ........................................................................... 495
Figure 545. Paths are correctly represented..................................................................................... 498
Figure 546. Actual network view ....................................................................................................... 499
Figure 547. Path list .......................................................................................................................... 499
Figure 548. Path highlight ................................................................................................................. 500
Figure 549. Path routing display ....................................................................................................... 501
Figure 550. Actual route and correct route ....................................................................................... 502
Figure 551. Virtual node: Modification: Routing domain: Assign ...................................................... 503
Figure 552. Routing domain mng wizard: AUTOMATIC ................................................................... 504
Figure 553. Report ............................................................................................................................ 504
Figure 554. Virtual Node: Search: Items: Ports................................................................................. 505
Figure 555. Virtual node port list ....................................................................................................... 505
Figure 556. Virtual node: Modification: Routing domain: Assign ...................................................... 507
Figure 557. Routing domain mng wizard .......................................................................................... 508
Figure 558. Port list........................................................................................................................... 508
Figure 559. Insert the Routing Domain string ................................................................................... 509
Figure 560. New routing domain name............................................................................................. 510
Figure 561. Port list........................................................................................................................... 511
Figure 562. New routing domain name............................................................................................. 511
Figure 563. Modification: Routing domain: Enable/disable............................................................... 512
Figure 564. Routing domain: Enabled for partitioning....................................................................... 512
Figure 565. Find wrong paths ........................................................................................................... 513
Figure 566. Find wrong paths execute notification ........................................................................... 513
Figure 567. Display the list of the wrong paths ................................................................................. 513
Figure 568. Fix wrong paths ............................................................................................................. 513
Figure 569. Fix wrong paths execution notification ........................................................................... 514
Figure 570. Fixed path routing,according to Figure 550.correct route .............................................. 514
Figure 571. Virtual node: Modification: Routing domain: Enable/Disable ......................................... 515
Figure 572. Enabled for migration..................................................................................................... 515
Figure 573. Virtual node: Modification: Move: Ports ......................................................................... 516
Figure 574. NE migration wizard step 1............................................................................................ 516
Figure 578. Ports assigned to the destination node.......................................................................... 518
Figure 579. Confirm move operation ................................................................................................ 519
Figure 580. Action report .................................................................................................................. 519
Figure 581. Network map after the split ............................................................................................ 520
Figure 582. Path locate..................................................................................................................... 520
Figure 583. Network map and path highlight .................................................................................... 521
Figure 584. Actions: Configure Download: Disable (for the involved nodes) .................................... 522
Figure 585. Node C: Modification: Routing domain: Assign ............................................................. 522
Figure 586. Routing domain mng: enter new domain ....................................................................... 523
Figure 587. Routing domain mng: enter new domain ....................................................................... 523
Figure 588. Node C: Modification: Routing Domain: Enable/Disable ............................................... 524
Figure 589. Routing domain state: enabled for migration ................................................................. 524
Figure 590. Node C: Modification: Move: Ports ................................................................................ 525
Figure 591. NE migration wizard step1............................................................................................. 525
Figure 592. NE migration wizard step2 (drag &drop the destination node) ...................................... 526

Figure 593. NE migration wizard step 3: selection of the destination port ........................................ 526
Figure 594. NE migration wizard step 4: destination port assignment.............................................. 527
Figure 595. NE migration wizard: all ports assigned......................................................................... 527
Figure 596. Confirmation box............................................................................................................ 528
Figure 597. Ports/connections moved from node C to node A ......................................................... 528
Figure 598. Node B: Modification: Move: Ports ................................................................................ 529
Figure 599. NE migration wizard step2 (drag &drop the destination node) ...................................... 529
Figure 600. NE migration wizard: destination port assigned............................................................. 530
Figure 601. Ports/connections moved from node B to node A ......................................................... 530
Figure 602. Actions: Configure Download: Enable (for the involved nodes)..................................... 531
Figure 603. Path highlight ................................................................................................................. 532
Figure 604. Node: Modification: Move: Convert Planned/real port ................................................... 533
Figure 605. Convert Planned/real port step 1 ................................................................................... 534
Figure 606. Convert Planned/real port step 2 ................................................................................... 534
Figure 607. Destination port selected ............................................................................................... 535
Figure 608. Action log ....................................................................................................................... 536
Figure 609. Protection Analyzer Interface......................................................................................... 547
Figure 610. Analyze path example ................................................................................................... 548
Figure 611. Analysis results .............................................................................................................. 548
Figure 612. Check whole network option.......................................................................................... 549
Figure 613. Analyze a subset of paths/trails ..................................................................................... 550
Figure 614. Filter results ................................................................................................................... 550
Figure 615. Filtering Results ............................................................................................................. 551
Figure 616. CSV files on Excel ......................................................................................................... 553
Figure 617. Alarm auto-Synchro after Flooding ................................................................................ 556
Figure 618. Path: Show/Set Attributes: alarm enabling .................................................................... 558
Figure 619. CAP Alarm Enabling. ..................................................................................................... 559
Figure 620. CAP: Show/Set Attributes.............................................................................................. 559
Figure 621. CAP: Show/Set Attributes: alarm enabling .................................................................... 560
Figure 622. Alarm Profile List............................................................................................................ 561
Figure 623. ASAP Creation dialog box. ............................................................................................ 561
Figure 624. Correlating paths ........................................................................................................... 562
Figure 625. Trail: Alarm: Management.............................................................................................. 562
Figure 626. Object correlation to an alarm profile............................................................................. 563
Figure 627. Alarm profile list ............................................................................................................. 564
Figure 628. ASAP selected............................................................................................................... 565
Figure 629. Auto Mode Disabled/Enabled ........................................................................................ 565
Figure 630. ASAP Profile attributes. ................................................................................................. 566
Figure 631. Alarm Management Icons.............................................................................................. 587
Figure 632. Counter summary window ............................................................................................. 591
Figure 633. Physical Connection Alarm sublist................................................................................. 591
Figure 634. Navigation: External Application: 1354RM. ................................................................... 592
Figure 635. Path alarm sublist .......................................................................................................... 592
Figure 636. Path Naps view.............................................................................................................. 593
Figure 637. Path Alarm details.......................................................................................................... 593
Figure 638. Physical connection structure window ........................................................................... 594
Figure 639. Alarm details window. .................................................................................................... 594
Figure 640. HO-trail alarm sublist ..................................................................................................... 595
Figure 641. Trail structure ................................................................................................................. 595
Figure 642. Alarmed object list ......................................................................................................... 596
Figure 643. Example of alarm detail ................................................................................................. 596
Figure 644. MS Trail alarm sublist. ................................................................................................... 597
Figure 645. MS-trail structure ........................................................................................................... 597
Figure 646. Alarm details. ................................................................................................................. 598

Figure 647. OMS trail structure......................................................................................................... 598
Figure 648. EML sublist .................................................................................................................... 599
Figure 649. EML navigation .............................................................................................................. 599
Figure 650. EML Show/Set Attributes............................................................................................... 600
Figure 651. Client path routing view ................................................................................................. 601
Figure 652. Alarm detail list .............................................................................................................. 601
Figure 653. NE Alarm Sublist............................................................................................................ 601
Figure 654. NE Navigation................................................................................................................ 601
Figure 655. Path 2Mb:Search:All Related Items............................................................................... 602
Figure 656. Alarmed Transport Objects at Server Layer .................................................................. 602
Figure 657. List of Alarmed Transport Objects from trail .................................................................. 603
Figure 658. List of Alarmed Transport Objects from trail .................................................................. 603
Figure 659. Alarmed Transport Objects icon .................................................................................... 604
Figure 660. Example of WDM map................................................................................................... 604
Figure 661. Highlight of the server WDM path (client path) ............................................................. 605
Figure 662. List of Alarmed Transport Objects from path in WDM network ...................................... 605
Figure 663. Allocation failure management ...................................................................................... 624
Figure 664. Path List......................................................................................................................... 625
Figure 665. Netscape Path/Trail allocation failure. ........................................................................... 626
Figure 666. Failed Object frame ....................................................................................................... 627
Figure 667. Netscape Path Trail allocation failure: problem summary frame. .................................. 628
Figure 668. ProblemType and Constraint list.................................................................................... 628
Figure 669. Route display components. ........................................................................................... 629
Figure 670. END 1 / END 2 termination point names. ...................................................................... 629
Figure 671. Problem Detail frame. .................................................................................................... 630
Figure 672. Netscape Path/Trail allocation failure description window. ............................................ 630
Figure 673. Generic Help on allocation failure.................................................................................. 631
Figure 674. Example of problem description .................................................................................... 631
Figure 675. Problem menu list .......................................................................................................... 632
Figure 676. Example of display of a protected path.......................................................................... 633
Figure 677. Example of display of a protected path.......................................................................... 634
Figure 678. Constraint List................................................................................................................ 635
Figure 679. Processed Constraint List.............................................................................................. 636
Figure 680. Examples of interpretation of the Constraint list rows.................................................... 637
Figure 681. Example of OTHER ERRROR display .......................................................................... 638
Figure 682. state diagram ................................................................................................................. 640
Figure 683. state A: 2 HO trails (A, B) .............................................................................................. 641
Figure 684. state H: 1 HO trail (C) .................................................................................................... 641
Figure 685. bidirectional protected path............................................................................................ 647
Figure 686. unidirectional protected path (using working resource between nodes E and D) .......... 648
Figure 687. unidirectional protected path (using protection resource between nodes E and D) ...... 648
Figure 688. broadcast protected path ............................................................................................... 649
Figure 689. 4 fibre MS SP reporting screen...................................................................................... 655
Figure 690. ConfigurationState = “virtual" icon ................................................................................. 655
Figure 691. ConfigurationState diagram ........................................................................................... 656
Figure 692. ConfigurationState = “enabled"/"active" icon ................................................................. 658
Figure 693. MidProtocolRole ( NODE CONDITION ) icons .............................................................. 658
Figure 694. WestProtocolRole icons................................................................................................. 659
Figure 695. EastProtocolRole icons.................................................................................................. 659
Figure 696. East/West failure Of Protocol......................................................................................... 660
Figure 697. East/West ring active condition...................................................................................... 660
Figure 698. East span active condition ............................................................................................. 661
Figure 699. West span active condition ............................................................................................ 661
Figure 700. East / West ring pending command ............................................................................... 661

Figure 701. East span pending command ........................................................................................ 662
Figure 702. West span pending command ....................................................................................... 662
Figure 703. East / West Lockout Working Ring ................................................................................ 662
Figure 704. East / West Lockout Working Span................................................................................ 663
Figure 705. Bi-directional Signal Fail / Ring...................................................................................... 664
Figure 706. Bi-directional Signal Fail / Ring cleared .WTR............................................................... 665
Figure 707. Double Bi-directional Signal Fail / Ring ......................................................................... 666
Figure 708. Forced Switch / Ring...................................................................................................... 667
Figure 709. Double Forced Switch / Ring to different nodes, node isolated ..................................... 668
Figure 710. Double signal Fail / ring, node isolated.......................................................................... 669
Figure 711. Forced Switch / Span ..................................................................................................... 670
Figure 712. Signal Fail / Ring pending, Forced Switch / Ring pending............................................. 671
Figure 713. Signal Fail Span, Signal Fail / Ring pending.................................................................. 672
Figure 714. Span Switch Request: Exercise East menu option........................................................ 673
Figure 715. Span Switch Request: Exercise East............................................................................. 674
Figure 716. Ring Switch Request: Exercise East menu option......................................................... 675
Figure 717. Ring Switch Request: Exercise East ............................................................................. 675
Figure 718. 1353NM map: misaligned NE ........................................................................................ 677
Figure 719. Path list: the path is disabled (OOS).............................................................................. 678
Figure 720. NE: Consistency Audit menu ......................................................................................... 678
Figure 721. Consistency report......................................................................................................... 679
Figure 722. Node list......................................................................................................................... 680
Figure 723. Consistency report......................................................................................................... 681
Figure 724. Consistency Download pop-up menu ............................................................................ 681
Figure 725. Confirmation dialog box. ................................................................................................ 682
Figure 726. Consistency download report ........................................................................................ 682
Figure 727. Physical Conn: Configuration: Trace Identifier............................................................... 688
Figure 728. Section Trace Identifier wizard: Step 1 .......................................................................... 689
Figure 729. Section Trace Identifier wizard: step 2........................................................................... 690
Figure 730. Section Trace Identifier dialog box................................................................................. 691
Figure 731. Trail: Configuration: Trace Identifier Management......................................................... 693
Figure 732. Trace Identifier wizard: Step 1 ....................................................................................... 694
Figure 733. Trace Identifier definition................................................................................................ 695
Figure 734. Path: Configuration: Trace Identifier .............................................................................. 696
Figure 735. Path trace identifier step 1 ............................................................................................. 697
Figure 736. Path trace identifier definition. ....................................................................................... 698
Figure 737. Configuration: Tandem Connection pop-up menu item ................................................. 701
Figure 738. Tandem Connection Management wizard ..................................................................... 702
Figure 739. Action selection radio buttons........................................................................................ 703
Figure 740. Tandem Connection create-step 2-TP selection............................................................ 703
Figure 741. TCT attributes specification ........................................................................................... 704
Figure 742. Path routing display ( tandem flag ) ............................................................................... 705
Figure 743. Path routing view: tandem flag ...................................................................................... 706
Figure 744. Path icon on browser: tandem connection state icon .................................................... 706
Figure 745. Tcm/tct list selection....................................................................................................... 707
Figure 746. Tcm/Tct list. .................................................................................................................... 707
Figure 747. Path NAPs view with TC................................................................................................ 708
Figure 748. Tandem Connection wizard ........................................................................................... 710
Figure 749. Path: Configuration: POM on Ctps pop-up menu. ......................................................... 712
Figure 750. Routing Display: path CTP ............................................................................................ 713
Figure 751. CTP: Trace identifier read.............................................................................................. 714
Figure 752. Nap: Manage Loopback................................................................................................. 715
Figure 753. Loopback active............................................................................................................. 716
Figure 754. Nap loopback status supervision ................................................................................... 717

Figure 755. CTP: Internal Loopback: Set.......................................................................................... 718
Figure 756. CTP: Internal Loopback display..................................................................................... 719
Figure 757. Path:Manage SNCP menu. ........................................................................................... 720
Figure 758. Example of display of a B & S connection in topology. .................................................. 722
Figure 759. Report. ........................................................................................................................... 723
Figure 760. Connection in topology attributes. ................................................................................. 723
Figure 761. HO-Trail with and without enhanced connectivity .......................................................... 724
Figure 762. Effect of a BRIDGE EAST ............................................................................................. 725
Figure 763. Effect of a BRIDGE WEST ............................................................................................ 726
Figure 764. Effect of a SWITCH EAST ............................................................................................. 726
Figure 765. Effect of a SWITCH WEST ............................................................................................ 727
Figure 766. :Example of six nodes ring............................................................................................. 729
Figure 767. Step 4: Final situation .................................................................................................... 730
Figure 768. Drop and Continue at the service nodes. ...................................................................... 731
Figure 769. Example of squelching table configuration .................................................................... 733
Figure 770. MS-Spring: Display All related items.............................................................................. 738
Figure 771. Examples of actual position of the switches. ................................................................. 738
Figure 772. PM functional buttons in the browser window................................................................ 740
Figure 773. Measure Creation dialog box......................................................................................... 741
Figure 774. PM domain related items ............................................................................................... 743
Figure 775. Measure list ................................................................................................................... 744
Figure 776. Measure: Actions pull-down menu................................................................................. 745
Figure 777. Transport correlation to a measure................................................................................ 746
Figure 778. Path: Actions:PM: Add Measure.................................................................................... 747
Figure 779. Performance Measurement: Add to dialog box ............................................................. 747
Figure 780. Correlate measure to path ............................................................................................. 748
Figure 781. Performance Monitoring: Correlate to Measure............................................................. 749
Figure 782. Measure TP list.............................................................................................................. 749
Figure 783. PM tp related items........................................................................................................ 750
Figure 784. PM tp view ..................................................................................................................... 751
Figure 785. MS trail: PM: Add measure............................................................................................ 752
Figure 786. Correlate measure wizard.............................................................................................. 753
Figure 787. List of Measures ............................................................................................................ 753
Figure 788. Correlate measure wizard: Finish .................................................................................. 754
Figure 789. MS trail: Monitoring Measures ....................................................................................... 754
Figure 790. Measure: button PM Transports. ................................................................................... 754
Figure 791. Transport: button PM Tps .............................................................................................. 755
Figure 792. List of the PmTps ........................................................................................................... 755
Figure 793. PMTP Show / Set Attributes .......................................................................................... 757
Figure 794. Side of the pmctps in a b&s connection ( signal from NE-A to NE-B ) .......................... 759
Figure 795. Side of the pmctps in a b&s connection ( signal from NE-B to NE-A ) .......................... 759
Figure 796. Side of the ctp/nap for a unidirectional connection ........................................................ 759
Figure 797. Counter Report Create .................................................................................................. 760
Figure 798. Counter Report profile list. ............................................................................................. 761
Figure 799. Counter report profiles. .................................................................................................. 761
Figure 800. Example of generated counter report ............................................................................ 762
Figure 801. Create: Threshold Report dialog box............................................................................. 764
Figure 802. Threshold Report Profile list. ......................................................................................... 765
Figure 803. Threshold report icon..................................................................................................... 765
Figure 804. Measure correlation pop-up menu................................................................................. 766
Figure 805. Correlate report.............................................................................................................. 766
Figure 806. TCA Profile creation....................................................................................................... 770
Figure 807. PMTP: Perform.Monitoring: Correlate to TCA ............................................................... 771
Figure 808. Measure merging........................................................................................................... 772

Figure 809. pmNE Show/Set attributes............................................................................................. 773
Figure 810. PM tp view ..................................................................................................................... 775
Figure 811. Object containment tree ................................................................................................. 779
Figure 812. Create: Physcon ............................................................................................................ 781
Figure 813. Create: Physcon: SDH,rate,name ................................................................................. 782
Figure 814. Create: Physcon: used for Test...................................................................................... 782
Figure 815. Create: Physcon: virt port label...................................................................................... 783
Figure 816. Create: Physcon: port selection..................................................................................... 783
Figure 817. Create: Physcon: Action report...................................................................................... 784
Figure 818. Port Show attr: used for test .......................................................................................... 784
Figure 819. Physcon: Configuration: Implement............................................................................... 784
Figure 820. Physcon structure .......................................................................................................... 785
Figure 821. Detail of the physcon link ............................................................................................... 785
Figure 822. Selection of paths crossing the physcon ....................................................................... 785
Figure 823. 1st CTP: Test Port: Addition Tool ................................................................................... 786
Figure 824. Test Port Addition Tool ................................................................................................... 786
Figure 825. Test Port Addition Tool: port selection............................................................................ 787
Figure 826. Test Port Addition Tool: payload position selection ........................................................ 787
Figure 827. Test Port present............................................................................................................ 788
Figure 828. Cross connection details................................................................................................ 788
Figure 829. Physcon structure: test path present ............................................................................. 789
Figure 830. 2nd CTP: Test Port: Addition Tool.................................................................................. 789
Figure 831. Test Port Addition Tool (CTP already selected) ............................................................. 789
Figure 832. Test Port Addition Tool: left scroll payload position ........................................................ 790
Figure 833. Test Port Addition Tool: right scroll payload position...................................................... 790
Figure 834. Test Port Addition Tool: Finish ....................................................................................... 791
Figure 835. Forward and Backward Test Ports present .................................................................... 791
Figure 836. Forward and Backward Test Ports creation report......................................................... 791
Figure 837. Forward and Backward Test paths ................................................................................ 792
Figure 838. Test Port: Remove ......................................................................................................... 792
Figure 839. Remove test port log...................................................................................................... 793
Figure 840. 1st Test port icon on CTP removed .............................................................................. 793
Figure 841. Multiple test port remove ............................................................................................... 794
Figure 842. Multiple test port addition............................................................................................... 794
Figure 843. Test Port addition tool (multiple) .................................................................................... 795
Figure 844. 1st CTP connection ....................................................................................................... 795
Figure 845. 1st CTP connection: setup............................................................................................. 796
Figure 846. 2nd CTP connection: setup ........................................................................................... 796
Figure 847. Path 2 Mb with test ports ............................................................................................... 797
Figure 848. Test Port: Test Port Addition Tool................................................................................... 797
Figure 849. Test Port Addition Tool ................................................................................................... 798
Figure 850. Test termination selection (NAP) ................................................................................... 798
Figure 851. Test termination selected ............................................................................................... 799
Figure 852. Added connection to the test port .................................................................................. 799
Figure 853. Configuration: Cross Connection................................................................................... 800
Figure 854. Cross Connection list..................................................................................................... 800
Figure 855. The 1354RM in the SDH management hierarchy.......................................................... 804
Figure 856. Protected path routes ( automatic algorithm )................................................................ 806
Figure 857. Collapsed dual node interconnection between two rings............................................... 807
Figure 858. Stacked rings ................................................................................................................ 808
Figure 859. NPA routing attributes effects in stacked rings ............................................................. 809
Figure 860. NPA Main & Spare Factor effects in stacked SNCP rings ............................................. 810
Figure 861. Routing in stacked MS-Springs - primary and secondary nodes not adjacent ............. 811
Figure 862. Routing in stacked MS-Springs - primary and secondary nodes adjacent ................... 811

Figure 863. Collapsed dual node D&C for SNCP ring ...................................................................... 812
Figure 864. Collapsed single node D&C for SNCP ring.................................................................... 813
Figure 865. Collapsed dual node D&C for SNCP ring ...................................................................... 813
Figure 866. Collapsed dual node D&C inter-working for 2f MS-Spring - config 1 ............................. 814
Figure 867. Collapsed dual node D&C inter-working for 2f MS-Spring - config 2 ............................. 814
Figure 868. Paths in stacked MS-SPrings ....................................................................................... 815
Figure 869. Extracosts ...................................................................................................................... 820
Figure 870. Example: setUpPriority_2 > priority_1 ........................................................................... 825
Figure 871. Schematic representation of the NE .............................................................................. 828
Figure 872. Trail and link connections .............................................................................................. 828
Figure 873. Objects involved in the structure.................................................................................... 829
Figure 874. WDM network managed model. .................................................................................... 830
Figure 875. WDM model. .................................................................................................................. 831
Figure 876. SDH-WDM interconnection scheme .............................................................................. 833

LIST OF TABLES
Table 1. Handbooks related to the specific software application ...................................................... 30
Table 2. Documentation on CD-ROM ............................................................................................... 30
Table 3. Items selection in the Browser ............................................................................................ 89

List of Tables 3AL 61269 AAAA Issue 4 25/854
26/854 3AL 61269 AAAA Issue 4 List of Tables
PREFACE
Preliminary Information
WARNING
ALCATEL makes no warranty of any kind with regards to this manual, and specifically disclaims the
implied warranties of merchantability and fitness for a particular purpose. ALCATEL will not be liable
for errors contained herein or for damages, whether direct, indirect, consequential, incidental, or spe-
cial, in connection with the furnishing, performance, or use of this material.
NOTICE
The product specification and/or performance levels contained in this document are for information
purposes only and are subject to change without notice. They do not represent any obligation on the
part of ALCATEL.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL and must not be copied, repro-
duced or disclosed to a third party without written consent.
TECHNICAL SUPPORT
Please contact your Local Alcatel Technical Assistance Center for questions reffered to the infor-
mation contained in this document.
To send your comments about this handbook please follow the indication on Customer Documen-
tation Feedback on page 853.

Preface 3AL 61269 AAAA Issue 4 27/854
Applicability
This handbook applies to following product–releases:
PRODUCT
1354RM
PRODUCT RELEASE VERSION (N.B.)
1354RM 7.4F 7.5.0
N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

Handbooks relevant to software applications are not modified unless the new software "ver-
sion" distributed to Customers implies man-machine interface changes or in case of slight mod-
ifications not affecting the understanding of the explained procedures.
Moreover, should the screen prints included in the handbook contain the product–release's
"version" marking, they are not replaced in the handbooks related to a subsequent version, if
the screen contents are unchanged.
Scope
This document aims to describe the 135RM Subsystem functionalities to manage a Network of regional
entity.
This document is intended to 1354RM Operators.

28/854 3AL 61269 AAAA Issue 4 Preface
History
ISSUE DATE DESCRIPTIONS
01 April 2008 Rel 7.4F (version 7.4.9)

Reroute of broadcast paths (section Operation)
Loopback management improvement (section Operation)
GMPLS support for 10GBE EPL (section Operation)
Ethernet auto negotiation for single port of a path (section Operation)
Alarm tables update (Section Maintenance)
Low BER management on 1626LM.(section WDM)
ES64 support in 1678MCC-10Gb paths (section Operation)
Management of GMRE installation version (section ASON)
GMRE node auto-restoration deactivation (section ASON)
R-OADM management in 1626LM R5.0 (section WDM)
T&R-OADM management in 1626LM R5.0 (section WDM)
OCH trail management by user (section WDM)
02 June 2008 Rel 7.4F (version 7.4.9)

Protection Analyzer Tool (section Operation)
Flexible X-connections (section WDM)
03 December 2008 Added Flexible X-connections procedures (section WDM)

Added PM on MS trail, Force Collection and update PM paragraph
(section Maintenance)
Added note to Join Physcons (section Operation)
Added Remove Node (section WDM)
04 May 2009 Added note to PM on MS trail (section Maintenance)

Added pl step to Remove DS trail (section WDM)
Added note (restart FEP) to NPA ASON implementation (section
ASON)
Improved note on multi-path create (section Operation)

Related Documents
The list of handbooks given here below is valid on the issue date of this
Handbook and can be changed without any obligation for ALCATEL to
update it in this Handbook.
Some of the handbooks listed here below may not be available on the
issue date of this Handbook.
The standard Customer Documentation in the English language for the equipment whose product–
release–version is stated in “Applicability” on page 28 consists of the following handbooks:
Table 1. Handbooks related to the specific software application
REF HANDBOOK Part Number Notes
[1] 1354RM Rel.7.4F

3AL 61269 CAAA
Administration Guide
[2] 1354RM Rel.7.4F - Basic Network Management THIS

3AL 61269 AAAA
User’s Guide HANDBOOK
[3] 1354RM Rel.7.4F- Advanced Provisioning

3AL 61269 BAAA
User’s Guide
Table 2. Documentation on CD-ROM
REF Documentation CD-ROM TITLE Part Number
1354RM Rel.7.4F CD-ROM-DOC EN 3AL 61278 AAAA
Contains handbooks REF.[1] to [2] in electronic format.

Tipically envisaged after the release of the handbooks.
HANDBOOKS RELATED TO THE PRODUCT'S HARDWARE
Refer to WS supplier handbooks.

In particular refer to such handbooks to obtain the following information (where applicable):
– COMPLIANCE WITH EUROPEAN NORMS

– SAFETY RULES
• General rules
• Harmful optical signals
• Risk of explosion
• Moving mechanical parts
• Heat-radiating Mechanical Parts
– ELECTROMAGNETIC COMPATIBILITY (EMC)
– ELECTROSTATIC DISCHARGERS (ESD)
– EQUIPMENT LABELS
– DISMANTLING & RECYCLING

Handbook Structure
This handbook has been edited according to the Alcatel standardized “drawing-up guides" complying with
such suggestion.
N.B. The 1354RM user documentation is split in two handbooks.
The first document (the document you are reading) contains the basic network management
description, it contains also the product overview and the graphical inteface description. The
main argument is the SDH network provisioning.
The second document describes particular network provisioning : WDM, ASON and Ethernet
provisioning.
This handbook is divided into the main topics described in the table of contents:
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.
GETTING STARTED This section aims introducing the 1354RM working environment, to
the users of the system, in terms of getting access to the system, the
environment utilities, the existing 1354RM functionalities and nav-
igation through the system
OPERATION This section describes the main steps required for the construction
of the network.
MAINTENANCE The aim of this section is to describe the operations related to the
maintenance of the protection network controlled by the 1354RM.
TECHNICAL ANNEXES The aim of this chapter is to give specific technical details on
1354RM functionalities
ABBREVIATIONS: The abbreviation list is supplied.
INDEX Index references are inserted
CUSTOMER DOCUMENTA- It contains info regarding customer opinions collection about this
TION FEEDBACK documentation.

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

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

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

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

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

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

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

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

1 Getting Started
1.1 Introduction
This chapter covers the following topics:
• 1354RM Overview
• Graphical User Interface Principles
• Preliminary Operations
• Access to the main functionalities
• Map navigation
• Browser
1.2 Overview
1.2.1 The Regional Manager in the controlled network

Main Product are: (please refer to the relevant documentation for further info).
1353NM is the Common Element Management Layer OS which can manage a large number of NE ver-
sions and types.
1354BM is the NML application for managing Ethernet services.
1354SN is the NML application for managing Submarine Line Systems.
1354NP is the Fast Restoration NML application for controlling DXC meshed backbone networks.
1355VPN permits to manage Optical Virtual Private Networks at the end Customer premises.
1355ONE (Optical Network Engineering) is a network analyser.
1354RM provides the management of SDH/SONET, WDM, ASON and NP(Fast Restoration) sub-net-
works. Via the 1353NM, 1354RM controls the Network Elements.
1.2.2 Topological Components

– Network: A path that crosses two Networks cannot be managed by 1354RM as a single transport
entity (i.e. it will be represented with two paths)

Getting Started 3AL 61269 AAAA Issue 4 37/854
– Subnetwork: A Network can be composed by more than one sub-network
– 2nd level Subnetwork: It represents a partitioning of a sub-network.
– Node: It represents the image of a Network Element.
– Physical Connection: It is the logical representation of fibers and coaxial cables, between network
ports
– EML Domain: It represents one EMLIM component of 1353NM.
– NE: It represents a physical NE.Network port. It represents the physical port where e.g. the fiber is
connected.
Example:
A STM-16 port of a SDH NE.
An OTS port of a DWDM NE.
– Access port: It represents the physical port where the client signal is added/dropped.
Example:a PDH port of a SDH NE.
1.2.3 Transport Entities

– Section: It is a trail at Multiplex Section Layer.
Example:
MS-Trail between two STM-n ports of two adjacent SDH NEs.
OMS-Trail between two OTS ports of two adjacent DWDM NEs.
– HO (Higher Order) Trail: An HO Trail is a HO route (e.g. infrastructure pipe) between two (either
adjacent or not) SDH NEs. It is delimited by two CAPs (Client Access Points) and it can be configured
to carry LO traffic.
– Path: A path (can be at either HO or LO path layer) is a route established in the SDH/SONET net-
work. It is delimited by NAPs (Network Access Points).
Example: A VC-12 path delimited by two VC-12 NAPs
– Link Connection: It is an arc delimited by the two CTPs with the same timeslot and it is supported
by the same server Trail
Example: An Au-4 Link Connection is delimited by two corresponding AU-4 CTPs and it supported
by a MS-Trail.
1.2.3.1 Network Construction
The operator can:

– Define the submaps according to the preferred network partitioning
– Define the physical connections
– Define the Network Protection Architectures one per each 2nd level subnetwork
To each access port the related Network Access Point is available.
Moreover the following feature is available:
– Add/Remove Network Element in Sub-network and in Elementary Topology including Join/Split

Physical Link Connection management.
• The map provides a network view partitioned in sub-networks, which can be partitioned in 2nd
level subnetworks, and nodes (sub-maps may have a geographical background). This map rep-
resentation is created during the network construction process.

38/854 3AL 61269 AAAA Issue 4 Getting Started
The different views are organized in hierarchical trees. Zooming operations allow the user to navigate
through a tree of hierarchical views.
1.2.3.2 Path Management
1354RM can manage the following path categories:
• Terminated, non terminated

• Unidirectional, bi-directional
• Point-to-point, point-to-multipoint
• Unprotected, end-to-end protected, enhanced protected by means of “drop and continue" facil-
ities,
– With automatic/semi-automatic protected or not protected route selection.
A path can be in the defined, allocated, implemented, and commissioned state. The picture describes the
admitted state transitions.
Figure 1. Path configuration status states
In the next paragraphs the description of management of these phases is provided.
1.2.3.3 Path Definition
During this phase the path description is stored in the data base; in the following the main information are
listed:
– Path name
– Path type (i.e. unidirectional, bidirectional or point to multipoint)
– Protection type
– Rate
– A-End and Z-End points
– Allocation/implementation rules
– Alarm enable/disable for the involved path up to the commissioning state.

1.2.3.4 Path Allocation
The path allocation can be performed either automatically (i.e. immediately after the creation) or manually
on user request.
During this phase the idle resources (link connections, cross-connections) are selected in order to assign
them to the path.
The routing search is performed on a lower cost basis applying the Dijkstra cost model, which assigns a
cost value to all relevant resources. The cost model is dynamic and it is influenced by the presence of pro-
tections.
Upon operator request the cost values can be:
– modified by the operator himself or
– automatically modified, in order to provide a balanced load of the network when resources become
scarcer.
When this activity is successfully terminated, the selected resources are locked; please notice that at the
end of this phase the path does not yet exist in the network.
1.2.3.5 Path Implementation
The path implementation can be performed either automatically after allocation or later, on user request.
During this phase, 1354RM sends the proper cross-connection (identified at allocation time) messages
to the relevant NEs via 1353SH/GEM.
Only if this scenario is successfully completed, the path becomes implemented, i.e. a real connection
between the selected endpoints exists in the network.
In this state it is possible to activate loop-backs on ports, in order to validate the path itself.
1.2.3.6 Path Commissioning
When test activities are terminated, the path is ready for service and the operator can declare it commis-
sioned. The alarm reporting related to the path is enabled, just in case it was inhibited before.
1.2.4 1330AS
1330AS is an ALMAP Generic Component, which is in charge to manage the network alarms generated
by 1354RM as soon as an elementary alarm affects a network resource (e.g. path, trail).
1330AS is the entry point for the operator to perform fault management and fault localization and it provide
capabilities for define alarm synthesis, alarm acknowledge, alarm archiving etc.
1.2.5 System Management Features

Main system utilities are:
– Operator Administration functions: Add Operator, Remove Operator, List Operators, Change
Password, List Current Login, List Successful Login and List Unsuccessful Login.
– Console Administration functions: Add Operator Console, Remove Operator Console, List Oper-
ator Consoles, Lock Operator Console and Unlock Operator Console.
– System Log functions: List System Messages, List Archived Messages and List restored Mes-
sages.

– Periodic Actions functions: Show Scheduling Time, Set Scheduling Time and Cancel Scheduling
Time, bearing in mind that the term “periodic actions" here refers to System Management Functions.
Also, the communication between the 1354RM and the registered Element Managers is tested peri-
odically, being an alarm generated when a communication test fails.
– Backup & Restore functions: It is possible to automatically back-up data periodically, since on-line
full backup is supported. It is possible to do a complete full backup on Operator request and to get
information on planned actions. It is possible to disable automatic operation and restore a full or an
incremental backup. Restore is off-line and 1354RM shall be previously shutdown.
– System Start/Stop functions: Start System, Stop System, Show System State, Auto-start Enable/
Disable and Show Auto-start State.
1.2.6 Fault Management

Incoming NE elementary alarms are managed by 1354RM in order to detect which network entities (e.g.
paths, trails) are impacted and to notify, if any, to the operator the resulting network alarm(s).
The elementary alarms are processed prioritizing, root problems against the effects. In case of alarm
flooding, 1354RM continues to process the primary alarms, discarding, if necessary, the secondary ones.
When this abnormal condition is finished, 1354RM can execute the alarm resynchronization.
The network alarms are generated by the system for physical connections, trails, and paths.
The severity of this type of alarms can be modified relying on the alarm severity assignment profile man-
agement available in 1354RM.
For the path and HO-trail alarms, the alarm is generated when the traffic is affected.
Each network alarm (X.733 compliant) provides information about the affected resource, alarm type, prob-
able cause, severity, timestamp and so on.
All the current network alarm information is shown to the operator in the current alarms list. The alarm
fields are customizable by the user. After the operator acknowledgement and alarm clearing the network
alarm is moved into the historical alarm log. As default, the system provides alarms counters related the
total alarms in the domain and to each managed alarm severity (critical, major, minor, warning, indeter-
minate), and cleared alarms. The user can define other type counters according his needs.
Starting from the alarm list it is possible for a specific network alarm to retrieve information about the ele-
mentary alarms correlated to it.
Network management topological objects (NE, ring, sub-network,...) containing the alarmed object (TP,
port, ...) are graphically displayed according the color of the highest alarm severity.

Figure 2. Alarm navigation
Log consultation and report generation are allowed by the system.

The alarm information can be made available to external system (via Ioo).

1.2.7 Performance Monitoring Management
In order to manage PM Data for Quality Of Service (QoS) and maintenance correlated to services (e.g.
paths), 1354RM provides a dedicated application.
The operator can manage PM measures, which can group together a set of transport entities (paths or
trails) having a common performance goal.
A measure (with 15 minutes and/or 24 hours periodicity) allows to collect the PM counters belonging to
specific Termination Point (TP) in order to control the performance of the related transport entities.
After the selection of a transport entity, 1354RM selects, as monitored points, the termination points of the
transport entity, e.g. for a path will select NAPs or border CTPs depending it is terminated or not.
Intermediate CTPs of a transport entity can be monitored as well.
Depending on the capability offered by the NEs, the operator can define and activate the Threshold Cross-
ing Alarm profiles for NAPs and CTPs.

1.3 REGIONAL Manager graphical user interface principles
1.3.1 Generalities
The users work environment can be partitioned into the following utilities:
– Keyboards: the different keys and the actions they induce will be defined.
– Mouse: the operation of the different buttons will be explained.
– Workspace: A workspace is the screen area where you bring the applications needed for your work.
– Icon: A small, graphic representation of an object on the workspace.
– Windows: the window's general layout, menu and configuration (size) will be described.
– Dialogue Boxes:
1.3.1.1 Mouse buttons
There are 3 Mouse buttons. The actions that are undertaken using the different mouse buttons depends
on their configuration.
– Select button: enables you to select objects (mouse button 1).

– Drag button: enables you to drag objects (mouse button 2).
– Custom button: enables you to generate pop-up menus (mouse button 3).
With a left handed mouse configuration, button 3 becomes the select button.
1.3.1.2 Select/Deselect/Drag-and-Drop functionalities
– Selecting an object: first move the mouse pointer to the object. Then select the object by clicking
on it with the "Select" mouse button. The object appearance changes indicating that it has been
selected.
– Drag-and-drop mouse functionality: used for displacing objects or icons on the workspace. To use
it, first move the mouse pointer to the object you wish to move. Then press, and hold down, the Drag
mouse button and drag the object to the chosen area using the mouse. When the object has reached
the chosen area, release the mouse button.
1.3.1.3 Double clicking
It can be used:
a) To open an object (file, directory..).

– Place the mouse pointer over the object you wish to open.
– Click twice, rapidly, using the "Select" mouse button on the object.
– The mouse pointer will take the work in progress representation until the object should open.
b) To open a symbol submap or the object view (this refers to the Operation Construction manual).
– Place the mouse pointer over the symbol whose submap you wish to open.
– Click twice, rapidly, using the "Select" mouse button on the object.
– The mouse pointer will take the work in progress representation until the symbol's submap should open.
c) To select from a list of selectable feature or function and confirm by pressing OK ( SMF context )
d) To get the selectable list of the object related items (browser context)

1.3.2 Windows
This section describes some particular aspects of the windows.
1.3.2.1 Window menu
Enables operations to be undertaken on the window.
To open the window menu, click on the window menu button using the "Select" mouse button. You can
then select an item from the pull down menu that appears. The window menu options are shown in the
figure below.
1.3.2.2 Scroll bars
There are three ways to use scroll bars:
– Using the stepper arrows.

Place the mouse pointer on the stepper arrow and click on it using the "Select" mouse button. The
contents in the client area are displaced only one unit in the direction indicated by the stepper arrow.
– Using the scroll regions.

Place the mouse pointer in the scroll region outside the sliders. Click, using the "Select" mouse but-
ton. The contents in the client area are displaced one window length.
– Using the sliders.

Place the mouse pointer on the slider. Drag, using the "Select" mouse button, the slider in the direc-
tion desired. The contents in the client area are displaced as long as the slider moves.
1.3.2.3 Buttons
1.3.2.3.1 Push buttons
Push buttons are identified by two characteristics:
– The graphical image representing the button. The buttons are generally of rectangular or square shape.
– The label identifying the action associated with the button. The label is placed on the button.
1.3.2.3.2 Radio buttons
Each radio button represents a single choice selection. Selecting one radio button automatically deselects
the others in the set.

1.3.2.4 Menus
Main menu types are:
– menu bars,
– pull down menus,
– pop-up menus.
These types of menus are described in detail below. The details concern a view of the menu types on real
windows.
1.3.2.4.1 Menu bars
They are present at the top of a window, under the title of the window. They appear automatically along
with the window. An example is given in the figure below. They contain the titles from which pull down
menus and cascading menus are opened.
1.3.2.4.2 Pull down menus
A pull down menu is pulled down from a menu item present in a menu bar. To open a pull down menu,
click on the title of the menu you need to open with the "Select" mouse button.
1.3.2.4.3 Cascading menus
Cascading menus are derived from pull down menus and represent additional options for the pull down
menu item selected. Cascading menus are indicated if the ">" sign follows an option in a pull down menu.
1.3.2.4.4 Pop-up menus
Pop-up menus appear when you click, using the "Custom" mouse button, in the following cases:
– Clicking on a symbol in a view.

In this case, once the symbol is selected, click on the symbol using the "Custom" mouse button. The
pop-up menu opens. Select an item from the menu by clicking on it using the "Custom" mouse but-
tons.
1.3.2.4.5 Unavailable menu items and Menu item Selection
In an opened menu (pull down or cascading), any item that is greyed indicates that you do not have access
to the menu item. Clicking on it will not activate it. You have access to all the items that are not greyed.
An example of an inaccessible or greyed menu item is shown below.
To select an item from a menu (any type of menu) place the mouse pointer over the item and click using
the "Select" mouse button. The item will appear highlighted.
1.3.2.4.6 Mnemonics
A mnemonic is a single letter that is underlined in a menu (in Menu bars, Pull down menus or Cascading
menus). To open a pull down menu press, simultaneously, the ALT key and the mnemonic of the pull down
menu you wish to open. The pull down menu opens immediately.
To select an option from the opened pull down menu, press on the keyboard the character corre-
sponding to the mnemonic of the option.
1.3.2.5 Entry boxes
Entry boxes are windows in which you can consult, add or modify information or data.

1.3.2.6 Dialogue boxes
1.3.2.7 Generalities
Dialogue boxes provide an interface between the Manager and the user. The main dialogue boxes are
described below.
1.3.2.8 List dialogue boxes
A list dialogue box is generally a window that enables you to consult and select items from an existing
list. They have a Title heading indicating the purpose or contents of the List box. Depending on the size
of the List box, scroll bars are present or not.
Different types of List boxes can be distinguished.
a) Single column lists.
As the name suggests, they enable you to select elements from a single list.
They contain:
• Title: specifying the context of the List box.

• List: from which an item or items are selected.
• Pull-down menu
• Tool bar which contains selectable icons
b) Multiple columns lists.
They display the data in the form of multiple columns. You can choose from the list the item you wish,
and if possible, using the menu bar options undertake certain operations concerning the item.
1.3.2.8.1 Message and Confirmation dialogue boxes
They display messages and information. They require a confirmation of the action you wish to undertake.
Generally, work is suspended till the dialogue box is closed. This means that you first have to click on the
corresponding button (OK, Cancel, Help or other options) before resuming operations.

1.4 PRELIMINARY OPERATIONS
1.4.1 Logging in to the System

This is the first operation to access the Regional Manager system. The view that will greet you, called the
Login panel is presented below.
Figure 3. Login panel view
To correctly access the Manager:
– Enter your login name.
N.B. You are assigned the login name by the Manager administrator.
– Enter your password.
After a correct login, the login view is replaced by a transition view giving certain software copyright indi-
cations. This view is automatically replaced by the normal workspace view containing the Front Panel from
which you will be able to access the Manager functionalities.
1.4.1.0.1 Workspace description
Your workspace includes the functionalities that appear on your workstation screen after login.
The workspace Front Panel is described below.
Figure 4. The SDH Manager workspace Front Panel.
The components of this front panel are:
• The Clock icon displays the current time on your workstation.

• The Date display indicates the day and the date.
• The WS activity icon indicates the activity of the workstation.

• The Padlock icon enables you to lock your workstation screen.
• The EXIT icon launches the logout procedure.
• The Workspaces icons enable you to access different workspaces. There are six available work-
spaces (workspaces One to Six)
• 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 Text Editor icon launches the hp text editor application.
• The TMN-OS icon gives you access to the functionalities offered by the Regional Manager
product for the management of the network.
1.4.2 Locking the screen

This utility enables you to lock the screen to prevent other users from using your working environment.
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.
Figure 6. Screen lock Password: entry box
To resume work type in your password in the Password: entry box.
1.4.3 Logging Out

Logging out from the workstation will automatically quit all Manager graphical applications that you
opened and give place to the Login panel. Notice the the Manager processes are still running.
Using the Front Panel.
Click on the EXIT icon on the front panel, using the "Select" mouse button, as shown in the figure
below.

Figure 7. Logging out using the front panel
A dialogue box opens from which you can confirm or cancel the "Logout" operation.

1.5 Access to the main functionalities
A more detailed description concerning the Regional Manager management domains is given in the
Regional Manager Introduction Manual.
Access to the Regional Manager functionalities is provided through the workspace front panel as
described in the following sections.
1.5.1 Introduction
The 1354RM graphical interface is based on:
– HP Common Desktop Environment (HP–CDE)
– OSF Motif applications (Browser, RM aplications, etc.).
– Task subpanel.
The HP_CDE Tool panel ( See Figure 8.) has been customized to contain the TMN-OS Manager (right-
hand side).
Figure 8. HP-CDE Panel
Clicking on the Manager icon you can open the TMN-OS Management. ( See Figure 9.)

1.5.2 The TMN-OS
Figure 9. TMN-OS manager
By clicking on the TMNOSs icon opens a window containing all the OSs icons, i.e. all the systems resident
on the server/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 pull-down menu bar comprising the following menus:
– File containing the only option "Close" to close the window
– Edit containing the only option Clear Message area
– View it allows to show/hide OS area orMessage area
– OS
Start System. This submenu is present both for RM and NM. The Start option is available
if the selected OS is in the Stop state.
Stop System. This submenu is present both for RM and NM. The Stop option is available
if the selected OS is in the running state.
Both options are provided if the selected OS is in the Wrong state (partially stopped).
System Config. This submenu is available both for RM and NM. It allows to configure
the system in terms of processes

Process Monitoring. This submenu is available both for RM and NM. It opens the Pro-
cess 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 or SH) and on its actual status. The relevant OS icon must be selected. The available sub-
menus are:
User Interface. This submenu is present both for RM and NM. It permits to launch the user
interface
Performance Monitoring. This submenu is present both for RM and NM. It permits to
launch the Performance Monitoring display window.
Alarms. This submenu is only available for NM. It permits to launch the AS application.
SMF. This submenu is present both for RM and NM. It contains the following options:
Operator
Log
Trace
Failure
Scheduler
Backup
Restore
Cleanup
Initiator
– Global Actions (active only for resident Manager) It permits to launch the entire system actions.
It contains the following sub-menus:
Operator. It contains the following options:
Global Operator Actions

Change Password
Session management
Max Operator Logged Administration
Set Personal Printer
Synchronize Systems
Alarm Federations

The window contains a tool bar (active only for resident Manager) which allows to launch the most fre-
quently used applications as shown in the figure.
1.5.3 Alarm management

From your workspace front panel click on the Alarm icon shown in Figure 9.on page 52.
The Counter summary window is opened from which the operations on alarms can be carried out.
A customized sublist is presented. This sublist contains the following rows:
1) PHYSICAL LINK IN SERVICE ( IMPLEMENTED )
2) OMS TRAIL IN SERVICE (IF IMPLEMENTED ITS SUPERORDINATE PHYSICAL CONNEC-

TION
3) HO TRAIL IN SERVICE ( IMPLEMENTED OR PARTIALLY IMPLEMENTED )
4) MS TRAIL IN SERVICE (IF IMPLEMENTED ITS SUPERORDINATE PHYSICAL CONNEC-

TION )
5) OCH TRAIL IN SERVICE ( IMPLEMENTED OR PARTIALLY IMPLEMENTED )
6) PATH IN SERVICE (IMPLEMENTED OR PARTIALLY IMPLEMENTED OR COMMIS-

SIONED)
7) CLIENT PATH IN SERVICE (IMPLEMENTED OR PARTIALLY IMPLEMENTED OR COM-

MISSIONED)
8) EML
9) NE
1) ALL PHYSICAL LINKs
2) ALL OMS TRAILs
3) ALL HO TRAILs
4) ALL MS TRAILs
5) ALL OCH TRAILs
6) ALL PATHs
7) ALL CLIENT PATHs

8) PRC
9) BACKBONE NETWORK
10) MAIN ALARM LIST
11) DEFAULT ALARM LIST
Alarms on NOT_ IN_ SERVICE entities are automatically acknowledged by AS.
The not in service declaration is done:
• by the user for physical connections, OCH/HO-trail and (client)path
• automatically by the system for physical connections, OCH/HO-trail and (client)path at deim-
plementation time
If an alarmed entity is declared in service, a warning is given to the user.
Each row of the above sublist has been created, activated and saved; each row of the default sublist
has been deactivated and deleted. (The default sublist contains one row per each alarm severity).
1.5.3.1 Alarm Navigation
The following sequence briefly describes the alarm navigation.
a) From the Counter summary window open the Alarm sublist clicking twice on the relevant row of the
Counter summary window. As an alternative select the row and issue the Sublist: Open pull-down
menu item.
The Alarm sublist is presented.
b) Select the alarm from the sublist and navigate it by selecting the Navigation: 1354RM pull-down
menu item. A confirmation dialog box appears. Click on OK to confirm.
The following cases are possible:
– for PATH object the napView window is presented
– for PHYSICAL CONNECTION object the physical connection structure window is pre-
sented
– for O/MS TRAIL object the physical connection structure window is presented
– for HO TRAIL object the path in trail window is presented
– for EML object only the navigated object is presented
Notice that in each view the alarmed object is marked by an alarm icon. By clicking on this icon a window
is presented, which gives details on the selected alarm.

1.5.4 Task Subpanel
The task subpanel (see Figure 11.).starts automatically at browser startup.
Figure 10. Self-hiding vertical palette
The self-hiding vertical palette contains:
– upper arrow. If you click with the left mouse button on it, the icons contained in the layered icon area
will shift to the top side of the area itself.
– lower arrow. Same as upper arrow, except for the direction.
– TASK BAR. It contains the Alcatel logo and the icons of the tasks customized by the user. If you click
with the left mouse button on the icon of task, this causes the task to start. The task bar is custom-
izable by the user, i.e. the user can add task buttons of the most frequently used applications by
means of the utility pop-up menu, available on each system menu item. See example in the following
pages. On the other hand the user can remove a less frequently used application icon by means of
the task bar pop-up menu ( Remove item ). The user can drag these icons by pressing the middle
mouse button.

1.5.5 Active task subpanel
The active task subpanel is an horizontal panel located on the bottom of the screen.
Figure 11. Active task subpanel
It contains:
– left arrow. If you click with the left mouse button on it, the icons contained in the layered icon area
will shift to the left-hand side of the area itself.
– right arrow. Same as left arrow, except for the direction.
– TASK BAR. It contains the Alcatel logo and the icons of the tasks customized by the user. If you click
with the left mouse button on the icon of task, this causes the task to start. The task bar is custom-
izable by the user, i.e. the user can add task buttons of the most frequently used applications by
means of the utility pop-up menu, available on each system menu item. See example in the following
pages. On the other hand the user can remove a less frequently used application icon by means of
the task bar pop-up menu ( Remove item ). The user can drag these icons by pressing the middle
mouse button.
– layered icon area. This area contains the icons of the browser windows actually opened. If you click
with the left mouse button on the icon of a browser window, this causes the window to open.
1.5.5.1 System Menus started from the logo icon
System Menus can be started from the logo icon. See para 1.5.5.2.1 on page 59.for details.

Figure 12. System Menus started from the logo icon
1.5.5.2 Menus
INTRODUCTION
-To lauch the application/function associated to a single item, select the item with the left mouse button
MENU DESCRIPTION
Point with the right mouse button to an empty area of the horizontal task bars.The main pop-up menu is
displayed. See below figure.
Figure 13. Pop-up menu
The main menu contais the following submenus:
– System menus. System menus contains a cascode menu of the main system applications.
– User menus. This menu is customizable by the user by means of the utility pop-up menu, available
on each system menu item. See example in the following pages.
– Close main panel. This menu item closes the panel. The panel opens automatically at browser star-
tup.
Figure 14. Panel Close confirmation window.

1.5.5.2.1 System menus
System menus ( see following figure ), include:
Figure 15. System menu
– Path Provisioning. The cascade menu is shown in Figure 16.
– Network Configuration. The cascade menu is shown in Figure 17.
– Maintenance. The cascade menu is shown in Figure 18.
– OS Supervision. The cascade menu is shown in Figure 19.
– Browser. This menu starts the browser application.
– Netview. This menu starts the Netview application.
Figure 16. System Menus: Path Provisioning menu
Figure 17. System Menus: Network Configuration menu

Figure 18. System Menus: Maintenance
Figure 19. System Menus: OS Supervision
1.5.5.3 Create new panel
This option allows to create a new panel: edge panel (horizontal) or corner panel (vertical)
Figure 20. Create New Panel submenu
Figures which follow show the icons of the corner and edge panel

NEW CORNER PANEL
Figure 21. Create: New Corner Panel
NEW EDGE PANEL
Figure 22. Create: New Edge Panel
1.5.5.4 Task bar pop-up menu
The task bar pop-up menu contains the following options:
– Remove from panel
– Move applet. If you click on this menu, you will be able to move the involved icon by dragging it by
means of the left mouse button. It is the same as using the middle mous button ( pressed ) to drag
icons
– Properties...
Figure 23. Task bar pop-up menu

1.5.5.5 This Panel Properties
Figure 24. Panel Properties: Edge Panel
Edge panel:
Position ( Top, Bottom, Left, Right )
Minimize Options ( Auto Hide, Enable hidebuttons, Enable hidebutton arrows )
Background:
Figure 25. Panel Properties: Background

1.5.5.6 Global Properties
The Global Properties menu item, if selected, allows to display/modify panel configuration. Figure which
follows shows the Global Panel Configuration first dialog box: Animation.
Figure 26. Global Panel Configuration: Animation
Parameters managed by this dialog box are:
Animation
– Auto hide animation speed ( in ms ) = delay to disappear of the panel when you move the pointer
outside the panel. This modality is in effect if you previously selected Auto-Hide in the Panel Prop-
erties: Edge Panel view. ( see previous paragraph.)
– Explicit hide animation speed ( in ms ) = delay to disappear of the panel when you move the pointer
outside the panel and a window overlaps the panel. This modality is in effect if you previously
selected Auto-Hide in the Panel Properties: Edge Panel view. ( see previous paragraph.)
– Drawer animation speed= N.A.
– Auto Hide minimize delay ( in ms. )=delay to appear of the panel when you move the pointer inside
the panel. This modality is in effect if you previously selected Auto-Hide in the Panel Properties: Edge
Panel view. ( see previous paragraph.)
– Auto Hide minimized size ( pixels )=size of the remaining bar when the most part is hidden ( the sur-
vivor, look carefully...)

Figure 27. Global Panel Configuration: Miscellaneous
Miscellaneous
If you click on Miscellaneous button, a different set of parameters is displayed. They are:
– Tooltips enabled=enables the display of the icon help textstrigs which appear when you move the
mouse pointer over the icon
– Show popup menus outside of panel N.A.
– Show buttons. If this option is enabled, the last submenus of the panel is is not available and is
replaced by a button ( see below figure). If you click on a button, the utility pop-up menu is provided,
allowing to customize groups of commands.
– keep menus in memory. This option can be used to speed-up panel performance.
– Remaining options are not applicable.

1.5.5.7 Utility pop-up menu
The user can add task buttons of the most frequently used applications by means of the utility pop-up
menu, available on each system menu item ( see figure below ). This menu, opened via the right mouse
button, contains the following options:
Add this as drawer to panel
Add this as menu to panel
Add this to personal menu
On the other hand the user can remove a less frequently used application icon by means of the task bar
pop-up menu ( Remove item )
Figure 28. Utility pop-up menu on each system menu item
1.5.5.8 Customize panel procedure
a) Point with the mouse to an empty region of the panel, press the right mouse button to open the pop-
up menu. Select Global Properties menu item.
b) From the Global Panel Configuration window click on Miscellaneous button. The Miscellaneous dia-
log box page is displayed. Select option Show...buttons. Click on OK button to confirm and close the
dialog box. If you click on Apply to confirm, the dialog box remains open.
c) Select the command or the group of commands you want to customize, marked by the button shown
in the figure below.

In the following two examples:
1) Managing a group of commands, e.g. Path Provisioning.
Select with the left mouse button the button placed on the right side of the command group line.
The utility menu is displayed. Possible actions are:
– Add this as drawer to panel
– Add this as menu to panel
– Add this to personal menu
a) If you select Add this as drawer to panel, the Path Provisioning icon will be added to the
panel, as in Figure 29.herebelow. Clicking on the icon a vertical panel is raised, containing
the icons of the commands included in the subgroup of commands.
Figure 29. Utility buttons
b) If you select Add this to personal menu, the Path Provisioning icon will be added to the
panel. Clicking on the icon a vertical panel is raised, containing the icons and the text-
strings of the commands included in the subgroup.
c) If you select Add this as menu to panel, the Path Provisioning icon will be added to the
personal menu. Clicking on the icon a vertical panel is raised, containing the icons and the
textstrings of the commands included in the subgroup.

Figure 30. Customized user menu.
2) Managing a single command i.e. Path Creation wizard
Select with the left mouse button the button placed on the right side of the command group line.
The utility menu is displayed. Possible actions are:
– Add this launcher to panel
– Add this to personal menu
a) If you select Add this launcher to panel, the Path Creation wizard icon will be added to the
panel. Clicking on the icon with the left mouse button, the application starts.
b) If you select Add this to personal menu, the Path Creation wizard icon will be added to the
panel.
1.5.5.9 Add this menu as drawer to panel
Referring Figure 31., if you want to add the icon of the path create to the task bar, select System menus
-> Path Provisioning -> Path Creation Wizard-> Add this to launcher panel
Figure 31. System menus: Path Provisioning: Path Creation Wizard: Add this to launcher panel
N.B. The window icon pop-up menu allows to close or restore the window

Figure 32. Window icon pop-up menu

1.6 Views Description
1.6.1 Overview
The User Interface of the 1354RM is the Browser. It allows to open many applications.
Netview allows to create and display the topological objects (Network, Subnetwork, Ring, Node, SDH
Port) and the physical connections involved.
In any submap, by clicking twice on an object, the submap associated to the object opens.
The different submaps are described in next Chapter "Navigation". It describes the Navigation procedures
among the Netview submaps.
The available submaps are:
– Network Domain submap
– Network submap.
– Subnetwork submap.
– 2nd level Subnetwork submap
– Link submap.
The physical connections are grouped in links.
The Browser application includes:
– a main view which allows to navigate among all the topological and connectivity objects;
– several views named:
• Netview, mentioned above
• Payload configuration of a Physical connection
• Port payload structure
• HO-TRAIL configuration (LO lc in HOtrail)
• LO Paths in a HO-TRAIL
• Payload Configuration of a SDH port
• MS-SPRING protection block view
• Single MS-SPRING Protection Block
• Path Routing view
• Node view
• Nap view

– several lists. Main lists are:
• Path List
• Trail List
• NAP List
• CTP List
• CAP List
• Port List
• Performance Measure List
• Alarmed Object List
• Alarm Profile List
1.6.2 Management Tools windows

Several windows associated to the Management Tools are also available. In the following are listed the
main ones
Payload Configuration It is used to create or modify a physical connection or a ring

payload structure
Trail Creation (WIZARD) It is used to create a trail.
Path Create (WIZARD ) It is used to create a path (end-to-end connection) between

two or more NAPs.
Path Constraints It is used to assign the constraints to a path or trail
PM Measure Create It permits to create a Performance Monitoring measure.
PM Measure Correlate t is used to assign the objects involved to a measure:

transports (trail/path)
termination points (tp)
Event logger It allows to display the events.
Node create ( WIZARD ) It allows to create a node.
Connection Create( WIZARD ) It allows to create a connection
1.6.2.1 Wizard
Wizards make use of a driven approach to better help the user in executing the requested procedures.
Each wizard is constituted by a fixed sequence of dialog boxes. For each dialog box the user is requested
to enter some parameters, names or values, and after filling the box the user passes to the subsequent
box by clicking on Next button.
Each box ( with the exception of the first one ) contains also the button Previous, which allows the user
to check / change the previously entered values.
The last dialog box contains the button Finish, which launches the execution of the procedure concerned.

Wizards are easy and friendly to the user, since they do not require to navigate through the browser to
select objects to be dropped: namely they contain dedicated selection buttons, which provide lists of the
objects suitable to be inserted to fill the wizard dialog boxes. Notice that these lists are filtered according
to the parameters entered in the previous dialog boxes.
It is also possible to navigate through Netview map to select the objects to insert into the dialog boxes.

1.7 SDH Netview : map navigation
1.7.1 Introduction
It is possible to start The Netview application from browser, pointing to the Network domain icon and issu-
ing the pop-up menu Display: All Related Items.
Select item Network Domain view and click on No Filter. Netview opens, showing the Network icon(s).
PULL_DOWN MENU
GENERAL TOOL BUTTONS
SHOW/
ATTRIBUTE
GET PARENT
GET PARENT
EXIT OBJEC
POP-DOWN SHOW
ALIGN
GET RELATED OBJECTs ITEMs USER
ACTIVATE WINDOW ZOOM

SHOW EQUIPMENT ZOOM TOOLS
HIGHLIGHT CREATE TOOLS MOVE NODE
SAVE
HIDE BACK-
COORDINATES
GROUND
RESIZE OBJECT
SAVE OPEN SET VISIBLE LAYER

BACKGROUND SECONDARY HIDE ISOLATED NODES
VIEW
SPECIFIC TOOL BUTTONS
Figure 33. Map window: Pull-down menu and tool buttons
N.B. Menus and tool buttons change according to the selected object. By moving the mouse over
the tool button icon, a ballon help is shown, explaining the operation invoked by the button itself.

1.7.1.1 Usage of zoom tool
The zoom pull-down menu includes:
– Zoom In to enlarge the working area of the map view. This item allows the operator to increase the
current scale factor. The view center point does not change.
– Zoom Out . This item allows the operator to reduce the scale of the current scale factor. The view
center point does not change.
– Fit. This item allows the operator to return to the original size and center of the view.
Figure 34. Zoom tool interface

Window Zoom
This item allows the operator to zoom into a defined view rectangle. Click on Activate Window Zoom but-
ton. Click on the first corner of the area to zoom and drag to the second corner of the area to zoom, thus
drawing a rectangle on the map.
Release mouse button. The selected rectangle fits the working area.
1.7.1.2 EXAMPLE of SDH submap navigation
An example of submap navigation is shown in the figures that follow.
a) Figure 35.shows the RM submap.
Figure 35. RM domain map

The display of the physical connections can be filtered by means of the Available Layers button, present
on the tool button palette, which allows to display separately the map connectivity.
Figure 36. Available Layers
Figure 37. Domain submap
b) Clicking twice on the network icon, the network map is opened. It contains the subnetwork symbols
along with their physical connections (see example in Figure 37.)

c) Clicking twice on the subnetwork icon, the submap of the objects belonging to that subnetwork is
opened (see example in Figure 38.)
Figure 38. Objects belonging to a subnetwork
d) Clicking twice on the icon of the 2nd level Subnetw, the submap of the objects belonging to it is pre-
sented (see example in Figure 39.on page 75)
Figure 39. Objects belonging to a 2nd level Subnetw

Clicking on the Physical Connection group, the Physical Connection list opens.
Figure 40. Physical Connection list
Select the Physical Connection and click on icon Physical Connection structure. The Physical Connection
structure opens.
Figure 41. Physical Connection structure
On each object represented in the map, the object pop-up menu can be opened. See Figure 42.

Figure 42. Pop-up menu

1.8 Layered maps
By means of the selection button on the horizontal palette you can select the layer, e.g. TU-12, as in figure
below.
Figure 43. Example of selection of layer TU-12
You can select the layerAU4-4C, as in figure below.

Figure 44. Example of layer TU-12
The three numbers beside each link represent the amount of total, busy and free resources.
Figure 45. Example of layer AU4-16C

1.9 Browser
1.9.1 Introduction
The Browser is an application which provides multiple navigation views. It supports full view of MIB data
objects or tailored views. The commands available in the browser depend on user's profile.
The Browser supports:
• Single/multiple selection operations
• Pull-down menu with generic and/or object specific commands
• Pop-up menus with generic and/or object specific commands
• Drag and drop operation for interworking between applications
• Help on item (Balloon help). A textstring describing the function is presented if you leave the
mouse more than one second on the functional button/object.
• Context-sensitive help. If you select the object and the pull-down menu Help on selected object,
the Worldview application starts and displays automatically the description of the selected
object class.
The Browser is based on the approach to enable navigation into all, a portion or a view of the containment
tree.
Objects are presented with:
• An icon related to the class (a bitmap) that can be related to one or more attribute values. Exam-
ple:
– class NE with bitmap depending on Type
• A color relevant to an attribute value (e.g. implementationStatus)
• A label related to one or more attribute values
• Additional labels/option buttons/texts or multicolor icon (pixmaps) displaying attribute values
• An alarm icon that appears only when the object is alarmed, whose color is related to the alarm
status value.
Object containment is represented using:
• Recursive object grouping into frames
• Indentation
The basic operations on objects are:
• Search (Display)
– Main related items ...

– All related items ...
– Align item(s)
– Parent

• Select
– Related items ...

– All related items
– Unselect all
• Details
– Show/Set attributes ...

– Displayed info ...
• Class specific actions (executed as separate processes)
1.9.1.1 Browser main window
After launching the Browser application, the Browser window is opened.
This window contains:
Figure 46. Browser main window.
• window title : 1354RM: Browser
• pull-down menu bar.
• icon bar. Refer to paragraph 10.2.1
• title : 1354 RM Viewer [ drop to view ]

You can drop here an item dragged from browser or other RM applications.
• counters area. It contains three counters:

– Total. It is the total number of objects actually retrieved by the Browser.
• Visible. It is the total number of objects visible in the window.
• Selected. It is the total number of objects selected (should be always 1)
• work area. It contains the retrieved objects.
• info area containing:
– logo
• help area providing the following information:
• values of displayed attributes.You get this information moving the mouse to the
involved object in the work area.
• function button description. You get this information moving the mouse to the
involved button in the button box.
• events flag indicator (Create not processed, Delete and Update processed).
• Balloon help are present on widgets (buttons, items, attributes, ...).
1.9.1.2 Icon bar
The first row of icon bar contains the following buttons:
– Exit. It corresponds to the pulldown command File: Exit.
– Display: Main Related Items. It corresponds to the pulldown command Actions:Search:Main

related items and/or to the popup command Search:Main related items
– Display parent item. It corresponds to the pulldown command Actions:Search:Parent and/or to the
popup command Search:Parent.
– Show/Set attributes. It corresponds to the pulldown command Actions:Details:Show/Set Attributes

and/or to the popup command Details:Show/Set Attributes.
– Align item(s). It corresponds to the pulldown command Actions::Align item(s) and/or to the popup
command Align item(s).
– User info. It provides the help information of the logged user.
The second row of icon bar contains the following buttons:
– Highlight button. It allows locate/display object
– Open Map. It opens the map view
– Topology tools. If you click on this button a submenu is opened. It includes the following buttons:
• go to parent menu
• go to home menu
• Create Node
• Create Physical Connection
• Shared Risk Group Management
Configuration Tools (CFG). It shows the configuration tools. If you click on this button a submenu is
opened. It includes the following buttons:
• go to home menu

• Payload configuration
• Concatenated rates set-up
• create HO trail
• add/remove protection
– Path tools. If you click on this button a submenu is opened. It includes the following buttons:
• go to home menu
• Create path
• Add Constraints to a path/trail
• Add leg to a path
• Show scheduled operations
• WDM Connectivity Tool
• Add/Remove protection
– Alarms tool. If you click on this button a cascode submenu is opened. It includes the following but-
tons:
• show alarms at server layer
• Report elementary alarm correlation
• Show active alarms
• Create Alarm profile
• Alarm Management wizard
– PM. It shows the performance monitoring tools. If you click on this button a submenu is opened. It
includes the following buttons:
• Create Measure
• Correlate transport to a measure
• Merge measure
• Show PM Data
– Tools
• go to home menu
• Active counters
• Event Log. It starts the Event Log application.
– Show Equipment. It opens the Equipment view of the selected NE
1.9.1.3 Counters area
In the Total, Visible and Selected field are shown respectively the total number of displayed items, the
number of visible items and the number of selected items.

1.9.2 Work area
Figure 47. Browser work area.
In the Browser main window work area are displayed the retrieved items that are configured to be shown
in that window (eg. Nodes in topology from the ET). Retrieved items can be also displayed in Drawing Win-
dows and in Multicolumn Windows (eg. All nodes from Network, Network Domain and Root Domain) and
will be detailed in the next paragraphs; in these cases a group icon that refer to the relative window is dis-
played in Browser Main Window work area.
1.9.2.1 Object filtering
Object filtering and scoping is supported through the Search:Main related items and Search:All related
items. Filtering can be performed with:
• Conditions entered by the user
• User defaults pre-saved conditions
• Class related predefined conditions (e.g. customerName=xyy)
Using the popup Search:Main related items or Search:All related items, or selecting one or more items
and using the icon button Display Related Items or the pulldown Actions:Search:Main related items or
Actions:Search:All related items a Chooser window of available navigation is shown:

Figure 48. Object filtering.
Clicking on the Options ... button the Define Query For window is shown (see next paragraph)

1.9.2.2 DEFINE QUERY FOR (the selection/filter window)
Figure 49. Define query window for Node
The DEFINE QUERY window is used to display a list of attributes of the selected object. This window has
a standard structure, described in the following:
– Window label The window label is: DEFINE QUERY FOR <object class name >
– Parameter group buttons The parameters are divided in groups. Each button activates the display
of the parameters belonging to that group
– Selection parameters The selection parameters are structured in three columns: attributes, filter-
criterion , value.
– Control buttons Three control buttons are provided: Apply, Cancel and Help
The left-hand column contains the list of all the attributes of the selected object
The central column (option button) specifies the filter condition. A pop-up menu can be opened, which
allows to select among the options.
If attribute is of type string the pop-up menu which can be opened is the following:
– None. No filtering is specified.
– Start with.This filter condition provides the instances which start with the specified string in the rel-
evant MIB data.
– Match exactly.This filter condition applies an exactly match between the field specified and the rel-
evant MIB data.
– Contains. This filter condition provides the instances which contain the specified string in the rele-
vant MIB data.

– End with. This filter condition provides the instances which ends with the specified string in the rel-
evant MIB data.
– Doesn't contain. This filter condition provides the instances which do not contain the specified string
in the relevant MIB data.
If the attribute is of the type enumerated, the pop-up menu which can be opened is the following:
– None
– Equal to
– Not Equal to
If the attribute type is date, the pop-up menu is:

– None
– Before
– Since
– Exactly
If the attribute type is integer the pop-up menu is:

– None
– Greater equal than
– Less equal than
– Equal to
– Not equal to
The right-hand column contains the attribute values. The value can be entered in text field, for the types
integer, date and string. The value can be entered as option for the type enumerated.
The function of the filter is an AND of all the previously specified conditions.
In case the selection is handled by pointers instead of containment tree, the filter is disabled.
1.9.2.3 Show/Set Attribute
The Show attribute operation is startable from popup Details:Show/Set attributes, from the pulldown
Actions:Details:Show/Set attributes and from Show/Set attributes icon and allows to display the
"ATTRIBUTE VALUES FOR" window that shows the item attributes retrieved.
The "ATTRIBUTE VALUES FOR" window is quite similar to the "DEFINE QUERY" window and is used
to display or change value in MIB of the selected object's attributes. This window has a standard structure,
( see Figure 50.) described in the following:
– Window label The window label is: ATTRIBUTE VALUE FOR <class> <item label>
– Parameter group buttons The parameters are divided in groups. Each button activates the display
of the parameters belonging to that group
– Parameters The parameters are structured in three columns: attributes name, set buttons (set and
set to default) present only if the attribute is modifiable, fields or option buttons.
– Control buttons Three control buttons are provided: Apply, Cancel and Help

Figure 50. Show/Set Attributes dialog box.
N.B. It is possible to copy a set of attributes from a certain object and paste them into another object
of the same class. Select the source object from the object list and issue Edit: Copy Attributes.
A selection box is opened, which allows to select, among the ‘clonable’ attributes, the attributes
to be copied.
Then select the sink object from the object list and issue Edit: Paste Attributes.
See following figures
Figure 51. Edit: Copy Attributes

Figure 52. Attribute selection
1.9.2.4 Items selection in the Browser
A possible use of this feature is, for example:
– select within a path list already displayed in the browser, all the paths where the configuration state
is allocated and the customer name matches a given value or pattern. After the selection, the con-
figuration action required can be issued.
The available commands and the behavior result from the following table:
Table 3. Items selection in the Browser
Command Browser Main Window Browser Multi Column Browser Graphical

Lists Views
Select All Not available All the items in the current Not available
multi column list are
selected
Select All the children of the given Not available Not available
All related items selected object are
selected
Unselect All All the selected objects are All the selected objects are All the selected objects are
unselected unselected unselected

Command Browser Main Window Browser Multi Column Browser Graphical
Lists Views
Select related A mask with the possible Not available A mask with the possible
items .... children classes for the classes displayed in the
selected object is pre- view is presented.From
sented. From this mask, this mask, the user can
the user can select a class select a class and, option-
and, optionally, the ally, the detailed filter to be
detailed filter to be applied applied (see description for
(see description for multi- multi-column view).
column view)
Select .... Not available A mask with the attributes Not available
of class displayed in the list
is presented. The user can
define a sequence of con-
ditions in order to perform
the needed selection.
N.B. The command Select All allows to select a maximum of 65 lines.
1.9.2.5 Generic Browser pull-down menu
1.9.2.6 Actions: Search: Main Related items...
The purpose of this procedure is to retrieve from the MIB data base the main information related to the
selected object. The relationship between the selected object and its related items is described in the
object containment tree. In detail, this relationship can be though as a father-child relationship or a pointer
relationship.
This operation can be executed either from the Actions pull-down menu, that starts the get operation of
all selected objects (they MUST belong to the same class) or from the object pop-up menu that starts the
get operation only on that object.
This operation can also be launched by double-clicking the object or clicking on the Get object from MIB
icon of the icon bar.
SEQUENCE
a) Select (left click) one or more object to browse and Actions: Search: Main Related items....
The related item selection window is displayed. This window contains the list of child classes of the
selected object.
b) Select the class to display and the search mode (Filter/No Filter). If you select No Filter the related
objects (children) of the selected object are displayed below the father icon.
If you select Filter the Define Query window is displayed (See Figure 49.).
The box containing the available related objects is indentated with respect to the symbol of the father.
c) You can continue displaying related items for an object selecting again Search: Main related items
pop-up or pull-down menu item, according to the database hierarchical tree.

N.B. The output of the Search Main Related items operation can be in normal format, i.e. displayed
indentated in graphical way, or in multi-column format or by means of dedicated views, i.e. giv-
ing a compacted list of the browsed objects.
1.9.2.7 Actions: Search: All Related items...
This command is analog to the command Actions: Search: Main Related items... (see paragraph
1.9.2.6) The only difference is that all related items are available to be displayed.Actions: Search: Parent.
The purpose of this procedure is to retrieve from the MIB data base information related to objects that con-
tains the selected one. The relationship between the selected object and its parent is described in the
object containment tree. More in detail, this relationship can be though as a father-child relationship or
a pointer relationship.
This operation can also be launched by clicking on the Get parent object from MIB icon of the icon bar
or from the object pop-up menu.
a) Select (left click) one/more object/s to browse or pop-up.

b) Select Actions: Search: Parent.
The Parent object is displayed in the Browser window below the icon of the child object.
1.9.2.8 Actions: Select: Related Items....
This menu, if selected, provides a mask with the possible children classes for the selected object.
From this mask the user can select a class and, optionally, the detailed filter to be applied.
This operation can be executed also from the object pop-up menu.
1.9.2.9 Actions: Select: All related Items....
All children of the given selected object are selected.
1.9.2.10 Actions: Select: Unselect All....
All selected objects are unselected.
1.9.2.11 Actions: Close: Item
The purpose of this procedure is to remove the selected object and its opened children from the window.
a) Select (left click) one or more object/s to close.
b) Select Close: Item.
The selected object/s is/are removed from the screen.
1.9.2.12 Actions: Close: Item by Class
The purpose of this procedure is to remove from the window the specific child class of the selected object.
This operation can be executed only from the Actions pull-down menu.

a) Select (left click) one/ more object/s whose child class has to be forgotten.
b) Make use of the Actions pull-down menu. Select Close: Items by Class.
c) The child selection window is displayed. One/more child class can be selected (left click).
d) Pressing the OK button the select classes are removed from the screen.
1.9.2.13 Actions: Close: All related items
This command removes from the window all displayed children of the selected object.
a) Select (left click) one/more object/s whose related items have to be removed.
b) Select Action: Close: All related items.
1.9.2.14 Actions: Align item(s)
The purpose of this procedure is to align the data displayed on the screen to MIB data.
This operation can be executed from the object pop-up menu and the pull-down menu.
a) Select (left click) one / more object/s to be aligned.
b) Select Actions: Align item(s) or by using the right mouse button, select Align item(s)
1.9.2.15 Actions: Details: Show/set attributes
This allows to show attributes of an object or modify the value of the simple attributes (Modifiable at UI)
in the MIB data base.
This operation can also be executed by clicking on the Show/Set attributes icon of the icon bar or from
the object pop-up menu.
a) Select (left click) the object whose attributes have to be set/shown.
b) Select Show/Set attributes. A dialog box is presented. It contains the object's attributes.
The attribute that cannot be modified is displayed without any
If the user selects the option Set, will enter the new value in the area of the field (string, integer and
date type) or set the new enumeration value.
If the user selects the option Set to default, the attribute will be set to the default value.
c) After entering the modifications, select Apply. The attribute will be modified.
The Show/Set dialog box also contains the Cancel button, which causes to abort the procedure and
close the window and the button Help providing the relevant Help information.
1.9.2.16 Actions: Details: Displayed info...
The purpose of this procedure is to display the information relative to the selected object class.
This operation can also be executed by clicking on the Details on the displayed information icon of the
icon bar or from the object pop-up menu (Details: Displayed info..).
SEQUENCE
a) Select (left click) one/more objects or right mouse...

b) Select View:Displayed info...
A dialog box is presented. It contains the information relative to class name, color of the icon, dis-
played attributes.

Figure 53. Actions: Details: Displayed Info.
1.9.2.17 View:Displayed info....
Same as 1.9.2.16
1.9.2.18 View:Report
The View:Report item allows to select one of the following submenus:

• Report full...
• Report full only selected...
• Report short...
• Report short only selected...

Figure 54. View:Report full
• Report short...(See Figure 55.)
• Report short only selected...

Figure 55. View:Report short
1.9.2.19 Options: Filtered presentation / Not filtered presentation
These options specify if the pull-down Search Related Items action is filtered or not when only one child
class exists.Options: Overlay windows
The purpose of this option is to overlay or not the opened browser windows.
1.9.2.20 Options: Enable AS link
The purpose of this option is to break off the talking between browser and AS application
1.9.2.21 .Options: Task bar
The purpose of this option is enable/disable the task bar to contain iconified browser windows. The fol-
lowing selections are allowed: Vertical / Horizontal / Show / Hide.
On each browser window icon the following pop-up menu is available:
– pop-up ( or double click ). This menu, if selected, causes the re-display of the iconified window on
the screen.
– pop-down. This menu, if selected, iconifies in the browser working area the relevant window.
– close. This menu closes the window.
1.9.2.22 Specific
It contains menus which depends on the selected item (typically specific actions).
1.9.2.23 Windows
It contains the list of opened windows (views and multi column lists). Iconified windows can be deiconified,
deiconified windows can be iconified.

1.9.2.24 Tools
It allows to open the Active Counters tool. See following figure.
Figure 56. Active Counters tool
1.9.3 Navigations
It allows to open views containing items built after AS navigation and navigation from external tools
(eg: setup trail, path creation). The menu has following submenus:
– from AS. It opens a browser instance containing objects navigated from the Alarm Surveillance
application.
– from Others. It opens a browser instance containing objects navigated from the Netview application.
1.9.4 Active Counters

The Active Counters feature offers a way to monitor objects that match a given condition (defined on the
object's attributes) and to detect objects matching the condition
A simple but complete GUI allows the user to perform these tasks (creating/modifying/deleting counters
(with their conditions) and monitoring objects) easily and quickly.
1.9.4.1 Overview
This section briefly describes how Active Counters feature works while illustrating the structure of this doc-
ument.
Every counter is defined by a name (its identifier), a description (generally longer than the name and useful
to understand/remember the meaning/use of the counter) and a condition.
A counter's condition is defined by the class to which is applied (route, high order CTP, TMLSTrail, etc.)
and a list of "terms" that represents the sub-conditions to apply to the single attributes of the class' ele-
ments (see 3.1 - Conditions).
In addition to schema classes, metaclasses (see 2 - Metaclasses) can be used to define conditions

Given the counter's condition, if we define a time origin that we call "epoch", at a given time (equal or sub-
sequent to the epoch) we can calculate four values:
– the absolute number of objects that match the condition (total)
– the number of objects "losing" the condition since the epoch (out)
– the number of objects "taking" the condition since the epoch (in)
– the objects repeatedly losing and taking the condition since the epoch (ups-and-downs)
These four values are called subcounters (of the counter) and are the values that the user will monitor.
The Active Counters feature uses as an epoch the time at which the user activated it. While the feature
is active the user can reset the epoch of any of the counters (or all of them) to the current time, so to restart
the count.
Counters are fully explained in paragraph Counters.
1.9.4.2 Metaclasses
Metaclasses are "virtual groups of classes", in order to handle counters defined on more than one class
Metaclasses have no real disadvantages over multiple classes while having two main advantages:
– the logic of the feature is simpler, thus keeping the design simple and, therefore, lowering the cost
of implementation and maintenance;
– from a user perspective, conditions that spawns multiple classes behave exactly as single-class con-
ditions. Moreover the user doesn't need to know whether he's dealing with a single class or a meta-
class.
Metaclasses are configured on a per USM machine basis, so they are stored in the file system of the
machine that hosts the USM. This means, amongst other things, that, if there is more than one USM
machine, is to the administrator to supply every machine with its own copy of the metaclasses configu-
ration file.
Metaclasses can only be defined/modified/removed by the administrator while other users can only use
them.
In this document we will talk of simple classes when we wish to refer to schema classes, we will talk of
metaclasses when we wish to refer to metaclasses and we will talk of classes referring to both schema
classes and metaclasses.
1.9.4.2.1 Structure of a metaclass
A metaclass is made of the following components:

– name: a string identifier
– metaattributes: a set of virtual attributes that group the attributes of the joining classes;
– joining classes: a set of simple classes that join the metaclass and, for each simple class, the
attributes of that class that join the metaattributes.
A metaclass is subject to the following constraints:
– the name of the metaclass must be unique among class name, i.e. it can't have the same name of
an existing simple class or of another metaclass;
a metaclass must have at least one metaattribute

– two metaattributes (of the same metaclass) can't have the same name: while two metaattributes of
different metaclass can;
– only "countable" simple classes may join metaclasses: metaclasses and "non-countable" simple
classes can't;
– a simple class may join a metaclass almost once
– a joining class associates one (and only one) of its attributes to each metaattribute, if a joining class
does not associate any attribute to one or more metaattributes, we say that the joining class does
not handle the metaattribute;
– a metaattribute must be supported by at least one joining class
– the simple attributes joining a metaattribute must be of compatible, i.e. one of the following condition
must be true:
• all joining attributes are of string type
• all joining attributes are the same simple attribute
1.9.4.3 How it works
As already told, metaclasses have been designed to minimize their impact on design, while needing some
support at implementation level.
In practice, a counter based on a metaclass is implemented creating one counter for each joining class.
Each "derived" counter has a condition obtained converting the original (meta)condition, in this way:
– the class of the derived condition is the joining class
– the terms of the derived condition are the original terms, except that:
• if the metaattribute of the original condition is handled by the joining class, the attribute of the
derived condition is the joining attribute for that joining class;
• if the joining class does not handle the metaattribute of the original condition, the term is not
included in the derived condition.
In spite of all this deriving/translating work, the end user only sees the original counter, while the derived
counters are invisible to him.
1.9.5 Counters
Every counter is defined by:
– a name: a unique string identifier
– a description: generally longer than the name and useful for the user to understand/remember the
meaning/use of the counter;
– a condition: a counter's condition is defined by the class to which is applied (route, high order CTP,
TMLSTrail, etc.) and a list of "terms" that represents the sub-conditions to apply to the single
attributes of the class elements
Given the counter's condition, if we define a time origin that we call "epoch", at a given time (equal to the
epoch or after it) we can calculate four values:
– the absolute number of objects that match the condition (total)
– the number of objects "losing" the condition since the epoch (out)

– the number of objects "taking" the condition since the epoch (in)
– the objects repeatedly losing and taking the condition since the epoch (ups-and-downs)
These four values are called subcounters (of the counter) and are the values that the user will monitor.
The epoch is the time at which the user activated the Active Counters feature. While the feature is active
the user can reset the epoch of any of the counters (or all of them) to the current time, so to restart the
count.
In addition to the concise view of subcounters, the user can inspect the situation with greater detail dis-
playing the list of the items that are counted by a specific subcounter. These lists are implemented using
the standard Browser's list, with the notable exception of lists opened for counters base on metaclasses.
In this case, in fact, we have implemented a special multilist widget that, visually similar to a standard
browser's list, is capable of displaying multiple lists of items in the same window.
Active Counters are defined and used on a per user basis, so that every user will have/will be able to create
its own counters independently from other users. Note that different Unix logins, even impersonating the
same operator, are considered different users.
A requirement for Active Counters is persistency for different sessions of the same user.
This current implementation supplies a per USM machine persistency, i.e. the counter definitions are
stored in the file system of the machine that hosts the USM. This means that different machines hosting
the USM will have different counter definitions. Moreover, because of the per user nature of the counters
a unique configuration file in the user's configuration directory will store its definitions.
1.9.5.1 Conditions
A condition is defined by the class to which is applied (route, high order CTP, TMLSTrail, etc.) and a list
of "terms" that represents the sub-conditions to apply to the single attributes of the class' elements.
Classes that can make part of conditions can either be simple classes or metaclasses. But non all simple
classes can make part of conditions: in fact, not all simple classes are suitable/sensible to be counted (e.g.
classes that are never instantiated, but serves only as base classes to derive from). The subset of count-
able classes is not configurable by the end user.
The conditions are generic and are based on AND/OR of terms.
A condition is of the form: (term1 OR term2) AND term3 OR Term4
(term1 OR term2) AND term3 OR Term4...AND termn
where termi (for i=1,...,n) is of the form:
termi = attri opi value

so, termi is true if applying opi to attri and valuei returns true.
Not all attributes of countable classes are allowed to make part of terms, in fact, only enumerated or string
attributes are allowed and only if they are primitive attributes (so IATTR and XATTR are excluded).
For what regards the operators:
· if the term's attribute is an enumerated one, the possible operators are: equal and not equal;
· if the term's attribute is of string type, the possible operators are: starts with, matches exactly, con-
tains, ends with, doesn't contain and differs from.
Finally the value must be compatible with the attribute, so:

– if the attribute is of enumerated type, the value must be one of the enumerated values;
– if the attribute if of string type, the value must be a string.
1.9.5.2 NAD
From an NAD point of view, active counters created by a certain user take into account only objects that
such user can access (or at least objects on which it has some visibility). Then:
– every object's security label is known: i.e. AVC events (and also other events) must bring security
label;
– a function that, knowing the user's rights, filters incoming events basing on the user's access rules.
Currently these two requirements can't be achieved, therefore, at least for this first release, the active
counters feature will behave differently, depending on user type:
– for administrators: objects handled by the feature will be all the object accessible by the operator (i.e.
all);
– for non-administrators: each counter will count every object satisfying its condition (also those not
visible/accessible by the user), but only accessible objects will be displayed by lists.
1.9.5.3 FAD
As for NAD, there is a different access/use of functions whether the operator is an administrator or not:
if the operator is an administrator:
– operator will be able to define new metaclasses and/or modify existing ones , to be used by all the
operators;
– all the lists opened through the Status Window will update in real-time, thus reflecting the respective
counter's status ;
if the operator is not an administrator:
– operator will be able to use the metaclasses defined by administrators;
– any lists opened through the Status Window will not update, unless the user requests a refresh.
1.9.6 User Interface

Two windows have been defined to support Active Counters:
– the Status window: a flying window that allows the user to display and manage the counters;
– the Create/Modify/Show Counter widget: a widget that will allow the user to create, show and/or mod-
ify existing active counters;
– the Multilist widget: a modified Browser's list that displays item's from different classes.
1.9.6.1 Monitoring
The Status Window is a standard window provided with its own menu, its own toolbar and the list of active
counters defined by the user.
The user will open the Status Window through the Tools menu of the Browser's main window .

Each counter can be selected by the user to perform a specific action on it. The selection is single, so only
one by one actions can be performed on active counters (e.g. is not possible to delete multiple counters
with a single action).
The counters are presented in a table-like layout, showing for each active counter the following items:
– the Counter name: a user defined label used to identify the counter
– the Tot (Total) count: the absolute number of objects that match the condition;
– the In count: the number of objects "taking" the condition from the last reset command;
– the Out count: the number of objects "losing" the condition from the last reset command
– the Up&Dw (Ups-and-downs) count: the number of objects "double-flipping" the condition from the
last reset command.
Figure 57. Browser: Tools: Active Counters
Figure 58. Status window

Figure 59. Status window menus
The monitor window displays all the active counters defined by the user and allows him to:
– show an existing counter definition either via the Actions menu (that will show the selected counter),
via the popup menu (that will show the active counter on which the right click has been performed)
or using the toolbar;
– modify an existing counter definition either via the Actions menu, via the popup menu or using the
toolbar;
– remove an existing active counter either via the Actions menu, via the popup menu or using the tool-
bar;
– reset an existing active counter (resetting In, Out and Ups-and-downs values) (via the Actions menu,
via the popup menu or using the associated toolbar icon);
– reset all existing counters (via the Actions menu, via the popup menu or using the associated toolbar
icon), after a user confirmation;
– create a new active counter (via the File menu or using the associated toolbar icon)
– counter save (via the File menu or using the associated toolbar icon); If a counter is changed and
the operator doesn't use this save, when he will close the Status Window a popup will point out the
loss of modification if the save is not invoked and the confirm of the exit operation.
– show the list of counted items via the Actions/Lists menu, via the Lists submenu of the popup menu
or as follows:

• double clicking on the In value will open the list of objects "taking" the condition of the active
counter from the last reset;
• double clicking on the Out value will open the list of objects "losing" the condition of the active
counter from the last reset;
• double clicking on the Tot (Total) value will open the list of objects that match the condition of
the active counter;
• double clicking on the Up&Dw (Ups-and-downs ) value will open the list of objects double-flip-
ping the condition of the active counter from the last reset.
The lists opened are not up-to-date, they can be up-to-date using the refresh function.
Even if not shown in the above figures, the columns for the four subcounters have different background
colors, in order to quickly recognize them. In addition, when a subcounter leaves the reset state its cell
is highlighted to capture the attention of the user.
1.9.7 Definition and Activation

The creation of a new Active Counter is performed from the status window, either choosing New counter
from the File menu or using the proper toolbar icon. The user action will invoke the Create Counter widget.
The approach proposed is the bottom-up type and consists to create before the terms of condition and
When opened, the Create Counter form is:
Figure 60. Active Counter Creation window
In this form all is disabled but the two text fields (name and description of counter), the option box for the
choice of the class to monitor and the cancel button to annul the counter creation.

When the class is chosen, more elements of the window are enabled and is possible to create the con-
dition terms.
Figure 61. Entering data in Active Counter Creation window

Figure 62. Monitored Class selection.
Clicking on "Add New", the term creation form is opened:
Figure 63. Condition Modification dialog box

Figure 64. Condition Modification: Attribute selection
After attribute selection, the window changes to allow the selection of the operator and the value(s), so
that:
– if the attribute is an enumerated one, an option box with the two foreseen operators ("equals", "not
equals") is followed by a list box with the attribute possible values:
Figure 65. Condition Modification: attribute (enumerated)
– if the attribute is of type string, an option box with the string operators ("Starts with", "Matches
exactly", "Contains", "Ends with", "Doesn't contain" and "Differs from") is followed by a text box in
which the user will type the string to compare to the attribute:

Figure 66. Condition Modification: attribute modification (label)
When the first term is created, the option box Monitored Class is disabled and it is not possible to change
the class. If all terms are removed the option box is enabled again.
Each object on the form has an its specific function:
– the list with the multiple selection Subconditions, lists all terms created by user and all partial con-
dition created joining two or more terms;
– in every moment, it is possible to create new terms clicking on Add new up to the maximum limit of
six terms;
– if a term is selected in Subconditions and you click on Modify, the term modify form is opened.
– if one or more elements (simple terms or partial condition) are selected, it is possible to delete clicking
on Remove (with a confirm by the user);
– if two or more elements (simple terms or partial condition) are selected, it is possible aggregate them
using AND Join or OR Join, so a new partial condition with the selected elements joined by AND
or OR (according to the push button selected) is obtained. Moreover, the original elements are elim-
inated. If, for example, we select the fist two terms and clicking on AND Join we obtain:

Figure 67. Split button enabled
– if one or more elements that represent partial condition are selected, it is possible to decompose
them using the Split button. See above figure. Split cancels the previous aggregation operation. So,
selecting on the first row of the above figure and clicking on Split, the following arises:
– since the partial condition can became long, can be difficult for the user examine a partial condition
only using the Subconditions list, so the last partial condition selected is displayed completely in
Selected subcondition field;
– the Overall condition shows as would be the final condition if all partial conditions were aggregated
using the function button (AND or OR) ;
– the OK button confirms the counter creation with the condition shown in condition
1.9.7.1 Modification
The form of counter modification is equal to the creation one but the differences described below:
– The form shows counter data (name, description, class and condition);
– The class is not modifiable.

Modifications that involve attributes and values (i.e. all except renaming), if successfully completed, reset
the counter (i.e. the Total counter is recomputed and the In, Out and Ups-and-downs counters are reset).
To modify the active counter, first select the counter and the issue the Modify pop-up menu. See Figure
68.herebelow.
Figure 69.shows the Active Counter Modify window.
Figure 68. Counter: Modify pop-up menu item

Figure 69. Active Counter: Modify
1.9.7.2 Visualization
For the visualization of Active Counters, issue the pop-up item Show. The same form of modification is
used except that user cannot modify values. See figure which follows.

Figure 70. Condition Visualization ( Show)
1.9.7.3 List visualization
Lists are displayed using the standard Browser's lists, sole exception are lists for metaclasses that are
displayed using the special Browser's multilists that allow to display multiple list of objects of different
classes into the same window.
The lists opened from Status Window (with double click on the column chosen) have as title the column
name ("In", "Out", "Tot", "Up&Dw") followed by the "counter name".

1.10 Browser: Drawing Windows
The Browser application includes the possibility to display several drawing windows, which are helpful in
managing the controlled network.
1.10.1 Introduction
Drawing windows support:
• Single/multiple selection operations
• Pull-down menu with generic and/or object specific commands
• Icon Bar generic commands
• Dynamic Icon Bar depending on selected class
• Pop-up menus with generic and/or object specific commands
• Help on item (Balloon help). A textstring describing the function is presented if you leave the
mouse more than one second on the functional button/object.
• Context-sensitive help. If you select the object and the pull-down menu Help on selected object,
the Worldview application starts and displays automatically the description of the selected
object class.
Drawing windows have the following look (see )
• window title : 1354RM: Browser
• pull-down menu bar. Refer to paragraph 1.3.2.4.2 .
• Icon bar
• title : eg. Physical connection structure
• work area: It contains the retrieved objects.
• info area (Refer to paragraph 1.9.1.1 )

1.10.2 Icon bar
The Icon bar area is subdivided in three rows. The first one contains the following buttons:
– Close window. It forget the window and all its opened ones. This operation can also be executed
from the pulldown menu (File:Close).
– Hide window. It hides the window. It can be redisplay without any re-get. This operation can also
be executed from the pulldown menu (File:Popdown).
– Go to the parent window. It goes to window from which this one has been opened. The current
drawing is hidden or not, depending the status of Options:Close window going to parent on browser
main window (see paragraph 1.9.2.21)
– Display Main Related Items. It navigates the selected object(s) on browser main window. The chil-
dren chooser is automatically proposed (Main related items). This operation can also be executed
by double click on object or from the object pop-up menu (Search:Main related items)
– Show/set attributes. This allows to show attributes of an object or modify the value of the simple
attributes (Modifiable at UI) in the MIB data base. This operation can also be executed from the
object pop-up menu (Details:show/Set attributes) or from pulldown menu (Actions:Details:show/Set
attributes)
– Align items (s). It alignes the data displayed on the screen to MIB data. Almost one object must be
selected. This operation can also be executed from the object pop-up menu (Display:Align items(s))
or from pulldown menu (Actions::Align item(s))
– Refresh this window. It deletes all items and re-gets all data. Note that all children views/multicol-
umns lists are closed.
– Order Items. It allows to manage the order and size of the table columns
– Sort Items. It allows to set in ascending/descending order the columns.
– Hide/Show attribute counter. It allows to display the attribute counters referred to the displayed list
The second row depends on the specific view. It typically allows to open an application (eg. Setup trail,
Payload configuration, Path/Trail constraints) or views to create instances or to correlate objects to each
others).
The third row depends on selected class. It dynamically shows icons to open view/multicolumn list asso-
ciated to selected object.
1.10.3 Work area

In the Drawing window, the work area displays the retrieved items typically located on graphic background
to show the relation to each other. Inside the work area are often displayed particularly items (named
'group') from which other view/multicolumn lists can be opened).

1.11 BROWSER: LOCATE ITEMS IN NETVIEW
1.11.1 Locate topological objects on Map

It is possible to locate toplogical objects from browser to Netview. In the following an example of locating
a node is given.
a) From the Node list ( see Figure 71.) select the node and click on Navigation button. The Node icon
is displayed in the Browser main window. ( already selected ).
Figure 71. Node list.

b) With the node already selected click on button Highlight . The node is highlighted in the Netview sub-
maps as in Figure 72.
Figure 72. Highlighted node in Netview.

1.12 On-line documentation
1.12.1 Overview
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. Nav-
igation through the help is also possible using a customized navigation bar permanently displayed in the
left of the help screen
The menu options 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.

2 Operation
2.1 Introduction
Network operation comprises the following topics:
– Topology management
– Configuration
– Transport management
– Network modifications
– Export of resources on ISN interface for 1355VPN
– Statistics tables
– Topological structure utilities
2.2 Network configuration

The main procedures described in this Chapter are:
– Network Construction
– Payload Configuration
– Upload NAPs
2.2.1 Network Construction

It is assumed that the controlled network has been correctly installed and tested and the 1354RM has
been properly installed.
The network construction consists in representing the whole managed network with the necessary sub-
maps and creating all the required objects in the RM-MIB data bases.
The macro-activities are:
– Create the network objects
– Implement the network.

Operation 3AL 61269 AAAA Issue 4 117/854
2.2.2 Start the Netview application
a) Start the Netview application. From the browser point to the Network domain icon and issue the pop-
up menu Search: Related Items. Select Network Map. The Netview opens.
Figure 73. Netview domain submap
2.2.2.1 Save Background
For each submap you can add a background. Select Save Background, select the suitable background
and click on OK.
Figure 74. Add background

118/854 3AL 61269 AAAA Issue 4 Operation
2.2.3 Create the network objects
During this activity, the operator has to create all the submaps according to the network partitioning levels
and insert inside them all the objects (network, subnetworks, 2nd level subnetworks, nodes, ports and
connections).
The following steps have to be executed:
2.2.3.1 Creating the Network
SEQUENCE
a) From browser, point to the 1354RM network domain and issue the Create: Network pop-up menu.
See Figure 76.on page 120
b) In the Create dialog box enter the Network name and click on Create button. See Figure 75. The Net-
work icon appears in the New Object Holding Area. Drag (holding the middle mouse button) the icon
into the window.
Figure 75. Create Network dialog box.
N.B. Many networks can be created. It is not possible to interconnect the networks to each other
N.B. Alternatively, from browser, point to the 1354RM network domain and issue the Create: Net-
work pop-up menu. See Figure 76.on page 120

Figure 76. Create: Network pop-up menu
Figure 77. Network Domain submap
2.2.3.2 Creating the Subnetwork
SEQUENCE
a) The subnetwork objects are created in the Network submap pointing to the network icon and issuing
the Create: Subnetwork pop-up menu.
b) In the Create:Subnetwork dialog box (see Figure 79.) enter the Subnetwork name and click on Cre-
ate button. The Subnetwork icon appears in the New Object Holding Area
c) Drag the icon to the window work area. See Figure 80.

N.B. Alternatively, from browser, point to the network icon and issue the Create: Subnetwork pop-
up menu.
Figure 78. Create: Subnetwork.
Figure 79. Create 1st lev. Subnetwork dialog box.

Figure 80. Network map
2.2.3.3 Creating the 2nd level Subnetwork
SEQUENCE
a) The 2nd level Subnetwork objects are created in a Subnetwork submap pointing to the subnetwork
icon and issuing the Create: 2nd level Subnetwork pop-up menu. See below figure.
Figure 81. Subnetwork: Create: 2nd level Subnetwork pop-up menu
a) The Create dialog box is presented. See Figure 82. Enter the following values:
• name

• comments (if any)
Figure 82. Create 2nd level Subnetwork dialog box.
b) Click on Create button. The 2nd level Subnetwork icon appears in the New Object Holding Area
Figure 83. New Object Holding Area
c) Drag the icon to the center of the window. See following figure. Double click on the icon to open the
submap.

Figure 84. Objects belonging to a subnetwork
2.2.3.4 Creating Nodes
SEQUENCE
The Node object is the representation of the network element in the 1354RM map. A node can be inserted
either in the Subnetwork submap or in the 2nd level submap.
a) Select the Subnetwork or the ET where the new node has to be inserted and issue the menu Actions:
Create: Node. See Figure 85. The Node Creation wizard is displayed. See Figure 86. Notice that
NAP automatic upload is the default.

Figure 85. Subnetwork: Actions: Create: Node

Figure 86. Node creation wizard: step 1
b) Click on NE list button. The list of the available NEs is displayed. Select the NE and click on Apply
button. The selected NE icon is now present in the list of the wizard.
c) Click on Finish button to confirm the node creation.

Figure 87. Node creation wizard: step 1: NE selection.
– the NE is pasted to the map in the new object holding area (See Figure 88.) and its related node is
created in the data base.
– Execute NE: Synchronize or NODE: Synchronize
d) Drag the node/s just created to the map working area. See Figure 89.on page 128
Figure 88. Node just created

Figure 89. Node drag to the working area.
2.2.4 External Network Reference

External Networks are used to describe a connection between various 1354RMs or to create a path ter-
minated on a node non controlled by 1354RM. A path is defined as non terminated if either one of the
NAPs or both are not in the 1354RM domain. A non-terminated path describes a path between a Trail Ter-
mination Point (TTP) associated to a PDH port and a Connection Termination Point (CTP).
2.2.4.1 Create the External Network Reference
SEQUENCE
a) Select from the map the topology (subnetwork or ET), which will contain the new External Network
and issue: Create : External Network.
b) The Create External Network wizard is displayed. Enter userlabel and location and click on Finish
button. See below figure.

Figure 90. External Network Creation wizard.
c) The External Network Reference is created and displayed in the New Object Holding area. You can
drag the object to the center of the map.
2.2.4.2 Create Connection to External network
a) From the map select the external network/s to connect and issue Actions: Create: Physical Con-
nection.
b) The Create connection wizard is presented. See below figure.

Figure 91. Create Connection step 1.
c) Select the connection type, enter the connection name and click on next button
Figure 92. Create Connection step2
d) Select the real node from the node list and enter the external network name. Click on Finish button.

Figure 93. Physical Connection: Implement
NOTE
After creating the virtual objects, you could follow the usual procedures:
– Create the Connection
– Implement the objects and the connection (see above figure)
– Create the Path
NOTE
The user can modify, by means of the Show/Set Attributes window, the userlabel of an external network
and the userlabel of a port belonging to an external network.

2.2.5 Create Connection
Figure 94. Actions: Create: Physical Connection
The Create Connection can be started from the map by selecting source node / destination node and issu-
ing the command Actions: Create: Connection.
The Create Connection wizard allows to select the connection type among:
– SDH. See Figure 95.
– WDM. See Figure 96.
– SDH-CBR/WDM interworking, where CBR=constant bit rate. See Figure 97.on page 135
– Generic Digital Client/WDM interworking. See Figure 98.on page 136

Figure 95. Create Connection-step 1-Type SDH
If you select connection type=SDH, you will further select the STM type

Figure 96. Create Connection-step 1-Type WDM
If you select connection type=WDM, you will further select the WDM connection type between OPS and
OTS, where:
OTS (Optical Transmission Section) is used for connections between different WDM nodes.
OPS (Optical Physical Section) is used for connections within the same WDM node, originated and ter-
minated to the same node.

Figure 97. Create Connection-step 1-Type SDH-CBR/WDM interworking

Figure 98. Create Connection-step 1-Type Generic Digital Client/WDM interworking
2.2.5.1 Example of SDH create connection
SEQUENCE
a) From the create connection wizard, select connection type=SDH, STM type and enter the connec-
tion name. Click on Next button.

Figure 99. Create Connection-step 2

Figure 100. Port selection.
b) Click on A-Term Node List. From the A-termination Node list (upper-right part of), select the node
to connect and click on Apply button. The icon of the selected Node is now present in the Create con-
nection dialog box.
c) Click on A-Term Port List. From the A-termination Port list select the port to connect and click on
Apply button. The icon of the selected Port is now present in the Create connection dialog box.
d) Execute the selection of the terminating node/port following the modality explained at above points
b) and c). Click on Next button.
e) Make the reservation for this physcon of concatenated AU4s or not
f) Enter the initial no. of AU4s structured at Lower Order
g) Select the transport (physcon) alarm enabling rule (when created, when implemented)
h) Select the implementation rule (auto on create / on user’s request)
i) Enter the allocation cost. This is the nominal cost of the physcon which will be used by the allocation
algorithm (Dijkstra static)
j) Select the saturation profile. Click on selection button. The list of the Saturation Profiles is displayed.
See below figure. Select the profile and click on Apply to confirm. For detailed information see SEC-
TION Technical Annexes.

The saturation is a structured (traffic) upper filling threshold which limits resource(trail,physcon) filling up
to the threshold. Two saturation profiles are automatically defined by the system. They cannot be modified
or deleted by the user.
The noExtraCost saturation profile will be used for no saturation policy in path allocation. The noExtraCost
saturation profile is the default.
The predefinedExtraCost saturation profile has been defined in order to satisfy configurations with dif-
ferent physcon costs
scroll left
scroll right
Figure 101. Saturation Profile list
k) Select the fragmentation profile. Click on selection button. The list of the Fragmentation Profiles Pro-
files is displayed. See below figure. Select the profile and click on Apply to confirm. For detailed infor-
mation see SECTION Technical Annexes.
NOTE. The defragmentation is a structured (traffic) mechanism which helps resource(trail,physcon) fill-
ing. In practice, depending on the traffic distribution on the resource, an additional allocation cost is eval-
uated, if the allocation being requested rejects the possibility of subsequently allocating a rate higher than
the one being requested. It is obvious that in a resource nearly empty, the allocation cost of a new traffic
is greater than the allocation cost of a resource almost filled.
For easy of understanding, an analogous mechanism is applied for last minute trips or for some young/
old resources.

scroll left
scroll right
Figure 102. Fragmentation Profile list
l) The Finish button, if selected, completes the connection create.
The Cancel button, if selected, aborts the connection create.
The Previous button allows to revert to the previous screen, in order to modify node/port selection,
connection name...
m) Wait... After the connection create the physical connection structure view, if required, is displayed.
See below figure.
Figure 103. Physical Connection Structure

n) Physical connections are implemented during network implementation; however it is possible to
implement individually a certain physical connection by means of the command Configuration:
Implement. See below figure.
Figure 104. Physical Connection: Configuration: Implement
Figure 105. Physical connection structure implemented.
• Having created the connection, an external connection symbol is created in the submaps which
contain the connected objects. The external connection symbol label contains the name of the
object connected at the other end plus the connection name.

The physical connection is created in the map and the parent link is also created, if no other con-
nections between the involved nodes were present. The link label indicates the number of present
physical connections.
o) Create all the remaining connections
Linear MSP schemes need to be carefully managed by the operator. For detail see paragraph
which follows.
2.2.5.2 Saturation and Fragmentation Profile Creation
The user can create new saturation and fragmentation profiles, if needed in network planning.
From the Create Connection step2 wizard click on button Saturation or Fragmentation profile creation.
Figure 106. Saturation/Fragmentation Profile create button
p) Figures which follow, show respectively Saturation or Fragmentation profile creation dialog boxes.
For detailed information see SECTION Technical Annexes.
Figure 107. Saturation Profile create
Figure 108. Fragmentation profile create

2.2.6 Introduction to NPA
A NPA is a set of NEs, protections blocks, physical connections working together to create a dedicated
protection mechanism or grouped together to establish path layer protections
NPAs are:
SNCP, 2f MS-SPRings, 4f MS-SPRings, Linear MSPs (e.g. 1:n, 1+1), ASON /Fast Restoration
SNCP rings do not use any dedicated protection mechanism related to the ring itself, but, RM treat them
in a special mode for the path routing and protection.
2.2.6.1 Topology definition
The RM operator builds the network defining:
– The partitioning topologies (i.e. network, first / second level sub-networks)
– The placement of NEs into the sub-networks (-> Nodes)
– The interconnections between the Nodes (physical connections) entered manually or using the auto-
discovery function (based on J0 or on NE cables)
As a further, independent step, the operator needs to build the NPAs.
No strict relation exist anymore in RM between topologies (used for partitioning) and protections. In pre-
vious RM, ET topologies were used to represent both a protection and partitioning of the network.
The ET (Elementary topology) can be considered a second level sub-network removing the payload con-
figuration capability and the statistics related to the configuration
N.B. For the scenario "adding a DXC NE in an MS-SPRing" (with split operation), the work-around
is to configure the MS-SPRing on SH before enabling the download on DXC NE.
N.B. For the scenario "removing a DXC NE from an MS-SPRing" (with join operation) the work-
around is to de-concatenate the concerned AU4s from CT before enabling the download on
DXC NE.
N.B. In MS Spring-2F it is possible to insert a Network Element not managed by 1354RM. This fea-
ture is managed also by RM batch utility. For details refer to the Administration Guide.
2.2.6.2 Network Protection Architecture Create
SCOPE
The scope of this procedure is to create a Network Protection Architecture (NPA)
The NPA creation tool allows to specify:
• the type,
the involved physical connections and, if applicable, their associated role (e.g. Working or Pro-
tection for 4f-MS-SPRing, and Linear MS-P).
For ASON NPA, the user must specify also the physical connections used for the interworking with the
rest of the network

A NPA can be defined independently from the Topologies used for the partitioning of the Network. This
means that a NPA can belong to different Topologies of different levels and that Topology can have NEs
and links involved in multiple NPAs
The creation tool can be started from :
-A topology: Network, Sub-network (lev.1 or lev.2)
Within the tool, the involved physical connections can be retrieved browsing from the initial topology(*)
or from a different one reached through up & down navigations.
The NPA definition ends with the creation in RM of a NPA and its visualization on the user Interface
The NPA can be created even if not valid (e.g. a ring can be open or even empty) but RM always provides
to the users the proper warnings.
Dependently from the type of NPA to be created, the creation activity requires different information and
performs different checks:
A SDH physical connection can only belong to one NPA with the following exceptions:
ASON internal / linear MS-P
ASON interworking / any other NPA
SNCP / linear MS-P
A SDH physical connection is present in RM also when supported by a WDM network. The server OTS
or OPS physical conn. Are, in RM, not part of any NPA
SNCP rings must have the same uniform rate and east/west sequence is checked for first gen. NEs
SEQUENCE
a) Select Actions: Create: Npa
Figure 109. Actions: Create: Npa
b) The Create: Npa: Step 1: dialog box opens. The following cases may arise:

1) selection of NPA type=SNCP (generic).
• NPA Reduction Cost Factor
• NPA Usage Cost
NPA Usage Cost:
It is an extra cost to pay for the usage of a NPA. It has the target to make costly to enter and to exit from
a Network Protection.
As bigger is set as more the routing in the current NPA will be preferred compared to a less expensive
detour outside the NPA in the meshed network or in another NPA.
It is not considered for the spare that uses the same ring of the main.
If set to 0, the routing is done not considering the NPAs.
If set to more than half of the cost of a physical link (Default value TBC), the routing is done as it would
be having only not stacked protections and an internal route is preferred to an external one even if it has
a double cost.
By default the NPA Usage Cost cost is set to an RM installation default value but can be modified by the
user. For example if L is the default cost of a physical connection, a meaningful default value for the NPA
Usage Cost can be L/2+1 ( i.e. (L/2+1)*2 )
Applications of the NPA Usage Cost
With the proposed NPA Usage Cost, the routing algorithm behaves for stacked and not stacked ring con-
figuration in a similar way (i.e. for the routing, it is like to have a physical link between two stacked rings)
An additional example of the stability effect of the NPA Usage Cost is the behavior in case of stacked and
unbalanced rings.
NPA Cost Factor:
The NPA cost factor is an additional parameter of each NPA, enabling a percentage cost reduction for its
links. This cost reduction has the target to balance the NPA Usage cost and makes more attractive the
routing inside a NPA compared to the one outside at least for route longer than a given number of arcs.
In the fact, it is an indicator on how much a Main/Spare routing in a NPA has to be preferred compared
to an external route. It works together with the NPA Usage Cost making more attractive long routes in a
NPA.
If equal 0 it has no effect.
As bigger it is set as more the cost of NPA internal route is reduced and as more the NPA attracts the rout-
ing.
Changing the default physical conn. cost
In case of particular unbalanced configurations, if the NPA Usage Cost is not enough to avoid the ring
changing, the user needs to properly set the costs of physical connections
RM Rules for Main & Spare in 2f MS-Spring
These routing rules are used by RM in order to fulfil the requirements:

– The NPA Usage Cost for the rings used by the main is set to 0 and the cost of all its routing resources
(e.g. physical conn) is reduced by a parametric cost factor k (the Main & Spare cost gravity factor)
This is equivalent to say that it is preferred a routing in the ring compared to the best route if its nom-
inal cost is no more that k times the external optimal route
– If the spare uses the same links and pass-through connection of the main, the cost is considered
zero. This tries to prefer main and spare overlapped and finally gives more priority to a D&C con-
figuration
The overlapping on Drop/Insert connections between main and spare is forbidden. This is the driver
to differentiate main and spare and has its effect mainly forcing a diversity outside the ring
– The cost of using the ring for the spare in opposite direction compared to the main is increased of
a cost n. In the previous versions of RM this opposite direction was totally disabled.
Enter NPA name and click on Apply
Figure 110. Create: Npa: Step 1: SNCP-U
2) Selection of NPA type=2 F MS Spring or 4 F MS Spring. Enter NPA name and click on Apply
3) Selection of NPA type=Linear plus, i.e. 1 + 1 protection. In this case the user must enter:
– NPA name (userlabel)
– Protection Switch Mode
– Switch upon SD (signal Degrade)

– Mode of operation
– Plus APS Mode
Enter NPA name and click on Apply
Figure 111. Create: Npa: Step 1: 1 + 1 protection
4) Selection of NPA type=Linear colon, i.e. 1 to N protection. Enter NPA name and click on Apply
Figure 112. Create: Npa: Step 1: 1 to N protection

5) Selection of NPA type=ASON. Enter NPA name and click on Apply
Figure 113. Create: Npa: Step 1: ASON protection
6) Selection of NPA type=Fast restoration. Enter NPA name and click on Apply
Figure 114. Create: Npa: Step 1: NPOS protection
N.B. RM can handle only one NP control plane. Then only one NPA fast restoration in Flow Through
context can be created.

c) The NPA Create step 2 dialog box is presented, asking to specify the physical connections to include
in the NPA. Click on Physical connection list button. The Physical connection list opens.
Figure 115. Selection of the Physical connections
Select the relevant Physical connections and click on Apply button. The icon(s) of the Physical connec-
tions are now present inthe main window. Click on Finish button to launch the creation.
N.B. In case of 1 to 1 NPA or 1 to N NPA the selection dialog box contains two subwindows, one to
select the main Physical connection (s), one for the protecting one. See example of 1 to N NPA
in the following figure

Figure 116. 1 to N NPA: physical connection selection
Figures which follow show the action creation report and the NPA highlight on the map.
Figure 117. Action creation report
Actions after NPA create : Modify NPA, Modify Ring Map, Implement and Unlock physical connections

Figure 118. NPA highlight
NPA highlight : shows the nodes connected by physical connections involved in the NPA on the map.
2.2.6.3 NPA display & Views
2.2.6.3.1 NPA display
NPAs can be retrieved from:
• The containing network (list of all the existing NPAs)
• The sub-networks (level 1 & 2) containing at least a Node (not a physical connection) involved
in a NPA.
• The map view of network and sub-networks
• A physical connection involved in a NPA. A specific graphical flag shows that a Phys.Conn.
belongs to a NPA. This flag is represented on the payload structure view
• The routing display of a path crossing one or more NPAs (LIN MS-P is under analysis). See spe-
cific information on Routing.
A map of a topology containing at least a Node involved in a NPA (different from linear MS-P) visualizes
a flag with the type and the name of the NPA :
The flag placement is in charge of the user (e.g. close to the right Nodes)
From the flag it is possible to retrieve the NPA and its view.
SEQUENCE
a) From the browser select Network: Search: All Related Items
2.2.6.4 NPA modify
SNCP Rings, 2f MS-SPRings, 4f MS-SPRings can be modified adding or removing physical links by
means of the commands Join/Split Physical Connection.

Linear MS-Ps can only be modified adding and removing members of the linear 1:n protection.
The command is performed using a tool similar to the creation/modification wizard.
MSP NPA, ASON NPA and Fast Restoration NPA can be modified adding and removing internal or inter-
working physical links . See procedures Remove the Physical Connection from RM: SET LOCKED
and Insert the Physcon in the NPA
The command is performed using a tool similar to the creation/modification wizard
As a specific tool for MS-SPRings, the user can also visualize and modify the NE sequence numbers in
the NPA ring to allow a hitless take-over.
The form display the current sequence of the NE protection blocks and allows the definition of a new con-
sistent one.
NOTE: Only a defined NPA can be modified.
Figure 119. NPA: Actions: Configuration: Modify NPA

Figure 120. NPA: Modify: step 1
Figure 121. NPA: Modify: step 2

2.2.6.5 NPA Implementation
The implementation creates the needed structures / protection blocks in the NEs.
Involved physical connections must be implemented
No paths must be present in case of Rings, ASON, Fast Restoration, with the exception of SNCP Rings.
No paths must be present on the spare in case of 1+1 Linear MS-P or 1:n Linear MS-P with no-extra traffic.
It is allowed to implement NPA + paths only for MSP/ SNCP.
Figure 122. NPA: Actions: Configuration: Implement
2.2.6.6 NPA: Specify Ring Map
NPA: Specify ring map ( only for 2F / 4 F rings), allows to change/display the Node position in NPA ring
and the Node Id in NPA.
The user can change these attributes, according to the NPA ring.

Figure 123. NPA: Specify ring map: step 1
Figure 124. NPA: Specify ring map: step 2
2.2.6.7 NPA Remove
The NPA can be removed only if not implemented

2.2.7 Create a 4-F STM-16 NPE Ring with 1664SM
SCOPE
The scope of this procedure is to create a 4-Fibre NPE ring with 1664SM equipment.
SEQUENCE
a) The ring (Elementary Topology) objects are created in a Subnetwork submap using the command
Construction:Create:
b) Create Nodes and ports
2.2.7.1 Creating the Connections between Nodes
The Creating of the Connections is described in the previous paragraph Create Connection. Notice that:
– East Working Ports must be connected to West Working Ports
– East Protection Ports must be connected to West Protection Ports
TX
RX
SLOT 17 SLOT 19
AGGR. WEST 1 AGGR. WEST 2
WORKING PROTECTION
SLOT 18 SLOT 20
AGGR. EAST 1 AGGR. EAST 2
WORKING PROTECTION
Figure 125. Physical view of the aggregates of 1664SM-NPE (from 1353NM)
N.B. The 1644SM network element, when inserted in a NPE ring is equipped with 4 STM-16 aggre-
gate boards, as shown in Figure 125. This figure is part of the 1353NM equipment view.
N.B. West 1 and East 1 aggregate ports support the working capacity, West 2 and East 2 aggregate
ports support the protection capacity.
c) Create NPA=4f-MS Spring
d) Implement NPA

2.2.8 Takeover procedure
CONDITIONS
The 4-F ring is already configured at 1353NM (EML) layer.
No path crosses the ring
SEQUENCE
a) Create the NPA 4-f for the topology which represents the existing ring
b) At the NE/EML layer read the information of Node Id and Node Position per each node
of the ring and move these information to 1354RM map.
c) Issue NPA: Specify Ring map setting Node Position and Node Id.
d) Issue Download Disable
e) Implement the ring
f) Execute the Mark Audit and verify differences, if any
g) Enable download
2.2.9 Create a 4-Fibre STM-64 NPE Ring with 1670SM

SCOPE
The scope is to create and implement a STM-64 4-Fibre NPE ring with 1670SM equipment.
SEQUENCE
a) Create the Nodes. See below figure.
b) Create all the connections “main" (clockwise). The following assignment is suggested:
1) Create the connection main A to B, selecting board 24 on node A and board 32 on node B
2) Create the connection main B to C, selecting board 24 on node B and board 32 on node C
3) Create the connection main C to D, selecting board 24 on node C and board 32 on node D
4) Create the connection main D to A, selecting board 24 on node D and board 32 on node A

Figure 126. Example of NPE ring with 1670SM
c) Create all the connections “spare" (clockwise). The following assignment is suggested:
1) Create the connection spare A to B, selecting board 28 on node A and board 36 on node B
2) Create the connection spare B to C, selecting board 28 on node B and board 36 on node C
3) Create the connection spare C to D, selecting board 28 on node C and board 36 on node D
4) Create the connection spare D to A, selecting board 28 on node D and board 36 on node A
d) Implement the Ring.
The attribute Nodeid of Node A is Nodeid=1
The attribute Nodeid of Node D is Nodeid=2
The attribute Nodeid of Node C is Nodeid=3
The attribute Nodeid of Node B is Nodeid=0
The first port, which has been selected while creating the A to B main connection (board 24 on node
A) is now distinguished by the attribute SDHPORTROLE=WEST MAIN. The second port, which has
been selected while creating the A to B main connection (board 32 on node B) has now the attribute
SDHPORTROLE=EAST MAIN. The remaining ports of the NPE ring are marked accordingly.
The first port, which has been selected while creating the A to B connection (board 28 on node A)
is now distinguished by the attribute SDHPORTROLE=EAST MAIN. The second port, which has
been selected while creating the A to B spare connection (board 36 on node B) has now the attribute
SDHPORTROLE=EAST MAIN. The remaining ports of the NPE ring are marked accordingly.
Figure 127. 1670SM equipment view

Assignments are visible only at 1353NM interface (4-Fibre NPE ring main dialog box). See below
figure
Figure 128. 4-Fibre NPE ring 1353NM main dialog box

e) Create NPA=4f-MS Spring
f) Implement NPA
2.2.10 Takeover procedure

CONDITIONS
The 4-F ring is already configured at 1353NM (EML) layer.

No path crosses the ring
SEQUENCE
a) Create the NPA 4-f for the topology which represents the existing ring
b) At the NE/EML layer read the information of Node Id and Node Position per each node of the ring
and move these information to 1354RM map.
c) Issue NPA: Specify Ring map setting Node Position and Node Id.
d) Issue Download Disable
e) Implement the ring
f) Execute the Mark Audit and verify differences, if any
g) Enable download
2.2.11 Upload Tools

The Upload Tools wizard allows to execute the following actions:

– Automatic Generation of Trace Identifier
– Upload Physical Connectivity
– Upload of Protection Schema
the Upload Tools wizard can be started from network, subnetwork, node.
Figure 129. Sbn: Configuration: Upload Tools
2.2.11.1 Automatic Generation of Trace Identifier (JO SET-UP)
J0 set-up can be entered from the Network, Subnetwork or Node, issuing the command Actions: Con-
figuration: Upload Tools.
From the Upload Tools dialog box (see following figure), select option Automatic Generation of Trace Iden-
tifier, which means J0 definition and click on Finish button to confirm. The following string is automatically
entered:
R$NDMPORTIDENTI
where NDM=Network Domain Id (3 characters), PORTIDENTI=port identifier (10 characters)
As an alternative, sent and expected J0 can be entered by the operator by using the CT/NM when the
fiber pair in put in service.

Figure 130. Upload Tools: Automatic generation of Trace Identifier
2.2.11.2 Upload Physical Connectivity
SCOPE
The scope of this procedure is to upload the physical media adjacency of the network. This means that
SDH/SONET physical links are automatically created in RM, when a fiber pair is connecting two ports.
The discovery is performed by using the trace identifier J0
CONDITIONS
The Automatic Generation of Trace Identifier has been previously executed.
SEQUENCE
a) The upload command is performed on one of the two NEs. Issue Configuration: Upload Tools. Select
option Upload Physical Connectivity
It is possible to issue this command on the whole network or on a subnetwork.
b) Click on Finish button to confirm

Figure 131. Upload Tools. Select option Upload Physical Connectivity
The action responses are directly displayed in the 'upload NPA' box at the User Interface.
2.2.11.3 Upload of Protection Schema
SCOPE
The scope of this procedure is to upload the Protection Schemes. This means that the protection schemes
are discovered and the relevant NPA is automatically created in RM.
NPA user label is: Auto-Disc-porId
where portId is the identifier of the port marked with channel number 0 (main)
CONDITIONS
The Upload Physical Connectivity has been previously executed.
SEQUENCE
a) The upload command is performed on one of the two NEs. Issue Configuration: Upload Tools. Select
option Upload of Protection Schema
It is possible to issue this command from node, network or subnetwork.
Select the type of protection schema: 2FMS Spring or
It is possible to set the auto implement option: the discovered NPA, after creation in RM database,
is implemented.

b) Click on Finish button to confirm
The action responses are directly displayed in the 'upload NPA' box at the User Interface.
Figure 132. Upload Tools: Upload of Protection Schema
As an example, figure which follows, shows the discovered 2-F MS Spring NPAs

Figure 133. Discovered NPAs
Internal Physical Connection Management
RM allows to manage a Physical Connections between ports of the same NE: this is mainly for WDM NE
management but it can be used in particular SDH application.
The following commands/actions are available:
– Creation of an internal physical connection

– The user can specify an internal physical connection by entering twice the Node to be intercon-
nected.
– Implementation of an internal physical connection
– Removal of an internal physical connection
– Display of an internal physical connection
Note that Physical Connection(s) between ports of the same Node are not displayed on the maps.
Internal Physical Connections can be retrieved through inventories requiring all Physical Connections that
are present in the topology where the Node is included, or that are starting-ending in the Node.

2.2.12 2Mb/s retiming management
SCOPE
The scope of this procedure is to enable/disable the retiming functionality, i.e. to manage a 2Mb/s syn-
chronous timing source going out from a certain NE port, used to synchronize the PDH network, in order
to reduce the pointer justification wander.
The value of the retiming is not reset to the default value when the path is de-implemented, but
it is persistent and it is taken into account when the path is again implemented.
This feature allows the enabling/disabling of the retiming functionality. This functionality is used to process
a 2Mb/s signal, going out from the NE, which can be used as synchronous source in a PDH network, so
that it does not have the wander created by pointer justification. When retiming is activated, the outgoing
signal is retimed with a clock free of the wander.
This procedure includes also the configuration of the action to perform in case of loss of synchronization.
The consequent actions that can be configured are:
– timingPDH (default) . Timing of the outgoing signal is synchronized by the incoming signal
– AIS. All ones are inserted in the 2Mbit/s outgoing signal
CONDITIONS
The functionality is applied at path level. The functionality can be enabled/disabled on the ports related
to the path. The retiming can be defined only for an already implemented or partially implemented path.
The retiming functionality is applicable only for 2Mbit/s signals and on ports belonging to Q3 NEs
SEQUENCE
a) Point to the path whose port is to be used as synchronization source and open the pop-up menu.
Select Configuration: 2Mbit/s Retiming management. See Figure 134. The Path Retiming wizard -
step 1 is displayed. See Figure 135.

Figure 134. Path: Configuration: 2Mbit/s Retiming management
Figure 135. Path Retiming; step 1

b) Click on Next button. The Path Retiming wizard-step 2 is displayed. See Figure 136.You can enter
the following:
• retiming supported (retiming/notsupported)
• retiming state (Disabled/Enabled)
c) Enter the suitable selection
Figure 136. Path: retiming: port selection-step 2

Figure 137. Port: Retiming state=enabled
The Operator can modify the retiming and the related consequent action on the displayed ports. For uni-
directional or broadcast path, only the "sink" ports supporting the retiming functionality are presented to
the Operator. In addition it is possible to navigate on the 1353NM in order to get further information.
The consequent actions are applicable only for ISDN-PRA or Leased Line signals and can be configured
only for bi-directional paths and only if the retiming functionality has been enabled.
2.2.13 Network implementation

– By network implementation it is meant putting the previously tested network in service .
– The NEs are reset and a default configuration is sent for the NE which includes only higher order
CTPs.
In case of NPE MS-Spring the Topology Implementation process performs the following steps:
a) starting from the “sequence number in et" node attribute (it provides the position of each node in the
et), it builds the string corresponding to the ring map info attribute of the 4f MS Protection Block MOC
b) for each node of the et:
1) it creates, 'contained' in the node, the MS Protection Block MOC filling the Configuration State
attribute with the “virtual" value

2) it submits to the proper TSD-IM Front End Processor (in charge of the node) the request to
change on the MS Protection Block (contained in the node and related to the et) the Configu-
ration State attribute to the “active" value and the ring map info attribute to the string set up at
step a). In case the topology is modified adding/removing a node and the et is requested to be
implemented again, the topology implementation process submits the request to change the
ring map info attribute only.
a) To execute the network implementation select the Network/Subnetwork/Ring icon in the Root/Net-
work/Subnetwork window and issue the command Actions: Configuration: Implement.
2.2.14 Payload structure modification:Ho/Lo

The payload structure is automatically executed by the system upon path allocation.
Anyway the user may change manually the Ho/Lo structure. The required menu item is present in yhe lc
pop-up menu. See following figures.
Figure 138. Payload structure modification: Ho-Cfg

Figure 139. Payload structure modification: Lo-Cfg
2.2.15 Trail Creation Wizard
2.2.15.1 Introduction
A HO-Trail can be created only between nodes external to the NPE MS-Spring.
The Trail creation wizard function is used to create, allocate, implement and configure an HO-Trail within
the SDH Network. A HO-Trail is a transport connection between HO-TTPs (HO-CAPs) related to SDH
ports. A HO Trail provides LO resources (LO-LCs) to carry LO traffic (i.e. LO paths).
Being a wizard, the user is driven by a series of steps to execute the procedure; subsequent boxes are
to be filled with requested parameters or values; in the first part of the boxes some comment helps the
user filling-in the fields; the Next button go to the next step/box and the Prev button allows to change pre-
viously entered values; the Finish button gives the execution of the procedure.

N.B. The user creates a network with different subnetworks.The user tries to select simultaneously
two NEs between two subnetworks and it is possible. But, once opened the trail window, only
one element is present, the first one selected. This is due to the structure of ilog maps. Namely,
it is possible to select a couple of nodes only if they belong to the same map view.
2.2.15.2 Operation
a) Select the Trail Termination points to be created on the map and then on the menu Actions: Create:
Trail. A sequence of boxes will open-up together with a browser window (if not already open).
Figure 140. Create trail wizard step1:configuration
On the upper part of Step1 box figure, there are helpful notes about choosing/selecting the parameters
and values.
b) Step1 of the trail creation box allows to set up many parameters, divided into folders:
– configuration
– protection
– PM
– Routing
– CP Restoration
The explanation of all parameters is the same as detailed at para Path Create

Figure 141. Create trail wizard step1: protection
Figure 142. Create trail wizard step1: protection

Figure 143. Create trail wizard step1: PM
Figure 144. Create trail wizard step1: routing

Figure 145. Create trail wizard step1: CP restoration
The subsequent steps to complete trail creation are the same as described in paragraph Trail setup
including an external network.
2.2.16 Improved path/trail management
2.2.16.1 Path highlight including crossed trail
Path highlight includes the crossed trail. See following figures.

Figure 146. Highlight of the path
Path highlight includes the crossed trail.
Figure 147. Highlight of the path including the crossed trails

2.2.16.2 Trail setup including an external network
Trail setup is possible between external networks and external network-real NE
Figure 148. Trail setup between external networks

Figure 149. Trail setup between an external network and a real NE
2.2.17 Upload NAPs

The Upload NAPs operation is required ONLY FOR QB3* NEs, to take in charge the NAPs (Network
Access Points) at RM side.
NAPs are Lower Order Trail Termination Points for 2 Mb and 34 Mb tributary ports or Higher Order Trail
Termination Points for 140 Mb tributary ports. In practice a NAP coincides with a VC-12, or VC-3, or VC-4.
As a result of this command, PDH ports are assigned to the Regional Manager and the related TTPs are
created in the RM database.
This command can be issued for the whole network, for a subnetwork only, or a single Node.
It can be launched from Browser or Netview.
This command is not required for QB3 NEs. As a default NAPs are uploaded upon Node create.
SEQUENCE
a) From the browser window point with the mouse at the topological object whose NAPs are to be
uploaded and open the pop-up menu. Select menu item Configuration: Upload NAPs. See Figure
150. A dialog box alerts that the action has been correctly started.

Figure 150. Topological object: Configuration: Upload NAPs.
2.2.18 Take-over of retiming

SCOPE
This feature allows to upload the retiming configuration from an existing network.
CONDITIONS
This feature is useful when the retiming has already been configured in the network (e.g. from SH) and
RM has to take in charge this configuration
SEQUENCE
a) the Synchronize NE command has to be executed on all the NEs that can support 2Mbs ports. As
a consequence, the retimingSupported attribute of the port is aligned
b) the NE has to be put in Download disabled mode
c) a dedicated script has to be executed. This script contains the following steps:
• the Consistency Audit (notify modality) has to be performed on all the ports involved in a path
and with the retimingSupported attribute different from notSupported. (through a dedicated
script). As a consequence, the consistency status of all the ports with the retiming enabled in
the NE is set to consistencyMismatch.
• the retimingStatus attribute of the paths involving ports with the consistencyStatus attribute
equal to consistencyMismatch is aligned (set to enabled. As a consequence, the retiming
attribute of the involved ports is aligned (set to enabled)

N.B. As the NE is in Download disabled mode, the consistencyStatus attribute of the involved ports
is equal to notAligned. Performing a new Consistency Audit (notify modality), the consisten-
cyStatus attribute will be set to normal. At the end, the NE has to be put in Download enabled
mode. the batch file has to be executedPM on regenerator section monitoring function (WDM/
PM/B1)This feature deals with the Performance monitoring of client path (B1 monitoring).
2.2.18.1 Measurement types
The supported types of PM measurements are:
PM 15 minutes for Maintenance (unidirectional)
PM 24 hours for Maintenance (unidirectional)
2.2.18.2 Creation of PM TPs
When a raw connection is transformed in a client path, RM automatically creates, for each end point of
the created client path, the following PM TPs:
• 24 hour / 15 minutes ingressing unidirectional for the boundary CTP
• 24 hoursminutes ingressing unidirectional for the adjacentBoundary CTP
PM TPs are created taking into account NE restriction. For example, in case of 1696MS, only the PM TP
for the adjacentBoundary CTP can be created.
N.B. The automatic creation of PM TPs can be disabled thought an environment variable set at
installationtimeManual Management of OADM Connectivity

2.3 Transport Management
– Path Provisioning and path visualization
– Path Constraints
– Add Leg
– OS driven restoration
– Join/Split path
– Join/Split trail
– Join/Split Physical Connection
N.B. After a 1354RM merge operation the Join/Split procedures will be used in the following order:
1-join path 2-join trail 3-join physical connection
– ISDN management
2.3.1 Path Provisioning
The path creation can be executed only in an implemented network with already uploaded NAPs.
Path Provisioning is composed by:
– path create. define a connection by making a reservation of its end points
– path allocate. make reservation of the route within the network. The route includes all relevant ele-
mentary connections (connections in topology). Path deallocate is the reverse operation
– The allocation algorithm chooses the less costly route by applying the Dijkstra algorithm
– path implement. transmit to the network the commands to activate all included connections in topol-
ogy, thus implementing (i.e. activating) the whole path. Path deimplement is the reverse operation
– path Commission, Decommission is only a lock which can be set / removed to / from an imple-
mented path
– path constraints. Used by the allocation algorithm, which is forced to follow user's preferences in
selecting the path route
It is possible to execute the allocation, deallocation, implementation, deimplementation, commission,

decommission on several paths at the same time.
You can then display the path route using the SDH netview or browser application.
Examples of path create commands (pull-down and pop-up, respectively), are shown in Figure 151.and
Figure 152.

Figure 151. Actions: Create: Path pull-down menu
Figure 152. Node: Create: Path pop-up menu

2.3.1.2 SHDSL path management for ISA BCE E1 1.0
With the ISA BCE board - 2Mbit/s application, the customer device (remote NTU) receives, from a cus-
tomer localPDH interface, E1 traffic and encapsulates it in a VC12, which is carried by SHDSL copper to the
ISA BCE board.
SHDSL is terminated on LTU side (ISA BCE board), VC12 is extracted and cross-connected in the OMSN,
then transmitted over SDH network.
The PDH port is characterized at the interface in such a way to allow the RM to distinguish it from a normal
PDH.
2.3.1.3 Remove an implemented, partially implemented or allocated path/trail
Allocation/de-allocation
When the command is started, a window is opened by the browser and a message is displayed to inform
the user if the operation is correctly started or not.
At the end of the command a message is displayed to inform the user if the operation is correctly finished
or not. If not, a raw error reason is provided to the user and he can have more details using the Path failure
Implementation/de-implementation
During the execution of the command some additional information can be displayed to the user. It can be
indication for the user, warning or error result related to an elementary operation (e.g. a cross-connection
creation failed).
At the end of the command a message is displayed to inform the user if the operation is correctly finished
or not. If not, a raw error reason is provided to the user.
Remove
The remove command of a path/trail is allowed even if the path/trail itself is implemented, partially imple-
mented or allocated.
During the execution of the command some additional information can be displayed to the user.
2.3.2 Path Create management

INTRODUCTION
Path management consists in:
– path create. define a connection by making a reservation of its end points
– path allocate. make reservation of the route within the network. The route includes all relevant ele-
mentary connections (connections in topology)
– path implement. transmit to the network the commands to activate all included connections in topol-
ogy, thus implementing (i.e. activating) the whole path

– path constraints. Used by the allocation algorithm, which is forced to follow user's preferencies in
selecting the path route
2.3.2.1 Path Create
SEQUENCE
a) Launch the path create application. The path create wizard is displayed. See Figure 153.
N.B. The user creates a network with different subnetworks. On these subnetworks, the user creates
some Ets with many adms. The user tries to select simultaneously two adms between two Ets
and it is possible. But, once opened the path window, only one element is present, the first one
selected. This is due to the structure of ilog maps. Namely, it is possible to select a couple of
nodes only if they belong to the same map view.
N.B. Multicast Path Create

The path create wizard is designed to take also into account the management of the mul-
ticast path (both X and Y configuration). The part related to the source Spare and sink
Spare are displayed only if the user requires to add the Spare (source or/and sink) by
means of the dedicated button
Figure 153. Path Create step1
b) Enter the following values:

– Service type (PDH/ATM/ETHERNET /DATA/CBR)
1) If you select PDH, selectable service rates are those shown in Figure 154.
Figure 154. Service type PDH: Service rate selection
2) If you select ATM, selectable service rates are the following:
Figure 155. Service type ATM: Service rate selection
3) If you select Service type=Ethernet, selectable service rates are;
Figure 156. Service type Ethernet: Service rate selection
4) If you select Service type=DATA, selectable service rates are shown in figure which follows:

Figure 157. Service type DATA: Service rate selection
Figure 158. Service type SDH: Service rate selection
a) For a 10-100Mb path enter:

– Service Rate=10-100 Mb Rate Adaptive
– Transport Rate: any
– Service type=Ethernet
– Service Rate=10-100 Mb Rate Adaptive
– Transport Rate: any
– Configuration rate: Automatic 10 Mb / Automatic 100 Mb / Manual 10 Mb / Manual 100 Mb
– Automatic means that the path adapts the rate to the ethernet port rate
– Manual means that the path does not adapt the rate to the ethernet port rate
– path name
b) For a 1 Gb transp see description at paragraph
– Path type. For details see explanation at section Technical Annexes.
Figure 159. Path type selection
– SNCP type
it describes different types of SNCP protection schemes for a path/trail. Allowed schemes are:
-SNCP/I (Inherent)
-SNCP/N (Not-intrusive)

The two schemes are related to the switch criteria. In particular:
SNCP/I switch criteria: AIS and LOP
SNCP/N switch criteria: Server Signal Failure, Signal Degraded, Trace Identifier Mismatch, Excessive-
BER and Unequipped
The user can specify the preferred type of SNCP protection using the Path Creation (for paths) and Set
up Trail (for trails) commands. Anyway, the type of SNCP protection can be modified, in a second step,
even if the path/trail is implemented.
If the user wants to add the protection to an unprotected path/trail, he has to use the Add Protection com-
mand. The preferred type of SNCP protection has to be previously chosen by the user modifying the
related attribute of the path.
Since this feature is not supported by all the NEs, a path/trail may have SNCP/I and SNCP/N protections.
RM does not provide provisioning of SNCP/N switching criteria (i.e. Excessive BER, Signal Degraded).
Figure 160. Path SNCP type
NOTE: For a path/trail, the management of this feature foresees the introduction of the following new
attributes:
sncpType: it specifies the type of the protection of the path/trail. The allowed values are:
• -sncpIpreferredNoAlr: the SNCP/I type has to be preferred for all the protected connections
of the path/trail
• -sncpIpreferredAlr: the SNCP/I type has to be preferred for all the protected connections of
the path/trail.The alarms have to be enabled on the unreliable CTPs involved in
the protection (default value)
-sncpNpref: the SNCP/N type has to be preferred for all the protected connections of the path/trail
– Protection. For details see explanation at section Technical Annexes.

Specifying "SNCP," the user requests to find the best protection by minimizing the number
of overlapping NEs and physical connections. Select SNCP type
Figure 161. Protection selection
D&C
For paths and trails with the protection type set to D&C, RM should be able to perform the automatic add-
ing of drop & continue connections when the main and the spare cross the same SNCP NPA ring.
In case of unsatisfactory results of the automatic algorithm, D&C can now be added or removed manually
specifying the start and end points.

The following rules are also used:
– The D&C must use only the resources of the NPA and protects only one direction.
– D&C related to adjacent NPAs are merged together producing dual node cross-connections in the
involved NEs
– Unneeded changes of rings is one of the possible source of wrong D&C protections
The NPA can be used as a type of constraint for paths & trails. The constraint types are:
– Use main. The main route of the path must use at least one of the physical links belonging to the
NPA. At Lower Order the LC satisfying this constraint must be completely contained in the NPA (i.e.
its server trail must use only physical connections internal to the NPA)
– Use spare. (as before changing main with spare)
– Don't use main
– Don't use spare
The add protection and D&C can now be performed without any limitation related to the partitioning (i.e.
to the involved topologies): any Node of the main can be selected as a starting or ending point of an added
spare protection.
No constraint exists anymore on the way to perform the network construction in order to allow path/trail
protections
The add/remove protection and add/remove D&C is performed from a wizard that allows to select the right
TPs or Nodes for the specified operation (protection in a NPA to be confirmed)
– MS Protection Usage Profile. For details see explanation at section Technical Annexes.
Figure 162. MS Protection Usage Profile
c) Click on Next button. The wizard presents now the Step 2 dialog box.

Figure 163. Step 2: End Points selection: Node selection: example of path
d) Step 2 wizard (see figure above) is designed to support the creation of the multicast path (both X and
Y configuration). The part related to the A spare and Z spare is displayed only if the user requires
to add the spare (A or/and Z) by means of button Add Backup. This button is enabled only if the
path is protected SNCP or D&C SNCP.
e) End Points selection: Node selection: request the list of the available nodes. A list of nodes is shown,
with the following characteristics: (alternatively it is possible to use the drag&drop functionality)
for non virtual concatenated paths:
External Networks with idle CTPs at the rate of the path (in this case the user can specify the name
of the client port to be created on the External Network)
nodes with idle boundary CTPs at the rate of the path
nodes with boundary HO CTPs belong to an HO-trail with at least one idle client link connection at
the rate of the path (only for a LO path)
for virtual concatenated paths:
External Networks (in this case the user can specify the name of the client port to be created on the
External Network)
N.B. For each node in the list, it is indicated if the node contains LO CTPs, HO CTPs or both.
f) SDH port selection

After the selection of the node, select the SDH port of the node to use (except for the case of con-
catenated paths where neither the port nor the timeslot have to be provided).
It is possible:
to request the list of the available SDH ports. In this case the system shows a list of ports, according
to the selected node and with the following characteristics:
• External Network: SDH ports with idle CTPs at the rate of the path
• real NE: SDH ports with idle boundary CTPs at the rate of the path
• SDH ports with boundary HO CTPs belong to an HO-trail with at least one idle client link con-
nection at the rate of the path (only for a LO path)
to use the drag&drop functionality
N.B. The user can avoid entering SDH port and time slot (only if the node is an External Network).
In this case, they are automatically chosen by the system at allocation time: SDH port to min-
imize the path cost and the first free time slot.
g) time slot selection
Select the time slot of the CTP to use.
It is possible:
to request the list of the available time slots. In this case the system shows a list of time slots, accord-
ing to the selected node and port, with the following characteristics:
port of an External Network: time slots related to idle CTPs at the rate of the path
port of a real NE:
time slots related to idle boundary CTPs at the rate of the path
time slots related to the CTPs at the rate of the path ending, on the External Network side, the
idle link connections of the HO-trails related the port (only for a LO path)
For each time slot, the following information is displayed:

the port name of the related port on the External Network
the payload position of the CTP on the External Network
the port name of the port on the real NE
the user label of the HO-trail involving the CTP
to enter directly the time slot. The time slot is a string with the following syntax:
AU4#
AU4#/TUG3#/TU3#
AU4#/TUG3#/TUG2#.TU12#
the user can avoid entering the time slot. In this case the first free time slot is automatically chosen
by the system
h) At the end of the operation, when the Finish button is pressed, the command to create the path is
sent to the Transport Service Agent with the following information:

for each terminated end:
the node
the node and the NAP
for each non terminated end:
the External Network and, optionally, the name of the client port
the External Network, the SDH port, and the time slot and, optionally, the name of the client port
the real node, the SDH port and the time slot
The name of the client port can be optionally provided.
As a result following steps are performed:
• the NAP is created on the External Network
• the CTP at the rate of the path on the External Network is marked ("userReservation" attribute
set to "forPath")
• a fixed cross-connection between the NAP and the CTP is created in RM DB
• the path is created
N.B. If the SDH port and the time slot of the External Network are not provided in the request,
the CTP will be chosen and connected to the NAP by means of a flexible connection at
allocation time. The CTP itself is not marked as reserved ("userReservation" attribute not
modified).
i) Click on Next, passing to Step 3-Attributes selection. See figure which follows. Select:

Figure 164. Path Create: step 3

CONFIGURATION
– Allocation rule (User / Automatic)
– Allocation Rule: it specifies if the path has to be allocated automatically after its definition
or subsequently upon user's command.
– Implementation rule (User / Automatic)
– Implementation Rule: it specifies if the path has to be implemented automatically after

having been allocated or following an user's request.
– Allocation Constraint (All Objects / Not Alarmed Objects)
– Algorithm (Automatic)
ALARM
– Propagation rule (when defined / when allocated / when implemented /when commissioned)
– Client Alarm Enabling Rule (On Implementation / On commissioning / Manual)
– Transport Alarm Enabling Rule (On Implementation / On commissioning / Manual)
ROUTING
-Routing parameters for paths and trails
-Main & Spare Cost gravity Factor
Percentage discount on NPA usage cost (NPA thru cost), only for spare route evaluation, while the main
already is crossing that NPA.
-D&C IC Cost Factor
Percentage of cost to avoid spare route direction different from main route direction. This percentage cost
is added to physcon basic cost if used in the direction opposite to the main route direction.
The definition of spare as disjointed from main, is respected.
N.B. If the user, when creating the path, selects Alarm Enabling Rule: Manual, for this Path it will be
possible to enable / disable the involved alarms (from the Path List: menu Actions: SDH/PDH
Alarms enable/disable.

USER
– Comment1-2, Customer, Text1-2-3 are text strings
– Path Group, to be used when defining multiple paths belonging to the same path group
– Automatic Monitoring (True/ False). If true starts the 24 h PM activity on path implementation
CP RESTORATION. It contains:
– Restoration Mode (No Restoration / On Control Plane)
– Priority of the path in the ASON network
j) Click on Finish button. The path is created and the routing view is displayed.
Figure 165. Path just created
N.B. Fast Ethernet boards have been already correctly set-up on the Equipment via 1353NM.

2.3.2.2 10/100Mbits Ethernet management (point to point)
The 10/100 Fast Ethernet board acts as a gateway towards the SDH network and is connected to the SDH
matrix via a STM-4 equivalent interface. Each of the 10 or 100Mb/s Ethernet traffic interface of the board
is mapped in a set of VCn (n=12, 3 or 4).
The Ethernet traffic is transported transparently in the SDH network: the board on the OMSN NE drops
Ethernet traffic towards switches or router without "terminating" the Ethernet frames.
Two cards constitute the board: an access card that provides 14 interfaces and a main one that provides
11 interfaces. The Ethernet traffic, mapped in the SDH transport structures, is then sent towards the SDH
matrix via a STM-4 equivalent interface.
To set-up an SDH path supporting, as client, the Ethernet traffic, execute the following steps:
a) upload the Data ports. The uploaded ports are created in the RM MIB. The technology of the ports
is "Data"
b) upload the Data NAPs. As a consequence of this operation the generic Data NAPs are created in
the RM MIB (no interaction with the NE)
c) create a path connecting two Data NAPs. The user enters the following information:
the two Data NAPs
the type of the server SDH container (tu12, tu3 or au4) or (tu12-nV - tu3-nV). If the user selects the
virtual concatenation (tu12-nV - tu3-nV), he will enter the number n (no. of TUs).
In the fact the path creation includes the specification of the VCs. As a consequence, data NAPs are
created in the NEs accordingly.
Figure 166. Fast Ethernet board

Figure 167. Fast Ethernet board view
Figure 168. Fast Ethernet board: Port view
Figure 169. Objects on browser.

2.3.2.3 Multi Path Create
Figure 170. Multiple path creation button
If the Operator selects the Multipath Create button, (see above figure), a dialog box is displayed. The fol-
lowing values must be specified:
Figure 171. Multi path creation
– Number of paths (numerical value)

– Starting (numerical value)
– Append (radio button)
– Replace (radio button)
If Append is selected, the path sequential numbering is added as a suffix to the name of the path.
If you want to insert the sequential numbering in the inner of the path name, the userlabel containing the
%nd characters should be written where "n" corresponds to the numbering field size. In this case you have
to select "Replace".
The Associate feature is provided (same route) if the following are selected:
number of paths >1
starting any
This feature allows to associate as constraint the first created path. The user can carefully setup the
first created path. The remaining ones will have the same route.
NOTE: Only nodes must be specified in this procedure.

End points for multiple path creation must be nodes. If a port and a time slot is specified it is impossible
to create more than one path.
It is impossible to specify a port without specifying the time slot.
The correct procedure is:
- multiple path creation without port and time slot (allocation rule = user)
- force paths to overlap the first one created (select button "associate as constraint the first created path"
in the last step of the wizard)
- open constraint wizard for the first path and add drop CTPs as constraints
- allocate first path
- allocate all the other paths (their route will overlap first path because it was specified in creation to over-
lap the first one)
2.3.2.4 Constraints
SDH routing is performed on a cost basis. This means that a route having the least cost will be used when
setting up a path.
The user can specify some constraints to be used by the allocation algorithm either during the path allo-
cation or the path add protection activities. These constraints are used to:
• specify the involved resource,
• indicate if the path has to cross the specified resource or not,
• specify if the constraint has to be applied to the path main route or to the spare one or both;
The user is informed at the end of the allocation activity.

Execution of path operations can be scheduled to a specified time.
The user is able to protect/unprotected a path in a given topology or in the whole network.
2.3.2.5 Path Constraints
– Path constraints allows the user to specify the constraints to be used by the allocation algorithm dur-
ing either the allocation or the protection activity or the addition of a leg in a broadcast path (i.e. Allo-
cate path and Protect path services broadcast path end point add). The user specified constraints
overrides the cost based allocation policy.
The constraints are defined by the following characteristics:
• Involved resources: they can be sub-networks, ETs, nodes, link connections, physical connec-
tions, CTPs, server trails and routing links.
• Constraint type : it specifies whether the path must use the specified resources or not
• Route Type : it specifies if the constraint is applied for the main route only, for the spare route
only or for both routes.

UPON CREATING A PATH AND SPECIFYING THE NOT ALARMED RESOURCES ONLY
OPTION, RM ONLY TAKES INTO ACCOUNT THE ROUTING RESOURCES AND NOT THE
NAP ONES.

2.3.3 Non terminated path
2.3.3.1 Routing display of a defined not terminated path
Path routing display of a defined not terminated path in addition to the NAP on the External Network,
shows:
the cross-connection, on the External Network, between NAP and CTP
the CTP on the External Network
the link connection
the CTP on the real NE
2.3.4 Path ends modification

The user can obtain an X or Y path modifying an existing one, by means of the Add ends/Remove ends
option of the Path ends modification tool. The user has to provide the end points he wants to add/
remove. The added end points are always spare, while the removed ones can be main or spare.
N.B.: During the add end points operation, the user can decide either associate the new end points to the
path or automatically allocate/implement the spare route.
2.3.4.1 Path ends modification: Add End Points
a) Select Add ends/Remove ends option of the Path ends modification tool
Figure 172. Path ends modification: Add Backup End Points
b) From the following box, select the Backup end point to add

Figure 173. Backup ends specification
c) Click on Finish button to confirm. Figure which follows shows an example of modified routing display.

Figure 174. Modified path routing display
Remove End Point
If Remove End Point option has been set at above step 1, following selection dialog box is presented.
Select the points to remove and click on Finish button.
Figure 175. Path ends modification: Remove End Points

2.3.5 Gigabit Ethernet path
The system is able to support the GigaEthernet rate adaptive on single VC4 virtually concatenated (VC4-
1v).
The following table lists the services supported by RM and the mapping with the Transport rate inside
the Transport Network:
SERVICE TYPE SERVICE RATE TRANSPORT RATE
ETHERNET 1 Gbit/s Ethernet transparent AU4-nV

(concLevel=8)
1 Gbit/s Ethernet Rate adaptive AU4-nV

(concLevel=1-7)
10/100 Mbit/s Ethernet Rate TU12-nV

adaptive
TU3-nV
AU4
10 Gbit/s Ethernet EPL AU4-nV (point to point)
10 Gbit/s Ethernet EVPL AU4-nV (point to multipoint)
2.3.5.1 1 Gigabit transparent path
DEFINITION
The 1 Gigabit transparent path makes use of a virtual concatenation of 8 AU4s to support the AU4-8V con-
nection rate.
The connections in topology between the 1 Gigabit NAP and the CTP are fixed, i.e. they cannot be
changed or deleted by 1354RM.
With reference to Figure 176., the 8 trails, which are virtually concatenated can be allocated to different
routes within the network
connection in topology FIXED AU4-8V

LC
CTP CTP
CAP-1 hotrail1 AU4-1

CAP-8 hotrail8 AU4-8
Figure 176. 1 Gigabit connection structure

2.3.5.2 Create 1 GB transparent path
The following figure show an example of creation of 1 GB transparent path
Figure 177. GB Eth path create step1

Figure 178. Path create step 2
2.3.5.3 Display 1 GB transparent path
The path routing display is shown in the following figure. Notice that the link connection configuration state
is implemented. Click on Server trail icon. The trail list of the 8 virtually concatenated trails is displayed.
See Figure 182.
Or, to highlight an Ethernet path issue, for the path : Search: Related Items: Server Trails.
The list of Server Trails is then displayed

Figure 179. Display: Server Trails
Each trail can be highlighted
Figure 180. Server Trail list

Figure 181. 1 Gigabit path routing display
Figure 182. Trail list
If all 8 trails are allocated, the attribute Server connectivity of the path is equal to fully connected.
If only some trails are allocated, the attribute Server connectivity of the path is equal to partially con-
nected. In this case the operator may add resources and subsequently allocate trails whose working
state is fail to allocate.

d) Launch path implementation. The system executes the implementation of the 8 trails.
It is possible to launch path implementation also on a path having some trails allocated and some
defined. In this case the path goes implemented, its defined trails remain defined, the allocated trails
go implemented or partially implemented.
2.3.5.4 EXAMPLES
EXAMPLE 1
A path has 7 trails allocated and 1 trail fails to allocate. By launching the implementation on the trail failed
to allocate, the server connectivity of the path goes fully connected.
EXAMPLE 2
A path has 1 trail allocated and 7 trails defined. By launching the deallocation on the allocated trail, the
path goes defined and all involved trails are deleted.
EXAMPLE 3
A path is allocated. By launching the implementation on one trail, the path goes partially implemented
2.3.5.5 1 GBit path protection
The Add Protection operation is available for the entire path or at trail level.
The protection can be viewed on the trail routing display.
2.3.5.6 Constraints
Constraints can be given at level of path or at level of trail. As usual, the system makes use of constraints
during allocation phase.
Figure which follows shows an example of constraint set-up.
Figure 183. Path: Modify Constraints

2.3.5.7 1 Gbit/s Ethernet Rate Adaptive
The 1 Gbit/s Ethernet Rate Adaptive path can have rate AU4-nV with n=1-7.
An example is shown in figures which follow.
Figure 184. 1 Gbit/s Ethernet Rate Adaptive path attributes
Figure 185. 1 Gbit/s Ethernet Rate Adaptive path routing display

Figure 186. 1 Gbit/s Ethernet Rate Adaptive path trail list
2.3.5.7.1 Operations on server HO Trail
The User, directly to a Server HO Trail, can perform the Allocation, De-allocation, Implementation, De-
implementation, Add protection, and Remove protection operations.
The operations allowed on the server HO Trail depend only on their configuration state, regardless the
GbE concatenated path configuration state. The path working state is checked in order to avoid concurrent
operations.
The configuration state and server connectivity of AU4-1v link connection and concatenated path are
always re-evaluated. After an add/remove protection applied to a server trail, also the path protection type
is re-evaluated.
2.3.5.7.2 GbE Path Route, Server HO Trails and GbE Path Attributes display
The Operator can visualize the routing of a GbE Path and from the route display of GbE paths, starting
from the AU4-1v LC, it is possible to retrieve all the server HO Trail.
In addition for the HO Trail participating in the virtual concatenation group (also if only in this particular
case), it is possible to retrieve the client GigE Path or the AU4-1v LC.
2.3.5.7.3 Redo-log
The system will trace in the redo-log all the operations performed by the User on a concatenated path and
on the server HO trail.
2.3.5.7.4 GbE Path and Server HO Trail Alarms
Elementary Alarms related to the GbE Ports, NAPs, CAPs, CTPs are correlated to the Server HO Trail
and GbE Path, which affect the GbE functionality.
Alarms related to the HO Trail are managed as usual, while alarms related to a GbE Paths are issued when
the GbE service is affected.
2.3.5.7.5 GbE Path Highlight
The system, as for all the other type of paths, allows to highlight on the Map where a GbE Path is passing
through.

2.3.6 LCAS Management
LCAS (Link Capacity Adjustment Scheme), is a protocol that improves Virtual Concatenation.
This protocol applies to the following boards:
– boards belonging to the Integrated Service Adapter (ISA) board family, named ES1 and ES4. The
ES1 board has a throughput, towards the SDH network, of 155Mb/s while the throughput of the ES4
one is 622Mb/s.
– ISA Gbe (with LCAS)
The management of these boards makes use of LCAS (Link Capacity Adjustment Scheme), which is a
protocol that improves Virtual Concatenation, allowing to:
– hitless increase/decrease the capacity of a Virtual Concatenation Group (VCG) link
– temporarily remove a member link that was affected by a failure (this member is hitless added again
after failure recovery)
This paragraph describes the following procedures:
– Path creation
– Optimized diverse routing of server trails
– LCAS enabling/disabling on an already defined path
– LCAS parameters configuration
2.3.6.1 Path creation
2.3.6.1.1 10/100Eth Rate Adaptive (no concatenation) service
The usual information to create this type of path has to be provided by the user.
2.3.6.1.2 10/100Eth Rate Adaptive (virtual conc.) & 1Gbit Eth Rate Adaptive services
a) The user, to create a path, has to provide the following information:
– serviceType=Ethernet
– serviceRate of the path eth1GbRateAdapt / eth10or100MbRateAdapt
– type of the server SDH container to be used to transport the traffic (transportRate). The allowed val-
ues are:
• au4-nV for eth1GbRateAdapt (automatically provided by the system)
• tu12-nV or tu3-nV for eth10or100MbRateAdapt
– concLevel of the path
– all the other information required for the path creation (user label, ...)
The list of the NAP is available to the user, satisfying the following conditions:
– napRate attribute matching the service rate of the path

– au4maxSupportedConcLevel (tu3maxSupportedConcLevel", tu12maxSupportedConcLevel) equal
or greater than the concatenation level of the path
If the user selects the NAP's, the compatibility of the two selected NAPs is verified accordingly.
N.B. The user can select the node instead of one or two NAPs. The compatibility of the two NAPs
is automatically verified.
At this point, the lcasControl and the diversesrvTrailsRoutingPreferred attributes of the path are set
according to the following table:
A-end type Z-end type LCAS control server trails rout- proposed/modifi-
ing able to/by the user
NOTE 2
virtual node virtual node enabled diverseRouting- Y

Preferred
virtual node real node enabled diverseRouting- Y

Preferred
virtual node nap not available uniformRouting- N

conc type DIFFER- Pref
ENT FROM virtu-
alLCAS
virtual node nap not available diverseRouting- Y

conc type = virtu- Preferred
alLCAS
real node real node NOTE 1 NOTE 1 N
real node nap not available uniformRouting- N

conc type DIFFER- Pref
ENT FROM virtu-
alLCAS
real node nap NOTE 1 NOTE 1 N

conc type = virtu-
alLCAS
nap nap not available uniformRouting- N

conc type DIFFER- conc type DIFFER- Pref
ENT FROM virtu- ENT FROM virtu-
alLCAS alLCAS
nap nap not available uniformRouting- N

conc type DIFFER- conc type = virtu- Pref
ENT FROM virtu- alLCAS
alLCAS
napconc type = vir- nap enabled diverseRouting- Y

tualLCAS conc type = virtu- Preferred
alLCAS
N.B. The values of the two attributes are calculated by the TRS (Transport Management process)
taking into account the type of the two NAPs chosen by the TRS itself.

N.B. The Y value in the column means that the values specified in the two previous columns are pre-
sented to the user and he can modify them in the path creation phase; the N value means that
the values specified in the two previous columns are not presented to the user and are auto-
matically set by the TRS.
b) The user launches the path creation. The path is created.
The following steps are performed on the two involved NAP's:
– the lcasControl attribute is set according to the value of the lcasControl attribute of the path. In par-
ticular:
• if the lcasControl attribute is equal to enable, the lcasControl attribute of the two involved NAPs
is set to enable
• if the lcasControl attribute is equal to disable, the lcasControl attribute of the two involved NAPs
is set to disabled
– if the lcasControl attribute is equal to notAvailable, the lcasControl attribute of the two involved NAPs
is set to notAvailable. Anyway, if one of the two NAP has the concatenationType attribute equal to
virtualLcas, the lcasControl attribute of the NAP itself is set to disable
2.3.6.2 Optimized diverse routing of server trails
If the user, during the path creation selects the diverse routing option (diversesrvTrailsRoutingPreferred
attribute of the path equal to diverseRoutingPref), the allocation of the server trails will apply the diverse
routing mechanism. In particular: the trail numbered n+1 (even) has to have a different routing from its
previous trail numbered n (odd). So a fault (i.e.cut fiber) impacts only a route providing anyway a minimum
level of functionality.
If there are not resources problem, this diverse routing mechanism allows:
– to have the 50% of the server trails on a route and the other 50% on another route
– to add and remove bandwidth maintaining the distributions of the server trails on the two diverse rout-
ing
These points cannot be guaranteed when the network resources are not enough to allow the diverse rout-
ing. In this case, the odd and the even trails could have the same route (partial or total).
N.B. The user can modify the srvTrailsRouting attribute of an already created path in any allowed
configuration state (confSt equal to defined, allocated, implemented, ...). In this case the new
provided value will be taken into account for the allocation of new trails (the already allocated
trails are not re-routed).
Figure 187. Server trail routing modification

2.3.6.3 Path removal
When a path is removal, the lcasControl attribute of the two involved NAPs is set according to the Port/
NAP configuration table paragraph in this document.
2.3.6.4 Add/remove bandwidth
It is possible to add/remove bandwidth to/from a concatenated path increasing/decreasing its transport

rate (changing the number of the server trails). This is performed modificating the concatenation level
attribute of the path.
The trails are added/removed starting from the last existing trail. This means that no intermediate trails
can be added or removed.
2.3.6.5 Activation/de-activation of an intermediate server trail
The intermediate trails can be activated/de-activated, that is included/excluded in/from the concatenation
group. In case of de-activation, the transport resources are not released.
2.3.6.6 LCAS enabling/disabling on an already defined path
The lcasControl attribute allows the inter-working between an NE not providing the LCAS protocol and
another providing it. A path can be allocated between an end point supporting the LCAS protocol and the
other not: the LCAS protocol has to be disabled on the end point supporting it.
To have the LCAS functionality, the LCAS protocol has to be enabled on both the end points.
The user has to select the path and to choose the LCAS control command on the User Interface.
N.B. LCAS protocol can be enabled/disabled also in the path creation phase. See following figure.

Figure 188. Path create:eth-adapt:es:step 3: LCAS
Figure 189. Path: Modification: Lcas control menu
Figure 190. Path: Modification: Lcas control dialog box

2.3.7 Compatibility tables
The following tables list the compatibility between the NAPs rate, the Ethernet mapping, the Transport rate
and the Service rate of the path.

(iv) Restriction: the two NAPs are compatible but the path does not work.

(*) GFP value not sent to NE. The value entered by RM user could be not consistent with the value
stored in the NE.

NOTE: for ISA-PREA of OMSN from 4.2 on, also vc3-nV and vc12-nV to external network.

2.3.7.1 Path creation using 16xGbE boards
The ports supported by the 16xGbE board in the 1678MCC R3.1A or later are compatible with all the
portsproviding a 1GbEth Rate Adapter service. The particularity of these ports is that they can work only
with a fixed rate (vc4-7V).
To create a path involving one or both these ports, the usual information to create a normal
eth1GbRateAdapt path have to be provided by the user. Concerning the concatenation level value, RM
does not check that it has to be equal to 7. This means that if the user specifies a different concatenation
level value RM does not return any error: the error will be returned only by the NE.
It has to be noted that the server trails related to the path (or only a part of them or none) can cross the
ASON domain.
2.3.7.2 Rate adaptive path : Modification: Bandwidth
SCOPE
The scope of this procedure is to modify the bandwidth of a rate adaptive path.
SEQUENCE
a) From the path list point to the rate adaptive path and select Path: Modification: Bandwidth. The wiz-
ard dialog box opens.
b) The user can:
1) verify the concatenation status:
• Maximum supported concatenation level
• Total concatenation level
• Active concatenation level
2) select the action:
• Increase bandwidth

Figure 191. Modification: Bandwidth: Increase bandwidth
If you select Increase bandwidth you will enter:
• the no. of trails to add
• the status of the added trails : Defined / allocated / implemented / Activated
• trail(s) protection type: None, SNCP, D & C SNCP
Click on Finish button to complete the action. The action report is provided.

Figure 192. Action report: Increase bandwidth
From the path routing display, clicking twice on the DISPLAY SERVER TRAILS icon, you can display the
trail list of the involved path.
Figure 193. Display server trails button.

Figure 194. Server trail list
The created trails are added as the last items of the trail list
• Decrease bandwidth
If you select Decrease bandwidth you will enter:
-the no. of trails to remove
-automatic deactivation or not of active trails to remove
Removed trails are the last items of the trail list
• Activate trails
If you select Activate trails you will enter:
-the no. of trails to activate
Trails are activated sequentially starting from the first idle trail.

Figure 195. Modification: Bandwidth: Activate Trails
• De-activate trails
If you select Deactivate trails you will enter:
• the no. of trails to deactivate
• status of the trails being deactivated (deactivate / deimplement / deallocate)
Trails being deactivated are the last active ones.

Figure 196. Modification: Bandwidth: Deactivate Trails

2.3.7.3 Path: Ethernet mapping
SCOPE
This procedure allows to define the Protocol format to be used for an Ethernet path.
CONDITIONS
Path status is defined or allocated
SEQUENCE
a) Point to the Ethernet path and select Configuration: Ethernet mapping. The relevant wizard is dis-
played.
Figure 197. GFP Protocol Modification wizard
b) You can select among:

• null extension header with FCS (used for inter-working between Ethernet and ISA/IP board)
• null extension header without FCS (used for inter-working between Ethernet and other vendors
board)
• linear extension header with FCS (used in case of grooming Ethernet interfaces into a single
vc-n)
• linear extension header without FCS (used in case of grooming Ethernet interfaces into a single
vc-n)
c) Click on Finish button to confirm.

2.3.8 Gigab broadcast 1 source
SCOPE
The scope of this procedure is to create a Gigab broadcast 1 source path
SEQUENCE
a) Launch the path creation. In the create step 1 dialog box enter:
Service Type=Ethernet
Service Rate=1 Gb Rate Adaptive
Transport rate=AU4-nV
Total Concatenation Level=3. It is the no. of desired trails.
Configuration Rate=Manual
User label
Path type=broadcast
Protection=NONE i.e. NO PROTECTION
Number of Sink End points. It is the no. of desired sinks.
SNCP Type=SNCP/N preferred
Click on Next button.
Figure 198. Gigab broadcast 1 source: create step 1
b) Select the source (unique). Click on Next button.

Figure 199. Gigab broadcast 1 source: source selection
c) In the sink selection box select the first sink. Click on Next to select the second sink.
Figure 200. Gigab broadcast 1 source: 1st sink selection

d) In the sink selection box select the first sink. Click on Next to select the second sink.
Figure 201. Gigab broadcast 1 source: 2nd sink selection
e) After selecting the programmed number of sinks, according to the previously selected parameter
Number of Sink End points, click on Finish button.

Figure 202. Gigab broadcast 1 source: configuration
f) The path is created and the routing display, as defined, is presented. See below figure.
Figure 203. Gigab broadcast 1 source defined view
g) Allocate the path

Figure 204. Gigab broadcast 1 source allocation
h) The following is the routing display of the allocated path
Figure 205. Gigab broadcast 1 source allocated view
i) Click on Server Trail List icon. The relevant list is displayed.

j) Selecting a trail, you may get the Trail view
Figure 207. Trail routing view
k) The trail highlight is shown in figure below

Figure 208. Broadcast path highlight
2.3.9 Gigab broadcast 2 sources

SCOPE
The scope of this procedure is to create a Gigab broadcast 2 sources path
SEQUENCE
Total Concatenation Level=3. It is the no. of desired sinks.
User label
Path type=broadcast
Protection=SNCP

Figure 209. Gigab broadcast 2 sources: create step 1

b) Select the 1st source.
Figure 210. Gigab broadcast 2 sources: 1st source selection
c) Click on page button Backup and select the 2nd source. Click on Next button.
Figure 211. Gigab broadcast 2 sources: 2nd source selection

d) In the sink selection box select the first sink. Click on Next to select the second sink.
Figure 212. Gigab broadcast 2 sources: sink selection
e) After selecting the programmed number of sinks, according to the previously selected parameter
Number of Sink End points, clicking on Next button, enter the path detailed parameters and click on
Finish. The path is created and the routing display, as defined, is presented. See below figure.
Figure 213. Gigab broadcast 2 sources-3 sinks defined view

f) Point to the path and issue Path: Configuration Modify: Allocate. Refresh the view. The allocated
view is shown below.
Figure 214. Gigab broadcast 2 sources-3 sinks allocated view
g) Click on Server Trail List icon. The relevant list is displayed.

h) Selecting a trail, you may get the Trail view
Figure 216. Trail view

2.3.10 2 MB broadcast 2 sources
SCOPE
The scope of this procedure is to create a 2 Mb broadcast 2 sources path
SEQUENCE
Service Type=PDH
Service Rate=2 MB-LO
User label
Path type=broadcast
Protection=SNCP
Figure 217. 2 Mb BROAD 2sources create step 1

b) Select the 1st source.
Figure 218. 2 Mb BROAD 2sources: 1st source selection

c) Click on page button Backup and select the 2nd source. Click on Next button.
d) In the sink selection box select the first sink. Click on Next to select the subsequent sink.
Figure 219. 2 Mb BROAD 2sources: sink selection

e) The selection of the sinks ends when the programmed no. of sinks is reached.
f) Enter the detailed path parameters and launch the creation, and subsequently the allocation. Figure
which follows shows the routing view of the 2 mb broadcast allocated path.
Figure 220. 2 Mb BROAD 2sources view
g) Path highlight is shown below
Figure 221. 2 Mb BROAD 2sources highlight

2.3.11 AU3 path
For AU3 management the related environment variable has to be set first. Please refer to the
Administration Guide for details.
SCOPE
The scope of this procedure is to create an AU3 path
SEQUENCE
Service Type=PDH
Service Rate=AU3
User label
Path type=bidirectional
Protection=None or SNCP
Figure 222. AU3 path create step 1

b) Select the end points. See following figure

Figure 223. AU3 path create step 2: end point selection
c) Click on Next and enter the path detailed parameters. Click on Finish. The path is created.
d) Allocate the path. The routing display is shown below.
Figure 224. AU3 path allocated view

e) AU3 path implemented view is shown below
Figure 225. AU3 path implemented view
2.3.12 User's Default

In the most used wizards, such as Node Creation, Path Creation, Setup HO trail, Payload Modification,
it is possible to save many user's defaults, in order to customize the wizard in the most suitable way.
To do this, open the pop-up menu on the parameters written in italic:: the options Save and Revert to Sys-
tem defaults are available.
This option is available on a operator' basis.
Figure 226. Save user defaults

2.3.13 AU3-NV path
SCOPE
The scope of this procedure is to create a Gigab broadcast 2 sources path
SEQUENCE
a) Launch the path creation. See below figure.
Figure 227. AU3-NV path create
b) In the create step 1 dialog box enter:

User label
Path type=bidirectional

Protection=NONE or SNCP
Figure 228. AU3-NV path create step1
c) Select the end points.
Figure 229. End points selection

d) Enter the detailed parameters. Click on Finish.
Figure 230. Detailed parameters selection example
e) Allocate the path
Figure 231. Allocate the path

f) Routing view of the allocated path
Figure 232. Routing view of the allocated path

g) Click on Server Trail List icon. The relevant list is displayed.
h) You can navigate to the Physical Connection. Select the trail and issue Search: All related Items:
Server Physical Connection

Figure 234. Search: All related Items: Server Physical Connection
i) From browser select the physical connection and issue Search: All related Items: Physical Connec-
tion Structure
Figure 235. Search: All related Items: Physical Connection Structure

j) The Physical Connection Structure is shown below. Notice the virtually concatenated AU3 trails.
Figure 236. Physical Connection Structure
2.3.14 Digital Video Broadcasting path (not protected)

DESCRIPTION
This feature allows to transport a television broadcast signal. Before entering into the transport network,
the television broadcast signal is compressed by a MPEG-2 encoder. At the receiving ends a network
adapter extracts the required data stream from the network.
RM provides the feature by means of a broadcast path using a new rate (digital video broadcasting).
The television broadcast signal is carried by LO resources (VC12 or VC3), virtually concatenated, with
an STM-1 equivalent throughoutput (i.e 63 VC12 or 3VC3).
SCOPE
Given the network shown in the following figure, where nodes 1660 SM-1, 1660 SM-2, 1660 SM-C are
equipped with DVB boards, create a digital video broadcasting path (not protected).

Figure 237. DVB Reference Network
Port list (including DVB ports) of node 1660 SM-C and the related NAP list are shown in figures which
follow.
Figure 238. Port list

Figure 239. NAP list
SEQUENCE
a) To create the path, point the source node and issue the pop-up Create:Path. See the following figure.
Figure 240. Create: Path pop-up menu

b) In the path create box select: Service type = DATA, Service rate = Digital Video Broadcasting, Trans-
port rate = TU12-nV, (or TU-3-nV), Protection = none, no. of sinks. Enter userlabel and path type
= broadcast. Server trail routing=uniform routing(not modifiable by the user).Click on Next. See fig-
ure which follows
Figure 241. DVB Path create box (step 1)
c) In the Source End Point selection box, click on NAP selection list. The list is displayed on the right
hand side. Select the source NAP (attribute direction=source) and click on Next. See figure which
follows

Figure 242. Source node selection
d) In the sink point selection box click on NAP selection list and select the sink NAP (attribute direc-
tion=sink) from the list. Click on Next. See figure below.
Figure 243. Source NAP selection

e) Same as above point d). Click on Next. All required vsink pionts have been selected, then the Addi-
tional Information box is presented. See following figure
Figure 244. Additional Info box
f) After entering all suitable selections, click on Finish to complete the creation.
g) The routing display of the defined path is shown. See following figure.

Figure 245. DVB defined path routing display
h) Allocate the path. See below figure.
Figure 246. Path: allocate pop-up menu

The routing display changes to allocated. The path is a virtually concatenated and broadcast path
(LCAS not supported).
Figure 247. DVB allocated path routing display
i) Implement the path
Figure 248. Path: Implement pop-up menu

The routing display of the implemented path is shown below.
Figure 249. DVB implemented path routing display
j) The path highlight is sshown in the following figure
Figure 250. DVB path highlight

k) The server trail list, invoked by the relevant button, present in the routing display, is shown below
2.3.15 Digital Video Broadcasting path (route protected)

SCOPE
Create a digital video broadcasting path (route protected).
SEQUENCE
a) To create the path, point the source node and issue the pop-up Create:Path. See the following figure.

Figure 252. Create: Path pop-up menu
b) In the path create box select: Service type = DATA, Service rate = Digital Video Broadcasting, Trans-
port rate = TU12-nV, Protection = SNCP, no. of sinks. Enter userlabel and path type = broadcast.
Click on Next. See figure which follows
Figure 253. DVB Path route prot. create box (step 1)

c) In the Source End Point selection box, click on NAP selection list. The list is displayed on the right
hand side. Select the source NAP and click on Next. NAPs selectable as source are odd. See figure
which follows
Figure 254. Source node selection

d) In the sink point selection box click on NAP selection list and select the sink NAP from the list. Click
on Next. See figure below. NAPs selectable as sink are even.
Figure 255. Sink1 NAP selection

e) Same as above point d). Click on Next. All required vsink pionts have been selected, then the Addi-
tional Information box is presented. See following figure
Figure 256. Sink2 selection

f) The Additional Information box is presented
Figure 257. Additional Information box

g) After entering all suitable selections, click on Finish to complete the creation. The routing display of
the defined path is shown. See following figure.
Figure 258. Routing display

h) Allocate and implement the path. From the routing display issue Highlight
Figure 259. DVB path route prot. Highlight

i) The routing display is shown below. For each leg its spare route is provided.
Figure 260. DVB path route prot. routing display
2.3.16 DVB path route (SNCP) and source protected

N.B. In case of source affected by a malfunction, DVB-AIS is inserted, then the sink NAP(s) selects
the correct signal from the protection source. Figure which follows shows the involved attribute.

Figure 261. VC-AIS insertion attribute
SCOPE
Create a digital video broadcasting path (route protected).
SEQUENCE
a) To create the path, point the source node and issue the pop-up Create:Path. In the path create box
select: Service type = DATA, Service rate = Digital Video Broadcasting, Transport rate = TU12-nV,
Protection = SNCP, no. of sinks. Enter userlabel and path type = broadcast. Click on Next. See Fig-
ure 262. on page 268.

Figure 262. DVB Path route-source prot. create box (step 1)
b) In the Source End Point selection box, click on Add Backup button (left-hand bottom). The Primary
Source selection is enabled. Click on NAP list selection, select the source NAP from the list and click
on Next. See figure which follows

Figure 263. Selection of the Primary source
c) Click on Backup. Click on Node selection button. See figure below.
Figure 264. Backup source node selection

d) From the node list select the node housing the source backup NAP.
Figure 265. Source backup NAP node selection
e) Select the source backup NAP
Figure 266. Source backup NAP selection

f) Then, the selection of both source and backup NAPs gives the situation shown in the following fig-
ures
Figure 267. Source backup NAP selected
Figure 268. Primary source NAP selected

g) At this point the selection of the first sink
Figure 269. Selection of the first sink
h) then the selection of the second sink
Figure 270. Selection of the second sink

i) Click on Next. All required source and sink points have been selected, then the Additional Informa-
tion box is presented. After entering all suitable selections, click on Finish to complete the creation
j) From the routing display, allocate and implement the path. Roting display and highlight are shown
in below figures.
Figure 271. Routing display
Figure 272. Highlight

2.3.17 10 GBE EPL point to point path
DEFINITION
This feature allows to create a 10 Gb Ethernet path in the SDH network, by means of AU4 and AU3
resources. The two end points of the path support the 10Gb rate.
N.B. 10GbE EPL Ethernet paths can be ended to the ASON NPA
SCOPE
The scope is to create a 10 GBE EPL path
SEQUENCE
a) Figure which follows shows the nodes housing the boards P4 x GE
Figure 273. 10 GBE EPL node
b) Point to the source node and issue Create: Path

Figure 274. Create path pop-up menu
c) In the create path dialog box enter:
– Service Type=Ethernet
– Service rate=10 Gb Rate Adaptive
– Transport rate ( AU4-nV or AU3-nV)
– userlabel
– total concatenation level. Must be greater than the actual.

Figure 275. 10 GBE EPL path create-step1
d) Select the end points.

Figure 276. 10 GBE EPL path end-point selection
e) Enter the remaining Additional Infos and click on Finish.
Figure 277. 10 GBE EPL path: Additional Infos
f) The path is created. See Path list: EPL and compounds

Figure 278. Path list: EPL and compounds
g) The 10 GBE EPL path routing view is displayed.
Figure 279. 10 GBE EPL path routing view
h) Allocate the path.

Figure 280. EPL path: Allocate
i) Implement the path.
Figure 281. EPL path: Implement

j) The EPL path: Implementation log is shown below.
Figure 282. EPL path: Implementation log
k) The EPL path: trail activation log is shown in figure which follows
Figure 283. EPL path: trail activation log

l) Select the path routing view

Figure 284. EPL path: routing view selection
m) From the link connection, select the server trail list
Figure 285. EPL link conn: Server trail selection
n) The Server trail list is shown below: the operational state of each trail is Disabled

Figure 286. EPL link conn: Server trail list
o) The operational state of each trail is Enabled
Figure 287. EPL path: trail list and routing display
p) Trail end points on EML are shown in figures which follow.

Figure 288. Trail end points on EML (1)
Figure 289. Trail end points on EML (2)

2.3.18 10 GBE EVPL point to multipoint path
The feature allows supporting of the point-to-multipoint EVPL services (G.8011.2 type 1). This type of ser-
vice provisioning is made available by the 10GBE board of the 1678MCC 4.1 through the Q3 management
interface.
N.B. No LCAS and no ASON management (EVPL services cannot terminate on ASON boundary)
are available in this release
SCOPE
The scope is to create a 10 GBE EVPL path
SEQUENCE
a) Select the ports and issue Create: Path
Figure 290. Port selection

b) In the Create step1 box, enter userlabel=evpl, service type Ethernet, Service rate=EVPL Rate Adap-
tive, transport rate=AU4-nV

Figure 291. Create EVPL path step 1
c) Select the ports, if not yet selected, click on button EVPL, VLAN ID=2, vcnv=3, Priority
Figure 292. Create EVPL path step 2
d) Complete the path creation with the Additional Information. Click on Finish.

Figure 293. Create EVPL path:Additional Information
e) The path evpl is now present in the path list.
Figure 294. Path list including path evpl
f) You can issue the routing display of path evpl.
Figure 295. Routing display of path evpl

g) Create the second EVPL path. In the Create step1 box, enter userlabel=evpl_1, service type Ether-
net, rate=EVPL Rate Adaptive, transport rate=AU4-nV. Click on Next.
h) Select the ports. The source port is the same of the previous path, called evpl ; the sink port is dif-
ferent. Click on button EVPL, enter VLAN ID=102, vcnv=14, Priority. Notice that username, sink port,
VLAN ID and vcnv are different from the ones relevant to the first path.
Figure 296. Create second EVPL path
i) Complete the path creation as for path evpl. Figure which follows shows the Path list including evpl
and evpl_1

Figure 297. Path list including evpl and evpl_1
j) Allocate and implement the two paths.
k) For each path you can display the relevant trail list.
Figure 298. Trail list
l) For each trail you can issue the Trail routing display

Figure 299. Trail routing display

2.3.19 EVPL mixed 10GbE-1GbE path flow control management
SCOPE
The scope of this procedure is to enable/disable the EVPL mixed 10GbE-1GbE path flow control.
This control is enabled as default.
Figure 300. Path list including the mixed path
Figure 301. Mixed path routing display

Figure 302. Flow control disabled on NM
Figure 303. NAP display

Figure 305. NM:Transmission:Physical Media:Ethernet Port Configuration

Figure 306. RM: Flow control set to Enabled
Figure 307. RM:Report:Flow control set to Enabled

Figure 308. Flow control enabled on NM
2.3.20 LCAS hold off time management on 1678MCC-1GBE path

SEQUENCE
a) Create a 1GBE path
Figure 309. Path create 1 GbE step1
b) Select the termination ports

Figure 310. Path create 1 GbE step2
c) Select LCAS control=Enabled
Figure 311. Path create 1 GbE step3:LCAS control=Enabled
d) Click on Finish. Allocate and Implement the path

Figure 312. Allocate and Implement path report
Figure 313. Path list: the path is implemented
Figure 314. Show/Set attributes. LCAS control=enabled

Figure 315. NM: ISA port configuration:LCAS control=enabled
e) From the path list, point to the path and issue Ethernet: LCAS Hold Off Time
Figure 316. Path: Ethernet: LCAS Hold Off Time

Figure 317. Dictionary and LCAS set hold off time
Figure 318. LCAS setting Hold Off time report
f) Verify on NM: ISA port configuration

Figure 319. NM: ISA port configuration
Figure 320. NM: ISA port configuration:Hold Off time=400
2.3.21 Ethernet auto-negotiation on single port of a path

DESCRIPTION
The auto-negotiation is an Ethernet mechanism that allows the connected Ethernet ports to configure
themselves in an optimal way (in terms of transmission parameters).
It applies to each type of ethernet path: uni-directional, bi-directional and broadcast.
The involved ports in the auto-negotiation mechanism are the Ethernet port of the NE and the port of the
connected router. For this reason, the auto-negotiation parameter can be set in a different way on the NE
ports ending an Ethernet path.
SCOPE
The feature allow to set in an independent way the auto-negotiation parameter on the Ethernet ports end-
ing an Ethernet path.
SEQUENCE

a) Point to the involved NAP and issue autonegotiation=enable/disable
The auto-negotiation on the Ethernet ports is applicable to all the Ethernet paths, that is uni-directional,
bi-directional and broadcast.
2.3.22 Ethernet path consequent actions configuration for 1678MCC R4.3
Description
The feature allows to shutdown the laser not only in case of client failures detected at the GbE interface,
but also in case of SDH failures, in order to perform the protection switch in the client device.
The functionality is performed by means of the insertion of the CSF not only in case of client failures
detected at the GbE interface, but also for failures of the opposite direction, where the SDH is terminated.
To obtain this behaviour, RM has to automatically enable the bidirectional CSF insertion and the laser
shutdown capabilities.
Ì The functionality is supported by both 1GbE and 10GbE (no EVPL) of the 1678MCC, starting
from the R4.3.
Ì The feature is enabled/disabled by means of an environmental variable. For backward com-

patibility, the functionality is disabled by default.
SCENARIOS
The following scenarios are supported.
Scenario 1: client failure on bidirectional path
1) a Client Failure is detected by A-Eth interface. As a consequence:
1a) the laser shutdown is performed towards the router
1b) the CSF is inserted
2) the CSF is detected by Z-Eth interface. As a consequence:
Figure 321. Scenario 1: client failure on bidirectional path

Scenario 2: SDH failure on bidirectional path
1) a SDH Failure is detected by A-Eth interface. As a consequence:
1b) the CSF is inserted in the opposite direction
Figure 322. Scenario 2: SDH failure on bidirectional path
Scenario 3: client failure on unidirectional path

1) a Client Failure is detected by A-Eth interface. As a consequence:
1a) the CSF is inserted
Figure 323. Scenario 3: client failure on unidirectional path
Scenario 4: SDH failure on unidirectional path
1) a SDH Failure is detected by Z-Eth interface. As a consequence:

Figure 324. Scenario 4: SDH failure on unidirectional path
According to the above scenarios, the following has to be taken into account:
bidirectional path
RM enables both the bidirectional CSF insertion and the laser shutdown consequent actions on the NAP.
In particular, for NAPs belonging to an ES64 board:
bidirectional CSF insertion consequent action is enabled by default; anyway the NE accept the request.
Laser shutdown is not meaningful, as only internal ports are equipped
unidirectional path
on the sender side (NAP), RM disables both the bidirectional CSF insertion and the laser shutdown con-
sequent actions
on the receiver side (NAP), RM disables the bidirectional CSF insertion consequent action and enables
laser shutdown consequent action
The bidirectional CSF insertion consequent action is enabled by means of the Q3 consequentActionSup-
pression attribute of the genericDataTransportCTP object.
The lasershutdown consequent action is enabled by means of the Q3 lasetShutdown attribute of the
gMAUTTP object.
2.3.23 Management of ISA ES64

DESCRIPTION
The ISA ES64 board belongs to the ISA-ES family of boards mapping Ethernet flow onto the SDH network.
It supports 10GbE interfaces and only HO virtual concatenation and it is only available in 1678MCC.
The ES64 board allows to create the following kinds of 10Gb rate adaptive path:
-path between two different ES64 boards (on different nodes)
-path between a ES64 and an External Node
-path between a ES64 and a 10Gb port on the same node

The above Ethernet paths (10Gb rate adaptive) cross the SDH physcons (STM-64 type) previously cre-
ated between the relevant nodes
path1Eth
ES-64 ES-64
STM-64
physcon
1678-A 1678-C
Figure 325. Path between two different ES64 boards
STM-64
physcon
Ext
Netw-1
ES-64 53
10Gb-NAP path3Eth
56
1678-A
Figure 326. Path between a ES64 and an External Node

ES-64
path2Eth
10Gb-NAP
1678-C
Figure 327. Path between a ES64 and a 10Gb port on the same node
Upon uploading of the ES64 board, 128 termination points (NAP) are uploaded. For each NAP a fictitious
port is created. In the example shown in below figure, via RM the user can create and implement paths
1, 2 and 3, i.e. RM only controls the SDH matrices (not drawn in this figure), which perform the SDH con-
nections. See para 10Gb Ethernet EPL for details.
path1Eth
Ext STM-64
physcon ES-64
Netw-1 53 ES-64
path3Eth
56
10Gb-NAP
STM-64 path2Eth
physcon
10Gb-NAP
1678-A 1678-C
Figure 328. Paths created via RM
The connections within the ES64 board are managed by the BM, which controls the entire Ethernet ser-
vice.
The user may access the ES64 board to check the connections, and, when requested, to create the con-
nections.
2.3.23.1 Create connection within ES-64
TASK

1) From the Show Equipment view of the 1678, select the ES64 board and issue Configura-
tion>1ES64ZIC. The available ports are 1 to 64 and 129 to192 (total of 128)
2) In our example we want to connect port 53 to port 56. Select port 53. Set Admin state=up. The
Operational state is Down, due to signal absence. The Rate Limited speed is the maximum
value admitted in Kb. (E.g. 10000=10Mb, 10000000=10Gb). The default value is 0 (no limita-
tion). Click on Save.
3) Select Inflow. Select Create. Enter userlabel and select the desired Traffic Descriptor, among
the available ones, previously created. Click on Save + Exit. At this point, according to the fol-
lowing scheme, Inflow 53 has been created
IN 53 XCON1 OUT 56
OUT 53 XCON2 IN 56
Figure 329. Cross-connection scheme
4) Select Outflow (for port 53). Enter userlabel. Save + Exit.
5) Execute above steps 2), 3) and 4) for port 56
6) Create cross-connection1 (XCON1).
Select Data: Crossconnection. Click on Create. A dialog box allows to specify From and To.
Click on From button. Select port 53. Select Inflow.
Click on To button. Select port 56. Select Outflow.
7) Create cross-connection2 (XCON2). The procedure is as described at above step.
2.3.23.2 Create paths Eth 1,2 and 3 for ES64
SEQUENCEpath between two different ES64 boards (on different nodes)
-path between a ES64 and an External Node
-path between a ES64 and a 10Gb port on the same node
a) Create path between two different ES64 boards (on 1678A and 1678C in this example). See fol-
lowing figures

Figure 330. Create path betw ES64 boards step1
Figure 331. Create path betw ES64 boards step2
b) Create path between a ES64 and a 10Gb port on the same node 1678C

Figure 332. Create path ES64 to 10Gb port same node step1
Figure 333. Create path ES64 to 10Gb port same node step2
c) Create path between ES64 of node 1678A and an External Node

2.3.24 Path Allocate, implicit payload
2.3.24.1 Path Allocate
This paragraph describes the commands used to modify path configuration state and to display the path.
The Path state is "defined" after having been created. In this state only path terminations (NAP=Network
access point) are reserved.
For a defined path the user can make a reservation of the network resources required for the route. This
operation is called allocation.
a) Open the Path list: from the Browser point to the Network icon and issue the Search: Related items
pop up command. From the list of the available items select Paths and click on OK button.
b) From the list select the path to allocate and select the Actions: Configuration: Configuration State
Modification: Allocate pull-down menu. This command is also available as a pop-up menu item.
A warning alerts: "Action correctly started..." .
The Path working state changes from allocating to normal at the end of the allocation.
The Path configuration state changes from defined to allocated at the end of the allocation.
N.B. The Path Allocation can be executed only if the network is properly configured.
N.B. The allocation of a certain path can be prioritized with respect to the allocation already
requested for other paths if you enter Configuration: Configuration State Modification: Allocate
with Priority
2.3.25 Lock of BM path

Two new attributes have been added:
– MinimumRequired Concatenation Level. It is specifies the minimum band required by the external
manager and that the RM operator should not modify. It corresponds to BM parameter CIR (see BM
Traffic Descriptor). E.g., for CIR=3000 (3Mb), if RM will carry this traffic on TU12-nV channels, at
least n=2 channels are required.
– Check Required Concatenation Level.(False/True). It specifies the lock. For active lock (True
value), RM operator cannot de-implement, remove or reduce band. Default value is False, then to
lock the path, RM operator must set the Check Required Concatenation Level to True.
Notice that RM administrator can change the default in the RM configuration files. See Administration
Guide for details.
If the lock is disabled the RM operator can do operation affecting traffic. In this case the system provides
a warning:
The command could cause a misalignment with external manager
Show/Set attribute manages these attributes. The attributes are meaningful only for Ethernet paths and
are visible/settable in folder Ethernet. See following figure.

Figure 334. BM lock attributes
2.3.25.1 Implicit payload
SCOPE
The allocation of a path is done with automatic payload configuration. The real payload change in the NE
occurs at path implementation time.
The dynamic payload can be enabled/disabled by means of the env parameter.
Figure 335. Reference network
CONDITIONS

An AU4-4C concatenated path must be created and allocated between NODE A and NODE D. All involved
physical connections (A to B, B to C, C to D) are not structured.
Figure 336. Payload not structured on the physcon
SEQUENCE
a) Point to NODE A and issue Create: Path.
Figure 337. Create path

Figure 338. AU4 4-C create path step1
b) Enter name, rate,...
Figure 339. AU4 4-C create path step 2
c) You can select the NAPs, in case of real node or enter the NAP name for Virtual node.

Figure 340. AU4 4-C create path step3
d) Check AU4 4-C create path step3.
Figure 341. AU4 4-C create path path report

e) This is the path report. The path routing is displayed.

Figure 342. AU4-4C path:configuration: Modify: Allocate
f) Issue path:configuration: Modify: Allocate. Path allocation in progress (see below figure)
Figure 343. AU4-4C path allocation in progress

g) AU4-4C path allocation in progress

Figure 344. AU4-4C path allocation in progress: refresh routing view
h) path allocation in progress: refresh routing view
Figure 345. AU4-4C path allocation report

Figure 346. AU4-4C allocated path routing display
i) The AU4-4C allocated path routing display shows the route: in the Link conn show you can check
that the path rate is =AU4-4C

Figure 347. Link conn show: path rate=AU4-4C
j) But the physical connection structure view is not yet updated. See below figure.
Figure 348. Physcon structure: it is not updated
k) Issue path:configuration: Modify: Implement

Figure 349. AU4-4C path:configuration: Modify: Implement
l) Trail configuration in progress. See below figure

Figure 350. Trail configuration in progress
m) The trail is configured on path implementation
Figure 351. The trail is configured on path implementation

2.3.26 Saturation and fragmentation profiles
RM creates automatically a set of system profiles, one for each class of objects involved.
The profile type of the system profiles is marked as AUTOmatic.
The profile type of the profiles created by the operator is marked as USER.
The system profiles (Automatic) cannot be deleted/modified by the operator.
The user profiles (USER) are managed by the operator and associated to the resources.
In this release the profiles can be associated only to the physical connections
SEQUENCE
a) From the horizontal palette of the browser, click on Topology Tools.
Select button Profiles. The following menu appears:
Saturation Profile Creation
Saturation Profile List
Fragmentation Profile Creation
Fragmentation Profile List
2.3.26.1 Saturation Profile Creation
N.B. For detailed information about the meaning and operation of the parameters, please refer to
chapter Technical Annexes, paragraph Allocation
With reference to the below figure, the following fields can be changed:
• user label
• medium threshold
• high threshold
• low usage extra cost
• medium usage extra cost
• high usage extra cost
Click on Create button to confirm creation.
2.3.26.2 Saturation Profile List
The Saturation Profile List can be obtained from menu item Saturation Profile List.
The following fields are displayed:
• profile type (auto/user)
• medium threshold

• high threshold
• low usage extra cost
• medium usage extra cost
• high usage extra cost
2.3.26.3 Fragmentation Profile Creation
The creation of the fragmentation profile can be launched by means of the command Fragmentation Pro-
file Create.
Following fields must be entered:
• AU4-64C Extra Cost
• AU4 Extra Cost
• TU3 Extra Cost
2.3.27 Allocation algorithm: defragmentation
The allocation algorithm includes the defragmentation feature. The defragmentation allows to rationally
organize the time slot occupation and optimize the allocation of higher order paths.
The detailed description of the algorithm can be found in Chapter TECHNICAL ANNEXES, paragraph
ALLOCATION and Defragmentation
CONDITIONS
The reference network is shown below.

An AU4-4C concatenated path is present between NODE A and NODE D. All involved physical connec-
tions (A to B, B to C, C to D) are structured as in figure which follows.
SCOPE
A 2 Mbit path, from NODE A to NODE D, called 'civetta', will be allocated, with constraints, to TRAIL 2.
A subsequent 2 Mbit path, from NODE A to NODE D, due to the defragmentation algorithm, should
be allocated (without constraints) to TRAIL 2, thus optimizing the allocation of higher order paths.
Figure 352. Actual payload structure
SEQUENCE
a) Create path 'civetta' from NODE A to NODE D, setting the constraints of TRAIL 2 (see figure here-
below).

Figure 353. Creation of path 'civetta' with constraint to trail 2
b) Allocate path 'civetta'. Issuing the detail of trail 2 it is possible to verify that path 'civetta' has been
correctly allocated. See figure below.

Figure 354. Path civetta position in trail 2
c) Create a new 2 Mbit path from NODE A to NODE D. See Figure 355.and Figure 356.
Figure 355. New path create step 1

Figure 356. New path create step 2
d) Allocate the new path. Issuing the detail of trail 2 it is possible to verify that the new path has been
correctly allocated to trail 2, due to defragmentation algorithm. See figure below.
Figure 357. New path allocated to trail 2, due to defragmentation algorithm

2.3.28 Path Implement
a) From the Path List select the path and the Actions --> Configuration --> Configuration State Modi-
fication --> Implement pull-down menu item. This command is also available as pop-up menu.
The Path Implement activity consists in sending commands to the NEs in order to set up the NE internal
connections.
The Path working state changes from implementing to normal at the end of the implementation.
The Path configuration state changes from allocated to implemented at the end of the implementation.
2.3.28.1 Path Commissioning
a) From the Path List select the path and the Actions: Configuration: Configuration State Modifica-
tion:Commission pull-down menu item.
When the path is in this state no other operations are possible except for path de-commissioning and per-
formance monitoring and TCAs enabling/disabling. (Threshold crossing).
2.3.28.2 Displaying the path route
It is possible to display the path route for allocated, implemented and commissioned paths from browser
or path inventory applications and from SDH netview.
2.3.28.3 Path route from Path List
From the Routing Display window you can display the Route Report by selecting View : Report: Route
full....
Figure 358. Route report example

2.3.28.4 Path Routing view
This view displays the complete path route including the main resources dedicated to the selected path.
From the Path Routing view you can display the route report of the path by entering the command View:
Report: Route full. An example of report is shown in Figure 358.
The Path Routing view wholly represents the connectivity objects belonging to a defined path.
The view is subdivided into vertical columns (named Main, Spare, Service), each of which represents a
whole route.
Some cases can be distinguished:
– in case of an unprotected path the Main route is only available;

– if the path is of the SNCP protected type, the Main route and the Spare one are available;
– if the path is of the D&C SNCP protected type, all the route graphical representations are present:
• Main
• Spare (more than one spare route can be present)
• different service routes
The number of service and spare connections depends on how the path has been constructed.
Moreover if the path is broadcast, the different legs are separately represented.
The main and spare routes are represented for each leg if the path is of the broadcast and protected type.
2.3.28.5 Main Route
The Main route graphical representation comprises (in the area relevant to the first column):
– on the upper left-hand side the connection in topology icon at network level
From the first row on are listed the connections in topology at subnetwork level and eventually the
first connection in topology at level of Elementary Topology (ET).
Note that for each connection in topology, a continuous vertical line permits to identify the end points.
If one connection in topology is inside one route only, the vertical line directly connects the TPs (TTPs
or CTPs) involved.
On the right-hand side of the different connections in topology the first end point (NAP) is depicted, hence
in the column are displayed the CTPs and the link connections connecting the CTPs belonging to different
nodes.
The link connection icon contains the label describing the relevant payload position.
The representation of the "Switch" connections in topology (either Switch or Bridge & Switch) contains an
icon (Resource Type) indicating the actual switch status. It can be:
• M Main The switch is set at "Main"

• S Spare The switch is set at "Spare"
• C It is used only for a D&C type switch, i.e. for the service type connections. It indi-
cates that the switch is set at "Service".
The connection in topology of the Switch, B&S, or Service type may also contain the Operation Mode infor-
mation (bidirectional arrow) which can be Revertive or not Revertive.
N.B. The Path Routing View permits to display the actual route of the path. For this purpose the
switch Resource Type indications should be analyzed. In the following Figure 359.are given two
examples:

MAIN
M M M M
M M
MAIN
SPARE
SPARE
Figure 359. Actual route
Figure 360. Path Routing example
Clicking on the group icon 'Routing display' located on the view next to the link connection, it is possible
to display the objects relevant to the Link Connection at higher order.
Clicking on 'Nap view' button inside the icon bar it is possible to open the view to display all path's ter-
minations.

N.B. For a path crossing a NPE Ring the path routing view displays the Main route: the link con-
nection label contain a “ R “ or a “ U “ to identify if the path is a High Priority (HP=Reliable) or
a Low Priority (LP=Unreliable). HP paths make use of the Working capacity; LP paths make use
of the Protection capacity.
For a path crossing a NPE Ring, the user can verify the connections on the traffic map.
2.3.28.6 Path route on the map
The scope of this procedure is to display the path/trail route in the Netview maps. The Highlite/Locate but-
ton is present in the Path list/ Trail list and in other drawing windows containing the object to show(Naps
view, Routing view, Paths in Trail, Physical connection...etc). The sequence listed herebelow refers to the
locate of a path from the path list.
Notice that the view is not automatically refreshed after a modification of the protection (Add/Remove pro-
tection); in this case the sequence of operations must be executed again.
SEQUENCE
a) From the path list select the path to display and click on Highlight/Locate button.
Figure 361. Highlight button.
1) If the transport is not protected the following are displayed: (see icons in the figure below)

main-nap main-nap-service main-spare-service-nap
main-spare-nap
Object Flag Parent Flag
Figure 362. Symbols used by Hyghlight feature
Figure 363. Path Locate button

Figure 364. Example of Path locate on subnetwork map
Figure 365. Example of protected Path locate

Figure 366. Locate path: protected on the same link group
N.B. Sometimes happens that asking for Path Status in Physical Connection the status of the path
is 'indeterminate' even if the traffic is stable in the physical connection.
A path is "indeterminated" when it is not possible to synchronize switches on the NEs. The reason of the
failure of the synchronization could be:
• an operation is already in progress on the PATH/TRAIL. TRS agent inhibited the operation
• NE_G/NE is unreachable
• NE fault
The first case is a typical situation when different users execute at the same time the same operation. The
same situation is also reached if the same user asks many times the same operation.
2.3.29 Service state modification

DEFINITION
This feature allows to declare the Service State (IN-SERVICE or NOT_IN_SERVICE) for a transport entity.
The transport entities involved are:
– physical connections (automatically propagated to the related HO/MS trail
– client/path
The IN-SERVICE declaration is entered by the user for:
– implemented physical connections
– implemented or partially implemented OCH/HO Trail
– client/path (implemented / partially implemented / commissioned)
The NOT- IN-SERVICE declaration is issued by:
– user for physical connections / OCH/HO Trail / client/path
– system for physical connections / OCH/HO Trail / client/path at deimplementation

Alarms on IN-SERVICE or on NOT- IN-SERVICE entities are automatically acknowledged by AS. Sep-
arate counters are provided, namely:
– alarms on both IN-SERVICE or on NOT- IN-SERVICE entities
– alarms on IN-SERVICE entities
EXAMPLE OF SERVICE STATE MODIFICATION
SEQUENCE
b) Point to the physical connection to modify and issue the pop-up menu item Configuration: Service
State Modification
c) A dictionary is displayed, allowing to select between IN-SERVICE and NOT-IN-SERVICE. Select the
desired service state and click on OK button.
Figure 367. Service State Modification box and dictionary
d) It is possible to supervise the successful Service State Modification on the AS Counter Summary.
2.3.30 Constraint management

The old constrainType parameter, for ease of clarity is now represented by two parameters: section & con-
straintType
The parameter section allows to assign a constraint directly to a specific branch (main, spare, service)
of the path/trail
The old constrainType parameter was an enumerated composed by many values (about 20). This con-
dition is not suitable for the operator that is obliged to choice a value among 20 different options. The idea
is to split this long list into two short lists
The backward compatibility is kept allowing the old constraint batch command batch utility and the exter-
nal managers to use the old constrainType (see Basic routing constraint management with dynamic pay-
load (Backward compatibility) feature) by the old action -definePathConstr.
Using as constraint also the potential resources LCs and CTPs (and, of course, the real ones)
The new path/trail constraint management allows to use as constraint the potential resources; i.e. poten-
tial LCs and CTPs (and, of course, the real ones).
2.3.30.1 Constraint parameters
The input parameters are:
• objConstraint: it identifies the object used as constraint

• constraintType: it identifies the type of constraint
• payloadpos: (OPTIONAL) it is a string identifying the payload position
• section: (OPTIONAL) it identifies the constraint branch
The old action definePathConstr is still working and allows the backward compatibility.
New constraintType management
In order to make easier the choice that the user has to do, the old constrainType field is split in two fields:
constraintType (the new one) & section. In details:
constraintType. allowed values:

• use
• useAsSource
• useAsSink
• dontUse
• overlap
• disjoined
• extOverlap
section. allowed values:
• main
• spare
• service
• service A-Z
• service Z-A
• common
The mapping between the old constrainType and the new parameters (Section, New constraintType) is:
Old constraintType Section New constraintType
UseMain main use
useSpare spare use
notUseMain main dontUse
notUseSpare spare dontUse
notUse common dontUse
useService service use
notUseService service dontUse
overlapped common overlap
disjoined common disjoint
overlappedRL common extOverlap
useMainA main useAsSink

useMainZ main useAsSource
useSpareA spare useAsSink
useSpareZ spare useAsSource
useServiceAZ serviceAZ use
useServiceZA serviceZA use
main use
useMainSpare
spare use
main useAsSink
useMainSpare
spare useAsSink
main useAsSource
useMainSpareZ
xpare useAsSource
N.B. Each one of the last three old constrainType values is mapped by two values of the couple (sec-
tion, new constraintType)
Explanation of some value of the new constraintType attribute
The following mapping may appear strange:
Old constraint Type Section New constraintType
useMainA main useAsSink
useMainZ main useAsSource
useSpareA spare useAsSink
useSpareZ spare useAsSource
The old useMainA is mapped with the new useAsSink. This mapping is due to the fact that the old con-
straintType is referred to the cross connection within network element, while the new constraint type is
referred externally to the network element.
The following figures clarifies the mentioned mapping.

Figure 368. Mapping between old constraint type and new constraint type
Using as constraint also the potential resources
The introduction of the new feature implicit payload configuration (the dynamic payload) allows the user
to allocate a path (at a specified rate) without configuring the needed link connections (then also the CTPs)
at the same rate of the path transport rate.
The new path/trail constraints management allows to use as constraint also the potential LCs and CTPs
(and, of course, the real ones).
Because of these reasons CTP and a LC correspond to:
LC = Trail + PayloadPosition;
CTP = Port + PayloadPosition.
Then, the list of objects that can be used as constraint is:
– Path
– Trail (+ payloadPosition [optional])
– PhysConn
– Node
– NPA
– Port (+ payloadPosition [mandatory])
– potential CTP (i.e. Port + PayloadPosition)
– potential LC (i.e. Trail + PayloadPosition)
By means of the wizard it is possible:
– Drag&drop; for the following objects there are some restrictions:
– Port: the operator has to specify also the payload position;

– CTP: the CTP is automatically managed as Port+PayloadPosition
– LC: the LC is automatically managed as Trail+PayloadPosition
Copy&Paste; also in this case the previous restrictions are valid.
Use as constraint function; this new function is available over the list of class tag that can be used as con-
straint. The object is automatically added to the constraints list on the wizard already open. Also in this
case the previous restrictions are valid.
The RM browser allows to keep open only one instance of constraints wizard; i.e. it is not possible to define
in parallel way the constraints of two different paths/trails.
2.3.30.2 Previous Constraint parameters
CONDITIONS
The use of the constraint/s allows the operator to execute:
– fully manual allocation. The path route can be fully specified, including the payload position. Namely
the user can specify the lower order link connection as constraint.
– partially automatic allocation. The user specifies only a part of the route. The allocation algorithm
completes the research of the route resources.
WARNING
The constraint is accepted as mandatory condition by the allocation algorithm, so the path/trail allocation
will fail if a constraint cannot be satisfied. If a path/trail allocation fails, the user is fully informed by the Path
Fail to Allocate tool. See Section Maintenance of this Handbook.
OPERATION
The Path Constraints can be always issued but they will be taken into account during the path allocation
phase: so if the path is implemented, the operator must deimplement and deallocate it and subsequently
issue a new allocation.
Trail Constraints can be always issued but they will be taken into account during the trail setup phase: so
if the trail is set, the operator must deimplement and deallocate it and subsequently issue a new allocation.
Previous Parameters
– Use Main
– Use Spare
– Not use Main
– Not use Spare
– Use Main and Spare
– Not use
– Use Service (for a D&C protected path)
– Not use Service (for a D&C protected path)
– Overlapped if the object utilized as a constraint is a path
– Disjointed if the object utilized as a constraint is a path
– Use Main as A. This constraint can be applied only to a CTP, used as constraint to a unidirectional
or broadcast path. See Figure 369.

NAP
source
CTP CTP CTP CTP CTP
A Z A Z A Z
Figure 369. CTP as constraint.
– Use Main as Z. This constraint can be applied only to a CTP, used as constraint to a unidirectional
or broadcast path. See Figure 369.
– Use Main and Spare as A, if the main and spare route are using the same CTP as A termination.
– Use Service Forwards
– Use Service Backwards
The values Use Service Forwards and Use Service Backwards are significant for paths crossing a
Dual Node SNCP network.
The user drops as constraint one of the Physical connections between the two D& C nodes, or a link
connection, or a CTP, then must select between Use Service Forwards and Use Service Backwards.
If the user selects Use Service Forwards, the object dropped as constraint will be used as service
route/termination to protect the forward transmission direction (from A to Z or from the left to the right
or the TX). See Figure 370.herebelow.
If the user selects Use Service Backwards, the object dropped as constraint will be used as service
route/termination to protect the backward transmission direction (from Z to A or from the right to the
left or the RX). See Figure 370.herebelow.

FORWARD
BACKWARD
THIS PHYSCON IS USED THIS PHYSCON IS USED

AS CONSTRAINT: AS CONSTRAINT:
USE SERVICE FORWARD USE SERVICE BACKWARD
Figure 370. Use Service Forward/Backward for Dual Node SNCP network

2.3.31 Add Constraints procedure
SEQUENCE
a) From Routing display click on button Add Constraints. See following figure
Figure 371. Add Constraints button

b) The Add Constraints start dialog box is presented. Click on Next.
Figure 372. Add Constraints start dialog box (step 1)
c) The Select Path/Trail box allows to drag and drop the object to constrain, if not yet selected. This
box allows to manage many sets of constraints, each of them can be active at a time. In absence
of previously entered constraints, the active set is said initial. The routing constraints selection
table is shown in the lower part of the window.
Figure 373. Add Constraints step 2 dialog box

– The constraint section is the constraint typology
• main
• spare
• service
• service A-Z
• service Z-A
• common
– the constraint type (it is the modality of application)
• use
• don't use
• overlap
• .......
N.B. The meaning of the above parameters, with reference to the previous parameters classification,
is detailed at previous paragraph .
d) Drag and drop (i.g. from the map) the object to be used as constraint and select type and section
Figure 374. Routing Constraints section

Figure 375. Routing Constraints type
e) Figure which follows shows a constraint already selected. To create a new set of constraints click
on Add Set button.
Figure 376. Add Set button

f) Enter the new constraint set name in the box textstring and click on OK.
Figure 377. Enter the new constraint name
g) Clicking twice on the cell relevant to position, a entry box opens, allowing to specify time slot position
Figure 378. Time slot position entry

Figure 379. Constraint set list
h) Click on Finish. The action to create and to render active the constraint set is executed.
Figure 380. The constraint set is executed

2.3.32 Potential time slot
It is possible to specify as constraint a time slot not yet structured.
Figure 381. Trail structure (2nd LC at TU3)
Figure 382. AU4 structure (TU3)

SCOPE
The trail structure is configured with the 2nd LC at TU3 and we want to use it for a 2Mb path.
SEQUENCE
i) From the Constraints wizard, set as constraint the trail

Figure 383. Path 2Mb: constraint trail wrongly structured
j) Select the position, choosing a 2 Mb time slot, which is contained is a link connection structured at
TU3.
Figure 384. Setting the position
k) Allocate the 2 Mb path.

Figure 385. AU4 structure (TU3)after 2Mb path allocation
l) Implement the 2 Mb path. Only after the implementation, the structure of the involved LC appears
complete.
Figure 386. AU4 structure (TU3)after 2Mb path implementation

2.3.33 Copy and Paste of Constraints set
Copy and Paste of Constraints set can be executed for whichever state of the path involved.
You can Paste the Constraints set to a single or to many paths.
Figure 387. Path: Constraints menu
The Path: Constraints menu contains the submenu: Show/Set, Copy Constraints and Paste Constraints.
An example of Paste Constraints to many paths is shown in the following figure.

Figure 388. Paste Constraints to many paths
2.3.34 Adding /Removing a leg to a path

a) From the Path List or from browser select the path (monodirectional/broadcast)
b) Enter the command Add: Leg either by selecting the relevant tool button or by using the menu
Modification: Add Leg. See Figure 389.The Add Leg dialog box opens. The path icon is contained
in the path drop area. See Figure 390.
c) Select the node from the browser/node list or the NAP from the nap list and enter the command Add:
Leg either by selecting the relevant tool button or by using the menu Modification: Add Leg. The
selected node now appears in the Leg drop area of the Add Leg dialog box. Alternatively you can
drag the node from browser to the Add Leg window, as per Figure 391.
d) Click on button Add Leg. See Figure 392.The leg is allocated and implemented.
e) Figure 393.shows an example of routing display of a broadcast path.
Removing a leg
Select the sink NAP to remove and issue the action Broadcast Path Modify: Remove Leg. It is possible
to release the NAP or to keep it associated to the path.

Figure 389. Add Leg menu item.
Figure 390. Add Leg dialog box.

Figure 391. Drag from browser
Figure 392. Add Leg button.

Figure 393. Routing display of a broadcast path.
2.3.35 Path in NPE ring

The attributes relevant to NPE features are:
– Server MS protection usage profile: it represents the profile of the MS resources to be used in allo-
cating the path.
The possible values are:
• Normal (default)
– For 1664SM rings, the RIP mechanism is used, i.e. when crossing 4 Fibers MS-Spring,
the path uses only working (high priority) resources, except for primary and secondary
nodes of the double interconnection with another ring, because these nodes are charac-
terized by the Drop & Continue protection (RIP)
as a result, in the segment between service nodes:
• if the path is bidirectional, the used resource (nodes E, D, H, I) can be only the pro-
tection one: a bidirectional D&C IC on protection is performed in the primary nodes
(D, H);
• if a path is unidirectional point-to-point, the used resource is:
• protection if the signal flows into the service nodes (B, C): a unidirectional D&C IC
on protection is performed in the primary node (B);
• working if the signal flows out of the service nodes (E, D): a multipoint connection
is performed in the primary node (E); this allows the user to perform subsequent add
leg operation;

it is possible to use the protection resource instead of the working (nodes E, D), e.g.
forced by a constraint;
• if a path is broadcast, the used resource is:
• protection if the signal flows into the service nodes (B, C) like in a unidirectional
point-to-point path: a unidirectional D&C IC on protection is performed in the primary
node;
is performed in the primary node);
it is not possible to use the protection resource instead of the working one.
As a result of the previous rules defined for unidirectional and broadcast paths, a uni-
directional point-to-point path can become broadcast only if the working resources
are used between service nodes (nodes E, D).
– For 1670SM rings the path uses only working resources (RIW)
• Protection preferred
When crossing a 4 Fibre MS-Spring, the path uses protecting (low priority) resources.
If the routing algorithm must use the working resource in one span of the 4F MS-spring (e.g.
no free resources in the protection, or a constraint is applied), all working resources are used
in the ring, in order to avoid jumps between working and protection resources (jumps not fore-
seen for the management of ring traffic map).
If the path is protected and main and spare routes are crossing the same MS-Spring, each route
crosses separately the ring itself since D&C connection are not available for protecting
resources.
As a consequence of this behavior and of the fact that the SNCP connection is not available
on a 4f MS-Spring, if the protected HO path is completely inside a 4f MS-Spring, the allocation
will always fail.
• Protection only
the path uses only protecting (low priority) resources.
N.B. The procedure used to create a path crossing a NPE Ring is the same as described in the pre-
vious paragraphs.

2.3.35.1 Examples of path crossing mixed rings
SNCP
A B C R
NPE
F E D
SNCP
SNCP
A B C
NPE
R F E D
Equipment=1664SM
SNCP
Figure 394. Bidir. Path, 1664SM, RIP

T
SNCP
A B C
NPE
F E D
R
SNCP SNCP
R
A B C
NPE
F E D
Equipment=1670SM
SNCP
Figure 395. Bidir path, 1670SM, RIW.

2.3.36 Drop and Continue path
The main topics described in this paragraph are:
4-Node Drop and Continue
D & C path in a 2-Node SNCP network
Path Constraints in a 2-Node SNCP network
D & C path in a 1-Node Enhanced SNCP network
2.3.36.1 4-Node Drop and Continue
(see Figure 396.on page 357, Figure 397.on page 358, Figure 398.on page 359, Figure 399.on page 359.)
Drop and Continue is a way of protecting a path crossing a number of sub-networks, e.g., rings.
The sub-networks should be connected through at least two nodes (so realizing two independent con-
nections).
The equipment is configured as "DROP and CONTINUE" on each interconnection node.
The subnetworks' equipment implement the SNCP/I 1+1 connection.
The resulting architecture affords protection against multiple failures (evenly distributed one per subnet-
work) tolerated without traffic loss (node failure or single cable cut).
The traffic entities interconnected by the drop and continue feature can be TU12, TU3 and AU-4.
The Drop and Continue feature improves traffic availability as compared with the simple "end-to-end
SNCP/I". More subnetworks are connected the further is availability increased.
The Drop and Continue features simultaneously realizes the following on one node:
• unidirectional pass-through
• protected drop
• insertion in the opposite direction with respect to the passthrough direction.
The configurations achievable are:
• D/C-W INS-W
• D/C-E INS-W
• D/C-E INS-E
• D/C-W INS-E
D/C stands for "Drop and Continue", the letter after it (W=West, E=East) indicates the "drop protected"
side (e.g., W means West main side, and spare side is the EAST one).
The end letter (INS-E or INS-W) indicates the insert side.
The "Unidirectional pass-through" is always in the direction opposite to that of the "insert" side (e.g., when
"INS E" the pass-through is from East to West).

For further information refer to Figure 396.on page 357 which shows the D/C-W INS-W configuration.
WEST AGGREGATES EAST

Rx Tx
Tx Rx
TRIBUTARY
Tx Rx
Figure 396. Drop and Continue D/C W INS W
The "Drop and Continue" featuring two connected rings (with dual connection) is indicated in Figure
397.on page 358.
Nodes 3, 4, 6 and 10 are configured as Drop and Continue.
SNCP/I protection is enabled throughout the equipment. When in normal condition, the unidirectional way
of traffic from 1 to 8 is supposed to be:1, 2, 3, 6, 7, 8.
After a failure on the 1st ring between nodes 2 and 3 (see Figure 398. on page359), the link direction is:
1 , 5 , 4 , 3 , 6 , 7, 8.
Pass-through is used between nodes 4 and 3, and switch on node 3.
After a second failure on the 2nd ring between nodes 6 and 7 (see Figure 399. on page 359) the selected
direction on the link is : 1 , 5 , 4 , 10 , 9 , 8.
The operative switch is on node 8 and the previous pass through between nodes 4 and 3 is no more used.

1
2 5
3 4
D/CW INSW D/CE INSE
W E W E
INS
INS E
W
TRIB TRIB
W E W E
INS
W INS
E
D/CW INSW D/CE INSE

6 10
7 9
Figure 397. Drop and Continue

1
2 5
3 4
6 10
7 9
Figure 398. Drop and Continue - 1st failure
2 5
3 4
6 10
7 9
Figure 399. Drop and Continue - 2nd failure

2.3.36.2 Path create in D & C network with ADMs (4-node D & C network)
a) With reference to a network like the one shown in Figure 397.select the end nodes and issue Actions:
Create Path.
b) In the path create wizard select protection = D & C SNCP. Execute the complete sequence of path
create, as required by the wizard. Finally click on Finish button.
c) The path is created and the NAP view is displayed.
d) Allocate the path
e) Clicking on Routing view button it is possible to display main, spare and service routes.
2.3.36.3 D & C path in a 2-Node SNCP network
Figure 400. Submaps of 2nd level subnetworks (ET-1 , ET-2, ET-3) for 2 ND&C

2-N D&C
ET-3
ET-1
tp
tp
tpAZ tpZA
tpAZ tpZA
tp tp
SIDE A ET-2 SIDE B
Figure 401. Example Network.
The path create procedure described at para 2.3.36.4 herebelow refers to the example network of Figure
400.and Figure 401.
2.3.36.4 D & C path create in a 2-Node SNCP network
The Path Create procedure is the same as described in the previous paragraphs, with the following excep-
tions:
– Rate=140 Mb,
– Protection type=D & C SNCP.
2.3.36.5 D & C path allocate in a 2-Node SNCP network
Upon path allocation, the system evaluates, as in case of basic D & C (see Figure 402.)
– main route
– spare route
– two service routes

Figure 402. Routing view for 2-N D & C path.
The graphical appearance of this figure has been changed while contents maintain their validity
If you click on the icon of the Switch status, the system opens a subwindow which displays the switch sta-
tus. Figure 403.shows the subwindows relevant to the routing display view of Figure 402.

Figure 403. Status switch subwindows for 2-N D & C.
Figure 404. Main route connection view detail

N.B. The drawing of the switch shows the main switch position (line) and spare switch position
(dashed line). The actual switch position is marked by a M (switch turned on main) or S (switch
turned on spare). See above Figure 404.
BOARD
CTP NAME DETAIL NODE NAME
SUBRACK PORT
RACK Channel (N.A.)
PAYLOAD POSITION
Figure 405. CTP name detail.
N.B. The CTP name (see above figure) contains the port name; then from the CTP issue Display:
Related items: Ports. From the Port issue Display: Related items: Physical Connection.
For the subwindow of Figure 403. the connections are:
– tp A: comprises a switch for the connections coming from tp Z and tp ZA, one point to point from tp
A to tp Z, one point to point from tp A to tp AZ
– tp Z: comprises a switch for the connections coming from tp A and tp AZ, one point to point from tp
Z to tp A, one point to point from tp Z to tp ZA
– tp ZA: comprises one point to point from tp ZA to tp A, one point to point from tp Z to tp ZA
– tp AZ: comprises one point to point from tp AZ to tp Z, one point to point from tp A to tp AZ
The default switch type is NOT revertive.
N.B. As in the case of the normal D&C, it is not possible from the User Interface to select the TPs
involved in the D&C but they are automatically selected by the algorithm. The TPs can be
selected from the command mode because this is needed to support the “redo-log" function-
ality.
It is also possible to add or to remove the D&C protection to path without or with D&C protection. Relevant
commands are under menus:
Protection: Add submenu
Protection: Remove pop-up submenu

2.3.36.6 Path Constraints in a 2-Node SNCP network
The values Use Service Forwards and Use Service Backwards are significant for paths crossing a
SNCP network.
The user drops as constraint one of the Physical connections between the two D& C nodes, or a link
connection, or a CTP, then must select between Use Service Forwards and Use Service Backwards.
If the user selects Use Service Forwards, the object dropped as constraint will be used as service
route/termination to protect the forward transmission direction (from A to Z or from the left to the right
or the TX). See Figure 406.
If the user selects Use Service Backwards, the object dropped as constraint will be used as service
route/termination to protect the backward transmission direction (from Z to A or from the right to the
left or the RX). See Figure 406.
FORWARD
BACKWARD
THIS PHYSCON IS USED THIS PHYSCON IS USED

AS CONSTRAINT: AS CONSTRAINT:
USE SERVICE FORWARD USE SERVICE BACKWARD
Figure 406. Use Service Forward/Backward for Dual Node SNCP network

2.3.36.7 D & C path in a 1-Node Enhanced SNCP network
This connection is useful to increase the protection level when a single NE is interconnecting multiple
rings.
In fact, a path supported by a single virtual ring between the end points A and Z, is not able to survive to
a double failure. See Figure 407.herebelow.
A Z
A A Z Z
1664SX cross connect equipment
Figure 407. Double failure for a SNCP path (w/o enhanced)
2.3.36.8 D & C path create in a 2-Node SNCP network
The Path Create procedure is the same as described in the previous paragraphs, with the following excep-
tions:
– Rate=140 Mb,
– Protection type=D & C SNCP.
2.3.36.9 D & C path allocate in a 2-Node SNCP network
Upon path allocation, the system evaluates, as in case of basic D & C

– main route
– spare route
– two service routes
If you click on the icon of the Switch status, the system opens a subwindow which displays the switch sta-
tus. shows the subwindows relevant to the routing display view of Figure 402.

The graphical appearance of this figure has been changed while contents maintain their validity
Figure 408. Path routing view (one node D & C)

Figure 409. Enhanced SNCP-one node connection detail.
N.B. Figure 409.shows the involved connections. The default switch type is NOT revertive
N.B. The drawing of the switch shows the main switch position (line) and spare switch position
(dashed line). The actual switch position is marked by a M (switch turned on main) or S (switch
turned on spare). See above Figure 409.

The implementation of the enhanced SNCP causes the creation of 4 unidirectional SNCP in the NE:.
– tp A: comprises a switch for the connections coming from tp Z and tp ZA, one point to point from tp
A to tp Z, one point to point from tp A to tp AZ
– tp Z: comprises a switch for the connections coming from tp A and tp AZ, one point to point from tp
Z to tp A, one point to point from tp Z to tp ZA
– tp ZA: comprises one point to point from tp ZA to tp A, one point to point from tp Z to tp ZA
– tp AZ: comprises one point to point from tp AZ to tp Z, one point to point from tp A to tp AZ
N.B. As in the case of the normal D&C, it is not possible from the User Interface to select the tp's
involved in the D&C but they are automatically selected by the routing algorithm. The tp's can
be selected from the command mode because this is needed to support the “redo-log" func-
tionality.
It is also possible to add or to remove the D&C protection to path without or with D&C protection by either
pointing to the topology where the interconnection NE's are included (e.g. the ET which contains the Cross
connect equipment) or to the whole path.
By using an enhanced SNCP the protection level of the path increases.
The default switch type is not revertive.
The RM behavior is as follows:
– the enhanced SNCP is automatically inserted at path/trail allocation time for protected paths/trails
when the main and the spare are crossing the same NE and the equipment supports this type of pro-
tection.
– The user can add / remove the enhanced SNCP protection in two different ways:
• applying the add/remove service to the whole path/trail: the enhanced SNCP protection is also
removed
• applying the add/remove service to the connection in topology at NE level: the enhanced SNCP
protection is modified only at NE level.
• No limitation should be present on the NE support of the connection since the result in this case
is the failure in implementing the protected path

2.3.36.10 2 - Node D & C on single physical connection
a) The path highlighted in figure below is SNCP protected. Only one physical connection is present from
node 1650SMC_C to node 1650SMC_A.
Figure 410. Highlight of a 2 Mb path
b) Point to the path to which the service protection has to be added and issue Path: Modify: Path Mod-
ification Tool
Figure 411. Path: Modify: Path Modification Tool

c) The Path modification tool is presented. Select options Add Service and Dual Node D & C. Click
on Next.
Figure 412. Add Service: Dual Node D & C
d) Select first and second destination, according to the standard selection mechanism. Figure which
follows shows the Selection of the second termination
Figure 413. Selection of the second termination

e) After the selection of both terminations (see below figure), click on Finish to complete the D
& C protection.
Figure 414. Terminations selected
2.3.37 Z & C - 4 Nodes interconnection

DESCRIPTION
The feature allows the management of the D&C 4 nodes interconnection also for the NEs that do not sup-
port, at Q3 interface, the Drop&Continue connection object (representing the three atomic connections
that compose a drop and continue connection schema). For these NEs, the three atomic connections are
provided by RM.
OPERATION
The following apply:
– NEs supporting the Drop&Continue connection object are:
• OMSN
– NEs supporting the three atomic connections are:
• 1850TSS
• 1678MCC
– for the NEs supporting the Drop&Continue connection object, the Drop&Continue connection object
is still provided to the NE
– the add/remove service, when the three atomic connections are provided to the NE, has no traffic
impact only if it is possible to join two unidirectional connection into one bidirectional (remove ser-
vice) and to split a bidirectional connection into two unidirectional (add service)

– the feature is not applicable to the following NEs:
• 1641SX
• 1664SX
• 1674LG
2.3.38 D&C for dual node interconnection on single physical connection (only add
service)
DESCRIPTION
The feature allows the use of a single physical connection for the two route services in a D&C dual node
interconnection, when no resources are available to use two physical connections. The functionality is
allowed only by means of the add service operation specifying the target connections/end points.
OPERATION
– a single physical connection is used for the two route services, when no resources are available to
use two physical connections
– a single physical connection is used for the two route services, even if resources are available to use
two physical connections, when a constraint to use the same physical connection is specified
– *the add service can be performed only by means of the wizard, providing the two target connections
The following figure gives an example.
Figure 415. D&C for dual node interconnection on single physical connection
2.3.39 Single timeslot across the ring

DESCRIPTION

The feature allows the inhibition of the timeslot interchange across a ring. As a consequence, the timeslot
interchange will be inhibited for all the paths/trails crossing the ring itself.
2.3.39.1 Characterizing a NPA to manage the timeslot interchange
A new attribute (timeslot interchange) has been added for the NPA. This attribute allows to inhibit or not
the timeslot interchange. The NPA can be marked as:
– timeslot interchange not meaningful (allowed), that is paths/trails will be allocated following the usual
rules, i.e.:
• for paths and HO trails of virtual concatenation: the rules are based on fragmentation and first
free time slot
• for other HO trails: the rules are the same described in next bullet (preferable avoided)
– time slot interchange still allowed (preferably avoided), but paths/trails will be allocated keeping the
same time slot in the NPA, if possible
– timeslot interchange not allowed (forbidden), that is paths/trails will be allocated keeping the same
time slot in the NPA, if possible; if not possible, the allocation fails
– the value of the attribute is meaningful only for new path/trail to be allocated; no modifications are
foreseen for paths/trails already allocated
– setting to preferable avoided or forbidden value on a NPA already crossed by paths/trails with
timeslot interchange is allowed
– in the trail setup between two CTPs, the trail definition is rejected if these CTPs are in the same NPA,
their payload position is different and the time slot interchange is forbidden in the NPA
– the attribute timeslot interchange is meaningful and modifiable only for SNCP and 2f MS-Spring at
Lower Order
– in all the MS-Springs (both 2F and 4F) at HO the time slot interchange is always forbidden, even if
timeslot interchange is allowed
– in case of add protection/add service, the spare/service to be added will be allocated keeping the
same payload position, that can be different from the payload positions of the link connections
already used in the path/trail in this ring
N.B. This add protection, followed by a remove protection keeping spare, provides a way for the user to
reroute a path/trail, removing the time slot interchange in the ring, without traffic hits
– in case of LO paths, the checks on payload position are performed at path layer only (cross-con-
nection at path layer without timeslot interchange). So, it may occur that a HO trail, completely inside
the ring, with at least 2 hops of length with timeslot interchange (e.g. 01 - 02), can be used by the
path even if timeslot interchange is forbidden
– In case of HO trail partially contained in the ring and partially out, the LO CTP in the aggregate port
inside the ring is to be considered as part of the ring. So, in case of LO path, the timeslot of CTP A
and CTP B has to be the same; the timeslot of CTP C can be different because the long HO trail per-
form timeslot interchange (see figure below)

Figure 416. Timeslot interchange ex 1
– if the CTP C (see figure below) belongs to an aggregate port of a node in another ring, in case of
LO path, the timeslot of CTP A and CTP B has to be the same; the timeslot of CTP C and CTP D
has to be the same but can be different from CTP A/B because the long HO trail perform timeslot
interchange
Figure 417. Timeslot interchange ex 2
– the paths/trails crossing the NPA with timeslot interchange can be retrieved from the NPA itself (new
inventory)
Figure which follows shows the selection of the time slot interchange mode during NPA creation and later
via NPA Show/Set Attributes.

Figure 418. Time slot interchange mode choice in NPA creation
Figure 419. Timeslot interchange attribute

2.3.40 NAPs with Path information
In path creation, step 3 of the wizard, group button=User, the operator can enter the customer name.
The same name is shown in the relevant NAP list (NAPs (with Path information). See following figures
Figure 420. Search from Node: NAPs (with Path information)

2.3.41 Path/Trail Modification Tool
The Add / Remove Protection command can be executed on the whole path/trail via menu command or
directly on the connections in topology via Path/Trail Modification Tool.
The resources needed for a successful command completion could be used by other paths; it
is advisable to create protected paths instead of adding subsequently the protection; namely in
this case the allocation algorithm makes the reservation of non-overlapped routes.
In case of overlapping of an existing route with the new protection route required by the Add Protection
command, it is possible to find the existing route by using the Paths in trail view invoked on the trails ter-
minated to the nodes where terminates the path to be protected.
The Path/Trail Modification Tool (see below icon), provides the following options:
Figure 422. Path/Trail Modification Tool

– Add Protection (Add allocated/implemented protection route between two NE's from routing)
– Remove Protection (Remove protection (keeping main/spare) from routing display)
– Add Service
– Remove service
– Reroute
– Undo Reroute
2.3.41.1 Add allocated/implemented protection route between two NE's from routing
display
Starting from the routing display, the user can add a protection route for an allocated/implemented path/
trail.
Selecting the two connections belonging to different nodes, the portion of path/trail to be protected is
identified.
The wizard provides two areas related to the two connections:
• “A" connection
• “Z" connection
After the selection of the first connection, the choice of the second one is restricted to a subset, with the
following rules:
– if the first connection was chosen starting from the “A connection" wizard area, the second one:
• must be in the same branch (i.e. main or spare or, for a broadcast path, same leg)
• must be located below the first selected connection
• must be located above the first bridge/switch connection below the selected connection
– if the first connection was chosen starting from the “Z connection" wizard area, the second one:
• must be in the same branch
• must be located above the first one
• must be located below the first bridge/switch connection above the selected connection
SEQUENCE
a) Select the path/trail and click on Path/Trail Modification icon.
b) The user selects a connection in the routing display window; this connection is dropped in the wizard
window. When both connections have been selected, the user can control if they are the desired
ones and confirm the operation.
N.B. The user is allowed to choose the same connection both at “A" and “Z" side. This allows a par-
ticular addition of protection that can be useful, for example, in the collapsed dual node between
two MS-Springs.

2.3.41.2 Remove protection (keeping main/spare) from routing display
SCOPE
Starting from the routing display, the user can remove a protection route (keeping main/spare) from apath/
trail. Selecting a connection/link connection of one branch (main/spare), the protection route to be
removed is identified.
SEQUENCE
b) Select Remove protection
The routing display helps the user enabling for selection, only connections in node/link connections
between a pair of bridge&switch. The user has to select only one element: the corresponding branch will
be removed.
When the element is selected, the bounding bridge&switch connections are retrieved and displayed on
the wizard and the information related to the selected branch (main/spare) is provided. At this point the
user can control if they are the desired ones and confirm the operation.
The result of the operation, if successful, is the removal, from the path/trail, of the protection route (keeping
main or spare) between the two bridge&switch connections.
N.B. The user is allowed to remove a branch of path/trail that starts and ends in the same connection
in topology, e.g. the one used in the collapsed dual node between two MS-Springs (see above
add spare).

2.3.41.3 Add service
The following types of add service can be selected: (see following figure)
Figure 423. Path/Trail Modification Tool: add service
– generic service
– 4 nodes drop and continue
– dual node drop & continue
– single node collapsed drop & continue

2.3.41.4 Generic drop & continue
SCOPE
The user is allowed to add:
• two services between four nodes, resulting in four “classic" drop & continue in all the nodes (it
is allowed only for bi-directional paths/trails)
• only one service between two nodes, resulting in two “classic" drop & continue in all the nodes
(it is allowed for both bi-directional paths/trails and unidirectional paths)
• a particular mixed case among three nodes, i.e. two nodes with “classic" drop & continue in one
branch, only one node with "Dual node" drop & continue in the other branch (it is allowed only
for bi-directional paths/trails)
The wizard has to be used with the advanced profile that allows the addition of services among two or
four generic nodes.
SEQUENCE
The wizard provides four areas related to four connections in node:
• “A" main
• “A" spare
• “Z" main
• “Z" spare
Clicking on one of these areas, the routing display allows the user to select connections. The set of select-
able connections is restricted by the following rules:
• the first connection is selectable among the connections belonging to the path/trail portions
between bridge & switch connections
• if a connection main (spare) was selected the spare (main) connections can be selected from
the corresponding path/trail spare portion
• if the A connection (main or spare) was already selected the Z connection is selectable among
the connections below the selected one and above the bridge & switch
• if the Z connection (main or spare) was already selected the A connection is selectable among
the connections above the selected one and below the bridge & switch
- Each time a connection is selected in the routing display window, it is dropped in the wizard window in
the proper area.
In general, the user can specify two or four connections, activating the request to add one or two services
to the path/trail.

2.3.41.5 Add service (4 node drop & continue)
SEQUENCE
b) The user selects a connection in the routing display window; this connection is dropped in the wizard
window. When both connections have been selected, the user can control if they are the desired
ones and confirm the operation.
SEQUENCE
Figure 424. Selection of the NPA
The wizard provides four areas related to four connections in node:
• “A" main
• “A" spare
• “Z" main
• “Z" spare
Only SNCP NPAs crossed by both main and spare branches of the path can be selectable. When the NPA
is selected, the four areas in the wizard window are automatically filled with the bound connections.
In general, the user can use two or four connections, activating the request to add one or two services
to the path/trail respectively.

2.3.41.6 Dual node drop & continue
SCOPE
The routing display let the user select only two connections inside two nodes.
The routing display restricts the selection of these two connections that must be:
• in different branches (i.e. one in the main and one in the spare branch)
• in different nodes
SEQUENCE
Figure 425. Dual node drop & continue

b) Select option Dual node drop & continue and click on Next button. the wizard is presented
c) Select the connection in topology and click on Select button. The selected connection in topology
is now present in the wizard
Figure 426. Selection of the connections in topology
d) After the selection of the second connections in topology, click on Finish button to confirm
An example of 2-node path D & C is shown in figure which follows.

Figure 427. 2-node D & C path

Figure which follows shows the main route connection view detail
Figure 428. Main route connection view detail

2.3.41.7 Single node drop & continue
SCOPE
The scope is to create a single node D & C protection switch.
SEQUENCE
b) Select option Single node drop & continue and click on Next button.
Figure 429. Add service: single node D & C

c) In the Step 2 Add Service (Single node D & C) dialog box click on Get Routing Display button. In the
routing display non selectable connections are greyed. See figure which follows
d) Select the switch (connection in topology). The second switch is automatically selected. See Figure
431.on page 390
Figure 430. Single node D & C. Switch selection.

Figure 431. Step 2. Selected switches.
e) Click on Finish to confirm.
The result of this operation, if successful, will be the addition to the path/trail of one single node drop &
continue connection, contained in the same node as the two selected connections.
2.3.41.8 Remove D&C between topologies, NPA's and NE's
To remove protection service, the user has to select one connection. Depending on the type of service
to remove the routing display retrieves other connections in topology. In particular:
• to remove a collapsed single node drop & continue, the user has to select the single node D&C:
no other connection is retrieved
• to remove a collapsed dual node drop & continue, the user has to select one of the two con-
nections that are ends of the two service: the other one is retrieved automatically
• to remove one or two services between two or four “classic" drop & continue, the user has to
select one of the involved connections: the other drop & continue in the same service is
retrieved; the user can also select another drop & continue related to a second service to be
removed
The user is allowed to select only the following type of connections:

• drop & continue
• dual node drop & continue
• single node drop & continue
The user has also to specify whether the system has to check if the services to be removed are supporting
traffic. The selected and retrieved connections are dropped in the wizard window. At this point the user
can control if they are the desired ones and confirm the operation. The result of this operation, if suc-
cessful, will be the removal from the path/trail of the service between the connections dropped in the wiz-
ard window.

2.3.41.9 Reroute
SCOPE
This command allows to reroute a transport object. The transport object can be allocated, partially imple-
mented or implemented.
SEQUENCE
The user can choose between two reroute modes:
– normal mode: the operation is allowed only when it is possible to avoid traffic hits, i.e. when the
transport object is allocated or in the following cases:
• inside an ASON NPA; in this case 1354RM uses the service offered by GMRE to move the nom-
inal route of a SNC, without affecting traffic
• inside a fast restoration NPA; in this case, the operation only changes the routing in the
1354RMMIB, without performing any operation to the NEs
• on not active trails of a virtual concatenated path, because they are not carrying traffic
– forced mode: the operation is allowed even if it can create traffic hits.For protected transports, the
segment that can be rerouted must contain only point-to-point connections intopology.For broadcast
paths, rerouting is not supported.
Figure which follows shows an example of Transport reroute step 2 dialog box.

Figure 432. Transport reroute step 2 dialog box
2.3.41.10 Undo Reroute
This command applies only to allocated transports and allows to revert to the previous route.

2.3.42 OS driven restoration for HO paths & trails
The OS driven restoration applies to HO paths and trails. OS driven restoration is not applicable for 2F
MS-Spring, 4F MS Spring and linear MSP.
2.3.42.1 Create a restoration rule
Create a restoration rule means enable the restoration function for the selected transport (path or trail)
according to the rule being created.
a) From the path list or trail list select an HO path or an HO trail and select button Create Restoration
Rule. See Figure 433.The Create Restoration Rule is displayed. See Figure 434.on page 394
Figure 433. Restoration:Create Restoration Rule.

Figure 434. Create: Restoration Rule.
b) Select the following attributes:
1) Restoration strategy. Possible values are:
– optimized add protection (for point to point transports only).This strategy does not cause
a complete path rerouting but only finds a spare route inside the lowest level topology (e.g.
a ring) affected by the fault.
– end to end add protection. (for point to point and broadcast transports) This strategy
causes a complete path rerouting by allocating the path spare route.
– remove protection + end to end add protection (for point to point transports only). It
removes the protections and adds one end to end spare route. For paths protected by the
D&C mechanism both spare and spare+service connections are removed; only one end
to end spare route is allocated.
the default value is optimized add protection.
2) Hold Off Time (sec). This time is the waiting time before starting the restoration subprocess.
3) Used Resources. Possible values are:
– not alarmed objects (default)
– all objects. This option will successfully restore the transport upon repair of the related
resources.

4) Constraint Rule. Possible values are:
– do not use constraints (default)
– use default constraints. This option sets the usage of the "spare" constraints for the trans-
port restoration. The "spare" constraints are added by means of the Path Constraints
application.
c) Click on the functional button Create. The restoration rule is created. Its name coincides with the
transport name.
2.3.42.2 Display a restoration rule
a) From the browser point to the network domain and issue the command Display: Related Items.
Select Restoration Rules. The icon of the restoration domain is displayed in the browser window (see
Figure 435.) and the restoration rule list opens. See Figure 436.
Figure 435. Browser: restoration domain.

Figure 436. Restoration Rule list.
The displayed attributes are:
– user label. It coincides with the transport name.

– object type. The possible values are path or trail.
– restoration strategy. See paragraph 2.3.42.1.
– hold off time. See paragraph 2.3.42.1.
– restore working state. It can assume one of the following values:
• normal. No restoration activity is in progress.
• hold off active. The restoration activity will start at hold off time expiration.
• waiting for concurrency. It is an internal waiting state.
• restoring. The restoration activity is in progress.
– last restoration result. It can assume one of the following values:
• none. No restoration has been requested for the transport.
• successful. The restoration process completed the allocation.
• failed. The restoration process did not complete the allocation because of lack of resources.
• not performed. The restoration process did not complete the allocation because of external
conditions.
– date of the last successful restoration result
b) You can display other attributes by selecting the transport and issuing the command
Actions:Details:Show/Set Attributes. The dialog box of Figure 437.is presented.

Figure 437. Restoration Rule attributes.
For trail or path the attribute Restoration state can assume one of the following values:
– none. No restoration rule is associated to the transport.
– supervised. A restoration rule is associated to the transport.
– restored. The transport has been restored. A subsequent restore cannot visualized. In
order to return to the supervised status, the operator must select the transport (from the
list) and issue the command Actions:Restoration:Set to Supervised.

2.3.43 Join/Split Path
Join/Split path are used to merge a pair of paths into one single path or to split a path into a pair of paths.
2.3.43.1 Join Paths
SCOPE The scope of this procedure is to merge a pair of paths into one single path.
CONDITIONS
a) In the example which follows a path crossing SUBN1 must be merged to a path crossing SUBN2.
b) By clicking twice on the icons of SUBN1 and SUBN2 it is possible to display the two subnetwork sub-
maps. See Figure 438.
c) Both SUBN1 and SUBN2 are crossed respectively by path P1 and path P2 which physically are the
same path. Namely both P1 and P2 are terminated to virtual nodes NE_V1 and NE_V2. The Path
List containing P1 and P2 is shown in Figure 439.To display the Path List, from the browser, point
to the Network icon and issue Actions: Display: Related items: Paths in Topology + No Filter.
The Path List is displayed. See Figure 439.on page 399
Figure 438. Submaps of SUBN1 and SUBN2

Figure 439. Path List containing paths P1 and P2
SEQUENCE
a) Create a physical connection between nodes NE-V1 and NE-V2. Select nodes NE-V1 and NE-V2
and issue Create: Physical Connection
b) In the Create Connection wizard step 1, select connection type SDH, enter connection name, select
STM type and click on Next button, thus passing to step 2.

Figure 440. Create connection-step 1
c) Node NE-V1 is already present in the drop area. Enter the port name. This causes the creation of
the virtual port. Node NE-V2 is already present in the drop area. Enter the port name. This causes
the creation of the virtual port. Click on Next button.

Figure 441. Create connection-step 2

d) The Finish button, if selected completes the connection create.
The Cancel button, if selected aborts the connection create.
The Previous button allows to revert to the previous screen, in order to modify port selection, con-
nection name...
Figure 442. Connection between the virtual nodes.
N.B. If the paths to merge are protected, two virtual Physical connections must be created at above
steps a) to d). The redundant SDH virtual ports must be created accordingly.
e) Execute the implementation of the virtual physical connection. Select the virtual physical connection
Actions: Modifications: Implement
f) Execute the payload configuration of the virtual physical connection: select the object from the map
and issue Tools: Modify Payload. The payload structure must be congruent with the configuration
of SUBN1 and SUBN2.

Figure 443. Payload configuration of the virtual physical connection

Figure 444. Path Create between external network references.

g) Create a “virtual" path PV between the external network references. This path should have the same
attributes as the two paths P1 and P2 to join.
h) Allocate and implement path PV (e.g. selecting the path from the path list and issuing Actions: Con-
figuration: Config. State modification: Allocate and then Actions: Configuration:Config. State mod-
ification: Implement.
i) From the path list (see Figure 445.herebelow) join first paths P1+PV. Select the paths and issue
Actions: Modification: Join.
Figure 445. P1+PV Join path pull-down menu.

j) In the Join path dialog box enter the name of the joined path (e.g. P3) and click on the functional but-
ton Join path. After a few seconds paths P1 and PV are deleted and the new path P3 is created and
implemented.
Figure 446. Join path dialog box (P1+PV=P3)
Figure 447. Path list: paths P2+P3

k) From the path list join paths P2+P3. Select the paths and issue Actions: Modification: Join.
Figure 448. Actions: Modification: Join
l) In the Join path dialog box enter the name of the joined path, e.g. P and click on the functional button
Join path. After a few seconds paths P2 and P3 are deleted and the new path P is created and imple-
mented. See Figure 449.
Figure 449. Path list after join operation.

Figure 450.shows the path routing view of path P.
Figure 450. Path P highlighted.

2.3.43.2 Split path
SCOPE
The split path is the reverse operation of the join path.
SEQUENCE
a) Select the path P to split from the path list and issue Actions: Manage path: Split path
b) In the Split path dialog box enter the names of the two paths which are replacing the path to split and
click on Split path button. The system presents to the user the list of the nodes along the path route.
c) Select the node where the path must be split and confirm. Path P is deleted and the new paths are
created and implemented.
Figure 451. Actions: Manage path: Split path

Figure 452. Split path dialog box.
Figure 453. Node selection.

2.3.44 Join-Split Trail
Two HO-Trails entering in a given NE can be joined in order to reduce the LO usage of resources or an
HO-Trail crossing at HO a Node can be split in order to perform crossing at LO.
2.3.44.1 Split a HO-Trail
A given HO-Trail crossing at HO a Node can be split in order to perform crossing at LO. This enables the
usage of LO resources in the splitting Node.
The operation reproduces in the splitting node the same payload structure of the starting trail.
The operation can be performed after the split of a Physical Connection.
Input to the operation is the HO-Trail to split.
SEQUENCE
a) Point to the trail to split and select Trail: Modification: Split
Figure 454. Trail: Modification: Split

b) in the Split trail dialog box enter the trail names of the new trails and click on Start Split button.
Figure 455. Split trail dialog box
c) The system presents the list of the possible splitting nodes. Select the node and click on OK.
Figure 456. Common node selection.

As a consequence of the operation:
– the old HO-Trail is deleted
– two new HO-Trails are created
– The LO-Paths "crossing" the splitting Node are modified by adding LO pass-through connection. The
related protection indexes are updated.
The payload structure and the LO connections of the 2 nodes at the end of the involved HO trails are not
modified during the operations: modifications to connections and payload structure are applied only to the
splitting node.
Figure 457. Split trail report
The operation reduces the impacts on the existing traffic: the LO-Paths client of the involved HO trails are
disconnected only for the time necessary to perform the operation: only the segment of network between
the end nodes of the involved HO trails is affected.

2.3.44.2 Join two HO-Trails
Two HO-Trails entering in a given NE can be joined in order to reduce the LO usage of resources.
SEQUENCE
a) From the trail list select the HO-Trails to join. See Figure 458.
b) Select the command Actions:Modification: Join. The Join trail dialog box is presented, containing the
two selected trails, as per Figure 459.Enter the name of the new joined trail.
c) Click on button Join trail to start the operation.
RM performs the following checks:

– the 2 HO Trails must have the same payload structure;
– it must be possible to create an HO connection in the intermediate node;
– all LO-paths using the original HO-Trails are crossing with pass-through connections the interme-
diate NE without LO time-slot interchange.

– the old HO-Trails are deleted
– the new HO-Trail is created
– the LO-Paths "crossing" the original HO-Trails are modified by removing the pass-through connec-
tions in the intermediate NE. The related protection indexes are updated.
intermediate node.
The operation reduces the impacts on the existing traffic: LO-Paths client of the involved HO trails are dis-
connected only for the time necessary to perform the operation and only in the segment of network
between the end nodes of the involved HO trails.

Figure 458. Actions: Modifications: Join.

Figure 459. Trail: Modification: Join dialog box.
2.3.45 Join-Split Physical Connection

According to different ring configurations, the usage of the join / split physical connection is
inserted in different macro-procedures. Please refer to paragraph Network Modifications.
2.3.45.1 Split Physical Connection
SCOPE
The Split Physical Connection is used to insert a new Node into a pre-existent topology.
STATUS CONDITIONS
Allowed Physical Connection working states are: Normal, Failed to Split, Failed to undo Split, Failed to
disconnect.
Allowed Physical Connection Implementation state is Implemented.
HO LCs working state must be Normal (no payload configuration in progress)
TOPOLOGY CONDITIONS
If the PhysCon is included in a ring the node to insert is not connected and placed in the ring map. See
example herebelow.

If the PhysCon is not included in a ring ET working state=Normal and ET Implementation state=Imple-
mented.
SEQUENCE
a) From browser interface point to the icon of the Physical Connection to split and issue the command
Topology Modification: Split.
Figure 460. Topology Management pop-up menu.

b) The guided interface structure (the so called wizard) opens. See Figure 461.herebelow. It contains
in the upper part of the window the icons of the physical connection to split and the connected ports.
Figure 461. Split wizard: step1
The central part of the window allows to select the node to insert. Click on the selection button (three
points). The node list is presented. See Figure 462.

c) Select the node to insert and click on Apply button. The icon of the selected node appears in the wiz-
ard. See Figure 463.herebelow. You can also display the node in the map by clicking on the Highlight
button.
Figure 463. Node inserted.

d) Click on Next button to continue the procedure. The wizard now presents the first port of the physical
connection being split and the node being inserted. Click on the selection button in order to select
the port of the new node to connect to the first port of the physical connection being split. The relevant
port list is displayed. See Figure 465.
Figure 464. Step 2. First port to use.

e) Select the port to connect and click on Apply button. The icon of the selected port is presented in
the wizard. See Figure 466.
Figure 466. Step 2. First port to use.

f) Enter the new connection name and click on Next button to continue.The wizard now presents the
second port of the physical connection being split and the node being inserted. Click on the selection
button in order to select the port of the new node to connect to the second port of the physical con-
nection being splitted. The relevant port list is displayed.
g) Select the port to connect and click on Apply button. The icon of the selected port is presented in
the wizard.
h) Enter the new connection name and click on Next button to continue.The wizard now presents the
summary view of the operations executed by the user. See Figure 467.herebelow.

Figure 467. Split connection summary dialog box.

i) If you click on Finish button the existing physical connection is deimplemented and deleted, while
the new physical connections are created, implemented and structured accordingly. In particular, the
following steps are performed:
1) Disconnect client paths/hoTrails
2) SDH ports assignment
3) Insert node in ET
4) MS-TP structure
5) create the objects in DB
6) Connect client paths/hoTrails
2.3.45.2 Join physical Connection
N.B. This command is not possible if the two physical connections are connected to the same nodes.
See following figure
A B
Join A+B allowed
B Join A+B not allowed
Figure 468. Restriction on Join physical connections
SCOPE
The Join Physical Connection is used to remove a Node from a topology
CONDITIONS
The topology implementation state is Implemented and the working state is Normal.
SEQUENCE
a) From browser interface point to the icon of the Physical Connection to slit and issue the command
Topology Modification: Join. The Join Physical Connections dialog box is displayed. See Figure
469.on page 425

b) From browser window drag and drop the second physical connection to join, enter the connection
name and click on Start Join button.
Figure 469. Join Physical Connections dialog box.
c) A report window is presented containing all messages

Figure 470. Join Physical Connection report
2.3.45.3 Fail to join working state
If following a join physical connection procedure, the physical connection enters the Fail to join state, the
operator can select the Undo Join physical connection.
2.3.45.4 Fail to split working state
If following a slit physical connection procedure, the physical connection enters the Fail to split state, the
operator can select the Undo Split physical connection.
2.3.45.5 Fail to disconnect working state
If following a join/slit physical connection procedure, the physical connection enters the Fail to disconnect
state, the operator can select the Connect path action or repeate the failed action.
2.3.45.6 Fail to connect working state
If following a join/slit physical connection procedure, the physical connection enters the Fail to connect
state, the operator can select the Connect/Disconnect Path/Trail
2.3.46 ISDN primary access management
This feature activates the adaptation function of the incoming 2 MB/s ISDN-PRA signal to process a
framed or not framed signal.
2.3.46.2 ISDN-PRA Procedure
a) From the path pop-up menu select item Client Alarms: PDH alarm monitoring. The ISDN-PRA dialog
box is presented. See Figure 472.on page 428. The dialog box is structured in two sequential views.
The first window allows to select the PDH alarm monitoring type. See Figure 472.on page 428.

Figure 471. Path: Alarms: Operations: On Clients: PDH framing

Figure 472. ISDN-PRA step 1 dialog box (alarm monitoring type)
b) You can select among the following options:
– unframed (default value). No path frame monitoring is performed.
– framed. The pdh signal frame is monitored and consequent alarms are generated. The monitoring
direction (ingressing / egressing, both or none)
– ISDN-PRA (Integrated Service Data Network-Primary Access=2 Mb/s). This option is allowed for
bidirectional paths only. Only one of the two ports must be marked as NT (Network Termination). PDH
monitoring (frame monitoring) will be activated only on the port marked as NT, which is the one con-
nected to the TE (Terminal Equipment = User's premises
– leased line PRA. This option is allowed for bidiectional paths only. One or both of the two ports can
be marked as NT (Network Termination). PDH alarm monitoring will be applied only on NT ports.

Figure 473. ISDN-PRA step 2 dialog box (Port role assignment)
c) Select the desired option and click on Next button.

Figure 474. ISDN-PRA: NT Ports selection.
2.3.47 4 x ANY
The 1696MetroSpan provides the 4XANY TDM card.
The 4XANY TDM card is a TDM concentrator board, based on the following concepts:
-The following client signals can be transported:
• FDDI (125 Mb/s)

• Fast Ethernet (FE) (125 Mbit/s)
• ESCON (200 Mbit/s)
• Digital Video (270 Mbit/s)
• STM-1 (155 Mbit/s)
• STM-4 (622 Mbit/s)
• FC (1.062 Gbit/s)
• Gigabit Ethernet (GE) (1.25 Gbit/s)
The board accepts at most 4 signals and mapping is performed into a STM-16 (2.5 Gbit/s) port
– The architecture of TDM concentrator board is based on the concept of virtual concatenation, and
on the mapping of SDH on OTN:
– Data traffic is packet into VC-4 structures (virtually concatenated)
• VC-4's are groomed into a STM-16 structure

• STM-16 signal is transported through the optical network as RS Client Path
The following table resumes the traffic that can be transported and the number of VC-4 required:
Traffic Speed SDH Transport Structure
FDDI 125 Mb/s VC-4-1v
Fast Ethernet 125 Mb/s VC-4-1v
ESCON 200 Mb/s VC-4-2v
DV 270 Mb/s VC-4-2v
STM-1 155 Mb/s VC-4-2v
STM-4 622 Mb/s VC4-5v
FC 1.062 Gb/s VC4-8v
Gigabit Ethernet 1.25 Gb/s VC4-8v
N.B. Applicable for STM-1 and STM-4 terminations. Only the SDH physical connection
between the 2 SDH NE is described in RM and the manual correlation function can per-
mit to associate the underlying DATA PATH to it. Fiber cut on the fiber connecting the
SDH NE adjacent to the SDH port of the 4xany card will be detected on SDH NE side and
will impact the mentioned above SDH physical connection.

The 4XANY card can be:
– Connected inside the 1696MetroSpan to the Transponder card to transport Data traffic on the RS
signal (STM-16) on the OTH network.
– Connected inside the 1696MetroSpan to the OPC card to perform the SNCP protection of the RS
client path in the OTH network (Optical protection).
– Alone inside the 1696MetroSpan (CPE configuration case). In this case, 1696MetroSpan, configured
as CPE, could be connected to either another 1696MetroSpan (not configured as CPE), a 1686WM
or a 1640WM (either through B&W or colored interface), an SDH NE (through B&W interface).
Due to the fact that the RS signal is terminated on the 4XANY, the 1696MS hosting this board has to be
visible both in SDH and OTH domain, i.e. the STM-16 port of the 4XANY board has to be managed as:
– UNI B&W or colored port of an SDH NE. In particular in the first and second above listed cases, the
STM-16 port will be connected by the user, through an internal physical connection, to the OPS port
of respectively the transponder or the OPC card.
In the third case, the user will create a physical connection connecting the STM-16 port of the 1696WM
(CPE) and the OPS port of either a 1686WM or a 1640WM.
On the client side (data port) the 4XANY can be physically connected to an OMSN NE to transport an
STM-1/STM-4/GigabitEthernet traffic, coming from the SDH network, into the OTH network. It is not pos-
sible to describe in the RM this physical connectivity (between an STM-1/STM-4/GigabitEthernet port of
the 4xANY and an OMSN NE port at the same rate); the user has to correlate through the "correlation func-
tion" the SDH physical connection between the two external OMSN NE's to the Data path terminated on
the two 1696MS NE's.
2.3.47.2 Upload of the Data ports
When uploading a gMAUTTP port of the 1696MS, the system automatically creates the following objects:
A RM port characterized with:
– Technology: "Data"
– Physical Port Type: is set according to the value of the "dataClientType" attribute of the
– gMAUCTPBid MOC retrieved from the NE
– Au4maxSupportedConcLevel and concLevelMode are set according to the following table
physicalPortType Au4Supported ConcLevel concLevelMode
Eth/100Mb-transp 1 notModifiable
Eth/1Gb-transp 8 notModifiable
Fddi 1 notModifiable
Escon 2 notModifiable
DigitalVideo 2 notModifiable
FiberChannel 8 notModifiable
Stm1 2 notModifiable
Stm4 5 notModifiable

2.3.47.3 Create Path
To create a path involving a 4XANY board, the user, during the path creation activity, has to select:
-Service Type either "Ethernet" or "Data".
According to the selected Service Type all consistent values of Service Rate attribute are presented to
the user.
In case of Service Type ="Ethernet" and Service Rate ="1Gbit/s Ethernet Transparent", the list of NAP'
s available on either 1670SM or 1696MS(4XANY) is provided. For all the other cases, only NAP' s on
1696MS will be listed. The path is created with Transport Rate attribute equal AU4-nV, concLevel attribute
equal to the concLevel attribute of NAP' s and concLevelMode equal notModifiable.
2.3.47.4 Example
a) From the browser node list select the node which houses the 4XANY board and issue Search: Main
Related items: Ports in Node
Figure 475. Ports in node
b) Ports managed by the 4xANY are:
– STM-16 board
– DATA boards, according to the table explained above at para 2.3.47.1 on page 430
c) The path using these ports is Ethernet with Service rate=AU4-nV (concatenated).
2.3.48 Take-over of paths and trails (point-to-point + SNCP)

DESCRIPTION

The feature includes the possibility to point to a Nap, to a CTP or to a trail (physical, MS, HO) and to upload
the network connectivity if not defined in RM. This includes also the take-over of the LO payload of HO
trails. The recursion between discovery of paths and trails is under analysis.
OPERATION
The feature allows the automatic creation (and eventually the allocation, implementation and commis-
sioning) of paths/trails starting from the information present in the NE.
SEQUENCE
a) Point to one of the following objects:

– NAP
– CAP
– CTP
– port
– physical connection
– link connection
– node
and issue Path/Trail take-over. The user has also to provide the target Configuration State for the dis-
covered path/trail (defined, allocated, implemented and commissioned).
Figure 476. Nap: Path/Trail take-over

Figure 477. Path/trail take over wizard step 1
b) Click on Next button.

As result of the-take over, the following operations are performed:
· the path/trail is created (allocated, implemented and commissioned)
N.B. The feature is applicable only to point-to-point or SNCP path/trail.
The created path/trail has the following characteristics:

– the user label of the created path/trail is automatically calculated by the system
– the ASAP profile of the created path/trail is not uploaded, but it is set according to the RM rules
– the PM related to the created path/trail are not uploaded, but they are started according to the RM
rules
Figure which follows shows the path list after the path upload.

Figure 480. Path list: uploaded path
2.3.49 Reroute paths from physcon

This procedure allows to select the destination physical connection. It is used for link capacity upgrade,
when replacing a small capacity link (e.g. a STM-4) with a bigger one (e.g. a STM-16)
Figure 481. Physical connection:Reroute paths

Figure 482. Reroute paths crossing a physical connection
2.3.50 Force path switch from physcon

The Force path switch moves paths from a physical connection.
It is applicable only to protected paths.
a) To start the procedure, point to the involved physical connection and issue Maintenance:Generic.

Figure 483. Force path switch (Physcon:Maintenance:Generic)
b) The Maintenance wizard is displayed

Figure 484. Maintenance wizard
The upper row contains the physical connection being set to maintenance, whose paths are to be moved.
Paths to move are listed in the lower list.
Commands can be selected by pressing one of the radio buttons:
– set in maintenance with check. The check is run on the not active route (at that time)
– set in maintenance no check
– remove from maintenance. The force command is released. The reversion will be active, if already
stored.
2.3.51 End to end path reroute (broadcast incl.)

This command causes an hitless path rerouting, in order to optimize the path route, which during the path
history, due to the occurrence of faults, could be not the best actual route. This command allows to perform
the reroute on the whole path/trail. It is not necessary to provide the cross-connections limiting the path/
trail segment to be rerouted. The user has to select the path he wants to reroute and perform the reroute
command (by means of the pop-up menu). See figure below.

The command is applicable for not protected path (concatenated or not, terminated or not): for concat-
enated path, the command performed on the path, leads to the reroute of all the server trails. The com-
mand is supported by the batch application too.
The command is applicable also for broadcast paths
Figure 485. Path: Modification: Reroute
The possible options are:
– Avoid traffic impact the reroute is not performed if there is a traffic impact
– Avoid traffic impact s (only allocation) the reroute is not performed if there is a traffic impact
– Allow traffic impacts the reroute is performed even if there is a traffic impact
– Allow traffic impacts (only allocation) the reroute is performed even if there is a traffic impact

2.3.51.1 Example reroute broadcast path
SCOPE
Given the broadcast path shown in figure below, perform the reroute
Figure 486. Broadcast path to reroute
SEQUENCE
a) From the path list, point to the path broadcast to reroute and issue Modification: Reroute:Allow traffic
impacts
Figure 487. Modification: Reroute:Allow traffic impacts
b) The broadcast path is rerouted. All legs have been rerouted. See following figure

Figure 488. Broadcast path has been rerouted
2.3.51.2 Broadcast path reroute leg from physcon
The highlight of the broadcast path shows also the list of the used physcons (first level)
Figure 489. Highlight broad path: physcons list (first level)
a) E.g., select the 3rd leg and click on highlight button. The relevant physcon structure is displayed.
Point to the physcon and issue Reroute paths

Figure 490. Highlight 3rd physcon: Reroute paths
b) The Reroute Physcon wizard opens. Click on specify destination physical connection
Figure 491. Reroute Physcon wizard

c) Select the reroute operation type (preserve or compact payload position). Preserve means that
paths are allocated in the destination physcon by keeping the same payload position as in the source
one, else the path reroute fails.
Figure 492. Select the reroute operation type
d) Click on destination physcon selection button. From the list, select the suitable physcon and click
on Apply
Figure 493. Destination physcon selection

e) The icon of the selected physcon is pasted in the destination physcon selection box. Click on Apply
to start the operation. A confirmation is requested. click on OK to continue. Now, you can click on
Show logger button, to see the result of the operation.
Figure 494. Reroute physcon end of selection
f) The path highlight shows also the list of used physcons (first level). The physcon specified as des-
tination is marked by M. From the physcon structure you can see that the involved path has been
correctly rerouted.
Figure 495. List of used physcons (first level) after physcon reroute
2.3.51.3 Save route and recall
a) Point to the path and issue Other: Save and Recall:Save route as constraint set. The set of con-
straints is saved.

b) Subsequently, on the same path, with configuration state=allocated, issue command Add Con-
straints. The constraints wizard opens. Click on Next. In the subsequent view, select Constraint
set=last route. Deselect Initial set button. The list of constraints is displayed
Figure 496. Constraint set=last route
c) You can modify the constraints set, e.g. as per figure below. Click on Finish to save the constraints
set

Figure 497. Constraint set modification
d) Allocate the path and implement the path. You can verify on the path highlight the successfull appli-
cation of the constraints. So the path has now new routes. This could be happen, also because of
a reroute operation caused by a fault occurrence.
Figure 498. Path highlight (application of the constraints)
e) If you want to revert to the initial situation when you saved as last saved route, you can issue
Other:Save and Recall: Recall last saved route

Figure 499. Other:Save and Recall: Recall last saved route
f) A warning message alerts that this could cause traffic hits. Click on YES. Figure which follows shows
the Highlight of the recalled route
Figure 500. Highlight of the recalled route
2.3.52 Reuse of Physical Connection on different VC for the same path

In order to connect an external test instrument, it is possible to specify as constraint the same Physical
Connection on different VC for the same path, i.e. specify 2 LCs on the same route with USE and MAIN.
2.3.53 Save and recall of nominal route with constraint set

This functionality, invoked via menu Other: Save and Recall: Save/Recall, allows to store the actual path
route by storing a complete set of constraints, that can be later retrieved and applied on.

2.3.54 Save and recall of nominal route as constraint set
SCOPE
This functionality, invoked via menu Other: Save and Recall: Save/Recall, allows to store the actual path
route by storing a complete set of constraints, that can be later retrieved and applied on.
2.3.54.1 Save and Recall: Save Route as Constraint set
SEQUENCE
a) Point to the path and issue Other: Save and Recall: Save Route as Constraint set
Figure 501. Other: Save and Recall: Save Route as Constraint set
b) A dialog box alerts that the new saved route will overwrite the old one, if any. Click on Yes to continue.

Figure 502. Save Route as Constraint set confirmation
c) You can check on the command log that the command has been successfully executed (green flag).
Figure 503. Save Route as Constraint command log
d) The Constraint wizard opens. Click on Next button
Figure 504. Constraints wizard
e) The Constraint wizard step 2 opens. Select the new Constraint set Last saved

Figure 505. Constraint set selection
f) The last saved route is displayed
Figure 506. Last (saved) route display

2.3.54.2 Save and Recall: Recall Route as Constraint set
SEQUENCE
a) Point to the path and issue Other: Save and Recall: Recall last saved route
Figure 507. Path: Other: Save and Recall: Recall last saved route
b) A warning box alerts that a traffic hit could arise, if the path is not protected.
Figure 508. Warning: traffic hit for not protected path
c) Figure which follows shows the example of unsuccessful reroute on the last save route

Figure 509. Unsuccessful reroute on the last save route

2.3.55 Planned Activities for path, trails and Nodes operations
Scheduling an action means planning (deferring) an action over a selected object.
This feature allows to schedule a set of actions over the following entities:
Path
Trail
Node
Scheduling may be set as:
-One shot: the action is started in a specific instant (start time) fixed by the operator;
-Cyclic way: the action is performed in a specific instant (start time) and will be repeated periodically.
Figure 510. Scheduled action: one shot.
Figure 511. Scheduled action: periodic task
With reference to above figure, Tstart = Start date and time instant; T* = Schedule interval; Tend = End
date and time instant.
In this case the scheduled action is executed 3 times at the instants:
Tstart+k(T*), with k = 0, 1, 2
2.3.55.1 Max execution delay
If at start time (Tstart) the Agent of the scheduled action is not running, the scheduled action is not exe-
cuted. The operator can define a guard time called max execution delay. This parameter represents the
maximum waiting time (in seconds), respect to the start time, that the system is waiting for Agent restart.

Figure 512. Max execution delay: agent state scenario
With reference to the above figure:
Tstart = Start date and time instant
Trun = instant when the Agent from not running goes to running
If MaxExecutionDelay<(Trun-Tstart) (e.g. MED) the scheduled action is not performed;
If MaxExecutionDelay>(Trun-Tstart) (e.g. MED) the scheduled action is started at the Trun instant.
2.3.55.2 Scheduler entity and state
The object called scheduler represents a scheduled job on a specified object (path, trail, node). The
attribute scheduleState informs the operator about the progress of the scheduled action. The scheduler
state may assume the following values:
idle: the scheduled action has been defined. This is a transient state, i.e. automatically the scheduler state
switches to the standby value;
standBy: the scheduler is waiting for start time elapsing.
active: the job defined in the scheduler entity is running. In case of periodic task (or cyclic way running)
this state is assumed at every job starting and running.
terminated : the job defined in the scheduler has run. In case of periodic task it means that the whole peri-
odic task has run.
suspended: the scheduler has been locked (before start time elapsing). This state is useful when the
operator has to perform an action having any impact on the scheduler. The state may be carried back to
the standBy state unlocking the scheduler.
The scheduler object is not automatically deleted; it can be deleted only by the operator.
In case of removing of the object (path, trail or node) on which a planned activity has been defined, the
state of the scheduler is set to terminated independently from the state (running or not) of the planned
activity.
The operator, reading the log file, can understand if the planned activity has run or not.

2.3.55.3 Activities from Netw Dom (NetworkDomain to Scheduler)
From ntwDomain issue Search: Related Objects: Planned Activities
Figure 513. Network Domain: Search: Related Objects: Planned Activities
The inventory retrieves all the schedulers belonging to the selected network domain. See below figure
Figure 514. Planned Activities list
2.3.55.4 Path to Scheduler
From path issue Search--> Related Objects--> Planned Activities
The inventory retrieves all the schedulers defined over the selected path.
2.3.55.5 Trail to Scheduler
From trail issue Search--> Related Objects--> Planned Activities
The inventory retrieves all the schedulers defined over the selected trail.
2.3.55.6 Node to Scheduler
From Node issue Search: Related Objects: Planned Activities
Behavior: the inventory retrieves all the schedulers defined over the selected node.

2.3.55.7 SchedulerReportList
From a Planned activity issue Actions: Scheduler Report List
Behavior: the inventory retrieves the selected scheduler associated with the remote attribute syncSched-
uleName. This remote attribute represents the name of the file log associated with the selected scheduler.
Case of a scheduler task defined one shot the output will be a single instance of the input scheduler asso-
ciated with the single log file. Case of a scheduler task defined periodic task the input object is reported
as output N-times according to the N reports name retrieved in the action.
2.3.55.8 Schedule operations wizard/tool
SCOPE
The scope is to manage the scheduled operations.
SEQUENCE
a) The tool may be started from the browser. As an example, from Path list, select the path and click
on button Planned Activities wizard. See following figure.
Figure 515. Planned Activities wizard button
b) The Planned Activities wizard: Start dialog box is displayed. Click on Next button.

Figure 516. Planned Activities wizard: Start
Figure 517. Planned Activities wizard: Select wizard

You can drag and drop the object, instead of starting the tool from the already selected object.
c) Select the action. Click on the expand button in correspondence to the desired commands. The com-
plete list of available commands is shown. See following figure.
Figure 518. Planned Activities wizard: Select Object step 1

d) Select the desired command. (e.g. Protection: Add Spare) as in figure herebelow.
Figure 519. Planned Activities wizard: selection of the command
e) Click on Next.
f) After the selection of an operation to be scheduled (e.g. configuration download enabling) and after
clicking on the Next button the wizard asks for:
-User Label: must be unique (max 32 chars)
Start date and time: is a STRING (having the format: YYYY/MM/DD-HH:MM:SS) representing date and
time when the scheduled action will start
Result location: This parameter is automatically loaded by the system with the following rule: http://mas-
ter/1354RM/log/scheduler/?userLabel?.txt.
Also for this reason the User Label parameter must be univocal. In case of Periodic Task the log files are
as many as the running time of the scheduled action in cyclic way, in this case the rule is:
http://master/1354RM/log/scheduler/?userLabel?/?userLabel?#.txt.
Max execution delay: INTEGER representing (in seconds) the maximum execution delay, respect to the
scheduleStartTime, of the scheduled operation. This optional attribute is useful to try to avoid that the
scheduled action is not performed because at the Start date and time instant the Agent is not running. The
same behavior is adopted in case of scheduler suspended and subsequently resumed, i.e. this param-
eter represents the maximum waiting time (in seconds), respect to the scheduleStartTime, that the system
is waiting to accept for Agent restarting or for scheduler unlocking. Default value is 0.

Task priority: (schedulePriority attribute) it is an enumerated representing the priority associated to a
scheduled action; i.e. two or more scheduled actions having the same scheduleStartTime should start
according to their priority: high, medium, low. It is used also in case of Agent restarting: it establishes the
priority of the eventual scheduled actions in queue. Default value is medium.
Periodic task: it is a flag allowing to choice the execution of the scheduled action in one of the following
ways: one shot (default value); cyclic way.
Schedule Interval: it coincides with the scheduleInterval attribute defined on the SNML-IM; this param-
eter is modifiable only if the operator selected the execution in cyclic way.
End date and time: it coincides with the scheduleEndTime attribute defined on the SNML-IM; this param-
eter is modifiable only if the operator selects the execution in cyclic way.
Figure 520. Planned Activities wizard: Select Parameters 1

Figure 521. Planned Activities wizard: Select Parameters 2
g) After clicking on Finish button, the scheduler object is created with scheduleState=idle (transient
state) that immediately becomes standBy.
Using Next and Back buttons of the wizard the operator can create more schedulers over the same object
or also over others objects. The operator can also read the log file related to the scheduler creation. Click-
ing on Action Log button a new window appears showing the log file related the creation session (see
next figure).

Figure 522. Planned Activities wizard: Logger messages
Operations that can be scheduled
The operations that can be scheduled depend on the selected entity: path, trail or node.
Not all possible operations can be scheduled.
Only the operations that do not need any additional parameter can be scheduled. Example: an add pro-
tection action on a path is schedulable if can be performed without adding any parameter; i.e. the pro-
tection is established between the two end points and not between an end point and an intermediate point
or between two intermediate points.

2.3.55.9 Operations on a Planned Activity
On a Planned Activity issue Actions: Modify Scheduler
If you issue Actions: Remove, the Planned Activity will be deleted.
On a Planned Activity the following operations can be executed: see figure
Lock
Unlock
Figure 523. Modify schedule wizard

Scheduler modification
The operator can modify some attributes of the scheduler object.
The modification is admitted only if the job is not started; i.e. if the scheduler state is suspended or in
standBy state.
The mentioned condition is valid also for a periodic task, but with a further restriction: no single job already
executed; i.e. it never crossed the active state.
The attributes that can be modified are:
comment1; scheduleStartTime; maxExecutionDelay; schedulePriority; scheduleInterval; scheduleEnd-

Time.
Moreover the user can change the execution modality: from one shot to cyclic way and viceversa.
Remove (Scheduler deletion)
The operator can delete a scheduler objects. The object deletion implies also its log file removing.
Lock (Scheduler suspending)
The operator can suspend a scheduler in standBy state. The suspension is done setting the adminState
to locked value the schedState becomes suspended. The suspending action is useful for example when
the operator has to perform an action having any impact on the scheduler.
Unlock (Scheduler resuming)
The operator can resume a scheduler in suspended state, i.e. a locked scheduler. The suspension is done
setting the adminState to unlocked value the schedState becomes standBy.
Following figure shows the role of the max execution delay parameter in case of a locked/unlocked/locked
scheduler.
Tsusp = instant when the scheduler from idle becomes suspended
Tstart = Start date and time instant
Tres = instant when the scheduler from suspended becomes resumed
If MaxExecutionDelay<(Tres-Tstart) (e.g. MED) AND (Tstart > Tsusp) the scheduled action is not per-
formed;

If MaxExecutionDelay>(Tres-Tstart) (e.g. MED) the scheduled action is started at the Tres instant.
Log showing
The operator can read the log files. This functionality is active only if the job is already started. In case
of periodic task the condition is: it exists at least a job already started.
The operator calling the SchedulerReportList inventory gets the file name(s) of the associated log file(s).
Clicking on a file name (i.e. syncScheduleName remote attribute), available on the output of the men-
tioned inventory, a new Java window appears and it contains the log file text.
The log file is composed by a multiple reply.

2.4 Network Modifications
2.4.1 Introduction
– Adding a Network Element to a SNCP Ring case
– Removing a Network Element from a SNCP Ring
– Add Q3 NE to a 2-F MS Spring
– Add QB3 STAR NE to a 2-F MS Spring
– Remove Q3 NE / Remove QB3 STAR NE from a 2-F MS Spring
– Add NE to a 4-Fiber NPE ring
– Remove NE from a 4-Fiber NPE ring
– Removing an SDH Tributary Board
– Configuration of a Transmux board
N.B. The execution of the Redo-Log file does not cause the allocation of the path/trail; however some
checks take into account the topological modifications:
– in case of node insertion the passthrough connection is added in the new node.
– in case of node remove the passthrough connection thorough the removed node is ignored.

2.4.1.1 Adding a Network Element (NE) to a SNCP ring
SCOPE
The scope of this procedure is to insert a NE into a SNCP ring.
CONDITIONS
The new Network Element must be inserted in the network as shown in Figure 524.
NE-2
NE-3
NE-1
NEW NETWORK ELEMENT
Figure 524. Adding a new Network Element to a SNCP ring
SEQUENCE
a) The user can protect paths using the physical connection to be interrupted (NE-1 Thorough NE-3).
The user can verify by means of the command Physical Connection: (display) Paths active in
physical connection which is the path actual route.
If traffic survivability is required, from the path list select all paths and protect them by means of Add
Protection: Spare. Verify, with reference to Figure 524.,that the upper route is working for all paths.
Execute the force operation to the upper route for all involved paths and verify that all paths have
been successfully forced and are operational.
b) Move all paths from the physical connection to be interrupted (NE-1 thorough NE-3)
1) For paths protected at above point a), select them and use option Remove Protection: Keeping
Spare.
2) For paths previously protected, reroute manually on the main or spare route according to the
route type crossing the physical connection.
c) If the node to be inserted is a QB3* node, put the node in download disable condition.
d) Execute the split physical connection procedure. See paragraph 2.3.45 on page 416.
e) If the node to be inserted is a QB3* node, put the node in download enable condition and execute
Global Download on QB3* NE.
– Remove the undesired protections and forced conditions.

2.4.1.2 Removing a Network Element (NE) from a SNCP ring
SCOPE
The scope of this procedure is to remove a Network Element from a SNCP ring.
CONDITIONS
The SNCP reference ring is shown in Figure 524.on page 469. Some paths are crossing the NE being
removed.
SEQUENCE
a) On the node issue the command Display: Paths active starting/ending from a node
b) The user can protect paths using the physical connection to be interrupted (NE-1 Through NE-3).
The user can verify by means of the command Physical Connection: (display) Paths active in
physical connection which is the path actual route.
If traffic survivability is required, from the path list select all paths and protect them by means of Add
Protection: Spare. Verify, with reference to Figure 524.,that the upper route is working for all paths.
Execute the force operation to the upper route for all involved paths and verify that all paths have
been successfully forced and are operational.
c) Move all paths from the physical connection to be interrupted (NE-1 thorough NE-3)
1) For paths protected at above point a), select them and use option Remove Protection: Keeping
Spare.
2) For paths previously protected, reroute manually on the main or spare route according to the
route type crossing the physical connection.
d) 1354RM
Execute the Join Physical Connection Procedure
2.4.1.3 Add Q3 NE to a 2-F MS Spring
SCOPE
The scope is to insert a Q3 NE into a 2-F MS Spring ring.
CONDITIONS
The ring is mixed, i.e. it contains Q3 NEs and QB3 STAR NEs.
SEQUENCE
a) Execute the Force Switch operation on adjacent protection blocks, where the new NE must be
inserted: Force West on one side and Force East on the other side.
The information of Node Position in ET and Node Id in ET can be displayed by issuing the Show/
Set Attributes command on the Protection Block.
b) Configure Download: Disable.
1) Execute the command Configure Download: Disable on QB3 STAR Network Elements.
2) Execute the command Configure Download: Disable on Q3 Network Elements.

3) Click twice on the physical connection group (line between the two nodes involved. The phys-
ical connection list opens.
Select the Physical Connection and issue Topology Modifications: Split Physical Connection.
Execute the split connection procedure.
c) Change the Run Level to Network Consistency. From the Process Monitor select Actions: Set Run
Level: 3 Ntw Consistency
d) Select all QB3 STAR NEs and execute Consistency Download: Global.
e) Change the Run Level to Full Functionality.
f) Enable the download on all QB3 STAR NEs
g) Enable the download on all Q3 NEs
DO NOT ENABLE THE DOWNLOAD ON THE INSERTED NE; THIS IS TO BE DONE LATER
h) Execute all cable unplug and plug operations NOW, before activating the MS Spring on the inserted
NE.
i) Enable the download on the inserted Q3 NE.
2.4.1.4 Add QB3 STAR NE to 2-F MS Spring
SCOPE
The scope is to insert a QB3 STAR NE into a 2-F MS Spring ring.
CONDITIONS
SEQUENCE
a) Execute the Force Switch operation on adjacent protection blocks, where the new NE must be
inserted: Force West on one side and Force East on the other side.
2) Execute the command Configure Download: Disable on QB3 STAR Network Elements and on
Q3 Network Elements
3) Click twice on the physical connection group (line between the two nodes involved. The phys-
ical connection submap opens. Select the physical connection and browse it by means of
Supervision: Browse: Object.
From the browser select the Physical Connection and issue Topology Modifications: Split Phys-
ical Connection.
c) Change the Run Level to Network Consistency. From the Process Monitor select Actions: Set Run

d) Select all QB3 STAR NEs and execute Consistency Download: Global.
e) Change the Run Level to Full Functionality.
f) Enable the download on all QB3 STAR NEs
g) Enable the download on all Q3 NEs
DO NOT ENABLE THE DOWNLOAD ON THE INSERTED NE; THIS IS TO BE DONE LATER
h) Execute all cable unplug and plug operations NOW, before activating the MS Spring on the inserted
NE.
i) Enable the download on the inserted QB3 Star NE.
j) Release switches
2.4.1.5 Remove Q3 NE / Remove QB3 STAR NE from a 2-F MS Spring
SCOPE
The scope is to remove a Q3 NE /QB3 STAR NE from a 2-F MS Spring ring.
CONDITIONS
SEQUENCE
a) Execute the Force Switch operation on adjacent protection blocks, where the NE must be removed
Force West on one side and Force East on the other side.
2) Execute the command Configure Download: Disable on Q3 Network Elements.
c) Disconnect the physical fibers from the node being removed.
d) Join physical connections
1) From the map click twice on the first physical connection group. The physical connection list
opens. Select the physical connection.
2) From the map click twice on the second physical connection group. The physical connection
list opens. Select the physical connection.
Select the two Physical Connections to join and issue Topology Modifications: Join Physical
Connection. Execute the join physical connection procedure.
e) Change the Run Level to Network Consistency. From the Process Monitor select Actions: Set Run
f) Select all QB3 STAR NEs and execute Consistency Download: Global.

g) Change the Run Level to Full Functionality.
h) Enable the download on all QB3 STAR NEs
i) Enable the download on all Q3 NEs
j) Execute all cable plug operations
k) Release all switches
2.4.1.6 Add NE to a 4-Fiber NPE ring
SCOPE
The scope is to add a NE to a 4-F MS Spring ring.
CONDITIONS
No protection is active (nor alarm neither command is active)
SEQUENCE
a) Set Download Disable mode on the node to be added
b) Execute the Split Physical Connection on the relevant Physical connection
c) Set Forced Ring Switch on the adjacent nodes
d) Remove the physical fibers SPARE between the nodes
e) Remove the physical fibers MAIN between the nodes
f) Set Download Enable mode on the node, which has just been inserted
g) Perform the physical fiber connections for the working fibers
h) Perform the physical fiber connections for the protecting fibers
i) Remove the Forced Ring Switch on the nodes adjacent to the inserted node
2.4.1.7 Remove NE from a 4-Fiber NPE ring
SCOPE
The scope is to remove a NE from a 4-F MS Spring ring.
CONDITIONS
No protection is active (nor alarm neither command is active)
SEQUENCE
a) Set Download Disable mode on the node to be removed
b) Execute the Join Physical Connection on the relevant Physical connections
c) Set Forced Ring Switch on the nodes adjacent to the node being removed
d) Remove the physical fibers from the node being removed, by respecting the following order:
1) remove RX spare

2) remove TX spare
3) remove RX main
4) remove TX main
e) Perform the physical fiber connections for the working fibers
f) Perform the physical fiber connections for the protecting fibers
g) Remove the Forced Ring Switch on the nodes which were adjacent to the removed node
h) Set Download Enable mode on the node, which has just been inserted
2.4.2 Remove Tributary Board
2.4.2.1 Remove a PDH Tributary Board
SCOPE
The scope is to remove a tributary board.
SEQUENCE
a) On the relevant NAP List verify that no path is using any trib. port of the board being removed i.e.
the nap idle indicator should be "Idle".
b) On the relevant NAP List select the NAP related to the trib. ports to be removed and issue the com-
mand Actions:Remove:Remove NAP. The relevant ports pass from Assigned to Observed.
c) On the 1353NM station delete the relevant board. The board is no longer present in the views.
d) In the NE port list the ports deleted are no longer present.
2.4.2.2 Removing an SDH Tributary Board
SEQUENCE
a) Select the physical connection associated to the SDH port to be removed.

b) Then select Display Related items: Paths in Physical Connection to verify that no path is using that
physical connection.
Should a path been using the involved physical connection, the path should be deimplemented/deal-
located or rerouted, if possible.
c) On the map delete the connection:
1) Deimplement the connection

2) Remove objects from RM
d) On the 1353NM station delete the relevant board. The board is no longer present in the views.

2.4.3 Configuration of a Transmux board
2.4.3.1 Payload Structure Configuration of a Transmux board
The payload configuration of a transmux board (VC-4 Synchronous to Plesiochronous) includes a

sequence of steps to execute on both 1354RM and 1353NM. Example which follows covers the config-
uration of a 140 Mb Port to 2Mb terminations.
a) On 1354RM: Remove the VC-4 NAP associated to the 140 Mb port. The detailed sequence is:
1) From browser point to the involved node and issue Actions: Display: Main related Items: NAPs.
2) The NAP list is displayed. Select the VC-4 NAP and issue Actions: Remove NAP.
3) the 140Mb port assignment status goes to OBSERVED.
4) Point to the Node and issue Actions: Display: Main Related Items: Ports. The Port List is dis-
played. The 140Mb port assignment status is OBSERVED.
b) On 1353SH: Execute the payload structure configuration to VC-12.
c) On 1354RM: Execute the EML: Synchronize command. The 140 Mb Port (OBSERVED) is replaced
by the 2 Mb ports (OBSERVED).
d) On 1354RM: Execute the Upload NAPs command. The detailed sequence is:
1) From browser point to the involved node and issue Actions: Configuration: Upload NAPs.
2) The user can display the uploaded NAPs, e.g. from browser, pointing to the node and issuing
the command Actions: Display: Main Related Items: NAPs. The NAP List now contains the VC-
12 TTPs (NAPs).
N.B. Configuring a TMUX board from one 34Mb port to 16 2Mb ports: The 'configure port' is done
on NM, then on RM a 'synch eml' and a 'upload NAPs' is performed.
Some problems occur if 'Upload NAPs' from RM is done immediately after getting all MUX
boards (synch eml).
On NM VC12 objects exist before all VC12 TPs have been configured on DXC. The result is
'misaligned ports' for all missing NAPs. A second 'Upload NAPs' which is performed some min-
utes later solves this misalignment.
2.4.3.2 Payload Structure Remove of a Transmux board
Example which follows covers the configuration of a 140 Mb Port from the 2Mb NAPs to one VC-4 TTP-
NAP.
a) On 1354RM: Remove the VC-12 NAPs associated to the 140 Mb port. The detailed sequence is:
1) From browser point to the involved node and issue Actions: Display: Main related Items: NAPs.
2) The NAP list is displayed. Select the VC-12 NAPs and issue Actions: Remove NAP.
3) Point to the Node and issue Actions: Display: Main Related Items: Ports. The Port List is dis-
played. The assignment status of the 64 2Mb ports is OBSERVED.
b) On 1353NM: Remove the payload structure configuration (from VC-12 to VC-4)
c) On 1354RM: Execute the EML: Synchronize command. The 2Mb Ports (OBSERVED) are replaced
by one 140 Mb port (OBSERVED)

2.5 Export of resources on ISN interface for 1355VPN
2.5.1 Introduction
The procedures which follow describe the export of resources to Virtual Private Network Management
system.
They are divided in:
• Adding a VPN initiator
• Add operator
• VPN assignment of the end points
• VPN assignment of the paths
• VPN assignment of the paths terminated outside an RM domain
2.5.1.1 Adding a VPN initiator
SEQUENCE
a) Select the Administration (SMF) icon from the vertical palette.

b) Select the feature Operator Administration and confirm by pressing OK.
c) From the Operator Administration Window select the option Add Initiator and confirm by pressing
OK. The Add Initiator window contains:
• the current Initiator list
• two textlines: RM Initiator and Initiator Name where the "Administrator" operator can digit the
RM Initiator (integer) and the Initiator Name (it must be unique in the file).
The Initiator Identifier must be given according to the following rules:
– VPN Initiators must have Identifier greater than 300
– The Identifier 301 is reserved for 1354NN (when present)
The Initiator Name is added to the possible values of the NAD attribute. The NAD attribute
is used to “mark” Network Resources (using the change NAD command) and to evaluate
Access Rules.
d) Enter the suitable RM Initiator and Initiator Name and select the rules to be associated. Click on
the Rule button. The list of the available rules opens. Each item of the list has a toggle button, i.e.
you can select many rules per each Initiator. The following rules can be selected:
• AC_R_VPN for Standard VPN Operators (not supported in this release)

• AC_R_EVPN for Enhanced VPN Operators
• AC_R_RVPN for Restricted VPN Operators
Click on the Add button to confirm the creation

2.5.1.2 Add Operator
SCOPE
This function allows the Administrator to create a new operator at a time on WSs belonging to the network
configuration.
SEQUENCE
a) Select the SMF icon from the vertical palette.

b) Select the feature Operator Administration and confirm by pressing OK.
c) From the Operator Administration window select the option Add Operator and confirm by pressing
OK. The Add Operator dialog window is presented.
d) Enter the required information, in particular:
– VPN Operator name. It is the same name which will be inserted by the VPN Administrator while
executing the VPN Handling procedure.
– Operator Profile: Path Builder
– Initiator: the Initiator Name previously specified at paragraph 2.5.1.1 on page 476.
e) A subsequent confirmation box containing all data relevant to the New Operator being created is pre-
sented. If you press OK the Operator is created. This dialog box also contains the button Abort to
abort the procedure.
f) you can confirm the Operator creation by pressing button Add.
The Add Operator window contains the following:
– The Header Area presents the function name: 'Add Operator';

– In the Work Area are present three sections:
WS filtering
• 1 listbox, selectable, which contains the list of defined WS;
• 1 couple of radiobuttons, with label: 'All WS' to select all WS on which to add operator, and
'Select WS' to allow selection from the listbox of WS;
• 1 button above the WS listbox, with label 'Apply' : it gives effect to WS selection for operator
creation, and filters the users list;
Data entering
• 1 listbox, unselectable, which contains the list of users existing on selected WS. The list is
equipped of an header indicating the composition of items line:
'WorkstationUsernameProfileReal Name''Initiator';
• 2 entries with labels: 'User name', 'Real Name';
• 1 pop-down menu for choosing among available profiles, with label 'Profiles';
• 1 pop-down menu for choosing among available initiators, with label 'Initiators';
• 2 entries for password definition: 'Password', 'Confirm Password';
Confirmations
• 2 buttons: 'Add' to create described operator, 'Close' to close the window and return to the
Main.

2.5.1.3 VPN assignment of the end points
2.5.1.3.1 NAP Assignment
SCOPE
The scope of this procedure is to assign the desired NAP to a certain NAD (Initiator Name), which cor-
responds to a certain RM Operator, which in turn will correspond to a certain VPN.
CONDITIONSThis assignment is required for all VPN types (Standard / Enhanced / Restricted)
SEQUENCE
1) Select the NAP(s) from the Nap list and issue the command NAD (Network Assignment
Domain): Change.
2) In the Change NAD dialog box select the icon dictionary. The NAD selection box opens. Select
the domain corresponding to the previously specified NAD (the Initiator Name mentioned at
paragraph2.5.1.1 and confirm by clicking on OK. Click again on OK of the dialog box.
2.5.1.3.2 Boundary CTP Assignment
SCOPE
The scope of this procedure is to assign the desired CTP to a certain NAD (Initiator Name), which cor-
responds to a certain RM Operator, which in turn will correspond to a certain VPN. To do so, it is required
to change the NAD of the link connection toward the virtual node.
CONDITIONSThis assignment can be executed for VPN types Standard and Enhanced
SEQUENCE
1) Select the link connection from the lc list and issue the command NAD (Network Assignment
Domain): Change.
paragraph 2.5.1.1 and confirm by clicking on OK. Click again on OK of the dialog box.
As a result of this operation, the boundary CTP is assigned to the above NAD.

2.5.1.4 VPN assignment of the bandwidth
2.5.1.4.1 Assignment of the link connection within an RM domain
SCOPE
The scope of this procedure is to assign the desired link connection to a certain NAD (Initiator Name),
which corresponds to a certain RM Operator, which in turn will correspond to a certain VPN.
CONDITIONSThis assignment can be executed for all VPN types (Standard / Enhanced / Restricted)
This assignment is MANDATORY for Restricted VPN
SEQUENCE
1) Select the NAP(s) from the Nap list and issue the command NAD (Network Assignment
Domain): Change.
paragraph 11.2 and confirm by clicking on OK. Click again on OK of the dialog box.
2.5.1.5 VPN assignment of the paths
2.5.1.5.1 VPN Assignment of paths terminated within an RM domain
SEQUENCE
1) Select the path(s) from the Path list and issue the command Actions: NAD (Network Assign-
ment Domain): Change.
paragraph 2.5.1.1 on page 476 and confirm by clicking on OK. Click again on OK of the dialog
box.
2.5.1.5.2 VPN Assignment of paths terminated outside an RM domain
SEQUENCE
1) Select the path(s) from the Path list and issue the command Actions: NAD (Network Assign-
ment Domain): Change.
paragraph 11.2 and confirm by clicking on OK. Click again on OK of the dialog box.
The NAP and the boundary CTP are not assigned automatically: the operator must execute the
procedures described at paragraphs 2.5.1.3.1 and 2.5.1.3.2 on page 478.
2.6 Statistics Tables

This feature is included in the delivery package only on Customer’s rquest.

It is not included in the standard delivery package.
2.6.1 Statistics Tables from Ntw, Sbn, Node

SCOPE
The scope of this procedure is to generate statistics tables to be used in network planning activities.
SEQUENCE
a) From browser point to the network and issue Network: Display Related Items. The selection box is
presented. See below figure.
Figure 525. Network: Display Related Items
b) You can select among:
– SDH CTPs statistics
– SDH PATHs statistics
– NAPs statistics
– NODEs statistics

c) If you start the search from the Subnetwork (1st or 2nd level), the available options are:
– NAPs statistics
– NODEs statistics
Figure 526. Subnetwork: Display Related Items
d) If you start the search from the Node, the available options are:
– NAPs statistics

Figure 527. Node: Display Related Items

2.6.1.1 SDH CTP Statistics table
Figure 528. SDH CTP Statistics
This table contains the following columns:
total no. of CTPs
path/trail indicator
rate
port name
node label
2nd level subnetwork name
1st level subnetwork name
network name

2.6.1.2 SDH PATHs statistics table
Figure 529. SDH PATHs statistics
total number
service rate
configuration state
2.6.1.3 NAPs statistics table
Figure 530. NAPs statistics
total number
idle indicator
NAP rate

node label
2nd level subnetwork name
1st level subnetwork name
network name
Figure 531. NODEs statistics
total number
type
site name

2.7 Topology structure change utilities
2.7.1 Move node from/to RM topologies

SCOPE
To move nodes from the source topology to a destination topology.
CONDITIONS
– no activities have to be in progress on the node to be moved.

– the working state of the node must be normal
– the working state of the source topologies in which the node is contained (ntw, sbn and et) must be
normal
– the working state of the destination topology in which the node has to be moved (ntw, sbn and et)
must be normal
– the working state of the involved physical connections must be NORMAL
N.B. Alternatively, the user can move nodes using dedicated scripts and an off-line tool, without inter-
action with the User Interface. See details in the 1354RM Administrator's Guide.
SEQUENCE
a) From the source map point to the node to move and issue Node: Modification: Move Node. The Move
node dialog box opens. See Figure 533.on page 487.
Figure 532. Node: Modification: Move Node

Figure 533. Move dialog box
b) From the Move dialog box click on button Selection of the Destination topology. The map opens in
selection modality.
c) Click twice on the network icon. The Network map opens.
Figure 534. Network Domain map opened in selection modality

Figure 535. Network map opened in selection modality
d) Click twice on the target subnetwork. The 2nd level subnetwork map opens.
Figure 536. 2nd level subnetwork map

e) Select the Destination topology and confirm by pressing button selection. The Destination topology
icon is present in the Move dialog box. See Figure 538.on page 489
Figure 537. Selection of the Destination topology
Figure 538. Move dialog box: command launch
f) Issue the Move command by clicking on Finish button. The moved node is present in the destination
submap in the New Object holding area.

Figure 539. Moved node in the New Object holding area
g) Drag the moved node from the New Object holding area to the center of the window. The connections
are drawn automatically.
Figure 540. Destination submap after the move operation
N.B. Multiple move operation is allowed. See below figure.

Figure 541. Multiple move operation

2.7.2 SPLIT OF VIRTUAL NE
SCOPE
The scope of this procedure is to split a virtual NE into more virtual NEs, in order to have a better display
of the paths and more clear representation of the network.
DESCRIPTION
To realize the split virtual NE into more virtual NEs, the concept of routing domain has been introduced.
The routing domain is a set of ports whose TP can be inter-connected. TPs inherit the routing domain of
the port they belong to.
With reference to below Figure 542., the path joining NAP A to NAP B makes use of two cross-connections
on the virtual node VIRTUAL. Our goal is to represent CROSS CONN 1 as belonging to virtual node VIR-
TUAL 1 and to represent CROSS CONN 2 as belonging to virtual node VIRTUAL NODE 2, as depicted
in Figure 543.
The means used to assign CROSS CONN 1 to virtual node VIRTUAL 1 and CROSS CONN 2 to VIRTUAL
NODE 2 is the new attribute ROUTING DOMAIN.
Then, a different routing domain will be assigned to the ports housing the TPs involved respectively in
CROSS CONN 1 and CROSS CONN 2. In the example shown in Figure 542., ports housing TP 1 + TP
2 will be assigned routing domain 1 and ports housing TP 3 + TP 4 will be assigned routing domain 2.
At this point ports housing TP 1 + TP 2 can be assigned to virtual node VIRTUAL NODE 1 and ports hous-
ing TP 3 + TP 4 can be moved to virtual node VIRTUAL NODE 2, thus obtaining the representation of Fig-
ure 543.
Obviously, virtual node VIRTUAL 1 and virtual node VIRTUAL NODE 2 represent real external equipment.
This subdivision must be done for ease of clarity.
NOTES ON THE PROCEDURE
The procedure is constituted by steps to be executed in sequence, some of them making use of the RM
graphical interface and others to be run off-line.
in particular, the assignment of the domains can be helped by launching an automatic algorithm, even if
the user's intervention is mostly required.
On the other hand, it is recommended to run the off-line tools FIND WRONG PATHS and FIX WRONG
PATHS, as they give a useful indication about the ports to move.
The procedure, as described in this document, applies to a single virtual NE.
It is assumed that no connection exist between real external nodes, as all paths have been created with
a suitable set of constraints. In other words the external (virtual) network acts mainly as interconnection
between adjacent rings.

VIRTUAL
NAP A
TP1
CROSS
CONN
1
TP2
TP3 CROSS
CONN
2
TP4
NAP B
Figure 542. Simplified example of actual network view

NAP A VIRTUAL 1
TP1
CROSS
CON
1
TP2
TP3 CROSS
CON
2
TP4
VIRTUAL2
NAP B
Figure 543. Network view after the split
SEQUENCE
a) Launch the Automatic calculation of the domains from the node. This step is optional but it is
suggested.
The procedure of automatic calculation of the domains causes the reset of the actual
domains, then can be executed only as the first step.
As a result of this step, each set of ports interconnected among them, or in the same NPA will be
marked by a distinct value of the attribute routing domain (numeric)
b) Manual assignment of the domains from the node.
This important step should be executed by the Customer, who knows the exact relationship
between the ports of the virtual NE and the real equipment (NEs) they belong to.

c) Set routingDomainStatus = enableForPartitioning on the involved nodes.
From this point on the new paths will be allocated correctly because the allocation algorithm takes
into account the routing domains. Cross-connections will be allocated only between ports
belonging to the same domain and /or with client ports (client=PDH, GMAU,...) of the domain 'free
pool' (NULL). The 'freePool' port will inherit the domain of the cross-connected port.
d) Paths off-line processing with routing domain
1) Find wrong paths
The objective of this off-line tool is to find paths wrongly represented. An example of wrongly
represented path is given in the following figure.
VIRTUAL
NAP A DOMAIN 1
TP
CROSS
CONN
1
TP
DOMAIN 2
CROSS
TP
CONN
2
TP
VIRTUAL2
NAP B
Figure 544. Example of wrongly represented path

This procedure finds out paths or trails crossing a virtual node via cross connections between dif-
ferent domains.
The output of this procedure is a list of wrongly represented paths.
The command to be entered to launch the procedure is:
/usr/Systems/1354RM_<nms_instance>/bin/findWrongPath <virtual node identifier>

[<wrong paths file name>]
where <wrong paths file> is the output file containing the list of wrong paths/trails.
It can be used in the fix wrong path procedure.
If not specified /tmp/wrongPath.lis is default value.
An example of list generated by the FIND WRONG PATHS procedure is show below
2006291 --- NODE ID, DO NOT DELETE THIS LINE

path 2119909 MILANO/TOW-POZZUOLI/L0I VC12S3
Two cases can arise:
a) In case the Find wrong paths procedure does not list any path, go to step e) on page
499.
b) In case the Find wrong paths procedure contains continue with following step 2)
N.B. Optionally, the user may edit the list of wrongly represented paths (only in particular cases)

2) Fix wrong paths
The scope of this procedure is to correct wrong paths or trails. Wrong cross connections within the
virtual node are removed and replaced by the correct ones. The initial situation is shown in Figure
544.
The final situation is shown in Figure 545.
The command to be entered to launch the procedure is:
/usr/Systems/1354RM_<nms_instance>/bin/fixWrongPath [<wrong paths file name>] [<log

file name>]
where <wrong paths file> is the input file produced by find wrong path procedure.
If not specified /tmp/wrongPath.lis is default value
<log file > is output file with detailed log informations.
If not specified /tmp/fixWrongPath.log is the default value
An example of the report generated by the FIX WRONG PATHS procedure is show below
WRONG PATH FILE: /tmp/wrongPath.lis

NODE ID : 2006291PATH ID: 2119909 USERLABEL: MILANO/TOW-POZZUOLI/L0I VC12S3
MAIN ROUTE
OK, 2 inconsistent cointos ADJUSTED
SPARE ROUTE
OK, 2 inconsistent cointos ADJUSTEDPATH ID: 2119917 USERLABEL: MILANO/TOW-POZZUOLI/L0I
VC12S5
MAIN ROUTE
cointo 4050664 is not pointToPoint.
Remove protection/service and retry

VIRTUAL
NAP A DOMAIN 1
TP
CROSS
CONN
1
TP
DOMAIN 2
TP CROSS
CONN
2
TP
VIRTUAL2
NAP B
Figure 545. Paths are correctly represented
Two cases can arise:
a) In case the Fix wrong paths procedure does not suggest any corrective action, go to
Find wrong paths, step 1) on page 495
b) In case the Fix wrong paths procedure suggest any corrective action, some actions on
the path should be executed, such as Remove Spare, followed by Add Spare.
Anyway, in particular cases, as an example for drop&cont paths, it is recommended to agree with Alcatel
Technical Assistance Center the best strategy, in order to avoid a degrade of service. Eventually set the
node to download disable, then enable the download after all changes have been entered.

e) Execute the Move of ports via graphical interface
f) It is suggested to run again, for checking purposes, the Find wrong paths, step 1) on page 495
2.7.2.1 Example
Figure 546.shows the actual network view taken as example, while Figure 547.the path list.
Figure 546. Actual network view
Figure 547. Path list

Figure 548. Path highlight
Path highlight and Path routing display are shown respectively in Figure 548.and Figure 549.

Figure 549. Path routing display

Path routing display info are summarized in Figure 550.(Actual Route)
Figure 550.shows both actual route and correct route.
B
C
ACTUAL
ROUTE
1
A
B
C
CORRECT
ROUTE
1
A
Figure 550. Actual route and correct route

2.7.2.2 Automatic calculation of the domains
a) Launch the Automatic calculation of the domains from the node. This step is optional but it is
suggested. From the Virtual node issue: Modification: Routing domain: Assign
Figure 551. Virtual node: Modification: Routing domain: Assign
b) Select AUTOMATIC and click on Apply. The report alerts that the operation is successfully termi-
nated.

Figure 552. Routing domain mng wizard: AUTOMATIC
Figure 553. Report
c) Display the port list with the Routing Domains assigned automatically. From the virtual node issue
Search: All Related Items: Ports

Figure 554. Virtual Node: Search: Items: Ports
Figure 555. Virtual node port list

d) The port list is displayed in Figure 555.
The assignment is wrong because port names (userlabel) having the same prefix should have same
domain. They don't. It is required a Manual assignment of the domains from the node

2.7.2.3 Manual assignment of the domains from the node
a) Execute the Manual assignment of the domains from the node.
b) From the Virtual node issue Modification: Routing domain: Assign
Figure 556. Virtual node: Modification: Routing domain: Assign

c) The Routing domain management wizard is presented.
Figure 557. Routing domain mng wizard
d) Option On selected ports is already selected. Click on Port list button.
e) Select the ports you want to change/assign the domain and click on Apply button.

f) The selected ports are now present in the wizard window. Insert the Routing Domain string (32-char-
acter alphanumeric) and click on Apply. The domain is assigned. Click on Erase button to clean the
window.
Figure 559. Insert the Routing Domain string

Figure 560. New routing domain name
g) Complete the assignment of the remaining ports:
1) Select the ports you want to change/assign the domain and click on Apply button.
2) The selected ports are now present in the wizard window. Insert the Routing Domain string and
click on Apply.

Figure 562. New routing domain name
2.7.2.4 Find/fix wrong paths
a) Set routingDomainStatus = enableForPartitioning on the involved nodes.

From this point on the new paths will be allocated correctly because the allocation algorithm takes
into account the routing domains. Cross-connections will be allocated only between ports
belonging to the same domain and /or with client ports (client=PDH, GMAU,...) of the domain 'free
pool' (NULL). The 'freePool' port will inherit the domain of the cross-connected port.
Figure 563. Modification: Routing domain: Enable/disable
Figure 564. Routing domain: Enabled for partitioning

b) Paths off-line processing with routing domain
1) Find wrong paths
NODE ID FILENAME
Figure 565. Find wrong paths
Figure 566. Find wrong paths execute notification
PATH ID PATH USERLABEL
Figure 567. Display the list of the wrong paths
2) Fix wrong paths
Figure 568. Fix wrong paths

Figure 569. Fix wrong paths execution notification
Figure 570. Fixed path routing,according to Figure 550.correct route

2.7.3 Move Ports of a Virtual Node
a) Set routingDomainStatus = enableForMigration on the involved nodes. From Virtual node issue
Modification: Routing domain: Enable/disable
Figure 571. Virtual node: Modification: Routing domain: Enable/Disable
b) In the selection box choose Enabled for migration
Figure 572. Enabled for migration

c) Start the move of the ports. From the Virtual node issue: Modification: Move: Ports
Figure 573. Virtual node: Modification: Move: Ports
Figure 574. NE migration wizard step 1

d) Click on next button.
The target node must be reachable, equipped and the NAPs must be in the OBSERVED state,
i.e. the NAPs have not to be uploaded.
e) Drag and drop from the map or from browser the destination node, where to move the ports.

f) Click on Next
g) Ports are grouped into domains.Select the domain to move and click on the right arrow. Ports to
move will maintain their name. It is also possible to modify the name by entering the desired name
in the suitable textline.
Figure 578. Ports assigned to the destination node
h) Click on Next

Figure 579. Confirm move operation
i) Confirm the move operation by clicking on OK button. The action report is displayed.
Figure 580. Action report

j) Check on the map that the split has been successful.
k) You may also locate the path and verify that has been correctly rerouted.
Figure 581. Network map after the split
Figure 582. Path locate

2.7.4 Move Ports (Real Node)
Ì Only SDH and PDH ports can be moved. N.A. for Ethernet ports.
SCOPE
The scope of this procedure is to move ports from one node to another node. Physical connections and
relevant traffic are moved too. The final goal is to replace one or more existing NE/s with another one.
Figure 583. Network map and path highlight
With reference to above figure, ports of nodes C and B must move to node A.
a) Select from the map the involved nodes and issue Actions: Configure Download: Disable

Figure 584. Actions: Configure Download: Disable (for the involved nodes)
b) Point to Node C and issue: Modification: Routing domain: Assign
Figure 585. Node C: Modification: Routing domain: Assign
c) In the Routing domain mng wizard enter the new domain and click on Apply

Figure 586. Routing domain mng: enter new domain
d) For node B do the same Routing domain: Assignment as already done for node C in steps b) and
c) above.
Figure 587. Routing domain mng: enter new domain

e) Node C: Modification: Routing Domain: Enable/Disable. See Figure 588.The Routing domain state
selection box is displayed. See Figure 589.Set Routing domain state= enabled for migration and click
on Apply.
f) The same operations specified at above point e) for Node C must be executed for Node B.
Figure 588. Node C: Modification: Routing Domain: Enable/Disable
Figure 589. Routing domain state: enabled for migration

g) Point from the map to node C and issue Modification: Move: Ports. The NE migration wizard step1
is displayed. See Figure 591.
Figure 590. Node C: Modification: Move: Ports
Figure 591. NE migration wizard step1

h) Drag &drop the destination node. Click on Next button.
Figure 592. NE migration wizard step2 (drag &drop the destination node)
i) The list of the selectable ports on the destination NE can be displayed by opening the pop-up menu
per each port. See below figure.
j) Select the destination port where to move the source port. See Figure 593.and Figure 594.
Figure 593. NE migration wizard step 3: selection of the destination port

Figure 594. NE migration wizard step 4: destination port assignment
k) Execute the assignment of all ports
Figure 595. NE migration wizard: all ports assigned

Figure 596. Confirmation box
l) As a result, now ports/connections are moved from node C to node A
Figure 597. Ports/connections moved from node C to node A
m) Point from the map to node B and issue Modification: Move: Ports. The NE migration wizard step1
is displayed. See Figure 599.

Figure 598. Node B: Modification: Move: Ports
Figure 599. NE migration wizard step2 (drag &drop the destination node)

n) The list of the selectable ports on the destination NE can be displayed by opening the pop-up menu
per each port.
o) Select the destination port where to move the source port. Click on Next button and subsequently
do the confirmation.
Figure 600. NE migration wizard: destination port assigned
Figure 601. Ports/connections moved from node B to node A

p) As a result, now ports/connections are moved from node C to node A
q) Issue Actions: Configure Download: Enable (for the involved nodes)
Figure 602. Actions: Configure Download: Enable (for the involved nodes)
r) New path highlight is shown in below figure

Figure 603. Path highlight
2.7.5 Conversion planned/real ports

SCOPE
On a given real node, the scope is to convert a planned port into a real port or a real port into an other
real port. This is useful e.g. in case the user moved a port (via NE port moving) from a node to an other
node with real port not yet installed.
In this case the port should be moved to a planned port. Then, after real port installation, the planned port
can be converted to real. The feature is traffic impacting.
CONDITIONS
The node must be a real node and not QB3*.
The procedure can be applied with the node either in download enable mode or in download disable mode.
In both cases, it is traffic impacting, but, operating in download disabled mode, the user can prepare the
RM MIB and modify the cables only before passing to download enabled mode
SEQUENCE
a) Select the real node and starts the convert planned/real port command.

Figure 604. Node: Modification: Move: Convert Planned/real port
b) The wizard starts, presenting in the source port column, the list of ports available in the node

Figure 605. Convert Planned/real port step 1
PLANNED
BUTTON
Figure 606. Convert Planned/real port step 2

c) Select from the source port list the port to convert:
1) If the selected port is a planned one, the real ports available in the node are listed in the des-
tination port column. Select the destination port.
2) If the selected source port is a real port, select the type of target port, i.e. planned or real
in case of planned port type, the port label must be entered.
in case of real port type, the list of the other real ports available in the node in the destination
port column is provided. The user can then select the destination port.
OPERATION
After the confirmation, the system performs the following steps:
-the node is temporary locked
-the physical connections and the related objects are migrated
-the involved paths and trails are migrated
Figure 607. Destination port selected

Figure 608. Action log

2.8 SDH Network Take Over
This paragraph gives a technical overview on the 1354RM 7.4 capability SDH Network Take Over.
The reader of such document is assumed to be familiar with 1354RM conventions.
Changes done vs the previous iteration can be highlighted enabling trace changes Word tool.
For any comment/remark on this document, please contact Stefano.Molaschi@alcatel.it
2.8.1 SDH Network Take Over Description
1354RM Network upload is a capability designed in order to cut human effort in populating the 1354RM
database in case of already deployed/operational network, managed at1353NM level only.
Network upload is also targeted to support operators to fully realign the 1354RM database against the
actual network configuration as soon as the 1354RM has recovered the supervision of the network after
a period of supervision-down. In this case a global resynchronization procedure helps operators in achiev-
ing again the full alignment.
For both of the previous applications, Network upload feature allows to shorten and ease human oper-
ations, implementing a set of capabilities, which reduce time-consuming and error-prone manual activi-
ties. Nevertheless to achieve full manageability of uploaded information, some manual intervention is
needed, (e.g. setting trail/path user labels, etc.).
Network upload capability is composed by a set of features (as described in the following), covering the
discovery of the following resources:
SDH physical connections
MS Protections
HO trails and paths
LO paths
The Network upload activities have to be applied in a correct sequence; Alcatel Operation Support Doc-
umentation shall be followed by the operator in order to assure that no traffic impacts are caused by the
use of such functions. Direct Alcatel support is advisable in this step. At each step a proper follow-up and
double check is to be performed.
More in details, user defined info (as user labels) has to be set. Performing double checks on 1354RM
DB consistency against network configuration is also advisable; 1354RM offers Mark Audit feature to do
this.
Mark Audit capability can be applied on a-per-NE-basis (download disabled mode); the Audit report con-
tains the list of NE misaligned resources.
1354RM Users are also able to identify which of the misaligned resources can cause traffic impact in case
1354RM downloads its own configuration (i.e. cross connection, paths trace). So the operator can man-
ually apply the proper actions at 1354RM level before performing a forced download onto the NE.
For the non-traffic-impacting misaligned items, 1354RM Users can either choose to align 1354RM DB or
force 1354RM values into the involved NEs.
2.8.1.2 General Restrictions
No 4F-MSPring take over support

No customized Alarm Severity Assignment Profile take over.
No threshold profiles take over.
No Performance Monitoring setting and data take over.

2.8.1.3 SDH Connectivity Take Over
2.8.1.4 Description
This feature allows to automatically discover the physical connectivity of the network, relying on the Trace
Identifier (J0).
Two different ways are available:
fully automatic: 1354RM generates unique sent J0 and builds the physical connections based on
the received values.
partially automatic: the sent/expected J0 values are set by the CT/1353NM operator when a fiber
is put in service and 1354RM simply re-uses this information to upload the connectivity
Two commands are available to the User:
Automatic generation of J0. The automatic generation of J0 has to be foreseen for a set of ports
or for all the port belonging to a NE. The User has to select the 1354RM entity (single port, node,
network, 1st level sub-network or 2nd level sub-network) and to choose the Automatic generation
of Trace Identifier command. As a result of the command, the sent value of J0 is generated for the
selected port or for all the ports belong to the selected topology, only if no value has not already be
set (the 1354RM is only overwriting the default value).
Upload connectivity. The upload of the connectivity is foreseen to discover, basing on J0 values,
the physical connection between two ports. The User has to select the 1354RM entity (single port,
node, network, 1st level sub-network or 2nd level sub-network) and to choose the Configuration/
Upload Physical Connectivity command. As a result of the command, the physical connections are
automatically created for the selected port or for all the ports belong to the selected topology.
When a physical connection is created, if the sentTraceId / expectedTraceId values are set, the values
are kept
When a physical connection is deleted:
• if the sentTraceId value has been automatically generated by 1354RM, the sentTraceId, the
expectedTraceId and the enabledTraceId info are reset
• if the sentTraceId value has been set by the User, the sentTraceId, the expectedTraceId and
the enabledTraceId info are preserved
2.8.1.5 Restrictions
This feature can be applied only to physical connections delimited on both side by SDH Q3 NEs supporting
the Section Trace Identifier management (J0), which are (not exhaustive list):
1640fox >= 3.1

1642em >= 2.0
1660sm >= 3.1
1662smC >= 1.0
1664sm >= 3.3
1670sm >= 2.0b
1641sx >= 6.3-1CL1
1664sx >= 2.3-1CL1
1674sx >= 1.0
1678MCC >=2.0

2.8.2 Linear MSP Take Over
2.8.2.1 Description
This feature allows uploading of different kind of Linear Multiplex Section Protection scheme, as e.g. (1+1)
and (m:n).
The MSP schemes are used to provide a protection for working channels set up between two NEs. The
physical connections, which implement such scheme, should be already present in 1354RM database;
if not, it is possible to upload them in a previous step, selecting the involved NEs and using the Upload
Physical Connectivity command.
When a consistent MSP scheme is found, a new NPA (including the involved NEs and the related physical
connections) is created in 1354RM database. This NPA can also be automatically implemented if the User
has chosen this option.
The User has to select a topology (node, sub-network or network) and to choose the Configuration/Upload
Tools, Upload of Protection Schema/Liner MSP command. Then he has to provide the list of topologies
(node, sub-network and network) that has to be taken into account by the command.
Only MSP schemes between NEs contained in this list are examined.
The User can also set the implement option: if this is done, the discovered NPA, after the creation in
1354RM database, is implemented too.
For all the NEs contained in the provided topologies, a take over request is sent in order to discover the
presence of one or more MSP protection blocks. The returned response includes information about the
protection block characteristics and the list of protection units associated to it.
Starting from the ports contained in this list, a check is performed to verify the existence in 1354RM data-
base of the protecting and working physical connections defined between two NEs which implement a
MSP scheme. If one or more of these connections are not found, a message is sent to the User to suggest
the calling of the Upload Physical Connectivity command before to re-start the upload NPA command.
Also the protection blocks characteristics should be consistent. If not, an error message is sent to the User.
After these checks, for every discovered linear MSP scheme a configure NPA action is automatically sent
to create the related NPA in the 1354RM database. The action responses are directly displayed in the
upload NPA box at the User Interface. If the action ends correctly and the auto implement option is set,
the created NPA is implemented. If this option has not been chosen, the NPA can be manually imple-
mented by the User later on.
The feature can be applied only to couples of SDH Q3 NEs supporting the Linear MSP (i.e. it is not sup-
ported if at least one NE of couple is QB3*).

2.8.3 2f MS-SPRings Take Over
2.8.3.1 Description
The User can point to a topology and ask for the upload of 2f MS-SRings as it is done for linear MSP.
The physical connections, which implement such scheme, should be already present and implemented
in 1354RM database; if not, it is possible to upload them in a previous step, selecting the involved NEs
(they can be either Q3 or QB3*) and using the Upload Physical Connectivity command.
Warning: The network construction operations performed in download enabled mode could remove the
protection schemes from the NE.
The take-over starts taking the 2f MS-SPRing protection blocks uploaded in the topologies provided by
the User. When a consistent 2f MS-SPRing scheme is found, a new NPA (including the involved NEs and
the related physical connections) is created in 1354RM database.
The User has to select a topology (node, sub-network or network) and to choose the Configuration/Upload
Tools command. Then he has to provide the type of the take-over he wants to perform (Upload of Pro-
tection Schema/2f MS Spring) and the list of topologies (node, sub-network and network) that has to be
taken into account by the command.
Only 2f MS-SPRing schemes involving NEs contained in this list are examined.
The User can also set the auto implement option: if this is done, the uploaded NPA, after the creation in
1354RM database, is implemented too.
Warning: The cross-connections belong to paths crossing the 2f ring are not removed on the NE, but the
paths themselves are removed from the Squelching Table of the 2f ring. These paths are so no longer pro-
tected in the 2f ring. If the User wants to correct this situation, he should set the nodes in download disable
mode then execute the take-over of the 2f ring then also the take-over of the paths; only afterwards the
nodes can be set in download enable mode: during the download, because the paths are existing at
1354RM level, the squelch tables are not going to be modified.
Note: the states of the protection blocks are reported only when the 2F MS-SPRing NPA is implemented
AND the nodes are in download enable mode
None.

2.8.4 Paths and Trails Take Over
2.8.4.1 Description
The feature includes the possibility to point to a NAP, to a CTP or to a trail (physical, MS, HO) and to upload
the network connectivity if not defined in 1354RM. This includes also the take-over of the LO payload of
HO trails.
The feature allows the automatic creation (and the allocation, implementation and commissioning as well)
of paths/trails starting from the actual configuration of the NEs.
Warning: The network construction operations performed in download enabled mode could remove the
protection schemes from the NE.
The User has to choose the proper command and to provide one of the following information:
NAP
CTP
port
physical connection
link connection
topology (node, 1st and 2nd level sub-network, network)
As result of the-take over, the following operations are performed:
– the path/trail involving the provided information is created (allocated, implemented and commis-
sioned) inside the 1354RM DB
– If the take-over of one or more than one path/trail fails, the information is provided to the User in the
report message area of the command.
The Userhas to select the Path/trail take-over command (Tools item on the static tool bar) and to provide
one or more than one of the following entities that have to be taken into account by the command:
NAP
boundary/intermediate CTP
PDH/SDH port
physical connection
link connection
topology (node, 1st and 2nd level sub-network, network)
The User has also to provide the target Configuration State for the uploaded path/trail (allocated, imple-
mented and commissioned) can also start the Path/trail take-over command from one or more NAPs or
CTPs.
The created path/trail has the following characteristics:

the User label of the created path/trail is automatically calculated by the system
the ASAP profiles of the involved TPs are not uploaded
the info of the created path/trail are set according to the following:
• path Type, path Rate and protection Type according to the information retrieved from the NE
• alarm Propagation Rule is set to whenImplemented
• pdh Alarm Enabling Rule and sdh Alarm Enabling Rule are set to onImplementation
• pm Automatic is set to true (the PM related to the created path/trail are started according to the
1354RM rules)
• other info are set to the 1354RM default values

N.B. if the option Show found path/trail is selected, a window is opened as soon as the takeover oper-
ation begins but ignore the displayed error message Nothing found; the paths are going to be
displayed in the opened window when found during the takeover is running.
The feature is applicable only to point-to-point unprotected or SNCP paths/trails. It is not possible to obtain
a SNCP Drop&Continue paths. For QB3* NEs only bidirectional paths are supported. The take-over of
ethernet path (virtually concatenated or not) is not available. It is not possible to obtain an X path if the
main and the spare route are completely disjointed; in this case, two paths will be created.
There are particular configurations that the take-over process is not able to manage or it should be chosen
how to manage them (e.g. because there are different possible choices). In particular:
– 140Mb transport not-terminated on both sides are handled as paths (and not as trails)
– unidirectional paths with only two legs ending on two different nodes (or on a single virtual node) are
treated as broadcast (and not as Y paths)
– SNCP paths/trails that have two branches ending on the same External-Network are automatically
closed by the system on a single NAP (i.e. they are not treated as an Y path or trail)
– SNCP paths/trails not-terminated on both sides (even if terminated with bridge&switch connections
on the real NEs), cannot be recognized as they are (i.e. as an X paths) and are thus uploaded as
two separate paths
– paths terminated by two PDH ports are treated as PDH paths, even if they can also be of ATM type
(ATM paths can have two, one or no ATM ports)
– concatenated path are created only if all physical connections the path is using have the correct con-
catenation configuration
2.8.5 Overview on the operational procedures for take over

In the following the high level description of the sequence of the operations, which are to be performed
by the 1354RM User for achieving take over.
2.8.6 Complete SDH Network take over

In the following the description of the procedure for achieving the complete SDH Network take over.
In case also the WDM network takeover is needed/required it can be done, using all the 1354RM capa-
bilities (already available starting from NR 6.3 on), after the successful completion of the overall SDH net-
work take over.
In the following envisaged procedure describes how to take over the complete network splitting this activ-
ity per layers; as soon as the previous step is successfully completed the next one can take place (the
complete network take over split per network partitioning is not considered reliable and effective, because
trail/path take over cannot succeed if all the relevant supporting MS and physical resources have been
properly discovered).
It is worth to mention that:
it is important to minimize as much as possible the intervention on the real network and for all the duration
of the complete network take over activity no provisioning on both 1353NM /CT is to be performed. For
most of the duration of the complete network take over the 1354RM is to be in download disable on all
the nodes
At this stage no configuration activities can be foreseen on a 1354RM off-line replica system (but possibly
the network structure partitioning).

2.8.6.1 Preconditions and general recommendations
Before starting the implementation of the complete Network take over, it is recommended to plan and
check accurately all the activities, which are to be performed in the proper sequence
Moreover:
• In case of network with NEs which do not support J0 Management, all the exiting SDH physical
connections are to be identified (by telecom Planning Department) with the relevant information
(e.g. user label, A-end and Z-end port/node)
• All the exiting Linear MSP delimited by at least a QB3* NE are to be identified (by telecom Plan-
ning Department) with the relevant information (e.g. user label, A-end and Z-end port/node)
• To plan (together with the telecom Planning Department) the definitions in 1354RM of the Net-
work(s), 1st level sub-network, 1st level sub-networks, external networks,
• In case Linear MSP are foreseen between a Q3 NE and a QB3* one an External Network is
to be foreseen, in order to terminate 2 SDH Physical connections (Linear MS Protected)
towards the Q3 NE and to terminate on 1 (protected) SDH Physical Connection towards the
QB3* NE.
• To check that NE Group User labels and NE ones are unique in the overall network.
• To get from the telecom Planning Department the user labels (if any) of the Multiplex sections
HO trails and Paths.
• Configure in the1354RM off-line replica system the structure of the Network(s), 1st level sub-
network, 1st level sub-networks, external networks.
• Perform the data back-up of such 1354RM DB and restore it in the system in field.
All the NEs are to be reachable via DCN.
• No provisioning at all is allowed at 1353NM/CT level during the network takeover
• Each step can be executed only if the previous one is completely successful (i.e. checking the
results of the operation and taking the proper actions to recover possible errors).
2.8.6.2 Operations to be applied to the Physical Layer
– Stop and restart each EMLIM QB3* (in order to allow to 1354RM to upload of QB3* NEs with the
related SDH and PDH ports)
– Synchronize EML Domain (in order to allow to 1354RM to upload the Q3 NEs with the related SDH
and PDH ports)
– For each partitioning level identify the QB3*/Q3 NEs to be contained and create the corresponding
nodes, WITHOUT automatic upload option enabled for avoiding the NE DB scratch; it is worth to
remind that 1354RM 7.4 can allow default setting change (this 1354RM capability can be used for
such purpose in order to make more reliable this operation)
– Create/check all the needed External Networks; create and implement with the option Preserve con-
catenation set to True (when relevant) the physical connections with the external networks
– Set J0 sent (by means of Automatic generation of Trace Identifier command) on all the SDH ports,
which belong to NEs supporting such feature and do not have yet configured such info (scope to be
provided by the User is Network Level)

– Put all the Q3 nodes of the network in download disabled mode, i.e. 1354RM is not allowed to set/
change any NE configuration
– Put all EML Domain QB3* in download disabled mode, i.e. 1354RM is not allowed to set/change any
QB3* NE configuration
– Perform the Upload Physical Connectivity command in an ordered way for each network topology
(scope to be provided by the User is Network Level)
– Implement all the discovered Physical Connections
– List for each node the observed SDH ports (i.e. not yet involved in a physical connection; for each
of this create the real physical connection towards the corresponding NE or the relevant external Net-
works (creating it if not existing) create and implement with the option Preserve concatenation set
to True (when relevant) the physical connections with the external networks
– Create the physical connections terminated by QB3* NE (this operation scratch the NE configuration
in 1353NM)
– Stop all the EMLIM QB3* on 1353NM
– Repeat this operation till all the SDH ports are involved in a Physical connection
– Change from assigned to observed for all the QB3* NEs
– Start EMLIM QB3* on 1353NM
– For each QB3* NE perform align up on 1353NM (to align the 1353NM DB to the QB3* configuration)
– Stop EMLIM QB3* on 1353NM
– Change from observed to assigned for all the QB3* NEs
– Start EMLIM QB3* on 1353NM
– From the network level, upload all the NAPs
2.8.6.3 Operations to be applied to the Multiplex Section Layer
After the successful completion of the previous phase:
– Perform the Upload of Protection Schema/Liner MSP command (with Implement option) in an
ordered way for each network topology (scope to be provided by the User is Network Level)
– Create in 1354RM the remaining not uploaded Linear MSP schemes (e. g. the ones terminated by
at least one QB3*)
– Perform the Upload of Protection Schema/2f MS Spring command (with Implement option) in an
ordered way for each network topology (scope to be provided by the User is Network Level)
2.8.6.4 Operations to be applied to the Path Layer
From the Network Level: Path take over for each NAP and each border CTP not yet involved in a con-
nectivity
N.B. in this way the HO Trails, which do not yet support LO Paths, are not discovered (it is worth to
notice that this case should be not so frequent. TBC how to solve this problem (it is possible
anyway to detect such problem in mark audit phase.

N.B. if the path/trail takeover operation started from a big topology, e.g. subnetwork - does not find
all the paths, repeat the operation starting from a more delimited object (node, physical con-
nection, CTP or NAP).
2.8.6.5 Final Operations
Consistency audit on all the NEs of the managed network on at least traffic affecting info (this is a very
time consuming activity, is there any mean to reduce in reliable way the execution time)
For each QB3* NE perform the MIB compare between 1353NM DB and the NE one
If problems (e.g. misalignments in cross-connection domain), analyze and fix them
If no problems, enable the download on all the nodes
2.8.7 Take over of specific SDH Paths/Trails

In the following the description of the procedure for achieving take over of specific Paths and Trails created
at 1353NM/CT.
It is worth to notice that such way of working is not recommended; in fact as soon as 1354RM is deployed
and it is fully operational, all the network operations are to be done by 1354RM User (and not by the
1353NM one). In fact when a NE is take in charge by 1354RM the regular 1353NM User cannot perform
provisioning activities on most of the transmission resources)
This procedure can be performed in download enabled mode for all the nodes.
2.8.7.1 Preconditions and general recommendations
The ending NAPs/border CTPs (HO-CAPs) of the newly created paths (HO Trails) should be known by
1354RM User
Each step can be executed only if the previous one is completely successful (i.e. checking the results of
the operation and taking the proper actions to recover possible errors).
2.8.7.2 Operations to be applied to the Path Layer
Path take over starting from for the relevant NAPs (CAP) and border LO CTPs connectivity check via Path
Trace for each new path
2.8.8 Resources managed by 1354RM

The ITU-T G.805 client-server relationship concepts are taken into account.
1354RM is able to manage the following layers for:
SDH Networks:
• Physical and Regeneration Section (RS)
• Multiplex Section (MS)
• Higher Order Path (HOPL)
• Lower Order Path (LOPL)
In the following some simplified definitions of the resources managed by 1354RM (formal descriptions of
a lot them are available in G.803, G.805)

Topological Components
Network: It represents the highest level of partitioning managed by 1354RM. A path that crosses two Net-
works cannot be managed by 1354RM as a single transport entity (i.e. it will be represented with two
paths)
1st level Subnetwork: It represents the second level of partitioning (i.e. a Network can be composed by
more than one sub-networks)
2nd level Subnetwork:It represents the third level of partitioning.
Node: It represents a partition of a Network Element.
Physical Connection: It is the logical representation of fibers and coaxial cables, between network ports
Example: The physical connection delimited by to SDH ports.
Physical Resources
EML Domain: It represents one EMLIM component of 1353NM.
NE:It represents a physical NE.
Network port: It represents the physical port where e.g. the fiber is connected. Example: A STM-16 port
of a SDH NE.
Access port: It represents the physical port where the client signal is added/dropped. Example: A PDH
port (e.g 140 Mbit/s Port) present in a SDH NE.
Transport Entities
MS Trail: It is a trail at Optical Multiplex Section Layer. Example: MS-Trail is between two SDH ports of
two adjacent SDH NEs.
HO Trail: An HO Trail is an infrastructure pipe between two (either adjacent or not) SDH NEs. It is delimited
by two CAPs (Client Access Points) and it can support optical client paths.
Path: A path (can be at either HO or LO path layer) is a route established in the SDH/SONET network.
It is delimited by NAPs (Network Access Points). Example: A VC-12 path delimited by two VC-12 NAPs
Link Connection: It is an arc delimited by the two CTPs with the same timeslot and it is supported by the
same server Trail. Example: An Au-4 Link Connection is delimited by two corresponding AU-4 CTPs and
it supported by a MS-Trail.
Reference Points
NAP (Network Access Point): It terminates a path; one Network Access Point is associated to one
access port. Example: A VC-3 NAP (can be called also VC-3 TTP) is associated to a 34 Mbit/s port (or
a 45 Mbit/s port) and it terminates VC-3 path).
CAP (Client Access Point): It terminates a HO-Trail; one CAP can support Lower Order CTPs.
Example: A VC-4 CAP can support TU-12 and/or TU-3 CTPs (depending how the payload has been con-
figured); it terminates a VC-4 HO-Trail.
CTP (Connection Termination Point): It is an intermediate point and, depending on NE capabilities, it

can provide non-intrusive monitoring functionalities in term of alarms and Performance Monitoring. Exam-
ple: An AU4-16c CTP delimits an AU4-16c link connection.

2.9 Protection Analyzer Tool
2.9.1 Tool Description

The aim of protection analyzer tool is to analyze path and trails in order to find potential single point of
failure. Not only the SNCP protection implemented at path rate are taken into account, but also the pro-
tections at server layers (linear MSP protections, 2F MS-Spring, protected HO trails).
The tool can be applied either to a single path or to a set of paths or to the entire network
The paths with the following service types are analyzed (the transport network is only SDH):
· PDH
· Ethernet
· DATA
· SDH
N.B. The analysis is not performed on WDM networks.
2.9.2 How to run the tool

Connect to 1354RM Master machine (the tool must run on RM master!).
Run the following command:
> runProtectionAnalyzer.sh
The following graphical user interface is opened:
Figure 609. Protection Analyzer Interface

2.9.3 Analyze a single path
In order to analyze a single path the user has to specify:
1. "Check one path/trail" option: filed Input file name is grayed and not editable.
2. Select the type of the object to be analyzed (path/trail)
3. Specify the identifier of the chosen object
4. Specify the output file (complete path) name where the results have to be put. Not that this name
will be completed by the string "_<number>.csv".
5. Press "Execute" button
For example if the user wants to analyze path with identifier 33117:
Figure 610. Analyze path example
After performing the analysis the tool produces the following outputs:
1. a csv file named <output file>_1.csv. Looking at the previous example the output file is /tmp/
path33117Analysis_1.csv
2. a new window that shows the analysis results for the specified object is shown
Figure 611. Analysis results
This view will be explained in section 2.5.

2.9.4 Analyze the entire network
In order to analyze the whole database:
1. "Check whole network" option: fields Object, Identifier, Input file name, Output file name are grayed
and not editable.
Figure 612. Check whole network option
Note that output file name is forced to SingleFailureAnalysisResult and cannot be changed: one or more
files SingleFailureAnalysisResult_xxx.csv will be saved in the current directory.
Note that the complete database analysis should take a long time depending on the amount of paths/trails
contained.
At the end of the analysis, no window will be opened because of the large amount of data that can be
retrieved. In this case, in order to analyze the results the user can click on "Filter results" button (see Fil-
tering results section).
2.9.5 Analyze a subset of paths/trails

In order to analyze a subset of paths/trails:
1. "Check paths/trails from file list" option: fields Object and Identifier are grayed and not editable.
2. Specify the input file name (complete path) containing the paths/trails labels in the following format:
trail "Milan - Rome 123"
path "London - Paris 001"
path "London - Paris 011"

Figure 613. Analyze a subset of paths/trails
Note that this operation should take a long time depending on the amount of paths/trails requested inside
the input file and output file name is cannot be changed.
At the end of the analysis, no window will be opened because of the large amount of data that can be
retrieved. In this case, in order to analyze the results the user can click on "Filter results" button (see Fil-
tering results section).
2.9.6 Filtering results

After performing the path analysis, results can be retrieve by clicking on button "Filter results" of the pro-
tection analyzer main window. In order to start the filtering results application the Output file name must
be specified using the same rules explained in 2.1.
Figure 614. Filter results
The user is allowed to specify the filtering criteria among the following:

- Path/trail id.
If Object selected is path then the path with the given identifier is searched.
If Object selected is trail then the trail with the given identifier is searched.
If no Object is specified the tool looks for both path and trail with the given identifier.
- Path/trail label.
If Object selected is path then the path with the given userlabel is searched.
If Object selected is trail then the trail with the given userlabel is searched.
If no Object is specified the tool looks for both path and trail with the given userlabel.
- Physical connection id. The tool looks for paths/trails impacted by the given physical connection
identifier.
- Physical connection label. The tool looks for paths/trails impacted by the given physical connection
userlabel.
- HO trail id. The tool looks for paths/trails impacted by the given server trail identifier.
- HO link connection id. The tool looks for paths/trails impacted by the given HO link connection iden-
tifier.
Then he must specify the filtering value and click on action button "Apply filter"
The results are presented in a window like the following.
Figure 615. Filtering Results
2.9.6.1 How to understand results
Each row of the previous table represents a single point of failure for a given path/trail.
Column TYPE describes the type of the object impacted (path or trail), and column id and userlabel its
identifier and label.
Column RATE is meaningful only for paths and represents the path rate.
Column RISK describes the type of problem that can occur to the impacted object. It may ranges among
the following values:

Ø Loose traffic: it means that a failure on the specified physical connection may lead to traffic losses
Ø None (fully protected): this means that the path/trail is fully protected, then no single point of failure
is present. In this case the following columns are empty.
Ø Bandwidth reduced: it is possible only for virtual concatenated paths and this means that a failure
on the specified physical connection may lead the path to work with only a subset of server trails carrying
traffic. In this case column VCG will report the identifier of the server trail impacted by the problem and
CHNUM contains the channel number of this server trail.
Under PHYSICAL CONNECTION group column ID and USERLABEL columns describe the physical con-
nection identifier and label that may generate the failure when damaged.
Column virt conc group id and channel number are meaningful only for virtual concatenated paths and
represent the identifier of the supporting trail and its channel number.
Column leg number is meaningful for broadcast paths only and reports the leg number impacted by the
failure.
Column LO link connection is meaningful only for LO paths or server trails and reports the impacted LO
link connection identifier impacted by the failure.
Column HO trail is meaningful only for LO paths or server trails and reports the impacted HO server trail
identifier impacted by the failure.
Column HO link connection reports the impacted HO link connection identifier impacted by the failure
2.9.7 Export entire network analysis to Excel

Since the tool generates CSV files, they can be transferred to a PC and then opened for example with
MS Excel. Using the excel file $NXNL_PRD/bin/Export_SingleFailureAnalysis_Result.xls it is possible to
open these CSV files with a predefined style that allows automatic filtering.
See the following example

Figure 616. CSV files on Excel
Steps necessary to open this file:
On Windows machine:
1. Create a directory where output files have to be placed
2. transfer to this directory output CSV files from RM Master machine
3. transfer to this directory $NXNL_PRD/bin/Export_SingleFailureAnalysis_Result.xls
4. export environment variable PROT_AN_DIR = <output files directory complete path>
5. open file Export_SingleFailureAnalysis_Result.xls and choose "enable macros" option when

requested by MS Excel. Then, all the files saved will be open in different sheets of the same worksheet
and automatic filtering will be enabled. The file generated is automatically saved and named
SingleFailureAnalysisResult_final.xls.

3 Maintenance
3.1 Introduction
• Fault Management
• Diagnostic
• Consistency
• Maintenance Tracing
• Protection Management
• Performance Monitoring
• Test Ports
• Logger
3.2 Fault Management

Alarm messages on elementary objects (nap, cap, ctp, port, mstp) are received from EML, processed and
propagated to the affected objects.
These alarms are propagated to the following objects:
a) Transport entities (link connection, trail, path)
b) Topological object (node, subnetwork, network)
Alarms are generated on paths, Physical Connections, Trails (both HO and MS).
Elementary Alarms are received from EML layer and processed by RM in order to determine the RM object
to be marked as faulty (RM Object Impacted). RM provides for the impacted object the Alarm Severity,
the Operational State and the Probable Cause.
SEN-IM and TSD-IM are the protocols, respectively used for QB3* and QB3 equipments, which describe
the EML to NML communication.
3.2.1 Elementary Alarms and RM Probable Causes

Elementary Alarms are described in the documentation of the Network Elements and in the documenta-
tion of the EML -NE.

Maintenance 3AL 61269 AAAA Issue 4 555/854
N.B. Transport Failure means that the path is not working end-to-end. The managed domain could
be not interested to this alarm if it is not interested to the end-to-end service. In this case, this
alarm can be squelched using an appropriate ASAP.
N.B. Transport Incoming Failure means that a failure is entering the managed domain. This alarm
alone does not tell if the end-to-end path works or not, it just tells that a wrong signal is entering.
The managed domain could be able to recover to the failure if the path is protected.
N.B. Transport Outgoing Failure means that the managed domain is providing to the outside at
least one flow that is in error. This alarm does not tell if the end-to-end path works or not. The
end-to-end path could be protected outside the managed domain in such a way that the failure
can be recovered.
N.B. Only when the path is not working end-to-end, the operational state of the path itself is set to
disable.
3.2.2 Alarm auto-Synchro after Flooding

The Alarm auto-Synchro after Flooding can be setup via Node Show/Set Attributes. In particular, in folder
Alarm set the last attribute.
Ì To render effective this functionality, the relevant FEP agent must be restarted.
Figure 617. Alarm auto-Synchro after Flooding
3.2.3 Alarm Enabling/Disabling

Alarms can be enabled or disabled only for TSD-IM Network Elements. For QB3* Network Elements only
the propagation of the selected alarms can be enabled / disabled at RM level.

556/854 3AL 61269 AAAA Issue 4 Maintenance
3.2.3.1 Q3 Alarm Enabling/Disabling
Q3 alarms can be enabled/disabled on the involved Network Element for a certain path.
SEQUENCE
a) On path creation
1) On path creation. The user can modify the following attributes:
• Client Alarm Enabling Rule (On Implementation/On Commissioning/Manual). For TSD-IM

equipments.
• Transport Alarm Enabling Rule (On Implementation/On Commissioning/Manual). For TSD-IM

equipments.
2) If the user, when creating the path, selects Alarm Enabling Rule: Manual, for this Path it will be
possible to enable / disable the involved alarms (from the Path List: menu Actions: Alarms: Con-
figuration: enable/disable for Client or Transport.
b) After path creation, from the Path List the user can modify the Client/Transport alarm enabling rule
by selecting the menu Actions: Alarms: Configuration: Client/Transport Enable/Disable rule, as in the
case of path creation.
c) A dialog box is presented, which allows the enabling rule selection by means of a dictionary.
Alarms on PDH ports, NAPs, boundary CTPs are enabled if the Client/Transport (Q3 only) Alarm
Enabling rule= on Implementation.
d) To verify the successful change of this values the user can issue a Show/Set Attributes on the
selected path. See Figure 618.
N.B. Q3 Alarms enabled means AIS, SSF and FERF enabled.
Q3 Alarms disabled means AIS, SSF and FERF disabled.
Q3 Alarms partially enabled means AIS and FERF enabled.
N.B. Q3 Alarm Enabling/Disabling is also available for HO trails:
from the HO Trail List the user can modify the Transport alarm enabling rule by selecting the
menu Actions: Alarms: Configuration: Transport Enable/Disable.

Figure 618. Path: Show/Set Attributes: alarm enabling
3.2.3.2 QB3* Enabling UPA on specific CTP/CAP
This includes the ability of RM to setup alarm propagation rules other than the default ones defined for
physical connections related to virtual elements or based on Line Systems / Radio Links. By default AIS
and UPA on CTPs are never received by RM and this prevents a correct alarm from being propagated
on not terminated paths.
To enable the UPA alarm you can enter the "Alarm enabling: LOP,EXBER,UPA command on the selected
CAP. See Figure 619.

Figure 619. CAP Alarm Enabling.
Figure 620. CAP: Show/Set Attributes

Figure 621. CAP: Show/Set Attributes: alarm enabling
3.2.3.3 Enable / Disable frame supervision alarm
This feature allows enabling and disabling frame supervision on bulk or structured PDH flows.
The operator can select a PDH port and execute the command to enable or disable the frame supervision.
The command is available on 1641SX (managed by WX 1.7.1) on configurable 140, 34, 2 Mbit/s PDH
ports.
By default the frame supervision alarm and the consequent action (AIS) are disabled.
3.2.3.4 ISDN-PRA alarm management
Refer to Section Operation. In particular see paragraph ISDN primary access management.
3.2.4 Alarm Severity Assignment Profile

RM Object Severity is the RM Object ALARMSTATUS field value, which depends on the correlated ASAP
(Alarm Severity Assignment Profile).
ASAP is managed for Physical Connections, MS-Trails, HO-Trails, paths.
The main operations relevant to ASAP are LIST, CREATE, CORRELATE and MODIFY.
3.2.4.1 ASAP list
The ASAP class is inserted under the Network Domain. From the browser the operator points with the
mouse to the Network Domain, issuing Search: Related Items: Alarm Profiles. The list of the current pro-
files is displayed. See Figure 622.as an example.

Figure 622. Alarm Profile List.
The severity can be "no alarm" if the alarm must not be emitted.
N.B. A default ASAP is available; when a path, a trail or a physical connection is created, the default
ASAP is assigned.
3.2.4.2 ASAP create
The user can create new ASAP's. The command is also available at the user interface from the path,
trail or physical connection views. The sequence is as follows:
1) From the browser point with the mouse to the Network Domain and issue the command Alarm:
Create Alarm Profile. The ASAP Creation dialog box is displayed. See Figure 623.
2) Enter via keyboard the ASAP userlabel and assign the suitable severity to the relevant probable
cause/s. Click on button Create to confirm the creation.
Figure 623. ASAP Creation dialog box.

3.2.4.3 ASAP correlate
A "correlation" action is available in order to assign a new ASAP to relevant objects. The command
is also available at the user interface from the path, trail or physical connection views. One of the
possible sequences is as follows:
1) Select the path/paths from path list and select Actions: Alarm: Management... as indicated in
the window shown in Figure 624.Figure 625.shows an other example. The object correlation
to an alarm profile dialog box is displayed (See Figure 626.on page 563). This dialog
box contains also the ASAP create button. See above paragraph 3.2.4.2 on page 561.
Figure 624. Correlating paths
Figure 625. Trail: Alarm: Management...

Figure 626. Object correlation to an alarm profile
2) Select the ASAP list button as can be seen from Figure 626.
The Alarm profile list window is presented (see Figure 627.on page 564).

Figure 627. Alarm profile list
3) Select the involved profile and click on button Apply. The selected ASAP icon is displayed in
the Correlate ASAP dialog box, as per Figure 628. Click on Next button to continue.

Figure 628. ASAP selected.
Figure 629. Auto Mode Disabled/Enabled

AUTO MODE button
The auto mode button can be set to enable or disable. This feature allows managing the auto mode
defined, according to ITU-T G.806, in the alarm port mode. This mode is supported by OMSN (Low Capac-
ity starting from release 4.3B and 1670SM starting from release 4.3) on SDH ports, PDH ports and on Eth-
ernet Gigabit ports.
A port, in terms of defect supervision, can be:
• Not monitored (i.e. the detected defects are never reported). In the current NE implementa-
tion, this is achieved by setting an appropriate ASAP able to disable the reporting
• Monitored (the detected defects are reported. This is achieved using an ASAP enabling the
reporting).
• Auto: the port is not monitored but waiting to go to the monitored state (provided the ASAP is
different than "no alarm"). The trigger to go from auto to monitored state is the first detection
of the signal (i.e. the clearing of the LOS defect) or a command from the NMS (e.g. RM).
The Auto state is initialized by means of a NMS command.
4) Click on Finish button.
3.2.4.4 ASAP modify
The user can modify a profile simply issuing a Show/Set Attributes of the profile. See Figure 630.
Figure 630. ASAP Profile attributes.
When a new ASAP is assigned to an object or the associated one is modified, the severity of alarms
present on the object is re-evaluated clearing the alarm and then generating the alarm with the new sever-
ity if different from “no alarm"
remSDHFailure alarm activation
By default this alarm is deactivated since the default ASAP sets it to notAlarmed. To activate it, a new
ASAP has to be created and correlated to the involved path.

3.2.4.5 Automatic alarm synchronization after a flooding alarm period for Q3 NE
The involved NE attribute is called autoAlarmSynchro, default value is Enabled. After a flooding alarm
period for Q3 NE, an automatic alarm synchronization is executed.

3.2.5 Object Alarm Propagation
The tables listed in the following, summarize the alarm propagation. Elementary Alarms are received from
EML layer and processed by RM in order to determine the RM object to be marked as faulty (RM Object
Impacted). RM provides for the impacted object the Alarm Severity, the Operational State and the Prob-
able Cause.

3.3 Integration of 1354RM with SEC Security Subsystem
3.3.1 Introduction
This Chapter deals about the following subjects:
– SEC Architecture on 1354RM System
– SEC Administration
– Alarm Access Configuration
3.3.1.1 SEC Architecture on 1354RM System
The SEC Subsystem is composed of two permanent processes:
– secim process, which is the agent of the Security Subsystem and keep all the informations related
to the users and the system. Secim process is running only on 1354RM-IM.
– lss process, which is a kind of gate for applications related to user Security profile. One lss process
is instantiated for each workstation/server belonging to the 1354RM system (1 for each presentation
and each IM).
These permanent processes are configured to automatically run after the installation.
The SEC integration on 1354RM, as a first step, is intended only for the integration of Security Manage-
ment within AS (Alarm Surveillance). This means that each 1354RM operator using AS is able to view/
manage only alarms coming from Network resources that it can manage.
In order to have inside SEC Subsystem all the informations concerning Security, SEC is also integrated
in SMF, in order to get informations related to new users, user removal, and initiator management. More-
over the integration of SEC in SMF is also related to the Backup operation. Each time a new Operator
backup is performed also SEC database is saved.
3.3.1.2 SEC Administration
SEC Subsystem is provided with a default customization for which on an RM is automatically configured
to run secim process if RM-IM and lss process for each kind of RM (IM|US.
The default configurations are put in the directory /usr/sec/1354RM_<NTWDOMAIN>.
In order to distinguish 1354RM SEC processes from the 1353SH ones the RM processes are called
<process_name>_1354RM_<NTWDOMAIN>.
The SEC configuration is also related to the automatic start of SEC process: in the /etc/inittab file is
inserted 1 line for each permanent SEC process. This line invokes the script
run_SECIM|LSS_1354RM_<NTWDOMAIN> that checks for SEC habilitation to run and launch the
secim|lss_1354RM_<NTWDOMAIN> process. The automatic start of SEC processes is set on run-level
4 that is the 1354RM run-level default. No checks are performed on the 1354RM effective run-level (it is
supposed to be 4).
During Operator Backup and Restore the SEC subsystem is stopped in order to add to the Operator Infor-
mations also Informations related to SEC. The actions related to SEC start and stop are automatically
launched by SMF.

If some problem occurs during SMF->Operator Administration and SEC DB is not updated by the changes
done on RM through the SMF, it is possible to launch the script as snml user:
/usr/sec/integration/script/alignsecdb
This procedure starts from the last successful SEC command and aligns the SEC DB to the actual RM
Security definitions.
If at login time the user is alerted by the Message Box:
Security for 1354RM_<NTWDOMAIN> is not activated. Please contact your System Administra-
tor, the problem is that the user is not defined in the SEC DB, or the SEC Subsystem has been stopped
(Restore proc.) or internal error.
N.B. If the Message doesn't say 1354RM it is belonging to the SEC installed for SH
RESTRICTIONS
SEC 5.0 doesn't manage the scheduling time. This means that if an user has a scheduled rule this rule
is applied everytime. This limitation is not due to the integration level but to the fact that SEC 5.0 doesn't
support it.
3.3.1.3 Alarm Access Configuration
Depending on 1354RM user definitions the following AS Access Rights are granted:
Where:
AS Access Rights means the AS accessibility in terms of AS Administration:
ADMIN: Users can invoke AS Administration and Synchronization
VIEW: Users can invoke AS Synchronization but cannot interact with AS Administration functionalities
Alarm Access Rights shows the Alarm accessibility rules that are allowed to user:
MGT: Users that have this capability, if allowed by the NAD Rule (see below), can manage accessible
alarms (acknowledgement)

Where:
Alarm AccessType shows the alarm accessibility
MGT means that user have the possibility to Acknowledge alarms (ManaGemenT)
RO means that user can only access alarms in a view mode (Read-Only)
The MGT Alarm Accessability is granted if allowed by the System Profile (previous table) otherwise (for
Look-Only users) is set to RO.
"X" show which alarm types that can be accessed by user with the corresponding NAD Rule associated
"X*" show alarm types (only marked with user NAD) that can be accessed by user with the corresponding
NAD Rule associated
In order to provide a flexible way to configure AS Access on Alarm the configuration file /usr/snml/conf/
sec/1354RM_Ruler is provided.
This file drives the user Access Rights definition in the SEC-DB and have to be changed before the SEC
installation in order to keep coherent user creations.
In particular in order to give to Look-Only users the possibility to manage all the Alarms without keeping
into account the RM Rule change the line:
System_Profile : LookOnly : ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,

ASHISTUSM_FAD@AsHistoricalUsm :
as follows:
System_Profile : LookOnly :ASCURUSM_ALARM_MANAGER_FAD@AsCurrentUsm,

ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm, ASHISTUSM_FAD@AsHistoricalUsm

On the other side, if the Look-Only users Accessability have to be extended to manage alarms depending
on 1354RM Access Rules (second table), change the line:

ASHISTUSM_FAD@AsHistoricalUsm :
as follows:

ASHISTUSM_FAD@AsHistoricalUsm : ASCURUSM_ALARM_MANAGER_FAD@AsCurrentUsm
3.3.2 Spurious alarm management on 1354RM

It is possible to avoid alarm generation for objects under testing.
3.3.2.1 New ASAP definition
Define a new ASAP setting the severity of all probable causes to Indeterminate. To do this perform the
following steps:
a) Start the browser.
b) Select the 1354RM icon.
c) Point with the mouse at the Network Domain and issue the command Alarm: Create Alarm Profile.
d) Fill User Label field with Indet_Alarm_Profile
e) Change to Indeterminate the severity associated to all the proposed probable causes.
f) Click on Create button.
3.3.2.2 Path Alarm Management
The following procedures describe how to manage paths in order to avoid that alarms on them are
reported to 1330AS while they are under test.
3.3.2.2.1 Naps view after path creation
a) The path has been created with Implementation Rule = User (default) and Propagation Rule = When
Implemented (default).
b) As soon as the path is created a new window is opened reporting the path icon with its Naps (Naps
View). Click on Alarm icon making available all the icons relevant for alarm management.
c) Select the path icon.
d) Select menu Actions: Alarm Management...; the correlation window is opened.

Figure 631. Alarm Management Icons
e) If in the ASAP space the Indet_Alarm_Profile is already present go to step h). (N.B. the ASAP pos-
sibly provided is not the ASAP currently associated to the path, but it is the last referred ASAP).
f) Click on “Alarm Profile list" button; the list of the available ASAP is provided.
g) Select the Indet_Alarm_Profile ASAP. Click on Apply.
h) Click on Next button, then on Finish button. At this point the path is correlated to the relevant ASAP.
i) Implement the path.
From this point in time on alarms are reported to the path and visible by means of 1354RM USM, but no
alarm on this path is reported to 1330AS. Tests can be performed on the path without affecting mainte-
nance people.
3.3.2.2.2 Path commissioning
a) From the Path List window select the relevant path.
b) Select menu Actions: Alarm Management...; the correlation window is opened.
c) If in the ASAP space the “default ASAP" is already present go to step f)
d) Click on “Alarm Profile list" button; the list of the available ASAP is provided.
e) Select the Indet_Alarm_Profile ASAP. Click on Apply.
f) Click on Next button, then on Finish button. At this point the path is correlated to the relevant ASAP.
g) At this point the path is correlated to the default ASAP. Since this point in time alarm on the path(s)
are reported also to 1330AS.
h) Commission the path.
3.3.2.3 HO-Trail Management
3.3.2.4 Trail creation
a) Set-up the trail setting Setup Rule = User (N.B. Default value is Automatic).
b) As soon as the trail is defined a new window is open (Paths in Trail View).

c) Open the pop-up menu on the trail icon (pressing right button of the mouse) and select the command
Alarms: Management... A new window is open (correlation wizard).
d) If the Indet_Alarm_Profile is already present within the correlation window go to step g).
e) Click on “Alarm Profile list button"; the list of the available ASAP is provided.
f) Select the Indet_Alarm_Profile ASAP. Click on Next button.
g) Click on Finish button. At this point the trail is correlated to the relevant ASAP.
h) Allocate the trail.
i) Implement the trail.
3.3.2.4.1 Trail commissioning
a) There is no explicit commissioning on HO-Trail. The scope of this phase is to cause the trail to report
alarms to 1330AS.
b) On the Trail list window (possibly filtered on HO-Trail) select the relevant trail(s).
c) Select the command Action->Alarms->Management...
d) A new window is open (correlation wizard).
e) If in the ASAP space the “default ASAP" is already present click on Next button and go to h).
f) Click on “Alarm Profile list" icon; the list of the available ASAP is provided.
g) Select the “default ASAP" and click on Next button. The ASAP icon is inserted into the correlation
window.
h) On the correlation window click on the icon “Finish" (the same as before). At this point the trail(s)
is(are) correlated to the default ASAP. From this point in time on alarms on trail(s) are reported also
to 1330AS.
3.3.2.5 Physical Link/MS-Trail Management
3.3.2.5.1 Physical Link/MS-Trail creation
a) Activate the Physical Connection; this action causes that alarms possibly present on it are imme-
diately reported to 1330AS too.
b) Navigate from Browser to the Physical Connection.
c) From the pop-up menu associated to the Physical Connection (on browser) select the command
Configuration: Implement to create the associated MS-Trail; this action causes that alarms possibly
present on the MS-Trail are immediately reported to 1330AS too.
The Physical connection implementation creates the MS-Trail(s)
d) From the pop-up menu associated to the Physical Connection select the command Display: All
Related Item.
e) Select MS-Trail within the box that is open.
f) Press No filter button; the associated MS-Trail is provided below the Physical connection.
g) From the pop-up menu associated to the Physical connection select the command Alarm: Manage-
ment; a new window is open (correlation window).

h) If in the ASAP space the Indet_Alarm_Profile is already present go to step m).
i) Click on “Alarm Profile list" button; the list of the available ASAP is provided)
j) Select the Indet_Alarm_Profile ASAP and click on the icon Next. The ASAP icon is inserted into the
correlation window
k) On the correlation window click on Finish button. At this point both the Physical Connection and the
MS-Trail are correlated to the relevant ASAP. Alarm possibly sent to 1330AS are automatically
cleared (but must be acknowledged by operator to make them disappear).
l) From the pop-up menu associated to the MS-Trail select the command Alarm->CorrelateAlarmPro-
file; the MS-Trail is added to the correlation window.
m) On the correlation window click on the icon “Start correlating all the specified objects". At this point
both the Physical Connection and the MS-Trail are correlated to the relevant ASAP. Alarm possibly
sent to 1330AS are automatically cleared (but must be acknowledged by operator to make them dis-
appear).
3.3.2.5.2 Physical Link/MS-Trail commissioning
There is no explicit commissioning of these entities. The mean of this phase is to cause both Physical Link
and MS-Trail to report alarms to 1330AS.
a) Put on the browser the relevant Physical Connection.

b) From the pop-up menu associated to the Physical Connection select the command Display->All
Related Item; select MS-Trail within the box that is opened and then No filter button; the associated
MS-Trail is provided below the Physical connection.
c) From the pop-up menu associated to the Physical connection select the command Alarm: Manage-
ment; a new window is open (correlation window).
d) Drag and drop the MS trail to the correlation window.
e) f in the ASAP space the “default ASAP" is already present go to step h)
f) Click on “Alarm Profile" icon; the list of the available ASAP is provided.
g) Select the “default ASAP" and click on the icon “Next". The ASAP icon is inserted into the correlation
window.
h) On the correlation window click on the icon “Finish". At this point both the Physical Connection and
the MS-Trail are correlated to the default ASAP. Alarm relevant for these entities are sent again to
1330AS.

3.4 INTRODUCTION TO MAINTENANCE
Maintenance operations consist of several functions that have to be executed following failures on the net-
work.
Note that the protection network comprises:
– Telecommunication network (Network Elements and physical connections)
– Control network consisting of 1354RM and 1353NM
– Data Communication Equipment (Routers and Bridges)
The maintenance operations inherent to the Routers and Bridges are described in the documentation of
the Routers and Bridges.
3.4.1 Alarm navigation and fault localization

The telecommunication network can bear various failures depending on the size of the resources.
The paths affected by a failure are automatically re-routed on the available route (spare or main).
Should a Network Element fully break-down, the system will attempt to reroute all paths crossing it.
Therefore, should one NE break-down, only local drop traffic would be lost.
The RM Operators control the network on the Workstation through the graphical interface.
The operator is informed on the telecommunication network alarms through:
– A1330AS application.
Notice that from 1354RM Rel.5.2.B on, alarms reported at 1330AS application are ONLY those
affecting the resources managed by the actually logged operator. This mainly applies to VPN
operators.
– the map displaying objects in different colors identifying the status
– the browser
The navigation from the Counter summary window is the first level maintenance procedure.
This procedure which is described in the following, applies to each row of the Counter summary window.
a) From the Counter summary window open the Alarm sublist clicking twice on the relevant row of the
Counter summary window. As an alternative select the row and issue the Sublist: Open pull-down
menu item. See Figure 632.

Figure 632. Counter summary window
The relevant Alarm sublist is presented. Figure 633.shows an example of Physical Connection Alarm
sublist.
Figure 633. Physical Connection Alarm sublist
b) Select the alarm from the sublist and navigate it by selecting the Navigation: External Application:
1354RM pull-down menu item.(See Figure 634.). A confirmation dialog box appears. Click on OK
to confirm.

Figure 634. Navigation: External Application: 1354RM.
3.4.1.1 Path in service
The Path alarm sublist is shown in Figure 635.
Figure 635. Path alarm sublist
For the Path object the Nap view window and relative navigation window is presented:

Figure 636. Path Naps view
The severity can be "no alarm" if the alarm must not be emitted.
An example of Alarms details is shown in Figure 637.
Figure 637. Path Alarm details

3.4.1.2 Physical link in service
For the Physical connection object the physical connection structure window is presented:
Figure 638. Physical connection structure window
Alarmed objects are marked by an alarm icon. By clicking on this icon a window is presented, which
gives details on the selected alarm. See Figure 639.
Figure 639. Alarm details window.

3.4.1.3 HO-trail in service
The HO-trail alarm sublist is shown in Figure 640.
Figure 640. HO-trail alarm sublist

For the HO-trail object the path in trail window and the relevant navigation window is presented:
Figure 641. Trail structure

Figure 642. Alarmed object list
Figure 643. Example of alarm detail

3.4.1.4 MS-trail in service
The MS-trail alarm sublist is shown in Figure 644.
Figure 644. MS Trail alarm sublist.
For the MS-trail object the physical connection structure and relative navigation window is presented:
Figure 645. MS-trail structure

Alarmed objects are marked by an alarm icon. By clicking on this icon, the Alarms details window is dis-
played. See Figure 646.
Figure 646. Alarm details.
3.4.1.5 OMS trail in service
Fro the OMS trail alarm sublist select the alarm and issue the navigation command. The OMS trail struc-
ture window is presented.
Figure 647. OMS trail structure

played.
3.4.1.6 OCH trail in service
From OCH trail alarm sublist select the alarm and perform the navigation.
The OCH trail structure window opens.
played.
3.4.1.7 EML
In the following is presented the Alarm processing sublist:
Figure 648. EML sublist
For Alarm processing (EML object), only the navigated object is presented in the browser window.
Figure 649. EML navigation

Figure 650. EML Show/Set Attributes
3.4.1.8 Client path in service
From the Client path alarm sublist select the alarm and open the navigation. The relevant client path rout-
ing view is displayed. See below figure.

Figure 651. Client path routing view
played.
Figure 652. Alarm detail list
3.4.1.9 NE
In the following is presented the Alarm processing sublist:
For Alarm processing (NE object), only the navigated object is presented in the browser window.
Figure 653. NE Alarm Sublist
Figure 654. NE Navigation

3.4.2 Navigation of alarmed transport objects at server layer
Starting from a path, trail or physical connection, it is possible to find the alarmed objects at server layer.
a) Point to the path and issue Search:All Related Items
Figure 655. Path 2Mb:Search:All Related Items
b) Select Alarmed Transport Objects at Server Layer and click on OK.
Figure 656. Alarmed Transport Objects at Server Layer
c) Analogously you can get the list of Alarmed Transport Objects from trail

Figure 657. List of Alarmed Transport Objects from trail
d) An example of list of Alarmed Transport Objects from trail is given below
Figure 658. List of Alarmed Transport Objects from trail
N.B. Alternatively, to get the list of Alarmed Transport Objects, you can click on the relevant
icon. See below figure

Figure 659. Alarmed Transport Objects icon
3.4.2.1 Alarmed Transport Objects for WDM network
In this example the navigation from an Alarmed Transport Object for WDM network is described. Fig-
ure which follows shows a WDM map
REAL WDM LAYER

(SERVER)
FICTITIOUS SDH PHYSCON
Figure 660. Example of WDM map
N.B. Notice that the SDH (fictitious) physical connection is automatically created (to adhere to the
info model), upon implementation of all WDM physical connections.
a) In this example, a SDH path from node T1 to node T2, is crossing the WDM server (said client path),
highlighted in the figure which follows

Figure 661. Highlight of the server WDM path (client path)
b) The list of Alarmed Transport Objects for the SDH path is given below
Figure 662. List of Alarmed Transport Objects from path in WDM network
N.B. For Ethernet path the List of Alarmed Transport Objects contains also the affected LO trails

3.4.3 Diagnostic of the main objects
This paragraph describes the diagnostic procedures to be executed for the main RM objects in case of
malfunction.
The objects are:
– path
– trail
– EML Domain
– NE
– Physical Connection
– SDH Port
– Subnetwork
– Node
– Payload
3.4.3.1 Diagnostic of the path
The path diagnostic concerns the following attributes:
– Path Alarm status
– Path working status
3.4.3.1.1 Path Alarm status
Regardless the path alarm status, navigate the path from the Alarm Counter Summary
N.B. The Path Alarm Status is Cleared if the path operational status is Enabled (In-Service), this
implies that a path using its spare route is not alarmed.
3.4.3.1.2 Path working status
The Path working status can be visualized on the Path List.

All the statuses whose description contains the "ing" suffix are of "the work-in-progress" type. Hence the
path is in this status only for a certain period of time; the path should assume the "Normal" condition when
a certain timeout has expired. This condition does not require the Operator's intervention. He must inter-
vene if one of the following conditions occurs:
– failed to Add Leg
– failed to Add Protection
– failed to Release Resources
– failed to Remove Leg
– failed to Remove Protection
– failed to Allocate

– failed to Deallocate
– failed to Implement
– failed to Deimplement
– failed to Align SNCPs
– failed to manage SNCPs
– failed to change SNCP Mode
– failed to connect
– failed to disconnect
3.4.3.1.3 Path: Failed to Add Leg
CONDITIONS The path involved is of the "broadcast" type. The Operator entered an Add Leg
command on the Path involved.
CAUSES Lack of resources
ACTIONS Verify the resources (physical connections and payload structure).Should the
path be protected, the protection can be removed and command Add Leg can
be entered again.
3.4.3.1.4 Path: Failed to Add Protection
CONDITIONS The path involved is of the "unprotected" type. The Operator entered command
Add Protection.
CAUSES Lack of resources, i.e. the "spare" resource corresponding to the "main" one is
not available.
ACTIONS Verify the resources (payload structure).
3.4.3.1.5 Path: Failed to Release Resources
CONDITIONS The Operator has entered an Add Protection or Remove Protection command
on the path.
CAUSES The cause is due to software latent errors.
ACTIONS Contact Alcatel Technical Assistance Center.
3.4.3.1.6 Path: Failed to Remove Leg
CONDITIONS The Operator has entered a Remove Leg command on a broadcast path.
CAUSES The cause may be due to the fact that the path section deimplementation has failed
(leg to be removed).
ACTIONS After having entered the command, perform an inspection at EML and NE layer level.
3.4.3.2 Path: Failed to Remove Protection
CONDITIONS The Operator has entered a Remove Protection command on the path.
CAUSES The two possible causes are:

1) if the command has been entered through the "With check" option, the
failed attempt to remove the protection may be due to the fact that the path
is utilizing the "spare" route.
2) if the command has been entered through the "No check" option, the failed
attempt to remove the protection is due to the unsuccessful spare route
deimplementation.
ACTIONS In the second case above described, inspect the EML and NE layers.

3.4.3.3 Path: Failed to Allocate
CONDITIONS The user enters a path allocation command.
CAUSES Lack of resources.
ACTIONS Execute a provisioning of the suitable resources.
NOTE For more detailed information refer to Chapter 3.5 PATH/TRAIL ALLO-
CATION FAILURES
3.4.3.4 Path: Failed to Deallocate
CONDITIONS The user entered a Path: Deallocation command.
CAUSES Software latent errors.
3.4.3.5 Path: Failed to Implement
CONDITIONS The user entered a Path Implementation command.
CAUSES The subordinate EML/NEs.
ACTIONS After having entered the command, inspect at EML and NE layer level.
3.4.3.6 Path: Failed to Deimplement
CONDITIONS The user entered a Path Deimplementation command.
ACTIONS After having entered the command, perform an inspection at EML and NE layer
level.
3.4.3.7 Path: Failed to Change SNCP Mode
CONDITIONS The Operator has previously entered a Set revertive/Set not revertive com-
mand on the SNCP Operation mode attribute.
level.
3.4.3.8 Path: Failed to Align SNCPs
CONDITIONS The operation has been automatically launched by the system which aligns the
paths and trails whose attribute is SNCP status=unknown. It can be launched
in a manual mode by the Operator via command Synchronize Switch on logi-
cally protected Path/trail/connInTopol.
CAUSES The problem is mainly at EML level or is a RM-EML communication problem.
ACTIONS
1) Identify the protected connection that has failed.

2) In the Browser navigate up to the EML level.

3.4.3.9 Path: Failed to manage SNCPs
CONDITIONS The Operator has requested an SNCP management (Forced Switch Main/
Spare/Lockout.
level.
3.4.3.10 Path: Failed to connect/disconnect
CONDITIONS The Operator has requested one of the following operations:
– HO trail join
– HO trail split
– HO trail connect/disconnect
– path connect/disconnect
CAUSES Data base misaligned
3.4.3.11 Diagnostic of the trail
The trail diagnostic concerns the following attributes:
– Alarm status
– Working status
3.4.3.11.1 Trail Alarm status
Regardless the trail alarm status, navigate the trail from the Alarm Counter Summary. See Paragr. 3.4.1
3.4.3.11.2 Trail working status
The Trail working status can be visualized on the Trail List.

All the statuses whose description contains the "ing" suffix are of "the work-in-progress" type. Hence the
trail is in this status only for a certain period of time; the trail should assume the "Normal" condition when
a certain timeout has expired. This condition does not require the Operator's intervention. He must inter-
vene if one of the following conditions occurs:
– failed to Add Protection
– failed to Release Resources
– failed to Remove Protection
– failed to Allocate
– failed to Deallocate
– failed to Deimplement

– failed to configure
– failed to Remove
– failed to Align SNCPs
– failed to manage SNCPs
– failed to change SNCP Mode
– failed to connect
– failed to disconnect
– failed to split
– failed to join
3.4.3.11.3 Trail: Failed to Add Protection
CONDITIONS The trail involved is of the "unprotected" type. The Operator entered command
Add Protection.
CAUSES Lack of resources, i.e. the "spare" resource corresponding to the "main" one is
not available.
ACTIONS Verify the resources (payload structure).
3.4.3.11.4 Trail: Failed to Release Resources
CONDITIONS The Operator has entered an Add Protection or Remove Protection command
on the trail.
CAUSES The cause is due to software latent errors.
3.4.3.11.5 Trail: Failed to Remove Protection
CONDITIONS The Operator has entered a Remove Protection command on the path.
CAUSES The two possible causes are:
1) if the command has been entered through the "With check" option, the
failed attempt to remove the protection may be due to the fact that the trail
is utilizing the "spare" route.
2) if the command has been entered through the "No check" option, the failed
attempt to remove the protection is due to the unsuccessful spare route
deimplementation.
ACTIONS In the second case above described, inspect the EML and NE layers.

3.4.3.11.6 Trail: Failed to Allocate
CONDITIONS The user enters a trail allocation command.
CAUSES Lack of resources.
ACTIONS Execute a provisioning of the suitable resources.
NOTE For more detailed information refer to Chapter 3.5 PATH/TRAIL ALLO-
CATION FAILURES
3.4.3.11.7 Trail: Failed to Deallocate
CONDITIONS The user entered a Path: Deallocation command.
CAUSES Software latent errors.
3.4.3.11.8 Trail: Failed to Implement
CONDITIONS The user entered a Path Implementation command.
ACTIONS After having entered the command, inspect at EML and NE layer level.
3.4.3.11.9 Trail: Failed to Deimplement
CONDITIONS The user entered a Path Deimplementation command.
level.
3.4.3.11.10 Trail: Failed to Change SNCP Mode
CONDITIONS The Operator has previously entered a Set revertive/Set not revertive com-
mand on the SNCP Operation mode attribute.
level.
3.4.3.11.11 Trail: Failed to Align SNCPs
CONDITIONS The operation has been automatically launched by the system which aligns the
paths and trails whose attribute is SNCP status=unknown. It can be launched
in a manual mode by the Operator via command Synchronize Switch on logi-
cally protected Path/trail/connInTopol.
CAUSES The problem is mainly at EML level or is a RM-EML communication problem.

ACTIONS
1) Identify the protected connection that has failed.

2) In the Browser navigate up to the EML level.
3.4.3.11.12 Trail: Failed to manage SNCPs
CONDITIONS The Operator has requested an SNCP management (Forced Switch Main/
Spare/Lockout.
level.
3.4.3.11.13 Trail: Failed to configure
CONDITIONS The working state is Fail to Configure.
CAUSES
1) Negative answer from EML: failed creation / connectivity object removal
2) Communication error received from EML. It may be due to a crash of EML.
3) Violation of the contraints on nodes (sometimes).
ACTIONS
1) Inspect the NM side in order to detect a possible NM-RM disalignment
2) Verify that EML is running and re-execute the payload configuration
3) Perform again payload configuration. Consult Event Logger and Addi-

tional Info. It may be necessary to launch the Consistency Download oper-
ation on the EML involved.
3.4.3.11.14 Trail: Failed to connect/disconnect
CONDITIONS The trail working status is Failed to connect/disconnect.
CAUSES One or more of the paths belonging to this trail is in the Fail to connect/discon-
nect status. This is due to data base misalignment.
3.4.3.11.15 Trail: Failed to join/split
CONDITIONS The user launched the trail join/split operation.
CAUSES From the multiple reply of the Event Logger it is possible to determine:
1) The operation was interrupted during a connect/disconnect phase.
2) The operation was interrupted during a configuration phase.
level.

3.4.3.12 EML Domain Diagnostic
3.4.3.12.1 EML Alarm status
Regardless the EML alarm status, navigate EML from the Alarm Counter Summary as described at para-
graph 3.4.1 .
As an alternative, from the Browser you can select the 1354RM icon and issue the command Actions: Dis-
play Main Related items: EML Domain.
The displayed object is blue if cannot be reached; otherwise it is green colored.
Furthermore the following attributes are presented:
– Alarms Aligned
– Alarms alignment. It can be: Normal, Failed, In progress. This attribute reflects the consequences
of the Synchronize command launched by the Operator.
– EML Domain Alignment
The conditions cited herebelow:
– EML not reachable
– EML Alarms Aligned false
– EML Alarms Alignment Failed
– EML Domain Alignment Failed
are described in the following.
3.4.3.12.2 EML Not Reachable
CONDITIONS blue EML= Not reachable
CAUSES
1) EML erroneously registered on the local registration file
2) EML processes not running
3) TCP-IP problems
ACTIONS
1) Verify the EML id on RM and NM.
2) Restart EML
3) Check the workstation physical connections. The last possible choice is

rebooting the workstations.

3.4.3.12.3 Alignment False/ Failed
CONDITIONS From Browser the attribute EML Alarms Aligned is false / the attribute EML
Alarms Alignment is Failed / the attribute EML Domain Alignment is Failed.
CAUSES The possible causes are indicated in the Event Logger.
ACTIONS
1) From Browser enter command EML Domain: Synchronize / Synchronize

Alarms.
2) If the Synchronize Operation fails, display the events associated to the

EML Domain object from the Event Logger.
The affected object inspection involves the NEs/ports whose attribute is
Consistency status= normal. Moreover compare the same attributes con-
sidering the values displayed on RM and those presented on NM/NE.
The Operator can now try to solve the problem at NE level utilizing the CT
(Craft Terminal) or the corresponding NM.
If the problem is not solved, launch Consistency Download on the NE
involved.
3.4.3.13 NE Diagnostic
The NE attributes displayed in the browser window are:
– Alarm status
– Consistency status. for TSD-IM ONLY.
The values to consider for diagnostic are:
• Not aligned.
• Failed to align
• Consistency Mismatch
– NE communication problems. for TSD-IM ONLY.
• NE unreachable.
– Configuration Download state
• Fail to Disable
• Fail to Enable
– EMLreachable. Refer to EML diagnostic.
– NE DB modified by CT. (for TSD-IM ONLY). The CT has been automatically enabled because of
isolation problem and some modifications have been made by the CT operator.
– Craft Terminal Access State. The possible values are:
• CT access granted=CT enabled+CTconnected

• CT access required=CT disabled+CTconnected
• CT not connected enabled
• CT access denied=CT disabled+CT not connected
– NE not EML aligned. for SEN-IM ONLY
• neNotEmlAligned_auditfailed
• neNotEmlAligned_misaligned
– Upload status. for TSD-IM ONLY.
• Not found=the NE is misaligned about physical objects, such as ports....
3.4.3.14 NE: Consistency Status=Not aligned ( TSD-IM ONLY)
CONDITIONS From Browser it is displayed as an icon
CAUSES The consistency download is probably disabled
ACTIONS Verify that the Consistency download is enabled. Then execute a consistency
download: (i.e. global) toward the NE.
NOTICE THAT FOR TSD_IM NE THE RUN LEVEL CHANGE TO EXECUTE THE CONSIS-
TENCY DOWNLOAD IS NOT REQUIRED.
3.4.3.15 NE: Consistency Status=Failed to Align (TSD-IM ONLY)
CAUSES Following an Audit operation a/some mismatches
ACTIONS Inspect the browser Error Log.
3.4.3.16 NE: Consistency Status=Consistency Mismatch (TSD-IM ONLY)
CAUSES The NE is probably unreachable.
ACTIONS Inspect the browser Error Log and eventually execute a consistency download:
(i.e. global) toward the NE
NOTICE THAT FOR TSD_IM NE THE RUN LEVEL CHANGE TO EXECUTE THE CONSIS-
TENCY DOWNLOAD IS NOT REQUIRED.

3.4.3.17 NE: NE Communication Problems: NE unreachable
CONDITIONS From Browser it is displayed as an icon.
CAUSES The NE did not answer following a certain operation executed by RM. (E.g. an
operation on a path, trail,...). The polling toward the NE is automatically started
and an automatic download is then executed.
ACTIONS Verify, by means of the Error Log the last operation executed on the involved
connectivity object of the NE.
3.4.3.18 NE Config. Download Status = fail to Disable / Enable
CONDITIONS From Browser it is displayed as a title
CAUSES Wrong answer from EML
ACTIONS Verify the EML layer
3.4.3.19 NE: NEnot EML Aligned_auditfailed / misaligned ( for SEN-IM ONLY)
CONDITIONS From Browser it is displayed as a title
CAUSES
1) EML/NE erroneously registered
3) TCP-IP problems
ACTIONS
1) Verify EML id/NE address
2) Restart EML
3) Verify the workstation physical connections
3.4.3.20 Physical connection diagnostic
3.4.3.20.1 PhysCon Alarm status
A physical connection failure is denoted by a color variation on the map.
Regardless the physical connection alarm status, navigate the path from the Alarm Counter Summary as
described at paragraph 3.4.1.
3.4.3.20.2 PhysCon Working status
The Physical Connection working status can be visualized on the Browser.
From Brower the diagnostic relevant attribute is Working State if it assumes the following values:
– Failed to Configure
– Failed to Implement
– Failed to Remove

All the object statuses, the description of which contains suffix "ing" are of the "work-in-progress" type and
as a consequence are temporary.
3.4.3.20.3 PhysCon Failed to Configure
CONDITIONS The working state is Fail to Configure. The user has previously started to modify
the payload.
CAUSES
1) Negative answer from EML: failed creation / connectivity object removal
2) Communication error received from EML. It may be due to a crash of EML.
3) Violation of the contraints on nodes (sometimes).
ACTIONS

3.4.3.20.4 PhysCon Failed to Implement
CONDITIONS The user has previously launched the Physical Connection Implementation
operation.
CAUSES
1) Negative answer from EML: connectivity object implementation failed.
2) Communication error
ACTIONS
2) Verify that EML is running and launch again the Physical Connection
Implementation operation.
3.4.3.20.5 PhysCon Failed to Remove
CONDITIONS The user has entered a "Delete" command from MIB
CAUSES
1) Negative answer from EML: object removal failed.
2) Communication error
ACTIONS
2) Verify that EML is running and launch again the Remove operation.

3.4.3.21 SDH Port Diagnostic
The SDH ports are displayed from Browser by utilizing command NE: Display Related Items: SDH Ports.
The attribute involved are
– Operational Status= disabled
– Consistency status (for SEN-IM ONLY). The values relevant to diagnostic are:
• Not found. The board has been extracted. Objects assigned to RM belong to this board. Verify
alarms on related objects at RM and NM level.
• Unknown. Communication problems at OS level.
– Upload status (for TSD-IM ONLY). The values relevant to diagnostic are:
• Not found. The board has been extracted. Objects assigned to RM belong to this board. Verify
alarms on related objects at RM and NM level.
• Wrong Communication problems at OS level.
3.4.3.21.1 SDH port disabled
CONDITIONS The icon displayed from the browser is distinguished by a bar and there is an
alarm icon near it.
CAUSES Hardware or connected signals
ACTIONS Inspect the port at hardware level.
3.4.3.22 SDH port Consistency status (for SEN-IM ONLY)=Not found
CONDITIONS This attribute is displayed by an icon in the browser
CAUSES The board has been extracted. Objects assigned to RM belong to this board.
ACTIONS Verify alarms on related objects at RM and NM level.
3.4.3.23 SDH port Consistency status (for SEN-IM ONLY)=Unknown
CAUSES Communication problems at OS level.
ACTIONS Verify the communication between OS. Refer to EML diagnostic.
3.4.3.24 SDH port Upload status (for TSD-IM ONLY)=Not found
CAUSES The board has been extracted. Objects assigned to RM belong to this board.
ACTIONS Verify alarms on related objects at RM and NM level.
3.4.3.25 SDH port Upload status (for TSD-IM ONLY)=Wrong
CAUSES Communication problems at OS level.

ACTIONS Verify the communication between OS. Refer to EML diagnostic.
3.4.3.26 Routing link diagnostics
The routing link diagnostic is intended as a verification of the values of counters displayed from Browser
and listed herebelow:
– Idle disabled. It informs on the idle, disabled link connections
– Busy disabled. It informs on the busy, disabled link connections.
The actions required are:
– display the disabled link connections
– continue the link connection diagnostic procedure.
3.4.3.27 Subnetwork diagnostic
The Subnetwork diagnostic concerns the Working status attribute when assumes the following values:
– failed to Remove
3.4.3.27.1 Subnetwork: Failed to Implement
CONDITIONS The user entered a Subnetwork Implementation command.
ACTIONS After having entered the command perform an inspection at EML and NE layer
level.
3.4.3.28 Subnetwork: Failed to Remove
CONDITIONS The user entered a Subnetwork Delete from MIB command.
ACTIONS After having entered the command perform an inspection at EML and NE layer
level.
3.4.3.29 Subnetwork diagnostic
A failure along the ring is denoted by a color variation in the map. In the Browser the attribute taken into
consideration for diagnostic is "Working State" if it assumes the following values:
– Failed to Configure
– Failed to Implement
– Failed to Remove
All the statuses whose description contains the "ing" suffix are of the "work-in-progress" type. Hence the
object is in this status only for a certain period of time.

3.4.3.29.1 Subnetwork Failed to Configure
CONDITIONS The Working state is "Failed to configure". The user has previously launched
the Payload Modify operation.
CAUSES
1) Negative answer from the NE: connectivity object creation/removal failed.
2) Communication error received from EML. It may be due to an EML crash.
3) Constraints violation on the nodes (in some cases).
ACTIONS

3.4.3.29.2 Subnetwork Failed to Implement
CONDITIONS The user has previously launched the "Ring Implementation" operation.
CAUSES
1) Negative answer from the NE: connectivity object implementation failed.
2) Communication error.
ACTIONS
2) Verify that EML is running and launch again the Implementation operation.
3.4.3.29.3 Subnetwork Failed to Remove
CONDITIONS The user has previously launched a Delete command from MIB.
CAUSES
ACTIONS
1) Inspect the NM side in order to detect a possible NM-RM disalignment.

3.4.3.30 Node diagnostic
A node failure is denoted by a color variation in the map. In the Browser the attributes considered for diag-
nostic are:
– CT access status:
– Working status:
• Failed to Remove
• Failed to Reset
• Failed to Activate MS Spring
– Reachable/Not reachable
3.4.3.30.1 Node Failed to Remove
CONDITIONS The user has previously launched a Delete Command from MIB.
CAUSES
ACTIONS
3.4.3.30.2 Node Failed to Reset
CONDITIONS The user has launched an Implementation command on the topology.

The command has been unsuccessful in that the NEs have not been reset.
CAUSES
1) Negative answer from EML.
ACTIONS
3.4.3.30.3 Node Failed to Activate MS spring
CONDITIONS The user has launched a Ring Implementation command.
CAUSES
1) Negative answer from EML: connectivity object implementation failed.
ACTIONS

3.4.3.30.4 Node Reachable/Not reachable
CONDITIONS blue NODE in the map= not reachable
CAUSES
1) NE address erroneously registered
3) TCP-IP problems
ACTIONS
1) Verify the NE addresses
2) Restart EML
3) Verify the workstation physical connections
3.4.3.31 Payload Configuration Diagnostic
3.4.3.31.1 Payload working status
The user issued a payload modify command. The payload modify command can be executed on:
• PhysConn
• HOlc
• HOtrail
The working state of the above listed objects is "Normal" after the successful completion of the config-
uration. The working state can be Fail to Configure for unsuccessful completion.
3.4.3.31.2 Fail to Configure
CONDITIONS One of the objects is Fail to Configure; this condition is propagated to its super-
ordinate object (e.g. the ET is the superordinate and the PhysConn is the sub-
ordinate).
ACTIONS Inspect the browser Show additional information to display the cause of the
problem and execute one of the following actions:
1) Execute again the payload modify command.
2) In case of data misalignment perform the consistency download on the

affected objects.

3.5 Path/Trail Allocation Failures
3.5.1 Introduction
Path/Trail allocation failures are localized in the browser Path/Trail list. Selecting the involved path/trail
and clicking on the Show Failure Information Tool button, the Netscape browser application starts and
displays all information relevant to the failure.
The failure identification tool is based on Internet technologies, such as HTML, Java programming lan-
guage and HTTP protocol.
The allocation failure of a path or trail is detected by the user by looking at the transport to allocate, whose
configuration state goes to Failed to allocate. This state is displayed in the path or trail list.
The information provided in case of allocation failure are summarized in Figure 663.on page 624, namely:
– OBSTACLES AND UNSATISFIED CONSTRAINTS are managed with the following structure:
• OBSTACLES. This problem type is described by a problem description which helps in solving
the problem.
• UNSATISFIED CONSTRAINTS. A Constraint List is provided, indicating the failed constraint(s)
• OBSTACLES AND UNSATISFIED CONSTRAINTS. Both Problem description and Constraint
List are provided.
– OTHER ERRORS are not described in detail. They indicate errors for which no further information
is provided.
For OBSTACLES AND UNSATISFIED CONSTRAINTS Problem description and Constraint List are pre-
sented with the support of a simple graphical representation of the path/trail routing.
The tool usage is described in the following paragraphs.
ALLOCATION FAILURE
OTHER
OBSTACLES AND
ERRORS
UNSATISFIED CONSTRAINTS
OBSTACLES
UNSATISFIED &
OBSTACLES UNSATISFIED
CONSTRAINTS
CONSTRAINTS
Figure 663. Allocation failure management

3.5.2 Allocation failure diagnostic
3.5.2.1 Show Failure information
SEQUENCE
a) Select the involved path/trail and click on the Show Failure Information Tool button. This button
is also present in the path/trail routing view. The Netscape browser application starts and displays
the Netscape Path/Trail allocation failure window. See paragraph 3.5.2.3
Figure 664. Path List

3.5.2.2 Obstacles and Unsatisfied Constraints
In case of Obstacles and Unsatisfied Constraints, the complete netscape view is provided.
SEQUENCE
a) Select the involved path/trail and click on the Show Failure Information Tool button. This button is
also present in the path/trail routing view. The Netscape browser application starts and displays the
Netscape Path/Trail allocation failure window. See Figure 665.herebelow.
Figure 665. Netscape Path/Trail allocation failure.

The Netscape Path/Trail allocation failure window shown in detail in Figure 667.on page 628. con-
tains the following frames:
Window title: Netscape Path/Trail allocation failure.
Failed object frame. It contains:
path/trail userlabel (name)
type (point to point or broadcast)
failure date
– failure time
– no. of failed legs (for broadcast paths only)
Figure 666. Failed Object frame
Problem Summary frame. See Figure 667. It contains:
frame title: PATH: path type or TRAIL
one row per each failed leg. The relevant leg number is shown in the left-hand column.
Each leg is described as:
End1 label (node+port) and End2 label (node+port)
PROBLEM TYPE, reference to the html Problem Detail frame. The following cases
are possible:
– NO PROBLEMS. This string can be present only in correspondence to the Main

route when PROBLEMS are present on the Spare route
– OBSTACLE PROBLEMS. The route cannot be completed because of a lack of

resources
– CONSTRAINTS PROBLEMS. The route cannot be completed because some

constraints cannot be satisfied
– OBSTACLE AND CONSTRAINTS PROBLEMS. Both obstacle and constraints

problems are present.
Two columns are displayable: MAIN (problems on the main route) and SPARE (problems
on the spare route, only for protected paths/trail)

Figure 667. Netscape Path Trail allocation failure: problem summary frame.
b) At this point you can select the problem type, or in case of unsatisfied constraints you can select the
constraint list. See Figure 668.herebelow.
Figure 668. ProblemType and Constraint list
1) If you click on the Problem Type, reference to the html Problem Detail frame (named OBSTA-
CLES and CONSTRAINTS PROBLEMS), the Problem Detail frame view will display the
selected leg. See Figure 671.on page 630.
The Problem Detail frame contains:
header (upper left-hand side), constituted by:
Leg no.,i.e. the selected leg number. This field is not present for point to point paths
ROUTE: End1 (node+port) and End2 (node+port)
route type: Main or Spare, followed by the PROBLEM TYPE
Failed routing display (left-hand side). It shows, per each row:
node icon (green triangle) with node name or link connection icon (yellow icon)
with link connection name: node A name - node B name - AU/TU pointer No.

Figure 669. Route display components.
END 1 name and END 2 name. See Figure 670.on page 629.
Figure 670. END 1 / END 2 termination point names.
Problem Type (yellow string which is the html reference to the Path/Trail allocation
failure description window of Figure 672.on page 630.

Figure 671. Problem Detail frame.
– From the Problem Detail frame of Figure 671.select the problem type. The Path/Trail allocation fail-
ure description window is displayed. See Figure 672.on page 630.
Figure 672. Netscape Path/Trail allocation failure description window.

The Path/Trail allocation failure description window contains:
Window title: Netscape Path/Trail allocation failure.
Failed object frame above described.
Problem Summary frame above described.
Generic Help on Allocation Failure. See Figure 673.on page 631. It contains a generic
description of the allocation failure.
A Main window reload button is present in this frame, allowing the operator to display the main
window.
Figure 673. Generic Help on allocation failure.
Problem description. See example in Figure 674.herebelow. It contains the detailed problem
description (Title and Explanation) of the problem and suggestions (Hints) how to solve the
problem.
Figure 674. Example of problem description
The different problem types are:
– NE Connection Not Supported
Explanation: The path/trail could not use a NE because it could not support a connection as
the one required.
Hints: If a constraint to use that NE has been set, try to remove it.
– NE Connection State Not Allowed
Explanation: The path/trail could not use a NE because it does not allow the connection with
the current set of connections already engaged.
Hints: Try to remove some other connection for this NE.

– Infinite Cost
Explanation: The routing algorithm has found a route which uses a routing link with infinite cost
Hints: Change the cost of the related physical connection
– No Free Link Connections
Explanation: The system tried to use a routing link without free link connections
Hints: Deallocate some paths/trails which use the same routing link or change the payload con-
figuration in order to create new link connections at the proper rate.
– Improper Payload Configuration
Explanation: No one hop routing link exists related to a physical connection. This can be due
to an improper payload configuration or to the presence of a user defined HO trail
Hints: Try to change the payload configuration or split the HO trail.
– Unsatisfied Constraints
Explanation: One or more of the constraints given to the path/trail cannot be satisfied
Hints: The only way to allocate the path/trail is to remove/modify some constraints
The left hand side frame contains the Problem menu list. Each menu item, if selected, will display its prob-
lem explanation and some hints to solve it.
PROBLEM MENU
Figure 675. Problem menu list
Figure 676.and Figure 677.herebelow display an example of protected path allocation failure.

Figure 676. Example of display of a protected path

Figure 677. Example of display of a protected path

2) If you click on the Constraint List icon, as per Figure 668.on page 628, the Constrain List is pre-
sented. See Figure 678.on page 635. Per each leg its Constraint List can be displayed in case
of Unsatisfied Constraints.
Figure 678. Constraint List
An example of Constraint List is shown in Figure 679.on page 636.

Figure 679. Processed Constraint List.
This graphical table contains one row per each constraint. The table is constituted by : (see Figure 679.)
– title: PROCESSED CONSTRAINTS LIST (route), where route is equal to Main or Spare
– four columns, namely:
satisfied/unsatisfied constraint. The green semaphore icon means that the constraint is satis-
fied. The red semaphore icon means that the constraint is not satisfied. In the latter case the
deletion of this constraint will probably solve the allocation problem.
constraint usage in the main route. The one-way icon means USE while the no entry icon
means NOT USE.
constraint usage in the spare route. The one-way icon means USE while the no entry icon
means NOT USE.
topology used as constraint. It includes the icon and the userlabel of the topological object
An example of interpretation of some rows is given in Figure 680.on page 637

Figure 680. Examples of interpretation of the Constraint list rows.
3.5.2.3 Other errors
OTHER ERRORS are not described in detail, no other information is provided for this kind of errors.
An example of other error display is shown in Figure 681.herebelow.

Figure 681. Example of OTHER ERRROR display

3.6 Join / Split Trail Failure
3.6.1 Joint / Split HO-Trails

The Split / Joint Physical Connections and HO-Trails are part of a suit of tools for Network Modification.
3.6.1.1 Split a HO-Trail
A given HO-Trail crossing at HO a Node can be split in order to perform crossing at LO. This enables the
usage of LO resources in the splitting Node.
The operation reproduces in the splitting node the same payload structure of the starting trail.
The operation can be performed after the split of a Physical Connection.
Input to the operation is the HO-Trail to split.
From the user point of view, the split trail operation consists of 2 phases:
a) the user specifies the trail to split: RM checks in which nodes of the trail the split can be performed
(i.e. nodes where LO capability is available, nodes not belonging to protected parts of the trail...) and
prompts to the user the list of these nodes; no other action is accomplished by RM neither in RM MIB
nor in the NEs;
b) the user selects the splitting node and the operation can be executed.

– the old HO-Trail is deleted
– two new HO-Trails are created
– The LO-Paths "crossing" the splitting Node are modified by adding LO pass-through connection. The
related protection indexes are updated.
splitting node.
The operation reduces the impacts on the existing traffic: the LO-Paths client of the involved HO trails are
disconnected only for the time necessary to perform the operation: only the segment of network between
the end nodes of the involved HO trails is affected.
3.6.1.2 Join two HO-Trails
Two HO-Trails entering in a given NE can be joined in order to reduce the LO usage of resources.
Inputs to the procedure are :

– the HO-Trails to join.
RM performs the following checks:

– the 2 HO Trails must have the same payload structure;
– it must be possible to create a HO connection in the intermediate node;
– all LO-paths using the original HO-Trails are crossing with pass-through connections the interme-
diate NE without LO time-slot interchange.

– the old HO-Trails are deleted
– the new HO-Trail is created

– the LO-Paths "crossing" the original HO-Trails are modified by removing the pass-through connec-
tions in the intermediate NE. The related protection indexes are updated.
intermediate node.
The operation reduces the impacts on the existing traffic: LO-Paths client of the involved HO trails are dis-
connected only for the time necessary to perform the operation and only in the segment of network
between the end nodes of the involved HO trails.
3.6.1.2.1 Description of the operations
Both split and join HO Trails are complex operations: they are composed of elementary operations (pay-
load configuration, trail implementation,...), as described in the following state diagram.
A
disconnect client paths connect client paths
from 1W to 4 E from 1W to 4E
B
deconfigure trail A configure trail A
deconfigure trail B configure trail B
C
deimplement conn 2 of trail A implement trail A
deimplement conn 2 of trail B implement trail B
D
JOIN join trails A,B into C split trail C into A,B SPLIT
E
implement trail C deimplement conn 2 of trail A
F
configure trail C deconfigure trail C
G
connect client paths disconnect client paths
from 1W to 4 E from 1W to 4E
H
Figure 682. state diagram
The join trails is an operation that changes the state from A to H, passing through intermediate states.
The split trails is an operation that changes the state from H to A, passing through intermediate states.
The states are described below.
– state A (see below): HO trails A and B are implemented and LO configured; some LO LCs (e.g. LC
A and B) and their CTPs are busy because they belong to a path; LO CTPs in the transit node 2 are
connected with point-to-point connections in topology without time-slot interchange; these connec-
tions can be allocated or implemented;

NAP LO CTP LO CTP LO CTP B1 LO CTP B2 NAP
A1 LO LC A A2 LO LC B
HO trail A HO trail B
HO LC A HO LC B1 HO LC B2
1 2 3 4
W E W E W E
Figure 683. state A: 2 HO trails (A, B)

– state B: HO trails A and B are implemented and LO configured; for all the LO paths that before used
LO LCs A and B:
• the objects between 1W and 4E are freed:
– the connections in topology in node 2 are removed, both on EML and on RM database;
– the LO CTPs in node 2 are idle; in nodes 1 and 4 are still busy;
– all the LO LCs are idle;
• the path is set to partiallyConnected;
for HO objects, no differences compared with state A;
– state C: HO trails A and B are implemented and "partially configured" at LO: the ports 1W and 4E
are still LO configured (with LO CTPs busy), but all the LO link connections have been removed; in
node 2 HO CAPs are virtual and LO CTPs are deleted;
– state D: HO trails A and B are partially implemented and "partially configured" at LO: the HO con-
nections in topology are all implemented except the 2 CTP-CAP in node 2;
– state E: HO trail C between nodes 1 and 4 is partially implemented and "partially configured" at LO:
the HO connections in topology are all implemented except the one in node 2; no LO LC exists;
– state F: HO trail C is implemented and "partially configured" at LO: all the HO connections in topology
are implemented; no LO LC exists;
– state G: HO trail C is implemented and LO configured; LO LC C is client of HO trail C; it is idle even
if it is terminated by the old LO CTPs that are still busy; LO path is still partiallyConnected;
– state H (see below): HO trail C is implemented and LO configured; LO LC C and its CTPs are busy
because they belong to a path, which is fullyConnected;
NAP NAP
LO CTP A1 LO LC C LO CTP B2
HO trail C
HO LC A HO LC B1 HO LC B2
1 2 3 4
W E W E W E
Figure 684. state H: 1 HO trail (C)
Note: in every state there is no difference in nodes 1 and 4.
Both join and split can be executed:
– in a single step: a new action is defined in order to perform automatically all the activities that join
or split trails (i.e. that move, if successful, from A to H or viceversa);
– step by step: the user can execute an action at a time.
Join and split trails are completely reversible: if a "join trails" is interrupted after an action, e.g. in the state
B after the first action, it is possible to go back to previous state, applying the action "connect client paths
from 1W to 4E". It is also possible to continue the "join trails", applying the same action (i.e. join trails) or
the remaining actions (deconfigure trail A, B, deimplement connections ...).

Also when an action is not completed (e.g. it fails, an agent crash occurs, ...), it is always possible to con-
tinue or to go back. For example, if during the "split trail" the implementation of trail B fails leaving this trail
partially implemented, while the trail A has been successfully implemented and configured, it is possible:
a) to continue, performing the following steps:
1) implement trail B;
2) configure trail B;
3) connect client paths from 1W to 4E;
b) to go back, executing the join trails (A, B) or performing the following steps:
1) deimplement connection in node 2 of trail B;

2) deconfigure trail A;
3) deimplement connection in node 2 of trail A;
4) execute the steps that move the trails from D to H.
The state transitions C - D and E - F are not symmetrical: the deimplementation is applied to a single con-
nection in topology for each trail (the one in the common node), while the implementation is applied to the
whole trail: this is due to the fact that, in MSSPRING, the implementation could modify the squelching
tables in the connections in topology contained in the other nodes of the same MSSPRING, while the
deimplementation of a single connection leaves those squelching tables to the old values.
A report is presented to the user indicating in real time which phase of the operation is in progress and
its result when completed. All the LO-Paths impacted by the operation (supported by the involved HO-
Trails) are reported too.
3.6.1.3 Join / Split trail diagnostic
3.6.1.3.1 Join trail diagnostic
With reference to Figure 682.on page 640, A to D statuses describe a condition which includes two trails
E to H statuses describe a condition which includes only one trail
In case the Join operation is blocked in the B,C,D statuses, the possible user operations are:
– the user can manually revert (step by step) to A status
or
– the user can try to re-launch the join operation, since the probable reason of the interruption is the
condition of EML/NE not reachable
In case the Join operation is blocked in the E,F,G statuses, the possible user operations are:
– the user wants to complete the join operation by manually proceeding (step by step) to H status
or
– the user wants to manually revert (step by step) to A status by re-issuing the split command
N.B. Connect/Disconnect commands must be executed from the HO trail/s

3.6.1.3.2 Split trail diagnostic
With reference to Figure 682.on page 640, A to D statuses describe a condition which includes two trails
E to H statuses describe a condition which includes only one trail
In case the Split operation is blocked in the G,F,E statuses, the possible user operations are:
– the user can manually revert (step by step) to H status
or
– the user can try to re-launch the split operation, since the probable reason of the interruption is the
condition of EML/NE not reachable
In case the Split operation is blocked in the D,C,B statuses, the possible user operations are:
– the user wants to complete the split operation by manually proceeding (step by step) to A status
or
– the user wants to manually revert (step by step) to H status by re-issuing the join command
N.B. Connect/Disconnect commands must be executed from the HO trail/s

3.7 Diagnostic of the NPE Ring
3.7.1 The 4-F MS Spring RM side
3.7.1.1 Some useful definitions
– Serving nodes: the two nodes that talk to each other on the K1K2 channel, sending their protocol
messages in order to serve their requests. If more than one request is served on the ring, the serving
nodes may be more than two.
– Intermediate nodes: the nodes that are not directly interested by the fault.
– MS-SPRING request (trigger): any kind of valid input to the MS-SPRING machine: equipment/sig-
nal failure, signal degrade, external commands, and protocol requests/replies.
– protocol request: a protocol message issued by a Tail node toward its peer request node (that may
either be a Tail node or Head node, depending on the nature of the trigger).
– protocol reply: a protocol message issued by a Head node back to its peer Tail node to acknowl-
edge a Tail node's protocol request.
– protocol message: a K1K2 code sent on the K1K2 channel that may either be a protocol request
or protocol reply.
– Lockout of Working channels - ring (LW-R): command that disables the node capability to issue
a ring protocol request of any kind. The node is anyway allowed to issue ring protocol replies. The
command is local, i.e. it is not forwarded to the other nodes through K1K2 channels.
– Lockout of Working channels - span (LW-S): command that disables the node capability to issue
a span protocol request of any kind. The node is allowed to issue span protocol replies. The com-
mand is local, i.e. it is not forwarded to the other nodes through K1K2 channels.
– Lockout of Protection channels - span (LP-S): command that prevents the use of the protection
channels over the addressed span. The command is not local, i.e. it is forwarded through K1K2 chan-
nels also to the other nodes that, as a consequence, do not take any action involving the addressed
span.
– Routing in Working (RIW). For 1670SM equipment. The protection route is within the working
capacity
– Routing in Protection (RIP). For 1664SM equipment. The protection route is within the protection
capacity
3.7.1.2 4f MS-Spring
The ring can be made up of a maximum of 64 ADM's. 1664SM equipments can build 4-Fiber STM-16 rings
with Routing in Protection mechanism.
1670SM equipments can build 4-Fiber STM-64 rings with Routing in Working mechanism.
For Paths and Trails an attribute enables the usage of low priority resources. This attribute is taken into
account during path allocation.
The protection capabilities of the ring are based on the information stored in the Ring Traffic Map and eval-
uated by each NE in order to take the appropriate decisions in case of fault.

The “component" of the ring traffic map related to each path and trail is evaluated and sent to all NEs in
the ring.
In order to avoid misconnections, RM, during implementation phase, sends the update of the ring traffic
maps before the creation of connections, and viceversa, during the de-implementation phase, updates
the maps only after the deletion of connections.
The ring traffic map is not shown to the RM operator, because the same information are provided by the
path/trail route display functionality.
The D&C is performed using protecting resource between Service Nodes while using 1664SM with RIP
mechanism and using working resource between Service Nodes while using 1670SM with RIW mecha-
nism.
As a consequence of limitations existing on equipment side:
– for 1664SM rings D&C on interconnected NPE rings is not always able to survive to double
failures, a failure per ring, (this happens when the primary node of one ring is connected to the sec-
ondary node of the other ring)
In addition to the previous limitation:
– the time-slot interchange on protecting resources is not available
3.7.1.2.1 Path
The attributes relevant to NPE features are:
– Server MS protection usage profile: it represents the profile of the MS resources to be used in allo-
cating the path.
The possible values are:
• Normal (default)
– For 1664SM rings, the RIP mechanism is used, i.e. when crossing 4 Fibers MS-Spring,
the path uses only working (high priority) resources, except for primary and secondary
nodes of the double interconnection with another ring, because these nodes are charac-
terized by the Drop & Continue protection (RIP)
as a result, in the segment between service nodes:
• if the path is bidirectional (Figure 685.), the used resource (nodes E, D, H, I) can be
only the protection one: a bidirectional D&C IC on protection is performed in the pri-
mary nodes (D, H);
• if a path is unidirectional point-to-point (Figure 686.), the used resource is:
• protection if the signal flows into the service nodes (B, C): a unidirectional D&C IC
on protection is performed in the primary node (B);
is performed in the primary node (E); this allows the user to perform subsequent add
leg operation;
it is possible to use the protection resource instead of the working (nodes E, D), e.g.
forced by a constraint (Figure 687.);
• if a path is broadcast (Figure 688.), the used resource is:
• protection if the signal flows into the service nodes (B, C) like in a unidirectional
point-to-point path: a unidirectional D&C IC on protection is performed in the primary
node;
is performed in the primary node);
it is not possible to use the protection resource instead of the working one.

As a result of the previous rules defined for unidirectional and broadcast paths, a uni-
directional point-to-point path can become broadcast only if the working resources
are used between service nodes (nodes E, D in Figure 688.).
– For 1670SM rings the path uses only working resources (RIW)
• Protection preferred
When crossing a 4 Fibre MS-Spring, the path uses protecting (low priority) resources.
If the routing algorithm must use the working resource in one span of the 4F MS-spring (e.g.
no free resources in the protection, or a constraint is applied), all working resources are used
in the ring, in order to avoid jumps between working and protection resources (jumps not fore-
seen for the management of ring traffic map).
If the path is protected and main and spare routes are crossing the same MS-Spring, each route
crosses separately the ring itself since D&C connection are not available for protecting
resources.
As a consequence of this behavior and of the fact that the SNCP connection is not available
on a 4f MS-Spring, if the protected HO path is completely inside a 4f MS-Spring, the allocation
will always fail.
• Protection only
the path uses only protecting (low priority) resources.

3.7.1.2.2 Trail
– Server Ms protection usage profile is added to HO trails (see the description given for paths).
working
protection
A B C
NPE
F E D
G H I
NPE
N M L
Figure 685. bidirectional protected path

working
protection
SNCP
A B C
NPE
F E D
SNCP
Figure 686. unidirectional protected path (using working resource between nodes E and D)
working
protection
SNCP
A B C
NPE
F E D
SNCP
Figure 687. unidirectional protected path (using protection resource between nodes E and D)

working
protection
SNCP
A B C
NPE
F E D
SNCP
Figure 688. broadcast protected path
3.7.1.2.3 Physical Connection
An attribute specifies if the Physical Connection is Working (i.e. it connects main ports, involved in a MS
protection mechanism) or Protecting (i.e. it connects spare ports) or Normal (i.e. it connects ports not
involved in any MS protection mechanism.

3.7.1.2.4 4f MS Protection Block
The 4f MS Protection Block contains the following information:
– Containment information (network Id, subnetwork Id, et Id, node Id)
– fdnMapper. It identifies the object inside the NE.
– Configuration State. It is the state requested at the interface Functional Agent / TSD-IM Front End
Processor and can assume the following values:
• virtual.
The MS-SPRING et topology is only planned inside the RM (i.e. is in the state “defined") and
is not established inside the NE (the ring coordinator object is not present in the NE)
• enabled (foreseen for future usage).

The MS-SPRING et topology is “enabled" inside the NE, i.e. all the relevant objects are created
inside NE but the MS-Spring mechanism is not active; the NE transmits idle code on the K1/
K2 channel (see also Transition State)
• active.
The MS-SPRING et topology is active in the NE, i.e. it is “implemented" in RM (see also Tran-
sition State)
– Transition State. It describes the transition state of the MS-SPRING in the NE during the configu-
ration phase. The following values are possible:
• idle. It is the value corresponding to the value “virtual" of the Configuration State
• defined. The ring has been defined by the action applied on the Protection Manager MOC in
NE: the information on working/protecting east/west msTTPs have been provided to the NEs.
As a result the Ring Coordinator object is created in the NE and all other objects (Ring Map,
Ring Traffic Map or Squelch Table, Ring Protection Group, Ring Protection Units ...) are created
and correlated to the Ring Coordinator. The Ring Coordinator has the status “enabled"
• populated map. The Ring Map has been populated according to the information contained in
the ring map info attribute through the populate action applied to the Ring Coordinator. As a
result, the information describing the map of the nodes inside the ring have been stored both
inside the Ring Map and in the Ring Traffic Map accordingly.
• activated. The Ring Coordinator has been activated (activate action). As a result, the pro-
tected msTTPs, unprotected CTPs, working/protecting east/west side have been put in relation
according to the ring type (2/4 fiber with/without extra-traffic) and the MS-Spring mechanism is
active
The Configuration State attribute “active" is consistent with the NE 'status' if the 4-F protection block
entered the sequence “defined", “populated map", “activated", i.e. if the Ring Coordinator is “acti-
vated". In this case the attribute value is “activated" and the Consistency Status is “normal" .
– node id: it refers to the node id attribute inside the node entity
– ring map info: it is a string representing the sequence of node identifiers following the direction east-
west in the ring. It is used to provide to the NE the information usefull when filling the Ring Map object
(e.g.: “x,y,z,w". Starting from the node x and moving to east the found nodes are in the sequence y,
z, w, where x,y,z,w are the identifiers of the nodes).

– traffic map: the attribute is a sort of 'token' used to apply the alignment of the Ring Traffic Map inside
the NE, according to the info, if any, contained in the AU4 Transport Map, plus the implicit information
that, when the au4(s) or piece(s) of au4(s) are not contained inside the AU4 Transport Map, no con-
nection has to be present inside the Ring Traffic Map.
– Consistency Status: normal, not aligned, failed to align.

It represents the consistency between RM object and NE objects (not aligned if at RM level a mis-
alignment between the two objects has been forced; failed to align if the re-alignment procedure,
either automatic or manual, has failed, normal if the re-alignment procedure is successfull)
– West Reliable ( protected ) Resource: it is the id of the reliable msCtpCap on the west main port
– East Reliable Resource: it is the id of the reliable msCtpCap on the east main port
– West Working Unreliable Resource: it is the id of the unreliable msCtpCap on the west main port
– East Working Unreliable Resource: it is the id of the unreliable msCtpCap on the east main port
– West Protecting Unrealiable Resource: it is the id of the unreliable msCtpCap on the west spare
port
– East Protecting Unreliable Resource: it is the id of the unreliable msCtpCap on the east spare port
– Ring WTR (Wait To Restore time): it containes the value to provide to the NE during the MS-Spring
provisioning phase.
– West Span WTR (Wait To Restore time): it contains the value (west side) to provide to the NE during
the MS-Spring provisioning phase.
– East Span WTR (Wait To Restore time): it contains the value (east side) to provide to the NE during
the MS-Spring provisioning phase.
– Current User Command. The attribute indicates the command (none, lockout working west, lockout
working east, west ring force switch...) requested by the RM user.
– West /East Ring Active Condition

This attribute indicates the ring command that is currently stored to and served by the NE on the
West/ East side of the node. The following values shall apply:
• no command: null
• Ring forced switch: forced
• Ring manual switch: manual
• Ring WTR running: wtrRunning
N.B. the WTR has been put together with the possible active commands because, even
if it is not a user command, it can be cleared through a user command as well as the
others.
• exercise

– West /East Ring Pending Command
This attribute indicates the ring command that is currently stored to but not served by the NE on its
West side. The following values shall apply:
• Ring forced switch: forced
• Ring manual switch: manual
• exercise
– West / East Span Active Condition

This attribute indicates the span command that is currently stored to and served by the NE on the
West / East side of the node. The following values shall apply:
• Span forced switch: forced
• Span manual switch: manual
• Span Lockout of Protection: lockoutProtection
• Span WTR running: wtrRunning
• exercise
– West / East Span Pending Command

This attribute indicates the span command that is currently stored to but not served by the NE on
its West side. The following values shall apply:
• Span forced switch: forced
• Span manual switch: manual
• exercise
– East / WestLockout Working Ring

This attribute indicates whether a Lockout of Working Channels Ring command is currently stored
to the NE on its East /West side. It can assume the following values: none, lockoutWorking.
– East / West Lockout Working Span

This attribute indicates whether a Lockout of Working Channels Span command is currently stored
to the NE on its East / West side. It can assume the following values: none, lockoutWorking.

– West / East Failure of Protocol
This attribute indicates the K1K2 protocol failure detected on the West / East side of the node. The
following values shall apply:
• no protocol failure detected: none
• default APS code detected: defaultKBytes
• improper APS code detected: improperCode
• node Id mismatch detected: nodeIdMismatch
• inconsistent code
– Node Condition (Mid Protocol Role)

This attribute represents the status of a node in terms of how the node is acting on the protocol chan-
nel in order to serve either a local (on west side) or remote trigger. The values of this attribute may be:
• role not known: unknown

• the MS-SPRING is enabled (configured) but not active (protection mechanism not running) at
the node: standby
• the MS-SPRING is enabled and active at the node; the role of the node is actually determined
by the West- and east Protocol Role (see below): idle
• the MS-SPRING is enabled and active at the node; either the node received/detected nothing
and some other node is serving an external command or the node received/detected a trigger
but some other node is serving another trigger of higher priority: intermediate
• end. It is the tailHead node, i.e. the node which initiates or terminates the protocol request.
– West / East Protocol Role

This attribute represents the status of a node in terms of how the node is acting on the protocol chan-
nel in order to serve either a local or remote trigger regarding its West / East side. The values of this
attribute may be:
• the node a) received no external command, or b) received no protocol request, or c) detected
no failure/degrade, or d) is isolated form the other nodes at MS level: idle
• the node is serving an external command-ring or failure/degrade-ring that involves its West/
East side: tailHeadRing ( interruption RING )
• the node is serving an external command-span or failure/degrade-span that involves its West/
East side: tailHeadSpan ( interruption SPAN )
• the protection MS on the West / East side of the node is unavailable or locked out (via LP-S
only): protUnav
• the node is serving an external command-ring or failure/degrade-ring that involves its West /
East side, the protection MS on the West / East side is unavailable or locked out: ( ext ) Ring-
ProtUnav
• tailHeadExrcRing external exercise Ring
• tailHeadExrcSpan external exercise Span
• thRingExrcRingProtUna the node is serving an exercise command that involves its West /
East side, the protection MS on the West / East side is unavailable or locked out

3.7.2 User Presentation
The protection status reporting window displays the current status of the MS SPring, in terms of:
– triggers =external commands and/or failure/degrade conditions. The nodes whose triggers are
being served are named served nodes. A served node has at least one trigger served and may have
some pending triggers.
– the reaction of the ring to those triggers, namely what triggers are being served, and which ones are
pending. (waiting to be served, either because they are at lower priority, or there are specific protocol
rules). The nodes that have no triggers or only pending ones are called intermediate nodes.
N.B. The protection status reporting screen is neither intended to display the status of the K1K2 sig-
naling, nor the status of the physical switches. With the 2F MS SP ring application, the
bridge&switch at multiplex section level always occurs at served nodes, whereas protection
channels pass-through is made by intermediate nodes. With the 4F MS SPring application,
bridge&switch at AU-4 level may take place at whatsoever node, depending on traffic distribu-
tion.
It should be noted that according to the MSSPring protocol rules any of the following scenarios may occur:
– no trigger is present, no protocol request (namely, K1K2 code other than noRequest) is signaled on
the ring;
– 1 trigger is present, 1 protocol request is signaled and served;
– N (>1) triggers are present, N protocol requests are signaled, only 1 is served (higher priority);
– N triggers are present, N protocol requests are signaled and served (same priority);
– N triggers are present, N protocol requests are signaled, none is served (same priority, but not
allowed to co-exist).
– 1 trigger is present and served, no protocol request is signaled (1);
– M (>1) triggers are present, N (<M) protocol requests are signaled, only 1 is served (higher priority);
– M triggers are present, N (<M) protocol requests are signaled and served (same priority);
– M triggers are present, N (<M) protocol requests are signaled, none is served (same priority, but not
allowed to co-exist).
(1) The Lockout of Working channels commands make the scenario even more complicated, as those
commands are not signaled but are actually served, in the sense that they influence the behavior
of the node to which they are addressed.
The window can display up to 16 node icons (see Figure 689.)

Figure 689. 4 fibre MS SP reporting screen
3.7.2.1 Configuration State attribute
Two node icons are associated to the values of the ConfigurationState attribute of the MSSPRingProtec-
tionBlock:
– ConfigurationState = “virtual", icon
– ConfigurationState = “enabled", icon (not managed in this version release)
– ConfigurationState = “active", icon
When the ConfigurationState is “virtual" for a node (because the relevant T-FEP fails) an all-grey icon (the
virtual node icon) is displayed as a placeholder for that node, but no additional information can be dis-
played on top of that icon about that node (see Figure 690.).
Figure 690. ConfigurationState = “virtual" icon
The virtual node icon being displayed means that the MS-SPRING is not configured at the node.
When the ConfigurationState is either “enabled" or “active" for a node, the node icon shown in Figure
692.is displayed. Such an icon then acts as a background for all the icons associated to the attributes of
the MSSPRingProtectionBlock.
The node icon always reports the actual condition of the node in terms of the protocol role the
node is playing to react to the MS-SPRING triggers, and the external commands being stored to
the node. If the condition required by the RM and the actual node condition do not match, the “not
aligned" indication is displayed along with the node icon.

virtual
topology implementation
topology deimplementation
MS-SPRING activation
enabled active
MS-SPRING deactivation
Figure 691. ConfigurationState diagram
The following table describes the rationale that drives the display of the various icons according to the
ConfigurationState state diagram (see Figure 691.).
ConfigurationState node condition displayed icons operation
virtual MS-SPRING not config- virtual node icon topology implementation

ured failure (T-FEP stalled)
active MS-SPRING not config- virtual node icon topology implementation

ured failure (TSD-IM establish
failed)
active ? node icon +MidProtocol- node unreachable

Role = “unknown" icon
on top
enabled enabled node icon +MidProtocol- MS-SPRING deactiva-

(not managed in this ver- Role = “standby" icon on tion successful
sion release) top
enabled active node icon + other icons MS-SPRING deactiva-

(not managed in this ver- on top to show protocol tion failure
sion release) role and stored com-
mands +
“not aligned" indication

ConfigurationState node condition displayed icons operation
active active node icon + topology implementation

other icons on top to successful or MS-
show protocol role and SPRING activation suc-
stored commands cessful
active enabled node icon + topology implementation

MidProtocolRole = failure (TSD-IM populate
“standby" icon on top + failed) or
“not aligned" indication MS-SPRING activation
failure
The node icon is a rectangle plus arrows that represent the fiber optics to connect the nodes to each other.
Plus, the node icon features a number of rectangles (see Figure 692.) to hold icons associated to all the
attributes of the MSSPRingProtectionBlock MOC:
– the icon for the MidProtocolRole attribute;
– the icon for the WestProtocolRole attribute;
– the icon for the EastProtectionRole attribute;
– the set of six icons for the WestRingActiveCondition, WestSpanActiveCondition, WestRing-
PendingCommand, WestSpanPendingCommand, WestLockoutWorkingRing, and West-
LockoutWorkingSpan on the West side of the node icon;
– the set of six icons for the EastRingActiveCondition, EastSpanActiveCondition, EastRingPend-
ingCommand, EastSpanPendingCommand, EastLockoutWorkingRing, and EastLockout-
WorkingSpan on the East side of the node icon;
– the icon for the FailureOfProtocol to be placed outside the node icon next the bottom left and right-
hand corner;
The reason for providing each node icon with 6 icons for the local commands comes from the combina-
tions of active and pending commands that are allowed to coexist at each node.
3.7.2.2 MidProtocol Role ( NODE CONDITION) attribute
The central rectangle with a black triangle in it - representing the NE - is the place where the values of
the MidProtocolRole are displayed (see Figure 693.).
When MidProtocolRole = “idle" and all other attributes are = “null", no additional icon is placed on top of
the node icon, so that all command-related rectangles still look gray - to show that no external command
is stored to the node, namely either active or pending - and the rectangles on the side of the central triangle
both looking green, to mean that both the East- and WestProtocolRole are in an idle condition, namely
the node is neither serving any trigger nor acknowledging a trigger to be served by some other node on
the ring.
Whenever the MidProtocolRole attribute changes from “idle" to another value, the icon associated to that
new value is displayed on top of the central rectangle with the black triangle in it.
Whenever either the East- and WestProtocolRole, or both, change to a value different from “null", the icon
associated to the new value (see Figure 694.and Figure 695.) are displayed on top of the designated
green rectangle.
Whenever any of the external commands is given to and stored by a node to go either active or pending,
the icon associated to the new value (see Figure 702.) are displayed on top of the designated gray rect-
angle

west ring pending command east ring pending command
east span pending command
west span pending command
working fibers east protocol role
east ring active condition
east span active condition
east Lockout W ring status

protection fibers
east Lockout W span status
west protocol role
west span active condition
west ring active condition
west Lockout W span status

east failure ofprotocol
west Lockout W ring status
Figure 692. ConfigurationState = “enabled"/"active" icon
idle intemediate unknown standby end
no icon
GREEN (not supported) GREEN
Figure 693. MidProtocolRole ( NODE CONDITION ) icons

3.7.2.2.1 West- and EastProtocolRole attributes
null tailHeadRing tailHeadSpan protUnav (EXT) thRingProtUnav

(interruption Ring) (interruption Span)
no icon
RED RED RED RED

tailHeadExrcRing thExRingProtUnav
BLUE BLUE
Figure 694. WestProtocolRole icons.
null tailHeadRing tailHeadSpan protUnav thRingProtUnav
no icon
RED RED RED RED
tailHeadExrcRing thExRingProtUnav
BLUE BLUE
Figure 695. EastProtocolRole icons.

3.7.2.2.2 Protocol Failure attribute
This attribute has icons (see Figure 696.) associated to each of its values to represent the various failure
conditions that may affect the K protocol. When a node detects a protocol failure in the incoming K bytes
on a given side, the relevant icon is displayed.
null defaultKBytes improperCode nodeIdMismatch inconsistentCode
no icon
RED RED RED RED
Figure 696. East/West failure Of Protocol
3.7.2.3 Ring Active Condition attributes
Each of these values is represented on the screen by an icon (see Figure 697.) located at the designated
position for this attribute, and pointing at the side of the node to which the command is addressed. Each
value other than null indicated either a command (forced, manual) given by the manager or a condition
(wtrRunning) automatically forced by the NE: each of those can be removed by the manager by the appro-
priate release command. Specifically, a release WTR command forces the WTR counter inside the NE
to immediate expiration.
Manual and Forced switch are represented by same symbol on different color, yellow and red respectively.
manual switch ring forced switch ring wtr ring exercise

null
no icon
YELLOW RED CIAN
Figure 697. East/West ring active condition
3.7.2.4 Span Active Condition attributes
Each of these values is represented on the screen by an icon (see Figure 698.and Figure 699.) located
at the designated position for this attribute. Each value other than null indicated either a command (forced,
manual, lockoutProtection) given by the manager or a condition (wtrRunning) automatically forced by the
NE: each of those can be removed by the manager by the appropriate release command. Specifically,
a release WTR command forces the WTR counter inside the NE to immediate expiration.

wtr span
manual switch span forced switch span exercise
null
no icon
YELLOW RE CIAN
Figure 698. East span active condition
wtr span exercise

manual switch span forced switch span null
no icon
YELLOW RED CIAN
Figure 699. West span active condition
3.7.2.5 Ring Pending Command
Each of these values is represented on the screen by an icon (see figure below) located at the designated
position for this attribute. Each value other than null indicates a command given by the manager and that
can be removed by the manager by the appropriate release command.
manual switch ring forced switch ring null exercise
no icon
YELLOW RED CIAN
Figure 700. East / West ring pending command
3.7.2.6 Span Pending Command
Each of these values is represented on the screen by an icon (see figure below) located at the designated
position for this attribute, and pointing at the side of the node to which the command is addressed. Each
value other than null indicates a command given by the manager and that can be removed by the manager
by the appropriate release command.

manual switch span forced switch span null exercise
no icon
YELLOW RED CIAN
Figure 701. East span pending command
manual switch span forced switch span null

exercise
no icon
YELLOW RED CIAN
Figure 702. West span pending command
3.7.2.7 Lockout Working Ring attributes
null Lockout working ring
no icon
Figure 703. East / West Lockout Working Ring

3.7.2.8 Lockout Working Span attributes
null Lockout working span
no icon
Figure 704. East / West Lockout Working Span
3.7.2.9 Inhibition chain
The possible requests are listed herebelow in decreasing priority.
– LP-S (Lockout Protection Span), SF-P (Signal Fail Protection), LOW-R (Lockout Working Ring),
LOW-S (Lockout Working Span); LOW-R, LOW-S LP-S
– FS-S (Forced Switch Span)
– FS-R (Forced Switch Ring)
– SF-S (Signal Fail Span)
– SF-R (Signal Fail Ring)
– SD-P (Signal Degrade Protection)
– SD-S (Signal Degrade Span)
– SD-R (Signal Degrade Ring)
– MS-S (Manual Switch Span)
– MS-R (Manual Switch Ring)
– WTR (Wait to Restore Time)
– EXER (Exercise)
EXCEPTIONS
– Two MS-S (Manual Switch Span): no action
– SF-R and FS-R : no action
– Two SD-R : no action
3.7.2.10 Scenarios
This paragraph describes various ring scenarios , as shown in the graphical interface.

3.7.2.11 Bi-directional Signal Fail / Ring Scenario
DESCRIPTION
A Bi-directional Signal Fail / Ring is present on A-B span. The relevant aggregate boards are affected by
LOS alarm.
SERVED REQUESTS DISPLAY
Bi-directional Signal Fail / Ring on A-B span (indicated by RING INTERRUPTION (tailHeadRing) icons
on A-B span)
OPERATION
The traffic affected by the failure is recovered on protection channels away from the failure. All LP traffic
paths whose channels are needed to recover HP traffic are pre-empted.
HP traffic is maintained. LP traffic paths whose channels are needed to recover HP traffic is lost.
REPAIR ACTION
Two alternatives are possible:
a) First execute the repair of the main span. HP traffic reverts to the main span while LP traffic still is lost.
1) Click on the alarm icon displayed on the main span. The alarm detail window is presented, giv-
ing the information needed to repair the span.
b) First execute the repair of the spare span, so moving to the Span switch scenario.The LP traffic not
overlapping HP traffic is restored.
1) Click on the alarm icon displayed on the spare span. The alarm detail window is presented, giv-
The scenario after the repair of the affected spans is described at paragraph 3.7.2.12.
Figure 705. Bi-directional Signal Fail / Ring

3.7.2.12 Bi-directional Signal Fail / Ring cleared .WTR
DESCRIPTION
The bi-directional Signal Fail / Ring on A-B span is cleared as a consequence of a repair action. The last
node detecting the signal failure clear starts the WTR ( wait to restore time )
on A-B span) is still displayed.
The 'east ring active condition' icon reports WTRrunning.
OPERATION
All nodes dropping/inserting HP traffic that was affected by the failure still recover it on protection channels
away from the failure.
All LP-traffic paths whose channels are needed to recover HP traffic are still pre-empted.
Node A (the last detecting the signal failure clear) is running
REPAIR ACTION
The WTR timer may be forced to expiration by RM via Clear WTR command. ( not implemented in this
version )
Figure 706. Bi-directional Signal Fail / Ring cleared .WTR
3.7.2.12.1 Double Bi-directional Signal Fail / Ring
DESCRIPTION
Bi-directional Signal Fail / Ring on A-B span.
Bi-directional Signal Fail / Ring on D-E span.
Bi-directional Signal Fail / Ring on D-E span (indicated by RING INTERRUPTION (tailHeadRing) icons

OPERATION
All nodes dropping/inserting HP traffic that was affected by the failure still recover it on protection channels
away from the failure.
HP traffic that was affected by either failure is not recovered
All LP-traffic paths whose channels are needed to recover HP traffic are pre-empted.
REPAIR ACTION
The scenario after the repair of one of the two faults is described at paragraph 3.7.2.11.
It is suggested the repair of the main span first.
Figure 707. Double Bi-directional Signal Fail / Ring

3.7.2.12.2 Forced Switch Ring
DESCRIPTION
A Forced Switch / Ring command is entered to A/East for A-B span.
Forced Switch / Ring command (indicated by tailHeadRing (RING INTERRUPTION) icons facing the A-
B span, and the FS/R icon pointing to the relevant node and side. This FS/R icon means that a command
is being served and may be removed).
OPERATION
All nodes dropping/inserting HP traffic that is traversing the addressed span is recovered on protection
channels away from that span (just like an SF/R affecting the same span).
REPAIR ACTION
This command is used in the Add/Remove Node procedures.
Figure 708. Forced Switch / Ring
3.7.2.12.3 Double Forced Switch / Ring to different nodes, node isolated
DESCRIPTION
Forced Switch / Ring command given to A/East for A-B span and Forced Switch / Ring command given
to C/West for B-C span.
This scenario can be established to put node B in local maintenance condition.

Forced Switch / Ring command given to A/East (indicated by tailHeadRing icon facing the A-B span, and
the FS/R icon . FS/R icon means that a command is being served and may be removed).
Forced Switch / Ring command given to C/West (indicated by tailHeadRing icon facing the B-C span, and
the FS/R icon . FS/R icon means that a command is being served and may be removed).
OPERATION
Node B is isolated, as the two Force Ring commands partition the ring into two segment, [B] alone and
[C, D, A].
HP traffic that is traversing both the involved spans is recovered on protection channels away from those
spans.
HP traffic that is traversing one of the involved spans is not recovered.
All LP paths whose channels are needed to recover HP traffic are pre-empted.
REPAIR ACTION
After the completion of the local maintenance condition of node B, enter the Release Forced Switch / Ring
on nodes A and C.
Figure 709. Double Forced Switch / Ring to different nodes, node isolated

3.7.2.12.4 Double signal Fail / ring, node isolated
DESCRIPTION
Bi-directional Signal Fail / Ring on B-C span.
Bi-directional Signal Fail / Ring on A-B span (indicated by tailHeadRing icons facing both the A-B span).
Bi-directional Signal Fail / Ring on B-C span (indicated by tailHeadRing icons facing both the B-C span).
OPERATION
Node B is isolated, as the two Force Ring commands partition the ring into two segment, [B] alone and
[C, D, A].
HP traffic that is traversing both the involved spans is recovered on protection channels away from those
spans.
HP traffic that is traversing one of the involved spans is not recovered.
All LP paths whose channels are needed to recover HP traffic are pre-empted.
REPAIR ACTION
a) Execute the repair of the main span. HP traffic reverts to the main span while LP traffic still is lost.
1) Click on the alarm icon displayed on the main span. The alarm detail window is presented, giv-
Figure 710. Double signal Fail / ring, node isolated
It is suggested the repair of the main span first.

3.7.2.12.5 Forced Switch / Span
DESCRIPTION
A Forced Switch / Span command is entered to B/West for A-B span.
This command is used when the A-B main span requires a local maintenance.
Forced Switch / Span command (indicated by “tailHeadSpan" icons facing the A-B span, and the FS/S icon
pointing to the relevant node and side).
OPERATION
Nodes A and B recover on the protection channels the traffic traversing the involved span (just like an SF/
S affecting the same span). The only channels that are bridged and switched by A and B are those that
actually carry traffic over A-B.
REPAIR ACTION
After the completion of A-B main span local maintenance the Release Switch Span West can be entered.
Figure 711. Forced Switch / Span
3.7.2.12.6 Forced Switch / Ring pending
DESCRIPTION

Forced Switch / Ring command given to D/West for D-C span.

Forced Switch Ring pending icon on D node.
OPERATION
Forced Switch / Ring command is pending (actually it is higher priority than the SF/R, but it cannot be
served because the protocol fails to complete on the long path).
REPAIR ACTION
Release Forced Switch Ring.
Figure 712. Signal Fail / Ring pending, Forced Switch / Ring pending
3.7.2.12.7 Double Fault/ Ring pending
DESCRIPTION
Bi-directional Signal Fail on Protection on B-A span.
Bi-directional Signal Fail / Ring on D-E span.
It is a double fault service affecting. The fault between A and B nodes (SF-P) has priority greater than the
fault between C and D nodes (SF-R)
Bi-directional Signal Fail on Protection (indicated by “protection unavailable" icons facing the A-B span)
OPERATION
Bi-directional Signal Fail / Ring is pending (it is lower priority than the Signal Fail /Span), affected traffic
is not recovered, all LP-traffic remains.

Bi-directional Signal Fail on Protection prevents the use of the protection channels on the A-B span.
Figure 713. Signal Fail Span, Signal Fail / Ring pending

3.7.2.12.8 Span Switch Request: Exercise East
DESCRIPTION
A Span Switch Request: Exercise East is issued on node B.
East Protocol Role=TailHeadExrcSpan on B node
West Protocol Role=TailHeadExrcSpan on C node
OPERATION
The Exercise command does not affect the traffic carried by the NPE ring
Figure 714. Span Switch Request: Exercise East menu option

Figure 715. Span Switch Request: Exercise East.
3.7.2.12.9 Ring Switch Request: Exercise East
DESCRIPTION
A Ring Switch Request: Exercise East is issued on node B.
East Protocol Role=TailHeadExrcRing on B node
West Protocol Role=TailHeadExrcRing on C node
OPERATION
The Exercise command does not affect the traffic carried by the NPE ring.

Figure 716. Ring Switch Request: Exercise East menu option
Figure 717. Ring Switch Request: Exercise East

3.8 NML-EML CONSISTENCY CHECKS
In the following are described the consistency audit and consistency download activities that can be exe-
cuted either on a single NE or the whole EML DOMAIN.
3.8.1 NML-EML Consistency Checks (SEN-IM)
3.8.1.1 Consistency audit (SEN-IM)
The Consistency Audit activity verifies the misalignments between the EML and the NML. This activ-
ity does not perform any corrective actions.
The Consistency Audit activity is required if the operation launched by 1354RM fails on EML.
To execute the consistency audit:
a) Activate the Network Consistency Agent. (Set Run Level=3 from Monitor application)
b) On the involved EML/NE execute the Consistency Audit pop-up menu.
The available options are:
1) Global
2) PDHPort NAP
3) SDHPort MStp
4) at HO/LO level
The option Global causes the execution of all the remaining checks from 2) thru 4).
The reporting of the operations is performed using multiple messages in order to display the current state
of the ongoing operations (number of not aligned objects, etc...) Otherwise from the Browser the mis-
aligned objects (tps) can be displayed by selecting the NE and issuing Display: Related items: All Mis-
aligned Objects.
3.8.1.2 Consistency download (SEN-IM)
The Consistency Download activity verifies the misalignments between EML and NML and aligns EML
data to RM data.
a) Execute a Download Disable command
b) Activate the Network Consistency Agent (Run Level=Consistency)
c) On the involved EML/NE execute the Consistency Download pop-up menu.
The available options are:
1) Global
2) PDHPort NAP
3) SDHPort MStp
4) at HO/LO level
5) Performance Monitoring (Only for Download)
The option Global causes the execution of all the remaining checks 2) thru 4).

The reporting of the operations is performed using multiple messages in order to display the current state
of the ongoing operations (number of not aligned objects, etc... Otherwise from the Browser the mis-
aligned objects (tps) can be displayed by selecting the NE and issuing Display: Related items: All Mis-
aligned Objects.
d) Set Run Level=Full Functionality
e) Execute checks on an eventual EML-NE misalignment. From browser point to the Node icon and
issue Display: Related items: Alarmed Objects, to verify the presence of a Configuration Mismatch
alarm
f) Set Configure Download: Enable on all the NEs/EMLs.
3.8.1.3 Example of SEN-IM NE misaligned
MISALIGNMENT INDICATIONS
The following indications of misalignment are perceived by the operator:
– On the 1354RM map a node is misaligned.
– On the 1353SH map the corresponding NE is misaligned. See following figure.
Figure 718. 1353NM map: misaligned NE
– a path is disabled, probably as a consequence of the misalignment

Figure 719. Path list: the path is disabled (OOS)
SEQUENCE OF LOCALIZATION OF THE MISALIGNMENT
1) Set the Run Level=Consistency. See following figure.
2) From the NE list select the misaligned NE and issue Consistency Audit: Global
Figure 720. NE: Consistency Audit menu

3) The consistency report does not include any indication of misalignment, then the misalign-
ment is localized between 1353NM and Network Element.
In addition, the errors are located at NE level, because are traffic affecting.
Figure 721. Consistency report
4) Set the Run Level to Full Functionality.
CORRECTIVE ACTION SEQUENCE
Due to the fact that the wrong data are localized at NE level, it is necessary to execute a download
of the data from 1353NM to the involved NE.
1) From 1353NM map window select the NE and issue: Operations:Supervision: Stop....
2) At this point the NE is no longer supervised. Execute NE: Supervision: Align down
3) Click on the NE name and confirm by clicking on OK button.
4) After a few seconds the alignment is completed.
5) From the NE list it is possible to verify that the involved NE is aligned.
6) From the 1354RM map the user can verify that the disalignment ceased

3.8.2 SEN-IM NM misaligned
MISALIGNMENT INDICATIONS
– On the 1354RM map a node is misaligned.
– On the 1354RM node list a node is misaligned. See following figure.
– On the 1353NM map the corresponding NE is misaligned.
– Traffic service is not affected
SEQUENCE OF LOCALIZATION OF THE MISALIGNMENT
a) From 1353NM select the involved NE and issue Supervision: MIB: Compare
b) In the Supervision: MIB: Compare confirmation box click on OK to confirm.
c) From the Compare dialog box NE-1 is misaligned with respect to 1353NM.
d) At this point, from 1354RM interface:
7) Set the Run Level=Consistency.
8) From the NE list select the misaligned NE and issue Consistency Audit: Global. The example
which follows reports an example of audit report on connections (at Lo / Ho)
9) The consistency report includes an indication of misalignment, in particular a mismatch has

been discovered for one subnetwork connection missing on 1353NM. See following figure.

Figure 723. Consistency report
The 1353NM MIB is misaligned with respect to 1354RM MIB and 1353NM MIB is misaligned
with respect to the NE MIB, then the problem is located in 1353NM MIB.
CORRECTIVE ACTION SEQUENCE
Due to the fact that the wrong data are localized at NM level, it is necessary to execute a download
of the data from 1354RM to 1353NM
a) From 1354RM execute Consistency Download.
Figure 724. Consistency Download pop-up menu

Figure 725. Confirmation dialog box.
Figure 726. Consistency download report
b) Set Run Level=Full Functionality
c) From the NE list it is possible to verify that the involved NE is aligned.

3.8.3 NML-EML Consistency Checks (Q3)
With TSD-IM, RM interacts directly with the NEs and directly manages alignment, consistency, isolation
and download enable / disable.
3.8.3.1 Download disable management (Q3)
The operator is able to specify for TSD-IM NEs the download disabled / enabled mode (download enabled
mode is the default condition)
When a NE is in “download - disabled" mode, all changes are buffered in the RM MIB, being not sent to NE.
Objects in the RM MIB that, as a consequence of the download disable mode, are not aligned with the
NE, are “marked” with the value of the consistency status attribute (“not aligned").
When the download disabled mode is removed and the NE is reachable, RM data are downloaded to NEs.
If the download disabled mode is removed and the NE is not reachable, the operation is rejected.
If problems are detected during the download, the NE is put in “isolation” mode.
During the “downloading" activity on a given NE, all concurrent operations requested by RM operator and
involving the same NE are rejected.
3.8.3.2 Ne isolation detection and recovery (Q3)
RM is able to detect not reachable NEs as a consequence both of problems in the EML, in the DCN or
in the NE.
When a NE is in “download enabled" mode and is not reachable, RM behavior is similar to the one
described for the download disable mode.
Elementary alarms are correlated to the impacted transport entity allowing a better identification of the
transport entity impacted by the isolation problem.
The isolation is detected as a consequence of a failure of an operation addressed to the NE.
The recovery from the isolation is detected by means of a slow polling performed by RM on the “isolated"
NE.
When an isolated NE is detected as reachable, the download is automatically started.
During downloading activity, the same considerations made for download disable to download enable
transition are applicable.
The OS isolation alarm received by NM and the NM isolation alarm detected by mean of a slow polling
performed by RM are reported as alarms at the RM user interface.
3.8.3.3 Consistency download management (Q3)
The objective of this feature is to align the NE to RM.
The operation is available for Q3 NEs while1354RM is in normal “online" run-level.
The operation is available when the NE is not isolated and in download enabled mode. If the communi-
cation is lost during the download, the operator is informed at user interface and the NE is left in the down-
load enabled mode; when the communication is resumed no automatic re-start of the consistency
download is performed.

3.8.3.4 Consistency audit management
The objective of this feature is to verify the alignment between NE and RM Mib.
The operation is available for TSD-IM NEs while the RM system is in normal online run-level.
Two types of consistency audit are available:
– Mark :
differencies are “marked". These differencies will be taken into account and downloaded during the
operations of enabling the download and isolation recovery.
– Notify:
differences are “marked" and wil be not taken into account during the operations of enabling down-
load or isolation recovery.
The consistency audit is available on the NE, only if the NE is not isolated and the 1354RM is in Download
Disable mode.
3.8.3.4.1 Consistency audit on objects
Objects impacted by the consistency audit are RM elementary objects like ports, single TPs, subnetwork
connections, ...
3.8.3.4.2 Download disabled to enabled transition
All current operations on the NE must be completed before serving the transition.
3.8.3.4.3 Startup / Restart scenario
RM elementary objects are taken into account by layers in a server to client order: physical ports, NAPs,
MS-TPs, HO-CTPs, HO connections, HO-TTPs, LO-CTPs, LO connections.
3.8.3.4.4 Ne reachable to unreachable transition
All the current operations on the NE must be completed considering the NE unreachable even if the state
changes again before the end of the current operations.
3.8.3.4.5 Download enabled to disabled transistion
All the current operations on the NE must be completed before serving the transition. For these operations
the NE has to be considered as still in download enabled.

3.8.3.4.6 Reporting
From browser issue Display: Related Items: All Misaligned Objects.
3.8.3.5 Reporting during consistency ( TSD-IM )
This feature allows to present the list of RM objects not consistent with the NE one's.
An object can be not consistent due to the misalignment of one or more attributes. For each attribute the
following information are presented :
– object class
– user label
– attribute: attribute of the object that causes the not consistency
– error type: reason of the in-consistency
– date
The user label field contains the user label of the object with the following exceptions:
– msProtBlock4f = user label of the node

– ctp (ho) = user label of the port - payload position
– nap = user label of the port
– au4RTM = user label of the node - au4
– ctp (lo) = user label of the port - payload position
– connInTopol = user label of the path
The user can choose, using two different commands, to display a global or a restricted list of the objects.
The global list comprises:
– ne
– port (sdh)
– msCtpCap
– msProtBlock4f
– ctp-ho
– port (pdh)
– nap
– au4RTM
– cap
– ctp-lo
– connInTopol
– pmTp
The restricted list comprises only traffic affecting attributes:
– ne (only if it is not reachable)

– msCtpCap (au4Structure, removeFromProtSchema, allAttributes)
– msProtBlock4f (msProtConfState, allAttributes)
– ctp-ho (disconnectOnNe, allAttributes)
– nap (disconnectOnNe, allAttributes)
– au4RTM (consistSt, allAttributes)
– cap (virtual, tug1Cfg, tug2Cfg, tug3Cfg, allAttributes)
– ctp-lo (disconnectOnNe, allAttributes)
The allAttributes value is used when it is not possible to determinate the attribute that caused the incon-
sistency.

3.8.3.6 Example of Q3 NE misaligned
– On the 1354RM a node is misaligned. ( From the map or from attibute NENOTEMLALIGNED on
the NE list)
– a path is disabled, probably as a consequence of the misalignment
SEQUENCE
a) Set the Network Element to Download Disable mode.
b) Issue Consistency Audit: Mark Audit
c) Select NE: Search all related objects: (Not Aligned) Misaligned Objects.
The list of Not aligned (misaligned) objects is displayed.
d) Enter Configure Download: Enable. The misalignment is recovered.
3.8.3.7 Consistency Status Diagnostic ( Q3 )
The Consistency Statuses are:
– Fail to align. failure.
The following table gives an overall mapping of the values of consistency status and consistency activity.
Consistency Semantic
Status
Normal RM MIB = NE - MIB.
Not aligned NE not reachable

NE in download disable mode
NE in mark audit
Failed to align The operator can click on the Consistency Status icon, thus displaying the
report identifying the RM failed operation, i.e. the not aligned attributes and the
causes of themisalignment
Config Mismatch Notify Audit
Aligning alignment in progress

3.9 Maintenance Tracing
– J0 Section Trace Identifier Set / Modify
– J1/J2 Trace Identifier
– Path Trace
– Tandem Connection
– Monitoring function (POM) on intermediate points
3.9.1 J0 Section Trace Identifier Set / Modify

SCOPE
The mechanism of section trace identifier ( byte J0 of the RSOH-Regenerator Section OverHead ) is used
to control the continuity of the trail in the regenerator section.
Trace Identifier is supported by ADM and DXC NEs according the following rules:
-Section Trace Identifier is supported only on SDH ports
-Section Trace Identifier is supported if a dedicated info model package ( rsTrailTraceSource/SinkPack-

age) is instantiated ( under the rsTTP related to the SDH port )
3.9.1.1 J0 Trace Identifier Set/Modify Virtual to real NE
The operation is not allowed if the port belongs to a virtual NE (external network reference), even if the
user can perform the operation on the other involved physical port.
3.9.1.2 J0 Trace Identifier Set/Modify
CONDITIONS
Definition or change of J0 is available only for an already Implemented physical connection
SEQUENCE
a) To configure the Section Trace Identifier, the user has to point to the involved physical connection
and issue the menu Configuration: Trace Identifier: Set/Modify/Read. See Figure 727.

Figure 727. Physical Conn: Configuration: Trace Identifier
b) The section trace identifier wizard is displayed. See Figure 728.

Figure 728. Section Trace Identifier wizard: Step 1
c) In this step the user can select either Set/Modify or Read the Section Trace Identifier. Select Set /
Modify. The Section Trace Identifier wizard: Step 2 is displayed. See Figure 729.herebelow.

Figure 729. Section Trace Identifier wizard: step 2
The two ports ending the physical connection are presented.
For each supported port the user can configure:
– Sent Trace Identifier
– Expected Trace Identifier
– Enabling/disabling of the Trace Identifier mismatch detection. It specifies if the detection of the Trace
Identifier mismatch is enabled or disabled
Mode1: 16 bytes string (the first byte used for CRC-7)
N.B. Expected Trace Identifier value may be different from Sent Trace Identifier if regenerators are
present along the physical connection.

Figure 730. Section Trace Identifier dialog box.
d) To prevent traffic loss the user has to perform the configuration operations in the following sequence:
1) Disable the Trace Identifier mismatch detection by setting to FALSE the Expected Trace Iden-
tifier Enabling
2) Configure the Expected value of one port to the desired value
3) Configure the Sent value of the other port to the desired value
4) Click on Finish to update the values in the equipments
5) Open again the Section Trace Identifier wizard on the same physical connection and Enable
the Trace Identifier mismatch detection of the previously disabled port by setting to TRUE the
Expected Trace Identifier Enabling
e) Implement the physical connection with the trace identifier enabled
3.9.1.3 J0 Trace Identifier Read
SCOPE
The user can ask to read the values of the received Trace identifier on the physical connection if the trace
identifier handling has been enabled on the related port.

SEQUENCE
a) To read the Section Trace Identifier, the user has to point to the involved physical connection and
issue the menu Configuration: Trace Identifier: Set/Modify/Read. See Figure 727.
b) The section trace identifier wizard is displayed. See Figure 728.
c) In this step the user can select either Set/Modify or Read the Section Trace Identifier. Select Read.
The Section Trace Identifier wizard: Step 2 is displayed.

3.9.2 J1/J2 Trace Identifier
SCOPE
The mechanism of trace identifier ( byte J1 of the VC-4 / VC-3 or byte J2 in the VC-12 ) is used to control
the continuity of the trail / path.
Figure 731. Trail: Configuration: Trace Identifier Management

a) From the Trail Routing display point to the trail icon and issue Configuration: Trace Identifier. The
window of Figure 732. is presented.
Figure 732. Trace Identifier wizard: Step 1

b) Click on Next button, thus passing to Trace Identifier definition, as per Figure 733.
Figure 733. Trace Identifier definition
c) Enter the desired values for Sent Trace Identifier ( max 15 characters ) and click on Finish button
to confirm.
3.9.3 Path Trace

DEFINITION
The trace identifier mechanism is used to control the continuity of a path/trail.
The end point of the transport (path/HO-trail) can be configured to send in the ongoing/egressing direction
a so-called trace identifier. The trace identifier is put into the byte J1 for 140Mb/ 34Mb or J2 for 2Mb.
OPERATION
The trace identifier sent at the end points in the two directions (one for unidirectional paths) can be com-
pared with the expected value programmed by the OS on end and intermediate points in the ingressing/
egressing direction. If a mismatch is found as a consequent action the client layer (e.g. PDH) , will receive
AIS.

When a mismatch of the identifier is found a trace identifier mismatch alarm can also be generated accord-
ing to the severity defined in the ASAP.
The trace identifier can be monitored also in the intermediate points of the transport entity in the ingressing
and/or egressing direction. Also in this case the received Trace Identifier can be read. If the expected value
is programmed, an alarm can be generated.
The functionality is not managed for QB3* NEs.
3.9.3.1 Send Trace Identifier Definition/Change
CONDITIONS
Trace Identifier setup is allowed on a defined, allocated, implemented path.
SEQUENCE
The Send Trace Identifier can be defined/changed only for an already created path/HO-trail.
SEQUENCE
a) From the path list open the path pop-up menu and select Path: Configuration: Trace Identifier. See
below figure.
Figure 734. Path: Configuration: Trace Identifier

b) The Trace Identifier wizard is displayed. See below figure.

Figure 735. Path trace identifier step 1
c) Click on Next button. The Trace Identifier wizard displays step 2 dialog box, ( see below figure ), ask-
ing the operator to enter the sent Trace Identifier for Source and sink TP

Figure 736. Path trace identifier definition.
d) Click on Finish button to confirm.
3.9.3.2 Reading Received Trace Identifier
CONDITIONS
Trace Identifier reading is allowed on a implemented or commissioned path.
DEFINITION
The Path Trace functionality is supported at least by the "source" end point (if the value of the "support-
edPathTrace" attribute of the "source" end point is "unknown" the Path Trace Identifier definition is
refused). If the Path Trace functionally is not supported by the "sink" end point, the operation is accepted
to allow, eventually, the management of the functionality in the intermediate points (if supported)
SEQUENCE
The user, on the path/HO-trail routing display. selects a single CTP/NAP where the TIM ( Trace Identifier
Mismatch ) alarm is present. Choosing the "Read received Trace Identifier" , the user will see, after the
NE response, the Received and the Expected Trace Identifier.
3.9.4 Tandem Connection

DEFINITION
The Tandem connection is a mechanism defined in SDH and OTN that makes use of:

Tandem Connection Termination points (TCT) on NAP`s and/or CTP`s
Tandem Connection Monitoring points (TCM) on intermediate CTP's of the Tandem Connection
The Tandem connection allows:
– The handling of Tandem connection specific alarms.
– The collection of performance data (15 minutes unidir. and 24 hours unidir. and bidir. ) on end points
(TCT) and on intermediate points (TCM) of the TC.
– The handling of the Trace Identifiers.
– The handling of elementary Threshold Crossing Alarms on TCT and TCM
– The handling of protections inside the TC not affected from external faults (SNCP/S)
FUNCTIONAL DESCRIPTION
A tandem connection represents the part of a path/HO trail that requires monitoring independently from
the monitoring of the complete path/HO trail.
Tandem connections may be directly monitored at one end by writing and reading a portion of the original
trail's overhead.
Tandem connections cannot be overlapped in SDH while 6 levels of TCM are defined for the OTN in G.709.
PROCEDURES
In the following the Tandem Connection management procedures are described.
3.9.4.1 Tandem Connection Create
SCOPE
The scope of this procedure is to define a Tandem Connection; starting from a path/trail, the user can
select a single TP (NAP/CAP or CTP) and specify:
– The type: TCM (for CTP's) or TCT (for CTP's or NAP's/CAP's)
– The level (always 0 for SDH)
– The direction: "Ingressing" or "Egressing" for TCM
– Including Matrix" or "Excluding Matrix" for TCT. In particular, NAP' s and CAP' s can only support
"Including Matrix" TCT
– The enabling or disabling of the consequent action (i.e. the enabling or not of AIS insertion in case
of TC problems).
CONDITION
The definition is possible only when the path/HO trail is at least allocated and it is lost when the path is
de-allocated.
OPERATION
The performed checks are related to unidirectional paths only and are the following:
• An "Ingressing" TCM cannot be instantiated below a CTP with "sink" role in the cross-connection

• An "Egressing" TCM cannot be instantiated below a CTP with "source" role in the cross-connection
Following the definition of at least one TCT or TCM, on the using path/trail, an attribute specifies that a
manual TCM have been enabled.
Where possible, restrictions at NE level, should be taken into account during this definition phase.
Possible restrictions to be detected in this phase are related to:
– NE type and version.
– The support in the same TP, of TCT with more than one direction (e.g. it is not possible to have two
TCT's, before and after matrix on the same AU4 for starting and ending two different tandem con-
nections in the same TP).
– On SDH it is not possible to instantiate a TCM and a TCT on the same TP, on OTN it will be possible
at different levels
TCT and TCM are managed as new classes contained in NAP's, CAP's and CTP's.
Once created TCT and TCM have a configuration state set to defined.
The system automatically sets the ASAP OF TCT/TCM according to the following rules:
– For a unidirectional path, the ASAP of a created TCT is set depending on both the role of the related
CTP in the connection and the TCT direction ("Including Matrix", "Excluding Matrix"), i.e. is set
according to the following table
Source CTP Sink CTP
Including Matrix "All disabled" (*) "Ferf&Ais disabled"
Excluding Matrix "Ferf&Ais disabled" "All disabled" (*)
(*) "All disabled" in order to not detect the Unequipped alarm in the not used sink direction.
For a bi-directional path:

– The ASAP of a created TCT is set ""Ferf&Ais disabled"
– The ASAP of a created "Ingressing" TCM instantiated below a boundary CTP is set "None disabled"
– The ASAP of a created "Egressing" TCM instantiated below a boundary CTP is set "Ferf&Ais dis-
abled"
– The ASAP of a created TCM instantiated below a not boundary CTP is set "None enabled". This
because the functionality to instantiate a TCM below a specific not boundary CTP has to be used
for performance monitoring purpose and not for fault localization (in this case another function will
be provided to the user to activate on all the CTP's internal to the TC the monitoring function).
AUTOMATIC DEFINITION of TC termination or monitoring points
The user can ask for the automatic definition of TC for a path or a HO trail.
The command is only accepted if the path or HO trail is
– Partially terminated and there is only one boundary CTP
– Fully not terminated and there is only two boundary CTPs.

The system automatically creates the TCT for the NAP and for the boundary CTP(s).
SEQUENCE
a) To open the pop-up menu, point to the path icon from the browser window or select the path from
the path list and press the right mouse button.
Figure 737. Configuration: Tandem Connection pop-up menu item
b) Select Configuration: Tandem Connection. The Tandem Connection Management wizard opens.
See Figure 738. herebelow.

Figure 738. Tandem Connection Management wizard
The possible actions you can select from the radio buttons box are:
• Creation
• Implementation
• Consequent Actions Enabling
• Consequent Actions Disabling
• Deimplementation
• Removal
c) Select option Creation and Creation modality. You can select between AUTOMATIC and MANUAL.
If you select AUTOMATIC the system creates TCTs on NAP/s and boundary CTP/s. If
you select MANUAL, you will select the termination points

Figure 739. Action selection radio buttons
d) Tandem Connection create-step 2 allows to select manually the TPs. By clicking on the selection but-
ton, the selection list is presented, as per Figure 740.herebelow. The upper selection button allows
to select the point/s on which TCT /s is/are to be defined. The lower selection button allows to select
the point/s on which TCM/s is/are to be defined.
e) Select the termination point and click on Apply. The icon of the selected termination point is displayed
Figure 740. Tandem Connection create-step 2-TP selection

Figure 741. TCT attributes specification
f) Select TCT attributes:
– The direction: "Ingressing" or "Egressing" for TCM
– Including Matrix" or "Excluding Matrix" for TCT. In particular, NAP' s and CAP' s can only support
"Including Matrix" TCT
– The enabling or disabling of the consequent action (i.e. the enabling or not of AIS insertion in case
of TC problems).
The operation is accepted either when the TCT is defined or implemented.
In case of TCT implemented, the operation (Enabling consequent action) may affect the traffic.
If the consequent action is not enabled, the far end counters are not managed both for TCM and TCT.
g) Click on Finish button to complete the Tandem Connection definition.
3.9.4.2 Tandem Connection display
SEQUENCE
a) Point to the path icon and select path routing display. Notice that a graphical flag is drawn in corre-
spondence of the path icon. See below figure. In
addition, dedicated flags are shown for TCT and TCM .

On each TP where at least one TCM or TCT has been at least defined, a flag is set to indicate this con-
dition.
Figure 742. Path routing display ( tandem flag )

Figure 743. Path routing view: tandem flag
Figure 744. Path icon on browser: tandem connection state icon
Starting from a path, it is possible to visualize the list of TCM or TCT: select the path from the path list and
issue Search: Related Items: TCM/TCT list. see following figure.

Figure 745. Tcm/tct list selection
Figure 746. Tcm/Tct list.

On a given TCT or TCM, it is possible to visualize all the attributes (e.g. consistency status, direction, level
etc.). Select the TP and issue Show/Set Attributes.
In addition, in the NAPs view, a NAP involved in a Tandem Connection is marked by a dedicated icon.
See below figure.
Figure 747. Path NAPs view with TC
3.9.4.3 Tandem Connection Implement
The user can manually implement (i.e. create in the NE) TCT and TCM through a manual command to
be issued on single TCTs and TCMs. The single TCT/TCM must be defined; if not, the command is
refused.
The belonging path/trail must be implemented.
Once created in the NE, the TCT or the TCM takes the configuration state equal to implemented.
If, at creation time, the NE provides a KO specifying that the TCT/TCM service is not supported, the TCT/
TCM consistency state is set "failed to align" with error type "feature not supported". The user will manually
de-implement and remove TCT/TCM .

3.9.4.3.1 TCT/TCM global manual implementation
The user can manually implement all the defined TCT's and TCM's through a manual command to be
issued at path/trail level. The Path/HO trail must be implemented; if not, the command is refused.
Please refer to the above Manual Implementation of TCT and TCM for each TCT/TCM implementation
activity inside the system.
3.9.4.4 TCT/TCM de-Implement
3.9.4.4.1 TCT/TCM manual deimplementation
The user can manually de-implement TCT and TCM through a manual command to be issued on single
TCTs and TCMs. The single TCT or TCM must be implemented: if not, the command is refused.
Once removed in the NE, the TCT and the TCM takes the configuration state equal to defined.
If the consistency state of the TCT/TCM was "feature not supported", no removal is performed towards
the NE.
This operation requires also an interaction at TCT/TCM level with the management of Performance Mon-
itoring (see SDH/PM section)
3.9.4.4.2 TCT/TCM global manual deimplementation
The user can manually de-implement all the TCTs and TCMs through a manual command issued at path/
trail level. Path/HO trail must be implemented: if not, the command is refused.
SEQUENCE
a) From the Tandem Connection wizard select action button Deimplement
b) Click on Finish button.

Figure 748. Tandem Connection wizard
3.9.5 TCT/TCM global automatic deimplementation ( upon path/trail deimplement )

TCT and TCM are removed in the NE if the path or trail containing TCT and TCM is de-implemented.
This is done as an implicit activity of the path/trail de-implementation command.
3.9.6 Manual remove of TCTs and TCMs

Single TCTs and TCMs can be removed through an operator command.
The TCT/TCM to be removed must be in the defined state. If the removal is performed in "download dis-
able" mode, the information of misalignment with respect to the NE will be reported on the related TP

If, under a given CTP or NAP, all the TCTs/TCMs are removed, the flag indicating the TC point is also reset.
All the flags on TP's and path/HO trail are updated in a consistent way.
N.B. When a path/HO trail (or a portion of it) is de-allocated, the defined TCTs and TCMs are auto-
matically removed.
All the flags on TP's and path/HO trail are updated in a consistent way.
3.9.7 Monitoring function (POM) on intermediate points

DEFINITION
The user can ask to enable or disable the monitoring function on the intermediate points of a path/HO trail.
By default when a path/HO trail is implemented, the monitoring function on intermediate points is disabled.
Enabling the monitoring function on intermediate points means:
– The instantiation of the POM (Path Overhead monitoring function) on intermediate CTP's (both
egressing and ingressing according to the real availability in the NE and the path directionality)
– The enabling of all alarms on the POM.
– The enabling of all alarms on the intermediate CTP's (LOP, AIS, etc.).
When the monitoring function on intermediate points is disabled, alarms and Overhead Monitoring capa-
bility is only enabled on Nap's and on boundary CTP's.
This functionality is targeted to perform the needed troubleshooting on a not working or not properly work-
ing path/HO trail.
The enabling of this functionality is intended only as a transitory state.
The user should limit the use of this functionality in order to not overload the system
This functionality is now intentionally disabled for SNC intermediate points in ASON. The reason
is that those CPTPs are directly managed by GMRE (ACD= G$ ), so RM cannot manage them.
The user can only ask to enable this functionality when the path is totally or partially implemented (not com-
missioned).
The system enables the monitoring function only on intermediate CTP's belonging to QB3 NE's. QB3*
NE's are not taken into account.
If the path/HO trail has the Trace identifier enabled, the expected trace identifier is set also on intermediate
points according to the type of the path.
The alarms received on POM functions and on CTP's are NOT propagated to the paths and are only used
to give information to the user. The main graphical view to be used for troubleshooting is the path/HO trail
route display.
The enabling status of this functionality is represented by a global attribute of the path/trail. To be noted
that the value enabled is only referred to the NE's supporting the functionality and it has in general the
meaning of "where possible".
When a path is de-implemented the monitoring function on intermediate points is disabled first.

The enabling of this functionality is performed regardless to the state of the QB3 SDH alarm enabling sta-
tus of the belonging path/HO trail.
The inter-working between Trace identifier management, alarm enabling/disabling on paths/HO trails,
monitoring function on intermediate points, is giving from the following table
Nap and boundary CTP's in Generic intermedi-

CTP's SNCP-N ate CTP's
Trace identifier Enable trace identifier on path/HO trail
Enabling of alarms Enable path/HO trail Enable Monitoring function on intermediate

alarms points
Figures which follow show:
– How to enable POM on a path, by pointing at the path icon and issuing the following command:
Path: Configuration: POM on Ctps: Enabling
Figure 749. Path: Configuration: POM on Ctps pop-up menu.

– path routing display: all alarms on intermediate CTPs are visible
Figure 750. Routing Display: path CTP
– Trace Identifier read on a certain CTP, by issuing the command Trace Identifier: Read.

Figure 751. CTP: Trace identifier read

3.9.8 Loopback on PDH port / NAP
The following loopback commands can be launched on PDH naps/ ports:
– No Loop
– Line Loop & AIS
– Internal Loop & AIS
– Line Loop & Continue
– Internal Loop & Continue
Figure which follows shows the Manage Loop pop-up menu available on NAP.
Figure 752. Nap: Manage Loopback

EXAMPLE OF LINE & AIS loopback
In this case, as shown in the following figure, on the port corresponding to the first NAP a line loop is exe-
cuted. AIS signal is sent toward the network, detected by the far end NAP and sent back.
Figure 753. Loopback active
The NAP loopback status can be shown via Show/set Attributes of the involved NAP. see below figure.

Figure 754. Nap loopback status supervision
EXAMPLE OF INTERNAL & AIS loopback
In this case, as shown in the following figure, on the port corresponding to the first NAP a loop is executed
toward the network. No alarm is detected by the network, while AIS signal is sent on the line and detected
by the client 2 Mb equipment.
The NAP loopback status can be shown via Show/set Attributes of the involved NAP.
N.B. From RM Rel.7.4.E on the KO response from the NE is correctly managed, in case the loop-
back functionality is not supported by the NE itself.
Up to now, if the loopback functionality is not supported by the NE, the loopback, even if not per-
formed on the NE, is present on RM and the remove loopback command has to be performed in order
to remove the loopback itself from RM.
The feature allows the management of the KO response from the NE, in case the loopback func-
tionality is not supported by the NE itself. In particular:
the loopback is stored in RM only if it has been successfully executed on he NE (i.e. only when the
OK response from the NE is received by RM)
if the NE or the related EML is not reachable, the loopback command is refused and a warning is
provided to the user

N.B. In QB3* NEs, KO is already managed in the correct way.
3.9.9 Loopback commands on CTP

The following loopback command can be launched on CTP:
– Set
– Remove
Figure which follows shows the Manage Loop pop-up menu available on CTP. Point to the CTP and issue
Internal Loopback: Set to setup the loop or Internal Loopback: Remove to remove the loop.
Figure 755. CTP: Internal Loopback: Set

EXAMPLE OF CTP loopback
In this case, as shown in the following figure, on a CTP a loop is executed toward the network. AIS signal
is sent toward the network and detected by the connected NAP.
Figure 756. CTP: Internal Loopback display
3.9.10 Craft Terminal Supervision

From browser the following information are displayed:
– CT Access Granted
– CT Access Required
– CT not connected enabled
– CT Access Denied
3.10 Protection management
3.10.1 SNCP path layer switch management

The SNCP switch management commands can be applied to SNCP paths or to Bridge & Switch con-
nections in topology

Figure 757. Path:Manage SNCP menu.
Events which manage the switch position have a priority mark; in particular Forced SNCP commands have
priority greater than failure events, while failure events have priority greater than Manual SNCP com-
mands.
SEQUENCE
a) From the browser window, e.g. from the Routing display, point with the mouse at the path icon and
open the Manage SNCP pop-up menu. It is possible to obtain this menu by selecting the path icon
and selecting the Actions:Manage SNCP pull-down menu. The Manage SNCP menu allows to fur-
ther select between:
• Synchronize. This command retrieves the actual switch status of the B & S connections from
EML.

• Release. This command clears the previously issued lockout/forced/manual command. This
command is available for all types of Network Element.
• Lockout. This command either locks( forces ) the path/switch to the main route if a Set Rever-
tive command has been previously entered or locks the path/switch to the actual position if a
Set not Revertive command has been previously entered.
• Force Main . This command forces the path on the main route. The path will remain on the main
route even in case of failure. This condition can be modified only by means of the Release com-
mand.This command is available for all types of Network Element.
• Force Spare . This command forces the path on the spare route. The path will remain on the
spare route even in case of failure. This condition can be modified only by means of the Release
command. This command is available for all types of Network Element.
• Manual Main . This command switches the path to the main route. The switch is rejected in
case of failure and if a previously issued Force/Lockout command is active. The Force/Lockout
condition can be cancelled by means of the Release command.
• Manual Spare . This command switches the path to the spare route. The switch is rejected in
case of failure and if a previously issued Force/Lockout command is active. The Force/Lockout
condition can be cancelled by means of the Release command.
• Set Revertive. This command causes the path to revert to the main route after the repair of the
involved objects. The Wait to restore time parameter is managed at Equipment layer. This com-
mand is available for all types of Add and Drop Multiplexers; it is not applicable to 1641SX cross
connect.
• Set not Revertive. ( default ) The path does not revert to the main route after the repair of the
involved objects. This command is available for all types of Add and Drop Multiplexers; it is not
applicable to 1641SX cross connect.

Figure 758.shows an example of display of a B & S connection in topology
Figure 758. Example of display of a B & S connection in topology.
The switch status can assume the values:
– M main. It means that the switch is turned to the main position
– S spare. It means that the switch is turned to the spare position
– C service. It means that the switch ( only for D & C ) is turned to the service position
The last operation executed on the switch can assume the values:
– F( forced) . It means that the switch has been forced.
– R (released). It means that the switch has been released.
– L (lockout) . It means that the switch has been locked.
– None. No action has been executed on the switch.
The Revertive operation mode icon is present if the switch has been set to Revertive.
b) After the execution of a Manage SNCP command a report is forwarded to the operator.
See Figure 759.

Figure 759. Report.
Figure 760. Connection in topology attributes.

N.B. For a SNCP path the attribute SNCP status can be:
– unknown. The actual position of one/more switch/switches is unknown. A Manage

SNCP: Synchronize command is required.
– idle. No force/manual command has been previously entered.
– forced SNCP. At least one switch is set to forced.
– manual SNCP. At least one switch is set to manual.
N.B. For a SNCP trail the same commands apply. Notice that The trail can be terminated with an
SNCP connection only in case of 1661SMC equipment with Enhanced connectivity (able to cre-
ate an SNCP connection with grooming). Otherwise the trail must utilize an unprotected phys-
ical connection and create the SNCP connection in another NE.
HO-Trail protected with enhanced connectivity
SPARE
LO-LCs
LO-CTPs
LO-CTPs
MAIN
HO-Trail protected without enhanced connectivity
SPARE
LO-LCs
LO-CTPs LO-CTPs
MAIN
Figure 761. HO-Trail with and without enhanced connectivity

3.10.2 Multiplex Section Layer switch management
3.10.2.1 Automatic Protection Switch in 2-fiber MS-SPRING
3.10.2.1.1 Bridge and Switch
In case of fiber breaks, the APS for 2F MS-SPRING uses a synchronized sequence of 'bridge' and 'switch'
operations that modify the internal connections of the two NEs adjacent to the failure.
The 'bridge' operation on the East (West) side has the effect of routing the outgoing high priority
West (East) traffic also to the outgoing protection East (West) capacity.
When a 'switch' operation is in effect on the East (West) side, all of the connections that have
as a source an Au4 belonging to the West (East) working capacity are replaced by connections
that have as a source the incoming East (West) protection traffic.
when one end of a connection is modified from working traffic to protection traffic, the Au4 of the protection
traffic that replaces the Au4 of the working traffic has an index that is always (n/2) greater (i.e., in case
of Stm16 aggregates, the Au4 #2, is substituted by the Au4 #10, where 10 = 2 + (16/2) ).
Note that the 'bridge' and 'switch' operations on the same side can co-exist (this is the typical case,
indeed): since they affect different class of connections, the final configuration is given by the sum of the
two.
W E W E
W E W E
protection
BEFORE working AFTER
Figure 762. Effect of a BRIDGE EAST

W E W E
W E W E
protection
Figure 763. Effect of a BRIDGE WEST
W E W E
W E W E
protection
Figure 764. Effect of a SWITCH EAST

W E W E
W E W E
protection
Figure 765. Effect of a SWITCH WEST

3.10.2.1.2 Steps of a ring switch
In case of failure of a span, the failed span is replaced with the capacity of the protection traffic of the spans
not affected by the failure (note that the protection switching can also be triggered by a command issued
by the OS, as will be described in the following). This situation is the result of the following sequence of
steps, synchronized via a protocol that uses the byte K1-K2 of the MSOH;
1) The node that detects the failure (Tail End), sends a Bridge Request to the node that is adjacent
along the direction where the failure is present (that becomes the Head End): this Bridge
Request is sent on both the long and the short path.
2) The intermediate nodes substitute all of the connections pertaining the low priority traffic with
bypasses among the two aggregates.
3) When the Head End receives the Bridge Request on the short path, it sends back to the tail end
a Reverse Request on the short path and a Bridge Request on the long path.
4) When the Head End receives the Bridge Request also on the long path, it performs a ring Bridge
and sends to the Tail End, on both paths, the notification of this new status
5) When the tail end receives, on the long path, the bridge request from the Head End it performs
a ring bridge and sends the notification of this new status to the head end, using both paths.
6) When the tail end receives, on the long path, the notification of the execution of the bridge on
the head end, it performs a ring bridge and switch and sends the notification of this new status
to the head end, using both paths.
7) When the head end is aware of the bridge and switch activated on the tail end, via the report
of the bridge status on the long path, it performs a switch, so that both ends are now in bridge
and switch
When a protection switch is in effect, all of the protection capacity is used to recover the working traffic;
in this situation no low priority connections can be established on the protection capacity and it is required
that, in order to avoid mis-connections, all of the tributaries that terminate a low-priority connection output
an AIS signal (this operation is called 'squelching').
After the failure has been removed, a similar sequence of operations is performed by the head and tail
end; if the failure was single, the reverse procedure can starts after a specified time interval, called Wait
Time to Restore (WTR).

3.10.2.1.3 Example of ring switch in a 6-nodes 2f MS-SPRING
The following diagrams depict the sequence of operations that occur in a six-nodes ring when a single
failure (signal degrade, in this case) occurs on the fiber that carries the traffic from node '2' to node '3'.
Figure 766.depicts the initial situation, where a tributary at node '1' is connected with another tributary at
node '4', using the clockwise direction for the path going from node '1' to node '4' . The remaining capacity,
both working and protection, is used to source and terminate unequipped VC between the adjacent nodes.
Tributary
e w w
w e
1 2 3
6 5 4
e w
w e w e
Tributary
Working Channels
Protection Channels
Figure 766. :Example of six nodes ring
a failure affects the connection from node '2' to node '3'.

Tributary
e w w
w e
1 2 3
6 5 4
e w
w e w e
Bridge
Working Channels Tributary
Protection Channels Switch
Figure 767. Step 4: Final situation
A squence of bridge and switch operations occurs. The final configuration is shown in Figure 767.
3.10.2.2 Squelching in case of isolated nodes
With some classes of multiple failures, some nodes in a 2f MS-SPRING could be isolated, i.e. unreachable
by the other nodes. When a node is unreachable, it can be demonstrated that, due to the bridge and switch
operations that are performed by the ring itself, some tributaries could be misconnected, i.e. connected
to the wrong source or destination. In order to avoid this effect, a technique called SQUELCHING consists
in the injection of an AIS signal on the VCs that come from or go to an isolated node.
The squelching technique requires that two different squelching actions are taken on the HVC and on the
LVC. The HVC are squelched only at the switching nodes, i.e. at the nodes that perform bridge and switch,
while the LVC are squelched where they are terminated. Furthermore, a different squelching action is
taken on the HVC according if they are 'accessed at the LVC level' or not; in detail, if the VC4 is composed
of VC12 that are terminated at different nodes, the squelching performed at the switching nodes must be
removed after the final bridge and switch state has been reached: this is necessary in order not to loose
LVCs that would be otherwise unnecessarily squelched.

3.10.2.3 MS-SPRING Interworking
When a 2f MS-SPRING is interworked with another ring (either SNC/I or MS-SPRING), the interconnec-
tion of the two is performed by connecting two pair of nodes per ring with HVC connections, as shown
in the following figure.
Each VC4 that has to cross the ring boundary (only HVC level ring interconnections are considered here)
must be output by two nodes, one of which, the primary service node (PSN) drops it and continues to the
secondary service node (SSN). In the opposite direction, the SSN inserts a copy of the VC4 into the ring
and the PSN selects between the VC4 coming from the SSN and the VC4 that can be locally inserted.
The selection is performed on the basis of the path-AIS.
The protection mechanism works on the hypothesis that the other ring selects one of the two version of
the incoming VC4 and transmits two identical copies of the VC4 towards the PSN and the SSN (this is
guaranteed if the other ring is an MS-SPRING or an SNC/I ring).
Note that the PSN and the SSN need not to be adjacent and need not to be the same for all of the VC4
that cross the ring boundary: i.e. each crossing VC4 has two associated nodes that act as PSN and SSN.
It is also possible to connect two rings at more than two points, but this is usually unfeasible with the normal
ring topologies and has not been considered here.
This document does not address the case where the VC4 that crosses the boundary is terminated at its
primary service node.
2f MS-SPRING
Primary Secondary
Service Service
Node Node
SNCP or MS-SPRING
Figure 768. Drop and Continue at the service nodes.

3.10.2.4 Provisioning of the APS Controller
The APS Controller blocks need a set of configuration information for properly execute their functions.
First of all, the APS Controller must know whether it shall operate or not, e.g. because the ring is protected
with a different strategy: this information will be called 'APS Controller enabling' and can be considered
as a binary value (enabled or disabled).
APS Controller must be explicitly activated to exchange K1 and K2 bytes with the other N.E.; also this
information can have only two values (activate or inactive). Note that an enabled but inactive APS Con-
troller is in a well defined state, which corresponds to a particular set of transmitted K1-K2 bytes, 'default
APS bytes'; It is required that the 'default APS code' on K1-K2 is a pattern of 'all zeroes'
An enabled APS Controller (even when it is inactive) needs to know the 'node identifier' of the N.E.
where it is operating; the node identifier is a number in the range 0 through 15, and is unique within
the ring.
An enabled and active APS controller must be aware of the topology of the ring, i.e. of the
sequence of nodes (ring map) that is encountered when traversing the ring in a specified direction
(e.g. clockwise); the crossed nodes are identified by their 'node id' and may not be more that 15 (the total
number of N.E. in a 2F MS-SPRING is 16) neither less than 2.
A final parameter that must be known by the APS Controller is the Wait Time to Restore value; this value
may range from 0 to, at least, 15 minutes (a step of 1 minute is accepted);
3.10.2.4.1 Squelching tables: definition and size
The 'HpSq' block needs to receive two sets of 'squelching tables' that contain some routing information
that is necessary to properly identifiy where and when inject AIS.
The first set is composed of four tables that will be called, in the following, 'VC4 squelching tables'. There
is a VC4 squelching table for each aggregate input and output of the network element. The structure of
the four tables is identical: for each incoming (or outgoing) High Priority Au4 (i.e. Au4 1..2 for the Stm4
and Au4 1..8 for the Stm16) the table must contain the source and the destination nodes of the transported
VC4; note that, in case of ring interworking, the VC4 can have two source nodes . It is also allowed for
a VC4 to have multiple destination nodes (up to 15 in the worst case). It can be demonstrated that only
one source and one destination node is necessary for the VC4 squelching tables, namely the farthest
source node and the fartherst destination node.
If a VC4 contains LVC that have different source or destination nodes, the VC4 squelching table must indi-
cate this situation: for this field a binary value is enough.
If a fixed size table is chosen, the size of each row of each VC4 squelching table is 9 bits, where this num-
ber is obtained by adding 4 bits for the source node identifier, 4 bits for the destination node identifier and
1 bit that indicates whether the VC4 is accessed at the LVC level or not. Multiplying the row size and the
number of rows and the number of tables, the final value of
4 x 8 x (4 + 4 + 1)= 288 bits(36 Bytes)
is obtained
The second set of squelching tables contains, for each terminated LVC, the indication of the source node
of the LVC itself. Also in this case an LVC may have two source nodes that musy be indicated in the table,
regardless of which is the primary and which is the secondary). In the worst case (8 VC4 structured as
63 TU12, all with double source) the following total size is obtained:
63 x 8 x (4 + 4) =4032 bits(504 Bytes)
As said before, the VC4 squelching tables have to be provided to all of the nodes of the ring, while the
LVC tables are required only at the nodes where LVC traffic is terminated.

3.10.2.4.2 Squelching tables: example
In order to explain with the sufficient detail level, an example of squelching table computation is presented.
In the following figure, a 7 node ring is considered, where the node id are represented by capital letters
from A to G. Five connections are supposed to exist, three regarding VC12 and two regarding VC4:
– VC12 #1 of VC4 #1 is supposed to be inserted at node A into the VC4 #1. The exit point of this VC12
is node G. Due to the connectivity restrictions, the VC12 will have not changed neither the TU12 nor
the Au4 along the path.
– VC12 #2 of VC4 #1 has two sources, due to the ring interworking: node B is the secondary service
node, while node C is the primary. The destination node is F. Vc12 #2 always occupies the TU12 #2
of the VC4 #1 that is transported into the Au4 #1.
– VC12 #63 of VC4 #1 has one source node, E, and two destination nodes, namely F and G: i.e. this
is a point-to-multipoint connection. The Vc12 #63 always occupies the Tu12 #63 of a VC4 that always
occupies the Au4 #1.
– VC4 #2 follows the same path of Vc12 #63 of VC4 #1.
– VC4 #8 has two sources, A and B, respectively the secondary and primary service nodes, and has
two destination nodes, E and F.
WEST EAST
A B C D E F G
VC12 #1
VC4 #1 VC12 #2
SS PS
VC12 #63
VC4 #2
VC4 #8
SS PS
Figure 769. Example of squelching table configuration
The VC4 squelching tables for the nodes represented in the example are listed in the following. Note that
a VC4 containing LVC is terminated each time an LVC is inserted and or dropped, so that the only node
where the VC4 #1 is not terminated is node D.

VC4 squelching table for node A
Node A
West Input West Output East Input East Output
From To LVC From To LVC From To LVC From To LVC
VC4 #1 A G YES
VC4 #2
VC4 #8 A F NO
LVC squelching table for node A (no entries)
Node A
From:
VC4 squelching table for node B
Node B
VC4 #1 A G YES A G YES
VC4 #2
VC4 #8 A F NO A F NO
LVC squelching table for node B (no entries)
Node B
From:

VC4 squelching table for node C
Node C
VC4 #2
LVC squelching table for node C (no entries)
Node C
From:
VC4 squelching table for node D
Node D
VC4 #2
VC4 squelching table for node E
Node E
VC4 #2 E G NO

LVC squelching table for node E
Node E
From:
VC4 squelching table for node F
Node F
VC4 #2 E G NO E G NO
VC4 #8 A F NO
LVC squelching table for node F
Node F
From:
Vc12 #2 of VC4 #1 B, C
Vc12 #63 of VC4 #1 E
VC4 squelching table for node G
Node G
VC4 #1 A G YES
VC4 #2 E G NO
VC4 #8

LVC squelching table for node G
Node G
From:
Vc12 #1 of VC4 #1 A
Vc12 #63 of VC4 #1 E
3.10.3 Management of switches at RM interface

An MS-SPRING can be created on the map by means of the command Construction: Add Object: Ring:
MS-Spring... Checks are performed during validation and activation phase: only 1661SMC and 1664SM
and 1670SM are allowed.
Implementation, de-implementation and removing can only be performed on the complete ring and not
on single connections.
During the implementation, RM creates :
– the MS-Spring protection block

– protected MS-TPs
– protected MS-Trails
and sets the Node Identifier in the MS-SPRING.
The payload configuration activity after ring implementation creates only 8 AU4s and any change of the
payload configuration requires the specification of 8 AU4s.
On the protection block, the following operations are available:
– synchronize
– release
– force east, west
– lockout east, west
– manual east, west
– change Wait To Restore time (5, 300, 600, 900 sec)
The position of the protection block is displayed using 4 attributes:
– Switch position (displayed on main view) : unknown, idle, bridge east or west, bridge & switch east
or west, pass through
– Switch cause (displayed on main view) : Failure, Restoration, Operator Request, None, Unknown.
– Active Operator Command : Release, Lockout, Force, Manual, None.
– Pending Operator Command : Release, Lockout, Force, Manual, None, Synchronize. It is the com-
mand under execution. It is set to "none" when the answer (OK or KO) is received from the EML.
At the beginning all the switch positions and switch causes are set to unknown, the pending is set to none.
After a parametric time T1, the managing process performs a synchronization for a parametric number
N of switches with the position set to unknown (i.e. not yet synchronized manually or through an event).
After another parametric time T2, the operation is repeated with another set of N "unknown" switches. Dur-
ing this automatic synchronization, the pending command of the switches under operation is set to Syn-
chronize.

3.10.3.1 Display of the Protection blocks
A view of all the MS Protection Blocks in a MS-SPRing is available in the browser. To display this view,
execute the following procedure:
a) From the browser point with the mouse at the network and open the pop-up menu. Select item
Search: All related items... ( see Figure 770.)
b) From the selection box select item NPAs and click on OK button. The NPA drawing window is dis-
played.
Figure 770. MS-Spring: Display All related items...
Figure 771. Examples of actual position of the switches.
3.10.3.1.1 Squelching Info
All the HO SbnConn's belonging to HO-Paths and HO-Trails in MS-SPRING topologies include squelch-
ing Information (4 values : West - Src / West Dst / East Src / East Dst end Nodes Identifiers). Squelching
Info are also set for the connections between HO-TTP and HO-CTP.

For broadcast paths, the squelching information related to legs is evaluated run time during the imple-
mentation (when multiple legs and pass-through are merged into a single broadcast connection).
3.10.3.1.2 Linear MS protection (1+1)
This feature is only applied to ADMs.
The management of the protection is done by the EMLs. On RM side, only the presence of the protection
is displayed to the operator.
In addition to the alarm already foreseen in case of failure on both the fibers involved in the linear MS pro-
tection, a new alarm is emitted at SEN-IM level also when a failure on a single fiber will occur. This will
warn the operator on the reduced degree of protection.
3.10.3.2 4-F NPE RING Switch Management
A view of all the MS Protection Blocks in a MS-SPRing is available in the browser. To display this view,
execute the following procedure:
a) From the browser point with the mouse at the network and open the pop-up menu. Select item
Search: All related items...
b) From the selection box select item NPA and click on OK. The NPA list is displayed.
c) Point to the 4-F NPE RING NPA and click on NPA view button. The NPA view is displayed.
d) From each protection block it is possible to issue the ring switch and span switch commands.
The effect of the Span Switch and Ring Switch operations is described in Section Technical Annexes, NPE
ring.
The above mentioned commands are mainly used for maintenance purposes. See Section MAINTE-
NANCE, Chapter 4 Diagnostic of the NPE Ring.

3.11 Performance Monitoring
3.11.1 Introduction
The aim of the Performance Monitoring at RM side is to allow the user to monitor transport objects, i.e.
the objects path and trail. The monitoring activity is executed on the involved tps.
In order to monitor transport objects, the user creates objects called " Measures ", which are performance
monitoring work sessions, defined by a set of characteristics according to the Customer's needs.
After creating the measure, the user must associate (correlate) to it the transport/s to monitor and the ter-
mination points (TPs).
The status of the measure can be:
– Planned. This means that the measure has been defined.
– Active. This means that the collection activity is working.
– Stopped. This means that the collection activity is terminated. The collection activity can restart upon
entering the Activate command.
To activate a measure on paths/trails, the following conditions are mandatory:
• the path/trail working state = normal

• the path configuration state = implemented or commissioned
• the trail configuration state = configured at LO
Figure 772.shows the PM menu items in the browser window.
Figure 772. PM functional buttons in the browser window.
In addition, the system supports PM at level of MS trail. See dedicated para PM on Multiplex Sec-
tion. The following mechanisms are allowed:
• the manual start-up of MS PM through specific MS Trail(s) selection
• the automatic start-up of MS PM on all the MS Trails that are created upon physical connection
implementation
• to launch the off-line tool for automatic PM startup on MS-trail on an already managed network
N.B. Only one measure can be active at the same time on a PM termination point for a given gran-
ularity value ( 15 ', 24 h )
N.B. For a path terminated to all virtual objects, the relevant tps cannot be automatically correlated.
In the following paragraphs it is given a description of the main procedures relevant to PM.
N.B. TCA handling on 24 Hours Measurements

This feature allows the definition of TCA profiles on 24h unidirectional measurements.
The user is able to correlate a TCA to 24h measurements. For new NEs, the Maintenance measurement
should to be used but, for compatibility, also the QoS measurement is accepted.
3.11.2 Creating the Measure

SEQUENCE
a) From the Browser select the PM domain and open the pop-up menu. Select the command Create:
Measure. The object creation dialog box is presented.
Figure 773. Measure Creation dialog box.
b) Enter the following attributes:
– measure name (userlabel) . The measure name can be modified, by means of the SHOW/Set
Attributes command, only if the measure status is PLANNED.
– Objective. Possible values are:

• Qos ( quality of service ). Counter started are: BBE, ES, SES, UASbidi
• Maintenance. Counter started are: BBE, ES, SES, UAS near end, UAS far end.
• Transport State NOT SUPPORTED
• Qos for Tandem Connection. The transport being associated is involved in a tandem connection
and Counter started are: BBE, ES, SES, UASbidi
• Maintenance for Tandem Connection. The transport being associated is involved in a tandem
connection and Counter started are: BBE, ES, SES, UAS near end, UAS far end.
– granularity. The granularity is the monitoring frequency, i.e. the frequency of historical data counters
grouping. You can select:
• 24 hours . Data are grouped per day.
• 15 minutes. Data are grouped per quarter of hour.
– Monitored layer. You can specify the layer of the objects monitored by the measure:
• HO - high order
• LO - low order
• No layer restriction
• CBR
• DATA
• MS
– Counters provided. If its value is:
• TRUE, the counters belonging to granularity periods will be collected, when the measure is acti-
vated
• FALSE, the historical data counters will not be collected, even when the measure is activated.
This implies that the goal of the measure is to set Threshold Crossing Alarm profiles on the ter-
mination points only.
– Add internal transport tps. If set to True, the internal pmtps are also set.
– defaults tps. You can specify:
• TRUE. The PM transport is created with some default TPs automatically correlated ( for each
of them a PMTP instance is created )
– One pmtp ( NAP/CAP type ) for a bidirectional transport is enough because the NE pro-
vides the information relevant to both ends (NEAR END + FAR END).
– If the path is broadcast all sink ends are monitored. (Only real ends are considered.). Vir-
tual NAPs or CAPs are not automatically monitored; the closest real CTP ( boundary CTP
) will be monitored.
• FALSE. Only the PM transport is created; no pmtp is created.

– start/end time. If you do not specify start/end time, you can subsequently activate manually the mea-
sure by means of the command Measure Start, otherwise the Measure will be started at the Start
Time and stopped at the Stop time.
– Automatic Purge of the Measure (TRUE/FALSE)
– Purge State of the Measure (when stopped/when terminated)
– Automatic deletion Hystorical Data (TRUE/FALSE).
– Number of historical data kept in db it is the no. of months of permanence for 24H measure
or the no. of weeks of permanence for 15m measure
c) Click on button Create.
d) To verify the successful creation of the measure, check on the Measure Create report window.
e) You can now navigate from the pmDomain, in order to find the new measure icon.( from the Browser
pmDomain select Search related items : Measures. The Measure List is presented).
Figure 774. PM domain related items

Figure 775. Measure list

3.11.3 Transport object Correlation to the Measure
INTRODUCTION
A measure can monitor paths and trails, i.e. transports of type path and transports of type trail. The
transports have to be correlated to the measure.
SEQUENCE
a) Select the Measure from the list. The Measure must be planned.
b) Select the menu Actions: Correlate/Merge. You can further select among:
• Correlate paths/trails
• Correlate reports
• Uncorrelate reports
• Merge measures
Figure 776. Measure: Actions pull-down menu.

c) Select Correlate: paths/trails. The Object Correlation window is presented. The measure is already
contained in the window . Drag and drop the paths/ trails to correlate to the window drop area.
Figure 777. Transport correlation to a measure
d) Click on the Create button.
e) To verify that the correlation has been properly entered, navigate the browser in order to find the icon
of the PMtransport which has been just created. From the browser point with the mouse to the mea-
sure icon and issue Display: Related items: PMTransports. The PMTransport icon/s are displayed
in the browser window.
N.B. The correlation Measure-Transport can be also executed starting from the transport (path /trail)
by using the relevant pop-up menu.

Figure 778. Path: Actions:PM: Add Measure
The Add measure dialog box opens. Click on Measure list button.
MEASURE LIST
Figure 779. Performance Measurement: Add to dialog box
Select the measure to correlate and click on Apply. The measure icon is present in the correlate area. Click
on Finish to confirm.

Figure 780. Correlate measure to path
3.11.4 Tp's correlation to the Measure

INTRODUCTION
For a transport ( path or trail ) to be monitored by a measure, at least one TP- termination point ( NAP,
CAP or CTP) of the transport must be monitored by the measure. This means that the measure, when
activated, will collect PM_ DATA relevant to the TPs correlated. To indicate that a measure has to monitor
a certain transport in a certain TP, the involved TP has to be correlated to the measure; the result of the
correlation procedure is that a new object is created: the pmTP. This object is created under the pmtrans-
port.
LIMITATIONS
In the correlation of a TP to a Measure, the following limitations apply:
– A TP can be correlated to a measure ( and so a PMTP can be created under a measure ) only if the
transport the TP belongs to is already correlated to that measure
– A TP can be monitored by at most 2 ( two ) activated measures at the same time, and the measures
must have different pm-Granularity values.
– A virtual TP cannot be monitored.
– The measure state to correlate can be planned, activated or stopped.
SEQUENCE
a) Select from Browser view the ctp / nap / cap to correlate. They must belong to a transport which is
already correlated to at least one Measure.
b) Issue Performance Monitoring: Correlate to Measure pop-up menu item.
c) The tp is correlated to the Measure which is already correlated to the relevant path. By using the
Browser you can verify the tp correlation to the Measure, looking for the newly created pmTP.

Figure 781. Performance Monitoring: Correlate to Measure
N.B. If the transport object the TP belongs to ( e.g. a path ) is correlated to many measures and you
issue the command to correlate the tp to a Measure, the system provides a measure selection
dialog box, in order to select which measures you want to correlate the tp to.
In addition ,from Measure: Search related items: PMtp , the list below is displayed.
Figure 782. Measure TP list

Figure 783. PM tp related items

Among PM tp related items you can select the PM tp view. See figure which follows.
Figure 784. PM tp view

3.11.5 PM on Multiplex Section
The feature allows:
• the manual start-up of MS PM through specific MS Trail(s) selection (described in the following)
• the automatic start-up of MS PM on all the MS Trails that are created upon physical connection
implementation (refer to Administration Guide, chapter Configuration, para Environment vari-
ables configuration, Performance Monitoring Customization, Automatic PM startup on MS-
trail)
• to launch the off-line tool for automatic PM startup on MS-trail on an already managed network
(refer to Administration Guide, chapter Procedures, para Procedure for automatic PM startup
on MS-trail)
MANUAL PM STARTUP ON MS
a) Create the measure. Select:
– measure name (userlabel) .
– Objective: Maintenance. Counter started are: BBE, ES, SES, UAS near end, UAS far end
– granularity. Select 24 hours
– Monitored layer. Select MS or No layer restriction
b) Select the MS trail and issue PM: Add measure
Figure 785. MS trail: PM: Add measure
c) The Correlate measure wizard is presented

Figure 786. Correlate measure wizard
d) Click on Get Measures button. The list of the Measures is displayed. Select the related measure and
click on Apply
Figure 787. List of Measures
e) In the Correlate measure wizard click on Finish

Figure 788. Correlate measure wizard: Finish
f) From the Physcon structure select the MS trail and click on Monitoring Measures
Figure 789. MS trail: Monitoring Measures
g) The list of the measures is displayed. Select the measure and click on button PM Transports.
Figure 790. Measure: button PM Transports.

h) The list of the PM Transports is displayed. Select the Transport and click on button PM Tps.
Figure 791. Transport: button PM Tps
i) The list of the PmTps is displayed. In this case only one is present, due to the fact that the involved
trail is connected to an external network.
Figure 792. List of the PmTps
N.B. Performance Measurements on trail start in accordance to the following rules:
– if the trail is unidir, only near-end counters are started on sink CAP.
– if the trail is bidir and maintenance, near-end counters are started on both CAPs.
– if the trail is bidir and QoS, near-end and far-end counters are started on both CAPs.
– if the trail is not- terminated, counters are started on CAP or CTP.
3.11.6 Force Collection

The Force collection command launches an asynchronous data collection operation on the NEs.

The Force Collection can be issued from the Measure via menu Measure: PM data: Force collection or
from a single path/trail/monitored TP. The relevant command is for example, Path: PM data: Force Col-
lection.
The Force collection command applies only to 15 minutes granularity.
Ì The Force collection is executed globally, on the entire NE. The operation is asynchronous, no
response messages, such as <collection in progress..> are sent by the NE. Then the display
of the retrieved data is not subsequent to the issue of the command. The display of the data,
after the successful collection operation on NE, is available at the subsequent collection time
instant.

3.11.7 PMTP Attributes
If you issue a Show/Set attributes of a PMTP object, you will get the dialog box of Figure 793.
Figure 793. PMTP Show / Set Attributes
The PMTP main attributes are:
• REQUIRED SIDE. The REQUIRED SIDE is the direction of the signal to monitor. It can be set
by the 1354RM to one of the following values:
– sink
– source
– both
Examples of assignement of the SIDE are given in paragraph 3.11.7.1 herebelow.
• ACTIVE SIDE. It represents the actual direction monitored on equipment for the specified TP.
• REQUIRED MODE. It represents the required mode to start the monitoring on the PMTPs.
The Mode (UNI or BIDI) determines the type of UAS counter to be collected by EML (SH/WX)
for a certain tp. The possible values are:
– unidirectional, RM will receive the values of two counters: Near End UAS (Unavailable
seconds) and FEUAS (Far End Unavailable Seconds)
– bidirectional, RM will receive the values of only one counter BID-UAS which represents
the logical OR function of the Near End UAS (Unavailable seconds) and FEUAS (Far End
Unavailable Seconds) counters.

• ACTIVE MODE. It represents the actual mode monitored on equipment for the specified TP.
REQ SIDE and REQ MODE are automatically selected by RM after executing the command
" Correlation of the tp to the measure ". They are chosen taking into account:
• the equipment type the tp belongs to
• the used direction of the tp (monodirectional / bidirectional)
• the type of tp ( ctp / nap / cap )
• ACTIVE PM. This attribute is set to TRUE if the RM wants to have PM available on that TP, e.g.
when the measures passes from the status planned to the status activated. This attribute is
set to FALSE if the RM does not want to have PM available on that TP, e.g. in case of transport
rerouting.
• sink/source REQUIRED TCA. This attribute is the name of the desired Threshold Crossing
Alarm profile on the termination point.
• sink/source ACTIVE TCA. This attribute is the name of the actual Threshold Crossing Alarm
profile on the termination point.
N.B. ACTIVE SIDE/ACTIVE MODE are not meaningful when the measure is planned.
After activating the measure it is possible to show the actual ACTIVE SIDE and the actual
ACTIVE MODE of the tp in the PMtp show/set attributes window. These attributes show the sit-
uation present on the equipments. If the PMTP is not consistent, this means that at least
one difference between Required and Active attributes is present.

3.11.7.1 Examples of assignement of the attribute SIDE
An example of assignement of the attribute REQUIRED SIDE for a bidirectional path is shown in Figure
794.and Figure 795.Notice that for a bidirectional path the involved CTPs ( if correlated ), become PMTPs
marked both as sink and source. Figure 796.shows an example of assignement of the attribute SIDE for
a unidirectional path.
NE-A NE-B
ctp ctp
MAIN
sink
B&S
B&S
ctp ctp source
ctp
SPARE
sink
Figure 794. Side of the pmctps in a b&s connection ( signal from NE-A to NE-B )
NE-A NE-B
ctp ctp
MAIN source
sink
B&S
ctp ctp
SPARE source ctp
Figure 795. Side of the pmctps in a b&s connection ( signal from NE-B to NE-A )
ctp ctp
nap nap
source source sink sink
Figure 796. Side of the ctp/nap for a unidirectional connection

3.11.8 Counter Report Profile Creation
INTRODUCTION
Counter reports Profiles are objects which allow the automatic generation and sending of documents (
Counter Reports) containing all the data collected by the measure in a range of time (T1, T2).
The document name derives from the measure userlabel by adding the character " _ "( underscore ) as
prefix and the characters "_CO " as suffix. As an example, the document name of the counter report asso-
ciated to the measure "MEASURE1" will be "_MEASURE1_CO".
First of all, the counter Report Profile instance has to be created, then it must be correlated to all the mea-
sures that require the generation of documents; only when the measures will be activated, the document
will be periodically generated and sent.
A counter report profile can be associated to more than one measure at the same time.
SEQUENCE
a) To create a counter report, from the browser, point to the PM domain and issue the command
PMdom: Create: Counter Report. Enter:
• userlabel, to identify the counter report profile.
• type (multiple report/single report/ printer / mail). The generated reports can be stored on file,
printed or sent by Email.
Multiple report means that a unique file will be created, containing all measures to which the
profile is correlated. Single report means that a single file will be created per each measure to
which the profile is correlated.
• destination name (e.g. the filename)
• frequency (15'/ 1 h / 1 Day / 1 Week / 1 Month / 1 Year). This attribute means that the counter
reports for the activated measures will be generated each quarter of hour / each hour / each
day...
Figure 797. Counter Report Create
b) Confirm the creation by selecting the button Create.

Now the counter report profile can be correlated to the measure. ( see paragraph 3.11.10 herebelow
)
While doing the correlation, measure granularity and Report window must be compatible, i.e.
the window must be a multiple of the granularity, according to the following table:
Measure granularity Report window
15m 15m / 1h / 1day
24h 1 day / 1 week /

1 month / 1 year
c) To verify the correlation, point at the measure and issue Display: Related items: counter Reports.
See Figure 798. and Figure 799.
Figure 798. Counter Report profile list.
Figure 799. Counter report profiles.

An example of the document that will be generated by a counter report profile is shown in Figure 800.
Figure 800. Example of generated counter report
N.B. The environmental variable PM_FORMAT can be set by the administrator to:
– PROPERTY ( format shown in Figure 800.) TBV
– CSV ( new format with improved placement of rows, columns ) TBV

3.11.9 Threshold Report Profiles Creation
INTRODUCTION
Threshold report profiles are objects which allow the automatic generation and sending of documents
(Threshold reports).
These documents contain only the values collected by the measure which exceed some user specified
threshold values.
As in the case of the counter report profiles, first you must create the threshold report profile object; then
it can be correlated to each measure you want the threshold reports to be generated for; threshold reports
will be sent only after measure activation.
SEQUENCE
To use this function you can execute the following steps:
a) From the pmDomain select Create: Threshold Report. Enter:
– userlabel, to identify the threshold report
type (/ printer / mail). The threshold report can be stored on file, printed or sent by Email.
Multiple report means that a unique file will be created, containing all measures to which the
profile is correlated. Single report means that a single file will be created per each measure to
which the profile is correlated.
– destination name (e.g. the filename)
– window (15'/ 1 h / 1 Day / 1 Week / 1 Month / 1 Year). This attribute means that the reports for the
activated measures will be generated each quarter of hour / each hour / each day...
– granularity: 15 min. or 24 hours
– The threshold values which will determine the contents of the generated documents.
N.B. The environmental variable PM_FORMAT can be set by the administrator to:
– PROPERTY ( format shown in Figure 800.)
– CSV ( new format with improved placement of rows, columns )

Figure 801. Create: Threshold Report dialog box
To execute a correlation, Measure granularity and Threshold report granularity must be the
same. The granularity value and the Report window must be compatible, i.e. the window must
be a multiple of the granularity, according to the following table:
granularity window
15m 15m / 1h / 1day
24h 1 day / 1 week / 1 month / 1 year
b) You can verify, by using the browser, that the Threshold Report Profile has been created. See Figure
802.

Figure 802. Threshold Report Profile list.
Figure 803. Threshold report icon.
Now measure and Threshold report profiles can be correlated.
3.11.10 Report Profile Correlation

SCOPE
The scope is to correlate a measure to a certain report profile.
SEQUENCE
a) From Measure list select a measure and issue Correlate/Merge:Correlate Report. A dialog box is
presented.

Figure 804. Measure correlation pop-up menu.
b) From Browser listt drag and drop the report profiles ( counter and threshold ) to the Correlation dialog
box drop area and click on button Create.
Figure 805. Correlate report
c) To verify the correlation, in the browser, from the measure issue Search: Related Items: Counter
reports/ Threshold Reports.

3.11.11 Measure Activation, Stop and Consistency
3.11.11.1 Measure Activation
INTRODUCTION
Planned measures may become activated when:
– their start time is reached ( this is automatically done )
– the user activates manually the measure. Stopped measures can be only manually reactivated.
Only when activated, the measure realizes the goal it has been created for: data collection from Network
Elements, automatic generation and sending of counters / thresholds reports (if they have been corre-
lated), generation of threshold crossing alarm ( in case TCA profiles have been correlated to pmTPs
belonging to the measure).
The conditions to activate a measure are:

– all correlated transports are allocated or implemented
– at least one tp is correlated for each monitored transport
The activity period of a measure terminates manually ( by means of a Measure: Stop command ) or auto-
matically ( when the measure end time is reached ).
SEQUENCE
a) Select from the measure list the measure and issue the Start / Consistency / Stop : Start command.
The status of the measure becomes activated (green).
After the activation of the measure, if the measure is marked as "consistent", this means that the
activation command has been successfully completed for all the correlated points. This means that
the NEs have started the monitoring action and the EMLs will provide the required data.
If the measure is displayed as "not consistent", it means that the activation command has failed
for at least one of the tps actually correlated to the measure. It is required to execute a Consistency
activity on the measure.

3.11.11.2 Measure Stop
INTRODUCTION
An activated measure may become stopped in one of the following cases:
– Manually, by means of the Measure: Stop action.
– Automatically, when the end time of the actually activated measure expires.
When Stopped, the measure will no longer collect data from the Network Elements and will not generate
reports or threshold crossing alarms.
After being stopped, the measure can be either Consistent or Not-consistent
A stopped measure can be manually reactivated.
SEQUENCE
a) Select from the browser the measure and issue the Specific: Stop command. The icon of the mea-
sure becomes light-blue.
3.11.11.3 Measure Consistency
INTRODUCTION
A Measure with Consistency attribute equal to Not consistent can be set consistent by means of the
Consistency action.
A measure is said consistent if all monitored TPs will provide the expected data to the measure.
SEQUENCE
a) Select from the browser the measure and issue the Actions: Start/Consistency/Stop: Consistency
command.

3.11.12 Threshold Crossing Alarm (TCA) Profile creation
INTRODUCTION
A Threshold Crossing Alarm Profile object allows the user to have the automatic generation of alarms for
each counter type, when the counter values run out of a range of values fixed by the user himself.
When the granularity period expires the alarm reset is performed.
SEQUENCE
a) From the browser, point with the mouse at the PM Domain and issue the command Create: TCA Pro-
file. Specify the high threshold value, the low threshold value and the severity for the counters listed
in the following. Maximum values are listed herebelow.
Performance Parameter Maximum Value Maximum Value

(15-minute period) (24-hour period)
BBE, FEBBE 539,100 51,753,600
STM-1 MS: BBE, FEBBE 2,159,100 207,273,600
STM-4 MS: BBE, FEBBE 8,639,100 829,353,600
STM-16 MS: BBE, FEBBE 34,559,100 3,317,673,600
OFS, ES, UAS, FEES, PSD, PSC 900 86,400
SES, FESES 810 78,760
PJCHigh, PJCLow 1,800,000 172,800,000
b) Select button Create to confirm.
N.B. At least one threshold value must be specified since default values are not present.

Figure 806. TCA Profile creation.

3.11.13 Threshold Crossing Alarm (TCA) Profile Correlation to the PMTP
SEQUENCE
a) In the browser point with the mouse at the PMTP to correlate.
Figure 807. PMTP: Perform.Monitoring: Correlate to TCA
b) Point with the mouse at the PMTP to correlate and issue the pop-up menu Performance Monitoring:
Correlate to TCA. The following conditions can be met:
1) The correlation is executed if in the RM exists only one TCA profile with granularity and rate
compatible with the PMTPs to correlate.
2) If in the RM exists more than one TCA profile with granularity and rate compatible with PMTPs
to correlate, a dialog box is presented. The operator has to select the specific TCA to correlate.
3) Select the TCA and press OK.
4) To verify the successful correlation, from the browser point with the mouse to the involved
PMTP and issue the Display: Main Related items: TCA Profile.
N.B. In the QB3*ADMs all TPs with same rate and granularity must have the same TCA profile, then
if you try to associate to a certain PMTP a TCA profile different from the TCA profile already
assigned to another TP, a dialog box is presented, asking the user either to force or not the TCA
profile on that NE.
The above limitation does not apply to QB3 ( INFO MODEL ) cross connect equipment.

3.11.14 Merging of several Measures
INTRODUCTION
The merging of more measures (input measures) into another one (target measure) is a complex action
which allows to put together more monitored objects (paths, trails and their termination points) into one
measure.
SEQUENCE
a) From the measure list select one of the measures to merge and click on button Merge. The Merge
dialog box is displayed. It contains in the upper area the previously selected measure, whose name
will be the name of the merged measure being created. See Figure 808.
Figure 808. Measure merging.
b) Drag to the drop area the measures to merge and select the button Merge measure. The measures
are merged into a new one. The dropped measures are deleted from MIB.

3.11.15 Displaying PM data
The detailed explanation of the displaying data function can be found in document PMDS.
The collected PM data can be presented to the user by means of the "Displaying PM data" option.
a) Select the measure from the browser and select the functional button Show Performance Monitoring
Data.
3.11.16 The pmNE

A pmNE object is automatically created the first time the user executes the correlation of a TP belonging
to a certain NE.
Starting from the PM domain, you can navigate, by means of the Display: Related Items command, to the
Monitored NEs. See figure below.
Figure 809. pmNE Show/Set attributes
The Show/Set attributes from this object contains the following attributes:
– userlabel
– NE type
– last collected file15m / last collected file 24h. These attributes are used to keep a history of the file
that has been collected from RM and to ask EML for sending the not yet received files.
– working status. This attribute is usually set to normal. It changes to Synchronizing when the attribute
On going activity is in one of the following states:

• Collect in progress ( receiving PM data from EML )
• Analyze in progress ( storing PM data in the RM-MIB )
• Consistency in progress ( a consistency activity is being executed )
– PM misalignment ( true/false ). This attribute is applicable to SEN-IM Network Elements, as specified

by the attribute IM type.
In addition, from browser it is possible to display the PM tp view and the PM transport view. See figure
which follows.

Figure 810. PM tp view

3.11.16.1 Archive Performance Monitoring data
INTRODUCTION
To Archive Monitoring data means to memorize PM data on a storing support ( tape / file )
Data archived are those relevant to:
– measures
– PM transport
– pmTPs
– historical data
The result of the Archive procedure is to obtain a series of mag-tapes, each one storing data relevant to
a certain period.
The Archive procedure avoids memory disk saturation, with the objective of maintain hystorical data and
transfer them to tape.
Archive procedure could be executed automatically and manually.
Only archived data can be deleted from disk.
It is strongly recommended to execute Archive and Delete procedures of the PM hystorical data with the
following time periods:
– one month for the 24 hours data
– one week for the 15 minutes data
It is strongly recommended to execute Archive and Delete procedures of the PM hystorical

data upon reception of diagnostic messages alerting: “ Disk Full ..."
3.11.16.2 Archive Performance Monitoring data
SEQUENCE
a) From TMN-OS view select the RM icon and issue the Actions: SMF: PMDS DB Administration item.
b) See detailed description in document PMDS User Guide.
3.11.16.3 Retrieve Performance Monitoring data
INTRODUCTION
To Retrieve Monitoring data means to memorize on RM_MIB data stored on archived tape.
SEQUENCE
a) From TMN-OS view select the RM icon and issue the Actions: Performance Monitoring menu item.

3.11.16.4 Display Performance Monitoring data
INTRODUCTION
To display Performance Monitoring data means to display data that have been previously retrieved.
SEQUENCE
3.11.16.5 Delete Monitored data
INTRODUCTION
To Delete Monitored data means to delete from RM-MIB all archived data. Only historical data are deleted.
SEQUENCE
3.11.17 Archive Session

INTRODUCTION
The Archive session allows to display previously completed archive to tape operations and programmed
archive operations.
SEQUENCE
Starting from the PM domain, you can navigate, by means of the Display: Related Items command, to the
Archive Session. The list of the Archive sessions is presented. For each item of the list the Show/Set
attributes dialog box contains the following attributes:
• user label, automatically built on from date and the granularity (e.g.: an archive performed on
15 min data from the 15/06/1998 will be given the following user label: “15 minutes counters
1998/06/15")
• tip dates (from date and to date)of the data period
• granularity of the archived data
• the date the archive operation has been performed
• the date the archived data have eventually been removed
An instance of archive session, concerning the next archive session, is automatically generated at the
end of each archive operation.
3.11.17.1 Attribute Setting
The only attribute which can be set by the user is the attribute to date, in order to anticipate or postpone
the next archive operation.

3.11.18 Uncorrelate the transport from planned measures
INTRODUCTION
This is the action opposite to the "Correlate Transport to planned Measures"; by uncorrelating a transport
from a planned Measure the user indicates that the termination points belonging to that transport will not
have to be monitored by the Measure.
SEQUENCE
a) From the browser point at the transport icon and issue the Performance Monitoring: Remove from
command.
b) Two cases are possible:
1) More than one measure is correlated. The system provides the list of the planned measures
which are monitoring the involved transport object.The user selects the measure to uncorre-
late and clicks on the confirmation button.
2) Only one measure is correlated. The uncorrelate action is automatically executed.
3.11.19 Uncorrelate the tp from planned measures

INTRODUCTION
This is the action opposite to the "Correlate tp to planned Measures"; by uncorrelating a tp from a planned
Measure, the user indicates that data concerning that tp are no more interesting for him: they will not be
collected when the measure will enter the activated state.
SEQUENCE
a) From the browser point at the tp icon and issue the Performance Monitoring: Uncorrelate from Mea-
sure pop-up menu.
b) Two cases are possible:
1) More than one measure is correlated. The system provides the list of the planned measures
which are monitoring the involved tp object.The user selects the measure to uncorrelate and
clicks on the confirmation button.
2) Only one measure is correlated. The uncorrelate action is automatically executed.

3.11.20 Remove from RM menu
INTRODUCTION
The Remove from RM menu item allows to remove the following objects:
– pm TP
– PM transport
– Measure
The object containment tree is shown in Figure 811., i.e. if you remove an object, all the contained objects
are automatically removed.
N.B. The Remove from RM action applies only to stopped or planned measures.
MEASURE
REPORT
COUNTER/
THRESHOLD
PM TRANSPORT
PMTP
HISTORICAL
DATA
Figure 811. Object containment tree

3.11.21 Uncorrelate the counter/threshold report profile from the measure
INTRODUCTION
This is the action opposite to the "Correlate Counter/threshold report to planned Measures", by uncorre-
lating a Counter/threshold report profile from a planned Measure.
SEQUENCE
a) From the browser, point at the measure icon and issue the Performance Monitoring: Uncorrelate
from Measure command. The list of the associated reports is presented.
b) Select the report to uncorrelate and click on OK.

3.12 Test Ports
The feature is applicable to paths without virtual concatenation, on an SDH transport network.
Only Q3 nodes can be used for monitor cross connections.
The paths can be bidirectional, unidirectional point-to-point or broadcast.
In case of bidirectional path, both directions can be dropped to the same test port or two different
test ports.
The test port can be PDH (at the same rate of the path) or SDH. In the latter case, signals coming from
different paths can be multiplied on the same SDH test port.
To use a SDH port as a test port, create a physical connection between that port and an external network,
then implement it.
In order to monitor LO paths, configure manually the LO payload of this physical connection. An SDH
port marked as test port cannot be used as a normal SDH port: no path can be allocated; this port can
be used only for test.
3.12.1 SDH Test Port setup: Forward connection addition (A to B)

With ref. to below figure, a 140Mb path is connecting node A to node B, thru node XC (1678DXC).
Create a physical connection between an SDH port of node XC, to be used as test port and the external
node T.
This test connection will monitor the TX from A to B through an unidirectional test cross connection from
XC to T.
SEQUENCE
a) From the map select nodes XC and T and issue Create: Physical Connection
XC
A T
Figure 812. Create: Physcon
b) In the Create: Physcon box select: SDH,rate, and enter the physcon name (TESTPHYSCON in this
case). Click on Next.

Figure 813. Create: Physcon: SDH,rate,name
c) Select attribute used for Test and set it to True.
Figure 814. Create: Physcon: used for Test
d) Enter the virtual port label

Figure 815. Create: Physcon: virt port label
e) With ref. to above figure, on the real node dialog area (upper-right hand), click on port selection but-
ton. The port selection list is presented. Select the SDH port and click on Apply.(see fig. herebelow)
Figure 816. Create: Physcon: port selection
f) In the main Create Physcon box, click on Finish to confirm. The Create: Physcon: Action report is
shown in figure which follows.

Figure 817. Create: Physcon: Action report
g) You can see that the port involved in the TESTPHYSCON is marked by attribute used for test=true.
See below figure.
Figure 818. Port Show attr: used for test
h) Point to the TESTPHYSCON and issue Physcon: Configuration: Implement
Figure 819. Physcon: Configuration: Implement
i) The Physcon structure is then automatically shown. See below figure

Figure 820. Physcon structure
j) The addition of the test port must be executed on the (being tested) path routing display. To get the
routing display, first get the crossed A to XC physcon.
Figure 821. Detail of the physcon link
k) Select the involved physcon and click on button Supported Paths
Figure 822. Selection of paths crossing the physcon
l) From the path list of the Supported Paths, select the relevant path and click on routing display button.
m) From the routing display select the 1st CTP and issue Test Port: Addition Tool. See below figure

Figure 823. 1st CTP: Test Port: Addition Tool
n) The Test Port: Addition Tool box opens. Click on Next.
Figure 824. Test Port Addition Tool
o) Select the port. The selection mechanism consists in clicking on the selection button, then selecting
the port from the list. The selection of the time slot (payload position) is also required (in case of an
SDH test port). Click on button payload position.

Figure 825. Test Port Addition Tool: port selection
p) Select the time slot and click on Apply.
Figure 826. Test Port Addition Tool: payload position selection
q) In the main box, click on Finish to confirm. The port is marked as Test Port and in the routing display
a dedicated icon is present on the involved CTP. See figure below.

Figure 827. Test Port present
r) If you click on this icon, you can get the Cross connection details box.
Figure 828. Cross connection details
s) Notice that automatically a test path is allocated. See Physcon structure in figure herebelow.

Figure 829. Physcon structure: test path present
3.12.2 SDH Test Port setup: backward connection addition (B to A)

a) On the 2nd CTP issue Test Port: Addition Tool, in order to monitor the TX from B to A through an
unidirectional test cross connection from XC to T.
XC
Figure 830. 2nd CTP: Test Port: Addition Tool
b) The Test Port: Addition Tool box opens. Click on Next
Figure 831. Test Port Addition Tool (CTP already selected)

c) Select the port. The selection mechanism consists in clicking on the selection button, then selecting
the port from the list. The selection of the time slot (payload position) is also required. Click on button
payload position.
Figure 832. Test Port Addition Tool: left scroll payload position
d) In this case the 2nd CTP must be cross connected the same test port, then a time slot different from
the first must be selected. Do a right scroll of the CTP list and select the time slot. Click on Apply
button.
Figure 833. Test Port Addition Tool: right scroll payload position
e) In the main Test Port Addition Tool click on Finish

Figure 834. Test Port Addition Tool: Finish
f) Both Forward and Backward Test ports are present
Figure 835. Forward and Backward Test Ports present
g) The Forward and Backward Test Ports creation report is shown below.
Figure 836. Forward and Backward Test Ports creation report
h) On the other hand both test paths are displayed in the physcon view. See below figure.

Figure 837. Forward and Backward Test paths
3.12.3 Test Port Remove

a) Point to the relevant CTP and issue Test Port: Remove
Figure 838. Test Port: Remove
b) The Remove test port log is shown below.

Figure 839. Remove test port log
c) The relevant 1st Test port icon on CTP is no more present.
Figure 840. 1st Test port icon on CTP removed
3.12.4 Multiple test port remove

Multiple test port remove is allowed. In the following example, both CTPs have been selected and the
command test port remove has been selected.

Figure 841. Multiple test port remove
3.12.5 Multiple Test port Addition

Multiple test port creation is allowed.
a) In the following example, both CTPs have been selected and the command test port addition tool
has been selected.
Figure 842. Multiple test port addition
b) The relevant dialog box is shown below. Click on Next

Figure 843. Test Port addition tool (multiple)
c) The 1st CTP is presented.
Figure 844. 1st CTP connection
d) Execute the connection, selecting the port and the time slot. Click on Next.

Figure 845. 1st CTP connection: setup
e) The 2nd CTP is presented. Execute the connection, selecting the port and the time slot. Click on Fin-
ish button to confirm the creation.
Figure 846. 2nd CTP connection: setup
3.12.6 PDH Test Ports

PDH test ports can be managed too.
a) The path given as example is shown in figure below.

Figure 847. Path 2 Mb with test ports
b) Point to the CTP to connect to the test port and issue Test Port: Test Port Addition Tool
Figure 848. Test Port: Test Port Addition Tool
c) The Test Port Addition Tool is displayed. Click on Next button.

Figure 849. Test Port Addition Tool
d) The dialog box asks to select the test termination. Select the NAP to be used as test termination.
Figure 850. Test termination selection (NAP)
e) Click on Finish to complete the selection.

Figure 851. Test termination selected
f) The connection to the test port is added. The involved CTP is marked by an arrow symbol.
Figure 852. Added connection to the test port
g) You can check the creation of the test cross connection from the Equipment view issuing

Figure 853. Configuration: Cross Connection.
h) The new connection is present in the list
Figure 854. Cross Connection list

3.13 LOGGER
The event logger displays the current events and the list of the events which have been stored in the log
file.
This box allows the user to select the following parameters:
– Class Type. The operator can choose to display events relative to:
• all classes (wildcard)

• path
• emlDomain
• ne
• port
• physicalConn
• ntw
• sbn
• et
• node
• lc
• trail
• connInTopol
• nap
– Event Type. The operator can select among the following types:
• all types (wildcard)

• attributeValueChange
• stateChange
• objectCreation
• objectDeletion
– Log Type. Two options are available:
• Immediate. The report window will work as a virtual printer ( FIFO ), displaying messages in real
time.
• From Log File. The Report will contain data extracted from the historical event log file of HP-OV.
– Start Time/End Time, to be specified for searching from Log File.
– Object_Instance. From "Browser" drag the object(s) whose event log is required and drop into this
area. A wrongly dropped object should be deleted by means of the "Delete" pop-up option. The pres-
ence of objects in this area automatically makes not meaningfull the content of the above described
Class-Type box.
The window contains four toolbuttons;
– Cancel, to cancel the operation and close the window.
– Apply, to start the event log process.
– Cancel Get, to abort the data retrieval.
– User's info

EVENT LOG
The Event Log dialog box contains the pull-down menu line with items File and Actions.
– Item File contains the following options:
• Open, to start a read operation on an ASCII file. This file is selected by the user by means of
a file filter.
• Save as... to save on file the content of the Event Log.
• Print all to print the Event Log content on the default printer.
• Print Selected to print part of the Event Log content on the default printer.
– Item Actions contains the only option Font.
still closed.

4 Technical Annexes
4.1 Introduction
• Introduction to Functionalities
• Routing Algorithm
• Allocation
• NE Constraints
• RM Objects
• Object names

Technical Annexes 3AL 61269 AAAA Issue 4 803/854
4.2 Functionalities
The 1354RM is a network management system that has been designed to handle SDH regional networks.
The aim of this chapter is to give an overview of the 1354RM. (See Figure 855.). The 1354RM covers the
1st NML level ( Network Management Layer). Figure 855. shows all the functional layers and the com-
munication protocols.
VPN NML
Client A
1354NN
http RMI
M
Web VPN ISN
Qnn
Server Server
NML
A
M 1354RM
QB3* QB
EML
A
QB3*
QB
NE M: MANAGER
A A: AGENT
Figure 855. The 1354RM in the SDH management hierarchy
4.2.1 Supported EMLs

The EML supported are:
– 1353NM
– 1353WX
4.2.2 Supported NEs

Please refer to the current External Release Notes

804/854 3AL 61269 AAAA Issue 4 Technical Annexes
4.3 ROUTING Algorithm
4.3.1 Routing Algorithm General

The routing algorithm acts during the allocation of path or trail, i.e. performs the operation that allocates
resources (link connections and CTPs) to the given path/trail and defines the cross connections (named
connections in topology)
Paths can be bi-directional point-to-point, unidirectional point-to-point and unidirectional broadcast. HO

trails are always bi-directional point-to-point.
Paths and trails can be:
– not protected: a single route (main) is defined between the end points
– protected SNCP: two routes (main and spare) are defined between the end points, in order to protect
the path against link faults and node faults;
– protected D&C SNCP: in addition to main and spare, one or more service route are inserted in the
path, in order to protect it against multiple faults; (available only for point_to_point paths and trails)
– protected in rings: the protection (spare) is added only inside rings
The basic algorithm has the objective of finding the minimum cost route between the end points (NAPs,
CAPs ).
The basic algorithm used is a particular customization of the Dijkstra Algorithm.
4.3.2 Point to point paths
4.3.2.1 Unprotected path
This is the simplest case. The algorithm computes a single lowest cost route from the source point to the
sink one, called main route.
4.3.2.2 SNCP Protection
A path is called protected when supplementary arcs or connections, called spare, are allocated in addition
to the main one to provide an alternative way in case there are one or more failures along the main route.
A SNCP protected path has two routes, main and spare, from source to sink vertex, sharing as less as
possible common resources. The algorithm therefore tries to minimize the overlaps between main and
spare . As a result, an end-to-end protection is obtained whenever possible.
The algorithm used is slightly different whether the path allocation is completely automatic or not.
SEMI-AUTOMATIC VERSION
It occurs when at least one path constraint has been entered by the user
The algorithm proceeds in the following way.
1.First, the lowest-cost main route is computed.
2.Then the spare route is computed with as less as possible overlaps with the main route.

Notes
In this case the algorithm would find the path with the lowest cost main route, not the lowest sum of main
and spare route costs,costs. This is acceptable for a semi-automatic path allocation, since the user has
forced the routing to be not necessarily the best one.
FULLY AUTOMATIC VERSION
The Dijkstra Algorithm has been customized in order to minimize the sum of main and spare route costs,
with the minimum number of overlapped resources.
Figure 856. Protected path routes ( automatic algorithm )
4.3.2.3 D & C Protection
For a D&C protected path the algorithm computes a SNCP protected path with additional routes, called
services, obtained connecting, for each ring and for each direction of the path, the ring exit nodes of the
main and spare route through D&C connections in order to protect the traffic in that direction against mul-
tiple failures.
Notes:
If the path is unidirectional each ring can have at most one service, if it is bi-directional two.
The service can exist if, in the direction to protect, the main and the spare route exit from different nodes.
The algorithm proceeds in the following way:
1. First, the lowest-cost main route is computed.
2. Then the spare route is computed with as less as possible overlaps with the main route (see 4.2.2).
3. Finally, it computes the service routes, with the following rules:
– Allocation/Add Service (without end points). Services are allocated in rings crossed by both main
and spare routes protecting the existing traffic.
– Add Service between specific end points. The user can specify the connections involved in the
service ( without topological restrictions) choosing the direction to protect
4.3.3 Protection in Rings

A path protected in ring has a protection just for the SNCP rings it crosses .

4.3.4 Broadcast path
If the path is not protected, Dijkstra is applied once for each leg.
If the path is protected and at least one constraint has been setup, the semi-automatic algorithm is applied
once per each leg.
If the path is protected, without constraints the fully automatic algorithm is applied once for each leg.
In general, different legs can share some arcs. It is also possible to use an arc in the main route of one
leg and in the spare route of another leg.
Legs are not routed independently: the base cost of arcs already used in a previous leg are decreased
by a configurable factor: in order to share as many as possible arcs between legs, by default the cost is
reduced to 20% of the original value if the arc is used with the same resource type, to 40% of the original
value if used with different resource type,
"Inter legs" checks are executed in order to avoid that 2 connections of different legs in the same node
result either in a connection not supported by the NE, or in a switch, whose main and spare TPs belong
to different legs.
4.3.5 Routing inside rings

Basic algorithm
1354RM manages the possibility to insert a node in more than one ring, as shown in the following two pic-
tures.
Figure 857. Collapsed dual node interconnection between two rings

Figure 858. Stacked rings
In these cases, the routing algorithm is not based on minimum cost criteria, but it tries to avoid ring cross-
ing.
4.3.5.1 NPA routing attributes
Two attributes are defined in NPA object:
– NPA Usage Cost: it is an extra cost used in the routing algorithm for the usage of the NPA. It ranges
from 0 to 100, like the cost of physical connection;
– NPA Reduction Cost Factor: the cost of physical connections inside a NPA is reduced by this factor
in the routing algorithm.
If equals 0, it has no effect. If equals 100, the cost becomes 0.
This reduction is introduced in order to compensate the cost for the usage of the ring.
By default, the NPA usage cost is 20 (like the default cost of a physical connection); the default NPA
Reduction Cost Factor is 20%. The user is allowed to modify these values. In particular, putting both val-
ues to 0 results in a minimum cost routing.
Example: in Figure 859. - below, using default values a path between N2 and N5 is routed through N3
and N4 using only ring 2 (continuous line), even if the minimum cost route, taking into account only the
physical connection costs, bypasses N3 but uses both ring 1 and ring 2 (dashed line).

Figure 859. NPA routing attributes effects in stacked rings
In the fact, the cost of the chosen route (N2 - N3 - N4 - N5) for RM routing algorithm is 68: 3*16 (cost of
three links) + 20 (access to ring 2); while the cost of the other route (N2 - N4 - N5) for RM routing algorithm
is 72: 2*16 (cost of two links) + 40 (access to ring 1 and ring 2).
Two attributes are defined in path and trail objects, relevant to the spare route:
NPA Main & Spare Factor: it is meaningful for SNCP or D&C SNCP paths/trails. During spare calculation,
the NPA Usage Cost, for rings already used by the main route, is reduced by this factor.
If equal to 0, it has no effect, i.e. NPA Usage Cost is not reduced by the routing algorithm.
If equal to 100, NPA Usage Cost becomes 0 in the routing algorithm.
By default, NPA Main & Spare Factor is 100%.
MS-SPring D&C Factor: it is meaningful for SNCP or D&C SNCP paths/trails crossing MS-SPring. It can
be used to encourage, during spare calculation, the usage of D&C inside MS-SPrings.
If equals 0, it has no effect.
By default, the MS-SPring D&C Factor is 80%.
As bigger is set the NPA Main & Spare Factor, as more main and spare are attracted to use the same rings,
resulting in a more ordered routing. This can be particularly useful for D&C paths/trails that use SNCP
rings.
Examples:
in Figure 860. - below (case A), using default values, the main route of a path between N2 and N6 is routed
through N4 using only ring 1. The spare is routed through N1, N8 and N7 still using only SNCP ring 1 (con-
tinuous line), while the routing obtained disabling NPA Main & Spare Factor bypasses N8 but uses SNCP
ring 2 (dashed line), that wasn't used in the main route. In fact, the cost of the chosen spare route (N2 -
N1 - N8 - N7 - N6) for RM routing algorithm is 64: 4*16 (cost of four links), without any additional NPA usage
cost; while the cost of the other route (N2 - N1 - N7 - N6) for RM routing algorithm is 68: 3*16 (cost of three
links) + 20 (access to ring 2).
not in all cases, the NPA Main & Spare Factor avoids the usage of new rings not used in the main route.

In Figure 860. - below (case B), using default values, the main route of a path between N2 and N3 is routed
using only ring 2. The spare is routed through N4 (continuous line) using both SNCP ring 1 and ring 2,
that is the same route obtained disabling NPA Main & Spare Factor.
In fact, the cost of the chosen spare route (N2 - N4 - N3) for RM routing algorithm is 52: 2*16 (cost of two
links), + 20 (access to ring 1); while the cost of the route that uses only ring 2 (dashed line) is 96: 6*16
(cost of six links), without any additional NPA usage cost.
Figure 860. NPA Main & Spare Factor effects in stacked SNCP rings
As bigger is the MS-SPring D&C Factor, as more the routing algorithm should automatically route main
and spare in order to create D&C-IC connections compared to other possible routes. When the cost of
the route with D&C-IC is too high, other solutions are preferred.
Examples:
In Figure 861. a MS-Spring is crossed by a protected path in such a way that there are a lot of NEs between
primary and secondary nodes. In this case, using default MS-SPring D&C Factor, the spare route of the
path is the one represented by the red continuous line. Increasing the value of the MS-SPring D&C Factor,
the dashed route can be preferred, resulting in two D&C connections in nodes N1 and N2.

Figure 861. Routing in stacked MS-Springs - primary and secondary nodes not adjacent
In Figure 862. primary and secondary nodes in the MS-Spring are adjacent. In this case, using the default
value of MS-SPring D&C Factor, the spare route of the path is the red continuous line with D&C-IC con-
nection in nodes N1 and N2. Reducing the value of the MS-SPring D&C Factor, the dashed route can be
preferred.
Figure 862. Routing in stacked MS-Springs - primary and secondary nodes adjacent
4.3.6 Service route in D&C paths

For service routes it is possible to distinguish three different situations:
Allocation of D&C protected paths: service routes are calculated in the rings (SNCP and 2F MS-SPrings
for LO paths) crossed by both main and spare. The NPA usage cost is not taken into account for rings
crossed by both main and spare; all the other rings cannot be used in the service route.

Add service to a previous SNCP protected path: the algorithm follows the same principles used for allo-
cation.
Add service between specific TPs of a path: service routes may connect the main with the spare branch
without topological restrictions. In this new scenario it is possible, for service routes, to traverse rings used
by both main and spare, only by the main, only by the spare or previously unused rings. As consequence,
the NPA usage cost taken into account by the routing algorithm is:
Equal to 0 for rings used by both main and spare
Half the value of the NPA usage cost for rings used only by the main/spare
Not modified for rings not yet used by main and spare
These rules advantage the use of rings already used by main and spare respect to others, but doesn't
prevent the usage of any ring.
4.3.6.1 Inter-working scenarios
4.3.6.1.1 SNCP ring inter-working
For collapsed dual node D&C inter-working, it is not necessary to define a specific meshed ET including
N3 and N4.
Figure 863. Collapsed dual node D&C for SNCP ring

Figure 864. Collapsed single node D&C for SNCP ring
A path can cross a node that is part of more than two rings; see N4 in the example shown in figure below.
As usual, the service routes are added only in the rings used by both main and spare of the path (N3-N4
for ring 1, N4-N5 for ring 3).
As a result, two classic D&C connections are created in N3 and N5; one dual node D&C is created in N4.
Figure 865. Collapsed dual node D&C for SNCP ring

4.3.6.1.2 Collapsed dual node D&C inter-working for 2f MS-Spring
Depending on the placement of the two end nodes, the two following routes can be obtained.
Figure 866. Collapsed dual node D&C inter-working for 2f MS-Spring - config 1
Figure 867. Collapsed dual node D&C inter-working for 2f MS-Spring - config 2
In case of stacked MS-SPrings, paths ending in different rings can be routed differently, depending on the
number of nodes between the end nodes. Note that SNCP connections, if supported by NEs, can be cre-
ated by the routing algorithm also inside MS-Springs (Figure - below case A).

Figure 868. Paths in stacked MS-SPrings

4.4 ALLOCATION
4.4.1 Allocation and Defragmentation

The allocation makes use of the defragmentation algorithm, with the following exceptions:
• inside a MS-SP Ring (both two and four fibers), the time slot interchange is not possible at HO:
the algorithm chooses the first free time slot in all the routing links of the ring used by the HO
path;
• in case of NE constraint (the protected connections in all QB3* ADMs must have the same time
slot at west and east aggregate ports), the algorithm chooses the first free time slot in both rout-
ing links adjacent to that NE.
DEFINITION
A physical connection or a trail is said fragmented if the busy time slots are not rationally organized and
impede the optimized allocation of higher order paths.
To avoid the fragmentation, the defragmentation mechanism is used. It applies to the nominal route.
The trail basic cost (see def. herebelow) is dinamically incremented to take into account the high rate
bandwidth that could be missing if that ts is used.
In practice the defragmentation is a structured (traffic) lower filling threshold which helps
resource(trail,physcon) filling up to the threshold.
On the other hand, the saturation is a structured (traffic) upper filling threshold which limits
resource(trail,physcon) filling up to the threshold.
Cases:
– empty physical connection or trail. In any case badwidth space fo higher rates is missing, i.e. setting
an AU4, the possibily of setting an AU4-4C/ an AU4-16C/ an AU4-64C would be lost.
– partially busy physical connection or trail. According to the actual traffic distribution, setting a new
path may affect the possibily of setting an higher rate path.
Trail extra cost
A trail extra cost is added. (MS trail or HO trail if a LO path is set. The extra cost is directly proportional
to the being missing bandwidth.
During the evaluation of the fragmentation cost, the routing algorithm does not consider the current pay-
load implemented on the NE but only the position of the busy bandwidth for allocated or implemented
paths/trail. The payload will be changed on the NE at path/trail implementation time. The change is done
directly by RM in legacy networks and by GMREs in the ASON. This is true only when the dynamic payload
is enabled.
Fragmentation cost
We define:
Basic cost=cost of the physical connection for HO trail

Basic cost=cost of the physical connection for LO path using an one-hop HO trail
Basic cost= [ max(Ci) + Σ Ci ] / 2 for LO path using n-hop HO trail
For lower order paths, the same concepts can be applied to tu3 and tu12 rates: in the allocation of a tu12
path, an extra cost can be added where the usage of a tu12 path reduces the available bandwidth of tu3
paths.
Environment Variables
The following Environment Variables are defined: (default 5%)
• AU4_EXTRACOSTFACTOR: 5%
• AU4C_EXTRACOSTFACTOR: 5%
• TU3_EXTRACOSTFACTOR: 5%
These variables are the percentage of the basic cost that gives contribution to the extra cost
In the following, some examples are reported. The following basic hypothesis are used:
-the basic cost is 20 (default value):
Cbasic = 20
the extra cost to pay to fragment an AU4-64C, an AU4-16C, an AU4-4C, an AU4 with an AU3 is, respec-
tively:
C1 = 5%
C4 = 5%
C16 = 5%
C64 = 5%
The following table shows an example with the total cost in different configurations of STM16link. Each
line is a different configuration of STM16. A busy time slot is in red (filled with 1 if used in a AU4 path, with
4 if used in a AU4-4c one), while other colours are used only to show different groups of time slots. The
cost to allocate paths with different rates is in the last 3 columns of each line.
N.B. In the example the AU3 is not supported and so it is not taken into account

The above table can be read taking into account the following:
case 1 (empty STM16):
– AU4-16C allocation => Cbasic = 20, because there is not any lost concatenation rate
– AU4-4C allocation => Cbasic + C16 = 21, because lost concatenation rate is AU4-16C
– AU4 allocation => Cbasic + C4 + C16 = 22, because lost concatenation rates are AU4-4C and AU4-
16C
case 2, 4 and 6:
– AU4-4C or AU4 allocation => Cbasic = 20, because there is not any lost concatenation rate
(case 3 and 5):
– AU4-4C allocation => Cbasic = 20, because there is not any lost concatenation rate
– AU4 allocation => Cbasic + C4 = 21, because lost concatenation rate is AU4-4C
TIME SLOT SELECTION
Once the route has been found for all the parts of a path/trail, the selection of Link Connections / time slots
has to be done.
The used criteria according to priority are:
– Constraints to be always satisfied, otherwise the allocation fails:
• NE constraints (mainly in old generation NE's like QB3*)
• Protection constraints (e.g. 2f-MS-SPRing without time-slot interchange)
• User defined constraints
– Minimization of fragmentation.

– This means to avoid the usage, if possible, of part of the bandwidth available for higher rate or, if not
possible, to impact the lower one. This means to reuse the same criteria used to calculate the frag-
mentation cost
– First free time slot. An exception to this rule is the protecting fibers inside 4F MS-Springs, where the
allocation of time slots starts from the last free one
4.4.2 De-saturation in routing

The de-saturation is a criteria used in routing algorithm, in order to choose the most suitable link. A link
is saturated if the used band exceeds a defined threshold.
The feature is an improvement of the path/trails allocation process, taking into account the prevention of
saturation.
The described improvement is related only to the allocation of the nominal routing.
The goal is to avoid that physical connections become saturated with path/trails.
This will minimize the effects of a single fault (in particular in case of restoration networks): part of the
resources not used by nominal paths are still available to support backup routes and restoration.
In order to prevent saturation, the basic physical connection cost is incremented of an additional cost when
the usage becomes higher than a parametric value.
Three saturation extra cost bands are defined:
– Low usage extra cost
– Medium usage extra cost
– High usage extra cost
The saturation cost is applied when the used bandwidth plus the bandwidth to be added is greater than
the saturation threshold. This means, for example, that an empty STM16 becomes automatically satu-
rated when used by an AU4-16C.
4.4.2.1 SaturationProfile
The saturationProfile contains the thresholds defining the three saturation extra cost bands and the
related extra cost. It includes:
profileId
userLabel
comment1
profileType: it indicates if the profile is defined by the user or not. Allowed values:
user: the profile is defined by the user (default value)
system: the profile is automatically defined by the system. It cannot be defined, modified and delet-
edby the user
mediumThreshold: (percentage of the whole band); it is the Medium usage extra cost band
highThreshold:(percentage of the whole band); it is the High usage extra cost band

lowUsageExtraCost: it indicates the extra cost, expressed in percentage of the basic cost, to use
resources belonging to the Low usage extra cost band
mediumUsageExtraCost: it indicates the extra cost, expressed in percentage of the basic cost, to use
resources belonging to the Medium usage extra cost band
highUsageExtraCost: it indicates the extra cost, expressed in percentage of the basic cost, to use
resources belonging to the High usage extra cost band
Cost of
physical
connection
High usage
Medium Extracost
Low usage usage
Extracost
Extracost
Basic cost
Used
band-
Total widht
Bandwidht
Figure 869. Extracosts
4.4.3 Saturation profile management

Two saturation profiles are automatically defined by the system. They cannot be modified or deleted by
the user. See following table
userLabel noExtraCost predefinedExtraCost
mediumThreshold 75% 75%
highThreshold 88% 88%
lowUsageExtraCost 0% 0%
mediumUsageExtraCost 0% 75%
highUsageExtraCost 0% 175%

The noExtraCost saturation profile will be used for no saturation policy in path allocation. The noExtraCost
saturation profile is the default.
The predefinedExtraCost saturation profile has been defined in order to satisfy the following configura-
tions (in bold the chosen route):
1. cost of 1 Medium usage link < cost of 2 Low usage links (35 < 40)
L L
2. cost of 2 Medium usage links > cost of 3 Low usage links (70 >60)
L L
L
M M
3. cost of 1 High usage link < cost of 2 Medium usage links (55 < 70)
M M
4. cost of 2 High usage links > cost of 3 Medium usage links (110 >105)
M M
H H

5. cost of 1 High usage link > cost of 2 Low usage links (55 >40)
L L
6. cost of 2 High usage links > cost of 3 Medium usage links (55 <60)
L L
The user cannot create/modify the saturation profile.
Saturation cost evaluation
According to the saturation profile associated to the physical connection, the total cost is calculated
according to the following formula:
Ctotal=Cbasic + Csaturation
If the fragmentation cost has to be taken into account, the total cost is calculated according to the follow-
ingformula:
Ctotal=Cbasic + Csaturation + Summation Cfragmentation

If both saturation and fragmentation costs are taken into account, they are separately calculated, respect
to the basic cost, and then added to the basic cost.
4.4.4 ASON GBE restoration type, priority, reversion type management on path
level
This feature allows, for a GBE path in an ASON domain, the propagation of the values at path level to the
trails and to the SPCs.
Functional view
The change of the value of the restoration type, priority and reversion type on a path GBE is propagated
to all the server trails and, if required by the user, from the trails to each supporting SPC.
Viceversa, when the value is modified on a server SPC or on a server trail, no propagation is done to the
path. This because the value on the path and on the trail is a "preferred value" and it is not the synthesis
of the values on the server objects.

4.4.5 AU3 SPC's
The feature deals with the set-up of an AU3 SPC inside the ASON as a consequence of the set-up of an
AU3 path crossing an ASON NPA.
The AU3 SPC is managed as well as the AU4 SPC, from the point of view of routing, implementation,
alarms and GUI.
The feature requires:
– handling of the AU3 SPC rate
– handling of the new payload when interacting with GMRE through MTNM (e.g. in Active backup
route, Traffic Status on physical connections, Highlight)
4.4.6 LO Matrix TTP's as SPC end points

This feature allows managing the payload-able trails as Soft Permanent Connections protected by
GMRE's. The SPC end points on LO matrix are explicitly requested by RM to GMRE (that retrieves them
from the pool via Q3) and then provided in the create SPC. The user is not allowed to payload physical
connections inside the ASON: only the set-up trail is available. The trail can be partially terminated in the
ASON domain.
The feature allows the management of trails with one of both the terminations inside the ASON domain.
These trails can only be created by means of the "Create new HO trail" command, while it is not possible
to create them by means of the payload of a physical connection inside the ASON domain.
These trails can be payloaded.
4.4.7 GBE@AU3 in ASON

The feature deals with the set-up of AU3 SPC' s inside the ASON as a consequence of the set-up of a
GBE path AU3-nV concatenated and having AU3 server trails crossing an ASON NPA
The AU3 SPC related to the AU3 server trails will be managed as well as the AU4 SPC' s related to the
AU4 server trails of GBE paths AU4-nV concatenated, from the point of view of the routing, implemen-
tation, alarms
The feature requires:
– The interface with GMRE (through MTNM) for the assignment of the TTP ending the SPC with the
related TTP rate and label
– The handling of the AU3 Trails (the AU3 SPC management is already required for the "AU3 SPC' s")
For the detailed description of a GBE path AU3-nV concatenated, please refer to the "Management of
GBE@AU3 in SDH networks" feature (DATA part of RM specifications).
4.4.8 SC support in AU3 based networks (AU3, AU4, AU4-nC)

The feature allows the support of SC in the networks where the default payload is AU3.
In AU3 based networks (default payload is AU3), the SC is managed as before but in case of AU4, AU4-
nC rates, the system has to re-map the AU4, AU4-nC payloads in the correct AU3 payload positions of
the UNI physical connection
De-implementation of SPC's with unreachable GMRE's

– Enhabling of de-implementation with unreachable head GMRE with annotation on RM
– Management of the SPC removed only in RM during modification of drop links (manual payload,
remove of drop physical connection)
– Visualization of an appropriate error message on the implementation of a SPC using a tail TP of an
SPC only removed in RM
4.4.9 Management of GMRE setUpPriority

The priority allows a resource to pre-empt an another one. existing. The pre-emption operation is done
in path/trail implementation or rerouting phase.
The criteria to establish if a resource already existing can or cannot be pre-empted by another one to be
implemented/rerouted is showed in the following table, where:
– priority_1 is the priority of the SNC1, i.e. the SNC already working
– setUpPriority_2 is the set-up priority of the SNC2, i.e. the SNC to be implemented or rerouted that
should preempt the SNC already working;
N.B. The priority scale is inverse: maximum priority is "1" and minimum is "5". In other words the
matching "setUpPriority_2 < priority_1" means that priority of SNC2 is major of the SNC1 one.
N.B. As already wrote the pre-emption cannot be done if the existing resource (SNC1) works on the
nominal route. In fact in this case RM automatically doesn't allows a new nominal SNC to over-
lap an existing SNC working on its nominal route.
This new introduced priority concept may be used also to avoid that an existing resource is pre-empted
by another one (to be implemented/rerouted). In this case is sufficient to set "priority=1" to be sure that
the existing resource will never be pre-empted.
Setting defaultSetUpPriority and setUpPriority in path/trail definition phase
The new "defaultSetUpPriority" attribute may be set in the path/trail definition phase. If the allocated (or
implemented) path/trail doesn't cross the ASON domain this new attribute is not managed.
If the allocated (or implemented) path/trail crosses the ASON domain at least one SNC is created and this
attribute is managed. In particular the "setUpPriority" attribute value of the created SNC(s) will mirror the
related attribute of the path/trail which belongs to.
Modify defaultSetUpPriority on path/trail
The user can modify the "defaultSetUpPriority" attribute value of a path/trail in any configurationState
(defined, allocated or implemented).
The modification is performed by the updSncAttrs action (see SNML-IM impacts). The user can choose
to propagate or not this modification to the related SNC(s) (if any). A flag in the GUI permits to do that.
Suggested behaviour is to align the "setUpPriority" of the SNC(s) with the related value of the path/trail.
Modification of setUpPriority on SNC
The user can modify the "setUpPriority" attribute value of a SNC.
The modification is performed by the updSncAttrs action (see SNML-IM impacts).
The SNC "setUpPriority" modification is not propagated to the path/trail belongs to. This behaviour is jus-
tified in the case of a path/trail having two or more SNCs. In general the SNCs don't have the same "set-
UpPriority" value, then the path/trail "defaultSetUpPriority" attribute cannot reflect the situation of different
attribute values; for this reason an alignment is not meaningful and cannot be required.

setup priority 5
SNC-2
priority 4
setup priority 5
SNC-1
priority 4
Figure 870. Example: setUpPriority_2 > priority_1
CONDITION RESULT
setUpPriority_2 < priority_1 SNC2 can pre-empt SNC1
setUpPriority_2 = priority_1 SNC2 cannot pre-empt SNC1
setUpPriority_2 > priority_1 SNC2 cannot pre-empt SNC1

4.5 NE CONSTRAINTS
The routing algorithm is aware about node connectivity restrictions.
The equipment doesn't support some type of connection (e.g. old-generation ADMs can perform
Bridge&Switch only between one tributary port and two aggregate ports)
Even if the equipment supports it, in that moment it is not able to implement it (e.g. 1661smc and 1651smc
can provide some HO connections up to a fixed limit)
4.6 RM objects
The database contains the object classes which are described in the following.
NtwDomain
The ntwDomain (network domain) is the whole area controlled by the 1354RM.
Ntw (Network)
The network comprises all the interconnected SDH equipment. A network comprises sub-networks.
A network object instance has an associated symbol and a submap. The symbol represents the network
in the root submap, and "clicking" on it the corresponding submap can be opened.
EmlDomain
An EML domain is maintained by a single EML OS. This object is generated in order to inform the Operator
on the OS a certain NE belongs to.
An EML-domain contains the NEs managed by the EML OS.
NE
A Network Element is an SDH telecommunication equipment managed by the OS.
A node has an associated symbol and a submap. The symbol is used to represent the node in the submap
describing the topology of the sub-network or ET where the node is contained. Clicking" on the node, the
asociated submap will be opened. This submap contains the uploaded ports.
Physical Connection
A physical connection connects two ports in the network. These two ports belong to different NEs and must
have the same transmission rate.
A physical connection has a symbol, that is used to represent the physical connection in the submap asso-
ciated.
Site
The site is the name of the physical location of the object.
Port
The port represents the physical accesses of the SDH equipment.
A port is a physical interface of a node. Two ports with the same interface can be connected by means
of a physical connection.

A port has a graphical symbol, that is used to represent the port in the submap associated to the node.
Path
The path defines a connection between ends (NAPs) of the network.
Sbn
The subnetwork is a partitioning of the NML network. It contains Elementary topologies and intercon-
nected Nodes.
A sub-network is a grouping of nodes and ETs.
A sub-network has a symbol and a submap.
ConnInTopol
The connInTopol (connection in topology) describes a generic connection (subnetwork connection, net-
work connection) between two or more ends (they can be Naps,Caps or Ctps) to realize a path in any par-
titioning level.
A connInTopol between Naps corresponds to a path.
Cap
The Cap (Connection access point) is a higher order trail termination. It can be the client access point
towards the network.
Ctp
Connection termination point. It is a physical termination point.
Ms CtpCap
It represents both the Msctp and the mscap entities related to an SDH physical port at MS layer.
NPA
Network Protection architecture. It is a protection modalkity, to be applied to a selected set of physical con-
nections.
SNC
Subnetwork connection. It is a connection internal to ASON-GMRE network.

NE
nap
connInTopol
nap
LOPL
td
HOPL
connInTopol
MSL
msctpcap
msctpcap
Figure 871. Schematic representation of the NE
Trail
It describes the connectivity between two caps in any partitioning level and in any layer. It defines the
association between client access points in the same transport network layer.
LOlink connection
ctp ctp LO
HOtrail
cap cap
HO
HO link connection
ctp ctp
ms trail
MS
msctpcap msctpcap
Figure 872. Trail and link connections

Link Connection
The link connection describes the connectivity between two CTPs in any partitioning level and in any layer.
The figure which follows describes the objects involved in the structure.
Figure 873. Objects involved in the structure

4.6.1 OTN WDM model
The model of the PRE-OTN WDM network managed by 1354RM includes several layers, as shown in fig-
ure below.
CLIENT LAYER ( SDH or generic )
OCH ( B / W ) OCH ( colored )
OMS
OPS-UNI OTS ( n lambda n>=1 )
Figure 874. WDM network managed model.
where:
OTH=optical transport hierarchy
OCH=optical channel
OMS=optical multiplex section
OTS=optical transmission section
NNI=network node interface
UNI=user to network interface
CBR=constant bit rate
OCH B / W= optical channel Black and White
In particular:
– OTS represents the transport section and includes:
• OTS ports ( NNI )
• OTS Physical connections representing the interconnections between OTS ports
Ports of Repeaters ( ILA ) are not treated by 1354RM.
Repeaters can be correlated to OTS physical connections

– OMS represents the Optical multiplex section and includes:
• OMS TPs
• OMS Trails representing the logical interconnection between OMS TPs
– OPS-UNI represents the physical interconnection between:
• UNI ports ( OGPI ) of WDM NEs ( e.g. back to back with or without transponders )
• UNI ports of WDM NEs and SDH ( or CBR ) NEs
It includes:
– OPS ( Optical physical section ) ports (=OGPI ports )
– OPS Physical connections representing the interconnections between OPS ports
– OCH ( colored ). It represents the Optical Channel (lambda) and includes:
• OCH CTPs on the MUX-DeMUX functional block
• OCH Link Connections connection ( LC's ) “logically interconnecting" OCH CTPs at the same
frequency
OCH LC
OCH-CTP
OCH-CTP
OMS Trail
OMS TP OMS TP
OTS Phys Conn

OTS Port OTS Port
Figure 875. WDM model.
– OCH (colored) layer includes:
• OCH TTPs representing the generation of the Lambda ( on Transponders )
• OCH trails representing the logical interconnections between OCH TTPs crossing OCH CTPs,
OCH LCs and OCH cross connections
• Not complete OCH Trails named OCH raw connections
In addition:
• OADMs provide OCH pass-through at the same Lambda (pass-through of the extra-band),
called by 1354RM, OCH pass-through cross-connection.
• 1696MS is able to perform OCH pass-through cross-connections changing frequency (O/E/O

conversion in MCC)

– The CLIENT LAYER represents the CBR / TDM service of the WDM network.
The Client path is the representation of this service. In case of SDH the client path is a trail at the
regenerator section layer.
The Client Layer includes:
• Client CTPs on transponders, that is TPs on I/O directions like rs-CTPs, gdc-CTPs, ochgdc
CTPs)
• Client Link Connections logically connecting client CTPs
• Client paths interconnecting client terminations ( client NAPs ) with a sequence of LCs and
cross-connections.
• The Client path is never terminated on WDM NEs
• OPC or OCP protections are managed by RM as client layer protected cross-connections
– The OCH ( B / W ) is a “technical layer' added at RM level to balance the model mainly in case of
SDH inter-working. It contains objects with no counterpart in the NE.

PATH
. connInTopol
LOlc(TU3#1) nap
nap
LOPL
140cap1 (VC4)
(VC4) HOtrail(VC4S1)
# 140cap1
connInTopol
connInTopol
ctp16
HOlc ( AU4#16) ctp1
HOlc ( AU4#1) HOPL
MS
ms trail
mstp mstp
OSPI
OSPI
physConn
rsttp
rsttp
rs trail = CLIENT PATH
4x2.5
clientctp
clientctp rsct
rsct client lc client lc client lc client lc
4x2. ODU ODU ODU ODU

4x2.
ochtrail ochtrail ochtrail ochtrail
ochttp ochttp
ochttp
OCHlc OCHlc OCHlc OCHlc

ochctp ochctp ochctp
ochctp
omstrail omstrail
opsphyscon
OMSTTP
OMSTP
opsphyscon
OMS-LC OMS-LC OPS
OP
OMSCTP
opsport opsport
SDH otsphyscon SDH
OTS OTS
otsport otsport otsport otsport

OSPIclone LT LT OSPIclone
OADM
Figure 876. SDH-WDM interconnection scheme
N.B. For more detailed information see section ASON-GMRE

4.6.2 Integrated approach
1354RM manages SDH and WDM networks with an integrated approach.
When the WDM interconnection is inserted in RM between a SDH-NE and a WDM transponder, the same
SDH port is presented two times:
– SDH representation to accomplish the SDH physical connection
– WDM-OPS representation to accomplish the OPTICAL physical connection
Namely the SDH physical connection is merely a logical connection from SDH to SDH port, while OPTI-
CAL physical connections maintain physical properties.
4.6.3 Functions
1354RM allows:
– upload of WDM NEs and ports from 1353SH
– placement of WDM NEs into RM topologies
– definition of OTS links and single lambda interconnections (OPS) between WDM NEs. OPS links are
needed for coloured or B/W back-to-back interconnections
– declaration of connectivity between SDH and WDM networks on a single map
– the upload of an existing connectivity at OCH and client layer during the implementation of physical
connections. The uploaded connectivity first generates raw connections and then OCH trails and in
turn client raw connections and client paths.
The type of WDM connection is OPS for SDH-WDM connection, OTS for WDM-WDM connection.

4.7 Object Names
RM object names characters used are:
– A-Z, a-z, 0-9, all special characters except: tilde (~), backslash (\), pipe (|), double quote ("), TAB
The maximum object username lenght is:
The length of the user label of the path is extended up to 130 characters.
As a consequence, the length of the user label of other entities related to the length of the user label of
the path is extended. In particular:
– port: the length of the user label is extended up to 132 characters (path user label length + 2)
– trail: the length of the user label is extended up to 138 characters (path user label length + 8)
– snc: the length of the user label is extended up to 141 characters (trail user label length + 3)
– pmTransp: the length of the user label is extended up to 138 characters (trail user label length)
In addition, the length of the customer field of the path (comment3 attribute) is extended up to 45 char-
acters.
The length of the user label of the NPA is extended up to 92 characters.
As a consequence, the length of the user label of other entities related to the length of the user label of
the npa is extended. In particular:
-msProtBlock, msProtBlock4f and msProtBlockLinear: the length of the user label is extended up to 125
characters (node user label length + npa user label length + 1)

ABBREVIATIONS AND GLOSSARY
ABBREVIATION MEANING
ACA Access Control Administration tool
ACD Access Control Domain
ADM Add Drop Multiplexer
AIS Alarm Indication Signal
ALS Automatic Laser Shutdown
AP Access Point
APS Automatic Protection Switching
AS Alarm Surveillance
ASAP: Alarm Severity Assignment Profile
ALMAP ALcatel MAnagement Platform
ATM Asynchronous Transfer Mode
AU Administrative Unit
AU PJC Administrative Unit Pointer Justification Counter
BER Bit Error Rate
BN Backbone Network
BR & SW Bridge & Switch
Browser Application which allows to browse all RM-MIB objects
CAP Client Access Point. It represents a point where a client layer can
access a server layer ( i.e. a VC-4 that is configured to carry lower
order signals is a HO-CAP)
CCITT Telegraph and Telephone International Consultative Committee
CCLNP ConnectionLess Network Protocol
CDCC Data Communication Channel
CD-ROM Compact Disc Read Only Memory
CI Communication Infrastructure

Abbreviations and Glossary 3AL 61269 AAAA Issue 4 837/854
CLNS ConnectionLess Network Service
CMISE Common Management Information Service ( ISO/OSI protocol )
CMOT Common Management Info Protocol on TCP/IP
CTP Connection Termination Point
CT Craft Terminal
DBMS Data Base Management System
DCI Drop & Continue Interconnection
DCN Data Communications Network
D&C Drop & Continue
DS Degraded Signal
DVB Digital Video Broadcasting
DWDM Dense Wavelength Division Multiplexing
ECC Embedded Communication Channels
EML Element Management Layer
EML domain A set of NEs that are maintained by the same EML-OS.
EPS Equipment Protection Switching
EM-OS Element Manager-Operation System
EMS Event Management Services
ESCON Enterprise Systems CONnection
ESN Elementary Subnetwork
ET Elementary Topology. It is a grouping of some nodes connected

according to specific rules. A typical ET is a ring.
FAD Functional Access Domain
FDDI Fiber Distributed Data Interface
FEC Forward Error Correction
FERF Far End Received Failure
FLS Frame Loss Second
Gbit/s Gigabits per second
FM FM Fault Management
FOX Fiber Optic Extender

838/854 3AL 61269 AAAA Issue 4 Abbreviations and Glossary
GIF Graphics Interchange Format
GNE Gateway Network Element
HMI Human Machine Interface
HO-AP High Order Access Points
HOA High Order Assembler
HO Matrix High Order Matrix
HOP-LN High Order Path Layer Network
HOPL HOPL Higher Order Path Layer
HP Higher Path Traffic
HPA High Order Path Adaptation
HPC High Order Path Connection
HPT High Order Path Termination
HP-OV Hewlett Packard OpenView
HP-OVW Hewlett Packard OpenView Windows
HP-UX Hewlett Packard Unix
HP-VUE Hewlett Packard Visual User Environment
HVC Higher Order Virtual Container
HTML Hyper Text Markup Language
IAP Inventory Application
IPC InterProcess Communication
ISA Integrated SDH ATM
Isn Interface between NML and SML
Link Connection (lc ) A transport entity provided by the client/server association.It is

formed by a near-end adaptation function,a server trail and a far-
end adaptation function between connection points. It can be con-
figured as part of the trail management process in the associated
server layer.
IEEE Institute of Electrical and Electronics Engineers
IM Information Manager
Kbit/s Kilobits per second
LAN Local Area Network

LO-AP Low Order Access Point
LOF Loss of Frame alignment
LOP Loss of Pointer
LP Lower Path traffic
LSP "Link single fault protection" index (LSP). The LSP index is deter-
mined (in a way similar to NSP for nodes) taking into account of
both the number (C) of archs belonging to the main route and the
number (D) of archs belonging to the main and spare routes.
Map Set of related objects , backgrounds,symbols and submaps
that provides a graphical and hierarchical representation of the
network.
LOS Loss Of Signal
LOT Loss Of Tributary
Mbit/s Megabits per seconds
MIB Management Information Base
MS Multiplex Section
MS-AP Multiplex Section Access Point
MS-CTPCAP Multiplex Section Termination Point
MS-EXBER Multiplex Section Excessive BER
MS-RDI Multiplex Section Remote Defect Indication
MSL Multiplex Section Layer
MSP Multiplex Section Protection
MS Spring Multiplex Section Shared Protection Ring
MS SIGDEG Multiplex Section Signal Degrade
MST Multiplex Section Termination
MS-LN Multiplex Section Layer Network
NAD Network Access Domain
NAP Network Access Point
NE Network Element
NML Network Management Layer
Node It is the view of the NE at NML level
NPE Network Protection Equipment-4 fibre MS Spring

NSAP Network Service Access Point
NSP "Node single fault protection" index (NSP). The NSP index is deter-
mined taking into account of both the number (A) of Nodes belong-
ing to the main route and the number (B) of Nodes belonging to the
main and spare routes, except the end nodes.
NTP NetworkTime Protocol
OAD Object Access Domain
OADM Optical Add-Drop Multiplexer
OCC Optical Channel Carrier
OCh Optical Channel
OCG Optical Channel Group
OFS Out of Frame Seconds
OH OverHead
OMS Optical Multiplex Section
OOS OTM Overhead Signal
OPS Optical Physical Section
OS Operation System
OSC Optical Supervisory Channel
OTH Optical Transport Hierarchy
OTM Optical Transport Module
OTN Optical Transport Network
OTS Optical transport Section
OXC Optical Cross-Connect
PCMAP Payload Configuration Management Application
PDH Plesiochronous Digital Hierarchy
Physical Connection A Physical Connection connects two SDH ports in the network.
These two ports belong to different NEs and must have the same
transmission rate.
PM Performance Monitoring
POH Path Overhead
Port Physical Interface of a Node. A port can be SDH or PDH.
PRC Protection and restoration combined

Q3 OSI Interface based on CMISE
Qnn Q3 Interface between 1354RM and 1354NN
PI Physical Interface
PPI PDH Physical Interface
PTM Path Trace Mismatch
RC Raw Connection
RS Regenerator Section
RSOH Regeneration Section OverHead
RST Regenerator Section Termination
SA Section Adaptation
SCSI Small Computer Serial Interface
sbn Subnetwork. It is a grouping of nodes and ETs.
SDH Synchronous Digital Hierarchy
SEN-IM Simple Element Network Information Model
SD Signal Degrade
SF Signal Failure
SMF System Management Features
SNML Sub-network Management Layer
SNCP Subnetwork Connection Protection
SONET Synchronous Optical Network
SPI SDH Physical Interface
STM Synchronous Transport Module
STM-N Synchronous Transport Module level N (N Integer = 1,4 or 16)
TDM Time Division Multiplexing
TE Transport Entity (generic term for Path or Trail in 1354RM)
TF Transmit Fail
TM Terminal Mode
TMN Telecommunications Management Network
TN Telecommunications Network
TCA Threshold Crossing Alarm

TP Termination Point
Trail A transport entity in a server layer responsible for the integrity of

transfer of characteristic information from one or more client net-
work layers between server layer access points.It defines the
association between access points in the same transport network
layer. It is formed by combining a near-end trail termination func-
tion, a netwrwork connection and a far-end trail-termination func-
tion.
Trail termination A transport processing function which generates the characteristic

information of a layer network and ensures integrity of that char-
acteristic information. The trail termination defines the association
between the access point and termination connection point and
these points thereofore delimit the trail termination.
TSD-IM Same as QB3 protocol. Information Model for interworking

between Network Managers and Network Elements.
TTP Trail Termination Point
TU Transport Unit
TU PJC Transport Unit Pointer Justification Counter
USM User Service Manager
VC Virtual Container
UPA Unavailable path alarm
URU Underlying Resource Unavailable
WDM Wavelength Division Multiplexing
WLA WaveLength Adapter
WTR Wait Time to Restore
XC Cross-Connect
Add and Drop Multiplexer:

Equipment used to combine several signals to produce one signal at a higher rate and to decompose it
back to the original lower rate signals.
Administrator:
A user who has access rights to all the Management Domains of the SDH Manager product. He has
access to the whole network and to all the management functionalities.
Alarm:
An alerting indication to a condition that may have an immediate or potentially negative impact on the state
of an equipment or the OS. An alarm is characterized by an alarm begin and an alarm end.
Alarm Indication Signal:

Alarm linked to the physical interface, associated with a probable alarm occurrence in the normal trans-
mission of the signal.

Automatic laser Shutdown:
Functionality provided by the SDH Manager to cut the laser source automatically in case of system failure.
Automatic Protection Switching:

Functionality related to Network Elements that automatically switches from the degraded resources to the
redundant or spare resources. This assures the best quality of transmission service.
Alarm Severity Assignment Profile:

Function allowing the assignment of severities to the alarms depending on their probable causes.
Alarm Status:
Identifies the type and severity of an occurring alarm.
Administrative Unit:
Entity composed of a high order virtual container (VC4) to which is added a pointer indicating the position
of the virtual container in the STM-N frame.
Administrative Unit pointer Justification Counter:

Counter indicating whether positive, negative or null justification is undertaken in the administrative unit.
This counter enables the management of the synchronization and the coherence of the transmitted signal.
Bit Error Rate:

This determines the number of errored bits in a signal frame. If the value exceeds a certain threshold then
an alarm is generated.
Board:
A board is part of an NE. They are electronic cards that fit into slots in the NE.
Compact Disk Read Only Memory:

Data saving support from which the information can only be read. Is useful for stocking data due to its avail-
able memory space.
Craft Terminal:
Workstation or Personal computer (PC) from which local address to an NE is possible. It can be used to
configure or perform monitoring tasks on the NE.
Cross-connect (XC)
Cross-Connects provide the network with the Routing Capabilities, this is the possibility of routing one sig-
nal to a particular destination.
Digital Communication network:

Communication Network in which the transmission of data is done in a digitized format.
Degraded Signal:
Alarm sent when the number of errors detected in a received signal frame exceeds a certain threshold.
Embedded Communication Channel:

Communication channel used in conjunction with packet commuting networks (X25) to manage distant
SDH networks. These communication channels are related to the QECC* protocols.
Element Management Layer:

This apllication is responsible for the configuration and management of Network Elements.
Equipment Protection Switching:

Used to provide protection for cards within the ADM to protect traffic in the event of card failure.
Filter:

They are related to the alarms or events generated on an NE or internally within the OS itself. They can
be configured by an operator to reject specified types of notifications and limit the processing that is
applied to them.
Flushing:
This deals with logs. When a log is flushed, all its records are deleted.
Functional Access Domain:

It defines the range of functions which are available to a specified user.
Far End Receive Failure:

Alarm linked to the multiplex section termination functional block, indicating that a receiving problem is
occurring at the far end of a communication link.
Gigabits per second:

Unit that corresponds to the transmission of 109 bits every second.
Gateway Network Element:

It is a Network Element devoted to the control, from the OS, of those NEs providing a QECC* interface.
High Order Assembler:

Function of the SDH Manager that is composed of the Higher Order Path Adaptation and the Higher Order
Path termination functions.
High Order Matrix:

Defines the ports of an NE handling transmission rates greater than 140 Mbit/s.
High Order Path Adaptation:

Function used to assemble the low order virtual containers (VC12 and VC3) into the high order virtual con-
tainer (VC4).
High Order Path Connection:

Function dealing with the establishment of high order connections (cross connections and pass through
connections) in boards.
High Order Path Termination:

Function used to complete the high order virtual container path overheads and vice versa extract the path
overhead from these virtual containers.
High Order Virtual Container:

A virtual container associated with a 140 Mbit/s signal (VC4).

History Report:
This function enables operators to get information concerning performances, security or alarms on entities
composing the network, or on the network itself. The operator specifies the time period for which he
requires the report.
Information Manager:
Processes used by the SDH Manger that are the functional part of the SDH Manager applications.
International Telegraph and Telephone Consultative Committee:

Standard organization for telecommunications. Now called the ITU-T (International Telecommunication
Union).
Kilobits per second:

Line Terminal:
A line terminal is the end point of a communication link. it is used to transmit or receive signals. They can
undertake signal conversion functions (adapting a signal to two different transmission media) or multi-
plexing/demultiplexing functions.
Logs:
Logs are files used to store history data concerning the incoming notifications, operator commands and
system alarms. The size of the log can be configured.
Loss Of Frame:
Alarm linked to the regenerator section termination functional block, associated with the loss of signal
frame.
Low Order Matrix:

Defines the ports of an NE handling transmission rates less than 140 Mbit/s.
Loss Of Pointer:
Alarm linked to the section adaptation functional block, associated with the loss of a pointer in an admin-
istrative unit.
Loss Of Signal:
Alarm linked to the physical interfaces, associated with the absence of a received signal.
Loss Of Tributary Signal:

Alarm linked to the PDH physical interface, indicating the loss of a tributary signal.
Low Order Path Adaptation:

Function of the 21x2Mbit/s, 3x34Mbit/s and the 140 Mbit/s tributary boards that maps (or de-maps) the
tributary signal to (or from) the virtual containers used in the synchronous transport domain.
Low Order Path Connection:

Function of the 21x2Mbit/s, 3x34Mbit/s and the 140 Mbit/s tributary boards that routes the lower order sig-
nals to the STM-N frame.
Low Order Path Termination:

Function of the 21x2Mbit/s, 3x34Mbit/s tributary boards that completes the signal by adding the path over-
head.
Low Order Virtual Container:

A virtual container associated with a 2 Mbit/s (VC12) or a 34 Mbit/s (VC3).

Management Domain:
The SDH Manager product is partitioned into management domains for functional proposes. Each man-
agement domain is associated with functionalities that enable the operators to manage the NEs.
Media Access Control Address:

Represents the Level 2 address for Local Area Networks.
Megabits per second:

Management Information Base:

Describes all the managed objects controlled by the system. An OS MIB and an NE MIB exist.
Multiplexer:
Equipment used to combine several signals to produce a single signal at a higher transmission rate and
to decompose it back to the smaller rate signals.
Multiplex Section:
In general, represents the section containing the multiplexed signals.
Multiplex Section Protection:

Provides protection for an STM-N signal in case of channel failure or low transmission quality.
Multiplex Section Termination:

Function of the 140 Mbit/s and the STM-1 tributary boards and aggregate boards that completes the sec-
tion overhead of the signal frame and checks the coherence of the transmitted signal. This functional block
also manages alarms linked to the multiplex section.
Network Access Domain:

NADs are used to define the set of resources a user can manage.
Network Element:
Either a telecommunication equipment or groups parts of a Telecommunication Network. Have charac-
teristics compliant with CCITT recommendations.
Network Management Level:

Designates the management functions performed on networks elements assembled in a network.
Network Service Access Point:

This refers to the access point in layer 3 (network layer) of the OSI stack which provides services to the
transport layer (layer 4). This access point is identified by a unique NSAP address which is constructed
according to international standards. On the 1353NM an NSAP address must be provided to uniquely
identify the NE to be supervised.
Notification:
Spontaneous data received by the system concerning an NE.
Operation System:
A system dedicated to the supervision of NEs in a standard way, using protocols and interfaces. it offers to
the operator a set of functions necessary to supervise the NEs. The SDH Manager is an Operation System.
Operator:
The end-user of the SDH Manager. He supervises a part of the network that is dependant on his user profile.

Plesiochronous Digital Hierarchy:
Represents the standard of signals having transmission rates less than 155 Mbit/s. The synchronization
signals for PDH networks are derived from different sources.
Physical Interface:
Electrical transformers that decouple the line signals and adapt the form of signal for further transmission.
This functional block also manages clock extraction, signal loss monitoring and loopback functions.
PDH Physical Interface:

As above but restricted to the PDH signals (140Mbit/s, 34Mbit/s and 2Mbit/s).
Path Trace Mismatch:

Alarm linked to the lower order path termination functional block in the 21x2Mbit/s and 3x34Mbit/s tributary
boards, indicating that a mismatch of the signal path trace has occurred.
Port:
A physical point at which the Network Element can be attached to a transmission medium. A port is either
a termination point or an origination point.
Regeneration Section:
When there is at least one repeater between two interconnected equipments, each part of the line section
between two repeaters or between a repeater and an line system is called a regenerator section.
Regeneration Section Termination:

Functional part of the 140 Mbit/s and STM-1 tributary boards and aggregate boards that completes the
section overhead and checks the level of the incoming signal to determine the correctness of the frame
pattern.
Repeater:
Equipment used to regenerate a signal when it has travelled a long distance.
Section Adaptation:
Synchronizes the incoming higher order virtual container (VC 4) or the incoming STM-1 signal to the out-
going STM-1 frame or the outgoing high order virtual container.
Severity:
Linked to alarms, severities indicate the magnitude related to the failure.
Small Computer Serial Interface:

The Small Computer System Interface is an American National Standard for interconnecting computers
and peripheral devices. The SCSI standard includes specifications for a variety of device types.
Synchronous Digital Hierarchy:

Represents a standard of signals having transmission rates greater than, or equal to, 155 Mbit/s. They
are derived from PDH signals. the term synchronous indicates that the synchronization signal for SDH
networks are derived from incoming transmitted information signals.
SDH Physical Interface:

Physical interface linked to the SDH signals that converts the electrical signal to the optical signal and
detects the loss of signal during reception.
Session:
A session is a temporary association between an operator and the SDH Manager. A session always
begins with the identification and authentication of the operator (the login phase) and ends with the exit
of the operator from the SDH Manager (the logout phase). A session generally lasts a few hours.
Synchronous Transport Module level N:

Indicates the type of SDH signals that exist. N is an integer (either 1,4 or 16) representing the transmission
rate of the SDH signal. For example, an STM-1 signal has a transmission rate of 155 Mbit/s while an STM-
16 signal has a transmission rate of 2.5 Gbit/s.
Transmit Fail:
Alarm that indicate a dysfunction in the transmission of the signal.
Telecommunication Management Network:

Defines the concept of interoperable management of TNs. They provide an organized network structure
to achieve the interconnection of the different components of the TN and the services to process the infor-
mation.
Telecommunication Network:
Describes the network to be managed. Provides the transmission, the transport and the switching sup-
ports to the interconnected Network Elements.
Terminal Point:
Describes either the origin or the termination of a signal in an equipment. Is related to a port.
Thresholding:
This is the assignment of a specified value to monitored parameters ( for example BIt Error Rates) that,
when exceeded, generate trouble indications.
Tributary Unit:
Entity composed of a virtual container to which is added a pointer that indicates the position of the con-
tainer in the STM-N frame.
Tributary Unit Pointer Justification Counter:

Counter indicating wether positive, negative or null justification is undertaken in the tributary unit. This
counter enables the management of the synchronization and the coherence of the transmitted signal.
User Profile:
Identifies the functionalities of the SDH Manager to which a user has access. A finite number of predefined
user profiles is determined by a fixed set of FADs.
User Service Manager:

These are presentation processes used by the SDH Manager to manage the Human Machine Interface
and facilitate the interaction with the product.
Virtual Container:
Virtual Containers are managed by the SDH Manager. Entity composed of an information signal to which
a path overhead has been added. The path overhead is used in the management of the information signal.
Different types of virtual containers exist depending on the rate of the information signal. Lower and Higher
order virtual containers exist. The SDH norm identifies VC11, VC12, VC2, VC3 and VC4 virtual containers
named from the lowest (VC11) to the highest (VC4) container capacity.
Wrapping:
Wrapping is the technique that enables the most recent entries in a file to replace the oldest when a file
is full.

INDEX
A Lockout of Protection channels - span, 644

Lockout of Working channels - ring (LW-R), 644
Alarm Propagation, 568
Lockout of Working channels - span, 644
Alarms, 555
Logger, 801
ASAP, 560
Login, 48
Logout
Front panel, 49
B
Browser Main, 80
Buttons M
Push buttons, 45
MAINTENANCE, 590
Radio buttons, 45
Measure, 741
Menu bar, 46
Menus
C Cascading menu, 46
Cascading menus, 46 item, 46
CONSISTENCY, 676 Menu bar, 46
Consistency audit, 676 Mnemonics, 46
Consistency download, 676 Pop-up menu, 46
Pull down menu, 46
Mnemonics, 46
D Mouse
Drawing Windows, 112 Actions, 44
Buttons, 44
MS-SPRING request (trigger), 644
E MS-trail, 597
Multicolumn Windows, 114
EML, 614
F N
NAP, 177
fault localization, 590
Navigation to/from
Forced Switch / Span, 670
Alarms, 54
Forced Switch Ring, 667
NE, 615
Node, 622
H NODE CONDITION, 657
NPE Ring, 644
HO-trail, 595
P
I
Path, 180, 592, 606
Implementation, 168 Physical Connection, 617
Inhibition chain, 663 Physical connection, 594
Intermediate nodes, 644 PM, 740
Pop-up menus, 46
Probable Causes, 555
L protocol message, 644
Leg, 349 protocol reply, 644
List dialogue boxes, 47 protocol request, 644
Lockout, 663 Pull down menus, 46

Index 3AL 61269 AAAA Issue 4 851/854
R U
Ring, 156 Upload, 177
User Interface
Standard elements, 44
S
Scenarios, 663
Screen W
Lock, 49 Windows
SDH Manager Layout, 45
Main functionalities, 51 Menu, 45
Serving nodes, 644 Scroll bars, 45
signal Fail, 669 Workspace
Subnetwork, 120, 620 Types of, 48

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

Customer Documentation Feedback 3AL 61269 AAAA Issue 4 853/854
CUSTOMER DOCUMENTATION FEEDBACK
Handbook Data
Handbook title, release,version:
Handbook type:
Handbook part number and edition:
General Feedback Evaluation
SUBJECT 5(max) 4 3 2 1 (min)
Total evaluation
Info quantity
Info quality
Info structure
Consulting facility
Layout
Chapters Feedback Evaluation
HANDBOOK PARTS 5(max) 4 3 2 1(min)
PREFACE
CHAPTER 1
CHAPTER 2
CHAPTER 3
CHAPTER 4
CHAPTER 5
CHAPTER 6
CHAPTER 7
Your Comments (stricltly necessary when value is less than 3):
Suggestion for Improvement

Which subject to deepen:
How to deepen:
Subject to eliminate or reduce
Other comments/suggestions
Errors Identified
Reader Info
Name:
Company:
Address:
E-mail:
Phone:
854 1354RM Rel.7.4F User Guide

854/854 3AL 61269 AAAA Issue 4 Customer Documentation Feedback
3AL 61269 AAAA
Edition 4
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

1354rm74f Oh v1 I4 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1354rm74f Oh v1 I4 PDF

Uploaded by

Copyright:

Available Formats

1354RM

Regional Network Manager for SDH and Optical Networks

All other trademarks are the property of their respective owners.

The information presented is subject to change without notice. Alcatel-Lucent assumes no

Copyright © 2007 Alcatel-Lucent

3AL 61269 AAAA

All rights reserved.

LIST OF TABLES ........................................................................................................................... 25

1 GETTING STARTED .................................................................................................................... 37

User Guide 1354RM Rel.7.4F

1354RM Rel.7.4F User Guide

User Guide 1354RM Rel.7.4F

3 MAINTENANCE ........................................................................................................................... 555

1354RM Rel.7.4F User Guide

4 TECHNICAL ANNEXES ............................................................................................................... 803

User Guide 1354RM Rel.7.4F

INDEX ............................................................................................................................................... 851

CUSTOMER DOCUMENTATION FEEDBACK.............................................................................. 853

1354RM Rel.7.4F User Guide

User Guide 1354RM Rel.7.4F

1354RM Rel.7.4F User Guide

User Guide 1354RM Rel.7.4F

1354RM Rel.7.4F User Guide

User Guide 1354RM Rel.7.4F

1354RM Rel.7.4F User Guide

User Guide 1354RM Rel.7.4F

1354RM Rel.7.4F User Guide

User Guide 1354RM Rel.7.4F

1354RM Rel.7.4F User Guide

User Guide 1354RM Rel.7.4F

1354RM Rel.7.4F User Guide

User Guide 1354RM Rel.7.4F

1354RM Rel.7.4F User Guide

User Guide 1354RM Rel.7.4F

1354RM Rel.7.4F User Guide

User Guide 1354RM Rel.7.4F

User Guide 1354RM Rel.7.4F

User Guide 1354RM Rel.7.4F

PRODUCT RELEASE VERSION (N.B.)

1354RM 7.4F 7.5.0

N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

This document is intended to 1354RM Operators.

1354RM Rel.7.4F User Guide

ISSUE DATE DESCRIPTIONS

01 April 2008 Rel 7.4F (version 7.4.9)

02 June 2008 Rel 7.4F (version 7.4.9)

03 December 2008 Added Flexible X-connections procedures (section WDM)

04 May 2009 Added note to PM on MS trail (section Maintenance)

User Guide 1354RM Rel.7.4F

Table 1. Handbooks related to the specific software application

REF HANDBOOK Part Number Notes

[1] 1354RM Rel.7.4F

[2] 1354RM Rel.7.4F - Basic Network Management THIS

[3] 1354RM Rel.7.4F- Advanced Provisioning

Table 2. Documentation on CD-ROM

REF Documentation CD-ROM TITLE Part Number

1354RM Rel.7.4F CD-ROM-DOC EN 3AL 61278 AAAA

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

HANDBOOKS RELATED TO THE PRODUCT'S HARDWARE

Refer to WS supplier handbooks.

– COMPLIANCE WITH EUROPEAN NORMS

1354RM Rel.7.4F User Guide

N.B. The 1354RM user documentation is split in two handbooks.