MSS-8MSS-4 Outdoor ODU300 MPT-HC MPTHC PDF

9500 MPR
Indoor: MSS-8/MSS-4 + Outdoor: ODU300 / MPT-HC / MPT-

HC V2 / MPT-MC
Rel. 3.0.0
User Manual
3DB 18793 AAAA
Issue 1
December 2010
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 © 2010 Alcatel-Lucent
3DB 18793 AAAA

Issue 1
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 ........................................................................................................................... 19
PREFACE......................................................................................................................................... 21
Preliminary Information.............................................................................................................. 21
Applicability................................................................................................................................. 22
Scope ........................................................................................................................................... 22
History.......................................................................................................................................... 22
Change notes .............................................................................................................................. 23
Handbook Structure ................................................................................................................... 23
General on Alcatel-Lucent Customer Documentation ............................................................ 24
1 SAFETY, EMC, EMF, ESD NORMS AND EQUIPMENT LABELLING ........................................ 29

1.1 Declaration of conformity to CE marking and Countries List ......................................... 30
1.2 Specific label for MPR-E equipment .................................................................................. 31
1.3 Applicable standards and recommendations ................................................................... 32
1.4 Safety Rules ......................................................................................................................... 32
1.4.1 General Rules ................................................................................................................. 32
1.4.2 Labels Indicating Danger, Forbiddance, Command........................................................ 33
1.5 Electromagnetic Compatibility (EMC norms) .................................................................... 37
1.6 Equipment protection against electrostatic discharges .................................................. 38
1.7 Cautions to avoid equipment damage ............................................................................... 38
2 PRODUCT INFORMATION AND PLANNING ............................................................................. 39

2.1 Purpose and Function ......................................................................................................... 42
2.1.1 Innovative solutions ........................................................................................................ 42
2.1.2 Description ...................................................................................................................... 45
2.1.3 MSS Purpose, Function and Description ........................................................................ 46
2.1.4 Stacking configuration..................................................................................................... 49
2.1.5 ODU300 .......................................................................................................................... 51
2.1.6 MPT-HC .......................................................................................................................... 52
2.1.7 MPT-MC.......................................................................................................................... 53
2.1.8 MPT-HC V2..................................................................................................................... 54
2.1.9 Power Extractor .............................................................................................................. 55
2.1.10 MSS to Outdoor Unit interconnections.......................................................................... 56
2.1.11 Antennas ....................................................................................................................... 65
2.2 Radio capacity, channelling and modulation .................................................................... 66
2.2.1 ODU300 .......................................................................................................................... 66
2.2.2 MPT-HC/MPT-HC V2/MPT-MC ....................................................................................... 67
2.3 Standard Features ............................................................................................................... 70
2.4 Radio Configurations .......................................................................................................... 71
2.5 Typical System Configurations .......................................................................................... 71
2.6 Environmental and Electrical Characteristics................................................................... 75
2.6.1 System Parameters ........................................................................................................ 75
2.6.2 ODU300 .......................................................................................................................... 77
2.6.3 MPT-HC/MPT-HC V2 ...................................................................................................... 78
2.6.4 MPT-MC.......................................................................................................................... 80
2.6.5 Radio performances ....................................................................................................... 80
2.7 Parts Lists............................................................................................................................. 81
2.7.1 MSS ................................................................................................................................ 81
2.7.2 ODU300 (with internal lightning surge suppressor) ........................................................ 84
2.7.3 MPT-HC with internal diplexer ........................................................................................ 98
User Manual 9500 MPR Rel. 3.0.0

Table of Contents 3DB 18793 AAAA Issue 1 1/876
2.7.4 MPT-HC V2 with internal diplexer ................................................................................... 100
2.7.5 MPT-MC with internal diplexer ........................................................................................ 102
2.7.6 Part lists of MPT-HC/MPT-HC V2/MPT-MC with external diplexer ................................. 104
2.7.7 MPT-HC optical interface (mandatory for 1+1 configuration).......................................... 107
2.7.8 MPT-HC V2 external modules (mandatory for 1+0/1+1 configurations) ......................... 108
2.7.9 MPT-HC/MPT-HC V2/MPT-MC couplers ........................................................................ 108
2.8 Functional description ........................................................................................................ 109
2.8.1 MSS (Indoor Unit) ........................................................................................................... 109
2.8.2 DC Extractor ................................................................................................................... 122
2.8.3 ODU300 .......................................................................................................................... 123
2.8.4 MPT-HC .......................................................................................................................... 127
2.8.5 MPT-HC V2..................................................................................................................... 135
2.8.6 MPT-MC.......................................................................................................................... 136
2.8.7 Protection schemes ........................................................................................................ 138
2.8.8 Radio Transmission Features with ODU300................................................................... 144
2.8.9 Radio Transmission Features with MPT-HC/MPT-HC V2/MPT-MC................................ 146
2.8.10 TMN interfaces ............................................................................................................. 149
2.8.11 Admission control in Adaptive Modulation (only with ODU300) .................................... 149
2.8.12 Managed Services and profiles .................................................................................... 154
2.8.13 TDM and Ethernet traffic management......................................................................... 156
2.8.14 ATM Traffic Management.............................................................................................. 161
2.8.15 Ethernet Traffic Management ....................................................................................... 168
2.8.16 LAG (Link Aggregation Group) ..................................................................................... 170
2.8.17 Quality Of Services (QoS) ............................................................................................ 172
2.8.18 Cross-connections ........................................................................................................ 178
2.8.19 Synchronization for PDH/SDH/DATA............................................................................ 190
2.8.20 Synchronization for E1 ports with ASAP unit ................................................................ 197
2.8.21 Synchronization distribution from 9500 MPR to 9400 AWY.......................................... 197
2.8.22 Synchronization connection in Stacking configuration with Core protection ................. 198
3 NE MANAGEMENT BY SOFTWARE APPLICATION ................................................................. 199

3.1 WebEML start ....................................................................................................................... 199
3.2 WebEML Main View ............................................................................................................. 201
3.2.1 Tab-panels ...................................................................................................................... 202
3.2.2 Main Tool Bar Area ......................................................................................................... 203
3.2.3 Severity Alarm Area ........................................................................................................ 204
3.2.4 Domain Alarm Synthesis Area ........................................................................................ 205
3.2.5 Management State Control Area .................................................................................... 205
3.2.6 Selection Criteria ............................................................................................................ 206
3.3 How to configure a new equipment ................................................................................... 207
3.4 Menu Configuration ............................................................................................................. 208
3.4.1 Menu NE Time ................................................................................................................ 208
3.4.2 Menu Network Configuration .......................................................................................... 209
3.4.3 Menu Alarm Severities.................................................................................................... 215
3.4.4 Menu System Settings .................................................................................................... 217
3.4.5 Menu Cross connections ................................................................................................ 220
3.4.6 AUX Cross Connections ................................................................................................. 256
3.4.7 Menu VLAN Configuration .............................................................................................. 259
3.4.8 Traffic Descriptors ........................................................................................................... 259
3.4.9 Menu Profile Management.............................................................................................. 261
3.4.10 Ethernet Features Shell ................................................................................................ 266
3.5 Menu Diagnosis ................................................................................................................... 302
3.5.1 Alarms............................................................................................................................. 302
3.5.2 Log Browsing .................................................................................................................. 309
9500 MPR Rel. 3.0.0 User Manual

2/876 3DB 18793 AAAA Issue 1 Table of Contents
3.5.3 Remote Inventory ........................................................................................................... 312
3.5.4 Abnormal Condition List.................................................................................................. 313
3.5.5 Summary Block Diagram View ....................................................................................... 314
3.5.6 Current Configuration View............................................................................................. 329
3.6 Menu Supervision ................................................................................................................ 330
3.6.1 Access State ................................................................................................................... 330
3.6.2 Restart NE ...................................................................................................................... 331
3.6.3 MIB Management ........................................................................................................... 332
3.6.4 SW Licence..................................................................................................................... 334
3.7 Menu SW Download............................................................................................................. 335
3.7.1 Server Access Configuration .......................................................................................... 335
3.7.2 Init Sw Download ............................................................................................................ 336
3.7.3 Sw Status ........................................................................................................................ 337
3.7.4 How to upgrade the software from an older version ....................................................... 338
3.8 Tab-panel Equipment........................................................................................................... 339
3.8.1 General ........................................................................................................................... 339
3.8.2 Starting From Scratch ..................................................................................................... 342
3.8.3 Tab panels in the Resource Detail Area.......................................................................... 343
3.8.4 Alarms tab-panel............................................................................................................. 343
3.8.5 Settings tab-panel ........................................................................................................... 344
3.8.6 Remote Inventory tab-panel............................................................................................ 349
3.8.7 How to configure a new equipment ................................................................................ 350
3.9 Tab-panel Protection Schemes........................................................................................... 351
3.9.1 Equipment Protection Management ............................................................................... 356
3.9.2 Rx Radio Protection Management .................................................................................. 358
3.9.3 HSB Protection Management ......................................................................................... 360
3.10 Tab-panel Synchronization ............................................................................................... 362
3.10.1 Synchronization Sources assignment........................................................................... 363
3.10.2 Synchronization sources assignment rules .................................................................. 364
3.10.3 Allowed synchronization sources assignment .............................................................. 364
3.10.4 SSM Summary Table .................................................................................................... 365
3.11 Tab-panel Connections...................................................................................................... 366
3.12 PDH VIEW for PDH DOMAIN (this menu opens with double click on a PDH unit)....... 367
3.12.1 General information on the PDH domain menu ............................................................ 367
3.12.2 Alarms & Settings ......................................................................................................... 367
3.12.3 Loopback ...................................................................................................................... 373
3.13 SDH VIEW for SDH DOMAIN (this menu opens with double click on an SDH unit) .... 375
3.13.1 General information on the SDH unit ............................................................................ 375
3.13.2 Alarms........................................................................................................................... 375
3.13.3 Settings......................................................................................................................... 376
3.14 RADIO VIEW for RADIO DOMAIN ..................................................................................... 377
3.14.1 General information on the Radio domain menu .......................................................... 377
3.14.2 Alarms........................................................................................................................... 378
3.14.3 Settings......................................................................................................................... 378
3.14.4 Measurement................................................................................................................ 400
3.14.5 Loopback ...................................................................................................................... 402
3.14.6 Power Source ............................................................................................................... 405
3.15 ATM view for ATM DOMAIN (this menu opens with double click on an ASAP unit).... 407
3.15.1 E1 Layer ....................................................................................................................... 407
3.15.2 IMA Layer ..................................................................................................................... 408
3.15.3 ATM Layer..................................................................................................................... 410
3.15.4 ATM PW Layer.............................................................................................................. 416
3.16 Core-E VIEW for Core-E and ETHERNET DOMAIN (this menu opens with double click on
a Core-E unit) .............................................................................................................................. 418

3.16.1 Core-E domain.............................................................................................................. 418
3.17 AUX view for AUX DOMAIN (this menu opens with double click on the AUX peripheral unit)
429
3.17.1 Settings......................................................................................................................... 429
3.17.2 External Points.............................................................................................................. 430
3.18 WT Performance Monitoring Suite ................................................................................... 432
3.18.1 How to start the WT Performance Monitoring Suite...................................................... 432
3.18.2 Tool bar ......................................................................................................................... 432
3.18.3 Menu bar....................................................................................................................... 433
3.18.4 Menu available on the Bird’s Eye View......................................................................... 435
3.18.5 PM selectable options................................................................................................... 436
3.18.6 How to start and stop the PM ....................................................................................... 437
3.18.7 Ethernet Statistics ......................................................................................................... 440
3.18.8 RADIO PMs .................................................................................................................. 451
3.18.9 PDH Performance Monitoring ....................................................................................... 458
3.18.10 IMA Layer Statistics .................................................................................................... 464
3.18.11 ATM Interface Statistics............................................................................................... 466
3.19 VLAN management ............................................................................................................ 469
3.19.1 802.1D .......................................................................................................................... 469
3.19.2 802.1Q .......................................................................................................................... 470
3.20 Annex A: Network Element Overview .............................................................................. 474
3.20.1 Main view...................................................................................................................... 474
3.20.2 NE Configuration area .................................................................................................. 475
3.20.3 Status & Alarms area .................................................................................................... 477
3.20.4 Supervision Function .................................................................................................... 478
3.20.5 Menu bar....................................................................................................................... 478
4 INSTALLATION............................................................................................................................ 481
4.1 Hardware Installation........................................................................................................... 481
4.1.1 Power consumption ........................................................................................................ 482
4.1.2 Rack Installation ............................................................................................................. 483
4.1.3 ODU300 Installation........................................................................................................ 497
4.1.4 MPT-HC Installation ........................................................................................................ 518
4.1.5 MPT-HC V2 Installation................................................................................................... 579
4.1.6 MPT-MC Installation........................................................................................................ 592
4.1.7 DC Extractor ................................................................................................................... 628
4.1.8 Nose Adapter for MPT-HC/V2 and MPT-MC .................................................................. 629
4.1.9 Flextwists for MPT-HC/V2 and MPT-MC......................................................................... 629
4.1.10 Indoor Installation ......................................................................................................... 630
4.1.11 Antenna Alignment........................................................................................................ 680
4.2 Software local copy ............................................................................................................. 689
4.2.1 Getting Started ................................................................................................................ 690
4.2.2 PC Characteristics .......................................................................................................... 690
4.2.3 Local copy of the Software Package (SWP) to the PC ................................................... 691
4.2.4 Local copy of the WebEML and TCO Suite Software to PC ........................................... 693
4.2.5 Configure PC Network Card to Connect to NE ............................................................... 700
4.2.6 Download Software Package to NE................................................................................ 704
5 PROVISIONING............................................................................................................................ 711
5.1 Provisioning by Provisioning Tool..................................................................................... 711
5.1.1 Start Provisioning Tool .................................................................................................... 711
5.2 Provisioning by WebEML.................................................................................................... 740
5.2.1 Start WebEML................................................................................................................. 740
5.2.2 Provisioning .................................................................................................................... 743

6 MAINTENANCE AND TROUBLE-CLEARING ............................................................................ 793
6.1 Introduction .......................................................................................................................... 793
6.2 Maintenance Philosophy..................................................................................................... 794
6.3 Personal Computer (PC)/Laptop ........................................................................................ 794
6.4 Troubleshooting................................................................................................................... 794
6.4.1 Before Going to Site Checklist ........................................................................................ 794
6.4.2 Troubleshooting Basics................................................................................................... 795
6.4.3 Troubleshooting Path Problems...................................................................................... 813
6.4.4 Troubleshooting Configuration Problems........................................................................ 815
6.4.5 Troubleshooting Ethernet Problems ............................................................................... 815
6.4.6 Troubleshooting TMN Problems ..................................................................................... 816
6.5 Card Removal and REPLACEMENT ................................................................................... 817
6.5.1 Core-E Card Removal and Replacement – Core-E Protected Radio ............................. 819
6.5.2 Flash card replacement procedure ................................................................................. 819
6.5.3 ODU300 or MPT-HC V2 or MPT-MC removal and replacement..................................... 820
6.5.4 MPT-HC removal and replacement................................................................................. 820
6.6 Upgrade from Not Protected to a Protected Radio (with ODU300) ................................. 821
6.6.1 1+0 Adaptive Modulation to 1+1 HSB Adaptive Modulation and 1+1 EPS..................... 821
6.6.2 1+0 Static Modulation to 1+1 HSB Static Modulation and 1+1 EPS ............................... 822
6.6.3 1+0 to 1+1 Frequency Diversity and 1+1 EPS................................................................ 822
6.7 Upgrade from Not Protected to a Protected Radio (with MPT-HC/MPT-HC V2 or MPT-MC)
823
6.7.1 1+0 Adaptive Modulation to 1+1 HSB/FD Adaptive Modulation and 1+1 EPS ............... 823
6.7.2 1+0 Static Modulation to 1+1 HSB/FD Static Modulation and 1+1 EPS ......................... 824
6.8 Downgrade from Protected to a Not Protected Radio (with ODU300) ............................ 825
6.8.1 1+1 HSB Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation..................... 825
6.8.2 1+1 HSB Static Modulation and 1+1 EPS to 1+0 Static Modulation ............................... 826
6.8.3 1+1 FD to 1+0 ................................................................................................................. 826
6.9 Downgrade from Protected to a Not Protected Radio (with MPT-HC/MPT-HC V2 or MPT-MC)
827
6.9.1 1+1 HSB/FD Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation ............... 827
6.9.2 1+1 HSB/FD Static Modulation and 1+1 EPS to 1+0 Static Modulation ......................... 828
6.10 Cleaning.............................................................................................................................. 828
7 LINE–UP AND COMMISSIONING ............................................................................................... 829

7.1 Introduction .......................................................................................................................... 830
7.1.1 General ........................................................................................................................... 830
7.1.2 Safety–EMC–EMF–ESD norms and cautions to avoid equipment damage ................... 831
7.1.3 Conventions.................................................................................................................... 831
7.1.4 Summary of the line–up, commissioning, and acceptance phases ................................ 832
7.1.5 General information about test bench drawings ............................................................. 833
7.2 Commissioning of STATION A – phase 1 (Turn up).......................................................... 834
7.2.1 Turn–on preliminary operations ...................................................................................... 834
7.2.2 Powering up the MSS(s) with ODU(s) connected........................................................... 835
7.3 Commissioning of STATION B – phase 1 (Turn up).......................................................... 836
7.4 Fine antenna alignment and preliminary checks – Stations A & B ................................. 836
7.4.1 Fine antenna alignment .................................................................................................. 836
7.4.2 Preliminary checks.......................................................................................................... 836
7.5 End of commissioning phase 1 (Turn up) in STATION A ................................................. 840
7.6 Commissioning station A – phase 2 (acceptance test) .................................................... 841
7.6.1 Installation and cabling visual inspection ........................................................................ 843
7.6.2 System configuration ...................................................................................................... 843
7.6.3 P32E1 unit ...................................................................................................................... 848
7.6.4 STM-1 unit ...................................................................................................................... 851

7.6.5 16E1/DS1 ASAP unit ...................................................................................................... 854
7.6.6 AUX unit.......................................................................................................................... 854
7.6.7 Core-E unit...................................................................................................................... 855
7.6.8 NE configuration ............................................................................................................. 855
7.6.9 Data/Time settings .......................................................................................................... 856
7.6.10 E1 Hop stability test ...................................................................................................... 856
7.6.11 STM-1 Hop stability test ................................................................................................ 858
7.6.12 Ethernet Traffic stability test.......................................................................................... 860
7.6.13 ATM Traffic stability test ................................................................................................ 864
7.6.14 64 kbit/s Service Channel functionality test (optional) .................................................. 866
7.7 Commissioning station B – Phase 2 (acceptance Test) ................................................... 867
7.8 Final operations ................................................................................................................... 867
7.9 Annex A: fine antenna alignment ....................................................................................... 867
ABBREVIATIONS ............................................................................................................................ 869
CUSTOMER DOCUMENTATION FEEDBACK.............................................................................. 875

LIST OF FIGURES
Figure 1. Multiservice Aggregation Layer ......................................................................................... 42
Figure 2. Service Awareness ............................................................................................................ 43
Figure 3. Packet Node ...................................................................................................................... 44
Figure 4. Service-driven Packet Adaptive Modulation ...................................................................... 44
Figure 5. Naming Convention ........................................................................................................... 45
Figure 6. MSS-8 shelf ....................................................................................................................... 46
Figure 7. MSS-4 shelf ....................................................................................................................... 46
Figure 8. MSS-8 block diagram ........................................................................................................ 48
Figure 9. MSS-4 block diagram ........................................................................................................ 48
Figure 10. Stacking configuration with 3 MSS .................................................................................. 49
Figure 11. Stacking configuration with 3 MSS with Core protection.................................................. 50
Figure 12. ODU300........................................................................................................................... 51
Figure 13. MPT-HC ........................................................................................................................... 52
Figure 14. MPT-MC........................................................................................................................... 53
Figure 15. MPT-HC V2...................................................................................................................... 54
Figure 16. Power Extractor ............................................................................................................... 55
Figure 17. MSS to ODU300 interconnection..................................................................................... 56
Figure 18. MSS to MPT-HC interconnection ..................................................................................... 57
Figure 22. MSS to MPT-HC V2 interconnection ............................................................................... 61
Figure 25. MSS to MPT-MC interconnection .................................................................................... 64
Figure 26. MPT-HC/MPT-HC V2 directly connected to the battery ................................................... 65
Figure 27. PDH/ATM Over Ethernet Packet Node - Mapping of 32 E1 and
16 E1 ATM on Ethernet..................................................................................................................... 72
Figure 28. PDH/SDH/ATM and Ethernet Terminal Packet Transport 32 E1, 2xSTM-1 and
16 E1 ATM Access, 1 Radio Direction .............................................................................................. 72
Figure 29. PDH/SDH/ATM and Ethernet Add/Drop Packed Node-Ethernet and 32 E1, 2xSTM-1 and 16
E1 ATM Local Access, 1 Back Link, 1 Haul Link .............................................................................. 73
Figure 30. PDH/SDH/ATM and Ethernet Terminal Packet Node-Ethernet and 32 E1, 2xSTM-1 and
16 E1 ATM Local Access, 2 Back Links............................................................................................ 73
Figure 31. PDH/SDH/ATM and Ethernet Add/Drop Packet Node-Ethernet and 32 E1, 2xSTM-1 and
16 E1 ATM Local Access, 1 Back Link and 2 Haul Links.................................................................. 74
16 E1 ATM Local Access, 2 Haul Links and 2 Back Links ................................................................ 74
Figure 33. Power Distribution Architecture ....................................................................................... 110
Figure 34. Core-E unit....................................................................................................................... 111
Figure 35. Core-E unit....................................................................................................................... 113
Figure 36. 32xE1 Local Access unit.................................................................................................. 113
Figure 37. PDH Access unit.............................................................................................................. 114
Figure 38. 2xSTM-1 Local Access unit ............................................................................................. 114
Figure 39. STM-1 Access unit........................................................................................................... 115
Figure 40. ASAP simplified block diagram........................................................................................ 117
Figure 41. ASAP unit ........................................................................................................................ 118
Figure 42. Modem unit ...................................................................................................................... 118
Figure 43. Modem unit ...................................................................................................................... 119
Figure 44. MPT Access unit (with PFoE) block diagram................................................................... 120
Figure 45. MPT Access Unit (with PFoE) ......................................................................................... 121
Figure 46. DC Extractor .................................................................................................................... 122

List of Figures 3DB 18793 AAAA Issue 1 7/876
Figure 47. ODU300 housing ............................................................................................................. 123
Figure 48. ODU block diagram ......................................................................................................... 124
Figure 49. MPT system ..................................................................................................................... 128
Figure 50. 11-38 GHz MPT-HC housing ........................................................................................... 128
Figure 51. 6 GHz MPT-HC housing .................................................................................................. 128
Figure 52. 7-8 GHz MPT-HC housing ............................................................................................... 129
Figure 53. MPT-HC block diagram.................................................................................................... 129
Figure 54. 7/8 GHz MPT-HC architecture ......................................................................................... 132
Figure 55. 11 to 38 GHz MPT-HC architecture ................................................................................. 133
Figure 56. MPT-HC V2 housing (6 GHz and 11 GHz to 38 GHz) ..................................................... 135
Figure 57. 6 GHz and from 11 to 38 GHz MPT-MC housing............................................................. 136
Figure 58. 7-8 GHz MPT-MC housing............................................................................................... 136
Figure 59. MPT-HC/MPT-HC V2 protection schemes....................................................................... 139
Figure 60. MPT-MC protection schemes .......................................................................................... 141
Figure 61. Available loopbacks ......................................................................................................... 145
Figure 62. Available loopbacks ......................................................................................................... 147
Figure 63. Example of traffic in case of 28MHz bandwidth and Admission Control Enabled............ 150
Figure 64. Example of traffic in case of 28MHz bandwidth and modulation downgraded to 16QAM 151
Figure 65. Example of traffic in case of 28MHz bandwidth and modulation downgraded to 4QAM . 151
Figure 66. Example of traffic in case of 28MHz bandwidth and Admission Control Disabled........... 152
Figure 67. Example of traffic in case of 28MHz bandwidth and modulation downgraded to 16QAM 153
Figure 68. Example of traffic in case of 28MHz bandwidth and modulation downgraded to 4QAM . 153
Figure 69. Traffic profiles .................................................................................................................. 156
Figure 70. Traffic profiles .................................................................................................................. 157
Figure 71. E1 Traffic.......................................................................................................................... 158
Figure 72. E1 Traffic.......................................................................................................................... 159
Figure 73. STM-1 Traffic ................................................................................................................... 160
Figure 74. E1 Traffic.......................................................................................................................... 160
Figure 75. ATM Traffic Management - General block diagram ......................................................... 161
Figure 76. Block diagram for ATM Ingress (ATM -> Packet) direction .............................................. 162
Figure 77. ATM Traffic Management on Modem card - Block diagram............................................. 165
Figure 78. ......................................................................................................................................... 170
Figure 79. ......................................................................................................................................... 171
Figure 80. ......................................................................................................................................... 171
Figure 81. QoS in the Core-E unit..................................................................................................... 173
Figure 82. QoS in the Modem unit .................................................................................................... 175
Figure 83. Cross-connection............................................................................................................. 178
Figure 84. Synchronization distribution from MPR to AWY............................................................... 197
Figure 85. Synchronization connection in Stacking configuration with Core protection .................... 198
Figure 86. MSS-8 Main view............................................................................................................. 201
Figure 87. MSS-4 Main view............................................................................................................. 202
Figure 88. Alarm Severities Profile ................................................................................................... 215
Figure 89. System Settings menu..................................................................................................... 217
Figure 90. Main Cross-Connections View......................................................................................... 220
Figure 91. LAG Radio and LAG Ethernet ......................................................................................... 221
Figure 92. Cross-connections Example ............................................................................................ 222
Figure 93. Creating cross-connection between PDH and radio........................................................ 223
Figure 94. Cross-connections buttons .............................................................................................. 223
Figure 95. Segregated Port View (default configuration) .................................................................. 224
Figure 96. ......................................................................................................................................... 224
Figure 97. ......................................................................................................................................... 225
Figure 98. Segregated Ports............................................................................................................. 225
Figure 99. Actual coloured view example ......................................................................................... 227
Figure 100. PDH to Radio configuration dialog................................................................................. 228

8/876 3DB 18793 AAAA Issue 1 List of Figures
Figure 101. Completed PDH to Radio cross-connection .................................................................. 229
Figure 102. Radio to Radio configuration dialog............................................................................... 229
Figure 103. Completed Radio to Radio cross-connection ................................................................ 230
Figure 104. Radio/MPT-ACC to Ethernet configuration dialog (ranges) ........................................... 231
Figure 105. Radio/MPT-ACC to Ethernet configuration dialog (values)............................................ 231
Figure 106. Completed Radio/MPT-ACC to Ethernet cross-connection ........................................... 232
Figure 107. PDH to Ethernet configuration dialog ............................................................................ 232
Figure 108. Completed PDH to Ethernet cross-connection .............................................................. 233
Figure 109. No protection ................................................................................................................. 233
Figure 110. 1+1 radio protection between NE B and C..................................................................... 234
Figure 111. 1+1 EPS protection in NE A ........................................................................................... 234
Figure 112. PDH to Radio cross-connection modification................................................................. 235
Figure 113. Modifying a Radio to Radio cross-connection................................................................ 235
Figure 114. Modifying a Radio/MPT-ACC to Ethernet cross-connection .......................................... 236
Figure 115. Modifying a PDH to Ethernet cross-connection ............................................................. 237
Figure 116. SDH to Radio configuration dialog ................................................................................. 238
Figure 117. Completed SDH to Radio cross-connection .................................................................. 238
Figure 118. Radio to Radio configuration dialog ............................................................................... 239
Figure 119. Completed Radio to Radio cross-connection................................................................. 239
Figure 120. SDH to Radio cross-connection modification ................................................................ 240
Figure 121. Modifying a Radio to Radio cross-connection ............................................................... 241
Figure 122. ASAP-Radio configuration dialog (ODU300) ................................................................. 242
Figure 123. ASAP-Radio configuration dialog (MPT-HC or MPT-MC) .............................................. 243
Figure 124. Completed ASAP-radio cross-connection ..................................................................... 243
Figure 125. Radio-radio configuration dialog .................................................................................... 244
Figure 126. Traffic Descriptor............................................................................................................ 244
Figure 127. Completed radio-radio cross-connection ....................................................................... 245
Figure 128. Radio-Ethernet configuration dialog .............................................................................. 246
Figure 129. Completed Radio-Ethernet cross-connection ................................................................ 246
Figure 130. ASAP-Ethernet configuration dialog .............................................................................. 247
Figure 131. Completed ASAP-Ethernet cross-connection................................................................ 248
Figure 132. ASAP-radio cross-connection modification.................................................................... 249
Figure 133. Modifying a Radio-Radio cross-connection ................................................................... 249
Figure 134. Modifying a Radio-Ethernet cross-connection ............................................................... 250
Figure 135. Modifying an ASAP-Ethernet cross-connection............................................................. 250
Figure 136. Radio LAG to Ethernet LAG configuration dialog .......................................................... 251
Figure 137. Completed Radio LAG to Ethernet LAG cross-connection............................................ 252
Figure 138. Radio LAG to Radio LAG configuration dialog .............................................................. 252
Figure 139. Completed Radio LAG to Radio LAG cross-connection ................................................ 253
Figure 140. Ethernet LAG to Radio LAG cross-connection modification .......................................... 254
Figure 141. Modifying a Radio to Radio cross-connection ............................................................... 255
Figure 142. Auxiliary Cross Connections menu................................................................................ 257
Figure 143. New AUX Cross Connection.......................................................................................... 257
Figure 144. Delete an AUX Cross Connection ................................................................................. 258
Figure 145. Traffic Description View ................................................................................................. 259
Figure 146. Login window ................................................................................................................. 261
Figure 147. Login Failed ................................................................................................................... 261
Figure 148. Profiles Management..................................................................................................... 262
Figure 149. Create User ................................................................................................................... 263
Figure 150. Delete user confirmation................................................................................................ 264
Figure 151. Confirm Administrator Password to Delete a User ........................................................ 264
Figure 152. Change Password of User by Admin ............................................................................. 265
Figure 153. Change User Password................................................................................................. 265
Figure 154. Summary block diagram ................................................................................................ 314

Figure 155. 1+0 block diagram (PDH unit) (without Core-E protection)............................................ 316
Figure 156. 1+0 block diagram (PDH unit) (with Core-E protection)................................................. 316
Figure 157. 1+1 block diagram (PDH units) (without Core-E protection).......................................... 317
Figure 158. 1+1 block diagram (PDH units) (with Core-E protection)............................................... 317
Figure 159. 1+0 block diagram (SDH unit) (without Core protection) ............................................... 318
Figure 160. 1+0 block diagram (SDH unit) (with Core protection) .................................................... 318
Figure 161. 1+1 block diagram (SDH unit) (without Core protection) ............................................... 319
Figure 162. 1+1 block diagram (SDH unit) (with Core protection) .................................................... 319
Figure 163. 1+0 block diagram (Radio unit) (without Core-E protection).......................................... 320
Figure 164. 1+0 block diagram (Radio unit) (with Core-E protection)............................................... 321
Figure 165. 1+1 FD block diagram (Radio units) (without Core-E protection) .................................. 321
Figure 166. 1+1 FD block diagram (Radio units) (with Core-E protection) ....................................... 322
Figure 167. 1+1 Hot Standby block diagram (Radio units) (without Core-E protection) ................... 322
Figure 168. 1+1 Hot Standby block diagram (Radio units) (with Core-E protection) ........................ 323
Figure 169. 1+0 block diagram (MPT-ACC unit) (without Core-E protection) ................................... 324
Figure 170. 1+0 block diagram (MPT-ACC unit) (with Core-E protection) ........................................ 324
Figure 171. 1+1 FD block diagram (MPT-ACC units) (without Core-E protection) ........................... 325
Figure 172. 1+1 FD block diagram (MPT-ACC units) (with Core-E protection) ................................ 325
Figure 173. 1+1 Hot Standby block diagram (MPT-ACC units) (without Core-E protection)............. 326
Figure 174. 1+1 Hot Standby block diagram (MPT-ACC units) (with Core-E protection).................. 326
Figure 175. 1+0 block diagram (MPT-ACC unit) (without Core protection)....................................... 327
Figure 176. 1+0 block diagram (MPT-ACC unit) (with Core protection)............................................ 327
Figure 177. 1+1 Hot Standby block diagram (MPT-ACC units) (without Core protection) ................ 328
Figure 178. 1+1 Hot Standby block diagram (MPT-ACC units) (with Core protection) ..................... 328
Figure 179. Panel 1 (Committed software) ....................................................................................... 337
Figure 180. Panel 2 (Stand by software)........................................................................................... 338
Figure 181. Available ODUs ............................................................................................................. 341
Figure 182. Equipment View (starting from scratch) with MSS-8...................................................... 342
Figure 183. Expected Equipment Type Configuration ...................................................................... 344
Figure 184. Core-E unit configuration ............................................................................................... 345
Figure 185. MPT Access settings ..................................................................................................... 345
Figure 186. STM-1 unit configuration................................................................................................ 346
Figure 187. Protection Example........................................................................................................ 347
Figure 188. How to configure the protection ..................................................................................... 348
Figure 189. Protected configuration with MPT-HC............................................................................ 349
Figure 190. Protection configuration with STM-1 units ..................................................................... 349
Figure 191. Protection scheme screen ............................................................................................. 352
Figure 192. 1+1 PDH unit block diagram .......................................................................................... 352
Figure 193. 1+1 SDH unit block diagram .......................................................................................... 353
Figure 194. 1+1 FD Radio unit block diagram (ODU300) ................................................................. 353
Figure 195. 1+1 HSB Radio unit block diagram (ODU300) .............................................................. 354
Figure 196. 1+1 FD Radio unit block diagram (MPT-HC) ................................................................. 354
Figure 197. 1+1 HSB Radio unit block diagram (MPT-HC)............................................................... 355
Figure 198. 1+1 HSB Radio unit block diagram (MPT-MC) .............................................................. 355
Figure 199. Synchronization Settings view ....................................................................................... 362
Figure 200. SSM Summary Table ..................................................................................................... 365
Figure 201. Cross-Connections View ............................................................................................... 366
Figure 202. Node timing.................................................................................................................... 372
Figure 203. E1 Loopbacks ................................................................................................................ 373
Figure 204. Modem unit without Adaptive Modulation settings (ODU300) ....................................... 379
Figure 205. Modem unit with Adaptive Modulation settings (ODU300) ............................................ 380
Figure 206. MPT Access unit without Adaptive Modulation settings (MPT-HC) ............................... 386
Figure 207. MPT Access unit with Adaptive Modulation settings (MPT-HC) .................................... 387
Figure 208. MPT Access unit without Adaptive Modulation settings (MPT-MC) ............................... 393

Figure 209. MPT Access unit with Adaptive Modulation settings (MPT-MC) .................................... 394
Figure 210. Loopback with ODU300................................................................................................. 403
Figure 211. Loopback with MPT-HC and MPT-MC ........................................................................... 403
Figure 212. Power Source ................................................................................................................ 405
Figure 213. ASAP E1 Layer view...................................................................................................... 407
Figure 214. ASAP IMA Layer view.................................................................................................... 408
Figure 215. IMA Link Monitoring ....................................................................................................... 409
Figure 216. IMA Group Monitoring.................................................................................................... 409
Figure 217. ATM Interface type......................................................................................................... 410
Figure 218. ASAP ATM Layer view................................................................................................... 411
Figure 219. VP Layer Configuration.................................................................................................. 411
Figure 220. Ingress Traffic Description ............................................................................................. 412
Figure 221. VC Layer Configuration ................................................................................................. 414
Figure 222. ASAP ATM PW Layer view ............................................................................................ 416
Figure 223. Core-E Main view .......................................................................................................... 418
Figure 224. Core-E Main view (with optical SFP Ethernet port#5) ................................................... 419
Figure 225. Settings tab-panel .......................................................................................................... 429
Figure 226. Input External Point View............................................................................................... 430
Figure 227. Output External Points View .......................................................................................... 431
Figure 228. WT Performance Monitoring Suite palette ..................................................................... 432
Figure 229. Export: Save .................................................................................................................. 434
Figure 230. Exported files ................................................................................................................. 434
Figure 231. Print ............................................................................................................................... 435
Figure 232. Types of PM................................................................................................................... 436
Figure 233. Selection tree and start button ....................................................................................... 437
Figure 234. Example of PM counters display ................................................................................... 438
Figure 235. How start and stop the PM ............................................................................................ 438
Figure 236. Offline: archive name ..................................................................................................... 439
Figure 237. Saving the current NE status ......................................................................................... 439
Figure 238. Offline: current status saving ......................................................................................... 439
Figure 239. Offline Mode: select the NE ........................................................................................... 439
Figure 240. Ethernet Aggregate Tx................................................................................................... 441
Figure 241. Port 1 Aggregate Rx ..................................................................................................... 442
Figure 242. Customized View Builder ............................................................................................... 443
Figure 243. Overview........................................................................................................................ 444
Figure 244. Bird’s Eye View .............................................................................................................. 444
Figure 245. MPT ACC unit statistics ................................................................................................. 445
Figure 246. Configurations of the MPTACC...................................................................................... 446
Figure 247. Ethernet Aggregate Per Queue (Queue #01) ................................................................ 447
Figure 248. Aggr.Tx and Queues Custom view ................................................................................ 448
Figure 249. Overview (Modem unit).................................................................................................. 449
Figure 250. Bird’s Eye View - MPT Access unit (Default Counters) ................................................. 449
Figure 251. Bird’s Eye View (Elaborated Counters).......................................................................... 450
Figure 252. Radio sections ............................................................................................................... 451
Figure 253. Radio PMs ..................................................................................................................... 452
Figure 254. Radio PMs: Hop Ch 1 counters ..................................................................................... 453
Figure 255. Radio: Customized View Builder ................................................................................... 454
Figure 256. Manage Thresholds: display.......................................................................................... 455
Figure 257. Manage Threshold: create............................................................................................. 456
Figure 258. Manage Thresholds: threshold 2 creation ..................................................................... 456
Figure 259. P32E1DS1 Incoming (15 Min) ....................................................................................... 459
Figure 260. Manage Thresholds ....................................................................................................... 461
Figure 261. Overview........................................................................................................................ 463
Figure 262. Bird’s Eye View .............................................................................................................. 463

Figure 263. IMA Group and IMA Link statistics................................................................................. 464
Figure 264. Custom View.................................................................................................................. 465
Figure 265. ATM Interface Statistics ................................................................................................. 466
Figure 266. Logical VPs Statistics Monitoring ................................................................................... 467
Figure 267. 802.1D VLAN management........................................................................................... 469
Figure 268. 802.1Q VLAN management (default VLAN only) .......................................................... 470
Figure 269. VLAN Table Management.............................................................................................. 471
Figure 270. 802.1Q VLAN management........................................................................................... 472
Figure 271. 802.1Q VLAN management (with LAGs)....................................................................... 473
Figure 272. NEtO main view: initial screen ....................................................................................... 474
Figure 273. NEtO main view: reduced screen .................................................................................. 475
Figure 274. NEtO NE Configuration View: NE Information ............................................................... 475
Figure 275. NEtO NE Configuration View: NE Description ............................................................... 476
Figure 276. NEtO NE Configuration View: Command Buttons ......................................................... 476
Figure 277. Main View: Status & Alarms........................................................................................... 477
Figure 278. NEtO List Management ................................................................................................. 479
Figure 279. Fixing the Rack to Floor (1) ........................................................................................... 484
Figure 280. Fixing the Rack to Floor (2) ........................................................................................... 485
Figure 281. Floor file drilling template............................................................................................... 486
Figure 282. Example of securing rack assembly to computer floor .................................................. 487
Figure 283. Laborack ........................................................................................................................ 488
Figure 284. MSS-8 Subrack.............................................................................................................. 489
Figure 285. MSS-4 Subrack.............................................................................................................. 489
Figure 286. Fix the subrack with screws........................................................................................... 490
Figure 287. Subrack grounding point (bracket on the right side) ...................................................... 490
Figure 288. Mechanical Support (Two brackets) .............................................................................. 491
Figure 289. Installation kit to fix the mechanical support .................................................................. 491
Figure 290. MSS 8 Fixed on wall mounting ...................................................................................... 492
Figure 291. Top Rack Unit (T.R.U.) ................................................................................................... 492
Figure 292. Top Rack Unit - Front/Rear ............................................................................................ 492
Figure 293. Top Rack Unit - Fixed to rack......................................................................................... 492
Figure 294. TRU Connections .......................................................................................................... 494
Figure 295. TRU Grounding position on Laborack ........................................................................... 494
Figure 296. ETSI Rack - Ground connection .................................................................................... 495
Figure 297. Laborack - Ground connection ...................................................................................... 495
Figure 298. 2W2C Connector and Cable (3DB18271AAXX)............................................................ 495
Figure 299. Battery Access Card on subrack ................................................................................... 496
Figure 300. ODU (with the internal Lightning Surge Suppressor)..................................................... 497
Figure 301. ODU and Mounting Collar.............................................................................................. 498
Figure 302. Andrew Pole Mount and ODU Mounting Collar ............................................................. 499
Figure 303. RFS Pole Mount and Mounting Collar ........................................................................... 499
Figure 304. Precision Pole Mounting and ODU Mounting Collar...................................................... 499
Figure 305. Andrew ODU Collar and Polarization Rotator................................................................ 500
Figure 306. RFS Rotator ................................................................................................................... 501
Figure 307. ODU orientation for Vertical or Horizontal Polarization .................................................. 501
Figure 308. Remote Mount: front view.............................................................................................. 503
Figure 309. Remote Mount: rear view............................................................................................... 503
Figure 310. Remote Mount with an ODU installed: front view .......................................................... 504
Figure 311. Remote Mount with an ODU installed: rear view ........................................................... 504
Figure 312. Remote Mount with an ODU installed and flexible waveguide ...................................... 505
Figure 313. Remote Mount with the 1+1 coupler installed................................................................ 505
Figure 314. Remote Mount with the 1+1 coupler and one ODU installed......................................... 506
Figure 315. Coupler fitted to Antenna ............................................................................................... 511

Figure 316. Coupler Installation with ODUs
(NB: The external ligthning suppressors are no more needed) ........................................................ 511
Figure 317. Coupler Installation with ODUs: Rear View
(NB: The external ligthning suppressors are no more needed) ........................................................ 512
Figure 318. Locations for Cable Grounds ......................................................................................... 515
Figure 319. Views of MPT-HC with embedded diplexer (11-38 GHz) ............................................... 519
Figure 320. Views of MPT-HC with embedded diplexer (6 GHz) ...................................................... 520
Figure 321. Views of MPT-HC with external diplexer (7 GHz and 8 GHz) ........................................ 520
Figure 322. Views of MPT-HC with embedded diplexer (11-38 GHz) ............................................... 522
Figure 323. Views of MPT-HC with external diplexer (7 GHz and 8 GHz) ........................................ 523
Figure 324. Views of MPT-HC with embedded diplexer (6 GHz) ...................................................... 524
Figure 325. Composition of MPT-HC with external diplexer ............................................................. 525
Figure 326. MPT-HC TRANSCEIVER and BRANCHING boxes coupling surfaces ......................... 526
Figure 327. 6-7-8 GHz MPT-HC BRANCHING box mistake-proofing............................................... 526
Figure 328. Label affixed on the MPT-HC and MPT-HC TRANSCEIVER box.................................. 527
Figure 329. Label affixed inside the MPT-HC BRANCHING box ...................................................... 528
Figure 330. MPT-HC RF coupler views (Bands 6-7-8 GHz) ............................................................. 531
Figure 331. MPT-HC RF coupler view (Bands from 11 to 38 GHz)................................................... 532
Figure 332. Example of integrated antenna Pole Mounting
(with antenna and nose adapter) ...................................................................................................... 533
Figure 333. "Pole Mounting for Remote ODU" Installation kit (3DB10137AAXX)............................ 534
Figure 334. Example of antenna polarization change (“1+0” MPT-HC integrated antenna) ............. 535
Figure 335. Putting silicone grease on O-ring before MPT-HC insertion .......................................... 536
Figure 336. MPT-HC 1+0 installation for integrated antenna (11-38 GHz) ....................................... 536
Figure 337. MPT-HC 1+0 installation for integrated antenna (6-7-8 GHz: vertical polarization) ....... 537
Figure 338. MPT-HC 1+0 installation for integrated antenna (6-7-8 GHz: horizontal polarization) ... 537
Figure 339. "Pole Mounting for Remote ODU" installation................................................................ 538
Figure 340. Putting silicone grease on O-ring before MPT-HC insertion .......................................... 538
Figure 341. MPT-HC 1+0 installation for not integrated antenna (11-38 GHz with pole mounting
P/N 3DB 10137 AAAB) ..................................................................................................................... 539
Figure 342. MPT-HC 1+0 installation for not integrated antenna (6-7-8 GHz with pole mounting
P/N 3DB10137AAXX) ....................................................................................................................... 539
Figure 343. Coupler Polarization Change (11-38 GHz) - 1st Step and 2nd step .............................. 540
Figure 344. Coupler Polarization Change (11-38 GHz) - 1st Step execution................................... 540
Figure 345. Coupler Polarization Change (11-38 GHz) - 2nd Step execution ................................. 541
Figure 346. Coupler Polarization Change (11-38 GHz) - Screws fixing ............................................ 541
Figure 347. Putting silicone grease on O-ring before RF coupler insertion (11-38 GHz).................. 542
Figure 348. Installing the RF coupler to the radio support (11-38 GHz)............................................ 542
Figure 349. Putting silicone grease on RF coupler’s O-ring before MPT-HC insertion (11-38 GHz) 543
Figure 350. Installing the MPT-HC 1+1 on the RF coupler (11-38 GHz)........................................... 543
Figure 351. Views of MPT-HC 1+1 integrated antenna after installation (11-38 GHz) ...................... 544
Figure 352. Coupler Polarization Change (6-7-8 GHz) ..................................................................... 545
Figure 353. Installing the RF coupler to the radio support (6-7-8 GHz) ............................................ 547
Figure 354. Putting silicone grease on O-ring before MPT-HC insertion (6-7-8 GHz) ...................... 547
Figure 355. Installing the MPT-HC 1+1 on the RF coupler (6-7-8 GHz) ........................................... 548
Figure 357. Putting silicone grease on O-ring before RF coupler insertion ...................................... 549
Figure 358. 11-38 GHz RF coupler installation (with pole mounting P/N 3DB 10137 AAXX) ........... 550
Figure 359. Putting silicone grease on RF coupler’s O-ring before MPT-HC insertion (11-38 GHz) 550
Figure 360. Installation of MPT-HC 1+1 (11-38 GHz) ....................................................................... 551
Figure 363. 6-7-8 GHz RF coupler installation (with pole mounting P/N 3DB 10137 AAAB)............ 553
Figure 364. Putting silicone grease on O-ring before MPT-HC insertion (6-7-8 GHz) ...................... 553

Figure 365. Installing the MPT-HC 1+1 on the RF coupler (7-8 GHz) .............................................. 554
Figure 366. MPT-HC 1+1 installed on the RF coupler (6-7-8 GHz) .................................................. 554
Figure 367. Locations for Cable Grounds ......................................................................................... 575
Figure 368. Views of MPT-HC V2 with embedded diplexer (6 GHz and 11-38 GHz) ....................... 580
Figure 369. RPS module................................................................................................................... 582
Figure 370. XPIC + RPS module ...................................................................................................... 582
Figure 371. External module installed............................................................................................... 583
Figure 372. Correct screw position ................................................................................................... 583
Figure 373. Views of MPT-HC V2 with embedded diplexer (6 GHz and 11-38 GHz) ....................... 585
Figure 374. Views of MPT-HC V2 with external diplexer (7 GHz and 8 GHz)................................... 586
Figure 375. Label affixed on the MPT-HC V2 and MPT-HC V2 TRANSCEIVER box ....................... 587
Figure 376. Label affixed inside the MPT-HC V2 BRANCHING box................................................. 588
Figure 377. Q-XCO to Q-XCO Fiber cord ......................................................................................... 590
Figure 378. RPS Q-XCO to Q-XCO optical jumper .......................................................................... 591
Figure 379. Views of MPT-MC with embedded diplexer (6 and 11-38 GHz)..................................... 593
Figure 380. Views of MPT-MC with external diplexer (7 GHz and 8 GHz)........................................ 594
Figure 381. Views of MPT-MC with embedded diplexer (6 and 11-38 GHz)..................................... 595
Figure 382. Views of MPT-MC with external diplexer (7 GHz and 8 GHz)........................................ 595
Figure 383. Composition of MPT-MC with external diplexer ............................................................. 596
Figure 384. MPT-MC TRANSCEIVER and BRANCHING boxes coupling surfaces ......................... 597
Figure 385. 7-8 GHz MPT-MC BRANCHING box mistake-proofing ................................................. 598
Figure 386. Label affixed on the MPT-MC and MPT-MC TRANSCEIVER box ................................. 599
Figure 387. Label affixed inside the MPT-MC BRANCHING box...................................................... 600
Figure 388. Example of antenna polarization change (“1+0” MPT-MC integrated antenna)............. 603
Figure 389. Putting silicone grease on O-ring before MPT-MC insertion.......................................... 604
Figure 390. MPT-MC 1+0 installation for integrated antenna (6 GHz and 11-38 GHz)..................... 604
Figure 391. MPT-MC 1+0 installation for integrated antenna (7-8 GHz: vertical polarization) .......... 605
Figure 392. MPT-MC 1+0 installation for integrated antenna (7-8 GHz: horizontal polarization)...... 605
Figure 394. Putting silicone grease on O-ring before MPT-MC insertion.......................................... 606
Figure 395. MPT-MC 1+0 installation for not integrated antenna (with pole mounting
P/N 3DB 10137 AAAB) ..................................................................................................................... 607
Figure 396. Coupler Polarization Change (6 GHz and 11-38 GHz) - 1st Step and 2nd step ............ 608
Figure 397. Coupler Polarization Change (6 GHz and 11-38 GHz) - 1st Step execution ................ 608
Figure 398. Coupler Polarization Change (6 GHz and 11-38 GHz) - 2nd Step execution ............... 609
Figure 399. Coupler Polarization Change (6 GHz and 11-38 GHz) - Screws fixing.......................... 609
Figure 400. Putting silicone grease on O-ring before RF coupler insertion (6 GHz and 11-38 GHz) 610
Figure 401. Installing the RF coupler to the radio support (6 GHz and 11-38 GHz) ......................... 610
Figure 402. Putting silicone grease on RF coupler’s O-ring before MPT-MC insertion (6 GHz and 11-38
GHz).................................................................................................................................................. 611
Figure 403. Installing the MAIN MPT-MC 1+1 on the RF coupler (6 GHz and 11-38 GHz) .............. 611
Figure 404. Installing the PROTECTION MPT-MC 1+1 on the RF coupler (6 GHz and 11-38 GHz) 612
Figure 405. Coupler Polarization Change (7-8 GHz) ........................................................................ 613
Figure 406. Installing the RF coupler to the radio support (7-8 GHz) ............................................... 615
Figure 407. Putting silicone grease on O-ring before MPT-MC insertion (7-8 GHz) ......................... 616
Figure 408. Installing the MPT-MC 1+1 on the RF coupler (7-8 GHz) .............................................. 616
Figure 411. 6 GHz and 11-38 GHz RF coupler installation (with pole mounting P/N 3DB 10137 AAXX)
618
Figure 412. Putting silicone grease on RF coupler’s O-ring before MPT-MC insertion (6 GHz and 11-38
GHz).................................................................................................................................................. 618
Figure 413. Installation of MPT-MC 1+1 (6 GHz and 11-38 GHz)..................................................... 619

Figure 416. 7-8 GHz RF coupler installation (with pole mounting P/N 3DB 10137 AAAB) ............... 621
Figure 417. Putting silicone grease on O-ring before MPT-MC insertion (7-8 GHz) ......................... 621
Figure 418. MPT-MC 1+1 installed on the RF coupler (7-8 GHz) ..................................................... 622
Figure 419. Plug kit R2CT................................................................................................................. 623
Figure 420. Plug kit R2CT items ....................................................................................................... 623
Figure 421. SCSI 68 male connector................................................................................................ 632
Figure 422. Protection Panel 32E1 SCSI 68 - 1.0/2.3 75 ohm (Front/Rear) (3DB16104AAAA) ....... 640
Figure 423. Protection Panel RJ45 120 ohm (Front/Rear) (1AF15245ABAA) ................................. 640
Figure 424. Protection Panel 32E1 SCSI 68 - 1.6/5.6 75 ohm (Front) (1AF15243AAAA) ................ 640
Figure 425. Protection Panel 32E1 BNC 75 ohm (Front) (1AF15244AAAA) .................................... 640
Figure 426. Connector support 1.6/5.6 75 ohm Panel 1U (3CC08061AAAA) .................................. 640
Figure 427. Connector support BNC 75 ohm Panel 1U (3CC08061ABAA)...................................... 640
Figure 428. Support 19 Inch modules 120 ohm Panel 3U (3CC07810AAAA).................................. 641
Figure 429. E1 Protection SCSI 68/Sub-D 37 (Front/Rear) (3DB16102AAAA) ................................ 641
Figure 430. Core-E Card................................................................................................................... 641
Figure 431. Modem Card (to inteface ODU300) ............................................................................... 641
Figure 432. MPT Access Card (to interface MPT-HC) ...................................................................... 642
Figure 433. 32xE1 PDH Access Card............................................................................................... 642
Figure 434. 16xE1 ATM ASAP Card ................................................................................................. 642
Figure 435. AUX Peripheral Card ..................................................................................................... 642
Figure 436. STM-1 Access Card....................................................................................................... 642
Figure 437. Installation subrack and 4 cord N/QMA Kit .................................................................... 644
Figure 438. Installation Card ............................................................................................................. 644
Figure 439. Installation Accessory .................................................................................................... 644
Figure 440. Connection Cables ........................................................................................................ 645
Figure 441. Repeater 2x1+0 32E1 (1 PBA PDH) towards customer DDF 120 Ohms 3U................. 646
Figure 442. Repeater 2x1+0 32E1 (1 PBA PDH) towards customer DDF 120 Ohms 3U................. 646
Figure 443. Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 120 Ohms 3U.................... 647
Figure 445. Repeater 2x1+0 32E1 (1 PBA PDH) towards 2xinternal DDF 75 Ohms BNC 2x1U with cords
3CC52134AAAA (1 SCSI68 to 2 DB37) ........................................................................................... 648
3CC52134AAAA (1 SCSI68 to 2 DB37) ........................................................................................... 648
3CC52134AAAA (1 SCSI68 to 2 DB37) ........................................................................................... 649
3CC52164AAAA (2 SCSI68 to 2 DB37) ........................................................................................... 649
3CC52164AAAA (2 SCSI68 to 2 DB37) ........................................................................................... 650
Figure 450. Repeater 2x1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms ...................... 651
Figure 453. Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 75 Ohms 1.6/5.6 2U.......... 653
Figure 454. Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 75 Ohms 1.6/5.6 2U.......... 653
Figure 455. Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U ............ 654
Figure 456. Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U ............ 654
Figure 460. Terminal 1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms ........................... 657
Figure 461. Terminal 1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms ........................... 657
Figure 462. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms BNC 3U .................. 658
Figure 463. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms BNC 3U .................. 658

Figure 464. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U......................... 659
Figure 465. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U......................... 659
Figure 466. Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms 1.0/2.3 1U
660
660
Figure 468. Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U
661
661
Figure 470. Terminal 1+1 32E1 Full protected with 2 cords 3CC52157AAAA (2 PBA PDH) towards internal
DDF 120 Ohms 3U ........................................................................................................................... 662
Figure 471. Terminal 1+1 32E1 Full protected with 2 cords 3CC52157AAAA (2 PBA PDH) towards internal
DDF 120 Ohms 3U ........................................................................................................................... 662
Figure 472. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards customer DDF 120 Ohms. 663
Figure 474. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 75 Ohms 1.0/2.3 1U
664
Figure 475. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 75 Ohms 1.0/2.3 1U
664
Figure 476. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 120 Ohms 3U 665
Figure 477. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 120 Ohms 3U 665
Figure 478. Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2xinternal DDF 75 Ohms 1.0/2.3 1U
666
666
667
Figure 481. Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2xinternal DDF 120 Ohms 3U
668
668
669
Figure 486. MPT-HC Access peripheral unit electrical connections ................................................. 671
Figure 487. MPT-HC Access peripheral unit optical connections ..................................................... 671
Figure 488. 2xE1 SFP and EoSDH SFP........................................................................................... 672
Figure 489. STM-1 units ................................................................................................................... 672
Figure 490. DTE-DCE Interface........................................................................................................ 677
Figure 491. Alarm Polarity ................................................................................................................ 678
Figure 492. Polarity of the alarm....................................................................................................... 679
Figure 493. MPT/AWY Service Cord ................................................................................................ 682
Figure 494. Checking Feedhead Flange with a Spirit level............................................................... 685
Figure 495. Indicative head-on signal pattern for a parabolic antenna ............................................. 687
Figure 496. Example Tracking Path Signals ..................................................................................... 688
Figure 497. Example Tracking Path Signals on the First Side Lobe................................................. 688
Figure 498. TCO Convergence (MPR Tools) .................................................................................... 693
Figure 499. TCO Convergence (MPR Tools) .................................................................................... 711
Figure 500. MSS-4/MSS-8................................................................................................................ 712
Figure 501. TCO Main Menu ............................................................................................................ 712
Figure 502. Provisioning Tool Connectivity ....................................................................................... 713
Figure 503. Provisioning Tool Connectivity ....................................................................................... 713

Figure 504. Provisioning Tool Screen (off-line working).................................................................... 714
Figure 505. Provisioning Tool Screen (direct connection to the NE)................................................. 714
Figure 506. Clear Database and Restart NE .................................................................................... 715
Figure 507. Configuration Options Screen........................................................................................ 716
Figure 508. Core-E Configuration (Sheet 1 of 2) .............................................................................. 717
Figure 509. Core-E Configuration (Sheet 2 of 2) .............................................................................. 718
Figure 510. E1 Configuration ............................................................................................................ 719
Figure 511. STM-1 Configuration ...................................................................................................... 720
Figure 512. Modem Provisioning (without Adaptive Modulation)...................................................... 721
Figure 513. Modem Provisioning (with Adaptive Modulation) ........................................................... 722
Figure 514. MPT Access configuration (1+0).................................................................................... 723
Figure 515. MPT-Access Provisioning (without Adaptive Modulation).............................................. 724
Figure 516. MPT-Access Provisioning (with Adaptive Modulation)................................................... 725
Figure 517. MPT Access configuration (protection enabling: 1+1) ................................................... 726
Figure 518. MPT-Access Provisioning (without Adaptive Modulation) (1+1) .................................... 727
Figure 519. MPT-Access Provisioning (with Adaptive Modulation) (1+1) ......................................... 728
Figure 520. Synchronization Configuration (Master) ........................................................................ 729
Figure 521. Synchronization Configuration (Slave) .......................................................................... 730
Figure 522. Cross Connections Configuration .................................................................................. 731
Figure 523. Segregated Port Configuration ...................................................................................... 732
Figure 524. 802.1D management ..................................................................................................... 733
Figure 525. 802.1Q management ..................................................................................................... 734
Figure 526. VLAN Management ....................................................................................................... 735
Figure 527. Port VLan configuration ................................................................................................. 736
Figure 528. Network Configuration ................................................................................................... 737
Figure 529. Trusted Managers screen .............................................................................................. 738
Figure 530. Typical Report Panel...................................................................................................... 739
Figure 531. Network Element Overview ........................................................................................... 740
Figure 532. How to Login.................................................................................................................. 741
Figure 533. Provisioning sequence................................................................................................... 743
Figure 534. Enable SFP optical plug-in ............................................................................................ 744
Figure 535. Enable Spare Core-E Card ............................................................................................ 745
Figure 536. Enabling E1 Access Card .............................................................................................. 746
Figure 537. Enabling E1 Access Card on the same row (to implement protected configuration) ..... 747
Figure 538. Enabling E1 Access Card protection ............................................................................. 748
Figure 539. Enabling STM-1 Access Card........................................................................................ 749
Figure 540. Enabling SFP................................................................................................................. 749
Figure 541. Enabling STM-1 Access Card on the same row (to implement protected configuration) 750
Figure 542. Enabling STM-1 Access Card protection....................................................................... 751
Figure 543. Enabling Modem Card ................................................................................................... 752
Figure 544. Enabling Modem Card on the same row (to implement protected configuration) .......... 753
Figure 545. Enabling Modem Card protection .................................................................................. 754
Figure 546. Enabling MPT Access Card ........................................................................................... 755
Figure 547. Enabling one port in the MPT Access card.................................................................... 755
Figure 548. Enabling MPT Access Card - 1...................................................................................... 756
Figure 549. Enabling one port in the MPT Access card - 1 .............................................................. 756
Figure 550. Enabling Protection configuration with MPT-HC/MPT-MC............................................. 757
Figure 551. Enabling ASAP Card ..................................................................................................... 758
Figure 552. Enabling AUX Card........................................................................................................ 759
Figure 553. Enabling Fan Unit .......................................................................................................... 760
Figure 554. Core-E Card Provisioning (Ethernet ports 1-4) .............................................................. 761
Figure 555. Core-E Card Provisioning (Ethernet port 5)................................................................... 762
Figure 556. PDH Access Card Provisioning (TDM2TDM) ................................................................ 763
Figure 557. PDH Access Card Provisioning (TDM2ETH) ................................................................. 764

Figure 558. PDH Access Card Details .............................................................................................. 765
Figure 559. SDH Access Card Provisioning (SDH2SDH)................................................................. 766
Figure 560. Modem Card Provisioning, Presetting Mode (Sheet 1 of 2) .......................................... 768
Figure 561. Modem Card Provisioning, Presetting Mode (Sheet 2 of 2) .......................................... 769
Figure 562. Modem Card Provisioning, Adaptive Modulation Mode (Sheet 1 of 3) .......................... 770
Figure 565. Power Source configuration........................................................................................... 773
Figure 566. MPT Access Card Provisioning, Presetting Mode (Sheet 1 of 2) .................................. 774
Figure 567. MPT Access Card Provisioning, Presetting Mode (Sheet 2 of 2) .................................. 775
Figure 568. MPT Access Card Provisioning, Adaptive Modulation Mode (Sheet 1 of 2) .................. 776
Figure 569. MPT Access Card Provisioning, Adaptive Modulation Mode (Sheet 2 of 2) .................. 777
Figure 570. ASAP Card Provisioning................................................................................................ 778
Figure 571. AUX Card Provisioning .................................................................................................. 779
Figure 572. Provisioning Master with E1/T1 port as Primary Source ............................................... 780
Figure 573. Provisioning NTP protocol ............................................................................................. 781
Figure 574. NE Time Provisioning .................................................................................................... 782
Figure 575. Auxiliary Cross Connections menu................................................................................ 784
Figure 576. System Setting............................................................................................................... 785
Figure 577. LAG creation.................................................................................................................. 786
Figure 578. Local Configuration Provisioning ................................................................................... 787
Figure 579. TMN Ethernet Port Configuration Provisioning .............................................................. 788
Figure 580. Ethernet Port 4 Configuration Provisioning.................................................................... 789
Figure 581. TMN In-band Configuration Provisioning....................................................................... 790
Figure 582. IP Static Routing Provisioning........................................................................................ 791
Figure 583. OSPF Static Routing Provisioning ................................................................................. 792
Figure 584. Relative positions of stations A and B ........................................................................... 831
Figure 585. Received power check................................................................................................... 838
Figure 586. Power measurements .................................................................................................... 838
Figure 587. Received power details.................................................................................................. 839
Figure 588. IF Cable loopback.......................................................................................................... 846
Figure 589. Core-facing loopback..................................................................................................... 847
Figure 590. Test bench for tributary functionality check with ODU300 ............................................. 849
Figure 591. Test bench for tributary functionality check with MPT-HC/MPT-HC V2/MPT-MC........... 850
Figure 592. Tributary alarm status monitoring .................................................................................. 851
Figure 593. Test bench for tributary functionality check with ODU300 ............................................. 852
Figure 595. Test bench for hop stability test with ODU300 ............................................................... 857
Figure 597. Test bench for hop stability test with ODU300 ............................................................... 858
Figure 599. Test bench for optional Ethernet Data Channel functionality with 1 additional PC and 1
Ethernet cable................................................................................................................................... 861
Figure 600. Test bench for optional Ethernet Data Channel functionality with 2 additional PCs ..... 862
Figure 601. Test bench for optional Ethernet Data Channel functionality with
2 Ethernet Data Analyzers ................................................................................................................ 863
Figure 602. Test bench for ATM traffic .............................................................................................. 865
Figure 603. Test bench for 64 kbit/s Service Channel functionality check ........................................ 866

LIST OF TABLES
Table 1. Radio capacity, channelling scheme and modulation (Static Modulation) ........................... 66
Table 2. Radio capacity, channelling scheme and modulation (Adaptive Modulation)...................... 66
Table 3. Radio capacity, channelling scheme and modulation (Static Modulation) ........................... 67
Table 4. Radio capacity, channelling scheme and modulation (Adaptive Modulation)...................... 69
Table 5. MSS item codes .................................................................................................................. 81
Table 6. Licence and software codes ................................................................................................ 82
Table 7. MPT-HC codes with internal diplexer .................................................................................. 98
Table 8. MPT-HC V2 codes with internal diplexer ............................................................................. 100
Table 9. MPT-MC codes with internal diplexer .................................................................................. 102
Table 10. 7 GHz MPT-MC codes with external diplexer.................................................................... 104
Table 11. 7 GHz MPT-HC codes with external diplexer .................................................................... 104
Table 12. 7 GHz MPT-HC V2 codes with external diplexer............................................................... 105
Table 13. 7 GHz MPT-HC V2 High Power codes with external diplexer ........................................... 105
Table 14. 7 GHz Branching assemblies (for MPT-HC and MPT-MC)................................................ 105
Table 15. 8 GHz MPT-MC codes with external diplexer.................................................................... 106
Table 16. 8 GHz MPT-HC codes with external diplexer .................................................................... 106
Table 17. 8 GHz MPT-HC V2 codes with external diplexer............................................................... 106
Table 18. 8 GHz MPT-HC V2 High Power codes with external diplexer ........................................... 106
Table 19. 8 GHz Branching assemblies (for MPT-HC and MPT-MC)................................................ 107
Table 20. MPT-HC optical interface (mandatory for 1+1 configuration) ............................................ 107
Table 21. MPT-HC V2 external modules ........................................................................................... 108
Table 22. MPT-HC/MPT-HC V2/MPT-MC couplers........................................................................... 108
Table 23. RSSI Table ........................................................................................................................ 125
Table 24. Waveguide Flange Data .................................................................................................... 126
Table 25. RSSI Table ........................................................................................................................ 134
Table 27. 802.1p mapping................................................................................................................. 163
Table 28. RR weights ........................................................................................................................ 164
Table 29. PW label EXP bits ............................................................................................................. 165
Table 30. Command priority list......................................................................................................... 357
Table 34. MPT-HC external interfaces ............................................................................................. 521
Table 35. RF interface...................................................................................................................... 521
Table 36. Codes, characteristics and views of RF couplers for bands from 6 to 8 GHz ................... 531
Table 37. Codes, characteristics and views of RF couplers for bands from 11 to 38 GHz................ 532
Table 38. MPT-HC Output flanges with external antenna ................................................................. 572
Table 39. 6-7-8GHz Flextwist waveguide.......................................................................................... 573
Table 40. 11-38GHz Flextwist waveguide ......................................................................................... 573
Table 41. MPT-HC V2 external interfaces ........................................................................................ 584
Table 43. MPT-MC external interfaces ............................................................................................. 594
Table 45. SCSI 68 pins FW cable colors........................................................................................... 632
Table 46. Pin Function: Tributaries 1-16 (32E1 PDH card/16E1 ASAP card) ................................... 673
Table 47. Pin Function: Tributaries 17-32 (32E1 PDH card) ............................................................. 674
Table 48. Service channel 1 pin functions......................................................................................... 676
Table 49. Service channel 2 pin functions......................................................................................... 676
Table 50. Housekeeping connector pin function ............................................................................... 678
Table 51. Alarm Matrix ...................................................................................................................... 796
Table 52. Modem Card and ODU300 Alarm Matrix .......................................................................... 802

List of Tables 3DB 18793 AAAA Issue 1 19/876
Table 53. MPT Access Peripheral Card and MPT-HC/MPT-HC V2 Alarm Matrix ............................. 805
Table 54. MPT Access Peripheral Card and MPT-MC Alarm Matrix................................................. 810
Table 55. TMN Network Troubleshooting ........................................................................................ 816
Table 56. Test and commissioning instruments ................................................................................ 830

20/876 3DB 18793 AAAA Issue 1 List of Tables
PREFACE
Preliminary Information
WARRANTY
Any warranty must be referred exclusively to the terms of the contract of sale of the equipment to
which this handbook refers to.
Alcatel–Lucent 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–Lucent will not
be liable for errors contained herein or for damages, whether direct, indirect, consequential, inci-
dental, or special, in connection with the furnishing, performance, or use of this material.
INFORMATION
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–Lucent.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of Alcatel–Lucent and must not be copied,
reproduced or disclosed to a third party without written consent.
SAFETY RECOMMENDATIONS
The safety recommendations here below must be considered to avoid injuries on persons and/or
damage to the equipment:
1) Service Personnel
Installation and service must be carried out by authorized persons having appropriate technical
training and experience necessary to be aware of hazardous operations during installation and
service, so as to prevent any personal injury or danger to other persons, as well as prevent-
damaging the equipment.
2) Access to the Equipment

Access to the Equipment in use must be restricted to Service Personnel only.
3) Safety Rules
Recommended safety rules are indicated in Chapter 1 from page 29.

Preface 3DB 18793 AAAA Issue 1 21/876
Local safety regulations must be used if mandatory. Safety instructions in this handbook should
be used in addition to the local safety regulations. In case of conflict between safety instructions
stated in this manual and those indicated in local regulations, mandatory local norms will pre-
vail. Should not local regulations be mandatory, then safety rules stated in this manual will pre-
vail.
SERVICE PERSONNEL SKILL
Service Personnel must have an adequate technical background on telecommunications and in par-
ticular on the equipment subject of this handbook.
An adequate background is required to properly install, operate and maintain equipment. The fact
of merely reading this handbook is considered as not enough.
Applicability
This handbook applies to the following product–release:
PRODUCT
9500 MPR
PRODUCT RELEASE
MSS-8/MSS-4 + ODU300/MPT-HC/MPT-HC V2/MPT-MC 3.0.0
Scope
This document aims to describe the hardware and software functionalities of the 9500 MPR-E.
This document is intended to the technicians involved in Planning, in Operation and Maintenance and in
Commissioning of the 9500 MPR-E.
History
ISSUE DATE DESCRIPTIONS
01 December 2010

22/876 3DB 18793 AAAA Issue 1 Preface
Change notes
The features of Rel. 3.0.0 have been inserted.
Handbook Structure
This handbook has been edited according to the Alcatel-Lucent standardized “drawing-up guides" com-
plying with such suggestion.
This handbook is divided into the main topics described in the table of contents:
PREFACE It contains general information as preliminary information, hand-

book scope, history. Furthermore, it describes the handbook struc-
ture and the customer documentation.
SAFETY This section includes all the safety instructions.
PRODUCT INFORMATION This section provides the equipment description (at system, MSS
AND PLANNING and ODU levels), introduces the basic information regarding the
HW architecture, and gives its technical characteristics.
NE MANAGEMENT BY This section gives the description and use of the SW tools available
SOFTWARE APPLICATIONS for the NE management.
INSTALLATION This section provides whole information regarding Equipment hard-

ware installation.
Moreover, it contains the whole operative information on:
– provisioning of equipment items (P/Ns, equipping rules)
– their physical position in the system
– unit assembly and front panel drawings, with the description
on the access point usage (connectors, visual indicators, but-
tons).
This section provides also the whole operative instructions for the
preparation of the WebEML for the Line–Up and Commissioning of
the two NEs making up the radio link.
PROVISIONING This section gives all the instructions to provision (to configure) the
NE.
MAINTENANCE AND This section contains the whole logical and operative information for
TROUBLE-CLEARING the equipment maintenance and system upgrade.
LINE-UP AND This section provides all the instructions for the line-up and com-
COMMISSIONING missioning of the NE.
ABBREVIATIONS The abbreviation list is supplied.
CUSTOMER DOCUMENTA- It contains info regarding customer opinions collection about this
TION FEEDBACK documentation.

General on Alcatel-Lucent Customer Documentation
This paragraph describes in general the Alcatel–Lucent Customer Documentation system, details the
association between the product levels and the associated documentation, and explains Customer Doc-
umentation characteristics as well as the policies for its delivery and updating.
Customer–Independent Standard Customer Documentation
a) Definition
Standard Customer Documentation, referred to hereafter, must be always meant as plant–indepen-
dent and is always independent of any Customization.
Plant–dependent and/or Customized documentation, if envisaged by the contract, is subjected to
commercial criteria as far as contents, formats and supply conditions are concerned.
N.B. Plant–dependent and Customized documentation is not described here.
b) Aims of standard Customer Documentation

Standard system, hardware and software documentation is meant to give the Customer personnel
the possibility and the information necessary for installing, commissioning, operating, and maintain-
ing the equipment according to Alcatel–Lucent Laboratory design and Installation Dept. choices. In
particular:
• the contents of the chapters associated to the software applications focus on the explanation
of the man–machine interface and of the operating procedures allowed by it;
• maintenance is described down to faulty PCB location and replacement.
N.B. No supply to Customers of design documentation (like PCB hardware design andproduction
documents and files, software source programs, programming tools, etc.) is envisaged.
Product levels and associated Customer Documentation
a) Products
A “product” is defined by the network hierarchical level where it can be inserted and by the whole
of performances and services that it is meant for.
E.g. 9500 MPR-E is a product.
b) Product-releases
A ”product” evolves through successive “product–releases”, which are the real products marketed
for their delivery at a certain ”product–release” availability date. A certain ”product–release” performs
more functionalities than the previous one.
E.g. Rel.1.0 and Rel.2.0 are two successive “product–releases” of the same “product”.
A “product–release” comprehends a set of hardware components and at least one “Software Pack-
age” (SWP); as a whole, they identify the possible network applications and the equipment perfor-
mances that the specific “product–release” has been designed, engineered, and marketed for.
c) Configurations and Network Elements

In some cases, a “product–release” includes different possible “configurations” which are distin-
guished from one another by different “Network Element” (NE) types and, from the management
point of view, by different SWPs.
d) SWP releases, versions, and CD–ROMs

• Each SWP is distributed by means of a specific SWP CD–ROM.
• A SWP is identified by its “Denomination”, “P/N” (Part Number) and “CS” (Change Status), that
are printed on the CD–ROM’s label:
– the first and second digits of the “Denomination” (e.g. 2.0) correspond to the “HW product–
release” number;
– the third digit of the of the “Denomination” (e.g. 2.0.2) identifies the Version Level of the
SWP.

• A SWP with new Version Level, providing main features in addition to those of the previous Ver-
sion Level SWP, is distributed by means of a SWP CD–ROM having new “Denomination”,“P/
N” (Part Number), and “CS” restarting from 01
• A SWP patch version, if any, is created to correct SW bugs, and/or to add minor features, andis
distributed by means of a SWP CD–ROM, that can be identified:
– by the same “P/N” of the former CD–ROM, but with an incremented “CS” number
(e.g.CS=02 instead of previous CS=01)
– or by a new “P/N”, and “CS” restarting from 01.
Handbook Updating
The handbooks associated to the "product-release" are listed in “History“ on page 22.
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 22;
• 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-
Lucent 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-Lucent 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-Lucent 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 Safety, EMC, EMF, ESD Norms and
Equipment Labelling
This chapter describes the equipment labelling and the norms mandatory or suggested that must be con-
sidered to avoid injuries on persons and/or damage to the equipment.
This chapter is organized as follows:
– Declaration of conformity to CE marking and Countries List
– Specific label for MPR-E equipment
– Applicable standards and recommendations
– Safety Rules
– Electromagnetic Compatibility (EMC norms)
– Equipment protection against electrostatic discharges
– Cautions to avoid equipment damage

Safety, EMC, EMF, ESD Norms and Equipment Label- 3DB 18793 AAAA Issue 1 29/876
1.1 Declaration of conformity to CE marking and Countries List
Indication of the countries where the equipment is intended to be used: Austria (AT) - Belgium (BE)
- Bulgaria (BG) - Switzerland/Liechtenstein (CH) - Cyprus (CY) - Czech Republic (CZ) - Germany (DE)
- Denmark (DK) - Estonia (EE) - Finland (FI) - France (FR) - Greece (GR) - Hungary (HU) – Italy (IT) -
Ireland (IE) - Iceland (IS) - Lithuania (LT) – Luxembourg (LU) - Latvia (LV) - Malta (MT) - Netherlands (NL)
- Norway (NO) –Poland (PL) – Portugal (PT) - Romania (RO) – Spain (SP) - Sweden (SE) - Slovenia (SI)
- Slovak Republic (SK) -United Kingdom (UK)
Indication of the intended use of the equipment: Point to Point PDH/Ethernet Transport radio Link

30/876 3DB 18793 AAAA Issue 1 Safety, EMC, EMF, ESD Norms and Equipment Label-
1.2 Specific label for MPR-E equipment
Field Field Name Note
A Alcatel-Lucent Logo
B Equipment acronym
C Power Supply Version MSS-8 See NB 1
Power Supply Version MSS-4 See NB 2
D Feeding to continuous current
E European Community Logo
F Not harmonized frequency logo
G WEEE Logo
H Electrostatic Device Logo
NB1: – 40.5V / - 57.6V ; 10.2A / 7.2A

NB2: – 40.5V / - 57.6V ; 7.2A / 5.0A

1.3 Applicable standards and recommendations
1999/5/CE of 09 March 1999
Safety: EN 60950, EN 60825-1, EN 60825-2, EN 50385
EMC: EN 301 489-1, EN 301 489-4
Spectrum: EN 302 217-2-2
1.4 Safety Rules
1.4.1 General Rules

Before carrying out any installation, turn-on, tests or operation and maintenance operations, read carefully
the related sections of this Manual, in particular:
– Hardware Installation
– Commissioning
– Maintenance and Upgrade
Observe safety rules
– When equipment is operating nobody is allowed to have access inside on the equipment parts which
are protected with Cover Plate Shields removable with tools.
– In case of absolute need to have access inside, on the equipment parts when it is operating this is
allowed exclusively to service personnel, where for Service Personnel or Technical assistance is
meant :
• "personnel which has adequate Technical Knowledge and experience necessary to be aware
of the danger that he might find in carrying out an operation and of the necessary measure-
ments to reduce danger to minimum for him and for others".
• The Service Personnel can only replace the faulty units with spare parts.
• The Service Personnel is not allowed to repair: hence the access to the parts no specified is
not permitted.
• The keys and/or the tools used to open doors, hinged covers to remove parts which give access
to compartments in which are present high dangerous voltages must belong exclusively to the
service personnel.
– For the eventual cleaning of the external parts of the equipment, absolutely do not use any inflam-
mable substance or substances which in some way may alter the markings, inscriptions ect.
– It is recommended to use a slightly wet cleaning cloth.
The Safety Rules stated in the handbook describe the operations and/or precautions to observe to safe-
guard service personnel during the working phases and to guarantee equipment safety, i.e., not exposing
persons, animals, things to the risk of being injured/damaged.
Whenever the safety protection features have been impaired, REMOVE POWER.

To cut off power proceed to switch off the power supply units as well as cut off power station upstream
(rack or station distribution frame).
The safety rules described in this handbook are distinguished by the following symbol and statement:
1.4.2 Labels Indicating Danger, Forbiddance, Command

It is of utmost importance to follow the instructions printed on the labels affixed to the units and assemblies.
– dangerous electrical voltages

– harmful optical signals
– risk of explosion
– moving mechanical parts
– heat-radiating Mechanical Parts
– microwave radiations
Pay attention to the information stated in the following, and proceed as instructed.
Note
The symbols presented in following paragraphs are all the possible symbols that could be present on Alca-
tel-Lucent equipment, but are not all necessarily present on the equipment this handbook refers to.
Dangerous Electrical Voltages
[1] Labeling
The following warning label is affixed next to dangerous voltages (>42.4 Vp; >60 Vdc).
If it is a Class 1 equipment connected to mains, then the label associated to it will state that the equip-
ment will have to be grounded before connecting it to the power supply voltage, e.g.:

[2] Safety instructions
DANGER! Possibility of personal injury:
Carefully observe the specific procedures for installation / turn-up and commissioning / maintenance
of equipment parts where D.C. power is present, described in the relevant installation / turn-up and
commissioning / maintenance documents and the following general rules:
• Personal injury can be caused by -48VDC. Avoid touching powered terminals with any exposed
part of your body.
• Short circuiting, low-voltage, low-impedance, DC circuits can cause severe arcing that can
result in burns and/or eye damage. Remove rings, watches, and other metal jewelry before
working with primary circuits. Exercise caution to avoid shorting power input terminals.
Risks of Explosions: labeling and safety instructions
This risk is present when batteries are used, and it is signaled by the following label:
Therefore, slits or apertures are made to let air circulate freely and allow dangerous gasses to down flow
(battery-emitted hydrogen). A 417-IEC-5641 Norm. compliant label is affixed next to it indicating that the
openings must not be covered up.
Moving Mechanical Parts: labeling and safety instructions
The following warning label is affixed next to fans or other moving mechanical parts:
Before carrying out any maintenance operation see that all the moving mechanical parts have been
stopped.

Equipment connection to earth
Terminals for equipment connection to earth , to be done according to international safety standards, are
pointed out by the suitable symbol:
The position of earth connection terminals is specified in the Hardware Installation section.
Heat-radiating Mechanical Parts: labeling and safety instructions
The presence of heat-radiating mechanical parts is indicated by the following warning label in compliancy
with IEC 417 Norm, Fig.5041:
DANGER! Possibility of personal injury:
Carefully observe the specific procedures for installation / turn-up and commissioning / maintenance of
equipment parts where heat-radiating mechanical parts are present, described in the relevant installation
/ turn-up and commissioning / maintenance documents and the following general rule:
Personal injury can be caused by heat. Avoid touching powered terminals with any exposed part of your
body.
Optical safety
The equipment contains Class 1 laser component according to IEC 60825-1 (par. 5).
CLASS 1 LASER PRODUCT
The laser source is placed in the optional SFP plug-in, which has to be installed in the Core-E unit. The
laser source is placed in the left side of the SFP plug-in.
According to the IEC 60825-1 the explanatory label is not sticked on the equipment due to the lack of
space.

Microwave radiations (EMF norms)
Equipment emitting RF power (Reminder from site preparation procedure):
The site must be compliant with ICNIRP guidelines or local regulation if more restrictive.
The following rules should be strictly applied by Customer:
– Non authorized persons should not enter the compliance boundaries, if any, for the general public.
– Compliance RF boundaries, if any, related to Electro Magnetic Field exposure must be marked.
– Workers should be allowed to switch-off the power if they have to operate inside compliance bound-
aries.
– Assure good cable connection.
– Install the antenna as high as possible from floor or area with public access ( if possible the cylinder
delimitating the compliance boundaries, if any, or the cylinder corresponding to the transmission
area directly in front of antenna with the same diameter as the antenna, more than 2 meters high).
– Install the antenna as far as possible from other existing equipment emitting RF power.
Anyway remind that someone standing in front of the 9500 MPR-E antenna may cause traffic shutdown.
Place the relevant stickers:
EMF emission warning sign
On the site when applicable (when people can cross the compliance boundaries and/or the transmission
area of the antenna, i.e. roof top installation)
– Warning label "Do not stand on the antenna axis"
On the mast (front side)
– EMF emission warning sign (Yellow and black) to be placed at bottom of antenna, visible by some-
one moving in front of the antenna (roof top installation)
On the antenna (rear side)
– EMF emission warning sign, placed on the antenna.

1.5 Electromagnetic Compatibility (EMC norms)
The equipment's EMC norms depend on the type of installation being carried out (cable termination,
grounding etc.,) and on the operating conditions (equipment, setting options of the electrical/electronic
units, presence of dummy covers, etc.).
Before carrying out any installation, turn-on, tests & operation and maintenance operations, read carefully
the related sections of this Manual, in particular:
– Hardware Installation
– Maintenance and Upgrade
The norms set down to guarantee EMC compatibility, are distinguished inside this Manual by the symbol
and term:
ATTENTION EMC Norms
[1] EMC General Norms - Installation
• All connections (towards the external source of the equipment) made with shielded cables use
only cables and connectors suggested in this Manual or in the relevant Plant Documentation,
or those specified in the Customer's "Installation Norms" (or similar documents)
• Shielded cables must be suitably terminated
• Install filters outside the equipment as required
• Ground connect the equipment utilizing a conductor with proper diameter and impedance
• Mount shields (if utilized), previously positioned during the installation phase, but not before
having cleaned and degrease it.
• Before inserting the shielded unit proceed to clean and degrease all peripheral surfaces (con-
tact springs and connection points, etc.)
• Screw fasten the units to the subrack.
• To correctly install EMC compatible equipment follow the instructions given.
[2] EMC General Norms - Turn-on, Tests & Operation
• Preset the electrical units as required to guarantee EMC compatibility
• Check that the equipment is operating with all the shields properly positioned (dummy covers,
ESD connector protections, etc.)
• To properly use EMC compatible equipment observe the information given
[3] EMC General Norms - Maintenance
• Before inserting the shielded unit, which will replace the faulty or modified unit, proceed to clean
and degrease all peripheral surfaces (contact springs and connection points, etc.)
• Clean the dummy covers of the spare units as well.
• Screw fasten the units to the subrack.

1.6 Equipment protection against electrostatic discharges
Before removing the ESD protections from the monitors, connectors etc., observe the precautionary mea-
sures stated. Make sure that the ESD protections have been replaced and after having terminated the
maintenance and monitoring operations.
Most electronic devices are sensitive to electrostatic discharges, to this concern the following warning
labels have been affixed:
Observe the precautionary measures stated when having to touch the electronic parts during the instal-
lation/maintenance phases.
Workers are supplied with anti static protection devices consisting of:
– an elasticized band worn around the wrist
– a coiled cord connected to the elasticized band and to the stud on the subrack
1.7 Cautions to avoid equipment damage

a. Anti static protection device kit
Whenever is necessary to handle spare parts and cards out of their own box, this kit (Illustration
below) must be always warn and its termination must be connected to a grounded structure, to avoid
the possible damage of the electronic devices for electrostatic discharges.
Anti static protection device kit
b. Screw fixing
In normal operation conditions, all screws (for unit box closing, cable fixing, etc.) must be always
tightened to avoid item detachment and to ensure the equipment EMI-EMC performance.
The screw tightening torque must be:
2.8 kg x cm (0.28 Newton x m) ±10 %

2.4317 in lb (0.2026 ft lb) ±10 %
Exceeding this value may result in screw breaking.
c. MSS-ODU cable disconnection / connection
Before to disconnect or connect the MSS-ODU cable (at MSS or ODU side) switch off the corre-
sponding MSS Unit.

2 Product information and planning
– Purpose and Function (par. 2.1 on page 42)
• Innovative solutions (par. 2.1.1 on page 42)
• Description (par. 2.1.2 on page 45)
• MSS Purpose, Function and Description (par. 2.1.3 on page 46)
• Stacking configuration (par. 2.1.4 on page 49)
• ODU300 (par. 2.1.5 on page 51)
• MPT-HC (par. 2.1.6 on page 52)
• MPT-MC (par. 2.1.7 on page 53)
• MPT-HC V2 (par. 2.1.8 on page 54)
• Power Extractor (par. 2.1.9 on page 55)
• MSS to Outdoor Unit interconnections (par. 2.1.10 on page 56)
– MSS to ODU300 interconnection (par. 2.1.10.1 on page 56)
– MSS to MPT-HC interconnection (par. 2.1.10.2 on page 57)
– MSS to MPT-HC V2 interconnection (par. 2.1.10.3 on page 61)
– MSS to MPT-MC interconnection (par. 2.1.10.4 on page 64)
– How to connect the MPT-HC/MPT-HC V2 to the battery (par. 2.1.10.5 on page 65)
• Antennas (par. 2.1.11 on page 65)
– Radio capacity, channelling and modulation (par. 2.2 on page 66)

• ODU300 (par. 2.2.1 on page 66)
• MPT-HC/MPT-HC V2/MPT-MC (par. 2.2.2 on page 67)
– Standard Features (par. 2.3 on page 70)
– Radio Configurations (par. 2.4 on page 71)
– Typical System Configurations (par. 2.5 on page 71)
– Environmental and Electrical Characteristics (par. 2.6 on page 75)

• System Parameters (par. 2.6.1 on page 75)
• ODU300 (par. 2.6.2 on page 77)
– 6 to 15 GHz (par. 2.6.2.1 on page 77)
– 18 to 38 GHz (par. 2.6.2.2 on page 77)
• MPT-HC/MPT-HC V2 (par. 2.6.3 on page 78)
– 6 to 13 GHz (par. 2.6.3.1 on page 78)
– 15 to 38 GHz (par. 2.6.3.2 on page 78)
– 6 to 13 GHz (par. 2.6.4.1 on page 80)
– 15 to 38 GHz (par. 2.6.4.2 on page 80)
• Radio performances (par. 2.6.5 on page 80)
– Parts Lists (par. 2.7 on page 81)

• MSS (par. 2.7.1 on page 81)
• ODU300 (with internal lightning surge suppressor) (par. 2.7.2 on page 84)
• MPT-HC with internal diplexer (par. 2.7.3 on page 98)
• MPT-HC V2 with internal diplexer (par. 2.7.4 on page 100)
• MPT-MC with internal diplexer (par. 2.7.5 on page 102)

Product information and planning 3DB 18793 AAAA Issue 1 39/876
• Part lists of MPT-HC/MPT-HC V2/MPT-MC with external diplexer (par. 2.7.6 on page 104)
– MPT-HC optical interface (mandatory for 1+1 configuration) (par. 2.7.7 on page 107)
– MPT-HC V2 external modules (mandatory for 1+0/1+1 configurations) (par. 2.7.8 on page
108)
– MPT-HC/MPT-HC V2/MPT-MC couplers (par. 2.7.9 on page 108)
– Functional description (par. 2.8 on page 109)

• MSS (Indoor Unit) (par. 2.8.1 on page 109)
– Power distribution (par. 2.8.1.1 on page 110)
– Core-E unit (par. 2.8.1.2 on page 111)
– 32xE1 Local Access unit (par. 2.8.1.3 on page 113)
– 2xSTM-1 Local Access unit (par. 2.8.1.4 on page 114)
– ASAP unit (par. 2.8.1.5 on page 115)
– Modem unit (par. 2.8.1.6 on page 118)
– MPT Access Unit (with PFoE) (par. 2.8.1.7 on page 120)
• DC Extractor (par. 2.8.2 on page 122)
• ODU300 (par. 2.8.3 on page 123)
– ODU block diagram (par. 2.8.3.1 on page 124)
– RSSI Monitoring Point (par. 2.8.3.2 on page 125)
– Waveguide Flange Data (par. 2.8.3.3 on page 125)
– ODU Coupler (par. 2.8.3.4 on page 126)
• MPT-HC (par. 2.8.4 on page 127)
– MPT-HC block diagram (par. 2.8.4.1 on page 129)
– RSSI Monitoring Point (par. 2.8.4.2 on page 134)
– Waveguide Flange Data (par. 2.8.4.3 on page 134)
– MPT-HC Coupler (par. 2.8.4.4 on page 134)
• MPT-HC V2 (par. 2.8.5 on page 135)
– MPT-MC Coupler (par. 2.8.6.1 on page 137)
• Protection schemes (par. 2.8.7 on page 138)
– Protection schemes with ODU300 (par. 2.8.7.1 on page 138)
– Protection schemes with MPT-HC/MPT-HC V2 (par. 2.8.7.2 on page 139)
– Protection schemes with MPT-MC (par. 2.8.7.3 on page 141)
– Core-E protection (par. 2.8.7.4 on page 142)
• Radio Transmission Features with ODU300 (par. 2.8.8 on page 144)
– Frequency Agility (par. 2.8.8.1 on page 144)
– Automatic Transmit Power Control (ATPC) (par. 2.8.8.2 on page 144)
– Transmitted power control: RTPC function (par. 2.8.8.3 on page 144)
– Power Monitoring (par. 2.8.8.4 on page 144)
– Adaptive Equalization (par. 2.8.8.5 on page 144)
– Link identifier (par. 2.8.8.6 on page 145)
– Loopbacks with ODU300 (par. 2.8.8.7 on page 145)
• Radio Transmission Features with MPT-HC/MPT-HC V2/MPT-MC (par. 2.8.9 on page 146)
– Frequency Agility (par. 2.8.9.1 on page 146)
– Automatic Transmit Power Control (ATPC) (par. 2.8.9.2 on page 146)
– Transmitted power control: RTPC function (par. 2.8.9.3 on page 146)
– Power Monitoring (par. 2.8.9.4 on page 146)
– Adaptive Equalization (par. 2.8.9.5 on page 146)
– Link identifier (par. 2.8.9.6 on page 147)
– Loopbacks with MPT-HC/MPT-HC V2/MPT-MC (par. 2.8.9.7 on page 147)
– Loopback activation (par. 2.8.9.8 on page 148)
– Loopback life time (par. 2.8.9.9 on page 148)
• TMN interfaces (par. 2.8.10 on page 149)
• Admission control in Adaptive Modulation (only with ODU300) (par. 2.8.11 on page 149)

40/876 3DB 18793 AAAA Issue 1 Product information and planning
– What does “Admission Control” mean? (par. 2.8.11.1 on page 149)
– Radio capacity in case of adaptive modulation (par. 2.8.11.2 on page 149)
– Adaptive modulation and admission control enabled (par. 2.8.11.3 on page 149)
– Adaptive modulation and admission control disabled (par. 2.8.11.4 on page 151)
• Managed Services and profiles (par. 2.8.12 on page 154)
• TDM and Ethernet traffic management (par. 2.8.13 on page 156)
– TDM2TDM (par. 2.8.13.1 on page 158)
– TDM2Eth (par. 2.8.13.2 on page 159)
– ETH2ETH (par. 2.8.13.4 on page 160)
• ATM Traffic Management (par. 2.8.14 on page 161)
– ATM Traffic Management on ASAP - PW Label Exp bits and scheduling type (par. 2.8.14.1
on page 165)
– ATM Traffic Management on Modem card - Block biagram for ATM PW Flow policer (par.
2.8.14.2 on page 165)
– Support of ATMoMPLS Protocl Stack (with or without MPLS Tunnel Label (par. 2.8.14.3
on page 165)
• Ethernet Traffic Management (par. 2.8.15 on page 168)
– Bridge type change (par. 2.8.15.1 on page 168)
– Reserved Multicast Addresses (par. 2.8.15.2 on page 168)
• LAG (Link Aggregation Group) (par. 2.8.16 on page 170)
– LAG overview (par. 2.8.16.1 on page 170)
• Quality Of Services (QoS) (par. 2.8.17 on page 172)
– QoS in the Core-E unit (par. 2.8.17.1 on page 173)
– QoS in the Modem unit (par. 2.8.17.2 on page 175)
– QoS in the MPT-HC/MPT-MC (par. 2.8.17.3 on page 177)
• Cross-connections (par. 2.8.18 on page 178)
– E1 Cross-connections (par. 2.8.18.1 on page 178)
– STM-1 Cross-connections (par. 2.8.18.2 on page 178)
– Radio-Radio Cross-connections (par. 2.8.18.3 on page 178)
– Ethernet Cross-connections (par. 2.8.18.4 on page 179)
– ATM PW cross-connections (par. 2.8.18.5 on page 179)
– Port Segregation (par. 2.8.18.6 on page 185)
• Synchronization for PDH/SDH/DATA (par. 2.8.19 on page 190)
– Synchronization overview (par. 2.8.19.1 on page 190)
– Synchronization Sources and protection policy (par. 2.8.19.2 on page 192)
– Synchronization Sources assignment (par. 2.8.19.3 on page 193)
– Synchronization sources assignment rules (par. 2.8.19.4 on page 195)
– Allowed synchronization sources assignment (par. 2.8.19.5 on page 195)
• Synchronization for E1 ports with ASAP unit (par. 2.8.20 on page 197)
• Synchronization distribution from 9500 MPR to 9400 AWY (par. 2.8.21 on page 197)
• Synchronization connection in Stacking configuration with Core protection (par. 2.8.22 on page
198)

2.1 Purpose and Function
The 9500 Microwave Packet Radio (MPR) is a microwave digital radio that supports PDH, SDH and
packet data (Ethernet) for migrating to IP. The 9500 MPR-E provides a generic, modular IP platform for
multiple network applications (including 2G/3G/HSDPA/WiMAX backhauling to Metro Ethernet areas) to
accommodate broadband services. The 9500 MPR-E radio family supports low, medium, and high
capacity applications using European data rates, frequencies, channel plans, and tributary interfaces.
– TDM/PDH Data Rates: E1
– SDH Data Rates: STM-1
– ATM Data Rates: E1
– Ethernet Data Speed: 10, 100, 1000 Mb/s
– RF Frequency Range: 6 to 38 GHz
2.1.1 Innovative solutions

The 9500 MPR-E innovative solutions mainly are:
[1] Multiservice aggregation layer: the capacity to use Ethernet as a common transmission layer to
transport any kind of traffic, independently by the type of interface. Ethernet becomes the conver-
gence layer.
[2] Service awareness: traffic handling and quality management, queuing traffic according to the type
of service assigned, independently by the type of interface
[3] Packet node: no service aggregation limits with all traffic aggregated in packets, in term of: capacity,
type of service requirements and type of interface
[4] Service-driven adaptive modulation: fully exploit the air bandwidth in its entirety by changing mod-
ulation scheme according to the propagation availability and allocate transport capacity, discrimi-
nating traffic by different services, only possible in a packet-based environment.
[1] Multiservice aggregation layer
Access network Packet Backhaul network

Any TDM/Ethernet interfaces Ethernet aggregation layer
nxE1 9500 MPR
GSM Aggregated traffic
2G over Ethernet
ISAM,
WiMAX
Ethernet
3G HSDPA
Voice on R99
nxE1
Single technology throughout the network: Ethernet as convergence layer
Figure 1. Multiservice Aggregation Layer

9500 MPR-E aggregates and carries over a COMMON PACKET LAYER: TDM 2G, 3G and IP/Ethernet.
This allows sharing of common packet transmission infrastructures, regardless of the nature of carried
traffic.
Due to the nature of Ethernet, each service can be discriminated based on several parameters like quality
of service.
Mapping different access technologies over Ethernet is achieved by standardized protocols like circuit
emulation and pseudo-wire.
[2] Service awareness
Figure 2. Service Awareness
Service awareness means the ability to discriminate the different traffic types carried over the converged
Ethernet stream. The traffic flow can be composed by E1, STM-1, ATM and/or IP/Eth, coming from
different sources, and therefore having different requirements.
For instance ATM traffic from a 3G base stations can carry voice (high priority, real time service) and data
(lower priority and possibly non real time with high variability load, such as internet browsing, music
download or video streaming).
Service awareness is what allows identifying the traffic types, and in case of the non real time variable
bit rate one, optimize the band with overbooking of the radio scarce resource.

[3] Packet node
Address new data services in the best way: packet natively
Figure 3. Packet Node
9500 MPR-E offers a SINGLE PACKET MATRIX able to switch, aggregate and handle any of the possible
incoming traffic types with virtually no capacity limits (up to 10 GBps).
[4] Service-driven adaptive modulation
Figure 4. Service-driven Packet Adaptive Modulation
Traffic with high priority will always have bandwidth available, like voice (deterministic approach).
Broadband traffic is discriminated by QoS dynamically, with modulation scheme changes driven by
propagation conditions.

2.1.2 Description
The 9500 MPR-E consists of a Microwave Service Switch (MSS) and Outdoor Unit (ODU).
Figure 5. Naming Convention
For the interconnections between the MSS and the Outdoor Units refer to paragraph 2.1.10 on page 56.

2.1.3 MSS Purpose, Function and Description
The MSS shelf houses the indoor cards. It is available in two versions:
– MSS-8
– MSS-4
The MSS provides cross-connection, port aggregation, switching, and equipment management.
The MSS shelf consists of card cage and backplane in which mounts access and radio peripheral and
Core-E control plug-in cards (see Figure 6. and Figure 7.).
Main Core-E Spare Core-E

module module
Transport Transport
module module
Transport Transport FANS

module module module
Transport Transport module

module or AUX peripheral
module
Figure 6. MSS-8 shelf
Main Core-E Spare Core-E

module module
FANS
Transport Transport module module
module or AUX peripheral
module
Figure 7. MSS-4 shelf
The Core-E modules provide six Ethernet user interfaces (4 electrical interfaces as default + 2 electrical/
optical interfaces available with optional SFP. Note: for the available SFPs refer to par. 2.8.1.2), the local
WebEML interface and the local debug interface.
The Main Core-E and the Spare Core-E modules have a different role.
The Main Core-E is always provided (Core-E in 1+0 configuration). It performs key node management and
control functions, and provides various dc rails from the -48 Vdc input. It also incorporates a plug-in flash
card, which holds node configuration and license data.
The Main Core-E also includes the cross-connection matrix, which implements all the cross-connections
between the Transport modules, between the Ethernet user ports and between the Ethernet user ports
and the Transport modules. The matrix is a standard Ethernet switch, based on VLAN, assigned by the
WebEML.
To the optional SFP can be connected also the MPT-HC.

The Spare Core-E is an optional unit to provide aggregated traffic protection and control platform
protection.
The following Transport modules are supported:
– TDM 32E1/DS1 local access module: provides the external interfaces for up to 32xE1 tributaries,
manages the encapsulation/reconstruction of PDH data to/from standard Ethernet packets and
sends/receives standard Ethernet packets to/from both Core-E modules; it contains the switch for
the EPS Core-E protection and the DC/DC converter unit.
– STM-1 local access module: provides the external interfaces for up to 2 electrical or optical STM-
1 signals, manages the encapsulation/reconstruction of SDH data to/from standard Ethernet packets
and sends/receives standard Ethernet packets to/from both Core-E modules; it contains the switch
for the EPS Core-E protection and the DC/DC converter unit.
– ASAP module: provides the external interfaces for up to 16xE1 tributaries carrying ATM cells,
manages the encapsulation/reconstruction of ATM cells (according to the PWE3 standard) to/from
standard Ethernet packets and sends/receives standard Ethernet packets to/from both Core-E
modules; it contains the DC/DC converter unit.
– ODU300 Access module: this module is used to interface one ODU300. It sends/receives standard
Ethernet packets to/from both Core-E modules, manages the radio frame (on Ethernet packet form)
generation/termination, the interface to/from the alternate Radio module (for RPS management), the
cable interface functions to ODU; it contains the logic for the EPS Core-E protection, the RPS logic
and the DC/DC converter unit.
For each radio direction with ODU300, one ODU300 Access module in the MSS and one associated
ODU300 has to be provisioned in case of 1+0 radio configuration. Two radio access modules and
two associated ODU300 have to be provisioned in case of 1+1 radio configurations.
– MPT Access (with PFoE) module: this module is used to interface up to two MPT-HC or the MPT-
MC. This module provides the Power Feed over Ethernet to the MPT (only one cable to carry
Ethernet traffic and power supply). The interface to the MPT-HC is a standard GbEth interface
(electrical or optical) and a power supply cable. The interface to the MPT-MC is a standard GbEth
interface (electrical). It sends/receives standard Ethernet packets to/from both Core-E modules. It
contains the logic for the EPS Core-E protection and the DC/DC converter unit.
For each radio direction with MPT, one MPT Access module in the MSS and one associated MPT
has to be provisioned in case of 1+0 radio configuration. One (or two) MPT Access modules and two
associated MPT have to be provisioned in case of 1+1 radio configurations.
According to the transport modules installed different configurations can be implemented.
The optional AUX peripheral module provides 2x64 kbit/s service channels and the housekeeping
alarms.
A simplified block diagram of the MSS is shown in Figure 8. for MSS-8 and in Figure 9. for MSS-4.

Core-E MODULE
Flash
TRANSPORT PSU Controller
MODULE RAM
TRANSPORT
MODULE
TRANSPORT
MODULE
1 GbEth
TRANSPORT
MODULE
TRANSPORT ETHERNET
MODULE SWITCH
TRANSPORT
MODULE
LIU LIU
4x10/100/1000 2 Electrical/Optical
electrical SFPs
Ethernet ports (port #5 to port #6)
(port #1 to port #4)
Figure 8. MSS-8 block diagram
Core-E MODULE
Flash
TRANSPORT PSU Controller
MODULE RAM
TRANSPORT
MODULE
1 GbEth
ETHERNET
SWITCH
LIU LIU
4x10/100/1000 2 Electrical/Optical
electrical SFPs
Ethernet ports (port #5 to port #6)
(port #1 to port #4)
Figure 9. MSS-4 block diagram

2.1.4 Stacking configuration
To manage more directions the “Stacking configuration” can be realized by installing up to 3 MSS, inter-
connected through the Ethernet ports in the Core-E module. In the example of Figure 10 are shown the
interconnected MSS.
Shelf 1
TMN In-band
Ethernet +
Synch
Shelf 2
TMN In-band
Ethernet +
Synch
Shelf 3
Figure 10. Stacking configuration with 3 MSS
For the Stacking configuration it is recommended to enable the Static Lag Criteria.
Also with the Core protection max. 3 MSS can be interconnected as shown in Figure 11.
To implement this configuration the LOS alarm on the Ethernet ports must be enabled as switching cri-
terion of the Core protection. To enable this functionality the “Ethernet LOS Criteria” feature has to be
enabled (refer to Menu System Setting in par. 3.4.4).

Shelf 1
TMN In-band
TMN In-band
Ethernet +
Ethernet +
Shelf 2
TMN In-band
TMN In-band
Ethernet +
Ethernet +
Shelf 3
Figure 11. Stacking configuration with 3 MSS with Core protection

2.1.5 ODU300
The ODU300 is a microprocessor controlled transceiver that interfaces the MSS with the antenna.
Transmitter circuits in the ODU300 consist of cable interface, local oscillator, upconverter/mixer, power
amplifier, and diplexer.
Receive circuits consist of diplexer, low-noise amplifier, local oscillator, downconverter/mixer, automatic
gain control, and cable interface.
Power is provided by -48Vdc from the MSS to the ODU300 DC-DC converter.
The ODU300 is frequency dependent.
Figure 12. ODU300

2.1.6 MPT-HC
MPT-HC is a Microwave Equipment capable of transporting the Ethernet traffic over an RF radio channel.
MPT-HC is a microprocessor controlled equipment that interfaces the MSS with the antenna.
The input interface is a standard Giga Ethernet interface (electrical or optical).
The Ethernet traffic is transmitted over the radio channel according to the configured QoS and to the
scheduler algorithms.
Transmitter circuits in the MPT-HC consist of Ethernet input interface, modulator, local oscillator, upcon-
verter/mixer, power amplifier, and diplexer.
Receiver circuits consist of diplexer, low-noise amplifier, local oscillator, downconverter/mixer, automatic
gain control, demodulator and Ethernet output interface.
The microprocessor manages the frequency, transmit power alarming, and performance monitoring.
The power is provided by -48 Vdc from the MSS to the MPT-HC DC-DC converter through a dedicated
power supply cable.
By using the Power Extractor (refer to par. 2.1.9) the MPT-HC can be connected to the MSS by using only
one cable carrying Ethernet traffic and power supply.
The MPT-HC is frequency dependent.
Figure 13. MPT-HC

2.1.7 MPT-MC
MPT-MC is similar to MPT-HC from architecture standpoint. Only differences are:
– MPT-MC is medium capacity
– MPT-MC is natively Ethernet powered through a proprietary PFoE
– MPT-MC cannot be connected in optical -> 100m length cable limitation.
Figure 14. MPT-MC
N.B. In the current release in the 1+1 configuration there is no coupling link between the two MPT-
MC, therefore:
– 1+1 FD cannot be supported
– 1+1 SD cannot be supported

2.1.8 MPT-HC V2
MPT-HC V2 is similar to MPT-HC from architecture standpoint and can be used as spare part of the MPT-
HC. The differences are:
– MPT-HC V2 can be natively Ethernet powered through a proprietary PFoE (or as alternative by using
two cables, one coaxial cable for the Power Supply and one optical cable for the Ethernet Traffic (as
MPT-HC)
– MPT-HC V2 is XPIC-ready (by the installation of a dedicated module). The XPIC connector will be
used, when this feature will be available.
Figure 15. MPT-HC V2

2.1.9 Power Extractor
The Power Extractor is an Outdoor Device, to be installed close to the MPT-HC, which receives on one
cable the “Power Feed over Ethernet” (Ethernet traffic and Power Supply), provided by the MPT Access
unit, and separates the Power Supply from the Ethernet traffic to be separately sent to the MPT-HC.
Figure 16. shows the Power Extractor.
Figure 16. Power Extractor
The Power Extractor has 3 connectors:
– DC+DATA In (PFoE from the MPT Access unit)
– DC Out (Power Supply to MPT-HC)
– Data Out (Ethernet traffic to MPT-HC)

2.1.10 MSS to Outdoor Unit interconnections
2.1.10.1 MSS to ODU300 interconnection
A single 50 ohm coaxial cable connects a ODU300 Modem unit to its ODU. The max. cable length is up
to 150 m. ODU cable, connectors and grounding kits are separatly provided.
The ODU cable carries DC power supply for the ODU and five signals:
– Tx telemetry
– Reference signal to synchronize the ODU IQ Mod/Demod oscillator
– 311 MHz IQ modulated signal from the ODU300 Radio Interface (transmit IF)
– Rx telemetry
– 126 MHz IQ modulated signals from the ODU (receive IF)
Figure 17. MSS to ODU300 interconnection

2.1.10.2 MSS to MPT-HC interconnection
The MPT-HC can be connected in 3 different ways:
– Two cables (MPT Access unit to MPT-HC) - par. 2.1.10.2.1
– One cable (MPT Access unit to MPT-HC) - par. 2.1.10.2.2
– Two cables (Core-E unit to MPT-HC) - par. 2.1.10.2.3
2.1.10.2.1 Two cables (MPT Access unit to MPT-HC)
Two cables connect an MPT-HC Access unit in the MSS to its MPT-HC (Figure 18 and Figure 19):
– One cable is a 50 ohm coaxial cable to send the power supply to the MPT-HC.
– The second cable is an Ethernet cable (optical or electrical).

The max cable length for electrical Ethernet connection is 100 m.
The max cable length for optical Ethernet connection is 450 m.
The standard delivery is up to 300 m. The cable for up to 450 m is available on demand.
The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool
(1AD160490001). The Ethernet optical cable is preassembled and available in different lengths.
Figure 18. MSS to MPT-HC interconnection


2.1.10.2.2 One cable (MPT Access unit to MPT-HC)
By using the optional DC Extractor, installed close to the MPT-HC, the interconnection between the MSS
and the MPT-HC can be made with a single electrical Ethernet cable (Figure 20) by using the Power Feed
over Ethernet (Ethernet traffic and Power Supply on the same cable). The DC Extractor then separates
the Power Supply from the Ethernet traffic, which are separately send to the MPT-HC.

2.1.10.2.3 Two cables (Core-E unit to MPT-HC)
Two cables connect the MPT:
– one optical cable connected to port#5 or port #6 of the Core-E unit
– a coaxial cable connected to the station battery to provide the power supply.
To connect the coaxial cable to the station battery refer to paragraph 2.1.10.5 on page 65.

2.1.10.3 MSS to MPT-HC V2 interconnection
The MPT-HC V2 can be connected in 3 different ways:
– One cable (MPT Access unit to MPT-HC V2) - par. 2.1.10.3.1
– Two cables (MPT Access unit to MPT-HC V2) - par. 2.1.10.3.2
– Two cables (Core-E unit to MPT-HC V2) - par. 2.1.10.3.3
2.1.10.3.1 One cable (MPT Access unit to MPT-HC V2)
One electrical Ethernet cable connects an MPT Access unit in the MSS to its MPT-HC V2 (the MPT Access
unit provides the PFoE).
The max cable length is 100 m.
(1AD160490001).
Figure 22. MSS to MPT-HC V2 interconnection

2.1.10.3.2 Two cables (MPT Access unit to MPT-HC V2)
Two cables connect an MPT Access unit in the MSS to its MPT-HC V2:
– One cable is a 50 ohm coaxial cable to send the power supply to the MPT-HC V2:
• for length lower or equal to 100 m the power cable can be CAT5E cable to send the power sup-
ply to the MPT-HC V2 . The Ethernet electrical cable is provided with connectors to be mounted
on site with the specific RJ45 tool (1AD160490001);
• for length higher than 100m, the cable is a 50 ohm coaxial cable to send the power supply to
the MPT-HC V2
Note: In case of length lower than 100m and presence in the field of 1 coaxial alredy installed
and free it is recomended to use the coax cable to minimise the installation effort.
– The second cable is an Ethernet optical cable.

The Ethernet optical cable is preassembled and available in different lengths (up to 450 m).
Note: A special cord adapter must be connected to the coaxial cable on the MPT-HC V2.

2.1.10.3.3 Two cables (Core-E unit to MPT-HC V2)
Two cables connect the MPT:
– one optical cable connected to port#5 or port #6 of the Core-E unit
– a coaxial cable connected to the station battery to provide the power supply.
To connect the coaxial cable to the station battery refer to paragraph 2.1.10.5 on page 65.

2.1.10.4 MSS to MPT-MC interconnection
One electrical Ethernet cable connects an MPT Access unit in the MSS to its MPT-MC (the MPT Access
unit provides the PFoE).
The max cable length is 100 m.
(1AD160490001).
Figure 25. MSS to MPT-MC interconnection

2.1.10.5 How to connect the MPT-HC/MPT-HC V2 to the battery
Figure 26. shows the devices used to connect a MPT directly to a battery.
From front to back:
– Coaxial cable with N connector
– Wall mount support 3CC50149AAXX (max 4 MPT)
– Lightning arrestor with its grounding cable
– Low pass filter
– Cable N to two wires ("pigtail")
Figure 26. MPT-HC/MPT-HC V2 directly connected to the battery
2.1.11 Antennas
Antennas for direct mounting an ODU are available in diameters from 0.3 m to 1.8 m, depending on the
frequency band.
A polarization rotator is included within the antenna collar, and direct-mounting equal or unequal loss
couplers are available for single antenna protected operation.
Antenna mounts are designed for use on industry-standard 114 mm OD pipe-mounts.
An ODU can also be used with standard antennas via a remote-mount kit and flexible waveguide.

2.2 Radio capacity, channelling and modulation
2.2.1 ODU300
Table 1. Radio capacity, channelling scheme and modulation (Static Modulation)
Channel FCM Mode ETSI Class # E1 Typical Ethernet
(TDM2TDM) Throughput (1518 bytes)
4 QAM 2 4 E1 9,3 Mbit/s
7 MHz 16 QAM 4 8 E1 19,9 Mbit/s
64 QAM 5 13 E1 30,5 Mbit/s
4 QAM 2 8 E1 19,9 Mbit/s
14 MHz 16 QAM 4 18 E1 41,1 Mbit/s
64 QAM 5 27 E1 62,3 Mbit/s
4 QAM 2 18 E1 41,1 Mbit/s
16 QAM 4 37 E1 83,6 Mbit/s
32 QAM 4 48 E1 107,3 Mbit/s

28 MHz
64 QAM 5 56 E1 126,1 Mbit/s
128 QAM 5 68 E1 151,7 Mbit/s
256 QAM 6 77 E1 172,0 Mbit/s
16 QAM 4 72 E1 161,0 Mbit/s
56 MHz 128 QAM 5 136 E1 304,7 Mbit/s
256 QAM 6 150 E1 335,9 Mbit/s
Table 2. Radio capacity, channelling scheme and modulation (Adaptive Modulation)

Channel ACM Mode ETSI Class # E1 (Note) Typical Ethernet
Spacing (TDM2TDM) Throughput (1518 bytes)
4 QAM 2 18 E1 41,1 Mbit/s
28 MHz 16 QAM 4 37 E1 83,6 Mbit/s
64 QAM 5 56 E1 126,1 Mbit/s
4 QAM 2 8 E1 19,9 Mbit/s
14 MHz 16 QAM 4 18 E1 41,1 Mbit/s
64 QAM 5 27 E1 62,3 Mbit/s
4 QAM 2 4 E1 9,3 Mbit/s
7 MHz 16 QAM 4 8 E1 19,9 Mbit/s
64 QAM 5 13 E1 30,5 Mbit/s

Note
The Admission Control for TDM flows (cross-connected to radio direction working in Adaptive Modulation)
can be enabled or disabled.
When the Admission Control is enabled, the check is performed taking into account the capacity of the
4 QAM modulation scheme for the relevant Channel Spacing.
When the Admission Control is disabled, the check is performed taking into account the capacity of the
highest modulation scheme for the relevant Channel Spacing (64 QAM for 4-16-64 QAM range or 16 QAM
for 4-16 QAM range).
2.2.2 MPT-HC/MPT-HC V2/MPT-MC

Table 3. Radio capacity, channelling scheme and modulation (Static Modulation)
Channel Spacing FCM ETSI # E1 # STM-1 Typical mean Ethernet
(MHz) Mode Class (TDM2TDM) (SDH2SDH) Throughput
(any length: 64-1518 bytes)
4 QAM 2 2 0 4,8 Mbit/s
16 QAM 4 4 0 9,3 Mbit/s

3.5
32 QAM 4 5 0 11,5 Mbit/s
64 QAM 5 6 0 14,3 Mbit/s
4 QAM 2 4 0 9,3 Mbit/s
16 QAM 4 9 0 20,2 Mbit/s
32 QAM 4 11 0 24,9 Mbit/s

7 64 QAM 5 13 0 30,3 Mbit/s
128 QAM 5 16 0 36,1 Mbit/s
256 QAM 6 19 0 41,3 Mbit/s

(NB3)
4 QAM 2 9 0 20,4 Mbit/s
16 QAM 4 19 0 41,6 Mbit/s
32 QAM 4 23 0 51,1 Mbit/s

14 64 QAM 5 29 0 62,8 Mbit/s
128 QAM 5 34 0 74,5 Mbit/s
256 QAM 6 41 0 87,4 Mbit/s

(NB3)

4 QAM 2 19 0 41,9 Mbit/s
4 QAM 2 (NB1) 20 0 43,8 Mbit/s
16 QAM 4 39 0 84,2 Mbit/s
16 QAM 4 (NB1) 41 0 87,9 Mbit/s

28 32 QAM 4 50 0 107,7 Mbit/s
64 QAM 5 60 0 129,0 Mbit/s
128 QAM 5 71 0 152,4 Mbit/s
256 QAM 6 85 1 180,7 Mbit/s

(NB3)
40 (NB2) 64 QAM 5 88 1 186,6 Mbit/s
128 QAM 5 104 1 220,6 Mbit/s
256 QAM 6 148 1 257,9 Mbit/s
50 (NB2) 256 QAM 6 148 1 314,4 Mbit/s
16 QAM 4 75 1 159,9 Mbit/s
16 QAM 4 (NB1) 76 1 161,9 Mbit/s
32 QAM 4 92 1 196,2 Mbit/s

56 (NB2)
64 QAM 5 119 1 252,6 Mbit/s
128 QAM 5 141 1 298,6 Mbit/s
256 QAM 6 160 2 339,8 Mbit/s
N.B.1: New ETSI mask.
N.B.2: MPT-MC does not support this Channel Spacing.
N.B.3: MPT-MC does not support this FCM mode.

Table 4. Radio capacity, channelling scheme and modulation (Adaptive Modulation)
Channel Spacing ACM Mode ETSI Modulation range Typical mean Ethernet
(MHz) Reference Class Throughput
(any length: 64-1518 bytes)
4 QAM 2 4 QAM to 64 QAM 4,8 Mbit/s

3.5

7

14
4 QAM 2 (NB2) 4 QAM to 256 QAM 43,8 Mbit/s

28
40 (NB1) 64 QAM 5 64 QAM to 128 QAM 186,6 Mbit/s

56 (NB1)
N.B.1: MPT-MC does not support this Channel Spacing.
N.B.2: New ETSI mask.

2.3 Standard Features
More radio and site scalability and flexibility for installation teams:
– Limited need for factory presetting channel frequency or bandwidth
– Interchangeable hardware units
– Supports cellular mobile networks, and microcellular network back and common carrier, private
carrier and data networks, and utility haul applications.
– 2G, 2.5G, and 3G network compatible
– Intelligent indoor nodal unit that supports up to 12 outdoor units, expandable to 36 with the stacking
configuration (with MPT)
– Flexible aggregate capacity sharing between E1, STM-1 and Ethernet
– Adaptive packet transport that improves performance for priority services
– Output power agility
– ATPC
– Adaptive Modulation
– Packet-based internal cross-connect
– E1 MEF8 encapsulation
– STM-1 encapsulation
– EoSDH feature
– ATM over PW according to RFC 4717
– Radio and Ethernet LAGs
– Electrical and optical GE interfaces
– Software-based configuration
– Multiservice Switching Capacity greater than 16 Gb/s
– No single point of failure

2.4 Radio Configurations
– 1+0
– 1+1 Hot-Standby (HSB)
• two types of coupler for ODU300:
– 3 dB/3 dB balanced coupler or 1.5 dB/6.0 dB unbalanced coupler
• two types of coupler for MPT-HC/MPT-MC:
– 3 dB/3 dB balanced coupler or 1 dB/10 dB unbalanced coupler
– 1+1 Hot-Standby Space Diversity (HSB SD) (no coupler)
– 1+1/2x(1+0) Frequency Diversity (FD) (co-polar)
– 1+1/2x(1+0) Frequency Diversity (FD) (cross-polar)
N.B. MPT-MC does not support the FD configuration.
N.B. In 1+1 configuration the 2 Outdoor Units must be of the same types.
2.5 Typical System Configurations

– PDH/ATM Over Ethernet Packet Node - Mapping of 32 E1 and 16 E1 ATM on Ethernet (Figure 27.)
– PDH/SDH/ATM and Ethernet Terminal Packet Transport 32 E1, 2xSTM-1 and 16 E1 ATM Access,
1 Radio Direction (Figure 28.)
– PDH/SDH/ATM and Ethernet Add/Drop Packed Node-Ethernet and 32 E1, 2xSTM-1 and 16 E1 ATM
Local Access, 1 Back Link, 1 Haul Link (Figure 29.)
– PDH/SDH/ATM and Ethernet Terminal Packet Node-Ethernet and 32 E1, 2xSTM-1 and 16 E1 ATM
Local Access, 2 Back Links (Figure 30.)
– PDH/SDH/ATM and Ethernet Add/Drop Packet Node-Ethernet and 32 E1, 2xSTM-1 and 16 E1 ATM
Local Access, 1 Back Link and 2 Haul Links (Figure 31.)
– PDH/SDH/ATM and Ethernet Add/Drop Packet Node-Ethernet and 32 E1, 2xSTM-1 and 16 E1 ATM
Local Access, 2 Haul Links and 2 Back Links (Figure 32.)
N.B. Radio LAG and Ethernet LAGs can be created to increase the capacity and availability.

Figure 27. PDH/ATM Over Ethernet Packet Node - Mapping of 32 E1 and
16 E1 ATM on Ethernet
Access Peripheral
2xSTM-1
Figure 28. PDH/SDH/ATM and Ethernet Terminal Packet Transport 32 E1, 2xSTM-1 and
16 E1 ATM Access, 1 Radio Direction

Access Peripheral
2xSTM-1
Figure 29. PDH/SDH/ATM and Ethernet Add/Drop Packed Node-Ethernet and 32 E1, 2xSTM-1 and
16 E1 ATM Local Access, 1 Back Link, 1 Haul Link
Access Peripheral
2xSTM-1
Figure 30. PDH/SDH/ATM and Ethernet Terminal Packet Node-Ethernet and 32 E1, 2xSTM-1 and
16 E1 ATM Local Access, 2 Back Links

Access Peripheral
2xSTM-1
16 E1 ATM Local Access, 1 Back Link and 2 Haul Links
Access Peripheral
2xSTM-1
16 E1 ATM Local Access, 2 Haul Links and 2 Back Links

2.6 Environmental and Electrical Characteristics
– System Parameters (par. 2.6.1)
– ODU300 (par. 2.6.2)
– MPT-HC/MPT-HC V2 (par. 2.6.3)
– MPT-MC (par. 2.6.4)
2.6.1 System Parameters
General with ODU300
Operating Frequency Range 6 - 38 GHz
Max Ethernet throuput from 10 up to 310 Mbit/s
Modulation Options in FCM 4 QAM, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM
Adaptive Modulation 4 QAM, 16 QAM, 64 QAM,
General with MPT-HC/MPT-HC V2
Max Ethernet throuput 340 Mbit/s
Bandwidth up to 56 MHz
Modulation Options in FCM 4 QAM, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM
Adaptive Modulation 4 QAM, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM
General with MPT-MC
Max Ethernet throuput 155 Mbit/s
Bandwidth up to 28 MHz
Modulation Options in FCM 4 QAM, 16 QAM, 32 QAM, 64 QAM, 128 QAM
Adaptive Modulation 4 QAM, 16 QAM, 32 QAM, 64 QAM, 128 QAM
Radio Path Protection Options
Non Protected, 1+0

Protected Hot Standby, 1+1
Space Diversity, 1+1
Frequency Diversity, 1+1 (with ODU300, MPT-HC/MPT-HC V2)
Radio LAG with two radio channels
MSS Power supply
Input voltage range -40.5 to -57.6 Vdc The input voltage range can be
also from -57 to -60 Vdc without
any damage, but with no guar-
anteed performance

Standards Compliance
EMC MSS-8/MSS-4 EN 301 489-1, EN 301 489-4

EN 55022 Class B)
Operation ODU300/MPT ETS 300 019, Class 4.1
Operation MSS-8/MSS-4 ETS 300 019, Class 3.2
Storage ETS 300 019, Class 1.2
Transportation ETS 300 019, Class 2.3
Safety IEC 60950-1/EN 60950-1
Radio Frequency EN 302 217 Classes 2, 4 & E5
Water Ingress ODU300/MPT IEC 60529 (IPX6)
Environmental
Operating Temperature MSS-8/MSS-4 Guaranteed -5° to +55° C
ODU300/MPT Guaranteed -33° to +55° C
Start up temperature from low ODU300 -20°C

temperature
MPT -40°C
Humidity MSS-8/MSS-4 Guaranteed 0 to 95%, non-condensing
ODU300/MPT Guaranteed 0 to 100%
Management
Protocol SNMP
Interface, electrical Ethernet 10/100/1000 Base-T (RJ45)
Local/remote Configuration and JUSM

Support Tool
Routing Protocols supported Static routing and dynamic routing (OSPF)
TMN In-band 2 interfaces
Network Management Alcatel-Lucent 1350 OMS

Alcatel-Lucent 1352 Compact
Alcatel-Lucent 5620 SAM

2.6.2 ODU300
2.6.2.1 6 to 15 GHz
L6/U6 GHz 7 GHz 8 GHz 10 GHz 11 GHz 13 GHz 15 GHz
System
Frequency Range, GHz 5.925 - 7.125 - 7.725 - 10.0 - 10.7 - 12.75 - 14.4 -
6.425 7.9 8.5 10.68 11.7 13.25 15.35
6.425 - 7.11
T-R Spacings supported MHz 252.04 340 154, 161, 119, 126, 91, 230, 490, 530 266 315, 420,
168, 196, 151.614, 143.5, 490, 644,
245 266, 350 728
311.32
Maximum Tuning Range 56 56 140 165 165 84 245

(dependent upon T-R spacing),
MHz
Antenna Interface
Waveguide Type R70 R84 R84 R100 R100 R120 R140

(WR137) (WR112) (WR112) (WR90) (WR90) (WR75) (WR62)
Flange Type UDR70 UDR84 UDR84 UDR100 UDR100 UBR120 UBR140
Mating Flange Type PDR70 or PDR84 PDR84 PDR100 PDR100 PBR120 PBR140
CDR70 or or or or or or
CDR84 CDR84 CDR100 CDR100 CDR120 CBR140
Guaranteed power 45 W
consumption
2.6.2.2 18 to 38 GHz
18 GHz 23 GHz 26 GHz 28 GHz 32 GHz 38 GHz
System
Frequency Range, GHz 17.7 - 21.2 - 24.52 - 27.5 - 31.8-33.4 37.0 -

19.7 23.632 26.483 29.5 39.46
T-R Spacings supported MHz 1010, 1008, 1008 1008 812 1260
1092.5 1200,
1232
Maximum Tuning Range (dependent upon 380 370 360 360 370 340
T-R spacing), MHz
Antenna Interface
Waveguide Type R220 R220 R220 R320 R320 R320

(WR42) (WR42) (WR42) (WR28) (WR28) (WR28)
Flange Type UBR220 UBR220 UBR220 UBR320 UBR321 UBR320
Mating Flange Type PBR220 PBR220 PBR220 PBR320 PBR321 PBR320
Guaranteed power consumption 30 W

2.6.3 MPT-HC/MPT-HC V2
2.6.3.1 6 to 13 GHz
L6 GHz U6 GHz 7 GHz 8 GHz 11 GHz 13 GHz
System
Frequency Range, GHz 5.925 - 6.425 - 7.125 - 7.725 - 10.7 - 12.75 -

6.425 7.11 7.9 8.5 11.7 13.25
T-R Spacings supported MHz 252.04 340 154, 119; 126; 490- 266
161, 151.614; 500-530
168, 208;
196, 245 213,5;
266;
294;
305;
311.32
Antenna Interface
Waveguide Type WR137 WR137 WR112 WR113 WR75 WR62
Typical power consumption (MPT-HC) 38 W
Guaranteed power consumption (MPT-HC) 40 W
Typical power consumption (MPT-HC V2) 37 W
Guaranteed power consumption (MPT-HC V2) 39 W
Typical power consumption (MPT-HC V2 with 38 W

RPS module)
Guaranteed power consumption (MPT-HC V2 40 W

with RPS module)

XPIC-RPS module)

with XPIC-RPS module)
2.6.3.2 15 to 38 GHz
15 GHz 18 GHz 23 GHz 26 GHz 38 GHz
System
Frequency Range, GHz 14.4 - 17.7 - 21.2 - 24.52 - 37.0 -

15.35 19.7 23.632 26.483 39.46
T-R Spacings supported MHz 308-315- 1008- 1008, 1008 1260

322, 420, 1010, 1050-
490, 644, 1560, 340 1200-
728 1232
Antenna Interface
Waveguide Type WR62 WR42 WR42 WR42 WR28

Typical power consumption (MPT-HC) 38 W
Guaranteed power consumption (MPT-HC) 40 W
Typical power consumption (MPT-HC V2) 37 W
Guaranteed power consumption (MPT-HC V2) 39 W

RPS module)

with RPS module)

XPIC-RPS module)

with XPIC-RPS module)

2.6.4 MPT-MC
2.6.4.1 6 to 13 GHz
L6 GHz U6 GHz 7 GHz 8 GHz 11 GHz 13 GHz
System
Frequency Range, GHz 5.925 - 6.425 - 7.125 - 7.725 - 10.7 - 12.75 -

6.425 7.11 7.9 8.5 11.7 13.25
T-R Spacings supported MHz 252.04 340 154, 161, 119; 126; 490-500- 266
168, 196, 151.614; 530
245 208;
213,5;
266; 294;
305;
311.32
Antenna Interface
Waveguide Type WR137 WR137 WR112 WR113 WR75 WR62
Typical power consumption 38 W
2.6.4.2 15 to 38 GHz
15 GHz 18 GHz 23 GHz 26 GHz 38 GHz
System
Frequency Range, GHz 14.4 - 17.7 - 21.2 - 24.52 - 37.0 -

15.35 19.7 23.632 26.483 39.46
T-R Spacings supported MHz 420-475, 1008- 1008, 1008 1260

490 1010, 1050-
1560 1200-
1232
Antenna Interface
Waveguide Type WR62 WR42 WR42 WR42 WR28
Typical power consumption 38 W
2.6.5 Radio performances
The radio performances are provided in the “Technical Description” document.

2.7 Parts Lists
2.7.1 MSS
Table 5. MSS item codes

APR Name APR Code Remarks
MSS-8 slot shelf 3DB18485AAXX
MSS-4 slot shelf 3DB18219ABXX
Core-E Card 3DB18326ABXX
Fan Card 3DB18134BAXX To be used in MSS-8
FAN1 Module 3DB18218ACXX To be used in MSS-4
STM-1 Access Card 3DB 18735 AAXX Up to 2 STM-1 signals
E1 Access Card 3DB18126ADXX Up to 32 E1 TDM stream
ASAP Card 3DB18602AAXX Up to 16 E1 streams with ATM cells
AUX peripheral card 3DB18236ABXX
Modem 300 3DB18136ACXX To interface the ODU300 to be used with

56 MHz bandwidth (no adaptive modulation)
3DB18136ADXX
Modem 300EN 3DB18538AAXX To interface the ODU300 to be used with

bandwidth up to 28 MHz (with or without
3DB18538ABXX
adaptive modulation)
MPT Access Card (with PFoE) 3DB18634ABXX To interface one or two MPT-HC or MPT-MC or
one MPT-HC and one MPT-MC
Front plate 3DB18163ABXX
SFP plug-in STM-1 L1.1 1AB194670005 To be installed in the STM-1 Access card
(option)
SFP plug-in STM-1 S1.1 1AB194670007 To be installed in the STM-1 Access card
(option)
SFP plug-in STM-1 Copper 1AB210170001 To be installed in the STM-1 Access card
(option)
SFP plug-in 1000Base-Lx 1AB187280040 To be installed in the Core-E card (option)
SFP plug-in 1000Base-Sx 1AB187280045 To be installed in the Core-E card (option)
SFP plug-in 1000Base-T 1AB359780001 To be installed in the Core-E card (option)

(Copper Transceiver)
SFP 2xE1 3DB78012AAAA To be installed in the Core-E card (option)

SFP S1.1 GE over STM-1 1AB380750003 To be installed in the Core-E card (option)
SFP 1000 Sx 1AB383760001 Optical SFP module to be installed optionally in

the Core-E card and in the MPT Access Card
Table 6. Licence and software codes

APR name APR Code License String
Flash Cards 3.0.0
MPR Memory L6TD-200 3DB18659AAAA R/6Cap040
MPR Memory M1TD-200 3DB18660AAAA R/5Cap040/1Cap080
MPR Memory M2TD-200 3DB18661AAAA R/4Cap040/2Cap080
MPR Memory M6TD-200 3DB18662AAAA R/6Cap080
MPR Memory H1TD-200 3DB18663AAAA R/5Cap040/1Cap100
MPR Memory H2TD-200 3DB18664AAAA R/4Cap040/2Cap100
MPR Memory H6TD-200 3DB18666AAAA R/6Cap100
MPR Memory V1TD-200 3DB18667AAAA R/5Cap040/1Cap150
MPR Memory V2TD-200 3DB18668AAAA R/4Cap040/2Cap150
MPR Memory V6TD-200 3DB18669AAAA R/6Cap150
MPR Memory E1TD-200 3DB18670AAAA R/5Cap040/1Cap300
MPR Memory E2TD-200 3DB18671AAAA R/4Cap040/2Cap300
MPR Memory E6TD-200 3DB18672AAAA R/6Cap300
MPR Memory D6TD-200 3DB18718AAAA R/6Cap350
MPR Memory L6SA-200 3DB18673AAAA R/6Cap040/TDM2Eth/ATM2Eth
MPR Memory M1SA-200 3DB18675AAAA R/5Cap040/1Cap080/TDM2Eth/ATM2Eth
MPR Memory M2SA-200 3DB18676AAAA R/4Cap040/2Cap080/TDM2Eth/ATM2Eth
MPR Memory M6SA-200 3DB18677AAAA R/6Cap080/TDM2Eth/ATM2Eth
MPR Memory H1SA-200 3DB18678AAAA R/5Cap040/1Cap100/TDM2Eth/ATM2Eth
MPR Memory H2SA-200 3DB18679AAAA R/4Cap040/2Cap100/TDM2Eth/ATM2Eth
MPR Memory H6SA-200 3DB18680AAAA R/6Cap100/TDM2Eth/ATM2Eth
MPR Memory V1SA-200 3DB18681AAAA R/5Cap040/1Cap150/TDM2Eth/ATM2Eth
MPR Memory V2SA-200 3DB18682AAAA R/4Cap040/2Cap150/TDM2Eth/ATM2Eth
MPR Memory V6SA-200 3DB18683AAAA R/6Cap150/TDM2Eth/ATM2Eth
MPR Memory E1SA-200 3DB18684AAAA R/5Cap040/1Cap300/TDM2Eth/ATM2Eth
MPR Memory E2SA-200 3DB18685AAAA R/4Cap040/2Cap300/TDM2Eth/ATM2Eth
MPR Memory E6SA-200 3DB18686AAAA R/6Cap300/TDM2Eth/ATM2Eth

MPR Memory I1TD-200 3DB18665AAAA R/5Cap040/1Cap060
MPR Memory I2TD-200 3DB18687AAAA R/4Cap040/2Cap060
MPR Memory I6TD-200 3DB18688AAAA R/6Cap060
MPR Memory I1SA-200 3DB18689AAAA R/5Cap040/1Cap060/TDM2Eth/ATM2Eth
MPR Memory I2SA-200 3DB18690AAAA R/4Cap040/2Cap060/TDM2Eth/ATM2Eth
MPR Memory I6SA-200 3DB18691AAAA R/6Cap060/TDM2Eth/ATM2Eth
MPR Memory A1TD-200 3DB18692AAAA R/5Cap040/1Cap130
MPR Memory A2TD-200 3DB18693AAAA R/4Cap040/2Cap130
MPR Memory A6TD-200 3DB18694AAAA R/6Cap130
MPR Memory A1SA-200 3DB18695AAAA R/5Cap040/1Cap130/TDM2Eth/ATM2Eth
MPR Memory A2SA-200 3DB18696AAAA R/4Cap040/2Cap130/TDM2Eth/ATM2Eth
MPR Memory A6SA-200 3DB18697AAAA R/6Cap130/TDM2Eth/ATM2Eth
MPR Memory A1TD-200A 3DB18698AAAA R/5Cap040/1Cap130/6modAdp
MPR Memory A2TD-200A 3DB18699AAAA R/4Cap040/2Cap130/6modAdp
MPR Memory A6TD-200A 3DB18700AAAA R/6Cap130/6modAdp
MPR Memory A1SA-200A 3DB18701AAAA R/5Cap040/1Cap130/TDM2Eth/ATM2Eth/6modAdp
MPR Memory A2SA-200A 3DB18702AAAA R/4Cap040/2Cap130/TDM2Eth/ATM2Eth/6modAdp
MPR Memory A6SA-200A 3DB18703AAAA R/6Cap130/TDM2Eth/ATM2Eth/6modAdp
MPR Memory L6TD-200A 3DB18704AAAA R/6Cap040/6modAdp
MPR Memory M2TD-200A 3DB18705AAAA R/4Cap040/2Cap080/6modAdp
MPR Memory M6TD-200A 3DB18706AAAA R/6Cap080/6modAdp
MPR Memory V1TD-200A 3DB18707AAAA R/5Cap040/1Cap150/6modAdp
MPR Memory L6SA-200A 3DB18708AAAA R/6Cap040/TDM2Eth/ATM2Eth/6modAdp
MPR Memory M2SA-200A 3DB18709AAAA R/4Cap040/2Cap080/TDM2Eth/ATM2Eth/6modAdp
MPR Memory M6SA-200A 3DB18710AAAA R/6Cap080/TDM2Eth/ATM2Eth/6modAdp
MPR Memory V1SA-200A 3DB18711AAAA R/5Cap040/1Cap150/TDM2Eth/ATM2Eth/6modAdp
MPR Memory D6SA-200A 3DB18719AAAA R/6Cap350/TDM2Eth/ATM2Eth/6modAdp
MPR Memory D6TD-200A 3DB18720AAAA R/6Cap350/6modAdp
MPR Memory D12SA-210A 3DB18757AAAA R/12Cap350/TDM2Eth/ATM2Eth/12modAdp
SW 3.0.0
SWP 9500 MPR-E 3.0.0 3DB18818AAAA

Hybrid Operating System
SWP9500 MPR-E 3.0.0 3DB18819AAAA

Packet Operating System

MPR-E 3.0.0 3DB18794AAAA
User Manual CD ROM EN
TCO SW Suite Rel 4.3.0 3DB75014AAAA
SWP OPTICS-IM WT SNMP 3DB18820AAAA

V4.21
2.7.2 ODU300 (with internal lightning surge suppressor)
APR CODES Freq. TRsp Frequency Description

(MHz) Range
3DB23214HAXX 6 GHz 160/170 6.540-6.610 ODU 300, 06GHz, T-R 160/170MHz, 6540-6610MHz,
HP, TX LOW
3DB23214HBXX 6.710-6.780 ODU 300, 06GHz, T-R 160/170MHz, 6710-6780MHz,

HP, TX HIGH
3DB23214HCXX 6.590-6.660 ODU 300, 06GHz, T-R 160/170MHz, 6590-6660MHz,

HP, TX LOW
3DB23214HDXX 6.760-6.830 ODU 300, 06GHz, T-R 160/170MHz, 6760-6830MHz,

HP, TX HIGH
3DB23214HEXX 6.640-6.710 ODU 300, 06GHz, T-R 160/170MHz, 6640-6710MHz,

HP, TX LOW
3DB23214HFXX 6.800-6.870 ODU 300, 06GHz, T-R 160/170MHz, 6800-6870MHz,

HP, TX HIGH
3DB23215HAXX 6 GHz 252 5930-6020 ODU 300, 06GHz, T-R 252MHz, 5930-6020MHz,
HHP, TX LOW
3DB23215HDXX 6182-6273 ODU 300, 06GHz, T-R 252MHz, 6182-6273MHz, HP

TX HIGH
3DB23215HBXX 5989-6079 ODU 300, 06GHz, T-R 252MHz, 5989-6079MHz, HP,

TX LOW
3DB23215HEXX 6241-6332 ODU 300, 06GHz, T-R 252MHz, 6241-6332MHz, HP,

TX HIGH
3DB23215HCXX 6078-6168 ODU 300, 06GHz, T-R 252MHz, 6078-6168MHz, HP,

TX LOW
3DB23215HFXX 6330-6421 ODU 300, 06GHz, T-R 252MHz, 6330-6421MHz, HP,

TX HIGH

(MHz) Range
HP, TX LOW
3DB23216HBXX 6770-6930 ODU 300, 06GHz, T-R 0340MHz, 6770-6930MHz,

HP, TX HIGH
3DB23216HCXX 6515-6675 ODU 300, 06GHz, T-R 0340MHz, 6515-6675MHz,

HP, TX LOW
3DB23216HDXX 6855-7015 ODU 300, 06GHz, T-R 0340MHz, 6855-7015MHz,

HP, TX HIGH
3DB23216HEXX 6600-6760 ODU 300, 06GHz, T-R 0340MHz, 6600-6760MHz,

HP, TX LOW
3DB23216HFXX 6940-7100 ODU 300, 06GHz, T-R 0340MHz, 6940-7100MHz,

HP, TX HIGH
7 GHz 150 7424-7485 ODU 300, 07GHz, T-R 0150MHz, 7424-7485MHz,

HP, TX LOW
7574-7635 ODU 300, 07GHz, T-R 0150MHz, 7574-7635MHz,

HP, TX HIGH
7470-7530 ODU 300, 07GHz, T-R 0150MHz, 7470-7530MHz,

HP, TX LOW
7620-7680 ODU 300, 07GHz, T-R 0150MHz, 7620-7680MHz,

HP, TX HIGH
7515-7575 ODU 300, 07GHz, T-R 0150MHz, 7515-7575MHz,

HP, TX LOW
7665-7725 ODU 300, 07GHz, T-R 0150MHz, 7665-7725MHz,

HP, TX HIGH
HP, TX LOW

HP, TX HIGH

(MHz) Range
3DB23028HBXX 7 GHz 161 7124-7184 ODU 300, 07GHz, T-R 0161MHz, 7124-7184MHz,
HP, TX LOW
3DB23028HGXX 7282-7342 ODU 300, 07GHz, T-R 0161MHz, 7282-7342MHz,

HP, TX HIGH

HP, TX LOW
3DB23028HIXX 7331-7391 ODU 300, 07GHz, T-R 0161MHz, 7331-7391MHz,

HP TX HIGH

HP, TX LOW
3DB23028HKXX 7366-7426 ODU 300, 07GHz, T-R 0161MHz, 7366-7426MHz,

HP, TX HIGH
3DB23028HOXX 7549-7606 ODU 300, 07GHz, T-R 0161MHz, 7549-7606MHz,

HP, TX LOW
3DB23028HRXX 7710-7767 ODU 300, 07GHz, T-R 0161MHz, 7710-7767MHz,

HP, TX HIGH
3DB23028HPXX 7598-7655 ODU 300, 07GHz, T-R 0161MHz, 7598-7655MHz,

HP, TX LOW
3DB23028HSXX 7759-7816 ODU 300, 07GHz, T-R 0161MHz, 7759-7816MHz,

HP, TX HIGH
3DB23028HQXX 7633-7690 ODU 300, 07GHz, T-R 0161MHz, 7633-7690MHz,

HP, TX LOW
3DB23028HTXX 7794-7851 ODU 300, 07GHz, T-R 0161MHz, 7794-7851MHz,

HP, TX HIGH

HP, TX LOW
3DB23028HLXX 7408-7467 ODU 300, 07GHz, T-R 0161MHz, 7408-7467MHz,

HP, TX HIGH
3DB23028HHXX 7299-7355 ODU 300, 07GHz, T-R 0161MHz, 7299-7355MHz,

HP, TX LOW
3DB23028HMXX 7460-7516 ODU 300, 07GHz, T-R 0161MHz, 7460-7516MHz,

HP, TX HIGH
3DB23028HJXX 7333.5-7390 ODU 300, 07GHz, T-R 0161MHz, 7333.5-7390MHz,

HP, TX LOW
3DB23028HNXX 7494.5-7551 ODU 300, 07GHz, T-R 0161MHz, 7494.5-7551MHz,

HP, TX HIGH

(MHz) Range
3DB23026HAXX 7 GHz 154/161/ 7424-7488 ODU 300, 07GHz, T-R 0154/0161/0168MHz, 7424-
168 7488MHz, HP, TX LOW
3DB23026HDXX 7581-7649 ODU 300, 07GHz, T-R 0154/0161/0168MHz, 7581-

7649MHz, HP, TX HIGH
3DB23026HBXX 7480-7544 ODU 300, 07GHz, T-R 0154/0161/0168MHz, 7480-

7544MHz, HP, TX LOW
3DB23026HEXX 7637-7705 ODU 300, 07GHz, T-R 0154/0161/0168MHz, 7637-

3DB23026HCXX 7512-7568 ODU 300, 07GHz, T-R 0154/0161/0168MHz, 7512-

7568MHz, HP, TX LOW
3DB23026HFXX 7666-7729 ODU 300, 07GHz, T-R 0154/0161/0168MHz, 7666-

3DB23028HAXX 7 GHz 161 7114-7170 ODU 300, 07GHz, T-R 0161MHz, 7114-7170MHZ,
HP, TX LOW
3DB23028HFXX 7275-7331 ODU 300, 07GHz, T-R 0161MHz, 7275-7331MHZ,

HP, TX HIGH
3DB23184HAXX 7298-7358 ODU 300, 07GHZ, T-R 0161MHZ, 7298-7358MHZ,

HP, TX LOW

HP, TX HIGH

HP, TX LOW
3DB23296HBXX 7282-7352 ODU 300, 07GHZ, T-R 0161MHZ, 7282-7352MHZ,

HP, TX HIGH
3DB23296HCXX 7209-7275 ODU 300, 07GHZ, T-R 0161MHZ, 7209-7275MHZ,

HP, TX LOW
3DB23296HDXX 7367-7436 ODU 300, 07GHZ, T-R 0161MHZ, 7367-7436MHZ,

HP, TX HIGH
HP, TX LOW

HP, TX HIGH
3DB23186HCXX 7 GHz 161/168 7499-7583 ODU 300, 07GHz, T-R 0161/0168MHz, 7499-
7583MHz, HP, TX LOW
3DB23186HDXX 7667-7751 ODU 300, 07GHz, T-R 0161/0168MHz, 7667-


(MHz) Range

HP, TX LOW
7299-7360 ODU 300, 07GHz, T-R 0175MHz, 7299-7360MHz,

HP, TX HIGH
7157.5-7217.5 ODU 300, 07GHz, T-R 0175MHz, 7157.5-

7217.5MHz, HP, TX LOW
7332.5-7392.5 ODU 300, 07GHz, T-R 0175MHz, 7332.5-

7392.5MHz, HP, TX HIGH
7190-7250 ODU 300, 07GHz, T-R 0175MHz, 7190-7250MHz,

HP, TX LOW
7365-7425 ODU 300, 07GHz, T-R 0175MHz, 7365-7425MHz,

HP, TX HIGH
HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH
HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX High

(MHz) Range
3DB23029HAXX 8 GHz 119/126 8279-8321 ODU 300, 08GHz, T-R 0119/0126MHz, 8279-
8321MHz, HP, TX LOW

3DB23029HBXX 8307-8349 ODU 300, 08GHz, T-R 0119/0126MHz, 8307-

8349MHz, HP, TX LOW
3DB23029HEXX 8426-8468 ODU 300, 08GHz, T-R 0119/0126MHz, 8426-

3DB23029HCXX 8335-8377 ODU 300, 08GHz, T-R 0119/0126MHz, 8335-

8377MHz, HP, TX LOW
3DB23029HFXX 8454-8496 ODU 300, 08GHz, T-R 0119/0126MHz, 8454-

HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH
HP, TX LOW

HP, TX HIGH
HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

HP, TX LOW
3DB23031HFXX 8356-8454 ODU 300, 08GHz, T-R 0208MHz,8356-8454MHz,

HP, TX HIGH

(MHz) Range
HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH
HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH
3DB23033HAXX 8 GHz 305/311 7722.5-7859 ODU 300, 08GHz, T-R 0305/0311MHz, 7722.5-
7859MHz, HP, TX LOW


7981MHz, HP, TX LOW


EP, TX LOW
10615-10625 ODU 300, 10GHz, T-R 0065MHz, 10615-10625MHz,

EP, TX HIGH
10560-10570 ODU 300, 10GHz, T-R 0065MHz, 10560-10570MHz,

EP, TX LOW
10625-10635 ODU 300, 10GHz, T-R 0065MHz, 10625-10635MHz,

EP, TX HIGH
10570-10580 ODU 300, 10GHz, T-R 0065MHz, 10570-10580MHz,

EP, TX LOW
10635-10645 ODU 300, 10GHz, T-R 0065MHz, 10635-10645MHz,

EP, TX HIGH
10580-10590 ODU 300, 10GHz, T-R 0065MHz, 10580-10590MHz,

EP, TX LOW

(MHz) Range

EP, TX HIGH
10590-10600 ODU 300, 10GHz, T-R 0065MHz, 10590-10600MHz,

EP, TX LOW
10655-10665 ODU 300, 10GHz, T-R 0065MHz, 10655-10665MHz,

EP, TX HIGH
10600-10610 ODU 300, 10GHz, T-R 0065MHz, 10600-10610MHz,

EP, TX LOW
10665-10675 ODU 300, 10GHz, T-R 0065MHz, 10665-10675MHz,

EP, TX HIGH
10605-10615 ODU 300, 10GHz, T-R 0065MHz, 10605-10615MHz,

EP, TX LOW
10670-10680 ODU 300, 10GHz, T-R 0065MHz, 10670-10680MHz,

EP, TX HIGH
3DB23255HAXX 10 GHz 91 10500.5-10516.3 ODU 300, 10GHz, T-R 0091MHz, 10500.5-

10516.3MHz, EP, TX LOW
3DB23255HBXX 10591.5-10607.3 ODU 300, 10GHz, T-R 0091MHz, 10591.5-

10607.3MHz, EP, TX HIGH
3DB23255HCXX 10514.5-10530.3 ODU 300, 10GHz, T-R 0091MHz, 10514.5-

3DB23255HDXX 10605.5-10621.3 ODU 300, 10GHz, T-R 0091MHz, 10605.5-

3DB23255HEXX 10528.5-10544.3 ODU 300, 10GHz, T-R 0091MHz, 10528.5-

3DB23255HFXX 10619.5-10635.3 ODU 300, 10GHz, T-R 0091MHz, 10619.5-

3DB23255HGXX 10542.5-10558.3 ODU 300, 10GHz, T-R 0091MHz, 10542.5-

3DB23255HHXX 10633.5-10649.3 ODU 300, 10GHz, T-R 0091MHz, 10633.5-

3DB23255HIXX 10556.5-10572.3 ODU 300, 10GHz, T-R 0091MHz, 10556.5-

3DB23255HLXX 10647.5-10663.3 ODU 300, 10GHz, T-R 0091MHz, 10647.5-

3DB23255HMXX 10570.5-10586.3 ODU 300, 10GHz, T-R 0091MHz, 10570.5-

3DB23255HNXX 10661.5-10677.3 ODU 300, 10GHz, T-R 0091MHz, 10661.5-


(MHz) Range
3DB23261HAXX 10 GHz 350 10150.5-10252 ODU 300, 10GHz, T-R 0350MHz, 10150.5-
10252MHz, EP, TX LOW
3DB23261HBXX 10500.5-10602 ODU 300, 10GHz, T-R 0350MHz, 10500.5-

10602MHz, EP, TX HIGH
3DB23261HCXX 10196-10297.5 ODU 300, 10GHz, T-R 0350MHz, 10196-

3DB23261HDXX 10546-10647.5 ODU 300, 10GHz, T-R 0350MHz, 10546-

3DB23035HAXX 11 GHz 490/500/ 10675-10835 ODU 300, 11GHz, T-R 0490/0500/0530MHz, 10675-
3DB23035HEXX 11200-11345 ODU 300, 11GHz, T-R 0490/0500/0530MHz, 11200-

3DB23035HBXX 10795-10955 ODU 300, 11GHz, T-R 0490/0500/0530MHz, 10795-

10955MHz, HP, TX LOW
3DB23035HFXX 11310-11465 ODU 300, 11GHz, T-R 0490/0500/0530MHz, 11310-

3DB23035HCXX 10915-11075 ODU 300, 11GHz, T-R 0490/0500/0530MHz, 10915-

3DB23035HGXX 11430-11585 ODU 300, 11GHz, T-R 0490/0500/0530MHz, 11430-

3DB23035HDXX 11035-11200 ODU 300, 11GHz, T-R 0490/0500/0530MHz, 11035-

3DB23035HHXX 11550-11705 ODU 300, 11GHz, T-R 0490/0500/0530MHz, 11550-

HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

HP, TX LOW

(MHz) Range
3DB23036HGXX 13 GHz 266 13101-13185 ODU 300, 13GHz, T-R 0266MHz, 13101-13185MHz,
HHP, TX HIGH
HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH
HHP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH
3DB23039HCXX 15 GHz 475 14500-14660 ODU 300, 15GHz, T-R 0475MHz, 14500-14660MHz,
HP, TX LOW

HP, TX HIGH
3DB23039HEXX 15 GHz 490 14403-14634 ODU 300, 15GHz, T-R 0490MHz, 14403-14634MHz,
HP, TX LOW

HP, TX HIGH
3DB23039HAXX 15 GHz 475/490 14627-14873 ODU 300, 15GHz, T-R 0475/0490MHz, 14627-


(MHz) Range
3DB23295HAXX 15 GHz 644/728 14500-14714.5 ODU 300, 15GHz, T-R 0644/0728MHz, 14500-
14714.5MHZ, HP, TX LOW
3DB23295HBXX 15136.5-15350 ODU 300, 15GHz, T-R 0644/0728MHz, 15136.5-

15350MHZ, HP, TX HIGH
HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH
3DB23042HAXX 18 GHz 1008/ 17700-18060 ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,

1010/ 17700-18060MHz, HP, TX LOW
1092/
3DB23042HEXX 1120 18710-19070 ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,
18710-19070MHz, HHP, TX HIGH
3DB23042HBXX 17905-18275 ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,

17905-18275MHz, HHP, TX LOW
3DB23042HFXX 18920-19290 ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,

18920-19290MHz, HP, TX HIGH
3DB23042HCXX 18110-18490 ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,

18110-18490MHz, HP, TX LOW
3DB23042HGXX 19130-19510 ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,

3DB23042HDXX 18330-18690 ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,

18330-18690MHz, HP, TX LOW
3DB23042HHXX 19340-19700 ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,


(MHz) Range
3DB23062HCXX 18 GHz 1560 17700 - 18140 ODU 300, 18GHz, T-R 1560MHz, 17700-18140MHz,
HP, TX LOW
3DB23062HDXX 19260 - 19700 ODU 300, 18GHz, T-R 1560MHz, 19260-19700MHz,

HP, TX HIGH
HP, TX LOW

HP, TX HIGH
HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH
3DB23045HAXX 23 GHz 1200/ 21200-21570 ODU 300, 23GHz, T-R 1200/1232MHz, 21200-
3DB23045HEXX 22400-22770 ODU 300, 23GHz, T-R 1200/1232MHz, 22400-


3DB23045HFXX 22675-23045 ODU 300, 23GHz, T-R 1200/1232MHz, 22675-


3DB23045HGXX 22950-23320 ODU 300, 23GHz, T-R 1200/1232MHz, 22950-


3DB23045HHXX 23320-23600 ODU 300, 23GHz, T-R 1200/1232MHz, 23230-


(MHz) Range
HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH
HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH
HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

(MHz) Range
3DB48245HGXX 32 GHz 812 32151-32401 ODU 300, 32GHz, T-R 0812MHz, 32151-32401MHz,
HP, TX LOW

HP, TX HIGH
HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH
3DB23258HGXX 37868-38208 ODU 300, 38GHz, T-R 1260MHz, 37868-38208MHz,

HP, TX LOW

HP, TX HIGH
3DB23258HIXX 37251-37526 ODU 300, 38GHz, T-R 1260MHz, 37251-37526MHz,

HP, TX LOW
3DB23258HLXX 38511-38786 ODU 300, 38GHz, T-R 1260MHz, 38511-38786MHz,

HP, TX HIGH
3DB23258HMXX 37058-37478 ODU 300, 38GHz, T-R 1260MHz, 37058-37478MHz,

HP, TX LOW
3DB23258HNXX 38318-38738 ODU 300, 38GHz, T-R 1260MHz, 38318-38738MHz,

HP, TX HIGH

HP, TX LOW
39000-39250 ODU 300, 38GHz, T-R 1000MHz, 39000-39250MHz,

HP, TX HIGH
38250-38500 ODU 300, 38GHz, T-R 1000MHz, 38250-38500MHz,

HP, TX LOW
39250-39500 ODU 300, 38GHz, T-R 1000MHz, 39250-39500MHz,

HP, TX HIGH

2.7.3 MPT-HC with internal diplexer
Table 7. MPT-HC codes with internal diplexer

Band (GHz) Shifter (MHz) Tx sub-band APR codes Tx frequency (MHz)
L6 252 1 3DB20441ABXX 5930-6049
1P 3DB20443ABXX 6182-6302
2 3DB20442ABXX 6048-6168
2P 3DB20444ABXX 6301-6420
U6 340 1 3DB20437ABXX 6420-6600
1P 3DB20439ABXX 6760-6940
2 3DB20438ABXX 6565-6745
2P 3DB20440ABXX 6905-7085
3 3DB20464ABXX 6595-6775
3P 3DB20465ABXX 6935-7115
11 530-490 1 3DB20371ABXX 10695-10955
1P 3DB20547ABXX 11205-11485
2 3DB20546ABXX 10935-11205
2P 3DB20548ABXX 11445-11705
13 266 1 3DB20372ABXX 12750-12865
1P 3DB20420ABXX 13016-13131
2 3DB20419ABXX 12861-12980
2P 3DB20421ABXX 13127-13246
15 308-315-322 1 3DB20466ABXX 14630-14766
1P 3DB20468ABXX 14945-15081
2 3DB20467ABXX 14759-14899
2P 3DB20469ABXX 15074-15215
420-475 1 3DB20373ABXX 14500-14724
1P 3DB20423ABXX 14920-15144
420 2 3DB20422ABXX 14710-14941
2P 3DB20424ABXX 15130-15361
490 1 3DB20425ABXX 14400-14635
1P 3DB20427ABXX 14890-15125
2 3DB20426ABXX 14625-14860
2P 3DB20428ABXX 15115-15350
640-644-728 1 3DB20448ABXX 14500-14700
1P 3DB20449ABXX 15144-15348

18 1560 1 3DB20432ABXX 17700-18140
1P 3DB20433ABXX 19260-19700
340 1 3DB20549ABXX 18581-18700
1P 3DB20551ABXX 18920-19040
2 3DB20550ABXX 18701-18820
2P 3DB20552ABXX 19040-19160
1008-1010 1 3DB20374ABXX 17700-18201
1P 3DB20430ABXX 18710-19211
2 3DB20429ABXX 18180-18690
2P 3DB20431ABXX 19190-19700
23 1200-1232 1 3DB20473ABXX 21198-21819
1P 3DB20475ABXX 22400-23019
1050-1200-1232 2 3DB20474ABXX 21781-22400
2P 3DB20476ABXX 22981-23600
1008 1 3DB20375ABXX 22000-22315
1P 3DB20471ABXX 23008-23323
2 3DB20470ABXX 22300-22600
2P 3DB20472ABXX 23308-23608
25 1008 1 3DB20376ABXX 24540-24997
1P 3DB20554ABXX 25548-26005
2 3DB20553ABXX 24994-25448
2P 3DB20555ABXX 26002-26456
38 1260 1 3DB20458ABXX 37050-37620
1P 3DB20460ABXX 38310-38880
2 3DB20459ABXX 37619-38180
2P 3DB20461ABXX 38879-39440

2.7.4 MPT-HC V2 with internal diplexer
Table 8. MPT-HC V2 codes with internal diplexer

L6 252 1 3DB20441BAXX 5930-6049
1P 3DB20443BAXX 6182-6302
2 3DB20442BAXX 6048-6168
2P 3DB20444BAXX 6301-6420
U6 340 1 3DB20437BAXX 6420-6600
1P 3DB20439BAXX 6760-6940
2 3DB20438BAXX 6565-6745
2P 3DB20440BAXX 6905-7085
3 3DB20464BAXX 6595-6775
3P 3DB20465BAXX 6935-7115
11 530-490 1 3DB20371BAXX 10695-10955
1P 3DB20547BAXX 11205-11485
2 3DB20546BAXX 10935-11205
2P 3DB20548BAXX 11445-11705
13 266 1 3DB20372BAXX 12750-12865
1P 3DB20420BAXX 13016-13131
2 3DB20419BAXX 12861-12980
2P 3DB20421BAXX 13127-13246
15 308-315-322 1 3DB20466BAXX 14630-14766
1P 3DB20468BAXX 14945-15081
2 3DB20467BAXX 14759-14899
2P 3DB20469BAXX 15074-15215
420-475 1 3DB20373BAXX 14500-14724
1P 3DB20423BAXX 14920-15144
420 2 3DB20422BAXX 14710-14941
2P 3DB20424BAXX 15130-15361
490 1 3DB20425BAXX 14400-14635
1P 3DB20427BAXX 14890-15125
2 3DB20426BAXX 14625-14860
2P 3DB20428BAXX 15115-15350
640-644-728 1 3DB20448BAXX 14500-14700
1P 3DB20449BAXX 15144-15348

18 1560 1 3DB20432BAXX 17700-18140
1P 3DB20433BAXX 19260-19700
340 1 3DB20549BAXX 18581-18700
1P 3DB20551BAXX 18920-19040
2 3DB20550BAXX 18701-18820
2P 3DB20552BAXX 19040-19160
1008-1010 1 3DB20374BAXX 17700-18201
1P 3DB20430BAXX 18710-19211
2 3DB20429BAXX 18180-18690
2P 3DB20431BAXX 19190-19700
23 1200-1232 1 3DB20473BAXX 21198-21819

(NB1)
1P 3DB20475BAXX 22400-23019
1050-1200-1232 2 3DB20474BAXX 21781-22400
2P 3DB20476BAXX 22981-23600
1008 1 3DB20375BAXX 22000-22315
1P 3DB20471BAXX 23008-23323
2 3DB20470BAXX 22300-22600
2P 3DB20472BAXX 23308-23608
25 1008 1 3DB20376BAXX 24540-24997
1P 3DB20554BAXX 25548-26005
2 3DB20553BAXX 24994-25448
2P 3DB20555BAXX 26002-26456
38 1260 1 3DB20458BAXX 37050-37620
1P 3DB20460BAXX 38310-38880
2 3DB20459BAXX 37619-38180
2P 3DB20461BAXX 38879-39440
N.B.1: The MPT-HC V2 is a Tx High Power version vs. MPT-HC. Take in account it when MPT-HC V2
is used as spare of MPT-HC.

2.7.5 MPT-MC with internal diplexer
Table 9. MPT-MC codes with internal diplexer

L6 252 1 3DB20838AAXX 5930-6049
1P 3DB20840AAXX 6182-6302
2 3DB20839AAXX 6048-6168
2P 3DB20841AAXX 6301-6420
11 490-530 1 3DB20874AAXX 10695-10955
1P 3DB20876AAXX 11205-11485
2 3DB20875AAXX 10935-11205
2P 3DB20877AAXX 11445-11705
13 266 1 3DB20818AAXX 12750-12865
1P 3DB20820AAXX 13016-13131
2 3DB20819AAXX 12861-12980
2P 3DB20821AAXX 13127-13246
15 420-475 1 3DB20822AAXX 14500-14724
1P 3DB20824AAXX 14920-15144
420 2 3DB20823AAXX 14710-14941
2P 3DB20825AAXX 15130-15361
490 1 3DB20826AAXX 14400-14635
1P 3DB20828AAXX 14890-15125
2 3DB20827AAXX 14625-14860
2P 3DB20829AAXX 15115-15350
18 1560 1 3DB20864AAXX 17700-18140
1P 3DB20865AAXX 19260-19700
1008-1010 1 3DB20860AAXX 17700-18201
1P 3DB20862AAXX 18710-19211
2 3DB20861AAXX 18180-18690
2P 3DB20863AAXX 19190-19700

23 1200-1232 1 3DB20834AAXX 21198-21819
1P 3DB20836AAXX 22400-23019
1050-1200-1232 2 3DB20835AAXX 21781-22400
2P 3DB20837AAXX 22981-23600
1008 1 3DB20830AAXX 22000-22315
1P 3DB20832AAXX 23008-23323
2 3DB20831AAXX 22300-22600
2P 3DB20833AAXX 23308-23608
25 1008 1 3DB20854AAXX 24540-24997
1P 3DB20856AAXX 25548-26005
2 3DB20855AAXX 24994-25448
2P 3DB20857AAXX 26002-26456
38 1260 1 3DB20870AAXX 37050-37620
1P 3DB20872AAXX 38310-38880
2 3DB20871AAXX 37619-38180
2P 3DB20873AAXX 38879-39440

2.7.6 Part lists of MPT-HC/MPT-HC V2/MPT-MC with external diplexer
The diplexer included in the available BRANCHING assemblies refers to ITU–R F.385, 386 and RF special
CUSTOMERS channelling with Tx/Rx separation specified in following Table 14. and Table 19.
Each diplexer is a 3-port passive device with two band–pass filters as described hereafter.
Each BRANCHING assembly has two different variants by duplex spacing, depending on the RF_Tx out-
put frequency band as described on the table below:
3DB Variant Channel
3DB xxxxx AAXX 1_1p
3DB xxxxx ABXX 2_2p
The arrangement between each filters on the same branching device is described below:
WARNING: f1, f2, f3 and f4 frequencies of the branching filters refer to the extreme channel frequencies
and not to the cut–off frequencies of the filters.
Table 10. 7 GHz MPT-MC codes with external diplexer

7/8 NA Lower 3DB20858AAXX 7107 - 8370
Upper 3DB20859AAXX 7261 - 8496
Table 11. 7 GHz MPT-HC codes with external diplexer

7/8 NA Lower 3DB20454ADXX 7107 - 8370
Upper 3DB20456ADXX 7261 - 8496

Table 12. 7 GHz MPT-HC V2 codes with external diplexer
7/8 NA Lower 3DB20454BAXX 7107 - 8370
Upper 3DB20456BAXX 7261 - 8496
Table 13. 7 GHz MPT-HC V2 High Power codes with external diplexer
7/8 NA Lower 3DB20454BBXX 7107 - 8370
Upper 3DB20456BBXX 7261 - 8496
Table 14. 7 GHz Branching assemblies (for MPT-HC and MPT-MC)

Filter 1 MHz Filter 2 MHz
Central BRANCHING ASSEMBLY
Shifter (Lower Band) (Upper Band)
Freq.
MHz Low High Low High
MHz APR codes Technical Description
Limit f1 Limit f2 Limit f3 Limit f4
154 7212,0 7107,0 7163,0 7261,0 7317,0 3DB 10060 AAXX ... CH1–1P P.SH. 154_C MHz
154 7547,0 7428,0 7512,0 7582,0 7666,0 3DB 06774 AAXX ... CH1–1P P.SH. 154_A MHz
154 7603,0 7484,0 7568,0 7638,0 7722,0 3DB 06774 ABXX ... CH2–2P P.SH. 154_A MHz
154 7561,0 7442,0 7526,0 7596,0 7680,0 ... CH1–1P P.SH.154_B MHz
3DB 06775 AAXX
160 7561,0 7442,0 7520,0 7602,0 7680,0 ... CH1–1P P.SH.160 MHz
154 7617,0 7498,0 7582,0 7652,0 7736,0 ... CH2–2P P.SH.154_B MHz
3DB 06775 ABXX
160 7617,0 7498,0 7576,0 7658,0 7736,0 ... CH2–2P P.SH.160 MHz
161 7240,0 7124,5 7194,5 7285,5 7355,5 3DB 06780 AAXX ... CH1–1P P.SH.161_A MHz
161 7310,0 7194,5 7264,5 7355,5 7425,5 3DB 06780 ABXX ... CH2–2P P.SH.161_A MHz
161 7365,0 7249,5 7319,5 7410,5 7480,5 3DB 06781 AAXX ... CH1–1P P.SH.161_B MHz
161 7435,0 7319,5 7389,5 7480,5 7550,5 3DB 06781 ABXX ... CH2–2P P.SH.161_B MHz
161 7390,0 7274,5 7344,5 7435,5 7505,5 3DB 06782 AAXX ... CH1–1P P.SH.161_C MHz
161 7460,0 7344,5 7414,5 7505,5 7575,5 3DB 06782 ABXX ... CH2–2P P.SH.161_C MHz
161 7540,0 7424,5 7494,5 7585,5 7655,5 3DB 06783 AAXX ... CH1–1P P.SH.161_D MHz
161 7610,0 7494,5 7564,5 7655,5 7725,5 3DB 06783 ABXX ... CH2–2P P.SH.161_D MHz
161 7665,0 7549,5 7619,5 7710,5 7780,5 3DB 06784 AAXX ... CH1–1P P.SH.161_E MHz
161 7735,0 7619,5 7689,5 7780,5 7850,5 3DB 06784 ABXX ... CH2–2P P.SH.161_E MHz
161 7690,0 7574,5 7644,5 7735,5 7805,5 3DB 06785 AAXX ... CH1–1P P.SH.161_F MHz
161 7760,0 7644,5 7714,5 7805,5 7875,5 3DB 06785 ABXX ... CH2–2P P.SH.161_F MHz

168 7299,0 7187,0 7243,0 7355,0 7411,0 3DB 10059 AAXX ... CH1–1P P.SH.168_B MHZ
168 7569,0 7443,0 7527,0 7611,0 7695,0 3DB 06776 AAXX ... CH1–1P P.SH.168 MHZ
168 7625,0 7499,0 7583,0 7667,0 7751,0 3DB 06776 ABXX ... CH2–2P P.SH.168 MHZ
N.B. Shifter value choice to be done by WebEML.
Table 15. 8 GHz MPT-MC codes with external diplexer

7/8 NA Lower 3DB20858AAXX 7107 - 8370
Upper 3DB20859AAXX 7261 - 8496
Table 16. 8 GHz MPT-HC codes with external diplexer

7/8 NA Lower 3DB20454ADXX 7107 - 8370
Upper 3DB20456ADXX 7261 - 8496
Table 17. 8 GHz MPT-HC V2 codes with external diplexer

7/8 NA Lower 3DB20454BAXX 7107 - 8370
Upper 3DB20456BAXX 7261 - 8496
Table 18. 8 GHz MPT-HC V2 High Power codes with external diplexer
7/8 NA Lower 3DB20454BBXX 7107 - 8370
Upper 3DB20456BBXX 7261 - 8496

Table 19. 8 GHz Branching assemblies (for MPT-HC and MPT-MC)
Filter 1 MHz Filter 2 MHz BRANCHING ASSEMBLY
Central (Lower Band) (Upper Band)
Shifter
Freq.
MHz Low High Low High
MHz APR codes Technical Description
Limit f1 Limit f2 Limit f3 Limit f4
119 8366.5 8286.0 8328.0 8405.0 8447.0 ... CH1–1P P.SH.119 MHz
3DB 06789 AAXX
126 8366.5 8282.5 8324.5 8408.5 8450.5 ... CH1–1P P.SH.126 MHz
119 8408.5 8328.0 8370.0 8447.0 8489.0 ... CH2–2P P.SH.119 MHz
3DB 06789 ABXX
126 8408.5 8324.5 8366.5 8450.5 8492.5 ... CH2–2P P.SH.126 MHz
151.614 8315.010 8204.217 8274.189 8355.831 8425.803 3DB 06787 AAXX ... CH1–1P P.SH.151 MHz
151.614 8384.982 8274.189 8344.161 8425.803 8495.775 3DB 06787 ABXX ... CH2–2P P.SH.151 MHz
208 8217.0 8064.0 8162.0 8272.0 8370.0 3DB 10073 AAXX ... CH1–1P P.SH.208 MHZ
208 8301.0 8148.0 8246.0 8356.0 8454.0 3DB 10073 ABXX ... CH2–2P P.SH.208 MHZ
266 8097.5 7905.0 8024.0 8171.0 8290.0 3DB 06788 AAXX ... CH1–1P P.SH.266 MHZ
266 8209.5 8017.0 8136.0 8283.0 8402.0 3DB 06788 ABXX ... CH2–2P P.SH.266 MHZ
294.440 7749.755 8145.915

... CH1–1P
305.560 7947.835 7738.635 7851.475 8044.195 8157.035 3DB 06786 AAXX
P.SH.294/305/311 MHZ
311.320 7732.875 8162.795
311.320 8066.435 7851.475 8162.795 8281.395

... CH2–2P
294.440 7862.965 7970.075 8264.515 3DB 06786 ABXX
8063.740 8157.405 P.SH.294/305/311 MHZ
305.560 7851.845 8275.635
213.5 8147.0 8035.0 8046.0 8248.0 8259.0 3DB 10103 AAXX ... CH1–1P P.SH. 213.5 MHZ
2.7.7 MPT-HC optical interface (mandatory for 1+1 configuration)
Table 20. MPT-HC optical interface (mandatory for 1+1 configuration)

Description APR Codes Remarks
SFP 1000Base-Sx Transceiver 1AB383760001 Optical SFP module to be installed optionally in

the MPT-HC to provide the optical interface
SFP 1000Base-Lx Transceiver 1AB187280040

2.7.8 MPT-HC V2 external modules (mandatory for 1+0/1+1 configurations)
Table 21. MPT-HC V2 external modules

Description APR Codes Remarks
RPS MODULE 3DB20117BAXX All frequency bands
XPIC-RPS MODULE 3DB20116BAXX All frequency bands. This module is also XPIC-
ready and the XPIC connector will be used
when the XPIC feature will be available.
2.7.9 MPT-HC/MPT-HC V2/MPT-MC couplers
Table 22. MPT-HC/MPT-HC V2/MPT-MC couplers

Description APR Codes
6 GHz 1 dB/10 dB coupler 3CC58056ABXX
7.1-8.5 GHz 1 dB/10 dB coupler 3CC14536AAXX
11 GHz 1 dB/10 dB coupler 3CC14140ABXX
13-15 GHz 1 dB/10 dB coupler 3CC13472ABXX
18-23-25 GHz 1 dB/10 dB coupler 3CC13473ABXX
28-32-38 GHz 1 dB/10 dB coupler 3CC13474ABXX
6 GHz 3 dB coupler 3CC58056AAXX
11 GHz 3 dB coupler 3CC14140AAXX
7.1-8.5 GHz 3 dB coupler AWY MPT 3CC14536ABAA
13-15 GHz 3 dB coupler AWY MPT 3CC13472AAXX
18-23-25 GHz 3 dB coupler AWY-MPT 3CC13473AAXX
28-32-38 GHz 3 dB coupler AWY MPT 3CC13474AAXX

2.8 Functional description
2.8.1 MSS (Indoor Unit)

The MSS incorporates the base–band processing and also modem functionalities only when ODU300 is
connected. MSS offers tributaries interfaces as well as supervision.
The MSS is frequency–independent.
Two MSS are available:
– MSS-8
– MSS-4
The MSS-8 is made of:
– 1 subrack (MSS-8 shelf)
– 1 or 2 Core-E Modules (Working & Spare)
– up to 6 Transport Modules
– 1 AUX peripheral unit (option: to be installed in Transport Module #8)
– 1 Fans unit
The MSS-4 is made of:
– 1 subrack (MSS-4 shelf)
– 1 or 2 Core-E Modules (Working & Spare)
– up to 2 Transport Modules
– 1 AUX peripheral unit (option: to be installed in Transport Module #4)
– 1 Fans unit
There are five types of Transport Modules:
– 32xE1 Local Access Module
– 16xE1 ATM Local Access - ASAP Module
– 2xSTM-1 Local Access Module
– Modem Module: to interface the ODU300
– MPT Access Module: to interface up to two MPT. It can provide the PFoE.
In the right part of the MSS shelf there are two sub-D 2-pole power supply connectors.

2.8.1.1 Power distribution
The system receives the Battery input through 2 power connectors mounted on the Subrack structure and
connected directly to the Backplane.
Each board, in which a DC/DC converter is mounted, is provided with fuses and diodes on all the lines,
in order to be fully independent from the other ones.
The ODU300 Modem unit provides the power supply to the ODU300.
The MPT Access unit can provide the PFoE to MPT to supply the MPT by using the same cable used also
to carry the Ethernet traffic.
On the output section the Core-E (Main) board provides +3.3V in parallel with the Core-E (Spare) board
to supply the Fan Unit.
A 3.3V, coming from the two Core-E units, is provided to read the EEPROM present on each board also
when the DC/DC converter, present on its board, is out of order.
Batt. A Batt. B
-48 Vdc +15%/-20% -48 Vdc +15%/-20%
Core-E
(Spare)
FAN UNIT
Core-E
(MAIN)
32E1/ASAP/
STM-1
MPT
Access
ODU300
MODEM
BACK PLANE
Figure 33. Power Distribution Architecture

2.8.1.2 Core-E unit
Figure 34. Core-E unit
– Based on packet technology with 7 GbEth serial internal interfaces between Core-E and
peripherals (jumbo frames 9728 bytes allowed)
– 4x10/100/1000 Ethernet electrical embedded interface (RJ45): port #1 to port #4
– 2 optional SFPs: port #5 and port #6
N.B. To port #5 and port #6 can be connected directly the MPT-HC.
The flash card stores the licence type, the equipment software, the equipment MIB and the equipment
MAC address.
2.8.1.2.1 Main Functions
– Controller
– Layer 2+ Eth Switch, VLAN management & MAC based

• Ethernet MAC learning
• x-connect function for PDH and Data payload traffic;
• For any “packetized” flow, the switch will be in charge to manage the EPS also.
• QoS management.
– Selection of the synchronization Ck to be distributed to all plug-in.
The Core-E unit has the option to equip two SFPs(in port #5, port #6. These ports can be also used to
connect directly an MPT-HC.

2.8.1.2.2 Available SFPs for port #5 and port #6
The following SFPs are available:
– 1000BASE-LX (optical interface for Ethernet traffic)
– 1000BASE-SX (optical interface for Ethernet traffic)
– 1000BASE-T (electrical interface for Ethernet traffic)
– 2xE1 (electrical interface for 2 E1 streams)
– EoSDH (optical interface for STM-1 signal with Ethernet traffic encapsulation)
2.8.1.2.2.1 2xE1 SFP
The 2xE1 SFP is an SFP module supporting MEF8 circuit emulation of up to 2 E1.
This module supports:
– differential clock recovery
– node timing
– loop timing
This module is Synchronous Ethernet capable and it is compliant to optical SFP 1000BASE-X. It can
deliver the clock recovered from one of two tributaries to hosting card through the standard SFP pin-out.
SFP module supports TDM2TDM and TDM2ETH services.
The port, in which the SFP has been installed, must be enabled by the WebEML as an optical port, then
all the configuration must be done with an Enhanced Configuration File.
Note: The SFP must be installed after the Configuration File has been downloaded. If the SFP has
been installed before, withdraw it and then installed it again.
2.8.1.2.2.2 EoSDH SFP
The Ethernet over SDH SFP is an SFP module supporting the delivery of Ethernet traffic over SDH layer
by GFP encapsulation.
The module is compliant to 1000BASE-X specification and support one STM1 interface.
The NE manages the EoSDH SFP as an optical User Ethernet interface. Synchronous operation mode
and SSM support are not available, when EoSDH SFP is hosted as optical User Ethernet interface.
Note: For the correct operation of the EoSDH SFP it is necessary to disable the autonegotiation via
the Configuration File (refer to paragraph 4.2 of the Configuration File User Manual).

Figure 35. Core-E unit
Warning: The optional optical SFP plug-in, which has to be installed in port #5 and port #6 of the Core-
E unit, contains a Class 1 laser source. The laser source is placed in the left side of the SFP plug-in.
space.
2.8.1.3 32xE1 Local Access unit
wk core
FPGA
32 E1 sp core
LIUs (Ceres) CES
wk core
sp core
Figure 36. 32xE1 Local Access unit
In the TX direction, the E1 PDH card (E1 Access) processes and encapsulates up to 32 E1 input lines
into an Ethernet packet that is sent to the Core-E card(s).
In the RX direction, the E1 Access card extracts data from the Ethernet data packets and processes the
data to provide up to 32 E1 output lines.

The 32xE1 Local Access Module performs the following macro functions:
– Termination of 32 E1 signals (32 E1 bi-directional interfaces according ITU-T G.703 on the front
panel)
– Framed E1 bi-directional alarm management
– Bi-directional Performance Monitoring on Framed E1
– Encapsulation/Extraction of those PDH data flows into/from standard Ethernet packets Inter Working
Function
– Reconstruction of the original PDH Timing meeting G823/824 Req.
– Selection of the Active Core-E
– Sending/getting those std Eth packets to the Core-E module
– Communication with the Controller for provisioning and status report
The module communicates with the Core-E modules through two GbEth Serial copper bi-directional
interfaces on the backplane.
E1 E1
17-32 1-16
Figure 37. PDH Access unit
2.8.1.4 2xSTM-1 Local Access unit
Figure 38. 2xSTM-1 Local Access unit
This unit can manage up to 2xSTM-1 by installing two optional STM-1 SFP plug-ins (electrical or optical).

In the TX direction, the STM-1 Local Access unit processes and encapsulates up to 2xSTM-1 input lines
into an Ethernet packet that is sent to the Core-E card(s).
In the RX direction, the STM-1 Local Access unit extracts data from the Ethernet data packets and
processes the data to provide up to 2 STM-1 output lines.
The 2xSTM-1 Local Access Unit performs the following macro functions:
– Transparent transport of the STM-1
– Encapsulation/Extraction of the STM-1 into/from standard Ethernet packets Inter Working Function
– Reconstruction of the original STM-1 Timing
– Selection of the Active Core-E
– Sending/getting those std Eth packets to the Core-E module
– Communication with the Controller for provisioning and status report
The unit communicates with the Core-E modules through two GbEth Serial copper bi-directional
interfaces on the backplane.
Optional SFP (electrical or optical)
Figure 39. STM-1 Access unit
2.8.1.5 ASAP unit
The ASAP unit is used to transport 16xE1 ATM traffic, with E1/IMA physical layer, in an MPR network.
The ASAP units are unprotected (No 1+1 EPS is available).
ATM traffic is transported within MPR network as "special" Ethernet traffic.
This "special" Ethernet traffic is managed by MPR following to RFC 4717 (IETF ATM PseudoWire Edge-
toEdgeEmulation, PWE3) with N-1 encapsulation format.
ATM PW Ethernet traffic is managed by MPR is such a way to emulate the native QoS that would be
applied by an ATM equipment; in addition to that, specific techniques, similar to those applied to
TDM2ETH traffic, are applied to have air bandwidth optimisation (ATM PW Header Compression) and
reduce Cell Error Rate degradation due to packetization.

Main Characteristics
– 16xE1 G.704 supporting ATM/IMA
– IMA protocol 1.1
– Node-timed/loop-timed E1 port synch
– ATM PWE3 encapsulation with N-to-one (N=1) encapsulation format (RFC 4717)
– Max 8 IMA group
– Max 16 E1 per IMA group
– The IMA group must be in the same ASAP card
– Ingress/Egress VPI translation
– Transport of ATM traffic can be done in VCC mode or VPC mode (all the nodes of the MPR chain
must have the same mode):
• VCC mode
– It is possible to transport max 48 VC for every IMA group. It is possible to manage VC

switching (= VCI and VPI change)
– It is possible to assign at every VC one specific QoS. Policing and shaping at ATM level
has performed VC mode only
– The VC of the same class level (CBR / UBR+ / UBR) are managed in the same radio
queue, then are available 3 different radio queues
• VPC mode
– It is possible to transport max 48 VP for every IMA group. It is possible to manage only
VP switching (=only VPI change)
– All the VC inside the VP must have same QoS (= for ex. all CBR or all UBR)
– The radio QoS (= radio tails) and QoS ATM (=policing and shaping) is managed only at
VP level.
N.B. The sum of VP + VC configured on a single ASAP card must be <128.
Interfaces
– 16 E1 G.704 - SCSI Connectors
– 75 ohm or 120 ohm (at NE level)
Block Diagram
(Refer to Figure 40. on page 117).
The 16xE1 ATM streams enter the ASAP unit on the front panel.

The block diagram is divided in 3 parts:
– LIU/Framer
– Network Processor
– Confederation FPGA
The main functions implemented by the LIU/Framer are:
– Internal termination supported: 75 ohm, 120 ohm.
– Line code supported: HDB3.
– Pulse shape: digitally programmable
– Framing to G.704 E1 signals and to CRC-4 multi-frame alignment signals.
– Detection of alarm conditions as loss of signal, loss of frame, loss of signaling multi-frame and loss
of CRC multi-frame.
The Network Processor is the heart of the ASAP card and provides the implementation of the protocols
to be supported as well as data forwarding. ATM-IMA over PseudoWire, SAToP (like on the PDH card),
CESoP, ML-PPP can be supported by the SW application controlling the Data Path and running on a dif-
ferent MIPS processor embedded on the same chip.
The main function implemented in the confederation FPGA is the clock management.
The right-hand side is the backplane with the 1 Gb bus shared among the other slots and hence common
with the other units (PDH units and Modem units).
Figure 40. ASAP simplified block diagram

Figure 41. ASAP unit
2.8.1.6 Modem unit
FPGA
(Guinnes)
AIR FRAMER
I
PDH/Data DAC IF TX
EPS
management TX TX Q
MODULATOR DAC
IDU/ODU
communication
311 Mhz /2
MODEM
ASIC
IF cable
AIR deFRAMER interface
PDH/Data I
RPS ADC
management IF RX
RX RX
Q
DEMOD ADC
ODU/IDU
communication
126 Mhz /2
Analog Chain
GbE Serial from/to Alternate

Radio Board for RPS
Figure 42. Modem unit
In Tx direction, the MODEM unit generates the IF signal to be sent to an Outdoor Unit. Such signal
contains a Constant Bit Rate signal built with the Ethernet packets coming from the Core-E; those packets
are managed in a different way depending on their own native nature.
Digital Framer
– Classification of incoming packets from the Core-E (QoS)
– Fragmentation
– Air Frame Generation (synchronous with NE clock)
Digital Modulator

TX Analog Chain
– DAC & low pass filtering
– Modulation to 311 MHz IF TX
In Rx direction, the MODEM 300 Module terminates the IF signal coming from the ODU300 extracting
the original CBR and then the original Ethernet packets to be given the Core-E which distributes them to
the proper Module.
RX Analog Chain
– 126 MHz IF RX demodulation to I & Q
– low pass filtering & ADC
Digital Demodulator
– Carrier & CK recovery
– Equalisation
– Error Correction
Digital Deframer
– RPS (hitless)
– Defragmentation
Transmitter connected to the antenna
Figure 43. Modem unit

2.8.1.7 MPT Access Unit (with PFoE)
Digital
Processing
Figure 44. MPT Access unit (with PFoE) block diagram
The MPT Access Unit is the interface for two MPT: MPT-HC or MPT-MC.
Two MPT-HC or MPT-MC can be connected to one MPT Access unit.
The two MPT can be configured in unprotected or protected configuration.
The connection to the MPT-HC can be realized:
a) by using two connectors:

• one DC power Supply connector to send the power supply to the MPT-HC
• one Gigabit Ethernet connector (electrical or optical) to send the Ethernet traffic and the Ether-
net control frames to the MPT-HC
b) or by using only one electrical Ethernet cable with the enabling of the PFoE (Power Feed over Ether-
net) function (Ethernet traffic + Power Supply on the same cable).
If the optical port has to be used, an SFP plug-in must be installed.
N.B. If has been enabled port #1 (optical or electrical), the associated Power Supply port is #1.
N.B. If has been enabled port #2 (optical or electrical), the associated Power Supply port is #2.
The connection to the MPT-MC is realized by using only one electrical Ethernet cable with the enabling
of the PFoE (Power Feed over Ethernet) function (Ethernet traffic + Power Supply on the same cable).
Main Functions
– Provide the power supply interface and the Ethernet interface

– Provide the Power Feed over Ethernet function
– Lightning and surge protection
– Ethernet and power interface supervision

– EPS/HSB management function
– Clock distribution function
– L2 packet based Proprietary clock algorithm
– Ethernet link quality monitor function
– Radio Link Quality notification through MPR Protection Protocol frames
– Communication with Core controller for provisioning and status report.
Card Status LED (Note 1).

Indicates the status of the printed circuit board as follows:
- Off - Card not equipped, n ot provisioned or not powered
- Green Blinking - Download, software booting or flash card realigment in progress
- Green - In service, normal operation and properly provisioned
- Yellow - In stand-by, properly provisioned as EPS
- Red - Card fail
- Red Blinking - Card mismatch
Electrical GigaEth Optical GigaEth DC Power Supply
Port 1 and 2 Port 1 and 2 Port 1 and 2
RJ45 Connector. Power Emission Status LED.

Side view showing the small LED lights. Indicates output power status of ODU as follows:
- Off - No output power (eg: unit in stand-by, software
Link Indicator Activity Indicator booting or FPGA downloading in progress)
On-Link Up Blinking-Tx/Rx Activity
Off-Link Down Off-No Activity
- Green - Transmitter connected to the antenna
- Yellow - Forced squelch enabled on WebEML
Note: the current behaviour is yellow LED ON, when
the unit is in stand-by: refer to the Product Release note)
- Red - Abnormal output power (high or low limits exceeded)
Figure 45. MPT Access Unit (with PFoE)
Note 1: The GREEN and YELLOW colours of the Card Status LED have different meaning, if two
MPT (HC or MC) are connected:
– no MPT in 1+1 EPS protection is provisioned:
• YELLOW colour is not applicable (traffic impact if peripheral is plugged-out)
– 1 MPT in 1+1 EPS protection is provisioned, with mated MPT provisioned on other MPT
Access peripheral:
• GREEN if provisioned MPT is EPS Active
• YELLOW if provisioned MPT is EPS Standby (no traffic impact if peripheral is
plugged-out)
– 1 MPT in 1+1 EPS protection is provisioned, with mated MPT provisioned on other MPT
Access peripheral, 1 MPT in 1+0 is provisioned on same MPT Access peripheral:
– 2 MPTs in 1+1 EPS protection are provisioned, with mated MPTs provisioned on other
MPT Access peripheral:
• GREEN if at least one of provisioned MPT is EPS Active
• YELLOW if both MPTs are EPS Standby (no traffic impact if peripheral is plugged-
out)
– 2 MPTs in 1+1 EPS protection on the same MPT Access peripheral are provisioned:
Warning: The optional SFP plug-in, which has to be installed in the MPT Access unit, contains a Class
1 laser source. The laser source is placed in the left side of the SFP plug-in.

space.
2.8.2 DC Extractor
The DC Extractor, installed close to the MPT-HC, allows to interconnect the MSS and the MPT-HC with
a single electrical Ethernet cable by using the “Power Feed over Ethernet” solution (Ethernet traffic and
Power Supply on the same cable). The DC Extractor then separates the Power Supply from the Ethernet
traffic, which are separately sent to the MPT-HC.
The two cables, interconnecting the DC Extractor to the MPT-HC (the Power Supply cable to be connected
to the DC Out connector of the DC Extractor and Ethernet cable to be connected to the Data Out con-
nector of the DC Extractor), are provided, already terminated (2 m long), with the DC Extractor itself.
Figure 46. DC Extractor

2.8.3 ODU300
The ODUs include a waveguide antenna port, type-N female connector for the ODU cable, a BNC female
connector (with captive protection cap) for RSSI access, and a grounding stud.
The ODUs, are designed for direct antenna attachment via a 9500 MPR-E-specific mounting collar
supplied with the antennas.
ODU polarization is determined by the position of a polarization rotator fitted within the antenna mounting
collar.
A remote ODU mounting kit is also available as an option. These may be used to connect an ODU to a
standard antenna, or to a dual-polarized antenna for co-channel link operation.
ODUs are fixed for Tx High or Tx Low operation.
Where two ODUs are to be connected to a single antenna for hot-standby or frequency diversity
configurations, a direct-mounting coupler is used. They are available for equal or unequal loss operation.
Balanced loss is nominally 3 dB. Unbalanced loss is nominally 1/6 dB.
The ODU assembly meets the ASTME standard for a 2000 hour salt-spray test, and relevant IEC, UL,
and Bellcore standards for wind-driven rain.
The ODU housing comprises:
– Cast aluminium base (alloy 380)
– Pressed aluminium cover (sheet grade alloy 1050).
– Base and cover passivated and then polyester powder coated
– Compression seal for base-cover weatherproofing
– Carry-handle
Figure 47. ODU300 housing
ODUs are frequency-band specific, but within each band are capacity-independent up to their design
maximums.

2.8.3.1 ODU block diagram
Figure 48.shows the ODU block diagram.
MSS
Figure 48. ODU block diagram
The quadrature modulated 311 MHz IF signal from the MSS is extracted at the N-Plexer and passed via
a cable AGC circuit to an IQ demodulator/modulator.
Here the 311 MHz IF is demodulated to derive the separate I and Q signals using the 10 MHz
synchronizing reference signal from the MSS.
These I and Q signals modulate a Tx IF, which has been set to a specific frequency between 1700 and
2300 MHz, such that when mixed with the Tx local oscillator signal (TXLO) in the subsequent mixer stage,
provides the selected transmit frequency. Both the IF and Tx local oscillators are synthesizer types.
Between the IQ modulator and the mixer, a variable attenuator provides software adjustment of Tx power.
After the mixer, the transmit signal is amplified in the PA (Power Amplifier) and passed via the diplexer
to the antenna feed port.
A microprocessor in the ODU supports configuration of the synthesizers, transmit power, and alarm and
performance monitoring. The ODU microprocessor is managed under the NCC microprocessor, with
which it communicates via the telemetry channel.
A DC-DC converter provides the required low-voltage DC rails from the -48 Vdc supply.
In the receive direction, the signal from the diplexer is passed via the LNA (Low Noise Amplifier) to the
Rx mixer, where it is mixed with the receive local oscillator (RXLO) input to provide an IF of between 1700
and 2300 MHz. It is then amplified in a gain-controlled stage to compensate for fluctuations in receive
level, and in the IF mixer, is converted to a 126 MHz IF for transport via the ODU cable to the MSS.
The offset of the transmit frequencies at each end of the link is determined by the required Tx/Rx split.
The split options provided are based on ETSI plans for each frequency band. The actual frequency range
per band and the allowable Tx/Rx splits are range-limited within 9500 MPR-E to prevent incorrect user
selection.

A power monitor circuit is included in the common port of the diplexer assembly to provide measurement
of transmit power. It is used to confirm transmit output power for performance monitoring purposes, and
to provide a closed-loop for power level management over the specified ODU temperature and frequency
range.
2.8.3.2 RSSI Monitoring Point
The ODU has a capped BNC female connector to access RSSI during antenna alignment.
There is a linear relationship of voltage to RSSI, as shown in the table below; an RSSI of 0.25 Vdc is
equivalent to -10 dBm RSSI, and each additional 0.25 Vdc RSSI increase thereafter corresponds to a 10
dBm decrease in RSSI.
The lower the voltage the higher RSSI and better aligned the antenna is.
Table 23. RSSI Table

Units Measurement
BNC (Vdc) 0.25 0.5 0.75 1.0 1.25 1.5 1.75 2.0 2.25 2.5
RSSI (dBm) -10 -20 -30 -40 -50 -60 -70 -80 -90 -100
2.8.3.3 Waveguide Flange Data
Table 24. lists the antenna port flange types used with the ODU300, plus their mating flange options and
fastening hardware for remote mount installations.
UDR/PDR flanges are rectangular; UBR/PDR flanges are square.
On the ODU, the two flange styles are:
– UDR. 6-hole or 8-hole (6/8 bolt holes depending on frequency range/waveguide type), flush-face
flange with threaded, blind holes.
– UBR. 4-hole flush-face flange with threaded, blind holes.
The corresponding mating flange styles are:
– PDR. 6-hole or 8-hole flange with gasket groove and clear holes.
– PBR. 4-hole flange with a gasket groove and clear holes.
All fastening hardware is metric.

Table 24. Waveguide Flange Data
Freq Radio Waveguide Waveguide Spring Bolts Bolt Thread Hole Bolt Length
Band Flange Mating Type Washers Reqd Type Spec Depth Required
Flange Reqd mm
6 GHz UDR70 PDR70 WR137 8 x M5 8 M5x0.8 6H 10 Flange thickness +
Hole depth - 2mm
7/8 GHz UDR84 PDR84 WR112 8 x M4 8 M4x0.7 6H 8 Flange thickness +
Hole depth - 2mm
10/11 GHz UDR100 PDR100 WR90 8 x M4 8 M4x0.7 6H 8 Flange thickness +
Hole depth - 2mm
13 GHz UBR120 PBR120 WR75 4 x M4 4 M4x0.7 6H 8 Flange thickness +
Hole depth - 2mm
15 GHz UBR140 PBR140 WR62 4 x M4 4 M4x0.7 6H 8 Flange thickness +
Hole depth - 2mm
18/23/26 UBR220 PBR220 WR42 4 x M3 4 M3x0.5 6H 6 Flange thickness +
GHz Hole depth - 2mm
28/32/38 UBR320 PBR320 WR28 4 x M3 4 M3x0.5 6H 6 Flange thickness +
2.8.3.4 ODU Coupler
The ODU coupler is used in the 1+1 HSB or 1+1/2x(1+0) FD co-polar configurations.
The coupler can be equal type (3 dB/3 dB insertion loss) or unequal type (1.5 dB on the main path/6 dB
on the secondary path).
The couplers are connected between the cabinets and the antenna.

2.8.4 MPT-HC
MPT-HC (Microwave Packet Transport) is a Microwave Equipment capable to transport the Ethernet traf-
fic over an RF radio channel.
The MPT-HC includes a waveguide antenna port, type-N female connector for the DC connection, a main-
tenance connector (with captive protection cap) for RSSI access, 1 electrical GE interface, 2 GE optical
interfaces (1 for data, 1 for for RPS) and a grounding stud.
The MPT-HC can be installed on an integrated antenna or on standard poles, wall or pedestal mount, with
an appropriate fastening system.
The MPT-HC (one or two depending on the configuration 1+0 or 1+1, each one with a solar shield) incor-
porates the complete RF transceiver and can be associated with an integrated or separate antenna.
The cabinet is a very compact and robust weatherproof (IP 67) container, designed to be compatible with
hot and very sunny climatic zones.
The MPT-HC can be rapidly installed on standard poles with an appropriate fastening system. The pole
mounting is the same for 1+0 or 1+1 configurations from 6 to 38 GHz.
The MPT-HC is fixed by means of quick latches. This system allows to change the MPT-HC without alter-
ing antenna pointing.
For 6 GHz & 7/8 GHz, the MPT-HC polarization is determined by the rotation of the MPT-HC in 1+0 con-
figuration and by the position of a polarization rotator fitted within the coupler in 1+1 configuration.
For 11 GHz to 38 GHz, the MPT-HC polarization is determined by the rotation of the nose fitted in the
antenna port of the MPT-HC in 1+0 configuration and by the position of a polarization rotator fitted within
the coupler in 1+1 configuration.
Where two MPT-HC have to be connected to a single antenna for hot-standby or frequency diversity con-
figurations, a direct-mounting coupler is used. They are available for equal or unequal loss operation.
Equal loss is nominally 3 dB. Unequal is nominally 1/10 dB.
Three mechanical solutions are adopted:
[1] with embedded diplexer for cost optimisation (11 GHz to 38 GHz), where the branching (diplexer)
is internal to the MPT-HC cabinet; this type of MPT-HC is identified by one Logistical Item only;
[2] with embedded diplexer for cost optimisation and different mechanics from 11-38 GHz (6 GHz),
where the branching (diplexer) is internal to the MPT-HC cabinet; this type of MPT-HC is identified
by one Logistical Item only;
[3] with external diplexer: due to a very high number of shifters the diplexer is external for the flexibility
of the shifter customization (7 GHz and 8 GHz), where MPT-HC is composed by two independent
units: the BRANCHING assembly (containing the diplexer) and the RF TRANSCEIVER assembly
(containing the RF section); each of this type of MPT-HC is identified by two Logistical Items, one
for the BRANCHING assembly and another for the RF TRANSCEIVER assembly. To read the
BRANCHING assembly identification label it is necessary to separate the BRANCHING assembly
from the RF TRANSCEIVER assembly.

MPT-HC is broken down to the following sections:
– MPT-CB: Common Belt section. This section is Frequency independent, and all the features relevant
to this unit are common to all the MPT RF options.
– MPT-RF: Radio Frequency section that is frequency dependent.
Figure 49. MPT system
The MPT-HC interface is based on a Gb Ethernet, that can be either optical or electrical depending on
the needs and the cable length. If the optical port has/have to be used (data and/or RPS port), the cor-
responfing SFP plug-in must be installed by opening the Cobox.
Figure 50. 11-38 GHz MPT-HC housing
Figure 51. 6 GHz MPT-HC housing

Figure 52. 7-8 GHz MPT-HC housing
2.8.4.1 MPT-HC block diagram
Figure 53. MPT-HC block diagram

2.8.4.1.1 Common Belt section
The Common Belt section is frequency independent. It is the digital section of the MPT-HC.
The main functions are the following:
1) Interfaces the MSS for traffic transport and MSS communication messages in both directions,
through one Gigabit Ethernet optical or electrical cable.
2) Micro-Processor for
– Indoor - MPT-HC dialogue

– Inter-MPT-HC dialog in 1+1 configurations
– HW configuration and monitoring of all MPT-HC parts
– Dynamic regulation process such as ATPC
3) Transport of the system reference clock (synchronisation)
4) Switches the traffic and management to the correct port (processor port, radio port)
5) Performs traffic adaptation if needed
6) Performs Quality of Service and policing on flow to be sent over the radio link.
7) Modulation and demodulation of the resulting modem frame
8) In 1+1 configuration manages the switching, forwarding received modem frame to the second
MPT-HC and sending built modem frame to the second MPT-HC.
Power supply interface
It is provided by a "N" 50 ohms connector, with the positive to ground.
The power supply is coming from the MSS in the range of -40,5 V to -58 V. MPT-HC input voltage range
is from -28 V to -58 V.
Lightning protection
The lightning protection is internal to the MPT-HC. No external protection must be used.
This protection applies to:
– the Ethernet electrical cables
– the power supply coax cable
INCA module
The INCA module hosts the physical Ethernet interfaces:
– One optical SFP device for traffic interface.
– One electrical device for traffic interface.
– One optical SFP device for 1+1 protection interface with the associated MPT-HC.
In order to reach 500m the MPT-HC uses an SFP multimode 805 nm with a 50/125 fibre.

Tx Side
Following the flow from user Ethernet port to radio, the section performs:
– Reception of incoming Ethernet frames from the optical or electrical user interface (through INCA)
– Recovery of the clock coming from the MSS
– Management of the 1+1 EPS protection layer 2 messages
– Switch of the management frames from user port to internal processor
– Generation of MPT-HC to MPT-HC messages needed for radio link (ATPC, ACM, ...)
– Compression of the TDMoEth frames header (TDM2TDM - MEF8, TDM2ETH - MEF8)
– Management of the Quality of Service
– Fragmentation of the Ethernet frames
– Shaping of the traffic to adapt it to radio bandwidth
– Tx Modem frame building
– In 1+1, duplication of the built Tx modem frame and sending to the second MPT-HC through the pro-
tection coupling port
– In 1+1, reception of the Tx modem frame coming from the second MPT-HC
– In 1+1, switch of the Tx modem frame between the local and the one coming from second MPT-HC
depending on the EPS position
– Tx Radio frame building (FEC, pilots, ...)
– Synchronisation of the symbol rate to the MSS recovered clock
– Modulation in I and Q analogue signals to be sent to the RF section.
Rx Side
Following the flow from radio to user Ethernet port, the section performs:
– Reception of the I and Q analogue signals coming from the RF section
– Demodulation of the Rx radio frame into Rx modem frame
– In 1+1, Recovery of the symbol clock and duplication to the second MPT-HC
– In 1+1, duplication of the Rx modem frame and sending to the second MPT-HC through the protec-
tion coupling port
– In 1+1, reception of the Rx modem frame coming from the second MPT-HC
– In 1+1, hosts the RPS decision machine
– In 1+1, switch of the Rx modem frame between the local and the one coming from second MPT-HC
depending on the traditional RPS position and the modem frames quality
– Enhanced RPS

– In 1+1, switch of the recovered clock between the local and the one coming from second MPT-HC
depending on the traditional RPS position
– Deframing of the Rx modem frame
– Re-assembly of fragmented Ethernet frame
– Decompression of TDMoEth frames header
– Extraction of MPT-HC to MPT-HC messages needed for radio link (ATPC, ACM, ...)
– Management of service channels frames
– Switch of the management frames from internal processor to user port.
– Management of the 1+1 EPS protection layer 2 messages
– Send the recovered clock to the MSS
– In 1+1 EPS, transmit or not the Ethernet frames to the MSS depending on the EPS position
2.8.4.1.2 RF Section
There are two architectures, the difference between these two architectures are only on Rx side:
– For the first one (used in MPT-HC band 7/8 GHz) there are only two frequency conversions between
RF input frequency and base band frequency
– For the second one (used for all other MPT-HC bands) there are three frequency conversions
The block diagrams of these two architectures are shown hereafter.
Figure 54. 7/8 GHz MPT-HC architecture

Figure 55. 11 to 38 GHz MPT-HC architecture
Main Functions
1. TX block:
• IF TX Quadrature modulator
• IF_Tx Synthesizer
• RF Up-Converter
• Output power management
2. Tx_Rx Common block:
• RF_LO Synthesizer
3. Rx block:
• LNA
• RF Down Converter
• First IF amplification and overload management
• First IF down conversion
• Second IF amplification and filtering (not present in 7/8 GHz)
• Quadrature demodulator
• Base band filter and AGC loop

2.8.4.2 RSSI Monitoring Point
The RSSI is available on the maintenance LEMO connector and is used to manually point the antenna
on the field.
The higher the voltage the higher RSSI and better aligned the antenna is.
Table 25. RSSI Table
Units Measurement (with MPT-HC)
BNC (Vdc) 5 4.71 4.12 3.5 2.9 2.3 1.71 1.11 0.59 0.14
RSL (dBm) -10 -20 -30 -40 -50 -60 -70 -80 -90 -100
2.8.4.3 Waveguide Flange Data

L6 U6 7 8 11 13 15 18 23 26 38
Waveguide GHz GHz GHz GHz GHz GHz GHz GHz GHz GHz GHz
Type
WR137 WR137 WR113 WR113 WR75 WR62 WR62 WR42 WR42 WR42 WR28
2.8.4.4 MPT-HC Coupler
The coupler is used in the 1+1 HSB or 1+1/2x(1+0) FD co-polar configurations.
The coupler can be equal type (3 dB/3 dB insertion loss) or unequal type (1 dB on the main path/10 dB
The couplers are connected between the MPT and the antenna.

2.8.5 MPT-HC V2
MPT-HC V2 is similar to MPT-HC from architecture standpoint and can be used as spare part of the MPT-
HC. The differences vs MPT-HC are:
– MPT-HC V2 can be natively Ethernet powered through a proprietary PFoE
– MPT-HC V2 is capable to host external modules (RPS module or XPIC_RPS module)
N.B. With release MPR3.0, the presence of one of the 2 modules is mandatory.
Two mechanical solutions are adopted:
[1] with embedded diplexer for cost optimisation (6 GHz and 11 GHz to 38 GHz), shown in Figure 56.,
where the branching (diplexer) is internal to the MPT-HC V2 cabinet; this type of MPT-HC V2 is iden-
tified by one Logistical Item only;
[2] with external diplexer: due to an high number of shifters the diplexer is external for the flexibility of
the shifter customization (7 GHz and 8 GHz), where MPT-HC V2 is composed by two independent
(containing the RF section); each of this type of MPT-HC V2 is identified by two Logistical Items,
one for the BRANCHING assembly and another for the RF TRANSCEIVER assembly. To read the
Figure 56. MPT-HC V2 housing (6 GHz and 11 GHz to 38 GHz)

2.8.6 MPT-MC
MPT-MC is similar to MPT-HC from architecture standpoint. MPT-MC has limited capacity vs MPT-HC and
is natively Ethernet powered.
[1] with embedded diplexer for cost optimisation (6 GHz and from 11 GHz to 38 GHz), where the
branching (diplexer) is internal to the MPT-MC cabinet; this type of MPT-MC is identified by one
Logistical Item only;
[2] with external diplexer: due to a vary high number of shifters the diplexer is external for the flexibility
of the shifter customization (7 GHz and 8 GHz), where MPT-MC is composed by two independent
(containing the RF section); each of this type of MPT-MC is identified by two Logistical Items, one
for the BRANCHING assembly and another for the RF TRANSCEIVER assembly. To read the
Figure 57. 6 GHz and from 11 to 38 GHz MPT-MC housing
Figure 58. 7-8 GHz MPT-MC housing

2.8.6.1 MPT-MC Coupler
The coupler is used in the 1+1 HSB configuration.
The coupler can be equal type (3 dB/3 dB insertion loss) or unequal type (1 dB on the main path/10 dB
The couplers are connected between the MPT and the antenna.

2.8.7 Protection schemes
2.8.7.1 Protection schemes with ODU300
Supported Protection types:
[1] RPS (Radio Protection Switching) Hitless for each radio direction (RPS-RX)
• RPS is distributed in 9500 MSS modules before termination of 9500 MSS frame.
[2] EPS (Equipment Protection Switching) for each module type

• Both Working and Spare modules send its own signal to the Core-E. Core-E selects the best
signal.
[3] HSB-TPS (Hot StandBy - Transmission Protection Switch)

• Spare ODU module is squelched.
2.8.7.1.1 RPS Switching Criteria
The switching criteria are:
– SF (Signal Fail): generated from transmission and equipment alarms affecting the Rx radio section:
– Demodulator Fail
– IDU-ODU cable loss
– LOF of aggregate signal radio side
– Main and spare ODU, IDU HW failures (card fail)
– HBER (high BER)
– EW (Early Warning)
2.8.7.1.2 EPS Switching Criteria
– Peripheral Card Fail (switching off of the peripheral included)
– Peripheral Card Missing
– LOS of all the tributaries (of course only in case of PDH local access peripheral protection) managed
via SW.
2.8.7.1.3 HSB Switching Criteria
– Radio Interface Peripheral Card Fail (switching off of the peripheral included)
– Radio Interface Peripheral Card Missing
– MSS-ODU cable loss
– ODU TX chain alarm (this is an OR of the following alarms: LOS at ODU input, modFail, txFail, ODU
card fail).

2.8.7.2 Protection schemes with MPT-HC/MPT-HC V2
To implement the 1+1 configuration an optical cable must be connected from one MPT-HC/MPT-HC V2
to the second MPT-HC/MPT-HC V2. In Figure 59 Ethernet port 2 of one MPT-HC/MPT-HC V2 is
connected to Ethernet port 2 of the second MPT-HC/MPT-HC V2.
N.B. In Figure 59 the two MPT are connected to two different MPT Access units, but they can also
be connected to the same MPT Access Unit.
[1] RPS (Radio Protection Switching) Hitless for each radio direction
• RPS is implemented directly on the two MPT-HC/MPT-HC V2.
[2] EPS (Equipment Protection Switching) for the MPT-HC/MPT-HC V2

• EPS protects the MPT-HC/MPT-HC V2 and the cables connecting it to the MSS.

Figure 59. MPT-HC/MPT-HC V2 protection schemes

2.8.7.2.1 RPS Switching Criteria
– SF (Signal Fail): generated from transmission and equipment alarms affecting the Rx radio section
– Rx Fail
– Demodulator Fail
– LOF of aggregate signal radio side
– inter-MPT coupling link failure
– HBER (high BER) based on the demodulated erroneous blocks ratio
– EW (Early Warning) based on MSE
Moreover, MPT-HC supports a further embedded functionality called "Enhanced RPS". Enhanced RPS
is a frame-based protection mechanism, aimed to reach a quick reaction time and increasing significantly
the quality of the radio interface in the Rx side. It assumes the alignment between the 2 received radio
channels and it is based on frame by frame selection of the "best" frame between the frames received
from the Main and the Spare radio channel. The Enhanced RPS assumes that the "classical" RPS criteria
are used to give indication about the "preferred" channel, whose frame has to be selected, when the
frame-based choice between the 2 streams is not possible (e.g. due to the frame alignment error). The
Enhanced RPS switching criterion depends on the presence of errors in the decoded LDPC word.
– MPT Access Card Fail status

– IDU-ODU Connection Failure
– ICP alarm
– Mated MPT Access card Failure

– ICP alarm
– Incompatible Shifter alarm
– Incompatible Frequency alarm
– Incompatible Power alarm
– Incompatible Modulation Parameters alarm
– Inter-MPT coupling link failure. Where there is a cross configuration (EPS on Spare & TPS on main),
HSB (TPS) will switch and align with EPS position, if there is an inter-MPT coupling link failure.

2.8.7.3 Protection schemes with MPT-MC
N.B. In Figure 60 the two MPT are connected to two different MPT Access units, but they can also
be connected to the same MPT Access Unit.
[1] EPS (Equipment Protection Switching) for the MPT-MC

• EPS protects the MPT-MC and the cables connecting it to the MSS.

Figure 60. MPT-MC protection schemes
N.B. Since there is no coupling link in the curren release the TPS Operator Commands are not sup-
ported.
Only Operator Commands for EPS are supported.


– ICP alarm

– ICP alarm
– Incompatible Shifter alarm
– Incompatible Frequency alarm
– Incompatible Power alarm
– Incompatible Modulation Parameters alarm
2.8.7.4 Core-E protection
The logic of this protection is distributed in each access and radio peripheral unit. All the switching criteria
coming from both the Core units, are available (via backpanel) to each peripheral in order to allow to each
logic to take the same decision.
Both the Cores (main and spare) send their signals to all the traffic peripherals.
Core protection supports two different types of protection:
– Traffic/services protection (protection of all the transport functions with the exception of the control
platform)
– Control Platform protection
In order to provide this protection the Flash Cards on the two Core boards are kept aligned (in terms of
SW and configuration data) both in case of new operations done by the management systems and in case
of Flash Card replacement.
User Ethernet interfaces protection
In order to support User Ethernet interfaces protection using an external device, the User Ethernet ports
of the Core in standby status are switched off.
The switch on of the User Ethernet interfaces when the Core in standby status becomes active, due to
operator commands or automatic switch, is done within few seconds. In case of Optical Ethernet interface,
the Lambda, Link Length, Connector and Gigabit Ethernet Compliance Code information are read from
the active Core.

TMN Local Ethernet interface protection
In order to support TMN Local Ethernet interface protection using an external device, the relevant Ethernet
port of the Core in standby status is switched off.
The switch on of the TMN Local Ethernet interface when the Core in standby status becomes active, due
to operator commands or automatic switch, is done within 5 seconds.
In order to avoid impact on the Core, the external device used for the TMN Local Ethernet interface pro-
tection is kept separate from the one used for protection of User Ethernet interface.
External synchronization interface protection
The Protection of the external synchronization interface is supported. The output port on the stand-by
Core is muted.
Node-Timed PDH interface protection
In case of node-timed PDH interface the protection of the NE Clock provided by Core is supported.
Core protection restoration mode
The restoration mode is always non revertive: the Core main becomes active as soon as it has recovered
from failure or when a switch command is released.
2.8.7.4.1 Core-E protection Switching Criteria
– Core Card Fail

– Core Card Missing
– Control Platform operational status failure
– Flash Card realignment in progress
– Flash Card failure
If the “Ethernet LOS Criteria” feature has been enabled the following additional switching criteria are
added:
– Card Fail of SFP optical module

– Card Missing of SFP optical module
– LOS of any Electrical User Ethernet interfaces, including the LOS of the forth User Ethernet interface
working as TMN Local Ethernet interface.
N.B. In case of stand-by Flash Card realignment in progress, the application SW refuses/removes
a manual switch command.
2.8.7.4.2 Port #5 and port #6 protection
– If in the Port #5 and/or port #6 a 2xE1 SFP or EoSDH SFP has been installed, the protection is
implemented by using special splitters (refer to paragraph 4.1.10.3 on page 634 and paragraph
4.1.10.4 on page 634).

2.8.8 Radio Transmission Features with ODU300
2.8.8.1 Frequency Agility
The Frequency Agility feature gives the Operator the possibility to set via ECT the frequency of a single
Transceiver within a chosen sub–band to select the RF working channel. This implies benefits for spare
parts, order processing and frequency co–ordination.
2.8.8.2 Automatic Transmit Power Control (ATPC)
The Automatic Transmit Power Control (ATPC) function automatically increases or decreases the trans-
mit output power upon request from the opposite terminal. The opposite terminal constantly monitors
Receive Signal Level (RSL), receive signal quality, and aggregate Bit Error Rate (BER) of the receive sig-
nal.
When ATPC Enabled is checked on the Modem Card Settings screen, the transmit output will remain at
it's lowest level until a fade occurs (or a receive circuit alarm is detected). When the change in RSL is
detected at the receive end, a command is sent to the transmit end to increase power in 1 dB steps to
it's highest level. After the fade is over, the receive end commands the transmit power to decreases in 1
dB steps to the lowest level.
The ATPC range (high and low limits) is variable, determined by link distance, link location, and link fre-
quency. When ATPC Enabled is checked, the range values are shown in parenthesis (minimum - maxi-
mum) following ATPC Range.
When ATPC Enabled is not checked on the Modem Card Settings screen, the transmit output will always
operate at it's highest level.
2.8.8.3 Transmitted power control: RTPC function
The capability to adjust the transmitted power in a static and fixed way (RTPC = Remote Transmit Power
Control) has been introduced for those countries where, due to internal rules, the ATPC function is not
accepted or for those hops in which due to the short length and interface problems, a fixed reduced
transmitted power is preferred. The range of the possible attenuation depends on the frequency band
involved. The setting of the transmitted power can be performed locally through ECT.
Output power is band and modulation dependent.
2.8.8.4 Power Monitoring
The ODU300 incorporates a detector for Tx power measurement. It is used to provide measurement of
forward power as a performance parameter, and to provide a calibration input for transmitter operation
over temperature and output range.
Viewed Tx power ranges always match the capabilities of the ODU300 for a given modulation. When
modulation is changed, the WebEML automatically adjusts/restricts Tx Power to be within valid range.
2.8.8.5 Adaptive Equalization
Adaptive equalization (AE) is employed to improve reliability of operation under dispersive fade
conditions, typically encountered over long and difficult paths.

This is achieved through a multi-tap equalizer consisting of two registers, one with feed-forward taps, the
other with feed-back taps. Each of these registers multiply successive delayed samples of the received
signal by weighting-coefficients to remove propagation induced inter-symbol interference.
2.8.8.6 Link identifier
The amount of microwave links, especially in urban areas puts the problem of possible interferences
during installation and turn-on phase.
The digital frame incorporates link identity coding capabilities to prevent the capture of an unwanted
signal.
Link identifier management can be enabled or disabled by the management systems.
2.8.8.7 Loopbacks with ODU300
To facilitate the installation/commissioning and the remote maintenance one loopback is available.
As the activation of a loopback affects the traffic, the presence of a loopback is indicated to the
management systems as an abnormal condition.
The loopback is "loop and cut" type (the signal sent after the loopback execution is the same signal sent
back).
The loopback supported by the Radio board is shown in the following figure.
PDH board RADIO board
CORE MODEM
LIU FPGA FPGA SWITCH FPGA
NxE1 SerDes
Figure 61. Available loopbacks
1) IF Radio loopback: is implemented in the analog IF part of the ODU300 Radio Module, the traffic
received from switch side is redirected toward the switch itself; this loopback can be activated
only on the aggregate traffic. When this loop is enabled the behaviour is the following:
– TDM2TDM flows: before transmitting the packets towards the switch, the FPGA looking
the VLAN will rebuild the right Ethernet header.
– TDM2ETH flows: before transmitting the packets towards the switch, the FPGA looking
the VLAN will rebuild the right Ethernet header.
– The Ethernet flows are dropped.

2.8.9 Radio Transmission Features with MPT-HC/MPT-HC V2/MPT-MC
2.8.9.1 Frequency Agility
The Frequency Agility feature gives the Operator the possibility to set via ECT the frequency of a single
Transceiver within a chosen sub–band to select the RF working channel. This implies benefits for spare
parts, order processing and frequency co–ordination.
2.8.9.2 Automatic Transmit Power Control (ATPC)
The Automatic Transmit Power Control (ATPC) function automatically increases or decreases the trans-
mit output power upon request from the opposite terminal. The opposite terminal constantly monitors
Receive Signal Level (RSL), receive signal quality, and aggregate Bit Error Rate (BER) of the receive sig-
nal.
When the ATPC is Enabled the transmit output will remain at it's lowest level until a fade occurs (or a
receive circuit alarm is detected). When the change in RSL is detected at the receive end, a command
is sent to the transmit end to increase power in 1 dB steps to it's highest level. After the fade is over, the
receive end commands the transmit power to decreases in 1 dB steps to the lowest level.
The ATPC range (high and low limits) is variable, determined by link distance, link location, and link fre-
quency. When ATPC Enabled is checked, the range values are shown in parenthesis (minimum - maxi-
mum) following ATPC Range.
When the ATPC is disabled the transmit output will always operate at it's highest level.
2.8.9.3 Transmitted power control: RTPC function
The capability to adjust the transmitted power in a static and fixed way (RTPC = Remote Transmit Power
Control) has been introduced for those countries where, due to internal rules, the ATPC function is not
accepted or for those hops in which due to the short length and interface problems, a fixed reduced
transmitted power is preferred. The range of the possible attenuation depends on the frequency band
involved. The setting of the transmitted power can be performed locally through ECT.
Output power is band and modulation dependent.
2.8.9.4 Power Monitoring
The MPT-HC/MPT-HC V2 incorporates a detector for Tx power measurement. It is used to provide

measurement of forward power as a performance parameter, and to provide a calibration input for
transmitter operation over temperature and output range.
Viewed Tx power ranges always match the capabilities of the MPT-HC/MPT-HC V2 for a given
modulation. When modulation is changed, the WebEML automatically adjusts/restricts Tx Power to be
within valid range.
2.8.9.5 Adaptive Equalization
Adaptive equalization (AE) is employed to improve reliability of operation under dispersive fade
conditions, typically encountered over long and difficult paths.

This is achieved through a multi-tap equalizer consisting of two registers, one with feed-forward taps, the
other with feed-back taps. Each of these registers multiply successive delayed samples of the received
signal by weighting-coefficients to remove propagation induced inter-symbol interference.
2.8.9.6 Link identifier
The amount of microwave links, especially in urban areas puts the problem of possible interferences
during installation and turn-on phase.
The digital frame incorporates link identity coding capabilities to prevent the capture of an unwanted
signal.
In case of “Link Identifier Mismatch” all the traffic is dropped.
The Link identifier management can be enabled or disabled by the management systems.
2.8.9.7 Loopbacks with MPT-HC/MPT-HC V2/MPT-MC
To facilitate the installation/commissioning and the remote maintenance one loopback is available.
As the activation of a loopback affects the traffic, the presence of a loopback is indicated to the
management systems as an abnormal condition.
The loopback is "loop and continue" type (the signal sent after the loopback execution is the same signal
sent back).
The loopbacks supported are shown in the following figure.
MPT Access
PDH board board MPT-HC
LIU CORE
NxE1 FPGA FPGA SerDes FPGA FPGA
SWITCH
1 2
Figure 62. Available loopbacks
1) Core facing radio loopback: this loopback routes data from the output of the Tx Data Awareness
block (after compression) to the input of the Rx data awareness (decompression).
This is an internal loopback provided by the MPT FPGA.
It is a Loop and Continue. It is possible to enable this loopback only at aggregate level.
When this loopback is activated the behavior is the following:
– Compressed flows (TDM2TDM,TDM2ETH and ATM PW) are forwarded back to Core
module with proper assignment of source and destination MAC addresses (e.g. incoming
MAC SA is used as MAC DA for looped frame, while MAC SA in the looped frame is the
MAC assigned to slot hosting radio card).
– For TDM2ETH flows the loopback works only if the ECID Tx and ECID Rx are the same,
in case of ECID Tx is different form ECID Rx the loopback doesn't work.
– For ATM PW flows the loopback works only if the Inbound and Outbound PW Labels are
the same, in case they are different the loopback doesn't work.

– Generic Ethernet flows are dropped.
The Core facing radio loopback operation implies the "Automatic Tx mute" before the execution
of the command and the "Tx mute removal" after the execution of the loopback command.
2) Radio facing Circuit loopback: remote loopback allows an over-the-air loopback test to be per-
formed when the modem is operating in a continuous mode.
The loopback is internally provided by the MPT FPGA and connects the Receive data interface
to the Transmit data interface.
This is a line external loopback. This loopback is a Loop and Continue.
It is possible to enable this loopback only at aggregate level.
When this loop is enabled the expected behavior is the following:
– Compressed flows (TDM2TDM,TDM2ETH and ATM PW) are forwarded back to Core
module with proper assignment of source and destination MAC addresses (e.g. incoming
MAC SA is used as MAC DA for looped frame, while MAC SA in the looped frame is the
MAC assigned to slot hosting radio card).
– For TDM2ETH flows the loopback works only if the ECID Tx and ECID Rx are the same,
in case of ECID Tx is different form ECID Rx the loopback doesn't work.
– For ATM PW flows the loopback works only if the Inbound and Outbound PW Labels are
the same, in case they are different the loopback doesn't work.
– Generic Ethernet flows are dropped.
2.8.9.8 Loopback activation
The loopback can be activated by each management system (local or remote). The activation command
permits to define the duration of the loopback (time-out).
The two loopbacks (Core facing and Radio facing) cannot be supported at the same time.
The time-out period starts at the activation time and expires at the end of the period spontaneously in the
NE, a part for the case in which another reconfiguration of the time-out period is requested at the operator
interface during the activation time. In this case, if the loopback point is still active because the activation
time-out is not expired yet, the time-out period is reconfigurable and the specified time range starts again
from the new updated activation date, overwriting the previous activation date and time-out values.
2.8.9.9 Loopback life time
In order to avoid the risk of a permanent disconnection from ECT/NMS of a remote NE after the execution
of a loopback, a time-out mechanism is supported.
The management system's operator has to provide the time range of the loopback time-out period
expressed in hours/minutes starting from the time of the loopback activation.
A default time-out period may be suggested at the operator interface, even if it could be modified on user-
needs basis.
After the NE reset, the activation of each loopback point is lost and must be recreated again if needed,
starting with a new time-out period.

2.8.10 TMN interfaces
On 9500 MPR-E Network Element the following types of TMN communication interfaces are present:
– TMN channel carried by Ethernet frames in the dedicated TMN port (on the front panel of the Core-
E module) (this port is normally used to connect the WebEML);
– TMN channel carried up to 512 kbit/s channel inside Radio frame;
– TMN channel carried by Ethernet frames in User Ethernet port# 4 (on the front panel of the Core-
E module);
– Two TMN In-band interfaces (by using the Ethernet traffic ports).
2.8.11 Admission control in Adaptive Modulation (only with ODU300)
Note
With the MPT-HC or MPT-HC V2 or MPT-MC the Admission Control is always enabled (and cannot be
disabled). The totat available capacity is the capacity available with the minimum modulation scheme.
2.8.11.1 What does “Admission Control” mean?
The Admission Control is a feature that is available only when operating in Adaptive modulation. It ensures
that the requested TDM flows are kept when the modulation scheme is downgraded automatically by the
system due to the degraded propagation condition.
The Admission Control check is optional: from WebEML, it is possible to decide to enable or not the admis-
sion control check (default value is Enabled).
2.8.11.2 Radio capacity in case of adaptive modulation
When the terminal operates in adaptive modulation, it is possible to commission a total capacity of both
Ethernet and TDM traffic, up to a bandwidth corresponding to the maximum modulation scheme chosen
by the operator. The Table 2. summarizes the E1 equivalent capacity supported by the MPR when using
the adaptive modulation. This capacity depends on the channel spacing and the modulation scheme.
2.8.11.3 Adaptive modulation and admission control enabled
The Admission Control feature allows the operator to protect the TDM traffic when this kind of traffic is
provisioned.
When admission control is enabled (default operator choice), the whole TDM traffic is kept. The maximum
number of E1 links that can be provisioned (or cross-connected in a given radio direction) is the one that
is fitting with 4QAM capacity.
N.B. There is no possibility to provision a number of E1s greater than the one fitting in 4QAM mod-
ulation. Indeed, as all the E1 links have the same priority, it is not possible from a system point
of view to decide "which" E1s should be dropped when the modulation scheme is downgraded
from 16QAM to 4QAM. To secure provisioning and commissioning operations, the admission
control check at WebEML level has been inserted, avoiding a possible mistake from the user
to provision a number of E1s that are not fitting inside 4QAM bandwidth.

Depending on the channel spacing value, the maximum number of E1 that can be provisioned is (refer
to Table 2.):
– Channel spacing of 7 MHz: 4 x E1
The remaining capacity is devoted to other types of traffic such as Ethernet best effort.
When RSL (received signal level) value decreases, modulation scheme is downgraded first from 64QAM
to 16QAM: the traffic with lower priority exceeding 16QAM bandwidth is dropped and all the E1s are kept.
As soon as the RSL value further decreases, modulation scheme is downgraded to 4QAM and the whole
traffic exceeding 4QAM bandwidth is dropped while the E1s are kept.
Figure 63., Figure 64. and Figure 65. here below show how the system operates, in case of modulation
changes when admission control is enabled (case of 28 MHz bandwidth).
Figure 63. Example of traffic in case of 28MHz bandwidth and Admission Control Enabled
In this case, the operator has commissioned 13xE1’s and enabled the Admission Control. There are two
other kinds of traffic provisioned, Ethernet traffic #1 and Fast Ethernet traffic #2. Furthermore, Ethernet
traffic #1 has a higher priority than Fast Ethernet traffic #2.
The 13xE1’s are saved even in the case of a degradation of the modulation down to 4QAM. Remaining
available capacity is used to transmit other kinds of traffic.
When the modulation is degraded from 64QAM to 16QAM (Figure 64.), the E1 flows are kept whilst the
Ethernet traffic with lowest priority (Fast Ethernet traffic #2) is reduced.

Figure 64. Example of traffic in case of 28MHz bandwidth and modulation downgraded to 16QAM
When the modulation is further degraded to 4QAM (Figure 65.), the E1 flows are still kept whilst the Ether-
net traffic with the lowest priority is dropped (Fast Ethernet traffic #2) and the Ethernet traffic with the high-
est priority is reduced (Ethernet traffic #1) to fit the remaining available bandwidth.
2.8.11.4 Adaptive modulation and admission control disabled
The E1 flows are no more guaranteed traffic when the operators disable the admission control. The max-
imum number of E1 links that can be cross-connected into a given radio direction is the one that is fitting
with 16QAM capacity but without any survival when the modulation scheme is degraded.
N.B. As all the E1 links have the same priority, it is not possible, from a system point of view, to decide
"which" E1’s should be dropped when the modulation scheme is degraded from 16QAM to
4QAM. To secure provisioning and commissioning operations, the admission control check
at WebEML level has been inserted, avoiding a possible mistake from the user to provision a
number of E1’s that are not fitting inside16QAM bandwidth.

Depending on the channel spacing value, the maximum number of E1’s that can be provisioned is (refer
to Table 2.):
The remaining capacity is devoted to other types of traffic such as Ethernet best effort.
When RSL (received signal level) value decreases, the modulation scheme is downgraded first from
64QAM to 16QAM and all E1 flows are kept because there is enough bandwidth to transmit them. When
the modulation further degrades to 4QAM, all E1 flows are dropped because there is no way to define any
kind of priority among them. The remaining bandwidth is filled with other traffics.
N.B. It might happen that some E1(s) are temporarily up and transmitting, but this is a random behav-
iour without any predefined mechanism, there is no control at all performed on the E1 links.
This feature addresses the need of transmitting a high number of E1’s, without giving up the benefits of
adaptive modulation for Ethernet traffic.
Figure 66., Figure 67. and Figure 68. show how the system operates in case of modulation changes when
admission control is disabled (case of 28 MHz bandwidth).
Figure 66. Example of traffic in case of 28MHz bandwidth and Admission Control Disabled
In this case, the operator has commissioned 32xE1’s and chosen to disable the Admission Control. These
32 xE1’s are kept as long as the modulation scheme is degraded down to 16QAM.
Other kinds of traffic are transmitted according to the available capacity and the priority defined beyond
them.
When the modulation is downgraded to 16QAM, all E1 flows are kept whilst the other traffic is reduced.

When the modulation is further degraded to 4QAM, all E1 flows are dropped whilst the other traffic is
reduced to fit the remaining available bandwidth.

2.8.12 Managed Services and profiles
Here below the association of managed services and profiles:
– TDM to TDM – This is the typical service associated to a traditional TDM network in which E1 traffic
is transported, switched and terminated inside a MPR network.
– TDM to ETH – This is the service allowing the TDM traffic to be aggregated and output in a single
ETH stream. On this service specific algorithms are applied in order the E1 is transported, switched
and provided to an external ETH network in standard format (MEF-8).
– SDH to SDH – This is the typical service associated to a traditional SDH transport network. STM-
1 traffic is transparently transported, switched and terminated inside a MPR network.
– ETH to ETH – This is not a real CES due to the native IP architecture of MPR. Ethernet traffic is
directly managed by the L2 switch on the Core board, thanks to the auto-learning algorithm, VLANs
etc.
– ATM to ATM – This profile allows the management of the ATM services inside a 9500 MPR network.
E1s IMA/ATM are terminated/reconstructed at the borders of the 9500 MPR cloud; encapsulation/
extraction of ATM streams into/from ATM PW packets is performed according to RFC 4717.
– ATM to ETH – This profile allows the ATM service to be terminated and encapsulated into an Ether-
net stream towards an IP/MPLS Core Network.
[1] TDM to TDM flow
– Definition: This service identifies a flow inside MPR network, in which E1 is transported, switched
and terminated.
– Application: Typical microwave 2G backhauling application, in which E1s are terminated before
entering into aggregation network.
[2] TDM to ETH flow
– Definition: E1 TDM input signals are packetized according to MEF8 standard; E1s are transported,
switched and provided to an external ETH network in standard format (MEF-8).
– Application:
• a) Typical microwave 2G backhauling application, in which E1s are terminated before entering
into aggregation network, where aggregation network is a packet network. E1s are not termi-
nated at the end of the microwave backhauling and an end-to-end circuit emulation services
could be established between 9500 MPR and the service router in front of BSC/RNC
• b) 9500 MPR without ODU (MSS-8 or MSS-4 stand alone) provides the same level of feature
of a site aggregator box, grooming together different services (in this particular case E1 TDM)
into the common Ethernet layer.

[3] TDM to TDM flow
– Definition: This service identifies a flow inside MPR network, in which STM-1 is transparently trans-
ported, switched and terminated.
– Application: Typical microwave transport application.
[4] ETH to ETH flow
– Definition: Ethernet traffic is transported and switched automatically by the standard auto-learning
algorithm of the built-in MPR 10 Gbit Ethernet switch.
– Application: Typical microwave 3G backhauling/WiMax application, in which transport of Ethernet

packets coming from basestations is requested.
[5] “ATM2ATM” flow
– Definition: 9500 MPR terminates the native IMA/ATM and performs encapsulation/extraction of
those ATM flows into/from ATM PW packets according to RFC 4717. The 9500MPR facing the aggre-
gation network, the original ATM flows are re-built on ASAP board.
– Application: Typical microwave 3G backhauling application, in which transport of Ethernet packets

coming from 3G base station is requested.
[6] “ATM2ETH” flow
– Definition: 9500 MPR terminates the native IMA/ATM and ATM traffic, encapsulated in Ethernet
frames, is transported into IP/MPLS Core Network.
– Application: Typical microwave 3G backhauling application, in which transport of Ethernet packets

coming from 3G basestation is requested.

2.8.13 TDM and Ethernet traffic management
Three kinds of traffic management have been identified:
– TDM2TDM (9500 MPR-E ⇔ 9500 MPR-E, internal to the MPR network)
– TDM2Eth (9500 MPR-E ⇔ TDM to Ethernet)
– SDH2SDH (9500 MPR-E ⇔ 9500 MPR-E, internal to the MPR network)
– DATA (Ethernet to Ethernet)
The first two profiles meet MEF8 standard.
E1 or STM-1
E1 or STM-1
Figure 69. Traffic profiles
Case 1 for E1
The E1 stream is inserted in Node 1 and extracted in Node 2. In this case the two IWFs used to packetize
the traffic for the Ethernet switch in the Core-E module are both internal to the 9500 MPR-E network. The
Circuit Emulation Service is TDM2TDM in Node 1 and Node 2. The Cross connections to be implemented
are PDH-Radio type.
Case 1 for STM-1

The STM-1 stream is inserted in Node 1 and extracted in Node 2. In this case the two IWFs used to pack-
etize the traffic for the Ethernet switch in the Core-E module are both internal to the 9500 MPR-E network.
The Circuit Emulation Service is SDH2SDH in Node 1 and Node 2. The Cross connections to be imple-
mented are SDH-Radio type.
Case 2
The E1 stream is inserted in Node 1 and extracted in Node 2. One IWF is inside the 9500 MPR-E, but
the second IWF is external to the 9500 MPR-E network. The Circuit Emulation Service is TDM2ETH in
Node 1 and Node 2. The Cross connections to be implemented are PDH-Radio type in Node 1 and Radio-
Eth type in Node 2.
Case 3
The E1 stream is inserted/extracted in Node 1. One IWF is inside the 9500 MPR-E, but the second IWF
is external to the 9500 MPR-E network. The Circuit Emulation Service is TDM2ETH in Node 1 and Node
2. The Cross connections to be implemented are PDH-Eth type in Node 1.

Figure 70. Traffic profiles
Case 4 and 5
In these cases Ethernet packets enter Node 1 and are extracted in Node 2. In case 4 the Ethernet packets
encapsulate the E1 stream; in case 5 the packets are native Ethernet packets. None of the IWFs belongs
to the 9500 MPR-E network. The Circuit Emulation Service is ETH2ETH in Node 1 and Node 2. No Cross
connections must be implemented. The path is automatically implemented with the standard auto-
learning algorithm of the 9500 MPR-E Ethernet switch.

2.8.13.1 TDM2TDM
E1 traffic packetized only internally to 9500 MPR-E equipment.
RADIO
E1
BTS RADIO
RADIO
PDH
E1
E1
BTS
BSC
E1
BTS
Figure 71. E1 Traffic
Flow Id present (user defined)
Intermediate node configuration (E1 provisioning):
– node by node (building Cross-connection tables based on Flow Id)
Bandwidth guaranteed (according to QoS → Highest Queue Priority association)
No flooding-autolearning necessary
Both the IWFs belong to 9500 MPR-E and the packets are not supposed to exit the 9500 MPR-E network.
The IWF parameters listed above, have predetermined values and don’t need to be provisioned.
– Mac addresses are determined as consequences of the cross connections.
– Payload size is fixed to 121 bytes
– ECID will be the same value as Flow Id (ECID = Emulated Circuit Identifier)
– TDM clock source: clock recovery differential,
– Flow Id provisioned by ECT/NMS

2.8.13.2 TDM2Eth
E1 traffic both internal and external to 9500 MPR-E equipment.
E1
BTS
PSN
Eth Eth E1
E1
BTS BSC
E1
BTS
All the parameters must be configured compliant with the MEF8 standard
Adaptive or differential clock recovery supported
Destination MAC added before going into whole network (MEF8 compliant)
Only one of the IWFs belongs to 9500 MPR-E and the packets are supposed to exit the 9500 MPR-E
network.
– MAC addresses: in all involved nodes are determined as consequences of the cross connections;
the only exception is the Ethernet Terminal Node (the node where the TDM2ETH traffic goes through
an user Ethernet port). In such ETN the source address is the node Mac address, the destination
Mac address will be provisioned by ECT/NMS.
– Payload size: is fixed to 256 bytes
– ECID: provisioned by ECT/NMS, 2 different values may be used for each direction (ECID = Emulated
Circuit Identifier)
– TDM clock source is provisioned by ECT/NMS: clock recovery adaptive, clock recovery differential,
clock loopback (TDM line in)
– Flow Id is provisioned by ECT/NMS (One Vlan is assigned to each bi-directional circuit emulated E1
flow)
For this case the expected latency for 1 hop is 3.5 msec for 256 bytes.

2.8.13.3 SDH2SDH
STM-1 traffic packetized only internally to 9500 MPR-E equipment.
Figure 73. STM-1 Traffic
If there are intermediate nodes in each node build the Cross-connection tables based on Flow Id.
No flooding-autolearning necessary
Both the IWFs belong to 9500 MPR-E and the packets are not supposed to exit the 9500 MPR-E network.
– Mac addresses are determined as consequences of the cross connections.
– Payload size is fixed
– Clock source: clock recovery differential/node timing
2.8.13.4 ETH2ETH
None of the IWFs belongs to 9500 MPR-E.
None of the parameters listed in the previous slide has to be configured (the 9500 MPR-E is transparent).
PSN
WiMAX
(NodeB) Eth Eth
Eth
Eth
RNC
PSN
WiMAX Eth
Eth
(NodeB) RNC
WiMAX
(NodeB) Eth
Any packet belonging to an Eth2Eth TDM flow is treated as any other Ethernet packet with the only
exception of giving it an higher priority based on the MEF 8 Ethertype.

2.8.14 ATM Traffic Management
– Three Ethernet CoS are foreseen for ATM PW flows, derived from ATM Service Category configured
for the related VP/VC at ATM layer (by ATM Traffic Descriptor):
• CBR
• UBR+ (MDCR > 0)
• UBR
– By proper mapping of these CoSs to Core Switch and Modem Switch (refer to Figure 75.), the native
ATM QoS can be emulated.
– ATM PW flow-based packet queueing is performed inside the ASAP unit, its Ethernet flow CIR/PIR/
MBS/EBS parameters are also derived from configured ATM TD.
– ATM PW flows that have been classified as CBR and UBR+ will be subjected to admission control
and then have guaranteed bandwidth; the required bandwidth will be derived from Ethernet flow CIR,
taking in account the ATM PW encapsulation and air frame structure.
Figure 75. ATM Traffic Management - General block diagram
In Figure 76 is shown a more detailed block diagram of the ASAP unit in Ingress.

Figure 76. Block diagram for ATM Ingress (ATM -> Packet) direction
[1] ATM Ingress Policing

• ATM Policing (cell-based) can be enabled/disabled, on provisioning base, for each VP/VC con-
figured on ATM interface, according to its Ingress Traffic Descriptor (PCR,SCR,CDVT,MCDR)
as defined by ATM Traffic Management AF-TM-0121.000
– Service Category: CBR, UBR+ and UBR
– Conformace Definition: CBR.1
[2] Cells to packet
The ATM cells are encapsulated in PWE3 packet.
[3] Packet Profiled Scheduling

• ATM cell(s) are put into a packet, as result of provisioned value of max concat. number or
elapsed timeout; an Ethernet flow is therefore created (identified by ATM PW Label/VLAN pair),
whose CoS and CIR/PIR are automatically assigned by MPR based on ATM Ingress Traffic
Descriptor and previous encaps params.
• This packet is then put in a dedicated queue where:
– it is scheduled for transmission towards Core switch, with a constant rate given by
assigned CIR/PIR (depending on CoS):
• if the actual flow rate is < CIR:
– 802.1p bits are marked as "GREEN", if CIR<actual flow rate<PIR,
– 802.1p bits are marked as "YELLOW", (the packet is descarded on the Modem
unit in case of congestion on radio i/f);
• if the actual flow rate is > PIR, congestion on this queue happens and the next PWE3
packets will be dropped directly in ASAP card.
In/out profile is a dynamic assignment, based on CIR/PIR conformance for packet queue, and FC
type (expedited vs best effort). The mapping of the 802.1p bits is shown in Table 27.
It is mapped to 802.1p bits in the following manner:

802.1p bits Usage Color
000 Best Effort, Out-of-Profile YELLOW
001 unused -
010 Expedited, Out-of-Profile YELLOW
011 unused -
100 Best Effort, In-Profile GREEN
101 unused -
110 Expedited, In-Profile GREEN
111 Contro - egress only -
Table 27. 802.1p mapping
[4] Packet Dropper
The packets marked with yellow are discarded in case of congestion, when the buffer in the Modem
unit exceed a specific threshold.
Dropping mechanism:
• if a configurable queue fill level is overcame, then ATM PW packets that have been marked by
ASAP as out of profile (within 802.1p bits) are discarded.
The dropping mechanism applyies to queues with guaranteed Traffic:

• It applies to queue 7 and 6.
• To avoid delay on queue 7, shared among TDM2ETH, ATM CBR, the fill level to start descarding
is configured according to max acceptable delay (about 1 ms).
[5] Shared Tx queues
The packet according to its service category is send to one of the output queues.
[6] Rx Queues
Flows of the same type are reassembled in different queues.
[7] Packet to cells
The ATM cells are extracted from the PWE3 packet.
[8] ATM Egress Shaping

• A four-queue scheduling is used for for ATM traffic egressing MPR system.
• The higher priority queues are reserved for ATM shaped traffic, while the lowest one is reserved
to not shaped traffic.
• Cell-based ATM Shaping is applied for a VP/VC that has been configured with CBR and VBR
Service Category on the basis of its configured egress ATM Traffic Descriptor, general refer-
ence for this feature is ATM standards.
• A Weighted Round Robin is instead applied for all VPs/VCs that are not shaped. The weights
are based on the value of configured MDCR in the egress ATM Traffic Descriptor value accord-
ing to below table:

MDCR [cell/s] RR Weight
<= 149 1
<= 300 2
<= 602 3
<= 1206 4
<= 2413 5
<= 3621 6
<= 4529 7
>= 4530 8
e.g. MDCR = 1000 [cell/s] -> Weight = 4

An UBR has MDCR=0 -> weight = 1
Table 28. RR weights
N.B. ATM “Light” Service

With MPT-HC or MPT-MC there is no full support of ATM Traffic as with ODU300, but the so-
called ATM “Light” Service applies.
In this release, ATM PW traffic will be transported as native Ethernet traffic over radio directions
with MPT ODU.
Radio QoS applied to ATM PW traffic will be the one for native Ethernet traffic, but since band-
width cannot be guaranteed, admission control will not be applied.
Transport of ATM PW traffic within an MPR network must be done with radio links using all the
same type of ODU, either ODU300 or MPT ODU.
To avoid NE reconfiguration in migration towards future release fully supporting ATM PW Ser-
vice on radio directions with MPT ODU, a complete provisioning is applied since this release
(including declaration of traffic descriptors).
However, configurations where ATM PW flows are cross-connected between a Radio-Ethernet
terminal and an ATM-Ethernet terminal will require NE reconfiguration, as different MAC
Address need to be provisioned.

2.8.14.1 ATM Traffic Management on ASAP - PW Label Exp bits and scheduling type
The scheduling is performed by using the EXP bit in the PW label. The assignment is according to ATM
PW Cos as reported in the following table.
ATM Service category EXP bits Scheduling type
CBR 110 Expedited
UBR+ 010 Best Effort
UBR 000 Best Effort
Table 29. PW label EXP bits
2.8.14.2 ATM Traffic Management on Modem card - Block biagram for ATM PW Flow policer
Queue_filling_status
ATM Flow
Type
CLASSIFIER FLOW HEADER FQoS FRAMER
POLICER COMPRESSION
802.1p
Drop packets
Figure 77. ATM Traffic Management on Modem card - Block diagram
– The CLASSIFIER provides to FLOW POLICER, for each ATM PW flow ((VLAN&MAC classification),
the 802.1p bits with the indication if the packet is in/out profile.
– FLOW POLICER, looking at the packet type, 802.1p bits and the filling status of queue, discards or
sends the ATM PW packet to HEADR COMPRESSION.
2.8.14.3 Support of ATMoMPLS Protocl Stack (with or without MPLS Tunnel Label
2.8.14.3.1 ATM PW over MPLS (ATMoMPLS)
In order to support inter-working of ATM PW Service with IP/MPLS network at least at datapath level, in
this release it will be supported the ATMoMPLS protocol stack referenced by RFC 4717, with the char-
acteristics/limitation described in this paragraph.
For network deployment where both terminations of ATM traffic is carried out by MPR NEs, in order to save
radio bandwidth it will be possible to have the ATM PW Service using the ATMoMPLS protocol stack with-
out the MPLS Tunnel Label.

2.8.14.3.2 Protocol Stack Termination
In this release the ATMoMPLS protocol stack is terminated directly by the MPR NE where native ATM
interface is present (i.e. MPLS Tunnel Label, if present, is added by ASAP Card).
That implies all MPR NEs must be aware of MPLS Tunnel Label presence, i.e. to apply ATM PW Header
Compression.
2.8.14.3.3 802.1q VLAN Tag
ATMoMPLS protocol stack used by MPR foresees to have the 802.1q VLAN Tag.
VLAN is used, within MPR network, to define for ATM PW frames:
– forwarding plane
– colour marking consequent to profiled scheduling
– specific processing (ATM PW Header Compression) and QoS (queue assignment and colour-based
policing) on radio interfaces
The same VLAN ID can be used by several ATM PW flows only if they share the same CoS and forwarding
plane. Thinking to future releases, to use the same VLAN ID, the ATM PW flows must also share the same
encapsulation format (i.e. N-1 cell mode with or without Control Word, AAL5 SDU or PDU modes)
A VLAN ID that is used by ATM PW flow(s) can never be used for TDM flows.
The fields of the 802.1Q VLAN Tag to be inserted into ATM PW flow frames are assigned in the following
manner:
– 12-bit VLAN ID will be provisioned by ECT/NMS
– 3-bit PCP field is assigned according to the ATM PW flow COS and packet profiled scheduling
– 1-bit CFI field is set to 0
2.8.14.3.4 VLAN Swap
VLAN Swap feature is foreseen on "hand-off" MPR NE, i.e. the NE connected to IP/MPLS network.
VLAN Swap means that ATM PW flows ingressing/egressing the "hand-off" MPR will have the same com-
mon "external" VLAN ID, while within MPR network each ATM PW flow will use its own "internal" VLAN
ID (may be shared among several ATM PW flows with same path and CoS).
To avoid possible configuration clashing, the above "external" VLAN ID should belong to the allowed
range. Moreover, the "external" VLAN ID should be different from each "internal" VLAN ID.
VLAN Swap performed by the "hand-off" MPR NE is based on:
– for ingress, IP/MPLS network -> MPR network direction: the Inbound PW Label value
– for egress, MPR network -> IP/MPLS network direction: ATM PW CoS (to reduce numbers of "rules"
used for such mapping).

2.8.14.3.5 802.1p remarking
In addition to VLAN Swap, 802.1p bits remarking are also applied by "hand-off" MPR NE to ATM PW
frames:
– for ingress, IP/MPLS network -> MPR network direction: all frames will be declared as "green"
– for egress, MPR network -> IP/MPLS network direction: 802.1p bits will copy ATM PW Exp Bits
2.8.14.3.6 Tunnel Label
The MPLS Tunnel Label for ATM PW frames is foreseen only for compatibility with ATMoMPLS protocol
stack.
MPR network is actually not using information from MPLS Tunnel Label value in ATM PW frames, for
example:
– forwarding is based on VLAN/MAC DA
– CoS assignment of such frames will be always based on PW Label Exp bits
Tunnel Label fields to be inserted into ATM PW frames generated by MPR are assigned as below reported:
– 20-bit Tunnel Label will be provisioned by ECT/NMS
– EXP bits are copied from PW Label Exp bits
– BoS bit is set to 0
– TTL field is set to 255

2.8.15 Ethernet Traffic Management
The Ethernet traffic is all the traffic entered the MPR network from user Ethernet ports.
By ECT/NMS it is possible to define the way to manage the Ethernet traffic according to one of the
following options:
– 802.1D (MAC Address bridge)
– 802.1Q (Virtual Bridge).
2.8.15.1 Bridge type change
In case of change of the bridge type from 802.1Q to 802.1D, the content of the VLAN table and the VLAN
assigned to the user Ethernet ports (refer to par. 2.8.15.2) has to be deleted by the Operator before to
change the bridge type.
2.8.15.2 Reserved Multicast Addresses
The following table summarizes the actions taken for specific reserved multicast addresses. Frames
identified with these destination addresses are handled uniquely since they are designed for Layer 2
Control Protocols.
The actions taken by the system can be:
– Discard - The system discards all ingress Ethernet frames and must not generate any egress Ether-
net Frame carrying the reserved multicast address.
– Forward - The system accepts all ingress Ethernet frames as standard multicast frames and for-
wards them accordingly.
– Peer - The system acts as a peer of the connected device in the operation of the relevant Layer 2
Control Protocol.
Reserved Multicast Function Action

Address
01-80-C2-00-00-00 Bridge Group Address Forward
01-80-C2-00-00-01 Clause 31 (MAC Control) of IEEE 802.3 Flow-Control enabled: Peer

Flow-Control disabled: Discard
01-80-C2-00-00-02 Clause 43 (Link Aggregation) and Clause 57 Forward

(OAM) of IEEE 802.3
01-80-C2-00-00-03 IEEE 802.1X PAE address Discard
01-80-C2-00-00-04 - Reserved for future standardization Discard

01-80-C2-00-00-0D
01-80-C2-00-00-0E IEEE 802.1AB LLDP multicast address Discard
01-80-C2-00-00-0F Reserved for future standardization Discard

Reserved Multicast Function Action
Address
01-80-C2-00-00-10 All LANs Bridge Management Group Address Forward
01-80-C2-00-00-11 - Reserved Forward

01-80-C2-00-00-1F
01-80-C2-00-00-20 GMRP Address (Clause 10 of IEEE 802.1D) Forward
01-80-C2-00-00-21 GVRP Address (IEEE 802.1Q) Forward
01-80-C2-00-00-22 - Reserved for GARP Application Forward

01-80-C2-00-00-2F
01-80-C2-00-00-30 - CCM and LTM Group Destination MAC Forward

01-80-C2-00-00-3F Addresses (IEEE 802.1ag)

2.8.16 LAG (Link Aggregation Group)
2.8.16.1 LAG overview
Link Aggregation groups a set of ports so that two network nodes can be interconnected using multiple
links to increase link capacity and availability between them.
When aggregated, two or more physical links operate as a single logical link with a traffic capacity that
is the sum of the individual link capacities.
This doubling, tripling or quadrupling of capacity is relevant where more capacity is required than can be
provided on one physical link.
Link aggregation also provides redundancy between the aggregated links. If a link fails, its traffic is redi-
rected onto the remaining link, or links.
If the remaining link or links do not have the capacity needed to avoid a traffic bottleneck, appropriate QoS
settings are used to prioritize traffic so that all high priority traffic continues to get through.
The Link Aggregation is performed according to 802.3ad and can be applied to Radio ports and to User
Ethernet ports.
2.8.16.1.1 Link aggregation on Radio ports (Radio LAG)
Link aggregation can be applied to radio ports (in this case it is named Radio Link Aggregation).
Figure 78.
In this example, user traffic is split up into radio channels. Main advantages:
– Throughput. The overall radio Ethernet throughput is more than 1 Gbit/sec (2 x 530 Mbit/s, being
this the value for 256QAM@56 MHz)
– Protection. In case of a failure of one of the three channels, all the traffic is redirected on the remain-
ing link (with a throughput of around 0.5 Gbit/sec). The discarded or dropped traffic is the one with
lower priority: high priority traffic is still running on the remaining active channels.

Figure 79.
One MPT per MPT plug-in.
2.8.16.1.2 Link aggregation on User Ethernet ports (Ethernet LAG)
Link aggregation can be applied to Ethernet user ports (electrical or optical ) on the same Core-E unit.
The LACP protocol is supported.
Note 1: the Ethernet ports involved in a LAG cannot be used as TMN In-band interface.
Figure 80.
2.8.16.1.3 Rules to be followed for the LAG creation
– Max number of Ethernet LAGs: 3 - each LAG with max 2 Ethernet ports (electrical or optical).
– Max number of Radio LAGs: 3 - each with max two MPT-HC or two MPT-MC (no ODU300 can be
used).
– The two MPT, grouped in a radio LAG, must be connected to two different MPT Access units (the
other port of the MPT Access unit must be EMPTY). The ports of the two MPT Access units can have
also a different port number.
Warning: the other port of the MPT Access unit must be DISABLED.
– The identifying number a LAG must be in the range 1-24.

2.8.17 Quality Of Services (QoS)
The QoS function inside 9500 MPR-E is the result of a distributed implementation in the switch and Radio
Interface module. Both those QoS functions are properly configured in order to get the wished behavior
on Ethernet flows that will be transmitted towards the Radio.
N.B. Configurations files
To obtain a specific behavior (not obtainable with the WebEML) the configuration files can be
used. The configuration files configure the Ethernet switch inside the Core-E and the FPGA
inside the Modem unit for ODU300 and inside the MPT Access unit for MPT-HC/MPT-MC.
The configuration files are written by using a set of low level commands provisioning in the
proper way different devices of different MPR cards. After an NE reset, the configuration file is
applied, provisioning the Ethernet switch and other devices to implement the desired feature.
The configuration file must be put in the compact flash plugged in Main Core, inside a specific
directory, via FTP.
The application of a new configuration file could cause traffic hits.
Supported feature list for ODU300:
– QinQ: how to apply 802.1ad to MPR

– Disable Autonegotiation on SFP port
– VLAN SWAP: possibility to swap incoming/outgoing VLAN IDs on MPR user Ethernet
interfaces
– Out of range VLAN SWAP: admit VLAN in range [4081:4094] inside MPR Network
– VLAN SWAP and dot1p remarking for ATM service: this feature describes how to have
MPR interworking with IP/MPLS equipment
– Port Based Rate Limiting: apply a ingress/egress rate limiting on MPR user Ethernet
interfaces
– Storm Control: allows to restrict the number of incoming broadcast, multicast or DLF traf-
fic in a 1 second interval on a specific port. When in a 1 second time interval, the number
of broadcast, multicast and DLF exceeds the configured limit, the dropping mechanism
is applied.
– Access Control List: allows to restrict MAC address in MPR network. Enabling this fea-
ture all MAC address not expressively include in the list will be automatically dropped.
– Per Vlan Rate Limiting: allows to apply an rate limiter to a specific VLAN ingressing the
MPR network. This feature is applicable in both 802.1Q and 802.1ad (QinQ) bridge mode.
– Scheduler Setting: customize scheduling policy on radio and Ethernet interfaces
– Mapping 802.1p to queues: customize 802.1p bits mapping to queues
– Mapping DiffServ to queues for IPv4 frames: customize IPv4 DSCP bits mapping to
queues
– IPv6 QoS support with flexible mapping traffic class to queues: customize IPv4 CoS
bits mapping to queues
– SFP2E1/DS1 Circuit Emulation: configure the 2xE1/DS1 streams which are hosted in
an SFP to be installed in the Core-E unit
– Alarm Severity Assignment profile: customize the mapping of the Non Service Affect-
ing Severity and Service Affecting Severity of each supported alarm.
Supported feature list for MPT-HC/MPT-MC:
– QinQ: how to apply 802.1ad to MPR

– VLAN SWAP: possibility to swap incoming/outgoing VLAN IDs on MPR user Ethernet
interfaces

– Out of range VLAN SWAP: admit VLAN in range [4081:4094] inside MPR Network
– Storm Control: allows to restrict the number of incoming broadcast, multicast or DLF traf-
fic in a 1 second interval on a specific port. When in a 1 second time interval, the number
of broadcast, multicast and DLF exceeds the configured limit, the dropping mechanism
is applied.
– Scheduler Setting: customize scheduling policy on radio and Ethernet interfaces
– Mapping 802.1p to queues: customize 802.1p bits mapping to queues
– Mapping DiffServ to queues for IPv4 frames: customize IPv4 DSCP bits mapping to
queues
– IPv6 QoS support with flexible mapping traffic class to queues: customize IPv4 CoS
bits mapping to queues
– SFP2E1/DS1 Circuit Emulation: configure the 2xE1/DS1 streams which are hosted in
an SFP to be installed in the Core-E unit
– Alarm Severity Assignment profile: customize the mapping of the Non Service Affect-
ing Severity and Service Affecting Severity of each supported alarm.
The use of the Configuration files is explained in the relevant document “Configuration File Management”.
2.8.17.1 QoS in the Core-E unit
Figure 81. QoS in the Core-E unit
The figure shows an overview of the QoS implementation inside the switch.
The Quality of Service feature of the Ethernet switch provides four internal queues per port to support four
different traffic priorities. Typically the high-priority traffic experiences less delay than that low-priority in
the switch under congested conditions.
For each egress port according to method of QoS classification configured in the switch, the packets are
assigned to each queue.
TDM flows classification
All the TDM2TDM traffic flows will be assigned to the highest egress priority queue (Q8). All the TDM2ETH
traffic flows will be assigned to the Q7 egress priority queue. All the MEF-8 ETH2ETH traffic flows will
be assigned to the Q5 egress priority queue.

Ethernet flows classification
For generic Ethernet flows in the switch the priority of each packet can be assigned according to the
information in:
– IEEE 802.1p: the packet is examined for the presence of a valid 802.1P user-priority tag. If the tag
is present the correspondent priority is assigned to the packet
.
802.1P priority Queue
111, 110 Q5 (higher priority)
101 Q4
100 Q3
011, 000 Q2
010, 001 Q1
– DiffServ: each packet is classified based on DSCP field in the IP header to determine the priority.
DiffServ priority Queue
111000, 110000, 101110, 101000 Q5 (higher priority)
100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000 Q2

001110, 001100, 001010, 001000
000000
All remaining values Q1
ATM PW flows classification
ATM PW flows will be assigned to Ethernet switch egress priority queues according to their CoS , as below
reported:
ATM PW CoS Switch Egress Queue
Guaranteed (CBR) Q7 (higher priority)
Best Effort (UBR+) Q6
BackGround (UBR) Q1

Scheduler
The scheduler algorithm cannot be configured. HQP scheduler algorithm is used on queues Q8, Q7 and
Q6.
Deficit Weighted Round Robin (DWRR) is used on the other queues with the following weights:
QUEUE WEIGHT
Q5 (higher priority) 16
Q4 8
Q3 4
Q2 2
Q1 1
QoS with jumbo frame
While there is no physical limitation to the number of ports that can receive jumbo frame, if more jumbo
flows are transmitted toward the same port into two different queues the QoS could work in wrong way.
It is recommended to forward jumbo frame only in the queue Q1 (lower priority).
2.8.17.2 QoS in the Modem unit
Figure 82. QoS in the Modem unit
In the figure is shown an overview of the QoS implementation inside the Modem unit which is used to
interface the ODU300.
The QoS feature provides eight internal queues to support different traffic priorities. The QoS function can
assign the packet to one of the eight egress transmit queues.
– Queue 8 is assigned to TDM2TDM traffic
– Queue 7 is assigned to TDM2Eth traffic

– Queue 6 is assigned to TMN
Queues 1 to 4 are assigned to Ethernet traffic according to the information inside the packet as 802.1p
field, DiffServ field, Ethertype or 802.1Q VLAN_ID.
TDM flows classification
All the TDM2TDM traffic flows are assigned to the highest egress priority queue (Q8). All the TDM2ETH
traffic flows are assigned to the Q7 egress priority queue. All the MEF-8 ETH2ETH traffic flows are
assigned to the Q5 egress priority queue.
TMN flows classification
All TMN traffic flows are assigned to the Q6 egress priority queue.
QoS based on IEEE std. 802.1p
When 802.1p QoS mechanism is adopted, the reference is the standard “IEEE 802.1D-2004 Annex G
User priorities and traffic classes” that defines 7 traffic types and the corresponding user priority values.
Considering that in the Radio Interface module for generic Ethernet traffic there are five egress queues
the mapping 802.1p value to queue is the following:
802.1p priority Queue
111, 110 Q5 (higher priority)
101 Q4
100 Q3
011, 000 Q2
010, 001 Q1
QoS based on DiffServ
DiffServ priority Queue
111000, 110000, 101110, 101000 Q5 (higher priority)
100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000 Q2

001010, 001100, 001010, 001000, 000000
All remaining values Q1

ATM PW flows classification
ATM PW flows will be assigned to radio queues according to below table:
ATM PW CoS Radio Queue
Guaranteed (CBR) Q7 (higher priority)
Best Effort (UBR+) Q6
BackGround (UBR) Q1
Scheduler
HQP scheduler algorithm will be used on Q8, Q7 and Q6.
Deficit Weighted Round Robin (DWRR) algorithm will be used for the other five queues.
By default, the DWRR algorithm is used with the following weights:
Queue Weight
Q5 (higher priority) 16
Q4 8
Q3 4
Q2 2
Q1 1
2.8.17.3 QoS in the MPT-HC/MPT-MC
The Radio QoS is implemented by MPT-HC/MPT-MC itself (not in the MPT Access unit).
The set of MPT Radio QoS features is the same of the one specified for the Modem unit (refer to par.
2.8.17.2) with the exception of the ATM CBR and UBR+ CoS: in MPT-HC/PT-MC they are sent to queue
#5 and queue #4 respectively (and not to queue #7 and queue #6).

2.8.18 Cross-connections
Figure 83. Cross-connection
The cross-connections between slots and between slot and Ethernet user ports are realized with a Layer-
2 Ethernet Switch inside the Core-E unit.
The decision made by the switch to forward the received packet is based on the destination MAC address.
2.8.18.1 E1 Cross-connections
Each E1 can be cross connected independently.
E1 can be cross connected to any of the following interfaces:
– Radio interface
– Ethernet interface
Each E1 (board #, port #) must be associated to an unique signal flow ID.
2.8.18.2 STM-1 Cross-connections
Each STM-1 can be cross connected independently.
STM-1 can be cross connected to the following interface:
– Radio interface
Each STM-1 (board #, port #) must be associated to an unique signal flow ID.
2.8.18.3 Radio-Radio Cross-connections
Ethernet frames, coming from a radio direction, can be cross-connected to another radio direction.

2.8.18.4 Ethernet Cross-connections
Generic Ethernet flows
All flows different from the TDM2TDM and TDM2ETH ones are managed as the standard Ethernet
packets: if the 802.1Q is enabled the related management is performed looking the VLAN and then,
according to the destination address, each packet is switched to the correct port: radio, user Ethernet or
E1/DS1. If the 802.1Q is not enabled only the destination address is considered.
For each radio interface, the bandwidth assigned, globally, to the Ethernet traffic is the consequence, with
a given radio capacity, of the number of E1/DS1 cross-connected on that radio interface. Hence the
available bandwidth for Ethernet flows will be the configured radio bandwidth decreased by bandwidth
used by each TDM2TDM and TDM2ETH.
2.8.18.5 ATM PW cross-connections
Cross-connection of ATM PW flows involves the following levels of operation:
– an ATM PW is composed of two unidirectional flows, so its cross-connection is internally managed

by NE as two unidirectional flow cross-connections
– for ATM PW flow with guaranteed bandwidth, an admission control check must be performed in each
flow direction: there shall be enough available bandwidth on both directions
– VLAN-based settings in terms of Ethernet switch and Radio QoS are then performed (as the same
VLAN can be used for ATM PW flows with same CoS and path).
– The minimum bandwidth foreseen for an ATM PW flow corresponds to the case of PCR, SCR or
MDCR of 1 cell/s rate, with max 1 cell for frame.
ATM "Light" Cross-connection Provisioning
In this release when a cross-connection toward a radio direction with MPT is involved, the related provi-
sioning is performed in almost the same way as with ODU300, with the following main differences:
– MAC DA is also explicitly provisioned in the NE acting as TPE role
– admission control, in terms of checking bandwidth required bt ATM PW flow against the available
bandwidth on radio interface, is never performed
MAC SA assignment for ATM PW frames generated by ASAP peripheral
MAC Source Address of ATM PW frames generated by ASAP peripheral should be assigned to be equal
to:
– the internal MAC Address of slot hosting that ASAP peripheral in case of cross-connection towards
radio interface
– the NE Mac Address in case of cross-connection towards Ethernet interface.
In this release it is accepted to assign always the NE Mac Address as MAC Source Address of ATM PW
frames generated by ASAP peripheral.
Admission control for ATM PW flows towards radio directions
Each time a cross-connection for an ATM PW flow involving, at least, one radio direction, is required by
the management systems, an admission control is performed.

The admission control depends on the remaining bandwidth computed on the basis of specific Radio
Profile and on the previously configured TDM or ATM PW flows.
The bandwidth available for each radio direction is available to ECT/NMS.
Admission control for ATM PW flows towards User Ethernet interface
Each time a cross-connection for ATM PW flow involving, at least, one user Ethernet port, is required by
the management systems, an admission control is to be performed if the Ethernet port is in manual
configuration with speed at 1000 MBit/s and pause disabled.
The admission control depends on the remaining bandwidth computed on the basis of the configured
speed and on the previously configured TDM2ETH or ATM PW flows.
The bandwidth available for each user Ethernet port is available to ECT/NMS.
Admission control for ATM PW flows towards ATM interface
In this release no admission control is performed for an ATM PW flow cross-connection in the direction
from a radio or Ethernet interface towards an ATM interface.
ATM PW flows admission control in AM
When the admission control is enabled, the cross-connection of the ATM PW flows requiring guaranteed
bandwidth towards a radio direction configured to work in Adaptive Modulation Mode, is allowed only if
there is sufficient bandwidth at the lowest modulation.
This means that it is not allowed to cross-connect ATM PW flows, requiring guaranteed bandwidth,
exceeding the bandwidth available with the lowest modulation.
When the admission control is disabled, the cross-connection of the ATM PW flows requiring guaranteed
bandwidth towards a radio direction configured to work in Adaptive Modulation Mode, is allowed only if
there is sufficient bandwidth at the highest modulation.
This means that it is not allowed to cross-connect ATM PW flows, requiring guaranteed bandwidth,
exceeding the bandwidth available with the highest modulation.
Admission Control and ATM Ligth
In this release, any kind of above Admission Control procedures for ATM PW flows is not applied for ATM
Light, i.e. when a radio direction with MPT radio is involved.
Common Consistency Checks
In any kind of below cross-connection, it is necessary to perform the following common checks:
– the same VLAN ID cannot be shared between a TDM2TDM/TDM2ETH flow and an ATM PW flow
– the same VLAN ID shall be used for the two directions of ATM PW
ATM PW flows into ATM-Radio terminal
This configuration is needed when an ATM PW flow terminated on ASAP board is transmitted on a radio
direction.
ATM PW flows termination on ASAP board assumes a previous layered configuration of E1, IMA and ATM
interface (the latter with the explicit definition of VPI/VCI, ATM Traffic Descriptors and VPC/VCC
termination).

Each ATM PW flow can be cross-connected towards a Radio direction according to the following rules:
– each ATM PW flow can be cross-connected independently
– each ATM PW flow can be cross-connected towards one Radio direction.
The cross-connection of an ATM PW flow involves the following main parameters:
– ATM PW flow n° A, its CoS and flow policing enable flag (derived by configured Ingress ATM Traffic
Descriptor)
– slot n° B of the ASAP board where the ATM PW n° A is terminated
– slot n° C of the Radio board
– VLAN_ID n° D used to transport the ATM PW flow.
If the ATM PW flow CoS requires guaranteed bandwidth towards radio interface, its CIR value and
average frame size S in ingress Ethernet Traffic Descriptor (both derived by configured Ingress ATM
Traffic Descriptor) shall be used to perform admission control on the Radio interface. In this release no
admission control towards ASAP board (ATM interface) is performed.
The above parameters shall be used:
– for ASAP board to derive the following ATM PW Header fields:

• slot n° C of the Radio board is used to derive MAC Destination Address
• VLAN_ID n° D is used for 802.1q VLAN tag
• ATM PW CoS defines static value for 802.1p bits (Expedite vs Best Effort scheduling)
• ATM PW flow n° A is mapped to the Outbound and Inbound PW Labels
• ATM PW CoS defines EXP bits in PW Header
– for Ethernet switch to perform configuration related to:

• VLAN_ID n° D membership for ASAP and Radio board ports
• assignment, for these ports and VLAN n° D, the egress queue as defined by ATM PW CoS
• configure static routes for internal MAC Address associated to slot n° B/C and VLAN_ID n° D
– for Radio board to perform configuration related to:

• to identify, by VLAN_ID n° D and MAC DA of the internal MAC associated to slot n° C, the ATM
PW flow frames to be transmitted over radio physical layer, in order:
– to enable/disable ATM PW flow policing
– to perform header compression and ATM PW frames fragmentation
– to perform queue assignment according to its CoS
• to identify, by VLAN_ID n° D, the ATM PW fragments received from radio physical layer, in order
to rebuild ATM PW frames performing header decompression, with assignment as MAC DA of
the internal MAC associated to slot n° B
Checks related to use of same VLAN_ID
Ethernet switch and Radio boards configuration must be done only in case they were not already done
for another ATM PW flow that is using the same VLAN_ID n° D (with same VLAN membership and CoS).
In case the VLAN_ID n° D has been already configured for different port membership and/or CoS, the
cross-connection will be refused.
Deletion of a ATM PW flow cross-connection previously configured according to SR. ID 8204, implies
deletion of Ethernet switch and Radio boards configuration only if no other ATM PW flow is using that
VLAN_ID.

ATM PW flows into Radio-Radio repeater
This configuration is needed when an ATM PW flow received on one radio direction doesn’t terminate but
it is transmitted on other radio direction (and viceversa).
Each ATM PW flow can be cross-connect between a pair of Radio directions according to the following
rules:
– each ATM PW flow can be cross-connected between one Radio direction pair.
The cross-connection of an ATM PW flow between a Radio direction pair involves the following param-
eters:
– ATM PW flow n° A, its CoS and flow policing enable flags
– slot n° B for first Radio board
– slot n° C for second Radio board
– VLAN_ID n° D used to transport the ATM PW flow
If the ATM PW flow CoS requires guaranteed bandwidth, the CIR value and average frame size S con-
figured in ATM PW flow Ethernet Traffic Descriptors, shall be used to perform admission control. The
cross-connection can be accepted only if there's available bandwidth for both directions, otherwise it shall
be refused.

• VLAN_ID n° D membership for Radio boards ports
– for Radio boards to perform configuration related to:

• to identify, by VLAN_ID n° D and MAC DA of the internal MAC associated to slot n° B/C, the
ATM PW flow frames to be transmitted over radio physical layer, in order:
to rebuild ATM PW frames performing header decompression, with assignment as MAC DA of
the internal MAC associated to slot n° B/C
Limitation for ODU300 <-> MPT Cross-connection
ATM PW Cross-Connection between a radio direction with ODU300 and another radio direction with MPT
ODU is not possible.
for another ATM PW flow that is using the same VLAN_ID n° D (with same VLAN membership and CoS).
In case the VLAN_ID n° D has been already configured for different port membership and/or CoS, the
cross-connection will be refused.

Deletion of a ATM PW flow cross-connection previously configured, implies deletion of Ethernet switch
and Radio boards configuration only if no other ATM PW flow is using that VLAN_ID.
Consequence of that is the deletion of an ATM PW cross-connection does not imply the related traffic is
implicitly stopped (if another ATM PW flow is using the associated VLAN_ID).
ATM PW flows into Radio-ETH terminal
This configuration is needed when an ATM PW flow generated by remote MPR node (with ASAP board)
is transported/terminated by external equipment linked to local MPR node by an User Ethernet interface.
In this case manual configuration of Ethernet interface at 1000 MBit/s and pause disabled is mandatory.
Each ATM PW flow can be cross-connect between a radio direction and an Ethernet interface according
to the following rules:
– each ATM PW flow can be cross-connected between one radio direction and one Ethernet interface.
The cross-connection of an ATM PW flow between a radio direction and an Ethernet interface involves
the following parameters:
– ATM PW flow n° A, its CoS, flow policing enable flag
– slot n° B for first Radio board
– User Ethernet port n° C
– VLAN_ID n° D used to transport the ATM PW flow
If the ATM PW flow CoS requires guaranteed bandwidth, the CIR value and average frame size S con-
figured in ATM PW flow Ethernet Traffic Descriptors shall be used to perform admission control. The cross-
connection can be accepted only if there's available bandwidth for both directions, otherwise it shall be
refused.

• VLAN_ID n° D membership for Radio boards ports
– for Radio board to perform configuration related to:

• to identify, by VLAN_ID n° D and MAC DA of the MPR NE MAC Address, the ATM PW flow
frames to be transmitted over radio physical layer, in order:
to:
– rebuild ATM PW frames performing header decompression
– assignment as MAC SA of the MPR NE MAC
– assignment as MAC DA of the MAC Address to be used for interworking that has been
configured for the ATM PW

for another ATM PW flow that is using the same VLAN_ID n° D (with same VLAN membership, CoS and
Peer MAC Address).
In case the VLAN_ID n° D has been already configured for different port membership, CoS and Peer MAC
Address, the cross-connection will be refused.
and Radio boards configuration only if no other ATM PW flow is using that VLAN_ID.
Consequence of that is the deletion of an ATM PW cross-connection does not imply the related traffic is
implicitly stopped (if another ATM PW flow is using the associated VLAN_ID).
Limitation in checks related to use of same VLAN ID
In this release, the check related to configure the same Peer MAC Address in case the same VLAN ID
is used by several ATM PW flows is not performed.
ATM PW flows into ATM-Ethernet terminal
This configuration is needed when an ATM PW flow terminated on ASAP board is directly transported/
terminated by external equipment linked to remote MSS node by an User Ethernet interface.
In this case manual configuration of Ethernet interface at 1000 MBit/s and pause disabled is mandatory.
ATM PW flows termination on ASAP board assumes a previous layered configuration of E1, IMA and ATM
interface (the latter with the explicit definition of VPI/VCI, ATM Traffic Descriptors and VPC/VCC termi-
nation).
Each ATM PW flow can be cross-connected towards an Ethernet interface according to the following
rules:
– each ATM PW flow can be cross-connected towards one Ethernet port.
The cross-connection of an ATM PW flow involves the following parameters:
– ATM PW flow n° A and its CoS (derived by configured Ingress ATM Traffic Descriptor)
– slot n° B of the ASAP board where the ATM PW n° A is terminated
– User Ethernet port n° C
– VLAN_ID n° D used to transport the ATM PW flow.
If the ATM PW flow CoS requires guaranteed bandwidth, its CIR value and average frame size S in ingress
Ethernet Traffic Descriptor (both derived by configured Ingress ATM Traffic Descriptor) shall be used to
perform admission control on the Ethernet interface. In this release no admission control towards ATM
interface (ASAP board) is performed.
– for ASAP board to derive the following ATM PW Header fields:

• MAC Destination Address is the provisioned Peer MAC Address
• VLAN_ID n° D is used for 802.1q VLAN tag
• ATM PW CoS defines static value for 802.1p bits (Expedite vs Best Effort scheduling)

• ATM PW flow n° A is mapped to the Outbound and Inbound PW Labels
• ATM PW CoS defines EXP bits in PW Header

• VLAN_ID n° D membership for ASAP board and User Ethernet ports
• configure static routes for MPR NE MAC Address, Peer MAC Address and VLAN_ID n° D
Ethernet switch configuration must be done only in case they were not already done for another ATM PW
flow that is using the same VLAN_ID n° D (with same VLAN membership, CoS and Peer MAC Address).
In case the VLAN_ID n° D has been already configured for different port membership, CoS, or Peer MAC
Address the cross-connection will be refused.
configuration only if no other ATM PW flow is using that VLAN_ID.
2.8.18.5.1 ATM Local Switch feature
Termination of ATM traffic into the same MPR Node ("ATM Switch-like") is supported with the following
characteristics:
1) ATM traffic switching requires in any case ATM PW termination;
2) the only limitation in terms of involved ATM i/f (IMA Groups), is switching is not possible
betweeen ATM i/fs hosted by same ASAP peripheral: VPs/VCs to be switched must always
belong to two ATM i/fs hosted by different ASAP peripherals; for example it is possible to aggre-
gate the VP/VC belonging to 2 or more different ATM i/fs, hosted by same ASAP peripheral,
towards a single ATM i/f only if the latter is hosted by a different ASAP peripheral;
3) no direct configuration of cross-connections for the ATM PW flow pair is supported, instead it
will be necessary to configure, for each ATM PW flow belonging to the ATM PW flow pair to be
cross-connected, an ATM->Ethernet cross-connection towards a given Ethernet port (it can be
the same); the Ethernet port(s) involved in these cross-connections can be used for other traf-
fic, with the only impact due to bandwidth reservation, if applicable;
4) a proper MAC Destination Address has to be configured for each ATM PW: it has to be different
from NE MAC, but since the ATM PW frames are not sent outside the NE, in principle any other
valid MAC value can be used;
5) to allow ATM PW flow frame forwarding, without external cable, and swap between VLAN IDs,
an Ethernet Switch configuration file has to be used.
2.8.18.6 Port Segregation
This feature is based on the port based VLAN feature supported by the Ethernet switch and allows the
following behavior: all traffic received/transmitted from one user Ethernet port or radio direction can not
be exchanged with specific user Ethernet ports/radio directions.
The default configuration foresees:
– Every user Ethernet port is cross-connected to all Radio directions (bidirectional connection)

– All the Radio directions are cross-connected between them (bidirectional connection)
– All the user Ethernet ports are cross-connected between them (bidirectional connection)
By ECT/NMS it is possible to change this default configuration. When TDM flow cross-connections or ATM
PW flow cross-connections are defined and involve TDM or ATM ports, port segregation involving these
ports are implicitly prohibited.
2.8.18.6.1 Port Segregation and Frame Duplication
The Operator must be aware that application of port segregation between an User Port and radio ports
in 1+0 configuration (segregated among them) towards the same NE can lead to duplication of broadcast,
multicast of flooding traffic.
2.8.18.6.2 TDM ports involving
Port Segregation is not supported for TDM ports (E1/DS1) by ECT/NMS. At system level TDM ports are
segregated among them and not segregated from Radio directions involved in TDM flows cross-connec-
tions.
2.8.18.6.3 ATM ports involving
Port Segregation is not supported for ATM ports by ECT/NMS. At system level ATM ports are segregated
amomg them and not segregated from Radio directions involved in ATM PW flows cross-connections.
2.8.18.6.4 General rules
Port Segregation between two ports can be applied only if they are not involved in TDM flows cross-con-
nections, ATM PW flows cross-connections or Service Channels cross-connections.

For example, when there is a TDM2ETH flow or ATM PW flow cross-connected between one User Ether-
net port and one Radio direction, it is not possible to apply Port Segregation.
A TDM flows cross-connection or an ATM PW flows cross-connection can be applied between User Ether-
net and Radio ports only if the involved ports are not segregated. Before apply the cross-connection the
operator has to remove the Port Segregation.
A Service Channels cross-connection between two Radio directions can be applied only if the involved
ports are not segregated.
2.8.18.6.5 MPT plug in ports
For MPT Access peripheral ports, port segregation can be applied by operator at two different points:
– between MPT Access peripheral ports connected to MPTs: to segregate connected MPTs
– between them between MPT Access peripheral port connected to MSS backplane and the other
backplane ports: to segregate all connected MPTs towards User Ports or other radio directions.
In case only one MPT is connected to MPT Access peripheral port, the port segregation behaviour is the
same as with ODU300 radio direction.
Assuming 2 MPTs in 1+0 configuration are connected to same MPT Access peripheral, since that is the
only configuration supported within this release with more than one MPT on same MPT Access peripheral,
three scenarios have to be considered:
1) no port segregation is applied by operator between MPT Access peripheral ports and to MPT
Access peripheral port towards backplane: in this case, all the involved ports can exchange the
data among them (case A);
2) port segregation is applied by operator between MPT Access plug-in ports, while no port seg-
regaton is applied by operator to MPT Access peripheral port towards backplane: in this case,
the two MPTs cannot exchange data (case B); in this case, frame duplication for broadcast, mul-
ticast and flooding traffic will surely occur in case the two radio directions are towards the same
NE;
3) no port segregation is applied by operator between MPT Access plug-in ports, while operator
applies segregation to MPT Access peripheral port towards backplane. This case represents
an MPT Access peripheral isolated from MSS backplane, in such case, the two MPTs can only
exchange data between them (case C).
A fourth scenario for application of port segregation is possible, but in this release is not applicable:
4) port segregation is applied by operator between MPT Access peripheral ports and MPT Access
peripheral port towards backplane, no traffic can be exchanged between MPTs and with MSS
with the current number of supported MPT Access peripheral ports. No check has to be imple-
mented to forbide this application of port segregation since it can be it applied in future releases
where use of all MPT Access peripheral ports is supported (case D).

2.8.18.6.6 MPTs number for each MPT plug in
If port segregation is applied by operator to an MSS User port and to MPT Access plug-in port towards
backplane, MPT ODUs connected to same MPT Access plug-in will have the same segregation.
This application of port segregation by operator has no consequence on the capability to provision up to
2 MPT ODUs on the same MPT Access plug-in (in 1+0).
Below it is reported an example of applicable port segregation configuration by operator.
In this case the goal of port segregation is the MPT1-MPT3 pair does not exchange traffic with MPT2-
MPT4 pair.

2.8.18.6.7 ODU300
In case the Core-E user port is segregated from ODU300 radio: consequently, the ODU300 is segregated
from the Core-E user port and vice versa.
In case of protected radio direction, the spare radio direction must have the same port segregation
configuration.
Any previous port segregation configuration for spare radio direction must be deleted by operator.
2.8.18.6.8 ODU300 and MPTACC
If port segregation is applied by operator to an ODU300 radio port and to MPT Access plug-in port towards
backplane, all the MPT Access ports are segregated from the ODU300 radio port and vice versa.
2.8.18.6.9 MPTs protected on different plug-ins
When two MPTs are provisioned for 1+1 protected configuration on two different MPT Access
peripherals,the MPT Access plug-in ports towards backplane will not implicitly segregated each other.
Otherwise, when it will be supported in future release the possibility to connect another MPT to the same
MPT Access peripheral(s), it would not possible to have it in repeater configuration with the protected MPT
pair.
Operator is allowed to apply port segregation to MPT Access peripherals hosting an MPT pair in 1+1, but
since connection to other MPT on same plug-in is not supported in this release, only the segregation of
MPT Access port towards the backplane is effective.
The spare radio direction must have the same port segregation configuration (for MPT Access plug-in port
towards backplane).
Any previous port segregation configuration for spare radio direction must be deleted by operator.

2.8.19 Synchronization for PDH/SDH/DATA
2.8.19.1 Synchronization overview
PDH/SDH data flow is fragmented and the fragments are transmitted over a Packet Switched Network
(PSN);
The received fragments need to be reassembled in the original PDH/SDH data flow at the “original bit rate”
Two main methods can be used to recover at the Rx site, the original bit rate:
– Differential clock recovery with or without the Node Timing: recalculation of the original clock
based of the Delta respect to a reference clock that is available at both Tx and Rx site (Differential:
used in case of clock distribution on the whole network. It’s more reliable than Adaptive; also used
in TDM2TDM/SDH2SDH traffic (MPR to MPR)). This method can be selected for each E1/STM-1
stream.
– Adaptive clock recovery with or without the Node Timing: based on the average rate at which
the packets (fragments) arrive at RX site (Adaptive: simpler network, but performances depends on
the PDV (Packet Delay Variation) in the Network. Always used when the reference clock isn’t
distributed on the whole network). This method can be selected for each E1 stream.
The available clock recovery techniques with TDM2TDM and SDH2SDH profiles are:
– DCR: differential clock recovery
– with/without Node timing
The available clock recovery techniques with TDM2ETH profile are:
– ACR: adaptive clock recovery (if a common reference clock is not available)
– DCR: differential clock recovery
– with/without Node timing.
Note
In meshed networks (rings) do not close the synchronisation configuration.
N.B. If the NODE TIMING is enabled, the WebEML still propose the possible selection between ACR
and DCR: in this specific case, the meaning of this option is not related to the clock recovery
algorithms, but rather to the MRF8 frame format.

2.8.19.1.1 Differential clock recovery
End End
System1 System2
IWF PSN
PSN IWF
Common reference clock IS available at both Ends.
IWF system, at RX side, generate output clock based on RTP TimeStamps which are sent together with
each Fragments.
2.8.19.1.2 Adaptive clock recovery
End End
System1 System2
IWF PSN
PSN IWF
Common reference clock is NOT available at both Ends.
IWF system, at RX side, generate output clock based on data arrival rate: TDM clock is slowly adjusted
to maintain the average fill level of a jitter buffer at its midpoint.
2.8.19.1.3 Node Timing
The Node Timing is the timing from the network clock as defined in G.8261. The enabling of the Node
Timing is applied to all E1s of the PDH unit or to each STM-1.
This feature (called either “network clock re-timing” or “node timing” or, according to G. 8261 wording, “net-
work-synchronous operation for service clock”) introduces an additional possibility to recover the clock.
Node timing is a way to recover the clock quite popular in the industry of service routers and site aggre-
gator boxes. This feature inside the 9500 MPR platform is adding interworking capabilities with third par-
ties service routers and circuit emulations gateway.
In node-timing working mode, all the E1s are re-sampled with the network element clock. This means that,
as also reported in G8261, this method does not preserve the service timing (E1 clock).
Recovered E1 clock is according to G. 823 synchronization masks.

2.8.19.2 Synchronization Sources and protection policy
In order to get any node in a meshed network or ring topology network always locked for each node the
synchronization sources and the automatic selection process are defined, as described in the following
points.
The selection process works always in QL-enabled mode, the selected synchronization clock source is
used to lock the NEC. The QL of the selected synchronization clock source determines the QL of the NEC,
unless the NEC is in Holdover mode.
The selection process has two nominated synchronization clock source inputs:
– Primary clock source input;
– Secondary clock source input.
For such sources the following selection criteria are defined:
– Clock Source Fail when the source is not available;
– Clock Source Degrade when the frequency of the source is away from its nominal value with the fol-
lowing rules: the degrade alarm will never be asserted if the actual frequency is within ±10 ppm of
its nominal value; the degrade alarm will always be asserted if the actual frequency is not within ±50
ppm of its nominal value;
– Clock Source Quality Level (QL) according to ITU-T G.781;
– Clock Source Quality Level Priority
According to Table 8 of ITU-T G.781 the Clock Source Quality Level is identified by the following SSM
Codes:
– 0010 - QL-PRC for timing quality generated by a primary reference clock as defined in ITU-T G.811;
– 0100 - QL-SSU-A for timing quality generated by a type I or V slave clock as defined in ITU-T G.812;
– 1000 - QL-SSU-B for timing quality generated by a type VI slave clock as defined in ITU-T G.812;
– 1011 - QL-SEC/QL-EEC1 for timing quality generated by a SEC or EEC as defined in ITU-T G.813/
ITU-T G.8262;
– 1111 - QL-DNU (Do Not Use).
Any other SSM Code values different from the ones listed above must be considered as an Invalid Quality
Level (QL-INV).
The QL of the NEC is advertised over radio interfaces and Synchronous Ethernet interfaces.
2.8.19.2.1 Quality Level Priority
A QL Priority parameter is defined for each node and assigned to synchronization clock sources and to
the NEC.
The QL Priority values are identified by the following codes:
– 0x00 - Undefined
– 0x01 - Master1

– 0x10 - Slave1
The QL Priority of the NEC is advertised, together with the QL, over radio interfaces.
The equipment shall be ready to advertise the QL Priority of the NEC over Synchronous Ethernet inter-
faces too.
The QL Priority is a proprietary parameter (not foreseen in G.781) introduced with the aim to deal with a
ring or meshed scenario where, due to a lack of external synchronization sources and failure on the syn-
chronization distribution path on the MPR wireless network, the synchronization distribution network is
partitioned in more than one isle each of them locked to a different oscillator in Holdover or Free-Run
mode.
2.8.19.2.2 Hold-off and Wait-To-Restore
In order to proper manage the QL-FAILED (Clock Source Fail or Clock Source Degrade) the automatic
selection process must take into account the Hold-Off time and Wait-To-Restore time defined in ITU-T
G.781:
– The Hold-Off time ensures that short activation of signal fail are not passed to the selection process.
The QL value of QL-FAILED is passed to the selection process after the Hold-off time. In the mean-
time, the previous QL value is passed to the selection process. The Hold-Off time is the same for
each input of the selection process and it is fixed to 500 ms.
– The Wait-To-Restore time ensures that a previous failed synchronization source is only again con-
sidered as available by the selection process if it is fault free for a certain time. When a Signal Fail
or Signal Degrade defects are cleared, the Wait-To-Restore time is applied before the new QL value
is passed to the selection process. In the meantime, the quality level QL-FAILED is passed to the
selection process. The Wait-To-Restore time is the same for each input of the selection process and
it is configurable in the range of 0 to 12 minutes in steps of 10 seconds. The default value is 5 minutes.
When changed before its expiration, the WTR time restart from the new value without take into
account the previous remaining time to expiration. The WTR time is also applied when a LOS of
ESMC defect is cleared on a synchronization clock source, also in that case the quality level QL-
FAILED is passed to the selection process until the WTR time expires.
2.8.19.3 Synchronization Sources assignment
The physical interfaces to be assigned to Primary and Secondary synchronization sources can be chosen
among the following:
[1] Free Run Local Oscillator. This source will never be affected by any alarm (no Fail, no Degrade).
Quality Level value is fixed to QL-SEC/EEC1 (G.812/G8262), the value of QL Priority is Master1 if
the NEC is configured as Master and Slave1 if the NEC is configured as Slave.
[2] Any E1 or T1 available at input traffic interfaces (the specific E1/T1 port has to be chosen). For these
sources the Fail alarm has to be detected by CRU when LOS, AIS or LOF (in case of E1s framed)
will happen. Default value for Quality Level is QL-SSU-A (G.812), the value of QL Priority is Master1
if the NEC is configured as Master and Slave1 if the NEC is configured as Slave.
[3] A specific synchronization signal available from the dedicated Sync-In port, which can be configured
according the following options:
a) 2.048 MHz, electrical levels according to G.703, clause 13;

b) 5 MHz, + 6 dBm into 50 ohm, sine-wave;
c) 10 MHz, + 6 dBm into 50 ohm, sine-wave;
d) 1.024 MHz, electrical levels according to G.703, clause 13 with the following exceptions:
– timing properly scaled from 2.048 MHz to 1.024 MHz.
For this source the Fail alarm is detected by CRU when LOS will happen. Default value for Quality
Level is QL-SSU-A (G.812), the value of QL Priority is Master1 if the NEC is configured as Master
and Slave1 if the NEC is configured as Slave.
[4] The Symbol Rate of the RX signal of any available Radio (the specific Radio Port has to be chosen).
For these sources the Fail alarm has to be detected by CRU when a DEM-Fail or a Loss of Radio
Frame will happen. When the SSM support is enabled the QL and QL Priority are acquired from
ESMC PDUs received on the specific radio interface. When the SSM support is disabled the default
value for Quality Level is QL-SSU-A (G.812), the value of QL Priority is Master1 if the NEC is con-
figured as Master and Slave1 if the NEC is configured as Slave.
[5] Any Synchronous Ethernet clock source available at enabled User Ethernet traffic interfaces (both
electrical and optical) configured in synchronous operation mode (the specific User Ethernet port has
to be chosen).
From ITU-T G.8261 point of view, the MSS is a Synchronous Ethernet equipment equipped with a
system clock (NEC) following the ITU-T G.8262 recommendation. A User Ethernet interface con-
figured in synchronous operation mode can work only at 1000 Mbit/s. In the particular case of elec-
trical User Ethernet interfaces, these interfaces perform link auto negotiation to determine the
master/slave role for clocks delivery over the link. The clock slave role must be configured as part
of auto negotiation parameters in order to use the interface as Synchronous Ethernet clock source
input, either as Primary or Secondary. This check is performed by WebEML/NMS but not by EC. The
clock master role must be configured as part of auto negotiation parameters in order to use the inter-
face as Synchronous Ethernet clock source output to distribute NEC to other equipments. For Syn-
chronous Ethernet clock sources from electrical User Ethernet ports the Fail alarm will be raised
when Loss of Synch (i.e. Ethernet Link Down) will happen. For Synchronous Ethernet clock sources
from optical User Ethernet ports the Fail alarm will be raised when Loss of Optical signal will happen.
[6] Any STM1 available at SDH input traffic interfaces (the specific STM1 port must be selected). For
these sources the Fail alarm will be raised when LOS, LOF, TIM, MS-AIS, or High BER happen.
Default value for Quality Level is QL-SSU-A (G.812), the value of QL Priority is Master1 if the NEC
is configured as Master and Slave1 if the NEC is configured as Slave.
[7] None of the above, this means that no physical synchronization interface is assigned to the syn-
chronization clock source input. In case of failure of the other clock source input the CRU enters the
Holdover state.

2.8.19.4 Synchronization sources assignment rules
Some rules have to be followed while assigning the Primary and Secondary clock sources:
The NEC has to be defined (configured) as Master or Slave.
– If a specific interface is chosen as Primary, it cannot be selected as Secondary too.
– If an E1/T1 is chosen to be Primary source, another E1/T1 coming from the same peripheral cannot
be selected as Secondary source and vice-versa.
– If an MPT radio interface is chosen to be Primary source, another MPT radio interface connected
to the same MPT Access peripheral cannot be selected as Secondary source and vice-versa.
– If an STM1 is chosen to be Primary source, another STM1 coming from the same peripheral cannot
2.8.19.5 Allowed synchronization sources assignment
Only one Master is allowed in the network.
If Master:
– The Restoration Mode must be chosen between Revertive and Non-Revertive;
– The Primary clock source input must be chosen among 1), 2), 3), 5) or 6).
If the selected Master Primary clock source input is 1):
– the Master Secondary clock source input doesn't need to be selected because the Primary is never
supposed to fail. If the selected Master Primary clock source input is 2), 3), 5) or 6):
– the Master Secondary clock source input must be selected among 1), 2), 3), 5), 6) or 7).
If Slave:
– The Restoration Mode is fixed to Revertive.
– The Primary clock source input must be chosen among 3), 4) or 5). Slave Primary clock source input
is allowed to be 3) or 5) for full indoor configuration and for Piling configuration.
– The Secondary clock source input must be chosen among 1), 2), 3), 4), 5), 6) or 7).
2.8.19.5.1 QL and QL Priority configuration
In the current release the QL of synchronization interfaces is not configurable by the operator and, when
applicable, takes the default values.
The QL Priority of the node is not configurable by the operator.

2.8.19.5.2 Synchronization Source with MPT
In order to use the symbol rate of the Rx signal of an MPT as selectable synchronization source for the
NEC, the following is needed:
– if an Optical Ethernet connection is used, then the optical Ethernet port of MPT must be locked, at
transmission, to symbol rate of the Rx signal;
– if an Electrical Ethernet connection is used, it shall be Synch-E capable, meaning that a common
clock at physical layer level, not locked to the NEC, is available between MSS and MPT for a dif-
ferential clock recovery method based on custom time-stamp protocol (referred to Symbol Rate of
the air Rx Signal).
2.8.19.5.3 Synchronization Source with MPT PFoE Access peripheral
MPT Access peripheral performs the clock recovery for each connected MPT, one of them can be selected
to be used as Primary synchronization Source.
2.8.19.5.4 Protected radio configuration with one MPT PFoE Access peripheral
When MPTs in protected configuration are connected to one MPT Access peripheral only, the MPT Access
peripheral selects, from the MPT in EPS active state, the clock signal to be used as synchronization
Source.
2.8.19.5.5 Protected radio configuration with 2 MPT PFoE Access peripheral
When MPTs in protected configuration are connected to two MPT Access peripherals, both MPT Access
peripheral, for the radio direction configured as synchronization Source, forwards its own recovered clock
signal.
This clock will be then selected according to the correspondent EPS state for MPT and MPT Access
peripheral.

2.8.20 Synchronization for E1 ports with ASAP unit
The synchronization of each E1 ATM port in the ASAP unit can be configured (by the WebEML) in two
ways:
– Loop-timed: the transmit clock is derived from the E1 clock source received
– Node-timed: the transmit clock is the NE clock
The E1 ports belonging to the same IMA group must have the same configuration.
2.8.21 Synchronization distribution from 9500 MPR to 9400 AWY

The Synch Out connector (set to 1024 kHz) through a cable can be connected to 9400 AWY to transfer
the synchronization to 9400 AWY.
Two types of interconnections can be implemented:
1) from Synch Out connector to one E1 connector of the 9400 AWY E1 distributor by using the
5 m microcoaxial cable 1.0/2.3 M 90 M 90 (3CC 52138 AAAA);
2) from Synch Out connector to the SCSI connector of 9400 AWY by using a dedicated cable as
shown in Figure 84.
N.B. With this second solution 9400 AWY must be used to transport Ethernet traffic only.
Install the Ethernet

Data plug-in
Figure 84. Synchronization distribution from MPR to AWY
N.B. The cable, not connected in the figure, can be connected to the Synch In connector of another
MPR to transfer the synch from AWY to MPR.

2.8.22 Synchronization connection in Stacking configuration with Core protection
In case of Stacking configuration with Core protection the two MPR must be synchronized as shown in
Figure 85.
Figure 85. Synchronization connection in Stacking configuration with Core protection
For more details refer to par. 4.1.4.11.

3 NE Management by software application
3.1 WebEML start

This chapter explains all the screens of the WebEML, which is started by a double click on the WebEML
icon of the PC desktop.
The PC must be connected to the TMN port of the Core-E unit in the MSS.
Refer to paragraph 4.2.4 - “Local copy of the WebEML and TCO Suite Software to PC” to get all the infor-
mation to copy the WebEML from the software package CD ROM and to connect the PC to the MSS-1c.
1) Start the WebEML by double click on the relevant icon on the PC desktop.
2) NEtO opens. Insert the IP address of the NE (default: 10.0.1.2) and click OK.
For more details on NEtO refer to paragraph 3.20 - “Annex A: Network Element Overview” on
page 474.
N.B. To access the NE the PC must be configured to “Get automatically an IP address”,

because the NE is configured as DHCP Server with default IP address 10.0.1.2.

NE Management by software application 3DB 18793 AAAA Issue 1 199/876
3) When the NE is supervised, click Show.
4) The Main view opens (refer to par. 3.2).

200/876 3DB 18793 AAAA Issue 1 NE Management by software application
3.2 WebEML Main View
The Main View Area manages all domains from which the operator can start. It is organized with tab pan-
els, e.g. many windows placed one upon another. Each window is selectable (placing it on top of the oth-
ers) with a tab shown on the top.
Two Main views are shown according to the MSS version:
– MSS-8 (refer to Figure 86)
– MSS-4 (refer to Figure 87)
Figure 86. MSS-8 Main view

Figure 87. MSS-4 Main view
3.2.1 Tab-panels
Each tab-panel represents a set of functions. The following tab-panels are present:
– Equipment (to manage the equipment configuration)
– Schemes (to manage the protection schemes in 1+1 configuration)
– Synchronization (to manage the synchronization)
– Connections (to manage the cross-connections)
The following figure shows the Main view organization.
Each tab-panel consists of three areas:
– Resource-Tree Area: displays all the available resources of the NE.
– Resource-List Area: may be represented by: Tabular View or Graphical View.
• Tabular View: displays a tabular representation of the selected resource. As default, no tabular
element is shown.
• Graphical View: displays a graphical representation of the selected resource. As default, no

tabular element is shown.
– Resource-Detail Area: displays detailed information of a selected item in the Resource List area.
As a default, no entry view is displayed as a consequence of the default behavior of the Resource
List area.

Figure 86. is the entry point of the application and provides basic diagnostic and configuration functions.
Following multiple main views are available:
– Equipment view, for Equipment configuration;
– Radio view, for Radio domain (double click on a Radio unit);
– PDH view, for PDH domain (double click on a PDH unit);
– SDH view, for SDH domain (double click on an SDH unit);
– ATM view, for ATM domain (double click on an ASAP unit);
– AUX view, for Auxiliary channel domain (double click on the AUX peripheral unit);
– Core-E view, for Core-E and Ethernet domain (double click on a Core-E unit).
Navigation from main view to multiple main views (related to the equipment components) can be done
by simply double-clicking on the component graphical representation. Such operation will open a new win-
dow containing selected secondary view. Starting from main view, the operator will also see all slots and
ODUs layout. Each slot contains schematics of available board (if present) together with status and other
details. Slots schematics will in fact contain usual alarms information with a clarifying coloured icon that
reports the same icon visible in tree view.
Other icons are:

– On the right of the unit front panel, a new icon could be a check mark ( ) or a switch symbol ( ).
• : it means the slot is “active”;
• : it means the slot is in “stand-by” mode.

– As shown in Figure 86., an X-shaped icon ( ) will be added on the left to slots when some cross
connections are related to it.
3.2.2 Main Tool Bar Area

This area contains a selection of handy quick-access buttons for common features.
– Left arrow to previous screen;

– Second button: not operative;
– Right arrow to next screen;
– Block Diagram View (refer to par. 3.5.5 on page 314);
– Current Configuration View (refer to par. 3.5.6 on page 329);
– Cross-Connections (refer to par. 3.4.5 on page 220);
– Segregated ports (refer to par. 3.4.5.1.5 on page 224);
– AUX Cross Connections (refer to par. 3.4.6 on page 256);
– VLAN management (refer to par. 3.19 on page 469).
– WT Performance Monitoring Suite (refer to par. 3.18 on page 432).

3.2.3 Severity Alarm Area
The WebEML provides an alarm functionality that informs the operator on the severity of the different
alarms in the NE as well as on the number of current alarms. There are five different alarm severity levels.
In the WebEML these different levels are associated with colors.
– Red: Critical alarm (CRI).
– Orange: Major alarm (MAJ).
– Yellow: Minor alarm (MIN).
– Cyan: Warning alarm (WNG).
– Blue: Indeterminate (IND).
N.B. The meaning of the icons in the Severity alarm synthesis is:
[1] CRI - Critical alarm

Synthesis of alarms that needs immediate troubleshooting (typical: NE isolation).
[2] MAJ - Major (Urgent) alarm

Synthesis of alarms that needs immediate troubleshooting.
[3] MIN - Minor (Not Urgent) alarm

Synthesis of alarms for which a deferred intervent can be decided.
[4] WNG - Warning alarm

Synthesis of alarms due to failure of other NE in the network.
[5] IND - Indeterminate alarm

Synthesis of alarms not associated with the previous severities. Not operative.
Each alarm severity is represented by an alarm icon situated in the top left hand corner of the view. These
alarm icons are constantly represented on the different Equipment views (NE view, Board view or Port
view) so that the operator is always aware of the alarms occurring in the system.
Furthermore the shape of the alarm icons in the alarm panel gives an indication of the occurrence of
alarms.
An alarm icon with a circle inside it (and a number at the bottom of the icon) indicates that alarms of the
number and the type defined by the icon are occurring.
An alarm icon with a rectangle inside it indicates that no alarms of the type defined by the icon are occur-
ring.
An alarm icon grayed out indicates that spontaneous incoming alarm notification have been inhibited.

3.2.4 Domain Alarm Synthesis Area
This area contains the bitmaps (more than one) representing the alarms per domain. Each bitmap indi-
cates the number of alarm occurrences for each domain.
The meaning of the icons in the Domain alarm synthesis area is:
[1] EXT - External Point

Synthesis of the External Points (Housekeeping alarms).
[2] EQP – Equipment alarm

Synthesis of alarms of the Equipment domain.
[3] TRS – Transmission alarm

Synthesis of alarms of the Transmission domain.
3.2.5 Management State Control Area

The different management states concerning the NE are also represented via icons located in the top right
corner of the equipment views. These icons are (from up to down):
[1] Icon with a key symbol: Local Access state: indicates whether the NE is managed by a WebEML
or by the OS
[2] COM icon: Operational state: indicates whether or not the communication with the OS is established.
[3] SUP icon: Supervision state: indicates whether or not the NE is under OS supervision.
[4] OS icon: OS isolation.
[5] NTP Server Status icon.
[6] AC icon: abnormal condition state: indicates whether some abnormal conditions have been recog-
nized. The operator can visualize them with the Diagnosis → Abnormal condition list menu.
N.B. As for the alarm icons, a rectangular management state icon represents the stable state while
a circular icon shape represents an unstable management state.
The meaning of the icons in the Management State Control Panel is:
[1] Local Access State

GREEN LED: Indicates that the WebEML has the OS permission to manage the NE (granted).
CYAN LED: Indicates that the WebEML has not the OS permission to manage the NE (denied).
[2] COM – NE reachable/unreachable

GREEN LED: Identifies the “Enable” operational state of the connection between NE and WebEML
(link down).
RED LED: Identifies the “Disable” operational state of the connection between NE and WebEML (link
down).
[3] SUP – Supervision state

GREEN LED: NE is under supervision
BROWN LED: NE is not under supervision
Used in the OS.

[4] OS – OS isolation
[5] NTP – Network Timing Protocol

BROWN LED: Protocol disabled
GREEN LED: Protocol enabled, but the two servers are unreachable.
CYAN LED: Protocol enabled and at least one of the two servers is reachable.
[6] AC – Abnormal Condition

GREEN LED: Normal operating condition.
CYAN LED: Detection of an ABNORMAL operative condition. Type: switch forcing.
3.2.6 Selection Criteria

Each tree node consists of possibly three symbols and a label. The first optional symbol indicates structure
state: if symbol is , three can be expanded showing its contained lower levels. Tree structure can be
collapsed if symbol is . With no symbol, node represents a tree leaf. Second symbol is the graphical
representation of resource itself. Third symbol is alarm status of component. The operator can select
resource by clicking with mouse to perform the action dependent on click type. Resource Detail Area
related to the selected item is displayed.
Each resource listed above may be selected by using the mouse by a:
– Single left click;
– Double left click
Single left click:
By a single left click the resource is highlighted. This selection causes the activation of the resource list
area, e.g., every time the operator selects a resource in the resource tree area the corresponding data
are displayed in the “Resource list area”.
Double left click:
Double click operation on resource tree items allows the operator expanding tree structure, so activating
the display/update of resource list area, that will display same information as for single click operation.
As soon as a node is expanded, another double click on such node would collapse tree structure to its
closed view.
Button Policy
The possible buttons for selection are the following:
– Apply this button activates the “modify”, but it does not close the window
– Cancel this button closes the window without modifying the parameters displayed in the window
– OK this button activates the modify and closes the window
– Close this button closes the window
– Help this button provides the help management for the functions of the supporting window.

3.3 How to configure a new equipment
The recommended sequence to configure the NE is the following:
[1] Enable the plug-in units: refer to TAB-PANEL EQUIPMENT (Equipment)
[2] Configure the Core-E unit: refer to Core-E VIEW for Core-E and ETHERNET DOMAIN (this menu
opens with double click on a Core-E unit) (Core-E domain)
[3] Configure the Radio unit or the MPT Access Unit: refer to RADIO VIEW for RADIO DOMAIN (this
menu opens with double click on a Radio unit) (Settings)
[4] Configure the PDH unit: refer to PDH VIEW for PDH DOMAIN (this menu opens with double click
on a PDH unit) (PDH unit configuration)
[5] Configure the SDH unit: refer to SDH VIEW for SDH DOMAIN (this menu opens with double click
on a SDH unit) (SDH unit configuration)
[6] Configure the 16xE1 ATM (ASAP) unit (if any): refer to ATM VIEW for ATM DOMAIN (this menu
opens with double click on an ASAP unit)
[7] Create Traffic Descriptors for ATM traffic: refer to MENU CONFIGURATION (Traffic Descriptors)
[8] Configure the LAGs (Ethernet or Radio) (if any): refer to MENU CONFIGURATION (Ethernet Fea-
tures Shell)
[9] Configure the AUX peripheral unit, if any, to enable the 64kbit/s service channels and to use the
external points: refer to AUX VIEW for AUX DOMAIN (this menu opens with double click on the AUX
Peripheral unit)
[10] Configure the Synchronization: refer to TAB-PANEL SYNCHRONIZATION (Synchronization)
[11] Configure the NE time: refer to MENU CONFIGURATION (NE Time)
[12] Configure the System parameters: refer to MENU CONFIGURATION (System Settings)
[13] Create the Cross-connections: refer to MENU CONFIGURATION (Cross-connections)
[14] Create the Auxiliary Service Channel cross connections, if the AUX peripheral unit has been
installed: refer to MENU CONFIGURATION (AUX Cross Connections)
[15] Configure IP/SNMP: refer to MENU CONFIGURATION (Network Configuration)
[16] Select the VLAN configuration and create VLAN, if required: refer to VLAN MANAGEMENT

3.4 Menu Configuration
3.4.1 Menu NE Time

The NE local time can be displayed and/or re-aligned to the OS time basis.
From the Configuration pull down menu, select the NE Time option.
The following dialogue box opens, from which the local NE time can be set.
The NE Time dialogue box displays the current NE time and the current OS time.
To re-align the NE time to the OS time, click on the Set NE Time With OS Time check box and click the
Apply pushbutton to validate.
The Refresh pushbutton causes the refresh of the screen.
The NTP Status field is a read-only field, which shows the configuration regarding the NTP (Network Time
Protocol), if the protocol has been enabled and configured in Menu Configuration → Network Config-
uration → NTP Configuration.
The NTP Status field shows:
– status of NTP (enabled/disabled);
– IP address of the Main Server, which distributes the time to all the NEs in the network;
– IP address of the Spare Server (IP address of a second NTP Server), which replaces the Main Server
in case of failure.

Note: If a change of Change Time Zone on the PC is applied with the JUSM opened, in order to make
it updated on WebEML Close/Open the JUSM application and Read Time another time.
3.4.2 Menu Network Configuration

To get access the Network Configuration option select the Configuration pull down menu.
The Network Configuration allows to perform the following operations:

Local Configuration: defines the local virtual NE address
NTP Configuration: defines the Network Time Protocol
Ethernet Configuration: not implemented
IP Configuration: which comprises:
IP static routing configuration: defines the Host/Network destination

address for IP static routing
OSPF Area configuration: defines the Open Shortest Path First address
IP Point-To-Point Configuration: defines the IP address of the interfaces

which use the PPP protocol (not implemented)
Routing information: shows a summary of the information relevant to the routing which has been
configured.

3.4.2.1 Local Configuration
Select the Configuration pull down menu.
Select the Network Configuration option and then, from the cascading menu, the Local Configuration
option.
The dialogue box opens, which allows to configure the local IP address of the NE.
This local IP address is the IP address associated to a virtual interface and to the other interfaces which
use the PPP protocol (the TMN-RF channels).
Default IP address: 10.0.1.2
Fixed default mask: 255.255.255.255
Apply button is used to perform a configuration change of the data contained in the dialogue box and
closes it; the dialogue is visible until the end of the operations and a wait cursor is displayed.
Close button closes the dialogue.
Help button provides some useful information on the dialogue.

3.4.2.2 NTP Configuration
This menu allows to enable the NTP (Network Time Protocol).
Put a check mark in the NTP protocol field to enable the protocol and write in the Main Server address
field the IP address of the server, which is in charge to distribute the time to all the NEs in the network.
In the Spare Server address field write the IP address of the Spare Server.
The Server reachability field is a read-only field, which shows the reachability of the NTP servers. The
following information can appear:
– "Main server reachable"
– "Spare server reachable"
– "None servers reachable"
– "Both servers reachable"
Click on Refresh to update the screen.
Click on Apply to send to the NE the NTP Configuration.
3.4.2.3 Ethernet Configuration
This menu is not implemented.

3.4.2.4 IP Static Routing Configuration
By selecting IP static routing configuration a dialog-box opens, which allows to configure the param-
eters for IP Static Routing Configuration.
The following fields and data are present:
[1] IP Address: allows to define the IP address to reach the specific host/network
[2] IP Mask: allows to define the IP Mask to reach a network
[3] Gateway IP Address: allows to define the address of the next hop gateway
[4] Interface type: allows to use point to point interfaces made available by the NE.
Apply button is used to perform a configuration change of the data contained in the complete table and
close the view; the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page.
Delete button is used to delete the selected page.
Close button closes the dialogue without changing of the data.
In the Host or Network Address Choice field select:
– Host to address to a single IP address;
– Network to address to a range of IP addresses.

This is the IP interface to a host or network. Typically used at a spur to interface a host over the RF path.
In this scenario, the Default Gateway IP Address is 0.0.0.0 and the IP Mask (greyed out) is 0.0.0.0. Also
typically used at an end terminal in a radio link for interface with the network.
In the Default Gateway or Point to Point I/F Choice select:
– Default Gateway IP Address for the Ethernet interface;
– Point to Point Interface Index for the NMS channels
WARNING: No pending (open) static routes are allowed.

The default software uses first the static routes and then the dynamic routes. An open
static route is always considered as a preferential path.
If in the screen the Default Gateway IP Address check box has been selected, write in the Default Gate-
way IP Address field below the relevant IP address.
By pressing Create pushbutton it is possible to create new or change existing IP static routes.
3.4.2.5 OSPF Area Configuration
By selecting OSPF Area Configuration a dialog-box opens, which allows to configure the parameters
for OSPF (Open Shortest Path First) Area Table Configuration.
The following fields and data are present:
– OSPF Area IP Address
– OSPF Area Stub
The fields give a synthetical information that includes all the addresses (specific to a NE and to a Network)
in an Area.
Apply button is used to perform a configuration change of the data contained in the complete RAP table
and close the view; the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page.

Delete button is used to delete the selected page.
Close button closes the dialogue without changing of the data.
WARNING: When the area is a Stub area, all the interfaces must be defined “Stub".
By pressing Create pushbutton a new screen opens.
N.B. 3 areas max. can be created.
In this new screen write the IP address, the IP mask and select the flag (True/False).
3.4.2.6 IP Point to Point Configuration
This menu is not implemented.
3.4.2.7 Routing Information
Select the Configuration pull down menu. Select the Network Configuration and then from the cas-
cading menu, the Routing information option.
A dialog-box opens: this screen is a read-only screen and displays the routing parameters currently active
on the NE.
The pushbutton Refresh allows to refresh the information shown in the screen.
The Close button closes the dialogue without changing of the data.

3.4.3 Menu Alarm Severities
By selecting the Alarm Severities option from the Configuration menu the screen in Figure 88. appears.
In this screen in the Profile Name field are listed the 4 default Alarm Severity Profiles:
– Profile "No Alarms". With this profile all alarms are disabled.
– Profile "All Alarms". This profile enables the emission of all the alarms.
– Profile "Radio Tx Alarms". This profile enables the emission of the Tx alarms of the radio link.
– Profile "Radio Rx Alarms". This profile enables the emission of the Rx alarms of the radio link.
Figure 88. Alarm Severities Profile
This screen is a read-only screen. It is only possible to select one Profile Name and display the relevant
alarms.
An Alarm Profile is the complete set of the equipment alarms with their severity in case of Service Affect-
ing situation and No Service Affecting situation.
Each alarm has its Service Affecting and No Service Affecting attribute, which can differ according to the
Alarm Severity Profile.
In the current release only to 3 objects in the equipment (MSS subrack, TMN local Ethernet, Radio) can
be assigned a specific Alarm Profile.
To do this association (in the example in the next Figure the MSS-8 object has been used):
1) Select the object to which an Alarm Profile has to be associated.
2) Click on the icon.

3) Select the Alarm Profile to be associated.
4) Put a check mark on the "Show details" box.
5) The list of the alarms with the relevant severity will appear.
6) Click on Apply to associate the Alarm Profile.

3.4.4 Menu System Settings
This menu allows the system configuration, providing the setting of some parameters for the NE setup.
The NE configuration tab-panel has 6 fields:
1) Tributary Port Configuration
2) Quality Of Service
3) DHCP
4) Admission Control for Adaptive Modulation (ODU300 only)
5) Ethernet LOS Criteria
6) Static Lag Criteria
7) Event and Alarm Log
8) NE MAC Address
Figure 89. System Settings menu

[1] Tributary Port Configuration
This field allows to set the suitable impedance of the E1 stream (Unbalanced 75 ohms/Balanced 120
ohm). To activate the new impedance, click on Apply.
[2] Quality Of Service
This field allows to set the suitable Quality Of Service (Disabled/DiffServ/802.1p). To activate the new
value, click on Apply.
The Ethernet switch provides a Quality of Service mechanism to control all streams. If the QoS is
disabled, all traffic inside the switch has the same priority; this means that for each switch port there
is only one queue (FIFO) therefore the first packet that arrives is the first that will be transmitted.
The following values are available:
• IEEE std 802.1p: the packet is examined for the presence of a valid 802.1P user-priority tag.
If the tag is present the correspondent priority is assigned to the packet;
• DiffServ: each packet is classified based on DSCP field in the IP header to determine the pri-
ority.
[3] DHCP
The DHCP server configures automatically IP address, IP mask and default gateway of the PC
Ethernet interface used to reach the NE. The PC must be configured to get automatically an IP
address.
The DHCP server uses an address pool of 10 IP addresses, defined according to the NE TMN port
IP address.
The IP mask is set to the mask of the NE TMN port and the default gateway is set to the NE IP
address.The lease time is fixed to 10 minutes.To activate the DHCP server, select Enabled and click
on Apply.
[4] Admission Control for Adaptive Modulation (ODU300 only)
The Admission Control for TDM flows (cross-connected to radio direction working in Adaptive Mod-
ulation) can be enabled or disabled. Default: “Enabled”.
When the Admission Control is "Enabled", the check is performed taking into account the capacity
of the 4 QAM modulation scheme for the relevant Channel Spacing.
Taking as example 28 MHz channel spacing (with around 130 Mbit/s of net throughput available
with 64QAM), the maximum number of E1s that could be provisioned is 18; the remaining capacity
is devoted to other types of traffic such as ATM or Ethernet.
When RSL value decreases, modulation schemes are downgraded, first from 64QAM to 16QAM:
the traffic with lower priority exceeding 16QAM bandwidth is dropped and of course the E1s are kept.
As soon as the RSL value further decreases, modulation scheme are downgraded to 4QAM and all
the traffic exceeding 4QAM bandwidth is dropped (while the E1s are kept). It should be noted that
there is no possibility to provision a number of E1s greater than 18, because being all the E1s with
the same priority, it should not possible from system point of view to decide "which" E1s should be
dropped passing from 16QAM to 4QAM. In order to facilitate provisioning and commissioning oper-
ations, a specific admission control check at WebEML level has been inserted, avoiding any potential
mistakes from the user provisioning a number of E1s that are not fitting inside 4QAM bandwidth.
When the Admission Control is "Disabled", the check is performed taking into account the capacity
of the highest modulation scheme for the relevant Channel Spacing (64 QAM for 4-16-64 QAM range
or 16 QAM for 4-16 QAM range).

it is possible to provision a number of E1s exceeding the 4QAM throughput; always keeping 28 MHz
channel as example, it is possible to provision more than 18E1s, up to 37E1s (value linked with
16QAM capacity). In this case, when RSL value degrades and modulation scheme is downgraded
from 16QAM to 4QAM, all the TDM traffic is impacted. This feature is answering the need of trans-
mitting an high number of E1s, but without giving up the benefits of adaptive modulation for Ethernet
traffic.
[5] Ethernet LOS Criteria
By enabling this feature the following additional criteria are added to the Core protection switching
criteria:
• LOS of Optical User Ethernet interface

• Card Fail of SFP optical module
• Card Missing of SFP optical module
• LOS of any Electrical User Ethernet interfaces, including the LOS of the forth User Ethernet
interface working as TMN Local Ethernet interface.
Note: the default switching criteria are:

• Core Card Missing
• Core Card Fail
• Control Platform operational status failure
• Flash Card realignment in progress
• Flash Card failure
[6] Static Lag Criteria
This feature is available only if the spare Core unit has been installed.
By enabling this feature the Ethernet ports of the Core-E unit in stand-by are in ON state (as the ports
of the Active Core-E unit), but the Ethernet traffic is not forwarded.
This behavior allows to reduce the out of service time (within few seconds) of user traffic passing
through the User Ethernet interfaces in case of Core protection switching.
This feature shall not be used, when the NE is connected to an equipment performing Link Aggre-
gation and not supporting Active/Standby management of aggregated links.
[7] Event and Alarm Log
As default the Logging is enabled. If set to "Disabled" the events are not sent to the Event Log
Browser application.
[8] NE MAC Address
This field is a read-only field, which shows the MAC address of the NE. This MAC address must be
used in the cross-connection with TDM2Eth profile.

3.4.5 Menu Cross connections
3.4.5.1 Main Cross Connection View
The Main view (refer to Figure 90.) is a graphical representation of Cross-connectable slots. Slots and
Ethernet ports (represented by “connectors”) are arranged according to the equipment configuration:
– There are a maximum of 6 Ethernet ports placed on the Core-E area in the left side of the screen.
Port 4 is visible only when set to “transport” mode. If Ethernet port 4 is set to “TMN”, icon 4 is not
shown. Port 5 and 6 are visible, if in the Core-E unit has been installed and enabled the SFP plug-in.
– There are a maximum of 6 PDH/SDH/ASAP/Radio/MPT-ACC slots (placed in the MSS-8 sub-rack)

or 2 PDH/SDH/ASAP/Radio/MPT-ACC slots (placed in the MSS-4 sub-rack).
N.B. In the following pages the examples will be done with MSS-8.
When two units are protected, the 2 protected slots are linked by a dashed line, (e.g.: Slot#5 RADIO is
protected with Slot#6 RADIO).
Figure 90. Main Cross-Connections View
Note
Ethernet port#5 and port#6 will appear only if the optional SFP plug-in has been installed and
enabled in the Core-E unit. To enable the SFP plug-in go to the Setting tab-panel of
the Core-E unit in the Equipment tab-panel.
Note
If Ethernet port#4 has been configured as TMN, the port does not appear
in the Main Cross-Connections view.

3.4.5.1.1 LAG area
If a LAG (Radio or Ethernet) has been created by using menu Configuration > Ethernet Features Shell
in the LAG area (on the right side of the screen) will appear the icons of the LAG with the identifying number
of the LAG.
Different icons are used to identify Radio LAG or Ethernet LAG.
The Ethernet ports involved in an Ethernet LAG are only present in the LAG area (not in the CORE-E
area).
In the Figure LAG #4 is a Radio LAG, LAG #1 is an Ethernet LAG.
Figure 91. LAG Radio and LAG Ethernet
3.4.5.1.2 Connectors
The connectors representing the MSS slots are start- and end-point for actual cross-connections. By
using the mouse drag-and-drop operations the operator can create cross-connections through these
points. These connectors have specific icons:
– identifies Ethernet RJ-45 connector (Ethernet ports)
– identifies PDH/SDH slots
– identifies Radio slots (to interface ODU300)
– identifies MPT-ACC slots (to interface MPT-HC)
– identifies Radio LAG

– identifies Ethernet LAG
The connectors have different colours depending on the associated slot’s state:
– White: a connector able to accept a cross-connection and has no active cross-connection yet;
– Green: a connector able to accept a cross-connection and already has one active cross-connection
at least;
– Blue: a connector not able to accept a cross-connection.
After a cross-connection creation between the points, their state will change and a line will be drawn
between the two cross-connected points (see Figure below).
Figure 92. Cross-connections Example

3.4.5.1.3 Graphical Area
This area contains a panel and various components representing NE cross-connectable slots (or con-
nectors). The operator can directly edit with the mouse this graphical area to visually create and modify
cross-connections between available connectors: the Figure below shows an example of ongoing cross-
connections configuration.
Figure 93. Creating cross-connection between PDH and radio
Some steps (modification dialogs, see paragraph below) would differ depending on cross-connection
types.
3.4.5.1.4 Buttons
Figure 94. Cross-connections buttons
At the bottom in the menu there are three buttons:
– Apply: will apply changes (if any) to NE. After they’ve been applied it will update graphical state by
performing a refresh; if the operation completes without errors the sub-sequent refresh won’t pro-
duce any visual change (in other words, the state of the NE will be consistent with what is shown
in the GUI) anyway, clicking on Apply button will show a progress dialog.
– Refresh: reload the data from the NE and update the graphical state; any modification performed
and not applied will be lost.
– Close: close the cross-connection view, and return to the caller (JusmMainView), any modification
performed and not applied will be lost.
– Help: opens the Help On Line.

3.4.5.1.5 Segregated port view
From the Cross Connection view by pressing Alt+W the Segregated Port view opens.
Figure 95. Segregated Port View (default configuration)
In the default configuration (shown in Figure 95.) all the slots and Ethernet ports in Core-E unit are cross-
connectable each other (all the slots/ports are not segregated).
To go back to the Cross Connection View press Alt+W.
Note: The MPT Access unit ports can be segregated from each other, but they cannot be individually
segregated with other ports belonging to other units.
Only the complete MPT Access unit can be segregated with other ports.
3.4.5.1.5.1 How to segregate slots or ports
Double click on a slot icon or an Ethernet port icon and select the slots/ports that can be connected (this
means that the not selected slots/ports cannot be connected; they are segregated).
Example: with a double click on the icon of Slot#5 RADIO Figure 96. opens.
Figure 96.
To segregate Slot#5 RADIO from Ethernet ports#2, #3, #4, #5 in the Core-E unit, click on the relevant
square to remove the check mark, as show in Figure 97.

Figure 97.
By clicking OK the Segregated Port view opens, which now shows (with dashed lines) the segregated
ports, as shown in Figure 98.
Figure 98. Segregated Ports
With the mouse pointer on a dashed line the following message will appear: "Dashed lines mean that these
ports cannot be cross-connected".

3.4.5.2 How to create a cross-connection
A cross-connection between two points is performed by:
1) Moving the mouse pointer on the source slot;
2) Press the left button and, while keeping button pressed, move mouse pointer onto destination slot;
3) Release the left button.
If the action involves two cross-connectable slots, a dialog will appear allowing the operator to setup a
cross-connection. Looking at Figure 99., it is possible to see different aspects of configuration created by
the operator:
– Slot#8 PDH is cross-connected to Slot#5 radio ODU300, to Slot#4 MPT-ACC and to Ethernet Port#1;
– Slot#4 MPT-ACC is cross-connected to Ethernet Port#1;
– Slot#5 RADIO (and Slot#6 RADIO) are cross-connected to Ethernet Port#2;
– Slot#3 MPT-ACC is cross-connected to Slot#4 MPT-ACC;
– Ethernet Port#3 PDH (blue) could not accept cross-connections;
– Slot#3 and Slot#4 (green) could accept more cross-connections;
– Slot#5 and Slot#6 are in 1+1 configuration.
Each connection line is coloured according to slots types it connects (as shown in Figure 99.):
– PDH-Radio connection: black line;
– SDH-Radio connection: black line;
– ATM-Radio connection: orange line;
– PDH-Eth connection: blue line;
– ATM-Eth connection: magenta line;
– Radio-Radio connection: red line;
– Radio-Eth line: green line.
These colours will be applied to the graphical area, when the operator releases the mouse button above
cross-connection destination slot.
Note: the ATM cross-connection lines have the following colours:
– ATM-Radio connection: orange line;
– ATM-Eth connection: magenta line.
In the types of cross-connections above Eth means "Ethernet User Port" or "Ethernet LAG" and Radio
means "Radio to interface ODU300" or "Radio LAG".

Figure 99. Actual coloured view example
3.4.5.2.1 Creation Dialogs
When connecting two linkable slots through a cross-connection, a dialog will appear, close to the desti-
nation point. This dialog contains connection information, depending on start- and end-point of connection
itself. Each cross-connection has different parameters and required data and information will depend on
ongoing cross-connecting. Dialog boxes can ask for specific Flow Ids through a set of checkboxes, a field
to fill-in “external” (incoming) Flow Ids, Ethernet parameters and so on. All the dialog boxes have a specific
title describing the building cross-connection; this states both slots numbers and types.
The “Ok” button will visually save the current modifications (this means that data are graphically saved
only, not sent to the NE!).
The “Cancel” button will graphically discard ongoing cross-connection, keeping the previous graphical.
3.4.5.2.2 Information Dialogs
By using the right-click button, the operator can gain information about the graphical representation of the
cross-connections. This information can be obtained on both connectors and connection lines. The oper-
ator can perform different actions in the area, depending on target and mouse-click type:
– Connector, right click: a dialog with information about all selected tributaries for that connector will
appear.
– Line, right click: a dialog with information about selected tributaries for that line will appear.

3.4.5.2.3 TDM Cross-Connections
The Cross-connections to be implemented are:
[1] PDH to Radio/MPT-ACC
[2] Radio to Radio or MPT-ACC to MPT-ACC or Radio to MPT-ACC or MPT-ACC to Radio
[3] Radio/MPT-ACC to Eth
[4] PDH to Eth
After a cross-connection has been created, two cross-connected slots are visually linked by a line: a line
in the context of this application represents a bundle of flows, which share same source and destination
entity.
[1] PDH to Radio/MPT-ACC
By dragging a connection between a PDH slot and a Radio slot or MPT-ACC slot, the operator will see
the configuration dialog in Figure 100.
Configuration parameters will ask to specify Flow ID number, as associated in PDH slot.
Figure 100. PDH to Radio configuration dialog
Once correctly completed the cross-connection configuration and clicked on “OK” button, the operator will
see a black line describing the PDH to Radio cross-connection defined (see Figure 101.).

Figure 101. Completed PDH to Radio cross-connection
By dragging a connection between two different Radio slots, the operator will see the configuration dialog
in Figure 102.
To create other cross-connections drag other lines between the two radio slots and repeat the operations.
Figure 102. Radio to Radio configuration dialog

Configuration parameters will introduce Flow ID number, as coming from remote radio signal, and a
parameter related to profile and TDM Clock Source. The operator has to fill in data to complete the cross-
connection configuration. The operator can use ranges and values.
To create in one shot several cross-connections the operator can use in the Flow Id field the notation
[n-m] to create all Flow IDs from n to m, both included. If the operator wants to specify different Flow Ids
grouping them without using ranges, commas can used to separate values.
For example:
– by entering in the FlowId field 10-15 in one shot will be created all the cross connections from FlowId
10 to FlowId 15 (10 and 15 included);
– by entering in the FlowId field 10, 200, 250 in one shot will be created the cross connections with
FlowId 10, FlowId 200 and FlowId 250.
It is not possible to merge the two solutions (ranges and values) by writing [n-m],[a-b], ... and so on. Based
on used input style (ranges or values), the operator will see two different confirmation dialogs.
see a red line describing the Radio to Radio cross-connection defined (see Figure 103.).
Figure 103. Completed Radio to Radio cross-connection

[3] Radio/MPT-ACC to Ethernet
By dragging a connection between a Radio slot and an Ethernet port, the operator will see the configu-
ration dialog in Figure 104.
Figure 104. Radio/MPT-ACC to Ethernet configuration dialog (ranges)
By using [n-m] the operator will specify adding all Flow IDs from n to m, both included. If the operator wants
to specify different Flow Ids grouping them without using ranges, it can use commas to separate values,
as in Figure 105.
Figure 105. Radio/MPT-ACC to Ethernet configuration dialog (values)

It is not possible to merge the two solutions (ranges and values) by writing [n-m],[a-b], … and so on. Based
see a green line describing the Radio/MPT-ACC to Ethernet cross-connection defined.
Figure 106. Completed Radio/MPT-ACC to Ethernet cross-connection
[4] PDH to Ethernet
By dragging a connection between a PDH slot and an Ethernet port, the operator will see the configuration
dialog in Figure 107.
To create other cross-connections drag other lines between the PDH slot and the Ethernet port and repeat
the operations.
Figure 107. PDH to Ethernet configuration dialog

Configuration parameters will introduce Flow ID number, as associated in PDH slot, and all parameters
related to such Flow ID. The operator has to put the correct MAC address to complete the cross-con-
nection configuration.
be able to see a blue line describing the PDH to Ethernet cross-connection defined (see Figure 108.).
Figure 108. Completed PDH to Ethernet cross-connection
Considering a connection to Ethernet ports, when a port reaches its full capacity, the operator will see a
specific report.
WARNING: Cross-Connections with TDM2Eth Service Profile
In these types of cross-connections the destination MAC address of the adjacent NE (unicast address in
case of unprotected configurations, multicast address in case of protected configurations) must be
inserted during the cross-connection creation. In the following figures are given 3 examples.
Figure 109. No protection

Figure 110. 1+1 radio protection between NE B and C
Figure 111. 1+1 EPS protection in NE A
Note
The unicast MAC address of the NE is shown in the System Settings menu (Bridge Address)
To assign the multicast MAC address of a NE start from the unicast MAC address and change a digit in
the first pair of digits in order to generate an odd binary number: example change the first pair of the
address from 00 to 01.
3.4.5.3 How to modify a TDM cross-connection
An existing cross-connection can be modified by double-clicking with the left mouse button on its symbolic
line.
Now from the screen you have to delete the cross-connections by removing the check mark from the rel-
evant Flow Id box and create again a new cross-connections.
3.4.5.3.1 PDH to Radio/MPT-ACC
In Figure 112., the operator is modifying a previously created cross-connection (in this case Slot#8 PDH
and Slot#5 radio): this action brings up a dialog almost like the creation one, but with some differences
in allowed actions:
– Previously assigned tributaries (400 to 405 in the example) are active and selected;

– Tributaries assigned to another cross-connection (406 to 431) are not active and not selected.
Figure 112. PDH to Radio cross-connection modification
3.4.5.3.2 Radio to Radio or MPT-ACC to MPT-ACC or Radio to MPT-ACC or MPT-ACC to Radio
The operator can click on a specific (red) line in order to modify connection parameters. With a double
click with the mouse on the connection line, the dialog window shown in Figure 113. will appear.
Figure 113. Modifying a Radio to Radio cross-connection
Remove the check mark and create again a cross-connection.

3.4.5.3.3 Radio/MPT-ACC to Ethernet
The operator can click on specific (green) line in order to modify connection parameters. With a double
click with the mouse on the connection line, the dialog window shown in Figure 114. can be managed by
the operator.
Figure 114. Modifying a Radio/MPT-ACC to Ethernet cross-connection

3.4.5.3.4 PDH to Ethernet
The operator can click on specific (blue) line in order to modify connection parameters. With a double click
with the mouse on the connection line, the dialog window shown in Figure 115. can be managed by the
operator.
Figure 115. Modifying a PDH to Ethernet cross-connection
3.4.5.4 SDH Cross-Connections
[1] SDH to Radio/MPT-ACC
entity.
[1] SDH to Radio/MPT-ACC
By dragging a connection between a SDH slot and a Radio slot or MPT-ACC slot, the operator will see
the configuration dialog in Figure 116.
The Flow ID is automatically recognized as associated to the SDH slot.

Figure 116. SDH to Radio configuration dialog
Once correctly completed the cross-connection configuration and clicked on "OK" button, the operator will
see a black line describing the SDH to Radio cross-connection defined (see Figure 117.).
Figure 117. Completed SDH to Radio cross-connection

By dragging a connection between two different Radio slots, the operator will see the configuration dialog
in Figure 118.
Figure 118. Radio to Radio configuration dialog
Configuration parameters will introduce Flow ID number, as coming from remote radio signal, and the pro-
file. The operator has to fill in data to complete the cross-connection configuration.
see a red line describing the Radio to Radio cross-connection defined (see Figure 119.).
Figure 119. Completed Radio to Radio cross-connection

3.4.5.5 How to modify an SDH cross-connection
line.
evant Flow ID box and create again a new cross-connections.
3.4.5.5.1 SDH to Radio/MPT-ACC
In Figure 120., the operator is modifying a previously created cross-connection (in this case Slot#8 SDH
and Slot#4 MPT-ACC): this action brings up a dialog almost like the creation one, but with some differ-
ences in allowed actions:
– Previously assigned STM-1 (222 in the example) is active and selected;
– In the example of the figure there is no other Flow ID and for this reason it is not possible to create
another cross-connection.
– Select the Flows ID and click OK to remove the cross-connection, then click Apply.
Figure 120. SDH to Radio cross-connection modification

3.4.5.5.2 Radio to Radio or MPT-ACC to MPT-ACC or Radio to MPT-ACC or MPT-ACC to Radio
3.4.5.6 ATM Cross-Connections
[1] ASAP-Radio
[2] Radio-Radio
[3] Radio-Eth
[4] ASAP-Eth
entity.
[1] ASAP to Radio
By dragging a connection between an ASAP slot and a radio slot, the operator will see the configuration

Configuration parameters will ask to:
– select the ATM interface (this interface is the IMA group: from 1 to 8)
– select the PW label
– enter the VPI
– assign the VLAN ID
– enter the Destination MAC Address (only with MPT-HC or MPT-MC), as shown in Figure 123..
N.B. The Traffic Descriptor is automatically created.
N.B. ATM "Light" Cross-connection Provisioning

In this release when a cross-connection toward a radio direction with MPT is involved, the
related provisioning is performed in almost the same way as with ODU300, with the following
main differences:
– MAC DA is also explicitly provisioned in the NE acting as TPE role
– admission control, in terms of checking bandwidth required bt ATM PW flow against the
available bandwidth on radio interface, is never performed.
see an orange line describing the ASAP-radio cross-connection defined (see Figure 124.).
Figure 122. ASAP-Radio configuration dialog (ODU300)

Figure 123. ASAP-Radio configuration dialog (MPT-HC or MPT-MC)
Figure 124. Completed ASAP-radio cross-connection

[2] Radio to Radio
The ATM Radio-Radio Cross-connections can be implemented between ODU300-ODU300, MPT-MPT

but not between ODU300-MPT.
By dragging a connection between two different radio slots, the operator will see the configuration dialog
in Figure 125.
Figure 125. Radio-radio configuration dialog
Configuration parameters are:

– select the Service: ATM or PW3
– associate the Traffic Descriptor by clicking on Browse and selecting a Traffic Descriptor previously
created. (Note: an ATM PW is made up of two undirectional flows).
Figure 126. Traffic Descriptor

The operator has to fill in data to complete the cross-connection configuration.
Figure 127. Completed radio-radio cross-connection
[3] Radio to Ethernet
By dragging a connection between a Radio slot and an Ethernet port, the operator will see the configu-
ration dialog in Figure 128.
– select the Service: ATM or PW3
– enter the Destination MAC address
– associate the Traffic Descriptor by clicking on Browse and selecting a Traffic Descriptor previously
created. (Note: an ATM PW is made up of two undirectional flows).

Figure 128. Radio-Ethernet configuration dialog
see a green line describing the Radio-Ethernet cross-connection defined.
Figure 129. Completed Radio-Ethernet cross-connection

[4] ASAP to Ethernet
By dragging a connection between an ASAP slot and an Ethernet port, the operator will see the config-
uration dialog in Figure 130.
To create other cross-connections drag other lines between the ASAP slot and the Ethernet port and
repeat the operations.
Figure 130. ASAP-Ethernet configuration dialog
– select the ATM interface
– enter the VPI
– enter the Destination MAC address
N.B. The Traffic Descriptor is automatically created.
The operator has to put the correct Destination MAC address to complete the cross-connection config-
uration.
be able to see a green line describing the ASAP-Ethernet cross-connection defined (see Figure 131.).

Figure 131. Completed ASAP-Ethernet cross-connection
Considering a connection to Ethernet ports, when a port reaches its full capacity, the operator will see a
specific report.

3.4.5.7 How to modify an ATM cross-connection
line.
evant Flow Id box and create again a new cross-connections.
3.4.5.7.1 ASAP to Radio
In Figure 132., the operator is modifying a previously created cross-connection: this action brings up a
dialog almost like the creation one:
– Previously assigned tributaries (111 in the example) are active and selected;
– Tributaries assigned to another cross-connection are not active and not selected.
Figure 132. ASAP-radio cross-connection modification
Select the ATM interface and remove the check mark and create again a cross-connection.
3.4.5.7.2 Radio to Radio
Figure 133. Modifying a Radio-Radio cross-connection
Select the ATM Service and remove the check mark and create again a cross-connection.

3.4.5.7.3 Radio to Ethernet
The operator can click on specific (green) line in order to modify connection parameters. With a double
click with the mouse on the connection line, the dialog window shown in Figure 134. can be managed by
the operator.
Figure 134. Modifying a Radio-Ethernet cross-connection
Select the ATM Service and remove the check mark and create again a cross-connection.
3.4.5.7.4 ASAP to Ethernet
The operator can click on specific (blue) line in order to modify connection parameters. With a double click
with the mouse on the connection line, the dialog window shown in Figure 135. can be managed by the
operator.
Figure 135. Modifying an ASAP-Ethernet cross-connection
Select the ATM interface and remove the check mark and create again a cross-connection.

3.4.5.8 LAG-LAG Cross-Connections
Two types of cross-connections can be implemented:
[1] Ethernet LAG - Radio LAG cross-connections
[2] Radio LAG - Radio LAG cross-connections
3.4.5.8.1 Ethernet LAG - Radio LAG cross-connections
By dragging a connection between a Radio LAG icon and an Ethernet LAG icon, the operator will see the
configuration dialog in Figure 136.
Figure 136. Radio LAG to Ethernet LAG configuration dialog
Configuration parameters will introduce the Service (TDM or ATM), Flow ID number and all parameters
related to such Flow ID. The operator has to put the correct MAC address to complete the cross-con-
nection configuration.
be able to see a green line describing the Radio LAG to Ethernet LAG cross-connection defined (see Fig-
ure 137.).

Figure 137. Completed Radio LAG to Ethernet LAG cross-connection
To create other cross-connections drag other lines between the Radio LAG and the Ethernet LAG and
repeat the operations.
3.4.5.8.2 Radio LAG - Radio LAG cross-connections
By dragging a connection between two different Radio LAG icons, the operator will see the configuration
Figure 138. Radio LAG to Radio LAG configuration dialog

Configuration parameters will introduce the Service (TDM or ATM), Flow ID number, as coming from
remote radio signal, and a parameter related to profile and TDM Clock Source. The operator has to fill
in data to complete the cross-connection configuration. The operator can use ranges and values.
To create in one shot several cross-connections the operator can use in the Flow ID field the notation [n-
m] to create all Flow IDs from n to m, both included. If the operator wants to specify different Flow IDs
grouping them without using ranges, commas can used to separate values.
For example:
– by entering in the FlowId field 10-15 in one shot will be created all the cross connections from FlowId
10 to FlowId 15 (10 and 15 included);
– by entering in the FlowId field 10, 200, 250 in one shot will be created the cross connections with
FlowId 10, FlowId 200 and FlowId 250.
It is not possible to merge the two solutions (ranges and values) by writing [n-m],[a-b], ... and so on. Based
see a red line describing the Radio LAG to Radio LAG cross-connection defined (see Figure 139.).
Figure 139. Completed Radio LAG to Radio LAG cross-connection

3.4.5.9 How to modify a LAG-LAG cross-connection
line.
evant Flow ID box and create again a new cross-connections.
3.4.5.9.1 Ethernet LAG to Radio LAG
In Figure 140., the operator is modifying a previously created cross-connection (in this case Radio LAG
#2 SDH and Ethernet LAG #24): this action brings up a dialog almost like the creation one, but with some
differences in allowed actions:
– Previously assigned Flow ID (654 in the example) is active and selected;
– Select the Service and the Flows ID and click OK to remove the cross-connection, then click Apply.
Figure 140. Ethernet LAG to Radio LAG cross-connection modification

3.4.5.9.2 Radio LAG to Radio LAG
– Previously assigned Flow ID (654 in the example) is active and selected;
– Select the Service and the Flows ID and click OK to remove the cross-connection, then click Apply.

3.4.6 AUX Cross Connections
Two types of AUX Cross-Connections can be implemented:
– Local User Service Channel Cross-Connection
– Service Channels Cross-connection in pass-through
N.B. Cross-Connection towards MPT

In this release cross-connection of Service Channels towards a radio direction with MPT is not
supported.
The operator therefore will not have the possibility to select a radio direction with MPT for such
cross-connection.
3.4.6.1 Local User Service Channel Cross-connection
The two local user 64 kbit/s Service Channels on the AUX peripheral unit can be cross-connected to one
radio link with one of the three available radio Service Channels.
Note: Before disabling a local user Service Channel interface, all Service Channel cross-connections
involving this interface must be removed.
Before disabling an Auxiliary or Radio peripheral, any Service Channel cross-connections involving this
peripheral must be removed.
3.4.6.2 Service Channels Cross-connection in pass-through
Independently of the presence of the Auxiliary peripheral unit, it is always possible to cross-connect each
individual radio Service Channel with a radio Service Channel of another radio direction, without any local
termination.
3.4.6.3 How to create an AUX cross-connection
1) Select in the New Cross-Connection area the first Termination Point (this can be a local ser-
vice channel or a service channel in a radio link).
2) Select the second Termination Point as shown in the example in the figure.
N.B. The cross-connections are bi-directional.

Figure 142. Auxiliary Cross Connections menu
3) Click on Add. The new cross-connection will appear in the list (upper part of the screen as
shown in the next figure).
N.B. Button Apply has not been implemented.
Figure 143. New AUX Cross Connection

3.4.6.4 How to delete an AUX Cross Connection
1) Select one Cross-Connection to be deleted from the list (as shown in the figure).
2) Click on Delete.
N.B. The multiple deletion of the Cross-Connection is not possible.
N.B. Button Apply has not been implemented.
Figure 144. Delete an AUX Cross Connection

3.4.7 Menu VLAN Configuration
For the VLAN Management refer to paragraph 3.19 on page 469.
3.4.8 Traffic Descriptors

This menu allows to create or to delete the traffic descriptors, that will be associated to the ATM traffic at
the ingress and/or at the egress.
Figure 145. Traffic Description View
To create a Traffic Descriptor:
[1] Select the domain: ATM (if in the NE the ASAP unit is present) or PWE3 (in the repeater nodes or
in the nodes, where an Ethernet termination is present)
[2] Insert a label to identify the Traffic Descriptor
[3] Configure the following parameters:

• Service Category: CBR, UBR+ or UBR (rtVBR and nrtVBR are not managed)
• Conformance Definition: CBR.1 (VBR.1, VBR.2, VBR.3 are not maneged)
[4] Configure the following TD Parameters: PCR, CDVT, MDCR
[5] Enable or disable the Policing. For each VP/VC it is possible to enable/disable a cell-based ATM
Policing, based on the related ingress ATM Traffic Descriptor. The default configuration of ATM Polic-
ing is according to configured Service Category:
• enabled for VP/VC having Service Category CBR;
• disabled for VP/VC having Service Category UBR+ and UBR.
[6] Click on Create

[7] The already created Traffic Descriptor will appear in the List Traffic Descriptors area.
To delete a Traffic Descriptor:
[1] Select in the List Traffic Descriptors area the Traffic Descriptor to be deleted and click on Delete.
N.B. By clicking on Refresh the list of the Traffic Descriptors will be updated.
N.B. The maximum number of ATM Traffic Descriptors configurable on a NE is given by 2 times the
max number of configurable VPs multiplied by max number of ASAP Cards that can be hosted:
2 (2 traffic Descriptors per circuit) x 128 (128 circuits max.) x 6 (6 ASAP units in the NE max.).
The types of ATM Traffic Contract (that is the Service Category/Conformance Definition pair) to be sup-
ported by MPR system and its relation with Traffic Descriptor parameters is reported in the table below.
Service Conform Traffic Descr Type Traffic Traffic Traffic

Category Def. Descr Descr Descr
Param1 Param2 Param3
cbr CBR.1 atmClpTransparentNoScr PCR CDVT
(CLP=0+1)
ubr+ CBR.1 atmClpTransparentNoScr PCR CDVT MDCR > 0
(CLP=0+1) (CLP=0+1)
ubr CBR.1 atmClpTransparentNoScr PCR CDVT MDCR = 0
(CLP=0+1) (CLP=0+1)
Notes:
[1] UBR+ Service Category is defined as an UBR Service Category with Traffic Descriptor Parameter
3 (MDCR) > 0
[2] ATM Traffic Descriptor Parameters for VP/VC rates (PCR,SCR) are defined in terms of cell/second,
for CDVT the unit is microseconds, for MBS the unit is cells
[3] Range for ATM Traffic Descriptor Parameters with VP/VC rates is 0 to the bandwidth of related phys-
ical or logical ATM interface, range for CDVT is 100 to 40000 microseconds, range for MBS is 0 to
1000 cells.

3.4.9 Menu Profile Management
3.4.9.1 Introduction
After the Start Supervision, each time the operator performs the Show Equipment action, the following
Dialog screen is displayed after the window with JUSM start-up message and before the window with load-
ing bar indicating JUSM start-up progress.
Figure 146. Login window
The operator has to insert the operator name and related password: by clicking on the Apply button, the
parameters are sent to NE.
The default Operator Name is “initial”.
The default Password is “adminadmin”.
According to the operator authentication (correct couple username/password) managed by the NE, the
operator will be authorized or not to continue. If the login parameters are not correct, an error message
(Figure 147.) will be displayed, while the Login window is still open for a new attempt. After 3 consecutive
failed attempts the login procedure is closed and JUSM does not start.
Figure 147. Login Failed
On the contrary if the user name and password are correct, JUSM will be started and the operator will be
allowed to perform the actions according to the right related to his profile.
WARNING:The NE rejects usernames and passwords that do not meet the following rules:
– Password length: the length must be not less than six (6) characters under any circum-
stances. Moreover the password length must be not longer than 20 characters.

– Password composition: the password can include full ASCII characters set (UPPER/
lower case, numeric and special characters).
– Username length: the length must be not longer than 20 characters.
By clicking on the Cancel button, the login procedure is stopped and the JUSM does not start.
3.4.9.2 User Profiles Management
If the operator right allows the profiles management, the operator can perform some actions on the pro-
files.
Under Configuration menu, the Profiles Management menu displays two items:
– Users Management
– Change Password
These items will be enabled according to the right of user profile recognised at login.
3.4.9.3 User Management
By clicking on Users Management the window displayed in Figure 148. appears.
The operator can perform the following actions:
– Create a new User by clicking on the Create button
After the selection of a user in the table, it’s possible:
– Delete an existing User (the Admin user cannot be deleted) by clicking on the Delete button
– Change PW (by Administrator) by clicking on the Change PW button.
Figure 148. Profiles Management
By clicking on the Cancel button the Profiles Management window closes.
By clicking on the Help button the help browser will display the help-on-line pages dedicated to this func-
tion.

3.4.9.4 How to Create a New User
By clicking on the Create button, the following window appears and allows the user Administrator to create
a new user.
Figure 149. Create User
In this dialog box the operator has to insert the parameters to define the new user and his profile rights:
1. AdminPassword: the password of Administrator for confirmation and validation.
2. UserName: the specific name to be assigned to the new User (if it exists, the action will be failed).
3. Profile: the specific profile to be assigned to the new User.
The supported profiles are:
• Administrator: full access also for security parameters

• Operator: person in charge to operate at network level, not at radio side; dangerous operations
that require NE reconfiguration at radio site are not permitted including backup/restore and
restart NE features; could change own password
• CraftPerson: person in charge for installation and the maintenance at radio site; full access to
NE but not for security parameters, only for own password
• Viewer: only to explore the NE
Supported operations by the profiles:
• Administrator profile: All the NE parameters are accessible both in writing and reading mode.
Also the management of user accounts is allowed (create/delete user accounts and change
of all passwords).
• Operator profile: Full reading access to NE parameters. For writing mode the following param-
eters are allowed to change:
– ATPC configuration (enabled, disabled)

– Performance Monitoring management
• start/stop CD
• threshold tables configuration
• reset
• archiving (only for NMS system)
Supported for all the types of Performance Monitoring (Radio Hop/Link, E1, Received Power
Levels, ....)

– NTP protocol:
• Enabled/Disabled
• NTP main server address configuration
• NTP spare server address configuration
• CraftPerson profile: This operator has the same priviledges of the Administrator, but cannot
manage the user accounts
• Viewer profile: This operator can only read and can change his own password.
4. Password: the specific password to be assigned to the new User.
5. Confirm Password: again the specific password to be assigned for confirmation and validation.
By clicking on Apply button, at first JUSM performs a syntax check of each field: if there are some errors,
JUSM will display the specific message and allows the operator to correct them. If all parameters are cor-
rect, all parameters are sent to NE; after to have automatically closed the window, a message with result
of the action will be displayed.
By clicking on Cancel button, the Create User window closes and no action will be performed.
3.4.9.5 How to Delete a User
After the selection of a User in the Profile Table, by clicking on the Delete button, at first a confirmation
dialog (Figure 150.) will be displayed; then the window to confirm the administrator password will be dis-
played (Figure 151.).
Figure 150. Delete user confirmation
Figure 151. Confirm Administrator Password to Delete a User
By clicking on the Apply button, a message with the result action will be displayed after to have closed
automatically the window above. If the operator clicks on Cancel button the window will closes and no
action is performed.

3.4.9.6 Change the Password (by the Administrator)
The Administrator User can change the password of another user: select the user in the Profile Table and
then click on Change PW button. The following dialog box is displayed:
Figure 152. Change Password of User by Admin
The admin has to insert his password and the new password for selected user in the two text fields.
rect, all parameters are sent to NE; after to have automatically closed the window, a message with result
By clicking on Cancel button, the window will be closed.
3.4.9.7 Change Password (by the User)
If the operator wants to change his password, he has to select the Change Password menu item. The
following dialog will be displayed:
Figure 153. Change User Password
The operator has to insert the current password and the new password in the two text fields.
rect, all parameters will be sent to NE; after to have automatically closed the window, a message with result
By clicking on Cancel button, the window closes.

3.4.10 Ethernet Features Shell
The LAG can be created by CLI commands launched with the WebEML from the menu Configuration
> Ethernet Features Shell.
3.4.10.1 Simple examples for LAG creation
Here below two examples of the CLI commands useful to create LAG.
Example 1 : Ethernet LAG with Ethernet User port 1 and 2
1) Create the LAG with index 1, Ethernet type, size 2 (2 user ports: max allowed number) called
“mario”
– lag 1 create type ethernet name mario size 2
2) Add User port 1 of the Core unit (slot 1) with priority 128 (128 means that the two ports have
the same priority)
– lag 1 port add 1/1 priority 128
3) Add User port 2 of the Core unit (slot 1) with priority 128
4) Enable the LAG
– lag 1 enable true
Example 2: Radio LAG between port 1 on MPACC in slot 3 and port 2 on MPTACC in slot 4
1) Create the LAG with index 5, Radio type, size 2 (2 radio ports: max allowed number), called
“paolo”
– lag 5 create type radio name paolo size 2
2) Add port 1 of the MPTACC in slot 3 with priority 128
3) Add port 2 of the MPTACC in slot 4 with priority 128
4) Enable the LAG
– lag 5 enable true
In bold characters the keywords, in italic characters the variables.
N.B. When from the WebEML is launched the CLI, the WebEML closes.
For a complete description of the CLI refer to the next paragraphs.
Note 1: To know if an MPT is grouped in a radio LAG, letter L is placed on the MPT icon on the
Equipment view, but in this view it not possible to see the association of a specific MPT to a
specific Radio LAG.

Note 2: To know if an Ethernet user port is grouped in an Ethernet LAG, in the CORE-E domain in the
Ethernet Physical Interface tab-panel the Settings tab-panel of the Ethernet port grouped in a
LAG is gray (no changes can be done), but it not possible to see the association of a specific
User Ethernet port to a specific Ethernet LAG.
Note 3: If a parameter has to be changed in an already configured Radio LAG, the final configuration
is available after the expiring of the Wait To Restore time.
3.4.10.2 LAG commands
3.4.10.2.1 Command Conventions
– Shell interface is case-sensitive, all the command keywords shall be lowercase
– Elements in angle brackets ( < > ) represent a field requested as an input to the operator
– Elements in square brackets ( [ ] ) represent an optional field
– Elements in braces ( { } ) represent the group of parameters admitted for the specific command. Dif-
ferent values are separated by the | separator
3.4.10.2.2 Link aggregation
COMMANDS DEFAULT VALUES
lag system priority <priority(0-65535)> priority 32768
key lag-id
lacp active
lag <lag-id(1-24)> create type {ethernet|radio} name <name> size <size(1-
8)> [key <admin_key(1-32)>] [lacp {active|passive|disabled}] [timeout type eth
{long|short}] [hash {l2|l3}]
timeout long
hash l2
lag <lag-id> modify hash {l2|l3}
lag <lag-id> modify size <size(1-8)>
lag <lag-id> modify timeout {long|short}
lag <lag-id> enable {true|false}
lag <lag-id> destroy
lag <lag-id> port add <slot/port> [priority <priority(0-65535)>] priority 128
lag <lag-id> port modify <slot/port> priority <priority(0-65535)>
lag <lag-id> port remove <slot/port>
lag [<lag-id>] show config
lag [<lag-id>] show status

CMD ID: LA_1 (SYSTEM PRIORITY)
lag system priority <priority(0-65535)>
Description: sets the priority of the system. The default value is set at the start-up to 32768. If two systems
have the same priority, the SystemID (NE MAC Address) is used to determine the LAG “master”
Parameters:
– priority (mandatory)
• Range: 0 (highest) – 65535 (lowest)
The 2-bytes System Priority value is used, together with the 6-bytes System ID (equal to the NE MAC
Address), to build the System Identifier.
System Identifier: 00:20:60:00:00:23 : 80:00
This is the System Identifier of a LAG system with System ID 00:20:60:00:00:23 and System Priority
32768 (8000h).
System Identifiers of LAG peers are compared (in priority comparisons, numerically lower values have
higher priority) in order to elect the LAG “master”. System Priorities are first compared. If two systems have
the same System Priority, the System ID is compared (lowest 6-bytes unsigned number have the higher
priority).
Example1:
00:20:60:00:00:23:80:01
00:20:60:00:00:24:80:00 (highest priority)
Example2:
00:20:60:00:00:23:80:00 (highest priority)
00:20:60:00:00:24:80:00
_________________________________________________________________________________
CMD ID: LA_2 (LAG CREATE)
lag <lag-id(1-24)> create type {ethernet|radio} name <name> size <size(1-8)> [key <admin_key(1-32)>]
[lacp {active|passive|disabled}] [timeout {long|short}] [hash {l2|l3}]
Description: creates a Link Aggregation Group. The LAG is identified by the LagID
Parameters:
– lag-id (mandatory)
• Range: 1-24
– type (mandatory)
• Values: ethernet|radio
• Description: sets the type of Link Aggregation. Use Ethernet parameter to configure a Link
Aggregation on User Ethernet Ports; use Radio parameter to configure a Link Aggregation on
Radio Interfaces
– name (mandatory)
– size (mandatory)
• Range: 1-8
• Description: represents the maximum number of Active links in the Link Aggregation Group.
– key (optional)

• Range: 1-32
• Default: equal to the lag-id value
• Description: sets the admin key of the LAG. This value is associated also to all the ports that
belong to the LAG.
– lacp (optional)
• Values: active|passive|disabled
• Default: active
• Description: sets the activity of the Link Aggregation Control Protocol. Set this value to disabled
to configure Static Link Aggregation. Active and Passive values are two modalities of the
Dynamic Link Aggregation. Active (send LACPDUs automatically with the defined periodicity);
Passive (send LACPDUs only if received by the Link Aggregation Partner)
– timeout (optional)
• Values: short|long
• Default: long
• Description: sets the timeout of the LA protocol and the related LACPDU transmission interval.
Long (transmission interval 30 seconds; timeout period 90 seconds); Short (transmission inter-
val 1 second; timeout period 3 seconds)
– hash (optional)
• Values: l2|l3
• Default: l2
• Description: sets the traffic distribution criteria.
Traffic Distribution Criteria:
Two different traffic load balancing algorithms can be configured on a LAG: Layer2 (hash l2) and Layer3
(hash l3).
Layer2 load balancing algorithm is based on fields contained in the Ethernet MAC frame header:
– Destination MAC Address + Source MAC Address + VLAN ID + EtherType + Ethernet Switch Source
Port
– Destination MAC Address + Source MAC Address + Ethernet Switch Source Port (for Multicast,
Broadcast and Unknown traffic)
Layer3 load balancing algorithm is based on fields contained in the IP frame header and TCP/UDP ports:
– Destination IP Address + Source IP Address + TCP/UDP Destination Port + TCP/UDP Source Port
– Destination IP Address + Source IP Address + Ethernet Switch Source Port (for Multicast IP traffic)
If the frame is not IP and Destination and Source IP Addresses are not available, Destination and Source
MAC Addresses are used to evaluate the traffic distribution.
_________________________________________________________________________________
CMD ID: LA_3 (MODIFY HASH)
lag <lag-id> modify hash {l2|l3}
Description: modifies the traffic distribution criteria of an existent LAG.
Parameters:
• Range: 1-24
– hash (mandatory)
• Values: l2|l3
• Description: sets the traffic distribution criteria.

Refer to LAG CREATE command for Traffic Distribution Criteria details.
_________________________________________________________________________________
CMD ID: LA_4 (MODIFY SIZE)
lag <lag-id> modify size <size(1-8)>
Description: modifies the size parameter of an existent LAG.
Parameters:
• Range: 1-24
– size (mandatory)
• Range: 1-8
• Description: represents the maximum number of Active links in the Link Aggregation Group.
If LACP is Disabled, Size cannot be less than the number of ports belonging to the LAG. To reduce the
number of ports, perform a PORT REMOVE and the a MODIFY SIZE.
_________________________________________________________________________________
CMD ID: LA_5 (MODIFY TIMEOUT)
lag <lag-id> modify timeout {long|short}
Description: modifies the timeout parameter of an existent LAG.
Parameters:
• Range: 1-24
– timeout (mandatory)
• Values: short|long
• Description: sets the timeout of the LA protocol and the related LACPDU transmission interval.
Long (transmission interval 30 seconds; timeout period 90 seconds); Short (transmission inter-
val 1 second; timeout period 3 seconds)
Timeout can be changed only if LACP is Active/Passive.
_________________________________________________________________________________
CMD ID: LA_6 (LAG ENABLE)
lag <lag-id> enable {true|false}
Description: sets the LAG Administrative State
Parameters:
• Range: 1-24
– enable (mandatory)
• Values: true|false
• Description: enable or disable the LAG, setting its Administrative State to True or False
To Enable a LAG, at least one port shall be added first.
Once LAG has been Enabled, Cross-connections and VLANs can be configured.
LAG cannot be Disabled if any Cross-connection or VLAN is present.

_________________________________________________________________________________
CMD ID: LA_7 (LAG DESTROY)
lag <lag-id> destroy
Description: destroys the LAG
Parameters:
• Range: 1-24
LAG can be destroyed if all ports have been removed and its status is Disabled.
_________________________________________________________________________________
CMD ID: LA_8 (PORT ADD)
lag <lag-id> port add <slot/port> [priority <priority(0-65535)>]
Description: adds a port to a specific LAG
Parameters:
• Range: 1-24
– slot/port (mandatory)
• Description: identifies the interface to be added to the LAG
– priority (optional)
• Default: 128
• Description: sets the priority of the port in the LAG. According to port priority and Size parameter,
ports are aggregated and set as Active or Stand-By.
Port to be added shall not have any Cross-connection, VLAN or Segregation configured.
Ethernet ports added to the LAG shall have the same capabilities configured through WebEML.
Additionally, if Auto Negotiation is Enabled, ports shall advertise one speed only (10Mb, 100Mb or
1000Mb).
_________________________________________________________________________________
CMD ID: LA_9 (PORT PRIORITY)
lag <lag-id> port modify <slot/port> priority <priority(0-65535)>
Description: modifies the port priority parameter
Parameters:
• Range: 1-24
• Description: identifies the interface to be modified
• Description: sets the priority of the port in the LAG. According to port priority and Size parameter,
ports are aggregated and set as Active or Stand-By.
_________________________________________________________________________________

CMD ID: LA_10 (PORT REMOVE)
lag <lag-id> port remove <slot/port>
Description: removes a port from a specific LAG
Parameters:
• Range: 1-24
• Description: identifies the interface to be removed
At least one port shall be present in an Enabled LAG. Before removing the last port, LAG shall be set to
Disabled.
_________________________________________________________________________________
CMD ID: LA_11 (SHOW CONFIG)
lag [<lag-id>] show config
Description: displays administrative parameters of all the LAGs created (or of a specific LAG)
Parameters:
– lag-id (optional)
• Range: 1-24
• Description: identifies the LAG to be shown. If not present, all LAGs created in the equipment
are shown
Display Example:
_________________________________________________________________________________
MPR> lag show config
System Identifier: 00:20:60:00:00:23:80:00
LAG 1
********
Lag name: LAG1
Type: Ethernet
Total ports: 2
Administrative size: 2
Administrative timeout: LONG
Administrative status: ENABLED
LACP: ACTIVE
Hashing: Layer2

SLOT/PORT | PORT-ID | PRIORITY
-------------------|-----------------|-------------
1/ 2 | 2 | 128
1/ 3 | 3 | 128
_________________________________________________________________________________
CMD ID: LA_12 (SHOW STATUS)
lag [<lag-id>] show status
Description: displays operational parameters of all the LAGs created (or of a specific LAG). It also includes
the Link Aggregation protocol values and the partner parameters.
Parameters:
– lag-id (optional)
• Range: 1-24
• Description: identifies the LAG to be shown. If not present, all LAGs created in the equipment
are shown.
Display Example:
_________________________________________________________________________________
MPR> lag show status
LAG 1
********
SLOT/PORT | LACPDU | MARKER | MARKER REPLY | LACPDU
| (Tx/Rx) | (Tx/Rx) | (Tx/Rx) | (Ill/Unk)
-----------------|--------------|---------------|------------------------|---------------
1/ 2 | 8/ 7 | 0/ 0 | 0/ 0 | 0/ 0
1/ 3 | 6/ 5 | 0/ 0 | 0/ 0 | 0/ 0
Active ports: 2
StandBy ports: 0
PARTNER PARAMETERS
Partner System ID: 00:20:60:00:00:24
Partner System Priority: 32768

Partner Operative Key: 1
PORT INFO
----------
PORT 1/2
------
Port status: UP IN BUNDLE
PARTNER INFO
------------
Partner Operative Timeout: LONG
Partner Activity ACTIVE
Partner Operative State: Aggregation Synchronization Collecting Distributing
PORT 1/3
------
Port status: UP IN BUNDLE
PARTNER INFO
------------
Partner Operative Timeout: LONG
Partner Activity ACTIVE
Partner Operative State: Aggregation Synchronization Collecting Distributing
_________________________________________________________________________________

3.4.10.2.3 Ethernet connectivity fault management (IEEE802.1ag)
format char-string
md <md_index> create [format {dns-like-name|mac-addr|char-string}] name
<md-name> level <level(0-7)> [mip-creation-criteria {none|default|explicit}] mip-creation-criteria
none
md <md_index> modify mip-creation-criteria {none|default|explicit}
md <md_index> destroy
format char-string
ma <ma_index> create md <md_index> [format {primary-vid|char-
string|unsigned-int16|rfc2865-vpn-id}] name <ma-name> vlan <vlan-id(0- mip-creation-criteria
4080)> [mip-creation-criteria {none|default|explicit|defer}] [interval {three- defer
hundred-hertz|ten-ms|hundred-ms|one-sec|ten-sec|one-min|ten-min}]
interval one-sec
ma <ma_index> modify mip-creation-criteria {none|default|explicit|defer}
ma <ma_index> modify interval {three-hundred-hertz|ten-ms|hundred-

ms|one-sec|ten-sec|one-min|ten-min}
ma <ma_index> destroy
ma <ma_index> mep assign <mepid>
ma <ma_index> mep remove <mepid>
direction down
mep <ma_index>:<mepid(1-8191)> create [direction {up|down}] {if <slot/
priority 7
port>|trunk <trunk-id>} [priority <priority(0-7)>] [enable {true|false}]
enable false
mep <ma_index>:<mepid> modify priority <priority(0-7)>
mep <ma_index>:<mepid> enable {true|false}
mep <ma_index>:<mepid> ccm enable {true|false} ccm enable false
mep <ma_index>:<mepid> destroy
loopback <ma_index>:<mepid> {mpid <peer-mepid(1-8191)> | mac <peer- count 1

mac(aa:aa:aa:aa:aa:aa)>} [count <num_of_msgs(1-1024)>]
linktrace <ma_index>:<mepid> {mpid <target-mepid(1-8191)> | mac ttl 64

<aa:aa:aa:aa:aa:aa>} [ttl <ttl-value(0-255)>] [usefdbonly] usefdbonly not set
md [<md_index>] show
ma [<ma_index>] show
ma <ma_index> show mp local
ma <ma_index> show mp remote

ma <ma_index> show errors
ma <ma_index> show error-log
clear ccm database
clear errors
clear error-log
_________________________________________________________________________________
CMD ID: ECFM_1 (MD CREATE)
md <md_index> create [format {dns-like-name|mac-addr|char-string}] name <md-name> level

<level(0-7)> [mip-creation-criteria {none|default|explicit}]
Description: creates a Maintenance Domain (MD)
Parameters:
– md_index (mandatory)
• Range: 1-16
• Description: identifies the MD in the equipment
– format (optional)
• Values: dns-like-name|mac-addr|char-string
• Default: char-string
• Description: sets the format of the name of the MD.
– dns-like-name: insert a DNS name string
– mac-addr: insert a MAC address and an unsigned integer (e.g., 00:00:00:00:00:01:3457).
Integer value shall be in the range 0 – 65535.
– char-string: insert a character string
• Description: sets the name of the MD according to the format configured
– level (mandatory)
• Range: 0-7
• Description: sets the MD Level. It is used to define different levels of monitoring for a specific
service.
– mip-creation-criteria (optional)
• Values: none|default|explicit
• Default: none
• Description: sets the creation criteria parameter of the MD. This parameter is used by the auto-
matic MIP creation mechanism. None (no MIPs are created); Default (MIPs are created on all
ports belonging to the MA’s VLAN); Explicit (MIPs are created on ports belonging to the MA’s
VLAN only if a MEP is present at a lower MD Level). See Appendix for details.
Network Element shall be in 802.1Q Virtual Bridge Mode.
_________________________________________________________________________________
CMD ID: ECFM_2 (MD MIP CREATION CRITERIA)
md <md_index> modify mip-creation-criteria {none|default|explicit}
Description: modifies the MIP creation criteria of a specific MD

Parameters:
• Range: 1-16
– mip-creation-criteria (mandatory)
• Values: none|default|explicit
• Description: sets the creation criteria parameter of the MD. This parameter is used by the auto-
VLAN only if a MEP is present at a lower MD Level). See Appendix for details.
_________________________________________________________________________________
CMD ID: ECFM_3 (MD DESTROY)
md <md_index> destroy
Description: destroys a MD
Parameters:
• Range: 1-16
MD cannot be destroyed if any MA is associated to it. Destroy all MAs belonging to the MD, using MA
DESTROY command, before removing it.
_________________________________________________________________________________
CMD ID: ECFM_4 (MA CREATE)
ma <ma_index> create md <md_index> [format {primary-vid|char-string|unsigned-int16|rfc2865-vpn-

id}] name <ma-name> vlan <vlan-id(0-4080)> [mip-creation-criteria {none|default|explicit|defer}]
[interval {three-hundred-hertz|ten-ms|hundred-ms|one-sec|ten-sec|one-min|ten-min}]
Description: creates a Maintenance Association (MA)
Parameters:
– ma_index (mandatory)
• Range: 1-512
• Description: identifies the MA in the equipment
– format (optional)
• Values: primary-vid|char-string|unsigned-int16|rfc2865-vpn-id
• Default: char-string
• Description: sets the format of the name of the MA
– primary-vid: insert a VLAN ID
– char-string: insert a character string
– unsigned-int: insert an unsigned integer in the range 0 – 65535.
– rfc2865-vpn-id: insert a VPN ID. It is composed by 3 bytes VPN OUI and 4 bytes VPN
Index separated by colon (e.g., 00A157:1111FFFF)
• Description: sets the name of the MA according to the format configured
– vlan (mandatory)
• Range: 0-4080
• Description: sets the VLAN ID to be associated to the MA. The value 0 configures a VLAN
unaware MA.
– mip-creation-criteria (optional)

• Values: none|default|explicit|defer
• Default: defer
• Description: sets the creation criteria parameter of the MA. This parameter is used by the auto-
VLAN only if a MEP is present at a lower MD Level); Defer (mip-creation-criteria of the asso-
ciated MD is considered). See Appendix for details.
– interval (optional)
• Values: three-hundred-hertz|ten-ms|hundred-ms|one-sec|ten-sec|one-min|ten-min
• Default: one-sec
• Description: set the transmission interval of CCM messages. Values lower than one-sec are
not supposed to be used.
MA cannot be created if the VLAN associated is not present in the Network Element.
Once an MA is created, the associated VLAN cannot be removed from the Network Element: MA shall
be destroyed before removing the VLAN.
MA cannot be created if there is another MA, in the same MD, associated to the same VLAN.
MA cannot be created if there is another MA, with same VLAN and MD Level, with an UpMEP configured.
The level of a VLAN-unaware MA cannot be equal or greater than the level of a VLAN-aware MA.
The level of a VLAN-aware MA cannot be equal or less than the level of a VLAN-unaware MA.
_________________________________________________________________________________
CMD ID: ECFM_5 (MA MIP CREATION CRITERIA)
ma <ma_index> modify mip-creation-criteria {none|default|explicit|defer}
Description: modifies the MIP creation criteria of a specific MA
Parameters:
• Range: 1-512
– mip-creation-criteria (mandatory)
• Values: none|default|explicit|defer
• Description: sets the creation criteria parameter of the MA. This parameter is used by the auto-
VLAN only if a MEP is present at a lower MD Level); Defer (mip-creation-criteria of the asso-
ciated MD is considered). See Appendix for details.
_________________________________________________________________________________
CMD ID: ECFM_6 (CCM INTERVAL)
ma <ma_index> modify interval {three-hundred-hertz|ten-ms|hundred-ms|one-sec|ten-sec|one-

min|ten-min}
Description: modifies the CCM interval of a specific MA
Parameters:
• Range: 1-512

– interval (mandatory)
• Values: three-hundred-hertz|ten-ms|hundred-ms|one-sec|ten-sec|one-min|ten-min
• Description: set the transmission interval of CCM messages. Values lower than one-sec are not
supposed to be used.
_________________________________________________________________________________
CMD ID: ECFM_7 (MA DESTROY)
ma <ma_index> destroy
Description: destroys a MA
Parameters:
• Range: 1-512
MA cannot be destroyed if any MEP is assigned to it. Remove all MEPs assigned to the MA, using MEP
REMOVE command, before removing it.
_________________________________________________________________________________
CMD ID: ECFM_8 (MEP ASSIGN)
ma <ma_index> mep assign <mepid>
Description: assigns MEPID to the MA. All MEPs belonging to a MA shall be inserted in the MEP table.
This list includes both local and remote MEPs. This command is used to populate that table. MEPIDs of
local MEPs must be inserted in this list before MEP creation.
Parameters:
• Range: 1-512
– mepid (mandatory)
• Range: 1-8191
• Description: represents the MEP identifier of the MEP to be associated to the MA
_________________________________________________________________________________
CMD ID: ECFM_9 (MEP REMOVE)
ma <ma_index> mep remove <mepid>
Description: removes MEPID from the MA.
Parameters:
• Range: 1-512
• Range: 1-8191
• Description: represents the MEP identifier of the MEP to be removed from the MA
MEP cannot be removed from the MA if it is still present in the Network Element. Destroy the MEP with
MEP DESTROY command before removing it.

_________________________________________________________________________________
CMD ID: ECFM_10 (MEP CREATE)
mep <ma_index>:<mepid(1-8191)> create [direction {up|down}] {if <slot/port>|trunk <trunk-id>} [pri-

ority <priority(0-7)>] [enable {true|false}]
Description: creates a MEP on a specific interface
Parameters:
• Range: 1-512
• Range: 1-8191
• Description: represents the MEP identifier of the MEP to be created
– direction (optional)
• Values: up|down
• Default: down
• Description: sets the direction of a MEP. Each MEP has an active and a passive side. The active
side generates CCM, LBM and LTM. It also receives all the response messages. A Down MEP
has the active side directed towards the physical layer. An Up MEP has the active side directed
towards the relay entity.
– slot/port|trunk-id (mandatory)
• Description: identifies the physical interface or the LAG on which configure the MEP
– priority (optional)
• Range: 0-7
• Default: 7
• Description: sets the priority bits of CCM, LBM and LTM.
– enable (optional)
• Default: false
• Description: enable or disable the MEP
Interface indicated (slot/port or LAG) shall belong to the VLAN of the MA.
MEP cannot be create if there is another MEP, on the same interface, with same Direction, MD Level and
VLAN.
UpMEP cannot be created on the MA if there is another MA with same VLAN and MD Level.
MEP cannot be configured if there is another MEP, with same MEP ID, on the same MD Level and VLAN.
UpMEP cannot be configured on a VLAN-unaware MA.
_________________________________________________________________________________
CMD ID: ECFM_11 (MEP PRIORITY)
mep <ma_index>:<mepid> modify priority <priority(0-7)>
Description: modifies the priority bits of messages sent by the MEP
Parameters:
• Range: 1-512

• Range: 1-8191
• Description: identifies the MEP in the MA
• Range: 0-7
• Description: sets the priority bits of CCM, LBM and LTM.
_________________________________________________________________________________
CMD ID: ECFM_12 (MEP ENABLE)
mep <ma_index>:<mepid> enable {true|false}
Description: modifies the administrative state of the MEP
Parameters:
• Range: 1-512
• Range: 1-8191
– enable (mandatory)
• Description: enable or disable the MEP
_________________________________________________________________________________
CMD ID: ECFM_13 (CCM ENABLE)
mep <ma_index>:<mepid> ccm enable {true|false}
Description: enables or disables the CCM transmission
Parameters:
• Range: 1-512
• Range: 1-8191
– ccm enable (mandatory)
• Description: enable or disable the CCM transmission. At the MEP creation this value is set to
False
_________________________________________________________________________________
CMD ID: ECFM_14 (MEP DESTROY)
mep <ma_index>:<mepid> destroy
Description: destroys a MA
Parameters:
• Range: 1-512

• Range: 1-8191
_________________________________________________________________________________
CMD ID: ECFM_15 (LOOPBACK)
loopback <ma_index>:<mepid> {mpid <peer-mepid(1-8191)> | mac <peer-mac(aa:aa:aa:aa:aa:aa)>}

[count <num_of_msgs(1-1024)>]
Description: sends a loopback message
Parameters:
• Range: 1-512
• Range: 1-8191
• Description: identifies the MEP in the MA. It is the source MEP of the LBM
– mpid|mac (mandatory)
• Description: defines the MEPID (valid for a LB towards a MEP) or the MAC Address (valid for
a LB towards both a MEP and a MIP) of the destination Maintenance Point
– count (optional)
• Range: 1-1024
• Default: 1
• Description: sets the number of LBM to be transmitted
Display Example:
MPR> loopback 1:1 mpid 2 count 1
Sending 1 Ethernet CFM loopback message, timeout is 5 seconds
Success rate is 100.0 percent 1/1
_________________________________________________________________________________
CMD ID: ECFM_16 (LINKTRACE)
linktrace <ma_index>:<mepid> {mpid <target-mepid(1-8191)> | mac <target-mac(aa:aa:aa:aa:aa:aa)>}

[ttl <ttl-value(0-255)>] [usefdbonly]
Description: sends a linktrace message
Parameters:
• Range: 1-512
• Range: 1-8191
• Description: identifies the MEP in the MA. It is the source MEP of the LTM
– mpid|mac (mandatory)
• Description: defines the MEPID (valid for a LT towards a MEP) or the MAC Address (valid for
a LT towards both a MEP and a MIP) of the target Maintenance Point

– ttl (optional)
• Range: 0-255
• Default: 64
• Description: sets the time-to-live of the LTM PDU
– usefdbonly (optional)
• Values: present(1) or not present(0)
• Default: not present(0)
• Description: intermediate nodes receiving LTM forward a new LTM towards the next hop only
if the target MAC Address has been learnt on a specific port. The target MAC Address can be
found in the FDB (ForwadingDataBase – L2 table used for normal traffic forwarding) or in a spe-
cific DB described in the CFM standard (MIP CCM DataBase) populated by MIPs with source
MAC Addresses of CCM traffic passing-through.
If usefdbonly parameter is not present, MIP shall look for the target MAC Address either in the
FDB or in the MIP CCM Database. If usefdbonly parameter is present, the target MAC Address
shall be found in the FDB only (otherwise, the frame must not be forwarded).
This parameter sets the useFDBonly flag bit in the LTM frame.
Display Example:
MPR> linktrace 1:1 mpid 2
Traceroute to Macaddress 00:20:60:00:00:24 in domain Domain5 at level 5
with vlanId 101
----------------------------------------------------------------------------------------------------------------------------
Hops Host Ingress MAC Ingress Action Relay Action

Next Host Egress MAC Egress Action Fwd Status
----------------------------------------------------------------------------------------------------------------------------
1 00:20:60:00:00:22:00:0c 00:20:60:00:00:23 IngOK RlyFDB

00:20:60:00:00:23:00:0c 00:20:60:00:00:23 EgrOK Forwarded
2 00:20:60:00:00:23:00:0c - - RlyHit
00:20:60:00:00:24:00:0b 00:20:60:00:00:24 EgrOK Terminal MEP
----------------------------------------------------------------------------------------------------------------------------
Each LTR received is displayed in this output. HOPS column identifies the LTR receiving order (in the
example: Hop 1 identifies the first LTR; Hop 2 identifies the second one, …).
For each Hop (LTR received), the following information is displayed:
– HOST: identifies the sender of the LTM that triggered the LTR response. The first 6 bytes represent
the sender MAC address; the last 2 bytes represent the port from which the LTM has been generated
(see below for port mapping).
– NEXT HOST: identifies the sender of the LTR (actually the LT Responder). The first 6 bytes represent
the sender MAC address; the last 2 bytes represent the port from which the LTR has been generated
(see below for port mapping).

– INGRESS MAC: represent the MAC address of the MP present at the ingress port (if not present,
a dash is displayed)
– EGRESS MAC: represent the MAC address of the MP present at the egress port (if not present, a
dash is displayed)
In the example: at Hop1, two MIPs are present at both the ingress and egress ports. At Hop2, a MEP is
present at the egress port.
– INGRESS ACTION: reports how the data frame targeted by LTM would be received on the receiving
MP
– EGRESS ACTION: reports how the data frame targeted by LTM would be passed through the egress
port
– RELAY ACTION: reports how the data frame targeted by LTM would be passed through the MAC
Relay Entity to the egress port. Possible values:
• RlyHit (the LTM reached an MP whose MAC address matches the Target MAC Address)
• RlyFDB (the egress port was determined by consulting the FDB)
• RlyMPDB (the egress port was determined by consulting the MIP CCM Database)
– FWD STATUS: represents the value of Flag Bits in the LTR. Possible values:
• Forwarded (the LTM, that triggered the LTR transmission, has been forwarded)
• Not Forwarded (the LTM, that triggered the LTR transmission, has not been forwarded)
• Terminal MEP (the MP that triggered the LTR transmission is a MEP)
Port Mapping:
_________________________________________________________________________________
CMD ID: ECFM_17 (MD SHOW)
md [<md_index>] show
Description: shows the parameters of one MD. If the MD Index is not present, a summary table of all the
MDs in the equipment is shown.
Parameters:
– md_index (optional)
• Range: 1-16
• Description: identifies the MD in the equipment. If not present, all MDs in the NE are shown

Display Example 1:
MPR> md show
MD NAME | MD ID | LEVEL | MIP-CREATION-CRITERIA
------------------------|----------|----------|----------------------
Domain5 | 1 | 5 | none
Domain2 | 2 | 2 | none
Display Example 2:
MPR> md 1 show
VLAN | MA ID | MA NAME
---------|----------|---------------------
101 | 1 | TDM101
Maintenance Domain 1
*********************
NAME: Domain5
FORMAT: char-string
INDEX: 1
LEVEL: 5
MIP-CREATION-CRITERIA: none
TOTAL MA: 1
_________________________________________________________________________________
CMD ID: ECFM_18 (MA SHOW)
ma [<ma_index>] show
Description: shows the parameters of one MA. If the MA Index is not present, a summary table of all the
MAs in the equipment is shown.
Parameters:
– ma_index (optional)
• Range: 1-512
• Description: identifies the MA in the equipment. If not present, all MAs in the NE are shown

Display Example 1:
MPR> ma show
MA NAME | MA ID | MD ID | VLAN | LEVEL | CCM INT | MIP-CREATION-CRITERIA
-------------------|----------|----------|---------|----------|--------------|----------------------
TDM101 | 1 | 1 | 101 | 5 | one-sec | defer
Link101 | 2 | 2 | 101 | 2 | one-sec | defer
Display Example 2:
MPR> ma 1 show
Maintenance Association 1
***********************
NAME: TDM101
FORMAT: char-string
INDEX: 1
MD NAME: Domain5
MD FORMAT: char-string
MD INDEX: 1
MD LEVEL: 5
VLAN ID: 101
CCM INTERVAL: one-sec
MIP-CREATION-CRITERIA: defer
TOTAL MEPS: 2
MPID | TYPE | STATUS | PORT | MAC
--------|------------|------------|----------|----------------------
1 | Local | Ena | 3/ 1 | 00:20:60:00:00:01
2 | Remote | OK | -/ - | 00:20:60:00:00:0A

_________________________________________________________________________________
CMD ID: ECFM_19 (SHOW MP LOCAL)
ma <ma_index> show mp local
Description: shows the parameters the local Maintenance Points associated to a MA.
Parameters:
• Range: 1-512
Display Example1:
MPR> ma 1 show mp local
MPID | LEVEL | VLAN | PRIO | TYPE | DIR | PORT | CC | STATUS
--------|-----------|---------|--------|---------|--------|---------|-------|-------
1 | 5 | 101 | 7 | Mep | Up | 0/ 0 | Ena | Ena
_________________________________________________________________________________
CMD ID: ECFM_20 (SHOW MP REMOTE)
ma <ma_index> show mp remote
Description: shows the parameters the remote MEP associated to a MA. These parameters are dynam-
ically learnt observing the received CCM frames.
Parameters:
• Range: 1-512
Display Example:
MPR> ma 1 show mp remote
MAC ADDRESS : 00:20:60:00:00:24
MD NAME: Domain5
MD LEVEL: 5
VLAN: 101
LOCAL MEP ID: 1
REMOTE MEP ID: 2
REMOTE MEP STATUS: OK

REMOTE MEP RDI: False
PORT STATUS TLV: Port is up
INTERFACE STATUS TLV: Interface up
_________________________________________________________________________________
CMD ID: ECFM_21 (SHOW ERRORS)
ma <ma_index> show errors
Description: shows the errors currently present in a MA
Parameters:
• Range: 1-512
Display Example:
MPR> ma 1 show errors
MEP ID: 1
**********
LEVEL | VLAN | RMEP ID | DEFECT TYPE
-----------|---------|-------------|-------------
5 | 101 | 2 | CCM Defect
_________________________________________________________________________________
CMD ID: ECFM_22 (SHOW ERROR-LOG)
ma <ma_index> show error-log
Description: shows the errors present in the error log table
Parameters:
• Range: 1-512
Display Example:
MPR> ma 1 show error-log
MEP ID:1
**********

TIME OF OCCURRANCE | RMEP ID | ERROR TYPE | STATUS
------------------------------------|-------------|---------------------------------|--------
26 June 2010 8:0:46 | 2 | Loss of Continuity | Exit
26 June 2010 8:0:40 | 2 | Loss of Continuity | Entry
_________________________________________________________________________________
CMD ID: ECFM_23 (CLEAR CCM DATABASE)
clear ccm database
Description: clears dynamic information held by MEPs in the NE retrieved from the received CCMs
The CCM Database, after the command is performed, is re-populated according to CCMs received.
_________________________________________________________________________________
CMD ID: ECFM_24 (CLEAR ERRORS)
clear errors
Description: clears all errors raised by MEPs in the NE. After the command is performed, errors are raised
again according to the current alarm conditions.
_________________________________________________________________________________
CMD ID: ECFM_25 (CLEAR ERROR-LOG)
clear error-log
Description: clears all errors contained in the error log table. Performed this command, all the Entry or Exit
events are lost and the error log is re-populated according to the new alarm state transitions.
_________________________________________________________________________________
3.4.10.2.4 APPENDIX A - Link Aggregation Scenarios
3.4.10.2.4.1 A.1 Static Ethernet Link Aggregation
Creation of a Static Ethernet Link Aggregation using 4 Electrical Core ports.

Network Element 1
Create a static link aggregation with size equal to 4. The hashing algorithm is layer2 by default.
MPR> lag 1 create type ethernet name Lag1 size 4 lacp disabled
MPR> lag 1 port add 1/1
MPR> lag 1 enable
Network Element 2
Create a static link aggregation with size equal to 4. The hashing algorithm is layer2 by default.
MPR> lag 4 create type ethernet name Lag1 size 4 lacp disabled
MPR> lag 4 enable
3.4.10.2.4.2 A.2 Static Ethernet Link Aggregation – Removal Procedure
Here is described the procedure to remove all the configurations done in Static Ethernet Link Aggregation
scenario. The following procedure can be applied, changing LAG IDs and interface indexes, to the other
scenarios.
VLAN, Cross-connection and Segregation configuration shall be removed from the Ethernet LAG inter-
face before applying the following procedures.
To avoid traffic loops it is suggested to Disable the ports once removed from the LAG.
Network Element 1
MPR> lag 1 enable false
MPR> lag 1 port remove 1/1
MPR> lag 1 destroy

Network Element 2
MPR> lag 4 enable false
MPR> lag 4 destroy
3.4.10.2.4.3 A.3 Ethernet Link Aggregation Active/Standby
Creation of an Active/Standby Ethernet Link Aggregation using Optical Core ports.
Network Element 1
Set the system priority to 534. Create a link aggregation with size equal to 1. The hashing algorithm is
layer2 by default and timeout is short.
MPR> lag system priority 10
MPR> lag 1 create type ethernet name LagAS1 size 1 lacp active timeout short
MPR> lag 1 port add 1/5 priority 1
MPR> lag 1 enable
Network Element 2
The system priority is set to 20. Create a link aggregation with size equal to 1. The hashing algorithm is
layer2 by default and timeout is short. Port priorities are not considered because the NE2 system priority
is lower (higher in value) than NE1. As a consequence, Port5 is ACT and Port6 is STBY.
MPR> lag system priority 20
MPR> lag 3 create type ethernet name LagAS1 size 1 lacp active timeout short

MPR> lag 3 enable
3.4.10.2.5 A.4 Radio Link Aggregation
Creation of a Radio Link Aggregation. Two MPT Access peripherals are provisioned in both NEs. Two
MPT radio links configured.
Network Element 1
Create a radio link aggregation with size equal to 2. The hashing algorithm is layer2 by default.
MPR> lag 1 create type radio name rLag1 size 2 lacp disabled
MPR> lag 1 enable
Network Element 2
Create a radio link aggregation with size equal to 2. The hashing algorithm is layer2 by default.
MPR> lag 3 create type radio name rLag1 size 2 lacp disabled
MPR> lag 3 enable

3.4.10.2.6 APPENDIX B - Ethernet CFM Scenarios
3.4.10.2.6.1 B.1 Scenario1
Set the 802.1Q bridge mode.
Create VLAN 100 on NE1 configuring the membership on Electrical Port 2 and Radio Port 2 on Slot 2.
Create VLAN 100 on NE2 configuring the membership on Optical Port 6 and Radio Port 1 on Slot 6.
Create a TDM2ETH with FlowID 50. Cross-connect, on NE1, PDH board on Slot 3 with Radio Port 2 on
Slot 2. On NE2, cross-connect PDH board on Slot 5 with Radio Port 1 on Slot 6.
Network Element 1
Configure a MD on Level 2, a MA and an Up MEP on Port 2 for VLAN 100. Configure a MD on Level 5,
a MA and an Up MEP on Slot 3 for FlowID 50.
MPR> md 1 create name Domain2 level 2
MPR> ma 1 create md 1 name Service100 vlan 100 interval one-sec
MPR> ma 1 mep assign 1
MPR> mep 1:1 create direction up if 1/2 enable true
MPR> mep 1:1 ccm enable true
MPR> ma 2 create md 2 name TDM2ETH50 vlan 50 interval one-sec

Network Element 2
3.4.10.2.6.2 B.2 Scenario1 - Removal Procedure
Here is described the procedure to remove all the configurations done in Scenario1.
Network Element 1
MPR> mep 1:1 destroy
MPR> ma 1 mep remove 1
MPR> ma 1 destroy
MPR> md 1 destroy
MPR> ma 2 destroy
MPR> md 2 destroy

Network Element 2
MPR> ma 1 destroy
MPR> md 1 destroy
MPR> ma 2 destroy
MPR> md 2 destroy
3.4.10.2.6.3 B.3 Scenario2
Set the 802.1Q bridge mode.
Create VLAN 100 on NE3 configuring the membership on Electrical Port 1 and Optical Port 6.
Slot 2. On NE2, cross-connect PDH board on Slot 3 with Radio Port 1 on Slot 6.
Slot 2. On NE2, cross-connect Radio Port 1 on Slot 6 with Electrical Port 2. Set the NE MAC Address of
NE3. On NE3, cross-connect PDH board on Slot 5 with Electrical Port 1. Set the NE MAC Address of NE2.
Network Element 1

Configure a MA and an Up MEP on Slot 3 for FlowID 75.
Network Element 2
Configure a MD on Level 2, a MA and MIPs for VLAN 100.
Configure a MD on Level 5, a MA and an Up MEP on Slot 3 for FlowID 50.
Configure a MA and MIPs for FlowID 75.
MPR> ma 1 create md 1 name Service100 vlan 100 mip-creation-criteria default

MPR> ma 3 create md 2 name TDM2ETH75 vlan 75 mip-creation-criteria default
Network Element 3
Configure a MD on Level 2, a MA and an Up MEP on Port 6 for VLAN 100.
Configure a MD on Level 5, a MA and an Up MEP on Slot 5 for FlowID 75.
3.4.10.2.6.4 B.4 Scenario2 - Removal Procedure
Here is described the procedure to remove all the configurations done in Scenario2.
Network Element 1
MPR> ma 1 destroy
MPR> md 1 destroy
MPR> ma 2 destroy

MPR> ma 3 destroy
MPR> md 2 destroy
Network Element 2
MPR> ma 1 destroy
MPR> md 1 destroy
MPR> ma 2 destroy
MPR> ma 3 destroy
MPR> md 2 destroy
Network Element 3
MPR> ma 1 destroy
MPR> md 1 destroy
MPR> ma 2 destroy
MPR> md 2 destroy

3.4.10.2.7 APPENDIX C - Automatic MIP Creation
Automatic MIP Creation scenarios are shown combining different mip-creation-criteria values.
MIPs are configured automatically, following the MIP Creation Criteria of their associated MD or MA.
The automatic MIP creation follows this procedure: for each port P and VLAN X, it is done a list of MD
Levels that contains:
– MD Levels of each of the MAs (if any) that includes VLAN X and a MEP configured on port P
– MD Levels of each of the MAs (if any) that includes VLAN X and has an Up MEP configured on a
port different from port P
– MD Levels of each of the MAs (if any) that includes VLAN X and has no MEPs configured on any
bridge port
From this list, the creation process selects the MA with the lowest MD Level D that:
– has not MEPs configured on port P and VLAN X at level D
– and has not MEPs configured on port P and VLAN X at an higher level
Once the MA is selected, the rules of MIP creation are defined by either the MIP Creation Criteria of MA
or the MIP Creation Criteria of the MD (if the MA parameter is set to Defer).
The possible values of MIP Creation Criteria are:
– None: no MIPs are created for this VLAN
– Default: MIPs are created on any port of this VLAN where (1) there are no lower MD levels or (2)
there is a MEP at the next lower MD level on the port
– Explicit: MIPs are created on any port of this VLAN where there is a MEP at the next lower MD level
on the port
_________________________________________________________________________________
Scenario 1
_________________________________________________________________________________
Scenario 2

MPR> ma 2 create md 2 name Service2 vlan 100 mip-creation-criteria default (or explicit)
_________________________________________________________________________________
Scenario 3
MPR> ma 1 create md 1 name Service1 vlan 100
MPR> ma 2 create md 2 name Service2 vlan 100 mip-creation-criteria default (or explicit)
If explicit is set, at the same way, MIP will be created only on port 1.
_________________________________________________________________________________
Scenario 4

MPR> ma 1 create md 1 name Service1 vlan 100
MPR> mep 1:1 create direction down if 1/2 enable true
If explicit is set, MIP will be created only on port 2.

3.5 Menu Diagnosis
3.5.1 Alarms
This menu opens the Alarms Monitor application.
Alarms Monitor is an application which allows to display and store the alarms of all the NEs requiring it.
Alarms Monitor can be also started by clicking on the Alarms Monitor button on NEtO.
When the Alarm Monitor is started, it collects all the alarms from the NEs.
On the left side of the application, below each NE, two global lists of alarms are displayed:
– CURRENT_ALARM shows all the equipment alarms currently present,
– ALARM_LOG shows all the equipment alarms currently present and the history of the alarms (i.e.
cleared alarms).

Note
When an alarm is no longer active it disappears from the current Global list and it is displayed in the
ALARM_LOG list as a cleared alarm
Each global list has some default filters (5 filters for the CURRENT_ALARM list and 8 filters for the
ALARM_LOG list), as follows:
– CRI contains all the alarms having a CRITICAL severity
– MAJ contains all the alarms having a MAJOR severity
– MIN contains all the alarms having a MINOR severity
– WRG contains all the alarms having a WARNING severity
– IND contains all the alarms having an INDETERMINATE severity
– CLR contains all the alarms which are in the CLEARED state, that is, which are no longer active (this
filter is available within the list ALARM_LOG only).
For each list and for each filter, the number of active alarms is shown inside brackets.
These two lists can be filtered using customized filters provided by means of the menu Filters → Add a
Filter.
Single clicking on a filter or on a global list on the left part of the screen shows up on the right side the
relevant tab panel with all the alarms.
Note
When the application is opened for the first time, only the tab-panels of the
two global lists are displayed on the right part of the window
At the top right, the field Synthesis shows the number of active alarms for any severity.
The alarms have a different color according to their severity and their state.
– Red: CRITICAL alarm
– Brown: MAJOR alarm
– Yellow: MINOR alarm
– Blue: WARNING alarm
– White: INDETERMINATE alarm (Note that the equipment has no alarm having such severity)
– Green: CLEARED alarm (alarm no longer active).
Within the tab-panel, each alarm is provided with the information below.
– Time & Date: date and time of the alarm. The format of date and time is yyyy/mm/dd hh:mm:ss.
– Probable cause: name of the probable cause of the alarm.

– Alarm Type: alarm class (TRS = Transmission Alarm – alarm not created inside the equipment, but
generated by a connected equipment or due to transmission/propagation problems; EQUIPMENT:
inside alarm of the equipment).
– Friendly Name: object of the equipment where the alarm occurred.
– Severity: alarm severity.
– Add Text: this is an additional text regarding the alarm.
– Specific problem: for some alarms, additional information is provided about the involved resource
(for instance, when a threshold alarm is raised, it states the specific threshold exceeded)
Right-clicking on an alarm row opens the menu shown in the following figure.
– Navigate to USM: to navigate to the object involved with the selected alarm and to open the relevant
window. Note: this option is available in the CURRENT_ALARM global list and in the relevant filters
only.
– Export Alarm: to create a file containing alarms data. Alarms have to be selected by means of the
menu Select → All. Generated file formats are CSV, HTML, XML and PDF.
– Print current view: it is possible to print the list of the alarms. The “Print Dialog” box is shown to
choose the printer and set Print range and Copies number.
– Select All: to select all the alarm of the list for further use, e.g. to export alarms to a file.
– Select None: to select no alarm.

The Menu Bar provides the following menus:
– File
– Filters
– Help
A) File Menu
Save Log for selected NE
This menu allows to save a file with one of the two global lists of each NE. Select the global list of a specific
NE, open the Save History menu for the selected NE and enter filename and relevant directory in the open-
ing window.
Load Log to selected NE
By means of this menu it is possible to display the global list of a certain NE previously saved.
Remove selected NE
By means of this menu an NE, selected in the list, can be removed.
Export Alarms
This menu allows to save a file with the alarms of the selected Log. Select the log, select "Export Alarms"
menu, choose the file format (CSV, HTML, HML or PDF) and then assign the name of the file.
B) Filters Menu
The Menu Filters provides the following menus:
1) Close Filter …
2) Add a Filter …
3) Edit Selected Filter …
4) Delete Selected Filter …
5) Delete Filters …
6) Save Filters As …
7) Load Filters From …
[1] Close Filter …
The Filter, currently open, is closed.

[2] Add a Filter …
This menus allows to create customized logs adding some new specific filters. The window which opens
is shown below.
Filter Name field
Enter the filter name in the Filter Name field.
The filters can be created selecting one of the following fields (or more). To save the created filter click
on the Done pushbutton. (Clicking on the Cancel pushbutton clears the filter configuration). The created
filter appears on the left side of the application.
Scope field
Select APT (Current) to create a filter showing the current alarms only or select Log to create a filter for
current and cleared alarms.
The filter can be applied to all the NEs by selecting All or it can be applied to one or more NEs by selecting
one or more NEs using the mouse.
Alarm Type field
Select Alarm Type to create a filter for the selected type of alarm:
– TRS = Transmission Alarm
– EQUIPMENT = Equipment alarm
Perceived severity field
Select Perceived severity and then one or more severity levels and/or Cleared state to filter the alarm
having the selected severity levels.
Event Time field
Select Event Time and then enter the starting date (From) and the ending date (To) to filter the alarms
created during that specific time frame only.

Probable Cause field
Select Probable Cause and then choose a specific alarm (one or more) to filter these particular alarms
only.
Resource field
Put a check mark on the Resource box and write the object name the alarms of which have to be filtered
(if required).
[3] Edit Selected Filter …
A filter, previously created, can be modified.
[4] Delete Selected Filter …
A filter, previously created, can be deleted.
[5] Delete Filters ...
When this menu is selected, the window shown below opens.
By means of this menu the filters previously created can be canceled. Default filters cannot be canceled.
Select one specific NE (or more NEs) in the Scope column, select a specific filter (or more filters) in the
Filters column and then click on the Done pushbutton.
Clicking on the Cancel pushbutton all the selections are cleared.

[6] Save Filters As ...
A default filter, or a filter previously created by means of the Add a filter … menu can be saved to be used
for some other WebEML.
Select in the Scope and Filters columns a specific filter to be saved, enter the filter name in the Name
field, select the Folder where to save the file relevant to filter and then click on the Done pushbutton.
Clicking on the Cancel pushbutton all the selections are cleared.
[7] Load Filters From ...
A filter previously saved can be loaded on the WebEML by means of the following menu.
Click on Browse to navigate and then choose the filter file to be loaded. The Scope and the Loaded Fil-
ters columns will show respectively the NE list and the filters list made available by the selected file.
Entering some characters in the Filters Prefix field and then clicking on the Done pushbutton, the inserted
characters are attached before the names of the Loaded Filters. For instance entering <Vim>, the names
of the filters change from APT to VimAPT.
C) Help Menu
This menu shows the Product Version.

3.5.2 Log Browsing
In the Diagnosis pull-down menu select the Log Browsing option.
– Software Trace Log option is reserved to the Alcatel-Lucent technicians.
– Event Log option opens the Event Log browser application.
3.5.2.1 Event Log Browser
Event Log Browser is an application which allows to display all the events occurred in the NE.
An event is meant to be:
– a configuration change
– a change of the value of an attribute
– an automatic switchover
– a manual operation carried out by the operator.
The opening window is shown below.
The following information is provided for each event:
– Time: date and time of occurrence of the event. The format is week day/month/day hh:mm:ss. Ref-
erence Time (CEST) year.
– Notification ID: a unique identifier for the event.
– Explanation: a statement built with the event log data to explain what the event represents.

The Menu Bar provides the following menus:
– File
– Help
A) File Menu
The Menu File makes available the following menus:
– Refresh Tables
– Export
– Print
– Exit
Refresh Tables
By means of this menu the event log is refreshed.
A refresh may be executed as well clicking on the relevant pushbutton below the menu bar.
Export
This menu allows to export the alarm table as a file.
The file can have the HTML, CSV, PDF or XML format. The file can store all the events (All entries) or
only those selected by means of the pointer of the mouse (Selection).
The Export may be executed as well clicking on the relevant pushbutton below the menu bar.

Print
It is possible to print the event list (all or just the selected ones). The Print Dialog box shows up allowing
to choose the printer and set print range and number of copies.
The print may be executed as well clicking on the relevant pushbutton below the menu bar.
B) Help Menu
This menu shows the Product Version.

3.5.3 Remote Inventory
This screen is a read-only screen, which shows all the information on the equipment.

3.5.4 Abnormal Condition List
The Abnormal Condition List option in the Diagnosis menu displays all the abnormal conditions cur-
rently active in the NE.
An abnormal condition is generated each time a non usual condition is present in the NE, detected auto-
matically (i.e. automatic Tx mute) or as consequence of management systems operation (i.e. force switch-
ing, loopbacks, manual Tx mute).
In the following, the list of the events which cause an abnormal condition:
– Forced switch (EPS, RPS, TPS)
– Lockout (EPS, RPS, TPS)
– Loopback activation
– Local radio Tx mute (manual)
– Adaptive Modulation in manual mode

3.5.5 Summary Block Diagram View
The “Summary Block Diagram View” of the Diagnosis menu displays a global logical view (strictly
related to the physical implementation) highlighting a synthesis of all the alarms and statuses present in
the system.
3.5.5.1 Main Block diagram view
Figure 154. shows an example of the Main block diagram view.
Figure 154. Summary block diagram
Each block has its Alarm indicator (coloured ball icon) that shows the alarm status (different colors
according to the alarm severity).
N.B. The Core-E has 2 alarm indicators in case of Core-E protection (as shown in Figure 154) and
only 1 alarm indicator (the ball icon on the left side) in case of unprotected configuration.
In the Summary block diagram view the current configuration of the MSS is shown, with the equipped units
(PDH or SDH or Radio or MPT-ACC, with the created LAGs), with the protection schemes and with the
cross-connections implemented between the different units and the different Ethernet ports, if any.
Note 1: The connection line between Slot #5 and Slot #6 in Figure 154 means that the two ports of the
two units are involved in a protection scheme.
Note 2: The connection square between Slot #3 and Slot #4 in Figure 154 means that the SDHACC
units are involved in a EPS protection scheme.
Note 3: Different icons are used to identify Radio LAG or Ethernet LAG. In Figure 154 LAG #4 is a Radio
LAG, LAG #1 is an Ethernet LAG.
Note 4: An Ethernet User port involved in an Ethernet LAG disappears from the CORE-E area (in
Figure 154 port #1 and #2 are grouped in Ethernet LAG#1. Port #5 and #6 are not shown
because are optional and have not been configured.

On the RADIO/MPT-ACC slot icon there is the symbol because on this unit a loopback can be acti-
vated, the symbol because it is also possible to activate a Performance Monitoring and/or the Ethernet
traffic counters. If these symbols are green, it means that the loopback is active or the Perfomance Mon-
itoring/Ethernet Counters have been activated.
By double clicking on an object it s possible to navigate to specific views. In detail:
– by double clicking on the Alarm indicator the relevant active alarm is displayed;
– by double clicking on the Abnormal Condition List box, it is possible to navigate to the Abnormal
Condition List menu;
– by double clicking on the TMN Local Interface box, it is possible to navigate to the TMN view in the
Core-E unit;
– by double clicking on a PDH slot icon, it is possible to navigate to the secondary view for the PDH
unit;
– by double clicking on a SDH slot icon, it is possible to navigate to the secondary view for the SDH
unit;
– by double clicking on a Radio slot icon, it is possible to navigate to the secondary view for the Radio
unit;
– by double clicking on an MPT-ACC slot icon, it is possible to navigate to the secondary view for the
MPT-ACC unit;
– by double clicking on a Protection switch the relevant configuration is displayed;
– by double clicking on a Loopback the relevant configuration is displayed.
The “Refresh” button will close all secondary windows, updating the main view one, and re-opening all
previously opened secondary windows, with updated content views.
All diagrams are automatically refreshed. According to the following figures, bold light green lines update
according to the actually NE working way; alarm icons update as well.
The green line is the current active path.
3.5.5.2 PDH unit secondary view
Depending on the configuration, different diagrams are shown to the operator (see Figure 155. to Figure
158.), describing the actual NE status and working mode.
Performance Monitoring icons ( ) are shown in green whenever a PM is active.
By double clicking on the Performance Monitoring icon ( ) the navigation to the WT Performance Mon-
itoring Suite starts.

Figure 155. 1+0 block diagram (PDH unit) (without Core-E protection)
Figure 156. 1+0 block diagram (PDH unit) (with Core-E protection)

Figure 157. 1+1 block diagram (PDH units) (without Core-E protection)
Figure 158. 1+1 block diagram (PDH units) (with Core-E protection)

3.5.5.3 SDH unit secondary view
Performance Monitoring icons ( ) are not supported.
Figure 159. 1+0 block diagram (SDH unit) (without Core protection)
Figure 160. 1+0 block diagram (SDH unit) (with Core protection)

Figure 161. 1+1 block diagram (SDH unit) (without Core protection)
Figure 162. 1+1 block diagram (SDH unit) (with Core protection)

3.5.5.4 Radio unit secondary view (ODU300)
Loopback icons ( ) are shown in green colour ( ) whenever a loopback is active.
Ethernet Counters icon ( ) is shown in green whenever the counter has been activated.
By double clicking on the Loopback icon, on the PM icon or on the Ethernet Counters icon the navigation
to the relevant menus starts.
The switch blocks are updated according to the signal path, following light green-coloured line.
Figure 163. 1+0 block diagram (Radio unit) (without Core-E protection)

Figure 164. 1+0 block diagram (Radio unit) (with Core-E protection)
Figure 165. 1+1 FD block diagram (Radio units) (without Core-E protection)

Figure 166. 1+1 FD block diagram (Radio units) (with Core-E protection)
Figure 167. 1+1 Hot Standby block diagram (Radio units) (without Core-E protection)

Figure 168. 1+1 Hot Standby block diagram (Radio units) (with Core-E protection)

3.5.5.5 MPT-ACC unit secondary view (MPT-HC)
Figure 169. 1+0 block diagram (MPT-ACC unit) (without Core-E protection)
Figure 170. 1+0 block diagram (MPT-ACC unit) (with Core-E protection)

Figure 171. 1+1 FD block diagram (MPT-ACC units) (without Core-E protection)
Figure 172. 1+1 FD block diagram (MPT-ACC units) (with Core-E protection)

Figure 173. 1+1 Hot Standby block diagram (MPT-ACC units) (without Core-E protection)
Figure 174. 1+1 Hot Standby block diagram (MPT-ACC units) (with Core-E protection)

3.5.5.6 MPT-ACC unit secondary view (MPT-MC)
Figure 175. 1+0 block diagram (MPT-ACC unit) (without Core protection)
Figure 176. 1+0 block diagram (MPT-ACC unit) (with Core protection)

Figure 177. 1+1 Hot Standby block diagram (MPT-ACC units) (without Core protection)
Figure 178. 1+1 Hot Standby block diagram (MPT-ACC units) (with Core protection)

3.5.6 Current Configuration View
This screen is a read-only screen, which shows the current configuration of the NE.

3.6 Menu Supervision
3.6.1 Access State

The NE can be managed by the OS or by the WebEML. To control the competition of the OS and the
WebEML, a Local Access Control (LAC) is available.
If the LAC is "access denied", it means that the OS manages the NE and the WebEML is not allowed to
modify the NE configuration (it can only "read"). In the view, the icon with a key symbol has a circular
shape.
If the LAC is "granted", it means that the WebEML is allowed to manage the NE. In the view, the icon with
a key symbol has a rectangular shape.
If the LAC is "requested", it means that the WebEML has requested a permission from the OS and is wait-
ing for a replay.
However, the OS does continue to provide a certain number of services. These services include:
– Alarm reception and processing,
– Performance processing,
– Switching back to the OS access state.
The access state of an NE can be modified from two types of views.
3.6.1.1 Requested (Switching from the OS to the WebEML access state)
Select the Supervision pull down menu. Then select the Requested option from the Access State cas-
cading menu.
If the OS does not answer in a predefined time, it is assumed that the NE is in the Craft access state and
can be managed by a WebEML.
3.6.1.2 OS (Switching from the WebEML access state back to the OS access state)
Select the Supervision pull down menu. Then from the Access State cascading menu select the OS
option.
The NE is now managed by the OS.

Note
The key symbol icon on the management states of the NE view indicates
whether the NE is managed by a WebEML or by the OS
Note
Local WebEML access is denied on recovery phase after a loss of communication of the NE.
When the communication with the NE is lost, the OS automatically recovers the
communication and forces the state existing before the loss of communication
(therefore, WebEML access can be denied or granted).
3.6.2 Restart NE
The Restart operation is a software reset and can be executed in normal traffic conditions.
From the Supervision cascading menu, select the Restart NE option.
A dialogue box opens.
Click the Yes button to confirm the restart N.E. operation
Click the No button to abort the restart N.E. operation.
WARNING: After the activation of the Restart NE Command (or after the pressing of the HW reset push-
button) the supervision of the local NE and the remote NEs is lost.

3.6.3 MIB Management
3.6.3.1 Backup
This menu allows to save on the WebEML the NE configuration.
To backup the configuration write the filename in the File Name field and press Save.
Warning: The backup file name must not include the following characters: space, &, /.
The file name contains always the version as prefix (example: "V020100_", corresponding to
version V2.1.0; "V030000_", corresponding to version V3.0.0). This prefix is inserted automat-
ically by the SW, when the MIB back-up file is created, and is used automatically by the SW,
when the MIB restore mustbe performed.
Confirm the backup operation by clicking Yes to start the operation.
When the backup is completed in the upper part appears the list of the previously created backups.
N.B. There is one default repository folder of MIB back-up files for all NEs having the same SWP-
release.
The folder name is "backup", and is under the path where you have performed the Local copy
of WebEML(Jusm/CT).
This folder is automatically selected when you perform any of the commands of the MIB man-
agerment menu.

3.6.3.2 Restore
This menu allows to download to the NE a previously created backup.
Select one of the backups to be downloaded in the upper part and press Open.
Confirm the restore operation by clicking Yes to start the operation.
When the restore is completed a message appears asking to activate the restored file. Click on Yes.
3.6.3.3 Remove file
This menu allows to remove from the list of the backups one particular backup.
To remove a backup select the backup file in the upper part and press Remove file.
Confirm the operation by clicking Yes to start the operation.
By pressing Refresh the list of backups in the upper part of the screen is updated.

3.6.4 SW Licence
In this screen the following fields are present.
– RMU Serial Number: in this read-only field appears the Serial Number of the Flash Card.
– License String: in this read-only field appears the type of the license written in the Flash Card.
– License Key: this field is used to upgrade the license. To upgrade the license copy in this field the
code of the new license and click on Apply.
The Refresh button activates a new reading of the read-only fields.

3.7 Menu SW Download
3.7.1 Server Access Configuration

This menu allows to configure the FTP server to be used to download the SWP to the NE.
Note
Copy the ECT directory present in the SWP CD on the FTP server
User Id and Password are the login information to access the FTP server.
In the Address field write the address of the FTP server.
In the Port field write the port to be used and in the Root Directory field write the directory into which the
software has been downloaded.
By clicking on the Set Default button a screen will appear, showing the default configuration.
The WebEML is the default FTP server with the following parameters:
– User Id: anonymous
– Password: -
– Address: Local host IP address
– Port: 21
– Root Dir: /
Note
The System Default can be changed by writing different values in the

fields and then by clicking on button OK

3.7.2 Init Sw Download
Through this menu the software is downloaded to the NE in order to upgrade the NE software version.
Recommended operation: Before to start the software download it is recommended to disable the ATPC
operation (if it has been enabled) and to set in RTPC mode the max. Tx power.
Follow the steps to perform this procedure:
[1] Click Add to add the available software packages on the PC.
[2] Browse to the directory where the NE software was installed and click Open.
[3] Highlight the description file (i.e. R95M.DSC) and click Open.
[4] Highlight the line and click on the Init Download button.
The Forced check box must be used to force download (i.e. the complete description file is down-
loaded to the NE).
[5] Click Yes to begin the download process.
[6] When the SW download starts, a screen showing the in progress operation of the download appears.
The download is aborted if the Abort button is pressed.
[7] Click Ok.

3.7.3 Sw Status
This menu displays information of the software installed in the NE.
The following information is displayed:

– Name: software name
– Version: software version
– Operational state: enabled or disabled
– Current status: committed or standby. The committed status refers to the software currently in use.
Note
With MPT-HC the Sw Status is available only after the MPT-HC software download completion.
Note
The equipment software is installed on the compact flash, which has two banks.
This screen has two panels (each for one bank):
- panel 1 refers to bank 1 with the Committed software and relevant information;
- panel 2 refers to bank 2 with the Stand by software and relevant information.
The Flash card, which stores the NE software, contains 2 banks.
The 2 banks can store 2 different software versions. One bank will be committed (active) and the other
bank will be standby.
Note
The second bank will appear, when a new software package has been downloaded for the first time.
During download, necessary to update the software version, the download file is automatically stored in
the standby bank.
To activate the new version first check the operational status of the standby bank. If the status is enabled
(this means that download took place without errors) select Activation or Forced Activation in the Soft-
ware Management Action field and click on the Apply Action button.
By selecting Forced Activation the bank to be activated is forced to restart.
By selecting Activation the bank to be activated restarts only if the content of the two banks differs.
Figure 179. Panel 1 (Committed software)

Figure 180. Panel 2 (Stand by software)
By clicking on the Software Units Status button a screen opens, giving additional information on the soft-
ware package.
3.7.4 How to upgrade the software from an older version

– Start the SW Download on the Standby bank (refer to par. 3.7.2)
– Activate the Standby bank by pressing Activation and Apply Action on the SW Status menu (refer
to par. 3.7.3)
– Start again the SW Download on the Standby bank (refer to 3.7.2).
– Activate the Standby bank by pressing Activation and Apply Action on the SW Status menu (refer
to par. 3.7.3)

3.8 Tab-panel Equipment
3.8.1 General
This chapter describes the types of functions offered to the operator for Equipment Management.
The equipment domain deals with the management of the NE as a whole and its physical components
(subrack, boards,..).
The main screen of the Equipment tab panel differs according to the configuration.
The equipment consists of one MSS and several ODUs according to the configuration.
In the Resource List Area is shown a graphical representation of the Equipment.
The MSS consists of different boards according to the configuration.
A colored ball gives information on the status of the associated object (Equipment, ODU, MSS, MSS
board). The color differs according to the severity of the alarms:
– Green: no alarm
– White: indetermination alarm active (not operative)
– Cyanic: warning alarm active
– Yellow: minor alarm active
– Brown: major alarm active
– Red: critical alarm active
MSS level (MSS-8 or MSS-4)
In Figure 182 is shown the MSS-8.
To enter the MSS level click on the MSS object in the Resource Tree Area.
MSS-8 consists of a subrack with 9 physical slots. Refer to Figure 182.
Slot 1 Slot 2
Slot 3 Slot 4
Slot 9
Slot 5 Slot 6
Slot 7 Slot 8
Slot 1 is reserved to the Core-E Main Controller.
Slot 2 is reserved to the Optional Spare Core-E Controller.
Slot 9 is reserved to the Fans.
Slots 3 to 8 are reserved to the units: Line-PDH unit, Line SDH unit, ASAP unit, Modem unit (to interface
ODU300), MPT Access Peripheral unit (to interface the MPT-HC or MPT-MC).
Slot 8 can be equipped also with the optional AUX peripheral unit.

During the first configuration every slot (except slot 1) must be configured according to the station con-
figuration.
To equip slot 2 click on the slot 2 icon. In the “Resource Detail Area” 3 tab-panels open. Select the Setting
tab-panel. In the type field select Core-E and click on Apply.
To equip slot 3 to 8 click on the slot icon. In the “Resource Detail Area” 3 tab-panels open. In the Type
field select the suitable unit: Line Unit (P32E1DS1 or SDHACC) or Radio Unit (MD300) or MPT Access
Peripheral unit (MPT-HC or MPT-MC) and click on Apply.
MSS-4 consists of a subrack with 5 physical slots.
Slot 1 Slot 2
Slot 5
Slot 3 Slot 4
Slot 1 is reserved to the Core-E Main Controller.
Slot 2 is reserved to the Optional Spare Core-E Controller.
Slot 5 is reserved to the Fans.
Slots 3 and 4 are reserved to the units: Line-PDH unit, Line SDH unit, ASAP unit, Modem unit (to interface
ODU300), MPT Access Peripheral unit (to interface the MPT-HC or MPT-MC).
Slot 4 can be equipped also with the optional AUX peripheral unit.
During the first configuration every slot (except slot 1) must be configured according to the station con-
figuration.
To equip slot 2 click on the slot 2 icon. In the “Resource Detail Area” 3 tab-panels open. Select the Setting
tab-panel. In the type field select Core-E and click on Apply.
To equip the other slots click on the slot icon. In the “Resource Detail Area” 3 tab-panels open. In the Type
field select the suitable unit: Line Unit (P32E1DS1 or SDHACC) or Radio Unit (MD300) or MPT Access
Peripheral unit (MPT-HC or MPT-MC) and click on Apply.
Board level
To enter a board click on the object in the Resource Tree Area or double click on the board image in the
Resource Detail Area.
ODU level
To enter the ODU level click on the ODU object in the Resource Tree Area or double click on the ODU
image in the Resource Detail Area.
Three types of ODU are available, as shown in Figure 181.

Figure 181. Available ODUs
The ODU300 is identified by a number indicating the slot number in the MSS, where the Modem unit is
installed.
The MPT-HC or MPT-MC is identified by two digits:
– the first digit indicating the slot number in the MSS, where the MPT Access unit is installed,
– the second digit indicating the enabled Ethernet port in the MPT Access unit (from 1 to 4).
N.B. The icon of the MPT-HC or MPT-MC will appear only if the MPT Access unit has been config-
ured in the MSS and one port (from 1 to 4) has been enabled.

3.8.2 Starting From Scratch
When the Equipment panel is open starting from a scratched NE, the operator will see the panel in figure
below. The Resource Tree area contains a list of empty slots that have to be configured.
Icon is used to identify an empty slot.
Figure 182. Equipment View (starting from scratch) with MSS-8
To create a unit select the slot. The setting tab-panel, shown in the figure, opens.
Select the unit type in the Equipment type profile and click on Apply.

3.8.3 Tab panels in the Resource Detail Area
For every unit there are 3 tab-panels:
– Alarms
– Settings
– Remote Inventory
3.8.4 Alarms tab-panel

The Alarms tab panel provides the fault management, which checks the current state of alarms related
to the selected object.
The alarm tab panel has one row for each possible alarm, but only rows related to the active alarms are
highlighted. When the alarm disappears it is automatically cleared in the screen.
By putting a tick in the Include alarms from sub-nodes box the alarms currently active in the sub-nodes
of the object will also appear.
For every alarm the following information is given:
– Severity: the severity associated to the alarm and assigned in the Alarm Profile
– Event Time: the time of the generation of the alarm
– Entity: the entity involved in the alarm
– Probable Cause: the probable cause of the alarm
– Managed Object Class: the class of the alarm.

3.8.5 Settings tab-panel
In the Settings tab-panel the following fields are present:
[1] Equipment Type
[2] Alarm Profile
[3] Protection Type Configuration
[4] Protection Type Configuration with MPT Access unit
[5] Protection Type Configuration with STM-1 units
[1] Equipment Type
This field lists all the units that can be installed in a specific slot.
If the user selects the expected equipment type equal to received one, the Apply button is enabled.
If the user selects an expected equipment type different from received expected equipment type, the
Apply button is disabled.
If the user applies a new expected equipment type, the panel is reloaded and updated.
If protection type is 1+1, the Apply button, related to expected equipment, is disabled (Expected equip-
ment change is allowed in 1+0 configuration only).
Figure 183. Expected Equipment Type Configuration

When a board shows the check mark icon, while same-pair (same-row) one shows switch symbol
, this means pair (row) is protected. In this situation, the couple is considered as if it is one board and
each single board cannot be removed/un-configured unless removing protection.
Check mark icon denotes “active” board while switch one represents “stand-by” board.
Same behaviour occurs when X-shaped icon , representing cross-connections, appears. PDH board
cannot be removed as well when Flow IDs are configured; this situation cannot be seen, while watching
MSS schematics as in Figure 183. An error message will be shown if the operator will try to perform such
operations.
Core-E unit configuration
Port #5 and port #6 of the Core-E can be configured in 2 ways:
– to be used as optical/electrical GigaEthernet interface for Ethernet traffic (by installing the optional
SFP)
– to be used to connect an MPT-HC
Select the option (SFP/MPT-HC) and click on Apply.
Figure 184. Core-E unit configuration
MPT Access unit configuration
In the Setting tab-panel one or two of the four Ethernet ports (to be connected to the MPT-HC or MPT-
MC) must be enabled as shown in Figure 185.
Figure 185. MPT Access settings
Select as Usage MPT-HC or MPT-MC (in 2 ports max) and click on Apply.
N.B. Port#1 and Port#2 are electrical Ethernet ports and Port#3 and Port#4 are optical Ethernet
ports.

STM-1 unit configuration
The Settings tab-panel of the STM-1 unit is shown below.
Figure 186. STM-1 unit configuration
Select the optical SFP (SFP-O) or the electrical SFP (SFP-E) installed on the STM-1 ports (SFP#1 and/
or SFP#2) and click Apply.
[2] Alarm Profile
This function relates to an alarm severity profile to be assigned to a selected object (implemented in MSS
object, in Local TMN Ethernet interface and in the Radio object).
[3] Protection Type Configuration with P32E1DS1 and MD300 units
This function allows the operator to configure the NE protection type. This function is shown selecting slots
3 to 8 only.
N.B. For slots 1 and 2 (reserved to Main and Spare Core-E boards), protection type is configured
by the system, according to equipped Core-E board.
After the equipment selection, protection type list box is filled with the allowed protection types list whose
content depends on expected equipment configured:
– If it is configured as P32E1DS1, allowed protection types are “1+0” and “1+1 EPS”;
– If it is configured as MD300, allowed protection types are “1+0”, “1+1 HSB” and “1+1 FD”.
If the operator selects a protection type equal to received one, the Apply button is disabled. If the operator
selects a protection type different from received one, Apply button is enabled. If slot is in protection mode
(received protection type different from “1+0”): Apply button related to expected-equipment is disabled
(equipment changing is allowed in “1+0” configuration only).

Figure 187. Protection Example
Configuring a 1+1 protected board, if peer board is not configured, the WebEML will be in charge of apply-
ing such configuration to un-configured peer board, before creating protection in MIB.
If the user applies a new expected protection type, both tree view and configuration panel are reloaded
and updated. With a configured 1+1 protection, involved slots are bounded by light green lines (see Figure
187.).
[4] Protection Type Configuration with MPT Access unit
To configure the protection scheme select the MPT as shown in Figure 188. (In the example MPT-HC#72:
connected to Port#2 of the MPT Access unit in Slot#7).

Figure 188. How to configure the protection
Choose in the Protect Port field one the ports available in the list. As protection can be also used an MPT
connected to the same MPT Access unit.
Choose the suitable Protection Type (1+1 FD or 1+1 HSB) and click on Apply.
After the configuration in the screen will appear the two jointed MPT-HC as shown in Figure 189.

Figure 189. Protected configuration with MPT-HC
[5] Protection Type Configuration with STM-1 units
To configure the protection select 1+1 EPS in the Protection Type field and click Apply.
Figure 190. Protection configuration with STM-1 units
N.B. The field Protection Type appear only when the 2 STM-1 units have the same configuration
(only with SFP-O, not with SFP-E).
3.8.6 Remote Inventory tab-panel

The Remote Inventory feature stores information used to identify all product components.
The whole information related to selected equipment type can be read, if available, in the remote inventory
panel, inside the Resource Detail area. Remote inventory data won’t be available for levels that do not
have remote inventory itself, as IDU Ch#1 or IDU Ch#0.

3.8.7 How to configure a new equipment
The recommended sequence to configure the NE is the following:
1) Enable the plug-in units: refer here in TAB-PANEL EQUIPMENT
2) Configure the Core-E unit: refer to Core-E VIEW for Core-E and ETHERNET DOMAIN (this
menu opens with double click on a Core-E unit).
Warning: Verify in the Configuration > System Setting menu that the “Ethernet LOS Criteria”
field is disabled.
3) Configure the Modem unit or the MPT Access unit: refer to RADIO VIEW for RADIO DOMAIN
(this menu opens with double click on a Radio unit) (Settings)
4) Configure the PDH unit: refer to PDH VIEW for PDH DOMAIN (this menu opens with double
click on a PDH unit)
5) Configure the SDH unit: refer to SDH VIEW for SDH DOMAIN (this menu opens with double
click on an SDH unit)
6) Configure the ASAP unit (if any): refer to ATM VIEW for ATM DOMAIN (this menu opens with
double click on an ASAP unit)
7) Create Traffic Descriptors for ATM traffic: refer to MENU CONFIGURATION (Traffic Descrip-
tors)
8) Configure the LAGs (Ethernet or Radio) (if any): refer to MENU CONFIGURATION (Ethernet
Features Shell)
9) Configure the AUX peripheral unit, if any, to enable the 64kbit/s service channels and to use
the external points: refer to AUX VIEW for AUX DOMAIN (this menu opens with double click
on the AUX Peripheral unit)
10) Configure the Synchronization: refer to TAB-PANEL SYNCHRONIZATION
11) Configure the NE time: refer to MENU CONFIGURATION (NE Time)
12) Configure the System parameters: refer to MENU CONFIGURATION (System Settings)
13) Create the Cross-connections: refer to MENU CONFIGURATION (Cross-connections)
14) Create the Auxiliary Service Channel cross connections, if the AUX peripheral unit has been
installed: refer to MENU CONFIGURATION (AUX Cross Connections)
15) Configure IP/SNMP: refer to MENU CONFIGURATION (Network Configuration)
16) Select the VLAN configuration and create VLAN, if required: refer to VLAN MANAGEMENT

3.9 Tab-panel Protection Schemes
This domain is present in 1+1 configuration only.
This domain view consists of the following areas:
– Resource Tree Area: displays all the protection schemes currently implemented for every pair of
units.
– Resource List Area: displays tabular information about the selected resource in tree area.
– Resource Detail Area: displays, through tabbed windows, the properties done in list area. This area
enable to perform the available functions for involved resource.
By clicking on the tree root the tree will be expanded according to the protection schemes supported.
A single left click selection of an element tree causes the activation of the corresponding representation
displayed in the “Resource List area”.
The 1+1 implemented protection schemes are:
– Equipment protection: EPS protection in Tx and Rx sides. This protection scheme can be imple-
mented for all the unit types: Modem unit, PDH unit, SDH unit and Core unit.
– Rx Radio protection: RPS Hitless Switch in Rx side (available for the Radio unit only)
– HSB protection: Hot Stand-by protection (available for the Radio unit only)
– FD protection: Frequency Diversity protection (available for the Radio unit only)
– Synchronization protection: This protection scheme will appear, if in the Synchronization tab panel
the Primary Source and the Secondary Source have been selected or the NE has been configured
as Master with Free Running mode.
Note 1
For the pair of Core-E units (slot 1 and 2) the only protection type is the
Equipment Protection in not revertive mode.
Note 2
For the pair of Radio units or MPT Access units the protection type are the Equipment Protection, Radio
Protection and HSB Protection or FD protection.
Note 3
For the pair of PDH units the only protection type is the Equipment Protection.
Note 4
For the pair of SDH units the only protection type is the Equipment Protection.

Figure 191. Protection scheme screen
To see the current position of the switches enter the menu Diagnosis → Summary Block Diagram View
and click on the icon of the equipped units.
The green line in the screen shows the current active path.
Figure 192. 1+1 PDH unit block diagram

Figure 193. 1+1 SDH unit block diagram
Figure 194. 1+1 FD Radio unit block diagram (ODU300)

Figure 195. 1+1 HSB Radio unit block diagram (ODU300)
Figure 196. 1+1 FD Radio unit block diagram (MPT-HC)

Figure 197. 1+1 HSB Radio unit block diagram (MPT-HC)
Figure 198. 1+1 HSB Radio unit block diagram (MPT-MC)
N.B. In Figure 198 is shown a connection in Tx side between the two MPT-MC. This connection is
not implemented by a cable, but it is a logical connection.

3.9.1 Equipment Protection Management
The Equipment Protection Management is performed by selecting the Equipment Protection tree element.
This window allows a complete view of all NE resource involved in the EPS protection.
The tab-panels are:
– Protection Schema Parameters
– Commands
3.9.1.1 Protection Schema Parameters
The tab-panel “Schema Parameters” displays the parameters that can be modify.
The parameters are:
– Protection Type: this parameter is defined at creation time and it is read only. The supported type
is: 1+1, e.g. a working channel (Main) is protected by a protecting channel (Spare).
– Restoration Criteria: it defines if automatic restoration from protecting to protected channel is

allowed (revertive mode) or inhibited (not revertive mode). The operator choice for “Operation Type”
will be applied by clicking on “Apply” button.
Note
The Core-E protection type is Not-Revertive and cannot be changed.

The PDH/SDH protection type is Not-Revertive and cannot be changed.
Note
In case of 1+1 HSB-EPS, the restoration criteria are always greyed out.
No changes can be done separately for 1+1 HSB-EPS.
The restoration criteria selected for HSB-TPS will be applied to EPS automatically.
3.9.1.2 Commands
To enter the Commands menu click on the Spare #0 element in the Tree view or on the Main #1 element.
The operator by the WebEML can modify the state of the switch through commands Lockout, Forced
and Manual. Select the suitable command and click on Apply.
Note
On the Main#1 channel the only available commands are Manual and
Forced (only Forced for the Core-E protection).
On the Spare#0 channel the only available commands are Manual and
Lockout (only Lockout for the Core-E protection).

Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel), inde-
pendently of the possible active alarms. This command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation of this command forces in service
Channel 0, independently of the possible active alarms. This command activates signaling ABN.
Automatic Switch is the normal operation condition: the position of the switch depends on the commands
generated by the logic.
Manual has the lowest priority: it is performed only if there are no alarms that can activate an automatic
switch. It cannot be performed if Lockout or Forced commands are already activated. If this command is
active, it will be removed by an incoming alarm. This command does not activate signaling ABN.
WARNING:All the commands are not error free.
Note
The “Forced” command for channel 1 is equivalent to the “Lockout” command for the channel 0.
In both case, the result is that the relevant channel protection path is forced to standby status.
Table 30. Command priority list

Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
Note
To release a previously activated command select None and click on Apply.
Warning for Core-E protection in Stacking

Configuration with 3 NEs
If the “Static Lag Criteria” has not been enabled in the System Settings menu, after a
Forced command to restore the correct operation the Lockout command has to be entered.

3.9.2 Rx Radio Protection Management
The Radio Protection Management is performed by selecting the Rx Radio Protection element tree.
This window allows a complete view of all NE resource involved in a RPS protection.
The tab-panels are:
– Commands
The tab-panel “Protection Schema Parameters” displays the parameters that can be modify.
The Schema Parameters are:
– “Protection Type” field: defines the protection schema architecture: 1+1 hitless;
– “Operation Type” field: the possible values are revertive (automatic restoration allowed) or notRe-
vertive (automatic restoration Inhibited).
3.9.2.2 Commands
To enter the Commands menu click on the Spare #0 element in the Tree view or on the Main #1 element.
The operator by the WebEML can modify the state of the switch through commands Lockout, Forced and
Manual. Select the suitable command and click on Apply.
Note
On the Main#1 channel the only available commands are Manual and Forced.
On the Spare#0 channel the only available commands are Manual and Lockout.
Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel), inde-
pendently of the possible active alarms. This command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation of this command forces in service
Channel 0, independently of the possible active alarms. This command activates signaling ABN.
The Manual command can be activated only if the two channels are aligned.

Note
The “Forced” command for channel 1 is equivalent to the “Lockout” command for the channel 0. In both
case, the result is that the relevant channel protection path is forced to standby status.

Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
Note

3.9.3 HSB Protection Management
The Transmission Protection Management is performed by selecting the HSB Protection element tree.
This window allows a complete view of all NE resource involved in the protection.
The tab-panels are:
– Commands
The tab-panel “Protection Schema Parameters” displays the parameters that can be modify.
The Schema parameters are:
– Protection Type: this parameter is defined at creation time and it is read only. The supported type
are: 1+1 (onePlusOne) ,e.g. a working element is protected by one protecting unit.
– Operation type: it defines if automatic restoration from protecting to protected unit is allowed (rever-
tive mode) or inhibited (not revertive mode). The operator choice for “Operation Type” will be applied
clicking on “Apply” button.
3.9.3.2 Commands
To enter the Commands menu click on the Spare #0 element or on the Main #1 element in the Tree view.
The operator by the WebEML can modify the state of the switch through commands Lockout, Forced
and Manual. Select the suitable command and click on Apply.
Note
On the Main#1 channel the only available commands are Manual and Forced.
On the Spare#0 channel the only available commands are Manual and Lockout.
Lockout has higher priority than Forced: the activation connects to the antenna Transmitter 1 (default
transmitter), independently of the possible active alarms. This command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation of this command connects to the
antenna Transmitter 0, independently of the possible active alarms. This command activates signaling
ABN.
WARNING:All the commands are not error free.

Note
The “Forced” command for channel 1 is equivalent to the “Lockout” command for the channel 0. In both
case, the result is that the relevant channel protection path is forced to standby status.

Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
Note

3.10 Tab-panel Synchronization
The Synchronization menu allows the operator to manage the synchronization features.
Using “Synchronization” tab view (shown in the figure below) the operator can select and configure syn-
chronization source(s) for the equipment.
Together with “Role” and “Restoration” criteria, the operator can select Input and Output ports and can
discriminate between different possible “Primary” or “Secondary” sources, according to the Role.
Figure 199. Synchronization Settings view
The Resource list area shows the configuration summary describing current synchronization.
As for all other views, Synchronization contains Alarms tab as well and it allows discriminating synchro-
nization-specific alarms.
Each Network Element must have a reference Clock (NEC), which will be distributed to each board of the
NE. Such clock is a 25 MHz generated in the CORE Module in the Clock Reference Unit (CRU) function.
The NEC is locked to a Synchronization Source.
The NEC also provides a Sync Out port on the Core Module, which can be used to synchronize other NEs.

3.10.1 Synchronization Sources assignment
The physical interfaces to be assigned to Primary and Secondary synchronization sources can be chosen
among the following:
[1] Free Run Local Oscillator. Quality Level value is fixed to QL-SEC/EEC1 (G.812/G8262), the value
of QL Priority is Master1 if the NEC is configured as Master and Slave1 if the NEC is configured as
Slave.
[2] Any E1 available at input traffic interfaces (the specific E1 port has to be chosen). Default value for
Quality Level is QL-SSU-A (G.812), the value of QL Priority is Master1 if the NEC is configured as
Master and Slave1 if the NEC is configured as Slave.
[3] A specific synchronization signal available from the dedicated Sync-In port, which can be configured
according the following options:
a) 2.048 MHz, electrical levels according to G.703, clause 13;
b) 5 MHz, + 6 dBm into 50 ohm, sine-wave;
c) 10 MHz, + 6 dBm into 50 ohm, sine-wave;
d) 1.024 MHz, electrical levels according to G.703, clause 13 with the following exceptions:
– timing properly scaled from 2.048 MHz to 1.024 MHz.
[4] The Symbol Rate of the RX signal of any available Radio (the specific Radio Port has to be chosen).
When the SSM support is enabled the QL and QL Priority are acquired from ESMC PDUs received
on the specific radio interface. When the SSM support is disabled the default value for Quality Level
is QL-SSU-A (G.812), the value of QL Priority is Master1 if the NEC is configured as Master and
Slave1 if the NEC is configured as Slave.
[5] Any Synchronous Ethernet clock source available at enabled User Ethernet traffic interfaces (both
electrical and optical) configured in synchronous slave operation mode (the specific User Ethernet
port has to be chosen).
From ITU-T G.8261 point of view, the MSS is a Synchronous Ethernet equipment equipped with a
system clock (NEC) following the ITU-T G.8262 recommendation. A User Ethernet interface con-
figured in synchronous operation mode can work only at 1000 Mbit/s. In the particular case of elec-
trical User Ethernet interfaces, these interfaces perform link auto negotiation to determine the
master/slave role for clocks delivery over the link. The clock slave role must be configured as part
of auto negotiation parameters in order to use the interface as Synchronous Ethernet clock source
input, either as Primary or Secondary. This check is performed by WebEML/NMS but not by EC. The
clock master role must be configured as part of auto negotiation parameters in order to use the inter-
face as Synchronous Ethernet clock source output to distribute NEC to other equipments. For Syn-
chronous Ethernet clock sources from electrical User Ethernet ports the Fail alarm will be raised
when Loss of Synch (i.e. Ethernet Link Down) will happen. For Synchronous Ethernet clock sources
from optical User Ethernet ports the Fail alarm will be raised when Loss of Optical signal will happen.
[6] Any STM1 available at SDH input traffic interfaces (the specific STM1 port must be selected). Default
value for Quality Level is QL-SSU-A (G.812), the value of QL Priority is Master1 if the NEC is con-
figured as Master and Slave1 if the NEC is configured as Slave.
[7] None of the above, this means that no physical synchronization interface is assigned to the syn-
chronization clock source input. In case of failure of the other clock source input the CRU enters the
Holdover state.

3.10.2 Synchronization sources assignment rules
Some rules have to be followed while assigning the Primary and Secondary clock sources.
The NEC has to be defined (configured) as Master or Slave.
– If a specific interface is chosen as Primary, it cannot be selected as Secondary too.
– If an E1/T1 is chosen to be Primary source, another E1/T1 coming from the same peripheral cannot
– If an MPT radio interface is chosen to be Primary source, another MPT radio interface connected
to the same MPT Access peripheral cannot be selected as Secondary source and vice-versa.
– If an STM1 is chosen to be Primary source, another STM1 coming from the same peripheral cannot
3.10.3 Allowed synchronization sources assignment

Only one Master is allowed in the network.
If Master:
– The Restoration Mode must be chosen between Revertive and Non-Revertive;
– The Primary clock source input must be chosen among 1), 2), 3), 5) or 6).
If the selected Master Primary clock source input is 1):
– the Master Secondary clock source input doesn't need to be selected because the Primary is never
supposed to fail. If the selected Master Primary clock source input is 2), 3), 5) or 6):
– the Master Secondary clock source input must be selected among 1), 2), 3), 5), 6) or 7).
If Slave:
– The Restoration Mode is fixed to Revertive.
– The Primary clock source input must be chosen among 3), 4) or 5). Slave Primary clock source input
is allowed to be 3) or 5) for full indoor configuration and for Piling configuration.
– The Secondary clock source input must be chosen among 1), 2), 3), 4), 5), 6) or 7).

3.10.4 SSM Summary Table
By pressing the SSM Summary button the SSM summary Table opens, which shows the SSM status
(enabled/disabled) of the interfaces carrying the SSM messages.
Figure 200. SSM Summary Table

3.11 Tab-panel Connections
This menu (available in the Main view) contains a summary table for all the cross-connections. This is
shown in the figure below.
In the Resource Detail Area are available two different functions usable to export and save cross-con-
nections data with different formats: hardcopy (Send To Printer) and File (Export To File).
Figure 201. Cross-Connections View

3.12 PDH VIEW for PDH DOMAIN (this menu opens with double click on
a PDH unit)
3.12.1 General information on the PDH domain menu

The PDH domain view allows the operator to manage the E1 streams.
– Resource Tree Area: displays the radio ports sorted by channel number.
– Resource Detail Area: displays, through tab windows, the object’ s properties selected in list area.
This area enables to execute the available functions for involved resource.
Two tab panels are present in the Resource Detail Area:
– Alarms & Settings: shows the active alarms and allows to configure the E1 streams
– Loopback: activates the loopbacks available with the equipment.
Refer to par. 3.12.2.4 to enable the Node Timing.
3.12.2 Alarms & Settings
In the Resource List Area is given the information related to the tributaries:
1) Port Number: port for a given channel and type of port
2) Signal Mode: type of frame (Unframed/Framed/Disabled)

3) Flow Id: identifier of the tributary for the cross-connection
4) Service Profile: possible profile to be associated to the tributary (TDM2TDM/TDM2Eth)
5) Payload: bytes of the payload (256)
6) ECID Tx: Emulated Circuit Identifier in Tx direction (up to 65.536)
7) ECID Rx: Emulated Circuit Identifier in Rx direction (up to 65.536)
8) TDM Clock source: type of the clock to be associated to the tributary (Adaptive/Differential/
Node Timing)
N.B. The selection of TDM clock source (clock recovery type) as to be common for all the E1 belong-
ing to the same 32E1 PDH card, independently if the node timing has been enabled in the same
NE, it is possible to mix 32 E1 PDH card with E1s set in DCR and 32 E1 PDH card with E1s
set in ACR. Of course the NODE TIMING must be use properly
Note
Columns 5, 6, 7 and 8 are only available if the Service Profile is TDM2Eth.
For every E1 tributary two tab-panels are available:
– Alarms tab-panel
– Settings tab-panel
3.12.2.1 Alarms tab-panel

3.12.2.2 Settings tab-panel
This tab-panel performs all available functions for a tributary port. The managed tributary types are: E1.
To define the involved ports, the interface selection in the tree view is first required; therefore the selection
of the desired tributary port in the tabular view enables the “Resource Detail list” to show the available func-
tions for the single one resource.
Warning: to change something in the Settings tab-panel first change the Signal Mode to Framed/
Unframed. Then, all the other fields can be changed.
In the Setting tab-panel there are the following fields:
Port Number: identifies the ports for a given interface and type of port (read-only fields)
Signal Mode:
The possible values are:
– Unframed for the unframed received signal
– Framed for the collection of the performances at the input in Tx side and at the output in Rx side
– Disabled
The current state can be modified selecting a different signal mode value and then click on the “Apply”
button to send the new value to NE.
Service Profile:
The possible profiles are:
– TDM2TDM
– TDM2Eth
Flow Id: To implement cross-connections between line side and radio side each E1 tributary must be
associated to an identifier. Enter the Flow identifier value in the relevant field (possible values: 2 to 4080)
and press Apply.
WARNING: The Flow Id must be unique in the MPR network.
Fields ECID Tx, ECID Rx, Payload Size and TDM Clock Source can be written only if the Service Profile
is TDM2Eth.

Note
With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP - Real Time Protocol
is used); with the TDM2Eth service profile the TDM Clock source can be Differential (RTP - Real Time
Protocol is used) or Adaptive (RTP is not used). In the unit it is not possible to have mixed configura-
tions with service profiles using RTP and other service profiles not using RTP.
Example: if in the unit only one E1 has service profile TDM2TDM it is possible to configure other E1 with
service profile TDM2Eth only with the Differential clock source (not with the Adaptive clock source). If the
Adaptive clock source is requested the E1 must be connected to another PDH unit.
Alarm profile: Not implemented now.
Buttons:
Apply: the configuration for the selected E1 tributary will become active
Apply to All: the configuration present in the screen will be applied to all the ports.
Help: by clicking on this button the operator calls the help on line.
3.12.2.3 General information on Circuit Emulation
9500 MPR-E performs Circuit Emulation on PDH TDM flows, and then transport those "TDM packets"
mixed to native Ethernet frames.
The Circuit Emulation IWF (inter-working function) is according the Metro Ethernet Forum implementation
agreement known as MEF 8, limited to the structure agnostic case.
MEF 8 emulated circuits is based on exchange of service parameters between two CES IWFs at either
end of the emulated circuit; if one of those IWFs belong to the 9500 MPR-E the following parameters are
defined:
– MAC addresses of the two IWFs
– Payload size
– ECID (2 different values may be used for each direction). It is suggested to set ECID Tx and ECID
Rx with the same value of the Flow Id.
– TDM clock source

• adaptive
• differential
• node timing
– VLAN (One Vlan is assigned to each bi-directional circuit emulated E1 flow)
Two different cases of Circuit Emulation services are implemented:
1) TDM2TDM
2) TDM2ETH

TDM2TDM
Both the IWFs belong to 9500 MPR-E and the packets are not supposed to go out the 9500 MPR-E net-
work.
– MAC addresses are determined as consequences of the cross connections.
– Payload size: fixed to 121 bytes
– ECID will be the same value as Flow Id
– TDM clock source: differential, node timing
TDM2ETH
Only one of the IWFs belongs to 9500 MPR-E and the packets are supposed to go out the 9500 MPR-
E network.
– MAC addresses: in all involved nodes are determined as consequences of the cross connections;
the only exception is the Ethernet Terminal Node (the node where that TDM2ETH traffic goes
through an user Ethernet port). In such ETN the source address will be the node Mac address, the
dest. mac address will be provisioned by ECT/NMS.
– Payload size: fixed to 256 bytes
– ECID : provisioned by ECT/NMS, 2 different values may be used for each direction
– TDM clock source will be provisioned by ECT/NMS: adaptive, differential, node timing
– Flow Id will be provisioned by ECT/NMS (One Vlan is assigned to each bi-directional circuit emulated
E1 flow)

3.12.2.4 Node Timing configuration
Click on the Slot icon (as shown in Figure 202.) to access the Node Timing menu.
Figure 202. Node timing
Node Timing: timing from the network clock as defined in G.8261. The enabling of the Node Timing is
applied to all E1s of the PDH unit.
By enabling the Node Timing the E1 streams in Rx side are retimed at the output with the network element
clock.

3.12.3 Loopback
The functions described in this section allow to perform the test operations by loopbacks.
Note
The loopbacks can be activated on the local NE only
In the Resource List Area are listed all the loopbacks which can be performed. In the current software
version only the IF cable loopback is available.
In this area the following information is given:
1) Interface: number of the channel and type of the loopback
2) Direction: type of the loopback
3) Activation: activation status of a loopback (Active/Not Active)
4) Activation date: date of loopback activation
5) Timeout: timeout period, if has been set.
Figure 203. E1 Loopbacks

3.12.3.1 How to activate a loopback
[1] Select the E1 tributary and select the loopback to be activated by clicking on the relevant object in
the Resource Tree Area or by selecting the relevant row in the Resource List Area.
[2] Select Active in the Activation field.
[3] Click on Apply.
[4] The Loopback is now ACTIVE (in the row in the Resource List Area the Activation field of the loop-
back will change from Not Active to Active).
Note
In the Timeout Period field a timeout period can be set for the loopback activation (max. 4 days).
At the end of this period the loopback will be automatically deactivated.
3.12.3.2 How to remove a loopback
[1] Select the loopback to be removed by clicking on the relevant object in the Resource Tree Area or
by selecting the relevant row in the Resource List Area.
[2] Select Not Active in the Activation field.
[3] Click on Apply.
[4] The Loopback is now DEACTIVATED (in the row in the Resource List Area the Activation field of the
relevant loopback will change from Active to Not Active).

3.13 SDH VIEW for SDH DOMAIN (this menu opens with double click on
an SDH unit)
3.13.1 General information on the SDH unit

The STM-1 unit supports up to 2 STM-1 interfaces.
The STM-1 signal is transported in a transparent way.
Link options include:
– 1+0 non-protected operation
– 1+1 EPS protection
3.13.1.1 Protection
When the protection of the unit is required (1+1 EPS protection), two STM-1 units must be installed.
The protection can be implemented only with the optical interface by using a splitted optical cable.
3.13.1.2 Tab-panels
Two tab-panels are present:
– Alarms: shows the active alarms
– Settings: allows to configure the STM-1 interface.
3.13.2 Alarms

3.13.3 Settings
This tab-panel allows to configure the STM-1 signal.
To configure the STM-1:
1) Put a check mark in the Port Status box to enable the STM-1.
2) Click on Apply.
3) Set the Auto Laser Shutdown: Enabled/Disabled ForcedOn/Disabled ForcedOff. This field
will appear only if the Settings tab-panel of the STM-1 unit the optical SFP has been selected.
4) Enable the J0, if required, by selecting one of the two modes (SixteenBytesFrame/OneRe-
peatedByte) and in the Expected Receiving Value field enter the expected value. Note: byte
J0 is only read, no Regeneration section Termination is done.
5) Click on Apply on the left part.
6) Enter the Flow ID (range: 2 to 4080). Warning: the flow id must be unique in the MPR network.
7) Select the Jitter Buffer Depth: High/Low.
8) Select the TDM Clock Source: Differential/Node Timing.
9) Click on Apply on the right part.
N.B. The Service profile is fixed to SDH2SDH: the STM-1 is packetized and is transmitted over an
MPR radio port.
N.B. The Alarm Profile field is not supported in the current release.

3.14 RADIO VIEW for RADIO DOMAIN
This menu opens with double click on a Modem unit for ODU300 and with double click on the MPT
Access unit or on the MPT-HC or MPT-MC.
3.14.1 General information on the Radio domain menu

The Radio domain view allows the operator to manage the resources of the radio transmission channel.
Three types of Outdoor Units are available:
1) ODU300 (up to 256 QAM/up to 56 MHz)
2) MPT-HC (High Capacity: up to 256 QAM/up to 56 MHz)
3) MPT-MC (Medium Capacity: up to 128 QAM/up to 28 MHz)
A Radio NE consists of one or two radio channels with a set of functional blocks (tributary ports, radio ports
etc).
– Resource Tree Area: displays the radio ports sorted by channel number.
– Resource Detail Area: displays, through tab windows, the object’ s properties selected in list area.
This area enables to execute the available functions for involved resource.
Four tab panels are present in the Resource Detail Area:
– Alarms: shows the active alarms
– Settings: configures the radio parameters
– Measurements: performs the Tx and Rx power measurements.
– Loopback: activates the loopbacks available with the equipment.
The tab-panel Power Source is available only with the MPT Access unit to interface MPT-HC or MPT-MC.

3.14.2 Alarms
3.14.3 Settings
3.14.3.1 ODU300
3.14.3.1.1 General
To configure click in the Main view on the icon of the Modem unit to be configured.
The Radio Main View opens.
The Radio Main View is divided in two parts:
– on the left side is present the Direction # area
– on the right side is present the Channel #1 area (for 1+0 configuration) and Channel #1 and Channel
#0 areas (for 1+1 configuration).
Warning: to configure the Radio unit first configure the Shifter and the Tx Frequency in the Frequency
field (in the Channel area) and click on Apply. Then configure all the other parameters.
3.14.3.1.2 Direction area
This part of the screen is divided into 5 parts:
1) Mode
2) Link Identifier Configuration
3) PPP RF
4) Alarm Profile
5) Synchronization

1) Mode
The operation mode can be without or with the Adaptive Modulation.
a) Operation without the Adaptive Modulation
Figure 204. Modem unit without Adaptive Modulation settings (ODU300)
– Select in the Mode field “Presettings”.
– Select in the Reference Channel Spacing field the suitable channel spacing to be used.
– Select in the Modulation field the suitable Modulation scheme.
– According to the selected Channel Spacing and to the Modulation the relevant capacity in the Capac-
ity field will appear.
– To confirm the selection click on Apply.

b) Operation with the Adaptive Modulation
The main idea behind Adaptive Modulation in Point to Point system is to adjust adaptively the modulation
as well as a range of other system parameters based on the near-instantaneous channel quality infor-
mation perceived by the receiver, which is fed back to the transmitter with the aid of a feedback channel.
The switching between the modulation schemes is hitless and maintains the same RF channel bandwidth.
The Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB) without ATPC.
Figure 205. Modem unit with Adaptive Modulation settings (ODU300)
To configure the Adaptive Modulation:
– Select in the Mode field “Adaptive Modulation”.
– Select in the Modulation Range field the Modulation range (4/16 QAM or 4/16/64 QAM) to be used
by the Adaptive Modulation.
– Select in the Reference Channel Spacing field the suitable channel spacing.
– Select in the Reference Mode field the spectral efficiency class to be set as reference.
– Select in the Remote Switching Threshold field how many dB the switching thresholds have to be
moved from the default value (+4 dB/-2 dB). The default value is approx. 6 dB below the 10-6 Rx
threshold.
The Current Modulation field is a read-only field, which shows the current used modulation. The current
modulation will depend on the fading activity during the propagation.

With a check mark in the Manual Operation box it is possible to force a modulation scheme by selecting
the scheme in the Forced Modulation field.
Note
Note: If the current Modulation scheme is 4 QAM, it not possible to force to 64 QAM, but first must be
forced to 16 QAM and then to 64 QAM. Also if the current Modulation is 64 QAM, to pass to 4 QAM first
must be forced to 16 QAM and then to 4 QAM.
Warning: with the up and down arrows, below the Forced Modulation field, it is possible to increase or
decrease the part of the screen relevant to the parameters of the Adaptive Modulation.
How to change the operation mode (from operation without Adaptive Modulation to operation with
Adaptive Modulation) in 1+1 HSB configuration
Follow the procedure:
1) Mute the 2 Transmitters
2) Remove the protection scheme: enter the Equipment tab-panel, select the unit and remove the
protection scheme
3) Enter the Main Radio unit setting tab-panel: set Mode Adaptive Modulation
4) Create again the protection scheme: enter the Equipment tab-panel, select the unit and create
the protection scheme (1+1 HSB)
5) Remove the muting from the Transmitters.
Note 1: Channel Spacing Change

A specific behavior must be followed when the Channel Spacing needs to be changed, to pre-
serve any pre-configured TDM or ATM PW. Consequently, two cases must be taken into
account: Capacity Up-grade and Capacity Down-Grade.
Capacity Up-Grade
When the admission control is enabled, this applies when the lowest modulation scheme of the
new channel spacing has a capacity which is larger than the one with the old channel spacing.
In this case all the pre-configured TDM or ATM PW will be kept. The residual bandwidth for the
lowest modulation scheme is recomputed.
When the admission control is disabled, this applies when the highest modulation scheme of
the new channel spacing has a capacity which is larger than the one with the old channel spac-
ing. In this case all the pre-configured TDM or ATM PW will be kept. The residual bandwidth
for the highest modulation scheme is recomputed.
Capacity Down-Grade
When the admission control is enabled this applies when the lowest modulation scheme of the
new channel spacing has a capacity which is smaller than the one with the old channel spacing.
If all the pre-configured TDM or ATM PW stays in the capacity associated to the lowest mod-
ulation scheme, they will be kept and the residual bandwidth for the lowest modulation scheme
is recomputed. If all the pre-configured TDM or ATM PW cannot stay in the capacity associated
to the lowest modulation scheme, the change of channel spacing is rejected by WebEML/NMS.

When the admission control is disabled this applies when the highest modulation scheme of
the new channel spacing has a capacity which is smaller than the one with the old channel spac-
ing. If all the pre-configured TDM or ATM PW stays in the capacity associated to the highest
modulation scheme, they will be kept and the residual bandwidth for the highest modulation
scheme is recomputed. If all the pre-configured TDM or ATM PW cannot stay in the capacity
associated to the highest modulation scheme, the change of channel spacing is rejected by
WebEML/NMS.
Note 2: Modulation Change

When the AM engine changes the modulation, the pre-configured TDM or ATM PW traffic must
be managed according to the behavior here after described. Two cases must be taken into
Capacity Up-Grade
This applies when the new modulation scheme has a capacity which is larger than the old one.
When the admission control is enabled all the pre-configured TDM or ATM PW are kept. When
the admission control is disabled all the pre-configured TDM or ATM PW will work if the current
capacity is able to support all of them, otherwise all pre-configured TDM or ATM PW will not
work.
Capacity Down-Grade
This applies when the new modulation scheme has a capacity which is smaller than the old one.
When the admission control is enabled, since the admission control was performed with the
capacity of the lowest modulation scheme, all the pre-configured TDM or ATM PW will be kept.
When the admission control is disabled, since the admission control was performed with the
capacity of the highest modulation scheme, all the pre-configured TDM or ATM PW will be kept
if the current capacity is able to support all of them, otherwise all pre-configured TDM or ATM
PW will be completely lost.
Note 3: Modulation Working Mode Change

A specific behavior must be followed when it is needed to move from Adaptive Modulation to
Static Modulation or vice-versa, in order to preserve any pre-configured TDM or ATM PW.
Two cases must be taken into account: from Static to Adaptive Modulation and from Adaptive
to Static Modulation.
The working mode changes, here below described, are generic. The changes cover both the
change of the modulation but with the same Channel Spacing and the change of the Channel
Spacing.
From Static to Adaptive

Adaptive Modulation can be enabled only if the ATPC is disabled.
When the Adaptive Modulation is enabled and Admission Control is enabled the behavior is:
If all the pre-configured TDM or ATM PW in the Old Static Modem Profile, stay in the capacity
associated to the lowest Modulation Scheme, the request of change is accepted and the resid-
ual bandwidth for the lowest Modulation Scheme is computed. If all the pre-configured TDM or
ATM PW cannot stay in the capacity associated to the lowest Modulation Scheme, the request
of change is rejected.
When the Adaptive Modulation is enabled and Admission Control is disabled all the pre-con-
figured TDM or ATM PW in the Old Static Modem Profile stay in the capacity associated to the
highest Modulation Scheme, then the request of change is always accepted and the residual
bandwidth for the highest Modulation Scheme is computed.

From Adaptive to Static
When the Adaptive Modulation is disabled, if all the pre-configured TDM or ATM PW in the Old
Adaptive Modem Profile, stays in the capacity of the New Static Modem Profile, the request is
accepted and the residual bandwidth for new Static Modem Profile will be computed. If all the
pre-configured TDM or ATM PW cannot stay in the capacity of the New Static Modem Profile,
the request of change is rejected.
2) Link Identifier
This part allows the operator to define the expected and sent identifier values of parameters related to
the link management and, if necessary, modify them.
The operator choices will be sent to the NE by clicking on the related “Apply” button.
If the Link Identifier is Enabled the following fields can be written:
– Expected Identifier: this field is the link identifier expected at the receiving NE
– Sent Identifier: this field is the link identifier inserted on the transmitting NE.
3) PPP RF
The “PPP-RF” interface is a communication interface based on the use of an inframe RF proprietary 64
kbit/s channel. Through the “PPP-RF” interface the NE can exchange management messages with a
remote OS (or WebEML) station.
The PPP-RF channel can be Enabled or Disabled.
If enabled, in the Remote Address field will appear the IP address of the remote connected NE.
In the Routing IP Protocol field enter the used IP protocol and in case of OSPF protocol select also the
associated OSPF area.
4) Alarm Profile
Not implemented in the current release.
5) Synchronization
Tick on Enable to enable the transmission of the SSM message over the radio channel.

3.14.3.1.3 Channel area
This area is divided in 5 parts:
a) Frequency
b) ATPC (this menu is alternative to RTPC menu)
c) Manual Transmit Power Control (this menu is alternative to ATPC menu)
d) Tx Mute
e) Alarm Profile
a) Frequency
The system can operate with different types of ODU according to the RF band and to the channel arrange-
ment. There are ODUs which can manage only one shifter or several predefined shifters.
In the Shifter field select the suitable shifter and press Apply.
In the Tx frequency field insert the suitable Tx frequency (the Rx frequency is automatically calculated
by using the inserted Tx frequency and the shifter) and press push-button Apply.
By pressing the Data Help button the list of all the available ODUs with the relevant P/N, shifter and Tx
frequency will appear. The Data Help table is usefull, if you are not connected to the ODU.
b) ATPC
Note
the ATPC area is not present if the Adaptive Modulation has been selected.
The ATPC can be Enabled or Disabled.
The new value will be applied when the Apply button is pressed. If the ATPC has been enabled, the ATPC
Range and ATPC Rx Threshold parameters must be filled.
ATPC Range
The Min Tx power and Max Tx power, regarding the Tx Range in the ATPC management, can be
written in the relevant field.
When the Apply button is pressed the new values will be applied.
ATPC Rx Threshold
The value of the low power threshold can be changed by writing the new value in the field. When
the Rx power is equal to this power the ATPC algorithm starts to operate.
c1) Manual Transmit Power Control (without Adaptive Modulation)
If the ATPC is disabled the Tx Power field is present.

In this field write the new value within the allowed transmitted power range. The range is shown on the
right side of Manual Transmit Power Control area.
c2) Tx Power (with Adaptive Modulation)
The operator can modify only the 4 QAM field. In this field the operator has to enter the constant power,
which will be used with 4 QAM modulation. The power range is shown on the right side and depends on
the selected reference mode.
Note
The same power value will be used by the 16 QAM and 64 QAM modulation schemes.
d) Tx Mute
The information related to the transmitter status is shown in the Tx Mute field (Off/Manual/Auto). To
squelch the transmitter select Enable and press Apply button.
The following indications will appear in the Tx Mute field:
– Off: Transmitter not squelch
– Manual: Transmitter squelched due to the manual operation
– Auto: Transmitter squelched due to an automatic operation
e) Alarm Profile
By clicking on the icon the Alarm Severity Profile menu opens, which allows to associate to the radio chan-
nel a specific alarm profile. Select one Alarm Profile in the Profile Name list (4 alarm profiles are listed)
and click Apply. Tick the Show details check box to see the severity associated to each alarm.
3.14.3.2 MPT-HC
3.14.3.2.1 General
To configure click in the Main view on the icon of the MPT-HC or of the MPT Access unit to be configured.
The Radio Main has 2 tab-panels:
– Power Source (par. 3.14.6)
– Port ##1 (par. 3.14.3.2.2 and 3.14.3.2.3)
– Port ##2 (this tab-panel is present if in the MPT Access unit a second port has been configured)
Warning: First configure the Port and then the Power Source.
Pay attention to configure properly the Power Source.

1) Mode
3) PPP RF
4) Alarm Profile
5) Synchronization
1) Mode
Figure 206. MPT Access unit without Adaptive Modulation settings (MPT-HC)
– Select in the Reference Channel Spacing field the suitable channel spacing to be used (up to
56 MHz).
– Select in the Modulation field the suitable Modulation scheme (up to 256 QAM).
– Select the Option ETSI mask: Current ETSI mask or New ETSI mask

The Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB/1+1 FD) Radio con-
figuration without ATPC.
Figure 207. MPT Access unit with Adaptive Modulation settings (MPT-HC)
– Select in the Modulation field the lowest modulation scheme (from 4 QAM) to be used by the Adap-
tive Modulation.
– Select in the Option field the spectral efficiency class to be set as reference: Current ETSI mask or
New ETSI mask.
– Choose in the Supported Modulation field all the modulation schemes to be used with the Adaptive
Modulation. The modulation schemes (from the lowest to the highest scheme) must be contiguous
and it must include the Reference Mode.

Note
The Remote Switching Threshold is not supported.
modulation will depend on the fading activity during the propagation. To update this field press the Refresh
button.
Note
Note. Example: if the current Modulation scheme is 4 QAM, it is not possible to force to 64 QAM, but first
must be forced to adjacent 16 QAM and then to 64 QAM. Also if the current Modulation is 64 QAM, to
pass to 4 QAM first must be forced to adjacent 16 QAM and then to 4 QAM.
Adaptive Modulation) in 1+1 configuration

protection scheme
the protection scheme (1+1 HSB)

Capacity Up-Grade
This applies when the lowest modulation scheme of the new channel spacing has a capacity
which is larger than the one with the old channel spacing. In this case all the pre-configured
TDM or ATM PW will be kept. The residual bandwidth for the lowest modulation scheme is
recomputed.
Capacity Down-Grade
which is smaller than the one with the old channel spacing. If all the pre-configured TDM or ATM
PW stays in the capacity associated to the lowest modulation scheme, they will be kept and the
residual bandwidth for the lowest modulation scheme is recomputed. If all the pre-configured
TDM or ATM PW cannot stay in the capacity associated to the lowest modulation scheme, the
change of channel spacing is rejected by WebEML/NMS.

Capacity Up-Grade
All the pre-configured TDM or ATM PW are kept.
Capacity Down-Grade
Since the admission control was performed with the capacity of the lowest modulation scheme,
all the pre-configured TDM or ATM PW will be kept.

Spacing.

When the Adaptive Modulation is enabled the behavior is: If all the pre-configured TDM or ATM
PW in the Old Static Modem Profile, stay in the capacity associated to the lowest Modulation
Scheme, the request of change is accepted and the residual bandwidth for the lowest Modu-
lation Scheme is computed. If all the pre-configured TDM or ATM PW cannot stay in the capac-
ity associated to the lowest Modulation Scheme, the request of change is rejected.

2) Link Identifier
Note
The "Link Identifier Mismatch" drops all the traffic.

3) PPP RF
4) Alarm Profile
5) Synchronization
a) Frequency
d) RSL Driving Criteria (only in 1+1 configuration without Adaptive Modulation)
e) Tx Mute
f) Alarm Profile
Warning: To configure the unit first configure the Shifter and the Tx Frequency in the Frequency field
(in the Channel area) and click on Apply. Then configure all the other parameters.
a) Frequency

In the Rx frequency field will appear the calculated Rx frequency, but this frequency can be changed in
+5 MHz range to implement the “Exotic” shifter configuration, if required. Change the Rx frequency and
press Apply.
frequency will appear. The Data Help table is usefull, if you are not connected to the ODU.
b) ATPC
Note
ATPC Range
ATPC Rx Threshold
c1) RTPC (Presetting Mode)
If the ATPC is disabled the Tx Power field is present. For the Tx Power range refer to the table.
c2) RTPC (Adaptive Modulation)
The operator can modify only the Tx power relevant to the lowest modulation scheme. In this field the oper-
ator has to enter the constant power, which will be used with the lowest modulation.
Note
The same power value will be used by the other modulation schemes.
d) RSL Driving Criteria
Select in the RSL Driving Criteria field the suitable value. In 1+1 HSB configuration both the transmitters
can be driven by the lowest or by the highest RSL values of the two remote demodulators.

e) Tx Mute
Note: In 1+1 HSB the command is applied to both transmitters.
f) Alarm Profile
3.14.3.3 MPT-MC
3.14.3.3.1 General
To configure click in the Main view on the icon of the MPT-MC or of the MPT Access unit to be configured.
The Radio Main has 2 tab-panels:
– Power Source (par. 3.14.6)
– Port ##1 (par. 3.14.3.2.2 and 3.14.3.2.3)
– Port ##2 (this tab-panel is present if in the MPT Access unit a second port has been configured)
Warning: First configure the Port and then the Power Source.
The MPT-MC cannot support 1+1 FD.
1) Mode
3) PPP RF
4) Alarm Profile
5) Synchronization

1) Mode
Figure 208. MPT Access unit without Adaptive Modulation settings (MPT-MC)
– Select in the Reference Channel Spacing field the suitable channel spacing to be used (up to
28 MHz).
– Select in the Modulation field the suitable Modulation scheme (up to 128 QAM).
– Select the Option ETSI mask: Current ETSI mask or New ETSI mask
The Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB) Radio configuration
without ATPC.

Figure 209. MPT Access unit with Adaptive Modulation settings (MPT-MC)
– Select in the Modulation field the lowest modulation scheme (from 4 QAM) to be used by the Adap-
tive Modulation.
– Select in the Option field the spectral efficiency class to be set as reference: Current ETSI mask or
New ETSI mask.
– Choose in the Supported Modulation field all the modulation schemes to be used with the Adaptive
Modulation. The modulation schemes (from the lowest to the highest scheme) must be contiguous
and it must include the Reference Mode.
Note
In 1+1 configuration the Driving MSE field is not supported.
Note
The Remote Switching Threshold is not supported.

modulation will depend on the fading activity during the propagation. To update this field press the Refresh
button.
Note
Note. Example: if the current Modulation scheme is 4 QAM, it not possible to force to 64 QAM, but first
must be forced to 16 QAM and then to 64 QAM. Also if the current Modulation is 64 QAM, to pass to 4
QAM first must be forced to 16 QAM and then to 4 QAM.
Adaptive Modulation) in 1+1 configuration
protection scheme
the protection scheme (1+1)

Capacity Up-Grade
which is larger than the one with the old channel spacing. In this case all the pre-configured
TDM or ATM PW will be kept. The residual bandwidth for the lowest modulation scheme is
recomputed.
Capacity Down-Grade
which is smaller than the one with the old channel spacing. If all the pre-configured TDM or ATM
PW stays in the capacity associated to the lowest modulation scheme, they will be kept and the
residual bandwidth for the lowest modulation scheme is recomputed. If all the pre-configured
TDM or ATM PW cannot stay in the capacity associated to the lowest modulation scheme, the
change of channel spacing is rejected by WebEML/NMS.

Capacity Up-Grade
All the pre-configured TDM or ATM PW are kept.
Capacity Down-Grade
Since the admission control was performed with the capacity of the lowest modulation scheme,
all the pre-configured TDM or ATM PW will be kept.

Spacing.

When the Adaptive Modulation is enabled the behavior is: If all the pre-configured TDM or ATM
PW in the Old Static Modem Profile, stay in the capacity associated to the lowest Modulation
Scheme, the request of change is accepted and the residual bandwidth for the lowest Modu-
lation Scheme is computed. If all the pre-configured TDM or ATM PW cannot stay in the capac-
ity associated to the lowest Modulation Scheme, the request of change is rejected.

2) Link Identifier
Note
The "Link Identifier Mismatch" drops all the traffic.

3) PPP RF
4) Alarm Profile
5) Synchronization
Note
The Channel #1 area is always present (in 1+0 and 1+1 configuration).
The Channel #0 area is present in 1+1 configuration only.
a) Frequency
d) RSL Driving Criteria (only in 1+1 configuration without Adaptive Modulation)
e) Tx Mute
f) Alarm Profile
Warning: To configure the unit first configure the Shifter and the Tx Frequency in the Frequency field
(in the Channel area) and click on Apply. Then configure all the other parameters.
a) Frequency

In the Rx frequency field will appear the calculated Rx frequency, but this frequency can be changed in
+5 MHz range to implement the “Exotic” shifter configuration, if required. Change the Rx frequency and
press Apply.
frequency will appear. The Data Help table is usefull if you are not connected to the ODU.
b) ATPC
Note
ATPC Range
ATPC Rx Threshold
c1) RTPC (Presetting Mode)
If the ATPC is disabled the Tx Power field is present. For the Tx Power range refer to the table.
c2) RTPC (Adaptive Modulation)
The operator can modify only the Tx power relevant to the lowest modulation scheme. In this field the oper-
ator has to enter the constant power, which will be used with the lowest modulation.
Note
The same power value will be used by the other modulation schemes.

d) RSL Driving Criteria
The RSL Driving Criteria field is not supported in the current release. In 1+1 HSB configuration without
the Adaptive Modulation each transmitter is driven by the RSL of the relevant remote demodulator.
e) Tx Mute
Note: In 1+1 HSB the command is applied to both transmitters.
f) Alarm Profile

3.14.4 Measurement
The Power Measurements capability is performed by means of the Measurement tabbed panel.
The Measurement screen allows the operator to set initial parameters for the required measurement.
"Measurement interval" fields allow the operator to set the time duration of the measurement. The default
is Days: 7, Hours: 0, Minutes: 0. A 7-day measurement interval is also the maximum allowed interval.
"Sample time" field is the period between two consecutive measurement samples. The choice is among
2, 4, 6, 30, 60 sec.
The last section of the dialog is referred to an optional Log file.
By selecting Create File the log file is created and a default path and name for this file is displayed to the
operator. The file is stored in the MPRE_CT_V00.07.08 directory.
Note
The file name must not include the following characters: \ ? : * “ < > |.
The log file contains the sample value and records the measurement up to a maximum dimension (7 days
for a 2 s sample time).
By clicking on the "Start" button the screen "Power Measurement Graphic" appears.
The Power Measurement Graphic is available only if the WebEML is connected to the NE.
The Power Measurement Graphic screen shows the Tx and Rx measurements related to the local and
remote NE.
Through this screen the operator can see, in real time, the power transmitted by the local and remote
transmitter (Tx) and the power received by the local and remote receiver (Rx).
The top graphic screen area shows the TX curves (local and remote), while the bottom area shows the
Rx curves (local and remote). Note that the colors represent the linked end-point of the two NE; for exam-
ple, if the local TX is blue, the remote receiver will also have the same color.
The top of the screen offers all the characteristics present in the current measurement:
– Radio port: gives the symbolic name associated to the radio channel being analyzed
– Sample time: indicates the frequency used to send the measurement requests to NE;
– Start time: is the first request time;
– Stop time: is the interval time selected in the previous parameters window, added to the start time;
– Time: is the current response time;
– Log File: is the complete pathname of the file where the received values are stored.
By clicking on "Show details" box, on the left side of the Power Measurement Graphic, a new table
appears; this table shows the following relevant values of the received and transmitted power:
– Tx Local End
max Tx local value and date when this value was received for the first time.
min. Tx local value and its current date when this value was received for the first time.
current Tx local value and its current date.

– Tx Far End
max Tx remote value and date when this value was received for the first time.
min. Tx remote value and its current date when this value was received for the first time.
current Tx remote value and its current date.
– Rx Local End
max Rx local value and date when this value was received for the first time.
min. Rx local value and its current date when this value was received for the first time.
current Rx local value and its current date.
– Rx Far End
max Rx remote value and date when this value was received for the first time.
min. Rx remote value and its current date when this value was received for the first time.
current Rx remote value and its current date.
Note
PTx and PRx levels software readings tolerance is:

– PTx = Real Value ± 3dB
– PRx = Real Value ± 5dB
WARNING:
Radio analog transmitted power level (local ODU)
In case of ICP or Cable Loss alarms the value shown at management system is -99.8 dBm. In case
of mute status the value shown at management system is -100 dBm. If the power level read is out
of the allowed range, the value shown by the management system is -101 dBm.
Radio analog received power level (local ODU)
In case of ICP or Cable Loss alarms the value shown at management system is -99.8 dBm. In case
of failure on reading the register containing the received power the value shown at management sys-
tem is -99.7 dBm. If the power level read is out of the allowed range, the value shown by the man-
agement system is -101 dBm.
Radio analog transmitted power level (remote ODU)
In case of broken radio link the value shown at management system shall be -99.6 dBm.
In case of mute status the value shown at management system shall be -100 dBm.
In case of failure on reading the register containing the remote transmitted power the value shown
at management system shall be -99.7 dBm.
If the power level read is out of the allowed range, the value shown by the management system shall
be -101 dBm.
Radio analog received power level (remote ODU)
In case of failure on reading the register containing the remote received power the value shown at
management system is -99.7 dBm. If the power level read is out of the allowed range, the value
shown by the management system is -101 dBm. In case of alarms on the remote NE on one of the
two radio channels in HSB configuration (typically ICP, Cable Loss, Card Missing, Card Fail), the
value shown by the management system is -127 dBm.

3.14.4.1 How to read a Power Measurement file
Click on Read File field and press on the Select File button. The directory of the WebEML automatically
opens to navigate and get the power measurement file.
Note
As default the measurement files are stored in the MPRE_ WebEML_V001.02.xx

directory and have extension .txt.
Select the desired file and click Open.
Click button Open on the right side of the Sample Time field.
The buttons in the lower part of the window allow to flow the graph within the measurement interval.
Note: The measurement file can be opened also with a standard text editor (e.g. WordPad). Go in the
directory where the txt files are stored and open the file. The measurements are shown in the tabular
mode.
3.14.5 Loopback
The functions described in this section allow to perform the test operations by loopbacks.
– Resource Tree Area: displays the object on which the loopbacks can be performed, sorted by num-
ber.
– Resource List Area: displays tabular information about the loopback supported by the resource
selected in the tree area.
– Resource Detail Area: displays, through tabbed windows, the properties done in list area. This area
enable to perform the available functions for the involved resource.
Note
The loopbacks can be activated on the local NE only.
In the Resource List Area are listed all the loopbacks which can be performed. In the current software
version the following loopbacks can be implemented:
– IF cable loopback with ODU300
– Core-facing and Radio-facing loopbacks with MPT-HC and MPT-MC
In this area the following information is given:
1) Interface: number of the channel and type of the loopback
2) Direction: type of the loopback
3) Activation: activation status of a loopback (Active/Not Active)
4) Activation Date: date of loopback activation

5) Timeout: timeout period, if has been set.
In Figure 210. and Figure 211. is given the association of the loopback and the position in the block dia-
gram of the equipment provided by the Summary Block Diagram View option, available in the Diag-
nosis menu.
Figure 210. Loopback with ODU300
Figure 211. Loopback with MPT-HC and MPT-MC

3.14.5.1 How to activate a loopback
[1] This operation must be done only with the Modem unit connected with ODU300. Before to activate
the loopback mute the Transmitter. Double click on the front panel of the Modem unit and enter the
Settings tab-panel.
[2] Select the loopback to be activated by clicking on the relevant object in the Resource Tree Area or
[3] Select Active in the Activation field.
[4] Click on Apply.
[5] The Loopback is now ACTIVE (in the row in the Resource List Area the Activation field of the loop-
back will change from Not Active to Active).
Note 1
The loopback are active only on the cross-connections with TDM2TDM and TDM2Eth profiles.
Note 2
In the Timeout Period field a timeout period can be set for the loopback activation (max. 4 days).
At the end of this period the loopback will be automatically deactivated.
3.14.5.2 How to remove a loopback
[1] Select the loopback to be removed by clicking on the relevant object in the Resource Tree Area or
[2] Select Not Active in the Activation field.
[3] Click on Apply.
[4] The Loopback is now DEACTIVATED (in the row in the Resource List Area the Activation field of the
relevant loopback will change from Active to Not Active).
[5] Remove the muting from the Transmitter.

3.14.6 Power Source
This menu is available only with MPT-HC and MPT-MC and it refers to the 2 different modes to power sup-
ply the MPT:
– QMA
– PFoE
Two Sources are available because the MPT Access unit can interface two MPT.
If the Type is Disabled no power supply is provided to the MPT.
After the power supply selection click on Apply.
N.B. The Alarm Profile field is not supported.
Figure 212. Power Source
3.14.6.1 Mode 1 - QMA (only with MPT-HC)
This mode is the default mode.
In this mode the MPT-HC is power supplied with a dedicated coaxial cable connected on the QMA con-
nector on the front panel of the MPT Access unit.

3.14.6.2 Mode 2 - PFoE (Power Feed on Ethernet)
In this mode the MPT-HC or MPT-MC are power supplied by using the electrical Ethernet cable.
Warning: Check the MPT Access card P/N before to provide power supply to the PFoE port.
To check the P/N use the Remote Inventory facility.
Warning
To implement this mode with MPT-HC the DC Extractor must be installed, near the MPT-HC,
to separate the Ethernet traffic and the power supply.
Warning
If you connect directly (without the DC Extractor) the MPT-HC with PFoE,
you can cause irreversible damages to the MPT-HC.

3.15 ATM view for ATM DOMAIN (this menu opens with double click on
an ASAP unit)
The configuration of the ASAP unit is divided in four tab-panels:
– E1 Layer (par. 3.15.1)
– IMA Layer (par. 3.15.2)
– ATM Layer (par. 3.15.3)
– ATM PW Layer (par. 3.15.4)
Warning: Migrations to MPR-E 2.1.

All the ATM PW flows configured on the NE but not yet cross-connected must be deleted
before performing the download of the MPR-E 2.1 SW Package. Otherwise, with the MPR-
E 2.1 SW Package, later configuration related to these ATM PW flows can lead to inco-
erent DataBase contents.
3.15.1 E1 Layer
Figure 213. ASAP E1 Layer view
This menu allows to configure the physical E1 layer.
To configure the E1 layer:
1. Select the E1 port# (from 1 to 16)

2. Select the Signal mode: Framed/Disabled
3. Select the Clock mode: node-timed/loop-timed.
4. Click on Apply.

N.B. By clicking on Apply To All the same configuration will be applied to the 16 E1 ports.
N.B. The line impedance can be 75 ohm or 120 ohm.
N.B. The Alarm Profile is not implemented in the current release.
3.15.2 IMA Layer
Figure 214. ASAP IMA Layer view
In the ASAP unit max. 8 IMA groups can be created.
To configure an IMA group:
1. Select the IMA group (from #01 to #08).
2. Enter the Near End ID (this identifier will be written in the ATM cells of the IMA protocol).
3. Enter the Min number of links (this is the minimum numbers of working E1 links, with which
the IMA group is still operational).
4. Enter the Max Differential Delay (in ms) between the E1 streams of the IMA group.
5. Click on Apply in the IMA Group Parameters are.
6. Select the E1 streams, which will be associated to the IMA group, by putting a check mark in
the Add check box. Up to 16 E1 links can be associated to the same IMA group.
N.B. When an E1 has to be removed from an IMA group it is necessary, before applying
the operation, to set the administrative status to down. In this case there is no affect
on the traffic.

7. Click on Apply in the IMA Link Table area.
N.B. By clicking on the Monitor in the Link column in the IMA Link Table area, the screen in
Figure 215 opens.
N.B. The Administrative Status must be set to Up in the ATM Layer tab-panel.
Figure 215. IMA Link Monitoring
This screen is a read-only screen in which all the parameters regarding the E1 link are shown.
N.B. By clicking on the IMA Group Monitoring the screen in Figure 216 opens.
Figure 216. IMA Group Monitoring
This screen is a read-only screen in which all the parameters regarding the IMA group are shown.

3.15.3 ATM Layer
3.15.3.1 ATM Layer Configuration
By clicking in the ATM # mode, as shown in Figure 217, the ATM Interface type can be selected: UNI
or NNI.
Figure 217. ATM Interface type
Each ATM interface (from #01 to #08) is an IMA group.
To activate an IMA group set the Admin Status to Up and click on Apply.

Figure 218. ASAP ATM Layer view
3.15.3.2 VP Layer Configuration
3.15.3.2.1 Create a VPI
To create a new VPI click on Create VPI. The next screen opens.
Figure 219. VP Layer Configuration
The definition of a VP over an ATM i/f is performed by the configuration the following parameters:
– VPI: in the range 0 to the value configured for the ATM i/f ;
– VP role: Not Logical (Connection end-point) or Logical (Termination end-point).

If the VP Role is configured as VP Connection end-point, then:
• ATM PW Service will be done in VPC mode, that is transport of ATM traffic into Ethernet frames
is done by encapsulating all ATM cells (i.e. for all VCs transported by that VP) with the config-
ured VPI into the same Ethernet flow;
• VP ATM Traffic Descriptor will be directly used to derive the traffic characteristic of the related
ATM PW Ethernet flow.
If the VP Role is configured as VP Termination end-point, then:
• ATM PW service will be done in VCC mode, that is transport of ATM traffic into Ethernet frames
is done by encapsulating into the same Ethernet flow only the ATM cells belonging to the same
VC (with the configured VPI);
• the VP configuration actually defines a "logical" ATM i/f, a specific VCI range can be configured
by NMS through SNMP interface for that VP (within the range previously configured for the ATM
i/f); by ECT instead, this parameter is not configurable (that is the default range for the ATM i/
f range applies);
• VP ATM Traffic Descriptor is not used to derive the traffic characteristic of the related ATM PW
Ethernet flow(s) but only to define the available bandwidth for "logical" ATM i/f (in ordet to per-
form ATM Admission Control at VC level);
• ATM Policing and Shaping are not applicable at VP level (but instead are to be configured at
VC level).
– Ingress and Egress Traffic Descriptors: For each VP it is possible to associate its ingress and
egress ATM Traffic Descriptors.
This applies in both cases of VP configured as Connection or Termination end-point. In the latter
case, the VP ATM Traffic Descriptor is used only to characterize the available bandwidth for ATM
Admission Control function. Click on Browse (the next screen opens for the Ingress Traffic Descrip-
tor) and select the TD in the Select TD field and click on OK.
The TD must be previously created in menu Configuration -> Traffic Descriptors.
Figure 220. Ingress Traffic Description
The configuration of a Traffic Descriptor associated to a “Logical” VP must be:

• Service Category = CBR
• PCR = sum of PCR of its CBR type VCs and MDCR of its UBR+ type VCs
• CDVT = don't care
• Policing = don't care

– Ingress Policing: this field allows to configure the policing in Ingress.
– Egress Shaping: this field is a read-only field. The shaping is automatically assigned according to
the Service Category.
3.15.3.2.2 Edit VPI
To modify a previously created VPI select the VPI from the Available VP list and click Edit VPI.
Change the parameters and click on Apply.
N.B. The VPI can be modified only if it is not involved in cross-connection. Otherwise the cross-con-
nection must be deleted, the PWE3 must be deleted and the VPI set to "Not in service".
3.15.3.2.3 Delete VPI
To delete a previously created VPI select the VPI from the Available VP list and click Delete VPI.
N.B. The VPI can be deleted only if it is not involved in cross-connection. Otherwise the cross-con-
nection must be deleted, the PWE3 must be deleted and the VPI set to "Not in service".
N.B. If the VP contains the VC, the VC must be removed.
N.B. VP ATM Admission Control
For every created VP an ATM Admission Control is performed in order to check that the resulting allocated
bandwidth is less or equal to the bandwidth available on the ATM i/f.
This applies in both cases of VP that is being configured as Connection or Termination end-point.
In case the resulting allocated bandwidth is greater than the ATM i/f available bandwidth, the VP definition
cannot be performed and an error indication is returned.
The allocated bandwidth is computed as the sum of the egress VP ATM Traffic Descriptor parameters,
according to the type of Traffic Contract (ATM Service Category/Conformance Definition pair) reported in
the below table:
Service Category Conformance Definition VP/VC Bandwidth
Cbr CBR.1 PCR
ubr+ CBR.1 MDCR (> 0)
ubr CBR.1 MDCR (= 0)
In case of VP that is being configured as Termination end-point, the egress VP ATM Traffic Descriptor
parameter defined in the above table is also defining the available bandwidth for the related "logical" ATM
i/f.

3.15.3.3 VC Layer Configuration
The VC Layer Management is used to define the characteristics of the VCs transported over an already
configured VP.
The VC Layer Configuration and relevant buttons are available only if a VPI has been configured Logical
as VP Role.
3.15.3.3.1 Create VCI
To create a VCI select the relevant VP in the Available VP list and click on Create VCI. The next screen
opens.
Figure 221. VC Layer Configuration
The definition of a VC (over an already configured VP) is performed by the configuration the following
parameters:
– VCI: in the range from 32 to the value configured for the underlaying logical (VP) ATM interface
– Ingress and Traffic Descriptor. For each VC it is possible to associate its ingress and egress ATM
Traffic Descriptors.
Click on Browse (the next screen opens for the Ingress Traffic Descriptor) and select the TD in the
Select TD field and click on OK.
The TD must be previously created in menu Configuration -> Traffic Descriptors.
– Ingress Policing: this field allows to configure the policing in Ingress.
– Egress Shaping: this field is a read-only field. The shaping is automatically assigned according to
the Service Category.
3.15.3.3.2 Edit VCI
To modify a previously created VCI select the VCI from the Available VC list and click Edit VCI.
Change the parameters and click on Apply.
N.B. The VCI can be modified only if it is not involved in cross-connection. Otherwise the cross-con-
nection must be deleted, the PWE3 must be deleted and the VCI set to "Not in service".

3.15.3.3.3 Delete VCI
To delete a previously created VCI select the VCI from the Available VC list and click Delete VCI.
N.B. The VCI can be deleted only if it is not involved in cross-connection. Otherwise the cross-con-
nection must be deleted, the PWE3 must be deleted and the VCI set to "Not in service".
N.B. VC ATM Admission Control
For every created VC an ATM Admission Control is performed in order to check that the resulting allocated
bandwidth is less or equal to the bandwidth available on the underlying VP, that is the "logical" ATM i/f.
In case the resulting allocated bandwidth is greater than the "logical" ATM i/f available bandwidth, the VC
definition cannot be performed and an error indication is returned.
The allocated bandwidth is computed as the sum of the egress VC ATM Traffic Descriptor parameters,
according to the type of Traffic Contract (ATM Service Category/Conformance Definition pair).

3.15.4 ATM PW Layer
Figure 222. ASAP ATM PW Layer view
3.15.4.1 ATM PW Parameters
To configure an ATM PW Layer select the Interface (from #01 to #08), enter the following parametrs and
click on Apply.
(Click on Create to configure another ATM PW. To delete an ATM PW select the ATM PW and click on
Delete).
– PW Label: it is possible to configure for each ATM PW, only one value, to be assigned to both
Inbound (Packet -> ATM direction) and Outbound (ATM -> Packet direction) PW Labels. The value
must be in the range: 16-65535.
Since de-multiplexing of ATM PW flows towards ATM interface is based on ATM PW Inbound Label
value, a check on all Inbound values, configured on the same NE, must be done in order to avoid
duplications.
The remaining fields of the 32-bit PW Label to be inserted into ATM PW frames will be assigned as
below reported:
• 3-bit EXP field is assigned according to the ATM PW flow CoS
• 1-bit S field is set to 1 (Bottom of Stack)
• 8-bit TTL is set to 255
– VPC/VCC Mode: it is possible to configure to have ATM PW Service in:

• VPC mode, i.e the multiplexing of one (N=1) or more (N>1) VPs to the same ATM PW Ethernet
flow;
• VCC mode, i.e the multiplexing of one (N=1) or more (N>1) VCs, belonging to the same VP,
to the same PWE3 ATM flow, will be supported.

N.B. If in VPC mode, the VPI only can be changed. If in VCC mode, the VPI only, the VCI only
or both can be changed.
In order to perform an ATM PW Service in VPC mode, the related VP must had be previously con-
figured at ATM Layer as Connection end-point.
In order to perform an ATM PW Service in VCC mode, it must had been previously configured at ATM
Layer the related VP, as Termination end-point, and VC.
– Max Cell Concatenation and Max Delay (timeout): for each ATM PW flow it is possible to configure
how ATM cells will be concatenated into the same Ethernet packet:
1. a timeout, after the reception of first ATM cell, expires;
2. a maximum number of concatenated ATM cells is reached
The above configuration parameters allow, for each ATM PW, to find the trade-off between latency
and ATM PW encapsulation overhead.
The timeout is configurable in the range 0.1 to 40 ms, with 0.1 ms steps. Default value is 1 ms.
The maximum number of concatenated cells is is configurable by ECT/NMS in the range 1 to 28 cells,
with 1 cell step . Default value is 1 cell.
N.B. Limitation for Cell Concatenation
In this release the following limitations apply:

• only timeout values from 1 to 10 ms, with 1 ms step, are configurable and tested;
• only maximum cell concatenation number 1, 2, 4, 5, 10, 28 cells are configurable.
– Admin Status: this field is a read-only field. The status is automatically set to "up", when a cross-
connection is established and set to "down", when a cross-connection is deleted.
3.15.4.2 VPI/VCI Translation
For each ATM PW flow, it is possible to change the VPI/VCI value of transported cells to a different value
from that used in the ATM VP/VC configuration.
– Ingress VPI/VCI Translation (ATM -> Ethernet direction): VPI/VCI value can be changed to a con-
figurable value in the ATM Cell(s) encapsulated into ATM PW Ethernet frames:
• if the ATM PW is configured in VPC mode, only VPI can be changed, with range from 0 to 255
or 4095 according to UNI or NNI configuration of related ATM interface;
• if the ATM PW is configured in VCC mode, then VPI, VCI or both can be changed, with range
from 0 to 65535
No check shall be performed on the new VPI/VCI values against the VPI/VCI range foreseen for ATM
i/f (VPC mode) or terminating VP (VCC mode).
– Egress VPI/VCI Translation (Ethernet -> ATM direction): whatever is the VPI/VCI value within
ATM cell(s) transported by ATM PW frame, it is changed into the ATM Cells sent towards ATM inter-
face to the configured value of related VP (in case of VPC mode) or VC (VCC mode).

3.16 Core-E VIEW for Core-E and ETHERNET DOMAIN (this menu opens
with double click on a Core-E unit)
3.16.1 Core-E domain

This chapter describes the functions types offered to the operator in order to navigate the Core-E board.
Core-E domain multiple main view contains two tab-panels:
– Ethernet Physical Interface
– TMN Interface
– Resource Tree, displaying Ethernet physical interface with related port number;
– Resource List, displaying tabular information about tributaries in tree area;
– Resource Detail, providing access to Core-E detail view “Alarms” and “Settings”.
3.16.1.1 Ethernet Physical Interface
Figure 223. Core-E Main view

If the optional SFP optical plug-in has been enabled in the Core-E unit in port #5 and/or in port #6 (refer
to Equipment menu) also the relevant Ethernet Port # will appear (see Figure 224.).
Figure 224. Core-E Main view (with optical SFP Ethernet port#5)
This tab-panel refers to the Ethernet ports, which can be used as traffic ports and includes two tab-panels
each Ethernet port:
– Alarms tab-panel
Alarms tab-panel
“Alarm” view shows the Ethernet ports-related alarms. Selecting the node in Tree area allows checking
Ethernet tributary alarms current state.

Settings tab-panel (for Ethernet Port#1 to Port#4)
The Settings view performs all the available functions for Ethernet tributary ports. Information related to
a data port configuration is provided by the following parameters:
– Port Status (Enabled or Disabled);
Warning:Before enabling an Ethernet port, when the “Static LAG Criteria” and the “Ethernet
Interface Criteria for 1+1 EPS Core” features have been enabled in Menu Configuration
> System Settings, it is recommended first to disable the “Ethernet Interface Criteria for
1+1 EPS Core” feature. This feature could be enabled again after that this additional port
has been properly configured. No traffic impact is foreseen with this operation.
– Auto-Negotiation Status (Enabled or Disabled);
– Flow Control (Enabled or Disabled);
N.B. Only asymmetric pause capability can be configured to transmit pause frame but not
receive pause frame on the Ethernet ports. If a pause frame is received on Ethernet ports
such frame is dropped. Default values for manual mode are 100 Mbit/s, full duplex, pause
disable.
– Configuration (“Other” / “Configuring” / “Complete” / “Disabled” / “Parallel Detect Fail”) all read-only;
– Advertised Capability, (“10 Mb/s – Half Duplex”, “10 Mb/s – Full Duplex”, “100 Mb/s – Half Duplex”,
“100 Mb/s – Full Duplex”). The “Restart” button allows forcing auto-negotiation to begin link re-nego-
tiation;
– VLAN configuration. The traffic, received on each user Ethernet port, can be untagged or tagged.
For each port it is possible to configure:
• Acceptable Frame Type:

– Admit tagged only (only tagged frames are allowed in ingress; the untagged frames are
dropped)
– Admit all (tagged and untagged frames are allowed in ingress)
Default value: “Admit all”.

• Port VLAN ID: if the Acceptable Frame Type is set to “Admit all” the VLAN-ID and Priority fields
(to be added in ingress to untagged frames) must be configured. Only VLAN-ID values already
defined (in the VLAN management menu) can be configured for this purpose. The Priority val-
ues allowed are in the range 0 - 7.
The default Port VLAN-ID and Priority values are: VLAN-ID=1; Priority=0.
The VLAN 1 is always removed when the frame is forwarded.
N.B. Untagged frames

The untagged frames received on one user Ethernet port, configured as “Admit tagged
only”, are dropped.
N.B. Priority frames

• The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as
“Admit tagged only”, are dropped.
• The priority packets (VLAN-ID=0) received on one user Ethernet port, with the "Admit
all" configuration enabled, are managed as untagged frames for VLAN-ID field, while
the Priority field is the same of the received packets".
– Alarm Profile (not implemented);
– Synchronous Ethernet Operation Mode
From the Ethernet traffic interfaces (configured as 1000 Mb/s) it is possible to recover the physical
Rx synchronization signal or to deliver the Network Element Clock synchronization signal (in this
case the Ethernet port must be set as Sync-E Master). This feature is needed in order to realize "syn-
chronous Ethernet Networks" addressed by G.8261.
Enable the Synch-E mode by setting Synchronous and selecting the operating mode: Master or
Slave.
Note: If the electrical Ethernet port has to be used as Synchronous Source, the Ethernet port must
be set as Synch-E Slave.
Settings tab-panel (for Ethernet Port #5 and Port #6)
The Settings view performs all the available functions for Ethernet tributary port #5 and port #6. Infor-
mation related to the port configuration is provided by the following parameters:
– Port Status (Enabled or Disabled);

Warning:Before enabling the Ethernet port, when the “Static LAG Criteria” and the “Ethernet
Interface Criteria for 1+1 EPS Core” features have been enabled in Menu Configuration
> System Settings, it is recommended first to disable the “Ethernet Interface Criteria for
1+1 EPS Core” feature. This feature could be enabled again after that this additional port
has been properly configured. No traffic impact is foreseen with this operation.
– Auto-Negotiation Status (Enabled or Disabled);
– Flow Control (Enabled or Disabled);
N.B. Only asymmetric pause capability can be configured to transmit pause frame but not
receive pause frame on the Ethernet ports. If a pause frame is received on Ethernet ports
such frame is dropped. Default values for manual mode are 100 Mbit/s, full duplex, pause
disable.
– Configuration (“Other” / “Configuring” / “Complete” / “Disabled” / “Parallel Detect Fail”) all read-only;
– Advertised Capability, (“1000 Mb/s – Full Duplex”). The “Restart” button allows forcing auto-nego-
tiation to begin link re-negotiation.
– Optical Info field: it is a read-only field not implemented in the current release.
dropped)
(to be added in ingress to untagged frames) must be configured. Only VLAN-ID values already
The VLAN 1 is always removed when the frame is forwarded.
N.B. Untagged frames

N.B. Priority frames

• The priority packets (VLAN-ID=0) received on one user Ethernet port, with the "Admit
all" configuration enabled, are managed as untagged frames for VLAN-ID field, while
the Priority field is the same of the received packets".
– Alarm Profile (not implemented);
– Synchronous Ethernet Operation Mode
From the optical Ethernet traffic interface it is possible to recover the physical Rx synchronization
signal or to deliver the Network Element Clock synchronization signal (in this case the Ethernet port
must be set as Sync-E Master). This feature is needed in order to realize "synchronous Ethernet Net-
works" addressed by G.8261.
Enable the Synch-E mode by setting Synchronous.

3.16.1.2 TMN Interface
With the introduction of TMN In-Band two new IP interfaces are added to those already available.
– NE Local IP Address
– TMN Local Ethernet interface, IP/subnet
– TMN Out-of-Band interface on User Ethernet port 4, IP/subnet
– TMN In-Band interface #1, IP/subnet
– TMN In-Band interface #2, IP/subnet
User Ethernet port 4 can then used as:
– pure Ethernet traffic interface

– pure Out-of-band TMN Local Ethernet interface
– Ethernet traffic interface carrying TMN In-Band traffic
The NE Local IP Address can be reused on one of the other TMN interfaces. These interfaces must have
different IP subnets.

This tab-panel refers to the TMN Interface. The interfaces are of two types:
1) TMN Ethernet on a dedicated connector
2) Port #4 of the Ethernet traffic ports, which can be dedicated to TMN purpose and not to traffic.
This tab-panel has 2 tab-panels:
– Alarm tab-panel
3.16.1.2.1 Alarms tab-panel
“Alarm” view shows the Ethernet ports-related alarms. Selecting the node in Tree area allows checking
Ethernet tributary alarms current state.
3.16.1.2.2 Settings tab-panel for TMN In-band
The TMN In-Band feature allows the extension of the DCN over User Ethernet interfaces used to carry
user traffic.
Two default TMN In-Band interfaces (TMN In-band #1 and #2) are supported, each having its own IP
address and subnet.
The TMN traffic delivered In-Band is VLAN tagged and identified by a specific VLAN ID defined by the
operator in the range 2-4080.
The delivery of TMN In-Band can be enabled on all User Ethernet interface of the Core board, both Optical
and Electrical.
Note 1: the Ethernet ports involved in a LAG cannot be used as TMN In-band interface.
Note 2: If the TMN In-band interface has been configured and the traffic classifier is according to
802.1p, the priority on the TMN traffic is highest. If the traffic classifier is according to DiffServ,
the priority on the TMN traffic is low and the traffic on the other Ethernet ports must be taken
in consideration.
Note 3: If two Ethernet ports, associated to the same TMN In-band logical interface, are segregated,
the two ports do not communicate each other, as for the normal Ethernet traffic (they have the
same VLAN ID). If two Ethernet ports, configured in different TMN In-band logical interfaces,
are segregated, the two ports can communicate each other, as they have 2 different VLAN IDs).

The OSPF and related Area ID can be enabled on a TMN In-Band interface.
For each TMN In-Band interface the following parameters must be selected:
– IP address and subnet: default 10.0.3.2/24 for interface #1 and 10.0.4.2/24 for interface #2
– VLAN ID: default 4097 for interface #1 and for interface #2
– List of User Ethernet interfaces where transmit/receive TMN In-Band traffic: default None (multiple
selection or deselection can be done by holding the Ctrl key while clicking on one or more entries)
– OSPF enable/disable: default disabled for both interfaces
– Area ID in case of OSPF protocol enabled: default 0.0.0.0
3.16.1.2.3 Settings tab-panel for TMN Ethernet port
If used, the TMN Ethernet must be:
– Enabled.
– Assigned an IP address with its IP mask.
– Selected the IP Routing Protocol: Static Routing or OSPF. If OSPF has been selected, assign also
the area number
– Click on the Alarm Profile icon to open the Alarm Severity Profile menu to associate to the TMN
Ethernet port a specific alarm profile. Select one Alarm Profile in the Profile Name list (4 alarm pro-
files are listed). Tick the Show details check box to see the severity associated to each alarm.
Click on Apply to activate the selections.

3.16.1.2.4 Settings tab-panel for TMN Ethernet Port #4
If the Ethernet Port 4 has been used as TMN port, the port 4 must be:
– Enabled.
– Assigned an IP address with its IP mask.
– Selected the IP Routing Protocol: Static Routing or OSPF. If OSPF has been selected, assign also
the area number.
Click on Apply to activate the selections.
3.16.1.3 Ethernet LAG
If in the Configuration > Ethernet Features Shell menu have been created the Ethernet LAGs (Link
Aggregation Group), the created Ethernet LAGs will appear in the Ethernet Physical Interface tab-panel
as shown in the figure. In the figure two LAGs have been created (Port #1 and Port #15).

Each Ethernet LAG has its Setting tab-panel.
In this tab-panel only the VLAN configuration field can be modified (all the other fields are read-only).

dropped)
(to be added in ingress to untagged frames), must be configured. Only VLAN-ID values already
VLAN 1 is always removed when the frame is forwarded.
N.B.: Untagged frames

N.B.: Priority frames

• The priority packets (VLAN-ID=0) received on one user Ethernet port, with the “Admit
all” configuration enabled, are managed as untagged frames for VLAN-ID field, while
the Priority field is the same of the received packets.

3.16.1.4 MPT-HC connected to the Core-E
When the Ethernet port #5 or/and port #6 are sent and used to connect an MPT-HC, a new toolbar button
is available inside the Core-E view; this button allows to access the MPT-HC menu.
In the example an MPT-HC (tab-panel Port #1.5) has been connected to Port #5.
The Ethernet Port #5 is not available as an Ethernet Physical Interface: it is removed from the Tributaries
Data list.

3.17 AUX view for AUX DOMAIN (this menu opens with double click on
the AUX peripheral unit)
The AUX peripheral unit has two tab-panels:
• Settings
• External points
3.17.1 Settings
To enable the 64 kbit/s user Service channel #1 or #2 set the Channel Status to Enabled and click Apply.
Note: the Protocol Type is fixed to Synchronous 64 kbit/s RS422/V.11 DCE co-directional.
N.B. The EOW Interface is not implemented in the current release.
Figure 225. Settings tab-panel

3.17.2 External Points
There are two types of external points: input and output external points.
By clicking on the tree root, displayed in Figure 226, the tree will be expanded.
A single left click selection of a tree element causes the activation of the corresponding Tabular repre-
sentation displayed in the "Resource list area" (upper right side of the screen).
A click on a row in the Resource list area opens the Settings menu.
3.17.2.1 Input External Points
An input external point is described by the following parameters (Figure below):
• Id: identification number
• UserLabel: associates a user-friendly name to an external point
• Polarity: describes the polarity (Active Low/ Active High)
• External State: describes the state (on /off)
• Alarm Profile: describes the associated Alarm Profile (not implemented)
After a row selection, the user can modify the User Label, the Polarity.
The operator choices will be sent to NE after selecting the "Apply" button.
Figure 226. Input External Point View

3.17.2.2 Output External Points
Seven output external points are available.
The output external points (CPO#1 ... 7) are described by the following parameters:
• Id: identification number
• UserLabel: a user friendly name can be associated to an external point
• Polarity: describes the polarity (Active Low/ Active High). In this field the polarity of the external
point can be changed.
• Criteria: fixed to Manual. (The output can be activated manually). Note: the Automatic mode
is not supported in this release.
• External State: describes the state (on /off). In this field the external point can be activated (on)
or deactivated (off).
The operator choices will be sent to NE by clicking on the "Apply" button.
Figure 227. Output External Points View

3.18 WT Performance Monitoring Suite
To open the WT Performance Monitoring Suite click on the relevant icon in the Menu bar as shown in the
next figure.
WT Performance Monitoring
Suite icon
The WT Performance Monitoring Suite provides PM measurements for Ethernet, Radio, E1, IMA and ATM
user lines.
3.18.1 How to start the WT Performance Monitoring Suite

The WT Performance Monitoring Suite can be invoked from WebEML by clicking the WT Performance
Monitoring Suite icon button in the Main Tool Bar. This operation opens the WT Performance Monitoring
Suite view described in the following.
3.18.2 Tool bar

The Tool bar (shown in Figure 228) provides an interface to collect the performance data from NE network
elements and provides the basic functionalities to collect the performance related statistics and other
types of measurements.
Figure 228. WT Performance Monitoring Suite palette
The buttons shown in the above figure, have the following functionalities:
– “Close” command removes a NE from NE list.
– “Move to front” command moves a selected NE performance monitoring view to the front.
– “Move to back” command moves a selected NE performance monitoring view to back.
– “Sort” command orders each NE performance monitoring view.
– “Background” command set the background colour of NE performance monitoring view.

– “Start/Stop” command starts or stops the counters for the data collection, when the CD (Current
Data) has been stopped or started.
– “Refresh” command retrieves the current PM reports form NE and update the table view and chart
view with the recently collected data.
– “Reset” button resets the data collection and related counters.
– “Archive” button archives current PM reports.
– “Export” button saves the report to be exported.
– “Print” button prints the user selected performance point.
– “Offline Mode” button saves the current status of the WT Performance Monitoring Suite to have later
the possibility to see the PM offline (refer to par. 3.18.6.3 on page 439).
– “List View” button shows all PM points' table view and chart view in one screen.
– “Overview” button shows a selected PM point's chart view in one screen.
– “Bird’s Eye View” button shows a selected PM point's table view and chart view in one screen.
– “Note” button shows the meaning of each parameter.
– “Help” button show help content.
3.18.3 Menu bar

The following menus are available:
– File: Export (par. 3.18.3.1 on page 434)

Print (par. 3.18.3.2 on page 435)
Exit
– Network: List View

Overview
Bird’s Eye View
– Action: Close
– Windows: it shows the IP address of the NEs
– Help: it shows some information on the Help
In the Menu bar are available the same menus present in the Tool bar. Refer to the Tool bar for details
(par. 3.18.2 on page 432).

3.18.3.1 Export
This menu allows to export in specific CSV files all the active performance tables.
By selecting this menu the following screen opens.
Figure 229. Export: Save
Select the directory (or create a new folder) and click on Open.
The tables are saved individually in a specific file with IP address of the NE, slot number of the unit and
type of the counter as shown in the following figure.
Figure 230. Exported files

3.18.3.2 Print
This menu allows to print all the tables.
Figure 231. Print
3.18.4 Menu available on the Bird’s Eye View

By right clicking with the mouse on the graphic the following menu will appear:
– Copy: to storage the image
– Save as: to save the image as .png or .jpeg
– Print: to print the image
– Zoom In: to enlarge the image
– Zoom Out: to shrink the image
– AutoRange: to fit the image

3.18.5 PM selectable options
Several tab-panels can be present:
– NEs List: it includes all the NEs, which launched the application
– Specific tab-panel (identified by the NE IP address) for each NE, which launched the application.
By clicking an NE in the NEs List or in the specific NE tab-panel, the available PM will appear.
The following types of Performance Monitoring are available:
1) Ethernet Statistics (par. 3.18.7)
2) Radio PM (par. 3.18.8)
3) PDH PM (par. 3.18.9)
4) IMA Layer Statistics (par. 3.18.10)
5) ATM Interface Statistics (par. 3.18.11)
B
A
1
2
3
4
5
Figure 232. Types of PM
In the left area a small rounded icon is associated to each object, taking the color and the letter of the object
alarm condition (C = Critical, M = Major, m = minor, W = Warning).

3.18.6 How to start and stop the PM
3.18.6.1 Start the PM
1) Select the type of PM. In the example shown in Figure 233, Ethernet Statistics has been
selected.
2) Select the slot. The slot selection corresponds to the selection of the unit. In the example which
follows Ethernet Statistics has been selected. The selection of the unit will cause the display
of the counters of all its subordinate objects, i.e. in this example the counters of all equipped
ports will be displayed.
3) Optionally, after the selection of the unit, you can select one of its subordinate objects. In this
case, only the selected object is highlighted in the frame area.
Figure 233. Selection tree and start button
N.B. The PM can be started individually or at slot level.
4) Start the counters by pressing button Stopped. Button Stopped (red-colored) changes
appearance and becomes green.
The start time is displayed in the Configuration area (left-lower part of the window). In the configu-
ration dialog box, you can select the collecting interval and Duration. Available collecting intervals
are 5s,10s,30s and 60s. The Duration is from 1 hour to 24 hours.

Figure 234. Example of PM counters display
3.18.6.2 Stop the PM
To stop PM application select the counter and click Stop button. Start and Stop buttons are shown below.
Figure 235. How start and stop the PM
N.B. The PM can be stopped individually or at slot level.

3.18.6.3 Offline Mode
By clicking the Offline button on the Tool-bar the current status of the WT Performance Monitoring Suite
is saved, as shown in Figure 236.
– Write the archive name and click OK.
Figure 236. Offline: archive name
– Click on Yes to save the current NE status.
Figure 237. Saving the current NE status
– The current status is saving.
Figure 238. Offline: current status saving
– Close NEtO. Click on the Offline Mode icon on the Desktop.
– The screen in Figure 239 opens. Select the file and click on OK.
Figure 239. Offline Mode: select the NE
Now the WT Performance Monitoring Suite previously saved open and you can navigate in all the
menus.

3.18.7 Ethernet Statistics
This option provides Ethernet PM statistical counters.
1) In the left area select bar Ethernet Statistics. The selected bar is moved to the upper part of
the left tree area.
You can expand the tree view of slots 1-8.
The slot equipped by CORE-ENH unit allows to select the enabled user ports 1-6.
The Ethernet Statistics are available in the Core-ENH unit, in MPTACC unit and in MD300 unit. The
MPTACC unit is the interface to MPT-HC/MPT-MC; the MD300 unit is the interface to ODU300.
3.18.7.1 CORE-ENH unit Ethernet Statistics
N.B. Ethernet Counters can be displayed in three different modalities:
– List View
– Overview
– Bird’s Eye View
In the example, the List View is shown. To display the other views select in the Menu bar the
view or click the view on the relevant icon in the Tool bar. Refer to par. 3.18.7.1.4 on page 444.
1) From the left-hand side tree execute the suitable selection of the CORE-ENH unit, to get the display
of the counters of all ports.
2) From the Configuration subwindow (lower left side of the window), select the Interval (the
collection time of the performances): 4, 6, 30, 60 seconds. The default value is 4 sec. From the same
subwindow select the Duration of the performance monitor in hour and minutes. The max. duration
is 24 hours.
3) Click on the Start button to start the monitoring.
4) The right-hand area contains the statistic data for the Ports.
Per each port the following tabs are selectable:
– Ethernet Aggregate Tx
– Ethernet Aggregate Rx
– Custom view

3.18.7.1.1 Ethernet Aggregate Tx
Figure 240. Ethernet Aggregate Tx
The available performances at port level are (see Port 1 selected in the above figure):
– TTO: total number of octets of Ethernet frames transmitted out by the Interface, including Ethernet
header characters.
– TTF: total number of Ethernet frames transmitted out by the interface.
– TDF: total number of Transmitted Ethernet frames which were chosen to be discarded due to buffer
congestion.
– TTF Unicast: total number of Ethernet Unicast frames transmitted out by the Virtual Ethernet
Interface.
– TTF Multicast: total number of good packets transmitted by this address that were directed to a
multicast address. This number does not include packets directed to the broadcast address.
– TTF Broadcast: total number of good packets transmitted by this address that were directed to the
broadcast address.

3.18.7.1.2 Ethernet Aggregate Rx
Figure 241. Port 1 Aggregate Rx
The available performances at port level (see Port 1 selected in the above figure):
– TRO: total number of octects of Ethernet frames received by the Virtual Ethernet Interface, including
Ethernet header characters.
– TRF: total number of Ethernet frames received by the Virtual Ethernet Interface.
– TRSEF: total number of errored frames.
– TDF: total number of Ethernet frames which were chosen to be discarded due to buffer congestion.
– TRF Unicast: total number of Ethernet Unicast frames received correctly by the Virtual Ethernet
Interface.
– TRF Multicast: total number of good packets received that were directed to a multicast address.
This number does not include packets directed to the broadcast address.
– TRF Broadcast: total number of good packets received that were directed to the broadcast address.
This number does not include multicast packets.

3.18.7.1.3 Port Custom view
You can customize the view by clicking on tab Custom View. The customized View Builder box is pre-
sented.
Figure 242. Customized View Builder
The view is divided into two areas:
– left area which contains the list of the selectable counters
– right area which contains the list of the selected counters
The user can select a counter on the left area and by clicking the upper arrow move it to the right area
in order to customize the counter view.
The opposite operation can be done by selecting the counter in the right area and by clicking the lower
arrow to move it to the left area.
Click on OK button to confirm.

3.18.7.1.4 Example of the other views
Figure 243. Overview
Navigation
bar
Figure 244. Bird’s Eye View
Note: Click on the Navigation bar to change the view.
Note: In the bottom 2 tab-panels show the counters:

– Deafult Counters: collected on the NE row
– Elaborated Counters: processed on the PC and are available only when the PC is con-
nected to the NE.

3.18.7.2 MPTACC unit and MD300 Ethernet Statistics
In the figure is shown the screen regarding the MPTACC unit. The screen for the MD300 is the same.
N.B. Ethernet Counters can be displayed in three different modalities:

– List View
– Overview
In the example, the List View is shown. To display the other views select in the Menu bar the
view or click the view on the relevant icon in the Tool bar. Refer to par. 3.18.7.2.4 on page 449.
Figure 245. MPT ACC unit statistics
The figure which follows shows examples of selection of a MPTACC unit:
• MPTACC in slot #3 refers to a 1+1 configuration.

• MPTACC in slot #4 refers to a 1+0 configuration.
• MPTACC in slot #5 refers to a non 1+1 configuration

1+1 CONFIGURATION (Direction#3.1/#3.2)
MPT
MPT
1 2
SLOT #3
MPTACC
1+0 CONFIGURATION (Direction#4.1)
MPT
1 2
SLOT #4
MPTACC
NON 1+1 CONFIGURATION (Direction#5.1 and Direction#5.2)
MPT
MPT
SLOT #5 1 2
MPTACC
Figure 246. Configurations of the MPTACC
N.B. Two types of MPT are available:
– MPT-HC (High Capacity), up to 256QAM
– MPT-HC (Medium Capacity), up to 128QAM
Per each Direction the following tabs are selectable:
– Queue #1 to Queue #5
– Ethernet Aggregate Tx
– Custom view
N.B. The MPTACC unit has 8 output queues:
• Queue 8 is reserved to TDM2TDM traffic.
• Queue 7 is reserved to TDM2Eth traffic.
• Queue 6 is reserved to TMN traffic.
• The remaining 5 queues are reserved to Ethernet traffic. Queue 5 is the highest priority queue.

3.18.7.2.1 Queue #1 to Queue #5
Figure 247. Ethernet Aggregate Per Queue (Queue #01)
Select the tab of the queue to display. The available performances at queue level (for each queue) are:
header characters.
congestion.
3.18.7.2.2 Ethernet Aggregate Tx
The available performances at aggregate level are:
header characters.
congestion.

3.18.7.2.3 Customized view builder (Aggr.Tx and Queues)
sented.
Figure 248. Aggr.Tx and Queues Custom view

3.18.7.2.4 Example of the other views
Figure 249. Overview (Modem unit)
Navigation
bar
Figure 250. Bird’s Eye View - MPT Access unit (Default Counters)

Navigation
bar
Figure 251. Bird’s Eye View (Elaborated Counters)

– Default Counters: collected on the NE row
nected to the NE.

3.18.8 RADIO PMs
3.18.8.1 General information on the radio performance monitoring process
The performance monitoring (PM) gives indication on the quality of the service.
Quality of service PM is performed in accordance with G.826 and G.784.
It is assumed that the quality of the single tributary (E1, …) can be derived from the quality of the aggregate
signal, therefore no dedicated quality of service PM is foreseen on the single tributaries.
Considering one section (see below figure), one current register is for 15 min report and one for 24 h
report; 96 history data can be stored for 15 min report and 8 history data for 24 h report.
N.B. N.B. The 15 min Performance Monitoring data are stored in the History Data report only if errors
have been occurred.
The 24 h Performance Monitoring data are always stored in the History Data report.
Two different radio sections can be monitored:
– Radio Hop Section: the section between two radio stations inside the protection section
– Radio Link Section: the section identifying the protected section.
Figure 252. Radio sections
The counters supported are the following:
– Errored Seconds
– Severely Errored Seconds (N.B.)
– Background Block Error
– Unavailable Seconds
N.B. According to ITU-T G.826 a second is declared Severely Errored Second if it is a second period
with more than 30 % of errored blocks or at least one defect.
The performance reports can be of 2 different types:
– 15 minutes
– 24 hours
The following description explains the functions to provide the PM process with a granularity period of
24 h. The same functions are provided for 24h PM process.
The PM are of HOP or LINK type:
– HOP refers to the PM before the RPS switch.

– LINK refers to Performance Monitoring after the RPS switch. The current report can be seen (and
configured) and the history log can be seen.

3.18.8.2 RADIO PMs performance monitoring procedures
RADIO Performance Monitoring provides quality data regarding the radio channels.
To the RADIO measurements thresholds can be associated. See procedure which follows.
Only the quality of the aggregate signal is provided.
1) In the left area select bar RADIO PM. The selected bar is moved to the upper part of the left tree
area.
2) Select the slot housing the MD300 or the MPTACC unit.
3) Select the Direction, in this example Direction #3.1/3.2 (MPT-HC).
4) Select the granularity tab-panel (15 min/24h). In the example which follows 15 min granularity
has been selected.
N.B. Radio Counters can be displayed in three different modalities:
– List View
– Overview
In the following example, the List View is shown. To display the other views select in the Menu bar the
view or click the view on the relevant icon in the Tool bar.
Figure 253. Radio PMs

The following tabs are selectable:
– Hop Ch 0 (Stand-by channel)

– Hop Ch 1 (Working channel)
– Link (RPS switch included)
In the example which follows Hop Ch 1 has been selected.
Figure 254. Radio PMs: Hop Ch 1 counters
The view contains the following collection data parameters:
– Time. It displayes the time of the Performance Monitoring. This time changes after the Auto Refresh.
– Elapsed Time. It displays the elapsed time in the current interval of monitoring.
– Suppressed Intervals. It displays the number of intervals (reports) suppressed in the History
because they don’t have errors.
– Suspect. It contains a flag symbol in case of suspect of data inconsistency.
N.B. An interval is defined as “suspect” if at least one of the following conditions occurs in the col-
lection period:
- the elapsed time deviates more than 10 seconds of the nominal time
- loss of the Performance Monitoring data in the equipment
- performance counters have been reset during the interval.
The displayed counters are:
– BBE (Background block Errors)

– ES (Errored Seconds )
– SES (Severily Errored Seconds )
– UAS (Unavailable Seconds )

3.18.8.3 Radio Custom view
sented.
Figure 255. Radio: Customized View Builder
3.18.8.4 Manage Thresholds
This paragraph describes how to display or change or create the thresholds assigned to Performance
Monitoring counters.
There are threshold tables for the HOP and for the LINK.
There are two default thresholds for HOP: Threshold #1 (to be associated to 15 min report) and Thresh-
old #4 (to be associated to 24 h report).
There are two default thresholds for LINK: Threshold #1 (to be associated to 15 min report) and Thresh-
old #3 (to be associated to 24 h report).
The user can manage thresholds to be associated to Hop or Link 15min report or 24h report. The following
actions are available, starting from button Manage Thresholds in the Configuration area:
• Thesholds display
• Create threshold
• Delete threshold
• Associate a threshold to a monitoring point

3.18.8.5 How to display a threshold
Click on button Manage Thresholds. The Manage Thresholds subwindow is displayed. See below figure
Figure 256. Manage Thresholds: display
3.18.8.6 How to create a new threshold
Four threshold tables can be created for the HOP (Threshold #2, #3, #5 and #6).
Two threshold tables can be created for the LINK (Threshold #2 and #4).
Two standard thresholds are available for the HOP (Threshold #1, #4).
Two standard thresholds are available for the LINK (Threshold #1 and #3).
To create a new threshold:
[1] Click on Manage Thresholds button. The Manage Threshold subwindow opens.
[2] Select HOP or LINK.

Figure 257. Manage Threshold: create
[3] Select the Measurement type: 15 min or 24 h.
[4] Enter the values for the Low and High thresholds.
[5] Click on Create. Automatically the new threshold takes a name with a progressive number. See
below the figure.
Figure 258. Manage Thresholds: threshold 2 creation

3.18.8.7 How to delete a threshold
Only the created thresholds can be deleted. The default thresholds can be only displayed.
[1] Select the Threshold to be deleted and click on Delete button.
3.18.8.8 How to associate a threshold
You can assign the desired theshold to a certain Monitoring Point.
Execute the following steps:
1) From the left-hand side lower Configuration area select the Monitor Point.
2) Select the Collection Period (15 min or 24h )
3) Select the Threshold. The list of the available thresholds for the previously selected Monitoring
Point is presented by clicking on the down arrow beside the field name (threshold in this case).
4) Notice that only the thresholds applicable to the selected Monitoring Point are presented.
5) The Threshold to be selected is identified by a number, in accordance to the detailed list con-
tained in the upper area of the Manage Thresholds dialog box.
6) Click on Apply button to confirm the assignment.

3.18.9 PDH Performance Monitoring
The PDH “Performance Monitoring” are available in the P32E1DS1 unit.
3.18.9.1 P32E1DS1 unit performances
Selecting the P32E1DS1 unit, the Performance Monitoring (PM) gives indication on the quality of the E1
Tributaries, which have been configured as "Framed".
E1 Tributaries, configured as "Framed" are shown in bold; for all the other E1 Tributaries (in grey) the per-
formance are not available, because the relevant streams are disabled or they have been configured as
"Unframed".
Two types of performances are available:
– Incoming: performances detected at the input in Tx side.
– Outgoing: performances detected at the output in Rx side.
Note: 9500MPR is transparent regarding the E1 stream. The CRC is used to detect the quality of the E1
stream.
The Quality is performed in accordance with G.826 and G.784.
The performance reports are of 2 different types:
– 15 minutes
– 24 hours
Note: For a better quality in the Performance Monitoring it is recommended to start up to 128 E1 PM
counters on the same NE. This means 4 counters (Incoming 15 Minutes, Incoming 24 hours, Outgoing
15 Minutes and Outgoing 24 Hours) for 32 E1 streams.
Note: Stability measurement on Ethernet counters (with duration from few hours to 24 Hours) should be
performed by selecting an high value (60 seconds) as collection time of the performances (refer to param-
eter Interval in the Configuration subwindow).
The following description explains the functions to provide the Performance Monitoring process with a
granularity period of 15 min. The same functions are provided for 24h Performance Monitoring process.
• Incoming
• Outgoing
• Customer View
N.B. The Counters can be displayed in three different modalities:
– List View
– Overview
In the following example, only the List View is shown. To display the other views select in the Menu bar
the view or click the view on the relevant icon in the Tool bar. Refer to par. 3.18.9.6 on page 463.

3.18.9.2 Incoming
Figure 259. P32E1DS1 Incoming (15 Min)
3.18.9.2.1 Displayed parameters
The displayed parameters are:
– Time. It displays the time of the Performance Monitoring. This time changes after the Auto Refresh
– Elapsed Time. It displays the elapsed time in the current interval of Performance Monitoring.
– Suppressed Intervals: number of intervals (reports) which are automatically suppressed, because
they don’t have errors.
– Suspect: shows whether the data are suspect or not (Note).
Note: An interval is defined as “Suspect” if at least one of the following conditions occurs in the collection
period:
– the elapsed time deviates more than 10 seconds of the nominal time
– loss of the Performance Monitoring data in the equipment
– performance counters have been reset during the interval.
– BBE (Background Block Errors)
– ES (Errored Second)

– SES (Severely Errored Second)
– UAS (Unavailable Second).
Note: These values refer to the last refresh performed with the Refresh button in the Tool bar.
3.18.9.3 Outgoing
3.18.9.3.1 Displayed parameters
The displayed parameters are:
– Time. It displays the time of the Performance Monitoring. This time changes after the Auto Refresh
– Elapsed Time. It displays the elapsed time in the current interval of Performance Monitoring.
– Suppressed Intervals: number of intervals (reports) which are automatically suppressed, because
they don’t have errors.
– Suspect: shows whether the data are suspect or not (Note).
Note: An interval is defined as “Suspect” if at least one of the following conditions occurs in the collection
period:
– the elapsed time deviates more than 10 seconds of the nominal time
– loss of the Performance Monitoring data in the equipment
– performance counters have been reset during the interval.
– BBE (Background Block Errors)
– ES (Errored Second)
– SES (Severely Errored Second)
– UAS (Unavailable Second).
Note: These values refer to the last refresh performed with the Refresh button in the Tool bar.

3.18.9.4 Customized view builder
sented.
3.18.9.5 Manage Thresholds
This paragraph describes how to display or create the threshold assigned to Performance Monitoring
counters.
There are two default threshold:
– Threshold #1 (to be associated to 15 min report)
– Threshold #4 (to be associated to 24 h report).
Figure 260. Manage Thresholds

3.18.9.5.1 How to create a new threshold table
Note: Four threshold tables can be created (Threshold #2, #3 for 15 min report and #5 and #6 for 24 h
report).
To create a new threshold table:
[1] Click on the Manage Threshold. The E1 Threshold screen will appear.
[2] Select the Measurement type: 15 min or 24 h.
[3] Enter the values for the Low and High thresholds.
[4] Click on Create. Automatically the new threshold takes a name with a progressive number.
3.18.9.5.2 How to delete a threshold
Note: Only the created thresholds can be deleted. The default thresholds can be only displayed.
[1] Click on the Threshold to be deleted in the upper area of Manage Thresholds window.
[2] Click on Delete button to delete the threshold.
3.18.9.5.3 How to associate a threshold
To associate a Threshold to E1 tributary:
1) From the left-hand side lower Configuration area select the Monitor Point (Incoming/Outgo-
ing).
2) Select the Collection Period (15 min or 24h )
3) Select the Threshold. The list of the available thresholds for the previously selected Monitoring
Point is presented by clicking on the down arrow beside the field name (threshold in this case).
Notice that only the thresholds applicable to the selected Monitoring Point are presented.
The Threshold to be selected is identified by a number, in accordance to the detailed list con-
tained in the upper area of the Manage Thresholds dialog box.
4) Click on Apply button to confirm the assignment.

3.18.9.6 Example of the other views
Figure 261. Overview
Navigation
bar
Figure 262. Bird’s Eye View

– Deafult Counters: collected on the NE row
nected to the NE.

3.18.10 IMA Layer Statistics
The IMA Layer Statistics are available with the A16E1DS1 unit.
3.18.10.1 IMA Group Monitoring
The quality of IMA Group and Links is evaluated by monitoring IMA Group and Link Counters. This mon-
itoring is based on IMA standard.
– List View
– Overview
the view or click the view on the relevant icon in the Tool bar.
For each configured and active IMA Group the following counters are available:
– Unavail Secs: counter of the seconds where the IMA group traffic state machine is down.
– NeNumFailures: counter of the number of times a failure alarm condition (Config-Aborted,Insuffi-

cient-Links, Config-Aborted-FE, Insufficient-Links-FE, Blocked-FE) has been reported for Near-End
IMA Group.
Figure 263. IMA Group and IMA Link statistics

For each active IMA link, belonging to an activated IMA Group, the following counters are available:
– IMA Violation: counter of errored, invalid or missing ICP cells, except during SES-IMA or UAS-IMA
conditions;
– OIF (Out of IMA Frame) anomalies: counter of OIF anomalies, except during SES-IMA or UAS-IMA
conditions;
– NeSES (Severly Errored Seconds): counter of one second intervals containing more then 30% of
the ICP cells counted as “IMA Violation”, or one or more link defects (e.g., LOS,OOF/LOF, AIS, or
LCD), LIF defects, or LODS defects, except during UAS-IMA condition, for Near-End side;
– NeUAS (UnAvailable Seconds): counter of the seconds unavailability beginning at the onset of 10
contiguous SES-IMA and ends at the onset of 10 contiguous seconds with no SES-IMA, for Near-
End side;
– Ne Tx UUS (UnUsable Seconds): counter of unusable seconds declared by the Link State Machine
at TX and RX directions for Near-End side;
– Ne Tx failure: counter of the number of times a failure alarm condition has been entered on this link
at Tx direction for Near-End side;
– Ne Rx failure: counter of the number of times a failure alarm condition has been entered on this link
at Rx direction for Near-End side.
sented.
Figure 264. Custom View

3.18.11 ATM Interface Statistics
The quality of ATM PW Service is evaluated by monitoring the ATM interface and VP/VC cell counters.
• Interface #
• Not Logical VPs
• Logical VPs
• Custom View
– List View
– Overview
the view or click the view on the relevant icon in the Tool bar.
3.18.11.1 Interface
Select the Interface as shown in figure below (Interface #1 has been selected).
Figure 265. ATM Interface Statistics

For each configured and active ATM interface the following counters are available:
– Usage Rx: counter of the number of cells received on the ATM interface.
– Usage Tx: counter of the number of cells transmitted on the ATM interface.
– Inv Header Discarded Cells: counter of the number of cells discarded because of Invalid Header,
invalid VPI or invalid VCI.
3.18.11.1.1 Not Logical VPs and Logical VPs
In the screen will appear all the configured VP/VC.
In the figure the screen refer to VP #144/VC #35.
Figure 266. Logical VPs Statistics Monitoring
For each active VP, if configured as Termination end-point, and active VC configured over an active ATM
interface, the following counters are available:
– Discarded Cells: counter of the total number of valid VP/VC cells discarded by the traffic policing
entity. This includes cells originally received with CLP=0 and CLP=1.
– Discarded CLP0 Cells: counter of the total number of valid VP/VC cells received with CLP=0 and
discarded by the traffic policing entity.
– Tagged Cells: counter of the total number of valid VP/VC cells tagged by the traffic policing entity
from CLP=0 to CLP=1 and transmitted.

– Usage Rx: counter of the total number of valid VP/VC cells received including both CLP=0 and
CLP=1 cells. The cells are counted prior to the application of the traffic policing.
– Usage Tx: counter of the total number of valid VP/VC cells transmitted including both CLP=0 and
CLP=1 cells. The cells are counted prior to the application of the traffic policing.
– Usage Rx CLP0: counter of the number of valid VP/VC cells received with CLP=0. The cells are
counted prior to the application of the traffic policing.
– Usage Tx CLP0: counter of the number of valid VP/VC cells transmitted with CLP=0. The cells are
counted prior to the application of the traffic policing.
sented.

3.19 VLAN management
Two different ways to manage the Ethernet traffic are allowed:
– 802.1D (MAC Address Bridge)
– 802.1Q (Virtual Bridge)
3.19.1 802.1D
When the NE is configured in this mode (default configuration), the Ethernet traffic is switched according
to the destination MAC address without looking the VLAN.
The packets from the user Ethernet ports having the VLAN ID out the allowed range (0 and 2-4080) are
dropped. The packets having a VLAN ID already used for a TDM flow are accepted.
Figure 267. 802.1D VLAN management

3.19.2 802.1Q
When the NE is configured in this mode, the management of Ethernet traffic looking the VLAN is enabled.
In this modality, one VLAN will be assigned to all Ethernet frames inside the MPR network.
WARNING: The VLAN ID values configurable must be in the range 2 - 4080. The VLAN IDs already
defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) cannot be used. The management
system prohibits the definition of VLAN ID already used. The VLAN ID must be different also from the Flow
Id associated to E1 tributaries not yet cross connected
Figure 268. 802.1Q VLAN management (default VLAN only)
VLAN 1 Management
VLAN-ID 1 is automatically defined by the NE when the 802.1Q bridge type is selected.
VLAN-ID 1 is shown to the operator, but it cannot be neither changed nor deleted.
All the user Ethernet ports (enabled and disabled) and all the radio ports are members of the VLAN 1.
In egress VLAN-ID 1 is always removed from all the ports.
Buttons
– New: to create a new VLAN (refer to VLAN table management)
– Edit: to change the parameters of a VLAN (VLAN name, VLAN member ports, VLAN untagged ports
in egress).

– Delete: to delete a VLAN-ID. It is possible to remove a VLAN-ID from the VLAN-ID table even if this
VLAN-ID has been already configured on one or more user ports as Port VLAN to be added in ingress
to untagged frames. As consequence, the VLAN-ID=1 and PRI=0 are added to the untagged frames
received on this port. Before applying this deletion, a confirmation of the operation is shown to the
operator.
– Export: to export the VLAN configuration in a file with extension CSV. The file can be stored in the
PC to be read later.
– Filter: by inserting a name in the "Filter by Name" box and by clicking on Filter will be displayed in
the table only the VLAN, which name corresponds (totally or partially) to the name written in the "Filter
by Name" box.
– Clear Filter: by clicking this button all the VLAN created in VLAN table will again appear.
– Refresh: the VLAN table is updated.
3.19.2.1 VLAN Table Management
1
2
3 4
Figure 269. VLAN Table Management
[1] VLAN ID field: Enter the VLAN ID (the values configurable must be in the range 2 - 4080)
N.B. The VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM,
TDM2ETH) cannot be used.
[2] VLAN Name field: Enter the VLAN Name: a text string of up to 32 characters.
N.B. There is no check on unambiguity name.
[3] VLAN Ports field: Select the ports members of this VLAN by putting a check mark on the relevant
check box. All the user Ethernet ports and all the Radio directions can be considered. Both enabled
and disabled user Ethernet ports (radio ports when declared are implicitly enabled) can be member
of a VLAN. This means that a disabled port can be configured as a member of a VLAN and a port
already member of a VLAN can be disabled continuing to be a member of the same VLAN.

[4] Untagged Ports field: Select, among the ports belonging to this VLAN (members), the untagged
ports (in egress the VLAN will be removed from the frames). Only the user Ethernet ports, enabled
and disabled, are manageable. The VLAN cannot be removed from the radio ports (with the excep-
tion of the VLAN 1).
N.B. The VLAN-ID values allowed are in the range 2 - 4080. By default, for the VLAN IDs defined,
all the ports are members and the Untag flag is set to “False”, which means all the frames are
transmitted with Tag.
N.B. Tagged frames

If one tagged packet with VLAN-ID X is received on a port which is not member of the VLAN-
ID X, the packet is dropped.
In Figure 270 three VLANs have been created (VLAN 2, 3 and 4).
Figure 270. 802.1Q VLAN management
In Figure 271 the LAGs (previously created) are also shown: Ethernet LAG #1 and Radio LAG #23.

Figure 271. 802.1Q VLAN management (with LAGs)
N.B. When an ODU300/MPT-HC or MPT-MC port which is member of a VLAN, is unconfigured, the
operation is denied stating that "Operation not permitted: the board <board no> is member of
a static VLAN". To unconfigure this board, the user must first navigate to VLAN Configuration
window and remove this port from the static VLAN.

3.20 Annex A: Network Element Overview
The Network Element Overview (NEtO) is the starting point of the WebEML application.
NEtO functions require to know the NE identity by means the related IP Address.
Only one NE can be managed in a NEtO session.
The User Interface is provided by the NEtO Main View described below.
3.20.1 Main view

When NEtO starts, the main view screen is shown in Figure 272.
Menu Bar
Figure 272. NEtO main view: initial screen
This screen has three specific areas:
– NE Configuration area: displays NE general information (left side);
– Status & Alarms area: reports supervision status and alarms (right side);
– Discovered NEs: in the lower part is shown the list of the discovered NEs. With a double click on
a row the IP address of the NE in the row automatically is written in the NE Info field
"Show" and "Alarm Monitor" buttons are enabled when a NE is supervised only. Supervision starts as
soon as the operator writes an IP address in the specific field and press the "OK" button.
NEtO Main view can also be reduced by using the shrink glass ( ) button in the Menu Bar.
Figure 273 shows the reduced NEtO view, allowing the operator to save screen space while continuously
checking supervision and alarms status. Gray icons mean that supervision is not active. The magnifying
glass ( ) button allows to show the normal NEtO main view (see Figure 272).
The alarm severity icon (shown in Figure 272 and Figure 273) appears in operating system "tray bar",
close to system clock and other system software icons.

Figure 273. NEtO main view: reduced screen
This icon also has a specific tooltip, visible when mouse cursor is moved over it, that will show: name of
application, NE IP address, and highest severity alarms number. The tray-bar icon is present in the Win-
dows system bar (in the lower part of the screen). The tray-bar icon takes the color of the most severe
alarm. The tray-bar icon is not interactive and does not present any menu or executable command if
clicked either with left or right mouse button.
3.20.2 NE Configuration area

The panel is divided in three sections:
[1] NE Info section, containing information related to NE addressing;
[2] NE Description section, with information about NE characteristics;
[3] Command Buttons section, providing buttons to manage NEtO functions.
3.20.2.1 NE Information
This area is related to wanted NE identification (Figure 274).
Figure 274. NEtO NE Configuration View: NE Information
"IP Address or DNS name" field: insert the NE IP address or DNS name, if the network can provide this
facility.
"OK" button will start supervision on specified NE, if reachable. Keyboard shortcut "Alt + o" behaves as
clicking on "OK" button with mouse.
Whether the IP address is correctly written, other than clicking on "OK" button, supervision process will
start on specified NE by pressing "enter" (carriage return) key on keyboard.

3.20.2.2 NE Description
This area contains some parameters displaying general information about the supervised NE
(Figure 275).
Figure 275. NEtO NE Configuration View: NE Description
Parameters can be read and modified (and applied to NE using the "Apply" button).
Please note that changing these labels values will also automatically update NEtO window title content:
window title will always contain "Site Name" of supervised NE. Keyboard shortcut "Alt + a" behaves the
same as clicking on "Apply" button with mouse.
3.20.2.3 Command Buttons
Figure 276 shows command buttons available through NEtO.
Figure 276. NEtO NE Configuration View: Command Buttons
"Show" button will start WebEML (JUSM/ WebEML) application on a supervised NE.
"Alarm Monitor" button starts AM application. For the Alarm Monitor application refer to par. 3.5.1.
Buttons "Show" and "Alarm Monitor" will be enabled when NE is supervised only.
"Exit" button will close NEtO, stopping a possibly running supervision and closing all related applications.
Keyboard shortcut "Alt + S" behaves as clicking on "Show" button with mouse. Keyboard shortcut "Alt +
m" behaves as clicking on "Alarm Monitor" button with mouse. Key-board shortcut "Alt + E" behaves as
clicking on "Exit" button with mouse.

3.20.3 Status & Alarms area
Information on supervision status and active alarms are shown in this area (Figure 277).
Figure 277. Main View: Status & Alarms
Round-shaped icons change their colours according to current NEtO functions and situation. With respect
to "Supervision" status:
– green colour means that supervision function is ongoing,
– red colour means that NE link does not work,
– gray icons mean that supervision is not active (to be started).
Alarm synthesis contains the list of the alarms listed by severity: whether an icon is not grey, means that
such kind of severity contains one alarm at least. "Alarm Monitor" button shown in Figure 276 opens the
Alarm Monitor application external tool.
The round-shaped icons change the colour and the letter inside according to the severity of the active
alarms:
– red (letter C): Critical alarm
– orange (letter M): Major alarm
– yellow (letter m): Minor alarm
– blue (letter W): Warning alarm

3.20.4 Supervision Function
The supervision function allows operator registering a new manager inside NE MIB and performing cyclic
(periodic) monitoring on connection.
To start supervision, the operator must specify NE IP address in the "IP Address" field and then simply
press "OK" button.
If supervision succeeds, screen is updated with information retrieved from NE and supervision icon
changes its colour from gray to green stating NE is correctly supervised.
When a supervision error, a link down or other problems arise during supervision, icon will become red.
Alarm Synthesis area will be updated as well. Clicking on "Show" button, NEtO will open the WebEML
(JUSM/ WebEML) for MPR equipment.
To close an ongoing supervision, simply click on "Exit" button (this will also close NEtO) or change NE
IP address and click "OK" button to start supervision procedure on a different NE (this will stop previous
supervision).
3.20.5 Menu bar
– (New)
– (Open)
NEtO can manage and organize a list of favorite NEs by showing operator a table containing such data.
Using both (New) and (Open) icons, the operator will be able to open NEs table modal window
(see Figure 278).
"Open" icon allows opening a previously saved file containing a list of NEs.
"New" icon allows creating a new list, specifying the file name containing its data, only when those data
will be saved. Window allows the operator managing its NEs data by:
– "Get Current" button is used to read information from main NEtO view. This operation will always
add a new line in NE list table with all information related to currently supervised NE. This happens
even though a NE with corresponding IP address is still present in the list;
– "New" button, adding a new NE from scratch. This allows the operator to fill the "IP Address" field
only with its needed NE.
– "Remove" button, removing a selected NE;
– "Set Current" button, filling main NEtO view IP address with datum from selected NE. The operator
must previously select a valid line in NEs table and then click on "Set Current" button so filling NEtO
main window data. This operation will automatically close the NE list window but does not start super-
vision on set NE;
– "Save" button, saving table list in a specified file.
All data are saved in a custom XML format called "NEtO" and this structured file will contain all data shown
in Figure 272 related to all NEs added to the list.

Figure 278. NEtO List Management
The operator can have its own NEs lists repository, containing all .NEtO files that it produced with NEs
information inside. To close this window click on "Close" button. The operator can see the data related
to NEs as shown in Figure 278. As for NEtO main window, even NE list window allows using keyboard
and hotkeys to perform operations. Through:
– Keyboard shortcut "Alt + g" behaves as clicking on "Get Current" button with mouse;
– Keyboard shortcut "Alt + s" behaves as clicking on "Set Current" button with mouse;
– Keyboard shortcut "Alt + n" behaves as clicking on "New" button with mouse;
– Keyboard shortcut "Alt + r" behaves as clicking on "Remove" button with mouse;
– Keyboard shortcut "Alt + v" behaves as clicking on "Save" button with mouse;
– Keyboard shortcut "Alt + c" behaves as clicking on "Close" button with mouse.
(Magnifying glass)
NEtO Main view can also be reduced by using the shrink glass ( ) button.
Suggested usage sequence for NEtO interface and NE list
1) Fill NEtO main view "IP Address" field with NE IP address;
2) Start supervision by clicking "Ok" button;
3) Open the NEs table (any method, through "New" or "Open" button);
4) Click on "Get Current";
5) "Save" the list and "Close" the list window.
This operation will produce a clean and up-to-date NEs table list. The NE table lists are not updated, if
the operator will modify, NE site name site location or even IP address. Such data are used for references
purposes, but the operator must take care to keep them updated.

4 Installation
4.1 Hardware Installation

– 4.1.1 - Power consumption on page 482
– 4.1.2 - Rack Installation on page 483
– 4.1.3 - ODU300 Installation on page 497
– 4.1.4 - MPT-HC Installation on page 518
– 4.1.5 - MPT-HC V2 Installation on page 579
– 4.1.6 - MPT-MC Installation: on page 592
– 4.1.7 - DC Extractor: on page 628
– 4.1.8 - Nose Adapter for MPT-HC/V2 and MPT-MC: on page 629
– 4.1.9 - Flextwists for MPT-HC/V2 and MPT-MC: on page 629
– 4.1.10 - Indoor Installation on page 630
– 4.1.11 - Antenna Alignment on page 680

Installation 3DB 18793 AAAA Issue 1 481/876
4.1.1 Power consumption
Part Max. Power Consumption Typical Power Consumption
Core-E 20 W 16 W
MODEM CARD 23 W 21 W
32 E1 PDH ACCESS CARD 10 W 9W
STM-1 ACCESS CARD 13 W 20 W
16 E1 ASAP CARD 22 W 21 W
AUX PERIPHERAL CARD 10 W 9W
MPT ACCESS CARD 17 W 13.5 W
FAN-MSS8 8W 8W
FAN-MSS4 5W 5W
ODU300 45 W for ODUs < 15 GHz

30 W for ODUs > 15 GHz
MPT-HC 40 W 38 W
MPT-HC V2 39 W 37 W
MPT-HC V2 (with RPS module) 40 W 38 W
MPT-HC V2 (with XPIC-RPS module) 47 W 45 W
MPT-MC 40 W 38 W
Note
Figures are for normal (not start-up) operation.

482/876 3DB 18793 AAAA Issue 1 Installation
4.1.2 Rack Installation
4.1.2.1 General
Indoor units (IDU) of the 9500 MPR-E system can be installed in 3 different ways:
– "ETSI (WTD) rack (21") (see par. 4.1.2.2 on page 483)
– Standard rack (19") (par. 4.1.2.3 on page 488)
– The equipment can also be installed on the wall (par. 4.1.2.5 on page 491)
For each of the above type of installation special mechanical supporting fixtures are available.
Special mechanical fittings are provided for this type of installation, depending on the width of rack (19"
or 21"). The examples show the fittings used to insert the equipment in ETSI racks (21"). For installation
in 21" racks the adaptors are needed.
4.1.2.2 ETSI Rack Installation
4.1.2.2.1 Mechanical Installation
Installation has been sub-divided into the following phases:
– Rack Positioning and Fastening
– Fixing the rack to floor using expansion bolts or Fixing to floating floor;
– T.R.U. fastening to ETSI rack.
4.1.2.2.2 Rack Positioning and fastening
Proceed as follows:
– Refer to the plant documentation to see rack row assignment
– Fasten the rack to the station structure according to one of the following procedures
– Fixing the rack to floor
– Fixing the rack to floating floor
4.1.2.2.3 Fixing the rack to floor using expansion bolts
(Refer to Figure 279. and Figure 280.).
– Mount the rack in a vertical position in the desired place.
– Mark the base-plate with six holes (1) to be drilled on the floor.
– Temporarily remove the rack and drill the holes at the points drawn on the floor. Place the inserts into
the holes.
– Secure the expander bolts to the floor through the base-plate holes.

Figure 279. Fixing the Rack to Floor (1)

Figure 280. Fixing the Rack to Floor (2)

4.1.2.2.4 Fixing to floating floor
(Refer to Figure 281. and Figure 282.).
The drilling mask is the same used for concrete floor fastening.
In this case a hole must be created for the cables coming from the bottom according to Figure 281.
The rack fastening is to be mounted on the concrete floor below using a suitable stud as shown in Figure
281.
Using the row layout drawing, mark out the cable entry areas in the floor tiles and cut out with a jigsaw.
Remember that the beginning of the row must be approved by the customer.
N.B. Unused or incompletely used cable entry areas should be blocked off with foam rubber.
Figure 281. Floor file drilling template

Figure 282. Example of securing rack assembly to computer floor

4.1.2.3 Laborack (19") installation
Figure 283. Laborack
The Laborack must be fixed to the floor by means of the four (4) screws.
(For more information see the manufacturer instructions).
When you have correctly positioned the fixing brackets on the 19" unit, the front panel will hold the
equipment by four screws fitted into the laborack cage nuts.
Fasten the IDU to the rack by inserting screws into holes of 19" mechanical adaptors and by screwing them
into relevant holes provided with nut cage situated on rack brackets.

4.1.2.4 Subrack Installation
Figure 284. MSS-8 Subrack
Figure 285. MSS-4 Subrack

Figure 286. Fix the subrack with screws
Figure 287. Subrack grounding point (bracket on the right side)
The subrack must be grounded using the ground screw present on the front panel of the bracket on the
right side.
The section cable (wire) to use must be a 6 mm² (9AWG) (Yellow/Green).
The subrack-mounting item adds a good electrical connection to rack ground.

4.1.2.5 Wall Mounting Installation
The IDU wall mounting kit (3CC50027AAAA) can be used for wall installation and it can support a
maximum of three units.
The kit includes:
– Two brackets
– Four fixing for the brackets
• M6x50 socket cap screws
• Onduflex washers
• Expansion bolt
The mechanical support is 10 U high.
Figure 288. Mechanical Support (Two brackets)
Figure 289. Installation kit to fix the mechanical support

Figure 290. MSS 8 Fixed on wall mounting
The mechanical support must be grounded using the Grounding Kit 3CC13423AAAA.
4.1.2.6 Top Rack Unit
The Top Rack Unit (T.R.U.) fastening to the rack guarantees the connection to the protection ground in
that the rack is wired to the station protection ground.
Figure 291. Top Rack Unit (T.R.U.)
The T.R.U. is positioned on the top of the Rack and it is used to provide the Power Supply to the equipment.
Figure 292. Top Rack Unit - Front/Rear
The T.R.U. is fixed to the rack by means of two (2) screws.
Figure 293. Top Rack Unit - Fixed to rack

4.1.2.6.1 Top Rack Unit Components
Description Component Q.ty Particular View
Terminal Block 16mm² 2
Thermal Magnetic Circuit Breaker Unipolar 6
Bus Bar Supply to 12 Fuse Carrier 1
Screws M6x16 with plastic Washer 4
Natched Clamp Nuts M6 4
Rail + Front 19" 1

4.1.2.6.2 Top Rack Unit Connections
The photos below show the connections from IDU to T.R.U.
Figure 294. TRU Connections
4.1.2.6.3 Top Rack Unit Grounding
The rack must be grounded by means of a connection to the protection ground terminal of the site
electrical plant.
The rack must be connected to the protection ground before performing any other electrical connection.
Figure 295. TRU Grounding position on Laborack
The rack is grounded to the station through a 16 to 25 mm2 (1 to 2 AWG) section cable (1) terminated
onto the cable terminal lug (2).

Figure 296. ETSI Rack - Ground connection
Figure 297. Laborack - Ground connection
4.1.2.6.4 Power Supply Cable
Two solutions of the Power Supply cable can be provided as shown in Figure 298.
N.B. Preassembled cord with moulded connector or metallic connector and raw cable to be assem-
bled on site.
Figure 298. 2W2C Connector and Cable (3DB18271AAXX)
N.B. Two cables for MSS-8 (as shown in Figure 298.), one cable for MSS-4.

Figure 299. Battery Access Card on subrack
A power cable is supplied in the IDU Installation Kit, which has a 2-pin 2W2C fitted at one end and wire
at the other. The cable is nominally 4 m, and the wires are 4 mm2 (AWG 12). The blue wire must be
connected to -48 Vdc (live); the black wire to ground/+ve.
Note
The 2W2C DC power connector can be shorted inadvertently if applied at an angle.

Always insert with correct alignment.
For WTD rack the TRU doesn't require any cable ground connection to the rack.
Note
The use of integrated LVD (Low Voltage Disconnect) device is suggested in order to
protect the battery devices: the power system senses the battery voltage and sends a
signal to the LVD to connect when the battery voltage rises to a user-defined level;
when the battery voltage drops below another user-defined level, the power system
removes the signal from the LVD and the LVD opens to prevent the
batteries from over-discharging.

4.1.3 ODU300 Installation
This section describes the following installation procedures:
– Installing the Antenna (par. 4.1.3.1 on page 497)
– Installing the ODU (par. 4.1.3.2 on page 498)
– Installing a Coupler (par. 4.1.3.3 on page 509)
– Installing ODU Cables and Connectors (par. 4.1.3.4 on page 513)
– Weatherproofing (par. 4.1.3.5 on page 516)
The ODU300 has an internal Lightning Surge Suppressor.
The figure shows on the left side the yellow sticker meaning the presence of the internal Lightning Surge
Suppressor.
Figure 300. ODU (with the internal Lightning Surge Suppressor)
4.1.3.1 Installing the Antenna
Antennas must be installed in accordance with the manufacturer's instructions.
– For direct-mounted ODUs the antenna includes a collar with integral polarization rotator. Dependant
on frequency band, these antennas are available in diameters up to 1.8 m (6 ft).
– Where standard antennas are to be used, the ODU must be installed on a remote-mount, and a flex-
ible waveguide used to connect to its antenna.
Before going to the site, check that you have the required installation tools as recommended by the
antenna manufacturer, and that you have data for positioning the antenna on the tower, its polarization
and initial pointing.
– For direct-mounted ODUs, polarization is determined by the setting of the polarization rotator.
– For standard antennas, polarization is determined by the orientation of the antenna.
Note
Unused or incompletely used cable entry areas should be blocked off with foam rubber.

4.1.3.2 Installing the ODU
The type is ODU300.
– All ODUs are designed for direct-mounting to a collar supplied with direct-fit antennas.
– All ODUs can also be installed with standard antennas using a flex-waveguide remote-mount kit.
For single-antenna protected operation a coupler is available to support direct mounting of the two ODUs
to its antenna, or to support direct mounting onto a remote-mounted coupler.
4.1.3.2.1 Direct-Mounted ODUs
4.1.3.2.1.1 Overview
The ODU is attached to its mounting collar using four mounting bolts, with captive 19 mm (3/4") nuts.
The ODU mounts directly to its antenna mount as shown below.
An ODU should be installed with its connectors facing down as shown below.
Figure 301. ODU and Mounting Collar

Figure 302. Andrew Pole Mount and ODU Mounting Collar
Figure 302. shows the ODU mounting collar, pole mounting polarization rotator for an Andrew antenna.
Figure 303. RFS Pole Mount and Mounting Collar
Figure 303. shows the ODU mounting collar, pole mounting, and polarization rotator for RFS antenna.
Figure 304. Precision Pole Mounting and ODU Mounting Collar
Figure 304. shows the ODU mounting collar, pole mount, and polarization rotator for a Precision antenna.

4.1.3.2.2 Setting the Polarization
The polarization of the transmitted signal, horizontal or vertical, is determined by the position of the
polarization rotator fitted within the ODU mounting collar. The ODU is then mounted on the collar to match
the chosen polarization. The rotator is an integral part of the antenna mount. Vertical polarization is the
default setting. If the rotator is not set for the required polarization, you must adjust its orientation. This
topic includes typical adjustment procedures for Radio Waves and Andrew antennas. Antenna installation
instructions are included with all antennas. These instructions include procedures for setting polarization.
4.1.3.2.2.1 Procedure for Andrew Rotator
To change the polarization of the Andrew antenna:
1) Release (do not completely undo) the six metric Allen-head screws approximately 10 mm (3/
8 inch). Pull the collar forward and hold the rotator back, which will allow the rotator to disengage
from a notch in the collar, and turn freely.
2) Turn the rotator hub 90° until it locates back into a notched "timing recess" in the collar.
3) Check that the timing mark on the rotator hub has aligned with either a V or an H on the collar
to confirm polarization. Refer to this photo.
4) Ensure the rotator hub is correctly seated within its collar, then push the collar back against the
antenna mount and re-tighten the six screws.
Figure 305. Andrew ODU Collar and Polarization Rotator

4.1.3.2.2.2 Procedure for RFS Rotator
The polarization rotator is fixed by two Allen-head bolts.
To change the polarization of the RFS antenna:
1) Loosen the bolts. Refer to Figure 306.
2) Rotate by 90°.
3) Check bolt heads are located in the slot recesses.
4) Refasten.
Figure 306. RFS Rotator
Figure 306. shows a close-up of the polarization rotator being released from the vertical position (left) and
rotated clockwise towards horizontal (right).
4.1.3.2.2.3 ODU Polarization
The ODU must be mounted on the collar to match the chosen polarization.
Correct positioning for vertical or horizontal polarization is shown below.
Figure 307. ODU orientation for Vertical or Horizontal Polarization

4.1.3.2.3 Direct-Mount ODU Attachment Procedure
This topic describes the physical attachment of an ODU to an antenna mounting collar.
Related procedures are:
– Grounding an ODU (par. 4.1.3.2.6 on page 508)
– Installing the ODU cable and connectors (par. 4.1.3.4 on page 513)
4.1.3.2.3.1 Attaching the ODU
An ODU should be installed with connectors facing down.
To attach the ODU:
1) Check that the ODU mounting collar, polarization rotator, ODU waveguide feed head and O-
ring, are undamaged, clean, and dry.
2) Set the polarization rotator for the required polarization. Refer to par. 4.1.3.2.2 - Setting the
Polarization on page 500.
3) Apply a thin layer of silicon grease around the ODU feed-head O-ring.
A tube of silicon grease is included in the ODU installation kit.
4) Fully loosen the nuts on the four ODU mounting bolts.
5) Position the ODU so the waveguide slots (ODU and rotator) will be aligned when the ODU is
rotated to its end position.
6) Fit the ODU onto its mounting collar by inserting the bolts through receptor holes in the collar,
then rotate the ODU clockwise to bring the mounting bolts hard up against the slot ends.
7) Carefully bring the ODU forward to fully engage the ODU feed head with the polarization rotator.
8) Finger-tighten the four nuts, checking to ensure correct engagement of ODU with mounting col-
lar.
9) Ensure the ODU bolt-down points are correctly seated, then tighten the four nuts with a 19 mm
(3/4") torque wrench (it must be set to 35 Nm).
10) To remove an ODU, reverse this procedure.
When removing an ODU from its mount, ensure the ODU fastening nuts are fully released.

4.1.3.2.4 Remote-Mounted ODUs
An ODU can be installed separate from its antenna, using a remote-mount to support the ODU, and a
flexible-waveguide to connect the ODU to its antenna. A remote mount allows use of standard, single or
dual polarization antennas. The mount can also be used to remotely support a protected ODU pairing
installed on a coupler. The coupler connects to the remote mount assembly in the same way as an ODU.
When co-channel XPIC single antenna link operation is required, the two ODUs must each be connected
to their respective V and H antenna ports using remote mounts.
The remote mount clamps to a standard 114 mm pole-mount, and is common to all frequency bands.
The following photos show the remote mount solution (P/N 3CC58046AAAA).
Figure 308. Remote Mount: front view
Figure 309. Remote Mount: rear view

Figure 310. Remote Mount with an ODU installed: front view
Figure 311. Remote Mount with an ODU installed: rear view

Figure 312. Remote Mount with an ODU installed and flexible waveguide
Figure 313. Remote Mount with the 1+1 coupler installed

Figure 314. Remote Mount with the 1+1 coupler and one ODU installed
4.1.3.2.4.1 Flexible waveguides
Flexible waveguides are frequency band specific and are normally available in two lengths, 600 mm (2
ft) or 1000 mm (3.28 ft). Both flange ends are identical, and are grooved for a half-thickness gasket, which
is supplied with the waveguide, along with flange mounting bolts.
To prevent wind-flex, a flexible waveguide or coax must be suitably fastened or supported over its length.
Note
The flexible waveguides have tin-plated brass flanges to minimize dissimilar-metal corrosion between the
aluminum feed-head on the ODU and the brass antenna port(s) used on most standard antennas.
Where the length is greater than the 1 m (3.28 ft) contact your Alcatel-Lucent service support center.

4.1.3.2.4.2 Waveguide Flange Data
Table 33. lists the antenna port flange types used with the ODU300, plus their mating flange options and
fastening hardware for remote mount installations. UDR/PDR flanges are rectangular; UBR/PDR flanges
are square.
On the ODU, the two flange styles are:
– UDR. 6-hole or 8-hole (6/8 bolt holes depending on frequency range/waveguide type), flush-face
flange with threaded, blind holes.
– UBR. 4-hole flush-face flange with threaded, blind holes.
The corresponding mating flange styles are:
– PDR. 6-hole or 8-hole flange with gasket groove and clear holes.
– PBR. 4-hole flange with a gasket groove and clear holes.
All fastening hardware is metric.

Waveguide
Waveguide
Frequency
Washers
Thread
Flange
Flange
Mating
Spring
Depth
Radio
Bolt Length
Band
Reqd
Reqd
Bolts
Spec
Type
Type
Hole
Bolt
Required
Flange thickness +
6 GHz UDR70 PDR70 WR137 8 x M5 8 M5x0.8 6H 10
Hole depth - 2mm
Flange thickness +
7/8 GHz UDR84 PDR84 WR112 8 x M4 8 M4x0.7 6H 8
Hole depth - 2mm
Flange thickness +
10/11 GHz UDR100 PDR100 WR90 8 x M4 8 M4x0.7 6H 8
Hole depth - 2mm
Flange thickness +
13 GHz UBR120 PBR120 WR75 4 x M4 4 M4x0.7 6H 8
Hole depth - 2mm
Flange thickness +
15 GHz UBR140 PBR140 WR62 4 x M4 4 M4x0.7 6H 8
Hole depth - 2mm
18/23/26 Flange thickness +

UBR220 PBR220 WR42 4 x M3 4 M3x0.5 6H 6
28/32/38 Flange thickness +

UBR320 PBR320 WR28 4 x M3 4 M3x0.5 6H 6

4.1.3.2.5 Remote-Mount Installation Procedure
This topic describes the installation of a remote mount, the attachment of the ODU to the mount, and the
installation of the flexible waveguide.
4.1.3.2.5.1 Installing the Remote Mount
The remote mount attaches to a standard 114 mm pipe mount using two saddle clamps. Firmly fasten the
clamp nuts.
4.1.3.2.5.2 Attaching the ODU and Flexible Waveguide
Before attaching the ODU to the remote mount, fit the flexible waveguide to the ODU.
1) Remove one gasket from the packet supplied with the flexible waveguide,apply a thin smear
of silicon grease to the gasket, and fit the gasket to the recess in the flange.
2) Firmly attach the flange to the ODU feed head using the bolts supplied.
3) Fully loosen the nuts on the four ODU mounting bolts, then thread the waveguide through the
center of the mount.
4) Attach the ODU to the mount by inserting the bolts through the receptor holes,and rotating the
ODU clockwise to bring the mounting bolts hard up against the slot ends.
5) Tighten the four nuts with a 19 mm (3/4") torque wrench (it must be set to 35 Nm).
6) Prepare the antenna-end of the flexible waveguide as in step 1 above.
7) Check, and adjust if necessary, the run of the waveguide for best protection and support posi-
tion before fastening the flange to the antenna port.
8) Secure the waveguide to prevent wind-flex using hanger assemblies or similar. If cable ties are
used, do not over-tighten.
4.1.3.2.6 Grounding the ODU
To ground the ODU use the following procedure:
1) Locate the 2 m ground wire (6 mm2) in the ODU installation Kit. One end is fitted with a crimp
lug, the other is free.
2) Fasten the lugged end of ground wire to the ODU grounding stud. Before tightening, ensure
the cable is correctly aligned towards the tower.
3) Locate a position on a tower member for the ground clamp. This must be as close as practical
below the ODU for downward-angled positioning of the ground wire.
4) Scrape any paint or oxidation from the tower at the clamping point to ensure there will be good
low-resistance contact
5) Cut the ground wire so there will be a just a little slack in the wire when it is connected to the
ground clamp. A ground clamp is supplied as part of all ODU Cable Installation and Suppressor
kits.

6) Strip the insulation back by 25 mm (1 inch), fit into ground clamp, and firmly secure the clamp
to tower.
7) Liberally apply conductive grease/paste around the ground clamp to provide corrosion resis-
tance. Also apply to the ODU ground stud.
4.1.3.3 Installing a Coupler
4.1.3.3.1 Coupler Overview
Couplers (combiners) are available for equal loss or unequal loss.
– For equal loss the attenuation per side is nominally 3 dB (3 dB), which applies to both the transmit
and receive directions, meaning the additional total one-way attenuation compared to a non-
protected link is 7 dB.
– For unequal loss the attenuation is nominally 1 dB/6 dB. They have application on rain-affected
bands, 13 GHz and above.
The rationale for using unequal ratios is that they can be shown to lower annual outage due to rain fades
as compared to links deployed with equal loss couplers.
4.1.3.3.2 Coupler Installation Procedure
Note
A coupler installation procedure is included with each coupler.
The following procedure summarizes installation of a direct-mounted coupler. A coupler may also be
installed remote-mounted, where a single flexible waveguide is used to connect the coupler to its antenna.
4.1.3.3.2.1 Attaching a Direct-Mounted Coupler
Before installing a coupler check there will be sufficient mechanical clearance for the coupler and its
ODUs. There should be no clearance issues using approved antennas when installed correctly on its
mount with the appropriate left or right offset. However care must be taken at locations where a non-
standard antenna installation is required.
The ODUs are attached to the coupler as if attaching to an antenna except that there is no polarization
rotator associated with each ODU. Rather the coupler polarization is set to match the V or H antenna
polarization using 0 degree or 90 degree coupler interfaces, which are supplied with the coupler. Couplers
are default fitted with the vertical polarization interface.
Note
To change the polarization refer to the procedure included in each coupler.
A coupler must always be installed onto its antenna before ODUs are attached to the coupler.

To install a coupler:
For a vertically polarized antenna proceed to step 2.
For a horizontally polarized antenna begin at step 1.
(Antenna polarization setting is described in par. 4.1.3.2.2 - Setting the Polarization on page 500).
1) To change the coupler interface, remove by unscrewing its four retaining screws. Replace with
the required interface, ensuring correct alignment between the interface and coupler body
alignment indicators. Relocate the O-ring to the newly fitted interface.
2) Remove all protective tape from the waveguide ports and check that the ODU/coupler mounting
collar, polarization rotator, coupler interface and O-ring, are undamaged, clean, and dry.
3) Apply a thin layer of silicon grease around the coupler interface O-ring.
Note
A tube of silicon grease is included in ODU and coupler installation kits
4) Fully loosen the nuts on the four coupler mounting bolts.
5) Position the coupler so the waveguide slots (coupler and rotator) will be aligned when the ODU
is rotated to its end position.
6) Fit the coupler onto its mounting collar by inserting the bolts through receptor holes in the collar,
then rotate the coupler clockwise to bring the mounting bolts hard up against the slot ends.
7) Carefully bring the coupler forward to fully engage the coupler feed head with the polarization
rotator in the mounting collar.
8) Finger-tighten the four nuts, checking to ensure correct engagement of coupler with mounting
collar.
9) Ensure the coupler bolt-down points are correctly seated, then tighten the four nuts with an
open-ended 19 mm (3/4") spanner.
10) To remove a coupler, reverse this procedure.
Figure 315. shows an installed coupler. Figure 316. and Figure 317. show a completed installation with
ODUs and grounding.
Related procedures are:
– Installing the ODUs; refer to par. 4.1.3.2.3 - Direct-Mount ODU Attachment Procedure on page 502.
Note that when attaching an ODU to a coupler there is no requirement to first set a polarization; the
ODUs are attached such that when rotated into position there is correct alignment of the waveguide
slots. ODUs may be attached such that cables exit to the right or left of the ODU.
– Grounding an ODU; refer to par. 4.1.3.2.6 - Grounding the ODU on page 508.
Installing the ODU cable and connectors; refer to par. 4.1.3.4 - Installing ODU Cables and Connectors on
page 513.

Figure 315. Coupler fitted to Antenna
Figure 316. Coupler Installation with ODUs

(NB: The external ligthning suppressors are no more needed)

Figure 317. Coupler Installation with ODUs: Rear View
(NB: The external ligthning suppressors are no more needed)
Warning: it is necessary to add some extra-length for maintenance or orientation modification of the
antenna.
4.1.3.3.3 Unused and Disconnected Coupler
Unused ODU ports on a coupler must the blanked off with a microwave load as at some frequencies the
reflected power can affect operation at the remaining port, partly canceling the wanted signal.
A flange-mounted termination is used to absorb the RF energy. They are needed in 1+0 and cascaded
coupler applications where some ODU ports are left open/ not attached to an ODU.
Terminations are available from Alcatel-Lucent.

4.1.3.4 Installing ODU Cables and Connectors
Note
The ODU cable installation must comply with 9500 MPR-E requirements. If the cable, grounds and
weatherproofing are incorrectly installed, the Alcatel-Lucent warranty can be voided.
This section includes information on:
– Cable Options (par. 4.1.3.4.1 on page 513)
– Coaxial Cable Installation Requirements (par. 4.1.3.4.1.1 on page 513)
– Cable Grounding (par. 4.1.3.4.2 on page 514)
– Type N Cable Connectors (par. 4.1.3.4.2.1 on page 515)
4.1.3.4.1 Cable Options
The recommended ODU cable type for connections of less than 80 m (262 ft) is the 1AC041350001 cable.
For other cable options to reach higher distance (300m/984ft) ask Alcatel-Lucent.
4.1.3.4.1.1 Coaxial Cable Installation Requirements
Task Required Considerations Explanation
Installing Connectors Crimped connectors Always use the crimp tool designed for the
crimped connectors/cable being used. A rec-
ommended crimp tool for the connectors
used with the ET 390998 cable is available
from Alcatel-Lucent.
When removing the jacket Take great care when removing the jacket to
- all coaxial cable keep the outer conductor intact. A scored
outer conductor will weaken the cable and,
for a solid outer cable, can cause the outer
conductor to break or crack when subse-
quently bent.
When removing the jacket Always use the cut-off and strip tool specifi-
-solid outer conductor cable cally designed for the cable being used.
Fastening Type N connectors Tighten Type N connectors (male to female)

by hand only.
Weatherproofing All outdoor connections must be made

weatherproof. Refer to Weatherproofing.
cont.

Planning the Route Protection for the cable The route chosen must provide physical pro-
tection for the cable (protection against acci-
dental damage).
Keep access to tower and ser- The cable must be positioned so that there is
vices clear unimpeded access to the tower and to ser-
vices on the tower.
Ease of running and fastening Use a route which minimizes potential for
damage to the cable jacket and avoids
excessive cable re-bending.
Installing the Cable Cable jacket Keep cable clear of sharp edges.
Cable support Rod support kits or similar must be used

across unsupported sections of the cable run
so that the cable cannot flex in the wind.
Bend radius Ensure the minimum bend radius for the

cable is not exceeded.
Cable ties Use one UV-resistant cable tie every 1m (3 ft)

or less, of cable.
Cable grounding Ensure the cable is grounded in accordance

with the instructions provided in Cable
Grounding.
Ice-fall protection Ensure adequate physical protection for the

cable where ice-fall from towers can occur.
4.1.3.4.2 Cable Grounding
Ground kits are included in the ODU Cable Kits.
For tower/mast installations the ODU cable must be grounded at:
– The point where it comes on to the tower from the ODU
– The point where it leaves the tower to go to the equipment building
– Not more than 25 m intervals on the tower if the height on the tower exceeds 50 m
– A point just prior to building entry
Figure 318. shows typical tower locations for cable grounding.
At non-standard installations, such as building tops or the sides of buildings, follow the same general
guidelines but where proper grounding points are not provided these must first be installed.
For ground kit installation instructions refer to the guide provided with each kit.

ODU & antenna
ODU ground wire
Cable ground
ODU cable supported by black cable ties

at not more than 1 m intervals.
Must not run adjacent to tower lightning
ground or electrical cables
Install additional cable grounds at not more

than 25 m intervals if the height of cable on
the tower exceeds 50 m
Cable ground Cable ground
Cable carrier Rack ground bar
ground bar
Site grounding
Figure 318. Locations for Cable Grounds
4.1.3.4.2.1 Type N Cable Connectors
Note
All type N connectors used outdoors must be weatherproofed.

Refer to par. 4.1.3.5 - Weatherproofing on page 516.
Ensure connectors are correctly fitted. Where crimp connectors are used, ensure the correct crimp tool
is used.

4.1.3.5 Weatherproofing
Weatherproofing kits are included with consumable kit. Two types of weatherproofing media are supplied.
4.1.3.5.1 Mastic Tape
The ODU cable ground kits include rolls of vinyl and butyl mastic tape. For these, a two-layer wrap process
is recommended:
– An initial layer of mastic tape. It is this tape that provides the weatherproofing.
– A top layer of vinyl tape to support good amalgamation and adhesion of the mastic tape and to
provide UV protection.
Note
If mastic tape is used to weatherproof connectors a three-layer process is recommended, where a layer
of vinyl tape is applied before the mastic to facilitate easy strip-back when connector disconnection is
required. Special attention must be given to ensuring the mastic tape seals cleanly to the primary surfaces,
such as the cable jacket.
4.1.3.5.1.1 Wrapping Guidelines, Mastic tape
To weatherproof connectors start at 1. To weatherproof a cable ground start at 3.
1) Ensure connectors are firmly hand-tightened, dry, and free from all grease and dirt. If neces-
sary, clean with rag lightly moistened with alcohol-based cleaner.
2) Pre-wrap using vinyl tape. Use a 25% overlay when wrapping. To avoid curl-back do not stretch
the tape too tightly at the end point.
Note
On an ODU connector, leave at least two-thirds of the smooth length of the barrel clear
of pre-wrap vinyl tape, to ensure the mastic tape has sufficient area of direct grip.
3) Wrap with mastic tape using a 75% overlay. Where possible, use not less than a 25 mm (1")
attachment onto the primary surface (25 mm past the cable sheath cut, or any pre-wrap).
Note
There must be a full seal of mastic tape onto the primary surface for weatherproofing integrity.
4) Lightly firm over by hand to ensure a full seal at all points, using a tear-off section of the mastic
tape backing to protect your hands. Check that there is no possibility of water entry before pro-
ceeding to the next step 5.
5) Cover the mastic tape with a final layer of vinyl tape. To avoid curl-back, do not stretch the tape
too tightly at the end.

Note
To avoid displacement of the mastic tape, do not stretch the final layer of
vinyl tape across sharp corners and edges.
4.1.3.5.2 Self Amalgamating Tape
Self amalgamating tape binds to the host and bonds between layers to provide a continuous seal. It is
especially useful in tight locations, such as around the Type N connectors of the suppressor when installed
with its support bracket on an ODU.
4.1.3.5.2.1 Wrapping Guidelines, Amalgamating Tape
1) Ensure the connectors are firmly hand-tightened, dry, and free from all grease and dirt. If nec-
essary, clean with a rag lightly moistened with alcohol-based cleaner.
2) Apply the tape with tension (slight stretching), using at least a 75% overlay.
3) Where possible, apply the tape 25 mm (1") past the ends of the connector barrels to ensure
the weatherproof bond extends beyond the areas requiring protection. The tape must be
applied in such a way that the sealing is robust (no obvious weak points).
4) To avoid curl-back, do not stretch the tape too tightly at the end.
5) To assist UV protection, a post-wrap using vinyl tape can be applied.

4.1.4 MPT-HC Installation
The MPT-HC installation section is divided in:
– Types of MPT-HC (par. 4.1.4.1 on page 519)
– MPT-HC operative information (par. 4.1.4.2 on page 521)
– How to change polarization in the MPT-HC (par. 4.1.4.3 on page 529)
– Types of RF couplers (par. 4.1.4.4 on page 531)
– Types of Pole Mounting Installation kits (par. 4.1.4.5 on page 533)
– Types of nose adapters (par. 4.1.4.6 on page 534)
– 1+0 MPT-HC installation (integrated antenna) - all frequencies (par. 4.1.4.7 on page 535)
– 1+0 MPT-HC installation (non integrated antenna) - all frequencies (par. 4.1.4.8 on page 538)
– 1+1 MPT-HC installation (integrated antenna) (par. 4.1.4.9 on page 540)
– 1+1 MPT-HC installation (non integrated antenna) (par. 4.1.4.10 on page 549)
– How to pull up the cables from indoor to the MPT-HC (par. 4.1.4.11 on page 555)
– Cable connection to MPT-HC (11-38 GHz) (par. 4.1.4.12 on page 560)
– Cable connection to MPT-HC (6-7-8 GHz) (par. 4.1.4.13 on page 567)
– Installing the “Flextwist“ waveguide (not integrated antenna cases) (par. 4.1.4.14 on page 572)
– MPT-HC system grounding (par. 4.1.4.15 on page 574)
– Cable Grounding (par. 4.1.4.16 on page 575)
– Type N connectors and Grounding kits waterproofing on the IDU/ODU cables (par. 4.1.4.17 on page
576)

4.1.4.1 Types of MPT-HC
The MPT-HC consists of one or two cabinets including the Ethernet interface + modem + RF transceiver
+ branching of a channel.
Three mechanical solutions are adopted:
[1] with embedded diplexer for cost optimisation (11 GHz to 38 GHz), shown in Figure 319., where the
branching (diplexer) is internal to the MPT-HC cabinet; this type of MPT-HC is identified by one
Logistical Item only;
[2] with embedded diplexer for cost optimisation and different mechanics from 11-38 GHz (6 GHz),
shown in Figure 320., where the branching (diplexer) is internal to the MPT-HC cabinet; this type
of MPT-HC is identified by one Logistical Item only;
the shifter customization (7 GHz and 8 GHz), shown in Figure 321., where MPT-HC is composed
by two independent units: the BRANCHING assembly (containing the diplexer) and the RF TRANS-
CEIVER assembly (containing the RF section); each of this type of MPT-HC is identified by two
Logistical Items, one for the BRANCHING assembly and another for the RF TRANSCEIVER
assembly. To read the BRANCHING assembly identification label it is necessary to separate the
BRANCHING assembly from the RF TRANSCEIVER assembly.
TRANSCEIVER + BRANCHING MPT-HC IDENTIFICATION LABEL
CO-BOX
Figure 319. Views of MPT-HC with embedded diplexer (11-38 GHz)

Figure 320. Views of MPT-HC with embedded diplexer (6 GHz)
TRANSCEIVER BRANCHING
TRANSCEIVER BRANCHING
IDENTIFICATION IDENTIFICATION
LABEL LABEL (INSIDE)
CO-BOX
Figure 321. Views of MPT-HC with external diplexer (7 GHz and 8 GHz)

4.1.4.2 MPT-HC operative information
This paragraph gives operative information, for installation regarding:
– MPT-HC with embedded or external diplexer herebelow
– MPT-HC with external diplexer (additional information) on page 524
4.1.4.2.1 Operative information on MPT-HC with embedded or external diplexer
4.1.4.2.1.1 General, views and access points
Figure 322. on page 522 (for MPT-HC with embedded diplexer) and Figure 323. on page 523 (for MPT-
HC with external diplexer) show MPT-HC views and access points.
The external interfaces are listed in Table 34. below, with the corresponding connector.
Table 34. MPT-HC external interfaces
Ref. in Interface Connector Further

Figure 322. information
and
Figure 323.
(1) RF interface for connection of antenna or coupler waveguide Table 35. herebelow
(2) Connector for power supply coax. cable male N 50 ohm
(3) Hole for Ethernet connection (in the co-box) Gland for Cat5e
or optical cable
(optional)
(4) Hole for connection to a second MPT-HC in 1+1 ODC

(in the co-box)
Table 35. RF interface

FREQUENCY GHz -> 6 7 8 11 13-15 18-26 38
Waveguide type -> WR137 WR112 WR112 WR75 WR62 WR42 WR28

(1) (A)
(A) (A)
(2)
(A) OPENING THE CO-BOX

Place to install
SFP for 1+1
RJ45 the optional SFP
configuration
plug-in
(3) (4)
(A) Locking hooks (4) to fix/unfix MPT-HC assembly to antenna or coupler
(1) RF interface for connection of antenna or coupler. Remove the plastic cover.
WARNING: A waterproofness tape is glued on the waveguide of the MPT-HC. It must never be
removed.
Figure 322. Views of MPT-HC with embedded diplexer (11-38 GHz)

(1)
(A)
(B) (B)
(A) (A)
(B) (B)
(A)
(2)
OPENING THE CO-BOX
RJ45 for electrical connection
(3)
Place to install the optional
(4) SFP for optical connection
SFP for 1+1 configuration
(A) 4 locking hooks to fix/unfix branching assembly (diplexer) to transceiver
(B) 4 locking hooks to fix/unfix branching assembly (diplexer) to antenna or coupler
removed.
Figure 323. Views of MPT-HC with external diplexer (7 GHz and 8 GHz)

(1)
(A)
(A) (A)
(A)
(2)
OPENING THE CO-BOX
RJ45 for electrical connection
(3)
Place to install the optional
(4) SFP for optical connection
SFP for 1+1 configuration
removed.
Figure 324. Views of MPT-HC with embedded diplexer (6 GHz)
4.1.4.2.2 Additional operative information on MPT-HC with external diplexer
4.1.4.2.2.1 MPT-HC composition
As shown in Figure 325., the MPT-HC assembly is made up of two boxes, one for diplexer system
(BRANCHING) and the other for the all other active functions (TRANSCEIVER) connected together to
form the MPT-HC.
An O-RING present in the TRANSCEIVER box guarantees the MPT-HC assembly waterproofness.

N.B. This is a conductive O-RING and must be left dry. Do not wet it with silicon grease (silicon
grease must be used only on O-ring between MPT-HC and antenna).
BRANCHING TRANSCEIVER
WARNING 1 WARNING 2
Figure 325. Composition of MPT-HC with external diplexer
WARNING 1: A waterproofness tape is glued on the waveguide of the MPT-HC. It must never be removed.
WARNING 2: This gasket must never be removed.
The TRANSCEIVER box performs all the functions, but does not include the diplexer system.
The BRANCHING box provides the interface between the pole mounting/antenna and the TRANS-
CEIVER.
The favorite solution foresees the possibility to change in field a spare part TRANSCEIVER without dis-
connecting the BRANCHING box from the pole mounting/antenna. The TRANSCEIVER and BRANCH-
ING boxes fixing and unfixing are obtained through the four levers.
4.1.4.2.2.2 TRANSCEIVER and BRANCHING boxes coupling
Figure 326. below shows the TRANSCEIVER and BRANCHING boxes coupling surfaces:
– (A) BRANCHING box label informative content

described in Figure 329. on page 528
– (B) (HIGH FREQ) and (C) (LOW FREQ) RF interfaces on BRANCHING box
– (D) (TX) and (E) (RX) RF interfaces on TRANSCEIVER box
The TRANSCEIVER and BRANCHING boxes can be coupled in two alternative ways (180°-rotated with
respect to each other):

– BRANCHING box (B) (HIGH FREQ) coupled to TRANSCEIVER box’s (D) (TX)
in this case the TX part of the transceiver uses the HIGH frequency range of the Shifter set by the
WebEML (see field D in Figure 329. on page 528); obviously the RX part of the transceiver uses the
corresponding LOW frequency range;
– BRANCHING box (C) (LOW FREQ) coupled to TRANSCEIVER box’s (D) (TX)
in this case the TX part of the transceiver uses the LOW frequency range of the Shifter set by the
corresponding HIGH frequency range.
(D)
(A) (B)
(C)
(E)
Figure 326. MPT-HC TRANSCEIVER and BRANCHING boxes coupling surfaces
N.B. There is only one possible way to couple the BRANCHING box and the TRANSCEIVER box:
there is a mistake-proofing put by the factory on the TRANSCEIVER box, whose position
depends on the type of transceiver (low or high band, as shown in Figure 327.) to ensure that
the association with the BRANCHING box is always the right one.
Hole
Mistake-proofing
Figure 327. 6-7-8 GHz MPT-HC BRANCHING box mistake-proofing

4.1.4.2.3 Labels affixed on the MPT-HC
a) The label depicted in Figure 328. below is affixed externally to all types of MPT-HC and MPT-HC
TRANSCEIVER boxes;
b) Only for MPT-HC with external diplexers, an additional label, depicted in Figure 329. on page 528,
is placed on the branching assembly.
SYMBOL OR WRITING MEANING
9500-MPR Equipment Acronym & Alcatel-Lucent Logo
CE European Community logo
! Not harmonized frequency logo
2002/96/EC WEEE (Waste Electrical and Elec-

tronic Equipment) Logo
-28 V / -58 V 1,6 A / 0,8 A Power supply range and current range
Logistical Item (shown numbers as examples) Logistical Item for Customer
A Logistical Item for Customer, bar code 128
Serial n° (shown numbers as examples) Factory Serial number
B Factory Serial number bar code 128
TX Frequency MHz (shown numbers as examples) Working frequency range
Shifter MHz (shown numbers as examples) Shifter
TX Sub-band (shown numbers as examples) TX Sub-band
Initial SW/ICS (shown numbers as examples) P/N and ICS of the software loaded in factory
PN/ICS (shown numbers as examples) Factory P/N + ICS
C Factory P/N + ICS bar code 128
Figure 328. Label affixed on the MPT-HC and MPT-HC TRANSCEIVER box

N.B. In the label A9400 is written because the diplexers are also used in A9400 AWY.
A9400 Equipment Acronym & Alcatel-Lucent Logo
12345 (example) Notified body

PN/ICS 3DB 06775 AAAA 01 (example) Factory Technical Code + ICS
A Factory Technical Code + ICS, bar code 128
Logistical Item 3DB 06775 AAXX (example) Logistical Item for Customer
B Logistical Item for Customer, bar code 128
S/N CW 050609001 (example) Factory Serial number
C Factory Serial number bar code 128
D (shown numbers as examples) – the field “Shifter MHz” indicates the possible
frequency bands that can be used with this
branching assembly.
The choice between different shifters is done
byCraft Terminal;
– for each “Shifter MHz”, the TX “LOW” and
“HIGH” rows indicate the frequency range
assumed by transceiver TX section, accord-
ing to the TRANSCEIVER and BRANCHING
boxes coupling.
Figure 329. Label affixed inside the MPT-HC BRANCHING box

4.1.4.3 How to change polarization in the MPT-HC
4.1.4.3.1 11-38 GHz MPT-HC
Note
The polarization must be changed to match the antenna polarization and the coupler nose waveguide.
1 Remove the plastic protection cap from the 2 Change the polarization of the MPT-HC, if
MPT-HC. required (default: vertical polarization).
Protection cover
Unscrew the 2 screws

and rotate by 45°
3 Horizontal polarization.

4.1.4.3.2 6-7-8 GHz MPT-HC
These MPT-HC have fixed polarization (vertical polarization). To change the polarization it is necessary
to change the antenna polarization and to install the MPT-HC 90° rotated.
1 Example of vertical polarization. 2 Example of horizontal polarization.

4.1.4.4 Types of RF couplers
– RF couplers for 6-7-8 GHz bands
– RF couplers for bands from 11 to 38 GHz
4.1.4.4.1 RF couplers for 6-7-8 GHz bands
Table 36. Codes, characteristics and views of RF couplers for bands from 6 to 8 GHz
Waveguide Coupler
Code Description Coupling loss
(3 ports) type
3CC58056AAXX 6 GHz 3 dB Coupler WR 137

Bal. 3 dB / 3 dB
3CC14536ABAA 7.1–8.5 GHz 3 dB Coupler WR 112
3CC58056ABXX 6 GHz 10 dB Coupler WR 137

Unbal. 1 dB / 10 dB
3CC14536AAXX 7.1–8.5 GHz 10 dB Coupler WR 112
Coupler weight = 6 Kg about
Figure 330. MPT-HC RF coupler views (Bands 6-7-8 GHz)

4.1.4.4.2 RF couplers for bands from 11 to 38 GHz
Table 37. Codes, characteristics and views of RF couplers for bands from 11 to 38 GHz
Waveguide Coupler Coupling
Code Description
(3 ports) type loss
3CC13472AAXX 13/15 GHz 3 dB Coupler WR 62

Bal. 3 dB / 3 dB
3CC13473AAXX 18/26 GHz 3 dB Coupler WR 42
3CC13472ABXX 13/15 GHz 10 dB Coupler WR 62

Unbal. 1 dB / 10 dB
3CC13473ABXX 18/26 GHz 10 dB Coupler WR 42
Coupler weight = 4.3 Kg about
Figure 331. MPT-HC RF coupler view (Bands from 11 to 38 GHz)

4.1.4.5 Types of Pole Mounting Installation kits
– Integrated antenna Pole Mounting Installation kits
– "Pole Mounting for Remote ODU" Installation kits
4.1.4.5.1 Integrated antenna Pole Mounting Installation kits
These integrated antenna Pole Mounting kits are designed for quick mechanical installation, and:
– are included inside the chosen antenna kit.
– foresee the “Fine Tuning” for the positioning of the Antenna.
As shown in Figure 332., these integrated antenna Pole Mounting kits are supplied with the frequency-
specific nose adapter for mounting the frequency-specific MPT-HC transceiver or RF Coupler.
In general, the nose adapter:
– in case of smallest antennas, is already mounted on the antenna
– in case of largest antennas, is supplied separately, and must be mounted on the antenna during the
installation procedure.
Figure 332. Example of integrated antenna Pole Mounting

(with antenna and nose adapter)

4.1.4.5.2 "Pole Mounting for Remote ODU" Installation kits
These kits are frequency independent, and provide only the mechanical support function. The frequency
specialization is obtained mounting the frequency-specific nose adapter.
N.B.: The nose adapter shown is not included in the kit.
Figure 333. "Pole Mounting for Remote ODU" Installation kit (3DB10137AAXX)
4.1.4.6 Types of nose adapters
In case of:
– integrated antenna configurations, the nose adapter is delivered inside the chosen antenna kit; in
this case the RF interface is used to attach the frequency-specific MPT-HC transceiver or RF Cou-
pler.
– Non Integrated Antenna configurations, the nose adapter is used to attach:
• at one side, the frequency-specific MPT-HC transceiver or RF Coupler
• at the other side, to attach the Flextwist cable toward the antenna.
In these Non Integrated Antenna configurations, the nose adapter is delivered as individual item, and
must be always mounted on the ODU or Coupler, during the installation procedure.
The mounting accessories are delivered with the nose adapter.

4.1.4.7 1+0 MPT-HC installation (integrated antenna) - all frequencies
[1] Check/Set the coupling between the TRANSCEIVER and BRANCHING boxes (only for MPT-HC
with external diplexer).
[2] Install the Antenna and Pole Mounting.

This pole mounting is delivered as “pole mounting”, “antenna”, and frequency-specific “nose
adapter” already assembled. The integrated antenna is mounted on the pole front.
Antenna and pole mounting must be installed in accordance with the manufacturer’s instructions.
[3] Check or change the polarization on the Antenna nose.

To change the polarization, follow the instructions supplied with each antenna. Figure below shows
an example.
N.B. The antennas are normally supplied with vertical polarization.
Figure 334. Example of antenna polarization change (“1+0” MPT-HC integrated antenna)
[4] Take off the solar shield from the MPT-HC transceiver by unscrewing the screws placed on the solar
shield back panel.
[5] Install the MPT-HC on the Antenna nose adapter.
N.B. Before inserting the MPT-HC on nose adapter, it is mandatory to put SILICONE grease
on the O-ring.

Putting silicone grease
Figure 335. Putting silicone grease on O-ring before MPT-HC insertion
1) Grasp the MPT-HC module by the handle.
2) Open the four looking hooks (1) arranged on the four walls of the MPT-HC unit.
3) For 6-7-8 GHz MPT-HC only rotate the MPT-HC depending on the horizontal or vertical polar-
ization, and slide it on the nose adapter.
4) Secure the MPT-HC module through the four hooks (1) on the relative brackets (2).
(2) Bracket
(1) Hook
Figure 336. MPT-HC 1+0 installation for integrated antenna (11-38 GHz)
N.B. For 11-38 GHz MPT-HC remember to set first the correct polarization.

(1) Hook
(2) Bracket
Figure 337. MPT-HC 1+0 installation for integrated antenna (6-7-8 GHz: vertical polarization)
(1) Hook
(2) Bracket
Figure 338. MPT-HC 1+0 installation for integrated antenna (6-7-8 GHz: horizontal polarization)
REMINDER: The MPT-HC/antenna assembly requires no additional seal on the SHF flanges; the
two ends are smooth. The O-ring seal around the male “nose” provides sealing.
[6] Ground the MPT-HC system.
[7] Pre-point the antenna.
[8] Reinstall the solar shield onto the MPT-HC transceiver by screwing on it the solar shield screws.
[9] Affix the EMF stickers.

4.1.4.8 1+0 MPT-HC installation (non integrated antenna) - all frequencies
[2] Install the Nose Adapter on the “Pole Mounting for Remote ODU”.
[3] Install the “Pole Mounting for Remote ODU”.

Pole mounting must be installed in accordance with the manufacturer’s instructions.
In case of missing instructions, fix the U-bolts with 34 N x m tightening torque.
N.B. The pole mounting can be installed on the Right or Left hand side of the pole depending
on the azimuth and on the configuration of the tower.
Figure 339. "Pole Mounting for Remote ODU" installation
[4] Take off the solar shield from the MPT-HC transceiver by unscrewing the screws placed on the solar
shield back panel.
[5] Install the MPT-HC.
N.B. Before inserting the MPT-HC on nose adapter, it is mandatory to put SILICONE grease
on the O-ring.
Figure 340. Putting silicone grease on O-ring before MPT-HC insertion
1) Grasp the MPT-HC module by the handle. Open the four looking hooks arranged on the four
walls of the MPT-HC unit.
2) Position the Pole mounting support on the pole side as shown in the plant documentation.

3) Position the MPT-HC and slide it on the nose adapter.
4) Secure the MPT-HC module through the four hooks onto the relative brackets.
Figure 341. MPT-HC 1+0 installation for not integrated antenna (11-38 GHz with pole mounting
P/N 3DB 10137 AAAB)
Figure 342. MPT-HC 1+0 installation for not integrated antenna (6-7-8 GHz with pole mounting
P/N 3DB10137AAXX)
[6] Install the external Antenna with its own Pole Mounting.
The installation of the antenna and of its own pole mounting, as well as the antenna polarization
check/change, must be done in accordance with the manufacturer’s instructions.
[7] Connect the antenna side (flange) of the Pole Mounting’s nose adapter to the external antenna, by
means of the “Flextwist“ waveguide.
[10] Reinstall the solar shield onto the MPT-HC transceiver by screwing on it the solar shield screws.

4.1.4.9 1+1 MPT-HC installation (integrated antenna)
4.1.4.9.1 11-38 GHz

[2] Check or change the polarization of the RF coupler.

The axial adaptation between H polarization to V polarization (and viceversa) is a mechanical/elec-
trical adjustment. Every mechanical “STEP” is a 30° adjustment.
Figure 343. Coupler Polarization Change (11-38 GHz) - 1st Step and 2nd step
The final result must be as shown in Figure 346. on page 541 (example for V polarization): the
engraved polarization symbols (H or V) must coincide with the reference blind hole.
Change Polarization Procedure
1) 1st Step = internal 30° rotate
Figure 344. Coupler Polarization Change (11-38 GHz) - 1st Step execution

2) 2nd Step= cover + screws 60°( 30°+ 30°) rotate
Figure 345. Coupler Polarization Change (11-38 GHz) - 2nd Step execution
The “spigot” in the integrated antenna configuration is 30° and complete the change of polarization
(90°).
Figure 346. Coupler Polarization Change (11-38 GHz) - Screws fixing
[3] Install the RF coupler on antenna’s nose adapter.
N.B. Before inserting the RF coupler on antenna’s nose adapter, it is mandatory to put SILI-
CONE grease on the O-ring.

Figure 347. Putting silicone grease on O-ring before RF coupler insertion (11-38 GHz)
Grasp the coupler by the handle. Fasten the coupler to the support through the four locking hooks
that will be tightened onto the relative fastening brackets on the radio support. The label corresponds
to the side of the pole.
Figure 348. Installing the RF coupler to the radio support (11-38 GHz)
WARNING: verify that the indication , engraved on the coupler, is directed toward the side
pole:
[4] For each MPT-HC transceiver, take off the solar shield by unscrewing the screws placed on the solar
shield back panel.

[5] Install the MPT-HC transceivers on the RF coupler.
N.B. Before inserting each MPT-HC on RF coupler’s nose adapters, it is mandatory to put SIL-
ICONE grease on the O-rings.
Figure 349. Putting silicone grease on RF coupler’s O-ring before MPT-HC insertion (11-38 GHz)
Grasp each MPT-HC by the handle. Fasten the MPT-HC module to the support through the locking
hooks that will be tightened onto the relative fastening bracket on the coupler.
N.B. Remember to set the correct polarization on the MPT-HC to match the coupler nose
waveguide.
Figure 350. Installing the MPT-HC 1+1 on the RF coupler (11-38 GHz)
Figure below shows the final result, and indicates the position of the MAIN and PROTECTION MPT-
HC.

Figure 351. Views of MPT-HC 1+1 integrated antenna after installation (11-38 GHz)
[8] Reinstall the solar shield onto each MPT-HC transceiver by screwing on it the solar shield screws.
4.1.4.9.2 6-7-8 GHz

[3] Check or change the polarization of the RF coupler (solution A).
a) Vertical Polarization to Horizontal Polarization

The point of reference is on the position V (Vertical Polarization).
To change the polarization, perform the following operations:
1) Unscrew the three screws.
2) Turn the thin twist and to make to coincide the position H to the point of reference ”A”
3) Screw the screws.
b) Horizontal Polarization to Vertical Polarization

The point of reference is on the position H (Horizontal Polarization).
5) Turn the thin twist and to make to coincide the position V to the point of reference ”A”

Figure 352. Coupler Polarization Change (6-7-8 GHz)
[4] Check or change the polarization of the RF coupler (solution B).
2 Vertical polarization
Unscrew the screws

3 Remove the disk. 4
5 Rotate clockwise the disk on the bottom. 6 Upset the removed disk in order to show
the side with H indication.
7 Reinsert the disk by setting letter H as in the figure.
that will be tightened onto the relative fastening brackets on the radio support .The label corresponds

Figure 353. Installing the RF coupler to the radio support (6-7-8 GHz)
shield back panel.
Figure 354. Putting silicone grease on O-ring before MPT-HC insertion (6-7-8 GHz)
Grasp the MPT-HC transceiver by the handle, and fasten it to the coupler support through the four
locking hooks that will be tightened onto the relative fastening brackets on coupler.
Figure below shows the final result, and indicates the position of the MAIN and PROTECTION MPT-
HC.

Figure 355. Installing the MPT-HC 1+1 on the RF coupler (6-7-8 GHz)

4.1.4.10 1+1 MPT-HC installation (non integrated antenna)
4.1.4.10.1 11-38 GHz
[1] Install the Nose Adapter on the "Pole Mounting for Remote ODU" for MPT-HC.
[2] Install the "Pole Mounting for Remote ODU" for MPT-HC.
[3] Install the RF coupler on the nose adapter.
N.B. Before inserting the RF coupler on nose adapter, it is mandatory to put SILICONE grease
on the O-ring.
Figure 357. Putting silicone grease on O-ring before RF coupler insertion
that will be tightened onto the relative fastening brackets on the Pole Mounting.

Warning:
Lock the 4 hooks.
Figure 358. 11-38 GHz RF coupler installation (with pole mounting P/N 3DB 10137 AAXX)
shield back panel.
Figure 359. Putting silicone grease on RF coupler’s O-ring before MPT-HC insertion (11-38 GHz)
Grasp each MPT-HC by the handle. Fasten the MPT-HC module to the support through the locking

Figure below shows the final result, and indicates the MAIN MPT-HC and the PROTECTION MPT-
HC.
RF coupler
PROTECTION MAIN
MPT-HC MPT-HC
Figure 360. Installation of MPT-HC 1+1 (11-38 GHz)
[7] Connect the antenna side (flange) of the MPT-HC Pole Mounting’s nose adapter to the external
antenna, by means of the “Flextwist“ waveguide.

4.1.4.10.2 6-7-8 GHz
[2] Install the Nose Adapter on the "Pole Mounting for Remote ODU" for MPT-HC.
[3] Install the "Pole Mounting for Remote ODU" for MPT-HC.
on the O-ring.

Figure 363. 6-7-8 GHz RF coupler installation (with pole mounting P/N 3DB 10137 AAAB)
shield back panel.
Putting
silicone
grease
Figure 364. Putting silicone grease on O-ring before MPT-HC insertion (6-7-8 GHz)
Grasp the MPT-HC transceiver by the handle, and fasten it to the coupler support through the four

Figure 365. Installing the MPT-HC 1+1 on the RF coupler (7-8 GHz)
Figure below shows the final result, and indicates the MAIN and PROTECTION MPT-HC.
Figure 366. MPT-HC 1+1 installed on the RF coupler (6-7-8 GHz)
[8] Connect the antenna side (flange) of the MPT-HC Pole Mounting’s nose adapter to the external

4.1.4.11 How to pull up the cables from indoor to the MPT-HC
4.1.4.11.1 Optical fiber
1 Take the optical fiber cable of the suitable 2 Take the Hoisting grip tool.
length.
3 Insert the fiber in the hoisting grip tool. 4
5 Screw the gland body to the hoisting grip 6

until the end of stroke with a fixed spanner.
Gland body Gland nut
7 8 Fix the gland nut with the dynamometric

wrench (10N).

9 Take a cord and insert it in the hoisting grip 10 Make a knot on the cord and pull up with
tool. the cord the hoisting grip tool.
11 The overlength of the optical fiber must be

rolled up in the Cable overlength box.

4.1.4.11.2 Electrical Ethernet cable
N.B. The cable must be terminated on field.
N.B. Install the gland before terminating the cable.
1 Inser the gland on the cable: first insert the 2 Terminate the Ethernet cable with the RJ45
gland nut, then the gland seal, last the gland connector (1AB074610027) according to
body. the plug assembling instructions included
in the relevant tool provided in the Special
tool bag (3CC50098AAAA).
Gland body Gland seal Gland nut
3 Terminate the Ethernet cable acording to EIA/TIA 568B STANDARD
4 Take the terminated electrical cable and 5

protect the RJ45 with a tape.

6 7 Take a 35 cm reference on the cable.
8 Sign 1.5 cm from the reference. 9 Sign 3 cm from the reference.
10 Remove the sheath of the cable from 1.5 11 Insert the cable in the hoisting grip tool.
cm to 3 cm from the reference.

12 Insert the cable in the hoisting grip tool. 13 Screw the gland body to the hoisting grip
until the end of stroke with a fixed spanner.
Gland body
14 15
Gland nut
16 Fix the gland nut with the dynamometric 17 Take a cord and insert it in the hoisting grip
wrench (10N). tool.
18 Make a knot on the cord and pull up with

the cord the hoisting grip tool.

4.1.4.12 Cable connection to MPT-HC (11-38 GHz)
4.1.4.12.1 Electrical cable installation
1 Remove the cap on the left side. 2 Take a 35 cm reference on the cable and
put a tape as reference length.
Remove
3 Insert the cable on the hole. 4 Take the gland body, move it on the hole.
Gland
body
5 Fix the gland body until the end of stroke 6 Fix the gland nut by the hand.
and push the seal in its seat.
Gland Seal Gland Reference

nut body

7 Pull back the cable until the reference is 8 Tighten the body and then the gland nut with
visible near the gland nut. the dynamometric wrench (10 N).
9 Remove the tape from the RJ45 connector. 10 Climp the yellow boot on the cable.
Boot
11 Put the boot on the RJ45 connector. 12 Make a loop on the cable.

13 Position of the cable with loop. 14 Connect the RJ45 connector on the
MPT-HC connector and close the co-box.
15 End of cable connection.
Warning: The Power Supply connection must be made waterproof :
1) Surround the connector with the auto amalgamate tape from up to down
2) Surround the connector with the adhesive tape from up to down
3) Put tie raps on the up and the down of the connector

4.1.4.12.2 Optical fiber cable installation
1 Insert the SFP on the MPT-HC. 2 Insert the optical fiber on the hole.
3 Take the gland body and move it on the 4 Fix the gland body.
hole.
Reference
Gland
Warning: The end of the heat-shrink tube
reference must be outside the gland.
5 Tighten the gland nut with the dynamometric 6 Remove the protection caps from the fiber
wrench. connectors.

7 Take the optical conectors and ... 8 ... connect them on the MPT-HC. Close
the co-box.
9 End of optical fiber connection.
Warning: The Power Supply connection must be made waterproof :
1) Surround the connector with the auto amalgamate tape from up to down
2) Surround the connector with the adhesive tape from up to down
3) Put tie raps on the up and the down of the connector

4.1.4.12.3 Connection of the two MPT-HC in 1+1 configuration
1 Take the ODC-LC jumper. 2 Remove the cap on the right side of the co-
box. Insert in the hole the ODC-LC jumper
and tighten it until the end of stroke.
3a In case of optical cable arrange the cables 3b In case of electrical cable arrange the
as shown in the figure below. cables as shown in the figure below.
4 Remove the protection caps from the 5 Insert the optical connectors in the SFP in
optical connectors. the MPT-HC.

6 Close the co-box and repeat the same 7 Take the ODC-ODC optical cable of the suit-
operation in the second MPT-HC. able length (0.7 m / 10 m / 20 m).
8 Remove the protection cap on the ODC 9 Remove the protection cap from the ODC
cord. connector on the co-box.
10 Assemble the ODC-ODC optical cable and 11 Repeat the operation in the second MPT-
tighten it with the dedicated dynamometric HC.
wrench (1N).

4.1.4.13 Cable connection to MPT-HC (6-7-8 GHz)
4.1.4.13.1 Electrical cable installation
1 Open the co-box. 2 Take a 29 cm reference on the cable and

put a tape as reference length.
3 Remove the cap from “User” and insert the 4 Move the gland nut and tighten it with the
cable on the hole. Tighten the gland body dynamometric wrench.
with the dynamometric wrench.
User
Gland
nut
5 Insert the yellow boot on the RJ45 6 End of cable connection.

connector and insert it in the co-box.
Close the co-box.

4.1.4.13.2 Optical fiber cable installation
1 Open the co-box. 2 Insert the SFP module.
3 Remove the cap from “User” and insert the 4 Move the gland body and tighten it with the
optical fiber on the hole. dynamometric wrench.
5 Tighten the gland nut with the dynamometric 6 Remove the protection caps from the fiber
wrench. connectors, insert them in the SFP.
Close the co-box.
Warning: The reference must be outside the co-

box and the gland nut.

7 End of optical fiber connection.

4.1.4.13.3 Connection of the two MPT-HC in 1+1 configuration
1 Take the ODC-LC jumper. 2 Remove the cap from RPS in the co-box.
Insert in the hole the ODC-LC jumper and
tighten it until the end of stroke.
3 Close the co-box and repeat the same 4 Take the ODC-ODC optical cable of the suit-
operation in the second MPT-HC. able length (0.7 m / 10 m / 20 m).
5 Remove the protection cap. 6 Insert the ODC-ODC optical cable and
tighten it with the dynamometric wrench
(1 N).

7 Repeat the operation in the second MPT-
HC and connect the ODC-ODC optical
cable.

4.1.4.14 Installing the “Flextwist“ waveguide (not integrated antenna cases)
Concerning the interface between the MPT-HC output flange and the suggested antenna flange, the fol-
lowing Table 38. details for each product the standard wave guide to be used and the suggested flange
for the external antenna.
Please note that the use of 600 mm flex twist is not suggested for antennas bigger than 3ft (90 cm diam-
eter), due to mechanical reasons. The suggested way to make the RF connection is to use the elliptical
wave guide fitted with flanged connectors.
Table 38. MPT-HC Output flanges with external antenna
Range MPT-HC FLEXTWIST Suggested

(GHz) Output Antenna
Flange Flange
C.E.I. E.I.A.
6 UBR70 R70 WR137 PDR70 UDR70 PDR70
UDR84 R84 WR112 PDR84 UBR84 PBR84
7-8 or
UBR84 R84 WR112 PBR84 UBR84 PBR84
11 UBR100 R100 WR90 PBR100 UBR100 PBR100
18
26
The long twistable flexible waveguide is supplied complete with gaskets and fasteners. At one end, it has
a smooth square or rectangular flange (to be mounted on the antenna) and at the other end, a grooved
square flange designed to accommodate an O–ring seal (mounted at the MPT-HC end).

Table 39. 6-7-8GHz Flextwist waveguide
FLEXIBLE TWISTABLE WAVEGUIDE KIT
Stainless Z. flat washers

Alcatel-Lucent code
“Onduflex” springy
socket cap screws
socket cap screws

Freq. Band GHz
crinkle washers
Stainless steel
Stainless steel
HM. Hex nuts

Length mm.
Waveguide
Flanges
8 8 8 8 8
1AF02951ABAA WR137 1000 6 PDR70 UDR70
(M4x25) (M4x12) (B4) (Z4) (HM4)
8 8 8 8 8
3CC08010ABAB WR112 1000 7,05–10 PBR84 UBR84
(M4x25) (M4x12) (B4) (Z4) (HM4)
Table 40. 11-38GHz Flextwist waveguide

FLEXIBLE TWISTABLE WAVEGUIDE KIT
Stainless Z. flat washers

Alcatel-Lucent code
socket cap screws
socket cap screws
“Onduflex” springy
Freq. Band GHz
crinkle washers
Stainless steel
Stainless steel
HM. Hex nuts

Length mm.
Waveguide
Flanges
8 8 8 12 12
1AF02957ABAA WR90 1000 11 PBR100 UBR100
(M4x20) (M4x12) (B4) (Z4) (HM4)
8 8 8 12 12
3CC05751ACAA WR75 600 10 – 15,0 PBR120 UBR120
(M4x20) (M4x12) (B4) (Z4) (HM4)
8 8 8 8 8
3CC05750ACAA WR62 600 12,4 – 18 PBR140 UBR140
(M4x20) (M4x12) (B4) (Z4) (HM4)
8 8 8 8 8
3CC05749ACAA WR42 600 18 – 26,5 PBR220 UBR220
(M3x20) (M3x12) (B3) (Z3) (HM3)
8 8 8 8 8
3DB00682AAAA WR28 600 26,5 – 40 PBR320 UBR320
(M3x20) (M3x12) (B3) (Z3) (HM3)
N.B. If the FLEX–TWIST is not provided by Alcatel, the user must carefully choose the type of the
connection guide in order to limit as much as possible galvanic couples between ANTENNA/
flex–twist and flex–twist/MPT-HC contact surfaces that can induce rust. For this purpose please
note that the surfaces are:
– chromium-plated at MPT-HC output flange side
– tin-plated at flex-twist’s flange side

4.1.4.15 MPT-HC system grounding
Each MPT-HC transceiver must be individually grounded.
N.B. Neither the RF coupler, nor the antenna(s), integrated or not integrated, must be grounded.
The following items are necessary for the individual grounding of each MPT-HC transceiver:
– one MPT-HC Grounding Kit (P/N 3CC08166AAXX).

This kit corresponds to a cable (16mm2 L = 15 m) that must be cut on site and connected to the ter-
minal provided on the MPT-HC transceiver, and, on the other side, to the nearest grounding plate;
This example figure shows the grounding connector position.
MPT-HC grounding connector:

to be connected with the
grounding cable to the nearest
grounding plate
Connect all grounding cables to the nearest grounding plate, as shown in this example:

4.1.4.16 Cable Grounding
The Power Supply cable and the Ethernet electrical cable must be grounded by using the dedicated
Grounding kits.
For ground kit installation instructions refer to the guide provided with each kit.
For tower/mast installations the cables must be grounded at:
– The point where it comes on to the tower from the MPT-HC
– The point where it leaves the tower to go to the equipment building
– Not more than 25 m intervals on the tower if the height on the tower exceeds 50 m
– A point just prior to building entry
Figure 367. shows typical tower locations for cable grounding.
Note: All the cables (coax cable, Cat5e cable, fiber cable) must be fixed to the tower with the relevant ties.
At non-standard installations, such as building tops or the sides of buildings, follow the same general
guidelines but where proper grounding points are not provided these must first be installed.
MPT & antenna
MPT ODU ground wire
Cable ground
Cable supported by black cable ties at

not more than 1 m intervals.
Must not run adjacent to tower lightning
ground or electrical cables
Install additional cable grounds at not more

than 25 m intervals if the height of cable on
the tower exceeds 50 m
Cable ground Cable ground
Cable carrier Rack ground bar
ground bar
Site grounding
Figure 367. Locations for Cable Grounds

4.1.4.17 Type N connectors and Grounding kits waterproofing on the IDU/ODU cables
For installation on the type N connectors and grounding kits please refer to the installation notice provided
with the connector and the grounding kit.
IMPORTANT:
To prevent potential risks of dysfunction it is recommended and a particular attention will be carried in the
realization of the waterproofing of connectings (see following page).
For the holding in the bad weather, do not forget the waterproofing at the end of the operation with the
Self auto-amalgamating + UV protection vinyl tape by necklaces Colson / Tie raps in every extremity.
For the assembly between the cable, grounding kit and ODU realized outside, it is recommended to use
the Self auto-amalgamating (several turns) to assure the waterproofing. Then to cover the set by the UV
protection vinyl tape to avoid the unsticking of the self-amalgamating and ended with a necklace Colson
/ Tie raps.
4.1.4.17.1 Example of Connector N waterproofing
4.1.4.17.2 Example of N Connector & Waterproofing
The principle of waterproofing given above is valid for the connections cable / ODU and for the grounding
kits of the coaxial cable. It is recommended to make this waterproofing by "dry" weather, to avoid locking
the humidity into the system.
Surround the connector with the auto amalgamate Surround the connector with the adhesive UV
tape from up to down tape from up to down

Put necklace Colson / tie raps on the up and the
down of the connector
4.1.4.17.3 Example of Grounding Kit & Waterproofing
In every kit for Power Supply cable and in every kit for Ethernet electrical cable is joined a detailed assem-
bling instruction.
Make then the Installation of the kit on the coaxial cable by not forgetting the waterproofing as example
below.
Example of realization. Detail of the waterproofing of the kit.
Metal contact
Install
grounding kit

Thighten with allen Waterproofing with
key 8 mm Almagamating + UV protection vinyl tape +
Necklace Colson / Tie rap

4.1.5 MPT-HC V2 Installation
The MPT-HC installation section is divided in:
– Types of MPT-HC V2 (par. 4.1.5.1 on page 580)
– MPT-HC V2 operative information (par. 4.1.5.3 on page 584)
– How to change polarization in the MPT-HC V2 (par. 4.1.5.4 on page 589)
– 1+0 MPT-HC V2 installation (integrated antenna) (par. 4.1.5.8 on page 590)
– 1+0 MPT-HC V2 installation (non integrated antenna) (par. 4.1.5.9 on page 590)
– 1+1 MPT-HC V2 installation (integrated antenna) (par. 4.1.5.10 on page 590)
– 1+1 MPT-HC V2 installation (non integrated antenna) (par. 4.1.5.11 on page 590)
– Cable connections (MPT-HC V2 to MSS) (par. 4.1.5.12 on page 590)
– MPT-HC V2 system grounding (par. 4.1.5.14 on page 591)

4.1.5.1 Types of MPT-HC V2
The MPT-HC V2 consists of one or two cabinets including the Ethernet interface + modem + RF trans-
ceiver + branching of a channel.
where the branching (diplexer) is internal to the MPT-HC V2 cabinet; this type of MPT-HC V2 is iden-
tified by one Logistical Item only;
the shifter customization (7 GHz and 8 GHz), where MPT-HC V2 is composed by two independent
(containing the RF section); each of this type of MPT-HC V2 is identified by two Logistical Items,
one for the BRANCHING assembly and another for the RF TRANSCEIVER assembly. To read the
Figure 368. Views of MPT-HC V2 with embedded diplexer (6 GHz and 11-38 GHz)

4.1.5.2 External module to be installed
The MPT-HC V2 is delivered from the factory in one packing-case in the basic configuration (without any
external module). The external module (RPS or XPIC+RPS) is delivered in another packing-case.
The external module must be installed in field on the MPT-HC V2.
Note: Before installing an external module (XPIC module or XPIC-RPS module) on a MPT-HC V2,
the corresponding MPT-HC V2 must be switched OFF. Switch ON can be done once the module
has been properly screwed.
To install it follow the following procedure:
1) Disinstall the solar shield by unlocking the 3 screws.
2) Unlock the 4 screws.
3) Remove the basic cover
Unlock the screws
Remove the cover
4) Remove the cap.
Remove the cap

5) Withdraw the external module from the packing-case (RPS: refer to Figure 369. or XPIC+RPS:
refer to Figure 370.) and remove the cap.
Top view
Bottom view
Remove the cap
Figure 369. RPS module
Top view
Bottom view
Remove the cap
Figure 370. XPIC + RPS module

6) Install the module on the MPT-HC V2 and lock the 4 screws. Pay attenation to the correct posi-
tion of the screws, as shown in Figure 371. The slot of the screw must be aligned with the indi-
cation on the MPT-HC V2.
Figure 371. External module installed
Indication
Figure 372. Correct screw position
7) Install the solar-shield taking into account the polarization to be used.

4.1.5.3 MPT-HC V2 operative information
– MPT-HC V2 with embedded or external diplexer herebelow
– MPT-HC V2 with external diplexer (additional information) on page 586
4.1.5.3.1 Operative information on MPT-HC V2 with embedded or external diplexer
Figure 373. on page 585 (for MPT-HC V2 with embedded diplexer) and Figure 374. on page 586 (for MPT-
HC V2 with external diplexer) show MPT-HC V2 views and access points.
The external interfaces are listed in Table 41. below with the corresponding connectors.
Table 41. MPT-HC V2 external interfaces

and
Figure 374.
(1) RF interface for connection of antenna or coupler Waveguide Table 42. herebelow
(2) Connector for power supply cable or for PFoE RJ45 + R2CT
(Power Supply + Ethernet Traffic) cable
(3) Optical Ethernet connection LC + Q-XCO
(4) Connection to a second MPT-HC V2 in 1+1 LC + Q-XCO
(5) XPIC connector Not used in the

current release

FREQUENCY GHz -> 6 7 8 11 13-15 18-26 38

(1) (A) MPT-HC V2 basic
(A) (A)
(3) (2)
(A)
MPT-HC V2 equipped with RPS module MPT-HC V2 equipped with XPIC-RPS module
(5)
(4)
(4)
(3) (2) (3) (2)
(A) Locking hooks (4) to fix/unfix MPT-HC V2 assembly to antenna or coupler
WARNING: A waterproofness tape is glued on the waveguide of the MPT-HC V2. It must never
be removed.
Figure 373. Views of MPT-HC V2 with embedded diplexer (6 GHz and 11-38 GHz)

(1)
(A)
MPT-HC V2 basic (B) (B)
(A) (A)
(3) (2) (B) (B)

(A)
MPT-HC V2 equipped with RPS module MPT-HC V2 equipped with XPIC-RPS module
(5)
(4)
(4)
(3) (2) (3) (2)
WARNING: A waterproofness tape is glued on the waveguide of the MPT-HC V2. It must never
be removed.
Figure 374. Views of MPT-HC V2 with external diplexer (7 GHz and 8 GHz)
4.1.5.3.2 Additional operative information on MPT-HC V2 with external diplexer
Refer to paragraph 4.1.4.2.2 on page 524.

4.1.5.3.3 Labels affixed on the MPT-HC V2
a) The label depicted in Figure 375. below is affixed externally to all types of MPT-HC V2 and MPT-
HC V2 TRANSCEIVER boxes;
b) Only for MPT-HC V2 with external diplexers, an additional label, depicted in Figure 376. on page
588, is placed on the branching assembly.

Figure 375. Label affixed on the MPT-HC V2 and MPT-HC V2 TRANSCEIVER box


branching assembly.
byCraft Terminal;
boxes coupling.
Figure 376. Label affixed inside the MPT-HC V2 BRANCHING box

4.1.5.4 How to change polarization in the MPT-HC V2
Refer to paragraph 4.1.4.3 on page 529.
WARNING: Re-use of already installed Pole mounting 3CC10752AAAA and couplers in 1+1
configuration
The 2 already installed “MELODY” or “AWY” ODU can be replaced with two MPT-HC V2
after having removed the pre-cut part of the solar-shield which faces the pole.
It concerns 13 GHz to 38 GHz frequency range.
Pre-cut part to be Pre-cut part to be

removed with a cutter in removed with a cutter in
case of 1+1 configuration case of 1+1 configuration
on the Left side. on the Right side.
Right pre-cut part removed
Left pre-cut part removed

4.1.5.8 1+0 MPT-HC V2 installation (integrated antenna)
4.1.5.9 1+0 MPT-HC V2 installation (non integrated antenna)
4.1.5.10 1+1 MPT-HC V2 installation (integrated antenna)
4.1.5.11 1+1 MPT-HC V2 installation (non integrated antenna)
4.1.5.12 Cable connections (MPT-HC V2 to MSS)
4.1.5.12.1 Electrical Ethernet cable
If the PFoE has been implemented, only one cable interconnects the MPT-HC V2 with the MSS. Refer
to paragraph 4.1.6.11 on page 623.
4.1.5.12.2 Optical cable connection
An optical cable must be used, if the PFoE has not been implemented.
The cable is shown in Figure 377. The cable is a preassembled cable available in different lengths (refer
to paragraph 4.1.10.7 on page 637).
Figure 377. Q-XCO to Q-XCO Fiber cord
To pull-up the cable take a cord and insert it in the slot of the cable cap. Make a knot on the cord and pull-
up the cable.
Remove the cap and connect the connector to the Q-XCO connector in the MPT-HC V2.

4.1.5.12.3 Power supply cable connection
The power supply cable is a coaxial cable, which is used only if the optical cable is used to transport the
Ethernet traffic. Two types of coaxial cables are available according to the length (less than 200 m or more
than 200 m).
The coaxial cable must be connected to:
– IDU-side to the MPT Access unit;
– ODU-side to the 1 m cord adapter (from N female to RJ45 plug). The RJ45 must be then connected
to the relevant connector on the MPT-HC V2.
4.1.5.12.4 Cable connection in 1+1 configuration
In 1+1 configuration the two MPT-HC V2 must be interconnected by using a preassembled jumper (Figure
378.). The jumper is available in different lengths (refer to paragraph 4.1.10.7 on page 637).
Figure 378. RPS Q-XCO to Q-XCO optical jumper
4.1.5.14 MPT-HC V2 system grounding

4.1.6 MPT-MC Installation
The MPT-MC installation section is divided in:
– Types of MPT-MC (par. 4.1.6.1 on page 593)
– MPT-MC operative information (par. 4.1.6.2 on page 594)
– How to change polarization in the MPT-MC (par. 4.1.6.3 on page 601)
– 1+0 MPT-MC installation (integrated antenna) - all frequencies (par. 4.1.6.7 on page 603)
– 1+0 MPT-MC installation (non integrated antenna) - all frequencies (par. 4.1.6.8 on page 606)
– 1+1 MPT-MC installation (integrated antenna) (par. 4.1.6.9 on page 608)
– 1+1 MPT-MC installation (non integrated antenna) (par. 4.1.6.10 on page 617)
– How to terminate and to connect the Ethernet cable (MPT side) (par. 4.1.6.11 on page 623)
– MPT-MC system grounding (par. 4.1.6.13 on page 627)

4.1.6.1 Types of MPT-MC
The MPT-MC consists of one or two cabinets including the Ethernet interface + modem + RF transceiver
+ branching of a channel.
where the branching (diplexer) is internal to the MPT-MC cabinet; this type of MPT-MC is identified
by one Logistical Item only;
the shifter customization (7 GHz and 8 GHz), shown in Figure 380., where MPT-MC is composed
by two independent units: the BRANCHING assembly (containing the diplexer) and the RF TRANS-
CEIVER assembly (containing the RF section); each of this type of MPT-MC is identified by two
Logistical Items, one for the BRANCHING assembly and another for the RF TRANSCEIVER
assembly. To read the BRANCHING assembly identification label it is necessary to separate the
BRANCHING assembly from the RF TRANSCEIVER assembly.
TRANSCEIVER + BRANCHING
Figure 379. Views of MPT-MC with embedded diplexer (6 and 11-38 GHz)

Figure 380. Views of MPT-MC with external diplexer (7 GHz and 8 GHz)
4.1.6.2 MPT-MC operative information
– MPT-MC with embedded or external diplexer herebelow
– MPT-MC with external diplexer (additional information) on page 596
4.1.6.2.1 Operative information on MPT-MC with embedded or external diplexer
Figure 381. on page 595 (for MPT-MC with embedded diplexer) and Figure 382. on page 595 (for MPT-
MC with external diplexer) show MPT-MC views and access points.
The external interfaces are listed in Table 43. below, with the corresponding connector.
Table 43. MPT-MC external interfaces

and
Figure 382.
(1) RF interface for connection of antenna or coupler waveguide Table 44. herebelow
(2) Ethernet electrical cable R2CT

FREQUENCY GHz -> 6 7 8 11 13-15 18-26 38

(1) (A)
(A) (A)
(2)
(A)
(A) Locking hooks (4) to fix/unfix MPT-MC assembly to antenna or coupler
WARNING: A waterproofness tape is glued on the waveguide of the MPT-MC. It must never be
removed.
Figure 381. Views of MPT-MC with embedded diplexer (6 and 11-38 GHz)
(1) (A)
(B) (B)
(A) (A)
(2) (B) (B)

(A)
WARNING: A waterproofness tape is glued on the waveguide of the MPT-MC. It must never be
removed.
Figure 382. Views of MPT-MC with external diplexer (7 GHz and 8 GHz)

4.1.6.2.2 Additional operative information on MPT-MC with external diplexer
4.1.6.2.2.1 MPT-MC composition
As shown in Figure 383., the MPT-MC assembly is made up of two boxes, one for diplexer system
(BRANCHING) and the other for the all other active functions (TRANSCEIVER) connected together to
form the MPT-MC.
An O-RING present in the TRANSCEIVER box guarantees the MPT-MC assembly waterproofness.
N.B. This is a conductive O-RING and must be left dry. Do not wet it with silicon grease (silicon
grease must be used only on O-ring between MPT-MC and antenna).
BRANCHING TRANSCEIVER
WARNING 1 WARNING 2
Figure 383. Composition of MPT-MC with external diplexer
WARNING 1: A waterproofness tape is glued on the waveguide of the MPT-MC. It must never be removed.
WARNING 2: This gasket must never be removed.
The TRANSCEIVER box performs all the functions, but does not include the diplexer system.
The BRANCHING box provides the interface between the pole mounting/antenna and the TRANS-
CEIVER.
The favorite solution foresees the possibility to change in field a spare part TRANSCEIVER without dis-
connecting the BRANCHING box from the pole mounting/antenna. The TRANSCEIVER and BRANCH-
ING boxes fixing and unfixing are obtained through the four levers.

4.1.6.2.2.2 TRANSCEIVER and BRANCHING boxes coupling
Figure 384. below shows the TRANSCEIVER and BRANCHING boxes coupling surfaces:
– (A) BRANCHING box label informative content

described in Figure 387. on page 600
– (B) (HIGH FREQ) and (C) (LOW FREQ) RF interfaces on BRANCHING box
– (D) (TX) and (E) (RX) RF interfaces on TRANSCEIVER box
The TRANSCEIVER and BRANCHING boxes can be coupled in two alternative ways (180°-rotated with
respect to each other):
– BRANCHING box (B) (HIGH FREQ) coupled to TRANSCEIVER box’s (D) (TX)
in this case the TX part of the transceiver uses the HIGH frequency range of the Shifter set by the
corresponding LOW frequency range;
– BRANCHING box (C) (LOW FREQ) coupled to TRANSCEIVER box’s (D) (TX)
in this case the TX part of the transceiver uses the LOW frequency range of the Shifter set by the
corresponding HIGH frequency range.
(D)
(A) (B)
(C)
(E)
Figure 384. MPT-MC TRANSCEIVER and BRANCHING boxes coupling surfaces
N.B. There is only one possible way to couple the BRANCHING box and the TRANSCEIVER box:
there is a mistake-proofing put by the factory on the TRANSCEIVER box, whose position
depends on the type of transceiver (low or high band, as shown in Figure 385.) to ensure that
the association with the BRANCHING box is always the right one.

Hole
Mistake-proofing
Figure 385. 7-8 GHz MPT-MC BRANCHING box mistake-proofing

4.1.6.2.3 Labels affixed on the MPT-MC
a) The label depicted in Figure 386. below is affixed externally to all types of MPT-MC and MPT-MC
TRANSCEIVER boxes;
b) Only for MPT-MC with external diplexers, an additional label, depicted in Figure 387. on page 600,
is placed on the branching assembly.

Initial SW/ICS (shown numbers as examples) P/N and ICS of the software loaded in factory
PN/ICS (shown numbers as examples) Factory P/N + ICS
C Factory P/N + ICS bar code 128
Figure 386. Label affixed on the MPT-MC and MPT-MC TRANSCEIVER box


branching assembly.
byCraft Terminal;
boxes coupling.
Figure 387. Label affixed inside the MPT-MC BRANCHING box

4.1.6.3 How to change polarization in the MPT-MC
4.1.6.3.1 6 and 11-38 GHz MPT-MC
Note
The polarization must be changed to match the antenna polarization and the coupler nose waveguide.
1 Remove the plastic protection cover from 2 Change the polarization of the MPT-MC, if
the MPT-MC. required (default: vertical polarization).
Protection cover
Polarization
reference
Unscrew the 2 screws

and rotate by 45°
3 Horizontal polarization.
Polarization
reference

4.1.6.3.2 7-8 GHz MPT-MC
These MPT-MC have fixed polarization (vertical polarization). To change the polarization it is necessary
to change the antenna polarization and to install the MPT-MC 90° rotated.
1 Example of vertical polarization (left offset). 2 Example of horizontal polarization

(left offset).
3 Example of vertical polarization (right 4 Example of horizontal polarization

offset). (right offset).

4.1.6.7 1+0 MPT-MC installation (integrated antenna) - all frequencies
[1] Check/Set the coupling between the TRANSCEIVER and BRANCHING boxes (only for MPT-MC

[3] Check or change the polarization on the Antenna nose.

To change the polarization, follow the instructions supplied with each antenna. Figure below shows
an example.
N.B. The antennas are normally supplied with vertical polarization.
Figure 388. Example of antenna polarization change (“1+0” MPT-MC integrated antenna)
[4] Take off the solar shield from the MPT-MC transceiver by unscrewing the screws placed on the solar
shield back panel.
[5] Install the MPT-MC on the Antenna nose adapter.
N.B. Before inserting the MPT-MC on nose adapter, it is mandatory to put SILICONE grease
on the O-ring.

Figure 389. Putting silicone grease on O-ring before MPT-MC insertion
1) Grasp the MPT-MC module by the handle.
2) Open the four looking hooks (1) arranged on the four walls of the MPT-MC unit.
3) For 7-8 GHz MPT-MC only rotate the MPT-MC depending on the horizontal or vertical polar-
ization, and slide it on the nose adapter.
4) Secure the MPT-MC module through the four hooks (1) on the relative brackets (2).
(2) Bracket
(1) Hook
Figure 390. MPT-MC 1+0 installation for integrated antenna (6 GHz and 11-38 GHz)
N.B. For 6 GHz and 11-38 GHz MPT-MC remember to set first the correct polarization.

(1) Hook
(2) Bracket
Figure 391. MPT-MC 1+0 installation for integrated antenna (7-8 GHz: vertical polarization)
(1) Hook
(2) Bracket
Figure 392. MPT-MC 1+0 installation for integrated antenna (7-8 GHz: horizontal polarization)
REMINDER: The MPT-MC/antenna assembly requires no additional seal on the SHF flanges; the
two ends are smooth. The O-ring seal around the male “nose” provides sealing.
[6] Ground the MPT-MC system.
[8] Reinstall the solar shield onto the MPT-MC transceiver by screwing on it the solar shield screws.

4.1.6.8 1+0 MPT-MC installation (non integrated antenna) - all frequencies
[2] Install the Nose Adapter on the “Pole Mounting for Remote ODU”.
[3] Install the “Pole Mounting for Remote ODU”.

[4] Take off the solar shield from the MPT-MC transceiver by unscrewing the screws placed on the solar
shield back panel.
[5] Install the MPT-MC.
N.B. Before inserting the MPT-MC on nose adapter, it is mandatory to put SILICONE grease
on the O-ring.
Figure 394. Putting silicone grease on O-ring before MPT-MC insertion
1) Grasp the MPT-MC module by the handle. Open the four looking hooks arranged on the four
walls of the MPT-MC unit.
2) Position the Pole mounting support on the pole side as shown in the plant documentation.

3) Position the MPT-MC and slide it on the nose adapter.
4) Secure the MPT-MC module through the four hooks onto the relative brackets.
Figure 395. MPT-MC 1+0 installation for not integrated antenna (with pole mounting
P/N 3DB 10137 AAAB)
[7] Connect the antenna side (flange) of the Pole Mounting’s nose adapter to the external antenna, by
means of the “Flextwist“ waveguide.
[10] Reinstall the solar shield onto the MPT-MC transceiver by screwing on it the solar shield screws.

4.1.6.9 1+1 MPT-MC installation (integrated antenna)
4.1.6.9.1 6 GHz and 11-38 GHz

[2] Check or change the polarization of the RF coupler.

The axial adaptation between H polarization to V polarization (and viceversa) is a mechanical/elec-
trical adjustment. Every mechanical “STEP” is a 30° adjustment.
Figure 396. Coupler Polarization Change (6 GHz and 11-38 GHz) - 1st Step and 2nd step
The final result must be as shown in Figure 346. on page 541 (example for V polarization): the
engraved polarization symbols (H or V) must coincide with the reference blind hole.
Change Polarization Procedure
1) 1st Step = internal 30° rotate
Figure 397. Coupler Polarization Change (6 GHz and 11-38 GHz) - 1st Step execution

2) 2nd Step= cover + screws 60°( 30°+ 30°) rotate
Figure 398. Coupler Polarization Change (6 GHz and 11-38 GHz) - 2nd Step execution
The “spigot” in the integrated antenna configuration is 30° and complete the change of polarization
(90°).
Figure 399. Coupler Polarization Change (6 GHz and 11-38 GHz) - Screws fixing

Figure 400. Putting silicone grease on O-ring before RF coupler insertion (6 GHz and 11-38 GHz)
that will be tightened onto the relative fastening brackets on the radio support. The label corresponds
Figure 401. Installing the RF coupler to the radio support (6 GHz and 11-38 GHz)
WARNING: verify that the indication , engraved on the coupler, is directed toward the side
pole:
[4] For each MPT-MC transceiver, take off the solar shield by unscrewing the screws placed on the solar
shield back panel.

[5] Install the MPT-MC transceivers on the RF coupler.
N.B. Before inserting each MPT-MC on RF coupler’s nose adapters, it is mandatory to put SIL-
Figure 402. Putting silicone grease on RF coupler’s O-ring before MPT-MC insertion (6 GHz and
11-38 GHz)
Grasp each MPT-MC by the handle. Fasten the MPT-MC module to the support through the locking
Warning: Remember to set the correct polarization on the MPT-MC to match the coupler nose
waveguide.
Warning: For the Horizontal polarization keep the Vertical polarization on the MPT-MC, but rotate
and install the MPT-MC on the coupler in order to match the coupler waveguide, as shown
in Figure 403.
The position of the PROTECTION MPT-MC is on the left side (as shown in Figure 403.).
The position of the MAIN MPT-MC is on the right side (as shown in Figure 404.).
Fastening Locking
brackets hooks
Figure 403. Installing the MAIN MPT-MC 1+1 on the RF coupler (6 GHz and 11-38 GHz)

Fastening Locking
brackets hooks
Figure 404. Installing the PROTECTION MPT-MC 1+1 on the RF coupler (6 GHz and 11-38 GHz)
[8] Reinstall the solar shield onto each MPT-MC transceiver by screwing on it the solar shield screws.

4.1.6.9.2 7-8 GHz

[3] Check or change the polarization of the RF coupler (solution A).
a) Vertical Polarization to Horizontal Polarization

The point of reference is on the position V (Vertical Polarization).
8) Turn the thin twist and to make to coincide the position H to the point of reference ”A”
b) Horizontal Polarization to Vertical Polarization

The point of reference is on the position H (Horizontal Polarization).
11) Turn the thin twist and to make to coincide the position V to the point of reference ”A”
Figure 405. Coupler Polarization Change (7-8 GHz)

[4] Check or change the polarization of the RF coupler (solution B).
2 Vertical polarization
Unscrew the screws
3 Remove the disk. 4
5 Rotate clockwise the disk on the bottom. 6 Upset the removed disk in order to show
the side with H indication.

7 Reinsert the disk by setting letter H as in the figure.
that will be tightened onto the relative fastening brackets on the radio support .The label corresponds
Figure 406. Installing the RF coupler to the radio support (7-8 GHz)
shield back panel.

Figure 407. Putting silicone grease on O-ring before MPT-MC insertion (7-8 GHz)
Grasp the MPT-MC transceiver by the handle, and fasten it to the coupler support through the four
The figure below shows the position of the MAIN MPT-MC. The PROTECTION MPT-MC must be
installed on the upper side.
MAIN
MPT-MC
Figure 408. Installing the MPT-MC 1+1 on the RF coupler (7-8 GHz)

4.1.6.10 1+1 MPT-MC installation (non integrated antenna)
4.1.6.10.1 6 GHz and 11-38 GHz
[1] Install the Nose Adapter on the "Pole Mounting for Remote ODU" for MPT-MC.
[2] Install the "Pole Mounting for Remote ODU" for MPT-MC.
on the O-ring.

Warning:
Lock the 4 hooks.
Figure 411. 6 GHz and 11-38 GHz RF coupler installation (with pole mounting P/
N 3DB 10137 AAXX)
shield back panel.
Figure 412. Putting silicone grease on RF coupler’s O-ring before MPT-MC insertion (6 GHz and
11-38 GHz)

Grasp each MPT-MC by the handle. Fasten the MPT-MC module to the support through the locking
The figure below shows the position of the MAIN MPT-MC. The PROTECTION MPT-MC must be
installed on the left side.
RF coupler
MAIN
MPT-MC
Figure 413. Installation of MPT-MC 1+1 (6 GHz and 11-38 GHz)
[7] Connect the antenna side (flange) of the MPT-MC Pole Mounting’s nose adapter to the external

4.1.6.10.2 7-8 GHz
[2] Install the Nose Adapter on the "Pole Mounting for Remote ODU" for MPT-MC.
[3] Install the "Pole Mounting for Remote ODU" for MPT-MC.
on the O-ring.

Figure 416. 7-8 GHz RF coupler installation (with pole mounting P/N 3DB 10137 AAAB)
shield back panel.
Putting
silicone
grease
Figure 417. Putting silicone grease on O-ring before MPT-MC insertion (7-8 GHz)
Grasp the MPT-MC transceiver by the handle, and fasten it to the coupler support through the four
The figure below shows the position of the PROTECTION MPT-MC. The MAIN MPT-MC must be
installed on the lower side.

PROTECTION
MPT-MC
RF
Pole mounting coupler
(not integrated
antenna)
Figure 418. MPT-MC 1+1 installed on the RF coupler (7-8 GHz)
[8] Connect the antenna side (flange) of the MPT-MC Pole Mounting’s nose adapter to the external

4.1.6.11 How to terminate and to connect the Ethernet cable (MPT side)
To terminate the cable the Plug kit R2CT must be used.
The kit is made up of 10 items as shown in Figure 420.
Figure 419. Plug kit R2CT
Figure 420. Plug kit R2CT items
Note: The boot delivered with the RJ45 connector must not be used together with the R2CT.

4.1.6.11.1 Mating sequence instructions
1 Turn and remove the protection cap. 2 Unscrew partially the nut spiral.
3 Pass the cable through the mini short kit plug and crimp the RJ45 plug according to the standard
procedure. The boot of the connector must not be mounted.
4 Insert the RJ45 plug inside the unlocking 5 Pull the cable and insert the unlocking clip
clip (keep attention to have the latches together with the RJ45 plug inside the body,
mechanisms on the same side ) the latches being aligned with the body bayonet
pin. Place the body arm on the left side.

6 If you need to hoist the assembly, pull the coupling nut so as to cover the plug body and put back
the protection cap on
7 Tighten the nut spiral with a 21 mm wrench with a torque of 3N.m mini and 3,5 maxi. The cable
is now fixed with the plug and ready to be pulled.
8 Install the cable then unscrew partially the nut spiral and remove the protection cap to connect
to the receptacle
9 Align the two marks on the plug body and 10 Connect the RJ45 plug to its socket by
the receptacle, insert and rotate clockwise pushing the cable.
the plug body into the receptacle

11 Push and rotate clockwise the coupling nut 12 Secure the assembly by screwing the nut
until secured onto the receptacle spiral with a 21mm wrench with a torque of
3 N.m mini and 3,5 N.m maxi
4.1.6.11.2 Unmating sequence instructions
1 Unscrew the nut spiral via 21 mm adapted 2 Rotate and unlock the coupling nut.
wrench.
3 Engage the RJ45 unlocking clip forward 4 Press on the unlocking clip latch.
until front stop.

5 Pull the clip and the cable rearward to 6 Rotate and disconnect the R2CT plug body.
disconnect the RJ45 plug.
4.1.6.13 MPT-MC system grounding

4.1.7 DC Extractor
With the DC Extractor, to be installed close to the MPT-HC, the interconnection between the MSS and the
MPT-HC can be made with a single electrical Ethernet cable by using the “Power Feed over Ethernet”
solution (Ethernet traffic and Power Supply on the same cable). The DC Extractor then separates the
Power Supply from the Ethernet traffic, which are separately sent to the MPT-HC.
The two cables, interconnecting the DC Extractor to the MPT-HC (the Power Supply cable to be connected
to the DC Out connector of the DC Extractor and Ethernet cable to be connected to the Data Out con-
nector of the DC Extractor), are provided, already terminated (2 m long), with the DC Extractor itself.
To prepare and to terminate the “Ethernet data + Power Supply” cable (to be connected to MSS and to
the DC+Data In connector of the DC Extractor) follow the instructions given in para. 4.1.6.11 on page 623.
The R2CT connector used to terminate the cable (DC Extractor side) is provided with the DC Extractor.
1 Install the DC Extractor on the pole close to 2 Connect the DC Extractor to the ground by
the MPT-HC. using the 6 mm2 grounding cable provided
with the DC Extractor.
3 Connect the 3 cables (2 cables to the MPT- 4 The final installation is shown in the figure.
HC and 1 cable to the MSS).

4.1.8 Nose Adapter for MPT-HC/V2 and MPT-MC
3DB01465AAAA 6 GHz Nose Adapter (for Not Integrated Antenna)
3DB01459AAAA 7/8 GHz Nose Adapter (for Not Integrated Antenna)
3CC50125AAXX 11 GHz Nose Adapter (for Not Integrated Antenna)
1AB146090003 13 GHz Nose Adapter (for Not Integrated Antenna)
1AB146090001 15 GHz Nose Adapter (for Not Integrated Antenna)
1AB146090002 18/23/25 Nose Adapter (for Not Integrated Antenna)
3DB02082AAXX 28/38 Nose Adapter (for Not Integrated Antenna)
4.1.9 Flextwists for MPT-HC/V2 and MPT-MC
1AF02951ABAA 6 GHz flextwist L = 1m (PDR-UDR)
1AF11977AAAA 7/8 GHz flextwist WR112 L = 1m (PDR84/UBR84)
3CC05751ACAA 11 GHz flextwist L = 0.6m
3CC05749ACAA 18/23/25 GHz flextwist L = 0.6m
3DB00682AAXX 28/38 GHz flextwist L = 0.6m

4.1.10 Indoor Installation
This section includes:
– Indoor accessories (par. 4.1.10.1 on page 630)
– Indoor cables (par. 4.1.10.2 on page 631)
– Optical splitters for STM-1 signal and EoSDH (SFP for port #5 and #6 of Core-E unit) (par. 4.1.10.3
on page 634)
– Splitter for 2xE1 SFP (SFP for port #5 and #6 of Core-E unit) (par. 4.1.10.4 on page 634)
– Accessories and cables for ODU300 connections (par. 4.1.10.5 on page 634)
– Accessories and cables for MPT-HC connections (par. 4.1.10.6 on page 635)
– Accessories and cables for MPT-HC V2 connections (par. 4.1.10.7 on page 637)
– Accessories and cables for MPT-MC connections (par. 4.1.10.8 on page 639)
– Distributors (par. 4.1.10.9 on page 640)
– MSS cards (par. 4.1.10.10 on page 641)
– Ethernet Electrical Cables (par. 4.1.10.11 on page 643)
– Ethernet Optical Cables (par. 4.1.10.12 on page 643)
– Installing the Indoor section (par. 4.1.10.13 on page 644)
– Type of Indoor configurations (par. 4.1.10.14 on page 646)
– Connectors on the front panel of the 32E1 PDH card and 16 E1 ASAP card (68 Pin SCSI Functions)
(par. 4.1.10.15 on page 673)
4.1.10.1 Indoor accessories
1AD137820001 TRU: Power Distribution with 1 Input 48VDC and 6 breakers 16A
1AD137830001 TRU: Power Distribution with 1 Input 48VDC and 12 breakers 16A
3CC50042AAAA ETSI Rack mounting kit (valid for TRU 1AD137820001, TRU 1AD137830001,
support 19" module 120 ohm 3CC07810AAAA)
3CC50027AAAA IDU wall mounting kit (10U)
3DB16102AAAA Panel E1 protection 120 ohm
3DB16151AAAA DIN rack kit for Panel distributor 120 ohm
3DB16152AAAA ETSI rack kit for Panel distributor 75/120 ohm
3CC07810AAAA 3U Distributor subrack for 120 ohm EMC
3CC08061AAAA Connector support 1.5./5.6 75 ohm (Panel 1U)

3DB16104AAAA Panel E1 protection 75 ohm 1.0/2.3
3CC08061ABAA Connector support BNC 75 ohm (Panel 1U)
1AD114560001 Laborack (19" rack)
3DB04656AAAA ETSI rack (H2200 21" rack)
3DB18171ABAA DIN Bracket
3DB18159ABAA ETSI bracket
3CC13424AAAA Rack grounding kit
3CC13423AAAA Subrack grounding kit (includes the yellow/green cable)
3CC06503AAAA Consumable kit
3DB18181AAAA IDU kit subrack (brackets 21" kit)
1AF15185AAAA IP Phone
3CC50065AAAA Adaptor bracket kit 1U ETSI (valid for 3CC08062AAAA, 3CC08061AAAA,

3CC08061ABAA)
4.1.10.2 Indoor cables
1AC041800001 24V DC 3G power supply cable (2x16mm2) (from Station battery to TRU)
3DB18271AAAB TRU-MSS power-cable supply connection 2x4mm2 unshielded (L = 4m)
3CC13423AAAA MSS grounding Kit
3DB18205AAAA QMA (male) - N (female) RF cable (from Radio Access card to bracket)
(L = 0.35m)
3DB18205ABXX QMA (male) - N (female) RF cable (L = 2m)
3CC52133AAAA SCSI 68pin - blue block L = 1.1m
3CC52118AAAA SCSI 68-SCSI 68 pin to pin
3CC07658AFAB Cable 8XE1 IDU-DISTRIBUTOR 120 ohm L = 1m 45° (37 pin)
3CC07885AFAA Cable 8XE1 IDU-DISTRIBUTOR 75 ohm 1.5/5.6 L = 1m 45° (37 pin)
3CC07759AFAA Cable 8XE1 IDU-DISTRIBUTOR 75 ohm BNC L = 1m 45° (37 pin)
3CC52157AAAA 2xSCSI, 68 pin - 4 Compax blue blocks (120 ohm) L = 1.1 m
3CC52134AAAA Adapter cord from 1SCSI68 male to 2DB37 female
3DB18204AAAA 1.0/2.3-1.0/2.3 Synchronization (2.048-5-10 MHz) protection

3DB10109AAAA Cord 1.0/2.3 M straight L = 15 m (for synch. distribution)
3CC52138AAAA Cord 1.0/2.3 M 90° M90° L = 5m (for synch. distribution)
3DB01516AAXX Cord 1.0/2.3 M 90° M90° L = 1.6m (for synch. distribution)
3CC52117AAAA SCSI 68pin - FW L = 30m (for the cable colors refer to Figure 421. and Table
45.)
3CC52117ABAA SCSI 68pin - FW L = 15m (for the cable colors refer to Figure 421. and Table
45.)
3DB10003AAXX Cable 8xE1 IDU-DISTRIBUTOR 75 ohm coax no connectors L = 15m (37 pin)
3DB06371ABAA SUB D 37 pin - FW L = 20m 45°
3CC52015AAXX Cable, Trib, E1, RJ45 to wire-wrap L = 5m
3CC52020AAXX RJ45 to RJ45 E1 cross-over cable
3CC52150AAAA SCSI-SCSI cross-cable L = 1.6m
3CC52150ABAA SCSI-SCSI cross-cable L = 6.4m
Figure 421. SCSI 68 male connector
Table 45. SCSI 68 pins FW cable colors

Pair No. Signal Pin # Wire colour Pin # Wire colour
GND 1 35
1 TTIP 2 White 36 Blue
1 RTIP 3 White 37 Blue
2 TTIP 4 White 38 Orange
2 RTIP 5 White 39 Orange
3 TTIP 6 White 40 Green
3 RTIP 7 White 41 Green
4 TTIP 8 White 42 Brown

4 RTIP 9 White 43 Brown
5 TTIP 10 White 44 Grey
5 RTIP 11 White 45 Grey
6 TTIP 12 Yellow 46 Blue
6 RTIP 13 Yellow 47 Blue
7 TTIP 14 Yellow 48 Orange
7 RTIP 15 Yellow 49 Orange
8 TTIP 16 Yellow 50 Green
8 RTIP 17 Yellow 51 Green
9 TTIP 18 Yellow 52 Brown
9 RTIP 19 Yellow 53 Brown
10 TTIP 20 Yellow 54 Grey
10 RTIP 21 Yellow 55 Grey
11 TTIP 22 Violet 56 Blue
11 RTIP 23 Violet 57 Blue
12 TTIP 24 Violet 58 Orange
12 RTIP 25 Violet 59 Orange
13 TTIP 26 Violet 60 Green
13 RTIP 27 Violet 61 Green
14 TTIP 28 Violet 62 Brown
14 RTIP 29 Violet 63 Brown
15 TTIP 30 Violet 64 Grey
15 RTIP 31 Violet 65 Grey
16 TTIP 32 Black 66 Blue
16 RTIP 33 Black 67 Blue
GND 34 68

4.1.10.3 Optical splitters for STM-1 signal and EoSDH (SFP for port #5 and #6 of Core-E
unit)
SC-SC to LC Splitter (L = 4 m) 3CC52062AAAA
LC-LC Output to FC Input Splitter (L = 4 m) 3CC52030AAAA
LC-LC Output to SC Input Splitter (L = 4 m) 3CC52035AAAA
LC-LC Output to LC Input Splitter (L = 4 m) 3CC52040AAAA
LC-LC Output to ST Input Splitter (L = 4 m) 3CC52043AAAA
4.1.10.4 Splitter for 2xE1 SFP (SFP for port #5 and #6 of Core-E unit)
2xE1 Splitter (L = 0.5 m) 3CC52172AAAA
4.1.10.5 Accessories and cables for ODU300 connections
3CC50074ABXX Support kit for 4 cord. N/QMA IDU MPR
1AB095530023 Coax cable conn. male straight 50 ohm (diam.=10.3 mm)
1AB128500002 Coax cable grounding kit (diam.=10.3 mm)
1AB095530036 Coax cable conn. male straight 50 ohm (diam.=6.85 mm)
1AD040130004 Coax cable grounding kit (diam.=6.85 mm)
3DB00714AAXX Coax cable N conn. male (LCF 3/8” CU H cable)
3DB00715AAXX Coax cable N conn. 90° male (LCF 3/8” CU H cable)
3DB00698AAXX Coax cable grounding kit (LCF 3/8” CU H cable)
1AD127970001 Cable grounding kit KMT11-N (Yellow/Green)
1AB3557780003 QMA Connector for coax. cable (diam. 6.85 mm)
1AC001100022 Coax cable 50 ohm (diam.=10.3 mm) (L = <150m )
1AC041350001 Coax cable 50 ohm (diam.=6.85 mm) (L = <80m)
3DB00713AAXX Coax cable 50 ohm LCF 3/8” CU H (L = <300m)
3CC50099AAXX Standard tool bag
3CC50100AAXX MSS ODU300 tool bag (special tools)

4.1.10.6 Accessories and cables for MPT-HC connections
1AC001100022 Coax cable 50 ohm (diam.=10.3 mm) for L>200 m
1AB095530023 Conn. male straigth 50 ohm (diam.=10.3 mm)
1AB128500002 Cable grounding kit (diam.=10.3 mm)
1AC041350001 Coax. cable 50 ohm (diam.=6.85 mm) for L<200 m
1AB095530036 N Conn. Male straigth 50 ohm for coax. cable (diam.=6.85 mm)
1AD040130004 Grounding kit for coax. cable (diam.=6.85 mm)
3DB18205AAAA QMA (male)-N (Female) RF cable
3CC50074ABAA Support kit for 4 cord N/QMA MPR IDU
1AB357780003 QMA 90° connector for coax. cable (diam.=6.85 mm)
1AC016760006 IDU-ODU Ethernet cable Cat5e shield 80% for outdoor environment
1AB074610027 RJ45 connector (cable diam <=7mm) (boot included)
1AD160490001 Tool for HIROSE RJ45 IDU-ODU cable assembling
1AD024450011 Gland, cable feed-through EMC (to be inserted in the electrical cable)
1AF17000AAAA Hoisting protection tube (for ethernet or fiber cord)
1AD040130004 Grounding kit for RJ45 Ethernet electrical cable
3CC08166AAXX ODU Grounding kit
3CC52160ALAA LC-LC cord for MPT IDU_ODU connection

80m pre-assembled fiber cable + gland
3CC52160AAAA LC-LC cord for MPT IDU_ODU connection

100m pre-assembled fiber cable+ gland
3CC52160ABAA LC-LC cord for MPT IDU_ODU connection

3CC52160ACAA LC-LC cord for MPT IDU_ODU connection

3CC52160ADAA LC-LC cord for MPT IDU_ODU connection

3CC52160AEAA LC-LC cord for MPT IDU_ODU connection

3CC52160AFAA LC-LC cord for MPT IDU_ODU connection


3CC52160AGAA LC-LC cord for MPT IDU_ODU connection
220m pre-assembled fiber able+ gland
3CC52160AHAA LC-LC cord for MPT IDU_ODU connection

3CC52160AIAA LC-LC cord for MPT IDU_ODU connection

3CC50097AAAA Cable overlength box (wall and pipe mounting only)
1AD161130001 Dynamometric wrench for Gland 20mm (10N)
1AD161030001 Dynamometric wrench for ODC
1AD160490001 HRS tool for RJ45 plug
1AB383760001 Optical SFP - MPR/MPT
3CC50098AAXX MPR-MPT tool bag (special tools)
1AB384430006 0.7m pre-assembled fiber cable with ODC connector (for 1+1 only)
1AB384430008 10m pre-assembled fiber cable with ODC connector (for 1+1 only)
1AB384430007 20m pre-assembled fiber cable with ODC connector (for 1+1 only)
1AD161030001 Dynamometric wrench for ODC 19mm (1N) (for 1+1 only)
3DB20079AAAA Jumper ODC-LC (for 1+1 only)
3CC50107AAAA DC Extractor (it includes the two 2 m jumpers for connection to MPT-MC, the
R2CT connector to terminate the MSS-DC Extractor cable and the grounding
kit)
3CC52159AAXX Pigtail
These optionals accessories must be
1AB251350001 Low Pass Filter used to connect the power coaxial
cable of MPT-HC to the station battery
3CC50030AAAA Lighting Arrestor

4.1.10.7 Accessories and cables for MPT-HC V2 connections
3DB18205AAAA QMA (male)-N (Female) RF cable
3CC50074ABAA Support kit for 4 cord N/QMA MPR IDU
1AB357780003 QMA 90° connector for coax. cable (diam.=6.85 mm)
3CC52188AAXX 1 m Adapter cord (N female-Free wires) (plus RJ45-indoor) for the power sup-
ply cable. To be used only if the optical cable is used for the Ethernet traffic.
3CC52188AAAA 1 m Adapter cord (N female-Free wires) (plus RJ45 plus R2CT-outdoor) for
the power supply cable. To be used only if the optical cable is used for the
Ethernet traffic.
1AC016760006 IDU-ODU Ethernet cable Cat5e shield 80% for outdoor environment (cable to
be used with PFoE)
1AC001100022 Coax cable 50 ohm (diam.=10.3 mm) for L>200 m
1AB095530023 N Conn. male straigth 50 ohm for coax. cable (diam.=10.3 mm)
1AB128500002 Grounding kit for coax. cable (diam.=10.3 mm)
1AC041350001 Coax. cable 50 ohm (diam.=6.85 mm) for L<200 m
1AB095530036 N Conn. male straigth 50 ohm for coax. cable (diam.=6.85 mm)
1AD040130004 Grounding kit for coax. cable (diam.=6.85 mm)
3CC52170AAAA Q-XCO to Q-XCO Fiber cord (L = 80 m for MPT IDU-ODU connection)
3CC52170ABAA Q-XCO to Q-XCO Fiber cord (L = 100 m for MPT IDU-ODU connection)
3CC52170ACAA Q-XCO to Q-XCO Fiber cord (L = 120 m for MPT IDU-ODU connection)
3CC52170ADAA Q-XCO to Q-XCO Fiber cord (L = 140 m for MPT IDU-ODU connection)
3CC52170AEAA Q-XCO to Q-XCO Fiber cord (L = 160 m for MPT IDU-ODU connection)
3CC52170AFAA Q-XCO to Q-XCO Fiber cord (L = 180 m for MPT IDU-ODU connection)
3CC52170AGAA Q-XCO to Q-XCO Fiber cord (L = 200 m for MPT IDU-ODU connection)
3CC52170AHAA Q-XCO to Q-XCO Fiber cord (L = 220 m for MPT IDU-ODU connection)

3CC52170AIAA Q-XCO to Q-XCO Fiber cord (L = 250 m for MPT IDU-ODU connection)
3CC52170ALAA Q-XCO to Q-XCO Fiber cord (L = 300 m for MPT IDU-ODU connection)
3CC50097AAAA Cable overlength box (wall and pipe mounting only)
3CC52169AAAA RPS Q-XCO to Q-XCO optical jumper (L = 1 m for 1+1)
3CC52169ABAA RPS Q-XCO to Q-XCO optical jumper (L = 10 m for 1+1)
3CC52169ACAA RPS Q-XCO to Q-XCO optical jumper (L = 20 m for 1+1)
3CC52159AAXX Pigtail These optionals accessories must be

used to connect the power coaxial
1AB251350001 Low Pass Filter
cable of MPT-HC V2 to the station bat-
3CC50030AAAA Lighting Arrestor tery

4.1.10.8 Accessories and cables for MPT-MC connections
1AC016760006 IDU-ODU Ethernet cable Cat5e shield 80% for outdoor environment
1AB074610027 RJ45 connector (cable diam <=7mm) (boot included)
1AD160490001 Tool for HIROSE RJ45 IDU-ODU cable assembling
1AD024450011 Gland, cable feed-through EMC (to be inserted in the electrical cable)
1AF17000AAAA Hoisting protection tube (for ethernet or fiber cord)
1AD040130004 Grounding kit for RJ45 Ethernet electrical cable
3CC50098AAXX MPR-MPT tool bag (special tools)

4.1.10.9 Distributors
The Distributor subracks available are:
Figure 422. Protection Panel 32E1 SCSI 68 - 1.0/2.3 75 ohm (Front/Rear) (3DB16104AAAA)
Figure 423. Protection Panel RJ45 120 ohm (Front/Rear) (1AF15245ABAA)
Figure 424. Protection Panel 32E1 SCSI 68 - 1.6/5.6 75 ohm (Front) (1AF15243AAAA)
Figure 425. Protection Panel 32E1 BNC 75 ohm (Front) (1AF15244AAAA)
Figure 426. Connector support 1.6/5.6 75 ohm Panel 1U (3CC08061AAAA)
Figure 427. Connector support BNC 75 ohm Panel 1U (3CC08061ABAA)

Figure 428. Support 19 Inch modules 120 ohm Panel 3U (3CC07810AAAA)
Figure 429. E1 Protection SCSI 68/Sub-D 37 (Front/Rear) (3DB16102AAAA)
4.1.10.10 MSS cards
The MSS available cards are:
Figure 430. Core-E Card
Figure 431. Modem Card (to inteface ODU300)

Figure 432. MPT Access Card (to interface MPT-HC)
Figure 433. 32xE1 PDH Access Card
Figure 434. 16xE1 ATM ASAP Card
Figure 435. AUX Peripheral Card
Figure 436. STM-1 Access Card

4.1.10.11 Ethernet Electrical Cables
3CC52141ABAA RJ45-RJ45 Eth. CAT5E shielded straight cable 5 m
3CC52141ACAA RJ45-RJ45 Eth. CAT5E shielded straight cable 15 m
4.1.10.12 Ethernet Optical Cables
The following multi-mode jumpers are available:
1AB214000016 Fiber Simplex MM jumper LC-LC L = 5m
1AB214000017 Fiber Simplex MM jumper LC-LC L = 10m
1AB240330033 Fiber Simplex MM jumper LC-FC L = 5m
1AB240330032 Fiber Simplex MM jumper LC-FC L = 10m
1AB200240003 Fiber Simplex MM jumper LC-SC L = 5m
1AB200240004 Fiber Simplex MM jumper LC-SC L = 10m
The following single-mode jumpers are available:
3CC52077AAAA Fiber 3M SM LC to LC
3CC52080AAAA Fiber 3M SM LC to FC
3CC52083AAAA Fiber 3M SM LC to SC
3CC52088AAAA Fiber 5M, SM FC-SC
3CC52017AAAA Fiber 10M, SM FC-SC
3CC52023AAAA Fiber 3M, SM SC-SC

4.1.10.13 Installing the Indoor section
Figure 437. Installation subrack and 4 cord N/QMA Kit
Figure 438. Installation Card
Figure 439. Installation Accessory

Figure 440. Connection Cables

4.1.10.14 Type of Indoor configurations
4.1.10.14.1 MSS-8 configurations with ODU300
4.1.10.14.1.1 Repeater 2x1+0 32E1 (1 PBA PDH) towards customer DDF 120 Ohms 3U
Figure 441. Repeater 2x1+0 32E1 (1 PBA PDH) towards customer DDF 120 Ohms 3U
Figure 442. Repeater 2x1+0 32E1 (1 PBA PDH) towards customer DDF 120 Ohms 3U

4.1.10.14.1.2 Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 120 Ohms 3U
Figure 443. Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 120 Ohms 3U

4.1.10.14.1.3 Repeater 2x1+0 32E1 towards 2xinternal DDF 75 Ohms BNC 2x1U
Figure 445. Repeater 2x1+0 32E1 (1 PBA PDH) towards 2xinternal DDF 75 Ohms BNC 2x1U with
cords 3CC52134AAAA (1 SCSI68 to 2 DB37)



4.1.10.14.1.4 Repeater 2x1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms
Figure 450. Repeater 2x1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms


4.1.10.14.1.5 Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 75 Ohms 1.6/5.6 2U
Figure 453. Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 75 Ohms 1.6/5.6 2U
Figure 454. Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 75 Ohms 1.6/5.6 2U

4.1.10.14.1.6 Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U
Figure 455. Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U
Figure 456. Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U

4.1.10.14.1.7 Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U


4.1.10.14.1.8 Terminal 1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms
Figure 460. Terminal 1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms
Figure 461. Terminal 1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms

4.1.10.14.1.9 Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms BNC 3U
Figure 462. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms BNC 3U
Figure 463. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms BNC 3U

4.1.10.14.1.10 Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U
Figure 464. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U
Figure 465. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U

4.1.10.14.1.11 Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms 1.0/
2.3 1U

4.1.10.14.1.12 Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms RJ45
2U

4.1.10.14.1.13 Terminal 1+1 32E1 Full protected with 2 cords 3CC52157AAAA (2 PBA PDH)
towards internal DDF 120 Ohms 3U
Figure 470. Terminal 1+1 32E1 Full protected with 2 cords 3CC52157AAAA (2 PBA PDH) towards
internal DDF 120 Ohms 3U
Figure 471. Terminal 1+1 32E1 Full protected with 2 cords 3CC52157AAAA (2 PBA PDH) towards
internal DDF 120 Ohms 3U

4.1.10.14.1.14 Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards customer DDF 120 Ohms
Figure 472. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards customer DDF 120 Ohms

4.1.10.14.1.15 Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 75 Ohms 1.0/
2.3 1U
Figure 474. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 75 Ohms 1.0/
2.3 1U
Figure 475. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 75 Ohms 1.0/
2.3 1U

4.1.10.14.1.16 Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 120 Ohms 3U
Figure 476. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 120 Ohms 3U
Figure 477. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 120 Ohms 3U

4.1.10.14.1.17 Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2xinternal DDF 75 Ohms
1.0/2.3 1U
Figure 478. Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2xinternal DDF 75 Ohms 1.0/
2.3 1U
2.3 1U

2.3 1U

4.1.10.14.1.18 Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2xinternal DDF 120 Ohms
3U


4.1.10.14.1.19 Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards customer DDF 120 Ohms

4.1.10.14.2 MPT-HC Access peripheral unit
Figure 486. MPT-HC Access peripheral unit electrical connections
Figure 487. MPT-HC Access peripheral unit optical connections

4.1.10.14.3 2xE1 SFP and EoSDH SFP on Ports #5 and #6 of the Core unit in protected mode with
splitter
Figure 488. 2xE1 SFP and EoSDH SFP
4.1.10.14.4 STM-1 units in protected mode with splitter
Figure 489. STM-1 units

4.1.10.15 Connectors on the front panel of the 32E1 PDH card and 16 E1 ASAP card (68
Pin SCSI Functions)
Table 46. Pin Function: Tributaries 1-16 (32E1 PDH card/16E1 ASAP card)
Description Pin # Pin # Description
GND 1 35 GND
TTIP Trib. 1 2 36 1 Trib. TTIP
RTIP Trib. 1 3 37 1 Trib. RTIP

GND 34 68 GND
Table 47. Pin Function: Tributaries 17-32 (32E1 PDH card)
Description Pin # Pin # Description
GND 1 35 GND

GND 34 68 GND

4.1.10.16 Connectors on the front panel of the AUX peripheral card
The Service Channel interface 1 connector on front panel is a SubD 15 female.
Table 48. Service channel 1 pin functions
Pin Signal Direction Pin Signal Direction
1 GND NA 9 Audio(-) from user

Input
2 Audio(+) from 10 Audio(-) to user Party Line

user Input Output
Party Line
3 Audio(+) to user Output 11
4 GND for Audio NA 12 RS422 Data in (-) Input
5 RS422 Data in Input 13 RS422 Clock in Input

(+) (-)
RS422/
6 RS422 Clock in Input 14 RS422 Data out Output
V.11
(+) RS422/ (-)
64K
V.11
7 RS422 Data out Output 15 RS422 Output
64K
(+) Clock out
(-)
8 RS422 Clock out Output

(+)
The Service Channel interface 2 connector on front panel is a SubD 15 female.
Table 49. Service channel 2 pin functions

1 GND NA 9 G 703 Data in (-)

Input
2 G 703 Data in (+) 10 G 703 Data out (-) G 703

Input Output 64K
G 703
3 G 703 Data out (+) Output 64K 11 RS232 Data out Output RS232/
V.24/V.28

4 RS232 Data in Input RS232/ 12 RS422 Data in (-) Input
V.24/V.28
5 RS422 Data in (+) Input 13 RS422 Clock in (-) Input

RS422/
V.11
6 RS422 Clock in Input 14 RS422 Data out (- Output
64K or 9.6K
(+) RS422/ )
V.11
7 RS422 Data out Output 15 RS422 Output
64K or 9.6K
(+) Clock out
(-)
8 RS422 Clock out Output

(+)
Synchronous 64 Kb/s RS422/V.11 DCE co-directional
Figure 490. DTE-DCE Interface
This interface is a particular case of the co-directional definition when it is possible to assume that the tim-
ing signals are equal in both the directions: the subordinate equipment (DTE) has to synchronize the out-
put data with the unique timing signal received.

Table 50. Housekeeping connector pin function
1 Housekeeping 1 Input 9 COM NA Common

return
2 Housekeeping 2 Input 10 GND NA Ground
3 Housekeeping 3 Input 11 Housekeeping 9 Output

House-
House-
6 Housekeeping 6 Input 14 Housekeeping 12 Output keeping
keeping
7 Housekeeping 7 Output 15 Housekeeping 13 Output
8 Housekeeping 8 Output
Input alarm
The polarity of each input Alarm-Housekeeping is configurable. The state of each alarm input is config-
urable by ECT/NMS in order to be active if the voltage on the input is high (open contact) or if the voltage
is low (closed contact). This second option is the default value.
The polling rate of the input alarms is 1 second, no latch of input state is performed.
Figure 491. Alarm Polarity

Input alarm electrical characteristics
open contact: 2V < |V|< 60 V; |I| < 0.2mA
closed contract: 0V < |V|< 2 V; |I| < 50mA
Though the housekeeping equipment requirement on max input voltage is 60 V, the PCB layout of periph-
eral must be able to manage 72 V.
By default the presence of active alarm corresponds to closed relay contact with a common wire available
to the customer. By WebEML/NMS it is possible to change the polarity independently for each alarm (both
normally closed and normally open contacts are available on the I/O connector).
When the power supply is down (and also when the power supply is on but the SW hasn't yet initialized
the HW), all the relays of the outputs of the alarms/housekeeping are in the "open" state (HW default con-
dition).
Figure 492. Polarity of the alarm
Output alarm electrical characteristics
open contact: 2V < |V|< 60V; |I| < 0.2mA
closed contract: 0V < |V|< 2V; |I| < 50mA
Though the housekeeping equipment requirement on max output voltage is 60 V, the PCB layout of
peripheral must be able to manage 72 V.
4.1.10.17 Interconnection to AWY
To interconnect the MPR to AWY refer to the AWY Hardware Installation manual.

4.1.11 Antenna Alignment
This section includes:
– Preparation (see par. 4.1.11.1 on page 680)

– Signal Measurement (see par. 4.1.11.2 on page 680)
– Aligning the Antenna (see par. 4.1.11.3 on page 683)
– Main Beams and Side Lobes (see par. 4.1.11.4 on page 687)
4.1.11.1 Preparation
Before aligning antennas ensure:
– The ODUs are powered up at both ends of the link.

– Transmit and receive frequencies are correctly set.
– Transmit powers are correctly set and transmit mute is turned off.
Note
If frequency and/or power settings are not correct for the application,
interference may be caused to other links in the same geographical area.
4.1.11.2 Signal Measurement
Two receive signal-strength indicators are provided to assist antenna alignment, RSL in the WebEML
Performance screen, and the RSSI voltage at the BNC connector on the ODU300 and at LEMO connector
on the MPT-HC. Refer to:
– Using RSL Data (see par. 4.1.11.2.1 on page 680)
– Using the RSSI Voltage at the ODU300 (see par. 4.1.11.2.2 on page 681)
– Using the RSSI Voltage at the MPT-HC (see par. 4.1.11.2.3 on page 681)
– RSL Measurement Guidelines (see par. 4.1.11.2.3.1 on page 683)
4.1.11.2.1 Using RSL Data
As WebEML is accessed via connection to the MSS, a separate means of communication such as two-
way radio or cell phone is required between the WebEML operator and the person at the antenna.
To align using RSL:
1) Monitor RSL in the WebEML Performance screen.
2) Set antenna alignment for maximum RSL.
3) Repeat for the far end of the link.
4) Compare actual RSLs with the expected RSLs from the link installation datapack. RSL mea-
surement accuracies:
a) ± 2 dB for levels -40 to -70 dBm, over a temperature range of 0 to +35°C.
b) ±4 dB for levels -25 to -85 dBm, over an extended -33 to +55°C range.

4.1.11.2.2 Using the RSSI Voltage at the ODU300
A voltmeter, such as a multimeter, is used to measure RSSI voltage at the BNC connector on the ODU.
A suitable BNC to banana-plug connecting cable is available as an optional ODU accessory.
1) Connect the voltmeter to the BNC connector. Center pin is positive. Use a low voltage range
for best resolution, nominally 2.5 Vdc FSD.
2) Adjust antenna alignment until the voltmeter reading is at minimum value.
Check and record the peak voltage at each end. The RSSI voltage provides a direct relationship with RSL,
as follows:
Units Measurement (with ODU300)
BNC (Vdc) 0.25 0.5 0.75 1.0 1.25 1.5 1.75 2.0 2.25 2.5
RSL (dBm) -10 -20 -30 -40 -50 -60 -70 -80 -90 -100
4) Compare actual RSLs to the expected RSLs from the link installation datapack. Refer to par.
4.1.11.2.3.1 - RSL Measurement Guidelines.
5) Replace the BNC weatherproofing.
Note
Failure to replace the RSSI BNC weatherproof cap may result in damage to the ODU.
4.1.11.2.3 Using the RSSI Voltage at the MPT-HC/MPT-MC
A voltmeter, such as a multimeter, is used to measure RSSI voltage.
Use the MPT/AWY Service Cord for the power monitoring in addition to a voltmeter.
1) Connect a voltmeter to the MPT-HC/MPT-MC through the MPT/AWY Service Cord.
2) Adjust antenna alignment until the voltage reading is at maximum value.
Check and record the peak voltage at each end. The RSSI voltage provides a direct relationship with RSL,
as follows:
Units Measurement (with MPT-HC/MPT-MC)
Service kit cable (Vdc) 5 4.71 4.12 3.5 2.9 2.3 1.71 1.11 0.59 0.14
RSL (dBm) -10 -20 -30 -40 -50 -60 -70 -80 -90 -100
4) Compare actual RSLs to the expected RSLs from the link installation datapack. Refer to par.
4.1.11.2.3.1 - RSL Measurement Guidelines.

MPT/AWY Service Cord operative information
Figure 493. herebelow shows the cable P/N 3CC52191AAXX to be used during the Commissioning to
point the antenna.
Connection table
Signal M1 M2 M3 M4
ETH_TXP_T 1 3
ETH_TXN_T 2 6
GND 3 X
ETH_RXP_T 4 1
ETH_RXN_T 5 2
LEMO wire 6 = ground
PRX_OUT 12 X
Figure 493. MPT/AWY Service Cord
Connector usage:
– (M1) LEMO connector, to be plugged into LEMO connector on MPT-HC/MPT-HC V2/MPT-MC.
– banana plugs (M3) and (M4): output is a 0 to +5V DC voltage proportional to the radio Rx field.
Duringequipment line–up, through a multi–meter it is possible to easily point the antenna until the
measuredvoltage is the maximum, corresponding to the maximum radio Rx field.
– (M2) Connector: for Alcatel–Lucent internal use only.

4.1.11.2.3.1 RSL Measurement Guidelines
Interference for ODU300 (Not applicable for MPT-HC/MPT-MC)
The RSSI filter has a nominal 56 MHz bandwidth, which means that depending on the channel bandwidth
used, multiple adjacent channels will be included within the filter passband. Normally this will not cause
a problem as antenna discrimination (beamwidth) and good frequency planning should exclude adjacent
channel interferers. However at sites where this is not the case, ATPC should not be enabled.
– ATPC operates on the RSL. Any interferer that affects the RSL will adversely affect ATPC operation
– Check for interference by muting the Tx at the far end and checking RSSI/RSL at the local end
RSSI/RSL Accuracy
When checking RSSI/RSL against the predicted link values ensure appropriate allowances are made for
Tx power-setting accuracy, path-loss calculation accuracy, and RSSI/RSL measurement accuracy.
– For a worst-case the overall accuracy is the sum of the individual accuracy limits, which for an
ODU300 link would be ±4 dB of the predicted value (±2 dB for transmit, ±2 dB for receive, 0 to 35°C),
aside from the path-loss calculation accuracy, which should be within limits of ±3 dB.
– Typically, where the measured RSSI/RSL is more than 4 dB lower than the expected receive level
you should check the path survey results, path calculations and antenna alignment.
Note
When checking RSSI/RSL ensure the measurement is made under normal,

unfaded and interference-free path conditions.
– A discrepancy of 20 dB or greater between the measured and calculated RSSI/ RSLs suggests an
antenna is aligned on a side lobe, or there is a polarization mismatch.
4.1.11.3 Aligning the Antenna
Antenna alignment involves adjusting the direction of each antenna until the received signal strength
reaches its maximum level at each end of the link.Fine adjustment for azimuth (horizontal angle) and
elevation (vertical angle) is built into each antenna mount.
Adjustment procedures will be provided with each antenna.If the horizontal adjuster does not provide suf-
ficient range to locate the main beam, the antenna mounting brackets will need to be loosened and the
antenna swiveled on its pole mount to locate the beam.
Before doing this ensure the horizontal adjuster is set for mid-travel.
Some mounts for larger antennas have a separately clamped swivel base to allow the loosened antenna
to swivel on it without fear of slippage down the pole. Where such a mount is not provided a temporary
swivel clamp can often be provided using a pair of pipe brackets bolted together immediately below the
antenna mount.
Note
Ensure antennas are aligned on the main beam, and not a side lobe.
For guidance, refer to the sections Locating the Main Beam (see par. 4.1.11.4.1 on page 687)
and Tracking Path Error (see par. 4.1.11.4.2 on page 688).
Ensure ATPC is turned off during the alignment procedure.

4.1.11.3.1 Standard Alignment Procedure
To align an antenna:
1) Loosen the azimuth adjuster on the antenna mount (horizontal angle) and adjust azimuth posi-
tion for maximum signal strength.
2) Tighten the azimuth securing mechanism. Ensure signal strength does not drop as it is tight-
ened.
3) Loosen the elevation adjuster (vertical angle) and adjust for maximum signal strength.
4) Tighten the elevation securing mechanism. Ensure signal strength does not drop as it is tight-
ened. The terminal is now aligned and ready to carry operational traffic.
5) Record RSL and/or RSSI voltage in the commissioning log.
4.1.11.3.2 Alignment Procedure for Dual polarized Antenna
The following procedure details steps required to:
– Check and if necessary set feedhead alignment using a spirit level.
– Align the antennas at each end using just one of the feeds, H or V. (Standard co-plane antenna
alignment).
– Check cross pole discrimination (XPD).
Note
Optimize alignment of the feed-heads to achieve maximum cross polarization discrimination.

This procedure assumes that the antennas used at each end of the link do comply with their
cross-polarization discrimination specification. If in doubt, refer to the antenna supplier.
Procedure:
[1] Static Feedhead Alignment
During antenna installation and before weatherproofing is installed, use a spirit level to check and
set exact vertical / horizontal alignment of the feeds:
• Do not rely on antenna markings as these will not be accurate where a mount is not perfectly
level.
• Set the spirit level against the flange of the feedhead. Take care that only the flange of the feed-
head is measured, so that no error is introduced by any minor misalignment of the mating flex-
ible waveguide flange. See Figure 494.

Figure 494. Checking Feedhead Flange with a Spirit level
• If not exactly vertical or horizontal, adjust the feedhead skew angle (rotate the feedhead) until
correct (spirit level bubble is precisely centered). For a typical feedhead check both flanges for
level, using an end point half way between the level points of the two flanges should there be
any discrepancy between the two.
[2] Align Antennas
Align the antennas at both ends using the standard (co-plane) alignment procedure, but using just one
of the feeds, V or H. Refer to Standard Alignment Procedure (see par. 4.1.11.3.1 on page 684). When
correct, proceed to step 3.
[3] Power-up both V and H links and check they are operating normally and are alarm-free. Use the Per-
formance screens to check that:
• Tx power measurements are within 1 dB (typically). If not check Tx power settings.
• RSL measurements are within 2 dB. See Using RSL Data (see par. 4.1.11.2.1 on page 680)
for guidance on measurement accuracy.
• Links are operating error-free.
Note
Where there is potential for interference from other links in the same geographical area,
check by turning the far end transmitter(s) off and measuring the local end RSL
on both V and H feeds.
[4] Measure the actual V and H signal discrimination from each antenna.

• Where measured XPDs are better than 25 dB no further adjustment is needed
• Where less than 25 dB proceed to the next step.
Note
The alignment procedures listed under steps 1 and 2 should result in a discrimination of better than 25dB.
However, for best results and greater operating margins during fading, feedhead alignment should be opti-
mized using the following procedure.
[5] Optimize End-End Feedhead Alignment
This procedure corrects for any minor rotational alignment between antennas at each end.
One antenna is the reference antenna and its feed-head assembly is not adjusted during this pro-
cedure.
Note
Only check/adjust skew angles on one antenna. If both antennas are adjusted and re-adjusted there is
potential for progressive misalignment to occur. Select one antenna as the reference antenna. On long
hops and where fading is prevalent there is potential for the V and H plane paths to be affected differently
and to therefore exhibit variable cross-polarization discrimination. This alignment procedure must be con-
ducted during periods of known, stable path conditions.
[6] Adjust the feedhead skew angle of the antenna for maximum XPD on both V and H link. If the max-
imums for each are at (slightly) different angles, adjust for a mid-point.
Note
Ensure that as you adjust the skew angle, the physical antenna alignment does not shift, which would
make it necessary to repeat step 2. Check that antenna mounting bolts and azimuth and elevation adjuster
locks have been correctly tightened. The maximum points may be quite sharp, rotate the feedhead slowly
to ensure they are not missed.
[7] Check the XPD on the link at the reference end of the link, which should be within 1 to 2 dB of the
measurements at the adjusted end.
[8] On completion ensure feedhead bolts are correctly tightened - check that XPDs do not change during
tightening.
[9] Retain feed-head adjustment data for the commissioning records.

4.1.11.4 Main Beams and Side Lobes
This section describes how to locate the main beam, and typical tracking path errors.
4.1.11.4.1 Locating the Main Beam
Ensure the antennas are aligned on the main beam, and not a side lobe.
Once a measurable signal is observed, very small alignment adjustments are required to locate the main
beam. For instance, a 1.2m antenna at 23 GHz typically has 0.9° of adjustment from center of main beam
to the first null (0.4° to the -3 dB point). Antenna movement across the main beam will result in a rapid
rise and fall of signal level. As a guide, 1 degree of beam width is equivalent to moving approximately 1.0
mm around a standard 114 mm (4.5 in.) diameter O/D pipe.
Antennas can be verified as being on main beam (as opposed to a side lobe) by comparing measured
receive signal level with the calculated level.
Signal strength readings are usually measurable when at least a main beam at one end and first side lobes
at the other are aligned.
The strongest signal occurs at the center of the main beam. The highest first lobe signal is typically 20 -
25 dB less than the main beam signal. When both antennas are aligned for maximum main beam signal
strength, the receive signal level should be within 2 dB of the calculated level for the path. This calculated
level should be included in the installation datapack for the link.
Figure 495. is an example of a head-on, conceptual view of the beam signal strength, with concentric rings
of side lobe peaks and troughs radiating outward from the main beam.
Figure 495. Indicative head-on signal pattern for a parabolic antenna

4.1.11.4.2 Tracking Path Error
Side lobe signal readings can be confused with main beam readings. This is particularly true for the first
side lobe as the signal level at its center is greater than the signal level at the edges of the main beam,
and if tracking on an incorrect elevation (or azimuth) a false impression of main beam reception can be
obtained. This illustration shows an example of this with a simplified head-on view of an antenna radiation
pattern, and tracking paths for three elevation settings.
Figure 496. Example Tracking Path Signals
Line AA represents the azimuth tracking path of a properly aligned antenna.The main beam is at point
2, and the first side lobes at points 1 and 3. Line BB represents the azimuth tracking path with the antenna
tilted down slightly. Signal strength readings show only the first side lobe peaks, 4 and 5. In some instances
the side lobe peaks are unequal due to antenna characteristics, which can lead to the larger peak being
mistaken for the main beam. The correct method for locating the main beam in this case is to set the
azimuth position midway between the first side lobe peaks, and then adjust the elevation for maximum
signal.
Line CC represents an azimuth tracking path with the antenna tilted down further still. The first side lobe
signal peaks (6 and 7) appear as one peak, leading to a mistaken interpretation of a main beam. The
correct method for locating the main beam is to set the azimuth at mid peak, between 6 and 7, and then
adjust elevation for maximum signal.
This first side lobe peaking is probably the most frequent cause of misalignment in both azimuth and
elevation, especially so if one side lobe peaks higher than the other, as shown in Figure 497. A common
error is to move the antenna left to right along line DD, or top to bottom along line EE, always ending up
with the maximum signal at position 1.
Figure 497. Example Tracking Path Signals on the First Side Lobe

4.2 Software local copy
This section explains how to prepare the TCO Suite and WebEML environment in your PC.
– Getting Started (par. 4.2.1 on page 690)
– PC Characteristics (par. 4.2.2 on page 690)
– Local copy of the Software Package (SWP) to the PC (par. 4.2.3 on page 691)
– Local copy of the WebEML and TCO Suite Software to PC (par. 4.2.4 on page 693)
• Java JRE Package Installation (par. 4.2.4.1 on page 697)
• Local Copy of WebEML (JUSM/ WebEML) (par. 4.2.4.2 on page 697)
• Local Copy of TCO Suite Installation (par. 4.2.4.3 on page 698)
– Configure PC Network Card to Connect to NE (par. 4.2.5 on page 700)
– Download Software Package to NE (par. 4.2.6 on page 704)
• Server Access Configuration (par. 4.2.6.1 on page 704)
• Init SW Download (par. 4.2.6.2 on page 705)
• Software Status Detail (par. 4.2.6.3 on page 708)

4.2.1 Getting Started
Note
Read the following before starting.
– The operator must be familiar with the use of personal computers in WINDOWS environment,
internally from which the NE application software operates.
– TCO Suite and WebEML applications are on one CD. Software Package (SWP) is on another CD.
Verify versions of the CD-ROM.
– To properly install TCO Suite and WebEML applications, a PC is required, having the characteristics
specified here below.
4.2.2 PC Characteristics
The PC to use for TCO Suite and WebEML applications must meet following characteristics:
PC Hardware Configuration:
– CPU: AMD Atlhon/Intel Celeron/Intel Pentium 4 or higher

– RAM: 500 MB (1 GB recommended - strongly recommended with Windows Vista)
– Hard Disk space: 1.5 GB (available space for log files, JRE excluded)
– Display Resolution: 1024x768 pixel
– CD-ROM Drive: 24X
– Ethernet Interface: Ethernet Card 10/100 Mbps
Operating Systems Supported:
– Microsoft Windows XP Professional service pack 3 or Microsoft Windows Vista Ultimate service pack
2
Additional requirements:
– Microsoft Internet Explorer 6 SP1, 7, 8, Mozilla Firefox 2, 3, 3.5

– The Administrator password is needed only for Java installation.
– When Java has been installed, the standard user can run the TCO Suite
– Java Runtime Environment (JRE) 6 Update 14
– Disable all Firewall software on PC used

4.2.3 Local copy of the Software Package (SWP) to the PC
Follow these steps to copy the Software Package (SWP) to the PC.
N.B. With Internet Explorer 8 on Windows 7 before inserting both the SWP CD-ROM and the TCO
SW Suite one, the user (only in Windows 7 when Internet Explorer is the default browser) has
to disable the Internet Explorer "Protected Mode". This can be performed via the "Internet
Options" icon in the control panel, selecting the "Security" tab and unchecking the related option
"Enable Protected Mode (requires restarting Internet Explorer)". Without this, the browser is
opened but the CD-ROM content is not displayed (an empty page is shown), because it's
blocked by IE Protected Mode.
[1] Insert the SWP CD into the CD-ROM drive.
Note
The Software Package will auto-run and open up the computer's default browser program (if auto-run fea-
ture is enabled on user's PC) as soon as the CD-ROM is read by the PC. If auto-run does not start, the
user must run (double-click with left mouse button on it) the aluopener.exe file, available on CD-ROM root,
in order to launch the Software Package.
Note
This certificate is not signed by a public/trusted certification authority. The Warning Security dialog will
inform the user about this problem and browser/JRE will probably recognize the signature as "not valid".
This is neither an error nor a problem. If the dialog message specifies that the signature cannot be ver-
ified, it means the signed applet is correct but that the signature cannot be publicly checked on the Internet.
As usual, both language and graphical layout could vary with respect to browser, operating system ver-
sion, operating system and browser languages and so on. To avoid further requests it is suggested to con-
firm and "always trust" the stated certificate source.
[2] Click on the Local Copy button to copy the software to your local PC.

[3] Click on the Start Copying button.
[4] Choose a directory location for the Local Copy of Software Package. Select the directory and click
on OK to begin the copy process.
Warning: Special characters (like #...) cannot be used.
[5] The files will be copied from the CD to the PC and will create a directory named ECT.
[6] A successful copy message will display, when all files have been copied. Click OK.
[7] Remove the SWP CD from the CD-ROM drive.

4.2.4 Local copy of the WebEML and TCO Suite Software to PC
Follow these steps to copy the WebEML/TCO Suite software to the PC.
N.B. With Internet Explorer 8 on Windows 7 before inserting both the SWP CD-ROM and the TCO
SW Suite one, the user (only in Windows 7 when Internet Explorer is the default browser) has
to disable the Internet Explorer "Protected Mode". This can be performed via the "Internet
Options" icon in the control panel, selecting the "Security" tab and unchecking the related option
"Enable Protected Mode (requires restarting Internet Explorer)". Without this, the browser is
opened but the CD-ROM content is not displayed (an empty page is shown), because it's
blocked by IE Protected Mode.
[1] Insert the TCO SW Suite CD-ROM into the CD-ROM drive.
Note
The TCO SW Suite CD-ROM will auto-run and open up the computer's default browser program (if auto-
run feature is enabled on user's PC) as soon as the CD-ROM is read by the PC. If auto-run does not start,
user must run (double-click with left mouse button on it) the Start.exe file, available on CD-ROM root, in
order to launch the Software Package.
Note
This certificate is not signed by a public/trusted certification authority. The Warning Security dialog will
inform the user about this problem and browser/JRE will probably recognize the signature as "not valid".
This is neither an error nor a problem. If the dialog message specifies that the signature cannot be
verified, it means the signed applet is correct, but that the signature cannot be publicly checked on the
Internet. As usual, both language and graphical layout could vary with respect to browser, operating
system version, operating system and browser languages and so on. To avoid further requests it is
suggested to confirm and "always trust" the stated certificate source.
[2] Click on MPR Tools.
Figure 498. TCO Convergence (MPR Tools)

[3] The following screen opens.
[4] Double click on MSS-8/MSS-4 icon to perform the Local Copy of the WebEML.

[5] Click No.
[6] Click Yes to perform the WebEML Local Copy.
[7] Select the directory and click Open.
[8] The copy is now in progress.
[9] Wait until the following message will appear. Click OK.

[10] Click Yes to set a link on the desktop.
[11] Click on the WebEML icon on the desktop to start the application.
N.B. An alternative way to perform the Local Copy of the WebEML is the following:
[1] Click on the Advanced Settings button below.
[2] Select one of the three Advanced Settings options to copy software to the PC.
• Java JRE Package Installation (par. 4.2.4.1 on page 697)
• Local Copy of WebEML (JUSM/ WebEML) (par. 4.2.4.2 on page 697)
• Local Copy of TCO Suite (par. 4.2.4.3 on page 698)

4.2.4.1 Java JRE Package Installation
[1] Click on the Java JRE Package Installation button to install the Sun Java Runtime Environment
(JRE) 6 Update 14 version to your PC.
4.2.4.2 Local Copy of WebEML (JUSM/ WebEML)
[1] Click on the Local Copy of WebEML (JUSM/WebEML) button to copy the WebEML software to your
PC. Choose the directory location and click Open and then OK.

[2] When the files have finished copying, this window will display. Click the OK button. The files will be
copied to a created directory named MPRE_WebEML_VXX.XX.XX (where the X's are the version
number).
[3] An icon will be created on the desktop if the user clicked yes.
4.2.4.3 Local Copy of TCO Suite Installation
[1] Click on the Local Copy of TCO Suite button to install the TCO Suite software to your PC. Choose
the directory location and click Open and then OK.
The files will be copied from the CD to the PC in a created directory.

[2] When the file has been successfully copied, click the OK button.
[3] The user has the option to create a shortcut link on the PC desktop. Click Yes or No.
An icon similar to this one will be created on the desktop if the user clicked yes.

4.2.5 Configure PC Network Card to Connect to NE
This example uses a Microsoft Windows XP Professional system.
[1] Connect a CAT 5/5E cable from the PC network card to NMS connector on Slot 1 Core-E card.
[2] Click on the START menu on the Windows desktop and open up the CONTROL PANEL.
[3] Open up the NETWORK CONNECTIONS. Highlight the network card as shown below.
[4] Dobule click on Properties to display the screen below and scroll down the list to highlight the Inter-
net Protocol (TCP/IP) line. Click the OK button.

[5] As default the DHCP server on the MPR is enabled. Set the PC to get automatically an IP address.

[6] If for any reason the DHCP server on the MPR has been disabled, enter the IP address of 10.0.1.3
for the PC network card as shown below. Click OK.
Note
The 10.0.1.3 IP address example shown below is derived from the default NE IP address (10.0.1.2) plus
1. If there is an IP address conflict within your network, increment the last number by two.
Note
It is suggested to keep enabled only one network connection on a PC.
[7] To check the connectivity between the PC and the NE, open up a DOS window or Command Prompt.
Click on the START menu on the Windows desktop and open up the RUN window as shown below.
[8] Type cmd and click OK to open up a DOS window.
The DOS window will display.

[9] In the DOS window, click the cursor after the > and type ping 10.0.1.2 to verify a connection between
the PC and the NE. The Ping statistics for the IP address 10.0.1.2 should display 4 packets sent and
and 4 packets received.
Note
The 10.0.1.2 IP address is the default NE IP address.

4.2.6 Download Software Package to NE
After the switching on of the equipment click on the MPRE-WebEML icon on your desktop.
The Server Access Configuration menu option in the menu bar allows the user to configure the FTP server
to be used to download the Software Package (SWP) to the NE.
[1] On the WebEML main screen, click on the SW Download dropdown menu and select Server
Access Configuration.
4.2.6.1 Server Access Configuration
The user has the choice of implementing Step 2 OR Step 3 below. Afterwards, continue to Step 4.
[2] Enter the User Id and Password login information to access the FTP server. In the Address field,
write the IP address of the FTP server. In the Port field, write the port to be used and in the Root
Directory field, write the directory into which the software has been downloaded.
[3] Click the Set Default button and the screen below will appear showing the default configuration. The
WebEML is the default FTP server with the following parameters:
• User Id: anonymous

• Password
• Address: Local host IP address
• Port: 21
• Root Dir: /

Note
The set default parameters can be changed by writing different values in the fields and then by clicking
on the OK button.
[4] Click the OK button.
4.2.6.2 Init SW Download
Warning:The download of a new software version takes time:

– 5 minutes for the Core-E unit
– 3 minutes for the PDH unit
– 3 minutes for the SDH unit
– 20 minutes for the Modem unit
– 3 minutes for the MPT Access unit
– 1 minute for the ASAP unit
– 30 seconds for the AUX unit
[1] On the WebEML main screen, click on the SW Download dropdown menu and select Init SW Down-
load. This menu option allows the user to download software to the NE for initial downloads and
upgrades.
[2] Click the Add button to add the available software packages on the PC.

Note
Before the starting the software download it is recommended to set the RTPC mode to the maximum Tx
power.
[3] Browse to the directory where the NE software was installed and click the Open button.
[4] Highlight the description file (i.e. R95M.DSC) and click the Open button.

[5] Highlight the line as shown below and click on the Init Download button.
[6] Click the Yes button to begin the download process.
Note: The complete SWP of 3.0.0 is made up of two packages:

• SWP 3.0.0
• SWP 3.0.0 followed by a letter
To upgrade from Rel. 2.1.0 to Rel. 3.0.0 download only the second SWP.
To upgrade from Rel. 1.3.1 or Rel. 1.4.0 to Rel. 3.0.0 first download the first SWP and then
the second one.

When the SW download starts, a screen showing the in progress operation of the download appears. The
download is aborted when the Abort button is pressed.
[7] Click Ok.
4.2.6.3 Software Status Detail
[1] On the WebEML main screen, click on the SW Download dropdown menu and select SW Status.
This screen shows the last two software versions details (par. 4.2.6.3.1 and par. 4.2.6.3.2) stored on
the NE. In this example, par. 4.2.6.3.1 shows the current committed software running on the NE. par.
4.2.6.3.2 shows the standby software or previous software.

4.2.6.3.1 Tab 1 Committed Software
This is the current software running on the NE.
4.2.6.3.2 Tab 2 Standby Software
This is the software that was downloaded above or was the previous SW version.
[2] Select Tab 2 and click on the Software Management Action drop down list.
[3] Select Activation from the Software Management Action drop down list.
[4] Click the Apply Action button to confirm the action.

[5] Click Confirm.
[6] Click OK.
[7] The card will reboot automatically with the new software in Tab 2 and will display this message. Click
OK.
Note
After the Core-E card reboots, the Tab 2 software version that was activated above will be listed under
the Tab 1 SW status detail and is the committed software running the NE. The previous software will be
listed under Tab 2 now.

5 Provisioning
The Provisioning can be performed by using:
– Provisioning tool (refer to paragraph 5.1 on page 711)
– WebEML (refer to paragraph 5.2 on page 740)
5.1 Provisioning by Provisioning Tool

The Provisioning Tool allows to create and modify provisioning files.
5.1.1 Start Provisioning Tool

[1] Double click on the mpreSuite300 icon on the Desktop (for the local copy on the PC refer to para-
graph 4.2.4 on page 693).
[2] Click on MPR Tools.
Figure 499. TCO Convergence (MPR Tools)

Provisioning 3DB 18793 AAAA Issue 1 711/876
[3] Double click on the MSS-4/MSS-8 icon.
Figure 500. MSS-4/MSS-8
[4] Click on the Provisioning Tool button.
Start provisioning
Figure 501. TCO Main Menu
The Provisioning Tool can be used "offline" and "online".
– In case of offline, it allows to prepare the provisionning in back office. Minimizing time on field and
mistakes.
– With the online mode you can either apply the "offline" configuration or fullfil online.

712/876 3DB 18793 AAAA Issue 1 Provisioning
This tool is recommended for first installation.
Thanks to a step by step approach this tool is easy to handle and allows to minimise time for provisioning
WebEML is more flexible and mandatory to configure AUX and ATM boards (not yet supported in provi-
sioning tool).
Select:
– the direct connection to the NE by putting a check mark on “Connect to NE”. When you locally
connect the PC to the NE, in the IP Address field automatically (through the autodiscovery) appears
the IP Address of the NE (in the NE the default configuration of the DHCP server is enabled; for this
reason your PC must be configured to obtain an IP Address automatically).
Click on OK.
Note 1: If the DHCP server is disabled, the IP address to be entered is the IP address of the NMS
Ethernet port.
or
– the off-line configuration by putting a check mark on “Do not connect to NE” and by clicking on
Apply.
Figure 502. Provisioning Tool Connectivity
Figure 503. Provisioning Tool Connectivity
After loading the JRE package, the screen in Figure 504 will display, if you are working off-line or the
screen in Figure 505, if you are directly connected to the NE.

Figure 504. Provisioning Tool Screen (off-line working)
Figure 505. Provisioning Tool Screen (direct connection to the NE)
If the NE does not have an empty configuration, the following screen with the following message will
appear.

Figure 506. Clear Database and Restart NE
Press the Clear Database and Restart NE button and then press Create to create a new configuration
or press Open to open a previously created configuration.
N.B. If you don't press the Clear Database and Restart NE button at the end of the configuration
you can save the file, but you cannot apply the configuration to the NE. (The Apply button will
not be available at the end of the procedure).

5.1.1.1 Configuration Screen Options
The screen below is a generic one that depicts all of the pull-down options possible depending on which
card is selected in the card slot. Protections options shown below are for all cards. See the screens shown
below for more information.
Warning: The Provisioning Tool allows to configue all the units, except the ASAP and AUX units. (The
ASAP and AUX cards must be configured with the WebEML and also the relevant ATM and Service
Channel cross-connections).
Warning: To configure the equipment extract the ASAP and/or AUX units, if any.
Protection options
for the Core cards
Protection options
for Slot 3 and Slot 4
To implement the
protection refer to
Figure 517.
Figure 507. Configuration Options Screen
Warning: If from this NE remote NEs have to be reached, remember to configure properly the Routing
Protocol of the TMN-RF channel, if the remote NE is connected through the radio link (refer
to Figure 512. or Figure 513. or Figure 515. or Figure 516.) or of the NMS Ethernet Port, if the
remote NE is connected through the Ethernet cable (refer to Figure 528.).
Buttons:
– Restore: allows to restore in the screen the initial data without any change
– Prev: the procedure goes back to the previous step (the changed data may be lost after the Warning
message)
– Next: the procedure goes on to the next step (some checks and data storage is done)
– Cancel: the procedure goes back to step 1 (Opening screen)
– Help: by clicking on this button the operator calls the help on line.

Note:
A white icon indicates that there are no cross-connec-
tions, but cross-connections can be created.
A blue icon indicates the destination is full. The limits
granted by the license key have been exceeded. A mes-
sage is also displayed stating that no more E1 ports will
be accepted. When checked this feature
A green icon indicates that the source and destination
are available and the destination can accept more E1 enables input and output
ports. pause features
Check to enable Check to enable

E1 Access Ethernet Icon
the selected port auto negotiation
Card Icon
Modem card +
ODU300 icon
MPT Access card

+ MPT-HC icon
Check to allow communication Check to allow Select Transport if ETH Port

at data rate in both directions communication at 4 on the Core Card is used
at the same time data rate but in to transport Ethernet data
only one direction
at a time
Select TMN if ETH Port
4 on the Core Card is
used for SNMP data
Figure 508. Core-E Configuration (Sheet 1 of 2)

The Quality Of Service feature enables priority forwarding
in the Core Card switch based on how the packets are
tagged: not tagged or tagged 802.1p or DiffServ. For general
traffic, the packets are not tagged and QOS can be disabled.
The user has to know if the packets are tagged, and if tagged
802.1p or DiffServ in order to know which QOS function to
chose.
Check to enable the Check to enable Each packet is classified

optical SFP plug-in the Admission based on presence of valid
Control 802.1p user priority tag
Check to select the
Each packet is based on
operation mode
Select Master DSCP field in IP header
Tick to enable or Slave to determine priority
the SSM
Priority forwarding
disabled
Figure 509. Core-E Configuration (Sheet 2 of 2)

Note
With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP - Real Time
Protocol is used); with the TDM2Eth service profile the TDM Clock source can be Differential
(RTP - Real Time Protocol is used) or Adaptive (RTP is not used). In the unit it is not possible to have
mixed configurations with service profiles using RTP and other service profiles not using RTP.
Example: if in the unit only one E1 has service profile TDM2TDM it is possible to configure other E1
with service profile TDM2Eth only with the Differential clock source (not with the Adaptive clock
source). If the Adaptive clock source is requested the E1 must be connected to another PDH unit.
Figure 510. E1 Configuration

Enable the J0, if required, by selecting one
of the two modes (SixteenBytesFrame/
OneRepeatedByte) and in the Expected
Receiving Value field enter the expected
value. Note: byte J0 is only read, no
Regeneration section Termination is done.
Set the Auto Laser Shutdown: Enabled/

Disabled ForcedOn/Disabled ForcedOff. Enter the Flow ID (range: 2
This field will appear only if the Settings to 4080). Warning: the flow id
tab-panel of the STM-1 unit the optical must be unique in the MPR
SFP has been selected. network.
Select the type: Electrical Select the Jitter Buffer

or Optical Depth: High/Low
Put a check mark in the

Port Status box to enable Select the TDM Clock
the STM-1 Source: Differential/Node
Timing
Enter the
Expected Value
Figure 511. STM-1 Configuration

Enter number from 1 to 255
for Receiver ID.
Must match associated
Receiver ID at other end of Select the suitable reference
hop. channel spacing.
Enter number from 1 to 255 for No check mark

Transmitter ID. here. Select the modulation scheme.
Must match associated Trans-
mitter ID at other end of hop.
The Revertive Restoration Criteria are
Check to enable PPP
Check to enable radio available only in 1+1 configuration, if you
RF port.
ID mismatch function want traffic on the protection channel to
The user can select:
automatically switch back to the main
- Static routing or
Tick to enable the SSM channel when alarms clear or a switch
- OSPF Area
Transmission over the command is release.
radio channel
Check to enable Enter the Tx

ATPC power Select the frequency separation
from drop-down list.
Enter the Tx RF frequecy

within the allowed range.
Figure 512. Modem Provisioning (without Adaptive Modulation)

for Receiver ID.
Must match associated Check mark to enable the
Receiver ID at other end of Adaptive Modulation. The
hop. only available configuration
is: 1+0, 1+1 HSB.
Enter number from 1 to 255 for
Transmitter ID.
Must match associated Trans- The Revertive Restoration Criteria are
mitter ID at other end of hop. available only in 1+1 configuration, if you
Enable PPP RF port. want traffic on the protection channel to
The user can select: automatically switch back to the main
Check to enable radio - Static routing or channel when alarms clear or a switch
ID mismatch function - OSPF Area command is release.
Tick to enable the SSM

Transmission over the
radio channel
Enable the Tx RF frequency

Select in the Reference Mode
field the spectral efficiency
Select the frequency separation class to be set as reference. Select in the Threshold field how
from drop-down list. many dB the switching thresholds have
to be moved from the default value (+4
Select in the Reference Channel dB/-2 dB). The default value is approx.
Spacing field the suitable channel 6 dB below the 10-6 Rx threshold.
Enter the Tx Power.
spacing.
Select in the Scheme field the

Modulation range (4/16 QAM
or 4/16/64 QAM) to be used by
the Adaptive Modulation.
Figure 513. Modem Provisioning (with Adaptive Modulation)

Enable one or two of the four ports by selection
the MPT type: HC or MC: Port#1 and Port#2 are
electrical Ethernet ports and Port#3 and Port#4
are optical Ethernet ports.
Figure 514. MPT Access configuration (1+0)
N.B. The selection of the Power Supply mode, used to supply the MPT (through 1 cable for MPT-
MC or MPT-HC with the DC Extractor or through 2 cables for MPT-HC) mst be done only with
WebEML.

for Receiver ID.
Receiver ID at other end of
hop.
Select the suitable reference
Enter number from 1 to 255 for channel spacing.
Transmitter ID.
Must match associated Trans- No check mark
mitter ID at other end of hop. here.
Select the modulation scheme.
Check to enable radio Check to enable PPP

ID mismatch function Select in the ETSI mask field
RF port.
the spectral efficiency class to
be set as reference: None, Old
Tick to enable the SSM - Static routing or
ETSI mask or New ETSI mask
Transmission over the - OSPF Area
radio channel
Check mark to enable Enter the Tx

the ATPC, if required power Select Tx (Go) and Rx (Return)
separation frequency from drop-
down list.

Figure 515. MPT-Access Provisioning (without Adaptive Modulation)

for Receiver ID.
Receiver ID at other end of
hop.
Check mark to enable the Adaptive
Modulation.
Transmitter ID.
Must match associated Trans-
mitter ID at other end of hop. Check to enable PPP
RF port.
Check to enable radio The user can select:
ID mismatch function - Static routing or
- OSPF Area
radio channel
Enable the Tx RF frequency Enter the Tx Power. Choose in the Supported Modulation
within the allowed range. field all the modulation schemes to be
used with the Adaptive Modulation.
Select in the ETSI mask field The modulation schemes (from the
Select the frequency separation the spectral efficiency class to lowest to the highest scheme) must be
from dropdown list. be set as reference: None, Old contiguous.
ETSI mask or New ETSI mask. Select in the MSE Driving Criteria field the suitable
value. In 1+1 FD and HSB configurations both the
Select in the Reference Mode transmitters can be driven by the lowest (1) or by
field the spectral efficiency the highest MSE values (2) of the two remote
class to be set as reference. demodulators.
Select in the Remote Switching

Threshold field how many dB the
Select in the Reference Channel
switching thresholds have to be moved
Spacing field the suitable channel
from the default value (+4 dB/-2 dB).
spacing.
The default value is approx. 6 dB below
the 10-6 Rx threshold.
Figure 516. MPT-Access Provisioning (with Adaptive Modulation)

Enable one of the four ports for the unit on the
left side and on the right side: Port#1 and
Port#2 are electrical Ethernet ports and
Port#3 and Port#4 are optical Ethernet ports.
Select the Ports used in the Select the protection scheme: Click on Add to enable
protection scheme 1+1 HSB, 1+1 FD. the protection scheme
With MPT-MC only 1+1 HSB
Figure 517. MPT Access configuration (protection enabling: 1+1)

for Receiver ID.
Must match associated Select the suitable reference
Receiver ID at other end of channel spacing.
hop. No check mark
here.
Enter number from 1 to 255 for Select the modulation scheme.
Transmitter ID.
Must match associated Trans- Check to enable PPP
mitter ID at other end of hop. RF port. Select in the ETSI mask field the spectral
The user can select: efficiency class to be set as reference:
- Static routing or None, Old ETSI mask or New ETSI mask
Check to enable radio - OSPF Area
ID mismatch function
Select Revertive feature if you want
traffic on the protection channel to
channel when alarms clear or a switch
command is released.
radio channel
Check mark to enable Enter the Tx

the ATPC, if required power Select Tx (Go) and Rx (Return)
separation frequency drom drop-
down list.

Figure 518. MPT-Access Provisioning (without Adaptive Modulation) (1+1)

for Receiver ID.
Receiver ID at other end of Check mark to enable the Adaptive
hop. Modulation. The available configurations
are: 1+1 HSB, 1+1 FD.
Transmitter ID.
Must match associated Trans- Check to enable PPP
mitter ID at other end of hop. RF port.
- Static routing or
Check to enable radio Select Revertive feature if you want
- OSPF Area
ID mismatch function traffic on the protection channel to
Tick to enable the SSM channel when alarms clear or a switch
Transmission over the command is released.
radio channel
Enable the Tx RF frequency Enter the Tx Power. Choose in the Supported Modulation
within the allowed range. field all the modulation schemes to be
used with the Adaptive Modulation.
Select in the ETSI mask field The modulation schemes (from the
Select the frequency separation the spectral efficiency class to lowest to the highest scheme) must be
from dropdown list. be set as reference: None, Old contiguous.
ETSI mask or New ETSI mask. Select in the MSE Driving Criteria field the suitable
value. In 1+1 FD and HSB configurations both the
Select in the Reference Mode transmitters can be driven by the lowest (1) or by
field the spectral efficiency the highest MSE values (2) of the two remote
class to be set as reference. demodulators.
The Remote Switching Threshold field

Select in the Reference Channel is not supported.
Spacing field the suitable channel
spacing.
Figure 519. MPT-Access Provisioning (with Adaptive Modulation) (1+1)

Secondary source:
- Synch-In Port
Clock from external source received on the
Sync In connector on the Core card.
- Any available E1
Clock from E1 source via E1 peripheral.
- Any available Synch-E
Clock from Giga Ethernet traffic.
- Any available STM-1 port
Clock from STM-1 source via STM-1 peripheral.
- Free Run Local Oscillator
Local oscillator on Core Card.
Restoration Criteria:
- Revertive Primary source:
Switches sync source back to primary source - Synch-In Port
after alarm on primary source clears. Clock from external source received on the
- Non-Revertive Sync In connector on the Core card.
Does not switch back to primary source after - Any available E1
primary alarm clears and stays on secondary Clock from E1 source via E1 peripheral.
sync source. - Any available Synch-E
Synchronization Role: Clock from STM-1 source via STM-1 peripheral.
Master - Free Run Local Oscillator
This field will appear, if as Synch-Out Port configuration This field will appear, if Enter the WTR time in
Source (Primary or Second- Connector that can be used to a Secondary Source the range 0-12 min-
ary) has been selected the provide sync to another radio or has been selected. utes at 10 second
“Synch-In port”: 1.024 MHz, ancillary equipment: 1.024 MHz, Select the suitable step. (Default: 5 min-
2.048 MHz, 5 MHz, 10 MHz. 2.048 MHz, 5 MHz, 10 MHz. configuration. utes)
Figure 520. Synchronization Configuration (Master)

Secondary source:
- Synch-In Port
- Any available E1
Clock from E1 source via E1 peripheral.
Clock from STM-1 source via STM-1 peripheral.
- Rx Symbol Rate
Clock extracted from the radio side.
- Free Run Local Oscillator
Primary source:
- Synch-In Port
Synchronization Role: Clock from Giga Ethernet traffic.
Slave - Rx Symbol Rate
Clock extracted from the radio side.
This field will appear, if as

Primary Source has been This field will appear, if as
selected the “Rx Symbol Source (Primary or Second-
Rate”. Select the radio slot ary) has been selected the
to be used. “Synch-In port”: 1.024 MHz,
2.048 MHz, 5 MHz, 10 MHz.
Synch-Out Port configuration

Connector that can be used to provide sync This field will appear, if as Secondary Source has
to another radio or ancillary equipment: been selected the “Any available E1”.
1.024 MHz, 2.048 MHz, 5 MHz, 10 MHz. Select the slot number and the E1 tributary number.
Figure 521. Synchronization Configuration (Slave)

By pressing Alt+W the Segregated Port View opens
(refer to the next figure).
To create the Cross-Connection refer to par. 3.4.5 where the explanation refer to the
JUSM menu.
Note: The only difference with the Provisioning Tool is in the LAG cross-connections.
No LAG cross-connections can be created with the Provisioning Tool.
The creation procedure is identical. The only difference is in pushbutton Apply, Refresh
and Close: not available in the Provisioning tool.
Figure 522. Cross Connections Configuration

By pressing Alt+W the Cross Connection View
opens (refer to the previous figure).
To segregate the ports refer to par. 3.4.5.1.5 where the explanation refer to the JUSM
menu.
The procedure is identical. The only difference is in pushbutton Apply, Refresh and
Close: not available in the Provisioning tool.
Figure 523. Segregated Port Configuration

When the NE is configured in this mode (default configuration),
the Ethernet traffic is switched according to the destination
MAC address without looking the VLAN.
The packets from the user Ethernet ports having the VLAN ID
out the allowed range (0 and 2-4080) are dropped. The packets
having a VLAN ID already used for a TDM flow are accepted.
Figure 524. 802.1D management

VLAN 1 Management
VLAN-ID 1 is automatically defined by the NE
when the 802.1Q bridge type is selected.
When the NE is configured in this
VLAN-ID 1 is shown to the operator, but it can-
mode, the management of Ethernet
not be neither changed nor deleted.
traffic looking the VLAN is enabled.
All the user Ethernet ports (enabled and dis-
abled) and all the radio ports are members of
In this mode, one VLAN will be
the VLAN 1.
assigned to all Ethernet frames inside
In egress VLAN-ID 1 is always removed from
the MPR network.
all the ports.
ADD VLan: to create a new VLAN By clicking Next the Port VLan con-
(refer to Figure 526 - VLAN manage- figuration screen opens (Figure 527).
ment)
DEL VLan: to delete a VLAN-ID. It is possible to
EDIT VLan: to change the parameters remove a VLAN-ID from the VLAN-ID table even if
of a VLAN (VLAN name, VLAN member this VLAN-ID has been already configured on one
ports, VLAN untagged ports in egress). or more user ports as Port VLAN to be added in
ingress to untagged frames. As consequence, the
VLAN-ID=1 and PRI=0 are added to the untagged
frames received on this port. Before applying this
deletion, a confirmation of the operation is shown to
the operator.
Figure 525. 802.1Q management

[1] VLAN ID field: Enter the VLAN ID (the configurable values must be in the range 2 - 4080)
N.B.: The VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) can-
not be used.
[2] VLAN Name field: Enter the VLAN Name: a text string of up to 32 characters.
N.B.: There is no check on unambiguity name.
[3] VLAN Ports field: Select the ports members of this VLAN by putting a check mark on the relevant
check box. All the user Ethernet ports and all the Radio directions can be considered. Both
enabled and disabled user Ethernet ports (radio ports when declared are implicitly enabled) can
be member of a VLAN. This means that a disabled port can be configured as a member of a
VLAN and a port already member of a VLAN can be disabled continuing to be a member of the
same VLAN.
[4] Untagged Ports field: Select, among the ports belonging to this VLAN (members), the untagged
ports (in egress the VLAN will be removed from the frames). Only the user Ethernet ports,
enabled and disabled, are manageable. The VLAN cannot be removed from the radio ports (with
the exception of the VLAN 1).
N.B.: The VLAN-ID values allowed are in the range 2 - 4080. By default, for the VLAN IDs defined,
all the ports are members and the Untag flag is set to “False”, which means all the frames are trans-
mitted with Tag.
N.B.: Tagged frames

If one tagged packet with VLAN-ID X is received on a port which is not member of the VLAN-
ID X, the packet is dropped.
Figure 526. VLAN Management

The untagged frames, received on each
user Ethernet port (port 1 to 4, and port 5
if the optical SFP plug-in has been
installed and configured), can be
Accepted or Discarded.
If the untagged frames are accepted, the VLAN-ID and Priority

fields must be configured. Only VLAN-ID values already defined
(in the VLAN management menu) can be configured for this pur-
pose. The Priority values allowed are in the range 0 - 7.
The default Port VLAN-ID and Priority values are: VLAN-ID=1;
Priority=0.
VLAN 1 is always removed, when the frame is forwarded.
Figure 527. Port VLan configuration
Note
The Port VLan Configuration screen opens only if in the Bridge Configuration screen the 802.1Q (Virtual
Bridge) has been selected.

Select Static Routing for manual routing.
Select OSPF (Open Shortest Path First
Protocol) for automatic routing.
Enter local IP Enter IP Address

Address. for Ethernet port.
Enable the Ethernet port

for management
Enable the NTP

Protocol. Enter the IP Address of Enter the IP Address
the Main NTP server. of the Spare (standby)
Enter the parameters for the NTP server.
TMN In-band management
(if required)
Figure 528. Network Configuration

A Trusted manager is an SNMP manager to which the NE automatically sends the TRAPS generated
inside the NE.
Figure 529. Trusted Managers screen

Figure 530. Typical Report Panel
By pressing the Save button an XML file is created with extension mcml.

5.2 Provisioning by WebEML
5.2.1 Start WebEML

1) Double click on the 9500MPR-E 3.0 WebEML icon on the Desktop (for the local copy on the
PC refer to paragraph 4.2.4 on page 693).
2) Enter the IP Address or DNS name.
3) Click OK.
2 3
Figure 531. Network Element Overview
4) If the Supervision is ongoing, click Show.
5) The application has been started pop-up will automatically close in a few seconds. Then the
Login screen will appear.
6) Type your Username – must not be more than 20 characters. Set the note at page 741.
7) Type your Password – must not be less than six (6) or more than 20 characters and must be
composed of full ASCII characters set (UPPER/lower case, numeric and special characters).
Set the note at page 741.
8) Click on Apply.

4
Figure 532. How to Login
Note
Profile Types – there are four user profiles defined.
– Administrator (full access also for NMS local system security parameters).
– CraftPerson: person in charge for installation and the mantenance at radio site; full access to NE but
not for security parameters, only for own password.
– Operator (person in charge to operate at the network level, not at the radio side).
– Viewer (view screens only).

Note
Default User Accounts – at the NE installation time, two default user accounts
are created on NE independently from the SNMP operating mode.
– Profile: administrator
– Username: initial
– Password: adminadmin
– Profile: craftPerson
– Username: Craftperson
– Password: craftcraft
To change the Default UserName and Password refer to par. 3.4.9 on page 261.

5.2.2 Provisioning
Note
Changes to provisioning do not have to be made in any particular order.
See Figure 533. for recommended sequence.
Start
Enable Plug-In Cards (par. 5.2.2.1)
Provision Plug-In Cards (par. 5.2.2.2)
Provision Synchronization (par. 5.2.2.3)
Provision NTP protocol (par. 5.2.2.4)
Provision NE Time (par. 5.2.2.5)
Provision VLAN (if required)

(par. 5.2.2.6)
TDM Cross-Connections
(par. 5.2.2.7)
STM-1 Cross-Connections
(par. 5.2.2.8)
ATM Cross-Connections
(par. 5.2.2.9)
AUX Cross-Connections (if

required) (par. 5.2.2.10)
Provision System (par. 5.2.2.11)
Provision management parameters

(par. 5.2.2.13 to par. 5.2.2.18)
Figure 533. Provisioning sequence
Warning: If from this NE remote NEs have to be reached, remember to configure properly the Routing
Protocol of the PPP RF channel, if the remote NE is connected through the radio link (refer
to Figure 560. or Figure 563. or Figure 566.) or of the NMS Ethernet Port, if the
remote NE is connected through the Ethernet cable (refer to Figure 579.).

5.2.2.1 Enable Plug-In Cards
All the cards that can be inserted in MSS4 or MSS8 chassis must be enabled in the equipment section:
– Spare CORE-E (in slot 2 only)

– E1-PDH Access card
– STM-1 Access card
– Modem Access card (ODU300 interconnection)
– MPT Access card (MPT interconnection)
– AUX board
– ASAP board
– FAN board
– SFP optical plug-in
Enable the MSS cards by using the following procedures. See Figure 534. through Figure 553.
5.2.2.1.1 Enable SFP optical plug-in
See Figure 534. Follow the steps to enable the optional SFP plug-in for the optical 1000 Mb/s Ethernet
interface.
Figure 534. Enable SFP optical plug-in

5.2.2.1.2 Enable Spare Core-E Card
See Figure 535. Follow the steps to enable the Spare Core-E Card in slot 2.
Figure 535. Enable Spare Core-E Card

5.2.2.1.3 Enable E1 Access Card
See Figure 536. Follow the steps to enable the E1 Access Card(s).
Figure 536. Enabling E1 Access Card

Figure 537. Enabling E1 Access Card on the same row (to implement protected configuration)

Figure 538. Enabling E1 Access Card protection

5.2.2.1.4 Enable STM-1 Access Card
See Figure 539. Follow the steps to enable the STM-1 Access Card(s).
Figure 539. Enabling STM-1 Access Card
Select the optical SFP (SFP-O) or the electrical SFP (SFP-E) installed on
the STM-1 ports (SFP#1 and/or SFP#2) and click Apply.
Note: It is not possible to enable SFP #1 and SFP #2 at the same time.
Figure 540. Enabling SFP

Figure 541. Enabling STM-1 Access Card on the same row (to implement protected configuration)

Figure 542. Enabling STM-1 Access Card protection

5.2.2.1.5 Enable Modem Card (to interface ODU300)
See Figure 543. Follow the steps to enable the Modem Card(s).
Note
ODU is automatically enabled when Modem Card is enabled.
Figure 543. Enabling Modem Card

Figure 544. Enabling Modem Card on the same row (to implement protected configuration)

Figure 545. Enabling Modem Card protection

5.2.2.1.6 Enable MPT Access Card (to interface the MPT-HC and MPT-MC)
See Figure 546. Follow the steps to enable the MPT Access Card.
Figure 546. Enabling MPT Access Card
5 Select as Usage MPT-HC or MPT-MC in one or two Ports.

N.B. Port#1 and Port#2 are electrical Ethernet ports and
6
Click on Apply
Figure 547. Enabling one port in the MPT Access card
N.B. Two unprotected or protected MPT-HC or MPT-MC can be connected to one MPT Access unit.

Figure 548. Enabling MPT Access Card - 1
5 Select as Usage MPT-HC or MPT-MC in one or two Ports.

N.B. Port#1 and Port#2 are electrical Ethernet ports and
6
Click on Apply
Figure 549. Enabling one port in the MPT Access card - 1

To configure the protection scheme
select the MPT-HC. (In the example
MPT-HC#31: connected to Port#1 of the
MPT Access unit in Slot#3).
1
4
Click on
Apply
2 3
Settings tab. Select the suitable
protection scheme
Figure 550. Enabling Protection configuration with MPT-HC/MPT-MC

5.2.2.1.7 Enable ASAP Card
See Figure 551. Follow the steps to enable the ASAP Card.
Figure 551. Enabling ASAP Card

5.2.2.1.8 Enable AUX Card (option)
See Figure 552. Follow the steps to enable the AUX Card.
Figure 552. Enabling AUX Card

5.2.2.1.9 Enable Fan Unit
See Figure 553. Follow the steps to enable the Fan Unit.
Figure 553. Enabling Fan Unit

5.2.2.2 Provision Plug-In Cards
See Figure 554. through Figure 564. to provision MSS plug-in card parameters after the cards have been
enabled.
5.2.2.2.1 Provision Core-E Card
See Figure 554. Follow the steps to provision Ethernet ports 1-4.
4
3
8
5
6
7
9
Figure 554. Core-E Card Provisioning (Ethernet ports 1-4)

See Figure 555. Follow the steps to provision Ethernet port 5 (available if the optional SFP plug-in has
been installed and enabled in the Core-E unit).
Figure 555. Core-E Card Provisioning (Ethernet port 5)

5.2.2.2.2 Provision PDH Access Card (TDM2TDM)
See Figure 556. Follow the steps to provision E1 lines (ports) 1-32.
Double Left
Click
1
3
See
details in
Figure
558.
5
6 Choose TDM2TDM if
Flow ID number 4 7 radio is being used to
required to transport transport E1 data only
E1 data. (no Ethernet).
Flow ID number is system unique and must not be

repeated in radio network. Loss of E1 data can occur.
Figure 556. PDH Access Card Provisioning (TDM2TDM)

5.2.2.2.3 Provision PDH Access Card (TDM2ETH)
See Figure 557. Follow the steps to provision E1 lines (ports) 1-32.
Double Left
Click
1
3
See
details in
Figure
558.
6
7 4 9
Flow ID number 8
required to transport
E1 data.

repeated in radio network. Loss of E1 data can occur.
Figure 557. PDH Access Card Provisioning (TDM2ETH)

Select Disabled if port (E1 line) is not:
– being used as a source or destination (typical
choice for a line not being used at a terminal or not
being dropped and inserted at a repeater);
– being dropped or inserted (typical choice for a line
being passed through at a through repeater and
not being dropped and inserted at a drop and insert
repeater).
Select Framed:
– to be able to collect the performances at the input
in Tx side and at the output in Rx side.
Signal Mode. Select Unframed:
Configures line format. Allows user – being used as a source or destination (typical
to choose if line is dropped and choice for a line being used at a terminal);
inserted (by selecting Framed/ – being dropped or inserted (typical choice for a line
Unframed) or passed through or being dropped and inserted at a drop and insert
not used (by selecting Disabled) repeater)
4
Figure 558. PDH Access Card Details

5.2.2.2.4 Provision SDH Access Card (SDH2SDH)
See Figure 559. Follow the steps to provision STM-1 ports #1 and #2.
Double Left
Click
1
2 6
4 7
8
5
3 9 10

repeated in radio network. Loss of STM-1 data can occur.
Figure 559. SDH Access Card Provisioning (SDH2SDH)

[2] Put a check mark in the Port Status box to enable the STM-1.
[3] Click on Apply.
[4] Set the Auto Laser Shutdown: Enabled/Disabled ForcedOn/Disabled ForcedOff. This field will
appear only if the Settings tab-panel of the STM-1 unit the optical SFP has been selected.
[5] Enable the J0, if required, by selecting one of the two modes (SixteenBytesFrame/OneRepeated-
Byte) and in the Expected Receiving Value field enter the expected value. Note: byte J0 is only read,
no Regeneration section Termination is done.
[6] Click on Apply on the left part.
[7 Enter the Flow ID (range: 2 to 4080). Warning: the flow id must be unique in the MPR network.
[8] Select the Jitter Buffer Depth: High/Low.
[9] Select the TDM Clock Source: Differential/Node Timing.
[10] Click on Apply on the right part.

5.2.2.2.5 Provision Modem Card
See Figure 560. and follow the steps to provision the Modem Card for Presetting Mode.
See Figure 562. and follow the steps to provision the Modem Card for Adaptive Modulation mode.
Tick on Enable to enable

the transmission of the
SSM message over the
radio channel
Figure 560. Modem Card Provisioning, Presetting Mode (Sheet 1 of 2)

By clicking on the icon the Alarm
Severity Profile menu opens,
which allows to associate to the
radio channel a specific alarm pro-
file. Select one Alarm Profile in the
Profile Name list (4 alarm profiles
are listed) and click Apply. Tick the
Show details check box to see the
severity associated to each alarm.
Figure 561. Modem Card Provisioning, Presetting Mode (Sheet 2 of 2)
Warning
When the Mode is changed from Presetting to Adaptive Modulation, the radio defaults to 14 MHz band-
width at 4 QAM. If the capacity of the radio (number of E1 lines cross connected) exceeds the available
capacity of a 14 MHz Channel at 4 QAM, Adaptive Modulation will not enable. It may be necessary to per-
form one of the following provisioning changes:
1. Reduce the quantity of E1 lines being transported to meet the required capacity.
2. Increase Reference Channel Spacing.

Figure 562. Modem Card Provisioning, Adaptive Modulation Mode (Sheet 1 of 3)


By clicking on the icon the Alarm

5.2.2.2.6 Provision MPT Access Card
See Figure 565. to Figure 569. and follow the steps to provision the MPT Access Card.
Mode 2 - PFoE (Power Fixed on Ethernet)

In this mode the MPT-HC or MPT-MC are
Mode 1 - QMA (only with MPT-HC)
power supplied by using the electrical
In this mode the MPT-HC is power
Ethernet cable.
supplied with a dedicated coaxial
Note: To implement this mode with MPT-
cable connected on the QMA
HC the DC Extractor must be installed, near
connector on the front panel of the
the MPT-HC, to separate the Ethernet traffic
MPT Access unit.
and the power supply.
Figure 565. Power Source configuration
Note: To unprovision an MPT:

– perform a Tx Mute;
– unprovision the MPT;
– remove the power supply.

Mode. Select Presetting Modulation. Displays
from dropdown list. modulation scheme
based on reference
channel spacing and
Reference Channel Spacing. capacity. Select from
Displays reference channel dropdown list.
spacing based on capacity and
modulation. Select from drop-
down list.
Check to enable radio ID

Capacity. Read Only Field. mismatch function.

PPP RF. Check to enable PPP RF for receiver ID. Must match
port. When not checked (disable) transmitter ID at other end
user command change: of hop.
- Routing IP Protocol
- OSPF Area Enter number from 1 to 255
- Remote Address for transmitter ID. Must
match associated receiver
Click to enable Open Shortest Path First
ID at other end of hop.
protocol then select area name that has
OSPF protocl. Select from dropdown list.
Alarm Profile. Not supported.

Tick on Enable to enable
the transmission of the
SSM message over the
radio channel
Figure 566. MPT Access Card Provisioning, Presetting Mode (Sheet 1 of 2)

Shifter. Select the frequency
separation from the Shifter
Data Help list.
Range. Displays range of Tx

Tx RF Frequency is automatically
RF frequencies that may be
entered by ODU when ODU is
entered.
connected to MSS. If the ODU is
not connected to the MSS, enter
the Tx RF Frequency, whitin
allowed range.
Read Only Field.

Displays Rx RF Frequency.
Result of calculation:
Rx Freq - X Freq = Shifter Freq.
Tx Mode. Read Only Field. ATPC. Check to enable ATPC.

Status of Local Tx Mute function.
ATPC Power Range.
By clicking on the icon the

Remote ATPC Tx Threshold.
Alarm Severity Profile menu
Default value is -55 dBm.
opens, which allows to associ-
ate to the radio channel a spe-
cific alarm profile. Select one Select in the RSL Driving Criteria
Alarm Profile in the Profile field the suitable valueonly for
Name list (4 alarm profiles are MPT-HC. In 1+1 FD and HSB con-
listed) and click Apply. Tick figurations both the transmitters
the Show details check box to can be driven by the lowest or by
see the severity associated to the highest RLS values of the two
each alarm. remote demodulators.
Figure 567. MPT Access Card Provisioning, Presetting Mode (Sheet 2 of 2)

Reference Channel Spacing.
Displays reference channel
spacing based on the modula-
Mode. tion mode and the modulation
Select from the dropdown list. range. Select from the drop-
down list.
Select the spectral efficiency

class to be set as reference:
None, Old ETSI mask or New
ETSI mark.
Modulation.
Select the lowest modulation Choose in the Supported
scheme. Modulation field all the modu-
lation schemes to be used with
the Adaptive Modulation. The
modulation schemes (from the
lowest to the highest scheme)
Manual Operation. must be contiguous.
When checked, allowed user Note: With MPT-MC max.
to select and test a specific scheme is 128 QAM.
modulation scheme.
Current Modulation. The Remote Switching

Read Onyl Field. Displays Threshold field is not
modulation scheme the radio supported.
is currently using.
Link Identifier Confguration.
Forced Modulation.
Check to enable radio ID mis-
Select modulation scheme
match function.
(one from the Modulation
Range selected) to test. When Expected Identifier.
activated by the Apply button, Enter number from 1 to 255 for
radio is forced to operate using receiver ID. Must match trans-
selected modulation scheme. mitter ID at other end of hop.
Sent Identifier.
PPP RF. Enter number from 1 to 255 for
Check to enable PPP RF port. transmitter ID. Must match
When not checked (disabled) user cannot change: associated receiver ID at other
- Routing IP Protocol end of hop.
- OSPF Area
- Remote Address
Figure 568. MPT Access Card Provisioning, Adaptive Modulation Mode (Sheet 1 of 2)

Tx RF Frequency is automati-
Select the frequency separation cally entered by ODU when
from the dropdown list. ODU is connected to MSS. If
the ODU is not connected to
the MSS, enter the Tx RF fre-
quency, within allowed range.
Displays range of Tx RF frequencies
that may be entered.
Read Only Field.
Displays Rx RF frequency.
Result of calculation:
The Tx Power function allows the Rx Freq - Tx Freq = Shifter Freq.
operator to select the transmitter
output power of each modulation Select in the RSL Driving
scheme. The default level is the Criteria field the suitable value.
expected output power. The mini- In 1+1 FD and HSB configura-
mum and maximum range of each tions both the transmitters can
modulation scheme is shown in be driven by the lowest or by the
parenthesis (min XX- max YY). highest RLS values of the two
remote demodulators.
Check to enable the Tx output

By clicking on the icon the Alarm power out of ODU.
Read Only Field.
Status of Local Tx Mute
function.
Figure 569. MPT Access Card Provisioning, Adaptive Modulation Mode (Sheet 2 of 2)

5.2.2.2.7 Provision ASAP Card
See Figure 570. and follow the steps to provision the ASAP Card.
Figure 570. ASAP Card Provisioning
The configuration of the ASAP unit is divided in four tab-panels:
– E1 Layer
– IMA Layer
– ATM Layer
– ATM PW Layer
For the configuration of the tab-panels refer to paragraph 3.15 on page 407.

5.2.2.2.8 Provision AUX Card
See Figure 571. and follow the steps to provision the AUX Card.
Figure 571. AUX Card Provisioning
The configuration of the AUX unit is divided in two tab-panels:
– Settings
– External Points
For the configuration of the tab-panels refer to paragraph 3.17 on page 429.

5.2.2.3 Provision Synchronization
All the NEs radios in the network must be synchronized to the same clock. One radio in the network is
provisioned Master. All other radios in the network must be provisioned Slave. The slave radios all sync
to the clock provided by the master.
For the Synchronization configuration refer to par. 3.10 on page 362.
In Figure 572 is given an example of a Master NE Synchronization by an E1 stream.
Figure 572. Provisioning Master with E1/T1 port as Primary Source

5.2.2.4 Provision NTP protocol
This menu allows to enable the NTP (Network Time Protocol).
Figure 573. Provisioning NTP protocol
Put a check mark in the NTP protocol field to enable the protocol and write in the Main Server address
field the IP address of the server, which is in charge to distribute the time to all the NEs in the network.
In the Spare Server address field write the IP address of the Spare Server, if any.
The Server reachability field is a read-only field, which shows the reachability of the NTP servers. The
following information can appear:
– "Main server reachable"
– "Spare server reachable"
– "None servers reachable"
– "Both servers reachable"
Click on Apply to send to the NE the NTP Configuration.
Refresh push-button can be used to update the screen.

5.2.2.5 Provision NE Time
The user can synchronize the NE time from either the PC/laptop or Network Time Protocol (NTP) servers.
Time and date provisioning is accomplished using the NE Time Configuration screens. See Figure 574.
and follow the steps to provision Network Equipment Time.
Click to display pop-up dialog

for NE Time configuration.
If NPT Protocol is disabled,

when checked, enables func-
tion to synchronize Operating
System and Network Equip-
ment Times.
3
Figure 574. NE Time Provisioning

5.2.2.6 Provision VLAN (if required)
To provision the VLAN management, if required, refer to par. 3.19 on page 469.
5.2.2.7 TDM Cross-Connections
The cross-connections screen is used to configure switching of packetized data through the Core-E Card.
The valid cross-connections are:
– PDH to RADIO
– PDH to ETH
– ETH to RADIO
– RADIO to RADIO
To create the TDM cross-connections refer to par. 3.4.5 on page 220.
5.2.2.8 STM-1 Cross-Connections
– SDH to RADIO
– RADIO to RADIO
To create the STM-1 cross-connections refer to par. 3.4.5.4 on page 237.
5.2.2.9 ATM Cross-Connections
– ASAP to RADIO
– RADIO to RADIO
– RADIO to ETH
– ASAP to ETH
To create the ATM Cross-connections refer to par. 3.4.5.6 on page 241.

5.2.2.10 AUX Cross-Connections
From the Configuration menu select AUX Cross-Connections.
Valid Cross Connections:
– Local User Service Cross-Connection
– Pass-through User Service Cross-Connection
Figure 575. Auxiliary Cross Connections menu

5.2.2.11 Provision System
See Figure 576. Follow the steps to provision the system parameters as explained in par. 3.4.4 on page
217.
Figure 576. System Setting

5.2.2.12 Provision LAG
See Figure 577. Follow the steps to provision the LAG.
For the LAG creation refer to par. 3.4.10
Figure 577. LAG creation

5.2.2.13 Provision Local NE IP Address
See Figure 578. Follow the steps to enter the NE IP address, allowing the network to communicate with
the NE.
Click to display pop-up dialog

for the IP configuration.
4
Enter NE IP Address.
5
Apply the IP Address.
Note
After IP address change, the NE restarts.
Figure 578. Local Configuration Provisioning

5.2.2.14 Provision TMN Ethernet Port
See Figure 579. Follow the steps to provision TMN Ethernet Port on the Core-E unit.
4
Enable TMN
Ethernet
5
Enter IP
address
6
Select Static Routing for manual 7
routing. Select OSPF (Open Enter IP Mask and
Shortest Path First protocol) for click on Apply
automatic routing. 8
Click on the Alarm Profile icon to open the Alarm Severity
Profile menu to associate to the TMN Ethernet port a
specific alarm profile. Select one Alarm Profile in the
Profile Name list (4 alarm profiles are listed). Tick the
Show details check box to see the severity associated to
each alarm.
Figure 579. TMN Ethernet Port Configuration Provisioning

5.2.2.15 Provision Ethernet Port 4 for TMN (if required)
See Figure 580. Follow the steps to provision Ethernet Port 4 for TMN on the Core-E unit to carry SNMP
data.
2
3
4
Enable the
TMN Port 4
5
Enter IP
address
6
Select Static Routing for manual 7
routing. Select OSPF (Open Enter IP Mask and
Shortest Path First protocol) for click on Apply
automatic routing. 8
Click on the Alarm Profile icon to open the Alarm Severity
Profile menu to associate to the TMN Ethernet port a
specific alarm profile. Select one Alarm Profile in the
Profile Name list (4 alarm profiles are listed). Tick the
Show details check box to see the severity associated to
each alarm.
Figure 580. Ethernet Port 4 Configuration Provisioning

5.2.2.16 Provision TMN in-band
See Figure 581. Follow the steps to provision TMN In-band.
3 5 6
4
7 8
Figure 581. TMN In-band Configuration Provisioning
[3] Enable.
[4] IP address and subnet: default 10.0.3.2/24 for interface #1 and 10.0.4.2/24 for interface #2
[5] VLAN ID: default 1000 for interface #1 and 1001 for interface #2
[6] List of User Ethernet interfaces where transmit/receive TMN In-Band traffic: default None (multiple
selection with the mouse can be done)
[7] OSPF enable/disable: default disabled for both interfaces
[8] Area ID in case of OSPF protocol enabled: default 0.0.0.0

5.2.2.17 Provision IP Static Routing
See Figure 582. Follow the steps to provision.
Click now to display pop-up dialog for

the IP Static Routing Configuration.
Route to specific IP address
5
Input IP Address. IP Mask.
6 7
8
IP interface to a host or network.
Typically used to a spur to
interface a host over the RF path.
In this scenario, the Default
Gateway IP Address is 0.0.0.0
9
List of RF path
and the IP Mask (greyed out) is
directions.
0.0.0.0. Also typically used at an
Click to view
end terminal in a radio link for
drop down list.
interface with the network.
Create new or change

10
existing IP static routes.
Figure 582. IP Static Routing Provisioning

5.2.2.18 Provision OSPF Static Routing
See Figure 583. Follow the steps to provision Open Shortest Path First (OSPF) protocol static (automatic)
routing.
Figure 583. OSPF Static Routing Provisioning

6 Maintenance and Trouble-clearing
6.1 Introduction
This section contains information and procedures to aid in restoring the equipment to its proper operating
condition after it has been determined that a problem exists.
The following warnings and cautions apply while operating, performance testing, troubleshooting, or
repairing the 9500 MPR-E series radios.
Short circuits in low-voltage, low-impedance dc circuits can cause

severe arcing that may result in burns or eye injury. Remove rings,
watches, and other metal jewelry while working with primary circuits.
Exercise caution to avoid shorting power input terminals.
Units with the electrostatic-sensitive (ESS) symbol contain ESS

devices. Store these units in an antistatic container when not in use,
and anyone handling a unit should observe antistatic precautions.
Refer to the Special Precautions pages in the front of the instruction
book for detailed handling information.
Note
Ensure that all antennas are properly aligned and waveguide is in

good physical condition.
Note
Before performing procedures that might in any way affect transmission,

it is recommended that the person performing the procedure
understand the Rules and Regulations pertaining to the equipment
and be properly authorized to operate the equipment.

Maintenance and Trouble-clearing 3DB 18793 AAAA Issue 1 793/876
6.2 Maintenance Philosophy
This section provides information and procedures for equipment maintenance down to the Card level.
Card repair is not covered in this manual.
The use of maintenance procedures in this section may result from failure of a periodic check, an alarm
indication, or unacceptable performance.
6.3 Personal Computer (PC)/Laptop

Connect the RJ45 Interface cable between WebEML connector on the Core-E Card and the PC.
6.4 Troubleshooting
This section provides guidance on:
– Before Going to Site Checklist
– Troubleshooting Basics
– Troubleshooting Path Problems
– Troubleshooting Configuration Problems
– Troubleshooting Ethernet Problems
– Troubleshooting TMN Problems
6.4.1 Before Going to Site Checklist

Where possible, before going to site obtain the following information:
– Does the fault require immediate attention?
– Determine who is the best-placed person to attend the fault.
– Confirm the nature and severity of the reported fault, its location, 9500 MPR-E type, frequency band,
high/low end ODU, capacity modulation and configuration (nonprotected, protected, diversity). Ask:
• Is just one 9500 MPR-E link affected, or a number of links in the same geographical area?
• Is the path down completely or is traffic passing but with a BER alarm?
• Is only one or a number of tributaries affected?
• Could the fault be in the equipment connected to 9500 MPR-E, rather than in 9500 MPR-E?
Are there alarms on other, connected equipment?
• Is it a hard or intermittent fault?
• Do alarms confirm which end of an alarmed link is faulty?
– Could the weather (rain, ice, high wind, temperature) be a factor in the reported fault?

794/876 3DB 18793 AAAA Issue 1 Maintenance and Trouble-clearing
Note
If the fault suggests a rain fade or other weather related fade

condition and it matches the prevailing weather conditions, do
not take any action until the weather abates.
– Does link history suggest any fault trends?
• Does the fault history for the link indicate a likely cause?
• Is the 9500 MPR-E link newly installed?
• Has there been any recent work done on the link?
– Ensure that you have with you:
• Appropriate spares. Where an equipment failure is suspected, these should include replace-
ment Cards/plug-ins and ODU. If an ODU is suspected then local/national climbing safety
requirements must be adhered to.
• A laptop PC loaded with WebEML, and an Ethernet cable. If an Ethernet connection is to be

used, you need the 9500 MPR-E Node/Terminal IP address and also the addresses for any
remote sites to be accessed.
• If login security has been enabled, you need the ‘engineer’ password for the local and also any
remote sites to be accessed.
• Any special test equipment that may be needed, such as a BER tester.
• Toolkit.
• Key(s) for access to the site.
6.4.2 Troubleshooting Basics

This section provides general guidance on 9500 MPR-E troubleshooting:
– Check front-panel LED indications. These provide summary alarm indications, which can help
narrow down the location and type of failure. Refer to Operation section for details.
• Where a Status LED on a plug-in is off (unlit), but power to the MS is confirmed by LEDs on
other plug-ins, check the seating of the affected plug-in.
– Check Main Screen. When logging into 9500 MPR-E with WebEML, the opening screen is the Main
Screen. Use the information provided in menu Diagnosis → Alarms → NE alarms and in menu
Diagnosis → Log Browsing → Event Log to check for severity and problem type.
Refer to Table 51., Table 52. and Table 53. for probable cause and recommended action.

Table 51. Alarm Matrix
Configuration/
Alarm
Equipment Alarm Description Most Probable Cause Action
1+0 1+1
EPS
Core-E Card Card Fail Major Minor Core-E card failed Replace Core-E Card
Equipment Mismatch N/A Minor Card in slot does not match Install correct configured
card configured in Core-E card
memory
Card Missing N/A Minor Core-E card is missing from Install Core-E Card in slot
slot
SFP missing alarm Major Minor The SFP optional plug-in is Install the plug-in in the
provisioned, but not present SFP slot
Unconfigured Equip- N/A Minor Card in slot is not provi- Provision card
ment sioned (enabled)
LOS on ETH TMN Minor Minor No Ethernet input signal Check link partner and
Interface detected on ETH 4 on Core- cable between link partner
E Card and ETH 4 connector
PPP IP Fail Minor Minor
LOS on Gigabit ETH Major Minor Loss of Ethernet is detected Check link partner and
Interface on ETH 1-4 on Core-E Card cable between link partner
and ETH 1-4 connector
Firmware Download Minor Minor Status of download Wait for downloading to

In Progress complete
LOS on Sync Inter- Minor Minor No sync clk detected at Check sync source and
face Sync in port on Core-E Card cable between sync
source and Sync in port
Degraded Signal on Minor Minor Sync clk errors detected at Check sync source for
Sync Interface Sync in port on Core-E Card errors
License Mismatch for Major Major Wrong flash card installed Install correct flash card
Equipment Provi- on Core-E Card for license
sioned
Underlying Resource Major Major On detection of card failure Replace Core-E card
Unavailable (URU) the E1 port, Ethernet port,
Radio port objects emit a
communication Alarm notifi-
cation showing the trans-
mission resources are
affected by the equipment
failure

Configuration/
Alarm
1+0 1+1
EPS
E1 Access Card Fail Major Minor Failure of E1 Access Card Replace E1 Access Card
Card
Equipment Mismatch Major Minor Card in slot does not match Install correct configured
Card configured in Core-E card
memory
Card Missing Major Minor E1 Access Card is missing Install E1 Access Card in
from slot slot
Unconfigured Equip- Major Major Card is not Enabled on the Enable card
ment Settings screen
LOS on PDH Tribu- Major Minor No E1 input signal detected Check E1 source and/or
tary on any one or more of 32 cable
lines
Degraded Signal Minor Minor Low quality sync signal for Replace E1 Access Card
E1 Access Card
AIS on PDH Tributary Major Major AIS detected by the receive Check for upstream E1
(RX) circuits on one or more E1 source for errors
lines, indicating upstream
failure
AIS on PDH Tributary Major Major AIS detected on one or Check E1 source
(TX) more E1 lines at input to
PDH 32xE1 Access Card
Loss of CESoETH Major Major Packets are not being 1. Check/troubleshoot

Frame received by the emulation far end alarms
circuits 2. Replace alarmed E1
Access Card

Underlying Resource Major Major On detection of card failure Replace E1 Access card
Unavailable (URU) the E1 port objects emit a
failure
STM-1 Access Card Fail Major Minor Failure of STM-1 Access Replace STM-1 Access
Card Card Card
Equipment Mismatch Major Minor Card in slot does not match Install correct configured
memory
Card Missing Major Minor STM-1 Access Card is miss- Install STM-1 Access
ing from slot Card in slot

Configuration/
Alarm
1+0 1+1
EPS
Unconfigured Equip- Major Major Card is not Enabled on the Enable card
LOS on STM-1 Tribu- Major Minor No STM-1 input signal Check STM-1 source and/
tary detected on any one or or cable
more of 32 lines
Tx Out of STM-1 Major Minor Loss of STM-1 frame align- Check STM-1 source
Frame (OOF) ment on each incoming
STM-1 channel detected
according to G.783
Tx Loss of STM-1 Major Minor Loss of frame from external Check STM-1 source
frame (LOF) line side
Tx Regeneration sec- Major Minor RS-TIM (regeneration sec- Check STM-1 source
tion trace identifier tion trace identifier mis-
mismatch (J0) match) detected on each
STM-1 channel from exter-
nal line which is known as J0
byte in regeneration section
overhead
Tx Multiplex section Major Minor Multiplex Section AIS (MS- Check STM-1 source
alarm indication sig- AIS) specified as all "1"s in
nal (MS-AIS) the entire STM-1 from exter-
nal line, excluding the STM-
1 RSOH
Tx Multiplex section Major Minor From external line. The Mul- Check STM-1 source
remote defect indica- tiplex Section Remote
tion (MS-RDI) Defect Indication (MS-RDI)
is used to return an indica-
tion to the transmit end that
the received end has
detected an incoming sec-
tion defect or is receiving
MS-AIS
Tx Excessive BER Major Minor In the direction from exter- Check STM-1 source
(HBER) nal line, when the line BER
exceeds 5*10-5
Sync Fail Major Minor Managed only if the Check STM-1 source
addressed STM-1 has been
configured as primary/sec-
ondary synchronization
source
Sync Degraded sig- Major Minor Managed only if the Check STM-1 source
nal addressed STM-1 has been
configured as primary or
secondary synchronization
source
Rx Loss of STM-1 Major Minor Loss of frame to external Check STM-1 source
frame (LOF) line side

Configuration/
Alarm
1+0 1+1
EPS
Rx Multiplex section Major Major Multiplex Section AIS (MS- Check STM-1 source
alarm indication sig- AIS) is specified as all "1"s in
nal (MS-AIS) the entire STM-1 to external
line, excluding the STM-1
RSOH
Rx Excessive BER Major Major In the direction to external Check STM-1 source
(HBER) line, when the line BER
exceeds 5*10-5
Loss of CESoETH Major Major Packets are not being 1. Check/troubleshoot

Frame received by the emulation far end alarms
circuits 2. Replace alarmed
STM-1 Access Card

Underlying Resource Major Major On detection of card failure Replace STM-1 Access
Unavailable (URU) the STM-1 port objects emit card
a communication Alarm
notification showing the
transmission resources are
failure
16E1DS1 ASAP Card Fail Major - Failure of ASAP Card Replace ASAP Card
Card
Equipment Mismatch Major - Card in slot does not match Install correct configured
memory
Card Missing Major - ASAP Card is missing from Install ASAP Card in slot
slot
Unconfigured Equip- Major - Card is not Enabled on the Enable card

Firmware Download Minor - Status of download Wait for downloading to

Loss Of Signal (LOS) Major - Loss of signal on each Check E1 source and/or
incoming E1 signal cable
(detected according to ITU-
T G.775-sect.4)
Tx Alarm Indication Major - Alarm Indication Signal Check E1 source

Signal (Tx AIS) detected on each incoming
E1 signal (Tx side)
T G.775-sect.4)

Configuration/
Alarm
1+0 1+1
EPS
Loss Of Frame (LOF) Major - Loss of frame on each Check to CRC4 multi-
incoming E1 signal frame alignment of the Far
(detected according to ITU- End equipment
T G.706-sect.4)
Loss of Cell Delinea- Major - Loss of ATM cell delineation Check the ATM scram-
tion (LCD) on each incoming E1 signal, bling of the Far End equip-
when the E1 port is used as ment
physical layer for ATM
T I.432)
Loss of IMA Frame Major - Loss of IMA Frame on each Check the IMA configura-
(LIF) incoming E1 signal, when tion of the Far End equip-
the E1 port is used as IMA ment
link (detected according to
IMA Standard AF-PHY-
0086.000)
Link Out of Delay Major - It reports the event that, Check the synchroniza-
Synchronisation when the E1 port is used as tion of the Far End equip-
(LODS) IMA link, it is not synchro- ment
nized with the other links
within the IMA group
(detected according to IMA
Standard AF-PHY-
0086.000)
RDI/Link Failure Major - It reports, when the E1 port Check the Far End equip-
is used as IMA link, the OR ment
of other alarms that are fore-
seen by IMA Standard AF-
PHY-0086.000:
– RFI-IMA
– Tx-Mis-Connected
– Rx-Mis-Connected
– Tx-Unusable-FE
– Link Rx-Unusable-FE

Configuration/
Alarm
1+0 1+1
EPS
IMA Group Trail Sig- Major - It reports, for a configured Check the Far End equip-
nal Fail (TSF) IMA Group, the event that its ment
Group Traffic State Machine
is 'down', that is NE and FE
Group State Machine are
both NOT in "operational"
state (IMA Standard AF-
PHY-0086.000)
IMA Group TSFAlarm is
also generated by OR of the
following alarms (IMA Stan-
dard AF-PHY-0086.000):
– Tx-Unusable-FE
– Link Rx-Unusable-FE
– Group Start-up-FE
– Group Config-Aborted
– Group Config-
Aborted-FE
– Group Insufficient-
Links
– Group Insufficient-
Links-FE
– Group Blocked-FE
– Group GR-Timing-
Mismatch
Underlying Resource Major Major On detection of card failure Replace 16E1DS1 ASAP
Unavailable (URU) the E1 port objects emit a Card
failure
Fans Unit Card Fail Major – Fan failed Replace fan unit
Card Missing Major – Fan unit is missing from slot Install fan unit
Unconfigured Equip- Minor Minor Unit is not Enabled on the Enable fan unit

Table 52. Modem Card and ODU300 Alarm Matrix
Configuration/Alarm

1+0 1+1 1+1
HS FD
Modem Card Card Fail Major Minor Minor Modem Card failed Replace Modem Card
Equipment Mismatch Minor Minor Minor Card in slot does not Install correct config-
match card configured ured card
in Core-E memory
Card Missing Major Minor Minor Modem Card is missing Install Modem Card in
from slot slot
Unconfigured Equip- Minor Minor Minor Card is not Enabled on Enable card
ment the Settings screen
PNU Cable Loss Major Minor Minor Bad cable connection Check/repair IF cable
at IF in/out connector connection on alarmed
on Modem Card Modem Card
Loss of Radio Frame Minor Minor Minor Far end problems, RF 1. Switch far end
path problems, or local equipment (in a
circuit failures have protected system).
caused BER to If alarm clears,
increase to the point replace far end off-
that frames are being line Modem Card.
lost 2. Check/troubleshoot
far end alarms
3. Replace alarmed
Modem Card
Loss of Alignment N/A Minor Minor Delay between main 1. Replace main Radio
and protect RF paths Modem Card
detected 2. Replace protect
Modem Card
3. Replace main ODU
4. Replace protect ODU
Demod Function Fail Major Minor Minor Internal receive circuit Replace Modem Card
failure
High BER Major Minor Minor Bit Error Rate threshold 1. Verify RF path is
(10E-4) exceeded on clear, antenna is
RCVR input circuits on aligned, and no
modem existing weather-
related problems
2. Verify RSL is above
RCV threshold.
If not – check
upstream transmitter
output/troubleshoot
transmitter
Early Warning N/A Minor Minor 10E-9 BER detected No action is required at
this time. Monitor
receive signal for
increased degrading

Configuration/Alarm

1+0 1+1 1+1
HS FD
Link Identifier Mis- Major Major Major Link identifier number Set numbers at both
match provisioned on Modem ends of hop to match
Card settings screen is
different from link iden-
tifier number provi-
sioned at other end of
hop
TCA on Radio Link N/A N/A Major Alarm threshold Switch far end equip-
exceeded on standby ment (in a protected sys-
Modem Card tem). If alarm clears,
replace far end off-line
Modem Card
TCA on Radio Hop Major N/A Minor Alarm threshold

exceeded on standby
Modem Card after
switching from main to
standby
UAT on Radio Link N/A N/A Major 10 consecutive SES Switch far end equip-
(unavailable time ment (in a protected sys-
period) detected on tem). If alarm clears,
main Modem Card replace far end off-line
Modem Card
UAT on Radio Hop Major N/A Minor 10 consecutive SES

(unavailable time
period) detected on
standby Modem Card
after switching from
admin to standby
Firmware Download Minor Minor Minor Download status Wait for downloading to
Degraded Signal Minor Minor Minor Low quality sync signal Replace Modem Card
from Modem Card
License Mismatch for Major Major Major Modem card type does Replace Modem Card
Equipment Provi- not match card type with correct card type
sioned stored in memory on
the Core-E Card flash
card
Underlying Resource Major Major Major On detection of card Replace Modem Card
Unavailable (URU) failure the Radio port
objects emit a commu-
nication Alarm notifica-
tion showing the
transmission
resources are affected
by the equipment fail-
ure

Configuration/Alarm

1+0 1+1 1+1
HS FD
ODU300 Card Fail Major Minor Minor ODU failed Replace ODU
Equipment Mismatch Major Minor Minor ODU does not match Replace ODU
ODU configured in
Core-E memory
RCV Function Fail Major Minor Minor ODU receiver circuit Replace ODU
failed
RF Frequency Mis- Major Minor Minor Frequency out-of- Re-configure frequency

match range of configured Tx
frequency
Shifter Frequency Major Minor Minor Configured shifter Re-configure shifter

Mismatch value not supported by value
ODU
TX Power Mismatch Minor Minor Minor Configured TX power Re-configure Tx power

value not supported by value
ODU
Software Mismatch Minor Minor Minor Software version on Download correct soft-
ODU does not match ware version
software version on
Core
ODU Not Responding Minor Minor Minor Loss of communication 1. Replace ODU
with ODU 2. Replace alarmed
Modem Card

Table 53. MPT Access Peripheral Card and MPT-HC/MPT-HC V2 Alarm Matrix
Configuration/Alarm

1+0 1+1 1+1
HS FD
MPT Access Card Fail Major - - MPT Access Card Replace MPT Access
Card failed Card
Equipment Mismatch Major - - Card in slot does not Install correct config-
match card configured ured card
in Core-E memory
Card Missing Major - - MPT Access Card is Install MPT Access

missing from slot Card in slot
Unconfigured Minor - - Card is not Enabled on Enable card

Equipment the Settings screen
MPT Power Supply Major - - Power Supply Failure Check/repair the cable
Failure connection. If ok,
replace MPT-HC
Loss Of Ethernet Sig- Major - - Loss of the incoming Check the cable con-
nal Ethernet signal (the nection. If ok, replace
signal is missing) or a the MPT Accerss unit
communication prob-
lem with the remote
peer (i.e. the communi-
cation has not been
established for physi-
cal problem on cable or
interface -> link down)
Ethernet Link Error Minor - - Partial failure of electri- Check the cable con-
cal or optical cable for nection. If ok, replace
the GbEth port the MPT Accerss unit
Degraded Signal of Minor - - This alarm is active Check the cable

the MPT Ethernet only when the interface
Interface is selected as Primary
or Secondary synchro-
nization source
Firmware Download Minor - - Download status Wait for downloading to


Configuration/Alarm

1+0 1+1 1+1
HS FD
MPT-HC/ Card Fail Major Minor Minor MPT-HC failed Replace MPT-HC
MPT-HC V2
Equipment Mismatch Major Minor Minor MPT-HC does not Replace MPT-HC
match MPT-HC config-
ured in Core-E memory
RCV Function Fail Major Minor Minor MPT-HC receiver cir- Replace MPT-HC
cuit failed
RF Frequency Mis- Major Minor Minor Frequency out-of- Re-configure frequency

frequency
Shifter Frequency Major Minor Minor Configured shifter Re-configure shifter

MPT-HC
TX Power Mismatch Minor Minor Minor Configured TX power Re-configure TX power

MPT-HC
Modulation parame- Major Minor Minor The modulation param- Change the modulation
ters Mismatch eters already config- parameters
ured and stored in the
MPR DB are not actu-
ally supported by MPT
Software Mismatch Minor Minor Minor Software version on Download correct soft-
MPT-HC does not ware version
match software version
on Core
MPT-HC Not Minor Minor Minor Loss of communication 1. Replace MPT-HC

Responding with MPT-HC 2. Replace alarmed
MPT Access Card
Loss of Radio Frame Major Minor Minor Far end problems, RF 1. Switch far end
that frames are being line MPT-HC.
far end alarms
3. Replace alarmed
MPT-HC
Loss of Alignment N/A Minor Minor Delay between main 1. Replace main MPT-
and protect RF paths MS
detected 2. Replace protect MPT-
MS

Configuration/Alarm

1+0 1+1 1+1
HS FD
Demod Function Fail Major Minor Minor Internal receive circuit Replace MPT-HC
failure
High BER Major Minor Minor Bit Error Rate threshold 1. Verify RF path is
(10E-4) exceeded clear, antenna is
aligned, and no
existing weather-
related problems
RCV threshold.
If not – check
output/troubleshoot
transmitter
Early Warning N/A Minor Minor 10E-9 BER detected No action is required at
this time. Monitor
receive signal for
increased degrading
Link Identifier Mis- Major Major Major Link identifier number Set numbers at both
match provisioned is different ends of hop to match
from link identifier num-
ber provisioned at
other end of hop
MPT Loop Communi- Minor Minor Minor Communication prob- Check the radio hop
cation alarm lem between the local
MPT and the remote
MPT for all the func-
tionalities requiring a
communication loop
(ATPC, ACM, Pre-dis-
torsion)
Sync Degraded sig- Minor Minor Minor This alarm can raise if Check the radio hop
nal the addressed Radio
interface has been con-
figured as primary/sec-
ondary
synchronization
source. It is active if the
frequency of the clock
recovered from radio
Rx signal is mistuned

Configuration/Alarm

1+0 1+1 1+1
HS FD
Coupling port Loss of N/A Minor Minor For the MPT Coupling Check the cable
Ethernet Signal optical port:
- the loss of incoming
Ethernet signal (the
signal is missing);
- a communication
problem with the
alternate MPT (i.e. the
communication has
not been established
for physical problem
on cable or interface
-> link down).
When this alarm is
raised, RPS is not
working
Coupling port Link N/A Minor Minor For the MPT Coupling Check the cable
Error optical port, the ratio
between the number of
received errored pack-
ets and the total num-
ber of received packets
is above a given
threshold.
When this alarm is
raised, RPS is not
working
Traffic port Link Error Minor Minor Minor For the MPT Traffic Check the cable
optical port, the ratio
between the number of
received errored pack-
ets and the total num-
ber of received packets
is above a given
threshold
MPT Tx Clock Failure Minor Minor Minor The MPT is not able to Check the radio hop
lock the air Tx symbol
rate to the NE Clock
TCA on Radio Link N/A N/A Major Alarm threshold Switch far end equip-
MPT-HC tem). If alarm clears,
MPT-HC
TCA on Radio Hop Major N/A Minor Alarm threshold

exceeded on standby
MPT-HC after switch-
ing from main to
standby

Configuration/Alarm

1+0 1+1 1+1
HS FD
UAT on Radio Link N/A N/A Major 10 consecutive SES Switch far end equip-
main MPT-HC replace far end off-line
MPT-HC
UAT on Radio Hop Major N/A Minor 10 consecutive SES

(unavailable time
period) detected on
standby MPT-HC after
switching from admin
to standby
Degraded Signal Minor Minor Minor Low quality sync signal Replace MPT-HC
from MPT-HC
PPP IP Fail Minor Minor Minor Point to point IP failure Check the settings

Table 54. MPT Access Peripheral Card and MPT-MC Alarm Matrix
Configuration/Alarm
1+0 1+1 HS
MPT-MC Card Fail Major Minor MPT-MC failed Replace MPT-MC
Equipment Mismatch Major Minor MPT-MC does not Replace MPT-MC

match MPT-MC config-
ured in Core-E memory
RCV Function Fail Major Minor MPT-MC receiver cir- Replace MPT-MC
cuit failed
RF Frequency Mis- Major Minor Frequency out-of- Re-configure frequency

frequency
Shifter Frequency Major Minor Configured shifter Re-configure shifter

MPT-MC
TX Power Mismatch Minor Minor Configured TX power Re-configure TX power

MPT-MC
Modulation parame- Major Minor The modulation param- Change the modulation
ters Mismatch eters already config- parameters
ured and stored in the
MPR DB are not actu-
ally supported by MPT
Software Mismatch Minor Minor Software version on Download correct soft-

MPT-MC does not ware version
match software version
on Core
MPT-HC Not Minor Minor Loss of communication 1. Replace MPT-MC

Responding with MPT-MC 2. Replace alarmed
MPT Access Card
Firmware Download Minor Minor Download status Wait for downloading to

Loss of Radio Frame Major Minor Far end problems, RF 1. Switch far end
that frames are being line MPT-MC.
far end alarms
3. Replace alarmed
MPT-MC
Demod Function Fail Major Minor Internal receive circuit Replace MPT-MC
failure

Configuration/Alarm
1+0 1+1 HS
High BER Major Minor Bit Error Rate threshold 1. Verify RF path is
(10E-4) exceeded clear, antenna is
aligned, and no
existing weather-
related problems
RCV threshold.
If not – check
output/troubleshoot
transmitter
Early Warning N/A Minor 10E-9 BER detected No action is required at

this time. Monitor
receive signal for
increased degrading
Link Identifier Mis- Major Major Link identifier number Set numbers at both
match provisioned is different ends of hop to match
from link identifier num-
ber provisioned at
other end of hop
MPT Loop Communi- Minor Minor Communication prob- Check the radio hop
cation alarm lem between the local
MPT and the remote
MPT for all the func-
tionalities requiring a
communication loop
(ATPC, ACM, Pre-dis-
torsion)
Sync Degraded sig- Minor Minor This alarm can raise if Check the radio hop
nal the addressed Radio
interface has been con-
figured as primary/sec-
ondary
synchronization
source. It is active if the
frequency of the clock
recovered from radio
Rx signal is mistuned
MPT Tx Clock Failure Minor Minor The MPT is not able to Check the radio hop
lock the air Tx symbol
rate to the NE Clock
TCA on Radio Link N/A N/A Alarm threshold Switch far end equip-
MPT-MC tem). If alarm clears,
MPT-MC

Configuration/Alarm
1+0 1+1 HS
TCA on Radio Hop Major N/A Alarm threshold

exceeded on standby
MPT-MC after switch-
ing from main to
standby
UAT on Radio Link N/A N/A 10 consecutive SES Switch far end equip-
main MPT-MC replace far end off-line
MPT-MC
UAT on Radio Hop Major N/A 10 consecutive SES

(unavailable time
period) detected on
standby MPT-MC after
switching from admin
to standby
Degraded Signal Minor Minor Low quality sync signal Replace MPT-MC
from MPT-MC
PPP IP Fail Minor Minor Point to point IP failure Check the settings
EPS – Equipment Protection Switching
LOS – Loss of Signal
RPS – Radio Protection Switching
RCV – Receiver
TCA – Threshold Crossing Alarm
UAT – Un-Available Time
– Check the basics first.
• For example, if multiple alarms are present, and these include power supply voltage or hard-
ware alarms, always check their cause before looking at resultant down-stream path failure or
path warning (signal) alarms.
• Similarly, if a path-related failure is indicated (no hardware or software alarms), investigate the
path. Go to the WebEML History screen (15 minute view) to check supporting data, such as low
RSL and incidence of intermittent pre-failure BER alarms, which if present are evidence of a
path-related failure.
– Check if symptoms match the alarm. Alarms reflect the alarm state, but in exceptional
circumstances an alarm may be raised because of a failure to communicate correctly with the alarm
source, or a failure in alarm management processing. Always check to see if symptoms match the
alarm, using LED indications and the WebEML.

– Check if recent work may be a cause. Recent work at the site may be a cause or contributing factor.
Check for a configuration change, software upgrade, power recycling (reboot), or other site work:
• Many hardware alarms are only initiated as a loss-of-communications alarm during a reboot,
software upgrade, or reconfiguration. By not being able to communicate with the Core-E, their
settings cannot be loaded. The fault may be at the hardware device (most likely), communi-
cations to it, or the Core-E.
• Hardware/software compatibility alarms will be raised when a new plug-in is installed that needs
a later version of 9500 MPR-E software.
• Hardware incompatible alarms will be raised when a plug-in is installed in a slot that has been
configured for a different plug-in.
– MSS before an ODU. If there is doubt about whether a fault is in the MSS or ODU, always replace
the MSS first; it is quicker and easier.
– Hot-pluggable. MSS cards are hot-pluggable. There is no need to power-down before replacing,
but traffic will be lost unless the plug-in is protected.
– Plug-in restoration time. Ensure adequate time is allowed for services to resume when a plug-in
is replaced.
6.4.3 Troubleshooting Path Problems

A path-related problem, with the exception of interference, is characterized by traffic being similarly
affected in both directions. Generally, if you are experiencing only a one-way problem, it is not a path
problem.
Note
A path extends from ODU antenna port to ODU antenna port.
– Normally a path problem is signalled by a reduced RSL, and depending on its severity, a high BER.
– Only in worst case situations, such as an antenna knocked out of alignment, will a path fail
completely, and stay that way.
– For weather-related problems, such as rain or ducting, the path problem will disappear as the
weather returns to normal.
6.4.3.1 Path Problems on a Commissioned Link
A path problem on an existing link, one that has been operating satisfactorily may be caused by:
– Weather-related path degradation
If BER alarms are fleeting/not permanent and RSL returns to its normal, commissioned level after
the alarm is cleared, rain, diffraction, or multipath fading is indicated. Rain fade is the likely cause
of fade for links 13 GHz and higher. Diffraction and multipath/ducting for links 11 GHz and lower. If
these alarms are persistent, there could be a problem with the link design or original installation.

– Changed antenna alignment or antenna feed problem
If RSLs do not return to commissioned levels after a period of exceptionally strong winds, suspect
antenna alignment. Also, check the antenna for physical damage, such as may occur with ice-fall.
For a remote-mounted ODU, check its antenna feeder.
– New path obstruction
Where all other parameters check as normal, and the path has potential for it to be obstructed by
construction works, view/survey the path for possible new obstructions.
– Interference from other signal sources
Interference usually affects traffic in just one direction. Unlike other path problems, RSL is not
affected. If suspected, check for new link installations at, or in the same geographical area, as the
affected site. Ultimately, a spectrum analyzer may have to be used to confirm interference, which is
not an easy task given the need to connect directly to the antenna port, after removing the ODU.
6.4.3.2 Path Problems on a New Link
For a new link, potential problems can extend to also include:
– Incorrect antenna alignment
One or both antennas incorrectly aligned. Refer to Installation alignment procedure on CD.
– Mismatching antenna polarizations
Given a typical polarization discrimination of 30 dB, for most links it is not possible to capture a signal
to begin the antenna alignment process.
– Incorrect path calculations
If the RSLs are too low or too high, antenna alignment is correct, and Tx power settings are correct,
check the path calculations used to determine the link performance. A good calculation match is +/
- 2 dB. Disagreements in excess of 3 dB should be investigated.
– Reflections
Reflection (path cancellation) problems may not have been picked up at the path planning stage, par-
ticularly if the survey was a simple line-of-sight. If suspected, resurvey the path.

6.4.4 Troubleshooting Configuration Problems
Configuration problems should only occur during the setup of a new link, or reconfiguration of an existing
link. The more common problems may be broadly categorized as:
– Compatibility Problems
The two alarms that may activate are Configuration Not Supported and SW/HW Incompatible:
• Configuration Not Supported: The plug-in installed is not enabled or is incorrect for the con-
figuration.
• SW/HW Incompatible: Typically raised when new hardware is plugged into an existing MSS
that has software from an earlier release. To remove the alarm, compatible 9500 MPR-E soft-
ware is required; install the latest software.
– Incorrect circuit connections
No alarms are activated for incorrect circuit connections. An incorrect assignment means the
expected end-to-end circuit connectivity will not happen. Re-check circuit assignments for all nodes
carrying the lost circuit(s).
Take extra care when configuring ring circuits.
– Incorrect ID naming and commissioning
All traffic-carrying circuits must have a unique flow ID for the cross-connect capability to operate.
– Incorrect/incompatible trib settings
Trib line interface settings incorrect, or line levels incompatible. While no alarm activates for an incor-
rect setting, its effect may result in line levels being too low (LOS alarm), or too high, resulting in a
high BER.
6.4.5 Troubleshooting Ethernet Problems

This section gives general guidance on troubleshooting problems related to the four Ethernet ports on the
Core-E Card.
The most common Ethernet problems are network and connectivity related and therefore always check
the following first:
– for User and NMS ports, verify link partner capability, provisioning, and connection
– for Radio ports, verify the cabling between ODU and MSS.
In order for the green Link LED to light:
1) Cable must be connected to Ethernet port
2) Ethernet port must be enabled (provisioned Enabled). Applicable for User and NMS ports
3) Speed and mode must be provisioned the same as the link partner.
The yellow LED opposite the green on the connector indicates activity only. The flashing yellow LED is
not an indicator of signal type or quality.

6.4.6 Troubleshooting TMN Problems
This section gives general guidance on troubleshooting TMN problems related to Ethernet port 4 on the
Core-E Card. Ethernet port 4 on the Core-E Card can be used to transport SNMP IP data. Troubleshoot
port 4 connectivity alarms the same as Ethernet ports 1-3.
The most common TMN problems are network related and first alert is normally observed by improper
operation at the SNMP master. Always check the following first:
– Verify master is properly registered in NE to receive traps.

– Verify SNMP version matches system requirements
– Verify correct community string and privileges
– Verify proper network routing.
Refer to Table 55. for detail TMN network troubleshooting.
Table 55. TMN Network Troubleshooting

Problem Possible Cause Possible Solution
Unusually slow communication in 1. Normal network management 1. There may be too many radios being
radio network traffic is saturating the communica- managed within a single region. Split the
tions channel. radio network management into differ-
ent regions and backhaul the traffic for
each region through separate channels.
2. Polling radios for PM data or 2. Poll the radios more slowly.
missed alarms too rapidly
3. Multiple remote software down- 3. Download to fewer radios at a time.
loads in process
4. IP traffic other than network 4. Configure external routers to allow
management traffic being routed only network management related traffic
through radio network through the Management network of the
radios. Dynamic route updates (OSPF,
RIP) may attempt to reroute high speed
traffic through the TMN network if a high
speed ink fails.
Unable to operate controls using To perform control operations, the Register the Manager as a craft device.
SNMP Manager must be registered as a Manager registration type can be
craft device. changed as needed to type ‘ct’ to allow
control operation and then be changed
back to ‘nml’ for normal operation.
Can Read SNMP objects but cannot 1. Incorrect community string 1. Use the correct community string.
Write to SNMP objects
2. If the TMN Interface is config- 2. Use the correct write community
ured for SNMPv2, the write com- string.
munity string is probably wrong.
No traps being received from NE 1. Manager not registered in NE to 1. Register Manager with NE.
receive traps
2. Communication failure in net- 2. Check network connectivity. Check
work redundant network paths and routing.
Traceroute (tracert) is useful for locating
path or routing faults.
Unable to communicate with the NE Possible communication path fail- Use traceroute (tracert) to help locate for
through the radio network (unable to ure or routing failure within the communication path or routing prob-
‘ping’ the NE). radio network. lems.
Can ‘ping’ the TMN Interface but can- If using SNMPv2, using the wrong Verify community string or username/
not communicate with the NE using community string. passphrase.
SNMP, or can only see a few SNMP
objects in the NE.

6.5 Card Removal and REPLACEMENT
The basic rules for installing plug-in cards are as follows:
Never install, change or remove a card without first connecting

to the shelf with an ESD grounding cable. Failure to do so may
cause ESD damage to the cards.
Plug-ins must be withdrawn and inserted using their finger-grip

fastener/pulls. Never withdraw or insert using attached cable(s).
Pulling on the cables may damage the cable, plug-in connector,
and/or plug-in card connector attachment.
When installing a plug-in, ensure its backplane connector is

correctly engaged before applying sufficient pressure to bring
the plug-in panel flush with the front panel. Improper alignment
can result in damaged pins on the backplane connector and/or
damage to the plug-in connector.
All slots must be filled with either a peripheral plug-in card or a

blank panel. Failure to do so will compromise EMC integrity and
cooling air from the fan.

Use extreme caution when connecting or disconnecting the ODU cable on the Modem Card.
The shelf battery voltage is present on the center conductor of the connector.
When removing or replacing a Modem Card, withdraw the card from the shelf before
disconnecting the cable to the ODU. Failure to follow these cautions may cause arcing
and/or possible power spikes that could affect traffic on other links installed at the node.
Removing an in-service card in an unprotected link will cause loss of traffic.

Removing an in-service card in a protected link requires switching the traffic
onto the standby (protection) channel.
– All plug-ins can be removed and installed with power applied.
If the main Core-E Card fails, traffic and platform data will switch to the spare
Core-E Card automatically. Do not remove power from the NE during the
removal and replacement of the failed main Core-E Card without
first reviewing/performing the following procedure:
a) Turn off NE power.
b) Remove failed main Core-E Card.
c) Turn on NE power.
d) Wait two (2) minutes.
e) Install replacement Core-E Card.

6.5.1 Core-E Card Removal and Replacement – Core-E Protected Radio
If the Main Core-E Card in slot 1 fails, traffic/services protection and control platform protection
switches to the spare Core-E Card in slot 2. Loopbacks and all other manual operations, such as
manual switch, tx mute, will be lost (deactivated). Alarms previously active will be newly
detected and reported via notification, with a new time stamp.
Verify the replacement Core-E Card meets the following compatibility rules:
– Main Core-E Card (in slot 1) and Spare Core-E Card (in slot 2) must be the same type.
– Local and far end Core-E Cards must use the same software version, but do not have to be the same
type.
6.5.2 Flash card replacement procedure

– First case: Core-E Protected
1) Get a spare FLASH CARD with the same sw-package release and license of the Main flash.
2) Remove the faulty FLASH CARD from the main Core-E and insert the spare one.
3) Insert the Core-E with the new FLASH CARD
4) The MIB (MAIN FLASH) will be automatically aligned with the MIB (SPARE FLASH).
– Second case: Core-E Not Protected (NB)
1) Get a spare FLASH CARD with the same sw-package release and license.
2) Remove the faulty FLASH CARD from the main Core-E and insert the spare one.
3) Insert the Core-E with the new FLASH CARD
4) Carry-out the RESTORE procedure.
ATTENTION (caution to avoid complete traffic loss)

Do not insert in the system a Flash Card the content of which is unknow.
You must be aware that, if a Flash Card with SW information different from that running in the
system is inserted “as it is”, the software download will be automatically carried out from the
Flash Card toward the System, thus causing a complete system crash.
Note
The license of the Spare Flash card can be different from the license of the Main Flash card.
Only the license of the Main Flash card manages the NE.
By changing the Main Flash card, also the MAC address changes:
in this case the cross-connection must be reviewed.

6.5.3 ODU300 or MPT-HC V2 or MPT-MC removal and replacement
Disconnect the cables from the Outdoor Unit to be replaced and connect them to the spare ODU.
6.5.4 MPT-HC removal and replacement

Disconnect the cables and the co-box from the MPT-HC to be replaced and connect them to the spare
MPT-HC.

6.6 Upgrade from Not Protected to a Protected Radio (with ODU300)
6.6.1 1+0 Adaptive Modulation to 1+1 HSB Adaptive Modulation and 1+1 EPS
Starting from a 1+0 configuration (see an example in the graphics below) perform the following procedure
to upgrade to a 1+1 HSB radio with Adaptive Modulation and 1+1 EPS.
This is an in-service but not a hitless procedure.
1) Plug-in E1 Access card in slot 4 (spare). An Unconfigured Equipment alarm displays.
2) Plug-in Modem card in slot 8 (spare). An Unconfigured Equipment alarm displays.
3) On WebEML Settings screen enable the E1 Access card in slot 4.
4) On WebEML Settings screen enable the Modem card in slot 8.
5) On WebEML Settings screen provision the E1 Access cards (slots 3 and 4) for 1+1 EPS Pro-
tection Type.
6) On WebEML Settings screen provision the Modem cards (slots 7 and 8) for HSB Protection
Type. Local station and remote station will observe 2 seconds sync loss.
7) Connect the E1 signal cables to the spare E1 Access card in slot 4.
8) Connect the new IDU/ODU cable to the spare Modem card in slot 8.
Note
After the changes a modification must be done in the TDM2Eth cross-connections of the remote
NE: the MAC address must be changed from “Unicast” to “Multicast” as explained in Figure 109., Figure
110. and Figure 111..

6.6.2 1+0 Static Modulation to 1+1 HSB Static Modulation and 1+1 EPS
Refer to the 1+0 Adaptive Modulation to 1+1 HSB Adaptive Modulation procedure above.
6.6.3 1+0 to 1+1 Frequency Diversity and 1+1 EPS
to upgrade to a 1+1 Frequency Diversity and 1+1 EPS.

2) Plug-in Modem card in slot 8 (spare). An Unconfigured Equipment alarm displays.
4) On WebEML Settings screen enable the Modem card in slot 8.
tection Type.
6) On WebEML Settings screen provision the Modem cards (slots 7 and 8) for 1+1 FD Protection
Type. Local station and remote station will observe 2 seconds sync loss.
8) Connect the new IDU/ODU cable to the spare Modem card in slot 8.
9) Properly configure the protection ODU.
Note
NE: the MAC address must be changed from “Unicast” to “Multicast” as explained in Figure 109., Figure

6.7 Upgrade from Not Protected to a Protected Radio (with MPT-HC/
MPT-HC V2 or MPT-MC)
Note
With MPT-MC only the 1+1 HSB configuration is available.
6.7.1 1+0 Adaptive Modulation to 1+1 HSB/FD Adaptive Modulation and 1+1 EPS
to upgrade to a 1+1 HSB radio with Adaptive Modulation and 1+1 EPS.
2) Plug-in MPT Access card in slot 8 (spare). An Unconfigured Equipment alarm displays.
4) On WebEML Settings screen enable the MPT Access card in slot 8.
tection Type.
6) On WebEML Settings screen provision the MPT Access cards (slots 7 and 8) for HSB or FD
Protection Type. The Local station and the Remote station will observe a short traffic impact.
8) Connect the new Power Supply cable and new Ethernet cable to the spare MPT Access card
in slot 8.

9) In case of 1+1 FD properly configure the protection MPT-HC.
Note
NE: the MAC address must be changed from “Multicast” to “Unicast” as explained in Figure 109., Figure
6.7.2 1+0 Static Modulation to 1+1 HSB/FD Static Modulation and 1+1 EPS
Refer to the 1+0 Adaptive Modulation to 1+1 HSB/FD Adaptive Modulation procedure above.

6.8 Downgrade from Protected to a Not Protected Radio (with
ODU300)
6.8.1 1+1 HSB Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation
Downgrading from 1+1 HSB and 1+1 EPS to 1+0 configuration is an out-of-service procedure.
The main channel must be in service including sync source before starting procedure.
1) Disconnect E1 signal cables from the spare E1 Access card in slot 4.

2) Disconnect IDU/ODU cable on the spare Modem card in slot 8.
3) On WebEML Settings screen for Modem cards (slots 7 and 8) enable Local Tx Mute for Channel
#1 and Channel #0.
4) On WebEML Settings screen for Modem cards (slots 7 and 8) set Protection Type to no Pro-
tection.
Protection Type. The Local station will observe a short traffic impact.
6) On WebEML Settings screen for Modem cards (slots 7 and 8) disable Local Tx Mute for Chan-
nel #1 and Channel #0.
7) On WebEML Settings screen for E1 Access cards (slots 3 and 4) set Protection Type to no Pro-
tection.
8) On WebEML Settings screen for spare E1 Access card (slot 4) set Equipment Type to EMPTY.
9) On WebEML Settings screen for spare Modem card (slot 8) set Equipment Type to EMPTY.
10) Remove spare Modem card (slot 8).
11) Remove spare E1 Access card (slot 4).
12) Power off and power on the NE.
Note

6.8.2 1+1 HSB Static Modulation and 1+1 EPS to 1+0 Static Modulation
Refer to the 1+1 HSB Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation procedure above.
6.8.3 1+1 FD to 1+0
Downgrading from 1+1 FD to 1+0 configuration is an out-of-service procedure.


2) Disconnect IDU/ODU cable on the spare Modem card in slot 8.
Note
Local AIS will remain active throughout remainder of procedure.
tection.
tection.
tection.
8) On WebEML Settings screen for spare Modem card (slot 8) set Equipment Type to EMPTY.
9) Remove spare Modem card (slot 8).
Note

6.9 Downgrade from Protected to a Not Protected Radio (with MPT-HC/
MPT-HC V2 or MPT-MC)
Note
With MPT-MC only the 1+1 HSB configuration is available.
6.9.1 1+1 HSB/FD Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation
Downgrading from 1+1 HSB/FD and 1+1 EPS to 1+0 configuration is an out-of-service procedure.
2) Disconnect IDU/ODU cables on the spare MPT Access card in slot 8.
Note
In case of 1+1 FD local AIS will remain active throughout remainder of procedure.
3) On WebEML Settings screen for MPT Access cards (slots 7 and 8) enable Local Tx Mute for
Channel #1 and Channel #0.
4) On WebEML Settings screen for MPT Access cards (slots 7 and 8) set Protection Type to no
Protection.

6) On WebEML Settings screen for MPT Access cards (slots 7 and 8) disable Local Tx Mute for
Channel #1 and Channel #0.
tection.
9) On WebEML Settings screen for spare MPT Access card (slot 8) set Equipment Type to
EMPTY.
10) Remove spare MPT Access card (slot 8).
Note
6.9.2 1+1 HSB/FD Static Modulation and 1+1 EPS to 1+0 Static Modulation
Refer to the 1+1 HSB/FD Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation procedure
above.
6.10 Cleaning
Do not use acid, alcohol, or brushes to clean cards because

damage to the silkscreen labeling and antistatic coating can
result. Cleaning should be confined to the removal of dust and
dirt using a damp cloth.
Cleaning should normally be confined to the removal of dust and dirt using a soft bristled (natural fiber)
brush and a low velocity blower (such as a vacuum cleaner with a plastic blower nozzle). Do not use acid
or synthetic bristled brushes to clean cards that contain electrostatic-sensitive components.

7 Line–up and Commissioning
This chapter details all phases necessary for the equipment line–up and commissioning.
Subject On page
Introduction 830
General 830
Safety–EMC–EMF–ESD norms and Cautions to avoid equipment damage 831
Conventions 831
Summary of the commissioning phases 832
General information about test bench drawings 833
Commissioning of STATION A – phase 1 (Turn up) 834
Commissioning of STATION B – phase 1 (Turn up) 836
Fine antenna alignment and preliminary checks – Stations A & B 836
End of commissioning phase 1 (Turn up) in STATION A 840
Commissioning station A – phase 2 (acceptance test) 841
Commissioning station B – Phase 2 (acceptance Test) 867
Final operations 867
Annex A: fine antenna alignment 867

Line–up and Commissioning 3DB 18793 AAAA Issue 1 829/876
7.1 Introduction
7.1.1 General
This chapter details all phases necessary for the equipment line–up, commissioning, and acceptance,
providing the user with the information needed to connect, power on, and perform a minimum turn–up of
a radio link comprising two 9500 MPR-E Rel.2.1.0 Network Elements.
It is assumed that, at both premises (Station A and Station B), the mechanical installation and cabling of
the INDOOR and OUTDOOR units is completed, the antennas are installed and pre–positioned, and the
MSS–ODU cable(s) has/have been connected to the MSS.
Any information needed to complete the above mentioned operations are out of the scope of this chapter.
For this purpose refer to the Installation section.
All the cables and measurement kits as described in Table 56. below are supposed to be available.
Table 56. Test and commissioning instruments

INSTRUMENT QTY CHARACTERISTICS
Laptop computer running the 1 SWP 9500 MPR-E V02.01.00

supervisory software
PDH Analyzer – Pattern Generator 1 E1 traffic
SDH Analyzer – Pattern Generator 1 STM-1 traffic
ATM Analyzer 1
V.11 Analyzer 1
Link Service kit cable (for MPT 1

antenna alignment)
In alternative, for Ethernet Data Optional

channel functionality tests:
– 1 PC + 1 Ethernet cable (for

ping function)
or
– 2 PCs (for ping function)
or
– 2 Ethernet Data Analyzers
Multi–meter 1 Voltmeter AC and DC – Loop tester
TRS 1 Test Result Sheet, available as separate document
The Alcatel–Lucent Software package SWP 9500 MPR-E V3.0.0 must have already been installed in the
PC used as the WebEML (WebEML) and the same software V3.0.0 must be already present as commit
version in the Flash Card of both two Network Elements.
Before proceeding with line–up and commissioning, ensure that you have the equipment and accesso-
riesrequired for that purpose.

830/876 3DB 18793 AAAA Issue 1 Line–up and Commissioning
7.1.2 Safety–EMC–EMF–ESD norms and cautions to avoid equipment damage
If not yet done, read whole Chapter 1 on page 29: it describes the operations and/or precautions to be
observed to safeguard operating personnel during the working phases, and to guarantee equipment
safety. Read them with accuracy before to start every action on the equipment.
7.1.3 Conventions
To simplify the description of actions, the following symbols are in use:
Symbol used Meaning
& Manual action
3 Check/Verify
WebEML⇒ On WebEML Select
⇒ Select a Menu item
→ Sub Menu item
The commissioning operations described in this document are for a radio link between a Station A and
a Station B.
If the network includes supervision, station A is the one located between the supervisory station and sta-
tion B (see figure below). Installation and commissioning begin at station A.
MSS MSS
Figure 584. Relative positions of stations A and B
WARNING: at the beginning of this procedure, the “local IP address” and “Ethernet IP address” of both
the NE 9500 MPR-E stations, are still set to default value “10.0.1.2” (as delivered from Alcatel–Lucent
factory). For this reason, their physical connection to the TMN network must be done after having changed
such addresses to correct values.

7.1.4 Summary of the line–up, commissioning, and acceptance phases
Note: The following procedure must be used for every Modem unit installed in MSS.
The commissioning procedure is summarized as follows:
[1] Turn up (phase 1)
1) Visual inspection and NE configuration.
a) Station A, roughly point the antenna towards station B (if not done in the Hardware Instal-
lation procedure)
b) Commission station A (phase 1)
c) Commission station B (phase 1)
MSS MSS
2) Fine antenna alignment and preliminary checks – Stations A & B
a) Station B, fine align the antenna towards station A, and preliminary checks
b) Station A, fine align the antenna towards station B, and preliminary checks
MSS MSS
[2] Site acceptance tests (phase 2)
3) Station A, perform all the commissioning checks and tests – Report the results in the TRS.
MSS MSS

4) Station B, perform all the commissioning checks and tests – Report the results in the TRS.
MSS MSS
7.1.5 General information about test bench drawings

In the test bench drawings depicted in the following paragraphs of this chapter, take always into account
the following considerations:
[1] Actual station configuration
For detailed information on the layout and equipment interconnections refer to the Plant documen-
tation.
[2] “1+0” and “1+1” configurations
Test bench drawings refer usually to the “1+0” configuration. When necessary, the additional material
for “1+1” configurations is drawn in dotted line.
[3] Equipment interfaces for test access points, signal meaning and use
The standard equipment interfaces for access points are always considered at Station DDF. Station
DDF is not detailed in the drawings: refer to your own plant documentation for details.
[4] Craft terminal need

The WebEML (WebEML) is always required.

7.2 Commissioning of STATION A – phase 1 (Turn up)
– Where necessary, switch OFF the power supply before disconnecting the earth connection,
– Do not connect instruments directly to the MSS/ODU cable connector since the connector
carries DC voltage used to supply the ODU.
– Do not connect the IF cable between MSS and ODU while the MSS is powered up.
7.2.1 Turn–on preliminary operations
ALL THESE OPERATIONS ARE PERFORMED WITH THE POWER OFF
3 The antenna of station A (or B) is pointed towards station B (or A) the best as possible (use compass
if necessary).
3 The hardware configuration of the equipment corresponds to the expected one.
3 Make visual inspection for units’ installation and cabling:
• The MSS subrack allocation according to the station lay–out
• The MSS subrack and units ground connections
• The power supply voltage is present with the correct polarity at the MSS power supply input
• Tributaries are cabled on the station DDF
• The MSS–ODU cables ground kit connections
• The ODU(s) ground connections (In the case of a non–integrated antenna, the antenna and the
ODU(s) must be ground connected)
• The MSS(s) / ODU(s) cables are connected to MSS(s) and ODU(s)
• The ODU(s) cables connectors waterproofing.

7.2.2 Powering up the MSS(s) with ODU(s) connected
This operation has the following scopes:
– verify the SWP present both in WebEML and NE
– make the Central Frequency and Shifter values of ODUs be acquired by MSS (so that they are
retained in the NE’s data base).
Proceed as follows:
a) Switch on the MSS by using the circuit breakers
b) Connect locally the WebEML to the MSS of the local station and perform the NE login with NEtO.
1) Make a local connection through the Ethernet cable, between the Ethernet port of the PC and
the NMS interface on the MSS
2) Power on the PC and wait for its start–up
3) Start–up the WebEML and wait for the NEtO screen
4) Insert the “local IP address” of the NE 9500 MPR-E station
5) Start supervision on the local Network Element
c) Configure the NE as explained in the Provisioning chapter.

7.3 Commissioning of STATION B – phase 1 (Turn up)
– To commission Station B, perform (at Station B premises) the same operations carried on at Station
A–Phase 1.
& For near future tests, establish, on the DDF of Station B, hardware loops on every tributary.
7.4 Fine antenna alignment and preliminary checks – Stations A & B
7.4.1 Fine antenna alignment

When Station A and Station B are fully configured and operational, and assuming that the antenna insta-
tion A (or B) has been previously correctly pointed toward the antenna in station B (or A), you should
receive some field from station B (or A).
Note 1: Verify that the ATPC is disabled.
Note 2: In case of 1+1 (with asymmetric coupler) to facilitate the alignment make sure that Channel #1
is active.
Now, proceed to a fine tuning of the antenna to improve as much as possible the received level, in both-
Station A (at Station A premises) and Station B (at Station B premises). To perform the fine antenna align-
ment refer to Annex A: fine antenna alignment on page 867.
7.4.2 Preliminary checks

At first on Station A (at Station A premises), then on Station B (at Station B premises), log in the NE and-
perform following checks by WebEML:
Subject On page
Verify ODU(s) alarm status 836
Transmitter power output check 837
Received power measurement 837
7.4.2.1 Verify ODU300/MPT-HC alarm status
Purpose: Verify no abnormal communication alarm between MSS(s) and ODU(s)
Required Instruments: PC with WebEML software
Procedure: Connect WebEML to MSS.
& WebEML ⇒ Views ⇒ Equipment
→ In the left window, select ODU ch#1n

3 In the lower right window, verify in the alarms list for that there is no internal communication failure
3 In the lower right window, verify in the alarms list that there is no TX failure
♦ Repeat for Ch#0 if any (1+1)
7.4.2.2 Transmitter power output check
Purpose: Verify via WebEML the ODU(s) transmitted power output.
& WebEML ⇒ Double click on the front panel of the Modem unit (Channel #1) (for ODU300) or on the
front panel of the MPT Access peripheral unit or MPT-HC (for MPT-HC)
3 Verify that ATPC is ”Disabled” (If required, change the ATPC status to disable in the ATPC field then
→ Apply)
3 Verify that Tx Power value complies with the suitable value already set (If required, change the Tx
Power in the RTPC field then → Apply)
♦ Repeat for Ch#0 if any (1+1).
7.4.2.3 Received power measurement
Purpose: Verify via WebEML the received power to detect any interference
& WebEML ⇒ Double click on the front panel of the Modem unit (Channel #1) (for ODU300) or on the
front panel of the MPT Access peripheral unit or MPT-HC (for MPT-HC)
→ Select “Measurements” tab panel
→ In the Sample time (sec), write the suitable measurement poling time then press → Start

Figure 585. Received power check
Pressing “Start” will prompt a graphic monitoring view of the transmitted and received levels:
Figure 586. Power measurements
Ticking the box “Show Details” in the lower left corner will call a summary view of the TX an Rx levels:

Figure 587. Received power details
3 Verify in the hop calculation (plant documentation) that the calculated received level has been
reached.
3 Verify that there are no interferences.
♦ Repeat for Ch#0 if any (1+1)
WARNING:
– If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in HSB Configuration the-
transmitter is in standby).
– If in the Tx end field the indication in dBm is +99 and, at the same time, in the relevant Rx end field
the information in dBm is –99, probably the supervision has been lost.

7.5 End of commissioning phase 1 (Turn up) in STATION A
– In Station A, proceed to a final fine alignment of the antenna toward the antenna of Station B. To per-
form the fine antenna alignment, refer to Annex A: fine antenna alignment on page 867.
– In Station A, proceed to the remote NE (station B) acquisition (by opening a second NEtO session)
in order to verify in both the stations:
3 Received level complies with hop calculation
3 No alarm showing (except unloaded tributaries)

7.6 Commissioning station A – phase 2 (acceptance test)
Commissioning phase 2 is a site acceptance test procedure made up of the required tests to ensure that
the equipment is fully operational.
This phase describes first of all the way to check and to change (if necessary) via the WebEML menu the
different configuration parameters already set, for most of them, during the Provisioning followed by var-
ious tests.
Most of the tests and checks results have to be recorded in the TRS (Test Results Sheet). Operator will
be invited to do so each time it is required by the following sentence: “Report… in the TRS.”
N.B. The lettered titles in following table [ a ) , b ) , etc.] correspond to the page’s heading titles of
the TRS document.
Test On page Report

in TRS
a) Installation and cabling visual inspection 843
Indoor System installation and cabling visual inspection 3
Outdoor System installation and cabling visual inspection 3
b) System configuration 843
Check Software Release 3
Check/set Mode (Presettings or Adaptive modulation), Channel spacing, 3

Modulation
Check/set Link Identifier configuration (optional) 3
Check/set the QoS criteria to be used 3
Check/set the Automatic Restoration Criteria (only 1+1) 3
HSB Transmission Protection (1+1 HSB configurations only) 3
Radio Protection (RPS) 3
EPS Protection 3
Check/set Tx/Rx Spacing, Transmission and Reception frequencies 3
Check/set Tx power (ATPC Off ) or Tx range and Rx threshold (ATPC On) 3
Check/set the synchronization 3
Tx and Rx power measurement (with WebEML) 3
IF Loopback functionality (ODU300) 3
Core-facing loopback functionality (MPT-HC/MPT-MC) 3
c) P32E1 unit 848
Balanced or Unbalanced impedance 3
Check/set E1 tributaries configuration 3
Protection functionality (1+1 only) 3
E1 point to point loop test 3

Test On page Report
in TRS
d) STM-1 unit 851
Check/set STM-1 configuration 3
Protection functionality (1+1 only) 3
STM-1 point to point loop test 3
e) 16E1/DS1 ASAP unit 854
Check/set E1 layer configuration 3
Check/set IMA layer configuration 3
Check/set ATM layer configuration 3
Check/set ATM PW layer configuration 3
f) AUX unit 854
Check/set AUX unit configuration 3
Check/set the Housekeeping configuration 3
g) Core-E unit 855
Check the Software Licence Code 3
Check/set Traffic Ethernet port parameters 3
h) NE configuration 855
Check/set the local NE IP address 3
Check/set OSPF Area Configuration 3
Check/set the Ethernet access (OS) configuration 3
Check/set IP static routing configuration 3
i) Data/Time settings 856 3
j) E1 Hop stability test 856 3
k) STM-1 Hop stability test 858 3
l) Ethernet Traffic stability test 860 3
m) ATM Traffic stability test 864 3
n) 64 kbit/s Service Channel functionality test (optional) 866 3

7.6.1 Installation and cabling visual inspection
7.6.1.1 Indoor System installation and cabling visual inspection
See and fill the indoor inspection check list in the TRS.
7.6.1.2 Outdoor System installation and cabling visual inspection
See and fill the indoor inspection check list in the TRS.
7.6.2 System configuration

Purpose: Verify via WebEML the configuration of the Local Station.
Procedure: Connect WebEML to MSS
7.6.2.1 Check Software Release
& WebEML ⇒ Menu bar ⇒ Menu SW Download ⇒ SW Status

Check the Software release.
Report in the TRS.
7.6.2.2 Check/set Mode (Presettings or Adaptive modulation), Channel spacing,

Modulation
& WebEML ⇒ Double click on the front panel of the Modem unit for ODU300 or of the MPT Access unit
or on the MPT-HC/MPT-MC for MPT-HC/MPT-MC → Settings tab panel
In the left window → Mode (Presettings or Adaptive modulation), Channel spacing, Modulation (Sup-
ported Modulation Schemes and Switching Threshold, if the Adaptive Modulation has been enabled)
If required, change any paramater.
Report the parameters in the TRS.
7.6.2.3 Check/set Link Identifier configuration (optional)
Double click on the front panel of the Modem unit for ODU300 or of the MPT Access unit or on the MPT-
HC/MPT-MC for MPT-HC/MPT-MC → Link Identifier
If it is necessary, change any parameter.
Report the Link Identifier status (Enabled or Disabled), and, if Enabled, the “Expected” and“Sent” values.
7.6.2.4 Check/set the QoS criteria to be used
& WebEML ⇒ Menu bar ⇒ Configuration ⇒ System Settings

Select the suitable QoS criteria to be used: Disabled/802.1p/DiffServ.
Report in the TRS.

7.6.2.5 Check/set the Automatic Restoration Criteria (only 1+1)
7.6.2.5.1 HSB Transmission Protection (1+1 HSB configurations only)
& WebEML ⇒ Views ⇒ Protection Schemes
In the left window → HSB Protection
In the lower right window → Protection Scheme Parameters Tab panel → Protection Type 1+1
If required, change Operation type (Revertive or Not Revertive) then → Apply
Report the Operation Type in the TRS.
7.6.2.5.2 Radio Protection (RPS)
In the left window → Rx Radio Protection (RPS)
7.6.2.5.3 EPS Protection
In the left window → Equipment Protection
7.6.2.6 Check/set Tx/Rx Spacing, Transmission and Reception frequencies
or on the MPT-HC/MPT-MC for MPT-HC/MPT-MC
In the central window → Channel #1 → Shifter, Tx frequency
Repeat for Channel 0 (only in 1+1)
Report the Shifter, Tx and the Rx frequencies in the TRS.
If required, change the Tx frequency then → Apply. Rx Freq. will be automatically adjusted.
7.6.2.7 Check/set Tx power (ATPC Off ) or Tx range and Rx threshold (ATPC On)
ATPC Disabled:
or on the MPT-HC/MPT-MC for MPT-HC/MPT-MC → Setting tab panel

“RTPC&ATPC” field
3 ATPC “Disabled”
Report the ATPC “Disabled” status, Tx nominal Power and Tx Power setting into theTRS.
ATPC Enabled:
or on the MPT-HC/MPT-MC for MPT-HC/MPT-MC → Setting tab panel
“RTPC&ATPC” field
3 ATPC “Enabled”
Report the ATPC “Enabled” status, ATPC Range and ATPC RX Threshold setting in the TRS.
If required, change ATPC Mode or ATPC Range or ATPC Rx Threshold then → Apply
7.6.2.8 Check/set the synchronization
& WebEML ⇒ Tab panel Synchronization

Check/set all the parameters regarding the synchronization.
Report in the TRS.
7.6.2.9 Tx and Rx power measurement (with WebEML)
Purpose: Verify via WebEML the Transmitted (PTx) and Received (PRx) power.
or on the MPT-HC/MPT-MC for MPT-HC/MPT-MC
→ From the left window → select Channel #1 → select Measurements tab panel
→ In the Sample time (sec), write the suitable measurement poling time then press → Start
Pressing “Start” will prompt a graphic monitoring view of the transmitted and received levels.
Ticking the box “Show details” in the lower left corner will call a summary view of the TX an Rx levels.
Report the Current Tx Local End (PTx) and the current Rx Local End (PRx) in the TRS.
7.6.2.10 Loopback functionality
7.6.2.10.1 IF Loopback functionality (ODU300)
Purpose: Verify via WebEML the IF cable loopback functionality (only in the local NE)

Required Instruments: PC with WebEML software and E1 Data Analyzer

Connect Pattern Generator/Error Detector analyzer on one Tributary Access
(At the Station DDF)
– A delay up to 10 seconds may be observed for each activation/deactivation.
– Ensure that the local tributary access is active (unframed and configured).
– Ensure that the local transmitter is muted (double click on the front panel of the Modem unit → Set-
tings tab panel).
IF cable loopback
Figure 588. IF Cable loopback
& WebEML ⇒ Double click on the front panel of the Modem unit → “Loopback” tab panel
In the left window → IF cable
In the lower right window → Active → Apply
3 Error Detector showing no errors.
3 Loopback showing in the Summary Block Diagram view.
To remove the loopback: in the lower right window → Not Active → Apply
Report about the Loopback functionality in the TRS.

7.6.2.10.2 Core-facing loopback functionality (MPT-HC/MPT-MC)
Purpose: Verify via WebEML the Core-facing loopback functionality (only in the local NE)

Connect Pattern Generator/Error Detector analyzer on one Tributary Access
(At the Station DDF)
– A delay up to 10 seconds may be observed for each activation/deactivation.
– Ensure that the local tributary access is active (unframed and configured).
Figure 589. Core-facing loopback
& WebEML ⇒ Double click on the front panel of the MPT-Access unit or on the MPT-HC/MPT-MC →
“Loopback” tab panel
In the left window → Core-facing
In the lower right window → Active → Apply
3 Error Detector showing no errors.
3 Loopback showing in the Summary Block Diagram view.
To remove the loopback: in the lower right window → Not Active → Apply
Report about the Loopback functionality in the TRS.

7.6.2.11 Protection functionality (1+1 only)
Purpose: Force command (if the active channel is the Main) and Lockout command (if the
active channel is the Spare)
& WebEML ⇒ View ⇒ Protection Schemes
In the left window → Rx Radio Protection → Main #1 or Spare #0
In the Commands tab panel window Commands scroll list → Forced or Lockout → Apply
Repeat for HSB Tx Protection (for “1+1 HSB” configurations only)
Repeat for Equipment Protection
3 Check in the Summary block diagram that the full channel (Tx and Rx) path is in service.
Report about the Channel protection switching functionality in the TRS.
7.6.3 P32E1 unit
7.6.3.1 Balanced or Unbalanced impedance
& WebEML ⇒ Menu bar → Configuration → System Settings

Set the impedance for the E1 streams.
Report the Impedance in the TRS.
7.6.3.2 Check/set E1 tributaries configuration
& WebEML ⇒ Double click on the front panel of the P32E1DS1 unit
In the left window → E1 port# 1
In the lower right window → “Settings” Tab panel
If it is necessary, change the E1 parameters.
Report in the TRS.
Repeat for each E1 port#

In the left window → Equipment Protection → Main #1 or Spare #0
In the Commands tab panel → Forced or Lockout → Apply
3 Check in the Summary block diagram that the full channel (TX and RX) path is in service.
7.6.3.4 E1 point to point loop test
Purpose: Verify the point to point Tributaries quality

Verify the tributaries alarm status monitoring functionality

Connect Pattern Generator/Error Detector on Tributary Access (At the Station
DDF)
& WebEML ⇒ Diagnosis ⇒ Summary Block Diagram View

Report the result in the TRS.
Figure 590. Test bench for tributary functionality check with ODU300

Figure 591. Test bench for tributary functionality check with MPT-HC/MPT-HC V2/MPT-MC
[1] Point to point Tributaries quality test
Assuming that all the tributaries have been enabled and configured (Unframed status and configu-
ration) via WebEML in both stations and that every tributary is looped at the DDF in the remote sta-
tion:
♦ Perform one minute of BER test on each E1 tributary
3 Verify that the analyzer detects no error.
3 Verify the tributary alarm status:
& WebEML ⇒ Double click on the front panel of the P32E1DS1 unit
In the lower right “Alarms” tab panel, verify that while the data analyzer is connected,
the“AlarmLossSignal” on the relevant tributary is off.
Leave the “Alarms” screen open, to perform following check
[2] Check of the tributaries alarm status monitoring functionality
To create an alarmed condition, remove the “Tributary loopback” at the Remote station.
In the lower right “Alarms”, verify that while the data analyzer is connected, the “AlarmLossSignal”on the
relevant tributary goes on.
Restore the “Tributary loopback” at the Remote station, and verify that the “AlarmLossSignal” on there-
levant tributary goes off.

Figure 592. Tributary alarm status monitoring
Report about the Tributary BER test and alarm WebEML monitoring in the TRS.
7.6.4 STM-1 unit
7.6.4.1 Check/set STM-1 configuration
& WebEML ⇒ Double click on the front panel of the SDHACC unit
In the left window → STM-1 port# 1
If it is necessary, change the STM-1 parameters.
Report in the TRS.
Repeat for each STM-1 port#2 (if any)

In the left window → Equipment Protection → Main #1 or Spare #0
In the Commands tab panel → Forced or Lockout → Apply
3 Check in the Summary block diagram that the full channel (TX and RX) path is in service.
7.6.4.3 STM-1 point to point loop test
Purpose: Verify the point to point STM-1 quality

Verify the tributaries alarm status monitoring functionality
Required Instruments: PC with WebEML software and SDH Data Analyzer

Connect Pattern Generator/Error Detector on STM-1 Access (At the Station
DDF)
& WebEML ⇒ Diagnosis ⇒ Summary Block Diagram View

Report the result in the TRS.
Figure 593. Test bench for tributary functionality check with ODU300

[1] Point to point quality test
Assuming that the STM-1 has been enabled and configured via WebEML in both stations and that
every STM-1 is looped at the DDF in the remote station:
♦ Perform one minute of BER test the STM-1
3 Verify that the analyzer detects no error.
3 Verify the STM-1 alarm status:
& WebEML ⇒ Double click on the front panel of the SDHACC unit
In the lower right “Alarms” tab panel, verify that while the data analyzer is connected,
the“AlarmLossSignal” on the relevant STM-1 is off.
Leave the “Alarms” screen open, to perform following check
[2] Check of the alarm status monitoring functionality
To create an alarmed condition, remove the “Loopback” at the Remote station.
In the lower right “Alarms”, verify that while the data analyzer is connected, the “AlarmLossSignal”on the
relevant signal goes on.
Restore the “Loopback” at the Remote station, and verify that the “AlarmLossSignal” on therelevant STM-
1 goes off.
Report about the BER test and alarm WebEML monitoring in the TRS.

7.6.5 16E1/DS1 ASAP unit
7.6.5.1 Check/set E1 layer configuration
& WebEML ⇒ Double click on the front panel of the 16E1/DS1 ASAP unit
To configure refer to par. 3.15.1 on page 407.
Report in the TRS.
7.6.5.2 Check/set IMA layer configuration
Report in the TRS.
7.6.5.3 Check/set ATM layer configuration
Report in the TRS.
7.6.5.4 Check/set ATM PW layer configuration
Report in the TRS.
7.6.6 AUX unit
7.6.6.1 Check/set AUX unit configuration
& WebEML ⇒ Double click on the front panel of the AUX unit
Report in the TRS.
7.6.6.2 Check/set the Housekeeping configuration
& WebEML ⇒ Double click on the front panel of the AUX unit
Report in the TRS.

7.6.7 Core-E unit
7.6.7.1 Check the Software Licence Code
& WebEML ⇒ Menu bar → Supervision → SW licence

Report the Licence string and code in the TRS.
7.6.7.2 Check/set Traffic Ethernet port parameters
& WebEML ⇒ Double click on the front panel of the Core-E unit
In the left window → Ethernet Port#1 or Ethernet Port#2 or Ethernet Port#3 or Ethernet Port#4 or Optical
SFP Ethernet Port #5.
If it is necessary, change the parameters.
Report in the TRS.
7.6.8 NE configuration
7.6.8.1 Check/set the local NE IP address
& WebEML ⇒ Configuration ⇒ Network Configuration ⇒ Local Configuration

Report the local IP Address in the TRS.
7.6.8.2 Check/set OSPF Area Configuration
& WebEML ⇒ Configuration ⇒ Network Configuration ⇒ IP Configuration ⇒ OSPF Area Configuration

Report the Id, IP Address, IP Mask and Stub flag in the TRS.
7.6.8.3 Check/set the Ethernet access (OS) configuration
& WebEML ⇒ Double click on the front panel fo the Core-E unit ⇒ TMN Interface tab panel
Report the IP Address, IP Mask, IP Routing protocol and OSPF Area in the TRS.
7.6.8.4 Check/set IP static routing configuration
& WebEML ⇒ Configuration ⇒ Network Configuration ⇒ IP Configuration ⇒ IP Static Routing Config-

uration
Report the IP Address, IP Mask and Default gateway IP Address or interface type into theTRS.

7.6.9 Data/Time settings
& WebEML ⇒ Menu bar ⇒ Configuration ⇒ NE Time

Enter the time settings.
Report in the TRS.
& WebEML ⇒ Menu bar ⇒ Configuration ⇒ Network Configuration ⇒ NTP Server Configuration
Enter the IP address of the NTP Server, if any.
7.6.10 E1 Hop stability test

N.B.: this test is in alternative to that described in point d) (performed on one Ethernet port)
Purpose: Verify the Hop stability

Connect Data analyzer on one Tributary Access (At the Station DDF)
– The Hop stability test is performed during two consecutive hours, one time, on one Tributary, in real-
working condition whatever the protection configuration (1+ 0 or 1+1).
– The two-hour stability test must be free of error in normal propagation conditions (out of fading
period)
♦ Via the WebEML, let only one active tributary in both station
♦ In the remote Station, place a hardware loop on the relevant tributary access (at the station DDF).
♦ In the local station, connect the E1 Data Analyzer on the relevant tributary. Check that the
“Tributary Alarm Loss” disappears.
3 Verify in both stations that there are no active software loopbacks or switching requests.
3 Verify in both stations that none alarm is showing.
Report the two-hour error-free of error Hop Stability Test result in the TRS.

Figure 595. Test bench for hop stability test with ODU300

7.6.11 STM-1 Hop stability test
N.B.: this test is in alternative to that described in point d) (performed on one Ethernet port)
Purpose: Verify the Hop stability

Connect Data analyzer on one Tributary Access (At the Station DDF)
– The Hop stability test is performed during two consecutive hours, one time, on one STM-1, in real-
working condition whatever the protection configuration (1+ 0 or 1+1).
– The two-hour stability test must be free of error in normal propagation conditions (out of fading
period)
♦ Via the WebEML, let only one active STM-1 in both station
♦ In the remote Station, place a hardware loop on the relevant STM-1 access (at the station DDF).
♦ In the local station, connect the SDH Data Analyzer on the relevant tributary. Check that the
“STM-1 Alarm Loss” disappears.
3 Verify in both stations that there are no active software loopbacks or switching requests.
3 Verify in both stations that none alarm is showing.
Report the two-hour error-free of error Hop Stability Test result in the TRS.
Figure 597. Test bench for hop stability test with ODU300


7.6.12 Ethernet Traffic stability test
Purpose: Verify the quality of point to point Ethernet Data Channels
Required Instruments: PC with WebEML software and, in alternative:

• 1 additional PC and 1 Ethernet cable
• 2 additional PCs
• 2 Ethernet Data Analyzers
Procedure:
a) Connect WebEML to MSS of local station
b) Perform the connectivity test on port #1, according to the chosen test bench:
• Test bench with 1 additional PC and 1 Ethernet cable: see point [1]
• Test bench with 2 additional PCs: see point [2]
• Test bench with 2 Ethernet Data Analyzers: see point [3]
c) Perform the connectivity test on ports #2 , #3, #4 and #5 (if enabled)

If required in plant documentation, repeat the connectivity test [step b) above] for the other three-
ports, with obvious test bench changes on remote station.
Report about the connectivity test of Ethernet Data Channels in the TRS.
d) Perform the hop stability test
1) Set up the test bench with 2 Ethernet Data Analyzers (point [3]). On both stations, connect the
Data analyzer on Ethernet port #1 on the Core-E unit.
2) Start this test after the “learning” of the MAC address.
3) Configure the pattern A generator, in order to generate continuos traffic, and set the data rate-
half to the radio capacity and with packet size of 1518 bytes.
4) Perform the stability test for 2 hours.
5) Compare the number of TX and Rx Frames on the Pattern A: the number of frames must be
equal in normal propagation conditions (out of fading period).
Report the two-hour error-free Ethernet Stability Test result in the TRS.

[1] Test bench with 1 additional PC and 1 Ethernet cable
a) Connections
On local station, connect the additional PC on Ethernet port #1 (testing port).
On remote station, through the Ethernet cable, connect the NMS Ethernet port to the
Ethernet port #1 (port to be tested)
b) Set “Enable”, “Flow Control disable”, and “Capability Advertised” for ports to test
& WebEML perform the following operations on each data port (Ethernet ports #1 to #4)
of both stations:
• Enabled ⇒ Apply
• Auto Negotiation Status ⇒ Disabled ⇒ Apply
• Flow Control ⇒ Disabled ⇒ Apply
• Capability Advertised ⇒ “1000 Mb/s Full” ⇒ Apply
c) Perform the connectivity test on port #1
1) at local station, on PC connected to Ethernet port #1 (N.B.), ping the remote station
(using) the NE’s “Ethernet Configuration IP address”) with 50 packets with 1000 byte
length.
N.B.: the “PC’s IP address” and the NE’s “Ethernet Configuration IP address” must
belong to the same subnetwork.
Windows OS details, if necessary:
– Start → Programs → Accessories → Command Prompt
– ping <space> –l <space> 1000 <space> –n <space> 50 <space> IP Address
<enter>
2) the RIGHT LED on the corresponding front panel blinks with cable inserted and traffic
running
At least 45 packets must pass without any packet loss from the 5th packet
Figure 599. Test bench for optional Ethernet Data Channel functionality with 1 additional PC and
1 Ethernet cable

[2] Test bench with 2 additional PCs
a) Connections
On local station, connect the additional PC on Ethernet port #1 (testing port)
On remote station, connect the additional PC on Ethernet port #1 (port to be tested)
of both stations:
1) at local station, on PC connected to Ethernet port #1, ping the far–end PC with 50
packets with 1000 byte length.
Windows OS details, if necessary:
– Start → Programs → Accessories → Command Prompt
– ping <space> –l <space> 1000 <space> –n <space> 50 <space> IP Address
<enter>
running.
At least 45 packets must pass without any packet loss from the 5th packet.
Figure 600. Test bench for optional Ethernet Data Channel functionality with 2 additional PCs

[3] Test bench with 2 Ethernet Data Analyzers
a) Connections
On local station, connect the Data analyzer on Ethernet port #1 (testing port)
On remote station, connect the Data analyzer on Ethernet port #1 (port to be tested)
of both stations:
1) Start this test after the “learning” of the MAC address.

2) Configure Pattern Generator A in order to generate 50 packets with 1000 byte length,
and set the data rate half of the radio capacity.
running.
At least 45 packets must pass without any packet loss from the 5th packet.
Figure 601. Test bench for optional Ethernet Data Channel functionality with
2 Ethernet Data Analyzers

7.6.13 ATM Traffic stability test
Purpose: Verify the quality of point to point ATM Data Channels (where 16E1/DS1 ASAP
unit has been installed)
Required Instruments: PC with WebEML software and 1 4xE1 ATM/IMA Generator/Analizer
Procedure:
– The Hop stability test is performed during two consecutive hours, one time, on one IMA Group con-
figured on 16E1DS ASAP peripheral, in realworking condition whatever the radio peripheral protec-
tion configuration (1+ 0 or 1+1).
– The two-hour stability test must be free of error (no ATM Cell Loss) in normal propagation conditions
(out of fading period)
a) Connect WebEML to MSS of local station
b) Check IMA connectivity in the local Station:
• "configure on ATM/IMA instrument a 4xE1 IMA Group with MPR default configuration values
• "activate the IMA Group of ATM/IMA instrument: it will result in "Not Operational" state since
no connection to MSS and IMA configuration has been yet performed
• "connect E1 ports of ATM/IMA instrument to DDF connection points corresponding to E1 ports

#1,#2,#3,#4 of relevant ASAP peripheral
– on MSS, enable E1 ports #1,#2,#3,#4 of relevant 16E1DS1 ASAP peripheral by config-

uring as Framed their Signal Mode
– without change to default configuration values, activate ATM interface #1 associated to

IMA Group #1 of relevant ASAP peripheral
– associate to IMA Group #1 of relevant ASAP peripheral and make active as IMA Links the
E1 ports #1,#2,#3,#4
– activate ATM interface #1,associated to IMA Group #1 of relevant ASAP peripheral
– the IMA Group #1 of relevant ASAP peripheral and the one in the ATM/IMA instrument
shall become "Operational" ("TSF" alarm should be cleared, if previously raised)
c) Perform the IMA connectivity test for all E1 ports of relevant ASAP peripheral(s)
Repeat the IMA connectivity test [step b) above] for the other E1 ports, with the below association
• associate to IMA Group #2 of relevant ASAP peripheral the E1 ports #5,#6,#7,#8
Report about the IMA connectivity test of ATM Data Channels in the TRS.
d) Configure ATM traffic in the local Station
• On ATM interface #1 (associated to IMA Group #1) of relevant ASAP peripheral create and con-
figure:

– "one ATM Traffic Descriptor for an ATM Circuit of type CBR, PCR=17960 cell/s,
CDVT=1000 microsecond, ATM Policing Enabled
– "one VP of "Not Logical" type, with VPI=1 and associate the above ATM TD (both for
Ingress/Egress)
• On PW Layer of relevant ASAP peripheral create one ATM PW flow associated to the above
VP, with PW Label = 100, 1 cell max per frame and 1 millisecond timeout (no VPI translation)
• On PW Layer of relevant ASAP peripheral create one ATM PW flow associated to the above
VP, with PW Label = 100, 1 cell max per frame and 1 millisecond timeout (no VPI translation)
• Configure the cross-connection of the above ATM PW flow towards the relevant radio periph-
eral, with associated VLAN ID = 4000
e) Configure in the remote Station a Loopback at DDF level, as shown in Figure 602.
f) Configure and start in the local Station the ATM Generator/Analizer
• Configure, ATM Generator of ATM/IMA instrument for one ATM Cell stream, with rate 17960
cell/s, VPI=1, VCI=1 (if the ATM Generator has this capability, use test pattern inside ATM Cells
to detect Cell Loss), without starting traffic
• Start ATM Analyzer
• Start ATM Generator
• Check the same rate of ATM Cell of configured ATM Circuit is transmitted by ATM Generator
is also received by the ATM Analyzer (since ATM Traffic is looped-back by the remote Station);
if random pattern is available on ATM/IMA instrument, directly check on ATM Analyzer that no
cell is actually lost
Report the two-hour error-free ATM Stability Test result in the TRS.
Figure 602. Test bench for ATM traffic

7.6.14 64 kbit/s Service Channel functionality test (optional)
Purpose: Verify the point to point Service Data Channel quality
Required Instruments: PC with WebEML software and RS422 / V11 64 Kbit/s Data Analyzer

Define the operational ESC ports (Enable/Disable) (local and remote NE).
Cross-connect the configured ports to the appropriate radio channel (local and
remote).
Connect Data analyzer on the service channel Access
Figure 603. Test bench for 64 kbit/s Service Channel functionality check
Assuming that the User service Channel is looped in the remote station:
♦ Perform 10 minutes of BER test.
3 Verify that the Data analyzer detects no error.
Report about the 64 Kbit/s Data channel BER test into the TRS.

7.7 Commissioning station B – Phase 2 (acceptance Test)
Repeat in Station B all the tests performed in Station A except the Hop Stability Test that has to be run
only one time for the full hop.
Fill a second Test Result Sheet for Station B
END OF COMMISSIONING ACCEPTANCE TEST
7.8 Final operations

Complete the commissioning of each NE, creating the NE operator profiles and saving its data.
7.9 Annex A: fine antenna alignment

Safety requirements for workers on antenna pole, and microwave radiations (EMF norms)
SAFETY RULES
When operating on the antenna pole, strictly follow cautions.
In particular, if ODU is powered on from MSS, do not stand on the antenna axis
and beaware of the compliance boundaries.
Antenna pre–pointing should have been done during equipment hardware installation.
This annex explains how to carry out the antenna fine alignment.
To monitor the received level during alignment in the local station:
– use the ODU Rx power monitoring in addition to a voltmeter,
– or, after having logged in the NE, use the WebEML received power measurement facility
Alignment procedure using the ODU Rx power monitoring
a) the radio link must be up and the ATPC disabled
b) in general, fine alignment should be done only on one station of the radio link
c) connect a voltmeter to the ODU (by using the Light Serfice kit cable for the MPT)
d) proceed with Vertical alignment, then with Horizontal alignment
e) in configurations with two antennas, repeat the procedure for the second antenna.
Note
Procedures for Vertical and Horizontal alignment depend on the type of integrated polemounting
employed.

ABBREVIATIONS
ABBREVIATION MEANING
ACM Adaptive Coding Modulation
ACR Adaptive Clock Recovery
ADM Add Drop Multiplexer
AIS Alarm Indication Signal
ALS Automatic Laser Shutdown
ANSI American National Standards Institute
AP Access Point
APS Automatic Protection Switching
APT Active Problem Table
AS Alarm Surveillance
ASAP Alarm Severity Assignment Profile
ATM Asynchronous Transport Module
ATPC Automatic Transmit Power Control
AVC Attribute Value Change
BBE Background Block Error
BER Bit Error Rate
BR & SW Bridge & Switch
Browser Application which allows to browse all RM-MIB objects
CCLNP ConnectionLess Network Protocol
CD Current Data
CDCC Data Communication Channel
CD-ROM Compact Disc Read Only Memory
CES Circuit Emulation Service
CI Communication Infrastructure

Abbreviations 3DB 18793 AAAA Issue 1 869/876
CLA Common Loss Alarm
CRU Clock Reference Unit
CTP Connection Termination Point
DCI Drop & Continue Interconnection
DCN Data Communications Network
DCR Differential Clock Recovery
DS Degraded Signal
EC Equipment Controller
ECC Embedded Communication Channels
EFC Ethernet Flow Control
EFD Event Forwarding Discriminator
EML Element Management Layer
EML domain A set of NEs that are maintained by the same EML-OS.
EoSDH Ethernet over SDH
EOW Engineering Order Wire
EPG Eps Protection Group
EPS Equipment Protection Switching
EPU Eps Protection Unit
EM-OS Element Manager-Operation System
EMS Event Management Services
ES Errored Second
ET Elementary Topology. It is a grouping of some nodes connected

according to specific rules. A typical ET is a ring.
ETH ETHernet
ETSI European Telecommunications Standards Institute
EW Early Warning
FCM Fixed Coding Modulation
FCS Frame Check Sequence
FD Frequency Diversity
FE Fast Ethernet

870/876 3DB 18793 AAAA Issue 1 Abbreviations
FLS Frame Loss Second
FM FM Fault Management
Gbit/s Gigabits per second
GFP Generic Frame Protocol
GNE Gateway Network Element
HBER High Bit Error Ratio
HD History Data
HET Hetero frequency
HS Hitless Switch
HSB Hot Stand-By
HTML HyperText Markup Language
ICP Internal Communication Problem
IDU InDoor Unit
IM Information Model
IMA Inverse Multiplexing over ATM
IP Internet Protocol
IWF Inter-Working Function
IEEE Institute of Electrical and Electronics Engineers
IM Information Manager
JUSM Java User Service Manager
Kbit/s Kilobits per second
LAG Link Aggregation Group
LAN Local Area Network
LAPD Link Access Procedure on D-channel
LBER Low Bit Error Ratio
LDPC Low Density Parity Check
LOF Loss Of Frame
LOS Loss Of Signal
MAC Medium Access Control
Mbit/s Megabits per seconds

MEF Metro Ethernet Forum
MIB Management Information Base
MPR Microwave Packet Radio
MPT-HC Microwave Packet Transport - High Capacity
MSS Microwave Service Switch
NE Network Element
NEC Network Element Clock
NEtO Network Element Overview
NMS Network Management system
Node It is the view of the NE at NML level
NSA Not Service Affecting
NTP NetworkTime Protocol
OC ODU Controller
OCN Object Creation Notification
ODN Object deletion Notification
ODU OutDoor Unit
OFS Out of Frame Seconds
OH OverHead
OS Operation System
PDH Plesiochronous Digital Hierarchy
PFoE Power Feed over Ethernet
PM Performance Monitoring
PNU Packet Node Unit
Port Physical Interface of a Node. A port can be SDH or PDH.
PI Physical Interface
PPI PDH Physical Interface
PRBS Pseudo Random Bit Sequence
PSU Power Supply Unit
PTU Packet Transport Unit
QL Quality Level

QoS Quality of Service
RACS Received Automatic Control Status
RAI Remote Alarm Indication
RDI Remote Defect Indication
RI Remote Inventory
RPG Rps Protection Group
RPU Rps Protection Unit
RPS Radio Protection Switching
RPPI Radio Plesyochronous Physical Interface
SA Site Aggregator
SCG Service Channel Protection Group
SCN State Change Notification
SCU Service Channel Protection Unit
SD Signal Degrade
SDH Synchronous Digital Hierarchy
SES Severely Errored Second
SF Signal Failure
SFP Small Form-factor Pluggable
SONET Synchronous Optical Network
SPDH Super PDH
SSM Synchronization Status Message
STM Synchronous Transport Module
TCA Threshold Crossing Alarm
TCO Total Cost of Ownership
TD Threshold Data
TDF Total Discarded Frames
TMN Telecommunications Management Network
TPS Tx Protection Switching
TPG Tps Protection Group
TPU Tps Protection Unit

TRCF Total Received Correct Frames
TRO Total Received Octets
TRSEF Total Received Service Errored Frames
TRsp Tx Rx spacing
TS Time Slot
TTF Total Transmitted Frames
TTO Total Transmitted Octets
TTP Trail Termination Point
UAS UnAvailable Second
UAT UnAvailable Time
USM User Service Manager
UPA Unavailable path alarm
URU Underlying Resource Unavailable
VC Virtual Channel
VCC Virtual Channel Circuit
VP Virtual Path
VPC Virtual Path Circuit
WTR Wait Time to Restore

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-Lucent 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-Lucent Technical Assis-
tance 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-Lucent Technical Assistance Center.
• creating a dedicated form on paper or file and sending it to your Local Alcatel-Lucent Technical
Assistance 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 3DB 18793 AAAA Issue 1 875/876
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:
876 9500 MPR Rel. 3.0.0 User Manual

876/876 3DB 18793 AAAA Issue 1 Customer Documentation Feedback
3DB 18793 AAAA
Edition 1
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

MSS-8MSS-4 Outdoor ODU300 MPT-HC MPTHC 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

MSS-8MSS-4 Outdoor ODU300 MPT-HC MPTHC PDF

Uploaded by

Copyright:

Available Formats

9500 MPR

Indoor: MSS-8/MSS-4 + Outdoor: ODU300 / MPT-HC / MPT-

All other trademarks are the property of their respective owners.

The information presented is subject to change without notice. Alcatel-Lucent assumes no

Copyright © 2010 Alcatel-Lucent

3DB 18793 AAAA

All rights reserved.

LIST OF TABLES ........................................................................................................................... 19

1 SAFETY, EMC, EMF, ESD NORMS AND EQUIPMENT LABELLING ........................................ 29

2 PRODUCT INFORMATION AND PLANNING ............................................................................. 39

User Manual 9500 MPR Rel. 3.0.0

3 NE MANAGEMENT BY SOFTWARE APPLICATION ................................................................. 199

9500 MPR Rel. 3.0.0 User Manual

User Manual 9500 MPR Rel. 3.0.0

9500 MPR Rel. 3.0.0 User Manual

7 LINE–UP AND COMMISSIONING ............................................................................................... 829

User Manual 9500 MPR Rel. 3.0.0

ABBREVIATIONS ............................................................................................................................ 869

CUSTOMER DOCUMENTATION FEEDBACK.............................................................................. 875

9500 MPR Rel. 3.0.0 User Manual

User Manual 9500 MPR Rel. 3.0.0

9500 MPR Rel. 3.0.0 User Manual

User Manual 9500 MPR Rel. 3.0.0

9500 MPR Rel. 3.0.0 User Manual

User Manual 9500 MPR Rel. 3.0.0

9500 MPR Rel. 3.0.0 User Manual

User Manual 9500 MPR Rel. 3.0.0

9500 MPR Rel. 3.0.0 User Manual

User Manual 9500 MPR Rel. 3.0.0

9500 MPR Rel. 3.0.0 User Manual

User Manual 9500 MPR Rel. 3.0.0

9500 MPR Rel. 3.0.0 User Manual

User Manual 9500 MPR Rel. 3.0.0

9500 MPR Rel. 3.0.0 User Manual

2) Access to the Equipment

User Manual 9500 MPR Rel. 3.0.0

SERVICE PERSONNEL SKILL

MSS-8/MSS-4 + ODU300/MPT-HC/MPT-HC V2/MPT-MC 3.0.0

ISSUE DATE DESCRIPTIONS

9500 MPR Rel. 3.0.0 User Manual

PREFACE It contains general information as preliminary information, hand-

SAFETY This section includes all the safety instructions.

INSTALLATION This section provides whole information regarding Equipment hard-

ABBREVIATIONS The abbreviation list is supplied.

User Manual 9500 MPR Rel. 3.0.0

Customer–Independent Standard Customer Documentation

b) Aims of standard Customer Documentation

Product levels and associated Customer Documentation

c) Configurations and Network Elements

d) SWP releases, versions, and CD–ROMs

9500 MPR Rel. 3.0.0 User Manual

Each handbook is identified by:

Changes introduced in the same product–release (same handbook P/N)

NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

Supplying updated handbooks to Customers

User Manual 9500 MPR Rel. 3.0.0

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

– CD-ROMs for Network Management products do not contain:

• the Installation Guides

– CD-ROMs for Network Elements products do not contain:

Suitable checks are made in order to have a virus-free product.