9500MPR1

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 Birds 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 LINEUP AND COMMISSIONING ............................................................................................... 829

7.1 Introduction .......................................................................................................................... 830
7.1.1 General ........................................................................................................................... 830
7.1.2 SafetyEMCEMFESD norms and cautions to avoid equipment damage ................... 831
7.1.3 Conventions.................................................................................................................... 831
7.1.4 Summary of the lineup, 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 Turnon 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. Birds 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. Birds Eye View - MPT Access unit (Default Counters) ................................................. 449
Figure 251. Birds 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. Birds 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 couplers 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 couplers 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 couplers 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 couplers 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
Figure 467. Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms 1.0/2.3 1U
660
Figure 468. Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U
661
Figure 469. Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U
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.
AlcatelLucent 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. AlcatelLucent 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 AlcatelLucent.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of AlcatelLucent 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 productrelease:
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 LineUp 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 AlcatelLucent 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.
CustomerIndependent Standard Customer Documentation
a) Definition
Standard Customer Documentation, referred to hereafter, must be always meant as plantindepen-
dent and is always independent of any Customization.
Plantdependent 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. Plantdependent 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 AlcatelLucent Laboratory design and Installation Dept. choices. In
particular:
the contents of the chapters associated to the software applications focus on the explanation
of the manmachine interface and of the operating procedures allowed by it;
maintenance is described down to faulty PCB location and replacement.
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 productreleases, which are the real products marketed
for their delivery at a certain productrelease availability date. A certain productrelease performs
more functionalities than the previous one.
E.g. Rel.1.0 and Rel.2.0 are two successive productreleases of the same product.
A productrelease 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 productrelease has been designed, engineered, and marketed for.
c) Configurations and Network Elements

In some cases, a productrelease 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 CDROMs

Each SWP is distributed by means of a specific SWP CDROM.
A SWP is identified by its Denomination, P/N (Part Number) and CS (Change Status), that
are printed on the CDROMs 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 CDROM 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 CDROM, that can be identified:
by the same P/N of the former CDROM, 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 "productrelease" (and "version" when the handbook is applicable to the versions
starting from it, but not to the previous ones),
the handbook name,
the handbook Part Number,
the handbook edition (usually first edition=01),
the handbook issue date. The date on the handbook does not refer to the date of print but to the date
on which the handbook source file has been completed and released for the production.
Changes introduced in the same productrelease (same handbook P/N)
The edition and date of issue might change on future handbook versions for the following reasons:
only the date changes (pointed out in the Table of Contents) when modifications are made to the 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 productrelease's
"version" marking, they are not replaced in the handbooks related to a subsequent version, if
the screen contents are unchanged.
Supplying updated handbooks to Customers
Supplying updated handbooks to Customers who have already received previous issues is submitted to
commercial criteria.
By updated handbook delivery it is meant the supply of a complete copy of the handbook new issue (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)

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)
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 -20C

temperature
MPT -40C
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 ITUR 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 bandpass 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 cutoff 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 ... CH11P P.SH. 154_C MHz
154 7547,0 7428,0 7512,0 7582,0 7666,0 3DB 06774 AAXX ... CH11P P.SH. 154_A MHz
154 7603,0 7484,0 7568,0 7638,0 7722,0 3DB 06774 ABXX ... CH22P P.SH. 154_A MHz
154 7561,0 7442,0 7526,0 7596,0 7680,0 ... CH11P P.SH.154_B MHz
3DB 06775 AAXX
160 7561,0 7442,0 7520,0 7602,0 7680,0 ... CH11P P.SH.160 MHz
154 7617,0 7498,0 7582,0 7652,0 7736,0 ... CH22P P.SH.154_B MHz
3DB 06775 ABXX
160 7617,0 7498,0 7576,0 7658,0 7736,0 ... CH22P P.SH.160 MHz
161 7240,0 7124,5 7194,5 7285,5 7355,5 3DB 06780 AAXX ... CH11P P.SH.161_A MHz
161 7310,0 7194,5 7264,5 7355,5 7425,5 3DB 06780 ABXX ... CH22P P.SH.161_A MHz
161 7365,0 7249,5 7319,5 7410,5 7480,5 3DB 06781 AAXX ... CH11P P.SH.161_B MHz
161 7435,0 7319,5 7389,5 7480,5 7550,5 3DB 06781 ABXX ... CH22P P.SH.161_B MHz
161 7390,0 7274,5 7344,5 7435,5 7505,5 3DB 06782 AAXX ... CH11P P.SH.161_C MHz
161 7460,0 7344,5 7414,5 7505,5 7575,5 3DB 06782 ABXX ... CH22P P.SH.161_C MHz
161 7540,0 7424,5 7494,5 7585,5 7655,5 3DB 06783 AAXX ... CH11P P.SH.161_D MHz
161 7610,0 7494,5 7564,5 7655,5 7725,5 3DB 06783 ABXX ... CH22P P.SH.161_D MHz
161 7665,0 7549,5 7619,5 7710,5 7780,5 3DB 06784 AAXX ... CH11P P.SH.161_E MHz
161 7735,0 7619,5 7689,5 7780,5 7850,5 3DB 06784 ABXX ... CH22P P.SH.161_E MHz
161 7690,0 7574,5 7644,5 7735,5 7805,5 3DB 06785 AAXX ... CH11P P.SH.161_F MHz
161 7760,0 7644,5 7714,5 7805,5 7875,5 3DB 06785 ABXX ... CH22P P.SH.161_F MHz

168 7299,0 7187,0 7243,0 7355,0 7411,0 3DB 10059 AAXX ... CH11P P.SH.168_B MHZ
168 7569,0 7443,0 7527,0 7611,0 7695,0 3DB 06776 AAXX ... CH11P P.SH.168 MHZ
168 7625,0 7499,0 7583,0 7667,0 7751,0 3DB 06776 ABXX ... CH22P 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 ... CH11P P.SH.119 MHz
3DB 06789 AAXX
126 8366.5 8282.5 8324.5 8408.5 8450.5 ... CH11P P.SH.126 MHz
119 8408.5 8328.0 8370.0 8447.0 8489.0 ... CH22P P.SH.119 MHz
3DB 06789 ABXX
126 8408.5 8324.5 8366.5 8450.5 8492.5 ... CH22P P.SH.126 MHz
151.614 8315.010 8204.217 8274.189 8355.831 8425.803 3DB 06787 AAXX ... CH11P P.SH.151 MHz
151.614 8384.982 8274.189 8344.161 8425.803 8495.775 3DB 06787 ABXX ... CH22P P.SH.151 MHz
208 8217.0 8064.0 8162.0 8272.0 8370.0 3DB 10073 AAXX ... CH11P P.SH.208 MHZ
208 8301.0 8148.0 8246.0 8356.0 8454.0 3DB 10073 ABXX ... CH22P P.SH.208 MHZ
266 8097.5 7905.0 8024.0 8171.0 8290.0 3DB 06788 AAXX ... CH11P P.SH.266 MHZ
266 8209.5 8017.0 8136.0 8283.0 8402.0 3DB 06788 ABXX ... CH22P P.SH.266 MHZ
294.440 7749.755 8145.915

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

... CH22P
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 ... CH11P 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 baseband processing and also modem functionalities only when ODU300 is
connected. MSS offers tributaries interfaces as well as supervision.
The MSS is frequencyindependent.
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 +
GHz Hole depth - 2mm
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
Table 26. 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.
Two mechanical solutions are adopted:
[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 subband to select the RF working channel. This implies benefits for spare
parts, order processing and frequency coordination.
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 subband to select the RF working channel. This implies benefits for spare
parts, order processing and frequency coordination.
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 13xE1s 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 13xE1s 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" E1s 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 E1s that are not fitting inside16QAM bandwidth.

Depending on the channel spacing value, the maximum number of E1s 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 E1s, 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 32xE1s and chosen to disable the Admission Control. These
32 xE1s 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 o 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 dont 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.
The IWF parameters listed above, have predetermined values and dont need to be provisioned.
Mac addresses are determined as consequences of the cross connections.
Payload size is fixed
Clock source: clock recovery differential/node timing
Flow Id provisioned by ECT/NMS
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 doesnt 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. Its 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 isnt
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
be selected as Secondary source and vice-versa.
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 o 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 o Network Config-
uration o 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 slots 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 theyve been applied it will update graphical state by
performing a refresh; if the operation completes without errors the sub-sequent refresh wont 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
select the PW label
assign the VLAN ID
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
select the PW label
assign the VLAN ID
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
select the PW label
enter the VPI
assign the VLAN ID
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, its 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:
lag-id (mandatory)
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:
lag-id (mandatory)
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:
lag-id (mandatory)
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:
lag-id (mandatory)
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:
lag-id (mandatory)
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:
lag-id (mandatory)
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:
lag-id (mandatory)
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:
lag-id (mandatory)
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
name (mandatory)
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 MAs VLAN); Explicit (MIPs are created on ports belonging to the MAs
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)
name (mandatory)
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
mepid (mandatory)
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
mepid (mandatory)
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)
Values: true|false
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

mepid (mandatory)
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
mepid (mandatory)
Range: 1-8191
enable (mandatory)
Values: true|false
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
mepid (mandatory)
Range: 1-8191
ccm enable (mandatory)
Values: true|false
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

mepid (mandatory)
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
mepid (mandatory)
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
mepid (mandatory)
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


9500MPR1

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

9500MPR1

Cargado por

Copyright:

Formatos disponibles

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

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

9500 MPR Rel. 3.0.0 User Manual

Each handbook is identified by:

Changes introduced in the same productrelease (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.

Use of the CD-ROM